diff -Nrcpad gcc-6.3.0/ChangeLog gcc-6.4.0/ChangeLog *** gcc-6.3.0/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,15 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-01-09 Andreas Tobler + + Backport from mainline + 2016-10-10 Andreas Tobler + + * configure.ac: Add aarch64-*-freebsd*. + * configure: Regenerate. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/INSTALL/binaries.html gcc-6.4.0/INSTALL/binaries.html *** gcc-6.3.0/INSTALL/binaries.html Wed Dec 21 07:54:11 2016 --- gcc-6.4.0/INSTALL/binaries.html Tue Jul 4 07:28:15 2017 *************** *** 1,150 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

We are often asked about pre-compiled versions of GCC. While we cannot ! provide these for all platforms, below you’ll find links to binaries for various platforms where creating them by yourself is not easy due to various reasons. !

!

Please note that we did not create these binaries, nor do we support them. If you have any problems installing them, please contact their makers. -

- !
!

Return to the GCC Installation page -

- - - - - - - --- 1,98 ---- ! ! ! Installing GCC: Binaries ! ! ! ! ! ! ! ! ! !

Installing GCC: Binaries

! ! We are often asked about pre-compiled versions of GCC. While we cannot ! provide these for all platforms, below you'll find links to binaries for various platforms where creating them by yourself is not easy due to various reasons. ! !

Please note that we did not create these binaries, nor do we support them. If you have any problems installing them, please contact their makers. !

!

Return to the GCC Installation page + + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/build.html gcc-6.4.0/INSTALL/build.html *** gcc-6.3.0/INSTALL/build.html Wed Dec 21 07:54:11 2016 --- gcc-6.4.0/INSTALL/build.html Tue Jul 4 07:28:15 2017 *************** *** 1,467 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

Now that GCC is configured, you are ready to build the compiler and runtime libraries. !

!

Some commands executed when making the compiler may fail (return a ! nonzero status) and be ignored by make. These failures, which are often due to files that were not found, are expected, and can safely be ignored. !

!

It is normal to have compiler warnings when compiling certain files. Unless you are a GCC developer, you can generally ignore these warnings unless they cause compilation to fail. Developers should attempt to fix any warnings encountered, however they can temporarily continue past warnings-as-errors by specifying the configure flag ! --disable-werror. !

!

On certain old systems, defining certain environment variables such as ! CC can interfere with the functioning of make. !

!

If you encounter seemingly strange errors when trying to build the compiler in a directory other than the source directory, it could be because you have previously configured the compiler in the source directory. Make sure you have done all the necessary preparations. !

!

If you build GCC on a BSD system using a directory stored in an old System ! V file system, problems may occur in running fixincludes if the ! System V file system doesn’t support symbolic links. These problems result in a failure to fix the declaration of size_t in ! sys/types.h. If you find that size_t is a signed type and that type mismatches occur, this could be the cause. !

!

The solution is not to use such a directory for building GCC. !

!

Similarly, when building from SVN or snapshots, or if you modify ! *.l files, you need the Flex lexical analyzer generator ! installed. If you do not modify *.l files, releases contain the Flex-generated files and you do not need Flex installed to build them. There is still one Flex-based lexical analyzer (part of the build machinery, not of GCC itself) that is used even if you only build the C front end. !

!

When building from SVN or snapshots, or if you modify Texinfo documentation, you need version 4.7 or later of Texinfo installed if you want Info documentation to be regenerated. Releases contain Info documentation pre-built for the unmodified documentation in the release. !

! !

Building a native compiler

For a native build, the default configuration is to perform ! a 3-stage bootstrap of the compiler when ‘make’ is invoked. This will build the entire GCC system and ensure that it compiles ! itself correctly. It can be disabled with the --disable-bootstrap ! parameter to ‘configure’, but bootstrapping is suggested because the compiler will be tested more completely and could also have better performance. -

-

The bootstrapping process will complete the following steps: -

- !

If you are short on disk space you might consider ‘make ! bootstrap-lean’ instead. The sequence of compilation is the same described above, but object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. !

!

If you wish to use non-default GCC flags when compiling the stage2 and stage3 compilers, set BOOT_CFLAGS on the command line when ! doing ‘make’. For example, if you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information as in the following example. This will save roughly 40% of disk space both for the bootstrap and the final installation. (Libraries will still contain debugging information.) -

-
- 
make BOOT_CFLAGS='-O' bootstrap
-
!

You can place non-default optimization flags into BOOT_CFLAGS; they ! are less well tested here than the default of ‘-g -O2’, but should still work. In a few cases, you may find that you need to specify special ! flags such as -msoft-float here to complete the bootstrap; or, if the native compiler miscompiles the stage1 compiler, you may need to work around this, by choosing BOOT_CFLAGS to avoid the parts ! of the stage1 compiler that were miscompiled, or by using ‘make ! bootstrap4’ to increase the number of stages of bootstrap. !

!

BOOT_CFLAGS does not apply to bootstrapped target libraries. Since these are always compiled with the compiler currently being bootstrapped, you can use CFLAGS_FOR_TARGET to modify their ! compilation flags, as for non-bootstrapped target libraries. Again, if the native compiler miscompiles the stage1 compiler, you may need to work around this by avoiding non-working parts of the stage1 compiler. Use STAGE1_TFLAGS to this end. !

!

If you used the flag --enable-languages=… to restrict ! the compilers to be built, only those you’ve actually enabled will be built. This will of course only build those runtime libraries, for which the particular compiler has been built. Please note, ! that re-defining LANGUAGES when calling ‘make’ does not work anymore! !

!

If the comparison of stage2 and stage3 fails, this normally indicates that the stage2 compiler has compiled GCC incorrectly, and is therefore a potentially serious bug which you should investigate and report. (On a few systems, meaningful comparison of object files is impossible; they always appear “different”. If you encounter this problem, you will ! need to disable comparison in the Makefile.) !

!

If you do not want to bootstrap your compiler, you can configure with ! --disable-bootstrap. In particular cases, you may want to bootstrap your compiler even if the target system is not the same as the one you are building on: for example, you could build a powerpc-unknown-linux-gnu toolchain on a powerpc64-unknown-linux-gnu host. In this case, pass ! --enable-bootstrap to the configure script. !

!

BUILD_CONFIG can be used to bring in additional customization ! to the build. It can be set to a whitespace-separated list of names. ! For each such NAME, top-level config/NAME.mk will ! be included by the top-level Makefile, bringing in any settings it contains. The default BUILD_CONFIG can be set using the ! configure option --with-build-config=NAME.... Some examples of supported build configurations are: !

!
!
‘bootstrap-O1’
!

Removes any -O-started option from BOOT_CFLAGS, and adds ! -O1 to it. ‘BUILD_CONFIG=bootstrap-O1’ is equivalent to ! ‘BOOT_CFLAGS='-g -O1'’. !

!
!
‘bootstrap-O3’
!

Analogous to bootstrap-O1. !

!
!
‘bootstrap-lto’
!

Enables Link-Time Optimization for host tools during bootstrapping. ! ‘BUILD_CONFIG=bootstrap-lto’ is equivalent to adding ! -flto to ‘BOOT_CFLAGS’. This option assumes that the host supports the linker plugin (e.g. GNU ld version 2.21 or later or GNU gold version 2.21 or later). !

!
!
‘bootstrap-lto-noplugin’
!

This option is similar to bootstrap-lto, but is intended for ! hosts that do not support the linker plugin. Without the linker plugin ! static libraries are not compiled with link-time optimizations. Since ! the GCC middle end and back end are in libbackend.a this means that only the front end is actually LTO optimized. !

!
!
‘bootstrap-debug’
!

Verifies that the compiler generates the same executable code, whether or not it is asked to emit debug information. To this end, this option builds stage2 host programs without debug information, and uses ! contrib/compare-debug to compare them with the stripped stage3 object files. If BOOT_CFLAGS is overridden so as to not enable ! debug information, stage2 will have it, and stage3 won’t. This option is enabled by default when GCC bootstrapping is enabled, if strip can turn object files compiled with and without debug info into identical object files. In addition to better test coverage, this option makes default bootstraps faster and leaner. !

!
!
‘bootstrap-debug-big’
!

Rather than comparing stripped object files, as in bootstrap-debug, this option saves internal compiler dumps during stage2 and stage3 and compares them as well, which helps catch additional potential problems, but at a great cost in terms of disk ! space. It can be specified in addition to ‘bootstrap-debug’. !

!
!
‘bootstrap-debug-lean’
!

This option saves disk space compared with bootstrap-debug-big, but at the expense of some recompilation. Instead of saving the dumps of stage2 and stage3 until the final compare, it uses ! -fcompare-debug to generate, compare and remove the dumps during stage3, repeating the compilation that already took place in stage2, whose dumps were not saved. !

!
!
‘bootstrap-debug-lib’
!

This option tests executable code invariance over debug information generation on target libraries, just like bootstrap-debug-lean tests it on host programs. It builds stage3 libraries with ! -fcompare-debug, and it can be used along with any of the bootstrap-debug options above. !

!

There aren’t -lean or -big counterparts to this option because most libraries are only build in stage3, so bootstrap compares would not get significant coverage. Moreover, the few libraries built ! in stage2 are used in stage3 host programs, so we wouldn’t want to compile stage2 libraries with different options for comparison purposes. !

!
!
‘bootstrap-debug-ckovw’
!

Arranges for error messages to be issued if the compiler built on any ! stage is run without the option -fcompare-debug. This is ! useful to verify the full -fcompare-debug testing coverage. It must be used along with bootstrap-debug-lean and bootstrap-debug-lib. !

!
!
‘bootstrap-time’
!

Arranges for the run time of each program started by the GCC driver, ! built in any stage, to be logged to time.log, in the top level of the build tree. -

-
-
! !

Building a cross compiler

When building a cross compiler, it is not generally possible to do a 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC. !

!

To build a cross compiler, we recommend first building and installing a native compiler. You can then use the native GCC compiler to build the cross compiler. The installed native compiler needs to be GCC version 2.95 or later. !

!

If the cross compiler is to be built with support for the Java programming language and the ability to compile .java source files is desired, the installed native compiler used to build the cross compiler needs to be the same GCC version as the cross compiler. In addition the cross compiler needs to be configured with ! --with-ecj-jar=…. !

!

Assuming you have already installed a native copy of GCC and configured ! your cross compiler, issue the command make, which performs the following steps: -

- !

Note that if an error occurs in any step the make process will exit. !

!

If you are not building GNU binutils in the same source tree as GCC, you will need a cross-assembler and cross-linker installed before configuring GCC. Put them in the directory ! prefix/target/bin. Here is a table of the tools you should put in this directory: !

!
!
as
!

This should be the cross-assembler. !

!
!
ld
!

This should be the cross-linker. !

!
!
ar
!

This should be the cross-archiver: a program which can manipulate ! archive files (linker libraries) in the target machine’s format. !

!
!
ranlib
!

This should be a program to construct a symbol table in an archive file. !

!

The installation of GCC will find these programs in that directory, and copy or link them to the proper place to for the cross-compiler to find them when run later. !

!

The easiest way to provide these files is to build the Binutils package. ! Configure it with the same --host and --target options that you use for configuring GCC, then build and install them. They install their executables automatically into the proper directory. Alas, they do not support all the targets that GCC supports. !

!

If you are not building a C library in the same source tree as GCC, you should also provide the target libraries and headers before configuring GCC, specifying the directories with ! --with-sysroot or --with-headers and ! --with-libs. Many targets also require “start files” such ! as crt0.o and ! crtn.o which are linked into each executable. There may be several ! alternatives for crt0.o, for use with profiling or other ! compilation options. Check your target’s definition of STARTFILE_SPEC to find out what start files it uses. !

! !

Building in parallel

GNU Make 3.80 and above, which is necessary to build GCC, support ! building in parallel. To activate this, you can use ‘make -j 2’ ! instead of ‘make’. You can also specify a bigger number, and in most cases using a value greater than the number of processors in your machine will result in fewer and shorter I/O latency hits, thus improving overall throughput; this is especially true for slow drives and network filesystems. !

! !

Building the Ada compiler

In order to build GNAT, the Ada compiler, you need a working GNAT ! compiler (GCC version 4.0 or later). ! This includes GNAT tools such as gnatmake and ! gnatlink, since the Ada front end is written in Ada and uses some GNAT-specific extensions. !

!

In order to build a cross compiler, it is suggested to install the new compiler as native first, and then use it to build the cross compiler. !

!

configure does not test whether the GNAT installation works and has a sufficiently recent version; if too old a GNAT version is ! installed, the build will fail unless --enable-languages is used to disable building the Ada front end. !

!

ADA_INCLUDE_PATH and ADA_OBJECT_PATH environment variables must not be set when building the Ada compiler, the Ada tools, or the Ada runtime libraries. You can check that your build environment is clean ! by verifying that ‘gnatls -v’ lists only one explicit path in each section. !

! !

Building with profile feedback

It is possible to use profile feedback to optimize the compiler itself. This should result in a faster compiler binary. Experiments done on x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C programs. To bootstrap the compiler with profile feedback, use make profiledbootstrap. !

!

When ‘make profiledbootstrap’ is run, it will first build a stage1 compiler. This compiler is used to build a stageprofile compiler instrumented to collect execution counts of instruction and branch ! probabilities. Then runtime libraries are compiled with profile collected. Finally a stagefeedback compiler is built using the information collected. -

-

Unlike standard bootstrap, several additional restrictions apply. The - compiler used to build stage1 needs to support a 64-bit integral type. - It is recommended to only use GCC for this. -

-
-

-

Return to the GCC Installation page -

- - - -
- - - - - --- 1,385 ---- ! ! ! Installing GCC: Building ! ! ! ! ! ! ! ! ! !

Installing GCC: Building

! ! Now that GCC is configured, you are ready to build the compiler and runtime libraries. ! !

Some commands executed when making the compiler may fail (return a ! nonzero status) and be ignored by make. These failures, which are often due to files that were not found, are expected, and can safely be ignored. ! !

It is normal to have compiler warnings when compiling certain files. Unless you are a GCC developer, you can generally ignore these warnings unless they cause compilation to fail. Developers should attempt to fix any warnings encountered, however they can temporarily continue past warnings-as-errors by specifying the configure flag ! --disable-werror. ! !

On certain old systems, defining certain environment variables such as ! CC can interfere with the functioning of make. ! !

If you encounter seemingly strange errors when trying to build the compiler in a directory other than the source directory, it could be because you have previously configured the compiler in the source directory. Make sure you have done all the necessary preparations. ! !

If you build GCC on a BSD system using a directory stored in an old System ! V file system, problems may occur in running fixincludes if the ! System V file system doesn't support symbolic links. These problems result in a failure to fix the declaration of size_t in ! sys/types.h. If you find that size_t is a signed type and that type mismatches occur, this could be the cause. ! !

The solution is not to use such a directory for building GCC. ! !

Similarly, when building from SVN or snapshots, or if you modify ! *.l files, you need the Flex lexical analyzer generator ! installed. If you do not modify *.l files, releases contain the Flex-generated files and you do not need Flex installed to build them. There is still one Flex-based lexical analyzer (part of the build machinery, not of GCC itself) that is used even if you only build the C front end. ! !

When building from SVN or snapshots, or if you modify Texinfo documentation, you need version 4.7 or later of Texinfo installed if you want Info documentation to be regenerated. Releases contain Info documentation pre-built for the unmodified documentation in the release. ! !

Building a native compiler

For a native build, the default configuration is to perform ! a 3-stage bootstrap of the compiler when ‘make’ is invoked. This will build the entire GCC system and ensure that it compiles ! itself correctly. It can be disabled with the --disable-bootstrap ! parameter to ‘configure’, but bootstrapping is suggested because the compiler will be tested more completely and could also have better performance. !

The bootstrapping process will complete the following steps: ! !

!

If you are short on disk space you might consider ‘make ! bootstrap-lean’ instead. The sequence of compilation is the same described above, but object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. ! !

If you wish to use non-default GCC flags when compiling the stage2 and stage3 compilers, set BOOT_CFLAGS on the command line when ! doing ‘make’. For example, if you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information as in the following example. This will save roughly 40% of disk space both for the bootstrap and the final installation. (Libraries will still contain debugging information.) ! 

     make BOOT_CFLAGS='-O' bootstrap
!
!

You can place non-default optimization flags into BOOT_CFLAGS; they ! are less well tested here than the default of ‘-g -O2’, but should still work. In a few cases, you may find that you need to specify special ! flags such as -msoft-float here to complete the bootstrap; or, if the native compiler miscompiles the stage1 compiler, you may need to work around this, by choosing BOOT_CFLAGS to avoid the parts ! of the stage1 compiler that were miscompiled, or by using ‘make ! bootstrap4’ to increase the number of stages of bootstrap. ! !

BOOT_CFLAGS does not apply to bootstrapped target libraries. Since these are always compiled with the compiler currently being bootstrapped, you can use CFLAGS_FOR_TARGET to modify their ! compilation flags, as for non-bootstrapped target libraries. Again, if the native compiler miscompiles the stage1 compiler, you may need to work around this by avoiding non-working parts of the stage1 compiler. Use STAGE1_TFLAGS to this end. ! !

If you used the flag --enable-languages=... to restrict ! the compilers to be built, only those you've actually enabled will be built. This will of course only build those runtime libraries, for which the particular compiler has been built. Please note, ! that re-defining LANGUAGES when calling ‘make’ does not work anymore! ! !

If the comparison of stage2 and stage3 fails, this normally indicates that the stage2 compiler has compiled GCC incorrectly, and is therefore a potentially serious bug which you should investigate and report. (On a few systems, meaningful comparison of object files is impossible; they always appear “different”. If you encounter this problem, you will ! need to disable comparison in the Makefile.) ! !

If you do not want to bootstrap your compiler, you can configure with ! --disable-bootstrap. In particular cases, you may want to bootstrap your compiler even if the target system is not the same as the one you are building on: for example, you could build a powerpc-unknown-linux-gnu toolchain on a powerpc64-unknown-linux-gnu host. In this case, pass ! --enable-bootstrap to the configure script. ! !

BUILD_CONFIG can be used to bring in additional customization ! to the build. It can be set to a whitespace-separated list of names. ! For each such NAME, top-level config/NAME.mk will ! be included by the top-level Makefile, bringing in any settings it contains. The default BUILD_CONFIG can be set using the ! configure option --with-build-config=NAME.... Some examples of supported build configurations are: ! !

!
‘bootstrap-O1’
Removes any -O-started option from BOOT_CFLAGS, and adds ! -O1 to it. ‘BUILD_CONFIG=bootstrap-O1’ is equivalent to ! ‘BOOT_CFLAGS='-g -O1'’. ! !
‘bootstrap-O3’
Analogous to bootstrap-O1. ! !
‘bootstrap-lto’
Enables Link-Time Optimization for host tools during bootstrapping. ! ‘BUILD_CONFIG=bootstrap-lto’ is equivalent to adding ! -flto to ‘BOOT_CFLAGS’. This option assumes that the host supports the linker plugin (e.g. GNU ld version 2.21 or later or GNU gold version 2.21 or later). ! !
‘bootstrap-lto-noplugin’
This option is similar to bootstrap-lto, but is intended for ! hosts that do not support the linker plugin. Without the linker plugin ! static libraries are not compiled with link-time optimizations. Since ! the GCC middle end and back end are in libbackend.a this means that only the front end is actually LTO optimized. ! !
‘bootstrap-debug’
Verifies that the compiler generates the same executable code, whether or not it is asked to emit debug information. To this end, this option builds stage2 host programs without debug information, and uses ! contrib/compare-debug to compare them with the stripped stage3 object files. If BOOT_CFLAGS is overridden so as to not enable ! debug information, stage2 will have it, and stage3 won't. This option is enabled by default when GCC bootstrapping is enabled, if strip can turn object files compiled with and without debug info into identical object files. In addition to better test coverage, this option makes default bootstraps faster and leaner. ! !
‘bootstrap-debug-big’
Rather than comparing stripped object files, as in bootstrap-debug, this option saves internal compiler dumps during stage2 and stage3 and compares them as well, which helps catch additional potential problems, but at a great cost in terms of disk ! space. It can be specified in addition to ‘bootstrap-debug’. ! !
‘bootstrap-debug-lean’
This option saves disk space compared with bootstrap-debug-big, but at the expense of some recompilation. Instead of saving the dumps of stage2 and stage3 until the final compare, it uses ! -fcompare-debug to generate, compare and remove the dumps during stage3, repeating the compilation that already took place in stage2, whose dumps were not saved. ! !
‘bootstrap-debug-lib’
This option tests executable code invariance over debug information generation on target libraries, just like bootstrap-debug-lean tests it on host programs. It builds stage3 libraries with ! -fcompare-debug, and it can be used along with any of the bootstrap-debug options above. ! !

There aren't -lean or -big counterparts to this option because most libraries are only build in stage3, so bootstrap compares would not get significant coverage. Moreover, the few libraries built ! in stage2 are used in stage3 host programs, so we wouldn't want to compile stage2 libraries with different options for comparison purposes. ! !

‘bootstrap-debug-ckovw’
Arranges for error messages to be issued if the compiler built on any ! stage is run without the option -fcompare-debug. This is ! useful to verify the full -fcompare-debug testing coverage. It must be used along with bootstrap-debug-lean and bootstrap-debug-lib. ! !
‘bootstrap-time’
Arranges for the run time of each program started by the GCC driver, ! built in any stage, to be logged to time.log, in the top level of the build tree. !
! !

Building a cross compiler

When building a cross compiler, it is not generally possible to do a 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC. ! !

To build a cross compiler, we recommend first building and installing a native compiler. You can then use the native GCC compiler to build the cross compiler. The installed native compiler needs to be GCC version 2.95 or later. ! !

If the cross compiler is to be built with support for the Java programming language and the ability to compile .java source files is desired, the installed native compiler used to build the cross compiler needs to be the same GCC version as the cross compiler. In addition the cross compiler needs to be configured with ! --with-ecj-jar=.... ! !

Assuming you have already installed a native copy of GCC and configured ! your cross compiler, issue the command make, which performs the following steps: !

!

Note that if an error occurs in any step the make process will exit. ! !

If you are not building GNU binutils in the same source tree as GCC, you will need a cross-assembler and cross-linker installed before configuring GCC. Put them in the directory ! prefix/target/bin. Here is a table of the tools you should put in this directory: ! !

!
as
This should be the cross-assembler. ! !
ld
This should be the cross-linker. ! !
ar
This should be the cross-archiver: a program which can manipulate ! archive files (linker libraries) in the target machine's format. ! !
ranlib
This should be a program to construct a symbol table in an archive file.
!

The installation of GCC will find these programs in that directory, and copy or link them to the proper place to for the cross-compiler to find them when run later. ! !

The easiest way to provide these files is to build the Binutils package. ! Configure it with the same --host and --target options that you use for configuring GCC, then build and install them. They install their executables automatically into the proper directory. Alas, they do not support all the targets that GCC supports. ! !

If you are not building a C library in the same source tree as GCC, you should also provide the target libraries and headers before configuring GCC, specifying the directories with ! --with-sysroot or --with-headers and ! --with-libs. Many targets also require “start files” such ! as crt0.o and ! crtn.o which are linked into each executable. There may be several ! alternatives for crt0.o, for use with profiling or other ! compilation options. Check your target's definition of STARTFILE_SPEC to find out what start files it uses. ! !

Building in parallel

GNU Make 3.80 and above, which is necessary to build GCC, support ! building in parallel. To activate this, you can use ‘make -j 2’ ! instead of ‘make’. You can also specify a bigger number, and in most cases using a value greater than the number of processors in your machine will result in fewer and shorter I/O latency hits, thus improving overall throughput; this is especially true for slow drives and network filesystems. ! !

Building the Ada compiler

In order to build GNAT, the Ada compiler, you need a working GNAT ! compiler (GCC version 4.0 or later). ! This includes GNAT tools such as gnatmake and ! gnatlink, since the Ada front end is written in Ada and uses some GNAT-specific extensions. ! !

In order to build a cross compiler, it is suggested to install the new compiler as native first, and then use it to build the cross compiler. ! !

configure does not test whether the GNAT installation works and has a sufficiently recent version; if too old a GNAT version is ! installed, the build will fail unless --enable-languages is used to disable building the Ada front end. ! !

ADA_INCLUDE_PATH and ADA_OBJECT_PATH environment variables must not be set when building the Ada compiler, the Ada tools, or the Ada runtime libraries. You can check that your build environment is clean ! by verifying that ‘gnatls -v’ lists only one explicit path in each section. ! !

Building with profile feedback

It is possible to use profile feedback to optimize the compiler itself. This should result in a faster compiler binary. Experiments done on x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C programs. To bootstrap the compiler with profile feedback, use make profiledbootstrap. ! !

When ‘make profiledbootstrap’ is run, it will first build a stage1 compiler. This compiler is used to build a stageprofile compiler instrumented to collect execution counts of instruction and branch ! probabilities. Then runtime libraries are compiled with profile collected. Finally a stagefeedback compiler is built using the information collected. +

Unlike standard bootstrap, several additional restrictions apply. The + compiler used to build stage1 needs to support a 64-bit integral type. + It is recommended to only use GCC for this. +

+

Return to the GCC Installation page + + + + + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/configure.html gcc-6.4.0/INSTALL/configure.html *** gcc-6.3.0/INSTALL/configure.html Wed Dec 21 07:54:10 2016 --- gcc-6.4.0/INSTALL/configure.html Tue Jul 4 07:28:15 2017 *************** *** 1,617 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

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 via SVN, srcdir must refer to the top ! gcc directory, the one where the MAINTAINERS file can be ! found, and not its gcc subdirectory, otherwise the build will fail. !

!

If either srcdir or objdir is located on an automounted NFS ! file system, the shell’s built-in pwd command will return temporary pathnames. Using these can lead to various sorts of build ! problems. To avoid this issue, set the PWDCMD environment ! variable to an automounter-aware pwd command, e.g., ! pawd or ‘amq -w’, during the configuration and build phases. !

!

First, we highly recommend that GCC be built into a separate directory from the sources which does not reside within the source tree. This is how we generally build GCC; building ! where srcdir == objdir should still work, but doesn’t get extensive testing; building where objdir is a subdirectory of srcdir is unsupported. !

!

If you have previously built GCC in the same directory for a ! different target machine, do ‘make distclean’ to delete all files ! that might be invalid. One of the files this deletes is Makefile; ! if ‘make distclean’ complains that Makefile does not exist ! or issues a message like “don’t know how to make distclean” it probably means that the directory is already suitably clean. However, with the recommended method of building in a separate objdir, you should simply use a different objdir for each target. !

!

Second, when configuring a native system, either cc or ! gcc must be in your path or you must set CC in your environment before running configure. Otherwise the configuration scripts may fail. -

!

To configure GCC: !

!
! 
% mkdir objdir
! % cd objdir
! % srcdir/configure [options] [target]
!
! !

Distributor options

If you will be distributing binary versions of GCC, with modifications to the source code, you should use the options described in this section to make clear that your version contains modifications. !

!
!
--with-pkgversion=version
!

Specify a string that identifies your package. You may wish to include a build number or build date. This version string will be ! included in the output of gcc --version. This suffix does ! not replace the default version string, only the ‘GCC’ part. !

!

The default value is ‘GCC’. !

!
!
--with-bugurl=url
!

Specify the URL that users should visit if they wish to report a bug. You are of course welcome to forward bugs reported to you to the FSF, if you determine that they are not bugs in your modifications. -

-

The default value refers to the FSF’s GCC bug tracker. -

-
-
! !

Target specification

! ! ! !

Options specification

Use options to override several configure time options for ! GCC. A list of supported options follows; ‘configure ! --help’ may list other options, but those not listed below may not work and should not normally be used. !

!

Note that each --enable option has a corresponding ! --disable option and that each --with option has a ! corresponding --without option. !

!
!
--prefix=dirname
!

Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to ! /usr/local. !

!

We highly recommend against dirname being the same or a subdirectory of objdir or vice versa. If specifying a directory ! beneath a user’s home directory tree, some shells will not expand ! dirname correctly if it contains the ‘~’ metacharacter; use ! $HOME instead. !

!

The following standard autoconf options are supported. Normally you should not need to use these options. !

!
--exec-prefix=dirname
!

Specify the toplevel installation directory for architecture-dependent files. The default is prefix. !

!
!
--bindir=dirname
!

Specify the installation directory for the executables called by users ! (such as gcc and g++). The default is ! exec-prefix/bin. !

!
!
--libdir=dirname
!

Specify the installation directory for object code libraries and ! internal data files of GCC. The default is exec-prefix/lib. !

!
!
--libexecdir=dirname
!

Specify the installation directory for internal executables of GCC. ! The default is exec-prefix/libexec. !

!
!
--with-slibdir=dirname
!

Specify the installation directory for the shared libgcc library. The default is libdir. !

!
!
--datarootdir=dirname
!

Specify the root of the directory tree for read-only architecture-independent ! data files referenced by GCC. The default is prefix/share. !

!
!
--infodir=dirname
!

Specify the installation directory for documentation in info format. ! The default is datarootdir/info. !

!
!
--datadir=dirname
!

Specify the installation directory for some architecture-independent data files referenced by GCC. The default is datarootdir. !

!
!
--docdir=dirname
!

Specify the installation directory for documentation files (other ! than Info) for GCC. The default is datarootdir/doc. !

!
!
--htmldir=dirname
!

Specify the installation directory for HTML documentation files. The default is docdir. !

!
!
--pdfdir=dirname
!

Specify the installation directory for PDF documentation files. The default is docdir. !

!
!
--mandir=dirname
!

Specify the installation directory for manual pages. The default is ! datarootdir/man. (Note that the manual pages are only extracts from the full GCC manuals, which are provided in Texinfo format. The manpages are derived by an automatic conversion process from parts of the full manual.) !

!
!
--with-gxx-include-dir=dirname
!

Specify the installation directory for G++ header files. The default depends on other configuration options, and differs between cross and native configurations. !

!
!
--with-specs=specs
!

Specify additional command line driver SPECS. This can be useful if you need to turn on a non-standard feature by ! default without modifying the compiler’s source code, for instance ! --with-specs=%{!fcommon:%{!fno-common:-fno-common}}. See “Spec Files” in the main manual -

-
-
!
!
--program-prefix=prefix
!

GCC supports some transformations of the names of its programs when installing them. This option prepends prefix to the names of programs to install in bindir (see above). For example, specifying ! --program-prefix=foo- would result in ‘gcc’ ! being installed as /usr/local/bin/foo-gcc. !

!
!
--program-suffix=suffix
!

Appends suffix to the names of programs to install in bindir ! (see above). For example, specifying --program-suffix=-3.1 ! would result in ‘gcc’ being installed as ! /usr/local/bin/gcc-3.1. !

!
!
--program-transform-name=pattern
!

Applies the ‘sed’ script pattern to be applied to the names of programs to install in bindir (see above). pattern has to ! consist of one or more basic ‘sed’ editing commands, separated by ! semicolons. For example, if you want the ‘gcc’ program name to be ! transformed to the installed program /usr/local/bin/myowngcc and ! the ‘g++’ program name to be transformed to ! /usr/local/bin/gspecial++ without changing other program names, you could use the pattern ! --program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/' to achieve this effect. !

!

All three options can be combined and used together, resulting in more complex conversion patterns. As a basic rule, prefix (and suffix) are prepended (appended) before further transformations can happen with a special transformation script pattern. !

!

As currently implemented, this option only takes effect for native ! builds; cross compiler binaries’ names are not transformed even when a transformation is explicitly asked for by one of these options. !

!

For native builds, some of the installed programs are also installed with the target alias in front of their name, as in ! ‘i686-pc-linux-gnu-gcc’. All of the above transformations happen before the target alias is prepended to the name—so, specifying ! --program-prefix=foo- and program-suffix=-3.1, the resulting binary would be installed as ! /usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1. !

!

As a last shortcoming, none of the installed Ada programs are transformed yet, which will be fixed in some time. !

!
!
--with-local-prefix=dirname
!

Specify the installation directory for local include files. The default is ! /usr/local. Specify this option if you want the compiler to ! search directory dirname/include for locally installed ! header files instead of /usr/local/include. !

!

You should specify --with-local-prefix only if your ! site has a different convention (not /usr/local) for where to put site-specific files. !

!

The default value for --with-local-prefix is /usr/local ! regardless of the value of --prefix. Specifying ! --prefix has no effect on which directory GCC searches for local header files. This may seem counterintuitive, but actually it is logical. !

!

The purpose of --prefix is to specify where to install ! GCC. The local header files in /usr/local/include—if you put any in that directory—are not part of GCC. They are part of other programs—perhaps many others. (GCC installs its own header files in ! another directory which is based on the --prefix value.) !

!

Both the local-prefix include directory and the GCC-prefix include ! directory are part of GCC’s “system include” directories. Although these two directories are not fixed, they need to be searched in the proper order for the correct processing of the include_next directive. The local-prefix include directory is searched before the GCC-prefix include directory. Another characteristic of system include directories is that pedantic warnings are turned off for headers in these directories. !

!

Some autoconf macros add -I directory options to the compiler command line, to ensure that directories containing installed ! packages’ headers are searched. When directory is one of GCC’s system include directories, GCC will ignore the option so that system directories continue to be processed in the correct order. This may result in a search order different from what was specified but the directory will still be searched. !

!

GCC automatically searches for ordinary libraries using ! GCC_EXEC_PREFIX. Thus, when the same installation prefix is used for both GCC and packages, GCC will automatically search for both headers and libraries. This provides a configuration that is easy to use. GCC behaves in a manner similar to that when it is ! installed as a system compiler in /usr. !

!

Sites that need to install multiple versions of GCC may not want to use the above simple configuration. It is possible to use the ! --program-prefix, --program-suffix and ! --program-transform-name options to install multiple versions into a single directory, but it may be simpler to use different prefixes ! and the --with-local-prefix option to specify the location of the site-specific files for each version. It will then be necessary for users to specify explicitly the location of local site libraries ! (e.g., with LIBRARY_PATH). !

!

The same value can be used for both --with-local-prefix and ! --prefix provided it is not /usr. This can be used ! to avoid the default search of /usr/local/include. !

!

Do not specify /usr as the --with-local-prefix! ! The directory you use for --with-local-prefix must not ! contain any of the system’s standard header files. If it did contain them, certain programs would be miscompiled (including GNU Emacs, on certain targets), because this would override and nullify the header ! file corrections made by the fixincludes script. !

!

Indications are that people who use this option use it based on mistaken ideas of what it is for. People use it as if it specified where to install part of GCC. Perhaps they make this assumption because installing GCC creates the directory. !

!
!
--with-native-system-header-dir=dirname
!

Specifies that dirname is the directory that contains native system ! header files, rather than /usr/include. This option is most useful if you are creating a compiler that should be isolated from the system as much as possible. It is most commonly used with the ! --with-sysroot option and will cause GCC to search dirname inside the system root specified by that option. !

!
!
--enable-shared[=package[,…]]
!

Build shared versions of libraries, if shared libraries are supported on the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that support shared libraries. !

!

If a list of packages is given as an argument, build shared libraries only for the listed packages. For other packages, only static libraries will be built. Package names currently recognized in the GCC tree are ! ‘libgcc’ (also known as ‘gcc’), ‘libstdc++’ (not ! ‘libstdc++-v3’), ‘libffi’, ‘zlib’, ‘boehm-gc’, ! ‘ada’, ‘libada’, ‘libjava’, ‘libgo’, and ‘libobjc’. ! Note ‘libiberty’ does not support shared libraries at all. !

!

Use --disable-shared to build only static libraries. Note that ! --disable-shared does not accept a list of package names as ! argument, only --enable-shared does. !

!

Contrast with --enable-host-shared, which affects host code. !

!
!
--enable-host-shared
!

Specify that the host code should be built into position-independent machine code (with -fPIC), allowing it to be used within shared libraries, but yielding a slightly slower compiler. !

!

This option is required when building the libgccjit.so library. !

!

Contrast with --enable-shared, which affects target libraries. !

!
!
--with-gnu-as
!

Specify that the compiler should assume that the assembler it finds is the GNU assembler. However, this does not modify the rules to find an assembler and will result in confusion if the assembler found is not actually the GNU assembler. (Confusion may also result if the compiler finds the GNU assembler but has not been ! configured with --with-gnu-as.) If you have more than one assembler installed on your system, you may want to use this option in ! connection with --with-as=pathname or ! --with-build-time-tools=pathname. !

!

The following systems are the only ones where it makes a difference whether you use the GNU assembler. On any other system, ! --with-gnu-as has no effect. !

!
    !
  • ‘hppa1.0-any-any’ !
  • ‘hppa1.1-any-any’ !
  • ‘sparc-sun-solaris2.any’ !
  • ‘sparc64-any-solaris2.any’ !
!
!
--with-as=pathname
!

Specify that the compiler should use the assembler pointed to by pathname, rather than the one found by the standard rules to find an assembler, which are: !

    !
  • Unless GCC is being built with a cross compiler, check the ! libexec/gcc/target/version directory. ! libexec defaults to exec-prefix/libexec; exec-prefix defaults to prefix, which ! defaults to /usr/local unless overridden by the ! --prefix=pathname switch described above. target ! is the target system triple, such as ‘sparc-sun-solaris2.7’, and version denotes the GCC version, such as 3.0. !
  • If the target system is the same that you are building on, check ! operating system specific directories (e.g. /usr/ccs/bin on Sun Solaris 2). !
  • Check in the PATH for a tool whose name is prefixed by the target system triple. !
  • Check in the PATH for a tool whose name is not prefixed by the target system triple, if the host and target system triple are the same (in other words, we use a host tool if it can be used for ! the target as well). !
!

You may want to use --with-as if no assembler is installed in the directories listed above, or if you have multiple assemblers installed and want to choose one that is not found by the above rules. !

!
!
--with-gnu-ld
!

Same as --with-gnu-as but for the linker. !

!
!
--with-ld=pathname
!

Same as --with-as but for the linker. !

!
!
--with-stabs
!

Specify that stabs debugging information should be used instead of whatever format the host normally uses. Normally GCC uses the same debug format as the host system. !

!

On MIPS based systems and on Alphas, you must specify whether you want GCC to create the normal ECOFF debugging format, or to use BSD-style stabs passed through the ECOFF symbol table. The normal ECOFF debug format cannot fully handle languages other than C. BSD stabs format can handle other languages, but it only works with the GNU debugger GDB. !

!

Normally, GCC uses the ECOFF debugging format by default; if you ! prefer BSD stabs, specify --with-stabs when you configure GCC. !

!

No matter which default you choose when you configure GCC, the user ! can use the -gcoff and -gstabs+ options to specify explicitly the debug format for a particular compilation. !

!

--with-stabs is meaningful on the ISC system on the 386, also, if ! --with-gas is used. It selects use of stabs debugging information embedded in COFF output. This kind of debugging information supports C++ well; ordinary COFF debugging information does not. !

!

--with-stabs is also meaningful on 386 systems running SVR4. It selects use of stabs debugging information embedded in ELF output. The C++ compiler currently (2.6.0) does not support the DWARF debugging information normally used on 386 SVR4 platforms; stabs provide a workable alternative. This requires gas and gdb, as the normal SVR4 tools can not generate or interpret stabs. !

!
!
--with-tls=dialect
!

Specify the default TLS dialect, for systems were there is a choice. For ARM targets, possible values for dialect are gnu or gnu2, which select between the original GNU dialect and the GNU TLS descriptor-based dialect. !

!
!
--enable-multiarch
!

Specify whether to enable or disable multiarch support. The default is to check for glibc start files in a multiarch location, and enable it if the files are found. The auto detection is enabled for native builds, ! and for cross builds configured with --with-sysroot, and without ! --with-native-system-header-dir. More documentation about multiarch can be found at https://wiki.debian.org/Multiarch. !

!
!
--enable-vtable-verify
!

Specify whether to enable or disable the vtable verification feature. Enabling this feature causes libstdc++ to be built with its virtual calls in verifiable mode. This means that, when linked with libvtv, every virtual call in libstdc++ will verify the vtable pointer through which the call will be made before actually making the call. If not linked with libvtv, ! the verifier will call stub functions (in libstdc++ itself) and do nothing. If vtable verification is disabled, then libstdc++ is not built with its virtual calls in verifiable mode at all. However the libvtv library will ! still be built (see --disable-libvtv to turn off building libvtv). ! --disable-vtable-verify is the default. !

!
!
--disable-multilib
!

Specify that multiple target libraries to support different target variants, calling conventions, etc. should not be built. The default is to build a predefined set of them. !

!

Some targets provide finer-grained control over which multilibs are built ! (e.g., --disable-softfloat): !

!
arm-*-*
!

fpu, 26bit, underscore, interwork, biendian, nofmult. !

!
!
m68*-*-*
!

softfloat, m68881, m68000, m68020. !

!
!
mips*-*-*
!

single-float, biendian, softfloat. !

!
!
powerpc*-*-*, rs6000*-*-*
!

aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, sysv, aix. -

-
-
!
!
--with-multilib-list=list
!
--without-multilib-list
!

Specify what multilibs to build. Currently only implemented for arm*-*-*, sh*-*-* and x86-64-*-linux*. !

!
!
arm*-*-*
!

list is either default or aprofile. Specifying default is equivalent to omitting this option while specifying aprofile builds multilibs for each combination of ISA (-marm or -mthumb), architecture (-march=armv7-a, -march=armv7ve, --- 1,495 ---- ! ! ! Installing GCC: Configuration ! ! ! ! ! ! ! ! ! !

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 via SVN, srcdir must refer to the top ! gcc directory, the one where the MAINTAINERS file can be ! found, and not its gcc subdirectory, otherwise the build will fail. ! !

If either srcdir or objdir is located on an automounted NFS ! file system, the shell's built-in pwd command will return temporary pathnames. Using these can lead to various sorts of build ! problems. To avoid this issue, set the PWDCMD environment ! variable to an automounter-aware pwd command, e.g., ! pawd or ‘amq -w’, during the configuration and build phases. ! !

First, we highly recommend that GCC be built into a separate directory from the sources which does not reside within the source tree. This is how we generally build GCC; building ! where srcdir == objdir should still work, but doesn't get extensive testing; building where objdir is a subdirectory of srcdir is unsupported. ! !

If you have previously built GCC in the same directory for a ! different target machine, do ‘make distclean’ to delete all files ! that might be invalid. One of the files this deletes is Makefile; ! if ‘make distclean’ complains that Makefile does not exist ! or issues a message like “don't know how to make distclean” it probably means that the directory is already suitably clean. However, with the recommended method of building in a separate objdir, you should simply use a different objdir for each target. ! !

Second, when configuring a native system, either cc or ! gcc must be in your path or you must set CC in your environment before running configure. Otherwise the configuration scripts may fail. !

To configure GCC: ! 

     % mkdir objdir
!      % cd objdir
!      % srcdir/configure [options] [target]
!
!

Distributor options

If you will be distributing binary versions of GCC, with modifications to the source code, you should use the options described in this section to make clear that your version contains modifications. ! !

!
--with-pkgversion=version
Specify a string that identifies your package. You may wish to include a build number or build date. This version string will be ! included in the output of gcc --version. This suffix does ! not replace the default version string, only the ‘GCC’ part. ! !

The default value is ‘GCC’. ! !

--with-bugurl=url
Specify the URL that users should visit if they wish to report a bug. You are of course welcome to forward bugs reported to you to the FSF, if you determine that they are not bugs in your modifications. !

The default value refers to the FSF's GCC bug tracker. ! !

! !

Target specification

! !
    !
  • GCC has code to correctly determine the correct value for target for nearly all native systems. Therefore, we highly recommend you do not provide a configure target when configuring a native compiler. !
  • target must be specified as --target=target when configuring a cross compiler; examples of valid targets would be m68k-elf, sh-elf, etc. !
  • Specifying just target instead of --target=target ! implies that the host defaults to target. !
!

Options specification

Use options to override several configure time options for ! GCC. A list of supported options follows; ‘configure ! --help’ may list other options, but those not listed below may not work and should not normally be used. ! !

Note that each --enable option has a corresponding ! --disable option and that each --with option has a ! corresponding --without option. ! !

!
--prefix=dirname
Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to ! /usr/local. ! !

We highly recommend against dirname being the same or a subdirectory of objdir or vice versa. If specifying a directory ! beneath a user's home directory tree, some shells will not expand ! dirname correctly if it contains the ‘~’ metacharacter; use ! $HOME instead. ! !

The following standard autoconf options are supported. Normally you should not need to use these options. !

!
--exec-prefix=dirname
Specify the toplevel installation directory for architecture-dependent files. The default is prefix. ! !
--bindir=dirname
Specify the installation directory for the executables called by users ! (such as gcc and g++). The default is ! exec-prefix/bin. ! !
--libdir=dirname
Specify the installation directory for object code libraries and ! internal data files of GCC. The default is exec-prefix/lib. ! !
--libexecdir=dirname
Specify the installation directory for internal executables of GCC. ! The default is exec-prefix/libexec. ! !
--with-slibdir=dirname
Specify the installation directory for the shared libgcc library. The default is libdir. ! !
--datarootdir=dirname
Specify the root of the directory tree for read-only architecture-independent ! data files referenced by GCC. The default is prefix/share. ! !
--infodir=dirname
Specify the installation directory for documentation in info format. ! The default is datarootdir/info. ! !
--datadir=dirname
Specify the installation directory for some architecture-independent data files referenced by GCC. The default is datarootdir. ! !
--docdir=dirname
Specify the installation directory for documentation files (other ! than Info) for GCC. The default is datarootdir/doc. ! !
--htmldir=dirname
Specify the installation directory for HTML documentation files. The default is docdir. ! !
--pdfdir=dirname
Specify the installation directory for PDF documentation files. The default is docdir. ! !
--mandir=dirname
Specify the installation directory for manual pages. The default is ! datarootdir/man. (Note that the manual pages are only extracts from the full GCC manuals, which are provided in Texinfo format. The manpages are derived by an automatic conversion process from parts of the full manual.) ! !
--with-gxx-include-dir=dirname
Specify the installation directory for G++ header files. The default depends on other configuration options, and differs between cross and native configurations. ! !
--with-specs=specs
Specify additional command line driver SPECS. This can be useful if you need to turn on a non-standard feature by ! default without modifying the compiler's source code, for instance ! --with-specs=%{!fcommon:%{!fno-common:-fno-common}}. See “Spec Files” in the main manual !
! !
--program-prefix=prefix
GCC supports some transformations of the names of its programs when installing them. This option prepends prefix to the names of programs to install in bindir (see above). For example, specifying ! --program-prefix=foo- would result in ‘gcc’ ! being installed as /usr/local/bin/foo-gcc. ! !
--program-suffix=suffix
Appends suffix to the names of programs to install in bindir ! (see above). For example, specifying --program-suffix=-3.1 ! would result in ‘gcc’ being installed as ! /usr/local/bin/gcc-3.1. ! !
--program-transform-name=pattern
Applies the ‘sed’ script pattern to be applied to the names of programs to install in bindir (see above). pattern has to ! consist of one or more basic ‘sed’ editing commands, separated by ! semicolons. For example, if you want the ‘gcc’ program name to be ! transformed to the installed program /usr/local/bin/myowngcc and ! the ‘g++’ program name to be transformed to ! /usr/local/bin/gspecial++ without changing other program names, you could use the pattern ! --program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/' to achieve this effect. ! !

All three options can be combined and used together, resulting in more complex conversion patterns. As a basic rule, prefix (and suffix) are prepended (appended) before further transformations can happen with a special transformation script pattern. ! !

As currently implemented, this option only takes effect for native ! builds; cross compiler binaries' names are not transformed even when a transformation is explicitly asked for by one of these options. ! !

For native builds, some of the installed programs are also installed with the target alias in front of their name, as in ! ‘i686-pc-linux-gnu-gcc’. All of the above transformations happen before the target alias is prepended to the name—so, specifying ! --program-prefix=foo- and program-suffix=-3.1, the resulting binary would be installed as ! /usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1. ! !

As a last shortcoming, none of the installed Ada programs are transformed yet, which will be fixed in some time. ! !

--with-local-prefix=dirname
Specify the installation directory for local include files. The default is ! /usr/local. Specify this option if you want the compiler to ! search directory dirname/include for locally installed ! header files instead of /usr/local/include. ! !

You should specify --with-local-prefix only if your ! site has a different convention (not /usr/local) for where to put site-specific files. ! !

The default value for --with-local-prefix is /usr/local ! regardless of the value of --prefix. Specifying ! --prefix has no effect on which directory GCC searches for local header files. This may seem counterintuitive, but actually it is logical. ! !

The purpose of --prefix is to specify where to install ! GCC. The local header files in /usr/local/include—if you put any in that directory—are not part of GCC. They are part of other programs—perhaps many others. (GCC installs its own header files in ! another directory which is based on the --prefix value.) ! !

Both the local-prefix include directory and the GCC-prefix include ! directory are part of GCC's “system include” directories. Although these two directories are not fixed, they need to be searched in the proper order for the correct processing of the include_next directive. The local-prefix include directory is searched before the GCC-prefix include directory. Another characteristic of system include directories is that pedantic warnings are turned off for headers in these directories. ! !

Some autoconf macros add -I directory options to the compiler command line, to ensure that directories containing installed ! packages' headers are searched. When directory is one of GCC's system include directories, GCC will ignore the option so that system directories continue to be processed in the correct order. This may result in a search order different from what was specified but the directory will still be searched. ! !

GCC automatically searches for ordinary libraries using ! GCC_EXEC_PREFIX. Thus, when the same installation prefix is used for both GCC and packages, GCC will automatically search for both headers and libraries. This provides a configuration that is easy to use. GCC behaves in a manner similar to that when it is ! installed as a system compiler in /usr. ! !

Sites that need to install multiple versions of GCC may not want to use the above simple configuration. It is possible to use the ! --program-prefix, --program-suffix and ! --program-transform-name options to install multiple versions into a single directory, but it may be simpler to use different prefixes ! and the --with-local-prefix option to specify the location of the site-specific files for each version. It will then be necessary for users to specify explicitly the location of local site libraries ! (e.g., with LIBRARY_PATH). ! !

The same value can be used for both --with-local-prefix and ! --prefix provided it is not /usr. This can be used ! to avoid the default search of /usr/local/include. ! !

Do not specify /usr as the --with-local-prefix! ! The directory you use for --with-local-prefix must not ! contain any of the system's standard header files. If it did contain them, certain programs would be miscompiled (including GNU Emacs, on certain targets), because this would override and nullify the header ! file corrections made by the fixincludes script. ! !

Indications are that people who use this option use it based on mistaken ideas of what it is for. People use it as if it specified where to install part of GCC. Perhaps they make this assumption because installing GCC creates the directory. ! !

--with-native-system-header-dir=dirname
Specifies that dirname is the directory that contains native system ! header files, rather than /usr/include. This option is most useful if you are creating a compiler that should be isolated from the system as much as possible. It is most commonly used with the ! --with-sysroot option and will cause GCC to search dirname inside the system root specified by that option. ! !
--enable-shared[=package[,...]]
Build shared versions of libraries, if shared libraries are supported on the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that support shared libraries. ! !

If a list of packages is given as an argument, build shared libraries only for the listed packages. For other packages, only static libraries will be built. Package names currently recognized in the GCC tree are ! ‘libgcc’ (also known as ‘gcc’), ‘libstdc++’ (not ! ‘libstdc++-v3’), ‘libffi’, ‘zlib’, ‘boehm-gc’, ! ‘ada’, ‘libada’, ‘libjava’, ‘libgo’, and ‘libobjc’. ! Note ‘libiberty’ does not support shared libraries at all. ! !

Use --disable-shared to build only static libraries. Note that ! --disable-shared does not accept a list of package names as ! argument, only --enable-shared does. ! !

Contrast with --enable-host-shared, which affects host code. ! !

--enable-host-shared
Specify that the host code should be built into position-independent machine code (with -fPIC), allowing it to be used within shared libraries, but yielding a slightly slower compiler. ! !

This option is required when building the libgccjit.so library. ! !

Contrast with --enable-shared, which affects target libraries. ! !

--with-gnu-as
Specify that the compiler should assume that the assembler it finds is the GNU assembler. However, this does not modify the rules to find an assembler and will result in confusion if the assembler found is not actually the GNU assembler. (Confusion may also result if the compiler finds the GNU assembler but has not been ! configured with --with-gnu-as.) If you have more than one assembler installed on your system, you may want to use this option in ! connection with --with-as=pathname or ! --with-build-time-tools=pathname. ! !

The following systems are the only ones where it makes a difference whether you use the GNU assembler. On any other system, ! --with-gnu-as has no effect. !

    !
  • ‘hppa1.0-any-any’ !
  • ‘hppa1.1-any-any’ !
  • ‘sparc-sun-solaris2.any’ !
  • ‘sparc64-any-solaris2.any’ !
! !
--with-as=pathname
Specify that the compiler should use the assembler pointed to by pathname, rather than the one found by the standard rules to find an assembler, which are: !
    !
  • Unless GCC is being built with a cross compiler, check the ! libexec/gcc/target/version directory. ! libexec defaults to exec-prefix/libexec; exec-prefix defaults to prefix, which ! defaults to /usr/local unless overridden by the ! --prefix=pathname switch described above. target ! is the target system triple, such as ‘sparc-sun-solaris2.7’, and version denotes the GCC version, such as 3.0. !
  • If the target system is the same that you are building on, check ! operating system specific directories (e.g. /usr/ccs/bin on Sun Solaris 2). !
  • Check in the PATH for a tool whose name is prefixed by the target system triple. !
  • Check in the PATH for a tool whose name is not prefixed by the target system triple, if the host and target system triple are the same (in other words, we use a host tool if it can be used for ! the target as well). !
!

You may want to use --with-as if no assembler is installed in the directories listed above, or if you have multiple assemblers installed and want to choose one that is not found by the above rules. ! !

--with-gnu-ld
Same as --with-gnu-as but for the linker. ! !
--with-ld=pathname
Same as --with-as but for the linker. ! !
--with-stabs
Specify that stabs debugging information should be used instead of whatever format the host normally uses. Normally GCC uses the same debug format as the host system. ! !

On MIPS based systems and on Alphas, you must specify whether you want GCC to create the normal ECOFF debugging format, or to use BSD-style stabs passed through the ECOFF symbol table. The normal ECOFF debug format cannot fully handle languages other than C. BSD stabs format can handle other languages, but it only works with the GNU debugger GDB. ! !

Normally, GCC uses the ECOFF debugging format by default; if you ! prefer BSD stabs, specify --with-stabs when you configure GCC. ! !

No matter which default you choose when you configure GCC, the user ! can use the -gcoff and -gstabs+ options to specify explicitly the debug format for a particular compilation. ! !

--with-stabs is meaningful on the ISC system on the 386, also, if ! --with-gas is used. It selects use of stabs debugging information embedded in COFF output. This kind of debugging information supports C++ well; ordinary COFF debugging information does not. ! !

--with-stabs is also meaningful on 386 systems running SVR4. It selects use of stabs debugging information embedded in ELF output. The C++ compiler currently (2.6.0) does not support the DWARF debugging information normally used on 386 SVR4 platforms; stabs provide a workable alternative. This requires gas and gdb, as the normal SVR4 tools can not generate or interpret stabs. ! !

--with-tls=dialect
Specify the default TLS dialect, for systems were there is a choice. For ARM targets, possible values for dialect are gnu or gnu2, which select between the original GNU dialect and the GNU TLS descriptor-based dialect. ! !
--enable-multiarch
Specify whether to enable or disable multiarch support. The default is to check for glibc start files in a multiarch location, and enable it if the files are found. The auto detection is enabled for native builds, ! and for cross builds configured with --with-sysroot, and without ! --with-native-system-header-dir. More documentation about multiarch can be found at https://wiki.debian.org/Multiarch. ! !
--enable-sjlj-exceptions
Force use of the setjmp/longjmp-based scheme for exceptions. ! ‘configure’ ordinarily picks the correct value based on the platform. ! Only use this option if you are sure you need a different setting. ! !
--enable-vtable-verify
Specify whether to enable or disable the vtable verification feature. Enabling this feature causes libstdc++ to be built with its virtual calls in verifiable mode. This means that, when linked with libvtv, every virtual call in libstdc++ will verify the vtable pointer through which the call will be made before actually making the call. If not linked with libvtv, ! the verifier will call stub functions (in libstdc++ itself) and do nothing. If vtable verification is disabled, then libstdc++ is not built with its virtual calls in verifiable mode at all. However the libvtv library will ! still be built (see --disable-libvtv to turn off building libvtv). ! --disable-vtable-verify is the default. ! !
--disable-multilib
Specify that multiple target libraries to support different target variants, calling conventions, etc. should not be built. The default is to build a predefined set of them. ! !

Some targets provide finer-grained control over which multilibs are built ! (e.g., --disable-softfloat): !

!
arm-*-*
fpu, 26bit, underscore, interwork, biendian, nofmult. ! !
m68*-*-*
softfloat, m68881, m68000, m68020. ! !
mips*-*-*
single-float, biendian, softfloat. ! !
powerpc*-*-*, rs6000*-*-*
aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, sysv, aix. !
! !
--with-multilib-list=list
--without-multilib-list
Specify what multilibs to build. Currently only implemented for arm*-*-*, sh*-*-* and x86-64-*-linux*. ! !
!
arm*-*-*
list is either default or aprofile. Specifying default is equivalent to omitting this option while specifying aprofile builds multilibs for each combination of ISA (-marm or -mthumb), architecture (-march=armv7-a, -march=armv7ve, *************** or -march=armv8-a), FPU ava *** 619,2073 **** -mfpu=neon, -mfpu=vfpv4-d16, -mfpu=neon-vfpv4 or -mfpu=neon-fp-armv8 depending on architecture) and floating-point ABI (-mfloat-abi=softfp or -mfloat-abi=hard). !

!
!
sh*-*-*
!

list is a comma separated list of CPU names. These must be of the form sh* or m* (in which case they match the compiler option for that processor). The list should not contain any endian options - ! these are handled by --with-endian. !

!

If list is empty, then there will be no multilibs for extra processors. The multilib for the secondary endian remains enabled. !

!

As a special case, if an entry in the list starts with a ! ! (exclamation point), then it is added to the list of excluded multilibs. ! Entries of this sort should be compatible with ‘MULTILIB_EXCLUDES’ (once the leading ! has been stripped). !

!

If --with-multilib-list is not given, then a default set of ! multilibs is selected based on the value of --target. This is usually the complete set of libraries, but some targets imply a more specialized subset. -

-

Example 1: to configure a compiler for SH4A only, but supporting both - endians, with little endian being the default: -

- 
--with-cpu=sh4a --with-endian=little,big --with-multilib-list=
-
!

Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with only little endian SH4AL: !

! 
--with-cpu=sh4a --with-endian=little,big \
! --with-multilib-list=sh4al,!mb/m4al
!
! !
!
x86-64-*-linux*
!

list is a comma separated list of m32, m64 and mx32 to enable 32-bit, 64-bit and x32 run-time libraries, respectively. If list is empty, then there will be no multilibs and only the default run-time library will be enabled. !

!

If --with-multilib-list is not given, then only 32-bit and ! 64-bit run-time libraries will be enabled. !

!
!
--with-endian=endians
!

Specify what endians to use. Currently only implemented for sh*-*-*. !

!

endians may be one of the following: !

!
big
!

Use big endian exclusively. !

!
little
!

Use little endian exclusively. !

!
big,little
!

Use big endian by default. Provide a multilib for little endian. !

!
little,big
!

Use little endian by default. Provide a multilib for big endian. !

!
!
--enable-threads
!

Specify that the target supports threads. This affects the Objective-C compiler and runtime ! library, and exception handling for other languages like C++ and Java. On some systems, this is the default. !

!

In general, the best (and, in many cases, the only known) threading model available will be configured for use. Beware that on some systems, GCC has not been taught what threading models are generally ! available for the system. In this case, --enable-threads is an ! alias for --enable-threads=single. !

!
!
--disable-threads
!

Specify that threading support should be disabled for the system. ! This is an alias for --enable-threads=single. !

!
!
--enable-threads=lib
!

Specify that lib is the thread support library. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. The possibilities for lib are: !

!
!
aix
!

AIX thread support. !

!
dce
!

DCE thread support. !

!
lynx
!

LynxOS thread support. !

!
mipssde
!

MIPS SDE thread support. !

!
no
!

This is an alias for ‘single’. !

!
posix
!

Generic POSIX/Unix98 thread support. !

!
rtems
!

RTEMS thread support. !

!
single
!

Disable thread support, should work for all platforms. !

!
tpf
!

TPF thread support. !

!
vxworks
!

VxWorks thread support. !

!
win32
!

Microsoft Win32 API thread support. !

!
!
--enable-tls
!

Specify that the target supports TLS (Thread Local Storage). Usually configure can correctly determine if TLS is supported. In cases where it guesses incorrectly, TLS can be explicitly enabled or disabled with ! --enable-tls or --disable-tls. This can happen if the assembler supports TLS but the C library does not, or if the assumptions made by the configure test are incorrect. !

!
!
--disable-tls
!

Specify that the target does not support TLS. ! This is an alias for --enable-tls=no. !

!
!
--with-cpu=cpu
!
--with-cpu-32=cpu
!
--with-cpu-64=cpu
!

Specify which cpu variant the compiler should generate code for by default. ! cpu will be used as the default value of the -mcpu= switch. This option is only supported on some targets, including ARC, ARM, i386, M68k, ! PowerPC, and SPARC. It is mandatory for ARC. The --with-cpu-32 and ! --with-cpu-64 options specify separate default CPUs for 32-bit and 64-bit modes; these options are only supported for i386, x86-64, PowerPC, and SPARC. !

!
!
--with-schedule=cpu
!
--with-arch=cpu
!
--with-arch-32=cpu
!
--with-arch-64=cpu
!
--with-tune=cpu
!
--with-tune-32=cpu
!
--with-tune-64=cpu
!
--with-abi=abi
!
--with-fpu=type
!
--with-float=type
!

These configure options provide default values for the -mschedule=, ! -march=, -mtune=, -mabi=, and -mfpu= ! options and for -mhard-float or -msoft-float. As with ! --with-cpu, which switches will be accepted and acceptable values of the arguments depend on the target. !

!
!
--with-mode=mode
!

Specify if the compiler should default to -marm or -mthumb. This option is only supported on ARM targets. !

!
!
--with-stack-offset=num
!

This option sets the default for the -mstack-offset=num option, and will thus generally also control the setting of this option for libraries. This option is only supported on Epiphany targets. !

!
!
--with-fpmath=isa
!

This options sets -mfpmath=sse by default and specifies the default ! ISA for floating-point arithmetics. You can select either ‘sse’ which ! enables -msse2 or ‘avx’ which enables -mavx by default. This option is only supported on i386 and x86-64 targets. !

!
!
--with-fp-32=mode
!

On MIPS targets, set the default value for the -mfp option when using the o32 ABI. The possibilities for mode are: !

!
32
!

Use the o32 FP32 ABI extension, as with the -mfp32 command-line ! option. !

!
xx
!

Use the o32 FPXX ABI extension, as with the -mfpxx command-line ! option. !

!
64
!

Use the o32 FP64 ABI extension, as with the -mfp64 command-line ! option. !

!

In the absence of this configuration option the default is to use the o32 FP32 ABI extension. !

!
!
--with-odd-spreg-32
!

On MIPS targets, set the -modd-spreg option by default when using the o32 ABI. !

!
!
--without-odd-spreg-32
!

On MIPS targets, set the -mno-odd-spreg option by default when using the o32 ABI. This is normally used in conjunction with ! --with-fp-32=64 in order to target the o32 FP64A ABI extension. !

!
!
--with-nan=encoding
!

On MIPS targets, set the default encoding convention to use for the special not-a-number (NaN) IEEE 754 floating-point data. The possibilities for encoding are: !

!
legacy
!

Use the legacy encoding, as with the -mnan=legacy command-line ! option. !

!
2008
!

Use the 754-2008 encoding, as with the -mnan=2008 command-line ! option. !

!

To use this configuration option you must have an assembler version ! installed that supports the -mnan= command-line option too. In the absence of this configuration option the default convention is ! the legacy encoding, as when neither of the -mnan=2008 and ! -mnan=legacy command-line options has been used. !

!
!
--with-divide=type
!

Specify how the compiler should generate code for checking for ! division by zero. This option is only supported on the MIPS target. The possibilities for type are: !

!
traps
!

Division by zero checks use conditional traps (this is the default on ! systems that support conditional traps). !

!
breaks
!

Division by zero checks use the break instruction. !

! !
!
--with-llsc
!

On MIPS targets, make -mllsc the default when no ! -mno-llsc option is passed. This is the default for Linux-based targets, as the kernel will emulate them if the ISA does not provide them. !

!
!
--without-llsc
!

On MIPS targets, make -mno-llsc the default when no ! -mllsc option is passed. !

!
!
--with-synci
!

On MIPS targets, make -msynci the default when no ! -mno-synci option is passed. !

!
!
--without-synci
!

On MIPS targets, make -mno-synci the default when no ! -msynci option is passed. This is the default. !

!
!
--with-mips-plt
!

On MIPS targets, make use of copy relocations and PLTs. These features are extensions to the traditional SVR4-based MIPS ABIs and require support from GNU binutils and the runtime C library. !

!
!
--enable-__cxa_atexit
!

Define if you want to use __cxa_atexit, rather than atexit, to ! register C++ destructors for local statics and global objects. This is essential for fully standards-compliant handling of destructors, but requires __cxa_atexit in libc. This option is currently only available on systems with GNU libc. When enabled, this will cause ! -fuse-cxa-atexit to be passed by default. !

!
!
--enable-gnu-indirect-function
!

Define if you want to enable the ifunc attribute. This option is currently only available on systems with GNU libc on certain targets. !

!
!
--enable-target-optspace
!

Specify that target ! libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. !

!
!
--with-cpp-install-dir=dirname
!

Specify that the user visible cpp program should be installed ! in prefix/dirname/cpp, in addition to bindir. !

!
!
--enable-comdat
!

Enable COMDAT group support. This is primarily used to override the automatically detected value. !

!
!
--enable-initfini-array
!

Force the use of sections .init_array and .fini_array (instead of .init and .fini) for constructors and ! destructors. Option --disable-initfini-array has the opposite effect. If neither option is specified, the configure script will try to guess whether the .init_array and .fini_array sections are supported and, if they are, use them. !

!
!
--enable-link-mutex
!

When building GCC, use a mutex to avoid linking the compilers for multiple languages at the same time, to avoid thrashing on build systems with limited free memory. The default is not to use such a mutex. !

!
!
--enable-maintainer-mode
!

The build rules that regenerate the Autoconf and Automake output files as ! well as the GCC master message catalog gcc.pot are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the ! catalog, configuring with --enable-maintainer-mode will enable this. Note that you need a recent version of the gettext tools to do so. !

!
!
--disable-bootstrap
!

For a native build, the default configuration is to perform ! a 3-stage bootstrap of the compiler when ‘make’ is invoked, testing that GCC can compile itself correctly. If you want to disable ! this process, you can configure with --disable-bootstrap. !

!
!
--enable-bootstrap
!

In special cases, you may want to perform a 3-stage build ! even if the target and host triplets are different. This is possible when the host can run code compiled for ! the target (e.g. host is i686-linux, target is i486-linux). Starting from GCC 4.2, to do this you have to configure explicitly ! with --enable-bootstrap. !

!
!
--enable-generated-files-in-srcdir
!

Neither the .c and .h files that are generated from Bison and flex nor the info manuals and man pages that are built from the .texi files are present in the SVN development tree. When building GCC from that development tree, or from one of our snapshots, those generated files are placed in your build directory, which allows for the source to be in a readonly directory. !

!

If you configure with --enable-generated-files-in-srcdir then those generated files will go into the source directory. This is mainly intended for generating release or prerelease tarballs of the GCC sources, since it is not a requirement that the users of source releases to have flex, Bison, or makeinfo. !

!
!
--enable-version-specific-runtime-libs
!

Specify that runtime libraries should be installed in the compiler specific ! subdirectory (libdir/gcc) rather than the usual places. In ! addition, ‘libstdc++’’s include files will be installed into libdir unless you overruled it by using ! --with-gxx-include-dir=dirname. Using this option is particularly useful if you intend to use several versions of GCC in ! parallel. This is currently supported by ‘libgfortran’, ! ‘libjava’, ‘libstdc++’, and ‘libobjc’. !

!
!
--with-aix-soname=‘aix’, ‘svr4’ or ‘both’
!

Traditional AIX shared library versioning (versioned Shared Object files as members of unversioned Archive Library files named ! ‘lib.a’) causes numerous headaches for package managers. However, Import Files as members of Archive Library files allow for filename-based versioning of shared libraries as seen on Linux/SVR4, ! where this is called the "SONAME". But as they prevent static linking, Import Files may be used with Runtime Linking only, where the ! linker does search for ‘libNAME.so’ before ‘libNAME.a’ library ! filenames with the ‘-lNAME’ linker flag. !

!

For detailed information please refer to the AIX ! ld ! Command reference. !

!

As long as shared library creation is enabled, upon: !

!
--with-aix-soname=aix
!
--with-aix-soname=both
!

A (traditional AIX) Shared Archive Library file is created: !

    !
  • using the ‘libNAME.a’ filename scheme !
  • with the Shared Object file as archive member named ! ‘libNAME.so.V’ (except for ‘libgcc_s’, where the Shared ! Object file is named ‘shr.o’ for backwards compatibility), which !
      !
    • - is used for runtime loading from inside the ‘libNAME.a’ file !
    • - is used for dynamic loading via ! dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER) !
    • - is used for shared linking !
    • - is used for static linking, so no separate Static Archive Library file is needed !
    !
!
!
--with-aix-soname=both
!
--with-aix-soname=svr4
!

A (second) Shared Archive Library file is created: !

    !
  • using the ‘libNAME.so.V’ filename scheme !
  • with the Shared Object file as archive member named ! ‘shr.o’, which !
      !
    • - is created with the -G linker flag !
    • - has the F_LOADONLY flag set !
    • - is used for runtime loading from inside the ‘libNAME.so.V’ file !
    • - is used for dynamic loading via dlopen("libNAME.so.V(shr.o)", RTLD_MEMBER) !
    !
  • with the Import File as archive member named ‘shr.imp’, which !
      !
    • - refers to ‘libNAME.so.V(shr.o)’ as the "SONAME", to be recorded in the Loader Section of subsequent binaries !
    • - indicates whether ‘libNAME.so.V(shr.o)’ is 32 or 64 bit !
    • - lists all the public symbols exported by ‘lib.so.V(shr.o)’, ! eventually decorated with the ‘weak’ Keyword !
    • - is necessary for shared linking against ‘lib.so.V(shr.o)’ !
    !
!

A symbolic link using the ‘libNAME.so’ filename scheme is created: !

    !
  • pointing to the ‘libNAME.so.V’ Shared Archive Library file !
  • to permit the ld Command to find ‘lib.so.V(shr.imp)’ via ! the ‘-lNAME’ argument (requires Runtime Linking to be enabled) !
  • to permit dynamic loading of ‘lib.so.V(shr.o)’ without the need ! to specify the version number via dlopen("libNAME.so(shr.o)", RTLD_MEMBER) !
!
!
!

As long as static library creation is enabled, upon: !

!
--with-aix-soname=svr4
!

A Static Archive Library is created: !

    !
  • using the ‘libNAME.a’ filename scheme !
  • with all the Static Object files as archive members, which !
      !
    • - are used for static linking !
    !
!
!
!

While the aix-soname=‘svr4’ option does not create Shared Object files as members of unversioned Archive Library files any more, package managers still are responsible to transfer Shared Object files found as member of a previously installed unversioned Archive Library file into the newly installed Archive Library file with the same filename. !

!

WARNING: Creating Shared Object files with Runtime Linking enabled may bloat the TOC, eventually leading to TOC overflow errors, ! requiring the use of either the -Wl,-bbigtoc linker flag (seen to break with the GDB debugger) or some of the TOC-related compiler flags, see “RS/6000 and PowerPC Options” in the main manual. !

!

--with-aix-soname is currently supported by ‘libgcc_s’ only, so this option is still experimental and not for normal use yet. !

!

Default is the traditional behavior --with-aix-soname=‘aix’. !

!
!
--enable-languages=lang1,lang2,…
!

Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for langN you can issue the following command in the ! gcc directory of your GCC source tree:
!

! 
grep ^language= */config-lang.in
!
!

Currently, you can use any of the following: all, ada, c, c++, fortran, ! go, java, jit, lto, objc, obj-c++. ! Building the Ada compiler has special requirements, see below. If you do not pass this flag, or specify the option all, then all ! default languages available in the gcc sub-tree will be configured. Ada, Go, Jit, and Objective-C++ are not default languages. LTO is not a ! default language, but is built by default because --enable-lto is enabled by default. The other languages are default languages. !

!
!
--enable-stage1-languages=lang1,lang2,…
!

Specify that a particular subset of compilers and their runtime libraries should be built with the system C compiler during stage 1 of the bootstrap process, rather than only in later stages with the bootstrapped C compiler. The list of valid values is the same as for ! --enable-languages, and the option all will select all ! of the languages enabled by --enable-languages. This option is primarily useful for GCC development; for instance, when a development version of the compiler cannot bootstrap due to compiler bugs, or when one is debugging front ends other than the C front end. When this option is used, one can then build the target libraries for the ! specified languages with the stage-1 compiler by using make ! stage1-bubble all-target, or run the testsuite on the stage-1 compiler ! for the specified languages using make stage1-start check-gcc. !

!
!
--disable-libada
!

Specify that the run-time libraries and tools used by GNAT should not be built. This can be useful for debugging, or for compatibility with previous Ada build procedures, when it was required to explicitly ! do a ‘make -C gcc gnatlib_and_tools’. !

!
!
--disable-libsanitizer
!

Specify that the run-time libraries for the various sanitizers should not be built. !

!
!
--disable-libssp
!

Specify that the run-time libraries for stack smashing protection should not be built. !

!
!
--disable-libquadmath
!

Specify that the GCC quad-precision math library should not be built. On some systems, the library is required to be linkable when building ! the Fortran front end, unless --disable-libquadmath-support is used. !

!
!
--disable-libquadmath-support
!

Specify that the Fortran front end and libgfortran do not add support for libquadmath on systems supporting it. !

!
!
--disable-libgomp
!

Specify that the GNU Offloading and Multi Processing Runtime Library should not be built. !

!
!
--disable-libvtv
!

Specify that the run-time libraries used by vtable verification should not be built. !

!
!
--with-dwarf2
!

Specify that the compiler should use DWARF 2 debugging information as the default. !

!
!
--with-advance-toolchain=at
!

On 64-bit PowerPC Linux systems, configure the compiler to use the header files, library files, and the dynamic linker from the Advance Toolchain release at instead of the default versions that are provided by the Linux distribution. In general, this option is intended for the developers of GCC, and it is not intended for general use. !

!
!
--enable-targets=all
!
--enable-targets=target_list
!

Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers. These are compilers that are able to generate either 64-bit or 32-bit ! code. Typically, the corresponding 32-bit target, e.g. powerpc-linux for powerpc64-linux, only generates 32-bit code. This option enables the 32-bit target to be a bi-arch compiler, which is useful when you want a bi-arch compiler that defaults to 32-bit, and ! you are building a bi-arch or multi-arch binutils in a combined tree. On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), ! defaulted to o32. Currently, this option only affects sparc-linux, powerpc-linux, x86-linux, mips-linux and s390-linux. !

!
!
--enable-default-pie
!

Turn on -fPIE and -pie by default. !

!
!
--enable-secureplt
!

This option enables -msecure-plt by default for powerpc-linux. See “RS/6000 and PowerPC Options” in the main manual !

!
!
--enable-default-ssp
!

Turn on -fstack-protector-strong by default. !

!
!
--enable-cld
!

This option enables -mcld by default for 32-bit x86 targets. See “i386 and x86-64 Options” in the main manual !

!
!
--enable-win32-registry
!
--enable-win32-registry=key
!
--disable-win32-registry
!

The --enable-win32-registry option enables Microsoft Windows-hosted GCC to look up installations paths in the registry using the following key: -

-
- 
HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\key
-
!

key defaults to GCC version number, and can be overridden by the ! --enable-win32-registry=key option. Vendors and distributors who use custom installers are encouraged to provide a different key, perhaps one comprised of vendor name and GCC version number, to avoid conflict with existing installations. This feature is enabled ! by default, and can be disabled by --disable-win32-registry option. This option has no effect on the other hosts. !

!
!
--nfp
!

Specify that the machine does not have a floating point unit. This ! option only applies to ‘m68k-sun-sunosn’. On any other ! system, --nfp has no effect. !

!
!
--enable-werror
!
--disable-werror
!
--enable-werror=yes
!
--enable-werror=no
!

When you specify this option, it controls whether certain files in the ! compiler are built with -Werror in bootstrap stage2 and later. ! If you don’t specify it, -Werror is turned on for the main development trunk. However it defaults to off for release branches and ! final releases. The specific files which get -Werror are controlled by the Makefiles. !

!
!
--enable-checking
!
--enable-checking=list
!

When you specify this option, the compiler is built to perform internal consistency checks of the requested complexity. This does not change the generated code, but adds error checking within the compiler. This will slow down the compiler and may only work properly if you are building ! the compiler with GCC. This is ‘yes’ by default when building ! from SVN or snapshots, but ‘release’ for releases. The default ! for building the stage1 compiler is ‘yes’. More control over the checks may be had by specifying list. The categories of ! checks available are ‘yes’ (most common checks ! ‘assert,misc,tree,gc,rtlflag,runtime’), ‘no’ (no checks at ! all), ‘all’ (all but ‘valgrind’), ‘release’ (cheapest ! checks ‘assert,runtime’) or ‘none’ (same as ‘no’). ! Individual checks can be enabled with these flags ‘assert’, ! ‘df’, ‘fold’, ‘gc’, ‘gcac’ ‘misc’, ‘rtl’, ! ‘rtlflag’, ‘runtime’, ‘tree’, and ‘valgrind’. !

!

The ‘valgrind’ check requires the external valgrind simulator, available from http://valgrind.org/. The ! ‘df’, ‘rtl’, ‘gcac’ and ‘valgrind’ checks are very expensive. ! To disable all checking, ‘--disable-checking’ or ! ‘--enable-checking=none’ must be explicitly requested. Disabling assertions will make the compiler and runtime slightly faster but increase the risk of undetected internal errors causing wrong code to be generated. !

!
!
--disable-stage1-checking
!
--enable-stage1-checking
!
--enable-stage1-checking=list
!

If no --enable-checking option is specified the stage1 ! compiler will be built with ‘yes’ checking enabled, otherwise the stage1 checking flags are the same as specified by ! --enable-checking. To build the stage1 compiler with ! different checking options use --enable-stage1-checking. ! The list of checking options is the same as for --enable-checking. If your system is too slow or too small to bootstrap a released compiler ! with checking for stage1 enabled, you can use ‘--disable-stage1-checking’ to disable checking for the stage1 compiler. !

!
!
--enable-coverage
!
--enable-coverage=level
!

With this option, the compiler is built to collect self coverage information, every time it is run. This is for internal development purposes, and only works when the compiler is being built with gcc. The level argument controls whether the compiler is built optimized or ! not, values are ‘opt’ and ‘noopt’. For coverage analysis you want to disable optimization, for performance analysis you want to enable optimization. When coverage is enabled, the default level is without optimization. !

!
!
--enable-gather-detailed-mem-stats
!

When this option is specified more detailed information on memory allocation is gathered. This information is printed when using ! -fmem-report. !

!
!
--enable-valgrind-annotations
!

Mark selected memory related operations in the compiler when run under valgrind to suppress false positives. !

!
!
--enable-nls
!
--disable-nls
!

The --enable-nls option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not doing a ! canadian cross build. The --disable-nls option disables NLS. !

!
!
--with-included-gettext
!

If NLS is enabled, the --with-included-gettext option causes the build ! procedure to prefer its copy of GNU gettext. !

!
!
--with-catgets
!

If NLS is enabled, and if the host lacks gettext but has the inferior catgets interface, the GCC build procedure normally ! ignores catgets and instead uses GCC’s copy of the GNU ! gettext library. The --with-catgets option causes the ! build procedure to use the host’s catgets in this situation. !

!
!
--with-libiconv-prefix=dir
!

Search for libiconv header files in dir/include and ! libiconv library files in dir/lib. !

!
!
--enable-obsolete
!

Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. !

!

All support for systems which have been obsoleted in one release of GCC is removed entirely in the next major release, unless someone steps forward to maintain the port. !

!
!
--enable-decimal-float
!
--enable-decimal-float=yes
!
--enable-decimal-float=no
!
--enable-decimal-float=bid
!
--enable-decimal-float=dpd
!
--disable-decimal-float
!

Enable (or disable) support for the C decimal floating point extension that is in the IEEE 754-2008 standard. This is enabled by default only on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also support it, but require the user to specifically enable it. You can optionally control which decimal floating point format is used (either ! ‘bid’ or ‘dpd’). The ‘bid’ (binary integer decimal) ! format is default on i386 and x86_64 systems, and the ‘dpd’ (densely packed decimal) format is default on PowerPC systems. !

!
!
--enable-fixed-point
!
--disable-fixed-point
!

Enable (or disable) support for C fixed-point arithmetic. This option is enabled by default for some targets (such as MIPS) which have hardware-support for fixed-point operations. On other targets, you may enable this option manually. !

!
!
--with-long-double-128
!

Specify if long double type should be 128-bit by default on selected GNU/Linux architectures. If using --without-long-double-128, ! long double will be by default 64-bit, the same as double type. When neither of these configure options are used, the default will be 128-bit long double when built against GNU C Library 2.4 and later, 64-bit long double otherwise. !

!
!
--enable-fdpic
!

On SH Linux systems, generate ELF FDPIC code. !

!
!
--with-gmp=pathname
!
--with-gmp-include=pathname
!
--with-gmp-lib=pathname
!
--with-mpfr=pathname
!
--with-mpfr-include=pathname
!
--with-mpfr-lib=pathname
!
--with-mpc=pathname
!
--with-mpc-include=pathname
!
--with-mpc-lib=pathname
!

If you want to build GCC but do not have the GMP library, the MPFR library and/or the MPC library installed in a standard location and do not have their sources present in the GCC source tree then you can explicitly specify the directory where they are installed ! (‘--with-gmp=gmpinstalldir’, ! ‘--with-mpfr=mpfrinstalldir’, ! ‘--with-mpc=mpcinstalldir’). The ! --with-gmp=gmpinstalldir option is shorthand for ! --with-gmp-lib=gmpinstalldir/lib and ! --with-gmp-include=gmpinstalldir/include. Likewise the ! --with-mpfr=mpfrinstalldir option is shorthand for ! --with-mpfr-lib=mpfrinstalldir/lib and ! --with-mpfr-include=mpfrinstalldir/include, also the ! --with-mpc=mpcinstalldir option is shorthand for ! --with-mpc-lib=mpcinstalldir/lib and ! --with-mpc-include=mpcinstalldir/include. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. You might also need to ensure the shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path ! variable (LD_LIBRARY_PATH on GNU/Linux and Solaris systems). !

!

These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. !

!
!
--with-isl=pathname
!
--with-isl-include=pathname
!
--with-isl-lib=pathname
!

If you do not have the isl library installed in a standard location and you want to build GCC, you can explicitly specify the directory where it is ! installed (‘--with-isl=islinstalldir’). The ! --with-isl=islinstalldir option is shorthand for ! --with-isl-lib=islinstalldir/lib and ! --with-isl-include=islinstalldir/include. If this shorthand assumption is not correct, you can use the explicit include and lib options directly. !

!

These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. !

!
!
--with-stage1-ldflags=flags
!

This option may be used to set linker flags to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with ! --disable-bootstrap. If --with-stage1-libs is not set to a ! value, then the default is ‘-static-libstdc++ -static-libgcc’, if supported. !

!
!
--with-stage1-libs=libs
!

This option may be used to set libraries to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with ! --disable-bootstrap. !

!
!
--with-boot-ldflags=flags
!

This option may be used to set linker flags to be used when linking stage 2 and later when bootstrapping GCC. If –with-boot-libs is not is set to a value, then the default is ! ‘-static-libstdc++ -static-libgcc’. !

!
!
--with-boot-libs=libs
!

This option may be used to set libraries to be used when linking stage 2 and later when bootstrapping GCC. !

!
!
--with-debug-prefix-map=map
!

Convert source directory names using -fdebug-prefix-map when building runtime libraries. ‘map’ is a space-separated ! list of maps of the form ‘old=new’. !

!
!
--enable-linker-build-id
!

Tells GCC to pass --build-id option to the linker for all final ! links (links performed without the -r or --relocatable option), if the linker supports it. If you specify ! --enable-linker-build-id, but your linker does not ! support --build-id option, a warning is issued and the ! --enable-linker-build-id option is ignored. The default is off. !

!
!
--with-linker-hash-style=choice
!

Tells GCC to pass --hash-style=choice option to the linker for all final links. choice can be one of ! ‘sysv’, ‘gnu’, and ‘both’ where ‘sysv’ is the default. !

!
!
--enable-gnu-unique-object
!
--disable-gnu-unique-object
!

Tells GCC to use the gnu_unique_object relocation for C++ template static data members and inline function local statics. Enabled by default for a toolchain with an assembler that accepts it and GLIBC 2.11 or above, otherwise disabled. !

!
!
--with-diagnostics-color=choice
!

Tells GCC to use choice as the default for -fdiagnostics-color= option (if not used explicitly on the command line). choice ! can be one of ‘never’, ‘auto’, ‘always’, and ‘auto-if-env’ ! where ‘auto’ is the default. ‘auto-if-env’ means that ! -fdiagnostics-color=auto will be the default if GCC_COLORS is present and non-empty in the environment, and ! -fdiagnostics-color=never otherwise. !

!
!
--enable-lto
!
--disable-lto
!

Enable support for link-time optimization (LTO). This is enabled by ! default, and may be disabled using --disable-lto. !

!
!
--enable-linker-plugin-configure-flags=FLAGS
!
--enable-linker-plugin-flags=FLAGS
!

By default, linker plugins (such as the LTO plugin) are built for the host system architecture. For the case that the linker has a different (but run-time compatible) architecture, these flags can be specified to build plugins that are compatible to the linker. For example, if you are building GCC for a 64-bit x86_64 ! (‘x86_64-unknown-linux-gnu’) host system, but have a 32-bit x86 ! GNU/Linux (‘i686-pc-linux-gnu’) linker executable (which is executable on the former system), you can configure GCC as follows for getting compatible linker plugins: -

-
- 
% srcdir/configure \
-     --host=x86_64-unknown-linux-gnu \
-     --enable-linker-plugin-configure-flags=--host=i686-pc-linux-gnu \
-     --enable-linker-plugin-flags='CC=gcc\ -m32\ -Wl,-rpath,[...]/i686-pc-linux-gnu/lib'
-
!
!
--with-plugin-ld=pathname
!

Enable an alternate linker to be used at link-time optimization (LTO) ! link time when -fuse-linker-plugin is enabled. This linker should have plugin support such as gold starting with ! version 2.20 or GNU ld starting with version 2.21. ! See -fuse-linker-plugin for details. !

!
!
--enable-canonical-system-headers
!
--disable-canonical-system-headers
!

Enable system header path canonicalization for libcpp. This can produce shorter header file paths in diagnostics and dependency output files, but these changed header paths may conflict with some compilation environments. Enabled by default, and may be disabled using ! --disable-canonical-system-headers. !

!
!
--with-glibc-version=major.minor
!

Tell GCC that when the GNU C Library (glibc) is used on the target it will be version major.minor or later. Normally this can ! be detected from the C library’s header files, but this option may be needed when bootstrapping a cross toolchain without the header files available for building the initial bootstrap compiler. !

!

If GCC is configured with some multilibs that use glibc and some that ! do not, this option applies only to the multilibs that use glibc. However, such configurations may not work well as not all the relevant configuration in GCC is on a per-multilib basis. !

!
!
--enable-as-accelerator-for=target
!

Build as offload target compiler. Specify offload host triple by target. !

!
!
--enable-offload-targets=target1[=path1],…,targetN[=pathN]
!

Enable offloading to targets target1, …, targetN. Offload compilers are expected to be already installed. Default search path for them is exec-prefix, but it can be changed by ! specifying paths path1, …, pathN. !

!
! 
% srcdir/configure \
!     --enable-offload-target=i686-unknown-linux-gnu=/path/to/i686/compiler,x86_64-pc-linux-gnu
!
!

If ‘hsa’ is specified as one of the targets, the compiler will be built with support for HSA GPU accelerators. Because the same compiler will emit the accelerator code, no path should be specified. !

!
!
--with-hsa-runtime=pathname
!
--with-hsa-runtime-include=pathname
!
--with-hsa-runtime-lib=pathname
!
!

If you configure GCC with HSA offloading but do not have the HSA run-time library installed in a standard location then you can explicitly specify the directory where they are installed. The ! --with-hsa-runtime=hsainstalldir option is a shorthand for ! --with-hsa-runtime-lib=hsainstalldir/lib and ! --with-hsa-runtime-include=hsainstalldir/include. !

!
!
--with-hsa-kmt-lib=pathname
!
!

If you configure GCC with HSA offloading but do not have the HSA KMT library installed in a standard location then you can ! explicitly specify the directory where it resides. !

! !

Cross-Compiler-Specific Options

The following options only apply to building cross compilers. !

!
!
--with-sysroot
!
--with-sysroot=dir
!

Tells GCC to consider dir as the root of a tree that contains ! (a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be searched for in there. More specifically, this acts as if ! --sysroot=dir was added to the default options of the built compiler. The specified directory is not copied into the ! install tree, unlike the options --with-headers and ! --with-libs that this option obsoletes. The default value, ! in case --with-sysroot is not given an argument, is ! ${gcc_tooldir}/sys-root. If the specified directory is a ! subdirectory of ${exec_prefix}, then it will be found relative to the GCC binaries if the installation tree is moved. !

!

This option affects the system root for the compiler used to build target libraries (which runs on the build system) and the compiler newly installed with make install; it does not affect the compiler which is used to build GCC itself. !

!

If you specify the --with-native-system-header-dir=dirname option then the compiler will search that directory within dirname for ! native system headers rather than the default /usr/include. !

!
!
--with-build-sysroot
!
--with-build-sysroot=dir
!

Tells GCC to consider dir as the system root (see ! --with-sysroot) while building target libraries, instead of ! the directory specified with --with-sysroot. This option is ! only useful when you are already using --with-sysroot. You ! can use --with-build-sysroot when you are configuring with ! --prefix set to a directory that is different from the one in which you are installing GCC and your target libraries. !

!

This option affects the system root for the compiler used to build target libraries (which runs on the build system); it does not affect the compiler which is used to build GCC itself. !

!

If you specify the --with-native-system-header-dir=dirname option then the compiler will search that directory within dirname for ! native system headers rather than the default /usr/include. !

!
!
--with-headers
!
--with-headers=dir
!

Deprecated in favor of --with-sysroot. ! Specifies that target headers are available when building a cross compiler. The dir argument specifies a directory which has the target include ! files. These include files will be copied into the gcc install ! directory. This option with the dir argument is required when ! building a cross compiler, if prefix/target/sys-include ! doesn’t pre-exist. If prefix/target/sys-include does ! pre-exist, the dir argument may be omitted. fixincludes will be run on these files to make them compatible with GCC. !

!
!
--without-headers
!

Tells GCC not use any target headers from a libc when building a cross compiler. When crossing to GNU/Linux, you need the headers so GCC can build the exception handling for libgcc. !

!
!
--with-libs
!
--with-libs="dir1 dir2 … dirN"
!

Deprecated in favor of --with-sysroot. Specifies a list of directories which contain the target runtime ! libraries. These libraries will be copied into the gcc install directory. If the directory list is omitted, this option has no effect. !

!
!
--with-newlib
!

Specifies that ‘newlib’ is being used as the target C library. This causes __eprintf to be ! omitted from libgcc.a on the assumption that it will be provided by ! ‘newlib’. !

!
!
--with-avrlibc
!

Specifies that ‘AVR-Libc’ is being used as the target C library. This causes float support ! functions like __addsf3 to be omitted from libgcc.a on ! the assumption that it will be provided by libm.a. For more ! technical details, cf. PR54461. This option is only supported for the AVR target. It is not supported for RTEMS configurations, which currently use newlib. The option is supported since version 4.7.2 and is the default in 4.8.0 and newer. !

!
!
--with-nds32-lib=library
!

Specifies that library setting is used for building libgcc.a. ! Currently, the valid library is ‘newlib’ or ‘mculib’. This option is only supported for the NDS32 target. !

!
!
--with-build-time-tools=dir
!

Specifies where to find the set of target tools (assembler, linker, etc.) that will be used while building GCC itself. This option can be useful if the directory layouts are different between the system you are building GCC on, and the system where you will deploy it. !

!

For example, on an ‘ia64-hp-hpux’ system, you may have the GNU ! assembler and linker in /usr/bin, and the native tools in a different path, and build a toolchain that expects to find the ! native tools in /usr/bin. !

!

When you use this option, you should ensure that dir includes ! ar, as, ld, nm, ! ranlib and strip if necessary, and possibly ! objdump. Otherwise, GCC may use an inconsistent set of ! tools. !

! !

Overriding configure test results

Sometimes, it might be necessary to override the result of some ! configure test, for example in order to ease porting to a new ! system or work around a bug in a test. The toplevel configure script provides three variables for this: !

!
!
build_configargs
!
!

The contents of this variable is passed to all build configure scripts. !

!
!
host_configargs
!
!

The contents of this variable is passed to all host configure scripts. !

!
!
target_configargs
!
!

The contents of this variable is passed to all target configure scripts. -

-
-
!

In order to avoid shell and make quoting issues for complex ! overrides, you can pass a setting for CONFIG_SITE and set variables in the site file. !

! !

Java-Specific Options

The following option applies to the build of the Java front end. !

!
!
--disable-libgcj
!

Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend ! to use GCJ with some other run-time, or you’re going to install it separately, or it just happens not to build on your particular machine. In general, if the Java front end is enabled, the GCJ ! libraries will be enabled too, unless they’re known to not work on ! the target platform. If GCJ is enabled but ‘libgcj’ isn’t built, you may need to port it; in this case, before modifying the top-level ! configure.ac so that ‘libgcj’ is enabled by default on this platform, ! you may use --enable-libgcj to override the default. !

!
!
!

The following options apply to building ‘libgcj’. !

! !

General Options

!
!
--enable-java-maintainer-mode
!

By default the ‘libjava’ build will not attempt to compile the ! .java source files to .class. Instead, it will use the ! .class files from the source tree. If you use this option you ! must have executables named ecj1 and gjavah in your path for use by the build. You must use this option if you intend to ! modify any .java files in libjava. !

!
!
--with-java-home=dirname
!

This ‘libjava’ option overrides the default value of the ! ‘java.home’ system property. It is also used to set ! ‘sun.boot.class.path’ to dirname/lib/rt.jar. By ! default ‘java.home’ is set to prefix and ! ‘sun.boot.class.path’ to ! datadir/java/libgcj-version.jar. !

!
!
--with-ecj-jar=filename
!

This option can be used to specify the location of an external jar file containing the Eclipse Java compiler. A specially modified ! version of this compiler is used by gcj to parse ! .java source files. If this option is given, the ! ‘libjava’ build will create and install an ecj1 executable which uses this jar file at runtime. !

!

If this option is not given, but an ecj.jar file is found in ! the topmost source tree at configure time, then the ‘libgcj’ ! build will create and install ecj1, and will also install the ! discovered ecj.jar into a suitable place in the install tree. !

!

If ecj1 is not installed, then the user will have to supply one ! on his path in order for gcj to properly parse .java source files. A suitable jar is available from ftp://sourceware.org/pub/java/. !

!
!
--disable-getenv-properties
!

Don’t set system properties from GCJ_PROPERTIES. !

!
!
--enable-hash-synchronization
!

Use a global hash table for monitor locks. Ordinarily, ! ‘libgcj’’s ‘configure’ script automatically makes the correct choice for this option for your platform. Only use this if you know you need the library to be configured differently. !

!
!
--enable-interpreter
!

Enable the Java interpreter. The interpreter is automatically enabled by default on all platforms that support it. This option is really only useful if you want to disable the interpreter ! (using --disable-interpreter). !

!
!
--disable-java-net
!

Disable java.net. This disables the native part of java.net only, using non-functional stubs for native method implementations. !

!
!
--disable-jvmpi
!

Disable JVMPI support. !

!
!
--disable-libgcj-bc
!

Disable BC ABI compilation of certain parts of libgcj. By default, ! some portions of libgcj are compiled with -findirect-dispatch ! and -fno-indirect-classes, allowing them to be overridden at run-time. !

!

If --disable-libgcj-bc is specified, libgcj is built without these options. This allows the compile-time linker to resolve dependencies when statically linking to libgcj. However it makes it impossible to override the affected portions of libgcj at run-time. !

!
!
--enable-reduced-reflection
!

Build most of libgcj with -freduced-reflection. This reduces the size of libgcj at the expense of not being able to do accurate reflection on the classes it contains. This option is safe if you know that code using libgcj will never use reflection on the standard runtime classes in libgcj (including using serialization, RMI or CORBA). !

!
!
--with-ecos
!

Enable runtime eCos target support. !

!
!
--without-libffi
!

Don’t use ‘libffi’. This will disable the interpreter and JNI ! support as well, as these require ‘libffi’ to work. !

!
!
--enable-libgcj-debug
!

Enable runtime debugging code. !

!
!
--enable-libgcj-multifile
!

If specified, causes all .java source files to be ! compiled into .class files in one invocation of ! ‘gcj’. This can speed up build time, but is more resource-intensive. If this option is unspecified or ! disabled, ‘gcj’ is invoked once for each .java ! file to compile into a .class file. !

!
!
--with-libiconv-prefix=DIR
!

Search for libiconv in DIR/include and DIR/lib. !

!
!
--enable-sjlj-exceptions
!

Force use of the setjmp/longjmp-based scheme for exceptions. ! ‘configure’ ordinarily picks the correct value based on the platform. ! Only use this option if you are sure you need a different setting. !

!
!
--with-system-zlib
!

Use installed ‘zlib’ rather than that included with GCC. !

!
!
--with-win32-nlsapi=ansi, unicows or unicode
!

Indicates how MinGW ‘libgcj’ translates between UNICODE characters and the Win32 API. !

!
!
--enable-java-home
!

If enabled, this creates a JPackage compatible SDK environment during install. Note that if –enable-java-home is used, –with-arch-directory=ARCH must also be specified. !

!
!
--with-arch-directory=ARCH
!

Specifies the name to use for the jre/lib/ARCH directory in the SDK environment created when –enable-java-home is passed. Typical names for this directory include i386, amd64, ia64, etc. !

!
!
--with-os-directory=DIR
!

Specifies the OS directory for the SDK include directory. This is set to auto ! detect, and is typically ’linux’. !

!
!
--with-origin-name=NAME
!

Specifies the JPackage origin name. This defaults to the ’gcj’ in java-1.5.0-gcj. !

!
!
--with-arch-suffix=SUFFIX
!

Specifies the suffix for the sdk directory. Defaults to the empty string. ! Examples include ’.x86_64’ in ’java-1.5.0-gcj-1.5.0.0.x86_64’. !

!
!
--with-jvm-root-dir=DIR
!

Specifies where to install the SDK. Default is $(prefix)/lib/jvm. !

!
!
--with-jvm-jar-dir=DIR
!

Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. !

!
!
--with-python-dir=DIR
!

Specifies where to install the Python modules used for aot-compile. DIR should not include the prefix used in installation. For example, if the Python modules are to be installed in /usr/lib/python2.5/site-packages, then –with-python-dir=/lib/python2.5/site-packages should be passed. If this is not specified, then the Python modules are installed in $(prefix)/share/python. !

!
!
--enable-aot-compile-rpm
!

Adds aot-compile-rpm to the list of installed scripts. !

!
!
--enable-browser-plugin
!

Build the gcjwebplugin web browser plugin. !

!
!
--enable-static-libjava
!

Build static libraries in libjava. The default is to only build shared libraries. !

!
!
ansi
!

Use the single-byte char and the Win32 A functions natively, translating to and from UNICODE when using these functions. If unspecified, this is the default. -

-
-
unicows
-

Use the WCHAR and Win32 W functions natively. Adds - -lunicows to libgcj.spec to link with ‘libunicows’. - unicows.dll needs to be deployed on Microsoft Windows 9X machines - running built executables. libunicows.a, an open-source - import library around Microsoft’s unicows.dll, is obtained from - http://libunicows.sourceforge.net/, which also gives details - on getting unicows.dll from Microsoft. -

-
-
unicode
-

Use the WCHAR and Win32 W functions natively. Does not - add -lunicows to libgcj.spec. The built executables will - only run on Microsoft Windows NT and above. -

-
-
-
! !

AWT-Specific Options

!
!
--with-x
!

Use the X Window System. !

!
!
--enable-java-awt=PEER(S)
!

Specifies the AWT peer library or libraries to build alongside ! ‘libgcj’. If this option is unspecified or disabled, AWT ! will be non-functional. Current valid values are gtk and ! xlib. Multiple libraries should be separated by a ! comma (i.e. --enable-java-awt=gtk,xlib). !

!
!
--enable-gtk-cairo
!

Build the cairo Graphics2D implementation on GTK. !

!
!
--enable-java-gc=TYPE
!

Choose garbage collector. Defaults to boehm if unspecified. !

!
!
--disable-gtktest
!

Do not try to compile and run a test GTK+ program. !

!
!
--disable-glibtest
!

Do not try to compile and run a test GLIB program. !

!
!
--with-libart-prefix=PFX
!

Prefix where libart is installed (optional). !

!
!
--with-libart-exec-prefix=PFX
!

Exec prefix where libart is installed (optional). !

!
!
--disable-libarttest
!

Do not try to compile and run a test libart program. !

!
!
!

!

Return to the GCC Installation page !

- - --- 497,1537 ---- -mfpu=neon, -mfpu=vfpv4-d16, -mfpu=neon-vfpv4 or -mfpu=neon-fp-armv8 depending on architecture) and floating-point ABI (-mfloat-abi=softfp or -mfloat-abi=hard). ! !
sh*-*-*
list is a comma separated list of CPU names. These must be of the form sh* or m* (in which case they match the compiler option for that processor). The list should not contain any endian options - ! these are handled by --with-endian. ! !

If list is empty, then there will be no multilibs for extra processors. The multilib for the secondary endian remains enabled. ! !

As a special case, if an entry in the list starts with a ! ! (exclamation point), then it is added to the list of excluded multilibs. ! Entries of this sort should be compatible with ‘MULTILIB_EXCLUDES’ (once the leading ! has been stripped). ! !

If --with-multilib-list is not given, then a default set of ! multilibs is selected based on the value of --target. This is usually the complete set of libraries, but some targets imply a more specialized subset. !

Example 1: to configure a compiler for SH4A only, but supporting both ! endians, with little endian being the default: ! 

               --with-cpu=sh4a --with-endian=little,big --with-multilib-list=
!
!

Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with only little endian SH4AL: ! 

               --with-cpu=sh4a --with-endian=little,big \
!                --with-multilib-list=sh4al,!mb/m4al
!
!
x86-64-*-linux*
list is a comma separated list of m32, m64 and mx32 to enable 32-bit, 64-bit and x32 run-time libraries, respectively. If list is empty, then there will be no multilibs and only the default run-time library will be enabled. ! !

If --with-multilib-list is not given, then only 32-bit and ! 64-bit run-time libraries will be enabled.

!
--with-endian=endians
Specify what endians to use. Currently only implemented for sh*-*-*. ! !

endians may be one of the following: !

!
big
Use big endian exclusively. !
little
Use little endian exclusively. !
big,little
Use big endian by default. Provide a multilib for little endian. !
little,big
Use little endian by default. Provide a multilib for big endian.
!
--enable-threads
Specify that the target supports threads. This affects the Objective-C compiler and runtime ! library, and exception handling for other languages like C++ and Java. On some systems, this is the default. ! !

In general, the best (and, in many cases, the only known) threading model available will be configured for use. Beware that on some systems, GCC has not been taught what threading models are generally ! available for the system. In this case, --enable-threads is an ! alias for --enable-threads=single. ! !

--disable-threads
Specify that threading support should be disabled for the system. ! This is an alias for --enable-threads=single. ! !
--enable-threads=lib
Specify that lib is the thread support library. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. The possibilities for lib are: ! !
!
aix
AIX thread support. !
dce
DCE thread support. !
lynx
LynxOS thread support. !
mipssde
MIPS SDE thread support. !
no
This is an alias for ‘single’. !
posix
Generic POSIX/Unix98 thread support. !
rtems
RTEMS thread support. !
single
Disable thread support, should work for all platforms. !
tpf
TPF thread support. !
vxworks
VxWorks thread support. !
win32
Microsoft Win32 API thread support.
!
--enable-tls
Specify that the target supports TLS (Thread Local Storage). Usually configure can correctly determine if TLS is supported. In cases where it guesses incorrectly, TLS can be explicitly enabled or disabled with ! --enable-tls or --disable-tls. This can happen if the assembler supports TLS but the C library does not, or if the assumptions made by the configure test are incorrect. ! !
--disable-tls
Specify that the target does not support TLS. ! This is an alias for --enable-tls=no. ! !
--with-cpu=cpu
--with-cpu-32=cpu
--with-cpu-64=cpu
Specify which cpu variant the compiler should generate code for by default. ! cpu will be used as the default value of the -mcpu= switch. This option is only supported on some targets, including ARC, ARM, i386, M68k, ! PowerPC, and SPARC. It is mandatory for ARC. The --with-cpu-32 and ! --with-cpu-64 options specify separate default CPUs for 32-bit and 64-bit modes; these options are only supported for i386, x86-64, PowerPC, and SPARC. ! !
--with-schedule=cpu
--with-arch=cpu
--with-arch-32=cpu
--with-arch-64=cpu
--with-tune=cpu
--with-tune-32=cpu
--with-tune-64=cpu
--with-abi=abi
--with-fpu=type
--with-float=type
These configure options provide default values for the -mschedule=, ! -march=, -mtune=, -mabi=, and -mfpu= ! options and for -mhard-float or -msoft-float. As with ! --with-cpu, which switches will be accepted and acceptable values of the arguments depend on the target. ! !
--with-mode=mode
Specify if the compiler should default to -marm or -mthumb. This option is only supported on ARM targets. ! !
--with-stack-offset=num
This option sets the default for the -mstack-offset=num option, and will thus generally also control the setting of this option for libraries. This option is only supported on Epiphany targets. ! !
--with-fpmath=isa
This options sets -mfpmath=sse by default and specifies the default ! ISA for floating-point arithmetics. You can select either ‘sse’ which ! enables -msse2 or ‘avx’ which enables -mavx by default. This option is only supported on i386 and x86-64 targets. ! !
--with-fp-32=mode
On MIPS targets, set the default value for the -mfp option when using the o32 ABI. The possibilities for mode are: !
!
32
Use the o32 FP32 ABI extension, as with the -mfp32 command-line ! option. !
xx
Use the o32 FPXX ABI extension, as with the -mfpxx command-line ! option. !
64
Use the o32 FP64 ABI extension, as with the -mfp64 command-line ! option.
! In the absence of this configuration option the default is to use the o32 FP32 ABI extension. ! !
--with-odd-spreg-32
On MIPS targets, set the -modd-spreg option by default when using the o32 ABI. ! !
--without-odd-spreg-32
On MIPS targets, set the -mno-odd-spreg option by default when using the o32 ABI. This is normally used in conjunction with ! --with-fp-32=64 in order to target the o32 FP64A ABI extension. ! !
--with-nan=encoding
On MIPS targets, set the default encoding convention to use for the special not-a-number (NaN) IEEE 754 floating-point data. The possibilities for encoding are: !
!
legacy
Use the legacy encoding, as with the -mnan=legacy command-line ! option. !
2008
Use the 754-2008 encoding, as with the -mnan=2008 command-line ! option.
! To use this configuration option you must have an assembler version ! installed that supports the -mnan= command-line option too. In the absence of this configuration option the default convention is ! the legacy encoding, as when neither of the -mnan=2008 and ! -mnan=legacy command-line options has been used. ! !
--with-divide=type
Specify how the compiler should generate code for checking for ! division by zero. This option is only supported on the MIPS target. The possibilities for type are: !
!
traps
Division by zero checks use conditional traps (this is the default on ! systems that support conditional traps). !
breaks
Division by zero checks use the break instruction.
! ! !
--with-llsc
On MIPS targets, make -mllsc the default when no ! -mno-llsc option is passed. This is the default for Linux-based targets, as the kernel will emulate them if the ISA does not provide them. ! !
--without-llsc
On MIPS targets, make -mno-llsc the default when no ! -mllsc option is passed. ! !
--with-synci
On MIPS targets, make -msynci the default when no ! -mno-synci option is passed. ! !
--without-synci
On MIPS targets, make -mno-synci the default when no ! -msynci option is passed. This is the default. ! !
--with-mips-plt
On MIPS targets, make use of copy relocations and PLTs. These features are extensions to the traditional SVR4-based MIPS ABIs and require support from GNU binutils and the runtime C library. ! !
--enable-__cxa_atexit
Define if you want to use __cxa_atexit, rather than atexit, to ! register C++ destructors for local statics and global objects. This is essential for fully standards-compliant handling of destructors, but requires __cxa_atexit in libc. This option is currently only available on systems with GNU libc. When enabled, this will cause ! -fuse-cxa-atexit to be passed by default. ! !
--enable-gnu-indirect-function
Define if you want to enable the ifunc attribute. This option is currently only available on systems with GNU libc on certain targets. ! !
--enable-target-optspace
Specify that target ! libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. ! !
--with-cpp-install-dir=dirname
Specify that the user visible cpp program should be installed ! in prefix/dirname/cpp, in addition to bindir. ! !
--enable-comdat
Enable COMDAT group support. This is primarily used to override the automatically detected value. ! !
--enable-initfini-array
Force the use of sections .init_array and .fini_array (instead of .init and .fini) for constructors and ! destructors. Option --disable-initfini-array has the opposite effect. If neither option is specified, the configure script will try to guess whether the .init_array and .fini_array sections are supported and, if they are, use them. ! !
--enable-link-mutex
When building GCC, use a mutex to avoid linking the compilers for multiple languages at the same time, to avoid thrashing on build systems with limited free memory. The default is not to use such a mutex. ! !
--enable-maintainer-mode
The build rules that regenerate the Autoconf and Automake output files as ! well as the GCC master message catalog gcc.pot are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the ! catalog, configuring with --enable-maintainer-mode will enable this. Note that you need a recent version of the gettext tools to do so. ! !
--disable-bootstrap
For a native build, the default configuration is to perform ! a 3-stage bootstrap of the compiler when ‘make’ is invoked, testing that GCC can compile itself correctly. If you want to disable ! this process, you can configure with --disable-bootstrap. ! !
--enable-bootstrap
In special cases, you may want to perform a 3-stage build ! even if the target and host triplets are different. This is possible when the host can run code compiled for ! the target (e.g. host is i686-linux, target is i486-linux). Starting from GCC 4.2, to do this you have to configure explicitly ! with --enable-bootstrap. ! !
--enable-generated-files-in-srcdir
Neither the .c and .h files that are generated from Bison and flex nor the info manuals and man pages that are built from the .texi files are present in the SVN development tree. When building GCC from that development tree, or from one of our snapshots, those generated files are placed in your build directory, which allows for the source to be in a readonly directory. ! !

If you configure with --enable-generated-files-in-srcdir then those generated files will go into the source directory. This is mainly intended for generating release or prerelease tarballs of the GCC sources, since it is not a requirement that the users of source releases to have flex, Bison, or makeinfo. ! !

--enable-version-specific-runtime-libs
Specify that runtime libraries should be installed in the compiler specific ! subdirectory (libdir/gcc) rather than the usual places. In ! addition, ‘libstdc++’'s include files will be installed into libdir unless you overruled it by using ! --with-gxx-include-dir=dirname. Using this option is particularly useful if you intend to use several versions of GCC in ! parallel. This is currently supported by ‘libgfortran’, ! ‘libjava’, ‘libstdc++’, and ‘libobjc’. ! !
--with-aix-soname=‘aix’, ‘svr4’ or ‘both’
Traditional AIX shared library versioning (versioned Shared Object files as members of unversioned Archive Library files named ! ‘lib.a’) causes numerous headaches for package managers. However, Import Files as members of Archive Library files allow for filename-based versioning of shared libraries as seen on Linux/SVR4, ! where this is called the "SONAME". But as they prevent static linking, Import Files may be used with Runtime Linking only, where the ! linker does search for ‘libNAME.so’ before ‘libNAME.a’ library ! filenames with the ‘-lNAME’ linker flag. ! !

For detailed information please refer to the AIX ! ld Command reference. ! !

As long as shared library creation is enabled, upon: !

!
--with-aix-soname=aix
--with-aix-soname=both
A (traditional AIX) Shared Archive Library file is created: !
    !
  • using the ‘libNAME.a’ filename scheme !
  • with the Shared Object file as archive member named ! ‘libNAME.so.V’ (except for ‘libgcc_s’, where the Shared ! Object file is named ‘shr.o’ for backwards compatibility), which !
      !
    • is used for runtime loading from inside the ‘libNAME.a’ file !
    • is used for dynamic loading via ! dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER) !
    • is used for shared linking !
    • is used for static linking, so no separate Static Archive Library file is needed !
    !
!
--with-aix-soname=both
--with-aix-soname=svr4
A (second) Shared Archive Library file is created: !
    !
  • using the ‘libNAME.so.V’ filename scheme !
  • with the Shared Object file as archive member named ! ‘shr.o’, which !
      !
    • is created with the -G linker flag !
    • has the F_LOADONLY flag set !
    • is used for runtime loading from inside the ‘libNAME.so.V’ file !
    • is used for dynamic loading via dlopen("libNAME.so.V(shr.o)", RTLD_MEMBER) !
    !
  • with the Import File as archive member named ‘shr.imp’, which !
      !
    • refers to ‘libNAME.so.V(shr.o)’ as the "SONAME", to be recorded in the Loader Section of subsequent binaries !
    • indicates whether ‘libNAME.so.V(shr.o)’ is 32 or 64 bit !
    • lists all the public symbols exported by ‘lib.so.V(shr.o)’, ! eventually decorated with the ‘weak’ Keyword !
    • is necessary for shared linking against ‘lib.so.V(shr.o)’ !
    !
! A symbolic link using the ‘libNAME.so’ filename scheme is created: !
    !
  • pointing to the ‘libNAME.so.V’ Shared Archive Library file !
  • to permit the ld Command to find ‘lib.so.V(shr.imp)’ via ! the ‘-lNAME’ argument (requires Runtime Linking to be enabled) !
  • to permit dynamic loading of ‘lib.so.V(shr.o)’ without the need ! to specify the version number via dlopen("libNAME.so(shr.o)", RTLD_MEMBER) !
!
!

As long as static library creation is enabled, upon: !

!
--with-aix-soname=svr4
A Static Archive Library is created: !
    !
  • using the ‘libNAME.a’ filename scheme !
  • with all the Static Object files as archive members, which !
      !
    • are used for static linking !
    !
!
!

While the aix-soname=‘svr4’ option does not create Shared Object files as members of unversioned Archive Library files any more, package managers still are responsible to transfer Shared Object files found as member of a previously installed unversioned Archive Library file into the newly installed Archive Library file with the same filename. ! !

WARNING: Creating Shared Object files with Runtime Linking enabled may bloat the TOC, eventually leading to TOC overflow errors, ! requiring the use of either the -Wl,-bbigtoc linker flag (seen to break with the GDB debugger) or some of the TOC-related compiler flags, see “RS/6000 and PowerPC Options” in the main manual. ! !

--with-aix-soname is currently supported by ‘libgcc_s’ only, so this option is still experimental and not for normal use yet. ! !

Default is the traditional behavior --with-aix-soname=‘aix’. ! !

--enable-languages=lang1,lang2,...
Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for langN you can issue the following command in the ! gcc directory of your GCC source tree:
! 
          grep ^language= */config-lang.in
!
!

Currently, you can use any of the following: all, ada, c, c++, fortran, ! go, java, jit, lto, objc, obj-c++. ! Building the Ada compiler has special requirements, see below. If you do not pass this flag, or specify the option all, then all ! default languages available in the gcc sub-tree will be configured. Ada, Go, Jit, and Objective-C++ are not default languages. LTO is not a ! default language, but is built by default because --enable-lto is enabled by default. The other languages are default languages. ! !

--enable-stage1-languages=lang1,lang2,...
Specify that a particular subset of compilers and their runtime libraries should be built with the system C compiler during stage 1 of the bootstrap process, rather than only in later stages with the bootstrapped C compiler. The list of valid values is the same as for ! --enable-languages, and the option all will select all ! of the languages enabled by --enable-languages. This option is primarily useful for GCC development; for instance, when a development version of the compiler cannot bootstrap due to compiler bugs, or when one is debugging front ends other than the C front end. When this option is used, one can then build the target libraries for the ! specified languages with the stage-1 compiler by using make ! stage1-bubble all-target, or run the testsuite on the stage-1 compiler ! for the specified languages using make stage1-start check-gcc. ! !
--disable-libada
Specify that the run-time libraries and tools used by GNAT should not be built. This can be useful for debugging, or for compatibility with previous Ada build procedures, when it was required to explicitly ! do a ‘make -C gcc gnatlib_and_tools’. ! !
--disable-libsanitizer
Specify that the run-time libraries for the various sanitizers should not be built. ! !
--disable-libssp
Specify that the run-time libraries for stack smashing protection should not be built. ! !
--disable-libquadmath
Specify that the GCC quad-precision math library should not be built. On some systems, the library is required to be linkable when building ! the Fortran front end, unless --disable-libquadmath-support is used. ! !
--disable-libquadmath-support
Specify that the Fortran front end and libgfortran do not add support for libquadmath on systems supporting it. ! !
--disable-libgomp
Specify that the GNU Offloading and Multi Processing Runtime Library should not be built. ! !
--disable-libvtv
Specify that the run-time libraries used by vtable verification should not be built. ! !
--with-dwarf2
Specify that the compiler should use DWARF 2 debugging information as the default. ! !
--with-advance-toolchain=at
On 64-bit PowerPC Linux systems, configure the compiler to use the header files, library files, and the dynamic linker from the Advance Toolchain release at instead of the default versions that are provided by the Linux distribution. In general, this option is intended for the developers of GCC, and it is not intended for general use. ! !
--enable-targets=all
--enable-targets=target_list
Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers. These are compilers that are able to generate either 64-bit or 32-bit ! code. Typically, the corresponding 32-bit target, e.g. powerpc-linux for powerpc64-linux, only generates 32-bit code. This option enables the 32-bit target to be a bi-arch compiler, which is useful when you want a bi-arch compiler that defaults to 32-bit, and ! you are building a bi-arch or multi-arch binutils in a combined tree. On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), ! defaulted to o32. Currently, this option only affects sparc-linux, powerpc-linux, x86-linux, mips-linux and s390-linux. ! !
--enable-default-pie
Turn on -fPIE and -pie by default. ! !
--enable-secureplt
This option enables -msecure-plt by default for powerpc-linux. See “RS/6000 and PowerPC Options” in the main manual ! !
--enable-default-ssp
Turn on -fstack-protector-strong by default. ! !
--enable-cld
This option enables -mcld by default for 32-bit x86 targets. See “i386 and x86-64 Options” in the main manual ! !
--enable-win32-registry
--enable-win32-registry=key
--disable-win32-registry
The --enable-win32-registry option enables Microsoft Windows-hosted GCC to look up installations paths in the registry using the following key: ! 
          HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\key
!
!

key defaults to GCC version number, and can be overridden by the ! --enable-win32-registry=key option. Vendors and distributors who use custom installers are encouraged to provide a different key, perhaps one comprised of vendor name and GCC version number, to avoid conflict with existing installations. This feature is enabled ! by default, and can be disabled by --disable-win32-registry option. This option has no effect on the other hosts. ! !

--nfp
Specify that the machine does not have a floating point unit. This ! option only applies to ‘m68k-sun-sunosn’. On any other ! system, --nfp has no effect. ! !
--enable-werror
--disable-werror
--enable-werror=yes
--enable-werror=no
When you specify this option, it controls whether certain files in the ! compiler are built with -Werror in bootstrap stage2 and later. ! If you don't specify it, -Werror is turned on for the main development trunk. However it defaults to off for release branches and ! final releases. The specific files which get -Werror are controlled by the Makefiles. ! !
--enable-checking
--enable-checking=list
When you specify this option, the compiler is built to perform internal consistency checks of the requested complexity. This does not change the generated code, but adds error checking within the compiler. This will slow down the compiler and may only work properly if you are building ! the compiler with GCC. This is ‘yes’ by default when building ! from SVN or snapshots, but ‘release’ for releases. The default ! for building the stage1 compiler is ‘yes’. More control over the checks may be had by specifying list. The categories of ! checks available are ‘yes’ (most common checks ! ‘assert,misc,tree,gc,rtlflag,runtime’), ‘no’ (no checks at ! all), ‘all’ (all but ‘valgrind’), ‘release’ (cheapest ! checks ‘assert,runtime’) or ‘none’ (same as ‘no’). ! Individual checks can be enabled with these flags ‘assert’, ! ‘df’, ‘fold’, ‘gc’, ‘gcac’ ‘misc’, ‘rtl’, ! ‘rtlflag’, ‘runtime’, ‘tree’, and ‘valgrind’. ! !

The ‘valgrind’ check requires the external valgrind simulator, available from http://valgrind.org/. The ! ‘df’, ‘rtl’, ‘gcac’ and ‘valgrind’ checks are very expensive. ! To disable all checking, ‘--disable-checking’ or ! ‘--enable-checking=none’ must be explicitly requested. Disabling assertions will make the compiler and runtime slightly faster but increase the risk of undetected internal errors causing wrong code to be generated. ! !

--disable-stage1-checking
--enable-stage1-checking
--enable-stage1-checking=list
If no --enable-checking option is specified the stage1 ! compiler will be built with ‘yes’ checking enabled, otherwise the stage1 checking flags are the same as specified by ! --enable-checking. To build the stage1 compiler with ! different checking options use --enable-stage1-checking. ! The list of checking options is the same as for --enable-checking. If your system is too slow or too small to bootstrap a released compiler ! with checking for stage1 enabled, you can use ‘--disable-stage1-checking’ to disable checking for the stage1 compiler. ! !
--enable-coverage
--enable-coverage=level
With this option, the compiler is built to collect self coverage information, every time it is run. This is for internal development purposes, and only works when the compiler is being built with gcc. The level argument controls whether the compiler is built optimized or ! not, values are ‘opt’ and ‘noopt’. For coverage analysis you want to disable optimization, for performance analysis you want to enable optimization. When coverage is enabled, the default level is without optimization. ! !
--enable-gather-detailed-mem-stats
When this option is specified more detailed information on memory allocation is gathered. This information is printed when using ! -fmem-report. ! !
--enable-valgrind-annotations
Mark selected memory related operations in the compiler when run under valgrind to suppress false positives. ! !
--enable-nls
--disable-nls
The --enable-nls option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not doing a ! canadian cross build. The --disable-nls option disables NLS. ! !
--with-included-gettext
If NLS is enabled, the --with-included-gettext option causes the build ! procedure to prefer its copy of GNU gettext. ! !
--with-catgets
If NLS is enabled, and if the host lacks gettext but has the inferior catgets interface, the GCC build procedure normally ! ignores catgets and instead uses GCC's copy of the GNU ! gettext library. The --with-catgets option causes the ! build procedure to use the host's catgets in this situation. ! !
--with-libiconv-prefix=dir
Search for libiconv header files in dir/include and ! libiconv library files in dir/lib. ! !
--enable-obsolete
Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. ! !

All support for systems which have been obsoleted in one release of GCC is removed entirely in the next major release, unless someone steps forward to maintain the port. ! !

--enable-decimal-float
--enable-decimal-float=yes
--enable-decimal-float=no
--enable-decimal-float=bid
--enable-decimal-float=dpd
--disable-decimal-float
Enable (or disable) support for the C decimal floating point extension that is in the IEEE 754-2008 standard. This is enabled by default only on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also support it, but require the user to specifically enable it. You can optionally control which decimal floating point format is used (either ! ‘bid’ or ‘dpd’). The ‘bid’ (binary integer decimal) ! format is default on i386 and x86_64 systems, and the ‘dpd’ (densely packed decimal) format is default on PowerPC systems. ! !
--enable-fixed-point
--disable-fixed-point
Enable (or disable) support for C fixed-point arithmetic. This option is enabled by default for some targets (such as MIPS) which have hardware-support for fixed-point operations. On other targets, you may enable this option manually. ! !
--with-long-double-128
Specify if long double type should be 128-bit by default on selected GNU/Linux architectures. If using --without-long-double-128, ! long double will be by default 64-bit, the same as double type. When neither of these configure options are used, the default will be 128-bit long double when built against GNU C Library 2.4 and later, 64-bit long double otherwise. ! !
--enable-fdpic
On SH Linux systems, generate ELF FDPIC code. ! !
--with-gmp=pathname
--with-gmp-include=pathname
--with-gmp-lib=pathname
--with-mpfr=pathname
--with-mpfr-include=pathname
--with-mpfr-lib=pathname
--with-mpc=pathname
--with-mpc-include=pathname
--with-mpc-lib=pathname
If you want to build GCC but do not have the GMP library, the MPFR library and/or the MPC library installed in a standard location and do not have their sources present in the GCC source tree then you can explicitly specify the directory where they are installed ! (‘--with-gmp=gmpinstalldir’, ! ‘--with-mpfr=mpfrinstalldir’, ! ‘--with-mpc=mpcinstalldir’). The ! --with-gmp=gmpinstalldir option is shorthand for ! --with-gmp-lib=gmpinstalldir/lib and ! --with-gmp-include=gmpinstalldir/include. Likewise the ! --with-mpfr=mpfrinstalldir option is shorthand for ! --with-mpfr-lib=mpfrinstalldir/lib and ! --with-mpfr-include=mpfrinstalldir/include, also the ! --with-mpc=mpcinstalldir option is shorthand for ! --with-mpc-lib=mpcinstalldir/lib and ! --with-mpc-include=mpcinstalldir/include. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. You might also need to ensure the shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path ! variable (LD_LIBRARY_PATH on GNU/Linux and Solaris systems). ! !

These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. ! !

--with-isl=pathname
--with-isl-include=pathname
--with-isl-lib=pathname
If you do not have the isl library installed in a standard location and you want to build GCC, you can explicitly specify the directory where it is ! installed (‘--with-isl=islinstalldir’). The ! --with-isl=islinstalldir option is shorthand for ! --with-isl-lib=islinstalldir/lib and ! --with-isl-include=islinstalldir/include. If this shorthand assumption is not correct, you can use the explicit include and lib options directly. ! !

These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. ! !

--with-stage1-ldflags=flags
This option may be used to set linker flags to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with ! --disable-bootstrap. If --with-stage1-libs is not set to a ! value, then the default is ‘-static-libstdc++ -static-libgcc’, if supported. ! !
--with-stage1-libs=libs
This option may be used to set libraries to be used when linking stage 1 of GCC. These are also used when linking GCC if configured with ! --disable-bootstrap. ! !
--with-boot-ldflags=flags
This option may be used to set linker flags to be used when linking stage 2 and later when bootstrapping GCC. If –with-boot-libs is not is set to a value, then the default is ! ‘-static-libstdc++ -static-libgcc’. ! !
--with-boot-libs=libs
This option may be used to set libraries to be used when linking stage 2 and later when bootstrapping GCC. ! !
--with-debug-prefix-map=map
Convert source directory names using -fdebug-prefix-map when building runtime libraries. ‘map’ is a space-separated ! list of maps of the form ‘old=new’. ! !
--enable-linker-build-id
Tells GCC to pass --build-id option to the linker for all final ! links (links performed without the -r or --relocatable option), if the linker supports it. If you specify ! --enable-linker-build-id, but your linker does not ! support --build-id option, a warning is issued and the ! --enable-linker-build-id option is ignored. The default is off. ! !
--with-linker-hash-style=choice
Tells GCC to pass --hash-style=choice option to the linker for all final links. choice can be one of ! ‘sysv’, ‘gnu’, and ‘both’ where ‘sysv’ is the default. ! !
--enable-gnu-unique-object
--disable-gnu-unique-object
Tells GCC to use the gnu_unique_object relocation for C++ template static data members and inline function local statics. Enabled by default for a toolchain with an assembler that accepts it and GLIBC 2.11 or above, otherwise disabled. ! !
--with-diagnostics-color=choice
Tells GCC to use choice as the default for -fdiagnostics-color= option (if not used explicitly on the command line). choice ! can be one of ‘never’, ‘auto’, ‘always’, and ‘auto-if-env’ ! where ‘auto’ is the default. ‘auto-if-env’ means that ! -fdiagnostics-color=auto will be the default if GCC_COLORS is present and non-empty in the environment, and ! -fdiagnostics-color=never otherwise. ! !
--enable-lto
--disable-lto
Enable support for link-time optimization (LTO). This is enabled by ! default, and may be disabled using --disable-lto. ! !
--enable-linker-plugin-configure-flags=FLAGS
--enable-linker-plugin-flags=FLAGS
By default, linker plugins (such as the LTO plugin) are built for the host system architecture. For the case that the linker has a different (but run-time compatible) architecture, these flags can be specified to build plugins that are compatible to the linker. For example, if you are building GCC for a 64-bit x86_64 ! (‘x86_64-unknown-linux-gnu’) host system, but have a 32-bit x86 ! GNU/Linux (‘i686-pc-linux-gnu’) linker executable (which is executable on the former system), you can configure GCC as follows for getting compatible linker plugins: ! 
          % srcdir/configure \
!               --host=x86_64-unknown-linux-gnu \
!               --enable-linker-plugin-configure-flags=--host=i686-pc-linux-gnu \
!               --enable-linker-plugin-flags='CC=gcc\ -m32\ -Wl,-rpath,[...]/i686-pc-linux-gnu/lib'
!
!
--with-plugin-ld=pathname
Enable an alternate linker to be used at link-time optimization (LTO) ! link time when -fuse-linker-plugin is enabled. This linker should have plugin support such as gold starting with ! version 2.20 or GNU ld starting with version 2.21. ! See -fuse-linker-plugin for details. ! !
--enable-canonical-system-headers
--disable-canonical-system-headers
Enable system header path canonicalization for libcpp. This can produce shorter header file paths in diagnostics and dependency output files, but these changed header paths may conflict with some compilation environments. Enabled by default, and may be disabled using ! --disable-canonical-system-headers. ! !
--with-glibc-version=major.minor
Tell GCC that when the GNU C Library (glibc) is used on the target it will be version major.minor or later. Normally this can ! be detected from the C library's header files, but this option may be needed when bootstrapping a cross toolchain without the header files available for building the initial bootstrap compiler. ! !

If GCC is configured with some multilibs that use glibc and some that ! do not, this option applies only to the multilibs that use glibc. However, such configurations may not work well as not all the relevant configuration in GCC is on a per-multilib basis. ! !

--enable-as-accelerator-for=target
Build as offload target compiler. Specify offload host triple by target. ! !
--enable-offload-targets=target1[=path1],...,targetN[=pathN]
Enable offloading to targets target1, ..., targetN. Offload compilers are expected to be already installed. Default search path for them is exec-prefix, but it can be changed by ! specifying paths path1, ..., pathN. ! 
          % srcdir/configure \
!               --enable-offload-target=i686-unknown-linux-gnu=/path/to/i686/compiler,x86_64-pc-linux-gnu
!
!

If ‘hsa’ is specified as one of the targets, the compiler will be built with support for HSA GPU accelerators. Because the same compiler will emit the accelerator code, no path should be specified. ! !

--with-hsa-runtime=pathname
--with-hsa-runtime-include=pathname
--with-hsa-runtime-lib=pathname
! If you configure GCC with HSA offloading but do not have the HSA run-time library installed in a standard location then you can explicitly specify the directory where they are installed. The ! --with-hsa-runtime=hsainstalldir option is a shorthand for ! --with-hsa-runtime-lib=hsainstalldir/lib and ! --with-hsa-runtime-include=hsainstalldir/include. ! !
--with-hsa-kmt-lib=pathname
! If you configure GCC with HSA offloading but do not have the HSA KMT library installed in a standard location then you can ! explicitly specify the directory where it resides.
!

Cross-Compiler-Specific Options

!

The following options only apply to building cross compilers. ! !

!
--with-sysroot
--with-sysroot=dir
Tells GCC to consider dir as the root of a tree that contains ! (a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be searched for in there. More specifically, this acts as if ! --sysroot=dir was added to the default options of the built compiler. The specified directory is not copied into the ! install tree, unlike the options --with-headers and ! --with-libs that this option obsoletes. The default value, ! in case --with-sysroot is not given an argument, is ! ${gcc_tooldir}/sys-root. If the specified directory is a ! subdirectory of ${exec_prefix}, then it will be found relative to the GCC binaries if the installation tree is moved. ! !

This option affects the system root for the compiler used to build target libraries (which runs on the build system) and the compiler newly installed with make install; it does not affect the compiler which is used to build GCC itself. ! !

If you specify the --with-native-system-header-dir=dirname option then the compiler will search that directory within dirname for ! native system headers rather than the default /usr/include. ! !

--with-build-sysroot
--with-build-sysroot=dir
Tells GCC to consider dir as the system root (see ! --with-sysroot) while building target libraries, instead of ! the directory specified with --with-sysroot. This option is ! only useful when you are already using --with-sysroot. You ! can use --with-build-sysroot when you are configuring with ! --prefix set to a directory that is different from the one in which you are installing GCC and your target libraries. ! !

This option affects the system root for the compiler used to build target libraries (which runs on the build system); it does not affect the compiler which is used to build GCC itself. ! !

If you specify the --with-native-system-header-dir=dirname option then the compiler will search that directory within dirname for ! native system headers rather than the default /usr/include. ! !

--with-headers
--with-headers=dir
Deprecated in favor of --with-sysroot. ! Specifies that target headers are available when building a cross compiler. The dir argument specifies a directory which has the target include ! files. These include files will be copied into the gcc install ! directory. This option with the dir argument is required when ! building a cross compiler, if prefix/target/sys-include ! doesn't pre-exist. If prefix/target/sys-include does ! pre-exist, the dir argument may be omitted. fixincludes will be run on these files to make them compatible with GCC. ! !
--without-headers
Tells GCC not use any target headers from a libc when building a cross compiler. When crossing to GNU/Linux, you need the headers so GCC can build the exception handling for libgcc. ! !
--with-libs
--with-libs="dir1 dir2 ... dirN"
Deprecated in favor of --with-sysroot. Specifies a list of directories which contain the target runtime ! libraries. These libraries will be copied into the gcc install directory. If the directory list is omitted, this option has no effect. ! !
--with-newlib
Specifies that ‘newlib’ is being used as the target C library. This causes __eprintf to be ! omitted from libgcc.a on the assumption that it will be provided by ! ‘newlib’. ! !
--with-avrlibc
Specifies that ‘AVR-Libc’ is being used as the target C library. This causes float support ! functions like __addsf3 to be omitted from libgcc.a on ! the assumption that it will be provided by libm.a. For more ! technical details, cf. PR54461. This option is only supported for the AVR target. It is not supported for RTEMS configurations, which currently use newlib. The option is supported since version 4.7.2 and is the default in 4.8.0 and newer. ! !
--with-nds32-lib=library
Specifies that library setting is used for building libgcc.a. ! Currently, the valid library is ‘newlib’ or ‘mculib’. This option is only supported for the NDS32 target. ! !
--with-build-time-tools=dir
Specifies where to find the set of target tools (assembler, linker, etc.) that will be used while building GCC itself. This option can be useful if the directory layouts are different between the system you are building GCC on, and the system where you will deploy it. ! !

For example, on an ‘ia64-hp-hpux’ system, you may have the GNU ! assembler and linker in /usr/bin, and the native tools in a different path, and build a toolchain that expects to find the ! native tools in /usr/bin. ! !

When you use this option, you should ensure that dir includes ! ar, as, ld, nm, ! ranlib and strip if necessary, and possibly ! objdump. Otherwise, GCC may use an inconsistent set of ! tools.

!
Overriding configure test results

Sometimes, it might be necessary to override the result of some ! configure test, for example in order to ease porting to a new ! system or work around a bug in a test. The toplevel configure script provides three variables for this: ! !

!
build_configargs
The contents of this variable is passed to all build configure scripts. ! !
host_configargs
The contents of this variable is passed to all host configure scripts. ! !
target_configargs
The contents of this variable is passed to all target configure scripts. !
! !

In order to avoid shell and make quoting issues for complex ! overrides, you can pass a setting for CONFIG_SITE and set variables in the site file. ! !

Java-Specific Options

The following option applies to the build of the Java front end. ! !

!
--disable-libgcj
Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend ! to use GCJ with some other run-time, or you're going to install it separately, or it just happens not to build on your particular machine. In general, if the Java front end is enabled, the GCJ ! libraries will be enabled too, unless they're known to not work on ! the target platform. If GCJ is enabled but ‘libgcj’ isn't built, you may need to port it; in this case, before modifying the top-level ! configure.ac so that ‘libgcj’ is enabled by default on this platform, ! you may use --enable-libgcj to override the default. !
!

The following options apply to building ‘libgcj’. ! !

General Options
! !
!
--enable-java-maintainer-mode
By default the ‘libjava’ build will not attempt to compile the ! .java source files to .class. Instead, it will use the ! .class files from the source tree. If you use this option you ! must have executables named ecj1 and gjavah in your path for use by the build. You must use this option if you intend to ! modify any .java files in libjava. ! !
--with-java-home=dirname
This ‘libjava’ option overrides the default value of the ! ‘java.home’ system property. It is also used to set ! ‘sun.boot.class.path’ to dirname/lib/rt.jar. By ! default ‘java.home’ is set to prefix and ! ‘sun.boot.class.path’ to ! datadir/java/libgcj-version.jar. ! !
--with-ecj-jar=filename
This option can be used to specify the location of an external jar file containing the Eclipse Java compiler. A specially modified ! version of this compiler is used by gcj to parse ! .java source files. If this option is given, the ! ‘libjava’ build will create and install an ecj1 executable which uses this jar file at runtime. ! !

If this option is not given, but an ecj.jar file is found in ! the topmost source tree at configure time, then the ‘libgcj’ ! build will create and install ecj1, and will also install the ! discovered ecj.jar into a suitable place in the install tree. ! !

If ecj1 is not installed, then the user will have to supply one ! on his path in order for gcj to properly parse .java source files. A suitable jar is available from ftp://sourceware.org/pub/java/. ! !

--disable-getenv-properties
Don't set system properties from GCJ_PROPERTIES. ! !
--enable-hash-synchronization
Use a global hash table for monitor locks. Ordinarily, ! ‘libgcj’'s ‘configure’ script automatically makes the correct choice for this option for your platform. Only use this if you know you need the library to be configured differently. ! !
--enable-interpreter
Enable the Java interpreter. The interpreter is automatically enabled by default on all platforms that support it. This option is really only useful if you want to disable the interpreter ! (using --disable-interpreter). ! !
--disable-java-net
Disable java.net. This disables the native part of java.net only, using non-functional stubs for native method implementations. ! !
--disable-jvmpi
Disable JVMPI support. ! !
--disable-libgcj-bc
Disable BC ABI compilation of certain parts of libgcj. By default, ! some portions of libgcj are compiled with -findirect-dispatch ! and -fno-indirect-classes, allowing them to be overridden at run-time. ! !

If --disable-libgcj-bc is specified, libgcj is built without these options. This allows the compile-time linker to resolve dependencies when statically linking to libgcj. However it makes it impossible to override the affected portions of libgcj at run-time. ! !

--enable-reduced-reflection
Build most of libgcj with -freduced-reflection. This reduces the size of libgcj at the expense of not being able to do accurate reflection on the classes it contains. This option is safe if you know that code using libgcj will never use reflection on the standard runtime classes in libgcj (including using serialization, RMI or CORBA). ! !
--with-ecos
Enable runtime eCos target support. ! !
--without-libffi
Don't use ‘libffi’. This will disable the interpreter and JNI ! support as well, as these require ‘libffi’ to work. ! !
--enable-libgcj-debug
Enable runtime debugging code. ! !
--enable-libgcj-multifile
If specified, causes all .java source files to be ! compiled into .class files in one invocation of ! ‘gcj’. This can speed up build time, but is more resource-intensive. If this option is unspecified or ! disabled, ‘gcj’ is invoked once for each .java ! file to compile into a .class file. ! !
--with-libiconv-prefix=DIR
Search for libiconv in DIR/include and DIR/lib. ! !
--with-system-zlib
Use installed ‘zlib’ rather than that included with GCC. ! !
--with-win32-nlsapi=ansi, unicows or unicode
Indicates how MinGW ‘libgcj’ translates between UNICODE characters and the Win32 API. ! !
--enable-java-home
If enabled, this creates a JPackage compatible SDK environment during install. Note that if –enable-java-home is used, –with-arch-directory=ARCH must also be specified. ! !
--with-arch-directory=ARCH
Specifies the name to use for the jre/lib/ARCH directory in the SDK environment created when –enable-java-home is passed. Typical names for this directory include i386, amd64, ia64, etc. ! !
--with-os-directory=DIR
Specifies the OS directory for the SDK include directory. This is set to auto ! detect, and is typically 'linux'. ! !
--with-origin-name=NAME
Specifies the JPackage origin name. This defaults to the 'gcj' in java-1.5.0-gcj. ! !
--with-arch-suffix=SUFFIX
Specifies the suffix for the sdk directory. Defaults to the empty string. ! Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'. ! !
--with-jvm-root-dir=DIR
Specifies where to install the SDK. Default is $(prefix)/lib/jvm. ! !
--with-jvm-jar-dir=DIR
Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. ! !
--with-python-dir=DIR
Specifies where to install the Python modules used for aot-compile. DIR should not include the prefix used in installation. For example, if the Python modules are to be installed in /usr/lib/python2.5/site-packages, then –with-python-dir=/lib/python2.5/site-packages should be passed. If this is not specified, then the Python modules are installed in $(prefix)/share/python. ! !
--enable-aot-compile-rpm
Adds aot-compile-rpm to the list of installed scripts. ! !
--enable-browser-plugin
Build the gcjwebplugin web browser plugin. ! !
--enable-static-libjava
Build static libraries in libjava. The default is to only build shared libraries. ! !
!
ansi
Use the single-byte char and the Win32 A functions natively, translating to and from UNICODE when using these functions. If unspecified, this is the default. !
unicows
Use the WCHAR and Win32 W functions natively. Adds ! -lunicows to libgcj.spec to link with ‘libunicows’. ! unicows.dll needs to be deployed on Microsoft Windows 9X machines ! running built executables. libunicows.a, an open-source ! import library around Microsoft's unicows.dll, is obtained from ! http://libunicows.sourceforge.net/, which also gives details ! on getting unicows.dll from Microsoft. !
unicode
Use the WCHAR and Win32 W functions natively. Does not ! add -lunicows to libgcj.spec. The built executables will ! only run on Microsoft Windows NT and above.
+
+
AWT-Specific Options
!
!
--with-x
Use the X Window System. ! !
--enable-java-awt=PEER(S)
Specifies the AWT peer library or libraries to build alongside ! ‘libgcj’. If this option is unspecified or disabled, AWT ! will be non-functional. Current valid values are gtk and ! xlib. Multiple libraries should be separated by a ! comma (i.e. --enable-java-awt=gtk,xlib). +
--enable-gtk-cairo
Build the cairo Graphics2D implementation on GTK. +
--enable-java-gc=TYPE
Choose garbage collector. Defaults to boehm if unspecified. +
--disable-gtktest
Do not try to compile and run a test GTK+ program. +
--disable-glibtest
Do not try to compile and run a test GLIB program. +
--with-libart-prefix=PFX
Prefix where libart is installed (optional). +
--with-libart-exec-prefix=PFX
Exec prefix where libart is installed (optional). +
--disable-libarttest
Do not try to compile and run a test libart program. +
+

+

Return to the GCC Installation page + + + + + + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/download.html gcc-6.4.0/INSTALL/download.html *** gcc-6.3.0/INSTALL/download.html Wed Dec 21 07:54:10 2016 --- gcc-6.4.0/INSTALL/download.html Tue Jul 4 07:28:15 2017 *************** *** 1,135 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

GCC is distributed via SVN and FTP ! tarballs compressed with gzip or ! bzip2. !

!

Please refer to the releases web page for information on how to obtain GCC. !

!

The source distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in the case of GCC 3.1 and later) compilers, as well as ! runtime libraries for C++, Objective-C, Fortran, and Java. For previous versions these were downloadable as separate components such as the core GCC distribution, which included the C language front end and shared components, and language-specific distributions including the language front end and the language runtime (where appropriate). !

!

If you also intend to build binutils (either to upgrade an existing installation or for use in place of the corresponding tools of your OS), unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components of the binutils you intend to build alongside the compiler ! (bfd, binutils, gas, gprof, ld, ! opcodes, …) to the directory containing the GCC sources. !

!

Likewise the GMP, MPFR and MPC libraries can be automatically built together with GCC. You may simply run the ! contrib/download_prerequisites script in the GCC source directory ! to set up everything. Otherwise unpack the GMP, MPFR and/or MPC source distributions in the directory containing the GCC sources and rename ! their directories to gmp, mpfr and mpc, respectively (or use symbolic links with the same name). -

-
-

-

Return to the GCC Installation page -

- - - - - - - - - - - --- 1,90 ---- ! ! ! Downloading GCC ! ! ! ! ! ! ! ! + +

Downloading GCC

+ + GCC is distributed via SVN and FTP + tarballs compressed with gzip or + bzip2. !

Please refer to the releases web page for information on how to obtain GCC. ! !

The source distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in the case of GCC 3.1 and later) compilers, as well as ! runtime libraries for C++, Objective-C, Fortran, and Java. For previous versions these were downloadable as separate components such as the core GCC distribution, which included the C language front end and shared components, and language-specific distributions including the language front end and the language runtime (where appropriate). ! !

If you also intend to build binutils (either to upgrade an existing installation or for use in place of the corresponding tools of your OS), unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components of the binutils you intend to build alongside the compiler ! (bfd, binutils, gas, gprof, ld, ! opcodes, ...) to the directory containing the GCC sources. ! !

Likewise the GMP, MPFR and MPC libraries can be automatically built together with GCC. You may simply run the ! contrib/download_prerequisites script in the GCC source directory ! to set up everything. Otherwise unpack the GMP, MPFR and/or MPC source distributions in the directory containing the GCC sources and rename ! their directories to gmp, mpfr and mpc, respectively (or use symbolic links with the same name). +

+

Return to the GCC Installation page + + + + + + + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/finalinstall.html gcc-6.4.0/INSTALL/finalinstall.html *** gcc-6.3.0/INSTALL/finalinstall.html Wed Dec 21 07:54:11 2016 --- gcc-6.4.0/INSTALL/finalinstall.html Tue Jul 4 07:28:15 2017 *************** *** 1,227 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

Now that GCC has been built (and optionally tested), you can install it with !

! 
cd objdir && make install
!
! !

We strongly recommend to install into a target directory where there is no previous version of GCC present. Also, the GNAT runtime should not be stripped, as this would break certain features of the debugger that depend on this debugging information (catching Ada exceptions for instance). !

!

That step completes the installation of GCC; user level binaries can ! be found in prefix/bin where prefix is the value ! you specified with the --prefix to configure (or ! /usr/local by default). (If you specified --bindir, that directory will be used instead; otherwise, if you specified ! --exec-prefix, exec-prefix/bin will be used.) Headers for the C++ and Java libraries are installed in ! prefix/include; libraries in libdir ! (normally prefix/lib); internal parts of the compiler in ! libdir/gcc and libexecdir/gcc; documentation in info format in infodir (normally ! prefix/info). !

!

When installing cross-compilers, GCC’s executables are not only installed into bindir, that ! is, exec-prefix/bin, but additionally into ! exec-prefix/target-alias/bin, if that directory ! exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker. !

!

Installation into a temporary staging area or into a chroot jail can be achieved with the command -

-
- 
make DESTDIR=path-to-rootdir install
-
!

where path-to-rootdir is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the directory specified by DESTDIR need not exist yet; it will be created if necessary. !

!

There is a subtle point with tooldirs and DESTDIR: If you relocate a cross-compiler installation with ! e.g. ‘DESTDIR=rootdir’, then the directory ! rootdir/exec-prefix/target-alias/bin will be filled with duplicated GCC executables only if it already exists, it will not be created otherwise. This is regarded as a feature, not as a bug, because it gives slightly more control to the packagers using the DESTDIR feature. -

-

You can install stripped programs and libraries with -

-
- 
make install-strip
-
!

If you are bootstrapping a released version of GCC then please quickly review the build status page for your release, available from ! http://gcc.gnu.org/buildstat.html. If your system is not listed for the version of GCC that you built, send a note to gcc@gcc.gnu.org indicating ! that you successfully built and installed GCC. Include the following information: !

! !

We’d also like to know if the host/target specific installation notes ! didn’t include your host/target information or if that information is incomplete or out of date. Send a note to gcc@gcc.gnu.org detailing how the information should be changed. !

!

If you find a bug, please report it following the bug reporting guidelines. !

!

If you want to print the GCC manuals, do ‘cd objdir; make ! dvi’. You will need to have texi2dvi (version at least 4.7) ! and TeX installed. This creates a number of .dvi files in subdirectories of objdir; these may be converted for ! printing with programs such as dvips. Alternately, by using ! ‘make pdf’ in place of ‘make dvi’, you can create documentation ! in the form of .pdf files; this requires texi2pdf, which is included with Texinfo version 4.8 and later. You can also ! buy printed manuals from the ! Free Software Foundation, though such manuals may not be for the most recent version of GCC. -

-

If you would like to generate online HTML documentation, do ‘cd - objdir; make html’ and HTML will be generated for the gcc manuals in - objdir/gcc/HTML. -

-
-

-

Return to the GCC Installation page -

- - - - - - --- 1,172 ---- ! ! ! Installing GCC: Final installation ! ! ! ! ! ! ! ! ! !

Installing GCC: Final installation

! Now that GCC has been built (and optionally tested), you can install it with ! 
     cd objdir && make install
!
!

We strongly recommend to install into a target directory where there is no previous version of GCC present. Also, the GNAT runtime should not be stripped, as this would break certain features of the debugger that depend on this debugging information (catching Ada exceptions for instance). ! !

That step completes the installation of GCC; user level binaries can ! be found in prefix/bin where prefix is the value ! you specified with the --prefix to configure (or ! /usr/local by default). (If you specified --bindir, that directory will be used instead; otherwise, if you specified ! --exec-prefix, exec-prefix/bin will be used.) Headers for the C++ and Java libraries are installed in ! prefix/include; libraries in libdir ! (normally prefix/lib); internal parts of the compiler in ! libdir/gcc and libexecdir/gcc; documentation in info format in infodir (normally ! prefix/info). ! !

When installing cross-compilers, GCC's executables are not only installed into bindir, that ! is, exec-prefix/bin, but additionally into ! exec-prefix/target-alias/bin, if that directory ! exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker. ! !

Installation into a temporary staging area or into a chroot jail can be achieved with the command ! 

     make DESTDIR=path-to-rootdir install
!
!

where path-to-rootdir is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the directory specified by DESTDIR need not exist yet; it will be created if necessary. ! !

There is a subtle point with tooldirs and DESTDIR: If you relocate a cross-compiler installation with ! e.g. ‘DESTDIR=rootdir’, then the directory ! rootdir/exec-prefix/target-alias/bin will be filled with duplicated GCC executables only if it already exists, it will not be created otherwise. This is regarded as a feature, not as a bug, because it gives slightly more control to the packagers using the DESTDIR feature. !

You can install stripped programs and libraries with ! ! 

     make install-strip
!
!

If you are bootstrapping a released version of GCC then please quickly review the build status page for your release, available from ! http://gcc.gnu.org/buildstat.html. If your system is not listed for the version of GCC that you built, send a note to gcc@gcc.gnu.org indicating ! that you successfully built and installed GCC. Include the following information: ! !

!

We'd also like to know if the host/target specific installation notes ! didn't include your host/target information or if that information is incomplete or out of date. Send a note to gcc@gcc.gnu.org detailing how the information should be changed. ! !

If you find a bug, please report it following the bug reporting guidelines. ! !

If you want to print the GCC manuals, do ‘cd objdir; make ! dvi’. You will need to have texi2dvi (version at least 4.7) ! and TeX installed. This creates a number of .dvi files in subdirectories of objdir; these may be converted for ! printing with programs such as dvips. Alternately, by using ! ‘make pdf’ in place of ‘make dvi’, you can create documentation ! in the form of .pdf files; this requires texi2pdf, which is included with Texinfo version 4.8 and later. You can also ! buy printed manuals from the Free Software Foundation, though such manuals may not be for the most recent version of GCC. +

If you would like to generate online HTML documentation, do ‘cd + objdir; make html’ and HTML will be generated for the gcc manuals in + objdir/gcc/HTML. +

+

Return to the GCC Installation page + + + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/gfdl.html gcc-6.4.0/INSTALL/gfdl.html *** gcc-6.3.0/INSTALL/gfdl.html Wed Dec 21 07:54:12 2016 --- gcc-6.4.0/INSTALL/gfdl.html Tue Jul 4 07:28:15 2017 *************** *** 1,133 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC: GNU Free Documentation License

! ! !
Version 1.3, 3 November 2008 !
!
! 
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
! http://fsf.org/
! 
! Everyone is permitted to copy and distribute verbatim copies
! of this license document, but changing it is not allowed.
!
!
    !
  1. PREAMBLE !

    The purpose of this License is to make a manual, textbook, or other ! functional and useful document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, ! with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. !

    !

    This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. !

    !

    We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. -

    -
  2. APPLICABILITY AND DEFINITIONS !

    This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that --- 1,82 ---- ! ! ! Installing GCC: GNU Free Documentation License ! ! ! ! ! ! ! ! + +

    Installing GCC: GNU Free Documentation License

    +

    Installing GCC: GNU Free Documentation License

    !

    Version 1.3, 3 November 2008
    ! 
         Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
!      http://fsf.org/
!      
!      Everyone is permitted to copy and distribute verbatim copies
!      of this license document, but changing it is not allowed.
!
    !
      !
    1. PREAMBLE !

      The purpose of this License is to make a manual, textbook, or other ! functional and useful document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, ! with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. ! !

      This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. ! !

      We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. !

    2. APPLICABILITY AND DEFINITIONS ! !

      This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that *************** refers to any such manual or work. Any *** 136,149 **** licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. !

      !

      A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. !

      !

      A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the ! publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain --- 85,98 ---- licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. ! !

      A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. ! !

      A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the ! publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain *************** any mathematics.) The relationship coul *** 151,171 **** connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. !

      !

      The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. !

      !

      The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. !

      !

      A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of --- 100,120 ---- connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. ! !

      The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. ! !

      The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. ! !

      A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of *************** drawing editor, and that is suitable for *** 174,185 **** for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart ! or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”. !

      !

      Examples of suitable formats for Transparent copies include plain ! ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples --- 123,134 ---- for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart ! or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”. ! !

      Examples of suitable formats for Transparent copies include plain ! ascii without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples *************** read and edited only by proprietary word *** 190,224 **** not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. !

      !

      The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means ! the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text. !

      !

      The “publisher” means any person or entity that distributes copies of the Document to the public. !

      !

      A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition. !

      !

      The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. -

      -
    3. VERBATIM COPYING !

      You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other --- 139,173 ---- not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. ! !

      The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means ! the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. ! !

      The “publisher” means any person or entity that distributes copies of the Document to the public. ! !

      A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition. ! !

      The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. !

    4. VERBATIM COPYING ! !

      You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other *************** technical measures to obstruct or contro *** 227,313 **** copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. !

      !

      You may also lend copies, under the same conditions stated above, and you may publicly display copies. -

      -
    5. COPYING IN QUANTITY !

      If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the ! Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and ! visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. !

      !

      If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. !

      !

      If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols ! a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. !

      !

      It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. -

      -
    6. MODIFICATIONS !

      You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: !

      !
        !
      1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. !
      2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. !
      3. State on the Title page the name of the publisher of the Modified Version, as the publisher. !
      4. Preserve all the copyright notices of the Document. !
      5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. !
      6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. !
      7. Preserve in that license notice the full lists of Invariant Sections ! and required Cover Texts given in the Document’s license notice. !
      8. Include an unaltered copy of this License. !
      9. Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one --- 176,262 ---- copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. ! !

        You may also lend copies, under the same conditions stated above, and you may publicly display copies. !

      10. COPYING IN QUANTITY ! !

        If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the ! Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and ! visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. ! !

        If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. ! !

        If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols ! a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. ! !

        It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. !

      11. MODIFICATIONS ! !

        You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: ! !

          !
        1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. !
        2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. !
        3. State on the Title page the name of the publisher of the Modified Version, as the publisher. !
        4. Preserve all the copyright notices of the Document. !
        5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. !
        6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. !
        7. Preserve in that license notice the full lists of Invariant Sections ! and required Cover Texts given in the Document's license notice. !
        8. Include an unaltered copy of this License. !
        9. Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one *************** stating the title, year, authors, and pu *** 315,360 **** given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. !
        10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions ! it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. !
        11. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. !
        12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. !
        13. Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version. !
        14. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section. !
        15. Preserve any Warranty Disclaimers. !
        !

        If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the ! list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles. !

        !

        You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. !

        !

        You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or --- 264,309 ---- given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. !

      12. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions ! it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. !
      13. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. !
      14. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. !
      15. Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version. !
      16. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section. !
      17. Preserve any Warranty Disclaimers. !
      !

      If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the ! list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. ! !

      You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. ! !

      You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or *************** includes a cover text for the same cover *** 363,433 **** by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. !

      !

      The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. -

      -
    7. COMBINING DOCUMENTS !

      You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. !

      !

      The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original ! author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. !

      !

      In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements.” -

      -
    8. COLLECTIONS OF DOCUMENTS !

      You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. !

      !

      You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. -

      -
    9. AGGREGATION WITH INDEPENDENT WORKS !

      A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights ! of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. !

      !

      If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of ! the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the ! electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. -

      -
    10. TRANSLATION !

      Translation is considered a kind of modification, so you may ! distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the --- 312,382 ---- by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. ! !

      The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. !

    11. COMBINING DOCUMENTS ! !

      You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. ! !

      The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original ! author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. ! !

      In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements.” !

    12. COLLECTIONS OF DOCUMENTS ! !

      You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. ! !

      You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. !

    13. AGGREGATION WITH INDEPENDENT WORKS ! !

      A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights ! of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. ! !

      If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of ! the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the ! electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. !

    14. TRANSLATION ! !

      Translation is considered a kind of modification, so you may ! distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the *************** the original English version of this Lic *** 438,485 **** of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. !

      !

      If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. -

      -
    15. TERMINATION !

      You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License. !

      !

      However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. !

      !

      Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. !

      !

      Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it. -

      -
    16. FUTURE REVISIONS OF THIS LICENSE !

      The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. !

      !

      Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or --- 387,434 ---- of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. ! !

      If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. !

    17. TERMINATION ! !

      You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License. ! !

      However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. ! !

      Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. ! !

      Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it. !

    18. FUTURE REVISIONS OF THIS LICENSE ! !

      The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. ! !

      Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or *************** Free Software Foundation. If the Docume *** 488,572 **** number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this ! License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Document. -

      -
    19. RELICENSING !

      “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A “Massive Multiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightable works thus published on the MMC site. !

      !

      “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization. !

      !

      “Incorporate” means to publish or republish a Document, in whole or in part, as part of another Document. !

      !

      An MMC is “eligible for relicensing” if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008. !

      !

      The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. -

      -
    ! !

    ADDENDUM: How to use this License for your documents

    To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: -

    -
    - 
      Copyright (C)  year  your name.
-   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 no Invariant Sections, no Front-Cover Texts, and no Back-Cover
-   Texts.  A copy of the license is included in the section entitled ``GNU
-   Free Documentation License''.
-
    !

    If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this: -

    -
    - 
        with the Invariant Sections being list their titles, with
-     the Front-Cover Texts being list, and with the Back-Cover Texts
-     being list.
-
    !

    If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. !

    !

    If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. -

    !
    !

    Return to the GCC Installation page -

    - -
    - - - --- 437,515 ---- number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this ! License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. !
  3. RELICENSING ! !

    “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A “Massive Multiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightable works thus published on the MMC site. ! !

    “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization. ! !

    “Incorporate” means to publish or republish a Document, in whole or in part, as part of another Document. ! !

    An MMC is “eligible for relicensing” if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008. ! !

    The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. !

! !

ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: ! 

       Copyright (C)  year  your name.
!        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 no Invariant Sections, no Front-Cover Texts, and no Back-Cover
!        Texts.  A copy of the license is included in the section entitled ``GNU
!        Free Documentation License''.
!
!

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this: ! 

         with the Invariant Sections being list their titles, with
!          the Front-Cover Texts being list, and with the Back-Cover Texts
!          being list.
!
!

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. ! !

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. ! ! ! ! !

Return to the GCC Installation page + + + diff -Nrcpad gcc-6.3.0/INSTALL/index.html gcc-6.4.0/INSTALL/index.html *** gcc-6.3.0/INSTALL/index.html Wed Dec 21 07:54:09 2016 --- gcc-6.4.0/INSTALL/index.html Tue Jul 4 07:28:15 2017 *************** *** 1,165 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

The latest version of this document is always available at ! http://gcc.gnu.org/install/. It refers to the current development sources, instructions for specific released versions are included with the sources. !

!

This document describes the generic installation procedure for GCC as well as detailing some target specific installation instructions. !

!

GCC includes several components that previously were separate distributions with their own installation instructions. This document supersedes all package-specific installation instructions. !

!

Before starting the build/install procedure please check the ! host/target specific installation notes. We recommend you browse the entire generic installation instructions before you proceed. !

!

Lists of successful builds for released versions of GCC are ! available at http://gcc.gnu.org/buildstat.html. These lists are updated as new information becomes available. -

-

The installation procedure itself is broken into five steps. -

-
    -
  1. Prerequisites -
  2. Downloading the source -
  3. Configuration -
  4. Building -
  5. Testing (optional) -
  6. Final install -
!

Please note that GCC does not support ‘make uninstall’ and probably ! won’t do so in the near future as this would open a can of worms. Instead, we suggest that you install GCC into a directory of its own and simply remove that directory when you do not need that specific version of GCC any longer, and, if shared libraries are installed there as well, no more binaries exist that use them. !

!

There are also some old installation instructions, which are mostly obsolete but still contain some information which has not yet been merged into the main part of this manual. !

!
!

Return to the GCC Installation page !

!

Copyright © 1988-2016 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 no Invariant Sections, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the ! license is included in the section entitled “GNU ! Free Documentation License”. !

!

(a) The FSF’s Front-Cover Text is: !

!

A GNU Manual !

!

(b) The FSF’s Back-Cover Text is: !

!

You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. !

! ! ! ! ! ! ! ! ! - - --- 1,123 ---- ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! !

Installing GCC

! The latest version of this document is always available at ! http://gcc.gnu.org/install/. It refers to the current development sources, instructions for specific released versions are included with the sources. ! !

This document describes the generic installation procedure for GCC as well as detailing some target specific installation instructions. ! !

GCC includes several components that previously were separate distributions with their own installation instructions. This document supersedes all package-specific installation instructions. ! !

Before starting the build/install procedure please check the ! host/target specific installation notes. We recommend you browse the entire generic installation instructions before you proceed. ! !

Lists of successful builds for released versions of GCC are ! available at http://gcc.gnu.org/buildstat.html. These lists are updated as new information becomes available. !

The installation procedure itself is broken into five steps. ! !

    !
  1. Prerequisites !
  2. Downloading the source !
  3. Configuration !
  4. Building !
  5. Testing (optional) !
  6. Final install !
! !

Please note that GCC does not support ‘make uninstall’ and probably ! won't do so in the near future as this would open a can of worms. Instead, we suggest that you install GCC into a directory of its own and simply remove that directory when you do not need that specific version of GCC any longer, and, if shared libraries are installed there as well, no more binaries exist that use them. ! !

There are also some old installation instructions, which are mostly obsolete but still contain some information which has not yet been merged into the main part of this manual. ! !

Return to the GCC Installation page ! !

Copyright © 1988-2017 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 no Invariant Sections, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the ! license is included in the section entitled “GNU Free Documentation License”. +

(a) The FSF's Front-Cover Text is: +

A GNU Manual +

(b) The FSF's Back-Cover Text is: +

You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + + + + + + + + + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/old.html gcc-6.4.0/INSTALL/old.html *** gcc-6.3.0/INSTALL/old.html Wed Dec 21 07:54:12 2016 --- gcc-6.4.0/INSTALL/old.html Tue Jul 4 07:28:15 2017 *************** *** 1,232 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

Old installation documentation

!

Note most of this information is out of date and superseded by the previous chapters of this manual. It is provided for historical reference only, because of a lack of volunteers to merge it into the main manual. -

!

Here is the procedure for installing GCC on a GNU or Unix system. !

!
    !
  1. If you have chosen a configuration for GCC which requires other GNU tools (such as GAS or the GNU linker) instead of the standard system tools, install the required tools in the build directory under the names ! as, ld or whatever is appropriate. !

    Alternatively, you can do subsequent compilation using a value of the PATH environment variable such that the necessary GNU tools come before the standard system tools. -

    -
  2. Specify the host, build and target machine configurations. You do this - when you run the configure script. !

    The build machine is the system which you are using, the ! host machine is the system where you want to run the resulting ! compiler (normally the build machine), and the target machine is the system for which you want the compiler to generate code. !

    !

    If you are building a compiler to produce code for the machine it runs on (a native compiler), you normally do not need to specify any operands ! to configure; it will try to guess the type of machine you are on ! and use that as the build, host and target machines. So you don’t need to specify a configuration when building a native compiler unless ! configure cannot figure out what your configuration is or guesses wrong. !

    !

    In those cases, specify the build machine’s configuration name ! with the --host option; the host and target will default to be the same as the host machine. -

    -

    Here is an example: -

    -
    - 
    ./configure --host=sparc-sun-sunos4.1
-
    !

    A configuration name may be canonical or it may be more or less abbreviated. !

    !

    A canonical configuration name has three parts, separated by dashes. ! It looks like this: ‘cpu-company-system’. ! (The three parts may themselves contain dashes; configure can figure out which dashes serve which purpose.) For example, ! ‘m68k-sun-sunos4.1’ specifies a Sun 3. !

    !

    You can also replace parts of the configuration by nicknames or aliases. ! For example, ‘sun3’ stands for ‘m68k-sun’, so ! ‘sun3-sunos4.1’ is another way to specify a Sun 3. !

    !

    You can specify a version number after any of the system types, and some of the CPU types. In most cases, the version is irrelevant, and will be ignored. So you might as well specify the version if you know it. !

    !

    See Configurations, for a list of supported configuration names and notes on many of the configurations. You should check the notes in that section before proceeding any further with the installation of GCC. -

    -
!

Configurations Supported by GCC

! !

Here are the possible CPU types: !

!
!

1750a, a29k, alpha, arm, avr, cn, clipper, dsp16xx, elxsi, fr30, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc, ! sparclite, sparc64, v850, vax, we32k. !

!

Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names. !

!
!

acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent, convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron, plexus, ! sequent, sgi, sony, sun, tti, unicom, wrs. !

!

The company name is meaningful only to disambiguate when the rest of the information supplied is insufficient. You can omit it, writing ! just ‘cpu-system’, if it is not needed. For example, ! ‘vax-ultrix4.2’ is equivalent to ‘vax-dec-ultrix4.2’. !

!

Here is a list of system types: !

!
!

386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs, netbsd, newsos, nindy, ns, osf, osfrose, ptx, riscix, riscos, rtu, sco, sim, solaris, sunos, sym, sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, ! vxworks, winnt, xenix. !

!

You can omit the system type; then configure guesses the operating system from the CPU and company. !

!

You can add a version number to the system type; this may or may not ! make a difference. For example, you can write ‘bsd4.3’ or ! ‘bsd4.4’ to distinguish versions of BSD. In practice, the version ! number is most needed for ‘sysv3’ and ‘sysv4’, which are often treated differently. !

!

‘linux-gnu’ is the canonical name for the GNU/Linux target; however ! GCC will also accept ‘linux’. The version of the kernel in use is ! not relevant on these systems. A suffix such as ‘libc1’ or ‘aout’ distinguishes major versions of the C library; all of the suffixed versions are obsolete. !

!

If you specify an impossible combination such as ‘i860-dg-vms’, ! then you may get an error message from configure, or it may ! ignore part of the information and do the best it can with the rest. ! configure always prints the canonical name for the alternative that it used. GCC does not support all possible alternatives. !

!

Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the machine ! name ‘sun3’, mentioned above, is an alias for ‘m68k-sun’. Sometimes we accept a company name as a machine name, when the name is popularly used for a particular machine. Here is a table of the known machine names: !

!
!

3300, 3b1, 3bn, 7300, altos3068, altos, apollo68, att-7300, balance, convex-cn, crds, decstation-3100, decstation, delta, encore, --- 1,181 ---- ! ! ! Installing GCC: Old documentation ! ! ! ! ! ! ! ! ! !

Installing GCC: Old documentation

Old installation documentation

!

Note most of this information is out of date and superseded by the previous chapters of this manual. It is provided for historical reference only, because of a lack of volunteers to merge it into the main manual. !

Here is the procedure for installing GCC on a GNU or Unix system. ! !

    !
  1. If you have chosen a configuration for GCC which requires other GNU tools (such as GAS or the GNU linker) instead of the standard system tools, install the required tools in the build directory under the names ! as, ld or whatever is appropriate. !

    Alternatively, you can do subsequent compilation using a value of the PATH environment variable such that the necessary GNU tools come before the standard system tools. !

  2. Specify the host, build and target machine configurations. You do this ! when you run the configure script. ! !

    The build machine is the system which you are using, the ! host machine is the system where you want to run the resulting ! compiler (normally the build machine), and the target machine is the system for which you want the compiler to generate code. ! !

    If you are building a compiler to produce code for the machine it runs on (a native compiler), you normally do not need to specify any operands ! to configure; it will try to guess the type of machine you are on ! and use that as the build, host and target machines. So you don't need to specify a configuration when building a native compiler unless ! configure cannot figure out what your configuration is or guesses wrong. ! !

    In those cases, specify the build machine's configuration name ! with the --host option; the host and target will default to be the same as the host machine. !

    Here is an example: ! ! 

              ./configure --host=sparc-sun-sunos4.1
!
    !

    A configuration name may be canonical or it may be more or less abbreviated. ! !

    A canonical configuration name has three parts, separated by dashes. ! It looks like this: ‘cpu-company-system’. ! (The three parts may themselves contain dashes; configure can figure out which dashes serve which purpose.) For example, ! ‘m68k-sun-sunos4.1’ specifies a Sun 3. ! !

    You can also replace parts of the configuration by nicknames or aliases. ! For example, ‘sun3’ stands for ‘m68k-sun’, so ! ‘sun3-sunos4.1’ is another way to specify a Sun 3. ! !

    You can specify a version number after any of the system types, and some of the CPU types. In most cases, the version is irrelevant, and will be ignored. So you might as well specify the version if you know it. ! !

    See Configurations, for a list of supported configuration names and notes on many of the configurations. You should check the notes in that section before proceeding any further with the installation of GCC. !

!

Configurations Supported by GCC

! Here are the possible CPU types: ! !
! ! 1750a, a29k, alpha, arm, avr, cn, clipper, dsp16xx, elxsi, fr30, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc, ! sparclite, sparc64, v850, vax, we32k. !
!

Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names. ! ! !

! acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent, convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron, plexus, ! sequent, sgi, sony, sun, tti, unicom, wrs. !
!

The company name is meaningful only to disambiguate when the rest of the information supplied is insufficient. You can omit it, writing ! just ‘cpu-system’, if it is not needed. For example, ! ‘vax-ultrix4.2’ is equivalent to ‘vax-dec-ultrix4.2’. ! !

Here is a list of system types: ! !

! 386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs, netbsd, newsos, nindy, ns, osf, osfrose, ptx, riscix, riscos, rtu, sco, sim, solaris, sunos, sym, sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, ! vxworks, winnt, xenix. !
!

You can omit the system type; then configure guesses the operating system from the CPU and company. ! !

You can add a version number to the system type; this may or may not ! make a difference. For example, you can write ‘bsd4.3’ or ! ‘bsd4.4’ to distinguish versions of BSD. In practice, the version ! number is most needed for ‘sysv3’ and ‘sysv4’, which are often treated differently. ! !

‘linux-gnu’ is the canonical name for the GNU/Linux target; however ! GCC will also accept ‘linux’. The version of the kernel in use is ! not relevant on these systems. A suffix such as ‘libc1’ or ‘aout’ distinguishes major versions of the C library; all of the suffixed versions are obsolete. ! !

If you specify an impossible combination such as ‘i860-dg-vms’, ! then you may get an error message from configure, or it may ! ignore part of the information and do the best it can with the rest. ! configure always prints the canonical name for the alternative that it used. GCC does not support all possible alternatives. ! !

Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the machine ! name ‘sun3’, mentioned above, is an alias for ‘m68k-sun’. Sometimes we accept a company name as a machine name, when the name is popularly used for a particular machine. Here is a table of the known machine names: ! !

! 3300, 3b1, 3bn, 7300, altos3068, altos, apollo68, att-7300, balance, convex-cn, crds, decstation-3100, decstation, delta, encore, *************** m3230, magnum, merlin, miniframe, *** 237,255 **** mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3, ! sun4, symmetry, tower-32, tower. !

!

Remember that a machine name specifies both the cpu type and the company ! name.

!

! Return to the GCC Installation page !

! ! ! - - --- 186,201 ---- mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3, ! sun4, symmetry, tower-32, tower. !
!

Remember that a machine name specifies both the cpu type and the company ! name.

!

Return to the GCC Installation page + + + + diff -Nrcpad gcc-6.3.0/INSTALL/prerequisites.html gcc-6.4.0/INSTALL/prerequisites.html *** gcc-6.3.0/INSTALL/prerequisites.html Wed Dec 21 07:54:10 2016 --- gcc-6.4.0/INSTALL/prerequisites.html Tue Jul 4 07:28:15 2017 *************** *** 1,421 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing 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++98 compiler
!

Necessary to bootstrap GCC, although versions of GCC prior to 4.8 also allow bootstrapping with a ISO C89 compiler and versions of GCC prior to 3.4 also allow bootstrapping with a traditional (K&R) C compiler. !

!

To build all languages in a cross-compiler or other configuration where 3-stage bootstrap is not performed, you need to start with an existing GCC binary (version 3.4 or later) because source code for language frontends other than C might use GCC extensions. !

!

Note that to bootstrap GCC with versions of GCC earlier than 3.4, you ! may need to use --disable-stage1-checking, though bootstrapping the compiler with such earlier compilers is strongly discouraged. !

!
!
C standard library and headers
!
!

In order to build GCC, the C standard library and headers must be present for all target variants for which target libraries will be built (and not only the variant of the host C++ compiler). !

!

This affects the popular ‘x86_64-unknown-linux-gnu’ platform (among ! other multilib targets), for which 64-bit (‘x86_64’) and 32-bit ! (‘i386’) libc headers are usually packaged separately. If you do a ! build of a native compiler on ‘x86_64-unknown-linux-gnu’, make sure you either have the 32-bit libc developer package properly installed (the exact name of the package depends on your distro) or you must build GCC as a 64-bit only compiler by configuring with the option ! --disable-multilib. Otherwise, you may encounter an error such as ! ‘fatal error: gnu/stubs-32.h: No such file’ !

!
!
GNAT
!
!

In order to build the Ada compiler (GNAT) you must already have GNAT installed because portions of the Ada frontend are written in Ada (with GNAT extensions.) Refer to the Ada installation instructions for more specific information. !

!
!
A “working” POSIX compatible shell, or GNU bash
!
!

Necessary when running configure because some ! /bin/sh shells have bugs and may crash when configuring the ! target libraries. In other cases, /bin/sh or ksh have disastrous corner-case performance problems. This ! can cause target configure runs to literally take days to complete in some cases. !

!

So on some platforms /bin/ksh is sufficient, on others it ! isn’t. See the host/target specific instructions for your platform, or ! use bash to be sure. Then set CONFIG_SHELL in your environment to your “good” shell prior to running ! configure/make. !

!

zsh is not a fully compliant POSIX shell and will not work when configuring GCC. !

!
!
A POSIX or SVR4 awk
!
!

Necessary for creating some of the generated source files for GCC. If in doubt, use a recent GNU awk version, as some of the older ones are broken. GNU awk version 3.1.5 is known to work. !

!
!
GNU binutils
!
!

Necessary in some circumstances, optional in others. See the host/target specific instructions for your platform for the exact requirements. !

!
!
gzip version 1.2.4 (or later) or
!
bzip2 version 1.0.2 (or later)
!
!

Necessary to uncompress GCC tar files when source code is obtained via FTP mirror sites. !

!
!
GNU make version 3.80 (or later)
!
!

You must have GNU make installed to build GCC. !

!
!
GNU tar version 1.14 (or later)
!
!

Necessary (only on some platforms) to untar the source code. Many ! systems’ tar programs will also work, only try GNU ! tar if you have problems. !

!
!
Perl version 5.6.1 (or later)
!
!

Necessary when targeting Darwin, building ‘libstdc++’, ! and not using --disable-symvers. ! Necessary when targeting Solaris 2 with Sun ld and not using ! --disable-symvers. The bundled perl in Solaris 8 and up works. !

!

Necessary when regenerating Makefile dependencies in libiberty. ! Necessary when regenerating libiberty/functions.texi. ! Necessary when generating manpages from Texinfo manuals. Used by various scripts to generate some files included in SVN (mainly Unicode-related and rarely changing) from source tables. !

!
!
jar, or InfoZIP (zip and unzip)
!
!

Necessary to build libgcj, the GCJ runtime. !

!
!

Several support libraries are necessary to build GCC, some are required, others optional. While any sufficiently new version of required tools usually work, library requirements are generally stricter. Newer ! versions may work in some cases, but it’s safer to use the exact versions documented. We appreciate bug reports about problems with newer versions, though. If your OS vendor provides packages for the support libraries then using those packages may be the simplest way to install the libraries. !

!
!
GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
!
!

Necessary to build GCC. If a GMP source distribution is found in a ! subdirectory of your GCC sources named gmp, it will be built together with GCC. Alternatively, if GMP is already installed but it is not in your library search path, you will have to configure with the ! --with-gmp configure option. See also --with-gmp-lib ! and --with-gmp-include. !

!
!
MPFR Library version 2.4.2 (or later)
!
!

Necessary to build GCC. It can be downloaded from http://www.mpfr.org/. If an MPFR source distribution is found ! in a subdirectory of your GCC sources named mpfr, it will be built together with GCC. Alternatively, if MPFR is already installed but it is not in your default library search path, the ! --with-mpfr configure option should be used. See also ! --with-mpfr-lib and --with-mpfr-include. !

!
!
MPC Library version 0.8.1 (or later)
!
!

Necessary to build GCC. It can be downloaded from http://www.multiprecision.org/. If an MPC source distribution ! is found in a subdirectory of your GCC sources named mpc, it will be built together with GCC. Alternatively, if MPC is already installed but it is not in your default library search path, the ! --with-mpc configure option should be used. See also ! --with-mpc-lib and --with-mpc-include. !

!
!
isl Library version 0.16, 0.15, or 0.14.
!
!

Necessary to build GCC with the Graphite loop optimizations. ! It can be downloaded from ftp://gcc.gnu.org/pub/gcc/infrastructure/. If an isl source distribution is found ! in a subdirectory of your GCC sources named isl, it will be ! built together with GCC. Alternatively, the --with-isl configure option should be used if isl is not installed in your default library search path. -

-
-
! !

Tools/packages necessary for modifying GCC

!
!
autoconf version 2.64
!
GNU m4 version 1.4.6 (or later)
!
!

Necessary when modifying configure.ac, aclocal.m4, etc. ! to regenerate configure and config.in files. !

!
!
automake version 1.11.6
!
!

Necessary when modifying a Makefile.am file to regenerate its ! associated Makefile.in. !

!

Much of GCC does not use automake, so directly edit the Makefile.in ! file. Specifically this applies to the gcc, intl, ! libcpp, libiberty, libobjc directories as well as any of their subdirectories. !

!

For directories that use automake, GCC requires the latest release in the 1.11 series, which is currently 1.11.6. When regenerating a directory to a newer version, please update all the directories using an older 1.11 to the latest released version. !

!
!
gettext version 0.14.5 (or later)
!
!

Needed to regenerate gcc.pot. !

!
!
gperf version 2.7.2 (or later)
!
!

Necessary when modifying gperf input files, e.g. ! gcc/cp/cfns.gperf to regenerate its associated header file, e.g. ! gcc/cp/cfns.h. !

!
!
DejaGnu 1.4.4
!
Expect
!
Tcl
!
!

Necessary to run the GCC testsuite; see the section on testing for details. Tcl 8.6 has a known regression in RE pattern handling that make parts of the testsuite fail. See http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f for more information. This bug has been fixed in 8.6.1. !

!
!
autogen version 5.5.4 (or later) and
!
guile version 1.4.1 (or later)
!
!

Necessary to regenerate fixinc/fixincl.x from ! fixinc/inclhack.def and fixinc/*.tpl. !

!

Necessary to run ‘make check’ for fixinc. !

!

Necessary to regenerate the top level Makefile.in file from ! Makefile.tpl and Makefile.def. !

!
!
Flex version 2.5.4 (or later)
!
!

Necessary when modifying *.l files. !

!

Necessary to build GCC during development because the generated output files are not included in the SVN repository. They are included in releases. !

!
!
Texinfo version 4.7 (or later)
!
!

Necessary for running makeinfo when modifying *.texi files to test your changes. !

!

Necessary for running make dvi or make pdf to create printable documentation in DVI or PDF format. Texinfo version ! 4.8 or later is required for make pdf. !

!

Necessary to build GCC documentation during development because the generated output files are not included in the SVN repository. They are included in releases. -

-
-
TeX (any working version)
-
-

Necessary for running texi2dvi and texi2pdf, which - are used when running make dvi or make pdf to create - DVI or PDF files, respectively. -

-
-
Sphinx version 1.0 (or later)
-
-

Necessary to regenerate jit/docs/_build/texinfo from the .rst - files in the directories below jit/docs. -

-
-
SVN (any version)
-
SSH (any version)
-
-

Necessary to access the SVN repository. Public releases and weekly - snapshots of the development sources are also available via FTP. -

-
-
GNU diffutils version 2.7 (or later)
-
-

Useful when submitting patches for the GCC source code. -

-
-
patch version 2.5.4 (or later)
-
-

Necessary when applying patches, created with diff, to one’s - own sources. -

-
-
ecj1
-
gjavah
-
-

If you wish to modify .java files in libjava, you will need to - configure with --enable-java-maintainer-mode, and you will need - to have executables named ecj1 and gjavah in your path. - The ecj1 executable should run the Eclipse Java compiler via - the GCC-specific entry point. You can download a suitable jar from - ftp://sourceware.org/pub/java/, or by running the script - contrib/download_ecj. -

-
-
antlr.jar version 2.7.1 (or later)
-
antlr binary
-
-

If you wish to build the gjdoc binary in libjava, you will - need to have an antlr.jar library available. The library is - searched for in system locations but can be specified with - --with-antlr-jar= instead. When configuring with - --enable-java-maintainer-mode, you will need to have one of - the executables named cantlr, runantlr or - antlr in your path. -

-
-
- -
-

-

Return to the GCC Installation page -

- - - - --- 1,310 ---- ! ! ! Prerequisites for GCC ! ! ! ! ! ! ! ! ! !

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++98 compiler
Necessary to bootstrap GCC, although versions of GCC prior to 4.8 also allow bootstrapping with a ISO C89 compiler and versions of GCC prior to 3.4 also allow bootstrapping with a traditional (K&R) C compiler. ! !

To build all languages in a cross-compiler or other configuration where 3-stage bootstrap is not performed, you need to start with an existing GCC binary (version 3.4 or later) because source code for language frontends other than C might use GCC extensions. ! !

Note that to bootstrap GCC with versions of GCC earlier than 3.4, you ! may need to use --disable-stage1-checking, though bootstrapping the compiler with such earlier compilers is strongly discouraged. ! !

C standard library and headers
! In order to build GCC, the C standard library and headers must be present for all target variants for which target libraries will be built (and not only the variant of the host C++ compiler). ! !

This affects the popular ‘x86_64-unknown-linux-gnu’ platform (among ! other multilib targets), for which 64-bit (‘x86_64’) and 32-bit ! (‘i386’) libc headers are usually packaged separately. If you do a ! build of a native compiler on ‘x86_64-unknown-linux-gnu’, make sure you either have the 32-bit libc developer package properly installed (the exact name of the package depends on your distro) or you must build GCC as a 64-bit only compiler by configuring with the option ! --disable-multilib. Otherwise, you may encounter an error such as ! ‘fatal error: gnu/stubs-32.h: No such file’ ! !

GNAT
! In order to build the Ada compiler (GNAT) you must already have GNAT installed because portions of the Ada frontend are written in Ada (with GNAT extensions.) Refer to the Ada installation instructions for more specific information. ! !
A “working” POSIX compatible shell, or GNU bash
! Necessary when running configure because some ! /bin/sh shells have bugs and may crash when configuring the ! target libraries. In other cases, /bin/sh or ksh have disastrous corner-case performance problems. This ! can cause target configure runs to literally take days to complete in some cases. ! !

So on some platforms /bin/ksh is sufficient, on others it ! isn't. See the host/target specific instructions for your platform, or ! use bash to be sure. Then set CONFIG_SHELL in your environment to your “good” shell prior to running ! configure/make. ! !

zsh is not a fully compliant POSIX shell and will not work when configuring GCC. ! !

A POSIX or SVR4 awk
! Necessary for creating some of the generated source files for GCC. If in doubt, use a recent GNU awk version, as some of the older ones are broken. GNU awk version 3.1.5 is known to work. ! !
GNU binutils
! Necessary in some circumstances, optional in others. See the host/target specific instructions for your platform for the exact requirements. ! !
gzip version 1.2.4 (or later) or
bzip2 version 1.0.2 (or later)
! Necessary to uncompress GCC tar files when source code is obtained via FTP mirror sites. ! !
GNU make version 3.80 (or later)
! You must have GNU make installed to build GCC. ! !
GNU tar version 1.14 (or later)
! Necessary (only on some platforms) to untar the source code. Many ! systems' tar programs will also work, only try GNU ! tar if you have problems. ! !
Perl version 5.6.1 (or later)
! Necessary when targeting Darwin, building ‘libstdc++’, ! and not using --disable-symvers. ! Necessary when targeting Solaris 2 with Sun ld and not using ! --disable-symvers. The bundled perl in Solaris 8 and up works. ! !

Necessary when regenerating Makefile dependencies in libiberty. ! Necessary when regenerating libiberty/functions.texi. ! Necessary when generating manpages from Texinfo manuals. Used by various scripts to generate some files included in SVN (mainly Unicode-related and rarely changing) from source tables. ! !

jar, or InfoZIP (zip and unzip)
! Necessary to build libgcj, the GCJ runtime. !
!

Several support libraries are necessary to build GCC, some are required, others optional. While any sufficiently new version of required tools usually work, library requirements are generally stricter. Newer ! versions may work in some cases, but it's safer to use the exact versions documented. We appreciate bug reports about problems with newer versions, though. If your OS vendor provides packages for the support libraries then using those packages may be the simplest way to install the libraries. ! !

!
GNU Multiple Precision Library (GMP) version 4.3.2 (or later)
! Necessary to build GCC. If a GMP source distribution is found in a ! subdirectory of your GCC sources named gmp, it will be built together with GCC. Alternatively, if GMP is already installed but it is not in your library search path, you will have to configure with the ! --with-gmp configure option. See also --with-gmp-lib ! and --with-gmp-include. ! !
MPFR Library version 2.4.2 (or later)
! Necessary to build GCC. It can be downloaded from http://www.mpfr.org/. If an MPFR source distribution is found ! in a subdirectory of your GCC sources named mpfr, it will be built together with GCC. Alternatively, if MPFR is already installed but it is not in your default library search path, the ! --with-mpfr configure option should be used. See also ! --with-mpfr-lib and --with-mpfr-include. ! !
MPC Library version 0.8.1 (or later)
! Necessary to build GCC. It can be downloaded from http://www.multiprecision.org/. If an MPC source distribution ! is found in a subdirectory of your GCC sources named mpc, it will be built together with GCC. Alternatively, if MPC is already installed but it is not in your default library search path, the ! --with-mpc configure option should be used. See also ! --with-mpc-lib and --with-mpc-include. ! !
isl Library version 0.16, 0.15, or 0.14.
! Necessary to build GCC with the Graphite loop optimizations. ! It can be downloaded from ftp://gcc.gnu.org/pub/gcc/infrastructure/. If an isl source distribution is found ! in a subdirectory of your GCC sources named isl, it will be ! built together with GCC. Alternatively, the --with-isl configure option should be used if isl is not installed in your default library search path. !
! !

Tools/packages necessary for modifying GCC

! !
!
autoconf version 2.64
GNU m4 version 1.4.6 (or later)
! Necessary when modifying configure.ac, aclocal.m4, etc. ! to regenerate configure and config.in files. ! !
automake version 1.11.6
! Necessary when modifying a Makefile.am file to regenerate its ! associated Makefile.in. ! !

Much of GCC does not use automake, so directly edit the Makefile.in ! file. Specifically this applies to the gcc, intl, ! libcpp, libiberty, libobjc directories as well as any of their subdirectories. ! !

For directories that use automake, GCC requires the latest release in the 1.11 series, which is currently 1.11.6. When regenerating a directory to a newer version, please update all the directories using an older 1.11 to the latest released version. ! !

gettext version 0.14.5 (or later)
! Needed to regenerate gcc.pot. ! !
gperf version 2.7.2 (or later)
! Necessary when modifying gperf input files, e.g. ! gcc/cp/cfns.gperf to regenerate its associated header file, e.g. ! gcc/cp/cfns.h. ! !
DejaGnu 1.4.4
Expect
Tcl
! Necessary to run the GCC testsuite; see the section on testing for details. Tcl 8.6 has a known regression in RE pattern handling that make parts of the testsuite fail. See http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f for more information. This bug has been fixed in 8.6.1. ! !
autogen version 5.5.4 (or later) and
guile version 1.4.1 (or later)
! Necessary to regenerate fixinc/fixincl.x from ! fixinc/inclhack.def and fixinc/*.tpl. ! !

Necessary to run ‘make check’ for fixinc. ! !

Necessary to regenerate the top level Makefile.in file from ! Makefile.tpl and Makefile.def. ! !

Flex version 2.5.4 (or later)
! Necessary when modifying *.l files. ! !

Necessary to build GCC during development because the generated output files are not included in the SVN repository. They are included in releases. ! !

Texinfo version 4.7 (or later)
! Necessary for running makeinfo when modifying *.texi files to test your changes. ! !

Necessary for running make dvi or make pdf to create printable documentation in DVI or PDF format. Texinfo version ! 4.8 or later is required for make pdf. ! !

Necessary to build GCC documentation during development because the generated output files are not included in the SVN repository. They are included in releases. +

TeX (any working version)
+ Necessary for running texi2dvi and texi2pdf, which + are used when running make dvi or make pdf to create + DVI or PDF files, respectively. +
Sphinx version 1.0 (or later)
+ Necessary to regenerate jit/docs/_build/texinfo from the .rst + files in the directories below jit/docs. +
SVN (any version)
SSH (any version)
+ Necessary to access the SVN repository. Public releases and weekly + snapshots of the development sources are also available via FTP. +
GNU diffutils version 2.7 (or later)
+ Useful when submitting patches for the GCC source code. +
patch version 2.5.4 (or later)
+ Necessary when applying patches, created with diff, to one's + own sources. +
ecj1
gjavah
+ If you wish to modify .java files in libjava, you will need to + configure with --enable-java-maintainer-mode, and you will need + to have executables named ecj1 and gjavah in your path. + The ecj1 executable should run the Eclipse Java compiler via + the GCC-specific entry point. You can download a suitable jar from + ftp://sourceware.org/pub/java/, or by running the script + contrib/download_ecj. +
antlr.jar version 2.7.1 (or later)
antlr binary
+ If you wish to build the gjdoc binary in libjava, you will + need to have an antlr.jar library available. The library is + searched for in system locations but can be specified with + --with-antlr-jar= instead. When configuring with + --enable-java-maintainer-mode, you will need to have one of + the executables named cantlr, runantlr or + antlr in your path. +
+

+

Return to the GCC Installation page + + + + + + + + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/specific.html gcc-6.4.0/INSTALL/specific.html *** gcc-6.3.0/INSTALL/specific.html Wed Dec 21 07:54:09 2016 --- gcc-6.4.0/INSTALL/specific.html Tue Jul 4 07:28:15 2017 *************** *** 1,738 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

Please read this document carefully before installing the GNU Compiler Collection on your machine. !

!

Note that this list of install notes is not a list of supported hosts or targets. Not all supported hosts and targets are listed here, only the ones that require host-specific or target-specific ! information have to. !

! ! ! !
! !

aarch64*-*-*

!

Binutils pre 2.24 does not have support for selecting -mabi and does not support ILP32. If it is used to build GCC 4.9 or later, GCC will ! not support option -mabi=ilp32. !

!

To enable a workaround for the Cortex-A53 erratum number 835769 by default (for all CPUs regardless of -mcpu option given) at configure time use the ! --enable-fix-cortex-a53-835769 option. This will enable the fix by default and can be explicitly disabled during compilation by passing the ! -mno-fix-cortex-a53-835769 option. Conversely, ! --disable-fix-cortex-a53-835769 will disable the workaround by default. The workaround is disabled by default if neither of ! --enable-fix-cortex-a53-835769 or ! --disable-fix-cortex-a53-835769 is given at configure time. !

!

To enable a workaround for the Cortex-A53 erratum number 843419 by default (for all CPUs regardless of -mcpu option given) at configure time use the ! --enable-fix-cortex-a53-843419 option. This workaround is applied at link time. Enabling the workaround will cause GCC to pass the relevant option to the linker. It can be explicitly disabled during compilation by passing the ! -mno-fix-cortex-a53-843419 option. Conversely, ! --disable-fix-cortex-a53-843419 will disable the workaround by default. The workaround is disabled by default if neither of ! --enable-fix-cortex-a53-843419 or ! --disable-fix-cortex-a53-843419 is given at configure time. !

!
! !

alpha*-*-*

This section contains general configuration information for all alpha-based platforms using ELF (in particular, ignore this section for DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this section, please read all other sections that match your target. !

!

We require binutils 2.11.2 or newer. Previous binutils releases had a number of problems with DWARF 2 debugging information, not the least of which is incorrect linking of shared libraries. !

!
! !

alpha*-dec-osf5.1

Systems using processors that implement the DEC Alpha architecture and are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. !

!

Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2, versions before alpha*-dec-osf4 are no longer supported. (These are the versions which identify themselves as DEC OSF/1.) -

-
- -

amd64-*-solaris2.1[0-9]*

-

This is a synonym for ‘x86_64-*-solaris2.1[0-9]*’. -

-
- -

arc-*-elf32

!

Use ‘configure --target=arc-elf32 --with-cpu=cpu --enable-languages="c,c++"’ ! to configure GCC, with cpu being one of ‘arc600’, ‘arc601’, ! or ‘arc700’. !

!
! !

arc-linux-uclibc

-

Use ‘configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"’ to configure GCC. -

-
- -

arm-*-eabi

ARM-family processors. Subtargets that use the ELF object format require GNU binutils 2.13 or newer. Such subtargets include: arm-*-netbsdelf, arm-*-*linux-* and arm-*-rtemseabi. !

!

Building the Ada frontend commonly fails (an infinite loop executing xsinfo) if the host compiler is GNAT 4.8. Host compilers built from the GNAT 4.6, 4.9 or 5 release branches are known to succeed. !

!
! !

avr

ATMEL AVR-family micro controllers. These are used in embedded ! applications. There are no standard Unix configurations. See “AVR Options” in the main manual for the list of supported MCU types. !

!

Use ‘configure --target=avr --enable-languages="c"’ to configure GCC. !

!

Further installation notes and other useful information about AVR tools can also be obtained from: -

- !

We strongly recommend using binutils 2.13 or newer. !

!

The following error: !

! 
Error: register required
!
!

indicates that you should upgrade to a newer version of the binutils. !

!
! !

Blackfin

!

The Blackfin processor, an Analog Devices DSP. See “Blackfin Options” in the main manual !

!

More information, and a version of binutils with support for this processor, is available at http://blackfin.uclinux.org !

!
! !

CR16

The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is used in embedded applications. -

!

See “CR16 Options” in the main manual for a list of CR16-specific options. !

!

Use ‘configure --target=cr16-elf --enable-languages=c,c++’ to configure ! GCC for building a CR16 elf cross-compiler. !

!

Use ‘configure --target=cr16-uclinux --enable-languages=c,c++’ to ! configure GCC for building a CR16 uclinux cross-compiler. !

!
! !

CRIS

CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip series. These are used in embedded applications. !

!

See “CRIS Options” in the main manual for a list of CRIS-specific options. !

!

There are a few different CRIS targets: !

!
cris-axis-elf
!

Mainly for monolithic embedded systems. Includes a multilib for the ! ‘v10’ core used in ‘ETRAX 100 LX’. !

!
cris-axis-linux-gnu
!

A GNU/Linux port for the CRIS architecture, currently targeting ! ‘ETRAX 100 LX’ by default. !

!

For cris-axis-elf you need binutils 2.11 or newer. For cris-axis-linux-gnu you need binutils 2.12 or newer. !

!

Pre-packaged tools can be obtained from ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/. More information about this platform is available at http://developer.axis.com/. !

!
! !

DOS

Please have a look at the binaries page. !

!

You cannot install GCC by itself on MSDOS; it will not compile under any MSDOS compiler except itself. You need to get the complete compilation package DJGPP, which includes binaries as well as sources, and includes all the necessary compilation tools and libraries. !

!
! !

epiphany-*-elf

!

Adapteva Epiphany. This configuration is intended for embedded systems. !

!
! !

*-*-freebsd*

Support for FreeBSD 1 was discontinued in GCC 3.2. Support for FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was discontinued in GCC 4.0. !

!

In order to better utilize FreeBSD base system functionality and match the configuration of the system compiler, GCC 4.5 and above as well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present on FreeBSD 7 or later) and the use of __cxa_atexit by default (on FreeBSD 6 or later). The use of dl_iterate_phdr inside ! libgcc_s.so.1 and boehm-gc (on FreeBSD 7 or later) is enabled by GCC 4.5 and above. !

!

We support FreeBSD using the ELF file format with DWARF 2 debugging ! for all CPU architectures. You may use -gstabs instead of ! -g, if you really want the old debugging format. There are no known issues with mixing object files and libraries with different debugging formats. Otherwise, this release of GCC should now match more of the configuration used in the stock FreeBSD configuration of ! GCC. In particular, --enable-threads is now configured by default. However, as a general user, do not attempt to replace the system compiler with this release. Known to bootstrap and check with good results on FreeBSD 7.2-STABLE. In the past, known to bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and 5-CURRENT. !

!

The version of binutils installed in /usr/bin probably works with this release of GCC. Bootstrapping against the latest GNU ! binutils and/or the version found in /usr/ports/devel/binutils has been known to enable additional features and improve overall testsuite results. However, it is currently known that boehm-gc (which itself is required for java) may not configure properly on FreeBSD prior to the FreeBSD 7.0 release with GNU binutils after 2.16.1. !

!
! !

ft32-*-elf

!

The FT32 processor. This configuration is intended for embedded systems. !

!
! !

h8300-hms

Renesas H8/300 series of processors. !

!

Please have a look at the binaries page. !

!

The calling convention and structure layout has changed in release 2.6. All code must be recompiled. The calling convention now passes the first three arguments in function calls in registers. Structures are no longer a multiple of 2 bytes. !

!
! !

hppa*-hp-hpux*

Support for HP-UX version 9 and older was discontinued in GCC 3.4. !

!

We require using gas/binutils on all hppa platforms. Version 2.19 or later is recommended. !

!

It may be helpful to configure GCC with the ! --with-gnu-as and ! --with-as=… options to ensure that GCC can find GAS. !

!

The HP assembler should not be used with GCC. It is rarely tested and may ! not work. It shouldn’t be used with any languages other than C due to its many limitations. !

!

Specifically, -g does not work (HP-UX uses a peculiar debugging format which GCC does not know about). It also inserts timestamps into each object file it creates, causing the 3-stage comparison test to fail during a bootstrap. You should be able to continue by saying ! ‘make all-host all-target’ after getting the failure from ‘make’. !

!

Various GCC features are not supported. For example, it does not support weak symbols or alias definitions. As a result, explicit template instantiations are required when using C++. This makes it difficult if not impossible to build many C++ applications. !

!

There are two default scheduling models for instructions. These are PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc ! architecture specified for the target machine when configuring. PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when ! the target is a ‘hppa1*’ machine. !

!

The PROCESSOR_8000 model is not well suited to older processors. Thus, it is important to completely specify the machine architecture when configuring if you want a model other than PROCESSOR_8000. The macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different default scheduling model is desired. !

!

As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 ! through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. This namespace change might cause problems when bootstrapping with an earlier version of GCC or the HP compiler as essentially the same namespace is required for an entire build. This problem can be avoided ! in a number of ways. With HP cc, UNIX_STD can be set to ‘95’ ! or ‘98’. Another way is to add an appropriate set of predefines ! to CC. The description for the munix= option contains a list of the predefines used with each standard. !

!

More specific information to ‘hppa*-hp-hpux*’ targets follows. !

!
! !

hppa*-hp-hpux10

For hpux10.20, we highly recommend you pick up the latest sed patch PHCO_19798 from HP. !

!

The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are used for one-only code and data. This resolves many of the previous problems in using C++ on this target. However, the ABI is not compatible with the one implemented under HP-UX 11 using secondary definitions. !

!
! !

hppa*-hp-hpux11

GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot be used to compile GCC 3.0 and up. !

!

The libffi and libjava libraries haven’t been ported to 64-bit HP-UX and don’t build. !

!

Refer to binaries for information about obtaining precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained ! to build the Ada language as it can’t be bootstrapped using C. Ada is only available for the 32-bit PA-RISC runtime. !

!

Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The ! bundled compiler supports only traditional C; you will need either HP’s unbundled compiler, or a binary distribution of GCC. !

!

It is possible to build GCC 3.3 starting with the bundled HP compiler, but the process requires several steps. GCC 3.3 can then be used to build later versions. The fastjar program contains ISO C code and ! can’t be built with the HP bundled compiler. This problem can be avoided by not building the Java language. For example, use the ! --enable-languages="c,c++,f77,objc" option in your configure command. !

!

There are several possible approaches to building the distribution. Binutils can be built first using the HP tools. Then, the GCC distribution can be built. The second approach is to build GCC ! first using the HP tools, then build binutils, then rebuild GCC. There have been problems with various binary distributions, so it is best not to start from a binary distribution. !

!

On 64-bit capable systems, there are two distinct targets. Different installation prefixes must be used if both are to be installed on ! the same system. The ‘hppa[1-2]*-hp-hpux11*’ target generates code ! for the 32-bit PA-RISC runtime architecture and uses the HP linker. ! The ‘hppa64-hp-hpux11*’ target generates 64-bit code for the PA-RISC 2.0 architecture. !

!

The script config.guess now selects the target type based on the compiler ! detected during configuration. You must define PATH or CC so ! that configure finds an appropriate compiler for the initial bootstrap. ! When CC is used, the definition should contain the options that are ! needed whenever CC is used. !

!

Specifically, options that determine the runtime architecture must be ! in CC to correctly select the target for the build. It is also ! convenient to place many other compiler options in CC. For example, ! CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE" can be used to bootstrap the GCC 3.3 branch with the HP compiler in ! 64-bit K&R/bundled mode. The +DA2.0W option will result in ! the automatic selection of the ‘hppa64-hp-hpux11*’ target. The macro definition table of cpp needs to be increased for a successful build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when building with the bundled compiler, or when using the ! -Ac option. These defines aren’t necessary with -Ae. !

!

It is best to explicitly configure the ‘hppa64-hp-hpux11*’ target ! with the --with-ld=… option. This overrides the standard search for ld. The two linkers supported on this target require different commands. The default linker is determined during configuration. As a ! result, it’s not possible to switch linkers in the middle of a GCC build. This has been reported to sometimes occur in unified builds of binutils and GCC. !

!

A recent linker patch must be installed for the correct operation of GCC 3.3 and later. PHSS_26559 and PHSS_24304 are the oldest linker patches that are known to work. They are for HP-UX 11.00 and 11.11, respectively. PHSS_24303, the companion to ! PHSS_24304, might be usable but it hasn’t been tested. These patches have been superseded. Consult the HP patch database to obtain the currently recommended linker patch for your system. !

!

The patches are necessary for the support of weak symbols on the 32-bit port, and for the running of initializers and finalizers. Weak symbols are implemented using SOM secondary definition symbols. Prior ! to HP-UX 11, there are bugs in the linker support for secondary symbols. The patches correct a problem of linker core dumps creating shared libraries containing secondary symbols, as well as various other linking issues involving secondary symbols. !

!

GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to run initializers and finalizers on the 64-bit port. The 32-bit port ! uses the linker +init and +fini options for the same purpose. The patches correct various problems with the +init/+fini options, including program core dumps. Binutils 2.14 corrects a ! problem on the 64-bit port resulting from HP’s non-standard use of the .init and .fini sections for array initializers and finalizers. !

!

Although the HP and GNU linkers are both supported for the ! ‘hppa64-hp-hpux11*’ target, it is strongly recommended that the HP linker be used for link editing on this target. !

!

At this time, the GNU linker does not support the creation of long ! branch stubs. As a result, it can’t successfully link binaries containing branch offsets larger than 8 megabytes. In addition, there are problems linking shared libraries, linking executables ! with -static, and with dwarf2 unwind and exception support. ! It also doesn’t provide stubs for internal calls to global functions ! in shared libraries, so these calls can’t be overloaded. !

!

The HP dynamic loader does not support GNU symbol versioning, so symbol versioning is not supported. It may be necessary to disable symbol ! versioning with --disable-symvers when using GNU ld. !

!

POSIX threads are the default. The optional DCE thread library is not ! supported, so --enable-threads=dce does not work. !

!
! !

*-*-linux-gnu

Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present in glibc 2.2.5 and later. More information is available in the libstdc++-v3 documentation. !

!
! !

i?86-*-linux*

!

As of GCC 3.3, binutils 2.13.1 or later is required for this platform. See bug 10877 for more information. !

!

If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can be found on www.bitwizard.nl. !

!
! !

i?86-*-solaris2.10

Use this for Solaris 10 or later on x86 and x86-64 systems. Starting ! with GCC 4.7, there is also a 64-bit ‘amd64-*-solaris2.1[0-9]*’ or ! ‘x86_64-*-solaris2.1[0-9]*’ configuration that corresponds to ! ‘sparcv9-sun-solaris2*’. !

!

It is recommended that you configure GCC to use the GNU assembler. The versions included in Solaris 10, from GNU binutils 2.15 (in ! /usr/sfw/bin/gas), and Solaris 11, from GNU binutils 2.19 or ! newer (also available as /usr/bin/gas and ! /usr/gnu/bin/as), work fine. Please note that the current version, from GNU binutils 2.26, only works on Solaris 12 when using the Solaris linker. On Solaris 10 and 11, you either have to wait for GNU binutils 2.26.1 or newer, or stay with GNU binutils 2.25.1. Recent ! versions of the Solaris assembler in /usr/ccs/bin/as work almost ! as well, though. !

!

For linking, the Solaris linker, is preferred. If you want to use the GNU linker instead, note that due to a packaging bug the version in Solaris ! 10, from GNU binutils 2.15 (in /usr/sfw/bin/gld), cannot be used, while the version in Solaris 11, from GNU binutils 2.19 or newer (also ! in /usr/gnu/bin/ld and /usr/bin/gld), works, as does the latest version, from GNU binutils 2.26. !

!

To use GNU as, configure with the options ! --with-gnu-as --with-as=/usr/sfw/bin/gas. It may be necessary ! to configure with --without-gnu-ld --with-ld=/usr/ccs/bin/ld to ! guarantee use of Sun ld. !

!
! !

ia64-*-linux

IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux. !

!

If you are using the installed system libunwind library with ! --with-system-libunwind, then you must use libunwind 0.98 or later. !

!

None of the following versions of GCC has an ABI that is compatible with any of the other versions in this list, with the exception that Red Hat 2.96 and Trillian 000171 are compatible with each other: ! 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. ! This primarily affects C++ programs and programs that create shared libraries. ! GCC 3.1 or later is recommended for compiling linux, the kernel. As of version 3.1 GCC is believed to be fully ABI compliant, and hence no more major ABI changes are expected. !

!
! !

ia64-*-hpux*

Building GCC on this target requires the GNU Assembler. The bundled HP assembler will not work. To prevent GCC from using the wrong assembler, ! the option --with-gnu-as may be necessary. !

!

The GCC libunwind library has not been ported to HPUX. This means that for ! GCC versions 3.2.3 and earlier, --enable-libunwind-exceptions ! is required to build GCC. For GCC 3.3 and later, this is the default. ! For gcc 3.4.3 and later, --enable-libunwind-exceptions is removed and the system libunwind library will always be used. !

!
! ! !

*-ibm-aix*

!

Support for AIX version 3 and older was discontinued in GCC 3.4. Support for AIX version 4.2 and older was discontinued in GCC 4.5. !

!

“out of memory” bootstrap failures may indicate a problem with process resource limits (ulimit). Hard limits are configured in the ! /etc/security/limits system configuration file. !

!

GCC 4.9 and above require a C++ compiler for bootstrap. IBM VAC++ / xlC cannot bootstrap GCC. xlc can bootstrap an older version of GCC and G++ can bootstrap recent releases of GCC. !

!

GCC can bootstrap with recent versions of IBM XLC, but bootstrapping with an earlier release of GCC is recommended. Bootstrapping with XLC requires a larger data segment, which can be enabled through the LDR_CNTRL environment variable, e.g., -

-
- 
% LDR_CNTRL=MAXDATA=0x50000000
- % export LDR_CNTRL
-
!

One can start with a pre-compiled version of GCC to build from ! sources. One may delete GCC’s “fixed” header files when starting with a version of GCC built for an earlier release of AIX. -

-

To speed up the configuration phases of bootstrapping and installing GCC, - one may use GNU Bash instead of AIX /bin/sh, e.g., -

-
- 
% CONFIG_SHELL=/opt/freeware/bin/bash
- % export CONFIG_SHELL
-
!

and then proceed as described in the build ! instructions, where we strongly recommend specifying an absolute path to invoke srcdir/configure. !

!

Because GCC on AIX is built as a 32-bit executable by default, (although it can generate 64-bit programs) the GMP and MPFR libraries required by gfortran must be 32-bit libraries. Building GMP and MPFR as static archive libraries works better than shared libraries. !

!

Errors involving alloca when building GCC generally are due to an incorrect definition of CC in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of ! the build, the native AIX compiler must be invoked as cc ! (not xlc). Once configure has been informed of ! xlc, one needs to use ‘make distclean’ to remove the ! configure cache files and ensure that CC environment variable ! does not provide a definition that will confuse configure. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). !

!

The native as and ld are recommended for bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is the minimum level that supports bootstrap on ! AIX 5. The GNU Assembler has not been updated to support AIX 6 or AIX 7. The native AIX tools do interoperate with GCC. !

!

AIX 7.1 added partial support for DWARF debugging, but full support requires AIX 7.1 TL03 SP7 that supports additional DWARF sections and fixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a version of libm.a missing important symbols; a fix for IV77796 will be included in SP6. !

!

AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX assembler change that sometimes produces corrupt assembly files causing AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause compilation failures with existing GCC installations. An --- 1,699 ---- ! ! ! Host/Target specific installation notes for GCC ! ! ! ! ! ! ! ! ! !

Host/Target specific installation notes for GCC

! ! Please read this document carefully before installing the GNU Compiler Collection on your machine. ! !

Note that this list of install notes is not a list of supported hosts or targets. Not all supported hosts and targets are listed here, only the ones that require host-specific or target-specific ! information have to. !

+ !

!

! !

aarch64*-*-*

! !

Binutils pre 2.24 does not have support for selecting -mabi and does not support ILP32. If it is used to build GCC 4.9 or later, GCC will ! not support option -mabi=ilp32. ! !

To enable a workaround for the Cortex-A53 erratum number 835769 by default (for all CPUs regardless of -mcpu option given) at configure time use the ! --enable-fix-cortex-a53-835769 option. This will enable the fix by default and can be explicitly disabled during compilation by passing the ! -mno-fix-cortex-a53-835769 option. Conversely, ! --disable-fix-cortex-a53-835769 will disable the workaround by default. The workaround is disabled by default if neither of ! --enable-fix-cortex-a53-835769 or ! --disable-fix-cortex-a53-835769 is given at configure time. ! !

To enable a workaround for the Cortex-A53 erratum number 843419 by default (for all CPUs regardless of -mcpu option given) at configure time use the ! --enable-fix-cortex-a53-843419 option. This workaround is applied at link time. Enabling the workaround will cause GCC to pass the relevant option to the linker. It can be explicitly disabled during compilation by passing the ! -mno-fix-cortex-a53-843419 option. Conversely, ! --disable-fix-cortex-a53-843419 will disable the workaround by default. The workaround is disabled by default if neither of ! --enable-fix-cortex-a53-843419 or ! --disable-fix-cortex-a53-843419 is given at configure time. ! !

! !

alpha*-*-*

!

This section contains general configuration information for all alpha-based platforms using ELF (in particular, ignore this section for DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this section, please read all other sections that match your target. ! !

We require binutils 2.11.2 or newer. Previous binutils releases had a number of problems with DWARF 2 debugging information, not the least of which is incorrect linking of shared libraries. ! !

! !

alpha*-dec-osf5.1

!

Systems using processors that implement the DEC Alpha architecture and are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. ! !

Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2, versions before alpha*-dec-osf4 are no longer supported. (These are the versions which identify themselves as DEC OSF/1.) !

! !

amd64-*-solaris2.1[0-9]*

! !

This is a synonym for ‘x86_64-*-solaris2.1[0-9]*’. ! !

! !

arc-*-elf32

! !

Use ‘configure --target=arc-elf32 --with-cpu=cpu --enable-languages="c,c++"’ ! to configure GCC, with cpu being one of ‘arc600’, ‘arc601’, ! or ‘arc700’. ! !

! !

arc-linux-uclibc

! !

Use ‘configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"’ to configure GCC. ! !

! !

arm-*-eabi

ARM-family processors. Subtargets that use the ELF object format require GNU binutils 2.13 or newer. Such subtargets include: arm-*-netbsdelf, arm-*-*linux-* and arm-*-rtemseabi. ! !

Building the Ada frontend commonly fails (an infinite loop executing xsinfo) if the host compiler is GNAT 4.8. Host compilers built from the GNAT 4.6, 4.9 or 5 release branches are known to succeed. ! !

! !

avr

!

ATMEL AVR-family micro controllers. These are used in embedded ! applications. There are no standard Unix configurations. See “AVR Options” in the main manual for the list of supported MCU types. ! !

Use ‘configure --target=avr --enable-languages="c"’ to configure GCC. ! !

Further installation notes and other useful information about AVR tools can also be obtained from: !

!

We strongly recommend using binutils 2.13 or newer. ! !

The following error: ! 

     Error: register required
!
!

indicates that you should upgrade to a newer version of the binutils. ! !

! !

Blackfin

! !

The Blackfin processor, an Analog Devices DSP. See “Blackfin Options” in the main manual ! !

More information, and a version of binutils with support for this processor, is available at http://blackfin.uclinux.org ! !

! !

CR16

!

The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is used in embedded applications. !

See “CR16 Options” in the main manual for a list of CR16-specific options. ! !

Use ‘configure --target=cr16-elf --enable-languages=c,c++’ to configure ! GCC for building a CR16 elf cross-compiler. ! !

Use ‘configure --target=cr16-uclinux --enable-languages=c,c++’ to ! configure GCC for building a CR16 uclinux cross-compiler. ! !

! !

CRIS

!

CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip series. These are used in embedded applications. ! !

See “CRIS Options” in the main manual for a list of CRIS-specific options. ! !

There are a few different CRIS targets: !

!
cris-axis-elf
Mainly for monolithic embedded systems. Includes a multilib for the ! ‘v10’ core used in ‘ETRAX 100 LX’. !
cris-axis-linux-gnu
A GNU/Linux port for the CRIS architecture, currently targeting ! ‘ETRAX 100 LX’ by default.
!

For cris-axis-elf you need binutils 2.11 or newer. For cris-axis-linux-gnu you need binutils 2.12 or newer. ! !

Pre-packaged tools can be obtained from ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/. More information about this platform is available at http://developer.axis.com/. ! !

! !

DOS

!

Please have a look at the binaries page. ! !

You cannot install GCC by itself on MSDOS; it will not compile under any MSDOS compiler except itself. You need to get the complete compilation package DJGPP, which includes binaries as well as sources, and includes all the necessary compilation tools and libraries. ! !

! !

epiphany-*-elf

! !

Adapteva Epiphany. This configuration is intended for embedded systems. ! !

! !

*-*-freebsd*

!

Support for FreeBSD 1 was discontinued in GCC 3.2. Support for FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was discontinued in GCC 4.0. ! !

In order to better utilize FreeBSD base system functionality and match the configuration of the system compiler, GCC 4.5 and above as well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present on FreeBSD 7 or later) and the use of __cxa_atexit by default (on FreeBSD 6 or later). The use of dl_iterate_phdr inside ! libgcc_s.so.1 and boehm-gc (on FreeBSD 7 or later) is enabled by GCC 4.5 and above. ! !

We support FreeBSD using the ELF file format with DWARF 2 debugging ! for all CPU architectures. You may use -gstabs instead of ! -g, if you really want the old debugging format. There are no known issues with mixing object files and libraries with different debugging formats. Otherwise, this release of GCC should now match more of the configuration used in the stock FreeBSD configuration of ! GCC. In particular, --enable-threads is now configured by default. However, as a general user, do not attempt to replace the system compiler with this release. Known to bootstrap and check with good results on FreeBSD 7.2-STABLE. In the past, known to bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and 5-CURRENT. ! !

The version of binutils installed in /usr/bin probably works with this release of GCC. Bootstrapping against the latest GNU ! binutils and/or the version found in /usr/ports/devel/binutils has been known to enable additional features and improve overall testsuite results. However, it is currently known that boehm-gc (which itself is required for java) may not configure properly on FreeBSD prior to the FreeBSD 7.0 release with GNU binutils after 2.16.1. ! !

! !

ft32-*-elf

! !

The FT32 processor. This configuration is intended for embedded systems. ! !

! !

h8300-hms

!

Renesas H8/300 series of processors. ! !

Please have a look at the binaries page. ! !

The calling convention and structure layout has changed in release 2.6. All code must be recompiled. The calling convention now passes the first three arguments in function calls in registers. Structures are no longer a multiple of 2 bytes. ! !

! !

hppa*-hp-hpux*

!

Support for HP-UX version 9 and older was discontinued in GCC 3.4. ! !

We require using gas/binutils on all hppa platforms. Version 2.19 or later is recommended. ! !

It may be helpful to configure GCC with the ! --with-gnu-as and ! --with-as=... options to ensure that GCC can find GAS. ! !

The HP assembler should not be used with GCC. It is rarely tested and may ! not work. It shouldn't be used with any languages other than C due to its many limitations. ! !

Specifically, -g does not work (HP-UX uses a peculiar debugging format which GCC does not know about). It also inserts timestamps into each object file it creates, causing the 3-stage comparison test to fail during a bootstrap. You should be able to continue by saying ! ‘make all-host all-target’ after getting the failure from ‘make’. ! !

Various GCC features are not supported. For example, it does not support weak symbols or alias definitions. As a result, explicit template instantiations are required when using C++. This makes it difficult if not impossible to build many C++ applications. ! !

There are two default scheduling models for instructions. These are PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc ! architecture specified for the target machine when configuring. PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when ! the target is a ‘hppa1*’ machine. ! !

The PROCESSOR_8000 model is not well suited to older processors. Thus, it is important to completely specify the machine architecture when configuring if you want a model other than PROCESSOR_8000. The macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different default scheduling model is desired. ! !

As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 ! through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. This namespace change might cause problems when bootstrapping with an earlier version of GCC or the HP compiler as essentially the same namespace is required for an entire build. This problem can be avoided ! in a number of ways. With HP cc, UNIX_STD can be set to ‘95’ ! or ‘98’. Another way is to add an appropriate set of predefines ! to CC. The description for the munix= option contains a list of the predefines used with each standard. ! !

More specific information to ‘hppa*-hp-hpux*’ targets follows. ! !

! !

hppa*-hp-hpux10

!

For hpux10.20, we highly recommend you pick up the latest sed patch PHCO_19798 from HP. ! !

The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are used for one-only code and data. This resolves many of the previous problems in using C++ on this target. However, the ABI is not compatible with the one implemented under HP-UX 11 using secondary definitions. ! !

! !

hppa*-hp-hpux11

!

GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot be used to compile GCC 3.0 and up. ! !

The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build. ! !

Refer to binaries for information about obtaining precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained ! to build the Ada language as it can't be bootstrapped using C. Ada is only available for the 32-bit PA-RISC runtime. ! !

Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The ! bundled compiler supports only traditional C; you will need either HP's unbundled compiler, or a binary distribution of GCC. ! !

It is possible to build GCC 3.3 starting with the bundled HP compiler, but the process requires several steps. GCC 3.3 can then be used to build later versions. The fastjar program contains ISO C code and ! can't be built with the HP bundled compiler. This problem can be avoided by not building the Java language. For example, use the ! --enable-languages="c,c++,f77,objc" option in your configure command. ! !

There are several possible approaches to building the distribution. Binutils can be built first using the HP tools. Then, the GCC distribution can be built. The second approach is to build GCC ! first using the HP tools, then build binutils, then rebuild GCC. There have been problems with various binary distributions, so it is best not to start from a binary distribution. ! !

On 64-bit capable systems, there are two distinct targets. Different installation prefixes must be used if both are to be installed on ! the same system. The ‘hppa[1-2]*-hp-hpux11*’ target generates code ! for the 32-bit PA-RISC runtime architecture and uses the HP linker. ! The ‘hppa64-hp-hpux11*’ target generates 64-bit code for the PA-RISC 2.0 architecture. ! !

The script config.guess now selects the target type based on the compiler ! detected during configuration. You must define PATH or CC so ! that configure finds an appropriate compiler for the initial bootstrap. ! When CC is used, the definition should contain the options that are ! needed whenever CC is used. ! !

Specifically, options that determine the runtime architecture must be ! in CC to correctly select the target for the build. It is also ! convenient to place many other compiler options in CC. For example, ! CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE" can be used to bootstrap the GCC 3.3 branch with the HP compiler in ! 64-bit K&R/bundled mode. The +DA2.0W option will result in ! the automatic selection of the ‘hppa64-hp-hpux11*’ target. The macro definition table of cpp needs to be increased for a successful build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when building with the bundled compiler, or when using the ! -Ac option. These defines aren't necessary with -Ae. ! !

It is best to explicitly configure the ‘hppa64-hp-hpux11*’ target ! with the --with-ld=... option. This overrides the standard search for ld. The two linkers supported on this target require different commands. The default linker is determined during configuration. As a ! result, it's not possible to switch linkers in the middle of a GCC build. This has been reported to sometimes occur in unified builds of binutils and GCC. ! !

A recent linker patch must be installed for the correct operation of GCC 3.3 and later. PHSS_26559 and PHSS_24304 are the oldest linker patches that are known to work. They are for HP-UX 11.00 and 11.11, respectively. PHSS_24303, the companion to ! PHSS_24304, might be usable but it hasn't been tested. These patches have been superseded. Consult the HP patch database to obtain the currently recommended linker patch for your system. ! !

The patches are necessary for the support of weak symbols on the 32-bit port, and for the running of initializers and finalizers. Weak symbols are implemented using SOM secondary definition symbols. Prior ! to HP-UX 11, there are bugs in the linker support for secondary symbols. The patches correct a problem of linker core dumps creating shared libraries containing secondary symbols, as well as various other linking issues involving secondary symbols. ! !

GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to run initializers and finalizers on the 64-bit port. The 32-bit port ! uses the linker +init and +fini options for the same purpose. The patches correct various problems with the +init/+fini options, including program core dumps. Binutils 2.14 corrects a ! problem on the 64-bit port resulting from HP's non-standard use of the .init and .fini sections for array initializers and finalizers. ! !

Although the HP and GNU linkers are both supported for the ! ‘hppa64-hp-hpux11*’ target, it is strongly recommended that the HP linker be used for link editing on this target. ! !

At this time, the GNU linker does not support the creation of long ! branch stubs. As a result, it can't successfully link binaries containing branch offsets larger than 8 megabytes. In addition, there are problems linking shared libraries, linking executables ! with -static, and with dwarf2 unwind and exception support. ! It also doesn't provide stubs for internal calls to global functions ! in shared libraries, so these calls can't be overloaded. ! !

The HP dynamic loader does not support GNU symbol versioning, so symbol versioning is not supported. It may be necessary to disable symbol ! versioning with --disable-symvers when using GNU ld. ! !

POSIX threads are the default. The optional DCE thread library is not ! supported, so --enable-threads=dce does not work. ! !

! !

*-*-linux-gnu

!

Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present in glibc 2.2.5 and later. More information is available in the libstdc++-v3 documentation. ! !

! !

i?86-*-linux*

! !

As of GCC 3.3, binutils 2.13.1 or later is required for this platform. See bug 10877 for more information. ! !

If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can be found on www.bitwizard.nl. ! !

! !

i?86-*-solaris2.10

!

Use this for Solaris 10 or later on x86 and x86-64 systems. Starting ! with GCC 4.7, there is also a 64-bit ‘amd64-*-solaris2.1[0-9]*’ or ! ‘x86_64-*-solaris2.1[0-9]*’ configuration that corresponds to ! ‘sparcv9-sun-solaris2*’. ! !

It is recommended that you configure GCC to use the GNU assembler. The versions included in Solaris 10, from GNU binutils 2.15 (in ! /usr/sfw/bin/gas), and Solaris 11, from GNU binutils 2.19 or ! newer (also available as /usr/bin/gas and ! /usr/gnu/bin/as), work fine. Please note that the current version, from GNU binutils 2.26, only works on Solaris 12 when using the Solaris linker. On Solaris 10 and 11, you either have to wait for GNU binutils 2.26.1 or newer, or stay with GNU binutils 2.25.1. Recent ! versions of the Solaris assembler in /usr/ccs/bin/as work almost ! as well, though. ! ! !

For linking, the Solaris linker, is preferred. If you want to use the GNU linker instead, note that due to a packaging bug the version in Solaris ! 10, from GNU binutils 2.15 (in /usr/sfw/bin/gld), cannot be used, while the version in Solaris 11, from GNU binutils 2.19 or newer (also ! in /usr/gnu/bin/ld and /usr/bin/gld), works, as does the latest version, from GNU binutils 2.26. ! !

To use GNU as, configure with the options ! --with-gnu-as --with-as=/usr/sfw/bin/gas. It may be necessary ! to configure with --without-gnu-ld --with-ld=/usr/ccs/bin/ld to ! guarantee use of Sun ld. ! ! !

! !

ia64-*-linux

!

IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux. ! !

If you are using the installed system libunwind library with ! --with-system-libunwind, then you must use libunwind 0.98 or later. ! !

None of the following versions of GCC has an ABI that is compatible with any of the other versions in this list, with the exception that Red Hat 2.96 and Trillian 000171 are compatible with each other: ! 3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. ! This primarily affects C++ programs and programs that create shared libraries. ! GCC 3.1 or later is recommended for compiling linux, the kernel. As of version 3.1 GCC is believed to be fully ABI compliant, and hence no more major ABI changes are expected. ! !

! !

ia64-*-hpux*

!

Building GCC on this target requires the GNU Assembler. The bundled HP assembler will not work. To prevent GCC from using the wrong assembler, ! the option --with-gnu-as may be necessary. ! !

The GCC libunwind library has not been ported to HPUX. This means that for ! GCC versions 3.2.3 and earlier, --enable-libunwind-exceptions ! is required to build GCC. For GCC 3.3 and later, this is the default. ! For gcc 3.4.3 and later, --enable-libunwind-exceptions is removed and the system libunwind library will always be used. ! !

! ! !

*-ibm-aix*

! !

Support for AIX version 3 and older was discontinued in GCC 3.4. Support for AIX version 4.2 and older was discontinued in GCC 4.5. ! !

“out of memory” bootstrap failures may indicate a problem with process resource limits (ulimit). Hard limits are configured in the ! /etc/security/limits system configuration file. ! !

GCC 4.9 and above require a C++ compiler for bootstrap. IBM VAC++ / xlC cannot bootstrap GCC. xlc can bootstrap an older version of GCC and G++ can bootstrap recent releases of GCC. ! !

GCC can bootstrap with recent versions of IBM XLC, but bootstrapping with an earlier release of GCC is recommended. Bootstrapping with XLC requires a larger data segment, which can be enabled through the LDR_CNTRL environment variable, e.g., ! 

     % LDR_CNTRL=MAXDATA=0x50000000
!      % export LDR_CNTRL
!
!

One can start with a pre-compiled version of GCC to build from ! sources. One may delete GCC's “fixed” header files when starting with a version of GCC built for an earlier release of AIX. !

To speed up the configuration phases of bootstrapping and installing GCC, ! one may use GNU Bash instead of AIX /bin/sh, e.g., ! ! 

     % CONFIG_SHELL=/opt/freeware/bin/bash
!      % export CONFIG_SHELL
!
!

and then proceed as described in the build instructions, where we strongly recommend specifying an absolute path to invoke srcdir/configure. ! !

Because GCC on AIX is built as a 32-bit executable by default, (although it can generate 64-bit programs) the GMP and MPFR libraries required by gfortran must be 32-bit libraries. Building GMP and MPFR as static archive libraries works better than shared libraries. ! !

Errors involving alloca when building GCC generally are due to an incorrect definition of CC in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of ! the build, the native AIX compiler must be invoked as cc ! (not xlc). Once configure has been informed of ! xlc, one needs to use ‘make distclean’ to remove the ! configure cache files and ensure that CC environment variable ! does not provide a definition that will confuse configure. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). ! !

The native as and ld are recommended for bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is the minimum level that supports bootstrap on ! AIX 5. The GNU Assembler has not been updated to support AIX 6 or AIX 7. The native AIX tools do interoperate with GCC. ! !

AIX 7.1 added partial support for DWARF debugging, but full support requires AIX 7.1 TL03 SP7 that supports additional DWARF sections and fixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a version of libm.a missing important symbols; a fix for IV77796 will be included in SP6. ! !

AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX assembler change that sometimes produces corrupt assembly files causing AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause compilation failures with existing GCC installations. An *************** AIX iFix for AIX 5.3 is available (APAR *** 740,1500 **** IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix. !

!

Building libstdc++.a requires a fix for an AIX Assembler bug APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix for another AIX Assembler bug and a co-dependent AIX Archiver fix referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1) !

!

‘libstdc++’ in GCC 3.4 increments the major version number of the ! shared object and GCC installation places the libstdc++.a shared library in a common location which will overwrite the and GCC 3.3 version of the shared library. Applications either need to be re-linked against the new shared library or the GCC 3.1 and GCC 3.3 ! versions of the ‘libstdc++’ shared object needs to be available ! to the AIX runtime loader. The GCC 3.1 ‘libstdc++.so.4’, if ! present, and GCC 3.3 ‘libstdc++.so.5’ shared objects can be installed for runtime dynamic loading using the following steps to set ! the ‘F_LOADONLY’ flag in the shared object for each ! multilib libstdc++.a installed: !

!

Extract the shared objects from the currently installed ! libstdc++.a archive: !

! 
% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
!
!

Enable the ‘F_LOADONLY’ flag so that the shared object will be available for runtime dynamic loading, but not linking: !

! 
% strip -e libstdc++.so.4 libstdc++.so.5
!
! !

Archive the runtime-only shared object in the GCC 3.4 ! libstdc++.a archive: !

! 
% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
!
! !

Eventually, the ! --with-aix-soname=svr4 configure option may drop the need for this procedure for libraries that support it. !

!

Linking executables and shared libraries may produce warnings of duplicate symbols. The assembly files generated by GCC for AIX always have included multiple symbol definitions for certain global variable and function declarations in the original program. The warnings should not prevent the linker from producing a correct library or runnable executable. !

!

AIX 4.3 utilizes a “large format” archive to support both 32-bit and 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 ! to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during linking such as “not a COFF file”. The version of the routines shipped ! with AIX 4.3.1 should work for a 32-bit environment. The -g option of the archive command may be used to create archives of 32-bit objects using the original “small format”. A correct version of the routines is shipped with AIX 4.3.2 and above. !

!

Some versions of the AIX binder (linker) can fail with a relocation ! overflow severe error when the -bbigtoc option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U455193. !

!

The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for APAR IX87327 is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. !

!

The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. !

!

AIX provides National Language Support (NLS). Compilers and assemblers use NLS to support locale-specific representations of various data ! formats including floating-point numbers (e.g., ‘.’ vs ‘,’ for separating decimal fractions). There have been problems reported where GCC does not produce the same floating-point formats that the assembler ! expects. If one encounters this problem, set the LANG ! environment variable to ‘C’ or ‘En_US’. !

!

A default can be specified with the -mcpu=cpu_type ! switch and using the configure option --with-cpu-cpu_type. !

!
! !

iq2000-*-elf

Vitesse IQ2000 processors. These are used in embedded applications. There are no standard Unix configurations. !

!
! !

lm32-*-elf

!

Lattice Mico32 processor. This configuration is intended for embedded systems. !

!
! !

lm32-*-uclinux

!

Lattice Mico32 processor. This configuration is intended for embedded systems running uClinux. !

!
! !

m32c-*-elf

!

Renesas M32C processor. This configuration is intended for embedded systems. !

!
! !

m32r-*-elf

!

Renesas M32R processor. This configuration is intended for embedded systems. !

!
! !

m68k-*-*

By default, ! ‘m68k-*-elf*’, ‘m68k-*-rtems’, ‘m68k-*-uclinux’ and ! ‘m68k-*-linux’ build libraries for both M680x0 and ColdFire processors. If you only need the M680x0 libraries, you can omit the ColdFire ones by passing ! --with-arch=m68k to configure. Alternatively, you ! can omit the M680x0 libraries by passing --with-arch=cf to ! configure. These targets default to 5206 or 5475 code as appropriate for the target system when ! configured with --with-arch=cf and 68020 code otherwise. !

!

The ‘m68k-*-netbsd’ and ! ‘m68k-*-openbsd’ targets also support the --with-arch option. They will generate ColdFire CFV4e code when configured with ! --with-arch=cf and 68020 code otherwise. !

!

You can override the default processors listed above by configuring ! with --with-cpu=target. This target can either ! be a -mcpu argument or one of the following values: ! ‘m68000’, ‘m68010’, ‘m68020’, ‘m68030’, ! ‘m68040’, ‘m68060’, ‘m68020-40’ and ‘m68020-60’. !

!

GCC requires at least binutils version 2.17 on these targets. !

!
! !

m68k-*-uclinux

GCC 4.3 changed the uClinux configuration so that it uses the ! ‘m68k-linux-gnu’ ABI rather than the ‘m68k-elf’ ABI. It also added improved support for C++ and flat shared libraries, both of which were ABI changes. !

!
! !

mep-*-elf

!

Toshiba Media embedded Processor. This configuration is intended for embedded systems. !

!
! !

microblaze-*-elf

!

Xilinx MicroBlaze processor. This configuration is intended for embedded systems. !

!
! !

mips-*-*

If on a MIPS system you get an error message saying “does not have gp ! sections for all it’s [sic] sectons [sic]”, don’t worry about it. This happens whenever you use GAS with the MIPS linker, but there is not really anything wrong, and it is okay to use the output file. You can stop such warnings by installing the GNU linker. !

!

It would be nice to extend GAS to produce the gp tables, but they are optional, and there should not be a warning about their absence. !

!

The libstdc++ atomic locking routines for MIPS targets requires MIPS II and later. A patch went in just after the GCC 3.3 release to ! make ‘mips*-*-*’ use the generic implementation instead. You can also ! configure for ‘mipsel-elf’ as a workaround. The ! ‘mips*-*-linux*’ target continues to use the MIPS II routines. More work on this is expected in future releases. -

!

The built-in __sync_* functions are available on MIPS II and ! later systems and others that support the ‘ll’, ‘sc’ and ! ‘sync’ instructions. This can be overridden by passing ! --with-llsc or --without-llsc when configuring GCC. Since the Linux kernel emulates these instructions if they are ! missing, the default for ‘mips*-*-linux*’ targets is ! --with-llsc. The --with-llsc and ! --without-llsc configure options may be overridden at compile ! time by passing the -mllsc or -mno-llsc options to the compiler. !

!

MIPS systems check for division by zero (unless ! -mno-check-zero-division is passed to the compiler) by generating either a conditional trap or a break instruction. Using trap results in smaller code, but is only supported on MIPS II and later. Also, some versions of the Linux kernel have a bug that prevents trap from generating the proper signal (SIGFPE). To enable ! the use of break, use the --with-divide=breaks ! configure option when configuring GCC. The default is to use traps on systems that support them. !

!

The assembler from GNU binutils 2.17 and earlier has a bug in the way it sorts relocations for REL targets (o32, o64, EABI). This can cause bad code to be generated for simple C++ programs. Also the linker from GNU binutils versions prior to 2.17 has a bug which causes the ! runtime linker stubs in very large programs, like libgcj.so, to be incorrectly generated. GNU Binutils 2.18 and later (and snapshots made after Nov. 9, 2006) should be free from both of these problems. !

!
! !

mips-sgi-irix5

Support for IRIX 5 has been removed in GCC 4.6. !

!
! !

mips-sgi-irix6

Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6 releases before 6.5 has been removed in GCC 4.6, as well as support for the O32 ABI. !

!
! !

moxie-*-elf

The moxie processor. !

!
! !

msp430-*-elf

!

TI MSP430 processor. This configuration is intended for embedded systems. !

!
! !

nds32le-*-elf

Andes NDS32 target in little endian mode. !

!
! !

nds32be-*-elf

Andes NDS32 target in big endian mode. !

!
! !

nvptx-*-none

Nvidia PTX target. !

!

Instead of GNU binutils, you will need to install ! nvptx-tools. Tell GCC where to find it: ! --with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin. !

!

A nvptx port of newlib is available at ! nvptx-newlib. It can be automatically built together with GCC. For this, add a ! symbolic link to nvptx-newlib’s newlib directory to the directory containing the GCC sources. !

!

Use the --disable-sjlj-exceptions and ! --enable-newlib-io-long-long options when configuring. !

!
! !

powerpc-*-*

!

You can specify a default version for the -mcpu=cpu_type ! switch by using the configure option --with-cpu-cpu_type. !

!

You will need binutils 2.15 or newer for a working GCC. !

!
! !

powerpc-*-darwin*

PowerPC running Darwin (Mac OS X kernel). !

!

Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool binaries are available at http://opensource.apple.com/. !

!

This version of GCC requires at least cctools-590.36. The cctools-590.36 package referenced from http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html will not work on systems older than 10.3.9 (aka darwin7.9.0). !

!
! !

powerpc-*-elf

PowerPC system in big endian mode, running System V.4. !

!
! !

powerpc*-*-linux-gnu*

PowerPC system in big endian mode running Linux. !

!
! !

powerpc-*-netbsd*

PowerPC system in big endian mode running NetBSD. !

!
! !

powerpc-*-eabisim

Embedded PowerPC system in big endian mode for use in running under the PSIM simulator. !

!
! !

powerpc-*-eabi

Embedded PowerPC system in big endian mode. !

!
! !

powerpcle-*-elf

PowerPC system in little endian mode, running System V.4. !

!
! !

powerpcle-*-eabisim

Embedded PowerPC system in little endian mode for use in running under the PSIM simulator. !

!
! !

powerpcle-*-eabi

Embedded PowerPC system in little endian mode. !

!
! !

rl78-*-elf

!

The Renesas RL78 processor. This configuration is intended for embedded systems. !

!
! !

rx-*-elf

The Renesas RX processor. See http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series for more information about this processor. !

!
! !

s390-*-linux*

S/390 system running GNU/Linux for S/390. !

!
! !

s390x-*-linux*

zSeries system (64-bit) running GNU/Linux for zSeries. !

!
! !

s390x-ibm-tpf*

zSeries system (64-bit) running TPF. This platform is supported as cross-compilation target only. !

!
! !

*-*-solaris2*

Support for Solaris 9 has been removed in GCC 5. Support for Solaris 8 has been removed in GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6. !

!

Sun does not ship a C compiler with Solaris 2 before Solaris 10, though you can download the Sun Studio compilers for free. In Solaris 10 and ! 11, GCC 3.4.3 is available as /usr/sfw/bin/gcc. Solaris 11 also provides GCC 4.5.2, 4.7.3, and 4.8.2 as ! /usr/gcc/4.5/bin/gcc or similar. Alternatively, you can install a pre-built GCC to bootstrap and install GCC. See the binaries page for details. !

!

The Solaris 2 /bin/sh will often fail to configure ! ‘libstdc++-v3’, ‘boehm-gc’ or ‘libjava’. We therefore recommend using the following initial sequence of commands -

-
- 
% CONFIG_SHELL=/bin/ksh
- % export CONFIG_SHELL
-
!

and proceed as described in the configure instructions. In addition we strongly recommend specifying an absolute path to invoke ! srcdir/configure. !

!

Solaris 10 comes with a number of optional OS packages. Some of these are needed to use GCC fully, namely SUNWarc, SUNWbtool, SUNWesu, SUNWhea, SUNWlibm, SUNWsprot, and SUNWtoo. If you did not install all optional packages when installing Solaris 10, you will need to verify that ! the packages that GCC needs are installed. To check whether an optional package is installed, use ! the pkginfo command. To add an optional package, use the ! pkgadd command. For further details, see the Solaris 10 documentation. !

!

Starting with Solaris 11, the package management has changed, so you need to check for system/header, system/linker, and developer/assembler packages. Checking for and installing ! packages is done with the pkg command now. !

!

Trying to use the linker and other tools in ! /usr/ucb to install GCC has been observed to cause trouble. For example, the linker may hang indefinitely. The fix is to remove ! /usr/ucb from your PATH. !

!

The build process works more smoothly with the legacy Sun tools so, if you ! have /usr/xpg4/bin in your PATH, we recommend that you place ! /usr/bin before /usr/xpg4/bin for the duration of the build. !

!

We recommend the use of the Solaris assembler or the GNU assembler, in ! conjunction with the Solaris linker. The GNU as versions included in Solaris 10, from GNU binutils 2.15 (in ! /usr/sfw/bin/gas), and Solaris 11, ! from GNU binutils 2.19 or newer (also in /usr/bin/gas and ! /usr/gnu/bin/as), are known to work. Current versions of GNU binutils (2.26) are known to work as well, with the caveat mentioned in i?86-*-solaris2.10 . Note that your mileage may vary if you use a combination of the GNU tools and the Solaris tools: while the ! combination GNU as + Sun ld should reasonably work, ! the reverse combination Sun as + GNU ld may fail to ! build or cause memory corruption at runtime in some cases for C++ programs. ! GNU ld usually works as well, although the version included in Solaris 10 cannot be used due to several bugs. Again, the current version (2.26) is known to work, but generally lacks platform specific ! features, so better stay with Solaris ld. To use the LTO linker ! plugin (-fuse-linker-plugin) with GNU ld, GNU ! binutils must be configured with --enable-largefile. !

!

To enable symbol versioning in ‘libstdc++’ with the Solaris linker, ! you need to have any version of GNU c++filt, which is part of ! GNU binutils. ‘libstdc++’ symbol versioning will be disabled if no ! appropriate version is found. Solaris c++filt from the Solaris Studio compilers does not work. !

!

GNU make version 3.81 or later is required to build libjava with the Solaris linker. !

!

Sun bug 4927647 sometimes causes random spurious testsuite failures ! related to missing diagnostic output. This bug doesn’t affect GCC ! itself, rather it is a kernel bug triggered by the expect program which is used only by the GCC testsuite driver. When the bug ! causes the expect program to miss anticipated output, extra testsuite failures appear. !

!
! !

sparc*-*-*

This section contains general configuration information for all SPARC-based platforms. In addition to reading this section, please read all other sections that match your target. !

!

Newer versions of the GNU Multiple Precision Library (GMP), the MPFR library and the MPC library are known to be miscompiled by earlier versions of GCC on these platforms. We therefore recommend the use of the exact versions of these libraries listed as minimal versions in the prerequisites. !

!
! !

sparc-sun-solaris2*

When GCC is configured to use GNU binutils 2.14 or later, the binaries ! produced are smaller than the ones produced using Sun’s native tools; this difference is quite significant for binaries containing debugging information. !

!

Starting with Solaris 7, the operating system is capable of executing 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports ! this; the -m64 option enables 64-bit code generation. However, if all you want is code tuned for the UltraSPARC CPU, you ! should try the -mtune=ultrasparc option instead, which produces code that, unlike full 64-bit code, can still run on non-UltraSPARC machines. !

!

When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library on a Solaris 7 or later system, the canonical ! target triplet must be specified as the build parameter on the ! configure line. This target triplet can be obtained by invoking ./config.guess in the toplevel source directory of GCC (and not that of GMP or MPFR or MPC). For example on a Solaris 9 system: -

-
- 
% ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
-
!
! !

sparc-sun-solaris2.10

There is a bug in older versions of the Sun assembler which breaks thread-local storage (TLS). A typical error message is -

-
- 
ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
-   symbol <unknown>: bad symbol type SECT: symbol type must be TLS
-
!

This bug is fixed in Sun patch 118683-03 or later. !

!
! !

sparc-*-linux*

GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or newer on this platform. All earlier binutils and glibc releases mishandled unaligned relocations on sparc-*-* targets. -

!
! !

sparc64-*-solaris2*

When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library, the canonical target triplet must be specified ! as the build parameter on the configure line. For example on a Solaris 9 system: -

-
- 
% ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
-
!
! !

sparcv9-*-solaris2*

!

This is a synonym for ‘sparc64-*-solaris2*’. !

!
! !

c6x-*-*

The C6X family of processors. This port requires binutils-2.22 or newer. !

!
! !

tilegx-*-linux*

The TILE-Gx processor in little endian mode, running GNU/Linux. This port requires binutils-2.22 or newer. !

!
! !

tilegxbe-*-linux*

The TILE-Gx processor in big endian mode, running GNU/Linux. This port requires binutils-2.23 or newer. !

!
! !

tilepro-*-linux*

The TILEPro processor running GNU/Linux. This port requires binutils-2.22 or newer. !

!
! !

visium-*-elf

!

CDS VISIUMcore processor. This configuration is intended for embedded systems. !

!
! !

*-*-vxworks*

Support for VxWorks is in flux. At present GCC supports only the ! very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. ! We welcome patches for other architectures supported by VxWorks 5.5. Support for VxWorks AE would also be welcome; we believe this is merely a matter of writing an appropriate “configlette” (see below). We are not interested in supporting older, a.out or COFF-based, versions of VxWorks in GCC 3. !

!

VxWorks comes with an older version of GCC installed in ! $WIND_BASE/host; we recommend you do not overwrite it. ! Choose an installation prefix entirely outside $WIND_BASE. ! Before running configure, create the directories prefix ! and prefix/bin. Link or copy the appropriate assembler, ! linker, etc. into prefix/bin, and set your PATH to ! include that directory while running both configure and ! make. !

!

You must give configure the ! --with-headers=$WIND_BASE/target/h switch so that it can find the VxWorks system headers. Since VxWorks is a cross compilation ! target only, you must also specify --target=target. ! configure will attempt to create the directory ! prefix/target/sys-include and copy files into it; ! make sure the user running configure has sufficient privilege to do so. !

!

GCC’s exception handling runtime requires a special “configlette” ! module, contrib/gthr_supp_vxw_5x.c. Follow the instructions in that file to add the module to your kernel build. (Future versions of VxWorks will incorporate this module.) !

!
! !

x86_64-*-*, amd64-*-*

GCC supports the x86-64 architecture implemented by the AMD64 processor ! (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. On GNU/Linux the default is a bi-arch compiler which is able to generate ! both 64-bit x86-64 and 32-bit x86 code (via the -m32 switch). !

!
! !

x86_64-*-solaris2.1[0-9]*

GCC also supports the x86-64 architecture implemented by the AMD64 ! processor (‘amd64-*-*’ is an alias for ‘x86_64-*-*’) on Solaris 10 or later. Unlike other systems, without special options a bi-arch compiler is built which generates 32-bit code by default, but ! can generate 64-bit x86-64 code with the -m64 switch. Since GCC 4.7, there is also a configuration that defaults to 64-bit code, but ! can generate 32-bit code with -m32. To configure and build ! this way, you have to provide all support libraries like libgmp ! as 64-bit code, configure with --target=x86_64-pc-solaris2.1x ! and ‘CC=gcc -m64’. !

!
! !

xtensa*-*-elf

This target is intended for embedded Xtensa systems using the ! ‘newlib’ C library. It uses ELF but does not support shared objects. Designed-defined instructions specified via the Tensilica Instruction Extension (TIE) language are only supported through inline assembly. !

!

The Xtensa configuration information must be specified prior to ! building GCC. The include/xtensa-config.h header file contains the configuration information. If you created your own Xtensa configuration with the Xtensa Processor Generator, the downloaded files include a customized copy of this header file, which you can use to replace the default header file. !

!
! !

xtensa*-*-linux*

This target is for Xtensa systems running GNU/Linux. It supports ELF shared objects and the GNU C library (glibc). It also generates position-independent code (PIC) regardless of whether the ! -fpic or -fPIC options are used. In other respects, this target is the same as the ! ‘xtensa*-*-elf’ target. !

!
! !

Microsoft Windows

- -

Intel 16-bit versions

The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not supported. !

!

However, the 32-bit port has limited support for Microsoft Windows 3.11 in the Win32s environment, as a target only. See below. !

! !

Intel 32-bit versions

The 32-bit versions of Windows, including Windows 95, Windows NT, Windows XP, and Windows Vista, are supported by several different target platforms. These targets differ in which Windows subsystem they target and which C libraries are used. -

- ! !

Intel 64-bit versions

GCC contains support for x86-64 using the mingw-w64 ! runtime library, available from http://mingw-w64.sourceforge.net/. This library should be used with the target triple x86_64-pc-mingw32. !

!

Presently Windows for Itanium is not supported. !

! !

Windows CE

Windows CE is supported as a target only on Hitachi SuperH (sh-wince-pe), and MIPS (mips-wince-pe). !

! !

Other Windows Platforms

GCC no longer supports Windows NT on the Alpha or PowerPC. !

!

GCC no longer supports the Windows POSIX subsystem. However, it does support the Interix subsystem. See above. !

!

Old target names including *-*-winnt and *-*-windowsnt are no longer used. !

!

PW32 (i386-pc-pw32) support was never completed, and the project seems to be inactive. See http://pw32.sourceforge.net/ for more information. !

!

UWIN support has been removed due to a lack of maintenance. !

!
! !

*-*-cygwin

Ports of GCC are included with the Cygwin environment. !

!

GCC will build under Cygwin without modification; it does not build ! with Microsoft’s C++ compiler and there are no plans to make it do so. !

!

The Cygwin native compiler can be configured to target any 32-bit x86 cpu architecture desired; the default is i686-pc-cygwin. It should be used with as up-to-date a version of binutils as possible; use either the latest official GNU binutils release in the Cygwin distribution, or version 2.20 or above if building your own. !

!
! !

*-*-interix

The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), and Subsystem for UNIX-based Applications (SUA). Applications compiled with this target run in the Interix subsystem, which is separate from the Win32 subsystem. This target was last known to work in GCC 3.3. !

!
! !

*-*-mingw32

!

GCC will build with and support only MinGW runtime 3.12 and later. Earlier versions of headers are incompatible with the new default semantics of extern inline in -std=c99 and -std=gnu99 modes. !

!
! !

Older systems

GCC contains support files for many older (1980s and early 1990s) Unix variants. For the most part, support for these systems has not been deliberately removed, but it has not been maintained for several years and may suffer from bitrot. !

!

Starting with GCC 3.1, each release has a list of “obsoleted” systems. Support for these systems is still present in that release, but ! configure will fail unless the --enable-obsolete option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC. !

!

Support for old systems as hosts for GCC can cause problems if the workarounds for compiler, library and operating system bugs affect the cleanliness or maintainability of the rest of GCC. In some cases, to bring GCC up on such a system, if still possible with current GCC, may require first installing an old version of GCC which did work on that system, and using it to compile a more recent GCC, to avoid bugs in the vendor compiler. Old releases of GCC 1 and GCC 2 are available in the ! old-releases directory on the GCC mirror ! sites. Header bugs may generally be avoided using ! fixincludes, but bugs or deficiencies in libraries and the operating system may still cause problems. !

!

Support for older systems as targets for cross-compilation is less problematic than support for them as hosts for GCC; if an enthusiast wishes to make such a target work again (including resurrecting any of the targets that never worked with GCC 2, starting from the last --- 701,1503 ---- IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix. ! !

Building libstdc++.a requires a fix for an AIX Assembler bug APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix for another AIX Assembler bug and a co-dependent AIX Archiver fix referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1) ! !

‘libstdc++’ in GCC 3.4 increments the major version number of the ! shared object and GCC installation places the libstdc++.a shared library in a common location which will overwrite the and GCC 3.3 version of the shared library. Applications either need to be re-linked against the new shared library or the GCC 3.1 and GCC 3.3 ! versions of the ‘libstdc++’ shared object needs to be available ! to the AIX runtime loader. The GCC 3.1 ‘libstdc++.so.4’, if ! present, and GCC 3.3 ‘libstdc++.so.5’ shared objects can be installed for runtime dynamic loading using the following steps to set ! the ‘F_LOADONLY’ flag in the shared object for each ! multilib libstdc++.a installed: !

Extract the shared objects from the currently installed ! libstdc++.a archive: ! 

     % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
!
!

Enable the ‘F_LOADONLY’ flag so that the shared object will be available for runtime dynamic loading, but not linking: ! 

     % strip -e libstdc++.so.4 libstdc++.so.5
!
!

Archive the runtime-only shared object in the GCC 3.4 ! libstdc++.a archive: ! 

     % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
!
!

Eventually, the ! --with-aix-soname=svr4 configure option may drop the need for this procedure for libraries that support it. ! !

Linking executables and shared libraries may produce warnings of duplicate symbols. The assembly files generated by GCC for AIX always have included multiple symbol definitions for certain global variable and function declarations in the original program. The warnings should not prevent the linker from producing a correct library or runnable executable. ! !

AIX 4.3 utilizes a “large format” archive to support both 32-bit and 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 ! to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during linking such as “not a COFF file”. The version of the routines shipped ! with AIX 4.3.1 should work for a 32-bit environment. The -g option of the archive command may be used to create archives of 32-bit objects using the original “small format”. A correct version of the routines is shipped with AIX 4.3.2 and above. ! !

Some versions of the AIX binder (linker) can fail with a relocation ! overflow severe error when the -bbigtoc option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U455193. ! !

The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for APAR IX87327 is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. ! !

The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. ! !

AIX provides National Language Support (NLS). Compilers and assemblers use NLS to support locale-specific representations of various data ! formats including floating-point numbers (e.g., ‘.’ vs ‘,’ for separating decimal fractions). There have been problems reported where GCC does not produce the same floating-point formats that the assembler ! expects. If one encounters this problem, set the LANG ! environment variable to ‘C’ or ‘En_US’. ! !

A default can be specified with the -mcpu=cpu_type ! switch and using the configure option --with-cpu-cpu_type. ! !

! !

iq2000-*-elf

!

Vitesse IQ2000 processors. These are used in embedded applications. There are no standard Unix configurations. ! !

! !

lm32-*-elf

! !

Lattice Mico32 processor. This configuration is intended for embedded systems. ! !

! !

lm32-*-uclinux

! !

Lattice Mico32 processor. This configuration is intended for embedded systems running uClinux. ! !

! !

m32c-*-elf

! !

Renesas M32C processor. This configuration is intended for embedded systems. ! !

! !

m32r-*-elf

! !

Renesas M32R processor. This configuration is intended for embedded systems. ! !

! !

m68k-*-*

!

By default, ! ‘m68k-*-elf*’, ‘m68k-*-rtems’, ‘m68k-*-uclinux’ and ! ‘m68k-*-linux’ build libraries for both M680x0 and ColdFire processors. If you only need the M680x0 libraries, you can omit the ColdFire ones by passing ! --with-arch=m68k to configure. Alternatively, you ! can omit the M680x0 libraries by passing --with-arch=cf to ! configure. These targets default to 5206 or 5475 code as appropriate for the target system when ! configured with --with-arch=cf and 68020 code otherwise. ! !

The ‘m68k-*-netbsd’ and ! ‘m68k-*-openbsd’ targets also support the --with-arch option. They will generate ColdFire CFV4e code when configured with ! --with-arch=cf and 68020 code otherwise. ! !

You can override the default processors listed above by configuring ! with --with-cpu=target. This target can either ! be a -mcpu argument or one of the following values: ! ‘m68000’, ‘m68010’, ‘m68020’, ‘m68030’, ! ‘m68040’, ‘m68060’, ‘m68020-40’ and ‘m68020-60’. ! !

GCC requires at least binutils version 2.17 on these targets. ! !

! !

m68k-*-uclinux

!

GCC 4.3 changed the uClinux configuration so that it uses the ! ‘m68k-linux-gnu’ ABI rather than the ‘m68k-elf’ ABI. It also added improved support for C++ and flat shared libraries, both of which were ABI changes. ! !

! !

mep-*-elf

! !

Toshiba Media embedded Processor. This configuration is intended for embedded systems. ! !

! !

microblaze-*-elf

! !

Xilinx MicroBlaze processor. This configuration is intended for embedded systems. ! !

! !

mips-*-*

!

If on a MIPS system you get an error message saying “does not have gp ! sections for all it's [sic] sectons [sic]”, don't worry about it. This happens whenever you use GAS with the MIPS linker, but there is not really anything wrong, and it is okay to use the output file. You can stop such warnings by installing the GNU linker. ! !

It would be nice to extend GAS to produce the gp tables, but they are optional, and there should not be a warning about their absence. ! !

The libstdc++ atomic locking routines for MIPS targets requires MIPS II and later. A patch went in just after the GCC 3.3 release to ! make ‘mips*-*-*’ use the generic implementation instead. You can also ! configure for ‘mipsel-elf’ as a workaround. The ! ‘mips*-*-linux*’ target continues to use the MIPS II routines. More work on this is expected in future releases. ! ! !

The built-in __sync_* functions are available on MIPS II and ! later systems and others that support the ‘ll’, ‘sc’ and ! ‘sync’ instructions. This can be overridden by passing ! --with-llsc or --without-llsc when configuring GCC. Since the Linux kernel emulates these instructions if they are ! missing, the default for ‘mips*-*-linux*’ targets is ! --with-llsc. The --with-llsc and ! --without-llsc configure options may be overridden at compile ! time by passing the -mllsc or -mno-llsc options to the compiler. ! !

MIPS systems check for division by zero (unless ! -mno-check-zero-division is passed to the compiler) by generating either a conditional trap or a break instruction. Using trap results in smaller code, but is only supported on MIPS II and later. Also, some versions of the Linux kernel have a bug that prevents trap from generating the proper signal (SIGFPE). To enable ! the use of break, use the --with-divide=breaks ! configure option when configuring GCC. The default is to use traps on systems that support them. ! !

The assembler from GNU binutils 2.17 and earlier has a bug in the way it sorts relocations for REL targets (o32, o64, EABI). This can cause bad code to be generated for simple C++ programs. Also the linker from GNU binutils versions prior to 2.17 has a bug which causes the ! runtime linker stubs in very large programs, like libgcj.so, to be incorrectly generated. GNU Binutils 2.18 and later (and snapshots made after Nov. 9, 2006) should be free from both of these problems. ! !

! !

mips-sgi-irix5

!

Support for IRIX 5 has been removed in GCC 4.6. ! !

! !

mips-sgi-irix6

!

Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6 releases before 6.5 has been removed in GCC 4.6, as well as support for the O32 ABI. ! !

! !

moxie-*-elf

!

The moxie processor. ! !

! !

msp430-*-elf

! !

TI MSP430 processor. This configuration is intended for embedded systems. ! !

! !

nds32le-*-elf

!

Andes NDS32 target in little endian mode. ! !

! !

nds32be-*-elf

!

Andes NDS32 target in big endian mode. ! !

! !

nvptx-*-none

!

Nvidia PTX target. ! !

Instead of GNU binutils, you will need to install ! nvptx-tools. Tell GCC where to find it: ! --with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin. ! !

A nvptx port of newlib is available at ! nvptx-newlib. It can be automatically built together with GCC. For this, add a ! symbolic link to nvptx-newlib's newlib directory to the directory containing the GCC sources. ! !

Use the --disable-sjlj-exceptions and ! --enable-newlib-io-long-long options when configuring. ! !

! !

powerpc-*-*

! !

You can specify a default version for the -mcpu=cpu_type ! switch by using the configure option --with-cpu-cpu_type. ! !

You will need binutils 2.15 or newer for a working GCC. ! !

! !

powerpc-*-darwin*

!

PowerPC running Darwin (Mac OS X kernel). ! !

Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool binaries are available at http://opensource.apple.com/. ! !

This version of GCC requires at least cctools-590.36. The cctools-590.36 package referenced from http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html will not work on systems older than 10.3.9 (aka darwin7.9.0). ! !

! !

powerpc-*-elf

!

PowerPC system in big endian mode, running System V.4. ! !

! !

powerpc*-*-linux-gnu*

!

PowerPC system in big endian mode running Linux. ! !

! !

powerpc-*-netbsd*

!

PowerPC system in big endian mode running NetBSD. ! !

! !

powerpc-*-eabisim

!

Embedded PowerPC system in big endian mode for use in running under the PSIM simulator. ! !

! !

powerpc-*-eabi

!

Embedded PowerPC system in big endian mode. ! !

! !

powerpcle-*-elf

!

PowerPC system in little endian mode, running System V.4. ! !

! !

powerpcle-*-eabisim

!

Embedded PowerPC system in little endian mode for use in running under the PSIM simulator. ! !

! !

powerpcle-*-eabi

!

Embedded PowerPC system in little endian mode. ! !

! !

rl78-*-elf

! !

The Renesas RL78 processor. This configuration is intended for embedded systems. ! !

! !

rx-*-elf

!

The Renesas RX processor. See http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series for more information about this processor. ! !

! !

s390-*-linux*

!

S/390 system running GNU/Linux for S/390. ! !

! !

s390x-*-linux*

!

zSeries system (64-bit) running GNU/Linux for zSeries. ! !

! !

s390x-ibm-tpf*

!

zSeries system (64-bit) running TPF. This platform is supported as cross-compilation target only. ! !

! ! ! ! ! !

*-*-solaris2*

!

Support for Solaris 9 has been removed in GCC 5. Support for Solaris 8 has been removed in GCC 4.8. Support for Solaris 7 has been removed in GCC 4.6. ! !

Sun does not ship a C compiler with Solaris 2 before Solaris 10, though you can download the Sun Studio compilers for free. In Solaris 10 and ! 11, GCC 3.4.3 is available as /usr/sfw/bin/gcc. Solaris 11 also provides GCC 4.5.2, 4.7.3, and 4.8.2 as ! /usr/gcc/4.5/bin/gcc or similar. Alternatively, you can install a pre-built GCC to bootstrap and install GCC. See the binaries page for details. ! !

The Solaris 2 /bin/sh will often fail to configure ! ‘libstdc++-v3’, ‘boehm-gc’ or ‘libjava’. We therefore recommend using the following initial sequence of commands ! 

     % CONFIG_SHELL=/bin/ksh
!      % export CONFIG_SHELL
!
!

and proceed as described in the configure instructions. In addition we strongly recommend specifying an absolute path to invoke ! srcdir/configure. ! !

Solaris 10 comes with a number of optional OS packages. Some of these are needed to use GCC fully, namely SUNWarc, SUNWbtool, SUNWesu, SUNWhea, SUNWlibm, SUNWsprot, and SUNWtoo. If you did not install all optional packages when installing Solaris 10, you will need to verify that ! the packages that GCC needs are installed. To check whether an optional package is installed, use ! the pkginfo command. To add an optional package, use the ! pkgadd command. For further details, see the Solaris 10 documentation. ! !

Starting with Solaris 11, the package management has changed, so you need to check for system/header, system/linker, and developer/assembler packages. Checking for and installing ! packages is done with the pkg command now. ! !

Trying to use the linker and other tools in ! /usr/ucb to install GCC has been observed to cause trouble. For example, the linker may hang indefinitely. The fix is to remove ! /usr/ucb from your PATH. ! !

The build process works more smoothly with the legacy Sun tools so, if you ! have /usr/xpg4/bin in your PATH, we recommend that you place ! /usr/bin before /usr/xpg4/bin for the duration of the build. ! !

We recommend the use of the Solaris assembler or the GNU assembler, in ! conjunction with the Solaris linker. The GNU as versions included in Solaris 10, from GNU binutils 2.15 (in ! /usr/sfw/bin/gas), and Solaris 11, ! from GNU binutils 2.19 or newer (also in /usr/bin/gas and ! /usr/gnu/bin/as), are known to work. Current versions of GNU binutils (2.26) are known to work as well, with the caveat mentioned in i?86-*-solaris2.10 . Note that your mileage may vary if you use a combination of the GNU tools and the Solaris tools: while the ! combination GNU as + Sun ld should reasonably work, ! the reverse combination Sun as + GNU ld may fail to ! build or cause memory corruption at runtime in some cases for C++ programs. ! ! GNU ld usually works as well, although the version included in Solaris 10 cannot be used due to several bugs. Again, the current version (2.26) is known to work, but generally lacks platform specific ! features, so better stay with Solaris ld. To use the LTO linker ! plugin (-fuse-linker-plugin) with GNU ld, GNU ! binutils must be configured with --enable-largefile. ! !

To enable symbol versioning in ‘libstdc++’ with the Solaris linker, ! you need to have any version of GNU c++filt, which is part of ! GNU binutils. ‘libstdc++’ symbol versioning will be disabled if no ! appropriate version is found. Solaris c++filt from the Solaris Studio compilers does not work. ! !

GNU make version 3.81 or later is required to build libjava with the Solaris linker. ! !

Sun bug 4927647 sometimes causes random spurious testsuite failures ! related to missing diagnostic output. This bug doesn't affect GCC ! itself, rather it is a kernel bug triggered by the expect program which is used only by the GCC testsuite driver. When the bug ! causes the expect program to miss anticipated output, extra testsuite failures appear. ! !

! !

sparc*-*-*

!

This section contains general configuration information for all SPARC-based platforms. In addition to reading this section, please read all other sections that match your target. ! !

Newer versions of the GNU Multiple Precision Library (GMP), the MPFR library and the MPC library are known to be miscompiled by earlier versions of GCC on these platforms. We therefore recommend the use of the exact versions of these libraries listed as minimal versions in the prerequisites. ! !

! !

sparc-sun-solaris2*

!

When GCC is configured to use GNU binutils 2.14 or later, the binaries ! produced are smaller than the ones produced using Sun's native tools; this difference is quite significant for binaries containing debugging information. ! !

Starting with Solaris 7, the operating system is capable of executing 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports ! this; the -m64 option enables 64-bit code generation. However, if all you want is code tuned for the UltraSPARC CPU, you ! should try the -mtune=ultrasparc option instead, which produces code that, unlike full 64-bit code, can still run on non-UltraSPARC machines. ! !

When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library on a Solaris 7 or later system, the canonical ! target triplet must be specified as the build parameter on the ! configure line. This target triplet can be obtained by invoking ./config.guess in the toplevel source directory of GCC (and not that of GMP or MPFR or MPC). For example on a Solaris 9 system: ! 

     % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
!
!

! !

sparc-sun-solaris2.10

!

There is a bug in older versions of the Sun assembler which breaks thread-local storage (TLS). A typical error message is ! 

     ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
!        symbol <unknown>: bad symbol type SECT: symbol type must be TLS
!
!

This bug is fixed in Sun patch 118683-03 or later. ! !

! !

sparc-*-linux*

GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or newer on this platform. All earlier binutils and glibc releases mishandled unaligned relocations on sparc-*-* targets. !

! !

sparc64-*-solaris2*

!

When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library, the canonical target triplet must be specified ! as the build parameter on the configure line. For example on a Solaris 9 system: ! 

     % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
!
!

! !

sparcv9-*-solaris2*

! !

This is a synonym for ‘sparc64-*-solaris2*’. ! !

! !

c6x-*-*

!

The C6X family of processors. This port requires binutils-2.22 or newer. ! !

! !

tilegx-*-linux*

!

The TILE-Gx processor in little endian mode, running GNU/Linux. This port requires binutils-2.22 or newer. ! !

! !

tilegxbe-*-linux*

!

The TILE-Gx processor in big endian mode, running GNU/Linux. This port requires binutils-2.23 or newer. ! !

! !

tilepro-*-linux*

!

The TILEPro processor running GNU/Linux. This port requires binutils-2.22 or newer. ! !

! !

visium-*-elf

! !

CDS VISIUMcore processor. This configuration is intended for embedded systems. ! !

! !

*-*-vxworks*

!

Support for VxWorks is in flux. At present GCC supports only the ! very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. ! We welcome patches for other architectures supported by VxWorks 5.5. Support for VxWorks AE would also be welcome; we believe this is merely a matter of writing an appropriate “configlette” (see below). We are not interested in supporting older, a.out or COFF-based, versions of VxWorks in GCC 3. ! !

VxWorks comes with an older version of GCC installed in ! $WIND_BASE/host; we recommend you do not overwrite it. ! Choose an installation prefix entirely outside $WIND_BASE. ! Before running configure, create the directories prefix ! and prefix/bin. Link or copy the appropriate assembler, ! linker, etc. into prefix/bin, and set your PATH to ! include that directory while running both configure and ! make. ! !

You must give configure the ! --with-headers=$WIND_BASE/target/h switch so that it can find the VxWorks system headers. Since VxWorks is a cross compilation ! target only, you must also specify --target=target. ! configure will attempt to create the directory ! prefix/target/sys-include and copy files into it; ! make sure the user running configure has sufficient privilege to do so. ! !

GCC's exception handling runtime requires a special “configlette” ! module, contrib/gthr_supp_vxw_5x.c. Follow the instructions in that file to add the module to your kernel build. (Future versions of VxWorks will incorporate this module.) ! !

! !

x86_64-*-*, amd64-*-*

!

GCC supports the x86-64 architecture implemented by the AMD64 processor ! (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. On GNU/Linux the default is a bi-arch compiler which is able to generate ! both 64-bit x86-64 and 32-bit x86 code (via the -m32 switch). ! !

! !

x86_64-*-solaris2.1[0-9]*

!

GCC also supports the x86-64 architecture implemented by the AMD64 ! processor (‘amd64-*-*’ is an alias for ‘x86_64-*-*’) on Solaris 10 or later. Unlike other systems, without special options a bi-arch compiler is built which generates 32-bit code by default, but ! can generate 64-bit x86-64 code with the -m64 switch. Since GCC 4.7, there is also a configuration that defaults to 64-bit code, but ! can generate 32-bit code with -m32. To configure and build ! this way, you have to provide all support libraries like libgmp ! as 64-bit code, configure with --target=x86_64-pc-solaris2.1x ! and ‘CC=gcc -m64’. ! !

! !

xtensa*-*-elf

!

This target is intended for embedded Xtensa systems using the ! ‘newlib’ C library. It uses ELF but does not support shared objects. Designed-defined instructions specified via the Tensilica Instruction Extension (TIE) language are only supported through inline assembly. ! !

The Xtensa configuration information must be specified prior to ! building GCC. The include/xtensa-config.h header file contains the configuration information. If you created your own Xtensa configuration with the Xtensa Processor Generator, the downloaded files include a customized copy of this header file, which you can use to replace the default header file. ! !

! !

xtensa*-*-linux*

!

This target is for Xtensa systems running GNU/Linux. It supports ELF shared objects and the GNU C library (glibc). It also generates position-independent code (PIC) regardless of whether the ! -fpic or -fPIC options are used. In other respects, this target is the same as the ! ‘xtensa*-*-elf’ target. ! !

! !

Microsoft Windows

! !

Intel 16-bit versions

The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not supported. ! !

However, the 32-bit port has limited support for Microsoft Windows 3.11 in the Win32s environment, as a target only. See below. ! !

Intel 32-bit versions

!

The 32-bit versions of Windows, including Windows 95, Windows NT, Windows XP, and Windows Vista, are supported by several different target platforms. These targets differ in which Windows subsystem they target and which C libraries are used. !

! !

Intel 64-bit versions

!

GCC contains support for x86-64 using the mingw-w64 ! runtime library, available from http://mingw-w64.sourceforge.net/. This library should be used with the target triple x86_64-pc-mingw32. ! !

Presently Windows for Itanium is not supported. ! !

Windows CE

!

Windows CE is supported as a target only on Hitachi SuperH (sh-wince-pe), and MIPS (mips-wince-pe). ! !

Other Windows Platforms

!

GCC no longer supports Windows NT on the Alpha or PowerPC. ! !

GCC no longer supports the Windows POSIX subsystem. However, it does support the Interix subsystem. See above. ! !

Old target names including *-*-winnt and *-*-windowsnt are no longer used. ! !

PW32 (i386-pc-pw32) support was never completed, and the project seems to be inactive. See http://pw32.sourceforge.net/ for more information. ! !

UWIN support has been removed due to a lack of maintenance. ! !

! !

*-*-cygwin

!

Ports of GCC are included with the Cygwin environment. ! !

GCC will build under Cygwin without modification; it does not build ! with Microsoft's C++ compiler and there are no plans to make it do so. ! !

The Cygwin native compiler can be configured to target any 32-bit x86 cpu architecture desired; the default is i686-pc-cygwin. It should be used with as up-to-date a version of binutils as possible; use either the latest official GNU binutils release in the Cygwin distribution, or version 2.20 or above if building your own. ! !

! !

*-*-interix

!

The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), and Subsystem for UNIX-based Applications (SUA). Applications compiled with this target run in the Interix subsystem, which is separate from the Win32 subsystem. This target was last known to work in GCC 3.3. ! !

! !

*-*-mingw32

! !

GCC will build with and support only MinGW runtime 3.12 and later. Earlier versions of headers are incompatible with the new default semantics of extern inline in -std=c99 and -std=gnu99 modes. ! !

! !

Older systems

!

GCC contains support files for many older (1980s and early 1990s) Unix variants. For the most part, support for these systems has not been deliberately removed, but it has not been maintained for several years and may suffer from bitrot. ! !

Starting with GCC 3.1, each release has a list of “obsoleted” systems. Support for these systems is still present in that release, but ! configure will fail unless the --enable-obsolete option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC. ! !

Support for old systems as hosts for GCC can cause problems if the workarounds for compiler, library and operating system bugs affect the cleanliness or maintainability of the rest of GCC. In some cases, to bring GCC up on such a system, if still possible with current GCC, may require first installing an old version of GCC which did work on that system, and using it to compile a more recent GCC, to avoid bugs in the vendor compiler. Old releases of GCC 1 and GCC 2 are available in the ! old-releases directory on the GCC mirror sites. Header bugs may generally be avoided using ! fixincludes, but bugs or deficiencies in libraries and the operating system may still cause problems. ! !

Support for older systems as targets for cross-compilation is less problematic than support for them as hosts for GCC; if an enthusiast wishes to make such a target work again (including resurrecting any of the targets that never worked with GCC 2, starting from the last *************** version before they were removed), patch *** 1502,1535 **** following the usual requirements would be likely to be accepted, since they should not affect the support for more modern targets. !

!

For some systems, old versions of GNU binutils may also be useful, ! and are available from pub/binutils/old-releases on sourceware.org mirror sites. !

!

Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems (which may no longer be applicable to current GCC) is to be found in the GCC texinfo manual. !

!
! !

all ELF targets (SVR4, Solaris 2, etc.)

C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically. -

!
!

Return to the GCC Installation page -

- - - - - - --- 1505,1535 ---- following the usual requirements would be likely to be accepted, since they should not affect the support for more modern targets. ! !

For some systems, old versions of GNU binutils may also be useful, ! and are available from pub/binutils/old-releases on sourceware.org mirror sites. ! !

Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems (which may no longer be applicable to current GCC) is to be found in the GCC texinfo manual. ! !

! !

all ELF targets (SVR4, Solaris 2, etc.)

!

C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically. !

Return to the GCC Installation page + + + + + diff -Nrcpad gcc-6.3.0/INSTALL/test.html gcc-6.4.0/INSTALL/test.html *** gcc-6.3.0/INSTALL/test.html Wed Dec 21 07:54:11 2016 --- gcc-6.4.0/INSTALL/test.html Tue Jul 4 07:28:15 2017 *************** *** 1,315 **** ! ! ! ! ! ! Installing GCC ! ! ! ! ! ! ! ! ! ! ! ! !

Installing GCC

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the ! gcc-testresults mailing list. Some of these archived results are linked from the build status lists at http://gcc.gnu.org/buildstat.html, although not everyone who ! reports a successful build runs the testsuites and submits the results. This step is optional and may require you to download additional software, but it can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC. !

!

First, you must have downloaded the testsuites. These are part of the full distribution, but if you downloaded the “core” compiler plus any front ends, you must download the testsuites separately. !

!

Second, you must have the testing tools installed. This includes DejaGnu, Tcl, and Expect; the DejaGnu site has links to these. !

!

If the directories where runtest and expect were ! installed are not in the PATH, you may need to set the following environment variables appropriately, as in the following example (which ! assumes that DejaGnu has been installed under /usr/local): !

!
! 
TCL_LIBRARY = /usr/local/share/tcl8.0
! DEJAGNULIBS = /usr/local/share/dejagnu
!
!

(On systems such as Cygwin, these paths are required to be actual paths, not mounts or links; presumably this is due to some lack of portability in the DejaGnu code.) -

- -

Finally, you can run the testsuite (which may take a long time): -

- 
cd objdir; make -k check
-
!

This will test various components of GCC, such as compiler front ends and runtime libraries. While running the testsuite, DejaGnu might emit some harmless messages resembling ! ‘WARNING: Couldn't find the global config file.’ or ! ‘WARNING: Couldn't find tool init file’ that can be ignored. !

!

If you are testing a cross-compiler, you may want to run the testsuite on a simulator as described at http://gcc.gnu.org/simtest-howto.html. !

! !

How can you run the testsuite on selected tests?

In order to run sets of tests selectively, there are targets ! ‘make check-gcc’ and language specific ‘make check-c’, ! ‘make check-c++’, ‘make check-fortran’, ‘make check-java’, ! ‘make check-ada’, ‘make check-objc’, ‘make check-obj-c++’, ! ‘make check-lto’ ! in the gcc subdirectory of the object directory. You can also ! just run ‘make check’ in a subdirectory of the object directory. !

!

A more selective way to just run all gcc execute tests in the testsuite is to use -

-
- 
make check-gcc RUNTESTFLAGS="execute.exp other-options"
-
!

Likewise, in order to run only the g++ “old-deja” tests in ! the testsuite with filenames matching ‘9805*’, you would use !

!
! 
make check-g++ RUNTESTFLAGS="old-deja.exp=9805* other-options"
!
!

The *.exp files are located in the testsuite directories of the GCC ! source, the most important ones being compile.exp, ! execute.exp, dg.exp and old-deja.exp. ! To get a list of the possible *.exp files, pipe the ! output of ‘make check’ into a file and look at the ! ‘Running … .exp’ lines. !

! !

Passing options and running multiple testsuites

You can pass multiple options to the testsuite using the ! ‘--target_board’ option of DejaGNU, either passed as part of ! ‘RUNTESTFLAGS’, or directly to runtest if you prefer to work outside the makefiles. For example, -

-
- 
make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
-
!

will run the standard g++ testsuites (“unix” is the target name for a standard native testsuite situation), passing ! ‘-O3 -fmerge-constants’ to the compiler on every test, i.e., slashes separate options. !

!

You can run the testsuites multiple times using combinations of options with a syntax similar to the brace expansion of popular shells: -

-
- 
…"--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}"
-
!

(Note the empty option caused by the trailing comma in the final group.) ! The following will run each testsuite eight times using the ‘arm-sim’ target, as if you had specified all possible combinations yourself: -

-
- 
--target_board='arm-sim/-mhard-float/-O1 \
-                 arm-sim/-mhard-float/-O2 \
-                 arm-sim/-mhard-float/-O3 \
-                 arm-sim/-mhard-float \
-                 arm-sim/-msoft-float/-O1 \
-                 arm-sim/-msoft-float/-O2 \
-                 arm-sim/-msoft-float/-O3 \
-                 arm-sim/-msoft-float'
-
!

They can be combined as many times as you wish, in arbitrary ways. This list: -

-
- 
…"--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
-
!

will generate four combinations, all involving ‘-Wextra’. !

!

The disadvantage to this method is that the testsuites are run in serial, which is a waste on multiprocessor systems. For users with GNU Make and a shell which performs brace expansion, you can run the testsuites in ! parallel by having the shell perform the combinations and make ! do the parallel runs. Instead of using ‘--target_board’, use a special makefile target: -

-
- 
make -jN check-testsuite//test-target/option1/option2/…
-
!

For example, !

!
! 
make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
!
!

will run three concurrent “make-gcc” testsuites, eventually testing all ten combinations as described above. Note that this is currently only ! supported in the gcc subdirectory. (To see how this works, try ! typing echo before the example given here.) !

! !

Additional testing for Java Class Libraries

!

The Java runtime tests can be executed via ‘make check’ ! in the target/libjava/testsuite directory in the build tree. !

!

The Mauve Project provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by placing the Mauve tree within the libjava ! testsuite at libjava/testsuite/libjava.mauve/mauve, or by ! specifying the location of that tree when invoking ‘make’, as in ! ‘make MAUVEDIR=~/mauve check’. !

! !

How to interpret test results

!

The result of running the testsuite are various *.sum and *.log ! files in the testsuite subdirectories. The *.log files contain a detailed log of the compiler invocations and the corresponding ! results, the *.sum files summarize the results. These summaries contain status codes for all tests: -

- !

It is normal for some tests to report unexpected failures. At the current time the testing harness does not allow fine grained control over whether or not a test is expected to fail. This problem should be fixed in future releases. -

! !

Submitting test results

If you want to report the results to the GCC project, use the ! contrib/test_summary shell script. Start it in the objdir with !

!
! 
srcdir/contrib/test_summary -p your_commentary.txt \
!     -m gcc-testresults@gcc.gnu.org |sh
!
!

This script uses the Mail program to send the results, so ! make sure it is in your PATH. The file your_commentary.txt is prepended to the testsuite summary and should contain any special remarks you have on your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. -

-
-

-

Return to the GCC Installation page -

- - - - - - -
- - --- 1,234 ---- ! ! ! Installing GCC: Testing ! ! ! ! ! ! ! ! ! !

Installing GCC: Testing

! ! Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the ! gcc-testresults mailing list. Some of these archived results are linked from the build status lists at http://gcc.gnu.org/buildstat.html, although not everyone who ! reports a successful build runs the testsuites and submits the results. This step is optional and may require you to download additional software, but it can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC. ! !

First, you must have downloaded the testsuites. These are part of the full distribution, but if you downloaded the “core” compiler plus any front ends, you must download the testsuites separately. ! !

Second, you must have the testing tools installed. This includes DejaGnu, Tcl, and Expect; the DejaGnu site has links to these. ! !

If the directories where runtest and expect were ! installed are not in the PATH, you may need to set the following environment variables appropriately, as in the following example (which ! assumes that DejaGnu has been installed under /usr/local): ! 

     TCL_LIBRARY = /usr/local/share/tcl8.0
!      DEJAGNULIBS = /usr/local/share/dejagnu
!
!

(On systems such as Cygwin, these paths are required to be actual paths, not mounts or links; presumably this is due to some lack of portability in the DejaGnu code.) !

Finally, you can run the testsuite (which may take a long time): ! 

     cd objdir; make -k check
!
!

This will test various components of GCC, such as compiler front ends and runtime libraries. While running the testsuite, DejaGnu might emit some harmless messages resembling ! ‘WARNING: Couldn't find the global config file.’ or ! ‘WARNING: Couldn't find tool init file’ that can be ignored. ! !

If you are testing a cross-compiler, you may want to run the testsuite on a simulator as described at http://gcc.gnu.org/simtest-howto.html. ! !

How can you run the testsuite on selected tests?

In order to run sets of tests selectively, there are targets ! ‘make check-gcc’ and language specific ‘make check-c’, ! ‘make check-c++’, ‘make check-fortran’, ‘make check-java’, ! ‘make check-ada’, ‘make check-objc’, ‘make check-obj-c++’, ! ‘make check-lto’ ! in the gcc subdirectory of the object directory. You can also ! just run ‘make check’ in a subdirectory of the object directory. !

A more selective way to just run all gcc execute tests in the testsuite is to use ! 

     make check-gcc RUNTESTFLAGS="execute.exp other-options"
!
!

Likewise, in order to run only the g++ “old-deja” tests in ! the testsuite with filenames matching ‘9805*’, you would use ! 

     make check-g++ RUNTESTFLAGS="old-deja.exp=9805* other-options"
!
!

The *.exp files are located in the testsuite directories of the GCC ! source, the most important ones being compile.exp, ! execute.exp, dg.exp and old-deja.exp. ! To get a list of the possible *.exp files, pipe the ! output of ‘make check’ into a file and look at the ! ‘Running ... .exp’ lines. ! !

Passing options and running multiple testsuites

You can pass multiple options to the testsuite using the ! ‘--target_board’ option of DejaGNU, either passed as part of ! ‘RUNTESTFLAGS’, or directly to runtest if you prefer to work outside the makefiles. For example, ! 

     make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
!
!

will run the standard g++ testsuites (“unix” is the target name for a standard native testsuite situation), passing ! ‘-O3 -fmerge-constants’ to the compiler on every test, i.e., slashes separate options. ! !

You can run the testsuites multiple times using combinations of options with a syntax similar to the brace expansion of popular shells: ! 

     ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}"
!
!

(Note the empty option caused by the trailing comma in the final group.) ! The following will run each testsuite eight times using the ‘arm-sim’ target, as if you had specified all possible combinations yourself: ! 

     --target_board='arm-sim/-mhard-float/-O1 \
!                      arm-sim/-mhard-float/-O2 \
!                      arm-sim/-mhard-float/-O3 \
!                      arm-sim/-mhard-float \
!                      arm-sim/-msoft-float/-O1 \
!                      arm-sim/-msoft-float/-O2 \
!                      arm-sim/-msoft-float/-O3 \
!                      arm-sim/-msoft-float'
!
!

They can be combined as many times as you wish, in arbitrary ways. This list: ! 

     ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
!
!

will generate four combinations, all involving ‘-Wextra’. ! !

The disadvantage to this method is that the testsuites are run in serial, which is a waste on multiprocessor systems. For users with GNU Make and a shell which performs brace expansion, you can run the testsuites in ! parallel by having the shell perform the combinations and make ! do the parallel runs. Instead of using ‘--target_board’, use a special makefile target: ! 

     make -jN check-testsuite//test-target/option1/option2/...
!
!

For example, ! 

     make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
!
!

will run three concurrent “make-gcc” testsuites, eventually testing all ten combinations as described above. Note that this is currently only ! supported in the gcc subdirectory. (To see how this works, try ! typing echo before the example given here.) !

Additional testing for Java Class Libraries

!

The Java runtime tests can be executed via ‘make check’ ! in the target/libjava/testsuite directory in the build tree. ! !

The Mauve Project provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by placing the Mauve tree within the libjava ! testsuite at libjava/testsuite/libjava.mauve/mauve, or by ! specifying the location of that tree when invoking ‘make’, as in ! ‘make MAUVEDIR=~/mauve check’. !

How to interpret test results

! !

The result of running the testsuite are various *.sum and *.log ! files in the testsuite subdirectories. The *.log files contain a detailed log of the compiler invocations and the corresponding ! results, the *.sum files summarize the results. These summaries contain status codes for all tests: !

! !

It is normal for some tests to report unexpected failures. At the current time the testing harness does not allow fine grained control over whether or not a test is expected to fail. This problem should be fixed in future releases. !

Submitting test results

If you want to report the results to the GCC project, use the ! contrib/test_summary shell script. Start it in the objdir with ! 

     srcdir/contrib/test_summary -p your_commentary.txt \
!          -m gcc-testresults@gcc.gnu.org |sh
!
!

This script uses the Mail program to send the results, so ! make sure it is in your PATH. The file your_commentary.txt is prepended to the testsuite summary and should contain any special remarks you have on your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. +

+

Return to the GCC Installation page + + + + + + + + diff -Nrcpad gcc-6.3.0/LAST_UPDATED gcc-6.4.0/LAST_UPDATED *** gcc-6.3.0/LAST_UPDATED Wed Dec 21 07:54:08 2016 --- gcc-6.4.0/LAST_UPDATED Tue Jul 4 07:28:15 2017 *************** *** 1 **** ! Obtained from SVN: tags/gcc_6_3_0_release revision 243837 --- 1 ---- ! Obtained from SVN: tags/gcc_6_4_0_release revision 249946 diff -Nrcpad gcc-6.3.0/MD5SUMS gcc-6.4.0/MD5SUMS *** gcc-6.3.0/MD5SUMS Wed Dec 21 09:56:51 2016 --- gcc-6.4.0/MD5SUMS Tue Jul 4 09:48:56 2017 *************** *** 1,5 **** # This file contains the MD5 checksums of the files in the ! # gcc-6.3.0.tar.bz2 tarball. # # Besides verifying that all files in the tarball were correctly expanded, # it also can be used to determine if any files have changed since the --- 1,5 ---- # This file contains the MD5 checksums of the files in the ! # gcc-6.4.0.tar.xz tarball. # # Besides verifying that all files in the tarball were correctly expanded, # it also can be used to determine if any files have changed since the *************** bca1d0b981220f8f259a9d4388f70546 .gitig *** 16,46 **** fe60d87048567d4fe8c8a0ed2448bcc8 COPYING.RUNTIME d32239bcb673463ab874e80d47fae504 COPYING3 6a6a8e020838b23406c81b19c1d46df6 COPYING3.LIB ! 4c846eb0913e2ac518ca683ce6cbbfce ChangeLog fd4ecdf5d672efe2b0e409aca9cf9446 ChangeLog.jit 09538b708302f1735f6fa05b622ecf5e ChangeLog.tree-ssa 24ab760126489e69436a43185dc3d202 INSTALL/README ! 2f28349f2d965a5b294b579a9c201ef2 INSTALL/binaries.html ! c83b1468ba1412d54a340b3871b6a48f INSTALL/build.html ! 1a1365d79b65e5a231fbdbeac1d363bc INSTALL/configure.html ! 5f6184da74bb12e500af5ac01273990f INSTALL/download.html ! 160609a99cb6fdaf35dc8d0c073723f1 INSTALL/finalinstall.html ! c1d79d599016cd6d3f5429b4b492005d INSTALL/gfdl.html ! e1c777ba85011ffe4325771151e2b819 INSTALL/index.html ! 17c749d6e33f4a8d140e30a64d3cddef INSTALL/old.html ! 6e8766b94f052996923912686984c7ed INSTALL/prerequisites.html ! 858fcc7cafd66b8f10cad4fb9a3b0472 INSTALL/specific.html ! 17fa2d93415c67ee34575ece24e6f691 INSTALL/test.html ! d0810ea0c30659564f50dfd402dd36c0 LAST_UPDATED b101e24e658738320c6f7460345cd30e MAINTAINERS ac51a3b92098155704bd0e6f3e27e70f Makefile.def 7fa740cb7ac3a6e647702770bb023340 Makefile.in 5658e4a049df2f77bee1189b6603aa77 Makefile.tpl ! 750fcc0d48f0be3bd610c301f19031c6 NEWS 80d26bc3b1ad4f6969a96a24c9181bf5 README b510a5285eb05298b5f3d9f5ae920588 boehm-gc/AmigaOS.c 2caafacabf758bb76a9dfce1fc544b97 boehm-gc/BCC_MAKEFILE ! debcf78a9f5385226d3655579f054091 boehm-gc/ChangeLog c18075e3729cd116028480307a8e845d boehm-gc/EMX_MAKEFILE 3b7cc3be9ed3c2135bbda990e8a69303 boehm-gc/MacOS.c 5cf7764626b7dd7272b2fe11403d1b6a boehm-gc/MacProjects.sit.hqx --- 16,46 ---- fe60d87048567d4fe8c8a0ed2448bcc8 COPYING.RUNTIME d32239bcb673463ab874e80d47fae504 COPYING3 6a6a8e020838b23406c81b19c1d46df6 COPYING3.LIB ! d6c437da9b051fdd4f7eb6ea1fa0c69c ChangeLog fd4ecdf5d672efe2b0e409aca9cf9446 ChangeLog.jit 09538b708302f1735f6fa05b622ecf5e ChangeLog.tree-ssa 24ab760126489e69436a43185dc3d202 INSTALL/README ! 24ecb3e7700afc5f49fb8be82d3d738b INSTALL/binaries.html ! 84d4308f451865f73d248e3f3020e527 INSTALL/build.html ! 864aad592c397278b74f98ce210ab715 INSTALL/configure.html ! ff0503b0236c7ca75c6914236e6a7d21 INSTALL/download.html ! fca0871b2542024bfc06f83d947144cb INSTALL/finalinstall.html ! 6cd4943d3fd0a684344aa9501c1f6a92 INSTALL/gfdl.html ! 990bc554f2ec342c9c2e7ee8d2214836 INSTALL/index.html ! 5298546b61e638e7afdea2f506a9c6a6 INSTALL/old.html ! 29049f0016c4bbe48651113132c27f3e INSTALL/prerequisites.html ! 5bbdc9f8c69d0eee010c34862fccd0ae INSTALL/specific.html ! 2bd6ab791fc86909e682cc70bc6cc3de INSTALL/test.html ! 3a40bf2300d5cefad207ea848700ac1d LAST_UPDATED b101e24e658738320c6f7460345cd30e MAINTAINERS ac51a3b92098155704bd0e6f3e27e70f Makefile.def 7fa740cb7ac3a6e647702770bb023340 Makefile.in 5658e4a049df2f77bee1189b6603aa77 Makefile.tpl ! 3c64174bb1ced89839979feb137f7a40 NEWS 80d26bc3b1ad4f6969a96a24c9181bf5 README b510a5285eb05298b5f3d9f5ae920588 boehm-gc/AmigaOS.c 2caafacabf758bb76a9dfce1fc544b97 boehm-gc/BCC_MAKEFILE ! 1e9b9b2d42549283e39622e0d700e2c3 boehm-gc/ChangeLog c18075e3729cd116028480307a8e845d boehm-gc/EMX_MAKEFILE 3b7cc3be9ed3c2135bbda990e8a69303 boehm-gc/MacOS.c 5cf7764626b7dd7272b2fe11403d1b6a boehm-gc/MacProjects.sit.hqx *************** c0c823fa830e3f7c4620a33fc4818f4d boehm- *** 219,228 **** 3428a06751c63f7aee005f42c714b00e config.guess 040359150cf11493f973a46d8a25b06b config.rpath 1343b4a2ffe75aaed02e84d0d3711424 config.sub ! c0dc689b433e312f571a6cc3b8da8c9e config/ChangeLog 0fcd4badfe2a2191778bdf5ab94aa40c config/acinclude.m4 9238d23c68259d195b332db71892d242 config/acx.m4 6b030f5cf640bdd401ea739f54a667f8 config/asmcfi.m4 596c2296c23cda1b6445427d6c3ce3ad config/bitfields.m4 5c6a030699353abe2ff69294a495e4cd config/bootstrap-O1.mk 4d3304310a9b7b17872d6f644e1dd7c8 config/bootstrap-O3.mk --- 219,229 ---- 3428a06751c63f7aee005f42c714b00e config.guess 040359150cf11493f973a46d8a25b06b config.rpath 1343b4a2ffe75aaed02e84d0d3711424 config.sub ! fbd9bf26fbdef9a1d751b24e5914c892 config/ChangeLog 0fcd4badfe2a2191778bdf5ab94aa40c config/acinclude.m4 9238d23c68259d195b332db71892d242 config/acx.m4 6b030f5cf640bdd401ea739f54a667f8 config/asmcfi.m4 + a6bf9c39c62222092ea6d5d8551c077f config/ax_check_define.m4 596c2296c23cda1b6445427d6c3ce3ad config/bitfields.m4 5c6a030699353abe2ff69294a495e4cd config/bootstrap-O1.mk 4d3304310a9b7b17872d6f644e1dd7c8 config/bootstrap-O3.mk *************** e2dc6b4fd62b77bff96b7951ef74f78f config *** 307,315 **** 5cabffc02a90bd9698105b9eef507f11 config/warnings.m4 7ef51b0adb98e5c5f7aba46d2c7293f1 config/weakref.m4 0163b672c888aaf1c8ad3e867a0ec9f1 config/zlib.m4 ! 44f774f8cae03497ae59f44c2d4b359b configure ! 8776f68fd3afeec59b3742c6ae22a2ec configure.ac ! 4ef56434d0c7412721a8c647f9a74aa5 contrib/ChangeLog 5fc435c7928f858246df931ea3f3ece7 contrib/ChangeLog.jit 7af8d2979bf1a7cfa88e30d05fa22be2 contrib/ChangeLog.tree-ssa e0ea80d7094bf66610f2f60db444f9a1 contrib/analyze_brprob --- 308,316 ---- 5cabffc02a90bd9698105b9eef507f11 config/warnings.m4 7ef51b0adb98e5c5f7aba46d2c7293f1 config/weakref.m4 0163b672c888aaf1c8ad3e867a0ec9f1 config/zlib.m4 ! ef1e1095f46c637c10c1bade0818776b configure ! 7bdb6b0080b3111cdfb9d51a9888db60 configure.ac ! ffe457f13821fea8187e3b06a9a170c3 contrib/ChangeLog 5fc435c7928f858246df931ea3f3ece7 contrib/ChangeLog.jit 7af8d2979bf1a7cfa88e30d05fa22be2 contrib/ChangeLog.tree-ssa e0ea80d7094bf66610f2f60db444f9a1 contrib/analyze_brprob *************** db03e57377f9eb202b7b783eb81fe40d contri *** 338,344 **** 5c3a4b2d03b05d953b3fec3c7e08a60a contrib/gennews 2d35f147fc45f270eb169156cf7550e0 contrib/gimple.vim 59304fc08afa489baa6b920cc76dc625 contrib/gthr_supp_vxw_5x.c ! 032af5c49f04d3e1d1c638213f2af331 contrib/header-tools/ChangeLog d3fcdb6edf2e1805da8b268465c7f8db contrib/header-tools/README 05ef7fb87e90ba93ee04659be072a357 contrib/header-tools/count-headers ba0485a3c721bce9e32407ef996d2a9d contrib/header-tools/gcc-order-headers --- 339,345 ---- 5c3a4b2d03b05d953b3fec3c7e08a60a contrib/gennews 2d35f147fc45f270eb169156cf7550e0 contrib/gimple.vim 59304fc08afa489baa6b920cc76dc625 contrib/gthr_supp_vxw_5x.c ! 435e416e7acf1ba6a3865246d900b4b4 contrib/header-tools/ChangeLog d3fcdb6edf2e1805da8b268465c7f8db contrib/header-tools/README 05ef7fb87e90ba93ee04659be072a357 contrib/header-tools/count-headers ba0485a3c721bce9e32407ef996d2a9d contrib/header-tools/gcc-order-headers *************** a7318fa2f0580c3a0d5dd4b14e4d0e0d contri *** 357,363 **** 0fb5c8c3cd465d8bd57b55b2548c683a contrib/paranoia.cc 9083c56c1c89c5bec355a27f78e49807 contrib/patch_tester.sh 87a19b40fbd220938cf6c23c42c255e2 contrib/prepare_patch.sh ! 1bb2b7152fba15f9d6614314379d0fbd contrib/reghunt/ChangeLog cf247a580e49d212518de409793db0a8 contrib/reghunt/bin/gcc-build-full 724e70ea3e80f87f2a201bbe2f1eef37 contrib/reghunt/bin/gcc-build-simple 3f2318bae7562a4ad1639e686916a545 contrib/reghunt/bin/gcc-cleanup --- 358,364 ---- 0fb5c8c3cd465d8bd57b55b2548c683a contrib/paranoia.cc 9083c56c1c89c5bec355a27f78e49807 contrib/patch_tester.sh 87a19b40fbd220938cf6c23c42c255e2 contrib/prepare_patch.sh ! 89fae63167e571a6e17875cd2dc0c500 contrib/reghunt/ChangeLog cf247a580e49d212518de409793db0a8 contrib/reghunt/bin/gcc-build-full 724e70ea3e80f87f2a201bbe2f1eef37 contrib/reghunt/bin/gcc-build-simple 3f2318bae7562a4ad1639e686916a545 contrib/reghunt/bin/gcc-cleanup *************** f251d49dd87647250fcd74dd50b7835f contri *** 416,422 **** e2829fc4af4f433a6a328a62d5ce8066 contrib/reghunt/examples/reg-watch afd863c2ec84c906e20f9b9787b1f0fe contrib/reghunt/examples/reg-watch.awk 8955535523d4b5f48006bcb851ba9b4b contrib/reghunt/examples/testall ! 785e7ad04a5a7cd4d2897d4c45a37445 contrib/regression/ChangeLog 30553bfced1b2b46bf7ca01ef6ba69d1 contrib/regression/GCC_Regression_Tester.wdgt/Default.png ad38ddd771df222eb9d413e3c7f6a751 contrib/regression/GCC_Regression_Tester.wdgt/Icon.png 777bd286c147cc02861811f66b9a4440 contrib/regression/GCC_Regression_Tester.wdgt/Info.plist --- 417,423 ---- e2829fc4af4f433a6a328a62d5ce8066 contrib/reghunt/examples/reg-watch afd863c2ec84c906e20f9b9787b1f0fe contrib/reghunt/examples/reg-watch.awk 8955535523d4b5f48006bcb851ba9b4b contrib/reghunt/examples/testall ! 2761ee0ef187900d3c124777c15b69f2 contrib/regression/ChangeLog 30553bfced1b2b46bf7ca01ef6ba69d1 contrib/regression/GCC_Regression_Tester.wdgt/Default.png ad38ddd771df222eb9d413e3c7f6a751 contrib/regression/GCC_Regression_Tester.wdgt/Icon.png 777bd286c147cc02861811f66b9a4440 contrib/regression/GCC_Regression_Tester.wdgt/Info.plist *************** c619e84bad79c6103190d13e243e923e contri *** 441,447 **** d25174fd04b32bbeab5f3cc783277ec1 contrib/vimrc 7cb42cbdf8becd280d1e16191416fb62 contrib/warn_summary 8b59f0d0a2dcdced14765c514fbad719 depcomp ! 706a7a7267c695e83801d101e8299eb1 fixincludes/ChangeLog c23ba4c4f4ca4dfcdd9b4155e4626da7 fixincludes/Makefile.in b6e3f4950abc6e254b467063381f6473 fixincludes/README 455903ad4ff71fa5c5340ef7ae41a0e6 fixincludes/README-fixinc --- 442,448 ---- d25174fd04b32bbeab5f3cc783277ec1 contrib/vimrc 7cb42cbdf8becd280d1e16191416fb62 contrib/warn_summary 8b59f0d0a2dcdced14765c514fbad719 depcomp ! d336291fe08741e0773f53533655c2f5 fixincludes/ChangeLog c23ba4c4f4ca4dfcdd9b4155e4626da7 fixincludes/Makefile.in b6e3f4950abc6e254b467063381f6473 fixincludes/README 455903ad4ff71fa5c5340ef7ae41a0e6 fixincludes/README-fixinc *************** e06760e2aaa65a20f4f201cf50e62a16 fixinc *** 454,466 **** 497da58c4b47627a33f754b61f6eb051 fixincludes/fixinc.in 9662d8ad173553c438e3ad3fc9db8352 fixincludes/fixincl.c e1cd70e73f3c2d2319fd9d210ad6a5ff fixincludes/fixincl.tpl ! 4fdab9e65d578b937d1439eded4182fd fixincludes/fixincl.x 47da6e634225e1667c26a71bcf234bfa fixincludes/fixlib.c d8aac376a7311e465eb0a98d341103a1 fixincludes/fixlib.h 5b2c1fd3ef9d44fb6beb1a0d45ddd533 fixincludes/fixopts.c ed1415e9dbc8f421fd9288bde0d90ad1 fixincludes/fixtests.c 6df145c7cea1e2099cf97a0d83564aca fixincludes/genfixes ! e04513bb7cc496e865e197ab7dd4b36b fixincludes/inclhack.def 73354a5ccc669d3a585be10f1f7e7cb7 fixincludes/mkfixinc.sh 5f9960cfe65b2e6bef658f770e52dfef fixincludes/mkheaders.in 3aa0563cd682ee61ecd9eb6eea0b0bce fixincludes/procopen.c --- 455,467 ---- 497da58c4b47627a33f754b61f6eb051 fixincludes/fixinc.in 9662d8ad173553c438e3ad3fc9db8352 fixincludes/fixincl.c e1cd70e73f3c2d2319fd9d210ad6a5ff fixincludes/fixincl.tpl ! fe2cac93b7983d72de2ecced395d6b5c fixincludes/fixincl.x 47da6e634225e1667c26a71bcf234bfa fixincludes/fixlib.c d8aac376a7311e465eb0a98d341103a1 fixincludes/fixlib.h 5b2c1fd3ef9d44fb6beb1a0d45ddd533 fixincludes/fixopts.c ed1415e9dbc8f421fd9288bde0d90ad1 fixincludes/fixtests.c 6df145c7cea1e2099cf97a0d83564aca fixincludes/genfixes ! 82ed4f7738ae28aefeb366ab5ce195a7 fixincludes/inclhack.def 73354a5ccc669d3a585be10f1f7e7cb7 fixincludes/mkfixinc.sh 5f9960cfe65b2e6bef658f770e52dfef fixincludes/mkheaders.in 3aa0563cd682ee61ecd9eb6eea0b0bce fixincludes/procopen.c *************** bfb58e3983fc133c965e434e57aed732 fixinc *** 498,504 **** a11561f51aa57e84e571f2073fb6bf60 fixincludes/tests/base/ioLib.h c8dd71b57c3a35b0c6760f7d38af6f42 fixincludes/tests/base/iso/math_c99.h 56aa16fdf3be46d7dc2b462246495f82 fixincludes/tests/base/iso/math_iso.h ! 5b48936adb644e9aa4b78d21297cc193 fixincludes/tests/base/iso/stdio_iso.h e1bd28539aceeab13a3028da02f8c4ae fixincludes/tests/base/iso/stdlib_iso.h 1ac942b363960bf8a865ffd9e3bf28be fixincludes/tests/base/linux/vt.h 8183eabf96be2918f3259a587329a813 fixincludes/tests/base/locale.h --- 499,506 ---- a11561f51aa57e84e571f2073fb6bf60 fixincludes/tests/base/ioLib.h c8dd71b57c3a35b0c6760f7d38af6f42 fixincludes/tests/base/iso/math_c99.h 56aa16fdf3be46d7dc2b462246495f82 fixincludes/tests/base/iso/math_iso.h ! cb3e756a4d569b97af1ed7a9d48ff57b fixincludes/tests/base/iso/stdio_iso.h ! 1c72f8feabf8899114770389de731d90 fixincludes/tests/base/iso/stdlib_c99.h e1bd28539aceeab13a3028da02f8c4ae fixincludes/tests/base/iso/stdlib_iso.h 1ac942b363960bf8a865ffd9e3bf28be fixincludes/tests/base/linux/vt.h 8183eabf96be2918f3259a587329a813 fixincludes/tests/base/locale.h *************** d2f1ddef1ca3edae298e37f7bc892941 fixinc *** 539,545 **** 563eddf934e21ec7f85628e18fb1c641 fixincludes/tests/base/stdint-hpux11.h cc3783f241fa992a305aced8e1195ee9 fixincludes/tests/base/stdint-newlib.h 1ee4e2b61ae5781d35271f3181927037 fixincludes/tests/base/stdint.h ! bd72848710b6f098f5e44218bfe3202e fixincludes/tests/base/stdio.h 1887d8bc1711dae9922852cda6027877 fixincludes/tests/base/stdio_tag.h 6b842aa18e09c73db745cbffa3cb34cf fixincludes/tests/base/stdlib.h 42a7de17fb8f2ac74bc30c7029199637 fixincludes/tests/base/string.h --- 541,547 ---- 563eddf934e21ec7f85628e18fb1c641 fixincludes/tests/base/stdint-hpux11.h cc3783f241fa992a305aced8e1195ee9 fixincludes/tests/base/stdint-newlib.h 1ee4e2b61ae5781d35271f3181927037 fixincludes/tests/base/stdint.h ! d47412644cdea4f030ba2744eca6d8ad fixincludes/tests/base/stdio.h 1887d8bc1711dae9922852cda6027877 fixincludes/tests/base/stdio_tag.h 6b842aa18e09c73db745cbffa3cb34cf fixincludes/tests/base/stdlib.h 42a7de17fb8f2ac74bc30c7029199637 fixincludes/tests/base/string.h *************** a5e817d35ded04a0fb03999b50c0e89e fixinc *** 572,583 **** 955462b555900ecd3934223c64e21fa7 fixincludes/tests/base/types/vxTypesBase.h c78e762f2c91f2af991feda7d3d7f4b2 fixincludes/tests/base/unistd.h a2fe1dc808019c9134bca8a4a9a8eec2 gcc/ABOUT-GCC-NLS ! 9cd76eedc9b725959003996068afdd13 gcc/BASE-VER 59530bdf33659b29e73d4adb9f9f6552 gcc/COPYING a916467b91076e631dd8edb7424769c7 gcc/COPYING.LIB d32239bcb673463ab874e80d47fae504 gcc/COPYING3 6a6a8e020838b23406c81b19c1d46df6 gcc/COPYING3.LIB ! 4ab516ac76ff5aac387e766fc697cbc9 gcc/ChangeLog a3b63c675afa7a655cc2bfa8a907af79 gcc/ChangeLog-1997 d9a88529352a010253c2e8fb1ed6023b gcc/ChangeLog-1998 240f08f81cb4699e8b49347db38233db gcc/ChangeLog-1999 --- 574,585 ---- 955462b555900ecd3934223c64e21fa7 fixincludes/tests/base/types/vxTypesBase.h c78e762f2c91f2af991feda7d3d7f4b2 fixincludes/tests/base/unistd.h a2fe1dc808019c9134bca8a4a9a8eec2 gcc/ABOUT-GCC-NLS ! 8dd877cbb3b6a77a849a54b5e3f53aa6 gcc/BASE-VER 59530bdf33659b29e73d4adb9f9f6552 gcc/COPYING a916467b91076e631dd8edb7424769c7 gcc/COPYING.LIB d32239bcb673463ab874e80d47fae504 gcc/COPYING3 6a6a8e020838b23406c81b19c1d46df6 gcc/COPYING3.LIB ! a947ae98e0ed7191f6166eb1538c334e gcc/ChangeLog a3b63c675afa7a655cc2bfa8a907af79 gcc/ChangeLog-1997 d9a88529352a010253c2e8fb1ed6023b gcc/ChangeLog-1998 240f08f81cb4699e8b49347db38233db gcc/ChangeLog-1999 *************** fb3fadb88e1d2b3b640cfaaa5ff11780 gcc/Ch *** 605,623 **** 3eb07e0b2e542409bf73d359f7f65609 gcc/ChangeLog.ptr e13638e26743ba41e6011b76cc00d9a9 gcc/ChangeLog.tree-ssa 739ab47f6425bcea1d05e4fc0542de54 gcc/ChangeLog.tuples ! 66efd343f06bbee2652ee8609990823c gcc/DATESTAMP d41d8cd98f00b204e9800998ecf8427e gcc/DEV-PHASE eb92e1ff5e982ca07e173e0eb286d243 gcc/FSFChangeLog 30e1e33411566388b3164558482dc5e6 gcc/FSFChangeLog.10 36698274bb69e2ada20f5cc434f3caa5 gcc/FSFChangeLog.11 c26cece9a404838a41d5d1725039ec98 gcc/LANGUAGES ! a79c88e6dc4496ee12fbca7203d3fa96 gcc/Makefile.in ec6799501b2eb2923d5de6a66169dbd2 gcc/ONEWS 3b453eda3aaca4dbe7399dc3420337fd gcc/README.Portability e71640635091e22ac2f09f2573aee53d gcc/acinclude.m4 9545fe83576dc99e441c64e268711730 gcc/aclocal.m4 9063d23e571fcde20283b9f34d5e3422 gcc/ada/9drpc.adb ! bcbbcf61b2d67af4e1e0b06eb03491a9 gcc/ada/ChangeLog 683be0b07dc4f64f118fd5e8ae9cb30d gcc/ada/ChangeLog-2001 7aff25efb203be4136b8776cdc812956 gcc/ada/ChangeLog-2002 cd2379152000f40157d349018fb9364d gcc/ada/ChangeLog-2003 --- 607,625 ---- 3eb07e0b2e542409bf73d359f7f65609 gcc/ChangeLog.ptr e13638e26743ba41e6011b76cc00d9a9 gcc/ChangeLog.tree-ssa 739ab47f6425bcea1d05e4fc0542de54 gcc/ChangeLog.tuples ! 7a24c7aa74f98ed602e64b231755da7d gcc/DATESTAMP d41d8cd98f00b204e9800998ecf8427e gcc/DEV-PHASE eb92e1ff5e982ca07e173e0eb286d243 gcc/FSFChangeLog 30e1e33411566388b3164558482dc5e6 gcc/FSFChangeLog.10 36698274bb69e2ada20f5cc434f3caa5 gcc/FSFChangeLog.11 c26cece9a404838a41d5d1725039ec98 gcc/LANGUAGES ! 5be54932b00fa25fb30ecafa1e964f0e gcc/Makefile.in ec6799501b2eb2923d5de6a66169dbd2 gcc/ONEWS 3b453eda3aaca4dbe7399dc3420337fd gcc/README.Portability e71640635091e22ac2f09f2573aee53d gcc/acinclude.m4 9545fe83576dc99e441c64e268711730 gcc/aclocal.m4 9063d23e571fcde20283b9f34d5e3422 gcc/ada/9drpc.adb ! 7af4e08710f8a28bd18e5ff9fda23f9b gcc/ada/ChangeLog 683be0b07dc4f64f118fd5e8ae9cb30d gcc/ada/ChangeLog-2001 7aff25efb203be4136b8776cdc812956 gcc/ada/ChangeLog-2002 cd2379152000f40157d349018fb9364d gcc/ada/ChangeLog-2003 *************** d7eca93022b3adc8f4a61dbe910e95d2 gcc/ad *** 1632,1652 **** b45654446bc74bb68ae4adef78906e9b gcc/ada/g-zspche.ads c97edf7ce39a908dcaec55eb49d0abee gcc/ada/g-zstspl.ads 2d84385afb15b1e902dcffc5a34f4d8d gcc/ada/gcc-interface/Make-lang.in ! 6bc778167716dec30c1bcd7fd679be57 gcc/ada/gcc-interface/Makefile.in 055be3d11fa6ccb53ffe7f8970a005ce gcc/ada/gcc-interface/ada-tree.def 71ae48a6622bd120e6be917ab8d64bf6 gcc/ada/gcc-interface/ada-tree.h 51c95420b5900990141d2e5705582197 gcc/ada/gcc-interface/ada.h 4cbfd794461da0feb1b8661ec623b6c6 gcc/ada/gcc-interface/config-lang.in 9779c4debc13c6f1cfa1e4e6a6e6c638 gcc/ada/gcc-interface/cuintp.c ! fde21dd114afcaa681cdef1f94d1f2c7 gcc/ada/gcc-interface/decl.c c413d4d50e9563859f4d751a4404b705 gcc/ada/gcc-interface/gadaint.h 610fd259aa8c7f70adaecc1a439ee311 gcc/ada/gcc-interface/gigi.h f2528ece7aa7e2ed8123de8fe434252a gcc/ada/gcc-interface/lang-specs.h e3a177357a504878ee8863c5dddf3b44 gcc/ada/gcc-interface/lang.opt 4c27c8d2e30202eac1e7d1e9bfffd989 gcc/ada/gcc-interface/misc.c 7bd3630f35c5ac7b5c6cfaf8b16e5723 gcc/ada/gcc-interface/targtyps.c ! c24acd0193cc38c43ad22911992a55b9 gcc/ada/gcc-interface/trans.c ! d4e4be3abf018c7c3db77373825a9286 gcc/ada/gcc-interface/utils.c d55eec83add5f1d2e50008abe398fe2c gcc/ada/gcc-interface/utils2.c 68b13816c95338a03ea3b161c2099ea1 gcc/ada/get_scos.adb baa8fdaf8d693eb6c5a7e42944887584 gcc/ada/get_scos.ads --- 1634,1654 ---- b45654446bc74bb68ae4adef78906e9b gcc/ada/g-zspche.ads c97edf7ce39a908dcaec55eb49d0abee gcc/ada/g-zstspl.ads 2d84385afb15b1e902dcffc5a34f4d8d gcc/ada/gcc-interface/Make-lang.in ! 27754de3ca2217c4f2f64bfe6aaa3ad4 gcc/ada/gcc-interface/Makefile.in 055be3d11fa6ccb53ffe7f8970a005ce gcc/ada/gcc-interface/ada-tree.def 71ae48a6622bd120e6be917ab8d64bf6 gcc/ada/gcc-interface/ada-tree.h 51c95420b5900990141d2e5705582197 gcc/ada/gcc-interface/ada.h 4cbfd794461da0feb1b8661ec623b6c6 gcc/ada/gcc-interface/config-lang.in 9779c4debc13c6f1cfa1e4e6a6e6c638 gcc/ada/gcc-interface/cuintp.c ! c60b129a815f77a281f031207699d5f5 gcc/ada/gcc-interface/decl.c c413d4d50e9563859f4d751a4404b705 gcc/ada/gcc-interface/gadaint.h 610fd259aa8c7f70adaecc1a439ee311 gcc/ada/gcc-interface/gigi.h f2528ece7aa7e2ed8123de8fe434252a gcc/ada/gcc-interface/lang-specs.h e3a177357a504878ee8863c5dddf3b44 gcc/ada/gcc-interface/lang.opt 4c27c8d2e30202eac1e7d1e9bfffd989 gcc/ada/gcc-interface/misc.c 7bd3630f35c5ac7b5c6cfaf8b16e5723 gcc/ada/gcc-interface/targtyps.c ! 112c42299092d8088ca89769fbe9dcd0 gcc/ada/gcc-interface/trans.c ! 0802ab9900bc5185fa1d65746789a9a2 gcc/ada/gcc-interface/utils.c d55eec83add5f1d2e50008abe398fe2c gcc/ada/gcc-interface/utils2.c 68b13816c95338a03ea3b161c2099ea1 gcc/ada/get_scos.adb baa8fdaf8d693eb6c5a7e42944887584 gcc/ada/get_scos.ads *************** c39300ff29503cedabd135fea15fe825 gcc/ad *** 2603,2609 **** f458e0e9debe0ed2c3f9d660e25b6e0b gcc/ada/snames.adb-tmpl f945614c9dd1a67212f4034bacd1e325 gcc/ada/snames.ads-tmpl 1d0f0a946dfb952f009ada43305106dd gcc/ada/snames.h-tmpl ! 45468ab978f26909ae88c91c0bd6de66 gcc/ada/socket.c fed699b16ff3756c6e148d28b2db1a6a gcc/ada/spark_xrefs.adb 5e1b6d2b92f062803f50f632b8b64ede gcc/ada/spark_xrefs.ads 06c27709b5f440d91ae501e950a94fc8 gcc/ada/spark_xrefs_test.adb --- 2605,2611 ---- f458e0e9debe0ed2c3f9d660e25b6e0b gcc/ada/snames.adb-tmpl f945614c9dd1a67212f4034bacd1e325 gcc/ada/snames.ads-tmpl 1d0f0a946dfb952f009ada43305106dd gcc/ada/snames.h-tmpl ! b684ef5a44004c6c8fffe33a1bd28809 gcc/ada/socket.c fed699b16ff3756c6e148d28b2db1a6a gcc/ada/spark_xrefs.adb 5e1b6d2b92f062803f50f632b8b64ede gcc/ada/spark_xrefs.ads 06c27709b5f440d91ae501e950a94fc8 gcc/ada/spark_xrefs_test.adb *************** f3529cf7e308b1c2f88769fece799df1 gcc/ad *** 2642,2647 **** --- 2644,2650 ---- e90465b96c4e84483cab3965b3bce9da gcc/ada/system-freebsd-x86_64.ads 5b2822ecc8b2fdb73d25e0c1a84ff1d1 gcc/ada/system-hpux-ia64.ads b6cc08525531d1f3982d9c75f478b398 gcc/ada/system-hpux.ads + 5c4c2d5f8f81c07957daf987909a6dab gcc/ada/system-linux-aarch64-ilp32.ads b3d780ff30e1fbd73604e66d30b08594 gcc/ada/system-linux-alpha.ads df0baf7575f16e2e7c9c8d3534d8d3d5 gcc/ada/system-linux-armeb.ads 01b0500080a147f99972b2d982e4125e gcc/ada/system-linux-armel.ads *************** b9c935b28aa1f615229b2de609214b9e gcc/ad *** 2650,2656 **** 34310963131cf321b5005366f8393685 gcc/ada/system-linux-mips.ads 37e0810c81778ea8393c4c7e85ccbf80 gcc/ada/system-linux-mips64el.ads 698db90ad06eb999ae9cf52eded7251f gcc/ada/system-linux-mipsel.ads ! a8c4e397d5daa041d7440584855959f1 gcc/ada/system-linux-ppc.ads 9e830ac9ed801e231eaf4b0b2de09bb1 gcc/ada/system-linux-s390.ads af5757813f0b2e2bbcf6a310584dfebe gcc/ada/system-linux-s390x.ads 97fd7cce986b18ba9ba777a6e8fe4bf9 gcc/ada/system-linux-sh4.ads --- 2653,2659 ---- 34310963131cf321b5005366f8393685 gcc/ada/system-linux-mips.ads 37e0810c81778ea8393c4c7e85ccbf80 gcc/ada/system-linux-mips64el.ads 698db90ad06eb999ae9cf52eded7251f gcc/ada/system-linux-mipsel.ads ! 233e3a6e4eb191151c93069ff6506cf3 gcc/ada/system-linux-ppc.ads 9e830ac9ed801e231eaf4b0b2de09bb1 gcc/ada/system-linux-s390.ads af5757813f0b2e2bbcf6a310584dfebe gcc/ada/system-linux-s390x.ads 97fd7cce986b18ba9ba777a6e8fe4bf9 gcc/ada/system-linux-sh4.ads *************** fc7be41f48bbad07a07baf3e27fc889b gcc/ad *** 2735,2750 **** 0493a7ed666c4b102be665a8e328be35 gcc/ada/xutil.adb 2c8b2f1975e4e064d3803db6dbd516cb gcc/ada/xutil.ads 50ccfa68b3ffc2cea9079d312bab3902 gcc/addresses.h ! 7775fff917e65f6f03072de4d1cacb53 gcc/alias.c 3f435b1cc17bbef3b90835cfda49b4eb gcc/alias.h 2129a033ed56d38308ca40e1424337c0 gcc/alloc-pool.c f9d22e8738cd46b8cd0075ae0e4bd5e1 gcc/alloc-pool.h ! 71922db6042ca44d9217d21a73c6b0be gcc/asan.c f24bb3e6f685b695e4763d26c6d5f82e gcc/asan.h f015e12bb7fc520fda759e96f1a39311 gcc/attribs.c 01d94dd275ab10965e144d0b9fa042f9 gcc/attribs.h f26aa1c63f9a0ae7f75bbc5d7b05f221 gcc/auto-inc-dec.c ! 7e6ab444d1b5407173534f0fd6733860 gcc/auto-profile.c 6bc02d4d5e6a01b745db21ed909a394a gcc/auto-profile.h 48db4552b98fa147c499c5fbb1e6525c gcc/backend.h b401992200a48301c1a893d41156dc3c gcc/basic-block.h --- 2738,2753 ---- 0493a7ed666c4b102be665a8e328be35 gcc/ada/xutil.adb 2c8b2f1975e4e064d3803db6dbd516cb gcc/ada/xutil.ads 50ccfa68b3ffc2cea9079d312bab3902 gcc/addresses.h ! 62d91f89038decc8b1a92d787c8172df gcc/alias.c 3f435b1cc17bbef3b90835cfda49b4eb gcc/alias.h 2129a033ed56d38308ca40e1424337c0 gcc/alloc-pool.c f9d22e8738cd46b8cd0075ae0e4bd5e1 gcc/alloc-pool.h ! aad82e03b4be837925c0c99a5f6458b9 gcc/asan.c f24bb3e6f685b695e4763d26c6d5f82e gcc/asan.h f015e12bb7fc520fda759e96f1a39311 gcc/attribs.c 01d94dd275ab10965e144d0b9fa042f9 gcc/attribs.h f26aa1c63f9a0ae7f75bbc5d7b05f221 gcc/auto-inc-dec.c ! abd554879edd19fa4b3d9d7440e4bac0 gcc/auto-profile.c 6bc02d4d5e6a01b745db21ed909a394a gcc/auto-profile.h 48db4552b98fa147c499c5fbb1e6525c gcc/backend.h b401992200a48301c1a893d41156dc3c gcc/basic-block.h *************** a475d3d54c99963bd6f1f7388fdf092a gcc/bi *** 2755,2770 **** 027981026a4e2d79b41ba78a21b4c34e gcc/bt-load.c 16e45280b913081f4097975ce8f1f501 gcc/builtin-attrs.def 82544414300ae940e1bda57f5f3e8f54 gcc/builtin-types.def ! a24786d45f0f3119ecc8d52d5b343d6f gcc/builtins.c d9b3f84012b6195bbd548885fa07798e gcc/builtins.def 70361ef7d2d5ef5ab078cc31686c0bde gcc/builtins.h ! c72412923cc3d659a9fc4ce92d7dae8c gcc/c-family/ChangeLog ea3fa1f4d7390a105fa3caab4f79aaf7 gcc/c-family/ChangeLog.gimple-classes a2097d99f50de5a2a2e9b9f45acca9af gcc/c-family/array-notation-common.c ! d268d78fdd0da46755bad2715380ca60 gcc/c-family/c-ada-spec.c 3f3d9fc98b14db4a909afffe3ca593ea gcc/c-family/c-ada-spec.h d1049a363c1ecd0f98eee1aeb9ff6bd1 gcc/c-family/c-cilkplus.c ! 31301557aad30b854f8712ab07ebcf71 gcc/c-family/c-common.c 2ace27db32acd08f6b79a83ac2586e45 gcc/c-family/c-common.def 9f20703bcd296e28b53330fdacbaa6c4 gcc/c-family/c-common.h 2726890948ddd8a7c99836847c4c465b gcc/c-family/c-cppbuiltin.c --- 2758,2773 ---- 027981026a4e2d79b41ba78a21b4c34e gcc/bt-load.c 16e45280b913081f4097975ce8f1f501 gcc/builtin-attrs.def 82544414300ae940e1bda57f5f3e8f54 gcc/builtin-types.def ! 00add7ef08573b7f4f1f5de60cf7da0a gcc/builtins.c d9b3f84012b6195bbd548885fa07798e gcc/builtins.def 70361ef7d2d5ef5ab078cc31686c0bde gcc/builtins.h ! ae6c7fc2ca7cdb1feed383d69782b7bf gcc/c-family/ChangeLog ea3fa1f4d7390a105fa3caab4f79aaf7 gcc/c-family/ChangeLog.gimple-classes a2097d99f50de5a2a2e9b9f45acca9af gcc/c-family/array-notation-common.c ! 45e3a3fd30411907f1cc076aa0b08204 gcc/c-family/c-ada-spec.c 3f3d9fc98b14db4a909afffe3ca593ea gcc/c-family/c-ada-spec.h d1049a363c1ecd0f98eee1aeb9ff6bd1 gcc/c-family/c-cilkplus.c ! ad80df99d116311ca9bd2cba2b48e75b gcc/c-family/c-common.c 2ace27db32acd08f6b79a83ac2586e45 gcc/c-family/c-common.def 9f20703bcd296e28b53330fdacbaa6c4 gcc/c-family/c-common.h 2726890948ddd8a7c99836847c4c465b gcc/c-family/c-cppbuiltin.c *************** c40da6434275aba5adccc92809e6e2d6 gcc/c- *** 2777,2783 **** 969f5257abd1441eb2e44ec57beac8a3 gcc/c-family/c-lex.c f9fc887cc07ce21721909e6cc63fe030 gcc/c-family/c-objc.h f10a78fbf89addf947056a7351a1eaad gcc/c-family/c-omp.c ! 39020d7f69c32d241015c39dff40d502 gcc/c-family/c-opts.c b243e9180d094b7539387b07231deb33 gcc/c-family/c-pch.c 25b59b2fa2b392ea34e1eafa54f0641a gcc/c-family/c-ppoutput.c 6d8207ba65156b5bc18d732e7e97b8fa gcc/c-family/c-pragma.c --- 2780,2786 ---- 969f5257abd1441eb2e44ec57beac8a3 gcc/c-family/c-lex.c f9fc887cc07ce21721909e6cc63fe030 gcc/c-family/c-objc.h f10a78fbf89addf947056a7351a1eaad gcc/c-family/c-omp.c ! effc8ea1b69a9bc9bc97432bfb3c376a gcc/c-family/c-opts.c b243e9180d094b7539387b07231deb33 gcc/c-family/c-pch.c 25b59b2fa2b392ea34e1eafa54f0641a gcc/c-family/c-ppoutput.c 6d8207ba65156b5bc18d732e7e97b8fa gcc/c-family/c-pragma.c *************** e61eafb842ffca3b21e6acaf62b9d679 gcc/c- *** 2788,2818 **** 6c692037c0b465e9089e22eb10598f7e gcc/c-family/c-target-def.h 9aafa99768218e9494b7557242b65117 gcc/c-family/c-target.def 84c72ad7037868dfe6b3ea01496d2b74 gcc/c-family/c-target.h ! c332b723ec991da5fb10d4b3b450baf6 gcc/c-family/c-ubsan.c ! 392b541b5038adb62676d41a74001649 gcc/c-family/c-ubsan.h cff22aa92cff7c3a722057eb507d5297 gcc/c-family/c.opt 087e1ce4fd7400b0b286e3c2c7bd9aa4 gcc/c-family/cilk.c 7deafa20602c6826937fab0a455cc8ed gcc/c-family/cppspec.c dad64a3c28e8bbc124ca8c2f3a7a9f69 gcc/c-family/stub-objc.c ! 85e17987ae520b90b997138684fdec9c gcc/c/ChangeLog 9cdf859ec7692fe84b67ba9109e3995e gcc/c/Make-lang.in 5bb4a410264b7f7ac0da9ddcffd92210 gcc/c/c-array-notation.c 6d3e1a369a7f78b2f8b9d9f0f6f8aff7 gcc/c/c-aux-info.c 75e6188c864e3e7a0398e821f83a49e6 gcc/c/c-convert.c ! ecc8bfdd3c268b7b211894952d5c07fc gcc/c/c-decl.c 7abaf0d72170be02c36b07d3105cdb5d gcc/c/c-errors.c ec05f0ce37695da803820ab28dd14147 gcc/c/c-fold.c 26eb1071d6015871e3f87f989c17ee2f gcc/c/c-lang.c 88a01d3181a5b0369e3febd6acfe9520 gcc/c/c-lang.h 8cac2a5e96973c846bd33bb75d3f651d gcc/c/c-objc-common.c 1092d3b7a8d0bc846e6d7f7433692208 gcc/c/c-objc-common.h ! 99f360f887deb4bc4197d0ec6f6d6105 gcc/c/c-parser.c 9b1855479c2c36717fefaba6896f2f8d gcc/c/c-tree.h ! 53207cec63783ceccc3bd6b1b7735c4e gcc/c/c-typeck.c 3747bb41e8fd6a5de51dd6e7a7a47970 gcc/c/config-lang.in 48ad75424472d7bdc1b734bf90e32a67 gcc/c/gccspec.c 82c12673c34f23c306e289a9143864bc gcc/caller-save.c ! 9e1a94e39fbf3c650570aa64ccd735ad gcc/calls.c f7110748a1375215f4469bde141b3432 gcc/calls.h 0d087c05ff5dd25db84dedfbaf568d4b gcc/ccmp.c d3d5b380ad6f749bd8db65a92d79e3ee gcc/ccmp.h --- 2791,2821 ---- 6c692037c0b465e9089e22eb10598f7e gcc/c-family/c-target-def.h 9aafa99768218e9494b7557242b65117 gcc/c-family/c-target.def 84c72ad7037868dfe6b3ea01496d2b74 gcc/c-family/c-target.h ! 4e15a8d2d61bd9a0e7e2bedef894cf26 gcc/c-family/c-ubsan.c ! 702dab38e1352a22011d6ccb5b2e5596 gcc/c-family/c-ubsan.h cff22aa92cff7c3a722057eb507d5297 gcc/c-family/c.opt 087e1ce4fd7400b0b286e3c2c7bd9aa4 gcc/c-family/cilk.c 7deafa20602c6826937fab0a455cc8ed gcc/c-family/cppspec.c dad64a3c28e8bbc124ca8c2f3a7a9f69 gcc/c-family/stub-objc.c ! 8deef7bd6ea882b3426ab41c122fcaa6 gcc/c/ChangeLog 9cdf859ec7692fe84b67ba9109e3995e gcc/c/Make-lang.in 5bb4a410264b7f7ac0da9ddcffd92210 gcc/c/c-array-notation.c 6d3e1a369a7f78b2f8b9d9f0f6f8aff7 gcc/c/c-aux-info.c 75e6188c864e3e7a0398e821f83a49e6 gcc/c/c-convert.c ! 3be1120b3ced7298341889daa80f5c21 gcc/c/c-decl.c 7abaf0d72170be02c36b07d3105cdb5d gcc/c/c-errors.c ec05f0ce37695da803820ab28dd14147 gcc/c/c-fold.c 26eb1071d6015871e3f87f989c17ee2f gcc/c/c-lang.c 88a01d3181a5b0369e3febd6acfe9520 gcc/c/c-lang.h 8cac2a5e96973c846bd33bb75d3f651d gcc/c/c-objc-common.c 1092d3b7a8d0bc846e6d7f7433692208 gcc/c/c-objc-common.h ! e4908a290c7d655df459c0073af10733 gcc/c/c-parser.c 9b1855479c2c36717fefaba6896f2f8d gcc/c/c-tree.h ! 8bd41cbf5446bc7f11a969f236ec636b gcc/c/c-typeck.c 3747bb41e8fd6a5de51dd6e7a7a47970 gcc/c/config-lang.in 48ad75424472d7bdc1b734bf90e32a67 gcc/c/gccspec.c 82c12673c34f23c306e289a9143864bc gcc/caller-save.c ! a08670dbd137544351acb8128dc2f6be gcc/calls.c f7110748a1375215f4469bde141b3432 gcc/calls.h 0d087c05ff5dd25db84dedfbaf568d4b gcc/ccmp.c d3d5b380ad6f749bd8db65a92d79e3ee gcc/ccmp.h *************** e40d94d671641c4d2a68835c259d8098 gcc/cf *** 2836,2846 **** 6b8000ec10e5f8d86a76268393bcb5a2 gcc/cfgloopmanip.h 0e5a7f5771e6f0aeb4ab18b86f9b38ee gcc/cfgrtl.c c5f49aa0380336a2a865262bdb6edf72 gcc/cfgrtl.h ! 2fedab6ca23bee11f601afc81abecadf gcc/cgraph.c ! 7605193302a08a7aa5813a2007e874ef gcc/cgraph.h 6db406b55343fb518e9a72363f82202e gcc/cgraphbuild.c ! 0dd454c4df9ab62c991b406f6ab4bf4f gcc/cgraphclones.c ! 0688d02f197ad8c981846efccb66bfc3 gcc/cgraphunit.c 0c9c8aa562ac171f10015c1043084ef9 gcc/chkp-builtins.def 07ea027630ae40e86ad846b7cbadaf7e gcc/cif-code.def 128e655a250477dc887f54bdde9fd902 gcc/cilk-builtins.def --- 2839,2849 ---- 6b8000ec10e5f8d86a76268393bcb5a2 gcc/cfgloopmanip.h 0e5a7f5771e6f0aeb4ab18b86f9b38ee gcc/cfgrtl.c c5f49aa0380336a2a865262bdb6edf72 gcc/cfgrtl.h ! cc18f6e807e83ead91e77e951985c3e7 gcc/cgraph.c ! 50152725336ce062d5da807b011062e3 gcc/cgraph.h 6db406b55343fb518e9a72363f82202e gcc/cgraphbuild.c ! 8cba3dee2bc5bac28887424884235c2f gcc/cgraphclones.c ! c7e06f5dfb81150c5b67017b54ebe577 gcc/cgraphunit.c 0c9c8aa562ac171f10015c1043084ef9 gcc/chkp-builtins.def 07ea027630ae40e86ad846b7cbadaf7e gcc/cif-code.def 128e655a250477dc887f54bdde9fd902 gcc/cilk-builtins.def *************** c01a9dcd3800482b2cda5629d2a70ec0 gcc/co *** 2854,2862 **** ff0562eab329938aa3f51db0dc404c54 gcc/collect2.c b5a8f10278340602c7a865cfc3771a16 gcc/collect2.h b71fd257dfe7683bfb4bcbbbb4a818d1 gcc/combine-stack-adj.c ! ae18fc47c0d5e33cc00150af2f7d7a50 gcc/combine.c c48799fbbb1868cf29a46c9e0a1f352d gcc/common.md ! 579e327cd15555e852cf84c1f2ac862f gcc/common.opt 82c2449a88fb549098771259232e29aa gcc/common/common-target-def.h 9f63fb150c4ecdf8fb7b94d562d837d4 gcc/common/common-target.def 4dac4353a3b07e61cb35aa44b0a1fa4b gcc/common/common-target.h --- 2857,2865 ---- ff0562eab329938aa3f51db0dc404c54 gcc/collect2.c b5a8f10278340602c7a865cfc3771a16 gcc/collect2.h b71fd257dfe7683bfb4bcbbbb4a818d1 gcc/combine-stack-adj.c ! 4677e833fa843bc08ce425d5672f29a6 gcc/combine.c c48799fbbb1868cf29a46c9e0a1f352d gcc/common.md ! 22b0da68e21100e6d454da14f1ff512a gcc/common.opt 82c2449a88fb549098771259232e29aa gcc/common/common-target-def.h 9f63fb150c4ecdf8fb7b94d562d837d4 gcc/common/common-target.def 4dac4353a3b07e61cb35aa44b0a1fa4b gcc/common/common-target.h *************** e7c872dbe8d1a1d2f4a90b7c91b0f69a gcc/co *** 2910,2917 **** 833a4f3b8d4bd41edd9548e426fd27b3 gcc/compare-elim.c 5d296c1586f1d268a85c2aa0a3b4d64a gcc/conditions.h 9f336f22045efcaa67e235fba1bc08d6 gcc/config.build ! b6e0dda7724b8c2dab50d90c24afd90d gcc/config.gcc ! 75d9643d9dc2c2d16c12cdcb12dd361a gcc/config.host 4e2947731497409633a627de2c11ab97 gcc/config.in 8e697813dc96ca90f5d0f4c196efe2cc gcc/config/README b94306d00c5458b99b6b45830bf1eae6 gcc/config/aarch64/aarch64-arches.def --- 2913,2920 ---- 833a4f3b8d4bd41edd9548e426fd27b3 gcc/compare-elim.c 5d296c1586f1d268a85c2aa0a3b4d64a gcc/conditions.h 9f336f22045efcaa67e235fba1bc08d6 gcc/config.build ! 82dd0dae93ff938783835e90935a7cdd gcc/config.gcc ! 08d30509a1414b1a303508475dd169de gcc/config.host 4e2947731497409633a627de2c11ab97 gcc/config.in 8e697813dc96ca90f5d0f4c196efe2cc gcc/config/README b94306d00c5458b99b6b45830bf1eae6 gcc/config/aarch64/aarch64-arches.def *************** b437366560c1a1e4affc8091f518829c gcc/co *** 2921,2941 **** 72ab79e2036fbde00d2e57fb18c4f07f gcc/config/aarch64/aarch64-cost-tables.h 03496aa80a36e18b7770069366ba2fac gcc/config/aarch64/aarch64-elf-raw.h 9a373cd901003bd32ba508635a8e3637 gcc/config/aarch64/aarch64-elf.h 58de924f48e7f259aceec9fa6e302122 gcc/config/aarch64/aarch64-fusion-pairs.def 42557678ba9f7004a8b886fe0c864e20 gcc/config/aarch64/aarch64-ldpstp.md 6d16b998b9f2218e78706db1526ac2d0 gcc/config/aarch64/aarch64-linux.h 9975d5306f1abb92695b558133cf1513 gcc/config/aarch64/aarch64-modes.def 9ac39a26639cd8b4ff912beb9d5b6a87 gcc/config/aarch64/aarch64-option-extensions.def 3f9b7aaf2703c560457dadd6e0c9148b gcc/config/aarch64/aarch64-opts.h ! 5e44cc5092927352daf58d5d06792e96 gcc/config/aarch64/aarch64-protos.h 34b37d5443fa4b7761945c006d214aff gcc/config/aarch64/aarch64-simd-builtin-types.def 2900ce100d2c396ab04379ddcaebb97d gcc/config/aarch64/aarch64-simd-builtins.def ! d9316f824c3e2ed2fe92b3216a75a60f gcc/config/aarch64/aarch64-simd.md e71203d59ad9d88352c651bf54967d4e gcc/config/aarch64/aarch64-tune.md 56e698ddd35d4d45d1b27f04173c27cc gcc/config/aarch64/aarch64-tuning-flags.def ! 9feb651c0986d193c190812e20f20fa3 gcc/config/aarch64/aarch64.c ! d878b72c5ad6aa7f098423969a9fb698 gcc/config/aarch64/aarch64.h ! d2cfa1a317c02edb13a710a4715f83bf gcc/config/aarch64/aarch64.md 8186400b6ebc5890fb03c1c392946923 gcc/config/aarch64/aarch64.opt ffcb2d86bab40fbb01226fcbac5f8afb gcc/config/aarch64/arm_acle.h 2307be37347862696a1710a987cb4f58 gcc/config/aarch64/arm_neon.h --- 2924,2945 ---- 72ab79e2036fbde00d2e57fb18c4f07f gcc/config/aarch64/aarch64-cost-tables.h 03496aa80a36e18b7770069366ba2fac gcc/config/aarch64/aarch64-elf-raw.h 9a373cd901003bd32ba508635a8e3637 gcc/config/aarch64/aarch64-elf.h + c107fe312939ec6f04e3e951ef5d6d43 gcc/config/aarch64/aarch64-freebsd.h 58de924f48e7f259aceec9fa6e302122 gcc/config/aarch64/aarch64-fusion-pairs.def 42557678ba9f7004a8b886fe0c864e20 gcc/config/aarch64/aarch64-ldpstp.md 6d16b998b9f2218e78706db1526ac2d0 gcc/config/aarch64/aarch64-linux.h 9975d5306f1abb92695b558133cf1513 gcc/config/aarch64/aarch64-modes.def 9ac39a26639cd8b4ff912beb9d5b6a87 gcc/config/aarch64/aarch64-option-extensions.def 3f9b7aaf2703c560457dadd6e0c9148b gcc/config/aarch64/aarch64-opts.h ! f2d064a151addbd68d372321f727724f gcc/config/aarch64/aarch64-protos.h 34b37d5443fa4b7761945c006d214aff gcc/config/aarch64/aarch64-simd-builtin-types.def 2900ce100d2c396ab04379ddcaebb97d gcc/config/aarch64/aarch64-simd-builtins.def ! 62ff772d53a166c2e7819a2dbe123cd5 gcc/config/aarch64/aarch64-simd.md e71203d59ad9d88352c651bf54967d4e gcc/config/aarch64/aarch64-tune.md 56e698ddd35d4d45d1b27f04173c27cc gcc/config/aarch64/aarch64-tuning-flags.def ! 7f63aa7c7f287f6bd7c41c05ada3d3d0 gcc/config/aarch64/aarch64.c ! 5254b1a742c2995e341dc3ca3e6152fa gcc/config/aarch64/aarch64.h ! c04b952281f839b9afee909c26c0ec15 gcc/config/aarch64/aarch64.md 8186400b6ebc5890fb03c1c392946923 gcc/config/aarch64/aarch64.opt ffcb2d86bab40fbb01226fcbac5f8afb gcc/config/aarch64/arm_acle.h 2307be37347862696a1710a987cb4f58 gcc/config/aarch64/arm_neon.h *************** ef04105e72304d0dadcfab0c7e6dcdb7 gcc/co *** 2952,2957 **** --- 2956,2962 ---- 7f1b7a8ae9c8e03d7a6fa2ba57fed6ff gcc/config/aarch64/predicates.md 5c37bae63e5016bded0d64a50d04985d gcc/config/aarch64/rtems.h 58f273b6c00b788bdeb6f33d02b151da gcc/config/aarch64/t-aarch64 + 0009b53648df6aa7d54ca692f1ee21e7 gcc/config/aarch64/t-aarch64-freebsd ed25b8a49c845978dc3fc8336b0a7336 gcc/config/aarch64/t-aarch64-linux 3df2e3d04b3963a1d0e9d24a05928719 gcc/config/aarch64/thunderx.md 8b41b511cae4a5eda35cf19755875d5a gcc/config/aarch64/x-aarch64 *************** ad543e30d590f678c2abbfb04e300700 gcc/co *** 3006,3012 **** 74de244fd60b2d76a3787960d782373f gcc/config/arm/aarch-cost-tables.h f2b572d07746e403fd525bf9691ee2a5 gcc/config/arm/aout.h 62fcdf218b75986907eca422e13aabd4 gcc/config/arm/arm-arches.def ! e4a314e21e266db6c5d485e913a6885c gcc/config/arm/arm-builtins.c 1e0456dd3a7822f2fa3e26f77e2c2d26 gcc/config/arm/arm-c.c 65b5dc7fa9360d10a9ca86119c20ba77 gcc/config/arm/arm-cores.def b63afb8e425edc52c016b6c15066845e gcc/config/arm/arm-fixed.md --- 3011,3017 ---- 74de244fd60b2d76a3787960d782373f gcc/config/arm/aarch-cost-tables.h f2b572d07746e403fd525bf9691ee2a5 gcc/config/arm/aout.h 62fcdf218b75986907eca422e13aabd4 gcc/config/arm/arm-arches.def ! 45c137a4c7f246222345ce652c93ee34 gcc/config/arm/arm-builtins.c 1e0456dd3a7822f2fa3e26f77e2c2d26 gcc/config/arm/arm-c.c 65b5dc7fa9360d10a9ca86119c20ba77 gcc/config/arm/arm-cores.def b63afb8e425edc52c016b6c15066845e gcc/config/arm/arm-fixed.md *************** b63afb8e425edc52c016b6c15066845e gcc/co *** 3015,3026 **** 6c53f95c2d0c8e4fecf3ad01be8d9483 gcc/config/arm/arm-ldmstm.ml 9261df1518ae5954dc8389ab14719345 gcc/config/arm/arm-modes.def 6bf89ad14d0fd9ff381b329241816539 gcc/config/arm/arm-opts.h ! ea9b2d762054d9652504eeb604ead9ed gcc/config/arm/arm-protos.h b1cbf9ca4f296f2f39987d24e0af2530 gcc/config/arm/arm-simd-builtin-types.def c103dfefc6fcb9ebb20a29729bfecb69 gcc/config/arm/arm-tables.opt 3f73ffc85b17a98310aef5b53adc5d98 gcc/config/arm/arm-tune.md ! 114e32156e92f3d4478a92054818c499 gcc/config/arm/arm.c ! 23e54a7c9fe7e1c62983bdd39f19951d gcc/config/arm/arm.h 7b2204cc2a5460036fccd7c995aaedcf gcc/config/arm/arm.md 2d7e7f27748045f2d77a7377fda31d5e gcc/config/arm/arm.opt 6baef6ec8641b9abc7cb7b9708bf05b6 gcc/config/arm/arm1020e.md --- 3020,3031 ---- 6c53f95c2d0c8e4fecf3ad01be8d9483 gcc/config/arm/arm-ldmstm.ml 9261df1518ae5954dc8389ab14719345 gcc/config/arm/arm-modes.def 6bf89ad14d0fd9ff381b329241816539 gcc/config/arm/arm-opts.h ! 97da565b3597d910959ff967959cca3e gcc/config/arm/arm-protos.h b1cbf9ca4f296f2f39987d24e0af2530 gcc/config/arm/arm-simd-builtin-types.def c103dfefc6fcb9ebb20a29729bfecb69 gcc/config/arm/arm-tables.opt 3f73ffc85b17a98310aef5b53adc5d98 gcc/config/arm/arm-tune.md ! 27c81004bfff69ffe22b7958e4c169b5 gcc/config/arm/arm.c ! bbb7cb0bfec1d758c0f8c723fe6a2467 gcc/config/arm/arm.h 7b2204cc2a5460036fccd7c995aaedcf gcc/config/arm/arm.md 2d7e7f27748045f2d77a7377fda31d5e gcc/config/arm/arm.opt 6baef6ec8641b9abc7cb7b9708bf05b6 gcc/config/arm/arm1020e.md *************** b08d4b1581307b34bb5a9792a0a09330 gcc/co *** 3074,3084 **** a979353df3e883287991c9ba806b8df8 gcc/config/arm/marvell-pj4.md fe891f8062dae2511030eacc9a2e8fa7 gcc/config/arm/mmintrin.h 317bf696d86ee48e9a3de08c927d58e8 gcc/config/arm/neon-testgen.ml ! 0a2b9881557ec3e8105a7af7421e9578 gcc/config/arm/neon.md 091cc79845a605488bee16706acab656 gcc/config/arm/neon.ml 2db383036041282bb96356c285f34a10 gcc/config/arm/netbsd-elf.h 930b6ba0f55f295476ed149f3efd7df5 gcc/config/arm/predicates.md ! c23bcd49de4c1ae905a22bb5d6f1ac78 gcc/config/arm/rtems.h c009ad3a5b938208225f76cd5bceab97 gcc/config/arm/semi.h 38f06710a04b9c6fdfd4d6e460657091 gcc/config/arm/symbian.h ed021f4200f3dcd2a16bb8f16cee10f3 gcc/config/arm/sync.md --- 3079,3089 ---- a979353df3e883287991c9ba806b8df8 gcc/config/arm/marvell-pj4.md fe891f8062dae2511030eacc9a2e8fa7 gcc/config/arm/mmintrin.h 317bf696d86ee48e9a3de08c927d58e8 gcc/config/arm/neon-testgen.ml ! e66f5a57d8515f788fd946555e3da560 gcc/config/arm/neon.md 091cc79845a605488bee16706acab656 gcc/config/arm/neon.ml 2db383036041282bb96356c285f34a10 gcc/config/arm/netbsd-elf.h 930b6ba0f55f295476ed149f3efd7df5 gcc/config/arm/predicates.md ! 0de1264a4289106763caf9dc80fd74bc gcc/config/arm/rtems.h c009ad3a5b938208225f76cd5bceab97 gcc/config/arm/semi.h 38f06710a04b9c6fdfd4d6e460657091 gcc/config/arm/symbian.h ed021f4200f3dcd2a16bb8f16cee10f3 gcc/config/arm/sync.md *************** acb8604f5d84dde1d6897a67b4d6be18 gcc/co *** 3116,3122 **** 4c3c46eb845e3505658b81b8eaa14288 gcc/config/avr/avr-modes.def 0fffc0f61c26f4c9de873ad542b094ed gcc/config/avr/avr-protos.h 41b9882721bdec25585513f697848b5d gcc/config/avr/avr-stdint.h ! 11ca469d9c83640c3db427c44be91acb gcc/config/avr/avr.c e85dcf00374c22efe74da576e0e0f052 gcc/config/avr/avr.h e7c7f8ca590b4f600384b83d1b73062f gcc/config/avr/avr.md 97ae0e97c66153cd01ba33e6dd23a191 gcc/config/avr/avr.opt --- 3121,3127 ---- 4c3c46eb845e3505658b81b8eaa14288 gcc/config/avr/avr-modes.def 0fffc0f61c26f4c9de873ad542b094ed gcc/config/avr/avr-protos.h 41b9882721bdec25585513f697848b5d gcc/config/avr/avr-stdint.h ! 75865a0994ceb679f8762ad375e15065 gcc/config/avr/avr.c e85dcf00374c22efe74da576e0e0f052 gcc/config/avr/avr.h e7c7f8ca590b4f600384b83d1b73062f gcc/config/avr/avr.md 97ae0e97c66153cd01ba33e6dd23a191 gcc/config/avr/avr.opt *************** c4c4f650f4dbd3a648a801ce6eda092c gcc/co *** 3203,3209 **** 1da3ab8fe0f51b88e01626f5858f59fc gcc/config/cris/t-elfmulti 5657034355d2720466dad6b98f794a8f gcc/config/cris/t-linux c8566e4b8192be8ea5341d9f2a7e9b57 gcc/config/darwin-c.c ! 1ae5fbab2927cf882b3715c192f18f28 gcc/config/darwin-driver.c bf399773df7c70ed0dd0750e2cabbb64 gcc/config/darwin-f.c 4ab1378170f290be0982057813dbf2f5 gcc/config/darwin-ppc-ldouble-patch.def 9a96119bd809f334545f28e92af4d7da gcc/config/darwin-protos.h --- 3208,3214 ---- 1da3ab8fe0f51b88e01626f5858f59fc gcc/config/cris/t-elfmulti 5657034355d2720466dad6b98f794a8f gcc/config/cris/t-linux c8566e4b8192be8ea5341d9f2a7e9b57 gcc/config/darwin-c.c ! 356c91dff2430bbbb56e2140ea538686 gcc/config/darwin-driver.c bf399773df7c70ed0dd0750e2cabbb64 gcc/config/darwin-f.c 4ab1378170f290be0982057813dbf2f5 gcc/config/darwin-ppc-ldouble-patch.def 9a96119bd809f334545f28e92af4d7da gcc/config/darwin-protos.h *************** ecc53305b08aa880f8075070842bcb56 gcc/co *** 3304,3323 **** 62bb4c93aafaacd519b018cbfb28713c gcc/config/i386/athlon.md e455413df71787859a26fdacf93bd5ba gcc/config/i386/atom.md dc6f62ede904e2f3de2037e7f24ecb0d gcc/config/i386/att.h ! 9d1877eb7a42c1ae4d1b6a3bbc25b6cc gcc/config/i386/avx2intrin.h ! 529c902186eed70ee023771a87349c94 gcc/config/i386/avx512bwintrin.h dbce93d80e05b41e7c9310744086319c gcc/config/i386/avx512cdintrin.h 60c601281f9198e3d8010430b8c76109 gcc/config/i386/avx512dqintrin.h 88a76e2acc1ff36354da2b635a29f110 gcc/config/i386/avx512erintrin.h ! ed9402ebeb9c5f2be7f1ed59632baed9 gcc/config/i386/avx512fintrin.h fd40a3994a031d23494319eeb5890e14 gcc/config/i386/avx512ifmaintrin.h 230a13a5117589196f0c0d6ddd19a459 gcc/config/i386/avx512ifmavlintrin.h ! 0ff51a630663417733439a8c37ead341 gcc/config/i386/avx512pfintrin.h e3719804447e4a86d250b6aa4a73d139 gcc/config/i386/avx512vbmiintrin.h 1e90300c6d08094855c82e4a975a48d9 gcc/config/i386/avx512vbmivlintrin.h dd65e9dc8e91ad003d4b4b0c64adda4f gcc/config/i386/avx512vlbwintrin.h d5ea6d87b81e9e28da46b0954847447b gcc/config/i386/avx512vldqintrin.h ! 1b76b348b3dd66b5c4b345848ff3782b gcc/config/i386/avx512vlintrin.h 23244ee6ec69094018c7e88b118e167f gcc/config/i386/avxintrin.h 95157e032097240e8dbbff5808ec2212 gcc/config/i386/avxmath.h 9fa05f800762ec6401f38786426c964e gcc/config/i386/bdver1.md --- 3309,3328 ---- 62bb4c93aafaacd519b018cbfb28713c gcc/config/i386/athlon.md e455413df71787859a26fdacf93bd5ba gcc/config/i386/atom.md dc6f62ede904e2f3de2037e7f24ecb0d gcc/config/i386/att.h ! 8189f763d53d0f9dc831ed8e3cf78698 gcc/config/i386/avx2intrin.h ! c68a78a785cc22c67f0f258513b89af0 gcc/config/i386/avx512bwintrin.h dbce93d80e05b41e7c9310744086319c gcc/config/i386/avx512cdintrin.h 60c601281f9198e3d8010430b8c76109 gcc/config/i386/avx512dqintrin.h 88a76e2acc1ff36354da2b635a29f110 gcc/config/i386/avx512erintrin.h ! 3c4706c4cc6dea2d5b398585d439b332 gcc/config/i386/avx512fintrin.h fd40a3994a031d23494319eeb5890e14 gcc/config/i386/avx512ifmaintrin.h 230a13a5117589196f0c0d6ddd19a459 gcc/config/i386/avx512ifmavlintrin.h ! 3db975ae169b88fc867d8c79ae116ef3 gcc/config/i386/avx512pfintrin.h e3719804447e4a86d250b6aa4a73d139 gcc/config/i386/avx512vbmiintrin.h 1e90300c6d08094855c82e4a975a48d9 gcc/config/i386/avx512vbmivlintrin.h dd65e9dc8e91ad003d4b4b0c64adda4f gcc/config/i386/avx512vlbwintrin.h d5ea6d87b81e9e28da46b0954847447b gcc/config/i386/avx512vldqintrin.h ! 5562d45ba5cebd5bea62a7d06079bb9a gcc/config/i386/avx512vlintrin.h 23244ee6ec69094018c7e88b118e167f gcc/config/i386/avxintrin.h 95157e032097240e8dbbff5808ec2212 gcc/config/i386/avxmath.h 9fa05f800762ec6401f38786426c964e gcc/config/i386/bdver1.md *************** fe17ca5109af0e6e93b74bae231d1a55 gcc/co *** 3334,3340 **** 876790e99f6c0bb421e1492c7ea46ff0 gcc/config/i386/clzerointrin.h a6979d6ddcc5bb8ecf2a26f5ea34c71c gcc/config/i386/constraints.md 71baed36fc56f65d8c91aaefd5758aa1 gcc/config/i386/core2.md ! 6be298791a58e8a9666c8d7e2a92e00b gcc/config/i386/cpuid.h 7fee26d8fedd334aa6fcd4bdc08cffb3 gcc/config/i386/cross-stdarg.h 69f9c11b17063c896813c5ca9d5b17eb gcc/config/i386/crtdll.h ac384469cee2e84b1be9baf66917497c gcc/config/i386/cygming.h --- 3339,3345 ---- 876790e99f6c0bb421e1492c7ea46ff0 gcc/config/i386/clzerointrin.h a6979d6ddcc5bb8ecf2a26f5ea34c71c gcc/config/i386/constraints.md 71baed36fc56f65d8c91aaefd5758aa1 gcc/config/i386/core2.md ! af1276d5c47a51a9ed8ea5d69de248a1 gcc/config/i386/cpuid.h 7fee26d8fedd334aa6fcd4bdc08cffb3 gcc/config/i386/cross-stdarg.h 69f9c11b17063c896813c5ca9d5b17eb gcc/config/i386/crtdll.h ac384469cee2e84b1be9baf66917497c gcc/config/i386/cygming.h *************** bf44099b2cb8c3551496ae076701ec22 gcc/co *** 3360,3366 **** b2fbe0a751c65b3c78b2dca04b902297 gcc/config/i386/fxsrintrin.h 3ae96fd541e363932260a487465f421c gcc/config/i386/gas.h ade2d1412285926ca3c5d45ec6bae8a4 gcc/config/i386/geode.md ! d04869c34459472b41b38f9f3bb9fd2e gcc/config/i386/gmm_malloc.h f830d2e889bb02408a54d531021c6cc8 gcc/config/i386/gnu-user-common.h e1d8df2e25020f981d9838adb79a77d0 gcc/config/i386/gnu-user.h fcaefa2eebd685b349d58b0be0098d08 gcc/config/i386/gnu-user64.h --- 3365,3371 ---- b2fbe0a751c65b3c78b2dca04b902297 gcc/config/i386/fxsrintrin.h 3ae96fd541e363932260a487465f421c gcc/config/i386/gas.h ade2d1412285926ca3c5d45ec6bae8a4 gcc/config/i386/geode.md ! ebc0f17587e0304e3b3a4b276076dfbc gcc/config/i386/gmm_malloc.h f830d2e889bb02408a54d531021c6cc8 gcc/config/i386/gnu-user-common.h e1d8df2e25020f981d9838adb79a77d0 gcc/config/i386/gnu-user.h fcaefa2eebd685b349d58b0be0098d08 gcc/config/i386/gnu-user64.h *************** fcaefa2eebd685b349d58b0be0098d08 gcc/co *** 3371,3388 **** 7207180c0653cb9c7507f26a9a814675 gcc/config/i386/host-i386-darwin.c b80037f63f5fd458518208bbd7dbaa4f gcc/config/i386/host-mingw32.c 47ac29c21a60ee2ca29d54ea4a345deb gcc/config/i386/i386-builtin-types.awk ! 38a33f510a42eb2a5d16044fee2084ba gcc/config/i386/i386-builtin-types.def 5987dd36c379ccb0419cbb675d58dd96 gcc/config/i386/i386-c.c c29497fe4c1e5389895075d220252ca8 gcc/config/i386/i386-interix.h 1c71860a666631f1a174dea14c52dbff gcc/config/i386/i386-modes.def ac0b4653ef3d1e8200e8efbf73c5d8f0 gcc/config/i386/i386-opts.h d3f3a1198cf0be4e2a3b9b10e0f761cc gcc/config/i386/i386-protos.h ! 37a1ded000aa3b1841df414c2a5f1684 gcc/config/i386/i386.c e21d3883b173794ad0c6724e144324d6 gcc/config/i386/i386.h ! 9a7bf26ca642b938c876c6ecd9f240c4 gcc/config/i386/i386.md fcfe67e0458640256c81b86e30fd5304 gcc/config/i386/i386.opt be209c39783d5218055012112fe03242 gcc/config/i386/i386elf.h ! a56c5de1cde5aaa7a3753ce09e0be661 gcc/config/i386/ia32intrin.h c86877b6f78344601b6f3c88be68407e gcc/config/i386/iamcu.h 31d107d5d14a8ed86cddbf9a06d1f80d gcc/config/i386/immintrin.h 36bf0710f7040682fece48e939caca02 gcc/config/i386/intelmic-mkoffload.c --- 3376,3393 ---- 7207180c0653cb9c7507f26a9a814675 gcc/config/i386/host-i386-darwin.c b80037f63f5fd458518208bbd7dbaa4f gcc/config/i386/host-mingw32.c 47ac29c21a60ee2ca29d54ea4a345deb gcc/config/i386/i386-builtin-types.awk ! deebf656960fb03db30ee8cf5088fa22 gcc/config/i386/i386-builtin-types.def 5987dd36c379ccb0419cbb675d58dd96 gcc/config/i386/i386-c.c c29497fe4c1e5389895075d220252ca8 gcc/config/i386/i386-interix.h 1c71860a666631f1a174dea14c52dbff gcc/config/i386/i386-modes.def ac0b4653ef3d1e8200e8efbf73c5d8f0 gcc/config/i386/i386-opts.h d3f3a1198cf0be4e2a3b9b10e0f761cc gcc/config/i386/i386-protos.h ! 8e5cf8849582869ad5b9439125b5fa8d gcc/config/i386/i386.c e21d3883b173794ad0c6724e144324d6 gcc/config/i386/i386.h ! 3dbf0f2634e6ebf0491f0caf09e6b426 gcc/config/i386/i386.md fcfe67e0458640256c81b86e30fd5304 gcc/config/i386/i386.opt be209c39783d5218055012112fe03242 gcc/config/i386/i386elf.h ! 3f06069affcd9b661e1444aa62b433d7 gcc/config/i386/ia32intrin.h c86877b6f78344601b6f3c88be68407e gcc/config/i386/iamcu.h 31d107d5d14a8ed86cddbf9a06d1f80d gcc/config/i386/immintrin.h 36bf0710f7040682fece48e939caca02 gcc/config/i386/intelmic-mkoffload.c *************** b498dbb5c9703bba1235c71dcd5372ca gcc/co *** 3397,3403 **** bf3c62346160f7c1f720e38651bfd9f5 gcc/config/i386/linux-common.h edc9521585efeb1953f50f9273d4b90d gcc/config/i386/linux.h 0e66de73af285b2c1420ed2cd5c30f74 gcc/config/i386/linux64.h ! 8d63719e1894a7895749004ece05758b gcc/config/i386/lwpintrin.h 0035dee4cedaa075ff03c87a739e6e1d gcc/config/i386/lynx.h 45512319928b01119f32f7322830b685 gcc/config/i386/lzcntintrin.h 90919473adc02dc5b2cc4438c25bba54 gcc/config/i386/mingw-pthread.h --- 3402,3408 ---- bf3c62346160f7c1f720e38651bfd9f5 gcc/config/i386/linux-common.h edc9521585efeb1953f50f9273d4b90d gcc/config/i386/linux.h 0e66de73af285b2c1420ed2cd5c30f74 gcc/config/i386/linux64.h ! e5f86d8086d06b791e0e16bee0ed86e1 gcc/config/i386/lwpintrin.h 0035dee4cedaa075ff03c87a739e6e1d gcc/config/i386/lynx.h 45512319928b01119f32f7322830b685 gcc/config/i386/lzcntintrin.h 90919473adc02dc5b2cc4438c25bba54 gcc/config/i386/mingw-pthread.h *************** e1c203e26354ffe66c7cac7886122b64 gcc/co *** 3406,3414 **** 47a49cd0f968a4269d3fb70cd1d34cd1 gcc/config/i386/mingw-w64.opt 7bf3e9078d8336a8ba2e99d0147c89de gcc/config/i386/mingw.opt 3fce1640bc20f36b48acc80a5dc02ea7 gcc/config/i386/mingw32.h ! 2178140f5056aa16b4f2410522796b09 gcc/config/i386/mm3dnow.h ! 07cc882e5dfdfa349d6d27d3145ef6ac gcc/config/i386/mmintrin.h ! bb3d9202affa8c14f3271974ecb6ffe5 gcc/config/i386/mmx.md 8750c7820ea7662c22ab288c00bffb16 gcc/config/i386/msformat-c.c 7ca84a2e632096e5785038a63bbdc69f gcc/config/i386/mwaitxintrin.h fa30c7cb908ed3e5f059a0382be844db gcc/config/i386/netbsd-elf.h --- 3411,3419 ---- 47a49cd0f968a4269d3fb70cd1d34cd1 gcc/config/i386/mingw-w64.opt 7bf3e9078d8336a8ba2e99d0147c89de gcc/config/i386/mingw.opt 3fce1640bc20f36b48acc80a5dc02ea7 gcc/config/i386/mingw32.h ! 7353bf4b5acbf6fc3b2bb19f1dd12692 gcc/config/i386/mm3dnow.h ! f31a5e3804b8dea7ae7ddd5de2e4b5ec gcc/config/i386/mmintrin.h ! 2dc0afd8fd36367dd3dc61efb8126ed0 gcc/config/i386/mmx.md 8750c7820ea7662c22ab288c00bffb16 gcc/config/i386/msformat-c.c 7ca84a2e632096e5785038a63bbdc69f gcc/config/i386/mwaitxintrin.h fa30c7cb908ed3e5f059a0382be844db gcc/config/i386/netbsd-elf.h *************** b3e5b6d58424881a27b995c610fefed2 gcc/co *** 3419,3426 **** 03e5d4855215c79ace0568fbc4d34ff2 gcc/config/i386/openbsd.h d3fb09540c2d8a5e198b974f35309f80 gcc/config/i386/openbsdelf.h faf43805b91b4afc50a1814fb6257920 gcc/config/i386/pentium.md ! 1212b5174e58248ecb9715637ee092fa gcc/config/i386/pkuintrin.h ! 16a4d1b90faa49d8d6f4807915bfb419 gcc/config/i386/pmm_malloc.h 5aa912e76dac257cfe5012440f7ad90a gcc/config/i386/pmmintrin.h 7810065fc76773a3b740126a476af54d gcc/config/i386/popcntintrin.h 4dcd1cf3c734c77f06e840e1fbd678f8 gcc/config/i386/ppro.md --- 3424,3431 ---- 03e5d4855215c79ace0568fbc4d34ff2 gcc/config/i386/openbsd.h d3fb09540c2d8a5e198b974f35309f80 gcc/config/i386/openbsdelf.h faf43805b91b4afc50a1814fb6257920 gcc/config/i386/pentium.md ! cbe898aef05ed8f46e984293e1cf3b97 gcc/config/i386/pkuintrin.h ! c6c28e716fe73119003638d891187a45 gcc/config/i386/pmm_malloc.h 5aa912e76dac257cfe5012440f7ad90a gcc/config/i386/pmmintrin.h 7810065fc76773a3b740126a476af54d gcc/config/i386/popcntintrin.h 4dcd1cf3c734c77f06e840e1fbd678f8 gcc/config/i386/ppro.md *************** faf43805b91b4afc50a1814fb6257920 gcc/co *** 3428,3445 **** a0f562fc0aef289f6cdef5b931f5e39f gcc/config/i386/prfchwintrin.h 7feefb44b5c73254b20e5b7820e45ba1 gcc/config/i386/rdos.h d57b23dfe66e6405fed787f9047ce355 gcc/config/i386/rdos64.h ! 1afa6d69de8e5333a0748b291b7c5d7a gcc/config/i386/rdseedintrin.h fb13e63400cd374a20d2d437e5980267 gcc/config/i386/rtems-64.h ! a9007ee20cfb47bc1f830c01e0e0db08 gcc/config/i386/rtemself.h ! 778f69e51947eeb82b49b55afd536ab8 gcc/config/i386/rtmintrin.h ed3ee42c50a4ea2d1cccc046aa7c7306 gcc/config/i386/shaintrin.h 6d7b4d52cdc2a6db01f9c20c45be0795 gcc/config/i386/slm.md d1a02c4509457e48895953880e756b4a gcc/config/i386/smmintrin.h 0a7e726af98f6a39952052f361cdfbee gcc/config/i386/sol2.h ! 6195fa85461a3fb9be79659790a663fe gcc/config/i386/sse.md 91d7c7f7b9b34e3ae4e87882a355bf2b gcc/config/i386/ssemath.h be9c2b7e2ff5d3a32ab3d902b56762ac gcc/config/i386/stringop.def - 96f9e071c5c165d0cc21e51cfebe5b92 gcc/config/i386/stringop.opt dd538a6193ed3c62883cd3fed5dd4461 gcc/config/i386/subst.md 70c08433c23b830ca860ece2b61285e4 gcc/config/i386/sync.md 3219bc7864c7b0cb60fab1dcf0dffdf7 gcc/config/i386/sysv4.h --- 3433,3449 ---- a0f562fc0aef289f6cdef5b931f5e39f gcc/config/i386/prfchwintrin.h 7feefb44b5c73254b20e5b7820e45ba1 gcc/config/i386/rdos.h d57b23dfe66e6405fed787f9047ce355 gcc/config/i386/rdos64.h ! 4cb63ac1dba90961eed946d63cbf456b gcc/config/i386/rdseedintrin.h fb13e63400cd374a20d2d437e5980267 gcc/config/i386/rtems-64.h ! b468336ec8c9314a8b3c8738c5bbe401 gcc/config/i386/rtemself.h ! 35112115660e6f05e39831eeaafa00f8 gcc/config/i386/rtmintrin.h ed3ee42c50a4ea2d1cccc046aa7c7306 gcc/config/i386/shaintrin.h 6d7b4d52cdc2a6db01f9c20c45be0795 gcc/config/i386/slm.md d1a02c4509457e48895953880e756b4a gcc/config/i386/smmintrin.h 0a7e726af98f6a39952052f361cdfbee gcc/config/i386/sol2.h ! d19c00e2e4fdda44c4398dcf66cd5dbf gcc/config/i386/sse.md 91d7c7f7b9b34e3ae4e87882a355bf2b gcc/config/i386/ssemath.h be9c2b7e2ff5d3a32ab3d902b56762ac gcc/config/i386/stringop.def dd538a6193ed3c62883cd3fed5dd4461 gcc/config/i386/subst.md 70c08433c23b830ca860ece2b61285e4 gcc/config/i386/sync.md 3219bc7864c7b0cb60fab1dcf0dffdf7 gcc/config/i386/sysv4.h *************** d2ad92f0b7fd7b714ba96bf653c1adeb gcc/co *** 3477,3483 **** bae69273c5e47d61e99558ca73c4fabd gcc/config/i386/x-darwin 12e09c6fa27c603c6db59fbfc2a6b089 gcc/config/i386/x-i386 214d4c585b541f5f045f139c36119850 gcc/config/i386/x-mingw32 ! 03bee72a17952ef9963f8dccbefd9734 gcc/config/i386/x86-64.h dda5cbc520b915635a3d4553bc838576 gcc/config/i386/x86-tune.def 58d683e0e4dcc86fd997fc078b31f54b gcc/config/i386/x86intrin.h de5913a1cbf5d37dbbc88e8a4ded82c5 gcc/config/i386/xm-cygwin.h --- 3481,3487 ---- bae69273c5e47d61e99558ca73c4fabd gcc/config/i386/x-darwin 12e09c6fa27c603c6db59fbfc2a6b089 gcc/config/i386/x-i386 214d4c585b541f5f045f139c36119850 gcc/config/i386/x-mingw32 ! 7b415e81225fe3f7288c2824b44b6f8e gcc/config/i386/x86-64.h dda5cbc520b915635a3d4553bc838576 gcc/config/i386/x86-tune.def 58d683e0e4dcc86fd997fc078b31f54b gcc/config/i386/x86intrin.h de5913a1cbf5d37dbbc88e8a4ded82c5 gcc/config/i386/xm-cygwin.h *************** b843b8ad610c3e807808d9b2cb87336d gcc/co *** 3819,3825 **** 1478623f6c99051509aa300018b934aa gcc/config/nds32/nds32-protos.h 9f3945b0bce60ad432e0d10d2bb3778a gcc/config/nds32/nds32.c ecff011ed5dd8d6af824aa9091254cfb gcc/config/nds32/nds32.h ! 9f1ba56dfb07c05a9ae96ae3c3354f17 gcc/config/nds32/nds32.md fd57c24d9bbb5724eea121cac0ec52ea gcc/config/nds32/nds32.opt be6cb77b2dcb9edaad2ca893cd624887 gcc/config/nds32/nds32_intrinsic.h da0b1418d4267fe0b25ebfd9d278d6cc gcc/config/nds32/pipelines.md --- 3823,3829 ---- 1478623f6c99051509aa300018b934aa gcc/config/nds32/nds32-protos.h 9f3945b0bce60ad432e0d10d2bb3778a gcc/config/nds32/nds32.c ecff011ed5dd8d6af824aa9091254cfb gcc/config/nds32/nds32.h ! 85804b1207e24228a1a35c5e47d67b59 gcc/config/nds32/nds32.md fd57c24d9bbb5724eea121cac0ec52ea gcc/config/nds32/nds32.opt be6cb77b2dcb9edaad2ca893cd624887 gcc/config/nds32/nds32_intrinsic.h da0b1418d4267fe0b25ebfd9d278d6cc gcc/config/nds32/pipelines.md *************** abea4d523d1b02ef93fc69e4159b6c20 gcc/co *** 3850,3856 **** d835d08884a2846e70bef505767bd3f1 gcc/config/nios2/t-rtems c2be83b7f197d233a6ce04c2245a312a gcc/config/nvptx/mkoffload.c 71182308acd7b24f983c5c3836f21e97 gcc/config/nvptx/nvptx-protos.h ! d16914348f2acdb5a72c4e8cd5c348d9 gcc/config/nvptx/nvptx.c ee26c09dc69c862b8465425e61efb50d gcc/config/nvptx/nvptx.h b6d00d17aa4debe5cbfb686a317af311 gcc/config/nvptx/nvptx.md f20baafe92ab83b58eced858f6668a59 gcc/config/nvptx/nvptx.opt --- 3854,3860 ---- d835d08884a2846e70bef505767bd3f1 gcc/config/nios2/t-rtems c2be83b7f197d233a6ce04c2245a312a gcc/config/nvptx/mkoffload.c 71182308acd7b24f983c5c3836f21e97 gcc/config/nvptx/nvptx-protos.h ! 725e3638da02e22dc3945cec254af50e gcc/config/nvptx/nvptx.c ee26c09dc69c862b8465425e61efb50d gcc/config/nvptx/nvptx.h b6d00d17aa4debe5cbfb686a317af311 gcc/config/nvptx/nvptx.md f20baafe92ab83b58eced858f6668a59 gcc/config/nvptx/nvptx.opt *************** b76b9aadbc83e352fd348980a93f6839 gcc/co *** 3863,3869 **** be5a4a16bb0d95cffa85d9b8ab47dcab gcc/config/openbsd.opt 10050f2883a638526cdadcec0d536bf5 gcc/config/pa/constraints.md 233bf6e3a3cc27aca8f75af9403305c4 gcc/config/pa/elf.h ! 7d30be10a892671b463d495509096cf7 gcc/config/pa/pa-64.h 618754aa60af62156ee24b682f08f7c8 gcc/config/pa/pa-hpux.h d4325294a658da362fd864357238309f gcc/config/pa/pa-hpux.opt 1429e13f812177ce77dd638dc380d76f gcc/config/pa/pa-hpux10.h --- 3867,3873 ---- be5a4a16bb0d95cffa85d9b8ab47dcab gcc/config/openbsd.opt 10050f2883a638526cdadcec0d536bf5 gcc/config/pa/constraints.md 233bf6e3a3cc27aca8f75af9403305c4 gcc/config/pa/elf.h ! f1c8501c52ac479dc1cd8e11a5146a95 gcc/config/pa/pa-64.h 618754aa60af62156ee24b682f08f7c8 gcc/config/pa/pa-hpux.h d4325294a658da362fd864357238309f gcc/config/pa/pa-hpux.opt 1429e13f812177ce77dd638dc380d76f gcc/config/pa/pa-hpux10.h *************** c71c9d34d6df22094a3f27d33693c09f gcc/co *** 3880,3886 **** e1c6685604f681faea2ce89975cb7fb0 gcc/config/pa/pa-openbsd.h 7fe7a5966510922de22aeefc35c8e010 gcc/config/pa/pa-opts.h b1fa12eef4f2d69520c8e33ff00ea833 gcc/config/pa/pa-protos.h ! 9a436df6ba10cb315e4759c263bb20f7 gcc/config/pa/pa.c cf85837fdda5b34386235c1ded652a62 gcc/config/pa/pa.h e6169925aae03f7207e5ca018a354de1 gcc/config/pa/pa.md 2a55715c21637c72f4c2306798f28715 gcc/config/pa/pa.opt --- 3884,3890 ---- e1c6685604f681faea2ce89975cb7fb0 gcc/config/pa/pa-openbsd.h 7fe7a5966510922de22aeefc35c8e010 gcc/config/pa/pa-opts.h b1fa12eef4f2d69520c8e33ff00ea833 gcc/config/pa/pa-protos.h ! af5ccaf4e328676c8d7821f146be0e40 gcc/config/pa/pa.c cf85837fdda5b34386235c1ded652a62 gcc/config/pa/pa.h e6169925aae03f7207e5ca018a354de1 gcc/config/pa/pa.md 2a55715c21637c72f4c2306798f28715 gcc/config/pa/pa.opt *************** fa946996696fb3df283f1891fcd00e4b gcc/co *** 3943,3953 **** 02a3d453ca7e43f4bf70187e1c3cf346 gcc/config/rs6000/aix61.h 21c1c24d19668403ff77dc915a743342 gcc/config/rs6000/aix64.opt 1088dba38de5967f615c2c010164ec48 gcc/config/rs6000/aix71.h ! 72b7be964acfdeb0ca6642e9bb019ee4 gcc/config/rs6000/altivec.h 1ae5cce9f95be1f33759897a0e901575 gcc/config/rs6000/altivec.md ebb5e6bcfc1093c0aff7c41cd9353433 gcc/config/rs6000/biarch64.h 936aede56563f66921091a90d3d1d56a gcc/config/rs6000/cell.md ! 9311e956976879953c699d3616089827 gcc/config/rs6000/constraints.md 3989f0e14500049f924ab6bf76471a93 gcc/config/rs6000/crypto.md c85b3bacf772d069c8a138ff0cf48400 gcc/config/rs6000/darwin.h 5c9894330fc994b0302bfc4c60989175 gcc/config/rs6000/darwin.md --- 3947,3957 ---- 02a3d453ca7e43f4bf70187e1c3cf346 gcc/config/rs6000/aix61.h 21c1c24d19668403ff77dc915a743342 gcc/config/rs6000/aix64.opt 1088dba38de5967f615c2c010164ec48 gcc/config/rs6000/aix71.h ! 40a704ae160673f3bb2db3e56ac529e6 gcc/config/rs6000/altivec.h 1ae5cce9f95be1f33759897a0e901575 gcc/config/rs6000/altivec.md ebb5e6bcfc1093c0aff7c41cd9353433 gcc/config/rs6000/biarch64.h 936aede56563f66921091a90d3d1d56a gcc/config/rs6000/cell.md ! 3dc33891037141fa757d109f7826402a gcc/config/rs6000/constraints.md 3989f0e14500049f924ab6bf76471a93 gcc/config/rs6000/crypto.md c85b3bacf772d069c8a138ff0cf48400 gcc/config/rs6000/darwin.h 5c9894330fc994b0302bfc4c60989175 gcc/config/rs6000/darwin.md *************** d7243dd7fa41b04c51d52b24425b48dd gcc/co *** 3956,3962 **** 78939b2279a4d082aea92f53a289d711 gcc/config/rs6000/darwin7.h ac431f1a0b8ae0c72fc7cab9bc9e2f1d gcc/config/rs6000/darwin8.h a77da74ccfb88c7b6bcd77d4a5f98c90 gcc/config/rs6000/default64.h ! 1a96a05c3098cba8dcad9a84f4da9c74 gcc/config/rs6000/dfp.md b9490f963c3648aa2f0de7bc1cd5af58 gcc/config/rs6000/driver-rs6000.c d949390c82f3443dbfb82eef160fa0c7 gcc/config/rs6000/e300c2c3.md 85e4c2a561d394919589b92fdf2a6da3 gcc/config/rs6000/e500.h --- 3960,3966 ---- 78939b2279a4d082aea92f53a289d711 gcc/config/rs6000/darwin7.h ac431f1a0b8ae0c72fc7cab9bc9e2f1d gcc/config/rs6000/darwin8.h a77da74ccfb88c7b6bcd77d4a5f98c90 gcc/config/rs6000/default64.h ! 26ac67ba1d90a9fdd6d81d75a961319b gcc/config/rs6000/dfp.md b9490f963c3648aa2f0de7bc1cd5af58 gcc/config/rs6000/driver-rs6000.c d949390c82f3443dbfb82eef160fa0c7 gcc/config/rs6000/e300c2c3.md 85e4c2a561d394919589b92fdf2a6da3 gcc/config/rs6000/e500.h *************** d8b143420c8e25c7b2a8df221ae27589 gcc/co *** 3997,4015 **** c335f4f65801de1318cd4db8b62934ba gcc/config/rs6000/ppc-asm.h ea4871edf7de554404015404bafd83e6 gcc/config/rs6000/ppc-auxv.h 30884ec5924e409646acd1aa99423fc5 gcc/config/rs6000/ppu_intrinsics.h ! c78862a99654d926e61f2d59794985f5 gcc/config/rs6000/predicates.md fed7519f3fb7d3f6e3b9e82dd640d7c0 gcc/config/rs6000/rs6000-builtin.def ! 7baaf3b9a76f29c14d1e20e921eef7da gcc/config/rs6000/rs6000-c.c 3e5ef6c30730e4575563890ec3cfe76b gcc/config/rs6000/rs6000-cpus.def 2f0d36a3bf95d74249364237cf04e29c gcc/config/rs6000/rs6000-linux.c 192ddf2c1b6fd7fe7e53b1acadaee645 gcc/config/rs6000/rs6000-modes.def 14f48bec5cd76d2a5aada931fb1fedf4 gcc/config/rs6000/rs6000-opts.h f9e83e56b3fbfbefb1355ec6235ffa03 gcc/config/rs6000/rs6000-protos.h b43d18bcb08f2293531b3302947868a2 gcc/config/rs6000/rs6000-tables.opt ! 9108fd4f8d25b312ee2ab15711d3f21f gcc/config/rs6000/rs6000.c ! 219d2a37391d11dee8e606c70d31fa65 gcc/config/rs6000/rs6000.h ! 8aebc4f0b78fd5769423afc48630e695 gcc/config/rs6000/rs6000.md ! ca447d624d64bde7352a3632cff4e012 gcc/config/rs6000/rs6000.opt 23eae5c1992970cba9db6c157ab8c4f6 gcc/config/rs6000/rs64.md 089f55bc6e1565ba82f6d496569d3280 gcc/config/rs6000/rtems.h 510ae383bcc5df111af9d4407a82b6cb gcc/config/rs6000/secureplt.h --- 4001,4019 ---- c335f4f65801de1318cd4db8b62934ba gcc/config/rs6000/ppc-asm.h ea4871edf7de554404015404bafd83e6 gcc/config/rs6000/ppc-auxv.h 30884ec5924e409646acd1aa99423fc5 gcc/config/rs6000/ppu_intrinsics.h ! 828b89834087bacd4af0af5e19a8e124 gcc/config/rs6000/predicates.md fed7519f3fb7d3f6e3b9e82dd640d7c0 gcc/config/rs6000/rs6000-builtin.def ! f51e3e86e1da29e05c4e6a034ff4be0f gcc/config/rs6000/rs6000-c.c 3e5ef6c30730e4575563890ec3cfe76b gcc/config/rs6000/rs6000-cpus.def 2f0d36a3bf95d74249364237cf04e29c gcc/config/rs6000/rs6000-linux.c 192ddf2c1b6fd7fe7e53b1acadaee645 gcc/config/rs6000/rs6000-modes.def 14f48bec5cd76d2a5aada931fb1fedf4 gcc/config/rs6000/rs6000-opts.h f9e83e56b3fbfbefb1355ec6235ffa03 gcc/config/rs6000/rs6000-protos.h b43d18bcb08f2293531b3302947868a2 gcc/config/rs6000/rs6000-tables.opt ! c191d4c1f9f21dc772a9bb9d8894eb72 gcc/config/rs6000/rs6000.c ! 6df05e7ac31c6c722809b9fcbcc8019d gcc/config/rs6000/rs6000.h ! ba680257efcdfe70886b6b5cb72436b7 gcc/config/rs6000/rs6000.md ! 5ed93a7516e6be435e463755e04b6061 gcc/config/rs6000/rs6000.opt 23eae5c1992970cba9db6c157ab8c4f6 gcc/config/rs6000/rs64.md 089f55bc6e1565ba82f6d496569d3280 gcc/config/rs6000/rtems.h 510ae383bcc5df111af9d4407a82b6cb gcc/config/rs6000/secureplt.h *************** d3e3ac831dff45625feb5c543903280d gcc/co *** 4018,4024 **** 8040d992aa75d10d1dcbfab10d8192a4 gcc/config/rs6000/spe.h 4916c7683b7e0a7036c40eb6d7ee92f0 gcc/config/rs6000/spe.md 70e488f99d30586ce36bfe7b9dc08fec gcc/config/rs6000/spu2vmx.h ! 89082edb09e5818e9e5f9f05685cadcd gcc/config/rs6000/sync.md 056da47aa9e7eb07f8dea417fb567401 gcc/config/rs6000/sysv4.h 2913dacd00e26860f7ad46828646ca14 gcc/config/rs6000/sysv4.opt 72d0179bc61a6d4aa963be895a0d6e5b gcc/config/rs6000/sysv4le.h --- 4022,4028 ---- 8040d992aa75d10d1dcbfab10d8192a4 gcc/config/rs6000/spe.h 4916c7683b7e0a7036c40eb6d7ee92f0 gcc/config/rs6000/spe.md 70e488f99d30586ce36bfe7b9dc08fec gcc/config/rs6000/spu2vmx.h ! 83969bf251c0226e69d361c5613a6841 gcc/config/rs6000/sync.md 056da47aa9e7eb07f8dea417fb567401 gcc/config/rs6000/sysv4.h 2913dacd00e26860f7ad46828646ca14 gcc/config/rs6000/sysv4.opt 72d0179bc61a6d4aa963be895a0d6e5b gcc/config/rs6000/sysv4le.h *************** f11925c88524d2fd457bf77944da1302 gcc/co *** 4048,4055 **** bb61df2b42a69a90853a503710200de1 gcc/config/rs6000/t-xilinx cc22792d76d22d8203dc7c3680c1dbc7 gcc/config/rs6000/titan.md 7369115a6bfe8259388f41e912c060f2 gcc/config/rs6000/vec_types.h ! ed5c9b710457da108e718e8517f71c08 gcc/config/rs6000/vector.md ! 47b9c515ae81bd9ee9127d0e1c4953d8 gcc/config/rs6000/vsx.md 4d14358837cff46d3efb3a12dfa4fb39 gcc/config/rs6000/vxworks.h 724f6bc5a165006b67c0526f1bd7477f gcc/config/rs6000/vxworksae.h d0482b801e0a94640973282cfb41b1a4 gcc/config/rs6000/vxworksmils.h --- 4052,4059 ---- bb61df2b42a69a90853a503710200de1 gcc/config/rs6000/t-xilinx cc22792d76d22d8203dc7c3680c1dbc7 gcc/config/rs6000/titan.md 7369115a6bfe8259388f41e912c060f2 gcc/config/rs6000/vec_types.h ! 1759069e8fe9a766cfc3af05e6e81d60 gcc/config/rs6000/vector.md ! 634a0dbc50271bc78481635e04c9fd66 gcc/config/rs6000/vsx.md 4d14358837cff46d3efb3a12dfa4fb39 gcc/config/rs6000/vxworks.h 724f6bc5a165006b67c0526f1bd7477f gcc/config/rs6000/vxworksae.h d0482b801e0a94640973282cfb41b1a4 gcc/config/rs6000/vxworksmils.h *************** b7d7076ce697ae031ce8e9044839e677 gcc/co *** 4167,4173 **** cce52944785c3c1036a7380adda38c22 gcc/config/sparc/constraints.md 4899a6b24fe9d952cbb0a117c5014933 gcc/config/sparc/cypress.md a6f5c02cb556d4484b510b1b080970f1 gcc/config/sparc/default-64.h ! 999b81b4a3d65c9f3913d9c5ac50116e gcc/config/sparc/driver-sparc.c 24b6ddb0c85a7d35c6bef23e162f238d gcc/config/sparc/freebsd.h e3873b9f7262fe2e5e1c1ff303fd07f1 gcc/config/sparc/hypersparc.md ceb5379ddc5c41b514ec37a1902d2f2e gcc/config/sparc/leon.md --- 4171,4177 ---- cce52944785c3c1036a7380adda38c22 gcc/config/sparc/constraints.md 4899a6b24fe9d952cbb0a117c5014933 gcc/config/sparc/cypress.md a6f5c02cb556d4484b510b1b080970f1 gcc/config/sparc/default-64.h ! 33ad488c69bc6a52e1221f781b9cdfb5 gcc/config/sparc/driver-sparc.c 24b6ddb0c85a7d35c6bef23e162f238d gcc/config/sparc/freebsd.h e3873b9f7262fe2e5e1c1ff303fd07f1 gcc/config/sparc/hypersparc.md ceb5379ddc5c41b514ec37a1902d2f2e gcc/config/sparc/leon.md *************** d14affc9d9a7c6d706ac72f92b369f54 gcc/co *** 4183,4198 **** df546d4092fe20ba80bd5a3954f0bd35 gcc/config/sparc/openbsd64.h fdf6ab88ad0b4e36a3b8ebf25cfdd547 gcc/config/sparc/predicates.md 2042472acbe05e3e6c55253f1b308604 gcc/config/sparc/rtemself.h ! ea486cef33954ec2c7cd6b2bcd57b5c1 gcc/config/sparc/sol2.h 027897262736bac521955a4e91403e9d gcc/config/sparc/sp-elf.h 16197cb93f1fda192e849bde60b989d3 gcc/config/sparc/sp64-elf.h 97a5fdf9526c5016673d199638234cfb gcc/config/sparc/sparc-c.c 6e05fd82c65a1c0b69f52820e4e2c82a gcc/config/sparc/sparc-modes.def 76ec8424fd03e5e3660223b5ca3cf59a gcc/config/sparc/sparc-opts.h 3b12f88afd2307417ea049e4a24a9bb8 gcc/config/sparc/sparc-protos.h ! a5fe2594395e521119271a742772ed63 gcc/config/sparc/sparc.c ! da3c18895492fa52031c534e5825b3fe gcc/config/sparc/sparc.h ! b3d3c46b415f62bef8a55b7c6b40449b gcc/config/sparc/sparc.md 18fcbfcaaf4ebb852311426ae9f8571d gcc/config/sparc/sparc.opt 9cb87fbe1c20a8991a89a8c2215a7c07 gcc/config/sparc/sparclet.md 8fa2a5576a24f640750e744d90353334 gcc/config/sparc/supersparc.md --- 4187,4202 ---- df546d4092fe20ba80bd5a3954f0bd35 gcc/config/sparc/openbsd64.h fdf6ab88ad0b4e36a3b8ebf25cfdd547 gcc/config/sparc/predicates.md 2042472acbe05e3e6c55253f1b308604 gcc/config/sparc/rtemself.h ! 547504ff7540297bf2dc3e72cd215316 gcc/config/sparc/sol2.h 027897262736bac521955a4e91403e9d gcc/config/sparc/sp-elf.h 16197cb93f1fda192e849bde60b989d3 gcc/config/sparc/sp64-elf.h 97a5fdf9526c5016673d199638234cfb gcc/config/sparc/sparc-c.c 6e05fd82c65a1c0b69f52820e4e2c82a gcc/config/sparc/sparc-modes.def 76ec8424fd03e5e3660223b5ca3cf59a gcc/config/sparc/sparc-opts.h 3b12f88afd2307417ea049e4a24a9bb8 gcc/config/sparc/sparc-protos.h ! 1b8bca8cb28391bd2dc5a646fb343873 gcc/config/sparc/sparc.c ! 20571e7241f7186b57b57c936019c773 gcc/config/sparc/sparc.h ! dc707109b011b8adb0449ec59a2cfc0b gcc/config/sparc/sparc.md 18fcbfcaaf4ebb852311426ae9f8571d gcc/config/sparc/sparc.opt 9cb87fbe1c20a8991a89a8c2215a7c07 gcc/config/sparc/sparclet.md 8fa2a5576a24f640750e744d90353334 gcc/config/sparc/supersparc.md *************** b2a5f5113aa5634b08547ce2619d7dba gcc/co *** 4269,4275 **** c65925a583582f5fdca859446b8b63bc gcc/config/tilegx/tilegx-multiply.h f08b1f5a155126213b5ce7e8ec87ce5b gcc/config/tilegx/tilegx-opts.h e44bf908ed53228aa137666bd80c1c15 gcc/config/tilegx/tilegx-protos.h ! cb5e782d8afa8e3c9a0d0578534daace gcc/config/tilegx/tilegx.c 4ad076cc711ad7270e807f21ebe26058 gcc/config/tilegx/tilegx.h 3e51c4dca770a4cf7d7313f1d593ddeb gcc/config/tilegx/tilegx.md 10ec07469bedf288baf9407746ae5885 gcc/config/tilegx/tilegx.opt --- 4273,4279 ---- c65925a583582f5fdca859446b8b63bc gcc/config/tilegx/tilegx-multiply.h f08b1f5a155126213b5ce7e8ec87ce5b gcc/config/tilegx/tilegx-opts.h e44bf908ed53228aa137666bd80c1c15 gcc/config/tilegx/tilegx-protos.h ! 57421824d74baac84b2dd29e907dc676 gcc/config/tilegx/tilegx.c 4ad076cc711ad7270e807f21ebe26058 gcc/config/tilegx/tilegx.h 3e51c4dca770a4cf7d7313f1d593ddeb gcc/config/tilegx/tilegx.md 10ec07469bedf288baf9407746ae5885 gcc/config/tilegx/tilegx.opt *************** bf09ba0352edd25999324ddd4e47191d gcc/co *** 4286,4292 **** c99773ebef141bd242a6821fb55dc8bc gcc/config/tilepro/tilepro-modes.def 8290d0efa9c4cc94c7becec0940bad27 gcc/config/tilepro/tilepro-multiply.h 29de92a2b471c6f2bb2d5c289f8341ac gcc/config/tilepro/tilepro-protos.h ! ca95d8e18a7cb50927245b811c54d9c9 gcc/config/tilepro/tilepro.c 09630a973accce7da046577669d2d140 gcc/config/tilepro/tilepro.h 5174f3e606a5d0e99cc4d95929eafb6d gcc/config/tilepro/tilepro.md 5e0b60d487b17fff65726a76e411b5a5 gcc/config/tilepro/tilepro.opt --- 4290,4296 ---- c99773ebef141bd242a6821fb55dc8bc gcc/config/tilepro/tilepro-modes.def 8290d0efa9c4cc94c7becec0940bad27 gcc/config/tilepro/tilepro-multiply.h 29de92a2b471c6f2bb2d5c289f8341ac gcc/config/tilepro/tilepro-protos.h ! e7754cffee227c667c93634cfd6e96e2 gcc/config/tilepro/tilepro.c 09630a973accce7da046577669d2d140 gcc/config/tilepro/tilepro.h 5174f3e606a5d0e99cc4d95929eafb6d gcc/config/tilepro/tilepro.md 5e0b60d487b17fff65726a76e411b5a5 gcc/config/tilepro/tilepro.opt *************** c281f2e9af80cc72bba6fd54bd02f078 gcc/co *** 4371,4391 **** ededba279c875242ed184a0ca6823677 gcc/config/xtensa/t-xtensa b38cc6421ca7d7c2df131805520197f8 gcc/config/xtensa/uclinux.h a09263d9768c434ff9da0afe8dd1f04e gcc/config/xtensa/uclinux.opt ! 9296660def4fef8b80b39a386fb9e05b gcc/config/xtensa/xtensa-protos.h ! 38304c3ded726c92438b7cf261e56f29 gcc/config/xtensa/xtensa.c ! bb1965ec2a1e0ce5e60d527c23ca610b gcc/config/xtensa/xtensa.h ! d3ed3f2851a6ee9f647a0fe488ad1639 gcc/config/xtensa/xtensa.md 6bc76a8cf807646d45ffd30b5ca7d2b2 gcc/config/xtensa/xtensa.opt f1745e8f62b23a8d906fccfb967039c1 gcc/configure 749fa2f7b91198a4b287baa858df40bd gcc/configure.ac 0ec5b41e50536d76b12ce8977926b0df gcc/context.c 26da2cb861339f31f80bd959e0d59598 gcc/context.h ! 76f5acc561ec0cdc7412066f1a775388 gcc/convert.c d84bc78e8cfdc1b1e4930926711d56d8 gcc/convert.h d80857164629763d35964508054ddcda gcc/coretypes.h ! c1d9055612e35b11f4c86de664f8e1a7 gcc/coverage.c ! 653580fc0a70e3ade04c5b00362b0daa gcc/coverage.h ! 9a340982b6ed49edaff5ed437e713c95 gcc/cp/ChangeLog d271e3663538ba1f3281cab3838e92cd gcc/cp/ChangeLog-1993 f5a44adbc05521162350ca409d1d95ce gcc/cp/ChangeLog-1994 ac55db48d964cb5469ff03c1cd3ee04d gcc/cp/ChangeLog-1995 --- 4375,4395 ---- ededba279c875242ed184a0ca6823677 gcc/config/xtensa/t-xtensa b38cc6421ca7d7c2df131805520197f8 gcc/config/xtensa/uclinux.h a09263d9768c434ff9da0afe8dd1f04e gcc/config/xtensa/uclinux.opt ! 5c6d44c80c62552399b15c7de3b52b12 gcc/config/xtensa/xtensa-protos.h ! fb4e09d2f31b041547273e997384947e gcc/config/xtensa/xtensa.c ! 5d2691d1b9c61c9889c1eb666127f253 gcc/config/xtensa/xtensa.h ! 8d5d03aedec908e97e57b62f2a511455 gcc/config/xtensa/xtensa.md 6bc76a8cf807646d45ffd30b5ca7d2b2 gcc/config/xtensa/xtensa.opt f1745e8f62b23a8d906fccfb967039c1 gcc/configure 749fa2f7b91198a4b287baa858df40bd gcc/configure.ac 0ec5b41e50536d76b12ce8977926b0df gcc/context.c 26da2cb861339f31f80bd959e0d59598 gcc/context.h ! 378b0b907eabb610ce310db8a7efa63c gcc/convert.c d84bc78e8cfdc1b1e4930926711d56d8 gcc/convert.h d80857164629763d35964508054ddcda gcc/coretypes.h ! a366efd2bb8ae44b8d5993f357bcccd1 gcc/coverage.c ! d2e9bad038f8b277c681b8095db51116 gcc/coverage.h ! 66c2d66748cb0236cab4f6b5c2fd2cb6 gcc/cp/ChangeLog d271e3663538ba1f3281cab3838e92cd gcc/cp/ChangeLog-1993 f5a44adbc05521162350ca409d1d95ce gcc/cp/ChangeLog-1994 ac55db48d964cb5469ff03c1cd3ee04d gcc/cp/ChangeLog-1995 *************** c1c7801b9b0f379e702a4f6cb83972e7 gcc/cp *** 4413,4468 **** 9aa3cd9f75c785de9f51446e3f295515 gcc/cp/ChangeLog.tree-ssa 40c026d4c25f7d1b05e9209c1db5fce9 gcc/cp/Make-lang.in 9bc6241e715c32f1a0f6e1b8028cb853 gcc/cp/NEWS ! ef277c1531a32c2d8bb69b651b47e39c gcc/cp/call.c afb9bd2c59a27b9a4e01674e6ef4c2d2 gcc/cp/cfns.gperf 4dc84f7aecf8adaa3133cffb6b7a9ca6 gcc/cp/cfns.h a28fc7e2b78b20cb8c087c6ba932f29f gcc/cp/class.c 739c569e48a7b41b606f425cbc9123d2 gcc/cp/config-lang.in ! 291df51bf1b4722cd5e2b40e3f12cd04 gcc/cp/constexpr.c c683759a418cb72958ad21fa84df0a0e gcc/cp/constraint.cc 3ba51b5d6be105c2076c7c57590c4ef3 gcc/cp/cp-array-notation.c 186d27a5d5d478e09c882e0110153c3e gcc/cp/cp-cilkplus.c ! a146bb8e68c7365f2756377f36428db8 gcc/cp/cp-gimplify.c bb99af59da6436bd29f57f3f050c526f gcc/cp/cp-lang.c f3d5c0a13bc26cb7c946210741aa3848 gcc/cp/cp-objcp-common.c f21d1769c40e5fb7e0b4bb740c877732 gcc/cp/cp-objcp-common.h d21831b373779814d66d82151827a70a gcc/cp/cp-tree.def ! 6c85ecb57567828b0206d6f1466bcac4 gcc/cp/cp-tree.h 1369f5ca78bd37e84d0985faff35f429 gcc/cp/cp-ubsan.c 9f77a7a0c8d02ceef78c0f1cc355cca6 gcc/cp/cvt.c 4fb925f8c277dfd445a3480f29c7ab2a gcc/cp/cxx-pretty-print.c eb1c2da742513f6f21d3de7d3d531d78 gcc/cp/cxx-pretty-print.h ! a4352b190863996750cd8dad1095292c gcc/cp/decl.c f43394b8806c96193cee8cfd4a55336b gcc/cp/decl.h ! de2c0d1c08ecc2a3c8cef00a05166a28 gcc/cp/decl2.c 7ae2c1642094de5138fbb999f0ba1dd7 gcc/cp/dump.c ! efd1d78636eabc8968b098869345d344 gcc/cp/error.c 55f92fe617bd4f1e45207eb0c41885fa gcc/cp/except.c e68580c70d9bfd1c150485b9fca85280 gcc/cp/expr.c 7fd276d735538ed700d62bbcceed734c gcc/cp/friend.c 953a6283c57f96c8e1146ea75f4e288b gcc/cp/g++spec.c ! c8abb0e1709c8cf6321ccc93db736fa5 gcc/cp/init.c ! 7df2289f6bb363fb7626282eaa41fa2f gcc/cp/lambda.c dd9fc96e1760180eadcc31d884bd5258 gcc/cp/lang-specs.h e978132617f114d81875d7e4a46eb0e9 gcc/cp/lex.c 229e017e45642f0baa01dd040584ce51 gcc/cp/logic.cc 56b196737887e003174e520076c50cfc gcc/cp/mangle.c ! 326b441b0bc0067d256b4b72cd6b73a0 gcc/cp/method.c ! 447088dbb1483cd82cfd32ddd03aaeb5 gcc/cp/name-lookup.c 70b3b6f7199163918e5d2a0c1452b772 gcc/cp/name-lookup.h 764366090f3163fb5ccd85cb19a94cff gcc/cp/operators.def 1cad434894b0845fc0a6f03de2d39180 gcc/cp/optimize.c ! 9ec4cb7ccf1d6bb875e1fac51f6c5b77 gcc/cp/parser.c b5da26fff61760a30cbda1f01a4c4808 gcc/cp/parser.h ! 5e7586796a06a86428858d66916c7b5c gcc/cp/pt.c e61259963d803da8e625c96134d4f5a6 gcc/cp/ptree.c f06807decf6ff4b02873679e35ef5865 gcc/cp/repo.c fc320188ae1e308c62b750b92ce39885 gcc/cp/rtti.c f0b16ecd9783b80773d4b1b34c7cca79 gcc/cp/search.c ! 04c47d73052781529421486c5f496e44 gcc/cp/semantics.c ! 79d814f96502c3b714d31e97796e9d17 gcc/cp/tree.c 4ac4dcdc19063fd7ea7055b2064b4d37 gcc/cp/type-utils.h ! d8713a1437d9d1f4f8de408be0cca095 gcc/cp/typeck.c 28e8d9e3a43c8f9376f2d935bb2f5e6a gcc/cp/typeck2.c 8b2699a100775446f1d3379bfb10c109 gcc/cp/vtable-class-hierarchy.c bd835b9ee78a94f4ae3f8adee63f9a51 gcc/cppbuiltin.c --- 4417,4472 ---- 9aa3cd9f75c785de9f51446e3f295515 gcc/cp/ChangeLog.tree-ssa 40c026d4c25f7d1b05e9209c1db5fce9 gcc/cp/Make-lang.in 9bc6241e715c32f1a0f6e1b8028cb853 gcc/cp/NEWS ! e67e77bae1060a2afeab6bd53770bbd9 gcc/cp/call.c afb9bd2c59a27b9a4e01674e6ef4c2d2 gcc/cp/cfns.gperf 4dc84f7aecf8adaa3133cffb6b7a9ca6 gcc/cp/cfns.h a28fc7e2b78b20cb8c087c6ba932f29f gcc/cp/class.c 739c569e48a7b41b606f425cbc9123d2 gcc/cp/config-lang.in ! 0791a4cecc5a38db4e687fa23e963cc6 gcc/cp/constexpr.c c683759a418cb72958ad21fa84df0a0e gcc/cp/constraint.cc 3ba51b5d6be105c2076c7c57590c4ef3 gcc/cp/cp-array-notation.c 186d27a5d5d478e09c882e0110153c3e gcc/cp/cp-cilkplus.c ! df63345aa689caab9243bd0177a4dbc8 gcc/cp/cp-gimplify.c bb99af59da6436bd29f57f3f050c526f gcc/cp/cp-lang.c f3d5c0a13bc26cb7c946210741aa3848 gcc/cp/cp-objcp-common.c f21d1769c40e5fb7e0b4bb740c877732 gcc/cp/cp-objcp-common.h d21831b373779814d66d82151827a70a gcc/cp/cp-tree.def ! 317d2b752260920c219efe839409fed5 gcc/cp/cp-tree.h 1369f5ca78bd37e84d0985faff35f429 gcc/cp/cp-ubsan.c 9f77a7a0c8d02ceef78c0f1cc355cca6 gcc/cp/cvt.c 4fb925f8c277dfd445a3480f29c7ab2a gcc/cp/cxx-pretty-print.c eb1c2da742513f6f21d3de7d3d531d78 gcc/cp/cxx-pretty-print.h ! 11599a832ca5bbd37f5249fe4389d635 gcc/cp/decl.c f43394b8806c96193cee8cfd4a55336b gcc/cp/decl.h ! 2cfe5844634fefd6f70d998a853ea1c8 gcc/cp/decl2.c 7ae2c1642094de5138fbb999f0ba1dd7 gcc/cp/dump.c ! 52830d80edaf8352e145040be52b6dfd gcc/cp/error.c 55f92fe617bd4f1e45207eb0c41885fa gcc/cp/except.c e68580c70d9bfd1c150485b9fca85280 gcc/cp/expr.c 7fd276d735538ed700d62bbcceed734c gcc/cp/friend.c 953a6283c57f96c8e1146ea75f4e288b gcc/cp/g++spec.c ! 42e5a5143a0b9056a2fbc61732f4addd gcc/cp/init.c ! da0411c522e8f3d9e3e7001e09e052bb gcc/cp/lambda.c dd9fc96e1760180eadcc31d884bd5258 gcc/cp/lang-specs.h e978132617f114d81875d7e4a46eb0e9 gcc/cp/lex.c 229e017e45642f0baa01dd040584ce51 gcc/cp/logic.cc 56b196737887e003174e520076c50cfc gcc/cp/mangle.c ! f1047d46fbff8ce8d2dbe6a7f7fd2fc1 gcc/cp/method.c ! 321d400cfd4b3e386db640747a6ad5f9 gcc/cp/name-lookup.c 70b3b6f7199163918e5d2a0c1452b772 gcc/cp/name-lookup.h 764366090f3163fb5ccd85cb19a94cff gcc/cp/operators.def 1cad434894b0845fc0a6f03de2d39180 gcc/cp/optimize.c ! 7ef526c7cdb1cf0a0e8dc08e99e03804 gcc/cp/parser.c b5da26fff61760a30cbda1f01a4c4808 gcc/cp/parser.h ! 25cf227f2b2d5fe15a9ee89e9ef90a1d gcc/cp/pt.c e61259963d803da8e625c96134d4f5a6 gcc/cp/ptree.c f06807decf6ff4b02873679e35ef5865 gcc/cp/repo.c fc320188ae1e308c62b750b92ce39885 gcc/cp/rtti.c f0b16ecd9783b80773d4b1b34c7cca79 gcc/cp/search.c ! b65f3fb6bf20f57b4d85a9370e15839b gcc/cp/semantics.c ! 187a1993ca8c0b7c274fc913d6e5976f gcc/cp/tree.c 4ac4dcdc19063fd7ea7055b2064b4d37 gcc/cp/type-utils.h ! d04f6c7a6e406c16da53d6a896861d6a gcc/cp/typeck.c 28e8d9e3a43c8f9376f2d935bb2f5e6a gcc/cp/typeck2.c 8b2699a100775446f1d3379bfb10c109 gcc/cp/vtable-class-hierarchy.c bd835b9ee78a94f4ae3f8adee63f9a51 gcc/cppbuiltin.c *************** a8b7256c689701d5c714e06099ce8503 gcc/cp *** 4471,4481 **** ac40c8d6feae034cb54496c0548be185 gcc/cppdefault.h cf38fdbbc6e6fd94f45791c5c213eb8d gcc/cprop.c 9ca76a939f80758fb8ce83d0b34b6b2f gcc/cse.c ! c354655301797083d12b9ba19cfe9230 gcc/cselib.c 9d78d06f2dc22606c4ce309ab94d0bf0 gcc/cselib.h 1ded054093de910d9786c62bc4fe8cc6 gcc/cstamp-h.in ! aaa6276890e44cc872798a0cfd3488e8 gcc/data-streamer-in.c ! da06696e64bc6c25f3892e864f3b282f gcc/data-streamer-out.c b5dac293ec8bbbe5ea1b2b6455ffecde gcc/data-streamer.c 051c2d013b32ef3a5d8d7e999b03fb2c gcc/data-streamer.h e22d68c4e2d663c5e52b7f3010d13a68 gcc/dbgcnt.c --- 4475,4485 ---- ac40c8d6feae034cb54496c0548be185 gcc/cppdefault.h cf38fdbbc6e6fd94f45791c5c213eb8d gcc/cprop.c 9ca76a939f80758fb8ce83d0b34b6b2f gcc/cse.c ! 0a939d24160312fad1d82a7b8b6e5c23 gcc/cselib.c 9d78d06f2dc22606c4ce309ab94d0bf0 gcc/cselib.h 1ded054093de910d9786c62bc4fe8cc6 gcc/cstamp-h.in ! 9adbecf352c635dc831940368f1018b2 gcc/data-streamer-in.c ! 0c5f32280e5691296cad9b2462f04124 gcc/data-streamer-out.c b5dac293ec8bbbe5ea1b2b6455ffecde gcc/data-streamer.c 051c2d013b32ef3a5d8d7e999b03fb2c gcc/data-streamer.h e22d68c4e2d663c5e52b7f3010d13a68 gcc/dbgcnt.c *************** e81f5611ca72ae89425ca6ee484d9f70 gcc/di *** 4503,4509 **** 6bb8763d2cd82acf9315292a011edb6a gcc/diagnostic.c cc2592797ca4befcbb1163c1a7a00f80 gcc/diagnostic.def b5b5c842e04bed80ee2680523e412d59 gcc/diagnostic.h ! 1e9f455d71b14f04f95cf87c540e5ecf gcc/doc/aot-compile.1 4b0e646c5de4431c5d6bbfe40f0cd073 gcc/doc/avr-mmcu.texi 67be61d4feeb4a05b9c19af733aa05ae gcc/doc/bugreport.texi 0615182a653a9840fd7ae8745219a5be gcc/doc/cfg.texi --- 4507,4513 ---- 6bb8763d2cd82acf9315292a011edb6a gcc/diagnostic.c cc2592797ca4befcbb1163c1a7a00f80 gcc/diagnostic.def b5b5c842e04bed80ee2680523e412d59 gcc/diagnostic.h ! e87ead717632de3714c0811b86e146f1 gcc/doc/aot-compile.1 4b0e646c5de4431c5d6bbfe40f0cd073 gcc/doc/avr-mmcu.texi 67be61d4feeb4a05b9c19af733aa05ae gcc/doc/bugreport.texi 0615182a653a9840fd7ae8745219a5be gcc/doc/cfg.texi *************** b5b5c842e04bed80ee2680523e412d59 gcc/di *** 4513,4552 **** 240a91046efda88ae96dd3386f6e431c gcc/doc/configterms.texi de72fb12d4dca40f7a8d5b4429df7991 gcc/doc/contrib.texi c498cc82ef6af94189c770012a2a18e9 gcc/doc/contribute.texi ! a964a4d9da316d3c4d4303ea5ad0eeae gcc/doc/cpp.1 ! 118f2baa2fd57ff1e7870798463a7bde gcc/doc/cpp.info ! 0f2a72efa57326c8f726620c490228a1 gcc/doc/cpp.texi c558a3f6cb1b068e5bdc0406d2ed7217 gcc/doc/cppenv.texi ! 569f1b340dac3b5683ec7babbf267ea0 gcc/doc/cppinternals.info ! 5e146b7ee23d2aecc854dcc8ab494552 gcc/doc/cppinternals.texi 594e4c25acf69b6587158d05dd033b24 gcc/doc/cppopts.texi ! 29e8e6f5768d61ca52aa15533dad6f10 gcc/doc/extend.texi 95f852d1ef912c794a713c43da587f55 gcc/doc/fragments.texi 6f0ea8cb29b8222c190965f0c877a2fa gcc/doc/frontends.texi ! 9a94859e75825cb8d07ee64861a78278 gcc/doc/fsf-funding.7 ! 1030754a36f689bc43b582008df3461f gcc/doc/g++.1 ! 564508756c86592e57f7d4b72913240e gcc/doc/gc-analyze.1 ! 1030754a36f689bc43b582008df3461f gcc/doc/gcc.1 ! 9d035bbebd8718e8f5c5cc1e383850ea gcc/doc/gcc.info ! 88763fd4a2ca7b1f84637c92258f12c3 gcc/doc/gcc.texi ! c260fb2480b207a17cf1f38d72cd30fc gcc/doc/gccinstall.info ! a8543f0246ce8a9a550e8839ef65af2a gcc/doc/gccint.info ! a1072c7fe384b26d4053192ee158b54a gcc/doc/gccint.texi ! e6e5cf4cd282511dd42e797a14e1f9c0 gcc/doc/gcj-dbtool.1 ! 90ef5e964b90d88430edf0bc150b85a4 gcc/doc/gcj.1 ! 238f22235b2c5f5f2082f9c50be8e716 gcc/doc/gcj.info ! 877f494d8f93ff49fa2c8398f659aa47 gcc/doc/gcov-tool.1 ! 600e5ec8739c8b59da149866fceeb218 gcc/doc/gcov-tool.texi ! d294f5ef324301fd158abee422b7eec6 gcc/doc/gcov.1 ! 72bbc01b16e62773dff9dfa7a60f2e01 gcc/doc/gcov.texi ! ccdbce7ea9c6edf013744bebd58a7236 gcc/doc/generic.texi ! b14c64de2670b7af0403c2d155c7a09f gcc/doc/gfdl.7 ! 399b67f5c64fbff7335ddc239f99bdb5 gcc/doc/gfortran.1 ! e12f762a0a56662c0cb7546601b95527 gcc/doc/gij.1 5d1606771c73c06954506e0770209ad6 gcc/doc/gimple.texi 290370669f02bef1502ada9273e5261f gcc/doc/gnu.texi ! 2b1da8dbbf38780e388f56a304255d69 gcc/doc/gpl.7 ! 452ed9d85b5fc69414db0cc7cf6ff0f6 gcc/doc/grmic.1 07064b30149463ca48cad1274d117022 gcc/doc/gty.texi ffbbf9909dbcbd3ce420b273106fe852 gcc/doc/headerdirs.texi 5ddad8e0920359df62f566823c25331e gcc/doc/hostconfig.texi --- 4517,4558 ---- 240a91046efda88ae96dd3386f6e431c gcc/doc/configterms.texi de72fb12d4dca40f7a8d5b4429df7991 gcc/doc/contrib.texi c498cc82ef6af94189c770012a2a18e9 gcc/doc/contribute.texi ! 327bbcec8c2a85f5ccc66a74077d97e0 gcc/doc/cpp.1 ! dbb0d7bbf30374a33b884afaef232900 gcc/doc/cpp.info ! 76604ef5a7cca53de25cb55020b9e160 gcc/doc/cpp.texi c558a3f6cb1b068e5bdc0406d2ed7217 gcc/doc/cppenv.texi ! 591d471f41214faf8448f7c46a692185 gcc/doc/cppinternals.info ! 1f36b3ac7360c14400719705305d3b68 gcc/doc/cppinternals.texi 594e4c25acf69b6587158d05dd033b24 gcc/doc/cppopts.texi ! 9a3e717b761db66ac6423760dee96626 gcc/doc/extend.texi 95f852d1ef912c794a713c43da587f55 gcc/doc/fragments.texi 6f0ea8cb29b8222c190965f0c877a2fa gcc/doc/frontends.texi ! 4c359292bb3069730bc409e057f76be3 gcc/doc/fsf-funding.7 ! 6653b3aa5f09b3e5f7f2f19c871a2e4b gcc/doc/g++.1 ! ea1c7694a27b4cdd86b6101dadb994ee gcc/doc/gc-analyze.1 ! 6653b3aa5f09b3e5f7f2f19c871a2e4b gcc/doc/gcc.1 ! ff3a4f9a1bb05158025377fa12ecfb68 gcc/doc/gcc.info ! 16a9a3c901b7de5a189295ae4a722207 gcc/doc/gcc.texi ! a424815bc02b9a8a786116e203b0c3fc gcc/doc/gccinstall.info ! 83145e0dd9cb0a4e71c0242aa49494b4 gcc/doc/gccint.info ! cbd1289c39d8b1e3ebb140eb4e14f4ec gcc/doc/gccint.texi ! c7b60f9a7e1535cdac5520c5b17a9d29 gcc/doc/gcj-dbtool.1 ! 158796bfe7e438fa4f8d900bb76faca2 gcc/doc/gcj.1 ! 341a5db189774764c173e51204ab3c81 gcc/doc/gcj.info ! 5898c16f8a284995f4773f9a7705bdb6 gcc/doc/gcov-dump.1 ! b8d24f76649917a88a4a7b21cd032a0f gcc/doc/gcov-dump.texi ! 2c18393def7e12665ef6f8718887b9b0 gcc/doc/gcov-tool.1 ! be6f92f693bcd6b988040c3873ea2516 gcc/doc/gcov-tool.texi ! 409edbafaacf51fc8159fd0a3ebf18f0 gcc/doc/gcov.1 ! f26d3920ba975f6297c473cb76dd79b1 gcc/doc/gcov.texi ! 2d556a2783b3b9eb0cab0873b7bec7c8 gcc/doc/generic.texi ! cb36ff621219abc027855a6aea6dce45 gcc/doc/gfdl.7 ! 3cc64044711ff7d7718d6c0b9e326eb6 gcc/doc/gfortran.1 ! 54245028253b5f598c3e3291b2899298 gcc/doc/gij.1 5d1606771c73c06954506e0770209ad6 gcc/doc/gimple.texi 290370669f02bef1502ada9273e5261f gcc/doc/gnu.texi ! 4dd53c8a4fcae9c9f43b95fa44d78716 gcc/doc/gpl.7 ! 76dc47cdc343ad25c26142b80cabaf45 gcc/doc/grmic.1 07064b30149463ca48cad1274d117022 gcc/doc/gty.texi ffbbf9909dbcbd3ce420b273106fe852 gcc/doc/headerdirs.texi 5ddad8e0920359df62f566823c25331e gcc/doc/hostconfig.texi *************** edc60ee5594a473072372bd3fcfbcc10 gcc/do *** 4558,4588 **** 5f5adc2c6c4ebdcf03cc0125250f5995 gcc/doc/include/gpl_v3.texi 73819b3930a3d4be5d6234070d02386a gcc/doc/include/texinfo.tex a57e0b900d0ae5846091a1e5f722fcf7 gcc/doc/install-old.texi ! 50ae385657454d98f1479997f9e3e942 gcc/doc/install.texi 9e425a943a46a878a1f546f928d14b04 gcc/doc/install.texi2html a869466cbfcd212e8988279541bdda16 gcc/doc/interface.texi ! 8acd73b8868d165bb592a2448c7f9df7 gcc/doc/invoke.texi ! 620ee83f9bf0990a2438efb067493ff3 gcc/doc/jcf-dump.1 ! 0014eb49bf8982f1e5d1b2795efeb624 gcc/doc/jv-convert.1 a0e7c077817653eddca3b287b2ec1499 gcc/doc/languages.texi ab4011897f2095293d3a4d9443678fb5 gcc/doc/libgcc.texi b0981441c4f9daaa09818d68a36bd67f gcc/doc/loop.texi ! fc3fd4aafdd4ab47930dcb216ffe03cc gcc/doc/lto.texi 5c2acf2b3a4a6b50ab9b1544cc49e81f gcc/doc/makefile.texi ab9503a1420248f03274f60100f0648a gcc/doc/match-and-simplify.texi ! 27523cb487a4388cb994819a94202ec0 gcc/doc/md.texi 1f5569ca70207eb8ded92ebefd130c2e gcc/doc/objc.texi 83bbf74c59b8849c2b8d083a134672c7 gcc/doc/optinfo.texi e2a974acfc3260f2407c7fe05a990bce gcc/doc/options.texi ! 6cd361bc13e8ff0fd0523b24175f2317 gcc/doc/passes.texi a989acbeb85b23b1813e7e65a54c288f gcc/doc/plugins.texi 6f4f5f396ee46b12e48520f7305e57d9 gcc/doc/portability.texi ! cdfcb235c98072bedf4a6a286e853785 gcc/doc/rebuild-gcj-db.1 944c63993645cd2a2bcb6cc7dcbbd103 gcc/doc/rtl.texi 29e91cae40a54cd373834ec123131f3d gcc/doc/service.texi ! 43460cd9078a9e21d9ac0d9315448c43 gcc/doc/sourcebuild.texi 92648bf67aa79bddaf088859206ae007 gcc/doc/standards.texi ! 77c76b0e5ed8d6acf68d6d741c6e8a86 gcc/doc/tm.texi 06793299c7507748161941a482ea7a29 gcc/doc/tm.texi.in 4951633b6a4e2b13199931a19d3ed85e gcc/doc/tree-ssa.texi a730c06aac74e5b6ff585addc044c4dd gcc/doc/trouble.texi --- 4564,4594 ---- 5f5adc2c6c4ebdcf03cc0125250f5995 gcc/doc/include/gpl_v3.texi 73819b3930a3d4be5d6234070d02386a gcc/doc/include/texinfo.tex a57e0b900d0ae5846091a1e5f722fcf7 gcc/doc/install-old.texi ! e41335c1551188f7918c9f0f797497bf gcc/doc/install.texi 9e425a943a46a878a1f546f928d14b04 gcc/doc/install.texi2html a869466cbfcd212e8988279541bdda16 gcc/doc/interface.texi ! b1e8bad377ae7805698d61be73645279 gcc/doc/invoke.texi ! aca3b199bb039227de4beb3d4eb14ee4 gcc/doc/jcf-dump.1 ! 9d417a42f3c048224f7e85095581b575 gcc/doc/jv-convert.1 a0e7c077817653eddca3b287b2ec1499 gcc/doc/languages.texi ab4011897f2095293d3a4d9443678fb5 gcc/doc/libgcc.texi b0981441c4f9daaa09818d68a36bd67f gcc/doc/loop.texi ! 5bc9c6bccc0f8b2172f59bae12d678bd gcc/doc/lto.texi 5c2acf2b3a4a6b50ab9b1544cc49e81f gcc/doc/makefile.texi ab9503a1420248f03274f60100f0648a gcc/doc/match-and-simplify.texi ! 029543bf0a9af36d1b595336c25d37f5 gcc/doc/md.texi 1f5569ca70207eb8ded92ebefd130c2e gcc/doc/objc.texi 83bbf74c59b8849c2b8d083a134672c7 gcc/doc/optinfo.texi e2a974acfc3260f2407c7fe05a990bce gcc/doc/options.texi ! 3ac6f5707360e738dac8d9b4416f4c54 gcc/doc/passes.texi a989acbeb85b23b1813e7e65a54c288f gcc/doc/plugins.texi 6f4f5f396ee46b12e48520f7305e57d9 gcc/doc/portability.texi ! 23be00ae0c611386b30d40e37e41c0bd gcc/doc/rebuild-gcj-db.1 944c63993645cd2a2bcb6cc7dcbbd103 gcc/doc/rtl.texi 29e91cae40a54cd373834ec123131f3d gcc/doc/service.texi ! 775ec57c13062fc5e4bf1823905ed536 gcc/doc/sourcebuild.texi 92648bf67aa79bddaf088859206ae007 gcc/doc/standards.texi ! 95a0077d549040919658adbee7cf4ccf gcc/doc/tm.texi 06793299c7507748161941a482ea7a29 gcc/doc/tm.texi.in 4951633b6a4e2b13199931a19d3ed85e gcc/doc/tree-ssa.texi a730c06aac74e5b6ff585addc044c4dd gcc/doc/trouble.texi *************** e517ff58548f83de7b8bbd573b7e6bca gcc/du *** 4600,4606 **** 3f5963da7e097503d222ddfc4cdf7f81 gcc/dwarf2asm.c 73944fce2a805f3b1672e5ed81f76558 gcc/dwarf2asm.h 8b34c3660aa997b685d65ad9a84e597b gcc/dwarf2cfi.c ! 4cdd3ca4416576ecfa55cf23650f6cb2 gcc/dwarf2out.c f2cf5c1bba29ec5e6a5fe0e97d33704b gcc/dwarf2out.h 07467e53d8d2dd27f0b59fe696a8fcdf gcc/emit-rtl.c abbd65c7d3f556b7463e8840d7f9d930 gcc/emit-rtl.h --- 4606,4612 ---- 3f5963da7e097503d222ddfc4cdf7f81 gcc/dwarf2asm.c 73944fce2a805f3b1672e5ed81f76558 gcc/dwarf2asm.h 8b34c3660aa997b685d65ad9a84e597b gcc/dwarf2cfi.c ! 197038a5714a61451bf4d901cc081909 gcc/dwarf2out.c f2cf5c1bba29ec5e6a5fe0e97d33704b gcc/dwarf2out.h 07467e53d8d2dd27f0b59fe696a8fcdf gcc/emit-rtl.c abbd65c7d3f556b7463e8840d7f9d930 gcc/emit-rtl.h *************** efb926b924a2b56981b4a714c04ce6de gcc/ex *** 4615,4622 **** edb04cc433cc4a6472575f824b35e1b5 gcc/explow.h e0a2e47206a445e3d5245a8436fcac1b gcc/expmed.c 227c6c12d547fda83c1d3779b675efc9 gcc/expmed.h ! c4bb53ab7f9183683e2c04fce7ed63ce gcc/expr.c ! ec39100e3d3393e18a40972210107398 gcc/expr.h 4b5d1201413da254f4027f9da61730fa gcc/fibonacci_heap.h d580b8d7b2e2cb33c7af0505f52d872d gcc/file-find.c 11b86e7523d07214d26758d1df794788 gcc/file-find.h --- 4621,4628 ---- edb04cc433cc4a6472575f824b35e1b5 gcc/explow.h e0a2e47206a445e3d5245a8436fcac1b gcc/expmed.c 227c6c12d547fda83c1d3779b675efc9 gcc/expmed.h ! 2fccb374435a7d5c4f8d69a610b74ef5 gcc/expr.c ! 8efb476e7345c14d0fc355be06b1e9d4 gcc/expr.h 4b5d1201413da254f4027f9da61730fa gcc/fibonacci_heap.h d580b8d7b2e2cb33c7af0505f52d872d gcc/file-find.c 11b86e7523d07214d26758d1df794788 gcc/file-find.h *************** a6615383c6273e7190e22f67d618d4a7 gcc/fl *** 4627,4635 **** 9666a2458f11468dd9979a7cfca842e3 gcc/flags.h b34c1b95a54e16d433363b08e57e7f85 gcc/fold-const-call.c f4d19b0528d646f769792430919be6ff gcc/fold-const-call.h ! 60455e2b318b6d748ebeff49bb0ef2f0 gcc/fold-const.c b6b5bb4a4f17604d5bcfb47ecba0768c gcc/fold-const.h ! 1978baf102712aeab943f15517fa6cd6 gcc/fortran/ChangeLog 3330102ad3a0217cba963be6b5eefd58 gcc/fortran/ChangeLog-2002 d000ab985b1eeb1ad5749f98b8fef99f gcc/fortran/ChangeLog-2003 bf42f94f0c51dcc7d8051cc7fda1efdc gcc/fortran/ChangeLog-2004 --- 4633,4641 ---- 9666a2458f11468dd9979a7cfca842e3 gcc/flags.h b34c1b95a54e16d433363b08e57e7f85 gcc/fold-const-call.c f4d19b0528d646f769792430919be6ff gcc/fold-const-call.h ! bd3f8d653921cfb27feb0913b011b4c9 gcc/fold-const.c b6b5bb4a4f17604d5bcfb47ecba0768c gcc/fold-const.h ! a6d8365fec6e945722d13f2d28caf6de gcc/fortran/ChangeLog 3330102ad3a0217cba963be6b5eefd58 gcc/fortran/ChangeLog-2002 d000ab985b1eeb1ad5749f98b8fef99f gcc/fortran/ChangeLog-2003 bf42f94f0c51dcc7d8051cc7fda1efdc gcc/fortran/ChangeLog-2004 *************** be4956add3a0a52371db809732688221 gcc/fo *** 4651,4657 **** 6c69c97bb68fff84c319bda150d48fa5 gcc/fortran/array.c c9fae371f8d0a027b1391ff1d82faaa8 gcc/fortran/bbt.c bdfc35cb00eff4244760acd86c99b4fc gcc/fortran/check.c ! c6792788d52a7e1c3e8ea31f3784b120 gcc/fortran/class.c 4819f6163cdda697542442ead8d1edb9 gcc/fortran/config-lang.in 1564600ca4ee09dae677a32e9632817c gcc/fortran/constructor.c 03ded9e724f957a8caca8c58de189bf9 gcc/fortran/constructor.h --- 4657,4663 ---- 6c69c97bb68fff84c319bda150d48fa5 gcc/fortran/array.c c9fae371f8d0a027b1391ff1d82faaa8 gcc/fortran/bbt.c bdfc35cb00eff4244760acd86c99b4fc gcc/fortran/check.c ! f44a013471446c64ac719650e6aad482 gcc/fortran/class.c 4819f6163cdda697542442ead8d1edb9 gcc/fortran/config-lang.in 1564600ca4ee09dae677a32e9632817c gcc/fortran/constructor.c 03ded9e724f957a8caca8c58de189bf9 gcc/fortran/constructor.h *************** b1689d8c78a9ebedfd57cb11ec38adb2 gcc/fo *** 4660,4681 **** 83041f3879c600754744a8da84761bc9 gcc/fortran/cpp.h 112c4ba412ed2704834031ec9a0838fa gcc/fortran/data.c 167ea51b39af01ee143176fe03d80fb1 gcc/fortran/data.h ! f0fefd8b9732111a156c1422941b3ea2 gcc/fortran/decl.c a35f5788bded49237879a7f19a6288ab gcc/fortran/dependency.c 272c4deffabcf4caf71d639c1c58c42d gcc/fortran/dependency.h 7819b2970d4d816cafb214702abb4ef5 gcc/fortran/dump-parse-tree.c 3de13f2b47e6b19d0ec70c245e5afabd gcc/fortran/error.c ! c24474942a0f154216297ebe2b002156 gcc/fortran/expr.c 8183028b3162dfef1b367f187a615b42 gcc/fortran/f95-lang.c ! b7e15afd8aec1362680b397866f30446 gcc/fortran/frontend-passes.c 9295becaf3bc8598cfdf49e3a4dd9f9b gcc/fortran/gfc-diagnostic.def 23d6c9cd5c12c7f2aca8fd69d8420b43 gcc/fortran/gfc-internals.texi d27235635f3a8da5058b24e0f055bf7d gcc/fortran/gfortran.h ! ec77cb25910e8ca2aefb8693859354e7 gcc/fortran/gfortran.info 80c16dc56896ccc10c0dc114ac976580 gcc/fortran/gfortran.texi ! f3790a90748e52fe5ebfcdc7a009181c gcc/fortran/gfortranspec.c f519487227b89f7bf81fefec0890b646 gcc/fortran/interface.c ! 7a2b0d45028389c5ff0597322e76ab44 gcc/fortran/intrinsic.c abc87572b30804f606b83e64ad5d40b1 gcc/fortran/intrinsic.h 142af973fab400802b42296914efd857 gcc/fortran/intrinsic.texi e8e86258dcee5ce75ba45253468ca0db gcc/fortran/invoke.texi --- 4666,4687 ---- 83041f3879c600754744a8da84761bc9 gcc/fortran/cpp.h 112c4ba412ed2704834031ec9a0838fa gcc/fortran/data.c 167ea51b39af01ee143176fe03d80fb1 gcc/fortran/data.h ! a81b03d1d2fb3100c2f44e78f6f2dd0e gcc/fortran/decl.c a35f5788bded49237879a7f19a6288ab gcc/fortran/dependency.c 272c4deffabcf4caf71d639c1c58c42d gcc/fortran/dependency.h 7819b2970d4d816cafb214702abb4ef5 gcc/fortran/dump-parse-tree.c 3de13f2b47e6b19d0ec70c245e5afabd gcc/fortran/error.c ! 7695f7d5959817fff6b02f750743a648 gcc/fortran/expr.c 8183028b3162dfef1b367f187a615b42 gcc/fortran/f95-lang.c ! cdb1d159bf653f96c8f34772ae2e5133 gcc/fortran/frontend-passes.c 9295becaf3bc8598cfdf49e3a4dd9f9b gcc/fortran/gfc-diagnostic.def 23d6c9cd5c12c7f2aca8fd69d8420b43 gcc/fortran/gfc-internals.texi d27235635f3a8da5058b24e0f055bf7d gcc/fortran/gfortran.h ! a2f35fc3a8d1bcc3e9f2a93564eb1b37 gcc/fortran/gfortran.info 80c16dc56896ccc10c0dc114ac976580 gcc/fortran/gfortran.texi ! b60d4d28d06ef6858b2d4edcc82a960b gcc/fortran/gfortranspec.c f519487227b89f7bf81fefec0890b646 gcc/fortran/interface.c ! 3fc77c67fd807894c0d1d2c8e76d454e gcc/fortran/intrinsic.c abc87572b30804f606b83e64ad5d40b1 gcc/fortran/intrinsic.h 142af973fab400802b42296914efd857 gcc/fortran/intrinsic.texi e8e86258dcee5ce75ba45253468ca0db gcc/fortran/invoke.texi *************** bcd95c52fee7834e91ea18d02d609eef gcc/fo *** 4692,4709 **** 8cd46cabc2dfb1a7496801a089b86445 gcc/fortran/matchexp.c e91ec831c84ed9fa96a1533122ba5461 gcc/fortran/mathbuiltins.def 0b73aa1351022bc9b69b35d237f97d12 gcc/fortran/misc.c ! 90de8ceb7bf48f35b7e7bc456635ccb5 gcc/fortran/module.c ! 7565bb87b7be3f2074aca168672f811b gcc/fortran/openmp.c f8b10b2e5c40bc25b4d9eef7295880fc gcc/fortran/options.c ! dbb8f0b12186b1b194ad630162aed040 gcc/fortran/parse.c 043cf75f229c25d3de2bb79cc984c69d gcc/fortran/parse.h 0a4f5b165f9cfa5a7f1629102b6b1a98 gcc/fortran/primary.c ! 215f1b1705d6bc81b86166a1dd2dc408 gcc/fortran/resolve.c 99540dc62dd0f048881facab0517a129 gcc/fortran/scanner.c 075cca4c5736634c587f4ed50ddc9f93 gcc/fortran/scanner.h 46390687ba9617a28b199c3d60830027 gcc/fortran/simplify.c 75d50e5ade35f92e65fab4fe0b20630b gcc/fortran/st.c ! 3ed89d67461ca9398cf546c39be0ea59 gcc/fortran/symbol.c a384935370d518ce742fb597d42cb542 gcc/fortran/target-memory.c 2da60d02c0a00a10366e3eb9b9897e69 gcc/fortran/target-memory.h 0f8231d8b4e17fbfb3294c5a2bf761e5 gcc/fortran/trans-array.c --- 4698,4715 ---- 8cd46cabc2dfb1a7496801a089b86445 gcc/fortran/matchexp.c e91ec831c84ed9fa96a1533122ba5461 gcc/fortran/mathbuiltins.def 0b73aa1351022bc9b69b35d237f97d12 gcc/fortran/misc.c ! da99aebea97e8a87b32591e67c9df652 gcc/fortran/module.c ! 5b74aa7e981eda790f272d7513767f14 gcc/fortran/openmp.c f8b10b2e5c40bc25b4d9eef7295880fc gcc/fortran/options.c ! 59266df0f9dea339a057f44b1bfd82d2 gcc/fortran/parse.c 043cf75f229c25d3de2bb79cc984c69d gcc/fortran/parse.h 0a4f5b165f9cfa5a7f1629102b6b1a98 gcc/fortran/primary.c ! f5851f8933f9db1d07584acceff00105 gcc/fortran/resolve.c 99540dc62dd0f048881facab0517a129 gcc/fortran/scanner.c 075cca4c5736634c587f4ed50ddc9f93 gcc/fortran/scanner.h 46390687ba9617a28b199c3d60830027 gcc/fortran/simplify.c 75d50e5ade35f92e65fab4fe0b20630b gcc/fortran/st.c ! 9e2b180b0a084bc679183d6d796b763a gcc/fortran/symbol.c a384935370d518ce742fb597d42cb542 gcc/fortran/target-memory.c 2da60d02c0a00a10366e3eb9b9897e69 gcc/fortran/target-memory.h 0f8231d8b4e17fbfb3294c5a2bf761e5 gcc/fortran/trans-array.c *************** a384935370d518ce742fb597d42cb542 gcc/fo *** 4711,4731 **** 2ff797b2faf1df38554b343b691f0019 gcc/fortran/trans-common.c 7ca10244eca4229e1c832b3c393d9a24 gcc/fortran/trans-const.c d23a0f8bcd86907559306d74723ffdbd gcc/fortran/trans-const.h ! a19bca1b2989d2f8e1abaa6a92ea964e gcc/fortran/trans-decl.c ! 022b3786dba46d3c38cc71ecfa67ea02 gcc/fortran/trans-expr.c 13a2ad4df58f0c9265d5986bd124ab8d gcc/fortran/trans-intrinsic.c 988afa7187f8648d73cbbdd53cf6155b gcc/fortran/trans-io.c ! 03416c7ba17b632460bb8ed766f0fc2b gcc/fortran/trans-openmp.c c9523529693197ab087f85d534dd8566 gcc/fortran/trans-stmt.c bd26fd364f82b04b35ca797f1500c5cd gcc/fortran/trans-stmt.h ! 3a0a015557497b74675a5808c440f290 gcc/fortran/trans-types.c 82b8673b874f75d8200f4128222beeee gcc/fortran/trans-types.h ! adca0f1898c7b04c8e1d9aee387964bd gcc/fortran/trans.c 584e7bad1d3257b528944c0a88ac18e9 gcc/fortran/trans.h ce4ba327ea19d94b982917bf5b2884d4 gcc/fortran/types.def e02967179fdfb529c8aff94baaf469c2 gcc/fp-test.c ! b61f1a62642aad6032bd3875e55d56ac gcc/function.c ! 047cfc91e18845f3b5cf442dbbdd1ee7 gcc/function.h 497184e6dc781c16b3012d224ab58dd0 gcc/fwprop.c 51d4643fae226ae5cb6c726118db12a3 gcc/gcc-ar.c 90a3361d438bfdd5cf633291501756c1 gcc/gcc-main.c --- 4717,4737 ---- 2ff797b2faf1df38554b343b691f0019 gcc/fortran/trans-common.c 7ca10244eca4229e1c832b3c393d9a24 gcc/fortran/trans-const.c d23a0f8bcd86907559306d74723ffdbd gcc/fortran/trans-const.h ! 90332753b200ef64c8733124ffd4d50d gcc/fortran/trans-decl.c ! 1b647b708eee0882ccf7de19ef628722 gcc/fortran/trans-expr.c 13a2ad4df58f0c9265d5986bd124ab8d gcc/fortran/trans-intrinsic.c 988afa7187f8648d73cbbdd53cf6155b gcc/fortran/trans-io.c ! cb2676ec80bbc5af31cd51e3cd31be6b gcc/fortran/trans-openmp.c c9523529693197ab087f85d534dd8566 gcc/fortran/trans-stmt.c bd26fd364f82b04b35ca797f1500c5cd gcc/fortran/trans-stmt.h ! 357c5b77629ec86c3d0d449e0ee7a8e6 gcc/fortran/trans-types.c 82b8673b874f75d8200f4128222beeee gcc/fortran/trans-types.h ! 4675996a6f5ff91015bf3404d5524ea0 gcc/fortran/trans.c 584e7bad1d3257b528944c0a88ac18e9 gcc/fortran/trans.h ce4ba327ea19d94b982917bf5b2884d4 gcc/fortran/types.def e02967179fdfb529c8aff94baaf469c2 gcc/fp-test.c ! 858bb03b609b117dfa5a1e8407306754 gcc/function.c ! 17cb1003d8ab8c1905fd3d57d38144b4 gcc/function.h 497184e6dc781c16b3012d224ab58dd0 gcc/fwprop.c 51d4643fae226ae5cb6c726118db12a3 gcc/gcc-ar.c 90a3361d438bfdd5cf633291501756c1 gcc/gcc-main.c *************** b4465d909a319a9a76bf72f7bbf227d1 gcc/gc *** 4733,4750 **** 22091c79c390a71cf211f90328383954 gcc/gcc-rich-location.c 6ab0670ac8edcc1a6f5cd76e7e47a982 gcc/gcc-rich-location.h 3ec648b31caf0bcc6b2062384510367b gcc/gcc-symtab.h ! db7a081100b3eef37a26dcba668fb64a gcc/gcc.c 8a5a93ab3252c5ded6be74e451700891 gcc/gcc.h 1bf3695cc620fbe4091e454d41be48a5 gcc/gcov-counter.def ! 46c61075acf42b3a7891409b607f0d19 gcc/gcov-dump.c ! 0efd28d953450ae8d7278860f0a575a4 gcc/gcov-io.c 7508c50ed72374750600c67262a0ee91 gcc/gcov-io.h b9f30fe6de4bc97164f6b840c88115a0 gcc/gcov-iov.c ! 0f896fd895be0d523f2ce0c223a47c6f gcc/gcov-tool.c ! 383f00b305ba1e312a8ddbd8cf0f000c gcc/gcov.c 0b3a6763857eb5018cc264aaeffac4a1 gcc/gcse-common.c 80740301e6b9f5adcb06f427fad71cdf gcc/gcse-common.h ! 72615267c975f93c3f660fa5fde4ee92 gcc/gcse.c cce1736eb13b343e6c33ec40948e365b gcc/gcse.h af83e4b4719ee065872080b713d24c2f gcc/gdbasan.in 1b66c4a93f2e26315375fa3d55d93e73 gcc/gdbhooks.py --- 4739,4756 ---- 22091c79c390a71cf211f90328383954 gcc/gcc-rich-location.c 6ab0670ac8edcc1a6f5cd76e7e47a982 gcc/gcc-rich-location.h 3ec648b31caf0bcc6b2062384510367b gcc/gcc-symtab.h ! 458f988b75accacbc948592ebf758a36 gcc/gcc.c 8a5a93ab3252c5ded6be74e451700891 gcc/gcc.h 1bf3695cc620fbe4091e454d41be48a5 gcc/gcov-counter.def ! c67781f214a5a3212bd9e68127a31237 gcc/gcov-dump.c ! 4c09e84b0f8d1e2b1ad5cc5579c618c3 gcc/gcov-io.c 7508c50ed72374750600c67262a0ee91 gcc/gcov-io.h b9f30fe6de4bc97164f6b840c88115a0 gcc/gcov-iov.c ! 09ec0e7c002e1e3bc10d457e29392518 gcc/gcov-tool.c ! 9df752eec85f0e461533a46d02471dbe gcc/gcov.c 0b3a6763857eb5018cc264aaeffac4a1 gcc/gcse-common.c 80740301e6b9f5adcb06f427fad71cdf gcc/gcse-common.h ! c0d217c92cb20b7b9f39b1e1395c8071 gcc/gcse.c cce1736eb13b343e6c33ec40948e365b gcc/gcse.h af83e4b4719ee065872080b713d24c2f gcc/gdbasan.in 1b66c4a93f2e26315375fa3d55d93e73 gcc/gdbhooks.py *************** a8c1ed7f39b117949e82c995bcb82b52 gcc/ge *** 4763,4781 **** bde14a2746a68e2110c947c6464860ba gcc/genconstants.c b928804fdd0d35d52ee55ad8e0382433 gcc/genemit.c ec7357ffd25aa42099050656cdd923f3 gcc/genenums.c ! 87fc6979a1576e1847755f66d7736753 gcc/generic-match-head.c 03c37e7110342d08ac445192af3d4afb gcc/generic-match.h 25b1b08c7f2e15a61f67137a395f2be5 gcc/genextract.c 282f3c7433a024d985ddccc10c82d417 gcc/genflags.c d44b194500c23b5c542dbac2c46abcec gcc/gengenrtl.c ! 0d51d96473c4e17a4708d071df968446 gcc/gengtype-lex.c 5a1368b972210328f48b0ea87a7191c1 gcc/gengtype-lex.l ff52666a6b0aebb48f2a4f746fe39b50 gcc/gengtype-parse.c 0151a4b7715cf1cb836ee33cf7bfdf27 gcc/gengtype-state.c db2e5a3681b97d90acccf90143063e63 gcc/gengtype.c 43fa66a1baf8052c56056203218486bb gcc/gengtype.h 79b33f0c8ac99ccfc71dcdf3e27ee2bf gcc/genhooks.c ! 3be5935abab096a672b81c80b559ef1b gcc/genmatch.c 07b0962a5b0ac2a5f29d44d710ce1ea7 gcc/genmddeps.c 43130364faec8aac159d938938a22fad gcc/genmddump.c 7c6aaaace1e7de1494b16ba3c1abbdb0 gcc/genmodes.c --- 4769,4787 ---- bde14a2746a68e2110c947c6464860ba gcc/genconstants.c b928804fdd0d35d52ee55ad8e0382433 gcc/genemit.c ec7357ffd25aa42099050656cdd923f3 gcc/genenums.c ! 96d3d9f8db34a41848364c80a2352dc8 gcc/generic-match-head.c 03c37e7110342d08ac445192af3d4afb gcc/generic-match.h 25b1b08c7f2e15a61f67137a395f2be5 gcc/genextract.c 282f3c7433a024d985ddccc10c82d417 gcc/genflags.c d44b194500c23b5c542dbac2c46abcec gcc/gengenrtl.c ! 649471ecc328d1da2e0219201ec56d32 gcc/gengtype-lex.c 5a1368b972210328f48b0ea87a7191c1 gcc/gengtype-lex.l ff52666a6b0aebb48f2a4f746fe39b50 gcc/gengtype-parse.c 0151a4b7715cf1cb836ee33cf7bfdf27 gcc/gengtype-state.c db2e5a3681b97d90acccf90143063e63 gcc/gengtype.c 43fa66a1baf8052c56056203218486bb gcc/gengtype.h 79b33f0c8ac99ccfc71dcdf3e27ee2bf gcc/genhooks.c ! 4c7f0c4164550ceb05044d5c2c3ce324 gcc/genmatch.c 07b0962a5b0ac2a5f29d44d710ce1ea7 gcc/genmddeps.c 43130364faec8aac159d938938a22fad gcc/genmddump.c 7c6aaaace1e7de1494b16ba3c1abbdb0 gcc/genmodes.c *************** d02355424c03ecf19c6b3f761cd634b4 gcc/gg *** 4795,4803 **** f27627de4e242103ec999d1ed5e0069e gcc/ggc.h 4812f02602614fff1a97ea875ec99db7 gcc/gimple-builder.c 18fb4705ad51bdf06734fbcfc8e39d64 gcc/gimple-builder.h ! f4acee1cf4c45a5b6db4d0ce9806d3cd gcc/gimple-expr.c c17954a852b3ab19a3008cca3b24c128 gcc/gimple-expr.h ! d0508247d09b099c588815b5d8b86570 gcc/gimple-fold.c 8951c8587158bdc60d4e7d612c6f838c gcc/gimple-fold.h a14e519ebabb942d1e8a48a4403acab5 gcc/gimple-iterator.c efd0e45c5f633c150550050337d54cd2 gcc/gimple-iterator.h --- 4801,4809 ---- f27627de4e242103ec999d1ed5e0069e gcc/ggc.h 4812f02602614fff1a97ea875ec99db7 gcc/gimple-builder.c 18fb4705ad51bdf06734fbcfc8e39d64 gcc/gimple-builder.h ! 6cce70751070c7f77b8b0a41983d9c1a gcc/gimple-expr.c c17954a852b3ab19a3008cca3b24c128 gcc/gimple-expr.h ! 46159d48910474de657313f526e9d8b9 gcc/gimple-fold.c 8951c8587158bdc60d4e7d612c6f838c gcc/gimple-fold.h a14e519ebabb942d1e8a48a4403acab5 gcc/gimple-iterator.c efd0e45c5f633c150550050337d54cd2 gcc/gimple-iterator.h *************** c6406313fb24ec56d6a71e73606ac882 gcc/gi *** 4820,4831 **** 8c571fcc3b1ac0c3989e3a4973246484 gcc/gimple-streamer.h 5b4269de0e90ff1a0e228f16c36acf15 gcc/gimple-walk.c ad1356d1aee1bfaba3647e9dd12fb0bc gcc/gimple-walk.h ! b174a67cf43b8c8919274680e0b3ed21 gcc/gimple.c 65f6f08852f115424e8495c343dcba61 gcc/gimple.def 641cc4b975ba19a5b0e628733901c0cd gcc/gimple.h e679c1b4ca7b2361262d0c6fa84805d2 gcc/gimplify-me.c 16af853ca2f3e873e723eb5ff29a8168 gcc/gimplify-me.h ! 65e8c931475ca68d8dcacbe0e53f438c gcc/gimplify.c 89047a7045c4653b6016516742695593 gcc/gimplify.h f8d3ba18b33f417a9767d330d93c0783 gcc/ginclude/float.h 619900a9f2191899ea818da9819f1182 gcc/ginclude/iso646.h --- 4826,4837 ---- 8c571fcc3b1ac0c3989e3a4973246484 gcc/gimple-streamer.h 5b4269de0e90ff1a0e228f16c36acf15 gcc/gimple-walk.c ad1356d1aee1bfaba3647e9dd12fb0bc gcc/gimple-walk.h ! a2785905366f09f1f079433963ea1253 gcc/gimple.c 65f6f08852f115424e8495c343dcba61 gcc/gimple.def 641cc4b975ba19a5b0e628733901c0cd gcc/gimple.h e679c1b4ca7b2361262d0c6fa84805d2 gcc/gimplify-me.c 16af853ca2f3e873e723eb5ff29a8168 gcc/gimplify-me.h ! 626a18c8582070a93687c2468779ca3a gcc/gimplify.c 89047a7045c4653b6016516742695593 gcc/gimplify.h f8d3ba18b33f417a9767d330d93c0783 gcc/ginclude/float.h 619900a9f2191899ea818da9819f1182 gcc/ginclude/iso646.h *************** f85aa0745c3e9e0d32fa64753089b2f1 gcc/gi *** 4842,4855 **** 0084f5d38807d071ff480eae89712f6f gcc/ginclude/unwind-arm-common.h 8d9ecf0d6ef93c79623ce1d27a32a2cb gcc/ginclude/varargs.h b54c253a51ca26084af892b1075aca95 gcc/glimits.h ! b4e074a040aa22faa1e3a1fac68452e9 gcc/go/ChangeLog c17df7037dd63662580cbdd99682dfcb gcc/go/Make-lang.in 60ea054548c83c7f66170073f9f3e74c gcc/go/README.gcc 8f67504370310cab25d2ff85696d5827 gcc/go/config-lang.in dd4fa176841ea7cf625980bd424fa7d3 gcc/go/gccgo.texi 7abd8ba03fd0dc867d35a00935f3f369 gcc/go/go-backend.c e9c328c9551317fed602dd224f199216 gcc/go/go-c.h ! 7472539c9df57466ae5360a935cc75f3 gcc/go/go-gcc.cc c4671c4850f97c06c588015cf629ee42 gcc/go/go-lang.c 23c13bf184eab0071ce44a00188801f6 gcc/go/go-linemap.cc e044aac17049110bf65f2288f6f7cace gcc/go/go-location.h --- 4848,4861 ---- 0084f5d38807d071ff480eae89712f6f gcc/ginclude/unwind-arm-common.h 8d9ecf0d6ef93c79623ce1d27a32a2cb gcc/ginclude/varargs.h b54c253a51ca26084af892b1075aca95 gcc/glimits.h ! 40a75dbd5fbf04055c856ffe5278d121 gcc/go/ChangeLog c17df7037dd63662580cbdd99682dfcb gcc/go/Make-lang.in 60ea054548c83c7f66170073f9f3e74c gcc/go/README.gcc 8f67504370310cab25d2ff85696d5827 gcc/go/config-lang.in dd4fa176841ea7cf625980bd424fa7d3 gcc/go/gccgo.texi 7abd8ba03fd0dc867d35a00935f3f369 gcc/go/go-backend.c e9c328c9551317fed602dd224f199216 gcc/go/go-c.h ! 8e734a8022107822c34a79a3a97112a6 gcc/go/go-gcc.cc c4671c4850f97c06c588015cf629ee42 gcc/go/go-lang.c 23c13bf184eab0071ce44a00188801f6 gcc/go/go-linemap.cc e044aac17049110bf65f2288f6f7cace gcc/go/go-location.h *************** ca3b234f7d0de8a560108e6e1464be53 gcc/go *** 4867,4874 **** e3ce95084dcb217a0c25620c6880169a gcc/go/gofrontend/escape.h 2e26e60d3afa0dc32c08080dadfb2fa9 gcc/go/gofrontend/export.cc 4df15bc59bd6fe46102428109d840294 gcc/go/gofrontend/export.h ! 00a1ff1f666c12a04db6acfb587edcb7 gcc/go/gofrontend/expressions.cc ! 328819e7b2482c4658fa9820c4a6ce6a gcc/go/gofrontend/expressions.h 19e66447fa803385274b4e1a7501a4d5 gcc/go/gofrontend/go-dump.cc e3f005ccc40000dcaf14ab6eec979f69 gcc/go/gofrontend/go-dump.h 505078b1e9185e86c97fda5cda6fa67a gcc/go/gofrontend/go-linemap.h --- 4873,4880 ---- e3ce95084dcb217a0c25620c6880169a gcc/go/gofrontend/escape.h 2e26e60d3afa0dc32c08080dadfb2fa9 gcc/go/gofrontend/export.cc 4df15bc59bd6fe46102428109d840294 gcc/go/gofrontend/export.h ! 7a782c3f34e862505a7b4feae66861a7 gcc/go/gofrontend/expressions.cc ! 44b37952324ecb160415b99da314164c gcc/go/gofrontend/expressions.h 19e66447fa803385274b4e1a7501a4d5 gcc/go/gofrontend/go-dump.cc e3f005ccc40000dcaf14ab6eec979f69 gcc/go/gofrontend/go-dump.h 505078b1e9185e86c97fda5cda6fa67a gcc/go/gofrontend/go-linemap.h *************** df0b2e89a7ce7d87c1816e63cdecbf48 gcc/go *** 4891,4897 **** f5c93bbd3acba425df7838d8ed3c8f1c gcc/go/gofrontend/statements.cc cbfb64c251df0db3e5ea8fdbb8082c4d gcc/go/gofrontend/statements.h 0ba1a11b029f92c6795e4c940c966f48 gcc/go/gofrontend/string-dump.h ! 18e6f0d6a260c37000a649c37ec50d73 gcc/go/gofrontend/types.cc bcafbf2626b564df6e9b7d55c03fd716 gcc/go/gofrontend/types.h 3662dad559a197b0771d9930d494949d gcc/go/gofrontend/unsafe.cc 7e30663b5b82b2f71ca4f3e91820a0df gcc/go/gospec.c --- 4897,4903 ---- f5c93bbd3acba425df7838d8ed3c8f1c gcc/go/gofrontend/statements.cc cbfb64c251df0db3e5ea8fdbb8082c4d gcc/go/gofrontend/statements.h 0ba1a11b029f92c6795e4c940c966f48 gcc/go/gofrontend/string-dump.h ! 80750415a7437275e3f9fb85bbf70827 gcc/go/gofrontend/types.cc bcafbf2626b564df6e9b7d55c03fd716 gcc/go/gofrontend/types.h 3662dad559a197b0771d9930d494949d gcc/go/gofrontend/unsafe.cc 7e30663b5b82b2f71ca4f3e91820a0df gcc/go/gospec.c *************** d4cdce02971c5f431434a19b1b4e5302 gcc/gr *** 4903,4913 **** 02e7e8c97cb2d8864b2f8a3135ed0011 gcc/graphds.c 43af169612c4e4d04e00673de385a56b gcc/graphds.h 800359328b63c4c5c0ef9d59bad00fca gcc/graphite-dependences.c ! 270c9294a35d9b4de4b4afa021b7774d gcc/graphite-isl-ast-to-gimple.c d7586bd35c3d11933ceb61445987b1be gcc/graphite-optimize-isl.c 44fa75ae4f5cb0ac377521ea75ea1739 gcc/graphite-poly.c ! 24cb5670390b40885b9f7e8cbc9e8f2d gcc/graphite-scop-detection.c ! 2145e44f71f0e71c5d7525d412b11dc6 gcc/graphite-sese-to-poly.c 5b53b1f39257a74d35d74267a10667d2 gcc/graphite.c e2a89ed2d54d88eb79e9c45ac760ba2d gcc/graphite.h 78929a7471f65e2cc719f6ceecc9783e gcc/gsstruct.def --- 4909,4919 ---- 02e7e8c97cb2d8864b2f8a3135ed0011 gcc/graphds.c 43af169612c4e4d04e00673de385a56b gcc/graphds.h 800359328b63c4c5c0ef9d59bad00fca gcc/graphite-dependences.c ! d71c41b1342ff36c768ea6fd82eedf25 gcc/graphite-isl-ast-to-gimple.c d7586bd35c3d11933ceb61445987b1be gcc/graphite-optimize-isl.c 44fa75ae4f5cb0ac377521ea75ea1739 gcc/graphite-poly.c ! 24daa11affe5e0abe5075891a94d0200 gcc/graphite-scop-detection.c ! 32d776f13b8baaf8bbdbe2e053b48779 gcc/graphite-sese-to-poly.c 5b53b1f39257a74d35d74267a10667d2 gcc/graphite.c e2a89ed2d54d88eb79e9c45ac760ba2d gcc/graphite.h 78929a7471f65e2cc719f6ceecc9783e gcc/gsstruct.def *************** e58d1c401a7593922b73a20746f8ffb8 gcc/in *** 4951,4957 **** 175904f3b9bf34ab0110539281d28c85 gcc/input.h 9660f1e74083fc135ca89befb999845b gcc/insn-addr.h 90dd0b46cd7663ba2931f2dc558feb26 gcc/insn-notes.def ! d09143bc0a89fd36399dc99bd81a29e1 gcc/internal-fn.c 8c2c2046c13cb04e77d871bf9e264fe0 gcc/internal-fn.def f6eb1829b56b52c1a98e463764f15bb2 gcc/internal-fn.h fdde96aa99d01f4a2e122427c73416e1 gcc/intl.c --- 4957,4963 ---- 175904f3b9bf34ab0110539281d28c85 gcc/input.h 9660f1e74083fc135ca89befb999845b gcc/insn-addr.h 90dd0b46cd7663ba2931f2dc558feb26 gcc/insn-notes.def ! 3e9015bfabd48231979750202f99332a gcc/internal-fn.c 8c2c2046c13cb04e77d871bf9e264fe0 gcc/internal-fn.def f6eb1829b56b52c1a98e463764f15bb2 gcc/internal-fn.h fdde96aa99d01f4a2e122427c73416e1 gcc/intl.c *************** fdde96aa99d01f4a2e122427c73416e1 gcc/in *** 4959,5000 **** 26faa305263ec4b39061a74359f92d08 gcc/ipa-chkp.c 0c2184ed06610d2b6afe4b6f4d417dbe gcc/ipa-chkp.h c8fc9c40a8c111733a2e9563789133c3 gcc/ipa-comdats.c ! 0da86e2392b6146c88d243312dd82027 gcc/ipa-cp.c ! 3806b82c3219bbb056f09bdbb0fbe520 gcc/ipa-devirt.c 09da3707dcc58023f746ab4e5fabd815 gcc/ipa-hsa.c 8cbeebf152275e9611ce91064d1006f3 gcc/ipa-icf-gimple.c 455a02b19595e17d311284b20cd9946f gcc/ipa-icf-gimple.h 656649a92c699b991ad734d5d4d4e64e gcc/ipa-icf.c 3845e71367066e50a9ccb88e87633748 gcc/ipa-icf.h a218a778bd374b99f367df36983a2e05 gcc/ipa-inline-analysis.c ! 02dbb68319cd1e4e8561bbcdc37e0b9d gcc/ipa-inline-transform.c 6ffb5637e26835334d307237572a86d3 gcc/ipa-inline.c 5b9e28f57d5dcf8db033236d6d5ff9d7 gcc/ipa-inline.h ! f387d30f4cd871e5ff80caf759f44767 gcc/ipa-polymorphic-call.c dd94f55f59c59919fcfe73719b53804c gcc/ipa-profile.c ! 3dae52cd00288c68de72c5ec8d71ae11 gcc/ipa-prop.c 7a7386b290a6a93fcfde58bd22cfb1f2 gcc/ipa-prop.h ! 74d1b10d200d7553ee6f2ca92c0887df gcc/ipa-pure-const.c ef575b78ba6545da9a738bb6492ffaea gcc/ipa-ref.c 56f49eec5aed2b807dcd0aafbf2c0dbf gcc/ipa-ref.h 03c13844b2253af7baa44eabf818c3d0 gcc/ipa-reference.c 4d96038c87fe5da9b9b5b703221330f4 gcc/ipa-reference.h ! 7e1899b2fb2b7ead4af572a8f76a3c61 gcc/ipa-split.c ed182ec474e37f10686adf168a899e01 gcc/ipa-utils.c d01eb784d4a63008ba2460c3b47972b2 gcc/ipa-utils.h ! 380724728441c80c569b8ee31d8ab4f1 gcc/ipa-visibility.c f5194dfc342426fb120aa6ef0dac2984 gcc/ipa.c d40b36379402518db3bf0d60d97b5b55 gcc/ira-build.c 964fe62f78d9da617c7eb903c20eb3da gcc/ira-color.c e983cefc45ef903cf9ff61d0968b3bab gcc/ira-conflicts.c ! 4a40c778a56feadfe0bd42965dbe084b gcc/ira-costs.c ebfd92168b72929f96260301cb580262 gcc/ira-emit.c ! d450bfb56852e4c3e2c735b44810de2e gcc/ira-int.h a08f51632a3451b17596365fab878fae gcc/ira-lives.c ! 048a61ff1463a425c9c13312cc4f2b77 gcc/ira.c 74580aa160542aa4992d6a08ca5bc8f2 gcc/ira.h 31f4d25e8f125875a26ac35cbc927cb8 gcc/is-a.h ! 34a1d54e2f1aca6b56da12ffd10ff247 gcc/java/ChangeLog 507793f7d137759eaebce11bb6904781 gcc/java/ChangeLog.gimple-classes c52fb3faa0748d26588a8c62e7a032e3 gcc/java/ChangeLog.jit 3becfaac793f49e1f52cd74e78172b48 gcc/java/ChangeLog.ptr --- 4965,5006 ---- 26faa305263ec4b39061a74359f92d08 gcc/ipa-chkp.c 0c2184ed06610d2b6afe4b6f4d417dbe gcc/ipa-chkp.h c8fc9c40a8c111733a2e9563789133c3 gcc/ipa-comdats.c ! d18651f25a52a6e5c2de783bb6b5fdb8 gcc/ipa-cp.c ! ee752d58a5c16d0db5a6fc4b44b765ca gcc/ipa-devirt.c 09da3707dcc58023f746ab4e5fabd815 gcc/ipa-hsa.c 8cbeebf152275e9611ce91064d1006f3 gcc/ipa-icf-gimple.c 455a02b19595e17d311284b20cd9946f gcc/ipa-icf-gimple.h 656649a92c699b991ad734d5d4d4e64e gcc/ipa-icf.c 3845e71367066e50a9ccb88e87633748 gcc/ipa-icf.h a218a778bd374b99f367df36983a2e05 gcc/ipa-inline-analysis.c ! a9eff32f514d9abe395b1c13b615aee5 gcc/ipa-inline-transform.c 6ffb5637e26835334d307237572a86d3 gcc/ipa-inline.c 5b9e28f57d5dcf8db033236d6d5ff9d7 gcc/ipa-inline.h ! d12277093a8d08b8750ecd9ef6d26f73 gcc/ipa-polymorphic-call.c dd94f55f59c59919fcfe73719b53804c gcc/ipa-profile.c ! 459ab509dc3f06c1380c4296a2fa571a gcc/ipa-prop.c 7a7386b290a6a93fcfde58bd22cfb1f2 gcc/ipa-prop.h ! 330b52c57c009b059df7313150c41686 gcc/ipa-pure-const.c ef575b78ba6545da9a738bb6492ffaea gcc/ipa-ref.c 56f49eec5aed2b807dcd0aafbf2c0dbf gcc/ipa-ref.h 03c13844b2253af7baa44eabf818c3d0 gcc/ipa-reference.c 4d96038c87fe5da9b9b5b703221330f4 gcc/ipa-reference.h ! 4b2e0fdfbd44dd085d645754144f679d gcc/ipa-split.c ed182ec474e37f10686adf168a899e01 gcc/ipa-utils.c d01eb784d4a63008ba2460c3b47972b2 gcc/ipa-utils.h ! e8d8e427380a4bd39ba323b887a4bca9 gcc/ipa-visibility.c f5194dfc342426fb120aa6ef0dac2984 gcc/ipa.c d40b36379402518db3bf0d60d97b5b55 gcc/ira-build.c 964fe62f78d9da617c7eb903c20eb3da gcc/ira-color.c e983cefc45ef903cf9ff61d0968b3bab gcc/ira-conflicts.c ! 548b74bcda75bcc215ba12c2d8b6a23b gcc/ira-costs.c ebfd92168b72929f96260301cb580262 gcc/ira-emit.c ! 83ec3a50387f61edbea5374a533f3d91 gcc/ira-int.h a08f51632a3451b17596365fab878fae gcc/ira-lives.c ! 19f6e39fbb14bd42ec74540f3b5904c8 gcc/ira.c 74580aa160542aa4992d6a08ca5bc8f2 gcc/ira.h 31f4d25e8f125875a26ac35cbc927cb8 gcc/is-a.h ! f8bc828c6d7857779b6c652db22996dd gcc/java/ChangeLog 507793f7d137759eaebce11bb6904781 gcc/java/ChangeLog.gimple-classes c52fb3faa0748d26588a8c62e7a032e3 gcc/java/ChangeLog.jit 3becfaac793f49e1f52cd74e78172b48 gcc/java/ChangeLog.ptr *************** b0fd09d4fa689123dab011faedb7b9e7 gcc/ja *** 5017,5023 **** 3ed82a77c7a13054c63ef8ca3fe11fb0 gcc/java/javaop.def c851e061133018e15e2543e489b21cd4 gcc/java/javaop.h 96feacb5737904d4da06ef6303805cc2 gcc/java/jcf-depend.c ! 4406bbc06ebd0fed87883e510f1bb93d gcc/java/jcf-dump.c e3604dd0cca68707b6a994fbacde0e5b gcc/java/jcf-io.c a65983392bfb2e36550cb16a6021fd1a gcc/java/jcf-parse.c 67d6f5693d81e0d67495d33f8d288f7c gcc/java/jcf-path.c --- 5023,5029 ---- 3ed82a77c7a13054c63ef8ca3fe11fb0 gcc/java/javaop.def c851e061133018e15e2543e489b21cd4 gcc/java/javaop.h 96feacb5737904d4da06ef6303805cc2 gcc/java/jcf-depend.c ! 15595dece86939d0ffc2e83810466007 gcc/java/jcf-dump.c e3604dd0cca68707b6a994fbacde0e5b gcc/java/jcf-io.c a65983392bfb2e36550cb16a6021fd1a gcc/java/jcf-parse.c 67d6f5693d81e0d67495d33f8d288f7c gcc/java/jcf-path.c *************** f7682b6af1012b5e80ec7ad2afbc0c7b gcc/ja *** 5039,5045 **** d0022673f3c1d3b88ec58af0afae3a10 gcc/java/win32-host.c f3b9d6331e08c7be4b0c454896354320 gcc/java/zextract.c c5cc3108cb4c92253001c801b4323c72 gcc/java/zipfile.h ! 44034ded7bcace0656c4bc03974b7ca1 gcc/jit/ChangeLog 6071bdf04fb356c5ac99a99ec00c9a12 gcc/jit/ChangeLog.jit c901faa33fe9e228daf4730cebf58493 gcc/jit/Make-lang.in fd0d76b6467c987f813d430a35d4760a gcc/jit/TODO.rst --- 5045,5051 ---- d0022673f3c1d3b88ec58af0afae3a10 gcc/java/win32-host.c f3b9d6331e08c7be4b0c454896354320 gcc/java/zextract.c c5cc3108cb4c92253001c801b4323c72 gcc/java/zipfile.h ! 15c9d4d7632eee5413a7522b9a1f0c72 gcc/jit/ChangeLog 6071bdf04fb356c5ac99a99ec00c9a12 gcc/jit/ChangeLog.jit c901faa33fe9e228daf4730cebf58493 gcc/jit/Make-lang.in fd0d76b6467c987f813d430a35d4760a gcc/jit/TODO.rst *************** cb1bb960c49fd7c94335215ecb38e0d9 gcc/li *** 5131,5137 **** 83de5c6450456e215a5484083afcd32a gcc/limity.h 8af4edfa93cdd39b0e0238b353e52450 gcc/lists.c 16086d64468975aa4ba54f78d2a7b542 gcc/lock-and-run.sh ! 8c863978f7835f5151b8d06db4c188dd gcc/loop-doloop.c 2a5aa60c754420a976b7691a7b112e09 gcc/loop-init.c 30c39c53d73587261d4b4c669d1c8af0 gcc/loop-invariant.c 389e5eba1fed82f05263da501c5a322c gcc/loop-iv.c --- 5137,5143 ---- 83de5c6450456e215a5484083afcd32a gcc/limity.h 8af4edfa93cdd39b0e0238b353e52450 gcc/lists.c 16086d64468975aa4ba54f78d2a7b542 gcc/lock-and-run.sh ! 4ddece6cfc77096de1ab81dad285c71d gcc/loop-doloop.c 2a5aa60c754420a976b7691a7b112e09 gcc/loop-init.c 30c39c53d73587261d4b4c669d1c8af0 gcc/loop-invariant.c 389e5eba1fed82f05263da501c5a322c gcc/loop-iv.c *************** d2dfe305d98199fd855b3c272a6b5817 gcc/lo *** 5141,5176 **** 180085424a33f9c10cbfbec3cb93efc9 gcc/lower-subreg.h 94dc02fec35d26d77004b2381d03cecc gcc/lra-assigns.c f4d829a6683fedfefe62a3e3ac43b786 gcc/lra-coalesce.c ! dfcc1bd64d1b22ad68ea5d393e63e8e0 gcc/lra-constraints.c 93e8a59645cee490782a216dc589d3e9 gcc/lra-eliminations.c 0ec666c87d6073289dff419425883a42 gcc/lra-int.h b25a89a4eea7f17af3b4fd6bd2db5d51 gcc/lra-lives.c ! 0e8fa2b2915cec41e6064151eec1bb59 gcc/lra-remat.c efcc5c3fd9badd23a1bec1dccd4e3d36 gcc/lra-spills.c 9369a238480de0b68a819392540667de gcc/lra.c 46b0f9512df7333037038c928b5c81d7 gcc/lra.h ! f7de66bdad2cff8c2ba57733d9b7af98 gcc/lto-cgraph.c c2db462bd6bae5d54ad68c35cfc3e4f0 gcc/lto-compress.c 89f19c1448c39424f2417d8c3b8894ba gcc/lto-compress.h 80c3ff24cc7ac2727022b2b59df2d13d gcc/lto-opts.c 983e3cdfbc24b3e956fc217f64eb07de gcc/lto-section-in.c 39e049d7c57dc1449677294e81cdad65 gcc/lto-section-names.h 32ac27eae1fd61f0baa4acfa3e24c355 gcc/lto-section-out.c ! 0e62588ade895bd5b41e9a9f468db224 gcc/lto-streamer-in.c b93b516820b533bd1682f7a148299c10 gcc/lto-streamer-out.c bdae986759b0d2c19d10cd95a3469cd6 gcc/lto-streamer.c ! cbc225f3a9d78c6fa301299f140baa3b gcc/lto-streamer.h fdd4f9b1c13609e47f794ce0d6f0e8da gcc/lto-wrapper.c ! 6545b920fc9a93f82c94eec77c8c1d38 gcc/lto/ChangeLog bdc9ad4ddf80ce5b1548924f27f8df54 gcc/lto/Make-lang.in aa2afb52f6db84edc90db60bc3566afe gcc/lto/common.c 6a181dcf9ccdcf338ab68dfd3e8ad75a gcc/lto/common.h 781182e3853c98133e52ae282200f73b gcc/lto/config-lang.in 7beb31d156a26623be5a29bee88d6399 gcc/lto/lang-specs.h f71ec5f2d42dab57f34078aea90bd6a9 gcc/lto/lang.opt ! 0bbc5d43608b8925e8a4bf0964a16ea2 gcc/lto/lto-lang.c ebdb315568c5e02e524992de99915d0f gcc/lto/lto-object.c ! 248b1106514fb28274ef40ea08a2b2d8 gcc/lto/lto-partition.c 951d15d79aa366d5055f880d2e9fabd0 gcc/lto/lto-partition.h f201454c2d7ed616ff317ce6b0c5d6fe gcc/lto/lto-symtab.c 46f5dceafcfeb62271edf76e1cd6aaf8 gcc/lto/lto-symtab.h --- 5147,5182 ---- 180085424a33f9c10cbfbec3cb93efc9 gcc/lower-subreg.h 94dc02fec35d26d77004b2381d03cecc gcc/lra-assigns.c f4d829a6683fedfefe62a3e3ac43b786 gcc/lra-coalesce.c ! 63942ce878bc910cb9c80cbcf89fc57c gcc/lra-constraints.c 93e8a59645cee490782a216dc589d3e9 gcc/lra-eliminations.c 0ec666c87d6073289dff419425883a42 gcc/lra-int.h b25a89a4eea7f17af3b4fd6bd2db5d51 gcc/lra-lives.c ! 8e1860282cb534901d7ff615a340cb08 gcc/lra-remat.c efcc5c3fd9badd23a1bec1dccd4e3d36 gcc/lra-spills.c 9369a238480de0b68a819392540667de gcc/lra.c 46b0f9512df7333037038c928b5c81d7 gcc/lra.h ! 985ec519e6805b0421930e4dec56c5ab gcc/lto-cgraph.c c2db462bd6bae5d54ad68c35cfc3e4f0 gcc/lto-compress.c 89f19c1448c39424f2417d8c3b8894ba gcc/lto-compress.h 80c3ff24cc7ac2727022b2b59df2d13d gcc/lto-opts.c 983e3cdfbc24b3e956fc217f64eb07de gcc/lto-section-in.c 39e049d7c57dc1449677294e81cdad65 gcc/lto-section-names.h 32ac27eae1fd61f0baa4acfa3e24c355 gcc/lto-section-out.c ! 639b478c6131079220477bedb1e47b30 gcc/lto-streamer-in.c b93b516820b533bd1682f7a148299c10 gcc/lto-streamer-out.c bdae986759b0d2c19d10cd95a3469cd6 gcc/lto-streamer.c ! 84dd34f2926fb927bddd444cbd5740ee gcc/lto-streamer.h fdd4f9b1c13609e47f794ce0d6f0e8da gcc/lto-wrapper.c ! 2f01d0020e2fd4e31566f54ccacdaace gcc/lto/ChangeLog bdc9ad4ddf80ce5b1548924f27f8df54 gcc/lto/Make-lang.in aa2afb52f6db84edc90db60bc3566afe gcc/lto/common.c 6a181dcf9ccdcf338ab68dfd3e8ad75a gcc/lto/common.h 781182e3853c98133e52ae282200f73b gcc/lto/config-lang.in 7beb31d156a26623be5a29bee88d6399 gcc/lto/lang-specs.h f71ec5f2d42dab57f34078aea90bd6a9 gcc/lto/lang.opt ! 4c83e04b5321b647889d9741dcb8c4b4 gcc/lto/lto-lang.c ebdb315568c5e02e524992de99915d0f gcc/lto/lto-object.c ! 4d806d3f2354a2eab518107c30a8900f gcc/lto/lto-partition.c 951d15d79aa366d5055f880d2e9fabd0 gcc/lto/lto-partition.h f201454c2d7ed616ff317ce6b0c5d6fe gcc/lto/lto-symtab.c 46f5dceafcfeb62271edf76e1cd6aaf8 gcc/lto/lto-symtab.h *************** ccfecfc6344c571f12776c61c50b98e1 gcc/lt *** 5180,5186 **** 1ad92c4f2096f1f11a9d722298472ee5 gcc/machmode.def 89fb633ceadc86168379eec86b822225 gcc/machmode.h cf42eb61030c258fdda933a353c46798 gcc/main.c ! 7af1043514419a0b1543c7f2d095ed24 gcc/match.pd b4586a3a75b5dc7b5d62ccb834ea81ef gcc/mcf.c 2befd16012fa1d3dc246e33d405b79f8 gcc/mem-stats-traits.h 3e4b7d3dfbb311377553673371f9561e gcc/mem-stats.h --- 5186,5192 ---- 1ad92c4f2096f1f11a9d722298472ee5 gcc/machmode.def 89fb633ceadc86168379eec86b822225 gcc/machmode.h cf42eb61030c258fdda933a353c46798 gcc/main.c ! 1806ddc7d7563d188fdcfb2841cacb57 gcc/match.pd b4586a3a75b5dc7b5d62ccb834ea81ef gcc/mcf.c 2befd16012fa1d3dc246e33d405b79f8 gcc/mem-stats-traits.h 3e4b7d3dfbb311377553673371f9561e gcc/mem-stats.h *************** e5b46c72998a06200ecc986fe1c79e56 gcc/mk *** 5190,5197 **** 5973888b10b2906aab70ce8da00128d2 gcc/mode-classes.def 5a9baa55381e02b459c341d64806ed7d gcc/mode-switching.c da4b5db61ce6faf08f42429c15f8fa06 gcc/modulo-sched.c ! 52d06569a72119f3428f65b0ead597d7 gcc/multiple_target.c ! 584f05a3d67f7f0f42776fe4e60346b2 gcc/objc/ChangeLog e0e250d535aa8a68ae28a8eac0b5d891 gcc/objc/Make-lang.in c30d037bac638bd79ce6921aad7056f0 gcc/objc/config-lang.in 3da193018c6dbee2a1f10c55657e1809 gcc/objc/lang-specs.h --- 5196,5203 ---- 5973888b10b2906aab70ce8da00128d2 gcc/mode-classes.def 5a9baa55381e02b459c341d64806ed7d gcc/mode-switching.c da4b5db61ce6faf08f42429c15f8fa06 gcc/modulo-sched.c ! d96ed9958d9632e5ac768579860166f0 gcc/multiple_target.c ! bcc91878b18dfaa8e57535604660d069 gcc/objc/ChangeLog e0e250d535aa8a68ae28a8eac0b5d891 gcc/objc/Make-lang.in c30d037bac638bd79ce6921aad7056f0 gcc/objc/config-lang.in 3da193018c6dbee2a1f10c55657e1809 gcc/objc/lang-specs.h *************** c702cd613c028b8ef8020cff71fbdc4d gcc/ob *** 5210,5216 **** 4c31a052046abab42222e4a4408d61f6 gcc/objc/objc-runtime-shared-support.c a243f7d55ec9ddd42101d3290be0e75e gcc/objc/objc-runtime-shared-support.h 96ed1eda42cd877908898ee0f7d77ca6 gcc/objc/objc-tree.def ! 49965eaacb2ca5fef062c6ca8713703b gcc/objcp/ChangeLog 96e34629089b8c3aa2a43d02340adcdd gcc/objcp/Make-lang.in 5ed4e1b3215d236abf28bf5ea33a79b6 gcc/objcp/config-lang.in bd48832cba9655ecb20a2db43e401205 gcc/objcp/lang-specs.h --- 5216,5222 ---- 4c31a052046abab42222e4a4408d61f6 gcc/objc/objc-runtime-shared-support.c a243f7d55ec9ddd42101d3290be0e75e gcc/objc/objc-runtime-shared-support.h 96ed1eda42cd877908898ee0f7d77ca6 gcc/objc/objc-tree.def ! 531759f8df3be36c8055a92892723884 gcc/objcp/ChangeLog 96e34629089b8c3aa2a43d02340adcdd gcc/objcp/Make-lang.in 5ed4e1b3215d236abf28bf5ea33a79b6 gcc/objcp/config-lang.in bd48832cba9655ecb20a2db43e401205 gcc/objcp/lang-specs.h *************** bd48832cba9655ecb20a2db43e401205 gcc/ob *** 5218,5224 **** 7d680f67db0eb1b8ff1b353ceb2caa2c gcc/objcp/objcp-decl.h 8cfb48ffee764ccd1ab5dbf70f0234e0 gcc/objcp/objcp-lang.c 742609336d1f57839866345f3fe16a98 gcc/omp-builtins.def ! 800a0d9f7a0aa8cedd0464da049bf5e2 gcc/omp-low.c 17f7f9a5279dd46aca82fdd23c6ed175 gcc/omp-low.h 1e1f9ff0b51d0841355e4ccab02555e5 gcc/omp-simd-clone.c f773f4ea009b64414353473ab70fc22d gcc/opt-functions.awk --- 5224,5230 ---- 7d680f67db0eb1b8ff1b353ceb2caa2c gcc/objcp/objcp-decl.h 8cfb48ffee764ccd1ab5dbf70f0234e0 gcc/objcp/objcp-lang.c 742609336d1f57839866345f3fe16a98 gcc/omp-builtins.def ! 01a48c0f7cbd54281c8f2a5afd2d2ba5 gcc/omp-low.c 17f7f9a5279dd46aca82fdd23c6ed175 gcc/omp-low.h 1e1f9ff0b51d0841355e4ccab02555e5 gcc/omp-simd-clone.c f773f4ea009b64414353473ab70fc22d gcc/opt-functions.awk *************** f7daf01f2540429baa36f933638dd34d gcc/ou *** 5246,5260 **** ffc82aaffe672d77f230f006908b6fd0 gcc/params-enum.h 6d350f6a56aff3c29a7b7ca665bc7c77 gcc/params-list.h 56fa7bf31c5d86186e22744a42543eac gcc/params.c ! 86f4270872b2a01ada79a1944661598e gcc/params.def aa4de28610e4765bdfd62c7780a7fdbf gcc/params.h faced9a76348a017a135efffbe0eaf5e gcc/pass_manager.h 06104fe7e3c63399d338f22901c2741c gcc/passes.c ! b4297fda0646de8d495847691de52b14 gcc/passes.def ! c35d166939d6fdbd9bb5853c96bb673b gcc/plugin.c 03231f119da6e6638a69e3c5111324f8 gcc/plugin.def eb08b5caab095677d912ce793705caf7 gcc/plugin.h ! f07af02080018ada9d4f8b68727c61ea gcc/po/ChangeLog b2d1566753aedf7900d55d33f985138c gcc/po/EXCLUDES bd056bfcd385263f3db54d24dec887fc gcc/po/be.gmo 3a73294a463e8e356414874bfb68eb2e gcc/po/be.po --- 5252,5266 ---- ffc82aaffe672d77f230f006908b6fd0 gcc/params-enum.h 6d350f6a56aff3c29a7b7ca665bc7c77 gcc/params-list.h 56fa7bf31c5d86186e22744a42543eac gcc/params.c ! a513b181050f2d240c41bb5fdb58dd72 gcc/params.def aa4de28610e4765bdfd62c7780a7fdbf gcc/params.h faced9a76348a017a135efffbe0eaf5e gcc/pass_manager.h 06104fe7e3c63399d338f22901c2741c gcc/passes.c ! dc6aed12ec5e928c80c813633c206004 gcc/passes.def ! e096740f20fe6b3282293fc93f25534f gcc/plugin.c 03231f119da6e6638a69e3c5111324f8 gcc/plugin.def eb08b5caab095677d912ce793705caf7 gcc/plugin.h ! acc1aefc35e99f1d81e99475e49e1e8c gcc/po/ChangeLog b2d1566753aedf7900d55d33f985138c gcc/po/EXCLUDES bd056bfcd385263f3db54d24dec887fc gcc/po/be.gmo 3a73294a463e8e356414874bfb68eb2e gcc/po/be.po *************** cc70c72957cff1e710b23dbe9d507443 gcc/po *** 5264,5277 **** 088a4ededc99540588bab41d66014858 gcc/po/de.po 0f8285dd8557282b2eaf6467f5657407 gcc/po/el.gmo c1ff020b18a51368db9607ccbbeaaa42 gcc/po/el.po ! 213e364f7da43135fcd8dae896a0e336 gcc/po/es.gmo ! d7cc0fe5000a6d41b63ee5fc83c01c41 gcc/po/es.po ! f9ca050e999d59313ea3c78909a9f041 gcc/po/exgettext d3bfe4fb20d853f28bbb2e560275e304 gcc/po/fi.gmo 3127fb1e25a5b3bb88c2995d8c11a8bc gcc/po/fi.po ! cb11c85c6a6819c75000050977c7157e gcc/po/fr.gmo ! 5069a422f67c27d5c129032a4a679e81 gcc/po/fr.po ! a380d09b1f2e4ac238b440718865ef66 gcc/po/gcc.pot 5d6d7afd8d8b00131a862318beccc74b gcc/po/hr.gmo 6186eb1c170cc87c61cade09807c5cb2 gcc/po/hr.po e2a2449eb084fd789d4d5de5107ec71c gcc/po/id.gmo --- 5270,5283 ---- 088a4ededc99540588bab41d66014858 gcc/po/de.po 0f8285dd8557282b2eaf6467f5657407 gcc/po/el.gmo c1ff020b18a51368db9607ccbbeaaa42 gcc/po/el.po ! 87599bd420d911326ee9c9aec6bca3a4 gcc/po/es.gmo ! b255558eaa9ef8b774fe13800fb4f719 gcc/po/es.po ! 6e40efc81f77ba2f1a02b3a942bb8296 gcc/po/exgettext d3bfe4fb20d853f28bbb2e560275e304 gcc/po/fi.gmo 3127fb1e25a5b3bb88c2995d8c11a8bc gcc/po/fi.po ! ef9ae622bb17e5b4b0cb10de2d8ae00d gcc/po/fr.gmo ! 4ed15adb5e3dd31fbf95f3394aed3cec gcc/po/fr.po ! 7c59c45f3b6dcd8af9f376eaec4c4380 gcc/po/gcc.pot 5d6d7afd8d8b00131a862318beccc74b gcc/po/hr.gmo 6186eb1c170cc87c61cade09807c5cb2 gcc/po/hr.po e2a2449eb084fd789d4d5de5107ec71c gcc/po/id.gmo *************** b3ab914b75cad131f23e0bf1339d642d gcc/po *** 5297,5303 **** 7032657d70a903f5d75696ea5de14457 gcc/po/zh_TW.gmo 2cdbb0fa7c665cce4d6d3ff525958adf gcc/po/zh_TW.po 69cb8c2cd669d2ccb4d80d86bafa9b03 gcc/postreload-gcse.c ! 652a5f22353b24336aad25fe019e6543 gcc/postreload.c 02aac36ac6c8089e57cdd45796f95237 gcc/predict.c 415a901fc3abaae33f61b9f1f799990d gcc/predict.def 553b321408297f956eb18cc94eef4e2d gcc/predict.h --- 5303,5309 ---- 7032657d70a903f5d75696ea5de14457 gcc/po/zh_TW.gmo 2cdbb0fa7c665cce4d6d3ff525958adf gcc/po/zh_TW.po 69cb8c2cd669d2ccb4d80d86bafa9b03 gcc/postreload-gcse.c ! 63a57e8e6f2adf1842b3865c3d451d38 gcc/postreload.c 02aac36ac6c8089e57cdd45796f95237 gcc/predict.c 415a901fc3abaae33f61b9f1f799990d gcc/predict.def 553b321408297f956eb18cc94eef4e2d gcc/predict.h *************** a5ef18ac5f749cc634f84d4973e1f537 gcc/pr *** 5314,5320 **** 3b27d8df6919f76040af0790bc20ddf2 gcc/read-md.c da163181b7b9de52b5ced97ec58438dd gcc/read-md.h 813aa6489b00e9b16bc07fc5ff94eb0c gcc/read-rtl.c ! acab6cfa0bd36b29c1347b448725cf47 gcc/real.c c491b51900a06e7ff86db90ef5aa0764 gcc/real.h f1d0c221012277898b08678be7adf997 gcc/realmpfr.c fac47f999b43725aa0113a21e9318b00 gcc/realmpfr.h --- 5320,5326 ---- 3b27d8df6919f76040af0790bc20ddf2 gcc/read-md.c da163181b7b9de52b5ced97ec58438dd gcc/read-md.h 813aa6489b00e9b16bc07fc5ff94eb0c gcc/read-rtl.c ! f5f2d5effa4a092e2ad7ae9e218df376 gcc/real.c c491b51900a06e7ff86db90ef5aa0764 gcc/real.h f1d0c221012277898b08678be7adf997 gcc/realmpfr.c fac47f999b43725aa0113a21e9318b00 gcc/realmpfr.h *************** e63fcf6dd469409d174998180691098b gcc/re *** 5334,5340 **** d4317de422a35b66c1618b7d8354b3f6 gcc/reload.c 4d9ef457fab328de8d75d78694a9b31d gcc/reload.h afb91f5a182c324d908f23dfe11f548f gcc/reload1.c ! d4117f915be01e2e0a18b1d416d9a4ae gcc/reorg.c bf1252245d535babfa24a237303e7b29 gcc/resource.c 4ea93ad8e433144870f7cbf37f816e1f gcc/resource.h 7c836e98661b7e6b63db89348be6214a gcc/rtl-chkp.c --- 5340,5346 ---- d4317de422a35b66c1618b7d8354b3f6 gcc/reload.c 4d9ef457fab328de8d75d78694a9b31d gcc/reload.h afb91f5a182c324d908f23dfe11f548f gcc/reload1.c ! 63bf45e5d16adb246722c8477531cbaa gcc/reorg.c bf1252245d535babfa24a237303e7b29 gcc/resource.c 4ea93ad8e433144870f7cbf37f816e1f gcc/resource.h 7c836e98661b7e6b63db89348be6214a gcc/rtl-chkp.c *************** f026bb9e1a00fedbacca236836cc9fe1 gcc/se *** 5365,5378 **** 143b7bfd2a985e5ef5c6188ed6fca821 gcc/sel-sched-dump.h 749f6f0790413c54ec0ee5a49c1fd5a0 gcc/sel-sched-ir.c f66e4b6fcc68dad613ac0f12ba573ee5 gcc/sel-sched-ir.h ! 9aca8d9110111a9c7e151a965240344d gcc/sel-sched.c d5f59bc7a87978c78b1f0017a8fa3b90 gcc/sel-sched.h 25b0d309c80f47e5d8610840bb16d571 gcc/sese.c 25e88cb3f28f314d95d2e26f7d22ddde gcc/sese.h 1d237562ab925216579c50bfbd77bc85 gcc/shrink-wrap.c 3436ff281fab7fb9d57e938898b7be8c gcc/shrink-wrap.h d224cc6bf0fd8d8cd3b3038b78cf0a11 gcc/signop.h ! 32372a84b7fb7cc666dcec9035bb5573 gcc/simplify-rtx.c 313b2917745aea0b562e53bef7263ae1 gcc/sparseset.c 32a9dbf0545f25b43a1bb3a30654b10c gcc/sparseset.h a6eb9aa21b664f67281e3af138c1df2d gcc/spellcheck-tree.c --- 5371,5384 ---- 143b7bfd2a985e5ef5c6188ed6fca821 gcc/sel-sched-dump.h 749f6f0790413c54ec0ee5a49c1fd5a0 gcc/sel-sched-ir.c f66e4b6fcc68dad613ac0f12ba573ee5 gcc/sel-sched-ir.h ! 16a7e91a1179a4cc1348fff291e6dfed gcc/sel-sched.c d5f59bc7a87978c78b1f0017a8fa3b90 gcc/sel-sched.h 25b0d309c80f47e5d8610840bb16d571 gcc/sese.c 25e88cb3f28f314d95d2e26f7d22ddde gcc/sese.h 1d237562ab925216579c50bfbd77bc85 gcc/shrink-wrap.c 3436ff281fab7fb9d57e938898b7be8c gcc/shrink-wrap.h d224cc6bf0fd8d8cd3b3038b78cf0a11 gcc/signop.h ! 79056c49c7791346ca6eec903567aeea gcc/simplify-rtx.c 313b2917745aea0b562e53bef7263ae1 gcc/sparseset.c 32a9dbf0545f25b43a1bb3a30654b10c gcc/sparseset.h a6eb9aa21b664f67281e3af138c1df2d gcc/spellcheck-tree.c *************** f5f79d3f7f15413b9096d592037d0446 gcc/st *** 5396,5402 **** f75b463b1db018200f196c0a0e918e3d gcc/stringpool.c 0803af7b75ee13cff5baffd8ff860b53 gcc/stringpool.h 13db02d15ea7277d1189f3b7d0557072 gcc/symbol-summary.h ! 77b58b8f60c55edd8958d50db11f0f9f gcc/symtab.c b2fe41501016667e8a7f7b1648c25b65 gcc/sync-builtins.def d89e42c95096b0f80d29548fecd3c8a6 gcc/system.h d15ba80a73576dfa8624740c7762f0f0 gcc/target-def.h --- 5402,5408 ---- f75b463b1db018200f196c0a0e918e3d gcc/stringpool.c 0803af7b75ee13cff5baffd8ff860b53 gcc/stringpool.h 13db02d15ea7277d1189f3b7d0557072 gcc/symbol-summary.h ! 13be08fb63dcbbbbbbe50403359c572e gcc/symtab.c b2fe41501016667e8a7f7b1648c25b65 gcc/sync-builtins.def d89e42c95096b0f80d29548fecd3c8a6 gcc/system.h d15ba80a73576dfa8624740c7762f0f0 gcc/target-def.h *************** d15ba80a73576dfa8624740c7762f0f0 gcc/ta *** 5404,5414 **** 09cfe0e0ec1d5046f34e2312e43eb0e8 gcc/target-globals.h 3a6821ad61dc3a0589ee2df5c4840df6 gcc/target-hooks-macros.h 838fe94c017691ae2d727077f784241a gcc/target-insns.def ! 424fa976908c0d941ac52cea1e7c95b1 gcc/target.def 43bc671be91bb4d94848b3e7f27a2930 gcc/target.h ! 390fdb346018f2dac89921ab740e4205 gcc/targhooks.c 4e44e54a960fb8713cc9c2975d7d27f9 gcc/targhooks.h ! f81e92239fa575a3d369ef847feb7d32 gcc/testsuite/ChangeLog 862f04afbd87da2cc6bc432c3f28430f gcc/testsuite/ChangeLog-1993-2007 029a5d8dacd25eb5d4711452ac448e5b gcc/testsuite/ChangeLog-2008 13ac28c41d51b66b4ec40dba6bd50f39 gcc/testsuite/ChangeLog-2009 --- 5410,5420 ---- 09cfe0e0ec1d5046f34e2312e43eb0e8 gcc/target-globals.h 3a6821ad61dc3a0589ee2df5c4840df6 gcc/target-hooks-macros.h 838fe94c017691ae2d727077f784241a gcc/target-insns.def ! d94eb43316cd04a038cba472458b9941 gcc/target.def 43bc671be91bb4d94848b3e7f27a2930 gcc/target.h ! afdabf32c1cb38e5544bd7a95d77845f gcc/targhooks.c 4e44e54a960fb8713cc9c2975d7d27f9 gcc/targhooks.h ! 3155a2f328dc1b3dbc86d4f5e5640a53 gcc/testsuite/ChangeLog 862f04afbd87da2cc6bc432c3f28430f gcc/testsuite/ChangeLog-1993-2007 029a5d8dacd25eb5d4711452ac448e5b gcc/testsuite/ChangeLog-2008 13ac28c41d51b66b4ec40dba6bd50f39 gcc/testsuite/ChangeLog-2009 *************** f79bc4a80b6890a56ed93a450311aa3f gcc/te *** 8078,8083 **** --- 8084,8090 ---- 42fc3aa54365f66ed90d26e70e157cc5 gcc/testsuite/c-c++-common/Wunused-var-12.c 15fe0702a484a3fe1c89d3bcd75bd508 gcc/testsuite/c-c++-common/Wunused-var-13.c 80c4ecb8009d5febfdba9eeaee769526 gcc/testsuite/c-c++-common/Wunused-var-14.c + 38f41715a5590e9152263fa65a5fd464 gcc/testsuite/c-c++-common/Wunused-var-16.c 5f69d6398e9b0fc829351a16f994916d gcc/testsuite/c-c++-common/Wunused-var-2.c 8504217c544401c14012c8e1a1c18970 gcc/testsuite/c-c++-common/Wunused-var-3.c 43839f1fa5726ea0a0d6e063d7980642 gcc/testsuite/c-c++-common/Wunused-var-4.c *************** ae5400233bb23dafe56f543cc5bb1ba6 gcc/te *** 8148,8153 **** --- 8155,8161 ---- 2a794af8b446f3413fe5b973ea309b7b gcc/testsuite/c-c++-common/asan/pr64820.c 430079f735bd0792e25216b9c0862dae gcc/testsuite/c-c++-common/asan/pr70541.c dee6718aa031ca364c15580524cba02b gcc/testsuite/c-c++-common/asan/pr70712.c + d4cafd1e2a02428237d07dbd1a042e54 gcc/testsuite/c-c++-common/asan/pr79944.c 53382ff9da47e361b5e5dc525d26e518 gcc/testsuite/c-c++-common/asan/red-align-1.c 40dc4b3092482d9427dfbc9415f0b0a8 gcc/testsuite/c-c++-common/asan/red-align-2.c 8940936501084c6e4d7f6d110ba612d8 gcc/testsuite/c-c++-common/asan/rlimit-mmap-test-1.c *************** fc773eb7f157bca78ec3ec3b690651cd gcc/te *** 8267,8272 **** --- 8275,8282 ---- 42ec4012de8202ec1100849077cf756a gcc/testsuite/c-c++-common/cilk-plus/CK/pr63307.c 65b5267c459e229f354bbc78bb054d9b gcc/testsuite/c-c++-common/cilk-plus/CK/pr69826-1.c 592958eac336c7a0ec397de746f07fcd gcc/testsuite/c-c++-common/cilk-plus/CK/pr69826-2.c + daa59a813ddb2262898d719bbf406aa1 gcc/testsuite/c-c++-common/cilk-plus/CK/pr79428-4.c + 77910ab2d274097e490925fbe44b6523 gcc/testsuite/c-c++-common/cilk-plus/CK/pr79428-7.c 8a70f2db9dba5ac2c7d4b6e8c09349cc gcc/testsuite/c-c++-common/cilk-plus/CK/spawn_in_return.c 18b039e638a83d3e168750d77150f57c gcc/testsuite/c-c++-common/cilk-plus/CK/spawnee_inline.c 724d7f3a3c81ade45c6b1a852304b7e3 gcc/testsuite/c-c++-common/cilk-plus/CK/spawner_inline.c *************** f5740839231c8e8304cea75d03b7fb0b gcc/te *** 8454,8465 **** da99712686fe793685ab6055e56491ed gcc/testsuite/c-c++-common/goacc/if-clause-2.c 3562d541b55248dec549e58714404d21 gcc/testsuite/c-c++-common/goacc/kernels-1.c 49535d0e79cfe2a3c595cef41f64c3e0 gcc/testsuite/c-c++-common/goacc/kernels-alias-2.c ! 67b6157dc4310795bed88f71bb45e29f gcc/testsuite/c-c++-common/goacc/kernels-alias-3.c ! ddb11f93965d11bb90dcd9bd3f99f156 gcc/testsuite/c-c++-common/goacc/kernels-alias-4.c ! 16a17f28e21c82c815d42fbe95179cec gcc/testsuite/c-c++-common/goacc/kernels-alias-5.c ! 67c9a9bc77d375297e5f8d8aa6558cfa gcc/testsuite/c-c++-common/goacc/kernels-alias-6.c ! 307ce591c5f308eb3571d8664596c6a5 gcc/testsuite/c-c++-common/goacc/kernels-alias-7.c ! d6b86983541aea5b0ea4073ad2f68692 gcc/testsuite/c-c++-common/goacc/kernels-alias-8.c e2a9cbb19ee091825a6c272813098029 gcc/testsuite/c-c++-common/goacc/kernels-alias-ipa-pta-2.c d7c4bc98680d9aee41756c5d1b5dffb6 gcc/testsuite/c-c++-common/goacc/kernels-alias-ipa-pta-3.c 2b543c4509b9dd121b87fc6367d41f78 gcc/testsuite/c-c++-common/goacc/kernels-alias-ipa-pta-4.c --- 8464,8475 ---- da99712686fe793685ab6055e56491ed gcc/testsuite/c-c++-common/goacc/if-clause-2.c 3562d541b55248dec549e58714404d21 gcc/testsuite/c-c++-common/goacc/kernels-1.c 49535d0e79cfe2a3c595cef41f64c3e0 gcc/testsuite/c-c++-common/goacc/kernels-alias-2.c ! b22fa8f5033d0cf254ba5fbbebcae032 gcc/testsuite/c-c++-common/goacc/kernels-alias-3.c ! aa5366d90bc230fd687a576a762248ee gcc/testsuite/c-c++-common/goacc/kernels-alias-4.c ! d96b6481be483baca0dfd486dab45a2e gcc/testsuite/c-c++-common/goacc/kernels-alias-5.c ! 3c89c1e0d95fb4f33562e9b7d8f26b5a gcc/testsuite/c-c++-common/goacc/kernels-alias-6.c ! 010520cb65564a4d628a3efd8f5309cd gcc/testsuite/c-c++-common/goacc/kernels-alias-7.c ! eec7263e8251e8ad4d5aeec9f0c73070 gcc/testsuite/c-c++-common/goacc/kernels-alias-8.c e2a9cbb19ee091825a6c272813098029 gcc/testsuite/c-c++-common/goacc/kernels-alias-ipa-pta-2.c d7c4bc98680d9aee41756c5d1b5dffb6 gcc/testsuite/c-c++-common/goacc/kernels-alias-ipa-pta-3.c 2b543c4509b9dd121b87fc6367d41f78 gcc/testsuite/c-c++-common/goacc/kernels-alias-ipa-pta-4.c *************** befbc361d92f725fefa0029d54d3c22b gcc/te *** 8600,8605 **** --- 8610,8622 ---- 4c7e38cbcd8c76fb43d8ce5a9a036711 gcc/testsuite/c-c++-common/gomp/pr70550-2.c 9c6ccd1b697ca4b2f7de134bafdfda56 gcc/testsuite/c-c++-common/gomp/pr71371.c 8d4187a1bda8777b2ff9ff3a8693ac86 gcc/testsuite/c-c++-common/gomp/pr71758.c + 659f0eff37ee1bdc697ff7962e983724 gcc/testsuite/c-c++-common/gomp/pr79428-2.c + d4234712e8b6ad1706a38530b6e6d890 gcc/testsuite/c-c++-common/gomp/pr79428-5.c + 2d68db57522d751eb11d8a844fa51e6d gcc/testsuite/c-c++-common/gomp/pr79428-6.c + 0c4f14dc0d4f392e3f8ebc8a86ed2e2f gcc/testsuite/c-c++-common/gomp/pr79429.c + aef2bdc20ca665badeb6ae399bf1d7e0 gcc/testsuite/c-c++-common/gomp/pr79431.c + a1d1201800784f60e84899ae25155f9b gcc/testsuite/c-c++-common/gomp/pr79512.c + 61e2ab40aa3cda7576749f11b6037c39 gcc/testsuite/c-c++-common/gomp/pr81006.c 5d522e2f1f7455bc45f6c1f230d5a5b0 gcc/testsuite/c-c++-common/gomp/priority-1.c 1dc7bbbafb91e179ac43fa3959ab125f gcc/testsuite/c-c++-common/gomp/reduction-1.c a73d7c3b3886856e6621c6e5854c3333 gcc/testsuite/c-c++-common/gomp/schedule-modifiers-1.c *************** d4e3dc1aa87409198ff78d00e3448b7a gcc/te *** 8625,8630 **** --- 8642,8648 ---- de3dd2daeb344b4e1fbcc4551d6441bc gcc/testsuite/c-c++-common/int128-types-1.c 01e056c68731cbfbfaba142a85c7d93a gcc/testsuite/c-c++-common/nonnull-1.c c173ff464a71a0767592505ad9027cfe gcc/testsuite/c-c++-common/nonnull-2.c + b5ecd0643340dd5cbd091366ced73bd5 gcc/testsuite/c-c++-common/nonnull-3.c 83a7bbdd99f0b1af923f0357c83b8dd1 gcc/testsuite/c-c++-common/opaque-vector.c f5dce8e27cfb8a6bfffe57596fecb796 gcc/testsuite/c-c++-common/pr19807-1.c 37a20253a6b6ae34269390b00efedddf gcc/testsuite/c-c++-common/pr20000.c *************** ab8ceba35b76e5122ef1d15e5a6d31ba gcc/te *** 8736,8741 **** --- 8754,8761 ---- e0a81999221bcfcb3f37370ca022637f gcc/testsuite/c-c++-common/pr72747-2.c aa9180dd8f8db71eedda52c54d5dcfe1 gcc/testsuite/c-c++-common/pr77624-1.c 6d950c28409779b8786e764dbfa04ed7 gcc/testsuite/c-c++-common/pr77624-2.c + 6c6ebe9e94d2f6d6f9e318d4247ea33a gcc/testsuite/c-c++-common/pr79428-3.c + ce91ea7c46f421a0b712ff52ee4f9985 gcc/testsuite/c-c++-common/pr79641.c b0ba836310044e7b419ef679f0b48d6f gcc/testsuite/c-c++-common/raw-string-1.c 554e7071d2525351de28445762633866 gcc/testsuite/c-c++-common/raw-string-10.c fc54e7227094f307fa566b3a8cd0ba9a gcc/testsuite/c-c++-common/raw-string-11.c *************** f7ac21b5467fdafd31e4d63c13bba697 gcc/te *** 8917,8922 **** --- 8937,8943 ---- 8a79b5ac2324b237d4b97f40d8caef20 gcc/testsuite/c-c++-common/ubsan/bounds-11.c c0cea811b60785fdbeb5a8c17cbfe97d gcc/testsuite/c-c++-common/ubsan/bounds-12.c e41a9c9640280bfabdc970ff41f1e444 gcc/testsuite/c-c++-common/ubsan/bounds-13.c + cd3471a668bc0c1cefbc4a040f2df388 gcc/testsuite/c-c++-common/ubsan/bounds-14.c 5ce7dbfd4301c9cde8b861eef45a151b gcc/testsuite/c-c++-common/ubsan/bounds-2.c e7f60e0642d24587e57ad55271053c36 gcc/testsuite/c-c++-common/ubsan/bounds-3.c 55d21c141077691618a0992441b77856 gcc/testsuite/c-c++-common/ubsan/bounds-4.c *************** ffc7c68789ff080a9c2dc0100772c9ea gcc/te *** 9024,9029 **** --- 9045,9051 ---- 9bd2c80828bcc0260a30db4f41b6dd8f gcc/testsuite/c-c++-common/ubsan/pr68142.c 233ec95eefe1d940a157245de1822945 gcc/testsuite/c-c++-common/ubsan/pr71512-1.c abaaaa855dd108b8d327718c2416ad01 gcc/testsuite/c-c++-common/ubsan/pr71512-2.c + c2f3b3be31f310c27528d1ee4cc38bb9 gcc/testsuite/c-c++-common/ubsan/pr80350.c dab28cca030f6a4bc8dd3c11ed677fff gcc/testsuite/c-c++-common/ubsan/recovery-1.c 5bb4d0c13ed60e4d8054523bc5e48304 gcc/testsuite/c-c++-common/ubsan/recovery-2.c aafe603ef0d928ea5f8241acd3077f5c gcc/testsuite/c-c++-common/ubsan/recovery-3.c *************** e556d95fc8d53f6631375ea8b85d3075 gcc/te *** 9037,9042 **** --- 9059,9065 ---- 82afee71f72fbf21412e2924f47ea4b8 gcc/testsuite/c-c++-common/ubsan/save-expr-3.c 6c0e99e114699e240db660fc574febe9 gcc/testsuite/c-c++-common/ubsan/save-expr-4.c 4a5186270de56b794677e64699b4db69 gcc/testsuite/c-c++-common/ubsan/shift-1.c + edd4fcff5550bbc876ceb98d62be3b21 gcc/testsuite/c-c++-common/ubsan/shift-10.c a18c6c5812c92fe7ae6c0d748ca4d92b gcc/testsuite/c-c++-common/ubsan/shift-2.c 0b6048e0bae5c56479d7ad8db84f1080 gcc/testsuite/c-c++-common/ubsan/shift-3.c 0583cbb89a0ca9b82aa6f779422b4f5e gcc/testsuite/c-c++-common/ubsan/shift-4.c *************** fe56cd912c0f058bb4436bed7ee10cea gcc/te *** 9260,9265 **** --- 9283,9289 ---- a63cefdf2683d4aa005634e3368984ba gcc/testsuite/g++.dg/abi/pr39188-3.h afd0ff2e30705970415e4aa6ca6e1468 gcc/testsuite/g++.dg/abi/pr39188-3a.C 98c00465484f65e4b1d1c30fbbb31e23 gcc/testsuite/g++.dg/abi/pr39188-3b.C + f490a138e96fa6bdd22efe9404004222 gcc/testsuite/g++.dg/abi/pr77728-1.C 4a1543932abd77ea1cfba28eecdeeef4 gcc/testsuite/g++.dg/abi/pragma-pack1.C 758c2fd81af2f42665b56b5d21b15e9f gcc/testsuite/g++.dg/abi/regparm1.C d90943e976dded1f4182aeb500d1f2c7 gcc/testsuite/g++.dg/abi/rtti1.C *************** e5fa8115f1c449f56d10e259c799b933 gcc/te *** 9831,9836 **** --- 9855,9861 ---- 72736d15450a5e2c6eff6d212a1c62ea gcc/testsuite/g++.dg/cpp0x/alias-decl-51.C ff3cdd35e9b74954a4247257ac643335 gcc/testsuite/g++.dg/cpp0x/alias-decl-52.C aeae7dcc61eb495ebb095caa00a5f429 gcc/testsuite/g++.dg/cpp0x/alias-decl-55.C + 445849a996785ae535a6c30f3b9a98fa gcc/testsuite/g++.dg/cpp0x/alias-decl-59.C a16b0e12dce894e9bc097e3fbad8787d gcc/testsuite/g++.dg/cpp0x/alias-decl-6.C 816dbf372a71890f9515376534ec312b gcc/testsuite/g++.dg/cpp0x/alias-decl-7.C 77aa48fcd9f9b9ffab08fa7ebc5d52e2 gcc/testsuite/g++.dg/cpp0x/alias-decl-8.C *************** ef369c9d8dbd4b3ba5c764f92fc53a46 gcc/te *** 9843,9848 **** --- 9868,9874 ---- 830a80101d211b99c4fce4c743aa6771 gcc/testsuite/g++.dg/cpp0x/alias-decl-enum-1.C 42802675fdf183e36c26b59ce2188fbd gcc/testsuite/g++.dg/cpp0x/alias-decl-pmf1.C 3160c52a8ac131b03192a1bc86ef7a35 gcc/testsuite/g++.dg/cpp0x/alignas1.C + cda964826837ac50113537351c4b8f2b gcc/testsuite/g++.dg/cpp0x/alignas11.C f1354435b9e53f5c5d923994edebb49f gcc/testsuite/g++.dg/cpp0x/alignas2.C f441b8f61e57b375afffc578a0ab410b gcc/testsuite/g++.dg/cpp0x/alignas3.C 842d4bc39d9ce4591190d72ce324a6a8 gcc/testsuite/g++.dg/cpp0x/alignas4.C *************** cbe0ba147a1df371f25c8ab8623476ef gcc/te *** 10383,10388 **** --- 10409,10415 ---- a5a365073fed8c5bd9263eef7df7b899 gcc/testsuite/g++.dg/cpp0x/deleted10.C 237265837e45688c4ab0305223c90d74 gcc/testsuite/g++.dg/cpp0x/deleted11.C 2983561177357253ebbb1f5c1fa5f8e4 gcc/testsuite/g++.dg/cpp0x/deleted12.C + 2d9bfdbc6407d55b8911aeaa44476c9f gcc/testsuite/g++.dg/cpp0x/deleted13.C d677b798550124a88e6345300f30828a gcc/testsuite/g++.dg/cpp0x/deleted2.C a9129f4cd34b93dbe745e3849ea1c38a gcc/testsuite/g++.dg/cpp0x/deleted3.C d6f65d86ea217a2efd4c31ebedc9c9db gcc/testsuite/g++.dg/cpp0x/deleted4.C *************** d3df2168b01c7df3891e31a076616e58 gcc/te *** 10576,10581 **** --- 10603,10609 ---- 69ee4b066e7054d7163a882761fcc7c7 gcc/testsuite/g++.dg/cpp0x/inh-ctor2.C 1e245cab6f0228068139bd22ddc79d66 gcc/testsuite/g++.dg/cpp0x/inh-ctor20.C ae53be78261501cbb9b25c7630f78cb5 gcc/testsuite/g++.dg/cpp0x/inh-ctor21.C + 3dd2cbce9f770ed128820376bcfc0ea3 gcc/testsuite/g++.dg/cpp0x/inh-ctor27.C 6a7a4b5897b83f2f6ebdd08eb567d152 gcc/testsuite/g++.dg/cpp0x/inh-ctor3.C 071eafda7f7d2d4bff42921fbd048a45 gcc/testsuite/g++.dg/cpp0x/inh-ctor4.C fda4f7d4f4b57c79d7734d634ae9041f gcc/testsuite/g++.dg/cpp0x/inh-ctor5.C *************** e441f7a8895e83d53f40d4ca21836ee2 gcc/te *** 10814,10819 **** --- 10842,10848 ---- 404693fec002449e01019ebc66a762f7 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-nested3.C b4ee4e860077c15b5f446a344ee80eb1 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-nested4.C 61ec239111bc86f289d1bee48e0c8003 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-nested5.C + 5fbb17b854d8fd1a54b7633e8347d839 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-nested6.C 473ec19f81d0003cf47717bbb9c67549 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-non-const.C fc0cbc487d6a1b6d02de8cbeb0f06f70 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-nop.C 45c8811455b2ff67d0b834d61c336d54 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-ns-scope.C *************** f9a95403a108b26b2de03038d43da14f gcc/te *** 10976,10981 **** --- 11005,11011 ---- 91a43b77eb14e3bcc8e25996943b3d03 gcc/testsuite/g++.dg/cpp0x/nsdmi10.C ef00b2c2beb9680889aec5881ac6e71e gcc/testsuite/g++.dg/cpp0x/nsdmi11.C 73f3d24b7fde9a7bfe33075395c0b3db gcc/testsuite/g++.dg/cpp0x/nsdmi12.C + efbe4509f010d6478960eb76bc669dd0 gcc/testsuite/g++.dg/cpp0x/nsdmi13.C 6441ebb320eb7cce0916b770b17635d3 gcc/testsuite/g++.dg/cpp0x/nsdmi2.C b49a256b7d52d077f75204867f7c282e gcc/testsuite/g++.dg/cpp0x/nsdmi3.C 5f65bb87e42c6ccb9b5a2788ce979bcf gcc/testsuite/g++.dg/cpp0x/nsdmi4.C *************** d584417478a609ab589447aa7e173812 gcc/te *** 11148,11158 **** --- 11178,11193 ---- 4ca96cbe7b69845eba2cf016007957a4 gcc/testsuite/g++.dg/cpp0x/pr70528.C cf9cf154014255688dedeb39cfe8e73b gcc/testsuite/g++.dg/cpp0x/pr70869.C c69896dc2fac3243e492d5e8acf8d0b8 gcc/testsuite/g++.dg/cpp0x/pr71054.C + 8cd9ca1dc7d8e3ad63d64b194e06d6ca gcc/testsuite/g++.dg/cpp0x/pr71182.C bf28b34cff6af29465046bf24b9bff82 gcc/testsuite/g++.dg/cpp0x/pr71739.C 7f91317e6447b60e485c696d632a9ae9 gcc/testsuite/g++.dg/cpp0x/pr71979.C 26ea08e9b4f6ddd2f8b2d8c726065478 gcc/testsuite/g++.dg/cpp0x/pr77907.C + 785e97f705ee538cb0d469f646b74caa gcc/testsuite/g++.dg/cpp0x/pr78341.C 7f20ecc1d0425b01c320b4d638d5dc4c gcc/testsuite/g++.dg/cpp0x/pr78649.C + fc11ff78853c75dd1793494cd38f1023 gcc/testsuite/g++.dg/cpp0x/pr78693.C a32de62864222434c111c70941412a14 gcc/testsuite/g++.dg/cpp0x/pr78701.C + f20119fcb0360fcb840fc98cdd160056 gcc/testsuite/g++.dg/cpp0x/pr79296.C + 66a521d2e849b0d860d730b03168d8af gcc/testsuite/g++.dg/cpp0x/pr80091.C 53428f69a6d0153074c9b06ee9fbe9e7 gcc/testsuite/g++.dg/cpp0x/ptrmem-cst-arg1.C 6e8e648c26d9bf237cc152180e88c2c2 gcc/testsuite/g++.dg/cpp0x/range-for1.C 5c7a98d8ca2f0f427c081bf6902aa831 gcc/testsuite/g++.dg/cpp0x/range-for10.C *************** a1ffe33575e516147d04bf615cd38349 gcc/te *** 11179,11184 **** --- 11214,11222 ---- ba9e5975a5058b94945c4d18bb19b344 gcc/testsuite/g++.dg/cpp0x/range-for3.C 4b0681c49d2c294d37da68e8ae679248 gcc/testsuite/g++.dg/cpp0x/range-for30.C 2e0b59cf549f3ada1e2c24f0828fd564 gcc/testsuite/g++.dg/cpp0x/range-for31.C + cac4db523ff451f6ffc7f57da72a4164 gcc/testsuite/g++.dg/cpp0x/range-for32.C + c0e5ee89c913d75b3174c2833d03f665 gcc/testsuite/g++.dg/cpp0x/range-for33.C + f6fdcf88436a7c2de904550e31de7cea gcc/testsuite/g++.dg/cpp0x/range-for34.C cf3faabae812bd6f8ade13f3c1d36871 gcc/testsuite/g++.dg/cpp0x/range-for4.C 9d70da20463079b62be580867a3e6601 gcc/testsuite/g++.dg/cpp0x/range-for5.C bf09a13cfe61445a898ea383c44bc795 gcc/testsuite/g++.dg/cpp0x/range-for6.C *************** b8b4ef414480ac8cc610a96093ab666f gcc/te *** 11469,11474 **** --- 11507,11513 ---- afebb5cb3a55d32fcecd85587b287bd9 gcc/testsuite/g++.dg/cpp0x/variadic-tuple.C eae406793547757d01528d5680162682 gcc/testsuite/g++.dg/cpp0x/variadic-tuple2.C 9cf2b1705ed83cc74a8a4b9eb2703186 gcc/testsuite/g++.dg/cpp0x/variadic-unify-2.C + 14d049c47cd861f03247bae7077f7a4a gcc/testsuite/g++.dg/cpp0x/variadic-unify-3.C 72f7c5714fa45fa32619b387e484e88b gcc/testsuite/g++.dg/cpp0x/variadic-unify.C 30d5d2ca1010b71be91917305590fe27 gcc/testsuite/g++.dg/cpp0x/variadic-unresolved.C edf9e45ed1a17b392fa9f15f8a7cce75 gcc/testsuite/g++.dg/cpp0x/variadic-value1.C *************** c4e86a95bc6b38f69a4a30b1b1cf1e4e gcc/te *** 11715,11720 **** --- 11754,11760 ---- 51f8ba9d1f0f20256658a6298e611261 gcc/testsuite/g++.dg/cpp1y/auto-fn30.C 2166d3092f2a511f64d91ad91795c1ac gcc/testsuite/g++.dg/cpp1y/auto-fn31.C f475a3e97ef5d08fb361f8070d183611 gcc/testsuite/g++.dg/cpp1y/auto-fn32.C + be0d5f10eb69b210aef36d86a139ae03 gcc/testsuite/g++.dg/cpp1y/auto-fn36.C a87641c12e6bf65af1e8d592973cba76 gcc/testsuite/g++.dg/cpp1y/auto-fn4.C eaab8c47716923537d6580ede6fbe3ae gcc/testsuite/g++.dg/cpp1y/auto-fn5.C 3861eed28323480e4913eea3d9c0ec00 gcc/testsuite/g++.dg/cpp1y/auto-fn6.C *************** d67958b896eb1dae6f8862fd59b01c62 gcc/te *** 11726,11731 **** --- 11766,11774 ---- f3e3d98fcbe616df26f26eb779c66c1f gcc/testsuite/g++.dg/cpp1y/complex_literals.h ff3e876f73b9e207bc74cebb8f681b24 gcc/testsuite/g++.dg/cpp1y/constexpr-77467.C 3703fe85dbf973a8e792adfb4de7f0fc gcc/testsuite/g++.dg/cpp1y/constexpr-77553.C + cfc19422b140639fdc2dc2bf7ca295b6 gcc/testsuite/g++.dg/cpp1y/constexpr-79639.C + 87e6acf3f9570693090bc9744174253b gcc/testsuite/g++.dg/cpp1y/constexpr-79681-1.C + c31b3bbd5d5198b87b168be79f7471eb gcc/testsuite/g++.dg/cpp1y/constexpr-79681-2.C 8ca7fb9e44e526f77542eaa59593c544 gcc/testsuite/g++.dg/cpp1y/constexpr-array1.C 10c765e5671de39fd3d751b2e3a5408b gcc/testsuite/g++.dg/cpp1y/constexpr-array2.C 192478e53d1e7dc7ab67b7b22a9678c1 gcc/testsuite/g++.dg/cpp1y/constexpr-array3.C *************** ce3d96795da2089956df925a1a9c9815 gcc/te *** 11739,11744 **** --- 11782,11788 ---- e6815ab618d6af99025ddeacf6ab0545 gcc/testsuite/g++.dg/cpp1y/constexpr-copy3.C 9b6ce1c2202c1ce9ea82fda5f060499b gcc/testsuite/g++.dg/cpp1y/constexpr-empty1.C 9e871814c326197a59b4ae1738313788 gcc/testsuite/g++.dg/cpp1y/constexpr-empty2.C + d4fc72d059e047077b1d6033d4c13026 gcc/testsuite/g++.dg/cpp1y/constexpr-empty3.C 995873768089d805df939c03d2be8b1c gcc/testsuite/g++.dg/cpp1y/constexpr-hana1.C f4f6c3d1cdaf2aa67bfa2b8c851853d5 gcc/testsuite/g++.dg/cpp1y/constexpr-incr1.C 3e9dd485a2a6d99132c92a6d04b96ee9 gcc/testsuite/g++.dg/cpp1y/constexpr-initlist1.C *************** f705c3231fd3394bbd8e1f6d3c18f870 gcc/te *** 11763,11771 **** 469cd1fc4d897d90592a00ce78be9201 gcc/testsuite/g++.dg/cpp1y/constexpr-switch2.C c1e1359ff4463d37602a3a97e87c775f gcc/testsuite/g++.dg/cpp1y/constexpr-switch3.C 2cf598a0cfa5187e173eb042b77aa4a7 gcc/testsuite/g++.dg/cpp1y/constexpr-switch4.C ! 04e1d26f77c1f444a58d9c3311978dab gcc/testsuite/g++.dg/cpp1y/constexpr-throw.C 0338099a8b7545e92dbe09d98b8c671d gcc/testsuite/g++.dg/cpp1y/constexpr-type-def-compound1.C f869695e4081f7115b13ec5e36fddb37 gcc/testsuite/g++.dg/cpp1y/constexpr-type-def1.C d05362a8ea33190463d383e8c676b147 gcc/testsuite/g++.dg/cpp1y/constexpr-void1.C f9177d17a8e7ca1cf52d2e3f3738490b gcc/testsuite/g++.dg/cpp1y/constexpr-void2.C 83f6314e632d195e61997bd04ab32847 gcc/testsuite/g++.dg/cpp1y/context-conv1.C --- 11807,11816 ---- 469cd1fc4d897d90592a00ce78be9201 gcc/testsuite/g++.dg/cpp1y/constexpr-switch2.C c1e1359ff4463d37602a3a97e87c775f gcc/testsuite/g++.dg/cpp1y/constexpr-switch3.C 2cf598a0cfa5187e173eb042b77aa4a7 gcc/testsuite/g++.dg/cpp1y/constexpr-switch4.C ! fc6eae1310169e00093e41f9d7bf977f gcc/testsuite/g++.dg/cpp1y/constexpr-throw.C 0338099a8b7545e92dbe09d98b8c671d gcc/testsuite/g++.dg/cpp1y/constexpr-type-def-compound1.C f869695e4081f7115b13ec5e36fddb37 gcc/testsuite/g++.dg/cpp1y/constexpr-type-def1.C + 165186eea0291986cb116c6366c5d09c gcc/testsuite/g++.dg/cpp1y/constexpr-union1.C d05362a8ea33190463d383e8c676b147 gcc/testsuite/g++.dg/cpp1y/constexpr-void1.C f9177d17a8e7ca1cf52d2e3f3738490b gcc/testsuite/g++.dg/cpp1y/constexpr-void2.C 83f6314e632d195e61997bd04ab32847 gcc/testsuite/g++.dg/cpp1y/context-conv1.C *************** a5fcad1d0708a6218c6fe69c1871df02 gcc/te *** 11792,11797 **** --- 11837,11843 ---- 18a2431f49a5d003b8c4af0ee1ee26fb gcc/testsuite/g++.dg/cpp1y/lambda-generic-cfun.C 043e19917f87f2b2acd754fc6d7db469 gcc/testsuite/g++.dg/cpp1y/lambda-generic-const1.C 565bd59fb2dca8cbcfbfa5b7e1e94368 gcc/testsuite/g++.dg/cpp1y/lambda-generic-const2.C + c1704c3068b9b801f6fca80634fa3d1c gcc/testsuite/g++.dg/cpp1y/lambda-generic-const3.C 2e80b291e01a2cfa45ff49e595eefeb5 gcc/testsuite/g++.dg/cpp1y/lambda-generic-conv1.C 4826d92e5c4d99fa506ff2e846ff01a4 gcc/testsuite/g++.dg/cpp1y/lambda-generic-conv2.C 78cdb2dc3c8d671d96c375fa61f96dc5 gcc/testsuite/g++.dg/cpp1y/lambda-generic-conv3.C *************** c6352418315616cd37a733490bfa2baf gcc/te *** 11886,11891 **** --- 11932,11940 ---- e870b2124044ac1320cf992f181773a4 gcc/testsuite/g++.dg/cpp1y/pr60626.C ccdf243ad72b9b0a028429d373468fef gcc/testsuite/g++.dg/cpp1y/pr60627.C 57a0dc24fb99fbd479aab82399935d96 gcc/testsuite/g++.dg/cpp1y/pr60943.C + 36ea8d632059da318eba95db916a7d67 gcc/testsuite/g++.dg/cpp1y/pr61636-1.C + 9b956ed4d6ed5d2856ccf34af41742c3 gcc/testsuite/g++.dg/cpp1y/pr61636-2.C + 8b18feb5bcdddcab93132675568377e3 gcc/testsuite/g++.dg/cpp1y/pr61636-3.C 80145d35968f0308732f07fb457345f2 gcc/testsuite/g++.dg/cpp1y/pr63996.C 2bf768dd7e19ea1f0872089c05d29aeb gcc/testsuite/g++.dg/cpp1y/pr64626-1.C b82fb5e4a473d7355f2d603a5f9c0809 gcc/testsuite/g++.dg/cpp1y/pr64626-2.C *************** c76033bace37fe8344dd999290834128 gcc/te *** 11983,11988 **** --- 12032,12038 ---- 87e28b8d91cdca54118621d517c2f9aa gcc/testsuite/g++.dg/cpp1z/abbrev2.C 68f716938002307e7dcda9d5dc357f14 gcc/testsuite/g++.dg/cpp1z/attributes-enum-1.C c0f76eabaeee19f702ca129c32355700 gcc/testsuite/g++.dg/cpp1z/attributes-enum-1a.C + b168fea8fd96c7b9e04f74cdd04de2a4 gcc/testsuite/g++.dg/cpp1z/constexpr-lambda15.C 98b1106ed209b91da77baabfe32a0221 gcc/testsuite/g++.dg/cpp1z/cplusplus.C b78ef62cdf62c62127e6ef6b082f3bbf gcc/testsuite/g++.dg/cpp1z/feat-cxx1z.C f6bf72fc22cf2e0b2625b0da029798a4 gcc/testsuite/g++.dg/cpp1z/fold-ice1.C *************** d108472b30fd8a2ccb535bb57ff25d0a gcc/te *** 12431,12436 **** --- 12481,12488 ---- 39041dce87ae406151a5cca310cd2ce4 gcc/testsuite/g++.dg/expr/ptrmem6.C 014c6e35722352b75d65d090cb999dd7 gcc/testsuite/g++.dg/expr/ptrmem6a.C 9b52a54a6bb9359f4cd984333c3b7ee6 gcc/testsuite/g++.dg/expr/ptrmem7.C + ff3a5759912b7f7418063e83588430a4 gcc/testsuite/g++.dg/expr/ptrmem8.C + c5dab48b8ba1e4045416f5a602e8b9a4 gcc/testsuite/g++.dg/expr/ptrmem9.C cfe9ff3c65c17e6ab2653583e3fd9e3c gcc/testsuite/g++.dg/expr/return1.C 0aff78a2cc7b554bd2a283f999880d26 gcc/testsuite/g++.dg/expr/sizeof1.C 1714277b99f69dbeee24b2fdf5626d32 gcc/testsuite/g++.dg/expr/sizeof2.C *************** ad9b04984e82c2e0e1fb2025de8f9a23 gcc/te *** 12666,12671 **** --- 12718,12724 ---- ab6acb4a7c8c1d0b3e7717da4ac42983 gcc/testsuite/g++.dg/ext/complit12.C 1ef2d5904216cc610d5c5dde143f79ac gcc/testsuite/g++.dg/ext/complit13.C 07cb245f4432f072b7263e83c675d2de gcc/testsuite/g++.dg/ext/complit14.C + b1b3d79f809712cfb571a36f0d6c8914 gcc/testsuite/g++.dg/ext/complit15.C 7350965e2763a3a6e1d4346deaa1e94e gcc/testsuite/g++.dg/ext/complit2.C 7c0cfd2335d61954c46222aa7517e055 gcc/testsuite/g++.dg/ext/complit3.C f2a3354acae823d1855d3f7820f78229 gcc/testsuite/g++.dg/ext/complit4.C *************** ebd21aaf9b21a61e56a1bcb1ace4b3c0 gcc/te *** 12722,12728 **** c0dc41d4a72302e0ac9ef29725c83d30 gcc/testsuite/g++.dg/ext/flexary1.C 4ce1c3c4d1695d0543f90340acfaa092 gcc/testsuite/g++.dg/ext/flexary10.C 0a9a0f2fb13b4a14f889ff0cddb53264 gcc/testsuite/g++.dg/ext/flexary11.C ! daa1aa9063032e4c5155d7341659f6f6 gcc/testsuite/g++.dg/ext/flexary12.C 53628223a07c6bbfb1cd7aef3f2b93cf gcc/testsuite/g++.dg/ext/flexary13.C c4a658a25ef8a25aeef375a3ce711fa2 gcc/testsuite/g++.dg/ext/flexary14.C aaba8fe44d3e6fec2f01feeb83885ba8 gcc/testsuite/g++.dg/ext/flexary15.C --- 12775,12781 ---- c0dc41d4a72302e0ac9ef29725c83d30 gcc/testsuite/g++.dg/ext/flexary1.C 4ce1c3c4d1695d0543f90340acfaa092 gcc/testsuite/g++.dg/ext/flexary10.C 0a9a0f2fb13b4a14f889ff0cddb53264 gcc/testsuite/g++.dg/ext/flexary11.C ! d99f2c5485b988981ae08bf0ab740d1b gcc/testsuite/g++.dg/ext/flexary12.C 53628223a07c6bbfb1cd7aef3f2b93cf gcc/testsuite/g++.dg/ext/flexary13.C c4a658a25ef8a25aeef375a3ce711fa2 gcc/testsuite/g++.dg/ext/flexary14.C aaba8fe44d3e6fec2f01feeb83885ba8 gcc/testsuite/g++.dg/ext/flexary15.C *************** aaba8fe44d3e6fec2f01feeb83885ba8 gcc/te *** 12730,12735 **** --- 12783,12791 ---- b97898a82d442beda87456e35688b856 gcc/testsuite/g++.dg/ext/flexary18.C 82265f1aad7d680fd972d1eddd67d3a9 gcc/testsuite/g++.dg/ext/flexary19.C fa0fdbfe242e37c8962c867f656e7e36 gcc/testsuite/g++.dg/ext/flexary2.C + f22af1474252d514ac0a12998e8af04c gcc/testsuite/g++.dg/ext/flexary20.C + 76f921b3421c6306d60e63d81bf695f4 gcc/testsuite/g++.dg/ext/flexary21.C + 799928c572de3a0a1d8c1318932df135 gcc/testsuite/g++.dg/ext/flexary24.C 21926590c31816347bbb7ba438127f63 gcc/testsuite/g++.dg/ext/flexary3.C 3d3772048887cc532cac316c5dfc3727 gcc/testsuite/g++.dg/ext/flexary4.C 68d60f0ca40a2d83ca7d64839921f352 gcc/testsuite/g++.dg/ext/flexary5.C *************** f2cf0baaaf489aa15f22210e07d052d1 gcc/te *** 12785,12790 **** --- 12841,12847 ---- 61fa88a10a461afa5233ba52ee25455d gcc/testsuite/g++.dg/ext/int128-2.h 8313f3d030293501382bb11536a8919a gcc/testsuite/g++.dg/ext/int128-3.C 3b33306d69b3ca18d4baf8c0846a03a3 gcc/testsuite/g++.dg/ext/int128-4.C + 754d9cd2dfd66632200e26d330e6b4a6 gcc/testsuite/g++.dg/ext/int128-5.C 3a16bb49d1e751989bc6c5980e68cc41 gcc/testsuite/g++.dg/ext/interface1.C a6025f300298ca27e5d4454172592895 gcc/testsuite/g++.dg/ext/interface1.h 0530572db926ff489aea49718a5eabe8 gcc/testsuite/g++.dg/ext/interface1a.cc *************** e7267f3b0ef839e4a2d835556d472a34 gcc/te *** 12871,12877 **** 0b7e6be63f874371a065af141e94dc40 gcc/testsuite/g++.dg/ext/mv5.C 5fa5e6eec310c2baca6e675f51db6f5b gcc/testsuite/g++.dg/ext/mv6.C d7e6a6acfdeef8fa4231626fa3e68f99 gcc/testsuite/g++.dg/ext/mv7.C ! 71756d5a370200272e4677b59eccf9c5 gcc/testsuite/g++.dg/ext/mv8.C 7610da3ac7479053e5453edaa297546d gcc/testsuite/g++.dg/ext/mv9.C d55fd7b81ee99b5c87c27d2c23053a32 gcc/testsuite/g++.dg/ext/mvc1.C fb55d0e97756a33733f9bed9c07f8d0c gcc/testsuite/g++.dg/ext/mvc2.C --- 12928,12934 ---- 0b7e6be63f874371a065af141e94dc40 gcc/testsuite/g++.dg/ext/mv5.C 5fa5e6eec310c2baca6e675f51db6f5b gcc/testsuite/g++.dg/ext/mv6.C d7e6a6acfdeef8fa4231626fa3e68f99 gcc/testsuite/g++.dg/ext/mv7.C ! fde70aca439cf147f99652ebf4e2e324 gcc/testsuite/g++.dg/ext/mv8.C 7610da3ac7479053e5453edaa297546d gcc/testsuite/g++.dg/ext/mv9.C d55fd7b81ee99b5c87c27d2c23053a32 gcc/testsuite/g++.dg/ext/mvc1.C fb55d0e97756a33733f9bed9c07f8d0c gcc/testsuite/g++.dg/ext/mvc2.C *************** da9f4d40914a62f10cfc08d681f84fe6 gcc/te *** 12912,12917 **** --- 12969,12975 ---- fa1bb59fa29c67300169c1e22d329d50 gcc/testsuite/g++.dg/ext/pr69145-2.h 55064040c04f03766a14346d8b726048 gcc/testsuite/g++.dg/ext/pr70290.C f59cca37bcf6bf005672f72a4f1ab0c0 gcc/testsuite/g++.dg/ext/pr70571.C + e7effb51effd21039f6a2279ef9eceb0 gcc/testsuite/g++.dg/ext/pr80363.C ad117686eb16e680b29f2f5e45ebe0df gcc/testsuite/g++.dg/ext/pragmaweak1.C ae2794e104309a224e228d70e4cede48 gcc/testsuite/g++.dg/ext/pretty1.C faa8333681bedde3ba84daa60ec26ff8 gcc/testsuite/g++.dg/ext/pretty2.C *************** ac4d6ed4fa7dd3fbe3400c186a7c46d8 gcc/te *** 13348,13353 **** --- 13406,13416 ---- 1c935120e3c1e7d165ea068f57519a6e gcc/testsuite/g++.dg/gomp/pr67523.C 1e46e97dc4fca9257e078353e30f0add gcc/testsuite/g++.dg/gomp/pr71910.C 79e222486ea33d87026b4ecac4bb3593 gcc/testsuite/g++.dg/gomp/pr71941.C + b818df42e2e83be27f8843cc160f0681 gcc/testsuite/g++.dg/gomp/pr79429.C + 82b6406eb003ee9e559f588951fd7b03 gcc/testsuite/g++.dg/gomp/pr79664.C + 61f6175348fda4d4917305d233417a28 gcc/testsuite/g++.dg/gomp/pr80141.C + ba547a4dc52e5fa57b7cf7b21dfac263 gcc/testsuite/g++.dg/gomp/pr81011.C + 002e68c629105684ed6e09f1c3c9f806 gcc/testsuite/g++.dg/gomp/pr81154.C d2c2484d4d1236326efc32a01fddaa03 gcc/testsuite/g++.dg/gomp/predetermined-1.C edac71d2b358ecd6e646fece69c5426d gcc/testsuite/g++.dg/gomp/private-1.C d447246d410ae61ed9f733998e77b958 gcc/testsuite/g++.dg/gomp/reference-1.C *************** f44963a0cd9c1736b28dd8d5a81a4a94 gcc/te *** 13764,13769 **** --- 13827,13833 ---- 559e18af649d0930e65e2663f043609b gcc/testsuite/g++.dg/init/ref20.C 9a5faac941462bf7541a81ebb5668997 gcc/testsuite/g++.dg/init/ref21.C 61efc80d9af550cf9c4146845d48798a gcc/testsuite/g++.dg/init/ref22.C + ef89ae0c3b4a590a94233819b506141f gcc/testsuite/g++.dg/init/ref23.C e21984c05c21d067e3b20b37c68bec76 gcc/testsuite/g++.dg/init/ref3.C f21f65304dbc9a97b63efafb7bb1a6df gcc/testsuite/g++.dg/init/ref4.C e7fdc3fa73fd7411222a32862636796b gcc/testsuite/g++.dg/init/ref5.C *************** a99b2fdf38ca55ba2af4c250d0c71086 gcc/te *** 13980,13986 **** --- 14044,14055 ---- b80e7226dbed91bfd07d3de88797e3ca gcc/testsuite/g++.dg/ipa/pr69241-3.C f3021b0cdc3816bbbaf3ca610d163e73 gcc/testsuite/g++.dg/ipa/pr69241-4.C 015159cfa161eb427da1e671b39b4765 gcc/testsuite/g++.dg/ipa/pr69649.C + cad676606f867ff6d3c0c30870ad11a0 gcc/testsuite/g++.dg/ipa/pr71207.C + 3a8004c0e4c3f3ec713f3674c6464c08 gcc/testsuite/g++.dg/ipa/pr77333.C + d53e2610da5ee135ff2297e91a0715be gcc/testsuite/g++.dg/ipa/pr77905.C 0d66afc3b6be386c8e29a4e0bbb7485d gcc/testsuite/g++.dg/ipa/pr78188.C + c5be5b54243f6264bf84d49d4a16947c gcc/testsuite/g++.dg/ipa/pr79931.C + 89f95e75e402e5135147f26252be06e5 gcc/testsuite/g++.dg/ipa/pr80205.C 65b30ac9d2b3a2244e49849aaad7dd78 gcc/testsuite/g++.dg/ipa/remref-1.C d26e3f0899c708e0f4b2ec8427502236 gcc/testsuite/g++.dg/ipa/remref-2.C b4804485e0df8c8497236eb6966a8244 gcc/testsuite/g++.dg/ipa/type-inheritance-1.C *************** b16d2b44bfa0aeed86e99a04f412703d gcc/te *** 14123,14128 **** --- 14192,14198 ---- 2ddc73877ee8726480b98b6b881569b6 gcc/testsuite/g++.dg/lookup/pr21802.C 6133d93b9e3d1477d5f921d386c406a0 gcc/testsuite/g++.dg/lookup/pr6936.C 3717c2026453719d4d718f3e8061ba28 gcc/testsuite/g++.dg/lookup/pr70205.C + 64b272011bdda1340d422fdc53bc678a gcc/testsuite/g++.dg/lookup/pr79377.C 9fc063d780e4510399927cfe832e8770 gcc/testsuite/g++.dg/lookup/pretty1.C f30dda31dee159f3aebbbc269a5fd8e4 gcc/testsuite/g++.dg/lookup/ptrmem1.C bcba89d3ec64e8fc005f26cebc29ef75 gcc/testsuite/g++.dg/lookup/redecl1.C *************** d3e7b46b355042e3d34530ae665a29e7 gcc/te *** 14417,14427 **** 11b7d69cfefec9d26ec290efdce4cddc gcc/testsuite/g++.dg/lto/pr69133_0.C ef5a2536eb458f4c1bb26650ac8cf4bc gcc/testsuite/g++.dg/lto/pr69133_1.C c96eb51fa2b7024612260c2b5bf7e61e gcc/testsuite/g++.dg/lto/pr69137_0.C ! b537c2e342c32ce6d0b3c3c1f07c32ff gcc/testsuite/g++.dg/lto/pr69589_0.C 028ec5371a2f90aff6959986ad96b4a2 gcc/testsuite/g++.dg/lto/pr69589_1.C 6b7544922085b3acc5747d6df94b222d gcc/testsuite/g++.dg/lto/pr69729_0.C b972d1fd05b76ae528924efc5e87e1e0 gcc/testsuite/g++.dg/lto/pr78472_0.c e2b3ea5caae8976b182bb721752f096a gcc/testsuite/g++.dg/lto/pr78472_1.C 6232508298dd20a759cf64fffbca9f5e gcc/testsuite/g++.dg/lto/v1-plugin-api-not-supported_0.C 80450d00a25790eac61041efe3b30bc0 gcc/testsuite/g++.dg/opt/20050511-1.C 960bd912d3dccb44df0ecdebdfd45b44 gcc/testsuite/g++.dg/opt/alias1.C --- 14487,14498 ---- 11b7d69cfefec9d26ec290efdce4cddc gcc/testsuite/g++.dg/lto/pr69133_0.C ef5a2536eb458f4c1bb26650ac8cf4bc gcc/testsuite/g++.dg/lto/pr69133_1.C c96eb51fa2b7024612260c2b5bf7e61e gcc/testsuite/g++.dg/lto/pr69137_0.C ! a66ce15fb60d398a3305f31de3dd8a46 gcc/testsuite/g++.dg/lto/pr69589_0.C 028ec5371a2f90aff6959986ad96b4a2 gcc/testsuite/g++.dg/lto/pr69589_1.C 6b7544922085b3acc5747d6df94b222d gcc/testsuite/g++.dg/lto/pr69729_0.C b972d1fd05b76ae528924efc5e87e1e0 gcc/testsuite/g++.dg/lto/pr78472_0.c e2b3ea5caae8976b182bb721752f096a gcc/testsuite/g++.dg/lto/pr78472_1.C + cbabc80851a14f5ce9acf898d69e0c56 gcc/testsuite/g++.dg/lto/pr79050_0.C 6232508298dd20a759cf64fffbca9f5e gcc/testsuite/g++.dg/lto/v1-plugin-api-not-supported_0.C 80450d00a25790eac61041efe3b30bc0 gcc/testsuite/g++.dg/opt/20050511-1.C 960bd912d3dccb44df0ecdebdfd45b44 gcc/testsuite/g++.dg/opt/alias1.C *************** cd9d658bcc74632f8c5f64180e52c3e8 gcc/te *** 14439,14444 **** --- 14510,14517 ---- 15dd66151b129bfdbe9cd873521b3467 gcc/testsuite/g++.dg/opt/builtins1.C 658263688b08330a026e1ad24c8f9b8f gcc/testsuite/g++.dg/opt/builtins2.C def63acb8ef99a4c443fc492c744024e gcc/testsuite/g++.dg/opt/call1.C + 1eba3f96de4bd15ebff2723155f41e53 gcc/testsuite/g++.dg/opt/call2.C + 85b07614ef2e4e3618196014b1b6b6dc gcc/testsuite/g++.dg/opt/call3.C 0365760743a63e367398b52c1a1ac37e gcc/testsuite/g++.dg/opt/cfg1.C 2db7ebcb2c45714978fcb3cadb7cb570 gcc/testsuite/g++.dg/opt/cfg2.C edb10b502f24cdcc3e2d6bd03834f453 gcc/testsuite/g++.dg/opt/cfg3.C *************** e98c78fcaf089947f989361b38fdf935 gcc/te *** 14471,14476 **** --- 14544,14550 ---- 110fc27204a84af6a62744d613b30944 gcc/testsuite/g++.dg/opt/cse3.C da545b524f9533548787d2126af2b0ea gcc/testsuite/g++.dg/opt/declone1.C 50ee927cf6fe85c47d711d0cc9801ad4 gcc/testsuite/g++.dg/opt/declone2.C + b21a48a250ef7c7bf5c2d289c1d68c60 gcc/testsuite/g++.dg/opt/declone3.C 903860d0fe2a846a5f1ee14453b38348 gcc/testsuite/g++.dg/opt/delay-slot-1.C fc3765afbe4eece1e37074054bfbd3e4 gcc/testsuite/g++.dg/opt/devirt1.C 7cb068437fa856224557f1c6ec473a59 gcc/testsuite/g++.dg/opt/devirt2.C *************** f527f51fa4c8b92a4d9374e96752d73a gcc/te *** 14554,14559 **** --- 14628,14634 ---- 4ed264b192fadaa6f3076ca27b4fc086 gcc/testsuite/g++.dg/opt/nrv15.C e94377182a1dedb230f53db874897364 gcc/testsuite/g++.dg/opt/nrv16.C 3bf30be38f5aa46b2a1c3f22d55000d4 gcc/testsuite/g++.dg/opt/nrv17.C + 3a570f71e0d06b55d991f8cab4b017d2 gcc/testsuite/g++.dg/opt/nrv18.C 360692bdb55de35cb68717ceb6c51fd7 gcc/testsuite/g++.dg/opt/nrv2.C 42adcc800d5d2029a2b831e1453e8f32 gcc/testsuite/g++.dg/opt/nrv3.C b2773b15109a2fc43572a97edf29b236 gcc/testsuite/g++.dg/opt/nrv4.C *************** e8fd45f660a33add25be711bbf9a8aed gcc/te *** 14713,14718 **** --- 14788,14797 ---- ea8361ea831bc7d6110a725ab74d2721 gcc/testsuite/g++.dg/opt/pr71387.C a380c45913d5ec3d5feed82fd2ba5c78 gcc/testsuite/g++.dg/opt/pr71528.C 90bdbfd9313461944756a9e9f01ce788 gcc/testsuite/g++.dg/opt/pr7503-1.C + 4b62fdd883db12cb5eca8e85001a63b2 gcc/testsuite/g++.dg/opt/pr79267.C + 23fbbe3312a22eb4c300b6e8552085cc gcc/testsuite/g++.dg/opt/pr79396.C + 5def8381ca76e609f29f7eca86db0b17 gcc/testsuite/g++.dg/opt/pr80275.C + 3793c7fdebffcc14d6e627f6ab5cdb04 gcc/testsuite/g++.dg/opt/pr80385.C 1451eba24eea82cbd0c1ab87885c0f77 gcc/testsuite/g++.dg/opt/preinc1.C 0841088f825be785d32663d712ecf675 gcc/testsuite/g++.dg/opt/ptrintsum1.C 8ceccf2f02b3f64f372600e32148e146 gcc/testsuite/g++.dg/opt/ptrmem1.C *************** bc5371eb8e8dcf79efb0889828991560 gcc/te *** 14924,14929 **** --- 15003,15009 ---- 47195a1b7ad4c24c5ccc7cbf50e26bb0 gcc/testsuite/g++.dg/other/gc5.C 3ca5017faf45f39326ff4e30a1ec1ba8 gcc/testsuite/g++.dg/other/i386-1.C 9913a24914ce11f6a0606c70ed58cb96 gcc/testsuite/g++.dg/other/i386-10.C + 8925c3efd781e76570846cfd6f817fd2 gcc/testsuite/g++.dg/other/i386-11.C 833a1f08b1d3dc3293958ea625cbf54c gcc/testsuite/g++.dg/other/i386-2.C 1260328409c9e98b15e071178f779402 gcc/testsuite/g++.dg/other/i386-3.C a4ad4c2cb3c1448496351241a77aedb7 gcc/testsuite/g++.dg/other/i386-4.C *************** e01d22af2bf54a4df755dfb677defefb gcc/te *** 15081,15086 **** --- 15161,15167 ---- e78713a0179131f593c8dd8fb9214bc5 gcc/testsuite/g++.dg/overload/addr2.C 7237d5fda21efc2bec2c4dd99601723c gcc/testsuite/g++.dg/overload/ambig1.C ea3127f4b42d821f844905a93809eb92 gcc/testsuite/g++.dg/overload/ambig2.C + c654c01b17fc05917f1abb232a0a09ba gcc/testsuite/g++.dg/overload/ambig3.C fb106edf83320ef2682b57be415f13ba gcc/testsuite/g++.dg/overload/arg1.C 4491935dbfe94276c1739fb569f323e7 gcc/testsuite/g++.dg/overload/arg2.C 56dec1a852941c80fa219023fa4df5df gcc/testsuite/g++.dg/overload/arg3.C *************** a7c7523f78d6f162791c48963beb5abd gcc/te *** 15556,15561 **** --- 15637,15643 ---- 6a0269c4616a620b7a973566b20dc501 gcc/testsuite/g++.dg/parse/ptrmem4.C f52d554c8ba213f3b2dd46e6ec8cf1e3 gcc/testsuite/g++.dg/parse/ptrmem5.C 58b8f9b33890f80dd9050c24c55321aa gcc/testsuite/g++.dg/parse/ptrmem6.C + 0792cea6ff9bc1b92f2d4519f9278823 gcc/testsuite/g++.dg/parse/ptrmem7.C 83d63dd38efaf7bc7408deb85bde6d3d gcc/testsuite/g++.dg/parse/pure1.C ee6ac3b84366a978a8fd11d55b342fb7 gcc/testsuite/g++.dg/parse/qualified1.C 824f236b15bcc9ff8b13f7275ea14210 gcc/testsuite/g++.dg/parse/qualified2.C *************** e77af829a8368cadb2874c601ccda7ee gcc/te *** 15797,15807 **** --- 15879,15893 ---- b6486240b7f881b41363b5c5aed08fef gcc/testsuite/g++.dg/pr70590-2.C 78887d1698e74e4fca9c756431fc9a37 gcc/testsuite/g++.dg/pr70590.C 0b728dae13a5f48195e47018a83c4f35 gcc/testsuite/g++.dg/pr71184.C + 9c7076eebc1a097805724107700a7e60 gcc/testsuite/g++.dg/pr71294.C dd5b895f9e8e377b3fc861eecf9bdbf7 gcc/testsuite/g++.dg/pr71389.C bb847cc20ee8eeae077a40b58e2964fc gcc/testsuite/g++.dg/pr71624.C 5d11f2248bc8824c7b2c877cacdb859e gcc/testsuite/g++.dg/pr77427.C b17059f1a5aa7cc26b5b24bca90c15c3 gcc/testsuite/g++.dg/pr77550.C + ea5dbf59cf2609041141d1523d1f4409 gcc/testsuite/g++.dg/pr77812.C 7759fc7f6478af699ff865a66c157487 gcc/testsuite/g++.dg/pr78229.C + f66afb99493b92c63a8b1e5a2bd2ca5c gcc/testsuite/g++.dg/pr79761.C + bfc1d08789ff600f77190c59b402a8ec gcc/testsuite/g++.dg/pr79769.C d038107e5b87bb2651ccfef7fa33748a gcc/testsuite/g++.dg/predict-loop-exit-1.C b091c5510d946f61175720e0e6a70c8e gcc/testsuite/g++.dg/predict-loop-exit-2.C 89ad4872e69c75752e361c89ce72b02b gcc/testsuite/g++.dg/predict-loop-exit-3.C *************** b8d7ae2a709e06f2d49e19cfb00e77d3 gcc/te *** 15984,15989 **** --- 16070,16076 ---- 63a5e3d5f634ef4eb13aa4a9d62a8cd7 gcc/testsuite/g++.dg/template/assign1.C 2f3399aac63bff69580e94f66f716e0b gcc/testsuite/g++.dg/template/bitfield1.C fc503a6c4d63b92622d495b917629877 gcc/testsuite/g++.dg/template/bitfield2.C + 8a0fec8b2c65fed33977466ab46bb239 gcc/testsuite/g++.dg/template/bitfield3.C 479ce6c62d0ab31928edd3bcef27bd5c gcc/testsuite/g++.dg/template/builtin1.C 11d89720e8ea4a5f11553338c13ffab9 gcc/testsuite/g++.dg/template/call1.C e459df3ddd572b111e8694073c95e5b9 gcc/testsuite/g++.dg/template/call2.C *************** af2fdbfedc537d2eafde78a5b6afc170 gcc/te *** 16417,16422 **** --- 16504,16510 ---- 9783cba5cd0e48e50ecc5c42ed1dd282 gcc/testsuite/g++.dg/template/init-list.C f30fe425de51d4cb2ab5ff05b71d616a gcc/testsuite/g++.dg/template/init1.C 7c6a96d0550437ed561f8825ad2bc25e gcc/testsuite/g++.dg/template/init10.C + ac6c40bfa874333f4cc3f13523df5556 gcc/testsuite/g++.dg/template/init11.C 76f88c13708d18ca711ab8287d1caac9 gcc/testsuite/g++.dg/template/init2.C 64314d0aa5b3600547adc69b42ab8e3c gcc/testsuite/g++.dg/template/init3.C e920cba477d63f2866ea0710ce55a2ce gcc/testsuite/g++.dg/template/init4.C *************** a028161f345a592e44b9dd2c85780ba8 gcc/te *** 16517,16522 **** --- 16605,16611 ---- 742c5d9c3baa52309d717d8a67cb74e7 gcc/testsuite/g++.dg/template/memtmpl2.C 65b31c49b4254df68b854aca90f1aa6a gcc/testsuite/g++.dg/template/memtmpl3.C 7dfe03ecbca075fc2421fa72bbaedb9d gcc/testsuite/g++.dg/template/memtmpl4.C + 93c9e5870c9ff510b245da97899aef66 gcc/testsuite/g++.dg/template/memtmpl5.C 39db6def8c2ae0c295a9f6433ab39375 gcc/testsuite/g++.dg/template/nested1.C 1cf2f3c9d70e586c16763a10c08d9972 gcc/testsuite/g++.dg/template/nested2.C ef7f36711851ed451f4f826a28d9fadd gcc/testsuite/g++.dg/template/nested3.C *************** f14b5f3bfea1cc2e75ee2c2e9d2b1411 gcc/te *** 17520,17525 **** --- 17609,17615 ---- 428a33df2d4d37db0c2c6dc17621a08a gcc/testsuite/g++.dg/torture/pr68852.C 8e220539300aa7238affb1416477dc23 gcc/testsuite/g++.dg/torture/pr69053.C f51b8164c5b5a2cdbfd601ffb720ee4b gcc/testsuite/g++.dg/torture/pr69136.C + c5893de07a3c9606d42bebb72dff3c9e gcc/testsuite/g++.dg/torture/pr69264.C 7a1908e05947b451b17cc334319526f3 gcc/testsuite/g++.dg/torture/pr69355.C c3d28acfa8ec50c2dd014722262ee3ec gcc/testsuite/g++.dg/torture/pr69553.C 4399ef75994fb88845d72598f53764bd gcc/testsuite/g++.dg/torture/pr69851.C *************** ea126398515e20d945d8e298598ba010 gcc/te *** 17538,17543 **** --- 17628,17639 ---- 8fcdf2e7c90f945065444414bbe585b8 gcc/testsuite/g++.dg/torture/pr77919.C d10be217a5318f5a30d2b4af7af2a910 gcc/testsuite/g++.dg/torture/pr78189.C fff85caa269f4d672ff9fa1e8ed455a5 gcc/testsuite/g++.dg/torture/pr78224.C + e7b6b1b081a787e4e53586f0eb586432 gcc/testsuite/g++.dg/torture/pr79034.C + 5f30adb3e661ee47f5fadbbad3ee23c1 gcc/testsuite/g++.dg/torture/pr80075.C + 7ca5ee7afef7aee7488a8e0511740522 gcc/testsuite/g++.dg/torture/pr80129.C + b620e6b75af7923a29a7c8bddaca3f88 gcc/testsuite/g++.dg/torture/pr80171.C + 6f487a92823e54104daa5a6110dea6d2 gcc/testsuite/g++.dg/torture/pr80297.C + c8ab626b8e279f6073645f31a011c9e3 gcc/testsuite/g++.dg/torture/pr80334.C 389892c1f2e87d69449479d1b053c70c gcc/testsuite/g++.dg/torture/predcom-1.C d28910105d9c9253d94d70eacd5e19d4 gcc/testsuite/g++.dg/torture/pushpop_macro.C a1b47b9c3e69d79d1895ebc4fd11032b gcc/testsuite/g++.dg/torture/stackalign/check.h *************** a5c9a4af6ba744a4f85e714099331f92 gcc/te *** 17784,17789 **** --- 17880,17887 ---- 9b5a06caba92828c4750975de63a4e6b gcc/testsuite/g++.dg/ubsan/cxx11-shift-1.C 8bf53f1eaf75bd6c4e99ba27faa57511 gcc/testsuite/g++.dg/ubsan/cxx11-shift-2.C 0ca804f477b0c9e836b136a51c725c61 gcc/testsuite/g++.dg/ubsan/div-by-zero-1.C + 5f6adf84c6b049487918b36dbd808b87 gcc/testsuite/g++.dg/ubsan/div-by-zero-2.C + 25697e9d3c9eae68321ae8a6d93e1ddf gcc/testsuite/g++.dg/ubsan/div-by-zero-3.C 2e0109a65e2e2a01e3066892b1dd1e46 gcc/testsuite/g++.dg/ubsan/float-cast-overflow-bf.C c7511655f2d54310866c998269060e60 gcc/testsuite/g++.dg/ubsan/null-1.C 58dd5b6b76901b231167f7516ed08820 gcc/testsuite/g++.dg/ubsan/null-2.C *************** f4706f41ca654ceb8586f65654dc9bed gcc/te *** 17792,17797 **** --- 17890,17896 ---- e33cd115b2a5b1796134963715ca2601 gcc/testsuite/g++.dg/ubsan/null-5.C ebc4dd8d7b9c346d612ab748d0d8bda0 gcc/testsuite/g++.dg/ubsan/null-6.C 9a6263b0a0fc24a8d910d2b11d215637 gcc/testsuite/g++.dg/ubsan/null-7.C + fd3675e0e495ef66af8324e0f90aeacf gcc/testsuite/g++.dg/ubsan/null-8.C cefd426836ca36a8554ac0ad41946a30 gcc/testsuite/g++.dg/ubsan/object-size-1.C a654df71119821a4303cc9fe0501191b gcc/testsuite/g++.dg/ubsan/pr59250.C 420a6623146bb014dc1310134356d81f gcc/testsuite/g++.dg/ubsan/pr59306.C *************** af8fe8f8c142ba4099bf3fd97c7fb5f4 gcc/te *** 17823,17828 **** --- 17922,17929 ---- 1248cf51218287e0763e9bafddb6e95e gcc/testsuite/g++.dg/ubsan/pr70847.C 3ad68deac55fd26921bbcc306e06b206 gcc/testsuite/g++.dg/ubsan/pr71393.C a652d398f7e96504646f5368eec534a2 gcc/testsuite/g++.dg/ubsan/pr71512.C + e404ef8c87748bc2b0f6de9481e23e82 gcc/testsuite/g++.dg/ubsan/pr80349.C + 0c929d635990ffd3d04edd4192b03cc7 gcc/testsuite/g++.dg/ubsan/pr80973.C 23b03c04f7b3df05a2e3c261dbfbc91d gcc/testsuite/g++.dg/ubsan/return-1.C c729687b59770dc8f9e0991370cb1879 gcc/testsuite/g++.dg/ubsan/return-2.C 40257a16173db28137a5538f88bfea0e gcc/testsuite/g++.dg/ubsan/return-3.C *************** b9654cf3094250bbfcbf3eb545179ab8 gcc/te *** 17872,17878 **** 2f3816d0e6487939ea2be2cc9c3d9ce7 gcc/testsuite/g++.dg/vect/pr33835.cc 2e2b8dd8b937805b7fd60158c01a2598 gcc/testsuite/g++.dg/vect/pr33860.cc 66027332b6029868b87b2f0fbc78a8c2 gcc/testsuite/g++.dg/vect/pr33860a.cc ! 39efc5aa732010708319e650b57baabe gcc/testsuite/g++.dg/vect/pr36648.cc 773b9686259a86422856a8bcf252cee5 gcc/testsuite/g++.dg/vect/pr37143.C df0a8be418558aea938e13b5f6a34f0f gcc/testsuite/g++.dg/vect/pr37174.cc 89b57c9cc24aec3cfe0e8765cda781bf gcc/testsuite/g++.dg/vect/pr43771.cc --- 17973,17979 ---- 2f3816d0e6487939ea2be2cc9c3d9ce7 gcc/testsuite/g++.dg/vect/pr33835.cc 2e2b8dd8b937805b7fd60158c01a2598 gcc/testsuite/g++.dg/vect/pr33860.cc 66027332b6029868b87b2f0fbc78a8c2 gcc/testsuite/g++.dg/vect/pr33860a.cc ! f44ba1e0a0b1d852185b0c01da56d79c gcc/testsuite/g++.dg/vect/pr36648.cc 773b9686259a86422856a8bcf252cee5 gcc/testsuite/g++.dg/vect/pr37143.C df0a8be418558aea938e13b5f6a34f0f gcc/testsuite/g++.dg/vect/pr37174.cc 89b57c9cc24aec3cfe0e8765cda781bf gcc/testsuite/g++.dg/vect/pr43771.cc *************** dab35a90f2d5d7420299ca9413e0edb0 gcc/te *** 17988,17993 **** --- 18089,18095 ---- d8d1e3a45dd0a9c718cefdd08d54e264 gcc/testsuite/g++.dg/warn/Wnonnull-compare-8.C 88849261dc2753b60777f99076e31e3f gcc/testsuite/g++.dg/warn/Wnonnull1.C d38c5795330625342ab67317e9b6f464 gcc/testsuite/g++.dg/warn/Wnonnull2.C + d8522883128c1eb223545be773c44b16 gcc/testsuite/g++.dg/warn/Wnonnull3.C 5166536e9ccab5b393cea7c99c4e8d59 gcc/testsuite/g++.dg/warn/Wnull-conversion-1.C 7612268fc1d96d20aa8372be5730baee gcc/testsuite/g++.dg/warn/Wnull-conversion-2.C 8c56c916a791bfbd1ac25b63b43b766c gcc/testsuite/g++.dg/warn/Wnvdtor-2.C *************** c461709cb6d2b6b381cace809e2a380d gcc/te *** 17999,18004 **** --- 18101,18107 ---- c8cfeb1be8b9ab6b1a5bf044e67e73e2 gcc/testsuite/g++.dg/warn/Woverflow-3.C 3fb9d4575f0f00803eef196d3233d454 gcc/testsuite/g++.dg/warn/Woverflow-4.C 4d3b7ed38b5e078db7e76014e7eab321 gcc/testsuite/g++.dg/warn/Woverloaded-1.C + 5433407ca1a050560b08f45d03fdef67 gcc/testsuite/g++.dg/warn/Wpadded-1.C d1f22f759809f81b1b677be34f938b02 gcc/testsuite/g++.dg/warn/Wparentheses-1.C 8c1be4fe2c44958f9fdf70a20cd94fbe gcc/testsuite/g++.dg/warn/Wparentheses-10.C 3be49cd413635d5c6d8228545da74c15 gcc/testsuite/g++.dg/warn/Wparentheses-11.C *************** e7274165f26fc70eff73fddbd77e3811 gcc/te *** 18185,18190 **** --- 18288,18294 ---- 2a0d783bf451e934bdfdc826cdaf5930 gcc/testsuite/g++.dg/warn/Wunused-var-23.C 591077c761c72f687b4f25942b7e1640 gcc/testsuite/g++.dg/warn/Wunused-var-24.C 8f153046ad0f87a8a4eb0cb739ec384c gcc/testsuite/g++.dg/warn/Wunused-var-25.C + 715f4e85764653a44e74c60a6624ff13 gcc/testsuite/g++.dg/warn/Wunused-var-26.C dd0f2a1889a83658587b5f12c08c0c1c gcc/testsuite/g++.dg/warn/Wunused-var-3.C 62e5565091b4ee3f018515196f818bf3 gcc/testsuite/g++.dg/warn/Wunused-var-4.C d9191ea69f8ac18b1043d3d093b1f0d4 gcc/testsuite/g++.dg/warn/Wunused-var-5.C *************** aa70acbcac721d041f597b57b2ec733b gcc/te *** 18415,18421 **** 55753064a6448159c52e77b933d914df gcc/testsuite/g++.old-deja/g++.abi/vbase8-9.C 445d95964ba4a777690cdf56c7f1bcb7 gcc/testsuite/g++.old-deja/g++.abi/vmihint.C 305181b858f05a2e683bd7322f635642 gcc/testsuite/g++.old-deja/g++.abi/vtable.C ! 42d4bbe5c694e1f4bc9f0d996d822c52 gcc/testsuite/g++.old-deja/g++.abi/vtable2.C f43645b177185eca1785bb1bc24abcc7 gcc/testsuite/g++.old-deja/g++.abi/vtable3.h 335628c4bb776c7871e9beac4869bf89 gcc/testsuite/g++.old-deja/g++.abi/vtable3a.C 56ddac7d105a11ccda8236145c04d603 gcc/testsuite/g++.old-deja/g++.abi/vtable3b.C --- 18519,18525 ---- 55753064a6448159c52e77b933d914df gcc/testsuite/g++.old-deja/g++.abi/vbase8-9.C 445d95964ba4a777690cdf56c7f1bcb7 gcc/testsuite/g++.old-deja/g++.abi/vmihint.C 305181b858f05a2e683bd7322f635642 gcc/testsuite/g++.old-deja/g++.abi/vtable.C ! 5c18b478ae35248275dbd4c1f22b93c5 gcc/testsuite/g++.old-deja/g++.abi/vtable2.C f43645b177185eca1785bb1bc24abcc7 gcc/testsuite/g++.old-deja/g++.abi/vtable3.h 335628c4bb776c7871e9beac4869bf89 gcc/testsuite/g++.old-deja/g++.abi/vtable3a.C 56ddac7d105a11ccda8236145c04d603 gcc/testsuite/g++.old-deja/g++.abi/vtable3b.C *************** c81d14b770f15026bfe61a7d372c3d0c gcc/te *** 23135,23140 **** --- 23239,23245 ---- e700f43c9f64656f7363a44babf1d9f6 gcc/testsuite/gcc.c-torture/compile/pr60556.c a4c74c3526e0718b04b6e2e2a9cb729b gcc/testsuite/gcc.c-torture/compile/pr60655-1.c ecd86b2ec3c6e99f8c9357249b8569eb gcc/testsuite/gcc.c-torture/compile/pr60655-2.c + 0d246b57fcfef0380c5ac5b0dccf1f50 gcc/testsuite/gcc.c-torture/compile/pr60818.c d47d48bc5d0479f66961edb27b343038 gcc/testsuite/gcc.c-torture/compile/pr61042.c 9463b77ac06a55b7d4a912e2b3389cc1 gcc/testsuite/gcc.c-torture/compile/pr61222-1.c e2006840cb2c2f8c11c42c49fd948263 gcc/testsuite/gcc.c-torture/compile/pr61222-2.c *************** d47f5879509ae9dfb39ea1ee1063230e gcc/te *** 23183,23188 **** --- 23288,23295 ---- 97df20a3b66d4cb718ca2f94a7c64ec5 gcc/testsuite/gcc.c-torture/compile/pr71693.c 6893a5c3e89b00abc6ffaaadabf19bbb gcc/testsuite/gcc.c-torture/compile/pr71916.c bd9f10a73e289f0fdac2ce08641816f0 gcc/testsuite/gcc.c-torture/compile/pr72802.c + 4bdafe7a5c32e03db39dc28806b6e3a0 gcc/testsuite/gcc.c-torture/compile/pr79197.c + 8d2b886d2a6084528abb808154bd0d6b gcc/testsuite/gcc.c-torture/compile/pr79411.c 9611ffa8936d9c80d0a9ccde8dd093b2 gcc/testsuite/gcc.c-torture/compile/pret-arg.c b9e6ce52b90320c1c3803c25113844c5 gcc/testsuite/gcc.c-torture/compile/pta-1.c ed716c1d1727fc2c748162e0cbc4ee47 gcc/testsuite/gcc.c-torture/compile/ptr-conv-1.c *************** a5f4cdd2313a084c86b42c022d5711d7 gcc/te *** 23754,23759 **** --- 23861,23867 ---- 572761fb614de0d4f9d476c472281506 gcc/testsuite/gcc.c-torture/execute/20141107-1.c 9c5cfadcc33f7680c33e3773cc10ee69 gcc/testsuite/gcc.c-torture/execute/20141125-1.c a41347b276541fc0f7e43aa3857bbcf3 gcc/testsuite/gcc.c-torture/execute/20150611-1.c + 13d1e16ba55cc014ade05fa4e93459a9 gcc/testsuite/gcc.c-torture/execute/20170419-1.c 65f01ac7346bd4d47ed9c1ca94ab74ff gcc/testsuite/gcc.c-torture/execute/900409-1.c 5aefab4daab0bd29ecf2a389f3c44f40 gcc/testsuite/gcc.c-torture/execute/920202-1.c 655936aaf9a63e991a555cbc16738485 gcc/testsuite/gcc.c-torture/execute/920302-1.c *************** a1122f266904033a972f83a856de97b9 gcc/te *** 24836,24842 **** --- 24944,24956 ---- 2b843741017aa652b5af0855cf7945c3 gcc/testsuite/gcc.c-torture/execute/pr71626-2.c 5226a45800ff3eb3550e4309d902aa9c gcc/testsuite/gcc.c-torture/execute/pr71700.c 3a2dbae8c6dae23b46868ca068ba47d6 gcc/testsuite/gcc.c-torture/execute/pr7284-1.c + 9bca5db87705467ddabeaa32b5223dba gcc/testsuite/gcc.c-torture/execute/pr77767.c 21b89420d9abfafd5252eafe2c1f8483 gcc/testsuite/gcc.c-torture/execute/pr78378.c + e378b6043986bf34c640d3c898b04895 gcc/testsuite/gcc.c-torture/execute/pr78617.c + 50dd995fe049f6e3600af9d40a5053f7 gcc/testsuite/gcc.c-torture/execute/pr79043.c + ee3df35673fd62ed80d1eda7d107f8eb gcc/testsuite/gcc.c-torture/execute/pr79121.c + 45833b96ada0857a18d70fa0804e7f6f gcc/testsuite/gcc.c-torture/execute/pr80501.c + 0ec1bcb863c85b3589a1923d51468ba2 gcc/testsuite/gcc.c-torture/execute/pr80692.c 85441b3599a9d20a4ede0f10c54a4e6b gcc/testsuite/gcc.c-torture/execute/printf-1.c 54f80bf321bfe46d44040493d9821a03 gcc/testsuite/gcc.c-torture/execute/printf-chk-1.c f397d221ccf3a7ce631cf42078dfadb5 gcc/testsuite/gcc.c-torture/execute/pta-field-1.c *************** a5e988481cd66b8acf6c610b847cb713 gcc/te *** 25480,25485 **** --- 25594,25601 ---- 9a45b4bebab3901180dbe2a44efcd070 gcc/testsuite/gcc.dg/asan/pr64170.c 73f04617a7b0ee3bd0e6f41d954ea876 gcc/testsuite/gcc.dg/asan/pr64981.c f809f9f9e609bf23b1ad12f7a74b21ae gcc/testsuite/gcc.dg/asan/pr66314.c + 97de4b173eeead7faba61cc66980de6f gcc/testsuite/gcc.dg/asan/pr80166.c + 44651454ed7fd7d367ecc8dbce7be369 gcc/testsuite/gcc.dg/asan/pr80168.c da89dc3f01ef08b35253f1daef462bec gcc/testsuite/gcc.dg/asan/sancov-1.c 5ff39290aee620ff2495e8cb5a3905ee gcc/testsuite/gcc.dg/asm-1.c 2f1cb5ecc9847df3e4ff43f286442e31 gcc/testsuite/gcc.dg/asm-10.c *************** eab441b992352dbf346de82ee5ac75d4 gcc/te *** 26154,26159 **** --- 26270,26276 ---- 0b463f87f522d5e174a16f72761a2e3a gcc/testsuite/gcc.dg/comp-goto-1.c b69efdebbddd406113314f5e2222b299 gcc/testsuite/gcc.dg/comp-goto-2.c a54f6f3014d2438520af47284381e304 gcc/testsuite/gcc.dg/comp-goto-3.c + 1f4f70817a422107e4e1998a93c17721 gcc/testsuite/gcc.dg/comp-goto-4.c 78fe3f6717c09fb4c953681eb32836bf gcc/testsuite/gcc.dg/comp-return-1.c 6f243a75c011aca0722f959f9ec14cde gcc/testsuite/gcc.dg/compare1.c ef38565f80d00d4a0dc79476956bb0b8 gcc/testsuite/gcc.dg/compare10.c *************** f83af2708ba44addea950f47d1a44c95 gcc/te *** 27148,27153 **** --- 27265,27271 ---- 7dc01e28775b3a200d65354a6eb7aad1 gcc/testsuite/gcc.dg/debug/pr65771.c 91097ab2e9d846f097881afd70e714fe gcc/testsuite/gcc.dg/debug/pr66068.c f04843ea87c9c55accf161e9ee241f15 gcc/testsuite/gcc.dg/debug/pr66432.c + 2444e8441e19d7a1f14287f247114ea3 gcc/testsuite/gcc.dg/debug/pr80321.c e39702ba4ac8cdf1b4d7895fa15c394f gcc/testsuite/gcc.dg/debug/redecl-1.c 60c3f3165dda429cbc7646a06969d16c gcc/testsuite/gcc.dg/debug/redecl-2.c 175fa916ededdb94d71518eecbe6fa1a gcc/testsuite/gcc.dg/debug/redecl-3.c *************** e6360f93ff139620b9b4a3b964c18b2f gcc/te *** 27378,27383 **** --- 27496,27502 ---- be23acf3456ffa13de8055db4f48d5a4 gcc/testsuite/gcc.dg/fixed-point/operator-logical.c 3024bebbf86c7b8c8e8c83995ddb5d4c gcc/testsuite/gcc.dg/fixed-point/operator-unary.c ab759da2baa8282403e179cab187e798 gcc/testsuite/gcc.dg/fixed-point/pr33466.c + a2912e74487dfcaf9581a1c04d0a91db gcc/testsuite/gcc.dg/fixed-point/pr79971.c 4f22c77ea5ef9ab9db8728bd111a5774 gcc/testsuite/gcc.dg/fixed-point/struct-layout-1.c c97b1003aacfdd8704b17bbedd652f19 gcc/testsuite/gcc.dg/fixed-point/struct-union.c e1a354c41bb3d4cc976c5187375ae365 gcc/testsuite/gcc.dg/fixed-point/types.c *************** e488893b50fec3458ff941b969c6a3ee gcc/te *** 27691,27696 **** --- 27810,27816 ---- b0c5cb8db5ab29eb4607edcfaf632c3c gcc/testsuite/gcc.dg/goacc-gomp/goacc-gomp.exp e301304e13590c1ce7f775ce00ef95b0 gcc/testsuite/gcc.dg/goacc/acc_on_device-1.c e16a173a45eff735a99e16e66cc01685 gcc/testsuite/gcc.dg/goacc/goacc.exp + 3da87b66f3539d73f8aec0575f2d0109 gcc/testsuite/gcc.dg/goacc/loop-processing-1.c 9e00e7a94f979942198724398d213cee gcc/testsuite/gcc.dg/goacc/nested-function-1.c d28df196e898f3e95d6f476710c89624 gcc/testsuite/gcc.dg/goacc/nested-function-2.c acdc22584322b69f4483834bf48a45e9 gcc/testsuite/gcc.dg/goacc/nvptx-merged-loop.c *************** a85b0288fea2d86fdb34d6e61c8fb5c4 gcc/te *** 27879,27885 **** 8e258b137294e32ab51ef624c590d38b gcc/testsuite/gcc.dg/gomp/pr67500.c 05752722a0138a041faa178f567bbfd2 gcc/testsuite/gcc.dg/gomp/pr68128-1.c bc9fedcf7d4ab83a9eac1b425a07e995 gcc/testsuite/gcc.dg/gomp/pr68128-2.c ! 786a43f9f43d8782f065d436edb07d19 gcc/testsuite/gcc.dg/gomp/pr68640.c 32d1b4709fce01c7b0f596da5c040f2a gcc/testsuite/gcc.dg/gomp/preprocess-1.c 5a96f232ac76ad6d8182f67c3f3a4acf gcc/testsuite/gcc.dg/gomp/reduction-1.c 536359d59fc418a1570a6d8574a66ca1 gcc/testsuite/gcc.dg/gomp/sections-1.c --- 27999,28005 ---- 8e258b137294e32ab51ef624c590d38b gcc/testsuite/gcc.dg/gomp/pr67500.c 05752722a0138a041faa178f567bbfd2 gcc/testsuite/gcc.dg/gomp/pr68128-1.c bc9fedcf7d4ab83a9eac1b425a07e995 gcc/testsuite/gcc.dg/gomp/pr68128-2.c ! b6e412b1e41464bf3c6ad63059710985 gcc/testsuite/gcc.dg/gomp/pr68640.c 32d1b4709fce01c7b0f596da5c040f2a gcc/testsuite/gcc.dg/gomp/preprocess-1.c 5a96f232ac76ad6d8182f67c3f3a4acf gcc/testsuite/gcc.dg/gomp/reduction-1.c 536359d59fc418a1570a6d8574a66ca1 gcc/testsuite/gcc.dg/gomp/sections-1.c *************** d0f22c16c5fac5ae8f190b3564aba97d gcc/te *** 28096,28105 **** --- 28216,28231 ---- cbc1d72a5a486c20f3b581d86ceb6480 gcc/testsuite/gcc.dg/graphite/pr69067.c 47d652714c7a00602400f743b5e3c11c gcc/testsuite/gcc.dg/graphite/pr69068.c 4e7f8240209ca1b787c57a784dd3ab73 gcc/testsuite/gcc.dg/graphite/pr69292.c + 4291fea3d27e2dfa567eac5cd625cee2 gcc/testsuite/gcc.dg/graphite/pr69823.c 469d8e302d82650a54a8f0b48adb251a gcc/testsuite/gcc.dg/graphite/pr70045.c 187adff90265612446489b184d1ca625 gcc/testsuite/gcc.dg/graphite/pr70956.c 556528d3765256e3d07d6a463f3541a3 gcc/testsuite/gcc.dg/graphite/pr71575-1.c 636c2aead02ee928a7ad79bdab38cbb3 gcc/testsuite/gcc.dg/graphite/pr71575-2.c + 951125fc2ea749b7c486d1196c946e86 gcc/testsuite/gcc.dg/graphite/pr71824-2.c + ac3c3d116a327df3d3173302cb1a531d gcc/testsuite/gcc.dg/graphite/pr71824-3.c + febbd295db57a2123e78312360a0adee gcc/testsuite/gcc.dg/graphite/pr71824.c + 1b9515edc4478a8ec28b75c7088351fc gcc/testsuite/gcc.dg/graphite/pr79977.c + bb10feccbec2eee90b555fb13034016d gcc/testsuite/gcc.dg/graphite/pr80167.c 16574d3df752f79e2361bed11b712e31 gcc/testsuite/gcc.dg/graphite/run-id-1.c 69c11dc302a921c92977db519167bec1 gcc/testsuite/gcc.dg/graphite/run-id-2.c 84a75a861553ce658d85018a3ced0a6b gcc/testsuite/gcc.dg/graphite/run-id-3.c *************** bbdc28908094ef1ce181532afaf1b2dc gcc/te *** 28455,28461 **** 80f4453150e9ddcd8976703b7c6ee1f6 gcc/testsuite/gcc.dg/ipa/noclone-1.c 40bd41302666d56c4edf7330db97920e gcc/testsuite/gcc.dg/ipa/pr42706.c e4887053c792f4f78b03804c148839ce gcc/testsuite/gcc.dg/ipa/pr45644.c ! 5c428c219954576c308c245d9256f052 gcc/testsuite/gcc.dg/ipa/pr48195.c cdec1b240b89ad7bf971aa799a1ea4a0 gcc/testsuite/gcc.dg/ipa/pr50744.c ca6dd47eed2470f390bd2cdca32f96fb gcc/testsuite/gcc.dg/ipa/pr51362.c ef3f699c90a5350ceb595934cf210763 gcc/testsuite/gcc.dg/ipa/pr55260.c --- 28581,28587 ---- 80f4453150e9ddcd8976703b7c6ee1f6 gcc/testsuite/gcc.dg/ipa/noclone-1.c 40bd41302666d56c4edf7330db97920e gcc/testsuite/gcc.dg/ipa/pr42706.c e4887053c792f4f78b03804c148839ce gcc/testsuite/gcc.dg/ipa/pr45644.c ! 6e1b4f2c5d0c0d768778da8e3b7df828 gcc/testsuite/gcc.dg/ipa/pr48195.c cdec1b240b89ad7bf971aa799a1ea4a0 gcc/testsuite/gcc.dg/ipa/pr50744.c ca6dd47eed2470f390bd2cdca32f96fb gcc/testsuite/gcc.dg/ipa/pr51362.c ef3f699c90a5350ceb595934cf210763 gcc/testsuite/gcc.dg/ipa/pr55260.c *************** e8c67154427e9f7bb58f77e26e3c2513 gcc/te *** 28483,28488 **** --- 28609,28615 ---- 47f323ada98e8576e87b3d61e280cf39 gcc/testsuite/gcc.dg/ipa/pr70306.c 9e20144eec96000223a2e983ffcba9fa gcc/testsuite/gcc.dg/ipa/pr70646.c 9b41a13a82881dc459bf71f6d78e8b4c gcc/testsuite/gcc.dg/ipa/pr71981.c + fa8ddbcc7285d68bc45e806fa10c5aa5 gcc/testsuite/gcc.dg/ipa/pr80104.c 923d1086789aa370483859e89c2a5e1e gcc/testsuite/gcc.dg/ipa/propalign-1.c c42a02d7f371ea4de7e4bb2088296655 gcc/testsuite/gcc.dg/ipa/propalign-2.c b9df72c49860f187596351812c6e05be gcc/testsuite/gcc.dg/ipa/propalign-3.c *************** c5d3ad9a0b06bb1d77cc89309b8629ab gcc/te *** 28734,28739 **** --- 28861,28867 ---- 957e327f63b137847986d2f4b832588e gcc/testsuite/gcc.dg/lto/pr47259_1.c 54e551daabafef19dff2d27e471c5a39 gcc/testsuite/gcc.dg/lto/pr47924_0.c 783b00cf61b59ac61283d1315751dc5c gcc/testsuite/gcc.dg/lto/pr48622_0.c + 2fa784dc45cba9ef34bcc21e141f0a25 gcc/testsuite/gcc.dg/lto/pr50199_0.c 626442299a26bfdc323c3151d4aa1295 gcc/testsuite/gcc.dg/lto/pr51572-1_0.c 383ec2ed7babb4bc10b561c2686f11cf gcc/testsuite/gcc.dg/lto/pr52097_0.c d27dcd8e1afb81501ed01884f9b048f3 gcc/testsuite/gcc.dg/lto/pr52634_0.c *************** e2a69fb19a42b9e9d0fb60b574fc8294 gcc/te *** 28788,28793 **** --- 28916,28923 ---- e79a03eaf2b833f7a45b0112c6e05b26 gcc/testsuite/gcc.dg/lto/pr66221_0.c e4c1f7966a0b687ade65605b5ef05172 gcc/testsuite/gcc.dg/lto/pr66221_1.c 513bc0d418851a55f4d310c4bd07a90b gcc/testsuite/gcc.dg/lto/pr67452_0.c + d042436d2f4ca534a8b4d81610559ebd gcc/testsuite/gcc.dg/lto/pr69188_0.c + 3b4bd973fa6b96913327e429117c532a gcc/testsuite/gcc.dg/lto/pr69188_1.c 90a4d5f47ebe1ffb08d2ceea08a50077 gcc/testsuite/gcc.dg/lto/pr70955_0.c 9e070e93615d99f5f50d833d9a344c13 gcc/testsuite/gcc.dg/lto/pr70955_1.c 260506c568e35bc49112021166edf8f2 gcc/testsuite/gcc.dg/lto/resolutions_0.c *************** c8b6cd5a10630b96dc3a5624216b7302 gcc/te *** 30450,30455 **** --- 30580,30596 ---- 036b89fa8e150cf11fc1400568acc2d2 gcc/testsuite/gcc.dg/pr78185.c 7bfaca350ee545dbe10363c435dfa736 gcc/testsuite/gcc.dg/pr78333.c 48b48216e75ee8522d8a76aa2ac4f516 gcc/testsuite/gcc.dg/pr78540.c + 59fab8559dce9fbb470768e4dc1a6e64 gcc/testsuite/gcc.dg/pr78644-1.c + 4a5d064e4d5178a1ef3e21d03e1a87ec gcc/testsuite/gcc.dg/pr78644-2.c + 24527a55d1c990ac1c42a74f0aae5949 gcc/testsuite/gcc.dg/pr79255.c + 9c25129a5f3400435bb046e327b76463 gcc/testsuite/gcc.dg/pr79494.c + 489b3e216679b50aa195c9691741e9a5 gcc/testsuite/gcc.dg/pr79570.c + 28988c41c40042f95506d21ea70f33cb gcc/testsuite/gcc.dg/pr79574-2.c + 8757e7055d5c4d752bee007011bd64a9 gcc/testsuite/gcc.dg/pr79574.c + c61145f66ad86d5750f921ee12a6d3ea gcc/testsuite/gcc.dg/pr80112.c + 443d0b623cd055eb8afd363bad4d21c4 gcc/testsuite/gcc.dg/pr80218.c + 84b0e8e3e377514aaf1b169b00c28bee gcc/testsuite/gcc.dg/pr80286.c + 21f1c2987bb9b7070a72257997833969 gcc/testsuite/gcc.dg/pr80492.c 8b7d73da2d5d78000716492365a85d5a gcc/testsuite/gcc.dg/pr8715.c 3d08410b2dd57259aa63f0e1c64b376e gcc/testsuite/gcc.dg/pr8788-1.c be04382a35ebb1cfae1b2168f1693a94 gcc/testsuite/gcc.dg/pr8835-1.c *************** cc4ae3ffffb03645629e69a469281efb gcc/te *** 30635,30640 **** --- 30776,30782 ---- ad32dc4c817caee29dda724b10b45399 gcc/testsuite/gcc.dg/spellcheck-options-1.c 2d679bf081885df2fd43ceb67d70169a gcc/testsuite/gcc.dg/spellcheck-options-10.c 44c49d832fbefb746e48d86f5808c52f gcc/testsuite/gcc.dg/spellcheck-options-12.c + 3a9faf9a7d29792a9c5b9ed19ff7ea55 gcc/testsuite/gcc.dg/spellcheck-options-13.c 59ceb721847c724a4d56bf8a0d6c13d6 gcc/testsuite/gcc.dg/spellcheck-options-2.c a2aa8beaba2a63cd762df20a0ff259f9 gcc/testsuite/gcc.dg/spellcheck-options-3.c 533ff9109ecb7635d6ee9e965bed64d5 gcc/testsuite/gcc.dg/spellcheck-options-4.c *************** a032c364dab71f2fa0d5d60b1c055cb4 gcc/te *** 30826,30832 **** a23e685830713b09d43fa65b1bd2e3e8 gcc/testsuite/gcc.dg/tls/diag-5.c f1c2dd7be1455380244b004ceb8da434 gcc/testsuite/gcc.dg/tls/diag-6.c f517413d69eee214da4fc3451286e955 gcc/testsuite/gcc.dg/tls/emutls-1.c ! d81fba04f74758e196f268f0296a10d6 gcc/testsuite/gcc.dg/tls/emutls-2.c f60857e024a3e6b1efbc3d8c46505370 gcc/testsuite/gcc.dg/tls/init-1.c f689330767b0df62f02d401e441836c4 gcc/testsuite/gcc.dg/tls/nonpic-1.c c1da9029fbd5d7305a2f7ad0f12eca29 gcc/testsuite/gcc.dg/tls/opt-1.c --- 30968,30974 ---- a23e685830713b09d43fa65b1bd2e3e8 gcc/testsuite/gcc.dg/tls/diag-5.c f1c2dd7be1455380244b004ceb8da434 gcc/testsuite/gcc.dg/tls/diag-6.c f517413d69eee214da4fc3451286e955 gcc/testsuite/gcc.dg/tls/emutls-1.c ! be5528123de014e5af71ed927343d30a gcc/testsuite/gcc.dg/tls/emutls-2.c f60857e024a3e6b1efbc3d8c46505370 gcc/testsuite/gcc.dg/tls/init-1.c f689330767b0df62f02d401e441836c4 gcc/testsuite/gcc.dg/tls/nonpic-1.c c1da9029fbd5d7305a2f7ad0f12eca29 gcc/testsuite/gcc.dg/tls/opt-1.c *************** da4037959e336e19cb95c25f91f8eb52 gcc/te *** 31699,31704 **** --- 31841,31847 ---- 058fe139380690d2ec38aa882c1f7908 gcc/testsuite/gcc.dg/torture/pr70780.c e8b6639bf1f3ed2ec4f89afdb36f44f9 gcc/testsuite/gcc.dg/torture/pr70935.c b6bb0c63d9e968f4f16f282365518a50 gcc/testsuite/gcc.dg/torture/pr70941.c + e46a78e3302efb3c3756c3e68db06652 gcc/testsuite/gcc.dg/torture/pr71055.c 08b15e14c6c9f4cc6291f19fc8ba963b gcc/testsuite/gcc.dg/torture/pr71423.c 0c398d952cf20fc83aec050f85d8a44b gcc/testsuite/gcc.dg/torture/pr71452.c d7822d9246b54abacbdc7d6230ab041d gcc/testsuite/gcc.dg/torture/pr71522.c *************** b0020481b01ba2fea155b7e666817dc3 gcc/te *** 31706,31712 **** e281b38a3466f38c9a2413771cb95374 gcc/testsuite/gcc.dg/torture/pr71762-1.c a106da354df87c5ff9562af3465dc6a2 gcc/testsuite/gcc.dg/torture/pr71762-2.c a311656e42125d7e8563fa88875fdafb gcc/testsuite/gcc.dg/torture/pr71762-3.c ! 004b0bd191cb4f3bdec6344d582cf888 gcc/testsuite/gcc.dg/torture/pr71881.c 5b3bbac9ac057f5f22a1c0c8f8e8610f gcc/testsuite/gcc.dg/torture/pr72851.c cfd3b0b79c48299cb6628f451d8bf121 gcc/testsuite/gcc.dg/torture/pr73434.c a60b7965903cb9c959e40c476b74eee8 gcc/testsuite/gcc.dg/torture/pr77309.c --- 31849,31855 ---- e281b38a3466f38c9a2413771cb95374 gcc/testsuite/gcc.dg/torture/pr71762-1.c a106da354df87c5ff9562af3465dc6a2 gcc/testsuite/gcc.dg/torture/pr71762-2.c a311656e42125d7e8563fa88875fdafb gcc/testsuite/gcc.dg/torture/pr71762-3.c ! 2efd169675d2de5378ad15e1d0e40378 gcc/testsuite/gcc.dg/torture/pr71881.c 5b3bbac9ac057f5f22a1c0c8f8e8610f gcc/testsuite/gcc.dg/torture/pr72851.c cfd3b0b79c48299cb6628f451d8bf121 gcc/testsuite/gcc.dg/torture/pr73434.c a60b7965903cb9c959e40c476b74eee8 gcc/testsuite/gcc.dg/torture/pr77309.c *************** a878d4452d87793c8c44834bb0002252 gcc/te *** 31730,31735 **** --- 31873,31887 ---- b0c885e4693ad5d7045cd6482b3302de gcc/testsuite/gcc.dg/torture/pr78546-1.c 36933cbf4d027aa17dd72d875c3827ae gcc/testsuite/gcc.dg/torture/pr78546-2.c 993a3dda89ab325c2c0104a20a2b3aa2 gcc/testsuite/gcc.dg/torture/pr78731.c + ab66b40ecce76ec45ca64c32ff85824f gcc/testsuite/gcc.dg/torture/pr78742.c + 0df5ceb12f76a6dc1bf36e2c5183b1b7 gcc/testsuite/gcc.dg/torture/pr79536.c + 454f620b10b777ffe98a6272450350e7 gcc/testsuite/gcc.dg/torture/pr79666.c + f32c1c2791d7c91b2c9f4e051cb74457 gcc/testsuite/gcc.dg/torture/pr79732.c + 028eb97756cfe96f0e2005402ce583df gcc/testsuite/gcc.dg/torture/pr80025.c + 836cdc8e8c71c2a740d491e170406a0c gcc/testsuite/gcc.dg/torture/pr80122.c + ed736f4d42d5b470961915a56ed1dc6c gcc/testsuite/gcc.dg/torture/pr80181.c + 18bcc1e2a028a46b70391f66f2fe3019 gcc/testsuite/gcc.dg/torture/pr80362.c + 87d263c15a5b5f49fa4a5414786fd90b gcc/testsuite/gcc.dg/torture/pr80539.c 62b28db4200d0c4e51bde8d1e5693886 gcc/testsuite/gcc.dg/torture/pr8081.c d086c3946230ba05df33a45be4862730 gcc/testsuite/gcc.dg/torture/pta-callused-1.c 39620328710fd9ff170741766805e426 gcc/testsuite/gcc.dg/torture/pta-escape-1.c *************** fa7217b4e402db46b1d64ca38eb6f212 gcc/te *** 31871,31876 **** --- 32023,32030 ---- 504f32de54a5ad49b342a10f337e5dab gcc/testsuite/gcc.dg/tree-prof/pr52027.c 345c39022fa99a5e40eae744b8bcc403 gcc/testsuite/gcc.dg/tree-prof/pr52150.c 3f27342de254e8240c99bdedc574ddfe gcc/testsuite/gcc.dg/tree-prof/pr59003.c + 4e614f7a830b78a59da0f0b57d372153 gcc/testsuite/gcc.dg/tree-prof/pr66295.c + 41f2b0f1caac2c21616dfe0830cd87fe gcc/testsuite/gcc.dg/tree-prof/pr79587.c 6326a041bce19e077fb8352676c53447 gcc/testsuite/gcc.dg/tree-prof/prof-robust-1.c efc5bb65e5ccc753f9d0b04da251e973 gcc/testsuite/gcc.dg/tree-prof/stringop-1.c 7af2690afeff3e0cd69fc38818777bc1 gcc/testsuite/gcc.dg/tree-prof/stringop-2.c *************** f7a3fabc9425270a4d8e40f8a991ca09 gcc/te *** 32591,32596 **** --- 32745,32753 ---- 6e6845a9fd535b1e4161176393d5993c gcc/testsuite/gcc.dg/tree-ssa/pr70232.c f1ac7f1c1aea72571d0586fcaa61bef4 gcc/testsuite/gcc.dg/tree-ssa/pr70372.c f25359056dca264e17755adacd92210b gcc/testsuite/gcc.dg/tree-ssa/pr70919.c + 54361b5a6c79884df71815f5ccc04ff8 gcc/testsuite/gcc.dg/tree-ssa/pr78428.c + bbf1c06c2256a14579c491f2da36264f gcc/testsuite/gcc.dg/tree-ssa/pr78886.c + 4ac3ddbb068bcfee51e3aaeaaa518512 gcc/testsuite/gcc.dg/tree-ssa/pr79803.c 183e9199984b76de9f1701381d4f612d gcc/testsuite/gcc.dg/tree-ssa/predcom-1.c e1366016e9a4c05dbd1cdb3f152b83dc gcc/testsuite/gcc.dg/tree-ssa/predcom-2.c 49817baec76470758acdd34458c9fb91 gcc/testsuite/gcc.dg/tree-ssa/predcom-3.c *************** acf0af3723cb1d2f1a5fe0dbbb7d9fa9 gcc/te *** 33150,33155 **** --- 33307,33314 ---- 8b53119c2975ba4eb7e0a8a3f21049bc gcc/testsuite/gcc.dg/ubsan/pr63690.c 7a3b89a11b570c0d6817707c745a9fba gcc/testsuite/gcc.dg/ubsan/pr67279.c c9a455b03d901e306e1836d50e9e37d6 gcc/testsuite/gcc.dg/ubsan/pr67662.c + 796829af36eae05fda4a4c261de44807 gcc/testsuite/gcc.dg/ubsan/pr70878.c + 3037e107357a95ddd6b61dbb90af7fde gcc/testsuite/gcc.dg/ubsan/pr80097.c cf1a15de76fafbdf71700c7728936778 gcc/testsuite/gcc.dg/ubsan/ubsan.exp b749062a1214fdf6ba947d30bdf90f30 gcc/testsuite/gcc.dg/ucnid-1.c deec75fcb663af9b8c0ad9b43a81dd3b gcc/testsuite/gcc.dg/ucnid-10.c *************** abe3c6bc74fd9730499cd8e54e143935 gcc/te *** 34290,34295 **** --- 34449,34455 ---- 431e29e277cc621ccb31b18bba96d195 gcc/testsuite/gcc.dg/vect/wrapv-vect-reduc-2short.c 128602b74124111cc0c303da7454560b gcc/testsuite/gcc.dg/vect/wrapv-vect-reduc-dot-s8b.c fd3bcd055bec50020f362b17a4410e68 gcc/testsuite/gcc.dg/vect/wrapv-vect-reduc-pattern-2c.c + deacf2b346fc9032e20669526a1ad31d gcc/testsuite/gcc.dg/vector-1.c 58b3ba1d4334276fa57ab63f07c9918b gcc/testsuite/gcc.dg/vector-shift-2.c fc8de79475ee3413d108466363dd60b6 gcc/testsuite/gcc.dg/vector-shift.c 682b52464ba3c1efc4293e4f2d4ba5b7 gcc/testsuite/gcc.dg/verbose-asm.c *************** daa118ed7835c32ea71c32e65d22689f gcc/te *** 35142,35147 **** --- 35302,35308 ---- f15d1ff83066971ce9a42593ae9e147c gcc/testsuite/gcc.target/aarch64/ctz.c 66e80d99734f8cef1f2093c52336c4c2 gcc/testsuite/gcc.target/aarch64/cvtf_1.c a3fe2b5cb90e5a815cac837604ad4859 gcc/testsuite/gcc.target/aarch64/dwarf-cfa-reg.c + 337c39f85c95ad488bb585665bf18a76 gcc/testsuite/gcc.target/aarch64/eh_return.c 0d0e2a489d3255344941fbdef5cd849a gcc/testsuite/gcc.target/aarch64/eon_1.c 4703bff993ef8bad5cc876cd178c66da gcc/testsuite/gcc.target/aarch64/extend.c 0b2712c817ff082c0b56ddf2137cd33f gcc/testsuite/gcc.target/aarch64/extr.c *************** c78c0b4bf1f9d71f6874b0be55f3f7b8 gcc/te *** 35284,35289 **** --- 35445,35451 ---- eb748e6de8945b3aa35ce6b22a073829 gcc/testsuite/gcc.target/aarch64/pr70398.c e7efe396ef16dbc7526785247ead6d84 gcc/testsuite/gcc.target/aarch64/pr70809_1.c c8c052e3ffb361fbe4b0043b1414c58b gcc/testsuite/gcc.target/aarch64/pr78038.c + ed6579d962ab6988afc3e526e6c51275 gcc/testsuite/gcc.target/aarch64/pr78255.c d3e6defa85b5cd4bb506306377e59a53 gcc/testsuite/gcc.target/aarch64/pragma_cpp_predefs_1.c 1f95766b4ed5bfb5f2cf1f168a607a8d gcc/testsuite/gcc.target/aarch64/predefine_large.c d38e476730748c653068e7cb2d8d6ca6 gcc/testsuite/gcc.target/aarch64/predefine_small.c *************** aa8e6314969635296b924c21de596181 gcc/te *** 36061,36066 **** --- 36223,36230 ---- b80315a2e089ca4c3248a4d827eb49ef gcc/testsuite/gcc.target/arm/atomic-op-seq_cst.c d6a110ab8373cfe1039d83e073de1dee gcc/testsuite/gcc.target/arm/atomic-op-short.c aa7c08b81d2519835225c2bf2d37373d gcc/testsuite/gcc.target/arm/atomic_loaddi_1.c + 5859020e19de924a786d03d4bd1ea91f gcc/testsuite/gcc.target/arm/atomic_loaddi_10.c + 342a363b77439a8d8d3d8a12284842d1 gcc/testsuite/gcc.target/arm/atomic_loaddi_11.c b0c810f8e8ebce60679fb5931167685d gcc/testsuite/gcc.target/arm/atomic_loaddi_2.c 067d9a4dd58e25375a194191c6ac7365 gcc/testsuite/gcc.target/arm/atomic_loaddi_3.c 1d7bea0fc7af466cfda2e07083caf4e7 gcc/testsuite/gcc.target/arm/atomic_loaddi_4.c *************** ef3b417cb5557b3d4caf7046dd71a0f6 gcc/te *** 36177,36182 **** --- 36341,36347 ---- 59b43d7fa573aec56d37e8d3ee175b75 gcc/testsuite/gcc.target/arm/fp16-unprototyped-1.c a60c72361842412ed806a9caeafedd5b gcc/testsuite/gcc.target/arm/fp16-unprototyped-2.c b627f1fc53dc3aa6e38826de78cc3f9d gcc/testsuite/gcc.target/arm/fp16-variadic-1.c + 662eaf09e7fb7e8da30a485a60b49e36 gcc/testsuite/gcc.target/arm/fpscr.c becd73a8b67b5a5ea5ac098897654766 gcc/testsuite/gcc.target/arm/frame-pointer-1.c d197c58c217da8cdebc4b5d30cce8a52 gcc/testsuite/gcc.target/arm/ftest-armv4-arm.c f8c88e22189f7cae3d54e35f7511abc6 gcc/testsuite/gcc.target/arm/ftest-armv4t-arm.c *************** e5aafcaef63ec87ca861c2c3df04f753 gcc/te *** 38479,38487 **** --- 38644,38656 ---- 7b0dff48f8c89cbeb037deb0439e2888 gcc/testsuite/gcc.target/arm/pr70496.c 48ed10e4b1714bfea3579dda3447be58 gcc/testsuite/gcc.target/arm/pr70830.c dc5c76ff01c564582222b3a2ea1fc21c gcc/testsuite/gcc.target/arm/pr71056.c + f54ef63fcfe6438f5564d5ecc3ab119f gcc/testsuite/gcc.target/arm/pr71778.c 7e18572e02a1f69ab777de60c194623d gcc/testsuite/gcc.target/arm/pr77904.c 4c5ae74514e166984fa2a6889c2e475e gcc/testsuite/gcc.target/arm/pr77933-1.c 5569dab63bab16df7a85b99d44757d38 gcc/testsuite/gcc.target/arm/pr77933-2.c + 68c26348d2a6791f295710024aba5c21 gcc/testsuite/gcc.target/arm/pr78041.c + 7ff23bd8b3754acf52c8f22104b1f9b6 gcc/testsuite/gcc.target/arm/pr78255-1.c + 4fffc267d9c8775478c72209db83f52e gcc/testsuite/gcc.target/arm/pr78255-2.c 321232597c3b16471c510b972ad557b4 gcc/testsuite/gcc.target/arm/pragma_attribute.c cdf14fd079c2cd544c152c39ceb8ac66 gcc/testsuite/gcc.target/arm/pragma_cpp_fma.c 639f9aee9e13df807ade02e6ee96c2d3 gcc/testsuite/gcc.target/arm/reg_equal_test.c *************** d2ddd9f00aa7a0ad9e2820dc1193f961 gcc/te *** 38702,38707 **** --- 38871,38877 ---- 30ab9af6e1b1729e2c1b8413367a3fa4 gcc/testsuite/gcc.target/arm/vfp-ldmdbs.c ed2ef7c840d9e4d1d48e068265c47830 gcc/testsuite/gcc.target/arm/vfp-ldmiad.c 87a33317c8651232cbf2e5d43f644e20 gcc/testsuite/gcc.target/arm/vfp-ldmias.c + b9e9de5096e9a8f5cd08694523c50990 gcc/testsuite/gcc.target/arm/vfp-longcall-apcs.c 513a08d8c68e8bd743d34a3725a0eb75 gcc/testsuite/gcc.target/arm/vfp-stmdbd.c 6e3f1e4ca84fd79ca1e8796a761b92c0 gcc/testsuite/gcc.target/arm/vfp-stmdbs.c 555c47f31004ac585fea5b377e38ce85 gcc/testsuite/gcc.target/arm/vfp-stmiad.c *************** b6e744a5c521873cc8be2dbb5f25790d gcc/te *** 39348,39353 **** --- 39518,39524 ---- ab15d222e706bd85c87c037d1e9b6f51 gcc/testsuite/gcc.target/i386/avx-pr63594-1.c 7e490de1d2a70d21844cdc70c1546f49 gcc/testsuite/gcc.target/i386/avx-pr63594-2.c 52efc199588007563ddb240d620c0f01 gcc/testsuite/gcc.target/i386/avx-pr71559.c + 15722fba52fd43dd64c47b080c1c307c gcc/testsuite/gcc.target/i386/avx-pr80286.c 4e3d37bb04b99394790fa9e8caddf790 gcc/testsuite/gcc.target/i386/avx-recip-vec.c 02ae18a66bd7b76f7a651b896f066b70 gcc/testsuite/gcc.target/i386/avx-reduc-1.c 772f703b19bb27d5947d136a2f72221e gcc/testsuite/gcc.target/i386/avx-rint-sfix-2-vec.c *************** e77e7a8b9ae50a450a04aced77a9cbd0 gcc/te *** 42671,42676 **** --- 42842,42851 ---- d961249337eb5f0487f3f532312e3199 gcc/testsuite/gcc.target/i386/mpx/pr68337-1.c e64de766303ab8d2b507adb2517650f5 gcc/testsuite/gcc.target/i386/mpx/pr68337-2.c dedcdece98d6722cf60573a8409aaa81 gcc/testsuite/gcc.target/i386/mpx/pr68416.c + 51d453987274aa6444003b6ad207c139 gcc/testsuite/gcc.target/i386/mpx/pr78339.c + 07d6ed7d973e170542d15b433c8db44e gcc/testsuite/gcc.target/i386/mpx/pr79631.c + d637fa6066a7da620fed27559d7da1b7 gcc/testsuite/gcc.target/i386/mpx/pr79753.c + e96704aac9ccfcbb20830047695ce956 gcc/testsuite/gcc.target/i386/mpx/pr79770.c cb8a04ee24250678af3e3e0db64ccfa6 gcc/testsuite/gcc.target/i386/mpx/realloc-1-lbv.c 16d5e4ac393ac4db6f87f25b4aab5ba2 gcc/testsuite/gcc.target/i386/mpx/realloc-1-nov.c 967cd8d609c7360939caec43d90b8813 gcc/testsuite/gcc.target/i386/mpx/realloc-1-ubv.c *************** dd539fb3f545d1e1b1e1eec620537fe0 gcc/te *** 42822,42827 **** --- 42997,43003 ---- 52d865ff547af45a7c2aeead94e2dde7 gcc/testsuite/gcc.target/i386/mvc5.c 7cc6b0b7de4d22833a76a08b26290ad4 gcc/testsuite/gcc.target/i386/mvc6.c f22ea4607c2fb006c334cb36d08accba gcc/testsuite/gcc.target/i386/mvc7.c + d0135fb9c155d933f970c1e813277fb0 gcc/testsuite/gcc.target/i386/mvc9.c a7f204e20c0df5dad30eac30c4a089ab gcc/testsuite/gcc.target/i386/nest-1.c 1d6127fc3efe2f33f6e8e1851511e6a0 gcc/testsuite/gcc.target/i386/nop-mcount.c 5d0156649119de49cd70a066987d52b0 gcc/testsuite/gcc.target/i386/noplt-1.c *************** a0e8df751a0532abc2f56fae74b35ceb gcc/te *** 43176,43182 **** bb87ab78d18ae08971157445a0d0d394 gcc/testsuite/gcc.target/i386/pr48723.c b26834e660d14d009bf72740343d1f1e gcc/testsuite/gcc.target/i386/pr49002-1.c 1744d1b6525d493782f9f5936b33c289 gcc/testsuite/gcc.target/i386/pr49002-2.c ! a65167e657bbab72f1506f31d68d9425 gcc/testsuite/gcc.target/i386/pr49095.c a294cc6e4c63c7891b458d6b03b24d18 gcc/testsuite/gcc.target/i386/pr49168-1.c e4cb1df2af54fb838523220e3c4c3720 gcc/testsuite/gcc.target/i386/pr49504.c 848587f75336b253219a56277622893a gcc/testsuite/gcc.target/i386/pr49567.c --- 43352,43358 ---- bb87ab78d18ae08971157445a0d0d394 gcc/testsuite/gcc.target/i386/pr48723.c b26834e660d14d009bf72740343d1f1e gcc/testsuite/gcc.target/i386/pr49002-1.c 1744d1b6525d493782f9f5936b33c289 gcc/testsuite/gcc.target/i386/pr49002-2.c ! 3369f8f1bc238cd96148ea54f9434e19 gcc/testsuite/gcc.target/i386/pr49095.c a294cc6e4c63c7891b458d6b03b24d18 gcc/testsuite/gcc.target/i386/pr49168-1.c e4cb1df2af54fb838523220e3c4c3720 gcc/testsuite/gcc.target/i386/pr49504.c 848587f75336b253219a56277622893a gcc/testsuite/gcc.target/i386/pr49567.c *************** fcdb8a2e469f382466d55620e63345f4 gcc/te *** 43439,43445 **** 10edafa5d28fec2dd9bc1ecab31a24f3 gcc/testsuite/gcc.target/i386/pr64617.c 564104a134a0332a3502e02b96c94cb3 gcc/testsuite/gcc.target/i386/pr64805.c 1373d22a1c11a77bbd5c3b0ae7ab163b gcc/testsuite/gcc.target/i386/pr64905.c ! 7fbcddb0d165454214ab9e55f3335039 gcc/testsuite/gcc.target/i386/pr65044.c 3f9f04c2528a876d6e1d568bacdc4432 gcc/testsuite/gcc.target/i386/pr65078-1.c eb5c42e7434196907a6b147b87ede739 gcc/testsuite/gcc.target/i386/pr65078-2.c 0135600497644144bf44c86c6019c038 gcc/testsuite/gcc.target/i386/pr65078-3.c --- 43615,43621 ---- 10edafa5d28fec2dd9bc1ecab31a24f3 gcc/testsuite/gcc.target/i386/pr64617.c 564104a134a0332a3502e02b96c94cb3 gcc/testsuite/gcc.target/i386/pr64805.c 1373d22a1c11a77bbd5c3b0ae7ab163b gcc/testsuite/gcc.target/i386/pr64905.c ! e0cea6ee3a0165475bae6ae4c5c70f79 gcc/testsuite/gcc.target/i386/pr65044.c 3f9f04c2528a876d6e1d568bacdc4432 gcc/testsuite/gcc.target/i386/pr65078-1.c eb5c42e7434196907a6b147b87ede739 gcc/testsuite/gcc.target/i386/pr65078-2.c 0135600497644144bf44c86c6019c038 gcc/testsuite/gcc.target/i386/pr65078-3.c *************** b98041baad19fb37bd266fc10bd5bc38 gcc/te *** 43648,43653 **** --- 43824,43830 ---- c4f6a31f14b030cd9290db1df9495760 gcc/testsuite/gcc.target/i386/pr70876.c 960f365b62f7bf57c12061d19e6822e3 gcc/testsuite/gcc.target/i386/pr70877.c cdf785a2bc0d7b4e9128691fc978d25e gcc/testsuite/gcc.target/i386/pr71077.c + 27e030b5f9e35d267c9bd37d4e1e4a68 gcc/testsuite/gcc.target/i386/pr71458.c 61d0b6b6f6714737a9330dc7fae9ed11 gcc/testsuite/gcc.target/i386/pr71529.C a9c6395b5501af8f7e41af6ddea5ede0 gcc/testsuite/gcc.target/i386/pr71647.c b0d4c3b8fe476c0eb8a512a6ef1cb447 gcc/testsuite/gcc.target/i386/pr72867.c *************** a0f1a716d3aa44f2dbe260d265da5118 gcc/te *** 43666,43671 **** --- 43843,43864 ---- 65244d7660e21de57b2f5bdf3df24107 gcc/testsuite/gcc.target/i386/pr78262.c deb27ae8ba4b14e7c0102c71de9b30e7 gcc/testsuite/gcc.target/i386/pr78310.c 5bf6414deb68de63787bac07281f201f gcc/testsuite/gcc.target/i386/pr78419.c + ca3856428f6efee273c964dd181478b9 gcc/testsuite/gcc.target/i386/pr79495.c + bc00dfd68405a008b750f094120fac4f gcc/testsuite/gcc.target/i386/pr79514.c + e24bb155bc16036a1f39902f9cda1133 gcc/testsuite/gcc.target/i386/pr79559.c + 7dda7ba5d0bc563d983cbcd61cf05cc8 gcc/testsuite/gcc.target/i386/pr79568-1.c + a11495811689152262f1a40e2f796ce9 gcc/testsuite/gcc.target/i386/pr79568-2.c + 18b2847f138512a15d9b786fc39ff5df gcc/testsuite/gcc.target/i386/pr79568-3.c + 775e7fe3e5625b784949e1922efab9ea gcc/testsuite/gcc.target/i386/pr79729.c + b3b6f5c8ba17ba3296bdffadca2efac2 gcc/testsuite/gcc.target/i386/pr79733.c + d6a597f0fbd3fbabaff69609d7a1c3b9 gcc/testsuite/gcc.target/i386/pr79807.c + 79f33466eabfc2e257a8fa0ed96c57ab gcc/testsuite/gcc.target/i386/pr79901.c + d8519fa7ee590fbd3c0a85e2b8653841 gcc/testsuite/gcc.target/i386/pr79932-1.c + f971fc2176ce03b9a33ca253f2499ca0 gcc/testsuite/gcc.target/i386/pr79932-2.c + e4e5537356578134ed01182ab2552b70 gcc/testsuite/gcc.target/i386/pr80019.c + 023c8a995f546efe601f4e53de2a1634 gcc/testsuite/gcc.target/i386/pr80262.c + e9694b4ac41a634860c750f43e4ff35c gcc/testsuite/gcc.target/i386/pr80298-1.c + 1741f4327b4263e09090e49b0a9ff7e1 gcc/testsuite/gcc.target/i386/pr80298-2.c 849234c7a569c1e86023244bc5561263 gcc/testsuite/gcc.target/i386/pr9771-1.c 24ceb6d5f3f5cde4b9d852839bdb98ae gcc/testsuite/gcc.target/i386/prefetchw-1.c f11f4731c396f099373c033ab016a64f gcc/testsuite/gcc.target/i386/prefetchwt1-1.c *************** caf01994c96172dac156c3da29317823 gcc/te *** 45300,45305 **** --- 45493,45499 ---- 37c12fff6f77333d7cb7d787bbb7f908 gcc/testsuite/gcc.target/powerpc/bswap64-4.c 1bdcd38f4043a35aa4799e5b7e1fd590 gcc/testsuite/gcc.target/powerpc/builtins-1.c fc8793b521e1298ab0e99e4fb318b34b gcc/testsuite/gcc.target/powerpc/builtins-2.c + 456232eb27e86ab509433f0e3c8f547d gcc/testsuite/gcc.target/powerpc/builtins-3-p8.c aa7f028ee43d6de435ef9e96d16926a5 gcc/testsuite/gcc.target/powerpc/cell_builtin-1.c 4d701030026d89cdc9d316ac4b013baa gcc/testsuite/gcc.target/powerpc/cell_builtin-2.c 49e4d6ccb42c80379975f32fce0efd5b gcc/testsuite/gcc.target/powerpc/cell_builtin-3.c *************** a034d7a8bf265623a75800f01113e836 gcc/te *** 45348,45355 **** f6511eaddea2d2d6dbb6428c8e9f5822 gcc/testsuite/gcc.target/powerpc/dform-1.c bf3533458cbe01184881116cdb4e822c gcc/testsuite/gcc.target/powerpc/dform-2.c 571072f2c83195496efb8b6a3d7921a1 gcc/testsuite/gcc.target/powerpc/dform-3.c ! f2e8694ab86e1d671840cc1b4d010431 gcc/testsuite/gcc.target/powerpc/dfp-builtin-1.c ! 70b901aef4fec169c6e0277e173417fe gcc/testsuite/gcc.target/powerpc/dfp-builtin-2.c edc590c61b2a5fd6c1f8da5e10b52099 gcc/testsuite/gcc.target/powerpc/dfp-dd-2.c 127103864713219a50dac28ee38910e0 gcc/testsuite/gcc.target/powerpc/dfp-dd.c 918f43d2707c381ec6a3c8f95d06ba7a gcc/testsuite/gcc.target/powerpc/dfp-td-2.c --- 45542,45549 ---- f6511eaddea2d2d6dbb6428c8e9f5822 gcc/testsuite/gcc.target/powerpc/dform-1.c bf3533458cbe01184881116cdb4e822c gcc/testsuite/gcc.target/powerpc/dform-2.c 571072f2c83195496efb8b6a3d7921a1 gcc/testsuite/gcc.target/powerpc/dform-3.c ! e861a888f1deb9e37547f0da1a5f7f2d gcc/testsuite/gcc.target/powerpc/dfp-builtin-1.c ! e5999c82fe083b7c9a7cd976f61a514b gcc/testsuite/gcc.target/powerpc/dfp-builtin-2.c edc590c61b2a5fd6c1f8da5e10b52099 gcc/testsuite/gcc.target/powerpc/dfp-dd-2.c 127103864713219a50dac28ee38910e0 gcc/testsuite/gcc.target/powerpc/dfp-dd.c 918f43d2707c381ec6a3c8f95d06ba7a gcc/testsuite/gcc.target/powerpc/dfp-td-2.c *************** a3a18f288ff9a907cedfa89231e2d3e8 gcc/te *** 45505,45510 **** --- 45699,45705 ---- d0a7757fdd02514672979d273c5dff0d gcc/testsuite/gcc.target/powerpc/optimize-bswapdi-3.c 6d4163ba4e3923c97e0146a17aa2cba9 gcc/testsuite/gcc.target/powerpc/optimize-bswapsi-2.c 582d7bb7e4106b5cb9134d552025a68e gcc/testsuite/gcc.target/powerpc/outofline_rnreg.c + bac0e7d390854f0c869cf6ae4b52c773 gcc/testsuite/gcc.target/powerpc/p8-vec-xl-xst.c d07905c4fe68bcbc9f8aef973a7a039b gcc/testsuite/gcc.target/powerpc/p8vector-builtin-1.c c9275a719128041f0bdbd96336d20f9c gcc/testsuite/gcc.target/powerpc/p8vector-builtin-2.c 330fc5c1657a0c9c682e64e1710acc46 gcc/testsuite/gcc.target/powerpc/p8vector-builtin-3.c *************** c1577e67394b1e9e7510e7d9b946226a gcc/te *** 45708,45713 **** --- 45903,45909 ---- 1dc925cae1c688a77865627d749d015c gcc/testsuite/gcc.target/powerpc/pr67071-3.c 35c73d31cfb2ab34903671c0ed5ded53 gcc/testsuite/gcc.target/powerpc/pr67789.c d513afbb48bce30e890a5d3d76987740 gcc/testsuite/gcc.target/powerpc/pr67808.c + 0d319100b6874eec254061c50995a16b gcc/testsuite/gcc.target/powerpc/pr68163.c b0dae0a08b67b28c3e8a71536d261274 gcc/testsuite/gcc.target/powerpc/pr68805.c d369a7045eda68cbec3227a16d5de67b gcc/testsuite/gcc.target/powerpc/pr68872.c faf2ed46677346059dd2b7fd42254985 gcc/testsuite/gcc.target/powerpc/pr69252.c *************** a31fef5f59c5f12ea342e66137c45ae7 gcc/te *** 45720,45725 **** --- 45916,45922 ---- da2f788bebe8f041672950b7347513cf gcc/testsuite/gcc.target/powerpc/pr70669.c d3a79432800e585b3905439b686d873b gcc/testsuite/gcc.target/powerpc/pr70963.c 31132ce703c42e34a14c7d103e655da2 gcc/testsuite/gcc.target/powerpc/pr71186.c + f417c588db95ee3f7fbced361af8dbfa gcc/testsuite/gcc.target/powerpc/pr71310.c 18f516c22671e1293affe8823881c35c gcc/testsuite/gcc.target/powerpc/pr71493-1.c 7d83053012a7579379ae3f803b73b2ec gcc/testsuite/gcc.target/powerpc/pr71493-2.c 28b1e9d8edb2081a7279eaec89871fee gcc/testsuite/gcc.target/powerpc/pr71656-1.c *************** d9ccfe0048f3d64bbe5861c9aea6294f gcc/te *** 45732,45737 **** --- 45929,45945 ---- 38b7723cf756d98e0ed05ddda91d13e3 gcc/testsuite/gcc.target/powerpc/pr72717.c 3c47d5ea6e68caafb336f0c2f694fea6 gcc/testsuite/gcc.target/powerpc/pr72853.c d13df2d4752807dad63a970f45225730 gcc/testsuite/gcc.target/powerpc/pr72863.c + 8fab8f018ebf5d442e39b9cc4bdf5300 gcc/testsuite/gcc.target/powerpc/pr78543.c + fb524be9fd12ca8094bde96a06f3bdd5 gcc/testsuite/gcc.target/powerpc/pr79197.c + c3838202fd2bf467b26b82f0e155ac76 gcc/testsuite/gcc.target/powerpc/pr79268.c + 0f9344c270baf27d9a4762d111adbc5e gcc/testsuite/gcc.target/powerpc/pr79439.c + 8c1e3ce96b0244e674ef5e0620a4b88e gcc/testsuite/gcc.target/powerpc/pr79544.c + c4116b75f2059a7e1bab2e403b724598 gcc/testsuite/gcc.target/powerpc/pr79947.c + 8fe70e669118bfd74ac64bf553741d89 gcc/testsuite/gcc.target/powerpc/pr79951.c + c74100b0e24e645cbd51ff8d93f11730 gcc/testsuite/gcc.target/powerpc/pr80246.c + 72ae35ee6424648259ebc86bd0a39eac gcc/testsuite/gcc.target/powerpc/pr80510-1.c + d47ea1598c1321fc4399901853c2e875 gcc/testsuite/gcc.target/powerpc/pr80510-2.c + 12068e972df8c5dd156551254f178638 gcc/testsuite/gcc.target/powerpc/pr80718.c 17f878b62dd2e08735d53fce64232a47 gcc/testsuite/gcc.target/powerpc/quad-atomic.c 171a411d14f30e8450dc3f2ef38b1bd7 gcc/testsuite/gcc.target/powerpc/recip-1.c 6b7c4920c070e84f6819377bcdb90c0d gcc/testsuite/gcc.target/powerpc/recip-2.c *************** caf83f2b272138041945d99cf818ff06 gcc/te *** 45766,45771 **** --- 45974,45980 ---- aefbc9c117b311a9394883e9c890efb9 gcc/testsuite/gcc.target/powerpc/spe-vector-memset.c 32bb5e201dd78c548aed0cdf044779ec gcc/testsuite/gcc.target/powerpc/spe1.c c9be7e0cc9ba390460928b1de506fa70 gcc/testsuite/gcc.target/powerpc/stabs-attrib-vect-darwin.c + ab241355ba77c8e163b05eb81f33d1c5 gcc/testsuite/gcc.target/powerpc/stack-limit.c a59ee456442fb848ede07589c0a6bb6e gcc/testsuite/gcc.target/powerpc/swaps-p8-1.c f9cfd48e5324b92443f64a93e5c47140 gcc/testsuite/gcc.target/powerpc/swaps-p8-10.c 150891aea1ac6751746c97b1d0f4215d gcc/testsuite/gcc.target/powerpc/swaps-p8-11.c *************** c891211b25d5266010cad8266c02fe3c gcc/te *** 45783,45788 **** --- 45992,45999 ---- 2fb907d90dbe8b909400b139bfd24dc2 gcc/testsuite/gcc.target/powerpc/swaps-p8-22.c 8cb758ec48a4fd3447970d6f85159dea gcc/testsuite/gcc.target/powerpc/swaps-p8-23.c 99bc5494b60bcbe35a2499e7bc74a125 gcc/testsuite/gcc.target/powerpc/swaps-p8-24.c + 6a3e75b25610f78efa0cbd974726d1df gcc/testsuite/gcc.target/powerpc/swaps-p8-26.c + 6fe65c4dc12e9e595c44e7bbf8f65dea gcc/testsuite/gcc.target/powerpc/swaps-p8-27.c 84237fc0555dd56c639a0274a8f4dbde gcc/testsuite/gcc.target/powerpc/swaps-p8-3.c 0df14a19fd6ee081105fc2b90003a0b4 gcc/testsuite/gcc.target/powerpc/swaps-p8-4.c 26517c689d143f1397c457beaff12ae6 gcc/testsuite/gcc.target/powerpc/swaps-p8-5.c *************** f89bc692aa33f0a854308215a8c5a45c gcc/te *** 45815,45836 **** fa102cb45e48c286b356759209443dea gcc/testsuite/gcc.target/powerpc/vec-mult-char-2.c bbd74596ca12fe9aac0347c6253db300 gcc/testsuite/gcc.target/powerpc/vec-shift.c 8ee50015e788404267646adf1ac95972 gcc/testsuite/gcc.target/powerpc/vec-shr.c 2c89883d083bc93d292eb8be25a26a55 gcc/testsuite/gcc.target/powerpc/vslv-0.c 3032ccdc175db10c55ecb393e9757ea8 gcc/testsuite/gcc.target/powerpc/vslv-1.c 249c2e1b9f88f56726ab8ecfe5c4e957 gcc/testsuite/gcc.target/powerpc/vsrv-0.c b5ff35f6c27a48ed531cd0cb2035da0b gcc/testsuite/gcc.target/powerpc/vsrv-1.c 4ceb6855c2485b8644bf41d0692dce88 gcc/testsuite/gcc.target/powerpc/vsx-builtin-1.c 9e3c77c5253ece30391881a511c37067 gcc/testsuite/gcc.target/powerpc/vsx-builtin-2.c ! 2cbc6ebb458b1e9d41b7cd611b4dbd55 gcc/testsuite/gcc.target/powerpc/vsx-builtin-3.c 6246ea29025c11b1b9f4c6b8d036cbc3 gcc/testsuite/gcc.target/powerpc/vsx-builtin-4.c acf95bd1a1e2b9b14c0640b45f2e75f5 gcc/testsuite/gcc.target/powerpc/vsx-builtin-5.c 0b61a376e7164778a523a0766df4ce6e gcc/testsuite/gcc.target/powerpc/vsx-builtin-6.c aec0aad4ad9d1a50c30d68081c0f2184 gcc/testsuite/gcc.target/powerpc/vsx-builtin-7.c 88cd9f4d3675a8897d01117429ae8094 gcc/testsuite/gcc.target/powerpc/vsx-builtin-8.c - 60164d527bd21ab51c50c80abf146df1 gcc/testsuite/gcc.target/powerpc/vsx-elemrev-1.c - 3af84d85921a35dbef53567c5ede1159 gcc/testsuite/gcc.target/powerpc/vsx-elemrev-2.c - 5b80f1ec62fecc5421d5ce52af4b330c gcc/testsuite/gcc.target/powerpc/vsx-elemrev-3.c - 6b19bf3ff62b230d7085a802e8199e3f gcc/testsuite/gcc.target/powerpc/vsx-elemrev-4.c 29415c0ab3cf79b03ca4a55fa764901b gcc/testsuite/gcc.target/powerpc/vsx-extract-1.c ad77cf7854ac810c73e5ad0184232f20 gcc/testsuite/gcc.target/powerpc/vsx-extract-2.c e4ac7f141f61cf4cf8934fe3ee7cf407 gcc/testsuite/gcc.target/powerpc/vsx-extract-3.c --- 46026,46045 ---- fa102cb45e48c286b356759209443dea gcc/testsuite/gcc.target/powerpc/vec-mult-char-2.c bbd74596ca12fe9aac0347c6253db300 gcc/testsuite/gcc.target/powerpc/vec-shift.c 8ee50015e788404267646adf1ac95972 gcc/testsuite/gcc.target/powerpc/vec-shr.c + 2f7d0faae17249a4c0239bf8d90e399a gcc/testsuite/gcc.target/powerpc/vec-xxpermdi.c + cfe95399d48da5db32fbce7f0c697a3c gcc/testsuite/gcc.target/powerpc/versioned-copy-loop.c 2c89883d083bc93d292eb8be25a26a55 gcc/testsuite/gcc.target/powerpc/vslv-0.c 3032ccdc175db10c55ecb393e9757ea8 gcc/testsuite/gcc.target/powerpc/vslv-1.c 249c2e1b9f88f56726ab8ecfe5c4e957 gcc/testsuite/gcc.target/powerpc/vsrv-0.c b5ff35f6c27a48ed531cd0cb2035da0b gcc/testsuite/gcc.target/powerpc/vsrv-1.c 4ceb6855c2485b8644bf41d0692dce88 gcc/testsuite/gcc.target/powerpc/vsx-builtin-1.c 9e3c77c5253ece30391881a511c37067 gcc/testsuite/gcc.target/powerpc/vsx-builtin-2.c ! d6aef2cc5b6d426a696fad3f9bd0cf2c gcc/testsuite/gcc.target/powerpc/vsx-builtin-3.c 6246ea29025c11b1b9f4c6b8d036cbc3 gcc/testsuite/gcc.target/powerpc/vsx-builtin-4.c acf95bd1a1e2b9b14c0640b45f2e75f5 gcc/testsuite/gcc.target/powerpc/vsx-builtin-5.c 0b61a376e7164778a523a0766df4ce6e gcc/testsuite/gcc.target/powerpc/vsx-builtin-6.c aec0aad4ad9d1a50c30d68081c0f2184 gcc/testsuite/gcc.target/powerpc/vsx-builtin-7.c 88cd9f4d3675a8897d01117429ae8094 gcc/testsuite/gcc.target/powerpc/vsx-builtin-8.c 29415c0ab3cf79b03ca4a55fa764901b gcc/testsuite/gcc.target/powerpc/vsx-extract-1.c ad77cf7854ac810c73e5ad0184232f20 gcc/testsuite/gcc.target/powerpc/vsx-extract-2.c e4ac7f141f61cf4cf8934fe3ee7cf407 gcc/testsuite/gcc.target/powerpc/vsx-extract-3.c *************** b3dd05db76a00a764bd5968152b2ef72 gcc/te *** 45952,45957 **** --- 46161,46167 ---- baa6d1c3d77baf7c1324df7bb6f4f40c gcc/testsuite/gcc.target/s390/insv-3.c 86858e91f5b4dabc479f75228a16d550 gcc/testsuite/gcc.target/s390/leaf-profile.c a054a9b008ac4cce6c7ab7a319e8ccf3 gcc/testsuite/gcc.target/s390/litpool-r3-1.c + 2b7175e138a756516a334fd03dd56b25 gcc/testsuite/gcc.target/s390/litpool-str-1.c 0eb4db3e520e292bba5127a08d0a982d gcc/testsuite/gcc.target/s390/load-relative-check.c 80c910b12aea74c278268b0c8ba833a4 gcc/testsuite/gcc.target/s390/md/movstr-1.c c06cf2adc5393d32c0b9a8d805d6afb4 gcc/testsuite/gcc.target/s390/md/setmem_long-1.c *************** ffba4a644f6c776dd608a5285349bff8 gcc/te *** 46340,46345 **** --- 46550,46556 ---- a67458660c2ef2010f128fdaa4faaa86 gcc/testsuite/gcc.target/sparc/20160104-1.c 22f916e859ece29a91c18dffaca9e14b gcc/testsuite/gcc.target/sparc/20160104-2.c 3d69d4562d0fbb323ff101a9d3271e9a gcc/testsuite/gcc.target/sparc/20160229-1.c + e470b0a0d1a056b60c3915a6dfcfd4ae gcc/testsuite/gcc.target/sparc/20170228-1.c 44373c57181608413fc07f3ec0e2ad6e gcc/testsuite/gcc.target/sparc/align.c 667a877a2fb02d919c4eaaea6fbccbad gcc/testsuite/gcc.target/sparc/array.c 51da71a9631e2769588765c1734024be gcc/testsuite/gcc.target/sparc/bmaskbshuf-1.c *************** bafb883b61e54f84d541ff234e2a48ae gcc/te *** 46397,46402 **** --- 46608,46614 ---- a7580ca897393594541f1e8a7faca531 gcc/testsuite/gcc.target/sparc/lzd.c a6501f830b7d1b9e944beb9e5db075f6 gcc/testsuite/gcc.target/sparc/mfpu.c 81c3ac360590e02354b69b4a77b74588 gcc/testsuite/gcc.target/sparc/mnofpu.c + 06ebc1bfb7ebac800bc8e13a4c96ecdc gcc/testsuite/gcc.target/sparc/niagara7-align.c 27bc21317eeddefa4b9cc41e1c4e363c gcc/testsuite/gcc.target/sparc/noresult.c 0e446c8782cfda1bf1b2b7467cdf43af gcc/testsuite/gcc.target/sparc/pdist-2.c 77281e86e797be1ef8a0784c9a4db58a gcc/testsuite/gcc.target/sparc/pdist-3.c *************** eb9fea9eb3ccdd5fb4d85ac011c10dc5 gcc/te *** 46420,46425 **** --- 46632,46638 ---- 632f93e6b0314e25ec1b43c771cb405c gcc/testsuite/gcc.target/sparc/sparc-reg-1.c 49d4346a32402759d7a9329d2375c502 gcc/testsuite/gcc.target/sparc/sparc-ret-1.c 111c6ff31ffc23f4b402354941b88338 gcc/testsuite/gcc.target/sparc/sparc-ret-2.c + 96ac755e92338efd01e188e2e94bbf8f gcc/testsuite/gcc.target/sparc/sparc-ret-3.c 1943f3e1f1253e644f6fe445637c2dec gcc/testsuite/gcc.target/sparc/sparc-trap-1.c 56916c729edb4e4a55554940b0a792d9 gcc/testsuite/gcc.target/sparc/sparc.exp 9d0e2b5fe42dfe4e33a910954d24877b gcc/testsuite/gcc.target/sparc/struct-ret-check-1.c *************** da95c5400735f4c2f4fc34487feb21f8 gcc/te *** 47827,47832 **** --- 48040,48046 ---- 081b7861449ee503eb0eafc38aa74102 gcc/testsuite/gfortran.dg/class_56.f90 e656331cc901eecd1321f4812180dc51 gcc/testsuite/gfortran.dg/class_57.f90 58bc4a716942caffe0323c7d0b20a63e gcc/testsuite/gfortran.dg/class_6.f03 + 28b51cf2f3868e0d992356221459b6b8 gcc/testsuite/gfortran.dg/class_62.f90 cc0c048415b8d0593fe7e5b164763dc7 gcc/testsuite/gfortran.dg/class_7.f03 765b5ae237d318aee8909def266c457e gcc/testsuite/gfortran.dg/class_8.f03 dac9a57a157d95214c44d80cc02bd042 gcc/testsuite/gfortran.dg/class_9.f03 *************** fed16f1f7d3b8c720c68cbd01b83fa43 gcc/te *** 47912,47917 **** --- 48126,48133 ---- 393c735e4ed3573f46d59b6be8dfe555 gcc/testsuite/gfortran.dg/coarray/dummy_1.f90 145d35dc06fc9f1f4dedae6e06844cc4 gcc/testsuite/gfortran.dg/coarray/event_1.f90 82478fce64f3e0b6eabec854f96800c2 gcc/testsuite/gfortran.dg/coarray/event_2.f90 + 7bdec35df5c34a10372c7a54a6b5ab8f gcc/testsuite/gfortran.dg/coarray/event_3.f08 + 69e67a47c4572bb8954e710fb63e1241 gcc/testsuite/gfortran.dg/coarray/event_4.f08 7d4c5cfc3c55e28060d2d7c4a70d70d9 gcc/testsuite/gfortran.dg/coarray/get_array.f90 6cb57e0edb7420fbfa56608c6eaa63df gcc/testsuite/gfortran.dg/coarray/image_index_1.f90 c9182edacbb3ad98cf9b81ced7356078 gcc/testsuite/gfortran.dg/coarray/image_index_2.f90 *************** ce022dd06d4bbcef98eafafee33de6d5 gcc/te *** 47970,47975 **** --- 48186,48192 ---- ac773563b3252cd5f895af702a441868 gcc/testsuite/gfortran.dg/coarray_39.f90 ad8ecfdba25ace790b9bfc8e94e0e05f gcc/testsuite/gfortran.dg/coarray_4.f90 a0baae37f57b46ddb5f4e90b382dcd9b gcc/testsuite/gfortran.dg/coarray_40.f90 + 92bca8fe3f596449a354c1e4133bdf71 gcc/testsuite/gfortran.dg/coarray_43.f90 ef172e1d19584d7e55648b555dbf8fa3 gcc/testsuite/gfortran.dg/coarray_5.f90 337935b709715398df39ee0eeaaec67b gcc/testsuite/gfortran.dg/coarray_6.f90 8cd45380911a9bd61eac7c6b76c8862b gcc/testsuite/gfortran.dg/coarray_7.f90 *************** d8b0925104e27edfd7554327aec7e656 gcc/te *** 48006,48011 **** --- 48223,48229 ---- 3868ecdad997c64216510129983de4eb gcc/testsuite/gfortran.dg/coarray_collectives_8.f90 e7f7c38c4530db86c8bf560b1800b017 gcc/testsuite/gfortran.dg/coarray_collectives_9.f90 967c97a8edd55b3e24d9f53bacf51ab2 gcc/testsuite/gfortran.dg/coarray_critical_1.f90 + ae24a8ba632b111617b5af3d9ec9ed23 gcc/testsuite/gfortran.dg/coarray_event_1.f08 bb588ca9ed7494c0c7d150e652ba7286 gcc/testsuite/gfortran.dg/coarray_lib_alloc_1.f90 1e959df691b79ed29fff217b53c74fe7 gcc/testsuite/gfortran.dg/coarray_lib_alloc_2.f90 af5efe6bd5b1719b406571ec7148073f gcc/testsuite/gfortran.dg/coarray_lib_alloc_3.f90 *************** c97065b51ddecb2dd0bed020f4e461ed gcc/te *** 48659,48664 **** --- 48877,48884 ---- 8d8068df6ac24ffed1c07629391baa04 gcc/testsuite/gfortran.dg/fgetc_2.f90 a5092dd9571c4f2b5be00428c0f86f5a gcc/testsuite/gfortran.dg/filename_null.f90 5131e5c566230f78ec144630a732c7a7 gcc/testsuite/gfortran.dg/filepos1.f90 + 18131393256651d0bd551639eab3e10e gcc/testsuite/gfortran.dg/fimplicit_none_1.f90 + c77a0a5fc1106230319c2398b807df5c gcc/testsuite/gfortran.dg/fimplicit_none_2.f90 c031807c998e0243776199536a506418 gcc/testsuite/gfortran.dg/finalize_1.f08 15ab8e9eee9458ca251042b82b7b69d5 gcc/testsuite/gfortran.dg/finalize_10.f90 784234f297364a91d0841e02c618213b gcc/testsuite/gfortran.dg/finalize_11.f90 *************** cd31a5dc5969cfcb906ab73337df18f6 gcc/te *** 49042,49049 **** 75939469112fee78b1b02766f3b89733 gcc/testsuite/gfortran.dg/goacc/host_data-tree.f95 0a980846e59d2913b99c250e76fa99cf gcc/testsuite/gfortran.dg/goacc/if.f95 ce74911a246da843d2626a4a20b1b0c4 gcc/testsuite/gfortran.dg/goacc/kernels-alias-2.f95 ! 8f1e7c7080f9fdb795e137d6f089ab43 gcc/testsuite/gfortran.dg/goacc/kernels-alias-3.f95 ! b109ab4acf7b62180f6f9edaf3bcec68 gcc/testsuite/gfortran.dg/goacc/kernels-alias-4.f95 7c77903590fd7c726078e8f685cade4a gcc/testsuite/gfortran.dg/goacc/kernels-alias.f95 b0bd0bb3bdbad78b6e58388874beba1f gcc/testsuite/gfortran.dg/goacc/kernels-loop-2.f95 0f109677300fb161c3249465887861ec gcc/testsuite/gfortran.dg/goacc/kernels-loop-data-2.f95 --- 49262,49269 ---- 75939469112fee78b1b02766f3b89733 gcc/testsuite/gfortran.dg/goacc/host_data-tree.f95 0a980846e59d2913b99c250e76fa99cf gcc/testsuite/gfortran.dg/goacc/if.f95 ce74911a246da843d2626a4a20b1b0c4 gcc/testsuite/gfortran.dg/goacc/kernels-alias-2.f95 ! d5dc508fa5f0c7f41320b204b50e6bc2 gcc/testsuite/gfortran.dg/goacc/kernels-alias-3.f95 ! 60e6738878a90bec1f4f070a03f9a09f gcc/testsuite/gfortran.dg/goacc/kernels-alias-4.f95 7c77903590fd7c726078e8f685cade4a gcc/testsuite/gfortran.dg/goacc/kernels-alias.f95 b0bd0bb3bdbad78b6e58388874beba1f gcc/testsuite/gfortran.dg/goacc/kernels-loop-2.f95 0f109677300fb161c3249465887861ec gcc/testsuite/gfortran.dg/goacc/kernels-loop-data-2.f95 *************** b7bb651884d39c2e5dce7d57d46f40a5 gcc/te *** 49174,49180 **** 26ce5f3f5538f91d60c481f8acdc7dd6 gcc/testsuite/gfortran.dg/gomp/gomp.exp ae3e8f9f2ac767a8a192a41e04d26667 gcc/testsuite/gfortran.dg/gomp/gridify-1.f90 c6b23e36c3423a3454fb19b0ec6f0e01 gcc/testsuite/gfortran.dg/gomp/intentin1.f90 ! b1673181b9c53873249af351f2b5c845 gcc/testsuite/gfortran.dg/gomp/map-1.f90 52223211c34f4dbace5e033f8243ae1f gcc/testsuite/gfortran.dg/gomp/omp_atomic1.f90 0e5454ac80bc199d6cf3e96e9750c33f gcc/testsuite/gfortran.dg/gomp/omp_atomic2.f90 5d43e477ab60e438b8824d612b24022d gcc/testsuite/gfortran.dg/gomp/omp_clauses1.f90 --- 49394,49400 ---- 26ce5f3f5538f91d60c481f8acdc7dd6 gcc/testsuite/gfortran.dg/gomp/gomp.exp ae3e8f9f2ac767a8a192a41e04d26667 gcc/testsuite/gfortran.dg/gomp/gridify-1.f90 c6b23e36c3423a3454fb19b0ec6f0e01 gcc/testsuite/gfortran.dg/gomp/intentin1.f90 ! be152538cccb659bb8dac0eda81355e5 gcc/testsuite/gfortran.dg/gomp/map-1.f90 52223211c34f4dbace5e033f8243ae1f gcc/testsuite/gfortran.dg/gomp/omp_atomic1.f90 0e5454ac80bc199d6cf3e96e9750c33f gcc/testsuite/gfortran.dg/gomp/omp_atomic2.f90 5d43e477ab60e438b8824d612b24022d gcc/testsuite/gfortran.dg/gomp/omp_clauses1.f90 *************** e5f0ff2c94fb41e447563955917d04b7 gcc/te *** 49246,49251 **** --- 49466,49474 ---- 8968b6642e6ba9ea7870f963ca23770a gcc/testsuite/gfortran.dg/gomp/pr77973.f90 597f76dd386ee781839ef6d3ac92cd38 gcc/testsuite/gfortran.dg/gomp/pr78298.f90 7031f0539504d7051ea534bfda971893 gcc/testsuite/gfortran.dg/gomp/pr78299.f90 + c77cea4fe3e6db60cec6014217b3e898 gcc/testsuite/gfortran.dg/gomp/pr78866-1.f90 + 7be086a304cd4d607913bd32ad2448ca gcc/testsuite/gfortran.dg/gomp/pr78866-2.f90 + 9b10d6e97e6ec036398bc75fe623a968 gcc/testsuite/gfortran.dg/gomp/pr80918.f90 b4be3f9de7631846875a711ae9b67293 gcc/testsuite/gfortran.dg/gomp/proc_ptr_1.f90 87885556568e657ef4c936c53e1c7305 gcc/testsuite/gfortran.dg/gomp/proc_ptr_2.f90 59e444df8ec8f5ea9859b5aef4d75865 gcc/testsuite/gfortran.dg/gomp/reduction1.f90 *************** d53eed77659562e5b66d14b3a5271897 gcc/te *** 49935,49940 **** --- 50158,50164 ---- 368ecceacb36bc8031de56fda6503830 gcc/testsuite/gfortran.dg/matmul_argument_types.f90 6ed82ab65a659c5528ba6467505d80bd gcc/testsuite/gfortran.dg/matmul_bounds_1.f90 6afa8720ca49e185b4be9435bcad728e gcc/testsuite/gfortran.dg/matmul_bounds_10.f90 + e14d55bfbb5ec45341e5817637d87094 gcc/testsuite/gfortran.dg/matmul_bounds_12.f90 593ee7fab776b72ccabee9746364f3ec gcc/testsuite/gfortran.dg/matmul_bounds_2.f90 04b6384e6df8392804f84acedfe4c7b9 gcc/testsuite/gfortran.dg/matmul_bounds_3.f90 1b539cfef798bf4060dbbccd58b5337c gcc/testsuite/gfortran.dg/matmul_bounds_4.f90 *************** a997ec96c9e5b5703664c90f0b844fe1 gcc/te *** 50727,50732 **** --- 50951,50957 ---- 6701f92b9541522f589f8caf4f94fe71 gcc/testsuite/gfortran.dg/pr78092.f90 38417bf1cb92bb7d70724f9be2c325ca gcc/testsuite/gfortran.dg/pr78279.f90 c8893a59741e05d503a560b19c9684a9 gcc/testsuite/gfortran.dg/pr78297.f90 + 2726988d026410339c6efa9ff66b2464 gcc/testsuite/gfortran.dg/pr80752.f90 6ff99f4b0021f30bee039a61db7cba9d gcc/testsuite/gfortran.dg/predcom-1.f 20a411a7e5a57891297c4c6a96d92009 gcc/testsuite/gfortran.dg/predcom-2.f 80cf60710448ac2378aecda5fc4a57b6 gcc/testsuite/gfortran.dg/present_1.f90 *************** d93a9e353ffa27762f707c539093d6ce gcc/te *** 50877,50883 **** --- 51102,51110 ---- 7e0250e09f1d6fd62c3c197b85915c43 gcc/testsuite/gfortran.dg/proc_ptr_comp_43.f90 72f01172bd92b8cb8853693a0a79310d gcc/testsuite/gfortran.dg/proc_ptr_comp_44.f90 c7c6f9039ee8a7d60608874366e1f0e6 gcc/testsuite/gfortran.dg/proc_ptr_comp_45.f90 + c75d4858dc637cf3362d7fd34a2b2c12 gcc/testsuite/gfortran.dg/proc_ptr_comp_49.f90 9440b7a38d0f8e2941673b44554c91fe gcc/testsuite/gfortran.dg/proc_ptr_comp_5.f90 + 301350ead67fb8e45886f0d873e81b06 gcc/testsuite/gfortran.dg/proc_ptr_comp_50.f90 6347d321213f9347afa49d4354eb67f7 gcc/testsuite/gfortran.dg/proc_ptr_comp_6.f90 f41c3a8af3a63f5aef54c294fa8cd9c5 gcc/testsuite/gfortran.dg/proc_ptr_comp_7.f90 a43898fbcd332118da14c8be5eec75b3 gcc/testsuite/gfortran.dg/proc_ptr_comp_8.f90 *************** f5153e8883f791f3cc0646a71b5c6e9b gcc/te *** 51247,51252 **** --- 51474,51480 ---- cedac13505e8a5175fa43ac2c3c4834d gcc/testsuite/gfortran.dg/specifics_2.f90 1fdd8f1d3aa20721e1933ead1efffc62 gcc/testsuite/gfortran.dg/spread_bounds_1.f90 daf0222210712781403f97bde0118f88 gcc/testsuite/gfortran.dg/spread_init_expr.f03 + 9739831622df43894c7628df7fbfdbe7 gcc/testsuite/gfortran.dg/spread_init_expr_2.f90 010cfcdec31146aa14377199603e5cca gcc/testsuite/gfortran.dg/spread_scalar_source.f90 654688402ffab04ce051df7b4f572427 gcc/testsuite/gfortran.dg/spread_shape_1.f90 4a6636fb35b05d54b152a2bb04221e10 gcc/testsuite/gfortran.dg/spread_size_limit.f90 *************** ed46c8518346f2d7541fbd9f524634aa gcc/te *** 51333,51338 **** --- 51561,51572 ---- 05fc9a3c7e9137124388bb9ec99e3025 gcc/testsuite/gfortran.dg/submodule_18.f08 7ec3aba83cb3dc8728e78a86df5c15ae gcc/testsuite/gfortran.dg/submodule_19.f08 97424405e3e17827757a639a19573fa4 gcc/testsuite/gfortran.dg/submodule_2.f08 + 970aae252f9aced89cf731d6e1ee1a88 gcc/testsuite/gfortran.dg/submodule_21.f08 + 2d6b9c10ee531746fc5c371c23349641 gcc/testsuite/gfortran.dg/submodule_22.f08 + 246b2f641ad26d811da35adb0b318bad gcc/testsuite/gfortran.dg/submodule_25.f08 + 1a357d1a6209523cf7353089bac999dd gcc/testsuite/gfortran.dg/submodule_26.f08 + e1ecc346f86103555c66ea6afae29102 gcc/testsuite/gfortran.dg/submodule_27.f08 + d1663fd4e1368341812629ea5580dde9 gcc/testsuite/gfortran.dg/submodule_28.f08 ac42e5598feef42b948692956c7ed537 gcc/testsuite/gfortran.dg/submodule_3.f08 68f9f70d888318a31160ba732171726f gcc/testsuite/gfortran.dg/submodule_4.f08 1fbed56af4313e533e45631365afe8d6 gcc/testsuite/gfortran.dg/submodule_5.f08 *************** c2c90d907c994840dc1230a7fae3bc20 gcc/te *** 52369,52374 **** --- 52603,52617 ---- 5619805d9941e991d13d9005752207f0 gcc/testsuite/gnat.dg/array25.adb bfa81d6728b526598e310927183d4f39 gcc/testsuite/gnat.dg/array25_pkg.adb a55a94a8501a09516bdb4c6e6905e7a3 gcc/testsuite/gnat.dg/array25_pkg.ads + 3bd423085efe4115ac63639bf9422281 gcc/testsuite/gnat.dg/array26.adb + 6b6bf4299eeadc76dc3c570dc20f5b45 gcc/testsuite/gnat.dg/array26_pkg.adb + 89300267032190ab3f5e2ded166db247 gcc/testsuite/gnat.dg/array26_pkg.ads + 813df093274825298b8e2ff0f06058c9 gcc/testsuite/gnat.dg/array27.adb + c826c2573fee2010dab38f0be39fab9a gcc/testsuite/gnat.dg/array27_pkg.adb + 0f5e293b040f83a0bcdc7e5f55a408a6 gcc/testsuite/gnat.dg/array27_pkg.ads + 992f8fadfe4c3c4b445834bf65695689 gcc/testsuite/gnat.dg/array28.adb + bf1a2c9b961f9dff5a53f9a8809384a9 gcc/testsuite/gnat.dg/array28_pkg.adb + 5ff837fbd986bc07a6a3af8c2adb4bc3 gcc/testsuite/gnat.dg/array28_pkg.ads ce95a40ed45efc9a52f92f6d4700acb5 gcc/testsuite/gnat.dg/array3.adb b1368ee1737ab5c2b00482e137e1a378 gcc/testsuite/gnat.dg/array4.adb 3d29182d58b83e2662df3d9534b80184 gcc/testsuite/gnat.dg/array5.adb *************** d715f4258a659b9f52add768ec0176d3 gcc/te *** 53073,53078 **** --- 53316,53322 ---- 955ffa4de9c3acdbd5ce5334b1af9aa3 gcc/testsuite/gnat.dg/opt59_pkg.ads e5e7ff61479fbeb7973786d07f72ba84 gcc/testsuite/gnat.dg/opt6.adb 87097de987361854f4c5179a6de42c2c gcc/testsuite/gnat.dg/opt6.ads + 05b2d9ff3364801eae257251792ddd49 gcc/testsuite/gnat.dg/opt63.adb a441d166cc0d4b34342468308b350060 gcc/testsuite/gnat.dg/opt7.adb 8ea613067c21d3bbf860fb8bb4013c79 gcc/testsuite/gnat.dg/opt7.ads 81951fc84d3d36131be8aca4f80c113b gcc/testsuite/gnat.dg/opt7_pkg.ads *************** b189cd562dad0502b19d7f4469da5973 gcc/te *** 55027,55033 **** bc3c7df09495f62a7ff924aeda27871f gcc/testsuite/lib/scantree.exp fd4fe0b217182ec61ad209b8b9560725 gcc/testsuite/lib/target-libpath.exp f475e8e2d4f9bd50e1c4f5ee88955e99 gcc/testsuite/lib/target-supports-dg.exp ! 49df8c79e02a44c764f42e21109d397f gcc/testsuite/lib/target-supports.exp cfcacc2a887c0ba90640d2646cdb13df gcc/testsuite/lib/target-utils.exp d0478737f0c5786d095c1ca581b0dafa gcc/testsuite/lib/timeout-dg.exp ab858bda48392f10cfc775daebf0bbd8 gcc/testsuite/lib/timeout.exp --- 55271,55277 ---- bc3c7df09495f62a7ff924aeda27871f gcc/testsuite/lib/scantree.exp fd4fe0b217182ec61ad209b8b9560725 gcc/testsuite/lib/target-libpath.exp f475e8e2d4f9bd50e1c4f5ee88955e99 gcc/testsuite/lib/target-supports-dg.exp ! d7688cbc8884b71ecee2a5e2c72976a0 gcc/testsuite/lib/target-supports.exp cfcacc2a887c0ba90640d2646cdb13df gcc/testsuite/lib/target-utils.exp d0478737f0c5786d095c1ca581b0dafa gcc/testsuite/lib/timeout-dg.exp ab858bda48392f10cfc775daebf0bbd8 gcc/testsuite/lib/timeout.exp *************** a57e521085412bbde60e78229ace4fd5 gcc/te *** 55982,55988 **** 270ecff76752a63ed71a9cd892884668 gcc/timevar.def 5d6d78630ce2cf12488bfb9fba34b7da gcc/timevar.h 1db6f2e372b1af92e0671da08d9bae7b gcc/tlink.c ! 67e5012a5b3f405f6257abc6a945e73e gcc/toplev.c 4b9e8fd609c1573d9fd5d43bde33866c gcc/toplev.h 640b9f5b4c75b1191149544e0f1c76d9 gcc/tracer.c c2de57030d2bf66cc4f12053073051ea gcc/tracer.h --- 56226,56232 ---- 270ecff76752a63ed71a9cd892884668 gcc/timevar.def 5d6d78630ce2cf12488bfb9fba34b7da gcc/timevar.h 1db6f2e372b1af92e0671da08d9bae7b gcc/tlink.c ! 7df85dd356e2967ffb6615047b75f648 gcc/toplev.c 4b9e8fd609c1573d9fd5d43bde33866c gcc/toplev.h 640b9f5b4c75b1191149544e0f1c76d9 gcc/tracer.c c2de57030d2bf66cc4f12053073051ea gcc/tracer.h *************** c2de57030d2bf66cc4f12053073051ea gcc/tr *** 55990,56008 **** 80e93288a01da9902b7ae5d4d7703d7d gcc/trans-mem.h ebf6771f48ae1841ddfbf88247a3f09c gcc/tree-affine.c b7ac15ce242138c75742658d56a84c21 gcc/tree-affine.h ! 2cfbb0b091bf329b0773fe5fd0a70413 gcc/tree-call-cdce.c 8adeb214714a7b5302880f0d135a2120 gcc/tree-cfg.c 00ab69b88ecd4e9242b16c9d28d3372b gcc/tree-cfg.h 8dd4804f8f9a45535c22b8a660afa1b7 gcc/tree-cfgcleanup.c 00f42379eee5485bfc493cb60e0d7d5b gcc/tree-cfgcleanup.h ! aca1f99bd5df778be73f5678d6f93360 gcc/tree-chkp-opt.c ! 7e6ad67e923cf3b95ff981d14d0c4a1d gcc/tree-chkp.c 2ff57aba516c82bd2d6d9444d695ca7c gcc/tree-chkp.h ! 322ccef77f65bb54598598c04a8c3ade gcc/tree-chrec.c 43ea0ae76ce17d30b45a0433304ef5b7 gcc/tree-chrec.h 96fa8679d7e4795292520374bdb5858e gcc/tree-complex.c 5731f012f23420d3b9062279797329a2 gcc/tree-core.h ! c7119678b014861faaee4afe5d14d184 gcc/tree-data-ref.c 1496ec37edd1937619bc6b375be9338b gcc/tree-data-ref.h a446fc894b8383c357a029c57fd75a17 gcc/tree-dfa.c 102e7b82072face5a636762f103313b1 gcc/tree-dfa.h --- 56234,56252 ---- 80e93288a01da9902b7ae5d4d7703d7d gcc/trans-mem.h ebf6771f48ae1841ddfbf88247a3f09c gcc/tree-affine.c b7ac15ce242138c75742658d56a84c21 gcc/tree-affine.h ! f08553a76094e9e1c91b0e121f082d7a gcc/tree-call-cdce.c 8adeb214714a7b5302880f0d135a2120 gcc/tree-cfg.c 00ab69b88ecd4e9242b16c9d28d3372b gcc/tree-cfg.h 8dd4804f8f9a45535c22b8a660afa1b7 gcc/tree-cfgcleanup.c 00f42379eee5485bfc493cb60e0d7d5b gcc/tree-cfgcleanup.h ! a0af19d7f8f74516a5e87d3b72f38040 gcc/tree-chkp-opt.c ! 58ccc7e97d9021608872d7663680ff19 gcc/tree-chkp.c 2ff57aba516c82bd2d6d9444d695ca7c gcc/tree-chkp.h ! 19d9e52ae4295dfc6c6562167b2fe5fe gcc/tree-chrec.c 43ea0ae76ce17d30b45a0433304ef5b7 gcc/tree-chrec.h 96fa8679d7e4795292520374bdb5858e gcc/tree-complex.c 5731f012f23420d3b9062279797329a2 gcc/tree-core.h ! 120259d02d1b105f0a84edafb50c1d88 gcc/tree-data-ref.c 1496ec37edd1937619bc6b375be9338b gcc/tree-data-ref.h a446fc894b8383c357a029c57fd75a17 gcc/tree-dfa.c 102e7b82072face5a636762f103313b1 gcc/tree-dfa.h *************** a446fc894b8383c357a029c57fd75a17 gcc/tr *** 56010,56023 **** 94f3c8f3c0a1d1b655295d9bba767402 gcc/tree-diagnostic.h 360910e9b7e81970e3a84e83c40ccb1f gcc/tree-dump.c 6264c6a5b3585a53739812488f1a7799 gcc/tree-dump.h ! 0da87f07c5ac041477e24cead6be7aba gcc/tree-eh.c 23faec462461de190dbd345899901987 gcc/tree-eh.h 23e376efd0609f310633c89495df98e1 gcc/tree-emutls.c 735714950a7040219bdede8abc940737 gcc/tree-hash-traits.h 4646d637e5cb964a4e6ad3a2589d1cda gcc/tree-hasher.h 4bbc44b137c67f0e938bded3978e7037 gcc/tree-if-conv.c ! fd40c71c70c910f7cfc9a59e66dbb861 gcc/tree-inline.c ! 38646e6febfe5a1052ade3533870efa3 gcc/tree-inline.h 0f77f4c320b8b8381c286d3e856c6093 gcc/tree-into-ssa.c fd4c3d5580777d50b0274967152c64a0 gcc/tree-into-ssa.h 222c5d841b6028c827eae9f43d0f4d20 gcc/tree-iterator.c --- 56254,56267 ---- 94f3c8f3c0a1d1b655295d9bba767402 gcc/tree-diagnostic.h 360910e9b7e81970e3a84e83c40ccb1f gcc/tree-dump.c 6264c6a5b3585a53739812488f1a7799 gcc/tree-dump.h ! 015aa712830a0381d6f8364fdecab98c gcc/tree-eh.c 23faec462461de190dbd345899901987 gcc/tree-eh.h 23e376efd0609f310633c89495df98e1 gcc/tree-emutls.c 735714950a7040219bdede8abc940737 gcc/tree-hash-traits.h 4646d637e5cb964a4e6ad3a2589d1cda gcc/tree-hasher.h 4bbc44b137c67f0e938bded3978e7037 gcc/tree-if-conv.c ! d9c354ccf0d5f256655a74b592e92c63 gcc/tree-inline.c ! ac9d6a0104dae943703687d0f66e6384 gcc/tree-inline.h 0f77f4c320b8b8381c286d3e856c6093 gcc/tree-into-ssa.c fd4c3d5580777d50b0274967152c64a0 gcc/tree-into-ssa.h 222c5d841b6028c827eae9f43d0f4d20 gcc/tree-iterator.c *************** f68eba59616ea0d71903e45ebf4f301b gcc/tr *** 56030,56036 **** 09aeb8e8a96f12d60fd3221cd8bbd33c gcc/tree-object-size.h bfdff86bbeca1fa7f1812fcf614346ef gcc/tree-outof-ssa.c d54568e25cf2ea37efc4fdbdb7cc946a gcc/tree-outof-ssa.h ! c9576b6902fcdea6aaeda58bf15e2b8e gcc/tree-parloops.c 7ce5eef33036ddee4a6e8a3acdfd1192 gcc/tree-parloops.h de582deb9950074ca35160a70f2150c3 gcc/tree-pass.h de6a035e990d1047ded9eac277e68d69 gcc/tree-phinodes.c --- 56274,56280 ---- 09aeb8e8a96f12d60fd3221cd8bbd33c gcc/tree-object-size.h bfdff86bbeca1fa7f1812fcf614346ef gcc/tree-outof-ssa.c d54568e25cf2ea37efc4fdbdb7cc946a gcc/tree-outof-ssa.h ! 11f2797acba14f8648e4f164d9a9bc4e gcc/tree-parloops.c 7ce5eef33036ddee4a6e8a3acdfd1192 gcc/tree-parloops.h de582deb9950074ca35160a70f2150c3 gcc/tree-pass.h de6a035e990d1047ded9eac277e68d69 gcc/tree-phinodes.c *************** fb39e381bdad8c9f691decc1711611e5 gcc/tr *** 56038,56052 **** b3cec16558bbed1986bfdb30a22d81e4 gcc/tree-predcom.c 1922c9942d592851fe6692b7143b0666 gcc/tree-pretty-print.c 19fc07dfdecf83a88085e472645be0a1 gcc/tree-pretty-print.h ! 99a21e7e99ce428caf4aff51ca2328a3 gcc/tree-profile.c c4a672c5b34898471e4c09cd7d897c6f gcc/tree-scalar-evolution.c ddd74c800272e36b5e04e6b839d5aaf9 gcc/tree-scalar-evolution.h ! fc0f9a64091d8fb69026693b3385fafe gcc/tree-sra.c 5cbd1c07136c29a87b15ca8006f24649 gcc/tree-ssa-address.c 1fb91694b7ea342f3f4755974d570401 gcc/tree-ssa-address.h 630bd55e80d8b02f04bf9979745e5eaa gcc/tree-ssa-alias.c b2112211d28a5a985396b2b827acfd25 gcc/tree-ssa-alias.h ! 43c33de0337c08cb765250c530472147 gcc/tree-ssa-ccp.c 4e0e13ee3807e5c0daad9489f9fd55d2 gcc/tree-ssa-coalesce.c 0a798eb3055ef1b38167cee71723befe gcc/tree-ssa-coalesce.h d655d555dd2ea00da5e0e3cfe76f03a6 gcc/tree-ssa-copy.c --- 56282,56296 ---- b3cec16558bbed1986bfdb30a22d81e4 gcc/tree-predcom.c 1922c9942d592851fe6692b7143b0666 gcc/tree-pretty-print.c 19fc07dfdecf83a88085e472645be0a1 gcc/tree-pretty-print.h ! 1d9b37e5c1d9cc9c241a85b1ac26e10c gcc/tree-profile.c c4a672c5b34898471e4c09cd7d897c6f gcc/tree-scalar-evolution.c ddd74c800272e36b5e04e6b839d5aaf9 gcc/tree-scalar-evolution.h ! 12e0234c05b5307085c95d6a37d41b2d gcc/tree-sra.c 5cbd1c07136c29a87b15ca8006f24649 gcc/tree-ssa-address.c 1fb91694b7ea342f3f4755974d570401 gcc/tree-ssa-address.h 630bd55e80d8b02f04bf9979745e5eaa gcc/tree-ssa-alias.c b2112211d28a5a985396b2b827acfd25 gcc/tree-ssa-alias.h ! 4aed348be779f9598cd4b4839836efa0 gcc/tree-ssa-ccp.c 4e0e13ee3807e5c0daad9489f9fd55d2 gcc/tree-ssa-coalesce.c 0a798eb3055ef1b38167cee71723befe gcc/tree-ssa-coalesce.h d655d555dd2ea00da5e0e3cfe76f03a6 gcc/tree-ssa-copy.c *************** dd17765c129a60e4842f1be570321c8b gcc/tr *** 56061,56073 **** faa2ead260ac7065c87fe77d282b0b7c gcc/tree-ssa-loop-ch.c 46b71bb339fc001411f6ebb8f0e83d65 gcc/tree-ssa-loop-im.c 8a60ce3730dab246e7ea2887c14af307 gcc/tree-ssa-loop-ivcanon.c ! 2fae1f94e6875fcff9135fc620dbe0b9 gcc/tree-ssa-loop-ivopts.c c1c4ac2934bf21e9832bc823cf1959ef gcc/tree-ssa-loop-ivopts.h e2fe3d55c10eecbecf9d0b4742c71cf4 gcc/tree-ssa-loop-manip.c 065575e0362775fbcfda919ac9d6a053 gcc/tree-ssa-loop-manip.h 037e46f901b04e1897e0f5338070fceb gcc/tree-ssa-loop-niter.c e39c11a700556495027cf2594eda607e gcc/tree-ssa-loop-niter.h ! 7206349f9866f4040378a141a4a3fc10 gcc/tree-ssa-loop-prefetch.c cedc12f866ad14c0ce0ff80357554e21 gcc/tree-ssa-loop-unswitch.c 7b56fac467e6a65d335907e274999ddb gcc/tree-ssa-loop.c 4c430ffbb3398e58ddeb42580926a06a gcc/tree-ssa-loop.h --- 56305,56317 ---- faa2ead260ac7065c87fe77d282b0b7c gcc/tree-ssa-loop-ch.c 46b71bb339fc001411f6ebb8f0e83d65 gcc/tree-ssa-loop-im.c 8a60ce3730dab246e7ea2887c14af307 gcc/tree-ssa-loop-ivcanon.c ! eac52ca9a95f6c5d55608c7350f37a89 gcc/tree-ssa-loop-ivopts.c c1c4ac2934bf21e9832bc823cf1959ef gcc/tree-ssa-loop-ivopts.h e2fe3d55c10eecbecf9d0b4742c71cf4 gcc/tree-ssa-loop-manip.c 065575e0362775fbcfda919ac9d6a053 gcc/tree-ssa-loop-manip.h 037e46f901b04e1897e0f5338070fceb gcc/tree-ssa-loop-niter.c e39c11a700556495027cf2594eda607e gcc/tree-ssa-loop-niter.h ! 5d25e098fe6afa1cdcded650233ae15d gcc/tree-ssa-loop-prefetch.c cedc12f866ad14c0ce0ff80357554e21 gcc/tree-ssa-loop-unswitch.c 7b56fac467e6a65d335907e274999ddb gcc/tree-ssa-loop.c 4c430ffbb3398e58ddeb42580926a06a gcc/tree-ssa-loop.h *************** ae2259e78bf92cdab02fb8c53b1f6140 gcc/tr *** 56080,56093 **** 09a99fd7453733a44ad2fc00914f6afe gcc/tree-ssa-pre.c 9f98b6151bf9386ea316e7b2957a3818 gcc/tree-ssa-propagate.c 2c2fdda0693f653ff6694bec50f9c6be gcc/tree-ssa-propagate.h ! 33d8e1cb9a77d4f2092ec76958543645 gcc/tree-ssa-reassoc.c ! 30c77244f7b2c50d404766dfa931aefb gcc/tree-ssa-sccvn.c ! bf9606517975c072a298e6e9648d84fe gcc/tree-ssa-sccvn.h 27f3203e67b17d43acb249774afcce00 gcc/tree-ssa-scopedtables.c faf7ec5d35f4c8016f9e652447e47297 gcc/tree-ssa-scopedtables.h b5d1efde969440d8b72d27d076a0ded2 gcc/tree-ssa-sink.c ! 5ca1b76e4fefc9dd0b6407eef1209e54 gcc/tree-ssa-strlen.c ! 26a4836d2768827341f20974c16b7146 gcc/tree-ssa-structalias.c 7ec3527cf8a88f81f3af7f7b328675a7 gcc/tree-ssa-tail-merge.c c42366aeb341396f5a20199f0a76464f gcc/tree-ssa-ter.c 72d07b4d9955684fab7636c602c4b360 gcc/tree-ssa-ter.h --- 56324,56337 ---- 09a99fd7453733a44ad2fc00914f6afe gcc/tree-ssa-pre.c 9f98b6151bf9386ea316e7b2957a3818 gcc/tree-ssa-propagate.c 2c2fdda0693f653ff6694bec50f9c6be gcc/tree-ssa-propagate.h ! b6b7347f6eba58f7fa05d06f90a737b1 gcc/tree-ssa-reassoc.c ! add8e340ea803ca23edc434674d7a152 gcc/tree-ssa-sccvn.c ! 5605591bb043eb3acc2ef42972e892b4 gcc/tree-ssa-sccvn.h 27f3203e67b17d43acb249774afcce00 gcc/tree-ssa-scopedtables.c faf7ec5d35f4c8016f9e652447e47297 gcc/tree-ssa-scopedtables.h b5d1efde969440d8b72d27d076a0ded2 gcc/tree-ssa-sink.c ! 6c79156a7ea6372a93fd1432f2d73ddd gcc/tree-ssa-strlen.c ! 054c7cdc05de735b2ffa6948e954343a gcc/tree-ssa-structalias.c 7ec3527cf8a88f81f3af7f7b328675a7 gcc/tree-ssa-tail-merge.c c42366aeb341396f5a20199f0a76464f gcc/tree-ssa-ter.c 72d07b4d9955684fab7636c602c4b360 gcc/tree-ssa-ter.h *************** d0ab33f383e86e2785c5c24335c92b6f gcc/tr *** 56111,56117 **** d582f891f95af854317037e4020c5f90 gcc/tree-streamer.h 11bd30d126bfef5e25674bf369287718 gcc/tree-switch-conversion.c 88fc834970e1ba32e98998d7ce7ecf09 gcc/tree-tailcall.c ! 21927caca7d15de3cd5f65fe356b777b gcc/tree-vect-data-refs.c a78063c6f19eea041e35fe5515a935f2 gcc/tree-vect-generic.c 318b8e4c49ce9ec44a055d34b947f5c9 gcc/tree-vect-loop-manip.c 295d03e5d7392b0acca8257dea216f96 gcc/tree-vect-loop.c --- 56355,56361 ---- d582f891f95af854317037e4020c5f90 gcc/tree-streamer.h 11bd30d126bfef5e25674bf369287718 gcc/tree-switch-conversion.c 88fc834970e1ba32e98998d7ce7ecf09 gcc/tree-tailcall.c ! 4bd68b981e5581a718f838ba1718003a gcc/tree-vect-data-refs.c a78063c6f19eea041e35fe5515a935f2 gcc/tree-vect-generic.c 318b8e4c49ce9ec44a055d34b947f5c9 gcc/tree-vect-loop-manip.c 295d03e5d7392b0acca8257dea216f96 gcc/tree-vect-loop.c *************** c2b28b1f389315c73c5ffce684eb42a1 gcc/tr *** 56120,56127 **** ccc4a8cdc6372398435b0e878b4d42f4 gcc/tree-vect-stmts.c 7729076c55712e0bfb562f337107c400 gcc/tree-vectorizer.c 99cdf0e00b25ff01da509c7f6bd7f8fd gcc/tree-vectorizer.h ! 311fb010ad0b307e6566edbcaacfd2b1 gcc/tree-vrp.c ! 3ddcaf335b0abb833cfccdba96dea856 gcc/tree.c 756c1546f4b1318f8d59106e5a786041 gcc/tree.def bf20bed9a2bd5dce0f8065faa99fc392 gcc/tree.h 59d18b65bc8897bea70f8d136681423f gcc/treestruct.def --- 56364,56371 ---- ccc4a8cdc6372398435b0e878b4d42f4 gcc/tree-vect-stmts.c 7729076c55712e0bfb562f337107c400 gcc/tree-vectorizer.c 99cdf0e00b25ff01da509c7f6bd7f8fd gcc/tree-vectorizer.h ! 2b9fcf0301877066c16c1880e896ff8b gcc/tree-vrp.c ! 77898b4b38f55c5830a146a4ea6c0b13 gcc/tree.c 756c1546f4b1318f8d59106e5a786041 gcc/tree.def bf20bed9a2bd5dce0f8065faa99fc392 gcc/tree.h 59d18b65bc8897bea70f8d136681423f gcc/treestruct.def *************** bf20bed9a2bd5dce0f8065faa99fc392 gcc/tr *** 56130,56143 **** 4fcf15c72e56a3360214b87bd3df82de gcc/tsystem.h abc8eba4119c9cb0bc421df5afb01334 gcc/typeclass.h 572fb9b575cab50b68cebce0e6aaab5b gcc/typed-splay-tree.h ! b4bcae7759570afae0d5dbbf648b6e1d gcc/ubsan.c 81e340a3b45094070fa00910435108f6 gcc/ubsan.h 7435de97b351df3a173bb3259cdfa730 gcc/valtrack.c fd43fe3f222442739550a35e7bad2e4f gcc/valtrack.h ! 261cb41f64e1df8a018fa2e22f98ccbf gcc/value-prof.c efdf833ec0d4de1263c1415b9c6b1758 gcc/value-prof.h 0bc8809ddcea64c6729556c6e81c9219 gcc/var-tracking.c ! 19bcb3bc6bbbd6cdc3ab738f42e19f51 gcc/varasm.c 35cdbb24cefe42c073a91a7d447d724a gcc/varasm.h 0ef531dd3789d1d3a025a50fad29f531 gcc/varpool.c 54714a012660a08c8fcf9ae0125540a4 gcc/vec.c --- 56374,56387 ---- 4fcf15c72e56a3360214b87bd3df82de gcc/tsystem.h abc8eba4119c9cb0bc421df5afb01334 gcc/typeclass.h 572fb9b575cab50b68cebce0e6aaab5b gcc/typed-splay-tree.h ! 3699f752ecf8b697be3168df40aac3d1 gcc/ubsan.c 81e340a3b45094070fa00910435108f6 gcc/ubsan.h 7435de97b351df3a173bb3259cdfa730 gcc/valtrack.c fd43fe3f222442739550a35e7bad2e4f gcc/valtrack.h ! 19b44904bef9264b0428f96e3563213d gcc/value-prof.c efdf833ec0d4de1263c1415b9c6b1758 gcc/value-prof.h 0bc8809ddcea64c6729556c6e81c9219 gcc/var-tracking.c ! d4697d1f0f6268949654090bd2b10106 gcc/varasm.c 35cdbb24cefe42c073a91a7d447d724a gcc/varasm.h 0ef531dd3789d1d3a025a50fad29f531 gcc/varpool.c 54714a012660a08c8fcf9ae0125540a4 gcc/vec.c *************** bccd357a7bfd6ee51c8eeb77b6b1d506 gcc/wi *** 56156,56166 **** e2ba6fa556cc8c3fbfab74ce4e426557 gcc/xcoff.h 4bd335ffbdc05ff6f6e2f85ed175ad8c gcc/xcoffout.c a8f1b8316e47fa12c065b76a13942877 gcc/xcoffout.h ! 678f65ae0ee39ac28f5075a09daa4fd2 gnattools/ChangeLog 06f67a6786f98a47b35a47fd6991882f gnattools/Makefile.in 505bc9465c6da8568cd37fe3672cb301 gnattools/configure 7f9d2150e9fcd26fd8537d8b8a8b8f5e gnattools/configure.ac ! 51c527ee44893bd8f00fd3659c088d4a gotools/ChangeLog 1c4ac17f512bc6f166b8b0fd3b2e5ec7 gotools/Makefile.am fb62a0006e185df390bc0ef648c1a6a7 gotools/Makefile.in 7e23031e2e274aaa07b61c1e8f18dc99 gotools/README --- 56400,56410 ---- e2ba6fa556cc8c3fbfab74ce4e426557 gcc/xcoff.h 4bd335ffbdc05ff6f6e2f85ed175ad8c gcc/xcoffout.c a8f1b8316e47fa12c065b76a13942877 gcc/xcoffout.h ! a0af20381b8e4298e30216b05350bac0 gnattools/ChangeLog 06f67a6786f98a47b35a47fd6991882f gnattools/Makefile.in 505bc9465c6da8568cd37fe3672cb301 gnattools/configure 7f9d2150e9fcd26fd8537d8b8a8b8f5e gnattools/configure.ac ! f3cf06e90c195019eca607805ef7c71e gotools/ChangeLog 1c4ac17f512bc6f166b8b0fd3b2e5ec7 gotools/Makefile.am fb62a0006e185df390bc0ef648c1a6a7 gotools/Makefile.in 7e23031e2e274aaa07b61c1e8f18dc99 gotools/README *************** c4e8176c1964a5ebe0a55900f2141299 gotool *** 56172,56178 **** eb2aeb3a6cffe7b26a8f1c8a2da23dcd gotools/gofmt.1 59530bdf33659b29e73d4adb9f9f6552 include/COPYING d32239bcb673463ab874e80d47fae504 include/COPYING3 ! 5a7e1982a9109871a5114a01f1e88194 include/ChangeLog 4263432a72ff47ed8bf420208ee7eea5 include/ChangeLog-9103 a43d76108493b20da790f953f829c6a5 include/ChangeLog.jit 383c798053c894e5961d48cc2bebbe94 include/ansidecl.h --- 56416,56422 ---- eb2aeb3a6cffe7b26a8f1c8a2da23dcd gotools/gofmt.1 59530bdf33659b29e73d4adb9f9f6552 include/COPYING d32239bcb673463ab874e80d47fae504 include/COPYING3 ! 84c55f7f88e7f3f43046eea11744f65e include/ChangeLog 4263432a72ff47ed8bf420208ee7eea5 include/ChangeLog-9103 a43d76108493b20da790f953f829c6a5 include/ChangeLog.jit 383c798053c894e5961d48cc2bebbe94 include/ansidecl.h *************** b8adb11c15033eab2f9d1b24dd363f3c includ *** 56213,56219 **** 98498058721a4a61a9d050d50584fc76 include/xregex2.h 8823a2b4676fef221902b03ddffff179 include/xtensa-config.h 361482dd6b5b5eb7090fff3986fba68a install-sh ! dfea10f6a2d21e00ee30b6993406af9d intl/ChangeLog cad1d6fab2274517783de7433c0faa74 intl/Makefile.in 6ec998bb4716c744bf8185e607f69301 intl/README 76ca170a525d5b84d90f0478fe788931 intl/VERSION --- 56457,56463 ---- 98498058721a4a61a9d050d50584fc76 include/xregex2.h 8823a2b4676fef221902b03ddffff179 include/xtensa-config.h 361482dd6b5b5eb7090fff3986fba68a install-sh ! 1cf48a6bd36e86a6ec05651b7d5f87ac intl/ChangeLog cad1d6fab2274517783de7433c0faa74 intl/Makefile.in 6ec998bb4716c744bf8185e607f69301 intl/README 76ca170a525d5b84d90f0478fe788931 intl/VERSION *************** d50a8c6c5b41089930accbdce767d3c0 intl/p *** 56255,56266 **** b4758a0194e3e41362b939911472ce62 intl/relocatable.c bedade7bcfc3bc5eb09a2c6844f637f3 intl/relocatable.h 43f287d082528203fc85c1d2d81bf30d intl/textdomain.c ! 120f462f674334eadf07d922fc9d11db libada/ChangeLog 02ee29191bf89e9d1bf4d0b5b45536d5 libada/Makefile.in ! 68395a53adb86132c753b865a97f49e5 libada/configure ! dc03104644ef27c11606ab0f4f675f06 libada/configure.ac 46d3fe6da7a771cc2d5420c4137a6861 libatomic/.gitignore ! db94fc594024dbe290a8476417b9f555 libatomic/ChangeLog f7e487a2a8e032a211ad21a5681e4b55 libatomic/Makefile.am 685ebec1fe8aa94deb1729b48bb2fc6c libatomic/Makefile.in f7853b06953072a9987a45a5b00782d6 libatomic/acinclude.m4 --- 56499,56510 ---- b4758a0194e3e41362b939911472ce62 intl/relocatable.c bedade7bcfc3bc5eb09a2c6844f637f3 intl/relocatable.h 43f287d082528203fc85c1d2d81bf30d intl/textdomain.c ! e0c4765e19f6ec258c968a7875f31df9 libada/ChangeLog 02ee29191bf89e9d1bf4d0b5b45536d5 libada/Makefile.in ! 56d60d329afe53cd781920647bf7d00c libada/configure ! 824c881ba0b726aa6855259b8a4cf6de libada/configure.ac 46d3fe6da7a771cc2d5420c4137a6861 libatomic/.gitignore ! 8ac71e5c370fc485ef46840463e1e06f libatomic/ChangeLog f7e487a2a8e032a211ad21a5681e4b55 libatomic/Makefile.am 685ebec1fe8aa94deb1729b48bb2fc6c libatomic/Makefile.in f7853b06953072a9987a45a5b00782d6 libatomic/acinclude.m4 *************** cbeb120f3cb8c120de8a74a3dee23e10 libato *** 56268,56274 **** e143acd5b2c5b05cc850e294c26cb1c6 libatomic/auto-config.h.in 3e0a3b23379049fbf0827a3531fb7da2 libatomic/cas_n.c 861cf48e833d114ea4e52abcfdda6328 libatomic/config/arm/arm-config.h ! 72e3a2f9211782851c8e833827f79ead libatomic/config/arm/exch_n.c 6b272347b6495b829ff036ddf4d65e93 libatomic/config/arm/host-config.h db43cf5a187a91251ef3198570679f95 libatomic/config/ia64/host-config.h 88124d0c3240dcc61609b432f8ce0d7c libatomic/config/linux/arm/host-config.h --- 56512,56518 ---- e143acd5b2c5b05cc850e294c26cb1c6 libatomic/auto-config.h.in 3e0a3b23379049fbf0827a3531fb7da2 libatomic/cas_n.c 861cf48e833d114ea4e52abcfdda6328 libatomic/config/arm/arm-config.h ! bc77367b5bcf5de5ccc0337b6f461b1e libatomic/config/arm/exch_n.c 6b272347b6495b829ff036ddf4d65e93 libatomic/config/arm/host-config.h db43cf5a187a91251ef3198570679f95 libatomic/config/ia64/host-config.h 88124d0c3240dcc61609b432f8ce0d7c libatomic/config/linux/arm/host-config.h *************** c03a072efac9b30f8f8429ac52fd246b libato *** 56344,56350 **** 8a7308fda7ed1543cb9e3be0f8e47bce libatomic/testsuite/libatomic.c/atomic-store-5.c 40618200985a15bcba64f871863da498 libatomic/testsuite/libatomic.c/c.exp 97b0c9cdfcb733664bdf4efe0f5dc449 libatomic/testsuite/libatomic.c/generic-2.c ! 667a98e7fd22b34d370acea82f5fb7f7 libbacktrace/ChangeLog eb3a88b53140eb234a99a4b3a55e56bf libbacktrace/ChangeLog.jit adcff7cabf0971aed26d7fe5e3630a23 libbacktrace/Makefile.am a4bbeef6b43604c1ca251b56c1bc4888 libbacktrace/Makefile.in --- 56588,56594 ---- 8a7308fda7ed1543cb9e3be0f8e47bce libatomic/testsuite/libatomic.c/atomic-store-5.c 40618200985a15bcba64f871863da498 libatomic/testsuite/libatomic.c/c.exp 97b0c9cdfcb733664bdf4efe0f5dc449 libatomic/testsuite/libatomic.c/generic-2.c ! 6568a6b5a5ddabc86f2ae4ca27566a98 libbacktrace/ChangeLog eb3a88b53140eb234a99a4b3a55e56bf libbacktrace/ChangeLog.jit adcff7cabf0971aed26d7fe5e3630a23 libbacktrace/Makefile.am a4bbeef6b43604c1ca251b56c1bc4888 libbacktrace/Makefile.in *************** ca4837bf9a4dd3eac655517890bca832 libbac *** 56376,56382 **** fa0d812b5ed2cf118f0ead5bb8f74ee5 libbacktrace/state.c 9bb42e6db4544b35ec281b4965f6c5a2 libbacktrace/stest.c 3f53712f748a05fcf7b54f6898f1b332 libbacktrace/unknown.c ! 325e23b7e10beba2cd9e80b8fef4c581 libcc1/ChangeLog c5252f48a827111e7b50794d54283864 libcc1/Makefile.am 8b8072253d069b01ea6488d82652deaa libcc1/Makefile.in 5f253fc15bb29a40419f12ce42f92147 libcc1/aclocal.m4 --- 56620,56626 ---- fa0d812b5ed2cf118f0ead5bb8f74ee5 libbacktrace/state.c 9bb42e6db4544b35ec281b4965f6c5a2 libbacktrace/stest.c 3f53712f748a05fcf7b54f6898f1b332 libbacktrace/unknown.c ! 8361c372bd0ae03fc9524e78c76d821d libcc1/ChangeLog c5252f48a827111e7b50794d54283864 libcc1/Makefile.am 8b8072253d069b01ea6488d82652deaa libcc1/Makefile.in 5f253fc15bb29a40419f12ce42f92147 libcc1/aclocal.m4 *************** ec29c212d8342e282234e53f69b3f8e6 libcc1 *** 56399,56405 **** 7b5e3c71c404e08cbe1d3ca92449c0eb libcc1/plugin.cc 595b9a542a8f80367ebbeecbc51b1ac7 libcc1/rpc.hh 14f215429d450a743fce24b101552f3e libcc1/status.hh ! 3ed39e7d4630f50edaf4438da08bd98b libcilkrts/ChangeLog df0ff198f37089171b490f87912f9602 libcilkrts/Makefile.am 71d9f8e3f82862af1e8d523b0ae6a587 libcilkrts/Makefile.in 4a307b1474cad63768b2ae0c183b6259 libcilkrts/README --- 56643,56649 ---- 7b5e3c71c404e08cbe1d3ca92449c0eb libcc1/plugin.cc 595b9a542a8f80367ebbeecbc51b1ac7 libcc1/rpc.hh 14f215429d450a743fce24b101552f3e libcc1/status.hh ! d12e6ca05bad99374f552efaba4646f1 libcilkrts/ChangeLog df0ff198f37089171b490f87912f9602 libcilkrts/Makefile.am 71d9f8e3f82862af1e8d523b0ae6a587 libcilkrts/Makefile.in 4a307b1474cad63768b2ae0c183b6259 libcilkrts/README *************** d4a2c447aba3e1afe4e9522d132a2e62 libcil *** 56507,56513 **** 94c538f9a3100a27649a9dc4d63d1677 libcilkrts/runtime/sysdep.h ffd8820979e88b4845e4b6ae604d2fdf libcilkrts/runtime/worker_mutex.c 9af2df6acad19a2001c2b1f68f5f59be libcilkrts/runtime/worker_mutex.h ! c0f7a07b0254ade6d38f8527b3140410 libcpp/ChangeLog 2bd831b17997584e38305782cebe6948 libcpp/ChangeLog.jit 922fc84f62df47f415a4c0dbf7eb74c2 libcpp/Makefile.in efb9decde4743620252ededfe7310a3d libcpp/aclocal.m4 --- 56751,56757 ---- 94c538f9a3100a27649a9dc4d63d1677 libcilkrts/runtime/sysdep.h ffd8820979e88b4845e4b6ae604d2fdf libcilkrts/runtime/worker_mutex.c 9af2df6acad19a2001c2b1f68f5f59be libcilkrts/runtime/worker_mutex.h ! 8d52c5f6d1e8c922001e6bd4d124ccb2 libcpp/ChangeLog 2bd831b17997584e38305782cebe6948 libcpp/ChangeLog.jit 922fc84f62df47f415a4c0dbf7eb74c2 libcpp/Makefile.in efb9decde4743620252ededfe7310a3d libcpp/aclocal.m4 *************** eba197e195fb1c007bf0724c8bed75ea libcpp *** 56535,56541 **** 8b169f1ea64fbdcd4eb3b28cc2a20e5d libcpp/makeucnid.c 13e85e048fd80372c5ee39c177ccda58 libcpp/mkdeps.c 2037cc2be924ca9b3d6dcf813bb1f5a5 libcpp/pch.c ! 99f505bddebbe8fd65f015c594087d38 libcpp/po/ChangeLog 6726e6c3f9ce8f080e427162df21cb85 libcpp/po/be.gmo 2ef89459bd607154106cddd9d5643379 libcpp/po/be.po a651af6fb7773350687b1c74bab26997 libcpp/po/ca.gmo --- 56779,56785 ---- 8b169f1ea64fbdcd4eb3b28cc2a20e5d libcpp/makeucnid.c 13e85e048fd80372c5ee39c177ccda58 libcpp/mkdeps.c 2037cc2be924ca9b3d6dcf813bb1f5a5 libcpp/pch.c ! e70768a8387763d944393acd9e26dea2 libcpp/po/ChangeLog 6726e6c3f9ce8f080e427162df21cb85 libcpp/po/be.gmo 2ef89459bd607154106cddd9d5643379 libcpp/po/be.po a651af6fb7773350687b1c74bab26997 libcpp/po/ca.gmo *************** f4fb93166f911a7496d4dd7cd1e57f8c libcpp *** 56585,56591 **** e42c4d6de56e2f1801ed2ace053c722d libcpp/ucnid.h 0a665ca1ee3db23a232526a3286c8374 libcpp/ucnid.tab a6c2b3de06c7424706b16f4c206396a1 libdecnumber/.gitignore ! f5acc130873496145e23024717437d94 libdecnumber/ChangeLog 2bd831b17997584e38305782cebe6948 libdecnumber/ChangeLog.jit be602f033bcd69fb23d0341b8913357e libdecnumber/Makefile.in b9ab907f769f0664ed31991a9c9bf3bb libdecnumber/aclocal.m4 --- 56829,56835 ---- e42c4d6de56e2f1801ed2ace053c722d libcpp/ucnid.h 0a665ca1ee3db23a232526a3286c8374 libcpp/ucnid.tab a6c2b3de06c7424706b16f4c206396a1 libdecnumber/.gitignore ! b942b13c5ac99b80fa4f00d276e66e06 libdecnumber/ChangeLog 2bd831b17997584e38305782cebe6948 libdecnumber/ChangeLog.jit be602f033bcd69fb23d0341b8913357e libdecnumber/Makefile.in b9ab907f769f0664ed31991a9c9bf3bb libdecnumber/aclocal.m4 *************** a97c47969dfc92a7666dfe3c2e1e1448 libdec *** 56648,56654 **** 1b8d5bd512629f5b4d1895fe4dd2c645 libdecnumber/dpd/decimal64.c 33e09faa8cbe6117509446874a776fc6 libdecnumber/dpd/decimal64.h 0f6db29710e7075c2fd62bc4478b3b8d libdecnumber/dpd/decimal64Symbols.h ! 74b8631bd8feaf941dd7e40a69d159d8 libffi/ChangeLog ba66fc19311348d373ec271be939a659 libffi/ChangeLog.libffi fbbc216bc25d759a72ea3e6d734af56b libffi/ChangeLog.libgcj d946d2b97454ad50a1dbfbf48923c5be libffi/ChangeLog.v1 --- 56892,56898 ---- 1b8d5bd512629f5b4d1895fe4dd2c645 libdecnumber/dpd/decimal64.c 33e09faa8cbe6117509446874a776fc6 libdecnumber/dpd/decimal64.h 0f6db29710e7075c2fd62bc4478b3b8d libdecnumber/dpd/decimal64Symbols.h ! 29226d9c29eb3142b39cc608d6417a63 libffi/ChangeLog ba66fc19311348d373ec271be939a659 libffi/ChangeLog.libffi fbbc216bc25d759a72ea3e6d734af56b libffi/ChangeLog.libgcj d946d2b97454ad50a1dbfbf48923c5be libffi/ChangeLog.v1 *************** e0338ba1ce12fd810fe35fed3a694725 libffi *** 56661,56667 **** 60bcb183fb531852628fcecb1ea6ed66 libffi/configure c9655a9cea2ec7adcdd5ca72cb247b90 libffi/configure.ac 84d2d9f2ebfac28a1697db5dc956a25b libffi/configure.host ! 06de21005f93a51347da09be8022b83b libffi/doc/libffi.info cfec4a5a1bb5d36550e15ac051c14148 libffi/doc/libffi.texi 2969ffc23f66d73392207633f25ab252 libffi/doc/version.texi 22b7acb3b27a7bc2c6d5e436e1944367 libffi/fficonfig.h.in --- 56905,56911 ---- 60bcb183fb531852628fcecb1ea6ed66 libffi/configure c9655a9cea2ec7adcdd5ca72cb247b90 libffi/configure.ac 84d2d9f2ebfac28a1697db5dc956a25b libffi/configure.host ! c12cbcc11aa52d4fb53c5f2ca6db8056 libffi/doc/libffi.info cfec4a5a1bb5d36550e15ac051c14148 libffi/doc/libffi.texi 2969ffc23f66d73392207633f25ab252 libffi/doc/version.texi 22b7acb3b27a7bc2c6d5e436e1944367 libffi/fficonfig.h.in *************** d47c79b281339983862a8e52d8c73f0f libffi *** 57006,57014 **** 291be426192f460f6a07dfe1c96ab094 libffi/testsuite/libffi.special/special.exp 93fc3ea311b79f64004992807ce75d1e libffi/testsuite/libffi.special/unwindtest.cc 185d0795017fbbe253a13db8e34085f9 libffi/testsuite/libffi.special/unwindtest_ffi_call.cc ! df41e953c2db9bc8463d004904d145f6 libgcc/ChangeLog d35f709a03da6e07d660c91956551a36 libgcc/Makefile.in ! e413fcbd3fcf1c55448dfe5e41381362 libgcc/config.host 3b9d11b9f405d47c079d725f2f16271e libgcc/config.in c1dd89f96f28e8843a51c0c7b560c6c7 libgcc/config/aarch64/crtfastmath.c 9dca9ad5de19b368a1b3ec83a660a34f libgcc/config/aarch64/crti.S --- 57250,57258 ---- 291be426192f460f6a07dfe1c96ab094 libffi/testsuite/libffi.special/special.exp 93fc3ea311b79f64004992807ce75d1e libffi/testsuite/libffi.special/unwindtest.cc 185d0795017fbbe253a13db8e34085f9 libffi/testsuite/libffi.special/unwindtest_ffi_call.cc ! 05d4a6b846a10b70d0f592c2a02840e1 libgcc/ChangeLog d35f709a03da6e07d660c91956551a36 libgcc/Makefile.in ! ddba3b1969d0e48c1b4a5f25139a58f0 libgcc/config.host 3b9d11b9f405d47c079d725f2f16271e libgcc/config.in c1dd89f96f28e8843a51c0c7b560c6c7 libgcc/config/aarch64/crtfastmath.c 9dca9ad5de19b368a1b3ec83a660a34f libgcc/config/aarch64/crti.S *************** a0a46a9affff177d894176604c30c40d libgcc *** 57023,57029 **** 00a63bcff52dd6af2601ce33f1214245 libgcc/config/alpha/libgcc-alpha-ldbl.ver 33596e8e4cfa811798555b6a97f2c3de libgcc/config/alpha/linux-unwind.h 64530bc923625cddb1e552e736157738 libgcc/config/alpha/qrnnd.S ! c45798ce39178e619ff48bf689b549be libgcc/config/alpha/t-alpha 95db551210150c5b18529c72cfdaeabf libgcc/config/alpha/t-ieee 70f7baadf7c58b1adae96daa38a6843f libgcc/config/alpha/t-linux 600b5cfe4987de3985ad1ff7316166cc libgcc/config/alpha/t-vms --- 57267,57273 ---- 00a63bcff52dd6af2601ce33f1214245 libgcc/config/alpha/libgcc-alpha-ldbl.ver 33596e8e4cfa811798555b6a97f2c3de libgcc/config/alpha/linux-unwind.h 64530bc923625cddb1e552e736157738 libgcc/config/alpha/qrnnd.S ! e06033e6f9902c9e703e237d511df6c4 libgcc/config/alpha/t-alpha 95db551210150c5b18529c72cfdaeabf libgcc/config/alpha/t-ieee 70f7baadf7c58b1adae96daa38a6843f libgcc/config/alpha/t-linux 600b5cfe4987de3985ad1ff7316166cc libgcc/config/alpha/t-vms *************** f1b505a32bcf62e674988eec0748c12b libgcc *** 57125,57132 **** fc87e45e073829d21e9427a38f435e3b libgcc/config/arm/t-symbian 0b61332cccc4af9b144b6db99e213dcb libgcc/config/arm/t-wince-pe 9a6b0c88f24964a109dff9004fb4fc88 libgcc/config/arm/unaligned-funcs.c ! 2d22cfa21cea492c1c6eee214ba7c2ec libgcc/config/arm/unwind-arm.c ! ff48c7ffc7b94fae725c79e56141c484 libgcc/config/arm/unwind-arm.h da5bbbfa5ef487bd7b56de9bc2fc0c13 libgcc/config/avr/avr-lib.h 33c688404b0a5845a3b44c84763710b9 libgcc/config/avr/lib1funcs-fixed.S 47f1bc30d6b146f6a008d0d94b198dfb libgcc/config/avr/lib1funcs.S --- 57369,57376 ---- fc87e45e073829d21e9427a38f435e3b libgcc/config/arm/t-symbian 0b61332cccc4af9b144b6db99e213dcb libgcc/config/arm/t-wince-pe 9a6b0c88f24964a109dff9004fb4fc88 libgcc/config/arm/unaligned-funcs.c ! bb626043297183e90e9124e224055fd3 libgcc/config/arm/unwind-arm.c ! 5e1bec96724ed88a4aff7ddc474f2e01 libgcc/config/arm/unwind-arm.h da5bbbfa5ef487bd7b56de9bc2fc0c13 libgcc/config/avr/avr-lib.h 33c688404b0a5845a3b44c84763710b9 libgcc/config/avr/lib1funcs-fixed.S 47f1bc30d6b146f6a008d0d94b198dfb libgcc/config/avr/lib1funcs.S *************** a853117f36a011bda408de79e30cf6dc libgcc *** 57361,57367 **** 5331d793e0ecd9208ce6f18cc3038dd3 libgcc/config/ia64/vms-unwind.h 468f59c2ac7f40b9460dc2ca6fb5ba75 libgcc/config/iq2000/lib2funcs.c 102f7dad8ad6b54434a1b8313d1e42c4 libgcc/config/iq2000/t-iq2000 ! 22f93a781a1acf462275f4dbd50f4493 libgcc/config/libbid/ChangeLog 71e401fe076997afe9d1a55f854029d9 libgcc/config/libbid/_addsub_dd.c 7435567b97fdc341a31732fba8e5990a libgcc/config/libbid/_addsub_sd.c b4b1e29d6fdc4dd4f10a985f903973b8 libgcc/config/libbid/_addsub_td.c --- 57605,57611 ---- 5331d793e0ecd9208ce6f18cc3038dd3 libgcc/config/ia64/vms-unwind.h 468f59c2ac7f40b9460dc2ca6fb5ba75 libgcc/config/iq2000/lib2funcs.c 102f7dad8ad6b54434a1b8313d1e42c4 libgcc/config/iq2000/t-iq2000 ! 4b336e5187f5e3e03523142cf0b409ad libgcc/config/libbid/ChangeLog 71e401fe076997afe9d1a55f854029d9 libgcc/config/libbid/_addsub_dd.c 7435567b97fdc341a31732fba8e5990a libgcc/config/libbid/_addsub_sd.c b4b1e29d6fdc4dd4f10a985f903973b8 libgcc/config/libbid/_addsub_td.c *************** aba354b12ccddf23281f544a4b3c446a libgcc *** 58004,58010 **** 692f688b65e81676c6fe126268165355 libgcc/config/rs6000/sol-ci.S a9c26737d9a7040c6b05404eda7b585d libgcc/config/rs6000/sol-cn.S 8e65197842ba39fd658038728475e572 libgcc/config/rs6000/t-aix-cxa ! fb6501d77928a3ea4f485c0f80eedf94 libgcc/config/rs6000/t-crtstuff fbf232aa523ca2f4bcf139e827eba2da libgcc/config/rs6000/t-darwin d7cdc73d7a8e658f872ea07474837bc2 libgcc/config/rs6000/t-darwin64 f809b3f51cd4c6b7b1b2a01f98f5917a libgcc/config/rs6000/t-e500v1-fp --- 58248,58254 ---- 692f688b65e81676c6fe126268165355 libgcc/config/rs6000/sol-ci.S a9c26737d9a7040c6b05404eda7b585d libgcc/config/rs6000/sol-cn.S 8e65197842ba39fd658038728475e572 libgcc/config/rs6000/t-aix-cxa ! 3c3fc29e8ce89e9bbebf4cfbd71a6b54 libgcc/config/rs6000/t-crtstuff fbf232aa523ca2f4bcf139e827eba2da libgcc/config/rs6000/t-darwin d7cdc73d7a8e658f872ea07474837bc2 libgcc/config/rs6000/t-darwin64 f809b3f51cd4c6b7b1b2a01f98f5917a libgcc/config/rs6000/t-e500v1-fp *************** e2c566123abbfcacdcf4d215a96f33c0 libgcc *** 58070,58076 **** d12e3dfd4476c276710b632a6f75304b libgcc/config/sparc/crtfastmath.c b8aecb8d125e2edefc61a1680d86abbe libgcc/config/sparc/crti.S 52f026c158895079984f85dd11618f7d libgcc/config/sparc/crtn.S ! 38890399560283d3053d6c66c5bfb517 libgcc/config/sparc/lb1spc.S 41be874e4b0dc2607d5f634b433a2e15 libgcc/config/sparc/libgcc-glibc.ver 06df54b859d38efa44cd8bf6ddb70d68 libgcc/config/sparc/linux-unwind.h c4db4083f474215686defd9d5dcfabf6 libgcc/config/sparc/sol2-c1.S --- 58314,58320 ---- d12e3dfd4476c276710b632a6f75304b libgcc/config/sparc/crtfastmath.c b8aecb8d125e2edefc61a1680d86abbe libgcc/config/sparc/crti.S 52f026c158895079984f85dd11618f7d libgcc/config/sparc/crtn.S ! b2a26791cd6002e4af29a7fa32510b3b libgcc/config/sparc/lb1spc.S 41be874e4b0dc2607d5f634b433a2e15 libgcc/config/sparc/libgcc-glibc.ver 06df54b859d38efa44cd8bf6ddb70d68 libgcc/config/sparc/linux-unwind.h c4db4083f474215686defd9d5dcfabf6 libgcc/config/sparc/sol2-c1.S *************** bca10713facd662410b2fb7994c82c17 libgcc *** 58194,58202 **** 973545127cc1fd16622e83cb2292c39d libgcc/config/xtensa/lib2funcs.S 8074695f5eea7b961c59ee9608973dac libgcc/config/xtensa/libgcc-glibc.ver 2755ee3c07a856dec2587e0f4dbc03d8 libgcc/config/xtensa/linux-unwind.h ! abaf6fc399453837c4d7bb2c36921c93 libgcc/config/xtensa/t-elf ! 726bfd6509f7943384215f04c9cf18a6 libgcc/config/xtensa/t-linux ! 2b2ae5e7326f0f8fdbe2bc9c17aa2494 libgcc/config/xtensa/t-windowed bf2471ce5bf90eaf3dd7074026fd33f5 libgcc/config/xtensa/t-xtensa 7da933432a6e52d1efc862332d430b9a libgcc/config/xtensa/unwind-dw2-xtensa.c 72278c0b1c231226f54fbb3722cedd3a libgcc/config/xtensa/unwind-dw2-xtensa.h --- 58438,58446 ---- 973545127cc1fd16622e83cb2292c39d libgcc/config/xtensa/lib2funcs.S 8074695f5eea7b961c59ee9608973dac libgcc/config/xtensa/libgcc-glibc.ver 2755ee3c07a856dec2587e0f4dbc03d8 libgcc/config/xtensa/linux-unwind.h ! d437dc5394da39dbe1ece64723e90a76 libgcc/config/xtensa/t-elf ! 4f2c91d0f57a675cc91b287ce2ad76aa libgcc/config/xtensa/t-linux ! ce614fa17d52c2d7121d7e2d6f80b02d libgcc/config/xtensa/t-windowed bf2471ce5bf90eaf3dd7074026fd33f5 libgcc/config/xtensa/t-xtensa 7da933432a6e52d1efc862332d430b9a libgcc/config/xtensa/unwind-dw2-xtensa.c 72278c0b1c231226f54fbb3722cedd3a libgcc/config/xtensa/unwind-dw2-xtensa.h *************** c1944db3272244cdfc3f4ffb9bd512e8 libgcc *** 58233,58239 **** 6b3d9a5c3693210ac72b3b361eddfdd1 libgcc/libgcc2.c 5185d0ee7180cb24784d1078584fbba4 libgcc/libgcc2.h f37ecfd97aced2b3b20a5cfab3934d37 libgcc/libgcov-driver-system.c ! 59613f1b0b973eb66080c92ad374872e libgcc/libgcov-driver.c 6cbf2f27836896baeee2fb5a89b36899 libgcc/libgcov-interface.c 2277149f23c77b66f0c372e7a7966f9f libgcc/libgcov-merge.c 57ad7c4ffa8e9a152c36142780c62816 libgcc/libgcov-profiler.c --- 58477,58483 ---- 6b3d9a5c3693210ac72b3b361eddfdd1 libgcc/libgcc2.c 5185d0ee7180cb24784d1078584fbba4 libgcc/libgcc2.h f37ecfd97aced2b3b20a5cfab3934d37 libgcc/libgcov-driver-system.c ! bf920f8c4b7c88fcf81d0d2b69ada9d0 libgcc/libgcov-driver.c 6cbf2f27836896baeee2fb5a89b36899 libgcc/libgcov-interface.c 2277149f23c77b66f0c372e7a7966f9f libgcc/libgcov-merge.c 57ad7c4ffa8e9a152c36142780c62816 libgcc/libgcov-profiler.c *************** c99b4b0797edf0de059bb4c01d1ad353 libgcc *** 58354,58360 **** 313b45ca7b9607eea7d19c449385d0a8 libgcc/vtv_end_preinit.c 7019557448f9060d5f347506b082def5 libgcc/vtv_start.c a3cf7192e94b8b4be04fad2b2eab3b65 libgcc/vtv_start_preinit.c ! ed596d20237abf8b9bdb773af3b8722f libgfortran/ChangeLog 9aca36338382e5b4b730e7779170b24d libgfortran/ChangeLog-2002 80d3edc880c2da0b7a2beec2e2c4f774 libgfortran/ChangeLog-2003 9f0239429993a5e64ed793eb6c55a5c1 libgfortran/ChangeLog-2004 --- 58598,58604 ---- 313b45ca7b9607eea7d19c449385d0a8 libgcc/vtv_end_preinit.c 7019557448f9060d5f347506b082def5 libgcc/vtv_start.c a3cf7192e94b8b4be04fad2b2eab3b65 libgcc/vtv_start_preinit.c ! 5a3f8c029524ab93a4690902e341a432 libgfortran/ChangeLog 9aca36338382e5b4b730e7779170b24d libgfortran/ChangeLog-2002 80d3edc880c2da0b7a2beec2e2c4f774 libgfortran/ChangeLog-2003 9f0239429993a5e64ed793eb6c55a5c1 libgfortran/ChangeLog-2004 *************** f565223da2dcb17328986889fbb15fa8 libgfo *** 58371,58391 **** 9e2925d753b1ba53f0dc0754d82741eb libgfortran/ChangeLog-2015 eb1faa67789d5284034097ac89b5a40d libgfortran/Makefile.am c34d59ac5dd6621be51f39b89fd1ec4c libgfortran/Makefile.in ! 3fb15c7486b06f10d7bd26eab852ac52 libgfortran/acinclude.m4 46fb3fd580a3c5df6b65f32947897d14 libgfortran/aclocal.m4 ! 2281fad52e5461c7bdce44191b37448b libgfortran/c99_protos.h 5edcb3893e56100ff91fa0580135f4de libgfortran/caf/libcaf.h 307931a253a106160cdca5698a0bb02d libgfortran/caf/mpi.c ! ab1a7d850911f20e36ab1df7ba83c128 libgfortran/caf/single.c d8aeb34f383344a51b38aca66d489e8e libgfortran/config.h.in 717966586685a9c0c5a32ea5e5c1955c libgfortran/config/fpu-387.h 2e7d9110fc8d56b43298fb97aa4f994d libgfortran/config/fpu-aix.h 0358de5fc932c8d470777fe6f881f2bd libgfortran/config/fpu-generic.h e43dd5a2728003132b765da26c666f00 libgfortran/config/fpu-glibc.h 671fbc72fb5ec17a642a4deba1a197f3 libgfortran/config/fpu-sysv.h ! 270ae013432e8045c779107c97369e8c libgfortran/configure ! 97e0431b826ba607687a2d6314ee50e8 libgfortran/configure.ac ! 65b58c656241792c97593a6fdc9cad9b libgfortran/configure.host d0912afa72afb61999ef3636fd924a2e libgfortran/generated/_abs_c10.F90 09e37c544e0be88e9966d70d201b0e62 libgfortran/generated/_abs_c16.F90 c2321407567829a000ee2e61e995738f libgfortran/generated/_abs_c4.F90 --- 58615,58635 ---- 9e2925d753b1ba53f0dc0754d82741eb libgfortran/ChangeLog-2015 eb1faa67789d5284034097ac89b5a40d libgfortran/Makefile.am c34d59ac5dd6621be51f39b89fd1ec4c libgfortran/Makefile.in ! 8146f254ccc11ca057d7d6ca207ebdbd libgfortran/acinclude.m4 46fb3fd580a3c5df6b65f32947897d14 libgfortran/aclocal.m4 ! aa65f674b1cf67402598a7b4fb65afe5 libgfortran/c99_protos.h 5edcb3893e56100ff91fa0580135f4de libgfortran/caf/libcaf.h 307931a253a106160cdca5698a0bb02d libgfortran/caf/mpi.c ! 40e496127783a843321f93ca731d699f libgfortran/caf/single.c d8aeb34f383344a51b38aca66d489e8e libgfortran/config.h.in 717966586685a9c0c5a32ea5e5c1955c libgfortran/config/fpu-387.h 2e7d9110fc8d56b43298fb97aa4f994d libgfortran/config/fpu-aix.h 0358de5fc932c8d470777fe6f881f2bd libgfortran/config/fpu-generic.h e43dd5a2728003132b765da26c666f00 libgfortran/config/fpu-glibc.h 671fbc72fb5ec17a642a4deba1a197f3 libgfortran/config/fpu-sysv.h ! a6af9bdadc62f0495e4c79c88cabdc6d libgfortran/configure ! a1acea3c2b4930ff9ca905826b042208 libgfortran/configure.ac ! 26d3d2f20028a910fbd80fc9c770806a libgfortran/configure.host d0912afa72afb61999ef3636fd924a2e libgfortran/generated/_abs_c10.F90 09e37c544e0be88e9966d70d201b0e62 libgfortran/generated/_abs_c16.F90 c2321407567829a000ee2e61e995738f libgfortran/generated/_abs_c4.F90 *************** cd20c3f8e69e490defe7f3005458a11e libgfo *** 58912,58918 **** 0f344f815222817776ac86e350b606e5 libgfortran/intrinsics/args.c 03225046e21a22bd5a6e3aa3cc4ba66e libgfortran/intrinsics/associated.c fa05502649a4b6649affaca89aeb6b3b libgfortran/intrinsics/bit_intrinsics.c ! e70e0a78f551e21f2f508737a971a30f libgfortran/intrinsics/c99_functions.c d589d42199660fd54ddaf1338e1e7bc6 libgfortran/intrinsics/chdir.c b4e201d1b59b030335b0f1e59fb45ce0 libgfortran/intrinsics/chmod.c 28b0cfd3ceb35eb08226d06957bc39ca libgfortran/intrinsics/clock.c --- 59156,59162 ---- 0f344f815222817776ac86e350b606e5 libgfortran/intrinsics/args.c 03225046e21a22bd5a6e3aa3cc4ba66e libgfortran/intrinsics/associated.c fa05502649a4b6649affaca89aeb6b3b libgfortran/intrinsics/bit_intrinsics.c ! 0028a2e1f27e64c024f4ca78b738b6ca libgfortran/intrinsics/c99_functions.c d589d42199660fd54ddaf1338e1e7bc6 libgfortran/intrinsics/chdir.c b4e201d1b59b030335b0f1e59fb45ce0 libgfortran/intrinsics/chmod.c 28b0cfd3ceb35eb08226d06957bc39ca libgfortran/intrinsics/clock.c *************** be3d538ac827d9e59677861a605b6bc0 libgfo *** 58996,59002 **** 592d87d80c7c219641176896833b2dd3 libgfortran/io/write.c 654f9fc8b73b41afe9dae45c5027c2ed libgfortran/io/write_float.def 4db360a6ad2bc360416cace6583dbddc libgfortran/kinds-override.h ! cfcfe9bfcf3e119fe47b07b61cfd60de libgfortran/libgfortran.h 2527bb19b82f08b34038b07b172d029d libgfortran/libgfortran.spec.in 25a776e70521ce48fb1bfdd7bfa1a646 libgfortran/libtool-version 2ca8f4e405f5c89bb87ebc1a38beb573 libgfortran/m4/all.m4 --- 59240,59246 ---- 592d87d80c7c219641176896833b2dd3 libgfortran/io/write.c 654f9fc8b73b41afe9dae45c5027c2ed libgfortran/io/write_float.def 4db360a6ad2bc360416cace6583dbddc libgfortran/kinds-override.h ! 4a3e45e593b46b04a992ddd18052aac3 libgfortran/libgfortran.h 2527bb19b82f08b34038b07b172d029d libgfortran/libgfortran.spec.in 25a776e70521ce48fb1bfdd7bfa1a646 libgfortran/libtool-version 2ca8f4e405f5c89bb87ebc1a38beb573 libgfortran/m4/all.m4 *************** f81db480cbfdc2b1d2291623c6cadb5f libgfo *** 59054,59060 **** 5d811a52f28106ce1c6e140f21048672 libgfortran/runtime/bounds.c 2d19197aae1d9cb1d79b73b641d28f91 libgfortran/runtime/compile_options.c 5ee5fa0e4b8e97c9777b093015e9a5ef libgfortran/runtime/convert_char.c ! de651050282f9d707b1dd044a9a75e4b libgfortran/runtime/environ.c b7a6a9bc7a0f7d55d4780af2b4be100b libgfortran/runtime/error.c 46b54eba3476a368e2db7e15bc034b01 libgfortran/runtime/fpu.c a958416b9abeeb972142197d67e3120b libgfortran/runtime/in_pack_generic.c --- 59298,59304 ---- 5d811a52f28106ce1c6e140f21048672 libgfortran/runtime/bounds.c 2d19197aae1d9cb1d79b73b641d28f91 libgfortran/runtime/compile_options.c 5ee5fa0e4b8e97c9777b093015e9a5ef libgfortran/runtime/convert_char.c ! 5fcc8b4b692bacb985a4ebd4b26685e7 libgfortran/runtime/environ.c b7a6a9bc7a0f7d55d4780af2b4be100b libgfortran/runtime/error.c 46b54eba3476a368e2db7e15bc034b01 libgfortran/runtime/fpu.c a958416b9abeeb972142197d67e3120b libgfortran/runtime/in_pack_generic.c *************** cb6b39f4a5519cd6f4af2f01f73ac617 libgo/ *** 61180,61186 **** 25666ff283df253ea6fe347037fc3ca8 libgo/runtime/go-typedesc-equal.c af5de48480273b6c892b00fc4277850a libgo/runtime/go-unsafe-new.c c4204400dda158eedfe16fcf9ddb2c71 libgo/runtime/go-unsafe-newarray.c ! 41881358737ae25a15250d1ae8ba86e5 libgo/runtime/go-unsafe-pointer.c a5595b6c7e2c1b845f8deb95af12f9a1 libgo/runtime/go-unsetenv.c d044f8850189eec00d2495830fbdd406 libgo/runtime/go-unwind.c cb972270ceb03f7fa39a2833ad2ef549 libgo/runtime/go-varargs.c --- 61424,61430 ---- 25666ff283df253ea6fe347037fc3ca8 libgo/runtime/go-typedesc-equal.c af5de48480273b6c892b00fc4277850a libgo/runtime/go-unsafe-new.c c4204400dda158eedfe16fcf9ddb2c71 libgo/runtime/go-unsafe-newarray.c ! f0eace9118703d35885141c7142bec5a libgo/runtime/go-unsafe-pointer.c a5595b6c7e2c1b845f8deb95af12f9a1 libgo/runtime/go-unsetenv.c d044f8850189eec00d2495830fbdd406 libgo/runtime/go-unwind.c cb972270ceb03f7fa39a2833ad2ef549 libgo/runtime/go-varargs.c *************** e4cf1605e531aad702667e48a08a4699 libgo/ *** 61210,61223 **** ec19dced922e915debe68f6f0cf6cf53 libgo/runtime/netpoll_select.c 84769ca25a40acf346e9b6bf704472f5 libgo/runtime/netpoll_stub.c 2b35f784267f741fb0008b336043643c libgo/runtime/panic.c ! e24a25558c3092a64b02619a3b32d01b libgo/runtime/parfor.c 2b67bae32fdbea99fb8faed3fb77b3dd libgo/runtime/print.c 1f693b2e4758a5548477934605ef690c libgo/runtime/proc.c 1f482dc4fcfc80d52995202c8eb4a52f libgo/runtime/rdebug.goc 4f0100df73bb1a65bcbc38f9b47cd748 libgo/runtime/reflect.goc 88236bd9baaae0e22c2fe3c097d9cfbf libgo/runtime/rtems-task-variable-add.c a0365ea080367e0af05f65031295af5c libgo/runtime/runtime.c ! 8323e5141b58baed3057daad09ac3a36 libgo/runtime/runtime.h 5643b4259a4567ef0ddd037315056280 libgo/runtime/runtime1.goc b55d0a0a062a05a2f5fa60facf06dfce libgo/runtime/sema.goc b90041786bbfa0dc568ac8db483c704e libgo/runtime/signal_unix.c --- 61454,61467 ---- ec19dced922e915debe68f6f0cf6cf53 libgo/runtime/netpoll_select.c 84769ca25a40acf346e9b6bf704472f5 libgo/runtime/netpoll_stub.c 2b35f784267f741fb0008b336043643c libgo/runtime/panic.c ! f420f44cd0a23b01dee8fad8dd079222 libgo/runtime/parfor.c 2b67bae32fdbea99fb8faed3fb77b3dd libgo/runtime/print.c 1f693b2e4758a5548477934605ef690c libgo/runtime/proc.c 1f482dc4fcfc80d52995202c8eb4a52f libgo/runtime/rdebug.goc 4f0100df73bb1a65bcbc38f9b47cd748 libgo/runtime/reflect.goc 88236bd9baaae0e22c2fe3c097d9cfbf libgo/runtime/rtems-task-variable-add.c a0365ea080367e0af05f65031295af5c libgo/runtime/runtime.c ! e4b4f52838af37845463114408863aeb libgo/runtime/runtime.h 5643b4259a4567ef0ddd037315056280 libgo/runtime/runtime1.goc b55d0a0a062a05a2f5fa60facf06dfce libgo/runtime/sema.goc b90041786bbfa0dc568ac8db483c704e libgo/runtime/signal_unix.c *************** cc55bc35b5b2bd7f5ca14fe722411128 libgo/ *** 61235,61241 **** 1526040f769ea611af781d4ed150f258 libgo/testsuite/gotest ead4e721beb57b319fcd7da8ddf10705 libgo/testsuite/lib/libgo.exp 6df485581d2f02246f41b5ca46f5bb5d libgo/testsuite/libgo.testmain/testmain.exp ! bdb9d59d2a06c37b9a7a7a659865457b libgomp/ChangeLog 0d55aa862aee66efdc5f8d62c94ff8fb libgomp/ChangeLog.graphite 255738c9562136c311d799ad06684be1 libgomp/Makefile.am a97552ea29bea4babb0d125f47fbc5f9 libgomp/Makefile.in --- 61479,61485 ---- 1526040f769ea611af781d4ed150f258 libgo/testsuite/gotest ead4e721beb57b319fcd7da8ddf10705 libgo/testsuite/lib/libgo.exp 6df485581d2f02246f41b5ca46f5bb5d libgo/testsuite/libgo.testmain/testmain.exp ! fa173824dc3ad162b3209f6eaf61d344 libgomp/ChangeLog 0d55aa862aee66efdc5f8d62c94ff8fb libgomp/ChangeLog.graphite 255738c9562136c311d799ad06684be1 libgomp/Makefile.am a97552ea29bea4babb0d125f47fbc5f9 libgomp/Makefile.in *************** d897ac758705911cd44613b6795ec1b6 libgom *** 61247,61253 **** 7a8e29e7711e60c55e1561d73e919cde libgomp/config/bsd/proc.c e99b1870c43707740718637072546464 libgomp/config/darwin/plugin-suffix.h 07691519d21be9fac037be6350ac32da libgomp/config/hpux/plugin-suffix.h ! 5fa8527a7cdd12080974b1c626c93d2d libgomp/config/linux/affinity.c 4a404410b28d68765390726f937fe193 libgomp/config/linux/alpha/futex.h 130151db19dc15c7353382648aae3371 libgomp/config/linux/bar.c 131b6b56ad2928d9f51ccdf5e35c23dd libgomp/config/linux/bar.h --- 61491,61497 ---- 7a8e29e7711e60c55e1561d73e919cde libgomp/config/bsd/proc.c e99b1870c43707740718637072546464 libgomp/config/darwin/plugin-suffix.h 07691519d21be9fac037be6350ac32da libgomp/config/hpux/plugin-suffix.h ! f006a3caa5b379366b0f70b49476673a libgomp/config/linux/affinity.c 4a404410b28d68765390726f937fe193 libgomp/config/linux/alpha/futex.h 130151db19dc15c7353382648aae3371 libgomp/config/linux/bar.c 131b6b56ad2928d9f51ccdf5e35c23dd libgomp/config/linux/bar.h *************** c421f01cf2ccff2e28808e9d9ef62e4b libgom *** 61339,61345 **** 845aba989905c7c6806400c6113e03b3 libgomp/configure.ac 2a5380316834e607859cc29c247eb9e7 libgomp/configure.tgt 7b5395b317e6649ea49e778281981dcd libgomp/critical.c ! c2874635cb81dc429c512ed36f7e6bdd libgomp/env.c 92fb74c07a2638b05d4c5e0dc45d6eda libgomp/error.c 0379d8f7eb70781af7c740c5b1ac6159 libgomp/fortran.c e1e859d2786858fddf4e00a3affaac45 libgomp/hashtab.h --- 61583,61589 ---- 845aba989905c7c6806400c6113e03b3 libgomp/configure.ac 2a5380316834e607859cc29c247eb9e7 libgomp/configure.tgt 7b5395b317e6649ea49e778281981dcd libgomp/critical.c ! 6ddb09f11fc7270a276ea9ea0b63adc6 libgomp/env.c 92fb74c07a2638b05d4c5e0dc45d6eda libgomp/error.c 0379d8f7eb70781af7c740c5b1ac6159 libgomp/fortran.c e1e859d2786858fddf4e00a3affaac45 libgomp/hashtab.h *************** b986b5883aa306b096b858d0f2e237bc libgom *** 61348,61354 **** 2a682110865cc758a3c1df97dd3992a3 libgomp/libgomp-plugin.c dd8799786633c7a3094553dfc8a9ca8b libgomp/libgomp-plugin.h 99fefc96d4bc2d4b96c65131330e2c70 libgomp/libgomp.h ! 4875c3b71c5573c9c83a10bdc3bec15e libgomp/libgomp.info 9a1ab09c02391af1c95e6d63cb8eb499 libgomp/libgomp.map 8b2aa50aecad82171348a6918309afd6 libgomp/libgomp.spec.in 6a91bc2eda39d9eddffc49cbcb5e07f2 libgomp/libgomp.texi --- 61592,61598 ---- 2a682110865cc758a3c1df97dd3992a3 libgomp/libgomp-plugin.c dd8799786633c7a3094553dfc8a9ca8b libgomp/libgomp-plugin.h 99fefc96d4bc2d4b96c65131330e2c70 libgomp/libgomp.h ! 5ff4539edc319d1129e213b45c6b3424 libgomp/libgomp.info 9a1ab09c02391af1c95e6d63cb8eb499 libgomp/libgomp.map 8b2aa50aecad82171348a6918309afd6 libgomp/libgomp.spec.in 6a91bc2eda39d9eddffc49cbcb5e07f2 libgomp/libgomp.texi *************** d40927d27fc8aa0a3f0aca700ccbd13b libgom *** 61519,61524 **** --- 61763,61769 ---- 3a212ac2024168bc7de1da7b0d3118e4 libgomp/testsuite/libgomp.c++/pr69555-1.C e05799ca0fb925e4de120a002da662ed libgomp/testsuite/libgomp.c++/pr69555-2.C 854c3912b1646c8771d7f3032a72cd1f libgomp/testsuite/libgomp.c++/pr70376.C + 80258160ea88fc6c77ba4774e507a905 libgomp/testsuite/libgomp.c++/pr81130.C a594cebdf052900dd0c8792068e14d85 libgomp/testsuite/libgomp.c++/reduction-1.C 1473f55e3f6f9827b6dd281025b88b85 libgomp/testsuite/libgomp.c++/reduction-10.C bd119573b86fb5577edaf97dd86d2a6c libgomp/testsuite/libgomp.c++/reduction-11.C *************** a78eae138c60567fc82530963386e74a libgom *** 61866,61871 **** --- 62111,62122 ---- fae0065b967df85f2d4ef6b0d6a27837 libgomp/testsuite/libgomp.c/pr69805.c 44e637116f58b1ad19c190f3b5a123fa libgomp/testsuite/libgomp.c/pr70680-1.c 2c3d1f7b987fcb66ad2f7ba2adc2dc73 libgomp/testsuite/libgomp.c/pr70680-2.c + de7474a566759aa74fe2275f18aea205 libgomp/testsuite/libgomp.c/pr79940.c + b39ac1676fce227eca227a5a7c39c784 libgomp/testsuite/libgomp.c/pr80394.c + cdbcad7124c1e89a09c38bffd2f8af26 libgomp/testsuite/libgomp.c/pr80809-1.c + 74aa701ffb4677d1a83a69caec90ea29 libgomp/testsuite/libgomp.c/pr80809-2.c + fbaa429fdd38498866cb27eca67eb819 libgomp/testsuite/libgomp.c/pr80809-3.c + e768743d2af95f59780e3418077b7e1e libgomp/testsuite/libgomp.c/pr80853.c 2a0a447db3ae892c0c62b0136b00360e libgomp/testsuite/libgomp.c/priority.c ea7c9e74bda402b1663a903b26400fab libgomp/testsuite/libgomp.c/private-1.c a594cebdf052900dd0c8792068e14d85 libgomp/testsuite/libgomp.c/reduction-1.c *************** e05c73847f8ec27c6cb39c45216fcf0f libgom *** 62279,62284 **** --- 62530,62536 ---- 082ce69140a390063d0f7f40d1eb2046 libgomp/testsuite/libgomp.oacc-c-c++-common/context-2.c 223e42eece140c60f9e6b5befdcca4e1 libgomp/testsuite/libgomp.oacc-c-c++-common/context-3.c 6d8fa953e8f4d1a98183167fca268885 libgomp/testsuite/libgomp.oacc-c-c++-common/context-4.c + 98ea87c8193e01406d01d50c3ec22bcf libgomp/testsuite/libgomp.oacc-c-c++-common/crash-1.c c826235c3b755ef2376b379ef9b17203 libgomp/testsuite/libgomp.oacc-c-c++-common/data-1.c f9b513f97ade99adac20db9907c31c9f libgomp/testsuite/libgomp.oacc-c-c++-common/data-2.c 7155897e75ff81819ab32987e061f8a7 libgomp/testsuite/libgomp.oacc-c-c++-common/data-3.c *************** d3f9f8b453576b8a24f3f2db4ad0cbe2 libgom *** 62583,62589 **** 6d7b9ef24d9986c5e4cb3f32834b1653 libgomp/work.c 99c2e5e712b990ee07be10f53e41f3fb libiberty/.gitignore a916467b91076e631dd8edb7424769c7 libiberty/COPYING.LIB ! bb29dba1e7628203378028746b52c5d7 libiberty/ChangeLog 347c31392973de6a4872d540c1718dc1 libiberty/ChangeLog.jit f925c3515902a26a68a6019f355abc56 libiberty/Makefile.in c68dbf7834af4281ebd84caa3fd54680 libiberty/README --- 62835,62841 ---- 6d7b9ef24d9986c5e4cb3f32834b1653 libgomp/work.c 99c2e5e712b990ee07be10f53e41f3fb libiberty/.gitignore a916467b91076e631dd8edb7424769c7 libiberty/COPYING.LIB ! b3f6d9512d834f16820e73c81147a70b libiberty/ChangeLog 347c31392973de6a4872d540c1718dc1 libiberty/ChangeLog.jit f925c3515902a26a68a6019f355abc56 libiberty/Makefile.in c68dbf7834af4281ebd84caa3fd54680 libiberty/README *************** f32b581d10bcc500277b6f4b4f923a4e libibe *** 62745,62751 **** 6f774a92661ca4a067f1691a7925524b libiberty/xstrerror.c c6e7ef53b4ff115a136d917511222656 libiberty/xstrndup.c 2f875f0d4ecdb15ca4d5a65ba2d56a93 libiberty/xvasprintf.c ! 641163cc4cd3eecdfd94fb343de2a4a0 libitm/ChangeLog 800745ad84882bc445410a58c2fddd51 libitm/Makefile.am 23235b4aa0699e1256a124e56d902921 libitm/Makefile.in 1a17c60965964328d1592ba6fd26d410 libitm/aatree.cc --- 62997,63003 ---- 6f774a92661ca4a067f1691a7925524b libiberty/xstrerror.c c6e7ef53b4ff115a136d917511222656 libiberty/xstrndup.c 2f875f0d4ecdb15ca4d5a65ba2d56a93 libiberty/xvasprintf.c ! 754429fdc9eb44266067ee80d4208f54 libitm/ChangeLog 800745ad84882bc445410a58c2fddd51 libitm/Makefile.am 23235b4aa0699e1256a124e56d902921 libitm/Makefile.in 1a17c60965964328d1592ba6fd26d410 libitm/aatree.cc *************** a0699edb774c43c5805121d3985c4ea2 libitm *** 62803,62809 **** ca06f6a22290f04aac1fc335ece29711 libitm/dispatch.h c4d7034d2f52d605b4b8f4644d0b669e libitm/eh_cpp.cc f545350500de7fa7f56cff5f11802e73 libitm/libitm.h ! 66cbb568ba09aad0f8035e9646a0ec0d libitm/libitm.info 0c43820b921ecdbe9d98f068100e716a libitm/libitm.map ea467d7117853d139bb288ab75261139 libitm/libitm.spec.in 1c481e6f4cca694530ceaa0fdf2623a5 libitm/libitm.texi --- 63055,63061 ---- ca06f6a22290f04aac1fc335ece29711 libitm/dispatch.h c4d7034d2f52d605b4b8f4644d0b669e libitm/eh_cpp.cc f545350500de7fa7f56cff5f11802e73 libitm/libitm.h ! 1e056608685399611919ababcb07a7f1 libitm/libitm.info 0c43820b921ecdbe9d98f068100e716a libitm/libitm.map ea467d7117853d139bb288ab75261139 libitm/libitm.spec.in 1c481e6f4cca694530ceaa0fdf2623a5 libitm/libitm.texi *************** ef24198422c19f99b0c41be6a16f7081 libitm *** 62849,62855 **** 62d4ccb869b56e1e27163303bf2a85f0 libitm/useraction.cc 3028050fc7e9c2aa747445850c00fe86 libitm/util.cc 94d55d512a9ba36caa9b7df079bae19f libjava/COPYING ! 3d1b37672644ed888bb9e618a518751e libjava/ChangeLog 03e1f38b916604fdf1470238201325f3 libjava/ChangeLog-1998 691acb61fbd6a2235826ff55db5578be libjava/ChangeLog-1999 b58c6701706771a02bf00a77666941ef libjava/ChangeLog-2000 --- 63101,63107 ---- 62d4ccb869b56e1e27163303bf2a85f0 libitm/useraction.cc 3028050fc7e9c2aa747445850c00fe86 libitm/util.cc 94d55d512a9ba36caa9b7df079bae19f libjava/COPYING ! 4bdcf9a10f49048a2321b18f6ef33076 libjava/ChangeLog 03e1f38b916604fdf1470238201325f3 libjava/ChangeLog-1998 691acb61fbd6a2235826ff55db5578be libjava/ChangeLog-1999 b58c6701706771a02bf00a77666941ef libjava/ChangeLog-2000 *************** de54f80484e640306e109e785e4611c8 libjav *** 62892,62898 **** 880a25226e4e4e4c241663041d24f8dd libjava/classpath/AUTHORS efd97e0bb913655e0c8b16fa78bdded4 libjava/classpath/BUGS af0004801732bc4b20d90f351cf80510 libjava/classpath/COPYING ! d45fc17eb4b5196674b23104e451c0b7 libjava/classpath/ChangeLog 3418fae58de967afe26d915a4b18d82c libjava/classpath/ChangeLog-2003 a5b72adb94a3c362738b0f52e57a82af libjava/classpath/ChangeLog-2004 61159c6e0802d0d2a92b3051003db5c5 libjava/classpath/ChangeLog-2005 --- 63144,63150 ---- 880a25226e4e4e4c241663041d24f8dd libjava/classpath/AUTHORS efd97e0bb913655e0c8b16fa78bdded4 libjava/classpath/BUGS af0004801732bc4b20d90f351cf80510 libjava/classpath/COPYING ! cec8b827070a5fb654fa88992b37acd4 libjava/classpath/ChangeLog 3418fae58de967afe26d915a4b18d82c libjava/classpath/ChangeLog-2003 a5b72adb94a3c362738b0f52e57a82af libjava/classpath/ChangeLog-2004 61159c6e0802d0d2a92b3051003db5c5 libjava/classpath/ChangeLog-2005 *************** a6cedb4991503f803e9f0870daf59c13 libjav *** 62930,62950 **** b343eec566430e85d1f95c21438aa4ee libjava/classpath/doc/api/Makefile.am 1d310e1c7d51b6af013da87024dc9620 libjava/classpath/doc/api/Makefile.in 5ddd829b35fc94b0cdb119084089edb8 libjava/classpath/doc/cp-hacking.texinfo ! 4462ed34d5cb7ce2d72cf955dd003c93 libjava/classpath/doc/cp-tools.info 0349e5c38c548584225423ef4bafd20b libjava/classpath/doc/cp-tools.texinfo 3155d9bd9a7bf4aff2ff0dfe4a2cb878 libjava/classpath/doc/cp-vmintegration.texinfo ! 3018e0177d4efb1ef08d92c03f2bf4ce libjava/classpath/doc/gappletviewer.1 ! bc3f78d7f3b77987dc22629e89278fac libjava/classpath/doc/gjar.1 ! d1c7aa87da2de2d02129f69b0df11412 libjava/classpath/doc/gjarsigner.1 ! 345e7ae67031bd7ec1f4651c60f6699e libjava/classpath/doc/gjavah.1 ! fcc787aa306f15a4ad10b0350351eeb5 libjava/classpath/doc/gjdoc.1 ! bb225a3e971c32e18666fe0e944249d5 libjava/classpath/doc/gkeytool.1 ! d51ab781d4257b97bf7f8a0b257dc28b libjava/classpath/doc/gnative2ascii.1 ! ecec5fda6789d1d7dcd9e6c31176b205 libjava/classpath/doc/gorbd.1 ! 5ce1c258608d8a1052d244ae007cfb44 libjava/classpath/doc/grmid.1 ! b9b54f46e49ae6e8f4f950ac104e6a29 libjava/classpath/doc/grmiregistry.1 ! 8235915fb4c30f2eaf06d8703ed19fb6 libjava/classpath/doc/gserialver.1 ! 7c81a3fe5cf9df5d70ff94e7bf718f69 libjava/classpath/doc/gtnameserv.1 f7edd2bbe78e9a7e7aa706fbfa6f467e libjava/classpath/doc/texi2pod.pl 01b23c87dcf82048a5958c8224653305 libjava/classpath/doc/texinfo.tex b1e0c0c30547d57d7a09b04d47c70b06 libjava/classpath/examples/.cvsignore --- 63182,63202 ---- b343eec566430e85d1f95c21438aa4ee libjava/classpath/doc/api/Makefile.am 1d310e1c7d51b6af013da87024dc9620 libjava/classpath/doc/api/Makefile.in 5ddd829b35fc94b0cdb119084089edb8 libjava/classpath/doc/cp-hacking.texinfo ! ea38d39dc4cef82662c24a90996000d2 libjava/classpath/doc/cp-tools.info 0349e5c38c548584225423ef4bafd20b libjava/classpath/doc/cp-tools.texinfo 3155d9bd9a7bf4aff2ff0dfe4a2cb878 libjava/classpath/doc/cp-vmintegration.texinfo ! c3ee65cdbda730784c93bd938ea09552 libjava/classpath/doc/gappletviewer.1 ! b1454f8ecfd8dc65259c1df434efc820 libjava/classpath/doc/gjar.1 ! b746f0089860c8a28341c7279c34966a libjava/classpath/doc/gjarsigner.1 ! 8717e280ae85199cd17c78a659dc7e99 libjava/classpath/doc/gjavah.1 ! 4d99ea1499a869f482796f4fa8ad5b94 libjava/classpath/doc/gjdoc.1 ! b8f189aaa401bcf54028a00ad266c838 libjava/classpath/doc/gkeytool.1 ! bf3dfe25b26210d257fe7c9d81cf9e54 libjava/classpath/doc/gnative2ascii.1 ! f01233911c43902ec3fa7d121aee3c55 libjava/classpath/doc/gorbd.1 ! 97d983cd87e77cf89ba6bff938acd5e8 libjava/classpath/doc/grmid.1 ! 0a2846c77abd824a9638b18a0be2876f libjava/classpath/doc/grmiregistry.1 ! f96e7a8ca41adad66634b883891f5003 libjava/classpath/doc/gserialver.1 ! 7fbeea52704135780b7affd5d420ab70 libjava/classpath/doc/gtnameserv.1 f7edd2bbe78e9a7e7aa706fbfa6f467e libjava/classpath/doc/texi2pod.pl 01b23c87dcf82048a5958c8224653305 libjava/classpath/doc/texinfo.tex b1e0c0c30547d57d7a09b04d47c70b06 libjava/classpath/examples/.cvsignore *************** a40a8f1527e2703fe2f08bf7276d8591 libjav *** 85162,85168 **** 697ca1de35069bd86456a5a19b9c4f11 libjava/libgcj.ver 184718636f014ef2ca46d62ba8d6c3bf libjava/libgcj_bc.c e3eda01d9815f8d24aae2dbd89b68b06 libjava/libltdl/COPYING.LIB ! 2b33b4cdb551a039ff475a5dafac6593 libjava/libltdl/ChangeLog 349267319e3d55dcf180a20f85394144 libjava/libltdl/Makefile.am adfab7044ad8486145007b99df5c5318 libjava/libltdl/Makefile.in 36da24f9facf00b349ea10dba3789d92 libjava/libltdl/README --- 85414,85420 ---- 697ca1de35069bd86456a5a19b9c4f11 libjava/libgcj.ver 184718636f014ef2ca46d62ba8d6c3bf libjava/libgcj_bc.c e3eda01d9815f8d24aae2dbd89b68b06 libjava/libltdl/COPYING.LIB ! 865c72009c79b4993f29a931000b447f libjava/libltdl/ChangeLog 349267319e3d55dcf180a20f85394144 libjava/libltdl/Makefile.am adfab7044ad8486145007b99df5c5318 libjava/libltdl/Makefile.in 36da24f9facf00b349ea10dba3789d92 libjava/libltdl/README *************** d41d8cd98f00b204e9800998ecf8427e libjav *** 86860,86866 **** 434ac04eb066f5075299583492846410 libjava/verify.cc 355440a0c2fb5e16259d7ae381b37ed5 libjava/win32-threads.cc 434d5e5e91727dec004f0d1d1fab47ec libjava/win32.cc ! 9ccd52488bdb7580be838ac594e4e546 libmpx/ChangeLog 38b5a5961bf81cf96b7905974a000dc2 libmpx/Makefile.am 52ceef9cd663650f4d1d9c8e91656d14 libmpx/Makefile.in 9883ed42b491d8aea83fdde90561cf2a libmpx/acinclude.m4 --- 87112,87118 ---- 434ac04eb066f5075299583492846410 libjava/verify.cc 355440a0c2fb5e16259d7ae381b37ed5 libjava/win32-threads.cc 434d5e5e91727dec004f0d1d1fab47ec libjava/win32.cc ! 64662197b39ae3786c002d5f295d9f46 libmpx/ChangeLog 38b5a5961bf81cf96b7905974a000dc2 libmpx/Makefile.am 52ceef9cd663650f4d1d9c8e91656d14 libmpx/Makefile.in 9883ed42b491d8aea83fdde90561cf2a libmpx/acinclude.m4 *************** e67fb1bdc86e2be5473ab0192835f369 libmpx *** 86883,86889 **** e7c62aca341ea472234d7cb0bc4af328 libmpx/mpxwrap/libmpxwrappers.map 514fed0b52cdd26987101b36d86a7cf8 libmpx/mpxwrap/libtool-version c32d22d10f53f727607e2159bb49c6c2 libmpx/mpxwrap/mpx_wrappers.c ! 778482fcc745193ddb483e43d57c9e71 libobjc/ChangeLog b9ae0bf274b89fa44e8eee13ad306f00 libobjc/Makefile.in 261388284fa6d545a9a911c95536c866 libobjc/NXConstStr.m bc65a6b5a27236334194af5a7d99c5e5 libobjc/Object.m --- 87135,87141 ---- e7c62aca341ea472234d7cb0bc4af328 libmpx/mpxwrap/libmpxwrappers.map 514fed0b52cdd26987101b36d86a7cf8 libmpx/mpxwrap/libtool-version c32d22d10f53f727607e2159bb49c6c2 libmpx/mpxwrap/mpx_wrappers.c ! f87643a4bb8ff1f66ca5164564392c41 libobjc/ChangeLog b9ae0bf274b89fa44e8eee13ad306f00 libobjc/Makefile.in 261388284fa6d545a9a911c95536c866 libobjc/NXConstStr.m bc65a6b5a27236334194af5a7d99c5e5 libobjc/Object.m *************** e6218a24eff5153bc00353f3422fddcd libobj *** 86940,86946 **** 724918aeb3ea9297276e9734e4fd45cc libobjc/selector.c e96a20fe7e87e480b2a9b85b6f812a1e libobjc/sendmsg.c 1904d9feab2663cba569f7eac1621890 libobjc/thr.c ! 6ad9f7b975c8c79ecf5232f7c74b0307 liboffloadmic/ChangeLog 721476c91f1c5862e3faf49e89d28b35 liboffloadmic/Makefile.am 38474037dd82c6d06e2e1f2c37123515 liboffloadmic/Makefile.in 6126c8d03f6c3cc1a2f5e502f3196cd7 liboffloadmic/aclocal.m4 --- 87192,87198 ---- 724918aeb3ea9297276e9734e4fd45cc libobjc/selector.c e96a20fe7e87e480b2a9b85b6f812a1e libobjc/sendmsg.c 1904d9feab2663cba569f7eac1621890 libobjc/thr.c ! 8e837e88acfcd6cf80ab306c284e3940 liboffloadmic/ChangeLog 721476c91f1c5862e3faf49e89d28b35 liboffloadmic/Makefile.am 38474037dd82c6d06e2e1f2c37123515 liboffloadmic/Makefile.in 6126c8d03f6c3cc1a2f5e502f3196cd7 liboffloadmic/aclocal.m4 *************** d15cf07e8d906fc3a590a354637de29c liboff *** 87042,87048 **** dff5c8575c49d6aa71e549b0fa021479 liboffloadmic/runtime/orsl-lite/version.txt 65455ebe4e5708535fba3a41d96e8acc liboffloadmic/runtime/use_mpss2.txt a916467b91076e631dd8edb7424769c7 libquadmath/COPYING.LIB ! 955a72e5681bcea4fe66b34c9b55561f libquadmath/ChangeLog 9ccac80a0c6650be0835f0f35cea32f6 libquadmath/Makefile.am 8c91333be633709af4fb3c9ea30ef0a7 libquadmath/Makefile.in 4c8b4478a1031d129e7cc6b341876b99 libquadmath/acinclude.m4 --- 87294,87300 ---- dff5c8575c49d6aa71e549b0fa021479 liboffloadmic/runtime/orsl-lite/version.txt 65455ebe4e5708535fba3a41d96e8acc liboffloadmic/runtime/use_mpss2.txt a916467b91076e631dd8edb7424769c7 libquadmath/COPYING.LIB ! 138500d789adcd225d7b400d27be84de libquadmath/ChangeLog 9ccac80a0c6650be0835f0f35cea32f6 libquadmath/Makefile.am 8c91333be633709af4fb3c9ea30ef0a7 libquadmath/Makefile.in 4c8b4478a1031d129e7cc6b341876b99 libquadmath/acinclude.m4 *************** b575232932aeb139e780664720bc8695 libqua *** 87050,87056 **** bf09ede5c6d78e3d132bde0f933590d8 libquadmath/config.h.in e2528fdd401f4aa4949acf6b7472c6e5 libquadmath/configure 29e66c9d2ef7b7621276c63bee20d622 libquadmath/configure.ac ! ce4f89fd0e83be7bdf263426f5e00bba libquadmath/libquadmath.info c4e13f3169f2de58d737acfdba76647b libquadmath/libquadmath.texi 77280bb7ee423875e03d9c0d34527df6 libquadmath/libtool-version f44065462735b4699d44588271a5f09a libquadmath/math/acoshq.c --- 87302,87308 ---- bf09ede5c6d78e3d132bde0f933590d8 libquadmath/config.h.in e2528fdd401f4aa4949acf6b7472c6e5 libquadmath/configure 29e66c9d2ef7b7621276c63bee20d622 libquadmath/configure.ac ! a1cc2f55622467226bcf5e45723775c5 libquadmath/libquadmath.info c4e13f3169f2de58d737acfdba76647b libquadmath/libquadmath.texi 77280bb7ee423875e03d9c0d34527df6 libquadmath/libtool-version f44065462735b4699d44588271a5f09a libquadmath/math/acoshq.c *************** e766022f8615b72cbc38335d262e9d3d libqua *** 87174,87180 **** a81cc82679e80c86cfbd5575867450d0 libquadmath/strtod/strtod_l.c da808e110fc09ebd41ebd405790a70df libquadmath/strtod/strtoflt128.c d15a18f7c46ba2add6148edc5b7563c0 libquadmath/strtod/tens_in_limb.c ! a5a5f7400fcf4b5510395d1ec0dfca5c libsanitizer/ChangeLog be9b1514f2ae0907d5459acd6331993d libsanitizer/HOWTO_MERGE 0249c37748936faf5b1efd5789587909 libsanitizer/LICENSE.TXT e9eb4a77cb6d1457005493aeef54478e libsanitizer/MERGE --- 87426,87432 ---- a81cc82679e80c86cfbd5575867450d0 libquadmath/strtod/strtod_l.c da808e110fc09ebd41ebd405790a70df libquadmath/strtod/strtoflt128.c d15a18f7c46ba2add6148edc5b7563c0 libquadmath/strtod/tens_in_limb.c ! bc6253ce3b4aed3dbfdb64a2e4c57d78 libsanitizer/ChangeLog be9b1514f2ae0907d5459acd6331993d libsanitizer/HOWTO_MERGE 0249c37748936faf5b1efd5789587909 libsanitizer/LICENSE.TXT e9eb4a77cb6d1457005493aeef54478e libsanitizer/MERGE *************** e583d50590d4efef84afb6f971f72edd libsan *** 87298,87304 **** 40f1f8c70306b4bd87eaf2b49f038521 libsanitizer/sanitizer_common/sanitizer_bvgraph.h 25500b6ee4ee2390869a82fd8ac51b06 libsanitizer/sanitizer_common/sanitizer_common.cc f7c4be9987acfaba5bbbe8150e8d689a libsanitizer/sanitizer_common/sanitizer_common.h ! 31ce783c7f5f7ed12ec248c6b2150b37 libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc 0245ca282af75f46391dd49d69bf72da libsanitizer/sanitizer_common/sanitizer_common_interceptors_format.inc 7e221dc10813e9b06f385692c9a73a6b libsanitizer/sanitizer_common/sanitizer_common_interceptors_ioctl.inc e4443a7b03e9196ec589a574beaa65b7 libsanitizer/sanitizer_common/sanitizer_common_libcdep.cc --- 87550,87556 ---- 40f1f8c70306b4bd87eaf2b49f038521 libsanitizer/sanitizer_common/sanitizer_bvgraph.h 25500b6ee4ee2390869a82fd8ac51b06 libsanitizer/sanitizer_common/sanitizer_common.cc f7c4be9987acfaba5bbbe8150e8d689a libsanitizer/sanitizer_common/sanitizer_common.h ! 77b08b09b82b523b3da72dbc24a4deb6 libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc 0245ca282af75f46391dd49d69bf72da libsanitizer/sanitizer_common/sanitizer_common_interceptors_format.inc 7e221dc10813e9b06f385692c9a73a6b libsanitizer/sanitizer_common/sanitizer_common_interceptors_ioctl.inc e4443a7b03e9196ec589a574beaa65b7 libsanitizer/sanitizer_common/sanitizer_common_libcdep.cc *************** dc19b6c6d105fe7ca9a91dcdfeb09e7c libsan *** 87336,87343 **** 6976c17606d22350f7ea30dc51a8a7c9 libsanitizer/sanitizer_common/sanitizer_platform.h 13ec74e7e8fd832b95b23cfd8dd8b1ce libsanitizer/sanitizer_common/sanitizer_platform_interceptors.h 3af384999d9dcbaba93afe259ebfc361 libsanitizer/sanitizer_common/sanitizer_platform_limits_linux.cc ! a87db107256c9d52d9145a95d2ee3576 libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc ! 57dacd721cfe23ef257e2dca3c782a9f libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h 0431401b47c8667bdb65915e9cdcd65e libsanitizer/sanitizer_common/sanitizer_posix.cc d1e4d3769547c1aa3ed1d2e9cf61901e libsanitizer/sanitizer_common/sanitizer_posix.h 0fd2c0d87903e069a27961b26db51952 libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cc --- 87588,87595 ---- 6976c17606d22350f7ea30dc51a8a7c9 libsanitizer/sanitizer_common/sanitizer_platform.h 13ec74e7e8fd832b95b23cfd8dd8b1ce libsanitizer/sanitizer_common/sanitizer_platform_interceptors.h 3af384999d9dcbaba93afe259ebfc361 libsanitizer/sanitizer_common/sanitizer_platform_limits_linux.cc ! 4fff80054340191d1fe4d26ac691a9d5 libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc ! 1af7cc7fb726a294e7e46c73fd87efdb libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.h 0431401b47c8667bdb65915e9cdcd65e libsanitizer/sanitizer_common/sanitizer_posix.cc d1e4d3769547c1aa3ed1d2e9cf61901e libsanitizer/sanitizer_common/sanitizer_posix.h 0fd2c0d87903e069a27961b26db51952 libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cc *************** e8a1f931c59862aa26d415ced67a4a41 libsan *** 87464,87470 **** 0f33fad437a0fa30b1527f8f957011d6 libsanitizer/ubsan/ubsan_type_hash_win.cc 219e3b5218298c97aaa60684b507ecbd libsanitizer/ubsan/ubsan_value.cc 735246869fac0a1e63b5d9c72143e63a libsanitizer/ubsan/ubsan_value.h ! 0b632310a9c089a49b8442ad9c5efb6e libssp/ChangeLog 01d9954c400db04da1b8705029e6d9d9 libssp/Makefile.am 52a76014afba3062c646a0b94878af1d libssp/Makefile.in b0548e1d34696c0fb30573ffde20c761 libssp/aclocal.m4 --- 87716,87722 ---- 0f33fad437a0fa30b1527f8f957011d6 libsanitizer/ubsan/ubsan_type_hash_win.cc 219e3b5218298c97aaa60684b507ecbd libsanitizer/ubsan/ubsan_value.cc 735246869fac0a1e63b5d9c72143e63a libsanitizer/ubsan/ubsan_value.h ! a187f3f0ba4d632afdad80c34bc5b706 libssp/ChangeLog 01d9954c400db04da1b8705029e6d9d9 libssp/Makefile.am 52a76014afba3062c646a0b94878af1d libssp/Makefile.in b0548e1d34696c0fb30573ffde20c761 libssp/aclocal.m4 *************** aeb2f84c5e8ba3215469d507bd2efe57 libssp *** 87493,87499 **** e9ab923d2562bf5f5be6883dfb9f0184 libssp/strncpy-chk.c 5e0d8b8a766c31b12354baec1b7a159c libssp/vsnprintf-chk.c f56ab1f8922a16f7e9e4f5270ae1e34e libssp/vsprintf-chk.c ! b43909c7408c4440ceaa3e5e4a5def19 libstdc++-v3/ChangeLog 7aa6c40440a44fcf5ec94c066160c2f8 libstdc++-v3/ChangeLog-1998 7aff86600b6a1ed3fa87305075a92db0 libstdc++-v3/ChangeLog-1999 a6f28e8fc9bb07696a9e068b439a3a87 libstdc++-v3/ChangeLog-2000 --- 87745,87751 ---- e9ab923d2562bf5f5be6883dfb9f0184 libssp/strncpy-chk.c 5e0d8b8a766c31b12354baec1b7a159c libssp/vsnprintf-chk.c f56ab1f8922a16f7e9e4f5270ae1e34e libssp/vsprintf-chk.c ! 28c236876b8d56690634a28aaf5f74a6 libstdc++-v3/ChangeLog 7aa6c40440a44fcf5ec94c066160c2f8 libstdc++-v3/ChangeLog-1998 7aff86600b6a1ed3fa87305075a92db0 libstdc++-v3/ChangeLog-1999 a6f28e8fc9bb07696a9e068b439a3a87 libstdc++-v3/ChangeLog-2000 *************** b331fae97e334afde1bd5fa125610458 libstd *** 87515,87521 **** 0149a86172f60638f0997bdcd38fd40a libstdc++-v3/Makefile.am 03a457b67d1b5a56dc0b2774631e9789 libstdc++-v3/Makefile.in f372af73db4ac0ad88e43199e1f29e08 libstdc++-v3/README ! b941def7df3b4dfc01dc7200f768397b libstdc++-v3/acinclude.m4 591861c10ebb94a293dd2f26c209cb0d libstdc++-v3/aclocal.m4 f80b04be648580537675c32fccf40441 libstdc++-v3/config.h.in 7571325be31ad750b8ed2f665cdd8856 libstdc++-v3/config/abi/compatibility.h --- 87767,87773 ---- 0149a86172f60638f0997bdcd38fd40a libstdc++-v3/Makefile.am 03a457b67d1b5a56dc0b2774631e9789 libstdc++-v3/Makefile.in f372af73db4ac0ad88e43199e1f29e08 libstdc++-v3/README ! 7b5cc428973a7bfc82f0ebbd0e8cdfe4 libstdc++-v3/acinclude.m4 591861c10ebb94a293dd2f26c209cb0d libstdc++-v3/aclocal.m4 f80b04be648580537675c32fccf40441 libstdc++-v3/config.h.in 7571325be31ad750b8ed2f665cdd8856 libstdc++-v3/config/abi/compatibility.h *************** fbbbeea894cf240b032e1a50a5338acb libstd *** 87672,87678 **** 4d378acb7d26c2cbdfb8189f02e0249a libstdc++-v3/config/os/mingw32-w64/ctype_base.h c32649b2ad73b2ac4dd148ec551cac90 libstdc++-v3/config/os/mingw32-w64/ctype_configure_char.cc 70ea119da20dc4115752b25de1207cca libstdc++-v3/config/os/mingw32-w64/ctype_inline.h ! 8aea07dab1b3720c947753fc7f49a1c4 libstdc++-v3/config/os/mingw32-w64/error_constants.h 3755e9141b3b62e4ca78cce025c796ae libstdc++-v3/config/os/mingw32-w64/os_defines.h 4d378acb7d26c2cbdfb8189f02e0249a libstdc++-v3/config/os/mingw32/ctype_base.h c32649b2ad73b2ac4dd148ec551cac90 libstdc++-v3/config/os/mingw32/ctype_configure_char.cc --- 87924,87930 ---- 4d378acb7d26c2cbdfb8189f02e0249a libstdc++-v3/config/os/mingw32-w64/ctype_base.h c32649b2ad73b2ac4dd148ec551cac90 libstdc++-v3/config/os/mingw32-w64/ctype_configure_char.cc 70ea119da20dc4115752b25de1207cca libstdc++-v3/config/os/mingw32-w64/ctype_inline.h ! f830f2298713bf762d02e738c5edef2e libstdc++-v3/config/os/mingw32-w64/error_constants.h 3755e9141b3b62e4ca78cce025c796ae libstdc++-v3/config/os/mingw32-w64/os_defines.h 4d378acb7d26c2cbdfb8189f02e0249a libstdc++-v3/config/os/mingw32/ctype_base.h c32649b2ad73b2ac4dd148ec551cac90 libstdc++-v3/config/os/mingw32/ctype_configure_char.cc *************** d1e250aa470907bf50d95531c2e2cf32 libstd *** 87703,87709 **** dd8e2e42c78cc04ce875590428fd16db libstdc++-v3/config/os/vxworks/ctype_configure_char.cc 814d7cabca76587085f430d17956155b libstdc++-v3/config/os/vxworks/ctype_inline.h 3bd3122d0d07760887f09f705c7644cd libstdc++-v3/config/os/vxworks/os_defines.h ! 5f1f5e03f86c21bcd2aa64a9ec746eb3 libstdc++-v3/configure 3143a5f1deb33dc7252b4815db0c6a25 libstdc++-v3/configure.ac 3406baa1ed40c1cb368fdab218546355 libstdc++-v3/configure.host faa579ca318e87a721a9eca8edf86134 libstdc++-v3/crossconfig.m4 --- 87955,87961 ---- dd8e2e42c78cc04ce875590428fd16db libstdc++-v3/config/os/vxworks/ctype_configure_char.cc 814d7cabca76587085f430d17956155b libstdc++-v3/config/os/vxworks/ctype_inline.h 3bd3122d0d07760887f09f705c7644cd libstdc++-v3/config/os/vxworks/os_defines.h ! 24c91e1eab91395746d51240cca6847f libstdc++-v3/configure 3143a5f1deb33dc7252b4815db0c6a25 libstdc++-v3/configure.ac 3406baa1ed40c1cb368fdab218546355 libstdc++-v3/configure.host faa579ca318e87a721a9eca8edf86134 libstdc++-v3/crossconfig.m4 *************** e24504647642dbafa49db140acc95c21 libstd *** 87722,87728 **** ced96a2fc57fb523e0a3343ba30832e8 libstdc++-v3/doc/html/ext/lwg-active.html 5ad4221cbae2df0098935da3d17182b1 libstdc++-v3/doc/html/ext/lwg-closed.html bc6aa1ba9307f4270c7741da9c16bd85 libstdc++-v3/doc/html/ext/lwg-defects.html ! 666dcd5dffd013b5063b3349b3167e6a libstdc++-v3/doc/html/faq.html 1ae70f0bf94464b036515d333fff8ab2 libstdc++-v3/doc/html/images/confdeps.png d7f63b43e9f4c39cf71de7585de522ee libstdc++-v3/doc/html/images/pbds_balls_and_bins.png 22eedc841676a98f8ae8b95131ac4d7e libstdc++-v3/doc/html/images/pbds_binary_priority_queue_int_push.png --- 87974,87980 ---- ced96a2fc57fb523e0a3343ba30832e8 libstdc++-v3/doc/html/ext/lwg-active.html 5ad4221cbae2df0098935da3d17182b1 libstdc++-v3/doc/html/ext/lwg-closed.html bc6aa1ba9307f4270c7741da9c16bd85 libstdc++-v3/doc/html/ext/lwg-defects.html ! 5b0be36aa288e29d23b619d172e87fae libstdc++-v3/doc/html/faq.html 1ae70f0bf94464b036515d333fff8ab2 libstdc++-v3/doc/html/images/confdeps.png d7f63b43e9f4c39cf71de7585de522ee libstdc++-v3/doc/html/images/pbds_balls_and_bins.png 22eedc841676a98f8ae8b95131ac4d7e libstdc++-v3/doc/html/images/pbds_binary_priority_queue_int_push.png *************** d7249eb4d31bd107d0b09ea3c80cb723 libstd *** 87803,87809 **** 33bc39e8f2d47f3d490d7ca7d4832b43 libstdc++-v3/doc/html/images/pbds_trie_node_updator_policy_cd.png df705f3839120dcb896e9839cf3404d0 libstdc++-v3/doc/html/images/pbds_update_seq_diagram.png 461308d82065c71a2ce326b4b5aca0ed libstdc++-v3/doc/html/index.html ! 94cd74df197e9287ae33be01e78a5922 libstdc++-v3/doc/html/manual/abi.html c50671050ff8de94cc275131201e5bd7 libstdc++-v3/doc/html/manual/algorithms.html 15818058c9d4057decee4a010f50ee09 libstdc++-v3/doc/html/manual/api.html 0054faf038f602ca985fe4da97553291 libstdc++-v3/doc/html/manual/appendix.html --- 88055,88061 ---- 33bc39e8f2d47f3d490d7ca7d4832b43 libstdc++-v3/doc/html/images/pbds_trie_node_updator_policy_cd.png df705f3839120dcb896e9839cf3404d0 libstdc++-v3/doc/html/images/pbds_update_seq_diagram.png 461308d82065c71a2ce326b4b5aca0ed libstdc++-v3/doc/html/index.html ! f9bd9edc7984b03cfad8b7269fe36892 libstdc++-v3/doc/html/manual/abi.html c50671050ff8de94cc275131201e5bd7 libstdc++-v3/doc/html/manual/algorithms.html 15818058c9d4057decee4a010f50ee09 libstdc++-v3/doc/html/manual/api.html 0054faf038f602ca985fe4da97553291 libstdc++-v3/doc/html/manual/appendix.html *************** b86617057a7d02b358290306b815792d libstd *** 87817,87823 **** 874c1b17a7b9b226aff1d793c2f23f64 libstdc++-v3/doc/html/manual/backwards.html 4bc46b36e9636b2f61911bec8741819b libstdc++-v3/doc/html/manual/bitmap_allocator.html b102b16060eb66b508228d886bb789eb libstdc++-v3/doc/html/manual/bitmap_allocator_impl.html ! 8f13f93f638ecc8335bbdb03871f099e libstdc++-v3/doc/html/manual/bugs.html ff5cb87200fbc4571c1b621cb0450053 libstdc++-v3/doc/html/manual/concept_checking.html ff8a760ba1cd40de947c0cb4ef121860 libstdc++-v3/doc/html/manual/concurrency.html ac6f8416ccf4463863f8233f046594b6 libstdc++-v3/doc/html/manual/configure.html --- 88069,88075 ---- 874c1b17a7b9b226aff1d793c2f23f64 libstdc++-v3/doc/html/manual/backwards.html 4bc46b36e9636b2f61911bec8741819b libstdc++-v3/doc/html/manual/bitmap_allocator.html b102b16060eb66b508228d886bb789eb libstdc++-v3/doc/html/manual/bitmap_allocator_impl.html ! 81dfa28070c9c913cbb57f4b69cf17f8 libstdc++-v3/doc/html/manual/bugs.html ff5cb87200fbc4571c1b621cb0450053 libstdc++-v3/doc/html/manual/concept_checking.html ff8a760ba1cd40de947c0cb4ef121860 libstdc++-v3/doc/html/manual/concurrency.html ac6f8416ccf4463863f8233f046594b6 libstdc++-v3/doc/html/manual/configure.html *************** c41dc87f8be3a367ba747353fbab2353 libstd *** 87858,87869 **** f2cbe7a16c1459eb9d661c4f59148c85 libstdc++-v3/doc/html/manual/license.html 756b894a64f9e63ec962a6742ba34bc8 libstdc++-v3/doc/html/manual/localization.html 518c609918662df90ec372996b1cee25 libstdc++-v3/doc/html/manual/make.html ! 250aa8325a3c9cb355bf01dc20b6996f libstdc++-v3/doc/html/manual/memory.html 2f0038d7682f075686ddeb6eb5700181 libstdc++-v3/doc/html/manual/mt_allocator.html 90aab30425d9f81569fd7f122545388f libstdc++-v3/doc/html/manual/mt_allocator_design.html 769263e7fac4c4320ed9890622a2691d libstdc++-v3/doc/html/manual/mt_allocator_ex_multi.html b477b181b88903e87cafffc02f82c26f libstdc++-v3/doc/html/manual/mt_allocator_ex_single.html ! 18a4f55ae43a71769f8b57d6318fe429 libstdc++-v3/doc/html/manual/mt_allocator_impl.html 961b1986cc712df4011f8f956904e08f libstdc++-v3/doc/html/manual/numerics.html 1e7bda9b7468a80644d426c5ec6d9956 libstdc++-v3/doc/html/manual/numerics_and_c.html 73a67e9f3ea3de4053702d5d42bc5dd5 libstdc++-v3/doc/html/manual/pairs.html --- 88110,88121 ---- f2cbe7a16c1459eb9d661c4f59148c85 libstdc++-v3/doc/html/manual/license.html 756b894a64f9e63ec962a6742ba34bc8 libstdc++-v3/doc/html/manual/localization.html 518c609918662df90ec372996b1cee25 libstdc++-v3/doc/html/manual/make.html ! 5b3b09bfb3538a873d8d2d07d7c81c68 libstdc++-v3/doc/html/manual/memory.html 2f0038d7682f075686ddeb6eb5700181 libstdc++-v3/doc/html/manual/mt_allocator.html 90aab30425d9f81569fd7f122545388f libstdc++-v3/doc/html/manual/mt_allocator_design.html 769263e7fac4c4320ed9890622a2691d libstdc++-v3/doc/html/manual/mt_allocator_ex_multi.html b477b181b88903e87cafffc02f82c26f libstdc++-v3/doc/html/manual/mt_allocator_ex_single.html ! 8e5ff1c36db70228ad85f9412c2d7e0d libstdc++-v3/doc/html/manual/mt_allocator_impl.html 961b1986cc712df4011f8f956904e08f libstdc++-v3/doc/html/manual/numerics.html 1e7bda9b7468a80644d426c5ec6d9956 libstdc++-v3/doc/html/manual/numerics_and_c.html 73a67e9f3ea3de4053702d5d42bc5dd5 libstdc++-v3/doc/html/manual/pairs.html *************** a4da9233e97dfbc6975e64682370e552 libstd *** 87885,87894 **** 119fba66274e9729e112f18c0a62af95 libstdc++-v3/doc/html/manual/profile_mode_diagnostics.html 959142a01bcfe51b5975541a3f0b6dc6 libstdc++-v3/doc/html/manual/profile_mode_impl.html 07a221c9bf5f7e46ea33f7c4a43cc754 libstdc++-v3/doc/html/manual/setup.html ! 6797250ede211d0c027dd4803fb15940 libstdc++-v3/doc/html/manual/source_code_style.html 0576cfcb1c478a91ea55484a0ff9a3ec libstdc++-v3/doc/html/manual/source_design_notes.html ! 4b33c74845f4c1725591e7974070e882 libstdc++-v3/doc/html/manual/source_organization.html ! 050ecdd165d6660df4a0dd234c886bb7 libstdc++-v3/doc/html/manual/status.html 6b028769a32926f8762762e79444becb libstdc++-v3/doc/html/manual/std_contents.html 9bb7d8baedf0c99049a912bf241462f1 libstdc++-v3/doc/html/manual/streambufs.html 0aad91af2fbe9bc6363598d5a79f7d36 libstdc++-v3/doc/html/manual/strings.html --- 88137,88146 ---- 119fba66274e9729e112f18c0a62af95 libstdc++-v3/doc/html/manual/profile_mode_diagnostics.html 959142a01bcfe51b5975541a3f0b6dc6 libstdc++-v3/doc/html/manual/profile_mode_impl.html 07a221c9bf5f7e46ea33f7c4a43cc754 libstdc++-v3/doc/html/manual/setup.html ! 6b6cefa7f9267ae701ee527c0cbe7f1e libstdc++-v3/doc/html/manual/source_code_style.html 0576cfcb1c478a91ea55484a0ff9a3ec libstdc++-v3/doc/html/manual/source_design_notes.html ! 30be5fac4a3b29dcdb65642f67eb868e libstdc++-v3/doc/html/manual/source_organization.html ! e4eb77a5ce04eceeaf9507e3fc589b11 libstdc++-v3/doc/html/manual/status.html 6b028769a32926f8762762e79444becb libstdc++-v3/doc/html/manual/std_contents.html 9bb7d8baedf0c99049a912bf241462f1 libstdc++-v3/doc/html/manual/streambufs.html 0aad91af2fbe9bc6363598d5a79f7d36 libstdc++-v3/doc/html/manual/strings.html *************** a5bf605e5e386aec1c46eb8299436b57 libstd *** 87904,87910 **** 6d0ec053f63417e2c27ac037304a5e62 libstdc++-v3/doc/html/manual/using_dynamic_or_shared.html a9088c9232d0e960dbbfd31e0393bee4 libstdc++-v3/doc/html/manual/using_exceptions.html 4c6bb05cc079802bc2624a8522213be0 libstdc++-v3/doc/html/manual/using_headers.html ! 5b2e708c7028e980733b58baa74fda40 libstdc++-v3/doc/html/manual/using_macros.html 5a9981980034ebcb698957f7baeac265 libstdc++-v3/doc/html/manual/using_namespaces.html 8c824a54ff9dd7a513a19ca3a058202a libstdc++-v3/doc/html/manual/utilities.html 449dbbf51240d77a37d2437eff256924 libstdc++-v3/doc/xml/api.xml --- 88156,88162 ---- 6d0ec053f63417e2c27ac037304a5e62 libstdc++-v3/doc/html/manual/using_dynamic_or_shared.html a9088c9232d0e960dbbfd31e0393bee4 libstdc++-v3/doc/html/manual/using_exceptions.html 4c6bb05cc079802bc2624a8522213be0 libstdc++-v3/doc/html/manual/using_headers.html ! f13d93fbad7d783f3f7416ddea47a4b8 libstdc++-v3/doc/html/manual/using_macros.html 5a9981980034ebcb698957f7baeac265 libstdc++-v3/doc/html/manual/using_namespaces.html 8c824a54ff9dd7a513a19ca3a058202a libstdc++-v3/doc/html/manual/utilities.html 449dbbf51240d77a37d2437eff256924 libstdc++-v3/doc/xml/api.xml *************** a9088c9232d0e960dbbfd31e0393bee4 libstd *** 87912,87918 **** f5a41d4f7585b850b3182fc5f4888f93 libstdc++-v3/doc/xml/book.txml 95d1335e76860d53246f3e400231ec38 libstdc++-v3/doc/xml/chapter.txml 7f8c520dc83013026c671c5c342f73e2 libstdc++-v3/doc/xml/class.txml ! cd598b0808ddfc0415f9b66d9fdf1bbc libstdc++-v3/doc/xml/faq.xml 0408e04957d20fcb2a1048c482230ec0 libstdc++-v3/doc/xml/gnu/fdl-1.3.xml df4574d04d7f029398ab0183832017b6 libstdc++-v3/doc/xml/gnu/gpl-3.0.xml 18a6390297702ec8fd75cbcc525d2005 libstdc++-v3/doc/xml/images/confdeps.dot --- 88164,88170 ---- f5a41d4f7585b850b3182fc5f4888f93 libstdc++-v3/doc/xml/book.txml 95d1335e76860d53246f3e400231ec38 libstdc++-v3/doc/xml/chapter.txml 7f8c520dc83013026c671c5c342f73e2 libstdc++-v3/doc/xml/class.txml ! c51fa440e8e6a3e232681b69829ab391 libstdc++-v3/doc/xml/faq.xml 0408e04957d20fcb2a1048c482230ec0 libstdc++-v3/doc/xml/gnu/fdl-1.3.xml df4574d04d7f029398ab0183832017b6 libstdc++-v3/doc/xml/gnu/gpl-3.0.xml 18a6390297702ec8fd75cbcc525d2005 libstdc++-v3/doc/xml/images/confdeps.dot *************** cc132f90a00a3ca05f64b578f9e332aa libstd *** 88092,88101 **** f63bfdc03ba2b82c74864f02206d7c52 libstdc++-v3/doc/xml/images/pbds_tree_text_lor_find.svg 33bc39e8f2d47f3d490d7ca7d4832b43 libstdc++-v3/doc/xml/images/pbds_trie_node_updator_policy_cd.png df705f3839120dcb896e9839cf3404d0 libstdc++-v3/doc/xml/images/pbds_update_seq_diagram.png ! 9848471637f30ed28662ffc5f1afc3a6 libstdc++-v3/doc/xml/manual/abi.xml 6a68f07a8b8abd9e65846432ed52d646 libstdc++-v3/doc/xml/manual/algorithms.xml ! fd2185821a70453792b0c373704f219b libstdc++-v3/doc/xml/manual/allocator.xml ! 031d46014e6f017fdc696198de31b6a7 libstdc++-v3/doc/xml/manual/appendix_contributing.xml 074e722c08588c6474b7eb1dc527bd89 libstdc++-v3/doc/xml/manual/appendix_free.xml fddfbac311009ebd3056c4edd7ee522a libstdc++-v3/doc/xml/manual/appendix_porting.xml e0b6ea09e982758f8a79d0d165939943 libstdc++-v3/doc/xml/manual/atomics.xml --- 88344,88353 ---- f63bfdc03ba2b82c74864f02206d7c52 libstdc++-v3/doc/xml/images/pbds_tree_text_lor_find.svg 33bc39e8f2d47f3d490d7ca7d4832b43 libstdc++-v3/doc/xml/images/pbds_trie_node_updator_policy_cd.png df705f3839120dcb896e9839cf3404d0 libstdc++-v3/doc/xml/images/pbds_update_seq_diagram.png ! 111d99bfa037ba775c1ebb314d390c4f libstdc++-v3/doc/xml/manual/abi.xml 6a68f07a8b8abd9e65846432ed52d646 libstdc++-v3/doc/xml/manual/algorithms.xml ! 832fb85e9dd8e40662f3abe5b0f7b070 libstdc++-v3/doc/xml/manual/allocator.xml ! 2301d6f8a02515bb29ab31a113a2e152 libstdc++-v3/doc/xml/manual/appendix_contributing.xml 074e722c08588c6474b7eb1dc527bd89 libstdc++-v3/doc/xml/manual/appendix_free.xml fddfbac311009ebd3056c4edd7ee522a libstdc++-v3/doc/xml/manual/appendix_porting.xml e0b6ea09e982758f8a79d0d165939943 libstdc++-v3/doc/xml/manual/atomics.xml *************** bab548248426e0e90cdc1436ff5b87de libstd *** 88122,88128 **** 5d3e282d89ac0af0f7752f88466a9d39 libstdc++-v3/doc/xml/manual/locale.xml 8d6a4daabfdaa26ed8c3bd68f6cb0930 libstdc++-v3/doc/xml/manual/localization.xml d1f75977cf17da71ede22a4884f5771f libstdc++-v3/doc/xml/manual/messages.xml ! 358c6c2b091982dafcd133cc65380653 libstdc++-v3/doc/xml/manual/mt_allocator.xml 0093c0e2ef4c460d644a7c3d3e90c7b4 libstdc++-v3/doc/xml/manual/numerics.xml e2b6426957c60c385c84e7b5143089ce libstdc++-v3/doc/xml/manual/parallel_mode.xml 877b32ce48c44db2c2ef8a7901d6157d libstdc++-v3/doc/xml/manual/policy_data_structures.xml --- 88374,88380 ---- 5d3e282d89ac0af0f7752f88466a9d39 libstdc++-v3/doc/xml/manual/locale.xml 8d6a4daabfdaa26ed8c3bd68f6cb0930 libstdc++-v3/doc/xml/manual/localization.xml d1f75977cf17da71ede22a4884f5771f libstdc++-v3/doc/xml/manual/messages.xml ! 489dc876235f0b46a0cf931a02ed38a6 libstdc++-v3/doc/xml/manual/mt_allocator.xml 0093c0e2ef4c460d644a7c3d3e90c7b4 libstdc++-v3/doc/xml/manual/numerics.xml e2b6426957c60c385c84e7b5143089ce libstdc++-v3/doc/xml/manual/parallel_mode.xml 877b32ce48c44db2c2ef8a7901d6157d libstdc++-v3/doc/xml/manual/policy_data_structures.xml *************** a40510266b01e2218276f4c31a205fa9 libstd *** 88158,88171 **** 67b67a08a20715a8fc137768c51e9703 libstdc++-v3/include/backward/hashtable.h 1e581c5cb61a75c024920266f9c059f6 libstdc++-v3/include/backward/strstream b03f0a343c7d8ddccca50a891caddc33 libstdc++-v3/include/bits/algorithmfwd.h ! 0fe4d830c25c6e4d106b542bce7e3e8c libstdc++-v3/include/bits/alloc_traits.h 44f2c0f822b24fcf390e4ee5958fd277 libstdc++-v3/include/bits/allocated_ptr.h f0578356a1efb465a5dba33347032ae8 libstdc++-v3/include/bits/allocator.h 5f30f701e7d6b34448934703eace46e4 libstdc++-v3/include/bits/atomic_base.h 3774566059c77d9385646dd5083abe4d libstdc++-v3/include/bits/atomic_futex.h f34e444d81ef2fa3d21e42bbd17438ff libstdc++-v3/include/bits/basic_ios.h 521135e1da8b9600515d55a7446e6886 libstdc++-v3/include/bits/basic_ios.tcc ! 07a1f10c6f595e19575e156717d045e0 libstdc++-v3/include/bits/basic_string.h 04e7a810e20631c4e4c55f70ff0568fc libstdc++-v3/include/bits/basic_string.tcc 4a4591228c96b08e8cfafd659ca4e914 libstdc++-v3/include/bits/boost_concept_check.h 6c698861fbe30dd645b02cc9332c3cc9 libstdc++-v3/include/bits/c++0x_warning.h --- 88410,88423 ---- 67b67a08a20715a8fc137768c51e9703 libstdc++-v3/include/backward/hashtable.h 1e581c5cb61a75c024920266f9c059f6 libstdc++-v3/include/backward/strstream b03f0a343c7d8ddccca50a891caddc33 libstdc++-v3/include/bits/algorithmfwd.h ! 0340e0b47f2b600692d7c491e056e20d libstdc++-v3/include/bits/alloc_traits.h 44f2c0f822b24fcf390e4ee5958fd277 libstdc++-v3/include/bits/allocated_ptr.h f0578356a1efb465a5dba33347032ae8 libstdc++-v3/include/bits/allocator.h 5f30f701e7d6b34448934703eace46e4 libstdc++-v3/include/bits/atomic_base.h 3774566059c77d9385646dd5083abe4d libstdc++-v3/include/bits/atomic_futex.h f34e444d81ef2fa3d21e42bbd17438ff libstdc++-v3/include/bits/basic_ios.h 521135e1da8b9600515d55a7446e6886 libstdc++-v3/include/bits/basic_ios.tcc ! 839a4fbc4d9034419742eee756aa5704 libstdc++-v3/include/bits/basic_string.h 04e7a810e20631c4e4c55f70ff0568fc libstdc++-v3/include/bits/basic_string.tcc 4a4591228c96b08e8cfafd659ca4e914 libstdc++-v3/include/bits/boost_concept_check.h 6c698861fbe30dd645b02cc9332c3cc9 libstdc++-v3/include/bits/c++0x_warning.h *************** bf7b65d8a82432770b67bfea05f76a70 libstd *** 88187,88221 **** 747ea12f6405b4d9609db30c8b675ca8 libstdc++-v3/include/bits/hashtable.h 35c9015e71ec28798e37f5631e191089 libstdc++-v3/include/bits/hashtable_policy.h 774d1c8adfc14db2a3d17978368b7a94 libstdc++-v3/include/bits/indirect_array.h ! 016acd65601ca9ac9b6e5ce4c5aea2f8 libstdc++-v3/include/bits/ios_base.h 4a33231c4f3da16b8d048a90122f9e59 libstdc++-v3/include/bits/istream.tcc ! a01776572e7b308a3cc8297db8ea6222 libstdc++-v3/include/bits/list.tcc ! 9a8090489e1fd4acce47fda64ee4c9a5 libstdc++-v3/include/bits/locale_classes.h 62727e19782c980c184170e77b458415 libstdc++-v3/include/bits/locale_classes.tcc ! ad841bfa9e190a5c451a5c84e28c95f3 libstdc++-v3/include/bits/locale_conv.h 38a077c57764371d274c5da42afec656 libstdc++-v3/include/bits/locale_facets.h 269d61c4c92ef7015a5b7229b8f049e3 libstdc++-v3/include/bits/locale_facets.tcc 958ccd825559a994271e7dd40885dd8c libstdc++-v3/include/bits/locale_facets_nonio.h 57574c985411dc1cd275d61e5d8b12bf libstdc++-v3/include/bits/locale_facets_nonio.tcc 9e85812e0df6942dfc802d0d6b42ef6e libstdc++-v3/include/bits/localefwd.h ! 09d25233c3ddd6a8e34dad3a7597d3ed libstdc++-v3/include/bits/mask_array.h 4700cb729fb53d1e6ab4a185610d50b3 libstdc++-v3/include/bits/memoryfwd.h 93c339fde000e78b3a7212cbff62e5c2 libstdc++-v3/include/bits/move.h f13f71d4c874fa7366b67b16589680a4 libstdc++-v3/include/bits/ostream.tcc bf4d38da115e3d9c7ebb029e7f99026a libstdc++-v3/include/bits/ostream_insert.h ba55c3cef8fad8738c0113d2d43e5d80 libstdc++-v3/include/bits/parse_numbers.h 63ac7d37bb8785a53dc0eea061f5f7f4 libstdc++-v3/include/bits/postypes.h ! bcae0c48c3483963757753ca69f91019 libstdc++-v3/include/bits/predefined_ops.h ! 184ad2dfbadb162cff503468c6225215 libstdc++-v3/include/bits/ptr_traits.h b8fa9a4955e72e151a315d0ec313ab26 libstdc++-v3/include/bits/quoted_string.h 2101a74a8ed2eb332acd7e7192ebe4f4 libstdc++-v3/include/bits/random.h ! 93db503eb71537bc8615cf01d6bbe1ba libstdc++-v3/include/bits/random.tcc 435b63fa25aff4083ff8c0c74195e000 libstdc++-v3/include/bits/range_access.h ! 0ea8a9569003a346685ed919a110b279 libstdc++-v3/include/bits/regex.h ! 7d49b1b21073f9fed6db34155a918c2a libstdc++-v3/include/bits/regex.tcc 88cc9836fc81f27f8cd7e67a1eafc064 libstdc++-v3/include/bits/regex_automaton.h 41c818acb838b922c969730ef5233be3 libstdc++-v3/include/bits/regex_automaton.tcc ! 107e06e6fd0a23fca408e9bcc0ea03fb libstdc++-v3/include/bits/regex_compiler.h c51f1826e40c0a529fc611d4262acf6f libstdc++-v3/include/bits/regex_compiler.tcc a51ea280252e9107724ee0e3975d832d libstdc++-v3/include/bits/regex_constants.h bcfc4f6420e156f313e5134606f70e18 libstdc++-v3/include/bits/regex_error.h --- 88439,88473 ---- 747ea12f6405b4d9609db30c8b675ca8 libstdc++-v3/include/bits/hashtable.h 35c9015e71ec28798e37f5631e191089 libstdc++-v3/include/bits/hashtable_policy.h 774d1c8adfc14db2a3d17978368b7a94 libstdc++-v3/include/bits/indirect_array.h ! cc00d4ad4bd18c6455cfe0d64a451447 libstdc++-v3/include/bits/ios_base.h 4a33231c4f3da16b8d048a90122f9e59 libstdc++-v3/include/bits/istream.tcc ! c9e773f121f52034017cbc6f543cdc10 libstdc++-v3/include/bits/list.tcc ! 4b329575ae94521d03405651d83be5c3 libstdc++-v3/include/bits/locale_classes.h 62727e19782c980c184170e77b458415 libstdc++-v3/include/bits/locale_classes.tcc ! 44310eaed2b4564283ac1dc18adba997 libstdc++-v3/include/bits/locale_conv.h 38a077c57764371d274c5da42afec656 libstdc++-v3/include/bits/locale_facets.h 269d61c4c92ef7015a5b7229b8f049e3 libstdc++-v3/include/bits/locale_facets.tcc 958ccd825559a994271e7dd40885dd8c libstdc++-v3/include/bits/locale_facets_nonio.h 57574c985411dc1cd275d61e5d8b12bf libstdc++-v3/include/bits/locale_facets_nonio.tcc 9e85812e0df6942dfc802d0d6b42ef6e libstdc++-v3/include/bits/localefwd.h ! 6c3acb00560cf05c9b43b94d70262eaa libstdc++-v3/include/bits/mask_array.h 4700cb729fb53d1e6ab4a185610d50b3 libstdc++-v3/include/bits/memoryfwd.h 93c339fde000e78b3a7212cbff62e5c2 libstdc++-v3/include/bits/move.h f13f71d4c874fa7366b67b16589680a4 libstdc++-v3/include/bits/ostream.tcc bf4d38da115e3d9c7ebb029e7f99026a libstdc++-v3/include/bits/ostream_insert.h ba55c3cef8fad8738c0113d2d43e5d80 libstdc++-v3/include/bits/parse_numbers.h 63ac7d37bb8785a53dc0eea061f5f7f4 libstdc++-v3/include/bits/postypes.h ! ce8f5a0774b2c721ea07efebc091bb3d libstdc++-v3/include/bits/predefined_ops.h ! 83526f2821465f628e3fbe995936dbd1 libstdc++-v3/include/bits/ptr_traits.h b8fa9a4955e72e151a315d0ec313ab26 libstdc++-v3/include/bits/quoted_string.h 2101a74a8ed2eb332acd7e7192ebe4f4 libstdc++-v3/include/bits/random.h ! 82cffdaec411d724ed3955c709b78cf0 libstdc++-v3/include/bits/random.tcc 435b63fa25aff4083ff8c0c74195e000 libstdc++-v3/include/bits/range_access.h ! 0a84ba9528235a687d1c111f8ad8a865 libstdc++-v3/include/bits/regex.h ! f8da396033b041f0683cd6d3e3c35e49 libstdc++-v3/include/bits/regex.tcc 88cc9836fc81f27f8cd7e67a1eafc064 libstdc++-v3/include/bits/regex_automaton.h 41c818acb838b922c969730ef5233be3 libstdc++-v3/include/bits/regex_automaton.tcc ! ddf585e15fb79f0e7e7a8d2189a64357 libstdc++-v3/include/bits/regex_compiler.h c51f1826e40c0a529fc611d4262acf6f libstdc++-v3/include/bits/regex_compiler.tcc a51ea280252e9107724ee0e3975d832d libstdc++-v3/include/bits/regex_constants.h bcfc4f6420e156f313e5134606f70e18 libstdc++-v3/include/bits/regex_error.h *************** bcfc4f6420e156f313e5134606f70e18 libstd *** 88226,88232 **** 406798bbd160315ee39b2f2a0a31c492 libstdc++-v3/include/bits/shared_ptr.h 4628af319413df349cb341f017754bf4 libstdc++-v3/include/bits/shared_ptr_atomic.h c195182e74e436bd0c1312732e5a7063 libstdc++-v3/include/bits/shared_ptr_base.h ! 6bef5a3f488d1e5e376f5e843a5cc22e libstdc++-v3/include/bits/slice_array.h 81a9105e594bdd4f31466efb0ea2591c libstdc++-v3/include/bits/specfun.h a046bed66696adfb2a6c4a593d6a1e3d libstdc++-v3/include/bits/sstream.tcc dca1017544bda4f3e231a60f4bfb96aa libstdc++-v3/include/bits/std_mutex.h --- 88478,88484 ---- 406798bbd160315ee39b2f2a0a31c492 libstdc++-v3/include/bits/shared_ptr.h 4628af319413df349cb341f017754bf4 libstdc++-v3/include/bits/shared_ptr_atomic.h c195182e74e436bd0c1312732e5a7063 libstdc++-v3/include/bits/shared_ptr_base.h ! abd9d5acbbc6548544e594820f168917 libstdc++-v3/include/bits/slice_array.h 81a9105e594bdd4f31466efb0ea2591c libstdc++-v3/include/bits/specfun.h a046bed66696adfb2a6c4a593d6a1e3d libstdc++-v3/include/bits/sstream.tcc dca1017544bda4f3e231a60f4bfb96aa libstdc++-v3/include/bits/std_mutex.h *************** fa1c52cdfd2eecb575dca6d77070b658 libstd *** 88241,88255 **** 5e0db7f463d8de067a2efdb81cd411ee libstdc++-v3/include/bits/stl_iterator_base_funcs.h 8a82f794191e4709b369e5b001811418 libstdc++-v3/include/bits/stl_iterator_base_types.h b08d97028761f7434c6ddc252c198fb2 libstdc++-v3/include/bits/stl_list.h ! b9a6477d248c68e13024d183eb291070 libstdc++-v3/include/bits/stl_map.h ! 9556f102bb23248e15e50709add12454 libstdc++-v3/include/bits/stl_multimap.h ! b4cac96e603293d608d97fa359d832ca libstdc++-v3/include/bits/stl_multiset.h 7e81280f87235c30dadf018e466e8267 libstdc++-v3/include/bits/stl_numeric.h ! f99232da5bbf6962d039ceb513785b7b libstdc++-v3/include/bits/stl_pair.h 1e8d9848331663b273447b434e7ace15 libstdc++-v3/include/bits/stl_queue.h 4f0a6596c3e76d1f0a0cfe8b8cd28c76 libstdc++-v3/include/bits/stl_raw_storage_iter.h a2879dc3e90b975b5f70e47477c27168 libstdc++-v3/include/bits/stl_relops.h ! 9cd9e33f00a387e52d0e48d3db82fb91 libstdc++-v3/include/bits/stl_set.h bd25b68e010234aa7db5f5bef0a38f5d libstdc++-v3/include/bits/stl_stack.h d98c5fe528142289d2e259d80ab99c27 libstdc++-v3/include/bits/stl_tempbuf.h d6439da38b829bfdf252367966e5ddc9 libstdc++-v3/include/bits/stl_tree.h --- 88493,88507 ---- 5e0db7f463d8de067a2efdb81cd411ee libstdc++-v3/include/bits/stl_iterator_base_funcs.h 8a82f794191e4709b369e5b001811418 libstdc++-v3/include/bits/stl_iterator_base_types.h b08d97028761f7434c6ddc252c198fb2 libstdc++-v3/include/bits/stl_list.h ! 2e4720ef3c8dace2ed9fa64328b4fabc libstdc++-v3/include/bits/stl_map.h ! 782a328d849a074c235ed9d44f07f8d0 libstdc++-v3/include/bits/stl_multimap.h ! 93dcbd37eaf0741310e4c0bd0e345f5f libstdc++-v3/include/bits/stl_multiset.h 7e81280f87235c30dadf018e466e8267 libstdc++-v3/include/bits/stl_numeric.h ! eb68f6f22b22a7e683a29e73a8ee75ad libstdc++-v3/include/bits/stl_pair.h 1e8d9848331663b273447b434e7ace15 libstdc++-v3/include/bits/stl_queue.h 4f0a6596c3e76d1f0a0cfe8b8cd28c76 libstdc++-v3/include/bits/stl_raw_storage_iter.h a2879dc3e90b975b5f70e47477c27168 libstdc++-v3/include/bits/stl_relops.h ! 4f65fd5314ae1f69054f77a34f73d740 libstdc++-v3/include/bits/stl_set.h bd25b68e010234aa7db5f5bef0a38f5d libstdc++-v3/include/bits/stl_stack.h d98c5fe528142289d2e259d80ab99c27 libstdc++-v3/include/bits/stl_tempbuf.h d6439da38b829bfdf252367966e5ddc9 libstdc++-v3/include/bits/stl_tree.h *************** efeeaa1ab1b8e409f22acf2410779a6e libstd *** 88394,88403 **** 23e7049f7e8b7983c52206aab9113937 libstdc++-v3/include/decimal/decimal 71e2a65287f65ee51824acf28e1d9f7a libstdc++-v3/include/decimal/decimal.h cef47487ea4eeee91808fa37fffb617e libstdc++-v3/include/experimental/algorithm ! a23ade4452726320927e4c0160f2c744 libstdc++-v3/include/experimental/any ! 89b45a19b6cf153e676d40cf2f37aaf7 libstdc++-v3/include/experimental/array 85e52e15dfc79b200b63888787b2490b libstdc++-v3/include/experimental/bits/erase_if.h ! 4d70dddb41c06385e971673506688312 libstdc++-v3/include/experimental/bits/fs_dir.h b6975747902d899871e3c45b472dc83a libstdc++-v3/include/experimental/bits/fs_fwd.h 6acd9b133367124e7a4b5e3973963bbb libstdc++-v3/include/experimental/bits/fs_ops.h adfb7c233abfc695a28f36108d2bf01d libstdc++-v3/include/experimental/bits/fs_path.h --- 88646,88655 ---- 23e7049f7e8b7983c52206aab9113937 libstdc++-v3/include/decimal/decimal 71e2a65287f65ee51824acf28e1d9f7a libstdc++-v3/include/decimal/decimal.h cef47487ea4eeee91808fa37fffb617e libstdc++-v3/include/experimental/algorithm ! a71144884b3953088347115c58a4a0aa libstdc++-v3/include/experimental/any ! c044fd0c3013c55ef7f3aa630ca6322c libstdc++-v3/include/experimental/array 85e52e15dfc79b200b63888787b2490b libstdc++-v3/include/experimental/bits/erase_if.h ! e1a4e8f91e7ca6ec168ea0a76ba9ceb8 libstdc++-v3/include/experimental/bits/fs_dir.h b6975747902d899871e3c45b472dc83a libstdc++-v3/include/experimental/bits/fs_fwd.h 6acd9b133367124e7a4b5e3973963bbb libstdc++-v3/include/experimental/bits/fs_ops.h adfb7c233abfc695a28f36108d2bf01d libstdc++-v3/include/experimental/bits/fs_path.h *************** ab000c677e388606f6945dbd74cbbfc6 libstd *** 88409,88421 **** f88ee31c92f92057c2fd3ac31e24d93e libstdc++-v3/include/experimental/filesystem 2bff8bbef91fcc1b5d11d98bf5905df8 libstdc++-v3/include/experimental/forward_list 1bec131356b46a279f98acb03786af00 libstdc++-v3/include/experimental/functional ! 6c5f935e4fff3629ee30c039f4c55bb6 libstdc++-v3/include/experimental/iterator cfe5bab2e8a6e1cfbfba279ecd095b9b libstdc++-v3/include/experimental/list 5ea3575f34c060bd14c6163b5c02910d libstdc++-v3/include/experimental/map ! 9f2ff72def8b2ccefde5f79da53d689c libstdc++-v3/include/experimental/memory a58ca4218450c4c272409fbaa5e80400 libstdc++-v3/include/experimental/memory_resource 86c5208bc19a50ccb6aae69928c38db7 libstdc++-v3/include/experimental/numeric ! 718163eafccb8dcececc204b59b8ea43 libstdc++-v3/include/experimental/optional e219d46576c4722d3a949b4f53d80f07 libstdc++-v3/include/experimental/propagate_const 5ecb05a63ef63286d0f60baeb682bc71 libstdc++-v3/include/experimental/random 74f47c9c081b9558c023bac72c5dcc3a libstdc++-v3/include/experimental/ratio --- 88661,88673 ---- f88ee31c92f92057c2fd3ac31e24d93e libstdc++-v3/include/experimental/filesystem 2bff8bbef91fcc1b5d11d98bf5905df8 libstdc++-v3/include/experimental/forward_list 1bec131356b46a279f98acb03786af00 libstdc++-v3/include/experimental/functional ! fb661a87aecc53c876e74ee3c46582f1 libstdc++-v3/include/experimental/iterator cfe5bab2e8a6e1cfbfba279ecd095b9b libstdc++-v3/include/experimental/list 5ea3575f34c060bd14c6163b5c02910d libstdc++-v3/include/experimental/map ! de58e936a54a53b05ba84111ae57c3bc libstdc++-v3/include/experimental/memory a58ca4218450c4c272409fbaa5e80400 libstdc++-v3/include/experimental/memory_resource 86c5208bc19a50ccb6aae69928c38db7 libstdc++-v3/include/experimental/numeric ! a1a1067550444547160071aaf9c60f9e libstdc++-v3/include/experimental/optional e219d46576c4722d3a949b4f53d80f07 libstdc++-v3/include/experimental/propagate_const 5ecb05a63ef63286d0f60baeb682bc71 libstdc++-v3/include/experimental/random 74f47c9c081b9558c023bac72c5dcc3a libstdc++-v3/include/experimental/ratio *************** c391acb611251285ddfe2950a63d7354 libstd *** 88467,88473 **** 3e923267cac7fa86be2079dc8e1e39e0 libstdc++-v3/include/ext/pb_ds/detail/bin_search_tree_/rotate_fn_imps.hpp 1119aa401884afa79c7fe590ac575f5f libstdc++-v3/include/ext/pb_ds/detail/bin_search_tree_/split_join_fn_imps.hpp 874655fd4dd9b6ff6ddf09645f837ba6 libstdc++-v3/include/ext/pb_ds/detail/bin_search_tree_/traits.hpp ! c9e707b775ee2579a20577631752b4b4 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/binary_heap_.hpp c13f516621213ade5c38e5de1edd73d3 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/const_iterator.hpp e0792592ab4986ab0f9c310b54e2c87c libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/constructors_destructor_fn_imps.hpp 1a0e2a5af58b4a5e5a49fa3a2c99614e libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/debug_fn_imps.hpp --- 88719,88725 ---- 3e923267cac7fa86be2079dc8e1e39e0 libstdc++-v3/include/ext/pb_ds/detail/bin_search_tree_/rotate_fn_imps.hpp 1119aa401884afa79c7fe590ac575f5f libstdc++-v3/include/ext/pb_ds/detail/bin_search_tree_/split_join_fn_imps.hpp 874655fd4dd9b6ff6ddf09645f837ba6 libstdc++-v3/include/ext/pb_ds/detail/bin_search_tree_/traits.hpp ! bafc8386227649f28ae2ab342220a358 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/binary_heap_.hpp c13f516621213ade5c38e5de1edd73d3 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/const_iterator.hpp e0792592ab4986ab0f9c310b54e2c87c libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/constructors_destructor_fn_imps.hpp 1a0e2a5af58b4a5e5a49fa3a2c99614e libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/debug_fn_imps.hpp *************** f9fd68af920e73a77561880446b3f25b libstd *** 88476,88482 **** e58d51c70607971034ad6d6089d3167b libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/erase_fn_imps.hpp 05e45195a744ee7f849200a842048176 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/find_fn_imps.hpp 1e41ca7a7258cc12ccc296ae8a6f5e5c libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/info_fn_imps.hpp ! 7bfd4804a081322f4280835e475d0fc7 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/insert_fn_imps.hpp 92cca28059b9b94b54d34478c677ab36 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/iterators_fn_imps.hpp fdecbec718612fbc94d39bad4bef1923 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/point_const_iterator.hpp 99fac05fb8ebf6c55fb354192226039d libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/policy_access_fn_imps.hpp --- 88728,88734 ---- e58d51c70607971034ad6d6089d3167b libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/erase_fn_imps.hpp 05e45195a744ee7f849200a842048176 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/find_fn_imps.hpp 1e41ca7a7258cc12ccc296ae8a6f5e5c libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/info_fn_imps.hpp ! 86d016af741e78e7d43adfac6b0bbfe3 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/insert_fn_imps.hpp 92cca28059b9b94b54d34478c677ab36 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/iterators_fn_imps.hpp fdecbec718612fbc94d39bad4bef1923 libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/point_const_iterator.hpp 99fac05fb8ebf6c55fb354192226039d libstdc++-v3/include/ext/pb_ds/detail/binary_heap_/policy_access_fn_imps.hpp *************** e65ba1ecda5d029cecf4ec8ce8295643 libstd *** 88695,88701 **** 0721a3fbb2ac575e58330df8fabe70ed libstdc++-v3/include/ext/pb_ds/tree_policy.hpp ef915c91c0376f73260c64937ac9e34d libstdc++-v3/include/ext/pb_ds/trie_policy.hpp a346905ef4d46ce3ac742cf27d99c045 libstdc++-v3/include/ext/pod_char_traits.h ! d2a3c7715f85d459f86647aa6796ba7b libstdc++-v3/include/ext/pointer.h 916b7173eeff52f19c2c24da079b7d35 libstdc++-v3/include/ext/pool_allocator.h 1afb7c72c88c99e9fdb7d7d70303f813 libstdc++-v3/include/ext/random 54640c89c94b1d9807445620414aa1ee libstdc++-v3/include/ext/random.tcc --- 88947,88953 ---- 0721a3fbb2ac575e58330df8fabe70ed libstdc++-v3/include/ext/pb_ds/tree_policy.hpp ef915c91c0376f73260c64937ac9e34d libstdc++-v3/include/ext/pb_ds/trie_policy.hpp a346905ef4d46ce3ac742cf27d99c045 libstdc++-v3/include/ext/pod_char_traits.h ! 16490a9f133714954c122665702687fd libstdc++-v3/include/ext/pointer.h 916b7173eeff52f19c2c24da079b7d35 libstdc++-v3/include/ext/pool_allocator.h 1afb7c72c88c99e9fdb7d7d70303f813 libstdc++-v3/include/ext/random 54640c89c94b1d9807445620414aa1ee libstdc++-v3/include/ext/random.tcc *************** ab8c66b09a866c6ebf1ee4c66a42ed8e libstd *** 88795,88801 **** 424792d12066c917087cd4eee43c482d libstdc++-v3/include/profile/vector 08a29edc8c0cf8b76717c282d1236f5f libstdc++-v3/include/std/algorithm 07dd14bd89de98cd98a9be7df560b1f6 libstdc++-v3/include/std/array ! 8f9fc0788c550f8c3465bcc3a402fc42 libstdc++-v3/include/std/atomic c901579f7cc4317131404166dc863abe libstdc++-v3/include/std/bitset 7ad6388b9ff453b72d35cad78bf3ce0d libstdc++-v3/include/std/chrono fa87c6bbe2315225e7c19bd3ef21bc0c libstdc++-v3/include/std/codecvt --- 89047,89053 ---- 424792d12066c917087cd4eee43c482d libstdc++-v3/include/profile/vector 08a29edc8c0cf8b76717c282d1236f5f libstdc++-v3/include/std/algorithm 07dd14bd89de98cd98a9be7df560b1f6 libstdc++-v3/include/std/array ! 47450c19f064df8f4626abaf59e76056 libstdc++-v3/include/std/atomic c901579f7cc4317131404166dc863abe libstdc++-v3/include/std/bitset 7ad6388b9ff453b72d35cad78bf3ce0d libstdc++-v3/include/std/chrono fa87c6bbe2315225e7c19bd3ef21bc0c libstdc++-v3/include/std/codecvt *************** b0e63f9d467dc4d30057e8332fb881cb libstd *** 88804,88810 **** 52e71286840cd721cd7d62041d05f0fd libstdc++-v3/include/std/deque 60dfc425eb5b809b73d9a7335d16c878 libstdc++-v3/include/std/forward_list b5cfb151507ebe2932159acd77a927a6 libstdc++-v3/include/std/fstream ! 639978a8ee6e221457c900c16b4f7551 libstdc++-v3/include/std/functional b0af42c19c4153e3a84d1e6a3592c576 libstdc++-v3/include/std/future 296fe913c506073fd36284585afe72c1 libstdc++-v3/include/std/iomanip 4de468438d1fd8a73a3c267d70fae515 libstdc++-v3/include/std/ios --- 89056,89062 ---- 52e71286840cd721cd7d62041d05f0fd libstdc++-v3/include/std/deque 60dfc425eb5b809b73d9a7335d16c878 libstdc++-v3/include/std/forward_list b5cfb151507ebe2932159acd77a927a6 libstdc++-v3/include/std/fstream ! f11609a13f16d1f3dc732adf478a9983 libstdc++-v3/include/std/functional b0af42c19c4153e3a84d1e6a3592c576 libstdc++-v3/include/std/future 296fe913c506073fd36284585afe72c1 libstdc++-v3/include/std/iomanip 4de468438d1fd8a73a3c267d70fae515 libstdc++-v3/include/std/ios *************** a4428d83d89681a780cc9f01c788d526 libstd *** 88816,88822 **** d8714613d81a828b255a76473de1b2e4 libstdc++-v3/include/std/list 30bbd58360a5a1b6301e3e0b19867b11 libstdc++-v3/include/std/locale f0557567fbcbeadb2365a27192577b1d libstdc++-v3/include/std/map ! 9c57f6035826b2918b8bc23e3b3a0952 libstdc++-v3/include/std/memory e134b882d192d8393528db9ad097823b libstdc++-v3/include/std/mutex 654e3c696e26e50e641664dcdabc6a12 libstdc++-v3/include/std/numeric 5f205d39cfadf62757ae374258ba3e5f libstdc++-v3/include/std/ostream --- 89068,89074 ---- d8714613d81a828b255a76473de1b2e4 libstdc++-v3/include/std/list 30bbd58360a5a1b6301e3e0b19867b11 libstdc++-v3/include/std/locale f0557567fbcbeadb2365a27192577b1d libstdc++-v3/include/std/map ! 14edac9f6f2105da9cbb79927ff58b9f libstdc++-v3/include/std/memory e134b882d192d8393528db9ad097823b libstdc++-v3/include/std/mutex 654e3c696e26e50e641664dcdabc6a12 libstdc++-v3/include/std/numeric 5f205d39cfadf62757ae374258ba3e5f libstdc++-v3/include/std/ostream *************** e1890cb0c780d3d3500dc2e8051f9cbc libstd *** 88833,88841 **** 64501e3b2fbc4c4fcc6b9fd5371cb059 libstdc++-v3/include/std/streambuf 4b6625c7cbce87a5b4a6e79c315b0f1d libstdc++-v3/include/std/string 56ecd8ef9e669ad9046f93b40c6adeb0 libstdc++-v3/include/std/system_error ! 3c38cff34b5471d6ef6b8f5ebd334363 libstdc++-v3/include/std/thread ! 69c9fe68e28b9c6a300b100398e4eff3 libstdc++-v3/include/std/tuple ! f897c7829163f135b3c6d809faf503fe libstdc++-v3/include/std/type_traits 66c41d38d5277a5c6662a5c974f65fc4 libstdc++-v3/include/std/typeindex b23b42f90aab11eae50546959be31645 libstdc++-v3/include/std/unordered_map dfd5ad58503f3b684221edc4f6e722ff libstdc++-v3/include/std/unordered_set --- 89085,89093 ---- 64501e3b2fbc4c4fcc6b9fd5371cb059 libstdc++-v3/include/std/streambuf 4b6625c7cbce87a5b4a6e79c315b0f1d libstdc++-v3/include/std/string 56ecd8ef9e669ad9046f93b40c6adeb0 libstdc++-v3/include/std/system_error ! dccdfe68e5427fd832cd0354370e6c06 libstdc++-v3/include/std/thread ! 46f481cd2eb91f7888c38d80496d3388 libstdc++-v3/include/std/tuple ! 4c551da2d8c7c74501c172f3f883d84b libstdc++-v3/include/std/type_traits 66c41d38d5277a5c6662a5c974f65fc4 libstdc++-v3/include/std/typeindex b23b42f90aab11eae50546959be31645 libstdc++-v3/include/std/unordered_map dfd5ad58503f3b684221edc4f6e722ff libstdc++-v3/include/std/unordered_set *************** a4094c82f3ba5d7e68a914c90b79214b libstd *** 88958,88964 **** e87e59c79d2b3f93f5fd0fa92ee9e0c7 libstdc++-v3/libsupc++/hash_bytes.h 690b0f67d4b481c6b9f9f72b2e9b4d44 libstdc++-v3/libsupc++/initializer_list f20bfbd46865176cf4fecbb568c093b3 libstdc++-v3/libsupc++/nested_exception.cc ! e49ea10cde847b73597d36d45c51de7d libstdc++-v3/libsupc++/nested_exception.h e9f699afd84cf54734f0c77d5eab2ec4 libstdc++-v3/libsupc++/new 584e331a0a21b9516e20b5cd90d6e559 libstdc++-v3/libsupc++/new_handler.cc 4943db7a9c563dc00929780cb13048ee libstdc++-v3/libsupc++/new_op.cc --- 89210,89216 ---- e87e59c79d2b3f93f5fd0fa92ee9e0c7 libstdc++-v3/libsupc++/hash_bytes.h 690b0f67d4b481c6b9f9f72b2e9b4d44 libstdc++-v3/libsupc++/initializer_list f20bfbd46865176cf4fecbb568c093b3 libstdc++-v3/libsupc++/nested_exception.cc ! b65d472c3288171b79fb5ddd21385795 libstdc++-v3/libsupc++/nested_exception.h e9f699afd84cf54734f0c77d5eab2ec4 libstdc++-v3/libsupc++/new 584e331a0a21b9516e20b5cd90d6e559 libstdc++-v3/libsupc++/new_handler.cc 4943db7a9c563dc00929780cb13048ee libstdc++-v3/libsupc++/new_op.cc *************** e7a447f4ecc88a94e22d2d29b36695bb libstd *** 88992,88999 **** 1eb61946b03363aaa3abaa07798d2bf5 libstdc++-v3/python/hook.in 68b329da9893e34099c7d8ad5cb9c940 libstdc++-v3/python/libstdcxx/__init__.py 80cd5897795f46a84d32406b892ae0fc libstdc++-v3/python/libstdcxx/v6/__init__.py ! e2399789cb7af1668159dce284747aad libstdc++-v3/python/libstdcxx/v6/printers.py ! 21410df856486fa3f124e19f749dec2a libstdc++-v3/python/libstdcxx/v6/xmethods.py b1441422cec6381d9285b7681b666124 libstdc++-v3/scripts/check_compile 533e594add6e79910b0e557ba690fac6 libstdc++-v3/scripts/check_performance f480e111db2d50194a3e1f7014c9f422 libstdc++-v3/scripts/create_testsuite_files --- 89244,89251 ---- 1eb61946b03363aaa3abaa07798d2bf5 libstdc++-v3/python/hook.in 68b329da9893e34099c7d8ad5cb9c940 libstdc++-v3/python/libstdcxx/__init__.py 80cd5897795f46a84d32406b892ae0fc libstdc++-v3/python/libstdcxx/v6/__init__.py ! 419d316287eefb0e843c3e8bc4a83f39 libstdc++-v3/python/libstdcxx/v6/printers.py ! 7e3dc61e504bdb245728b286998bbb5a libstdc++-v3/python/libstdcxx/v6/xmethods.py b1441422cec6381d9285b7681b666124 libstdc++-v3/scripts/check_compile 533e594add6e79910b0e557ba690fac6 libstdc++-v3/scripts/check_performance f480e111db2d50194a3e1f7014c9f422 libstdc++-v3/scripts/create_testsuite_files *************** ca4c9e33da238aa7dd71a195ce77e48d libstd *** 89011,89017 **** 30665c8b6d46064d472972b057ac96cb libstdc++-v3/src/c++11/Makefile.am a71513788b148a7ade2ec04c6070aa8e libstdc++-v3/src/c++11/Makefile.in 4fdcbea8f299a029c4f5ea8d59f630c6 libstdc++-v3/src/c++11/chrono.cc ! 28ba9ca2926c19035cb646b2329710f4 libstdc++-v3/src/c++11/codecvt.cc 8bfae905b9eab9ab26ee92eb3978ab4a libstdc++-v3/src/c++11/compatibility-atomic-c++0x.cc 5d0b8ad9f6d2ee8e8040a8b666bf9e40 libstdc++-v3/src/c++11/compatibility-c++0x.cc 4c716fd1981b6de7c33c9ee168aaa28d libstdc++-v3/src/c++11/compatibility-chrono.cc --- 89263,89269 ---- 30665c8b6d46064d472972b057ac96cb libstdc++-v3/src/c++11/Makefile.am a71513788b148a7ade2ec04c6070aa8e libstdc++-v3/src/c++11/Makefile.in 4fdcbea8f299a029c4f5ea8d59f630c6 libstdc++-v3/src/c++11/chrono.cc ! a6ad6bfb7cce19b9cdf432a0e30251b9 libstdc++-v3/src/c++11/codecvt.cc 8bfae905b9eab9ab26ee92eb3978ab4a libstdc++-v3/src/c++11/compatibility-atomic-c++0x.cc 5d0b8ad9f6d2ee8e8040a8b666bf9e40 libstdc++-v3/src/c++11/compatibility-c++0x.cc 4c716fd1981b6de7c33c9ee168aaa28d libstdc++-v3/src/c++11/compatibility-chrono.cc *************** f46a3bd56f96f2edfe7c1cee363ec7f6 libstd *** 89022,89035 **** 98214d46bbe793351796b07e0a42a42d libstdc++-v3/src/c++11/cow-locale_init.cc 8b1fca2685592e27c6e2512aab409c53 libstdc++-v3/src/c++11/cow-shim_facets.cc a1e95554d798e75aaf108cf99555acbe libstdc++-v3/src/c++11/cow-sstream-inst.cc ! 11f38398949bd792c8cf299bb71de812 libstdc++-v3/src/c++11/cow-stdexcept.cc f24a3851a742dd9c9e641146183b51a8 libstdc++-v3/src/c++11/cow-string-inst.cc 2fc29df6c120b834cdf25d9a94bb04be libstdc++-v3/src/c++11/cow-wstring-inst.cc a85f17026568d8b29a5918c5fdb0de37 libstdc++-v3/src/c++11/ctype.cc 41ee708e71077f109227fa0484ffad3a libstdc++-v3/src/c++11/cxx11-hash_tr1.cc bcf497f5dbefc12d9990f4efe488613f libstdc++-v3/src/c++11/cxx11-ios_failure.cc 22e6b1d711ad689a29e2eb38cd9dcef9 libstdc++-v3/src/c++11/cxx11-locale-inst.cc ! 8109e2cc335547ce572629861f7ae9fa libstdc++-v3/src/c++11/cxx11-shim_facets.cc db46283df4058e114555a40560f0edf1 libstdc++-v3/src/c++11/cxx11-stdexcept.cc 8d48447ffd568ec3abde5f537c2b3e74 libstdc++-v3/src/c++11/cxx11-wlocale-inst.cc 301aa7be0da00bf9f33aa25e9cc98a1c libstdc++-v3/src/c++11/debug.cc --- 89274,89287 ---- 98214d46bbe793351796b07e0a42a42d libstdc++-v3/src/c++11/cow-locale_init.cc 8b1fca2685592e27c6e2512aab409c53 libstdc++-v3/src/c++11/cow-shim_facets.cc a1e95554d798e75aaf108cf99555acbe libstdc++-v3/src/c++11/cow-sstream-inst.cc ! 373fd73849df9a6375db3569ae20b005 libstdc++-v3/src/c++11/cow-stdexcept.cc f24a3851a742dd9c9e641146183b51a8 libstdc++-v3/src/c++11/cow-string-inst.cc 2fc29df6c120b834cdf25d9a94bb04be libstdc++-v3/src/c++11/cow-wstring-inst.cc a85f17026568d8b29a5918c5fdb0de37 libstdc++-v3/src/c++11/ctype.cc 41ee708e71077f109227fa0484ffad3a libstdc++-v3/src/c++11/cxx11-hash_tr1.cc bcf497f5dbefc12d9990f4efe488613f libstdc++-v3/src/c++11/cxx11-ios_failure.cc 22e6b1d711ad689a29e2eb38cd9dcef9 libstdc++-v3/src/c++11/cxx11-locale-inst.cc ! 7a654514ef56973ab346e80eec81da61 libstdc++-v3/src/c++11/cxx11-shim_facets.cc db46283df4058e114555a40560f0edf1 libstdc++-v3/src/c++11/cxx11-stdexcept.cc 8d48447ffd568ec3abde5f537c2b3e74 libstdc++-v3/src/c++11/cxx11-wlocale-inst.cc 301aa7be0da00bf9f33aa25e9cc98a1c libstdc++-v3/src/c++11/debug.cc *************** d94df9f2a6058590ea20cace55bbda8d libstd *** 89142,89147 **** --- 89394,89400 ---- 4ff5d11b8470405e4886cf3a3fa58ba2 libstdc++-v3/testsuite/17_intro/headers/c++2014/operator_names.cc c78c3f91f2a110ee69cf4e57c7ccd127 libstdc++-v3/testsuite/17_intro/headers/c++2014/stdc++.cc 3c8255034e81ad41296ae7287978bd19 libstdc++-v3/testsuite/17_intro/headers/c++2014/stdc++_multiple_inclusion.cc + e5203b13d9e40e55dfe4e0ca32686e3a libstdc++-v3/testsuite/17_intro/names.cc e79c04fb064066d3427dfe0922d74f0d libstdc++-v3/testsuite/17_intro/shared_with_static_deps.cc 5c8746cb5f66609444c6aaeaf1cf5931 libstdc++-v3/testsuite/17_intro/static.cc 81c3cdd8400d460b783381ce0bef986f libstdc++-v3/testsuite/17_intro/tag_type_explicit_ctor.cc *************** c8ebbcb48fda8f626b6f61c6fb97a2c8 libstd *** 89153,89159 **** 76c45a3f4bd00f799e3aacb175c7542b libstdc++-v3/testsuite/18_support/bad_alloc/what.cc de498383286dc76f11ac0897af7376e0 libstdc++-v3/testsuite/18_support/bad_cast/cons_virtual_derivation.cc 33ff4d51a05fcba82ed6be9fdda91c7b libstdc++-v3/testsuite/18_support/bad_cast/what.cc ! 9c917e72a163e95d3c40d70e2d1f3739 libstdc++-v3/testsuite/18_support/bad_exception/23591_thread-1.c 6ede12503dd76496fb09201ba4a92f5b libstdc++-v3/testsuite/18_support/bad_exception/59392.cc 6f6574c927a503ff06158bd6c2335a41 libstdc++-v3/testsuite/18_support/bad_exception/cons_virtual_derivation.cc a1a313355ff2fc1580e74e47bd27be7b libstdc++-v3/testsuite/18_support/bad_exception/what.cc --- 89406,89412 ---- 76c45a3f4bd00f799e3aacb175c7542b libstdc++-v3/testsuite/18_support/bad_alloc/what.cc de498383286dc76f11ac0897af7376e0 libstdc++-v3/testsuite/18_support/bad_cast/cons_virtual_derivation.cc 33ff4d51a05fcba82ed6be9fdda91c7b libstdc++-v3/testsuite/18_support/bad_cast/what.cc ! e64da0ce52d968dff95f39052df82c92 libstdc++-v3/testsuite/18_support/bad_exception/23591_thread-1.c 6ede12503dd76496fb09201ba4a92f5b libstdc++-v3/testsuite/18_support/bad_exception/59392.cc 6f6574c927a503ff06158bd6c2335a41 libstdc++-v3/testsuite/18_support/bad_exception/cons_virtual_derivation.cc a1a313355ff2fc1580e74e47bd27be7b libstdc++-v3/testsuite/18_support/bad_exception/what.cc *************** ee75c5fe37e5fea00956be77edbf747c libstd *** 89215,89220 **** --- 89468,89474 ---- 5da2bf5a207ebfe2d89180f264861833 libstdc++-v3/testsuite/18_support/nested_exception/51438.cc d46527a858184da7d3fac8c910097f04 libstdc++-v3/testsuite/18_support/nested_exception/62154.cc 39eac0cfb7026f80f116b7eec7f24093 libstdc++-v3/testsuite/18_support/nested_exception/68139.cc + 84077f35446b6875be83e147a23bde8b libstdc++-v3/testsuite/18_support/nested_exception/79114.cc f52d15093557d2f6fd588c288e47c940 libstdc++-v3/testsuite/18_support/nested_exception/cons.cc cb67da20acc5641854de8f06763adef4 libstdc++-v3/testsuite/18_support/nested_exception/nested_ptr.cc 834a6358c4319a06ec83cabe79a75444 libstdc++-v3/testsuite/18_support/nested_exception/rethrow_if_nested.cc *************** b45f741a937643d0bc7235bff9b9e2b4 libstd *** 89276,89282 **** 921ea794007c80adc95a70e7c131f27a libstdc++-v3/testsuite/19_diagnostics/headers/stdexcept/synopsis.cc 1e7340f9363818aa432f84df67f643ce libstdc++-v3/testsuite/19_diagnostics/headers/stdexcept/types_std.cc f1f67a7a537ed551a7b872e9c1100afb libstdc++-v3/testsuite/19_diagnostics/headers/system_error/34538.cc ! 50192a11dc76dca70935e44f5bcd9fcb libstdc++-v3/testsuite/19_diagnostics/headers/system_error/errc_std_c++0x.cc 0847edcc8c2ab21a6c6a84988a57d0e2 libstdc++-v3/testsuite/19_diagnostics/headers/system_error/std_c++0x_neg.cc aa74b549ffc9b1a6e15dda955a777a6e libstdc++-v3/testsuite/19_diagnostics/headers/system_error/types_std_c++0x.cc 108e77ea7d996f9a86c328588c7b7203 libstdc++-v3/testsuite/19_diagnostics/logic_error/cons_virtual_derivation.cc --- 89530,89536 ---- 921ea794007c80adc95a70e7c131f27a libstdc++-v3/testsuite/19_diagnostics/headers/stdexcept/synopsis.cc 1e7340f9363818aa432f84df67f643ce libstdc++-v3/testsuite/19_diagnostics/headers/stdexcept/types_std.cc f1f67a7a537ed551a7b872e9c1100afb libstdc++-v3/testsuite/19_diagnostics/headers/system_error/34538.cc ! 91e468aaae5558c9d50c9b489e3b92d7 libstdc++-v3/testsuite/19_diagnostics/headers/system_error/errc_std_c++0x.cc 0847edcc8c2ab21a6c6a84988a57d0e2 libstdc++-v3/testsuite/19_diagnostics/headers/system_error/std_c++0x_neg.cc aa74b549ffc9b1a6e15dda955a777a6e libstdc++-v3/testsuite/19_diagnostics/headers/system_error/types_std_c++0x.cc 108e77ea7d996f9a86c328588c7b7203 libstdc++-v3/testsuite/19_diagnostics/logic_error/cons_virtual_derivation.cc *************** f58b3d2922d9bdd559a6a159569f4d12 libstd *** 89342,89347 **** --- 89596,89603 ---- 2d898e5aa0cc331b0b76b0f076c857a2 libstdc++-v3/testsuite/20_util/allocator_traits/members/destroy.cc 19c34e72998570edc3bd31bd5078c383 libstdc++-v3/testsuite/20_util/allocator_traits/members/is_always_equal.cc 550e525d030133e052b6f7991bd7acb4 libstdc++-v3/testsuite/20_util/allocator_traits/members/max_size.cc + 3e8ffacb83d358b3a08a8ff84d9c0a72 libstdc++-v3/testsuite/20_util/allocator_traits/members/pointers.cc + 6287d72a814902ab68a360a4cadd57b0 libstdc++-v3/testsuite/20_util/allocator_traits/members/rebind_alloc.cc bff6dcfd662b987557a2c1554bbc83ad libstdc++-v3/testsuite/20_util/allocator_traits/members/select.cc e56f0e8ddf19336e411de95c2685e070 libstdc++-v3/testsuite/20_util/allocator_traits/requirements/explicit_instantiation.cc 7243d1a91e5122e2bebc6a30f8ea65bc libstdc++-v3/testsuite/20_util/allocator_traits/requirements/typedefs.cc *************** d89f6fb07684572a501cfdb2c4d55c37 libstd *** 89775,89780 **** --- 90031,90037 ---- a4a288b2d2a70de0346bd190c163013d libstdc++-v3/testsuite/20_util/pair/40925.cc 99a525748fc512545b0334ba2ceb5ce6 libstdc++-v3/testsuite/20_util/pair/44487.cc 8f02878973f833be005189171b4cd263 libstdc++-v3/testsuite/20_util/pair/70437.cc + 2d4c79c749099bb0f784eb806c4db85d libstdc++-v3/testsuite/20_util/pair/79141.cc 0a002d2309ee2dc915820989441f7eed libstdc++-v3/testsuite/20_util/pair/astuple/astuple.cc 0ab0c4f421a0d607d5f9ced3a8523fa3 libstdc++-v3/testsuite/20_util/pair/astuple/astuple_cpp14.cc f35631c8e1a0a50df8a35abd89d7b05e libstdc++-v3/testsuite/20_util/pair/astuple/constexpr_get.cc *************** c1f175dcc9e14d76e26cd101566ad7e4 libstd *** 89802,89807 **** --- 90059,90065 ---- d676c52c30dc0f3fee02ca1611d99cff libstdc++-v3/testsuite/20_util/pair/traits.cc c84dfb351801d6dfb5f541c78f973e9b libstdc++-v3/testsuite/20_util/pointer_safety/1.cc b0329d518a714b62417cec0f2f185827 libstdc++-v3/testsuite/20_util/pointer_traits/pointer_to.cc + e703c1e31fa4a7fc898466c63aeece8f libstdc++-v3/testsuite/20_util/pointer_traits/rebind.cc 2f045fd8f778b2a6b1b3f7c6b4afbd14 libstdc++-v3/testsuite/20_util/pointer_traits/requirements/explicit_instantiation.cc 4839893385372ad31433bad0a2fee64c libstdc++-v3/testsuite/20_util/pointer_traits/requirements/typedefs.cc 853aef1adaf036e23bee53c641f5aca2 libstdc++-v3/testsuite/20_util/rank/requirements/explicit_instantiation.cc *************** bd1fe6512b64ad90c2df37a7a24fca58 libstd *** 89827,89835 **** d578053aedc9553729c81089824d0c4c libstdc++-v3/testsuite/20_util/raw_storage_iterator/requirements/typedefs.cc d1e3ae4e52326f811b3d3badb9873a40 libstdc++-v3/testsuite/20_util/reference_wrapper/24803.cc ef1bd9ca22474d52c1e9ae85ab8084fb libstdc++-v3/testsuite/20_util/reference_wrapper/41792.cc 411973b51e160812d42f6a8a447f2393 libstdc++-v3/testsuite/20_util/reference_wrapper/invoke-2.cc 7c4e57253d8cd57d4db41f2a03bd60a2 libstdc++-v3/testsuite/20_util/reference_wrapper/invoke-3.cc ! 4fb6c4136180a262c0b0dbf4da9f541d libstdc++-v3/testsuite/20_util/reference_wrapper/invoke.cc bb64493851fc4d09275c56e3d0b28535 libstdc++-v3/testsuite/20_util/reference_wrapper/ref_neg.cc ecba0a29b38bdb76262a01e845dab61d libstdc++-v3/testsuite/20_util/reference_wrapper/requirements.cc a52afbc7a7d349d16f1fa31d84cfe25a libstdc++-v3/testsuite/20_util/reference_wrapper/result_type.cc --- 90085,90094 ---- d578053aedc9553729c81089824d0c4c libstdc++-v3/testsuite/20_util/raw_storage_iterator/requirements/typedefs.cc d1e3ae4e52326f811b3d3badb9873a40 libstdc++-v3/testsuite/20_util/reference_wrapper/24803.cc ef1bd9ca22474d52c1e9ae85ab8084fb libstdc++-v3/testsuite/20_util/reference_wrapper/41792.cc + 175371b8c91e7bc43f9b27d55096bd8e libstdc++-v3/testsuite/20_util/reference_wrapper/80504.cc 411973b51e160812d42f6a8a447f2393 libstdc++-v3/testsuite/20_util/reference_wrapper/invoke-2.cc 7c4e57253d8cd57d4db41f2a03bd60a2 libstdc++-v3/testsuite/20_util/reference_wrapper/invoke-3.cc ! 76920ddc6ec823085724f87e6893d5ed libstdc++-v3/testsuite/20_util/reference_wrapper/invoke.cc bb64493851fc4d09275c56e3d0b28535 libstdc++-v3/testsuite/20_util/reference_wrapper/ref_neg.cc ecba0a29b38bdb76262a01e845dab61d libstdc++-v3/testsuite/20_util/reference_wrapper/requirements.cc a52afbc7a7d349d16f1fa31d84cfe25a libstdc++-v3/testsuite/20_util/reference_wrapper/result_type.cc *************** cd9f32efbce974f7fa962caf7f284003 libstd *** 89983,89989 **** d5a7d0b863a5d2a743628adb83f2de44 libstdc++-v3/testsuite/20_util/tuple/56785.cc 7ccfe89f86ed931c69450bf0dfe29b56 libstdc++-v3/testsuite/20_util/tuple/60497.cc e785e7e65b569121eccdec534ad4ca88 libstdc++-v3/testsuite/20_util/tuple/61947.cc ! f0c96270a95be421d346f06ced861b37 libstdc++-v3/testsuite/20_util/tuple/67844.cc 8ed073f2f9e63722588c468ba39a5740 libstdc++-v3/testsuite/20_util/tuple/77395.cc f0e96ee38662e2d7fce0240a390813ad libstdc++-v3/testsuite/20_util/tuple/comparison_operators/35480_neg.cc b79799fec5549a94047c977a78e5536b libstdc++-v3/testsuite/20_util/tuple/comparison_operators/comparisons.cc --- 90242,90248 ---- d5a7d0b863a5d2a743628adb83f2de44 libstdc++-v3/testsuite/20_util/tuple/56785.cc 7ccfe89f86ed931c69450bf0dfe29b56 libstdc++-v3/testsuite/20_util/tuple/60497.cc e785e7e65b569121eccdec534ad4ca88 libstdc++-v3/testsuite/20_util/tuple/61947.cc ! 4142519a2a3c966808b22df3d01fbd02 libstdc++-v3/testsuite/20_util/tuple/67844.cc 8ed073f2f9e63722588c468ba39a5740 libstdc++-v3/testsuite/20_util/tuple/77395.cc f0e96ee38662e2d7fce0240a390813ad libstdc++-v3/testsuite/20_util/tuple/comparison_operators/35480_neg.cc b79799fec5549a94047c977a78e5536b libstdc++-v3/testsuite/20_util/tuple/comparison_operators/comparisons.cc *************** a0e208e3c8e14a69d9f91d62990cec5e libstd *** 89993,89998 **** --- 90252,90258 ---- 811a2ee9638d2e35d68917949c02c1a2 libstdc++-v3/testsuite/20_util/tuple/cons/44487.cc 1110bc031cfd63e12fb1169096a64fc1 libstdc++-v3/testsuite/20_util/tuple/cons/45228.cc 0236325c01dc2454d290d0cddd83407f libstdc++-v3/testsuite/20_util/tuple/cons/48476.cc + 8f009d4008d5361f200d27f952053115 libstdc++-v3/testsuite/20_util/tuple/cons/allocator_with_any.cc 7431479d7846feed1dfd0eab574dcc02 libstdc++-v3/testsuite/20_util/tuple/cons/allocators.cc 35946a0b34545f95afa9f7db9905684e libstdc++-v3/testsuite/20_util/tuple/cons/assignment.cc 03d6ef4ba9817e1b3f3a5f9abfc79894 libstdc++-v3/testsuite/20_util/tuple/cons/big_tuples.cc *************** a0e208e3c8e14a69d9f91d62990cec5e libstd *** 90000,90008 **** f2c34e193c19314affc8a00a6a445a92 libstdc++-v3/testsuite/20_util/tuple/cons/constexpr-3.cc a9cd6398ea857a03537f88c7e23f4b60 libstdc++-v3/testsuite/20_util/tuple/cons/constructor.cc 0aabd51cea226df6c82b765ef09c9441 libstdc++-v3/testsuite/20_util/tuple/cons/converting.cc ! 26bb13fcf5c5e3ab980dfe85b16b7496 libstdc++-v3/testsuite/20_util/tuple/cons/element_accepts_anything_byval.cc 7e5c8d7e9d12164bb1347a124ace6a37 libstdc++-v3/testsuite/20_util/tuple/cons/explicit_construct.cc ! 080671dc61cd5a1adb690c82272a7aa5 libstdc++-v3/testsuite/20_util/tuple/cons/nested_tuple_construct.cc 441b45a224b065aa135d3ec04bd9a4b2 libstdc++-v3/testsuite/20_util/tuple/cons/noexcept_move_construct.cc 6d4b2f9c5a2d54eeb908998a734b68cc libstdc++-v3/testsuite/20_util/tuple/creation_functions/23978.cc d6e605ae8f8f74c704aada7b4fd59244 libstdc++-v3/testsuite/20_util/tuple/creation_functions/48476.cc --- 90260,90268 ---- f2c34e193c19314affc8a00a6a445a92 libstdc++-v3/testsuite/20_util/tuple/cons/constexpr-3.cc a9cd6398ea857a03537f88c7e23f4b60 libstdc++-v3/testsuite/20_util/tuple/cons/constructor.cc 0aabd51cea226df6c82b765ef09c9441 libstdc++-v3/testsuite/20_util/tuple/cons/converting.cc ! 36a15e48b8177f1f89af2479ab527ca9 libstdc++-v3/testsuite/20_util/tuple/cons/element_accepts_anything_byval.cc 7e5c8d7e9d12164bb1347a124ace6a37 libstdc++-v3/testsuite/20_util/tuple/cons/explicit_construct.cc ! 59f63d947bdd0f8eb5998678a0f89b2e libstdc++-v3/testsuite/20_util/tuple/cons/nested_tuple_construct.cc 441b45a224b065aa135d3ec04bd9a4b2 libstdc++-v3/testsuite/20_util/tuple/cons/noexcept_move_construct.cc 6d4b2f9c5a2d54eeb908998a734b68cc libstdc++-v3/testsuite/20_util/tuple/creation_functions/23978.cc d6e605ae8f8f74c704aada7b4fd59244 libstdc++-v3/testsuite/20_util/tuple/creation_functions/48476.cc *************** ddca69c8a636f0d74dd18fdb9a59cdaf libstd *** 90096,90109 **** 6759230139352cf7e4cbd1160c4f3d00 libstdc++-v3/testsuite/20_util/weak_ptr/requirements/explicit_instantiation/2.cc f0a4325fad100579e7be08ef2827932c libstdc++-v3/testsuite/21_strings/basic_string/40160.cc c659e34abddf363d854dc6253404a9d7 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/copy.cc ! d8a2ccf379ce515692c37eb677ab7e2b libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/copy_assign.cc c3416011864e7ce9d5a55b206793e139 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/minimal.cc aa258ded545d1cd3df8ea4ac1ec417e1 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/move.cc 656dd139e9ae41b3c66988b59a2ecc89 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/move_assign.cc 841f6ed867f0ad73e72209e062575151 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/noexcept.cc 4eb72a72e905f892e1bba28a8a62b8f7 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/swap.cc a087eb140a7813456a62d452b76a7f9a libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/copy.cc ! 7a734694bc090c708e3ea58eff86a122 libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/copy_assign.cc 056e4a3cbb75f10e5ddded45726e456d libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/minimal.cc b89a84e542649c0f3c2d9d9fcc5c81db libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/move.cc 268f5470ef60f3f3b30cfb1b162c1314 libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/move_assign.cc --- 90356,90369 ---- 6759230139352cf7e4cbd1160c4f3d00 libstdc++-v3/testsuite/20_util/weak_ptr/requirements/explicit_instantiation/2.cc f0a4325fad100579e7be08ef2827932c libstdc++-v3/testsuite/21_strings/basic_string/40160.cc c659e34abddf363d854dc6253404a9d7 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/copy.cc ! bd2e21799f51a89c0755adb4b2a41d69 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/copy_assign.cc c3416011864e7ce9d5a55b206793e139 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/minimal.cc aa258ded545d1cd3df8ea4ac1ec417e1 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/move.cc 656dd139e9ae41b3c66988b59a2ecc89 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/move_assign.cc 841f6ed867f0ad73e72209e062575151 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/noexcept.cc 4eb72a72e905f892e1bba28a8a62b8f7 libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/swap.cc a087eb140a7813456a62d452b76a7f9a libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/copy.cc ! 4fe811423aef5a2023c1569e8f70eef8 libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/copy_assign.cc 056e4a3cbb75f10e5ddded45726e456d libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/minimal.cc b89a84e542649c0f3c2d9d9fcc5c81db libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/move.cc 268f5470ef60f3f3b30cfb1b162c1314 libstdc++-v3/testsuite/21_strings/basic_string/allocator/wchar_t/move_assign.cc *************** fb4c80aa2f3965e8a807cf632dd40511 libstd *** 90344,90356 **** 220c628cc24af6bbcbfd47f001616ef1 libstdc++-v3/testsuite/22_locale/codecvt/always_noconv/wchar_t/4.cc fb4c80aa2f3965e8a807cf632dd40511 libstdc++-v3/testsuite/22_locale/codecvt/always_noconv/wchar_t/wrapped_env.cc 080459f541e0f9c983b0c2511c319421 libstdc++-v3/testsuite/22_locale/codecvt/always_noconv/wchar_t/wrapped_locale.cc ! 23e0dac88b5421a326f5657685c0da9b libstdc++-v3/testsuite/22_locale/codecvt/char16_t.cc c97f26a8973c209ae0f7d360ad9f2fcc libstdc++-v3/testsuite/22_locale/codecvt/char32_t.cc c5071e3bdcb84c6edc7d311f74de1d4a libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/66417.cc a9d0a70ac98a0b17d2d1cc8c848a8efc libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/requirements/1.cc d1ed67ee033e3f14a4e84f4874b7f324 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8/69703.cc ff59d91f6f27e3904a6f0c4e0fc63592 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8/requirements/1.cc a6f9396f0c42a4c6d1d6de7ae30882e3 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8_utf16/66855.cc 50aec117b3903134dc297553a6e7d171 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8_utf16/requirements/1.cc fb446a5424dced8689e50d049d902d15 libstdc++-v3/testsuite/22_locale/codecvt/encoding/char/1.cc fb4c80aa2f3965e8a807cf632dd40511 libstdc++-v3/testsuite/22_locale/codecvt/encoding/char/wrapped_env.cc --- 90604,90624 ---- 220c628cc24af6bbcbfd47f001616ef1 libstdc++-v3/testsuite/22_locale/codecvt/always_noconv/wchar_t/4.cc fb4c80aa2f3965e8a807cf632dd40511 libstdc++-v3/testsuite/22_locale/codecvt/always_noconv/wchar_t/wrapped_env.cc 080459f541e0f9c983b0c2511c319421 libstdc++-v3/testsuite/22_locale/codecvt/always_noconv/wchar_t/wrapped_locale.cc ! 6ee90f7554749f98fff2a8ae4ceccdcd libstdc++-v3/testsuite/22_locale/codecvt/char16_t.cc c97f26a8973c209ae0f7d360ad9f2fcc libstdc++-v3/testsuite/22_locale/codecvt/char32_t.cc c5071e3bdcb84c6edc7d311f74de1d4a libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/66417.cc + b59930931ab0756e3a99b900cbadf303 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/79980.cc + 1c8529e26494931134d69c9d85c5864a libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/80041.cc + b401b5f49d27dcc14cb2f8fc5518ad0a libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/members.cc + 0232727b4ef5f9d7a55164d70075af2c libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/misaligned.cc a9d0a70ac98a0b17d2d1cc8c848a8efc libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf16/requirements/1.cc d1ed67ee033e3f14a4e84f4874b7f324 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8/69703.cc + 6d036cd16e2b152bc495f87d19ba75b6 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8/79980.cc + 48a19c06bd558fc0cc79f04b6eba976d libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8/members.cc ff59d91f6f27e3904a6f0c4e0fc63592 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8/requirements/1.cc a6f9396f0c42a4c6d1d6de7ae30882e3 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8_utf16/66855.cc + bc8366ae0b770af4ad2295e1b00ae27b libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8_utf16/79511.cc + 9fa291011214705ff29b9c858d91395f libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8_utf16/members.cc 50aec117b3903134dc297553a6e7d171 libstdc++-v3/testsuite/22_locale/codecvt/codecvt_utf8_utf16/requirements/1.cc fb446a5424dced8689e50d049d902d15 libstdc++-v3/testsuite/22_locale/codecvt/encoding/char/1.cc fb4c80aa2f3965e8a807cf632dd40511 libstdc++-v3/testsuite/22_locale/codecvt/encoding/char/wrapped_env.cc *************** b1ce9969455e540de745e2d87c8b887c libstd *** 90464,90469 **** --- 90732,90738 ---- 98e1abc66af0b85c9f3c9c2b24524da3 libstdc++-v3/testsuite/22_locale/collate_byname/requirements/explicit_instantiation.cc d8b7a2f14b32d3008122db738b02f581 libstdc++-v3/testsuite/22_locale/collate_byname/requirements/typedefs.cc 09a60faff43ef20f524afd2c618a80d8 libstdc++-v3/testsuite/22_locale/conversions/buffer/1.cc + 3fbaa9f6bcbaf536b0e6d981761efdbd libstdc++-v3/testsuite/22_locale/conversions/buffer/2.cc 4d18b9103ca960e892c39cbaedb03ab2 libstdc++-v3/testsuite/22_locale/conversions/buffer/requirements/typedefs.cc 212ac47998d5e5f83ad70307a2f9f5da libstdc++-v3/testsuite/22_locale/conversions/string/1.cc 1331a4635468632b7184619726887d3f libstdc++-v3/testsuite/22_locale/conversions/string/2.cc *************** e4de5c08ffff4a1f8cef20b81c98d055 libstd *** 91070,91080 **** 8ba5383d2c83d41436ab7cb60f2bd350 libstdc++-v3/testsuite/23_containers/deque/range_access.cc 3f5fa26773f1e5e686837e3e285f80d4 libstdc++-v3/testsuite/23_containers/deque/requirements/citerators.cc c40870452860e6fad5ab34761009be02 libstdc++-v3/testsuite/23_containers/deque/requirements/do_the_right_thing.cc ! d105d423e37a100e3bd42992212c0af3 libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/assign_neg.cc 520509db142c364f1d1020eab7c16124 libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor.cc ! 7e02cac287ab31af47d872d817aa9b6f libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor_1_neg.cc ! 76367ff3fba8bd4710bca9f0489ed4fd libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor_2_neg.cc ! 2a24a4ad37f3805108d63e18c9049ecc libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/insert_neg.cc 97aa1ba95cf29a5a876b22f004c1b4e7 libstdc++-v3/testsuite/23_containers/deque/requirements/exception/basic.cc ce57d97e5892ac0c034b85786bebfeb8 libstdc++-v3/testsuite/23_containers/deque/requirements/exception/generation_prohibited.cc 966a0c2685f234cef278918b7d3fee47 libstdc++-v3/testsuite/23_containers/deque/requirements/exception/propagation_consistent.cc --- 91339,91349 ---- 8ba5383d2c83d41436ab7cb60f2bd350 libstdc++-v3/testsuite/23_containers/deque/range_access.cc 3f5fa26773f1e5e686837e3e285f80d4 libstdc++-v3/testsuite/23_containers/deque/requirements/citerators.cc c40870452860e6fad5ab34761009be02 libstdc++-v3/testsuite/23_containers/deque/requirements/do_the_right_thing.cc ! 00b6688915ab972e4e18b127eea26945 libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/assign_neg.cc 520509db142c364f1d1020eab7c16124 libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor.cc ! 4c9053a446fefba73e029fbbe070aa10 libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor_1_neg.cc ! 5fa97c444179f2f061e353b494aae8d1 libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor_2_neg.cc ! be790dbe338ffeda705d66fef3efd617 libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/insert_neg.cc 97aa1ba95cf29a5a876b22f004c1b4e7 libstdc++-v3/testsuite/23_containers/deque/requirements/exception/basic.cc ce57d97e5892ac0c034b85786bebfeb8 libstdc++-v3/testsuite/23_containers/deque/requirements/exception/generation_prohibited.cc 966a0c2685f234cef278918b7d3fee47 libstdc++-v3/testsuite/23_containers/deque/requirements/exception/propagation_consistent.cc *************** afe322595a50c38f5c423219db9a2ab7 libstd *** 91288,91304 **** 392e09d626eb15b87a85179701a013fe libstdc++-v3/testsuite/23_containers/list/operations/4.cc 8c0e71f82c6aa71605025658695091df libstdc++-v3/testsuite/23_containers/list/operations/4.h baf17eb1f8720d03177fa74df349a25c libstdc++-v3/testsuite/23_containers/list/operations/42352.cc 4e81fecb380bce60f017cd8ca4c391ad libstdc++-v3/testsuite/23_containers/list/operations/splice/const_iterator.cc 0993ab3e75bdd72f150208e1ce26e2d7 libstdc++-v3/testsuite/23_containers/list/pthread1.cc 0e9a6d6976cd8da10cd323367e1e4445 libstdc++-v3/testsuite/23_containers/list/pthread5.cc 72d8def126c164b1e0096aedf7f0cda1 libstdc++-v3/testsuite/23_containers/list/range_access.cc b3d78210ad719db7c423263f0cc0c0f9 libstdc++-v3/testsuite/23_containers/list/requirements/citerators.cc 3a2ca3cf41a4cc935d5d1bc8c8e83980 libstdc++-v3/testsuite/23_containers/list/requirements/do_the_right_thing.cc ! cb96fcee0257aaf5bd505de62de9f4d9 libstdc++-v3/testsuite/23_containers/list/requirements/dr438/assign_neg.cc fbc50fc7fdc8b0c1978d4ff5142fc8a7 libstdc++-v3/testsuite/23_containers/list/requirements/dr438/constructor.cc ! 11f2c9e7c83ebda5587b70fff43c848c libstdc++-v3/testsuite/23_containers/list/requirements/dr438/constructor_1_neg.cc ! 177d5b0cc0bf371984fe744956a8bbfc libstdc++-v3/testsuite/23_containers/list/requirements/dr438/constructor_2_neg.cc ! cdf3780ff70d87c90a748acc4c1c87fd libstdc++-v3/testsuite/23_containers/list/requirements/dr438/insert_neg.cc 579de9484cad65a10269f1a93775ddff libstdc++-v3/testsuite/23_containers/list/requirements/exception/basic.cc 020387b73e6d3672d075e285e41b283b libstdc++-v3/testsuite/23_containers/list/requirements/exception/generation_prohibited.cc 08d3024d935eb882c5152581dedd343a libstdc++-v3/testsuite/23_containers/list/requirements/exception/propagation_consistent.cc --- 91557,91575 ---- 392e09d626eb15b87a85179701a013fe libstdc++-v3/testsuite/23_containers/list/operations/4.cc 8c0e71f82c6aa71605025658695091df libstdc++-v3/testsuite/23_containers/list/operations/4.h baf17eb1f8720d03177fa74df349a25c libstdc++-v3/testsuite/23_containers/list/operations/42352.cc + 1f64b45c836b72e5943e2165afb1c62b libstdc++-v3/testsuite/23_containers/list/operations/78389.cc + 2e48ac629e274a125bbb34b2e932fd5b libstdc++-v3/testsuite/23_containers/list/operations/80034.cc 4e81fecb380bce60f017cd8ca4c391ad libstdc++-v3/testsuite/23_containers/list/operations/splice/const_iterator.cc 0993ab3e75bdd72f150208e1ce26e2d7 libstdc++-v3/testsuite/23_containers/list/pthread1.cc 0e9a6d6976cd8da10cd323367e1e4445 libstdc++-v3/testsuite/23_containers/list/pthread5.cc 72d8def126c164b1e0096aedf7f0cda1 libstdc++-v3/testsuite/23_containers/list/range_access.cc b3d78210ad719db7c423263f0cc0c0f9 libstdc++-v3/testsuite/23_containers/list/requirements/citerators.cc 3a2ca3cf41a4cc935d5d1bc8c8e83980 libstdc++-v3/testsuite/23_containers/list/requirements/do_the_right_thing.cc ! 71644fc3cea8d4927eaecc61104589e6 libstdc++-v3/testsuite/23_containers/list/requirements/dr438/assign_neg.cc fbc50fc7fdc8b0c1978d4ff5142fc8a7 libstdc++-v3/testsuite/23_containers/list/requirements/dr438/constructor.cc ! a95ecdb5c9649c07d202dc39a894bb26 libstdc++-v3/testsuite/23_containers/list/requirements/dr438/constructor_1_neg.cc ! 11bade1f6e03097381a016a5d6535be3 libstdc++-v3/testsuite/23_containers/list/requirements/dr438/constructor_2_neg.cc ! 1f81727e88de074cbfa406afff71338a libstdc++-v3/testsuite/23_containers/list/requirements/dr438/insert_neg.cc 579de9484cad65a10269f1a93775ddff libstdc++-v3/testsuite/23_containers/list/requirements/exception/basic.cc 020387b73e6d3672d075e285e41b283b libstdc++-v3/testsuite/23_containers/list/requirements/exception/generation_prohibited.cc 08d3024d935eb882c5152581dedd343a libstdc++-v3/testsuite/23_containers/list/requirements/exception/propagation_consistent.cc *************** a370015a548ea46de698be7b48f57d2a libstd *** 91363,91375 **** a3812737025b491710d1698d2ea6162b libstdc++-v3/testsuite/23_containers/map/modifiers/insert/3.cc 22891d45e5dc102123fab0d89431f108 libstdc++-v3/testsuite/23_containers/map/modifiers/insert/4.cc aa69bb2dcbbaba5e72c99b8dfc7d8c24 libstdc++-v3/testsuite/23_containers/map/modifiers/insert/5.cc ! 5d7c74c76425e9c9d435fc61f0831962 libstdc++-v3/testsuite/23_containers/map/modifiers/insert_or_assign/1.cc 562e91f60a9710aa8ab9308eea34384a libstdc++-v3/testsuite/23_containers/map/modifiers/swap/1.cc 1f7b7237f3c472f92d51fa6596767ae9 libstdc++-v3/testsuite/23_containers/map/modifiers/swap/2.cc 18d8078711be8b3fc1e97657fd94f3ff libstdc++-v3/testsuite/23_containers/map/modifiers/swap/3.cc eefef90f865563e42b108d079d0574b6 libstdc++-v3/testsuite/23_containers/map/modifiers/try_emplace/1.cc d206e0688df88b887aa15e2613bef41a libstdc++-v3/testsuite/23_containers/map/operations/1.cc ! 1ec389fcd0abd818ff364d502d8c5259 libstdc++-v3/testsuite/23_containers/map/operations/2.cc 9676e11eb11bdfcf07900af58d72d9ce libstdc++-v3/testsuite/23_containers/map/operations/31440.cc 7a7c1ccc55bf0199f88221c3d2578fdd libstdc++-v3/testsuite/23_containers/map/operations/count.cc 8ad8d5bc8c38901b744af0bd4b2f3b2f libstdc++-v3/testsuite/23_containers/map/operators/1.cc --- 91634,91646 ---- a3812737025b491710d1698d2ea6162b libstdc++-v3/testsuite/23_containers/map/modifiers/insert/3.cc 22891d45e5dc102123fab0d89431f108 libstdc++-v3/testsuite/23_containers/map/modifiers/insert/4.cc aa69bb2dcbbaba5e72c99b8dfc7d8c24 libstdc++-v3/testsuite/23_containers/map/modifiers/insert/5.cc ! 2b041f3262a88384efa607ee67c25905 libstdc++-v3/testsuite/23_containers/map/modifiers/insert_or_assign/1.cc 562e91f60a9710aa8ab9308eea34384a libstdc++-v3/testsuite/23_containers/map/modifiers/swap/1.cc 1f7b7237f3c472f92d51fa6596767ae9 libstdc++-v3/testsuite/23_containers/map/modifiers/swap/2.cc 18d8078711be8b3fc1e97657fd94f3ff libstdc++-v3/testsuite/23_containers/map/modifiers/swap/3.cc eefef90f865563e42b108d079d0574b6 libstdc++-v3/testsuite/23_containers/map/modifiers/try_emplace/1.cc d206e0688df88b887aa15e2613bef41a libstdc++-v3/testsuite/23_containers/map/operations/1.cc ! d083f0d14f203710d5890e58a83a899b libstdc++-v3/testsuite/23_containers/map/operations/2.cc 9676e11eb11bdfcf07900af58d72d9ce libstdc++-v3/testsuite/23_containers/map/operations/31440.cc 7a7c1ccc55bf0199f88221c3d2578fdd libstdc++-v3/testsuite/23_containers/map/operations/count.cc 8ad8d5bc8c38901b744af0bd4b2f3b2f libstdc++-v3/testsuite/23_containers/map/operators/1.cc *************** b5ee5664115d601c354009b36e2e2480 libstd *** 91437,91443 **** 37e87d983414e952224a24686ddb260b libstdc++-v3/testsuite/23_containers/multimap/modifiers/swap/2.cc ce998e612aa7037557476db259df644d libstdc++-v3/testsuite/23_containers/multimap/modifiers/swap/3.cc e6adf46ee8ec6be9eb5f0269b0177d52 libstdc++-v3/testsuite/23_containers/multimap/operations/1.cc ! 5fa57744747bfd2919a8977f39b24c88 libstdc++-v3/testsuite/23_containers/multimap/operations/2.cc e92a4fb1cb563d3d7a77d0ce86c383e2 libstdc++-v3/testsuite/23_containers/multimap/operations/count.cc 9c3dc0c6dd12e7b23ad9600a83e0fbe3 libstdc++-v3/testsuite/23_containers/multimap/range_access.cc 0238922d86527b9285736c5c6b3d6702 libstdc++-v3/testsuite/23_containers/multimap/requirements/citerators.cc --- 91708,91714 ---- 37e87d983414e952224a24686ddb260b libstdc++-v3/testsuite/23_containers/multimap/modifiers/swap/2.cc ce998e612aa7037557476db259df644d libstdc++-v3/testsuite/23_containers/multimap/modifiers/swap/3.cc e6adf46ee8ec6be9eb5f0269b0177d52 libstdc++-v3/testsuite/23_containers/multimap/operations/1.cc ! 2e639e98c975d3b98025a2c8170a4a18 libstdc++-v3/testsuite/23_containers/multimap/operations/2.cc e92a4fb1cb563d3d7a77d0ce86c383e2 libstdc++-v3/testsuite/23_containers/multimap/operations/count.cc 9c3dc0c6dd12e7b23ad9600a83e0fbe3 libstdc++-v3/testsuite/23_containers/multimap/range_access.cc 0238922d86527b9285736c5c6b3d6702 libstdc++-v3/testsuite/23_containers/multimap/requirements/citerators.cc *************** be5d1113eb21ee6315bca0cc0d7fcdaa libstd *** 91499,91505 **** 583ecfe2bd3cac90a5a5024dad3f5e10 libstdc++-v3/testsuite/23_containers/multiset/modifiers/swap/2.cc 08f7d6ed0956ce25ae348f646bdcb4c5 libstdc++-v3/testsuite/23_containers/multiset/modifiers/swap/3.cc 1c6fa7ae25e3bbe4007e5a7293f2b6c2 libstdc++-v3/testsuite/23_containers/multiset/operations/1.cc ! 2e53c89c1facfaefa80127bd7b098897 libstdc++-v3/testsuite/23_containers/multiset/operations/2.cc f1943ae1c1e99667d2826df23e317d7b libstdc++-v3/testsuite/23_containers/multiset/operations/count.cc 92833c68b6786d8e2efb97893157ac29 libstdc++-v3/testsuite/23_containers/multiset/range_access.cc a6b5c715c6f43abe298b18850c842ec6 libstdc++-v3/testsuite/23_containers/multiset/requirements/citerators.cc --- 91770,91776 ---- 583ecfe2bd3cac90a5a5024dad3f5e10 libstdc++-v3/testsuite/23_containers/multiset/modifiers/swap/2.cc 08f7d6ed0956ce25ae348f646bdcb4c5 libstdc++-v3/testsuite/23_containers/multiset/modifiers/swap/3.cc 1c6fa7ae25e3bbe4007e5a7293f2b6c2 libstdc++-v3/testsuite/23_containers/multiset/operations/1.cc ! 86db4dd5565fd5e75da7f4dd25f6d1b9 libstdc++-v3/testsuite/23_containers/multiset/operations/2.cc f1943ae1c1e99667d2826df23e317d7b libstdc++-v3/testsuite/23_containers/multiset/operations/count.cc 92833c68b6786d8e2efb97893157ac29 libstdc++-v3/testsuite/23_containers/multiset/range_access.cc a6b5c715c6f43abe298b18850c842ec6 libstdc++-v3/testsuite/23_containers/multiset/requirements/citerators.cc *************** c86735e592aa5ba784b15ea808f6ddfb libstd *** 91578,91584 **** 91328528ce9a1f2f64229621ef6026f2 libstdc++-v3/testsuite/23_containers/set/modifiers/swap/2.cc 3413b3caca0da9aacaef00bcacca158b libstdc++-v3/testsuite/23_containers/set/modifiers/swap/3.cc 7ac92ab110377a785ff2a862ea8c0dfb libstdc++-v3/testsuite/23_containers/set/operations/1.cc ! 68372a642a0e4864443b2e6e2b521536 libstdc++-v3/testsuite/23_containers/set/operations/2.cc 56e210c3fc9ea1e41773aadc10677f86 libstdc++-v3/testsuite/23_containers/set/operations/count.cc 5fd105acc6762bbe74836c6ef51685ab libstdc++-v3/testsuite/23_containers/set/operators/1_neg.cc dd7a84c8f90dd451facb3cc997e08c36 libstdc++-v3/testsuite/23_containers/set/range_access.cc --- 91849,91855 ---- 91328528ce9a1f2f64229621ef6026f2 libstdc++-v3/testsuite/23_containers/set/modifiers/swap/2.cc 3413b3caca0da9aacaef00bcacca158b libstdc++-v3/testsuite/23_containers/set/modifiers/swap/3.cc 7ac92ab110377a785ff2a862ea8c0dfb libstdc++-v3/testsuite/23_containers/set/operations/1.cc ! dffc56a4506548101c654e6223a05ac1 libstdc++-v3/testsuite/23_containers/set/operations/2.cc 56e210c3fc9ea1e41773aadc10677f86 libstdc++-v3/testsuite/23_containers/set/operations/count.cc 5fd105acc6762bbe74836c6ef51685ab libstdc++-v3/testsuite/23_containers/set/operators/1_neg.cc dd7a84c8f90dd451facb3cc997e08c36 libstdc++-v3/testsuite/23_containers/set/range_access.cc *************** ccf6757beecd2458995e637cb8ec2454 libstd *** 91657,91663 **** 15a2060773a1ddb77650ac6e277efaa7 libstdc++-v3/testsuite/23_containers/unordered_map/insert/map_single_move-2.cc 5b6f157723927e00538fc5ebe0aab86b libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/61667.cc 4463eb1258ccb63871ee50666939717f libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/emplace.cc ! b19dc40358c42037b60b6a71f749fe69 libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/insert_or_assign.cc 869fb9456d63f3b0d412171a478bf708 libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/reserve.cc 29af96852365fca1755437b26e319291 libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/try_emplace.cc e39f41bf420df7d0f0eff7fb9b757859 libstdc++-v3/testsuite/23_containers/unordered_map/observers.cc --- 91928,91934 ---- 15a2060773a1ddb77650ac6e277efaa7 libstdc++-v3/testsuite/23_containers/unordered_map/insert/map_single_move-2.cc 5b6f157723927e00538fc5ebe0aab86b libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/61667.cc 4463eb1258ccb63871ee50666939717f libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/emplace.cc ! 560d77a4a3d6c0e95bd37cb8c2d55af6 libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/insert_or_assign.cc 869fb9456d63f3b0d412171a478bf708 libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/reserve.cc 29af96852365fca1755437b26e319291 libstdc++-v3/testsuite/23_containers/unordered_map/modifiers/try_emplace.cc e39f41bf420df7d0f0eff7fb9b757859 libstdc++-v3/testsuite/23_containers/unordered_map/observers.cc *************** c7b7fb2877f61a0dfa091f87e0222583 libstd *** 92062,92072 **** beca24159c546f7b7dc7a441fa54999f libstdc++-v3/testsuite/23_containers/vector/range_access.cc e2fdb0a5b48c9ccacf99bcc78126ac38 libstdc++-v3/testsuite/23_containers/vector/requirements/citerators.cc ec99a4d22b280521a4f97ae79871c67d libstdc++-v3/testsuite/23_containers/vector/requirements/do_the_right_thing.cc ! f937ba33eb2e4f637a9913dd546f39f8 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/assign_neg.cc e207c5018f8e3abb90b44982cb31b156 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor.cc ! 3f334a75b43b58ae9df636f85aab29bf libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor_1_neg.cc ! 533ead37480d35f18f49bf2e2eec1211 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor_2_neg.cc ! d73c44e44b81c3581f9dbef104ebce36 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/insert_neg.cc a6c4b5ddc14b52902745f50890520ff9 libstdc++-v3/testsuite/23_containers/vector/requirements/exception/basic.cc 2b8aac91ece89b6f8008eb939b094c47 libstdc++-v3/testsuite/23_containers/vector/requirements/exception/generation_prohibited.cc bb4be8047d48fb6e365e3ab3a3ea063f libstdc++-v3/testsuite/23_containers/vector/requirements/exception/propagation_consistent.cc --- 92333,92343 ---- beca24159c546f7b7dc7a441fa54999f libstdc++-v3/testsuite/23_containers/vector/range_access.cc e2fdb0a5b48c9ccacf99bcc78126ac38 libstdc++-v3/testsuite/23_containers/vector/requirements/citerators.cc ec99a4d22b280521a4f97ae79871c67d libstdc++-v3/testsuite/23_containers/vector/requirements/do_the_right_thing.cc ! ea7263977460f0a788b92587e40a3d33 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/assign_neg.cc e207c5018f8e3abb90b44982cb31b156 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor.cc ! 615ab340b74ab479307ff937fe75a910 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor_1_neg.cc ! 144ec3f78751564fad68dc10af58ed67 libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor_2_neg.cc ! 4f5c9330870db42967584602e3137c8d libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/insert_neg.cc a6c4b5ddc14b52902745f50890520ff9 libstdc++-v3/testsuite/23_containers/vector/requirements/exception/basic.cc 2b8aac91ece89b6f8008eb939b094c47 libstdc++-v3/testsuite/23_containers/vector/requirements/exception/generation_prohibited.cc bb4be8047d48fb6e365e3ab3a3ea063f libstdc++-v3/testsuite/23_containers/vector/requirements/exception/propagation_consistent.cc *************** fd7dbc508f736ff753e97b3450bb2777 libstd *** 92329,92335 **** ca976b190abea2e5187343ff5ed201c0 libstdc++-v3/testsuite/25_algorithms/lower_bound/2.cc 79262bb2dd874fed4d031b5866994123 libstdc++-v3/testsuite/25_algorithms/lower_bound/33613.cc f3bcfbb7cff9aba454e55e19bcf2baf8 libstdc++-v3/testsuite/25_algorithms/lower_bound/check_type.cc ! 20a0ac6a9a8d6fefcde91c6b9e41e0c6 libstdc++-v3/testsuite/25_algorithms/lower_bound/debug/irreflexive.cc 63320e25fd7aa7498b9e83cc5cd18506 libstdc++-v3/testsuite/25_algorithms/lower_bound/no_operator_ne.cc 7539641d39861d52133a38d930f614e5 libstdc++-v3/testsuite/25_algorithms/lower_bound/partitioned.cc b081808f9153f80a70b6a6a0bcb10b0a libstdc++-v3/testsuite/25_algorithms/lower_bound/requirements/explicit_instantiation/2.cc --- 92600,92606 ---- ca976b190abea2e5187343ff5ed201c0 libstdc++-v3/testsuite/25_algorithms/lower_bound/2.cc 79262bb2dd874fed4d031b5866994123 libstdc++-v3/testsuite/25_algorithms/lower_bound/33613.cc f3bcfbb7cff9aba454e55e19bcf2baf8 libstdc++-v3/testsuite/25_algorithms/lower_bound/check_type.cc ! 3e6fe50fc145e9c576beca1e247e7da3 libstdc++-v3/testsuite/25_algorithms/lower_bound/debug/irreflexive.cc 63320e25fd7aa7498b9e83cc5cd18506 libstdc++-v3/testsuite/25_algorithms/lower_bound/no_operator_ne.cc 7539641d39861d52133a38d930f614e5 libstdc++-v3/testsuite/25_algorithms/lower_bound/partitioned.cc b081808f9153f80a70b6a6a0bcb10b0a libstdc++-v3/testsuite/25_algorithms/lower_bound/requirements/explicit_instantiation/2.cc *************** bd1952f4d14db0319e3ceeee78d6a33c libstd *** 92510,92515 **** --- 92781,92787 ---- 881597214aaf235e830cd6dd1dd8197a libstdc++-v3/testsuite/25_algorithms/rotate_copy/requirements/explicit_instantiation/2.cc 528ba5846be05a18bc76e07ecf18d6d1 libstdc++-v3/testsuite/25_algorithms/rotate_copy/requirements/explicit_instantiation/pod.cc 4d081cf9ad03fb57fbd2678f9bbec070 libstdc++-v3/testsuite/25_algorithms/search/1.cc + d97984c977a680e56edcfa755c94e699 libstdc++-v3/testsuite/25_algorithms/search/78346.cc f3d79be3cdbd0dc9197ce75ccc0fc574 libstdc++-v3/testsuite/25_algorithms/search/check_type.cc 74cbad7d7dee016bc80c9108b1b7eecb libstdc++-v3/testsuite/25_algorithms/search/requirements/explicit_instantiation/2.cc 0bd540e9a4f03bac092cbbb7e4dc1329 libstdc++-v3/testsuite/25_algorithms/search/requirements/explicit_instantiation/pod.cc *************** a40c7fe287ee052ee8d9602dde2d00fd libstd *** 92544,92549 **** --- 92816,92822 ---- 829760303869b70eeeb31a2b0949d5a4 libstdc++-v3/testsuite/25_algorithms/sort/34095.cc 310c23e9a6781ad0eac2fe96736f828d libstdc++-v3/testsuite/25_algorithms/sort/34636.cc 9e9978bbc94d89eefed75e43f8d1f455 libstdc++-v3/testsuite/25_algorithms/sort/35588.cc + 4b76c17dba24d84cee7c85cb520677da libstdc++-v3/testsuite/25_algorithms/sort/78991.cc dba4752d614856959d0a317696af20a8 libstdc++-v3/testsuite/25_algorithms/sort/check_compare_by_value.cc 20aea69177cbac520e733da49eee4989 libstdc++-v3/testsuite/25_algorithms/sort/moveable.cc 7e7ab93b61d1a7e0794841c7dd40bea3 libstdc++-v3/testsuite/25_algorithms/sort/random_test.cc *************** a71f8761363c8add22d049c4c8ea59fc libstd *** 92939,92945 **** 272a1827e8199d92bf8ba9cd853f90ba libstdc++-v3/testsuite/26_numerics/random/uniform_int_distribution/requirements/typedefs.cc 64de8e7e1b426c525a1b526e77f8db40 libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/cons/default.cc ed6b9c29c8ac1e12a6d08e584e56b9da libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/cons/parms.cc ! acfd8373a2f89988d424c1b2599d8a96 libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/64351.cc 1570e5563ebc3689d20a22b70c2e8d30 libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/equal.cc 09695e0e42a5b1d86b444b40d7fa26d3 libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/inequal.cc 9a815c1f9a093992986e779c22b14d8d libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/serialize.cc --- 93212,93218 ---- 272a1827e8199d92bf8ba9cd853f90ba libstdc++-v3/testsuite/26_numerics/random/uniform_int_distribution/requirements/typedefs.cc 64de8e7e1b426c525a1b526e77f8db40 libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/cons/default.cc ed6b9c29c8ac1e12a6d08e584e56b9da libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/cons/parms.cc ! 61c346d5cbf3f5be5e7368e68827a74b libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/64351.cc 1570e5563ebc3689d20a22b70c2e8d30 libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/equal.cc 09695e0e42a5b1d86b444b40d7fa26d3 libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/inequal.cc 9a815c1f9a093992986e779c22b14d8d libstdc++-v3/testsuite/26_numerics/random/uniform_real_distribution/operators/serialize.cc *************** e78f2cb7a78943ee4298174c7a0c0162 libstd *** 93761,93773 **** ec69ce704f589a0604916d68e620074e libstdc++-v3/testsuite/27_io/ios_base/sync_with_stdio/2.cc 16e1bc9a7eeccc2360ca90333790cb32 libstdc++-v3/testsuite/27_io/ios_base/sync_with_stdio/9523.cc a50303d9c9896160f8efc660fc348cf0 libstdc++-v3/testsuite/27_io/ios_base/types/fmtflags/bitmask_operators.cc ! 5217e055030b19e2df033c86d80ee667 libstdc++-v3/testsuite/27_io/ios_base/types/fmtflags/case_label.cc 8c54c54ffca3b0efc5640cace75fd378 libstdc++-v3/testsuite/27_io/ios_base/types/fmtflags/constexpr_operators.cc 6700b4fc80be1eb1383d107c8f91a907 libstdc++-v3/testsuite/27_io/ios_base/types/iostate/bitmask_operators.cc ! 3e14cdb631dd712b8a857e7468d6033e libstdc++-v3/testsuite/27_io/ios_base/types/iostate/case_label.cc 51263c305bda563bf7e4334a81e381bb libstdc++-v3/testsuite/27_io/ios_base/types/iostate/constexpr_operators.cc 196ac594ba61a55f95c89a5f8d8320ea libstdc++-v3/testsuite/27_io/ios_base/types/openmode/bitmask_operators.cc ! e2ef7c84f2d8dba8f3e665916cbf939e libstdc++-v3/testsuite/27_io/ios_base/types/openmode/case_label.cc 50ed0d88c7c0394322cd5a7930603c0b libstdc++-v3/testsuite/27_io/ios_base/types/openmode/constexpr_operators.cc 65173e26112f63f8b891d939d9da81c3 libstdc++-v3/testsuite/27_io/ios_base/types/seekdir/case_label.cc 27a21b18db4b52b3593690da3847d761 libstdc++-v3/testsuite/27_io/manipulators/adjustfield/char/1.cc --- 94034,94046 ---- ec69ce704f589a0604916d68e620074e libstdc++-v3/testsuite/27_io/ios_base/sync_with_stdio/2.cc 16e1bc9a7eeccc2360ca90333790cb32 libstdc++-v3/testsuite/27_io/ios_base/sync_with_stdio/9523.cc a50303d9c9896160f8efc660fc348cf0 libstdc++-v3/testsuite/27_io/ios_base/types/fmtflags/bitmask_operators.cc ! 567ef869ead986353d767ae3ffdef00c libstdc++-v3/testsuite/27_io/ios_base/types/fmtflags/case_label.cc 8c54c54ffca3b0efc5640cace75fd378 libstdc++-v3/testsuite/27_io/ios_base/types/fmtflags/constexpr_operators.cc 6700b4fc80be1eb1383d107c8f91a907 libstdc++-v3/testsuite/27_io/ios_base/types/iostate/bitmask_operators.cc ! 243be0344f58b045b2700735b472882d libstdc++-v3/testsuite/27_io/ios_base/types/iostate/case_label.cc 51263c305bda563bf7e4334a81e381bb libstdc++-v3/testsuite/27_io/ios_base/types/iostate/constexpr_operators.cc 196ac594ba61a55f95c89a5f8d8320ea libstdc++-v3/testsuite/27_io/ios_base/types/openmode/bitmask_operators.cc ! 0f7d4e1275750b05559e3aca947e81b6 libstdc++-v3/testsuite/27_io/ios_base/types/openmode/case_label.cc 50ed0d88c7c0394322cd5a7930603c0b libstdc++-v3/testsuite/27_io/ios_base/types/openmode/constexpr_operators.cc 65173e26112f63f8b891d939d9da81c3 libstdc++-v3/testsuite/27_io/ios_base/types/seekdir/case_label.cc 27a21b18db4b52b3593690da3847d761 libstdc++-v3/testsuite/27_io/manipulators/adjustfield/char/1.cc *************** a9e1c9bbd0e1eb92c98d6868d7900b6d libstd *** 93888,93894 **** b715c45a6677f269807dab0bbcf0ee1d libstdc++-v3/testsuite/27_io/objects/wchar_t/9_xin.in f1681f97a9f016f33aa4240ffc054f7f libstdc++-v3/testsuite/27_io/objects/wchar_t/dr455.cc c5a1bba63600a3c89a74a6eaf107c076 libstdc++-v3/testsuite/27_io/rvalue_streams-2.cc ! c5c81e05480054b93354031ef1515eb0 libstdc++-v3/testsuite/27_io/rvalue_streams.cc 674fe833ce8b1c2414c00970719852b0 libstdc++-v3/testsuite/27_io/types/1.cc 11573fa1a1261ae909084be15debf07c libstdc++-v3/testsuite/27_io/types/2.cc f02ab13e31cea5f9070bfaea25b1b231 libstdc++-v3/testsuite/27_io/types/3.cc --- 94161,94167 ---- b715c45a6677f269807dab0bbcf0ee1d libstdc++-v3/testsuite/27_io/objects/wchar_t/9_xin.in f1681f97a9f016f33aa4240ffc054f7f libstdc++-v3/testsuite/27_io/objects/wchar_t/dr455.cc c5a1bba63600a3c89a74a6eaf107c076 libstdc++-v3/testsuite/27_io/rvalue_streams-2.cc ! 2612a437d8790fcbf5fd9ffc694f50b7 libstdc++-v3/testsuite/27_io/rvalue_streams.cc 674fe833ce8b1c2414c00970719852b0 libstdc++-v3/testsuite/27_io/types/1.cc 11573fa1a1261ae909084be15debf07c libstdc++-v3/testsuite/27_io/types/2.cc f02ab13e31cea5f9070bfaea25b1b231 libstdc++-v3/testsuite/27_io/types/3.cc *************** e7067fbe523c6772056bbd3db6b5a262 libstd *** 93952,93957 **** --- 94225,94231 ---- d07c560931ec5252834914b445bcfe26 libstdc++-v3/testsuite/28_regex/basic_regex/ctors/47724.cc 326bbf252dc9afc3d66f09406a11ce06 libstdc++-v3/testsuite/28_regex/basic_regex/ctors/basic/cstring.cc 7dc043298e8d07ca8f8b5631dd113491 libstdc++-v3/testsuite/28_regex/basic_regex/ctors/basic/default.cc + 1f2aed16200172a658646299e552350c libstdc++-v3/testsuite/28_regex/basic_regex/ctors/basic/iter.cc 89686c4cfa27f2e9ee243a37fae0cd75 libstdc++-v3/testsuite/28_regex/basic_regex/ctors/basic/pstring_char.cc 534828c9960a4136b9d0863aca50a2ee libstdc++-v3/testsuite/28_regex/basic_regex/ctors/basic/pstring_wchar_t.cc 21427c0c30a7b22f050065553cebb60f libstdc++-v3/testsuite/28_regex/basic_regex/ctors/basic/raw_string.cc *************** e2d7778e834dc03d399bd1c0871ebde4 libstd *** 94007,94013 **** 2dcf8f30d0c3f2e409bb34ede6a65b86 libstdc++-v3/testsuite/28_regex/range_access.cc 5f9d219283f91aa32685ee7cc7d0abc1 libstdc++-v3/testsuite/28_regex/regex_error/base.cc 19e22529270c44d785b6556fb927fc47 libstdc++-v3/testsuite/28_regex/regex_error/regex_error.cc ! 68f151d3274defb8f59d8b7ff7d2a94e libstdc++-v3/testsuite/28_regex/regression.cc bf2839ff0490457b1b711c8115fd75de libstdc++-v3/testsuite/28_regex/requirements/typedefs.cc 0e0c88b853b0ff77fa836b54e0607a49 libstdc++-v3/testsuite/28_regex/sub_match/cast_char.cc 33bb9f9adc1e784cb0d19f13eaf3537b libstdc++-v3/testsuite/28_regex/sub_match/cast_wchar_t.cc --- 94281,94287 ---- 2dcf8f30d0c3f2e409bb34ede6a65b86 libstdc++-v3/testsuite/28_regex/range_access.cc 5f9d219283f91aa32685ee7cc7d0abc1 libstdc++-v3/testsuite/28_regex/regex_error/base.cc 19e22529270c44d785b6556fb927fc47 libstdc++-v3/testsuite/28_regex/regex_error/regex_error.cc ! d33e022e0e6b6b81dafd27434acda9e4 libstdc++-v3/testsuite/28_regex/regression.cc bf2839ff0490457b1b711c8115fd75de libstdc++-v3/testsuite/28_regex/requirements/typedefs.cc 0e0c88b853b0ff77fa836b54e0607a49 libstdc++-v3/testsuite/28_regex/sub_match/cast_char.cc 33bb9f9adc1e784cb0d19f13eaf3537b libstdc++-v3/testsuite/28_regex/sub_match/cast_wchar_t.cc *************** fe0b2f3cd47d5d8dbea6f144cb813987 libstd *** 94042,94047 **** --- 94316,94322 ---- 1cbde7b07616550ff6f216b789642fcc libstdc++-v3/testsuite/29_atomics/atomic/64658.cc d0b280679a246549737c764aba7ae9b9 libstdc++-v3/testsuite/29_atomics/atomic/65147.cc 7af3c44a3de4fb0cddf38f3113cbc24e libstdc++-v3/testsuite/29_atomics/atomic/65913.cc + 91fa5fb74d19cc4c7ccaf8bf7ce5490a libstdc++-v3/testsuite/29_atomics/atomic/69301.cc c80acf835c5ce4abaa0ac617f980355b libstdc++-v3/testsuite/29_atomics/atomic/cons/49445.cc acd3b57ed2ac2fc5ea6b2320f307149c libstdc++-v3/testsuite/29_atomics/atomic/cons/assign_neg.cc be3374ed0e8ba400524eecc5b4f20e62 libstdc++-v3/testsuite/29_atomics/atomic/cons/constexpr.cc *************** db5ecca9146c7b296130664f2e86e83f libstd *** 94318,94323 **** --- 94593,94599 ---- 0534f0e159d032c3f08bf98ba17467dc libstdc++-v3/testsuite/30_threads/thread/cons/9.cc 464c2e5f300bb7c4be7295443bd48662 libstdc++-v3/testsuite/30_threads/thread/cons/assign_neg.cc 4ed1b212caaa3ed1bb133c378299b215 libstdc++-v3/testsuite/30_threads/thread/cons/copy_neg.cc + cc309c9b467ecb015d9fbb12271121ae libstdc++-v3/testsuite/30_threads/thread/cons/lwg2097.cc ab5dc353030937f33755038315092a94 libstdc++-v3/testsuite/30_threads/thread/cons/moveable.cc d1dde412f82680e8a2af2d9a8f5c8531 libstdc++-v3/testsuite/30_threads/thread/id/hash.cc 21e0ac8c7be313b478cccd48fb4e2356 libstdc++-v3/testsuite/30_threads/thread/id/operators.cc *************** b886edc31890a2d16b28d1a2da4f1867 libstd *** 94445,94451 **** a2a23cf0ed7892aaa1822fabd84001d8 libstdc++-v3/testsuite/abi/demangle/regression/cw-15.cc 4cde177f1ef1bd4c0b82e4e230c6e5bd libstdc++-v3/testsuite/abi/demangle/regression/cw-16.cc 88a0fbd4d91bcdec33f9ab17329b22a4 libstdc++-v3/testsuite/abi/demangle/regression/old.cc ! 7be58b289c222fdd3f872f1104b6cb62 libstdc++-v3/testsuite/abi/header_cxxabi.c eb211087d450aa52e8e371d3b6e43f0b libstdc++-v3/testsuite/abi/pr42230.cc fccc2ccd9d499e0d1dd6dc9a621a7d45 libstdc++-v3/testsuite/backward/11460.cc 0c4994e1800714363097ce1d3bce5e0d libstdc++-v3/testsuite/backward/hash_map/1.cc --- 94721,94727 ---- a2a23cf0ed7892aaa1822fabd84001d8 libstdc++-v3/testsuite/abi/demangle/regression/cw-15.cc 4cde177f1ef1bd4c0b82e4e230c6e5bd libstdc++-v3/testsuite/abi/demangle/regression/cw-16.cc 88a0fbd4d91bcdec33f9ab17329b22a4 libstdc++-v3/testsuite/abi/demangle/regression/old.cc ! 7cb1a0b6d6e473017facefe77d4b8309 libstdc++-v3/testsuite/abi/header_cxxabi.c eb211087d450aa52e8e371d3b6e43f0b libstdc++-v3/testsuite/abi/pr42230.cc fccc2ccd9d499e0d1dd6dc9a621a7d45 libstdc++-v3/testsuite/backward/11460.cc 0c4994e1800714363097ce1d3bce5e0d libstdc++-v3/testsuite/backward/hash_map/1.cc *************** f3cc688cbe5878fc515ed2d72179a197 libstd *** 94542,94555 **** 4d143ca68b2fc8e2f44162f96937b954 libstdc++-v3/testsuite/experimental/any/cons/2.cc bcb1af3db3b58578f36d9fc7692922cf libstdc++-v3/testsuite/experimental/any/cons/aligned.cc 48399811d2d329c756e82d87ef698e93 libstdc++-v3/testsuite/experimental/any/cons/nontrivial.cc ! f202bdedc914a2ba5e8700ca4b541d88 libstdc++-v3/testsuite/experimental/any/misc/any_cast.cc 3a88c591b8a2e756c12def4c1cbe0f50 libstdc++-v3/testsuite/experimental/any/misc/any_cast_neg.cc ede8bc6c2abc8e8e88dd015c19f35bc9 libstdc++-v3/testsuite/experimental/any/misc/any_cast_no_rtti.cc 4c83567229f17dfc9aeee2ceada69bc7 libstdc++-v3/testsuite/experimental/any/misc/swap.cc 89d8fbc9a4c2072fb0d49f46675f92e7 libstdc++-v3/testsuite/experimental/any/modifiers/1.cc e4fd72003cbbc2ce4004360eeff650e5 libstdc++-v3/testsuite/experimental/any/observers/type.cc f9130543194f9b55a8d690474e1b5667 libstdc++-v3/testsuite/experimental/any/typedefs.cc ! 1f60d193bfb2b984e48fa843e63cf42d libstdc++-v3/testsuite/experimental/array/make_array.cc 3c0fc5584f2c2249022f0b8c7542a586 libstdc++-v3/testsuite/experimental/array/neg.cc 261513dfd61fbdb473ad1c2630145109 libstdc++-v3/testsuite/experimental/chrono/value.cc 080593077dfd3a8a1b069f2faccb2b88 libstdc++-v3/testsuite/experimental/deque/erasure.cc --- 94818,94831 ---- 4d143ca68b2fc8e2f44162f96937b954 libstdc++-v3/testsuite/experimental/any/cons/2.cc bcb1af3db3b58578f36d9fc7692922cf libstdc++-v3/testsuite/experimental/any/cons/aligned.cc 48399811d2d329c756e82d87ef698e93 libstdc++-v3/testsuite/experimental/any/cons/nontrivial.cc ! 3163e58f0dd800110951aac5a0da071a libstdc++-v3/testsuite/experimental/any/misc/any_cast.cc 3a88c591b8a2e756c12def4c1cbe0f50 libstdc++-v3/testsuite/experimental/any/misc/any_cast_neg.cc ede8bc6c2abc8e8e88dd015c19f35bc9 libstdc++-v3/testsuite/experimental/any/misc/any_cast_no_rtti.cc 4c83567229f17dfc9aeee2ceada69bc7 libstdc++-v3/testsuite/experimental/any/misc/swap.cc 89d8fbc9a4c2072fb0d49f46675f92e7 libstdc++-v3/testsuite/experimental/any/modifiers/1.cc e4fd72003cbbc2ce4004360eeff650e5 libstdc++-v3/testsuite/experimental/any/observers/type.cc f9130543194f9b55a8d690474e1b5667 libstdc++-v3/testsuite/experimental/any/typedefs.cc ! 9fb3c90fb0538227094ef617e4537121 libstdc++-v3/testsuite/experimental/array/make_array.cc 3c0fc5584f2c2249022f0b8c7542a586 libstdc++-v3/testsuite/experimental/array/neg.cc 261513dfd61fbdb473ad1c2630145109 libstdc++-v3/testsuite/experimental/chrono/value.cc 080593077dfd3a8a1b069f2faccb2b88 libstdc++-v3/testsuite/experimental/deque/erasure.cc *************** fa2b5430b4dc9d19e155fb55bf89cdef libstd *** 94623,94629 **** 043c6e8e4f78804111ba475b4b36f43a libstdc++-v3/testsuite/experimental/functional/value.cc b8a37dc3290caea1a96660d87ea5a9a3 libstdc++-v3/testsuite/experimental/iterator/make_ostream_joiner.cc 1c550ab3838807146948e05c220dd3c2 libstdc++-v3/testsuite/experimental/iterator/ostream_joiner.cc ! 17ccd1743755323342124adc0b6836f8 libstdc++-v3/testsuite/experimental/iterator/requirements.cc d3ab5e86aa5e7ac55f5d37a6f735280e libstdc++-v3/testsuite/experimental/list/erasure.cc 70125c85000789057c8687a6838e9adb libstdc++-v3/testsuite/experimental/map/erasure.cc 8c013545f075901650904a3cd5c65631 libstdc++-v3/testsuite/experimental/memory/observer_ptr/assignment/assign.cc --- 94899,94905 ---- 043c6e8e4f78804111ba475b4b36f43a libstdc++-v3/testsuite/experimental/functional/value.cc b8a37dc3290caea1a96660d87ea5a9a3 libstdc++-v3/testsuite/experimental/iterator/make_ostream_joiner.cc 1c550ab3838807146948e05c220dd3c2 libstdc++-v3/testsuite/experimental/iterator/ostream_joiner.cc ! b38c8c8fd83cd4c520c33faf1fe740fb libstdc++-v3/testsuite/experimental/iterator/requirements.cc d3ab5e86aa5e7ac55f5d37a6f735280e libstdc++-v3/testsuite/experimental/list/erasure.cc 70125c85000789057c8687a6838e9adb libstdc++-v3/testsuite/experimental/map/erasure.cc 8c013545f075901650904a3cd5c65631 libstdc++-v3/testsuite/experimental/memory/observer_ptr/assignment/assign.cc *************** c4b1087862c4083c3916414a0e9ab53e libstd *** 94658,94664 **** 070f72cad715d52fbb7f562052cd8231 libstdc++-v3/testsuite/experimental/memory/shared_ptr/observers/owner_before.cc 19a87aff6cab6612f673b1b6bbb83561 libstdc++-v3/testsuite/experimental/memory/shared_ptr/observers/use_count.cc d76f77a05da4f9bccc54a418c5480422 libstdc++-v3/testsuite/experimental/memory_resource/1.cc ! 74e76db79b7b18854cb327a3d6dfd1ca libstdc++-v3/testsuite/experimental/memory_resource/null_memory_resource.cc 50a1072449816a3c9c47e8c9766e9432 libstdc++-v3/testsuite/experimental/memory_resource/resource_adaptor.cc ae383e40a008068368a3fbeff039591f libstdc++-v3/testsuite/experimental/numeric/77801.cc c77b6abd738996b68bdbcd45a18d3920 libstdc++-v3/testsuite/experimental/numeric/gcd.cc --- 94934,94940 ---- 070f72cad715d52fbb7f562052cd8231 libstdc++-v3/testsuite/experimental/memory/shared_ptr/observers/owner_before.cc 19a87aff6cab6612f673b1b6bbb83561 libstdc++-v3/testsuite/experimental/memory/shared_ptr/observers/use_count.cc d76f77a05da4f9bccc54a418c5480422 libstdc++-v3/testsuite/experimental/memory_resource/1.cc ! 433d79761e6e012f2ea4835338ef95f8 libstdc++-v3/testsuite/experimental/memory_resource/null_memory_resource.cc 50a1072449816a3c9c47e8c9766e9432 libstdc++-v3/testsuite/experimental/memory_resource/resource_adaptor.cc ae383e40a008068368a3fbeff039591f libstdc++-v3/testsuite/experimental/numeric/77801.cc c77b6abd738996b68bdbcd45a18d3920 libstdc++-v3/testsuite/experimental/numeric/gcd.cc *************** a89041db77745da6173891d8f9309bbf libstd *** 94799,94806 **** d06b27a201ab805ecd5bf89b4fc369f7 libstdc++-v3/testsuite/experimental/system_error/value.cc 569c8323b111fc2d8af937c6ac7019da libstdc++-v3/testsuite/experimental/tuple/apply.cc 101ee52327cadd9f462e13aa38d5e67d libstdc++-v3/testsuite/experimental/tuple/tuple_size.cc ! 51f0edc8115f8eeca62450473e6e5567 libstdc++-v3/testsuite/experimental/type_erased_allocator/2.cc ! 213ec373f1e3ce0b6c403e1522457bb3 libstdc++-v3/testsuite/experimental/type_erased_allocator/uses_allocator.cc 8eb16260dc8f4ee27e52d211e03816b9 libstdc++-v3/testsuite/experimental/type_traits/detection.cc 55a49a967400e4f33106adf30b860c48 libstdc++-v3/testsuite/experimental/type_traits/value.cc d49b53a5eb472c8dc41325dfa373cc77 libstdc++-v3/testsuite/experimental/unordered_map/erasure.cc --- 95075,95082 ---- d06b27a201ab805ecd5bf89b4fc369f7 libstdc++-v3/testsuite/experimental/system_error/value.cc 569c8323b111fc2d8af937c6ac7019da libstdc++-v3/testsuite/experimental/tuple/apply.cc 101ee52327cadd9f462e13aa38d5e67d libstdc++-v3/testsuite/experimental/tuple/tuple_size.cc ! dc3c9ea70ed07b4e5203e16f6dcc48db libstdc++-v3/testsuite/experimental/type_erased_allocator/2.cc ! fe273bbf3c582c174e76bfbd827a36a2 libstdc++-v3/testsuite/experimental/type_erased_allocator/uses_allocator.cc 8eb16260dc8f4ee27e52d211e03816b9 libstdc++-v3/testsuite/experimental/type_traits/detection.cc 55a49a967400e4f33106adf30b860c48 libstdc++-v3/testsuite/experimental/type_traits/value.cc d49b53a5eb472c8dc41325dfa373cc77 libstdc++-v3/testsuite/experimental/unordered_map/erasure.cc *************** b024313f4d905fe5d16c9ec00404cdfb libstd *** 94925,94933 **** 2b5b5888c16c75b99a2e56dff6ac274a libstdc++-v3/testsuite/ext/pb_ds/regression/list_update_map_rand_debug.cc 864210f11a1e818437257838a267fc2f libstdc++-v3/testsuite/ext/pb_ds/regression/list_update_set_rand.cc b45b53a45abac9df4595d3470101c37f libstdc++-v3/testsuite/ext/pb_ds/regression/list_update_set_rand_debug.cc 56160086eff60d66382f6a9753e027d3 libstdc++-v3/testsuite/ext/pb_ds/regression/priority_queue_rand.cc f5705716a8949f5fbabe70320466c6cf libstdc++-v3/testsuite/ext/pb_ds/regression/priority_queue_rand_debug.cc ! f004883a4ac86c70537d2cc6a45c0de5 libstdc++-v3/testsuite/ext/pb_ds/regression/priority_queues.cc deb68d181e7d14f11b6b5c7d4754aeec libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand.cc cfa6365b89bf777eb605321402aa8d7f libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand_debug.cc 57885fe90b5eee246e9ab3e0f8448166 libstdc++-v3/testsuite/ext/pb_ds/regression/tree_set_rand.cc --- 95201,95210 ---- 2b5b5888c16c75b99a2e56dff6ac274a libstdc++-v3/testsuite/ext/pb_ds/regression/list_update_map_rand_debug.cc 864210f11a1e818437257838a267fc2f libstdc++-v3/testsuite/ext/pb_ds/regression/list_update_set_rand.cc b45b53a45abac9df4595d3470101c37f libstdc++-v3/testsuite/ext/pb_ds/regression/list_update_set_rand_debug.cc + adaf4213d618ef3bf2e611c156e73ce1 libstdc++-v3/testsuite/ext/pb_ds/regression/priority_queue_binary_heap-62045.cc 56160086eff60d66382f6a9753e027d3 libstdc++-v3/testsuite/ext/pb_ds/regression/priority_queue_rand.cc f5705716a8949f5fbabe70320466c6cf libstdc++-v3/testsuite/ext/pb_ds/regression/priority_queue_rand_debug.cc ! e7b42131e75daabcb7cc15080164e9bc libstdc++-v3/testsuite/ext/pb_ds/regression/priority_queues.cc deb68d181e7d14f11b6b5c7d4754aeec libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand.cc cfa6365b89bf777eb605321402aa8d7f libstdc++-v3/testsuite/ext/pb_ds/regression/tree_map_rand_debug.cc 57885fe90b5eee246e9ab3e0f8448166 libstdc++-v3/testsuite/ext/pb_ds/regression/tree_set_rand.cc *************** c7c910ce272dc705dc1f44285ddd2571 libstd *** 95060,95071 **** 4f2697a635ba2976fdb4d9747bdb9f7a libstdc++-v3/testsuite/ext/slist/23781_neg.cc 097820ca02a93cd00ddee86d180cacdc libstdc++-v3/testsuite/ext/slist/check_construct_destroy.cc 879a60e19dec978037a284c693a67f66 libstdc++-v3/testsuite/ext/slist/requirements/explicit_instantiation.cc ! 2f2934a102a12a65e979a275eb0994cc libstdc++-v3/testsuite/ext/special_functions/conf_hyperg/check_nan.cc ! 166f34a9f49ed60a91f6d1c00c418a2c libstdc++-v3/testsuite/ext/special_functions/conf_hyperg/check_value.cc ! 68a64fa38dc26405d1b3e1095376b334 libstdc++-v3/testsuite/ext/special_functions/conf_hyperg/compile.cc ! da58102fddd27b2f574e95fcd9b5f8dd libstdc++-v3/testsuite/ext/special_functions/hyperg/check_nan.cc ! b7b12c4be546bfa8fcdbf33d91c20bf9 libstdc++-v3/testsuite/ext/special_functions/hyperg/check_value.cc ! 12d3e71ae4753daf74dc8b584b496ae1 libstdc++-v3/testsuite/ext/special_functions/hyperg/compile.cc d87c528fef89174f4b009a39059764aa libstdc++-v3/testsuite/ext/stdio_filebuf/char/10063-1.cc 6d481e8d41d85d3f9adc43f207071661 libstdc++-v3/testsuite/ext/stdio_filebuf/char/10063-2.cc cacc2855ee42b2c0ed738c61d97cdd1f libstdc++-v3/testsuite/ext/stdio_filebuf/char/10063-3.cc --- 95337,95348 ---- 4f2697a635ba2976fdb4d9747bdb9f7a libstdc++-v3/testsuite/ext/slist/23781_neg.cc 097820ca02a93cd00ddee86d180cacdc libstdc++-v3/testsuite/ext/slist/check_construct_destroy.cc 879a60e19dec978037a284c693a67f66 libstdc++-v3/testsuite/ext/slist/requirements/explicit_instantiation.cc ! 4cdb5dab0fb36951b220fd2eb8e57df7 libstdc++-v3/testsuite/ext/special_functions/conf_hyperg/check_nan.cc ! a6dacbacfcdf92daca7a890d14c5265d libstdc++-v3/testsuite/ext/special_functions/conf_hyperg/check_value.cc ! 771e26ed744e6b785ca21166a87747b1 libstdc++-v3/testsuite/ext/special_functions/conf_hyperg/compile.cc ! b1db96f8609944a40bc8c316b2da91f2 libstdc++-v3/testsuite/ext/special_functions/hyperg/check_nan.cc ! 9ab749163b8cf62cdff552ce24ea1af5 libstdc++-v3/testsuite/ext/special_functions/hyperg/check_value.cc ! 1747846ce6ea2c80e99b839a283b51f2 libstdc++-v3/testsuite/ext/special_functions/hyperg/compile.cc d87c528fef89174f4b009a39059764aa libstdc++-v3/testsuite/ext/stdio_filebuf/char/10063-1.cc 6d481e8d41d85d3f9adc43f207071661 libstdc++-v3/testsuite/ext/stdio_filebuf/char/10063-2.cc cacc2855ee42b2c0ed738c61d97cdd1f libstdc++-v3/testsuite/ext/stdio_filebuf/char/10063-3.cc *************** b15c6db83318815cd34020c84f331491 libstd *** 95147,95159 **** b3c3d1874b99c71e9b712cbeef9b38bc libstdc++-v3/testsuite/libstdc++-abi/abi.exp 74d9b6079ff372f6105439bdb293da63 libstdc++-v3/testsuite/libstdc++-dg/conformance.exp a5a3e18e12e56fd3383d69db66735619 libstdc++-v3/testsuite/libstdc++-prettyprinters/48362.cc f2e284a2aa11b988e4fd36f6af208f13 libstdc++-v3/testsuite/libstdc++-prettyprinters/cxx11.cc b0fe02d5361c7b9c4421e591b0c8cb21 libstdc++-v3/testsuite/libstdc++-prettyprinters/debug.cc a6b0f8872932b8704c4f04be2690295a libstdc++-v3/testsuite/libstdc++-prettyprinters/libfundts.cc 9d43067f8da943e58554c34ba974eabd libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp c9765f7b65bcf12c97be4a7216cd46be libstdc++-v3/testsuite/libstdc++-prettyprinters/shared_ptr.cc ! e4eb6f1942fce974ee6f4ebeebe2c011 libstdc++-v3/testsuite/libstdc++-prettyprinters/simple.cc ! 9cbcdca344065a90d63ffb9ed12629ae libstdc++-v3/testsuite/libstdc++-prettyprinters/simple11.cc 9007dcf2e7b1f149d4aa6be505ff160a libstdc++-v3/testsuite/libstdc++-prettyprinters/tr1.cc 5f6dc49936d2a29f253ea420f931311d libstdc++-v3/testsuite/libstdc++-prettyprinters/whatis.cc ac96152bfef0eaac717cdce923dd43c7 libstdc++-v3/testsuite/libstdc++-xmethods/array.cc --- 95424,95437 ---- b3c3d1874b99c71e9b712cbeef9b38bc libstdc++-v3/testsuite/libstdc++-abi/abi.exp 74d9b6079ff372f6105439bdb293da63 libstdc++-v3/testsuite/libstdc++-dg/conformance.exp a5a3e18e12e56fd3383d69db66735619 libstdc++-v3/testsuite/libstdc++-prettyprinters/48362.cc + 68e683137d64badec192d4c3bd419579 libstdc++-v3/testsuite/libstdc++-prettyprinters/59161.cc f2e284a2aa11b988e4fd36f6af208f13 libstdc++-v3/testsuite/libstdc++-prettyprinters/cxx11.cc b0fe02d5361c7b9c4421e591b0c8cb21 libstdc++-v3/testsuite/libstdc++-prettyprinters/debug.cc a6b0f8872932b8704c4f04be2690295a libstdc++-v3/testsuite/libstdc++-prettyprinters/libfundts.cc 9d43067f8da943e58554c34ba974eabd libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp c9765f7b65bcf12c97be4a7216cd46be libstdc++-v3/testsuite/libstdc++-prettyprinters/shared_ptr.cc ! 7d71d9377c3f1a779e371cd82afa3e5a libstdc++-v3/testsuite/libstdc++-prettyprinters/simple.cc ! 6f62024e0f64c92d31a74e17f26ed5fd libstdc++-v3/testsuite/libstdc++-prettyprinters/simple11.cc 9007dcf2e7b1f149d4aa6be505ff160a libstdc++-v3/testsuite/libstdc++-prettyprinters/tr1.cc 5f6dc49936d2a29f253ea420f931311d libstdc++-v3/testsuite/libstdc++-prettyprinters/whatis.cc ac96152bfef0eaac717cdce923dd43c7 libstdc++-v3/testsuite/libstdc++-xmethods/array.cc *************** ac96152bfef0eaac717cdce923dd43c7 libstd *** 95161,95167 **** c9f2671155c8f1a9cd87381efbadfec2 libstdc++-v3/testsuite/libstdc++-xmethods/deque.cc 4595684b440f9f7174fdd3166126c25a libstdc++-v3/testsuite/libstdc++-xmethods/forwardlist.cc 8b48c4e87af1633b343e1f1908706bdb libstdc++-v3/testsuite/libstdc++-xmethods/list.cc ! b3e67becd9117c5299170076354e6621 libstdc++-v3/testsuite/libstdc++-xmethods/unique_ptr.cc caaacb0448644459699cee301461e43f libstdc++-v3/testsuite/libstdc++-xmethods/vector.cc 2835f1b72d8916a68a4a2b43b8991749 libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp 8b06aa47bfa95eba0f51541ccb2b1969 libstdc++-v3/testsuite/performance/21_strings/append-1.cc --- 95439,95446 ---- c9f2671155c8f1a9cd87381efbadfec2 libstdc++-v3/testsuite/libstdc++-xmethods/deque.cc 4595684b440f9f7174fdd3166126c25a libstdc++-v3/testsuite/libstdc++-xmethods/forwardlist.cc 8b48c4e87af1633b343e1f1908706bdb libstdc++-v3/testsuite/libstdc++-xmethods/list.cc ! 7469f8d40ba270926c36a45b15e9ebbd libstdc++-v3/testsuite/libstdc++-xmethods/shared_ptr.cc ! 652ca73fa98a636970fa6ddbd4a90c77 libstdc++-v3/testsuite/libstdc++-xmethods/unique_ptr.cc caaacb0448644459699cee301461e43f libstdc++-v3/testsuite/libstdc++-xmethods/vector.cc 2835f1b72d8916a68a4a2b43b8991749 libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp 8b06aa47bfa95eba0f51541ccb2b1969 libstdc++-v3/testsuite/performance/21_strings/append-1.cc *************** fdf312c05b12573189c296172704fe5f libstd *** 95260,95350 **** 40f57b144133b4978e8ee99f76578f3b libstdc++-v3/testsuite/performance/ext/pb_ds/tree_split_join.cc 15e001e2a323ee66eb95de1f4f31bfa0 libstdc++-v3/testsuite/performance/ext/pb_ds/tree_text_insert.cc c3f8a6a803eb052e3b2a532d092d2690 libstdc++-v3/testsuite/performance/ext/pb_ds/tree_text_lor_find.cc ! 4f06dc604a2781b6c42be07f1fb92508 libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/check_nan.cc ! b72515bd5e9405964bff5c52f2920029 libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/check_value.cc ! 5702fea130e42bcfdc84107d137b29cd libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/compile.cc ! a76747b3e5bc6f015f739d63c1a5f9d2 libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/compile_2.cc ! 989160c41a68bdf50cc2e94cb621bbf4 libstdc++-v3/testsuite/special_functions/02_assoc_legendre/check_nan.cc ! b93c847e7257b142f70796cf196add5b libstdc++-v3/testsuite/special_functions/02_assoc_legendre/check_value.cc ! 7486db1eb6ea4bf2d7f2192a2c92afcd libstdc++-v3/testsuite/special_functions/02_assoc_legendre/compile.cc ! 88a47a24f4d63dc8887b046141eb69fd libstdc++-v3/testsuite/special_functions/02_assoc_legendre/compile_2.cc ! 450be0e8ac6fccb3cebe69c6f947a21e libstdc++-v3/testsuite/special_functions/03_beta/check_nan.cc ! c2fb4eb93a2ced4f4f5f615446108217 libstdc++-v3/testsuite/special_functions/03_beta/check_value.cc ! f2ad69fbb9f798c0de2c0c7cc64e1b2a libstdc++-v3/testsuite/special_functions/03_beta/compile.cc ! 494eb2d0779d93b73b0281399a6e99b3 libstdc++-v3/testsuite/special_functions/03_beta/compile_2.cc ! 5c7d98e5dc6b3e8b03b1095818d145a8 libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/check_nan.cc ! a39942de65c5207bc48c2bdacdbd1115 libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/check_value.cc ! a6bbec5ca2ce3755d9cb13d2489b83f9 libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/compile.cc ! 7fd99fac9fc5022f0868e4eb7625577d libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/compile_2.cc ! 90f8f09ed7b9a1320828faaedf6b902b libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/check_nan.cc ! 2662589f9a01267302321f422f2b42e0 libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/check_value.cc ! 520fdb6ecf7672a0f773094d7dc93704 libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/compile.cc ! f7016adfc7f3b5e0132f2e1d54c39758 libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/compile_2.cc ! dc32bbc933c23a9581d4ea0a0865d173 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/check_nan.cc ! 2bd360c5335884c2ace8b97ab1dd14b8 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/check_value.cc ! 2a45381c354281982c3e5efa9154e0a8 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/compile.cc ! 982c74cce7931e7b1cb0226554834137 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/compile_2.cc ! f8e5740ef151b0e5eb0a9393faa833dc libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/check_nan.cc ! 325103e90a15d9c64dc0aece78ddfb41 libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/check_value.cc ! f9f7931789f67865785c8daac2921dc7 libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/compile.cc ! 641c0c58fefaab3e2d0e7b8bd2921f92 libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/compile_2.cc ! 577fa2b65a5f8e0823894f0c0f4f02ae libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/pr56216.cc ! 4b458c6841aa5061c313a3a2f19811df libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/check_nan.cc ! c0330c81d172cc0a7f09928e8b410332 libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/check_value.cc ! 7875d98b47f82f167ff78c67b498c909 libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/compile.cc ! 84b6bb4b5f61ed2a9b8e7fb9e4eb9b12 libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/compile_2.cc ! e2eb263eee26336dd29d2af9a5b26cd8 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/check_nan.cc ! 92afa4c8a12b3103014775130fef2a24 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/check_value.cc ! 1bc6f8f9cbc2308e058ba428f28ee2b2 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/compile.cc ! 15cad8b6d521bbd400078bda25f77b16 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/compile_2.cc ! 75ce7cd296e75b0ad3ea7f695ecf80e9 libstdc++-v3/testsuite/special_functions/10_cyl_neumann/check_nan.cc ! b28cde9f06d2d2ce507ceabfe58d58bb libstdc++-v3/testsuite/special_functions/10_cyl_neumann/check_value.cc ! d4e59fec5b03e258f33b9ee1f303b756 libstdc++-v3/testsuite/special_functions/10_cyl_neumann/compile.cc ! 1b2e2121554966d2ce1cba0078a722c1 libstdc++-v3/testsuite/special_functions/10_cyl_neumann/compile_2.cc ! ebef2a3c554bcfccacaa4ae34f52e0a6 libstdc++-v3/testsuite/special_functions/11_ellint_1/check_nan.cc ! e8216a594cb361f6468da7aad7cd509d libstdc++-v3/testsuite/special_functions/11_ellint_1/check_value.cc ! 69a3bd726e0c157c90e02ca8e634cb78 libstdc++-v3/testsuite/special_functions/11_ellint_1/compile.cc ! 2300015f6be26a46ce52d64679327a14 libstdc++-v3/testsuite/special_functions/11_ellint_1/compile_2.cc ! 04a5dee012aee20fa8e579127be85368 libstdc++-v3/testsuite/special_functions/12_ellint_2/check_nan.cc ! 4bb8f4f970032aa48c6a3cc4ce25a41c libstdc++-v3/testsuite/special_functions/12_ellint_2/check_value.cc ! 6ec9abe81244b25cab16bde6db628d10 libstdc++-v3/testsuite/special_functions/12_ellint_2/compile.cc ! 82de168f5fdb59bcbf059986175df82f libstdc++-v3/testsuite/special_functions/12_ellint_2/compile_2.cc ! b8122fb39a80f301a37daf86c25927b2 libstdc++-v3/testsuite/special_functions/13_ellint_3/check_nan.cc ! 67bc433055fbece921b6389379c0f41e libstdc++-v3/testsuite/special_functions/13_ellint_3/check_value.cc ! 608c008910b0c114ca140b7cf07e603b libstdc++-v3/testsuite/special_functions/13_ellint_3/compile.cc ! f5986191813e2c7ac51c0b63b5867c37 libstdc++-v3/testsuite/special_functions/13_ellint_3/compile_2.cc ! a72d4f15159d5ebaddc5c24aef7b2266 libstdc++-v3/testsuite/special_functions/14_expint/check_nan.cc ! 472ca7fa4a50963506ca61b01c1225e5 libstdc++-v3/testsuite/special_functions/14_expint/check_value.cc ! 71f03892520557aabed06c8382c62238 libstdc++-v3/testsuite/special_functions/14_expint/compile.cc ! e0a6e0e27dc96fc1c4844afc771a41cb libstdc++-v3/testsuite/special_functions/14_expint/compile_2.cc ! 935c63fa979703935888cceb7ffa8a53 libstdc++-v3/testsuite/special_functions/15_hermite/check_nan.cc ! 0a8c2942905322245a7cf6677718bbc6 libstdc++-v3/testsuite/special_functions/15_hermite/check_value.cc ! 1a5327ca9bd92d6c207de9c53289ca56 libstdc++-v3/testsuite/special_functions/15_hermite/compile.cc ! 7b9a676ba2e8cbde5542030a5c87c03a libstdc++-v3/testsuite/special_functions/15_hermite/compile_2.cc ! 72a3211e2525aa9c3963258dd01a4118 libstdc++-v3/testsuite/special_functions/16_laguerre/check_nan.cc ! 7a90cbefe3f13695de3eceb6fbe02aab libstdc++-v3/testsuite/special_functions/16_laguerre/check_value.cc ! 369b09d5dec6b05fa41f1eb2f79c2aea libstdc++-v3/testsuite/special_functions/16_laguerre/compile.cc ! b674246b090640b9fb3ef8467d127c4e libstdc++-v3/testsuite/special_functions/16_laguerre/compile_2.cc ! 8545aed2f13090964408b79278654955 libstdc++-v3/testsuite/special_functions/17_legendre/check_nan.cc ! 563cc90b5b9021b5cdb7cad913900744 libstdc++-v3/testsuite/special_functions/17_legendre/check_value.cc ! 71d00303ae108fb2df256a5da61ea171 libstdc++-v3/testsuite/special_functions/17_legendre/compile.cc ! 8662507a7e272b8a36a9a64cb134894e libstdc++-v3/testsuite/special_functions/17_legendre/compile_2.cc ! 30ecd1ee1ee135a6fd0be487a6c0e378 libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_nan.cc ! bab4df59d6108aa58fff41b75cb145f3 libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_value.cc ! 63ba20dbcd503d6a95d5cb6d43ed7108 libstdc++-v3/testsuite/special_functions/18_riemann_zeta/compile.cc ! d6f396155a579dafbcbe91d9bf3d0007 libstdc++-v3/testsuite/special_functions/18_riemann_zeta/compile_2.cc ! 0945d7dd43ebbc25a9c85e7565e6908f libstdc++-v3/testsuite/special_functions/19_sph_bessel/check_nan.cc ! 535700ac37d4bccb61b32cdcf7d2d3e8 libstdc++-v3/testsuite/special_functions/19_sph_bessel/check_value.cc ! c7dd4878e46a288ea784d578dbfb54df libstdc++-v3/testsuite/special_functions/19_sph_bessel/compile.cc ! 1810efe00d17f3547150525373b39676 libstdc++-v3/testsuite/special_functions/19_sph_bessel/compile_2.cc ! 06b9392c90e87b5d8b89f4487b47c7c4 libstdc++-v3/testsuite/special_functions/20_sph_legendre/check_nan.cc ! 6f0f1702d5e3151abd591541f97049af libstdc++-v3/testsuite/special_functions/20_sph_legendre/check_value.cc ! 4cad83cbaf4c870d6e0fec904fff91c8 libstdc++-v3/testsuite/special_functions/20_sph_legendre/compile.cc ! 68ea8774b0b0817692072b7bbc741deb libstdc++-v3/testsuite/special_functions/20_sph_legendre/compile_2.cc ! a8afcbefa8f4d2b66d780f238bd270e9 libstdc++-v3/testsuite/special_functions/21_sph_neumann/check_nan.cc ! e00396e02820a7740c317b26fb113b5d libstdc++-v3/testsuite/special_functions/21_sph_neumann/check_value.cc ! 061325791a6b3b25f1f6122e3355341a libstdc++-v3/testsuite/special_functions/21_sph_neumann/compile.cc ! f8d8fa6eb8eb88f1ac4174909d3217de libstdc++-v3/testsuite/special_functions/21_sph_neumann/compile_2.cc db59d84f34e748db7b1dfa2c8b226d5f libstdc++-v3/testsuite/tr1/2_general_utilities/enable_shared_from_this/1.cc 9489c2f0342abf91af32b980141dcb3e libstdc++-v3/testsuite/tr1/2_general_utilities/enable_shared_from_this/not_shared.cc 8f1f797304d58d0a316b989811618970 libstdc++-v3/testsuite/tr1/2_general_utilities/enable_shared_from_this/not_shared2.cc --- 95539,95629 ---- 40f57b144133b4978e8ee99f76578f3b libstdc++-v3/testsuite/performance/ext/pb_ds/tree_split_join.cc 15e001e2a323ee66eb95de1f4f31bfa0 libstdc++-v3/testsuite/performance/ext/pb_ds/tree_text_insert.cc c3f8a6a803eb052e3b2a532d092d2690 libstdc++-v3/testsuite/performance/ext/pb_ds/tree_text_lor_find.cc ! d6bca76694568673dcfd6949bef461f1 libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/check_nan.cc ! 9763e6d4bae72ee65c8fd67a09404b9b libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/check_value.cc ! 129a650f3925fecf10e37f8a49aea9e4 libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/compile.cc ! aa9f69e567ff77f4dd025e561257ba71 libstdc++-v3/testsuite/special_functions/01_assoc_laguerre/compile_2.cc ! a45155ace7b1733aa5e8226f00585a67 libstdc++-v3/testsuite/special_functions/02_assoc_legendre/check_nan.cc ! d5f588ea2dc0475e52f2bb3ea540e85e libstdc++-v3/testsuite/special_functions/02_assoc_legendre/check_value.cc ! 2dcbccee4c871251736c3bfeb2ab93a6 libstdc++-v3/testsuite/special_functions/02_assoc_legendre/compile.cc ! 1212b54410597cb3159b6a265bdbcbe5 libstdc++-v3/testsuite/special_functions/02_assoc_legendre/compile_2.cc ! 6862d6cdd947b6ee95b10d749177ac9e libstdc++-v3/testsuite/special_functions/03_beta/check_nan.cc ! 31fc7a0d7376b9f13133abcadcfed609 libstdc++-v3/testsuite/special_functions/03_beta/check_value.cc ! 34342769e88a18c28df41fd448bb2e5f libstdc++-v3/testsuite/special_functions/03_beta/compile.cc ! 2dfe905b0a48ec59d3702fcf19f43615 libstdc++-v3/testsuite/special_functions/03_beta/compile_2.cc ! f6f7a698d5ee9c3cca7bed2da2f6a8e4 libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/check_nan.cc ! 004c24bddcdb9ffb8845efbff3a506b4 libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/check_value.cc ! db6797f46469bc5b57a3aca794f595b4 libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/compile.cc ! bc770012c2caeb4f1e62d987b0eae7f2 libstdc++-v3/testsuite/special_functions/04_comp_ellint_1/compile_2.cc ! 23ad95a1745a05e856f86376dc80b2e6 libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/check_nan.cc ! 5e30209cc7aa8383bcf8fc351744f225 libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/check_value.cc ! 1d9bc223a6299f3ed252bd14e152151a libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/compile.cc ! df8a1c39b6b30a41e602ffd863995f51 libstdc++-v3/testsuite/special_functions/05_comp_ellint_2/compile_2.cc ! 55cb22417a4bbea445f520e4c13b6c29 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/check_nan.cc ! c5ecb1c1803a5326db0539123548e963 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/check_value.cc ! 39d8f3e6c1b2ea025b073ca097741fd8 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/compile.cc ! 3246b4797f16b5f56e05b9590724b512 libstdc++-v3/testsuite/special_functions/06_comp_ellint_3/compile_2.cc ! 134fe58f2322d3726f520ffc8ac4a842 libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/check_nan.cc ! 65439593d95c654c396ca88d6103658d libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/check_value.cc ! e569155b2ab0f3bc4074ddc2fa644806 libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/compile.cc ! 2ddba23e560a286f8580c3f88b2084fa libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/compile_2.cc ! a428497f319b7f711f3d11a49f2ccedb libstdc++-v3/testsuite/special_functions/07_cyl_bessel_i/pr56216.cc ! b72a43414bab0d21430faa0a6848291b libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/check_nan.cc ! 427ee29c29f3466204f4b0795ee1f7bd libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/check_value.cc ! e6ece41b8ca290a0d2b0d971e9ec8e20 libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/compile.cc ! 73f4af57e50fee3d007e241cdbc6b6bb libstdc++-v3/testsuite/special_functions/08_cyl_bessel_j/compile_2.cc ! d2db09693754a5074054d929c3fb1ac0 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/check_nan.cc ! be14f6d139a5011665114b667cb6a315 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/check_value.cc ! 6512df4688008a3b83eca96a49a8e249 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/compile.cc ! 1617a89f33a68e8f54caf1df0c87adf2 libstdc++-v3/testsuite/special_functions/09_cyl_bessel_k/compile_2.cc ! 78722bc1ecc8d0d686c3309251885198 libstdc++-v3/testsuite/special_functions/10_cyl_neumann/check_nan.cc ! d0ec4692475ea7c2a9093b46af32f148 libstdc++-v3/testsuite/special_functions/10_cyl_neumann/check_value.cc ! 5288f6ca57bf75398c684f95bf345d84 libstdc++-v3/testsuite/special_functions/10_cyl_neumann/compile.cc ! 9b71146e251551de2b71d9a39c722845 libstdc++-v3/testsuite/special_functions/10_cyl_neumann/compile_2.cc ! 3a16fdd8dd50dc7f25c88c1788d35833 libstdc++-v3/testsuite/special_functions/11_ellint_1/check_nan.cc ! 85200990acde72b1c686523ae4f4fc33 libstdc++-v3/testsuite/special_functions/11_ellint_1/check_value.cc ! 9c7d7d2f4288b1656494f73ac8891736 libstdc++-v3/testsuite/special_functions/11_ellint_1/compile.cc ! 528b96e564e88e3e488c7b2e09251891 libstdc++-v3/testsuite/special_functions/11_ellint_1/compile_2.cc ! fb97d3c43cbe360ea19620a525c41630 libstdc++-v3/testsuite/special_functions/12_ellint_2/check_nan.cc ! ad9c022f3fd552a61653edff5cb91a94 libstdc++-v3/testsuite/special_functions/12_ellint_2/check_value.cc ! 0f393ba29f9f8851abba36ce32bbda36 libstdc++-v3/testsuite/special_functions/12_ellint_2/compile.cc ! 04e2612c8666dd28f59cbeb23c273966 libstdc++-v3/testsuite/special_functions/12_ellint_2/compile_2.cc ! 8e25768533355325d04e85dc0192c071 libstdc++-v3/testsuite/special_functions/13_ellint_3/check_nan.cc ! d77f3c2918d4484991e2a33adcb7c52f libstdc++-v3/testsuite/special_functions/13_ellint_3/check_value.cc ! 37c30e7f5eb837354f728f38199ae2e9 libstdc++-v3/testsuite/special_functions/13_ellint_3/compile.cc ! 6536626dca2b267702bd6d83a0fed55f libstdc++-v3/testsuite/special_functions/13_ellint_3/compile_2.cc ! 422610b8f5c0571f9d1dcaa5680e3bf2 libstdc++-v3/testsuite/special_functions/14_expint/check_nan.cc ! 6f03ccee8cd192922525dc43ec943c21 libstdc++-v3/testsuite/special_functions/14_expint/check_value.cc ! de144099dfe50015fe26a4ba02c972db libstdc++-v3/testsuite/special_functions/14_expint/compile.cc ! 97d7553c1c19fae8aa105056332fd763 libstdc++-v3/testsuite/special_functions/14_expint/compile_2.cc ! 791dd595d7f0042730cab85812996b97 libstdc++-v3/testsuite/special_functions/15_hermite/check_nan.cc ! 4addecab90d3e2047c48b0d7b4ed1073 libstdc++-v3/testsuite/special_functions/15_hermite/check_value.cc ! 84878e120f93790e2bd814f227e0b676 libstdc++-v3/testsuite/special_functions/15_hermite/compile.cc ! 3417049d1240f127ff79f3f95453a21d libstdc++-v3/testsuite/special_functions/15_hermite/compile_2.cc ! d923a342805f419d07abebd15aca27c4 libstdc++-v3/testsuite/special_functions/16_laguerre/check_nan.cc ! 5a103bf98afc5d085178a8e97e43ccbe libstdc++-v3/testsuite/special_functions/16_laguerre/check_value.cc ! d576c14ece72b65003f85d4211c18e20 libstdc++-v3/testsuite/special_functions/16_laguerre/compile.cc ! 5f9a86b822b0cacbb653bf7aec2260a4 libstdc++-v3/testsuite/special_functions/16_laguerre/compile_2.cc ! 66555f29b019e2d11fdf3f66ad9dc5db libstdc++-v3/testsuite/special_functions/17_legendre/check_nan.cc ! 593302ff347ed2c2a79b7db8456251c5 libstdc++-v3/testsuite/special_functions/17_legendre/check_value.cc ! 46dff17b86cadf2b90e43821f7a9939b libstdc++-v3/testsuite/special_functions/17_legendre/compile.cc ! 6c054567ff1692b1e733fc2b16df7cd5 libstdc++-v3/testsuite/special_functions/17_legendre/compile_2.cc ! b1d7e3a9b112dd43061d74f40cc85aad libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_nan.cc ! 6812bac9bf606cb3baaf72a13da52e30 libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_value.cc ! 88e8e4e2eae81bcb38c40f519b2c88db libstdc++-v3/testsuite/special_functions/18_riemann_zeta/compile.cc ! dc29924449594b632e8af6a133c70ee0 libstdc++-v3/testsuite/special_functions/18_riemann_zeta/compile_2.cc ! 347714e74d0b02779a2fcf7f18a320fc libstdc++-v3/testsuite/special_functions/19_sph_bessel/check_nan.cc ! 574b7d6f9a9cf5541260fb96ff79a728 libstdc++-v3/testsuite/special_functions/19_sph_bessel/check_value.cc ! e348e6224cefb827254650f1b8c5963b libstdc++-v3/testsuite/special_functions/19_sph_bessel/compile.cc ! cf4264cc0ace50f4280e719297e92138 libstdc++-v3/testsuite/special_functions/19_sph_bessel/compile_2.cc ! 4a677946a75d0eda4a873b3278e7f5ec libstdc++-v3/testsuite/special_functions/20_sph_legendre/check_nan.cc ! 65b05211320dd59892d7ab5ae412afe6 libstdc++-v3/testsuite/special_functions/20_sph_legendre/check_value.cc ! 95e095ddec442e97fd959f86b66ab6d8 libstdc++-v3/testsuite/special_functions/20_sph_legendre/compile.cc ! c4f3a33bd5933dec7171c5134d77e231 libstdc++-v3/testsuite/special_functions/20_sph_legendre/compile_2.cc ! 0cf2e15663567b0643f04b350c5c02bd libstdc++-v3/testsuite/special_functions/21_sph_neumann/check_nan.cc ! c509d4385f9c22d2d8fa6775e1ba3428 libstdc++-v3/testsuite/special_functions/21_sph_neumann/check_value.cc ! 38a92e30b3ebac8e65ed4a742f3da1d1 libstdc++-v3/testsuite/special_functions/21_sph_neumann/compile.cc ! 7bf984287a5d79c1d0a38fc60fecc476 libstdc++-v3/testsuite/special_functions/21_sph_neumann/compile_2.cc db59d84f34e748db7b1dfa2c8b226d5f libstdc++-v3/testsuite/tr1/2_general_utilities/enable_shared_from_this/1.cc 9489c2f0342abf91af32b980141dcb3e libstdc++-v3/testsuite/tr1/2_general_utilities/enable_shared_from_this/not_shared.cc 8f1f797304d58d0a316b989811618970 libstdc++-v3/testsuite/tr1/2_general_utilities/enable_shared_from_this/not_shared2.cc *************** d50458761e75cbfe917048b85e10929d libstd *** 95714,95720 **** 32ec433d6047ab535d8bca33defc9fee libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/15_expint/compile.cc 4dea46bab1d8199b8d85cf0a3f66d237 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/15_expint/compile_2.cc d5a56898e336a0b024ef6a8828238ac8 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/check_nan.cc ! 99e5442eaf81f85a201268716891930d libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/check_value.cc 572faca966fb9464ccab1e645b278914 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/compile.cc dcbf52a4f47379c6e3c7ef17c9ea7ce6 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/compile_2.cc 143ef6a2d8e9f45fd646fc245fe2fe76 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/17_hyperg/check_nan.cc --- 95993,95999 ---- 32ec433d6047ab535d8bca33defc9fee libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/15_expint/compile.cc 4dea46bab1d8199b8d85cf0a3f66d237 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/15_expint/compile_2.cc d5a56898e336a0b024ef6a8828238ac8 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/check_nan.cc ! c462c61af4d3d60d4bc68b753baf0968 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/check_value.cc 572faca966fb9464ccab1e645b278914 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/compile.cc dcbf52a4f47379c6e3c7ef17c9ea7ce6 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/16_hermite/compile_2.cc 143ef6a2d8e9f45fd646fc245fe2fe76 libstdc++-v3/testsuite/tr1/5_numerical_facilities/special_functions/17_hyperg/check_nan.cc *************** e89aed78eb0c5a1be98e970dfc9cd16d libstd *** 96022,96028 **** 5e9c3749239e9bb533aa20bfd1ac1aec libstdc++-v3/testsuite/util/testsuite_abi.h 36e2943cac49fc06d42450a302758c3c libstdc++-v3/testsuite/util/testsuite_abi_check.cc c587eb9f6eefadcca70f4af1ad3e6d04 libstdc++-v3/testsuite/util/testsuite_allocator.cc ! fe68e8e3e25b171800ef91da13019510 libstdc++-v3/testsuite/util/testsuite_allocator.h 5949296edbbfd2bde121909d2690903a libstdc++-v3/testsuite/util/testsuite_api.h dba65a8227d38a8c35d47991059d8db3 libstdc++-v3/testsuite/util/testsuite_character.cc 47447d98ff7c4851fbe64fc8f0e54f33 libstdc++-v3/testsuite/util/testsuite_character.h --- 96301,96307 ---- 5e9c3749239e9bb533aa20bfd1ac1aec libstdc++-v3/testsuite/util/testsuite_abi.h 36e2943cac49fc06d42450a302758c3c libstdc++-v3/testsuite/util/testsuite_abi_check.cc c587eb9f6eefadcca70f4af1ad3e6d04 libstdc++-v3/testsuite/util/testsuite_allocator.cc ! 3796cdb7b688bf1efef8c3f22b90e60a libstdc++-v3/testsuite/util/testsuite_allocator.h 5949296edbbfd2bde121909d2690903a libstdc++-v3/testsuite/util/testsuite_api.h dba65a8227d38a8c35d47991059d8db3 libstdc++-v3/testsuite/util/testsuite_character.cc 47447d98ff7c4851fbe64fc8f0e54f33 libstdc++-v3/testsuite/util/testsuite_character.h *************** a6c215203442d14c9caba2165ce9294e libstd *** 96035,96041 **** ddba9e53377a44e2e0539802ac2b4bc2 libstdc++-v3/testsuite/util/testsuite_fs.h ff826c1dd2ee6a0fe894da2321232547 libstdc++-v3/testsuite/util/testsuite_greedy_ops.h c2aa93a55fce4b410f3963907115507e libstdc++-v3/testsuite/util/testsuite_hooks.cc ! a837c7d31a1866b0a6125d854aeeb3ba libstdc++-v3/testsuite/util/testsuite_hooks.h 03ef0d72a4d44308b72f20d48a98490f libstdc++-v3/testsuite/util/testsuite_io.h 014a5d7501d7109088bf371b70c55f19 libstdc++-v3/testsuite/util/testsuite_iterators.h 915de1d2f670ce7f4b76542e99a70c50 libstdc++-v3/testsuite/util/testsuite_new_operators.h --- 96314,96320 ---- ddba9e53377a44e2e0539802ac2b4bc2 libstdc++-v3/testsuite/util/testsuite_fs.h ff826c1dd2ee6a0fe894da2321232547 libstdc++-v3/testsuite/util/testsuite_greedy_ops.h c2aa93a55fce4b410f3963907115507e libstdc++-v3/testsuite/util/testsuite_hooks.cc ! 166c5f4e2e157df790e0c3c3f713ce04 libstdc++-v3/testsuite/util/testsuite_hooks.h 03ef0d72a4d44308b72f20d48a98490f libstdc++-v3/testsuite/util/testsuite_io.h 014a5d7501d7109088bf371b70c55f19 libstdc++-v3/testsuite/util/testsuite_iterators.h 915de1d2f670ce7f4b76542e99a70c50 libstdc++-v3/testsuite/util/testsuite_new_operators.h *************** b68e0657596760163b695df6c9e0547e libstd *** 96049,96055 **** 204ec69a032d5a889dacc11cf18fa4ed libstdc++-v3/testsuite/util/thread/all.h b950d655469c477755252b1e18009596 libtool-ldflags 7a2b83d2d625a4022b9213ceb75f5897 libtool.m4 ! 96336466ef7a21688c150beb0fb314e8 libvtv/ChangeLog 580d40bdd6efd6663aa0d78101a2ef1a libvtv/Makefile.am c9973f89d6d559403509edf0c5aa127f libvtv/Makefile.in 4ce86f8604e6c86211a4cb2025ffc53e libvtv/acinclude.m4 --- 96328,96334 ---- 204ec69a032d5a889dacc11cf18fa4ed libstdc++-v3/testsuite/util/thread/all.h b950d655469c477755252b1e18009596 libtool-ldflags 7a2b83d2d625a4022b9213ceb75f5897 libtool.m4 ! dbf8cf46013372fb608e22baa003d652 libvtv/ChangeLog 580d40bdd6efd6663aa0d78101a2ef1a libvtv/Makefile.am c9973f89d6d559403509edf0c5aa127f libvtv/Makefile.in 4ce86f8604e6c86211a4cb2025ffc53e libvtv/acinclude.m4 *************** aaf93f12a8558a61140e7da299033d08 libvtv *** 96132,96138 **** c69f9a511aeaa739d64c2ad1e42b2824 libvtv/vtv_utils.h 247597a3fcc5b5aa8bd923351c59d853 ltgcc.m4 4e65f2f6a05f5eca82ba79c6363aa3db ltmain.sh ! 373c4331cf29ef04de88111e79f0cb9f lto-plugin/ChangeLog 85ecc9762e15f3f34eda1f4861238840 lto-plugin/Makefile.am 7659e38293e2e0eefda3737f344a6a79 lto-plugin/Makefile.in b8a21afb1f79664ea28d8892b4907746 lto-plugin/aclocal.m4 --- 96411,96417 ---- c69f9a511aeaa739d64c2ad1e42b2824 libvtv/vtv_utils.h 247597a3fcc5b5aa8bd923351c59d853 ltgcc.m4 4e65f2f6a05f5eca82ba79c6363aa3db ltmain.sh ! e6c5f4122b9865d1ae6e40aae9a05d46 lto-plugin/ChangeLog 85ecc9762e15f3f34eda1f4861238840 lto-plugin/Makefile.am 7659e38293e2e0eefda3737f344a6a79 lto-plugin/Makefile.in b8a21afb1f79664ea28d8892b4907746 lto-plugin/aclocal.m4 *************** dee72a6a60e99528b0d17bf3ff9a1e15 ltopti *** 96145,96151 **** bc2f6032c98896249eadb56177c7d357 ltsugar.m4 c30cd33c496505f13d9fbdb6970c7c33 ltversion.m4 293853a13b7e218e3a4342cf85fbbf25 lt~obsolete.m4 ! de083dd0d17ab26462e5f67c44169fab maintainer-scripts/ChangeLog 33c7bc2d2c55956dfac85a05d8a80eff maintainer-scripts/README d0d4b92a5ba9606c481075c7bf65469a maintainer-scripts/crontab 91544f3a251dde1c76b2b9a58aee73a9 maintainer-scripts/gcc_release --- 96424,96430 ---- bc2f6032c98896249eadb56177c7d357 ltsugar.m4 c30cd33c496505f13d9fbdb6970c7c33 ltversion.m4 293853a13b7e218e3a4342cf85fbbf25 lt~obsolete.m4 ! 1cf49dcd8bc65e2e24dc6e43f5ef1622 maintainer-scripts/ChangeLog 33c7bc2d2c55956dfac85a05d8a80eff maintainer-scripts/README d0d4b92a5ba9606c481075c7bf65469a maintainer-scripts/crontab 91544f3a251dde1c76b2b9a58aee73a9 maintainer-scripts/gcc_release *************** fbe2467afef81c41c166173adeb0ee20 mkdep *** 96161,96167 **** cf2baa0854f564a7785307e79f155efc symlink-tree cb06c1be6a41d68b0a65e0c1a91752bc ylwrap 165622295231e685aaf15ec8de9e67f1 zlib/CMakeLists.txt ! b1444ab34b36c02ab041a9f63d5d154a zlib/ChangeLog 15b985f2db030e174ecd9aefc95df09b zlib/ChangeLog.gcj 0e9a37be8e3b85cc0ccf60504064c297 zlib/ChangeLog.jit b7a1991f01daea3efe108a215c5514a5 zlib/FAQ --- 96440,96446 ---- cf2baa0854f564a7785307e79f155efc symlink-tree cb06c1be6a41d68b0a65e0c1a91752bc ylwrap 165622295231e685aaf15ec8de9e67f1 zlib/CMakeLists.txt ! 6e27603bd93ec345e60cfdf4f2cecffb zlib/ChangeLog 15b985f2db030e174ecd9aefc95df09b zlib/ChangeLog.gcj 0e9a37be8e3b85cc0ccf60504064c297 zlib/ChangeLog.jit b7a1991f01daea3efe108a215c5514a5 zlib/FAQ diff -Nrcpad gcc-6.3.0/NEWS gcc-6.4.0/NEWS *** gcc-6.3.0/NEWS Wed Dec 21 07:55:26 2016 --- gcc-6.4.0/NEWS Tue Jul 4 07:29:30 2017 *************** see ONEWS. *** 6,31 **** ====================================================================== http://gcc.gnu.org/gcc-6/index.html GCC 6 Release Series ! December 21, 2016 The [1]GNU project and the GCC developers are pleased to announce the ! release of GCC 6.3. This release is a bug-fix release, containing fixes for regressions in ! GCC 6.2 relative to previous releases of GCC. Release History GCC 6.3 ! December 21, 2016 ([2]changes, [3]documentation) GCC 6.2 ! August 22, 2016 ([4]changes, [5]documentation) GCC 6.1 ! April 27, 2016 ([6]changes, [7]documentation) References and Acknowledgements --- 6,35 ---- ====================================================================== http://gcc.gnu.org/gcc-6/index.html + GCC 6 Release Series ! July 4, 2017 The [1]GNU project and the GCC developers are pleased to announce the ! release of GCC 6.4. This release is a bug-fix release, containing fixes for regressions in ! GCC 6.3 relative to previous releases of GCC. Release History + GCC 6.4 + July 4, 2017 ([2]changes, [3]documentation) + GCC 6.3 ! December 21, 2016 ([4]changes, [5]documentation) GCC 6.2 ! August 22, 2016 ([6]changes, [7]documentation) GCC 6.1 ! April 27, 2016 ([8]changes, [9]documentation) References and Acknowledgements *************** References and Acknowledgements *** 33,90 **** supports several other languages aside from C, it now stands for the GNU Compiler Collection. ! A list of [8]successful builds is updated as new information becomes available. The GCC developers would like to thank the numerous people that have contributed new features, improvements, bug fixes, and other changes as ! well as test results to GCC. This [9]amazing group of volunteers is what makes GCC successful. ! For additional information about GCC please refer to the [10]GCC ! project web site or contact the [11]GCC development mailing list. ! To obtain GCC please use [12]our mirror sites or [13]our SVN server. For questions related to the use of GCC, please consult these web ! pages and the [14]GCC manuals. If that fails, the ! [15]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 [16]gcc@gcc.gnu.org. All of [17]our lists have public archives. ! Copyright (C) [18]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [19]maintained by the GCC team. Last modified ! 2016-12-21[20]. References 1. http://www.gnu.org/ 2. http://gcc.gnu.org/gcc-6/changes.html ! 3. http://gcc.gnu.org/onlinedocs/6.3.0/ 4. http://gcc.gnu.org/gcc-6/changes.html ! 5. http://gcc.gnu.org/onlinedocs/6.2.0/ 6. http://gcc.gnu.org/gcc-6/changes.html ! 7. http://gcc.gnu.org/onlinedocs/6.1.0/ ! 8. http://gcc.gnu.org/gcc-6/buildstat.html ! 9. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html ! 10. http://gcc.gnu.org/index.html ! 11. mailto:gcc@gcc.gnu.org ! 12. http://gcc.gnu.org/mirrors.html ! 13. http://gcc.gnu.org/svn.html ! 14. https://gcc.gnu.org/onlinedocs/ ! 15. mailto:gcc-help@gcc.gnu.org ! 16. mailto:gcc@gcc.gnu.org ! 17. https://gcc.gnu.org/lists.html ! 18. http://www.fsf.org/ ! 19. https://gcc.gnu.org/about.html ! 20. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-6/changes.html GCC 6 Release Series Changes, New Features, and Fixes --- 37,97 ---- supports several other languages aside from C, it now stands for the GNU Compiler Collection. ! A list of [10]successful builds is updated as new information becomes available. The GCC developers would like to thank the numerous people that have contributed new features, improvements, bug fixes, and other changes as ! well as test results to GCC. This [11]amazing group of volunteers is what makes GCC successful. ! For additional information about GCC please refer to the [12]GCC ! project web site or contact the [13]GCC development mailing list. ! To obtain GCC please use [14]our mirror sites or [15]our SVN server. For questions related to the use of GCC, please consult these web ! pages and the [16]GCC manuals. If that fails, the ! [17]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 [18]gcc@gcc.gnu.org. All of [19]our lists have public archives. ! Copyright (C) [20]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [21]maintained by the GCC team. Last modified ! 2017-07-04[22]. References 1. http://www.gnu.org/ 2. http://gcc.gnu.org/gcc-6/changes.html ! 3. http://gcc.gnu.org/onlinedocs/6.4.0/ 4. http://gcc.gnu.org/gcc-6/changes.html ! 5. http://gcc.gnu.org/onlinedocs/6.3.0/ 6. http://gcc.gnu.org/gcc-6/changes.html ! 7. http://gcc.gnu.org/onlinedocs/6.2.0/ ! 8. http://gcc.gnu.org/gcc-6/changes.html ! 9. http://gcc.gnu.org/onlinedocs/6.1.0/ ! 10. http://gcc.gnu.org/gcc-6/buildstat.html ! 11. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html ! 12. http://gcc.gnu.org/index.html ! 13. mailto:gcc@gcc.gnu.org ! 14. http://gcc.gnu.org/mirrors.html ! 15. http://gcc.gnu.org/svn.html ! 16. https://gcc.gnu.org/onlinedocs/ ! 17. mailto:gcc-help@gcc.gnu.org ! 18. mailto:gcc@gcc.gnu.org ! 19. https://gcc.gnu.org/lists.html ! 20. http://www.fsf.org/ ! 21. https://gcc.gnu.org/about.html ! 22. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-6/changes.html + GCC 6 Release Series Changes, New Features, and Fixes *************** General Optimizer Improvements *** 117,126 **** 20-30% on higher-level C++ programs. Programs doing invalid type punning of pointer types may now need -fno-strict-aliasing to work correctly. ! * Alias analysis now correctly supports weakref and alias attributes. ! This makes it possible to access both a variable and its alias in one translation unit which is common with link-time optimization. ! * Value range propagation now assumes that the this pointer of C++ member functions is non-null. This eliminates common null pointer checks but also breaks some non-conforming code-bases (such as Qt-5, Chromium, KDevelop). As a temporary work-around --- 124,133 ---- 20-30% on higher-level C++ programs. Programs doing invalid type punning of pointer types may now need -fno-strict-aliasing to work correctly. ! * Alias analysis now correctly supports the weakref and alias ! attributes. This allows accessing both a variable and its alias in one translation unit which is common with link-time optimization. ! * Value range propagation now assumes that the this pointer in C++ member functions is non-null. This eliminates common null pointer checks but also breaks some non-conforming code-bases (such as Qt-5, Chromium, KDevelop). As a temporary work-around *************** General Optimizer Improvements *** 137,146 **** with char in all cases because it is an array while char is scalar. INTEGER(KIND=C_SIGNED_CHAR) should be used instead. In general, this inter-operability cannot be implemented, for ! example, on targets where function passing conventions of arrays differs from scalars. ! + More type information is now preserved at link time reducing ! the loss of accuracy of the type based alias analysis compared to builds without link-time optimization. + Invalid type punning on global variables and declarations is now reported with -Wodr-type-mismatch. --- 144,153 ---- with char in all cases because it is an array while char is scalar. INTEGER(KIND=C_SIGNED_CHAR) should be used instead. In general, this inter-operability cannot be implemented, for ! example on targets where the argument passing convention for arrays differs from scalars. ! + More type information is now preserved at link time, reducing ! the loss of accuracy of the type-based alias analysis compared to builds without link-time optimization. + Invalid type punning on global variables and declarations is now reported with -Wodr-type-mismatch. *************** General Optimizer Improvements *** 150,178 **** significantly improved by decreasing the size of streamed data when partitioning programs. The size of streamed IL while compiling Firefox 46.0 was reduced by 66%. ! + The linker plugin was extended to pass information about type ! of binary produced to GCC back end (that can be also manually ! controlled by -flinker-output). This makes it possible to ! properly configure the code generator and support incremental ! linking. Incremental linking of LTO objects by gcc -r is now ! supported on plugin-enabled setups. There are two ways to perform incremental linking: 1. Linking by ld -r will result in an object file with all sections from individual object files mechanically ! merged. This delays the actual link time optimization to ! final linking step and thus permits whole program ! optimization. Linking final binary with such object files ! is however slower. ! 2. Linking by gcc -r will lead to link time optimization and ! produce final binary into the object file. Linking such ! object file is fast but avoids any benefits from whole program optimization. GCC 7 will support incremental link-time optimization with gcc -r. * Inter-procedural optimization improvements: + Basic jump threading is now performed before profile construction and inline analysis, resulting in more realistic ! size and time estimates that drive the heuristics of the of inliner and function cloning passes. + Function cloning now more aggressively eliminates unused function parameters. --- 157,185 ---- significantly improved by decreasing the size of streamed data when partitioning programs. The size of streamed IL while compiling Firefox 46.0 was reduced by 66%. ! + The linker plugin was extended to pass information about the ! type of binary produced to the GCC back end. (That can also be ! controlled manually by -flinker-output.) This makes it ! possible to properly configure the code generator and support ! incremental linking. Incremental linking of LTO objects by gcc ! -r is now supported for plugin-enabled setups. There are two ways to perform incremental linking: 1. Linking by ld -r will result in an object file with all sections from individual object files mechanically ! merged. This delays the actual link-time optimization to ! the final linking step and thus permits whole program ! optimization. Linking the final binary with such object ! files is however slower. ! 2. Linking by gcc -r will lead to link-time optimization and ! emit the final binary into the object file. Linking such ! an object file is fast but avoids any benefits from whole program optimization. GCC 7 will support incremental link-time optimization with gcc -r. * Inter-procedural optimization improvements: + Basic jump threading is now performed before profile construction and inline analysis, resulting in more realistic ! size and time estimates that drive the heuristics of the inliner and function cloning passes. + Function cloning now more aggressively eliminates unused function parameters. *************** New Targets and Target Specific Improvem *** 388,396 **** AArch64 * A number of AArch64-specific options have been added. The most ! important ones are summarised in this section but for usage ! instructions please refer to the documentation. ! * The new command-line options -march=native, -mcpu=native and -mtune=native are now available on native AArch64 GNU/Linux systems. Specifying these options causes GCC to auto-detect the host CPU and choose the optimal setting for that system. --- 395,403 ---- AArch64 * A number of AArch64-specific options have been added. The most ! important ones are summarised in this section; for more detailed ! information please refer to the documentation. ! * The command-line options -march=native, -mcpu=native and -mtune=native are now available on native AArch64 GNU/Linux systems. Specifying these options causes GCC to auto-detect the host CPU and choose the optimal setting for that system. *************** New Targets and Target Specific Improvem *** 437,450 **** offer increased performance when compiling with -mcpu=exynos-m1 or -mtune=exynos-m1. * Improvements in the generation of conditional branches and literal ! pools were made to allow the compiler to compile functions of a ! large size. Constant pools are now placed into separate rodata ! sections. The new option -mpc-relative-literal-loads is introduced ! to generate per-function literal pools, limiting the maximum size ! of functions to 1MiB. ! * Several correctness issues with generation of Advanced SIMD ! instructions for big-endian targets have been fixed resulting in ! improved code generation for ACLE intrinsics with -mbig-endian. ARM --- 444,456 ---- offer increased performance when compiling with -mcpu=exynos-m1 or -mtune=exynos-m1. * Improvements in the generation of conditional branches and literal ! pools allow the compiler to compile functions of a large size. ! Constant pools are now placed into separate rodata sections. The ! new option -mpc-relative-literal-loads generates per-function ! literal pools, limiting the maximum size of functions to 1MiB. ! * Several correctness issues generating Advanced SIMD instructions ! for big-endian targets have been fixed resulting in improved code ! generation for ACLE intrinsics with -mbig-endian. ARM *************** New Targets and Target Specific Improvem *** 630,640 **** partially compatible to the PowerPC Altivec builtins. In order to make use of these builtins the vecintrin.h header file needs to be included. ! * The new command line options -march=native, and -mtune=native are now available on native IBM z Systems. Specifying these options ! will cause GCC to auto-detect the host CPU and rewrite these ! options to the optimal setting for that system. If GCC is unable to ! detect the host CPU these options have no effect. * The IBM z Systems port now supports target attributes and pragmas. Please refer to the [19]documentation for details of available attributes and pragmas as well as usage instructions. --- 636,646 ---- partially compatible to the PowerPC Altivec builtins. In order to make use of these builtins the vecintrin.h header file needs to be included. ! * The new command-line options -march=native, and -mtune=native are now available on native IBM z Systems. Specifying these options ! causes GCC to auto-detect the host CPU and choose the optimal ! setting for that system. If GCC is unable to detect the host CPU ! these options have no effect. * The IBM z Systems port now supports target attributes and pragmas. Please refer to the [19]documentation for details of available attributes and pragmas as well as usage instructions. *************** Operating Systems *** 715,721 **** Other significant improvements * The gcc and g++ driver programs will now provide suggestions for ! misspelled command line options. $ gcc -static-libfortran test.f95 gcc: error: unrecognized command line option '-static-libfortran'; did you mean --- 721,727 ---- Other significant improvements * The gcc and g++ driver programs will now provide suggestions for ! misspelled command-line options. $ gcc -static-libfortran test.f95 gcc: error: unrecognized command line option '-static-libfortran'; did you mean *************** gcc: error: unrecognized command line op *** 724,730 **** * The --enable-default-pie configure option enables generation of PIE by default. ! GCC 6.2 This is the [21]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 6.2 release. This list might --- 730,736 ---- * The --enable-default-pie configure option enables generation of PIE by default. ! GCC 6.2 This is the [21]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 6.2 release. This list might *************** Target Specific Changes *** 740,766 **** * Support for the SPARC M7 (Niagara 7) processor has been added. * Support for the VIS 4.0 instruction set has been added. ! GCC 6.3 This is the [22]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 6.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [23]GCC manuals. If that fails, the ! [24]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 [25]gcc@gcc.gnu.org. All of [26]our lists have public archives. ! Copyright (C) [27]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [28]maintained by the GCC team. Last modified ! 2016-12-21[29]. References --- 746,792 ---- * Support for the SPARC M7 (Niagara 7) processor has been added. * Support for the VIS 4.0 instruction set has been added. ! GCC 6.3 This is the [22]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 6.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). + Target Specific Changes + + IA-32/x86-64 + + * Support for the [23]deprecated pcommit instruction has been + removed. + + GCC 6.4 + + This is the [24]list of problem reports (PRs) from GCC's bug tracking + system that are known to be fixed in the 6.4 release. This list might + not be complete (that is, it is possible that some PRs that have been + fixed are not listed here). + + Operating Systems + + RTEMS + + * The ABI changes on ARM so that no short enums are used by default. + For questions related to the use of GCC, please consult these web ! pages and the [25]GCC manuals. If that fails, the ! [26]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 [27]gcc@gcc.gnu.org. All of [28]our lists have public archives. ! Copyright (C) [29]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [30]maintained by the GCC team. Last modified ! 2017-07-04[31]. References *************** References *** 768,780 **** 2. http://gcc.gnu.org/onlinedocs/index.html#current 3. https://gcc.gnu.org/ml/gcc/2015-08/msg00101.html 4. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71151 ! 5. http://www.openacc.org/ 6. https://gcc.gnu.org/wiki/OpenACC 7. https://gcc.gnu.org/wiki/Offloading ! 8. http://openmp.org/wp/openmp-specifications/ 9. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-1266 10. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4377.pdf ! 11. https://gcc.gnu.org/projects/cxx-status.html#cxx1z.html 12. https://gcc.gnu.org/onlinedocs/gcc-6.1.0/jit/topics/performance.html 13. https://gcc.gnu.org/onlinedocs/gcc-6.1.0/jit/topics/functions.html#gcc_jit_block_end_with_switch 14. https://gcc.gnu.org/onlinedocs/gcc-6.1.0/jit/topics/contexts.html#gcc_jit_context_set_bool_allow_unreachable_blocks --- 794,806 ---- 2. http://gcc.gnu.org/onlinedocs/index.html#current 3. https://gcc.gnu.org/ml/gcc/2015-08/msg00101.html 4. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71151 ! 5. https://www.openacc.org/ 6. https://gcc.gnu.org/wiki/OpenACC 7. https://gcc.gnu.org/wiki/Offloading ! 8. http://www.openmp.org/specifications/ 9. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-1266 10. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4377.pdf ! 11. https://gcc.gnu.org/projects/cxx-status.html#cxx1z 12. https://gcc.gnu.org/onlinedocs/gcc-6.1.0/jit/topics/performance.html 13. https://gcc.gnu.org/onlinedocs/gcc-6.1.0/jit/topics/functions.html#gcc_jit_block_end_with_switch 14. https://gcc.gnu.org/onlinedocs/gcc-6.1.0/jit/topics/contexts.html#gcc_jit_context_set_bool_allow_unreachable_blocks *************** References *** 786,800 **** 20. http://www.musl-libc.org/ 21. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=6.2 22. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=6.3 ! 23. https://gcc.gnu.org/onlinedocs/ ! 24. mailto:gcc-help@gcc.gnu.org ! 25. mailto:gcc@gcc.gnu.org ! 26. https://gcc.gnu.org/lists.html ! 27. http://www.fsf.org/ ! 28. https://gcc.gnu.org/about.html ! 29. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-5/index.html GCC 5 Release Series June 3, 2016 --- 812,829 ---- 20. http://www.musl-libc.org/ 21. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=6.2 22. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=6.3 ! 23. https://software.intel.com/en-us/blogs/2016/09/12/deprecate-pcommit-instruction ! 24. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=6.4 ! 25. https://gcc.gnu.org/onlinedocs/ ! 26. mailto:gcc-help@gcc.gnu.org ! 27. mailto:gcc@gcc.gnu.org ! 28. https://gcc.gnu.org/lists.html ! 29. http://www.fsf.org/ ! 30. https://gcc.gnu.org/about.html ! 31. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-5/index.html + GCC 5 Release Series June 3, 2016 *************** References *** 879,884 **** --- 908,914 ---- 22. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-5/changes.html + GCC 5 Release Series Changes, New Features, and Fixes *************** void operator delete[] (void *, std::siz *** 1293,1300 **** * Compatibility notice: + The version of the module files (.mod) has been incremented. ! + For free-form source files, [22]-Werror=line-truncation is now ! enabled by default; note that comments exceeding the line length are not diagnosed. (For fixed-form source code, the same warning is available but turned off by default, such that excess characters are ignored. -ffree-line-length-n and --- 1323,1330 ---- * Compatibility notice: + The version of the module files (.mod) has been incremented. ! + For free-form source files [22]-Werror=line-truncation is now ! enabled by default. Note that comments exceeding the line length are not diagnosed. (For fixed-form source code, the same warning is available but turned off by default, such that excess characters are ignored. -ffree-line-length-n and *************** void operator delete[] (void *, std::siz *** 1303,1309 **** + The -Wtabs option is now more sensible: with -Wtabs the compiler warns if it encounters tabs and with -Wno-tabs this warning is turned off. Before, -Wno-tabs warned and -Wtabs ! turned the warning off. As before, the warning is also enabled by -Wall, -pedantic and the f95, f2003, f2008 and f2008ts options of -std=. * Incomplete support for colorizing diagnostics emitted by gfortran --- 1333,1339 ---- + The -Wtabs option is now more sensible: with -Wtabs the compiler warns if it encounters tabs and with -Wno-tabs this warning is turned off. Before, -Wno-tabs warned and -Wtabs ! disabled the warning. As before, this warning is also enabled by -Wall, -pedantic and the f95, f2003, f2008 and f2008ts options of -std=. * Incomplete support for colorizing diagnostics emitted by gfortran *************** New Targets and Target Specific Improvem *** 1493,1499 **** IA-32/x86-64 ! * New ISA extensions support [40]AVX-512{BW,DQ,VL,IFMA,VBMI} of Intel's CPU codenamed Skylake Server was added to GCC. That includes inline assembly support, new intrinsics, and basic autovectorization. These new AVX-512 extensions are available via --- 1523,1529 ---- IA-32/x86-64 ! * New [40]ISA extensions support AVX-512{BW,DQ,VL,IFMA,VBMI} of Intel's CPU codenamed Skylake Server was added to GCC. That includes inline assembly support, new intrinsics, and basic autovectorization. These new AVX-512 extensions are available via *************** New Targets and Target Specific Improvem *** 1502,1508 **** Dword and Qword instructions: -mavx512dq, AVX-512 FMA-52 instructions: -mavx512ifma and for AVX-512 Vector Bit Manipulation Instructions: -mavx512vbmi. ! * New ISA extensions support [41]Intel MPX was added to GCC. This new extension is available via the -mmpx compiler switch. Intel MPX is a set of processor features which, with compiler, run-time library and OS support, brings increased robustness to software by run-time --- 1532,1538 ---- Dword and Qword instructions: -mavx512dq, AVX-512 FMA-52 instructions: -mavx512ifma and for AVX-512 Vector Bit Manipulation Instructions: -mavx512vbmi. ! * New ISA extensions support Intel MPX was added to GCC. This new extension is available via the -mmpx compiler switch. Intel MPX is a set of processor features which, with compiler, run-time library and OS support, brings increased robustness to software by run-time *************** New Targets and Target Specific Improvem *** 1632,1637 **** --- 1662,1673 ---- Operating Systems + AIX + + * GCC now supports stabs debugging continuation lines to allow long + stabs debug information without overflow that generates AIX linker + errors. + DragonFly BSD * GCC now supports the DragonFly BSD operating system. *************** Other significant improvements *** 1656,1664 **** automatically generates a developer-friendly reproducer whenever an internal compiler error is encountered. ! GCC 5.2 ! This is the [42]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). --- 1692,1700 ---- automatically generates a developer-friendly reproducer whenever an internal compiler error is encountered. ! GCC 5.2 ! This is the [41]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). *************** Target Specific Changes *** 1697,1705 **** make use of these builtins the vecintrin.h header file needs to be included. ! GCC 5.3 ! This is the [43]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). --- 1733,1741 ---- make use of these builtins the vecintrin.h header file needs to be included. ! GCC 5.3 ! This is the [42]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). *************** Target Specific Changes *** 1719,1738 **** the GO runtime environment. GCC 5.3 has proven to be able to compile larger GO applications on IBM z Systems. ! GCC 5.4 ! This is the [44]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). ! (Pending) GCC 5.5 ! This is the [45]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web pages and the [46]GCC manuals. If that fails, the --- 1755,1781 ---- the GO runtime environment. GCC 5.3 has proven to be able to compile larger GO applications on IBM z Systems. ! GCC 5.4 ! This is the [43]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). ! (Pending) GCC 5.5 ! This is the [44]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 5.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). + Target Specific Changes + + IA-32/x86-64 + + * Support for the [45]deprecated pcommit instruction has been + removed. + For questions related to the use of GCC, please consult these web pages and the [46]GCC manuals. If that fails, the *************** GCC 5.4 *** 1746,1761 **** provided this notice is preserved. These pages are [51]maintained by the GCC team. Last modified ! 2016-06-03[52]. References 1. http://gcc.gnu.org/gcc-5/changes.html#libstdcxx 2. https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html 3. https://savannah.nongnu.org/bugs/?44574 ! 4. https://gcc.gnu.org/wiki/Intel MPX support in the GCC compiler ! 5. http://www.openmp.org/mp-documents/OpenMP4.0.0.pdf ! 6. http://openmp.org/mp-documents/OpenMP4.0.0.Examples.pdf 7. https://gcc.gnu.org/wiki/OpenACC 8. https://gcc.gnu.org/install/configure.html 9. https://www.cilkplus.org/ --- 1789,1804 ---- provided this notice is preserved. These pages are [51]maintained by the GCC team. Last modified ! 2017-03-12[52]. References 1. http://gcc.gnu.org/gcc-5/changes.html#libstdcxx 2. https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html 3. https://savannah.nongnu.org/bugs/?44574 ! 4. https://gcc.gnu.org/wiki/Intel%20MPX%20support%20in%20the%20GCC%20compiler ! 5. http://www.openmp.org/wp-content/uploads/OpenMP4.0.0.pdf ! 6. http://www.openmp.org/wp-content/uploads/OpenMP4.0.0.Examples.pdf 7. https://gcc.gnu.org/wiki/OpenACC 8. https://gcc.gnu.org/install/configure.html 9. https://www.cilkplus.org/ *************** References *** 1789,1800 **** 37. https://gcc.gnu.org/onlinedocs/gcc-5.1.0/jit/intro/tutorial05.html 38. https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html 39. https://gcc.gnu.org/onlinedocs/gcc/Named-Address-Spaces.html ! 40. https://software.intel.com/sites/default/files/managed/0d/53/319433-023.pdf ! 41. https://software.intel.com/sites/default/files/managed/0d/53/319433-022.pdf ! 42. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.2 ! 43. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.3 ! 44. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.4 ! 45. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.5 46. https://gcc.gnu.org/onlinedocs/ 47. mailto:gcc-help@gcc.gnu.org 48. mailto:gcc@gcc.gnu.org --- 1832,1843 ---- 37. https://gcc.gnu.org/onlinedocs/gcc-5.1.0/jit/intro/tutorial05.html 38. https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html 39. https://gcc.gnu.org/onlinedocs/gcc/Named-Address-Spaces.html ! 40. https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf ! 41. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.2 ! 42. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.3 ! 43. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.4 ! 44. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.5 ! 45. https://software.intel.com/en-us/blogs/2016/09/12/deprecate-pcommit-instruction 46. https://gcc.gnu.org/onlinedocs/ 47. mailto:gcc-help@gcc.gnu.org 48. mailto:gcc@gcc.gnu.org *************** References *** 1804,1809 **** --- 1847,1853 ---- 52. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.9/index.html + GCC 4.9 Release Series Aug 3, 2016 *************** References *** 1895,1900 **** --- 1939,1945 ---- 24. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.9/changes.html + GCC 4.9 Release Series Changes, New Features, and Fixes *************** New Languages and Language specific impr *** 2008,2028 **** -fdiagnostics-color=never. Sample diagnostics output: $ g++ -fdiagnostics-color=always -S -Wall test.C ! test.C: In function ‘int foo()’: test.C:1:14: warning: no return statement in function returning non-void [-W return-type] int foo () { } ^ test.C:2:46: error: template instantiation depth exceeds maximum of 900 (use ! -ftemplate-depth= to increase the maximum) instantiating ‘struct X<100>’ template struct X { static const int value = X::value; }; temp late struct X<1000>; ^ ! test.C:2:46: recursively required from ‘const int X<999>::value’ ! test.C:2:46: required from ‘const int X<1000>::value’ test.C:2:88: required from here ! test.C:2:46: error: incomplete type ‘X<100>’ used in nested name specifier * With the new [7]#pragma GCC ivdep, the user can assert that there are no loop-carried dependencies which would prevent concurrent --- 2053,2073 ---- -fdiagnostics-color=never. Sample diagnostics output: $ g++ -fdiagnostics-color=always -S -Wall test.C ! test.C: In function `int foo()': test.C:1:14: warning: no return statement in function returning non-void [-W return-type] int foo () { } ^ test.C:2:46: error: template instantiation depth exceeds maximum of 900 (use ! -ftemplate-depth= to increase the maximum) instantiating `struct X<100>' template struct X { static const int value = X::value; }; temp late struct X<1000>; ^ ! test.C:2:46: recursively required from `const int X<999>::value' ! test.C:2:46: required from `const int X<1000>::value' test.C:2:88: required from here ! test.C:2:46: error: incomplete type `X<100>' used in nested name specifier * With the new [7]#pragma GCC ivdep, the user can assert that there are no loop-carried dependencies which would prevent concurrent *************** auto incr = [](auto x) { return x++; }; *** 2127,2137 **** // a functional object that will add two like-type objects auto add = [] (T a, T b) { return a + b; }; ! * G++ supports unconstrained generic functions as specified by §4.1.2 ! and §5.1.1 of [16]N3889: Concepts Lite Specification. Briefly, auto ! may be used as a type-specifier in a parameter declaration of any ! function declarator in order to introduce an implicit function ! template parameter, akin to generic lambdas. // the following two function declarations are equivalent auto incr(auto x) { return x++; } --- 2172,2182 ---- // a functional object that will add two like-type objects auto add = [] (T a, T b) { return a + b; }; ! * G++ supports unconstrained generic functions as specified by ! S:4.1.2 and S:5.1.1 of [16]N3889: Concepts Lite Specification. ! Briefly, auto may be used as a type-specifier in a parameter ! declaration of any function declarator in order to introduce an ! implicit function template parameter, akin to generic lambdas. // the following two function declarations are equivalent auto incr(auto x) { return x++; } *************** auto incr(T x) { return x++; } *** 2221,2227 **** be used as argument to ISO_C_BINDING's C_LOC and as actual argument to another NO_ARG_CHECK dummy argument; also the other constraints of TYPE(*) apply. The dummy arguments should be declared as scalar ! or assumed-size variable of type type(*) (recommended) – or of type integer, real, complex or logical. With NO_ARG_CHECK, a pointer to the data without further type or shape information is passed, similar to C's void*. Note that also TS 29113's --- 2266,2272 ---- be used as argument to ISO_C_BINDING's C_LOC and as actual argument to another NO_ARG_CHECK dummy argument; also the other constraints of TYPE(*) apply. The dummy arguments should be declared as scalar ! or assumed-size variable of type type(*) (recommended) - or of type integer, real, complex or logical. With NO_ARG_CHECK, a pointer to the data without further type or shape information is passed, similar to C's void*. Note that also TS 29113's *************** GCC 4.9.1 *** 2467,2517 **** not be complete (that is, it is possible that some PRs that have been fixed are not listed here). ! Version 4.0 of the [26]OpenMP specification is supported even in ! Fortran, not just C and C++. GCC 4.9.2 ! This is the [27]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.9.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.9.3 ! This is the [28]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.9.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.9.4 ! This is the [29]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.9.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [30]GCC manuals. If that fails, the ! [31]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 [32]gcc@gcc.gnu.org. All of [33]our lists have public archives. ! Copyright (C) [34]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [35]maintained by the GCC team. Last modified ! 2016-08-03[36]. References 1. https://gcc.gnu.org/ml/gcc-patches/2013-05/msg00728.html 2. https://gcc.gnu.org/PR60825 3. https://gcc.gnu.org/gcc-4.9/porting_to.html ! 4. http://openmp.org/wp/openmp-specifications/ 5. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html#index-fsimd-cost-model-908 6. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Language-Independent-Options.html#index-fdiagnostics-color-252 7. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Loop-Specific-Pragmas.html --- 2512,2562 ---- not be complete (that is, it is possible that some PRs that have been fixed are not listed here). ! Version 4.0 of the OpenMP specification is supported even in Fortran, ! not just C and C++. GCC 4.9.2 ! This is the [26]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.9.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.9.3 ! This is the [27]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.9.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.9.4 ! This is the [28]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.9.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [29]GCC manuals. If that fails, the ! [30]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 [31]gcc@gcc.gnu.org. All of [32]our lists have public archives. ! Copyright (C) [33]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [34]maintained by the GCC team. Last modified ! 2016-12-28[35]. References 1. https://gcc.gnu.org/ml/gcc-patches/2013-05/msg00728.html 2. https://gcc.gnu.org/PR60825 3. https://gcc.gnu.org/gcc-4.9/porting_to.html ! 4. http://www.openmp.org/specifications/ 5. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html#index-fsimd-cost-model-908 6. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Language-Independent-Options.html#index-fdiagnostics-color-252 7. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Loop-Specific-Pragmas.html *************** References *** 2533,2551 **** 23. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gfortran/Debugging-Options.html 24. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Function-Multiversioning.html 25. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.1 ! 26. http://openmp.org/wp/openmp-specifications/ ! 27. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.2 ! 28. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.3 ! 29. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.4 ! 30. https://gcc.gnu.org/onlinedocs/ ! 31. mailto:gcc-help@gcc.gnu.org ! 32. mailto:gcc@gcc.gnu.org ! 33. https://gcc.gnu.org/lists.html ! 34. http://www.fsf.org/ ! 35. https://gcc.gnu.org/about.html ! 36. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.8/index.html GCC 4.8 Release Series June 23, 2015 --- 2578,2596 ---- 23. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gfortran/Debugging-Options.html 24. https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Function-Multiversioning.html 25. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.1 ! 26. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.2 ! 27. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.3 ! 28. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.4 ! 29. https://gcc.gnu.org/onlinedocs/ ! 30. mailto:gcc-help@gcc.gnu.org ! 31. mailto:gcc@gcc.gnu.org ! 32. https://gcc.gnu.org/lists.html ! 33. http://www.fsf.org/ ! 34. https://gcc.gnu.org/about.html ! 35. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.8/index.html + GCC 4.8 Release Series June 23, 2015 *************** References *** 2642,2647 **** --- 2687,2693 ---- 26. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.8/changes.html + GCC 4.8 Release Series Changes, New Features, and Fixes *************** New Languages and Language specific impr *** 2770,2777 **** diagnostics. Combined with the caret information, an example diagnostic showing these two features is: ! t.c:1:94: error: invalid operands to binary < (have ‘struct mystruct’ and ‘float ! ’) #define MYMAX(A,B) __extension__ ({ __typeof__(A) __a = (A); __typeof__(B) _ _b = (B); __a < __b ? __b : __a; }) --- 2816,2823 ---- diagnostics. Combined with the caret information, an example diagnostic showing these two features is: ! t.c:1:94: error: invalid operands to binary < (have `struct mystruct' and `float ! ') #define MYMAX(A,B) __extension__ ({ __typeof__(A) __a = (A); __typeof__(B) _ _b = (B); __a < __b ? __b : __a; }) *************** int i = A().f(); // error, f() requires *** 2895,2902 **** older versions except as noted below. + ABI: Some internal names (used in the assembler/object file) have changed for symbols declared in the specification part of ! a module. If an affected module – or a file using it via use ! association – is recompiled, the module and all files which directly use such symbols have to be recompiled as well. This change only affects the following kind of module symbols: o Procedure pointers. Note: C-interoperable function --- 2941,2948 ---- older versions except as noted below. + ABI: Some internal names (used in the assembler/object file) have changed for symbols declared in the specification part of ! a module. If an affected module - or a file using it via use ! association - is recompiled, the module and all files which directly use such symbols have to be recompiled as well. This change only affects the following kind of module symbols: o Procedure pointers. Note: C-interoperable function *************** int i = A().f(); // error, f() requires *** 2923,2929 **** * The [21]-Wcompare-reals command-line option has been added. When this is set, warnings are issued when comparing REAL or COMPLEX types for equality and inequality; consider replacing a == b by ! abs(a−b) < eps with a suitable eps. -Wcompare-reals is enabled by -Wextra. * The [22]-Wtarget-lifetime command-line option has been added (enabled with -Wall), which warns if the pointer in a pointer --- 2969,2975 ---- * The [21]-Wcompare-reals command-line option has been added. When this is set, warnings are issued when comparing REAL or COMPLEX types for equality and inequality; consider replacing a == b by ! abs(a-b) < eps with a suitable eps. -Wcompare-reals is enabled by -Wextra. * The [22]-Wtarget-lifetime command-line option has been added (enabled with -Wall), which warns if the pointer in a pointer *************** int i = A().f(); // error, f() requires *** 2935,2941 **** 4.0e0). (For Fortran source code, consider replacing the "q" in floating-point literals by a kind parameter (e.g. 4.0e0_qp with a ! suitable qp). Note that – in Fortran source code – replacing "q" by a simple "e" is not equivalent.) * The GFORTRAN_TMPDIR environment variable for specifying a non-default directory for files opened with STATUS="SCRATCH", is --- 2981,2987 ---- 4.0e0). (For Fortran source code, consider replacing the "q" in floating-point literals by a kind parameter (e.g. 4.0e0_qp with a ! suitable qp). Note that - in Fortran source code - replacing "q" by a simple "e" is not equivalent.) * The GFORTRAN_TMPDIR environment variable for specifying a non-default directory for files opened with STATUS="SCRATCH", is *************** New Targets and Target Specific Improvem *** 3030,3037 **** } The inline assembler in this example will generate code like mov r24, 8+7 ! provided c is allocated to R24 and val is allocated to R8…R15. This ! works because the GNU assembler accepts plain register numbers without register prefix. * Static initializers with 3-byte symbols are supported now: extern const __memx char foo; --- 3076,3083 ---- } The inline assembler in this example will generate code like mov r24, 8+7 ! provided c is allocated to R24 and val is allocated to R8...R15. ! This works because the GNU assembler accepts plain register numbers without register prefix. * Static initializers with 3-byte symbols are supported now: extern const __memx char foo; *************** New Targets and Target Specific Improvem *** 3282,3287 **** --- 3328,3338 ---- Operating Systems + OpenBSD + + * Support for OpenBSD/amd64 (x86_64-*-openbsd*) has been added and + support for OpenBSD/i386 (i386-*-openbsd*) has been rejuvenated. + Windows (Cygwin) * Executables are now linked against shared libgcc by default. The *************** GCC 4.8.5 *** 3360,3366 **** provided this notice is preserved. These pages are [43]maintained by the GCC team. Last modified ! 2016-05-28[44]. References --- 3411,3417 ---- provided this notice is preserved. These pages are [43]maintained by the GCC team. Last modified ! 2017-02-27[44]. References *************** References *** 3389,3395 **** 23. https://gcc.gnu.org/onlinedocs/gfortran/TMPDIR.html 24. https://gcc.gnu.org/wiki/Fortran2003Status 25. https://gcc.gnu.org/wiki/TS29113Status ! 26. https://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text/plain&view=co 27. http://chasm-interop.sourceforge.net/ 28. https://gcc.gnu.org/wiki/avr-gcc#Fixed-Point_Support 29. https://gcc.gnu.org/onlinedocs/gcc/Fixed-Point.html --- 3440,3446 ---- 23. https://gcc.gnu.org/onlinedocs/gfortran/TMPDIR.html 24. https://gcc.gnu.org/wiki/Fortran2003Status 25. https://gcc.gnu.org/wiki/TS29113Status ! 26. https://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text%2Fplain&view=co 27. http://chasm-interop.sourceforge.net/ 28. https://gcc.gnu.org/wiki/avr-gcc#Fixed-Point_Support 29. https://gcc.gnu.org/onlinedocs/gcc/Fixed-Point.html *************** References *** 3410,3415 **** --- 3461,3467 ---- 44. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.7/index.html + GCC 4.7 Release Series June 12, 2014 *************** References *** 3501,3506 **** --- 3553,3559 ---- 24. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.7/changes.html + GCC 4.7 Release Series Changes, New Features, and Fixes *************** long double pi = 180.0_degrees; *** 3831,3837 **** template using Ptr = T*; Ptr ip; // decltype(ip) is int* ! * Thanks to Ville Voutilainen and Pedro Lamarão, G++ now implements [13]C++11 delegating constructors. struct A { --- 3884,3890 ---- template using Ptr = T*; Ptr ip; // decltype(ip) is int* ! * Thanks to Ville Voutilainen and Pedro Lamarao, G++ now implements [13]C++11 delegating constructors. struct A { *************** New Targets and Target Specific Improvem *** 4025,4031 **** * GCC now supports the XMEGA architecture. This requires GNU binutils 2.22 or later. ! * Support for the [36]named address spaces __flash, __flash1, …, __flash5 and __memx has been added. These address spaces locate read-only data in flash memory and allow reading from flash memory by means of ordinary C code, i.e. without the need of (inline) --- 4078,4084 ---- * GCC now supports the XMEGA architecture. This requires GNU binutils 2.22 or later. ! * Support for the [36]named address spaces __flash, __flash1, ..., __flash5 and __memx has been added. These address spaces locate read-only data in flash memory and allow reading from flash memory by means of ordinary C code, i.e. without the need of (inline) *************** void set_portb (uint8_t value) *** 4069,4075 **** suitable to be used as operand in an I/O command. The address must be a constant integer known at compile time. * The inline assembler constraint "R" to represent integers in the ! range −6 … 5 has been removed without replacement. * Many optimizations to: + 64-bit integer arithmetic + Widening multiplication --- 4122,4128 ---- suitable to be used as operand in an I/O command. The address must be a constant integer known at compile time. * The inline assembler constraint "R" to represent integers in the ! range -6 ... 5 has been removed without replacement. * Many optimizations to: + 64-bit integer arithmetic + Widening multiplication *************** void set_portb (uint8_t value) *** 4081,4087 **** + If-else decision trees generated by switch instructions + Merging of data located in flash memory + New libgcc variants for devices with 8-bit wide stack pointer ! + … * Better documentation: + Handling of EIND and indirect jumps on devices with more than 128 KiB of program memory. --- 4134,4140 ---- + If-else decision trees generated by switch instructions + Merging of data located in flash memory + New libgcc variants for devices with 8-bit wide stack pointer ! + ... * Better documentation: + Handling of EIND and indirect jumps on devices with more than 128 KiB of program memory. *************** GCC 4.7.4 *** 4292,4298 **** provided this notice is preserved. These pages are [55]maintained by the GCC team. Last modified ! 2016-11-27[56]. References --- 4345,4351 ---- provided this notice is preserved. These pages are [55]maintained by the GCC team. Last modified ! 2017-03-03[56]. References *************** References *** 4300,4306 **** 2. http://savannah.nongnu.org/bugs/?35407 3. https://gcc.gnu.org/PR18145 4. https://gcc.gnu.org/gcc-4.7/porting_to.html ! 5. http://openmp.org/wp/openmp-specifications/ 6. https://gcc.gnu.org/wiki/TransactionalMemory 7. https://gcc.gnu.org/wiki/Atomic/GCCMM 8. http://gcc.gnu.org/gcc-4.7/cxx0x_status.html --- 4353,4359 ---- 2. http://savannah.nongnu.org/bugs/?35407 3. https://gcc.gnu.org/PR18145 4. https://gcc.gnu.org/gcc-4.7/porting_to.html ! 5. http://www.openmp.org/specifications/ 6. https://gcc.gnu.org/wiki/TransactionalMemory 7. https://gcc.gnu.org/wiki/Atomic/GCCMM 8. http://gcc.gnu.org/gcc-4.7/cxx0x_status.html *************** References *** 4321,4327 **** 23. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfaggressive-function-elimination_007d-270 24. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWreal-q-constant_007d-149 25. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/SELECTED_005fREAL_005fKIND.html ! 26. https://msdn.microsoft.com/en-us/library/bb787181(v=vs.85).aspx 27. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Debugging-Options.html#index-g_t_0040code_007bfno-backtrace_007d-183 28. https://gcc.gnu.org/wiki/Fortran2003Status 29. https://gcc.gnu.org/wiki/OOP --- 4374,4380 ---- 23. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfaggressive-function-elimination_007d-270 24. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWreal-q-constant_007d-149 25. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/SELECTED_005fREAL_005fKIND.html ! 26. https://msdn.microsoft.com/en-us/library/bb787181%28v=vs.85%29.aspx 27. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Debugging-Options.html#index-g_t_0040code_007bfno-backtrace_007d-183 28. https://gcc.gnu.org/wiki/Fortran2003Status 29. https://gcc.gnu.org/wiki/OOP *************** References *** 4334,4344 **** 36. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Named-Address-Spaces.html 37. http://nongnu.org/avr-libc/ 38. https://gcc.gnu.org/PR54461 ! 39. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/AVR-Built_002din-Functions.html 40. https://sites.google.com/site/x32abi/ 41. http://www.dwarfstd.org/ShowIssue.php?issue=100909.1 42. http://www.dwarfstd.org/ShowIssue.php?issue=100909.2 ! 43. http://www.dwarfstd.org/doc/040408.1.html 44. http://www.dwarfstd.org/ShowIssue.php?issue=110722.1 45. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.1 46. https://golang.org/doc/go1 --- 4387,4397 ---- 36. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Named-Address-Spaces.html 37. http://nongnu.org/avr-libc/ 38. https://gcc.gnu.org/PR54461 ! 39. https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/AVR-Built%5f002din-Functions.html 40. https://sites.google.com/site/x32abi/ 41. http://www.dwarfstd.org/ShowIssue.php?issue=100909.1 42. http://www.dwarfstd.org/ShowIssue.php?issue=100909.2 ! 43. http://www.dwarfstd.org/ShowIssue.php?issue=140425.1 44. http://www.dwarfstd.org/ShowIssue.php?issue=110722.1 45. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.1 46. https://golang.org/doc/go1 *************** References *** 4354,4359 **** --- 4407,4413 ---- 56. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.6/index.html + GCC 4.6 Release Series April 12, 2013 *************** References *** 4445,4450 **** --- 4499,4505 ---- 24. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.6/changes.html + GCC 4.6 Release Series Changes, New Features, and Fixes *************** New Languages and Language specific impr *** 4784,4790 **** * [12]Improved experimental support for the upcoming ISO C++ standard, C++0x, including using constexpr and nullptr. ! * Performance improvements to the [13]Debug Mode, thanks to François Dumont. * Atomic operations used for reference-counting are annotated so that they can be understood by race detectors such as Helgrind, see --- 4839,4845 ---- * [12]Improved experimental support for the upcoming ISO C++ standard, C++0x, including using constexpr and nullptr. ! * Performance improvements to the [13]Debug Mode, thanks to Franc,ois Dumont. * Atomic operations used for reference-counting are annotated so that they can be understood by race detectors such as Helgrind, see *************** New Languages and Language specific impr *** 4839,4845 **** allocated (if unallocated) or reallocated (if the shape or type parameter is different). To avoid the small performance penalty, you can use a(:) = ... instead of a = ... for arrays ! and character strings – or disable the feature using -std=f95 or -fno-realloc-lhs. + Deferred type parameter: For scalar allocatable and pointer variables the character length can be deferred. --- 4894,4900 ---- allocated (if unallocated) or reallocated (if the shape or type parameter is different). To avoid the small performance penalty, you can use a(:) = ... instead of a = ... for arrays ! and character strings - or disable the feature using -std=f95 or -fno-realloc-lhs. + Deferred type parameter: For scalar allocatable and pointer variables the character length can be deferred. *************** New Languages and Language specific impr *** 4894,4900 **** be declared in a single PROCEDURE statement; implied-shape arrays are supported for named constants (PARAMETER). The transformational, three argument versions of BESSEL_JN and ! BESSEL_YN were added – the elemental, two-argument version had been added in GCC 4.4; note that the transformational functions use a recurrence algorithm. --- 4949,4955 ---- be declared in a single PROCEDURE statement; implied-shape arrays are supported for named constants (PARAMETER). The transformational, three argument versions of BESSEL_JN and ! BESSEL_YN were added - the elemental, two-argument version had been added in GCC 4.4; note that the transformational functions use a recurrence algorithm. *************** References *** 5375,5380 **** --- 5430,5436 ---- 30. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.5/index.html + GCC 4.5 Release Series Jul 2, 2012 *************** References *** 5461,5466 **** --- 5517,5523 ---- 19. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.5/changes.html + GCC 4.5 Release Series Changes, New Features, and Fixes *************** Caveats *** 5502,5508 **** epilogue unwind info is emitted unconditionally whenever unwind info is emitted. * On x86 targets, code containing floating-point calculations may run ! significantly slower when compiled with GCC 4.5 in strict C99 conformance mode than they did with earlier GCC versions. This is due to stricter standard conformance of the compiler and can be avoided by using the option -fexcess-precision=fast; also see --- 5559,5565 ---- epilogue unwind info is emitted unconditionally whenever unwind info is emitted. * On x86 targets, code containing floating-point calculations may run ! significantly more slowly when compiled with GCC 4.5 in strict C99 conformance mode than they did with earlier GCC versions. This is due to stricter standard conformance of the compiler and can be avoided by using the option -fexcess-precision=fast; also see *************** New Languages and Language specific impr *** 5697,5703 **** defined ([13]DR 757). * Labels may now have attributes, as has been permitted for a while in C. This is only permitted when the label definition and the ! attribute specifier is followed by a semicolon—i.e., the label applies to an empty statement. The only useful attribute for a label is unused. * G++ now implements [14]DR 176. Previously G++ did not support using --- 5754,5760 ---- defined ([13]DR 757). * Labels may now have attributes, as has been permitted for a while in C. This is only permitted when the label definition and the ! attribute specifier is followed by a semicolon--i.e., the label applies to an empty statement. The only useful attribute for a label is unused. * G++ now implements [14]DR 176. Previously G++ did not support using *************** vector-size: improvement = 3: call stack *** 5779,5785 **** Fortran ! * The COMMON default padding has been changed – instead of adding the padding before a variable it is now added afterwards, which increases the compatibility with other vendors and helps to obtain the correct output in some cases. Cf. also the -falign-commons --- 5836,5842 ---- Fortran ! * The COMMON default padding has been changed - instead of adding the padding before a variable it is now added afterwards, which increases the compatibility with other vendors and helps to obtain the correct output in some cases. Cf. also the -falign-commons *************** GCC 4.5.4 *** 6108,6114 **** provided this notice is preserved. These pages are [33]maintained by the GCC team. Last modified ! 2016-05-28[34]. References --- 6165,6171 ---- provided this notice is preserved. These pages are [33]maintained by the GCC team. Last modified ! 2017-02-28[34]. References *************** References *** 6148,6153 **** --- 6205,6211 ---- 34. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.4/index.html + GCC 4.4 Release Series March 13, 2012 *************** References *** 6246,6251 **** --- 6304,6310 ---- 22. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.4/changes.html + GCC 4.4 Release Series Changes, New Features, and Fixes *************** New warning options *** 6461,6469 **** New Languages and Language specific improvements ! * Version 3.0 of the [5]OpenMP specification is now supported for the ! C, C++, and Fortran compilers. ! * New character data types, per [6]TR 19769: New character types in C, are now supported for the C compiler in -std=gnu99 mode, as __CHAR16_TYPE__ and __CHAR32_TYPE__, and for the C++ compiler in -std=c++0x and -std=gnu++0x modes, as char16_t and char32_t too. --- 6520,6528 ---- New Languages and Language specific improvements ! * Version 3.0 of the OpenMP specification is now supported for the C, ! C++, and Fortran compilers. ! * New character data types, per [5]TR 19769: New character types in C, are now supported for the C compiler in -std=gnu99 mode, as __CHAR16_TYPE__ and __CHAR32_TYPE__, and for the C++ compiler in -std=c++0x and -std=gnu++0x modes, as char16_t and char32_t too. *************** New Languages and Language specific impr *** 6492,6498 **** C++ ! * [7]Improved experimental support for the upcoming ISO C++ standard, C++0x. Including support for auto, inline namespaces, generalized initializer lists, defaulted and deleted functions, new character types, and scoped enums. --- 6551,6557 ---- C++ ! * [6]Improved experimental support for the upcoming ISO C++ standard, C++0x. Including support for auto, inline namespaces, generalized initializer lists, defaulted and deleted functions, new character types, and scoped enums. *************** New Languages and Language specific impr *** 6532,6543 **** Fortran * GNU Fortran now employs libcpp directly instead of using cc1 as an ! external preprocessor. The [8]-cpp option was added to allow manual invocation of the preprocessor without relying on filename extensions. ! * The [9]-Warray-temporaries option warns about array temporaries generated by the compiler, as an aid to optimization. ! * The [10]-fcheck-array-temporaries option has been added, printing a notification at run time, when an array temporary had to be created for an function argument. Contrary to -Warray-temporaries the warning is only printed if the array is noncontiguous. --- 6591,6602 ---- Fortran * GNU Fortran now employs libcpp directly instead of using cc1 as an ! external preprocessor. The [7]-cpp option was added to allow manual invocation of the preprocessor without relying on filename extensions. ! * The [8]-Warray-temporaries option warns about array temporaries generated by the compiler, as an aid to optimization. ! * The [9]-fcheck-array-temporaries option has been added, printing a notification at run time, when an array temporary had to be created for an function argument. Contrary to -Warray-temporaries the warning is only printed if the array is noncontiguous. *************** New Languages and Language specific impr *** 6559,6565 **** * Fortran 2003 support has been extended: + Wide characters (ISO 10646, UCS-4, kind=4) and UTF-8 I/O is now supported (except internal reads from/writes to wide ! strings). [11]-fbackslash now supports also \unnnn and \Unnnnnnnn to enter Unicode characters. + Asynchronous I/O (implemented as synchronous I/O) and the decimal=, size=, sign=, pad=, blank=, and delim= specifiers --- 6618,6624 ---- * Fortran 2003 support has been extended: + Wide characters (ISO 10646, UCS-4, kind=4) and UTF-8 I/O is now supported (except internal reads from/writes to wide ! strings). [10]-fbackslash now supports also \unnnn and \Unnnnnnnn to enter Unicode characters. + Asynchronous I/O (implemented as synchronous I/O) and the decimal=, size=, sign=, pad=, blank=, and delim= specifiers *************** Other significant improvements *** 6788,6854 **** GCC 4.4.1 ! This is the [12]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.2 ! This is the [13]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.3 ! This is the [14]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.4 ! This is the [15]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.5 ! This is the [16]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.6 ! This is the [17]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.6 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.7 ! This is the [18]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.7 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [19]GCC manuals. If that fails, the ! [20]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 [21]gcc@gcc.gnu.org. All of [22]our lists have public archives. ! Copyright (C) [23]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [24]maintained by the GCC team. Last modified ! 2016-01-30[25]. References --- 6847,6913 ---- GCC 4.4.1 ! This is the [11]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.2 ! This is the [12]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.3 ! This is the [13]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.4 ! This is the [14]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.5 ! This is the [15]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.6 ! This is the [16]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.6 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.4.7 ! This is the [17]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.4.7 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [18]GCC manuals. If that fails, the ! [19]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 [20]gcc@gcc.gnu.org. All of [21]our lists have public archives. ! Copyright (C) [22]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [23]maintained by the GCC team. Last modified ! 2016-12-28[24]. References *************** References *** 6856,6884 **** 2. http://gcc.gnu.org/gcc-4.3/changes.html#obsoleted 3. http://gcc.gnu.org/gcc-4.4/porting_to.html 4. https://gcc.gnu.org/wiki/Graphite ! 5. http://openmp.org/wp/openmp-specifications/ ! 6. http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1040.pdf ! 7. http://gcc.gnu.org/gcc-4.4/cxx0x_status.html ! 8. https://gcc.gnu.org/onlinedocs/gfortran/Preprocessing-Options.html ! 9. https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWarray-temporaries_007d-125 ! 10. https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfcheck-array-temporaries_007d-221 ! 11. https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html#index-g_t_0040code_007bbackslash_007d-34 ! 12. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.1 ! 13. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.2 ! 14. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.3 ! 15. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.4 ! 16. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.5 ! 17. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.6 ! 18. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.7 ! 19. https://gcc.gnu.org/onlinedocs/ ! 20. mailto:gcc-help@gcc.gnu.org ! 21. mailto:gcc@gcc.gnu.org ! 22. https://gcc.gnu.org/lists.html ! 23. http://www.fsf.org/ ! 24. https://gcc.gnu.org/about.html ! 25. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.3/index.html GCC 4.3 Release Series Jun 27, 2011 --- 6915,6943 ---- 2. http://gcc.gnu.org/gcc-4.3/changes.html#obsoleted 3. http://gcc.gnu.org/gcc-4.4/porting_to.html 4. https://gcc.gnu.org/wiki/Graphite ! 5. http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1040.pdf ! 6. http://gcc.gnu.org/gcc-4.4/cxx0x_status.html ! 7. https://gcc.gnu.org/onlinedocs/gfortran/Preprocessing-Options.html ! 8. https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWarray-temporaries_007d-125 ! 9. https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfcheck-array-temporaries_007d-221 ! 10. https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html#index-g_t_0040code_007bbackslash_007d-34 ! 11. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.1 ! 12. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.2 ! 13. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.3 ! 14. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.4 ! 15. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.5 ! 16. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.6 ! 17. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.7 ! 18. https://gcc.gnu.org/onlinedocs/ ! 19. mailto:gcc-help@gcc.gnu.org ! 20. mailto:gcc@gcc.gnu.org ! 21. https://gcc.gnu.org/lists.html ! 22. http://www.fsf.org/ ! 23. https://gcc.gnu.org/about.html ! 24. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.3/index.html + GCC 4.3 Release Series Jun 27, 2011 *************** References *** 6973,6978 **** --- 7032,7038 ---- 21. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.3/changes.html + GCC 4.3 Release Series Changes, New Features, and Fixes *************** New Languages and Language specific impr *** 7221,7234 **** * [13]Experimental support for the upcoming ISO C++ standard, C++0x. * Support for TR1 mathematical special functions and regular ! expressions. ([14]Implementation status of TR1) * Default what implementations give more elaborate exception strings for bad_cast, bad_typeid, bad_exception, and bad_alloc. * Header dependencies have been streamlined, reducing unnecessary includes and pre-processed bloat. * Variadic template implementations of items in and . ! * An experimental [15]parallel mode has been added. This is a parallel implementation of many C++ Standard library algorithms, like std::accumulate, std::for_each, std::transform, or std::sort, to give but four examples. These algorithms can be substituted for --- 7281,7294 ---- * [13]Experimental support for the upcoming ISO C++ standard, C++0x. * Support for TR1 mathematical special functions and regular ! expressions. * Default what implementations give more elaborate exception strings for bad_cast, bad_typeid, bad_exception, and bad_alloc. * Header dependencies have been streamlined, reducing unnecessary includes and pre-processed bloat. * Variadic template implementations of items in and . ! * An experimental [14]parallel mode has been added. This is a parallel implementation of many C++ Standard library algorithms, like std::accumulate, std::for_each, std::transform, or std::sort, to give but four examples. These algorithms can be substituted for *************** New Languages and Language specific impr *** 7259,7265 **** * Due to the fact that the GMP and MPFR libraries are required for all languages, Fortran is no longer special in this regard and is available by default. ! * The [16]-fexternal-blas option has been added, which generates calls to BLAS routines for intrinsic matrix operations such as matmul rather than using the built-in algorithms. * Support to give a backtrace (compiler flag -fbacktrace or --- 7319,7325 ---- * Due to the fact that the GMP and MPFR libraries are required for all languages, Fortran is no longer special in this regard and is available by default. ! * The [15]-fexternal-blas option has been added, which generates calls to BLAS routines for intrinsic matrix operations such as matmul rather than using the built-in algorithms. * Support to give a backtrace (compiler flag -fbacktrace or *************** New Languages and Language specific impr *** 7268,7283 **** run-time error occured. * GNU Fortran now defines __GFORTRAN__ when it runs the C preprocessor (CPP). ! * The [17]-finit-local-zero, -finit-real, -finit-integer, -finit-character, and -finit-logical options have been added, which can be used to initialize local variables. ! * The intrinsic procedures [18]GAMMA and [19]LGAMMA have been added, which calculate the Gamma function and its logarithm. Use EXTERNAL gamma if you want to use your own gamma function. * GNU Fortran now regards the backslash character as literal (as ! required by the Fortran 2003 standard); using [20]-fbackslash GNU Fortran interprets backslashes as C-style escape characters. ! * The [21]interpretation of binary, octal and hexadecimal (BOZ) literal constants has been changed. Before they were always interpreted as integer; now they are bit-wise transferred as argument of INT, REAL, DBLE and CMPLX as required by the Fortran --- 7328,7343 ---- run-time error occured. * GNU Fortran now defines __GFORTRAN__ when it runs the C preprocessor (CPP). ! * The [16]-finit-local-zero, -finit-real, -finit-integer, -finit-character, and -finit-logical options have been added, which can be used to initialize local variables. ! * The intrinsic procedures [17]GAMMA and [18]LGAMMA have been added, which calculate the Gamma function and its logarithm. Use EXTERNAL gamma if you want to use your own gamma function. * GNU Fortran now regards the backslash character as literal (as ! required by the Fortran 2003 standard); using [19]-fbackslash GNU Fortran interprets backslashes as C-style escape characters. ! * The [20]interpretation of binary, octal and hexadecimal (BOZ) literal constants has been changed. Before they were always interpreted as integer; now they are bit-wise transferred as argument of INT, REAL, DBLE and CMPLX as required by the Fortran *************** Documentation improvements *** 7647,7653 **** * Existing libstdc++ documentation has been edited and restructured into a single DocBook XML manual. The results can be viewed online ! [22]here. Other significant improvements --- 7707,7713 ---- * Existing libstdc++ documentation has been edited and restructured into a single DocBook XML manual. The results can be viewed online ! [21]here. Other significant improvements *************** Other significant improvements *** 7679,7685 **** GCC 4.3.1 ! This is the [23]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). --- 7739,7745 ---- GCC 4.3.1 ! This is the [22]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). *************** Target Specific Changes *** 7705,7757 **** GCC 4.3.2 ! This is the [24]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.3 ! This is the [25]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.4 ! This is the [26]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.5 ! This is the [27]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.6 ! This is the [28]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.6 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [29]GCC manuals. If that fails, the ! [30]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 [31]gcc@gcc.gnu.org. All of [32]our lists have public archives. ! Copyright (C) [33]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [34]maintained by the GCC team. Last modified ! 2016-01-30[35]. References --- 7765,7817 ---- GCC 4.3.2 ! This is the [23]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.2 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.3 ! This is the [24]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.4 ! This is the [25]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.5 ! This is the [26]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). GCC 4.3.6 ! This is the [27]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 4.3.6 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [28]GCC manuals. If that fails, the ! [29]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 [30]gcc@gcc.gnu.org. All of [31]our lists have public archives. ! Copyright (C) [32]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [33]maintained by the GCC team. Last modified ! 2017-02-07[34]. References *************** References *** 7768,7797 **** 11. https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html 12. http://gcc.gnu.org/gcc-4.3/cxx0x_status.html 13. http://gcc.gnu.org/gcc-4.3/cxx0x_status.html ! 14. https://gcc.gnu.org/onlinedocs/libstdc++/manual/bk01pt01ch01.html#m anual.intro.status.standard.tr1 ! 15. https://gcc.gnu.org/onlinedocs/libstdc++/manual/parallel_mode.html ! 16. https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#Code-Gen-Options ! 17. https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfinit-local-zero_007d-167 ! 18. https://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/GAMMA.html ! 19. https://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/LGAMMA.html ! 20. https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html ! 21. https://gcc.gnu.org/onlinedocs/gfortran/BOZ-literal-constants.html ! 22. https://gcc.gnu.org/onlinedocs/libstdc++/ ! 23. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.1 ! 24. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.2 ! 25. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.3 ! 26. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.4 ! 27. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.5 ! 28. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.6 ! 29. https://gcc.gnu.org/onlinedocs/ ! 30. mailto:gcc-help@gcc.gnu.org ! 31. mailto:gcc@gcc.gnu.org ! 32. https://gcc.gnu.org/lists.html ! 33. http://www.fsf.org/ ! 34. https://gcc.gnu.org/about.html ! 35. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.2/index.html GCC 4.2 Release Series May 19, 2008 --- 7828,7857 ---- 11. https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html 12. http://gcc.gnu.org/gcc-4.3/cxx0x_status.html 13. http://gcc.gnu.org/gcc-4.3/cxx0x_status.html ! 14. https://gcc.gnu.org/onlinedocs/libstdc++/manual/parallel_mode.html ! 15. https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#Code-Gen-Options ! 16. https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfinit-local-zero_007d-167 ! 17. https://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/GAMMA.html ! 18. https://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/LGAMMA.html ! 19. https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html ! 20. https://gcc.gnu.org/onlinedocs/gfortran/BOZ-literal-constants.html ! 21. https://gcc.gnu.org/onlinedocs/libstdc++/ ! 22. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.1 ! 23. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.2 ! 24. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.3 ! 25. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.4 ! 26. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.5 ! 27. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.6 ! 28. https://gcc.gnu.org/onlinedocs/ ! 29. mailto:gcc-help@gcc.gnu.org ! 30. mailto:gcc@gcc.gnu.org ! 31. https://gcc.gnu.org/lists.html ! 32. http://www.fsf.org/ ! 33. https://gcc.gnu.org/about.html ! 34. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.2/index.html + GCC 4.2 Release Series May 19, 2008 *************** References *** 7878,7883 **** --- 7938,7944 ---- 19. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.2/changes.html + GCC 4.2 Release Series Changes, New Features, and Fixes *************** New Languages and Language specific impr *** 8003,8009 **** * Added support for TR1 , , and C compatibility headers. In addition, a lock-free version of shared_ptr was contributed as part of Phillip Jordan's Google Summer of Code ! project on lock-free containers. ([3]Implementation status of TR1) * In association with the Summer of Code work on lock-free containers, the interface for atomic builtins was adjusted, creating simpler alternatives for non-threaded code paths. Also, --- 8064,8070 ---- * Added support for TR1 , , and C compatibility headers. In addition, a lock-free version of shared_ptr was contributed as part of Phillip Jordan's Google Summer of Code ! project on lock-free containers. * In association with the Summer of Code work on lock-free containers, the interface for atomic builtins was adjusted, creating simpler alternatives for non-threaded code paths. Also, *************** New Languages and Language specific impr *** 8021,8027 **** (basic_tree, tree, trie), lists (list_update), and both collision-chaining and probing hash-based containers (basic_hash_table, cc_hash_table, gp_hash_table). More details per ! the [4]documentation. * The implementation of the debug mode was modified, whereby the debug namespaces were nested inside of namespace std and namespace __gnu_cxx in order to resolve some long standing corner cases --- 8082,8088 ---- (basic_tree, tree, trie), lists (list_update), and both collision-chaining and probing hash-based containers (basic_hash_table, cc_hash_table, gp_hash_table). More details per ! the [3]documentation. * The implementation of the debug mode was modified, whereby the debug namespaces were nested inside of namespace std and namespace __gnu_cxx in order to resolve some long standing corner cases *************** New Languages and Language specific impr *** 8054,8060 **** gfortran used 8-byte record markers by default (on most systems). In order to change the length of the record markers, e.g. to read unformatted files created by older gfortran versions, the ! [5]-frecord-marker=8 option can be used. Java (GCJ) --- 8115,8121 ---- gfortran used 8-byte record markers by default (on most systems). In order to change the length of the record markers, e.g. to read unformatted files created by older gfortran versions, the ! [4]-frecord-marker=8 option can be used. Java (GCJ) *************** New Languages and Language specific impr *** 8065,8071 **** memory than if the shared version of libgcj were used. However caution should be used as it can also cause essential parts of the library to be omitted. Some of these issues are discussed in: ! [6]https://gcc.gnu.org/wiki/Statically_linking_libgcj * fastjar is no longer bundled with GCC. To build libgcj, you will need either InfoZIP (both zip and unzip) or an external jar program. In the former case, the GCC build will install a jar shell --- 8126,8132 ---- memory than if the shared version of libgcj were used. However caution should be used as it can also cause essential parts of the library to be omitted. Some of these issues are discussed in: ! [5]https://gcc.gnu.org/wiki/Statically_linking_libgcj * fastjar is no longer bundled with GCC. To build libgcj, you will need either InfoZIP (both zip and unzip) or an external jar program. In the former case, the GCC build will install a jar shell *************** Other significant improvements *** 8171,8206 **** For questions related to the use of GCC, please consult these web ! pages and the [7]GCC manuals. If that fails, the ! [8]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 [9]gcc@gcc.gnu.org. All of [10]our lists have public ! archives. ! Copyright (C) [11]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [12]maintained by the GCC team. Last modified ! 2016-01-30[13]. References 1. http://gcc.gnu.org/projects/gomp/ 2. https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html ! 3. https://gcc.gnu.org/onlinedocs/libstdc++/manual/bk01pt01ch01.html#manual.intro.status.standard.tr1 ! 4. https://gcc.gnu.org/onlinedocs/libstdc++/ext/pb_ds/index.html ! 5. https://gcc.gnu.org/onlinedocs/gfortran/Runtime-Options.html ! 6. https://gcc.gnu.org/wiki/Statically_linking_libgcj ! 7. https://gcc.gnu.org/onlinedocs/ ! 8. mailto:gcc-help@gcc.gnu.org ! 9. mailto:gcc@gcc.gnu.org ! 10. https://gcc.gnu.org/lists.html ! 11. http://www.fsf.org/ ! 12. https://gcc.gnu.org/about.html ! 13. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.1/index.html GCC 4.1 Release Series February 13, 2007 --- 8232,8266 ---- For questions related to the use of GCC, please consult these web ! pages and the [6]GCC manuals. If that fails, the ! [7]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 [8]gcc@gcc.gnu.org. All of [9]our lists have public archives. ! Copyright (C) [10]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [11]maintained by the GCC team. Last modified ! 2017-02-07[12]. References 1. http://gcc.gnu.org/projects/gomp/ 2. https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html ! 3. https://gcc.gnu.org/onlinedocs/libstdc++/ext/pb_ds/index.html ! 4. https://gcc.gnu.org/onlinedocs/gfortran/Runtime-Options.html ! 5. https://gcc.gnu.org/wiki/Statically_linking_libgcj ! 6. https://gcc.gnu.org/onlinedocs/ ! 7. mailto:gcc-help@gcc.gnu.org ! 8. mailto:gcc@gcc.gnu.org ! 9. https://gcc.gnu.org/lists.html ! 10. http://www.fsf.org/ ! 11. https://gcc.gnu.org/about.html ! 12. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.1/index.html + GCC 4.1 Release Series February 13, 2007 *************** References *** 8279,8284 **** --- 8339,8345 ---- 17. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.1/changes.html + GCC 4.1 Release Series Changes, New Features, and Fixes *************** References *** 8838,8843 **** --- 8899,8905 ---- 13. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.0/index.html + GCC 4.0 Release Series January 31, 2007 *************** References *** 8924,8929 **** --- 8986,8992 ---- 19. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-4.0/changes.html + GCC 4.0 Release Series Changes, New Features, and Fixes *************** Obsolete Systems *** 9333,9339 **** declared obsolete: * Intel i860 * Ubicom IP2022 ! * National Semiconductor NS32K * Texas Instruments TMS320C[34]x Also, those for some individual systems have been obsoleted: --- 9396,9402 ---- declared obsolete: * Intel i860 * Ubicom IP2022 ! * National Semiconductor NS32K (ns32k) * Texas Instruments TMS320C[34]x Also, those for some individual systems have been obsoleted: *************** GCC 4.0.4 *** 9425,9431 **** provided this notice is preserved. These pages are [21]maintained by the GCC team. Last modified ! 2016-05-27[22]. References --- 9488,9494 ---- provided this notice is preserved. These pages are [21]maintained by the GCC team. Last modified ! 2017-03-29[22]. References *************** References *** 9436,9442 **** 5. http://gcc.gnu.org/news/sms.html 6. https://www.akkadia.org/drepper/dsohowto.pdf 7. http://gcc.gnu.org/gcc-4.0/changes.html#visibility ! 8. http://mentorembedded.github.io/cxx-abi/ 9. http://gcc.gnu.org/fortran/ 10. https://gcc.gnu.org/install/ 11. https://gcc.gnu.org/wiki/Visibility --- 9499,9505 ---- 5. http://gcc.gnu.org/news/sms.html 6. https://www.akkadia.org/drepper/dsohowto.pdf 7. http://gcc.gnu.org/gcc-4.0/changes.html#visibility ! 8. https://itanium-cxx-abi.github.io/cxx-abi/ 9. http://gcc.gnu.org/fortran/ 10. https://gcc.gnu.org/install/ 11. https://gcc.gnu.org/wiki/Visibility *************** References *** 9453,9458 **** --- 9516,9522 ---- 22. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.4/index.html + GCC 3.4 Release Series May 26, 2006 *************** References *** 9554,9559 **** --- 9618,9624 ---- 23. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.4/changes.html + GCC 3.4 Release Series Changes, New Features, and Fixes *************** New Targets and Target Specific Improvem *** 10160,10168 **** __builtin_alpha_zap to allow utilizing the more obscure instructions of the CPU. * Parameter passing of complex arguments has changed to match the ! [20]ABI. This change is incompatible with previous GCC versions, ! but does fix compatibility with the Tru64 compiler and several ! corner cases where GCC was incompatible with itself. ARM --- 10225,10233 ---- __builtin_alpha_zap to allow utilizing the more obscure instructions of the CPU. * Parameter passing of complex arguments has changed to match the ! ABI. This change is incompatible with previous GCC versions, but ! does fix compatibility with the Tru64 compiler and several corner ! cases where GCC was incompatible with itself. ARM *************** New Targets and Target Specific Improvem *** 10177,10184 **** * A new ARM target has been added: arm-wince-pe. This is similar to the arm-pe target, but it defaults to using the APCS32 ABI. * The existing ARM pipeline description has been converted to the use ! the [21]DFA processor pipeline model. There is not much change in ! code performance, but the description is now [22]easier to understand. * Support for the Cirrus EP9312 Maverick floating point co-processor added. Enabled at run time with the -mcpu=ep9312 command line --- 10242,10249 ---- * A new ARM target has been added: arm-wince-pe. This is similar to the arm-pe target, but it defaults to using the APCS32 ABI. * The existing ARM pipeline description has been converted to the use ! the [20]DFA processor pipeline model. There is not much change in ! code performance, but the description is now [21]easier to understand. * Support for the Cirrus EP9312 Maverick floating point co-processor added. Enabled at run time with the -mcpu=ep9312 command line *************** New Targets and Target Specific Improvem *** 10224,10230 **** generation of code tuned for Itanium 2 (option -mtune=itanium2) is enabled by default now. To generate code tuned for Itanium 1 the option -mtune=itanium1 should be used. ! * [23]DFA processor pipeline descriptions for the IA-64 processors have been added. This resulted in about 3% improvement on the SPECInt2000 benchmark for Itanium 2. * Instruction bundling for the IA-64 processors has been rewritten --- 10289,10295 ---- generation of code tuned for Itanium 2 (option -mtune=itanium2) is enabled by default now. To generate code tuned for Itanium 1 the option -mtune=itanium1 should be used. ! * [22]DFA processor pipeline descriptions for the IA-64 processors have been added. This resulted in about 3% improvement on the SPECInt2000 benchmark for Itanium 2. * Instruction bundling for the IA-64 processors has been rewritten *************** New Targets and Target Specific Improvem *** 10288,10294 **** General ! * Several [24]ABI bugs have been fixed. Unfortunately, these changes will break binary compatibility with earlier releases. * GCC can now use explicit relocation operators when generating -mabicalls code. This behavior is controlled by -mexplicit-relocs --- 10353,10359 ---- General ! * Several [23]ABI bugs have been fixed. Unfortunately, these changes will break binary compatibility with earlier releases. * GCC can now use explicit relocation operators when generating -mabicalls code. This behavior is controlled by -mexplicit-relocs *************** New Targets and Target Specific Improvem *** 10313,10319 **** PowerPC * GCC 3.4 releases have a number of fixes for PowerPC and PowerPC64 ! [25]ABI incompatibilities regarding the way parameters are passed during functions calls. These changes may result in incompatibility between code compiled with GCC 3.3 and GCC 3.4. --- 10378,10384 ---- PowerPC * GCC 3.4 releases have a number of fixes for PowerPC and PowerPC64 ! [24]ABI incompatibilities regarding the way parameters are passed during functions calls. These changes may result in incompatibility between code compiled with GCC 3.3 and GCC 3.4. *************** New Targets and Target Specific Improvem *** 10395,10401 **** * The option -mflat is deprecated. * Support for large (> 2GB) frames has been added to the 64-bit port. ! * Several [26]ABI bugs have been fixed. Unfortunately, these changes will break binary compatibility with earlier releases. * The default debugging format has been switched from STABS to DWARF-2 for 32-bit code on Solaris 7 and later. DWARF-2 is already --- 10460,10466 ---- * The option -mflat is deprecated. * Support for large (> 2GB) frames has been added to the 64-bit port. ! * Several [25]ABI bugs have been fixed. Unfortunately, these changes will break binary compatibility with earlier releases. * The default debugging format has been switched from STABS to DWARF-2 for 32-bit code on Solaris 7 and later. DWARF-2 is already *************** GCC 3.4.0 *** 10508,10514 **** Bug Fixes A vast number of bugs have been fixed in 3.4.0, too many to publish a ! complete list here. [27]Follow this link to query the Bugzilla database for the list of over 900 bugs fixed in 3.4.0. This is the list of all bugs marked as resolved and fixed in 3.4.0 that are not flagged as 3.4 regressions. --- 10573,10579 ---- Bug Fixes A vast number of bugs have been fixed in 3.4.0, too many to publish a ! complete list here. [26]Follow this link to query the Bugzilla database for the list of over 900 bugs fixed in 3.4.0. This is the list of all bugs marked as resolved and fixed in 3.4.0 that are not flagged as 3.4 regressions. *************** GCC 3.4.1 *** 10525,10788 **** Bootstrap failures ! * [28]10129 Ada bootstrap fails on PPC-Darwin - invalid assembler emitted - PIC related ! * [29]14576 [ARM] ICE in libiberty when building gcc-3.4 for arm-elf ! * [30]14760 A bug in configure.in prevents using both --program-suffix and --program-prefix ! * [31]14671 [hppa64] bootstrap fails: ICE in save_call_clobbered_regs, in caller_save.c ! * [32]15093 [alpha][Java] make bootstrap fails to configure libffi on Alpha ! * [33]15178 Solaris 9/x86 fails linking after stage 3 Multi-platform internal compiler errors (ICEs) ! * [34]12753 (preprocessor) Memory corruption in preprocessor on bad input ! * [35]13985 ICE in gcc.c-torture/compile/930621-1.c ! * [36]14810 (c++) tree check failures with invalid code involving templates ! * [37]14883 (c++) ICE on invalid code, in cp_parser_lookup_name, in cp/parser.c ! * [38]15044 (c++) ICE on syntax error, template header ! * [39]15057 (c++) Compiling of conditional value throw constructs cause a segmentation violation ! * [40]15064 (c++) typeid of template parameter gives ICE ! * [41]15142 (c++) ICE when passing a string where a char* is expected in a throw statement ! * [42]15159 ICE in rtl_verify_flow_info_1 ! * [43]15165 (c++) ICE in instantiate_template ! * [44]15193 Unary minus using pointer to V4SF vector causes -fforce-mem to exhaust all memory ! * [45]15209 (c++) Runs out of memory with packed structs ! * [46]15227 (c++) Trouble with invalid function definition ! * [47]15285 (c++) instantiate_type ICE when forming pointer to template function ! * [48]15299 (c++) ICE in resolve_overloaded_unification ! * [49]15329 (c++) ICE on constructor of member template ! * [50]15550 ICE in extract_insn, in recog.c ! * [51]15554 (c++) ICE in tsubst_copy, in cp/pt.c ! * [52]15640 (c++) ICE on invalid code in arg_assoc, in cp/name-lookup.c ! * [53]15666 [unit-at-a-time] Gcc abort on valid code ! * [54]15696 (c++) ICE with bad pointer-to-member code ! * [55]15701 (c++) ICE with friends and template template parameter ! * [56]15761 ICE in do_SUBST, in combine.c ! * [57]15829 (c++) ICE on Botan-1.3.13 due to -funroll-loops Ada ! * [58]14538 All RTEMS targets broken for gnat C front end ! * [59]12391 missing warning about assigning to an incomplete type ! * [60]14649 atan(1.0) should not be a constant expression ! * [61]15004 [unit-at-a-time] no warning for unused paramater in static function ! * [62]15749 --pedantic-errors behaves differently from --pedantic with C-compiler on GNU/Linux C++ compiler and library ! * [63]10646 non-const reference is incorrectly matched in a "const T" partial specialization ! * [64]12077 wcin.rdbuf()->in_avail() return value too high ! * [65]13598 enc_filebuf doesn't work ! * [66]14211 const_cast returns lvalue but should be rvalue ! * [67]14220 num_put::do_put() undesired float/double behavior ! * [68]14245 problem with user-defined allocators in std::basic_string ! * [69]14340 libstdc++ Debug mode: failure to convert iterator to const_iterator ! * [70]14600 __gnu_cxx::stdio_sync_filebuf should expose internal FILE* ! * [71]14668 no warning anymore for reevaluation of declaration ! * [72]14775 LFS (large file support) tests missing ! * [73]14821 Duplicate namespace alias declaration should not conflict ! * [74]14930 Friend declaration ignored ! * [75]14932 cannot use offsetof to get offsets of array elements in g++ 3.4.0 ! * [76]14950 [non unit-at-a-time] always_inline does not mix with templates and -O0 ! * [77]14962 g++ ignores #pragma redefine_extname ! * [78]14975 Segfault on low-level write error during imbue ! * [79]15002 Linewise stream input is unusably slow (std::string slow) ! * [80]15025 compiler accepts redeclaration of template as non-template ! * [81]15046 [arm] Math functions misdetected by cross configuration ! * [82]15069 a bit test on a variable of enum type is miscompiled ! * [83]15074 g++ -lsupc++ still links against libstdc++ ! * [84]15083 spurious "statement has no effect" warning ! * [85]15096 parse error with templates and pointer to const member ! * [86]15287 combination of operator[] and operator .* fails in templates ! * [87]15317 __attribute__ unused in first parameter of constructor gives error ! * [88]15337 sizeof on incomplete type diagnostic ! * [89]15361 bitset<>::_Find_next fails ! * [90]15412 _GLIBCXX_ symbols symbols defined and used in different namespaces ! * [91]15427 valid code results in incomplete type error ! * [92]15471 Incorrect member pointer offsets in anonymous structs/unions ! * [93]15503 nested template problem ! * [94]15507 compiler hangs while laying out union ! * [95]15542 operator & and template definitions ! * [96]15565 SLES9: leading + sign for unsigned int with showpos ! * [97]15625 friend defined inside a template fails to find static function ! * [98]15629 Function templates, overloads, and friend name injection ! * [99]15742 'noreturn' attribute ignored in method of template functions. ! * [100]15775 Allocator::pointer consistently ignored ! * [101]15821 Duplicate namespace alias within namespace rejected ! * [102]15862 'enum yn' fails (confict with undeclared builtin) ! * [103]15875 rejects pointer to member in template ! * [104]15877 valid code using templates and anonymous enums is rejected ! * [105]15947 Puzzling error message for wrong destructor declaration in template class ! * [106]16020 cannot copy __gnu_debug::bitset ! * [107]16154 input iterator concept too restrictive ! * [108]16174 deducing top-level consts Java ! * [109]14315 Java compiler is not parallel make safe Fortran ! * [110]15151 [g77] incorrect logical i/o in 64-bit mode Objective-C ! * [111]7993 private variables cannot be shadowed in subclasses Optimization bugs ! * [112]15228 useless copies of floating point operands ! * [113]15345 [non-unit-at-a-time] unreferenced nested inline functions not optimized away ! * [114]15945 Incorrect floating point optimization ! * [115]15526 ftrapv aborts on 0 * (-1) ! * [116]14690 Miscompiled POOMA tests ! * [117]15112 GCC generates code to write to unchanging memory Preprocessor ! * [118]15067 Minor glitch in the source of cpp Main driver program bugs ! * [119]1963 collect2 interprets -oldstyle_liblookup as -o ldstyle_liblookup x86-specific (Intel/AMD) ! * [120]15717 Error: can't resolve `L0' {*ABS* section} - `xx' {*UND* section} HPPA-specific ! * [121]14782 GCC produces an unaligned data access at -O2 ! * [122]14828 FAIL: gcc.c-torture/execute/20030408-1.c execution, -O2 ! * [123]15202 ICE in reload_cse_simplify_operands, in postreload.c IA64-specific ! * [124]14610 __float80 constants incorrectly emitted ! * [125]14813 init_array sections are initialized in the wrong order ! * [126]14857 GCC segfault on duplicated asm statement ! * [127]15598 Gcc 3.4 ICE on valid code ! * [128]15653 Gcc 3.4 ICE on valid code MIPS-specific ! * [129]15189 wrong filling of delay slot with -march=mips1 -G0 -mno-split-addresses -mno-explicit-relocs ! * [130]15331 Assembler error building gnatlib on IRIX 6.5 with GNU as 2.14.91 ! * [131]16144 Bogus reference to __divdf3 when -O1 ! * [132]16176 Miscompilation of unaligned data in MIPS backend PowerPC-specific ! * [133]11591 ICE in gcc.dg/altivec-5.c ! * [134]12028 powerpc-eabispe produces bad sCOND operation ! * [135]14478 rs6000 geu/ltu patterns generate incorrect code ! * [136]14567 long double and va_arg complex args ! * [137]14715 Altivec stack layout may overlap gpr save with stack temps ! * [138]14902 (libstdc++) Stream checking functions fail when -pthread option is used. ! * [139]14924 Compiler ICE on valid code ! * [140]14960 -maltivec affects vector return with -mabi=no-altivec ! * [141]15106 vector varargs failure passing from altivec to non-altivec code for -m32 ! * [142]16026 ICE in function.c:4804, assign_parms, when -mpowerpc64 & half-word operation ! * [143]15191 -maltivec -mabi=no-altivec results in mis-aligned lvx and stvx ! * [144]15662 Segmentation fault when an exception is thrown - even if try and catch are specified s390-specific ! * [145]15054 Bad code due to overlapping stack temporaries SPARC-specific ! * [146]15783 ICE with union assignment in 64-bit mode ! * [147]15626 GCC 3.4 emits "ld: warning: relocation error: R_SPARC_UA32" x86-64-specific ! * [148]14326 boehm-gc hardcodes to 3DNow! prefetch for x86_64 ! * [149]14723 Backported -march=nocona from mainline ! * [150]15290 __float128 failed to pass to function properly Cygwin/Mingw32-specific ! * [151]15250 Option -mms-bitfields support on GCC 3.4 is not conformant to MS layout ! * [152]15551 -mtune=pentium4 -O2 with sjlj EH breaks stack probe worker on windows32 targets Bugs specific to embedded processors ! * [153]8309 [m68k] -m5200 produces erroneous SImode set of short varaible on stack ! * [154]13250 [SH] Gcc code for rotation clobbers the register, but gcc continues to use the register as if it was not clobbered ! * [155]13803 [coldfire] movqi operand constraints too restrictivefor TARGET_COLDFIRE ! * [156]14093 [SH] ICE for code when using -mhitachi option in SH ! * [157]14457 [m6811hc] ICE with simple c++ source ! * [158]14542 [m6811hc] ICE on simple source ! * [159]15100 [SH] cc1plus got hang-up on libstdc++-v3/testsuite/abi_check.cc ! * [160]15296 [CRIS] Delayed branch scheduling causing invalid code on cris-* ! * [161]15396 [SH] ICE with -O2 -fPIC ! * [162]15782 [coldfire] m68k_output_mi_thunk emits wrong code for ColdFire Testsuite problems (compiler not affected) ! * [163]11610 libstdc++ testcases 27_io/* don't work properly remotely ! * [164]15488 (libstdc++) possibly insufficient file permissions for executing test suite ! * [165]15489 (libstdc++) testsuite_files determined incorrectly Documentation bugs ! * [166]13928 (libstdc++) no whatis info in some man pages generated by doxygen ! * [167]14150 Ada documentation out of date ! * [168]14949 (c++) Need to document method visibility changes ! * [169]15123 libstdc++-doc: Allocators.3 manpage is empty __________________________________________________________________ GCC 3.4.2 --- 10590,10853 ---- Bootstrap failures ! * [27]10129 Ada bootstrap fails on PPC-Darwin - invalid assembler emitted - PIC related ! * [28]14576 [ARM] ICE in libiberty when building gcc-3.4 for arm-elf ! * [29]14760 A bug in configure.in prevents using both --program-suffix and --program-prefix ! * [30]14671 [hppa64] bootstrap fails: ICE in save_call_clobbered_regs, in caller_save.c ! * [31]15093 [alpha][Java] make bootstrap fails to configure libffi on Alpha ! * [32]15178 Solaris 9/x86 fails linking after stage 3 Multi-platform internal compiler errors (ICEs) ! * [33]12753 (preprocessor) Memory corruption in preprocessor on bad input ! * [34]13985 ICE in gcc.c-torture/compile/930621-1.c ! * [35]14810 (c++) tree check failures with invalid code involving templates ! * [36]14883 (c++) ICE on invalid code, in cp_parser_lookup_name, in cp/parser.c ! * [37]15044 (c++) ICE on syntax error, template header ! * [38]15057 (c++) Compiling of conditional value throw constructs cause a segmentation violation ! * [39]15064 (c++) typeid of template parameter gives ICE ! * [40]15142 (c++) ICE when passing a string where a char* is expected in a throw statement ! * [41]15159 ICE in rtl_verify_flow_info_1 ! * [42]15165 (c++) ICE in instantiate_template ! * [43]15193 Unary minus using pointer to V4SF vector causes -fforce-mem to exhaust all memory ! * [44]15209 (c++) Runs out of memory with packed structs ! * [45]15227 (c++) Trouble with invalid function definition ! * [46]15285 (c++) instantiate_type ICE when forming pointer to template function ! * [47]15299 (c++) ICE in resolve_overloaded_unification ! * [48]15329 (c++) ICE on constructor of member template ! * [49]15550 ICE in extract_insn, in recog.c ! * [50]15554 (c++) ICE in tsubst_copy, in cp/pt.c ! * [51]15640 (c++) ICE on invalid code in arg_assoc, in cp/name-lookup.c ! * [52]15666 [unit-at-a-time] Gcc abort on valid code ! * [53]15696 (c++) ICE with bad pointer-to-member code ! * [54]15701 (c++) ICE with friends and template template parameter ! * [55]15761 ICE in do_SUBST, in combine.c ! * [56]15829 (c++) ICE on Botan-1.3.13 due to -funroll-loops Ada ! * [57]14538 All RTEMS targets broken for gnat C front end ! * [58]12391 missing warning about assigning to an incomplete type ! * [59]14649 atan(1.0) should not be a constant expression ! * [60]15004 [unit-at-a-time] no warning for unused paramater in static function ! * [61]15749 --pedantic-errors behaves differently from --pedantic with C-compiler on GNU/Linux C++ compiler and library ! * [62]10646 non-const reference is incorrectly matched in a "const T" partial specialization ! * [63]12077 wcin.rdbuf()->in_avail() return value too high ! * [64]13598 enc_filebuf doesn't work ! * [65]14211 const_cast returns lvalue but should be rvalue ! * [66]14220 num_put::do_put() undesired float/double behavior ! * [67]14245 problem with user-defined allocators in std::basic_string ! * [68]14340 libstdc++ Debug mode: failure to convert iterator to const_iterator ! * [69]14600 __gnu_cxx::stdio_sync_filebuf should expose internal FILE* ! * [70]14668 no warning anymore for reevaluation of declaration ! * [71]14775 LFS (large file support) tests missing ! * [72]14821 Duplicate namespace alias declaration should not conflict ! * [73]14930 Friend declaration ignored ! * [74]14932 cannot use offsetof to get offsets of array elements in g++ 3.4.0 ! * [75]14950 [non unit-at-a-time] always_inline does not mix with templates and -O0 ! * [76]14962 g++ ignores #pragma redefine_extname ! * [77]14975 Segfault on low-level write error during imbue ! * [78]15002 Linewise stream input is unusably slow (std::string slow) ! * [79]15025 compiler accepts redeclaration of template as non-template ! * [80]15046 [arm] Math functions misdetected by cross configuration ! * [81]15069 a bit test on a variable of enum type is miscompiled ! * [82]15074 g++ -lsupc++ still links against libstdc++ ! * [83]15083 spurious "statement has no effect" warning ! * [84]15096 parse error with templates and pointer to const member ! * [85]15287 combination of operator[] and operator .* fails in templates ! * [86]15317 __attribute__ unused in first parameter of constructor gives error ! * [87]15337 sizeof on incomplete type diagnostic ! * [88]15361 bitset<>::_Find_next fails ! * [89]15412 _GLIBCXX_ symbols symbols defined and used in different namespaces ! * [90]15427 valid code results in incomplete type error ! * [91]15471 Incorrect member pointer offsets in anonymous structs/unions ! * [92]15503 nested template problem ! * [93]15507 compiler hangs while laying out union ! * [94]15542 operator & and template definitions ! * [95]15565 SLES9: leading + sign for unsigned int with showpos ! * [96]15625 friend defined inside a template fails to find static function ! * [97]15629 Function templates, overloads, and friend name injection ! * [98]15742 'noreturn' attribute ignored in method of template functions. ! * [99]15775 Allocator::pointer consistently ignored ! * [100]15821 Duplicate namespace alias within namespace rejected ! * [101]15862 'enum yn' fails (confict with undeclared builtin) ! * [102]15875 rejects pointer to member in template ! * [103]15877 valid code using templates and anonymous enums is rejected ! * [104]15947 Puzzling error message for wrong destructor declaration in template class ! * [105]16020 cannot copy __gnu_debug::bitset ! * [106]16154 input iterator concept too restrictive ! * [107]16174 deducing top-level consts Java ! * [108]14315 Java compiler is not parallel make safe Fortran ! * [109]15151 [g77] incorrect logical i/o in 64-bit mode Objective-C ! * [110]7993 private variables cannot be shadowed in subclasses Optimization bugs ! * [111]15228 useless copies of floating point operands ! * [112]15345 [non-unit-at-a-time] unreferenced nested inline functions not optimized away ! * [113]15945 Incorrect floating point optimization ! * [114]15526 ftrapv aborts on 0 * (-1) ! * [115]14690 Miscompiled POOMA tests ! * [116]15112 GCC generates code to write to unchanging memory Preprocessor ! * [117]15067 Minor glitch in the source of cpp Main driver program bugs ! * [118]1963 collect2 interprets -oldstyle_liblookup as -o ldstyle_liblookup x86-specific (Intel/AMD) ! * [119]15717 Error: can't resolve `L0' {*ABS* section} - `xx' {*UND* section} HPPA-specific ! * [120]14782 GCC produces an unaligned data access at -O2 ! * [121]14828 FAIL: gcc.c-torture/execute/20030408-1.c execution, -O2 ! * [122]15202 ICE in reload_cse_simplify_operands, in postreload.c IA64-specific ! * [123]14610 __float80 constants incorrectly emitted ! * [124]14813 init_array sections are initialized in the wrong order ! * [125]14857 GCC segfault on duplicated asm statement ! * [126]15598 Gcc 3.4 ICE on valid code ! * [127]15653 Gcc 3.4 ICE on valid code MIPS-specific ! * [128]15189 wrong filling of delay slot with -march=mips1 -G0 -mno-split-addresses -mno-explicit-relocs ! * [129]15331 Assembler error building gnatlib on IRIX 6.5 with GNU as 2.14.91 ! * [130]16144 Bogus reference to __divdf3 when -O1 ! * [131]16176 Miscompilation of unaligned data in MIPS backend PowerPC-specific ! * [132]11591 ICE in gcc.dg/altivec-5.c ! * [133]12028 powerpc-eabispe produces bad sCOND operation ! * [134]14478 rs6000 geu/ltu patterns generate incorrect code ! * [135]14567 long double and va_arg complex args ! * [136]14715 Altivec stack layout may overlap gpr save with stack temps ! * [137]14902 (libstdc++) Stream checking functions fail when -pthread option is used. ! * [138]14924 Compiler ICE on valid code ! * [139]14960 -maltivec affects vector return with -mabi=no-altivec ! * [140]15106 vector varargs failure passing from altivec to non-altivec code for -m32 ! * [141]16026 ICE in function.c:4804, assign_parms, when -mpowerpc64 & half-word operation ! * [142]15191 -maltivec -mabi=no-altivec results in mis-aligned lvx and stvx ! * [143]15662 Segmentation fault when an exception is thrown - even if try and catch are specified s390-specific ! * [144]15054 Bad code due to overlapping stack temporaries SPARC-specific ! * [145]15783 ICE with union assignment in 64-bit mode ! * [146]15626 GCC 3.4 emits "ld: warning: relocation error: R_SPARC_UA32" x86-64-specific ! * [147]14326 boehm-gc hardcodes to 3DNow! prefetch for x86_64 ! * [148]14723 Backported -march=nocona from mainline ! * [149]15290 __float128 failed to pass to function properly Cygwin/Mingw32-specific ! * [150]15250 Option -mms-bitfields support on GCC 3.4 is not conformant to MS layout ! * [151]15551 -mtune=pentium4 -O2 with sjlj EH breaks stack probe worker on windows32 targets Bugs specific to embedded processors ! * [152]8309 [m68k] -m5200 produces erroneous SImode set of short varaible on stack ! * [153]13250 [SH] Gcc code for rotation clobbers the register, but gcc continues to use the register as if it was not clobbered ! * [154]13803 [coldfire] movqi operand constraints too restrictivefor TARGET_COLDFIRE ! * [155]14093 [SH] ICE for code when using -mhitachi option in SH ! * [156]14457 [m6811hc] ICE with simple c++ source ! * [157]14542 [m6811hc] ICE on simple source ! * [158]15100 [SH] cc1plus got hang-up on libstdc++-v3/testsuite/abi_check.cc ! * [159]15296 [CRIS] Delayed branch scheduling causing invalid code on cris-* ! * [160]15396 [SH] ICE with -O2 -fPIC ! * [161]15782 [coldfire] m68k_output_mi_thunk emits wrong code for ColdFire Testsuite problems (compiler not affected) ! * [162]11610 libstdc++ testcases 27_io/* don't work properly remotely ! * [163]15488 (libstdc++) possibly insufficient file permissions for executing test suite ! * [164]15489 (libstdc++) testsuite_files determined incorrectly Documentation bugs ! * [165]13928 (libstdc++) no whatis info in some man pages generated by doxygen ! * [166]14150 Ada documentation out of date ! * [167]14949 (c++) Need to document method visibility changes ! * [168]15123 libstdc++-doc: Allocators.3 manpage is empty __________________________________________________________________ GCC 3.4.2 *************** GCC 3.4.2 *** 10796,11111 **** Bootstrap failures and issues ! * [170]16469 [mips-sgi-irix5.3] bootstrap fails in libstdc++-v3/testsuite ! * [171]16344 [hppa-linux-gnu] libstdc++'s PCH built by profiledbootstrap does not work with the built compiler ! * [172]16842 [Solaris/x86] mkheaders can not find mkheaders.conf Multi-platform internal compiler errors (ICEs) ! * [173]12608 (c++) ICE: expected class 't', have 'x' (error_mark) in cp_parser_class_specifier, in cp/parser.c ! * [174]14492 ICE in loc_descriptor_from_tree, in dwarf2out.c ! * [175]15461 (c++) ICE due to NRV and inlining ! * [176]15890 (c++) ICE in c_expand_expr, in c-common.c ! * [177]16180 ICE: segmentation fault in RTL optimization ! * [178]16224 (c++) ICE in write_unscoped_name (template/namespace) ! * [179]16408 ICE: in delete_insn, in cfgrtl.c ! * [180]16529 (c++) ICE for: namespace-alias shall not be declared as the name of any other entity ! * [181]16698 (c++) ICE with exceptions and declaration of __cxa_throw ! * [182]16706 (c++) ICE in finish_member_declaration, in cp/semantics.c ! * [183]16810 (c++) Legal C++ program with cast gives ICE in build_ptrmemfunc ! * [184]16851 (c++) ICE when throwing a comma expression ! * [185]16870 (c++) Boost.Spirit causes ICE in tsubst, in cp/pt.c ! * [186]16904 (c++) ICE in finish_class_member_access_expr, in cp/typeck.c ! * [187]16905 (c++) ICE (segfault) with exceptions ! * [188]16964 (c++) ICE in cp_parser_class_specifier due to redefinition ! * [189]17068 (c++) ICE: tree check: expected class 'd', have 'x' (identifier_node) in dependent_template_p, in cp/pt.c Preprocessor bugs ! * [190]16366 Preprocessor option -remap causes memory corruption Optimization ! * [191]15345 unreferenced nested inline functions not optimized away ! * [192]16590 Incorrect execution when compiling with -O2 ! * [193]16693 Bitwise AND is lost when used within a cast to an enum of the same precision ! * [194]17078 Jump into if(0) substatement fails Problems in generated debug information ! * [195]13956 incorrect stabs for nested local variables C front end bugs ! * [196]16684 GCC should not warn about redundant redeclarations of built-ins C++ compiler and library ! * [197]12658 Thread safety problems in locale::global() and locale::locale() ! * [198]13092 g++ accepts invalid pointer-to-member conversion ! * [199]15320 Excessive memory consumption ! * [200]16246 Incorrect template argument deduction ! * [201]16273 Memory exhausted when using nested classes and virtual functions ! * [202]16401 ostringstream in gcc 3.4.x very slow for big data ! * [203]16411 undefined reference to __gnu_cxx::stdio_sync_filebuf >::file() ! * [204]16489 G++ incorrectly rejects use of a null constant integral expression as a null constant pointer ! * [205]16618 offsetof fails with constant member ! * [206]16637 syntax error reported for valid input code ! * [207]16717 __attribute__((constructor)) broken in C++ ! * [208]16813 compiler error in DEBUG version of range insertion std::map::insert ! * [209]16853 pointer-to-member initialization from incompatible one accepted ! * [210]16889 ambiguity is not detected ! * [211]16959 Segmentation fault in ios_base::sync_with_stdio Java compiler and library ! * [212]7587 direct threaded interpreter not thread-safe ! * [213]16473 ServerSocket accept() leaks file descriptors ! * [214]16478 Hash synchronization deadlock with finalizers Alpha-specific ! * [215]10695 ICE in dwarf2out_frame_debug_expr, in dwarf2out.c ! * [216]16974 could not split insn (ice in final_scan_insn, in final.c) x86-specific ! * [217]16298 ICE in output_operand ! * [218]17113 ICE with SSE2 intrinsics x86-64 specific ! * [219]14697 libstdc++ couldn't find 32bit libgcc_s MIPS-specific ! * [220]15869 [mips64] No NOP after LW (with -mips1 -O0) ! * [221]16325 [mips64] value profiling clobbers gp on mips ! * [222]16357 [mipsisa64-elf] ICE copying 7 bytes between extern char[]s ! * [223]16380 [mips64] Use of uninitialised register after dbra conversion ! * [224]16407 [mips64] Unaligned access to local variables ! * [225]16643 [mips64] verify_local_live_at_start ICE after crossjumping & cfgcleanup ARM-specific ! * [226]15927 THUMB -O2: strength-reduced iteration variable ends up off by 1 ! * [227]15948 THUMB: ICE with non-commutative cbranch ! * [228]17019 THUMB: bad switch statement in md code for addsi3_cbranch_scratch IA64-specific ! * [229]16130 ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=merced) ! * [230]16142 ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=itanium) ! * [231]16278 Gcc failed to build Linux kernel with -mtune=merced ! * [232]16414 ICE on valid code: typo in comparison of asm_noperands result ! * [233]16445 ICE on valid code: don't count ignored insns ! * [234]16490 ICE (segfault) while compiling with -fprofile-use ! * [235]16683 ia64 does not honor SUBTARGET_EXTRA_SPECS PowerPC-specific ! * [236]16195 (ppc64): Miscompilation of GCC 3.3.x by 3.4.x ! * [237]16239 ICE on ppc64 (mozilla 1.7 compile, -O1 -fno-exceptions issue) SPARC-specific ! * [238]16199 ICE while compiling apache 2.0.49 ! * [239]16416 -m64 doesn't imply -mcpu=v9 anymore ! * [240]16430 ICE when returning non-C aggregates larger than 16 bytes Bugs specific to embedded processors ! * [241]16379 [m32r] can't output large model function call of memcpy ! * [242]17093 [m32r] ICE with -msdata=use -O0 ! * [243]17119 [m32r] ICE at switch case 0x8000 DJGPP-specific ! * [244]15928 libstdc++ in 3.4.x doesn't cross-compile for djgpp Alpha Tru64-specific ! * [245]16210 libstdc++ gratuitously omits "long long" I/O Testsuite, documentation issues (compiler is not affected): ! * [246]15488 (libstdc++) possibly insufficient file permissions for executing test suite ! * [247]16250 ada/doctools runs makeinfo even in release tarball __________________________________________________________________ GCC 3.4.3 ! This is the [248]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). Bootstrap failures ! * [249]17369 [ia64] Bootstrap failure with binutils-2.15.90.0.1.1 ! * [250]17850 [arm-elf] bootstrap failure - libstdc++ uses strtold when undeclared Internal compiler errors (ICEs) affecting multiple platforms ! * [251]13948 (java) GCJ segmentation fault while compiling GL4Java .class files ! * [252]14492 ICE in loc_descriptor_from_tree, in dwarf2out.c ! * [253]16301 (c++) ICE when "strong" attribute is attached to a using directive ! * [254]16566 ICE with flexible arrays ! * [255]17023 ICE with nested functions in parameter declaration ! * [256]17027 ICE with noreturn function in loop at -O2 ! * [257]17524 ICE in grokdeclarator, in cp/decl.c ! * [258]17826 (c++) ICE in cp_tree_equal C and optimization bugs ! * [259]15526 -ftrapv aborts on 0 * (-1) ! * [260]16999 #ident stopped working ! * [261]17503 quadratic behaviour in invalid_mode_change_p ! * [262]17581 Long long arithmetic fails inside a switch/case statement when compiled with -O2 ! * [263]18129 -fwritable-strings doesn't work C++ compiler and library bugs ! * [264]10975 incorrect initial ostringstream::tellp() ! * [265]11722 Unbuffered filebuf::sgetn is slow ! * [266]14534 Unrecognizing static function as a template parameter when its return value is also templated ! * [267]15172 Copy constructor optimization in aggregate initialization ! * [268]15786 Bad error message for frequently occuring error. ! * [269]16162 Rejects valid member-template-definition ! * [270]16612 empty basic_strings can't live in shared memory ! * [271]16715 std::basic_iostream is instantiated when used, even though instantiations are already contained in libstdc++ ! * [272]16848 code in /ext/demangle.h appears broken ! * [273]17132 GCC fails to eliminate function template specialization when argument deduction fails ! * [274]17259 One more _S_leaf incorrectly qualified with _RopeRep:: in ropeimpl.h ! * [275]17327 use of `enumeral_type' in template type unification ! * [276]17393 "unused variable '._0'" warning with -Wall ! * [277]17501 Confusion with member templates ! * [278]17537 g++ not passing -lstdc++ to linker when all command line arguments are libraries ! * [279]17585 usage of unqualified name of static member from within class not allowed ! * [280]17821 Poor diagnostic for using "." instead of "->" ! * [281]17829 wrong error: call of overloaded function is ambiguous ! * [282]17851 Misleading diagnostic for invalid function declarations with undeclared types ! * [283]17976 Destructor is called twice ! * [284]18020 rejects valid definition of enum value in template ! * [285]18093 bogus conflict in namespace aliasing ! * [286]18140 C++ parser bug when using >> in templates Fortran ! * [287]17541 data statements with double precision constants fail x86-specific ! * [288]17853 -O2 ICE for MMX testcase SPARC-specific ! * [289]17245 ICE compiling gsl-1.5 statistics/lag1.c Darwin-specific ! * [290]17167 FATAL:Symbol L_foo$stub already defined. AIX-specific ! * [291]17277 could not catch an exception when specified -maix64 Solaris-specific ! * [292]17505 calls acosf(), ceilf(), and other functions missing from system libraries HP/UX specific: ! * [293]17684 /usr/ccs/bin/ld: Can't create libgcc_s.sl ARM-specific ! * [294]17384 ICE with mode attribute on structures MIPS-specific ! * [295]17770 No NOP after LWL with -mips1 Other embedded target specific ! * [296]11476 [arc-elf] gcc ICE on newlib's vfprintf.c ! * [297]14064 [avr-elf] -fdata-sections triggers ICE ! * [298]14678 [m68hc11-elf] gcc ICE ! * [299]15583 [powerpc-rtems] powerpc-rtems lacks __USE_INIT_FINI__ ! * [300]15790 [i686-coff] Alignment error building gcc with i686-coff target ! * [301]15886 [SH] Miscompilation with -O2 -fPIC ! * [302]16884 [avr-elf] [fweb related] bug while initializing variables Bugs relating to debugger support ! * [303]13841 missing debug info for _Complex function arguments ! * [304]15860 [big-endian targets] No DW_AT_location debug info is emitted for formal arguments to a function that uses "register" qualifiers Testsuite issues (compiler not affected) ! * [305]17465 Testsuite in libffi overrides LD_LIBRARY_PATH ! * [306]17469 Testsuite in libstdc++ overrides LD_LIBRARY_PATH ! * [307]18138 [mips-sgi-irix6.5] libgcc_s.so.1 not found by 64-bit testsuite Documentation ! * [308]15498 typo in gcc manual: non-existing locale example en_UK, should be en_GB ! * [309]15747 [mips-sgi-irix5.3] /bin/sh hangs during bootstrap: document broken shell ! * [310]16406 USE_LD_AS_NEEDED undocumented __________________________________________________________________ GCC 3.4.4 ! This is the [311]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). --- 10861,11176 ---- Bootstrap failures and issues ! * [169]16469 [mips-sgi-irix5.3] bootstrap fails in libstdc++-v3/testsuite ! * [170]16344 [hppa-linux-gnu] libstdc++'s PCH built by profiledbootstrap does not work with the built compiler ! * [171]16842 [Solaris/x86] mkheaders can not find mkheaders.conf Multi-platform internal compiler errors (ICEs) ! * [172]12608 (c++) ICE: expected class 't', have 'x' (error_mark) in cp_parser_class_specifier, in cp/parser.c ! * [173]14492 ICE in loc_descriptor_from_tree, in dwarf2out.c ! * [174]15461 (c++) ICE due to NRV and inlining ! * [175]15890 (c++) ICE in c_expand_expr, in c-common.c ! * [176]16180 ICE: segmentation fault in RTL optimization ! * [177]16224 (c++) ICE in write_unscoped_name (template/namespace) ! * [178]16408 ICE: in delete_insn, in cfgrtl.c ! * [179]16529 (c++) ICE for: namespace-alias shall not be declared as the name of any other entity ! * [180]16698 (c++) ICE with exceptions and declaration of __cxa_throw ! * [181]16706 (c++) ICE in finish_member_declaration, in cp/semantics.c ! * [182]16810 (c++) Legal C++ program with cast gives ICE in build_ptrmemfunc ! * [183]16851 (c++) ICE when throwing a comma expression ! * [184]16870 (c++) Boost.Spirit causes ICE in tsubst, in cp/pt.c ! * [185]16904 (c++) ICE in finish_class_member_access_expr, in cp/typeck.c ! * [186]16905 (c++) ICE (segfault) with exceptions ! * [187]16964 (c++) ICE in cp_parser_class_specifier due to redefinition ! * [188]17068 (c++) ICE: tree check: expected class 'd', have 'x' (identifier_node) in dependent_template_p, in cp/pt.c Preprocessor bugs ! * [189]16366 Preprocessor option -remap causes memory corruption Optimization ! * [190]15345 unreferenced nested inline functions not optimized away ! * [191]16590 Incorrect execution when compiling with -O2 ! * [192]16693 Bitwise AND is lost when used within a cast to an enum of the same precision ! * [193]17078 Jump into if(0) substatement fails Problems in generated debug information ! * [194]13956 incorrect stabs for nested local variables C front end bugs ! * [195]16684 GCC should not warn about redundant redeclarations of built-ins C++ compiler and library ! * [196]12658 Thread safety problems in locale::global() and locale::locale() ! * [197]13092 g++ accepts invalid pointer-to-member conversion ! * [198]15320 Excessive memory consumption ! * [199]16246 Incorrect template argument deduction ! * [200]16273 Memory exhausted when using nested classes and virtual functions ! * [201]16401 ostringstream in gcc 3.4.x very slow for big data ! * [202]16411 undefined reference to __gnu_cxx::stdio_sync_filebuf >::file() ! * [203]16489 G++ incorrectly rejects use of a null constant integral expression as a null constant pointer ! * [204]16618 offsetof fails with constant member ! * [205]16637 syntax error reported for valid input code ! * [206]16717 __attribute__((constructor)) broken in C++ ! * [207]16813 compiler error in DEBUG version of range insertion std::map::insert ! * [208]16853 pointer-to-member initialization from incompatible one accepted ! * [209]16889 ambiguity is not detected ! * [210]16959 Segmentation fault in ios_base::sync_with_stdio Java compiler and library ! * [211]7587 direct threaded interpreter not thread-safe ! * [212]16473 ServerSocket accept() leaks file descriptors ! * [213]16478 Hash synchronization deadlock with finalizers Alpha-specific ! * [214]10695 ICE in dwarf2out_frame_debug_expr, in dwarf2out.c ! * [215]16974 could not split insn (ice in final_scan_insn, in final.c) x86-specific ! * [216]16298 ICE in output_operand ! * [217]17113 ICE with SSE2 intrinsics x86-64 specific ! * [218]14697 libstdc++ couldn't find 32bit libgcc_s MIPS-specific ! * [219]15869 [mips64] No NOP after LW (with -mips1 -O0) ! * [220]16325 [mips64] value profiling clobbers gp on mips ! * [221]16357 [mipsisa64-elf] ICE copying 7 bytes between extern char[]s ! * [222]16380 [mips64] Use of uninitialised register after dbra conversion ! * [223]16407 [mips64] Unaligned access to local variables ! * [224]16643 [mips64] verify_local_live_at_start ICE after crossjumping & cfgcleanup ARM-specific ! * [225]15927 THUMB -O2: strength-reduced iteration variable ends up off by 1 ! * [226]15948 THUMB: ICE with non-commutative cbranch ! * [227]17019 THUMB: bad switch statement in md code for addsi3_cbranch_scratch IA64-specific ! * [228]16130 ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=merced) ! * [229]16142 ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=itanium) ! * [230]16278 Gcc failed to build Linux kernel with -mtune=merced ! * [231]16414 ICE on valid code: typo in comparison of asm_noperands result ! * [232]16445 ICE on valid code: don't count ignored insns ! * [233]16490 ICE (segfault) while compiling with -fprofile-use ! * [234]16683 ia64 does not honor SUBTARGET_EXTRA_SPECS PowerPC-specific ! * [235]16195 (ppc64): Miscompilation of GCC 3.3.x by 3.4.x ! * [236]16239 ICE on ppc64 (mozilla 1.7 compile, -O1 -fno-exceptions issue) SPARC-specific ! * [237]16199 ICE while compiling apache 2.0.49 ! * [238]16416 -m64 doesn't imply -mcpu=v9 anymore ! * [239]16430 ICE when returning non-C aggregates larger than 16 bytes Bugs specific to embedded processors ! * [240]16379 [m32r] can't output large model function call of memcpy ! * [241]17093 [m32r] ICE with -msdata=use -O0 ! * [242]17119 [m32r] ICE at switch case 0x8000 DJGPP-specific ! * [243]15928 libstdc++ in 3.4.x doesn't cross-compile for djgpp Alpha Tru64-specific ! * [244]16210 libstdc++ gratuitously omits "long long" I/O Testsuite, documentation issues (compiler is not affected): ! * [245]15488 (libstdc++) possibly insufficient file permissions for executing test suite ! * [246]16250 ada/doctools runs makeinfo even in release tarball __________________________________________________________________ GCC 3.4.3 ! This is the [247]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). Bootstrap failures ! * [248]17369 [ia64] Bootstrap failure with binutils-2.15.90.0.1.1 ! * [249]17850 [arm-elf] bootstrap failure - libstdc++ uses strtold when undeclared Internal compiler errors (ICEs) affecting multiple platforms ! * [250]13948 (java) GCJ segmentation fault while compiling GL4Java .class files ! * [251]14492 ICE in loc_descriptor_from_tree, in dwarf2out.c ! * [252]16301 (c++) ICE when "strong" attribute is attached to a using directive ! * [253]16566 ICE with flexible arrays ! * [254]17023 ICE with nested functions in parameter declaration ! * [255]17027 ICE with noreturn function in loop at -O2 ! * [256]17524 ICE in grokdeclarator, in cp/decl.c ! * [257]17826 (c++) ICE in cp_tree_equal C and optimization bugs ! * [258]15526 -ftrapv aborts on 0 * (-1) ! * [259]16999 #ident stopped working ! * [260]17503 quadratic behaviour in invalid_mode_change_p ! * [261]17581 Long long arithmetic fails inside a switch/case statement when compiled with -O2 ! * [262]18129 -fwritable-strings doesn't work C++ compiler and library bugs ! * [263]10975 incorrect initial ostringstream::tellp() ! * [264]11722 Unbuffered filebuf::sgetn is slow ! * [265]14534 Unrecognizing static function as a template parameter when its return value is also templated ! * [266]15172 Copy constructor optimization in aggregate initialization ! * [267]15786 Bad error message for frequently occuring error. ! * [268]16162 Rejects valid member-template-definition ! * [269]16612 empty basic_strings can't live in shared memory ! * [270]16715 std::basic_iostream is instantiated when used, even though instantiations are already contained in libstdc++ ! * [271]16848 code in /ext/demangle.h appears broken ! * [272]17132 GCC fails to eliminate function template specialization when argument deduction fails ! * [273]17259 One more _S_leaf incorrectly qualified with _RopeRep:: in ropeimpl.h ! * [274]17327 use of `enumeral_type' in template type unification ! * [275]17393 "unused variable '._0'" warning with -Wall ! * [276]17501 Confusion with member templates ! * [277]17537 g++ not passing -lstdc++ to linker when all command line arguments are libraries ! * [278]17585 usage of unqualified name of static member from within class not allowed ! * [279]17821 Poor diagnostic for using "." instead of "->" ! * [280]17829 wrong error: call of overloaded function is ambiguous ! * [281]17851 Misleading diagnostic for invalid function declarations with undeclared types ! * [282]17976 Destructor is called twice ! * [283]18020 rejects valid definition of enum value in template ! * [284]18093 bogus conflict in namespace aliasing ! * [285]18140 C++ parser bug when using >> in templates Fortran ! * [286]17541 data statements with double precision constants fail x86-specific ! * [287]17853 -O2 ICE for MMX testcase SPARC-specific ! * [288]17245 ICE compiling gsl-1.5 statistics/lag1.c Darwin-specific ! * [289]17167 FATAL:Symbol L_foo$stub already defined. AIX-specific ! * [290]17277 could not catch an exception when specified -maix64 Solaris-specific ! * [291]17505 calls acosf(), ceilf(), and other functions missing from system libraries HP/UX specific: ! * [292]17684 /usr/ccs/bin/ld: Can't create libgcc_s.sl ARM-specific ! * [293]17384 ICE with mode attribute on structures MIPS-specific ! * [294]17770 No NOP after LWL with -mips1 Other embedded target specific ! * [295]11476 [arc-elf] gcc ICE on newlib's vfprintf.c ! * [296]14064 [avr-elf] -fdata-sections triggers ICE ! * [297]14678 [m68hc11-elf] gcc ICE ! * [298]15583 [powerpc-rtems] powerpc-rtems lacks __USE_INIT_FINI__ ! * [299]15790 [i686-coff] Alignment error building gcc with i686-coff target ! * [300]15886 [SH] Miscompilation with -O2 -fPIC ! * [301]16884 [avr-elf] [fweb related] bug while initializing variables Bugs relating to debugger support ! * [302]13841 missing debug info for _Complex function arguments ! * [303]15860 [big-endian targets] No DW_AT_location debug info is emitted for formal arguments to a function that uses "register" qualifiers Testsuite issues (compiler not affected) ! * [304]17465 Testsuite in libffi overrides LD_LIBRARY_PATH ! * [305]17469 Testsuite in libstdc++ overrides LD_LIBRARY_PATH ! * [306]18138 [mips-sgi-irix6.5] libgcc_s.so.1 not found by 64-bit testsuite Documentation ! * [307]15498 typo in gcc manual: non-existing locale example en_UK, should be en_GB ! * [308]15747 [mips-sgi-irix5.3] /bin/sh hangs during bootstrap: document broken shell ! * [309]16406 USE_LD_AS_NEEDED undocumented __________________________________________________________________ GCC 3.4.4 ! This is the [310]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.4 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). *************** GCC 3.4.4 *** 11113,11319 **** GCC 3.4.5 ! This is the [312]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). Bootstrap issues ! * [313]24688 sco_math fixincl breaks math.h C compiler bugs ! * [314]17188 struct Foo { } redefinition ! * [315]20187 wrong code for ((unsigned char)(unsigned long long)((a?a:1)&(a*b)))?0:1) ! * [316]21873 infinite warning loop on bad array initializer ! * [317]21899 enum definition accepts values to be overriden ! * [318]22061 ICE in find_function_data, in function.c ! * [319]22308 Failure to diagnose violation of constraint 6.516p2 ! * [320]22458 ICE on missing brace ! * [321]22589 ICE casting to long long ! * [322]24101 Segfault with preprocessed source C++ compiler and library bugs ! * [323]10611 operations on vector mode not recognized in C++ ! * [324]13377 unexpected behavior of namespace usage directive ! * [325]16002 Strange error message with new parser ! * [326]17413 local classes as template argument ! * [327]17609 spurious error message after using keyword ! * [328]17618 ICE in cp_convert_to_pointer, in cp/cvt.c ! * [329]18124 ICE with invalid template template parameter ! * [330]18155 typedef in template declaration not rejected ! * [331]18177 ICE with const_cast for undeclared variable ! * [332]18368 C++ error message regression ! * [333]16378 ICE when returning a copy of a packed member ! * [334]18466 int ::i; accepted ! * [335]18512 ICE on invalid usage of template base class ! * [336]18454 ICE when returning undefined type ! * [337]18738 typename not allowed with non-dependent qualified name ! * [338]18803 rejects access to operator() in template ! * [339]19004 ICE in uses_template_parms, in cp/pt.c ! * [340]19208 Spurious error about variably modified type ! * [341]18253 bad error message / ICE for invalid template parameter ! * [342]19608 ICE after friend function definition in local class ! * [343]19884 ICE on explicit instantiation of a non-template constructor ! * [344]20153 ICE when C++ template function contains anonymous union ! * [345]20563 Infinite loop in diagnostic (and ice after error message) ! * [346]20789 ICE with incomplete type in template ! * [347]21336 Internal compiler error when using custom new operators ! * [348]21768 ICE in error message due to violation of coding conventions ! * [349]21853 constness of pointer to data member ignored ! * [350]21903 Default argument of template function causes a compile-time error ! * [351]21983 multiple diagnostics ! * [352]21987 New testsuite failure g++.dg/warn/conversion-function-1.C ! * [353]22153 ICE on invalid template specialization ! * [354]22172 Internal compiler error, seg fault. ! * [355]21286 filebuf::xsgetn vs pipes ! * [356]22233 ICE with wrong number of template parameters ! * [357]22508 ICE after invalid operator new ! * [358]22545 ICE with pointer to class member & user defined conversion operator ! * [359]23528 Wrong default allocator in ext/hash_map ! * [360]23550 char_traits requirements/1.cc test bad math ! * [361]23586 Bad diagnostic for invalid namespace-name ! * [362]23624 ICE in invert_truthvalue, in fold-const.c ! * [363]23639 Bad error message: not a member of '' ! * [364]23797 ICE on typename outside template ! * [365]23965 Bogus error message: no matching function for call to 'foo()' ! * [366]24052 &#`label_decl' not supported by dump_expr# ! * [367]24580 virtual base class cause exception not to be caught Problems in generated debug information ! * [368]24267 Bad DWARF for altivec vectors Optimizations issues ! * [369]17810 ICE in verify_local_live_at_start ! * [370]17860 Wrong generated code for loop with varying bound ! * [371]21709 ICE on compile-time complex NaN ! * [372]21964 broken tail call at -O2 or more ! * [373]22167 Strange optimization bug when using -Os ! * [374]22619 Compilation failure for real_const_1.f and real_const_2.f90 ! * [375]23241 Invalid code generated for comparison of uchar to 255 ! * [376]23478 Miscompilation due to reloading of a var that is also used in EH pad ! * [377]24470 segmentation fault in cc1plus when compiling with -O ! * [378]24950 ICE in operand_subword_force Precompiled headers problems ! * [379]14400 Cannot compile qt-x11-free-3.3.0 ! * [380]14940 PCH largefile test fails on various platforms Preprocessor bugs ! * [381]20239 ICE on empty preprocessed input ! * [382]15220 "gcc -E -MM -MG" reports missing system headers in source directory Testsuite issues ! * [383]19275 gcc.dg/20020919-1.c fails with -fpic/-fPIC on i686-pc-linux-gnu Alpha specific ! * [384]21888 bootstrap failure with linker relaxation enabled ARM specific ! * [385]15342 [arm-linux]: ICE in verify_local_live_at_start ! * [386]23985 Memory aliasing information incorrect in inlined memcpy ColdFile specific ! * [387]16719 Illegal move of byte into address register causes compiler to ICE HPPA specific ! * [388]21723 ICE while building libgfortran ! * [389]21841 -mhp-ld/-mgnu-ld documentation IA-64 specific ! * [390]23644 IA-64 hardware models and configuration options documentation error ! * [391]24718 Shared libgcc not used for linking by default M68000 specific ! * [392]18421 ICE in reload_cse_simplify_operands, in postreload.c MIPS specific ! * [393]20621 ICE in change_address_1, in emit-rtl.c PowerPC and PowerPC64 specific ! * [394]18583 error on valid code: const __attribute__((altivec(vector__))) doesn't work in arrays ! * [395]20191 ICE in reload_cse_simplify_operands ! * [396]22083 AIX: TARGET_C99_FUNCTIONS is wrongly defined ! * [397]23070 CALL_V4_CLEAR_FP_ARGS flag not properly set ! * [398]23404 gij trashes args of functions with more than 8 fp args ! * [399]23539 C & C++ compiler generating misaligned references regardless of compiler flags ! * [400]24102 floatdisf2_internal2 broken ! * [401]24465 -mminimal-toc miscompilation of __thread vars Solaris specific ! * [402]19933 Problem with define of HUGE_VAL in math_c99 ! * [403]21889 Native Solaris assembler cannot grok DTP-relative debug symbols SPARC specific ! * [404]19300 PCH failures on sparc-linux ! * [405]20301 Assembler labels have a leading "-" ! * [406]20673 C PCH testsuite assembly comparison failure x86 and x86_64 specific ! * [407]18582 ICE with arrays of type V2DF ! * [408]19340 Compilation SEGFAULTs with -O1 -fschedule-insns2 -fsched2-use-traces ! * [409]21716 ICE in reg-stack.c's swap_rtx_condition ! * [410]24315 amd64 fails -fpeephole2 __________________________________________________________________ GCC 3.4.6 ! This is the [411]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.6 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [412]GCC manuals. If that fails, the ! [413]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 [414]gcc@gcc.gnu.org. All of [415]our lists have public archives. ! Copyright (C) [416]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [417]maintained by the GCC team. Last modified ! 2016-01-30[418]. References --- 11178,11384 ---- GCC 3.4.5 ! This is the [311]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.5 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). Bootstrap issues ! * [312]24688 sco_math fixincl breaks math.h C compiler bugs ! * [313]17188 struct Foo { } redefinition ! * [314]20187 wrong code for ((unsigned char)(unsigned long long)((a?a:1)&(a*b)))?0:1) ! * [315]21873 infinite warning loop on bad array initializer ! * [316]21899 enum definition accepts values to be overriden ! * [317]22061 ICE in find_function_data, in function.c ! * [318]22308 Failure to diagnose violation of constraint 6.516p2 ! * [319]22458 ICE on missing brace ! * [320]22589 ICE casting to long long ! * [321]24101 Segfault with preprocessed source C++ compiler and library bugs ! * [322]10611 operations on vector mode not recognized in C++ ! * [323]13377 unexpected behavior of namespace usage directive ! * [324]16002 Strange error message with new parser ! * [325]17413 local classes as template argument ! * [326]17609 spurious error message after using keyword ! * [327]17618 ICE in cp_convert_to_pointer, in cp/cvt.c ! * [328]18124 ICE with invalid template template parameter ! * [329]18155 typedef in template declaration not rejected ! * [330]18177 ICE with const_cast for undeclared variable ! * [331]18368 C++ error message regression ! * [332]16378 ICE when returning a copy of a packed member ! * [333]18466 int ::i; accepted ! * [334]18512 ICE on invalid usage of template base class ! * [335]18454 ICE when returning undefined type ! * [336]18738 typename not allowed with non-dependent qualified name ! * [337]18803 rejects access to operator() in template ! * [338]19004 ICE in uses_template_parms, in cp/pt.c ! * [339]19208 Spurious error about variably modified type ! * [340]18253 bad error message / ICE for invalid template parameter ! * [341]19608 ICE after friend function definition in local class ! * [342]19884 ICE on explicit instantiation of a non-template constructor ! * [343]20153 ICE when C++ template function contains anonymous union ! * [344]20563 Infinite loop in diagnostic (and ice after error message) ! * [345]20789 ICE with incomplete type in template ! * [346]21336 Internal compiler error when using custom new operators ! * [347]21768 ICE in error message due to violation of coding conventions ! * [348]21853 constness of pointer to data member ignored ! * [349]21903 Default argument of template function causes a compile-time error ! * [350]21983 multiple diagnostics ! * [351]21987 New testsuite failure g++.dg/warn/conversion-function-1.C ! * [352]22153 ICE on invalid template specialization ! * [353]22172 Internal compiler error, seg fault. ! * [354]21286 filebuf::xsgetn vs pipes ! * [355]22233 ICE with wrong number of template parameters ! * [356]22508 ICE after invalid operator new ! * [357]22545 ICE with pointer to class member & user defined conversion operator ! * [358]23528 Wrong default allocator in ext/hash_map ! * [359]23550 char_traits requirements/1.cc test bad math ! * [360]23586 Bad diagnostic for invalid namespace-name ! * [361]23624 ICE in invert_truthvalue, in fold-const.c ! * [362]23639 Bad error message: not a member of '' ! * [363]23797 ICE on typename outside template ! * [364]23965 Bogus error message: no matching function for call to 'foo()' ! * [365]24052 &#`label_decl' not supported by dump_expr# ! * [366]24580 virtual base class cause exception not to be caught Problems in generated debug information ! * [367]24267 Bad DWARF for altivec vectors Optimizations issues ! * [368]17810 ICE in verify_local_live_at_start ! * [369]17860 Wrong generated code for loop with varying bound ! * [370]21709 ICE on compile-time complex NaN ! * [371]21964 broken tail call at -O2 or more ! * [372]22167 Strange optimization bug when using -Os ! * [373]22619 Compilation failure for real_const_1.f and real_const_2.f90 ! * [374]23241 Invalid code generated for comparison of uchar to 255 ! * [375]23478 Miscompilation due to reloading of a var that is also used in EH pad ! * [376]24470 segmentation fault in cc1plus when compiling with -O ! * [377]24950 ICE in operand_subword_force Precompiled headers problems ! * [378]14400 Cannot compile qt-x11-free-3.3.0 ! * [379]14940 PCH largefile test fails on various platforms Preprocessor bugs ! * [380]20239 ICE on empty preprocessed input ! * [381]15220 "gcc -E -MM -MG" reports missing system headers in source directory Testsuite issues ! * [382]19275 gcc.dg/20020919-1.c fails with -fpic/-fPIC on i686-pc-linux-gnu Alpha specific ! * [383]21888 bootstrap failure with linker relaxation enabled ARM specific ! * [384]15342 [arm-linux]: ICE in verify_local_live_at_start ! * [385]23985 Memory aliasing information incorrect in inlined memcpy ColdFile specific ! * [386]16719 Illegal move of byte into address register causes compiler to ICE HPPA specific ! * [387]21723 ICE while building libgfortran ! * [388]21841 -mhp-ld/-mgnu-ld documentation IA-64 specific ! * [389]23644 IA-64 hardware models and configuration options documentation error ! * [390]24718 Shared libgcc not used for linking by default M68000 specific ! * [391]18421 ICE in reload_cse_simplify_operands, in postreload.c MIPS specific ! * [392]20621 ICE in change_address_1, in emit-rtl.c PowerPC and PowerPC64 specific ! * [393]18583 error on valid code: const __attribute__((altivec(vector__))) doesn't work in arrays ! * [394]20191 ICE in reload_cse_simplify_operands ! * [395]22083 AIX: TARGET_C99_FUNCTIONS is wrongly defined ! * [396]23070 CALL_V4_CLEAR_FP_ARGS flag not properly set ! * [397]23404 gij trashes args of functions with more than 8 fp args ! * [398]23539 C & C++ compiler generating misaligned references regardless of compiler flags ! * [399]24102 floatdisf2_internal2 broken ! * [400]24465 -mminimal-toc miscompilation of __thread vars Solaris specific ! * [401]19933 Problem with define of HUGE_VAL in math_c99 ! * [402]21889 Native Solaris assembler cannot grok DTP-relative debug symbols SPARC specific ! * [403]19300 PCH failures on sparc-linux ! * [404]20301 Assembler labels have a leading "-" ! * [405]20673 C PCH testsuite assembly comparison failure x86 and x86_64 specific ! * [406]18582 ICE with arrays of type V2DF ! * [407]19340 Compilation SEGFAULTs with -O1 -fschedule-insns2 -fsched2-use-traces ! * [408]21716 ICE in reg-stack.c's swap_rtx_condition ! * [409]24315 amd64 fails -fpeephole2 __________________________________________________________________ GCC 3.4.6 ! This is the [410]list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the 3.4.6 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). For questions related to the use of GCC, please consult these web ! pages and the [411]GCC manuals. If that fails, the ! [412]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 [413]gcc@gcc.gnu.org. All of [414]our lists have public archives. ! Copyright (C) [415]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [416]maintained by the GCC team. Last modified ! 2016-12-30[417]. References *************** References *** 11326,11332 **** 7. http://www.boost.org/ 8. https://gcc.gnu.org/PR11953 9. https://gcc.gnu.org/PR8361 ! 10. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Other-Builtins.html#Other Builtins 11. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_closed.html#209 12. http://gcc.gnu.org/bugs/#cxx_rvalbind 13. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Objective-C-Dialect-Options.html --- 11391,11397 ---- 7. http://www.boost.org/ 8. https://gcc.gnu.org/PR11953 9. https://gcc.gnu.org/PR8361 ! 10. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Other-Builtins.html#Other%20Builtins 11. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_closed.html#209 12. http://gcc.gnu.org/bugs/#cxx_rvalbind 13. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Objective-C-Dialect-Options.html *************** References *** 11336,11742 **** 17. http://www.eclipse.org/ 18. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/g77/News.html 19. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Alpha-Built-in-Functions.html ! 20. http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51A_HTML/ARH9MBTE/DTMNPLTN.HTM#normal-argument-list-structure ! 21. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gccint/Processor-pipeline-description.html ! 22. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gccint/Comparison-of-the-two-descriptions.html ! 23. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gccint/Processor-pipeline-description.html ! 24. http://gcc.gnu.org/gcc-3.4/mips-abi.html ! 25. http://gcc.gnu.org/gcc-3.4/powerpc-abi.html ! 26. http://gcc.gnu.org/gcc-3.4/sparc-abi.html ! 27. https://gcc.gnu.org/bugzilla/buglist.cgi?short_desc_type=notregexp&short_desc=\[3\.4.*[Rr]egression&target_milestone=3.4.0&bug_status=RESOLVED&resolution=FIXED ! 28. https://gcc.gnu.org/PR10129 ! 29. https://gcc.gnu.org/PR14576 ! 30. https://gcc.gnu.org/PR14760 ! 31. https://gcc.gnu.org/PR14671 ! 32. https://gcc.gnu.org/PR15093 ! 33. https://gcc.gnu.org/PR15178 ! 34. https://gcc.gnu.org/PR12753 ! 35. https://gcc.gnu.org/PR13985 ! 36. https://gcc.gnu.org/PR14810 ! 37. https://gcc.gnu.org/PR14883 ! 38. https://gcc.gnu.org/PR15044 ! 39. https://gcc.gnu.org/PR15057 ! 40. https://gcc.gnu.org/PR15064 ! 41. https://gcc.gnu.org/PR15142 ! 42. https://gcc.gnu.org/PR15159 ! 43. https://gcc.gnu.org/PR15165 ! 44. https://gcc.gnu.org/PR15193 ! 45. https://gcc.gnu.org/PR15209 ! 46. https://gcc.gnu.org/PR15227 ! 47. https://gcc.gnu.org/PR15285 ! 48. https://gcc.gnu.org/PR15299 ! 49. https://gcc.gnu.org/PR15329 ! 50. https://gcc.gnu.org/PR15550 ! 51. https://gcc.gnu.org/PR15554 ! 52. https://gcc.gnu.org/PR15640 ! 53. https://gcc.gnu.org/PR15666 ! 54. https://gcc.gnu.org/PR15696 ! 55. https://gcc.gnu.org/PR15701 ! 56. https://gcc.gnu.org/PR15761 ! 57. https://gcc.gnu.org/PR15829 ! 58. https://gcc.gnu.org/PR14538 ! 59. https://gcc.gnu.org/PR12391 ! 60. https://gcc.gnu.org/PR14649 ! 61. https://gcc.gnu.org/PR15004 ! 62. https://gcc.gnu.org/PR15749 ! 63. https://gcc.gnu.org/PR10646 ! 64. https://gcc.gnu.org/PR12077 ! 65. https://gcc.gnu.org/PR13598 ! 66. https://gcc.gnu.org/PR14211 ! 67. https://gcc.gnu.org/PR14220 ! 68. https://gcc.gnu.org/PR14245 ! 69. https://gcc.gnu.org/PR14340 ! 70. https://gcc.gnu.org/PR14600 ! 71. https://gcc.gnu.org/PR14668 ! 72. https://gcc.gnu.org/PR14775 ! 73. https://gcc.gnu.org/PR14821 ! 74. https://gcc.gnu.org/PR14930 ! 75. https://gcc.gnu.org/PR14932 ! 76. https://gcc.gnu.org/PR14950 ! 77. https://gcc.gnu.org/PR14962 ! 78. https://gcc.gnu.org/PR14975 ! 79. https://gcc.gnu.org/PR15002 ! 80. https://gcc.gnu.org/PR15025 ! 81. https://gcc.gnu.org/PR15046 ! 82. https://gcc.gnu.org/PR15069 ! 83. https://gcc.gnu.org/PR15074 ! 84. https://gcc.gnu.org/PR15083 ! 85. https://gcc.gnu.org/PR15096 ! 86. https://gcc.gnu.org/PR15287 ! 87. https://gcc.gnu.org/PR15317 ! 88. https://gcc.gnu.org/PR15337 ! 89. https://gcc.gnu.org/PR15361 ! 90. https://gcc.gnu.org/PR15412 ! 91. https://gcc.gnu.org/PR15427 ! 92. https://gcc.gnu.org/PR15471 ! 93. https://gcc.gnu.org/PR15503 ! 94. https://gcc.gnu.org/PR15507 ! 95. https://gcc.gnu.org/PR15542 ! 96. https://gcc.gnu.org/PR15565 ! 97. https://gcc.gnu.org/PR15625 ! 98. https://gcc.gnu.org/PR15629 ! 99. https://gcc.gnu.org/PR15742 ! 100. https://gcc.gnu.org/PR15775 ! 101. https://gcc.gnu.org/PR15821 ! 102. https://gcc.gnu.org/PR15862 ! 103. https://gcc.gnu.org/PR15875 ! 104. https://gcc.gnu.org/PR15877 ! 105. https://gcc.gnu.org/PR15947 ! 106. https://gcc.gnu.org/PR16020 ! 107. https://gcc.gnu.org/PR16154 ! 108. https://gcc.gnu.org/PR16174 ! 109. https://gcc.gnu.org/PR14315 ! 110. https://gcc.gnu.org/PR15151 ! 111. https://gcc.gnu.org/PR7993 ! 112. https://gcc.gnu.org/PR15228 ! 113. https://gcc.gnu.org/PR15345 ! 114. https://gcc.gnu.org/PR15945 ! 115. https://gcc.gnu.org/PR15526 ! 116. https://gcc.gnu.org/PR14690 ! 117. https://gcc.gnu.org/PR15112 ! 118. https://gcc.gnu.org/PR15067 ! 119. https://gcc.gnu.org/PR1963 ! 120. https://gcc.gnu.org/PR15717 ! 121. https://gcc.gnu.org/PR14782 ! 122. https://gcc.gnu.org/PR14828 ! 123. https://gcc.gnu.org/PR15202 ! 124. https://gcc.gnu.org/PR14610 ! 125. https://gcc.gnu.org/PR14813 ! 126. https://gcc.gnu.org/PR14857 ! 127. https://gcc.gnu.org/PR15598 ! 128. https://gcc.gnu.org/PR15653 ! 129. https://gcc.gnu.org/PR15189 ! 130. https://gcc.gnu.org/PR15331 ! 131. https://gcc.gnu.org/PR16144 ! 132. https://gcc.gnu.org/PR16176 ! 133. https://gcc.gnu.org/PR11591 ! 134. https://gcc.gnu.org/PR12028 ! 135. https://gcc.gnu.org/PR14478 ! 136. https://gcc.gnu.org/PR14567 ! 137. https://gcc.gnu.org/PR14715 ! 138. https://gcc.gnu.org/PR14902 ! 139. https://gcc.gnu.org/PR14924 ! 140. https://gcc.gnu.org/PR14960 ! 141. https://gcc.gnu.org/PR15106 ! 142. https://gcc.gnu.org/PR16026 ! 143. https://gcc.gnu.org/PR15191 ! 144. https://gcc.gnu.org/PR15662 ! 145. https://gcc.gnu.org/PR15054 ! 146. https://gcc.gnu.org/PR15783 ! 147. https://gcc.gnu.org/PR15626 ! 148. https://gcc.gnu.org/PR14326 ! 149. https://gcc.gnu.org/PR14723 ! 150. https://gcc.gnu.org/PR15290 ! 151. https://gcc.gnu.org/PR15250 ! 152. https://gcc.gnu.org/PR15551 ! 153. https://gcc.gnu.org/PR8309 ! 154. https://gcc.gnu.org/PR13250 ! 155. https://gcc.gnu.org/PR13803 ! 156. https://gcc.gnu.org/PR14093 ! 157. https://gcc.gnu.org/PR14457 ! 158. https://gcc.gnu.org/PR14542 ! 159. https://gcc.gnu.org/PR15100 ! 160. https://gcc.gnu.org/PR15296 ! 161. https://gcc.gnu.org/PR15396 ! 162. https://gcc.gnu.org/PR15782 ! 163. https://gcc.gnu.org/PR11610 ! 164. https://gcc.gnu.org/PR15488 ! 165. https://gcc.gnu.org/PR15489 ! 166. https://gcc.gnu.org/PR13928 ! 167. https://gcc.gnu.org/PR14150 ! 168. https://gcc.gnu.org/PR14949 ! 169. https://gcc.gnu.org/PR15123 ! 170. https://gcc.gnu.org/PR16469 ! 171. https://gcc.gnu.org/PR16344 ! 172. https://gcc.gnu.org/PR16842 ! 173. https://gcc.gnu.org/PR12608 ! 174. https://gcc.gnu.org/PR14492 ! 175. https://gcc.gnu.org/PR15461 ! 176. https://gcc.gnu.org/PR15890 ! 177. https://gcc.gnu.org/PR16180 ! 178. https://gcc.gnu.org/PR16224 ! 179. https://gcc.gnu.org/PR16408 ! 180. https://gcc.gnu.org/PR16529 ! 181. https://gcc.gnu.org/PR16698 ! 182. https://gcc.gnu.org/PR16706 ! 183. https://gcc.gnu.org/PR16810 ! 184. https://gcc.gnu.org/PR16851 ! 185. https://gcc.gnu.org/PR16870 ! 186. https://gcc.gnu.org/PR16904 ! 187. https://gcc.gnu.org/PR16905 ! 188. https://gcc.gnu.org/PR16964 ! 189. https://gcc.gnu.org/PR17068 ! 190. https://gcc.gnu.org/PR16366 ! 191. https://gcc.gnu.org/PR15345 ! 192. https://gcc.gnu.org/PR16590 ! 193. https://gcc.gnu.org/PR16693 ! 194. https://gcc.gnu.org/PR17078 ! 195. https://gcc.gnu.org/PR13956 ! 196. https://gcc.gnu.org/PR16684 ! 197. https://gcc.gnu.org/PR12658 ! 198. https://gcc.gnu.org/PR13092 ! 199. https://gcc.gnu.org/PR15320 ! 200. https://gcc.gnu.org/PR16246 ! 201. https://gcc.gnu.org/PR16273 ! 202. https://gcc.gnu.org/PR16401 ! 203. https://gcc.gnu.org/PR16411 ! 204. https://gcc.gnu.org/PR16489 ! 205. https://gcc.gnu.org/PR16618 ! 206. https://gcc.gnu.org/PR16637 ! 207. https://gcc.gnu.org/PR16717 ! 208. https://gcc.gnu.org/PR16813 ! 209. https://gcc.gnu.org/PR16853 ! 210. https://gcc.gnu.org/PR16889 ! 211. https://gcc.gnu.org/PR16959 ! 212. https://gcc.gnu.org/PR7587 ! 213. https://gcc.gnu.org/PR16473 ! 214. https://gcc.gnu.org/PR16478 ! 215. https://gcc.gnu.org/PR10695 ! 216. https://gcc.gnu.org/PR16974 ! 217. https://gcc.gnu.org/PR16298 ! 218. https://gcc.gnu.org/PR17113 ! 219. https://gcc.gnu.org/PR14697 ! 220. https://gcc.gnu.org/PR15869 ! 221. https://gcc.gnu.org/PR16325 ! 222. https://gcc.gnu.org/PR16357 ! 223. https://gcc.gnu.org/PR16380 ! 224. https://gcc.gnu.org/PR16407 ! 225. https://gcc.gnu.org/PR16643 ! 226. https://gcc.gnu.org/PR15927 ! 227. https://gcc.gnu.org/PR15948 ! 228. https://gcc.gnu.org/PR17019 ! 229. https://gcc.gnu.org/PR16130 ! 230. https://gcc.gnu.org/PR16142 ! 231. https://gcc.gnu.org/PR16278 ! 232. https://gcc.gnu.org/PR16414 ! 233. https://gcc.gnu.org/PR16445 ! 234. https://gcc.gnu.org/PR16490 ! 235. https://gcc.gnu.org/PR16683 ! 236. https://gcc.gnu.org/PR16195 ! 237. https://gcc.gnu.org/PR16239 ! 238. https://gcc.gnu.org/PR16199 ! 239. https://gcc.gnu.org/PR16416 ! 240. https://gcc.gnu.org/PR16430 ! 241. https://gcc.gnu.org/PR16379 ! 242. https://gcc.gnu.org/PR17093 ! 243. https://gcc.gnu.org/PR17119 ! 244. https://gcc.gnu.org/PR15928 ! 245. https://gcc.gnu.org/PR16210 ! 246. https://gcc.gnu.org/PR15488 ! 247. https://gcc.gnu.org/PR16250 ! 248. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.3 ! 249. https://gcc.gnu.org/PR17369 ! 250. https://gcc.gnu.org/PR17850 ! 251. https://gcc.gnu.org/PR13948 ! 252. https://gcc.gnu.org/PR14492 ! 253. https://gcc.gnu.org/PR16301 ! 254. https://gcc.gnu.org/PR16566 ! 255. https://gcc.gnu.org/PR17023 ! 256. https://gcc.gnu.org/PR17027 ! 257. https://gcc.gnu.org/PR17524 ! 258. https://gcc.gnu.org/PR17826 ! 259. https://gcc.gnu.org/PR15526 ! 260. https://gcc.gnu.org/PR16999 ! 261. https://gcc.gnu.org/PR17503 ! 262. https://gcc.gnu.org/PR17581 ! 263. https://gcc.gnu.org/PR18129 ! 264. https://gcc.gnu.org/PR10975 ! 265. https://gcc.gnu.org/PR11722 ! 266. https://gcc.gnu.org/PR14534 ! 267. https://gcc.gnu.org/PR15172 ! 268. https://gcc.gnu.org/PR15786 ! 269. https://gcc.gnu.org/PR16162 ! 270. https://gcc.gnu.org/PR16612 ! 271. https://gcc.gnu.org/PR16715 ! 272. https://gcc.gnu.org/PR16848 ! 273. https://gcc.gnu.org/PR17132 ! 274. https://gcc.gnu.org/PR17259 ! 275. https://gcc.gnu.org/PR17327 ! 276. https://gcc.gnu.org/PR17393 ! 277. https://gcc.gnu.org/PR17501 ! 278. https://gcc.gnu.org/PR17537 ! 279. https://gcc.gnu.org/PR17585 ! 280. https://gcc.gnu.org/PR17821 ! 281. https://gcc.gnu.org/PR17829 ! 282. https://gcc.gnu.org/PR17851 ! 283. https://gcc.gnu.org/PR17976 ! 284. https://gcc.gnu.org/PR18020 ! 285. https://gcc.gnu.org/PR18093 ! 286. https://gcc.gnu.org/PR18140 ! 287. https://gcc.gnu.org/PR17541 ! 288. https://gcc.gnu.org/PR17853 ! 289. https://gcc.gnu.org/PR17245 ! 290. https://gcc.gnu.org/PR17167 ! 291. https://gcc.gnu.org/PR17277 ! 292. https://gcc.gnu.org/PR17505 ! 293. https://gcc.gnu.org/PR17684 ! 294. https://gcc.gnu.org/PR17384 ! 295. https://gcc.gnu.org/PR17770 ! 296. https://gcc.gnu.org/PR11476 ! 297. https://gcc.gnu.org/PR14064 ! 298. https://gcc.gnu.org/PR14678 ! 299. https://gcc.gnu.org/PR15583 ! 300. https://gcc.gnu.org/PR15790 ! 301. https://gcc.gnu.org/PR15886 ! 302. https://gcc.gnu.org/PR16884 ! 303. https://gcc.gnu.org/PR13841 ! 304. https://gcc.gnu.org/PR15860 ! 305. https://gcc.gnu.org/PR17465 ! 306. https://gcc.gnu.org/PR17469 ! 307. https://gcc.gnu.org/PR18138 ! 308. https://gcc.gnu.org/PR15498 ! 309. https://gcc.gnu.org/PR15747 ! 310. https://gcc.gnu.org/PR16406 ! 311. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.4 ! 312. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.5 ! 313. https://gcc.gnu.org/PR24688 ! 314. https://gcc.gnu.org/PR17188 ! 315. https://gcc.gnu.org/PR20187 ! 316. https://gcc.gnu.org/PR21873 ! 317. https://gcc.gnu.org/PR21899 ! 318. https://gcc.gnu.org/PR22061 ! 319. https://gcc.gnu.org/PR22208 ! 320. https://gcc.gnu.org/PR22458 ! 321. https://gcc.gnu.org/PR22589 ! 322. https://gcc.gnu.org/PR24101 ! 323. https://gcc.gnu.org/PR10611 ! 324. https://gcc.gnu.org/PR13377 ! 325. https://gcc.gnu.org/PR16002 ! 326. https://gcc.gnu.org/PR17413 ! 327. https://gcc.gnu.org/PR17609 ! 328. https://gcc.gnu.org/PR17618 ! 329. https://gcc.gnu.org/PR18124 ! 330. https://gcc.gnu.org/PR18155 ! 331. https://gcc.gnu.org/PR18177 ! 332. https://gcc.gnu.org/PR18368 ! 333. https://gcc.gnu.org/PR18378 ! 334. https://gcc.gnu.org/PR18466 ! 335. https://gcc.gnu.org/PR18512 ! 336. https://gcc.gnu.org/PR18545 ! 337. https://gcc.gnu.org/PR18738 ! 338. https://gcc.gnu.org/PR18803 ! 339. https://gcc.gnu.org/PR19004 ! 340. https://gcc.gnu.org/PR19208 ! 341. https://gcc.gnu.org/PR19253 ! 342. https://gcc.gnu.org/PR19608 ! 343. https://gcc.gnu.org/PR19884 ! 344. https://gcc.gnu.org/PR20153 ! 345. https://gcc.gnu.org/PR20563 ! 346. https://gcc.gnu.org/PR20789 ! 347. https://gcc.gnu.org/PR21336 ! 348. https://gcc.gnu.org/PR21768 ! 349. https://gcc.gnu.org/PR21853 ! 350. https://gcc.gnu.org/PR21903 ! 351. https://gcc.gnu.org/PR21983 ! 352. https://gcc.gnu.org/PR21987 ! 353. https://gcc.gnu.org/PR22153 ! 354. https://gcc.gnu.org/PR22172 ! 355. https://gcc.gnu.org/PR21286 ! 356. https://gcc.gnu.org/PR22233 ! 357. https://gcc.gnu.org/PR22508 ! 358. https://gcc.gnu.org/PR22545 ! 359. https://gcc.gnu.org/PR23528 ! 360. https://gcc.gnu.org/PR23550 ! 361. https://gcc.gnu.org/PR23586 ! 362. https://gcc.gnu.org/PR23624 ! 363. https://gcc.gnu.org/PR23639 ! 364. https://gcc.gnu.org/PR23797 ! 365. https://gcc.gnu.org/PR23965 ! 366. https://gcc.gnu.org/PR24052 ! 367. https://gcc.gnu.org/PR24580 ! 368. https://gcc.gnu.org/PR24267 ! 369. https://gcc.gnu.org/PR17810 ! 370. https://gcc.gnu.org/PR17860 ! 371. https://gcc.gnu.org/PR21709 ! 372. https://gcc.gnu.org/PR21964 ! 373. https://gcc.gnu.org/PR22167 ! 374. https://gcc.gnu.org/PR22619 ! 375. https://gcc.gnu.org/PR23241 ! 376. https://gcc.gnu.org/PR23478 ! 377. https://gcc.gnu.org/PR24470 ! 378. https://gcc.gnu.org/PR24950 ! 379. https://gcc.gnu.org/PR14400 ! 380. https://gcc.gnu.org/PR14940 ! 381. https://gcc.gnu.org/PR20239 ! 382. https://gcc.gnu.org/PR15220 ! 383. https://gcc.gnu.org/PR19275 ! 384. https://gcc.gnu.org/PR21888 ! 385. https://gcc.gnu.org/PR15342 ! 386. https://gcc.gnu.org/PR23985 ! 387. https://gcc.gnu.org/PR16719 ! 388. https://gcc.gnu.org/PR21723 ! 389. https://gcc.gnu.org/PR21841 ! 390. https://gcc.gnu.org/PR23644 ! 391. https://gcc.gnu.org/PR24718 ! 392. https://gcc.gnu.org/PR18421 ! 393. https://gcc.gnu.org/PR20621 ! 394. https://gcc.gnu.org/PR18583 ! 395. https://gcc.gnu.org/PR20191 ! 396. https://gcc.gnu.org/PR22083 ! 397. https://gcc.gnu.org/PR23070 ! 398. https://gcc.gnu.org/PR23404 ! 399. https://gcc.gnu.org/PR23539 ! 400. https://gcc.gnu.org/PR24102 ! 401. https://gcc.gnu.org/PR24465 ! 402. https://gcc.gnu.org/PR19933 ! 403. https://gcc.gnu.org/PR21889 ! 404. https://gcc.gnu.org/PR19300 ! 405. https://gcc.gnu.org/PR20301 ! 406. https://gcc.gnu.org/PR20673 ! 407. https://gcc.gnu.org/PR18582 ! 408. https://gcc.gnu.org/PR19340 ! 409. https://gcc.gnu.org/PR21716 ! 410. https://gcc.gnu.org/PR24315 ! 411. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.6 ! 412. https://gcc.gnu.org/onlinedocs/ ! 413. mailto:gcc-help@gcc.gnu.org ! 414. mailto:gcc@gcc.gnu.org ! 415. https://gcc.gnu.org/lists.html ! 416. http://www.fsf.org/ ! 417. https://gcc.gnu.org/about.html ! 418. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.3/index.html GCC 3.3 Release Series May 03, 2005 --- 11401,11807 ---- 17. http://www.eclipse.org/ 18. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/g77/News.html 19. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Alpha-Built-in-Functions.html ! 20. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gccint/Processor-pipeline-description.html ! 21. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gccint/Comparison-of-the-two-descriptions.html ! 22. https://gcc.gnu.org/onlinedocs/gcc-3.4.3/gccint/Processor-pipeline-description.html ! 23. http://gcc.gnu.org/gcc-3.4/mips-abi.html ! 24. http://gcc.gnu.org/gcc-3.4/powerpc-abi.html ! 25. http://gcc.gnu.org/gcc-3.4/sparc-abi.html ! 26. https://gcc.gnu.org/bugzilla/buglist.cgi?short_desc_type=notregexp&short_desc=%5C%5B3%5C.4.*%5BRr%5Degression&target_milestone=3.4.0&bug_status=RESOLVED&resolution=FIXED ! 27. https://gcc.gnu.org/PR10129 ! 28. https://gcc.gnu.org/PR14576 ! 29. https://gcc.gnu.org/PR14760 ! 30. https://gcc.gnu.org/PR14671 ! 31. https://gcc.gnu.org/PR15093 ! 32. https://gcc.gnu.org/PR15178 ! 33. https://gcc.gnu.org/PR12753 ! 34. https://gcc.gnu.org/PR13985 ! 35. https://gcc.gnu.org/PR14810 ! 36. https://gcc.gnu.org/PR14883 ! 37. https://gcc.gnu.org/PR15044 ! 38. https://gcc.gnu.org/PR15057 ! 39. https://gcc.gnu.org/PR15064 ! 40. https://gcc.gnu.org/PR15142 ! 41. https://gcc.gnu.org/PR15159 ! 42. https://gcc.gnu.org/PR15165 ! 43. https://gcc.gnu.org/PR15193 ! 44. https://gcc.gnu.org/PR15209 ! 45. https://gcc.gnu.org/PR15227 ! 46. https://gcc.gnu.org/PR15285 ! 47. https://gcc.gnu.org/PR15299 ! 48. https://gcc.gnu.org/PR15329 ! 49. https://gcc.gnu.org/PR15550 ! 50. https://gcc.gnu.org/PR15554 ! 51. https://gcc.gnu.org/PR15640 ! 52. https://gcc.gnu.org/PR15666 ! 53. https://gcc.gnu.org/PR15696 ! 54. https://gcc.gnu.org/PR15701 ! 55. https://gcc.gnu.org/PR15761 ! 56. https://gcc.gnu.org/PR15829 ! 57. https://gcc.gnu.org/PR14538 ! 58. https://gcc.gnu.org/PR12391 ! 59. https://gcc.gnu.org/PR14649 ! 60. https://gcc.gnu.org/PR15004 ! 61. https://gcc.gnu.org/PR15749 ! 62. https://gcc.gnu.org/PR10646 ! 63. https://gcc.gnu.org/PR12077 ! 64. https://gcc.gnu.org/PR13598 ! 65. https://gcc.gnu.org/PR14211 ! 66. https://gcc.gnu.org/PR14220 ! 67. https://gcc.gnu.org/PR14245 ! 68. https://gcc.gnu.org/PR14340 ! 69. https://gcc.gnu.org/PR14600 ! 70. https://gcc.gnu.org/PR14668 ! 71. https://gcc.gnu.org/PR14775 ! 72. https://gcc.gnu.org/PR14821 ! 73. https://gcc.gnu.org/PR14930 ! 74. https://gcc.gnu.org/PR14932 ! 75. https://gcc.gnu.org/PR14950 ! 76. https://gcc.gnu.org/PR14962 ! 77. https://gcc.gnu.org/PR14975 ! 78. https://gcc.gnu.org/PR15002 ! 79. https://gcc.gnu.org/PR15025 ! 80. https://gcc.gnu.org/PR15046 ! 81. https://gcc.gnu.org/PR15069 ! 82. https://gcc.gnu.org/PR15074 ! 83. https://gcc.gnu.org/PR15083 ! 84. https://gcc.gnu.org/PR15096 ! 85. https://gcc.gnu.org/PR15287 ! 86. https://gcc.gnu.org/PR15317 ! 87. https://gcc.gnu.org/PR15337 ! 88. https://gcc.gnu.org/PR15361 ! 89. https://gcc.gnu.org/PR15412 ! 90. https://gcc.gnu.org/PR15427 ! 91. https://gcc.gnu.org/PR15471 ! 92. https://gcc.gnu.org/PR15503 ! 93. https://gcc.gnu.org/PR15507 ! 94. https://gcc.gnu.org/PR15542 ! 95. https://gcc.gnu.org/PR15565 ! 96. https://gcc.gnu.org/PR15625 ! 97. https://gcc.gnu.org/PR15629 ! 98. https://gcc.gnu.org/PR15742 ! 99. https://gcc.gnu.org/PR15775 ! 100. https://gcc.gnu.org/PR15821 ! 101. https://gcc.gnu.org/PR15862 ! 102. https://gcc.gnu.org/PR15875 ! 103. https://gcc.gnu.org/PR15877 ! 104. https://gcc.gnu.org/PR15947 ! 105. https://gcc.gnu.org/PR16020 ! 106. https://gcc.gnu.org/PR16154 ! 107. https://gcc.gnu.org/PR16174 ! 108. https://gcc.gnu.org/PR14315 ! 109. https://gcc.gnu.org/PR15151 ! 110. https://gcc.gnu.org/PR7993 ! 111. https://gcc.gnu.org/PR15228 ! 112. https://gcc.gnu.org/PR15345 ! 113. https://gcc.gnu.org/PR15945 ! 114. https://gcc.gnu.org/PR15526 ! 115. https://gcc.gnu.org/PR14690 ! 116. https://gcc.gnu.org/PR15112 ! 117. https://gcc.gnu.org/PR15067 ! 118. https://gcc.gnu.org/PR1963 ! 119. https://gcc.gnu.org/PR15717 ! 120. https://gcc.gnu.org/PR14782 ! 121. https://gcc.gnu.org/PR14828 ! 122. https://gcc.gnu.org/PR15202 ! 123. https://gcc.gnu.org/PR14610 ! 124. https://gcc.gnu.org/PR14813 ! 125. https://gcc.gnu.org/PR14857 ! 126. https://gcc.gnu.org/PR15598 ! 127. https://gcc.gnu.org/PR15653 ! 128. https://gcc.gnu.org/PR15189 ! 129. https://gcc.gnu.org/PR15331 ! 130. https://gcc.gnu.org/PR16144 ! 131. https://gcc.gnu.org/PR16176 ! 132. https://gcc.gnu.org/PR11591 ! 133. https://gcc.gnu.org/PR12028 ! 134. https://gcc.gnu.org/PR14478 ! 135. https://gcc.gnu.org/PR14567 ! 136. https://gcc.gnu.org/PR14715 ! 137. https://gcc.gnu.org/PR14902 ! 138. https://gcc.gnu.org/PR14924 ! 139. https://gcc.gnu.org/PR14960 ! 140. https://gcc.gnu.org/PR15106 ! 141. https://gcc.gnu.org/PR16026 ! 142. https://gcc.gnu.org/PR15191 ! 143. https://gcc.gnu.org/PR15662 ! 144. https://gcc.gnu.org/PR15054 ! 145. https://gcc.gnu.org/PR15783 ! 146. https://gcc.gnu.org/PR15626 ! 147. https://gcc.gnu.org/PR14326 ! 148. https://gcc.gnu.org/PR14723 ! 149. https://gcc.gnu.org/PR15290 ! 150. https://gcc.gnu.org/PR15250 ! 151. https://gcc.gnu.org/PR15551 ! 152. https://gcc.gnu.org/PR8309 ! 153. https://gcc.gnu.org/PR13250 ! 154. https://gcc.gnu.org/PR13803 ! 155. https://gcc.gnu.org/PR14093 ! 156. https://gcc.gnu.org/PR14457 ! 157. https://gcc.gnu.org/PR14542 ! 158. https://gcc.gnu.org/PR15100 ! 159. https://gcc.gnu.org/PR15296 ! 160. https://gcc.gnu.org/PR15396 ! 161. https://gcc.gnu.org/PR15782 ! 162. https://gcc.gnu.org/PR11610 ! 163. https://gcc.gnu.org/PR15488 ! 164. https://gcc.gnu.org/PR15489 ! 165. https://gcc.gnu.org/PR13928 ! 166. https://gcc.gnu.org/PR14150 ! 167. https://gcc.gnu.org/PR14949 ! 168. https://gcc.gnu.org/PR15123 ! 169. https://gcc.gnu.org/PR16469 ! 170. https://gcc.gnu.org/PR16344 ! 171. https://gcc.gnu.org/PR16842 ! 172. https://gcc.gnu.org/PR12608 ! 173. https://gcc.gnu.org/PR14492 ! 174. https://gcc.gnu.org/PR15461 ! 175. https://gcc.gnu.org/PR15890 ! 176. https://gcc.gnu.org/PR16180 ! 177. https://gcc.gnu.org/PR16224 ! 178. https://gcc.gnu.org/PR16408 ! 179. https://gcc.gnu.org/PR16529 ! 180. https://gcc.gnu.org/PR16698 ! 181. https://gcc.gnu.org/PR16706 ! 182. https://gcc.gnu.org/PR16810 ! 183. https://gcc.gnu.org/PR16851 ! 184. https://gcc.gnu.org/PR16870 ! 185. https://gcc.gnu.org/PR16904 ! 186. https://gcc.gnu.org/PR16905 ! 187. https://gcc.gnu.org/PR16964 ! 188. https://gcc.gnu.org/PR17068 ! 189. https://gcc.gnu.org/PR16366 ! 190. https://gcc.gnu.org/PR15345 ! 191. https://gcc.gnu.org/PR16590 ! 192. https://gcc.gnu.org/PR16693 ! 193. https://gcc.gnu.org/PR17078 ! 194. https://gcc.gnu.org/PR13956 ! 195. https://gcc.gnu.org/PR16684 ! 196. https://gcc.gnu.org/PR12658 ! 197. https://gcc.gnu.org/PR13092 ! 198. https://gcc.gnu.org/PR15320 ! 199. https://gcc.gnu.org/PR16246 ! 200. https://gcc.gnu.org/PR16273 ! 201. https://gcc.gnu.org/PR16401 ! 202. https://gcc.gnu.org/PR16411 ! 203. https://gcc.gnu.org/PR16489 ! 204. https://gcc.gnu.org/PR16618 ! 205. https://gcc.gnu.org/PR16637 ! 206. https://gcc.gnu.org/PR16717 ! 207. https://gcc.gnu.org/PR16813 ! 208. https://gcc.gnu.org/PR16853 ! 209. https://gcc.gnu.org/PR16889 ! 210. https://gcc.gnu.org/PR16959 ! 211. https://gcc.gnu.org/PR7587 ! 212. https://gcc.gnu.org/PR16473 ! 213. https://gcc.gnu.org/PR16478 ! 214. https://gcc.gnu.org/PR10695 ! 215. https://gcc.gnu.org/PR16974 ! 216. https://gcc.gnu.org/PR16298 ! 217. https://gcc.gnu.org/PR17113 ! 218. https://gcc.gnu.org/PR14697 ! 219. https://gcc.gnu.org/PR15869 ! 220. https://gcc.gnu.org/PR16325 ! 221. https://gcc.gnu.org/PR16357 ! 222. https://gcc.gnu.org/PR16380 ! 223. https://gcc.gnu.org/PR16407 ! 224. https://gcc.gnu.org/PR16643 ! 225. https://gcc.gnu.org/PR15927 ! 226. https://gcc.gnu.org/PR15948 ! 227. https://gcc.gnu.org/PR17019 ! 228. https://gcc.gnu.org/PR16130 ! 229. https://gcc.gnu.org/PR16142 ! 230. https://gcc.gnu.org/PR16278 ! 231. https://gcc.gnu.org/PR16414 ! 232. https://gcc.gnu.org/PR16445 ! 233. https://gcc.gnu.org/PR16490 ! 234. https://gcc.gnu.org/PR16683 ! 235. https://gcc.gnu.org/PR16195 ! 236. https://gcc.gnu.org/PR16239 ! 237. https://gcc.gnu.org/PR16199 ! 238. https://gcc.gnu.org/PR16416 ! 239. https://gcc.gnu.org/PR16430 ! 240. https://gcc.gnu.org/PR16379 ! 241. https://gcc.gnu.org/PR17093 ! 242. https://gcc.gnu.org/PR17119 ! 243. https://gcc.gnu.org/PR15928 ! 244. https://gcc.gnu.org/PR16210 ! 245. https://gcc.gnu.org/PR15488 ! 246. https://gcc.gnu.org/PR16250 ! 247. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.3 ! 248. https://gcc.gnu.org/PR17369 ! 249. https://gcc.gnu.org/PR17850 ! 250. https://gcc.gnu.org/PR13948 ! 251. https://gcc.gnu.org/PR14492 ! 252. https://gcc.gnu.org/PR16301 ! 253. https://gcc.gnu.org/PR16566 ! 254. https://gcc.gnu.org/PR17023 ! 255. https://gcc.gnu.org/PR17027 ! 256. https://gcc.gnu.org/PR17524 ! 257. https://gcc.gnu.org/PR17826 ! 258. https://gcc.gnu.org/PR15526 ! 259. https://gcc.gnu.org/PR16999 ! 260. https://gcc.gnu.org/PR17503 ! 261. https://gcc.gnu.org/PR17581 ! 262. https://gcc.gnu.org/PR18129 ! 263. https://gcc.gnu.org/PR10975 ! 264. https://gcc.gnu.org/PR11722 ! 265. https://gcc.gnu.org/PR14534 ! 266. https://gcc.gnu.org/PR15172 ! 267. https://gcc.gnu.org/PR15786 ! 268. https://gcc.gnu.org/PR16162 ! 269. https://gcc.gnu.org/PR16612 ! 270. https://gcc.gnu.org/PR16715 ! 271. https://gcc.gnu.org/PR16848 ! 272. https://gcc.gnu.org/PR17132 ! 273. https://gcc.gnu.org/PR17259 ! 274. https://gcc.gnu.org/PR17327 ! 275. https://gcc.gnu.org/PR17393 ! 276. https://gcc.gnu.org/PR17501 ! 277. https://gcc.gnu.org/PR17537 ! 278. https://gcc.gnu.org/PR17585 ! 279. https://gcc.gnu.org/PR17821 ! 280. https://gcc.gnu.org/PR17829 ! 281. https://gcc.gnu.org/PR17851 ! 282. https://gcc.gnu.org/PR17976 ! 283. https://gcc.gnu.org/PR18020 ! 284. https://gcc.gnu.org/PR18093 ! 285. https://gcc.gnu.org/PR18140 ! 286. https://gcc.gnu.org/PR17541 ! 287. https://gcc.gnu.org/PR17853 ! 288. https://gcc.gnu.org/PR17245 ! 289. https://gcc.gnu.org/PR17167 ! 290. https://gcc.gnu.org/PR17277 ! 291. https://gcc.gnu.org/PR17505 ! 292. https://gcc.gnu.org/PR17684 ! 293. https://gcc.gnu.org/PR17384 ! 294. https://gcc.gnu.org/PR17770 ! 295. https://gcc.gnu.org/PR11476 ! 296. https://gcc.gnu.org/PR14064 ! 297. https://gcc.gnu.org/PR14678 ! 298. https://gcc.gnu.org/PR15583 ! 299. https://gcc.gnu.org/PR15790 ! 300. https://gcc.gnu.org/PR15886 ! 301. https://gcc.gnu.org/PR16884 ! 302. https://gcc.gnu.org/PR13841 ! 303. https://gcc.gnu.org/PR15860 ! 304. https://gcc.gnu.org/PR17465 ! 305. https://gcc.gnu.org/PR17469 ! 306. https://gcc.gnu.org/PR18138 ! 307. https://gcc.gnu.org/PR15498 ! 308. https://gcc.gnu.org/PR15747 ! 309. https://gcc.gnu.org/PR16406 ! 310. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.4 ! 311. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.5 ! 312. https://gcc.gnu.org/PR24688 ! 313. https://gcc.gnu.org/PR17188 ! 314. https://gcc.gnu.org/PR20187 ! 315. https://gcc.gnu.org/PR21873 ! 316. https://gcc.gnu.org/PR21899 ! 317. https://gcc.gnu.org/PR22061 ! 318. https://gcc.gnu.org/PR22208 ! 319. https://gcc.gnu.org/PR22458 ! 320. https://gcc.gnu.org/PR22589 ! 321. https://gcc.gnu.org/PR24101 ! 322. https://gcc.gnu.org/PR10611 ! 323. https://gcc.gnu.org/PR13377 ! 324. https://gcc.gnu.org/PR16002 ! 325. https://gcc.gnu.org/PR17413 ! 326. https://gcc.gnu.org/PR17609 ! 327. https://gcc.gnu.org/PR17618 ! 328. https://gcc.gnu.org/PR18124 ! 329. https://gcc.gnu.org/PR18155 ! 330. https://gcc.gnu.org/PR18177 ! 331. https://gcc.gnu.org/PR18368 ! 332. https://gcc.gnu.org/PR18378 ! 333. https://gcc.gnu.org/PR18466 ! 334. https://gcc.gnu.org/PR18512 ! 335. https://gcc.gnu.org/PR18545 ! 336. https://gcc.gnu.org/PR18738 ! 337. https://gcc.gnu.org/PR18803 ! 338. https://gcc.gnu.org/PR19004 ! 339. https://gcc.gnu.org/PR19208 ! 340. https://gcc.gnu.org/PR19253 ! 341. https://gcc.gnu.org/PR19608 ! 342. https://gcc.gnu.org/PR19884 ! 343. https://gcc.gnu.org/PR20153 ! 344. https://gcc.gnu.org/PR20563 ! 345. https://gcc.gnu.org/PR20789 ! 346. https://gcc.gnu.org/PR21336 ! 347. https://gcc.gnu.org/PR21768 ! 348. https://gcc.gnu.org/PR21853 ! 349. https://gcc.gnu.org/PR21903 ! 350. https://gcc.gnu.org/PR21983 ! 351. https://gcc.gnu.org/PR21987 ! 352. https://gcc.gnu.org/PR22153 ! 353. https://gcc.gnu.org/PR22172 ! 354. https://gcc.gnu.org/PR21286 ! 355. https://gcc.gnu.org/PR22233 ! 356. https://gcc.gnu.org/PR22508 ! 357. https://gcc.gnu.org/PR22545 ! 358. https://gcc.gnu.org/PR23528 ! 359. https://gcc.gnu.org/PR23550 ! 360. https://gcc.gnu.org/PR23586 ! 361. https://gcc.gnu.org/PR23624 ! 362. https://gcc.gnu.org/PR23639 ! 363. https://gcc.gnu.org/PR23797 ! 364. https://gcc.gnu.org/PR23965 ! 365. https://gcc.gnu.org/PR24052 ! 366. https://gcc.gnu.org/PR24580 ! 367. https://gcc.gnu.org/PR24267 ! 368. https://gcc.gnu.org/PR17810 ! 369. https://gcc.gnu.org/PR17860 ! 370. https://gcc.gnu.org/PR21709 ! 371. https://gcc.gnu.org/PR21964 ! 372. https://gcc.gnu.org/PR22167 ! 373. https://gcc.gnu.org/PR22619 ! 374. https://gcc.gnu.org/PR23241 ! 375. https://gcc.gnu.org/PR23478 ! 376. https://gcc.gnu.org/PR24470 ! 377. https://gcc.gnu.org/PR24950 ! 378. https://gcc.gnu.org/PR14400 ! 379. https://gcc.gnu.org/PR14940 ! 380. https://gcc.gnu.org/PR20239 ! 381. https://gcc.gnu.org/PR15220 ! 382. https://gcc.gnu.org/PR19275 ! 383. https://gcc.gnu.org/PR21888 ! 384. https://gcc.gnu.org/PR15342 ! 385. https://gcc.gnu.org/PR23985 ! 386. https://gcc.gnu.org/PR16719 ! 387. https://gcc.gnu.org/PR21723 ! 388. https://gcc.gnu.org/PR21841 ! 389. https://gcc.gnu.org/PR23644 ! 390. https://gcc.gnu.org/PR24718 ! 391. https://gcc.gnu.org/PR18421 ! 392. https://gcc.gnu.org/PR20621 ! 393. https://gcc.gnu.org/PR18583 ! 394. https://gcc.gnu.org/PR20191 ! 395. https://gcc.gnu.org/PR22083 ! 396. https://gcc.gnu.org/PR23070 ! 397. https://gcc.gnu.org/PR23404 ! 398. https://gcc.gnu.org/PR23539 ! 399. https://gcc.gnu.org/PR24102 ! 400. https://gcc.gnu.org/PR24465 ! 401. https://gcc.gnu.org/PR19933 ! 402. https://gcc.gnu.org/PR21889 ! 403. https://gcc.gnu.org/PR19300 ! 404. https://gcc.gnu.org/PR20301 ! 405. https://gcc.gnu.org/PR20673 ! 406. https://gcc.gnu.org/PR18582 ! 407. https://gcc.gnu.org/PR19340 ! 408. https://gcc.gnu.org/PR21716 ! 409. https://gcc.gnu.org/PR24315 ! 410. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.6 ! 411. https://gcc.gnu.org/onlinedocs/ ! 412. mailto:gcc-help@gcc.gnu.org ! 413. mailto:gcc@gcc.gnu.org ! 414. https://gcc.gnu.org/lists.html ! 415. http://www.fsf.org/ ! 416. https://gcc.gnu.org/about.html ! 417. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.3/index.html + GCC 3.3 Release Series May 03, 2005 *************** References *** 11838,11843 **** --- 11903,11909 ---- 22. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.3/changes.html + GCC 3.3 Release Series Changes, New Features, and Fixes *************** References *** 13748,13753 **** --- 13814,13820 ---- 557. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.2/index.html + GCC 3.2 Release Series April 25, 2003 *************** References *** 13839,13844 **** --- 13906,13912 ---- 18. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.2/changes.html + GCC 3.2 Release Series Changes, New Features, and Fixes *************** References *** 14696,14701 **** --- 14764,14770 ---- 252. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.1/index.html + GCC 3.1 July 27, 2002 *************** References *** 14764,14769 **** --- 14833,14839 ---- 15. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.1/changes.html + GCC 3.1 Release Series Changes, New Features, and Fixes *************** New Targets and Target Specific Improvem *** 14956,14964 **** * Hans-Peter Nilsson has contributed a port to [8]MMIX, the CPU architecture used in new editions of Donald E. Knuth's The Art of Computer Programming. ! * [9]Axis Communications has contributed its port to the CRIS CPU ! architecture, used in the ETRAX system-on-a-chip series. See ! [10]Axis' developer site for technical information. * Alexandre Oliva, of Red Hat, has contributed a port to the SuperH SH5 64-bit RISC microprocessor architecture, extending the existing SH port. --- 15026,15033 ---- * Hans-Peter Nilsson has contributed a port to [8]MMIX, the CPU architecture used in new editions of Donald E. Knuth's The Art of Computer Programming. ! * Axis Communications has contributed its port to the CRIS CPU ! architecture, used in the ETRAX system-on-a-chip series. * Alexandre Oliva, of Red Hat, has contributed a port to the SuperH SH5 64-bit RISC microprocessor architecture, extending the existing SH port. *************** New Targets and Target Specific Improvem *** 14969,14975 **** * The x86 back end has had some noticeable work done to it. + SuSE Labs developers Jan Hubicka, Bo Thorsen and Andreas Jaeger have contributed a port to the AMD x86-64 architecture. ! For more information on x86-64 see [11]http://www.x86-64.org. + The compiler now supports MMX, 3DNow!, SSE, and SSE2 instructions. Options -mmmx, -m3dnow, -msse, and -msse2 will enable the respective instruction sets. Intel C++ compatible --- 15038,15044 ---- * The x86 back end has had some noticeable work done to it. + SuSE Labs developers Jan Hubicka, Bo Thorsen and Andreas Jaeger have contributed a port to the AMD x86-64 architecture. ! For more information on x86-64 see http://www.x86-64.org. + The compiler now supports MMX, 3DNow!, SSE, and SSE2 instructions. Options -mmmx, -m3dnow, -msse, and -msse2 will enable the respective instruction sets. Intel C++ compatible *************** New Targets and Target Specific Improvem *** 14982,14988 **** + For those targets that support it, -mfpmath=sse will cause the compiler to generate SSE/SSE2 instructions for floating point math instead of x87 instructions. Usually, this will lead to ! quicker code — especially on the Pentium 4. Note that only scalar floating point instructions are used and GCC does not exploit SIMD features yet. + Prefetch support has been added to the Pentium III, Pentium 4, --- 15051,15057 ---- + For those targets that support it, -mfpmath=sse will cause the compiler to generate SSE/SSE2 instructions for floating point math instead of x87 instructions. Usually, this will lead to ! quicker code -- especially on the Pentium 4. Note that only scalar floating point instructions are used and GCC does not exploit SIMD features yet. + Prefetch support has been added to the Pentium III, Pentium 4, *************** Documentation improvements *** 15087,15104 **** For questions related to the use of GCC, please consult these web ! pages and the [12]GCC manuals. If that fails, the ! [13]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 [14]gcc@gcc.gnu.org. All of [15]our lists have public archives. ! Copyright (C) [16]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [17]maintained by the GCC team. Last modified ! 2016-08-22[18]. References --- 15156,15173 ---- For questions related to the use of GCC, please consult these web ! pages and the [9]GCC manuals. If that fails, the ! [10]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 [11]gcc@gcc.gnu.org. All of [12]our lists have public archives. ! Copyright (C) [13]Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! These pages are [14]maintained by the GCC team. Last modified ! 2017-01-29[15]. References *************** References *** 15110,15127 **** 6. https://gcc.gnu.org/onlinedocs/gcc-3.1.1/g77/News.html 7. http://www.adacore.com/ 8. http://www-cs-faculty.stanford.edu/~uno/mmix.html ! 9. http://www.axis.com/ ! 10. http://developer.axis.com/ ! 11. http://www.x86-64.org/ ! 12. https://gcc.gnu.org/onlinedocs/ ! 13. mailto:gcc-help@gcc.gnu.org ! 14. mailto:gcc@gcc.gnu.org ! 15. https://gcc.gnu.org/lists.html ! 16. http://www.fsf.org/ ! 17. https://gcc.gnu.org/about.html ! 18. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.0/index.html GCC 3.0.4 February 20, 2002 --- 15179,15194 ---- 6. https://gcc.gnu.org/onlinedocs/gcc-3.1.1/g77/News.html 7. http://www.adacore.com/ 8. http://www-cs-faculty.stanford.edu/~uno/mmix.html ! 9. https://gcc.gnu.org/onlinedocs/ ! 10. mailto:gcc-help@gcc.gnu.org ! 11. mailto:gcc@gcc.gnu.org ! 12. https://gcc.gnu.org/lists.html ! 13. http://www.fsf.org/ ! 14. https://gcc.gnu.org/about.html ! 15. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.0/index.html + GCC 3.0.4 February 20, 2002 *************** References *** 15197,15202 **** --- 15264,15270 ---- 15. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.0/features.html + GCC 3.0 New Features Additional changes in GCC 3.0.4 *************** References *** 15392,15397 **** --- 15460,15466 ---- 19. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.0/caveats.html + GCC 3.0 Caveats * -fstrict-aliasing is now part of -O2 and higher optimization *************** References *** 15452,15457 **** --- 15521,15527 ---- 8. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-2.95/index.html + GCC 2.95 March 16, 2001: The GNU project and the GCC developers are pleased to *************** References *** 15542,15547 **** --- 15612,15618 ---- 16. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-2.95/features.html + GCC 2.95 New Features * General Optimizer Improvements: *************** http://gcc.gnu.org/gcc-2.95/features.htm *** 15562,15569 **** * New Languages and Language specific improvements + [8]Many C++ improvements. + [9]Many Fortran improvements. ! + [10]Java front-end has been integrated. [11]runtime library is ! available separately. + [12]ISO C99 support + [13]Chill front-end and runtime has been integrated. + Boehm garbage collector support in libobjc. --- 15633,15640 ---- * New Languages and Language specific improvements + [8]Many C++ improvements. + [9]Many Fortran improvements. ! + [10]Java front-end has been integrated. A [11]runtime library ! is available separately. + [12]ISO C99 support + [13]Chill front-end and runtime has been integrated. + Boehm garbage collector support in libobjc. *************** Additional Changes in GCC 2.95.3 *** 15785,15791 **** provided this notice is preserved. These pages are [22]maintained by the GCC team. Last modified ! 2016-01-30[23]. References --- 15856,15862 ---- provided this notice is preserved. These pages are [22]maintained by the GCC team. Last modified ! 2016-12-29[23]. References *************** References *** 15798,15804 **** 7. http://gcc.gnu.org/news/alias.html 8. http://gcc.gnu.org/gcc-2.95/c++features.html 9. https://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/News.html ! 10. http://gcc.gnu.org/java/gcj-announce.txt 11. http://gcc.gnu.org/news/javaannounce.html 12. http://gcc.gnu.org/c99status.html 13. http://gcc.gnu.org/news/chill.html --- 15869,15875 ---- 7. http://gcc.gnu.org/news/alias.html 8. http://gcc.gnu.org/gcc-2.95/c++features.html 9. https://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/News.html ! 10. http://gcc.gnu.org/news/gcj-announce.txt 11. http://gcc.gnu.org/news/javaannounce.html 12. http://gcc.gnu.org/c99status.html 13. http://gcc.gnu.org/news/chill.html *************** References *** 15814,15819 **** --- 15885,15891 ---- 23. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-2.95/caveats.html + GCC 2.95 Caveats * GCC 2.95 will issue an error for invalid asm statements that had *************** References *** 15882,15887 **** --- 15954,15960 ---- 8. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/egcs-1.1/index.html + EGCS 1.1 September 3, 1998: We are pleased to announce the release of EGCS 1.1. *************** References *** 16111,16116 **** --- 16184,16190 ---- 16. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/egcs-1.1/features.html + EGCS 1.1 new features * Integrated GNU Fortran (g77) compiler and runtime library with *************** References *** 16205,16210 **** --- 16279,16285 ---- 11. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/egcs-1.1/caveats.html + EGCS 1.1 Caveats * EGCS has an integrated libstdc++, but does not have an integrated *************** References *** 16255,16260 **** --- 16330,16336 ---- 7. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/egcs-1.0/index.html + EGCS 1.0 December 3, 1997: We are pleased to announce the release of EGCS 1.0. *************** References *** 16455,16460 **** --- 16531,16537 ---- 11. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/egcs-1.0/features.html + EGCS 1.0 features * Core compiler is based on the gcc2 development tree from Aug 2, *************** References *** 16519,16524 **** --- 16596,16602 ---- 9. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/egcs-1.0/caveats.html + EGCS 1.0 Caveats * EGCS has an integrated libstdc++, but does not have an integrated diff -Nrcpad gcc-6.3.0/boehm-gc/ChangeLog gcc-6.4.0/boehm-gc/ChangeLog *** gcc-6.3.0/boehm-gc/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/boehm-gc/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/config/ChangeLog gcc-6.4.0/config/ChangeLog *** gcc-6.3.0/config/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/config/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,12 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-01-24 Uros Bizjak + + PR target/78478 + * ax_check_define.m4: New file. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/config/ax_check_define.m4 gcc-6.4.0/config/ax_check_define.m4 *** gcc-6.3.0/config/ax_check_define.m4 Thu Jan 1 00:00:00 1970 --- gcc-6.4.0/config/ax_check_define.m4 Tue Jan 24 10:54:56 2017 *************** *** 0 **** --- 1,92 ---- + # =========================================================================== + # http://www.gnu.org/software/autoconf-archive/ax_check_define.html + # =========================================================================== + # + # SYNOPSIS + # + # AC_CHECK_DEFINE([symbol], [ACTION-IF-FOUND], [ACTION-IF-NOT]) + # AX_CHECK_DEFINE([includes],[symbol], [ACTION-IF-FOUND], [ACTION-IF-NOT]) + # + # DESCRIPTION + # + # Complements AC_CHECK_FUNC but it does not check for a function but for a + # define to exist. Consider a usage like: + # + # AC_CHECK_DEFINE(__STRICT_ANSI__, CFLAGS="$CFLAGS -D_XOPEN_SOURCE=500") + # + # LICENSE + # + # Copyright (c) 2008 Guido U. Draheim + # + # This program is free software; you can redistribute it and/or modify it + # under the terms of the GNU General Public License as published by the + # Free Software Foundation; either version 3 of the License, or (at your + # option) any later version. + # + # This program is distributed in the hope that it will be useful, but + # WITHOUT ANY WARRANTY; without even the implied warranty of + # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General + # Public License for more details. + # + # You should have received a copy of the GNU General Public License along + # with this program. If not, see . + # + # As a special exception, the respective Autoconf Macro's copyright owner + # gives unlimited permission to copy, distribute and modify the configure + # scripts that are the output of Autoconf when processing the Macro. You + # need not follow the terms of the GNU General Public License when using + # or distributing such scripts, even though portions of the text of the + # Macro appear in them. The GNU General Public License (GPL) does govern + # all other use of the material that constitutes the Autoconf Macro. + # + # This special exception to the GPL applies to versions of the Autoconf + # Macro released by the Autoconf Archive. When you make and distribute a + # modified version of the Autoconf Macro, you may extend this special + # exception to the GPL to apply to your modified version as well. + + #serial 8 + + AU_ALIAS([AC_CHECK_DEFINED], [AC_CHECK_DEFINE]) + AC_DEFUN([AC_CHECK_DEFINE],[ + AS_VAR_PUSHDEF([ac_var],[ac_cv_defined_$1])dnl + AC_CACHE_CHECK([for $1 defined], ac_var, + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]], [[ + #ifdef $1 + int ok; + #else + choke me + #endif + ]])],[AS_VAR_SET(ac_var, yes)],[AS_VAR_SET(ac_var, no)])) + AS_IF([test AS_VAR_GET(ac_var) != "no"], [$2], [$3])dnl + AS_VAR_POPDEF([ac_var])dnl + ]) + + AU_ALIAS([AX_CHECK_DEFINED], [AX_CHECK_DEFINE]) + AC_DEFUN([AX_CHECK_DEFINE],[ + AS_VAR_PUSHDEF([ac_var],[ac_cv_defined_$2_$1])dnl + AC_CACHE_CHECK([for $2 defined in $1], ac_var, + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include <$1>]], [[ + #ifdef $2 + int ok; + #else + choke me + #endif + ]])],[AS_VAR_SET(ac_var, yes)],[AS_VAR_SET(ac_var, no)])) + AS_IF([test AS_VAR_GET(ac_var) != "no"], [$3], [$4])dnl + AS_VAR_POPDEF([ac_var])dnl + ]) + + AC_DEFUN([AX_CHECK_FUNC], + [AS_VAR_PUSHDEF([ac_var], [ac_cv_func_$2])dnl + AC_CACHE_CHECK([for $2], ac_var, + dnl AC_LANG_FUNC_LINK_TRY + [AC_LINK_IFELSE([AC_LANG_PROGRAM([$1 + #undef $2 + char $2 ();],[ + char (*f) () = $2; + return f != $2; ])], + [AS_VAR_SET(ac_var, yes)], + [AS_VAR_SET(ac_var, no)])]) + AS_IF([test AS_VAR_GET(ac_var) = yes], [$3], [$4])dnl + AS_VAR_POPDEF([ac_var])dnl + ])# AC_CHECK_FUNC diff -Nrcpad gcc-6.3.0/configure gcc-6.4.0/configure *** gcc-6.3.0/configure Thu Mar 17 22:54:19 2016 --- gcc-6.4.0/configure Mon Jan 9 21:01:26 2017 *************** case "${target}" in *** 3483,3488 **** --- 3483,3491 ---- *-*-vxworks*) noconfigdirs="$noconfigdirs ${libgcj}" ;; + aarch64*-*-freebsd*) + noconfigdirs="$noconfigdirs ${libgcj}" + ;; alpha*-*-*vms*) noconfigdirs="$noconfigdirs ${libgcj}" ;; diff -Nrcpad gcc-6.3.0/configure.ac gcc-6.4.0/configure.ac *** gcc-6.3.0/configure.ac Thu Mar 17 22:54:19 2016 --- gcc-6.4.0/configure.ac Mon Jan 9 21:01:26 2017 *************** case "${target}" in *** 819,824 **** --- 819,827 ---- *-*-vxworks*) noconfigdirs="$noconfigdirs ${libgcj}" ;; + aarch64*-*-freebsd*) + noconfigdirs="$noconfigdirs ${libgcj}" + ;; alpha*-*-*vms*) noconfigdirs="$noconfigdirs ${libgcj}" ;; diff -Nrcpad gcc-6.3.0/contrib/ChangeLog gcc-6.4.0/contrib/ChangeLog *** gcc-6.3.0/contrib/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/contrib/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/contrib/header-tools/ChangeLog gcc-6.4.0/contrib/header-tools/ChangeLog *** gcc-6.3.0/contrib/header-tools/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/contrib/header-tools/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/contrib/reghunt/ChangeLog gcc-6.4.0/contrib/reghunt/ChangeLog *** gcc-6.3.0/contrib/reghunt/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/contrib/reghunt/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/contrib/regression/ChangeLog gcc-6.4.0/contrib/regression/ChangeLog *** gcc-6.3.0/contrib/regression/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/contrib/regression/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/fixincludes/ChangeLog gcc-6.4.0/fixincludes/ChangeLog *** gcc-6.3.0/fixincludes/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/fixincludes/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,20 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-01-30 Rainer Orth + + Backport from mainline + 2017-01-13 Rainer Orth + + PR libstdc++/78979 + * inclhack.def (solaris_gets_c11, solaris_gets_cxx14) + (solaris_std_gets_cxx14, solaris_stdlib_noreturn): New fixes. + * fixincl.x: Regenerate. + * tests/base/iso/stdio_iso.h [SOLARIS_GETS_C11_CHECK, + SOLARIS_GETS_CXX14_CHECK, SOLARIS_STD_GETS_CXX14_CHECK, + SOLARIS_STDLIB_NORETURN_CHECK]: New tests. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/fixincludes/fixincl.x gcc-6.4.0/fixincludes/fixincl.x *** gcc-6.3.0/fixincludes/fixincl.x Thu Dec 1 15:02:37 2016 --- gcc-6.4.0/fixincludes/fixincl.x Mon Jan 30 16:01:11 2017 *************** *** 2,12 **** * * DO NOT EDIT THIS FILE (fixincl.x) * ! * It has been AutoGen-ed November 18, 2016 at 12:35:01 PM by AutoGen 5.16.2 * From the definitions inclhack.def * and the template file fixincl */ ! /* DO NOT SVN-MERGE THIS FILE, EITHER Fri Nov 18 12:35:01 2016 * * You must regenerate it. Use the ./genfixes script. * --- 2,12 ---- * * DO NOT EDIT THIS FILE (fixincl.x) * ! * It has been AutoGen-ed January 5, 2017 at 06:03:22 PM by AutoGen 5.16.2 * From the definitions inclhack.def * and the template file fixincl */ ! /* DO NOT SVN-MERGE THIS FILE, EITHER Thu Jan 5 18:03:22 CET 2017 * * You must regenerate it. Use the ./genfixes script. * *************** *** 15,21 **** * certain ANSI-incompatible system header files which are fixed to work * correctly with ANSI C and placed in a directory that GNU C will search. * ! * This file contains 236 fixup descriptions. * * See README for more information. * --- 15,21 ---- * certain ANSI-incompatible system header files which are fixed to work * correctly with ANSI C and placed in a directory that GNU C will search. * ! * This file contains 240 fixup descriptions. * * See README for more information. * *************** static const char* apzSolaris_Getc_Stric *** 6824,6829 **** --- 6824,6907 ---- /* * * * * * * * * * * * * * * * * * * * * * * * * * * + * Description of Solaris_Gets_C11 fix + */ + tSCC zSolaris_Gets_C11Name[] = + "solaris_gets_c11"; + + /* + * File name selection pattern + */ + tSCC zSolaris_Gets_C11List[] = + "iso/stdio_iso.h\0"; + /* + * Machine/OS name selection pattern + */ + tSCC* apzSolaris_Gets_C11Machs[] = { + "*-*-solaris2*", + (const char*)NULL }; + + /* + * content selection pattern - do fix if pattern found + */ + tSCC zSolaris_Gets_C11Select0[] = + "(extern char[ \t]*\\*gets\\(char \\*\\));"; + + #define SOLARIS_GETS_C11_TEST_CT 1 + static tTestDesc aSolaris_Gets_C11Tests[] = { + { TT_EGREP, zSolaris_Gets_C11Select0, (regex_t*)NULL }, }; + + /* + * Fix Command Arguments for Solaris_Gets_C11 + */ + static const char* apzSolaris_Gets_C11Patch[] = { + "format", + "#if __STDC_VERSION__ < 201112L && __cplusplus < 201402L\n\ + %1 __attribute__((__deprecated__));\n\ + #endif", + (char*)NULL }; + + /* * * * * * * * * * * * * * * * * * * * * * * * * * + * + * Description of Solaris_Gets_Cxx14 fix + */ + tSCC zSolaris_Gets_Cxx14Name[] = + "solaris_gets_cxx14"; + + /* + * File name selection pattern + */ + tSCC zSolaris_Gets_Cxx14List[] = + "iso/stdio_iso.h\0"; + /* + * Machine/OS name selection pattern + */ + tSCC* apzSolaris_Gets_Cxx14Machs[] = { + "*-*-solaris2*", + (const char*)NULL }; + + /* + * content selection pattern - do fix if pattern found + */ + tSCC zSolaris_Gets_Cxx14Select0[] = + "(#if __STDC_VERSION__ < 201112L)\n\ + (extern char\t\\*gets\\(char \\*\\) __ATTR_DEPRECATED;)"; + + #define SOLARIS_GETS_CXX14_TEST_CT 1 + static tTestDesc aSolaris_Gets_Cxx14Tests[] = { + { TT_EGREP, zSolaris_Gets_Cxx14Select0, (regex_t*)NULL }, }; + + /* + * Fix Command Arguments for Solaris_Gets_Cxx14 + */ + static const char* apzSolaris_Gets_Cxx14Patch[] = { + "format", + "%1 && __cplusplus < 201402L\n\ + %2", + (char*)NULL }; + + /* * * * * * * * * * * * * * * * * * * * * * * * * * + * * Description of Solaris_Int_Const fix */ tSCC zSolaris_Int_ConstName[] = *************** using std::__flsbuf;\n\ *** 7576,7581 **** --- 7654,7698 ---- /* * * * * * * * * * * * * * * * * * * * * * * * * * * + * Description of Solaris_Std_Gets_Cxx14 fix + */ + tSCC zSolaris_Std_Gets_Cxx14Name[] = + "solaris_std_gets_cxx14"; + + /* + * File name selection pattern + */ + tSCC zSolaris_Std_Gets_Cxx14List[] = + "stdio.h\0"; + /* + * Machine/OS name selection pattern + */ + tSCC* apzSolaris_Std_Gets_Cxx14Machs[] = { + "*-*-solaris2*", + (const char*)NULL }; + + /* + * content selection pattern - do fix if pattern found + */ + tSCC zSolaris_Std_Gets_Cxx14Select0[] = + "using std::gets;"; + + #define SOLARIS_STD_GETS_CXX14_TEST_CT 1 + static tTestDesc aSolaris_Std_Gets_Cxx14Tests[] = { + { TT_EGREP, zSolaris_Std_Gets_Cxx14Select0, (regex_t*)NULL }, }; + + /* + * Fix Command Arguments for Solaris_Std_Gets_Cxx14 + */ + static const char* apzSolaris_Std_Gets_Cxx14Patch[] = { + "format", + "#if __cplusplus < 201402L\n\ + %0\n\ + #endif", + (char*)NULL }; + + /* * * * * * * * * * * * * * * * * * * * * * * * * * + * * Description of Solaris_Stdio_Tag fix */ tSCC zSolaris_Stdio_TagName[] = *************** static const char* apzSolaris_Stdio_TagP *** 7617,7622 **** --- 7734,7776 ---- /* * * * * * * * * * * * * * * * * * * * * * * * * * * + * Description of Solaris_Stdlib_Noreturn fix + */ + tSCC zSolaris_Stdlib_NoreturnName[] = + "solaris_stdlib_noreturn"; + + /* + * File name selection pattern + */ + tSCC zSolaris_Stdlib_NoreturnList[] = + "iso/stdlib_c99.h\0"; + /* + * Machine/OS name selection pattern + */ + tSCC* apzSolaris_Stdlib_NoreturnMachs[] = { + "*-*-solaris2*", + (const char*)NULL }; + + /* + * content selection pattern - do fix if pattern found + */ + tSCC zSolaris_Stdlib_NoreturnSelect0[] = + "(extern) _Noreturn (void quick_exit\\(int\\));"; + + #define SOLARIS_STDLIB_NORETURN_TEST_CT 1 + static tTestDesc aSolaris_Stdlib_NoreturnTests[] = { + { TT_EGREP, zSolaris_Stdlib_NoreturnSelect0, (regex_t*)NULL }, }; + + /* + * Fix Command Arguments for Solaris_Stdlib_Noreturn + */ + static const char* apzSolaris_Stdlib_NoreturnPatch[] = { + "format", + "%1 %2 __attribute__((__noreturn__));", + (char*)NULL }; + + /* * * * * * * * * * * * * * * * * * * * * * * * * * + * * Description of Statsswtch fix */ tSCC zStatsswtchName[] = *************** static const char* apzX11_SprintfPatch[] *** 9664,9672 **** * * List of all fixes */ ! #define REGEX_COUNT 272 #define MACH_LIST_SIZE_LIMIT 187 ! #define FIX_COUNT 236 /* * Enumerate the fixes --- 9818,9826 ---- * * List of all fixes */ ! #define REGEX_COUNT 276 #define MACH_LIST_SIZE_LIMIT 187 ! #define FIX_COUNT 240 /* * Enumerate the fixes *************** typedef enum { *** 9837,9842 **** --- 9991,9998 ---- SOLARIS_COMPLEX_CXX_FIXIDX, SOLARIS_CXX_LINKAGE_FIXIDX, SOLARIS_GETC_STRICT_STDC_FIXIDX, + SOLARIS_GETS_C11_FIXIDX, + SOLARIS_GETS_CXX14_FIXIDX, SOLARIS_INT_CONST_FIXIDX, SOLARIS_INT_LIMITS_1_FIXIDX, SOLARIS_INT_LIMITS_2_FIXIDX, *************** typedef enum { *** 9855,9861 **** --- 10011,10019 ---- SOLARIS_POW_INT_OVERLOAD_FIXIDX, SOLARIS_RWLOCK_INIT_1_FIXIDX, SOLARIS_STD___FILBUF_FIXIDX, + SOLARIS_STD_GETS_CXX14_FIXIDX, SOLARIS_STDIO_TAG_FIXIDX, + SOLARIS_STDLIB_NORETURN_FIXIDX, STATSSWTCH_FIXIDX, STDIO_STDARG_H_FIXIDX, STDIO_VA_LIST_FIXIDX, *************** tFixDesc fixDescList[ FIX_COUNT ] = { *** 10736,10741 **** --- 10894,10909 ---- SOLARIS_GETC_STRICT_STDC_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, aSolaris_Getc_Strict_StdcTests, apzSolaris_Getc_Strict_StdcPatch, 0 }, + { zSolaris_Gets_C11Name, zSolaris_Gets_C11List, + apzSolaris_Gets_C11Machs, + SOLARIS_GETS_C11_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, + aSolaris_Gets_C11Tests, apzSolaris_Gets_C11Patch, 0 }, + + { zSolaris_Gets_Cxx14Name, zSolaris_Gets_Cxx14List, + apzSolaris_Gets_Cxx14Machs, + SOLARIS_GETS_CXX14_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, + aSolaris_Gets_Cxx14Tests, apzSolaris_Gets_Cxx14Patch, 0 }, + { zSolaris_Int_ConstName, zSolaris_Int_ConstList, apzSolaris_Int_ConstMachs, SOLARIS_INT_CONST_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, *************** tFixDesc fixDescList[ FIX_COUNT ] = { *** 10826,10836 **** --- 10994,11014 ---- SOLARIS_STD___FILBUF_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, aSolaris_Std___FilbufTests, apzSolaris_Std___FilbufPatch, 0 }, + { zSolaris_Std_Gets_Cxx14Name, zSolaris_Std_Gets_Cxx14List, + apzSolaris_Std_Gets_Cxx14Machs, + SOLARIS_STD_GETS_CXX14_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, + aSolaris_Std_Gets_Cxx14Tests, apzSolaris_Std_Gets_Cxx14Patch, 0 }, + { zSolaris_Stdio_TagName, zSolaris_Stdio_TagList, apzSolaris_Stdio_TagMachs, SOLARIS_STDIO_TAG_TEST_CT, FD_MACH_ONLY, aSolaris_Stdio_TagTests, apzSolaris_Stdio_TagPatch, 0 }, + { zSolaris_Stdlib_NoreturnName, zSolaris_Stdlib_NoreturnList, + apzSolaris_Stdlib_NoreturnMachs, + SOLARIS_STDLIB_NORETURN_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, + aSolaris_Stdlib_NoreturnTests, apzSolaris_Stdlib_NoreturnPatch, 0 }, + { zStatsswtchName, zStatsswtchList, apzStatsswtchMachs, STATSSWTCH_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE, diff -Nrcpad gcc-6.3.0/fixincludes/inclhack.def gcc-6.4.0/fixincludes/inclhack.def *** gcc-6.3.0/fixincludes/inclhack.def Thu Dec 1 15:02:37 2016 --- gcc-6.4.0/fixincludes/inclhack.def Mon Jan 30 16:01:11 2017 *************** fix = { *** 3482,3487 **** --- 3482,3524 ---- }; /* + * Solaris should deprecate gets before C11. + */ + fix = { + hackname = solaris_gets_c11; + mach = "*-*-solaris2*"; + files = "iso/stdio_iso.h"; + select = "(extern char[ \t]*\\*gets\\(char \\*\\));"; + + c_fix = format; + c_fix_arg = "#if __STDC_VERSION__ < 201112L && __cplusplus < 201402L\n" + "%1 __attribute__((__deprecated__));\n" + "#endif"; + + test_text = "extern char *gets(char *);"; + }; + + /* + * Solaris shouldn't declare gets for C++14. + */ + fix = { + hackname = solaris_gets_cxx14; + mach = "*-*-solaris2*"; + files = "iso/stdio_iso.h"; + select = <<- _EOSelect_ + (#if __STDC_VERSION__ < 201112L) + (extern char \*gets\(char \*\) __ATTR_DEPRECATED;) + _EOSelect_; + c_fix = format; + c_fix_arg = "%1 && __cplusplus < 201402L\n%2"; + + test_text = <<- _EOText_ + #if __STDC_VERSION__ < 201112L + extern char *gets(char *) __ATTR_DEPRECATED; + _EOText_; + }; + + /* * Sun Solaris 2 has a version of sys/int_const.h that defines * UINT8_C and UINT16_C to unsigned constants. */ *************** fix = { *** 3871,3876 **** --- 3908,3928 ---- }; /* + * Solaris shouldn't use std::gets for C++14. + */ + fix = { + hackname = solaris_std_gets_cxx14; + mach = "*-*-solaris2*"; + files = "stdio.h"; + select = "using std::gets;"; + + c_fix = format; + c_fix_arg = "#if __cplusplus < 201402L\n%0\n#endif"; + + test_text = "using std::gets;"; + }; + + /* * Sun Solaris 8 has what appears to be some gross workaround for * some old version of their c++ compiler. G++ doesn't want it * either, but doesn't want to be tied to SunPRO version numbers. *************** fix = { *** 3889,3894 **** --- 3941,3961 ---- }; /* + * Solaris shouldn't use _Noreturn, breaks with C++. + */ + fix = { + hackname = solaris_stdlib_noreturn; + mach = "*-*-solaris2*"; + files = "iso/stdlib_c99.h"; + select = "(extern) _Noreturn (void quick_exit\\(int\\));"; + + c_fix = format; + c_fix_arg = "%1 %2 __attribute__((__noreturn__));"; + + test_text = "extern _Noreturn void quick_exit(int);"; + }; + + /* * a missing semi-colon at the end of the statsswtch structure definition. */ fix = { diff -Nrcpad gcc-6.3.0/fixincludes/tests/base/iso/stdio_iso.h gcc-6.4.0/fixincludes/tests/base/iso/stdio_iso.h *** gcc-6.3.0/fixincludes/tests/base/iso/stdio_iso.h Wed Aug 10 08:43:38 2011 --- gcc-6.4.0/fixincludes/tests/base/iso/stdio_iso.h Mon Jan 30 16:01:11 2017 *************** *** 12,14 **** --- 12,27 ---- #if defined( SOLARIS_GETC_STRICT_STDC_CHECK ) #if !defined(_REENTRANT) && !defined(_LP64) && (!defined(_STRICT_STDC) || (__cplusplus >= 199711L)) #endif /* SOLARIS_GETC_STRICT_STDC_CHECK */ + + + #if defined( SOLARIS_GETS_C11_CHECK ) + #if __STDC_VERSION__ < 201112L && __cplusplus < 201402L + extern char *gets(char *) __attribute__((__deprecated__)); + #endif + #endif /* SOLARIS_GETS_C11_CHECK */ + + + #if defined( SOLARIS_GETS_CXX14_CHECK ) + #if __STDC_VERSION__ < 201112L && __cplusplus < 201402L + extern char *gets(char *) __ATTR_DEPRECATED; + #endif /* SOLARIS_GETS_CXX14_CHECK */ diff -Nrcpad gcc-6.3.0/fixincludes/tests/base/iso/stdlib_c99.h gcc-6.4.0/fixincludes/tests/base/iso/stdlib_c99.h *** gcc-6.3.0/fixincludes/tests/base/iso/stdlib_c99.h Thu Jan 1 00:00:00 1970 --- gcc-6.4.0/fixincludes/tests/base/iso/stdlib_c99.h Mon Jan 30 16:01:11 2017 *************** *** 0 **** --- 1,14 ---- + /* DO NOT EDIT THIS FILE. + + It has been auto-edited by fixincludes from: + + "fixinc/tests/inc/iso/stdlib_c99.h" + + This had to be done to correct non-standard usages in the + original, manufacturer supplied header file. */ + + + + #if defined( SOLARIS_STDLIB_NORETURN_CHECK ) + extern void quick_exit(int) __attribute__((__noreturn__)); + #endif /* SOLARIS_STDLIB_NORETURN_CHECK */ diff -Nrcpad gcc-6.3.0/fixincludes/tests/base/stdio.h gcc-6.4.0/fixincludes/tests/base/stdio.h *** gcc-6.3.0/fixincludes/tests/base/stdio.h Mon Feb 1 00:54:22 2016 --- gcc-6.4.0/fixincludes/tests/base/stdio.h Mon Jan 30 16:01:11 2017 *************** using std::__flsbuf; *** 90,95 **** --- 90,102 ---- #endif /* SOLARIS_STD___FILBUF_CHECK */ + #if defined( SOLARIS_STD_GETS_CXX14_CHECK ) + #if __cplusplus < 201402L + using std::gets; + #endif + #endif /* SOLARIS_STD_GETS_CXX14_CHECK */ + + #if defined( STDIO_STDARG_H_CHECK ) #endif /* STDIO_STDARG_H_CHECK */ diff -Nrcpad gcc-6.3.0/gcc/BASE-VER gcc-6.4.0/gcc/BASE-VER *** gcc-6.3.0/gcc/BASE-VER Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/BASE-VER Tue Jul 4 07:22:46 2017 *************** *** 1 **** ! 6.3.0 --- 1 ---- ! 6.4.0 diff -Nrcpad gcc-6.3.0/gcc/ChangeLog gcc-6.4.0/gcc/ChangeLog *** gcc-6.3.0/gcc/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,2415 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-07-03 Segher Boessenkool + + Backport from trunk: + + 2017-06-15 Segher Boessenkool + + * config/rs6000/rs6000.md (add3): Use reg_or_subregno instead + of REGNO. + + 2017-06-30 Michael Meissner + + Backport from mainline + 2017-06-23 Michael Meissner + + PR target/80510 + * config/rs6000/rs6000.md (ALTIVEC_DFORM): Do not allow DImode in + 32-bit, since indexed is not valid for DImode. + (mov_hardfloat32): Reorder ISA 2.07 load/stores before ISA + 3.0 d-form load/stores to be the same as mov_hardfloat64. + (define_peephole2 for Altivec d-form load): Add 32-bit support. + (define_peephole2 for Altivec d-form store): Likewise. + + 2017-06-27 Segher Boessenkool + + Backports from trunk: + + 2016-08-15 Segher Boessenkool + PR rtl-optimization/73650 + * lra-constraints.c (simple_move_p): If the insn is multiple_sets + it is not a simple move. + + 2017-01-20 Segher Boessenkool + PR target/61729 + PR target/77850 + * config/rs6000/rs6000.c (rs6000_gimplify_va_arg): Adjust address to + read from, for big endian. + + 2017-04-04 Segher Boessenkool + PR rtl-optimization/60818 + * simplify-rtx.c (simplify_binary_operation_1): Do not replace + a compare of comparisons with the thing compared if this results + in a different machine mode. + + 2017-04-12 Segher Boessenkool + PR target/80382 + * config/rs6000/sync.md (atomic_load, atomic_store + PR rtl-optimization/80429 + * ira.c (split_live_ranges_for_shrink_wrap): Don't split regs that + are only used in debug insns. + + 2017-05-17 Segher Boessenkool + PR middle-end/80692 + * real.c (do_compare): Give decimal_do_compare preference over + comparing just the signs. + + 2017-05-31 Segher Boessenkool + PR target/80618 + * config/rs6000/vector.md (*vector_uneq): Write the nor in the + splitter result in the canonical way. + + 2017-06-09 Segher Boessenkool + PR target/80966 + * config/rs6000/rs6000.c (rs6000_emit_allocate_stack): Assert that + gen_add3_insn did not fail. + * config/rs6000/rs6000.md (add3): If asked to add a constant to + r0, construct that number in a temporary reg and add that reg to r0. + If asked to put the result in r0 as well, fail. + + 2017-06-23 Segher Boessenkool + PR middle-end/80902 + * builtins.c (expand_builtin_atomic_fetch_op): If emitting code after + a call, force the call to not be a tail call. + + 2017-06-23 Thomas Preud'homme + + Backport from mainline + 2017-05-04 Prakhar Bahuguna + + * gcc/config/arm/arm-builtins.c (arm_init_builtins): Rename + __builtin_arm_ldfscr to __builtin_arm_get_fpscr, and rename + __builtin_arm_stfscr to __builtin_arm_set_fpscr. + + 2017-06-22 Richard Biener + + Backport from mainline + 2017-02-17 Richard Biener + + PR tree-optimization/79552 + * tree-ssa-structalias.c (visit_loadstore): Properly verify + default defs. + + 2016-04-18 Richard Biener + + PR tree-optimization/43434 + * tree-ssa-structalias.c (struct vls_data): New. + (visit_loadstore): Handle all pointer-based accesses. + (compute_dependence_clique): Compute a bitmap of restrict tags + assigned bases and pass it to visit_loadstore. + + 2017-06-22 Jakub Jelinek + + Backported from mainline + 2017-06-21 Jakub Jelinek + + PR c++/81130 + * gimplify.c (omp_add_variable): Don't force GOVD_SEEN for types + with ctors/dtors if GOVD_SHARED is set. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-05-31 Martin Liska + + PR target/79155 + * config/i386/cpuid.h: Fix typo in a comment in cpuid.h. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-05-30 Martin Liska + + PR other/80909 + * auto-profile.c (get_function_decl_from_block): Fix + parenthesis. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-05-26 Martin Liska + + PR ipa/80663 + * params.def: Bound partial-inlining-entry-probability param. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-05-16 Martin Liska + + PR ipa/79849. + PR ipa/79850. + * ipa-devirt.c (warn_types_mismatch): Fix typo. + (odr_types_equivalent_p): Likewise. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-05-15 Martin Liska + + PR driver/31468 + * gcc.c (process_command): Do not allow empty argument of -o option. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-05-02 Martin Liska + + * doc/gcov.texi: Add missing preposition. + * gcov.c (function_info::function_info): Properly fill up + all member variables. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-05-02 Martin Liska + + PR other/80589 + * common.opt: Fix typo. + * doc/invoke.texi: Likewise. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-04-28 Martin Liska + + * doc/gcov.texi: Enhance documentation of gcov. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-04-28 Martin Liska + + * doc/gcov.texi: Sort options in alphabetic order. + * doc/gcov-dump.texi: Likewise. + * doc/gcov-tool.texi: Likewise. + * gcov.c (print_usage): Likewise. + * gcov-dump.c (print_usage): Likewise. + * gcov-tool.c (print_merge_usage_message): Likewise. + (print_rewrite_usage_message): Likewise. + (print_overlap_usage_message): Likewise. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-04-28 Martin Liska + + PR gcov-profile/53915 + * gcov.c (format_gcov): Print 'NAN %' when top > bottom. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-04-28 Martin Liska + + PR driver/56469 + * coverage.c (coverage_remove_note_file): New function. + * coverage.h: Declare the function. + * toplev.c (finalize): Clean if an error has been seen. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-04-12 Jan Hubicka + + PR lto/69953 + * ipa-visibility.c (non_local_p): Fix typos. + (localize_node): When localizing symbol in same comdat group, + dissolve the group only when we know external symbols are going + to be privatized. + (function_and_variable_visibility): Do not localize DECL_EXTERNAL. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-01-17 Nathan Sidwell + + * ipa-visibility.c (localize_node): New function, broken out of ... + (function_and_variable_visibility): ... here. Call it. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-01-06 Nathan Sidwell + + * ipa-visibility.c (function_and_variable_visibility): Reformat + comments and long lines. Remove extrneous if. + * symtab.c (symtab_node::make_decl_local): Fix code format. + (symtab_node::set_section_for_node): Fix comment typo. + + 2017-06-22 Martin Liska + + Backport from mainline + 2016-10-20 Martin Liska + + PR lto/78049 + * lto-streamer-in.c (fixup_call_stmt_edges_1): Replace value + comparison with STMT_UID_NOT_IN_RANGE. + (fixup_call_stmt_edges): Do not fixup edges of a thunk in + LTRANS. + + 2017-06-22 Jakub Jelinek + + Backported from mainline + 2017-05-22 Jakub Jelinek + + PR middle-end/80809 + * omp-low.c (finish_taskreg_remap): New function. + (finish_taskreg_scan): If unit size of ctx->record_type + is non-constant, unshare the size expression and replace + decls in it with possible outer var refs. + + PR middle-end/80809 + * gimplify.c (omp_add_variable): For GOVD_DEBUG_PRIVATE use + GOVD_SHARED rather than GOVD_PRIVATE with it. + (gimplify_adjust_omp_clauses_1, gimplify_adjust_omp_clauses): Expect + GOVD_SHARED rather than GOVD_PRIVATE with GOVD_DEBUG_PRIVATE. + + PR middle-end/80853 + * omp-low.c (lower_reduction_clauses): Pass OMP_CLAUSE_PRIVATE + as last argument to build_outer_var_ref for pointer bases of array + section reductions. + + 2017-06-22 Richard Biener + + Backport from mainline + 2017-04-20 Richard Biener + + PR tree-optimization/80453 + * tree-ssa-sccvn.h (struct vn_phi_s): Add cclhs and ccrhs members. + * tree-ssa-sccvn.c (cond_stmts_equal_p): Use recorded lhs and rhs + from the conditions. + (vn_phi_eq): Pass them down. + (vn_phi_lookup): Record them. + (vn_phi_insert): Likewise. + + 2017-04-07 Richard Biener + + PR middle-end/80341 + * tree.c (get_unwidened): Also handle ! for_type case for + INTEGER_CSTs. + * convert.c (do_narrow): Split out from ... + (convert_to_integer_1): ... here. Do not pass final truncation + type to get_unwidened for TRUNC_DIV_EXPR. + + 2017-04-04 Richard Biener + + PR middle-end/80281 + * match.pd (A + (-B) -> A - B): Make sure to preserve unsigned + arithmetic done for the negate or the plus. Simplify. + (A - (-B) -> A + B): Likewise. + * fold-const.c (split_tree): Make sure to not negate pointers. + + 2017-06-22 Richard Biener + + Backport from mainline + 2017-01-30 Richard Biener + + PR tree-optimization/79256 + * targhooks.c (default_builtin_vector_alignment_reachable): Honor + BIGGEST_FIELD_ALIGNMENT and ADJUST_FIELD_ALIGN to fix up bogus + alignment on TYPE. + * tree.c (build_aligned_type): Set TYPE_USER_ALIGN. + + 2017-01-25 Richard Biener + + PR tree-optimization/69264 + * target.def (vector_alignment_reachable): Improve documentation. + * doc/tm.texi: Regenerate. + * targhooks.c (default_builtin_vector_alignment_reachable): Simplify + and add a comment. + * tree-vect-data-refs.c (vect_supportable_dr_alignment): Revert + earlier changes with respect to TYPE_USER_ALIGN. + (vector_alignment_reachable_p): Likewise. Improve dumping. + + 2017-02-09 Richard Biener + + PR tree-optimization/69823 + * graphite-scop-detection.c (scop_detection::harmful_loop_in_region): + Properly enumerate all BBs in the region. Use auto_vec. + + 2017-06-21 Michael Meissner + + Back port from mainline + 2017-05-19 Michael Meissner + + PR target/80718 + * config/rs6000/vsx.md (vsx_splat_, VSX_D iterator): Prefer + VSX registers over GPRs, particularly on ISA 2.07 which does not + have the MTVSRDD instruction. + + Back port from mainline + 2017-05-18 Michael Meissner + + PR target/80510 + * config/rs6000/predicates.md (simple_offsettable_mem_operand): + New predicate. + + * config/rs6000/rs6000.md (ALTIVEC_DFORM): New iterator. + (define_peephole2 for Altivec d-form load): Add peepholes to catch + cases where the register allocator uses a move and an offsettable + memory operation to/from a FPR register on ISA 2.06/2.07. + (define_peephole2 for Altivec d-form store): Likewise. + + Back port from mainline + 2017-05-09 Michael Meissner + + PR target/68163 + * config/rs6000/rs6000.md (f32_lr): Delete mode attributes that + are now unused after splitting mov{sf,sd}_hardfloat. + (f32_lr2): Likewise. + (f32_lm): Likewise. + (f32_lm2): Likewise. + (f32_li): Likewise. + (f32_li2): Likewise. + (f32_lv): Likewise. + (f32_sr): Likewise. + (f32_sr2): Likewise. + (f32_sm): Likewise. + (f32_sm2): Likewise. + (f32_si): Likewise. + (f32_si2): Likewise. + (f32_sv): Likewise. + (f32_dm): Likewise. + (f32_vsx): Likewise. + (f32_av): Likewise. + (mov_hardfloat): Split into separate movsf and movsd pieces. + For movsf, order stores so the VSX stores occur before the GPR + store which encourages the register allocator to use a traditional + FPR instead of a GPR. For movsd, order the stores so that the GPR + store comes before the VSX stores to allow the power6 to work. + This is due to the power6 not having a 32-bit integer store + instruction from a FPR. + (movsf_hardfloat): Likewise. + (movsd_hardfloat): Likewise. + + 2017-06-21 Jeff Law + + * config/darwin-driver.c (darwin_driver_init): Const-correctness + fixes for first_period and second_period variables. + + 2017-06-19 James Greenhalgh + + Backport from mainline + 2017-06-16 James Greenhalgh + + PR target/71778 + * config/arm/arm-builtins.c (arm_expand_builtin_args): Return TARGET + if given a non-constant argument for an intrinsic which requires a + constant. + + 2017-06-15 Eric Botcazou + + PR rtl-optimization/80474 + * reorg.c (update_block): Do not ignore instructions in a delay slot. + + 2017-06-14 Eric Botcazou + + * config/sparc/driver-sparc.c (cpu_names): Add SPARC-T5 entry. + + 2017-06-09 David S. Miller + + PR target/80968 + * config/sparc/sparc.c (sparc_flat_expand_epilogue): Don't + emit frame blockage here. + (sparc_expand_epilogue): Do it here. + * config/sparc/sparc.md (return expander): Emit frame blockage + for alloca here too. + + 2017-06-06 David S. Miller + + PR target/80968 + * config/sparc/sparc.c (sparc_expand_prologue): Emit frame + blockage if function uses alloca. + + 2017-06-06 Toma Tabacu + + Backported from mainline + 2017-03-09 Toma Tabacu + + * doc/sourcebuild.texi (Effective-Target Keywords, Other attributes): + Document rdynamic. + + 2017-06-01 Jakub Jelinek + + Backported from mainline + 2016-08-19 Jakub Jelinek + + * config/i386/rdseedintrin.h (_rdseed16_step, _rdseed32_step, + _rdseed64_step): Uglify argument names and/or local variable names + in inline functions. + * config/i386/rtmintrin.h (_xabort): Likewise. + * config/i386/avx512vlintrin.h (_mm256_ternarylogic_epi64, + _mm256_mask_ternarylogic_epi64, _mm256_maskz_ternarylogic_epi64, + _mm256_ternarylogic_epi32, _mm256_mask_ternarylogic_epi32, + _mm256_maskz_ternarylogic_epi32, _mm_ternarylogic_epi64, + _mm_mask_ternarylogic_epi64, _mm_maskz_ternarylogic_epi64, + _mm_ternarylogic_epi32, _mm_mask_ternarylogic_epi32, + _mm_maskz_ternarylogic_epi32): Likewise. + * config/i386/lwpintrin.h (__llwpcb, __lwpval32, __lwpval64, + __lwpins32, __lwpins64): Likewise. + * config/i386/avx2intrin.h (_mm_i32gather_pd, _mm_mask_i32gather_pd, + _mm256_i32gather_pd, _mm256_mask_i32gather_pd, _mm_i64gather_pd, + _mm_mask_i64gather_pd, _mm256_i64gather_pd, _mm256_mask_i64gather_pd, + _mm_i32gather_ps, _mm_mask_i32gather_ps, _mm256_i32gather_ps, + _mm256_mask_i32gather_ps, _mm_i64gather_ps, _mm_mask_i64gather_ps, + _mm256_i64gather_ps, _mm256_mask_i64gather_ps, _mm_i32gather_epi64, + _mm_mask_i32gather_epi64, _mm256_i32gather_epi64, + _mm256_mask_i32gather_epi64, _mm_i64gather_epi64, + _mm_mask_i64gather_epi64, _mm256_i64gather_epi64, + _mm256_mask_i64gather_epi64, _mm_i32gather_epi32, + _mm_mask_i32gather_epi32, _mm256_i32gather_epi32, + _mm256_mask_i32gather_epi32, _mm_i64gather_epi32, + _mm_mask_i64gather_epi32, _mm256_i64gather_epi32, + _mm256_mask_i64gather_epi32): Likewise. + * config/i386/pmm_malloc.h (_mm_malloc, _mm_free): Likewise. + * config/i386/ia32intrin.h (__writeeflags): Likewise. + * config/i386/pkuintrin.h (_wrpkru): Likewise. + * config/i386/avx512pfintrin.h (_mm512_mask_prefetch_i32gather_pd, + _mm512_mask_prefetch_i32gather_ps, _mm512_mask_prefetch_i64gather_pd, + _mm512_mask_prefetch_i64gather_ps, _mm512_prefetch_i32scatter_pd, + _mm512_prefetch_i32scatter_ps, _mm512_mask_prefetch_i32scatter_pd, + _mm512_mask_prefetch_i32scatter_ps, _mm512_prefetch_i64scatter_pd, + _mm512_prefetch_i64scatter_ps, _mm512_mask_prefetch_i64scatter_pd, + _mm512_mask_prefetch_i64scatter_ps): Likewise. + * config/i386/gmm_malloc.h (_mm_malloc, _mm_free): Likewise. + * config/i386/avx512fintrin.h (_mm512_ternarylogic_epi64, + _mm512_mask_ternarylogic_epi64, _mm512_maskz_ternarylogic_epi64, + _mm512_ternarylogic_epi32, _mm512_mask_ternarylogic_epi32, + _mm512_maskz_ternarylogic_epi32, _mm512_i32gather_ps, + _mm512_mask_i32gather_ps, _mm512_i32gather_pd, _mm512_i64gather_ps, + _mm512_i64gather_pd, _mm512_i32gather_epi32, _mm512_i32gather_epi64, + _mm512_i64gather_epi32, _mm512_i64gather_epi64): Likewise. + + 2017-05-30 Max Filippov + + Backport from mainline + 2017-05-29 Max Filippov + + * config/xtensa/xtensa.c (xtensa_emit_call): Use + HOST_WIDE_INT_PRINT_HEX instead of 0x%lx format string. + (print_operand): Use HOST_WIDE_INT_PRINT_DEC instead of %ld + format string. + + 2017-05-30 Max Filippov + + Backport from mainline + 2016-11-29 Max Filippov + + * config/xtensa/xtensa.c (hwloop_optimize): Don't emit zero + overhead loop start between a call and its CALL_ARG_LOCATION + note. + + 2017-05-30 Max Filippov + + Backport from mainline + 2016-11-01 Max Filippov + + * config/xtensa/xtensa-protos.h + (xtensa_use_return_instruction_p): New prototype. + * config/xtensa/xtensa.c (xtensa_current_frame_size, + xtensa_callee_save_size): Remove. + (struct machine_function): Add new fields: current_frame_size, + callee_save_size, frame_laid_out and epilogue_done. + (compute_frame_size, xtensa_expand_prologue, + xtensa_expand_epilogue): Replace xtensa_callee_save_size with + cfun->machine->callee_save_size and xtensa_current_frame_size + with cfun->machine->current_frame_size. + (compute_frame_size): Update cfun->machine->frame_laid_out and + don't update frame layout after reload completion. + (xtensa_expand_epilogue): Set cfun->machine->epilogue_done + instead of zeroing xtensa_current_frame_size. + (xtensa_use_return_instruction_p): New function. + * config/xtensa/xtensa.h (xtensa_current_frame_size): Remove + declaration. + (INITIAL_ELIMINATION_OFFSET): Use return value of + compute_frame_size instead of xtensa_current_frame_size value. + * config/xtensa/xtensa.md ("return" pattern): Use new predicate + function xtensa_use_return_instruction_p instead of inline code. + + 2017-05-29 Eric Botcazou + + * doc/install.texi (Options specification): Move entry of + --enable-sjlj-exceptions. + + 2017-05-26 Sheldon Lobo + + Backported from mainline + 2017-05-24 Sheldon Lobo + + * config/sparc/sparc.md (length): Return the correct value for -mflat + sibcalls to match output_sibcall. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-24 Jan Hubicka + + PR middle-end/79931 + * ipa-devirt.c (dump_possible_polymorphic_call_targets): Fix ICE. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-19 Richard Biener + + PR ipa/65972 + * auto-profile.c (afdo_vpt_for_early_inline): Update SSA + when needed by AutoPGO. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-19 Paulo J. Matos + + PR lto/50345 + * doc/lto.texi: Remove an extra 'that'. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-18 Martin Liska + + PR gcov-profile/78783 + * gcov-tool.c (gcov_output_files): Validate that destination + file is either removed by the tool or by a user. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-13 Martin Liska + + PR gcov-profile/80413 + * gcov-io.c (gcov_write_string): Copy to buffer just when + allocated size is greater than zero. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-11 Martin Liska + + PR ipa/80212 + * cgraph.c (cgraph_node::dump): Dump calls_comdat_local. + * ipa-split.c (split_function): Create a local comdat symbol + if caller is in a comdat group. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-11 Martin Liska + + PR ipa/80212 + * ipa-cp.c (determine_versionability): Handle calls_comdat_local + flags. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-11 Martin Liska + + PR sanitizer/70878 + * ubsan.c (instrument_object_size): Do not instrument register + variables. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-10 Martin Liska + + PR gcov-profile/80224 + * gcov.c (print_usage): Fix usage string. + (get_gcov_intermediate_filename): Remove. + (output_gcov_file): Use both for normal and intermediate format. + (generate_results): Do not initialize special file for + intermediate format. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-03-28 Richard Biener + + PR ipa/80205 + * tree-inline.c (copy_phis_for_bb): Do not create PHI node + without arguments, generate default definition of a SSA name. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-03-28 Martin Liska + + PR ipa/80104 + * cgraphunit.c (cgraph_node::expand_thunk): Mark argument of a + thunk call as DECL_GIMPLE_REG_P when vector or complex type. + + 2017-05-23 Sheldon Lobo + + Backport from mainline + 2017-05-18 Sheldon Lobo + + * config/sparc/sparc.c (sparc_option_override): Set function + alignment for -mcpu=niagara7 to 64 to match the I$ line. + * config/sparc/sparc.h (BRANCH_COST): Set the SPARC M7 branch + latency to 1. + * config/sparc/sparc.h (BRANCH_COST): Set the SPARC T4 branch + latency to 2. + * config/sparc/sol2.h: Fix a ASM_CPU32_DEFAULT_SPEC typo. + + 2017-05-19 Uros Bizjak + + Backport from mainline + 2017-05-18 Uros Bizjak + + PR target/80799 + * config/i386/mmx.md (*mov_internal): Enable + alternatives 11, 12, 13 and 14 also for 32bit targets. + Remove alternatives 15, 16, 17 and 18. + * config/i386/sse.md (vec_concatv2di): Change + alternative (!x, *y) to (x, ?!*Yn). + + 2017-05-15 Richard Biener + + Revert backport of + PR middle-end/80222 + * gimple-fold.c (gimple_fold_indirect_ref): Do not touch + TYPE_REF_CAN_ALIAS_ALL references. + * fold-const.c (fold_indirect_ref_1): Likewise. + + 2017-05-13 Bill Schmidt + + Backport from mainline + 2017-05-05 Bill Schmidt + + * config/rs6000/rs6000.c (rs6000_vect_nonmem): New static var. + (rs6000_init_cost): Initialize rs6000_vect_nonmem. + (rs6000_add_stmt_cost): Update rs6000_vect_nonmem. + (rs6000_finish_cost): Avoid vectorizing simple copy loops with + VF=2 that require versioning. + + 2017-05-12 Bill Schmidt + + Backport from mainline + 2017-05-10 Bill Schmidt + + * config/rs6000/rs6000.c (altivec_init_builtins): Define POWER8 + built-ins for vec_xl and vec_xst with short and char pointer + arguments. + + 2017-05-10 John David Anglin + + PR target/80090 + * config/pa/pa.c (pa_assemble_integer): When outputting a SYMBOL_REF, + handle calling assemble_external ourself. + + PR target/79027 + * config/pa/pa.c (pa_cannot_change_mode_class): Reject changes to/from + modes with zero size. Enhance comment. + + 2017-05-10 Richard Biener + + Backport from mainline + 2017-03-17 Richard Biener + + PR middle-end/80075 + * tree-eh.c (stmt_could_throw_1_p): Only handle gimple assigns. + Properly verify the LHS before the RHS possibly claims to be + handled. + (stmt_could_throw_p): Hande gimple conds fully here. Clobbers + do not throw. + + 2017-03-21 Brad Spengler + + PR plugin/80094 + * plugin.c (htab_hash_plugin): New function. + (add_new_plugin): Use it and adjust. + (parse_plugin_arg_opt): Adjust. + (init_one_plugin): Likewise. + + 2017-03-20 Richard Biener + + PR tree-optimization/80113 + * graphite-isl-ast-to-gimple.c (copy_loop_phi_nodes): Do not + allocate extra SSA name for PHI def. + (add_close_phis_to_outer_loops): Likewise. + (add_close_phis_to_merge_points): Likewise. + (copy_loop_close_phi_args): Likewise. + (copy_cond_phi_nodes): Likewise. + + 2017-03-21 Richard Biener + + PR tree-optimization/80122 + * tree-inline.c (copy_bb): Do not expans va-arg packs or + va_arg_pack_len when the inlined call stmt requires pack + expansion itself. + * tree-inline.h (struct copy_body_data): Make call_stmt a gcall *. + + 2017-03-24 Richard Biener + + PR tree-optimization/80167 + * graphite-isl-ast-to-gimple.c + (translate_isl_ast_to_gimple::is_valid_rename): Handle default-defs + properly. + (translate_isl_ast_to_gimple::get_rename): Likewise. + + 2017-03-27 Richard Biener + + PR tree-optimization/80170 + * tree-vect-data-refs.c (vect_compute_data_ref_alignment): Make + sure DR/SCEV didnt fold in constants we do not see when looking + at the reference base alignment. + + 2017-03-27 Richard Biener + + PR middle-end/80171 + * gimple-fold.c (fold_ctor_reference): Properly guard against + NULL return value from canonicalize_constructor_val. + + 2017-05-09 Richard Biener + + Backport from mainline + 2017-03-28 Richard Biener + + PR middle-end/80222 + * gimple-fold.c (gimple_fold_indirect_ref): Do not touch + TYPE_REF_CAN_ALIAS_ALL references. + * fold-const.c (fold_indirect_ref_1): Likewise. + + 2017-04-06 Richard Biener + + PR tree-optimization/80262 + * tree-sra.c (build_ref_for_offset): Preserve address-space + information. + * tree-ssa-sccvn.c (vn_reference_maybe_forwprop_address): + Drop useless address-space information on MEM_REF offsets. + + 2017-04-03 Richard Biener + + PR tree-optimization/80275 + * fold-const.c (split_address_to_core_and_offset): Handle + POINTER_PLUS_EXPR. + + 2017-04-06 Richard Biener + + PR tree-optimization/80334 + * tree-ssa-loop-ivopts.c (rewrite_use_address): Properly + preserve alignment of accesses. + + 2017-04-10 Richard Biener + + PR middle-end/80362 + * fold-const.c (fold_binary_loc): Look at unstripped ops when + looking for NEGATE_EXPR in -A / -B to A / B folding. + + 2017-04-25 Richard Biener + + PR tree-optimization/80492 + * alias.c (compare_base_decls): Handle registers with asm + specification conservatively. + + 2017-04-27 Richard Biener + + PR middle-end/80539 + * tree-chrec.c (chrec_fold_plus_poly_poly): Deal with not + being in loop-closed SSA form conservatively. + (chrec_fold_multiply_poly_poly): Likewise. + + 2017-05-09 Jakub Jelinek + + PR testsuite/80678 + 2016-06-14 Richard Biener + + PR middle-end/71310 + PR bootstrap/71510 + * expr.h (get_bit_range): Declare. + * expr.c (get_bit_range): Export. + * fold-const.c (optimize_bit_field_compare): Use get_bit_range and + word_mode again to constrain the bitfield access. + + 2016-06-11 Segher Boessenkool + + PR middle-end/71310 + * fold-const.c (optimize_bit_field_compare): Don't try to use + word_mode unconditionally for reading the bit field, look at + DECL_BIT_FIELD_REPRESENTATIVE instead. + + 2017-05-05 Jakub Jelinek + + Backported from mainline + 2017-04-25 Jakub Jelinek + + * Makefile.in (s-options): Invoke opt-gather.awk with LC_ALL=C in the + environment. + + PR rtl-optimization/80501 + * combine.c (make_compound_operation_int): Set subreg_code to SET + even for AND with mask of the sign bit of mode. + + 2017-04-12 Jakub Jelinek + + PR sanitizer/80349 + * fold-const.c (fold_binary_loc) : Convert arg0's + first argument to type. + + 2017-04-11 Jakub Jelinek + + PR rtl-optimization/80385 + * simplify-rtx.c (simplify_unary_operation_1): Don't transform + (not (neg X)) into (plus X -1) for complex or non-integral modes. + + PR libgomp/80394 + * omp-low.c (scan_omp_task): Don't optimize away empty tasks + if they have any depend clauses. + + 2017-04-04 Jakub Jelinek + Richard Biener + + PR c++/80297 + * genmatch.c (capture::gen_transform): For GENERIC unshare_expr + captures used multiple times, except for the last use. + * generic-match-head.c: Include gimplify.h. + + 2017-04-04 Jakub Jelinek + + PR target/80286 + * config/i386/i386.c (ix86_expand_args_builtin): If op has scalar + int mode, convert_modes it to mode as unsigned, otherwise use + lowpart_subreg to mode rather than SImode. + * config/i386/sse.md (ashr3, + ashr3, ashr3, 3): + Use DImode instead of SImode for the shift count operand. + * config/i386/mmx.md (mmx_ashr3, mmx_3): + Likewise. + + 2017-04-13 Jakub Jelinek + + PR debug/80321 + * dwarf2out.c (decls_for_scope): Ignore declarations of + current_function_decl in BLOCK_NONLOCALIZED_VARS. + + 2017-03-31 Jakub Jelinek + + PR debug/79255 + * dwarf2out.c (decls_for_scope): If BLOCK_NONLOCALIZED_VAR is + a FUNCTION_DECL, pass it as decl instead of origin to + process_scope_var. + + PR debug/80025 + * cselib.c (cselib_hasher::equal): Pass 0 to rtx_equal_for_cselib_1. + (rtx_equal_for_cselib_1): Add depth argument. If depth + is 128, don't look up VALUE locs and punt. Increment + depth in recursive calls when walking VALUE locs. + + 2017-03-27 Jakub Jelinek + + PR sanitizer/80168 + * asan.c (instrument_derefs): Copy over last operand from + original COMPONENT_REF to the new COMPONENT_REF with + DECL_BIT_FIELD_REPRESENTATIVE. + * ubsan.c (instrument_object_size): Likewise. + + 2017-03-24 Jakub Jelinek + + PR rtl-optimization/80112 + * loop-doloop.c (doloop_condition_get): Don't check condition + if cmp isn't SET with IF_THEN_ELSE src. + + 2017-03-22 Jakub Jelinek + + PR c++/80129 + * gimplify.c (gimplify_modify_expr_rhs) : Clear + TREE_READONLY on result if writing it more than once. + + 2017-03-09 Jakub Jelinek + + PR sanitizer/79944 + * asan.c (get_mem_refs_of_builtin_call): For BUILT_IN_ATOMIC* and + BUILT_IN_SYNC*, determine the access type from the size suffix and + always build a MEM_REF with that type. Handle forgotten + BUILT_IN_SYNC_FETCH_AND_NAND_16 and BUILT_IN_SYNC_NAND_AND_FETCH_16. + + PR target/79932 + * config/i386/avx512vlintrin.h (_mm256_cmpge_epi32_mask, + _mm256_cmpge_epi64_mask, _mm256_cmpge_epu32_mask, + _mm256_cmpge_epu64_mask, _mm256_cmple_epi32_mask, + _mm256_cmple_epi64_mask, _mm256_cmple_epu32_mask, + _mm256_cmple_epu64_mask, _mm256_cmplt_epi32_mask, + _mm256_cmplt_epi64_mask, _mm256_cmplt_epu32_mask, + _mm256_cmplt_epu64_mask, _mm256_cmpneq_epi32_mask, + _mm256_cmpneq_epi64_mask, _mm256_cmpneq_epu32_mask, + _mm256_cmpneq_epu64_mask, _mm256_mask_cmpge_epi32_mask, + _mm256_mask_cmpge_epi64_mask, _mm256_mask_cmpge_epu32_mask, + _mm256_mask_cmpge_epu64_mask, _mm256_mask_cmple_epi32_mask, + _mm256_mask_cmple_epi64_mask, _mm256_mask_cmple_epu32_mask, + _mm256_mask_cmple_epu64_mask, _mm256_mask_cmplt_epi32_mask, + _mm256_mask_cmplt_epi64_mask, _mm256_mask_cmplt_epu32_mask, + _mm256_mask_cmplt_epu64_mask, _mm256_mask_cmpneq_epi32_mask, + _mm256_mask_cmpneq_epi64_mask, _mm256_mask_cmpneq_epu32_mask, + _mm256_mask_cmpneq_epu64_mask, _mm_cmpge_epi32_mask, + _mm_cmpge_epi64_mask, _mm_cmpge_epu32_mask, _mm_cmpge_epu64_mask, + _mm_cmple_epi32_mask, _mm_cmple_epi64_mask, _mm_cmple_epu32_mask, + _mm_cmple_epu64_mask, _mm_cmplt_epi32_mask, _mm_cmplt_epi64_mask, + _mm_cmplt_epu32_mask, _mm_cmplt_epu64_mask, _mm_cmpneq_epi32_mask, + _mm_cmpneq_epi64_mask, _mm_cmpneq_epu32_mask, _mm_cmpneq_epu64_mask, + _mm_mask_cmpge_epi32_mask, _mm_mask_cmpge_epi64_mask, + _mm_mask_cmpge_epu32_mask, _mm_mask_cmpge_epu64_mask, + _mm_mask_cmple_epi32_mask, _mm_mask_cmple_epi64_mask, + _mm_mask_cmple_epu32_mask, _mm_mask_cmple_epu64_mask, + _mm_mask_cmplt_epi32_mask, _mm_mask_cmplt_epi64_mask, + _mm_mask_cmplt_epu32_mask, _mm_mask_cmplt_epu64_mask, + _mm_mask_cmpneq_epi32_mask, _mm_mask_cmpneq_epi64_mask, + _mm_mask_cmpneq_epu32_mask, _mm_mask_cmpneq_epu64_mask): Move + definitions outside of __OPTIMIZE__ guarded section. + + PR target/79932 + * config/i386/avx512bwintrin.h (_mm512_packs_epi32, + _mm512_maskz_packs_epi32, _mm512_mask_packs_epi32, + _mm512_packus_epi32, _mm512_maskz_packus_epi32, + _mm512_mask_packus_epi32): Move definitions outside of __OPTIMIZE__ + guarded section. + + 2017-03-08 Jakub Jelinek + + PR c/79940 + * gimplify.c (gimplify_omp_for): Replace index var in outer + taskloop statement with an artificial variable and add + OMP_CLAUSE_PRIVATE clause for it. + + 2017-03-07 Jakub Jelinek + + PR rtl-optimization/79901 + * config/i386/sse.md (*avx512bw_3): Renamed to + ... + (*avx512f_3): ... this. + (3 with maxmin code iterator): Use VI8_AVX2_AVX512F + iterator instead of VI8_AVX2_AVX512BW. + + PR rtl-optimization/79901 + * expr.c (expand_expr_real_2): For vector MIN/MAX, if there is no + min/max expander, expand it using expand_vec_cond_expr. + + 2017-03-03 Jakub Jelinek + + PR target/79807 + * config/i386/i386.c (ix86_expand_multi_arg_builtin): If target + is a memory operand, increase num_memory. + (ix86_expand_args_builtin): Likewise. + + 2017-03-01 Jakub Jelinek + + PR c++/79681 + * fold-const.c (make_bit_field_ref): If orig_inner is COMPONENT_REF, + attempt to use its first operand as BIT_FIELD_REF base. + + 2017-02-28 Jakub Jelinek + + PR target/79729 + * config/i386/i386.c (ix86_print_operand) : Replace + gcc_unreachable with output_operand_lossage. + + 2017-02-25 Jakub Jelinek + + PR middle-end/79396 + * tree-eh.c (operation_could_trap_p, stmt_could_throw_1_p): Handle + FMA_EXPR like tcc_binary or tcc_unary. + + 2017-02-21 Jakub Jelinek + + PR target/79570 + * sel-sched.c (moveup_expr_cached): Don't call sel_bb_head + on temporarily removed DEBUG_INSNs. + + PR target/79494 + * config/i386/i386.c (ix86_expand_split_stack_prologue): Call + make_reg_eh_region_note_nothrow_nononlocal on call_insn. + * config/rs6000/rs6000.c: Include except.h. + (rs6000_expand_split_stack_prologue): Call + make_reg_eh_region_note_nothrow_nononlocal on the call insn. + + 2017-02-20 Jakub Jelinek + + PR target/79568 + * config/i386/i386.c (ix86_expand_builtin): Handle + OPTION_MASK_ISA_AVX512VL and OPTION_MASK_ISA_64BIT in + ix86_builtins_isa[fcode].isa as a requirement of those + flags and any other flag in the bitmask. + (ix86_init_mmx_sse_builtins): Use 0 instead of + ~OPTION_MASK_ISA_64BIT as mask. + * config/i386/i386-builtin.def (bdesc_special_args, + bdesc_args): Likewise. + + 2017-02-18 Jakub Jelinek + + PR target/79559 + * config/i386/i386.c (ix86_print_operand): Use output_operand_lossage + instead of gcc_assert for K, r and R code checks. Formatting fixes. + + 2017-05-05 Marek Polacek + Ramana Radhakrishnan + Jakub Jelinek + + PR target/77728 + * config/arm/arm.c: Include gimple.h. + (aapcs_layout_arg): Emit -Wpsabi note if arm_needs_doubleword_align + returns negative, increment ncrn if it returned non-zero. + (arm_needs_doubleword_align): Return int instead of bool, + ignore DECL_ALIGN of non-FIELD_DECL TYPE_FIELDS chain + members, but if there is any such non-FIELD_DECL + > PARM_BOUNDARY aligned decl, return -1 instead of false. + (arm_function_arg): Emit -Wpsabi note if arm_needs_doubleword_align + returns negative, increment nregs if it returned non-zero. + (arm_setup_incoming_varargs): Likewise. + (arm_function_arg_boundary): Emit -Wpsabi note if + arm_needs_doubleword_align returns negative, return + DOUBLEWORD_ALIGNMENT if it returned non-zero. + + 2017-05-03 Uros Bizjak + + Backport from mainline + 2017-05-01 Uros Bizjak + + PR target/68491 + * config/i386/cpuid.h (__get_cpuid): Always return 0 when + __get_cpuid_max returns 0. + (__get_cpuid_count): Ditto. + + 2017-04-21 Eric Botcazou + + Backport from mainline + 2017-04-19 Eric Botcazou + Jakub Jelinek + + PR tree-optimization/80426 + * tree-vrp.c (extract_range_from_binary_expr_1): For an additive + operation on symbolic operands, also compute the overflow for the + invariant part when the operation degenerates into a negation. + + 2017-04-19 Georg-Johann Lay + + Backport from 2017-04-19 trunk r246997. + + PR target/80462 + * config/avr/avr.c (tree.h): Include it. + (cgraph.h): Include it. + (avr_encode_section_info): Don't warn for uninitialized progmem + variable if it's just an alias. + + 2017-04-18 Georg-Johann Lay + + Backport from 2017-04-18 trunk r246966. + + PR target/79453 + * config/avr/avr.c (intl.h): Include it. + (avr_pgm_check_var_decl) [reason]: Wrap diagnostic snippets into _(). + + 2017-04-12 Bill Schmidt + + Backport from mainline + 2017-04-11 Bill Schmidt + + PR target/80376 + PR target/80315 + * config/rs6000/rs6000.c (rs6000_expand_unop_builtin): Return + CONST0_RTX (mode) rather than const0_rtx where appropriate. + (rs6000_expand_binop_builtin): Likewise. + (rs6000_expand_ternop_builtin): Likewise; also add missing + vsx_xxpermdi_* variants; also fix typo (arg1 => arg2) for + vshasigma built-ins. + * doc/extend.texi: Document that vec_xxpermdi's third argument + must be a constant. + + 2017-04-11 Pat Haugen + + Backport from mainline + 2017-04-07 Pat Haugen + + * rs6000/rs6000.c (vec_load_pendulum): Rename... + (vec_pairing): ...to this. + (power9_sched_reorder2): Rewrite code for pairing vector/vecload insns. + (rs6000_sched_init): Adjust for name change. + (struct rs6000_sched_context): Likewise. + (rs6000_init_sched_context): Likewise. + (rs6000_set_sched_context): Likewise. + + 2017-04-11 Martin Jambor + + Backport from mainline + 2017-03-30 Martin Jambor + + PR ipa/77333 + * cgraph.h (cgraph_build_function_type_skip_args): Declare. + * cgraph.c (redirect_call_stmt_to_callee): Set gimple fntype so that + it reflects the signature changes performed at the callee side. + * cgraphclones.c (build_function_type_skip_args): Make public, renamed + to cgraph_build_function_type_skip_args. + (build_function_decl_skip_args): Adjust call to the above function. + + 2017-04-08 Andreas Tobler + + Backport from mainline + 2017-04-08 Andreas Tobler + + * config/aarch64/aarch64-freebsd.h: Define MCOUNT_NAME. + Add comment for WCHAR_T. + + 2017-04-07 Andreas Tobler + + Backport from mainline + 2017-04-07 Andreas Tobler + + * config/aarch64/aarch64-freebsd.h: Define WCHAR_T. + + 2017-04-07 Eric Botcazou + + Backport from mainline + 2017-04-05 Eric Botcazou + + PR target/78002 + * config/aarch64/aarch64.c (aarch64_emit_probe_stack_range): Replace + ptr_mode with Pmode throughout. + * config/aarch64/aarch64.md (probe_stack_range_ + + Backport from mainline + 2017-04-07 Sebastian Huber + + * config/arm/arm.h (ARM_DEFAULT_SHORT_ENUMS): Provide default + definition. + * config/arm/arm.c (arm_default_short_enums): Use + ARM_DEFAULT_SHORT_ENUMS. + * config/arm/rtems.h (ARM_DEFAULT_SHORT_ENUMS): Define. + + 2017-04-06 Uros Bizjak + + Backport from mainline + 2017-04-06 Uros Bizjak + + PR target/79733 + * config/i386/i386.c (ix86_expand_builtin) + : Determine insn operand + mode from insn data. Convert operands to insn operand mode. + Copy operands that don't satisfy insn predicate to a register. + + 2017-04-05 Uros Bizjak + + PR target/80298 + * config/i386/mmintrin.h: Add -msse target option when __SSE__ is + not defined for x86_64 target. Add -mmmx target option when __SSE2__ + is not defined. + * config/i386/mm3dnow.h: Add -msse target when __SSE__ is not defined + for x86_64 target. + + 2017-04-06 Thomas Preud'homme + + PR target/80082 + * config/arm/arm-protos.h (FL_LPAE): Define macro. + (FL_FOR_ARCH7VE): Add FL_LPAE. + (arm_arch_lpae): Declare extern. + * config/arm/arm.c (arm_arch_lpae): Declare. + (arm_option_override): Define arm_arch_lpae. + * config/arm/arm.h (TARGET_HAVE_LPAE): Redefine in term of + arm_arch_lpae. + + 2017-04-03 Michael Meissner + + Back port from the trunk + 2017-03-14 Michael Meissner + + PR target/79947 + * config/rs6000/rs6000.h (TARGET_FRSQRTES): Add check for + -mpowerpc-gfxopt. + + 2017-03-31 Richard Sandiford + + PR tree-optimization/80218 + * tree-call-cdce.c (shrink_wrap_one_built_in_call_with_conds): + Update block frequencies and counts. + + 2017-03-30 Peter Bergner + + Backport from mainline + 2017-03-30 Peter Bergner + + PR target/80246 + * config/rs6000/dfp.md (dfp_dxex_): Update mode of operand 0. + (dfp_diex_): Update mode of operand 1. + * doc/extend.texi (dxex, dxexq): Document change to return type. + (diex, diexq): Document change to argument type. + + 2017-03-29 Michael Meissner + + Back port from trunk + 2017-03-21 Aaron Sawdey + + PR target/80123 + * doc/md.texi (Constraints): Document wA constraint. + * config/rs6000/constraints.md (wA): New. + * config/rs6000/rs6000.c (rs6000_debug_reg_global): Add wA reg_class. + (rs6000_init_hard_regno_mode_ok): Init wA constraint. + * config/rs6000/rs6000.h (RS6000_CONSTRAINT_wA): New. + * config/rs6000/vsx.md (vsx_splat_): Use wA constraint. + + 2017-03-16 Michael Meissner + + PR target/71294 + * config/rs6000/vsx.md (vsx_splat_, VSX_D iterator): Allow a + SPLAT operation on ISA 2.07 64-bit systems that have direct move, + but no MTVSRDD support, by doing MTVSRD and XXPERMDI. + + 2017-03-29 Richard Biener + + Backport from mainline + 2017-03-28 Richard Biener + + PR tree-optimization/78644 + * tree-ssa-ccp.c (evaluate_stmt): When we may not use the value + of a simplification result we may not use it at all. + + 2017-03-27 Richard Biener + + PR tree-optimization/80181 + * tree-ssa-ccp.c (likely_value): UNDEFINED ^ X is UNDEFINED. + + 2017-03-28 Marek Polacek + + Backport from mainline + 2017-03-28 Marek Polacek + + PR sanitizer/80067 + * fold-const.c (fold_comparison): Use protected_set_expr_location + instead of SET_EXPR_LOCATION. + + 2017-03-27 Michael Meissner + + Back port from trunk + 2017-03-27 Michael Meissner + + PR target/78543 + * config/rs6000/rs6000.md (bswaphi2_extenddi): Combine bswap + HImode and SImode with zero extend to DImode to one insn. + (bswap2_extenddi): Likewise. + (bswapsi2_extenddi): Likewise. + (bswaphi2_extendsi): Likewise. + (bswaphi2): Combine bswap HImode and SImode into one insn. + Separate memory insns from swapping register. + (bswapsi2): Likewise. + (bswap2): Likewise. + (bswaphi2_internal): Delete, no longer used. + (bswapsi2_internal): Likewise. + (bswap2_load): Split bswap HImode/SImode into separate load, + store, and gpr<-gpr swap insns. + (bswap2_store): Likewise. + (bswaphi2_reg): Register only splitter, combine with the splitter. + (bswaphi2 splitter): Likewise. + (bswapsi2_reg): Likewise. + (bswapsi2 splitter): Likewise. + (bswapdi2): If we have the LDBRX and STDBRX instructions, split + the insns into load, store, and register/register insns. + (bswapdi2_ldbrx): Likewise. + (bswapdi2_load): Likewise. + (bswapdi2_store): Likewise. + (bswapdi2_reg): Likewise. + + 2017-03-25 Uros Bizjak + + PR target/80180 + * config/i386/i386.c (ix86_expand_builtin) + : Do not expand arg0 between + flags reg setting and flags reg using instructions. + : Ditto. Use non-flags reg + clobbering instructions to zero extend op2. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-14 Martin Liska + + PR lto/66295 + * multiple_target.c (expand_target_clones): Drop local.local + flag for default implementation. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-02-22 Martin Liska + + PR lto/79587 + * data-streamer-in.c (streamer_read_gcov_count): Remove assert. + * data-streamer-out.c (streamer_write_gcov_count_stream): + Likewise. + * value-prof.c (stream_out_histogram_value): Make assert more + precise based on type of counter. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-02-03 Martin Liska + + PR lto/66295 + * multiple_target.c (create_dispatcher_calls): Redirect edge + from a caller of a dispatcher. + (expand_target_clones): Make the clones local. + (ipa_target_clone): Do both target clones and resolvers. + (ipa_dispatcher_calls): Remove the pass. + (pass_dispatcher_calls::gate): Likewise. + (make_pass_dispatcher_calls): Likewise. + * passes.def (pass_target_clone): Put as very first IPA early + pass. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-22 Martin Liska + + PR target/79906 + * config/rs6000/rs6000.c (rs6000_inner_target_options): Show + error message instead of an ICE. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-21 Martin Liska + + PR gcov-profile/80081 + * Makefile.in: Add gcov-dump and fix installation of gcov-tool. + * doc/gcc.texi: Include gcov-dump stuff. + * doc/gcov-dump.texi: New file. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-20 Martin Liska + + PR middle-end/79753 + * tree-chkp.c (chkp_build_returned_bound): Do not build + returned bounds for a LHS that's not a BOUNDED_P type. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-20 Martin Liska + + PR target/79769 + PR target/79770 + * tree-chkp.c (chkp_find_bounds_1): Handle REAL_CST, + COMPLEX_CST and VECTOR_CST. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-14 Martin Liska + + PR middle-end/79831 + * doc/invoke.texi (-Wchkp): Document the option. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-14 Martin Liska + + PR target/79892 + * multiple_target.c (create_dispatcher_calls): Check that + a target can create a function dispatcher. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-13 Martin Liska + + PR middle-end/78339 + * ipa-pure-const.c (warn_function_noreturn): If the declarations + is a CHKP clone, use original declaration. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-10 Martin Liska + + PR target/65705 + PR target/69804 + * toplev.c (process_options): Enable MPX with LSAN and UBSAN. + * tree-chkp.c (chkp_walk_pointer_assignments): Verify that + FIELD != NULL. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-09 Martin Liska + + PR tree-optimization/79631 + * tree-chkp-opt.c (chkp_is_constant_addr): Call + tree_int_cst_sign_bit just for INTEGER constants. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-09 Martin Liska + + PR target/65705 + PR target/69804 + * toplev.c (process_options): Disable -fcheck-pointer-bounds with + sanitizers. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-09 Martin Liska + + PR ipa/79761 + * tree-chkp.c (chkp_get_bound_for_parm): Get bounds for a param. + (chkp_find_bounds_1): Remove gcc_unreachable. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-03 Jan Hubicka + + PR lto/79760 + * ipa-devirt.c (maybe_record_node): Properly handle + __cxa_pure_virtual visibility. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-03 Martin Liska + + PR tree-optimization/79803 + * tree-ssa-loop-prefetch.c (tree_ssa_prefetch_arrays): Remove + assert. + (pass_loop_prefetch::execute): Disabled optimization if an + assumption about L1 cache size is not met. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-03 Martin Liska + + PR rtl-optimization/79574 + * gcse.c (struct gcse_expr): Use HOST_WIDE_INT instead of int. + (hash_scan_set): Likewise. + (dump_hash_table): Likewise. + (hoist_code): Likewise. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-02-17 Martin Liska + + PR rtl-optimization/79574 + * gcse.c (want_to_gcse_p): Prevent integer overflow. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-02-17 Martin Liska + + PR rtl-optimization/79577 + * params.def (selsched-max-sched-times): Increase minimum to 1. + + 2017-03-22 Martin Liska + + Backport from mainline + 2016-06-13 Martin Liska + + PR sanitizer/71458 + * toplev.c (process_options): Do not enable -fcheck-pointer-bounds + w/ -fsanitize=bounds. + + 2017-03-21 Pat Haugen + + Backport from mainline: + 2017-03-17 Pat Haugen + + PR target/79951 + * config/rs6000/rs6000.md (copysign3_fcpsgn): Test + for VECTOR_UNIT_VSX_P (mode) too. + + 2017-03-21 Tamar Christina + + * config/aarch64/aarch64-simd.md (*aarch64_simd_mov) + Change ins into fmov. + + 2017-03-19 Dominique d'Humieres + + PR target/71017 + * config/i386/cpuid.h: Fix another undefined behavior. + + 2017-03-17 Tom de Vries + + backport from trunk: + 2017-03-17 Tom de Vries + + * gcov-dump.c (print_usage): Print bug_report_url. + + 2017-03-16 Richard Biener + + Backport from mainline + 2017-02-28 Richard Biener + + PR tree-optimization/79732 + * tree-inline.c (expand_call_inline): Handle anonymous + SSA lhs properly when inlining a function without return + value. + + 2017-03-15 Matthias Klose + + Backport from mainline + 2017-03-14 Martin Liska + + * Makefile.in: Install gcov-dump. + + 2017-03-15 Uros Bizjak + + PR target/80019 + * config/i386/i386.c (ix86_vector_duplicate_value): Create + subreg of inner mode for values already in registers. + + 2017-03-14 Aaron Sawdey + + Backport from mainline + 2017-02-28 Aaron Sawdey + + PR target/79752 + * config/rs6000/rs6000.md (peephole2 for udiv/umod): Should emit + udiv rather than div since input pattern is unsigned. + + 2017-03-14 Richard Biener + + Backport from mainline + 2016-05-02 Jakub Jelinek + + PR middle-end/80004 + PR target/49244 + * gimple.c (gimple_builtin_call_types_compatible_p): Allow + char/short arguments promoted to int because of promote_prototypes. + + 2017-03-09 Richard Biener + + PR tree-optimization/79977 + * graphite-scop-detection.c (scop_detection::merge_sese): + Handle the case of extra exits to blocks dominating the entry. + + 2017-03-09 Richard Biener + + PR middle-end/79971 + * gimple-expr.c (useless_type_conversion_p): Preserve + TYPE_SATURATING for fixed-point types. + + 2017-02-22 Richard Biener + + PR tree-optimization/79666 + * tree-vrp.c (extract_range_from_binary_expr_1): Make sure + to not symbolically negate if that may introduce undefined + overflow. + + 2017-02-17 Richard Biener + + PR middle-end/79576 + * params.def (max-ssa-name-query-depth): Limit to 10. + + 2017-03-07 Uros Bizjak + + Backport from mainline + 2017-03-07 Segher Boessenkool + + * config/i386/i386.c (ix86_local_alignment): Align most aggregates + of 16 bytes and more to 16 bytes, not those of 16 bits and more. + + 2017-03-06 John David Anglin + + PR target/77850 + * config/pa/pa-64.h (PAD_VARARGS_DOWN): Don't pad down complex and + vector types. + + 2017-03-06 Michael Meissner + + Back port from trunk + 2017-03-01 Michael Meissner + + PR target/79439 + * config/rs6000/predicates.md (current_file_function_operand): Do + not allow self calls to be local if the function is replaceable. + + 2017-03-02 Uros Bizjak + + PR target/79514 + * config/i386/i386.md (*pushxf_rounded): New insn_and_split pattern. + + 2017-03-01 Pat Haugen + + Backport from mainline: + 2017-02-27 Pat Haugen + + PR target/79544 + * rs6000/rs6000-c.c (struct altivec_builtin_types): Use VSRAD for + arithmetic shift of unsigned V2DI. + + 2017-03-01 Martin Jambor + + Backport from mainline + 2017-02-21 Martin Jambor + + PR lto/79579 + * ipa-prop.c (ipa_prop_write_jump_functions): Bail out if no edges + have been analyzed. + + 2017-02-28 Eric Botcazou + + PR target/79749 + * config/sparc/sparc.c (sparc_frame_pointer_required): Add missing + condition on optimize for the leaf function test. + + 2017-02-22 Bill Schmidt + + Backport from mainline + 2017-02-17 Bill Schmidt + + PR target/79261 + * config/rs6000/rs6000.c (rs6000_expand_ternop_builtin): Add + support for CODE_FOR_vsx_xxpermdi_v2d[fi]_be. + * config/rs6000/rs6000.md (reload_gpr_from_vsx): Call + generator for vsx_xxpermdi__be. + * config/rs6000/vsx.md (vsx_xxpermdi_): Remove logic to + force big-endian semantics. + (vsx_xxpermdi__be): New define_expand with same + implementation as previous version of vsx_xxpermdi_. + + 2017-02-20 Marek Polacek + + Backport from mainline + 2017-02-20 Marek Polacek + + PR middle-end/79537 + * gimplify.c (gimplify_expr): Handle unused *&&L;. + + PR sanitizer/79558 + * ubsan.c (ubsan_type_descriptor): Check if TYPE_MAX_VALUE is null. + + 2017-02-20 Marek Polacek + + Backport from mainline + 2017-02-17 Marek Polacek + + PR middle-end/79536 + * fold-const.c (fold_negate_expr_1): Renamed from fold_negate_expr. + (fold_negate_expr): New wrapper. + + 2017-02-17 Carl Love + + Backport from mainline commit r245460 on 2017-02-14 + + PR 79545 + * config/rs6000/rs6000.c: Add case statement entry to make the xvcvuxdsp + built-in argument unsigned. + * config/rs6000/vsx.md: Fix the source and return operand types so they + match the instruction definitions from the ISA document. Fix typo + in the instruction generation for the (define_insn "vsx_xvcvuxdsp" + statement. + + 2017-01-17 Julia Koval + + PR target/76731 + * config/i386/avx512fintrin.h + (_mm512_i32gather_ps): Change __addr type to void const*. + (_mm512_mask_i32gather_ps): Ditto. + (_mm512_i32gather_pd): Ditto. + (_mm512_mask_i32gather_pd): Ditto. + (_mm512_i64gather_ps): Ditto. + (_mm512_mask_i64gather_ps): Ditto. + (_mm512_i64gather_pd): Ditto. + (_mm512_mask_i64gather_pd): Ditto. + (_mm512_i32gather_epi32): Ditto. + (_mm512_mask_i32gather_epi32): Ditto. + (_mm512_i32gather_epi64): Ditto. + (_mm512_mask_i32gather_epi64): Ditto. + (_mm512_i64gather_epi32): Ditto. + (_mm512_mask_i64gather_epi32): Ditto. + (_mm512_i64gather_epi64): Ditto. + (_mm512_mask_i64gather_epi64): Ditto. + (_mm512_i32scatter_ps): Change __addr type to void*. + (_mm512_mask_i32scatter_ps): Ditto. + (_mm512_i32scatter_pd): Ditto. + (_mm512_mask_i32scatter_pd): Ditto. + (_mm512_i64scatter_ps): Ditto. + (_mm512_mask_i64scatter_ps): Ditto. + (_mm512_i64scatter_pd): Ditto. + (_mm512_mask_i64scatter_pd): Ditto. + (_mm512_i32scatter_epi32): Ditto. + (_mm512_mask_i32scatter_epi32): Ditto. + (_mm512_i32scatter_epi64): Ditto. + (_mm512_mask_i32scatter_epi64): Ditto. + (_mm512_i64scatter_epi32): Ditto. + (_mm512_mask_i64scatter_epi32): Ditto. + (_mm512_i64scatter_epi64): Ditto. + (_mm512_mask_i64scatter_epi64): Ditto. + * config/i386/avx512pfintrin.h + (_mm512_mask_prefetch_i32gather_pd): Change addr type to void const*. + (_mm512_mask_prefetch_i32gather_ps): Ditto. + (_mm512_mask_prefetch_i64gather_pd): Ditto. + (_mm512_mask_prefetch_i64gather_ps): Ditto. + (_mm512_prefetch_i32scatter_pd): Change addr type to void*. + (_mm512_prefetch_i32scatter_ps): Ditto. + (_mm512_mask_prefetch_i32scatter_pd): Ditto. + (_mm512_mask_prefetch_i32scatter_ps): Ditto. + (_mm512_prefetch_i64scatter_pd): Ditto. + (_mm512_prefetch_i64scatter_ps): Ditto. + (_mm512_mask_prefetch_i64scatter_pd): Ditto. + (_mm512_mask_prefetch_i64scatter_ps): Ditto. + * config/i386/avx512vlintrin.h + (_mm256_mmask_i32gather_ps): Change __addr type to void const*. + (_mm_mmask_i32gather_ps): Ditto. + (_mm256_mmask_i32gather_pd): Ditto. + (_mm_mmask_i32gather_pd): Ditto. + (_mm256_mmask_i64gather_ps): Ditto. + (_mm_mmask_i64gather_ps): Ditto. + (_mm256_mmask_i64gather_pd): Ditto. + (_mm_mmask_i64gather_pd): Ditto. + (_mm256_mmask_i32gather_epi32): Ditto. + (_mm_mmask_i32gather_epi32): Ditto. + (_mm256_mmask_i32gather_epi64): Ditto. + (_mm_mmask_i32gather_epi64): Ditto. + (_mm256_mmask_i64gather_epi32): Ditto. + (_mm_mmask_i64gather_epi32): Ditto. + (_mm256_mmask_i64gather_epi64): Ditto. + (_mm_mmask_i64gather_epi64): Ditto. + (_mm256_i32scatter_ps): Change __addr type to void*. + (_mm256_mask_i32scatter_ps): Ditto. + (_mm_i32scatter_ps): Ditto. + (_mm_mask_i32scatter_ps): Ditto. + (_mm256_i32scatter_pd): Ditto. + (_mm256_mask_i32scatter_pd): Ditto. + (_mm_i32scatter_pd): Ditto. + (_mm_mask_i32scatter_pd): Ditto. + (_mm256_i64scatter_ps): Ditto. + (_mm256_mask_i64scatter_ps): Ditto. + (_mm_i64scatter_ps): Ditto. + (_mm_mask_i64scatter_ps): Ditto. + (_mm256_i64scatter_pd): Ditto. + (_mm256_mask_i64scatter_pd): Ditto. + (_mm_i64scatter_pd): Ditto. + (_mm_mask_i64scatter_pd): Ditto. + (_mm256_i32scatter_epi32): Ditto. + (_mm256_mask_i32scatter_epi32): Ditto. + (_mm_i32scatter_epi32): Ditto. + (_mm_mask_i32scatter_epi32): Ditto. + (_mm256_i32scatter_epi64): Ditto. + (_mm256_mask_i32scatter_epi64): Ditto. + (_mm_i32scatter_epi64): Ditto. + (_mm_mask_i32scatter_epi64): Ditto. + (_mm256_i64scatter_epi32): Ditto. + (_mm256_mask_i64scatter_epi32): Ditto. + (_mm_i64scatter_epi32): Ditto. + (_mm_mask_i64scatter_epi32): Ditto. + (_mm256_i64scatter_epi64): Ditto. + (_mm256_mask_i64scatter_epi64): Ditto. + (_mm_i64scatter_epi64): Ditto. + (_mm_mask_i64scatter_epi64): Ditto. + * config/i386/i386-builtin-types.def (V16SF_V16SF_PCFLOAT_V16SI_HI_INT) + (V8DF_V8DF_PCDOUBLE_V8SI_QI_INT, V8SF_V8SF_PCFLOAT_V8DI_QI_INT) + (V8DF_V8DF_PCDOUBLE_V8DI_QI_INT, V16SI_V16SI_PCINT_V16SI_HI_INT) + (V8DI_V8DI_PCINT64_V8SI_QI_INT, V8SI_V8SI_PCINT_V8DI_QI_INT) + (V8DI_V8DI_PCINT64_V8DI_QI_INT, V2DF_V2DF_PCDOUBLE_V4SI_QI_INT) + (V4DF_V4DF_PCDOUBLE_V4SI_QI_INT, V2DF_V2DF_PCDOUBLE_V2DI_QI_INT) + (V4DF_V4DF_PCDOUBLE_V4DI_QI_INT, V4SF_V4SF_PCFLOAT_V4SI_QI_INT) + (V8SF_V8SF_PCFLOAT_V8SI_QI_INT, V4SF_V4SF_PCFLOAT_V2DI_QI_INT) + (V4SF_V4SF_PCFLOAT_V4DI_QI_INT, V2DI_V2DI_PCINT64_V4SI_QI_INT) + (V4DI_V4DI_PCINT64_V4SI_QI_INT, V2DI_V2DI_PCINT64_V2DI_QI_INT) + (V4DI_V4DI_PCINT64_V4DI_QI_INT, V4SI_V4SI_PCINT_V4SI_QI_INT) + (V8SI_V8SI_PCINT_V8SI_QI_INT, V4SI_V4SI_PCINT_V2DI_QI_INT) + (V4SI_V4SI_PCINT_V4DI_QI_INT, VOID_PFLOAT_HI_V16SI_V16SF_INT) + (VOID_PFLOAT_QI_V8SI_V8SF_INT, VOID_PFLOAT_QI_V4SI_V4SF_INT) + (VOID_PDOUBLE_QI_V8SI_V8DF_INT, VOID_PDOUBLE_QI_V4SI_V4DF_INT) + (VOID_PDOUBLE_QI_V4SI_V2DF_INT, VOID_PFLOAT_QI_V8DI_V8SF_INT) + (VOID_PFLOAT_QI_V4DI_V4SF_INT, VOID_PFLOAT_QI_V2DI_V4SF_INT) + (VOID_PDOUBLE_QI_V8DI_V8DF_INT, VOID_PDOUBLE_QI_V4DI_V4DF_INT) + (VOID_PDOUBLE_QI_V2DI_V2DF_INT, VOID_PINT_HI_V16SI_V16SI_INT) + (VOID_PINT_QI_V8SI_V8SI_INT, VOID_PINT_QI_V4SI_V4SI_INT) + (VOID_PLONGLONG_QI_V8SI_V8DI_INT, VOID_PLONGLONG_QI_V4SI_V4DI_INT) + (VOID_PLONGLONG_QI_V4SI_V2DI_INT, VOID_PINT_QI_V8DI_V8SI_INT) + (VOID_PINT_QI_V4DI_V4SI_INT, VOID_PINT_QI_V2DI_V4SI_INT) + (VOID_PLONGLONG_QI_V8DI_V8DI_INT, VOID_QI_V8SI_PCINT64_INT_INT) + (VOID_PLONGLONG_QI_V4DI_V4DI_INT, VOID_PLONGLONG_QI_V2DI_V2DI_INT) + (VOID_HI_V16SI_PCINT_INT_INT, VOID_QI_V8DI_PCINT64_INT_INT) + (VOID_QI_V8DI_PCINT_INT_INT): Remove. + (V16SF_V16SF_PCVOID_V16SI_HI_INT, V8DF_V8DF_PCVOID_V8SI_QI_INT) + (V8SF_V8SF_PCVOID_V8DI_QI_INT, V8DF_V8DF_PCVOID_V8DI_QI_INT) + (V16SI_V16SI_PCVOID_V16SI_HI_INT, V8DI_V8DI_PCVOID_V8SI_QI_INT) + (V8SI_V8SI_PCVOID_V8DI_QI_INT, V8DI_V8DI_PCVOID_V8DI_QI_INT) + (VOID_PVOID_HI_V16SI_V16SF_INT, VOID_PVOID_QI_V8SI_V8DF_INT) + (VOID_PVOID_QI_V8DI_V8SF_INT, VOID_PVOID_QI_V8DI_V8DF_INT) + (VOID_PVOID_HI_V16SI_V16SI_INT, VOID_PVOID_QI_V8SI_V8DI_INT) + (VOID_PVOID_QI_V8DI_V8SI_INT, VOID_PVOID_QI_V8DI_V8DI_INT) + (V2DF_V2DF_PCVOID_V4SI_QI_INT, V4DF_V4DF_PCVOID_V4SI_QI_INT) + (V2DF_V2DF_PCVOID_V2DI_QI_INT, V4DF_V4DF_PCVOID_V4DI_QI_INT + (V4SF_V4SF_PCVOID_V4SI_QI_INT, V8SF_V8SF_PCVOID_V8SI_QI_INT) + (V4SF_V4SF_PCVOID_V2DI_QI_INT, V4SF_V4SF_PCVOID_V4DI_QI_INT) + (V2DI_V2DI_PCVOID_V4SI_QI_INT, V4DI_V4DI_PCVOID_V4SI_QI_INT) + (V2DI_V2DI_PCVOID_V2DI_QI_INT, V4DI_V4DI_PCVOID_V4DI_QI_INT) + (V4SI_V4SI_PCVOID_V4SI_QI_INT, V8SI_V8SI_PCVOID_V8SI_QI_INT) + (V4SI_V4SI_PCVOID_V2DI_QI_INT, V4SI_V4SI_PCVOID_V4DI_QI_INT) + (VOID_PVOID_QI_V8SI_V8SF_INT, VOID_PVOID_QI_V4SI_V4SF_INT) + (VOID_PVOID_QI_V4SI_V4DF_INT, VOID_PVOID_QI_V4SI_V2DF_INT) + (VOID_PVOID_QI_V4DI_V4SF_INT, VOID_PVOID_QI_V2DI_V4SF_INT) + (VOID_PVOID_QI_V4DI_V4DF_INT, VOID_PVOID_QI_V2DI_V2DF_INT) + (VOID_PVOID_QI_V8SI_V8SI_INT, VOID_PVOID_QI_V4SI_V4SI_INT) + (VOID_PVOID_QI_V4SI_V4DI_INT, VOID_PVOID_QI_V4SI_V2DI_INT) + (VOID_PVOID_QI_V4DI_V4SI_INT, VOID_PVOID_QI_V2DI_V4SI_INT) + (VOID_PVOID_QI_V4DI_V4DI_INT, VOID_PVOID_QI_V2DI_V2DI_INT) + (VOID_QI_V8SI_PCVOID_INT_INT, VOID_HI_V16SI_PCVOID_INT_INT) + (VOID_QI_V8DI_PCVOID_INT_INT): Add. + * config/i386/i386.c (ix86_init_mmx_sse_builtins): Adjust builtin + definitions accordingly. + + 2017-02-16 Jakub Jelinek + + Backported from mainline + 2017-02-09 Marek Polacek + + PR c/79428 + * c-parser.c (c_parser_omp_ordered): Call c_parser_skip_to_pragma_eol + instead of c_parser_skip_until_found. + + 2017-02-15 Jakub Jelinek + + Backported from mainline + 2017-02-10 Jakub Jelinek + + PR tree-optimization/79411 + * tree-ssa-reassoc.c (is_reassociable_op): Return false if + stmt operands are SSA_NAMEs used in abnormal phis. + (can_reassociate_p): Return false if op is SSA_NAME used in abnormal + phis. + + 2017-02-09 Jakub Jelinek + + PR c/79431 + * gimplify.c (gimplify_adjust_omp_clauses): Ignore + "omp declare target link" attribute unless is_global_var. + * omp-low.c (find_link_var_op): Likewise. + + 2017-02-07 Jakub Jelinek + Richard Biener + + PR middle-end/79399 + * ira-int.h (struct target_ira_int): Change x_max_struct_costs_size + type from int to size_t. + * ira-costs.c (struct_costs_size): Change type from int to size_t. + + 2017-02-04 Jakub Jelinek + + PR tree-optimization/79338 + * tree-parloops.c (gather_scalar_reductions): Don't call + vect_analyze_loop_form for loop->inner before destroying loop's + loop_vinfo. + + 2017-02-02 Jakub Jelinek + + PR target/79197 + * config/rs6000/rs6000.md (*fixuns_truncdi2_fctiduz): Rename to ... + (fixuns_truncdi2): ... this, remove previous expander. Put all + conditions on a single line. + + 2017-01-31 Jakub Jelinek + + PR tree-optimization/79267 + * value-prof.c (gimple_ic): Only drop lhs for noreturn calls + if should_remove_lhs_p is true. + + 2017-01-17 Kito Cheng + Kuan-Lin Chen + + PR target/79079 + * internal-fn.c (expand_mul_overflow): Use convert_modes instead of + gen_lowpart. + + 2017-02-14 Uros Bizjak + + PR target/79495 + * config/i386/i386.md (*movxf_internal): Add (o,rC) alternative. + + 2017-02-14 Martin Liska + + Backport from mainline + 2017-02-13 Martin Liska + + PR c/79471 + * calls.c (expand_call): Replace XALLOCAVEC with XCNEWVEC. + + 2017-02-13 Gerald Pfeifer + + Backport from mainline + 2016-12-11 Roger Pau Monné + + * config/i386/x86-64.h: Append --32 to the assembler options when + -m16 is used on non-glibc systems as well. + + 2017-02-08 Segher Boessenkool + + PR translation/79397 + * config/rs6000/rs6000.opt (maltivec=le, maltivec=be): Fix spelling + of AltiVec. + + 2017-02-08 Richard Biener + + Backport from mainline + 2017-02-08 Richard Biener + + PR tree-optimization/71824 + * graphite-scop-detection.c (scop_detection::build_scop_breadth): + Check all loops contained in the merged region. + + 2017-02-01 Richard Biener + + PR tree-optimization/71824 + * graphite-scop-detection.c (scop_detection::build_scop_breadth): + Verify the loops are valid in the merged SESE region. + (scop_detection::can_represent_loop_1): Check analyzing the + evolution of the number of iterations in the region succeeds. + + 2017-01-31 Richard Biener + + PR tree-optimization/77318 + * graphite-sese-to-poly.c (extract_affine): Fix assert. + (create_pw_aff_from_tree): Take loop parameter. + (add_condition_to_pbb): Pass loop of the condition to + create_pw_aff_from_tree. + + 2017-02-06 Dominique d'Humieres + + PR target/71017 + * config/i386/cpuid.h: Fix undefined behavior. + + 2017-02-03 Carl Love + + Backport of two commits from mainline, r244943 and r244904, + dated 017-01-26 and 2017-01-25 respectively + + * config/rs6000/rs6000-c (altivec_overloaded_builtins): Fix order + of entries for ALTIVEC_BUILTIN_VEC_PACKS. Remove bogus entries + for P8V_BUILTIN_VEC_VGBBD. + + 2017-02-03 Walter Lee + + Backport from mainline + 2017-02-03 Walter Lee + + PR target/78862 + * config/tilegx/tilegx.md (tilegx_expand_prologue): Add blockage + after initial stackframe link reg save. + * config/tilepro/tilepro.md (tilepro_expand_prologue): Likewise. + + 2017-02-03 Maxim Ostapenko + + PR lto/79061 + * asan.c (asan_add_global): Force has_dynamic_init to zero in LTO mode. + + 2017-01-31 Bill Schmidt + + Backport from mainline + 2017-01-29 Bill Schmidt + + PR target/79268 + * config/rs6000/altivec.h (vec_xl): Revise #define. + (vec_xst): Likewise. + + 2017-01-26 Eric Botcazou + + Backport from mainline + 2017-01-10 Eric Botcazou + + * expr.c (store_field): In the bitfield case, fetch the return value + from the registers before applying a single big-endian adjustment. + Always do a final load for a BLKmode value not larger than a word. + + 2017-01-09 Eric Botcazou + + * expr.c (store_field): In the bitfield case, if the value comes from + a function call and is of an aggregate type returned in registers, do + not modify the field mode; extract the value in all cases if the mode + is BLKmode and the size is not larger than a word. + + 2017-01-26 Richard Biener + + * tree-vrp.c (vrp_visit_assignment_or_call): Use set_defs_to_varying. + + Backport from mainline + 2016-01-10 Richard Biener + + PR tree-optimization/79034 + * tree-call-cdce.c (shrink_wrap_one_built_in_call_with_conds): + Propagate out degenerate PHIs in the joiner. + + 2016-12-13 Richard Biener + + PR middle-end/78742 + * tree.c (cst_and_fits_in_hwi): Look if the actual value fits. + * tree-object-size.c (compute_builtin_object_size): Use + tree_fits_shwi_p. + * tree-data-ref.c (initialize_matrix_A): Remove excess assert. + + 2017-01-26 Richard Biener + + Backport from mainline + 2016-09-03 Kirill Yukhin + + * ubsan.c (ubsan_use_new_style_p): Fix check for empty string. + + 2017-01-24 Eric Botcazou + + PR target/77439 + * config/arm/arm.c (arm_function_ok_for_sibcall): Add back restriction + for long calls with APCS frame and VFP. + + 2017-01-24 Uros Bizjak + + PR target/78478 + Revert: + 2013-11-05 Uros Bizjak + + * config/i386/rtemself.h (LONG_DOUBLE_TYPE_SIZE): New define. + + 2017-01-23 Martin Liska + + Backport from mainline + 2017-01-20 Martin Liska + + PR lto/69188 + * tree-profile.c (init_ic_make_global_vars): Do not call + finalize_decl. + (gimple_init_gcov_profiler): Likewise. + + 2017-01-21 Gerald Pfeifer + + Backport from mainline + 2016-12-29 Gerald Pfeifer + + * doc/extend.texi (Cilk Plus Builtins): cilkplus.org now uses + https by default. + * doc/passes.texi (Cilk Plus Transformation): Ditto. + * doc/generic.texi (Statements for C++): Ditto, and use @uref. + + 2017-01-20 Bill Schmidt + + Backport from mainline + 2017-01-16 Bill Schmidt + + * config/rs6000/rs6000.c (rtx_is_swappable_p): Change + UNSPEC_VSX__XXSPLTD to require special splat handling. + + 2017-01-20 Wilco Dijkstra + + Backport from mainline + PR target/77455 + * config/aarch64/aarch64.md (eh_return): Remove pattern and splitter. + * config/aarch64/aarch64.h (AARCH64_EH_STACKADJ_REGNUM): Remove. + (EH_RETURN_HANDLER_RTX): New define. + * config/aarch64/aarch64.c (aarch64_frame_pointer_required): + Force frame pointer in EH return functions. + (aarch64_expand_epilogue): Add barrier for eh_return. + (aarch64_final_eh_return_addr): Remove. + (aarch64_eh_return_handler_rtx): New function. + * config/aarch64/aarch64-protos.h (aarch64_final_eh_return_addr): + Remove. + (aarch64_eh_return_handler_rtx): New prototype. + + 2017-01-20 Richard Earnshaw + + Backported from mainline + 2017-01-19 Richard Earnshaw + + PR rtl-optimization/79121 + * expr.c (expand_expr_real_2, case LSHIFT_EXPR): Look at the signedness + of the inner type when shifting an extended value. + + 2017-01-20 Martin Liska + + Backport from mainline + 2017-01-13 Martin Liska + + PR ipa/79043 + * function.c (set_cfun): Add new argument force. + * function.h (set_cfun): Likewise. + * ipa-inline-transform.c (inline_call): Use the function when + strict alising from is dropped for function we inline to. + + 2017-01-20 Martin Liska + + Backport from mainline + 2017-01-17 Martin Liska + + PR ipa/71207 + * ipa-polymorphic-call.c (contains_type_p): Fix wrong + assumption and add comment. + + 2017-01-19 Richard Biener + + PR tree-optimization/72488 + * tree-ssa-sccvn.c (run_scc_vn): When we abort the VN make + sure to restore SSA info. + + 2017-01-17 Jakub Jelinek + + PR debug/78839 + * dwarf2out.c (field_byte_offset): Restore the + PCC_BITFIELD_TYPE_MATTERS behavior for INTEGER_CST DECL_FIELD_OFFSET + and DECL_FIELD_BIT_OFFSET. Use fold_build2 instead of build2 + fold. + (analyze_variants_discr, gen_variant_part): Use fold_build2 instead + of build2 + fold. + + 2017-01-17 Thomas Preud'homme + + Backport from mainline + 2016-12-07 Thomas Preud'homme + + PR rtl-optimization/78617 + * lra-remat.c (do_remat): Initialize live_hard_regs from live in + registers, also setting hard registers mapped to pseudo registers. + + 2017-01-13 Christophe Lyon + + Backport from mainline r244320. + 2017-01-11 Christophe Lyon + + PR target/78253 + * config/arm/arm.c (legitimize_pic_address): Handle reference to + weak symbol. + (arm_assemble_integer): Likewise. + + 2017-01-12 Bill Schmidt + + Backport from mainline + 2017-01-12 Bill Schmidt + + PR target/79044 + * config/rs6000/rs6000.c (insn_is_swappable_p): Mark + element-reversing loads and stores as not swappable. + + 2017-01-11 Uros Bizjak + + * config/i386/i386.c (memory_address_length): Increase len + only when rip_relative_addr_p returns false. + + 2017-01-11 Maxim Ostapenko + + Backport from mainline + 2017-01-11 Maxim Ostapenko + + PR lto/79042 + * lto-cgraph.c (lto_output_varpool_node): Pack dynamically_initialized + bit. + (input_varpool_node): Unpack dynamically_initialized bit. + * lto-streamer.h (LTO_minor_version): Bump version. + + 2017-01-10 Michael Meissner + + Backport from mainline + 2016-12-30 Michael Meissner + + PR target/78900 + * config/rs6000/rs6000.c (rs6000_split_signbit): Change some + assertions. Add support for doing the signbit if the IEEE 128-bit + floating point value is in a GPR. + * config/rs6000/rs6000.md (Fsignbit): Delete. + (signbit2_dm): Delete using and just use "wa". + Update the length attribute if the value is in a GPR. + (signbit2_dm_ext): Add combiner pattern to eliminate + the sign or zero extension instruction, since the value is always + 0/1. + (signbit2_dm2): Delete using . + + 2017-01-10 Martin Liska + + Backport from mainline + 2017-01-09 Martin Liska + + PR pch/78970 + * gcc.c (driver_handle_option): Handle OPT_E and set + have_E. + (lookup_compiler): Do not show error message with have_E. + + 2017-01-10 Martin Liska + + Backport from mainline + 2017-01-05 Martin Liska + + PR pch/78970 + * gcc.c (lookup_compiler): Reject '-' filename for a precompiled + header. + + 2017-01-10 Thomas Schwinge + + PR tree-optimization/78024 + * omp-low.c (oacc_loop_discovery): Call clear_bb_flags. + + Backport trunk r239086: + 2016-08-03 Nathan Sidwell + + * config/nvptx/nvptx.c (nvptx_declare_function_name): Round frame + size to DImode boundary. + (nvptx_propagate): Likewise. + + 2017-01-10 Chung-Ju Wu + + Backport from mainline + 2016-04-28 Segher Boessenkool + + PR target/70668 + * config/nds32/nds32.md (casesi): Don't access the operands array + out of bounds. + + 2017-01-09 Andreas Tobler + + Backport from mainline + 2016-10-10 Andreas Tobler + + * config.gcc: Add aarch64-*-freebsd* support. + * config.host: Likewise. + * config/aarch64/aarch64-freebsd.h: New file. + * config/aarch64/t-aarch64-freebsd: Ditto. + + 2017-01-09 Bill Seurer + + Backport from mainline + 2016-12-21 Bill Seurer + + PR sanitizer/65479 + * config/rs6000/rs6000.c (rs6000_option_override_internal): Add + -fasynchronous-unwind-tables option when -fsanitize=address is + specified. + + 2017-01-09 Andreas Tobler + + Backport from mainline + 2016-09-19 Richard Biener + + * dwarf2out.c (dwarf2out_late_global_decl): When being during the + early debug phase do not add locations but only const value + attributes. + + Backport from mainline + 2016-10-20 Richard Biener + + * cgraphunit.c (analyze_functions): Set node->definition to + false to signal symbol removal to debug_hooks->late_global_decl. + + 2017-01-09 Andre Vieira + + Backport from mainline + 2016-12-09 Andre Vieira + + PR rtl-optimization/78255 + * gcc/postreload.c (reload_cse_simplify): Do not CSE a function if + NO_FUNCTION_CSE is true. + + 2017-01-06 Wilco Dijkstra + + Backport from mainline + 2016-10-25 Wilco Dijkstra + + PR target/78041 + * config/arm/neon.md (ashldi3_neon): Add "r 0 i" and "&r r i" variants. + Remove partial overlap check for shift by 1. + (ashldi3_neon): Likewise. + + 2017-01-05 Kelvin Nilsen + + Backport from mainline + 2016-07-22 Kelvin Nilsen + + * config/rs6000/rs6000.c (rs6000_option_override_internal): Add + comments to explain why certain error messages make mention of + undocumented options. + (rs6000_invalid_builtin): Change error messages to replace mention + of undocumented options with mention of the -mcpu=power9 option + that enables those undocumented options. + * config/rs6000/rs6000.h: Add macro definition of MASK_FLOAT128 + and change the macro definition of RS6000_BTM_FLOAT128 to correct + an error that was discovered during the development of this patch. + * config/rs6000/rs6000.opt: Add the Undocumented qualifier to the + mpower9-fusion, mpower9-vector, mpower9-dform, and mmodulo entries. + * doc/extend.texi (PowerPC AltiVec Built-in Functions): Modify + descriptions of built-in functions so that they depend on + -mcpu=power9 instead of on the corresponding undocumented flags. + * doc/invoke.texi (Option Summary): Remove all mention of newly + undocumented flags. + (IBM RS/6000 and PowerPC Options): Likewise. + * doc/md.texi (Constraints for Particuliar Machines): Remove all + mention of newly undocumented flags. + + 2017-01-05 Andreas Krebbel + + Backport from mainline + 2016-12-22 Andreas Krebbel + + * varasm.c (build_constant_desc): Use the alignment of the var + decl instead of the original expression. + + 2017-01-04 Richard Biener + + Backport from mainline + 2016-05-11 Richard Biener + + PR tree-optimization/71055 + * tree-ssa-sccvn.c (vn_reference_lookup_3): When native-interpreting + sth with precision not equal to access size verify we don't chop + off bits. + + 2017-01-03 Martin Liska + + Backport from mainline + 2016-12-21 Jakub Jelinek + Martin Liska + + PR driver/78863 + * gcc.c (driver::build_option_suggestions): Do not add + -fsanitize=all as a suggestion candidate. + + 2017-01-03 Martin Liska + + Backport from mainline + 2016-12-22 Martin Liska + + PR tree-optimization/78886 + * tree-ssa-strlen.c (handle_builtin_malloc): Return when LHS + is equal to NULL. + + 2017-01-03 Martin Liska + + Backport from mainline + 2016-12-13 Martin Liska + + PR tree-optimization/78428 + * expr.c (store_constructor_field): Add new arguments to the + function. + (store_constructor): Set up bitregion_end and add + gcc_unreachable to fields that have either non-constant size + or (and) offset. + + 2016-12-27 Jakub Jelinek + + PR translation/78922 + * config/i386/stringop.opt: Remove. + + 2016-12-21 Jakub Jelinek + + Backported from mainline + 2016-12-13 Jakub Jelinek + + PR ipa/77905 + * ipa-pure-const.c (cdtor_p): Return true for + DECL_STATIC_{CON,DE}STRUCTOR even when it is + DECL_LOOPING_CONST_OR_PURE_P. + + 2016-12-21 Jakub Jelinek + + * BASE-VER: Set to 6.3.1. + 2016-12-21 Release Manager * GCC 6.3.0 released. *************** *** 68,78 **** Backport from mainline 2016-11-07 Bernd Schmidt ! PR rtl-optimization/77309 ! * combine.c (make_compound_operation): Allow EQ for IN_CODE, and ! don't assume an equality comparison for plain COMPARE. ! (simplify_comparison): Pass a more accurate code to ! make_compound_operation. 2016-12-12 Thomas Preud'homme --- 2480,2490 ---- Backport from mainline 2016-11-07 Bernd Schmidt ! PR rtl-optimization/77309 ! * combine.c (make_compound_operation): Allow EQ for IN_CODE, and ! don't assume an equality comparison for plain COMPARE. ! (simplify_comparison): Pass a more accurate code to ! make_compound_operation. 2016-12-12 Thomas Preud'homme diff -Nrcpad gcc-6.3.0/gcc/DATESTAMP gcc-6.4.0/gcc/DATESTAMP *** gcc-6.3.0/gcc/DATESTAMP Wed Dec 21 00:16:13 2016 --- gcc-6.4.0/gcc/DATESTAMP Tue Jul 4 00:16:13 2017 *************** *** 1 **** ! 20161221 --- 1 ---- ! 20170704 diff -Nrcpad gcc-6.3.0/gcc/Makefile.in gcc-6.4.0/gcc/Makefile.in *** gcc-6.3.0/gcc/Makefile.in Tue Nov 22 17:33:07 2016 --- gcc-6.4.0/gcc/Makefile.in Fri May 5 21:56:33 2017 *************** GCC_TARGET_INSTALL_NAME := $(target_nonc *** 787,792 **** --- 787,793 ---- CPP_INSTALL_NAME := $(shell echo cpp|sed '$(program_transform_name)') GCOV_INSTALL_NAME := $(shell echo gcov|sed '$(program_transform_name)') GCOV_TOOL_INSTALL_NAME := $(shell echo gcov-tool|sed '$(program_transform_name)') + GCOV_DUMP_INSTALL_NAME := $(shell echo gcov-dump|sed '$(program_transform_name)') # Setup the testing framework, if you have one EXPECT = `if [ -f $${rootme}/../expect/expect ] ; then \ *************** s-specs : Makefile *** 2047,2052 **** --- 2048,2054 ---- optionlist: s-options ; @true s-options: $(ALL_OPT_FILES) Makefile $(srcdir)/opt-gather.awk + LC_ALL=C ; export LC_ALL ; \ $(AWK) -f $(srcdir)/opt-gather.awk $(ALL_OPT_FILES) > tmp-optionlist $(SHELL) $(srcdir)/../move-if-change tmp-optionlist optionlist $(STAMP) s-options *************** TEXI_GCC_FILES = gcc.texi gcc-common.tex *** 2976,2982 **** gcov.texi trouble.texi bugreport.texi service.texi \ contribute.texi compat.texi funding.texi gnu.texi gpl_v3.texi \ fdl.texi contrib.texi cppenv.texi cppopts.texi avr-mmcu.texi \ ! implement-c.texi implement-cxx.texi gcov-tool.texi # we explicitly use $(srcdir)/doc/tm.texi here to avoid confusion with # the generated tm.texi; the latter might have a more recent timestamp, --- 2978,2984 ---- gcov.texi trouble.texi bugreport.texi service.texi \ contribute.texi compat.texi funding.texi gnu.texi gpl_v3.texi \ fdl.texi contrib.texi cppenv.texi cppopts.texi avr-mmcu.texi \ ! implement-c.texi implement-cxx.texi gcov-tool.texi gcov-dump.texi # we explicitly use $(srcdir)/doc/tm.texi here to avoid confusion with # the generated tm.texi; the latter might have a more recent timestamp, *************** $(build_htmldir)/gccinstall/index.html: *** 3099,3105 **** $(SHELL) $(srcdir)/doc/install.texi2html MANFILES = doc/gcov.1 doc/cpp.1 doc/gcc.1 doc/gfdl.7 doc/gpl.7 \ ! doc/fsf-funding.7 doc/gcov-tool.1 generated-manpages: man --- 3101,3107 ---- $(SHELL) $(srcdir)/doc/install.texi2html MANFILES = doc/gcov.1 doc/cpp.1 doc/gcc.1 doc/gfdl.7 doc/gpl.7 \ ! doc/fsf-funding.7 doc/gcov-tool.1 doc/gcov-dump.1 generated-manpages: man *************** install-common: native lang.install-comm *** 3408,3413 **** --- 3410,3424 ---- gcov-tool$(exeext) $(DESTDIR)$(bindir)/$(GCOV_TOOL_INSTALL_NAME)$(exeext); \ fi; \ fi + # Install gcov-dump if it was compiled. + -if test "$(enable_as_accelerator)" != "yes" ; then \ + if [ -f gcov-dump$(exeext) ]; \ + then \ + rm -f $(DESTDIR)$(bindir)/$(GCOV_DUMP_INSTALL_NAME)$(exeext); \ + $(INSTALL_PROGRAM) \ + gcov-dump$(exeext) $(DESTDIR)$(bindir)/$(GCOV_DUMP_INSTALL_NAME)$(exeext); \ + fi; \ + fi # Install the driver program as $(target_noncanonical)-gcc, # $(target_noncanonical)-gcc-$(version), and also as gcc if native. *************** install-man: lang.install-man \ *** 3491,3496 **** --- 3502,3509 ---- $(DESTDIR)$(man1dir)/$(GCC_INSTALL_NAME)$(man1ext) \ $(DESTDIR)$(man1dir)/$(CPP_INSTALL_NAME)$(man1ext) \ $(DESTDIR)$(man1dir)/$(GCOV_INSTALL_NAME)$(man1ext) \ + $(DESTDIR)$(man1dir)/$(GCOV_TOOL_INSTALL_NAME)$(man1ext) \ + $(DESTDIR)$(man1dir)/$(GCOV_DUMP_INSTALL_NAME)$(man1ext) \ $(DESTDIR)$(man7dir)/fsf-funding$(man7ext) \ $(DESTDIR)$(man7dir)/gfdl$(man7ext) \ $(DESTDIR)$(man7dir)/gpl$(man7ext) *************** $(DESTDIR)$(man1dir)/$(GCOV_TOOL_INSTALL *** 3519,3524 **** --- 3532,3542 ---- -rm -f $@ -$(INSTALL_DATA) $< $@ -chmod a-x $@ + + $(DESTDIR)$(man1dir)/$(GCOV_DUMP_INSTALL_NAME)$(man1ext): doc/gcov-dump.1 installdirs + -rm -f $@ + -$(INSTALL_DATA) $< $@ + -chmod a-x $@ # Install all the header files built in the include subdirectory. install-headers: $(INSTALL_HEADERS_DIR) diff -Nrcpad gcc-6.3.0/gcc/ada/ChangeLog gcc-6.4.0/gcc/ada/ChangeLog *** gcc-6.3.0/gcc/ada/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/ada/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,59 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-03-28 Andreas Schwab + + Backport from trunk + + 2017-03-28 Andreas Schwab + + PR ada/80117 + * system-linux-aarch64-ilp32.ads: New file. + * gcc-interface/Makefile.in (LIBGNAT_TARGET_PAIRS_COMMON): Rename + from LIBGNAT_TARGET_PAIRS. + (LIBGNAT_TARGET_PAIRS_32, LIBGNAT_TARGET_PAIRS_64): Define. + (LIBGNAT_TARGET_PAIRS): Use LIBGNAT_TARGET_PAIRS_COMMON, and + LIBGNAT_TARGET_PAIRS_64 or LIBGNAT_TARGET_PAIRS_32 for -mabi=lp64 + or -mabi=ilp32, resp. + + 2017-03-08 Thanassis Tsiodras + + PR ada/79903 + * socket.c (__gnat_gethostbyaddr): Add missing test for __rtems__. + + 2017-03-08 Eric Botcazou + + PR ada/79945 + * system-linux-ppc.ads (Default_Bit_Order): Use Standard's setting. + + 2017-02-24 Eric Botcazou + + * gcc-interface/decl.c (gnat_to_gnu_field): Do not remove the wrapper + around a justified modular type if it doesn't have the same scalar + storage order as the enclosing record type. + + 2017-02-24 Eric Botcazou + + * gcc-interface/trans.c (gnat_to_gnu): Do not apply special handling + of boolean rvalues to function calls. + + 2017-02-24 Eric Botcazou + + * gcc-interface/utils.c (fold_bit_position): New function. + (rest_of_record_type_compilation): Call it instead of bit_position to + compute the field position and remove the call to remove_conversions. + (compute_related_constant): Factor out the multiplication in both + operands, if any, and streamline the final test. + + 2017-02-24 Eric Botcazou + + * gcc-interface/trans.c (return_value_ok_for_nrv_p): Add sanity check. + + 2017-02-12 John Marino + + * gcc-interface/Makefile.in: Support aarch64-freebsd. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/ada/gcc-interface/Makefile.in gcc-6.4.0/gcc/ada/gcc-interface/Makefile.in *** gcc-6.3.0/gcc/ada/gcc-interface/Makefile.in Tue Oct 11 20:03:58 2016 --- gcc-6.4.0/gcc/ada/gcc-interface/Makefile.in Tue Mar 28 14:22:29 2017 *************** ifeq ($(strip $(filter-out x86_64 kfreeb *** 1475,1480 **** --- 1475,1508 ---- LIBRARY_VERSION := $(LIB_VERSION) endif + # aarch64 FreeBSD + ifeq ($(strip $(filter-out %aarch64 freebsd%,$(target_cpu) $(target_os))),) + LIBGNAT_TARGET_PAIRS = \ + a-intnam.ads DECL_ALIGN (ret_obj)) return false; + /* For the unconstrained case, test for bogus initialization. */ + if (!ret_obj + && DECL_INITIAL (ret_val) + && TREE_CODE (DECL_INITIAL (ret_val)) == NULL_EXPR) + return false; + return true; } *************** gnat_to_gnu (Node_Id gnat_node) *** 7696,7702 **** && (kind == N_Identifier || kind == N_Expanded_Name || kind == N_Explicit_Dereference - || kind == N_Function_Call || kind == N_Indexed_Component || kind == N_Selected_Component) && TREE_CODE (get_base_type (gnu_result_type)) == BOOLEAN_TYPE --- 7703,7708 ---- diff -Nrcpad gcc-6.3.0/gcc/ada/gcc-interface/utils.c gcc-6.4.0/gcc/ada/gcc-interface/utils.c *** gcc-6.3.0/gcc/ada/gcc-interface/utils.c Wed Dec 7 11:29:39 2016 --- gcc-6.4.0/gcc/ada/gcc-interface/utils.c Fri Feb 24 10:49:05 2017 *************** static GTY ((cache)) *** 238,243 **** --- 238,244 ---- hash_table *pad_type_hash_table; static tree merge_sizes (tree, tree, tree, bool, bool); + static tree fold_bit_position (const_tree); static tree compute_related_constant (tree, tree); static tree split_plus (tree, tree *); static tree float_type_for_precision (int, machine_mode); *************** rest_of_record_type_compilation (tree re *** 2021,2035 **** { tree field_type = TREE_TYPE (old_field); tree field_name = DECL_NAME (old_field); ! tree curpos = bit_position (old_field); tree pos, new_field; bool var = false; unsigned int align = 0; - /* We're going to do some pattern matching below so remove as many - conversions as possible. */ - curpos = remove_conversions (curpos, true); - /* See how the position was modified from the last position. There are two basic cases we support: a value was added --- 2022,2032 ---- { tree field_type = TREE_TYPE (old_field); tree field_name = DECL_NAME (old_field); ! tree curpos = fold_bit_position (old_field); tree pos, new_field; bool var = false; unsigned int align = 0; /* See how the position was modified from the last position. There are two basic cases we support: a value was added *************** rest_of_record_type_compilation (tree re *** 2126,2132 **** is when there are other components at fixed positions after it (meaning there was a rep clause for every field) and we want to be able to encode them. */ ! last_pos = size_binop (PLUS_EXPR, bit_position (old_field), (TREE_CODE (TREE_TYPE (old_field)) == QUAL_UNION_TYPE) ? bitsize_zero_node --- 2123,2129 ---- is when there are other components at fixed positions after it (meaning there was a rep clause for every field) and we want to be able to encode them. */ ! last_pos = size_binop (PLUS_EXPR, curpos, (TREE_CODE (TREE_TYPE (old_field)) == QUAL_UNION_TYPE) ? bitsize_zero_node *************** merge_sizes (tree last_size, tree first_ *** 2181,2203 **** return new_size; } /* Utility function of above to see if OP0 and OP1, both of SIZETYPE, are related by the addition of a constant. Return that constant if so. */ static tree compute_related_constant (tree op0, tree op1) { ! tree op0_var, op1_var; ! tree op0_con = split_plus (op0, &op0_var); ! tree op1_con = split_plus (op1, &op1_var); ! tree result = size_binop (MINUS_EXPR, op0_con, op1_con); ! if (operand_equal_p (op0_var, op1_var, 0)) ! return result; ! else if (operand_equal_p (op0, size_binop (PLUS_EXPR, op1_var, result), 0)) ! return result; else ! return 0; } /* Utility function of above to split a tree OP which may be a sum, into a --- 2178,2228 ---- return new_size; } + /* Return the bit position of FIELD, in bits from the start of the record, + and fold it as much as possible. This is a tree of type bitsizetype. */ + + static tree + fold_bit_position (const_tree field) + { + tree offset = DECL_FIELD_OFFSET (field); + if (TREE_CODE (offset) == MULT_EXPR || TREE_CODE (offset) == PLUS_EXPR) + offset = size_binop (TREE_CODE (offset), + fold_convert (bitsizetype, TREE_OPERAND (offset, 0)), + fold_convert (bitsizetype, TREE_OPERAND (offset, 1))); + else + offset = fold_convert (bitsizetype, offset); + return size_binop (PLUS_EXPR, DECL_FIELD_BIT_OFFSET (field), + size_binop (MULT_EXPR, offset, bitsize_unit_node)); + } + /* Utility function of above to see if OP0 and OP1, both of SIZETYPE, are related by the addition of a constant. Return that constant if so. */ static tree compute_related_constant (tree op0, tree op1) { ! tree factor, op0_var, op1_var, op0_cst, op1_cst, result; ! if (TREE_CODE (op0) == MULT_EXPR ! && TREE_CODE (op1) == MULT_EXPR ! && TREE_CODE (TREE_OPERAND (op0, 1)) == INTEGER_CST ! && TREE_OPERAND (op1, 1) == TREE_OPERAND (op0, 1)) ! { ! factor = TREE_OPERAND (op0, 1); ! op0 = TREE_OPERAND (op0, 0); ! op1 = TREE_OPERAND (op1, 0); ! } else ! factor = NULL_TREE; ! ! op0_cst = split_plus (op0, &op0_var); ! op1_cst = split_plus (op1, &op1_var); ! result = size_binop (MINUS_EXPR, op0_cst, op1_cst); ! ! if (operand_equal_p (op0_var, op1_var, 0)) ! return factor ? size_binop (MULT_EXPR, factor, result) : result; ! ! return NULL_TREE; } /* Utility function of above to split a tree OP which may be a sum, into a diff -Nrcpad gcc-6.3.0/gcc/ada/socket.c gcc-6.4.0/gcc/ada/socket.c *** gcc-6.3.0/gcc/ada/socket.c Mon Jun 8 07:27:56 2015 --- gcc-6.4.0/gcc/ada/socket.c Wed Mar 8 09:20:35 2017 *************** __gnat_gethostbyaddr (const char *addr, *** 202,208 **** struct hostent *rh; int ri; ! #if defined(__linux__) || defined(__GLIBC__) (void) gethostbyaddr_r (addr, len, type, ret, buf, buflen, &rh, h_errnop); #else rh = gethostbyaddr_r (addr, len, type, ret, buf, buflen, h_errnop); --- 202,208 ---- struct hostent *rh; int ri; ! #if defined(__linux__) || defined(__GLIBC__) || defined(__rtems__) (void) gethostbyaddr_r (addr, len, type, ret, buf, buflen, &rh, h_errnop); #else rh = gethostbyaddr_r (addr, len, type, ret, buf, buflen, h_errnop); diff -Nrcpad gcc-6.3.0/gcc/ada/system-linux-aarch64-ilp32.ads gcc-6.4.0/gcc/ada/system-linux-aarch64-ilp32.ads *** gcc-6.3.0/gcc/ada/system-linux-aarch64-ilp32.ads Thu Jan 1 00:00:00 1970 --- gcc-6.4.0/gcc/ada/system-linux-aarch64-ilp32.ads Tue Mar 28 14:22:29 2017 *************** *** 0 **** --- 1,157 ---- + ------------------------------------------------------------------------------ + -- -- + -- GNAT RUN-TIME COMPONENTS -- + -- -- + -- S Y S T E M -- + -- -- + -- S p e c -- + -- (GNU-Linux/ARM Version) -- + -- -- + -- Copyright (C) 1992-2017, Free Software Foundation, Inc. -- + -- -- + -- This specification is derived from the Ada Reference Manual for use with -- + -- GNAT. The copyright notice above, and the license provisions that follow -- + -- apply solely to the contents of the part following the private keyword. -- + -- -- + -- GNAT is free software; you can redistribute it and/or modify it under -- + -- terms of the GNU General Public License as published by the Free Soft- -- + -- ware Foundation; either version 3, or (at your option) any later ver- -- + -- sion. GNAT is distributed in the hope that it will be useful, but WITH- -- + -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY -- + -- or FITNESS FOR A PARTICULAR PURPOSE. -- + -- -- + -- As a special exception under Section 7 of GPL version 3, you are granted -- + -- additional permissions described in the GCC Runtime Library Exception, -- + -- version 3.1, as published by the Free Software Foundation. -- + -- -- + -- You should have received a copy of the GNU General Public License and -- + -- a copy of the GCC Runtime Library Exception along with this program; -- + -- see the files COPYING3 and COPYING.RUNTIME respectively. If not, see -- + -- . -- + -- -- + -- GNAT was originally developed by the GNAT team at New York University. -- + -- Extensive contributions were provided by Ada Core Technologies Inc. -- + -- -- + ------------------------------------------------------------------------------ + + package System is + pragma Pure; + -- Note that we take advantage of the implementation permission to make + -- this unit Pure instead of Preelaborable; see RM 13.7.1(15). In Ada + -- 2005, this is Pure in any case (AI-362). + + pragma No_Elaboration_Code_All; + -- Allow the use of that restriction in units that WITH this unit + + type Name is (SYSTEM_NAME_GNAT); + System_Name : constant Name := SYSTEM_NAME_GNAT; + + -- System-Dependent Named Numbers + + Min_Int : constant := Long_Long_Integer'First; + Max_Int : constant := Long_Long_Integer'Last; + + Max_Binary_Modulus : constant := 2 ** Long_Long_Integer'Size; + Max_Nonbinary_Modulus : constant := 2 ** Integer'Size - 1; + + Max_Base_Digits : constant := Long_Long_Float'Digits; + Max_Digits : constant := Long_Long_Float'Digits; + + Max_Mantissa : constant := 63; + Fine_Delta : constant := 2.0 ** (-Max_Mantissa); + + Tick : constant := 0.000_001; + + -- Storage-related Declarations + + type Address is private; + pragma Preelaborable_Initialization (Address); + Null_Address : constant Address; + + Storage_Unit : constant := 8; + Word_Size : constant := 32; + Memory_Size : constant := 2 ** Word_Size; + + -- Address comparison + + function "<" (Left, Right : Address) return Boolean; + function "<=" (Left, Right : Address) return Boolean; + function ">" (Left, Right : Address) return Boolean; + function ">=" (Left, Right : Address) return Boolean; + function "=" (Left, Right : Address) return Boolean; + + pragma Import (Intrinsic, "<"); + pragma Import (Intrinsic, "<="); + pragma Import (Intrinsic, ">"); + pragma Import (Intrinsic, ">="); + pragma Import (Intrinsic, "="); + + -- Other System-Dependent Declarations + + type Bit_Order is (High_Order_First, Low_Order_First); + Default_Bit_Order : constant Bit_Order := + Bit_Order'Val (Standard'Default_Bit_Order); + pragma Warnings (Off, Default_Bit_Order); -- kill constant condition warning + + -- Priority-related Declarations (RM D.1) + + -- 0 .. 98 corresponds to the system priority range 1 .. 99. + -- + -- If the scheduling policy is SCHED_FIFO or SCHED_RR the runtime makes use + -- of the entire range provided by the system. + -- + -- If the scheduling policy is SCHED_OTHER the only valid system priority + -- is 1 and other values are simply ignored. + + Max_Priority : constant Positive := 97; + Max_Interrupt_Priority : constant Positive := 98; + + subtype Any_Priority is Integer range 0 .. 98; + subtype Priority is Any_Priority range 0 .. 97; + subtype Interrupt_Priority is Any_Priority range 98 .. 98; + + Default_Priority : constant Priority := 48; + + private + + type Address is mod Memory_Size; + Null_Address : constant Address := 0; + + -------------------------------------- + -- System Implementation Parameters -- + -------------------------------------- + + -- These parameters provide information about the target that is used + -- by the compiler. They are in the private part of System, where they + -- can be accessed using the special circuitry in the Targparm unit + -- whose source should be consulted for more detailed descriptions + -- of the individual switch values. + + Backend_Divide_Checks : constant Boolean := False; + Backend_Overflow_Checks : constant Boolean := True; + Command_Line_Args : constant Boolean := True; + Configurable_Run_Time : constant Boolean := False; + Denorm : constant Boolean := True; + Duration_32_Bits : constant Boolean := False; + Exit_Status_Supported : constant Boolean := True; + Fractional_Fixed_Ops : constant Boolean := False; + Frontend_Layout : constant Boolean := False; + Machine_Overflows : constant Boolean := False; + Machine_Rounds : constant Boolean := True; + Preallocated_Stacks : constant Boolean := False; + Signed_Zeros : constant Boolean := True; + Stack_Check_Default : constant Boolean := False; + Stack_Check_Probes : constant Boolean := True; + Stack_Check_Limits : constant Boolean := False; + Support_Aggregates : constant Boolean := True; + Support_Atomic_Primitives : constant Boolean := True; + Support_Composite_Assign : constant Boolean := True; + Support_Composite_Compare : constant Boolean := True; + Support_Long_Shifts : constant Boolean := True; + Always_Compatible_Rep : constant Boolean := False; + Suppress_Standard_Library : constant Boolean := False; + Use_Ada_Main_Program_Name : constant Boolean := False; + Frontend_Exceptions : constant Boolean := False; + ZCX_By_Default : constant Boolean := True; + + end System; diff -Nrcpad gcc-6.3.0/gcc/ada/system-linux-ppc.ads gcc-6.4.0/gcc/ada/system-linux-ppc.ads *** gcc-6.3.0/gcc/ada/system-linux-ppc.ads Tue Oct 11 20:03:58 2016 --- gcc-6.4.0/gcc/ada/system-linux-ppc.ads Wed Mar 8 09:09:11 2017 *************** *** 7,13 **** -- S p e c -- -- (GNU-Linux/PPC Version) -- -- -- ! -- Copyright (C) 1992-2016, Free Software Foundation, Inc. -- -- -- -- This specification is derived from the Ada Reference Manual for use with -- -- GNAT. The copyright notice above, and the license provisions that follow -- --- 7,13 ---- -- S p e c -- -- (GNU-Linux/PPC Version) -- -- -- ! -- Copyright (C) 1992-2017, Free Software Foundation, Inc. -- -- -- -- This specification is derived from the Ada Reference Manual for use with -- -- GNAT. The copyright notice above, and the license provisions that follow -- *************** package System is *** 89,95 **** -- Other System-Dependent Declarations type Bit_Order is (High_Order_First, Low_Order_First); ! Default_Bit_Order : constant Bit_Order := High_Order_First; pragma Warnings (Off, Default_Bit_Order); -- kill constant condition warning -- Priority-related Declarations (RM D.1) --- 89,96 ---- -- Other System-Dependent Declarations type Bit_Order is (High_Order_First, Low_Order_First); ! Default_Bit_Order : constant Bit_Order := ! Bit_Order'Val (Standard'Default_Bit_Order); pragma Warnings (Off, Default_Bit_Order); -- kill constant condition warning -- Priority-related Declarations (RM D.1) diff -Nrcpad gcc-6.3.0/gcc/alias.c gcc-6.4.0/gcc/alias.c *** gcc-6.3.0/gcc/alias.c Wed Dec 7 22:47:48 2016 --- gcc-6.4.0/gcc/alias.c Tue May 9 12:27:24 2017 *************** compare_base_decls (tree base1, tree bas *** 2035,2040 **** --- 2035,2052 ---- if (base1 == base2) return 1; + /* If we have two register decls with register specification we + cannot decide unless their assembler name is the same. */ + if (DECL_REGISTER (base1) + && DECL_REGISTER (base2) + && DECL_ASSEMBLER_NAME_SET_P (base1) + && DECL_ASSEMBLER_NAME_SET_P (base2)) + { + if (DECL_ASSEMBLER_NAME (base1) == DECL_ASSEMBLER_NAME (base2)) + return 1; + return -1; + } + /* Declarations of non-automatic variables may have aliases. All other decls are unique. */ if (!decl_in_symtab_p (base1) diff -Nrcpad gcc-6.3.0/gcc/asan.c gcc-6.4.0/gcc/asan.c *** gcc-6.3.0/gcc/asan.c Thu Jul 21 16:18:46 2016 --- gcc-6.4.0/gcc/asan.c Fri May 5 21:45:42 2017 *************** get_mem_refs_of_builtin_call (const gcal *** 587,804 **** case BUILT_IN_STRLEN: source0 = gimple_call_arg (call, 0); len = gimple_call_lhs (call); ! break ; /* And now the __atomic* and __sync builtins. These are handled differently from the classical memory memory access builtins above. */ case BUILT_IN_ATOMIC_LOAD_1: - case BUILT_IN_ATOMIC_LOAD_2: - case BUILT_IN_ATOMIC_LOAD_4: - case BUILT_IN_ATOMIC_LOAD_8: - case BUILT_IN_ATOMIC_LOAD_16: is_store = false; ! /* fall through. */ ! case BUILT_IN_SYNC_FETCH_AND_ADD_1: - case BUILT_IN_SYNC_FETCH_AND_ADD_2: - case BUILT_IN_SYNC_FETCH_AND_ADD_4: - case BUILT_IN_SYNC_FETCH_AND_ADD_8: - case BUILT_IN_SYNC_FETCH_AND_ADD_16: - case BUILT_IN_SYNC_FETCH_AND_SUB_1: - case BUILT_IN_SYNC_FETCH_AND_SUB_2: - case BUILT_IN_SYNC_FETCH_AND_SUB_4: - case BUILT_IN_SYNC_FETCH_AND_SUB_8: - case BUILT_IN_SYNC_FETCH_AND_SUB_16: - case BUILT_IN_SYNC_FETCH_AND_OR_1: - case BUILT_IN_SYNC_FETCH_AND_OR_2: - case BUILT_IN_SYNC_FETCH_AND_OR_4: - case BUILT_IN_SYNC_FETCH_AND_OR_8: - case BUILT_IN_SYNC_FETCH_AND_OR_16: - case BUILT_IN_SYNC_FETCH_AND_AND_1: - case BUILT_IN_SYNC_FETCH_AND_AND_2: - case BUILT_IN_SYNC_FETCH_AND_AND_4: - case BUILT_IN_SYNC_FETCH_AND_AND_8: - case BUILT_IN_SYNC_FETCH_AND_AND_16: - case BUILT_IN_SYNC_FETCH_AND_XOR_1: - case BUILT_IN_SYNC_FETCH_AND_XOR_2: - case BUILT_IN_SYNC_FETCH_AND_XOR_4: - case BUILT_IN_SYNC_FETCH_AND_XOR_8: - case BUILT_IN_SYNC_FETCH_AND_XOR_16: - case BUILT_IN_SYNC_FETCH_AND_NAND_1: - case BUILT_IN_SYNC_FETCH_AND_NAND_2: - case BUILT_IN_SYNC_FETCH_AND_NAND_4: - case BUILT_IN_SYNC_FETCH_AND_NAND_8: - case BUILT_IN_SYNC_ADD_AND_FETCH_1: - case BUILT_IN_SYNC_ADD_AND_FETCH_2: - case BUILT_IN_SYNC_ADD_AND_FETCH_4: - case BUILT_IN_SYNC_ADD_AND_FETCH_8: - case BUILT_IN_SYNC_ADD_AND_FETCH_16: - case BUILT_IN_SYNC_SUB_AND_FETCH_1: - case BUILT_IN_SYNC_SUB_AND_FETCH_2: - case BUILT_IN_SYNC_SUB_AND_FETCH_4: - case BUILT_IN_SYNC_SUB_AND_FETCH_8: - case BUILT_IN_SYNC_SUB_AND_FETCH_16: - case BUILT_IN_SYNC_OR_AND_FETCH_1: - case BUILT_IN_SYNC_OR_AND_FETCH_2: - case BUILT_IN_SYNC_OR_AND_FETCH_4: - case BUILT_IN_SYNC_OR_AND_FETCH_8: - case BUILT_IN_SYNC_OR_AND_FETCH_16: - case BUILT_IN_SYNC_AND_AND_FETCH_1: - case BUILT_IN_SYNC_AND_AND_FETCH_2: - case BUILT_IN_SYNC_AND_AND_FETCH_4: - case BUILT_IN_SYNC_AND_AND_FETCH_8: - case BUILT_IN_SYNC_AND_AND_FETCH_16: - case BUILT_IN_SYNC_XOR_AND_FETCH_1: - case BUILT_IN_SYNC_XOR_AND_FETCH_2: - case BUILT_IN_SYNC_XOR_AND_FETCH_4: - case BUILT_IN_SYNC_XOR_AND_FETCH_8: - case BUILT_IN_SYNC_XOR_AND_FETCH_16: - case BUILT_IN_SYNC_NAND_AND_FETCH_1: - case BUILT_IN_SYNC_NAND_AND_FETCH_2: - case BUILT_IN_SYNC_NAND_AND_FETCH_4: - case BUILT_IN_SYNC_NAND_AND_FETCH_8: - case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_1: - case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_2: - case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_4: - case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_8: - case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_16: - case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_1: - case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_2: - case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_4: - case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_8: - case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_16: - case BUILT_IN_SYNC_LOCK_TEST_AND_SET_1: - case BUILT_IN_SYNC_LOCK_TEST_AND_SET_2: - case BUILT_IN_SYNC_LOCK_TEST_AND_SET_4: - case BUILT_IN_SYNC_LOCK_TEST_AND_SET_8: - case BUILT_IN_SYNC_LOCK_TEST_AND_SET_16: - case BUILT_IN_SYNC_LOCK_RELEASE_1: - case BUILT_IN_SYNC_LOCK_RELEASE_2: - case BUILT_IN_SYNC_LOCK_RELEASE_4: - case BUILT_IN_SYNC_LOCK_RELEASE_8: - case BUILT_IN_SYNC_LOCK_RELEASE_16: - case BUILT_IN_ATOMIC_EXCHANGE_1: - case BUILT_IN_ATOMIC_EXCHANGE_2: - case BUILT_IN_ATOMIC_EXCHANGE_4: - case BUILT_IN_ATOMIC_EXCHANGE_8: - case BUILT_IN_ATOMIC_EXCHANGE_16: - case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_1: - case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_2: - case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_4: - case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_8: - case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_16: - case BUILT_IN_ATOMIC_STORE_1: - case BUILT_IN_ATOMIC_STORE_2: - case BUILT_IN_ATOMIC_STORE_4: - case BUILT_IN_ATOMIC_STORE_8: - case BUILT_IN_ATOMIC_STORE_16: - case BUILT_IN_ATOMIC_ADD_FETCH_1: - case BUILT_IN_ATOMIC_ADD_FETCH_2: - case BUILT_IN_ATOMIC_ADD_FETCH_4: - case BUILT_IN_ATOMIC_ADD_FETCH_8: - case BUILT_IN_ATOMIC_ADD_FETCH_16: - case BUILT_IN_ATOMIC_SUB_FETCH_1: - case BUILT_IN_ATOMIC_SUB_FETCH_2: - case BUILT_IN_ATOMIC_SUB_FETCH_4: - case BUILT_IN_ATOMIC_SUB_FETCH_8: - case BUILT_IN_ATOMIC_SUB_FETCH_16: - case BUILT_IN_ATOMIC_AND_FETCH_1: - case BUILT_IN_ATOMIC_AND_FETCH_2: - case BUILT_IN_ATOMIC_AND_FETCH_4: - case BUILT_IN_ATOMIC_AND_FETCH_8: - case BUILT_IN_ATOMIC_AND_FETCH_16: - case BUILT_IN_ATOMIC_NAND_FETCH_1: - case BUILT_IN_ATOMIC_NAND_FETCH_2: - case BUILT_IN_ATOMIC_NAND_FETCH_4: - case BUILT_IN_ATOMIC_NAND_FETCH_8: - case BUILT_IN_ATOMIC_NAND_FETCH_16: - case BUILT_IN_ATOMIC_XOR_FETCH_1: - case BUILT_IN_ATOMIC_XOR_FETCH_2: - case BUILT_IN_ATOMIC_XOR_FETCH_4: - case BUILT_IN_ATOMIC_XOR_FETCH_8: - case BUILT_IN_ATOMIC_XOR_FETCH_16: - case BUILT_IN_ATOMIC_OR_FETCH_1: - case BUILT_IN_ATOMIC_OR_FETCH_2: - case BUILT_IN_ATOMIC_OR_FETCH_4: - case BUILT_IN_ATOMIC_OR_FETCH_8: - case BUILT_IN_ATOMIC_OR_FETCH_16: - case BUILT_IN_ATOMIC_FETCH_ADD_1: - case BUILT_IN_ATOMIC_FETCH_ADD_2: - case BUILT_IN_ATOMIC_FETCH_ADD_4: - case BUILT_IN_ATOMIC_FETCH_ADD_8: - case BUILT_IN_ATOMIC_FETCH_ADD_16: - case BUILT_IN_ATOMIC_FETCH_SUB_1: - case BUILT_IN_ATOMIC_FETCH_SUB_2: - case BUILT_IN_ATOMIC_FETCH_SUB_4: - case BUILT_IN_ATOMIC_FETCH_SUB_8: - case BUILT_IN_ATOMIC_FETCH_SUB_16: - case BUILT_IN_ATOMIC_FETCH_AND_1: - case BUILT_IN_ATOMIC_FETCH_AND_2: - case BUILT_IN_ATOMIC_FETCH_AND_4: - case BUILT_IN_ATOMIC_FETCH_AND_8: - case BUILT_IN_ATOMIC_FETCH_AND_16: - case BUILT_IN_ATOMIC_FETCH_NAND_1: - case BUILT_IN_ATOMIC_FETCH_NAND_2: - case BUILT_IN_ATOMIC_FETCH_NAND_4: - case BUILT_IN_ATOMIC_FETCH_NAND_8: - case BUILT_IN_ATOMIC_FETCH_NAND_16: - case BUILT_IN_ATOMIC_FETCH_XOR_1: - case BUILT_IN_ATOMIC_FETCH_XOR_2: - case BUILT_IN_ATOMIC_FETCH_XOR_4: - case BUILT_IN_ATOMIC_FETCH_XOR_8: - case BUILT_IN_ATOMIC_FETCH_XOR_16: - case BUILT_IN_ATOMIC_FETCH_OR_1: case BUILT_IN_ATOMIC_FETCH_OR_2: case BUILT_IN_ATOMIC_FETCH_OR_4: case BUILT_IN_ATOMIC_FETCH_OR_8: case BUILT_IN_ATOMIC_FETCH_OR_16: { dest = gimple_call_arg (call, 0); /* DEST represents the address of a memory location. instrument_derefs wants the memory location, so lets dereference the address DEST before handing it to instrument_derefs. */ ! if (TREE_CODE (dest) == ADDR_EXPR) ! dest = TREE_OPERAND (dest, 0); ! else if (TREE_CODE (dest) == SSA_NAME || TREE_CODE (dest) == INTEGER_CST) ! dest = build2 (MEM_REF, TREE_TYPE (TREE_TYPE (dest)), ! dest, build_int_cst (TREE_TYPE (dest), 0)); ! else ! gcc_unreachable (); ! ! access_size = int_size_in_bytes (TREE_TYPE (dest)); } default: --- 587,794 ---- case BUILT_IN_STRLEN: source0 = gimple_call_arg (call, 0); len = gimple_call_lhs (call); ! break; /* And now the __atomic* and __sync builtins. These are handled differently from the classical memory memory access builtins above. */ case BUILT_IN_ATOMIC_LOAD_1: is_store = false; ! /* FALLTHRU */ case BUILT_IN_SYNC_FETCH_AND_ADD_1: case BUILT_IN_SYNC_FETCH_AND_SUB_1: case BUILT_IN_SYNC_FETCH_AND_OR_1: case BUILT_IN_SYNC_FETCH_AND_AND_1: case BUILT_IN_SYNC_FETCH_AND_XOR_1: case BUILT_IN_SYNC_FETCH_AND_NAND_1: case BUILT_IN_SYNC_ADD_AND_FETCH_1: case BUILT_IN_SYNC_SUB_AND_FETCH_1: case BUILT_IN_SYNC_OR_AND_FETCH_1: case BUILT_IN_SYNC_AND_AND_FETCH_1: case BUILT_IN_SYNC_XOR_AND_FETCH_1: case BUILT_IN_SYNC_NAND_AND_FETCH_1: case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_1: case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_1: case BUILT_IN_SYNC_LOCK_TEST_AND_SET_1: case BUILT_IN_SYNC_LOCK_RELEASE_1: case BUILT_IN_ATOMIC_EXCHANGE_1: case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_1: case BUILT_IN_ATOMIC_STORE_1: case BUILT_IN_ATOMIC_ADD_FETCH_1: case BUILT_IN_ATOMIC_SUB_FETCH_1: case BUILT_IN_ATOMIC_AND_FETCH_1: case BUILT_IN_ATOMIC_NAND_FETCH_1: case BUILT_IN_ATOMIC_XOR_FETCH_1: case BUILT_IN_ATOMIC_OR_FETCH_1: case BUILT_IN_ATOMIC_FETCH_ADD_1: case BUILT_IN_ATOMIC_FETCH_SUB_1: case BUILT_IN_ATOMIC_FETCH_AND_1: case BUILT_IN_ATOMIC_FETCH_NAND_1: case BUILT_IN_ATOMIC_FETCH_XOR_1: case BUILT_IN_ATOMIC_FETCH_OR_1: + access_size = 1; + goto do_atomic; + + case BUILT_IN_ATOMIC_LOAD_2: + is_store = false; + /* FALLTHRU */ + case BUILT_IN_SYNC_FETCH_AND_ADD_2: + case BUILT_IN_SYNC_FETCH_AND_SUB_2: + case BUILT_IN_SYNC_FETCH_AND_OR_2: + case BUILT_IN_SYNC_FETCH_AND_AND_2: + case BUILT_IN_SYNC_FETCH_AND_XOR_2: + case BUILT_IN_SYNC_FETCH_AND_NAND_2: + case BUILT_IN_SYNC_ADD_AND_FETCH_2: + case BUILT_IN_SYNC_SUB_AND_FETCH_2: + case BUILT_IN_SYNC_OR_AND_FETCH_2: + case BUILT_IN_SYNC_AND_AND_FETCH_2: + case BUILT_IN_SYNC_XOR_AND_FETCH_2: + case BUILT_IN_SYNC_NAND_AND_FETCH_2: + case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_2: + case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_2: + case BUILT_IN_SYNC_LOCK_TEST_AND_SET_2: + case BUILT_IN_SYNC_LOCK_RELEASE_2: + case BUILT_IN_ATOMIC_EXCHANGE_2: + case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_2: + case BUILT_IN_ATOMIC_STORE_2: + case BUILT_IN_ATOMIC_ADD_FETCH_2: + case BUILT_IN_ATOMIC_SUB_FETCH_2: + case BUILT_IN_ATOMIC_AND_FETCH_2: + case BUILT_IN_ATOMIC_NAND_FETCH_2: + case BUILT_IN_ATOMIC_XOR_FETCH_2: + case BUILT_IN_ATOMIC_OR_FETCH_2: + case BUILT_IN_ATOMIC_FETCH_ADD_2: + case BUILT_IN_ATOMIC_FETCH_SUB_2: + case BUILT_IN_ATOMIC_FETCH_AND_2: + case BUILT_IN_ATOMIC_FETCH_NAND_2: + case BUILT_IN_ATOMIC_FETCH_XOR_2: case BUILT_IN_ATOMIC_FETCH_OR_2: + access_size = 2; + goto do_atomic; + + case BUILT_IN_ATOMIC_LOAD_4: + is_store = false; + /* FALLTHRU */ + case BUILT_IN_SYNC_FETCH_AND_ADD_4: + case BUILT_IN_SYNC_FETCH_AND_SUB_4: + case BUILT_IN_SYNC_FETCH_AND_OR_4: + case BUILT_IN_SYNC_FETCH_AND_AND_4: + case BUILT_IN_SYNC_FETCH_AND_XOR_4: + case BUILT_IN_SYNC_FETCH_AND_NAND_4: + case BUILT_IN_SYNC_ADD_AND_FETCH_4: + case BUILT_IN_SYNC_SUB_AND_FETCH_4: + case BUILT_IN_SYNC_OR_AND_FETCH_4: + case BUILT_IN_SYNC_AND_AND_FETCH_4: + case BUILT_IN_SYNC_XOR_AND_FETCH_4: + case BUILT_IN_SYNC_NAND_AND_FETCH_4: + case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_4: + case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_4: + case BUILT_IN_SYNC_LOCK_TEST_AND_SET_4: + case BUILT_IN_SYNC_LOCK_RELEASE_4: + case BUILT_IN_ATOMIC_EXCHANGE_4: + case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_4: + case BUILT_IN_ATOMIC_STORE_4: + case BUILT_IN_ATOMIC_ADD_FETCH_4: + case BUILT_IN_ATOMIC_SUB_FETCH_4: + case BUILT_IN_ATOMIC_AND_FETCH_4: + case BUILT_IN_ATOMIC_NAND_FETCH_4: + case BUILT_IN_ATOMIC_XOR_FETCH_4: + case BUILT_IN_ATOMIC_OR_FETCH_4: + case BUILT_IN_ATOMIC_FETCH_ADD_4: + case BUILT_IN_ATOMIC_FETCH_SUB_4: + case BUILT_IN_ATOMIC_FETCH_AND_4: + case BUILT_IN_ATOMIC_FETCH_NAND_4: + case BUILT_IN_ATOMIC_FETCH_XOR_4: case BUILT_IN_ATOMIC_FETCH_OR_4: + access_size = 4; + goto do_atomic; + + case BUILT_IN_ATOMIC_LOAD_8: + is_store = false; + /* FALLTHRU */ + case BUILT_IN_SYNC_FETCH_AND_ADD_8: + case BUILT_IN_SYNC_FETCH_AND_SUB_8: + case BUILT_IN_SYNC_FETCH_AND_OR_8: + case BUILT_IN_SYNC_FETCH_AND_AND_8: + case BUILT_IN_SYNC_FETCH_AND_XOR_8: + case BUILT_IN_SYNC_FETCH_AND_NAND_8: + case BUILT_IN_SYNC_ADD_AND_FETCH_8: + case BUILT_IN_SYNC_SUB_AND_FETCH_8: + case BUILT_IN_SYNC_OR_AND_FETCH_8: + case BUILT_IN_SYNC_AND_AND_FETCH_8: + case BUILT_IN_SYNC_XOR_AND_FETCH_8: + case BUILT_IN_SYNC_NAND_AND_FETCH_8: + case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_8: + case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_8: + case BUILT_IN_SYNC_LOCK_TEST_AND_SET_8: + case BUILT_IN_SYNC_LOCK_RELEASE_8: + case BUILT_IN_ATOMIC_EXCHANGE_8: + case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_8: + case BUILT_IN_ATOMIC_STORE_8: + case BUILT_IN_ATOMIC_ADD_FETCH_8: + case BUILT_IN_ATOMIC_SUB_FETCH_8: + case BUILT_IN_ATOMIC_AND_FETCH_8: + case BUILT_IN_ATOMIC_NAND_FETCH_8: + case BUILT_IN_ATOMIC_XOR_FETCH_8: + case BUILT_IN_ATOMIC_OR_FETCH_8: + case BUILT_IN_ATOMIC_FETCH_ADD_8: + case BUILT_IN_ATOMIC_FETCH_SUB_8: + case BUILT_IN_ATOMIC_FETCH_AND_8: + case BUILT_IN_ATOMIC_FETCH_NAND_8: + case BUILT_IN_ATOMIC_FETCH_XOR_8: case BUILT_IN_ATOMIC_FETCH_OR_8: + access_size = 8; + goto do_atomic; + + case BUILT_IN_ATOMIC_LOAD_16: + is_store = false; + /* FALLTHRU */ + case BUILT_IN_SYNC_FETCH_AND_ADD_16: + case BUILT_IN_SYNC_FETCH_AND_SUB_16: + case BUILT_IN_SYNC_FETCH_AND_OR_16: + case BUILT_IN_SYNC_FETCH_AND_AND_16: + case BUILT_IN_SYNC_FETCH_AND_XOR_16: + case BUILT_IN_SYNC_FETCH_AND_NAND_16: + case BUILT_IN_SYNC_ADD_AND_FETCH_16: + case BUILT_IN_SYNC_SUB_AND_FETCH_16: + case BUILT_IN_SYNC_OR_AND_FETCH_16: + case BUILT_IN_SYNC_AND_AND_FETCH_16: + case BUILT_IN_SYNC_XOR_AND_FETCH_16: + case BUILT_IN_SYNC_NAND_AND_FETCH_16: + case BUILT_IN_SYNC_BOOL_COMPARE_AND_SWAP_16: + case BUILT_IN_SYNC_VAL_COMPARE_AND_SWAP_16: + case BUILT_IN_SYNC_LOCK_TEST_AND_SET_16: + case BUILT_IN_SYNC_LOCK_RELEASE_16: + case BUILT_IN_ATOMIC_EXCHANGE_16: + case BUILT_IN_ATOMIC_COMPARE_EXCHANGE_16: + case BUILT_IN_ATOMIC_STORE_16: + case BUILT_IN_ATOMIC_ADD_FETCH_16: + case BUILT_IN_ATOMIC_SUB_FETCH_16: + case BUILT_IN_ATOMIC_AND_FETCH_16: + case BUILT_IN_ATOMIC_NAND_FETCH_16: + case BUILT_IN_ATOMIC_XOR_FETCH_16: + case BUILT_IN_ATOMIC_OR_FETCH_16: + case BUILT_IN_ATOMIC_FETCH_ADD_16: + case BUILT_IN_ATOMIC_FETCH_SUB_16: + case BUILT_IN_ATOMIC_FETCH_AND_16: + case BUILT_IN_ATOMIC_FETCH_NAND_16: + case BUILT_IN_ATOMIC_FETCH_XOR_16: case BUILT_IN_ATOMIC_FETCH_OR_16: + access_size = 16; + /* FALLTHRU */ + do_atomic: { dest = gimple_call_arg (call, 0); /* DEST represents the address of a memory location. instrument_derefs wants the memory location, so lets dereference the address DEST before handing it to instrument_derefs. */ ! tree type = build_nonstandard_integer_type (access_size ! * BITS_PER_UNIT, 1); ! dest = build2 (MEM_REF, type, dest, ! build_int_cst (build_pointer_type (char_type_node), 0)); ! break; } default: *************** instrument_derefs (gimple_stmt_iterator *** 1801,1807 **** tree repr = DECL_BIT_FIELD_REPRESENTATIVE (TREE_OPERAND (t, 1)); instrument_derefs (iter, build3 (COMPONENT_REF, TREE_TYPE (repr), TREE_OPERAND (t, 0), repr, ! NULL_TREE), location, is_store); return; } --- 1791,1798 ---- tree repr = DECL_BIT_FIELD_REPRESENTATIVE (TREE_OPERAND (t, 1)); instrument_derefs (iter, build3 (COMPONENT_REF, TREE_TYPE (repr), TREE_OPERAND (t, 0), repr, ! TREE_OPERAND (t, 2)), ! location, is_store); return; } *************** asan_add_global (tree decl, tree type, v *** 2275,2281 **** CONSTRUCTOR_APPEND_ELT (vinner, NULL_TREE, fold_convert (const_ptr_type_node, module_name_cst)); varpool_node *vnode = varpool_node::get (decl); ! int has_dynamic_init = vnode ? vnode->dynamically_initialized : 0; CONSTRUCTOR_APPEND_ELT (vinner, NULL_TREE, build_int_cst (uptr, has_dynamic_init)); tree locptr = NULL_TREE; --- 2266,2276 ---- CONSTRUCTOR_APPEND_ELT (vinner, NULL_TREE, fold_convert (const_ptr_type_node, module_name_cst)); varpool_node *vnode = varpool_node::get (decl); ! int has_dynamic_init = 0; ! /* FIXME: Enable initialization order fiasco detection in LTO mode once ! proper fix for PR 79061 will be applied. */ ! if (!in_lto_p) ! has_dynamic_init = vnode ? vnode->dynamically_initialized : 0; CONSTRUCTOR_APPEND_ELT (vinner, NULL_TREE, build_int_cst (uptr, has_dynamic_init)); tree locptr = NULL_TREE; diff -Nrcpad gcc-6.3.0/gcc/auto-profile.c gcc-6.4.0/gcc/auto-profile.c *** gcc-6.3.0/gcc/auto-profile.c Fri Apr 22 11:09:22 2016 --- gcc-6.4.0/gcc/auto-profile.c Thu Jun 22 11:20:15 2017 *************** get_function_decl_from_block (tree block *** 353,359 **** { tree decl; ! if (LOCATION_LOCUS (BLOCK_SOURCE_LOCATION (block) == UNKNOWN_LOCATION)) return NULL_TREE; for (decl = BLOCK_ABSTRACT_ORIGIN (block); --- 353,359 ---- { tree decl; ! if (LOCATION_LOCUS (BLOCK_SOURCE_LOCATION (block)) == UNKNOWN_LOCATION) return NULL_TREE; for (decl = BLOCK_ABSTRACT_ORIGIN (block); *************** afdo_vpt_for_early_inline (stmt_set *pro *** 1437,1443 **** if (has_vpt) { ! optimize_inline_calls (current_function_decl); return true; } --- 1437,1445 ---- if (has_vpt) { ! unsigned todo = optimize_inline_calls (current_function_decl); ! if (todo & TODO_update_ssa_any) ! update_ssa (TODO_update_ssa); return true; } diff -Nrcpad gcc-6.3.0/gcc/builtins.c gcc-6.4.0/gcc/builtins.c *** gcc-6.3.0/gcc/builtins.c Wed Dec 7 22:29:54 2016 --- gcc-6.4.0/gcc/builtins.c Tue Jun 27 17:11:01 2017 *************** expand_builtin_atomic_fetch_op (machine_ *** 5288,5293 **** --- 5288,5299 ---- gcc_assert (TREE_OPERAND (addr, 0) == fndecl); TREE_OPERAND (addr, 0) = builtin_decl_explicit (ext_call); + /* If we will emit code after the call, the call can not be a tail call. + If it is emitted as a tail call, a barrier is emitted after it, and + then all trailing code is removed. */ + if (!ignore) + CALL_EXPR_TAILCALL (exp) = 0; + /* Expand the call here so we can emit trailing code. */ ret = expand_call (exp, target, ignore); diff -Nrcpad gcc-6.3.0/gcc/c/ChangeLog gcc-6.4.0/gcc/c/ChangeLog *** gcc-6.3.0/gcc/c/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/c/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,43 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-06-08 Jakub Jelinek + + PR c/81006 + * c-typeck.c (handle_omp_array_sections_1): Convert TYPE_MAX_VALUE + to sizetype before size_binop. + + 2017-05-05 Jakub Jelinek + + Backported from mainline + 2017-03-21 Jakub Jelinek + + PR c/80097 + * c-typeck.c (build_binary_op): Add EXCESS_PRECISION_EXPR only around + optional COMPOUND_EXPR with ubsan instrumentation. + + 2017-02-16 Jakub Jelinek + + PR c++/79512 + * c-parser.c (c_parser_omp_target): For -fopenmp-simd + ignore #pragma omp target even when not followed by identifier. + + 2017-02-15 Jakub Jelinek + + Backported from mainline + 2017-02-09 Jakub Jelinek + + PR c/79431 + * c-parser.c (c_parser_omp_declare_target): Don't invoke + symtab_node::get on automatic variables. + + 2016-12-21 Jakub Jelinek + + PR c/77767 + * c-decl.c (grokdeclarator): If *expr is non-NULL, append expression + to *expr instead of overwriting it. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/c/c-decl.c gcc-6.4.0/gcc/c/c-decl.c *** gcc-6.3.0/gcc/c/c-decl.c Thu Aug 11 15:14:17 2016 --- gcc-6.4.0/gcc/c/c-decl.c Wed Dec 21 12:52:06 2016 *************** grokdeclarator (const struct c_declarato *** 5400,5410 **** if (TREE_CODE (type) == ERROR_MARK) return error_mark_node; if (expr == NULL) ! expr = &expr_dummy; if (expr_const_operands == NULL) expr_const_operands = &expr_const_operands_dummy; ! *expr = declspecs->expr; *expr_const_operands = declspecs->expr_const_operands; if (decl_context == FUNCDEF) --- 5400,5420 ---- if (TREE_CODE (type) == ERROR_MARK) return error_mark_node; if (expr == NULL) ! { ! expr = &expr_dummy; ! expr_dummy = NULL_TREE; ! } if (expr_const_operands == NULL) expr_const_operands = &expr_const_operands_dummy; ! if (declspecs->expr) ! { ! if (*expr) ! *expr = build2 (COMPOUND_EXPR, TREE_TYPE (declspecs->expr), *expr, ! declspecs->expr); ! else ! *expr = declspecs->expr; ! } *expr_const_operands = declspecs->expr_const_operands; if (decl_context == FUNCDEF) diff -Nrcpad gcc-6.3.0/gcc/c/c-parser.c gcc-6.4.0/gcc/c/c-parser.c *** gcc-6.3.0/gcc/c/c-parser.c Fri Jun 10 09:46:04 2016 --- gcc-6.4.0/gcc/c/c-parser.c Fri May 5 21:23:09 2017 *************** c_parser_omp_ordered (c_parser *parser, *** 15180,15186 **** if (context != pragma_stmt && context != pragma_compound) { c_parser_error (parser, "expected declaration specifiers"); ! c_parser_skip_until_found (parser, CPP_PRAGMA_EOL, NULL); return false; } --- 15180,15186 ---- if (context != pragma_stmt && context != pragma_compound) { c_parser_error (parser, "expected declaration specifiers"); ! c_parser_skip_to_pragma_eol (parser, false); return false; } *************** c_parser_omp_target (c_parser *parser, e *** 16212,16217 **** --- 16212,16222 ---- return c_parser_omp_target_update (loc, parser, context); } } + if (!flag_openmp) /* flag_openmp_simd */ + { + c_parser_skip_to_pragma_eol (parser, false); + return false; + } stmt = make_node (OMP_TARGET); TREE_TYPE (stmt) = void_type_node; *************** c_parser_omp_declare_target (c_parser *p *** 16560,16567 **** } if (!at1) { - symtab_node *node = symtab_node::get (t); DECL_ATTRIBUTES (t) = tree_cons (id, NULL_TREE, DECL_ATTRIBUTES (t)); if (node != NULL) { node->offloadable = 1; --- 16565,16575 ---- } if (!at1) { DECL_ATTRIBUTES (t) = tree_cons (id, NULL_TREE, DECL_ATTRIBUTES (t)); + if (TREE_CODE (t) != FUNCTION_DECL && !is_global_var (t)) + continue; + + symtab_node *node = symtab_node::get (t); if (node != NULL) { node->offloadable = 1; diff -Nrcpad gcc-6.3.0/gcc/c/c-typeck.c gcc-6.4.0/gcc/c/c-typeck.c *** gcc-6.3.0/gcc/c/c-typeck.c Sat Nov 5 22:41:18 2016 --- gcc-6.4.0/gcc/c/c-typeck.c Thu Jun 8 19:13:51 2017 *************** build_binary_op (location_t location, en *** 11627,11640 **** else if (TREE_CODE (ret) != INTEGER_CST && int_operands && !in_late_binary_op) ret = note_integer_operands (ret); - if (semantic_result_type) - ret = build1 (EXCESS_PRECISION_EXPR, semantic_result_type, ret); protected_set_expr_location (ret, location); if (instrument_expr != NULL) ret = fold_build2 (COMPOUND_EXPR, TREE_TYPE (ret), instrument_expr, ret); return ret; } --- 11627,11642 ---- else if (TREE_CODE (ret) != INTEGER_CST && int_operands && !in_late_binary_op) ret = note_integer_operands (ret); protected_set_expr_location (ret, location); if (instrument_expr != NULL) ret = fold_build2 (COMPOUND_EXPR, TREE_TYPE (ret), instrument_expr, ret); + if (semantic_result_type) + ret = build1_loc (location, EXCESS_PRECISION_EXPR, + semantic_result_type, ret); + return ret; } *************** handle_omp_array_sections_1 (tree c, tre *** 12085,12093 **** && TREE_CODE (TYPE_MAX_VALUE (TYPE_DOMAIN (type))) == INTEGER_CST) { ! tree size = size_binop (PLUS_EXPR, ! TYPE_MAX_VALUE (TYPE_DOMAIN (type)), ! size_one_node); if (TREE_CODE (low_bound) == INTEGER_CST) { if (tree_int_cst_lt (size, low_bound)) --- 12087,12095 ---- && TREE_CODE (TYPE_MAX_VALUE (TYPE_DOMAIN (type))) == INTEGER_CST) { ! tree size ! = fold_convert (sizetype, TYPE_MAX_VALUE (TYPE_DOMAIN (type))); ! size = size_binop (PLUS_EXPR, size, size_one_node); if (TREE_CODE (low_bound) == INTEGER_CST) { if (tree_int_cst_lt (size, low_bound)) diff -Nrcpad gcc-6.3.0/gcc/c-family/ChangeLog gcc-6.4.0/gcc/c-family/ChangeLog *** gcc-6.3.0/gcc/c-family/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/c-family/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,72 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-05-26 Martin Liska + + Backport from mainline + 2017-04-10 Martin Liska + + PR sanitizer/80350 + * c-ubsan.c (ubsan_instrument_shift): Evaluate RHS before + doing an UBSAN check. + + 2017-05-05 Jakub Jelinek + + Backported from mainline + 2017-03-31 Jakub Jelinek + + PR c++/79572 + * c-ubsan.h (ubsan_maybe_instrument_reference): Change argument to + tree *. + * c-ubsan.c (ubsan_maybe_instrument_reference): Likewise. Handle + not just NOP_EXPR to REFERENCE_TYPE, but also INTEGER_CST with + REFERENCE_TYPE. + + 2017-02-21 Jakub Jelinek + + PR c++/79641 + * c-common.c (handle_mode_attribute): Use build_qualified_type to + preserve quals. + + 2017-03-22 Martin Liska + + Backport from mainline + 2017-03-09 Martin Liska + + * c-ada-spec.c (macro_length): Increment value instead of a pointer. + + 2017-03-21 Martin Sebor + + PR c++/79548 + * c-common.c (set_underlying_type): Mark type used only when + original del is declared unused. + + 2017-03-14 Marek Polacek + + PR c++/79962 + PR c++/79984 + * c-common.c (handle_nonnull_attribute): Save the result of default + conversion to the attribute list. + + 2017-03-14 Richard Biener + + Backport from mainline + 2017-03-02 Richard Biener + + PR c/79756 + * c-common.c (c_common_mark_addressable_vec): Look through + C_MAYBE_CONST_EXPR. + + 2017-01-10 Martin Liska + + Backport from mainline + 2017-01-05 Martin Liska + + PR pch/78970 + * c-opts.c (c_common_post_options): Reject '-' filename for a precompiled + header. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/c-family/c-ada-spec.c gcc-6.4.0/gcc/c-family/c-ada-spec.c *** gcc-6.3.0/gcc/c-family/c-ada-spec.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/c-family/c-ada-spec.c Wed Mar 22 10:43:10 2017 *************** macro_length (const cpp_macro *macro, in *** 72,78 **** if (macro->fun_like) { ! param_len++; for (i = 0; i < macro->paramc; i++) { cpp_hashnode *param = macro->params[i]; --- 72,78 ---- if (macro->fun_like) { ! (*param_len)++; for (i = 0; i < macro->paramc; i++) { cpp_hashnode *param = macro->params[i]; diff -Nrcpad gcc-6.3.0/gcc/c-family/c-common.c gcc-6.4.0/gcc/c-family/c-common.c *** gcc-6.3.0/gcc/c-family/c-common.c Tue Sep 27 10:54:00 2016 --- gcc-6.4.0/gcc/c-family/c-common.c Fri May 5 21:28:09 2017 *************** handle_mode_attribute (tree *node, tree *** 7596,7602 **** return NULL_TREE; } ! *node = typefm; } return NULL_TREE; --- 7596,7602 ---- return NULL_TREE; } ! *node = build_qualified_type (typefm, TYPE_QUALS (type)); } return NULL_TREE; *************** handle_nonnull_attribute (tree *node, tr *** 9061,9067 **** tree arg = TREE_VALUE (args); if (arg && TREE_CODE (arg) != IDENTIFIER_NODE && TREE_CODE (arg) != FUNCTION_DECL) ! arg = default_conversion (arg); if (!get_nonnull_operand (arg, &arg_num)) { --- 9061,9067 ---- tree arg = TREE_VALUE (args); if (arg && TREE_CODE (arg) != IDENTIFIER_NODE && TREE_CODE (arg) != FUNCTION_DECL) ! TREE_VALUE (args) = arg = default_conversion (arg); if (!get_nonnull_operand (arg, &arg_num)) { *************** complete_array_type (tree *ptype, tree i *** 10677,10682 **** --- 10677,10684 ---- void c_common_mark_addressable_vec (tree t) { + if (TREE_CODE (t) == C_MAYBE_CONST_EXPR) + t = C_MAYBE_CONST_EXPR_EXPR (t); while (handled_component_p (t)) t = TREE_OPERAND (t, 0); if (!VAR_P (t) *************** set_underlying_type (tree x) *** 12026,12032 **** tt = build_variant_type_copy (tt); TYPE_STUB_DECL (tt) = TYPE_STUB_DECL (DECL_ORIGINAL_TYPE (x)); TYPE_NAME (tt) = x; ! TREE_USED (tt) = TREE_USED (x); TREE_TYPE (x) = tt; } } --- 12028,12039 ---- tt = build_variant_type_copy (tt); TYPE_STUB_DECL (tt) = TYPE_STUB_DECL (DECL_ORIGINAL_TYPE (x)); TYPE_NAME (tt) = x; ! ! /* Mark the type as used only when its type decl is decorated ! with attribute unused. */ ! if (lookup_attribute ("unused", DECL_ATTRIBUTES (x))) ! TREE_USED (tt) = 1; ! TREE_TYPE (x) = tt; } } diff -Nrcpad gcc-6.3.0/gcc/c-family/c-opts.c gcc-6.4.0/gcc/c-family/c-opts.c *** gcc-6.3.0/gcc/c-family/c-opts.c Tue Mar 8 22:30:44 2016 --- gcc-6.4.0/gcc/c-family/c-opts.c Tue Jan 10 14:09:43 2017 *************** c_common_post_options (const char **pfil *** 742,748 **** in_fnames[0] = ""; } else if (strcmp (in_fnames[0], "-") == 0) ! in_fnames[0] = ""; if (out_fname == NULL || !strcmp (out_fname, "-")) out_fname = ""; --- 742,753 ---- in_fnames[0] = ""; } else if (strcmp (in_fnames[0], "-") == 0) ! { ! if (pch_file) ! error ("cannot use %<-%> as input filename for a precompiled header"); ! ! in_fnames[0] = ""; ! } if (out_fname == NULL || !strcmp (out_fname, "-")) out_fname = ""; diff -Nrcpad gcc-6.3.0/gcc/c-family/c-ubsan.c gcc-6.4.0/gcc/c-family/c-ubsan.c *** gcc-6.3.0/gcc/c-family/c-ubsan.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/c-family/c-ubsan.c Fri May 26 11:26:45 2017 *************** ubsan_instrument_shift (location_t loc, *** 169,174 **** --- 169,175 ---- /* In case we have a SAVE_EXPR in a conditional context, we need to make sure it gets evaluated before the condition. */ t = fold_build2 (COMPOUND_EXPR, TREE_TYPE (t), unshare_expr (op0), t); + t = fold_build2 (COMPOUND_EXPR, TREE_TYPE (t), unshare_expr (op1), t); t = fold_build2 (TRUTH_OR_EXPR, boolean_type_node, t, tt ? tt : integer_zero_node); *************** ubsan_maybe_instrument_reference_or_call *** 425,441 **** return fold_build2 (COMPOUND_EXPR, TREE_TYPE (op), call, op); } ! /* Instrument a NOP_EXPR to REFERENCE_TYPE if needed. */ void ! ubsan_maybe_instrument_reference (tree stmt) { ! tree op = TREE_OPERAND (stmt, 0); op = ubsan_maybe_instrument_reference_or_call (EXPR_LOCATION (stmt), op, TREE_TYPE (stmt), UBSAN_REF_BINDING); if (op) ! TREE_OPERAND (stmt, 0) = op; } /* Instrument a CALL_EXPR to a method if needed. */ --- 426,451 ---- return fold_build2 (COMPOUND_EXPR, TREE_TYPE (op), call, op); } ! /* Instrument a NOP_EXPR to REFERENCE_TYPE or INTEGER_CST with REFERENCE_TYPE ! type if needed. */ void ! ubsan_maybe_instrument_reference (tree *stmt_p) { ! tree stmt = *stmt_p; ! tree op = stmt; ! if (TREE_CODE (stmt) == NOP_EXPR) ! op = TREE_OPERAND (stmt, 0); op = ubsan_maybe_instrument_reference_or_call (EXPR_LOCATION (stmt), op, TREE_TYPE (stmt), UBSAN_REF_BINDING); if (op) ! { ! if (TREE_CODE (stmt) == NOP_EXPR) ! TREE_OPERAND (stmt, 0) = op; ! else ! *stmt_p = op; ! } } /* Instrument a CALL_EXPR to a method if needed. */ diff -Nrcpad gcc-6.3.0/gcc/c-family/c-ubsan.h gcc-6.4.0/gcc/c-family/c-ubsan.h *** gcc-6.3.0/gcc/c-family/c-ubsan.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/c-family/c-ubsan.h Fri May 5 21:49:20 2017 *************** extern tree ubsan_instrument_return (loc *** 28,34 **** extern tree ubsan_instrument_bounds (location_t, tree, tree *, bool); extern bool ubsan_array_ref_instrumented_p (const_tree); extern void ubsan_maybe_instrument_array_ref (tree *, bool); ! extern void ubsan_maybe_instrument_reference (tree); extern void ubsan_maybe_instrument_member_call (tree, bool); /* Declare this here as well as in ubsan.h. */ --- 28,34 ---- extern tree ubsan_instrument_bounds (location_t, tree, tree *, bool); extern bool ubsan_array_ref_instrumented_p (const_tree); extern void ubsan_maybe_instrument_array_ref (tree *, bool); ! extern void ubsan_maybe_instrument_reference (tree *); extern void ubsan_maybe_instrument_member_call (tree, bool); /* Declare this here as well as in ubsan.h. */ diff -Nrcpad gcc-6.3.0/gcc/calls.c gcc-6.4.0/gcc/calls.c *** gcc-6.3.0/gcc/calls.c Wed May 11 09:51:49 2016 --- gcc-6.4.0/gcc/calls.c Tue Feb 14 08:05:38 2017 *************** expand_call (tree exp, rtx target, int i *** 2695,2702 **** n_named_args = num_actuals; /* Make a vector to hold all the information about each arg. */ ! args = XALLOCAVEC (struct arg_data, num_actuals); ! memset (args, 0, num_actuals * sizeof (struct arg_data)); /* Build up entries in the ARGS array, compute the size of the arguments into ARGS_SIZE, etc. */ --- 2695,2701 ---- n_named_args = num_actuals; /* Make a vector to hold all the information about each arg. */ ! args = XCNEWVEC (struct arg_data, num_actuals); /* Build up entries in the ARGS array, compute the size of the arguments into ARGS_SIZE, etc. */ *************** expand_call (tree exp, rtx target, int i *** 3710,3715 **** --- 3709,3715 ---- currently_expanding_call--; free (stack_usage_map_buf); + free (args); /* Join result with returned bounds so caller may use them if needed. */ target = chkp_join_splitted_slot (target, valbnd); diff -Nrcpad gcc-6.3.0/gcc/cgraph.c gcc-6.4.0/gcc/cgraph.c *** gcc-6.3.0/gcc/cgraph.c Wed Dec 7 22:29:01 2016 --- gcc-6.4.0/gcc/cgraph.c Fri May 26 11:29:35 2017 *************** cgraph_edge::redirect_call_stmt_to_calle *** 1413,1420 **** if (skip_bounds) new_stmt = chkp_copy_call_skip_bounds (new_stmt); gimple_call_set_fndecl (new_stmt, e->callee->decl); ! gimple_call_set_fntype (new_stmt, gimple_call_fntype (e->call_stmt)); if (gimple_vdef (new_stmt) && TREE_CODE (gimple_vdef (new_stmt)) == SSA_NAME) --- 1413,1435 ---- if (skip_bounds) new_stmt = chkp_copy_call_skip_bounds (new_stmt); + tree old_fntype = gimple_call_fntype (e->call_stmt); gimple_call_set_fndecl (new_stmt, e->callee->decl); ! cgraph_node *origin = e->callee; ! while (origin->clone_of) ! origin = origin->clone_of; ! ! if ((origin->former_clone_of ! && old_fntype == TREE_TYPE (origin->former_clone_of)) ! || old_fntype == TREE_TYPE (origin->decl)) ! gimple_call_set_fntype (new_stmt, TREE_TYPE (e->callee->decl)); ! else ! { ! bitmap skip = e->callee->clone.combined_args_to_skip; ! tree t = cgraph_build_function_type_skip_args (old_fntype, skip, ! false); ! gimple_call_set_fntype (new_stmt, t); ! } if (gimple_vdef (new_stmt) && TREE_CODE (gimple_vdef (new_stmt)) == SSA_NAME) *************** cgraph_node::dump (FILE *f) *** 2071,2076 **** --- 2086,2093 ---- fprintf (f, " only_called_at_exit"); if (tm_clone) fprintf (f, " tm_clone"); + if (calls_comdat_local) + fprintf (f, " calls_comdat_local"); if (icf_merged) fprintf (f, " icf_merged"); if (merged_comdat) diff -Nrcpad gcc-6.3.0/gcc/cgraph.h gcc-6.4.0/gcc/cgraph.h *** gcc-6.3.0/gcc/cgraph.h Thu Apr 7 21:32:05 2016 --- gcc-6.4.0/gcc/cgraph.h Tue Apr 11 13:23:48 2017 *************** tree clone_function_name (tree decl, con *** 2272,2277 **** --- 2272,2279 ---- void tree_function_versioning (tree, tree, vec *, bool, bitmap, bool, bitmap, basic_block); + tree cgraph_build_function_type_skip_args (tree orig_type, bitmap args_to_skip, + bool skip_return); /* In cgraphbuild.c */ int compute_call_stmt_bb_frequency (tree, basic_block bb); diff -Nrcpad gcc-6.3.0/gcc/cgraphclones.c gcc-6.4.0/gcc/cgraphclones.c *** gcc-6.3.0/gcc/cgraphclones.c Tue Mar 29 19:37:55 2016 --- gcc-6.4.0/gcc/cgraphclones.c Tue Apr 11 13:23:48 2017 *************** cgraph_edge::clone (cgraph_node *n, gcal *** 152,160 **** /* Build variant of function type ORIG_TYPE skipping ARGS_TO_SKIP and the return value if SKIP_RETURN is true. */ ! static tree ! build_function_type_skip_args (tree orig_type, bitmap args_to_skip, ! bool skip_return) { tree new_type = NULL; tree args, new_args = NULL; --- 152,160 ---- /* Build variant of function type ORIG_TYPE skipping ARGS_TO_SKIP and the return value if SKIP_RETURN is true. */ ! tree ! cgraph_build_function_type_skip_args (tree orig_type, bitmap args_to_skip, ! bool skip_return) { tree new_type = NULL; tree args, new_args = NULL; *************** build_function_decl_skip_args (tree orig *** 219,225 **** if (prototype_p (new_type) || (skip_return && !VOID_TYPE_P (TREE_TYPE (new_type)))) new_type ! = build_function_type_skip_args (new_type, args_to_skip, skip_return); TREE_TYPE (new_decl) = new_type; /* For declarations setting DECL_VINDEX (i.e. methods) --- 219,226 ---- if (prototype_p (new_type) || (skip_return && !VOID_TYPE_P (TREE_TYPE (new_type)))) new_type ! = cgraph_build_function_type_skip_args (new_type, args_to_skip, ! skip_return); TREE_TYPE (new_decl) = new_type; /* For declarations setting DECL_VINDEX (i.e. methods) diff -Nrcpad gcc-6.3.0/gcc/cgraphunit.c gcc-6.4.0/gcc/cgraphunit.c *** gcc-6.3.0/gcc/cgraphunit.c Wed Mar 16 15:51:47 2016 --- gcc-6.4.0/gcc/cgraphunit.c Fri May 26 11:24:49 2017 *************** analyze_functions (bool first_time) *** 1193,1200 **** at looking at optimized away DECLs, since late_global_decl will subsequently be called from the contents of the now pruned symbol table. */ ! if (!decl_function_context (node->decl)) ! (*debug_hooks->late_global_decl) (node->decl); node->remove (); continue; --- 1193,1208 ---- at looking at optimized away DECLs, since late_global_decl will subsequently be called from the contents of the now pruned symbol table. */ ! if (VAR_P (node->decl) ! && !decl_function_context (node->decl)) ! { ! /* We are reclaiming totally unreachable code and variables ! so they effectively appear as readonly. Show that to ! the debug machinery. */ ! TREE_READONLY (node->decl) = 1; ! node->definition = false; ! (*debug_hooks->late_global_decl) (node->decl); ! } node->remove (); continue; *************** cgraph_node::expand_thunk (bool output_a *** 1756,1761 **** --- 1764,1773 ---- for (; i < nargs; i++, arg = DECL_CHAIN (arg)) { tree tmp = arg; + if (VECTOR_TYPE_P (TREE_TYPE (arg)) + || TREE_CODE (TREE_TYPE (arg)) == COMPLEX_TYPE) + DECL_GIMPLE_REG_P (arg) = 1; + if (!is_gimple_val (arg)) { tmp = create_tmp_reg (TYPE_MAIN_VARIANT diff -Nrcpad gcc-6.3.0/gcc/combine.c gcc-6.4.0/gcc/combine.c *** gcc-6.3.0/gcc/combine.c Mon Dec 12 13:00:53 2016 --- gcc-6.4.0/gcc/combine.c Fri May 5 21:56:08 2017 *************** make_compound_operation (rtx x, enum rtx *** 8069,8080 **** || GET_CODE (inner) == SUBREG /* (subreg:SI (and:DI (reg:DI) (const_int 0x800000000)) 0) is (const_int 0), rather than ! (subreg:SI (lshiftrt:DI (reg:DI) (const_int 35)) 0). */ || (GET_CODE (inner) == AND && CONST_INT_P (XEXP (inner, 1)) && GET_MODE_SIZE (mode) < GET_MODE_SIZE (GET_MODE (inner)) && exact_log2 (UINTVAL (XEXP (inner, 1))) ! >= GET_MODE_BITSIZE (mode)))) subreg_code = SET; tem = make_compound_operation (inner, subreg_code); --- 8069,8083 ---- || GET_CODE (inner) == SUBREG /* (subreg:SI (and:DI (reg:DI) (const_int 0x800000000)) 0) is (const_int 0), rather than ! (subreg:SI (lshiftrt:DI (reg:DI) (const_int 35)) 0). ! Similarly (subreg:QI (and:SI (reg:SI) (const_int 0x80)) 0) ! for non-equality comparisons against 0 is not equivalent ! to (subreg:QI (lshiftrt:SI (reg:SI) (const_int 7)) 0). */ || (GET_CODE (inner) == AND && CONST_INT_P (XEXP (inner, 1)) && GET_MODE_SIZE (mode) < GET_MODE_SIZE (GET_MODE (inner)) && exact_log2 (UINTVAL (XEXP (inner, 1))) ! >= GET_MODE_BITSIZE (mode) - 1))) subreg_code = SET; tem = make_compound_operation (inner, subreg_code); diff -Nrcpad gcc-6.3.0/gcc/common.opt gcc-6.4.0/gcc/common.opt *** gcc-6.3.0/gcc/common.opt Thu Mar 17 15:11:35 2016 --- gcc-6.4.0/gcc/common.opt Thu Jun 22 11:17:56 2017 *************** flow and turn the statement with erroneo *** 2373,2379 **** fisolate-erroneous-paths-attribute Common Report Var(flag_isolate_erroneous_paths_attribute) Optimization ! Detect paths that trigger erroneous or undefined behavior due a null value being used in a way forbidden by a returns_nonnull or nonnull attribute. Isolate those paths from the main control flow and turn the statement with erroneous or undefined behavior into a trap. --- 2373,2379 ---- fisolate-erroneous-paths-attribute Common Report Var(flag_isolate_erroneous_paths_attribute) Optimization ! Detect paths that trigger erroneous or undefined behavior due to a null value being used in a way forbidden by a returns_nonnull or nonnull attribute. Isolate those paths from the main control flow and turn the statement with erroneous or undefined behavior into a trap. diff -Nrcpad gcc-6.3.0/gcc/config/aarch64/aarch64-freebsd.h gcc-6.4.0/gcc/config/aarch64/aarch64-freebsd.h *** gcc-6.3.0/gcc/config/aarch64/aarch64-freebsd.h Thu Jan 1 00:00:00 1970 --- gcc-6.4.0/gcc/config/aarch64/aarch64-freebsd.h Sat Apr 8 19:16:17 2017 *************** *** 0 **** --- 1,102 ---- + /* Definitions for AArch64 running FreeBSD + Copyright (C) 2016-2017 Free Software Foundation, Inc. + + This file is part of GCC. + + GCC is free software; you can redistribute it and/or modify it + under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 3, or (at your option) + any later version. + + GCC is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + General Public License for more details. + + You should have received a copy of the GNU General Public License + along with GCC; see the file COPYING3. If not see + . */ + + #ifndef GCC_AARCH64_FREEBSD_H + #define GCC_AARCH64_FREEBSD_H + + #undef SUBTARGET_CPP_SPEC + #define SUBTARGET_CPP_SPEC FBSD_CPP_SPEC + + #if TARGET_BIG_ENDIAN_DEFAULT + #define TARGET_LINKER_EMULATION "aarch64fbsdb" + #else + #define TARGET_LINKER_EMULATION "aarch64fbsd" + #endif + + #undef SUBTARGET_EXTRA_LINK_SPEC + #define SUBTARGET_EXTRA_LINK_SPEC " -m" TARGET_LINKER_EMULATION + + #undef FBSD_TARGET_LINK_SPEC + #define FBSD_TARGET_LINK_SPEC " \ + %{p:%nconsider using `-pg' instead of `-p' with gprof (1) } \ + %{v:-V} \ + %{assert*} %{R*} %{rpath*} %{defsym*} \ + %{shared:-Bshareable %{h*} %{soname*}} \ + %{symbolic:-Bsymbolic} \ + %{static:-Bstatic} \ + %{!static: \ + %{rdynamic:-export-dynamic} \ + %{!shared:-dynamic-linker " FBSD_DYNAMIC_LINKER " }} \ + -X" SUBTARGET_EXTRA_LINK_SPEC " \ + %{mbig-endian:-EB} %{mlittle-endian:-EL}" + + #if TARGET_FIX_ERR_A53_835769_DEFAULT + #define CA53_ERR_835769_SPEC \ + " %{!mno-fix-cortex-a53-835769:--fix-cortex-a53-835769}" + #else + #define CA53_ERR_835769_SPEC \ + " %{mfix-cortex-a53-835769:--fix-cortex-a53-835769}" + #endif + + #ifdef TARGET_FIX_ERR_A53_843419_DEFAULT + #define CA53_ERR_843419_SPEC \ + " %{!mno-fix-cortex-a53-843419:--fix-cortex-a53-843419}" + #else + #define CA53_ERR_843419_SPEC \ + " %{mfix-cortex-a53-843419:--fix-cortex-a53-843419}" + #endif + + #undef LINK_SPEC + #define LINK_SPEC FBSD_TARGET_LINK_SPEC \ + CA53_ERR_835769_SPEC \ + CA53_ERR_843419_SPEC + + #define GNU_USER_TARGET_MATHFILE_SPEC \ + "%{Ofast|ffast-math|funsafe-math-optimizations:crtfastmath.o%s}" + + #undef ENDFILE_SPEC + #define ENDFILE_SPEC \ + GNU_USER_TARGET_MATHFILE_SPEC " " \ + FBSD_ENDFILE_SPEC + + #undef TARGET_OS_CPP_BUILTINS + #define TARGET_OS_CPP_BUILTINS() \ + do \ + { \ + FBSD_TARGET_OS_CPP_BUILTINS (); \ + } \ + while (false) + + #define TARGET_ASM_FILE_END file_end_indicate_exec_stack + + /* Uninitialized common symbols in non-PIE executables, even with + strong definitions in dependent shared libraries, will resolve + to COPY relocated symbol in the executable. See PR65780. */ + #undef TARGET_BINDS_LOCAL_P + #define TARGET_BINDS_LOCAL_P default_binds_local_p_2 + + /* Use the AAPCS type for wchar_t, override the one from + config/freebsd.h. */ + #undef WCHAR_TYPE + #define WCHAR_TYPE "unsigned int" + + #undef MCOUNT_NAME + #define MCOUNT_NAME ".mcount" + + #endif /* GCC_AARCH64_FREEBSD_H */ diff -Nrcpad gcc-6.3.0/gcc/config/aarch64/aarch64-protos.h gcc-6.4.0/gcc/config/aarch64/aarch64-protos.h *** gcc-6.3.0/gcc/config/aarch64/aarch64-protos.h Mon Apr 11 10:14:59 2016 --- gcc-6.4.0/gcc/config/aarch64/aarch64-protos.h Fri Jan 20 15:34:41 2017 *************** int aarch64_hard_regno_nregs (unsigned, *** 338,344 **** int aarch64_simd_attr_length_move (rtx_insn *); int aarch64_uxt_size (int, HOST_WIDE_INT); int aarch64_vec_fpconst_pow_of_2 (rtx); ! rtx aarch64_final_eh_return_addr (void); rtx aarch64_legitimize_reload_address (rtx *, machine_mode, int, int, int); rtx aarch64_mask_from_zextract_ops (rtx, rtx); const char *aarch64_output_move_struct (rtx *operands); --- 338,344 ---- int aarch64_simd_attr_length_move (rtx_insn *); int aarch64_uxt_size (int, HOST_WIDE_INT); int aarch64_vec_fpconst_pow_of_2 (rtx); ! rtx aarch64_eh_return_handler_rtx (void); rtx aarch64_legitimize_reload_address (rtx *, machine_mode, int, int, int); rtx aarch64_mask_from_zextract_ops (rtx, rtx); const char *aarch64_output_move_struct (rtx *operands); diff -Nrcpad gcc-6.3.0/gcc/config/aarch64/aarch64-simd.md gcc-6.4.0/gcc/config/aarch64/aarch64-simd.md *** gcc-6.3.0/gcc/config/aarch64/aarch64-simd.md Tue May 17 13:08:01 2016 --- gcc-6.4.0/gcc/config/aarch64/aarch64-simd.md Tue Mar 21 09:14:05 2017 *************** *** 107,113 **** case 1: return "str\\t%d1, %0"; case 2: return "orr\t%0., %1., %1."; case 3: return "umov\t%0, %1.d[0]"; ! case 4: return "ins\t%0.d[0], %1"; case 5: return "mov\t%0, %1"; case 6: return aarch64_output_simd_mov_immediate (operands[1], --- 107,113 ---- case 1: return "str\\t%d1, %0"; case 2: return "orr\t%0., %1., %1."; case 3: return "umov\t%0, %1.d[0]"; ! case 4: return "fmov\t%d0, %1"; case 5: return "mov\t%0, %1"; case 6: return aarch64_output_simd_mov_immediate (operands[1], *************** *** 116,123 **** } } [(set_attr "type" "neon_load1_1reg, neon_store1_1reg,\ ! neon_logic, neon_to_gp, neon_from_gp,\ ! mov_reg, neon_move")] ) (define_insn "*aarch64_simd_mov" --- 116,123 ---- } } [(set_attr "type" "neon_load1_1reg, neon_store1_1reg,\ ! neon_logic, neon_to_gp, f_mcr,\ ! mov_reg, neon_move")] ) (define_insn "*aarch64_simd_mov" diff -Nrcpad gcc-6.3.0/gcc/config/aarch64/aarch64.c gcc-6.4.0/gcc/config/aarch64/aarch64.c *** gcc-6.3.0/gcc/config/aarch64/aarch64.c Wed Dec 14 10:50:46 2016 --- gcc-6.4.0/gcc/config/aarch64/aarch64.c Fri Apr 7 16:26:52 2017 *************** aarch64_libgcc_cmp_return_mode (void) *** 2316,2322 **** static void aarch64_emit_probe_stack_range (HOST_WIDE_INT first, HOST_WIDE_INT size) { ! rtx reg1 = gen_rtx_REG (ptr_mode, PROBE_STACK_FIRST_REG); /* See the same assertion on PROBE_INTERVAL above. */ gcc_assert ((first % ARITH_FACTOR) == 0); --- 2316,2322 ---- static void aarch64_emit_probe_stack_range (HOST_WIDE_INT first, HOST_WIDE_INT size) { ! rtx reg1 = gen_rtx_REG (Pmode, PROBE_STACK_FIRST_REG); /* See the same assertion on PROBE_INTERVAL above. */ gcc_assert ((first % ARITH_FACTOR) == 0); *************** aarch64_emit_probe_stack_range (HOST_WID *** 2328,2336 **** const HOST_WIDE_INT base = ROUND_UP (size, ARITH_FACTOR); emit_set_insn (reg1, ! plus_constant (ptr_mode, stack_pointer_rtx, -(first + base))); ! emit_stack_probe (plus_constant (ptr_mode, reg1, base - size)); } /* The run-time loop is made up of 8 insns in the generic case while the --- 2328,2336 ---- const HOST_WIDE_INT base = ROUND_UP (size, ARITH_FACTOR); emit_set_insn (reg1, ! plus_constant (Pmode, stack_pointer_rtx, -(first + base))); ! emit_stack_probe (plus_constant (Pmode, reg1, base - size)); } /* The run-time loop is made up of 8 insns in the generic case while the *************** aarch64_emit_probe_stack_range (HOST_WID *** 2340,2346 **** HOST_WIDE_INT i, rem; emit_set_insn (reg1, ! plus_constant (ptr_mode, stack_pointer_rtx, -(first + PROBE_INTERVAL))); emit_stack_probe (reg1); --- 2340,2346 ---- HOST_WIDE_INT i, rem; emit_set_insn (reg1, ! plus_constant (Pmode, stack_pointer_rtx, -(first + PROBE_INTERVAL))); emit_stack_probe (reg1); *************** aarch64_emit_probe_stack_range (HOST_WID *** 2351,2357 **** for (i = 2 * PROBE_INTERVAL; i < size; i += PROBE_INTERVAL) { emit_set_insn (reg1, ! plus_constant (ptr_mode, reg1, -PROBE_INTERVAL)); emit_stack_probe (reg1); } --- 2351,2357 ---- for (i = 2 * PROBE_INTERVAL; i < size; i += PROBE_INTERVAL) { emit_set_insn (reg1, ! plus_constant (Pmode, reg1, -PROBE_INTERVAL)); emit_stack_probe (reg1); } *************** aarch64_emit_probe_stack_range (HOST_WID *** 2360,2370 **** { const HOST_WIDE_INT base = ROUND_UP (rem, ARITH_FACTOR); ! emit_set_insn (reg1, plus_constant (ptr_mode, reg1, -base)); ! emit_stack_probe (plus_constant (ptr_mode, reg1, base - rem)); } else ! emit_stack_probe (plus_constant (ptr_mode, reg1, -rem)); } /* Otherwise, do the same as above, but in a loop. Note that we must be --- 2360,2370 ---- { const HOST_WIDE_INT base = ROUND_UP (rem, ARITH_FACTOR); ! emit_set_insn (reg1, plus_constant (Pmode, reg1, -base)); ! emit_stack_probe (plus_constant (Pmode, reg1, base - rem)); } else ! emit_stack_probe (plus_constant (Pmode, reg1, -rem)); } /* Otherwise, do the same as above, but in a loop. Note that we must be *************** aarch64_emit_probe_stack_range (HOST_WID *** 2374,2380 **** equality test for the loop condition. */ else { ! rtx reg2 = gen_rtx_REG (ptr_mode, PROBE_STACK_SECOND_REG); /* Step 1: round SIZE to the previous multiple of the interval. */ --- 2374,2380 ---- equality test for the loop condition. */ else { ! rtx reg2 = gen_rtx_REG (Pmode, PROBE_STACK_SECOND_REG); /* Step 1: round SIZE to the previous multiple of the interval. */ *************** aarch64_emit_probe_stack_range (HOST_WID *** 2385,2395 **** /* TEST_ADDR = SP + FIRST. */ emit_set_insn (reg1, ! plus_constant (ptr_mode, stack_pointer_rtx, -first)); /* LAST_ADDR = SP + FIRST + ROUNDED_SIZE. */ emit_set_insn (reg2, ! plus_constant (ptr_mode, stack_pointer_rtx, -(first + rounded_size))); --- 2385,2395 ---- /* TEST_ADDR = SP + FIRST. */ emit_set_insn (reg1, ! plus_constant (Pmode, stack_pointer_rtx, -first)); /* LAST_ADDR = SP + FIRST + ROUNDED_SIZE. */ emit_set_insn (reg2, ! plus_constant (Pmode, stack_pointer_rtx, -(first + rounded_size))); *************** aarch64_emit_probe_stack_range (HOST_WID *** 2405,2414 **** probes at FIRST + N * PROBE_INTERVAL for values of N from 1 until it is equal to ROUNDED_SIZE. */ ! if (ptr_mode == DImode) ! emit_insn (gen_probe_stack_range_di (reg1, reg1, reg2)); ! else ! emit_insn (gen_probe_stack_range_si (reg1, reg1, reg2)); /* Step 4: probe at FIRST + SIZE if we cannot assert at compile-time --- 2405,2411 ---- probes at FIRST + N * PROBE_INTERVAL for values of N from 1 until it is equal to ROUNDED_SIZE. */ ! emit_insn (gen_probe_stack_range (reg1, reg1, reg2)); /* Step 4: probe at FIRST + SIZE if we cannot assert at compile-time *************** aarch64_emit_probe_stack_range (HOST_WID *** 2422,2432 **** { const HOST_WIDE_INT base = ROUND_UP (rem, ARITH_FACTOR); ! emit_set_insn (reg2, plus_constant (ptr_mode, reg2, -base)); ! emit_stack_probe (plus_constant (ptr_mode, reg2, base - rem)); } else ! emit_stack_probe (plus_constant (ptr_mode, reg2, -rem)); } } --- 2419,2429 ---- { const HOST_WIDE_INT base = ROUND_UP (rem, ARITH_FACTOR); ! emit_set_insn (reg2, plus_constant (Pmode, reg2, -base)); ! emit_stack_probe (plus_constant (Pmode, reg2, base - rem)); } else ! emit_stack_probe (plus_constant (Pmode, reg2, -rem)); } } *************** aarch64_frame_pointer_required (void) *** 2480,2485 **** --- 2477,2486 ---- && (!crtl->is_leaf || df_regs_ever_live_p (LR_REGNUM))) return true; + /* Force a frame pointer for EH returns so the return address is at FP+8. */ + if (crtl->calls_eh_return) + return true; + return false; } *************** aarch64_expand_epilogue (bool for_sibcal *** 3036,3042 **** rtx_insn *insn; /* We need to add memory barrier to prevent read from deallocated stack. */ bool need_barrier_p = (get_frame_size () != 0 ! || cfun->machine->frame.saved_varargs_size); aarch64_layout_frame (); --- 3037,3044 ---- rtx_insn *insn; /* We need to add memory barrier to prevent read from deallocated stack. */ bool need_barrier_p = (get_frame_size () != 0 ! || cfun->machine->frame.saved_varargs_size ! || crtl->calls_eh_return); aarch64_layout_frame (); *************** aarch64_expand_epilogue (bool for_sibcal *** 3189,3240 **** emit_jump_insn (ret_rtx); } ! /* Return the place to copy the exception unwinding return address to. ! This will probably be a stack slot, but could (in theory be the ! return register). */ ! rtx ! aarch64_final_eh_return_addr (void) ! { ! HOST_WIDE_INT fp_offset; ! ! aarch64_layout_frame (); ! ! fp_offset = cfun->machine->frame.frame_size ! - cfun->machine->frame.hard_fp_offset; ! if (cfun->machine->frame.reg_offset[LR_REGNUM] < 0) ! return gen_rtx_REG (DImode, LR_REGNUM); ! /* DSE and CSELIB do not detect an alias between sp+k1 and fp+k2. This can ! result in a store to save LR introduced by builtin_eh_return () being ! incorrectly deleted because the alias is not detected. ! So in the calculation of the address to copy the exception unwinding ! return address to, we note 2 cases. ! If FP is needed and the fp_offset is 0, it means that SP = FP and hence ! we return a SP-relative location since all the addresses are SP-relative ! in this case. This prevents the store from being optimized away. ! If the fp_offset is not 0, then the addresses will be FP-relative and ! therefore we return a FP-relative location. */ ! if (frame_pointer_needed) ! { ! if (fp_offset) ! return gen_frame_mem (DImode, ! plus_constant (Pmode, hard_frame_pointer_rtx, UNITS_PER_WORD)); ! else ! return gen_frame_mem (DImode, ! plus_constant (Pmode, stack_pointer_rtx, UNITS_PER_WORD)); ! } ! /* If FP is not needed, we calculate the location of LR, which would be ! at the top of the saved registers block. */ ! return gen_frame_mem (DImode, ! plus_constant (Pmode, ! stack_pointer_rtx, ! fp_offset ! + cfun->machine->frame.saved_regs_size ! - 2 * UNITS_PER_WORD)); } /* Possibly output code to build up a constant in a register. For --- 3191,3230 ---- emit_jump_insn (ret_rtx); } ! /* Implement EH_RETURN_HANDLER_RTX. EH returns need to either return ! normally or return to a previous frame after unwinding. ! An EH return uses a single shared return sequence. The epilogue is ! exactly like a normal epilogue except that it has an extra input ! register (EH_RETURN_STACKADJ_RTX) which contains the stack adjustment ! that must be applied after the frame has been destroyed. An extra label ! is inserted before the epilogue which initializes this register to zero, ! and this is the entry point for a normal return. ! An actual EH return updates the return address, initializes the stack ! adjustment and jumps directly into the epilogue (bypassing the zeroing ! of the adjustment). Since the return address is typically saved on the ! stack when a function makes a call, the saved LR must be updated outside ! the epilogue. ! This poses problems as the store is generated well before the epilogue, ! so the offset of LR is not known yet. Also optimizations will remove the ! store as it appears dead, even after the epilogue is generated (as the ! base or offset for loading LR is different in many cases). ! To avoid these problems this implementation forces the frame pointer ! in eh_return functions so that the location of LR is fixed and known early. ! It also marks the store volatile, so no optimization is permitted to ! remove the store. */ ! rtx ! aarch64_eh_return_handler_rtx (void) ! { ! rtx tmp = gen_frame_mem (Pmode, ! plus_constant (Pmode, hard_frame_pointer_rtx, UNITS_PER_WORD)); ! /* Mark the store volatile, so no optimization is permitted to remove it. */ ! MEM_VOLATILE_P (tmp) = true; ! return tmp; } /* Possibly output code to build up a constant in a register. For diff -Nrcpad gcc-6.3.0/gcc/config/aarch64/aarch64.h gcc-6.4.0/gcc/config/aarch64/aarch64.h *** gcc-6.3.0/gcc/config/aarch64/aarch64.h Fri Aug 12 11:26:06 2016 --- gcc-6.4.0/gcc/config/aarch64/aarch64.h Fri Jan 20 15:34:41 2017 *************** extern unsigned aarch64_architecture_ver *** 389,397 **** #define ASM_DECLARE_FUNCTION_NAME(STR, NAME, DECL) \ aarch64_declare_function_name (STR, NAME, DECL) ! /* The register that holds the return address in exception handlers. */ ! #define AARCH64_EH_STACKADJ_REGNUM (R0_REGNUM + 4) ! #define EH_RETURN_STACKADJ_RTX gen_rtx_REG (Pmode, AARCH64_EH_STACKADJ_REGNUM) /* Don't use __builtin_setjmp until we've defined it. */ #undef DONT_USE_BUILTIN_SETJMP --- 389,397 ---- #define ASM_DECLARE_FUNCTION_NAME(STR, NAME, DECL) \ aarch64_declare_function_name (STR, NAME, DECL) ! /* For EH returns X4 contains the stack adjustment. */ ! #define EH_RETURN_STACKADJ_RTX gen_rtx_REG (Pmode, R4_REGNUM) ! #define EH_RETURN_HANDLER_RTX aarch64_eh_return_handler_rtx () /* Don't use __builtin_setjmp until we've defined it. */ #undef DONT_USE_BUILTIN_SETJMP diff -Nrcpad gcc-6.3.0/gcc/config/aarch64/aarch64.md gcc-6.4.0/gcc/config/aarch64/aarch64.md *** gcc-6.3.0/gcc/config/aarch64/aarch64.md Tue Nov 22 16:55:16 2016 --- gcc-6.4.0/gcc/config/aarch64/aarch64.md Fri Apr 7 16:26:52 2017 *************** *** 587,611 **** [(set_attr "type" "branch")] ) - (define_insn "eh_return" - [(unspec_volatile [(match_operand:DI 0 "register_operand" "r")] - UNSPECV_EH_RETURN)] - "" - "#" - [(set_attr "type" "branch")] - - ) - - (define_split - [(unspec_volatile [(match_operand:DI 0 "register_operand" "")] - UNSPECV_EH_RETURN)] - "reload_completed" - [(set (match_dup 1) (match_dup 0))] - { - operands[1] = aarch64_final_eh_return_addr (); - } - ) - (define_insn "*cb1" [(set (pc) (if_then_else (EQL (match_operand:GPI 0 "register_operand" "r") (const_int 0)) --- 587,592 ---- *************** *** 5121,5131 **** (set_attr "type" "block")] ) ! (define_insn "probe_stack_range_" ! [(set (match_operand:PTR 0 "register_operand" "=r") ! (unspec_volatile:PTR [(match_operand:PTR 1 "register_operand" "0") ! (match_operand:PTR 2 "register_operand" "r")] ! UNSPECV_PROBE_STACK_RANGE))] "" { return aarch64_output_probe_stack_range (operands[0], operands[2]); --- 5102,5112 ---- (set_attr "type" "block")] ) ! (define_insn "probe_stack_range" ! [(set (match_operand:DI 0 "register_operand" "=r") ! (unspec_volatile:DI [(match_operand:DI 1 "register_operand" "0") ! (match_operand:DI 2 "register_operand" "r")] ! UNSPECV_PROBE_STACK_RANGE))] "" { return aarch64_output_probe_stack_range (operands[0], operands[2]); diff -Nrcpad gcc-6.3.0/gcc/config/aarch64/t-aarch64-freebsd gcc-6.4.0/gcc/config/aarch64/t-aarch64-freebsd *** gcc-6.3.0/gcc/config/aarch64/t-aarch64-freebsd Thu Jan 1 00:00:00 1970 --- gcc-6.4.0/gcc/config/aarch64/t-aarch64-freebsd Mon Jan 9 21:01:26 2017 *************** *** 0 **** --- 1,21 ---- + # Machine description for AArch64 architecture. + # Copyright (C) 2016-2017 Free Software Foundation, Inc. + # + # This file is part of GCC. + # + # GCC is free software; you can redistribute it and/or modify it + # under the terms of the GNU General Public License as published by + # the Free Software Foundation; either version 3, or (at your option) + # any later version. + # + # GCC is distributed in the hope that it will be useful, but + # WITHOUT ANY WARRANTY; without even the implied warranty of + # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + # General Public License for more details. + # + # You should have received a copy of the GNU General Public License + # along with GCC; see the file COPYING3. If not see + # . + + LIB1ASMSRC = aarch64/lib1funcs.asm + LIB1ASMFUNCS = _aarch64_sync_cache_range diff -Nrcpad gcc-6.3.0/gcc/config/arm/arm-builtins.c gcc-6.4.0/gcc/config/arm/arm-builtins.c *** gcc-6.3.0/gcc/config/arm/arm-builtins.c Tue May 31 08:29:39 2016 --- gcc-6.4.0/gcc/config/arm/arm-builtins.c Fri Jun 23 16:13:02 2017 *************** arm_init_builtins (void) *** 1783,1792 **** = build_function_type_list (unsigned_type_node, NULL); arm_builtin_decls[ARM_BUILTIN_GET_FPSCR] ! = add_builtin_function ("__builtin_arm_ldfscr", ftype_get_fpscr, ARM_BUILTIN_GET_FPSCR, BUILT_IN_MD, NULL, NULL_TREE); arm_builtin_decls[ARM_BUILTIN_SET_FPSCR] ! = add_builtin_function ("__builtin_arm_stfscr", ftype_set_fpscr, ARM_BUILTIN_SET_FPSCR, BUILT_IN_MD, NULL, NULL_TREE); } } --- 1783,1792 ---- = build_function_type_list (unsigned_type_node, NULL); arm_builtin_decls[ARM_BUILTIN_GET_FPSCR] ! = add_builtin_function ("__builtin_arm_get_fpscr", ftype_get_fpscr, ARM_BUILTIN_GET_FPSCR, BUILT_IN_MD, NULL, NULL_TREE); arm_builtin_decls[ARM_BUILTIN_SET_FPSCR] ! = add_builtin_function ("__builtin_arm_set_fpscr", ftype_set_fpscr, ARM_BUILTIN_SET_FPSCR, BUILT_IN_MD, NULL, NULL_TREE); } } *************** constant_arg: *** 2121,2127 **** { error ("%Kargument %d must be a constant immediate", exp, argc + 1); ! return const0_rtx; } break; --- 2121,2132 ---- { error ("%Kargument %d must be a constant immediate", exp, argc + 1); ! /* We have failed to expand the pattern, and are safely ! in to invalid code. But the mid-end will still try to ! build an assignment for this node while it expands, ! before stopping for the error, just pass it back ! TARGET to ensure a valid assignment. */ ! return target; } break; diff -Nrcpad gcc-6.3.0/gcc/config/arm/arm-protos.h gcc-6.4.0/gcc/config/arm/arm-protos.h *** gcc-6.3.0/gcc/config/arm/arm-protos.h Wed Feb 10 12:36:03 2016 --- gcc-6.4.0/gcc/config/arm/arm-protos.h Thu Apr 6 16:26:39 2017 *************** extern bool arm_is_constant_pool_ref (rt *** 360,366 **** #define FL_STRONG (1 << 8) /* StrongARM */ #define FL_ARCH5E (1 << 9) /* DSP extensions to v5 */ #define FL_XSCALE (1 << 10) /* XScale */ ! /* spare (1 << 11) */ #define FL_ARCH6 (1 << 12) /* Architecture rel 6. Adds media instructions. */ #define FL_VFPV2 (1 << 13) /* Vector Floating Point V2. */ --- 360,366 ---- #define FL_STRONG (1 << 8) /* StrongARM */ #define FL_ARCH5E (1 << 9) /* DSP extensions to v5 */ #define FL_XSCALE (1 << 10) /* XScale */ ! #define FL_LPAE (1 << 11) /* ARMv7-A LPAE. */ #define FL_ARCH6 (1 << 12) /* Architecture rel 6. Adds media instructions. */ #define FL_VFPV2 (1 << 13) /* Vector Floating Point V2. */ *************** extern bool arm_is_constant_pool_ref (rt *** 412,418 **** #define FL_FOR_ARCH6M (FL_FOR_ARCH6 & ~FL_NOTM) #define FL_FOR_ARCH7 ((FL_FOR_ARCH6T2 & ~FL_NOTM) | FL_ARCH7) #define FL_FOR_ARCH7A (FL_FOR_ARCH7 | FL_NOTM | FL_ARCH6K) ! #define FL_FOR_ARCH7VE (FL_FOR_ARCH7A | FL_THUMB_DIV | FL_ARM_DIV) #define FL_FOR_ARCH7R (FL_FOR_ARCH7A | FL_THUMB_DIV) #define FL_FOR_ARCH7M (FL_FOR_ARCH7 | FL_THUMB_DIV) #define FL_FOR_ARCH7EM (FL_FOR_ARCH7M | FL_ARCH7EM) --- 412,418 ---- #define FL_FOR_ARCH6M (FL_FOR_ARCH6 & ~FL_NOTM) #define FL_FOR_ARCH7 ((FL_FOR_ARCH6T2 & ~FL_NOTM) | FL_ARCH7) #define FL_FOR_ARCH7A (FL_FOR_ARCH7 | FL_NOTM | FL_ARCH6K) ! #define FL_FOR_ARCH7VE (FL_FOR_ARCH7A | FL_THUMB_DIV | FL_ARM_DIV | FL_LPAE) #define FL_FOR_ARCH7R (FL_FOR_ARCH7A | FL_THUMB_DIV) #define FL_FOR_ARCH7M (FL_FOR_ARCH7 | FL_THUMB_DIV) #define FL_FOR_ARCH7EM (FL_FOR_ARCH7M | FL_ARCH7EM) *************** extern int arm_arch_thumb2; *** 608,613 **** --- 608,616 ---- extern int arm_arch_arm_hwdiv; extern int arm_arch_thumb_hwdiv; + /* Nonzero if this chip supports the Large Physical Address Extension. */ + extern int arm_arch_lpae; + /* Nonzero if chip disallows volatile memory access in IT block. */ extern int arm_arch_no_volatile_ce; diff -Nrcpad gcc-6.3.0/gcc/config/arm/arm.c gcc-6.4.0/gcc/config/arm/arm.c *** gcc-6.3.0/gcc/config/arm/arm.c Mon Dec 12 10:58:17 2016 --- gcc-6.4.0/gcc/config/arm/arm.c Fri May 5 15:38:04 2017 *************** *** 61,66 **** --- 61,67 ---- #include "builtins.h" #include "tm-constrs.h" #include "rtl-iter.h" + #include "gimple.h" /* This file should be included last. */ #include "target-def.h" *************** struct four_ints *** 78,84 **** /* Forward function declarations. */ static bool arm_const_not_ok_for_debug_p (rtx); ! static bool arm_needs_doubleword_align (machine_mode, const_tree); static int arm_compute_static_chain_stack_bytes (void); static arm_stack_offsets *arm_get_frame_offsets (void); static void arm_add_gc_roots (void); --- 79,85 ---- /* Forward function declarations. */ static bool arm_const_not_ok_for_debug_p (rtx); ! static int arm_needs_doubleword_align (machine_mode, const_tree); static int arm_compute_static_chain_stack_bytes (void); static arm_stack_offsets *arm_get_frame_offsets (void); static void arm_add_gc_roots (void); *************** int arm_arch_thumb2; *** 859,864 **** --- 860,868 ---- int arm_arch_arm_hwdiv; int arm_arch_thumb_hwdiv; + /* Nonzero if this chip supports the Large Physical Address Extension. */ + int arm_arch_lpae; + /* Nonzero if chip disallows volatile memory access in IT block. */ int arm_arch_no_volatile_ce; *************** arm_option_override (void) *** 3181,3186 **** --- 3185,3191 ---- arm_arch_iwmmxt2 = ARM_FSET_HAS_CPU1 (insn_flags, FL_IWMMXT2); arm_arch_thumb_hwdiv = ARM_FSET_HAS_CPU1 (insn_flags, FL_THUMB_DIV); arm_arch_arm_hwdiv = ARM_FSET_HAS_CPU1 (insn_flags, FL_ARM_DIV); + arm_arch_lpae = ARM_FSET_HAS_CPU1 (insn_flags, FL_LPAE); arm_arch_no_volatile_ce = ARM_FSET_HAS_CPU1 (insn_flags, FL_NO_VOLATILE_CE); arm_tune_cortex_a9 = (arm_tune == cortexa9) != 0; arm_arch_crc = ARM_FSET_HAS_CPU1 (insn_flags, FL_CRC32); *************** aapcs_layout_arg (CUMULATIVE_ARGS *pcum, *** 6133,6140 **** /* C3 - For double-word aligned arguments, round the NCRN up to the next even number. */ ncrn = pcum->aapcs_ncrn; ! if ((ncrn & 1) && arm_needs_doubleword_align (mode, type)) ! ncrn++; nregs = ARM_NUM_REGS2(mode, type); --- 6138,6157 ---- /* C3 - For double-word aligned arguments, round the NCRN up to the next even number. */ ncrn = pcum->aapcs_ncrn; ! if (ncrn & 1) ! { ! int res = arm_needs_doubleword_align (mode, type); ! /* Only warn during RTL expansion of call stmts, otherwise we would ! warn e.g. during gimplification even on functions that will be ! always inlined, and we'd warn multiple times. Don't warn when ! called in expand_function_start either, as we warn instead in ! arm_function_arg_boundary in that case. */ ! if (res < 0 && warn_psabi && currently_expanding_gimple_stmt) ! inform (input_location, "parameter passing for argument of type " ! "%qT will change in GCC 7.1", type); ! if (res != 0) ! ncrn++; ! } nregs = ARM_NUM_REGS2(mode, type); *************** arm_init_cumulative_args (CUMULATIVE_ARG *** 6239,6250 **** } } ! /* Return true if mode/type need doubleword alignment. */ ! static bool arm_needs_doubleword_align (machine_mode mode, const_tree type) { if (!type) ! return PARM_BOUNDARY < GET_MODE_ALIGNMENT (mode); /* Scalar and vector types: Use natural alignment, i.e. of base type. */ if (!AGGREGATE_TYPE_P (type)) --- 6256,6271 ---- } } ! /* Return 1 if double word alignment is required for argument passing. ! Return -1 if double word alignment used to be required for argument ! passing before PR77728 ABI fix, but is not required anymore. ! Return 0 if double word alignment is not required and wasn't requried ! before either. */ ! static int arm_needs_doubleword_align (machine_mode mode, const_tree type) { if (!type) ! return GET_MODE_ALIGNMENT (mode) > PARM_BOUNDARY; /* Scalar and vector types: Use natural alignment, i.e. of base type. */ if (!AGGREGATE_TYPE_P (type)) *************** arm_needs_doubleword_align (machine_mode *** 6254,6265 **** if (TREE_CODE (type) == ARRAY_TYPE) return TYPE_ALIGN (TREE_TYPE (type)) > PARM_BOUNDARY; /* Record/aggregate types: Use greatest member alignment of any member. */ for (tree field = TYPE_FIELDS (type); field; field = DECL_CHAIN (field)) if (DECL_ALIGN (field) > PARM_BOUNDARY) ! return true; ! return false; } --- 6275,6295 ---- if (TREE_CODE (type) == ARRAY_TYPE) return TYPE_ALIGN (TREE_TYPE (type)) > PARM_BOUNDARY; + int ret = 0; /* Record/aggregate types: Use greatest member alignment of any member. */ for (tree field = TYPE_FIELDS (type); field; field = DECL_CHAIN (field)) if (DECL_ALIGN (field) > PARM_BOUNDARY) ! { ! if (TREE_CODE (field) == FIELD_DECL) ! return 1; ! else ! /* Before PR77728 fix, we were incorrectly considering also ! other aggregate fields, like VAR_DECLs, TYPE_DECLs etc. ! Make sure we can warn about that with -Wpsabi. */ ! ret = -1; ! } ! return ret; } *************** arm_function_arg (cumulative_args_t pcum *** 6316,6325 **** } /* Put doubleword aligned quantities in even register pairs. */ ! if (pcum->nregs & 1 ! && ARM_DOUBLEWORD_ALIGN ! && arm_needs_doubleword_align (mode, type)) ! pcum->nregs++; /* Only allow splitting an arg between regs and memory if all preceding args were allocated to regs. For args passed by reference we only count --- 6346,6360 ---- } /* Put doubleword aligned quantities in even register pairs. */ ! if ((pcum->nregs & 1) && ARM_DOUBLEWORD_ALIGN) ! { ! int res = arm_needs_doubleword_align (mode, type); ! if (res < 0 && warn_psabi) ! inform (input_location, "parameter passing for argument of type " ! "%qT will change in GCC 7.1", type); ! if (res != 0) ! pcum->nregs++; ! } /* Only allow splitting an arg between regs and memory if all preceding args were allocated to regs. For args passed by reference we only count *************** arm_function_arg (cumulative_args_t pcum *** 6338,6346 **** static unsigned int arm_function_arg_boundary (machine_mode mode, const_tree type) { ! return (ARM_DOUBLEWORD_ALIGN && arm_needs_doubleword_align (mode, type) ! ? DOUBLEWORD_ALIGNMENT ! : PARM_BOUNDARY); } static int --- 6373,6387 ---- static unsigned int arm_function_arg_boundary (machine_mode mode, const_tree type) { ! if (!ARM_DOUBLEWORD_ALIGN) ! return PARM_BOUNDARY; ! ! int res = arm_needs_doubleword_align (mode, type); ! if (res < 0 && warn_psabi) ! inform (input_location, "parameter passing for argument of type %qT " ! "will change in GCC 7.1", type); ! ! return res != 0 ? DOUBLEWORD_ALIGNMENT : PARM_BOUNDARY; } static int *************** arm_function_ok_for_sibcall (tree decl, *** 6707,6712 **** --- 6748,6761 ---- if (TARGET_VXWORKS_RTP && flag_pic && decl && !targetm.binds_local_p (decl)) return false; + /* ??? Cannot tail-call to long calls with APCS frame and VFP, because IP + may be used both as target of the call and base register for restoring + the VFP registers */ + if (TARGET_APCS_FRAME && TARGET_ARM + && TARGET_HARD_FLOAT && TARGET_VFP + && decl && arm_is_long_call_p (decl)) + return false; + /* If we are interworking and the function is not declared static then we can't tail-call it unless we know that it exists in this compilation unit (since it might be a Thumb routine). */ *************** legitimize_pic_address (rtx orig, machin *** 6859,6867 **** same segment as the GOT. Unfortunately, the flexibility of linker scripts means that we can't be sure of that in general, so assume that GOTOFF is never valid on VxWorks. */ if ((GET_CODE (orig) == LABEL_REF ! || (GET_CODE (orig) == SYMBOL_REF && ! SYMBOL_REF_LOCAL_P (orig))) && NEED_GOT_RELOC && arm_pic_data_is_text_relative) insn = arm_pic_static_addr (orig, reg); --- 6908,6920 ---- same segment as the GOT. Unfortunately, the flexibility of linker scripts means that we can't be sure of that in general, so assume that GOTOFF is never valid on VxWorks. */ + /* References to weak symbols cannot be resolved locally: they + may be overridden by a non-weak definition at link time. */ if ((GET_CODE (orig) == LABEL_REF ! || (GET_CODE (orig) == SYMBOL_REF ! && SYMBOL_REF_LOCAL_P (orig) ! && (SYMBOL_REF_DECL (orig) ! ? !DECL_WEAK (SYMBOL_REF_DECL (orig)) : 1))) && NEED_GOT_RELOC && arm_pic_data_is_text_relative) insn = arm_pic_static_addr (orig, reg); *************** arm_assemble_integer (rtx x, unsigned in *** 22687,22694 **** { /* See legitimize_pic_address for an explanation of the TARGET_VXWORKS_RTP check. */ if (!arm_pic_data_is_text_relative ! || (GET_CODE (x) == SYMBOL_REF && !SYMBOL_REF_LOCAL_P (x))) fputs ("(GOT)", asm_out_file); else fputs ("(GOTOFF)", asm_out_file); --- 22740,22753 ---- { /* See legitimize_pic_address for an explanation of the TARGET_VXWORKS_RTP check. */ + /* References to weak symbols cannot be resolved locally: + they may be overridden by a non-weak definition at link + time. */ if (!arm_pic_data_is_text_relative ! || (GET_CODE (x) == SYMBOL_REF ! && (!SYMBOL_REF_LOCAL_P (x) ! || (SYMBOL_REF_DECL (x) ! ? DECL_WEAK (SYMBOL_REF_DECL (x)) : 0)))) fputs ("(GOT)", asm_out_file); else fputs ("(GOTOFF)", asm_out_file); *************** arm_setup_incoming_varargs (cumulative_a *** 26380,26387 **** if (pcum->pcs_variant <= ARM_PCS_AAPCS_LOCAL) { nregs = pcum->aapcs_ncrn; ! if ((nregs & 1) && arm_needs_doubleword_align (mode, type)) ! nregs++; } else nregs = pcum->nregs; --- 26439,26453 ---- if (pcum->pcs_variant <= ARM_PCS_AAPCS_LOCAL) { nregs = pcum->aapcs_ncrn; ! if (nregs & 1) ! { ! int res = arm_needs_doubleword_align (mode, type); ! if (res < 0 && warn_psabi) ! inform (input_location, "parameter passing for argument of " ! "type %qT will change in GCC 7.1", type); ! if (res != 0) ! nregs++; ! } } else nregs = pcum->nregs; *************** arm_promote_function_mode (const_tree ty *** 26413,26424 **** return mode; } - /* AAPCS based ABIs use short enums by default. */ static bool arm_default_short_enums (void) { ! return TARGET_AAPCS_BASED && arm_abi != ARM_ABI_AAPCS_LINUX; } --- 26479,26489 ---- return mode; } static bool arm_default_short_enums (void) { ! return ARM_DEFAULT_SHORT_ENUMS; } diff -Nrcpad gcc-6.3.0/gcc/config/arm/arm.h gcc-6.4.0/gcc/config/arm/arm.h *** gcc-6.3.0/gcc/config/arm/arm.h Fri Apr 1 14:58:53 2016 --- gcc-6.4.0/gcc/config/arm/arm.h Fri Apr 7 07:06:01 2017 *************** extern void (*arm_lang_output_object_att *** 254,261 **** #define TARGET_HAVE_LDREX ((arm_arch6 && TARGET_ARM) || arm_arch7) /* Nonzero if this chip supports LPAE. */ ! #define TARGET_HAVE_LPAE \ ! (arm_arch7 && ARM_FSET_HAS_CPU1 (insn_flags, FL_FOR_ARCH7VE)) /* Nonzero if this chip supports ldrex{bh} and strex{bh}. */ #define TARGET_HAVE_LDREXBH ((arm_arch6k && TARGET_ARM) || arm_arch7) --- 254,260 ---- #define TARGET_HAVE_LDREX ((arm_arch6 && TARGET_ARM) || arm_arch7) /* Nonzero if this chip supports LPAE. */ ! #define TARGET_HAVE_LPAE (arm_arch_lpae) /* Nonzero if this chip supports ldrex{bh} and strex{bh}. */ #define TARGET_HAVE_LDREXBH ((arm_arch6k && TARGET_ARM) || arm_arch7) *************** extern int arm_fpu_attr; *** 374,379 **** --- 373,384 ---- #define ARM_DEFAULT_ABI ARM_ABI_APCS #endif + /* AAPCS based ABIs use short enums by default. */ + #ifndef ARM_DEFAULT_SHORT_ENUMS + #define ARM_DEFAULT_SHORT_ENUMS \ + (TARGET_AAPCS_BASED && arm_abi != ARM_ABI_AAPCS_LINUX) + #endif + /* Map each of the micro-architecture variants to their corresponding major architecture revision. */ diff -Nrcpad gcc-6.3.0/gcc/config/arm/neon.md gcc-6.4.0/gcc/config/arm/neon.md *** gcc-6.3.0/gcc/config/arm/neon.md Thu Feb 11 23:53:54 2016 --- gcc-6.4.0/gcc/config/arm/neon.md Fri Jan 6 14:26:06 2017 *************** *** 1045,1056 **** ) (define_insn_and_split "ashldi3_neon" ! [(set (match_operand:DI 0 "s_register_operand" "= w, w,?&r,?r, ?w,w") ! (ashift:DI (match_operand:DI 1 "s_register_operand" " 0w, w, 0r, r, 0w,w") ! (match_operand:SI 2 "general_operand" "rUm, i, r, i,rUm,i"))) ! (clobber (match_scratch:SI 3 "= X, X,?&r, X, X,X")) ! (clobber (match_scratch:SI 4 "= X, X,?&r, X, X,X")) ! (clobber (match_scratch:DI 5 "=&w, X, X, X, &w,X")) (clobber (reg:CC_C CC_REGNUM))] "TARGET_NEON" "#" --- 1045,1056 ---- ) (define_insn_and_split "ashldi3_neon" ! [(set (match_operand:DI 0 "s_register_operand" "= w, w,?&r,?r,?&r, ?w,w") ! (ashift:DI (match_operand:DI 1 "s_register_operand" " 0w, w, 0r, 0, r, 0w,w") ! (match_operand:SI 2 "general_operand" "rUm, i, r, i, i,rUm,i"))) ! (clobber (match_scratch:SI 3 "= X, X,?&r, X, X, X,X")) ! (clobber (match_scratch:SI 4 "= X, X,?&r, X, X, X,X")) ! (clobber (match_scratch:DI 5 "=&w, X, X, X, X, &w,X")) (clobber (reg:CC_C CC_REGNUM))] "TARGET_NEON" "#" *************** *** 1082,1090 **** } else { ! if (CONST_INT_P (operands[2]) && INTVAL (operands[2]) == 1 ! && (!reg_overlap_mentioned_p (operands[0], operands[1]) ! || REGNO (operands[0]) == REGNO (operands[1]))) /* This clobbers CC. */ emit_insn (gen_arm_ashldi3_1bit (operands[0], operands[1])); else --- 1082,1092 ---- } else { ! /* The shift expanders support either full overlap or no overlap. */ ! gcc_assert (!reg_overlap_mentioned_p (operands[0], operands[1]) ! || REGNO (operands[0]) == REGNO (operands[1])); ! ! if (operands[2] == CONST1_RTX (SImode)) /* This clobbers CC. */ emit_insn (gen_arm_ashldi3_1bit (operands[0], operands[1])); else *************** *** 1093,1100 **** } DONE; }" ! [(set_attr "arch" "neon_for_64bits,neon_for_64bits,*,*,avoid_neon_for_64bits,avoid_neon_for_64bits") ! (set_attr "opt" "*,*,speed,speed,*,*") (set_attr "type" "multiple")] ) --- 1095,1102 ---- } DONE; }" ! [(set_attr "arch" "neon_for_64bits,neon_for_64bits,*,*,*,avoid_neon_for_64bits,avoid_neon_for_64bits") ! (set_attr "opt" "*,*,speed,speed,speed,*,*") (set_attr "type" "multiple")] ) *************** *** 1143,1154 **** ;; ashrdi3_neon ;; lshrdi3_neon (define_insn_and_split "di3_neon" ! [(set (match_operand:DI 0 "s_register_operand" "= w, w,?&r,?r,?w,?w") ! (RSHIFTS:DI (match_operand:DI 1 "s_register_operand" " 0w, w, 0r, r,0w, w") ! (match_operand:SI 2 "reg_or_int_operand" " r, i, r, i, r, i"))) ! (clobber (match_scratch:SI 3 "=2r, X, &r, X,2r, X")) ! (clobber (match_scratch:SI 4 "= X, X, &r, X, X, X")) ! (clobber (match_scratch:DI 5 "=&w, X, X, X,&w, X")) (clobber (reg:CC CC_REGNUM))] "TARGET_NEON" "#" --- 1145,1156 ---- ;; ashrdi3_neon ;; lshrdi3_neon (define_insn_and_split "di3_neon" ! [(set (match_operand:DI 0 "s_register_operand" "= w, w,?&r,?r,?&r,?w,?w") ! (RSHIFTS:DI (match_operand:DI 1 "s_register_operand" " 0w, w, 0r, 0, r,0w, w") ! (match_operand:SI 2 "reg_or_int_operand" " r, i, r, i, i, r, i"))) ! (clobber (match_scratch:SI 3 "=2r, X, &r, X, X,2r, X")) ! (clobber (match_scratch:SI 4 "= X, X, &r, X, X, X, X")) ! (clobber (match_scratch:DI 5 "=&w, X, X, X, X,&w, X")) (clobber (reg:CC CC_REGNUM))] "TARGET_NEON" "#" *************** *** 1184,1192 **** } else { ! if (CONST_INT_P (operands[2]) && INTVAL (operands[2]) == 1 ! && (!reg_overlap_mentioned_p (operands[0], operands[1]) ! || REGNO (operands[0]) == REGNO (operands[1]))) /* This clobbers CC. */ emit_insn (gen_arm_di3_1bit (operands[0], operands[1])); else --- 1186,1196 ---- } else { ! /* The shift expanders support either full overlap or no overlap. */ ! gcc_assert (!reg_overlap_mentioned_p (operands[0], operands[1]) ! || REGNO (operands[0]) == REGNO (operands[1])); ! ! if (operands[2] == CONST1_RTX (SImode)) /* This clobbers CC. */ emit_insn (gen_arm_di3_1bit (operands[0], operands[1])); else *************** *** 1197,1204 **** DONE; }" ! [(set_attr "arch" "neon_for_64bits,neon_for_64bits,*,*,avoid_neon_for_64bits,avoid_neon_for_64bits") ! (set_attr "opt" "*,*,speed,speed,*,*") (set_attr "type" "multiple")] ) --- 1201,1208 ---- DONE; }" ! [(set_attr "arch" "neon_for_64bits,neon_for_64bits,*,*,*,avoid_neon_for_64bits,avoid_neon_for_64bits") ! (set_attr "opt" "*,*,speed,speed,speed,*,*") (set_attr "type" "multiple")] ) diff -Nrcpad gcc-6.3.0/gcc/config/arm/rtems.h gcc-6.4.0/gcc/config/arm/rtems.h *** gcc-6.3.0/gcc/config/arm/rtems.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/arm/rtems.h Fri Apr 7 07:06:01 2017 *************** *** 27,29 **** --- 27,31 ---- builtin_assert ("system=rtems"); \ TARGET_BPABI_CPP_BUILTINS(); \ } while (0) + + #define ARM_DEFAULT_SHORT_ENUMS false diff -Nrcpad gcc-6.3.0/gcc/config/avr/avr.c gcc-6.4.0/gcc/config/avr/avr.c *** gcc-6.3.0/gcc/config/avr/avr.c Fri Sep 23 08:14:28 2016 --- gcc-6.4.0/gcc/config/avr/avr.c Wed Apr 19 12:22:59 2017 *************** *** 20,29 **** --- 20,32 ---- #include "config.h" #include "system.h" + #include "intl.h" #include "coretypes.h" #include "backend.h" #include "target.h" #include "rtl.h" + #include "tree.h" + #include "cgraph.h" #include "c-family/c-common.h" #include "cfghooks.h" #include "df.h" *************** avr_pgm_check_var_decl (tree node) *** 9272,9299 **** case VAR_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (node)), as) ! reason = "variable"; break; case PARM_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (node)), as) ! reason = "function parameter"; break; case FIELD_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (node)), as) ! reason = "structure field"; break; case FUNCTION_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (TREE_TYPE (node))), as) ! reason = "return type of function"; break; case POINTER_TYPE: if (as = avr_nonconst_pointer_addrspace (node), as) ! reason = "pointer"; break; } --- 9275,9302 ---- case VAR_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (node)), as) ! reason = _("variable"); break; case PARM_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (node)), as) ! reason = _("function parameter"); break; case FIELD_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (node)), as) ! reason = _("structure field"); break; case FUNCTION_DECL: if (as = avr_nonconst_pointer_addrspace (TREE_TYPE (TREE_TYPE (node))), as) ! reason = _("return type of function"); break; case POINTER_TYPE: if (as = avr_nonconst_pointer_addrspace (node), as) ! reason = _("pointer"); break; } *************** avr_encode_section_info (tree decl, rtx *** 9592,9600 **** && !DECL_EXTERNAL (decl) && avr_progmem_p (decl, DECL_ATTRIBUTES (decl))) { ! warning (OPT_Wuninitialized, ! "uninitialized variable %q+D put into " ! "program memory area", decl); } default_encode_section_info (decl, rtl, new_decl_p); --- 9595,9608 ---- && !DECL_EXTERNAL (decl) && avr_progmem_p (decl, DECL_ATTRIBUTES (decl))) { ! // Don't warn for (implicit) aliases like in PR80462. ! tree asmname = DECL_ASSEMBLER_NAME (decl); ! varpool_node *node = varpool_node::get_for_asmname (asmname); ! bool alias_p = node && node->alias; ! ! if (!alias_p) ! warning (OPT_Wuninitialized, "uninitialized variable %q+D put into " ! "program memory area", decl); } default_encode_section_info (decl, rtl, new_decl_p); diff -Nrcpad gcc-6.3.0/gcc/config/darwin-driver.c gcc-6.4.0/gcc/config/darwin-driver.c *** gcc-6.3.0/gcc/config/darwin-driver.c Sun Dec 11 16:23:04 2016 --- gcc-6.4.0/gcc/config/darwin-driver.c Wed Jun 21 16:03:07 2017 *************** darwin_driver_init (unsigned int *decode *** 299,308 **** if (vers_string != NULL) { char *asm_major = NULL; ! char *first_period = strchr(vers_string, '.'); if (first_period != NULL) { ! char *second_period = strchr(first_period+1, '.'); if (second_period != NULL) asm_major = xstrndup (vers_string, second_period-vers_string); else --- 299,308 ---- if (vers_string != NULL) { char *asm_major = NULL; ! const char *first_period = strchr(vers_string, '.'); if (first_period != NULL) { ! const char *second_period = strchr(first_period+1, '.'); if (second_period != NULL) asm_major = xstrndup (vers_string, second_period-vers_string); else diff -Nrcpad gcc-6.3.0/gcc/config/i386/avx2intrin.h gcc-6.4.0/gcc/config/i386/avx2intrin.h *** gcc-6.3.0/gcc/config/i386/avx2intrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/avx2intrin.h Thu Jun 1 19:38:29 2017 *************** _mm_srlv_epi64 (__m128i __X, __m128i __Y *** 1246,1667 **** #ifdef __OPTIMIZE__ extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_pd (double const *base, __m128i index, const int scale) { ! __v2df zero = _mm_setzero_pd (); ! __v2df mask = _mm_cmpeq_pd (zero, zero); return (__m128d) __builtin_ia32_gathersiv2df (_mm_undefined_pd (), ! base, ! (__v4si)index, ! mask, ! scale); } extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_pd (__m128d src, double const *base, __m128i index, ! __m128d mask, const int scale) { ! return (__m128d) __builtin_ia32_gathersiv2df ((__v2df)src, ! base, ! (__v4si)index, ! (__v2df)mask, ! scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_pd (double const *base, __m128i index, const int scale) { ! __v4df zero = _mm256_setzero_pd (); ! __v4df mask = _mm256_cmp_pd (zero, zero, _CMP_EQ_OQ); return (__m256d) __builtin_ia32_gathersiv4df (_mm256_undefined_pd (), ! base, ! (__v4si)index, ! mask, ! scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_pd (__m256d src, double const *base, ! __m128i index, __m256d mask, const int scale) { ! return (__m256d) __builtin_ia32_gathersiv4df ((__v4df)src, ! base, ! (__v4si)index, ! (__v4df)mask, ! scale); } extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_pd (double const *base, __m128i index, const int scale) { ! __v2df src = _mm_setzero_pd (); ! __v2df mask = _mm_cmpeq_pd (src, src); ! return (__m128d) __builtin_ia32_gatherdiv2df (src, ! base, ! (__v2di)index, ! mask, ! scale); } extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_pd (__m128d src, double const *base, __m128i index, ! __m128d mask, const int scale) { ! return (__m128d) __builtin_ia32_gatherdiv2df ((__v2df)src, ! base, ! (__v2di)index, ! (__v2df)mask, ! scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_pd (double const *base, __m256i index, const int scale) { ! __v4df src = _mm256_setzero_pd (); ! __v4df mask = _mm256_cmp_pd (src, src, _CMP_EQ_OQ); ! return (__m256d) __builtin_ia32_gatherdiv4df (src, ! base, ! (__v4di)index, ! mask, ! scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_pd (__m256d src, double const *base, ! __m256i index, __m256d mask, const int scale) { ! return (__m256d) __builtin_ia32_gatherdiv4df ((__v4df)src, ! base, ! (__v4di)index, ! (__v4df)mask, ! scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_ps (float const *base, __m128i index, const int scale) { ! __v4sf src = _mm_setzero_ps (); ! __v4sf mask = _mm_cmpeq_ps (src, src); ! return (__m128) __builtin_ia32_gathersiv4sf (src, ! base, ! (__v4si)index, ! mask, ! scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_ps (__m128 src, float const *base, __m128i index, ! __m128 mask, const int scale) { ! return (__m128) __builtin_ia32_gathersiv4sf ((__v4sf)src, ! base, ! (__v4si)index, ! (__v4sf)mask, ! scale); } extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_ps (float const *base, __m256i index, const int scale) { ! __v8sf src = _mm256_setzero_ps (); ! __v8sf mask = _mm256_cmp_ps (src, src, _CMP_EQ_OQ); ! return (__m256) __builtin_ia32_gathersiv8sf (src, ! base, ! (__v8si)index, ! mask, ! scale); } extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_ps (__m256 src, float const *base, ! __m256i index, __m256 mask, const int scale) { ! return (__m256) __builtin_ia32_gathersiv8sf ((__v8sf)src, ! base, ! (__v8si)index, ! (__v8sf)mask, ! scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_ps (float const *base, __m128i index, const int scale) { ! __v4sf src = _mm_setzero_ps (); ! __v4sf mask = _mm_cmpeq_ps (src, src); ! return (__m128) __builtin_ia32_gatherdiv4sf (src, ! base, ! (__v2di)index, ! mask, ! scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_ps (__m128 src, float const *base, __m128i index, ! __m128 mask, const int scale) { ! return (__m128) __builtin_ia32_gatherdiv4sf ((__v4sf)src, ! base, ! (__v2di)index, ! (__v4sf)mask, ! scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_ps (float const *base, __m256i index, const int scale) { ! __v4sf src = _mm_setzero_ps (); ! __v4sf mask = _mm_cmpeq_ps (src, src); ! return (__m128) __builtin_ia32_gatherdiv4sf256 (src, ! base, ! (__v4di)index, ! mask, ! scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_ps (__m128 src, float const *base, ! __m256i index, __m128 mask, const int scale) { ! return (__m128) __builtin_ia32_gatherdiv4sf256 ((__v4sf)src, ! base, ! (__v4di)index, ! (__v4sf)mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_epi64 (long long int const *base, ! __m128i index, const int scale) { ! __v2di src = __extension__ (__v2di){ 0, 0 }; ! __v2di mask = __extension__ (__v2di){ ~0, ~0 }; ! return (__m128i) __builtin_ia32_gathersiv2di (src, ! base, ! (__v4si)index, ! mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_epi64 (__m128i src, long long int const *base, ! __m128i index, __m128i mask, const int scale) { ! return (__m128i) __builtin_ia32_gathersiv2di ((__v2di)src, ! base, ! (__v4si)index, ! (__v2di)mask, ! scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_epi64 (long long int const *base, ! __m128i index, const int scale) { ! __v4di src = __extension__ (__v4di){ 0, 0, 0, 0 }; ! __v4di mask = __extension__ (__v4di){ ~0, ~0, ~0, ~0 }; ! return (__m256i) __builtin_ia32_gathersiv4di (src, ! base, ! (__v4si)index, ! mask, ! scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_epi64 (__m256i src, long long int const *base, ! __m128i index, __m256i mask, const int scale) { ! return (__m256i) __builtin_ia32_gathersiv4di ((__v4di)src, ! base, ! (__v4si)index, ! (__v4di)mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_epi64 (long long int const *base, ! __m128i index, const int scale) { ! __v2di src = __extension__ (__v2di){ 0, 0 }; ! __v2di mask = __extension__ (__v2di){ ~0, ~0 }; ! return (__m128i) __builtin_ia32_gatherdiv2di (src, ! base, ! (__v2di)index, ! mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_epi64 (__m128i src, long long int const *base, __m128i index, ! __m128i mask, const int scale) { ! return (__m128i) __builtin_ia32_gatherdiv2di ((__v2di)src, ! base, ! (__v2di)index, ! (__v2di)mask, ! scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_epi64 (long long int const *base, ! __m256i index, const int scale) { ! __v4di src = __extension__ (__v4di){ 0, 0, 0, 0 }; ! __v4di mask = __extension__ (__v4di){ ~0, ~0, ~0, ~0 }; ! return (__m256i) __builtin_ia32_gatherdiv4di (src, ! base, ! (__v4di)index, ! mask, ! scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_epi64 (__m256i src, long long int const *base, ! __m256i index, __m256i mask, const int scale) { ! return (__m256i) __builtin_ia32_gatherdiv4di ((__v4di)src, ! base, ! (__v4di)index, ! (__v4di)mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_epi32 (int const *base, __m128i index, const int scale) { ! __v4si src = __extension__ (__v4si){ 0, 0, 0, 0 }; ! __v4si mask = __extension__ (__v4si){ ~0, ~0, ~0, ~0 }; ! return (__m128i) __builtin_ia32_gathersiv4si (src, ! base, ! (__v4si)index, ! mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_epi32 (__m128i src, int const *base, __m128i index, ! __m128i mask, const int scale) { ! return (__m128i) __builtin_ia32_gathersiv4si ((__v4si)src, ! base, ! (__v4si)index, ! (__v4si)mask, ! scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_epi32 (int const *base, __m256i index, const int scale) { ! __v8si src = __extension__ (__v8si){ 0, 0, 0, 0, 0, 0, 0, 0 }; ! __v8si mask = __extension__ (__v8si){ ~0, ~0, ~0, ~0, ~0, ~0, ~0, ~0 }; ! return (__m256i) __builtin_ia32_gathersiv8si (src, ! base, ! (__v8si)index, ! mask, ! scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_epi32 (__m256i src, int const *base, ! __m256i index, __m256i mask, const int scale) { ! return (__m256i) __builtin_ia32_gathersiv8si ((__v8si)src, ! base, ! (__v8si)index, ! (__v8si)mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_epi32 (int const *base, __m128i index, const int scale) { ! __v4si src = __extension__ (__v4si){ 0, 0, 0, 0 }; ! __v4si mask = __extension__ (__v4si){ ~0, ~0, ~0, ~0 }; ! return (__m128i) __builtin_ia32_gatherdiv4si (src, ! base, ! (__v2di)index, ! mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_epi32 (__m128i src, int const *base, __m128i index, ! __m128i mask, const int scale) { ! return (__m128i) __builtin_ia32_gatherdiv4si ((__v4si)src, ! base, ! (__v2di)index, ! (__v4si)mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_epi32 (int const *base, __m256i index, const int scale) { ! __v4si src = __extension__ (__v4si){ 0, 0, 0, 0 }; ! __v4si mask = __extension__ (__v4si){ ~0, ~0, ~0, ~0 }; ! return (__m128i) __builtin_ia32_gatherdiv4si256 (src, ! base, ! (__v4di)index, ! mask, ! scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_epi32 (__m128i src, int const *base, ! __m256i index, __m128i mask, const int scale) { ! return (__m128i) __builtin_ia32_gatherdiv4si256 ((__v4si)src, ! base, ! (__v4di)index, ! (__v4si)mask, ! scale); } #else /* __OPTIMIZE__ */ #define _mm_i32gather_pd(BASE, INDEX, SCALE) \ --- 1246,1671 ---- #ifdef __OPTIMIZE__ extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_pd (double const *__base, __m128i __index, const int __scale) { ! __v2df __zero = _mm_setzero_pd (); ! __v2df __mask = _mm_cmpeq_pd (__zero, __zero); return (__m128d) __builtin_ia32_gathersiv2df (_mm_undefined_pd (), ! __base, ! (__v4si)__index, ! __mask, ! __scale); } extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_pd (__m128d __src, double const *__base, __m128i __index, ! __m128d __mask, const int __scale) { ! return (__m128d) __builtin_ia32_gathersiv2df ((__v2df)__src, ! __base, ! (__v4si)__index, ! (__v2df)__mask, ! __scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_pd (double const *__base, __m128i __index, const int __scale) { ! __v4df __zero = _mm256_setzero_pd (); ! __v4df __mask = _mm256_cmp_pd (__zero, __zero, _CMP_EQ_OQ); return (__m256d) __builtin_ia32_gathersiv4df (_mm256_undefined_pd (), ! __base, ! (__v4si)__index, ! __mask, ! __scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_pd (__m256d __src, double const *__base, ! __m128i __index, __m256d __mask, const int __scale) { ! return (__m256d) __builtin_ia32_gathersiv4df ((__v4df)__src, ! __base, ! (__v4si)__index, ! (__v4df)__mask, ! __scale); } extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_pd (double const *__base, __m128i __index, const int __scale) { ! __v2df __src = _mm_setzero_pd (); ! __v2df __mask = _mm_cmpeq_pd (__src, __src); ! return (__m128d) __builtin_ia32_gatherdiv2df (__src, ! __base, ! (__v2di)__index, ! __mask, ! __scale); } extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_pd (__m128d __src, double const *__base, __m128i __index, ! __m128d __mask, const int __scale) { ! return (__m128d) __builtin_ia32_gatherdiv2df ((__v2df)__src, ! __base, ! (__v2di)__index, ! (__v2df)__mask, ! __scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_pd (double const *__base, __m256i __index, const int __scale) { ! __v4df __src = _mm256_setzero_pd (); ! __v4df __mask = _mm256_cmp_pd (__src, __src, _CMP_EQ_OQ); ! return (__m256d) __builtin_ia32_gatherdiv4df (__src, ! __base, ! (__v4di)__index, ! __mask, ! __scale); } extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_pd (__m256d __src, double const *__base, ! __m256i __index, __m256d __mask, const int __scale) { ! return (__m256d) __builtin_ia32_gatherdiv4df ((__v4df)__src, ! __base, ! (__v4di)__index, ! (__v4df)__mask, ! __scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_ps (float const *__base, __m128i __index, const int __scale) { ! __v4sf __src = _mm_setzero_ps (); ! __v4sf __mask = _mm_cmpeq_ps (__src, __src); ! return (__m128) __builtin_ia32_gathersiv4sf (__src, ! __base, ! (__v4si)__index, ! __mask, ! __scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_ps (__m128 __src, float const *__base, __m128i __index, ! __m128 __mask, const int __scale) { ! return (__m128) __builtin_ia32_gathersiv4sf ((__v4sf)__src, ! __base, ! (__v4si)__index, ! (__v4sf)__mask, ! __scale); } extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_ps (float const *__base, __m256i __index, const int __scale) { ! __v8sf __src = _mm256_setzero_ps (); ! __v8sf __mask = _mm256_cmp_ps (__src, __src, _CMP_EQ_OQ); ! return (__m256) __builtin_ia32_gathersiv8sf (__src, ! __base, ! (__v8si)__index, ! __mask, ! __scale); } extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_ps (__m256 __src, float const *__base, ! __m256i __index, __m256 __mask, const int __scale) { ! return (__m256) __builtin_ia32_gathersiv8sf ((__v8sf)__src, ! __base, ! (__v8si)__index, ! (__v8sf)__mask, ! __scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_ps (float const *__base, __m128i __index, const int __scale) { ! __v4sf __src = _mm_setzero_ps (); ! __v4sf __mask = _mm_cmpeq_ps (__src, __src); ! return (__m128) __builtin_ia32_gatherdiv4sf (__src, ! __base, ! (__v2di)__index, ! __mask, ! __scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_ps (__m128 __src, float const *__base, __m128i __index, ! __m128 __mask, const int __scale) { ! return (__m128) __builtin_ia32_gatherdiv4sf ((__v4sf)__src, ! __base, ! (__v2di)__index, ! (__v4sf)__mask, ! __scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_ps (float const *__base, __m256i __index, const int __scale) { ! __v4sf __src = _mm_setzero_ps (); ! __v4sf __mask = _mm_cmpeq_ps (__src, __src); ! return (__m128) __builtin_ia32_gatherdiv4sf256 (__src, ! __base, ! (__v4di)__index, ! __mask, ! __scale); } extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_ps (__m128 __src, float const *__base, ! __m256i __index, __m128 __mask, const int __scale) { ! return (__m128) __builtin_ia32_gatherdiv4sf256 ((__v4sf)__src, ! __base, ! (__v4di)__index, ! (__v4sf)__mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_epi64 (long long int const *__base, ! __m128i __index, const int __scale) { ! __v2di __src = __extension__ (__v2di){ 0, 0 }; ! __v2di __mask = __extension__ (__v2di){ ~0, ~0 }; ! return (__m128i) __builtin_ia32_gathersiv2di (__src, ! __base, ! (__v4si)__index, ! __mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_epi64 (__m128i __src, long long int const *__base, ! __m128i __index, __m128i __mask, const int __scale) { ! return (__m128i) __builtin_ia32_gathersiv2di ((__v2di)__src, ! __base, ! (__v4si)__index, ! (__v2di)__mask, ! __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_epi64 (long long int const *__base, ! __m128i __index, const int __scale) { ! __v4di __src = __extension__ (__v4di){ 0, 0, 0, 0 }; ! __v4di __mask = __extension__ (__v4di){ ~0, ~0, ~0, ~0 }; ! return (__m256i) __builtin_ia32_gathersiv4di (__src, ! __base, ! (__v4si)__index, ! __mask, ! __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_epi64 (__m256i __src, long long int const *__base, ! __m128i __index, __m256i __mask, ! const int __scale) { ! return (__m256i) __builtin_ia32_gathersiv4di ((__v4di)__src, ! __base, ! (__v4si)__index, ! (__v4di)__mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_epi64 (long long int const *__base, ! __m128i __index, const int __scale) { ! __v2di __src = __extension__ (__v2di){ 0, 0 }; ! __v2di __mask = __extension__ (__v2di){ ~0, ~0 }; ! return (__m128i) __builtin_ia32_gatherdiv2di (__src, ! __base, ! (__v2di)__index, ! __mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_epi64 (__m128i __src, long long int const *__base, ! __m128i __index, __m128i __mask, const int __scale) { ! return (__m128i) __builtin_ia32_gatherdiv2di ((__v2di)__src, ! __base, ! (__v2di)__index, ! (__v2di)__mask, ! __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_epi64 (long long int const *__base, ! __m256i __index, const int __scale) { ! __v4di __src = __extension__ (__v4di){ 0, 0, 0, 0 }; ! __v4di __mask = __extension__ (__v4di){ ~0, ~0, ~0, ~0 }; ! return (__m256i) __builtin_ia32_gatherdiv4di (__src, ! __base, ! (__v4di)__index, ! __mask, ! __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_epi64 (__m256i __src, long long int const *__base, ! __m256i __index, __m256i __mask, ! const int __scale) { ! return (__m256i) __builtin_ia32_gatherdiv4di ((__v4di)__src, ! __base, ! (__v4di)__index, ! (__v4di)__mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32gather_epi32 (int const *__base, __m128i __index, const int __scale) { ! __v4si __src = __extension__ (__v4si){ 0, 0, 0, 0 }; ! __v4si __mask = __extension__ (__v4si){ ~0, ~0, ~0, ~0 }; ! return (__m128i) __builtin_ia32_gathersiv4si (__src, ! __base, ! (__v4si)__index, ! __mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32gather_epi32 (__m128i __src, int const *__base, __m128i __index, ! __m128i __mask, const int __scale) { ! return (__m128i) __builtin_ia32_gathersiv4si ((__v4si)__src, ! __base, ! (__v4si)__index, ! (__v4si)__mask, ! __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32gather_epi32 (int const *__base, __m256i __index, const int __scale) { ! __v8si __src = __extension__ (__v8si){ 0, 0, 0, 0, 0, 0, 0, 0 }; ! __v8si __mask = __extension__ (__v8si){ ~0, ~0, ~0, ~0, ~0, ~0, ~0, ~0 }; ! return (__m256i) __builtin_ia32_gathersiv8si (__src, ! __base, ! (__v8si)__index, ! __mask, ! __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32gather_epi32 (__m256i __src, int const *__base, ! __m256i __index, __m256i __mask, ! const int __scale) { ! return (__m256i) __builtin_ia32_gathersiv8si ((__v8si)__src, ! __base, ! (__v8si)__index, ! (__v8si)__mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64gather_epi32 (int const *__base, __m128i __index, const int __scale) { ! __v4si __src = __extension__ (__v4si){ 0, 0, 0, 0 }; ! __v4si __mask = __extension__ (__v4si){ ~0, ~0, ~0, ~0 }; ! return (__m128i) __builtin_ia32_gatherdiv4si (__src, ! __base, ! (__v2di)__index, ! __mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64gather_epi32 (__m128i __src, int const *__base, __m128i __index, ! __m128i __mask, const int __scale) { ! return (__m128i) __builtin_ia32_gatherdiv4si ((__v4si)__src, ! __base, ! (__v2di)__index, ! (__v4si)__mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64gather_epi32 (int const *__base, __m256i __index, const int __scale) { ! __v4si __src = __extension__ (__v4si){ 0, 0, 0, 0 }; ! __v4si __mask = __extension__ (__v4si){ ~0, ~0, ~0, ~0 }; ! return (__m128i) __builtin_ia32_gatherdiv4si256 (__src, ! __base, ! (__v4di)__index, ! __mask, ! __scale); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64gather_epi32 (__m128i __src, int const *__base, ! __m256i __index, __m128i __mask, ! const int __scale) { ! return (__m128i) __builtin_ia32_gatherdiv4si256 ((__v4si)__src, ! __base, ! (__v4di)__index, ! (__v4si)__mask, ! __scale); } #else /* __OPTIMIZE__ */ #define _mm_i32gather_pd(BASE, INDEX, SCALE) \ diff -Nrcpad gcc-6.3.0/gcc/config/i386/avx512bwintrin.h gcc-6.4.0/gcc/config/i386/avx512bwintrin.h *** gcc-6.3.0/gcc/config/i386/avx512bwintrin.h Sun Aug 14 13:42:38 2016 --- gcc-6.4.0/gcc/config/i386/avx512bwintrin.h Fri May 5 21:38:35 2017 *************** _mm512_cmple_epi16_mask (__m512i __X, __ *** 2420,2425 **** --- 2420,2491 ---- (__mmask32) -1); } + extern __inline __m512i + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm512_packs_epi32 (__m512i __A, __m512i __B) + { + return (__m512i) __builtin_ia32_packssdw512_mask ((__v16si) __A, + (__v16si) __B, + (__v32hi) + _mm512_setzero_hi (), + (__mmask32) -1); + } + + extern __inline __m512i + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm512_maskz_packs_epi32 (__mmask32 __M, __m512i __A, __m512i __B) + { + return (__m512i) __builtin_ia32_packssdw512_mask ((__v16si) __A, + (__v16si) __B, + (__v32hi) + _mm512_setzero_hi (), + __M); + } + + extern __inline __m512i + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm512_mask_packs_epi32 (__m512i __W, __mmask32 __M, __m512i __A, + __m512i __B) + { + return (__m512i) __builtin_ia32_packssdw512_mask ((__v16si) __A, + (__v16si) __B, + (__v32hi) __W, + __M); + } + + extern __inline __m512i + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm512_packus_epi32 (__m512i __A, __m512i __B) + { + return (__m512i) __builtin_ia32_packusdw512_mask ((__v16si) __A, + (__v16si) __B, + (__v32hi) + _mm512_setzero_hi (), + (__mmask32) -1); + } + + extern __inline __m512i + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm512_maskz_packus_epi32 (__mmask32 __M, __m512i __A, __m512i __B) + { + return (__m512i) __builtin_ia32_packusdw512_mask ((__v16si) __A, + (__v16si) __B, + (__v32hi) + _mm512_setzero_hi (), + __M); + } + + extern __inline __m512i + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm512_mask_packus_epi32 (__m512i __W, __mmask32 __M, __m512i __A, + __m512i __B) + { + return (__m512i) __builtin_ia32_packusdw512_mask ((__v16si) __A, + (__v16si) __B, + (__v32hi) __W, + __M); + } + #ifdef __OPTIMIZE__ extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) *************** _mm512_cmp_epu8_mask (__m512i __X, __m51 *** 2744,2815 **** } extern __inline __m512i - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm512_packs_epi32 (__m512i __A, __m512i __B) - { - return (__m512i) __builtin_ia32_packssdw512_mask ((__v16si) __A, - (__v16si) __B, - (__v32hi) - _mm512_setzero_hi (), - (__mmask32) -1); - } - - extern __inline __m512i - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm512_maskz_packs_epi32 (__mmask32 __M, __m512i __A, __m512i __B) - { - return (__m512i) __builtin_ia32_packssdw512_mask ((__v16si) __A, - (__v16si) __B, - (__v32hi) - _mm512_setzero_hi(), - __M); - } - - extern __inline __m512i - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm512_mask_packs_epi32 (__m512i __W, __mmask32 __M, __m512i __A, - __m512i __B) - { - return (__m512i) __builtin_ia32_packssdw512_mask ((__v16si) __A, - (__v16si) __B, - (__v32hi) __W, - __M); - } - - extern __inline __m512i - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm512_packus_epi32 (__m512i __A, __m512i __B) - { - return (__m512i) __builtin_ia32_packusdw512_mask ((__v16si) __A, - (__v16si) __B, - (__v32hi) - _mm512_setzero_hi (), - (__mmask32) -1); - } - - extern __inline __m512i - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm512_maskz_packus_epi32 (__mmask32 __M, __m512i __A, __m512i __B) - { - return (__m512i) __builtin_ia32_packusdw512_mask ((__v16si) __A, - (__v16si) __B, - (__v32hi) - _mm512_setzero_hi(), - __M); - } - - extern __inline __m512i - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm512_mask_packus_epi32 (__m512i __W, __mmask32 __M, __m512i __A, - __m512i __B) - { - return (__m512i) __builtin_ia32_packusdw512_mask ((__v16si) __A, - (__v16si) __B, - (__v32hi) __W, - __M); - } - - extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_bslli_epi128 (__m512i __A, const int __N) { --- 2810,2815 ---- diff -Nrcpad gcc-6.3.0/gcc/config/i386/avx512fintrin.h gcc-6.4.0/gcc/config/i386/avx512fintrin.h *** gcc-6.3.0/gcc/config/i386/avx512fintrin.h Sun Aug 14 13:42:38 2016 --- gcc-6.4.0/gcc/config/i386/avx512fintrin.h Thu Jun 1 19:38:29 2017 *************** _mm_sub_round_ss (__m128 __A, __m128 __B *** 1438,1503 **** #ifdef __OPTIMIZE__ extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_ternarylogic_epi64 (__m512i __A, __m512i __B, __m512i __C, const int imm) { return (__m512i) __builtin_ia32_pternlogq512_mask ((__v8di) __A, (__v8di) __B, ! (__v8di) __C, imm, (__mmask8) -1); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_ternarylogic_epi64 (__m512i __A, __mmask8 __U, __m512i __B, ! __m512i __C, const int imm) { return (__m512i) __builtin_ia32_pternlogq512_mask ((__v8di) __A, (__v8di) __B, ! (__v8di) __C, imm, (__mmask8) __U); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_maskz_ternarylogic_epi64 (__mmask8 __U, __m512i __A, __m512i __B, ! __m512i __C, const int imm) { return (__m512i) __builtin_ia32_pternlogq512_maskz ((__v8di) __A, (__v8di) __B, (__v8di) __C, ! imm, (__mmask8) __U); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_ternarylogic_epi32 (__m512i __A, __m512i __B, __m512i __C, const int imm) { return (__m512i) __builtin_ia32_pternlogd512_mask ((__v16si) __A, (__v16si) __B, (__v16si) __C, ! imm, (__mmask16) -1); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_ternarylogic_epi32 (__m512i __A, __mmask16 __U, __m512i __B, ! __m512i __C, const int imm) { return (__m512i) __builtin_ia32_pternlogd512_mask ((__v16si) __A, (__v16si) __B, (__v16si) __C, ! imm, (__mmask16) __U); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_maskz_ternarylogic_epi32 (__mmask16 __U, __m512i __A, __m512i __B, ! __m512i __C, const int imm) { return (__m512i) __builtin_ia32_pternlogd512_maskz ((__v16si) __A, (__v16si) __B, (__v16si) __C, ! imm, (__mmask16) __U); } #else #define _mm512_ternarylogic_epi64(A, B, C, I) \ --- 1438,1505 ---- #ifdef __OPTIMIZE__ extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_ternarylogic_epi64 (__m512i __A, __m512i __B, __m512i __C, ! const int __imm) { return (__m512i) __builtin_ia32_pternlogq512_mask ((__v8di) __A, (__v8di) __B, ! (__v8di) __C, __imm, (__mmask8) -1); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_ternarylogic_epi64 (__m512i __A, __mmask8 __U, __m512i __B, ! __m512i __C, const int __imm) { return (__m512i) __builtin_ia32_pternlogq512_mask ((__v8di) __A, (__v8di) __B, ! (__v8di) __C, __imm, (__mmask8) __U); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_maskz_ternarylogic_epi64 (__mmask8 __U, __m512i __A, __m512i __B, ! __m512i __C, const int __imm) { return (__m512i) __builtin_ia32_pternlogq512_maskz ((__v8di) __A, (__v8di) __B, (__v8di) __C, ! __imm, (__mmask8) __U); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_ternarylogic_epi32 (__m512i __A, __m512i __B, __m512i __C, ! const int __imm) { return (__m512i) __builtin_ia32_pternlogd512_mask ((__v16si) __A, (__v16si) __B, (__v16si) __C, ! __imm, (__mmask16) -1); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_ternarylogic_epi32 (__m512i __A, __mmask16 __U, __m512i __B, ! __m512i __C, const int __imm) { return (__m512i) __builtin_ia32_pternlogd512_mask ((__v16si) __A, (__v16si) __B, (__v16si) __C, ! __imm, (__mmask16) __U); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_maskz_ternarylogic_epi32 (__mmask16 __U, __m512i __A, __m512i __B, ! __m512i __C, const int __imm) { return (__m512i) __builtin_ia32_pternlogd512_maskz ((__v16si) __A, (__v16si) __B, (__v16si) __C, ! __imm, (__mmask16) __U); } #else #define _mm512_ternarylogic_epi64(A, B, C, I) \ *************** _mm_mask_cmp_round_ss_mask (__mmask8 __M *** 9209,9231 **** #ifdef __OPTIMIZE__ extern __inline __m512 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_ps (__m512i __index, float const *__addr, int __scale) { ! __m512 v1_old = _mm512_undefined_ps (); ! __mmask16 mask = 0xFFFF; ! return (__m512) __builtin_ia32_gathersiv16sf ((__v16sf) v1_old, __addr, (__v16si) __index, ! mask, __scale); } extern __inline __m512 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32gather_ps (__m512 v1_old, __mmask16 __mask, ! __m512i __index, float const *__addr, int __scale) { ! return (__m512) __builtin_ia32_gathersiv16sf ((__v16sf) v1_old, __addr, (__v16si) __index, __mask, __scale); --- 9211,9233 ---- #ifdef __OPTIMIZE__ extern __inline __m512 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_ps (__m512i __index, void const *__addr, int __scale) { ! __m512 __v1_old = _mm512_undefined_ps (); ! __mmask16 __mask = 0xFFFF; ! return (__m512) __builtin_ia32_gathersiv16sf ((__v16sf) __v1_old, __addr, (__v16si) __index, ! __mask, __scale); } extern __inline __m512 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32gather_ps (__m512 __v1_old, __mmask16 __mask, ! __m512i __index, void const *__addr, int __scale) { ! return (__m512) __builtin_ia32_gathersiv16sf ((__v16sf) __v1_old, __addr, (__v16si) __index, __mask, __scale); *************** _mm512_mask_i32gather_ps (__m512 v1_old, *** 9233,9253 **** extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_pd (__m256i __index, double const *__addr, int __scale) { ! __m512d v1_old = _mm512_undefined_pd (); ! __mmask8 mask = 0xFF; ! return (__m512d) __builtin_ia32_gathersiv8df ((__v8df) v1_old, __addr, ! (__v8si) __index, mask, __scale); } extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i32gather_pd (__m512d __v1_old, __mmask8 __mask, ! __m256i __index, double const *__addr, int __scale) { return (__m512d) __builtin_ia32_gathersiv8df ((__v8df) __v1_old, __addr, --- 9235,9255 ---- extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_pd (__m256i __index, void const *__addr, int __scale) { ! __m512d __v1_old = _mm512_undefined_pd (); ! __mmask8 __mask = 0xFF; ! return (__m512d) __builtin_ia32_gathersiv8df ((__v8df) __v1_old, __addr, ! (__v8si) __index, __mask, __scale); } extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i32gather_pd (__m512d __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m512d) __builtin_ia32_gathersiv8df ((__v8df) __v1_old, __addr, *************** _mm512_mask_i32gather_pd (__m512d __v1_o *** 9257,9277 **** extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_ps (__m512i __index, float const *__addr, int __scale) { ! __m256 v1_old = _mm256_undefined_ps (); ! __mmask8 mask = 0xFF; ! return (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf) v1_old, __addr, ! (__v8di) __index, mask, __scale); } extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_ps (__m256 __v1_old, __mmask8 __mask, ! __m512i __index, float const *__addr, int __scale) { return (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf) __v1_old, __addr, --- 9259,9279 ---- extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_ps (__m512i __index, void const *__addr, int __scale) { ! __m256 __v1_old = _mm256_undefined_ps (); ! __mmask8 __mask = 0xFF; ! return (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf) __v1_old, __addr, ! (__v8di) __index, __mask, __scale); } extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_ps (__m256 __v1_old, __mmask8 __mask, ! __m512i __index, void const *__addr, int __scale) { return (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf) __v1_old, __addr, *************** _mm512_mask_i64gather_ps (__m256 __v1_ol *** 9281,9301 **** extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_pd (__m512i __index, double const *__addr, int __scale) { ! __m512d v1_old = _mm512_undefined_pd (); ! __mmask8 mask = 0xFF; ! return (__m512d) __builtin_ia32_gatherdiv8df ((__v8df) v1_old, __addr, ! (__v8di) __index, mask, __scale); } extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_pd (__m512d __v1_old, __mmask8 __mask, ! __m512i __index, double const *__addr, int __scale) { return (__m512d) __builtin_ia32_gatherdiv8df ((__v8df) __v1_old, __addr, --- 9283,9303 ---- extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_pd (__m512i __index, void const *__addr, int __scale) { ! __m512d __v1_old = _mm512_undefined_pd (); ! __mmask8 __mask = 0xFF; ! return (__m512d) __builtin_ia32_gatherdiv8df ((__v8df) __v1_old, __addr, ! (__v8di) __index, __mask, __scale); } extern __inline __m512d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_pd (__m512d __v1_old, __mmask8 __mask, ! __m512i __index, void const *__addr, int __scale) { return (__m512d) __builtin_ia32_gatherdiv8df ((__v8df) __v1_old, __addr, *************** _mm512_mask_i64gather_pd (__m512d __v1_o *** 9305,9325 **** extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_epi32 (__m512i __index, int const *__addr, int __scale) { ! __m512i v1_old = _mm512_undefined_epi32 (); ! __mmask16 mask = 0xFFFF; ! return (__m512i) __builtin_ia32_gathersiv16si ((__v16si) v1_old, __addr, (__v16si) __index, ! mask, __scale); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i32gather_epi32 (__m512i __v1_old, __mmask16 __mask, ! __m512i __index, int const *__addr, int __scale) { return (__m512i) __builtin_ia32_gathersiv16si ((__v16si) __v1_old, __addr, --- 9307,9327 ---- extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_epi32 (__m512i __index, void const *__addr, int __scale) { ! __m512i __v1_old = _mm512_undefined_epi32 (); ! __mmask16 __mask = 0xFFFF; ! return (__m512i) __builtin_ia32_gathersiv16si ((__v16si) __v1_old, __addr, (__v16si) __index, ! __mask, __scale); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i32gather_epi32 (__m512i __v1_old, __mmask16 __mask, ! __m512i __index, void const *__addr, int __scale) { return (__m512i) __builtin_ia32_gathersiv16si ((__v16si) __v1_old, __addr, *************** _mm512_mask_i32gather_epi32 (__m512i __v *** 9329,9349 **** extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_epi64 (__m256i __index, long long const *__addr, int __scale) { ! __m512i v1_old = _mm512_undefined_epi32 (); ! __mmask8 mask = 0xFF; ! return (__m512i) __builtin_ia32_gathersiv8di ((__v8di) v1_old, __addr, ! (__v8si) __index, mask, __scale); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i32gather_epi64 (__m512i __v1_old, __mmask8 __mask, ! __m256i __index, long long const *__addr, int __scale) { return (__m512i) __builtin_ia32_gathersiv8di ((__v8di) __v1_old, --- 9331,9351 ---- extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32gather_epi64 (__m256i __index, void const *__addr, int __scale) { ! __m512i __v1_old = _mm512_undefined_epi32 (); ! __mmask8 __mask = 0xFF; ! return (__m512i) __builtin_ia32_gathersiv8di ((__v8di) __v1_old, __addr, ! (__v8si) __index, __mask, __scale); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i32gather_epi64 (__m512i __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m512i) __builtin_ia32_gathersiv8di ((__v8di) __v1_old, *************** _mm512_mask_i32gather_epi64 (__m512i __v *** 9354,9374 **** extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_epi32 (__m512i __index, int const *__addr, int __scale) { ! __m256i v1_old = _mm256_undefined_si256 (); ! __mmask8 mask = 0xFF; ! return (__m256i) __builtin_ia32_gatherdiv16si ((__v8si) v1_old, __addr, (__v8di) __index, ! mask, __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_epi32 (__m256i __v1_old, __mmask8 __mask, ! __m512i __index, int const *__addr, int __scale) { return (__m256i) __builtin_ia32_gatherdiv16si ((__v8si) __v1_old, __addr, --- 9356,9376 ---- extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_epi32 (__m512i __index, void const *__addr, int __scale) { ! __m256i __v1_old = _mm256_undefined_si256 (); ! __mmask8 __mask = 0xFF; ! return (__m256i) __builtin_ia32_gatherdiv16si ((__v8si) __v1_old, __addr, (__v8di) __index, ! __mask, __scale); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_epi32 (__m256i __v1_old, __mmask8 __mask, ! __m512i __index, void const *__addr, int __scale) { return (__m256i) __builtin_ia32_gatherdiv16si ((__v8si) __v1_old, __addr, *************** _mm512_mask_i64gather_epi32 (__m256i __v *** 9378,9398 **** extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_epi64 (__m512i __index, long long const *__addr, int __scale) { ! __m512i v1_old = _mm512_undefined_epi32 (); ! __mmask8 mask = 0xFF; ! return (__m512i) __builtin_ia32_gatherdiv8di ((__v8di) v1_old, __addr, ! (__v8di) __index, mask, __scale); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_epi64 (__m512i __v1_old, __mmask8 __mask, ! __m512i __index, long long const *__addr, int __scale) { return (__m512i) __builtin_ia32_gatherdiv8di ((__v8di) __v1_old, --- 9380,9400 ---- extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64gather_epi64 (__m512i __index, void const *__addr, int __scale) { ! __m512i __v1_old = _mm512_undefined_epi32 (); ! __mmask8 __mask = 0xFF; ! return (__m512i) __builtin_ia32_gatherdiv8di ((__v8di) __v1_old, __addr, ! (__v8di) __index, __mask, __scale); } extern __inline __m512i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm512_mask_i64gather_epi64 (__m512i __v1_old, __mmask8 __mask, ! __m512i __index, void const *__addr, int __scale) { return (__m512i) __builtin_ia32_gatherdiv8di ((__v8di) __v1_old, *************** _mm512_mask_i64gather_epi64 (__m512i __v *** 9403,9409 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_ps (float *__addr, __m512i __index, __m512 __v1, int __scale) { __builtin_ia32_scattersiv16sf (__addr, (__mmask16) 0xFFFF, (__v16si) __index, (__v16sf) __v1, __scale); --- 9405,9411 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_ps (void *__addr, __m512i __index, __m512 __v1, int __scale) { __builtin_ia32_scattersiv16sf (__addr, (__mmask16) 0xFFFF, (__v16si) __index, (__v16sf) __v1, __scale); *************** _mm512_i32scatter_ps (float *__addr, __m *** 9411,9417 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_ps (float *__addr, __mmask16 __mask, __m512i __index, __m512 __v1, int __scale) { __builtin_ia32_scattersiv16sf (__addr, __mask, (__v16si) __index, --- 9413,9419 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_ps (void *__addr, __mmask16 __mask, __m512i __index, __m512 __v1, int __scale) { __builtin_ia32_scattersiv16sf (__addr, __mask, (__v16si) __index, *************** _mm512_mask_i32scatter_ps (float *__addr *** 9420,9426 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_pd (double *__addr, __m256i __index, __m512d __v1, int __scale) { __builtin_ia32_scattersiv8df (__addr, (__mmask8) 0xFF, --- 9422,9428 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_pd (void *__addr, __m256i __index, __m512d __v1, int __scale) { __builtin_ia32_scattersiv8df (__addr, (__mmask8) 0xFF, *************** _mm512_i32scatter_pd (double *__addr, __ *** 9429,9435 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_pd (double *__addr, __mmask8 __mask, __m256i __index, __m512d __v1, int __scale) { __builtin_ia32_scattersiv8df (__addr, __mask, (__v8si) __index, --- 9431,9437 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_pd (void *__addr, __mmask8 __mask, __m256i __index, __m512d __v1, int __scale) { __builtin_ia32_scattersiv8df (__addr, __mask, (__v8si) __index, *************** _mm512_mask_i32scatter_pd (double *__add *** 9438,9444 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_ps (float *__addr, __m512i __index, __m256 __v1, int __scale) { __builtin_ia32_scatterdiv16sf (__addr, (__mmask8) 0xFF, (__v8di) __index, (__v8sf) __v1, __scale); --- 9440,9446 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_ps (void *__addr, __m512i __index, __m256 __v1, int __scale) { __builtin_ia32_scatterdiv16sf (__addr, (__mmask8) 0xFF, (__v8di) __index, (__v8sf) __v1, __scale); *************** _mm512_i64scatter_ps (float *__addr, __m *** 9446,9452 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_ps (float *__addr, __mmask8 __mask, __m512i __index, __m256 __v1, int __scale) { __builtin_ia32_scatterdiv16sf (__addr, __mask, (__v8di) __index, --- 9448,9454 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_ps (void *__addr, __mmask8 __mask, __m512i __index, __m256 __v1, int __scale) { __builtin_ia32_scatterdiv16sf (__addr, __mask, (__v8di) __index, *************** _mm512_mask_i64scatter_ps (float *__addr *** 9455,9461 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_pd (double *__addr, __m512i __index, __m512d __v1, int __scale) { __builtin_ia32_scatterdiv8df (__addr, (__mmask8) 0xFF, --- 9457,9463 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_pd (void *__addr, __m512i __index, __m512d __v1, int __scale) { __builtin_ia32_scatterdiv8df (__addr, (__mmask8) 0xFF, *************** _mm512_i64scatter_pd (double *__addr, __ *** 9464,9470 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_pd (double *__addr, __mmask8 __mask, __m512i __index, __m512d __v1, int __scale) { __builtin_ia32_scatterdiv8df (__addr, __mask, (__v8di) __index, --- 9466,9472 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_pd (void *__addr, __mmask8 __mask, __m512i __index, __m512d __v1, int __scale) { __builtin_ia32_scatterdiv8df (__addr, __mask, (__v8di) __index, *************** _mm512_mask_i64scatter_pd (double *__add *** 9473,9479 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_epi32 (int *__addr, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv16si (__addr, (__mmask16) 0xFFFF, --- 9475,9481 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_epi32 (void *__addr, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv16si (__addr, (__mmask16) 0xFFFF, *************** _mm512_i32scatter_epi32 (int *__addr, __ *** 9482,9488 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_epi32 (int *__addr, __mmask16 __mask, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv16si (__addr, __mask, (__v16si) __index, --- 9484,9490 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_epi32 (void *__addr, __mmask16 __mask, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv16si (__addr, __mask, (__v16si) __index, *************** _mm512_mask_i32scatter_epi32 (int *__add *** 9491,9497 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_epi64 (long long *__addr, __m256i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv8di (__addr, (__mmask8) 0xFF, --- 9493,9499 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i32scatter_epi64 (void *__addr, __m256i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv8di (__addr, (__mmask8) 0xFF, *************** _mm512_i32scatter_epi64 (long long *__ad *** 9500,9506 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_epi64 (long long *__addr, __mmask8 __mask, __m256i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv8di (__addr, __mask, (__v8si) __index, --- 9502,9508 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i32scatter_epi64 (void *__addr, __mmask8 __mask, __m256i __index, __m512i __v1, int __scale) { __builtin_ia32_scattersiv8di (__addr, __mask, (__v8si) __index, *************** _mm512_mask_i32scatter_epi64 (long long *** 9509,9515 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_epi32 (int *__addr, __m512i __index, __m256i __v1, int __scale) { __builtin_ia32_scatterdiv16si (__addr, (__mmask8) 0xFF, --- 9511,9517 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_epi32 (void *__addr, __m512i __index, __m256i __v1, int __scale) { __builtin_ia32_scatterdiv16si (__addr, (__mmask8) 0xFF, *************** _mm512_i64scatter_epi32 (int *__addr, __ *** 9518,9524 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_epi32 (int *__addr, __mmask8 __mask, __m512i __index, __m256i __v1, int __scale) { __builtin_ia32_scatterdiv16si (__addr, __mask, (__v8di) __index, --- 9520,9526 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_epi32 (void *__addr, __mmask8 __mask, __m512i __index, __m256i __v1, int __scale) { __builtin_ia32_scatterdiv16si (__addr, __mask, (__v8di) __index, *************** _mm512_mask_i64scatter_epi32 (int *__add *** 9527,9533 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_epi64 (long long *__addr, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scatterdiv8di (__addr, (__mmask8) 0xFF, --- 9529,9535 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_i64scatter_epi64 (void *__addr, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scatterdiv8di (__addr, (__mmask8) 0xFF, *************** _mm512_i64scatter_epi64 (long long *__ad *** 9536,9542 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_epi64 (long long *__addr, __mmask8 __mask, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scatterdiv8di (__addr, __mask, (__v8di) __index, --- 9538,9544 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_i64scatter_epi64 (void *__addr, __mmask8 __mask, __m512i __index, __m512i __v1, int __scale) { __builtin_ia32_scatterdiv8di (__addr, __mask, (__v8di) __index, *************** _mm512_mask_i64scatter_epi64 (long long *** 9545,9721 **** #else #define _mm512_i32gather_ps(INDEX, ADDR, SCALE) \ (__m512) __builtin_ia32_gathersiv16sf ((__v16sf)_mm512_undefined_ps(),\ ! (float const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)0xFFFF, (int)SCALE) #define _mm512_mask_i32gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512) __builtin_ia32_gathersiv16sf ((__v16sf)(__m512)V1OLD, \ ! (float const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)MASK, (int)SCALE) #define _mm512_i32gather_pd(INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gathersiv8df ((__v8df)_mm512_undefined_pd(), \ ! (double const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i32gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gathersiv8df ((__v8df)(__m512d)V1OLD, \ ! (double const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_ps(INDEX, ADDR, SCALE) \ (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf)_mm256_undefined_ps(), \ ! (float const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf)(__m256)V1OLD, \ ! (float const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_pd(INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gatherdiv8df ((__v8df)_mm512_undefined_pd(), \ ! (double const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gatherdiv8df ((__v8df)(__m512d)V1OLD, \ ! (double const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i32gather_epi32(INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv16si ((__v16si)_mm512_undefined_epi32 (), \ ! (int const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)0xFFFF, (int)SCALE) #define _mm512_mask_i32gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv16si ((__v16si)(__m512i)V1OLD, \ ! (int const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)MASK, (int)SCALE) #define _mm512_i32gather_epi64(INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv8di ((__v8di)_mm512_undefined_epi32 (), \ ! (long long const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i32gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv8di ((__v8di)(__m512i)V1OLD, \ ! (long long const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_epi32(INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gatherdiv16si ((__v8si)_mm256_undefined_si256(), \ ! (int const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gatherdiv16si ((__v8si)(__m256i)V1OLD, \ ! (int const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_epi64(INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gatherdiv8di ((__v8di)_mm512_undefined_epi32 (), \ ! (long long const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gatherdiv8di ((__v8di)(__m512i)V1OLD, \ ! (long long const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i32scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16sf ((float *)ADDR, (__mmask16)0xFFFF, \ (__v16si)(__m512i)INDEX, \ (__v16sf)(__m512)V1, (int)SCALE) #define _mm512_mask_i32scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16sf ((float *)ADDR, (__mmask16)MASK, \ (__v16si)(__m512i)INDEX, \ (__v16sf)(__m512)V1, (int)SCALE) #define _mm512_i32scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8df ((double *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_mask_i32scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8df ((double *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_i64scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16sf ((float *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm512_mask_i64scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16sf ((float *)ADDR, (__mmask16)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm512_i64scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8df ((double *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_mask_i64scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8df ((double *)ADDR, (__mmask8)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_i32scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16si ((int *)ADDR, (__mmask16)0xFFFF, \ (__v16si)(__m512i)INDEX, \ (__v16si)(__m512i)V1, (int)SCALE) #define _mm512_mask_i32scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16si ((int *)ADDR, (__mmask16)MASK, \ (__v16si)(__m512i)INDEX, \ (__v16si)(__m512i)V1, (int)SCALE) #define _mm512_i32scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8di ((long long *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #define _mm512_mask_i32scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8di ((long long *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #define _mm512_i64scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16si ((int *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm512_mask_i64scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16si ((int *)ADDR, (__mmask8)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm512_i64scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8di ((long long *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #define _mm512_mask_i64scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8di ((long long *)ADDR, (__mmask8)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #endif --- 9547,9723 ---- #else #define _mm512_i32gather_ps(INDEX, ADDR, SCALE) \ (__m512) __builtin_ia32_gathersiv16sf ((__v16sf)_mm512_undefined_ps(),\ ! (void const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)0xFFFF, (int)SCALE) #define _mm512_mask_i32gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512) __builtin_ia32_gathersiv16sf ((__v16sf)(__m512)V1OLD, \ ! (void const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)MASK, (int)SCALE) #define _mm512_i32gather_pd(INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gathersiv8df ((__v8df)_mm512_undefined_pd(), \ ! (void const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i32gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gathersiv8df ((__v8df)(__m512d)V1OLD, \ ! (void const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_ps(INDEX, ADDR, SCALE) \ (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf)_mm256_undefined_ps(), \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256) __builtin_ia32_gatherdiv16sf ((__v8sf)(__m256)V1OLD, \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_pd(INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gatherdiv8df ((__v8df)_mm512_undefined_pd(), \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512d) __builtin_ia32_gatherdiv8df ((__v8df)(__m512d)V1OLD, \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i32gather_epi32(INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv16si ((__v16si)_mm512_undefined_epi32 (), \ ! (void const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)0xFFFF, (int)SCALE) #define _mm512_mask_i32gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv16si ((__v16si)(__m512i)V1OLD, \ ! (void const *)ADDR, \ (__v16si)(__m512i)INDEX, \ (__mmask16)MASK, (int)SCALE) #define _mm512_i32gather_epi64(INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv8di ((__v8di)_mm512_undefined_epi32 (), \ ! (void const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i32gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gathersiv8di ((__v8di)(__m512i)V1OLD, \ ! (void const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_epi32(INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gatherdiv16si ((__v8si)_mm256_undefined_si256(), \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gatherdiv16si ((__v8si)(__m256i)V1OLD, \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i64gather_epi64(INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gatherdiv8di ((__v8di)_mm512_undefined_epi32 (), \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)0xFF, (int)SCALE) #define _mm512_mask_i64gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m512i) __builtin_ia32_gatherdiv8di ((__v8di)(__m512i)V1OLD, \ ! (void const *)ADDR, \ (__v8di)(__m512i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm512_i32scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16sf ((void *)ADDR, (__mmask16)0xFFFF, \ (__v16si)(__m512i)INDEX, \ (__v16sf)(__m512)V1, (int)SCALE) #define _mm512_mask_i32scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16sf ((void *)ADDR, (__mmask16)MASK, \ (__v16si)(__m512i)INDEX, \ (__v16sf)(__m512)V1, (int)SCALE) #define _mm512_i32scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8df ((void *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_mask_i32scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8df ((void *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_i64scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16sf ((void *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm512_mask_i64scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16sf ((void *)ADDR, (__mmask16)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm512_i64scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8df ((void *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_mask_i64scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8df ((void *)ADDR, (__mmask8)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8df)(__m512d)V1, (int)SCALE) #define _mm512_i32scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16si ((void *)ADDR, (__mmask16)0xFFFF, \ (__v16si)(__m512i)INDEX, \ (__v16si)(__m512i)V1, (int)SCALE) #define _mm512_mask_i32scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv16si ((void *)ADDR, (__mmask16)MASK, \ (__v16si)(__m512i)INDEX, \ (__v16si)(__m512i)V1, (int)SCALE) #define _mm512_i32scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8di ((void *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #define _mm512_mask_i32scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8di ((void *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #define _mm512_i64scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16si ((void *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm512_mask_i64scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv16si ((void *)ADDR, (__mmask8)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm512_i64scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8di ((void *)ADDR, (__mmask8)0xFF, \ (__v8di)(__m512i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #define _mm512_mask_i64scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8di ((void *)ADDR, (__mmask8)MASK, \ (__v8di)(__m512i)INDEX, \ (__v8di)(__m512i)V1, (int)SCALE) #endif diff -Nrcpad gcc-6.3.0/gcc/config/i386/avx512pfintrin.h gcc-6.4.0/gcc/config/i386/avx512pfintrin.h *** gcc-6.3.0/gcc/config/i386/avx512pfintrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/avx512pfintrin.h Thu Jun 1 19:38:29 2017 *************** typedef unsigned short __mmask16; *** 48,207 **** #ifdef __OPTIMIZE__ extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32gather_pd (__m256i index, __mmask8 mask, ! void *addr, int scale, int hint) { ! __builtin_ia32_gatherpfdpd (mask, (__v8si) index, (long long const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32gather_ps (__m512i index, __mmask16 mask, ! void *addr, int scale, int hint) { ! __builtin_ia32_gatherpfdps (mask, (__v16si) index, (int const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64gather_pd (__m512i index, __mmask8 mask, ! void *addr, int scale, int hint) { ! __builtin_ia32_gatherpfqpd (mask, (__v8di) index, (long long const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64gather_ps (__m512i index, __mmask8 mask, ! void *addr, int scale, int hint) { ! __builtin_ia32_gatherpfqps (mask, (__v8di) index, (int const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i32scatter_pd (void *addr, __m256i index, int scale, ! int hint) { ! __builtin_ia32_scatterpfdpd ((__mmask8) 0xFF, (__v8si) index, ! (long long const *)addr, scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i32scatter_ps (void *addr, __m512i index, int scale, ! int hint) { ! __builtin_ia32_scatterpfdps ((__mmask16) 0xFFFF, (__v16si) index, (int const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32scatter_pd (void *addr, __mmask8 mask, ! __m256i index, int scale, int hint) { ! __builtin_ia32_scatterpfdpd (mask, (__v8si) index, (long long const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32scatter_ps (void *addr, __mmask16 mask, ! __m512i index, int scale, int hint) { ! __builtin_ia32_scatterpfdps (mask, (__v16si) index, (int const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i64scatter_pd (void *addr, __m512i index, int scale, ! int hint) { ! __builtin_ia32_scatterpfqpd ((__mmask8) 0xFF, (__v8di) index, (long long const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i64scatter_ps (void *addr, __m512i index, int scale, ! int hint) { ! __builtin_ia32_scatterpfqps ((__mmask8) 0xFF, (__v8di) index, (int const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64scatter_pd (void *addr, __mmask16 mask, ! __m512i index, int scale, int hint) { ! __builtin_ia32_scatterpfqpd (mask, (__v8di) index, (long long const *) addr, ! scale, hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64scatter_ps (void *addr, __mmask16 mask, ! __m512i index, int scale, int hint) { ! __builtin_ia32_scatterpfqps (mask, (__v8di) index, (int const *) addr, ! scale, hint); } #else #define _mm512_mask_prefetch_i32gather_pd(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfdpd ((__mmask8)MASK, (__v8si)(__m256i)INDEX, \ ! (long long const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i32gather_ps(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfdps ((__mmask16)MASK, (__v16si)(__m512i)INDEX, \ ! (int const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64gather_pd(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfqpd ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (long long const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64gather_ps(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfqps ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (int const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i32scatter_pd(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdpd ((__mmask8)0xFF, (__v8si)(__m256i)INDEX, \ ! (long long const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i32scatter_ps(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdps ((__mmask16)0xFFFF, (__v16si)(__m512i)INDEX, \ ! (int const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i32scatter_pd(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdpd ((__mmask8)MASK, (__v8si)(__m256i)INDEX, \ ! (long long const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i32scatter_ps(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdps ((__mmask16)MASK, (__v16si)(__m512i)INDEX, \ ! (int const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i64scatter_pd(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqpd ((__mmask8)0xFF, (__v8di)(__m512i)INDEX, \ ! (long long const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i64scatter_ps(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqps ((__mmask8)0xFF, (__v8di)(__m512i)INDEX, \ ! (int const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64scatter_pd(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqpd ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (long long const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64scatter_ps(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqps ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (int const *)ADDR, (int)SCALE, (int)HINT) #endif #ifdef __DISABLE_AVX512PF__ --- 48,207 ---- #ifdef __OPTIMIZE__ extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32gather_pd (__m256i __index, __mmask8 __mask, ! void const *__addr, int __scale, int __hint) { ! __builtin_ia32_gatherpfdpd (__mask, (__v8si) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32gather_ps (__m512i __index, __mmask16 __mask, ! void const *__addr, int __scale, int __hint) { ! __builtin_ia32_gatherpfdps (__mask, (__v16si) __index, __addr, ! __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64gather_pd (__m512i __index, __mmask8 __mask, ! void const *__addr, int __scale, int __hint) { ! __builtin_ia32_gatherpfqpd (__mask, (__v8di) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64gather_ps (__m512i __index, __mmask8 __mask, ! void const *__addr, int __scale, int __hint) { ! __builtin_ia32_gatherpfqps (__mask, (__v8di) __index, __addr, ! __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i32scatter_pd (void *__addr, __m256i __index, int __scale, ! int __hint) { ! __builtin_ia32_scatterpfdpd ((__mmask8) 0xFF, (__v8si) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i32scatter_ps (void *__addr, __m512i __index, int __scale, ! int __hint) { ! __builtin_ia32_scatterpfdps ((__mmask16) 0xFFFF, (__v16si) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32scatter_pd (void *__addr, __mmask8 __mask, ! __m256i __index, int __scale, int __hint) { ! __builtin_ia32_scatterpfdpd (__mask, (__v8si) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i32scatter_ps (void *__addr, __mmask16 __mask, ! __m512i __index, int __scale, int __hint) { ! __builtin_ia32_scatterpfdps (__mask, (__v16si) __index, __addr, ! __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i64scatter_pd (void *__addr, __m512i __index, int __scale, ! int __hint) { ! __builtin_ia32_scatterpfqpd ((__mmask8) 0xFF, (__v8di) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_prefetch_i64scatter_ps (void *__addr, __m512i __index, int __scale, ! int __hint) { ! __builtin_ia32_scatterpfqps ((__mmask8) 0xFF, (__v8di) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64scatter_pd (void *__addr, __mmask16 __mask, ! __m512i __index, int __scale, int __hint) { ! __builtin_ia32_scatterpfqpd (__mask, (__v8di) __index, ! __addr, __scale, __hint); } extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm512_mask_prefetch_i64scatter_ps (void *__addr, __mmask16 __mask, ! __m512i __index, int __scale, int __hint) { ! __builtin_ia32_scatterpfqps (__mask, (__v8di) __index, __addr, ! __scale, __hint); } #else #define _mm512_mask_prefetch_i32gather_pd(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfdpd ((__mmask8)MASK, (__v8si)(__m256i)INDEX, \ ! (void const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i32gather_ps(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfdps ((__mmask16)MASK, (__v16si)(__m512i)INDEX, \ ! (void const *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64gather_pd(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfqpd ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64gather_ps(INDEX, MASK, ADDR, SCALE, HINT) \ __builtin_ia32_gatherpfqps ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i32scatter_pd(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdpd ((__mmask8)0xFF, (__v8si)(__m256i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i32scatter_ps(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdps ((__mmask16)0xFFFF, (__v16si)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i32scatter_pd(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdpd ((__mmask8)MASK, (__v8si)(__m256i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i32scatter_ps(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfdps ((__mmask16)MASK, (__v16si)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i64scatter_pd(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqpd ((__mmask8)0xFF, (__v8di)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_prefetch_i64scatter_ps(ADDR, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqps ((__mmask8)0xFF, (__v8di)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64scatter_pd(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqpd ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #define _mm512_mask_prefetch_i64scatter_ps(ADDR, MASK, INDEX, SCALE, HINT) \ __builtin_ia32_scatterpfqps ((__mmask8)MASK, (__v8di)(__m512i)INDEX, \ ! (void *)ADDR, (int)SCALE, (int)HINT) #endif #ifdef __DISABLE_AVX512PF__ diff -Nrcpad gcc-6.3.0/gcc/config/i386/avx512vlintrin.h gcc-6.4.0/gcc/config/i386/avx512vlintrin.h *** gcc-6.3.0/gcc/config/i386/avx512vlintrin.h Sun Aug 14 13:42:38 2016 --- gcc-6.4.0/gcc/config/i386/avx512vlintrin.h Thu Jun 1 19:38:29 2017 *************** _mm256_mask_permutexvar_epi32 (__m256i _ *** 9159,9164 **** --- 9159,9740 ---- __M); } + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpneq_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpneq_epu32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmplt_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmplt_epu32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpge_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpge_epu32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmple_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmple_epu32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, + (__v8si) __Y, 2, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpneq_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpneq_epu64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmplt_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmplt_epu64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpge_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpge_epu64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmple_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmple_epu64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, + (__v4di) __Y, 2, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpneq_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpneq_epi32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmplt_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmplt_epi32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpge_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpge_epi32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmple_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmple_epi32_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, + (__v8si) __Y, 2, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpneq_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpneq_epi64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmplt_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmplt_epi64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmpge_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmpge_epi64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_mask_cmple_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm256_cmple_epi64_mask (__m256i __X, __m256i __Y) + { + return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, + (__v4di) __Y, 2, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpneq_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpneq_epu32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmplt_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmplt_epu32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpge_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpge_epu32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmple_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmple_epu32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, + (__v4si) __Y, 2, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpneq_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpneq_epu64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmplt_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmplt_epu64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpge_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpge_epu64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmple_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmple_epu64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, + (__v2di) __Y, 2, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpneq_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpneq_epi32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmplt_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmplt_epi32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpge_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpge_epi32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmple_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmple_epi32_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, + (__v4si) __Y, 2, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpneq_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 4, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpneq_epi64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 4, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmplt_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 1, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmplt_epi64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 1, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmpge_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 5, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmpge_epi64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 5, + (__mmask8) -1); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_mask_cmple_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 2, + (__mmask8) __M); + } + + extern __inline __mmask8 + __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) + _mm_cmple_epi64_mask (__m128i __X, __m128i __Y) + { + return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, + (__v2di) __Y, 2, + (__mmask8) -1); + } + #ifdef __OPTIMIZE__ extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) *************** _mm_maskz_srli_epi64 (__mmask8 __U, __m1 *** 9796,9806 **** extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_ternarylogic_epi64 (__m256i __A, __m256i __B, __m256i __C, ! const int imm) { return (__m256i) __builtin_ia32_pternlogq256_mask ((__v4di) __A, (__v4di) __B, ! (__v4di) __C, imm, (__mmask8) -1); } --- 10372,10382 ---- extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_ternarylogic_epi64 (__m256i __A, __m256i __B, __m256i __C, ! const int __imm) { return (__m256i) __builtin_ia32_pternlogq256_mask ((__v4di) __A, (__v4di) __B, ! (__v4di) __C, __imm, (__mmask8) -1); } *************** extern __inline __m256i *** 9808,9818 **** __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mask_ternarylogic_epi64 (__m256i __A, __mmask8 __U, __m256i __B, __m256i __C, ! const int imm) { return (__m256i) __builtin_ia32_pternlogq256_mask ((__v4di) __A, (__v4di) __B, ! (__v4di) __C, imm, (__mmask8) __U); } --- 10384,10394 ---- __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mask_ternarylogic_epi64 (__m256i __A, __mmask8 __U, __m256i __B, __m256i __C, ! const int __imm) { return (__m256i) __builtin_ia32_pternlogq256_mask ((__v4di) __A, (__v4di) __B, ! (__v4di) __C, __imm, (__mmask8) __U); } *************** extern __inline __m256i *** 9820,9842 **** __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_maskz_ternarylogic_epi64 (__mmask8 __U, __m256i __A, __m256i __B, __m256i __C, ! const int imm) { return (__m256i) __builtin_ia32_pternlogq256_maskz ((__v4di) __A, (__v4di) __B, (__v4di) __C, ! imm, (__mmask8) __U); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_ternarylogic_epi32 (__m256i __A, __m256i __B, __m256i __C, ! const int imm) { return (__m256i) __builtin_ia32_pternlogd256_mask ((__v8si) __A, (__v8si) __B, ! (__v8si) __C, imm, (__mmask8) -1); } --- 10396,10418 ---- __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_maskz_ternarylogic_epi64 (__mmask8 __U, __m256i __A, __m256i __B, __m256i __C, ! const int __imm) { return (__m256i) __builtin_ia32_pternlogq256_maskz ((__v4di) __A, (__v4di) __B, (__v4di) __C, ! __imm, (__mmask8) __U); } extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_ternarylogic_epi32 (__m256i __A, __m256i __B, __m256i __C, ! const int __imm) { return (__m256i) __builtin_ia32_pternlogd256_mask ((__v8si) __A, (__v8si) __B, ! (__v8si) __C, __imm, (__mmask8) -1); } *************** extern __inline __m256i *** 9844,9854 **** __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mask_ternarylogic_epi32 (__m256i __A, __mmask8 __U, __m256i __B, __m256i __C, ! const int imm) { return (__m256i) __builtin_ia32_pternlogd256_mask ((__v8si) __A, (__v8si) __B, ! (__v8si) __C, imm, (__mmask8) __U); } --- 10420,10430 ---- __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mask_ternarylogic_epi32 (__m256i __A, __mmask8 __U, __m256i __B, __m256i __C, ! const int __imm) { return (__m256i) __builtin_ia32_pternlogd256_mask ((__v8si) __A, (__v8si) __B, ! (__v8si) __C, __imm, (__mmask8) __U); } *************** extern __inline __m256i *** 9856,9935 **** __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_maskz_ternarylogic_epi32 (__mmask8 __U, __m256i __A, __m256i __B, __m256i __C, ! const int imm) { return (__m256i) __builtin_ia32_pternlogd256_maskz ((__v8si) __A, (__v8si) __B, (__v8si) __C, ! imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_ternarylogic_epi64 (__m128i __A, __m128i __B, __m128i __C, ! const int imm) { return (__m128i) __builtin_ia32_pternlogq128_mask ((__v2di) __A, (__v2di) __B, ! (__v2di) __C, imm, (__mmask8) -1); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mask_ternarylogic_epi64 (__m128i __A, __mmask8 __U, ! __m128i __B, __m128i __C, const int imm) { return (__m128i) __builtin_ia32_pternlogq128_mask ((__v2di) __A, (__v2di) __B, ! (__v2di) __C, imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_maskz_ternarylogic_epi64 (__mmask8 __U, __m128i __A, ! __m128i __B, __m128i __C, const int imm) { return (__m128i) __builtin_ia32_pternlogq128_maskz ((__v2di) __A, (__v2di) __B, (__v2di) __C, ! imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_ternarylogic_epi32 (__m128i __A, __m128i __B, __m128i __C, ! const int imm) { return (__m128i) __builtin_ia32_pternlogd128_mask ((__v4si) __A, (__v4si) __B, ! (__v4si) __C, imm, (__mmask8) -1); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mask_ternarylogic_epi32 (__m128i __A, __mmask8 __U, ! __m128i __B, __m128i __C, const int imm) { return (__m128i) __builtin_ia32_pternlogd128_mask ((__v4si) __A, (__v4si) __B, ! (__v4si) __C, imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_maskz_ternarylogic_epi32 (__mmask8 __U, __m128i __A, ! __m128i __B, __m128i __C, const int imm) { return (__m128i) __builtin_ia32_pternlogd128_maskz ((__v4si) __A, (__v4si) __B, (__v4si) __C, ! imm, (__mmask8) __U); } --- 10432,10511 ---- __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_maskz_ternarylogic_epi32 (__mmask8 __U, __m256i __A, __m256i __B, __m256i __C, ! const int __imm) { return (__m256i) __builtin_ia32_pternlogd256_maskz ((__v8si) __A, (__v8si) __B, (__v8si) __C, ! __imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_ternarylogic_epi64 (__m128i __A, __m128i __B, __m128i __C, ! const int __imm) { return (__m128i) __builtin_ia32_pternlogq128_mask ((__v2di) __A, (__v2di) __B, ! (__v2di) __C, __imm, (__mmask8) -1); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mask_ternarylogic_epi64 (__m128i __A, __mmask8 __U, ! __m128i __B, __m128i __C, const int __imm) { return (__m128i) __builtin_ia32_pternlogq128_mask ((__v2di) __A, (__v2di) __B, ! (__v2di) __C, __imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_maskz_ternarylogic_epi64 (__mmask8 __U, __m128i __A, ! __m128i __B, __m128i __C, const int __imm) { return (__m128i) __builtin_ia32_pternlogq128_maskz ((__v2di) __A, (__v2di) __B, (__v2di) __C, ! __imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_ternarylogic_epi32 (__m128i __A, __m128i __B, __m128i __C, ! const int __imm) { return (__m128i) __builtin_ia32_pternlogd128_mask ((__v4si) __A, (__v4si) __B, ! (__v4si) __C, __imm, (__mmask8) -1); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mask_ternarylogic_epi32 (__m128i __A, __mmask8 __U, ! __m128i __B, __m128i __C, const int __imm) { return (__m128i) __builtin_ia32_pternlogd128_mask ((__v4si) __A, (__v4si) __B, ! (__v4si) __C, __imm, (__mmask8) __U); } extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_maskz_ternarylogic_epi32 (__mmask8 __U, __m128i __A, ! __m128i __B, __m128i __C, const int __imm) { return (__m128i) __builtin_ia32_pternlogd128_maskz ((__v4si) __A, (__v4si) __B, (__v4si) __C, ! __imm, (__mmask8) __U); } *************** _mm_maskz_getmant_pd (__mmask8 __U, __m1 *** 10216,10222 **** extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_ps (__m256 __v1_old, __mmask8 __mask, ! __m256i __index, float const *__addr, int __scale) { return (__m256) __builtin_ia32_gather3siv8sf ((__v8sf) __v1_old, --- 10792,10798 ---- extern __inline __m256 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_ps (__m256 __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m256) __builtin_ia32_gather3siv8sf ((__v8sf) __v1_old, *************** _mm256_mmask_i32gather_ps (__m256 __v1_o *** 10228,10234 **** extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_ps (__m128 __v1_old, __mmask8 __mask, ! __m128i __index, float const *__addr, int __scale) { return (__m128) __builtin_ia32_gather3siv4sf ((__v4sf) __v1_old, --- 10804,10810 ---- extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_ps (__m128 __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128) __builtin_ia32_gather3siv4sf ((__v4sf) __v1_old, *************** _mm_mmask_i32gather_ps (__m128 __v1_old, *** 10240,10246 **** extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_pd (__m256d __v1_old, __mmask8 __mask, ! __m128i __index, double const *__addr, int __scale) { return (__m256d) __builtin_ia32_gather3siv4df ((__v4df) __v1_old, --- 10816,10822 ---- extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_pd (__m256d __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m256d) __builtin_ia32_gather3siv4df ((__v4df) __v1_old, *************** _mm256_mmask_i32gather_pd (__m256d __v1_ *** 10252,10258 **** extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_pd (__m128d __v1_old, __mmask8 __mask, ! __m128i __index, double const *__addr, int __scale) { return (__m128d) __builtin_ia32_gather3siv2df ((__v2df) __v1_old, --- 10828,10834 ---- extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_pd (__m128d __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128d) __builtin_ia32_gather3siv2df ((__v2df) __v1_old, *************** _mm_mmask_i32gather_pd (__m128d __v1_old *** 10264,10270 **** extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_ps (__m128 __v1_old, __mmask8 __mask, ! __m256i __index, float const *__addr, int __scale) { return (__m128) __builtin_ia32_gather3div8sf ((__v4sf) __v1_old, --- 10840,10846 ---- extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_ps (__m128 __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m128) __builtin_ia32_gather3div8sf ((__v4sf) __v1_old, *************** _mm256_mmask_i64gather_ps (__m128 __v1_o *** 10276,10282 **** extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_ps (__m128 __v1_old, __mmask8 __mask, ! __m128i __index, float const *__addr, int __scale) { return (__m128) __builtin_ia32_gather3div4sf ((__v4sf) __v1_old, --- 10852,10858 ---- extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_ps (__m128 __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128) __builtin_ia32_gather3div4sf ((__v4sf) __v1_old, *************** _mm_mmask_i64gather_ps (__m128 __v1_old, *** 10288,10294 **** extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_pd (__m256d __v1_old, __mmask8 __mask, ! __m256i __index, double const *__addr, int __scale) { return (__m256d) __builtin_ia32_gather3div4df ((__v4df) __v1_old, --- 10864,10870 ---- extern __inline __m256d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_pd (__m256d __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m256d) __builtin_ia32_gather3div4df ((__v4df) __v1_old, *************** _mm256_mmask_i64gather_pd (__m256d __v1_ *** 10300,10306 **** extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_pd (__m128d __v1_old, __mmask8 __mask, ! __m128i __index, double const *__addr, int __scale) { return (__m128d) __builtin_ia32_gather3div2df ((__v2df) __v1_old, --- 10876,10882 ---- extern __inline __m128d __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_pd (__m128d __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128d) __builtin_ia32_gather3div2df ((__v2df) __v1_old, *************** _mm_mmask_i64gather_pd (__m128d __v1_old *** 10312,10318 **** extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_epi32 (__m256i __v1_old, __mmask8 __mask, ! __m256i __index, int const *__addr, int __scale) { return (__m256i) __builtin_ia32_gather3siv8si ((__v8si) __v1_old, --- 10888,10894 ---- extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_epi32 (__m256i __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m256i) __builtin_ia32_gather3siv8si ((__v8si) __v1_old, *************** _mm256_mmask_i32gather_epi32 (__m256i __ *** 10324,10330 **** extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_epi32 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, int const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3siv4si ((__v4si) __v1_old, --- 10900,10906 ---- extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_epi32 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3siv4si ((__v4si) __v1_old, *************** _mm_mmask_i32gather_epi32 (__m128i __v1_ *** 10336,10342 **** extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_epi64 (__m256i __v1_old, __mmask8 __mask, ! __m128i __index, long long const *__addr, int __scale) { return (__m256i) __builtin_ia32_gather3siv4di ((__v4di) __v1_old, --- 10912,10918 ---- extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i32gather_epi64 (__m256i __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m256i) __builtin_ia32_gather3siv4di ((__v4di) __v1_old, *************** _mm256_mmask_i32gather_epi64 (__m256i __ *** 10348,10354 **** extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_epi64 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, long long const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3siv2di ((__v2di) __v1_old, --- 10924,10930 ---- extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i32gather_epi64 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3siv2di ((__v2di) __v1_old, *************** _mm_mmask_i32gather_epi64 (__m128i __v1_ *** 10360,10366 **** extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_epi32 (__m128i __v1_old, __mmask8 __mask, ! __m256i __index, int const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3div8si ((__v4si) __v1_old, --- 10936,10942 ---- extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_epi32 (__m128i __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3div8si ((__v4si) __v1_old, *************** _mm256_mmask_i64gather_epi32 (__m128i __ *** 10372,10378 **** extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_epi32 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, int const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3div4si ((__v4si) __v1_old, --- 10948,10954 ---- extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_epi32 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3div4si ((__v4si) __v1_old, *************** _mm_mmask_i64gather_epi32 (__m128i __v1_ *** 10384,10390 **** extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_epi64 (__m256i __v1_old, __mmask8 __mask, ! __m256i __index, long long const *__addr, int __scale) { return (__m256i) __builtin_ia32_gather3div4di ((__v4di) __v1_old, --- 10960,10966 ---- extern __inline __m256i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm256_mmask_i64gather_epi64 (__m256i __v1_old, __mmask8 __mask, ! __m256i __index, void const *__addr, int __scale) { return (__m256i) __builtin_ia32_gather3div4di ((__v4di) __v1_old, *************** _mm256_mmask_i64gather_epi64 (__m256i __ *** 10396,10402 **** extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_epi64 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, long long const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3div2di ((__v2di) __v1_old, --- 10972,10978 ---- extern __inline __m128i __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_mmask_i64gather_epi64 (__m128i __v1_old, __mmask8 __mask, ! __m128i __index, void const *__addr, int __scale) { return (__m128i) __builtin_ia32_gather3div2di ((__v2di) __v1_old, *************** _mm_mmask_i64gather_epi64 (__m128i __v1_ *** 10407,10413 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_ps (float *__addr, __m256i __index, __m256 __v1, const int __scale) { __builtin_ia32_scattersiv8sf (__addr, (__mmask8) 0xFF, --- 10983,10989 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_ps (void *__addr, __m256i __index, __m256 __v1, const int __scale) { __builtin_ia32_scattersiv8sf (__addr, (__mmask8) 0xFF, *************** _mm256_i32scatter_ps (float *__addr, __m *** 10417,10423 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_ps (float *__addr, __mmask8 __mask, __m256i __index, __m256 __v1, const int __scale) { --- 10993,10999 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_ps (void *__addr, __mmask8 __mask, __m256i __index, __m256 __v1, const int __scale) { *************** _mm256_mask_i32scatter_ps (float *__addr *** 10427,10433 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_ps (float *__addr, __m128i __index, __m128 __v1, const int __scale) { __builtin_ia32_scattersiv4sf (__addr, (__mmask8) 0xFF, --- 11003,11009 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_ps (void *__addr, __m128i __index, __m128 __v1, const int __scale) { __builtin_ia32_scattersiv4sf (__addr, (__mmask8) 0xFF, *************** _mm_i32scatter_ps (float *__addr, __m128 *** 10437,10443 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_ps (float *__addr, __mmask8 __mask, __m128i __index, __m128 __v1, const int __scale) { --- 11013,11019 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_ps (void *__addr, __mmask8 __mask, __m128i __index, __m128 __v1, const int __scale) { *************** _mm_mask_i32scatter_ps (float *__addr, _ *** 10447,10453 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_pd (double *__addr, __m128i __index, __m256d __v1, const int __scale) { __builtin_ia32_scattersiv4df (__addr, (__mmask8) 0xFF, --- 11023,11029 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_pd (void *__addr, __m128i __index, __m256d __v1, const int __scale) { __builtin_ia32_scattersiv4df (__addr, (__mmask8) 0xFF, *************** _mm256_i32scatter_pd (double *__addr, __ *** 10457,10463 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_pd (double *__addr, __mmask8 __mask, __m128i __index, __m256d __v1, const int __scale) { --- 11033,11039 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_pd (void *__addr, __mmask8 __mask, __m128i __index, __m256d __v1, const int __scale) { *************** _mm256_mask_i32scatter_pd (double *__add *** 10467,10473 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_pd (double *__addr, __m128i __index, __m128d __v1, const int __scale) { __builtin_ia32_scattersiv2df (__addr, (__mmask8) 0xFF, --- 11043,11049 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_pd (void *__addr, __m128i __index, __m128d __v1, const int __scale) { __builtin_ia32_scattersiv2df (__addr, (__mmask8) 0xFF, *************** _mm_i32scatter_pd (double *__addr, __m12 *** 10477,10483 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_pd (double *__addr, __mmask8 __mask, __m128i __index, __m128d __v1, const int __scale) { --- 11053,11059 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_pd (void *__addr, __mmask8 __mask, __m128i __index, __m128d __v1, const int __scale) { *************** _mm_mask_i32scatter_pd (double *__addr, *** 10487,10493 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_ps (float *__addr, __m256i __index, __m128 __v1, const int __scale) { __builtin_ia32_scatterdiv8sf (__addr, (__mmask8) 0xFF, --- 11063,11069 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_ps (void *__addr, __m256i __index, __m128 __v1, const int __scale) { __builtin_ia32_scatterdiv8sf (__addr, (__mmask8) 0xFF, *************** _mm256_i64scatter_ps (float *__addr, __m *** 10497,10503 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_ps (float *__addr, __mmask8 __mask, __m256i __index, __m128 __v1, const int __scale) { --- 11073,11079 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_ps (void *__addr, __mmask8 __mask, __m256i __index, __m128 __v1, const int __scale) { *************** _mm256_mask_i64scatter_ps (float *__addr *** 10507,10513 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_ps (float *__addr, __m128i __index, __m128 __v1, const int __scale) { __builtin_ia32_scatterdiv4sf (__addr, (__mmask8) 0xFF, --- 11083,11089 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_ps (void *__addr, __m128i __index, __m128 __v1, const int __scale) { __builtin_ia32_scatterdiv4sf (__addr, (__mmask8) 0xFF, *************** _mm_i64scatter_ps (float *__addr, __m128 *** 10517,10523 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_ps (float *__addr, __mmask8 __mask, __m128i __index, __m128 __v1, const int __scale) { --- 11093,11099 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_ps (void *__addr, __mmask8 __mask, __m128i __index, __m128 __v1, const int __scale) { *************** _mm_mask_i64scatter_ps (float *__addr, _ *** 10527,10533 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_pd (double *__addr, __m256i __index, __m256d __v1, const int __scale) { __builtin_ia32_scatterdiv4df (__addr, (__mmask8) 0xFF, --- 11103,11109 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_pd (void *__addr, __m256i __index, __m256d __v1, const int __scale) { __builtin_ia32_scatterdiv4df (__addr, (__mmask8) 0xFF, *************** _mm256_i64scatter_pd (double *__addr, __ *** 10537,10543 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_pd (double *__addr, __mmask8 __mask, __m256i __index, __m256d __v1, const int __scale) { --- 11113,11119 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_pd (void *__addr, __mmask8 __mask, __m256i __index, __m256d __v1, const int __scale) { *************** _mm256_mask_i64scatter_pd (double *__add *** 10547,10553 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_pd (double *__addr, __m128i __index, __m128d __v1, const int __scale) { __builtin_ia32_scatterdiv2df (__addr, (__mmask8) 0xFF, --- 11123,11129 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_pd (void *__addr, __m128i __index, __m128d __v1, const int __scale) { __builtin_ia32_scatterdiv2df (__addr, (__mmask8) 0xFF, *************** _mm_i64scatter_pd (double *__addr, __m12 *** 10557,10563 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_pd (double *__addr, __mmask8 __mask, __m128i __index, __m128d __v1, const int __scale) { --- 11133,11139 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_pd (void *__addr, __mmask8 __mask, __m128i __index, __m128d __v1, const int __scale) { *************** _mm_mask_i64scatter_pd (double *__addr, *** 10567,10573 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_epi32 (int *__addr, __m256i __index, __m256i __v1, const int __scale) { __builtin_ia32_scattersiv8si (__addr, (__mmask8) 0xFF, --- 11143,11149 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_epi32 (void *__addr, __m256i __index, __m256i __v1, const int __scale) { __builtin_ia32_scattersiv8si (__addr, (__mmask8) 0xFF, *************** _mm256_i32scatter_epi32 (int *__addr, __ *** 10577,10583 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_epi32 (int *__addr, __mmask8 __mask, __m256i __index, __m256i __v1, const int __scale) { --- 11153,11159 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_epi32 (void *__addr, __mmask8 __mask, __m256i __index, __m256i __v1, const int __scale) { *************** _mm256_mask_i32scatter_epi32 (int *__add *** 10587,10593 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_epi32 (int *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scattersiv4si (__addr, (__mmask8) 0xFF, --- 11163,11169 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_epi32 (void *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scattersiv4si (__addr, (__mmask8) 0xFF, *************** _mm_i32scatter_epi32 (int *__addr, __m12 *** 10597,10603 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_epi32 (int *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { --- 11173,11179 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_epi32 (void *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { *************** _mm_mask_i32scatter_epi32 (int *__addr, *** 10607,10613 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_epi64 (long long *__addr, __m128i __index, __m256i __v1, const int __scale) { __builtin_ia32_scattersiv4di (__addr, (__mmask8) 0xFF, --- 11183,11189 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i32scatter_epi64 (void *__addr, __m128i __index, __m256i __v1, const int __scale) { __builtin_ia32_scattersiv4di (__addr, (__mmask8) 0xFF, *************** _mm256_i32scatter_epi64 (long long *__ad *** 10617,10623 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_epi64 (long long *__addr, __mmask8 __mask, __m128i __index, __m256i __v1, const int __scale) { --- 11193,11199 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i32scatter_epi64 (void *__addr, __mmask8 __mask, __m128i __index, __m256i __v1, const int __scale) { *************** _mm256_mask_i32scatter_epi64 (long long *** 10627,10633 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_epi64 (long long *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scattersiv2di (__addr, (__mmask8) 0xFF, --- 11203,11209 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i32scatter_epi64 (void *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scattersiv2di (__addr, (__mmask8) 0xFF, *************** _mm_i32scatter_epi64 (long long *__addr, *** 10637,10643 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_epi64 (long long *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { --- 11213,11219 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i32scatter_epi64 (void *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { *************** _mm_mask_i32scatter_epi64 (long long *__ *** 10647,10653 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_epi32 (int *__addr, __m256i __index, __m128i __v1, const int __scale) { __builtin_ia32_scatterdiv8si (__addr, (__mmask8) 0xFF, --- 11223,11229 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_epi32 (void *__addr, __m256i __index, __m128i __v1, const int __scale) { __builtin_ia32_scatterdiv8si (__addr, (__mmask8) 0xFF, *************** _mm256_i64scatter_epi32 (int *__addr, __ *** 10657,10663 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_epi32 (int *__addr, __mmask8 __mask, __m256i __index, __m128i __v1, const int __scale) { --- 11233,11239 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_epi32 (void *__addr, __mmask8 __mask, __m256i __index, __m128i __v1, const int __scale) { *************** _mm256_mask_i64scatter_epi32 (int *__add *** 10667,10673 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_epi32 (int *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scatterdiv4si (__addr, (__mmask8) 0xFF, --- 11243,11249 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_epi32 (void *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scatterdiv4si (__addr, (__mmask8) 0xFF, *************** _mm_i64scatter_epi32 (int *__addr, __m12 *** 10677,10683 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_epi32 (int *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { --- 11253,11259 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_epi32 (void *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { *************** _mm_mask_i64scatter_epi32 (int *__addr, *** 10687,10693 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_epi64 (long long *__addr, __m256i __index, __m256i __v1, const int __scale) { __builtin_ia32_scatterdiv4di (__addr, (__mmask8) 0xFF, --- 11263,11269 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_i64scatter_epi64 (void *__addr, __m256i __index, __m256i __v1, const int __scale) { __builtin_ia32_scatterdiv4di (__addr, (__mmask8) 0xFF, *************** _mm256_i64scatter_epi64 (long long *__ad *** 10697,10703 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_epi64 (long long *__addr, __mmask8 __mask, __m256i __index, __m256i __v1, const int __scale) { --- 11273,11279 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm256_mask_i64scatter_epi64 (void *__addr, __mmask8 __mask, __m256i __index, __m256i __v1, const int __scale) { *************** _mm256_mask_i64scatter_epi64 (long long *** 10707,10713 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_epi64 (long long *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scatterdiv2di (__addr, (__mmask8) 0xFF, --- 11283,11289 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_i64scatter_epi64 (void *__addr, __m128i __index, __m128i __v1, const int __scale) { __builtin_ia32_scatterdiv2di (__addr, (__mmask8) 0xFF, *************** _mm_i64scatter_epi64 (long long *__addr, *** 10717,10723 **** extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_epi64 (long long *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { --- 11293,11299 ---- extern __inline void __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) ! _mm_mask_i64scatter_epi64 (void *__addr, __mmask8 __mask, __m128i __index, __m128i __v1, const int __scale) { *************** _mm256_permutex_pd (__m256d __X, const i *** 11771,12352 **** (__mmask8) -1); } - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpneq_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpneq_epu32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmplt_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmplt_epu32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpge_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpge_epu32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmple_epu32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmple_epu32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd256_mask ((__v8si) __X, - (__v8si) __Y, 2, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpneq_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpneq_epu64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmplt_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmplt_epu64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpge_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpge_epu64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmple_epu64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmple_epu64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq256_mask ((__v4di) __X, - (__v4di) __Y, 2, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpneq_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpneq_epi32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmplt_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmplt_epi32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpge_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpge_epi32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmple_epi32_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmple_epi32_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpd256_mask ((__v8si) __X, - (__v8si) __Y, 2, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpneq_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpneq_epi64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmplt_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmplt_epi64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmpge_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmpge_epi64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_mask_cmple_epi64_mask (__mmask8 __M, __m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm256_cmple_epi64_mask (__m256i __X, __m256i __Y) - { - return (__mmask8) __builtin_ia32_cmpq256_mask ((__v4di) __X, - (__v4di) __Y, 2, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpneq_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpneq_epu32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmplt_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmplt_epu32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpge_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpge_epu32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmple_epu32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmple_epu32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpd128_mask ((__v4si) __X, - (__v4si) __Y, 2, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpneq_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpneq_epu64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmplt_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmplt_epu64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpge_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpge_epu64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmple_epu64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmple_epu64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_ucmpq128_mask ((__v2di) __X, - (__v2di) __Y, 2, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpneq_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpneq_epi32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmplt_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmplt_epi32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpge_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpge_epi32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmple_epi32_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmple_epi32_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpd128_mask ((__v4si) __X, - (__v4si) __Y, 2, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpneq_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 4, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpneq_epi64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 4, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmplt_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 1, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmplt_epi64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 1, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmpge_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 5, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmpge_epi64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 5, - (__mmask8) -1); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_mask_cmple_epi64_mask (__mmask8 __M, __m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 2, - (__mmask8) __M); - } - - extern __inline __mmask8 - __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) - _mm_cmple_epi64_mask (__m128i __X, __m128i __Y) - { - return (__mmask8) __builtin_ia32_cmpq128_mask ((__v2di) __X, - (__v2di) __Y, 2, - (__mmask8) -1); - } - #else #define _mm256_permutex_pd(X, M) \ ((__m256d) __builtin_ia32_permdf256_mask ((__v4df)(__m256d)(X), (int)(M), \ --- 12347,12352 ---- *************** _mm_cmple_epi64_mask (__m128i __X, __m12 *** 12868,13124 **** #define _mm256_mmask_i32gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256) __builtin_ia32_gather3siv8sf ((__v8sf)(__m256)V1OLD, \ ! (float const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128) __builtin_ia32_gather3siv4sf ((__v4sf)(__m128)V1OLD, \ ! (float const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i32gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256d) __builtin_ia32_gather3siv4df ((__v4df)(__m256d)V1OLD, \ ! (double const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128d) __builtin_ia32_gather3siv2df ((__v2df)(__m128d)V1OLD, \ ! (double const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128) __builtin_ia32_gather3div8sf ((__v4sf)(__m128)V1OLD, \ ! (float const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128) __builtin_ia32_gather3div4sf ((__v4sf)(__m128)V1OLD, \ ! (float const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256d) __builtin_ia32_gather3div4df ((__v4df)(__m256d)V1OLD, \ ! (double const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128d) __builtin_ia32_gather3div2df ((__v2df)(__m128d)V1OLD, \ ! (double const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i32gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gather3siv8si ((__v8si)(__m256i)V1OLD, \ ! (int const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3siv4si ((__v4si)(__m128i)V1OLD, \ ! (int const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i32gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gather3siv4di ((__v4di)(__m256i)V1OLD, \ ! (long long const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3siv2di ((__v2di)(__m128i)V1OLD, \ ! (long long const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3div8si ((__v4si)(__m128i)V1OLD, \ ! (int const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3div4si ((__v4si)(__m128i)V1OLD, \ ! (int const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gather3div4di ((__v4di)(__m256i)V1OLD, \ ! (long long const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3div2di ((__v2di)(__m128i)V1OLD, \ ! (long long const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_i32scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8sf ((float *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm256_mask_i32scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8sf ((float *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm_i32scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4sf ((float *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm_mask_i32scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4sf ((float *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm256_i32scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4df ((double *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm256_mask_i32scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4df ((double *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm_i32scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2df ((double *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm_mask_i32scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2df ((double *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm256_i64scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8sf ((float *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm256_mask_i64scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8sf ((float *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm_i64scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4sf ((float *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm_mask_i64scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4sf ((float *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm256_i64scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4df ((double *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm256_mask_i64scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4df ((double *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm_i64scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2df ((double *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm_mask_i64scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2df ((double *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm256_i32scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8si ((int *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm256_mask_i32scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8si ((int *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm_i32scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4si ((int *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm_mask_i32scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4si ((int *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm256_i32scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4di ((long long *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm256_mask_i32scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4di ((long long *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm_i32scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2di ((long long *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) #define _mm_mask_i32scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2di ((long long *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) #define _mm256_i64scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8si ((int *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm256_mask_i64scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8si ((int *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm_i64scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4si ((int *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm_mask_i64scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4si ((int *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm256_i64scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4di ((long long *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm256_mask_i64scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4di ((long long *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm_i64scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2di ((long long *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) #define _mm_mask_i64scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2di ((long long *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) --- 12868,13124 ---- #define _mm256_mmask_i32gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256) __builtin_ia32_gather3siv8sf ((__v8sf)(__m256)V1OLD, \ ! (void const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128) __builtin_ia32_gather3siv4sf ((__v4sf)(__m128)V1OLD, \ ! (void const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i32gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256d) __builtin_ia32_gather3siv4df ((__v4df)(__m256d)V1OLD, \ ! (void const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128d) __builtin_ia32_gather3siv2df ((__v2df)(__m128d)V1OLD, \ ! (void const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128) __builtin_ia32_gather3div8sf ((__v4sf)(__m128)V1OLD, \ ! (void const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_ps(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128) __builtin_ia32_gather3div4sf ((__v4sf)(__m128)V1OLD, \ ! (void const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256d) __builtin_ia32_gather3div4df ((__v4df)(__m256d)V1OLD, \ ! (void const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_pd(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128d) __builtin_ia32_gather3div2df ((__v2df)(__m128d)V1OLD, \ ! (void const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i32gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gather3siv8si ((__v8si)(__m256i)V1OLD, \ ! (void const *)ADDR, \ (__v8si)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3siv4si ((__v4si)(__m128i)V1OLD, \ ! (void const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i32gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gather3siv4di ((__v4di)(__m256i)V1OLD, \ ! (void const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i32gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3siv2di ((__v2di)(__m128i)V1OLD, \ ! (void const *)ADDR, \ (__v4si)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3div8si ((__v4si)(__m128i)V1OLD, \ ! (void const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_epi32(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3div4si ((__v4si)(__m128i)V1OLD, \ ! (void const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_mmask_i64gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m256i) __builtin_ia32_gather3div4di ((__v4di)(__m256i)V1OLD, \ ! (void const *)ADDR, \ (__v4di)(__m256i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm_mmask_i64gather_epi64(V1OLD, MASK, INDEX, ADDR, SCALE) \ (__m128i) __builtin_ia32_gather3div2di ((__v2di)(__m128i)V1OLD, \ ! (void const *)ADDR, \ (__v2di)(__m128i)INDEX, \ (__mmask8)MASK, (int)SCALE) #define _mm256_i32scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8sf ((void *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm256_mask_i32scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8sf ((void *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8sf)(__m256)V1, (int)SCALE) #define _mm_i32scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4sf ((void *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm_mask_i32scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4sf ((void *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm256_i32scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4df ((void *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm256_mask_i32scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4df ((void *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm_i32scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2df ((void *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm_mask_i32scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2df ((void *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm256_i64scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8sf ((void *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm256_mask_i64scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8sf ((void *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm_i64scatter_ps(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4sf ((void *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm_mask_i64scatter_ps(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4sf ((void *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v4sf)(__m128)V1, (int)SCALE) #define _mm256_i64scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4df ((void *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm256_mask_i64scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4df ((void *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4df)(__m256d)V1, (int)SCALE) #define _mm_i64scatter_pd(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2df ((void *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm_mask_i64scatter_pd(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2df ((void *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v2df)(__m128d)V1, (int)SCALE) #define _mm256_i32scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8si ((void *)ADDR, (__mmask8)0xFF, \ (__v8si)(__m256i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm256_mask_i32scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv8si ((void *)ADDR, (__mmask8)MASK, \ (__v8si)(__m256i)INDEX, \ (__v8si)(__m256i)V1, (int)SCALE) #define _mm_i32scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4si ((void *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm_mask_i32scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4si ((void *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm256_i32scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4di ((void *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm256_mask_i32scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv4di ((void *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm_i32scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2di ((void *)ADDR, (__mmask8)0xFF, \ (__v4si)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) #define _mm_mask_i32scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scattersiv2di ((void *)ADDR, (__mmask8)MASK, \ (__v4si)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) #define _mm256_i64scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8si ((void *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm256_mask_i64scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv8si ((void *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm_i64scatter_epi32(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4si ((void *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm_mask_i64scatter_epi32(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4si ((void *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v4si)(__m128i)V1, (int)SCALE) #define _mm256_i64scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4di ((void *)ADDR, (__mmask8)0xFF, \ (__v4di)(__m256i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm256_mask_i64scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv4di ((void *)ADDR, (__mmask8)MASK, \ (__v4di)(__m256i)INDEX, \ (__v4di)(__m256i)V1, (int)SCALE) #define _mm_i64scatter_epi64(ADDR, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2di ((void *)ADDR, (__mmask8)0xFF, \ (__v2di)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) #define _mm_mask_i64scatter_epi64(ADDR, MASK, INDEX, V1, SCALE) \ ! __builtin_ia32_scatterdiv2di ((void *)ADDR, (__mmask8)MASK, \ (__v2di)(__m128i)INDEX, \ (__v2di)(__m128i)V1, (int)SCALE) diff -Nrcpad gcc-6.3.0/gcc/config/i386/cpuid.h gcc-6.4.0/gcc/config/i386/cpuid.h *** gcc-6.3.0/gcc/config/i386/cpuid.h Thu Oct 13 21:15:45 2016 --- gcc-6.4.0/gcc/config/i386/cpuid.h Thu Jun 22 11:20:29 2017 *************** *** 63,69 **** #define bit_MMXEXT (1 << 22) #define bit_LM (1 << 29) #define bit_3DNOWP (1 << 30) ! #define bit_3DNOW (1 << 31) /* %ebx. */ #define bit_CLZERO (1 << 0) --- 63,69 ---- #define bit_MMXEXT (1 << 22) #define bit_LM (1 << 29) #define bit_3DNOWP (1 << 30) ! #define bit_3DNOW (1u << 31) /* %ebx. */ #define bit_CLZERO (1 << 0) *************** *** 89,95 **** #define bit_AVX512CD (1 << 28) #define bit_SHA (1 << 29) #define bit_AVX512BW (1 << 30) ! #define bit_AVX512VL (1 << 31) /* %ecx */ #define bit_PREFETCHWT1 (1 << 0) --- 89,95 ---- #define bit_AVX512CD (1 << 28) #define bit_SHA (1 << 29) #define bit_AVX512BW (1 << 30) ! #define bit_AVX512VL (1u << 31) /* %ecx */ #define bit_PREFETCHWT1 (1 << 0) *************** *** 172,178 **** /* Return highest supported input value for cpuid instruction. ext can ! be either 0x0 or 0x8000000 to return highest supported value for basic or extended cpuid information. Function returns 0 if cpuid is not supported or whatever cpuid returns in eax register. If sig pointer is non-null, then first four bytes of the signature --- 172,178 ---- /* Return highest supported input value for cpuid instruction. ext can ! be either 0x0 or 0x80000000 to return highest supported value for basic or extended cpuid information. Function returns 0 if cpuid is not supported or whatever cpuid returns in eax register. If sig pointer is non-null, then first four bytes of the signature *************** __get_cpuid (unsigned int __leaf, *** 239,246 **** unsigned int *__ecx, unsigned int *__edx) { unsigned int __ext = __leaf & 0x80000000; ! if (__get_cpuid_max (__ext, 0) < __leaf) return 0; __cpuid (__leaf, *__eax, *__ebx, *__ecx, *__edx); --- 239,247 ---- unsigned int *__ecx, unsigned int *__edx) { unsigned int __ext = __leaf & 0x80000000; + unsigned int __maxlevel = __get_cpuid_max (__ext, 0); ! if (__maxlevel == 0 || __maxlevel < __leaf) return 0; __cpuid (__leaf, *__eax, *__ebx, *__ecx, *__edx); *************** __get_cpuid_count (unsigned int __leaf, *** 255,262 **** unsigned int *__ecx, unsigned int *__edx) { unsigned int __ext = __leaf & 0x80000000; ! if (__get_cpuid_max (__ext, 0) < __leaf) return 0; __cpuid_count (__leaf, __subleaf, *__eax, *__ebx, *__ecx, *__edx); --- 256,264 ---- unsigned int *__ecx, unsigned int *__edx) { unsigned int __ext = __leaf & 0x80000000; + unsigned int __maxlevel = __get_cpuid_max (__ext, 0); ! if (__maxlevel == 0 || __maxlevel < __leaf) return 0; __cpuid_count (__leaf, __subleaf, *__eax, *__ebx, *__ecx, *__edx); diff -Nrcpad gcc-6.3.0/gcc/config/i386/gmm_malloc.h gcc-6.4.0/gcc/config/i386/gmm_malloc.h *** gcc-6.3.0/gcc/config/i386/gmm_malloc.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/gmm_malloc.h Thu Jun 1 19:38:29 2017 *************** *** 27,74 **** #include #include ! static __inline__ void* ! _mm_malloc (size_t size, size_t align) { ! void * malloc_ptr; ! void * aligned_ptr; /* Error if align is not a power of two. */ ! if (align & (align - 1)) { errno = EINVAL; ! return ((void*) 0); } ! if (size == 0) return ((void *) 0); /* Assume malloc'd pointer is aligned at least to sizeof (void*). If necessary, add another sizeof (void*) to store the value returned by malloc. Effectively this enforces a minimum alignment of sizeof double. */ ! if (align < 2 * sizeof (void *)) ! align = 2 * sizeof (void *); ! malloc_ptr = malloc (size + align); ! if (!malloc_ptr) return ((void *) 0); /* Align We have at least sizeof (void *) space below malloc'd ptr. */ ! aligned_ptr = (void *) (((size_t) malloc_ptr + align) ! & ~((size_t) (align) - 1)); /* Store the original pointer just before p. */ ! ((void **) aligned_ptr) [-1] = malloc_ptr; ! return aligned_ptr; } static __inline__ void ! _mm_free (void * aligned_ptr) { ! if (aligned_ptr) ! free (((void **) aligned_ptr) [-1]); } #endif /* _MM_MALLOC_H_INCLUDED */ --- 27,74 ---- #include #include ! static __inline__ void * ! _mm_malloc (size_t __size, size_t __align) { ! void * __malloc_ptr; ! void * __aligned_ptr; /* Error if align is not a power of two. */ ! if (__align & (__align - 1)) { errno = EINVAL; ! return ((void *) 0); } ! if (__size == 0) return ((void *) 0); /* Assume malloc'd pointer is aligned at least to sizeof (void*). If necessary, add another sizeof (void*) to store the value returned by malloc. Effectively this enforces a minimum alignment of sizeof double. */ ! if (__align < 2 * sizeof (void *)) ! __align = 2 * sizeof (void *); ! __malloc_ptr = malloc (__size + __align); ! if (!__malloc_ptr) return ((void *) 0); /* Align We have at least sizeof (void *) space below malloc'd ptr. */ ! __aligned_ptr = (void *) (((size_t) __malloc_ptr + __align) ! & ~((size_t) (__align) - 1)); /* Store the original pointer just before p. */ ! ((void **) __aligned_ptr)[-1] = __malloc_ptr; ! return __aligned_ptr; } static __inline__ void ! _mm_free (void *__aligned_ptr) { ! if (__aligned_ptr) ! free (((void **) __aligned_ptr)[-1]); } #endif /* _MM_MALLOC_H_INCLUDED */ diff -Nrcpad gcc-6.3.0/gcc/config/i386/i386-builtin-types.def gcc-6.4.0/gcc/config/i386/i386-builtin-types.def *** gcc-6.3.0/gcc/config/i386/i386-builtin-types.def Wed Oct 26 15:13:39 2016 --- gcc-6.4.0/gcc/config/i386/i386-builtin-types.def Thu Feb 16 16:41:36 2017 *************** DEF_FUNCTION_TYPE (V4SI, V4SI, PCINT, V2 *** 969,1040 **** DEF_FUNCTION_TYPE (V4SI, V4SI, PCINT, V4DI, V4SI, INT) DEF_FUNCTION_TYPE (V8SI, V8SI, PCINT, V4DI, V8SI, INT) - DEF_FUNCTION_TYPE (V16SF, V16SF, PCFLOAT, V16SI, HI, INT) DEF_FUNCTION_TYPE (V16SF, V16SF, PCFLOAT, V8DI, HI, INT) - DEF_FUNCTION_TYPE (V8DF, V8DF, PCDOUBLE, V8SI, QI, INT) DEF_FUNCTION_TYPE (V8DF, V8DF, PCDOUBLE, V16SI, QI, INT) - DEF_FUNCTION_TYPE (V8SF, V8SF, PCFLOAT, V8DI, QI, INT) - DEF_FUNCTION_TYPE (V8DF, V8DF, PCDOUBLE, V8DI, QI, INT) - DEF_FUNCTION_TYPE (V16SI, V16SI, PCINT, V16SI, HI, INT) DEF_FUNCTION_TYPE (V16SI, V16SI, PCINT, V8DI, HI, INT) - DEF_FUNCTION_TYPE (V8DI, V8DI, PCINT64, V8SI, QI, INT) DEF_FUNCTION_TYPE (V8DI, V8DI, PCINT64, V16SI, QI, INT) - DEF_FUNCTION_TYPE (V8SI, V8SI, PCINT, V8DI, QI, INT) - DEF_FUNCTION_TYPE (V8DI, V8DI, PCINT64, V8DI, QI, INT) - DEF_FUNCTION_TYPE (V2DF, V2DF, PCDOUBLE, V4SI, QI, INT) - DEF_FUNCTION_TYPE (V4DF, V4DF, PCDOUBLE, V4SI, QI, INT) DEF_FUNCTION_TYPE (V4DF, V4DF, PCDOUBLE, V8SI, QI, INT) - DEF_FUNCTION_TYPE (V2DF, V2DF, PCDOUBLE, V2DI, QI, INT) - DEF_FUNCTION_TYPE (V4DF, V4DF, PCDOUBLE, V4DI, QI, INT) - DEF_FUNCTION_TYPE (V4SF, V4SF, PCFLOAT, V4SI, QI, INT) - DEF_FUNCTION_TYPE (V8SF, V8SF, PCFLOAT, V8SI, QI, INT) - DEF_FUNCTION_TYPE (V4SF, V4SF, PCFLOAT, V2DI, QI, INT) - DEF_FUNCTION_TYPE (V4SF, V4SF, PCFLOAT, V4DI, QI, INT) DEF_FUNCTION_TYPE (V8SF, V8SF, PCFLOAT, V4DI, QI, INT) - DEF_FUNCTION_TYPE (V2DI, V2DI, PCINT64, V4SI, QI, INT) - DEF_FUNCTION_TYPE (V4DI, V4DI, PCINT64, V4SI, QI, INT) DEF_FUNCTION_TYPE (V4DI, V4DI, PCINT64, V8SI, QI, INT) - DEF_FUNCTION_TYPE (V2DI, V2DI, PCINT64, V2DI, QI, INT) - DEF_FUNCTION_TYPE (V4DI, V4DI, PCINT64, V4DI, QI, INT) - DEF_FUNCTION_TYPE (V4SI, V4SI, PCINT, V4SI, QI, INT) - DEF_FUNCTION_TYPE (V8SI, V8SI, PCINT, V8SI, QI, INT) - DEF_FUNCTION_TYPE (V4SI, V4SI, PCINT, V2DI, QI, INT) - DEF_FUNCTION_TYPE (V4SI, V4SI, PCINT, V4DI, QI, INT) DEF_FUNCTION_TYPE (V8SI, V8SI, PCINT, V4DI, QI, INT) - DEF_FUNCTION_TYPE (VOID, PFLOAT, HI, V16SI, V16SF, INT) - DEF_FUNCTION_TYPE (VOID, PFLOAT, QI, V8SI, V8SF, INT) - DEF_FUNCTION_TYPE (VOID, PFLOAT, QI, V4SI, V4SF, INT) - DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V8SI, V8DF, INT) - DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V4SI, V4DF, INT) - DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V4SI, V2DF, INT) - DEF_FUNCTION_TYPE (VOID, PFLOAT, QI, V8DI, V8SF, INT) - DEF_FUNCTION_TYPE (VOID, PFLOAT, QI, V4DI, V4SF, INT) - DEF_FUNCTION_TYPE (VOID, PFLOAT, QI, V2DI, V4SF, INT) - DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V8DI, V8DF, INT) - DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V4DI, V4DF, INT) - DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V2DI, V2DF, INT) - DEF_FUNCTION_TYPE (VOID, PINT, HI, V16SI, V16SI, INT) - DEF_FUNCTION_TYPE (VOID, PINT, QI, V8SI, V8SI, INT) - DEF_FUNCTION_TYPE (VOID, PINT, QI, V4SI, V4SI, INT) - DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V8SI, V8DI, INT) - DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V4SI, V4DI, INT) - DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V4SI, V2DI, INT) - DEF_FUNCTION_TYPE (VOID, PINT, QI, V8DI, V8SI, INT) - DEF_FUNCTION_TYPE (VOID, PINT, QI, V4DI, V4SI, INT) - DEF_FUNCTION_TYPE (VOID, PINT, QI, V2DI, V4SI, INT) - DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V8DI, V8DI, INT) DEF_FUNCTION_TYPE (VOID, PFLOAT, HI, V8DI, V16SF, INT) DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V16SI, V8DF, INT) DEF_FUNCTION_TYPE (VOID, PINT, HI, V8DI, V16SI, INT) DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V16SI, V8DI, INT) ! DEF_FUNCTION_TYPE (VOID, QI, V8SI, PCINT64, INT, INT) ! DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V4DI, V4DI, INT) ! DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V2DI, V2DI, INT) ! DEF_FUNCTION_TYPE (VOID, HI, V16SI, PCINT, INT, INT) ! DEF_FUNCTION_TYPE (VOID, QI, V8DI, PCINT64, INT, INT) ! DEF_FUNCTION_TYPE (VOID, QI, V8DI, PCINT, INT, INT) DEF_FUNCTION_TYPE_ALIAS (V2DF_FTYPE_V2DF, ROUND) DEF_FUNCTION_TYPE_ALIAS (V4DF_FTYPE_V4DF, ROUND) --- 969,1040 ---- DEF_FUNCTION_TYPE (V4SI, V4SI, PCINT, V4DI, V4SI, INT) DEF_FUNCTION_TYPE (V8SI, V8SI, PCINT, V4DI, V8SI, INT) DEF_FUNCTION_TYPE (V16SF, V16SF, PCFLOAT, V8DI, HI, INT) DEF_FUNCTION_TYPE (V8DF, V8DF, PCDOUBLE, V16SI, QI, INT) DEF_FUNCTION_TYPE (V16SI, V16SI, PCINT, V8DI, HI, INT) DEF_FUNCTION_TYPE (V8DI, V8DI, PCINT64, V16SI, QI, INT) DEF_FUNCTION_TYPE (V4DF, V4DF, PCDOUBLE, V8SI, QI, INT) DEF_FUNCTION_TYPE (V8SF, V8SF, PCFLOAT, V4DI, QI, INT) DEF_FUNCTION_TYPE (V4DI, V4DI, PCINT64, V8SI, QI, INT) DEF_FUNCTION_TYPE (V8SI, V8SI, PCINT, V4DI, QI, INT) DEF_FUNCTION_TYPE (VOID, PFLOAT, HI, V8DI, V16SF, INT) DEF_FUNCTION_TYPE (VOID, PDOUBLE, QI, V16SI, V8DF, INT) DEF_FUNCTION_TYPE (VOID, PINT, HI, V8DI, V16SI, INT) DEF_FUNCTION_TYPE (VOID, PLONGLONG, QI, V16SI, V8DI, INT) ! ! DEF_FUNCTION_TYPE (V16SF, V16SF, PCVOID, V16SI, HI, INT) ! DEF_FUNCTION_TYPE (V8DF, V8DF, PCVOID, V8SI, QI, INT) ! DEF_FUNCTION_TYPE (V8SF, V8SF, PCVOID, V8DI, QI, INT) ! DEF_FUNCTION_TYPE (V8DF, V8DF, PCVOID, V8DI, QI, INT) ! DEF_FUNCTION_TYPE (V16SI, V16SI, PCVOID, V16SI, HI, INT) ! DEF_FUNCTION_TYPE (V8DI, V8DI, PCVOID, V8SI, QI, INT) ! DEF_FUNCTION_TYPE (V8SI, V8SI, PCVOID, V8DI, QI, INT) ! DEF_FUNCTION_TYPE (V8DI, V8DI, PCVOID, V8DI, QI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, HI, V16SI, V16SF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8SI, V8DF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8DI, V8SF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8DI, V8DF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, HI, V16SI, V16SI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8SI, V8DI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8DI, V8SI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8DI, V8DI, INT) ! DEF_FUNCTION_TYPE (V2DF, V2DF, PCVOID, V4SI, QI, INT) ! DEF_FUNCTION_TYPE (V4DF, V4DF, PCVOID, V4SI, QI, INT) ! DEF_FUNCTION_TYPE (V2DF, V2DF, PCVOID, V2DI, QI, INT) ! DEF_FUNCTION_TYPE (V4DF, V4DF, PCVOID, V4DI, QI, INT) ! DEF_FUNCTION_TYPE (V4SF, V4SF, PCVOID, V4SI, QI, INT) ! DEF_FUNCTION_TYPE (V8SF, V8SF, PCVOID, V8SI, QI, INT) ! DEF_FUNCTION_TYPE (V4SF, V4SF, PCVOID, V2DI, QI, INT) ! DEF_FUNCTION_TYPE (V4SF, V4SF, PCVOID, V4DI, QI, INT) ! DEF_FUNCTION_TYPE (V2DI, V2DI, PCVOID, V4SI, QI, INT) ! DEF_FUNCTION_TYPE (V4DI, V4DI, PCVOID, V4SI, QI, INT) ! DEF_FUNCTION_TYPE (V2DI, V2DI, PCVOID, V2DI, QI, INT) ! DEF_FUNCTION_TYPE (V4DI, V4DI, PCVOID, V4DI, QI, INT) ! DEF_FUNCTION_TYPE (V4SI, V4SI, PCVOID, V4SI, QI, INT) ! DEF_FUNCTION_TYPE (V8SI, V8SI, PCVOID, V8SI, QI, INT) ! DEF_FUNCTION_TYPE (V4SI, V4SI, PCVOID, V2DI, QI, INT) ! DEF_FUNCTION_TYPE (V4SI, V4SI, PCVOID, V4DI, QI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8SI, V8SF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4SI, V4SF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4SI, V4DF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4SI, V2DF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4DI, V4SF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V2DI, V4SF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4DI, V4DF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V2DI, V2DF, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V8SI, V8SI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4SI, V4SI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4SI, V4DI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4SI, V2DI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4DI, V4SI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V2DI, V4SI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V4DI, V4DI, INT) ! DEF_FUNCTION_TYPE (VOID, PVOID, QI, V2DI, V2DI, INT) ! DEF_FUNCTION_TYPE (VOID, QI, V8SI, PCVOID, INT, INT) ! DEF_FUNCTION_TYPE (VOID, HI, V16SI, PCVOID, INT, INT) ! DEF_FUNCTION_TYPE (VOID, QI, V8DI, PCVOID, INT, INT) DEF_FUNCTION_TYPE_ALIAS (V2DF_FTYPE_V2DF, ROUND) DEF_FUNCTION_TYPE_ALIAS (V4DF_FTYPE_V4DF, ROUND) diff -Nrcpad gcc-6.3.0/gcc/config/i386/i386.c gcc-6.4.0/gcc/config/i386/i386.c *** gcc-6.3.0/gcc/config/i386/i386.c Wed Dec 14 15:44:07 2016 --- gcc-6.4.0/gcc/config/i386/i386.c Fri May 5 21:51:14 2017 *************** ix86_expand_split_stack_prologue (void) *** 14027,14032 **** --- 14027,14034 ---- GEN_INT (UNITS_PER_WORD), constm1_rtx, NULL_RTX, false); add_function_usage_to (call_insn, call_fusage); + /* Indicate that this function can't jump to non-local gotos. */ + make_reg_eh_region_note_nothrow_nononlocal (as_a (call_insn)); /* In order to make call/return prediction work right, we now need to execute a return instruction. See *************** ix86_print_operand (FILE *file, rtx x, i *** 16812,16819 **** break; default: ! output_operand_lossage ! ("invalid operand size for operand code 'O'"); return; } --- 16814,16821 ---- break; default: ! output_operand_lossage ("invalid operand size for operand " ! "code 'O'"); return; } *************** ix86_print_operand (FILE *file, rtx x, i *** 16847,16861 **** return; default: ! output_operand_lossage ! ("invalid operand size for operand code 'z'"); return; } } if (GET_MODE_CLASS (GET_MODE (x)) == MODE_FLOAT) ! warning ! (0, "non-integer operand used with operand code 'z'"); /* FALLTHRU */ case 'Z': --- 16849,16862 ---- return; default: ! output_operand_lossage ("invalid operand size for operand " ! "code 'z'"); return; } } if (GET_MODE_CLASS (GET_MODE (x)) == MODE_FLOAT) ! warning (0, "non-integer operand used with operand code 'z'"); /* FALLTHRU */ case 'Z': *************** ix86_print_operand (FILE *file, rtx x, i *** 16917,16929 **** } else { ! output_operand_lossage ! ("invalid operand type used with operand code 'Z'"); return; } ! output_operand_lossage ! ("invalid operand size for operand code 'Z'"); return; case 'd': --- 16918,16929 ---- } else { ! output_operand_lossage ("invalid operand type used with " ! "operand code 'Z'"); return; } ! output_operand_lossage ("invalid operand size for operand code 'Z'"); return; case 'd': *************** ix86_print_operand (FILE *file, rtx x, i *** 17115,17121 **** break; case 'K': ! gcc_assert (CONST_INT_P (x)); if (INTVAL (x) & IX86_HLE_ACQUIRE) #ifdef HAVE_AS_IX86_HLE --- 17115,17126 ---- break; case 'K': ! if (!CONST_INT_P (x)) ! { ! output_operand_lossage ("operand is not an integer, invalid " ! "operand code 'K'"); ! return; ! } if (INTVAL (x) & IX86_HLE_ACQUIRE) #ifdef HAVE_AS_IX86_HLE *************** ix86_print_operand (FILE *file, rtx x, i *** 17138,17145 **** return; case 'r': ! gcc_assert (CONST_INT_P (x)); ! gcc_assert (INTVAL (x) == ROUND_SAE); if (ASSEMBLER_DIALECT == ASM_INTEL) fputs (", ", file); --- 17143,17154 ---- return; case 'r': ! if (!CONST_INT_P (x) || INTVAL (x) != ROUND_SAE) ! { ! output_operand_lossage ("operand is not a specific integer, " ! "invalid operand code 'r'"); ! return; ! } if (ASSEMBLER_DIALECT == ASM_INTEL) fputs (", ", file); *************** ix86_print_operand (FILE *file, rtx x, i *** 17152,17158 **** return; case 'R': ! gcc_assert (CONST_INT_P (x)); if (ASSEMBLER_DIALECT == ASM_INTEL) fputs (", ", file); --- 17161,17172 ---- return; case 'R': ! if (!CONST_INT_P (x)) ! { ! output_operand_lossage ("operand is not an integer, invalid " ! "operand code 'R'"); ! return; ! } if (ASSEMBLER_DIALECT == ASM_INTEL) fputs (", ", file); *************** ix86_print_operand (FILE *file, rtx x, i *** 17172,17178 **** fputs ("{rz-sae}", file); break; default: ! gcc_unreachable (); } if (ASSEMBLER_DIALECT == ASM_ATT) --- 17186,17193 ---- fputs ("{rz-sae}", file); break; default: ! output_operand_lossage ("operand is not a specific integer, " ! "invalid operand code 'R'"); } if (ASSEMBLER_DIALECT == ASM_ATT) *************** ix86_print_operand (FILE *file, rtx x, i *** 17267,17273 **** return; default: ! output_operand_lossage ("invalid operand code '%c'", code); } } --- 17282,17288 ---- return; default: ! output_operand_lossage ("invalid operand code '%c'", code); } } *************** memory_address_length (rtx addr, bool le *** 27721,27727 **** else if (disp && !base && !index) { len += 4; ! if (rip_relative_addr_p (&parts)) len++; } else --- 27736,27742 ---- else if (disp && !base && !index) { len += 4; ! if (!rip_relative_addr_p (&parts)) len++; } else *************** ix86_local_alignment (tree exp, machine_ *** 29372,29378 **** != TYPE_MAIN_VARIANT (va_list_type_node))) && TYPE_SIZE (type) && TREE_CODE (TYPE_SIZE (type)) == INTEGER_CST ! && wi::geu_p (TYPE_SIZE (type), 16) && align < 128) return 128; } --- 29387,29393 ---- != TYPE_MAIN_VARIANT (va_list_type_node))) && TYPE_SIZE (type) && TREE_CODE (TYPE_SIZE (type)) == INTEGER_CST ! && wi::geu_p (TYPE_SIZE (type), 128) && align < 128) return 128; } *************** static const struct builtin_description *** 32715,32723 **** /* Special builtins with variable number of arguments. */ static const struct builtin_description bdesc_special_args[] = { ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_nothing, "__builtin_ia32_rdtsc", IX86_BUILTIN_RDTSC, UNKNOWN, (int) UINT64_FTYPE_VOID }, ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_nothing, "__builtin_ia32_rdtscp", IX86_BUILTIN_RDTSCP, UNKNOWN, (int) UINT64_FTYPE_PUNSIGNED }, ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_pause, "__builtin_ia32_pause", IX86_BUILTIN_PAUSE, UNKNOWN, (int) VOID_FTYPE_VOID }, /* 80387 (for use internally for atomic compound assignment). */ { 0, CODE_FOR_fnstenv, "__builtin_ia32_fnstenv", IX86_BUILTIN_FNSTENV, UNKNOWN, (int) VOID_FTYPE_PVOID }, --- 32730,32738 ---- /* Special builtins with variable number of arguments. */ static const struct builtin_description bdesc_special_args[] = { ! { 0, CODE_FOR_nothing, "__builtin_ia32_rdtsc", IX86_BUILTIN_RDTSC, UNKNOWN, (int) UINT64_FTYPE_VOID }, ! { 0, CODE_FOR_nothing, "__builtin_ia32_rdtscp", IX86_BUILTIN_RDTSCP, UNKNOWN, (int) UINT64_FTYPE_PUNSIGNED }, ! { 0, CODE_FOR_pause, "__builtin_ia32_pause", IX86_BUILTIN_PAUSE, UNKNOWN, (int) VOID_FTYPE_VOID }, /* 80387 (for use internally for atomic compound assignment). */ { 0, CODE_FOR_fnstenv, "__builtin_ia32_fnstenv", IX86_BUILTIN_FNSTENV, UNKNOWN, (int) VOID_FTYPE_PVOID }, *************** static const struct builtin_description *** 33012,33024 **** /* Builtins with variable number of arguments. */ static const struct builtin_description bdesc_args[] = { ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_bsr, "__builtin_ia32_bsrsi", IX86_BUILTIN_BSRSI, UNKNOWN, (int) INT_FTYPE_INT }, { OPTION_MASK_ISA_64BIT, CODE_FOR_bsr_rex64, "__builtin_ia32_bsrdi", IX86_BUILTIN_BSRDI, UNKNOWN, (int) INT64_FTYPE_INT64 }, ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_nothing, "__builtin_ia32_rdpmc", IX86_BUILTIN_RDPMC, UNKNOWN, (int) UINT64_FTYPE_INT }, ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_rotlqi3, "__builtin_ia32_rolqi", IX86_BUILTIN_ROLQI, UNKNOWN, (int) UINT8_FTYPE_UINT8_INT }, ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_rotlhi3, "__builtin_ia32_rolhi", IX86_BUILTIN_ROLHI, UNKNOWN, (int) UINT16_FTYPE_UINT16_INT }, ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_rotrqi3, "__builtin_ia32_rorqi", IX86_BUILTIN_RORQI, UNKNOWN, (int) UINT8_FTYPE_UINT8_INT }, ! { ~OPTION_MASK_ISA_64BIT, CODE_FOR_rotrhi3, "__builtin_ia32_rorhi", IX86_BUILTIN_RORHI, UNKNOWN, (int) UINT16_FTYPE_UINT16_INT }, /* MMX */ { OPTION_MASK_ISA_MMX, CODE_FOR_mmx_addv8qi3, "__builtin_ia32_paddb", IX86_BUILTIN_PADDB, UNKNOWN, (int) V8QI_FTYPE_V8QI_V8QI }, --- 33027,33039 ---- /* Builtins with variable number of arguments. */ static const struct builtin_description bdesc_args[] = { ! { 0, CODE_FOR_bsr, "__builtin_ia32_bsrsi", IX86_BUILTIN_BSRSI, UNKNOWN, (int) INT_FTYPE_INT }, { OPTION_MASK_ISA_64BIT, CODE_FOR_bsr_rex64, "__builtin_ia32_bsrdi", IX86_BUILTIN_BSRDI, UNKNOWN, (int) INT64_FTYPE_INT64 }, ! { 0, CODE_FOR_nothing, "__builtin_ia32_rdpmc", IX86_BUILTIN_RDPMC, UNKNOWN, (int) UINT64_FTYPE_INT }, ! { 0, CODE_FOR_rotlqi3, "__builtin_ia32_rolqi", IX86_BUILTIN_ROLQI, UNKNOWN, (int) UINT8_FTYPE_UINT8_INT }, ! { 0, CODE_FOR_rotlhi3, "__builtin_ia32_rolhi", IX86_BUILTIN_ROLHI, UNKNOWN, (int) UINT16_FTYPE_UINT16_INT }, ! { 0, CODE_FOR_rotrqi3, "__builtin_ia32_rorqi", IX86_BUILTIN_RORQI, UNKNOWN, (int) UINT8_FTYPE_UINT8_INT }, ! { 0, CODE_FOR_rotrhi3, "__builtin_ia32_rorhi", IX86_BUILTIN_RORHI, UNKNOWN, (int) UINT16_FTYPE_UINT16_INT }, /* MMX */ { OPTION_MASK_ISA_MMX, CODE_FOR_mmx_addv8qi3, "__builtin_ia32_paddb", IX86_BUILTIN_PADDB, UNKNOWN, (int) V8QI_FTYPE_V8QI_V8QI }, *************** ix86_init_mmx_sse_builtins (void) *** 35719,35753 **** /* AVX512F */ def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv16sf", ! V16SF_FTYPE_V16SF_PCFLOAT_V16SI_HI_INT, IX86_BUILTIN_GATHER3SIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv8df", ! V8DF_FTYPE_V8DF_PCDOUBLE_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv16sf", ! V8SF_FTYPE_V8SF_PCFLOAT_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv8df", ! V8DF_FTYPE_V8DF_PCDOUBLE_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv16si", ! V16SI_FTYPE_V16SI_PCINT_V16SI_HI_INT, IX86_BUILTIN_GATHER3SIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv8di", ! V8DI_FTYPE_V8DI_PCINT64_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv16si", ! V8SI_FTYPE_V8SI_PCINT_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv8di", ! V8DI_FTYPE_V8DI_PCINT64_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV8DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatheraltsiv8df ", --- 35734,35768 ---- /* AVX512F */ def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv16sf", ! V16SF_FTYPE_V16SF_PCVOID_V16SI_HI_INT, IX86_BUILTIN_GATHER3SIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv8df", ! V8DF_FTYPE_V8DF_PCVOID_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv16sf", ! V8SF_FTYPE_V8SF_PCVOID_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv8df", ! V8DF_FTYPE_V8DF_PCVOID_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv16si", ! V16SI_FTYPE_V16SI_PCVOID_V16SI_HI_INT, IX86_BUILTIN_GATHER3SIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gathersiv8di", ! V8DI_FTYPE_V8DI_PCVOID_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv16si", ! V8SI_FTYPE_V8SI_PCVOID_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatherdiv8di", ! V8DI_FTYPE_V8DI_PCVOID_V8DI_QI_INT, IX86_BUILTIN_GATHER3DIV8DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_gatheraltsiv8df ", *************** ix86_init_mmx_sse_builtins (void) *** 35767,35866 **** IX86_BUILTIN_GATHER3ALTDIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv16sf", ! VOID_FTYPE_PFLOAT_HI_V16SI_V16SF_INT, IX86_BUILTIN_SCATTERSIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv8df", ! VOID_FTYPE_PDOUBLE_QI_V8SI_V8DF_INT, IX86_BUILTIN_SCATTERSIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv16sf", ! VOID_FTYPE_PFLOAT_QI_V8DI_V8SF_INT, IX86_BUILTIN_SCATTERDIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv8df", ! VOID_FTYPE_PDOUBLE_QI_V8DI_V8DF_INT, IX86_BUILTIN_SCATTERDIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv16si", ! VOID_FTYPE_PINT_HI_V16SI_V16SI_INT, IX86_BUILTIN_SCATTERSIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv8di", ! VOID_FTYPE_PLONGLONG_QI_V8SI_V8DI_INT, IX86_BUILTIN_SCATTERSIV8DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv16si", ! VOID_FTYPE_PINT_QI_V8DI_V8SI_INT, IX86_BUILTIN_SCATTERDIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv8di", ! VOID_FTYPE_PLONGLONG_QI_V8DI_V8DI_INT, IX86_BUILTIN_SCATTERDIV8DI); /* AVX512VL */ def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv2df", ! V2DF_FTYPE_V2DF_PCDOUBLE_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4df", ! V4DF_FTYPE_V4DF_PCDOUBLE_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div2df", ! V2DF_FTYPE_V2DF_PCDOUBLE_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4df", ! V4DF_FTYPE_V4DF_PCDOUBLE_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4sf", ! V4SF_FTYPE_V4SF_PCFLOAT_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv8sf", ! V8SF_FTYPE_V8SF_PCFLOAT_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4sf", ! V4SF_FTYPE_V4SF_PCFLOAT_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div8sf", ! V4SF_FTYPE_V4SF_PCFLOAT_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv2di", ! V2DI_FTYPE_V2DI_PCINT64_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV2DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4di", ! V4DI_FTYPE_V4DI_PCINT64_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div2di", ! V2DI_FTYPE_V2DI_PCINT64_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV2DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4di", ! V4DI_FTYPE_V4DI_PCINT64_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4si", ! V4SI_FTYPE_V4SI_PCINT_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv8si", ! V8SI_FTYPE_V8SI_PCINT_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4si", ! V4SI_FTYPE_V4SI_PCINT_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div8si", ! V4SI_FTYPE_V4SI_PCINT_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3altsiv4df ", --- 35782,35881 ---- IX86_BUILTIN_GATHER3ALTDIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv16sf", ! VOID_FTYPE_PVOID_HI_V16SI_V16SF_INT, IX86_BUILTIN_SCATTERSIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv8df", ! VOID_FTYPE_PVOID_QI_V8SI_V8DF_INT, IX86_BUILTIN_SCATTERSIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv16sf", ! VOID_FTYPE_PVOID_QI_V8DI_V8SF_INT, IX86_BUILTIN_SCATTERDIV16SF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv8df", ! VOID_FTYPE_PVOID_QI_V8DI_V8DF_INT, IX86_BUILTIN_SCATTERDIV8DF); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv16si", ! VOID_FTYPE_PVOID_HI_V16SI_V16SI_INT, IX86_BUILTIN_SCATTERSIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scattersiv8di", ! VOID_FTYPE_PVOID_QI_V8SI_V8DI_INT, IX86_BUILTIN_SCATTERSIV8DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv16si", ! VOID_FTYPE_PVOID_QI_V8DI_V8SI_INT, IX86_BUILTIN_SCATTERDIV16SI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatterdiv8di", ! VOID_FTYPE_PVOID_QI_V8DI_V8DI_INT, IX86_BUILTIN_SCATTERDIV8DI); /* AVX512VL */ def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv2df", ! V2DF_FTYPE_V2DF_PCVOID_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4df", ! V4DF_FTYPE_V4DF_PCVOID_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div2df", ! V2DF_FTYPE_V2DF_PCVOID_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4df", ! V4DF_FTYPE_V4DF_PCVOID_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4sf", ! V4SF_FTYPE_V4SF_PCVOID_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv8sf", ! V8SF_FTYPE_V8SF_PCVOID_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4sf", ! V4SF_FTYPE_V4SF_PCVOID_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div8sf", ! V4SF_FTYPE_V4SF_PCVOID_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv2di", ! V2DI_FTYPE_V2DI_PCVOID_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV2DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4di", ! V4DI_FTYPE_V4DI_PCVOID_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div2di", ! V2DI_FTYPE_V2DI_PCVOID_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV2DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4di", ! V4DI_FTYPE_V4DI_PCVOID_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv4si", ! V4SI_FTYPE_V4SI_PCVOID_V4SI_QI_INT, IX86_BUILTIN_GATHER3SIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3siv8si", ! V8SI_FTYPE_V8SI_PCVOID_V8SI_QI_INT, IX86_BUILTIN_GATHER3SIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div4si", ! V4SI_FTYPE_V4SI_PCVOID_V2DI_QI_INT, IX86_BUILTIN_GATHER3DIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3div8si", ! V4SI_FTYPE_V4SI_PCVOID_V4DI_QI_INT, IX86_BUILTIN_GATHER3DIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_gather3altsiv4df ", *************** ix86_init_mmx_sse_builtins (void) *** 35880,35946 **** IX86_BUILTIN_GATHER3ALTDIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv8sf", ! VOID_FTYPE_PFLOAT_QI_V8SI_V8SF_INT, IX86_BUILTIN_SCATTERSIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4sf", ! VOID_FTYPE_PFLOAT_QI_V4SI_V4SF_INT, IX86_BUILTIN_SCATTERSIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4df", ! VOID_FTYPE_PDOUBLE_QI_V4SI_V4DF_INT, IX86_BUILTIN_SCATTERSIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv2df", ! VOID_FTYPE_PDOUBLE_QI_V4SI_V2DF_INT, IX86_BUILTIN_SCATTERSIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv8sf", ! VOID_FTYPE_PFLOAT_QI_V4DI_V4SF_INT, IX86_BUILTIN_SCATTERDIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4sf", ! VOID_FTYPE_PFLOAT_QI_V2DI_V4SF_INT, IX86_BUILTIN_SCATTERDIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4df", ! VOID_FTYPE_PDOUBLE_QI_V4DI_V4DF_INT, IX86_BUILTIN_SCATTERDIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv2df", ! VOID_FTYPE_PDOUBLE_QI_V2DI_V2DF_INT, IX86_BUILTIN_SCATTERDIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv8si", ! VOID_FTYPE_PINT_QI_V8SI_V8SI_INT, IX86_BUILTIN_SCATTERSIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4si", ! VOID_FTYPE_PINT_QI_V4SI_V4SI_INT, IX86_BUILTIN_SCATTERSIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4di", ! VOID_FTYPE_PLONGLONG_QI_V4SI_V4DI_INT, IX86_BUILTIN_SCATTERSIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv2di", ! VOID_FTYPE_PLONGLONG_QI_V4SI_V2DI_INT, IX86_BUILTIN_SCATTERSIV2DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv8si", ! VOID_FTYPE_PINT_QI_V4DI_V4SI_INT, IX86_BUILTIN_SCATTERDIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4si", ! VOID_FTYPE_PINT_QI_V2DI_V4SI_INT, IX86_BUILTIN_SCATTERDIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4di", ! VOID_FTYPE_PLONGLONG_QI_V4DI_V4DI_INT, IX86_BUILTIN_SCATTERDIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv2di", ! VOID_FTYPE_PLONGLONG_QI_V2DI_V2DI_INT, IX86_BUILTIN_SCATTERDIV2DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatteraltsiv8df ", VOID_FTYPE_PDOUBLE_QI_V16SI_V8DF_INT, --- 35895,35961 ---- IX86_BUILTIN_GATHER3ALTDIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv8sf", ! VOID_FTYPE_PVOID_QI_V8SI_V8SF_INT, IX86_BUILTIN_SCATTERSIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4sf", ! VOID_FTYPE_PVOID_QI_V4SI_V4SF_INT, IX86_BUILTIN_SCATTERSIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4df", ! VOID_FTYPE_PVOID_QI_V4SI_V4DF_INT, IX86_BUILTIN_SCATTERSIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv2df", ! VOID_FTYPE_PVOID_QI_V4SI_V2DF_INT, IX86_BUILTIN_SCATTERSIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv8sf", ! VOID_FTYPE_PVOID_QI_V4DI_V4SF_INT, IX86_BUILTIN_SCATTERDIV8SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4sf", ! VOID_FTYPE_PVOID_QI_V2DI_V4SF_INT, IX86_BUILTIN_SCATTERDIV4SF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4df", ! VOID_FTYPE_PVOID_QI_V4DI_V4DF_INT, IX86_BUILTIN_SCATTERDIV4DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv2df", ! VOID_FTYPE_PVOID_QI_V2DI_V2DF_INT, IX86_BUILTIN_SCATTERDIV2DF); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv8si", ! VOID_FTYPE_PVOID_QI_V8SI_V8SI_INT, IX86_BUILTIN_SCATTERSIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4si", ! VOID_FTYPE_PVOID_QI_V4SI_V4SI_INT, IX86_BUILTIN_SCATTERSIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv4di", ! VOID_FTYPE_PVOID_QI_V4SI_V4DI_INT, IX86_BUILTIN_SCATTERSIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scattersiv2di", ! VOID_FTYPE_PVOID_QI_V4SI_V2DI_INT, IX86_BUILTIN_SCATTERSIV2DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv8si", ! VOID_FTYPE_PVOID_QI_V4DI_V4SI_INT, IX86_BUILTIN_SCATTERDIV8SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4si", ! VOID_FTYPE_PVOID_QI_V2DI_V4SI_INT, IX86_BUILTIN_SCATTERDIV4SI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv4di", ! VOID_FTYPE_PVOID_QI_V4DI_V4DI_INT, IX86_BUILTIN_SCATTERDIV4DI); def_builtin (OPTION_MASK_ISA_AVX512VL, "__builtin_ia32_scatterdiv2di", ! VOID_FTYPE_PVOID_QI_V2DI_V2DI_INT, IX86_BUILTIN_SCATTERDIV2DI); def_builtin (OPTION_MASK_ISA_AVX512F, "__builtin_ia32_scatteraltsiv8df ", VOID_FTYPE_PDOUBLE_QI_V16SI_V8DF_INT, *************** ix86_init_mmx_sse_builtins (void) *** 35960,35987 **** /* AVX512PF */ def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfdpd", ! VOID_FTYPE_QI_V8SI_PCINT64_INT_INT, IX86_BUILTIN_GATHERPFDPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfdps", ! VOID_FTYPE_HI_V16SI_PCINT_INT_INT, IX86_BUILTIN_GATHERPFDPS); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfqpd", ! VOID_FTYPE_QI_V8DI_PCINT64_INT_INT, IX86_BUILTIN_GATHERPFQPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfqps", ! VOID_FTYPE_QI_V8DI_PCINT_INT_INT, IX86_BUILTIN_GATHERPFQPS); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfdpd", ! VOID_FTYPE_QI_V8SI_PCINT64_INT_INT, IX86_BUILTIN_SCATTERPFDPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfdps", ! VOID_FTYPE_HI_V16SI_PCINT_INT_INT, IX86_BUILTIN_SCATTERPFDPS); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfqpd", ! VOID_FTYPE_QI_V8DI_PCINT64_INT_INT, IX86_BUILTIN_SCATTERPFQPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfqps", ! VOID_FTYPE_QI_V8DI_PCINT_INT_INT, IX86_BUILTIN_SCATTERPFQPS); /* SHA */ --- 35975,36002 ---- /* AVX512PF */ def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfdpd", ! VOID_FTYPE_QI_V8SI_PCVOID_INT_INT, IX86_BUILTIN_GATHERPFDPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfdps", ! VOID_FTYPE_HI_V16SI_PCVOID_INT_INT, IX86_BUILTIN_GATHERPFDPS); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfqpd", ! VOID_FTYPE_QI_V8DI_PCVOID_INT_INT, IX86_BUILTIN_GATHERPFQPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_gatherpfqps", ! VOID_FTYPE_QI_V8DI_PCVOID_INT_INT, IX86_BUILTIN_GATHERPFQPS); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfdpd", ! VOID_FTYPE_QI_V8SI_PCVOID_INT_INT, IX86_BUILTIN_SCATTERPFDPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfdps", ! VOID_FTYPE_HI_V16SI_PCVOID_INT_INT, IX86_BUILTIN_SCATTERPFDPS); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfqpd", ! VOID_FTYPE_QI_V8DI_PCVOID_INT_INT, IX86_BUILTIN_SCATTERPFQPD); def_builtin (OPTION_MASK_ISA_AVX512PF, "__builtin_ia32_scatterpfqps", ! VOID_FTYPE_QI_V8DI_PCVOID_INT_INT, IX86_BUILTIN_SCATTERPFQPS); /* SHA */ *************** ix86_init_mmx_sse_builtins (void) *** 36085,36095 **** IX86_BUILTIN_SBB64); /* Read/write FLAGS. */ ! def_builtin (~OPTION_MASK_ISA_64BIT, "__builtin_ia32_readeflags_u32", UNSIGNED_FTYPE_VOID, IX86_BUILTIN_READ_FLAGS); def_builtin (OPTION_MASK_ISA_64BIT, "__builtin_ia32_readeflags_u64", UINT64_FTYPE_VOID, IX86_BUILTIN_READ_FLAGS); ! def_builtin (~OPTION_MASK_ISA_64BIT, "__builtin_ia32_writeeflags_u32", VOID_FTYPE_UNSIGNED, IX86_BUILTIN_WRITE_FLAGS); def_builtin (OPTION_MASK_ISA_64BIT, "__builtin_ia32_writeeflags_u64", VOID_FTYPE_UINT64, IX86_BUILTIN_WRITE_FLAGS); --- 36100,36110 ---- IX86_BUILTIN_SBB64); /* Read/write FLAGS. */ ! def_builtin (0, "__builtin_ia32_readeflags_u32", UNSIGNED_FTYPE_VOID, IX86_BUILTIN_READ_FLAGS); def_builtin (OPTION_MASK_ISA_64BIT, "__builtin_ia32_readeflags_u64", UINT64_FTYPE_VOID, IX86_BUILTIN_READ_FLAGS); ! def_builtin (0, "__builtin_ia32_writeeflags_u32", VOID_FTYPE_UNSIGNED, IX86_BUILTIN_WRITE_FLAGS); def_builtin (OPTION_MASK_ISA_64BIT, "__builtin_ia32_writeeflags_u64", VOID_FTYPE_UINT64, IX86_BUILTIN_WRITE_FLAGS); *************** ix86_expand_multi_arg_builtin (enum insn *** 38062,38067 **** --- 38077,38084 ---- || GET_MODE (target) != tmode || !insn_data[icode].operand[0].predicate (target, tmode)) target = gen_reg_rtx (tmode); + else if (memory_operand (target, tmode)) + num_memory++; gcc_assert (nargs <= 4); *************** ix86_expand_args_builtin (const struct b *** 39336,39341 **** --- 39353,39360 ---- || GET_MODE (target) != tmode || !insn_p->operand[0].predicate (target, tmode)) target = gen_reg_rtx (tmode); + else if (memory_operand (target, tmode)) + num_memory++; real_target = target; } else *************** ix86_expand_args_builtin (const struct b *** 39355,39364 **** { /* SIMD shift insns take either an 8-bit immediate or register as count. But builtin functions take int as ! count. If count doesn't match, we put it in register. */ if (!match) { ! op = simplify_gen_subreg (SImode, op, GET_MODE (op), 0); if (!insn_p->operand[i + 1].predicate (op, mode)) op = copy_to_reg (op); } --- 39374,39390 ---- { /* SIMD shift insns take either an 8-bit immediate or register as count. But builtin functions take int as ! count. If count doesn't match, we put it in register. ! The instructions are using 64-bit count, if op is just ! 32-bit, zero-extend it, as negative shift counts ! are undefined behavior and zero-extension is more ! efficient. */ if (!match) { ! if (SCALAR_INT_MODE_P (GET_MODE (op))) ! op = convert_modes (mode, GET_MODE (op), op, 1); ! else ! op = simplify_gen_subreg (mode, op, GET_MODE (op), 0); if (!insn_p->operand[i + 1].predicate (op, mode)) op = copy_to_reg (op); } *************** ix86_expand_builtin (tree exp, rtx targe *** 40518,40526 **** Originally the builtin was not created if it wasn't applicable to the current ISA based on the command line switches. With function specific options, we need to check in the context of the function making the call ! whether it is supported. */ ! if (ix86_builtins_isa[fcode].isa ! && !(ix86_builtins_isa[fcode].isa & ix86_isa_flags)) { char *opts = ix86_target_string (ix86_builtins_isa[fcode].isa, 0, NULL, NULL, (enum fpmath_unit) 0, false); --- 40544,40561 ---- Originally the builtin was not created if it wasn't applicable to the current ISA based on the command line switches. With function specific options, we need to check in the context of the function making the call ! whether it is supported. Treat AVX512VL specially. For other flags, ! if isa includes more than one ISA bit, treat those are requiring any ! of them. For AVX512VL, require both AVX512VL and the non-AVX512VL ! ISAs. Similarly for 64BIT, but we shouldn't be building such builtins ! at all, -m64 is a whole TU option. */ ! if (((ix86_builtins_isa[fcode].isa ! & ~(OPTION_MASK_ISA_AVX512VL | OPTION_MASK_ISA_64BIT)) ! && !(ix86_builtins_isa[fcode].isa ! & ~(OPTION_MASK_ISA_AVX512VL | OPTION_MASK_ISA_64BIT) ! & ix86_isa_flags)) ! || ((ix86_builtins_isa[fcode].isa & OPTION_MASK_ISA_AVX512VL) ! && !(ix86_isa_flags & OPTION_MASK_ISA_AVX512VL))) { char *opts = ix86_target_string (ix86_builtins_isa[fcode].isa, 0, NULL, NULL, (enum fpmath_unit) 0, false); *************** ix86_expand_builtin (tree exp, rtx targe *** 41322,41330 **** mode0 = DImode; rdrand_step: - op0 = gen_reg_rtx (mode0); - emit_insn (GEN_FCN (icode) (op0)); - arg0 = CALL_EXPR_ARG (exp, 0); op1 = expand_normal (arg0); if (!address_operand (op1, VOIDmode)) --- 41357,41362 ---- *************** rdrand_step: *** 41332,41337 **** --- 41364,41373 ---- op1 = convert_memory_address (Pmode, op1); op1 = copy_addr_to_reg (op1); } + + op0 = gen_reg_rtx (mode0); + emit_insn (GEN_FCN (icode) (op0)); + emit_move_insn (gen_rtx_MEM (mode0, op1), op0); op1 = gen_reg_rtx (SImode); *************** rdrand_step: *** 41340,41347 **** /* Emit SImode conditional move. */ if (mode0 == HImode) { ! op2 = gen_reg_rtx (SImode); ! emit_insn (gen_zero_extendhisi2 (op2, op0)); } else if (mode0 == SImode) op2 = op0; --- 41376,41395 ---- /* Emit SImode conditional move. */ if (mode0 == HImode) { ! if (TARGET_ZERO_EXTEND_WITH_AND ! && optimize_function_for_speed_p (cfun)) ! { ! op2 = force_reg (SImode, const0_rtx); ! ! emit_insn (gen_movstricthi ! (gen_lowpart (HImode, op2), op0)); ! } ! else ! { ! op2 = gen_reg_rtx (SImode); ! ! emit_insn (gen_zero_extendhisi2 (op2, op0)); ! } } else if (mode0 == SImode) op2 = op0; *************** rdrand_step: *** 41373,41381 **** mode0 = DImode; rdseed_step: - op0 = gen_reg_rtx (mode0); - emit_insn (GEN_FCN (icode) (op0)); - arg0 = CALL_EXPR_ARG (exp, 0); op1 = expand_normal (arg0); if (!address_operand (op1, VOIDmode)) --- 41421,41426 ---- *************** rdseed_step: *** 41383,41388 **** --- 41428,41437 ---- op1 = convert_memory_address (Pmode, op1); op1 = copy_addr_to_reg (op1); } + + op0 = gen_reg_rtx (mode0); + emit_insn (GEN_FCN (icode) (op0)); + emit_move_insn (gen_rtx_MEM (mode0, op1), op0); op2 = gen_reg_rtx (QImode); *************** rdseed_step: *** 41488,41501 **** case IX86_BUILTIN_KORTESTC16: icode = CODE_FOR_kortestchi; ! mode0 = HImode; ! mode1 = CCCmode; goto kortest; case IX86_BUILTIN_KORTESTZ16: icode = CODE_FOR_kortestzhi; ! mode0 = HImode; ! mode1 = CCZmode; kortest: arg0 = CALL_EXPR_ARG (exp, 0); /* Mask reg src1. */ --- 41537,41548 ---- case IX86_BUILTIN_KORTESTC16: icode = CODE_FOR_kortestchi; ! mode3 = CCCmode; goto kortest; case IX86_BUILTIN_KORTESTZ16: icode = CODE_FOR_kortestzhi; ! mode3 = CCZmode; kortest: arg0 = CALL_EXPR_ARG (exp, 0); /* Mask reg src1. */ *************** rdseed_step: *** 41503,41521 **** op0 = expand_normal (arg0); op1 = expand_normal (arg1); ! op0 = copy_to_reg (op0); ! op0 = simplify_gen_subreg (mode0, op0, GET_MODE (op0), 0); ! op1 = copy_to_reg (op1); ! op1 = simplify_gen_subreg (mode0, op1, GET_MODE (op1), 0); target = gen_reg_rtx (QImode); - emit_insn (gen_rtx_SET (target, const0_rtx)); /* Emit kortest. */ emit_insn (GEN_FCN (icode) (op0, op1)); /* And use setcc to return result from flags. */ ix86_expand_setcc (target, EQ, ! gen_rtx_REG (mode1, FLAGS_REG), const0_rtx); return target; case IX86_BUILTIN_GATHERSIV2DF: --- 41550,41581 ---- op0 = expand_normal (arg0); op1 = expand_normal (arg1); ! mode0 = insn_data[icode].operand[0].mode; ! mode1 = insn_data[icode].operand[1].mode; ! ! if (GET_MODE (op0) != VOIDmode) ! op0 = force_reg (GET_MODE (op0), op0); ! ! op0 = gen_lowpart (mode0, op0); ! ! if (!insn_data[icode].operand[0].predicate (op0, mode0)) ! op0 = copy_to_mode_reg (mode0, op0); ! ! if (GET_MODE (op1) != VOIDmode) ! op1 = force_reg (GET_MODE (op1), op1); ! ! op1 = gen_lowpart (mode1, op1); ! ! if (!insn_data[icode].operand[1].predicate (op1, mode1)) ! op1 = copy_to_mode_reg (mode1, op1); target = gen_reg_rtx (QImode); /* Emit kortest. */ emit_insn (GEN_FCN (icode) (op0, op1)); /* And use setcc to return result from flags. */ ix86_expand_setcc (target, EQ, ! gen_rtx_REG (mode3, FLAGS_REG), const0_rtx); return target; case IX86_BUILTIN_GATHERSIV2DF: *************** ix86_vector_duplicate_value (machine_mod *** 45938,45947 **** if (recog_memoized (insn) < 0) { rtx_insn *seq; /* If that fails, force VAL into a register. */ start_sequence (); ! XEXP (dup, 0) = force_reg (GET_MODE_INNER (mode), val); seq = get_insns (); end_sequence (); if (seq) --- 45998,46013 ---- if (recog_memoized (insn) < 0) { rtx_insn *seq; + machine_mode innermode = GET_MODE_INNER (mode); + rtx reg; + /* If that fails, force VAL into a register. */ start_sequence (); ! reg = force_reg (innermode, val); ! if (GET_MODE (reg) != innermode) ! reg = gen_lowpart (innermode, reg); ! XEXP (dup, 0) = reg; seq = get_insns (); end_sequence (); if (seq) diff -Nrcpad gcc-6.3.0/gcc/config/i386/i386.md gcc-6.4.0/gcc/config/i386/i386.md *** gcc-6.3.0/gcc/config/i386/i386.md Wed Nov 23 20:58:46 2016 --- gcc-6.4.0/gcc/config/i386/i386.md Fri Mar 3 09:34:14 2017 *************** *** 2938,2943 **** --- 2938,2973 ---- operands[0] = replace_equiv_address (operands[0], stack_pointer_rtx); }) + (define_insn_and_split "*pushxf_rounded" + [(set (mem:XF + (pre_modify:P + (reg:P SP_REG) + (plus:P (reg:P SP_REG) (const_int -16)))) + (match_operand:XF 0 "nonmemory_no_elim_operand" "f,r,*r,C"))] + "TARGET_64BIT" + "#" + "&& 1" + [(set (reg:P SP_REG) (plus:P (reg:P SP_REG) (const_int -16))) + (set (match_dup 1) (match_dup 0))] + { + rtx pat = PATTERN (curr_insn); + operands[1] = SET_DEST (pat); + + /* Preserve memory attributes. */ + operands[1] = replace_equiv_address (operands[1], stack_pointer_rtx); + } + [(set_attr "type" "multi") + (set_attr "unit" "i387,*,*,*") + (set (attr "mode") + (cond [(eq_attr "alternative" "1,2,3") + (const_string "DI") + ] + (const_string "XF"))) + (set (attr "preferred_for_size") + (cond [(eq_attr "alternative" "1") + (symbol_ref "false")] + (symbol_ref "true")))]) + (define_insn "*pushxf" [(set (match_operand:XF 0 "push_operand" "=<,<,<,<") (match_operand:XF 1 "general_no_elim_operand" "f,r,*r,oF"))] *************** *** 3172,3180 **** ;; in alternatives 4, 6, 7 and 8. (define_insn "*movxf_internal" [(set (match_operand:XF 0 "nonimmediate_operand" ! "=f,m,f,?r ,!o,?*r ,!o,!o,!o,r ,o") (match_operand:XF 1 "general_operand" ! "fm,f,G,roF,r , *roF,*r,F ,C,roF,rF"))] "!(MEM_P (operands[0]) && MEM_P (operands[1])) && (lra_in_progress || reload_completed || (ix86_cmodel == CM_MEDIUM || ix86_cmodel == CM_LARGE) --- 3202,3210 ---- ;; in alternatives 4, 6, 7 and 8. (define_insn "*movxf_internal" [(set (match_operand:XF 0 "nonimmediate_operand" ! "=f,m,f,?r ,!o,?*r ,!o,!o,!o,r ,o ,o") (match_operand:XF 1 "general_operand" ! "fm,f,G,roF,r ,*roF,*r,F ,C ,roF,rF,rC"))] "!(MEM_P (operands[0]) && MEM_P (operands[1])) && (lra_in_progress || reload_completed || (ix86_cmodel == CM_MEDIUM || ix86_cmodel == CM_LARGE) *************** *** 3201,3219 **** } } [(set (attr "isa") ! (cond [(eq_attr "alternative" "7") (const_string "nox64") ! (eq_attr "alternative" "8") (const_string "x64") ] (const_string "*"))) (set (attr "type") ! (cond [(eq_attr "alternative" "3,4,5,6,7,8,9,10") (const_string "multi") ] (const_string "fmov"))) (set (attr "mode") ! (cond [(eq_attr "alternative" "3,4,5,6,7,8,9,10") (if_then_else (match_test "TARGET_64BIT") (const_string "DI") (const_string "SI")) --- 3231,3249 ---- } } [(set (attr "isa") ! (cond [(eq_attr "alternative" "7,10") (const_string "nox64") ! (eq_attr "alternative" "8,11") (const_string "x64") ] (const_string "*"))) (set (attr "type") ! (cond [(eq_attr "alternative" "3,4,5,6,7,8,9,10,11") (const_string "multi") ] (const_string "fmov"))) (set (attr "mode") ! (cond [(eq_attr "alternative" "3,4,5,6,7,8,9,10,11") (if_then_else (match_test "TARGET_64BIT") (const_string "DI") (const_string "SI")) *************** *** 3224,3230 **** (symbol_ref "false")] (symbol_ref "true"))) (set (attr "enabled") ! (cond [(eq_attr "alternative" "9,10") (if_then_else (match_test "TARGET_HARD_XF_REGS") (symbol_ref "false") --- 3254,3260 ---- (symbol_ref "false")] (symbol_ref "true"))) (set (attr "enabled") ! (cond [(eq_attr "alternative" "9,10,11") (if_then_else (match_test "TARGET_HARD_XF_REGS") (symbol_ref "false") diff -Nrcpad gcc-6.3.0/gcc/config/i386/ia32intrin.h gcc-6.4.0/gcc/config/i386/ia32intrin.h *** gcc-6.3.0/gcc/config/i386/ia32intrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/ia32intrin.h Thu Jun 1 19:38:29 2017 *************** __readeflags (void) *** 261,269 **** /* Write flags register */ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __writeeflags (unsigned long long X) { ! __builtin_ia32_writeeflags_u64 (X); } #define _bswap64(a) __bswapq(a) --- 261,269 ---- /* Write flags register */ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __writeeflags (unsigned long long __X) { ! __builtin_ia32_writeeflags_u64 (__X); } #define _bswap64(a) __bswapq(a) *************** __readeflags (void) *** 281,289 **** /* Write flags register */ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __writeeflags (unsigned int X) { ! __builtin_ia32_writeeflags_u32 (X); } #endif --- 281,289 ---- /* Write flags register */ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __writeeflags (unsigned int __X) { ! __builtin_ia32_writeeflags_u32 (__X); } #endif diff -Nrcpad gcc-6.3.0/gcc/config/i386/lwpintrin.h gcc-6.4.0/gcc/config/i386/lwpintrin.h *** gcc-6.3.0/gcc/config/i386/lwpintrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/lwpintrin.h Thu Jun 1 19:38:29 2017 *************** *** 35,43 **** #endif /* __LWP__ */ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __llwpcb (void *pcbAddress) { ! __builtin_ia32_llwpcb (pcbAddress); } extern __inline void * __attribute__((__gnu_inline__, __always_inline__, __artificial__)) --- 35,43 ---- #endif /* __LWP__ */ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __llwpcb (void *__pcbAddress) { ! __builtin_ia32_llwpcb (__pcbAddress); } extern __inline void * __attribute__((__gnu_inline__, __always_inline__, __artificial__)) *************** __slwpcb (void) *** 48,63 **** #ifdef __OPTIMIZE__ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpval32 (unsigned int data2, unsigned int data1, unsigned int flags) { ! __builtin_ia32_lwpval32 (data2, data1, flags); } #ifdef __x86_64__ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpval64 (unsigned long long data2, unsigned int data1, unsigned int flags) { ! __builtin_ia32_lwpval64 (data2, data1, flags); } #endif #else --- 48,64 ---- #ifdef __OPTIMIZE__ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpval32 (unsigned int __data2, unsigned int __data1, unsigned int __flags) { ! __builtin_ia32_lwpval32 (__data2, __data1, __flags); } #ifdef __x86_64__ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpval64 (unsigned long long __data2, unsigned int __data1, ! unsigned int __flags) { ! __builtin_ia32_lwpval64 (__data2, __data1, __flags); } #endif #else *************** __lwpval64 (unsigned long long data2, un *** 74,89 **** #ifdef __OPTIMIZE__ extern __inline unsigned char __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpins32 (unsigned int data2, unsigned int data1, unsigned int flags) { ! return __builtin_ia32_lwpins32 (data2, data1, flags); } #ifdef __x86_64__ extern __inline unsigned char __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpins64 (unsigned long long data2, unsigned int data1, unsigned int flags) { ! return __builtin_ia32_lwpins64 (data2, data1, flags); } #endif #else --- 75,91 ---- #ifdef __OPTIMIZE__ extern __inline unsigned char __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpins32 (unsigned int __data2, unsigned int __data1, unsigned int __flags) { ! return __builtin_ia32_lwpins32 (__data2, __data1, __flags); } #ifdef __x86_64__ extern __inline unsigned char __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! __lwpins64 (unsigned long long __data2, unsigned int __data1, ! unsigned int __flags) { ! return __builtin_ia32_lwpins64 (__data2, __data1, __flags); } #endif #else diff -Nrcpad gcc-6.3.0/gcc/config/i386/mm3dnow.h gcc-6.4.0/gcc/config/i386/mm3dnow.h *** gcc-6.3.0/gcc/config/i386/mm3dnow.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/mm3dnow.h Thu Apr 6 21:06:08 2017 *************** *** 30,38 **** #include #include ! #ifndef __3dNOW__ #pragma GCC push_options #pragma GCC target("3dnow") #define __DISABLE_3dNOW__ #endif /* __3dNOW__ */ --- 30,42 ---- #include #include ! #if defined __x86_64__ && !defined __SSE__ || !defined __3dNOW__ #pragma GCC push_options + #ifdef __x86_64__ + #pragma GCC target("sse,3dnow") + #else #pragma GCC target("3dnow") + #endif #define __DISABLE_3dNOW__ #endif /* __3dNOW__ */ diff -Nrcpad gcc-6.3.0/gcc/config/i386/mmintrin.h gcc-6.4.0/gcc/config/i386/mmintrin.h *** gcc-6.3.0/gcc/config/i386/mmintrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/mmintrin.h Thu Apr 6 21:06:08 2017 *************** *** 27,35 **** #ifndef _MMINTRIN_H_INCLUDED #define _MMINTRIN_H_INCLUDED ! #ifndef __MMX__ #pragma GCC push_options #pragma GCC target("mmx") #define __DISABLE_MMX__ #endif /* __MMX__ */ --- 27,39 ---- #ifndef _MMINTRIN_H_INCLUDED #define _MMINTRIN_H_INCLUDED ! #if defined __x86_64__ && !defined __SSE__ || !defined __MMX__ #pragma GCC push_options + #ifdef __x86_64__ + #pragma GCC target("sse,mmx") + #else #pragma GCC target("mmx") + #endif #define __DISABLE_MMX__ #endif /* __MMX__ */ *************** _m_paddd (__m64 __m1, __m64 __m2) *** 308,314 **** /* Add the 64-bit values in M1 to the 64-bit values in M2. */ #ifndef __SSE2__ #pragma GCC push_options ! #pragma GCC target("sse2") #define __DISABLE_SSE2__ #endif /* __SSE2__ */ --- 312,318 ---- /* Add the 64-bit values in M1 to the 64-bit values in M2. */ #ifndef __SSE2__ #pragma GCC push_options ! #pragma GCC target("sse2,mmx") #define __DISABLE_SSE2__ #endif /* __SSE2__ */ *************** _m_psubd (__m64 __m1, __m64 __m2) *** 420,426 **** /* Add the 64-bit values in M1 to the 64-bit values in M2. */ #ifndef __SSE2__ #pragma GCC push_options ! #pragma GCC target("sse2") #define __DISABLE_SSE2__ #endif /* __SSE2__ */ --- 424,430 ---- /* Add the 64-bit values in M1 to the 64-bit values in M2. */ #ifndef __SSE2__ #pragma GCC push_options ! #pragma GCC target("sse2,mmx") #define __DISABLE_SSE2__ #endif /* __SSE2__ */ diff -Nrcpad gcc-6.3.0/gcc/config/i386/mmx.md gcc-6.4.0/gcc/config/i386/mmx.md *** gcc-6.3.0/gcc/config/i386/mmx.md Mon Aug 22 20:42:03 2016 --- gcc-6.4.0/gcc/config/i386/mmx.md Fri May 19 15:51:10 2017 *************** *** 78,86 **** (define_insn "*mov_internal" [(set (match_operand:MMXMODE 0 "nonimmediate_operand" ! "=r ,o ,r,r ,m ,?!y,!y,?!y,m ,r ,?!Ym,v,v,v,m,*x,*x,*x,m ,r ,Yi,!Ym,*Yi") (match_operand:MMXMODE 1 "vector_move_operand" ! "rCo,rC,C,rm,rC,C ,!y,m ,?!y,?!Yn,r ,C,v,m,v,C ,*x,m ,*x,Yj,r ,*Yj,!Yn"))] "TARGET_MMX && !(MEM_P (operands[0]) && MEM_P (operands[1]))" { --- 78,86 ---- (define_insn "*mov_internal" [(set (match_operand:MMXMODE 0 "nonimmediate_operand" ! "=r ,o ,r,r ,m ,?!y,!y,?!y,m ,r ,?!Ym,v,v,v,m,r ,Yi,!Ym,*Yi") (match_operand:MMXMODE 1 "vector_move_operand" ! "rCo,rC,C,rm,rC,C ,!y,m ,?!y,?!Yn,r ,C,v,m,v,Yj,r ,*Yj,!Yn"))] "TARGET_MMX && !(MEM_P (operands[0]) && MEM_P (operands[1]))" { *************** *** 146,152 **** [(set (attr "isa") (cond [(eq_attr "alternative" "0,1") (const_string "nox64") ! (eq_attr "alternative" "2,3,4,9,10,11,12,13,14,19,20") (const_string "x64") ] (const_string "*"))) --- 146,152 ---- [(set (attr "isa") (cond [(eq_attr "alternative" "0,1") (const_string "nox64") ! (eq_attr "alternative" "2,3,4,9,10,15,16") (const_string "x64") ] (const_string "*"))) *************** *** 159,172 **** (const_string "mmx") (eq_attr "alternative" "6,7,8,9,10") (const_string "mmxmov") ! (eq_attr "alternative" "11,15") (const_string "sselog1") ! (eq_attr "alternative" "21,22") (const_string "ssecvt") ] (const_string "ssemov"))) (set (attr "prefix_rex") ! (if_then_else (eq_attr "alternative" "9,10,19,20") (const_string "1") (const_string "*"))) (set (attr "prefix") --- 159,172 ---- (const_string "mmx") (eq_attr "alternative" "6,7,8,9,10") (const_string "mmxmov") ! (eq_attr "alternative" "11") (const_string "sselog1") ! (eq_attr "alternative" "17,18") (const_string "ssecvt") ] (const_string "ssemov"))) (set (attr "prefix_rex") ! (if_then_else (eq_attr "alternative" "9,10,15,16") (const_string "1") (const_string "*"))) (set (attr "prefix") *************** *** 181,187 **** (set (attr "mode") (cond [(eq_attr "alternative" "2") (const_string "SI") ! (eq_attr "alternative" "11,12,15,16") (cond [(ior (match_operand 0 "ext_sse_reg_operand") (match_operand 1 "ext_sse_reg_operand")) (const_string "XI") --- 181,187 ---- (set (attr "mode") (cond [(eq_attr "alternative" "2") (const_string "SI") ! (eq_attr "alternative" "11,12") (cond [(ior (match_operand 0 "ext_sse_reg_operand") (match_operand 1 "ext_sse_reg_operand")) (const_string "XI") *************** *** 197,203 **** ] (const_string "TI")) ! (and (eq_attr "alternative" "13,14,17,18") (ior (match_test "mode == V2SFmode") (not (match_test "TARGET_SSE2")))) (const_string "V2SF") --- 197,203 ---- ] (const_string "TI")) ! (and (eq_attr "alternative" "13,14") (ior (match_test "mode == V2SFmode") (not (match_test "TARGET_SSE2")))) (const_string "V2SF") *************** *** 931,937 **** [(set (match_operand:MMXMODE24 0 "register_operand" "=y") (ashiftrt:MMXMODE24 (match_operand:MMXMODE24 1 "register_operand" "0") ! (match_operand:SI 2 "nonmemory_operand" "yN")))] "TARGET_MMX" "psra\t{%2, %0|%0, %2}" [(set_attr "type" "mmxshft") --- 931,937 ---- [(set (match_operand:MMXMODE24 0 "register_operand" "=y") (ashiftrt:MMXMODE24 (match_operand:MMXMODE24 1 "register_operand" "0") ! (match_operand:DI 2 "nonmemory_operand" "yN")))] "TARGET_MMX" "psra\t{%2, %0|%0, %2}" [(set_attr "type" "mmxshft") *************** *** 945,951 **** [(set (match_operand:MMXMODE248 0 "register_operand" "=y") (any_lshift:MMXMODE248 (match_operand:MMXMODE248 1 "register_operand" "0") ! (match_operand:SI 2 "nonmemory_operand" "yN")))] "TARGET_MMX" "p\t{%2, %0|%0, %2}" [(set_attr "type" "mmxshft") --- 945,951 ---- [(set (match_operand:MMXMODE248 0 "register_operand" "=y") (any_lshift:MMXMODE248 (match_operand:MMXMODE248 1 "register_operand" "0") ! (match_operand:DI 2 "nonmemory_operand" "yN")))] "TARGET_MMX" "p\t{%2, %0|%0, %2}" [(set_attr "type" "mmxshft") diff -Nrcpad gcc-6.3.0/gcc/config/i386/pkuintrin.h gcc-6.4.0/gcc/config/i386/pkuintrin.h *** gcc-6.3.0/gcc/config/i386/pkuintrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/pkuintrin.h Thu Jun 1 19:38:29 2017 *************** *** 36,51 **** extern __inline unsigned int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdpkru_u32(void) { return __builtin_ia32_rdpkru (); } extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _wrpkru(unsigned int key) { ! return __builtin_ia32_wrpkru (key); } #ifdef __DISABLE_PKU__ --- 36,51 ---- extern __inline unsigned int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdpkru_u32 (void) { return __builtin_ia32_rdpkru (); } extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _wrpkru (unsigned int __key) { ! __builtin_ia32_wrpkru (__key); } #ifdef __DISABLE_PKU__ diff -Nrcpad gcc-6.3.0/gcc/config/i386/pmm_malloc.h gcc-6.4.0/gcc/config/i386/pmm_malloc.h *** gcc-6.3.0/gcc/config/i386/pmm_malloc.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/pmm_malloc.h Thu Jun 1 19:38:29 2017 *************** extern "C" int posix_memalign (void **, *** 35,57 **** #endif static __inline void * ! _mm_malloc (size_t size, size_t alignment) { ! void *ptr; ! if (alignment == 1) ! return malloc (size); ! if (alignment == 2 || (sizeof (void *) == 8 && alignment == 4)) ! alignment = sizeof (void *); ! if (posix_memalign (&ptr, alignment, size) == 0) ! return ptr; else return NULL; } static __inline void ! _mm_free (void * ptr) { ! free (ptr); } #endif /* _MM_MALLOC_H_INCLUDED */ --- 35,57 ---- #endif static __inline void * ! _mm_malloc (size_t __size, size_t __alignment) { ! void *__ptr; ! if (__alignment == 1) ! return malloc (__size); ! if (__alignment == 2 || (sizeof (void *) == 8 && __alignment == 4)) ! __alignment = sizeof (void *); ! if (posix_memalign (&__ptr, __alignment, __size) == 0) ! return __ptr; else return NULL; } static __inline void ! _mm_free (void *__ptr) { ! free (__ptr); } #endif /* _MM_MALLOC_H_INCLUDED */ diff -Nrcpad gcc-6.3.0/gcc/config/i386/rdseedintrin.h gcc-6.4.0/gcc/config/i386/rdseedintrin.h *** gcc-6.3.0/gcc/config/i386/rdseedintrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/rdseedintrin.h Thu Jun 1 19:38:29 2017 *************** *** 37,60 **** extern __inline int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdseed16_step (unsigned short *p) { ! return __builtin_ia32_rdseed_hi_step (p); } extern __inline int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdseed32_step (unsigned int *p) { ! return __builtin_ia32_rdseed_si_step (p); } #ifdef __x86_64__ extern __inline int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdseed64_step (unsigned long long *p) { ! return __builtin_ia32_rdseed_di_step (p); } #endif --- 37,60 ---- extern __inline int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdseed16_step (unsigned short *__p) { ! return __builtin_ia32_rdseed_hi_step (__p); } extern __inline int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdseed32_step (unsigned int *__p) { ! return __builtin_ia32_rdseed_si_step (__p); } #ifdef __x86_64__ extern __inline int __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _rdseed64_step (unsigned long long *__p) { ! return __builtin_ia32_rdseed_di_step (__p); } #endif diff -Nrcpad gcc-6.3.0/gcc/config/i386/rtemself.h gcc-6.4.0/gcc/config/i386/rtemself.h *** gcc-6.3.0/gcc/config/i386/rtemself.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/rtemself.h Tue Jan 24 10:54:56 2017 *************** along with GCC; see the file COPYING3. *** 29,35 **** } \ while (0) - #undef LONG_DOUBLE_TYPE_SIZE - #define LONG_DOUBLE_TYPE_SIZE (TARGET_80387 ? 80 : 64) - #define IX86_NO_LIBGCC_TFMODE --- 29,32 ---- diff -Nrcpad gcc-6.3.0/gcc/config/i386/rtmintrin.h gcc-6.4.0/gcc/config/i386/rtmintrin.h *** gcc-6.3.0/gcc/config/i386/rtmintrin.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/rtmintrin.h Thu Jun 1 19:38:29 2017 *************** _xend (void) *** 68,76 **** #ifdef __OPTIMIZE__ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _xabort (const unsigned int imm) { ! __builtin_ia32_xabort (imm); } #else #define _xabort(N) __builtin_ia32_xabort (N) --- 68,76 ---- #ifdef __OPTIMIZE__ extern __inline void __attribute__((__gnu_inline__, __always_inline__, __artificial__)) ! _xabort (const unsigned int __imm) { ! __builtin_ia32_xabort (__imm); } #else #define _xabort(N) __builtin_ia32_xabort (N) diff -Nrcpad gcc-6.3.0/gcc/config/i386/sse.md gcc-6.4.0/gcc/config/i386/sse.md *** gcc-6.3.0/gcc/config/i386/sse.md Thu Oct 6 17:53:15 2016 --- gcc-6.4.0/gcc/config/i386/sse.md Fri May 19 15:51:10 2017 *************** *** 10485,10491 **** [(set (match_operand:VI24_AVX2 0 "register_operand" "=x,x") (ashiftrt:VI24_AVX2 (match_operand:VI24_AVX2 1 "register_operand" "0,x") ! (match_operand:SI 2 "nonmemory_operand" "xN,xN")))] "TARGET_SSE2" "@ psra\t{%2, %0|%0, %2} --- 10485,10491 ---- [(set (match_operand:VI24_AVX2 0 "register_operand" "=x,x") (ashiftrt:VI24_AVX2 (match_operand:VI24_AVX2 1 "register_operand" "0,x") ! (match_operand:DI 2 "nonmemory_operand" "xN,xN")))] "TARGET_SSE2" "@ psra\t{%2, %0|%0, %2} *************** *** 10504,10510 **** [(set (match_operand:VI24_AVX512BW_1 0 "register_operand" "=v,v") (ashiftrt:VI24_AVX512BW_1 (match_operand:VI24_AVX512BW_1 1 "nonimmediate_operand" "v,vm") ! (match_operand:SI 2 "nonmemory_operand" "v,N")))] "TARGET_AVX512VL" "vpsra\t{%2, %1, %0|%0, %1, %2}" [(set_attr "type" "sseishft") --- 10504,10510 ---- [(set (match_operand:VI24_AVX512BW_1 0 "register_operand" "=v,v") (ashiftrt:VI24_AVX512BW_1 (match_operand:VI24_AVX512BW_1 1 "nonimmediate_operand" "v,vm") ! (match_operand:DI 2 "nonmemory_operand" "v,N")))] "TARGET_AVX512VL" "vpsra\t{%2, %1, %0|%0, %1, %2}" [(set_attr "type" "sseishft") *************** *** 10532,10538 **** [(set (match_operand:VI248_AVX512BW_AVX512VL 0 "register_operand" "=v,v") (ashiftrt:VI248_AVX512BW_AVX512VL (match_operand:VI248_AVX512BW_AVX512VL 1 "nonimmediate_operand" "v,vm") ! (match_operand:SI 2 "nonmemory_operand" "v,N")))] "TARGET_AVX512F" "vpsra\t{%2, %1, %0|%0, %1, %2}" [(set_attr "type" "sseishft") --- 10532,10538 ---- [(set (match_operand:VI248_AVX512BW_AVX512VL 0 "register_operand" "=v,v") (ashiftrt:VI248_AVX512BW_AVX512VL (match_operand:VI248_AVX512BW_AVX512VL 1 "nonimmediate_operand" "v,vm") ! (match_operand:DI 2 "nonmemory_operand" "v,N")))] "TARGET_AVX512F" "vpsra\t{%2, %1, %0|%0, %1, %2}" [(set_attr "type" "sseishft") *************** *** 10546,10552 **** [(set (match_operand:VI2_AVX2_AVX512BW 0 "register_operand" "=x,v") (any_lshift:VI2_AVX2_AVX512BW (match_operand:VI2_AVX2_AVX512BW 1 "register_operand" "0,v") ! (match_operand:SI 2 "nonmemory_operand" "xN,vN")))] "TARGET_SSE2 && && " "@ p\t{%2, %0|%0, %2} --- 10546,10552 ---- [(set (match_operand:VI2_AVX2_AVX512BW 0 "register_operand" "=x,v") (any_lshift:VI2_AVX2_AVX512BW (match_operand:VI2_AVX2_AVX512BW 1 "register_operand" "0,v") ! (match_operand:DI 2 "nonmemory_operand" "xN,vN")))] "TARGET_SSE2 && && " "@ p\t{%2, %0|%0, %2} *************** *** 10565,10571 **** [(set (match_operand:VI48_AVX2 0 "register_operand" "=x,x,v") (any_lshift:VI48_AVX2 (match_operand:VI48_AVX2 1 "register_operand" "0,x,v") ! (match_operand:SI 2 "nonmemory_operand" "xN,xN,vN")))] "TARGET_SSE2 && " "@ p\t{%2, %0|%0, %2} --- 10565,10571 ---- [(set (match_operand:VI48_AVX2 0 "register_operand" "=x,x,v") (any_lshift:VI48_AVX2 (match_operand:VI48_AVX2 1 "register_operand" "0,x,v") ! (match_operand:DI 2 "nonmemory_operand" "xN,xN,vN")))] "TARGET_SSE2 && " "@ p\t{%2, %0|%0, %2} *************** *** 10585,10591 **** [(set (match_operand:VI48_512 0 "register_operand" "=v,v") (any_lshift:VI48_512 (match_operand:VI48_512 1 "nonimmediate_operand" "v,m") ! (match_operand:SI 2 "nonmemory_operand" "vN,N")))] "TARGET_AVX512F && " "vp\t{%2, %1, %0|%0, %1, %2}" [(set_attr "isa" "avx512f") --- 10585,10591 ---- [(set (match_operand:VI48_512 0 "register_operand" "=v,v") (any_lshift:VI48_512 (match_operand:VI48_512 1 "nonimmediate_operand" "v,m") ! (match_operand:DI 2 "nonmemory_operand" "vN,N")))] "TARGET_AVX512F && " "vp\t{%2, %1, %0|%0, %1, %2}" [(set_attr "isa" "avx512f") *************** *** 10728,10734 **** "TARGET_AVX512F" "ix86_fixup_binary_operands_no_copy (, mode, operands);") ! (define_insn "*avx512bw_3" [(set (match_operand:VI48_AVX512VL 0 "register_operand" "=v") (maxmin:VI48_AVX512VL (match_operand:VI48_AVX512VL 1 "nonimmediate_operand" "%v") --- 10728,10734 ---- "TARGET_AVX512F" "ix86_fixup_binary_operands_no_copy (, mode, operands);") ! (define_insn "*avx512f_3" [(set (match_operand:VI48_AVX512VL 0 "register_operand" "=v") (maxmin:VI48_AVX512VL (match_operand:VI48_AVX512VL 1 "nonimmediate_operand" "%v") *************** *** 10752,10761 **** (set_attr "mode" "")]) (define_expand "3" ! [(set (match_operand:VI8_AVX2_AVX512BW 0 "register_operand") ! (maxmin:VI8_AVX2_AVX512BW ! (match_operand:VI8_AVX2_AVX512BW 1 "register_operand") ! (match_operand:VI8_AVX2_AVX512BW 2 "register_operand")))] "TARGET_SSE4_2" { if (TARGET_AVX512F --- 10752,10761 ---- (set_attr "mode" "")]) (define_expand "3" ! [(set (match_operand:VI8_AVX2_AVX512F 0 "register_operand") ! (maxmin:VI8_AVX2_AVX512F ! (match_operand:VI8_AVX2_AVX512F 1 "register_operand") ! (match_operand:VI8_AVX2_AVX512F 2 "register_operand")))] "TARGET_SSE4_2" { if (TARGET_AVX512F *************** *** 13607,13616 **** ;; movd instead of movq is required to handle broken assemblers. (define_insn "vec_concatv2di" [(set (match_operand:V2DI 0 "register_operand" ! "=Yr,*x,x ,Yi,x ,!x,x,x,x,x,x") (vec_concat:V2DI (match_operand:DI 1 "nonimmediate_operand" ! " 0, 0,x ,r ,xm,*y,0,x,0,0,x") (match_operand:DI 2 "vector_move_operand" "*rm,rm,rm,C ,C ,C ,x,x,x,m,m")))] "TARGET_SSE" --- 13607,13616 ---- ;; movd instead of movq is required to handle broken assemblers. (define_insn "vec_concatv2di" [(set (match_operand:V2DI 0 "register_operand" ! "=Yr,*x,x ,Yi,x ,x ,x,x,x,x,x") (vec_concat:V2DI (match_operand:DI 1 "nonimmediate_operand" ! " 0, 0,x ,r ,xm,?!*Yn,0,x,0,0,x") (match_operand:DI 2 "vector_move_operand" "*rm,rm,rm,C ,C ,C ,x,x,x,m,m")))] "TARGET_SSE" diff -Nrcpad gcc-6.3.0/gcc/config/i386/stringop.opt gcc-6.4.0/gcc/config/i386/stringop.opt *** gcc-6.3.0/gcc/config/i386/stringop.opt Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/stringop.opt Thu Jan 1 00:00:00 1970 *************** *** 1,31 **** - /* Definitions for stringop option handling for IA-32. - Copyright (C) 2013-2016 Free Software Foundation, Inc. - - This file is part of GCC. - - GCC is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 3, or (at your option) - any later version. - - GCC is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with GCC; see the files COPYING3. If not, - see . */ - - Enum(stringop_alg) String(rep_byte) Value(rep_prefix_1_byte) - - #undef DEF_ENUM - #define DEF_ENUM EnumValue - - #undef DEF_ALG - #define DEF_ALG(alg, name) Enum(stringop_alg) String(name) Value(alg) - - #include "stringop.def" - - #undef DEF_ENUM - #undef DEF_ALG --- 0 ---- diff -Nrcpad gcc-6.3.0/gcc/config/i386/x86-64.h gcc-6.4.0/gcc/config/i386/x86-64.h *** gcc-6.3.0/gcc/config/i386/x86-64.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/i386/x86-64.h Mon Feb 13 12:35:20 2017 *************** see the files COPYING3 and COPYING.RUNTI *** 49,55 **** #define WCHAR_TYPE_SIZE 32 #undef ASM_SPEC ! #define ASM_SPEC "%{m32:--32} %{m64:--64} %{mx32:--x32}" #undef ASM_OUTPUT_ALIGNED_BSS #define ASM_OUTPUT_ALIGNED_BSS(FILE, DECL, NAME, SIZE, ALIGN) \ --- 49,55 ---- #define WCHAR_TYPE_SIZE 32 #undef ASM_SPEC ! #define ASM_SPEC "%{m16|m32:--32} %{m64:--64} %{mx32:--x32}" #undef ASM_OUTPUT_ALIGNED_BSS #define ASM_OUTPUT_ALIGNED_BSS(FILE, DECL, NAME, SIZE, ALIGN) \ diff -Nrcpad gcc-6.3.0/gcc/config/nds32/nds32.md gcc-6.4.0/gcc/config/nds32/nds32.md *** gcc-6.3.0/gcc/config/nds32/nds32.md Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/nds32/nds32.md Tue Jan 10 04:18:11 2017 *************** create_template: *** 2288,2298 **** emit_jump_insn (gen_cbranchsi4 (test, operands[0], operands[2], operands[4])); ! operands[5] = gen_reg_rtx (SImode); ! /* Step C, D, E, and F, using another temporary register operands[5]. */ ! emit_jump_insn (gen_casesi_internal (operands[0], ! operands[3], ! operands[5])); DONE; }) --- 2288,2296 ---- emit_jump_insn (gen_cbranchsi4 (test, operands[0], operands[2], operands[4])); ! /* Step C, D, E, and F, using another temporary register. */ ! rtx tmp = gen_reg_rtx (SImode); ! emit_jump_insn (gen_casesi_internal (operands[0], operands[3], tmp)); DONE; }) diff -Nrcpad gcc-6.3.0/gcc/config/nvptx/nvptx.c gcc-6.4.0/gcc/config/nvptx/nvptx.c *** gcc-6.3.0/gcc/config/nvptx/nvptx.c Tue May 17 16:08:37 2016 --- gcc-6.4.0/gcc/config/nvptx/nvptx.c Tue Jan 10 12:07:13 2017 *************** nvptx_declare_function_name (FILE *file, *** 989,999 **** init_frame (file, STACK_POINTER_REGNUM, UNITS_PER_WORD, crtl->outgoing_args_size); ! /* Declare a local variable for the frame. */ HOST_WIDE_INT sz = get_frame_size (); if (sz || cfun->machine->has_chain) init_frame (file, FRAME_POINTER_REGNUM, ! crtl->stack_alignment_needed / BITS_PER_UNIT, sz); /* Declare the pseudos we have as ptx registers. */ int maxregs = max_reg_num (); --- 989,1002 ---- init_frame (file, STACK_POINTER_REGNUM, UNITS_PER_WORD, crtl->outgoing_args_size); ! /* Declare a local variable for the frame. Force its size to be ! DImode-compatible. */ HOST_WIDE_INT sz = get_frame_size (); if (sz || cfun->machine->has_chain) init_frame (file, FRAME_POINTER_REGNUM, ! crtl->stack_alignment_needed / BITS_PER_UNIT, ! (sz + GET_MODE_SIZE (DImode) - 1) ! & ~(HOST_WIDE_INT)(GET_MODE_SIZE (DImode) - 1)); /* Declare the pseudos we have as ptx registers. */ int maxregs = max_reg_num (); *************** nvptx_propagate (basic_block block, rtx_ *** 3212,3219 **** rtx pred = NULL_RTX; rtx_code_label *label = NULL; ! gcc_assert (!(fs & (GET_MODE_SIZE (DImode) - 1))); ! fs /= GET_MODE_SIZE (DImode); /* Detect single iteration loop. */ if (fs == 1) fs = 0; --- 3215,3223 ---- rtx pred = NULL_RTX; rtx_code_label *label = NULL; ! /* The frame size might not be DImode compatible, but the frame ! array's declaration will be. So it's ok to round up here. */ ! fs = (fs + GET_MODE_SIZE (DImode) - 1) / GET_MODE_SIZE (DImode); /* Detect single iteration loop. */ if (fs == 1) fs = 0; diff -Nrcpad gcc-6.3.0/gcc/config/pa/pa-64.h gcc-6.4.0/gcc/config/pa/pa-64.h *** gcc-6.3.0/gcc/config/pa/pa-64.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/pa/pa-64.h Mon Mar 6 22:52:46 2017 *************** along with GCC; see the file COPYING3. *** 83,89 **** arguments are padded down when BYTES_BIG_ENDIAN is true. We don't want aggregates padded down. */ ! #define PAD_VARARGS_DOWN (!AGGREGATE_TYPE_P (type)) /* In the PA architecture, it is not possible to directly move data between GENERAL_REGS and FP_REGS. On the 32-bit port, we use the --- 83,92 ---- arguments are padded down when BYTES_BIG_ENDIAN is true. We don't want aggregates padded down. */ ! #define PAD_VARARGS_DOWN \ ! (!AGGREGATE_TYPE_P (type) \ ! && TREE_CODE (type) != COMPLEX_TYPE \ ! && TREE_CODE (type) != VECTOR_TYPE) /* In the PA architecture, it is not possible to directly move data between GENERAL_REGS and FP_REGS. On the 32-bit port, we use the diff -Nrcpad gcc-6.3.0/gcc/config/pa/pa.c gcc-6.4.0/gcc/config/pa/pa.c *** gcc-6.3.0/gcc/config/pa/pa.c Wed Jul 20 22:35:50 2016 --- gcc-6.4.0/gcc/config/pa/pa.c Thu May 11 00:15:04 2017 *************** pa_output_64bit_ior (rtx *operands) *** 3302,3307 **** --- 3302,3325 ---- static bool pa_assemble_integer (rtx x, unsigned int size, int aligned_p) { + bool result; + tree decl = NULL; + + /* When we have a SYMBOL_REF with a SYMBOL_REF_DECL, we need to call + call assemble_external and set the SYMBOL_REF_DECL to NULL before + calling output_addr_const. Otherwise, it may call assemble_external + in the midst of outputing the assembler code for the SYMBOL_REF. + We restore the SYMBOL_REF_DECL after the output is done. */ + if (GET_CODE (x) == SYMBOL_REF) + { + decl = SYMBOL_REF_DECL (x); + if (decl) + { + assemble_external (decl); + SET_SYMBOL_REF_DECL (x, NULL); + } + } + if (size == UNITS_PER_WORD && aligned_p && function_label_operand (x, VOIDmode)) *************** pa_assemble_integer (rtx x, unsigned int *** 3314,3322 **** output_addr_const (asm_out_file, x); fputc ('\n', asm_out_file); ! return true; } ! return default_assemble_integer (x, size, aligned_p); } /* Output an ascii string. */ --- 3332,3346 ---- output_addr_const (asm_out_file, x); fputc ('\n', asm_out_file); ! result = true; } ! else ! result = default_assemble_integer (x, size, aligned_p); ! ! if (decl) ! SET_SYMBOL_REF_DECL (x, decl); ! ! return result; } /* Output an ascii string. */ *************** pa_cannot_change_mode_class (machine_mod *** 9913,9931 **** if (from == to) return false; /* Reject changes to/from complex and vector modes. */ if (COMPLEX_MODE_P (from) || VECTOR_MODE_P (from) || COMPLEX_MODE_P (to) || VECTOR_MODE_P (to)) return true; ! if (GET_MODE_SIZE (from) == GET_MODE_SIZE (to)) ! return false; ! ! /* There is no way to load QImode or HImode values directly from ! memory. SImode loads to the FP registers are not zero extended. ! On the 64-bit target, this conflicts with the definition of ! LOAD_EXTEND_OP. Thus, we can't allow changing between modes ! with different sizes in the floating-point registers. */ if (MAYBE_FP_REG_CLASS_P (rclass)) return true; --- 9937,9959 ---- if (from == to) return false; + if (GET_MODE_SIZE (from) == GET_MODE_SIZE (to)) + return false; + + /* Reject changes to/from modes with zero size. */ + if (!GET_MODE_SIZE (from) || !GET_MODE_SIZE (to)) + return true; + /* Reject changes to/from complex and vector modes. */ if (COMPLEX_MODE_P (from) || VECTOR_MODE_P (from) || COMPLEX_MODE_P (to) || VECTOR_MODE_P (to)) return true; ! /* There is no way to load QImode or HImode values directly from memory ! to a FP register. SImode loads to the FP registers are not zero ! extended. On the 64-bit target, this conflicts with the definition ! of LOAD_EXTEND_OP. Thus, we can't allow changing between modes with ! different sizes in the floating-point registers. */ if (MAYBE_FP_REG_CLASS_P (rclass)) return true; diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/altivec.h gcc-6.4.0/gcc/config/rs6000/altivec.h *** gcc-6.3.0/gcc/config/rs6000/altivec.h Fri Jul 1 15:08:18 2016 --- gcc-6.4.0/gcc/config/rs6000/altivec.h Tue Jan 31 22:57:55 2017 *************** *** 327,334 **** #define vec_sqrt __builtin_vec_sqrt #define vec_vsx_ld __builtin_vec_vsx_ld #define vec_vsx_st __builtin_vec_vsx_st ! #define vec_xl __builtin_vec_xl ! #define vec_xst __builtin_vec_xst /* Note, xxsldi and xxpermdi were added as __builtin_vsx_ functions instead of __builtin_vec_ */ --- 327,334 ---- #define vec_sqrt __builtin_vec_sqrt #define vec_vsx_ld __builtin_vec_vsx_ld #define vec_vsx_st __builtin_vec_vsx_st ! #define vec_xl __builtin_vec_vsx_ld ! #define vec_xst __builtin_vec_vsx_st /* Note, xxsldi and xxpermdi were added as __builtin_vsx_ functions instead of __builtin_vec_ */ diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/constraints.md gcc-6.4.0/gcc/config/rs6000/constraints.md *** gcc-6.3.0/gcc/config/rs6000/constraints.md Tue Aug 9 05:43:29 2016 --- gcc-6.4.0/gcc/config/rs6000/constraints.md Wed Mar 29 23:15:51 2017 *************** *** 135,140 **** --- 135,143 ---- (define_register_constraint "wz" "rs6000_constraints[RS6000_CONSTRAINT_wz]" "Floating point register if the LFIWZX instruction is enabled or NO_REGS.") + (define_register_constraint "wA" "rs6000_constraints[RS6000_CONSTRAINT_wA]" + "BASE_REGS if 64-bit instructions are enabled or NO_REGS.") + (define_constraint "wD" "Int constant that is the element number of the 64-bit scalar in a vector." (and (match_code "const_int") diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/dfp.md gcc-6.4.0/gcc/config/rs6000/dfp.md *** gcc-6.3.0/gcc/config/rs6000/dfp.md Thu Jul 7 19:42:07 2016 --- gcc-6.4.0/gcc/config/rs6000/dfp.md Thu Mar 30 20:06:06 2017 *************** *** 347,362 **** [(set_attr "type" "dfp")]) (define_insn "dfp_dxex_" ! [(set (match_operand:D64_D128 0 "gpc_reg_operand" "=d") ! (unspec:D64_D128 [(match_operand:D64_D128 1 "gpc_reg_operand" "d")] ! UNSPEC_DXEX))] "TARGET_DFP" "dxex %0,%1" [(set_attr "type" "dfp")]) (define_insn "dfp_diex_" [(set (match_operand:D64_D128 0 "gpc_reg_operand" "=d") ! (unspec:D64_D128 [(match_operand:D64_D128 1 "gpc_reg_operand" "d") (match_operand:D64_D128 2 "gpc_reg_operand" "d")] UNSPEC_DXEX))] "TARGET_DFP" --- 347,362 ---- [(set_attr "type" "dfp")]) (define_insn "dfp_dxex_" ! [(set (match_operand:DI 0 "gpc_reg_operand" "=d") ! (unspec:DI [(match_operand:D64_D128 1 "gpc_reg_operand" "d")] ! UNSPEC_DXEX))] "TARGET_DFP" "dxex %0,%1" [(set_attr "type" "dfp")]) (define_insn "dfp_diex_" [(set (match_operand:D64_D128 0 "gpc_reg_operand" "=d") ! (unspec:D64_D128 [(match_operand:DI 1 "gpc_reg_operand" "d") (match_operand:D64_D128 2 "gpc_reg_operand" "d")] UNSPEC_DXEX))] "TARGET_DFP" diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/predicates.md gcc-6.4.0/gcc/config/rs6000/predicates.md *** gcc-6.3.0/gcc/config/rs6000/predicates.md Thu Dec 1 19:26:15 2016 --- gcc-6.4.0/gcc/config/rs6000/predicates.md Wed Jun 21 18:02:37 2017 *************** *** 737,742 **** --- 737,758 ---- (and (match_operand 0 "memory_operand") (match_test "offsettable_nonstrict_memref_p (op)"))) + ;; Return 1 if the operand is a simple offsettable memory operand + ;; that does not include pre-increment, post-increment, etc. + (define_predicate "simple_offsettable_mem_operand" + (match_operand 0 "offsettable_mem_operand") + { + rtx addr = XEXP (op, 0); + + if (GET_CODE (addr) != PLUS && GET_CODE (addr) != LO_SUM) + return 0; + + if (!CONSTANT_P (XEXP (addr, 1))) + return 0; + + return base_reg_operand (XEXP (addr, 0), Pmode); + }) + ;; Return 1 if the operand is suitable for load/store quad memory. ;; This predicate only checks for non-atomic loads/stores (not lqarx/stqcx). (define_predicate "quad_memory_operand" *************** *** 1000,1006 **** (and (match_code "symbol_ref") (match_test "(DEFAULT_ABI != ABI_AIX || SYMBOL_REF_FUNCTION_P (op)) && (SYMBOL_REF_LOCAL_P (op) ! || op == XEXP (DECL_RTL (current_function_decl), 0)) && !((DEFAULT_ABI == ABI_AIX || DEFAULT_ABI == ABI_ELFv2) && (SYMBOL_REF_EXTERNAL_P (op) --- 1016,1023 ---- (and (match_code "symbol_ref") (match_test "(DEFAULT_ABI != ABI_AIX || SYMBOL_REF_FUNCTION_P (op)) && (SYMBOL_REF_LOCAL_P (op) ! || (op == XEXP (DECL_RTL (current_function_decl), 0) ! && !decl_replaceable_p (current_function_decl))) && !((DEFAULT_ABI == ABI_AIX || DEFAULT_ABI == ABI_ELFv2) && (SYMBOL_REF_EXTERNAL_P (op) diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/rs6000-c.c gcc-6.4.0/gcc/config/rs6000/rs6000-c.c *** gcc-6.3.0/gcc/config/rs6000/rs6000-c.c Thu Jul 7 19:42:07 2016 --- gcc-6.4.0/gcc/config/rs6000/rs6000-c.c Wed Mar 1 21:18:18 2017 *************** const struct altivec_builtin_types altiv *** 2133,2146 **** RS6000_BTI_unsigned_V8HI, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, { ALTIVEC_BUILTIN_VEC_PACKS, ALTIVEC_BUILTIN_VPKSWSS, RS6000_BTI_V8HI, RS6000_BTI_V4SI, RS6000_BTI_V4SI, 0 }, - { ALTIVEC_BUILTIN_VEC_VPKSWSS, ALTIVEC_BUILTIN_VPKSWSS, - RS6000_BTI_V8HI, RS6000_BTI_V4SI, RS6000_BTI_V4SI, 0 }, - { ALTIVEC_BUILTIN_VEC_VPKUWUS, ALTIVEC_BUILTIN_VPKUWUS, - RS6000_BTI_unsigned_V8HI, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, { ALTIVEC_BUILTIN_VEC_PACKS, P8V_BUILTIN_VPKUDUS, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, { ALTIVEC_BUILTIN_VEC_PACKS, P8V_BUILTIN_VPKSDSS, RS6000_BTI_V4SI, RS6000_BTI_V2DI, RS6000_BTI_V2DI, 0 }, { ALTIVEC_BUILTIN_VEC_VPKSHSS, ALTIVEC_BUILTIN_VPKSHSS, RS6000_BTI_V16QI, RS6000_BTI_V8HI, RS6000_BTI_V8HI, 0 }, { ALTIVEC_BUILTIN_VEC_VPKUHUS, ALTIVEC_BUILTIN_VPKUHUS, --- 2133,2146 ---- RS6000_BTI_unsigned_V8HI, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, { ALTIVEC_BUILTIN_VEC_PACKS, ALTIVEC_BUILTIN_VPKSWSS, RS6000_BTI_V8HI, RS6000_BTI_V4SI, RS6000_BTI_V4SI, 0 }, { ALTIVEC_BUILTIN_VEC_PACKS, P8V_BUILTIN_VPKUDUS, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, { ALTIVEC_BUILTIN_VEC_PACKS, P8V_BUILTIN_VPKSDSS, RS6000_BTI_V4SI, RS6000_BTI_V2DI, RS6000_BTI_V2DI, 0 }, + { ALTIVEC_BUILTIN_VEC_VPKSWSS, ALTIVEC_BUILTIN_VPKSWSS, + RS6000_BTI_V8HI, RS6000_BTI_V4SI, RS6000_BTI_V4SI, 0 }, + { ALTIVEC_BUILTIN_VEC_VPKUWUS, ALTIVEC_BUILTIN_VPKUWUS, + RS6000_BTI_unsigned_V8HI, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, { ALTIVEC_BUILTIN_VEC_VPKSHSS, ALTIVEC_BUILTIN_VPKSHSS, RS6000_BTI_V16QI, RS6000_BTI_V8HI, RS6000_BTI_V8HI, 0 }, { ALTIVEC_BUILTIN_VEC_VPKUHUS, ALTIVEC_BUILTIN_VPKUHUS, *************** const struct altivec_builtin_types altiv *** 2411,2417 **** RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, { ALTIVEC_BUILTIN_VEC_SRA, P8V_BUILTIN_VSRAD, RS6000_BTI_V2DI, RS6000_BTI_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, ! { ALTIVEC_BUILTIN_VEC_SRA, P8V_BUILTIN_VSRD, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, { ALTIVEC_BUILTIN_VEC_VSRAW, ALTIVEC_BUILTIN_VSRAW, RS6000_BTI_V4SI, RS6000_BTI_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, --- 2411,2417 ---- RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, { ALTIVEC_BUILTIN_VEC_SRA, P8V_BUILTIN_VSRAD, RS6000_BTI_V2DI, RS6000_BTI_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, ! { ALTIVEC_BUILTIN_VEC_SRA, P8V_BUILTIN_VSRAD, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, { ALTIVEC_BUILTIN_VEC_VSRAW, ALTIVEC_BUILTIN_VSRAW, RS6000_BTI_V4SI, RS6000_BTI_V4SI, RS6000_BTI_unsigned_V4SI, 0 }, *************** const struct altivec_builtin_types altiv *** 4512,4518 **** { P8V_BUILTIN_VEC_VSRAD, P8V_BUILTIN_VSRAD, RS6000_BTI_V2DI, RS6000_BTI_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, ! { P8V_BUILTIN_VEC_VSRAD, P8V_BUILTIN_VSRD, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, { P8V_BUILTIN_VEC_VSUBCUQ, P8V_BUILTIN_VSUBCUQ, --- 4512,4518 ---- { P8V_BUILTIN_VEC_VSRAD, P8V_BUILTIN_VSRAD, RS6000_BTI_V2DI, RS6000_BTI_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, ! { P8V_BUILTIN_VEC_VSRAD, P8V_BUILTIN_VSRAD, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, 0 }, { P8V_BUILTIN_VEC_VSUBCUQ, P8V_BUILTIN_VSUBCUQ, *************** const struct altivec_builtin_types altiv *** 4550,4560 **** { P8V_BUILTIN_VEC_VUPKLSW, P8V_BUILTIN_VUPKLSW, RS6000_BTI_bool_V2DI, RS6000_BTI_bool_V4SI, 0, 0 }, - { P8V_BUILTIN_VEC_VGBBD, P8V_BUILTIN_VGBBD, - RS6000_BTI_V16QI, 0, 0, 0 }, - { P8V_BUILTIN_VEC_VGBBD, P8V_BUILTIN_VGBBD, - RS6000_BTI_unsigned_V16QI, 0, 0, 0 }, - { P9V_BUILTIN_VEC_VSLV, P9V_BUILTIN_VSLV, RS6000_BTI_unsigned_V16QI, RS6000_BTI_unsigned_V16QI, RS6000_BTI_unsigned_V16QI, 0 }, --- 4550,4555 ---- diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/rs6000.c gcc-6.4.0/gcc/config/rs6000/rs6000.c *** gcc-6.3.0/gcc/config/rs6000/rs6000.c Tue Dec 13 23:56:17 2016 --- gcc-6.4.0/gcc/config/rs6000/rs6000.c Tue Jun 27 17:11:01 2017 *************** *** 64,69 **** --- 64,70 ---- #include "builtins.h" #include "context.h" #include "tree-pass.h" + #include "except.h" #if TARGET_XCOFF #include "xcoffout.h" /* get declarations of xcoff_*_section_name */ #endif *************** rs6000_debug_reg_global (void) *** 2405,2410 **** --- 2406,2412 ---- "wx reg_class = %s\n" "wy reg_class = %s\n" "wz reg_class = %s\n" + "wA reg_class = %s\n" "\n", reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_d]], reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_f]], *************** rs6000_debug_reg_global (void) *** 2432,2438 **** reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_ww]], reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_wx]], reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_wy]], ! reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_wz]]); nl = "\n"; for (m = 0; m < NUM_MACHINE_MODES; ++m) --- 2434,2441 ---- reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_ww]], reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_wx]], reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_wy]], ! reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_wz]], ! reg_class_names[rs6000_constraints[RS6000_CONSTRAINT_wA]]); nl = "\n"; for (m = 0; m < NUM_MACHINE_MODES; ++m) *************** rs6000_init_hard_regno_mode_ok (bool glo *** 3119,3125 **** } if (TARGET_POWERPC64) ! rs6000_constraints[RS6000_CONSTRAINT_wr] = GENERAL_REGS; if (TARGET_P8_VECTOR && TARGET_UPPER_REGS_SF) /* SFmode */ { --- 3122,3131 ---- } if (TARGET_POWERPC64) ! { ! rs6000_constraints[RS6000_CONSTRAINT_wr] = GENERAL_REGS; ! rs6000_constraints[RS6000_CONSTRAINT_wA] = BASE_REGS; ! } if (TARGET_P8_VECTOR && TARGET_UPPER_REGS_SF) /* SFmode */ { *************** rs6000_option_override_internal (bool gl *** 3750,3755 **** --- 3756,3768 ---- && !global_options_set.x_flag_ira_loop_pressure) flag_ira_loop_pressure = 1; + /* -fsanitize=address needs to turn on -fasynchronous-unwind-tables in order + for tracebacks to be complete but not if any -fasynchronous-unwind-tables + options were already specified. */ + if (flag_sanitize & SANITIZE_USER_ADDRESS + && !global_options_set.x_flag_asynchronous_unwind_tables) + flag_asynchronous_unwind_tables = 1; + /* Set the pointer size. */ if (TARGET_64BIT) { *************** rs6000_option_override_internal (bool gl *** 4190,4195 **** --- 4203,4212 ---- { if (rs6000_isa_flags_explicit & OPTION_MASK_P8_FUSION) { + /* We prefer to not mention undocumented options in + error messages. However, if users have managed to select + power9-fusion without selecting power8-fusion, they + already know about undocumented flags. */ error ("-mpower9-fusion requires -mpower8-fusion"); rs6000_isa_flags &= ~OPTION_MASK_P9_FUSION; } *************** rs6000_option_override_internal (bool gl *** 4237,4242 **** --- 4254,4263 ---- /* ISA 3.0 vector instructions include ISA 2.07. */ if (TARGET_P9_VECTOR && !TARGET_P8_VECTOR) { + /* We prefer to not mention undocumented options in + error messages. However, if users have managed to select + power9-vector without selecting power8-vector, they + already know about undocumented flags. */ if (rs6000_isa_flags_explicit & OPTION_MASK_P8_VECTOR) error ("-mpower9-vector requires -mpower8-vector"); rs6000_isa_flags &= ~OPTION_MASK_P9_VECTOR; *************** rs6000_option_override_internal (bool gl *** 4264,4269 **** --- 4285,4294 ---- /* ISA 3.0 D-form instructions require p9-vector and upper-regs. */ if ((TARGET_P9_DFORM_SCALAR || TARGET_P9_DFORM_VECTOR) && !TARGET_P9_VECTOR) { + /* We prefer to not mention undocumented options in + error messages. However, if users have managed to select + power9-dform without selecting power9-vector, they + already know about undocumented flags. */ if (rs6000_isa_flags_explicit & OPTION_MASK_P9_VECTOR) error ("-mpower9-dform requires -mpower9-vector"); rs6000_isa_flags &= ~(OPTION_MASK_P9_DFORM_SCALAR *************** rs6000_option_override_internal (bool gl *** 4272,4277 **** --- 4297,4306 ---- if (TARGET_P9_DFORM_SCALAR && !TARGET_UPPER_REGS_DF) { + /* We prefer to not mention undocumented options in + error messages. However, if users have managed to select + power9-dform without selecting upper-regs-df, they + already know about undocumented flags. */ if (rs6000_isa_flags_explicit & OPTION_MASK_UPPER_REGS_DF) error ("-mpower9-dform requires -mupper-regs-df"); rs6000_isa_flags &= ~OPTION_MASK_P9_DFORM_SCALAR; *************** rs6000_density_test (rs6000_cost_data *d *** 5340,5345 **** --- 5369,5378 ---- /* Implement targetm.vectorize.init_cost. */ + /* For each vectorized loop, this var holds TRUE iff a non-memory vector + instruction is needed by the vectorization. */ + static bool rs6000_vect_nonmem; + static void * rs6000_init_cost (struct loop *loop_info) { *************** rs6000_init_cost (struct loop *loop_info *** 5348,5353 **** --- 5381,5387 ---- data->cost[vect_prologue] = 0; data->cost[vect_body] = 0; data->cost[vect_epilogue] = 0; + rs6000_vect_nonmem = false; return data; } *************** rs6000_add_stmt_cost (void *data, int co *** 5374,5379 **** --- 5408,5422 ---- retval = (unsigned) (count * stmt_cost); cost_data->cost[where] += retval; + + /* Check whether we're doing something other than just a copy loop. + Not all such loops may be profitably vectorized; see + rs6000_finish_cost. */ + if ((kind == vec_to_scalar || kind == vec_perm + || kind == vec_promote_demote || kind == vec_construct + || kind == scalar_to_vec) + || (where == vect_body && kind == vector_stmt)) + rs6000_vect_nonmem = true; } return retval; *************** rs6000_finish_cost (void *data, unsigned *** 5390,5395 **** --- 5433,5452 ---- if (cost_data->loop_info) rs6000_density_test (cost_data); + /* Don't vectorize minimum-vectorization-factor, simple copy loops + that require versioning for any reason. The vectorization is at + best a wash inside the loop, and the versioning checks make + profitability highly unlikely and potentially quite harmful. */ + if (cost_data->loop_info) + { + loop_vec_info vec_info = loop_vec_info_for_loop (cost_data->loop_info); + if (!rs6000_vect_nonmem + && LOOP_VINFO_VECT_FACTOR (vec_info) == 2 + && (LOOP_REQUIRES_VERSIONING_FOR_ALIGNMENT (vec_info) + || LOOP_REQUIRES_VERSIONING_FOR_ALIAS (vec_info))) + cost_data->cost[vect_body] += 10000; + } + *prologue_cost = cost_data->cost[vect_prologue]; *body_cost = cost_data->cost[vect_body]; *epilogue_cost = cost_data->cost[vect_epilogue]; *************** rs6000_gimplify_va_arg (tree valist, tre *** 12557,12562 **** --- 12614,12620 ---- size = int_size_in_bytes (type); rsize = (size + 3) / 4; + int pad = 4 * rsize - size; align = 1; machine_mode mode = TYPE_MODE (type); *************** rs6000_gimplify_va_arg (tree valist, tre *** 12638,12643 **** --- 12696,12705 ---- && mode == SDmode) t = fold_build_pointer_plus_hwi (t, size); + /* Args are right-aligned. */ + if (BYTES_BIG_ENDIAN) + t = fold_build_pointer_plus_hwi (t, pad); + gimplify_assign (addr, t, pre_p); gimple_seq_add_stmt (pre_p, gimple_build_goto (lab_over)); *************** rs6000_gimplify_va_arg (tree valist, tre *** 12663,12668 **** --- 12725,12735 ---- t = build2 (BIT_AND_EXPR, TREE_TYPE (t), t, build_int_cst (TREE_TYPE (t), -align)); } + + /* Args are right-aligned. */ + if (BYTES_BIG_ENDIAN) + t = fold_build_pointer_plus_hwi (t, pad); + gimplify_expr (&t, pre_p, NULL, is_gimple_val, fb_rvalue); gimplify_assign (unshare_expr (addr), t, pre_p); *************** rs6000_expand_unop_builtin (enum insn_co *** 13257,13263 **** || INTVAL (op0) < -16) { error ("argument 1 must be a 5-bit signed literal"); ! return const0_rtx; } } --- 13324,13330 ---- || INTVAL (op0) < -16) { error ("argument 1 must be a 5-bit signed literal"); ! return CONST0_RTX (tmode); } } *************** rs6000_expand_binop_builtin (enum insn_c *** 13360,13366 **** || TREE_INT_CST_LOW (arg1) & ~0x1f) { error ("argument 2 must be a 5-bit unsigned literal"); ! return const0_rtx; } } else if (icode == CODE_FOR_dfptstsfi_eq_dd --- 13427,13433 ---- || TREE_INT_CST_LOW (arg1) & ~0x1f) { error ("argument 2 must be a 5-bit unsigned literal"); ! return CONST0_RTX (tmode); } } else if (icode == CODE_FOR_dfptstsfi_eq_dd *************** rs6000_expand_ternop_builtin (enum insn_ *** 14152,14162 **** || TREE_INT_CST_LOW (arg2) & ~0xf) { error ("argument 3 must be a 4-bit unsigned literal"); ! return const0_rtx; } } else if (icode == CODE_FOR_vsx_xxpermdi_v2df || icode == CODE_FOR_vsx_xxpermdi_v2di || icode == CODE_FOR_vsx_xxsldwi_v16qi || icode == CODE_FOR_vsx_xxsldwi_v8hi || icode == CODE_FOR_vsx_xxsldwi_v4si --- 14219,14236 ---- || TREE_INT_CST_LOW (arg2) & ~0xf) { error ("argument 3 must be a 4-bit unsigned literal"); ! return CONST0_RTX (tmode); } } else if (icode == CODE_FOR_vsx_xxpermdi_v2df || icode == CODE_FOR_vsx_xxpermdi_v2di + || icode == CODE_FOR_vsx_xxpermdi_v2df_be + || icode == CODE_FOR_vsx_xxpermdi_v2di_be + || icode == CODE_FOR_vsx_xxpermdi_v1ti + || icode == CODE_FOR_vsx_xxpermdi_v4sf + || icode == CODE_FOR_vsx_xxpermdi_v4si + || icode == CODE_FOR_vsx_xxpermdi_v8hi + || icode == CODE_FOR_vsx_xxpermdi_v16qi || icode == CODE_FOR_vsx_xxsldwi_v16qi || icode == CODE_FOR_vsx_xxsldwi_v8hi || icode == CODE_FOR_vsx_xxsldwi_v4si *************** rs6000_expand_ternop_builtin (enum insn_ *** 14170,14176 **** || TREE_INT_CST_LOW (arg2) & ~0x3) { error ("argument 3 must be a 2-bit unsigned literal"); ! return const0_rtx; } } else if (icode == CODE_FOR_vsx_set_v2df --- 14244,14250 ---- || TREE_INT_CST_LOW (arg2) & ~0x3) { error ("argument 3 must be a 2-bit unsigned literal"); ! return CONST0_RTX (tmode); } } else if (icode == CODE_FOR_vsx_set_v2df *************** rs6000_expand_ternop_builtin (enum insn_ *** 14190,14196 **** || TREE_INT_CST_LOW (arg2) & ~0x1) { error ("argument 3 must be a 1-bit unsigned literal"); ! return const0_rtx; } } else if (icode == CODE_FOR_dfp_ddedpd_dd --- 14264,14270 ---- || TREE_INT_CST_LOW (arg2) & ~0x1) { error ("argument 3 must be a 1-bit unsigned literal"); ! return CONST0_RTX (tmode); } } else if (icode == CODE_FOR_dfp_ddedpd_dd *************** rs6000_expand_ternop_builtin (enum insn_ *** 14202,14208 **** || TREE_INT_CST_LOW (arg2) & ~0x3) { error ("argument 1 must be 0 or 2"); ! return const0_rtx; } } else if (icode == CODE_FOR_dfp_denbcd_dd --- 14276,14282 ---- || TREE_INT_CST_LOW (arg2) & ~0x3) { error ("argument 1 must be 0 or 2"); ! return CONST0_RTX (tmode); } } else if (icode == CODE_FOR_dfp_denbcd_dd *************** rs6000_expand_ternop_builtin (enum insn_ *** 14214,14220 **** || TREE_INT_CST_LOW (arg0) & ~0x1) { error ("argument 1 must be a 1-bit unsigned literal"); ! return const0_rtx; } } else if (icode == CODE_FOR_dfp_dscli_dd --- 14288,14294 ---- || TREE_INT_CST_LOW (arg0) & ~0x1) { error ("argument 1 must be a 1-bit unsigned literal"); ! return CONST0_RTX (tmode); } } else if (icode == CODE_FOR_dfp_dscli_dd *************** rs6000_expand_ternop_builtin (enum insn_ *** 14228,14234 **** || TREE_INT_CST_LOW (arg1) & ~0x3f) { error ("argument 2 must be a 6-bit unsigned literal"); ! return const0_rtx; } } else if (icode == CODE_FOR_crypto_vshasigmaw --- 14302,14308 ---- || TREE_INT_CST_LOW (arg1) & ~0x3f) { error ("argument 2 must be a 6-bit unsigned literal"); ! return CONST0_RTX (tmode); } } else if (icode == CODE_FOR_crypto_vshasigmaw *************** rs6000_expand_ternop_builtin (enum insn_ *** 14240,14253 **** if (TREE_CODE (arg1) != INTEGER_CST || wi::geu_p (arg1, 2)) { error ("argument 2 must be 0 or 1"); ! return const0_rtx; } STRIP_NOPS (arg2); ! if (TREE_CODE (arg2) != INTEGER_CST || wi::geu_p (arg1, 16)) { error ("argument 3 must be in the range 0..15"); ! return const0_rtx; } } --- 14314,14327 ---- if (TREE_CODE (arg1) != INTEGER_CST || wi::geu_p (arg1, 2)) { error ("argument 2 must be 0 or 1"); ! return CONST0_RTX (tmode); } STRIP_NOPS (arg2); ! if (TREE_CODE (arg2) != INTEGER_CST || wi::geu_p (arg2, 16)) { error ("argument 3 must be in the range 0..15"); ! return CONST0_RTX (tmode); } } *************** rs6000_invalid_builtin (enum rs6000_buil *** 15412,15424 **** else if ((fnmask & RS6000_BTM_P8_VECTOR) != 0) error ("Builtin function %s requires the -mpower8-vector option", name); else if ((fnmask & RS6000_BTM_P9_VECTOR) != 0) ! error ("Builtin function %s requires the -mpower9-vector option", name); else if ((fnmask & (RS6000_BTM_P9_MISC | RS6000_BTM_64BIT)) == (RS6000_BTM_P9_MISC | RS6000_BTM_64BIT)) ! error ("Builtin function %s requires the -mpower9-misc and" " -m64 options", name); else if ((fnmask & RS6000_BTM_P9_MISC) == RS6000_BTM_P9_MISC) ! error ("Builtin function %s requires the -mpower9-misc option", name); else if ((fnmask & (RS6000_BTM_HARD_FLOAT | RS6000_BTM_LDBL128)) == (RS6000_BTM_HARD_FLOAT | RS6000_BTM_LDBL128)) error ("Builtin function %s requires the -mhard-float and" --- 15486,15498 ---- else if ((fnmask & RS6000_BTM_P8_VECTOR) != 0) error ("Builtin function %s requires the -mpower8-vector option", name); else if ((fnmask & RS6000_BTM_P9_VECTOR) != 0) ! error ("Builtin function %s requires the -mcpu=power9 option", name); else if ((fnmask & (RS6000_BTM_P9_MISC | RS6000_BTM_64BIT)) == (RS6000_BTM_P9_MISC | RS6000_BTM_64BIT)) ! error ("Builtin function %s requires the -mcpu=power9 and" " -m64 options", name); else if ((fnmask & RS6000_BTM_P9_MISC) == RS6000_BTM_P9_MISC) ! error ("Builtin function %s requires the -mcpu=power9 option", name); else if ((fnmask & (RS6000_BTM_HARD_FLOAT | RS6000_BTM_LDBL128)) == (RS6000_BTM_HARD_FLOAT | RS6000_BTM_LDBL128)) error ("Builtin function %s requires the -mhard-float and" *************** altivec_init_builtins (void) *** 16545,16550 **** --- 16619,16635 ---- def_builtin ("__builtin_vsx_st_elemrev_v16qi", void_ftype_v16qi_long_pvoid, VSX_BUILTIN_ST_ELEMREV_V16QI); } + else + { + rs6000_builtin_decls[(int)VSX_BUILTIN_LD_ELEMREV_V8HI] + = rs6000_builtin_decls[(int)VSX_BUILTIN_LXVW4X_V8HI]; + rs6000_builtin_decls[(int)VSX_BUILTIN_LD_ELEMREV_V16QI] + = rs6000_builtin_decls[(int)VSX_BUILTIN_LXVW4X_V16QI]; + rs6000_builtin_decls[(int)VSX_BUILTIN_ST_ELEMREV_V8HI] + = rs6000_builtin_decls[(int)VSX_BUILTIN_STXVW4X_V8HI]; + rs6000_builtin_decls[(int)VSX_BUILTIN_ST_ELEMREV_V16QI] + = rs6000_builtin_decls[(int)VSX_BUILTIN_STXVW4X_V16QI]; + } def_builtin ("__builtin_vec_vsx_ld", opaque_ftype_long_pcvoid, VSX_BUILTIN_VEC_LD); *************** builtin_function_type (machine_mode mode *** 17057,17062 **** --- 17142,17148 ---- break; /* unsigned args, signed return. */ + case VSX_BUILTIN_XVCVUXDSP: case VSX_BUILTIN_XVCVUXDDP_UNS: case ALTIVEC_BUILTIN_UNSFLOAT_V4SI_V4SF: h.uns_p[1] = 1; *************** rs6000_split_signbit (rtx dest, rtx src) *** 23084,23092 **** rtx dest_di = (d_mode == DImode) ? dest : gen_lowpart (DImode, dest); rtx shift_reg = dest_di; ! gcc_assert (REG_P (dest)); ! gcc_assert (REG_P (src) || MEM_P (src)); ! gcc_assert (s_mode == KFmode || s_mode == TFmode); if (MEM_P (src)) { --- 23170,23176 ---- rtx dest_di = (d_mode == DImode) ? dest : gen_lowpart (DImode, dest); rtx shift_reg = dest_di; ! gcc_assert (FLOAT128_IEEE_P (s_mode) && TARGET_POWERPC64); if (MEM_P (src)) { *************** rs6000_split_signbit (rtx dest, rtx src) *** 23098,23114 **** else { ! unsigned int r = REGNO (src); ! /* If this is a VSX register, generate the special mfvsrd instruction ! to get it in a GPR. Until we support SF and DF modes, that will ! always be true. */ ! gcc_assert (VSX_REGNO_P (r)); - if (s_mode == KFmode) - emit_insn (gen_signbitkf2_dm2 (dest_di, src)); else ! emit_insn (gen_signbittf2_dm2 (dest_di, src)); } emit_insn (gen_lshrdi3 (dest_di, shift_reg, GEN_INT (63))); --- 23182,23201 ---- else { ! unsigned int r = reg_or_subregno (src); ! if (INT_REGNO_P (r)) ! shift_reg = gen_rtx_REG (DImode, r + (BYTES_BIG_ENDIAN == 0)); else ! { ! /* Generate the special mfvsrd instruction to get it in a GPR. */ ! gcc_assert (VSX_REGNO_P (r)); ! if (s_mode == KFmode) ! emit_insn (gen_signbitkf2_dm2 (dest_di, src)); ! else ! emit_insn (gen_signbittf2_dm2 (dest_di, src)); ! } } emit_insn (gen_lshrdi3 (dest_di, shift_reg, GEN_INT (63))); *************** rs6000_emit_allocate_stack (HOST_WIDE_IN *** 25358,25366 **** && REGNO (stack_limit_rtx) > 1 && REGNO (stack_limit_rtx) <= 31) { ! emit_insn (gen_add3_insn (tmp_reg, stack_limit_rtx, GEN_INT (size))); ! emit_insn (gen_cond_trap (LTU, stack_reg, tmp_reg, ! const0_rtx)); } else if (GET_CODE (stack_limit_rtx) == SYMBOL_REF && TARGET_32BIT --- 25445,25455 ---- && REGNO (stack_limit_rtx) > 1 && REGNO (stack_limit_rtx) <= 31) { ! rtx_insn *insn ! = gen_add3_insn (tmp_reg, stack_limit_rtx, GEN_INT (size)); ! gcc_assert (insn); ! emit_insn (insn); ! emit_insn (gen_cond_trap (LTU, stack_reg, tmp_reg, const0_rtx)); } else if (GET_CODE (stack_limit_rtx) == SYMBOL_REF && TARGET_32BIT *************** rs6000_expand_split_stack_prologue (void *** 28881,28886 **** --- 28970,28977 ---- split_stack_return use r0. */ use_reg (&call_fusage, r0); add_function_usage_to (insn, call_fusage); + /* Indicate that this function can't jump to non-local gotos. */ + make_reg_eh_region_note_nothrow_nononlocal (insn); emit_insn (gen_frame_load (r0, r1, info->lr_save_offset)); insn = emit_move_insn (lr, r0); add_reg_note (insn, REG_CFA_RESTORE, lr); *************** static int load_store_pendulum; *** 29933,29939 **** static int divide_cnt; /* The following variable helps pair and alternate vector and vector load insns during scheduling. */ ! static int vec_load_pendulum; /* Power4 load update and store update instructions are cracked into a --- 30024,30030 ---- static int divide_cnt; /* The following variable helps pair and alternate vector and vector load insns during scheduling. */ ! static int vec_pairing; /* Power4 load update and store update instructions are cracked into a *************** power9_sched_reorder2 (rtx_insn **ready, *** 30890,30896 **** int pos; int i; rtx_insn *tmp; ! enum attr_type type; type = get_attr_type (last_scheduled_insn); --- 30981,30987 ---- int pos; int i; rtx_insn *tmp; ! enum attr_type type, type2; type = get_attr_type (last_scheduled_insn); *************** power9_sched_reorder2 (rtx_insn **ready, *** 30923,31105 **** /* Last insn was the 2nd divide or not a divide, reset the counter. */ divide_cnt = 0; ! /* Power9 can execute 2 vector operations and 2 vector loads in a single ! cycle. So try to pair up and alternate groups of vector and vector ! load instructions. ! ! To aid this formation, a counter is maintained to keep track of ! vec/vecload insns issued. The value of vec_load_pendulum maintains ! the current state with the following values: ! ! 0 : Initial state, no vec/vecload group has been started. ! ! -1 : 1 vector load has been issued and another has been found on ! the ready list and moved to the end. ! ! -2 : 2 vector loads have been issued and a vector operation has ! been found and moved to the end of the ready list. ! ! -3 : 2 vector loads and a vector insn have been issued and a ! vector operation has been found and moved to the end of the ! ready list. ! 1 : 1 vector insn has been issued and another has been found and ! moved to the end of the ready list. ! 2 : 2 vector insns have been issued and a vector load has been ! found and moved to the end of the ready list. ! 3 : 2 vector insns and a vector load have been issued and another ! vector load has been found and moved to the end of the ready ! list. */ if (type == TYPE_VECLOAD) { /* Issued a vecload. */ ! if (vec_load_pendulum == 0) { ! /* We issued a single vecload, look for another and move it to ! the end of the ready list so it will be scheduled next. ! Set pendulum if found. */ pos = lastpos; while (pos >= 0) { ! if (recog_memoized (ready[pos]) >= 0 ! && get_attr_type (ready[pos]) == TYPE_VECLOAD) { ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_load_pendulum = -1; ! return cached_can_issue_more; } pos--; } ! } ! else if (vec_load_pendulum == -1) ! { ! /* This is the second vecload we've issued, search the ready ! list for a vector operation so we can try to schedule a ! pair of those next. If found move to the end of the ready ! list so it is scheduled next and set the pendulum. */ ! pos = lastpos; ! while (pos >= 0) { ! if (recog_memoized (ready[pos]) >= 0 ! && is_power9_pairable_vec_type ( ! get_attr_type (ready[pos]))) ! { ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_load_pendulum = -2; ! return cached_can_issue_more; ! } ! pos--; ! } ! } ! else if (vec_load_pendulum == 2) ! { ! /* Two vector ops have been issued and we've just issued a ! vecload, look for another vecload and move to end of ready ! list if found. */ ! pos = lastpos; ! while (pos >= 0) ! { ! if (recog_memoized (ready[pos]) >= 0 ! && get_attr_type (ready[pos]) == TYPE_VECLOAD) ! { ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! /* Set pendulum so that next vecload will be seen as ! finishing a group, not start of one. */ ! vec_load_pendulum = 3; ! return cached_can_issue_more; ! } ! pos--; } } } else if (is_power9_pairable_vec_type (type)) { /* Issued a vector operation. */ ! if (vec_load_pendulum == 0) ! /* We issued a single vec op, look for another and move it ! to the end of the ready list so it will be scheduled next. ! Set pendulum if found. */ ! { ! pos = lastpos; ! while (pos >= 0) ! { ! if (recog_memoized (ready[pos]) >= 0 ! && is_power9_pairable_vec_type ( ! get_attr_type (ready[pos]))) ! { ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_load_pendulum = 1; ! return cached_can_issue_more; ! } ! pos--; ! } ! } ! else if (vec_load_pendulum == 1) { ! /* This is the second vec op we've issued, search the ready ! list for a vecload operation so we can try to schedule a ! pair of those next. If found move to the end of the ready ! list so it is scheduled next and set the pendulum. */ pos = lastpos; while (pos >= 0) { ! if (recog_memoized (ready[pos]) >= 0 ! && get_attr_type (ready[pos]) == TYPE_VECLOAD) { ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_load_pendulum = 2; ! return cached_can_issue_more; } pos--; } ! } ! else if (vec_load_pendulum == -2) ! { ! /* Two vecload ops have been issued and we've just issued a ! vec op, look for another vec op and move to end of ready ! list if found. */ ! pos = lastpos; ! while (pos >= 0) { ! if (recog_memoized (ready[pos]) >= 0 ! && is_power9_pairable_vec_type ( ! get_attr_type (ready[pos]))) ! { ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! /* Set pendulum so that next vec op will be seen as ! finishing a group, not start of one. */ ! vec_load_pendulum = -3; ! return cached_can_issue_more; ! } ! pos--; } } } ! /* We've either finished a vec/vecload group, couldn't find an insn to ! continue the current group, or the last insn had nothing to do with ! with a group. In any case, reset the pendulum. */ ! vec_load_pendulum = 0; } return cached_can_issue_more; --- 31014,31127 ---- /* Last insn was the 2nd divide or not a divide, reset the counter. */ divide_cnt = 0; ! /* The best dispatch throughput for vector and vector load insns can be ! achieved by interleaving a vector and vector load such that they'll ! dispatch to the same superslice. If this pairing cannot be achieved ! then it is best to pair vector insns together and vector load insns ! together. ! To aid in this pairing, vec_pairing maintains the current state with ! the following values: ! 0 : Initial state, no vecload/vector pairing has been started. ! 1 : A vecload or vector insn has been issued and a candidate for ! pairing has been found and moved to the end of the ready ! list. */ if (type == TYPE_VECLOAD) { /* Issued a vecload. */ ! if (vec_pairing == 0) { ! int vecload_pos = -1; ! /* We issued a single vecload, look for a vector insn to pair it ! with. If one isn't found, try to pair another vecload. */ pos = lastpos; while (pos >= 0) { ! if (recog_memoized (ready[pos]) >= 0) { ! type2 = get_attr_type (ready[pos]); ! if (is_power9_pairable_vec_type (type2)) ! { ! /* Found a vector insn to pair with, move it to the ! end of the ready list so it is scheduled next. */ ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_pairing = 1; ! return cached_can_issue_more; ! } ! else if (type2 == TYPE_VECLOAD && vecload_pos == -1) ! /* Remember position of first vecload seen. */ ! vecload_pos = pos; } pos--; } ! if (vecload_pos >= 0) { ! /* Didn't find a vector to pair with but did find a vecload, ! move it to the end of the ready list. */ ! tmp = ready[vecload_pos]; ! for (i = vecload_pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_pairing = 1; ! return cached_can_issue_more; } } } else if (is_power9_pairable_vec_type (type)) { /* Issued a vector operation. */ ! if (vec_pairing == 0) { ! int vec_pos = -1; ! /* We issued a single vector insn, look for a vecload to pair it ! with. If one isn't found, try to pair another vector. */ pos = lastpos; while (pos >= 0) { ! if (recog_memoized (ready[pos]) >= 0) { ! type2 = get_attr_type (ready[pos]); ! if (type2 == TYPE_VECLOAD) ! { ! /* Found a vecload insn to pair with, move it to the ! end of the ready list so it is scheduled next. */ ! tmp = ready[pos]; ! for (i = pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_pairing = 1; ! return cached_can_issue_more; ! } ! else if (is_power9_pairable_vec_type (type2) ! && vec_pos == -1) ! /* Remember position of first vector insn seen. */ ! vec_pos = pos; } pos--; } ! if (vec_pos >= 0) { ! /* Didn't find a vecload to pair with but did find a vector ! insn, move it to the end of the ready list. */ ! tmp = ready[vec_pos]; ! for (i = vec_pos; i < lastpos; i++) ! ready[i] = ready[i + 1]; ! ready[lastpos] = tmp; ! vec_pairing = 1; ! return cached_can_issue_more; } } } ! /* We've either finished a vec/vecload pair, couldn't find an insn to ! continue the current pair, or the last insn had nothing to do with ! with pairing. In any case, reset the state. */ ! vec_pairing = 0; } return cached_can_issue_more; *************** rs6000_sched_init (FILE *dump ATTRIBUTE_ *** 32014,32020 **** last_scheduled_insn = NULL; load_store_pendulum = 0; divide_cnt = 0; ! vec_load_pendulum = 0; } /* The following function is called at the end of scheduling BB. --- 32036,32042 ---- last_scheduled_insn = NULL; load_store_pendulum = 0; divide_cnt = 0; ! vec_pairing = 0; } /* The following function is called at the end of scheduling BB. *************** struct rs6000_sched_context *** 32061,32067 **** rtx_insn *last_scheduled_insn; int load_store_pendulum; int divide_cnt; ! int vec_load_pendulum; }; typedef struct rs6000_sched_context rs6000_sched_context_def; --- 32083,32089 ---- rtx_insn *last_scheduled_insn; int load_store_pendulum; int divide_cnt; ! int vec_pairing; }; typedef struct rs6000_sched_context rs6000_sched_context_def; *************** rs6000_init_sched_context (void *_sc, bo *** 32087,32093 **** sc->last_scheduled_insn = NULL; sc->load_store_pendulum = 0; sc->divide_cnt = 0; ! sc->vec_load_pendulum = 0; } else { --- 32109,32115 ---- sc->last_scheduled_insn = NULL; sc->load_store_pendulum = 0; sc->divide_cnt = 0; ! sc->vec_pairing = 0; } else { *************** rs6000_init_sched_context (void *_sc, bo *** 32095,32101 **** sc->last_scheduled_insn = last_scheduled_insn; sc->load_store_pendulum = load_store_pendulum; sc->divide_cnt = divide_cnt; ! sc->vec_load_pendulum = vec_load_pendulum; } } --- 32117,32123 ---- sc->last_scheduled_insn = last_scheduled_insn; sc->load_store_pendulum = load_store_pendulum; sc->divide_cnt = divide_cnt; ! sc->vec_pairing = vec_pairing; } } *************** rs6000_set_sched_context (void *_sc) *** 32111,32117 **** last_scheduled_insn = sc->last_scheduled_insn; load_store_pendulum = sc->load_store_pendulum; divide_cnt = sc->divide_cnt; ! vec_load_pendulum = sc->vec_load_pendulum; } /* Free _SC. */ --- 32133,32139 ---- last_scheduled_insn = sc->last_scheduled_insn; load_store_pendulum = sc->load_store_pendulum; divide_cnt = sc->divide_cnt; ! vec_pairing = sc->vec_pairing; } /* Free _SC. */ *************** rs6000_inner_target_options (tree args, *** 36141,36147 **** } else ! gcc_unreachable (); return ret; } --- 36163,36172 ---- } else ! { ! error ("attribute % argument not a string"); ! return false; ! } return ret; } *************** rtx_is_swappable_p (rtx op, unsigned int *** 38564,38569 **** --- 38589,38595 ---- case UNSPEC_VSX_CVSPDPN: return 0; case UNSPEC_VSPLT_DIRECT: + case UNSPEC_VSX_XXSPLTD: *special = SH_SPLAT; return 1; case UNSPEC_REDUC_PLUS: *************** insn_is_swappable_p (swap_web_entry *ins *** 38634,38639 **** --- 38660,38671 ---- { if (GET_CODE (body) == SET) { + rtx rhs = SET_SRC (body); + /* Even without a swap, the RHS might be a vec_select for, say, + a byte-reversing load. */ + if (GET_CODE (rhs) != MEM) + return 0; + *special = SH_NOSWAP_LD; return 1; } *************** insn_is_swappable_p (swap_web_entry *ins *** 38645,38650 **** --- 38677,38688 ---- { if (GET_CODE (body) == SET && GET_CODE (SET_SRC (body)) != UNSPEC) { + rtx lhs = SET_DEST (body); + /* Even without a swap, the LHS might be a vec_select for, say, + a byte-reversing store. */ + if (GET_CODE (lhs) != MEM) + return 0; + *special = SH_NOSWAP_ST; return 1; } diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/rs6000.h gcc-6.4.0/gcc/config/rs6000/rs6000.h *** gcc-6.3.0/gcc/config/rs6000/rs6000.h Thu Jul 7 19:42:07 2016 --- gcc-6.4.0/gcc/config/rs6000/rs6000.h Mon Apr 3 22:57:32 2017 *************** extern int rs6000_vector_align[]; *** 635,640 **** --- 635,641 ---- #define MASK_DIRECT_MOVE OPTION_MASK_DIRECT_MOVE #define MASK_DLMZB OPTION_MASK_DLMZB #define MASK_EABI OPTION_MASK_EABI + #define MASK_FLOAT128 OPTION_MASK_FLOAT128 #define MASK_FPRND OPTION_MASK_FPRND #define MASK_P8_FUSION OPTION_MASK_P8_FUSION #define MASK_HARD_FLOAT OPTION_MASK_HARD_FLOAT *************** extern int rs6000_vector_align[]; *** 743,749 **** && (TARGET_POPCNTB || VECTOR_UNIT_VSX_P (DFmode))) #define TARGET_FRSQRTES (TARGET_HARD_FLOAT && TARGET_POPCNTB \ ! && TARGET_FPRS && TARGET_SINGLE_FLOAT) #define TARGET_FRSQRTE (TARGET_HARD_FLOAT && TARGET_FPRS \ && TARGET_DOUBLE_FLOAT \ --- 744,751 ---- && (TARGET_POPCNTB || VECTOR_UNIT_VSX_P (DFmode))) #define TARGET_FRSQRTES (TARGET_HARD_FLOAT && TARGET_POPCNTB \ ! && TARGET_PPC_GFXOPT && TARGET_FPRS \ ! && TARGET_SINGLE_FLOAT) #define TARGET_FRSQRTE (TARGET_HARD_FLOAT && TARGET_FPRS \ && TARGET_DOUBLE_FLOAT \ *************** enum r6000_reg_class_enum { *** 1588,1593 **** --- 1590,1596 ---- RS6000_CONSTRAINT_wx, /* FPR register for STFIWX */ RS6000_CONSTRAINT_wy, /* VSX register for SF */ RS6000_CONSTRAINT_wz, /* FPR register for LFIWZX */ + RS6000_CONSTRAINT_wA, /* BASE_REGS if 64-bit. */ RS6000_CONSTRAINT_MAX }; *************** extern int frame_pointer_needed; *** 2718,2724 **** #define RS6000_BTM_HARD_FLOAT MASK_SOFT_FLOAT /* Hardware floating point. */ #define RS6000_BTM_LDBL128 MASK_MULTIPLE /* 128-bit long double. */ #define RS6000_BTM_64BIT MASK_64BIT /* 64-bit addressing. */ ! #define RS6000_BTM_FLOAT128 MASK_P9_VECTOR /* IEEE 128-bit float. */ #define RS6000_BTM_COMMON (RS6000_BTM_ALTIVEC \ | RS6000_BTM_VSX \ --- 2721,2727 ---- #define RS6000_BTM_HARD_FLOAT MASK_SOFT_FLOAT /* Hardware floating point. */ #define RS6000_BTM_LDBL128 MASK_MULTIPLE /* 128-bit long double. */ #define RS6000_BTM_64BIT MASK_64BIT /* 64-bit addressing. */ ! #define RS6000_BTM_FLOAT128 MASK_FLOAT128 /* IEEE 128-bit float. */ #define RS6000_BTM_COMMON (RS6000_BTM_ALTIVEC \ | RS6000_BTM_VSX \ diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/rs6000.md gcc-6.4.0/gcc/config/rs6000/rs6000.md *** gcc-6.3.0/gcc/config/rs6000/rs6000.md Thu Dec 1 19:26:15 2016 --- gcc-6.4.0/gcc/config/rs6000/rs6000.md Mon Jul 3 12:33:00 2017 *************** *** 1,5 **** ;; Machine description for IBM RISC System 6000 (POWER) for GNU C compiler ! ;; Copyright (C) 1990-2016 Free Software Foundation, Inc. ;; Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) ;; This file is part of GCC. --- 1,5 ---- ;; Machine description for IBM RISC System 6000 (POWER) for GNU C compiler ! ;; Copyright (C) 1990-2017 Free Software Foundation, Inc. ;; Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) ;; This file is part of GCC. *************** *** 442,476 **** (DD "wn") (TD "wn")]) - ; Definitions for load to 32-bit fpr register - (define_mode_attr f32_lr [(SF "f") (SD "wz")]) - (define_mode_attr f32_lr2 [(SF "wb") (SD "wn")]) - (define_mode_attr f32_lm [(SF "m") (SD "Z")]) - (define_mode_attr f32_lm2 [(SF "wY") (SD "wn")]) - (define_mode_attr f32_li [(SF "lfs%U1%X1 %0,%1") (SD "lfiwzx %0,%y1")]) - (define_mode_attr f32_li2 [(SF "lxssp %0,%1") (SD "lfiwzx %0,%y1")]) - (define_mode_attr f32_lv [(SF "lxsspx %x0,%y1") (SD "lxsiwzx %x0,%y1")]) - - ; Definitions for store from 32-bit fpr register - (define_mode_attr f32_sr [(SF "f") (SD "wx")]) - (define_mode_attr f32_sr2 [(SF "wb") (SD "wn")]) - (define_mode_attr f32_sm [(SF "m") (SD "Z")]) - (define_mode_attr f32_sm2 [(SF "wY") (SD "wn")]) - (define_mode_attr f32_si [(SF "stfs%U0%X0 %1,%0") (SD "stfiwx %1,%y0")]) - (define_mode_attr f32_si2 [(SF "stxssp %1,%0") (SD "stfiwx %1,%y0")]) - (define_mode_attr f32_sv [(SF "stxsspx %x1,%y0") (SD "stxsiwzx %x1,%y0")]) - - ; Definitions for 32-bit fpr direct move - ; At present, the decimal modes are not allowed in the traditional altivec - ; registers, so restrict the constraints to just the traditional FPRs. - (define_mode_attr f32_dm [(SF "wn") (SD "wh")]) - - ; Definitions for 32-bit VSX - (define_mode_attr f32_vsx [(SF "ww") (SD "wn")]) - - ; Definitions for 32-bit use of altivec registers - (define_mode_attr f32_av [(SF "wu") (SD "wn")]) - ; Definitions for 64-bit VSX (define_mode_attr f64_vsx [(DF "ws") (DD "wn")]) --- 442,447 ---- *************** *** 514,522 **** (define_mode_iterator SIGNBIT [(KF "FLOAT128_VECTOR_P (KFmode)") (TF "FLOAT128_VECTOR_P (TFmode)")]) - (define_mode_attr Fsignbit [(KF "wa") - (TF "wa")]) - ; SF/DF suffix for traditional floating instructions (define_mode_attr Ftrad [(SF "s") (DF "")]) --- 485,490 ---- *************** *** 724,729 **** --- 692,702 ---- (define_code_attr SMINMAX [(smin "SMIN") (smax "SMAX")]) + ;; Iterator to optimize the following cases: + ;; D-form load to FPR register & move to Altivec register + ;; Move Altivec register to FPR register and store + (define_mode_iterator ALTIVEC_DFORM [DF SF]) + ;; Start with fixed-point load and store insns. Here we put only the more ;; complex forms. Basic data transfer is done later. *************** *** 1586,1591 **** --- 1559,1575 ---- || rtx_equal_p (operands[0], operands[1])) ? operands[0] : gen_reg_rtx (mode)); + /* Adding a constant to r0 is not a valid insn, so use a different + strategy in that case. */ + if (reg_or_subregno (operands[1]) == 0 || reg_or_subregno (tmp) == 0) + { + if (operands[0] == operands[1]) + FAIL; + rs6000_emit_move (operands[0], operands[2], mode); + emit_insn (gen_add3 (operands[0], operands[1], operands[0])); + DONE; + } + HOST_WIDE_INT val = INTVAL (operands[2]); HOST_WIDE_INT low = ((val & 0xffff) ^ 0x8000) - 0x8000; HOST_WIDE_INT rest = trunc_int_for_mode (val - low, mode); *************** *** 2255,2266 **** ;; Since the hardware zeros the upper part of the register, save generating the ;; AND immediate if we are converting to unsigned ! (define_insn "*bswaphi2_extenddi" [(set (match_operand:DI 0 "gpc_reg_operand" "=r") (zero_extend:DI ! (bswap:HI (match_operand:HI 1 "memory_operand" "Z"))))] "TARGET_POWERPC64" ! "lhbrx %0,%y1" [(set_attr "length" "4") (set_attr "type" "load")]) --- 2239,2250 ---- ;; Since the hardware zeros the upper part of the register, save generating the ;; AND immediate if we are converting to unsigned ! (define_insn "*bswap2_extenddi" [(set (match_operand:DI 0 "gpc_reg_operand" "=r") (zero_extend:DI ! (bswap:HSI (match_operand:HSI 1 "memory_operand" "Z"))))] "TARGET_POWERPC64" ! "lbrx %0,%y1" [(set_attr "length" "4") (set_attr "type" "load")]) *************** *** 2273,2306 **** [(set_attr "length" "4") (set_attr "type" "load")]) ! (define_expand "bswaphi2" ! [(parallel [(set (match_operand:HI 0 "reg_or_mem_operand" "") ! (bswap:HI ! (match_operand:HI 1 "reg_or_mem_operand" ""))) ! (clobber (match_scratch:SI 2 ""))])] "" { ! if (!REG_P (operands[0]) && !REG_P (operands[1])) ! operands[1] = force_reg (HImode, operands[1]); }) ! (define_insn "bswaphi2_internal" ! [(set (match_operand:HI 0 "reg_or_mem_operand" "=r,Z,&r") ! (bswap:HI ! (match_operand:HI 1 "reg_or_mem_operand" "Z,r,r"))) ! (clobber (match_scratch:SI 2 "=X,X,&r"))] "" ! "@ ! lhbrx %0,%y1 ! sthbrx %1,%y0 ! #" ! [(set_attr "length" "4,4,12") ! (set_attr "type" "load,store,*")]) ! (define_split ! [(set (match_operand:HI 0 "gpc_reg_operand" "") ! (bswap:HI (match_operand:HI 1 "gpc_reg_operand" ""))) ! (clobber (match_operand:SI 2 "gpc_reg_operand" ""))] "reload_completed" [(set (match_dup 3) (and:SI (lshiftrt:SI (match_dup 4) --- 2257,2308 ---- [(set_attr "length" "4") (set_attr "type" "load")]) ! ;; Separate the bswap patterns into load, store, and gpr<-gpr. This prevents ! ;; the register allocator from converting a gpr<-gpr swap into a store and then ! ;; load with byte swap, which can be slower than doing it in the registers. It ! ;; also prevents certain failures with the RELOAD register allocator. ! ! (define_expand "bswap2" ! [(use (match_operand:HSI 0 "reg_or_mem_operand")) ! (use (match_operand:HSI 1 "reg_or_mem_operand"))] "" { ! rtx dest = operands[0]; ! rtx src = operands[1]; ! ! if (!REG_P (dest) && !REG_P (src)) ! src = force_reg (mode, src); ! ! if (MEM_P (src)) ! emit_insn (gen_bswap2_load (dest, src)); ! else if (MEM_P (dest)) ! emit_insn (gen_bswap2_store (dest, src)); ! else ! emit_insn (gen_bswap2_reg (dest, src)); ! DONE; }) ! (define_insn "bswap2_load" ! [(set (match_operand:HSI 0 "gpc_reg_operand" "=r") ! (bswap:HSI (match_operand:HSI 1 "memory_operand" "Z")))] "" ! "lbrx %0,%y1" ! [(set_attr "type" "load")]) ! (define_insn "bswap2_store" ! [(set (match_operand:HSI 0 "memory_operand" "=Z") ! (bswap:HSI (match_operand:HSI 1 "gpc_reg_operand" "r")))] ! "" ! "stbrx %1,%y0" ! [(set_attr "type" "store")]) ! ! (define_insn_and_split "bswaphi2_reg" ! [(set (match_operand:HI 0 "gpc_reg_operand" "=&r") ! (bswap:HI ! (match_operand:HI 1 "gpc_reg_operand" "r"))) ! (clobber (match_scratch:SI 2 "=&r"))] ! "" ! "#" "reload_completed" [(set (match_dup 3) (and:SI (lshiftrt:SI (match_dup 4) *************** *** 2313,2360 **** (set (match_dup 3) (ior:SI (match_dup 3) (match_dup 2)))] - " { operands[3] = simplify_gen_subreg (SImode, operands[0], HImode, 0); operands[4] = simplify_gen_subreg (SImode, operands[1], HImode, 0); ! }") ! ! (define_insn "*bswapsi2_extenddi" ! [(set (match_operand:DI 0 "gpc_reg_operand" "=r") ! (zero_extend:DI ! (bswap:SI (match_operand:SI 1 "memory_operand" "Z"))))] ! "TARGET_POWERPC64" ! "lwbrx %0,%y1" ! [(set_attr "length" "4") ! (set_attr "type" "load")]) ! ! (define_expand "bswapsi2" ! [(set (match_operand:SI 0 "reg_or_mem_operand" "") ! (bswap:SI ! (match_operand:SI 1 "reg_or_mem_operand" "")))] ! "" ! { ! if (!REG_P (operands[0]) && !REG_P (operands[1])) ! operands[1] = force_reg (SImode, operands[1]); ! }) ! ! (define_insn "*bswapsi2_internal" ! [(set (match_operand:SI 0 "reg_or_mem_operand" "=r,Z,&r") ! (bswap:SI ! (match_operand:SI 1 "reg_or_mem_operand" "Z,r,r")))] ! "" ! "@ ! lwbrx %0,%y1 ! stwbrx %1,%y0 ! #" ! [(set_attr "length" "4,4,12") ! (set_attr "type" "load,store,*")]) ;; We are always BITS_BIG_ENDIAN, so the bit positions below in ;; zero_extract insns do not change for -mlittle. ! (define_split ! [(set (match_operand:SI 0 "gpc_reg_operand" "") ! (bswap:SI (match_operand:SI 1 "gpc_reg_operand" "")))] "reload_completed" [(set (match_dup 0) ; DABC (rotate:SI (match_dup 1) --- 2315,2335 ---- (set (match_dup 3) (ior:SI (match_dup 3) (match_dup 2)))] { operands[3] = simplify_gen_subreg (SImode, operands[0], HImode, 0); operands[4] = simplify_gen_subreg (SImode, operands[1], HImode, 0); ! } ! [(set_attr "length" "12") ! (set_attr "type" "*")]) ;; We are always BITS_BIG_ENDIAN, so the bit positions below in ;; zero_extract insns do not change for -mlittle. ! (define_insn_and_split "bswapsi2_reg" ! [(set (match_operand:SI 0 "gpc_reg_operand" "=&r") ! (bswap:SI ! (match_operand:SI 1 "gpc_reg_operand" "r")))] ! "" ! "#" "reload_completed" [(set (match_dup 0) ; DABC (rotate:SI (match_dup 1) *************** *** 2370,2380 **** (const_int 24)) (const_int 255)) (and:SI (match_dup 0) ! (const_int -256)))) ! ! ] "") (define_expand "bswapdi2" [(parallel [(set (match_operand:DI 0 "reg_or_mem_operand" "") (bswap:DI --- 2345,2357 ---- (const_int 24)) (const_int 255)) (and:SI (match_dup 0) ! (const_int -256))))] "") + ;; On systems with LDBRX/STDBRX generate the loads/stores directly, just like + ;; we do for L{H,W}BRX and ST{H,W}BRX above. If not, we have to generate more + ;; complex code. + (define_expand "bswapdi2" [(parallel [(set (match_operand:DI 0 "reg_or_mem_operand" "") (bswap:DI *************** *** 2383,2415 **** (clobber (match_scratch:DI 3 ""))])] "" { ! if (!REG_P (operands[0]) && !REG_P (operands[1])) ! operands[1] = force_reg (DImode, operands[1]); if (!TARGET_POWERPC64) { /* 32-bit mode needs fewer scratch registers, but 32-bit addressing mode that uses 64-bit registers needs the same scratch registers as 64-bit mode. */ ! emit_insn (gen_bswapdi2_32bit (operands[0], operands[1])); DONE; } }) ;; Power7/cell has ldbrx/stdbrx, so use it directly ! (define_insn "*bswapdi2_ldbrx" ! [(set (match_operand:DI 0 "reg_or_mem_operand" "=r,Z,&r") ! (bswap:DI (match_operand:DI 1 "reg_or_mem_operand" "Z,r,r"))) ! (clobber (match_scratch:DI 2 "=X,X,&r")) ! (clobber (match_scratch:DI 3 "=X,X,&r"))] ! "TARGET_POWERPC64 && TARGET_LDBRX ! && (REG_P (operands[0]) || REG_P (operands[1]))" ! "@ ! ldbrx %0,%y1 ! stdbrx %1,%y0 ! #" ! [(set_attr "length" "4,4,36") ! (set_attr "type" "load,store,*")]) ;; Non-power7/cell, fall back to use lwbrx/stwbrx (define_insn "*bswapdi2_64bit" --- 2360,2415 ---- (clobber (match_scratch:DI 3 ""))])] "" { ! rtx dest = operands[0]; ! rtx src = operands[1]; ! ! if (!REG_P (dest) && !REG_P (src)) ! operands[1] = src = force_reg (DImode, src); ! ! if (TARGET_POWERPC64 && TARGET_LDBRX) ! { ! if (MEM_P (src)) ! emit_insn (gen_bswapdi2_load (dest, src)); ! else if (MEM_P (dest)) ! emit_insn (gen_bswapdi2_store (dest, src)); ! else ! emit_insn (gen_bswapdi2_reg (dest, src)); ! DONE; ! } if (!TARGET_POWERPC64) { /* 32-bit mode needs fewer scratch registers, but 32-bit addressing mode that uses 64-bit registers needs the same scratch registers as 64-bit mode. */ ! emit_insn (gen_bswapdi2_32bit (dest, src)); DONE; } }) ;; Power7/cell has ldbrx/stdbrx, so use it directly ! (define_insn "bswapdi2_load" ! [(set (match_operand:DI 0 "gpc_reg_operand" "=r") ! (bswap:DI (match_operand:DI 1 "memory_operand" "Z")))] ! "TARGET_POWERPC64 && TARGET_LDBRX" ! "ldbrx %0,%y1" ! [(set_attr "type" "load")]) ! ! (define_insn "bswapdi2_store" ! [(set (match_operand:DI 0 "memory_operand" "=Z") ! (bswap:DI (match_operand:DI 1 "gpc_reg_operand" "r")))] ! "TARGET_POWERPC64 && TARGET_LDBRX" ! "stdbrx %1,%y0" ! [(set_attr "type" "store")]) ! ! (define_insn "bswapdi2_reg" ! [(set (match_operand:DI 0 "gpc_reg_operand" "=&r") ! (bswap:DI (match_operand:DI 1 "gpc_reg_operand" "r"))) ! (clobber (match_scratch:DI 2 "=&r")) ! (clobber (match_scratch:DI 3 "=&r"))] ! "TARGET_POWERPC64 && TARGET_LDBRX" ! "#" ! [(set_attr "length" "36")]) ;; Non-power7/cell, fall back to use lwbrx/stwbrx (define_insn "*bswapdi2_64bit" *************** *** 3066,3073 **** && ! reg_mentioned_p (operands[3], operands[1]) && ! reg_mentioned_p (operands[3], operands[2])" [(set (match_dup 0) ! (div:GPR (match_dup 1) ! (match_dup 2))) (set (match_dup 3) (mult:GPR (match_dup 0) (match_dup 2))) --- 3066,3073 ---- && ! reg_mentioned_p (operands[3], operands[1]) && ! reg_mentioned_p (operands[3], operands[2])" [(set (match_dup 0) ! (udiv:GPR (match_dup 1) ! (match_dup 2))) (set (match_dup 3) (mult:GPR (match_dup 0) (match_dup 2))) *************** *** 4616,4622 **** (define_insn_and_split "signbit2_dm" [(set (match_operand:SI 0 "gpc_reg_operand" "=r,r,r") (unspec:SI ! [(match_operand:SIGNBIT 1 "input_operand" ",m,r")] UNSPEC_SIGNBIT))] "TARGET_POWERPC64 && TARGET_DIRECT_MOVE" "#" --- 4616,4622 ---- (define_insn_and_split "signbit2_dm" [(set (match_operand:SI 0 "gpc_reg_operand" "=r,r,r") (unspec:SI ! [(match_operand:SIGNBIT 1 "input_operand" "wa,m,r")] UNSPEC_SIGNBIT))] "TARGET_POWERPC64 && TARGET_DIRECT_MOVE" "#" *************** *** 4626,4632 **** rs6000_split_signbit (operands[0], operands[1]); DONE; } ! [(set_attr "length" "8,8,12") (set_attr "type" "mftgpr,load,integer")]) ;; MODES_TIEABLE_P doesn't allow DImode to be tied with the various floating --- 4626,4649 ---- rs6000_split_signbit (operands[0], operands[1]); DONE; } ! [(set_attr "length" "8,8,4") ! (set_attr "type" "mftgpr,load,integer")]) ! ! (define_insn_and_split "*signbit2_dm_ext" ! [(set (match_operand:DI 0 "gpc_reg_operand" "=r,r,r") ! (any_extend:DI ! (unspec:SI ! [(match_operand:SIGNBIT 1 "input_operand" "wa,m,r")] ! UNSPEC_SIGNBIT)))] ! "TARGET_POWERPC64 && TARGET_DIRECT_MOVE" ! "#" ! "&& reload_completed" ! [(const_int 0)] ! { ! rs6000_split_signbit (operands[0], operands[1]); ! DONE; ! } ! [(set_attr "length" "8,8,4") (set_attr "type" "mftgpr,load,integer")]) ;; MODES_TIEABLE_P doesn't allow DImode to be tied with the various floating *************** *** 4634,4640 **** ;; special pattern to avoid using a normal movdi. (define_insn "signbit2_dm2" [(set (match_operand:DI 0 "gpc_reg_operand" "=r") ! (unspec:DI [(match_operand:SIGNBIT 1 "gpc_reg_operand" "") (const_int 0)] UNSPEC_SIGNBIT))] "TARGET_POWERPC64 && TARGET_DIRECT_MOVE" --- 4651,4657 ---- ;; special pattern to avoid using a normal movdi. (define_insn "signbit2_dm2" [(set (match_operand:DI 0 "gpc_reg_operand" "=r") ! (unspec:DI [(match_operand:SIGNBIT 1 "gpc_reg_operand" "wa") (const_int 0)] UNSPEC_SIGNBIT))] "TARGET_POWERPC64 && TARGET_DIRECT_MOVE" *************** *** 4649,4655 **** (unspec:SFDF [(match_operand:SFDF 1 "gpc_reg_operand" ",") (match_operand:SFDF 2 "gpc_reg_operand" ",")] UNSPEC_COPYSIGN))] ! "TARGET__FPR && TARGET_CMPB" "@ fcpsgn %0,%2,%1 xscpsgndp %x0,%x2,%x1" --- 4666,4672 ---- (unspec:SFDF [(match_operand:SFDF 1 "gpc_reg_operand" ",") (match_operand:SFDF 2 "gpc_reg_operand" ",")] UNSPEC_COPYSIGN))] ! "TARGET__FPR && (TARGET_CMPB || VECTOR_UNIT_VSX_P (mode))" "@ fcpsgn %0,%2,%1 xscpsgndp %x0,%x2,%x1" *************** *** 5415,5431 **** [(set_attr "length" "12") (set_attr "type" "fp")]) ! (define_expand "fixuns_truncdi2" ! [(set (match_operand:DI 0 "register_operand" "") ! (unsigned_fix:DI (match_operand:SFDF 1 "register_operand" "")))] ! "TARGET_HARD_FLOAT && (TARGET_FCTIDUZ || VECTOR_UNIT_VSX_P (mode))" ! "") ! ! (define_insn "*fixuns_truncdi2_fctiduz" [(set (match_operand:DI 0 "gpc_reg_operand" "=d,wi") (unsigned_fix:DI (match_operand:SFDF 1 "gpc_reg_operand" ",")))] ! "TARGET_HARD_FLOAT && TARGET_DOUBLE_FLOAT && TARGET_FPRS ! && TARGET_FCTIDUZ" "@ fctiduz %0,%1 xscvdpuxds %x0,%x1" --- 5432,5441 ---- [(set_attr "length" "12") (set_attr "type" "fp")]) ! (define_insn "fixuns_truncdi2" [(set (match_operand:DI 0 "gpc_reg_operand" "=d,wi") (unsigned_fix:DI (match_operand:SFDF 1 "gpc_reg_operand" ",")))] ! "TARGET_HARD_FLOAT && TARGET_DOUBLE_FLOAT && TARGET_FPRS && TARGET_FCTIDUZ" "@ fctiduz %0,%1 xscvdpuxds %x0,%x1" *************** *** 6552,6589 **** operands[3] = gen_int_mode (l, SImode); }") ! (define_insn "mov_hardfloat" ! [(set (match_operand:FMOVE32 0 "nonimmediate_operand" ! "=!r, , , , m, , ! , Z, , !r, ?, ?r, ! f, , !r, *c*l, !r, *h") ! (match_operand:FMOVE32 1 "input_operand" ! "m, , , Z, r, , ! , , , , r, , ! f, , r, r, *h, 0"))] ! "(gpc_reg_operand (operands[0], mode) ! || gpc_reg_operand (operands[1], mode)) ! && (TARGET_HARD_FLOAT && TARGET_FPRS && TARGET_SINGLE_FLOAT)" "@ lwz%U1%X1 %0,%1 ! ! ! stw%U0%X0 %1,%0 - - - xxlxor %x0,%x0,%x0 li %0,0 mtvsrwz %x0,%1 mfvsrwz %0,%x1 fmr %0,%1 - xscpsgndp %x0,%x1,%x1 mr %0,%1 mt%0 %1 mf%1 %0 nop" ! [(set_attr "type" "load,fpload,fpload,fpload,store,fpstore,fpstore,fpstore,veclogical,integer,mffgpr,mftgpr,fpsimple,fpsimple,*,mtjmpr,mfjmpr,*")]) (define_insn "*mov_softfloat" [(set (match_operand:FMOVE32 0 "nonimmediate_operand" "=r,cl,r,r,m,r,r,r,r,*h") --- 6562,6641 ---- operands[3] = gen_int_mode (l, SImode); }") ! ;; Originally, we tried to keep movsf and movsd common, but the differences ! ;; addressing was making it rather difficult to hide with mode attributes. In ! ;; particular for SFmode, on ISA 2.07 (power8) systems, having the GPR store ! ;; before the VSX stores meant that the register allocator would tend to do a ! ;; direct move to the GPR (which involves conversion from scalar to ! ;; vector/memory formats) to save values in the traditional Altivec registers, ! ;; while SDmode had problems on power6 if the GPR store was not first due to ! ;; the power6 not having an integer store operation. ! ;; ! ;; LWZ LFS LXSSP LXSSPX STFS STXSSP ! ;; STXSSPX STW XXLXOR LI FMR XSCPSGNDP ! ;; MR MT MF NOP ! ! (define_insn "movsf_hardfloat" ! [(set (match_operand:SF 0 "nonimmediate_operand" ! "=!r, f, wb, wu, m, wY, ! Z, m, ww, !r, f, ww, ! !r, *c*l, !r, *h") ! (match_operand:SF 1 "input_operand" ! "m, m, wY, Z, f, wb, ! wu, r, j, j, f, ww, ! r, r, *h, 0"))] ! "(register_operand (operands[0], SFmode) ! || register_operand (operands[1], SFmode)) ! && TARGET_HARD_FLOAT && TARGET_FPRS && TARGET_SINGLE_FLOAT" "@ lwz%U1%X1 %0,%1 ! lfs%U1%X1 %0,%1 ! lxssp %0,%1 ! lxsspx %x0,%y1 ! stfs%U0%X0 %1,%0 ! stxssp %1,%0 ! stxsspx %x1,%y0 stw%U0%X0 %1,%0 xxlxor %x0,%x0,%x0 li %0,0 + fmr %0,%1 + xscpsgndp %x0,%x1,%x1 + mr %0,%1 + mt%0 %1 + mf%1 %0 + nop" + [(set_attr "type" + "load, fpload, fpload, fpload, fpstore, fpstore, + fpstore, store, veclogical, integer, fpsimple, fpsimple, + *, mtjmpr, mfjmpr, *")]) + + ;; LWZ LFIWZX STW STFIWX MTVSRWZ MFVSRWZ + ;; FMR MR MT%0 MF%1 NOP + (define_insn "movsd_hardfloat" + [(set (match_operand:SD 0 "nonimmediate_operand" + "=!r, wz, m, Z, ?wh, ?r, + f, !r, *c*l, !r, *h") + (match_operand:SD 1 "input_operand" + "m, Z, r, wx, r, wh, + f, r, r, *h, 0"))] + "(register_operand (operands[0], SDmode) + || register_operand (operands[1], SDmode)) + && TARGET_HARD_FLOAT && TARGET_FPRS && TARGET_SINGLE_FLOAT" + "@ + lwz%U1%X1 %0,%1 + lfiwzx %0,%y1 + stw%U0%X0 %1,%0 + stfiwx %1,%y0 mtvsrwz %x0,%1 mfvsrwz %0,%x1 fmr %0,%1 mr %0,%1 mt%0 %1 mf%1 %0 nop" ! [(set_attr "type" ! "load, fpload, store, fpstore, mffgpr, mftgpr, ! fpsimple, *, mtjmpr, mfjmpr, *")]) (define_insn "*mov_softfloat" [(set (match_operand:FMOVE32 0 "nonimmediate_operand" "=r,cl,r,r,m,r,r,r,r,*h") *************** *** 6698,6705 **** ;; except for 0.0 which can be created on VSX with an xor instruction. (define_insn "*mov_hardfloat32" ! [(set (match_operand:FMOVE64 0 "nonimmediate_operand" "=m,d,d,,Z,,o,,,!r,Y,r,!r") ! (match_operand:FMOVE64 1 "input_operand" "d,m,d,Z,,o,,,,,r,Y,r"))] "! TARGET_POWERPC64 && TARGET_HARD_FLOAT && TARGET_FPRS && TARGET_DOUBLE_FLOAT && (gpc_reg_operand (operands[0], mode) || gpc_reg_operand (operands[1], mode))" --- 6750,6757 ---- ;; except for 0.0 which can be created on VSX with an xor instruction. (define_insn "*mov_hardfloat32" ! [(set (match_operand:FMOVE64 0 "nonimmediate_operand" "=m,d,d,,wY,,Z,,,!r,Y,r,!r") ! (match_operand:FMOVE64 1 "input_operand" "d,m,d,wY,,Z,,,,,r,Y,r"))] "! TARGET_POWERPC64 && TARGET_HARD_FLOAT && TARGET_FPRS && TARGET_DOUBLE_FLOAT && (gpc_reg_operand (operands[0], mode) || gpc_reg_operand (operands[1], mode))" *************** *** 6707,6716 **** stfd%U0%X0 %1,%0 lfd%U1%X1 %0,%1 fmr %0,%1 - lxsd%U1x %x0,%y1 - stxsd%U0x %x1,%y0 lxsd %0,%1 stxsd %1,%0 xxlor %x0,%x1,%x1 xxlxor %x0,%x0,%x0 # --- 6759,6768 ---- stfd%U0%X0 %1,%0 lfd%U1%X1 %0,%1 fmr %0,%1 lxsd %0,%1 stxsd %1,%0 + lxsd%U1x %x0,%y1 + stxsd%U0x %x1,%y0 xxlor %x0,%x1,%x1 xxlxor %x0,%x0,%x0 # *************** *** 7720,7726 **** rtx gpr_lo_reg = gen_lowpart (DFmode, dest); emit_insn (gen_p8_mfvsrd_3_ (gpr_hi_reg, src)); ! emit_insn (gen_vsx_xxpermdi_ (tmp, src, src, GEN_INT (3))); emit_insn (gen_p8_mfvsrd_3_ (gpr_lo_reg, tmp)); DONE; } --- 7772,7778 ---- rtx gpr_lo_reg = gen_lowpart (DFmode, dest); emit_insn (gen_p8_mfvsrd_3_ (gpr_hi_reg, src)); ! emit_insn (gen_vsx_xxpermdi__be (tmp, src, src, GEN_INT (3))); emit_insn (gen_p8_mfvsrd_3_ (gpr_lo_reg, tmp)); DONE; } *************** *** 13121,13126 **** --- 13173,13246 ---- (set_attr "length" "8")]) + ;; Optimize cases where we want to do a D-form load (register+offset) on + ;; ISA 2.06/2.07 to an Altivec register, and the register allocator + ;; has generated: + ;; load fpr + ;; move fpr->altivec + + (define_peephole2 + [(match_scratch:P 0 "b") + (set (match_operand:ALTIVEC_DFORM 1 "fpr_reg_operand") + (match_operand:ALTIVEC_DFORM 2 "simple_offsettable_mem_operand")) + (set (match_operand:ALTIVEC_DFORM 3 "altivec_register_operand") + (match_dup 1))] + "TARGET_VSX && TARGET_UPPER_REGS_ && !TARGET_P9_DFORM_SCALAR + && peep2_reg_dead_p (2, operands[1])" + [(set (match_dup 0) + (match_dup 4)) + (set (match_dup 3) + (match_dup 5))] + { + rtx tmp_reg = operands[0]; + rtx mem = operands[2]; + rtx addr = XEXP (mem, 0); + rtx add_op0, add_op1, new_addr; + + gcc_assert (GET_CODE (addr) == PLUS || GET_CODE (addr) == LO_SUM); + add_op0 = XEXP (addr, 0); + add_op1 = XEXP (addr, 1); + gcc_assert (REG_P (add_op0)); + new_addr = gen_rtx_PLUS (Pmode, add_op0, tmp_reg); + + operands[4] = add_op1; + operands[5] = change_address (mem, mode, new_addr); + }) + + ;; Optimize cases were want to do a D-form store on ISA 2.06/2.07 from an + ;; Altivec register, and the register allocator has generated: + ;; move altivec->fpr + ;; store fpr + + (define_peephole2 + [(match_scratch:P 0 "b") + (set (match_operand:ALTIVEC_DFORM 1 "fpr_reg_operand") + (match_operand:ALTIVEC_DFORM 2 "altivec_register_operand")) + (set (match_operand:ALTIVEC_DFORM 3 "simple_offsettable_mem_operand") + (match_dup 1))] + "TARGET_VSX && TARGET_UPPER_REGS_ && !TARGET_P9_DFORM_SCALAR + && peep2_reg_dead_p (2, operands[1])" + [(set (match_dup 0) + (match_dup 4)) + (set (match_dup 5) + (match_dup 2))] + { + rtx tmp_reg = operands[0]; + rtx mem = operands[3]; + rtx addr = XEXP (mem, 0); + rtx add_op0, add_op1, new_addr; + + gcc_assert (GET_CODE (addr) == PLUS || GET_CODE (addr) == LO_SUM); + add_op0 = XEXP (addr, 0); + add_op1 = XEXP (addr, 1); + gcc_assert (REG_P (add_op0)); + new_addr = gen_rtx_PLUS (Pmode, add_op0, tmp_reg); + + operands[4] = add_op1; + operands[5] = change_address (mem, mode, new_addr); + }) + + ;; Miscellaneous ISA 2.06 (power7) instructions (define_insn "addg6s" [(set (match_operand:SI 0 "register_operand" "=r") diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/rs6000.opt gcc-6.4.0/gcc/config/rs6000/rs6000.opt *** gcc-6.3.0/gcc/config/rs6000/rs6000.opt Thu Jul 7 19:42:07 2016 --- gcc-6.4.0/gcc/config/rs6000/rs6000.opt Wed Feb 8 21:41:31 2017 *************** Use AltiVec instructions. *** 142,152 **** maltivec=le Target Report RejectNegative Var(rs6000_altivec_element_order, 1) Save ! Generate Altivec instructions using little-endian element order. maltivec=be Target Report RejectNegative Var(rs6000_altivec_element_order, 2) ! Generate Altivec instructions using big-endian element order. mhard-dfp Target Report Mask(DFP) Var(rs6000_isa_flags) --- 142,152 ---- maltivec=le Target Report RejectNegative Var(rs6000_altivec_element_order, 1) Save ! Generate AltiVec instructions using little-endian element order. maltivec=be Target Report RejectNegative Var(rs6000_altivec_element_order, 2) ! Generate AltiVec instructions using big-endian element order. mhard-dfp Target Report Mask(DFP) Var(rs6000_isa_flags) *************** Target Undocumented Var(rs6000_optimize_ *** 602,608 **** Analyze and remove doubleword swaps from VSX computations. mpower9-fusion ! Target Report Mask(P9_FUSION) Var(rs6000_isa_flags) Fuse certain operations together for better performance on power9. mpower9-misc --- 602,608 ---- Analyze and remove doubleword swaps from VSX computations. mpower9-fusion ! Target Undocumented Report Mask(P9_FUSION) Var(rs6000_isa_flags) Fuse certain operations together for better performance on power9. mpower9-misc *************** Target Undocumented Report Mask(P9_MISC) *** 610,616 **** Use/do not use certain scalar instructions added in ISA 3.0. mpower9-vector ! Target Report Mask(P9_VECTOR) Var(rs6000_isa_flags) Use/do not use vector instructions added in ISA 3.0. mpower9-dform-scalar --- 610,616 ---- Use/do not use certain scalar instructions added in ISA 3.0. mpower9-vector ! Target Undocumented Report Mask(P9_VECTOR) Var(rs6000_isa_flags) Use/do not use vector instructions added in ISA 3.0. mpower9-dform-scalar *************** Target Undocumented Mask(P9_DFORM_VECTOR *** 622,628 **** Use/do not use vector register+offset memory instructions added in ISA 3.0. mpower9-dform ! Target Report Var(TARGET_P9_DFORM_BOTH) Init(-1) Save Use/do not use register+offset memory instructions added in ISA 3.0. mpower9-minmax --- 622,628 ---- Use/do not use vector register+offset memory instructions added in ISA 3.0. mpower9-dform ! Target Undocumented Report Var(TARGET_P9_DFORM_BOTH) Init(-1) Save Use/do not use register+offset memory instructions added in ISA 3.0. mpower9-minmax *************** Target Undocumented Mask(TOC_FUSION) Var *** 634,640 **** Fuse medium/large code model toc references with the memory instruction. mmodulo ! Target Report Mask(MODULO) Var(rs6000_isa_flags) Generate the integer modulo instructions. mfloat128 --- 634,640 ---- Fuse medium/large code model toc references with the memory instruction. mmodulo ! Target Undocumented Report Mask(MODULO) Var(rs6000_isa_flags) Generate the integer modulo instructions. mfloat128 diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/sync.md gcc-6.4.0/gcc/config/rs6000/sync.md *** gcc-6.3.0/gcc/config/rs6000/sync.md Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/rs6000/sync.md Tue Jun 27 17:11:01 2017 *************** *** 157,164 **** rtx op1 = operands[1]; rtx pti_reg = gen_reg_rtx (PTImode); ! // Can't have indexed address for 'lq' ! if (indexed_address (XEXP (op1, 0), TImode)) { rtx old_addr = XEXP (op1, 0); rtx new_addr = force_reg (Pmode, old_addr); --- 157,163 ---- rtx op1 = operands[1]; rtx pti_reg = gen_reg_rtx (PTImode); ! if (!quad_address_p (XEXP (op1, 0), TImode, false)) { rtx old_addr = XEXP (op1, 0); rtx new_addr = force_reg (Pmode, old_addr); *************** *** 231,238 **** rtx op1 = operands[1]; rtx pti_reg = gen_reg_rtx (PTImode); ! // Can't have indexed address for 'stq' ! if (indexed_address (XEXP (op0, 0), TImode)) { rtx old_addr = XEXP (op0, 0); rtx new_addr = force_reg (Pmode, old_addr); --- 230,236 ---- rtx op1 = operands[1]; rtx pti_reg = gen_reg_rtx (PTImode); ! if (!quad_address_p (XEXP (op0, 0), TImode, false)) { rtx old_addr = XEXP (op0, 0); rtx new_addr = force_reg (Pmode, old_addr); diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/vector.md gcc-6.4.0/gcc/config/rs6000/vector.md *** gcc-6.3.0/gcc/config/rs6000/vector.md Wed Jun 1 23:23:42 2016 --- gcc-6.4.0/gcc/config/rs6000/vector.md Tue Jun 27 17:11:01 2017 *************** *** 556,568 **** (gt:VEC_F (match_dup 2) (match_dup 1))) (set (match_dup 0) ! (not:VEC_F (ior:VEC_F (match_dup 3) ! (match_dup 4))))] ! " { operands[3] = gen_reg_rtx (mode); operands[4] = gen_reg_rtx (mode); ! }") (define_insn_and_split "*vector_ltgt" [(set (match_operand:VEC_F 0 "vfloat_operand" "") --- 556,567 ---- (gt:VEC_F (match_dup 2) (match_dup 1))) (set (match_dup 0) ! (and:VEC_F (not:VEC_F (match_dup 3)) ! (not:VEC_F (match_dup 4))))] { operands[3] = gen_reg_rtx (mode); operands[4] = gen_reg_rtx (mode); ! }) (define_insn_and_split "*vector_ltgt" [(set (match_operand:VEC_F 0 "vfloat_operand" "") diff -Nrcpad gcc-6.3.0/gcc/config/rs6000/vsx.md gcc-6.4.0/gcc/config/rs6000/vsx.md *** gcc-6.3.0/gcc/config/rs6000/vsx.md Thu Aug 25 14:24:17 2016 --- gcc-6.4.0/gcc/config/rs6000/vsx.md Wed Jun 21 18:02:37 2017 *************** *** 1827,1845 **** [(set_attr "type" "vecdouble")]) (define_insn "vsx_xvcvsxdsp" ! [(set (match_operand:V4SI 0 "vsx_register_operand" "=wd,?wa") ! (unspec:V4SI [(match_operand:V2DF 1 "vsx_register_operand" "wf,wa")] UNSPEC_VSX_CVSXDSP))] "VECTOR_UNIT_VSX_P (V2DFmode)" "xvcvsxdsp %x0,%x1" [(set_attr "type" "vecfloat")]) (define_insn "vsx_xvcvuxdsp" ! [(set (match_operand:V4SI 0 "vsx_register_operand" "=wd,?wa") ! (unspec:V4SI [(match_operand:V2DF 1 "vsx_register_operand" "wf,wa")] UNSPEC_VSX_CVUXDSP))] "VECTOR_UNIT_VSX_P (V2DFmode)" ! "xvcvuxwdp %x0,%x1" [(set_attr "type" "vecdouble")]) ;; Convert from 32-bit to 64-bit types --- 1827,1845 ---- [(set_attr "type" "vecdouble")]) (define_insn "vsx_xvcvsxdsp" ! [(set (match_operand:V4SF 0 "vsx_register_operand" "=wd,?wa") ! (unspec:V4SF [(match_operand:V2DI 1 "vsx_register_operand" "wf,wa")] UNSPEC_VSX_CVSXDSP))] "VECTOR_UNIT_VSX_P (V2DFmode)" "xvcvsxdsp %x0,%x1" [(set_attr "type" "vecfloat")]) (define_insn "vsx_xvcvuxdsp" ! [(set (match_operand:V4SF 0 "vsx_register_operand" "=wd,?wa") ! (unspec:V4SF [(match_operand:V2DI 1 "vsx_register_operand" "wf,wa")] UNSPEC_VSX_CVUXDSP))] "VECTOR_UNIT_VSX_P (V2DFmode)" ! "xvcvuxdsp %x0,%x1" [(set_attr "type" "vecdouble")]) ;; Convert from 32-bit to 64-bit types *************** *** 2276,2281 **** --- 2276,2313 ---- op1 = gen_lowpart (V2DImode, op1); } } + emit_insn (gen (target, op0, op1, perm0, perm1)); + DONE; + }) + + ;; Special version of xxpermdi that retains big-endian semantics. + (define_expand "vsx_xxpermdi__be" + [(match_operand:VSX_L 0 "vsx_register_operand" "") + (match_operand:VSX_L 1 "vsx_register_operand" "") + (match_operand:VSX_L 2 "vsx_register_operand" "") + (match_operand:QI 3 "u5bit_cint_operand" "")] + "VECTOR_MEM_VSX_P (mode)" + { + rtx target = operands[0]; + rtx op0 = operands[1]; + rtx op1 = operands[2]; + int mask = INTVAL (operands[3]); + rtx perm0 = GEN_INT ((mask >> 1) & 1); + rtx perm1 = GEN_INT ((mask & 1) + 2); + rtx (*gen) (rtx, rtx, rtx, rtx, rtx); + + if (mode == V2DFmode) + gen = gen_vsx_xxpermdi2_v2df_1; + else + { + gen = gen_vsx_xxpermdi2_v2di_1; + if (mode != V2DImode) + { + target = gen_lowpart (V2DImode, target); + op0 = gen_lowpart (V2DImode, op0); + op1 = gen_lowpart (V2DImode, op1); + } + } /* In little endian mode, vsx_xxpermdi2__1 will perform a transformation we don't want; it is necessary for rs6000_expand_vec_perm_const_1 but not for this use. So we *************** *** 2397,2412 **** }) ;; V2DF/V2DI splat ! (define_insn "vsx_splat_" ! [(set (match_operand:VSX_D 0 "vsx_register_operand" "=,,we") (vec_duplicate:VSX_D ! (match_operand: 1 "splat_input_operand" ",Z,b")))] "VECTOR_MEM_VSX_P (mode)" "@ xxpermdi %x0,%x1,%x1,0 lxvdsx %x0,%y1 ! mtvsrdd %x0,%1,%1" ! [(set_attr "type" "vecperm,vecload,mftgpr")]) ;; V4SI splat (ISA 3.0) ;; When SI's are allowed in VSX registers, add XXSPLTW support --- 2429,2462 ---- }) ;; V2DF/V2DI splat ! (define_insn_and_split "vsx_splat_" ! [(set (match_operand:VSX_D 0 "vsx_register_operand" ! "=, ,?we,??") ! (vec_duplicate:VSX_D ! (match_operand: 1 "splat_input_operand" ! ",Z, b, wA")))] "VECTOR_MEM_VSX_P (mode)" "@ xxpermdi %x0,%x1,%x1,0 lxvdsx %x0,%y1 ! mtvsrdd %x0,%1,%1 ! #" ! "&& reload_completed ! && !vsx_register_operand (operands[1], mode) ! && !(MEM_P (operands[1]) ! && indexed_or_indirect_address (XEXP (operands[1], 0), Pmode)) ! && !(TARGET_POWERPC64 && TARGET_P9_VECTOR ! && base_reg_operand (operands[1], mode))" ! [(set (match_dup 2) ! (match_dup 1)) ! (set (match_dup 0) ! (vec_duplicate:VSX_D (match_dup 2)))] ! { ! operands[2] = gen_rtx_REG (mode, reg_or_subregno (operands[0])); ! } ! [(set_attr "type" "vecperm,vecload,vecperm,vecperm") ! (set_attr "length" "4,4,4,8")]) ;; V4SI splat (ISA 3.0) ;; When SI's are allowed in VSX registers, add XXSPLTW support diff -Nrcpad gcc-6.3.0/gcc/config/sparc/driver-sparc.c gcc-6.4.0/gcc/config/sparc/driver-sparc.c *** gcc-6.3.0/gcc/config/sparc/driver-sparc.c Wed Jun 8 19:13:37 2016 --- gcc-6.4.0/gcc/config/sparc/driver-sparc.c Wed Jun 14 07:46:03 2017 *************** static const struct cpu_names { *** 57,62 **** --- 57,63 ---- { "UltraSPARC-T2+", "niagara2" }, { "SPARC-T3", "niagara3" }, { "SPARC-T4", "niagara4" }, + { "SPARC-T5", "niagara4" }, #else { "SuperSparc", "supersparc" }, { "HyperSparc", "hypersparc" }, *************** static const struct cpu_names { *** 73,78 **** --- 74,80 ---- { "UltraSparc T2", "niagara2" }, { "UltraSparc T3", "niagara3" }, { "UltraSparc T4", "niagara4" }, + { "UltraSparc T5", "niagara4" }, { "LEON", "leon3" }, #endif { "SPARC-M7", "niagara7" }, diff -Nrcpad gcc-6.3.0/gcc/config/sparc/sol2.h gcc-6.4.0/gcc/config/sparc/sol2.h *** gcc-6.3.0/gcc/config/sparc/sol2.h Wed Jun 8 13:34:25 2016 --- gcc-6.4.0/gcc/config/sparc/sol2.h Tue May 23 18:54:17 2017 *************** along with GCC; see the file COPYING3. *** 169,175 **** #undef CPP_CPU64_DEFAULT_SPEC #define CPP_CPU64_DEFAULT_SPEC "" #undef ASM_CPU32_DEFAULT_SPEC ! #define ASM_CPU32_DEFAUILT_SPEC AS_SPARC32_FLAG AS_NIAGARA7_FLAG #undef ASM_CPU64_DEFAULT_SPEC #define ASM_CPU64_DEFAULT_SPEC AS_SPARC64_FLAG AS_NIAGARA7_FLAG #endif --- 169,175 ---- #undef CPP_CPU64_DEFAULT_SPEC #define CPP_CPU64_DEFAULT_SPEC "" #undef ASM_CPU32_DEFAULT_SPEC ! #define ASM_CPU32_DEFAULT_SPEC AS_SPARC32_FLAG AS_NIAGARA7_FLAG #undef ASM_CPU64_DEFAULT_SPEC #define ASM_CPU64_DEFAULT_SPEC AS_SPARC64_FLAG AS_NIAGARA7_FLAG #endif diff -Nrcpad gcc-6.3.0/gcc/config/sparc/sparc.c gcc-6.4.0/gcc/config/sparc/sparc.c *** gcc-6.3.0/gcc/config/sparc/sparc.c Sun Oct 16 19:37:50 2016 --- gcc-6.4.0/gcc/config/sparc/sparc.c Fri Jun 9 19:24:51 2017 *************** sparc_option_override (void) *** 1503,1517 **** target_flags &= ~MASK_STACK_BIAS; /* Supply a default value for align_functions. */ ! if (align_functions == 0 ! && (sparc_cpu == PROCESSOR_ULTRASPARC || sparc_cpu == PROCESSOR_ULTRASPARC3 || sparc_cpu == PROCESSOR_NIAGARA || sparc_cpu == PROCESSOR_NIAGARA2 || sparc_cpu == PROCESSOR_NIAGARA3 ! || sparc_cpu == PROCESSOR_NIAGARA4 ! || sparc_cpu == PROCESSOR_NIAGARA7)) ! align_functions = 32; /* Validate PCC_STRUCT_RETURN. */ if (flag_pcc_struct_return == DEFAULT_PCC_STRUCT_RETURN) --- 1503,1520 ---- target_flags &= ~MASK_STACK_BIAS; /* Supply a default value for align_functions. */ ! if (align_functions == 0) ! { ! if (sparc_cpu == PROCESSOR_ULTRASPARC || sparc_cpu == PROCESSOR_ULTRASPARC3 || sparc_cpu == PROCESSOR_NIAGARA || sparc_cpu == PROCESSOR_NIAGARA2 || sparc_cpu == PROCESSOR_NIAGARA3 ! || sparc_cpu == PROCESSOR_NIAGARA4) ! align_functions = 32; ! else if (sparc_cpu == PROCESSOR_NIAGARA7) ! align_functions = 64; ! } /* Validate PCC_STRUCT_RETURN. */ if (flag_pcc_struct_return == DEFAULT_PCC_STRUCT_RETURN) *************** sparc_expand_epilogue (bool for_eh) *** 5753,5758 **** --- 5756,5764 ---- { HOST_WIDE_INT size = sparc_frame_size; + if (cfun->calls_alloca) + emit_insn (gen_frame_blockage ()); + if (sparc_n_global_fp_regs > 0) emit_save_or_restore_global_fp_regs (sparc_frame_base_reg, sparc_frame_base_offset *************** sparc_frame_pointer_required (void) *** 11970,11977 **** if (TARGET_FLAT) return false; ! /* Otherwise, the frame pointer is required if the function isn't leaf. */ ! return !(crtl->is_leaf && only_leaf_regs_used ()); } /* The way this is structured, we can't eliminate SFP in favor of SP --- 11976,11984 ---- if (TARGET_FLAT) return false; ! /* Otherwise, the frame pointer is required if the function isn't leaf, but ! we cannot use sparc_leaf_function_p since it hasn't been computed yet. */ ! return !(optimize > 0 && crtl->is_leaf && only_leaf_regs_used ()); } /* The way this is structured, we can't eliminate SFP in favor of SP diff -Nrcpad gcc-6.3.0/gcc/config/sparc/sparc.h gcc-6.4.0/gcc/config/sparc/sparc.h *** gcc-6.3.0/gcc/config/sparc/sparc.h Wed Jun 8 13:34:25 2016 --- gcc-6.4.0/gcc/config/sparc/sparc.h Tue May 23 18:54:17 2017 *************** do { \ *** 1570,1576 **** and annulled branches insert 4 bubbles. On Niagara-2 and Niagara-3, a not-taken branch costs 1 cycle whereas ! a taken branch costs 6 cycles. */ #define BRANCH_COST(speed_p, predictable_p) \ ((sparc_cpu == PROCESSOR_V9 \ --- 1570,1579 ---- and annulled branches insert 4 bubbles. On Niagara-2 and Niagara-3, a not-taken branch costs 1 cycle whereas ! a taken branch costs 6 cycles. ! ! The T4 Supplement specifies the branch latency at 2 cycles. ! The M7 Supplement specifies the branch latency at 1 cycle. */ #define BRANCH_COST(speed_p, predictable_p) \ ((sparc_cpu == PROCESSOR_V9 \ *************** do { \ *** 1583,1589 **** : ((sparc_cpu == PROCESSOR_NIAGARA2 \ || sparc_cpu == PROCESSOR_NIAGARA3) \ ? 5 \ ! : 3)))) /* Control the assembler format that we output. */ --- 1586,1596 ---- : ((sparc_cpu == PROCESSOR_NIAGARA2 \ || sparc_cpu == PROCESSOR_NIAGARA3) \ ? 5 \ ! : (sparc_cpu == PROCESSOR_NIAGARA4 \ ! ? 2 \ ! : (sparc_cpu == PROCESSOR_NIAGARA7 \ ! ? 1 \ ! : 3)))))) /* Control the assembler format that we output. */ diff -Nrcpad gcc-6.3.0/gcc/config/sparc/sparc.md gcc-6.4.0/gcc/config/sparc/sparc.md *** gcc-6.3.0/gcc/config/sparc/sparc.md Sun Oct 23 20:31:56 2016 --- gcc-6.4.0/gcc/config/sparc/sparc.md Fri Jun 9 19:24:51 2017 *************** *** 331,337 **** (const_int 2) (const_int 1)) (eq_attr "type" "sibcall") ! (if_then_else (eq_attr "leaf_function" "true") (if_then_else (eq_attr "empty_delay_slot" "true") (const_int 3) (const_int 2)) --- 331,338 ---- (const_int 2) (const_int 1)) (eq_attr "type" "sibcall") ! (if_then_else (ior (eq_attr "leaf_function" "true") ! (eq_attr "flat" "true")) (if_then_else (eq_attr "empty_delay_slot" "true") (const_int 3) (const_int 2)) *************** *** 6427,6433 **** (define_expand "return" [(return)] "sparc_can_use_return_insn_p ()" ! "") (define_insn "*return_internal" [(return)] --- 6428,6437 ---- (define_expand "return" [(return)] "sparc_can_use_return_insn_p ()" ! { ! if (cfun->calls_alloca) ! emit_insn (gen_frame_blockage ()); ! }) (define_insn "*return_internal" [(return)] diff -Nrcpad gcc-6.3.0/gcc/config/tilegx/tilegx.c gcc-6.4.0/gcc/config/tilegx/tilegx.c *** gcc-6.3.0/gcc/config/tilegx/tilegx.c Sat Nov 19 03:11:57 2016 --- gcc-6.4.0/gcc/config/tilegx/tilegx.c Fri Feb 3 18:46:57 2017 *************** tilegx_expand_prologue (void) *** 3996,4003 **** /* Save lr first in its special location because code after this might use the link register as a scratch register. */ if (df_regs_ever_live_p (TILEGX_LINK_REGNUM) || crtl->calls_eh_return) ! FRP (frame_emit_store (TILEGX_LINK_REGNUM, TILEGX_LINK_REGNUM, ! stack_pointer_rtx, stack_pointer_rtx, 0)); if (total_size == 0) { --- 3996,4006 ---- /* Save lr first in its special location because code after this might use the link register as a scratch register. */ if (df_regs_ever_live_p (TILEGX_LINK_REGNUM) || crtl->calls_eh_return) ! { ! FRP (frame_emit_store (TILEGX_LINK_REGNUM, TILEGX_LINK_REGNUM, ! stack_pointer_rtx, stack_pointer_rtx, 0)); ! emit_insn (gen_blockage ()); ! } if (total_size == 0) { diff -Nrcpad gcc-6.3.0/gcc/config/tilepro/tilepro.c gcc-6.4.0/gcc/config/tilepro/tilepro.c *** gcc-6.3.0/gcc/config/tilepro/tilepro.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/tilepro/tilepro.c Fri Feb 3 18:46:57 2017 *************** tilepro_expand_prologue (void) *** 3534,3541 **** /* Save lr first in its special location because code after this might use the link register as a scratch register. */ if (df_regs_ever_live_p (TILEPRO_LINK_REGNUM) || crtl->calls_eh_return) ! FRP (frame_emit_store (TILEPRO_LINK_REGNUM, TILEPRO_LINK_REGNUM, ! stack_pointer_rtx, stack_pointer_rtx, 0)); if (total_size == 0) { --- 3534,3544 ---- /* Save lr first in its special location because code after this might use the link register as a scratch register. */ if (df_regs_ever_live_p (TILEPRO_LINK_REGNUM) || crtl->calls_eh_return) ! { ! FRP (frame_emit_store (TILEPRO_LINK_REGNUM, TILEPRO_LINK_REGNUM, ! stack_pointer_rtx, stack_pointer_rtx, 0)); ! emit_insn (gen_blockage ()); ! } if (total_size == 0) { diff -Nrcpad gcc-6.3.0/gcc/config/xtensa/xtensa-protos.h gcc-6.4.0/gcc/config/xtensa/xtensa-protos.h *** gcc-6.3.0/gcc/config/xtensa/xtensa-protos.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/xtensa/xtensa-protos.h Wed May 31 00:05:01 2017 *************** extern rtx xtensa_return_addr (int, rtx) *** 68,73 **** --- 68,74 ---- extern void xtensa_setup_frame_addresses (void); extern int xtensa_dbx_register_number (int); extern long compute_frame_size (int); + extern bool xtensa_use_return_instruction_p (void); extern void xtensa_expand_prologue (void); extern void xtensa_expand_epilogue (void); extern void order_regs_for_local_alloc (void); diff -Nrcpad gcc-6.3.0/gcc/config/xtensa/xtensa.c gcc-6.4.0/gcc/config/xtensa/xtensa.c *** gcc-6.3.0/gcc/config/xtensa/xtensa.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/xtensa/xtensa.c Wed May 31 00:06:11 2017 *************** enum internal_test *** 78,88 **** can support a given mode. */ char xtensa_hard_regno_mode_ok[(int) MAX_MACHINE_MODE][FIRST_PSEUDO_REGISTER]; - /* Current frame size calculated by compute_frame_size. */ - unsigned xtensa_current_frame_size; - /* Callee-save area size in the current frame calculated by compute_frame_size. */ - int xtensa_callee_save_size; - /* Largest block move to handle in-line. */ #define LARGEST_MOVE_RATIO 15 --- 78,83 ---- *************** struct GTY(()) machine_function *** 94,99 **** --- 89,101 ---- bool vararg_a7; rtx vararg_a7_copy; rtx_insn *set_frame_ptr_insn; + /* Current frame size calculated by compute_frame_size. */ + unsigned current_frame_size; + /* Callee-save area size in the current frame calculated by + compute_frame_size. */ + int callee_save_size; + bool frame_laid_out; + bool epilogue_done; }; /* Vector, indexed by hard register number, which contains 1 for a *************** xtensa_emit_call (int callop, rtx *opera *** 1774,1780 **** rtx tgt = operands[callop]; if (GET_CODE (tgt) == CONST_INT) ! sprintf (result, "call%d\t0x%lx", WINDOW_SIZE, INTVAL (tgt)); else if (register_operand (tgt, VOIDmode)) sprintf (result, "callx%d\t%%%d", WINDOW_SIZE, callop); else --- 1776,1783 ---- rtx tgt = operands[callop]; if (GET_CODE (tgt) == CONST_INT) ! sprintf (result, "call%d\t" HOST_WIDE_INT_PRINT_HEX, ! WINDOW_SIZE, INTVAL (tgt)); else if (register_operand (tgt, VOIDmode)) sprintf (result, "callx%d\t%%%d", WINDOW_SIZE, callop); else *************** print_operand (FILE *file, rtx x, int le *** 2345,2358 **** case 'L': if (GET_CODE (x) == CONST_INT) ! fprintf (file, "%ld", (32 - INTVAL (x)) & 0x1f); else output_operand_lossage ("invalid %%L value"); break; case 'R': if (GET_CODE (x) == CONST_INT) ! fprintf (file, "%ld", INTVAL (x) & 0x1f); else output_operand_lossage ("invalid %%R value"); break; --- 2348,2361 ---- case 'L': if (GET_CODE (x) == CONST_INT) ! fprintf (file, HOST_WIDE_INT_PRINT_DEC, (32 - INTVAL (x)) & 0x1f); else output_operand_lossage ("invalid %%L value"); break; case 'R': if (GET_CODE (x) == CONST_INT) ! fprintf (file, HOST_WIDE_INT_PRINT_DEC, INTVAL (x) & 0x1f); else output_operand_lossage ("invalid %%R value"); break; *************** print_operand (FILE *file, rtx x, int le *** 2366,2372 **** case 'd': if (GET_CODE (x) == CONST_INT) ! fprintf (file, "%ld", INTVAL (x)); else output_operand_lossage ("invalid %%d value"); break; --- 2369,2375 ---- case 'd': if (GET_CODE (x) == CONST_INT) ! fprintf (file, HOST_WIDE_INT_PRINT_DEC, INTVAL (x)); else output_operand_lossage ("invalid %%d value"); break; *************** print_operand (FILE *file, rtx x, int le *** 2431,2437 **** else if (GET_CODE (x) == MEM) output_address (GET_MODE (x), XEXP (x, 0)); else if (GET_CODE (x) == CONST_INT) ! fprintf (file, "%ld", INTVAL (x)); else output_addr_const (file, x); } --- 2434,2440 ---- else if (GET_CODE (x) == MEM) output_address (GET_MODE (x), XEXP (x, 0)); else if (GET_CODE (x) == CONST_INT) ! fprintf (file, HOST_WIDE_INT_PRINT_DEC, INTVAL (x)); else output_addr_const (file, x); } *************** compute_frame_size (int size) *** 2628,2651 **** { int regno; /* Add space for the incoming static chain value. */ if (cfun->static_chain_decl != NULL) size += (1 * UNITS_PER_WORD); ! xtensa_callee_save_size = 0; for (regno = 0; regno < FIRST_PSEUDO_REGISTER; ++regno) { if (xtensa_call_save_reg(regno)) ! xtensa_callee_save_size += UNITS_PER_WORD; } ! xtensa_current_frame_size = XTENSA_STACK_ALIGN (size ! + xtensa_callee_save_size + crtl->outgoing_args_size + (WINDOW_SIZE * UNITS_PER_WORD)); ! xtensa_callee_save_size = XTENSA_STACK_ALIGN (xtensa_callee_save_size); ! return xtensa_current_frame_size; } --- 2631,2659 ---- { int regno; + if (reload_completed && cfun->machine->frame_laid_out) + return cfun->machine->current_frame_size; + /* Add space for the incoming static chain value. */ if (cfun->static_chain_decl != NULL) size += (1 * UNITS_PER_WORD); ! cfun->machine->callee_save_size = 0; for (regno = 0; regno < FIRST_PSEUDO_REGISTER; ++regno) { if (xtensa_call_save_reg(regno)) ! cfun->machine->callee_save_size += UNITS_PER_WORD; } ! cfun->machine->current_frame_size = XTENSA_STACK_ALIGN (size ! + cfun->machine->callee_save_size + crtl->outgoing_args_size + (WINDOW_SIZE * UNITS_PER_WORD)); ! cfun->machine->callee_save_size = ! XTENSA_STACK_ALIGN (cfun->machine->callee_save_size); ! cfun->machine->frame_laid_out = true; ! return cfun->machine->current_frame_size; } *************** xtensa_expand_prologue (void) *** 2696,2701 **** --- 2704,2710 ---- { int regno; HOST_WIDE_INT offset = 0; + int callee_save_size = cfun->machine->callee_save_size; /* -128 is a limit of single addi instruction. */ if (total_size > 0 && total_size <= 128) *************** xtensa_expand_prologue (void) *** 2709,2715 **** add_reg_note (insn, REG_FRAME_RELATED_EXPR, note_rtx); offset = total_size - UNITS_PER_WORD; } ! else if (xtensa_callee_save_size) { /* 1020 is maximal s32i offset, if the frame is bigger than that * we move sp to the end of callee-saved save area, save and then --- 2718,2724 ---- add_reg_note (insn, REG_FRAME_RELATED_EXPR, note_rtx); offset = total_size - UNITS_PER_WORD; } ! else if (callee_save_size) { /* 1020 is maximal s32i offset, if the frame is bigger than that * we move sp to the end of callee-saved save area, save and then *************** xtensa_expand_prologue (void) *** 2717,2729 **** if (total_size > 1024) { insn = emit_insn (gen_addsi3 (stack_pointer_rtx, stack_pointer_rtx, ! GEN_INT (-xtensa_callee_save_size))); RTX_FRAME_RELATED_P (insn) = 1; note_rtx = gen_rtx_SET (stack_pointer_rtx, plus_constant (Pmode, stack_pointer_rtx, ! -xtensa_callee_save_size)); add_reg_note (insn, REG_FRAME_RELATED_EXPR, note_rtx); ! offset = xtensa_callee_save_size - UNITS_PER_WORD; } else { --- 2726,2738 ---- if (total_size > 1024) { insn = emit_insn (gen_addsi3 (stack_pointer_rtx, stack_pointer_rtx, ! GEN_INT (-callee_save_size))); RTX_FRAME_RELATED_P (insn) = 1; note_rtx = gen_rtx_SET (stack_pointer_rtx, plus_constant (Pmode, stack_pointer_rtx, ! -callee_save_size)); add_reg_note (insn, REG_FRAME_RELATED_EXPR, note_rtx); ! offset = callee_save_size - UNITS_PER_WORD; } else { *************** xtensa_expand_prologue (void) *** 2759,2771 **** { rtx tmp_reg = gen_rtx_REG (Pmode, A9_REG); emit_move_insn (tmp_reg, GEN_INT (total_size - ! xtensa_callee_save_size)); insn = emit_insn (gen_subsi3 (stack_pointer_rtx, stack_pointer_rtx, tmp_reg)); RTX_FRAME_RELATED_P (insn) = 1; note_rtx = gen_rtx_SET (stack_pointer_rtx, plus_constant (Pmode, stack_pointer_rtx, ! xtensa_callee_save_size - total_size)); add_reg_note (insn, REG_FRAME_RELATED_EXPR, note_rtx); } --- 2768,2780 ---- { rtx tmp_reg = gen_rtx_REG (Pmode, A9_REG); emit_move_insn (tmp_reg, GEN_INT (total_size - ! callee_save_size)); insn = emit_insn (gen_subsi3 (stack_pointer_rtx, stack_pointer_rtx, tmp_reg)); RTX_FRAME_RELATED_P (insn) = 1; note_rtx = gen_rtx_SET (stack_pointer_rtx, plus_constant (Pmode, stack_pointer_rtx, ! callee_save_size - total_size)); add_reg_note (insn, REG_FRAME_RELATED_EXPR, note_rtx); } *************** xtensa_expand_epilogue (void) *** 2833,2853 **** int regno; HOST_WIDE_INT offset; ! if (xtensa_current_frame_size > (frame_pointer_needed ? 127 : 1024)) { rtx tmp_reg = gen_rtx_REG (Pmode, A9_REG); ! emit_move_insn (tmp_reg, GEN_INT (xtensa_current_frame_size - ! xtensa_callee_save_size)); emit_insn (gen_addsi3 (stack_pointer_rtx, frame_pointer_needed ? hard_frame_pointer_rtx : stack_pointer_rtx, tmp_reg)); ! offset = xtensa_callee_save_size - UNITS_PER_WORD; } else { if (frame_pointer_needed) emit_move_insn (stack_pointer_rtx, hard_frame_pointer_rtx); ! offset = xtensa_current_frame_size - UNITS_PER_WORD; } /* Prevent reordering of saved a0 update and loading it back from --- 2842,2862 ---- int regno; HOST_WIDE_INT offset; ! if (cfun->machine->current_frame_size > (frame_pointer_needed ? 127 : 1024)) { rtx tmp_reg = gen_rtx_REG (Pmode, A9_REG); ! emit_move_insn (tmp_reg, GEN_INT (cfun->machine->current_frame_size - ! cfun->machine->callee_save_size)); emit_insn (gen_addsi3 (stack_pointer_rtx, frame_pointer_needed ? hard_frame_pointer_rtx : stack_pointer_rtx, tmp_reg)); ! offset = cfun->machine->callee_save_size - UNITS_PER_WORD; } else { if (frame_pointer_needed) emit_move_insn (stack_pointer_rtx, hard_frame_pointer_rtx); ! offset = cfun->machine->current_frame_size - UNITS_PER_WORD; } /* Prevent reordering of saved a0 update and loading it back from *************** xtensa_expand_epilogue (void) *** 2867,2882 **** } } ! if (xtensa_current_frame_size > 0) { if (frame_pointer_needed || /* always reachable with addi */ ! xtensa_current_frame_size > 1024 || ! xtensa_current_frame_size <= 127) { ! if (xtensa_current_frame_size <= 127) ! offset = xtensa_current_frame_size; else ! offset = xtensa_callee_save_size; emit_insn (gen_addsi3 (stack_pointer_rtx, stack_pointer_rtx, --- 2876,2891 ---- } } ! if (cfun->machine->current_frame_size > 0) { if (frame_pointer_needed || /* always reachable with addi */ ! cfun->machine->current_frame_size > 1024 || ! cfun->machine->current_frame_size <= 127) { ! if (cfun->machine->current_frame_size <= 127) ! offset = cfun->machine->current_frame_size; else ! offset = cfun->machine->callee_save_size; emit_insn (gen_addsi3 (stack_pointer_rtx, stack_pointer_rtx, *************** xtensa_expand_epilogue (void) *** 2885,2891 **** else { rtx tmp_reg = gen_rtx_REG (Pmode, A9_REG); ! emit_move_insn (tmp_reg, GEN_INT (xtensa_current_frame_size)); emit_insn (gen_addsi3 (stack_pointer_rtx, stack_pointer_rtx, tmp_reg)); } --- 2894,2901 ---- else { rtx tmp_reg = gen_rtx_REG (Pmode, A9_REG); ! emit_move_insn (tmp_reg, ! GEN_INT (cfun->machine->current_frame_size)); emit_insn (gen_addsi3 (stack_pointer_rtx, stack_pointer_rtx, tmp_reg)); } *************** xtensa_expand_epilogue (void) *** 2896,2906 **** stack_pointer_rtx, EH_RETURN_STACKADJ_RTX)); } ! xtensa_current_frame_size = 0; ! xtensa_callee_save_size = 0; emit_jump_insn (gen_return ()); } void xtensa_set_return_address (rtx address, rtx scratch) { --- 2906,2927 ---- stack_pointer_rtx, EH_RETURN_STACKADJ_RTX)); } ! cfun->machine->epilogue_done = true; emit_jump_insn (gen_return ()); } + bool + xtensa_use_return_instruction_p (void) + { + if (!reload_completed) + return false; + if (TARGET_WINDOWED_ABI) + return true; + if (compute_frame_size (get_frame_size ()) == 0) + return true; + return cfun->machine->epilogue_done; + } + void xtensa_set_return_address (rtx address, rtx scratch) { *************** hwloop_optimize (hwloop_info loop) *** 4138,4144 **** entry_after = BB_END (entry_bb); while (DEBUG_INSN_P (entry_after) || (NOTE_P (entry_after) ! && NOTE_KIND (entry_after) != NOTE_INSN_BASIC_BLOCK)) entry_after = PREV_INSN (entry_after); emit_insn_after (seq, entry_after); --- 4159,4168 ---- entry_after = BB_END (entry_bb); while (DEBUG_INSN_P (entry_after) || (NOTE_P (entry_after) ! && NOTE_KIND (entry_after) != NOTE_INSN_BASIC_BLOCK ! /* Make sure we don't split a call and its corresponding ! CALL_ARG_LOCATION note. */ ! && NOTE_KIND (entry_after) != NOTE_INSN_CALL_ARG_LOCATION)) entry_after = PREV_INSN (entry_after); emit_insn_after (seq, entry_after); diff -Nrcpad gcc-6.3.0/gcc/config/xtensa/xtensa.h gcc-6.4.0/gcc/config/xtensa/xtensa.h *** gcc-6.3.0/gcc/config/xtensa/xtensa.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/xtensa/xtensa.h Wed May 31 00:05:01 2017 *************** along with GCC; see the file COPYING3. *** 23,30 **** /* External variables defined in xtensa.c. */ - extern unsigned xtensa_current_frame_size; - /* Macros used in the machine description to select various Xtensa configuration options. */ #ifndef XCHAL_HAVE_MUL32_HIGH --- 23,28 ---- *************** enum reg_class *** 477,490 **** /* Specify the initial difference between the specified pair of registers. */ #define INITIAL_ELIMINATION_OFFSET(FROM, TO, OFFSET) \ do { \ ! compute_frame_size (get_frame_size ()); \ switch (FROM) \ { \ case FRAME_POINTER_REGNUM: \ (OFFSET) = 0; \ break; \ case ARG_POINTER_REGNUM: \ ! (OFFSET) = xtensa_current_frame_size; \ break; \ default: \ gcc_unreachable (); \ --- 475,488 ---- /* Specify the initial difference between the specified pair of registers. */ #define INITIAL_ELIMINATION_OFFSET(FROM, TO, OFFSET) \ do { \ ! long frame_size = compute_frame_size (get_frame_size ()); \ switch (FROM) \ { \ case FRAME_POINTER_REGNUM: \ (OFFSET) = 0; \ break; \ case ARG_POINTER_REGNUM: \ ! (OFFSET) = frame_size; \ break; \ default: \ gcc_unreachable (); \ diff -Nrcpad gcc-6.3.0/gcc/config/xtensa/xtensa.md gcc-6.4.0/gcc/config/xtensa/xtensa.md *** gcc-6.3.0/gcc/config/xtensa/xtensa.md Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config/xtensa/xtensa.md Wed May 31 00:05:01 2017 *************** *** 1663,1669 **** (define_insn "return" [(return) (use (reg:SI A0_REG))] ! "(TARGET_WINDOWED_ABI || !xtensa_current_frame_size) && reload_completed" { return TARGET_WINDOWED_ABI ? (TARGET_DENSITY ? "retw.n" : "retw") : --- 1663,1669 ---- (define_insn "return" [(return) (use (reg:SI A0_REG))] ! "xtensa_use_return_instruction_p ()" { return TARGET_WINDOWED_ABI ? (TARGET_DENSITY ? "retw.n" : "retw") : diff -Nrcpad gcc-6.3.0/gcc/config.gcc gcc-6.4.0/gcc/config.gcc *** gcc-6.3.0/gcc/config.gcc Mon Nov 7 21:38:43 2016 --- gcc-6.4.0/gcc/config.gcc Mon Jan 9 21:01:26 2017 *************** aarch64*-*-elf | aarch64*-*-rtems*) *** 946,951 **** --- 946,956 ---- done TM_MULTILIB_CONFIG=`echo $TM_MULTILIB_CONFIG | sed 's/^,//'` ;; + aarch64*-*-freebsd*) + tm_file="${tm_file} dbxelf.h elfos.h ${fbsd_tm_file}" + tm_file="${tm_file} aarch64/aarch64-elf.h aarch64/aarch64-freebsd.h" + tmake_file="${tmake_file} aarch64/t-aarch64 aarch64/t-aarch64-freebsd" + ;; aarch64*-*-linux*) tm_file="${tm_file} dbxelf.h elfos.h gnu-user.h linux.h glibc-stdint.h" tm_file="${tm_file} aarch64/aarch64-elf.h aarch64/aarch64-linux.h" diff -Nrcpad gcc-6.3.0/gcc/config.host gcc-6.4.0/gcc/config.host *** gcc-6.3.0/gcc/config.host Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/config.host Mon Jan 9 21:01:26 2017 *************** case ${host} in *** 99,105 **** esac case ${host} in ! aarch64*-*-linux*) case ${target} in aarch64*-*-*) host_extra_gcc_objs="driver-aarch64.o" --- 99,105 ---- esac case ${host} in ! aarch64*-*-freebsd* | aarch64*-*-linux*) case ${target} in aarch64*-*-*) host_extra_gcc_objs="driver-aarch64.o" diff -Nrcpad gcc-6.3.0/gcc/convert.c gcc-6.4.0/gcc/convert.c *** gcc-6.3.0/gcc/convert.c Fri Dec 9 14:04:53 2016 --- gcc-6.4.0/gcc/convert.c Thu Jun 22 07:30:03 2017 *************** convert_to_real_maybe_fold (tree type, t *** 411,416 **** --- 411,493 ---- return convert_to_real_1 (type, expr, dofold || CONSTANT_CLASS_P (expr)); } + /* Try to narrow EX_FORM ARG0 ARG1 in narrowed arg types producing a + result in TYPE. */ + + static tree + do_narrow (location_t loc, + enum tree_code ex_form, tree type, tree arg0, tree arg1, + tree expr, unsigned inprec, unsigned outprec, bool dofold) + { + /* Do the arithmetic in type TYPEX, + then convert result to TYPE. */ + tree typex = type; + + /* Can't do arithmetic in enumeral types + so use an integer type that will hold the values. */ + if (TREE_CODE (typex) == ENUMERAL_TYPE) + typex = lang_hooks.types.type_for_size (TYPE_PRECISION (typex), + TYPE_UNSIGNED (typex)); + + /* But now perhaps TYPEX is as wide as INPREC. + In that case, do nothing special here. + (Otherwise would recurse infinitely in convert. */ + if (TYPE_PRECISION (typex) != inprec) + { + /* Don't do unsigned arithmetic where signed was wanted, + or vice versa. + Exception: if both of the original operands were + unsigned then we can safely do the work as unsigned. + Exception: shift operations take their type solely + from the first argument. + Exception: the LSHIFT_EXPR case above requires that + we perform this operation unsigned lest we produce + signed-overflow undefinedness. + And we may need to do it as unsigned + if we truncate to the original size. */ + if (TYPE_UNSIGNED (TREE_TYPE (expr)) + || (TYPE_UNSIGNED (TREE_TYPE (arg0)) + && (TYPE_UNSIGNED (TREE_TYPE (arg1)) + || ex_form == LSHIFT_EXPR + || ex_form == RSHIFT_EXPR + || ex_form == LROTATE_EXPR + || ex_form == RROTATE_EXPR)) + || ex_form == LSHIFT_EXPR + /* If we have !flag_wrapv, and either ARG0 or + ARG1 is of a signed type, we have to do + PLUS_EXPR, MINUS_EXPR or MULT_EXPR in an unsigned + type in case the operation in outprec precision + could overflow. Otherwise, we would introduce + signed-overflow undefinedness. */ + || ((!TYPE_OVERFLOW_WRAPS (TREE_TYPE (arg0)) + || !TYPE_OVERFLOW_WRAPS (TREE_TYPE (arg1))) + && ((TYPE_PRECISION (TREE_TYPE (arg0)) * 2u + > outprec) + || (TYPE_PRECISION (TREE_TYPE (arg1)) * 2u + > outprec)) + && (ex_form == PLUS_EXPR + || ex_form == MINUS_EXPR + || ex_form == MULT_EXPR))) + { + if (!TYPE_UNSIGNED (typex)) + typex = unsigned_type_for (typex); + } + else + { + if (TYPE_UNSIGNED (typex)) + typex = signed_type_for (typex); + } + /* We should do away with all this once we have a proper + type promotion/demotion pass, see PR45397. */ + expr = maybe_fold_build2_loc (dofold, loc, ex_form, typex, + convert (typex, arg0), + convert (typex, arg1)); + return convert (type, expr); + } + + return NULL_TREE; + } + /* Convert EXPR to some integer (or enum) type TYPE. EXPR must be pointer, integer, discrete (enum, char, or bool), float, *************** convert_to_integer_1 (tree type, tree ex *** 717,724 **** case TRUNC_DIV_EXPR: { ! tree arg0 = get_unwidened (TREE_OPERAND (expr, 0), type); ! tree arg1 = get_unwidened (TREE_OPERAND (expr, 1), type); /* Don't distribute unless the output precision is at least as big as the actual inputs and it has the same signedness. */ --- 794,801 ---- case TRUNC_DIV_EXPR: { ! tree arg0 = get_unwidened (TREE_OPERAND (expr, 0), NULL_TREE); ! tree arg1 = get_unwidened (TREE_OPERAND (expr, 1), NULL_TREE); /* Don't distribute unless the output precision is at least as big as the actual inputs and it has the same signedness. */ *************** convert_to_integer_1 (tree type, tree ex *** 736,742 **** && (TYPE_UNSIGNED (TREE_TYPE (arg0)) || (TREE_CODE (arg1) == INTEGER_CST && !integer_all_onesp (arg1)))) ! goto trunc1; break; } --- 813,824 ---- && (TYPE_UNSIGNED (TREE_TYPE (arg0)) || (TREE_CODE (arg1) == INTEGER_CST && !integer_all_onesp (arg1)))) ! { ! tree tem = do_narrow (loc, ex_form, type, arg0, arg1, ! expr, inprec, outprec, dofold); ! if (tem) ! return tem; ! } break; } *************** convert_to_integer_1 (tree type, tree ex *** 784,855 **** || inprec > TYPE_PRECISION (TREE_TYPE (arg0)) || inprec > TYPE_PRECISION (TREE_TYPE (arg1))) { ! /* Do the arithmetic in type TYPEX, ! then convert result to TYPE. */ ! tree typex = type; ! ! /* Can't do arithmetic in enumeral types ! so use an integer type that will hold the values. */ ! if (TREE_CODE (typex) == ENUMERAL_TYPE) ! typex ! = lang_hooks.types.type_for_size (TYPE_PRECISION (typex), ! TYPE_UNSIGNED (typex)); ! ! /* But now perhaps TYPEX is as wide as INPREC. ! In that case, do nothing special here. ! (Otherwise would recurse infinitely in convert. */ ! if (TYPE_PRECISION (typex) != inprec) ! { ! /* Don't do unsigned arithmetic where signed was wanted, ! or vice versa. ! Exception: if both of the original operands were ! unsigned then we can safely do the work as unsigned. ! Exception: shift operations take their type solely ! from the first argument. ! Exception: the LSHIFT_EXPR case above requires that ! we perform this operation unsigned lest we produce ! signed-overflow undefinedness. ! And we may need to do it as unsigned ! if we truncate to the original size. */ ! if (TYPE_UNSIGNED (TREE_TYPE (expr)) ! || (TYPE_UNSIGNED (TREE_TYPE (arg0)) ! && (TYPE_UNSIGNED (TREE_TYPE (arg1)) ! || ex_form == LSHIFT_EXPR ! || ex_form == RSHIFT_EXPR ! || ex_form == LROTATE_EXPR ! || ex_form == RROTATE_EXPR)) ! || ex_form == LSHIFT_EXPR ! /* If we have !flag_wrapv, and either ARG0 or ! ARG1 is of a signed type, we have to do ! PLUS_EXPR, MINUS_EXPR or MULT_EXPR in an unsigned ! type in case the operation in outprec precision ! could overflow. Otherwise, we would introduce ! signed-overflow undefinedness. */ ! || ((!TYPE_OVERFLOW_WRAPS (TREE_TYPE (arg0)) ! || !TYPE_OVERFLOW_WRAPS (TREE_TYPE (arg1))) ! && ((TYPE_PRECISION (TREE_TYPE (arg0)) * 2u ! > outprec) ! || (TYPE_PRECISION (TREE_TYPE (arg1)) * 2u ! > outprec)) ! && (ex_form == PLUS_EXPR ! || ex_form == MINUS_EXPR ! || ex_form == MULT_EXPR))) ! { ! if (!TYPE_UNSIGNED (typex)) ! typex = unsigned_type_for (typex); ! } ! else ! { ! if (TYPE_UNSIGNED (typex)) ! typex = signed_type_for (typex); ! } ! /* We should do away with all this once we have a proper ! type promotion/demotion pass, see PR45397. */ ! expr = maybe_fold_build2_loc (dofold, loc, ex_form, typex, ! convert (typex, arg0), ! convert (typex, arg1)); ! return convert (type, expr); ! } } } break; --- 866,875 ---- || inprec > TYPE_PRECISION (TREE_TYPE (arg0)) || inprec > TYPE_PRECISION (TREE_TYPE (arg1))) { ! tree tem = do_narrow (loc, ex_form, type, arg0, arg1, ! expr, inprec, outprec, dofold); ! if (tem) ! return tem; } } break; diff -Nrcpad gcc-6.3.0/gcc/coverage.c gcc-6.4.0/gcc/coverage.c *** gcc-6.3.0/gcc/coverage.c Tue Mar 29 19:37:55 2016 --- gcc-6.4.0/gcc/coverage.c Thu Jun 22 11:16:39 2017 *************** coverage_end_function (unsigned lineno_c *** 725,730 **** --- 725,742 ---- } } + /* Remove coverage file if opened. */ + + void + coverage_remove_note_file (void) + { + if (bbg_file_name) + { + gcov_close (); + unlink (bbg_file_name); + } + } + /* Build a coverage variable of TYPE for function FN_DECL. If COUNTER >= 0 it is a counter array, otherwise it is the function structure. */ diff -Nrcpad gcc-6.3.0/gcc/coverage.h gcc-6.4.0/gcc/coverage.h *** gcc-6.3.0/gcc/coverage.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/coverage.h Thu Jun 22 11:16:39 2017 *************** along with GCC; see the file COPYING3. *** 24,29 **** --- 24,30 ---- extern void coverage_init (const char *); extern void coverage_finish (void); + extern void coverage_remove_note_file (void); /* Start outputting coverage information for the current function. */ diff -Nrcpad gcc-6.3.0/gcc/cp/ChangeLog gcc-6.4.0/gcc/cp/ChangeLog *** gcc-6.3.0/gcc/cp/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/cp/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,331 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-06-24 Marek Polacek + + Backported from mainline + 2017-04-18 Marek Polacek + + PR c++/80241 - ICE with alignas pack expansion. + * error.c (dump_expr): Handle TREE_LIST. + * parser.c (cp_parser_std_attribute_list): Return error_mark if + make_pack_expansion returns an error. + + PR c++/80244 - ICE with attribute in template alias. + * tree.c (strip_typedefs): Handle UNDERLYING_TYPE. + + 2017-04-10 Marek Polacek + + PR sanitizer/80348 + * typeck.c (cp_build_binary_op): Use NULL_TREE instead of NULL. Set + ORIG_TYPE earlier and not only when shortening. + + 2017-04-07 Marek Polacek + + PR sanitizer/80348 + * typeck.c (cp_build_binary_op): Convert COP[01] to ORIG_TYPE. + + 2017-06-22 Jakub Jelinek + + Backported from mainline + 2017-06-21 Jakub Jelinek + + PR c++/81154 + * semantics.c (handle_omp_array_sections_1, finish_omp_clauses): + Complain about t not being a variable if t is OVERLOAD even + when processing_template_decl. + + 2017-06-13 Jakub Jelinek + + PR c++/80973 + * cp-gimplify.c (cp_genericize_r): Don't instrument MEM_REF second + argument even if it has REFERENCE_TYPE. + + PR c++/80984 + * cp-gimplify.c (cp_genericize): Only look for VAR_DECLs in + BLOCK_VARS (outer) chain. + (cxx_omp_const_qual_no_mutable): Likewise. + + 2017-06-17 Jason Merrill + + PR c++/70844 - -Wuseless-cast and inheriting constructor. + * method.c (forward_parm): Suppress warn_useless_cast. + + 2017-06-08 Jakub Jelinek + + PR c/81006 + * semantics.c (handle_omp_array_sections_1): Convert TYPE_MAX_VALUE + to sizetype before size_binop. + + PR c++/81011 + * cp-gimplify.c (cxx_omp_finish_clause): When changing clause + to OMP_CLAUSE_SHARED, also clear OMP_CLAUSE_SHARED_FIRSTPRIVATE + and OMP_CLAUSE_SHARED_READONLY flags. + + 2017-05-31 Jason Merrill + + PR c++/80179 - ICE with initialized flexible array member. + * constexpr.c (verify_ctor_sanity): Handle flexible array members. + + 2017-05-23 Jason Merrill + + PR c++/80267 - ICE with nested capture of reference + PR c++/60992 + * pt.c (tsubst_copy): Handle lookup finding a capture proxy. + + PR c++/80294 - ICE with constexpr and inheritance. + * constexpr.c (reduced_constant_expression_p): + A null constructor element is non-constant. + (cxx_eval_indirect_ref): Don't VERIFY_CONSTANT before + returning an empty base. + + 2017-05-05 Jakub Jelinek + + Backported from mainline + 2017-04-11 Jakub Jelinek + + PR c++/80363 + * error.c (dump_expr): Handle VEC_COND_EXPR like COND_EXPR. + + 2017-04-10 Jakub Jelinek + + PR c++/80176 + * tree.c (lvalue_kind): For COMPONENT_REF with BASELINK second + operand, if it is a static member function, recurse on the + BASELINK. + + 2017-03-31 Jakub Jelinek + + PR c++/79572 + * cp-gimplify.c (cp_genericize_r): Sanitize INTEGER_CSTs with + REFERENCE_TYPE. Adjust ubsan_maybe_instrument_reference caller + for NOP_EXPR to REFERENCE_TYPE. + + 2017-03-22 Jakub Jelinek + + PR c++/80141 + * semantics.c (finish_omp_clause) : Call maybe_constant_value only when not + processing_template_decl. + + 2017-03-10 Jakub Jelinek + + PR c++/79896 + * decl.c (finish_enum_value_list): If value is error_mark_node, + don't copy it and change its type. + * init.c (constant_value_1): Return error_mark_node if DECL_INITIAL + of CONST_DECL is error_mark_node. + + 2017-02-22 Jakub Jelinek + + PR c++/79664 + * parser.c (cp_parser_omp_teams, cp_parser_omp_target): Use + SET_EXPR_LOCATION on OMP_TARGET/OMP_TEAMS tree. + * constexpr.c (potential_constant_expression_1): Handle + OMP_*, OACC_* and CILK_* trees. + + 2017-02-21 Jakub Jelinek + + PR c++/79639 + * constexpr.c (cxx_eval_store_expression): If *valp is a PTRMEM_CST, + call cplus_expand_constant on it first. + + 2017-02-16 Jakub Jelinek + + PR c++/79512 + * parser.c (cp_parser_omp_target): For -fopenmp-simd + ignore #pragma omp target even when not followed by identifier. + + 2017-04-12 Jason Merrill + + PR c++/80150 - ICE with overloaded variadic deduction. + * pt.c (try_one_overload): Remove asserts. + + PR c++/77563 - missing ambiguous conversion error. + * call.c (convert_like_real): Use LOOKUP_IMPLICIT. + + PR c++/79519 - ICE with deleted template friend. + * decl.c (grokdeclarator): Complain about misplaced function + definition using =, as well. + + PR c++/79640 - infinite recursion with generic lambda. + * pt.c (tsubst_copy) [VAR_DECL]: Register the dummy instantiation + before substituting its initializer. + + PR c++/80043 - ICE with -fpermissive + * typeck.c (convert_for_assignment): Handle instantiate_type + not giving an error. + + PR c++/78282 - auto template and pack expansion + * pt.c (find_parameter_packs_r): Don't walk into the type of + templates other than template template-parameters. + + PR c++/79607 - ICE with T{} initializer + * decl.c (type_dependent_init_p): Check the type of a CONSTRUCTOR. + + PR c++/79566 - elaborated-type-specifier in range for + * parser.c (cp_parser_simple_declaration): Fix check for type + definition. + + PR c++/79580 - ICE with compound literal + * parser.c (cp_parser_class_head): If we're in the middle of an + expression, use ts_within_enclosing_non_class. + + PR c++/79508 - lookup error with member template + * parser.c (cp_parser_template_name): Clear + parser->context->object_type if we aren't doing lookup. + + PR c++/79050 - ICE with undeduced auto and LTO + * decl.c (poplevel): Remove undeduced auto decls. + + PR c++/79461 - ICE with lambda in constexpr constructor + * constexpr.c (build_data_member_initialization): Ignore + initialization of a local variable. + + 2017-03-20 Nathan Sidwell + + PR c++/80091 + * lambda.c (maybe_generic_this_capture): Capture when fn + is an identifier node. + + 2017-03-15 Marek Polacek + + Backported from mainline + 2016-12-14 Marek Polacek + + PR c++/72775 + * init.c (perform_member_init): Diagnose member initializer for + flexible array member. + + 2017-03-14 Marek Polacek + + Backported from mainline + 2017-03-09 Marek Polacek + + PR c++/79900 - ICE in strip_typedefs + * tree.c (strip_typedefs): Skip the attribute handling if T is + a variant type which hasn't been updated yet. + + PR c++/79687 + * init.c (constant_value_1): Break if the variable has a dynamic + initializer. + + Backported from mainline + 2017-01-31 Nathan Sidwell + + PR c++/79264 + * lambda.c (maybe_generic_this_capture): Deal with template-id-exprs. + * semantics.c (finish_member_declaration): Assert class is being + defined. + + Backported from mainline + 2017-01-17 Nathan Sidwell + + PR c++/61636 + * cp-tree.h (maybe_generic_this_capture): Declare. + * lambda.c (resolvable_dummy_lambda): New, broken out of ... + (maybe_resolve_dummy): ... here. Call it. + (maybe_generic_this_capture): New. + * parser.c (cp_parser_postfix_expression): Speculatively capture + this in generic lambda in unresolved member function call. + * pt.c (tsubst_copy_and_build): Force hard error from failed + member function lookup in generic lambda. + + 2017-03-07 Marek Polacek + + Backported from mainline + 2017-03-06 Marek Polacek + + PR c++/79796 - ICE with NSDMI and this pointer + * call.c (build_over_call): Handle NSDMI with a 'this' by calling + replace_placeholders. + + 2017-02-15 Jakub Jelinek + + Backported from mainline + 2017-02-09 Jakub Jelinek + + PR c++/79429 + * parser.c (cp_parser_omp_ordered): Don't check for non-pragma_stmt + non-pragma_compound context here. + (cp_parser_omp_target): Likewise. + (cp_parser_pragma): Don't call push_omp_privatization_clauses and + parsing for ordered and target omp pragmas in non-pragma_stmt + non-pragma_compound contexts. + + PR c/79431 + * parser.c (cp_parser_oacc_declare): Formatting fix. + (cp_parser_omp_declare_target): Don't invoke symtab_node::get on + automatic variables. + + 2017-02-06 Jakub Jelinek + + PR c++/79377 + * tree.c (build_min_non_dep_op_overload): For POST{INC,DEC}REMENT_EXPR + allow one fewer than expected arguments if flag_permissive. + + 2017-02-13 Nathan Sidwell + + PR c++/79296 - ICE mangling localized template instantiation + * decl2.c (determine_visibility): Use template fn context for + local class instantiations. + + 2017-02-11 Jason Merrill + + PR c++/78908 - template ops and bitfields + * tree.c (build_min_non_dep): Use unlowered_expr_type. + + 2017-02-10 Jason Merrill + + PR c++/78897 - constexpr union + * constexpr.c (cxx_eval_store_expression): A store to a union member + erases a previous store to another member. + + 2017-01-26 Jason Merrill + + PR c++/79176 - lambda ICE with -flto -Os + * decl2.c (vague_linkage_p): Handle decloned 'tors. + * tree.c (decl_linkage): Likewise. + + 2017-01-20 Marek Polacek + + Backported from mainline + 2017-01-04 Marek Polacek + + PR c++/77545 + PR c++/77284 + * constexpr.c (potential_constant_expression_1): Handle CLEANUP_STMT. + + 2017-01-17 Jakub Jelinek + + Backported from mainline + 2017-01-11 Jakub Jelinek + + PR c++/78341 + * parser.c (cp_parser_std_attribute_spec): Remove over-eager + assertion. Formatting fix. + + 2017-01-04 Jakub Jelinek + + PR c++/78949 + * typeck.c (cp_build_unary_op): Call mark_rvalue_use on arg if it has + vector type. + + PR c++/78693 + * parser.c (cp_parser_simple_declaration): Only complain about + inconsistent auto deduction if auto_result doesn't use auto. + + PR c++/71182 + * parser.c (cp_lexer_previous_token): Use vec_safe_address in the + assertion, as lexer->buffer may be NULL. + + 2017-01-11 Nathan Sidwell + + PR c++/77812 + * name-lookup.c (set_namespace_binding_1): An overload of 1 decl + is a new overload. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/cp/call.c gcc-6.4.0/gcc/cp/call.c *** gcc-6.3.0/gcc/cp/call.c Mon Jul 25 21:14:20 2016 --- gcc-6.4.0/gcc/cp/call.c Wed Apr 12 19:23:30 2017 *************** convert_like_real (conversion *convs, tr *** 6465,6471 **** if (complain & tf_error) { /* Call build_user_type_conversion again for the error. */ ! build_user_type_conversion (totype, convs->u.expr, LOOKUP_NORMAL, complain); if (fn) inform (DECL_SOURCE_LOCATION (fn), --- 6465,6471 ---- if (complain & tf_error) { /* Call build_user_type_conversion again for the error. */ ! build_user_type_conversion (totype, convs->u.expr, LOOKUP_IMPLICIT, complain); if (fn) inform (DECL_SOURCE_LOCATION (fn), *************** build_over_call (struct z_candidate *can *** 7667,7672 **** --- 7667,7675 ---- { arg = cp_build_indirect_ref (arg, RO_NULL, complain); val = build2 (MODIFY_EXPR, TREE_TYPE (to), to, arg); + if (cxx_dialect >= cxx14) + /* Handle NSDMI that refer to the object being initialized. */ + replace_placeholders (arg, to); } else { diff -Nrcpad gcc-6.3.0/gcc/cp/constexpr.c gcc-6.4.0/gcc/cp/constexpr.c *** gcc-6.3.0/gcc/cp/constexpr.c Thu Dec 8 18:37:03 2016 --- gcc-6.4.0/gcc/cp/constexpr.c Wed May 31 18:53:57 2017 *************** build_data_member_initialization (tree t *** 378,383 **** --- 378,386 ---- if (TREE_CODE (member) == COMPONENT_REF) { tree aggr = TREE_OPERAND (member, 0); + if (TREE_CODE (aggr) == VAR_DECL) + /* Initializing a local variable, don't add anything. */ + return true; if (TREE_CODE (aggr) != COMPONENT_REF) /* Normal member initialization. */ member = TREE_OPERAND (member, 1); *************** reduced_constant_expression_p (tree t) *** 1611,1618 **** /* And we need to handle PTRMEM_CST wrapped in a CONSTRUCTOR. */ tree elt; unsigned HOST_WIDE_INT idx; FOR_EACH_CONSTRUCTOR_VALUE (CONSTRUCTOR_ELTS (t), idx, elt) ! if (!reduced_constant_expression_p (elt)) ! return false; return true; default: --- 1614,1626 ---- /* And we need to handle PTRMEM_CST wrapped in a CONSTRUCTOR. */ tree elt; unsigned HOST_WIDE_INT idx; FOR_EACH_CONSTRUCTOR_VALUE (CONSTRUCTOR_ELTS (t), idx, elt) ! { ! if (!elt) ! /* We're in the middle of initializing this element. */ ! return false; ! if (!reduced_constant_expression_p (elt)) ! return false; ! } return true; default: *************** verify_ctor_sanity (const constexpr_ctx *** 2493,2500 **** /* We used to check that ctx->ctor was empty, but that isn't the case when the object is zero-initialized before calling the constructor. */ if (ctx->object) ! gcc_assert (same_type_ignoring_top_level_qualifiers_p ! (type, TREE_TYPE (ctx->object))); gcc_assert (!ctx->object || !DECL_P (ctx->object) || *(ctx->values->get (ctx->object)) == ctx->ctor); } --- 2501,2516 ---- /* We used to check that ctx->ctor was empty, but that isn't the case when the object is zero-initialized before calling the constructor. */ if (ctx->object) ! { ! tree otype = TREE_TYPE (ctx->object); ! gcc_assert (same_type_ignoring_top_level_qualifiers_p (type, otype) ! /* Handle flexible array members. */ ! || (TREE_CODE (otype) == ARRAY_TYPE ! && TYPE_DOMAIN (otype) == NULL_TREE ! && TREE_CODE (type) == ARRAY_TYPE ! && (same_type_ignoring_top_level_qualifiers_p ! (TREE_TYPE (type), TREE_TYPE (otype))))); ! } gcc_assert (!ctx->object || !DECL_P (ctx->object) || *(ctx->values->get (ctx->object)) == ctx->ctor); } *************** cxx_eval_indirect_ref (const constexpr_c *** 3004,3015 **** if (*non_constant_p) return t; ! /* If we're pulling out the value of an empty base, make sure ! that the whole object is constant and then return an empty CONSTRUCTOR. */ if (empty_base && !lval) { - VERIFY_CONSTANT (r); r = build_constructor (TREE_TYPE (t), NULL); TREE_CONSTANT (r) = true; } --- 3020,3029 ---- if (*non_constant_p) return t; ! /* If we're pulling out the value of an empty base, just return an empty CONSTRUCTOR. */ if (empty_base && !lval) { r = build_constructor (TREE_TYPE (t), NULL); TREE_CONSTANT (r) = true; } *************** cxx_eval_store_expression (const constex *** 3239,3244 **** --- 3253,3263 ---- tree fields = TYPE_FIELDS (DECL_CONTEXT (index)); unsigned HOST_WIDE_INT idx; + if (code == UNION_TYPE && CONSTRUCTOR_NELTS (*valp) + && CONSTRUCTOR_ELT (*valp, 0)->index != index) + /* Changing active member. */ + vec_safe_truncate (CONSTRUCTOR_ELTS (*valp), 0); + for (idx = 0; vec_safe_iterate (CONSTRUCTOR_ELTS (*valp), idx, &cep); idx++, fields = DECL_CHAIN (fields)) *************** cxx_eval_store_expression (const constex *** 3275,3285 **** wants to modify it. */ if (*valp == NULL_TREE) { ! *valp = new_ctx.ctor = build_constructor (type, NULL); ! CONSTRUCTOR_NO_IMPLICIT_ZERO (new_ctx.ctor) = no_zero_init; } ! else ! new_ctx.ctor = *valp; new_ctx.object = target; } --- 3294,3305 ---- wants to modify it. */ if (*valp == NULL_TREE) { ! *valp = build_constructor (type, NULL); ! CONSTRUCTOR_NO_IMPLICIT_ZERO (*valp) = no_zero_init; } ! else if (TREE_CODE (*valp) == PTRMEM_CST) ! *valp = cplus_expand_constant (*valp); ! new_ctx.ctor = *valp; new_ctx.object = target; } *************** potential_constant_expression_1 (tree t, *** 4976,4985 **** --- 4996,5035 ---- case DELETE_EXPR: case VEC_DELETE_EXPR: case THROW_EXPR: + case OMP_PARALLEL: + case OMP_TASK: + case OMP_FOR: + case OMP_DISTRIBUTE: + case OMP_TASKLOOP: + case OMP_TEAMS: + case OMP_TARGET_DATA: + case OMP_TARGET: + case OMP_SECTIONS: + case OMP_ORDERED: + case OMP_CRITICAL: + case OMP_SINGLE: + case OMP_SECTION: + case OMP_MASTER: + case OMP_TASKGROUP: + case OMP_TARGET_UPDATE: + case OMP_TARGET_ENTER_DATA: + case OMP_TARGET_EXIT_DATA: case OMP_ATOMIC: case OMP_ATOMIC_READ: case OMP_ATOMIC_CAPTURE_OLD: case OMP_ATOMIC_CAPTURE_NEW: + case OACC_PARALLEL: + case OACC_KERNELS: + case OACC_DATA: + case OACC_HOST_DATA: + case OACC_LOOP: + case OACC_CACHE: + case OACC_DECLARE: + case OACC_ENTER_DATA: + case OACC_EXIT_DATA: + case OACC_UPDATE: + case CILK_SIMD: + case CILK_FOR: /* GCC internal stuff. */ case VA_ARG_EXPR: case OBJ_TYPE_REF: *************** potential_constant_expression_1 (tree t, *** 4988,4994 **** case AT_ENCODE_EXPR: fail: if (flags & tf_error) ! error ("expression %qE is not a constant-expression", t); return false; case TYPEID_EXPR: --- 5038,5045 ---- case AT_ENCODE_EXPR: fail: if (flags & tf_error) ! error_at (EXPR_LOC_OR_LOC (t, input_location), ! "expression %qE is not a constant-expression", t); return false; case TYPEID_EXPR: *************** potential_constant_expression_1 (tree t, *** 5295,5300 **** --- 5346,5352 ---- /* We can see these in statement-expressions. */ return true; + case CLEANUP_STMT: case EMPTY_CLASS_EXPR: return false; diff -Nrcpad gcc-6.3.0/gcc/cp/cp-gimplify.c gcc-6.4.0/gcc/cp/cp-gimplify.c *** gcc-6.3.0/gcc/cp/cp-gimplify.c Wed Dec 7 22:55:04 2016 --- gcc-6.4.0/gcc/cp/cp-gimplify.c Thu Jun 22 11:13:29 2017 *************** cp_genericize_r (tree *stmt_p, int *walk *** 1065,1070 **** --- 1065,1083 ---- } } + if (TREE_CODE (stmt) == INTEGER_CST + && TREE_CODE (TREE_TYPE (stmt)) == REFERENCE_TYPE + && (flag_sanitize & (SANITIZE_NULL | SANITIZE_ALIGNMENT)) + && !wtd->no_sanitize_p) + { + ubsan_maybe_instrument_reference (stmt_p); + if (*stmt_p != stmt) + { + *walk_subtrees = 0; + return NULL_TREE; + } + } + /* Other than invisiref parms, don't walk the same tree twice. */ if (p_set->contains (stmt)) { *************** cp_genericize_r (tree *stmt_p, int *walk *** 1413,1418 **** --- 1426,1441 ---- *stmt_p = cplus_expand_constant (stmt); *walk_subtrees = 0; } + else if (TREE_CODE (stmt) == MEM_REF) + { + /* For MEM_REF, make sure not to sanitize the second operand even + if it has reference type. It is just an offset with a type + holding other information. There is no other processing we + need to do for INTEGER_CSTs, so just ignore the second argument + unconditionally. */ + cp_walk_tree (&TREE_OPERAND (stmt, 0), cp_genericize_r, data, NULL); + *walk_subtrees = 0; + } else if ((flag_sanitize & (SANITIZE_NULL | SANITIZE_ALIGNMENT | SANITIZE_VPTR)) && !wtd->no_sanitize_p) *************** cp_genericize_r (tree *stmt_p, int *walk *** 1420,1426 **** if ((flag_sanitize & (SANITIZE_NULL | SANITIZE_ALIGNMENT)) && TREE_CODE (stmt) == NOP_EXPR && TREE_CODE (TREE_TYPE (stmt)) == REFERENCE_TYPE) ! ubsan_maybe_instrument_reference (stmt); else if (TREE_CODE (stmt) == CALL_EXPR) { tree fn = CALL_EXPR_FN (stmt); --- 1443,1449 ---- if ((flag_sanitize & (SANITIZE_NULL | SANITIZE_ALIGNMENT)) && TREE_CODE (stmt) == NOP_EXPR && TREE_CODE (TREE_TYPE (stmt)) == REFERENCE_TYPE) ! ubsan_maybe_instrument_reference (stmt_p); else if (TREE_CODE (stmt) == CALL_EXPR) { tree fn = CALL_EXPR_FN (stmt); *************** cp_genericize (tree fndecl) *** 1553,1559 **** if (outer) for (var = BLOCK_VARS (outer); var; var = DECL_CHAIN (var)) ! if (DECL_NAME (t) == DECL_NAME (var) && DECL_HAS_VALUE_EXPR_P (var) && DECL_VALUE_EXPR (var) == t) { --- 1576,1583 ---- if (outer) for (var = BLOCK_VARS (outer); var; var = DECL_CHAIN (var)) ! if (VAR_P (var) ! && DECL_NAME (t) == DECL_NAME (var) && DECL_HAS_VALUE_EXPR_P (var) && DECL_VALUE_EXPR (var) == t) { *************** cxx_omp_const_qual_no_mutable (tree decl *** 1800,1806 **** if (outer) for (var = BLOCK_VARS (outer); var; var = DECL_CHAIN (var)) ! if (DECL_NAME (decl) == DECL_NAME (var) && (TYPE_MAIN_VARIANT (type) == TYPE_MAIN_VARIANT (TREE_TYPE (var)))) { --- 1824,1831 ---- if (outer) for (var = BLOCK_VARS (outer); var; var = DECL_CHAIN (var)) ! if (VAR_P (var) ! && DECL_NAME (decl) == DECL_NAME (var) && (TYPE_MAIN_VARIANT (type) == TYPE_MAIN_VARIANT (TREE_TYPE (var)))) { *************** cxx_omp_finish_clause (tree c, gimple_se *** 1875,1881 **** make_shared = true; if (make_shared) ! OMP_CLAUSE_CODE (c) = OMP_CLAUSE_SHARED; } /* Return true if DECL's DECL_VALUE_EXPR (if any) should be --- 1900,1910 ---- make_shared = true; if (make_shared) ! { ! OMP_CLAUSE_CODE (c) = OMP_CLAUSE_SHARED; ! OMP_CLAUSE_SHARED_FIRSTPRIVATE (c) = 0; ! OMP_CLAUSE_SHARED_READONLY (c) = 0; ! } } /* Return true if DECL's DECL_VALUE_EXPR (if any) should be diff -Nrcpad gcc-6.3.0/gcc/cp/cp-tree.h gcc-6.4.0/gcc/cp/cp-tree.h *** gcc-6.3.0/gcc/cp/cp-tree.h Fri Nov 18 20:27:41 2016 --- gcc-6.4.0/gcc/cp/cp-tree.h Tue Mar 14 16:03:10 2017 *************** extern bool is_capture_proxy (tree); *** 6447,6452 **** --- 6447,6453 ---- extern bool is_normal_capture_proxy (tree); extern void register_capture_members (tree); extern tree lambda_expr_this_capture (tree, bool); + extern void maybe_generic_this_capture (tree, tree); extern tree maybe_resolve_dummy (tree, bool); extern tree current_nonlambda_function (void); extern tree nonlambda_method_basetype (void); diff -Nrcpad gcc-6.3.0/gcc/cp/decl.c gcc-6.4.0/gcc/cp/decl.c *** gcc-6.3.0/gcc/cp/decl.c Wed Dec 7 22:59:28 2016 --- gcc-6.4.0/gcc/cp/decl.c Fri May 5 21:41:16 2017 *************** poplevel (int keep, int reverse, int fun *** 778,791 **** back ends won't understand OVERLOAD, so we remove them here. Because the BLOCK_VARS are (temporarily) shared with CURRENT_BINDING_LEVEL->NAMES we must do this fixup after we have ! popped all the bindings. */ if (block) { tree* d; for (d = &BLOCK_VARS (block); *d; ) { ! if (TREE_CODE (*d) == TREE_LIST) *d = TREE_CHAIN (*d); else d = &DECL_CHAIN (*d); --- 778,794 ---- back ends won't understand OVERLOAD, so we remove them here. Because the BLOCK_VARS are (temporarily) shared with CURRENT_BINDING_LEVEL->NAMES we must do this fixup after we have ! popped all the bindings. Also remove undeduced 'auto' decls, ! which LTO doesn't understand, and can't have been used by anything. */ if (block) { tree* d; for (d = &BLOCK_VARS (block); *d; ) { ! if (TREE_CODE (*d) == TREE_LIST ! || (!processing_template_decl ! && undeduced_auto_decl (*d))) *d = TREE_CHAIN (*d); else d = &DECL_CHAIN (*d); *************** type_dependent_init_p (tree init) *** 6488,6493 **** --- 6491,6499 ---- else if (TREE_CODE (init) == CONSTRUCTOR) /* A brace-enclosed initializer, e.g.: int i = { 3 }; ? */ { + if (dependent_type_p (TREE_TYPE (init))) + return true; + vec *elts; size_t nelts; size_t i; *************** grokdeclarator (const cp_declarator *dec *** 10574,10582 **** else if (TREE_CODE (type) == FUNCTION_TYPE) { if (current_class_type ! && (!friendp || funcdef_flag)) { ! error (funcdef_flag ? G_("cannot define member function %<%T::%s%> " "within %<%T%>") : G_("cannot declare member function %<%T::%s%> " --- 10580,10588 ---- else if (TREE_CODE (type) == FUNCTION_TYPE) { if (current_class_type ! && (!friendp || funcdef_flag || initialized)) { ! error (funcdef_flag || initialized ? G_("cannot define member function %<%T::%s%> " "within %<%T%>") : G_("cannot declare member function %<%T::%s%> " *************** finish_enum_value_list (tree enumtype) *** 13491,13499 **** input_location = saved_location; /* Do not clobber shared ints. */ ! value = copy_node (value); ! TREE_TYPE (value) = enumtype; DECL_INITIAL (decl) = value; } --- 13497,13508 ---- input_location = saved_location; /* Do not clobber shared ints. */ ! if (value != error_mark_node) ! { ! value = copy_node (value); ! TREE_TYPE (value) = enumtype; ! } DECL_INITIAL (decl) = value; } diff -Nrcpad gcc-6.3.0/gcc/cp/decl2.c gcc-6.4.0/gcc/cp/decl2.c *** gcc-6.3.0/gcc/cp/decl2.c Tue Dec 6 18:51:56 2016 --- gcc-6.4.0/gcc/cp/decl2.c Mon Feb 13 18:12:17 2017 *************** vague_linkage_p (tree decl) *** 1875,1880 **** --- 1875,1888 ---- { if (!TREE_PUBLIC (decl)) { + /* maybe_thunk_body clears TREE_PUBLIC on the maybe-in-charge 'tor + variants, check one of the "clones" for the real linkage. */ + if ((DECL_MAYBE_IN_CHARGE_DESTRUCTOR_P (decl) + || DECL_MAYBE_IN_CHARGE_CONSTRUCTOR_P (decl)) + && DECL_CHAIN (decl) + && DECL_CLONED_FUNCTION (DECL_CHAIN (decl))) + return vague_linkage_p (DECL_CHAIN (decl)); + gcc_checking_assert (!DECL_COMDAT (decl)); return false; } *************** constrain_visibility_for_template (tree *** 2272,2282 **** void determine_visibility (tree decl) { - tree class_type = NULL_TREE; - bool use_template; - bool orig_visibility_specified; - enum symbol_visibility orig_visibility; - /* Remember that all decls get VISIBILITY_DEFAULT when built. */ /* Only relevant for names with external linkage. */ --- 2280,2285 ---- *************** determine_visibility (tree decl) *** 2288,2312 **** maybe_clone_body. */ gcc_assert (!DECL_CLONED_FUNCTION_P (decl)); ! orig_visibility_specified = DECL_VISIBILITY_SPECIFIED (decl); ! orig_visibility = DECL_VISIBILITY (decl); if (TREE_CODE (decl) == TYPE_DECL) { if (CLASS_TYPE_P (TREE_TYPE (decl))) ! use_template = CLASSTYPE_USE_TEMPLATE (TREE_TYPE (decl)); else if (TYPE_TEMPLATE_INFO (TREE_TYPE (decl))) ! use_template = 1; ! else ! use_template = 0; } ! else if (DECL_LANG_SPECIFIC (decl)) ! use_template = DECL_USE_TEMPLATE (decl); ! else ! use_template = 0; /* If DECL is a member of a class, visibility specifiers on the class can influence the visibility of the DECL. */ if (DECL_CLASS_SCOPE_P (decl)) class_type = DECL_CONTEXT (decl); else --- 2291,2318 ---- maybe_clone_body. */ gcc_assert (!DECL_CLONED_FUNCTION_P (decl)); ! bool orig_visibility_specified = DECL_VISIBILITY_SPECIFIED (decl); ! enum symbol_visibility orig_visibility = DECL_VISIBILITY (decl); + /* The decl may be a template instantiation, which could influence + visibilty. */ + tree template_decl = NULL_TREE; if (TREE_CODE (decl) == TYPE_DECL) { if (CLASS_TYPE_P (TREE_TYPE (decl))) ! { ! if (CLASSTYPE_USE_TEMPLATE (TREE_TYPE (decl))) ! template_decl = decl; ! } else if (TYPE_TEMPLATE_INFO (TREE_TYPE (decl))) ! template_decl = decl; } ! else if (DECL_LANG_SPECIFIC (decl) && DECL_USE_TEMPLATE (decl)) ! template_decl = decl; /* If DECL is a member of a class, visibility specifiers on the class can influence the visibility of the DECL. */ + tree class_type = NULL_TREE; if (DECL_CLASS_SCOPE_P (decl)) class_type = DECL_CONTEXT (decl); else *************** determine_visibility (tree decl) *** 2349,2356 **** } /* Local classes in templates have CLASSTYPE_USE_TEMPLATE set, ! but have no TEMPLATE_INFO, so don't try to check it. */ ! use_template = 0; } else if (VAR_P (decl) && DECL_TINFO_P (decl) && flag_visibility_ms_compat) --- 2355,2365 ---- } /* Local classes in templates have CLASSTYPE_USE_TEMPLATE set, ! but have no TEMPLATE_INFO. Their containing template ! function does, and the local class could be constrained ! by that. */ ! if (template_decl) ! template_decl = fn; } else if (VAR_P (decl) && DECL_TINFO_P (decl) && flag_visibility_ms_compat) *************** determine_visibility (tree decl) *** 2380,2386 **** && !CLASSTYPE_VISIBILITY_SPECIFIED (TREE_TYPE (DECL_NAME (decl)))) targetm.cxx.determine_class_data_visibility (decl); } ! else if (use_template) /* Template instantiations and specializations get visibility based on their template unless they override it with an attribute. */; else if (! DECL_VISIBILITY_SPECIFIED (decl)) --- 2389,2395 ---- && !CLASSTYPE_VISIBILITY_SPECIFIED (TREE_TYPE (DECL_NAME (decl)))) targetm.cxx.determine_class_data_visibility (decl); } ! else if (template_decl) /* Template instantiations and specializations get visibility based on their template unless they override it with an attribute. */; else if (! DECL_VISIBILITY_SPECIFIED (decl)) *************** determine_visibility (tree decl) *** 2397,2407 **** } } ! if (use_template) { /* If the specialization doesn't specify visibility, use the visibility from the template. */ ! tree tinfo = get_template_info (decl); tree args = TI_ARGS (tinfo); tree attribs = (TREE_CODE (decl) == TYPE_DECL ? TYPE_ATTRIBUTES (TREE_TYPE (decl)) --- 2406,2416 ---- } } ! if (template_decl) { /* If the specialization doesn't specify visibility, use the visibility from the template. */ ! tree tinfo = get_template_info (template_decl); tree args = TI_ARGS (tinfo); tree attribs = (TREE_CODE (decl) == TYPE_DECL ? TYPE_ATTRIBUTES (TREE_TYPE (decl)) diff -Nrcpad gcc-6.3.0/gcc/cp/error.c gcc-6.4.0/gcc/cp/error.c *** gcc-6.3.0/gcc/cp/error.c Wed Dec 7 22:27:27 2016 --- gcc-6.4.0/gcc/cp/error.c Sat Jun 24 10:50:08 2017 *************** dump_expr (cxx_pretty_printer *pp, tree *** 2029,2034 **** --- 2029,2035 ---- break; case COND_EXPR: + case VEC_COND_EXPR: pp_cxx_left_paren (pp); dump_expr (pp, TREE_OPERAND (t, 0), flags | TFF_EXPR_IN_PARENS); pp_string (pp, " ? "); *************** dump_expr (cxx_pretty_printer *pp, tree *** 2765,2770 **** --- 2766,2775 ---- pp_string (pp, M_("*this")); break; + case TREE_LIST: + dump_expr_list (pp, t, flags); + break; + /* This list is incomplete, but should suffice for now. It is very important that `sorry' does not call `report_error_function'. That could cause an infinite loop. */ diff -Nrcpad gcc-6.3.0/gcc/cp/init.c gcc-6.4.0/gcc/cp/init.c *** gcc-6.3.0/gcc/cp/init.c Tue Oct 4 17:55:43 2016 --- gcc-6.4.0/gcc/cp/init.c Fri May 5 21:41:16 2017 *************** perform_member_init (tree member, tree i *** 796,801 **** --- 796,809 ---- in that case. */ init = build_x_compound_expr_from_list (init, ELK_MEM_INIT, tf_warning_or_error); + if (TREE_CODE (type) == ARRAY_TYPE + && TYPE_DOMAIN (type) == NULL_TREE + && init != NULL_TREE) + { + error_at (DECL_SOURCE_LOCATION (current_function_decl), + "member initializer for flexible array member"); + inform (DECL_SOURCE_LOCATION (member), "%q#D initialized", member); + } if (init) finish_expr_stmt (cp_build_modify_expr (decl, INIT_EXPR, init, *************** constant_value_1 (tree decl, bool strict *** 2069,2075 **** init = DECL_INITIAL (decl); if (init == error_mark_node) { ! if (DECL_INITIALIZED_BY_CONSTANT_EXPRESSION_P (decl)) /* Treat the error as a constant to avoid cascading errors on excessively recursive template instantiation (c++/9335). */ return init; --- 2077,2084 ---- init = DECL_INITIAL (decl); if (init == error_mark_node) { ! if (TREE_CODE (decl) == CONST_DECL ! || DECL_INITIALIZED_BY_CONSTANT_EXPRESSION_P (decl)) /* Treat the error as a constant to avoid cascading errors on excessively recursive template instantiation (c++/9335). */ return init; *************** constant_value_1 (tree decl, bool strict *** 2110,2115 **** --- 2119,2131 ---- if (TREE_CODE (init) == CONSTRUCTOR && !DECL_INITIALIZED_BY_CONSTANT_EXPRESSION_P (decl)) break; + /* If the variable has a dynamic initializer, don't use its + DECL_INITIAL which doesn't reflect the real value. */ + if (VAR_P (decl) + && TREE_STATIC (decl) + && !DECL_INITIALIZED_BY_CONSTANT_EXPRESSION_P (decl) + && DECL_NONTRIVIALLY_INITIALIZED_P (decl)) + break; decl = unshare_expr (init); } return decl; diff -Nrcpad gcc-6.3.0/gcc/cp/lambda.c gcc-6.4.0/gcc/cp/lambda.c *** gcc-6.3.0/gcc/cp/lambda.c Mon Aug 8 09:40:17 2016 --- gcc-6.4.0/gcc/cp/lambda.c Tue Mar 21 17:40:40 2017 *************** lambda_expr_this_capture (tree lambda, b *** 746,761 **** return result; } ! /* We don't want to capture 'this' until we know we need it, i.e. after ! overload resolution has chosen a non-static member function. At that ! point we call this function to turn a dummy object into a use of the ! 'this' capture. */ ! tree ! maybe_resolve_dummy (tree object, bool add_capture_p) { if (!is_dummy_object (object)) ! return object; tree type = TYPE_MAIN_VARIANT (TREE_TYPE (object)); gcc_assert (!TYPE_PTR_P (type)); --- 746,759 ---- return result; } ! /* Return the current LAMBDA_EXPR, if this is a resolvable dummy ! object. NULL otherwise.. */ ! static tree ! resolvable_dummy_lambda (tree object) { if (!is_dummy_object (object)) ! return NULL_TREE; tree type = TYPE_MAIN_VARIANT (TREE_TYPE (object)); gcc_assert (!TYPE_PTR_P (type)); *************** maybe_resolve_dummy (tree object, bool a *** 765,782 **** && LAMBDA_TYPE_P (current_class_type) && lambda_function (current_class_type) && DERIVED_FROM_P (type, current_nonlambda_class_type ())) ! { ! /* In a lambda, need to go through 'this' capture. */ ! tree lam = CLASSTYPE_LAMBDA_EXPR (current_class_type); ! tree cap = lambda_expr_this_capture (lam, add_capture_p); ! if (cap && cap != error_mark_node) object = build_x_indirect_ref (EXPR_LOCATION (object), cap, RO_NULL, tf_warning_or_error); - } return object; } /* Returns the innermost non-lambda function. */ tree --- 763,826 ---- && LAMBDA_TYPE_P (current_class_type) && lambda_function (current_class_type) && DERIVED_FROM_P (type, current_nonlambda_class_type ())) ! return CLASSTYPE_LAMBDA_EXPR (current_class_type); ! ! return NULL_TREE; ! } ! ! /* We don't want to capture 'this' until we know we need it, i.e. after ! overload resolution has chosen a non-static member function. At that ! point we call this function to turn a dummy object into a use of the ! 'this' capture. */ ! ! tree ! maybe_resolve_dummy (tree object, bool add_capture_p) ! { ! if (tree lam = resolvable_dummy_lambda (object)) ! if (tree cap = lambda_expr_this_capture (lam, add_capture_p)) ! if (cap != error_mark_node) object = build_x_indirect_ref (EXPR_LOCATION (object), cap, RO_NULL, tf_warning_or_error); return object; } + /* When parsing a generic lambda containing an argument-dependent + member function call we defer overload resolution to instantiation + time. But we have to know now whether to capture this or not. + Do that if FNS contains any non-static fns. + The std doesn't anticipate this case, but I expect this to be the + outcome of discussion. */ + + void + maybe_generic_this_capture (tree object, tree fns) + { + if (tree lam = resolvable_dummy_lambda (object)) + if (!LAMBDA_EXPR_THIS_CAPTURE (lam)) + { + /* We've not yet captured, so look at the function set of + interest. */ + if (BASELINK_P (fns)) + fns = BASELINK_FUNCTIONS (fns); + bool id_expr = TREE_CODE (fns) == TEMPLATE_ID_EXPR; + if (id_expr) + fns = TREE_OPERAND (fns, 0); + for (; fns; fns = OVL_NEXT (fns)) + { + tree fn = OVL_CURRENT (fns); + + if (identifier_p (fns) + || ((!id_expr || TREE_CODE (fn) == TEMPLATE_DECL) + && DECL_NONSTATIC_MEMBER_FUNCTION_P (fn))) + { + /* Found a non-static member. Capture this. */ + lambda_expr_this_capture (lam, true); + break; + } + } + } + } + /* Returns the innermost non-lambda function. */ tree diff -Nrcpad gcc-6.3.0/gcc/cp/method.c gcc-6.4.0/gcc/cp/method.c *** gcc-6.3.0/gcc/cp/method.c Thu Jun 2 11:30:44 2016 --- gcc-6.4.0/gcc/cp/method.c Mon Jun 19 16:21:40 2017 *************** forward_parm (tree parm) *** 486,491 **** --- 486,492 ---- type = PACK_EXPANSION_PATTERN (type); if (TREE_CODE (type) != REFERENCE_TYPE) type = cp_build_reference_type (type, /*rval=*/true); + warning_sentinel w (warn_useless_cast); exp = build_static_cast (type, exp, tf_warning_or_error); if (DECL_PACK_P (parm)) exp = make_pack_expansion (exp); diff -Nrcpad gcc-6.3.0/gcc/cp/name-lookup.c gcc-6.4.0/gcc/cp/name-lookup.c *** gcc-6.3.0/gcc/cp/name-lookup.c Tue May 31 21:36:28 2016 --- gcc-6.4.0/gcc/cp/name-lookup.c Wed Jan 11 20:49:50 2017 *************** set_namespace_binding_1 (tree name, tree *** 3470,3476 **** if (scope == NULL_TREE) scope = global_namespace; b = binding_for_name (NAMESPACE_LEVEL (scope), name); ! if (!b->value || TREE_CODE (val) == OVERLOAD || val == error_mark_node) b->value = val; else supplement_binding (b, val); --- 3470,3481 ---- if (scope == NULL_TREE) scope = global_namespace; b = binding_for_name (NAMESPACE_LEVEL (scope), name); ! if (!b->value ! /* For templates and using we create a single element OVERLOAD. ! Look for the chain to know whether this is really augmenting ! an existing overload. */ ! || (TREE_CODE (val) == OVERLOAD && OVL_CHAIN (val)) ! || val == error_mark_node) b->value = val; else supplement_binding (b, val); diff -Nrcpad gcc-6.3.0/gcc/cp/parser.c gcc-6.4.0/gcc/cp/parser.c *** gcc-6.3.0/gcc/cp/parser.c Wed Dec 7 22:46:26 2016 --- gcc-6.4.0/gcc/cp/parser.c Sat Jun 24 10:50:08 2017 *************** cp_lexer_previous_token (cp_lexer *lexer *** 762,768 **** /* Skip past purged tokens. */ while (tp->purged_p) { ! gcc_assert (tp != lexer->buffer->address ()); tp--; } --- 762,768 ---- /* Skip past purged tokens. */ while (tp->purged_p) { ! gcc_assert (tp != vec_safe_address (lexer->buffer)); tp--; } *************** cp_parser_postfix_expression (cp_parser *** 6867,6872 **** --- 6867,6873 ---- || type_dependent_expression_p (fn) || any_type_dependent_arguments_p (args))) { + maybe_generic_this_capture (instance, fn); postfix_expression = build_nt_call_vec (postfix_expression, args); release_tree_vector (args); *************** cp_parser_simple_declaration (cp_parser* *** 12406,12414 **** if (cp_parser_error_occurred (parser)) goto done; ! if (auto_result) { ! if (last_type && last_type != error_mark_node && !same_type_p (auto_result, last_type)) { /* If the list of declarators contains more than one declarator, --- 12407,12417 ---- if (cp_parser_error_occurred (parser)) goto done; ! if (auto_result ! && (!processing_template_decl || !type_uses_auto (auto_result))) { ! if (last_type ! && last_type != error_mark_node && !same_type_p (auto_result, last_type)) { /* If the list of declarators contains more than one declarator, *************** cp_parser_simple_declaration (cp_parser* *** 12459,12465 **** break; else if (maybe_range_for_decl) { ! if (declares_class_or_enum && token->type == CPP_COLON) pedwarn (decl_specifiers.locations[ds_type_spec], 0, "types may not be defined in a for-range-declaration"); break; --- 12462,12468 ---- break; else if (maybe_range_for_decl) { ! if ((declares_class_or_enum & 2) && token->type == CPP_COLON) pedwarn (decl_specifiers.locations[ds_type_spec], 0, "types may not be defined in a for-range-declaration"); break; *************** cp_parser_template_name (cp_parser* pars *** 15153,15158 **** --- 15156,15162 ---- cp_lexer_purge_tokens_after (parser->lexer, start); if (is_identifier) *is_identifier = true; + parser->context->object_type = NULL_TREE; return identifier; } *************** cp_parser_template_name (cp_parser* pars *** 15164,15170 **** && (!parser->scope || (TYPE_P (parser->scope) && dependent_type_p (parser->scope)))) ! return identifier; } /* Look up the name. */ --- 15168,15179 ---- && (!parser->scope || (TYPE_P (parser->scope) && dependent_type_p (parser->scope)))) ! { ! /* We're optimizing away the call to cp_parser_lookup_name, but we ! still need to do this. */ ! parser->context->object_type = NULL_TREE; ! return identifier; ! } } /* Look up the name. */ *************** cp_parser_class_head (cp_parser* parser, *** 21996,22002 **** /* If the class was unnamed, create a dummy name. */ if (!id) id = make_anon_name (); ! type = xref_tag (class_key, id, /*tag_scope=*/ts_current, parser->num_template_parameter_lists); } --- 22005,22014 ---- /* If the class was unnamed, create a dummy name. */ if (!id) id = make_anon_name (); ! tag_scope tag_scope = (parser->in_type_id_in_expr_p ! ? ts_within_enclosing_non_class ! : ts_current); ! type = xref_tag (class_key, id, tag_scope, parser->num_template_parameter_lists); } *************** cp_parser_std_attribute_list (cp_parser *** 24070,24077 **** error_at (token->location, "expected attribute before %<...%>"); else ! TREE_VALUE (attribute) ! = make_pack_expansion (TREE_VALUE (attribute)); token = cp_lexer_peek_token (parser->lexer); } if (token->type != CPP_COMMA) --- 24082,24093 ---- error_at (token->location, "expected attribute before %<...%>"); else ! { ! tree pack = make_pack_expansion (TREE_VALUE (attribute)); ! if (pack == error_mark_node) ! return error_mark_node; ! TREE_VALUE (attribute) = pack; ! } token = cp_lexer_peek_token (parser->lexer); } if (token->type != CPP_COMMA) *************** cp_parser_std_attribute_spec (cp_parser *** 24140,24150 **** if (!cp_parser_parse_definitely (parser)) { ! gcc_assert (alignas_expr == error_mark_node ! || alignas_expr == NULL_TREE); ! ! alignas_expr = ! cp_parser_assignment_expression (parser); if (alignas_expr == error_mark_node) cp_parser_skip_to_end_of_statement (parser); if (alignas_expr == NULL_TREE --- 24156,24162 ---- if (!cp_parser_parse_definitely (parser)) { ! alignas_expr = cp_parser_assignment_expression (parser); if (alignas_expr == error_mark_node) cp_parser_skip_to_end_of_statement (parser); if (alignas_expr == NULL_TREE *************** cp_parser_omp_ordered (cp_parser *parser *** 34060,34072 **** { location_t loc = pragma_tok->location; - if (context != pragma_stmt && context != pragma_compound) - { - cp_parser_error (parser, "expected declaration specifiers"); - cp_parser_skip_to_pragma_eol (parser, pragma_tok); - return false; - } - if (cp_lexer_next_token_is (parser->lexer, CPP_NAME)) { tree id = cp_lexer_peek_token (parser->lexer)->u.value; --- 34072,34077 ---- *************** cp_parser_omp_teams (cp_parser *parser, *** 34624,34629 **** --- 34629,34635 ---- OMP_TEAMS_CLAUSES (ret) = clauses; OMP_TEAMS_BODY (ret) = body; OMP_TEAMS_COMBINED (ret) = 1; + SET_EXPR_LOCATION (ret, loc); return add_stmt (ret); } } *************** cp_parser_omp_teams (cp_parser *parser, *** 34645,34650 **** --- 34651,34657 ---- TREE_TYPE (stmt) = void_type_node; OMP_TEAMS_CLAUSES (stmt) = clauses; OMP_TEAMS_BODY (stmt) = cp_parser_omp_structured_block (parser, if_p); + SET_EXPR_LOCATION (stmt, loc); return add_stmt (stmt); } *************** cp_parser_omp_target (cp_parser *parser, *** 34959,34971 **** { tree *pc = NULL, stmt; - if (context != pragma_stmt && context != pragma_compound) - { - cp_parser_error (parser, "expected declaration specifiers"); - cp_parser_skip_to_pragma_eol (parser, pragma_tok); - return false; - } - if (cp_lexer_next_token_is (parser->lexer, CPP_NAME)) { tree id = cp_lexer_peek_token (parser->lexer)->u.value; --- 34966,34971 ---- *************** cp_parser_omp_target (cp_parser *parser, *** 35070,35075 **** --- 35070,35076 ---- OMP_TARGET_CLAUSES (stmt) = cclauses[C_OMP_CLAUSE_SPLIT_TARGET]; OMP_TARGET_BODY (stmt) = body; OMP_TARGET_COMBINED (stmt) = 1; + SET_EXPR_LOCATION (stmt, pragma_tok->location); add_stmt (stmt); pc = &OMP_TARGET_CLAUSES (stmt); goto check_clauses; *************** cp_parser_omp_target (cp_parser *parser, *** 35103,35108 **** --- 35104,35114 ---- return cp_parser_omp_target_update (parser, pragma_tok, context); } } + if (!flag_openmp) /* flag_openmp_simd */ + { + cp_parser_skip_to_pragma_eol (parser, pragma_tok); + return false; + } stmt = make_node (OMP_TARGET); TREE_TYPE (stmt) = void_type_node; *************** cp_parser_oacc_declare (cp_parser *parse *** 35347,35353 **** id = get_identifier ("omp declare target"); DECL_ATTRIBUTES (decl) ! = tree_cons (id, NULL_TREE, DECL_ATTRIBUTES (decl)); if (global_bindings_p ()) { symtab_node *node = symtab_node::get (decl); --- 35353,35359 ---- id = get_identifier ("omp declare target"); DECL_ATTRIBUTES (decl) ! = tree_cons (id, NULL_TREE, DECL_ATTRIBUTES (decl)); if (global_bindings_p ()) { symtab_node *node = symtab_node::get (decl); *************** cp_parser_omp_declare_target (cp_parser *** 35887,35894 **** } if (!at1) { - symtab_node *node = symtab_node::get (t); DECL_ATTRIBUTES (t) = tree_cons (id, NULL_TREE, DECL_ATTRIBUTES (t)); if (node != NULL) { node->offloadable = 1; --- 35893,35903 ---- } if (!at1) { DECL_ATTRIBUTES (t) = tree_cons (id, NULL_TREE, DECL_ATTRIBUTES (t)); + if (TREE_CODE (t) != FUNCTION_DECL && !is_global_var (t)) + continue; + + symtab_node *node = symtab_node::get (t); if (node != NULL) { node->offloadable = 1; *************** cp_parser_pragma (cp_parser *parser, enu *** 37404,37415 **** --- 37413,37428 ---- return true; case PRAGMA_OMP_ORDERED: + if (context != pragma_stmt && context != pragma_compound) + goto bad_stmt; stmt = push_omp_privatization_clauses (false); ret = cp_parser_omp_ordered (parser, pragma_tok, context, if_p); pop_omp_privatization_clauses (stmt); return ret; case PRAGMA_OMP_TARGET: + if (context != pragma_stmt && context != pragma_compound) + goto bad_stmt; stmt = push_omp_privatization_clauses (false); ret = cp_parser_omp_target (parser, pragma_tok, context, if_p); pop_omp_privatization_clauses (stmt); diff -Nrcpad gcc-6.3.0/gcc/cp/pt.c gcc-6.4.0/gcc/cp/pt.c *** gcc-6.3.0/gcc/cp/pt.c Wed Dec 14 17:23:06 2016 --- gcc-6.4.0/gcc/cp/pt.c Tue May 23 20:51:33 2017 *************** find_parameter_packs_r (tree *tp, int *w *** 3549,3556 **** *walk_subtrees = 0; return NULL_TREE; - case CONSTRUCTOR: case TEMPLATE_DECL: cp_walk_tree (&TREE_TYPE (t), &find_parameter_packs_r, ppd, ppd->visited); return NULL_TREE; --- 3549,3560 ---- *walk_subtrees = 0; return NULL_TREE; case TEMPLATE_DECL: + if (!DECL_TEMPLATE_TEMPLATE_PARM_P (t)) + return NULL_TREE; + /* Fall through. */ + + case CONSTRUCTOR: cp_walk_tree (&TREE_TYPE (t), &find_parameter_packs_r, ppd, ppd->visited); return NULL_TREE; *************** tsubst_copy (tree t, tree args, tsubst_f *** 14082,14088 **** { /* First try name lookup to find the instantiation. */ r = lookup_name (DECL_NAME (t)); ! if (r) { /* Make sure that the one we found is the one we want. */ tree ctx = DECL_CONTEXT (t); --- 14086,14092 ---- { /* First try name lookup to find the instantiation. */ r = lookup_name (DECL_NAME (t)); ! if (r && !is_capture_proxy (r)) { /* Make sure that the one we found is the one we want. */ tree ctx = DECL_CONTEXT (t); *************** tsubst_copy (tree t, tree args, tsubst_f *** 14101,14106 **** --- 14105,14113 ---- local static or constant. Building a new VAR_DECL should be OK in all those cases. */ r = tsubst_decl (t, args, complain); + if (local_specializations) + /* Avoid infinite recursion (79640). */ + register_local_specialization (r, t); if (decl_maybe_constant_var_p (r)) { /* We can't call cp_finish_decl, so handle the *************** tsubst_copy_and_build (tree t, *** 16613,16631 **** if (unq != function) { ! tree fn = unq; ! if (INDIRECT_REF_P (fn)) ! fn = TREE_OPERAND (fn, 0); ! if (TREE_CODE (fn) == COMPONENT_REF) ! fn = TREE_OPERAND (fn, 1); ! if (is_overloaded_fn (fn)) ! fn = get_first_fn (fn); ! if (permerror (EXPR_LOC_OR_LOC (t, input_location), ! "%qD was not declared in this scope, " ! "and no declarations were found by " ! "argument-dependent lookup at the point " ! "of instantiation", function)) { if (!DECL_P (fn)) /* Can't say anything more. */; else if (DECL_CLASS_SCOPE_P (fn)) --- 16620,16653 ---- if (unq != function) { ! /* In a lambda fn, we have to be careful to not ! introduce new this captures. Legacy code can't ! be using lambdas anyway, so it's ok to be ! stricter. */ ! bool in_lambda = (current_class_type ! && LAMBDA_TYPE_P (current_class_type)); ! char const *msg = "%qD was not declared in this scope, " ! "and no declarations were found by " ! "argument-dependent lookup at the point " ! "of instantiation"; ! ! bool diag = true; ! if (in_lambda) ! error_at (EXPR_LOC_OR_LOC (t, input_location), ! msg, function); ! else ! diag = permerror (EXPR_LOC_OR_LOC (t, input_location), ! msg, function); ! if (diag) { + tree fn = unq; + if (INDIRECT_REF_P (fn)) + fn = TREE_OPERAND (fn, 0); + if (TREE_CODE (fn) == COMPONENT_REF) + fn = TREE_OPERAND (fn, 1); + if (is_overloaded_fn (fn)) + fn = get_first_fn (fn); + if (!DECL_P (fn)) /* Can't say anything more. */; else if (DECL_CLASS_SCOPE_P (fn)) *************** tsubst_copy_and_build (tree t, *** 16648,16654 **** --- 16670,16682 ---- inform (DECL_SOURCE_LOCATION (fn), "%qD declared here, later in the " "translation unit", fn); + if (in_lambda) + { + release_tree_vector (call_args); + RETURN (error_mark_node); + } } + function = unq; } } *************** try_one_overload (tree tparms, *** 18904,18912 **** is equivalent to the corresponding explicitly specified argument. We may have deduced more arguments than were explicitly specified, and that's OK. */ ! gcc_assert (ARGUMENT_PACK_INCOMPLETE_P (oldelt)); ! gcc_assert (ARGUMENT_PACK_ARGS (oldelt) ! == ARGUMENT_PACK_EXPLICIT_ARGS (oldelt)); tree explicit_pack = ARGUMENT_PACK_ARGS (oldelt); tree deduced_pack = ARGUMENT_PACK_ARGS (elt); --- 18932,18941 ---- is equivalent to the corresponding explicitly specified argument. We may have deduced more arguments than were explicitly specified, and that's OK. */ ! ! /* We used to assert ARGUMENT_PACK_INCOMPLETE_P (oldelt) here, but ! that's wrong if we deduce the same argument pack from multiple ! function arguments: it's only incomplete the first time. */ tree explicit_pack = ARGUMENT_PACK_ARGS (oldelt); tree deduced_pack = ARGUMENT_PACK_ARGS (elt); diff -Nrcpad gcc-6.3.0/gcc/cp/semantics.c gcc-6.4.0/gcc/cp/semantics.c *** gcc-6.3.0/gcc/cp/semantics.c Fri Nov 18 20:27:41 2016 --- gcc-6.4.0/gcc/cp/semantics.c Thu Jun 22 11:24:43 2017 *************** finish_member_declaration (tree decl) *** 2965,2970 **** --- 2965,2976 ---- /* We should see only one DECL at a time. */ gcc_assert (DECL_CHAIN (decl) == NULL_TREE); + /* Don't add decls after definition. */ + gcc_assert (TYPE_BEING_DEFINED (current_class_type) + /* We can add lambda types when late parsing default + arguments. */ + || LAMBDA_TYPE_P (TREE_TYPE (decl))); + /* Set up access control for DECL. */ TREE_PRIVATE (decl) = (current_access_specifier == access_private_node); *************** handle_omp_array_sections_1 (tree c, tre *** 4525,4531 **** } if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl) return NULL_TREE; if (DECL_P (t)) error_at (OMP_CLAUSE_LOCATION (c), --- 4531,4537 ---- } if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl && TREE_CODE (t) != OVERLOAD) return NULL_TREE; if (DECL_P (t)) error_at (OMP_CLAUSE_LOCATION (c), *************** handle_omp_array_sections_1 (tree c, tre *** 4669,4677 **** && TREE_CODE (TYPE_MAX_VALUE (TYPE_DOMAIN (type))) == INTEGER_CST) { ! tree size = size_binop (PLUS_EXPR, ! TYPE_MAX_VALUE (TYPE_DOMAIN (type)), ! size_one_node); if (TREE_CODE (low_bound) == INTEGER_CST) { if (tree_int_cst_lt (size, low_bound)) --- 4675,4683 ---- && TREE_CODE (TYPE_MAX_VALUE (TYPE_DOMAIN (type))) == INTEGER_CST) { ! tree size ! = fold_convert (sizetype, TYPE_MAX_VALUE (TYPE_DOMAIN (type))); ! size = size_binop (PLUS_EXPR, size, size_one_node); if (TREE_CODE (low_bound) == INTEGER_CST) { if (tree_int_cst_lt (size, low_bound)) *************** finish_omp_clauses (tree clauses, bool a *** 6007,6013 **** if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL && (!field_ok || TREE_CODE (t) != FIELD_DECL)) { ! if (processing_template_decl) break; if (DECL_P (t)) error ("%qD is not a variable in clause %qs", t, --- 6013,6019 ---- if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL && (!field_ok || TREE_CODE (t) != FIELD_DECL)) { ! if (processing_template_decl && TREE_CODE (t) != OVERLOAD) break; if (DECL_P (t)) error ("%qD is not a variable in clause %qs", t, *************** finish_omp_clauses (tree clauses, bool a *** 6063,6069 **** if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL && (!allow_fields || TREE_CODE (t) != FIELD_DECL)) { ! if (processing_template_decl) break; if (DECL_P (t)) error ("%qD is not a variable in clause %", t); --- 6069,6075 ---- if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL && (!allow_fields || TREE_CODE (t) != FIELD_DECL)) { ! if (processing_template_decl && TREE_CODE (t) != OVERLOAD) break; if (DECL_P (t)) error ("%qD is not a variable in clause %", t); *************** finish_omp_clauses (tree clauses, bool a *** 6102,6108 **** if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL && (!allow_fields || TREE_CODE (t) != FIELD_DECL)) { ! if (processing_template_decl) break; if (DECL_P (t)) error ("%qD is not a variable in clause %", t); --- 6108,6114 ---- if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL && (!allow_fields || TREE_CODE (t) != FIELD_DECL)) { ! if (processing_template_decl && TREE_CODE (t) != OVERLOAD) break; if (DECL_P (t)) error ("%qD is not a variable in clause %", t); *************** finish_omp_clauses (tree clauses, bool a *** 6325,6333 **** else { t = mark_rvalue_use (t); - t = maybe_constant_value (t); if (!processing_template_decl) { if (TREE_CODE (t) != INTEGER_CST || tree_int_cst_sgn (t) != 1) { --- 6331,6339 ---- else { t = mark_rvalue_use (t); if (!processing_template_decl) { + t = maybe_constant_value (t); if (TREE_CODE (t) != INTEGER_CST || tree_int_cst_sgn (t) != 1) { *************** finish_omp_clauses (tree clauses, bool a *** 6452,6458 **** } if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl) break; if (DECL_P (t)) error ("%qD is not a variable in % clause", t); --- 6458,6464 ---- } if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl && TREE_CODE (t) != OVERLOAD) break; if (DECL_P (t)) error ("%qD is not a variable in % clause", t); *************** finish_omp_clauses (tree clauses, bool a *** 6495,6503 **** else { t = mark_rvalue_use (t); - t = maybe_constant_value (t); if (!processing_template_decl) { if (TREE_CODE (t) != INTEGER_CST || tree_int_cst_sgn (t) != 1) { --- 6501,6509 ---- else { t = mark_rvalue_use (t); if (!processing_template_decl) { + t = maybe_constant_value (t); if (TREE_CODE (t) != INTEGER_CST || tree_int_cst_sgn (t) != 1) { *************** finish_omp_clauses (tree clauses, bool a *** 6534,6540 **** remove = true; else if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl) break; if (DECL_P (t)) error ("%qD is not a variable in % clause", t); --- 6540,6546 ---- remove = true; else if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl && TREE_CODE (t) != OVERLOAD) break; if (DECL_P (t)) error ("%qD is not a variable in % clause", t); *************** finish_omp_clauses (tree clauses, bool a *** 6662,6668 **** } if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl) break; if (OMP_CLAUSE_CODE (c) == OMP_CLAUSE_MAP && (OMP_CLAUSE_MAP_KIND (c) == GOMP_MAP_POINTER --- 6668,6674 ---- } if (!VAR_P (t) && TREE_CODE (t) != PARM_DECL) { ! if (processing_template_decl && TREE_CODE (t) != OVERLOAD) break; if (OMP_CLAUSE_CODE (c) == OMP_CLAUSE_MAP && (OMP_CLAUSE_MAP_KIND (c) == GOMP_MAP_POINTER diff -Nrcpad gcc-6.3.0/gcc/cp/tree.c gcc-6.4.0/gcc/cp/tree.c *** gcc-6.3.0/gcc/cp/tree.c Thu Jul 21 06:18:06 2016 --- gcc-6.4.0/gcc/cp/tree.c Sat Jun 24 10:53:48 2017 *************** lvalue_kind (const_tree ref) *** 107,112 **** --- 107,123 ---- return op1_lvalue_kind; case COMPONENT_REF: + if (BASELINK_P (TREE_OPERAND (ref, 1))) + { + tree fn = BASELINK_FUNCTIONS (TREE_OPERAND (ref, 1)); + + /* For static member function recurse on the BASELINK, we can get + here e.g. from reference_binding. If BASELINK_FUNCTIONS is + OVERLOAD, the overload is resolved first if possible through + resolve_address_of_overloaded_function. */ + if (TREE_CODE (fn) == FUNCTION_DECL && DECL_STATIC_FUNCTION_P (fn)) + return lvalue_kind (TREE_OPERAND (ref, 1)); + } op1_lvalue_kind = lvalue_kind (TREE_OPERAND (ref, 0)); /* Look at the member designator. */ if (!op1_lvalue_kind) *************** strip_typedefs (tree t, bool *remove_att *** 1446,1451 **** --- 1457,1466 ---- DECLTYPE_TYPE_ID_EXPR_OR_MEMBER_ACCESS_P (t), tf_none)); break; + case UNDERLYING_TYPE: + type = strip_typedefs (UNDERLYING_TYPE_TYPE (t), remove_attributes); + result = finish_underlying_type (type); + break; default: break; } *************** strip_typedefs (tree t, bool *remove_att *** 1463,1491 **** result = TYPE_MAIN_VARIANT (t); } gcc_assert (!typedef_variant_p (result)); ! if (TYPE_USER_ALIGN (t) != TYPE_USER_ALIGN (result) ! || TYPE_ALIGN (t) != TYPE_ALIGN (result)) { ! gcc_assert (TYPE_USER_ALIGN (t)); ! if (remove_attributes) ! *remove_attributes = true; ! else { ! if (TYPE_ALIGN (t) == TYPE_ALIGN (result)) ! result = build_variant_type_copy (result); else ! result = build_aligned_type (result, TYPE_ALIGN (t)); ! TYPE_USER_ALIGN (result) = true; } } ! if (TYPE_ATTRIBUTES (t)) ! { ! if (remove_attributes) ! result = apply_identity_attributes (result, TYPE_ATTRIBUTES (t), ! remove_attributes); ! else ! result = cp_build_type_attribute_variant (result, TYPE_ATTRIBUTES (t)); ! } return cp_build_qualified_type (result, cp_type_quals (t)); } --- 1478,1517 ---- result = TYPE_MAIN_VARIANT (t); } gcc_assert (!typedef_variant_p (result)); ! ! if (COMPLETE_TYPE_P (result) && !COMPLETE_TYPE_P (t)) ! /* If RESULT is complete and T isn't, it's likely the case that T ! is a variant of RESULT which hasn't been updated yet. Skip the ! attribute handling. */; ! else { ! if (TYPE_USER_ALIGN (t) != TYPE_USER_ALIGN (result) ! || TYPE_ALIGN (t) != TYPE_ALIGN (result)) { ! gcc_assert (TYPE_USER_ALIGN (t)); ! if (remove_attributes) ! *remove_attributes = true; else ! { ! if (TYPE_ALIGN (t) == TYPE_ALIGN (result)) ! result = build_variant_type_copy (result); ! else ! result = build_aligned_type (result, TYPE_ALIGN (t)); ! TYPE_USER_ALIGN (result) = true; ! } ! } ! ! if (TYPE_ATTRIBUTES (t)) ! { ! if (remove_attributes) ! result = apply_identity_attributes (result, TYPE_ATTRIBUTES (t), ! remove_attributes); ! else ! result = cp_build_type_attribute_variant (result, ! TYPE_ATTRIBUTES (t)); } } ! return cp_build_qualified_type (result, cp_type_quals (t)); } *************** build_min_non_dep (enum tree_code code, *** 2775,2781 **** t = make_node (code); length = TREE_CODE_LENGTH (code); ! TREE_TYPE (t) = TREE_TYPE (non_dep); TREE_SIDE_EFFECTS (t) = TREE_SIDE_EFFECTS (non_dep); for (i = 0; i < length; i++) --- 2801,2807 ---- t = make_node (code); length = TREE_CODE_LENGTH (code); ! TREE_TYPE (t) = unlowered_expr_type (non_dep); TREE_SIDE_EFFECTS (t) = TREE_SIDE_EFFECTS (non_dep); for (i = 0; i < length; i++) *************** build_min_non_dep_op_overload (enum tree *** 2830,2837 **** nargs = call_expr_nargs (non_dep); expected_nargs = cp_tree_code_length (op); ! if (op == POSTINCREMENT_EXPR ! || op == POSTDECREMENT_EXPR) expected_nargs += 1; gcc_assert (nargs == expected_nargs); --- 2856,2865 ---- nargs = call_expr_nargs (non_dep); expected_nargs = cp_tree_code_length (op); ! if ((op == POSTINCREMENT_EXPR ! || op == POSTDECREMENT_EXPR) ! /* With -fpermissive non_dep could be operator++(). */ ! && (!flag_permissive || nargs != expected_nargs)) expected_nargs += 1; gcc_assert (nargs == expected_nargs); *************** decl_linkage (tree decl) *** 4146,4151 **** --- 4174,4187 ---- if (TREE_PUBLIC (decl)) return lk_external; + /* maybe_thunk_body clears TREE_PUBLIC on the maybe-in-charge 'tor variants, + check one of the "clones" for the real linkage. */ + if ((DECL_MAYBE_IN_CHARGE_DESTRUCTOR_P (decl) + || DECL_MAYBE_IN_CHARGE_CONSTRUCTOR_P (decl)) + && DECL_CHAIN (decl) + && DECL_CLONED_FUNCTION (DECL_CHAIN (decl))) + return decl_linkage (DECL_CHAIN (decl)); + if (TREE_CODE (decl) == NAMESPACE_DECL) return lk_external; diff -Nrcpad gcc-6.3.0/gcc/cp/typeck.c gcc-6.4.0/gcc/cp/typeck.c *** gcc-6.3.0/gcc/cp/typeck.c Wed Dec 7 22:56:45 2016 --- gcc-6.4.0/gcc/cp/typeck.c Sat Jun 24 10:59:00 2017 *************** cp_build_binary_op (location_t location, *** 4042,4048 **** /* Data type in which the computation is to be performed. In the simplest cases this is the common type of the arguments. */ ! tree result_type = NULL; /* Nonzero means operands have already been type-converted in whatever way is necessary. --- 4042,4048 ---- /* Data type in which the computation is to be performed. In the simplest cases this is the common type of the arguments. */ ! tree result_type = NULL_TREE; /* Nonzero means operands have already been type-converted in whatever way is necessary. *************** cp_build_binary_op (location_t location, *** 4058,4064 **** tree final_type = 0; tree result, result_ovl; - tree orig_type = NULL; /* Nonzero if this is an operation like MIN or MAX which can safely be computed in short if both args are promoted shorts. --- 4058,4063 ---- *************** cp_build_binary_op (location_t location, *** 4090,4096 **** bool doing_shift = false; /* Tree holding instrumentation expression. */ ! tree instrument_expr = NULL; if (code == TRUTH_AND_EXPR || code == TRUTH_ANDIF_EXPR || code == TRUTH_OR_EXPR || code == TRUTH_ORIF_EXPR --- 4089,4095 ---- bool doing_shift = false; /* Tree holding instrumentation expression. */ ! tree instrument_expr = NULL_TREE; if (code == TRUTH_AND_EXPR || code == TRUTH_ANDIF_EXPR || code == TRUTH_OR_EXPR || code == TRUTH_ORIF_EXPR *************** cp_build_binary_op (location_t location, *** 4966,4971 **** --- 4965,4974 ---- return tmp; } + /* Remember the original type; RESULT_TYPE might be changed later on + by shorten_binary_op. */ + tree orig_type = result_type; + if (arithmetic_types_p) { bool first_complex = (code0 == COMPLEX_TYPE); *************** cp_build_binary_op (location_t location, *** 5062,5068 **** if (shorten && none_complex) { - orig_type = result_type; final_type = result_type; result_type = shorten_binary_op (result_type, op0, op1, shorten == -1); --- 5065,5070 ---- *************** cp_build_binary_op (location_t location, *** 5142,5152 **** original result_type. */ tree cop0 = op0; tree cop1 = op1; ! if (orig_type != NULL && result_type != orig_type) ! { ! cop0 = cp_convert (orig_type, op0, complain); ! cop1 = cp_convert (orig_type, op1, complain); ! } instrument_expr = ubsan_instrument_division (location, cop0, cop1); } else if (doing_shift && (flag_sanitize & SANITIZE_SHIFT)) --- 5144,5153 ---- original result_type. */ tree cop0 = op0; tree cop1 = op1; ! if (TREE_TYPE (cop0) != orig_type) ! cop0 = cp_convert (orig_type, op0, complain); ! if (TREE_TYPE (cop1) != orig_type) ! cop1 = cp_convert (orig_type, op1, complain); instrument_expr = ubsan_instrument_division (location, cop0, cop1); } else if (doing_shift && (flag_sanitize & SANITIZE_SHIFT)) *************** cp_build_unary_op (enum tree_code code, *** 5848,5853 **** --- 5849,5856 ---- errstring = _("wrong type argument to bit-complement"); else if (!noconvert && CP_INTEGRAL_TYPE_P (TREE_TYPE (arg))) arg = cp_perform_integral_promotions (arg, complain); + else if (!noconvert && VECTOR_TYPE_P (TREE_TYPE (arg))) + arg = mark_rvalue_use (arg); break; case ABS_EXPR: *************** convert_for_assignment (tree type, tree *** 8341,8347 **** overloaded function. Call instantiate_type to get error messages. */ if (rhstype == unknown_type_node) ! instantiate_type (type, rhs, tf_warning_or_error); else if (fndecl) error ("cannot convert %qT to %qT for argument %qP to %qD", rhstype, type, parmnum, fndecl); --- 8344,8355 ---- overloaded function. Call instantiate_type to get error messages. */ if (rhstype == unknown_type_node) ! { ! tree r = instantiate_type (type, rhs, tf_warning_or_error); ! /* -fpermissive might allow this. */ ! if (!seen_error ()) ! return r; ! } else if (fndecl) error ("cannot convert %qT to %qT for argument %qP to %qD", rhstype, type, parmnum, fndecl); diff -Nrcpad gcc-6.3.0/gcc/cselib.c gcc-6.4.0/gcc/cselib.c *** gcc-6.3.0/gcc/cselib.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/cselib.c Fri May 5 21:48:02 2017 *************** static void unchain_one_value (cselib_va *** 49,55 **** static void unchain_one_elt_list (struct elt_list **); static void unchain_one_elt_loc_list (struct elt_loc_list **); static void remove_useless_values (void); ! static int rtx_equal_for_cselib_1 (rtx, rtx, machine_mode); static unsigned int cselib_hash_rtx (rtx, int, machine_mode); static cselib_val *new_cselib_val (unsigned int, machine_mode, rtx); static void add_mem_for_addr (cselib_val *, cselib_val *, rtx); --- 49,55 ---- static void unchain_one_elt_list (struct elt_list **); static void unchain_one_elt_loc_list (struct elt_loc_list **); static void remove_useless_values (void); ! static int rtx_equal_for_cselib_1 (rtx, rtx, machine_mode, int); static unsigned int cselib_hash_rtx (rtx, int, machine_mode); static cselib_val *new_cselib_val (unsigned int, machine_mode, rtx); static void add_mem_for_addr (cselib_val *, cselib_val *, rtx); *************** cselib_hasher::equal (const cselib_val * *** 125,131 **** /* We don't guarantee that distinct rtx's have different hash values, so we need to do a comparison. */ for (l = v->locs; l; l = l->next) ! if (rtx_equal_for_cselib_1 (l->loc, x, memmode)) { promote_debug_loc (l); return true; --- 125,131 ---- /* We don't guarantee that distinct rtx's have different hash values, so we need to do a comparison. */ for (l = v->locs; l; l = l->next) ! if (rtx_equal_for_cselib_1 (l->loc, x, memmode, 0)) { promote_debug_loc (l); return true; *************** cselib_reg_set_mode (const_rtx x) *** 794,800 **** int rtx_equal_for_cselib_p (rtx x, rtx y) { ! return rtx_equal_for_cselib_1 (x, y, VOIDmode); } /* If x is a PLUS or an autoinc operation, expand the operation, --- 794,800 ---- int rtx_equal_for_cselib_p (rtx x, rtx y) { ! return rtx_equal_for_cselib_1 (x, y, VOIDmode, 0); } /* If x is a PLUS or an autoinc operation, expand the operation, *************** autoinc_split (rtx x, rtx *off, machine_ *** 844,850 **** addresses, MEMMODE should be VOIDmode. */ static int ! rtx_equal_for_cselib_1 (rtx x, rtx y, machine_mode memmode) { enum rtx_code code; const char *fmt; --- 844,850 ---- addresses, MEMMODE should be VOIDmode. */ static int ! rtx_equal_for_cselib_1 (rtx x, rtx y, machine_mode memmode, int depth) { enum rtx_code code; const char *fmt; *************** rtx_equal_for_cselib_1 (rtx x, rtx y, ma *** 877,882 **** --- 877,885 ---- if (GET_CODE (y) == VALUE) return e == canonical_cselib_val (CSELIB_VAL_PTR (y)); + if (depth == 128) + return 0; + for (l = e->locs; l; l = l->next) { rtx t = l->loc; *************** rtx_equal_for_cselib_1 (rtx x, rtx y, ma *** 886,892 **** list. */ if (REG_P (t) || MEM_P (t) || GET_CODE (t) == VALUE) continue; ! else if (rtx_equal_for_cselib_1 (t, y, memmode)) return 1; } --- 889,895 ---- list. */ if (REG_P (t) || MEM_P (t) || GET_CODE (t) == VALUE) continue; ! else if (rtx_equal_for_cselib_1 (t, y, memmode, depth + 1)) return 1; } *************** rtx_equal_for_cselib_1 (rtx x, rtx y, ma *** 897,909 **** cselib_val *e = canonical_cselib_val (CSELIB_VAL_PTR (y)); struct elt_loc_list *l; for (l = e->locs; l; l = l->next) { rtx t = l->loc; if (REG_P (t) || MEM_P (t) || GET_CODE (t) == VALUE) continue; ! else if (rtx_equal_for_cselib_1 (x, t, memmode)) return 1; } --- 900,915 ---- cselib_val *e = canonical_cselib_val (CSELIB_VAL_PTR (y)); struct elt_loc_list *l; + if (depth == 128) + return 0; + for (l = e->locs; l; l = l->next) { rtx t = l->loc; if (REG_P (t) || MEM_P (t) || GET_CODE (t) == VALUE) continue; ! else if (rtx_equal_for_cselib_1 (x, t, memmode, depth + 1)) return 1; } *************** rtx_equal_for_cselib_1 (rtx x, rtx y, ma *** 924,935 **** if (!xoff != !yoff) return 0; ! if (xoff && !rtx_equal_for_cselib_1 (xoff, yoff, memmode)) return 0; /* Don't recurse if nothing changed. */ if (x != xorig || y != yorig) ! return rtx_equal_for_cselib_1 (x, y, memmode); return 0; } --- 930,941 ---- if (!xoff != !yoff) return 0; ! if (xoff && !rtx_equal_for_cselib_1 (xoff, yoff, memmode, depth)) return 0; /* Don't recurse if nothing changed. */ if (x != xorig || y != yorig) ! return rtx_equal_for_cselib_1 (x, y, memmode, depth); return 0; } *************** rtx_equal_for_cselib_1 (rtx x, rtx y, ma *** 963,969 **** case MEM: /* We have to compare any autoinc operations in the addresses using this MEM's mode. */ ! return rtx_equal_for_cselib_1 (XEXP (x, 0), XEXP (y, 0), GET_MODE (x)); default: break; --- 969,976 ---- case MEM: /* We have to compare any autoinc operations in the addresses using this MEM's mode. */ ! return rtx_equal_for_cselib_1 (XEXP (x, 0), XEXP (y, 0), GET_MODE (x), ! depth); default: break; *************** rtx_equal_for_cselib_1 (rtx x, rtx y, ma *** 998,1014 **** /* And the corresponding elements must match. */ for (j = 0; j < XVECLEN (x, i); j++) if (! rtx_equal_for_cselib_1 (XVECEXP (x, i, j), ! XVECEXP (y, i, j), memmode)) return 0; break; case 'e': if (i == 1 && targetm.commutative_p (x, UNKNOWN) ! && rtx_equal_for_cselib_1 (XEXP (x, 1), XEXP (y, 0), memmode) ! && rtx_equal_for_cselib_1 (XEXP (x, 0), XEXP (y, 1), memmode)) return 1; ! if (! rtx_equal_for_cselib_1 (XEXP (x, i), XEXP (y, i), memmode)) return 0; break; --- 1005,1024 ---- /* And the corresponding elements must match. */ for (j = 0; j < XVECLEN (x, i); j++) if (! rtx_equal_for_cselib_1 (XVECEXP (x, i, j), ! XVECEXP (y, i, j), memmode, depth)) return 0; break; case 'e': if (i == 1 && targetm.commutative_p (x, UNKNOWN) ! && rtx_equal_for_cselib_1 (XEXP (x, 1), XEXP (y, 0), memmode, ! depth) ! && rtx_equal_for_cselib_1 (XEXP (x, 0), XEXP (y, 1), memmode, ! depth)) return 1; ! if (! rtx_equal_for_cselib_1 (XEXP (x, i), XEXP (y, i), memmode, ! depth)) return 0; break; diff -Nrcpad gcc-6.3.0/gcc/data-streamer-in.c gcc-6.4.0/gcc/data-streamer-in.c *** gcc-6.3.0/gcc/data-streamer-in.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/data-streamer-in.c Wed Mar 22 14:32:24 2017 *************** gcov_type *** 181,186 **** streamer_read_gcov_count (struct lto_input_block *ib) { gcov_type ret = streamer_read_hwi (ib); - gcc_assert (ret >= 0); return ret; } --- 181,185 ---- diff -Nrcpad gcc-6.3.0/gcc/data-streamer-out.c gcc-6.4.0/gcc/data-streamer-out.c *** gcc-6.3.0/gcc/data-streamer-out.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/data-streamer-out.c Wed Mar 22 14:32:24 2017 *************** streamer_write_hwi_stream (struct lto_ou *** 340,346 **** void streamer_write_gcov_count_stream (struct lto_output_stream *obs, gcov_type work) { - gcc_assert (work >= 0); gcc_assert ((HOST_WIDE_INT) work == work); streamer_write_hwi_stream (obs, work); } --- 340,345 ---- diff -Nrcpad gcc-6.3.0/gcc/doc/aot-compile.1 gcc-6.4.0/gcc/doc/aot-compile.1 *** gcc-6.3.0/gcc/doc/aot-compile.1 Wed Dec 21 09:34:12 2016 --- gcc-6.4.0/gcc/doc/aot-compile.1 Tue Jul 4 09:27:49 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "AOT-COMPILE 1" ! .TH AOT-COMPILE 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "AOT-COMPILE 1" ! .TH AOT-COMPILE 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/cpp.1 gcc-6.4.0/gcc/doc/cpp.1 *** gcc-6.3.0/gcc/doc/cpp.1 Wed Dec 21 08:06:52 2016 --- gcc-6.4.0/gcc/doc/cpp.1 Tue Jul 4 07:37:44 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "CPP 1" ! .TH CPP 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "CPP 1" ! .TH CPP 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** get trigraph conversion without warnings *** 302,308 **** .IP "\fB\-Wtraditional\fR" 4 .IX Item "-Wtraditional" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C.\s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and problematic constructs which should be avoided. .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" --- 306,312 ---- .IP "\fB\-Wtraditional\fR" 4 .IX Item "-Wtraditional" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and problematic constructs which should be avoided. .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" *************** line. If the value is less than 1 or gr *** 749,755 **** ignored. The default is 8. .IP "\fB\-fdebug\-cpp\fR" 4 .IX Item "-fdebug-cpp" ! This option is only useful for debugging \s-1GCC.\s0 When used with \&\fB\-E\fR, dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. The dump of the map holding the location of a token would --- 753,759 ---- ignored. The default is 8. .IP "\fB\-fdebug\-cpp\fR" 4 .IX Item "-fdebug-cpp" ! This option is only useful for debugging \s-1GCC. \s0 When used with \&\fB\-E\fR, dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. The dump of the map holding the location of a token would *************** Note that \f(CW\*(C`\-ftrack\-macro\-exp *** 782,788 **** .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fexec-charset=charset" Set the execution character set, used for string and character ! constants. The default is \s-1UTF\-8.\s0 \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fwide-exec-charset=charset" --- 786,792 ---- .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fexec-charset=charset" Set the execution character set, used for string and character ! constants. The default is \s-1UTF\-8. \s0\fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fwide-exec-charset=charset" *************** problems with encodings that do not fit *** 795,803 **** .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 .IX Item "-finput-charset=charset" Set the input character set, used for translation from the character ! set of the input file to the source character set used by \s-1GCC.\s0 If the locale does not specify, or \s-1GCC\s0 cannot get this information from the ! locale, the default is \s-1UTF\-8.\s0 This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. --- 799,807 ---- .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 .IX Item "-finput-charset=charset" Set the input character set, used for translation from the character ! set of the input file to the source character set used by \s-1GCC. \s0 If the locale does not specify, or \s-1GCC\s0 cannot get this information from the ! locale, the default is \s-1UTF\-8. \s0 This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. *************** main input file is omitted. *** 1016,1022 **** \&\fIbinutils\fR. .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1987\-2016 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or --- 1020,1026 ---- \&\fIbinutils\fR. .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1987\-2017 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or diff -Nrcpad gcc-6.3.0/gcc/doc/cpp.info gcc-6.4.0/gcc/doc/cpp.info *** gcc-6.3.0/gcc/doc/cpp.info Wed Dec 21 09:33:47 2016 --- gcc-6.4.0/gcc/doc/cpp.info Tue Jul 4 09:27:45 2017 *************** *** 1,6 **** ! This is cpp.info, produced by makeinfo version 6.1 from cpp.texi. ! Copyright (C) 1987-2016 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 --- 1,7 ---- ! This is doc/cpp.info, produced by makeinfo version 4.13 from ! /space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/doc/cpp.texi. ! Copyright (C) 1987-2017 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 *************** are (a) (see below), and the Back-Cover *** 18,25 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * Cpp: (cpp). The GNU C preprocessor. --- 19,27 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. ! INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * Cpp: (cpp). The GNU C preprocessor. *************** useful on its own. *** 55,61 **** * Option Index:: * Concept Index:: ! -- The Detailed Node Listing -- Overview --- 57,63 ---- * Option Index:: * Concept Index:: ! --- The Detailed Node Listing --- Overview *************** Obsolete Features *** 130,137 **** * Obsolete Features:: ! ! Copyright (C) 1987-2016 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 --- 132,138 ---- * Obsolete Features:: ! Copyright (C) 1987-2017 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 *************** are (a) (see below), and the Back-Cover *** 149,156 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development.  File: cpp.info, Node: Overview, Next: Header Files, Prev: Top, Up: Top --- 150,157 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development.  File: cpp.info, Node: Overview, Next: Header Files, Prev: Top, Up: Top *************** File: cpp.info, Node: Overview, Next: *** 158,167 **** 1 Overview ********** ! The C preprocessor, often known as "cpp", is a "macro processor" that is ! used automatically by the C compiler to transform your program before ! compilation. It is called a macro processor because it allows you to ! define "macros", which are brief abbreviations for longer constructs. The C preprocessor is intended to be used only with C, C++, and Objective-C source code. In the past, it has been abused as a general --- 159,169 ---- 1 Overview ********** ! The C preprocessor, often known as "cpp", is a "macro processor" that ! is used automatically by the C compiler to transform your program ! before compilation. It is called a macro processor because it allows ! you to define "macros", which are brief abbreviations for longer ! constructs. The C preprocessor is intended to be used only with C, C++, and Objective-C source code. In the past, it has been abused as a general *************** will be removed, and the Makefile will n *** 174,180 **** Having said that, you can often get away with using cpp on things which are not C. Other Algol-ish programming languages are often safe ! (Pascal, Ada, etc.) So is assembly, with caution. '-traditional-cpp' mode preserves more white space, and is otherwise more permissive. Many of the problems can be avoided by writing C or C++ style comments instead of native language comments, and keeping macros simple. --- 176,182 ---- Having said that, you can often get away with using cpp on things which are not C. Other Algol-ish programming languages are often safe ! (Pascal, Ada, etc.) So is assembly, with caution. `-traditional-cpp' mode preserves more white space, and is otherwise more permissive. Many of the problems can be avoided by writing C or C++ style comments instead of native language comments, and keeping macros simple. *************** instead of native language comments, and *** 182,189 **** Wherever possible, you should use a preprocessor geared to the language you are writing in. Modern versions of the GNU assembler have macro facilities. Most high level programming languages have their own ! conditional compilation and inclusion mechanism. If all else fails, try ! a true general text processor, such as GNU M4. C preprocessors vary in some details. This manual discusses the GNU C preprocessor, which provides a small superset of the features of ISO --- 184,191 ---- Wherever possible, you should use a preprocessor geared to the language you are writing in. Modern versions of the GNU assembler have macro facilities. Most high level programming languages have their own ! conditional compilation and inclusion mechanism. If all else fails, ! try a true general text processor, such as GNU M4. C preprocessors vary in some details. This manual discusses the GNU C preprocessor, which provides a small superset of the features of ISO *************** Standard C. In its default mode, the GN *** 191,199 **** few things required by the standard. These are features which are rarely, if ever, used, and may cause surprising changes to the meaning of a program which does not expect them. To get strict ISO Standard C, ! you should use the '-std=c90', '-std=c99' or '-std=c11' options, depending on which version of the standard you want. To get all the ! mandatory diagnostics, you must also use '-pedantic'. *Note Invocation::. This manual describes the behavior of the ISO preprocessor. To --- 193,201 ---- few things required by the standard. These are features which are rarely, if ever, used, and may cause surprising changes to the meaning of a program which does not expect them. To get strict ISO Standard C, ! you should use the `-std=c90', `-std=c99' or `-std=c11' options, depending on which version of the standard you want. To get all the ! mandatory diagnostics, you must also use `-pedantic'. *Note Invocation::. This manual describes the behavior of the ISO preprocessor. To *************** does not conflict with traditional seman *** 202,208 **** preprocessor should behave the same way. The various differences that do exist are detailed in the section *note Traditional Mode::. ! For clarity, unless noted otherwise, references to 'CPP' in this manual refer to GNU CPP. * Menu: --- 204,210 ---- preprocessor should behave the same way. The various differences that do exist are detailed in the section *note Traditional Mode::. ! For clarity, unless noted otherwise, references to `CPP' in this manual refer to GNU CPP. * Menu: *************** there are really at least four. *** 224,265 **** The files input to CPP might be in any character set at all. CPP's very first action, before it even looks for line boundaries, is to ! convert the file into the character set it uses for internal processing. ! That set is what the C standard calls the "source" character set. It ! must be isomorphic with ISO 10646, also known as Unicode. CPP uses the ! UTF-8 encoding of Unicode. The character sets of the input files are specified using the ! '-finput-charset=' option. All preprocessing work (the subject of the rest of this manual) is carried out in the source character set. If you request textual output ! from the preprocessor with the '-E' option, it will be in UTF-8. After preprocessing is complete, string and character constants are ! converted again, into the "execution" character set. This character set ! is under control of the user; the default is UTF-8, matching the source ! character set. Wide string and character constants have their own ! character set, which is not called out specifically in the standard. ! Again, it is under control of the user. The default is UTF-16 or ! UTF-32, whichever fits in the target's 'wchar_t' type, in the target ! machine's byte order.(1) Octal and hexadecimal escape sequences do not ! undergo conversion; '\x12' has the value 0x12 regardless of the currently selected execution character set. All other escapes are replaced by the character in the source character set that they represent, then converted to the execution character set, just like unescaped characters. In identifiers, characters outside the ASCII range can only be ! specified with the '\u' and '\U' escapes, not used directly. If strict ! ISO C90 conformance is specified with an option such as '-std=c90', or ! '-fno-extended-identifiers' is used, then those escapes are not permitted in identifiers. ---------- Footnotes ---------- (1) UTF-16 does not meet the requirements of the C standard for a ! wide character set, but the choice of 16-bit 'wchar_t' is enshrined in some system ABIs so we cannot fix this.  --- 226,267 ---- The files input to CPP might be in any character set at all. CPP's very first action, before it even looks for line boundaries, is to ! convert the file into the character set it uses for internal ! processing. That set is what the C standard calls the "source" ! character set. It must be isomorphic with ISO 10646, also known as ! Unicode. CPP uses the UTF-8 encoding of Unicode. The character sets of the input files are specified using the ! `-finput-charset=' option. All preprocessing work (the subject of the rest of this manual) is carried out in the source character set. If you request textual output ! from the preprocessor with the `-E' option, it will be in UTF-8. After preprocessing is complete, string and character constants are ! converted again, into the "execution" character set. This character ! set is under control of the user; the default is UTF-8, matching the ! source character set. Wide string and character constants have their ! own character set, which is not called out specifically in the ! standard. Again, it is under control of the user. The default is ! UTF-16 or UTF-32, whichever fits in the target's `wchar_t' type, in the ! target machine's byte order.(1) Octal and hexadecimal escape sequences ! do not undergo conversion; '\x12' has the value 0x12 regardless of the currently selected execution character set. All other escapes are replaced by the character in the source character set that they represent, then converted to the execution character set, just like unescaped characters. In identifiers, characters outside the ASCII range can only be ! specified with the `\u' and `\U' escapes, not used directly. If strict ! ISO C90 conformance is specified with an option such as `-std=c90', or ! `-fno-extended-identifiers' is used, then those escapes are not permitted in identifiers. ---------- Footnotes ---------- (1) UTF-16 does not meet the requirements of the C standard for a ! wide character set, but the choice of 16-bit `wchar_t' is enshrined in some system ABIs so we cannot fix this.  *************** standard. *** 279,313 **** 1. The input file is read into memory and broken into lines. Different systems use different conventions to indicate the end of ! a line. GCC accepts the ASCII control sequences 'LF', 'CR LF' and ! 'CR' as end-of-line markers. These are the canonical sequences used by Unix, DOS and VMS, and the classic Mac OS (before OSX) ! respectively. You may therefore safely copy source code written on ! any of those systems to a different one and use it without conversion. (GCC may lose track of the current line number if a file doesn't consistently use one convention, as sometimes happens when it is edited on computers with different conventions that share a network file system.) ! If the last line of any input file lacks an end-of-line marker, the ! end of the file is considered to implicitly supply one. The C standard says that this condition provokes undefined behavior, so GCC will emit a warning message. 2. If trigraphs are enabled, they are replaced by their corresponding single characters. By default GCC ignores trigraphs, but if you ! request a strictly conforming mode with the '-std' option, or you ! specify the '-trigraphs' option, then it converts them. ! These are nine three-character sequences, all starting with '??', that are defined by ISO C to stand for single characters. They ! permit obsolete systems that lack some of C's punctuation to use C. ! For example, '??/' stands for '\', so '??/n' is a character constant for a newline. Trigraphs are not popular and many compilers implement them incorrectly. Portable code should not rely on trigraphs being ! either converted or ignored. With '-Wtrigraphs' GCC will warn you when a trigraph may change the meaning of your program if it were converted. *Note Wtrigraphs::. --- 281,315 ---- 1. The input file is read into memory and broken into lines. Different systems use different conventions to indicate the end of ! a line. GCC accepts the ASCII control sequences `LF', `CR LF' and ! `CR' as end-of-line markers. These are the canonical sequences used by Unix, DOS and VMS, and the classic Mac OS (before OSX) ! respectively. You may therefore safely copy source code written ! on any of those systems to a different one and use it without conversion. (GCC may lose track of the current line number if a file doesn't consistently use one convention, as sometimes happens when it is edited on computers with different conventions that share a network file system.) ! If the last line of any input file lacks an end-of-line marker, ! the end of the file is considered to implicitly supply one. The C standard says that this condition provokes undefined behavior, so GCC will emit a warning message. 2. If trigraphs are enabled, they are replaced by their corresponding single characters. By default GCC ignores trigraphs, but if you ! request a strictly conforming mode with the `-std' option, or you ! specify the `-trigraphs' option, then it converts them. ! These are nine three-character sequences, all starting with `??', that are defined by ISO C to stand for single characters. They ! permit obsolete systems that lack some of C's punctuation to use ! C. For example, `??/' stands for `\', so '??/n' is a character constant for a newline. Trigraphs are not popular and many compilers implement them incorrectly. Portable code should not rely on trigraphs being ! either converted or ignored. With `-Wtrigraphs' GCC will warn you when a trigraph may change the meaning of your program if it were converted. *Note Wtrigraphs::. *************** standard. *** 315,322 **** from being confused with a trigraph by inserting a backslash between the question marks, or by separating the string literal at the trigraph and making use of string literal concatenation. ! "(??\?)" is the string '(???)', not '(?]'. Traditional C compilers ! do not recognize these idioms. The nine trigraphs and their replacements are --- 317,324 ---- from being confused with a trigraph by inserting a backslash between the question marks, or by separating the string literal at the trigraph and making use of string literal concatenation. ! "(??\?)" is the string `(???)', not `(?]'. Traditional C ! compilers do not recognize these idioms. The nine trigraphs and their replacements are *************** standard. *** 325,331 **** 3. Continued lines are merged into one long line. ! A continued line is a line which ends with a backslash, '\'. The backslash is removed and the following line is joined with the current one. No space is inserted, so you may split a line anywhere, even in the middle of a word. (It is generally more --- 327,333 ---- 3. Continued lines are merged into one long line. ! A continued line is a line which ends with a backslash, `\'. The backslash is removed and the following line is joined with the current one. No space is inserted, so you may split a line anywhere, even in the middle of a word. (It is generally more *************** standard. *** 336,352 **** If there is white space between a backslash and the end of a line, that is still a continued line. However, as this is usually the ! result of an editing mistake, and many compilers will not accept it ! as a continued line, GCC will warn you about it. 4. All comments are replaced with single spaces. ! There are two kinds of comments. "Block comments" begin with '/*' ! and continue until the next '*/'. Block comments do not nest: /* this is /* one comment */ text outside comment ! "Line comments" begin with '//' and continue to the end of the current line. Line comments do not nest either, but it does not matter, because they would end in the same place anyway. --- 338,354 ---- If there is white space between a backslash and the end of a line, that is still a continued line. However, as this is usually the ! result of an editing mistake, and many compilers will not accept ! it as a continued line, GCC will warn you about it. 4. All comments are replaced with single spaces. ! There are two kinds of comments. "Block comments" begin with `/*' ! and continue until the next `*/'. Block comments do not nest: /* this is /* one comment */ text outside comment ! "Line comments" begin with `//' and continue to the end of the current line. Line comments do not nest either, but it does not matter, because they would end in the same place anyway. *************** comment. *** 369,375 **** oops! this isn't a comment anymore */ Comments are not recognized within string literals. "/* blah */" is ! the string constant '/* blah */', not an empty string. Line comments are not in the 1989 edition of the C standard, but they are recognized by GCC as an extension. In C++ and in the 1999 edition --- 371,377 ---- oops! this isn't a comment anymore */ Comments are not recognized within string literals. "/* blah */" is ! the string constant `/* blah */', not an empty string. Line comments are not in the 1989 edition of the C standard, but they are recognized by GCC as an extension. In C++ and in the 1999 edition *************** of the C standard, they are an official *** 378,385 **** Since these transformations happen before all other processing, you can split a line mechanically with backslash-newline anywhere. You can comment out the end of a line. You can continue a line comment onto the ! next line with backslash-newline. You can even split '/*', '*/', and ! '//' onto multiple lines with backslash-newline. For example: /\ * --- 380,387 ---- Since these transformations happen before all other processing, you can split a line mechanically with backslash-newline anywhere. You can comment out the end of a line. You can continue a line comment onto the ! next line with backslash-newline. You can even split `/*', `*/', and ! `//' onto multiple lines with backslash-newline. For example: /\ * *************** next line with backslash-newline. You c *** 389,395 **** O 10\ 20 ! is equivalent to '#define FOO 1020'. All these tricks are extremely confusing and should not be used in code intended to be readable. There is no way to prevent a backslash at the end of a line from --- 391,397 ---- O 10\ 20 ! is equivalent to `#define FOO 1020'. All these tricks are extremely confusing and should not be used in code intended to be readable. There is no way to prevent a backslash at the end of a line from *************** token of any kind. Tokens do not have t *** 410,423 **** but it is often necessary to avoid ambiguities. When faced with a sequence of characters that has more than one ! possible tokenization, the preprocessor is greedy. It always makes each ! token, starting from the left, as big as possible before moving on to ! the next token. For instance, 'a+++++b' is interpreted as ! 'a ++ ++ + b', not as 'a ++ + ++ b', even though the latter tokenization ! could be part of a valid C program and the former could not. Once the input file is broken into tokens, the token boundaries never ! change, except when the '##' preprocessing operator is used to paste tokens together. *Note Concatenation::. For example, #define foo() bar --- 412,426 ---- but it is often necessary to avoid ambiguities. When faced with a sequence of characters that has more than one ! possible tokenization, the preprocessor is greedy. It always makes ! each token, starting from the left, as big as possible before moving on ! to the next token. For instance, `a+++++b' is interpreted as ! `a ++ ++ + b', not as `a ++ + ++ b', even though the latter ! tokenization could be part of a valid C program and the former could ! not. Once the input file is broken into tokens, the token boundaries never ! change, except when the `##' preprocessing operator is used to paste tokens together. *Note Concatenation::. For example, #define foo() bar *************** preprocessing token becomes one compiler *** 431,442 **** Preprocessing tokens fall into five broad classes: identifiers, preprocessing numbers, string literals, punctuators, and other. An ! "identifier" is the same as an identifier in C: any sequence of letters, ! digits, or underscores, which begins with a letter or underscore. ! Keywords of C have no significance to the preprocessor; they are ! ordinary identifiers. You can define a macro whose name is a keyword, ! for instance. The only identifier which can be considered a ! preprocessing keyword is 'defined'. *Note Defined::. This is mostly true of other languages which use the C preprocessor. However, a few of the keywords of C++ are significant even in the --- 434,445 ---- Preprocessing tokens fall into five broad classes: identifiers, preprocessing numbers, string literals, punctuators, and other. An ! "identifier" is the same as an identifier in C: any sequence of ! letters, digits, or underscores, which begins with a letter or ! underscore. Keywords of C have no significance to the preprocessor; ! they are ordinary identifiers. You can define a macro whose name is a ! keyword, for instance. The only identifier which can be considered a ! preprocessing keyword is `defined'. *Note Defined::. This is mostly true of other languages which use the C preprocessor. However, a few of the keywords of C++ are significant even in the *************** preprocessor. *Note C++ Named Operators *** 446,458 **** part of the "basic source character set", at the implementation's discretion (such as accented Latin letters, Greek letters, or Chinese ideograms). This may be done with an extended character set, or the ! '\u' and '\U' escape sequences. GCC only accepts such characters in the ! '\u' and '\U' forms. ! As an extension, GCC treats '$' as a letter. This is for ! compatibility with some systems, such as VMS, where '$' is commonly used ! in system-defined function and object names. '$' is not a letter in ! strictly conforming mode, or if you specify the '-$' option. *Note Invocation::. A "preprocessing number" has a rather bizarre definition. The --- 449,461 ---- part of the "basic source character set", at the implementation's discretion (such as accented Latin letters, Greek letters, or Chinese ideograms). This may be done with an extended character set, or the ! `\u' and `\U' escape sequences. GCC only accepts such characters in ! the `\u' and `\U' forms. ! As an extension, GCC treats `$' as a letter. This is for ! compatibility with some systems, such as VMS, where `$' is commonly ! used in system-defined function and object names. `$' is not a letter ! in strictly conforming mode, or if you specify the `-$' option. *Note Invocation::. A "preprocessing number" has a rather bizarre definition. The *************** one expects of C, but also a number of o *** 461,469 **** initially recognize as a number. Formally, preprocessing numbers begin with an optional period, a required decimal digit, and then continue with any sequence of letters, digits, underscores, periods, and ! exponents. Exponents are the two-character sequences 'e+', 'e-', 'E+', ! 'E-', 'p+', 'p-', 'P+', and 'P-'. (The exponents that begin with 'p' or ! 'P' are new to C99. They are used for hexadecimal floating-point constants.) The purpose of this unusual definition is to isolate the preprocessor --- 464,472 ---- initially recognize as a number. Formally, preprocessing numbers begin with an optional period, a required decimal digit, and then continue with any sequence of letters, digits, underscores, periods, and ! exponents. Exponents are the two-character sequences `e+', `e-', `E+', ! `E-', `p+', `p-', `P+', and `P-'. (The exponents that begin with `p' ! or `P' are new to C99. They are used for hexadecimal floating-point constants.) The purpose of this unusual definition is to isolate the preprocessor *************** from the full complexity of numeric cons *** 471,492 **** distinguish between lexically valid and invalid floating-point numbers, which is complicated. The definition also permits you to split an identifier at any position and get exactly two tokens, which can then be ! pasted back together with the '##' operator. It's possible for preprocessing numbers to cause programs to be ! misinterpreted. For example, '0xE+12' is a preprocessing number which does not translate to any valid numeric constant, therefore a syntax ! error. It does not mean '0xE + 12', which is what you might have intended. "String literals" are string constants, character constants, and ! header file names (the argument of '#include').(1) String constants and ! character constants are straightforward: "..." or '...'. In either case ! embedded quotes should be escaped with a backslash: '\'' is the ! character constant for '''. There is no limit on the length of a character constant, but the value of a character constant that contains ! more than one character is implementation-defined. *Note Implementation ! Details::. Header file names either look like string constants, "...", or are written with angle brackets instead, <...>. In either case, backslash --- 474,495 ---- distinguish between lexically valid and invalid floating-point numbers, which is complicated. The definition also permits you to split an identifier at any position and get exactly two tokens, which can then be ! pasted back together with the `##' operator. It's possible for preprocessing numbers to cause programs to be ! misinterpreted. For example, `0xE+12' is a preprocessing number which does not translate to any valid numeric constant, therefore a syntax ! error. It does not mean `0xE + 12', which is what you might have intended. "String literals" are string constants, character constants, and ! header file names (the argument of `#include').(1) String constants ! and character constants are straightforward: "..." or '...'. In either ! case embedded quotes should be escaped with a backslash: '\'' is the ! character constant for `''. There is no limit on the length of a character constant, but the value of a character constant that contains ! more than one character is implementation-defined. *Note ! Implementation Details::. Header file names either look like string constants, "...", or are written with angle brackets instead, <...>. In either case, backslash *************** Operation::. *** 497,515 **** No string literal may extend past the end of a line. Older versions of GCC accepted multi-line string constants. You may use continued ! lines instead, or string constant concatenation. *Note Differences from ! previous versions::. "Punctuators" are all the usual bits of punctuation which are meaningful to C and C++. All but three of the punctuation characters in ! ASCII are C punctuators. The exceptions are '@', '$', and '`'. In addition, all the two- and three-character operators are punctuators. ! There are also six "digraphs", which the C++ standard calls "alternative ! tokens", which are merely alternate ways to spell other punctuators. ! This is a second attempt to work around missing punctuation in obsolete ! systems. It has no negative side effects, unlike trigraphs, but does ! not cover as much ground. The digraphs and their corresponding normal ! punctuators are: Digraph: <% %> <: :> %: %:%: Punctuator: { } [ ] # ## --- 500,518 ---- No string literal may extend past the end of a line. Older versions of GCC accepted multi-line string constants. You may use continued ! lines instead, or string constant concatenation. *Note Differences ! from previous versions::. "Punctuators" are all the usual bits of punctuation which are meaningful to C and C++. All but three of the punctuation characters in ! ASCII are C punctuators. The exceptions are `@', `$', and ``'. In addition, all the two- and three-character operators are punctuators. ! There are also six "digraphs", which the C++ standard calls ! "alternative tokens", which are merely alternate ways to spell other ! punctuators. This is a second attempt to work around missing ! punctuation in obsolete systems. It has no negative side effects, ! unlike trigraphs, but does not cover as much ground. The digraphs and ! their corresponding normal punctuators are: Digraph: <% %> <: :> %: %:%: Punctuator: { } [ ] # ## *************** punctuators are: *** 517,527 **** Any other single character is considered "other". It is passed on to the preprocessor's output unmolested. The C compiler will almost certainly reject source code containing "other" tokens. In ASCII, the ! only other characters are '@', '$', '`', and control characters other ! than NUL (all bits zero). (Note that '$' is normally considered a ! letter.) All characters with the high bit set (numeric range 0x7F-0xFF) ! are also "other" in the present implementation. This will change when ! proper support for international character sets is added to GCC. NUL is a special case because of the high probability that its appearance is accidental, and because it may be invisible to the user --- 520,531 ---- Any other single character is considered "other". It is passed on to the preprocessor's output unmolested. The C compiler will almost certainly reject source code containing "other" tokens. In ASCII, the ! only other characters are `@', `$', ``', and control characters other ! than NUL (all bits zero). (Note that `$' is normally considered a ! letter.) All characters with the high bit set (numeric range ! 0x7F-0xFF) are also "other" in the present implementation. This will ! change when proper support for international character sets is added to ! GCC. NUL is a special case because of the high probability that its appearance is accidental, and because it may be invisible to the user *************** have the same meaning. *** 533,541 **** #define X^@1 #define X 1 ! (where '^@' is ASCII NUL). Within string or character constants, NULs ! are preserved. In the latter two cases the preprocessor emits a warning ! message. ---------- Footnotes ---------- --- 537,545 ---- #define X^@1 #define X 1 ! (where `^@' is ASCII NUL). Within string or character constants, NULs ! are preserved. In the latter two cases the preprocessor emits a ! warning message. ---------- Footnotes ---------- *************** and "macros" to be expanded. Its primar *** 569,576 **** program according to various conditions. * Line control. If you use a program to combine or rearrange source ! files into an intermediate file which is then compiled, you can use ! line control to inform the compiler where each source line originally came from. * Diagnostics. You can detect problems at compile time and issue --- 573,580 ---- program according to various conditions. * Line control. If you use a program to combine or rearrange source ! files into an intermediate file which is then compiled, you can ! use line control to inform the compiler where each source line originally came from. * Diagnostics. You can detect problems at compile time and issue *************** and "macros" to be expanded. Its primar *** 579,594 **** There are a few more, less useful, features. Except for expansion of predefined macros, all these operations are ! triggered with "preprocessing directives". Preprocessing directives are ! lines in your program that start with '#'. Whitespace is allowed before ! and after the '#'. The '#' is followed by an identifier, the "directive ! name". It specifies the operation to perform. Directives are commonly ! referred to as '#NAME' where NAME is the directive name. For example, ! '#define' is the directive that defines a macro. ! The '#' which begins a directive cannot come from a macro expansion. ! Also, the directive name is not macro expanded. Thus, if 'foo' is ! defined as a macro expanding to 'define', that does not make '#foo' a valid preprocessing directive. The set of valid directive names is fixed. Programs cannot define --- 583,598 ---- There are a few more, less useful, features. Except for expansion of predefined macros, all these operations are ! triggered with "preprocessing directives". Preprocessing directives ! are lines in your program that start with `#'. Whitespace is allowed ! before and after the `#'. The `#' is followed by an identifier, the ! "directive name". It specifies the operation to perform. Directives ! are commonly referred to as `#NAME' where NAME is the directive name. ! For example, `#define' is the directive that defines a macro. ! The `#' which begins a directive cannot come from a macro expansion. ! Also, the directive name is not macro expanded. Thus, if `foo' is ! defined as a macro expanding to `define', that does not make `#foo' a valid preprocessing directive. The set of valid directive names is fixed. Programs cannot define *************** new preprocessing directives. *** 596,603 **** Some directives require arguments; these make up the rest of the directive line and must be separated from the directive name by ! whitespace. For example, '#define' must be followed by a macro name and ! the intended expansion of the macro. A preprocessing directive cannot cover more than one line. The line may, however, be continued with backslash-newline, or by a block comment --- 600,607 ---- Some directives require arguments; these make up the rest of the directive line and must be separated from the directive name by ! whitespace. For example, `#define' must be followed by a macro name ! and the intended expansion of the macro. A preprocessing directive cannot cover more than one line. The line may, however, be continued with backslash-newline, or by a block comment *************** File: cpp.info, Node: Header Files, Ne *** 614,620 **** A header file is a file containing C declarations and macro definitions (*note Macros::) to be shared between several source files. You request the use of a header file in your program by "including" it, with the C ! preprocessing directive '#include'. Header files serve two purposes. --- 618,624 ---- A header file is a file containing C declarations and macro definitions (*note Macros::) to be shared between several source files. You request the use of a header file in your program by "including" it, with the C ! preprocessing directive `#include'. Header files serve two purposes. *************** preprocessing directive '#include'. *** 625,632 **** * Your own header files contain declarations for interfaces between the source files of your program. Each time you have a group of ! related declarations and macro definitions all or most of which are ! needed in several different source files, it is a good idea to create a header file for them. Including a header file produces the same results as copying the --- 629,636 ---- * Your own header files contain declarations for interfaces between the source files of your program. Each time you have a group of ! related declarations and macro definitions all or most of which ! are needed in several different source files, it is a good idea to create a header file for them. Including a header file produces the same results as copying the *************** as the risk that a failure to find one c *** 640,646 **** inconsistencies within a program. In C, the usual convention is to give header files names that end ! with '.h'. It is most portable to use only letters, digits, dashes, and underscores in header file names, and at most one dot. * Menu: --- 644,650 ---- inconsistencies within a program. In C, the usual convention is to give header files names that end ! with `.h'. It is most portable to use only letters, digits, dashes, and underscores in header file names, and at most one dot. * Menu: *************** File: cpp.info, Node: Include Syntax, *** 661,693 **** ================== Both user and system header files are included using the preprocessing ! directive '#include'. It has two variants: ! '#include ' This variant is used for system header files. It searches for a file named FILE in a standard list of system directories. You can ! prepend directories to this list with the '-I' option (*note Invocation::). ! '#include "FILE"' This variant is used for header files of your own program. It searches for a file named FILE first in the directory containing the current file, then in the quote directories and then the same ! directories used for ''. You can prepend directories to the ! list of quote directories with the '-iquote' option. ! The argument of '#include', whether delimited with quote marks or angle brackets, behaves like a string constant in that comments are not ! recognized, and macro names are not expanded. Thus, '#include ' ! specifies inclusion of a system header file named 'x/*y'. However, if backslashes occur within FILE, they are considered ordinary text characters, not escape characters. None of the character escape sequences appropriate to string constants in C are processed. ! Thus, '#include "x\n\\y"' specifies a filename containing three ! backslashes. (Some systems interpret '\' as a pathname separator. All ! of these also interpret '/' the same way. It is most portable to use ! only '/'.) It is an error if there is anything (other than comments) on the line after the file name. --- 665,697 ---- ================== Both user and system header files are included using the preprocessing ! directive `#include'. It has two variants: ! `#include ' This variant is used for system header files. It searches for a file named FILE in a standard list of system directories. You can ! prepend directories to this list with the `-I' option (*note Invocation::). ! `#include "FILE"' This variant is used for header files of your own program. It searches for a file named FILE first in the directory containing the current file, then in the quote directories and then the same ! directories used for `'. You can prepend directories to the ! list of quote directories with the `-iquote' option. ! The argument of `#include', whether delimited with quote marks or angle brackets, behaves like a string constant in that comments are not ! recognized, and macro names are not expanded. Thus, `#include ' ! specifies inclusion of a system header file named `x/*y'. However, if backslashes occur within FILE, they are considered ordinary text characters, not escape characters. None of the character escape sequences appropriate to string constants in C are processed. ! Thus, `#include "x\n\\y"' specifies a filename containing three ! backslashes. (Some systems interpret `\' as a pathname separator. All ! of these also interpret `/' the same way. It is most portable to use ! only `/'.) It is an error if there is anything (other than comments) on the line after the file name. *************** File: cpp.info, Node: Include Operation *** 698,714 **** 2.2 Include Operation ===================== ! The '#include' directive works by directing the C preprocessor to scan the specified file as input before continuing with the rest of the current file. The output from the preprocessor contains the output already generated, followed by the output resulting from the included file, followed by the output that comes from the text after the ! '#include' directive. For example, if you have a header file 'header.h' ! as follows, char *test (void); ! and a main program called 'program.c' that uses the header file, like this, int x; --- 702,718 ---- 2.2 Include Operation ===================== ! The `#include' directive works by directing the C preprocessor to scan the specified file as input before continuing with the rest of the current file. The output from the preprocessor contains the output already generated, followed by the output resulting from the included file, followed by the output that comes from the text after the ! `#include' directive. For example, if you have a header file ! `header.h' as follows, char *test (void); ! and a main program called `program.c' that uses the header file, like this, int x; *************** this, *** 720,726 **** puts (test ()); } ! the compiler will see the same token stream as it would if 'program.c' read int x; --- 724,730 ---- puts (test ()); } ! the compiler will see the same token stream as it would if `program.c' read int x; *************** the file. *** 746,752 **** syntactic units--function declarations or definitions, type declarations, etc. ! The line following the '#include' directive is always treated as a separate line by the C preprocessor, even if the included file lacks a final newline. --- 750,756 ---- syntactic units--function declarations or definitions, type declarations, etc. ! The line following the `#include' directive is always treated as a separate line by the C preprocessor, even if the included file lacks a final newline. *************** File: cpp.info, Node: Search Path, Nex *** 758,764 **** GCC looks in several different places for headers. On a normal Unix system, if you do not instruct it otherwise, it will look for headers ! requested with '#include ' in: /usr/local/include LIBDIR/gcc/TARGET/VERSION/include --- 762,768 ---- GCC looks in several different places for headers. On a normal Unix system, if you do not instruct it otherwise, it will look for headers ! requested with `#include ' in: /usr/local/include LIBDIR/gcc/TARGET/VERSION/include *************** requested with '#include ' in: *** 766,779 **** /usr/include For C++ programs, it will also look in ! 'LIBDIR/../include/c++/VERSION', first. In the above, TARGET is the canonical name of the system GCC was configured to compile code for; often but not always the same as the canonical name of the system it runs on. VERSION is the version of GCC in use. ! You can add to this list with the '-IDIR' command-line option. All ! the directories named by '-I' are searched, in left-to-right order, ! _before_ the default directories. The only exception is when 'dir' is already searched by default. In this case, the option is ignored and the search order for system directories remains unchanged. --- 770,783 ---- /usr/include For C++ programs, it will also look in ! `LIBDIR/../include/c++/VERSION', first. In the above, TARGET is the canonical name of the system GCC was configured to compile code for; often but not always the same as the canonical name of the system it runs on. VERSION is the version of GCC in use. ! You can add to this list with the `-IDIR' command-line option. All ! the directories named by `-I' are searched, in left-to-right order, ! _before_ the default directories. The only exception is when `dir' is already searched by default. In this case, the option is ignored and the search order for system directories remains unchanged. *************** Thus, it is possible for a directory to *** 783,820 **** chain if it was specified in both the quote and bracket chains. You can prevent GCC from searching any of the default directories ! with the '-nostdinc' option. This is useful when you are compiling an operating system kernel or some other program that does not use the ! standard C library facilities, or the standard C library itself. '-I' ! options are not ignored as described above when '-nostdinc' is in effect. ! GCC looks for headers requested with '#include "FILE"' first in the directory containing the current file, then in the directories as ! specified by '-iquote' options, then in the same places it would have looked for a header requested with angle brackets. For example, if ! '/usr/include/sys/stat.h' contains '#include "types.h"', GCC looks for ! 'types.h' first in '/usr/include/sys', then in its usual search path. ! '#line' (*note Line Control::) does not change GCC's idea of the directory containing the current file. ! You may put '-I-' at any point in your list of '-I' options. This ! has two effects. First, directories appearing before the '-I-' in the list are searched only for headers requested with quote marks. ! Directories after '-I-' are searched for all headers. Second, the directory containing the current file is not searched for anything, ! unless it happens to be one of the directories named by an '-I' switch. ! '-I-' is deprecated, '-iquote' should be used instead. ! '-I. -I-' is not the same as no '-I' options at all, and does not ! cause the same behavior for '<>' includes that '""' includes get with no ! special options. '-I.' searches the compiler's current working directory for header files. That may or may not be the same as the directory containing the current file. ! If you need to look for headers in a directory named '-', write ! '-I./-'. There are several more ways to adjust the header search path. They are generally less useful. *Note Invocation::. --- 787,824 ---- chain if it was specified in both the quote and bracket chains. You can prevent GCC from searching any of the default directories ! with the `-nostdinc' option. This is useful when you are compiling an operating system kernel or some other program that does not use the ! standard C library facilities, or the standard C library itself. `-I' ! options are not ignored as described above when `-nostdinc' is in effect. ! GCC looks for headers requested with `#include "FILE"' first in the directory containing the current file, then in the directories as ! specified by `-iquote' options, then in the same places it would have looked for a header requested with angle brackets. For example, if ! `/usr/include/sys/stat.h' contains `#include "types.h"', GCC looks for ! `types.h' first in `/usr/include/sys', then in its usual search path. ! `#line' (*note Line Control::) does not change GCC's idea of the directory containing the current file. ! You may put `-I-' at any point in your list of `-I' options. This ! has two effects. First, directories appearing before the `-I-' in the list are searched only for headers requested with quote marks. ! Directories after `-I-' are searched for all headers. Second, the directory containing the current file is not searched for anything, ! unless it happens to be one of the directories named by an `-I' switch. ! `-I-' is deprecated, `-iquote' should be used instead. ! `-I. -I-' is not the same as no `-I' options at all, and does not ! cause the same behavior for `<>' includes that `""' includes get with ! no special options. `-I.' searches the compiler's current working directory for header files. That may or may not be the same as the directory containing the current file. ! If you need to look for headers in a directory named `-', write ! `-I./-'. There are several more ways to adjust the header search path. They are generally less useful. *Note Invocation::. *************** contents of the file in a conditional, l *** 843,862 **** This construct is commonly known as a "wrapper #ifndef". When the header is included again, the conditional will be false, because ! 'FILE_FOO_SEEN' is defined. The preprocessor will skip over the entire contents of the file, and the compiler will not see it twice. CPP optimizes even further. It remembers when a header file has a ! wrapper '#ifndef'. If a subsequent '#include' specifies that header, ! and the macro in the '#ifndef' is still defined, it does not bother to rescan the file at all. You can put comments outside the wrapper. They will not interfere with this optimization. ! The macro 'FILE_FOO_SEEN' is called the "controlling macro" or "guard ! macro". In a user header file, the macro name should not begin with ! '_'. In a system header file, it should begin with '__' to avoid conflicts with user programs. In any kind of header file, the macro name should contain the name of the file and some additional text, to avoid conflicts with other header files. --- 847,866 ---- This construct is commonly known as a "wrapper #ifndef". When the header is included again, the conditional will be false, because ! `FILE_FOO_SEEN' is defined. The preprocessor will skip over the entire contents of the file, and the compiler will not see it twice. CPP optimizes even further. It remembers when a header file has a ! wrapper `#ifndef'. If a subsequent `#include' specifies that header, ! and the macro in the `#ifndef' is still defined, it does not bother to rescan the file at all. You can put comments outside the wrapper. They will not interfere with this optimization. ! The macro `FILE_FOO_SEEN' is called the "controlling macro" or ! "guard macro". In a user header file, the macro name should not begin ! with `_'. In a system header file, it should begin with `__' to avoid conflicts with user programs. In any kind of header file, the macro name should contain the name of the file and some additional text, to avoid conflicts with other header files. *************** File: cpp.info, Node: Alternatives to W *** 868,902 **** =================================== CPP supports two more ways of indicating that a header file should be ! read only once. Neither one is as portable as a wrapper '#ifndef' and we recommend you do not use them in new programs, with the caveat that ! '#import' is standard practice in Objective-C. ! CPP supports a variant of '#include' called '#import' which includes ! a file, but does so at most once. If you use '#import' instead of ! '#include', then you don't need the conditionals inside the header file ! to prevent multiple inclusion of the contents. '#import' is standard in ! Objective-C, but is considered a deprecated extension in C and C++. ! '#import' is not a well designed feature. It requires the users of a ! header file to know that it should only be included once. It is much better for the header file's implementor to write the file so that users ! don't need to know this. Using a wrapper '#ifndef' accomplishes this goal. ! In the present implementation, a single use of '#import' will prevent ! the file from ever being read again, by either '#import' or '#include'. ! You should not rely on this; do not use both '#import' and '#include' to ! refer to the same header file. Another way to prevent a header file from being included more than ! once is with the '#pragma once' directive. If '#pragma once' is seen when scanning a header file, that file will never be read again, no matter what. ! '#pragma once' does not have the problems that '#import' does, but it ! is not recognized by all preprocessors, so you cannot rely on it in a ! portable program.  File: cpp.info, Node: Computed Includes, Next: Wrapper Headers, Prev: Alternatives to Wrapper #ifndef, Up: Header Files --- 872,906 ---- =================================== CPP supports two more ways of indicating that a header file should be ! read only once. Neither one is as portable as a wrapper `#ifndef' and we recommend you do not use them in new programs, with the caveat that ! `#import' is standard practice in Objective-C. ! CPP supports a variant of `#include' called `#import' which includes ! a file, but does so at most once. If you use `#import' instead of ! `#include', then you don't need the conditionals inside the header file ! to prevent multiple inclusion of the contents. `#import' is standard ! in Objective-C, but is considered a deprecated extension in C and C++. ! `#import' is not a well designed feature. It requires the users of ! a header file to know that it should only be included once. It is much better for the header file's implementor to write the file so that users ! don't need to know this. Using a wrapper `#ifndef' accomplishes this goal. ! In the present implementation, a single use of `#import' will ! prevent the file from ever being read again, by either `#import' or ! `#include'. You should not rely on this; do not use both `#import' and ! `#include' to refer to the same header file. Another way to prevent a header file from being included more than ! once is with the `#pragma once' directive. If `#pragma once' is seen when scanning a header file, that file will never be read again, no matter what. ! `#pragma once' does not have the problems that `#import' does, but ! it is not recognized by all preprocessors, so you cannot rely on it in ! a portable program.  File: cpp.info, Node: Computed Includes, Next: Wrapper Headers, Prev: Alternatives to Wrapper #ifndef, Up: Header Files *************** systems, for instance. You could do thi *** 920,946 **** That rapidly becomes tedious. Instead, the preprocessor offers the ability to use a macro for the header name. This is called a "computed include". Instead of writing a header name as the direct argument of ! '#include', you simply put a macro name there instead: #define SYSTEM_H "system_1.h" ... #include SYSTEM_H ! 'SYSTEM_H' will be expanded, and the preprocessor will look for ! 'system_1.h' as if the '#include' had been written that way originally. ! 'SYSTEM_H' could be defined by your Makefile with a '-D' option. ! You must be careful when you define the macro. '#define' saves tokens, not text. The preprocessor has no way of knowing that the macro ! will be used as the argument of '#include', so it generates ordinary tokens, not a header name. This is unlikely to cause problems if you use double-quote includes, which are close enough to string constants. If you use angle brackets, however, you may have trouble. The syntax of a computed include is actually a bit more general than ! the above. If the first non-whitespace character after '#include' is ! not '"' or '<', then the entire line is macro-expanded like running text ! would be. If the line expands to a single string constant, the contents of that string constant are the file to be included. CPP does not re-examine --- 924,950 ---- That rapidly becomes tedious. Instead, the preprocessor offers the ability to use a macro for the header name. This is called a "computed include". Instead of writing a header name as the direct argument of ! `#include', you simply put a macro name there instead: #define SYSTEM_H "system_1.h" ... #include SYSTEM_H ! `SYSTEM_H' will be expanded, and the preprocessor will look for ! `system_1.h' as if the `#include' had been written that way originally. ! `SYSTEM_H' could be defined by your Makefile with a `-D' option. ! You must be careful when you define the macro. `#define' saves tokens, not text. The preprocessor has no way of knowing that the macro ! will be used as the argument of `#include', so it generates ordinary tokens, not a header name. This is unlikely to cause problems if you use double-quote includes, which are close enough to string constants. If you use angle brackets, however, you may have trouble. The syntax of a computed include is actually a bit more general than ! the above. If the first non-whitespace character after `#include' is ! not `"' or `<', then the entire line is macro-expanded like running ! text would be. If the line expands to a single string constant, the contents of that string constant are the file to be included. CPP does not re-examine *************** escapes in the string. Therefore *** 950,969 **** #define HEADER "a\"b" #include HEADER ! looks for a file named 'a\"b'. CPP searches for the file according to the rules for double-quoted includes. ! If the line expands to a token stream beginning with a '<' token and ! including a '>' token, then the tokens between the '<' and the first '>' ! are combined to form the filename to be included. Any whitespace between tokens is reduced to a single space; then any space after the ! initial '<' is retained, but a trailing space before the closing '>' is ignored. CPP searches for the file according to the rules for angle-bracket includes. In either case, if there are any tokens on the line after the file ! name, an error occurs and the directive is not processed. It is also an ! error if the result of expansion does not match either of the two expected forms. These rules are implementation-defined behavior according to the C --- 954,973 ---- #define HEADER "a\"b" #include HEADER ! looks for a file named `a\"b'. CPP searches for the file according to the rules for double-quoted includes. ! If the line expands to a token stream beginning with a `<' token and ! including a `>' token, then the tokens between the `<' and the first ! `>' are combined to form the filename to be included. Any whitespace between tokens is reduced to a single space; then any space after the ! initial `<' is retained, but a trailing space before the closing `>' is ignored. CPP searches for the file according to the rules for angle-bracket includes. In either case, if there are any tokens on the line after the file ! name, an error occurs and the directive is not processed. It is also ! an error if the result of expansion does not match either of the two expected forms. These rules are implementation-defined behavior according to the C *************** File: cpp.info, Node: Wrapper Headers, *** 979,1026 **** =================== Sometimes it is necessary to adjust the contents of a system-provided ! header file without editing it directly. GCC's 'fixincludes' operation does this, for example. One way to do that would be to create a new header file with the same name and insert it in the search path before the original header. That works fine as long as you're willing to replace the old header entirely. But what if you want to refer to the old header from the new one? ! You cannot simply include the old header with '#include'. That will start from the beginning, and find your new header again. If your header is not protected from multiple inclusion (*note Once-Only Headers::), it will recurse infinitely and cause a fatal error. You could include the old header with an absolute pathname: #include "/usr/include/old-header.h" ! This works, but is not clean; should the system headers ever move, you ! would have to edit the new headers to match. There is no way to solve this problem within the C standard, but you ! can use the GNU extension '#include_next'. It means, "Include the ! _next_ file with this name". This directive works like '#include' ! except in searching for the specified file: it starts searching the list ! of header file directories _after_ the directory in which the current ! file was found. ! Suppose you specify '-I /usr/local/include', and the list of ! directories to search also includes '/usr/include'; and suppose both ! directories contain 'signal.h'. Ordinary '#include ' finds ! the file under '/usr/local/include'. If that file contains ! '#include_next ', it starts searching after that directory, ! and finds the file in '/usr/include'. ! '#include_next' does not distinguish between '' and '"FILE"' ! inclusion, nor does it check that the file you specify has the same name ! as the current file. It simply looks for the file named, starting with ! the directory in the search path after the one where the current file ! was found. ! The use of '#include_next' can lead to great confusion. We recommend ! it be used only when there is no other alternative. In particular, it ! should not be used in the headers belonging to a specific program; it ! should be used only to make global corrections along the lines of ! 'fixincludes'.  File: cpp.info, Node: System Headers, Prev: Wrapper Headers, Up: Header Files --- 983,1030 ---- =================== Sometimes it is necessary to adjust the contents of a system-provided ! header file without editing it directly. GCC's `fixincludes' operation does this, for example. One way to do that would be to create a new header file with the same name and insert it in the search path before the original header. That works fine as long as you're willing to replace the old header entirely. But what if you want to refer to the old header from the new one? ! You cannot simply include the old header with `#include'. That will start from the beginning, and find your new header again. If your header is not protected from multiple inclusion (*note Once-Only Headers::), it will recurse infinitely and cause a fatal error. You could include the old header with an absolute pathname: #include "/usr/include/old-header.h" ! This works, but is not clean; should the system headers ever move, ! you would have to edit the new headers to match. There is no way to solve this problem within the C standard, but you ! can use the GNU extension `#include_next'. It means, "Include the ! _next_ file with this name". This directive works like `#include' ! except in searching for the specified file: it starts searching the ! list of header file directories _after_ the directory in which the ! current file was found. ! Suppose you specify `-I /usr/local/include', and the list of ! directories to search also includes `/usr/include'; and suppose both ! directories contain `signal.h'. Ordinary `#include ' finds ! the file under `/usr/local/include'. If that file contains ! `#include_next ', it starts searching after that directory, ! and finds the file in `/usr/include'. ! `#include_next' does not distinguish between `' and `"FILE"' ! inclusion, nor does it check that the file you specify has the same ! name as the current file. It simply looks for the file named, starting ! with the directory in the search path after the one where the current ! file was found. ! The use of `#include_next' can lead to great confusion. We ! recommend it be used only when there is no other alternative. In ! particular, it should not be used in the headers belonging to a specific ! program; it should be used only to make global corrections along the ! lines of `fixincludes'.  File: cpp.info, Node: System Headers, Prev: Wrapper Headers, Up: Header Files *************** File: cpp.info, Node: System Headers, *** 1031,1068 **** The header files declaring interfaces to the operating system and runtime libraries often cannot be written in strictly conforming C. Therefore, GCC gives code found in "system headers" special treatment. ! All warnings, other than those generated by '#warning' (*note Diagnostics::), are suppressed while GCC is processing a system header. Macros defined in a system header are immune to a few warnings wherever ! they are expanded. This immunity is granted on an ad-hoc basis, when we ! find that a warning generates lots of false positives because of code in ! macros defined in system headers. Normally, only the headers found in specific directories are ! considered system headers. These directories are determined when GCC is ! compiled. There are, however, two ways to make normal headers into system headers. ! The '-isystem' command-line option adds its argument to the list of ! directories to search for headers, just like '-I'. Any headers found in ! that directory will be considered system headers. ! All directories named by '-isystem' are searched _after_ all ! directories named by '-I', no matter what their order was on the command ! line. If the same directory is named by both '-I' and '-isystem', the ! '-I' option is ignored. GCC provides an informative message when this ! occurs if '-v' is used. ! There is also a directive, '#pragma GCC system_header', which tells ! GCC to consider the rest of the current include file a system header, no ! matter where it was found. Code that comes before the '#pragma' in the ! file will not be affected. '#pragma GCC system_header' has no effect in ! the primary source file. On very old systems, some of the pre-defined system header directories get even more special treatment. GNU C++ considers code in ! headers found in those directories to be surrounded by an 'extern "C"' ! block. There is no way to request this behavior with a '#pragma', or from the command line.  --- 1035,1072 ---- The header files declaring interfaces to the operating system and runtime libraries often cannot be written in strictly conforming C. Therefore, GCC gives code found in "system headers" special treatment. ! All warnings, other than those generated by `#warning' (*note Diagnostics::), are suppressed while GCC is processing a system header. Macros defined in a system header are immune to a few warnings wherever ! they are expanded. This immunity is granted on an ad-hoc basis, when ! we find that a warning generates lots of false positives because of ! code in macros defined in system headers. Normally, only the headers found in specific directories are ! considered system headers. These directories are determined when GCC ! is compiled. There are, however, two ways to make normal headers into system headers. ! The `-isystem' command-line option adds its argument to the list of ! directories to search for headers, just like `-I'. Any headers found ! in that directory will be considered system headers. ! All directories named by `-isystem' are searched _after_ all ! directories named by `-I', no matter what their order was on the ! command line. If the same directory is named by both `-I' and ! `-isystem', the `-I' option is ignored. GCC provides an informative ! message when this occurs if `-v' is used. ! There is also a directive, `#pragma GCC system_header', which tells ! GCC to consider the rest of the current include file a system header, ! no matter where it was found. Code that comes before the `#pragma' in ! the file will not be affected. `#pragma GCC system_header' has no ! effect in the primary source file. On very old systems, some of the pre-defined system header directories get even more special treatment. GNU C++ considers code in ! headers found in those directories to be surrounded by an `extern "C"' ! block. There is no way to request this behavior with a `#pragma', or from the command line.  *************** File: cpp.info, Node: Macros, Next: Co *** 1073,1089 **** A "macro" is a fragment of code which has been given a name. Whenever the name is used, it is replaced by the contents of the macro. There ! are two kinds of macros. They differ mostly in what they look like when ! they are used. "Object-like" macros resemble data objects when used, ! "function-like" macros resemble function calls. You may define any valid identifier as a macro, even if it is a C keyword. The preprocessor does not know anything about keywords. This ! can be useful if you wish to hide a keyword such as 'const' from an older compiler that does not understand it. However, the preprocessor ! operator 'defined' (*note Defined::) can never be defined as a macro, ! and C++'s named operators (*note C++ Named Operators::) cannot be macros ! when you are compiling C++. * Menu: --- 1077,1093 ---- A "macro" is a fragment of code which has been given a name. Whenever the name is used, it is replaced by the contents of the macro. There ! are two kinds of macros. They differ mostly in what they look like ! when they are used. "Object-like" macros resemble data objects when ! used, "function-like" macros resemble function calls. You may define any valid identifier as a macro, even if it is a C keyword. The preprocessor does not know anything about keywords. This ! can be useful if you wish to hide a keyword such as `const' from an older compiler that does not understand it. However, the preprocessor ! operator `defined' (*note Defined::) can never be defined as a macro, ! and C++'s named operators (*note C++ Named Operators::) cannot be ! macros when you are compiling C++. * Menu: *************** a code fragment. It is called object-li *** 1109,1129 **** object in code that uses it. They are most commonly used to give symbolic names to numeric constants. ! You create macros with the '#define' directive. '#define' is followed by the name of the macro and then the token sequence it should be an abbreviation for, which is variously referred to as the macro's "body", "expansion" or "replacement list". For example, #define BUFFER_SIZE 1024 ! defines a macro named 'BUFFER_SIZE' as an abbreviation for the token ! '1024'. If somewhere after this '#define' directive there comes a C statement of the form foo = (char *) malloc (BUFFER_SIZE); then the C preprocessor will recognize and "expand" the macro ! 'BUFFER_SIZE'. The C compiler will see the same tokens as it would if you had written foo = (char *) malloc (1024); --- 1113,1133 ---- object in code that uses it. They are most commonly used to give symbolic names to numeric constants. ! You create macros with the `#define' directive. `#define' is followed by the name of the macro and then the token sequence it should be an abbreviation for, which is variously referred to as the macro's "body", "expansion" or "replacement list". For example, #define BUFFER_SIZE 1024 ! defines a macro named `BUFFER_SIZE' as an abbreviation for the token ! `1024'. If somewhere after this `#define' directive there comes a C statement of the form foo = (char *) malloc (BUFFER_SIZE); then the C preprocessor will recognize and "expand" the macro ! `BUFFER_SIZE'. The C compiler will see the same tokens as it would if you had written foo = (char *) malloc (1024); *************** you had written *** 1132,1138 **** easier to read when it is possible to tell at a glance which names are macros. ! The macro's body ends at the end of the '#define' line. You may continue the definition onto multiple lines, if necessary, using backslash-newline. When the macro is expanded, however, it will all come out on one line. For example, --- 1136,1142 ---- easier to read when it is possible to tell at a glance which names are macros. ! The macro's body ends at the end of the `#define' line. You may continue the definition onto multiple lines, if necessary, using backslash-newline. When the macro is expanded, however, it will all come out on one line. For example, *************** macros to expand. For example, *** 1174,1191 **** ==> BUFSIZE ==> 1024 ! 'TABLESIZE' is expanded first to produce 'BUFSIZE', then that macro is ! expanded to produce the final result, '1024'. ! Notice that 'BUFSIZE' was not defined when 'TABLESIZE' was defined. ! The '#define' for 'TABLESIZE' uses exactly the expansion you specify--in ! this case, 'BUFSIZE'--and does not check to see whether it too contains ! macro names. Only when you _use_ 'TABLESIZE' is the result of its ! expansion scanned for more macro names. ! This makes a difference if you change the definition of 'BUFSIZE' at ! some point in the source file. 'TABLESIZE', defined as shown, will ! always expand using the definition of 'BUFSIZE' that is currently in effect: #define BUFSIZE 1020 --- 1178,1195 ---- ==> BUFSIZE ==> 1024 ! `TABLESIZE' is expanded first to produce `BUFSIZE', then that macro is ! expanded to produce the final result, `1024'. ! Notice that `BUFSIZE' was not defined when `TABLESIZE' was defined. ! The `#define' for `TABLESIZE' uses exactly the expansion you ! specify--in this case, `BUFSIZE'--and does not check to see whether it ! too contains macro names. Only when you _use_ `TABLESIZE' is the ! result of its expansion scanned for more macro names. ! This makes a difference if you change the definition of `BUFSIZE' at ! some point in the source file. `TABLESIZE', defined as shown, will ! always expand using the definition of `BUFSIZE' that is currently in effect: #define BUFSIZE 1020 *************** effect: *** 1193,1199 **** #undef BUFSIZE #define BUFSIZE 37 ! Now 'TABLESIZE' expands (in two stages) to '37'. If the expansion of a macro contains its own name, either directly or via intermediate macros, it is not expanded again when the expansion is --- 1197,1203 ---- #undef BUFSIZE #define BUFSIZE 37 ! Now `TABLESIZE' expands (in two stages) to `37'. If the expansion of a macro contains its own name, either directly or via intermediate macros, it is not expanded again when the expansion is *************** File: cpp.info, Node: Function-like Mac *** 1207,1214 **** ======================== You can also define macros whose use looks like a function call. These ! are called "function-like macros". To define a function-like macro, you ! use the same '#define' directive, but you put a pair of parentheses immediately after the macro name. For example, #define lang_init() c_init() --- 1211,1218 ---- ======================== You can also define macros whose use looks like a function call. These ! are called "function-like macros". To define a function-like macro, ! you use the same `#define' directive, but you put a pair of parentheses immediately after the macro name. For example, #define lang_init() c_init() *************** same name, and you wish to use the funct *** 1226,1234 **** foo(); funcptr = foo; ! Here the call to 'foo()' will use the macro, but the function pointer ! will get the address of the real function. If the macro were to be ! expanded, it would cause a syntax error. If you put spaces between the macro name and the parentheses in the macro definition, that does not define a function-like macro, it defines --- 1230,1238 ---- foo(); funcptr = foo; ! Here the call to `foo()' will use the macro, but the function ! pointer will get the address of the real function. If the macro were to ! be expanded, it would cause a syntax error. If you put spaces between the macro name and the parentheses in the macro definition, that does not define a function-like macro, it defines *************** parentheses. *** 1241,1247 **** The first two pairs of parentheses in this expansion come from the macro. The third is the pair that was originally after the macro ! invocation. Since 'lang_init' is an object-like macro, it does not consume those parentheses.  --- 1245,1251 ---- The first two pairs of parentheses in this expansion come from the macro. The third is the pair that was originally after the macro ! invocation. Since `lang_init' is an object-like macro, it does not consume those parentheses.  *************** File: cpp.info, Node: Macro Arguments, *** 1250,1260 **** 3.3 Macro Arguments =================== ! Function-like macros can take "arguments", just like true functions. To ! define a macro that uses arguments, you insert "parameters" between the ! pair of parentheses in the macro definition that make the macro ! function-like. The parameters must be valid C identifiers, separated by ! commas and optionally whitespace. To invoke a macro that takes arguments, you write the name of the macro followed by a list of "actual arguments" in parentheses, separated --- 1254,1264 ---- 3.3 Macro Arguments =================== ! Function-like macros can take "arguments", just like true functions. ! To define a macro that uses arguments, you insert "parameters" between ! the pair of parentheses in the macro definition that make the macro ! function-like. The parameters must be valid C identifiers, separated ! by commas and optionally whitespace. To invoke a macro that takes arguments, you write the name of the macro followed by a list of "actual arguments" in parentheses, separated *************** prevent a comma from separating argument *** 1286,1304 **** macro (array[x = y, x + 1]) ! passes two arguments to 'macro': 'array[x = y' and 'x + 1]'. If you ! want to supply 'array[x = y, x + 1]' as an argument, you can write it as ! 'array[(x = y, x + 1)]', which is equivalent C code. All arguments to a macro are completely macro-expanded before they are substituted into the macro body. After substitution, the complete text is scanned again for macros to expand, including the arguments. ! This rule may seem strange, but it is carefully designed so you need not ! worry about whether any function call is actually a macro invocation. ! You can run into trouble if you try to be too clever, though. *Note ! Argument Prescan::, for detailed discussion. ! For example, 'min (min (a, b), c)' is first expanded to min (((a) < (b) ? (a) : (b)), (c)) --- 1290,1308 ---- macro (array[x = y, x + 1]) ! passes two arguments to `macro': `array[x = y' and `x + 1]'. If you ! want to supply `array[x = y, x + 1]' as an argument, you can write it ! as `array[(x = y, x + 1)]', which is equivalent C code. All arguments to a macro are completely macro-expanded before they are substituted into the macro body. After substitution, the complete text is scanned again for macros to expand, including the arguments. ! This rule may seem strange, but it is carefully designed so you need ! not worry about whether any function call is actually a macro ! invocation. You can run into trouble if you try to be too clever, ! though. *Note Argument Prescan::, for detailed discussion. ! For example, `min (min (a, b), c)' is first expanded to min (((a) < (b) ? (a) : (b)), (c)) *************** and then to *** 1314,1334 **** preprocessor (but many macros will then expand to invalid code). You cannot leave out arguments entirely; if a macro takes two arguments, there must be exactly one comma at the top level of its argument list. ! Here are some silly examples using 'min': min(, b) ==> (( ) < (b) ? ( ) : (b)) min(a, ) ==> ((a ) < ( ) ? (a ) : ( )) min(,) ==> (( ) < ( ) ? ( ) : ( )) min((,),) ==> (((,)) < ( ) ? ((,)) : ( )) ! min() error-> macro "min" requires 2 arguments, but only 1 given ! min(,,) error-> macro "min" passed 3 arguments, but takes just 2 ! Whitespace is not a preprocessing token, so if a macro 'foo' takes ! one argument, 'foo ()' and 'foo ( )' both supply it an empty argument. Previous GNU preprocessor implementations and documentation were ! incorrect on this point, insisting that a function-like macro that takes ! a single argument be passed a space if an empty argument was required. Macro parameters appearing inside string literals are not replaced by their corresponding actual arguments. --- 1318,1339 ---- preprocessor (but many macros will then expand to invalid code). You cannot leave out arguments entirely; if a macro takes two arguments, there must be exactly one comma at the top level of its argument list. ! Here are some silly examples using `min': min(, b) ==> (( ) < (b) ? ( ) : (b)) min(a, ) ==> ((a ) < ( ) ? (a ) : ( )) min(,) ==> (( ) < ( ) ? ( ) : ( )) min((,),) ==> (((,)) < ( ) ? ((,)) : ( )) ! min() error--> macro "min" requires 2 arguments, but only 1 given ! min(,,) error--> macro "min" passed 3 arguments, but takes just 2 ! Whitespace is not a preprocessing token, so if a macro `foo' takes ! one argument, `foo ()' and `foo ( )' both supply it an empty argument. Previous GNU preprocessor implementations and documentation were ! incorrect on this point, insisting that a function-like macro that ! takes a single argument be passed a space if an empty argument was ! required. Macro parameters appearing inside string literals are not replaced by their corresponding actual arguments. *************** File: cpp.info, Node: Stringification, *** 1344,1351 **** Sometimes you may want to convert a macro argument into a string constant. Parameters are not replaced inside string constants, but you ! can use the '#' preprocessing operator instead. When a macro parameter ! is used with a leading '#', the preprocessor replaces it with the literal text of the actual argument, converted to a string constant. Unlike normal parameter replacement, the argument is not macro-expanded first. This is called "stringification". --- 1349,1356 ---- Sometimes you may want to convert a macro argument into a string constant. Parameters are not replaced inside string constants, but you ! can use the `#' preprocessing operator instead. When a macro parameter ! is used with a leading `#', the preprocessor replaces it with the literal text of the actual argument, converted to a string constant. Unlike normal parameter replacement, the argument is not macro-expanded first. This is called "stringification". *************** first. This is called "stringification" *** 1353,1361 **** There is no way to combine an argument with surrounding text and stringify it all together. Instead, you can write a series of adjacent string constants and stringified arguments. The preprocessor will ! replace the stringified arguments with string constants. The C compiler ! will then combine all the adjacent string constants into one long ! string. Here is an example of a macro definition that uses stringification: --- 1358,1366 ---- There is no way to combine an argument with surrounding text and stringify it all together. Instead, you can write a series of adjacent string constants and stringified arguments. The preprocessor will ! replace the stringified arguments with string constants. The C ! compiler will then combine all the adjacent string constants into one ! long string. Here is an example of a macro definition that uses stringification: *************** string. *** 1367,1388 **** ==> do { if (x == 0) fprintf (stderr, "Warning: " "x == 0" "\n"); } while (0); ! The argument for 'EXP' is substituted once, as-is, into the 'if' ! statement, and once, stringified, into the argument to 'fprintf'. If ! 'x' were a macro, it would be expanded in the 'if' statement, but not in ! the string. ! The 'do' and 'while (0)' are a kludge to make it possible to write ! 'WARN_IF (ARG);', which the resemblance of 'WARN_IF' to a function would ! make C programmers want to do; see *note Swallowing the Semicolon::. Stringification in C involves more than putting double-quote characters around the fragment. The preprocessor backslash-escapes the ! quotes surrounding embedded string constants, and all backslashes within ! string and character constants, in order to get a valid C string ! constant with the proper contents. Thus, stringifying 'p = "foo\n";' results in "p = \"foo\\n\";". However, backslashes that are not inside ! string or character constants are not duplicated: '\n' by itself stringifies to "\n". All leading and trailing whitespace in text being stringified is --- 1372,1394 ---- ==> do { if (x == 0) fprintf (stderr, "Warning: " "x == 0" "\n"); } while (0); ! The argument for `EXP' is substituted once, as-is, into the `if' ! statement, and once, stringified, into the argument to `fprintf'. If ! `x' were a macro, it would be expanded in the `if' statement, but not ! in the string. ! The `do' and `while (0)' are a kludge to make it possible to write ! `WARN_IF (ARG);', which the resemblance of `WARN_IF' to a function ! would make C programmers want to do; see *note Swallowing the ! Semicolon::. Stringification in C involves more than putting double-quote characters around the fragment. The preprocessor backslash-escapes the ! quotes surrounding embedded string constants, and all backslashes ! within string and character constants, in order to get a valid C string ! constant with the proper contents. Thus, stringifying `p = "foo\n";' results in "p = \"foo\\n\";". However, backslashes that are not inside ! string or character constants are not duplicated: `\n' by itself stringifies to "\n". All leading and trailing whitespace in text being stringified is *************** you have to use two levels of macros. *** 1407,1417 **** ==> str (4) ==> "4" ! 's' is stringified when it is used in 'str', so it is not ! macro-expanded first. But 's' is an ordinary argument to 'xstr', so it ! is completely macro-expanded before 'xstr' itself is expanded (*note ! Argument Prescan::). Therefore, by the time 'str' gets to its argument, ! it has already been macro-expanded.  File: cpp.info, Node: Concatenation, Next: Variadic Macros, Prev: Stringification, Up: Macros --- 1413,1423 ---- ==> str (4) ==> "4" ! `s' is stringified when it is used in `str', so it is not ! macro-expanded first. But `s' is an ordinary argument to `xstr', so it ! is completely macro-expanded before `xstr' itself is expanded (*note ! Argument Prescan::). Therefore, by the time `str' gets to its ! argument, it has already been macro-expanded.  File: cpp.info, Node: Concatenation, Next: Variadic Macros, Prev: Stringification, Up: Macros *************** File: cpp.info, Node: Concatenation, N *** 1420,1458 **** ================= It is often useful to merge two tokens into one while expanding macros. ! This is called "token pasting" or "token concatenation". The '##' preprocessing operator performs token pasting. When a macro is ! expanded, the two tokens on either side of each '##' operator are ! combined into a single token, which then replaces the '##' and the two original tokens in the macro expansion. Usually both will be identifiers, or one will be an identifier and the other a preprocessing number. When pasted, they make a longer identifier. This isn't the only valid case. It is also possible to concatenate two numbers (or a ! number and a name, such as '1.5' and 'e3') into a number. Also, ! multi-character operators such as '+=' can be formed by token pasting. However, two tokens that don't together form a valid token cannot be ! pasted together. For example, you cannot concatenate 'x' with '+' in either order. If you try, the preprocessor issues a warning and emits the two tokens. Whether it puts white space between the tokens is ! undefined. It is common to find unnecessary uses of '##' in complex macros. If you get this warning, it is likely that you can simply ! remove the '##'. ! Both the tokens combined by '##' could come from the macro body, but you could just as well write them as one token in the first place. Token pasting is most useful when one or both of the tokens comes from a ! macro argument. If either of the tokens next to an '##' is a parameter ! name, it is replaced by its actual argument before '##' executes. As with stringification, the actual argument is not macro-expanded first. ! If the argument is empty, that '##' has no effect. Keep in mind that the C preprocessor converts comments to whitespace before macros are even considered. Therefore, you cannot create a ! comment by concatenating '/' and '*'. You can put as much whitespace ! between '##' and its operands as you like, including comments, and you ! can put comments in arguments that will be concatenated. However, it is ! an error if '##' appears at either end of a macro body. Consider a C program that interprets named commands. There probably needs to be a table of commands, perhaps an array of structures declared --- 1426,1464 ---- ================= It is often useful to merge two tokens into one while expanding macros. ! This is called "token pasting" or "token concatenation". The `##' preprocessing operator performs token pasting. When a macro is ! expanded, the two tokens on either side of each `##' operator are ! combined into a single token, which then replaces the `##' and the two original tokens in the macro expansion. Usually both will be identifiers, or one will be an identifier and the other a preprocessing number. When pasted, they make a longer identifier. This isn't the only valid case. It is also possible to concatenate two numbers (or a ! number and a name, such as `1.5' and `e3') into a number. Also, ! multi-character operators such as `+=' can be formed by token pasting. However, two tokens that don't together form a valid token cannot be ! pasted together. For example, you cannot concatenate `x' with `+' in either order. If you try, the preprocessor issues a warning and emits the two tokens. Whether it puts white space between the tokens is ! undefined. It is common to find unnecessary uses of `##' in complex macros. If you get this warning, it is likely that you can simply ! remove the `##'. ! Both the tokens combined by `##' could come from the macro body, but you could just as well write them as one token in the first place. Token pasting is most useful when one or both of the tokens comes from a ! macro argument. If either of the tokens next to an `##' is a parameter ! name, it is replaced by its actual argument before `##' executes. As with stringification, the actual argument is not macro-expanded first. ! If the argument is empty, that `##' has no effect. Keep in mind that the C preprocessor converts comments to whitespace before macros are even considered. Therefore, you cannot create a ! comment by concatenating `/' and `*'. You can put as much whitespace ! between `##' and its operands as you like, including comments, and you ! can put comments in arguments that will be concatenated. However, it ! is an error if `##' appears at either end of a macro body. Consider a C program that interprets named commands. There probably needs to be a table of commands, perhaps an array of structures declared *************** as follows: *** 1471,1482 **** ... }; ! It would be cleaner not to have to give each command name twice, once ! in the string constant and once in the function name. A macro which ! takes the name of a command as an argument can make this unnecessary. ! The string constant can be created with stringification, and the ! function name by concatenating the argument with '_command'. Here is ! how it is done: #define COMMAND(NAME) { #NAME, NAME ## _command } --- 1477,1488 ---- ... }; ! It would be cleaner not to have to give each command name twice, ! once in the string constant and once in the function name. A macro ! which takes the name of a command as an argument can make this ! unnecessary. The string constant can be created with stringification, ! and the function name by concatenating the argument with `_command'. ! Here is how it is done: #define COMMAND(NAME) { #NAME, NAME ## _command } *************** a function. Here is an example: *** 1502,1508 **** This kind of macro is called "variadic". When the macro is invoked, all the tokens in its argument list after the last named argument (this macro has none), including any commas, become the "variable argument". ! This sequence of tokens replaces the identifier '__VA_ARGS__' in the macro body wherever it appears. Thus, we have this expansion: eprintf ("%s:%d: ", input_file, lineno) --- 1508,1514 ---- This kind of macro is called "variadic". When the macro is invoked, all the tokens in its argument list after the last named argument (this macro has none), including any commas, become the "variable argument". ! This sequence of tokens replaces the identifier `__VA_ARGS__' in the macro body wherever it appears. Thus, we have this expansion: eprintf ("%s:%d: ", input_file, lineno) *************** macro body wherever it appears. Thus, w *** 1510,1532 **** The variable argument is completely macro-expanded before it is inserted into the macro expansion, just like an ordinary argument. You ! may use the '#' and '##' operators to stringify the variable argument or ! to paste its leading or trailing token with another token. (But see ! below for an important special case for '##'.) If your macro is complicated, you may want a more descriptive name ! for the variable argument than '__VA_ARGS__'. CPP permits this, as an ! extension. You may write an argument name immediately before the '...'; ! that name is used for the variable argument. The 'eprintf' macro above ! could be written #define eprintf(args...) fprintf (stderr, args) ! using this extension. You cannot use '__VA_ARGS__' and this extension in the same macro. You can have named arguments as well as variable arguments in a ! variadic macro. We could define 'eprintf' like this, instead: #define eprintf(format, ...) fprintf (stderr, format, __VA_ARGS__) --- 1516,1538 ---- The variable argument is completely macro-expanded before it is inserted into the macro expansion, just like an ordinary argument. You ! may use the `#' and `##' operators to stringify the variable argument ! or to paste its leading or trailing token with another token. (But see ! below for an important special case for `##'.) If your macro is complicated, you may want a more descriptive name ! for the variable argument than `__VA_ARGS__'. CPP permits this, as an ! extension. You may write an argument name immediately before the ! `...'; that name is used for the variable argument. The `eprintf' ! macro above could be written #define eprintf(args...) fprintf (stderr, args) ! using this extension. You cannot use `__VA_ARGS__' and this extension in the same macro. You can have named arguments as well as variable arguments in a ! variadic macro. We could define `eprintf' like this, instead: #define eprintf(format, ...) fprintf (stderr, format, __VA_ARGS__) *************** This formulation looks more descriptive, *** 1534,1541 **** flexible: you must now supply at least one argument after the format string. In standard C, you cannot omit the comma separating the named argument from the variable arguments. Furthermore, if you leave the ! variable argument empty, you will get a syntax error, because there will ! be an extra comma after the format string. eprintf("success!\n", ); ==> fprintf(stderr, "success!\n", ); --- 1540,1547 ---- flexible: you must now supply at least one argument after the format string. In standard C, you cannot omit the comma separating the named argument from the variable arguments. Furthermore, if you leave the ! variable argument empty, you will get a syntax error, because there ! will be an extra comma after the format string. eprintf("success!\n", ); ==> fprintf(stderr, "success!\n", ); *************** First, you are allowed to leave the vari *** 1546,1591 **** eprintf ("success!\n") ==> fprintf(stderr, "success!\n", ); ! Second, the '##' token paste operator has a special meaning when placed between a comma and a variable argument. If you write #define eprintf(format, ...) fprintf (stderr, format, ##__VA_ARGS__) ! and the variable argument is left out when the 'eprintf' macro is used, ! then the comma before the '##' will be deleted. This does _not_ happen ! if you pass an empty argument, nor does it happen if the token preceding ! '##' is anything other than a comma. eprintf ("success!\n") ==> fprintf(stderr, "success!\n"); The above explanation is ambiguous about the case where the only macro ! parameter is a variable arguments parameter, as it is meaningless to try ! to distinguish whether no argument at all is an empty argument or a ! missing argument. In this case the C99 standard is clear that the comma ! must remain, however the existing GCC extension used to swallow the ! comma. So CPP retains the comma when conforming to a specific C standard, and drops it otherwise. ! C99 mandates that the only place the identifier '__VA_ARGS__' can appear is in the replacement list of a variadic macro. It may not be ! used as a macro name, macro argument name, or within a different type of ! macro. It may also be forbidden in open text; the standard is ambiguous. We recommend you avoid using it except for its defined purpose. Variadic macros are a new feature in C99. GNU CPP has supported them ! for a long time, but only with a named variable argument ('args...', not ! '...' and '__VA_ARGS__'). If you are concerned with portability to previous versions of GCC, you should use only named variable arguments. On the other hand, if you are concerned with portability to other ! conforming implementations of C99, you should use only '__VA_ARGS__'. Previous versions of CPP implemented the comma-deletion extension much more generally. We have restricted it in this release to minimize the differences from C99. To get the same effect with both this and ! previous versions of GCC, the token preceding the special '##' must be a ! comma, and there must be white space between that comma and whatever comes immediately before it: #define eprintf(format, args...) fprintf (stderr, format , ##args) --- 1552,1597 ---- eprintf ("success!\n") ==> fprintf(stderr, "success!\n", ); ! Second, the `##' token paste operator has a special meaning when placed between a comma and a variable argument. If you write #define eprintf(format, ...) fprintf (stderr, format, ##__VA_ARGS__) ! and the variable argument is left out when the `eprintf' macro is used, ! then the comma before the `##' will be deleted. This does _not_ happen ! if you pass an empty argument, nor does it happen if the token ! preceding `##' is anything other than a comma. eprintf ("success!\n") ==> fprintf(stderr, "success!\n"); The above explanation is ambiguous about the case where the only macro ! parameter is a variable arguments parameter, as it is meaningless to ! try to distinguish whether no argument at all is an empty argument or a ! missing argument. In this case the C99 standard is clear that the ! comma must remain, however the existing GCC extension used to swallow ! the comma. So CPP retains the comma when conforming to a specific C standard, and drops it otherwise. ! C99 mandates that the only place the identifier `__VA_ARGS__' can appear is in the replacement list of a variadic macro. It may not be ! used as a macro name, macro argument name, or within a different type ! of macro. It may also be forbidden in open text; the standard is ambiguous. We recommend you avoid using it except for its defined purpose. Variadic macros are a new feature in C99. GNU CPP has supported them ! for a long time, but only with a named variable argument (`args...', ! not `...' and `__VA_ARGS__'). If you are concerned with portability to previous versions of GCC, you should use only named variable arguments. On the other hand, if you are concerned with portability to other ! conforming implementations of C99, you should use only `__VA_ARGS__'. Previous versions of CPP implemented the comma-deletion extension much more generally. We have restricted it in this release to minimize the differences from C99. To get the same effect with both this and ! previous versions of GCC, the token preceding the special `##' must be ! a comma, and there must be white space between that comma and whatever comes immediately before it: #define eprintf(format, args...) fprintf (stderr, format , ##args) *************** File: cpp.info, Node: Standard Predefin *** 1619,1643 **** -------------------------------- The standard predefined macros are specified by the relevant language ! standards, so they are available with all compilers that implement those ! standards. Older compilers may not provide all of them. Their names ! all start with double underscores. ! '__FILE__' This macro expands to the name of the current input file, in the form of a C string constant. This is the path by which the preprocessor opened the file, not the short name specified in ! '#include' or as the input file name argument. For example, ! '"/usr/local/include/myheader.h"' is a possible expansion of this macro. ! '__LINE__' ! This macro expands to the current input line number, in the form of ! a decimal integer constant. While we call it a predefined macro, ! it's a pretty strange macro, since its "definition" changes with ! each new line of source code. ! '__FILE__' and '__LINE__' are useful in generating an error message to report an inconsistency detected by the program; the message can state the source line at which the inconsistency was detected. For example, --- 1625,1649 ---- -------------------------------- The standard predefined macros are specified by the relevant language ! standards, so they are available with all compilers that implement ! those standards. Older compilers may not provide all of them. Their ! names all start with double underscores. ! `__FILE__' This macro expands to the name of the current input file, in the form of a C string constant. This is the path by which the preprocessor opened the file, not the short name specified in ! `#include' or as the input file name argument. For example, ! `"/usr/local/include/myheader.h"' is a possible expansion of this macro. ! `__LINE__' ! This macro expands to the current input line number, in the form ! of a decimal integer constant. While we call it a predefined ! macro, it's a pretty strange macro, since its "definition" changes ! with each new line of source code. ! `__FILE__' and `__LINE__' are useful in generating an error message to report an inconsistency detected by the program; the message can state the source line at which the inconsistency was detected. For example, *************** example, *** 1647,1748 **** "%d at %s, line %d.", length, __FILE__, __LINE__); ! An '#include' directive changes the expansions of '__FILE__' and ! '__LINE__' to correspond to the included file. At the end of that file, ! when processing resumes on the input file that contained the '#include' ! directive, the expansions of '__FILE__' and '__LINE__' revert to the ! values they had before the '#include' (but '__LINE__' is then ! incremented by one as processing moves to the line after the ! '#include'). ! A '#line' directive changes '__LINE__', and may change '__FILE__' as well. *Note Line Control::. ! C99 introduces '__func__', and GCC has provided '__FUNCTION__' for a ! long time. Both of these are strings containing the name of the current ! function (there are slight semantic differences; see the GCC manual). ! Neither of them is a macro; the preprocessor does not know the name of ! the current function. They tend to be useful in conjunction with ! '__FILE__' and '__LINE__', though. ! '__DATE__' This macro expands to a string constant that describes the date on which the preprocessor is being run. The string constant contains ! eleven characters and looks like '"Feb 12 1996"'. If the day of the month is less than 10, it is padded with a space on the left. If GCC cannot determine the current date, it will emit a warning ! message (once per compilation) and '__DATE__' will expand to ! '"??? ?? ????"'. ! '__TIME__' This macro expands to a string constant that describes the time at which the preprocessor is being run. The string constant contains ! eight characters and looks like '"23:59:01"'. If GCC cannot determine the current time, it will emit a warning ! message (once per compilation) and '__TIME__' will expand to ! '"??:??:??"'. ! '__STDC__' In normal operation, this macro expands to the constant 1, to signify that this compiler conforms to ISO Standard C. If GNU CPP is used with a compiler other than GCC, this is not necessarily true; however, the preprocessor always conforms to the standard ! unless the '-traditional-cpp' option is used. ! This macro is not defined if the '-traditional-cpp' option is used. On some hosts, the system compiler uses a different convention, ! where '__STDC__' is normally 0, but is 1 if the user specifies strict conformance to the C Standard. CPP follows the host ! convention when processing system header files, but when processing ! user files '__STDC__' is always 1. This has been reported to cause ! problems; for instance, some versions of Solaris provide X Windows ! headers that expect '__STDC__' to be either undefined or 1. *Note ! Invocation::. ! '__STDC_VERSION__' This macro expands to the C Standard's version number, a long ! integer constant of the form 'YYYYMML' where YYYY and MM are the year and month of the Standard version. This signifies which version of the C Standard the compiler conforms to. Like ! '__STDC__', this is not necessarily accurate for the entire implementation, unless GNU CPP is being used with GCC. ! The value '199409L' signifies the 1989 C standard as amended in ! 1994, which is the current default; the value '199901L' signifies ! the 1999 revision of the C standard. Support for the 1999 revision ! is not yet complete. ! This macro is not defined if the '-traditional-cpp' option is used, ! nor when compiling C++ or Objective-C. ! '__STDC_HOSTED__' This macro is defined, with value 1, if the compiler's target is a "hosted environment". A hosted environment has the complete facilities of the standard C library available. ! '__cplusplus' This macro is defined when the C++ compiler is in use. You can use ! '__cplusplus' to test whether a header is compiled by a C compiler ! or a C++ compiler. This macro is similar to '__STDC_VERSION__', in that it expands to a version number. Depending on the language ! standard selected, the value of the macro is '199711L' for the 1998 ! C++ standard, '201103L' for the 2011 C++ standard, '201402L' for ! the 2014 C++ standard, or an unspecified value strictly larger than ! '201402L' for the experimental languages enabled by '-std=c++1z' ! and '-std=gnu++1z'. ! '__OBJC__' This macro is defined, with value 1, when the Objective-C compiler ! is in use. You can use '__OBJC__' to test whether a header is compiled by a C compiler or an Objective-C compiler. ! '__ASSEMBLER__' This macro is defined with value 1 when preprocessing assembly language.  File: cpp.info, Node: Common Predefined Macros, Next: System-specific Predefined Macros, Prev: Standard Predefined Macros, Up: Predefined Macros --- 1653,1755 ---- "%d at %s, line %d.", length, __FILE__, __LINE__); ! An `#include' directive changes the expansions of `__FILE__' and ! `__LINE__' to correspond to the included file. At the end of that ! file, when processing resumes on the input file that contained the ! `#include' directive, the expansions of `__FILE__' and `__LINE__' ! revert to the values they had before the `#include' (but `__LINE__' is ! then incremented by one as processing moves to the line after the ! `#include'). ! A `#line' directive changes `__LINE__', and may change `__FILE__' as well. *Note Line Control::. ! C99 introduces `__func__', and GCC has provided `__FUNCTION__' for a ! long time. Both of these are strings containing the name of the ! current function (there are slight semantic differences; see the GCC ! manual). Neither of them is a macro; the preprocessor does not know the ! name of the current function. They tend to be useful in conjunction ! with `__FILE__' and `__LINE__', though. ! `__DATE__' This macro expands to a string constant that describes the date on which the preprocessor is being run. The string constant contains ! eleven characters and looks like `"Feb 12 1996"'. If the day of the month is less than 10, it is padded with a space on the left. If GCC cannot determine the current date, it will emit a warning ! message (once per compilation) and `__DATE__' will expand to ! `"??? ?? ????"'. ! `__TIME__' This macro expands to a string constant that describes the time at which the preprocessor is being run. The string constant contains ! eight characters and looks like `"23:59:01"'. If GCC cannot determine the current time, it will emit a warning ! message (once per compilation) and `__TIME__' will expand to ! `"??:??:??"'. ! `__STDC__' In normal operation, this macro expands to the constant 1, to signify that this compiler conforms to ISO Standard C. If GNU CPP is used with a compiler other than GCC, this is not necessarily true; however, the preprocessor always conforms to the standard ! unless the `-traditional-cpp' option is used. ! This macro is not defined if the `-traditional-cpp' option is used. On some hosts, the system compiler uses a different convention, ! where `__STDC__' is normally 0, but is 1 if the user specifies strict conformance to the C Standard. CPP follows the host ! convention when processing system header files, but when ! processing user files `__STDC__' is always 1. This has been ! reported to cause problems; for instance, some versions of Solaris ! provide X Windows headers that expect `__STDC__' to be either ! undefined or 1. *Note Invocation::. ! `__STDC_VERSION__' This macro expands to the C Standard's version number, a long ! integer constant of the form `YYYYMML' where YYYY and MM are the year and month of the Standard version. This signifies which version of the C Standard the compiler conforms to. Like ! `__STDC__', this is not necessarily accurate for the entire implementation, unless GNU CPP is being used with GCC. ! The value `199409L' signifies the 1989 C standard as amended in ! 1994, which is the current default; the value `199901L' signifies ! the 1999 revision of the C standard. Support for the 1999 ! revision is not yet complete. ! This macro is not defined if the `-traditional-cpp' option is ! used, nor when compiling C++ or Objective-C. ! `__STDC_HOSTED__' This macro is defined, with value 1, if the compiler's target is a "hosted environment". A hosted environment has the complete facilities of the standard C library available. ! `__cplusplus' This macro is defined when the C++ compiler is in use. You can use ! `__cplusplus' to test whether a header is compiled by a C compiler ! or a C++ compiler. This macro is similar to `__STDC_VERSION__', in that it expands to a version number. Depending on the language ! standard selected, the value of the macro is `199711L' for the ! 1998 C++ standard, `201103L' for the 2011 C++ standard, `201402L' ! for the 2014 C++ standard, or an unspecified value strictly larger ! than `201402L' for the experimental languages enabled by ! `-std=c++1z' and `-std=gnu++1z'. ! `__OBJC__' This macro is defined, with value 1, when the Objective-C compiler ! is in use. You can use `__OBJC__' to test whether a header is compiled by a C compiler or an Objective-C compiler. ! `__ASSEMBLER__' This macro is defined with value 1 when preprocessing assembly language. +  File: cpp.info, Node: Common Predefined Macros, Next: System-specific Predefined Macros, Prev: Standard Predefined Macros, Up: Predefined Macros *************** with the same meanings regardless of the *** 1754,1795 **** which you are using GNU C or GNU Fortran. Their names all start with double underscores. ! '__COUNTER__' This macro expands to sequential integral values starting from 0. ! In conjunction with the '##' operator, this provides a convenient ! means to generate unique identifiers. Care must be taken to ensure ! that '__COUNTER__' is not expanded prior to inclusion of precompiled headers which use it. Otherwise, the precompiled headers will not be used. ! '__GFORTRAN__' The GNU Fortran compiler defines this. ! '__GNUC__' ! '__GNUC_MINOR__' ! '__GNUC_PATCHLEVEL__' These macros are defined by all GNU compilers that use the C preprocessor: C, C++, Objective-C and Fortran. Their values are the major version, minor version, and patch level of the compiler, as integer constants. For example, GCC 3.2.1 will define ! '__GNUC__' to 3, '__GNUC_MINOR__' to 2, and '__GNUC_PATCHLEVEL__' ! to 1. These macros are also defined if you invoke the preprocessor ! directly. ! '__GNUC_PATCHLEVEL__' is new to GCC 3.0; it is also present in the widely-used development snapshots leading up to 3.0 (which identify themselves as GCC 2.96 or 2.97, depending on which snapshot you have). If all you need to know is whether or not your program is being compiled by GCC, or a non-GCC compiler that claims to accept the ! GNU C dialects, you can simply test '__GNUC__'. If you need to write code which depends on a specific version, you must be more ! careful. Each time the minor version is increased, the patch level ! is reset to zero; each time the major version is increased (which ! happens rarely), the minor version and patch level are reset. If ! you wish to use the predefined macros directly in the conditional, ! you will need to write it like this: /* Test for GCC > 3.2.0 */ #if __GNUC__ > 3 || \ --- 1761,1802 ---- which you are using GNU C or GNU Fortran. Their names all start with double underscores. ! `__COUNTER__' This macro expands to sequential integral values starting from 0. ! In conjunction with the `##' operator, this provides a convenient ! means to generate unique identifiers. Care must be taken to ! ensure that `__COUNTER__' is not expanded prior to inclusion of precompiled headers which use it. Otherwise, the precompiled headers will not be used. ! `__GFORTRAN__' The GNU Fortran compiler defines this. ! `__GNUC__' ! `__GNUC_MINOR__' ! `__GNUC_PATCHLEVEL__' These macros are defined by all GNU compilers that use the C preprocessor: C, C++, Objective-C and Fortran. Their values are the major version, minor version, and patch level of the compiler, as integer constants. For example, GCC 3.2.1 will define ! `__GNUC__' to 3, `__GNUC_MINOR__' to 2, and `__GNUC_PATCHLEVEL__' ! to 1. These macros are also defined if you invoke the ! preprocessor directly. ! `__GNUC_PATCHLEVEL__' is new to GCC 3.0; it is also present in the widely-used development snapshots leading up to 3.0 (which identify themselves as GCC 2.96 or 2.97, depending on which snapshot you have). If all you need to know is whether or not your program is being compiled by GCC, or a non-GCC compiler that claims to accept the ! GNU C dialects, you can simply test `__GNUC__'. If you need to write code which depends on a specific version, you must be more ! careful. Each time the minor version is increased, the patch ! level is reset to zero; each time the major version is increased ! (which happens rarely), the minor version and patch level are ! reset. If you wish to use the predefined macros directly in the ! conditional, you will need to write it like this: /* Test for GCC > 3.2.0 */ #if __GNUC__ > 3 || \ *************** double underscores. *** 1809,1856 **** Many people find this form easier to understand. ! '__GNUG__' The GNU C++ compiler defines this. Testing it is equivalent to ! testing '(__GNUC__ && __cplusplus)'. ! '__STRICT_ANSI__' ! GCC defines this macro if and only if the '-ansi' switch, or a ! '-std' switch specifying strict conformance to some version of ISO ! C or ISO C++, was specified when GCC was invoked. It is defined to ! '1'. This macro exists primarily to direct GNU libc's header files ! to restrict their definitions to the minimal set found in the 1989 ! C standard. ! '__BASE_FILE__' This macro expands to the name of the main input file, in the form of a C string constant. This is the source file that was specified on the command line of the preprocessor or C compiler. ! '__INCLUDE_LEVEL__' This macro expands to a decimal integer constant that represents the depth of nesting in include files. The value of this macro is ! incremented on every '#include' directive and decremented at the end of every included file. It starts out at 0, its value within the base file specified on the command line. ! '__ELF__' This macro is defined if the target uses the ELF object format. ! '__VERSION__' ! This macro expands to a string constant which describes the version ! of the compiler in use. You should not rely on its contents having ! any particular form, but it can be counted on to contain at least ! the release number. ! '__OPTIMIZE__' ! '__OPTIMIZE_SIZE__' ! '__NO_INLINE__' ! These macros describe the compilation mode. '__OPTIMIZE__' is ! defined in all optimizing compilations. '__OPTIMIZE_SIZE__' is defined if the compiler is optimizing for size, not speed. ! '__NO_INLINE__' is defined if no functions will be inlined into their callers (when not optimizing, or when inlining has been ! specifically disabled by '-fno-inline'). These macros cause certain GNU header files to provide optimized definitions, using macros or inline functions, of system library --- 1816,1863 ---- Many people find this form easier to understand. ! `__GNUG__' The GNU C++ compiler defines this. Testing it is equivalent to ! testing `(__GNUC__ && __cplusplus)'. ! `__STRICT_ANSI__' ! GCC defines this macro if and only if the `-ansi' switch, or a ! `-std' switch specifying strict conformance to some version of ISO ! C or ISO C++, was specified when GCC was invoked. It is defined ! to `1'. This macro exists primarily to direct GNU libc's header ! files to restrict their definitions to the minimal set found in ! the 1989 C standard. ! `__BASE_FILE__' This macro expands to the name of the main input file, in the form of a C string constant. This is the source file that was specified on the command line of the preprocessor or C compiler. ! `__INCLUDE_LEVEL__' This macro expands to a decimal integer constant that represents the depth of nesting in include files. The value of this macro is ! incremented on every `#include' directive and decremented at the end of every included file. It starts out at 0, its value within the base file specified on the command line. ! `__ELF__' This macro is defined if the target uses the ELF object format. ! `__VERSION__' ! This macro expands to a string constant which describes the ! version of the compiler in use. You should not rely on its ! contents having any particular form, but it can be counted on to ! contain at least the release number. ! `__OPTIMIZE__' ! `__OPTIMIZE_SIZE__' ! `__NO_INLINE__' ! These macros describe the compilation mode. `__OPTIMIZE__' is ! defined in all optimizing compilations. `__OPTIMIZE_SIZE__' is defined if the compiler is optimizing for size, not speed. ! `__NO_INLINE__' is defined if no functions will be inlined into their callers (when not optimizing, or when inlining has been ! specifically disabled by `-fno-inline'). These macros cause certain GNU header files to provide optimized definitions, using macros or inline functions, of system library *************** double underscores. *** 1858,2073 **** make sure that programs will execute with the same effect whether or not they are defined. If they are defined, their value is 1. ! '__GNUC_GNU_INLINE__' ! GCC defines this macro if functions declared 'inline' will be handled in GCC's traditional gnu90 mode. Object files will contain ! externally visible definitions of all functions declared 'inline' ! without 'extern' or 'static'. They will not contain any ! definitions of any functions declared 'extern inline'. ! '__GNUC_STDC_INLINE__' ! GCC defines this macro if functions declared 'inline' will be handled according to the ISO C99 standard. Object files will contain externally visible definitions of all functions declared ! 'extern inline'. They will not contain definitions of any ! functions declared 'inline' without 'extern'. ! If this macro is defined, GCC supports the 'gnu_inline' function attribute as a way to always get the gnu90 behavior. Support for ! this and '__GNUC_GNU_INLINE__' was added in GCC 4.1.3. If neither ! macro is defined, an older version of GCC is being used: 'inline' ! functions will be compiled in gnu90 mode, and the 'gnu_inline' function attribute will not be recognized. ! '__CHAR_UNSIGNED__' ! GCC defines this macro if and only if the data type 'char' is unsigned on the target machine. It exists to cause the standard ! header file 'limits.h' to work correctly. You should not use this macro yourself; instead, refer to the standard macros defined in ! 'limits.h'. ! '__WCHAR_UNSIGNED__' ! Like '__CHAR_UNSIGNED__', this macro is defined if and only if the ! data type 'wchar_t' is unsigned and the front-end is in C++ mode. ! '__REGISTER_PREFIX__' This macro expands to a single token (not a string constant) which is the prefix applied to CPU register names in assembly language for this target. You can use it to write assembly that is usable ! in multiple environments. For example, in the 'm68k-aout' ! environment it expands to nothing, but in the 'm68k-coff' ! environment it expands to a single '%'. ! '__USER_LABEL_PREFIX__' This macro expands to a single token which is the prefix applied to user labels (symbols visible to C code) in assembly. For example, ! in the 'm68k-aout' environment it expands to an '_', but in the ! 'm68k-coff' environment it expands to nothing. This macro will have the correct definition even if ! '-f(no-)underscores' is in use, but it will not be correct if target-specific options that adjust this prefix are used (e.g. the ! OSF/rose '-mno-underscores' option). ! '__SIZE_TYPE__' ! '__PTRDIFF_TYPE__' ! '__WCHAR_TYPE__' ! '__WINT_TYPE__' ! '__INTMAX_TYPE__' ! '__UINTMAX_TYPE__' ! '__SIG_ATOMIC_TYPE__' ! '__INT8_TYPE__' ! '__INT16_TYPE__' ! '__INT32_TYPE__' ! '__INT64_TYPE__' ! '__UINT8_TYPE__' ! '__UINT16_TYPE__' ! '__UINT32_TYPE__' ! '__UINT64_TYPE__' ! '__INT_LEAST8_TYPE__' ! '__INT_LEAST16_TYPE__' ! '__INT_LEAST32_TYPE__' ! '__INT_LEAST64_TYPE__' ! '__UINT_LEAST8_TYPE__' ! '__UINT_LEAST16_TYPE__' ! '__UINT_LEAST32_TYPE__' ! '__UINT_LEAST64_TYPE__' ! '__INT_FAST8_TYPE__' ! '__INT_FAST16_TYPE__' ! '__INT_FAST32_TYPE__' ! '__INT_FAST64_TYPE__' ! '__UINT_FAST8_TYPE__' ! '__UINT_FAST16_TYPE__' ! '__UINT_FAST32_TYPE__' ! '__UINT_FAST64_TYPE__' ! '__INTPTR_TYPE__' ! '__UINTPTR_TYPE__' These macros are defined to the correct underlying types for the ! 'size_t', 'ptrdiff_t', 'wchar_t', 'wint_t', 'intmax_t', ! 'uintmax_t', 'sig_atomic_t', 'int8_t', 'int16_t', 'int32_t', ! 'int64_t', 'uint8_t', 'uint16_t', 'uint32_t', 'uint64_t', ! 'int_least8_t', 'int_least16_t', 'int_least32_t', 'int_least64_t', ! 'uint_least8_t', 'uint_least16_t', 'uint_least32_t', ! 'uint_least64_t', 'int_fast8_t', 'int_fast16_t', 'int_fast32_t', ! 'int_fast64_t', 'uint_fast8_t', 'uint_fast16_t', 'uint_fast32_t', ! 'uint_fast64_t', 'intptr_t', and 'uintptr_t' typedefs, respectively. They exist to make the standard header files ! 'stddef.h', 'stdint.h', and 'wchar.h' work correctly. You should not use these macros directly; instead, include the appropriate headers and use the typedefs. Some of these macros may not be ! defined on particular systems if GCC does not provide a 'stdint.h' header on those systems. ! '__CHAR_BIT__' Defined to the number of bits used in the representation of the ! 'char' data type. It exists to make the standard header given numerical limits work correctly. You should not use this macro directly; instead, include the appropriate headers. ! '__SCHAR_MAX__' ! '__WCHAR_MAX__' ! '__SHRT_MAX__' ! '__INT_MAX__' ! '__LONG_MAX__' ! '__LONG_LONG_MAX__' ! '__WINT_MAX__' ! '__SIZE_MAX__' ! '__PTRDIFF_MAX__' ! '__INTMAX_MAX__' ! '__UINTMAX_MAX__' ! '__SIG_ATOMIC_MAX__' ! '__INT8_MAX__' ! '__INT16_MAX__' ! '__INT32_MAX__' ! '__INT64_MAX__' ! '__UINT8_MAX__' ! '__UINT16_MAX__' ! '__UINT32_MAX__' ! '__UINT64_MAX__' ! '__INT_LEAST8_MAX__' ! '__INT_LEAST16_MAX__' ! '__INT_LEAST32_MAX__' ! '__INT_LEAST64_MAX__' ! '__UINT_LEAST8_MAX__' ! '__UINT_LEAST16_MAX__' ! '__UINT_LEAST32_MAX__' ! '__UINT_LEAST64_MAX__' ! '__INT_FAST8_MAX__' ! '__INT_FAST16_MAX__' ! '__INT_FAST32_MAX__' ! '__INT_FAST64_MAX__' ! '__UINT_FAST8_MAX__' ! '__UINT_FAST16_MAX__' ! '__UINT_FAST32_MAX__' ! '__UINT_FAST64_MAX__' ! '__INTPTR_MAX__' ! '__UINTPTR_MAX__' ! '__WCHAR_MIN__' ! '__WINT_MIN__' ! '__SIG_ATOMIC_MIN__' ! Defined to the maximum value of the 'signed char', 'wchar_t', ! 'signed short', 'signed int', 'signed long', 'signed long long', ! 'wint_t', 'size_t', 'ptrdiff_t', 'intmax_t', 'uintmax_t', ! 'sig_atomic_t', 'int8_t', 'int16_t', 'int32_t', 'int64_t', ! 'uint8_t', 'uint16_t', 'uint32_t', 'uint64_t', 'int_least8_t', ! 'int_least16_t', 'int_least32_t', 'int_least64_t', 'uint_least8_t', ! 'uint_least16_t', 'uint_least32_t', 'uint_least64_t', ! 'int_fast8_t', 'int_fast16_t', 'int_fast32_t', 'int_fast64_t', ! 'uint_fast8_t', 'uint_fast16_t', 'uint_fast32_t', 'uint_fast64_t', ! 'intptr_t', and 'uintptr_t' types and to the minimum value of the ! 'wchar_t', 'wint_t', and 'sig_atomic_t' types respectively. They ! exist to make the standard header given numerical limits work ! correctly. You should not use these macros directly; instead, ! include the appropriate headers. Some of these macros may not be ! defined on particular systems if GCC does not provide a 'stdint.h' ! header on those systems. ! '__INT8_C' ! '__INT16_C' ! '__INT32_C' ! '__INT64_C' ! '__UINT8_C' ! '__UINT16_C' ! '__UINT32_C' ! '__UINT64_C' ! '__INTMAX_C' ! '__UINTMAX_C' ! Defined to implementations of the standard 'stdint.h' macros with ! the same names without the leading '__'. They exist the make the implementation of that header work correctly. You should not use these macros directly; instead, include the appropriate headers. Some of these macros may not be defined on particular systems if ! GCC does not provide a 'stdint.h' header on those systems. ! '__SIZEOF_INT__' ! '__SIZEOF_LONG__' ! '__SIZEOF_LONG_LONG__' ! '__SIZEOF_SHORT__' ! '__SIZEOF_POINTER__' ! '__SIZEOF_FLOAT__' ! '__SIZEOF_DOUBLE__' ! '__SIZEOF_LONG_DOUBLE__' ! '__SIZEOF_SIZE_T__' ! '__SIZEOF_WCHAR_T__' ! '__SIZEOF_WINT_T__' ! '__SIZEOF_PTRDIFF_T__' ! Defined to the number of bytes of the C standard data types: 'int', ! 'long', 'long long', 'short', 'void *', 'float', 'double', 'long ! double', 'size_t', 'wchar_t', 'wint_t' and 'ptrdiff_t'. ! '__BYTE_ORDER__' ! '__ORDER_LITTLE_ENDIAN__' ! '__ORDER_BIG_ENDIAN__' ! '__ORDER_PDP_ENDIAN__' ! '__BYTE_ORDER__' is defined to one of the values ! '__ORDER_LITTLE_ENDIAN__', '__ORDER_BIG_ENDIAN__', or ! '__ORDER_PDP_ENDIAN__' to reflect the layout of multi-byte and ! multi-word quantities in memory. If '__BYTE_ORDER__' is equal to ! '__ORDER_LITTLE_ENDIAN__' or '__ORDER_BIG_ENDIAN__', then multi-byte and multi-word quantities are laid out identically: the byte (word) at the lowest address is the least significant or most significant byte (word) of the quantity, respectively. If ! '__BYTE_ORDER__' is equal to '__ORDER_PDP_ENDIAN__', then bytes in 16-bit words are laid out in a little-endian fashion, whereas the 16-bit subwords of a 32-bit quantity are laid out in big-endian fashion. --- 1865,2080 ---- make sure that programs will execute with the same effect whether or not they are defined. If they are defined, their value is 1. ! `__GNUC_GNU_INLINE__' ! GCC defines this macro if functions declared `inline' will be handled in GCC's traditional gnu90 mode. Object files will contain ! externally visible definitions of all functions declared `inline' ! without `extern' or `static'. They will not contain any ! definitions of any functions declared `extern inline'. ! `__GNUC_STDC_INLINE__' ! GCC defines this macro if functions declared `inline' will be handled according to the ISO C99 standard. Object files will contain externally visible definitions of all functions declared ! `extern inline'. They will not contain definitions of any ! functions declared `inline' without `extern'. ! If this macro is defined, GCC supports the `gnu_inline' function attribute as a way to always get the gnu90 behavior. Support for ! this and `__GNUC_GNU_INLINE__' was added in GCC 4.1.3. If neither ! macro is defined, an older version of GCC is being used: `inline' ! functions will be compiled in gnu90 mode, and the `gnu_inline' function attribute will not be recognized. ! `__CHAR_UNSIGNED__' ! GCC defines this macro if and only if the data type `char' is unsigned on the target machine. It exists to cause the standard ! header file `limits.h' to work correctly. You should not use this macro yourself; instead, refer to the standard macros defined in ! `limits.h'. ! `__WCHAR_UNSIGNED__' ! Like `__CHAR_UNSIGNED__', this macro is defined if and only if the ! data type `wchar_t' is unsigned and the front-end is in C++ mode. ! `__REGISTER_PREFIX__' This macro expands to a single token (not a string constant) which is the prefix applied to CPU register names in assembly language for this target. You can use it to write assembly that is usable ! in multiple environments. For example, in the `m68k-aout' ! environment it expands to nothing, but in the `m68k-coff' ! environment it expands to a single `%'. ! `__USER_LABEL_PREFIX__' This macro expands to a single token which is the prefix applied to user labels (symbols visible to C code) in assembly. For example, ! in the `m68k-aout' environment it expands to an `_', but in the ! `m68k-coff' environment it expands to nothing. This macro will have the correct definition even if ! `-f(no-)underscores' is in use, but it will not be correct if target-specific options that adjust this prefix are used (e.g. the ! OSF/rose `-mno-underscores' option). ! `__SIZE_TYPE__' ! `__PTRDIFF_TYPE__' ! `__WCHAR_TYPE__' ! `__WINT_TYPE__' ! `__INTMAX_TYPE__' ! `__UINTMAX_TYPE__' ! `__SIG_ATOMIC_TYPE__' ! `__INT8_TYPE__' ! `__INT16_TYPE__' ! `__INT32_TYPE__' ! `__INT64_TYPE__' ! `__UINT8_TYPE__' ! `__UINT16_TYPE__' ! `__UINT32_TYPE__' ! `__UINT64_TYPE__' ! `__INT_LEAST8_TYPE__' ! `__INT_LEAST16_TYPE__' ! `__INT_LEAST32_TYPE__' ! `__INT_LEAST64_TYPE__' ! `__UINT_LEAST8_TYPE__' ! `__UINT_LEAST16_TYPE__' ! `__UINT_LEAST32_TYPE__' ! `__UINT_LEAST64_TYPE__' ! `__INT_FAST8_TYPE__' ! `__INT_FAST16_TYPE__' ! `__INT_FAST32_TYPE__' ! `__INT_FAST64_TYPE__' ! `__UINT_FAST8_TYPE__' ! `__UINT_FAST16_TYPE__' ! `__UINT_FAST32_TYPE__' ! `__UINT_FAST64_TYPE__' ! `__INTPTR_TYPE__' ! `__UINTPTR_TYPE__' These macros are defined to the correct underlying types for the ! `size_t', `ptrdiff_t', `wchar_t', `wint_t', `intmax_t', ! `uintmax_t', `sig_atomic_t', `int8_t', `int16_t', `int32_t', ! `int64_t', `uint8_t', `uint16_t', `uint32_t', `uint64_t', ! `int_least8_t', `int_least16_t', `int_least32_t', `int_least64_t', ! `uint_least8_t', `uint_least16_t', `uint_least32_t', ! `uint_least64_t', `int_fast8_t', `int_fast16_t', `int_fast32_t', ! `int_fast64_t', `uint_fast8_t', `uint_fast16_t', `uint_fast32_t', ! `uint_fast64_t', `intptr_t', and `uintptr_t' typedefs, respectively. They exist to make the standard header files ! `stddef.h', `stdint.h', and `wchar.h' work correctly. You should not use these macros directly; instead, include the appropriate headers and use the typedefs. Some of these macros may not be ! defined on particular systems if GCC does not provide a `stdint.h' header on those systems. ! `__CHAR_BIT__' Defined to the number of bits used in the representation of the ! `char' data type. It exists to make the standard header given numerical limits work correctly. You should not use this macro directly; instead, include the appropriate headers. ! `__SCHAR_MAX__' ! `__WCHAR_MAX__' ! `__SHRT_MAX__' ! `__INT_MAX__' ! `__LONG_MAX__' ! `__LONG_LONG_MAX__' ! `__WINT_MAX__' ! `__SIZE_MAX__' ! `__PTRDIFF_MAX__' ! `__INTMAX_MAX__' ! `__UINTMAX_MAX__' ! `__SIG_ATOMIC_MAX__' ! `__INT8_MAX__' ! `__INT16_MAX__' ! `__INT32_MAX__' ! `__INT64_MAX__' ! `__UINT8_MAX__' ! `__UINT16_MAX__' ! `__UINT32_MAX__' ! `__UINT64_MAX__' ! `__INT_LEAST8_MAX__' ! `__INT_LEAST16_MAX__' ! `__INT_LEAST32_MAX__' ! `__INT_LEAST64_MAX__' ! `__UINT_LEAST8_MAX__' ! `__UINT_LEAST16_MAX__' ! `__UINT_LEAST32_MAX__' ! `__UINT_LEAST64_MAX__' ! `__INT_FAST8_MAX__' ! `__INT_FAST16_MAX__' ! `__INT_FAST32_MAX__' ! `__INT_FAST64_MAX__' ! `__UINT_FAST8_MAX__' ! `__UINT_FAST16_MAX__' ! `__UINT_FAST32_MAX__' ! `__UINT_FAST64_MAX__' ! `__INTPTR_MAX__' ! `__UINTPTR_MAX__' ! `__WCHAR_MIN__' ! `__WINT_MIN__' ! `__SIG_ATOMIC_MIN__' ! Defined to the maximum value of the `signed char', `wchar_t', ! `signed short', `signed int', `signed long', `signed long long', ! `wint_t', `size_t', `ptrdiff_t', `intmax_t', `uintmax_t', ! `sig_atomic_t', `int8_t', `int16_t', `int32_t', `int64_t', ! `uint8_t', `uint16_t', `uint32_t', `uint64_t', `int_least8_t', ! `int_least16_t', `int_least32_t', `int_least64_t', ! `uint_least8_t', `uint_least16_t', `uint_least32_t', ! `uint_least64_t', `int_fast8_t', `int_fast16_t', `int_fast32_t', ! `int_fast64_t', `uint_fast8_t', `uint_fast16_t', `uint_fast32_t', ! `uint_fast64_t', `intptr_t', and `uintptr_t' types and to the ! minimum value of the `wchar_t', `wint_t', and `sig_atomic_t' types ! respectively. They exist to make the standard header given ! numerical limits work correctly. You should not use these macros ! directly; instead, include the appropriate headers. Some of these ! macros may not be defined on particular systems if GCC does not ! provide a `stdint.h' header on those systems. ! `__INT8_C' ! `__INT16_C' ! `__INT32_C' ! `__INT64_C' ! `__UINT8_C' ! `__UINT16_C' ! `__UINT32_C' ! `__UINT64_C' ! `__INTMAX_C' ! `__UINTMAX_C' ! Defined to implementations of the standard `stdint.h' macros with ! the same names without the leading `__'. They exist the make the implementation of that header work correctly. You should not use these macros directly; instead, include the appropriate headers. Some of these macros may not be defined on particular systems if ! GCC does not provide a `stdint.h' header on those systems. ! `__SIZEOF_INT__' ! `__SIZEOF_LONG__' ! `__SIZEOF_LONG_LONG__' ! `__SIZEOF_SHORT__' ! `__SIZEOF_POINTER__' ! `__SIZEOF_FLOAT__' ! `__SIZEOF_DOUBLE__' ! `__SIZEOF_LONG_DOUBLE__' ! `__SIZEOF_SIZE_T__' ! `__SIZEOF_WCHAR_T__' ! `__SIZEOF_WINT_T__' ! `__SIZEOF_PTRDIFF_T__' ! Defined to the number of bytes of the C standard data types: `int', ! `long', `long long', `short', `void *', `float', `double', `long ! double', `size_t', `wchar_t', `wint_t' and `ptrdiff_t'. ! `__BYTE_ORDER__' ! `__ORDER_LITTLE_ENDIAN__' ! `__ORDER_BIG_ENDIAN__' ! `__ORDER_PDP_ENDIAN__' ! `__BYTE_ORDER__' is defined to one of the values ! `__ORDER_LITTLE_ENDIAN__', `__ORDER_BIG_ENDIAN__', or ! `__ORDER_PDP_ENDIAN__' to reflect the layout of multi-byte and ! multi-word quantities in memory. If `__BYTE_ORDER__' is equal to ! `__ORDER_LITTLE_ENDIAN__' or `__ORDER_BIG_ENDIAN__', then multi-byte and multi-word quantities are laid out identically: the byte (word) at the lowest address is the least significant or most significant byte (word) of the quantity, respectively. If ! `__BYTE_ORDER__' is equal to `__ORDER_PDP_ENDIAN__', then bytes in 16-bit words are laid out in a little-endian fashion, whereas the 16-bit subwords of a 32-bit quantity are laid out in big-endian fashion. *************** double underscores. *** 2077,2227 **** /* Test for a little-endian machine */ #if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__ ! '__FLOAT_WORD_ORDER__' ! '__FLOAT_WORD_ORDER__' is defined to one of the values ! '__ORDER_LITTLE_ENDIAN__' or '__ORDER_BIG_ENDIAN__' to reflect the layout of the words of multi-word floating-point quantities. ! '__DEPRECATED' This macro is defined, with value 1, when compiling a C++ source file with warnings about deprecated constructs enabled. These warnings are enabled by default, but can be disabled with ! '-Wno-deprecated'. ! '__EXCEPTIONS' This macro is defined, with value 1, when compiling a C++ source ! file with exceptions enabled. If '-fno-exceptions' is used when compiling the file, then this macro is not defined. ! '__GXX_RTTI' This macro is defined, with value 1, when compiling a C++ source ! file with runtime type identification enabled. If '-fno-rtti' is used when compiling the file, then this macro is not defined. ! '__USING_SJLJ_EXCEPTIONS__' This macro is defined, with value 1, if the compiler uses the old ! mechanism based on 'setjmp' and 'longjmp' for exception handling. ! '__GXX_EXPERIMENTAL_CXX0X__' This macro is defined when compiling a C++ source file with the ! option '-std=c++0x' or '-std=gnu++0x'. It indicates that some ! features likely to be included in C++0x are available. Note that these features are experimental, and may change or be removed in future versions of GCC. ! '__GXX_WEAK__' This macro is defined when compiling a C++ source file. It has the value 1 if the compiler will use weak symbols, COMDAT sections, or other similar techniques to collapse symbols with "vague linkage" that are defined in multiple translation units. If the compiler ! will not collapse such symbols, this macro is defined with value 0. ! In general, user code should not need to make use of this macro; ! the purpose of this macro is to ease implementation of the C++ ! runtime library provided with G++. ! '__NEXT_RUNTIME__' This macro is defined, with value 1, if (and only if) the NeXT ! runtime (as in '-fnext-runtime') is in use for Objective-C. If the ! GNU runtime is used, this macro is not defined, so that you can use ! this macro to determine which runtime (NeXT or GNU) is being used. ! '__LP64__' ! '_LP64' These macros are defined, with value 1, if (and only if) the ! compilation is for a target where 'long int' and pointer both use ! 64-bits and 'int' uses 32-bit. ! '__SSP__' ! This macro is defined, with value 1, when '-fstack-protector' is in use. ! '__SSP_ALL__' ! This macro is defined, with value 2, when '-fstack-protector-all' is in use. ! '__SSP_STRONG__' This macro is defined, with value 3, when ! '-fstack-protector-strong' is in use. ! '__SSP_EXPLICIT__' This macro is defined, with value 4, when ! '-fstack-protector-explicit' is in use. ! '__SANITIZE_ADDRESS__' ! This macro is defined, with value 1, when '-fsanitize=address' or ! '-fsanitize=kernel-address' are in use. ! '__TIMESTAMP__' ! This macro expands to a string constant that describes the date and ! time of the last modification of the current source file. The ! string constant contains abbreviated day of the week, month, day of ! the month, time in hh:mm:ss form, year and looks like ! '"Sun Sep 16 01:03:52 1973"'. If the day of the month is less than ! 10, it is padded with a space on the left. If GCC cannot determine the current date, it will emit a warning ! message (once per compilation) and '__TIMESTAMP__' will expand to ! '"??? ??? ?? ??:??:?? ????"'. ! '__GCC_HAVE_SYNC_COMPARE_AND_SWAP_1' ! '__GCC_HAVE_SYNC_COMPARE_AND_SWAP_2' ! '__GCC_HAVE_SYNC_COMPARE_AND_SWAP_4' ! '__GCC_HAVE_SYNC_COMPARE_AND_SWAP_8' ! '__GCC_HAVE_SYNC_COMPARE_AND_SWAP_16' These macros are defined when the target processor supports atomic compare and swap operations on operands 1, 2, 4, 8 or 16 bytes in length, respectively. ! '__GCC_HAVE_DWARF2_CFI_ASM' This macro is defined when the compiler is emitting DWARF CFI directives to the assembler. When this is defined, it is possible to emit those same directives in inline assembly. ! '__FP_FAST_FMA' ! '__FP_FAST_FMAF' ! '__FP_FAST_FMAL' These macros are defined with value 1 if the backend supports the ! 'fma', 'fmaf', and 'fmal' builtin functions, so that the include ! file 'math.h' can define the macros 'FP_FAST_FMA', 'FP_FAST_FMAF', ! and 'FP_FAST_FMAL' for compatibility with the 1999 C standard. ! '__GCC_IEC_559' This macro is defined to indicate the intended level of support for IEEE 754 (IEC 60559) floating-point arithmetic. It expands to a ! nonnegative integer value. If 0, it indicates that the combination ! of the compiler configuration and the command-line options is not ! intended to support IEEE 754 arithmetic for 'float' and 'double' as ! defined in C99 and C11 Annex F (for example, that the standard ! rounding modes and exceptions are not supported, or that ! optimizations are enabled that conflict with IEEE 754 semantics). ! If 1, it indicates that IEEE 754 arithmetic is intended to be ! supported; this does not mean that all relevant language features ! are supported by GCC. If 2 or more, it additionally indicates ! support for IEEE 754-2008 (in particular, that the binary encodings ! for quiet and signaling NaNs are as specified in IEEE 754-2008). This macro does not indicate the default state of command-line options that control optimizations that C99 and C11 permit to be controlled by standard pragmas, where those standards do not require a particular default state. It does not indicate whether optimizations respect signaling NaN semantics (the macro for that ! is '__SUPPORT_SNAN__'). It does not indicate support for decimal floating point or the IEEE 754 binary16 and binary128 types. ! '__GCC_IEC_559_COMPLEX' This macro is defined to indicate the intended level of support for ! IEEE 754 (IEC 60559) floating-point arithmetic for complex numbers, ! as defined in C99 and C11 Annex G. It expands to a nonnegative ! integer value. If 0, it indicates that the combination of the ! compiler configuration and the command-line options is not intended ! to support Annex G requirements (for example, because ! '-fcx-limited-range' was used). If 1 or more, it indicates that it ! is intended to support those requirements; this does not mean that ! all relevant language features are supported by GCC. ! '__NO_MATH_ERRNO__' ! This macro is defined if '-fno-math-errno' is used, or enabled by ! another option such as '-ffast-math' or by default.  File: cpp.info, Node: System-specific Predefined Macros, Next: C++ Named Operators, Prev: Common Predefined Macros, Up: Predefined Macros --- 2084,2237 ---- /* Test for a little-endian machine */ #if __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__ ! `__FLOAT_WORD_ORDER__' ! `__FLOAT_WORD_ORDER__' is defined to one of the values ! `__ORDER_LITTLE_ENDIAN__' or `__ORDER_BIG_ENDIAN__' to reflect the layout of the words of multi-word floating-point quantities. ! `__DEPRECATED' This macro is defined, with value 1, when compiling a C++ source file with warnings about deprecated constructs enabled. These warnings are enabled by default, but can be disabled with ! `-Wno-deprecated'. ! `__EXCEPTIONS' This macro is defined, with value 1, when compiling a C++ source ! file with exceptions enabled. If `-fno-exceptions' is used when compiling the file, then this macro is not defined. ! `__GXX_RTTI' This macro is defined, with value 1, when compiling a C++ source ! file with runtime type identification enabled. If `-fno-rtti' is used when compiling the file, then this macro is not defined. ! `__USING_SJLJ_EXCEPTIONS__' This macro is defined, with value 1, if the compiler uses the old ! mechanism based on `setjmp' and `longjmp' for exception handling. ! `__GXX_EXPERIMENTAL_CXX0X__' This macro is defined when compiling a C++ source file with the ! option `-std=c++0x' or `-std=gnu++0x'. It indicates that some ! features likely to be included in C++0x are available. Note that these features are experimental, and may change or be removed in future versions of GCC. ! `__GXX_WEAK__' This macro is defined when compiling a C++ source file. It has the value 1 if the compiler will use weak symbols, COMDAT sections, or other similar techniques to collapse symbols with "vague linkage" that are defined in multiple translation units. If the compiler ! will not collapse such symbols, this macro is defined with value ! 0. In general, user code should not need to make use of this ! macro; the purpose of this macro is to ease implementation of the ! C++ runtime library provided with G++. ! `__NEXT_RUNTIME__' This macro is defined, with value 1, if (and only if) the NeXT ! runtime (as in `-fnext-runtime') is in use for Objective-C. If ! the GNU runtime is used, this macro is not defined, so that you ! can use this macro to determine which runtime (NeXT or GNU) is ! being used. ! `__LP64__' ! `_LP64' These macros are defined, with value 1, if (and only if) the ! compilation is for a target where `long int' and pointer both use ! 64-bits and `int' uses 32-bit. ! `__SSP__' ! This macro is defined, with value 1, when `-fstack-protector' is in use. ! `__SSP_ALL__' ! This macro is defined, with value 2, when `-fstack-protector-all' is in use. ! `__SSP_STRONG__' This macro is defined, with value 3, when ! `-fstack-protector-strong' is in use. ! `__SSP_EXPLICIT__' This macro is defined, with value 4, when ! `-fstack-protector-explicit' is in use. ! `__SANITIZE_ADDRESS__' ! This macro is defined, with value 1, when `-fsanitize=address' or ! `-fsanitize=kernel-address' are in use. ! `__TIMESTAMP__' ! This macro expands to a string constant that describes the date ! and time of the last modification of the current source file. The ! string constant contains abbreviated day of the week, month, day ! of the month, time in hh:mm:ss form, year and looks like ! `"Sun Sep 16 01:03:52 1973"'. If the day of the month is less ! than 10, it is padded with a space on the left. If GCC cannot determine the current date, it will emit a warning ! message (once per compilation) and `__TIMESTAMP__' will expand to ! `"??? ??? ?? ??:??:?? ????"'. ! `__GCC_HAVE_SYNC_COMPARE_AND_SWAP_1' ! `__GCC_HAVE_SYNC_COMPARE_AND_SWAP_2' ! `__GCC_HAVE_SYNC_COMPARE_AND_SWAP_4' ! `__GCC_HAVE_SYNC_COMPARE_AND_SWAP_8' ! `__GCC_HAVE_SYNC_COMPARE_AND_SWAP_16' These macros are defined when the target processor supports atomic compare and swap operations on operands 1, 2, 4, 8 or 16 bytes in length, respectively. ! `__GCC_HAVE_DWARF2_CFI_ASM' This macro is defined when the compiler is emitting DWARF CFI directives to the assembler. When this is defined, it is possible to emit those same directives in inline assembly. ! `__FP_FAST_FMA' ! `__FP_FAST_FMAF' ! `__FP_FAST_FMAL' These macros are defined with value 1 if the backend supports the ! `fma', `fmaf', and `fmal' builtin functions, so that the include ! file `math.h' can define the macros `FP_FAST_FMA', `FP_FAST_FMAF', ! and `FP_FAST_FMAL' for compatibility with the 1999 C standard. ! `__GCC_IEC_559' This macro is defined to indicate the intended level of support for IEEE 754 (IEC 60559) floating-point arithmetic. It expands to a ! nonnegative integer value. If 0, it indicates that the ! combination of the compiler configuration and the command-line ! options is not intended to support IEEE 754 arithmetic for `float' ! and `double' as defined in C99 and C11 Annex F (for example, that ! the standard rounding modes and exceptions are not supported, or ! that optimizations are enabled that conflict with IEEE 754 ! semantics). If 1, it indicates that IEEE 754 arithmetic is ! intended to be supported; this does not mean that all relevant ! language features are supported by GCC. If 2 or more, it ! additionally indicates support for IEEE 754-2008 (in particular, ! that the binary encodings for quiet and signaling NaNs are as ! specified in IEEE 754-2008). This macro does not indicate the default state of command-line options that control optimizations that C99 and C11 permit to be controlled by standard pragmas, where those standards do not require a particular default state. It does not indicate whether optimizations respect signaling NaN semantics (the macro for that ! is `__SUPPORT_SNAN__'). It does not indicate support for decimal floating point or the IEEE 754 binary16 and binary128 types. ! `__GCC_IEC_559_COMPLEX' This macro is defined to indicate the intended level of support for ! IEEE 754 (IEC 60559) floating-point arithmetic for complex ! numbers, as defined in C99 and C11 Annex G. It expands to a ! nonnegative integer value. If 0, it indicates that the ! combination of the compiler configuration and the command-line ! options is not intended to support Annex G requirements (for ! example, because `-fcx-limited-range' was used). If 1 or more, it ! indicates that it is intended to support those requirements; this ! does not mean that all relevant language features are supported by ! GCC. ! `__NO_MATH_ERRNO__' ! This macro is defined if `-fno-math-errno' is used, or enabled by ! another option such as `-ffast-math' or by default.  File: cpp.info, Node: System-specific Predefined Macros, Next: C++ Named Operators, Prev: Common Predefined Macros, Up: Predefined Macros *************** File: cpp.info, Node: System-specific P *** 2232,2254 **** The C preprocessor normally predefines several macros that indicate what type of system and machine is in use. They are obviously different on each target supported by GCC. This manual, being for all systems and ! machines, cannot tell you what their names are, but you can use 'cpp -dM' to see them all. *Note Invocation::. All system-specific predefined macros expand to a constant value, so you can test them with ! either '#ifdef' or '#if'. The C standard requires that all system-specific macros be part of the "reserved namespace". All names which begin with two underscores, or an underscore and a capital letter, are reserved for the compiler and library to use as they wish. However, historically system-specific macros have had names with no special prefix; for instance, it is common ! to find 'unix' defined on Unix systems. For all such macros, GCC provides a parallel macro with two underscores added at the beginning ! and the end. If 'unix' is defined, '__unix__' will be defined too. ! There will never be more than two underscores; the parallel of '_mips' ! is '__mips__'. ! When the '-ansi' option, or any '-std' option that requests strict conformance, is given to the compiler, all the system-specific predefined macros outside the reserved namespace are suppressed. The parallel macros, inside the reserved namespace, remain defined. --- 2242,2264 ---- The C preprocessor normally predefines several macros that indicate what type of system and machine is in use. They are obviously different on each target supported by GCC. This manual, being for all systems and ! machines, cannot tell you what their names are, but you can use `cpp -dM' to see them all. *Note Invocation::. All system-specific predefined macros expand to a constant value, so you can test them with ! either `#ifdef' or `#if'. The C standard requires that all system-specific macros be part of the "reserved namespace". All names which begin with two underscores, or an underscore and a capital letter, are reserved for the compiler and library to use as they wish. However, historically system-specific macros have had names with no special prefix; for instance, it is common ! to find `unix' defined on Unix systems. For all such macros, GCC provides a parallel macro with two underscores added at the beginning ! and the end. If `unix' is defined, `__unix__' will be defined too. ! There will never be more than two underscores; the parallel of `_mips' ! is `__mips__'. ! When the `-ansi' option, or any `-std' option that requests strict conformance, is given to the compiler, all the system-specific predefined macros outside the reserved namespace are suppressed. The parallel macros, inside the reserved namespace, remain defined. *************** encourage you to correct older code to u *** 2259,2265 **** you find it. We don't recommend you use the system-specific macros that are in the reserved namespace, either. It is better in the long run to check specifically for features you need, using a tool such as ! 'autoconf'.  File: cpp.info, Node: C++ Named Operators, Prev: System-specific Predefined Macros, Up: Predefined Macros --- 2269,2275 ---- you find it. We don't recommend you use the system-specific macros that are in the reserved namespace, either. It is better in the long run to check specifically for features you need, using a tool such as ! `autoconf'.  File: cpp.info, Node: C++ Named Operators, Prev: System-specific Predefined Macros, Up: Predefined Macros *************** File: cpp.info, Node: C++ Named Operato *** 2270,2294 **** In C++, there are eleven keywords which are simply alternate spellings of operators normally written with punctuation. These keywords are treated as such even in the preprocessor. They function as operators in ! '#if', and they cannot be defined as macros or poisoned. In C, you can request that those keywords take their C++ meaning by including ! 'iso646.h'. That header defines each one as a normal object-like macro expanding to the appropriate punctuator. These are the named operators and their corresponding punctuators: Named Operator Punctuator ! 'and' '&&' ! 'and_eq' '&=' ! 'bitand' '&' ! 'bitor' '|' ! 'compl' '~' ! 'not' '!' ! 'not_eq' '!=' ! 'or' '||' ! 'or_eq' '|=' ! 'xor' '^' ! 'xor_eq' '^='  File: cpp.info, Node: Undefining and Redefining Macros, Next: Directives Within Macro Arguments, Prev: Predefined Macros, Up: Macros --- 2280,2304 ---- In C++, there are eleven keywords which are simply alternate spellings of operators normally written with punctuation. These keywords are treated as such even in the preprocessor. They function as operators in ! `#if', and they cannot be defined as macros or poisoned. In C, you can request that those keywords take their C++ meaning by including ! `iso646.h'. That header defines each one as a normal object-like macro expanding to the appropriate punctuator. These are the named operators and their corresponding punctuators: Named Operator Punctuator ! `and' `&&' ! `and_eq' `&=' ! `bitand' `&' ! `bitor' `|' ! `compl' `~' ! `not' `!' ! `not_eq' `!=' ! `or' `||' ! `or_eq' `|=' ! `xor' `^' ! `xor_eq' `^='  File: cpp.info, Node: Undefining and Redefining Macros, Next: Directives Within Macro Arguments, Prev: Predefined Macros, Up: Macros *************** File: cpp.info, Node: Undefining and Re *** 2296,2306 **** 3.8 Undefining and Redefining Macros ==================================== ! If a macro ceases to be useful, it may be "undefined" with the '#undef' ! directive. '#undef' takes a single argument, the name of the macro to undefine. You use the bare macro name, even if the macro is ! function-like. It is an error if anything appears on the line after the ! macro name. '#undef' has no effect if the name is not a macro. #define FOO 4 x = FOO; ==> x = 4; --- 2306,2316 ---- 3.8 Undefining and Redefining Macros ==================================== ! If a macro ceases to be useful, it may be "undefined" with the `#undef' ! directive. `#undef' takes a single argument, the name of the macro to undefine. You use the bare macro name, even if the macro is ! function-like. It is an error if anything appears on the line after ! the macro name. `#undef' has no effect if the name is not a macro. #define FOO 4 x = FOO; ==> x = 4; *************** macro name. '#undef' has no effect if t *** 2308,2322 **** x = FOO; ==> x = FOO; Once a macro has been undefined, that identifier may be "redefined" ! as a macro by a subsequent '#define' directive. The new definition need ! not have any resemblance to the old definition. However, if an identifier which is currently a macro is redefined, then the new definition must be "effectively the same" as the old one. Two macro definitions are effectively the same if: * Both are the same type of macro (object- or function-like). * All the tokens of the replacement list are the same. * If there are any parameters, they are the same. * Whitespace appears in the same places in both. It need not be exactly the same amount of whitespace, though. Remember that comments count as whitespace. --- 2318,2335 ---- x = FOO; ==> x = FOO; Once a macro has been undefined, that identifier may be "redefined" ! as a macro by a subsequent `#define' directive. The new definition ! need not have any resemblance to the old definition. However, if an identifier which is currently a macro is redefined, then the new definition must be "effectively the same" as the old one. Two macro definitions are effectively the same if: * Both are the same type of macro (object- or function-like). + * All the tokens of the replacement list are the same. + * If there are any parameters, they are the same. + * Whitespace appears in the same places in both. It need not be exactly the same amount of whitespace, though. Remember that comments count as whitespace. *************** These definitions are effectively the sa *** 2325,2331 **** #define FOUR (2 + 2) #define FOUR (2 + 2) #define FOUR (2 /* two */ + 2) ! but these are not: #define FOUR (2 + 2) #define FOUR ( 2+2 ) #define FOUR (2 * 2) --- 2338,2344 ---- #define FOUR (2 + 2) #define FOUR (2 + 2) #define FOUR (2 /* two */ + 2) ! but these are not: #define FOUR (2 + 2) #define FOUR ( 2+2 ) #define FOUR (2 * 2) *************** these cases is undefined. *** 2351,2361 **** Versions of CPP prior to 3.2 would reject such constructs with an error message. This was the only syntactic difference between normal functions and function-like macros, so it seemed attractive to remove ! this limitation, and people would often be surprised that they could not ! use macros in this way. Moreover, sometimes people would use conditional compilation in the argument list to a normal library ! function like 'printf', only to find that after a library upgrade ! 'printf' had changed to be a function-like macro, and their code would no longer compile. So from version 3.2 we changed CPP to successfully process arbitrary directives within macro arguments in exactly the same way as it would have processed the directive were the function-like --- 2364,2374 ---- Versions of CPP prior to 3.2 would reject such constructs with an error message. This was the only syntactic difference between normal functions and function-like macros, so it seemed attractive to remove ! this limitation, and people would often be surprised that they could ! not use macros in this way. Moreover, sometimes people would use conditional compilation in the argument list to a normal library ! function like `printf', only to find that after a library upgrade ! `printf' had changed to be a function-like macro, and their code would no longer compile. So from version 3.2 we changed CPP to successfully process arbitrary directives within macro arguments in exactly the same way as it would have processed the directive were the function-like *************** outside of it. For example, *** 2426,2434 **** strange(stderr) p, 35) ==> fprintf (stderr, "%s %d", p, 35) ! The ability to piece together a macro call can be useful, but the use ! of unbalanced open parentheses in a macro body is just confusing, and ! should be avoided.  File: cpp.info, Node: Operator Precedence Problems, Next: Swallowing the Semicolon, Prev: Misnesting, Up: Macro Pitfalls --- 2439,2447 ---- strange(stderr) p, 35) ==> fprintf (stderr, "%s %d", p, 35) ! The ability to piece together a macro call can be useful, but the ! use of unbalanced open parentheses in a macro body is just confusing, ! and should be avoided.  File: cpp.info, Node: Operator Precedence Problems, Next: Swallowing the Semicolon, Prev: Misnesting, Up: Macro Pitfalls *************** way. *** 2447,2454 **** #define ceil_div(x, y) (x + y - 1) / y whose purpose is to divide, rounding up. (One use for this operation is ! to compute how many 'int' objects are needed to hold a certain number of ! 'char' objects.) Then suppose it is used as follows: a = ceil_div (b & c, sizeof (int)); ==> a = (b & c + sizeof (int) - 1) / sizeof (int); --- 2460,2467 ---- #define ceil_div(x, y) (x + y - 1) / y whose purpose is to divide, rounding up. (One use for this operation is ! to compute how many `int' objects are needed to hold a certain number ! of `char' objects.) Then suppose it is used as follows: a = ceil_div (b & c, sizeof (int)); ==> a = (b & c + sizeof (int) - 1) / sizeof (int); *************** Defining the macro as *** 2468,2486 **** provides the desired result. ! Unintended grouping can result in another way. Consider 'sizeof ceil_div(1, 2)'. That has the appearance of a C expression that would ! compute the size of the type of 'ceil_div (1, 2)', but in fact it means something very different. Here is what it expands to: sizeof ((1) + (2) - 1) / (2) This would take the size of an integer and divide it by two. The ! precedence rules have put the division outside the 'sizeof' when it was intended to be inside. Parentheses around the entire macro definition prevent such problems. ! Here, then, is the recommended way to define 'ceil_div': #define ceil_div(x, y) (((x) + (y) - 1) / (y)) --- 2481,2499 ---- provides the desired result. ! Unintended grouping can result in another way. Consider `sizeof ceil_div(1, 2)'. That has the appearance of a C expression that would ! compute the size of the type of `ceil_div (1, 2)', but in fact it means something very different. Here is what it expands to: sizeof ((1) + (2) - 1) / (2) This would take the size of an integer and divide it by two. The ! precedence rules have put the division outside the `sizeof' when it was intended to be inside. Parentheses around the entire macro definition prevent such problems. ! Here, then, is the recommended way to define `ceil_div': #define ceil_div(x, y) (((x) + (y) - 1) / (y)) *************** File: cpp.info, Node: Swallowing the Se *** 2492,2498 **** Often it is desirable to define a macro that expands into a compound statement. Consider, for example, the following macro, that advances a ! pointer (the argument 'p' says where to find it) across whitespace characters: #define SKIP_SPACES(p, limit) \ --- 2505,2511 ---- Often it is desirable to define a macro that expands into a compound statement. Consider, for example, the following macro, that advances a ! pointer (the argument `p' says where to find it) across whitespace characters: #define SKIP_SPACES(p, limit) \ *************** Here backslash-newline is used to split *** 2505,2518 **** be a single logical line, so that it resembles the way such code would be laid out if not part of a macro definition. ! A call to this macro might be 'SKIP_SPACES (p, lim)'. Strictly speaking, the call expands to a compound statement, which is a complete statement with no need for a semicolon to end it. However, since it looks like a function call, it minimizes confusion if you can use it ! like a function call, writing a semicolon afterward, as in 'SKIP_SPACES (p, lim);' ! This can cause trouble before 'else' statements, because the semicolon is actually a null statement. Suppose you write if (*p != 0) --- 2518,2531 ---- be a single logical line, so that it resembles the way such code would be laid out if not part of a macro definition. ! A call to this macro might be `SKIP_SPACES (p, lim)'. Strictly speaking, the call expands to a compound statement, which is a complete statement with no need for a semicolon to end it. However, since it looks like a function call, it minimizes confusion if you can use it ! like a function call, writing a semicolon afterward, as in `SKIP_SPACES (p, lim);' ! This can cause trouble before `else' statements, because the semicolon is actually a null statement. Suppose you write if (*p != 0) *************** semicolon is actually a null statement. *** 2520,2530 **** else ... The presence of two statements--the compound statement and a null ! statement--in between the 'if' condition and the 'else' makes invalid C code. ! The definition of the macro 'SKIP_SPACES' can be altered to solve ! this problem, using a 'do ... while' statement. Here is how: #define SKIP_SPACES(p, limit) \ do { char *lim = (limit); \ --- 2533,2543 ---- else ... The presence of two statements--the compound statement and a null ! statement--in between the `if' condition and the `else' makes invalid C code. ! The definition of the macro `SKIP_SPACES' can be altered to solve ! this problem, using a `do ... while' statement. Here is how: #define SKIP_SPACES(p, limit) \ do { char *lim = (limit); \ *************** this problem, using a 'do ... while' sta *** 2533,2539 **** p--; break; }}} \ while (0) ! Now 'SKIP_SPACES (p, lim);' expands into do {...} while (0); --- 2546,2552 ---- p--; break; }}} \ while (0) ! Now `SKIP_SPACES (p, lim);' expands into do {...} while (0); *************** File: cpp.info, Node: Duplication of Si *** 2546,2557 **** 3.10.4 Duplication of Side Effects ---------------------------------- ! Many C programs define a macro 'min', for "minimum", like this: #define min(X, Y) ((X) < (Y) ? (X) : (Y)) ! When you use this macro with an argument containing a side effect, as ! shown here, next = min (x + y, foo (z)); --- 2559,2570 ---- 3.10.4 Duplication of Side Effects ---------------------------------- ! Many C programs define a macro `min', for "minimum", like this: #define min(X, Y) ((X) < (Y) ? (X) : (Y)) ! When you use this macro with an argument containing a side effect, ! as shown here, next = min (x + y, foo (z)); *************** it expands as follows: *** 2559,2575 **** next = ((x + y) < (foo (z)) ? (x + y) : (foo (z))); ! where 'x + y' has been substituted for 'X' and 'foo (z)' for 'Y'. ! The function 'foo' is used only once in the statement as it appears ! in the program, but the expression 'foo (z)' has been substituted twice ! into the macro expansion. As a result, 'foo' might be called two times ! when the statement is executed. If it has side effects or if it takes a ! long time to compute, the results might not be what you intended. We ! say that 'min' is an "unsafe" macro. ! The best solution to this problem is to define 'min' in a way that ! computes the value of 'foo (z)' only once. The C language offers no standard way to do this, but it can be done with GNU extensions as follows: --- 2572,2588 ---- next = ((x + y) < (foo (z)) ? (x + y) : (foo (z))); ! where `x + y' has been substituted for `X' and `foo (z)' for `Y'. ! The function `foo' is used only once in the statement as it appears ! in the program, but the expression `foo (z)' has been substituted twice ! into the macro expansion. As a result, `foo' might be called two times ! when the statement is executed. If it has side effects or if it takes ! a long time to compute, the results might not be what you intended. We ! say that `min' is an "unsafe" macro. ! The best solution to this problem is to define `min' in a way that ! computes the value of `foo (z)' only once. The C language offers no standard way to do this, but it can be done with GNU extensions as follows: *************** follows: *** 2578,2584 **** typeof (Y) y_ = (Y); \ (x_ < y_) ? x_ : y_; }) ! The '({ ... })' notation produces a compound statement that acts as an expression. Its value is the value of its last statement. This permits us to define local variables and assign each argument to one. The local variables have underscores after their names to reduce the --- 2591,2597 ---- typeof (Y) y_ = (Y); \ (x_ < y_) ? x_ : y_; }) ! The `({ ... })' notation produces a compound statement that acts as an expression. Its value is the value of its last statement. This permits us to define local variables and assign each argument to one. The local variables have underscores after their names to reduce the *************** risk of conflict with an identifier of w *** 2586,2594 **** avoid this entirely). Now each argument is evaluated exactly once. If you do not wish to use GNU C extensions, the only solution is to ! be careful when _using_ the macro 'min'. For example, you can calculate ! the value of 'foo (z)', save it in a variable, and use that variable in ! 'min': #define min(X, Y) ((X) < (Y) ? (X) : (Y)) ... --- 2599,2607 ---- avoid this entirely). Now each argument is evaluated exactly once. If you do not wish to use GNU C extensions, the only solution is to ! be careful when _using_ the macro `min'. For example, you can ! calculate the value of `foo (z)', save it in a variable, and use that ! variable in `min': #define min(X, Y) ((X) < (Y) ? (X) : (Y)) ... *************** the value of 'foo (z)', save it in a var *** 2597,2603 **** next = min (x + y, tem); } ! (where we assume that 'foo' returns type 'int').  File: cpp.info, Node: Self-Referential Macros, Next: Argument Prescan, Prev: Duplication of Side Effects, Up: Macro Pitfalls --- 2610,2616 ---- next = min (x + y, tem); } ! (where we assume that `foo' returns type `int').  File: cpp.info, Node: Self-Referential Macros, Next: Argument Prescan, Prev: Duplication of Side Effects, Up: Macro Pitfalls *************** preprocessor output unchanged. Consider *** 2614,2655 **** #define foo (4 + foo) ! where 'foo' is also a variable in your program. ! Following the ordinary rules, each reference to 'foo' will expand ! into '(4 + foo)'; then this will be rescanned and will expand into '(4 + ! (4 + foo))'; and so on until the computer runs out of memory. The self-reference rule cuts this process short after one step, at ! '(4 + foo)'. Therefore, this macro definition has the possibly useful ! effect of causing the program to add 4 to the value of 'foo' wherever ! 'foo' is referred to. In most cases, it is a bad idea to take advantage of this feature. A ! person reading the program who sees that 'foo' is a variable will not expect that it is a macro as well. The reader will come across the ! identifier 'foo' in the program and think its value should be that of ! the variable 'foo', whereas in fact the value is four greater. One common, useful use of self-reference is to create a macro which expands to itself. If you write #define EPERM EPERM ! then the macro 'EPERM' expands to 'EPERM'. Effectively, it is left alone by the preprocessor whenever it's used in running text. You can ! tell that it's a macro with '#ifdef'. You might do this if you want to ! define numeric constants with an 'enum', but have '#ifdef' be true for each constant. ! If a macro 'x' expands to use a macro 'y', and the expansion of 'y' ! refers to the macro 'x', that is an "indirect self-reference" of 'x'. ! 'x' is not expanded in this case either. Thus, if we have #define x (4 + y) #define y (2 * x) ! then 'x' and 'y' expand as follows: x ==> (4 + y) ==> (4 + (2 * x)) --- 2627,2668 ---- #define foo (4 + foo) ! where `foo' is also a variable in your program. ! Following the ordinary rules, each reference to `foo' will expand ! into `(4 + foo)'; then this will be rescanned and will expand into `(4 ! + (4 + foo))'; and so on until the computer runs out of memory. The self-reference rule cuts this process short after one step, at ! `(4 + foo)'. Therefore, this macro definition has the possibly useful ! effect of causing the program to add 4 to the value of `foo' wherever ! `foo' is referred to. In most cases, it is a bad idea to take advantage of this feature. A ! person reading the program who sees that `foo' is a variable will not expect that it is a macro as well. The reader will come across the ! identifier `foo' in the program and think its value should be that of ! the variable `foo', whereas in fact the value is four greater. One common, useful use of self-reference is to create a macro which expands to itself. If you write #define EPERM EPERM ! then the macro `EPERM' expands to `EPERM'. Effectively, it is left alone by the preprocessor whenever it's used in running text. You can ! tell that it's a macro with `#ifdef'. You might do this if you want to ! define numeric constants with an `enum', but have `#ifdef' be true for each constant. ! If a macro `x' expands to use a macro `y', and the expansion of `y' ! refers to the macro `x', that is an "indirect self-reference" of `x'. ! `x' is not expanded in this case either. Thus, if we have #define x (4 + y) #define y (2 * x) ! then `x' and `y' expand as follows: x ==> (4 + y) ==> (4 + (2 * x)) *************** same results. *** 2682,2709 **** You might expect the double scan to change the results when a self-referential macro is used in an argument of another macro (*note ! Self-Referential Macros::): the self-referential macro would be expanded ! once in the first scan, and a second time in the second scan. However, ! this is not what happens. The self-references that do not expand in the ! first scan are marked so that they will not expand in the second scan ! either. You might wonder, "Why mention the prescan, if it makes no ! difference? And why not skip it and make the preprocessor faster?" The ! answer is that the prescan does make a difference in three special cases: * Nested calls to a macro. We say that "nested" calls to a macro occur when a macro's argument ! contains a call to that very macro. For example, if 'f' is a macro ! that expects one argument, 'f (f (1))' is a nested pair of calls to ! 'f'. The desired expansion is made by expanding 'f (1)' and ! substituting that into the definition of 'f'. The prescan causes ! the expected result to happen. Without the prescan, 'f (1)' itself ! would be substituted as an argument, and the inner use of 'f' would ! appear during the main scan as an indirect self-reference and would ! not be expanded. * Macros that call other macros that stringify or concatenate. --- 2695,2722 ---- You might expect the double scan to change the results when a self-referential macro is used in an argument of another macro (*note ! Self-Referential Macros::): the self-referential macro would be ! expanded once in the first scan, and a second time in the second scan. ! However, this is not what happens. The self-references that do not ! expand in the first scan are marked so that they will not expand in the ! second scan either. You might wonder, "Why mention the prescan, if it makes no ! difference? And why not skip it and make the preprocessor faster?" ! The answer is that the prescan does make a difference in three special cases: * Nested calls to a macro. We say that "nested" calls to a macro occur when a macro's argument ! contains a call to that very macro. For example, if `f' is a macro ! that expects one argument, `f (f (1))' is a nested pair of calls to ! `f'. The desired expansion is made by expanding `f (1)' and ! substituting that into the definition of `f'. The prescan causes ! the expected result to happen. Without the prescan, `f (1)' itself ! would be substituted as an argument, and the inner use of `f' would ! appear during the main scan as an indirect self-reference and ! would not be expanded. * Macros that call other macros that stringify or concatenate. *************** cases: *** 2718,2725 **** #define TABLESIZE 1024 #define BUFSIZE TABLESIZE ! then 'AFTERX(BUFSIZE)' expands to 'X_BUFSIZE', and ! 'XAFTERX(BUFSIZE)' expands to 'X_1024'. (Not to 'X_TABLESIZE'. Prescan always does a complete expansion.) * Macros used in arguments, whose expansions contain unshielded --- 2731,2738 ---- #define TABLESIZE 1024 #define BUFSIZE TABLESIZE ! then `AFTERX(BUFSIZE)' expands to `X_BUFSIZE', and ! `XAFTERX(BUFSIZE)' expands to `X_1024'. (Not to `X_TABLESIZE'. Prescan always does a complete expansion.) * Macros used in arguments, whose expansions contain unshielded *************** cases: *** 2732,2740 **** #define bar(x) lose(x) #define lose(x) (1 + (x)) ! We would like 'bar(foo)' to turn into '(1 + (foo))', which would ! then turn into '(1 + (a,b))'. Instead, 'bar(foo)' expands into ! 'lose(a,b)', and you get an error because 'lose' requires a single argument. In this case, the problem is easily solved by the same parentheses that ought to be used to prevent misnesting of arithmetic operations: --- 2745,2753 ---- #define bar(x) lose(x) #define lose(x) (1 + (x)) ! We would like `bar(foo)' to turn into `(1 + (foo))', which would ! then turn into `(1 + (a,b))'. Instead, `bar(foo)' expands into ! `lose(a,b)', and you get an error because `lose' requires a single argument. In this case, the problem is easily solved by the same parentheses that ought to be used to prevent misnesting of arithmetic operations: *************** cases: *** 2743,2751 **** or #define bar(x) lose((x)) ! The extra pair of parentheses prevents the comma in 'foo''s definition from being interpreted as an argument separator.  File: cpp.info, Node: Newlines in Arguments, Prev: Argument Prescan, Up: Macro Pitfalls --- 2756,2765 ---- or #define bar(x) lose((x)) ! The extra pair of parentheses prevents the comma in `foo''s definition from being interpreted as an argument separator. +  File: cpp.info, Node: Newlines in Arguments, Prev: Argument Prescan, Up: Macro Pitfalls *************** different to the line containing the arg *** 2766,2772 **** ignored (), syntax error); ! The syntax error triggered by the tokens 'syntax error' results in an error message citing line three--the line of ignore_second_arg-- even though the problematic code comes from line five. --- 2780,2786 ---- ignored (), syntax error); ! The syntax error triggered by the tokens `syntax error' results in an error message citing line three--the line of ignore_second_arg-- even though the problematic code comes from line five. *************** File: cpp.info, Node: Conditionals, Ne *** 2778,2804 **** 4 Conditionals ************** ! A "conditional" is a directive that instructs the preprocessor to select ! whether or not to include a chunk of code in the final token stream ! passed to the compiler. Preprocessor conditionals can test arithmetic ! expressions, or whether a name is defined as a macro, or both ! simultaneously using the special 'defined' operator. ! A conditional in the C preprocessor resembles in some ways an 'if' statement in C, but it is important to understand the difference between ! them. The condition in an 'if' statement is tested during the execution ! of your program. Its purpose is to allow your program to behave ! differently from run to run, depending on the data it is operating on. ! The condition in a preprocessing conditional directive is tested when ! your program is compiled. Its purpose is to allow different code to be ! included in the program depending on the situation at the time of ! compilation. However, the distinction is becoming less clear. Modern compilers ! often do test 'if' statements when a program is compiled, if their conditions are known not to vary at run time, and eliminate code which can never be executed. If you can count on your compiler to do this, ! you may find that your program is more readable if you use 'if' statements with constant conditions (perhaps determined by macros). Of course, you can only use this to exclude code, not type definitions or other preprocessing directives, and you can only do it if the code --- 2792,2818 ---- 4 Conditionals ************** ! A "conditional" is a directive that instructs the preprocessor to ! select whether or not to include a chunk of code in the final token ! stream passed to the compiler. Preprocessor conditionals can test ! arithmetic expressions, or whether a name is defined as a macro, or both ! simultaneously using the special `defined' operator. ! A conditional in the C preprocessor resembles in some ways an `if' statement in C, but it is important to understand the difference between ! them. The condition in an `if' statement is tested during the ! execution of your program. Its purpose is to allow your program to ! behave differently from run to run, depending on the data it is ! operating on. The condition in a preprocessing conditional directive is ! tested when your program is compiled. Its purpose is to allow different ! code to be included in the program depending on the situation at the ! time of compilation. However, the distinction is becoming less clear. Modern compilers ! often do test `if' statements when a program is compiled, if their conditions are known not to vary at run time, and eliminate code which can never be executed. If you can count on your compiler to do this, ! you may find that your program is more readable if you use `if' statements with constant conditions (perhaps determined by macros). Of course, you can only use this to exclude code, not type definitions or other preprocessing directives, and you can only do it if the code *************** There are three general reasons to use a *** 2826,2844 **** one operating system may be erroneous on another operating system; for example, it might refer to data types or constants that do not exist on the other system. When this happens, it is not enough to ! avoid executing the invalid code. Its mere presence will cause the ! compiler to reject the program. With a preprocessing conditional, ! the offending code can be effectively excised from the program when ! it is not valid. * You may want to be able to compile the same source file into two different programs. One version might make frequent time-consuming consistency checks on its intermediate data, or print the values of those data for debugging, and the other not. ! * A conditional whose condition is always false is one way to exclude ! code from the program but keep it as a sort of comment for future ! reference. Simple programs that do not need system-specific logic or complex debugging hooks generally will not need to use preprocessing --- 2840,2858 ---- one operating system may be erroneous on another operating system; for example, it might refer to data types or constants that do not exist on the other system. When this happens, it is not enough to ! avoid executing the invalid code. Its mere presence will cause ! the compiler to reject the program. With a preprocessing ! conditional, the offending code can be effectively excised from ! the program when it is not valid. * You may want to be able to compile the same source file into two different programs. One version might make frequent time-consuming consistency checks on its intermediate data, or print the values of those data for debugging, and the other not. ! * A conditional whose condition is always false is one way to ! exclude code from the program but keep it as a sort of comment for ! future reference. Simple programs that do not need system-specific logic or complex debugging hooks generally will not need to use preprocessing *************** File: cpp.info, Node: Conditional Synta *** 2851,2857 **** ====================== A conditional in the C preprocessor begins with a "conditional ! directive": '#if', '#ifdef' or '#ifndef'. * Menu: --- 2865,2871 ---- ====================== A conditional in the C preprocessor begins with a "conditional ! directive": `#if', `#ifdef' or `#ifndef'. * Menu: *************** included in the output of the preprocess *** 2880,2891 **** defined. We say that the conditional "succeeds" if MACRO is defined, "fails" if it is not. ! The CONTROLLED TEXT inside of a conditional can include preprocessing ! directives. They are executed only if the conditional succeeds. You ! can nest conditional groups inside other conditional groups, but they ! must be completely nested. In other words, '#endif' always matches the ! nearest '#ifdef' (or '#ifndef', or '#if'). Also, you cannot start a ! conditional group in one file and end it in another. Even if a conditional fails, the CONTROLLED TEXT inside it is still run through initial transformations and tokenization. Therefore, it --- 2894,2905 ---- defined. We say that the conditional "succeeds" if MACRO is defined, "fails" if it is not. ! The CONTROLLED TEXT inside of a conditional can include ! preprocessing directives. They are executed only if the conditional ! succeeds. You can nest conditional groups inside other conditional ! groups, but they must be completely nested. In other words, `#endif' ! always matches the nearest `#ifdef' (or `#ifndef', or `#if'). Also, ! you cannot start a conditional group in one file and end it in another. Even if a conditional fails, the CONTROLLED TEXT inside it is still run through initial transformations and tokenization. Therefore, it *************** must all be lexically valid C. Normally *** 2893,2910 **** that all comments and string literals inside a failing conditional group must still be properly ended. ! The comment following the '#endif' is not required, but it is a good practice if there is a lot of CONTROLLED TEXT, because it helps people ! match the '#endif' to the corresponding '#ifdef'. Older programs ! sometimes put MACRO directly after the '#endif' without enclosing it in a comment. This is invalid code according to the C standard. CPP ! accepts it with a warning. It never affects which '#ifndef' the ! '#endif' matches. ! Sometimes you wish to use some code if a macro is _not_ defined. You ! can do this by writing '#ifndef' instead of '#ifdef'. One common use of ! '#ifndef' is to include code only the first time a header file is ! included. *Note Once-Only Headers::. Macro definitions can vary between compilations for several reasons. Here are some samples. --- 2907,2924 ---- that all comments and string literals inside a failing conditional group must still be properly ended. ! The comment following the `#endif' is not required, but it is a good practice if there is a lot of CONTROLLED TEXT, because it helps people ! match the `#endif' to the corresponding `#ifdef'. Older programs ! sometimes put MACRO directly after the `#endif' without enclosing it in a comment. This is invalid code according to the C standard. CPP ! accepts it with a warning. It never affects which `#ifndef' the ! `#endif' matches. ! Sometimes you wish to use some code if a macro is _not_ defined. ! You can do this by writing `#ifndef' instead of `#ifdef'. One common ! use of `#ifndef' is to include code only the first time a header file ! is included. *Note Once-Only Headers::. Macro definitions can vary between compilations for several reasons. Here are some samples. *************** Here are some samples. *** 2918,2936 **** conditionals to avoid using a system feature on a machine where it is not implemented. ! * Macros can be defined or undefined with the '-D' and '-U' ! command-line options when you compile the program. You can arrange ! to compile the same source file into two different programs by ! choosing a macro name to specify which program you want, writing ! conditionals to test whether or how this macro is defined, and then ! controlling the state of the macro with command-line options, ! perhaps set in the Makefile. *Note Invocation::. * Your program might have a special header file (often called ! 'config.h') that is adjusted when the program is compiled. It can ! define or not define macros depending on the features of the system ! and the desired capabilities of the program. The adjustment can be ! automated by a tool such as 'autoconf', or done by hand.  File: cpp.info, Node: If, Next: Defined, Prev: Ifdef, Up: Conditional Syntax --- 2932,2952 ---- conditionals to avoid using a system feature on a machine where it is not implemented. ! * Macros can be defined or undefined with the `-D' and `-U' ! command-line options when you compile the program. You can ! arrange to compile the same source file into two different ! programs by choosing a macro name to specify which program you ! want, writing conditionals to test whether or how this macro is ! defined, and then controlling the state of the macro with ! command-line options, perhaps set in the Makefile. *Note ! Invocation::. * Your program might have a special header file (often called ! `config.h') that is adjusted when the program is compiled. It can ! define or not define macros depending on the features of the ! system and the desired capabilities of the program. The ! adjustment can be automated by a tool such as `autoconf', or done ! by hand.  File: cpp.info, Node: If, Next: Defined, Prev: Ifdef, Up: Conditional Syntax *************** File: cpp.info, Node: If, Next: Define *** 2938,2944 **** 4.2.2 If -------- ! The '#if' directive allows you to test the value of an arithmetic expression, rather than the mere existence of one macro. Its syntax is #if EXPRESSION --- 2954,2960 ---- 4.2.2 If -------- ! The `#if' directive allows you to test the value of an arithmetic expression, rather than the mere existence of one macro. Its syntax is #if EXPRESSION *************** restrictions. It may contain *** 2957,2985 **** * Arithmetic operators for addition, subtraction, multiplication, division, bitwise operations, shifts, comparisons, and logical ! operations ('&&' and '||'). The latter two obey the usual short-circuiting rules of standard C. * Macros. All macros in the expression are expanded before actual computation of the expression's value begins. ! * Uses of the 'defined' operator, which lets you check whether macros ! are defined in the middle of an '#if'. * Identifiers that are not macros, which are all considered to be the ! number zero. This allows you to write '#if MACRO' instead of ! '#ifdef MACRO', if you know that MACRO, when defined, will always have a nonzero value. Function-like macros used without their function call parentheses are also treated as zero. ! In some contexts this shortcut is undesirable. The '-Wundef' option causes GCC to warn whenever it encounters an identifier ! which is not a macro in an '#if'. The preprocessor does not know anything about types in the language. ! Therefore, 'sizeof' operators are not recognized in '#if', and neither ! are 'enum' constants. They will be taken as identifiers which are not ! macros, and replaced by zero. In the case of 'sizeof', this is likely to cause the expression to be invalid. The preprocessor calculates the value of EXPRESSION. It carries out --- 2973,3001 ---- * Arithmetic operators for addition, subtraction, multiplication, division, bitwise operations, shifts, comparisons, and logical ! operations (`&&' and `||'). The latter two obey the usual short-circuiting rules of standard C. * Macros. All macros in the expression are expanded before actual computation of the expression's value begins. ! * Uses of the `defined' operator, which lets you check whether macros ! are defined in the middle of an `#if'. * Identifiers that are not macros, which are all considered to be the ! number zero. This allows you to write `#if MACRO' instead of ! `#ifdef MACRO', if you know that MACRO, when defined, will always have a nonzero value. Function-like macros used without their function call parentheses are also treated as zero. ! In some contexts this shortcut is undesirable. The `-Wundef' option causes GCC to warn whenever it encounters an identifier ! which is not a macro in an `#if'. The preprocessor does not know anything about types in the language. ! Therefore, `sizeof' operators are not recognized in `#if', and neither ! are `enum' constants. They will be taken as identifiers which are not ! macros, and replaced by zero. In the case of `sizeof', this is likely to cause the expression to be invalid. The preprocessor calculates the value of EXPRESSION. It carries out *************** all calculations in the widest integer t *** 2987,2993 **** most machines supported by GCC this is 64 bits. This is not the same rule as the compiler uses to calculate the value of a constant expression, and may give different results in some cases. If the value ! comes out to be nonzero, the '#if' succeeds and the CONTROLLED TEXT is included; otherwise it is skipped.  --- 3003,3009 ---- most machines supported by GCC this is 64 bits. This is not the same rule as the compiler uses to calculate the value of a constant expression, and may give different results in some cases. If the value ! comes out to be nonzero, the `#if' succeeds and the CONTROLLED TEXT is included; otherwise it is skipped.  *************** File: cpp.info, Node: Defined, Next: E *** 2996,3028 **** 4.2.3 Defined ------------- ! The special operator 'defined' is used in '#if' and '#elif' expressions ! to test whether a certain name is defined as a macro. 'defined NAME' ! and 'defined (NAME)' are both expressions whose value is 1 if NAME is ! defined as a macro at the current point in the program, and 0 otherwise. ! Thus, '#if defined MACRO' is precisely equivalent to '#ifdef MACRO'. ! 'defined' is useful when you wish to test more than one macro for existence at once. For example, #if defined (__vax__) || defined (__ns16000__) ! would succeed if either of the names '__vax__' or '__ns16000__' is defined as a macro. Conditionals written like this: #if defined BUFSIZE && BUFSIZE >= 1024 ! can generally be simplified to just '#if BUFSIZE >= 1024', since if ! 'BUFSIZE' is not defined, it will be interpreted as having the value zero. ! If the 'defined' operator appears as a result of a macro expansion, the C standard says the behavior is undefined. GNU cpp treats it as a ! genuine 'defined' operator and evaluates it normally. It will warn wherever your code uses this feature if you use the command-line option ! '-pedantic', since other compilers may handle it differently.  File: cpp.info, Node: Else, Next: Elif, Prev: Defined, Up: Conditional Syntax --- 3012,3045 ---- 4.2.3 Defined ------------- ! The special operator `defined' is used in `#if' and `#elif' expressions ! to test whether a certain name is defined as a macro. `defined NAME' ! and `defined (NAME)' are both expressions whose value is 1 if NAME is ! defined as a macro at the current point in the program, and 0 ! otherwise. Thus, `#if defined MACRO' is precisely equivalent to ! `#ifdef MACRO'. ! `defined' is useful when you wish to test more than one macro for existence at once. For example, #if defined (__vax__) || defined (__ns16000__) ! would succeed if either of the names `__vax__' or `__ns16000__' is defined as a macro. Conditionals written like this: #if defined BUFSIZE && BUFSIZE >= 1024 ! can generally be simplified to just `#if BUFSIZE >= 1024', since if ! `BUFSIZE' is not defined, it will be interpreted as having the value zero. ! If the `defined' operator appears as a result of a macro expansion, the C standard says the behavior is undefined. GNU cpp treats it as a ! genuine `defined' operator and evaluates it normally. It will warn wherever your code uses this feature if you use the command-line option ! `-pedantic', since other compilers may handle it differently.  File: cpp.info, Node: Else, Next: Elif, Prev: Defined, Up: Conditional Syntax *************** File: cpp.info, Node: Else, Next: Elif *** 3030,3036 **** 4.2.4 Else ---------- ! The '#else' directive can be added to a conditional to provide alternative text to be used if the condition fails. This is what it looks like: --- 3047,3053 ---- 4.2.4 Else ---------- ! The `#else' directive can be added to a conditional to provide alternative text to be used if the condition fails. This is what it looks like: *************** looks like: *** 3043,3049 **** If EXPRESSION is nonzero, the TEXT-IF-TRUE is included and the TEXT-IF-FALSE is skipped. If EXPRESSION is zero, the opposite happens. ! You can use '#else' with '#ifdef' and '#ifndef', too.  File: cpp.info, Node: Elif, Prev: Else, Up: Conditional Syntax --- 3060,3066 ---- If EXPRESSION is nonzero, the TEXT-IF-TRUE is included and the TEXT-IF-FALSE is skipped. If EXPRESSION is zero, the opposite happens. ! You can use `#else' with `#ifdef' and `#ifndef', too.  File: cpp.info, Node: Elif, Prev: Else, Up: Conditional Syntax *************** two possible alternatives. For example, *** 3064,3071 **** #endif /* X != 2 */ #endif /* X != 1 */ ! Another conditional directive, '#elif', allows this to be abbreviated ! as follows: #if X == 1 ... --- 3081,3088 ---- #endif /* X != 2 */ #endif /* X != 1 */ ! Another conditional directive, `#elif', allows this to be ! abbreviated as follows: #if X == 1 ... *************** as follows: *** 3075,3094 **** ... #endif /* X != 2 and X != 1*/ ! '#elif' stands for "else if". Like '#else', it goes in the middle of ! a conditional group and subdivides it; it does not require a matching ! '#endif' of its own. Like '#if', the '#elif' directive includes an ! expression to be tested. The text following the '#elif' is processed ! only if the original '#if'-condition failed and the '#elif' condition ! succeeds. ! More than one '#elif' can go in the same conditional group. Then the ! text after each '#elif' is processed only if the '#elif' condition ! succeeds after the original '#if' and all previous '#elif' directives within it have failed. ! '#else' is allowed after any number of '#elif' directives, but ! '#elif' may not follow '#else'.  File: cpp.info, Node: Deleted Code, Prev: Conditional Syntax, Up: Conditionals --- 3092,3111 ---- ... #endif /* X != 2 and X != 1*/ ! `#elif' stands for "else if". Like `#else', it goes in the middle ! of a conditional group and subdivides it; it does not require a ! matching `#endif' of its own. Like `#if', the `#elif' directive ! includes an expression to be tested. The text following the `#elif' is ! processed only if the original `#if'-condition failed and the `#elif' ! condition succeeds. ! More than one `#elif' can go in the same conditional group. Then ! the text after each `#elif' is processed only if the `#elif' condition ! succeeds after the original `#if' and all previous `#elif' directives within it have failed. ! `#else' is allowed after any number of `#elif' directives, but ! `#elif' may not follow `#else'.  File: cpp.info, Node: Deleted Code, Prev: Conditional Syntax, Up: Conditionals *************** code will end the commenting-out. The p *** 3103,3122 **** syntax errors. One way to avoid this problem is to use an always-false conditional ! instead. For instance, put '#if 0' before the deleted code and '#endif' ! after it. This works even if the code being turned off contains ! conditionals, but they must be entire conditionals (balanced '#if' and ! '#endif'). ! Some people use '#ifdef notdef' instead. This is risky, because ! 'notdef' might be accidentally defined as a macro, and then the ! conditional would succeed. '#if 0' can be counted on to fail. ! Do not use '#if 0' for comments which are not C code. Use a real ! comment, instead. The interior of '#if 0' must consist of complete tokens; in particular, single-quote characters must balance. Comments often contain unbalanced single-quote characters (known in English as ! apostrophes). These confuse '#if 0'. They don't confuse '/*'.  File: cpp.info, Node: Diagnostics, Next: Line Control, Prev: Conditionals, Up: Top --- 3120,3139 ---- syntax errors. One way to avoid this problem is to use an always-false conditional ! instead. For instance, put `#if 0' before the deleted code and ! `#endif' after it. This works even if the code being turned off ! contains conditionals, but they must be entire conditionals (balanced ! `#if' and `#endif'). ! Some people use `#ifdef notdef' instead. This is risky, because ! `notdef' might be accidentally defined as a macro, and then the ! conditional would succeed. `#if 0' can be counted on to fail. ! Do not use `#if 0' for comments which are not C code. Use a real ! comment, instead. The interior of `#if 0' must consist of complete tokens; in particular, single-quote characters must balance. Comments often contain unbalanced single-quote characters (known in English as ! apostrophes). These confuse `#if 0'. They don't confuse `/*'.  File: cpp.info, Node: Diagnostics, Next: Line Control, Prev: Conditionals, Up: Top *************** File: cpp.info, Node: Diagnostics, Nex *** 3124,3134 **** 5 Diagnostics ************* ! The directive '#error' causes the preprocessor to report a fatal error. ! The tokens forming the rest of the line following '#error' are used as the error message. ! You would use '#error' inside of a conditional that detects a combination of parameters which you know the program does not properly support. For example, if you know that the program will not run properly on a VAX, you might write --- 3141,3151 ---- 5 Diagnostics ************* ! The directive `#error' causes the preprocessor to report a fatal error. ! The tokens forming the rest of the line following `#error' are used as the error message. ! You would use `#error' inside of a conditional that detects a combination of parameters which you know the program does not properly support. For example, if you know that the program will not run properly on a VAX, you might write *************** properly on a VAX, you might write *** 3139,3162 **** If you have several configuration parameters that must be set up by the installation in a consistent way, you can use conditionals to detect ! an inconsistency and report it with '#error'. For example, #if !defined(FOO) && defined(BAR) #error "BAR requires FOO." #endif ! The directive '#warning' is like '#error', but causes the preprocessor to issue a warning and continue preprocessing. The tokens ! following '#warning' are used as the warning message. ! You might use '#warning' in obsolete header files, with a message directing the user to the header file which should be used instead. ! Neither '#error' nor '#warning' macro-expands its argument. Internal ! whitespace sequences are each replaced with a single space. The line ! must consist of complete tokens. It is wisest to make the argument of ! these directives be a single string constant; this avoids problems with ! apostrophes and the like.  File: cpp.info, Node: Line Control, Next: Pragmas, Prev: Diagnostics, Up: Top --- 3156,3179 ---- If you have several configuration parameters that must be set up by the installation in a consistent way, you can use conditionals to detect ! an inconsistency and report it with `#error'. For example, #if !defined(FOO) && defined(BAR) #error "BAR requires FOO." #endif ! The directive `#warning' is like `#error', but causes the preprocessor to issue a warning and continue preprocessing. The tokens ! following `#warning' are used as the warning message. ! You might use `#warning' in obsolete header files, with a message directing the user to the header file which should be used instead. ! Neither `#error' nor `#warning' macro-expands its argument. ! Internal whitespace sequences are each replaced with a single space. ! The line must consist of complete tokens. It is wisest to make the ! argument of these directives be a single string constant; this avoids ! problems with apostrophes and the like.  File: cpp.info, Node: Line Control, Next: Pragmas, Prev: Diagnostics, Up: Top *************** reported as having appeared on the line *** 3171,3228 **** outermost macro was used. We intend to be more accurate in the future. If you write a program which generates source code, such as the ! 'bison' parser generator, you may want to adjust the preprocessor's notion of the current file name and line number by hand. Parts of the ! output from 'bison' are generated from scratch, other parts come from a ! standard parser file. The rest are copied verbatim from 'bison''s ! input. You would like compiler error messages and symbolic debuggers to ! be able to refer to 'bison''s input file. ! 'bison' or any such program can arrange this by writing '#line' ! directives into the output file. '#line' is a directive that specifies the original line number and source file name for subsequent input in ! the current preprocessor input file. '#line' has three variants: ! '#line LINENUM' LINENUM is a non-negative decimal integer constant. It specifies the line number which should be reported for the following line of input. Subsequent lines are counted from LINENUM. ! '#line LINENUM FILENAME' ! LINENUM is the same as for the first form, and has the same effect. ! In addition, FILENAME is a string constant. The following line and ! all subsequent lines are reported to come from the file it ! specifies, until something else happens to change that. FILENAME ! is interpreted according to the normal rules for a string constant: ! backslash escapes are interpreted. This is different from ! '#include'. ! Previous versions of CPP did not interpret escapes in '#line'; we have changed it because the standard requires they be interpreted, and most other compilers do. ! '#line ANYTHING ELSE' ANYTHING ELSE is checked for macro calls, which are expanded. The result should match one of the above two forms. ! '#line' directives alter the results of the '__FILE__' and '__LINE__' ! predefined macros from that point on. *Note Standard Predefined ! Macros::. They do not have any effect on '#include''s idea of the ! directory containing the current file. This is a change from GCC 2.95. ! Previously, a file reading #include "gram.h" ! would search for 'gram.h' in '../src', then the '-I' chain; the ! directory containing the physical source file would not be searched. In ! GCC 3.0 and later, the '#include' is not affected by the presence of a ! '#line' referring to a different directory. We made this change because the old behavior caused problems when generated source files were transported between machines. For instance, it is common practice to ship generated parsers with a source release, so that people building the distribution do not need to have yacc or ! Bison installed. These files frequently have '#line' directives referring to the directory tree of the system where the distribution was created. If GCC tries to search for headers in those directories, the build is likely to fail. --- 3188,3246 ---- outermost macro was used. We intend to be more accurate in the future. If you write a program which generates source code, such as the ! `bison' parser generator, you may want to adjust the preprocessor's notion of the current file name and line number by hand. Parts of the ! output from `bison' are generated from scratch, other parts come from a ! standard parser file. The rest are copied verbatim from `bison''s ! input. You would like compiler error messages and symbolic debuggers ! to be able to refer to `bison''s input file. ! `bison' or any such program can arrange this by writing `#line' ! directives into the output file. `#line' is a directive that specifies the original line number and source file name for subsequent input in ! the current preprocessor input file. `#line' has three variants: ! `#line LINENUM' LINENUM is a non-negative decimal integer constant. It specifies the line number which should be reported for the following line of input. Subsequent lines are counted from LINENUM. ! `#line LINENUM FILENAME' ! LINENUM is the same as for the first form, and has the same ! effect. In addition, FILENAME is a string constant. The ! following line and all subsequent lines are reported to come from ! the file it specifies, until something else happens to change that. ! FILENAME is interpreted according to the normal rules for a string ! constant: backslash escapes are interpreted. This is different ! from `#include'. ! Previous versions of CPP did not interpret escapes in `#line'; we have changed it because the standard requires they be interpreted, and most other compilers do. ! `#line ANYTHING ELSE' ANYTHING ELSE is checked for macro calls, which are expanded. The result should match one of the above two forms. ! `#line' directives alter the results of the `__FILE__' and ! `__LINE__' predefined macros from that point on. *Note Standard ! Predefined Macros::. They do not have any effect on `#include''s idea ! of the directory containing the current file. This is a change from ! GCC 2.95. Previously, a file reading + #line 1 "../src/gram.y" #include "gram.h" ! would search for `gram.h' in `../src', then the `-I' chain; the ! directory containing the physical source file would not be searched. ! In GCC 3.0 and later, the `#include' is not affected by the presence of ! a `#line' referring to a different directory. We made this change because the old behavior caused problems when generated source files were transported between machines. For instance, it is common practice to ship generated parsers with a source release, so that people building the distribution do not need to have yacc or ! Bison installed. These files frequently have `#line' directives referring to the directory tree of the system where the distribution was created. If GCC tries to search for headers in those directories, the build is likely to fail. *************** build is likely to fail. *** 3231,3237 **** in the same directory as its source and it attempts to include a header which would be visible searching from the directory containing the source file. However, this problem is easily solved with an additional ! '-I' switch on the command line. The failures caused by the old semantics could sometimes be corrected only by editing the generated files, which is difficult and error-prone. --- 3249,3255 ---- in the same directory as its source and it attempts to include a header which would be visible searching from the directory containing the source file. However, this problem is easily solved with an additional ! `-I' switch on the command line. The failures caused by the old semantics could sometimes be corrected only by editing the generated files, which is difficult and error-prone. *************** File: cpp.info, Node: Pragmas, Next: O *** 3241,3288 **** 7 Pragmas ********* ! The '#pragma' directive is the method specified by the C standard for providing additional information to the compiler, beyond what is conveyed in the language itself. Three forms of this directive ! (commonly known as "pragmas") are specified by the 1999 C standard. A C ! compiler is free to attach any meaning it likes to other pragmas. GCC has historically preferred to use extensions to the syntax of the ! language, such as '__attribute__', for this purpose. However, GCC does define a few pragmas of its own. These mostly have effects on the entire translation unit or source file. In GCC version 3, all GNU-defined, supported pragmas have been given ! a 'GCC' prefix. This is in line with the 'STDC' prefix on all pragmas defined by C99. For backward compatibility, pragmas which were ! recognized by previous versions are still recognized without the 'GCC' ! prefix, but that usage is deprecated. Some older pragmas are deprecated ! in their entirety. They are not recognized with the 'GCC' prefix. ! *Note Obsolete Features::. ! C99 introduces the '_Pragma' operator. This feature addresses a ! major problem with '#pragma': being a directive, it cannot be produced ! as the result of macro expansion. '_Pragma' is an operator, much like ! 'sizeof' or 'defined', and can be embedded in a macro. ! Its syntax is '_Pragma (STRING-LITERAL)', where STRING-LITERAL can be ! either a normal or wide-character string literal. It is destringized, ! by replacing all '\\' with a single '\' and all '\"' with a '"'. The ! result is then processed as if it had appeared as the right hand side of ! a '#pragma' directive. For example, _Pragma ("GCC dependency \"parse.y\"") ! has the same effect as '#pragma GCC dependency "parse.y"'. The same effect could be achieved using macros, for example #define DO_PRAGMA(x) _Pragma (#x) DO_PRAGMA (GCC dependency "parse.y") ! The standard is unclear on where a '_Pragma' operator can appear. The preprocessor does not accept it within a preprocessing conditional ! directive like '#if'. To be safe, you are probably best keeping it out ! of directives other than '#define', and putting it on a line of its own. This manual documents the pragmas which are meaningful to the preprocessor itself. Other pragmas are meaningful to the C or C++ --- 3259,3306 ---- 7 Pragmas ********* ! The `#pragma' directive is the method specified by the C standard for providing additional information to the compiler, beyond what is conveyed in the language itself. Three forms of this directive ! (commonly known as "pragmas") are specified by the 1999 C standard. A ! C compiler is free to attach any meaning it likes to other pragmas. GCC has historically preferred to use extensions to the syntax of the ! language, such as `__attribute__', for this purpose. However, GCC does define a few pragmas of its own. These mostly have effects on the entire translation unit or source file. In GCC version 3, all GNU-defined, supported pragmas have been given ! a `GCC' prefix. This is in line with the `STDC' prefix on all pragmas defined by C99. For backward compatibility, pragmas which were ! recognized by previous versions are still recognized without the `GCC' ! prefix, but that usage is deprecated. Some older pragmas are ! deprecated in their entirety. They are not recognized with the `GCC' ! prefix. *Note Obsolete Features::. ! C99 introduces the `_Pragma' operator. This feature addresses a ! major problem with `#pragma': being a directive, it cannot be produced ! as the result of macro expansion. `_Pragma' is an operator, much like ! `sizeof' or `defined', and can be embedded in a macro. ! Its syntax is `_Pragma (STRING-LITERAL)', where STRING-LITERAL can ! be either a normal or wide-character string literal. It is ! destringized, by replacing all `\\' with a single `\' and all `\"' with ! a `"'. The result is then processed as if it had appeared as the right ! hand side of a `#pragma' directive. For example, _Pragma ("GCC dependency \"parse.y\"") ! has the same effect as `#pragma GCC dependency "parse.y"'. The same effect could be achieved using macros, for example #define DO_PRAGMA(x) _Pragma (#x) DO_PRAGMA (GCC dependency "parse.y") ! The standard is unclear on where a `_Pragma' operator can appear. The preprocessor does not accept it within a preprocessing conditional ! directive like `#if'. To be safe, you are probably best keeping it out ! of directives other than `#define', and putting it on a line of its own. This manual documents the pragmas which are meaningful to the preprocessor itself. Other pragmas are meaningful to the C or C++ *************** compilers. They are documented in the G *** 3290,3297 **** GCC plugins may provide their own pragmas. ! '#pragma GCC dependency' ! '#pragma GCC dependency' allows you to check the relative dates of the current file and another file. If the other file is more recent than the current file, a warning is issued. This is useful if the current file is derived from the other file, and should be --- 3308,3315 ---- GCC plugins may provide their own pragmas. ! `#pragma GCC dependency' ! `#pragma GCC dependency' allows you to check the relative dates of the current file and another file. If the other file is more recent than the current file, a warning is issued. This is useful if the current file is derived from the other file, and should be *************** compilers. They are documented in the G *** 3302,3312 **** #pragma GCC dependency "parse.y" #pragma GCC dependency "/usr/include/time.h" rerun fixincludes ! '#pragma GCC poison' Sometimes, there is an identifier that you want to remove completely from your program, and make sure that it never creeps back in. To enforce this, you can "poison" the identifier with ! this pragma. '#pragma GCC poison' is followed by a list of identifiers to poison. If any of those identifiers appears anywhere in the source after the directive, it is a hard error. For example, --- 3320,3330 ---- #pragma GCC dependency "parse.y" #pragma GCC dependency "/usr/include/time.h" rerun fixincludes ! `#pragma GCC poison' Sometimes, there is an identifier that you want to remove completely from your program, and make sure that it never creeps back in. To enforce this, you can "poison" the identifier with ! this pragma. `#pragma GCC poison' is followed by a list of identifiers to poison. If any of those identifiers appears anywhere in the source after the directive, it is a hard error. For example, *************** compilers. They are documented in the G *** 3317,3325 **** will produce an error. If a poisoned identifier appears as part of the expansion of a ! macro which was defined before the identifier was poisoned, it will ! _not_ cause an error. This lets you poison an identifier without ! worrying about system headers defining macros that use it. For example, --- 3335,3343 ---- will produce an error. If a poisoned identifier appears as part of the expansion of a ! macro which was defined before the identifier was poisoned, it ! will _not_ cause an error. This lets you poison an identifier ! without worrying about system headers defining macros that use it. For example, *************** compilers. They are documented in the G *** 3329,3347 **** will not produce an error. ! '#pragma GCC system_header' This pragma takes no arguments. It causes the rest of the code in the current file to be treated as if it came from a system header. *Note System Headers::. ! '#pragma GCC warning' ! '#pragma GCC error' ! '#pragma GCC warning "message"' causes the preprocessor to issue a ! warning diagnostic with the text 'message'. The message contained ! in the pragma must be a single string literal. Similarly, '#pragma ! GCC error "message"' issues an error message. Unlike the ! '#warning' and '#error' directives, these pragmas can be embedded ! in preprocessor macros using '_Pragma'.  File: cpp.info, Node: Other Directives, Next: Preprocessor Output, Prev: Pragmas, Up: Top --- 3347,3366 ---- will not produce an error. ! `#pragma GCC system_header' This pragma takes no arguments. It causes the rest of the code in the current file to be treated as if it came from a system header. *Note System Headers::. ! `#pragma GCC warning' ! `#pragma GCC error' ! `#pragma GCC warning "message"' causes the preprocessor to issue a ! warning diagnostic with the text `message'. The message contained ! in the pragma must be a single string literal. Similarly, ! `#pragma GCC error "message"' issues an error message. Unlike the ! `#warning' and `#error' directives, these pragmas can be embedded ! in preprocessor macros using `_Pragma'. !  File: cpp.info, Node: Other Directives, Next: Preprocessor Output, Prev: Pragmas, Up: Top *************** File: cpp.info, Node: Other Directives, *** 3349,3369 **** 8 Other Directives ****************** ! The '#ident' directive takes one argument, a string constant. On some systems, that string constant is copied into a special segment of the ! object file. On other systems, the directive is ignored. The '#sccs' ! directive is a synonym for '#ident'. These directives are not part of the C standard, but they are not official GNU extensions either. What historical information we have been able to find, suggests they originated with System V. ! The "null directive" consists of a '#' followed by a newline, with only whitespace (including comments) in between. A null directive is understood as a preprocessing directive but has no effect on the preprocessor output. The primary significance of the existence of the ! null directive is that an input line consisting of just a '#' will ! produce no output, rather than a line of output containing just a '#'. Supposedly some old C programs contain such lines.  --- 3368,3388 ---- 8 Other Directives ****************** ! The `#ident' directive takes one argument, a string constant. On some systems, that string constant is copied into a special segment of the ! object file. On other systems, the directive is ignored. The `#sccs' ! directive is a synonym for `#ident'. These directives are not part of the C standard, but they are not official GNU extensions either. What historical information we have been able to find, suggests they originated with System V. ! The "null directive" consists of a `#' followed by a newline, with only whitespace (including comments) in between. A null directive is understood as a preprocessing directive but has no effect on the preprocessor output. The primary significance of the existence of the ! null directive is that an input line consisting of just a `#' will ! produce no output, rather than a line of output containing just a `#'. Supposedly some old C programs contain such lines.  *************** that the following line originated in fi *** 3405,3440 **** FILENAME will never contain any non-printing characters; they are replaced with octal escape sequences. ! After the file name comes zero or more flags, which are '1', '2', ! '3', or '4'. If there are multiple flags, spaces separate them. Here is what the flags mean: ! '1' This indicates the start of a new file. ! '2' This indicates returning to a file (after having included another file). ! '3' This indicates that the following text comes from a system header file, so certain warnings should be suppressed. ! '4' This indicates that the following text should be treated as being ! wrapped in an implicit 'extern "C"' block. As an extension, the preprocessor accepts linemarkers in non-assembler input files. They are treated like the corresponding ! '#line' directive, (*note Line Control::), except that trailing flags are permitted, and are interpreted with the meanings described above. If multiple flags are given, they must be in ascending order. Some directives may be duplicated in the output of the preprocessor. ! These are '#ident' (always), '#pragma' (only if the preprocessor does ! not handle the pragma itself), and '#define' and '#undef' (with certain ! debugging options). If this happens, the '#' of the directive will always be in the first column, and there will be no space between the ! '#' and the directive name. If macro expansion happens to generate tokens which might be mistaken for a duplicated directive, a space will ! be inserted between the '#' and the directive name.  File: cpp.info, Node: Traditional Mode, Next: Implementation Details, Prev: Preprocessor Output, Up: Top --- 3424,3462 ---- FILENAME will never contain any non-printing characters; they are replaced with octal escape sequences. ! After the file name comes zero or more flags, which are `1', `2', ! `3', or `4'. If there are multiple flags, spaces separate them. Here is what the flags mean: ! `1' This indicates the start of a new file. ! ! `2' This indicates returning to a file (after having included another file). ! ! `3' This indicates that the following text comes from a system header file, so certain warnings should be suppressed. ! ! `4' This indicates that the following text should be treated as being ! wrapped in an implicit `extern "C"' block. As an extension, the preprocessor accepts linemarkers in non-assembler input files. They are treated like the corresponding ! `#line' directive, (*note Line Control::), except that trailing flags are permitted, and are interpreted with the meanings described above. If multiple flags are given, they must be in ascending order. Some directives may be duplicated in the output of the preprocessor. ! These are `#ident' (always), `#pragma' (only if the preprocessor does ! not handle the pragma itself), and `#define' and `#undef' (with certain ! debugging options). If this happens, the `#' of the directive will always be in the first column, and there will be no space between the ! `#' and the directive name. If macro expansion happens to generate tokens which might be mistaken for a duplicated directive, a space will ! be inserted between the `#' and the directive name.  File: cpp.info, Node: Traditional Mode, Next: Implementation Details, Prev: Preprocessor Output, Up: Top *************** File: cpp.info, Node: Traditional Mode, *** 3444,3450 **** Traditional (pre-standard) C preprocessing is rather different from the preprocessing specified by the standard. When GCC is given the ! '-traditional-cpp' option, it attempts to emulate a traditional preprocessor. GCC versions 3.2 and later only support traditional mode semantics in --- 3466,3472 ---- Traditional (pre-standard) C preprocessing is rather different from the preprocessing specified by the standard. When GCC is given the ! `-traditional-cpp' option, it attempts to emulate a traditional preprocessor. GCC versions 3.2 and later only support traditional mode semantics in *************** simply treated as a stream of text with *** 3477,3506 **** This implementation does not treat trigraphs (*note trigraphs::) specially since they were an invention of the standards committee. It ! handles arbitrarily-positioned escaped newlines properly and splices the ! lines as you would expect; many traditional preprocessors did not do ! this. The form of horizontal whitespace in the input file is preserved in the output. In particular, hard tabs remain hard tabs. This can be useful if, for example, you are preprocessing a Makefile. Traditional CPP only recognizes C-style block comments, and treats ! the '/*' sequence as introducing a comment only if it lies outside quoted text. Quoted text is introduced by the usual single and double ! quotes, and also by an initial '<' in a '#include' directive. Traditionally, comments are completely removed and are not replaced ! with a space. Since a traditional compiler does its own tokenization of ! the output of the preprocessor, this means that comments can effectively ! be used as token paste operators. However, comments behave like ! separators for text handled by the preprocessor itself, since it doesn't ! re-lex its input. For example, in #if foo/**/bar ! 'foo' and 'bar' are distinct identifiers and expanded separately if they ! happen to be macros. In other words, this directive is equivalent to #if foo bar --- 3499,3529 ---- This implementation does not treat trigraphs (*note trigraphs::) specially since they were an invention of the standards committee. It ! handles arbitrarily-positioned escaped newlines properly and splices ! the lines as you would expect; many traditional preprocessors did not ! do this. The form of horizontal whitespace in the input file is preserved in the output. In particular, hard tabs remain hard tabs. This can be useful if, for example, you are preprocessing a Makefile. Traditional CPP only recognizes C-style block comments, and treats ! the `/*' sequence as introducing a comment only if it lies outside quoted text. Quoted text is introduced by the usual single and double ! quotes, and also by an initial `<' in a `#include' directive. Traditionally, comments are completely removed and are not replaced ! with a space. Since a traditional compiler does its own tokenization ! of the output of the preprocessor, this means that comments can ! effectively be used as token paste operators. However, comments behave ! like separators for text handled by the preprocessor itself, since it ! doesn't re-lex its input. For example, in #if foo/**/bar ! `foo' and `bar' are distinct identifiers and expanded separately if ! they happen to be macros. In other words, this directive is equivalent ! to #if foo bar *************** with replacement text that contains an u *** 3514,3520 **** you attempt to compile preprocessed output containing an unmatched quote you will get a syntax error. ! However, all preprocessing directives other than '#define' require matching quotes. For example: #define m This macro's fine and has an unmatched quote --- 3537,3543 ---- you attempt to compile preprocessed output containing an unmatched quote you will get a syntax error. ! However, all preprocessing directives other than `#define' require matching quotes. For example: #define m This macro's fine and has an unmatched quote *************** can run together with the text after the *** 3545,3560 **** single token. Normally comments are removed from the replacement text after the ! macro is expanded, but if the '-CC' option is passed on the command-line ! comments are preserved. (In fact, the current implementation removes ! comments even before saving the macro replacement text, but it careful ! to do it in such a way that the observed effect is identical even in the ! function-like macro case.) ! The ISO stringification operator '#' and token paste operator '##' ! have no special meaning. As explained later, an effect similar to these ! operators can be obtained in a different way. Macro names that are ! embedded in quotes, either from the main file or after macro replacement, do not expand. CPP replaces an unquoted object-like macro name with its replacement --- 3568,3583 ---- single token. Normally comments are removed from the replacement text after the ! macro is expanded, but if the `-CC' option is passed on the ! command-line comments are preserved. (In fact, the current ! implementation removes comments even before saving the macro ! replacement text, but it careful to do it in such a way that the ! observed effect is identical even in the function-like macro case.) ! The ISO stringification operator `#' and token paste operator `##' ! have no special meaning. As explained later, an effect similar to ! these operators can be obtained in a different way. Macro names that ! are embedded in quotes, either from the main file or after macro replacement, do not expand. CPP replaces an unquoted object-like macro name with its replacement *************** invocation. *** 3574,3595 **** Function-like macros are similar in form but quite different in behavior to their ISO counterparts. Their arguments are contained within parentheses, are comma-separated, and can cross physical lines. ! Commas within nested parentheses are not treated as argument separators. ! Similarly, a quote in an argument cannot be left unclosed; a following ! comma or parenthesis that comes before the closing quote is treated like ! any other character. There is no facility for handling variadic macros. This implementation removes all comments from macro arguments, unless ! the '-C' option is given. The form of all other horizontal whitespace in arguments is preserved, including leading and trailing whitespace. In particular f( ) ! is treated as an invocation of the macro 'f' with a single argument consisting of a single space. If you want to invoke a function-like ! macro that takes no arguments, you must not leave any whitespace between ! the parentheses. If a macro argument crosses a new line, the new line is replaced with a space when forming the argument. If the previous line contained an --- 3597,3619 ---- Function-like macros are similar in form but quite different in behavior to their ISO counterparts. Their arguments are contained within parentheses, are comma-separated, and can cross physical lines. ! Commas within nested parentheses are not treated as argument ! separators. Similarly, a quote in an argument cannot be left unclosed; ! a following comma or parenthesis that comes before the closing quote is ! treated like any other character. There is no facility for handling ! variadic macros. This implementation removes all comments from macro arguments, unless ! the `-C' option is given. The form of all other horizontal whitespace in arguments is preserved, including leading and trailing whitespace. In particular f( ) ! is treated as an invocation of the macro `f' with a single argument consisting of a single space. If you want to invoke a function-like ! macro that takes no arguments, you must not leave any whitespace ! between the parentheses. If a macro argument crosses a new line, the new line is replaced with a space when forming the argument. If the previous line contained an *************** File: cpp.info, Node: Traditional misce *** 3620,3635 **** Here are some things to be aware of when using the traditional preprocessor. ! * Preprocessing directives are recognized only when their leading '#' ! appears in the first column. There can be no whitespace between ! the beginning of the line and the '#', but whitespace can follow ! the '#'. ! * A true traditional C preprocessor does not recognize '#error' or ! '#pragma', and may not recognize '#elif'. CPP supports all the directives in traditional mode that it supports in ISO mode, including extensions, with the exception that the effects of ! '#pragma GCC poison' are undefined. * __STDC__ is not defined. --- 3644,3659 ---- Here are some things to be aware of when using the traditional preprocessor. ! * Preprocessing directives are recognized only when their leading ! `#' appears in the first column. There can be no whitespace ! between the beginning of the line and the `#', but whitespace can ! follow the `#'. ! * A true traditional C preprocessor does not recognize `#error' or ! `#pragma', and may not recognize `#elif'. CPP supports all the directives in traditional mode that it supports in ISO mode, including extensions, with the exception that the effects of ! `#pragma GCC poison' are undefined. * __STDC__ is not defined. *************** preprocessor. *** 3638,3643 **** --- 3662,3668 ---- * If a line that looks like a directive appears within macro arguments, the behavior is undefined. +  File: cpp.info, Node: Traditional warnings, Prev: Traditional miscellany, Up: Traditional Mode *************** File: cpp.info, Node: Traditional warni *** 3645,3668 **** ========================= You can request warnings about features that did not exist, or worked ! differently, in traditional C with the '-Wtraditional' option. GCC does ! not warn about features of ISO C which you must use when you are using a ! conforming compiler, such as the '#' and '##' operators. ! Presently '-Wtraditional' warns about: * Macro parameters that appear within string literals in the macro ! body. In traditional C macro replacement takes place within string ! literals, but does not in ISO C. * In traditional C, some preprocessor directives did not exist. Traditional preprocessors would only consider a line to be a ! directive if the '#' appeared in column 1 on the line. Therefore ! '-Wtraditional' warns about directives that traditional C ! understands but would ignore because the '#' does not appear as the first character on the line. It also suggests you hide directives ! like '#pragma' not understood by traditional C by indenting them. ! Some traditional implementations would not recognize '#elif', so it suggests avoiding it altogether. * A function-like macro that appears without an argument list. In --- 3670,3693 ---- ========================= You can request warnings about features that did not exist, or worked ! differently, in traditional C with the `-Wtraditional' option. GCC ! does not warn about features of ISO C which you must use when you are ! using a conforming compiler, such as the `#' and `##' operators. ! Presently `-Wtraditional' warns about: * Macro parameters that appear within string literals in the macro ! body. In traditional C macro replacement takes place within ! string literals, but does not in ISO C. * In traditional C, some preprocessor directives did not exist. Traditional preprocessors would only consider a line to be a ! directive if the `#' appeared in column 1 on the line. Therefore ! `-Wtraditional' warns about directives that traditional C ! understands but would ignore because the `#' does not appear as the first character on the line. It also suggests you hide directives ! like `#pragma' not understood by traditional C by indenting them. ! Some traditional implementations would not recognize `#elif', so it suggests avoiding it altogether. * A function-like macro that appears without an argument list. In *************** conforming compiler, such as the '#' and *** 3671,3682 **** * The unary plus operator. This did not exist in traditional C. ! * The 'U' and 'LL' integer constant suffixes, which were not ! available in traditional C. (Traditional C does support the 'L' suffix for simple long integer constants.) You are not warned about uses of these suffixes in macros defined in system headers. ! For instance, 'UINT_MAX' may well be defined as '4294967295U', but ! you will not be warned if you use 'UINT_MAX'. You can usually avoid the warning, and the related warning about constants which are so large that they are unsigned, by writing the --- 3696,3707 ---- * The unary plus operator. This did not exist in traditional C. ! * The `U' and `LL' integer constant suffixes, which were not ! available in traditional C. (Traditional C does support the `L' suffix for simple long integer constants.) You are not warned about uses of these suffixes in macros defined in system headers. ! For instance, `UINT_MAX' may well be defined as `4294967295U', but ! you will not be warned if you use `UINT_MAX'. You can usually avoid the warning, and the related warning about constants which are so large that they are unsigned, by writing the *************** File: cpp.info, Node: Implementation-de *** 3712,3779 **** ==================================== This is how CPP behaves in all the cases which the C standard describes ! as "implementation-defined". This term means that the implementation is ! free to do what it likes, but must document its choice and stick to it. * The mapping of physical source file multi-byte characters to the execution character set. The input character set can be specified using the ! '-finput-charset' option, while the execution character set may be ! controlled using the '-fexec-charset' and '-fwide-exec-charset' options. ! * Identifier characters. ! ! The C and C++ standards allow identifiers to be composed of '_' and ! the alphanumeric characters. C++ and C99 also allow universal ! character names, and C99 further permits implementation-defined ! characters. ! GCC allows the '$' character in identifiers as an extension for ! most targets. This is true regardless of the 'std=' switch, since this extension cannot conflict with standards-conforming programs. When preprocessing assembler, however, dollars are not identifier characters by default. ! Currently the targets that by default do not permit '$' are AVR, IP2K, MMIX, MIPS Irix 3, ARM aout, and PowerPC targets for the AIX operating system. ! You can override the default with '-fdollars-in-identifiers' or ! 'fno-dollars-in-identifiers'. *Note fdollars-in-identifiers::. * Non-empty sequences of whitespace characters. In textual output, each whitespace sequence is collapsed to a single space. For aesthetic reasons, the first token on each non-directive line of output is preceded with sufficient spaces ! that it appears in the same column as it did in the original source ! file. * The numeric value of character constants in preprocessor expressions. The preprocessor and compiler interpret character constants in the ! same way; i.e. escape sequences such as '\a' are given the values they would have on the target machine. The compiler evaluates a multi-character character constant a ! character at a time, shifting the previous value left by the number ! of bits per target character, and then or-ing in the bit-pattern of ! the new character truncated to the width of a target character. ! The final bit-pattern is given type 'int', and is therefore signed, ! regardless of whether single characters are signed or not (a slight ! change from versions 3.1 and earlier of GCC). If there are more ! characters in the constant than would fit in the target 'int' the ! compiler issues a warning, and the excess leading characters are ! ignored. ! For example, ''ab'' for a target with an 8-bit 'char' would be interpreted as ! '(int) ((unsigned char) 'a' * 256 + (unsigned char) 'b')', and ! ''\234a'' as ! '(int) ((unsigned char) '\234' * 256 + (unsigned char) 'a')'. * Source file inclusion. --- 3737,3803 ---- ==================================== This is how CPP behaves in all the cases which the C standard describes ! as "implementation-defined". This term means that the implementation ! is free to do what it likes, but must document its choice and stick to ! it. * The mapping of physical source file multi-byte characters to the execution character set. The input character set can be specified using the ! `-finput-charset' option, while the execution character set may be ! controlled using the `-fexec-charset' and `-fwide-exec-charset' options. ! * Identifier characters. The C and C++ standards allow identifiers ! to be composed of `_' and the alphanumeric characters. C++ and ! C99 also allow universal character names, and C99 further permits ! implementation-defined characters. ! GCC allows the `$' character in identifiers as an extension for ! most targets. This is true regardless of the `std=' switch, since this extension cannot conflict with standards-conforming programs. When preprocessing assembler, however, dollars are not identifier characters by default. ! Currently the targets that by default do not permit `$' are AVR, IP2K, MMIX, MIPS Irix 3, ARM aout, and PowerPC targets for the AIX operating system. ! You can override the default with `-fdollars-in-identifiers' or ! `fno-dollars-in-identifiers'. *Note fdollars-in-identifiers::. * Non-empty sequences of whitespace characters. In textual output, each whitespace sequence is collapsed to a single space. For aesthetic reasons, the first token on each non-directive line of output is preceded with sufficient spaces ! that it appears in the same column as it did in the original ! source file. * The numeric value of character constants in preprocessor expressions. The preprocessor and compiler interpret character constants in the ! same way; i.e. escape sequences such as `\a' are given the values they would have on the target machine. The compiler evaluates a multi-character character constant a ! character at a time, shifting the previous value left by the ! number of bits per target character, and then or-ing in the ! bit-pattern of the new character truncated to the width of a ! target character. The final bit-pattern is given type `int', and ! is therefore signed, regardless of whether single characters are ! signed or not (a slight change from versions 3.1 and earlier of ! GCC). If there are more characters in the constant than would fit ! in the target `int' the compiler issues a warning, and the excess ! leading characters are ignored. ! For example, `'ab'' for a target with an 8-bit `char' would be interpreted as ! `(int) ((unsigned char) 'a' * 256 + (unsigned char) 'b')', and ! `'\234a'' as ! `(int) ((unsigned char) '\234' * 256 + (unsigned char) 'a')'. * Source file inclusion. *************** free to do what it likes, but must docum *** 3781,3798 **** *note Include Operation::. * Interpretation of the filename resulting from a macro-expanded ! '#include' directive. *Note Computed Includes::. ! * Treatment of a '#pragma' directive that after macro-expansion results in a standard pragma. ! No macro expansion occurs on any '#pragma' directive line, so the question does not arise. Note that GCC does not yet implement any of the standard pragmas.  File: cpp.info, Node: Implementation limits, Next: Obsolete Features, Prev: Implementation-defined behavior, Up: Implementation Details --- 3805,3823 ---- *note Include Operation::. * Interpretation of the filename resulting from a macro-expanded ! `#include' directive. *Note Computed Includes::. ! * Treatment of a `#pragma' directive that after macro-expansion results in a standard pragma. ! No macro expansion occurs on any `#pragma' directive line, so the question does not arise. Note that GCC does not yet implement any of the standard pragmas. +  File: cpp.info, Node: Implementation limits, Next: Obsolete Features, Prev: Implementation-defined behavior, Up: Implementation Details *************** limit, please report that as a bug. *No *** 3807,3818 **** Where we say something is limited "only by available memory", that means that internal data structures impose no intrinsic limit, and space ! is allocated with 'malloc' or equivalent. The actual limit will therefore depend on many things, such as the size of other things allocated by the compiler at the same time, the amount of memory consumed by other processes on the same computer, etc. ! * Nesting levels of '#include' files. We impose an arbitrary limit of 200 levels, to avoid runaway recursion. The standard requires at least 15 levels. --- 3832,3843 ---- Where we say something is limited "only by available memory", that means that internal data structures impose no intrinsic limit, and space ! is allocated with `malloc' or equivalent. The actual limit will therefore depend on many things, such as the size of other things allocated by the compiler at the same time, the amount of memory consumed by other processes on the same computer, etc. ! * Nesting levels of `#include' files. We impose an arbitrary limit of 200 levels, to avoid runaway recursion. The standard requires at least 15 levels. *************** consumed by other processes on the same *** 3838,3847 **** The standard requires at least 4095 be possible. CPP is limited only by available memory. ! * Number of parameters in a macro definition and arguments in a macro ! call. ! We allow 'USHRT_MAX', which is no smaller than 65,535. The minimum required by the standard is 127. * Number of characters on a logical source line. --- 3863,3872 ---- The standard requires at least 4095 be possible. CPP is limited only by available memory. ! * Number of parameters in a macro definition and arguments in a ! macro call. ! We allow `USHRT_MAX', which is no smaller than 65,535. The minimum required by the standard is 127. * Number of characters on a logical source line. *************** consumed by other processes on the same *** 3853,3862 **** * Maximum size of a source file. The standard does not specify any lower limit on the maximum size ! of a source file. GNU cpp maps files into memory, so it is limited ! by the available address space. This is generally at least two ! gigabytes. Depending on the operating system, the size of physical ! memory may or may not be a limitation.  File: cpp.info, Node: Obsolete Features, Next: Differences from previous versions, Prev: Implementation limits, Up: Implementation Details --- 3878,3888 ---- * Maximum size of a source file. The standard does not specify any lower limit on the maximum size ! of a source file. GNU cpp maps files into memory, so it is ! limited by the available address space. This is generally at ! least two gigabytes. Depending on the operating system, the size ! of physical memory may or may not be a limitation. !  File: cpp.info, Node: Obsolete Features, Next: Differences from previous versions, Prev: Implementation limits, Up: Implementation Details *************** File: cpp.info, Node: Obsolete Features *** 3865,3872 **** ====================== CPP has some features which are present mainly for compatibility with ! older programs. We discourage their use in new code. In some cases, we ! plan to remove the feature in a future version of GCC. 11.3.1 Assertions ----------------- --- 3891,3898 ---- ====================== CPP has some features which are present mainly for compatibility with ! older programs. We discourage their use in new code. In some cases, ! we plan to remove the feature in a future version of GCC. 11.3.1 Assertions ----------------- *************** define them with preprocessing directive *** 3880,3887 **** the compiler's target system and we added them for compatibility with existing compilers. In practice they are just as unpredictable as the system-specific predefined macros. In addition, they are not part of ! any standard, and only a few compilers support them. Therefore, the use ! of assertions is *less* portable than the use of system-specific predefined macros. We recommend you do not use them at all. An assertion looks like this: --- 3906,3913 ---- the compiler's target system and we added them for compatibility with existing compilers. In practice they are just as unpredictable as the system-specific predefined macros. In addition, they are not part of ! any standard, and only a few compilers support them. Therefore, the ! use of assertions is *less* portable than the use of system-specific predefined macros. We recommend you do not use them at all. An assertion looks like this: *************** PREDICATE must be a single identifier. *** 3892,3903 **** tokens; all characters are significant except for leading and trailing whitespace, and differences in internal whitespace sequences are ignored. (This is similar to the rules governing macro redefinition.) ! Thus, '(x + y)' is different from '(x+y)' but equivalent to '( x + y )'. ! Parentheses do not nest inside an answer. ! To test an assertion, you write it in an '#if'. For example, this ! conditional succeeds if either 'vax' or 'ns16000' has been asserted as ! an answer for 'machine'. #if #machine (vax) || #machine (ns16000) --- 3918,3929 ---- tokens; all characters are significant except for leading and trailing whitespace, and differences in internal whitespace sequences are ignored. (This is similar to the rules governing macro redefinition.) ! Thus, `(x + y)' is different from `(x+y)' but equivalent to ! `( x + y )'. Parentheses do not nest inside an answer. ! To test an assertion, you write it in an `#if'. For example, this ! conditional succeeds if either `vax' or `ns16000' has been asserted as ! an answer for `machine'. #if #machine (vax) || #machine (ns16000) *************** omitting the answer in the conditional: *** 3906,3913 **** #if #machine ! Assertions are made with the '#assert' directive. Its sole argument ! is the assertion to make, without the leading '#' that identifies assertions in conditionals. #assert PREDICATE (ANSWER) --- 3932,3939 ---- #if #machine ! Assertions are made with the `#assert' directive. Its sole argument ! is the assertion to make, without the leading `#' that identifies assertions in conditionals. #assert PREDICATE (ANSWER) *************** answers. Subsequent assertions do not o *** 3917,3931 **** same predicate. All the answers for any given predicate are simultaneously true. ! Assertions can be canceled with the '#unassert' directive. It has ! the same syntax as '#assert'. In that form it cancels only the answer ! which was specified on the '#unassert' line; other answers for that predicate remain true. You can cancel an entire predicate by leaving out the answer: #unassert PREDICATE ! In either form, if no such assertion has been made, '#unassert' has no effect. You can also make or cancel assertions using command-line options. --- 3943,3957 ---- same predicate. All the answers for any given predicate are simultaneously true. ! Assertions can be canceled with the `#unassert' directive. It has ! the same syntax as `#assert'. In that form it cancels only the answer ! which was specified on the `#unassert' line; other answers for that predicate remain true. You can cancel an entire predicate by leaving out the answer: #unassert PREDICATE ! In either form, if no such assertion has been made, `#unassert' has no effect. You can also make or cancel assertions using command-line options. *************** File: cpp.info, Node: Differences from *** 3938,3945 **** ======================================= This section details behavior which has changed from previous versions ! of CPP. We do not plan to change it again in the near future, but we do ! not promise not to, either. The "previous versions" discussed here are 2.95 and before. The behavior of GCC 3.0 is mostly the same as the behavior of the widely --- 3964,3971 ---- ======================================= This section details behavior which has changed from previous versions ! of CPP. We do not plan to change it again in the near future, but we ! do not promise not to, either. The "previous versions" discussed here are 2.95 and before. The behavior of GCC 3.0 is mostly the same as the behavior of the widely *************** they generally represent bugs in the sna *** 3948,3995 **** * -I- deprecated ! This option has been deprecated in 4.0. '-iquote' is meant to replace the need for this option. ! * Order of evaluation of '#' and '##' operators The standard does not specify the order of evaluation of a chain of ! '##' operators, nor whether '#' is evaluated before, after, or at ! the same time as '##'. You should therefore not write any code which depends on any specific ordering. It is possible to guarantee an ordering, if you need one, by suitable use of nested macros. ! An example of where this might matter is pasting the arguments '1', ! 'e' and '-2'. This would be fine for left-to-right pasting, but ! right-to-left pasting would produce an invalid token 'e-2'. ! GCC 3.0 evaluates '#' and '##' at the same time and strictly left ! to right. Older versions evaluated all '#' operators first, then ! all '##' operators, in an unreliable order. * The form of whitespace between tokens in preprocessor output *Note Preprocessor Output::, for the current textual format. This is also the format used by stringification. Normally, the ! preprocessor communicates tokens directly to the compiler's parser, ! and whitespace does not come up at all. ! Older versions of GCC preserved all whitespace provided by the user ! and inserted lots more whitespace of their own, because they could ! not accurately predict when extra spaces were needed to prevent ! accidental token pasting. * Optional argument when invoking rest argument macros As an extension, GCC permits you to omit the variable arguments ! entirely when you use a variable argument macro. This is forbidden ! by the 1999 C standard, and will provoke a pedantic warning with ! GCC 3.0. Previous versions accepted it silently. ! * '##' swallowing preceding text in rest argument macros ! Formerly, in a macro expansion, if '##' appeared before a variable arguments parameter, and the set of tokens specified for that argument in the macro invocation was empty, previous versions of CPP would back up and remove the preceding sequence of --- 3974,4021 ---- * -I- deprecated ! This option has been deprecated in 4.0. `-iquote' is meant to replace the need for this option. ! * Order of evaluation of `#' and `##' operators The standard does not specify the order of evaluation of a chain of ! `##' operators, nor whether `#' is evaluated before, after, or at ! the same time as `##'. You should therefore not write any code which depends on any specific ordering. It is possible to guarantee an ordering, if you need one, by suitable use of nested macros. ! An example of where this might matter is pasting the arguments `1', ! `e' and `-2'. This would be fine for left-to-right pasting, but ! right-to-left pasting would produce an invalid token `e-2'. ! GCC 3.0 evaluates `#' and `##' at the same time and strictly left ! to right. Older versions evaluated all `#' operators first, then ! all `##' operators, in an unreliable order. * The form of whitespace between tokens in preprocessor output *Note Preprocessor Output::, for the current textual format. This is also the format used by stringification. Normally, the ! preprocessor communicates tokens directly to the compiler's ! parser, and whitespace does not come up at all. ! Older versions of GCC preserved all whitespace provided by the ! user and inserted lots more whitespace of their own, because they ! could not accurately predict when extra spaces were needed to ! prevent accidental token pasting. * Optional argument when invoking rest argument macros As an extension, GCC permits you to omit the variable arguments ! entirely when you use a variable argument macro. This is ! forbidden by the 1999 C standard, and will provoke a pedantic ! warning with GCC 3.0. Previous versions accepted it silently. ! * `##' swallowing preceding text in rest argument macros ! Formerly, in a macro expansion, if `##' appeared before a variable arguments parameter, and the set of tokens specified for that argument in the macro invocation was empty, previous versions of CPP would back up and remove the preceding sequence of *************** they generally represent bugs in the sna *** 3997,4025 **** extension is in direct conflict with the 1999 C standard and has been drastically pared back. ! In the current version of the preprocessor, if '##' appears between a comma and a variable arguments parameter, and the variable argument is omitted entirely, the comma will be removed from the expansion. If the variable argument is empty, or the token before ! '##' is not a comma, then '##' behaves as a normal token paste. ! * '#line' and '#include' ! The '#line' directive used to change GCC's notion of the "directory ! containing the current file", used by '#include' with a double-quoted header file name. In 3.0 and later, it does not. *Note Line Control::, for further explanation. ! * Syntax of '#line' ! In GCC 2.95 and previous, the string constant argument to '#line' ! was treated the same way as the argument to '#include': backslash ! escapes were not honored, and the string ended at the second '"'. This is not compliant with the C standard. In GCC 3.0, an attempt ! was made to correct the behavior, so that the string was treated as ! a real string constant, but it turned out to be buggy. In 3.1, the ! bugs have been fixed. (We are not fixing the bugs in 3.0 because ! they affect relatively few people and the fix is quite invasive.)  File: cpp.info, Node: Invocation, Next: Environment Variables, Prev: Implementation Details, Up: Top --- 4023,4053 ---- extension is in direct conflict with the 1999 C standard and has been drastically pared back. ! In the current version of the preprocessor, if `##' appears between a comma and a variable arguments parameter, and the variable argument is omitted entirely, the comma will be removed from the expansion. If the variable argument is empty, or the token before ! `##' is not a comma, then `##' behaves as a normal token paste. ! * `#line' and `#include' ! The `#line' directive used to change GCC's notion of the ! "directory containing the current file", used by `#include' with a double-quoted header file name. In 3.0 and later, it does not. *Note Line Control::, for further explanation. ! * Syntax of `#line' ! In GCC 2.95 and previous, the string constant argument to `#line' ! was treated the same way as the argument to `#include': backslash ! escapes were not honored, and the string ended at the second `"'. This is not compliant with the C standard. In GCC 3.0, an attempt ! was made to correct the behavior, so that the string was treated ! as a real string constant, but it turned out to be buggy. In 3.1, ! the bugs have been fixed. (We are not fixing the bugs in 3.0 ! because they affect relatively few people and the fix is quite ! invasive.) !  File: cpp.info, Node: Invocation, Next: Environment Variables, Prev: Implementation Details, Up: Top *************** here are also acceptable to the C compil *** 4034,4072 **** except that the C compiler has different rules for specifying the output file. ! _Note:_ Whether you use the preprocessor by way of 'gcc' or 'cpp', the "compiler driver" is run first. This program's purpose is to translate your command into invocations of the programs that do the actual work. Their command-line interfaces are similar but not identical to the documented interface, and may change without notice. The C preprocessor expects two file names as arguments, INFILE and ! OUTFILE. The preprocessor reads INFILE together with any other files it ! specifies with '#include'. All the output generated by the combined input files is written in OUTFILE. ! Either INFILE or OUTFILE may be '-', which as INFILE means to read from standard input and as OUTFILE means to write to standard output. ! Also, if either file is omitted, it means the same as if '-' had been specified for that file. ! Unless otherwise noted, or the option ends in '=', all options which take an argument may have that argument appear either immediately after ! the option, or with a space between option and argument: '-Ifoo' and '-I ! foo' have the same effect. Many options have multi-letter names; therefore multiple ! single-letter options may _not_ be grouped: '-dM' is very different from ! '-d -M'. ! '-D NAME' ! Predefine NAME as a macro, with definition '1'. ! '-D NAME=DEFINITION' The contents of DEFINITION are tokenized and processed as if they ! appeared during translation phase three in a '#define' directive. ! In particular, the definition will be truncated by embedded newline ! characters. If you are invoking the preprocessor from a shell or shell-like program you may need to use the shell's quoting syntax to protect --- 4062,4100 ---- except that the C compiler has different rules for specifying the output file. ! _Note:_ Whether you use the preprocessor by way of `gcc' or `cpp', the "compiler driver" is run first. This program's purpose is to translate your command into invocations of the programs that do the actual work. Their command-line interfaces are similar but not identical to the documented interface, and may change without notice. The C preprocessor expects two file names as arguments, INFILE and ! OUTFILE. The preprocessor reads INFILE together with any other files ! it specifies with `#include'. All the output generated by the combined input files is written in OUTFILE. ! Either INFILE or OUTFILE may be `-', which as INFILE means to read from standard input and as OUTFILE means to write to standard output. ! Also, if either file is omitted, it means the same as if `-' had been specified for that file. ! Unless otherwise noted, or the option ends in `=', all options which take an argument may have that argument appear either immediately after ! the option, or with a space between option and argument: `-Ifoo' and ! `-I foo' have the same effect. Many options have multi-letter names; therefore multiple ! single-letter options may _not_ be grouped: `-dM' is very different from ! `-d -M'. ! `-D NAME' ! Predefine NAME as a macro, with definition `1'. ! `-D NAME=DEFINITION' The contents of DEFINITION are tokenized and processed as if they ! appeared during translation phase three in a `#define' directive. ! In particular, the definition will be truncated by embedded ! newline characters. If you are invoking the preprocessor from a shell or shell-like program you may need to use the shell's quoting syntax to protect *************** single-letter options may _not_ be group *** 4075,4150 **** If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the equals sign (if any). Parentheses are meaningful to most shells, ! so you will need to quote the option. With 'sh' and 'csh', ! '-D'NAME(ARGS...)=DEFINITION'' works. ! '-D' and '-U' options are processed in the order they are given on ! the command line. All '-imacros FILE' and '-include FILE' options ! are processed after all '-D' and '-U' options. ! '-U NAME' ! Cancel any previous definition of NAME, either built in or provided ! with a '-D' option. ! '-undef' Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. *Note Standard Predefined Macros::. ! '-I DIR' ! Add the directory DIR to the list of directories to be searched for ! header files. *Note Search Path::. Directories named by '-I' are ! searched before the standard system include directories. If the ! directory DIR is a standard system include directory, the option is ! ignored to ensure that the default search order for system ! directories and the special treatment of system headers are not ! defeated (*note System Headers::) . If DIR begins with '=', then ! the '=' will be replaced by the sysroot prefix; see '--sysroot' and ! '-isysroot'. ! '-o FILE' Write output to FILE. This is the same as specifying FILE as the ! second non-option argument to 'cpp'. 'gcc' has a different interpretation of a second non-option argument, so you must use ! '-o' to specify the output file. ! '-Wall' Turns on all optional warnings which are desirable for normal code. ! At present this is '-Wcomment', '-Wtrigraphs', '-Wmultichar' and a ! warning about integer promotion causing a change of sign in '#if' expressions. Note that many of the preprocessor's warnings are on by default and have no options to control them. ! '-Wcomment' ! '-Wcomments' ! Warn whenever a comment-start sequence '/*' appears in a '/*' ! comment, or whenever a backslash-newline appears in a '//' comment. (Both forms have the same effect.) ! '-Wtrigraphs' Most trigraphs in comments cannot affect the meaning of the program. However, a trigraph that would form an escaped newline ! ('??/' at the end of a line) can, by changing where the comment begins or ends. Therefore, only trigraphs that would form escaped newlines produce warnings inside a comment. ! This option is implied by '-Wall'. If '-Wall' is not given, this option is still enabled unless trigraphs are enabled. To get ! trigraph conversion without warnings, but get the other '-Wall' ! warnings, use '-trigraphs -Wall -Wno-trigraphs'. ! '-Wtraditional' Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and problematic constructs which should be avoided. *Note Traditional Mode::. ! '-Wundef' Warn whenever an identifier which is not a macro is encountered in ! an '#if' directive, outside of 'defined'. Such identifiers are replaced with zero. ! '-Wunused-macros' Warn about macros defined in the main file that are unused. A macro is "used" if it is expanded or tested for existence at least once. The preprocessor will also warn if the macro has not been --- 4103,4178 ---- If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the equals sign (if any). Parentheses are meaningful to most shells, ! so you will need to quote the option. With `sh' and `csh', ! `-D'NAME(ARGS...)=DEFINITION'' works. ! `-D' and `-U' options are processed in the order they are given on ! the command line. All `-imacros FILE' and `-include FILE' options ! are processed after all `-D' and `-U' options. ! `-U NAME' ! Cancel any previous definition of NAME, either built in or ! provided with a `-D' option. ! `-undef' Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. *Note Standard Predefined Macros::. ! `-I DIR' ! Add the directory DIR to the list of directories to be searched ! for header files. *Note Search Path::. Directories named by `-I' ! are searched before the standard system include directories. If ! the directory DIR is a standard system include directory, the ! option is ignored to ensure that the default search order for ! system directories and the special treatment of system headers are ! not defeated (*note System Headers::) . If DIR begins with `=', ! then the `=' will be replaced by the sysroot prefix; see ! `--sysroot' and `-isysroot'. ! `-o FILE' Write output to FILE. This is the same as specifying FILE as the ! second non-option argument to `cpp'. `gcc' has a different interpretation of a second non-option argument, so you must use ! `-o' to specify the output file. ! `-Wall' Turns on all optional warnings which are desirable for normal code. ! At present this is `-Wcomment', `-Wtrigraphs', `-Wmultichar' and a ! warning about integer promotion causing a change of sign in `#if' expressions. Note that many of the preprocessor's warnings are on by default and have no options to control them. ! `-Wcomment' ! `-Wcomments' ! Warn whenever a comment-start sequence `/*' appears in a `/*' ! comment, or whenever a backslash-newline appears in a `//' comment. (Both forms have the same effect.) ! `-Wtrigraphs' Most trigraphs in comments cannot affect the meaning of the program. However, a trigraph that would form an escaped newline ! (`??/' at the end of a line) can, by changing where the comment begins or ends. Therefore, only trigraphs that would form escaped newlines produce warnings inside a comment. ! This option is implied by `-Wall'. If `-Wall' is not given, this option is still enabled unless trigraphs are enabled. To get ! trigraph conversion without warnings, but get the other `-Wall' ! warnings, use `-trigraphs -Wall -Wno-trigraphs'. ! `-Wtraditional' Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and problematic constructs which should be avoided. *Note Traditional Mode::. ! `-Wundef' Warn whenever an identifier which is not a macro is encountered in ! an `#if' directive, outside of `defined'. Such identifiers are replaced with zero. ! `-Wunused-macros' Warn about macros defined in the main file that are unused. A macro is "used" if it is expanded or tested for existence at least once. The preprocessor will also warn if the macro has not been *************** single-letter options may _not_ be group *** 4163,4171 **** #if defined the_macro_causing_the_warning #endif ! '-Wendif-labels' ! Warn whenever an '#else' or an '#endif' are followed by text. This ! usually happens in code of the form #if FOO ... --- 4191,4199 ---- #if defined the_macro_causing_the_warning #endif ! `-Wendif-labels' ! Warn whenever an `#else' or an `#endif' are followed by text. ! This usually happens in code of the form #if FOO ... *************** single-letter options may _not_ be group *** 4173,4264 **** ... #endif FOO ! The second and third 'FOO' should be in comments, but often are not in older programs. This warning is on by default. ! '-Werror' Make all warnings into hard errors. Source code which triggers warnings will be rejected. ! '-Wsystem-headers' Issue warnings for code in system headers. These are normally unhelpful in finding bugs in your own code, therefore suppressed. If you are responsible for the system library, you may want to see them. ! '-w' Suppress all warnings, including those which GNU CPP issues by default. ! '-pedantic' ! Issue all the mandatory diagnostics listed in the C standard. Some ! of them are left out by default, since they trigger frequently on ! harmless code. ! '-pedantic-errors' Issue all the mandatory diagnostics, and make all mandatory diagnostics into errors. This includes mandatory diagnostics that ! GCC issues without '-pedantic' but treats as warnings. ! '-M' Instead of outputting the result of preprocessing, output a rule ! suitable for 'make' describing the dependencies of the main source ! file. The preprocessor outputs one 'make' rule containing the object file name for that source file, a colon, and the names of ! all the included files, including those coming from '-include' or ! '-imacros' command-line options. ! Unless specified explicitly (with '-MT' or '-MQ'), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is ! split into several lines using '\'-newline. The rule has no commands. ! This option does not suppress the preprocessor's debug output, such ! as '-dM'. To avoid mixing such debug output with the dependency ! rules you should explicitly specify the dependency output file with ! '-MF', or use an environment variable like 'DEPENDENCIES_OUTPUT' ! (*note Environment Variables::). Debug output will still be sent ! to the regular output stream as normal. ! Passing '-M' to the driver implies '-E', and suppresses warnings ! with an implicit '-w'. ! '-MM' ! Like '-M' but do not mention header files that are found in system ! header directories, nor header files that are included, directly or ! indirectly, from such a header. This implies that the choice of angle brackets or double quotes in ! an '#include' directive does not in itself determine whether that ! header will appear in '-MM' dependency output. This is a slight change in semantics from GCC versions 3.0 and earlier. ! '-MF FILE' ! When used with '-M' or '-MM', specifies a file to write the ! dependencies to. If no '-MF' switch is given the preprocessor sends the rules to the same place it would have sent preprocessed output. ! When used with the driver options '-MD' or '-MMD', '-MF' overrides the default dependency output file. ! '-MG' ! In conjunction with an option such as '-M' requesting dependency ! generation, '-MG' assumes missing header files are generated files ! and adds them to the dependency list without raising an error. The ! dependency filename is taken directly from the '#include' directive ! without prepending any path. '-MG' also suppresses preprocessed ! output, as a missing header file renders this useless. This feature is used in automatic updating of makefiles. ! '-MP' This option instructs CPP to add a phony target for each dependency other than the main file, causing each to depend on nothing. These ! dummy rules work around errors 'make' gives if you remove header ! files without updating the 'Makefile' to match. This is typical output: --- 4201,4292 ---- ... #endif FOO ! The second and third `FOO' should be in comments, but often are not in older programs. This warning is on by default. ! `-Werror' Make all warnings into hard errors. Source code which triggers warnings will be rejected. ! `-Wsystem-headers' Issue warnings for code in system headers. These are normally unhelpful in finding bugs in your own code, therefore suppressed. If you are responsible for the system library, you may want to see them. ! `-w' Suppress all warnings, including those which GNU CPP issues by default. ! `-pedantic' ! Issue all the mandatory diagnostics listed in the C standard. ! Some of them are left out by default, since they trigger ! frequently on harmless code. ! `-pedantic-errors' Issue all the mandatory diagnostics, and make all mandatory diagnostics into errors. This includes mandatory diagnostics that ! GCC issues without `-pedantic' but treats as warnings. ! `-M' Instead of outputting the result of preprocessing, output a rule ! suitable for `make' describing the dependencies of the main source ! file. The preprocessor outputs one `make' rule containing the object file name for that source file, a colon, and the names of ! all the included files, including those coming from `-include' or ! `-imacros' command-line options. ! Unless specified explicitly (with `-MT' or `-MQ'), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is ! split into several lines using `\'-newline. The rule has no commands. ! This option does not suppress the preprocessor's debug output, ! such as `-dM'. To avoid mixing such debug output with the ! dependency rules you should explicitly specify the dependency ! output file with `-MF', or use an environment variable like ! `DEPENDENCIES_OUTPUT' (*note Environment Variables::). Debug ! output will still be sent to the regular output stream as normal. ! Passing `-M' to the driver implies `-E', and suppresses warnings ! with an implicit `-w'. ! `-MM' ! Like `-M' but do not mention header files that are found in system ! header directories, nor header files that are included, directly ! or indirectly, from such a header. This implies that the choice of angle brackets or double quotes in ! an `#include' directive does not in itself determine whether that ! header will appear in `-MM' dependency output. This is a slight change in semantics from GCC versions 3.0 and earlier. ! `-MF FILE' ! When used with `-M' or `-MM', specifies a file to write the ! dependencies to. If no `-MF' switch is given the preprocessor sends the rules to the same place it would have sent preprocessed output. ! When used with the driver options `-MD' or `-MMD', `-MF' overrides the default dependency output file. ! `-MG' ! In conjunction with an option such as `-M' requesting dependency ! generation, `-MG' assumes missing header files are generated files ! and adds them to the dependency list without raising an error. ! The dependency filename is taken directly from the `#include' ! directive without prepending any path. `-MG' also suppresses ! preprocessed output, as a missing header file renders this useless. This feature is used in automatic updating of makefiles. ! `-MP' This option instructs CPP to add a phony target for each dependency other than the main file, causing each to depend on nothing. These ! dummy rules work around errors `make' gives if you remove header ! files without updating the `Makefile' to match. This is typical output: *************** single-letter options may _not_ be group *** 4266,4701 **** test.h: ! '-MT TARGET' ! Change the target of the rule emitted by dependency generation. By default CPP takes the name of the main input file, deletes any ! directory components and any file suffix such as '.c', and appends the platform's usual object suffix. The result is the target. ! An '-MT' option will set the target to be exactly the string you specify. If you want multiple targets, you can specify them as a ! single argument to '-MT', or use multiple '-MT' options. ! For example, '-MT '$(objpfx)foo.o'' might give $(objpfx)foo.o: foo.c ! '-MQ TARGET' ! ! Same as '-MT', but it quotes any characters which are special to ! Make. '-MQ '$(objpfx)foo.o'' gives $$(objpfx)foo.o: foo.c The default target is automatically quoted, as if it were given ! with '-MQ'. ! '-MD' ! '-MD' is equivalent to '-M -MF FILE', except that '-E' is not ! implied. The driver determines FILE based on whether an '-o' ! option is given. If it is, the driver uses its argument but with a ! suffix of '.d', otherwise it takes the name of the input file, ! removes any directory components and suffix, and applies a '.d' suffix. ! If '-MD' is used in conjunction with '-E', any '-o' switch is understood to specify the dependency output file (*note -MF: ! dashMF.), but if used without '-E', each '-o' is understood to specify a target object file. ! Since '-E' is not implied, '-MD' can be used to generate a dependency output file as a side-effect of the compilation process. ! '-MMD' ! Like '-MD' except mention only user header files, not system header ! files. ! '-x c' ! '-x c++' ! '-x objective-c' ! '-x assembler-with-cpp' Specify the source language: C, C++, Objective-C, or assembly. ! This has nothing to do with standards conformance or extensions; it ! merely selects which base syntax to expect. If you give none of ! these options, cpp will deduce the language from the extension of ! the source file: '.c', '.cc', '.m', or '.S'. Some other common extensions for C++ and assembly are also recognized. If cpp does not recognize the extension, it will treat the file as C; this is the most generic mode. ! _Note:_ Previous versions of cpp accepted a '-lang' option which selected both the language and the standards conformance level. ! This option has been removed, because it conflicts with the '-l' option. ! '-std=STANDARD' ! '-ansi' Specify the standard to which the code should conform. Currently CPP knows about C and C++ standards; others may be added in the future. STANDARD may be one of: ! 'c90' ! 'c89' ! 'iso9899:1990' ! The ISO C standard from 1990. 'c90' is the customary shorthand for this version of the standard. ! The '-ansi' option is equivalent to '-std=c90'. ! 'iso9899:199409' The 1990 C standard, as amended in 1994. ! 'iso9899:1999' ! 'c99' ! 'iso9899:199x' ! 'c9x' The revised ISO C standard, published in December 1999. Before publication, this was known as C9X. ! 'iso9899:2011' ! 'c11' ! 'c1x' The revised ISO C standard, published in December 2011. Before publication, this was known as C1X. ! 'gnu90' ! 'gnu89' The 1990 C standard plus GNU extensions. This is the default. ! 'gnu99' ! 'gnu9x' The 1999 C standard plus GNU extensions. ! 'gnu11' ! 'gnu1x' The 2011 C standard plus GNU extensions. ! 'c++98' The 1998 ISO C++ standard plus amendments. ! 'gnu++98' ! The same as '-std=c++98' plus GNU extensions. This is the default for C++ code. ! '-I-' ! Split the include path. Any directories specified with '-I' ! options before '-I-' are searched only for headers requested with ! '#include "FILE"'; they are not searched for '#include '. If ! additional directories are specified with '-I' options after the ! '-I-', those directories are searched for all '#include' directives. ! In addition, '-I-' inhibits the use of the directory of the current ! file directory as the first search directory for '#include "FILE"'. *Note Search Path::. This option has been deprecated. ! '-nostdinc' Do not search the standard system directories for header files. ! Only the directories you have specified with '-I' options (and the directory of the current file, if appropriate) are searched. ! '-nostdinc++' Do not search for header files in the C++-specific standard directories, but do still search the other standard directories. (This option is used when building the C++ library.) ! '-include FILE' ! Process FILE as if '#include "file"' appeared as the first line of ! the primary source file. However, the first directory searched for ! FILE is the preprocessor's working directory _instead of_ the directory containing the main source file. If not found there, it ! is searched for in the remainder of the '#include "..."' search chain as normal. ! If multiple '-include' options are given, the files are included in ! the order they appear on the command line. ! '-imacros FILE' ! Exactly like '-include', except that any output produced by scanning FILE is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its declarations. ! All files specified by '-imacros' are processed before all files ! specified by '-include'. ! '-idirafter DIR' Search DIR for header files, but do it _after_ all directories ! specified with '-I' and the standard system directories have been exhausted. DIR is treated as a system include directory. If DIR ! begins with '=', then the '=' will be replaced by the sysroot ! prefix; see '--sysroot' and '-isysroot'. ! '-iprefix PREFIX' ! Specify PREFIX as the prefix for subsequent '-iwithprefix' options. ! If the prefix represents a directory, you should include the final ! '/'. ! '-iwithprefix DIR' ! '-iwithprefixbefore DIR' ! Append DIR to the prefix specified previously with '-iprefix', and add the resulting directory to the include search path. ! '-iwithprefixbefore' puts it in the same place '-I' would; ! '-iwithprefix' puts it where '-idirafter' would. ! '-isysroot DIR' ! This option is like the '--sysroot' option, but applies only to header files (except for Darwin targets, where it applies to both ! header files and libraries). See the '--sysroot' option for more information. ! '-imultilib DIR' Use DIR as a subdirectory of the directory containing target-specific C++ headers. ! '-isystem DIR' Search DIR for header files, after all directories specified by ! '-I' but before the standard system directories. Mark it as a system directory, so that it gets the same special treatment as is applied to the standard system directories. *Note System ! Headers::. If DIR begins with '=', then the '=' will be replaced ! by the sysroot prefix; see '--sysroot' and '-isysroot'. ! '-iquote DIR' ! Search DIR only for header files requested with '#include "FILE"'; ! they are not searched for '#include ', before all directories ! specified by '-I' and before the standard system directories. ! *Note Search Path::. If DIR begins with '=', then the '=' will be ! replaced by the sysroot prefix; see '--sysroot' and '-isysroot'. ! '-fdirectives-only' When preprocessing, handle directives, but do not expand macros. ! The option's behavior depends on the '-E' and '-fpreprocessed' options. ! With '-E', preprocessing is limited to the handling of directives ! such as '#define', '#ifdef', and '#error'. Other preprocessor ! operations, such as macro expansion and trigraph conversion are not ! performed. In addition, the '-dD' option is implicitly enabled. ! With '-fpreprocessed', predefinition of command line and most ! builtin macros is disabled. Macros such as '__LINE__', which are contextually dependent, are handled normally. This enables ! compilation of files previously preprocessed with '-E -fdirectives-only'. ! With both '-E' and '-fpreprocessed', the rules for '-fpreprocessed' ! take precedence. This enables full preprocessing of files ! previously preprocessed with '-E -fdirectives-only'. ! '-fdollars-in-identifiers' ! Accept '$' in identifiers. *Note Identifier characters::. ! '-fextended-identifiers' Accept universal character names in identifiers. This option is enabled by default for C99 (and later C standard versions) and C++. ! '-fno-canonical-system-headers' When preprocessing, do not shorten system header paths with canonicalization. ! '-fpreprocessed' Indicate to the preprocessor that the input file has already been preprocessed. This suppresses things like macro expansion, trigraph conversion, escaped newline splicing, and processing of most directives. The preprocessor still recognizes and removes ! comments, so that you can pass a file preprocessed with '-C' to the ! compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends. ! '-fpreprocessed' is implicit if the input file has one of the ! extensions '.i', '.ii' or '.mi'. These are the extensions that GCC ! uses for preprocessed files created by '-save-temps'. ! '-ftabstop=WIDTH' Set the distance between tab stops. This helps the preprocessor report correct column numbers in warnings or errors, even if tabs appear on the line. If the value is less than 1 or greater than 100, the option is ignored. The default is 8. ! '-fdebug-cpp' ! This option is only useful for debugging GCC. When used with '-E', ! dumps debugging information about location maps. Every token in ! the output is preceded by the dump of the map its location belongs ! to. The dump of the map holding the location of a token would be: ! {'P':/file/path;'F':/includer/path;'L':LINE_NUM;'C':COL_NUM;'S':SYSTEM_HEADER_P;'M':MAP_ADDRESS;'E':MACRO_EXPANSION_P,'loc':LOCATION} ! When used without '-E', this option has no effect. ! '-ftrack-macro-expansion[=LEVEL]' ! Track locations of tokens across macro expansions. This allows the compiler to emit diagnostic about the current macro expansion stack ! when a compilation error occurs in a macro expansion. Using this ! option makes the preprocessor and the compiler consume more memory. ! The LEVEL parameter can be used to choose the level of precision of ! token location tracking thus decreasing the memory consumption if ! necessary. Value '0' of LEVEL de-activates this option just as if ! no '-ftrack-macro-expansion' was present on the command line. ! Value '1' tracks tokens locations in a degraded mode for the sake ! of minimal memory overhead. In this mode all tokens resulting from ! the expansion of an argument of a function-like macro have the same ! location. Value '2' tracks tokens locations completely. This ! value is the most memory hungry. When this option is given no ! argument, the default parameter value is '2'. ! Note that '-ftrack-macro-expansion=2' is activated by default. ! '-fexec-charset=CHARSET' Set the execution character set, used for string and character constants. The default is UTF-8. CHARSET can be any encoding ! supported by the system's 'iconv' library routine. ! '-fwide-exec-charset=CHARSET' Set the wide execution character set, used for wide string and character constants. The default is UTF-32 or UTF-16, whichever ! corresponds to the width of 'wchar_t'. As with '-fexec-charset', ! CHARSET can be any encoding supported by the system's 'iconv' library routine; however, you will have problems with encodings ! that do not fit exactly in 'wchar_t'. ! '-finput-charset=CHARSET' Set the input character set, used for translation from the ! character set of the input file to the source character set used by ! GCC. If the locale does not specify, or GCC cannot get this information from the locale, the default is UTF-8. This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. CHARSET can be any encoding supported by the system's ! 'iconv' library routine. ! '-fworking-directory' Enable generation of linemarkers in the preprocessor output that will let the compiler know the current working directory at the time of preprocessing. When this option is enabled, the preprocessor will emit, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC will use this directory, when it's present in the ! preprocessed input, as the directory emitted as the current working ! directory in some debugging information formats. This option is ! implicitly enabled if debugging information is enabled, but this ! can be inhibited with the negated form '-fno-working-directory'. ! If the '-P' flag is present in the command line, this option has no ! effect, since no '#line' directives are emitted whatsoever. ! '-fno-show-column' Do not print column numbers in diagnostics. This may be necessary if diagnostics are being scanned by a program that does not ! understand the column numbers, such as 'dejagnu'. ! '-A PREDICATE=ANSWER' Make an assertion with the predicate PREDICATE and answer ANSWER. ! This form is preferred to the older form '-A PREDICATE(ANSWER)', which is still supported, because it does not use shell special characters. *Note Obsolete Features::. ! '-A -PREDICATE=ANSWER' Cancel an assertion with the predicate PREDICATE and answer ANSWER. ! '-dCHARS' ! CHARS is a sequence of one or more of the following characters, and ! must not be preceded by a space. Other characters are interpreted ! by the compiler proper, or reserved for future versions of GCC, and ! so are silently ignored. If you specify characters whose behavior ! conflicts, the result is undefined. ! 'M' ! Instead of the normal output, generate a list of '#define' directives for all the macros defined during the execution of ! the preprocessor, including predefined macros. This gives you ! a way of finding out what is predefined in your version of the ! preprocessor. Assuming you have no file 'foo.h', the command touch foo.h; cpp -dM foo.h will show all the predefined macros. ! If you use '-dM' without the '-E' option, '-dM' is interpreted ! as a synonym for '-fdump-rtl-mach'. *Note (gcc)Developer ! Options::. ! 'D' ! Like 'M' except in two respects: it does _not_ include the ! predefined macros, and it outputs _both_ the '#define' directives and the result of preprocessing. Both kinds of output go to the standard output file. ! 'N' ! Like 'D', but emit only the macro names, not their expansions. ! 'I' ! Output '#include' directives in addition to the result of preprocessing. ! 'U' ! Like 'D' except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and ! '#undef' directives are also output for macros tested but undefined at the time. ! '-P' Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. *Note Preprocessor Output::. ! '-C' Do not discard comments. All comments are passed through to the ! output file, except for comments in processed directives, which are ! deleted along with the directive. ! You should be prepared for side effects when using '-C'; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no ! longer a '#'. ! '-CC' Do not discard comments, including during macro expansion. This is ! like '-C', except that comments contained within macros are also passed through to the output file where the macro is expanded. ! In addition to the side-effects of the '-C' option, the '-CC' ! option causes all C++-style comments inside a macro to be converted ! to C-style comments. This is to prevent later use of that macro ! from inadvertently commenting out the remainder of the source line. ! The '-CC' option is generally used to support lint comments. ! '-traditional-cpp' Try to imitate the behavior of old-fashioned C preprocessors, as opposed to ISO C preprocessors. *Note Traditional Mode::. ! '-trigraphs' Process trigraph sequences. *Note Initial processing::. ! '-remap' Enable special code to work around file systems which only permit very short file names, such as MS-DOS. ! '--help' ! '--target-help' Print text describing all the command-line options instead of preprocessing anything. ! '-v' Verbose mode. Print out GNU CPP's version number at the beginning of execution, and report the final form of the include path. ! '-H' Print the name of each header file used, in addition to other normal activities. Each name is indented to show how deep in the ! '#include' stack it is. Precompiled header files are also printed, ! even if they are found to be invalid; an invalid precompiled header ! file is printed with '...x' and a valid one with '...!' . ! '-version' ! '--version' Print out GNU CPP's version number. With one dash, proceed to preprocess as normal. With two dashes, exit immediately. --- 4294,4734 ---- test.h: ! `-MT TARGET' Change the target of the rule emitted by dependency generation. By default CPP takes the name of the main input file, deletes any ! directory components and any file suffix such as `.c', and appends the platform's usual object suffix. The result is the target. ! An `-MT' option will set the target to be exactly the string you specify. If you want multiple targets, you can specify them as a ! single argument to `-MT', or use multiple `-MT' options. ! For example, `-MT '$(objpfx)foo.o'' might give $(objpfx)foo.o: foo.c ! `-MQ TARGET' ! Same as `-MT', but it quotes any characters which are special to ! Make. `-MQ '$(objpfx)foo.o'' gives $$(objpfx)foo.o: foo.c The default target is automatically quoted, as if it were given ! with `-MQ'. ! `-MD' ! `-MD' is equivalent to `-M -MF FILE', except that `-E' is not ! implied. The driver determines FILE based on whether an `-o' ! option is given. If it is, the driver uses its argument but with ! a suffix of `.d', otherwise it takes the name of the input file, ! removes any directory components and suffix, and applies a `.d' suffix. ! If `-MD' is used in conjunction with `-E', any `-o' switch is understood to specify the dependency output file (*note -MF: ! dashMF.), but if used without `-E', each `-o' is understood to specify a target object file. ! Since `-E' is not implied, `-MD' can be used to generate a dependency output file as a side-effect of the compilation process. ! `-MMD' ! Like `-MD' except mention only user header files, not system ! header files. ! `-x c' ! `-x c++' ! `-x objective-c' ! `-x assembler-with-cpp' Specify the source language: C, C++, Objective-C, or assembly. ! This has nothing to do with standards conformance or extensions; ! it merely selects which base syntax to expect. If you give none ! of these options, cpp will deduce the language from the extension ! of the source file: `.c', `.cc', `.m', or `.S'. Some other common extensions for C++ and assembly are also recognized. If cpp does not recognize the extension, it will treat the file as C; this is the most generic mode. ! _Note:_ Previous versions of cpp accepted a `-lang' option which selected both the language and the standards conformance level. ! This option has been removed, because it conflicts with the `-l' option. ! `-std=STANDARD' ! `-ansi' Specify the standard to which the code should conform. Currently CPP knows about C and C++ standards; others may be added in the future. STANDARD may be one of: ! `c90' ! `c89' ! `iso9899:1990' ! The ISO C standard from 1990. `c90' is the customary shorthand for this version of the standard. ! The `-ansi' option is equivalent to `-std=c90'. ! `iso9899:199409' The 1990 C standard, as amended in 1994. ! `iso9899:1999' ! `c99' ! `iso9899:199x' ! `c9x' The revised ISO C standard, published in December 1999. Before publication, this was known as C9X. ! `iso9899:2011' ! `c11' ! `c1x' The revised ISO C standard, published in December 2011. Before publication, this was known as C1X. ! `gnu90' ! `gnu89' The 1990 C standard plus GNU extensions. This is the default. ! `gnu99' ! `gnu9x' The 1999 C standard plus GNU extensions. ! `gnu11' ! `gnu1x' The 2011 C standard plus GNU extensions. ! `c++98' The 1998 ISO C++ standard plus amendments. ! `gnu++98' ! The same as `-std=c++98' plus GNU extensions. This is the default for C++ code. ! `-I-' ! Split the include path. Any directories specified with `-I' ! options before `-I-' are searched only for headers requested with ! `#include "FILE"'; they are not searched for `#include '. ! If additional directories are specified with `-I' options after ! the `-I-', those directories are searched for all `#include' directives. ! In addition, `-I-' inhibits the use of the directory of the current ! file directory as the first search directory for `#include "FILE"'. *Note Search Path::. This option has been deprecated. ! `-nostdinc' Do not search the standard system directories for header files. ! Only the directories you have specified with `-I' options (and the directory of the current file, if appropriate) are searched. ! `-nostdinc++' Do not search for header files in the C++-specific standard directories, but do still search the other standard directories. (This option is used when building the C++ library.) ! `-include FILE' ! Process FILE as if `#include "file"' appeared as the first line of ! the primary source file. However, the first directory searched ! for FILE is the preprocessor's working directory _instead of_ the directory containing the main source file. If not found there, it ! is searched for in the remainder of the `#include "..."' search chain as normal. ! If multiple `-include' options are given, the files are included ! in the order they appear on the command line. ! `-imacros FILE' ! Exactly like `-include', except that any output produced by scanning FILE is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its declarations. ! All files specified by `-imacros' are processed before all files ! specified by `-include'. ! `-idirafter DIR' Search DIR for header files, but do it _after_ all directories ! specified with `-I' and the standard system directories have been exhausted. DIR is treated as a system include directory. If DIR ! begins with `=', then the `=' will be replaced by the sysroot ! prefix; see `--sysroot' and `-isysroot'. ! `-iprefix PREFIX' ! Specify PREFIX as the prefix for subsequent `-iwithprefix' ! options. If the prefix represents a directory, you should include ! the final `/'. ! `-iwithprefix DIR' ! `-iwithprefixbefore DIR' ! Append DIR to the prefix specified previously with `-iprefix', and add the resulting directory to the include search path. ! `-iwithprefixbefore' puts it in the same place `-I' would; ! `-iwithprefix' puts it where `-idirafter' would. ! `-isysroot DIR' ! This option is like the `--sysroot' option, but applies only to header files (except for Darwin targets, where it applies to both ! header files and libraries). See the `--sysroot' option for more information. ! `-imultilib DIR' Use DIR as a subdirectory of the directory containing target-specific C++ headers. ! `-isystem DIR' Search DIR for header files, after all directories specified by ! `-I' but before the standard system directories. Mark it as a system directory, so that it gets the same special treatment as is applied to the standard system directories. *Note System ! Headers::. If DIR begins with `=', then the `=' will be replaced ! by the sysroot prefix; see `--sysroot' and `-isysroot'. ! `-iquote DIR' ! Search DIR only for header files requested with `#include "FILE"'; ! they are not searched for `#include ', before all ! directories specified by `-I' and before the standard system ! directories. *Note Search Path::. If DIR begins with `=', then ! the `=' will be replaced by the sysroot prefix; see `--sysroot' ! and `-isysroot'. ! `-fdirectives-only' When preprocessing, handle directives, but do not expand macros. ! The option's behavior depends on the `-E' and `-fpreprocessed' options. ! With `-E', preprocessing is limited to the handling of directives ! such as `#define', `#ifdef', and `#error'. Other preprocessor ! operations, such as macro expansion and trigraph conversion are ! not performed. In addition, the `-dD' option is implicitly ! enabled. ! With `-fpreprocessed', predefinition of command line and most ! builtin macros is disabled. Macros such as `__LINE__', which are contextually dependent, are handled normally. This enables ! compilation of files previously preprocessed with `-E -fdirectives-only'. ! With both `-E' and `-fpreprocessed', the rules for ! `-fpreprocessed' take precedence. This enables full preprocessing ! of files previously preprocessed with `-E -fdirectives-only'. ! `-fdollars-in-identifiers' ! Accept `$' in identifiers. *Note Identifier characters::. ! `-fextended-identifiers' Accept universal character names in identifiers. This option is enabled by default for C99 (and later C standard versions) and C++. ! `-fno-canonical-system-headers' When preprocessing, do not shorten system header paths with canonicalization. ! `-fpreprocessed' Indicate to the preprocessor that the input file has already been preprocessed. This suppresses things like macro expansion, trigraph conversion, escaped newline splicing, and processing of most directives. The preprocessor still recognizes and removes ! comments, so that you can pass a file preprocessed with `-C' to ! the compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends. ! `-fpreprocessed' is implicit if the input file has one of the ! extensions `.i', `.ii' or `.mi'. These are the extensions that ! GCC uses for preprocessed files created by `-save-temps'. ! `-ftabstop=WIDTH' Set the distance between tab stops. This helps the preprocessor report correct column numbers in warnings or errors, even if tabs appear on the line. If the value is less than 1 or greater than 100, the option is ignored. The default is 8. ! `-fdebug-cpp' ! This option is only useful for debugging GCC. When used with ! `-E', dumps debugging information about location maps. Every ! token in the output is preceded by the dump of the map its location ! belongs to. The dump of the map holding the location of a token ! would be: ! {`P':`/file/path';`F':`/includer/path';`L':LINE_NUM;`C':COL_NUM;`S':SYSTEM_HEADER_P;`M':MAP_ADDRESS;`E':MACRO_EXPANSION_P,`loc':LOCATION} ! When used without `-E', this option has no effect. ! `-ftrack-macro-expansion[=LEVEL]' ! Track locations of tokens across macro expansions. This allows the compiler to emit diagnostic about the current macro expansion stack ! when a compilation error occurs in a macro expansion. Using this ! option makes the preprocessor and the compiler consume more ! memory. The LEVEL parameter can be used to choose the level of ! precision of token location tracking thus decreasing the memory ! consumption if necessary. Value `0' of LEVEL de-activates this ! option just as if no `-ftrack-macro-expansion' was present on the ! command line. Value `1' tracks tokens locations in a degraded mode ! for the sake of minimal memory overhead. In this mode all tokens ! resulting from the expansion of an argument of a function-like ! macro have the same location. Value `2' tracks tokens locations ! completely. This value is the most memory hungry. When this ! option is given no argument, the default parameter value is `2'. ! Note that `-ftrack-macro-expansion=2' is activated by default. ! `-fexec-charset=CHARSET' Set the execution character set, used for string and character constants. The default is UTF-8. CHARSET can be any encoding ! supported by the system's `iconv' library routine. ! `-fwide-exec-charset=CHARSET' Set the wide execution character set, used for wide string and character constants. The default is UTF-32 or UTF-16, whichever ! corresponds to the width of `wchar_t'. As with `-fexec-charset', ! CHARSET can be any encoding supported by the system's `iconv' library routine; however, you will have problems with encodings ! that do not fit exactly in `wchar_t'. ! `-finput-charset=CHARSET' Set the input character set, used for translation from the ! character set of the input file to the source character set used ! by GCC. If the locale does not specify, or GCC cannot get this information from the locale, the default is UTF-8. This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. CHARSET can be any encoding supported by the system's ! `iconv' library routine. ! `-fworking-directory' Enable generation of linemarkers in the preprocessor output that will let the compiler know the current working directory at the time of preprocessing. When this option is enabled, the preprocessor will emit, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC will use this directory, when it's present in the ! preprocessed input, as the directory emitted as the current ! working directory in some debugging information formats. This ! option is implicitly enabled if debugging information is enabled, ! but this can be inhibited with the negated form ! `-fno-working-directory'. If the `-P' flag is present in the ! command line, this option has no effect, since no `#line' ! directives are emitted whatsoever. ! `-fno-show-column' Do not print column numbers in diagnostics. This may be necessary if diagnostics are being scanned by a program that does not ! understand the column numbers, such as `dejagnu'. ! `-A PREDICATE=ANSWER' Make an assertion with the predicate PREDICATE and answer ANSWER. ! This form is preferred to the older form `-A PREDICATE(ANSWER)', which is still supported, because it does not use shell special characters. *Note Obsolete Features::. ! `-A -PREDICATE=ANSWER' Cancel an assertion with the predicate PREDICATE and answer ANSWER. ! `-dCHARS' ! CHARS is a sequence of one or more of the following characters, ! and must not be preceded by a space. Other characters are ! interpreted by the compiler proper, or reserved for future ! versions of GCC, and so are silently ignored. If you specify ! characters whose behavior conflicts, the result is undefined. ! `M' ! Instead of the normal output, generate a list of `#define' directives for all the macros defined during the execution of ! the preprocessor, including predefined macros. This gives ! you a way of finding out what is predefined in your version ! of the preprocessor. Assuming you have no file `foo.h', the ! command touch foo.h; cpp -dM foo.h will show all the predefined macros. ! If you use `-dM' without the `-E' option, `-dM' is ! interpreted as a synonym for `-fdump-rtl-mach'. *Note ! Developer Options: (gcc)Developer Options. ! `D' ! Like `M' except in two respects: it does _not_ include the ! predefined macros, and it outputs _both_ the `#define' directives and the result of preprocessing. Both kinds of output go to the standard output file. ! `N' ! Like `D', but emit only the macro names, not their expansions. ! `I' ! Output `#include' directives in addition to the result of preprocessing. ! `U' ! Like `D' except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and ! `#undef' directives are also output for macros tested but undefined at the time. ! `-P' Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. *Note Preprocessor Output::. ! `-C' Do not discard comments. All comments are passed through to the ! output file, except for comments in processed directives, which ! are deleted along with the directive. ! You should be prepared for side effects when using `-C'; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no ! longer a `#'. ! `-CC' Do not discard comments, including during macro expansion. This is ! like `-C', except that comments contained within macros are also passed through to the output file where the macro is expanded. ! In addition to the side-effects of the `-C' option, the `-CC' ! option causes all C++-style comments inside a macro to be ! converted to C-style comments. This is to prevent later use of ! that macro from inadvertently commenting out the remainder of the ! source line. ! The `-CC' option is generally used to support lint comments. ! `-traditional-cpp' Try to imitate the behavior of old-fashioned C preprocessors, as opposed to ISO C preprocessors. *Note Traditional Mode::. ! `-trigraphs' Process trigraph sequences. *Note Initial processing::. ! `-remap' Enable special code to work around file systems which only permit very short file names, such as MS-DOS. ! `--help' ! `--target-help' Print text describing all the command-line options instead of preprocessing anything. ! `-v' Verbose mode. Print out GNU CPP's version number at the beginning of execution, and report the final form of the include path. ! `-H' Print the name of each header file used, in addition to other normal activities. Each name is indented to show how deep in the ! `#include' stack it is. Precompiled header files are also ! printed, even if they are found to be invalid; an invalid ! precompiled header file is printed with `...x' and a valid one ! with `...!' . ! `-version' ! `--version' Print out GNU CPP's version number. With one dash, proceed to preprocess as normal. With two dashes, exit immediately. *************** operates. You can use them to specify d *** 4710,4769 **** when searching for include files, or to control dependency output. Note that you can also specify places to search using options such as ! '-I', and control dependency output with options like '-M' (*note Invocation::). These take precedence over environment variables, which in turn take precedence over the configuration of GCC. ! 'CPATH' ! 'C_INCLUDE_PATH' ! 'CPLUS_INCLUDE_PATH' ! 'OBJC_INCLUDE_PATH' Each variable's value is a list of directories separated by a ! special character, much like 'PATH', in which to look for header ! files. The special character, 'PATH_SEPARATOR', is target-dependent and determined at GCC build time. For Microsoft Windows-based targets it is a semicolon, and for almost all other targets it is a colon. ! 'CPATH' specifies a list of directories to be searched as if ! specified with '-I', but after any paths given with '-I' options on ! the command line. This environment variable is used regardless of ! which language is being preprocessed. The remaining environment variables apply only when preprocessing the particular language indicated. Each specifies a list of ! directories to be searched as if specified with '-isystem', but ! after any paths given with '-isystem' options on the command line. In all these variables, an empty element instructs the compiler to ! search its current working directory. Empty elements can appear at ! the beginning or end of a path. For instance, if the value of ! 'CPATH' is ':/special/include', that has the same effect as ! '-I. -I/special/include'. See also *note Search Path::. ! 'DEPENDENCIES_OUTPUT' If this variable is set, its value specifies how to output dependencies for Make based on the non-system header files processed by the compiler. System header files are ignored in the dependency output. ! The value of 'DEPENDENCIES_OUTPUT' can be just a file name, in which case the Make rules are written to that file, guessing the target name from the source file name. Or the value can have the ! form 'FILE TARGET', in which case the rules are written to file FILE using TARGET as the target name. In other words, this environment variable is equivalent to ! combining the options '-MM' and '-MF' (*note Invocation::), with an ! optional '-MT' switch too. ! 'SUNPRO_DEPENDENCIES' ! This variable is the same as 'DEPENDENCIES_OUTPUT' (see above), ! except that system header files are not ignored, so it implies '-M' ! rather than '-MM'. However, the dependence on the main input file ! is omitted. *Note Invocation::.  File: cpp.info, Node: GNU Free Documentation License, Next: Index of Directives, Prev: Environment Variables, Up: Top --- 4743,4802 ---- when searching for include files, or to control dependency output. Note that you can also specify places to search using options such as ! `-I', and control dependency output with options like `-M' (*note Invocation::). These take precedence over environment variables, which in turn take precedence over the configuration of GCC. ! `CPATH' ! `C_INCLUDE_PATH' ! `CPLUS_INCLUDE_PATH' ! `OBJC_INCLUDE_PATH' Each variable's value is a list of directories separated by a ! special character, much like `PATH', in which to look for header ! files. The special character, `PATH_SEPARATOR', is target-dependent and determined at GCC build time. For Microsoft Windows-based targets it is a semicolon, and for almost all other targets it is a colon. ! `CPATH' specifies a list of directories to be searched as if ! specified with `-I', but after any paths given with `-I' options ! on the command line. This environment variable is used regardless ! of which language is being preprocessed. The remaining environment variables apply only when preprocessing the particular language indicated. Each specifies a list of ! directories to be searched as if specified with `-isystem', but ! after any paths given with `-isystem' options on the command line. In all these variables, an empty element instructs the compiler to ! search its current working directory. Empty elements can appear ! at the beginning or end of a path. For instance, if the value of ! `CPATH' is `:/special/include', that has the same effect as ! `-I. -I/special/include'. See also *note Search Path::. ! `DEPENDENCIES_OUTPUT' If this variable is set, its value specifies how to output dependencies for Make based on the non-system header files processed by the compiler. System header files are ignored in the dependency output. ! The value of `DEPENDENCIES_OUTPUT' can be just a file name, in which case the Make rules are written to that file, guessing the target name from the source file name. Or the value can have the ! form `FILE TARGET', in which case the rules are written to file FILE using TARGET as the target name. In other words, this environment variable is equivalent to ! combining the options `-MM' and `-MF' (*note Invocation::), with ! an optional `-MT' switch too. ! `SUNPRO_DEPENDENCIES' ! This variable is the same as `DEPENDENCIES_OUTPUT' (see above), ! except that system header files are not ignored, so it implies ! `-M' rather than `-MM'. However, the dependence on the main input ! file is omitted. *Note Invocation::.  File: cpp.info, Node: GNU Free Documentation License, Next: Index of Directives, Prev: Environment Variables, Up: Top *************** GNU Free Documentation License *** 4774,4780 **** Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 4807,4813 ---- Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU Free Documentation License *** 4799,4819 **** free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. We ! recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it can ! be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You accept ! the license if you copy, modify or distribute the work in a way ! requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with --- 4832,4852 ---- free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. ! We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it ! can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You ! accept the license if you copy, modify or distribute the work in a ! way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with *************** GNU Free Documentation License *** 4831,4842 **** regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in the ! notice that says that the Document is released under this License. ! If a section does not fit the above definition of Secondary then it ! is not allowed to be designated as Invariant. The Document may ! contain zero Invariant Sections. If the Document does not identify ! any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice --- 4864,4875 ---- regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in ! the notice that says that the Document is released under this ! License. If a section does not fit the above definition of ! Secondary then it is not allowed to be designated as Invariant. ! The Document may contain zero Invariant Sections. If the Document ! does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice *************** GNU Free Documentation License *** 4847,4873 **** A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images composed ! of pixels) generic paint programs or (for drawings) some widely ! available drawing editor, and that is suitable for input to text ! formatters or for automatic translation to a variety of formats ! suitable for input to text formatters. A copy made in an otherwise ! Transparent file format whose markup, or absence of markup, has ! been arranged to thwart or discourage subsequent modification by ! readers is not Transparent. An image format is not Transparent if ! used for any substantial amount of text. A copy that is not ! "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and standard-conforming ! simple HTML, PostScript or PDF designed for human modification. ! Examples of transparent image formats include PNG, XCF and JPG. ! Opaque formats include proprietary formats that can be read and ! edited only by proprietary word processors, SGML or XML for which ! the DTD and/or processing tools are not generally available, and ! the machine-generated HTML, PostScript or PDF produced by some word ! processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the --- 4880,4906 ---- A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images ! composed of pixels) generic paint programs or (for drawings) some ! widely available drawing editor, and that is suitable for input to ! text formatters or for automatic translation to a variety of ! formats suitable for input to text formatters. A copy made in an ! otherwise Transparent file format whose markup, or absence of ! markup, has been arranged to thwart or discourage subsequent ! modification by readers is not Transparent. An image format is ! not Transparent if used for any substantial amount of text. A ! copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and ! standard-conforming simple HTML, PostScript or PDF designed for ! human modification. Examples of transparent image formats include ! PNG, XCF and JPG. Opaque formats include proprietary formats that ! can be read and edited only by proprietary word processors, SGML or ! XML for which the DTD and/or processing tools are not generally ! available, and the machine-generated HTML, PostScript or PDF ! produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the *************** GNU Free Documentation License *** 4905,4912 **** may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow the ! conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. --- 4938,4945 ---- may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow ! the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. *************** GNU Free Documentation License *** 4920,4930 **** these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the title ! equally prominent and visible. You may add other material on the ! covers in addition. Copying with changes limited to the covers, as ! long as they preserve the title of the Document and satisfy these ! conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit --- 4953,4964 ---- these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the ! title equally prominent and visible. You may add other material ! on the covers in addition. Copying with changes limited to the ! covers, as long as they preserve the title of the Document and ! satisfy these conditions, can be treated as verbatim copying in ! other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit *************** GNU Free Documentation License *** 4932,4970 **** adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a machine-readable ! Transparent copy along with each Opaque copy, or state in or with ! each Opaque copy a computer-network location from which the general ! network-using public has access to download using public-standard ! network protocols a complete Transparent copy of the Document, free ! of added material. If you use the latter option, you must take ! reasonably prudent steps, when you begin distribution of Opaque ! copies in quantity, to ensure that this Transparent copy will ! remain thus accessible at the stated location until at least one ! year after the last time you distribute an Opaque copy (directly or ! through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of copies, ! to give them a chance to provide you with an updated version of the ! Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with the ! Modified Version filling the role of the Document, thus licensing ! distribution and modification of the Modified Version to whoever ! possesses a copy of it. In addition, you must do these things in ! the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of previous ! versions (which should, if there were any, be listed in the ! History section of the Document). You may use the same title ! as a previous version if the original publisher of that ! version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in --- 4966,5005 ---- adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a ! machine-readable Transparent copy along with each Opaque copy, or ! state in or with each Opaque copy a computer-network location from ! which the general network-using public has access to download ! using public-standard network protocols a complete Transparent ! copy of the Document, free of added material. If you use the ! latter option, you must take reasonably prudent steps, when you ! begin distribution of Opaque copies in quantity, to ensure that ! this Transparent copy will remain thus accessible at the stated ! location until at least one year after the last time you ! distribute an Opaque copy (directly or through your agents or ! retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of ! copies, to give them a chance to provide you with an updated ! version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with ! the Modified Version filling the role of the Document, thus ! licensing distribution and modification of the Modified Version to ! whoever possesses a copy of it. In addition, you must do these ! things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of ! previous versions (which should, if there were any, be listed ! in the History section of the Document). You may use the ! same title as a previous version if the original publisher of ! that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in *************** GNU Free Documentation License *** 4994,5023 **** I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on the ! Title Page. If there is no section Entitled "History" in the ! Document, create one stating the title, year, authors, and ! publisher of the Document as given on its Title Page, then add ! an item describing the Modified Version as stated in the ! previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in the ! "History" section. You may omit a network location for a work ! that was published at least four years before the Document ! itself, or if the original publisher of the version it refers ! to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the section ! all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, unaltered ! in their text and in their titles. Section numbers or the ! equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. --- 5029,5059 ---- I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on ! the Title Page. If there is no section Entitled "History" in ! the Document, create one stating the title, year, authors, ! and publisher of the Document as given on its Title Page, ! then add an item describing the Modified Version as stated in ! the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in ! the "History" section. You may omit a network location for a ! work that was published at least four years before the ! Document itself, or if the original publisher of the version ! it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the ! section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, ! unaltered in their text and in their titles. Section numbers ! or the equivalent are not considered part of the section ! titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. *************** GNU Free Documentation License *** 5030,5040 **** If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option designate ! some or all of these sections as invariant. To do this, add their ! titles to the list of Invariant Sections in the Modified Version's ! license notice. These titles must be distinct from any other ! section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various --- 5066,5076 ---- If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option ! designate some or all of these sections as invariant. To do this, ! add their titles to the list of Invariant Sections in the Modified ! Version's license notice. These titles must be distinct from any ! other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various *************** GNU Free Documentation License *** 5043,5057 **** definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end of ! the list of Cover Texts in the Modified Version. Only one passage ! of Front-Cover Text and one of Back-Cover Text may be added by (or ! through arrangements made by) any one entity. If the Document ! already includes a cover text for the same cover, previously added ! by you or by arrangement made by the same entity you are acting on ! behalf of, you may not add another; but you may replace the old ! one, on explicit permission from the previous publisher that added ! the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to --- 5079,5093 ---- definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end ! of the list of Cover Texts in the Modified Version. Only one ! passage of Front-Cover Text and one of Back-Cover Text may be ! added by (or through arrangements made by) any one entity. If the ! Document already includes a cover text for the same cover, ! previously added by you or by arrangement made by the same entity ! you are acting on behalf of, you may not add another; but you may ! replace the old one, on explicit permission from the previous ! publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to *************** GNU Free Documentation License *** 5061,5068 **** You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination all ! of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. --- 5097,5104 ---- You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination ! all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. *************** GNU Free Documentation License *** 5089,5108 **** documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the documents ! in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow this ! License in all other respects regarding verbatim copying of that ! document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of a ! storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this --- 5125,5144 ---- documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the ! documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow ! this License in all other respects regarding verbatim copying of ! that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of ! a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this *************** GNU Free Documentation License *** 5147,5154 **** However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 5183,5190 ---- However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** GNU Free Documentation License *** 5160,5192 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, receipt of a copy of some or all of the ! same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! . Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If the ! Document does not specify a version number of this License, you may ! choose any version ever published (not as a draft) by the Free ! Software Foundation. If the Document specifies that a proxy can ! decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also --- 5196,5228 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, receipt of a copy of some or all of ! the same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! `http://www.gnu.org/copyleft/'. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If ! the Document does not specify a version number of this License, ! you may choose any version ever published (not as a draft) by the ! Free Software Foundation. If the Document specifies that a proxy ! can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also *************** GNU Free Documentation License *** 5216,5221 **** --- 5252,5258 ---- site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. + ADDENDUM: How to use this License for your documents ==================================================== *************** notices just after the title page: *** 5232,5238 **** Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts --- 5269,5275 ---- Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts *************** combination of the three, merge those tw *** 5243,5251 **** situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of free ! software license, such as the GNU General Public License, to permit ! their use in free software.  File: cpp.info, Node: Index of Directives, Next: Option Index, Prev: GNU Free Documentation License, Up: Top --- 5280,5288 ---- situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of ! free software license, such as the GNU General Public License, to ! permit their use in free software.  File: cpp.info, Node: Index of Directives, Next: Option Index, Prev: GNU Free Documentation License, Up: Top *************** Index of Directives *** 5274,5281 **** * #pragma GCC dependency: Pragmas. (line 55) * #pragma GCC error: Pragmas. (line 100) * #pragma GCC poison: Pragmas. (line 67) - * #pragma GCC system_header: System Headers. (line 31) * #pragma GCC system_header <1>: Pragmas. (line 94) * #pragma GCC warning: Pragmas. (line 99) * #sccs: Other Directives. (line 6) * #unassert: Obsolete Features. (line 59) --- 5311,5318 ---- * #pragma GCC dependency: Pragmas. (line 55) * #pragma GCC error: Pragmas. (line 100) * #pragma GCC poison: Pragmas. (line 67) * #pragma GCC system_header <1>: Pragmas. (line 94) + * #pragma GCC system_header: System Headers. (line 31) * #pragma GCC warning: Pragmas. (line 99) * #sccs: Other Directives. (line 6) * #unassert: Obsolete Features. (line 59) *************** Option Index *** 5290,5385 **** ************ CPP's command-line options and environment variables are indexed here ! without any initial '-' or '--'. [index] * Menu: ! * A: Invocation. (line 566) ! * ansi: Invocation. (line 311) ! * C: Invocation. (line 624) * CPATH: Environment Variables. (line 15) * CPLUS_INCLUDE_PATH: Environment Variables. (line 17) ! * C_INCLUDE_PATH: Environment Variables. ! (line 16) ! * D: Invocation. (line 40) ! * dD: Invocation. (line 597) * DEPENDENCIES_OUTPUT: Environment Variables. ! (line 45) ! * dI: Invocation. (line 606) ! * dM: Invocation. (line 582) ! * dN: Invocation. (line 603) ! * dU: Invocation. (line 610) ! * fdebug-cpp: Invocation. (line 497) ! * fdirectives-only: Invocation. (line 446) ! * fdollars-in-identifiers: Invocation. (line 467) * fexec-charset: Invocation. (line 524) ! * fextended-identifiers: Invocation. (line 470) * finput-charset: Invocation. (line 537) ! * fno-canonical-system-headers: Invocation. (line 474) ! * fno-show-column: Invocation. (line 561) * fno-working-directory: Invocation. (line 547) ! * fpreprocessed: Invocation. (line 478) ! * ftabstop: Invocation. (line 491) * ftrack-macro-expansion: Invocation. (line 506) * fwide-exec-charset: Invocation. (line 529) * fworking-directory: Invocation. (line 547) ! * H: Invocation. (line 668) ! * help: Invocation. (line 660) ! * I: Invocation. (line 72) ! * I-: Invocation. (line 360) ! * idirafter: Invocation. (line 402) ! * imacros: Invocation. (line 393) ! * imultilib: Invocation. (line 427) ! * include: Invocation. (line 382) ! * iprefix: Invocation. (line 409) ! * iquote: Invocation. (line 439) ! * isysroot: Invocation. (line 421) ! * isystem: Invocation. (line 431) ! * iwithprefix: Invocation. (line 415) ! * iwithprefixbefore: Invocation. (line 415) ! * M: Invocation. (line 181) ! * MD: Invocation. (line 272) ! * MF: Invocation. (line 216) ! * MG: Invocation. (line 225) ! * MM: Invocation. (line 206) ! * MMD: Invocation. (line 288) ! * MP: Invocation. (line 235) ! * MQ: Invocation. (line 262) ! * MT: Invocation. (line 247) ! * nostdinc: Invocation. (line 372) ! * nostdinc++: Invocation. (line 377) ! * o: Invocation. (line 83) * OBJC_INCLUDE_PATH: Environment Variables. (line 18) ! * P: Invocation. (line 617) ! * pedantic: Invocation. (line 171) ! * pedantic-errors: Invocation. (line 176) ! * remap: Invocation. (line 655) ! * std=: Invocation. (line 311) * SUNPRO_DEPENDENCIES: Environment Variables. ! (line 61) ! * target-help: Invocation. (line 660) ! * traditional-cpp: Invocation. (line 648) ! * trigraphs: Invocation. (line 652) ! * U: Invocation. (line 63) ! * undef: Invocation. (line 67) ! * v: Invocation. (line 664) ! * version: Invocation. (line 676) ! * w: Invocation. (line 167) ! * Wall: Invocation. (line 89) ! * Wcomment: Invocation. (line 97) ! * Wcomments: Invocation. (line 97) ! * Wendif-labels: Invocation. (line 144) ! * Werror: Invocation. (line 157) ! * Wsystem-headers: Invocation. (line 161) ! * Wtraditional: Invocation. (line 114) ! * Wtrigraphs: Invocation. (line 102) ! * Wundef: Invocation. (line 120) ! * Wunused-macros: Invocation. (line 125) ! * x: Invocation. (line 295)  File: cpp.info, Node: Concept Index, Prev: Option Index, Up: Top --- 5327,5422 ---- ************ CPP's command-line options and environment variables are indexed here ! without any initial `-' or `--'. [index] * Menu: ! * A: Invocation. (line 567) ! * ansi: Invocation. (line 308) ! * C: Invocation. (line 626) ! * C_INCLUDE_PATH: Environment Variables. ! (line 16) * CPATH: Environment Variables. (line 15) * CPLUS_INCLUDE_PATH: Environment Variables. (line 17) ! * D: Invocation. (line 39) ! * dD: Invocation. (line 599) * DEPENDENCIES_OUTPUT: Environment Variables. ! (line 44) ! * dI: Invocation. (line 608) ! * dM: Invocation. (line 583) ! * dN: Invocation. (line 605) ! * dU: Invocation. (line 612) ! * fdebug-cpp: Invocation. (line 496) ! * fdirectives-only: Invocation. (line 444) ! * fdollars-in-identifiers: Invocation. (line 466) * fexec-charset: Invocation. (line 524) ! * fextended-identifiers: Invocation. (line 469) * finput-charset: Invocation. (line 537) ! * fno-canonical-system-headers: Invocation. (line 473) ! * fno-show-column: Invocation. (line 562) * fno-working-directory: Invocation. (line 547) ! * fpreprocessed: Invocation. (line 477) ! * ftabstop: Invocation. (line 490) * ftrack-macro-expansion: Invocation. (line 506) * fwide-exec-charset: Invocation. (line 529) * fworking-directory: Invocation. (line 547) ! * H: Invocation. (line 671) ! * help: Invocation. (line 663) ! * I: Invocation. (line 71) ! * I-: Invocation. (line 357) ! * idirafter: Invocation. (line 399) ! * imacros: Invocation. (line 390) ! * imultilib: Invocation. (line 424) ! * include: Invocation. (line 379) ! * iprefix: Invocation. (line 406) ! * iquote: Invocation. (line 436) ! * isysroot: Invocation. (line 418) ! * isystem: Invocation. (line 428) ! * iwithprefix: Invocation. (line 412) ! * iwithprefixbefore: Invocation. (line 412) ! * M: Invocation. (line 180) ! * MD: Invocation. (line 269) ! * MF: Invocation. (line 215) ! * MG: Invocation. (line 224) ! * MM: Invocation. (line 205) ! * MMD: Invocation. (line 285) ! * MP: Invocation. (line 234) ! * MQ: Invocation. (line 260) ! * MT: Invocation. (line 246) ! * nostdinc: Invocation. (line 369) ! * nostdinc++: Invocation. (line 374) ! * o: Invocation. (line 82) * OBJC_INCLUDE_PATH: Environment Variables. (line 18) ! * P: Invocation. (line 619) ! * pedantic: Invocation. (line 170) ! * pedantic-errors: Invocation. (line 175) ! * remap: Invocation. (line 658) ! * std=: Invocation. (line 308) * SUNPRO_DEPENDENCIES: Environment Variables. ! (line 60) ! * target-help: Invocation. (line 663) ! * traditional-cpp: Invocation. (line 651) ! * trigraphs: Invocation. (line 655) ! * U: Invocation. (line 62) ! * undef: Invocation. (line 66) ! * v: Invocation. (line 667) ! * version: Invocation. (line 680) ! * w: Invocation. (line 166) ! * Wall: Invocation. (line 88) ! * Wcomment: Invocation. (line 96) ! * Wcomments: Invocation. (line 96) ! * Wendif-labels: Invocation. (line 143) ! * Werror: Invocation. (line 156) ! * Wsystem-headers: Invocation. (line 160) ! * Wtraditional: Invocation. (line 113) ! * Wtrigraphs: Invocation. (line 101) ! * Wundef: Invocation. (line 119) ! * Wunused-macros: Invocation. (line 124) ! * x: Invocation. (line 292)  File: cpp.info, Node: Concept Index, Prev: Option Index, Up: Top *************** Concept Index *** 5393,5399 **** * # operator: Stringification. (line 6) * ## operator: Concatenation. (line 6) * _Pragma: Pragmas. (line 25) ! * alternative tokens: Tokenization. (line 104) * arguments: Macro Arguments. (line 6) * arguments in macro definitions: Macro Arguments. (line 6) * assertions: Obsolete Features. (line 13) --- 5430,5436 ---- * # operator: Stringification. (line 6) * ## operator: Concatenation. (line 6) * _Pragma: Pragmas. (line 25) ! * alternative tokens: Tokenization. (line 105) * arguments: Macro Arguments. (line 6) * arguments in macro definitions: Macro Arguments. (line 6) * assertions: Obsolete Features. (line 13) *************** Concept Index *** 5401,5407 **** * backslash-newline: Initial processing. (line 61) * block comments: Initial processing. (line 77) * C++ named operators: C++ Named Operators. (line 6) ! * character constants: Tokenization. (line 83) * character set, execution: Invocation. (line 524) * character set, input: Invocation. (line 537) * character set, wide execution: Invocation. (line 529) --- 5438,5444 ---- * backslash-newline: Initial processing. (line 61) * block comments: Initial processing. (line 77) * C++ named operators: C++ Named Operators. (line 6) ! * character constants: Tokenization. (line 84) * character set, execution: Invocation. (line 524) * character set, input: Invocation. (line 537) * character set, wide execution: Invocation. (line 529) *************** Concept Index *** 5418,5431 **** * controlling macro: Once-Only Headers. (line 35) * defined: Defined. (line 6) * dependencies for make as output: Environment Variables. ! (line 46) ! * dependencies for make as output <1>: Environment Variables. ! (line 62) ! * dependencies, make: Invocation. (line 181) * diagnostic: Diagnostics. (line 6) * differences from previous versions: Differences from previous versions. (line 6) ! * digraphs: Tokenization. (line 104) * directive line: The preprocessing language. (line 6) * directive name: The preprocessing language. --- 5455,5466 ---- * controlling macro: Once-Only Headers. (line 35) * defined: Defined. (line 6) * dependencies for make as output: Environment Variables. ! (line 45) ! * dependencies, make: Invocation. (line 180) * diagnostic: Diagnostics. (line 6) * differences from previous versions: Differences from previous versions. (line 6) ! * digraphs: Tokenization. (line 105) * directive line: The preprocessing language. (line 6) * directive name: The preprocessing language. *************** Concept Index *** 5443,5450 **** * grouping options: Invocation. (line 34) * guard macro: Once-Only Headers. (line 35) * header file: Header Files. (line 6) ! * header file names: Tokenization. (line 83) ! * identifiers: Tokenization. (line 33) * implementation limits: Implementation limits. (line 6) * implementation-defined behavior: Implementation-defined behavior. --- 5478,5485 ---- * grouping options: Invocation. (line 34) * guard macro: Once-Only Headers. (line 35) * header file: Header Files. (line 6) ! * header file names: Tokenization. (line 84) ! * identifiers: Tokenization. (line 34) * implementation limits: Implementation limits. (line 6) * implementation-defined behavior: Implementation-defined behavior. *************** Concept Index *** 5462,5478 **** * macros in include: Computed Includes. (line 6) * macros with arguments: Macro Arguments. (line 6) * macros with variable arguments: Variadic Macros. (line 6) ! * make: Invocation. (line 181) * manifest constants: Object-like Macros. (line 6) * named operators: C++ Named Operators. (line 6) * newlines in macro arguments: Newlines in Arguments. (line 6) * null directive: Other Directives. (line 15) ! * numbers: Tokenization. (line 59) * object-like macro: Object-like Macros. (line 6) ! * options: Invocation. (line 39) * options, grouping: Invocation. (line 34) ! * other tokens: Tokenization. (line 118) * output format: Preprocessor Output. (line 12) * overriding a header file: Wrapper Headers. (line 6) * parentheses in macro bodies: Operator Precedence Problems. --- 5497,5513 ---- * macros in include: Computed Includes. (line 6) * macros with arguments: Macro Arguments. (line 6) * macros with variable arguments: Variadic Macros. (line 6) ! * make: Invocation. (line 180) * manifest constants: Object-like Macros. (line 6) * named operators: C++ Named Operators. (line 6) * newlines in macro arguments: Newlines in Arguments. (line 6) * null directive: Other Directives. (line 15) ! * numbers: Tokenization. (line 60) * object-like macro: Object-like Macros. (line 6) ! * options: Invocation. (line 38) * options, grouping: Invocation. (line 34) ! * other tokens: Tokenization. (line 119) * output format: Preprocessor Output. (line 12) * overriding a header file: Wrapper Headers. (line 6) * parentheses in macro bodies: Operator Precedence Problems. *************** Concept Index *** 5484,5494 **** * predicates: Obsolete Features. (line 26) * preprocessing directives: The preprocessing language. (line 6) ! * preprocessing numbers: Tokenization. (line 59) * preprocessing tokens: Tokenization. (line 6) * prescan of macro arguments: Argument Prescan. (line 6) * problems with macros: Macro Pitfalls. (line 6) ! * punctuators: Tokenization. (line 104) * redefining macros: Undefining and Redefining Macros. (line 6) * repeated inclusion: Once-Only Headers. (line 6) --- 5519,5529 ---- * predicates: Obsolete Features. (line 26) * preprocessing directives: The preprocessing language. (line 6) ! * preprocessing numbers: Tokenization. (line 60) * preprocessing tokens: Tokenization. (line 6) * prescan of macro arguments: Argument Prescan. (line 6) * problems with macros: Macro Pitfalls. (line 6) ! * punctuators: Tokenization. (line 105) * redefining macros: Undefining and Redefining Macros. (line 6) * repeated inclusion: Once-Only Headers. (line 6) *************** Concept Index *** 5504,5515 **** (line 6) * standard predefined macros.: Standard Predefined Macros. (line 6) ! * string constants: Tokenization. (line 83) ! * string literals: Tokenization. (line 83) * stringification: Stringification. (line 6) * symbolic constants: Object-like Macros. (line 6) - * system header files: Header Files. (line 13) * system header files <1>: System Headers. (line 6) * system-specific predefined macros: System-specific Predefined Macros. (line 6) * testing predicates: Obsolete Features. (line 37) --- 5539,5550 ---- (line 6) * standard predefined macros.: Standard Predefined Macros. (line 6) ! * string constants: Tokenization. (line 84) ! * string literals: Tokenization. (line 84) * stringification: Stringification. (line 6) * symbolic constants: Object-like Macros. (line 6) * system header files <1>: System Headers. (line 6) + * system header files: Header Files. (line 13) * system-specific predefined macros: System-specific Predefined Macros. (line 6) * testing predicates: Obsolete Features. (line 37) *************** Concept Index *** 5529,5607 ****  Tag Table: ! Node: Top945 ! Node: Overview3549 ! Node: Character sets6383 ! Ref: Character sets-Footnote-18538 ! Node: Initial processing8719 ! Ref: trigraphs10278 ! Node: Tokenization14478 ! Ref: Tokenization-Footnote-121507 ! Node: The preprocessing language21618 ! Node: Header Files24497 ! Node: Include Syntax26413 ! Node: Include Operation28050 ! Node: Search Path29898 ! Node: Once-Only Headers33099 ! Node: Alternatives to Wrapper #ifndef34758 ! Node: Computed Includes36500 ! Node: Wrapper Headers39658 ! Node: System Headers42081 ! Node: Macros44131 ! Node: Object-like Macros45272 ! Node: Function-like Macros48862 ! Node: Macro Arguments50478 ! Node: Stringification54621 ! Node: Concatenation57827 ! Node: Variadic Macros60935 ! Node: Predefined Macros65722 ! Node: Standard Predefined Macros66310 ! Node: Common Predefined Macros72311 ! Node: System-specific Predefined Macros92383 ! Node: C++ Named Operators94406 ! Node: Undefining and Redefining Macros95370 ! Node: Directives Within Macro Arguments97468 ! Node: Macro Pitfalls99016 ! Node: Misnesting99549 ! Node: Operator Precedence Problems100661 ! Node: Swallowing the Semicolon102527 ! Node: Duplication of Side Effects104550 ! Node: Self-Referential Macros106733 ! Node: Argument Prescan109142 ! Node: Newlines in Arguments112897 ! Node: Conditionals113848 ! Node: Conditional Uses115677 ! Node: Conditional Syntax117035 ! Node: Ifdef117355 ! Node: If120512 ! Node: Defined122816 ! Node: Else124097 ! Node: Elif124667 ! Node: Deleted Code125956 ! Node: Diagnostics127203 ! Node: Line Control128752 ! Node: Pragmas132527 ! Node: Other Directives137281 ! Node: Preprocessor Output138331 ! Node: Traditional Mode141529 ! Node: Traditional lexical analysis142587 ! Node: Traditional macros145090 ! Node: Traditional miscellany148891 ! Node: Traditional warnings149887 ! Node: Implementation Details152084 ! Node: Implementation-defined behavior152705 ! Ref: Identifier characters153455 ! Node: Implementation limits156344 ! Node: Obsolete Features159017 ! Node: Differences from previous versions161904 ! Node: Invocation166106 ! Ref: Wtrigraphs170558 ! Ref: dashMF175335 ! Ref: fdollars-in-identifiers185077 ! Node: Environment Variables194880 ! Node: GNU Free Documentation License197846 ! Node: Index of Directives222991 ! Node: Option Index225071 ! Node: Concept Index231474  End Tag Table --- 5564,5642 ----  Tag Table: ! Node: Top996 ! Node: Overview3601 ! Node: Character sets6434 ! Ref: Character sets-Footnote-18591 ! Node: Initial processing8772 ! Ref: trigraphs10331 ! Node: Tokenization14533 ! Ref: Tokenization-Footnote-121564 ! Node: The preprocessing language21675 ! Node: Header Files24553 ! Node: Include Syntax26469 ! Node: Include Operation28106 ! Node: Search Path29954 ! Node: Once-Only Headers33155 ! Node: Alternatives to Wrapper #ifndef34814 ! Node: Computed Includes36557 ! Node: Wrapper Headers39715 ! Node: System Headers42141 ! Node: Macros44191 ! Node: Object-like Macros45332 ! Node: Function-like Macros48922 ! Node: Macro Arguments50538 ! Node: Stringification54683 ! Node: Concatenation57889 ! Node: Variadic Macros60997 ! Node: Predefined Macros65784 ! Node: Standard Predefined Macros66372 ! Node: Common Predefined Macros72375 ! Node: System-specific Predefined Macros92463 ! Node: C++ Named Operators94486 ! Node: Undefining and Redefining Macros95450 ! Node: Directives Within Macro Arguments97554 ! Node: Macro Pitfalls99102 ! Node: Misnesting99635 ! Node: Operator Precedence Problems100747 ! Node: Swallowing the Semicolon102613 ! Node: Duplication of Side Effects104636 ! Node: Self-Referential Macros106819 ! Node: Argument Prescan109228 ! Node: Newlines in Arguments112982 ! Node: Conditionals113933 ! Node: Conditional Uses115763 ! Node: Conditional Syntax117121 ! Node: Ifdef117441 ! Node: If120607 ! Node: Defined122911 ! Node: Else124194 ! Node: Elif124764 ! Node: Deleted Code126053 ! Node: Diagnostics127300 ! Node: Line Control128847 ! Node: Pragmas132651 ! Node: Other Directives137407 ! Node: Preprocessor Output138457 ! Node: Traditional Mode141658 ! Node: Traditional lexical analysis142716 ! Node: Traditional macros145219 ! Node: Traditional miscellany149021 ! Node: Traditional warnings150018 ! Node: Implementation Details152215 ! Node: Implementation-defined behavior152836 ! Ref: Identifier characters153588 ! Node: Implementation limits156472 ! Node: Obsolete Features159146 ! Node: Differences from previous versions162034 ! Node: Invocation166242 ! Ref: Wtrigraphs170694 ! Ref: dashMF175469 ! Ref: fdollars-in-identifiers185200 ! Node: Environment Variables195045 ! Node: GNU Free Documentation License198011 ! Node: Index of Directives223175 ! Node: Option Index225255 ! Node: Concept Index231658  End Tag Table diff -Nrcpad gcc-6.3.0/gcc/doc/cpp.texi gcc-6.4.0/gcc/doc/cpp.texi *** gcc-6.3.0/gcc/doc/cpp.texi Thu Jan 21 00:59:54 2016 --- gcc-6.4.0/gcc/doc/cpp.texi Tue Jul 4 07:15:57 2017 *************** *** 10,16 **** @copying @c man begin COPYRIGHT ! Copyright @copyright{} 1987-2016 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 --- 10,16 ---- @copying @c man begin COPYRIGHT ! Copyright @copyright{} 1987-2017 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 diff -Nrcpad gcc-6.3.0/gcc/doc/cppinternals.info gcc-6.4.0/gcc/doc/cppinternals.info *** gcc-6.3.0/gcc/doc/cppinternals.info Wed Dec 21 09:34:05 2016 --- gcc-6.4.0/gcc/doc/cppinternals.info Tue Jul 4 09:27:46 2017 *************** *** 1,12 **** ! This is cppinternals.info, produced by makeinfo version 6.1 from ! cppinternals.texi. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * Cpplib: (cppinternals). Cpplib internals. END-INFO-DIR-ENTRY ! This file documents the internals of the GNU C Preprocessor. Copyright (C) 2000-2016 Free Software Foundation, Inc. --- 1,12 ---- ! This is doc/cppinternals.info, produced by makeinfo version 4.13 from ! /space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/doc/cppinternals.texi. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * Cpplib: (cppinternals). Cpplib internals. END-INFO-DIR-ENTRY ! This file documents the internals of the GNU C Preprocessor. Copyright (C) 2000-2016 Free Software Foundation, Inc. *************** preserved on all copies. *** 16,23 **** Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also ! that the entire resulting derived work is distributed under the terms of ! a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified --- 16,23 ---- Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also ! that the entire resulting derived work is distributed under the terms ! of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified *************** preprocessor in previous versions of GCC *** 46,54 **** as the fundamental unit. This brief manual documents the internals of cpplib, and explains ! some of the tricky issues. It is intended that, along with the comments ! in the source code, a reasonably competent C programmer should be able ! to figure out what the code is doing, and why things have been implemented the way they have. * Menu: --- 46,54 ---- as the fundamental unit. This brief manual documents the internals of cpplib, and explains ! some of the tricky issues. It is intended that, along with the ! comments in the source code, a reasonably competent C programmer should ! be able to figure out what the code is doing, and why things have been implemented the way they have. * Menu: *************** File: cppinternals.info, Node: Conventi *** 69,85 **** Conventions *********** ! cpplib has two interfaces--one is exposed internally only, and the other ! is for both internal and external use. The convention is that functions and types that are exposed to ! multiple files internally are prefixed with '_cpp_', and are to be found ! in the file 'internal.h'. Functions and types exposed to external ! clients are in 'cpplib.h', and prefixed with 'cpp_'. For historical reasons this is no longer quite true, but we should strive to stick to it. ! We are striving to reduce the information exposed in 'cpplib.h' to the bare minimum necessary, and then to keep it there. This makes clear exactly what external clients are entitled to assume, and allows us to change internals in the future without worrying whether library clients --- 69,85 ---- Conventions *********** ! cpplib has two interfaces--one is exposed internally only, and the ! other is for both internal and external use. The convention is that functions and types that are exposed to ! multiple files internally are prefixed with `_cpp_', and are to be ! found in the file `internal.h'. Functions and types exposed to external ! clients are in `cpplib.h', and prefixed with `cpp_'. For historical reasons this is no longer quite true, but we should strive to stick to it. ! We are striving to reduce the information exposed in `cpplib.h' to the bare minimum necessary, and then to keep it there. This makes clear exactly what external clients are entitled to assume, and allows us to change internals in the future without worrying whether library clients *************** The Lexer *** 95,101 **** Overview ======== ! The lexer is contained in the file 'lex.c'. It is a hand-coded lexer, and not implemented as a state machine. It can understand C, C++ and Objective-C source code, and has been extended to allow reasonably successful preprocessing of assembly language. The lexer does not make --- 95,101 ---- Overview ======== ! The lexer is contained in the file `lex.c'. It is a hand-coded lexer, and not implemented as a state machine. It can understand C, C++ and Objective-C source code, and has been extended to allow reasonably successful preprocessing of assembly language. The lexer does not make *************** them as they are encountered in a single *** 104,120 **** returns preprocessing tokens individually, not a line at a time. It is mostly transparent to users of the library, since the library's ! interface for obtaining the next token, 'cpp_get_token', takes care of lexing new tokens, handling directives, and expanding macros as necessary. However, the lexer does expose some functionality so that clients of the library can easily spell a given token, such as ! 'cpp_spell_token' and 'cpp_token_len'. These functions are useful when generating diagnostics, and for emitting the preprocessed output. Lexing a token ============== ! Lexing of an individual token is handled by '_cpp_lex_direct' and its subroutines. In its current form the code is quite complicated, with read ahead characters and such-like, since it strives to not step back in the character stream in preparation for handling non-ASCII file --- 104,120 ---- returns preprocessing tokens individually, not a line at a time. It is mostly transparent to users of the library, since the library's ! interface for obtaining the next token, `cpp_get_token', takes care of lexing new tokens, handling directives, and expanding macros as necessary. However, the lexer does expose some functionality so that clients of the library can easily spell a given token, such as ! `cpp_spell_token' and `cpp_token_len'. These functions are useful when generating diagnostics, and for emitting the preprocessed output. Lexing a token ============== ! Lexing of an individual token is handled by `_cpp_lex_direct' and its subroutines. In its current form the code is quite complicated, with read ahead characters and such-like, since it strives to not step back in the character stream in preparation for handling non-ASCII file *************** encodings. The current plan is to conve *** 122,187 **** before processing them. This complexity is therefore unnecessary and will be removed, so I'll not discuss it further here. ! The job of '_cpp_lex_direct' is simply to lex a token. It is not responsible for issues like directive handling, returning lookahead tokens directly, multiple-include optimization, or conditional block ! skipping. It necessarily has a minor ro^le to play in memory management ! of lexed lines. I discuss these issues in a separate section (*note ! Lexing a line::). The lexer places the token it lexes into storage pointed to by the ! variable 'cur_token', and then increments it. This variable is important for correct diagnostic positioning. Unless a specific line and column are passed to the diagnostic routines, they will examine the ! 'line' and 'col' values of the token just before the location that ! 'cur_token' points to, and use that location to report the diagnostic. The lexer does not consider whitespace to be a token in its own right. If whitespace (other than a new line) precedes a token, it sets ! the 'PREV_WHITE' bit in the token's flags. Each token has its 'line' ! and 'col' variables set to the line and column of the first character of ! the token. This line number is the line number in the translation unit, ! and can be converted to a source (file, line) pair using the line map ! code. ! The first token on a logical, i.e. unescaped, line has the flag 'BOL' ! set for beginning-of-line. This flag is intended for internal use, both ! to distinguish a '#' that begins a directive from one that doesn't, and ! to generate a call-back to clients that want to be notified about the ! start of every non-directive line with tokens on it. Clients cannot ! reliably determine this for themselves: the first token might be a ! macro, and the tokens of a macro expansion do not have the 'BOL' flag ! set. The macro expansion may even be empty, and the next token on the ! line certainly won't have the 'BOL' flag set. New lines are treated specially; exactly how the lexer handles them is context-dependent. The C standard mandates that directives are terminated by the first unescaped newline character, even if it appears in the middle of a macro expansion. Therefore, if the state variable ! 'in_directive' is set, the lexer returns a 'CPP_EOF' token, which is ! normally used to indicate end-of-file, to indicate end-of-directive. In ! a directive a 'CPP_EOF' token never means end-of-file. Conveniently, if ! the caller was 'collect_args', it already handles 'CPP_EOF' as if it ! were end-of-file, and reports an error about an unterminated macro ! argument list. The C standard also specifies that a new line in the middle of the arguments to a macro is treated as whitespace. This white space is important in case the macro argument is stringified. The state variable ! 'parsing_args' is nonzero when the preprocessor is collecting the arguments to a macro call. It is set to 1 when looking for the opening parenthesis to a function-like macro, and 2 when collecting the actual arguments up to the closing parenthesis, since these two cases need to be distinguished sometimes. One such time is here: the lexer sets the ! 'PREV_WHITE' flag of a token if it meets a new line when 'parsing_args' is set to 2. It doesn't set it if it meets a new line when ! 'parsing_args' is 1, since then code like #define foo() bar foo baz ! would be output with an erroneous space before 'baz': foo baz --- 122,187 ---- before processing them. This complexity is therefore unnecessary and will be removed, so I'll not discuss it further here. ! The job of `_cpp_lex_direct' is simply to lex a token. It is not responsible for issues like directive handling, returning lookahead tokens directly, multiple-include optimization, or conditional block ! skipping. It necessarily has a minor ro^le to play in memory ! management of lexed lines. I discuss these issues in a separate section ! (*note Lexing a line::). The lexer places the token it lexes into storage pointed to by the ! variable `cur_token', and then increments it. This variable is important for correct diagnostic positioning. Unless a specific line and column are passed to the diagnostic routines, they will examine the ! `line' and `col' values of the token just before the location that ! `cur_token' points to, and use that location to report the diagnostic. The lexer does not consider whitespace to be a token in its own right. If whitespace (other than a new line) precedes a token, it sets ! the `PREV_WHITE' bit in the token's flags. Each token has its `line' ! and `col' variables set to the line and column of the first character ! of the token. This line number is the line number in the translation ! unit, and can be converted to a source (file, line) pair using the line ! map code. ! The first token on a logical, i.e. unescaped, line has the flag ! `BOL' set for beginning-of-line. This flag is intended for internal ! use, both to distinguish a `#' that begins a directive from one that ! doesn't, and to generate a call-back to clients that want to be ! notified about the start of every non-directive line with tokens on it. ! Clients cannot reliably determine this for themselves: the first token ! might be a macro, and the tokens of a macro expansion do not have the ! `BOL' flag set. The macro expansion may even be empty, and the next ! token on the line certainly won't have the `BOL' flag set. New lines are treated specially; exactly how the lexer handles them is context-dependent. The C standard mandates that directives are terminated by the first unescaped newline character, even if it appears in the middle of a macro expansion. Therefore, if the state variable ! `in_directive' is set, the lexer returns a `CPP_EOF' token, which is ! normally used to indicate end-of-file, to indicate end-of-directive. ! In a directive a `CPP_EOF' token never means end-of-file. ! Conveniently, if the caller was `collect_args', it already handles ! `CPP_EOF' as if it were end-of-file, and reports an error about an ! unterminated macro argument list. The C standard also specifies that a new line in the middle of the arguments to a macro is treated as whitespace. This white space is important in case the macro argument is stringified. The state variable ! `parsing_args' is nonzero when the preprocessor is collecting the arguments to a macro call. It is set to 1 when looking for the opening parenthesis to a function-like macro, and 2 when collecting the actual arguments up to the closing parenthesis, since these two cases need to be distinguished sometimes. One such time is here: the lexer sets the ! `PREV_WHITE' flag of a token if it meets a new line when `parsing_args' is set to 2. It doesn't set it if it meets a new line when ! `parsing_args' is 1, since then code like #define foo() bar foo baz ! would be output with an erroneous space before `baz': foo baz *************** would be output with an erroneous space *** 190,276 **** correct in the preprocessor; there are plenty of tests in the testsuite for corner cases like this. ! The lexer is written to treat each of '\r', '\n', '\r\n' and '\n\r' as a single new line indicator. This allows it to transparently preprocess MS-DOS, Macintosh and Unix files without their needing to pass through a special filter beforehand. ! We also decided to treat a backslash, either '\' or the trigraph ! '??/', separated from one of the above newline indicators by non-comment ! whitespace only, as intending to escape the newline. It tends to be a ! typing mistake, and cannot reasonably be mistaken for anything else in ! any of the C-family grammars. Since handling it this way is not ! strictly conforming to the ISO standard, the library issues a warning ! wherever it encounters it. Handling newlines like this is made simpler by doing it in one place ! only. The function 'handle_newline' takes care of all newline ! characters, and 'skip_escaped_newlines' takes care of arbitrarily long ! sequences of escaped newlines, deferring to 'handle_newline' to handle the newlines themselves. The most painful aspect of lexing ISO-standard C and C++ is handling trigraphs and backlash-escaped newlines. Trigraphs are processed before any interpretation of the meaning of a character is made, and unfortunately there is a trigraph representation for a backslash, so it ! is possible for the trigraph '??/' to introduce an escaped newline. Escaped newlines are tedious because theoretically they can occur ! anywhere--between the '+' and '=' of the '+=' token, within the ! characters of an identifier, and even between the '*' and '/' that terminates a comment. Moreover, you cannot be sure there is just one--there might be an arbitrarily long sequence of them. ! So, for example, the routine that lexes a number, 'parse_number', cannot assume that it can scan forwards until the first non-number ! character and be done with it, because this could be the '\' introducing ! an escaped newline, or the '?' introducing the trigraph sequence that ! represents the '\' of an escaped newline. If it encounters a '?' or ! '\', it calls 'skip_escaped_newlines' to skip over any potential escaped ! newlines before checking whether the number has been finished. ! Similarly code in the main body of '_cpp_lex_direct' cannot simply ! check for a '=' after a '+' character to determine whether it has a '+=' ! token; it needs to be prepared for an escaped newline of some sort. ! Such cases use the function 'get_effective_char', which returns the ! first character after any intervening escaped newlines. The lexer needs to keep track of the correct column position, ! including counting tabs as specified by the '-ftabstop=' option. This should be done even within C-style comments; they can appear in the middle of a line, and we want to report diagnostics in the correct position for text appearing after the end of the comment. ! Some identifiers, such as '__VA_ARGS__' and poisoned identifiers, may ! be invalid and require a diagnostic. However, if they appear in a macro ! expansion we don't want to complain with each use of the macro. It is ! therefore best to catch them during the lexing stage, in ! 'parse_identifier'. In both cases, whether a diagnostic is needed or not is dependent upon the lexer's state. For example, we don't want to issue a diagnostic for re-poisoning a poisoned identifier, or for using ! '__VA_ARGS__' in the expansion of a variable-argument macro. Therefore ! 'parse_identifier' makes use of state flags to determine whether a diagnostic is appropriate. Since we change state on a per-token basis, and don't lex whole lines at a time, this is not a problem. Another place where state flags are used to change behavior is whilst ! lexing header names. Normally, a '<' would be lexed as a single token. ! After a '#include' directive, though, it should be lexed as a single ! token as far as the nearest '>' character. Note that we don't allow the ! terminators of header names to be escaped; the first '"' or '>' terminates the header name. Interpretation of some character sequences depends upon whether we are lexing C, C++ or Objective-C, and on the revision of the standard in ! force. For example, '::' is a single token in C++, but in C it is two ! separate ':' tokens and almost certainly a syntax error. Such cases are ! handled by '_cpp_lex_direct' based upon command-line flags stored in the ! 'cpp_options' structure. Once a token has been lexed, it leads an independent existence. The spelling of numbers, identifiers and strings is copied to permanent storage from the original input buffer, so a token remains valid and ! correct even if its source buffer is freed with '_cpp_pop_buffer'. The storage holding the spellings of such tokens remains until the client program calls cpp_destroy, probably at the end of the translation unit. --- 190,277 ---- correct in the preprocessor; there are plenty of tests in the testsuite for corner cases like this. ! The lexer is written to treat each of `\r', `\n', `\r\n' and `\n\r' as a single new line indicator. This allows it to transparently preprocess MS-DOS, Macintosh and Unix files without their needing to pass through a special filter beforehand. ! We also decided to treat a backslash, either `\' or the trigraph ! `??/', separated from one of the above newline indicators by ! non-comment whitespace only, as intending to escape the newline. It ! tends to be a typing mistake, and cannot reasonably be mistaken for ! anything else in any of the C-family grammars. Since handling it this ! way is not strictly conforming to the ISO standard, the library issues a ! warning wherever it encounters it. Handling newlines like this is made simpler by doing it in one place ! only. The function `handle_newline' takes care of all newline ! characters, and `skip_escaped_newlines' takes care of arbitrarily long ! sequences of escaped newlines, deferring to `handle_newline' to handle the newlines themselves. The most painful aspect of lexing ISO-standard C and C++ is handling trigraphs and backlash-escaped newlines. Trigraphs are processed before any interpretation of the meaning of a character is made, and unfortunately there is a trigraph representation for a backslash, so it ! is possible for the trigraph `??/' to introduce an escaped newline. Escaped newlines are tedious because theoretically they can occur ! anywhere--between the `+' and `=' of the `+=' token, within the ! characters of an identifier, and even between the `*' and `/' that terminates a comment. Moreover, you cannot be sure there is just one--there might be an arbitrarily long sequence of them. ! So, for example, the routine that lexes a number, `parse_number', cannot assume that it can scan forwards until the first non-number ! character and be done with it, because this could be the `\' ! introducing an escaped newline, or the `?' introducing the trigraph ! sequence that represents the `\' of an escaped newline. If it ! encounters a `?' or `\', it calls `skip_escaped_newlines' to skip over ! any potential escaped newlines before checking whether the number has ! been finished. ! Similarly code in the main body of `_cpp_lex_direct' cannot simply ! check for a `=' after a `+' character to determine whether it has a ! `+=' token; it needs to be prepared for an escaped newline of some ! sort. Such cases use the function `get_effective_char', which returns ! the first character after any intervening escaped newlines. The lexer needs to keep track of the correct column position, ! including counting tabs as specified by the `-ftabstop=' option. This should be done even within C-style comments; they can appear in the middle of a line, and we want to report diagnostics in the correct position for text appearing after the end of the comment. ! Some identifiers, such as `__VA_ARGS__' and poisoned identifiers, ! may be invalid and require a diagnostic. However, if they appear in a ! macro expansion we don't want to complain with each use of the macro. ! It is therefore best to catch them during the lexing stage, in ! `parse_identifier'. In both cases, whether a diagnostic is needed or not is dependent upon the lexer's state. For example, we don't want to issue a diagnostic for re-poisoning a poisoned identifier, or for using ! `__VA_ARGS__' in the expansion of a variable-argument macro. Therefore ! `parse_identifier' makes use of state flags to determine whether a diagnostic is appropriate. Since we change state on a per-token basis, and don't lex whole lines at a time, this is not a problem. Another place where state flags are used to change behavior is whilst ! lexing header names. Normally, a `<' would be lexed as a single token. ! After a `#include' directive, though, it should be lexed as a single ! token as far as the nearest `>' character. Note that we don't allow ! the terminators of header names to be escaped; the first `"' or `>' terminates the header name. Interpretation of some character sequences depends upon whether we are lexing C, C++ or Objective-C, and on the revision of the standard in ! force. For example, `::' is a single token in C++, but in C it is two ! separate `:' tokens and almost certainly a syntax error. Such cases ! are handled by `_cpp_lex_direct' based upon command-line flags stored ! in the `cpp_options' structure. Once a token has been lexed, it leads an independent existence. The spelling of numbers, identifiers and strings is copied to permanent storage from the original input buffer, so a token remains valid and ! correct even if its source buffer is freed with `_cpp_pop_buffer'. The storage holding the spellings of such tokens remains until the client program calls cpp_destroy, probably at the end of the translation unit. *************** to cpplib itself internally. *** 287,295 **** token stream. For example, after the name of a function-like macro, it wants to check the next token to see if it is an opening parenthesis. Another example is that, after reading the first few tokens of a ! '#pragma' directive and not recognizing it as a registered pragma, it wants to backtrack and allow the user-defined handler for unknown ! pragmas to access the full '#pragma' token stream. The stand-alone preprocessor wants to be able to test the current token with the previous one to see if a space needs to be inserted to preserve their separate tokenization upon re-lexing (paste avoidance), so it needs to --- 288,296 ---- token stream. For example, after the name of a function-like macro, it wants to check the next token to see if it is an opening parenthesis. Another example is that, after reading the first few tokens of a ! `#pragma' directive and not recognizing it as a registered pragma, it wants to backtrack and allow the user-defined handler for unknown ! pragmas to access the full `#pragma' token stream. The stand-alone preprocessor wants to be able to test the current token with the previous one to see if a space needs to be inserted to preserve their separate tokenization upon re-lexing (paste avoidance), so it needs to *************** to jump back to a prior position in that *** 302,309 **** preprocessor lex all tokens on a line consecutively into a token buffer, which I call a "token run", and when meeting an unescaped new line (newlines within comments do not count either), to start lexing back at ! the beginning of the run. Note that we do _not_ lex a line of tokens at ! once; if we did that 'parse_identifier' would not have state flags available to warn about invalid identifiers (*note Invalid identifiers::). --- 303,310 ---- preprocessor lex all tokens on a line consecutively into a token buffer, which I call a "token run", and when meeting an unescaped new line (newlines within comments do not count either), to start lexing back at ! the beginning of the run. Note that we do _not_ lex a line of tokens ! at once; if we did that `parse_identifier' would not have state flags available to warn about invalid identifiers (*note Invalid identifiers::). *************** identifiers::). *** 311,335 **** line is valid, but since each logical line overwrites the tokens of the previous line, tokens from prior lines are unavailable. In particular, since a directive only occupies a single logical line, this means that ! the directive handlers like the '#pragma' handler can jump around in the ! directive's tokens if necessary. Two issues remain: what about tokens that arise from macro ! expansions, and what happens when we have a long line that overflows the ! token run? Since we promise clients that we preserve the validity of pointers that we have already returned for tokens that appeared earlier in the ! line, we cannot reallocate the run. Instead, on overflow it is expanded ! by chaining a new token run on to the end of the existing one. The tokens forming a macro's replacement list are collected by the ! '#define' handler, and placed in storage that is only freed by ! 'cpp_destroy'. So if a macro is expanded in the line of tokens, the pointers to the tokens of its expansion that are returned will always remain valid. However, macros are a little trickier than that, since they give rise to three sources of fresh tokens. They are the built-in ! macros like '__LINE__', and the '#' and '##' operators for stringification and token pasting. I handled this by allocating space for these tokens from the lexer's token run chain. This means they automatically receive the same lifetime guarantees as lexed tokens, and --- 312,336 ---- line is valid, but since each logical line overwrites the tokens of the previous line, tokens from prior lines are unavailable. In particular, since a directive only occupies a single logical line, this means that ! the directive handlers like the `#pragma' handler can jump around in ! the directive's tokens if necessary. Two issues remain: what about tokens that arise from macro ! expansions, and what happens when we have a long line that overflows ! the token run? Since we promise clients that we preserve the validity of pointers that we have already returned for tokens that appeared earlier in the ! line, we cannot reallocate the run. Instead, on overflow it is ! expanded by chaining a new token run on to the end of the existing one. The tokens forming a macro's replacement list are collected by the ! `#define' handler, and placed in storage that is only freed by ! `cpp_destroy'. So if a macro is expanded in the line of tokens, the pointers to the tokens of its expansion that are returned will always remain valid. However, macros are a little trickier than that, since they give rise to three sources of fresh tokens. They are the built-in ! macros like `__LINE__', and the `#' and `##' operators for stringification and token pasting. I handled this by allocating space for these tokens from the lexer's token run chain. This means they automatically receive the same lifetime guarantees as lexed tokens, and *************** management issues, but not all. The ope *** 340,359 **** function-like macro name might lie on a different line, and the front ends definitely want the ability to look ahead past the end of the current line. So cpplib only moves back to the start of the token run ! at the end of a line if the variable 'keep_tokens' is zero. Line-buffering is quite natural for the preprocessor, and as a result the only time cpplib needs to increment this variable is whilst looking for the opening parenthesis to, and reading the arguments of, a ! function-like macro. In the near future cpplib will export an interface ! to increment and decrement this variable, so that clients can share full ! control over the lifetime of token pointers too. ! The routine '_cpp_lex_token' handles moving to new token runs, ! calling '_cpp_lex_direct' to lex new tokens, or returning previously-lexed tokens if we stepped back in the token stream. It also ! checks each token for the 'BOL' flag, which might indicate a directive that needs to be handled, or require a start-of-line call-back to be ! made. '_cpp_lex_token' also handles skipping over tokens in failed conditional blocks, and invalidates the control macro of the multiple-include optimization if a token was successfully lexed outside a directive. In other words, its callers do not need to concern --- 341,360 ---- function-like macro name might lie on a different line, and the front ends definitely want the ability to look ahead past the end of the current line. So cpplib only moves back to the start of the token run ! at the end of a line if the variable `keep_tokens' is zero. Line-buffering is quite natural for the preprocessor, and as a result the only time cpplib needs to increment this variable is whilst looking for the opening parenthesis to, and reading the arguments of, a ! function-like macro. In the near future cpplib will export an ! interface to increment and decrement this variable, so that clients can ! share full control over the lifetime of token pointers too. ! The routine `_cpp_lex_token' handles moving to new token runs, ! calling `_cpp_lex_direct' to lex new tokens, or returning previously-lexed tokens if we stepped back in the token stream. It also ! checks each token for the `BOL' flag, which might indicate a directive that needs to be handled, or require a start-of-line call-back to be ! made. `_cpp_lex_token' also handles skipping over tokens in failed conditional blocks, and invalidates the control macro of the multiple-include optimization if a token was successfully lexed outside a directive. In other words, its callers do not need to concern *************** Hash Nodes *** 367,376 **** When cpplib encounters an "identifier", it generates a hash code for it and stores it in the hash table. By "identifier" we mean tokens with ! type 'CPP_NAME'; this includes identifiers in the usual C sense, as well ! as keywords, directive names, macro names and so on. For example, all ! of 'pragma', 'int', 'foo' and '__GNUC__' are identifiers and hashed when ! lexed. Each node in the hash table contain various information about the identifier it represents. For example, its length and type. At any one --- 368,377 ---- When cpplib encounters an "identifier", it generates a hash code for it and stores it in the hash table. By "identifier" we mean tokens with ! type `CPP_NAME'; this includes identifiers in the usual C sense, as ! well as keywords, directive names, macro names and so on. For example, ! all of `pragma', `int', `foo' and `__GNUC__' are identifiers and hashed ! when lexed. Each node in the hash table contain various information about the identifier it represents. For example, its length and type. At any one *************** time, each identifier falls into exactly *** 379,424 **** * Macros These have been declared to be macros, either on the command line ! or with '#define'. A few, such as '__TIME__' are built-ins entered ! in the hash table during initialization. The hash node for a ! normal macro points to a structure with more information about the ! macro, such as whether it is function-like, how many arguments it ! takes, and its expansion. Built-in macros are flagged as special, ! and instead contain an enum indicating which of the various ! built-in macros it is. * Assertions ! Assertions are in a separate namespace to macros. To enforce this, ! cpp actually prepends a '#' character before hashing and entering ! it in the hash table. An assertion's node points to a chain of ! answers to that assertion. * Void Everything else falls into this category--an identifier that is not currently a macro, or a macro that has since been undefined with ! '#undef'. When preprocessing C++, this category also includes the named ! operators, such as 'xor'. In expressions these behave like the operators they represent, but in contexts where the spelling of a token matters they are spelt differently. This spelling distinction is relevant when they are operands of the stringizing ! and pasting macro operators '#' and '##'. Named operator hash nodes are flagged, both to catch the spelling distinction and to prevent them from being defined as macros. The same identifiers share the same hash node. Since each identifier token, after lexing, contains a pointer to its hash node, this is used to provide rapid lookup of various information. For example, when ! parsing a '#define' statement, CPP flags each argument's identifier hash ! node with the index of that argument. This makes duplicated argument ! checking an O(1) operation for each argument. Similarly, for each ! identifier in the macro's expansion, lookup to see if it is an argument, ! and which argument it is, is also an O(1) operation. Further, each ! directive name, such as 'endif', has an associated directive enum stored ! in its hash node, so that directive lookup is also O(1).  File: cppinternals.info, Node: Macro Expansion, Next: Token Spacing, Prev: Hash Nodes, Up: Top --- 380,425 ---- * Macros These have been declared to be macros, either on the command line ! or with `#define'. A few, such as `__TIME__' are built-ins ! entered in the hash table during initialization. The hash node ! for a normal macro points to a structure with more information ! about the macro, such as whether it is function-like, how many ! arguments it takes, and its expansion. Built-in macros are ! flagged as special, and instead contain an enum indicating which ! of the various built-in macros it is. * Assertions ! Assertions are in a separate namespace to macros. To enforce ! this, cpp actually prepends a `#' character before hashing and ! entering it in the hash table. An assertion's node points to a ! chain of answers to that assertion. * Void Everything else falls into this category--an identifier that is not currently a macro, or a macro that has since been undefined with ! `#undef'. When preprocessing C++, this category also includes the named ! operators, such as `xor'. In expressions these behave like the operators they represent, but in contexts where the spelling of a token matters they are spelt differently. This spelling distinction is relevant when they are operands of the stringizing ! and pasting macro operators `#' and `##'. Named operator hash nodes are flagged, both to catch the spelling distinction and to prevent them from being defined as macros. The same identifiers share the same hash node. Since each identifier token, after lexing, contains a pointer to its hash node, this is used to provide rapid lookup of various information. For example, when ! parsing a `#define' statement, CPP flags each argument's identifier ! hash node with the index of that argument. This makes duplicated ! argument checking an O(1) operation for each argument. Similarly, for ! each identifier in the macro's expansion, lookup to see if it is an ! argument, and which argument it is, is also an O(1) operation. Further, ! each directive name, such as `endif', has an associated directive enum ! stored in its hash node, so that directive lookup is also O(1).  File: cppinternals.info, Node: Macro Expansion, Next: Token Spacing, Prev: Hash Nodes, Up: Top *************** and situations that render what you thou *** 431,459 **** the preprocessor's expansion algorithm wrong in quite subtle ways. I strongly recommend you have a good grasp of how the C and C++ ! standards require macros to be expanded before diving into this section, ! let alone the code!. If you don't have a clear mental picture of how ! things like nested macro expansion, stringification and token pasting ! are supposed to work, damage to your sanity can quickly result. Internal representation of macros ================================= The preprocessor stores macro expansions in tokenized form. This saves ! repeated lexing passes during expansion, at the cost of a small increase ! in memory consumption on average. The tokens are stored contiguously in ! memory, so a pointer to the first one and a token count is all you need ! to get the replacement list of a macro. If the macro is a function-like macro the preprocessor also stores its parameters, in the form of an ordered list of pointers to the hash table entry of each parameter's identifier. Further, in the macro's stored expansion each occurrence of a parameter is replaced with a ! special token of type 'CPP_MACRO_ARG'. Each such token holds the index ! of the parameter it represents in the parameter list, which allows rapid ! replacement of parameters with their arguments during expansion. Despite this optimization it is still necessary to store the original ! parameters to the macro, both for dumping with e.g., '-dD', and to warn about non-trivial macro redefinitions when the parameter names have changed. --- 432,460 ---- the preprocessor's expansion algorithm wrong in quite subtle ways. I strongly recommend you have a good grasp of how the C and C++ ! standards require macros to be expanded before diving into this ! section, let alone the code!. If you don't have a clear mental picture ! of how things like nested macro expansion, stringification and token ! pasting are supposed to work, damage to your sanity can quickly result. Internal representation of macros ================================= The preprocessor stores macro expansions in tokenized form. This saves ! repeated lexing passes during expansion, at the cost of a small ! increase in memory consumption on average. The tokens are stored ! contiguously in memory, so a pointer to the first one and a token count ! is all you need to get the replacement list of a macro. If the macro is a function-like macro the preprocessor also stores its parameters, in the form of an ordered list of pointers to the hash table entry of each parameter's identifier. Further, in the macro's stored expansion each occurrence of a parameter is replaced with a ! special token of type `CPP_MACRO_ARG'. Each such token holds the index ! of the parameter it represents in the parameter list, which allows ! rapid replacement of parameters with their arguments during expansion. Despite this optimization it is still necessary to store the original ! parameters to the macro, both for dumping with e.g., `-dD', and to warn about non-trivial macro redefinitions when the parameter names have changed. *************** Macro expansion overview *** 461,516 **** ======================== The preprocessor maintains a "context stack", implemented as a linked ! list of 'cpp_context' structures, which together represent the macro ! expansion state at any one time. The 'struct cpp_reader' member ! variable 'context' points to the current top of this stack. The top normally holds the unexpanded replacement list of the innermost macro under expansion, except when cpplib is about to pre-expand an argument, in which case it holds that argument's unexpanded tokens. When there are no macros under expansion, cpplib is in "base ! context". All contexts other than the base context contain a contiguous ! list of tokens delimited by a starting and ending token. When not in ! base context, cpplib obtains the next token from the list of the top ! context. If there are no tokens left in the list, it pops that context ! off the stack, and subsequent ones if necessary, until an unexhausted ! context is found or it returns to base context. In base context, cpplib ! reads tokens directly from the lexer. If it encounters an identifier that is both a macro and enabled for expansion, cpplib prepares to push a new context for that macro on the ! stack by calling the routine 'enter_macro_context'. When this routine returns, the new context will contain the unexpanded tokens of the replacement list of that macro. In the case of function-like macros, ! 'enter_macro_context' also replaces any parameters in the replacement ! list, stored as 'CPP_MACRO_ARG' tokens, with the appropriate macro argument. If the standard requires that the parameter be replaced with its expanded argument, the argument will have been fully macro expanded first. ! 'enter_macro_context' also handles special macros like '__LINE__'. Although these macros expand to a single token which cannot contain any ! further macros, for reasons of token spacing (*note Token Spacing::) and ! simplicity of implementation, cpplib handles these special macros by ! pushing a context containing just that one token. ! The final thing that 'enter_macro_context' does before returning is ! to mark the macro disabled for expansion (except for special macros like ! '__TIME__'). The macro is re-enabled when its context is later popped ! from the context stack, as described above. This strict ordering ! ensures that a macro is disabled whilst its expansion is being scanned, ! but that it is _not_ disabled whilst any arguments to it are being ! expanded. Scanning the replacement list for macros to expand ================================================== ! The C standard states that, after any parameters have been replaced with ! their possibly-expanded arguments, the replacement list is scanned for ! nested macros. Further, any identifiers in the replacement list that ! are not expanded during this scan are never again eligible for expansion ! in the future, if the reason they were not expanded is that the macro in ! question was disabled. Clearly this latter condition can only apply to tokens resulting from argument pre-expansion. Other tokens never have an opportunity to be --- 462,517 ---- ======================== The preprocessor maintains a "context stack", implemented as a linked ! list of `cpp_context' structures, which together represent the macro ! expansion state at any one time. The `struct cpp_reader' member ! variable `context' points to the current top of this stack. The top normally holds the unexpanded replacement list of the innermost macro under expansion, except when cpplib is about to pre-expand an argument, in which case it holds that argument's unexpanded tokens. When there are no macros under expansion, cpplib is in "base ! context". All contexts other than the base context contain a ! contiguous list of tokens delimited by a starting and ending token. ! When not in base context, cpplib obtains the next token from the list ! of the top context. If there are no tokens left in the list, it pops ! that context off the stack, and subsequent ones if necessary, until an ! unexhausted context is found or it returns to base context. In base ! context, cpplib reads tokens directly from the lexer. If it encounters an identifier that is both a macro and enabled for expansion, cpplib prepares to push a new context for that macro on the ! stack by calling the routine `enter_macro_context'. When this routine returns, the new context will contain the unexpanded tokens of the replacement list of that macro. In the case of function-like macros, ! `enter_macro_context' also replaces any parameters in the replacement ! list, stored as `CPP_MACRO_ARG' tokens, with the appropriate macro argument. If the standard requires that the parameter be replaced with its expanded argument, the argument will have been fully macro expanded first. ! `enter_macro_context' also handles special macros like `__LINE__'. Although these macros expand to a single token which cannot contain any ! further macros, for reasons of token spacing (*note Token Spacing::) ! and simplicity of implementation, cpplib handles these special macros ! by pushing a context containing just that one token. ! The final thing that `enter_macro_context' does before returning is ! to mark the macro disabled for expansion (except for special macros ! like `__TIME__'). The macro is re-enabled when its context is later ! popped from the context stack, as described above. This strict ! ordering ensures that a macro is disabled whilst its expansion is being ! scanned, but that it is _not_ disabled whilst any arguments to it are ! being expanded. Scanning the replacement list for macros to expand ================================================== ! The C standard states that, after any parameters have been replaced ! with their possibly-expanded arguments, the replacement list is scanned ! for nested macros. Further, any identifiers in the replacement list ! that are not expanded during this scan are never again eligible for ! expansion in the future, if the reason they were not expanded is that ! the macro in question was disabled. Clearly this latter condition can only apply to tokens resulting from argument pre-expansion. Other tokens never have an opportunity to be *************** looking for the _next_ token do we pop i *** 529,555 **** lower context. This makes backing up by one token easy, but more importantly ensures that the macro corresponding to the current context is still disabled when we are considering the last token of its ! replacement list for expansion (or indeed expanding it). As an example, ! which illustrates many of the points above, consider #define foo(x) bar x foo(foo) (2) ! which fully expands to 'bar foo (2)'. During pre-expansion of the ! argument, 'foo' does not expand even though the macro is enabled, since it has no following parenthesis [pre-expansion of an argument only uses tokens from that argument; it cannot take tokens from whatever follows ! the macro invocation]. This still leaves the argument token 'foo' eligible for future expansion. Then, when re-scanning after argument ! replacement, the token 'foo' is rejected for expansion, and marked ! ineligible for future expansion, since the macro is now disabled. It is ! disabled because the replacement list 'bar foo' of the macro is still on ! the context stack. If instead the algorithm looked for an opening parenthesis first and then tested whether the macro were disabled it would be subtly wrong. ! In the example above, the replacement list of 'foo' would be popped in ! the process of finding the parenthesis, re-enabling 'foo' and expanding it a second time. Looking for a function-like macro's opening parenthesis --- 530,556 ---- lower context. This makes backing up by one token easy, but more importantly ensures that the macro corresponding to the current context is still disabled when we are considering the last token of its ! replacement list for expansion (or indeed expanding it). As an ! example, which illustrates many of the points above, consider #define foo(x) bar x foo(foo) (2) ! which fully expands to `bar foo (2)'. During pre-expansion of the ! argument, `foo' does not expand even though the macro is enabled, since it has no following parenthesis [pre-expansion of an argument only uses tokens from that argument; it cannot take tokens from whatever follows ! the macro invocation]. This still leaves the argument token `foo' eligible for future expansion. Then, when re-scanning after argument ! replacement, the token `foo' is rejected for expansion, and marked ! ineligible for future expansion, since the macro is now disabled. It ! is disabled because the replacement list `bar foo' of the macro is ! still on the context stack. If instead the algorithm looked for an opening parenthesis first and then tested whether the macro were disabled it would be subtly wrong. ! In the example above, the replacement list of `foo' would be popped in ! the process of finding the parenthesis, re-enabling `foo' and expanding it a second time. Looking for a function-like macro's opening parenthesis *************** Function-like macros only expand when im *** 559,576 **** parenthesis. To do this cpplib needs to temporarily disable macros and read the next token. Unfortunately, because of spacing issues (*note Token Spacing::), there can be fake padding tokens in-between, and if ! the next real token is not a parenthesis cpplib needs to be able to back ! up that one token as well as retain the information in any intervening ! padding tokens. Backing up more than one token when macros are involved is not permitted by cpplib, because in general it might involve issues like restoring popped contexts onto the context stack, which are too hard. ! Instead, searching for the parenthesis is handled by a special function, ! 'funlike_invocation_p', which remembers padding information as it reads ! tokens. If the next real token is not an opening parenthesis, it backs ! up that one token, and then pushes an extra context just containing the ! padding information if necessary. Marking tokens ineligible for future expansion ============================================== --- 560,577 ---- parenthesis. To do this cpplib needs to temporarily disable macros and read the next token. Unfortunately, because of spacing issues (*note Token Spacing::), there can be fake padding tokens in-between, and if ! the next real token is not a parenthesis cpplib needs to be able to ! back up that one token as well as retain the information in any ! intervening padding tokens. Backing up more than one token when macros are involved is not permitted by cpplib, because in general it might involve issues like restoring popped contexts onto the context stack, which are too hard. ! Instead, searching for the parenthesis is handled by a special ! function, `funlike_invocation_p', which remembers padding information ! as it reads tokens. If the next real token is not an opening ! parenthesis, it backs up that one token, and then pushes an extra ! context just containing the padding information if necessary. Marking tokens ineligible for future expansion ============================================== *************** Marking tokens ineligible for future exp *** 578,589 **** As discussed above, cpplib needs a way of marking tokens as unexpandable. Since the tokens cpplib handles are read-only once they have been lexed, it instead makes a copy of the token and adds the flag ! 'NO_EXPAND' to the copy. For efficiency and to simplify memory management by avoiding having to remember to free these tokens, they are allocated as temporary tokens from the lexer's current token run (*note Lexing a line::) using the ! function '_cpp_temp_token'. The tokens are then re-used once the current line of tokens has been read in. This might sound unsafe. However, tokens runs are not re-used at the --- 579,590 ---- As discussed above, cpplib needs a way of marking tokens as unexpandable. Since the tokens cpplib handles are read-only once they have been lexed, it instead makes a copy of the token and adds the flag ! `NO_EXPAND' to the copy. For efficiency and to simplify memory management by avoiding having to remember to free these tokens, they are allocated as temporary tokens from the lexer's current token run (*note Lexing a line::) using the ! function `_cpp_temp_token'. The tokens are then re-used once the current line of tokens has been read in. This might sound unsafe. However, tokens runs are not re-used at the *************** both for aesthetic reasons and because i *** 618,637 **** still try to abuse the preprocessor for things like Fortran source and Makefiles. ! For now, just notice that when tokens are added (or removed, as shown ! by the 'EMPTY' example) from the original lexed token stream, we need to ! check for accidental token pasting. We call this "paste avoidance". ! Token addition and removal can only occur because of macro expansion, ! but accidental pasting can occur in many places: both before and after ! each macro replacement, each argument replacement, and additionally each ! token created by the '#' and '##' operators. ! Look at how the preprocessor gets whitespace output correct normally. ! The 'cpp_token' structure contains a flags byte, and one of those flags ! is 'PREV_WHITE'. This is flagged by the lexer, and indicates that the ! token was preceded by whitespace of some form other than a new line. ! The stand-alone preprocessor can use this flag to decide whether to ! insert a space between tokens in the output. Now consider the result of the following macro expansion: --- 619,638 ---- still try to abuse the preprocessor for things like Fortran source and Makefiles. ! For now, just notice that when tokens are added (or removed, as ! shown by the `EMPTY' example) from the original lexed token stream, we ! need to check for accidental token pasting. We call this "paste ! avoidance". Token addition and removal can only occur because of macro ! expansion, but accidental pasting can occur in many places: both before ! and after each macro replacement, each argument replacement, and ! additionally each token created by the `#' and `##' operators. ! Look at how the preprocessor gets whitespace output correct ! normally. The `cpp_token' structure contains a flags byte, and one of ! those flags is `PREV_WHITE'. This is flagged by the lexer, and ! indicates that the token was preceded by whitespace of some form other ! than a new line. The stand-alone preprocessor can use this flag to ! decide whether to insert a space between tokens in the output. Now consider the result of the following macro expansion: *************** insert a space between tokens in the out *** 639,677 **** sum = add (1,2, 3); ==> sum = 1 + 2 +3; ! The interesting thing here is that the tokens '1' and '2' are output ! with a preceding space, and '3' is output without a preceding space, but ! when lexed none of these tokens had that property. Careful ! consideration reveals that '1' gets its preceding whitespace from the ! space preceding 'add' in the macro invocation, _not_ replacement list. ! '2' gets its whitespace from the space preceding the parameter 'y' in ! the macro replacement list, and '3' has no preceding space because ! parameter 'z' has none in the replacement list. Once lexed, tokens are effectively fixed and cannot be altered, since pointers to them might be held in many places, in particular by in-progress macro expansions. So instead of modifying the two tokens ! above, the preprocessor inserts a special token, which I call a "padding ! token", into the token stream to indicate that spacing of the subsequent ! token is special. The preprocessor inserts padding tokens in front of ! every macro expansion and expanded macro argument. These point to a ! "source token" from which the subsequent real token should inherit its ! spacing. In the above example, the source tokens are 'add' in the macro ! invocation, and 'y' and 'z' in the macro replacement list, respectively. ! It is quite easy to get multiple padding tokens in a row, for example ! if a macro's first replacement token expands straight into another ! macro. #define foo bar #define bar baz [foo] ==> [baz] ! Here, two padding tokens are generated with sources the 'foo' token ! between the brackets, and the 'bar' token from foo's replacement list, ! respectively. Clearly the first padding token is the one to use, so the ! output code should contain a rule that the first padding token in a sequence is the one that matters. But what if a macro expansion is left? Adjusting the above example --- 640,679 ---- sum = add (1,2, 3); ==> sum = 1 + 2 +3; ! The interesting thing here is that the tokens `1' and `2' are output ! with a preceding space, and `3' is output without a preceding space, ! but when lexed none of these tokens had that property. Careful ! consideration reveals that `1' gets its preceding whitespace from the ! space preceding `add' in the macro invocation, _not_ replacement list. ! `2' gets its whitespace from the space preceding the parameter `y' in ! the macro replacement list, and `3' has no preceding space because ! parameter `z' has none in the replacement list. Once lexed, tokens are effectively fixed and cannot be altered, since pointers to them might be held in many places, in particular by in-progress macro expansions. So instead of modifying the two tokens ! above, the preprocessor inserts a special token, which I call a ! "padding token", into the token stream to indicate that spacing of the ! subsequent token is special. The preprocessor inserts padding tokens ! in front of every macro expansion and expanded macro argument. These ! point to a "source token" from which the subsequent real token should ! inherit its spacing. In the above example, the source tokens are `add' ! in the macro invocation, and `y' and `z' in the macro replacement list, ! respectively. ! It is quite easy to get multiple padding tokens in a row, for ! example if a macro's first replacement token expands straight into ! another macro. #define foo bar #define bar baz [foo] ==> [baz] ! Here, two padding tokens are generated with sources the `foo' token ! between the brackets, and the `bar' token from foo's replacement list, ! respectively. Clearly the first padding token is the one to use, so ! the output code should contain a rule that the first padding token in a sequence is the one that matters. But what if a macro expansion is left? Adjusting the above example *************** slightly: *** 683,695 **** [foo] EMPTY; ==> [ baz] ; ! As shown, now there should be a space before 'baz' and the semicolon in the output. ! The rules we decided above fail for 'baz': we generate three padding ! tokens, one per macro invocation, before the token 'baz'. We would then ! have it take its spacing from the first of these, which carries source ! token 'foo' with no leading space. It is vital that cpplib get spacing correct in these examples since any of these macro expansions could be stringified, where spacing --- 685,697 ---- [foo] EMPTY; ==> [ baz] ; ! As shown, now there should be a space before `baz' and the semicolon in the output. ! The rules we decided above fail for `baz': we generate three padding ! tokens, one per macro invocation, before the token `baz'. We would ! then have it take its spacing from the first of these, which carries ! source token `foo' with no leading space. It is vital that cpplib get spacing correct in these examples since any of these macro expansions could be stringified, where spacing *************** matters. *** 697,707 **** So, this demonstrates that not just entering macro and argument expansions, but leaving them requires special handling too. I made ! cpplib insert a padding token with a 'NULL' source token when leaving macro expansions, as well as after each replaced argument in a macro's replacement list. It also inserts appropriate padding tokens on either ! side of tokens created by the '#' and '##' operators. I expanded the ! rule so that, if we see a padding token with a 'NULL' source token, _and_ that source token has no leading space, then we behave as if we have seen no padding tokens at all. A quick check shows this rule will then get the above example correct as well. --- 699,709 ---- So, this demonstrates that not just entering macro and argument expansions, but leaving them requires special handling too. I made ! cpplib insert a padding token with a `NULL' source token when leaving macro expansions, as well as after each replaced argument in a macro's replacement list. It also inserts appropriate padding tokens on either ! side of tokens created by the `#' and `##' operators. I expanded the ! rule so that, if we see a padding token with a `NULL' source token, _and_ that source token has no leading space, then we behave as if we have seen no padding tokens at all. A quick check shows this rule will then get the above example correct as well. *************** implementation of paste avoidance easy: *** 713,719 **** preprocessor is fixing up spacing because of padding tokens, and it turns out that no space is needed, it has to take the extra step to check that a space is not needed after all to avoid an accidental paste. ! The function 'cpp_avoid_paste' advises whether a space is required between two consecutive tokens. To avoid excessive spacing, it tries hard to only require a space if one is likely to be necessary, but for reasons of efficiency it is slightly conservative and might recommend a --- 715,721 ---- preprocessor is fixing up spacing because of padding tokens, and it turns out that no space is needed, it has to take the extra step to check that a space is not needed after all to avoid an accidental paste. ! The function `cpp_avoid_paste' advises whether a space is required between two consecutive tokens. To avoid excessive spacing, it tries hard to only require a space if one is likely to be necessary, but for reasons of efficiency it is slightly conservative and might recommend a *************** There are three reasonable requirements *** 732,737 **** --- 734,740 ---- the line number of a token passed to it: * The source line it was lexed on. + * The line it is output on. This can be different to the line it was lexed on if, for example, there are intervening escaped newlines or C-style comments. For example: *************** the line number of a token passed to it: *** 746,759 **** name, or possibly the line of the closing parenthesis in the case of function-like macro expansion. ! The 'cpp_token' structure contains 'line' and 'col' members. The lexer fills these in with the line and column of the first character of the token. Consequently, but maybe unexpectedly, a token from the replacement list of a macro expansion carries the location of the token ! within the '#define' directive, because cpplib expands a macro by returning pointers to the tokens in its replacement list. The current ! implementation of cpplib assigns tokens created from built-in macros and ! the '#' and '##' operators the location of the most recently lexed token. This is a because they are allocated from the lexer's token runs, and because of the way the diagnostic routines infer the appropriate location to report. --- 749,762 ---- name, or possibly the line of the closing parenthesis in the case of function-like macro expansion. ! The `cpp_token' structure contains `line' and `col' members. The lexer fills these in with the line and column of the first character of the token. Consequently, but maybe unexpectedly, a token from the replacement list of a macro expansion carries the location of the token ! within the `#define' directive, because cpplib expands a macro by returning pointers to the tokens in its replacement list. The current ! implementation of cpplib assigns tokens created from built-in macros ! and the `#' and `##' operators the location of the most recently lexed token. This is a because they are allocated from the lexer's token runs, and because of the way the diagnostic routines infer the appropriate location to report. *************** line other than the first. *** 775,784 **** To solve these issues, cpplib provides a callback that is generated whenever it lexes a preprocessing token that starts a new logical line ! other than a directive. It passes this token (which may be a 'CPP_EOF' token indicating the end of the translation unit) to the callback ! routine, which can then use the line and column of this token to produce ! correct output. Representation of line numbers ============================== --- 778,787 ---- To solve these issues, cpplib provides a callback that is generated whenever it lexes a preprocessing token that starts a new logical line ! other than a directive. It passes this token (which may be a `CPP_EOF' token indicating the end of the translation unit) to the callback ! routine, which can then use the line and column of this token to ! produce correct output. Representation of line numbers ============================== *************** starts counting from one. *** 798,811 **** translation unit. With some simple infrastructure, it is straight forward to map from this to the original source file and line number pair, saving space whenever line number information needs to be saved. ! The code the implements this mapping lies in the files 'line-map.c' and ! 'line-map.h'. Command-line macros and assertions are implemented by pushing a ! buffer containing the right hand side of an equivalent '#define' or ! '#assert' directive. Some built-in macros are handled similarly. Since ! these are all processed before the first line of the main input file, it ! will typically have an assigned line closer to twenty than to one.  File: cppinternals.info, Node: Guard Macros, Next: Files, Prev: Line Numbering, Up: Top --- 801,815 ---- translation unit. With some simple infrastructure, it is straight forward to map from this to the original source file and line number pair, saving space whenever line number information needs to be saved. ! The code the implements this mapping lies in the files `line-map.c' and ! `line-map.h'. Command-line macros and assertions are implemented by pushing a ! buffer containing the right hand side of an equivalent `#define' or ! `#assert' directive. Some built-in macros are handled similarly. ! Since these are all processed before the first line of the main input ! file, it will typically have an assigned line closer to twenty than to ! one.  File: cppinternals.info, Node: Guard Macros, Next: Files, Prev: Line Numbering, Up: Top *************** Header files are often of the form *** 822,828 **** to prevent the compiler from processing them more than once. The preprocessor notices such header files, so that if the header file ! appears in a subsequent '#include' directive and 'FOO' is defined, then it is ignored and it doesn't preprocess or even re-open the file a second time. This is referred to as the "multiple include optimization". --- 826,832 ---- to prevent the compiler from processing them more than once. The preprocessor notices such header files, so that if the header file ! appears in a subsequent `#include' directive and `FOO' is defined, then it is ignored and it doesn't preprocess or even re-open the file a second time. This is referred to as the "multiple include optimization". *************** inclusion would result in no tokens to r *** 833,844 **** directives to process. Therefore the current implementation imposes requirements and makes some allowances as follows: ! 1. There must be no tokens outside the controlling '#if'-'#endif' pair, but whitespace and comments are permitted. ! 2. There must be no directives outside the controlling directive pair, ! but the "null directive" (a line containing nothing other than a ! single '#' and possibly whitespace) is permitted. 3. The opening directive must be of the form --- 837,848 ---- directives to process. Therefore the current implementation imposes requirements and makes some allowances as follows: ! 1. There must be no tokens outside the controlling `#if'-`#endif' pair, but whitespace and comments are permitted. ! 2. There must be no directives outside the controlling directive ! pair, but the "null directive" (a line containing nothing other ! than a single `#' and possibly whitespace) is permitted. 3. The opening directive must be of the form *************** requirements and makes some allowances a *** 848,915 **** #if !defined FOO [equivalently, #if !defined(FOO)] ! 4. In the second form above, the tokens forming the '#if' expression must have come directly from the source file--no macro expansion must have been involved. This is because macro definitions can ! change, and tracking whether or not a relevant change has been made ! is not worth the implementation cost. ! 5. There can be no '#else' or '#elif' directives at the outer conditional block level, because they would probably contain something of interest to a subsequent pass. First, when pushing a new file on the buffer stack, ! '_stack_include_file' sets the controlling macro 'mi_cmacro' to 'NULL', ! and sets 'mi_valid' to 'true'. This indicates that the preprocessor has ! not yet encountered anything that would invalidate the multiple-include ! optimization. As described in the next few paragraphs, these two ! variables having these values effectively indicates top-of-file. When about to return a token that is not part of a directive, ! '_cpp_lex_token' sets 'mi_valid' to 'false'. This enforces the constraint that tokens outside the controlling conditional block invalidate the optimization. ! The 'do_if', when appropriate, and 'do_ifndef' directive handlers ! pass the controlling macro to the function 'push_conditional'. cpplib maintains a stack of nested conditional blocks, and after processing ! every opening conditional this function pushes an 'if_stack' structure onto the stack. In this structure it records the controlling macro for the block, provided there is one and we're at top-of-file (as described ! above). If an '#elif' or '#else' directive is encountered, the ! controlling macro for that block is cleared to 'NULL'. Otherwise, it ! survives until the '#endif' closing the block, upon which 'do_endif' ! sets 'mi_valid' to true and stores the controlling macro in 'mi_cmacro'. ! '_cpp_handle_directive' clears 'mi_valid' when processing any directive other than an opening conditional and the null directive. With this, and requiring top-of-file to record a controlling macro, and ! no '#else' or '#elif' for it to survive and be copied to 'mi_cmacro' by ! 'do_endif', we have enforced the absence of directives outside the main conditional block for the optimization to be on. ! Note that whilst we are inside the conditional block, 'mi_valid' is ! likely to be reset to 'false', but this does not matter since the ! closing '#endif' restores it to 'true' if appropriate. ! Finally, since '_cpp_lex_direct' pops the file off the buffer stack ! at 'EOF' without returning a token, if the '#endif' directive was not ! followed by any tokens, 'mi_valid' is 'true' and '_cpp_pop_file_buffer' remembers the controlling macro associated with the file. Subsequent ! calls to 'stack_include_file' result in no buffer being pushed if the controlling macro is defined, effecting the optimization. A quick word on how we handle the #if !defined FOO ! case. '_cpp_parse_expr' and 'parse_defined' take steps to see whether ! the three stages '!', 'defined-expression' and 'end-of-directive' occur ! in order in a '#if' expression. If so, they return the guard macro to ! 'do_if' in the variable 'mi_ind_cmacro', and otherwise set it to 'NULL'. ! 'enter_macro_context' sets 'mi_valid' to false, so if a macro was ! expanded whilst parsing any part of the expression, then the top-of-file ! test in 'push_conditional' fails and the optimization is turned off.  File: cppinternals.info, Node: Files, Next: Concept Index, Prev: Guard Macros, Up: Top --- 852,921 ---- #if !defined FOO [equivalently, #if !defined(FOO)] ! 4. In the second form above, the tokens forming the `#if' expression must have come directly from the source file--no macro expansion must have been involved. This is because macro definitions can ! change, and tracking whether or not a relevant change has been ! made is not worth the implementation cost. ! 5. There can be no `#else' or `#elif' directives at the outer conditional block level, because they would probably contain something of interest to a subsequent pass. First, when pushing a new file on the buffer stack, ! `_stack_include_file' sets the controlling macro `mi_cmacro' to `NULL', ! and sets `mi_valid' to `true'. This indicates that the preprocessor ! has not yet encountered anything that would invalidate the ! multiple-include optimization. As described in the next few ! paragraphs, these two variables having these values effectively ! indicates top-of-file. When about to return a token that is not part of a directive, ! `_cpp_lex_token' sets `mi_valid' to `false'. This enforces the constraint that tokens outside the controlling conditional block invalidate the optimization. ! The `do_if', when appropriate, and `do_ifndef' directive handlers ! pass the controlling macro to the function `push_conditional'. cpplib maintains a stack of nested conditional blocks, and after processing ! every opening conditional this function pushes an `if_stack' structure onto the stack. In this structure it records the controlling macro for the block, provided there is one and we're at top-of-file (as described ! above). If an `#elif' or `#else' directive is encountered, the ! controlling macro for that block is cleared to `NULL'. Otherwise, it ! survives until the `#endif' closing the block, upon which `do_endif' ! sets `mi_valid' to true and stores the controlling macro in `mi_cmacro'. ! `_cpp_handle_directive' clears `mi_valid' when processing any directive other than an opening conditional and the null directive. With this, and requiring top-of-file to record a controlling macro, and ! no `#else' or `#elif' for it to survive and be copied to `mi_cmacro' by ! `do_endif', we have enforced the absence of directives outside the main conditional block for the optimization to be on. ! Note that whilst we are inside the conditional block, `mi_valid' is ! likely to be reset to `false', but this does not matter since the ! closing `#endif' restores it to `true' if appropriate. ! Finally, since `_cpp_lex_direct' pops the file off the buffer stack ! at `EOF' without returning a token, if the `#endif' directive was not ! followed by any tokens, `mi_valid' is `true' and `_cpp_pop_file_buffer' remembers the controlling macro associated with the file. Subsequent ! calls to `stack_include_file' result in no buffer being pushed if the controlling macro is defined, effecting the optimization. A quick word on how we handle the #if !defined FOO ! case. `_cpp_parse_expr' and `parse_defined' take steps to see whether ! the three stages `!', `defined-expression' and `end-of-directive' occur ! in order in a `#if' expression. If so, they return the guard macro to ! `do_if' in the variable `mi_ind_cmacro', and otherwise set it to `NULL'. ! `enter_macro_context' sets `mi_valid' to false, so if a macro was ! expanded whilst parsing any part of the expression, then the ! top-of-file test in `push_conditional' fails and the optimization is ! turned off.  File: cppinternals.info, Node: Files, Next: Concept Index, Prev: Guard Macros, Up: Top *************** File Handling *** 918,930 **** ************* Fairly obviously, the file handling code of cpplib resides in the file ! 'files.c'. It takes care of the details of file searching, opening, reading and caching, for both the main source file and all the headers it recursively includes. The basic strategy is to minimize the number of system calls. On ! many systems, the basic 'open ()' and 'fstat ()' system calls can be ! quite expensive. For every '#include'-d file, we need to try all the directories in the search path until we find a match. Some projects, such as glibc, pass twenty or thirty include paths on the command line, so this can rapidly become time consuming. --- 924,936 ---- ************* Fairly obviously, the file handling code of cpplib resides in the file ! `files.c'. It takes care of the details of file searching, opening, reading and caching, for both the main source file and all the headers it recursively includes. The basic strategy is to minimize the number of system calls. On ! many systems, the basic `open ()' and `fstat ()' system calls can be ! quite expensive. For every `#include'-d file, we need to try all the directories in the search path until we find a match. Some projects, such as glibc, pass twenty or thirty include paths on the command line, so this can rapidly become time consuming. *************** repeating the filesystem queries whilst *** 936,980 **** For each file we try to open, we store the constructed path in a splay tree. This path first undergoes simplification by the function ! '_cpp_simplify_pathname'. For example, '/usr/include/bits/../foo.h' is ! simplified to '/usr/include/foo.h' before we enter it in the splay tree ! and try to 'open ()' the file. CPP will then find subsequent uses of ! 'foo.h', even as '/usr/include/foo.h', in the splay tree and save system ! calls. ! Further, it is likely the file contents have also been cached, saving ! a 'read ()' system call. We don't bother caching the contents of header ! files that are re-inclusion protected, and whose re-inclusion macro is ! defined when we leave the header file for the first time. If the host ! supports it, we try to map suitably large files into memory, rather than ! reading them in directly. The include paths are internally stored on a null-terminated ! singly-linked list, starting with the '"header.h"' directory search ! chain, which then links into the '' directory chain. ! Files included with the '' syntax start the lookup directly in ! the second half of this chain. However, files included with the ! '"foo.h"' syntax start at the beginning of the chain, but with one extra ! directory prepended. This is the directory of the current file; the one ! containing the '#include' directive. Prepending this directory on a ! per-file basis is handled by the function 'search_from'. Note that a header included with a directory component, such as ! '#include "mydir/foo.h"' and opened as '/usr/local/include/mydir/foo.h', ! will have the complete path minus the basename 'foo.h' as the current ! directory. Enough information is stored in the splay tree that CPP can immediately tell whether it can skip the header file because of the ! multiple include optimization, whether the file didn't exist or couldn't ! be opened for some reason, or whether the header was flagged not to be ! re-used, as it is with the obsolete '#import' directive. For the benefit of MS-DOS filesystems with an 8.3 filename limitation, CPP offers the ability to treat various include file names as aliases for the real header files with shorter names. The map from ! one to the other is found in a special file called 'header.gcc', stored in the command line (or system) include directories to which the mapping applies. This may be higher up the directory tree than the full path to the file minus the base name. --- 942,986 ---- For each file we try to open, we store the constructed path in a splay tree. This path first undergoes simplification by the function ! `_cpp_simplify_pathname'. For example, `/usr/include/bits/../foo.h' is ! simplified to `/usr/include/foo.h' before we enter it in the splay tree ! and try to `open ()' the file. CPP will then find subsequent uses of ! `foo.h', even as `/usr/include/foo.h', in the splay tree and save ! system calls. ! Further, it is likely the file contents have also been cached, ! saving a `read ()' system call. We don't bother caching the contents of ! header files that are re-inclusion protected, and whose re-inclusion ! macro is defined when we leave the header file for the first time. If ! the host supports it, we try to map suitably large files into memory, ! rather than reading them in directly. The include paths are internally stored on a null-terminated ! singly-linked list, starting with the `"header.h"' directory search ! chain, which then links into the `' directory chain. ! Files included with the `' syntax start the lookup directly ! in the second half of this chain. However, files included with the ! `"foo.h"' syntax start at the beginning of the chain, but with one ! extra directory prepended. This is the directory of the current file; ! the one containing the `#include' directive. Prepending this directory ! on a per-file basis is handled by the function `search_from'. Note that a header included with a directory component, such as ! `#include "mydir/foo.h"' and opened as ! `/usr/local/include/mydir/foo.h', will have the complete path minus the ! basename `foo.h' as the current directory. Enough information is stored in the splay tree that CPP can immediately tell whether it can skip the header file because of the ! multiple include optimization, whether the file didn't exist or ! couldn't be opened for some reason, or whether the header was flagged ! not to be re-used, as it is with the obsolete `#import' directive. For the benefit of MS-DOS filesystems with an 8.3 filename limitation, CPP offers the ability to treat various include file names as aliases for the real header files with shorter names. The map from ! one to the other is found in a special file called `header.gcc', stored in the command line (or system) include directories to which the mapping applies. This may be higher up the directory tree than the full path to the file minus the base name. *************** Concept Index *** 990,996 **** * assertions: Hash Nodes. (line 6) * controlling macros: Guard Macros. (line 6) ! * escaped newlines: Lexer. (line 5) * files: Files. (line 6) * guard macros: Guard Macros. (line 6) * hash table: Hash Nodes. (line 6) --- 996,1002 ---- * assertions: Hash Nodes. (line 6) * controlling macros: Guard Macros. (line 6) ! * escaped newlines: Lexer. (line 6) * files: Files. (line 6) * guard macros: Guard Macros. (line 6) * hash table: Hash Nodes. (line 6) *************** Concept Index *** 998,1004 **** * identifiers: Hash Nodes. (line 6) * interface: Conventions. (line 6) * lexer: Lexer. (line 6) ! * line numbers: Line Numbering. (line 5) * macro expansion: Macro Expansion. (line 6) * macro representation (internal): Macro Expansion. (line 19) * macros: Hash Nodes. (line 6) --- 1004,1010 ---- * identifiers: Hash Nodes. (line 6) * interface: Conventions. (line 6) * lexer: Lexer. (line 6) ! * line numbers: Line Numbering. (line 6) * macro expansion: Macro Expansion. (line 6) * macro representation (internal): Macro Expansion. (line 19) * macros: Hash Nodes. (line 6) *************** Concept Index *** 1007,1029 **** * newlines: Lexer. (line 6) * paste avoidance: Token Spacing. (line 6) * spacing: Token Spacing. (line 6) ! * token run: Lexer. (line 191) * token spacing: Token Spacing. (line 6)  Tag Table: ! Node: Top905 ! Node: Conventions2590 ! Node: Lexer3532 ! Ref: Invalid identifiers11447 ! Ref: Lexing a line13397 ! Node: Hash Nodes18170 ! Node: Macro Expansion21049 ! Node: Token Spacing29997 ! Node: Line Numbering35854 ! Node: Guard Macros39939 ! Node: Files44730 ! Node: Concept Index48196  End Tag Table --- 1013,1035 ---- * newlines: Lexer. (line 6) * paste avoidance: Token Spacing. (line 6) * spacing: Token Spacing. (line 6) ! * token run: Lexer. (line 192) * token spacing: Token Spacing. (line 6)  Tag Table: ! Node: Top958 ! Node: Conventions2643 ! Node: Lexer3585 ! Ref: Invalid identifiers11498 ! Ref: Lexing a line13447 ! Node: Hash Nodes18220 ! Node: Macro Expansion21099 ! Node: Token Spacing30046 ! Node: Line Numbering35906 ! Node: Guard Macros39991 ! Node: Files44782 ! Node: Concept Index48248  End Tag Table diff -Nrcpad gcc-6.3.0/gcc/doc/cppinternals.texi gcc-6.4.0/gcc/doc/cppinternals.texi *** gcc-6.3.0/gcc/doc/cppinternals.texi Mon Jan 4 13:03:35 2016 --- gcc-6.4.0/gcc/doc/cppinternals.texi Tue Jul 4 07:15:57 2017 *************** into another language, under the above c *** 47,53 **** @page @vskip 0pt plus 1filll @c man begin COPYRIGHT ! Copyright @copyright{} 2000-2016 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice --- 47,53 ---- @page @vskip 0pt plus 1filll @c man begin COPYRIGHT ! Copyright @copyright{} 2000-2017 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice diff -Nrcpad gcc-6.3.0/gcc/doc/extend.texi gcc-6.4.0/gcc/doc/extend.texi *** gcc-6.3.0/gcc/doc/extend.texi Fri Sep 16 21:37:49 2016 --- gcc-6.4.0/gcc/doc/extend.texi Wed Apr 12 13:37:30 2017 *************** is enabled. Cilk Plus can be enabled usi *** 10157,10163 **** Further details and examples about these built-in functions are described in the Cilk Plus language manual which can be found at ! @uref{http://www.cilkplus.org}. @node Other Builtins @section Other Built-in Functions Provided by GCC --- 10157,10163 ---- Further details and examples about these built-in functions are described in the Cilk Plus language manual which can be found at ! @uref{https://www.cilkplus.org}. @node Other Builtins @section Other Built-in Functions Provided by GCC *************** The following built-in functions are ava *** 13973,13986 **** of processors when hardware decimal floating point (@option{-mhard-dfp}) is available: @smallexample ! _Decimal64 __builtin_dxex (_Decimal64); ! _Decimal128 __builtin_dxexq (_Decimal128); _Decimal64 __builtin_ddedpd (int, _Decimal64); _Decimal128 __builtin_ddedpdq (int, _Decimal128); _Decimal64 __builtin_denbcd (int, _Decimal64); _Decimal128 __builtin_denbcdq (int, _Decimal128); ! _Decimal64 __builtin_diex (_Decimal64, _Decimal64); ! _Decimal128 _builtin_diexq (_Decimal128, _Decimal128); _Decimal64 __builtin_dscli (_Decimal64, int); _Decimal128 __builtin_dscliq (_Decimal128, int); _Decimal64 __builtin_dscri (_Decimal64, int); --- 13973,13986 ---- of processors when hardware decimal floating point (@option{-mhard-dfp}) is available: @smallexample ! long long __builtin_dxex (_Decimal64); ! long long __builtin_dxexq (_Decimal128); _Decimal64 __builtin_ddedpd (int, _Decimal64); _Decimal128 __builtin_ddedpdq (int, _Decimal128); _Decimal64 __builtin_denbcd (int, _Decimal64); _Decimal128 __builtin_denbcdq (int, _Decimal128); ! _Decimal64 __builtin_diex (long long, _Decimal64); ! _Decimal128 _builtin_diexq (long long, _Decimal128); _Decimal64 __builtin_dscli (_Decimal64, int); _Decimal128 __builtin_dscliq (_Decimal128, int); _Decimal64 __builtin_dscri (_Decimal64, int); *************** void vec_vsx_st (vector bool char, int, *** 16149,16168 **** void vec_vsx_st (vector bool char, int, unsigned char *); void vec_vsx_st (vector bool char, int, signed char *); ! vector double vec_xxpermdi (vector double, vector double, int); ! vector float vec_xxpermdi (vector float, vector float, int); ! vector long long vec_xxpermdi (vector long long, vector long long, int); vector unsigned long long vec_xxpermdi (vector unsigned long long, ! vector unsigned long long, int); ! vector int vec_xxpermdi (vector int, vector int, int); vector unsigned int vec_xxpermdi (vector unsigned int, ! vector unsigned int, int); ! vector short vec_xxpermdi (vector short, vector short, int); vector unsigned short vec_xxpermdi (vector unsigned short, ! vector unsigned short, int); ! vector signed char vec_xxpermdi (vector signed char, vector signed char, int); vector unsigned char vec_xxpermdi (vector unsigned char, ! vector unsigned char, int); vector double vec_xxsldi (vector double, vector double, int); vector float vec_xxsldi (vector float, vector float, int); --- 16149,16169 ---- void vec_vsx_st (vector bool char, int, unsigned char *); void vec_vsx_st (vector bool char, int, signed char *); ! vector double vec_xxpermdi (vector double, vector double, const int); ! vector float vec_xxpermdi (vector float, vector float, const int); ! vector long long vec_xxpermdi (vector long long, vector long long, const int); vector unsigned long long vec_xxpermdi (vector unsigned long long, ! vector unsigned long long, const int); ! vector int vec_xxpermdi (vector int, vector int, const int); vector unsigned int vec_xxpermdi (vector unsigned int, ! vector unsigned int, const int); ! vector short vec_xxpermdi (vector short, vector short, const int); vector unsigned short vec_xxpermdi (vector unsigned short, ! vector unsigned short, const int); ! vector signed char vec_xxpermdi (vector signed char, vector signed char, ! const int); vector unsigned char vec_xxpermdi (vector unsigned char, ! vector unsigned char, const int); vector double vec_xxsldi (vector double, vector double, int); vector float vec_xxsldi (vector float, vector float, int); *************** int __builtin_bcdsub_gt (vector __int128 *** 16554,16561 **** int __builtin_bcdsub_ov (vector __int128_t, vector__int128_t); @end smallexample ! If the ISA 3.00 additions to the vector/scalar (power9-vector) ! instruction set are available: @smallexample vector long long vec_vctz (vector long long); --- 16555,16562 ---- int __builtin_bcdsub_ov (vector __int128_t, vector__int128_t); @end smallexample ! If the ISA 3.0 instruction set additions (@option{-mcpu=power9}) ! are available: @smallexample vector long long vec_vctz (vector long long); *************** vector long long vec_vprtybd (vector lon *** 16591,16600 **** vector unsigned long long vec_vprtybd (vector unsigned long long); @end smallexample ! ! If the ISA 3.00 additions to the vector/scalar (power9-vector) ! instruction set are available for 64-bit targets: ! @smallexample vector long vec_vprtyb (vector long); vector unsigned long vec_vprtyb (vector unsigned long); --- 16592,16600 ---- vector unsigned long long vec_vprtybd (vector unsigned long long); @end smallexample ! On 64-bit targets, if the ISA 3.0 additions (@option{-mcpu=power9}) ! are available: ! @smallexample vector long vec_vprtyb (vector long); vector unsigned long vec_vprtyb (vector unsigned long); *************** vector __uint128_t vec_vprtybd (vector _ *** 16609,16617 **** @end smallexample The following built-in vector functions are available for the PowerPC family ! of processors, starting with ISA 3.0 or later (@option{-mcpu=power9}) ! or with @option{-mpower9-vector}: ! @smallexample __vector unsigned char vec_absd (__vector unsigned char arg1, __vector unsigned char arg2); --- 16609,16615 ---- @end smallexample The following built-in vector functions are available for the PowerPC family ! of processors, starting with ISA 3.0 or later (@option{-mcpu=power9}): @smallexample __vector unsigned char vec_absd (__vector unsigned char arg1, __vector unsigned char arg2); *************** The second argument to the @var{__builti *** 16723,16731 **** integer that is 0 or 1. The third argument to these builtin functions must be a constant integer in the range of 0 to 15. ! If the ISA 3.00 additions to the vector/scalar (power9-vector) ! instruction set are available, the following additional functions are ! available for both 32-bit and 64-bit targets. vector short vec_xl (int, vector short *); vector short vec_xl (int, short *); --- 16721,16729 ---- integer that is 0 or 1. The third argument to these builtin functions must be a constant integer in the range of 0 to 15. ! If the ISA 3.0 instruction set additions ! are enabled (@option{-mcpu=power9}), the following additional ! functions are available for both 32-bit and 64-bit targets. vector short vec_xl (int, vector short *); vector short vec_xl (int, short *); diff -Nrcpad gcc-6.3.0/gcc/doc/fsf-funding.7 gcc-6.4.0/gcc/doc/fsf-funding.7 *** gcc-6.3.0/gcc/doc/fsf-funding.7 Wed Dec 21 08:06:54 2016 --- gcc-6.4.0/gcc/doc/fsf-funding.7 Tue Jul 4 07:37:47 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "FSF-FUNDING 7" ! .TH FSF-FUNDING 7 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "FSF-FUNDING 7" ! .TH FSF-FUNDING 7 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/g++.1 gcc-6.4.0/gcc/doc/g++.1 *** gcc-6.3.0/gcc/doc/g++.1 Wed Dec 21 09:34:11 2016 --- gcc-6.4.0/gcc/doc/g++.1 Tue Jul 4 09:27:49 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GCC 1" ! .TH GCC 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GCC 1" ! .TH GCC 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** in the following sections. *** 278,284 **** \&\fB\-Wno\-attributes \-Wbool\-compare \-Wno\-builtin\-macro\-redefined \&\-Wc90\-c99\-compat \-Wc99\-c11\-compat \&\-Wc++\-compat \-Wc++11\-compat \-Wc++14\-compat \-Wcast\-align \-Wcast\-qual ! \&\-Wchar\-subscripts \-Wclobbered \-Wcomment \-Wconditionally\-supported \&\-Wconversion \-Wcoverage\-mismatch \-Wno\-cpp \-Wdate\-time \-Wdelete\-incomplete \&\-Wno\-deprecated \-Wno\-deprecated\-declarations \-Wno\-designated\-init \&\-Wdisabled\-optimization --- 282,288 ---- \&\fB\-Wno\-attributes \-Wbool\-compare \-Wno\-builtin\-macro\-redefined \&\-Wc90\-c99\-compat \-Wc99\-c11\-compat \&\-Wc++\-compat \-Wc++11\-compat \-Wc++14\-compat \-Wcast\-align \-Wcast\-qual ! \&\-Wchar\-subscripts \-Wchkp \-Wclobbered \-Wcomment \-Wconditionally\-supported \&\-Wconversion \-Wcoverage\-mismatch \-Wno\-cpp \-Wdate\-time \-Wdelete\-incomplete \&\-Wno\-deprecated \-Wno\-deprecated\-declarations \-Wno\-designated\-init \&\-Wdisabled\-optimization *************** See \s-1RS/6000\s0 and PowerPC Options. *** 1009,1018 **** \&\-mquad\-memory\-atomic \-mno\-quad\-memory\-atomic \&\-mcompat\-align\-parm \-mno\-compat\-align\-parm \&\-mupper\-regs\-df \-mno\-upper\-regs\-df \-mupper\-regs\-sf \-mno\-upper\-regs\-sf ! \&\-mupper\-regs \-mno\-upper\-regs \-mmodulo \-mno\-modulo \&\-mfloat128 \-mno\-float128 \-mfloat128\-hardware \-mno\-float128\-hardware ! \&\-mpower9\-fusion \-mno\-mpower9\-fusion \-mpower9\-vector \-mno\-power9\-vector ! \&\-mpower9\-dform \-mno\-power9\-dform \-mlra \-mno\-lra\fR .Sp \&\fI\s-1RX\s0 Options\fR \&\fB\-m64bit\-doubles \-m32bit\-doubles \-fpu \-nofpu --- 1013,1021 ---- \&\-mquad\-memory\-atomic \-mno\-quad\-memory\-atomic \&\-mcompat\-align\-parm \-mno\-compat\-align\-parm \&\-mupper\-regs\-df \-mno\-upper\-regs\-df \-mupper\-regs\-sf \-mno\-upper\-regs\-sf ! \&\-mupper\-regs \-mno\-upper\-regs \&\-mfloat128 \-mno\-float128 \-mfloat128\-hardware \-mno\-float128\-hardware ! \&\-mlra \-mno\-lra\fR .Sp \&\fI\s-1RX\s0 Options\fR \&\fB\-m64bit\-doubles \-m32bit\-doubles \-fpu \-nofpu *************** In C mode, this is equivalent to \fB\-st *** 1692,1698 **** equivalent to \fB\-std=c++98\fR. .Sp This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO ! C90\s0 (when compiling C code), or of standard \*(C+ (when compiling \*(C+ code), such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, and predefined macros such as \f(CW\*(C`unix\*(C'\fR and \f(CW\*(C`vax\*(C'\fR that identify the type of system you are using. It also enables the undesirable and --- 1695,1701 ---- equivalent to \fB\-std=c++98\fR. .Sp This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO ! C90 \s0(when compiling C code), or of standard \*(C+ (when compiling \*(C+ code), such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, and predefined macros such as \f(CW\*(C`unix\*(C'\fR and \f(CW\*(C`vax\*(C'\fR that identify the type of system you are using. It also enables the undesirable and *************** from declaring certain functions or defi *** 1719,1725 **** programs that might use these names for other things. .Sp Functions that are normally built in but do not have semantics ! defined by \s-1ISO C\s0 (such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in functions when \fB\-ansi\fR is used. .IP "\fB\-std=\fR" 4 .IX Item "-std=" --- 1722,1728 ---- programs that might use these names for other things. .Sp Functions that are normally built in but do not have semantics ! defined by \s-1ISO C \s0(such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in functions when \fB\-ansi\fR is used. .IP "\fB\-std=\fR" 4 .IX Item "-std=" *************** with \s-1ISO C90\s0 are disabled). Same *** 1769,1775 **** .IP "\fBiso9899:199x\fR" 4 .IX Item "iso9899:199x" .PD ! \&\s-1ISO C99.\s0 This standard is substantially completely supported, modulo bugs and floating-point issues (mainly but not entirely relating to optional C99 features from Annexes F and G). See --- 1772,1778 ---- .IP "\fBiso9899:199x\fR" 4 .IX Item "iso9899:199x" .PD ! \&\s-1ISO C99. \s0 This standard is substantially completely supported, modulo bugs and floating-point issues (mainly but not entirely relating to optional C99 features from Annexes F and G). See *************** interfaces) and L (Analyzability). The *** 1794,1814 **** .IP "\fBgnu89\fR" 4 .IX Item "gnu89" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C90\s0 (including some C99 features). .IP "\fBgnu99\fR" 4 .IX Item "gnu99" .PD 0 .IP "\fBgnu9x\fR" 4 .IX Item "gnu9x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C99.\s0 The name \fBgnu9x\fR is deprecated. .IP "\fBgnu11\fR" 4 .IX Item "gnu11" .PD 0 .IP "\fBgnu1x\fR" 4 .IX Item "gnu1x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C11.\s0 This is the default for C code. The name \fBgnu1x\fR is deprecated. .IP "\fBc++98\fR" 4 .IX Item "c++98" --- 1797,1817 ---- .IP "\fBgnu89\fR" 4 .IX Item "gnu89" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C90 \s0(including some C99 features). .IP "\fBgnu99\fR" 4 .IX Item "gnu99" .PD 0 .IP "\fBgnu9x\fR" 4 .IX Item "gnu9x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C99. \s0 The name \fBgnu9x\fR is deprecated. .IP "\fBgnu11\fR" 4 .IX Item "gnu11" .PD 0 .IP "\fBgnu1x\fR" 4 .IX Item "gnu1x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C11. \s0 This is the default for C code. The name \fBgnu1x\fR is deprecated. .IP "\fBc++98\fR" 4 .IX Item "c++98" *************** relevant for \*(C+ programs. *** 2147,2153 **** Here is a list of options that are \fIonly\fR for compiling \*(C+ programs: .IP "\fB\-fabi\-version=\fR\fIn\fR" 4 .IX Item "-fabi-version=n" ! Use version \fIn\fR of the \*(C+ \s-1ABI.\s0 The default is version 0. .Sp Version 0 refers to the version conforming most closely to the \*(C+ \s-1ABI\s0 specification. Therefore, the \s-1ABI\s0 obtained using version 0 --- 2150,2156 ---- Here is a list of options that are \fIonly\fR for compiling \*(C+ programs: .IP "\fB\-fabi\-version=\fR\fIn\fR" 4 .IX Item "-fabi-version=n" ! Use version \fIn\fR of the \*(C+ \s-1ABI. \s0 The default is version 0. .Sp Version 0 refers to the version conforming most closely to the \*(C+ \s-1ABI\s0 specification. Therefore, the \s-1ABI\s0 obtained using version 0 *************** exhaustion is signalled by throwing \f(C *** 2223,2229 **** .IP "\fB\-fconcepts\fR" 4 .IX Item "-fconcepts" Enable support for the \*(C+ Extensions for Concepts Technical ! Specification, \s-1ISO 19217\s0 (2015), which allows code like .Sp .Vb 2 \& template concept bool Addable = requires (T t) { t + t; }; --- 2226,2232 ---- .IP "\fB\-fconcepts\fR" 4 .IX Item "-fconcepts" Enable support for the \*(C+ Extensions for Concepts Technical ! Specification, \s-1ISO 19217 \s0(2015), which allows code like .Sp .Vb 2 \& template concept bool Addable = requires (T t) { t + t; }; *************** int and getting a pointer to member func *** 2351,2357 **** .IP "\fB\-fno\-nonansi\-builtins\fR" 4 .IX Item "-fno-nonansi-builtins" Disable built-in declarations of functions that are not mandated by ! \&\s-1ANSI/ISO C.\s0 These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR, \&\f(CW\*(C`index\*(C'\fR, \f(CW\*(C`bzero\*(C'\fR, \f(CW\*(C`conjf\*(C'\fR, and other related functions. .IP "\fB\-fnothrow\-opt\fR" 4 .IX Item "-fnothrow-opt" --- 2354,2360 ---- .IP "\fB\-fno\-nonansi\-builtins\fR" 4 .IX Item "-fno-nonansi-builtins" Disable built-in declarations of functions that are not mandated by ! \&\s-1ANSI/ISO C. \s0 These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR, \&\f(CW\*(C`index\*(C'\fR, \f(CW\*(C`bzero\*(C'\fR, \f(CW\*(C`conjf\*(C'\fR, and other related functions. .IP "\fB\-fnothrow\-opt\fR" 4 .IX Item "-fnothrow-opt" *************** are taken in different shared objects. *** 2466,2472 **** The effect of this is that \s-1GCC\s0 may, effectively, mark inline methods with \&\f(CW\*(C`_\|_attribute_\|_ ((visibility ("hidden")))\*(C'\fR so that they do not appear in the export table of a \s-1DSO\s0 and do not require a \s-1PLT\s0 indirection ! when used within the \s-1DSO.\s0 Enabling this option can have a dramatic effect on load and link times of a \s-1DSO\s0 as it massively reduces the size of the dynamic export table when the library makes heavy use of templates. .Sp --- 2469,2475 ---- The effect of this is that \s-1GCC\s0 may, effectively, mark inline methods with \&\f(CW\*(C`_\|_attribute_\|_ ((visibility ("hidden")))\*(C'\fR so that they do not appear in the export table of a \s-1DSO\s0 and do not require a \s-1PLT\s0 indirection ! when used within the \s-1DSO. \s0 Enabling this option can have a dramatic effect on load and link times of a \s-1DSO\s0 as it massively reduces the size of the dynamic export table when the library makes heavy use of templates. .Sp *************** have meanings only for \*(C+ programs: *** 2536,2542 **** .IP "\fB\-Wabi\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wabi (C, Objective-C, and Objective- only)" Warn when G++ it generates code that is probably not compatible with ! the vendor-neutral \*(C+ \s-1ABI.\s0 Since G++ now defaults to updating the \&\s-1ABI\s0 with each major release, normally \fB\-Wabi\fR will warn only if there is a check added later in a release series for an \s-1ABI\s0 issue discovered since the initial release. \fB\-Wabi\fR will warn about --- 2539,2545 ---- .IP "\fB\-Wabi\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wabi (C, Objective-C, and Objective- only)" Warn when G++ it generates code that is probably not compatible with ! the vendor-neutral \*(C+ \s-1ABI. \s0 Since G++ now defaults to updating the \&\s-1ABI\s0 with each major release, normally \fB\-Wabi\fR will warn only if there is a check added later in a release series for an \s-1ABI\s0 issue discovered since the initial release. \fB\-Wabi\fR will warn about *************** unsignedness, but the standard mandates *** 2851,2878 **** Warn when a primary template declaration is encountered. Some coding rules disallow templates, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so ! one can still use the \s-1STL.\s0 One may also instantiate or specialize templates. .IP "\fB\-Wmultiple\-inheritance\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wmultiple-inheritance ( and Objective- only)" Warn when a class is defined with multiple direct base classes. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL.\s0 One may also define classes that indirectly use multiple inheritance. .IP "\fB\-Wvirtual\-inheritance\fR" 4 .IX Item "-Wvirtual-inheritance" Warn when a class is defined with a virtual direct base classe. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL.\s0 One may also define classes that indirectly use virtual inheritance. .IP "\fB\-Wnamespaces\fR" 4 .IX Item "-Wnamespaces" Warn when a namespace definition is opened. Some coding rules disallow namespaces, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so one can still ! use the \s-1STL.\s0 One may also use using directives and qualified names. .IP "\fB\-Wno\-terminate\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wno-terminate ( and Objective- only)" Disable the warning about a throw-expression that will immediately --- 2854,2881 ---- Warn when a primary template declaration is encountered. Some coding rules disallow templates, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so ! one can still use the \s-1STL. \s0 One may also instantiate or specialize templates. .IP "\fB\-Wmultiple\-inheritance\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wmultiple-inheritance ( and Objective- only)" Warn when a class is defined with multiple direct base classes. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL. \s0 One may also define classes that indirectly use multiple inheritance. .IP "\fB\-Wvirtual\-inheritance\fR" 4 .IX Item "-Wvirtual-inheritance" Warn when a class is defined with a virtual direct base classe. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL. \s0 One may also define classes that indirectly use virtual inheritance. .IP "\fB\-Wnamespaces\fR" 4 .IX Item "-Wnamespaces" Warn when a namespace definition is opened. Some coding rules disallow namespaces, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so one can still ! use the \s-1STL. \s0 One may also use using directives and qualified names. .IP "\fB\-Wno\-terminate\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wno-terminate ( and Objective- only)" Disable the warning about a throw-expression that will immediately *************** runtime. This is the default for most t *** 2918,2924 **** .IP "\fB\-fnext\-runtime\fR" 4 .IX Item "-fnext-runtime" Generate output compatible with the NeXT runtime. This is the default ! for NeXT-based systems, including Darwin and Mac \s-1OS X.\s0 The macro \&\f(CW\*(C`_\|_NEXT_RUNTIME_\|_\*(C'\fR is predefined if (and only if) this option is used. .IP "\fB\-fno\-nil\-receivers\fR" 4 --- 2921,2927 ---- .IP "\fB\-fnext\-runtime\fR" 4 .IX Item "-fnext-runtime" Generate output compatible with the NeXT runtime. This is the default ! for NeXT-based systems, including Darwin and Mac \s-1OS X. \s0 The macro \&\f(CW\*(C`_\|_NEXT_RUNTIME_\|_\*(C'\fR is predefined if (and only if) this option is used. .IP "\fB\-fno\-nil\-receivers\fR" 4 *************** This option is currently supported only *** 2935,2941 **** case, Version 0 is the traditional (32\-bit) \s-1ABI\s0 without support for properties and other Objective-C 2.0 additions. Version 1 is the traditional (32\-bit) \s-1ABI\s0 with support for properties and other ! Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI.\s0 If nothing is specified, the default is Version 0 on 32\-bit target machines, and Version 2 on 64\-bit target machines. .IP "\fB\-fobjc\-call\-cxx\-cdtors\fR" 4 --- 2938,2944 ---- case, Version 0 is the traditional (32\-bit) \s-1ABI\s0 without support for properties and other Objective-C 2.0 additions. Version 1 is the traditional (32\-bit) \s-1ABI\s0 with support for properties and other ! Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI. \s0 If nothing is specified, the default is Version 0 on 32\-bit target machines, and Version 2 on 64\-bit target machines. .IP "\fB\-fobjc\-call\-cxx\-cdtors\fR" 4 *************** version of the NeXT runtime \s-1ABI,\s0 *** 2993,2999 **** .IP "\fB\-fobjc\-std=objc1\fR" 4 .IX Item "-fobjc-std=objc1" Conform to the language syntax of Objective-C 1.0, the language ! recognized by \s-1GCC 4.0.\s0 This only affects the Objective-C additions to the C/\*(C+ language; it does not affect conformance to C/\*(C+ standards, which is controlled by the separate C/\*(C+ dialect option flags. When this option is used with the Objective-C or Objective\-\*(C+ compiler, --- 2996,3002 ---- .IP "\fB\-fobjc\-std=objc1\fR" 4 .IX Item "-fobjc-std=objc1" Conform to the language syntax of Objective-C 1.0, the language ! recognized by \s-1GCC 4.0. \s0 This only affects the Objective-C additions to the C/\*(C+ language; it does not affect conformance to C/\*(C+ standards, which is controlled by the separate C/\*(C+ dialect option flags. When this option is used with the Objective-C or Objective\-\*(C+ compiler, *************** warns that an unrecognized option is pre *** 3293,3299 **** .PD Issue all the warnings demanded by strict \s-1ISO C\s0 and \s-1ISO \*(C+\s0; reject all programs that use forbidden extensions, and some other ! programs that do not follow \s-1ISO C\s0 and \s-1ISO \*(C+.\s0 For \s-1ISO C,\s0 follows the version of the \s-1ISO C\s0 standard specified by any \fB\-std\fR option used. .Sp Valid \s-1ISO C\s0 and \s-1ISO \*(C+\s0 programs should compile properly with or without --- 3296,3302 ---- .PD Issue all the warnings demanded by strict \s-1ISO C\s0 and \s-1ISO \*(C+\s0; reject all programs that use forbidden extensions, and some other ! programs that do not follow \s-1ISO C\s0 and \s-1ISO \*(C+. \s0 For \s-1ISO C,\s0 follows the version of the \s-1ISO C\s0 standard specified by any \fB\-std\fR option used. .Sp Valid \s-1ISO C\s0 and \s-1ISO \*(C+\s0 programs should compile properly with or without *************** these escape routes; application program *** 3311,3317 **** Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO C\s0 conformance. They soon find that it does not do quite what they want: it finds some non-ISO practices, but not all\-\-\-only those for which ! \&\s-1ISO C\s0 \fIrequires\fR a diagnostic, and some others for which diagnostics have been added. .Sp A feature to report any failure to conform to \s-1ISO C\s0 might be useful in --- 3314,3320 ---- Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO C\s0 conformance. They soon find that it does not do quite what they want: it finds some non-ISO practices, but not all\-\-\-only those for which ! \&\s-1ISO C \s0\fIrequires\fR a diagnostic, and some others for which diagnostics have been added. .Sp A feature to report any failure to conform to \s-1ISO C\s0 might be useful in *************** This warning is enabled by \fB\-Wall\fR. *** 3448,3453 **** --- 3451,3460 ---- Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR comment, or whenever a Backslash-Newline appears in a \fB//\fR comment. This warning is enabled by \fB\-Wall\fR. + .IP "\fB\-Wchkp\fR" 4 + .IX Item "-Wchkp" + Warn about an invalid memory access that is found by Pointer Bounds Checker + (\fB\-fcheck\-pointer\-bounds\fR). .IP "\fB\-Wno\-coverage\-mismatch\fR" 4 .IX Item "-Wno-coverage-mismatch" Warn if feedback profiles do not match when using the *************** This warning is enabled by \fB\-Wall\fR *** 4094,4100 **** .IP "\fB\-Wunknown\-pragmas\fR" 4 .IX Item "-Wunknown-pragmas" Warn when a \f(CW\*(C`#pragma\*(C'\fR directive is encountered that is not understood by ! \&\s-1GCC.\s0 If this command-line option is used, warnings are even issued for unknown pragmas in system header files. This is not the case if the warnings are only enabled by the \fB\-Wall\fR command-line option. .IP "\fB\-Wno\-pragmas\fR" 4 --- 4101,4107 ---- .IP "\fB\-Wunknown\-pragmas\fR" 4 .IX Item "-Wunknown-pragmas" Warn when a \f(CW\*(C`#pragma\*(C'\fR directive is encountered that is not understood by ! \&\s-1GCC. \s0 If this command-line option is used, warnings are even issued for unknown pragmas in system header files. This is not the case if the warnings are only enabled by the \fB\-Wall\fR command-line option. .IP "\fB\-Wno\-pragmas\fR" 4 *************** probably mistaken. *** 4398,4404 **** .IP "\fB\-Wtraditional\fR (C and Objective-C only)" 4 .IX Item "-Wtraditional (C and Objective-C only)" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C.\s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and/or problematic constructs that should be avoided. .RS 4 .IP "*" 4 --- 4405,4411 ---- .IP "\fB\-Wtraditional\fR (C and Objective-C only)" 4 .IX Item "-Wtraditional (C and Objective-C only)" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and/or problematic constructs that should be avoided. .RS 4 .IP "*" 4 *************** except when the same as the default prom *** 4480,4486 **** .IX Item "-Wdeclaration-after-statement (C and Objective-C only)" Warn when a declaration is found after a statement in a block. This construct, known from \*(C+, was introduced with \s-1ISO C99\s0 and is by default ! allowed in \s-1GCC.\s0 It is not supported by \s-1ISO C90.\s0 .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" Warn if an undefined identifier is evaluated in an \f(CW\*(C`#if\*(C'\fR directive. --- 4487,4493 ---- .IX Item "-Wdeclaration-after-statement (C and Objective-C only)" Warn when a declaration is found after a statement in a block. This construct, known from \*(C+, was introduced with \s-1ISO C99\s0 and is by default ! allowed in \s-1GCC. \s0 It is not supported by \s-1ISO C90. \s0 .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" Warn if an undefined identifier is evaluated in an \f(CW\*(C`#if\*(C'\fR directive. *************** Warn about \s-1ISO C\s0 constructs that *** 4652,4663 **** .IX Item "-Wc++11-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 1998\s0 and \s-1ISO \*(C+ 2011,\s0 e.g., identifiers in \s-1ISO \*(C+ 1998\s0 that are keywords ! in \s-1ISO \*(C+ 2011.\s0 This warning turns on \fB\-Wnarrowing\fR and is enabled by \fB\-Wall\fR. .IP "\fB\-Wc++14\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wc++14-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 2011\s0 ! and \s-1ISO \*(C+ 2014.\s0 This warning is enabled by \fB\-Wall\fR. .IP "\fB\-Wcast\-qual\fR" 4 .IX Item "-Wcast-qual" Warn whenever a pointer is cast so as to remove a type qualifier from --- 4659,4670 ---- .IX Item "-Wc++11-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 1998\s0 and \s-1ISO \*(C+ 2011,\s0 e.g., identifiers in \s-1ISO \*(C+ 1998\s0 that are keywords ! in \s-1ISO \*(C+ 2011. \s0 This warning turns on \fB\-Wnarrowing\fR and is enabled by \fB\-Wall\fR. .IP "\fB\-Wc++14\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wc++14-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 2011\s0 ! and \s-1ISO \*(C+ 2014. \s0 This warning is enabled by \fB\-Wall\fR. .IP "\fB\-Wcast\-qual\fR" 4 .IX Item "-Wcast-qual" Warn whenever a pointer is cast so as to remove a type qualifier from *************** when applied ensure that two sequences t *** 4990,4996 **** the same sequence. \s-1GCC\s0 can warn you if you are using identifiers that have not been normalized; this option controls that warning. .Sp ! There are four levels of warning supported by \s-1GCC.\s0 The default is \&\fB\-Wnormalized=nfc\fR, which warns about any identifier that is not in the \s-1ISO 10646 \*(L"C\*(R"\s0 normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the recommended form for most uses. It is equivalent to --- 4997,5003 ---- the same sequence. \s-1GCC\s0 can warn you if you are using identifiers that have not been normalized; this option controls that warning. .Sp ! There are four levels of warning supported by \s-1GCC. \s0 The default is \&\fB\-Wnormalized=nfc\fR, which warns about any identifier that is not in the \s-1ISO 10646 \*(L"C\*(R"\s0 normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the recommended form for most uses. It is equivalent to *************** recommended form for most uses. It is e *** 4999,5006 **** Unfortunately, there are some characters allowed in identifiers by \&\s-1ISO C\s0 and \s-1ISO \*(C+\s0 that, when turned into \s-1NFC,\s0 are not allowed in identifiers. That is, there's no way to use these symbols in portable ! \&\s-1ISO C\s0 or \*(C+ and have all your identifiers in \s-1NFC.\s0 ! \&\fB\-Wnormalized=id\fR suppresses the warning for these characters. It is hoped that future versions of the standards involved will correct this, which is why this option is not the default. .Sp --- 5006,5013 ---- Unfortunately, there are some characters allowed in identifiers by \&\s-1ISO C\s0 and \s-1ISO \*(C+\s0 that, when turned into \s-1NFC,\s0 are not allowed in identifiers. That is, there's no way to use these symbols in portable ! \&\s-1ISO C\s0 or \*(C+ and have all your identifiers in \s-1NFC. ! \&\s0\fB\-Wnormalized=id\fR suppresses the warning for these characters. It is hoped that future versions of the standards involved will correct this, which is why this option is not the default. .Sp *************** standard's minimum limit, but very porta *** 5219,5225 **** using longer strings. .Sp The limit applies \fIafter\fR string constant concatenation, and does ! not count the trailing \s-1NUL.\s0 In C90, the limit was 509 characters; in C99, it was raised to 4095. \*(C+98 does not specify a normative minimum maximum, so we do not diagnose overlength strings in \*(C+. .Sp --- 5226,5232 ---- using longer strings. .Sp The limit applies \fIafter\fR string constant concatenation, and does ! not count the trailing \s-1NUL. \s0 In C90, the limit was 509 characters; in C99, it was raised to 4095. \*(C+98 does not specify a normative minimum maximum, so we do not diagnose overlength strings in \*(C+. .Sp *************** to generate the extra information, use \ *** 5276,5282 **** \&\fB\-gxcoff+\fR, \fB\-gxcoff\fR, or \fB\-gvms\fR (see below). .IP "\fB\-ggdb\fR" 4 .IX Item "-ggdb" ! Produce debugging information for use by \s-1GDB.\s0 This means to use the most expressive format available (\s-1DWARF,\s0 stabs, or the native format if neither of those are supported), including \s-1GDB\s0 extensions if at all possible. --- 5283,5289 ---- \&\fB\-gxcoff+\fR, \fB\-gxcoff\fR, or \fB\-gvms\fR (see below). .IP "\fB\-ggdb\fR" 4 .IX Item "-ggdb" ! Produce debugging information for use by \s-1GDB. \s0 This means to use the most expressive format available (\s-1DWARF,\s0 stabs, or the native format if neither of those are supported), including \s-1GDB\s0 extensions if at all possible. *************** be useful, this option requires a debugg *** 5419,5425 **** files. .IP "\fB\-gpubnames\fR" 4 .IX Item "-gpubnames" ! Generate \s-1DWARF\s0 \f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections. .IP "\fB\-ggnu\-pubnames\fR" 4 .IX Item "-ggnu-pubnames" Generate \f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections in a format --- 5426,5432 ---- files. .IP "\fB\-gpubnames\fR" 4 .IX Item "-gpubnames" ! Generate \s-1DWARF \s0\f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections. .IP "\fB\-ggnu\-pubnames\fR" 4 .IX Item "-ggnu-pubnames" Generate \f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections in a format *************** This option works only with \s-1DWARF\s0 *** 5547,5553 **** .IP "\fB\-fno\-dwarf2\-cfi\-asm\fR" 4 .IX Item "-fno-dwarf2-cfi-asm" Emit \s-1DWARF\s0 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section ! instead of using \s-1GAS\s0 \f(CW\*(C`.cfi_*\*(C'\fR directives. .IP "\fB\-fno\-eliminate\-unused\-debug\-types\fR" 4 .IX Item "-fno-eliminate-unused-debug-types" Normally, when producing \s-1DWARF\s0 output, \s-1GCC\s0 avoids producing debug symbol --- 5554,5560 ---- .IP "\fB\-fno\-dwarf2\-cfi\-asm\fR" 4 .IX Item "-fno-dwarf2-cfi-asm" Emit \s-1DWARF\s0 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section ! instead of using \s-1GAS \s0\f(CW\*(C`.cfi_*\*(C'\fR directives. .IP "\fB\-fno\-eliminate\-unused\-debug\-types\fR" 4 .IX Item "-fno-eliminate-unused-debug-types" Normally, when producing \s-1DWARF\s0 output, \s-1GCC\s0 avoids producing debug symbol *************** function calls and pops them all at once *** 5758,5764 **** Disabled at levels \fB\-O\fR, \fB\-O2\fR, \fB\-O3\fR, \fB\-Os\fR. .IP "\fB\-fforward\-propagate\fR" 4 .IX Item "-fforward-propagate" ! Perform a forward propagation pass on \s-1RTL.\s0 The pass tries to combine two instructions and checks if the result can be simplified. If loop unrolling is active, two passes are performed and the second is scheduled after loop unrolling. --- 5765,5771 ---- Disabled at levels \fB\-O\fR, \fB\-O2\fR, \fB\-O3\fR, \fB\-Os\fR. .IP "\fB\-fforward\-propagate\fR" 4 .IX Item "-fforward-propagate" ! Perform a forward propagation pass on \s-1RTL. \s0 The pass tries to combine two instructions and checks if the result can be simplified. If loop unrolling is active, two passes are performed and the second is scheduled after loop unrolling. *************** attribute or declspec *** 5909,5915 **** In C, emit \f(CW\*(C`static\*(C'\fR functions that are declared \f(CW\*(C`inline\*(C'\fR into the object file, even if the function has been inlined into all of its callers. This switch does not affect functions using the ! \&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU C90.\s0 In \*(C+, emit any and all inline functions into the object file. .IP "\fB\-fkeep\-static\-functions\fR" 4 .IX Item "-fkeep-static-functions" --- 5916,5922 ---- In C, emit \f(CW\*(C`static\*(C'\fR functions that are declared \f(CW\*(C`inline\*(C'\fR into the object file, even if the function has been inlined into all of its callers. This switch does not affect functions using the ! \&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU C90. \s0 In \*(C+, emit any and all inline functions into the object file. .IP "\fB\-fkeep\-static\-functions\fR" 4 .IX Item "-fkeep-static-functions" *************** The default is \fB\-ffunction\-cse\fR *** 5983,5989 **** .IP "\fB\-fno\-zero\-initialized\-in\-bss\fR" 4 .IX Item "-fno-zero-initialized-in-bss" If the target supports a \s-1BSS\s0 section, \s-1GCC\s0 by default puts variables that ! are initialized to zero into \s-1BSS.\s0 This can save space in the resulting code. .Sp This option turns off this behavior because some programs explicitly --- 5990,5996 ---- .IP "\fB\-fno\-zero\-initialized\-in\-bss\fR" 4 .IX Item "-fno-zero-initialized-in-bss" If the target supports a \s-1BSS\s0 section, \s-1GCC\s0 by default puts variables that ! are initialized to zero into \s-1BSS. \s0 This can save space in the resulting code. .Sp This option turns off this behavior because some programs explicitly *************** pseudo-register that does not get a hard *** 6278,6284 **** stack slot, and as a result function stack frames are larger. .IP "\fB\-flra\-remat\fR" 4 .IX Item "-flra-remat" ! Enable CFG-sensitive rematerialization in \s-1LRA.\s0 Instead of loading values of spilled pseudos, \s-1LRA\s0 tries to rematerialize (recalculate) values if it is profitable. .Sp --- 6285,6291 ---- stack slot, and as a result function stack frames are larger. .IP "\fB\-flra\-remat\fR" 4 .IX Item "-flra-remat" ! Enable CFG-sensitive rematerialization in \s-1LRA. \s0 Instead of loading values of spilled pseudos, \s-1LRA\s0 tries to rematerialize (recalculate) values if it is profitable. .Sp *************** transformation infrastructure. *** 6691,6697 **** Enable the identity transformation for graphite. For every SCoP we generate the polyhedral representation and transform it back to gimple. Using \&\fB\-fgraphite\-identity\fR we can check the costs or benefits of the ! \&\s-1GIMPLE\s0 \-> \s-1GRAPHITE\s0 \-> \s-1GIMPLE\s0 transformation. Some minimal optimizations are also performed by the code generator isl, like index splitting and dead code elimination in loops. .IP "\fB\-floop\-nest\-optimize\fR" 4 --- 6698,6704 ---- Enable the identity transformation for graphite. For every SCoP we generate the polyhedral representation and transform it back to gimple. Using \&\fB\-fgraphite\-identity\fR we can check the costs or benefits of the ! \&\s-1GIMPLE \-\s0> \s-1GRAPHITE \-\s0> \s-1GIMPLE\s0 transformation. Some minimal optimizations are also performed by the code generator isl, like index splitting and dead code elimination in loops. .IP "\fB\-floop\-nest\-optimize\fR" 4 *************** information. *** 7207,7213 **** .IP "\fB\-flto[=\fR\fIn\fR\fB]\fR" 4 .IX Item "-flto[=n]" This option runs the standard link-time optimizer. When invoked ! with source code, it generates \s-1GIMPLE\s0 (one of \s-1GCC\s0's internal representations) and writes it to special \s-1ELF\s0 sections in the object file. When the object files are linked together, all the function bodies are read from these \s-1ELF\s0 sections and instantiated as if they --- 7214,7220 ---- .IP "\fB\-flto[=\fR\fIn\fR\fB]\fR" 4 .IX Item "-flto[=n]" This option runs the standard link-time optimizer. When invoked ! with source code, it generates \s-1GIMPLE \s0(one of \s-1GCC\s0's internal representations) and writes it to special \s-1ELF\s0 sections in the object file. When the object files are linked together, all the function bodies are read from these \s-1ELF\s0 sections and instantiated as if they *************** E.g. *** 7547,7553 **** .Ve .Sp Then use the \fBcreate_gcov\fR tool to convert the raw profile data ! to a format that can be used by \s-1GCC.\s0 You must also supply the unstripped binary for your program to this tool. See <\fBhttps://github.com/google/autofdo\fR>. .Sp --- 7554,7560 ---- .Ve .Sp Then use the \fBcreate_gcov\fR tool to convert the raw profile data ! to a format that can be used by \s-1GCC. \s0 You must also supply the unstripped binary for your program to this tool. See <\fBhttps://github.com/google/autofdo\fR>. .Sp *************** them to store all pertinent intermediate *** 7577,7584 **** .IP "\fB\-fexcess\-precision=\fR\fIstyle\fR" 4 .IX Item "-fexcess-precision=style" This option allows further control over excess precision on machines ! where floating-point registers have more precision than the \s-1IEEE\s0 ! \&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not support operations rounding to those types. By default, \&\fB\-fexcess\-precision=fast\fR is in effect; this means that operations are carried out in the precision of the registers and that --- 7584,7591 ---- .IP "\fB\-fexcess\-precision=\fR\fIstyle\fR" 4 .IX Item "-fexcess-precision=style" This option allows further control over excess precision on machines ! where floating-point registers have more precision than the \s-1IEEE ! \&\s0\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not support operations rounding to those types. By default, \&\fB\-fexcess\-precision=fast\fR is in effect; this means that operations are carried out in the precision of the registers and that *************** whether the result of a complex multipli *** 7752,7759 **** default is \fB\-fno\-cx\-limited\-range\fR, but is enabled by \&\fB\-ffast\-math\fR. .Sp ! This option controls the default setting of the \s-1ISO C99\s0 ! \&\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to all languages. .IP "\fB\-fcx\-fortran\-rules\fR" 4 .IX Item "-fcx-fortran-rules" --- 7759,7766 ---- default is \fB\-fno\-cx\-limited\-range\fR, but is enabled by \&\fB\-ffast\-math\fR. .Sp ! This option controls the default setting of the \s-1ISO C99 ! \&\s0\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to all languages. .IP "\fB\-fcx\-fortran\-rules\fR" 4 .IX Item "-fcx-fortran-rules" *************** Tuning this may improve compilation spee *** 8358,8364 **** generation. .Sp The default is 30% + 70% * (\s-1RAM/1GB\s0) with an upper bound of 100% when ! \&\s-1RAM\s0 >= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\*(R"\s0 is the smallest of actual \s-1RAM\s0 and \f(CW\*(C`RLIMIT_DATA\*(C'\fR or \f(CW\*(C`RLIMIT_AS\*(C'\fR. If \&\s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower bound of 30% is used. Setting this parameter and --- 8365,8371 ---- generation. .Sp The default is 30% + 70% * (\s-1RAM/1GB\s0) with an upper bound of 100% when ! \&\s-1RAM \s0>= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\*(R"\s0 is the smallest of actual \s-1RAM\s0 and \f(CW\*(C`RLIMIT_DATA\*(C'\fR or \f(CW\*(C`RLIMIT_AS\*(C'\fR. If \&\s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower bound of 30% is used. Setting this parameter and *************** This value is the best found from numero *** 8582,8588 **** This optimization is called inheritance. \s-1EBB\s0 is used as a region to do this optimization. The parameter defines a minimal fall-through edge probability in percentage used to add \s-1BB\s0 to inheritance \s-1EBB\s0 in ! \&\s-1LRA.\s0 The default value of the parameter is 40. The value was chosen from numerous runs of \s-1SPEC2000\s0 on x86\-64. .IP "\fBloop-invariant-max-bbs-in-loop\fR" 4 .IX Item "loop-invariant-max-bbs-in-loop" --- 8589,8595 ---- This optimization is called inheritance. \s-1EBB\s0 is used as a region to do this optimization. The parameter defines a minimal fall-through edge probability in percentage used to add \s-1BB\s0 to inheritance \s-1EBB\s0 in ! \&\s-1LRA. \s0 The default value of the parameter is 40. The value was chosen from numerous runs of \s-1SPEC2000\s0 on x86\-64. .IP "\fBloop-invariant-max-bbs-in-loop\fR" 4 .IX Item "loop-invariant-max-bbs-in-loop" *************** The number of partitions should exceed t *** 8724,8730 **** The default value is 32. .IP "\fBlto-min-partition\fR" 4 .IX Item "lto-min-partition" ! Size of minimal partition for \s-1WHOPR\s0 (in estimated instructions). This prevents expenses of splitting very small programs into too many partitions. .IP "\fBcxx-max-namespaces-for-diagnostic-help\fR" 4 --- 8731,8737 ---- The default value is 32. .IP "\fBlto-min-partition\fR" 4 .IX Item "lto-min-partition" ! Size of minimal partition for \s-1WHOPR \s0(in estimated instructions). This prevents expenses of splitting very small programs into too many partitions. .IP "\fBcxx-max-namespaces-for-diagnostic-help\fR" 4 *************** get trigraph conversion without warnings *** 9647,9653 **** .IP "\fB\-Wtraditional\fR" 4 .IX Item "-Wtraditional" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C.\s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and problematic constructs which should be avoided. .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" --- 9654,9660 ---- .IP "\fB\-Wtraditional\fR" 4 .IX Item "-Wtraditional" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and problematic constructs which should be avoided. .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" *************** When \fB\-fpreprocessed\fR is in use, \s *** 9843,9849 **** and loads the \s-1PCH.\s0 .Sp This option is off by default, because the resulting preprocessed output ! is only really suitable as input to \s-1GCC.\s0 It is switched on by \&\fB\-save\-temps\fR. .Sp You should not write this \f(CW\*(C`#pragma\*(C'\fR in your own code, but it is --- 9850,9856 ---- and loads the \s-1PCH.\s0 .Sp This option is off by default, because the resulting preprocessed output ! is only really suitable as input to \s-1GCC. \s0 It is switched on by \&\fB\-save\-temps\fR. .Sp You should not write this \f(CW\*(C`#pragma\*(C'\fR in your own code, but it is *************** line. If the value is less than 1 or gr *** 10115,10121 **** ignored. The default is 8. .IP "\fB\-fdebug\-cpp\fR" 4 .IX Item "-fdebug-cpp" ! This option is only useful for debugging \s-1GCC.\s0 When used with \&\fB\-E\fR, dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. The dump of the map holding the location of a token would --- 10122,10128 ---- ignored. The default is 8. .IP "\fB\-fdebug\-cpp\fR" 4 .IX Item "-fdebug-cpp" ! This option is only useful for debugging \s-1GCC. \s0 When used with \&\fB\-E\fR, dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. The dump of the map holding the location of a token would *************** Note that \f(CW\*(C`\-ftrack\-macro\-exp *** 10148,10154 **** .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fexec-charset=charset" Set the execution character set, used for string and character ! constants. The default is \s-1UTF\-8.\s0 \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fwide-exec-charset=charset" --- 10155,10161 ---- .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fexec-charset=charset" Set the execution character set, used for string and character ! constants. The default is \s-1UTF\-8. \s0\fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fwide-exec-charset=charset" *************** problems with encodings that do not fit *** 10161,10169 **** .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 .IX Item "-finput-charset=charset" Set the input character set, used for translation from the character ! set of the input file to the source character set used by \s-1GCC.\s0 If the locale does not specify, or \s-1GCC\s0 cannot get this information from the ! locale, the default is \s-1UTF\-8.\s0 This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. --- 10168,10176 ---- .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 .IX Item "-finput-charset=charset" Set the input character set, used for translation from the character ! set of the input file to the source character set used by \s-1GCC. \s0 If the locale does not specify, or \s-1GCC\s0 cannot get this information from the ! locale, the default is \s-1UTF\-8. \s0 This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. *************** the \s-1GOT\s0 size for the linked execu *** 11039,11045 **** maximum size, you get an error message from the linker indicating that \&\fB\-fpic\fR does not work; in that case, recompile with \fB\-fPIC\fR instead. (These maximums are 8k on the \s-1SPARC,\s0 28k on AArch64 and 32k ! on the m68k and \s-1RS/6000.\s0 The x86 has no such limit.) .Sp Position-independent code requires special support, and therefore works only on certain machines. For the x86, \s-1GCC\s0 supports \s-1PIC\s0 for System V --- 11046,11052 ---- maximum size, you get an error message from the linker indicating that \&\fB\-fpic\fR does not work; in that case, recompile with \fB\-fPIC\fR instead. (These maximums are 8k on the \s-1SPARC,\s0 28k on AArch64 and 32k ! on the m68k and \s-1RS/6000. \s0 The x86 has no such limit.) .Sp Position-independent code requires special support, and therefore works only on certain machines. For the x86, \s-1GCC\s0 supports \s-1PIC\s0 for System V *************** Enable showing virtual operands for ever *** 11721,11727 **** Enable showing line numbers for statements. .IP "\fBuid\fR" 4 .IX Item "uid" ! Enable showing the unique \s-1ID\s0 (\f(CW\*(C`DECL_UID\*(C'\fR) for each variable. .IP "\fBverbose\fR" 4 .IX Item "verbose" Enable showing the tree dump for each statement. --- 11728,11734 ---- Enable showing line numbers for statements. .IP "\fBuid\fR" 4 .IX Item "uid" ! Enable showing the unique \s-1ID \s0(\f(CW\*(C`DECL_UID\*(C'\fR) for each variable. .IP "\fBverbose\fR" 4 .IX Item "verbose" Enable showing the tree dump for each statement. *************** Dump aliasing information for each funct *** 11803,11809 **** appending \fI.alias\fR to the source file name. .IP "\fBccp\fR" 4 .IX Item "ccp" ! Dump each function after \s-1CCP.\s0 The file name is made by appending \&\fI.ccp\fR to the source file name. .IP "\fBstoreccp\fR" 4 .IX Item "storeccp" --- 11810,11816 ---- appending \fI.alias\fR to the source file name. .IP "\fBccp\fR" 4 .IX Item "ccp" ! Dump each function after \s-1CCP. \s0 The file name is made by appending \&\fI.ccp\fR to the source file name. .IP "\fBstoreccp\fR" 4 .IX Item "storeccp" *************** values for \fIcpu\fR are *** 12825,12845 **** .IP "\fBarc600\fR" 4 .IX Item "arc600" .PD ! Compile for \s-1ARC600.\s0 Aliases: \fB\-mA6\fR, \fB\-mARC600\fR. .IP "\fB\s-1ARC601\s0\fR" 4 .IX Item "ARC601" .PD 0 .IP "\fBarc601\fR" 4 .IX Item "arc601" .PD ! Compile for \s-1ARC601.\s0 Alias: \fB\-mARC601\fR. .IP "\fB\s-1ARC700\s0\fR" 4 .IX Item "ARC700" .PD 0 .IP "\fBarc700\fR" 4 .IX Item "arc700" .PD ! Compile for \s-1ARC700.\s0 Aliases: \fB\-mA7\fR, \fB\-mARC700\fR. This is the default when configured with \fB\-\-with\-cpu=arc700\fR. .IP "\fB\s-1ARCEM\s0\fR" 4 .IX Item "ARCEM" --- 12832,12852 ---- .IP "\fBarc600\fR" 4 .IX Item "arc600" .PD ! Compile for \s-1ARC600. \s0 Aliases: \fB\-mA6\fR, \fB\-mARC600\fR. .IP "\fB\s-1ARC601\s0\fR" 4 .IX Item "ARC601" .PD 0 .IP "\fBarc601\fR" 4 .IX Item "arc601" .PD ! Compile for \s-1ARC601. \s0 Alias: \fB\-mARC601\fR. .IP "\fB\s-1ARC700\s0\fR" 4 .IX Item "ARC700" .PD 0 .IP "\fBarc700\fR" 4 .IX Item "arc700" .PD ! Compile for \s-1ARC700. \s0 Aliases: \fB\-mA7\fR, \fB\-mARC700\fR. This is the default when configured with \fB\-\-with\-cpu=arc700\fR. .IP "\fB\s-1ARCEM\s0\fR" 4 .IX Item "ARCEM" *************** Replaced by \fB\-mmultcost\fR. *** 13359,13365 **** These \fB\-m\fR options are defined for the \s-1ARM\s0 port: .IP "\fB\-mabi=\fR\fIname\fR" 4 .IX Item "-mabi=name" ! Generate code for the specified \s-1ABI.\s0 Permissible values are: \fBapcs-gnu\fR, \&\fBatpcs\fR, \fBaapcs\fR, \fBaapcs-linux\fR and \fBiwmmxt\fR. .IP "\fB\-mapcs\-frame\fR" 4 .IX Item "-mapcs-frame" --- 13366,13372 ---- These \fB\-m\fR options are defined for the \s-1ARM\s0 port: .IP "\fB\-mabi=\fR\fIname\fR" 4 .IX Item "-mabi=name" ! Generate code for the specified \s-1ABI. \s0 Permissible values are: \fBapcs-gnu\fR, \&\fBatpcs\fR, \fBaapcs\fR, \fBaapcs-linux\fR and \fBiwmmxt\fR. .IP "\fB\-mapcs\-frame\fR" 4 .IX Item "-mapcs-frame" *************** The default for this option is@tie{}\fBa *** 13822,13829 **** .ie n .IP """avrxmega5""" 4 .el .IP "\f(CWavrxmega5\fR" 4 .IX Item "avrxmega5" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.\s0 ! \&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR. .ie n .IP """avrxmega6""" 4 .el .IP "\f(CWavrxmega6\fR" 4 .IX Item "avrxmega6" --- 13829,13836 ---- .ie n .IP """avrxmega5""" 4 .el .IP "\f(CWavrxmega5\fR" 4 .IX Item "avrxmega5" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM. ! \&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR. .ie n .IP """avrxmega6""" 4 .el .IP "\f(CWavrxmega6\fR" 4 .IX Item "avrxmega6" *************** The default for this option is@tie{}\fBa *** 13832,13839 **** .ie n .IP """avrxmega7""" 4 .el .IP "\f(CWavrxmega7\fR" 4 .IX Item "avrxmega7" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.\s0 ! \&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR. .ie n .IP """avrtiny""" 4 .el .IP "\f(CWavrtiny\fR" 4 .IX Item "avrtiny" --- 13839,13846 ---- .ie n .IP """avrxmega7""" 4 .el .IP "\f(CWavrxmega7\fR" 4 .IX Item "avrxmega7" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM. ! \&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR. .ie n .IP """avrtiny""" 4 .el .IP "\f(CWavrtiny\fR" 4 .IX Item "avrtiny" *************** for \fImcu\fR=\f(CW\*(C`avrtiny\*(C'\fR, *** 14154,14160 **** If \fImcu\fR specifies a device, this built-in macro is set accordingly. For example, with \fB\-mmcu=atmega8\fR the macro is defined to \f(CW4\fR. ! .ie n .IP """_\|_AVR_\fIDevice\fP_\|_""" 4 .el .IP "\f(CW_\|_AVR_\f(CIDevice\f(CW_\|_\fR" 4 .IX Item "__AVR_Device__" Setting \fB\-mmcu=\fR\fIdevice\fR defines this built-in macro which reflects --- 14161,14167 ---- If \fImcu\fR specifies a device, this built-in macro is set accordingly. For example, with \fB\-mmcu=atmega8\fR the macro is defined to \f(CW4\fR. ! .ie n .IP """_\|_AVR_\f(CIDevice\f(CW_\|_""" 4 .el .IP "\f(CW_\|_AVR_\f(CIDevice\f(CW_\|_\fR" 4 .IX Item "__AVR_Device__" Setting \fB\-mmcu=\fR\fIdevice\fR defines this built-in macro which reflects *************** The definition of these macros is affect *** 14248,14254 **** .el .IP "\f(CW_\|_AVR_SP8_\|_\fR" 4 .IX Item "__AVR_SP8__" .PD ! The device has the \s-1SPH\s0 (high part of stack pointer) special function register or has an 8\-bit stack pointer, respectively. The definition of these macros is affected by \fB\-mmcu=\fR and in the cases of \fB\-mmcu=avr2\fR and \fB\-mmcu=avr25\fR also --- 14255,14261 ---- .el .IP "\f(CW_\|_AVR_SP8_\|_\fR" 4 .IX Item "__AVR_SP8__" .PD ! The device has the \s-1SPH \s0(high part of stack pointer) special function register or has an 8\-bit stack pointer, respectively. The definition of these macros is affected by \fB\-mmcu=\fR and in the cases of \fB\-mmcu=avr2\fR and \fB\-mmcu=avr25\fR also *************** set. *** 14290,14296 **** .el .IP "\f(CW_\|_AVR_ISA_RMW_\|_\fR" 4 .IX Item "__AVR_ISA_RMW__" The device has Read-Modify-Write instructions (\s-1XCH, LAC, LAS\s0 and \s-1LAT\s0). ! .ie n .IP """_\|_AVR_SFR_OFFSET_\|_=\fIoffset\fP""" 4 .el .IP "\f(CW_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW\fR" 4 .IX Item "__AVR_SFR_OFFSET__=offset" Instructions that can address I/O special function registers directly --- 14297,14303 ---- .el .IP "\f(CW_\|_AVR_ISA_RMW_\|_\fR" 4 .IX Item "__AVR_ISA_RMW__" The device has Read-Modify-Write instructions (\s-1XCH, LAC, LAS\s0 and \s-1LAT\s0). ! .ie n .IP """_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW""" 4 .el .IP "\f(CW_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW\fR" 4 .IX Item "__AVR_SFR_OFFSET__=offset" Instructions that can address I/O special function registers directly *************** or storage for local variables needs to *** 14626,14632 **** With \fB\-fpic\fR and \fB\-fPIC\fR, don't generate (do generate) instruction sequences that load addresses for functions from the \s-1PLT\s0 part of the \s-1GOT\s0 rather than (traditional on other architectures) calls to the ! \&\s-1PLT.\s0 The default is \fB\-mgotplt\fR. .IP "\fB\-melf\fR" 4 .IX Item "-melf" Legacy no-op option only recognized with the cris-axis-elf and --- 14633,14639 ---- With \fB\-fpic\fR and \fB\-fPIC\fR, don't generate (do generate) instruction sequences that load addresses for functions from the \s-1PLT\s0 part of the \s-1GOT\s0 rather than (traditional on other architectures) calls to the ! \&\s-1PLT. \s0 The default is \fB\-mgotplt\fR. .IP "\fB\-melf\fR" 4 .IX Item "-melf" Legacy no-op option only recognized with the cris-axis-elf and *************** compilers call this option \fB\-ieee_wit *** 14992,14998 **** .IP "\fB\-mieee\-with\-inexact\fR" 4 .IX Item "-mieee-with-inexact" This is like \fB\-mieee\fR except the generated code also maintains ! the \s-1IEEE\s0 \fIinexact-flag\fR. Turning on this option causes the generated code to implement fully-compliant \s-1IEEE\s0 math. In addition to \&\f(CW\*(C`_IEEE_FP\*(C'\fR, \f(CW\*(C`_IEEE_FP_EXACT\*(C'\fR is defined as a preprocessor macro. On some Alpha implementations the resulting code may execute --- 14999,15005 ---- .IP "\fB\-mieee\-with\-inexact\fR" 4 .IX Item "-mieee-with-inexact" This is like \fB\-mieee\fR except the generated code also maintains ! the \s-1IEEE \s0\fIinexact-flag\fR. Turning on this option causes the generated code to implement fully-compliant \s-1IEEE\s0 math. In addition to \&\f(CW\*(C`_IEEE_FP\*(C'\fR, \f(CW\*(C`_IEEE_FP_EXACT\*(C'\fR is defined as a preprocessor macro. On some Alpha implementations the resulting code may execute *************** These \fB\-m\fR options are defined for *** 15621,15627 **** .IP "\fB\-march=\fR\fIarchitecture-type\fR" 4 .IX Item "-march=architecture-type" Generate code for the specified architecture. The choices for ! \&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA 1.0,\s0 \fB1.1\fR for \s-1PA 1.1,\s0 and \fB2.0\fR for \s-1PA 2.0\s0 processors. Refer to \&\fI/usr/lib/sched.models\fR on an HP-UX system to determine the proper architecture option for your machine. Code compiled for lower numbered --- 15628,15634 ---- .IP "\fB\-march=\fR\fIarchitecture-type\fR" 4 .IX Item "-march=architecture-type" Generate code for the specified architecture. The choices for ! \&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA 1.0, \s0\fB1.1\fR for \s-1PA 1.1,\s0 and \fB2.0\fR for \s-1PA 2.0\s0 processors. Refer to \&\fI/usr/lib/sched.models\fR on an HP-UX system to determine the proper architecture option for your machine. Code compiled for lower numbered *************** library that comes with \s-1GCC,\s0 with *** 15709,15721 **** this to work. .IP "\fB\-msio\fR" 4 .IX Item "-msio" ! Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO.\s0 The default is \&\fB\-mwsio\fR. This generates the predefines, \f(CW\*(C`_\|_hp9000s700\*(C'\fR, ! \&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO.\s0 These options are available under HP-UX and HI-UX. .IP "\fB\-mgnu\-ld\fR" 4 .IX Item "-mgnu-ld" ! Use options specific to \s-1GNU\s0 \fBld\fR. This passes \fB\-shared\fR to \fBld\fR when building a shared library. It is the default when \s-1GCC\s0 is configured, explicitly or implicitly, with the \s-1GNU\s0 linker. This option does not --- 15716,15728 ---- this to work. .IP "\fB\-msio\fR" 4 .IX Item "-msio" ! Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO. \s0 The default is \&\fB\-mwsio\fR. This generates the predefines, \f(CW\*(C`_\|_hp9000s700\*(C'\fR, ! \&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO. \s0 These options are available under HP-UX and HI-UX. .IP "\fB\-mgnu\-ld\fR" 4 .IX Item "-mgnu-ld" ! Use options specific to \s-1GNU \s0\fBld\fR. This passes \fB\-shared\fR to \fBld\fR when building a shared library. It is the default when \s-1GCC\s0 is configured, explicitly or implicitly, with the \s-1GNU\s0 linker. This option does not *************** using \fBwhich `gcc \-print\-prog\-name= *** 15728,15734 **** on the 64\-bit HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR. .IP "\fB\-mhp\-ld\fR" 4 .IX Item "-mhp-ld" ! Use options specific to \s-1HP\s0 \fBld\fR. This passes \fB\-b\fR to \fBld\fR when building a shared library and passes \fB+Accept TypeMismatch\fR to \fBld\fR on all links. It is the default when \s-1GCC\s0 is configured, explicitly or --- 15735,15741 ---- on the 64\-bit HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR. .IP "\fB\-mhp\-ld\fR" 4 .IX Item "-mhp-ld" ! Use options specific to \s-1HP \s0\fBld\fR. This passes \fB\-b\fR to \fBld\fR when building a shared library and passes \fB+Accept TypeMismatch\fR to \fBld\fR on all links. It is the default when \s-1GCC\s0 is configured, explicitly or *************** have to be emulated by software on the 6 *** 16395,16401 **** does not have code to emulate those instructions. .IP "\fB\-mcpu32\fR" 4 .IX Item "-mcpu32" ! Generate output for a \s-1CPU32.\s0 This is the default when the compiler is configured for CPU32\-based systems. It is equivalent to \fB\-march=cpu32\fR. .Sp --- 16402,16408 ---- does not have code to emulate those instructions. .IP "\fB\-mcpu32\fR" 4 .IX Item "-mcpu32" ! Generate output for a \s-1CPU32. \s0 This is the default when the compiler is configured for CPU32\-based systems. It is equivalent to \fB\-march=cpu32\fR. .Sp *************** Use this option for microcontrollers wit *** 16404,16410 **** 68336, 68340, 68341, 68349 and 68360. .IP "\fB\-m5200\fR" 4 .IX Item "-m5200" ! Generate output for a 520X ColdFire \s-1CPU.\s0 This is the default when the compiler is configured for 520X\-based systems. It is equivalent to \fB\-mcpu=5206\fR, and is now deprecated in favor of that option. --- 16411,16417 ---- 68336, 68340, 68341, 68349 and 68360. .IP "\fB\-m5200\fR" 4 .IX Item "-m5200" ! Generate output for a 520X ColdFire \s-1CPU. \s0 This is the default when the compiler is configured for 520X\-based systems. It is equivalent to \fB\-mcpu=5206\fR, and is now deprecated in favor of that option. *************** Use this option for microcontroller with *** 16413,16419 **** the \s-1MCF5202, MCF5203, MCF5204\s0 and \s-1MCF5206.\s0 .IP "\fB\-m5206e\fR" 4 .IX Item "-m5206e" ! Generate output for a 5206e ColdFire \s-1CPU.\s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5206e\fR. .IP "\fB\-m528x\fR" 4 .IX Item "-m528x" --- 16420,16426 ---- the \s-1MCF5202, MCF5203, MCF5204\s0 and \s-1MCF5206.\s0 .IP "\fB\-m5206e\fR" 4 .IX Item "-m5206e" ! Generate output for a 5206e ColdFire \s-1CPU. \s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5206e\fR. .IP "\fB\-m528x\fR" 4 .IX Item "-m528x" *************** The option is now deprecated in favor of *** 16422,16436 **** \&\fB\-mcpu=528x\fR. .IP "\fB\-m5307\fR" 4 .IX Item "-m5307" ! Generate output for a ColdFire 5307 \s-1CPU.\s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5307\fR. .IP "\fB\-m5407\fR" 4 .IX Item "-m5407" ! Generate output for a ColdFire 5407 \s-1CPU.\s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5407\fR. .IP "\fB\-mcfv4e\fR" 4 .IX Item "-mcfv4e" ! Generate output for a ColdFire V4e family \s-1CPU\s0 (e.g. 547x/548x). This includes use of hardware floating-point instructions. The option is equivalent to \fB\-mcpu=547x\fR, and is now deprecated in favor of that option. --- 16429,16443 ---- \&\fB\-mcpu=528x\fR. .IP "\fB\-m5307\fR" 4 .IX Item "-m5307" ! Generate output for a ColdFire 5307 \s-1CPU. \s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5307\fR. .IP "\fB\-m5407\fR" 4 .IX Item "-m5407" ! Generate output for a ColdFire 5407 \s-1CPU. \s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5407\fR. .IP "\fB\-mcfv4e\fR" 4 .IX Item "-mcfv4e" ! Generate output for a ColdFire V4e family \s-1CPU \s0(e.g. 547x/548x). This includes use of hardware floating-point instructions. The option is equivalent to \fB\-mcpu=547x\fR, and is now deprecated in favor of that option. *************** The option is equivalent to \fB\-march=6 *** 16457,16463 **** .IX Item "-m68881" .PD Generate floating-point instructions. This is the default for 68020 ! and above, and for ColdFire devices that have an \s-1FPU.\s0 It defines the macro \f(CW\*(C`_\|_HAVE_68881_\|_\*(C'\fR on M680x0 targets and \f(CW\*(C`_\|_mcffpu_\|_\*(C'\fR on ColdFire targets. .IP "\fB\-msoft\-float\fR" 4 --- 16464,16470 ---- .IX Item "-m68881" .PD Generate floating-point instructions. This is the default for 68020 ! and above, and for ColdFire devices that have an \s-1FPU. \s0 It defines the macro \f(CW\*(C`_\|_HAVE_68881_\|_\*(C'\fR on M680x0 targets and \f(CW\*(C`_\|_mcffpu_\|_\*(C'\fR on ColdFire targets. .IP "\fB\-msoft\-float\fR" 4 *************** the default for ColdFire devices that ha *** 16474,16481 **** Generate (do not generate) ColdFire hardware divide and remainder instructions. If \fB\-march\fR is used without \fB\-mcpu\fR, the default is \*(L"on\*(R" for ColdFire architectures and \*(L"off\*(R" for M680x0 ! architectures. Otherwise, the default is taken from the target \s-1CPU\s0 ! (either the default \s-1CPU,\s0 or the one specified by \fB\-mcpu\fR). For example, the default is \*(L"off\*(R" for \fB\-mcpu=5206\fR and \*(L"on\*(R" for \&\fB\-mcpu=5206e\fR. .Sp --- 16481,16488 ---- Generate (do not generate) ColdFire hardware divide and remainder instructions. If \fB\-march\fR is used without \fB\-mcpu\fR, the default is \*(L"on\*(R" for ColdFire architectures and \*(L"off\*(R" for M680x0 ! architectures. Otherwise, the default is taken from the target \s-1CPU ! \&\s0(either the default \s-1CPU,\s0 or the one specified by \fB\-mcpu\fR). For example, the default is \*(L"off\*(R" for \fB\-mcpu=5206\fR and \*(L"on\*(R" for \&\fB\-mcpu=5206e\fR. .Sp *************** The processor names are: *** 16960,16966 **** \&\fBvr5000\fR, \fBvr5400\fR, \fBvr5500\fR, \&\fBxlr\fR and \fBxlp\fR. The special value \fBfrom-abi\fR selects the ! most compatible architecture for the selected \s-1ABI\s0 (that is, \&\fBmips1\fR for 32\-bit ABIs and \fBmips3\fR for 64\-bit ABIs). .Sp The native Linux/GNU toolchain also supports the value \fBnative\fR, --- 16967,16973 ---- \&\fBvr5000\fR, \fBvr5400\fR, \fBvr5500\fR, \&\fBxlr\fR and \fBxlp\fR. The special value \fBfrom-abi\fR selects the ! most compatible architecture for the selected \s-1ABI \s0(that is, \&\fBmips1\fR for 32\-bit ABIs and \fBmips3\fR for 64\-bit ABIs). .Sp The native Linux/GNU toolchain also supports the value \fBnative\fR, *************** remains the same in that the even-number *** 17123,17130 **** are saved. .Sp Two additional variants of the o32 \s-1ABI\s0 are supported to enable ! a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX\s0 ! (\fB\-mfpxx\fR) and \s-1FP64A\s0 (\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR). The \s-1FPXX\s0 extension mandates that all code must execute correctly when run using 32\-bit or 64\-bit registers. The code can be interlinked with either \s-1FP32\s0 or \s-1FP64,\s0 but not both. --- 17130,17137 ---- are saved. .Sp Two additional variants of the o32 \s-1ABI\s0 are supported to enable ! a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX ! \&\s0(\fB\-mfpxx\fR) and \s-1FP64A \s0(\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR). The \s-1FPXX\s0 extension mandates that all code must execute correctly when run using 32\-bit or 64\-bit registers. The code can be interlinked with either \s-1FP32\s0 or \s-1FP64,\s0 but not both. *************** operations. This is the default. *** 17257,17264 **** .IX Item "-mno-odd-spreg" .PD Enable the use of odd-numbered single-precision floating-point registers ! for the o32 \s-1ABI.\s0 This is the default for processors that are known to ! support these registers. When using the o32 \s-1FPXX ABI,\s0 \fB\-mno\-odd\-spreg\fR is set by default. .IP "\fB\-mabs=2008\fR" 4 .IX Item "-mabs=2008" --- 17264,17271 ---- .IX Item "-mno-odd-spreg" .PD Enable the use of odd-numbered single-precision floating-point registers ! for the o32 \s-1ABI. \s0 This is the default for processors that are known to ! support these registers. When using the o32 \s-1FPXX ABI, \s0\fB\-mno\-odd\-spreg\fR is set by default. .IP "\fB\-mabs=2008\fR" 4 .IX Item "-mabs=2008" *************** configurations; see the installation doc *** 17327,17334 **** .IP "\fB\-mno\-dsp\fR" 4 .IX Item "-mno-dsp" .PD ! Use (do not use) revision 1 of the \s-1MIPS DSP ASE.\s0 ! This option defines the preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines \&\f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 1. .IP "\fB\-mdspr2\fR" 4 --- 17334,17341 ---- .IP "\fB\-mno\-dsp\fR" 4 .IX Item "-mno-dsp" .PD ! Use (do not use) revision 1 of the \s-1MIPS DSP ASE. ! \s0 This option defines the preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines \&\f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 1. .IP "\fB\-mdspr2\fR" 4 *************** preprocessor macro \f(CW\*(C`_\|_mips_ds *** 17337,17344 **** .IP "\fB\-mno\-dspr2\fR" 4 .IX Item "-mno-dspr2" .PD ! Use (do not use) revision 2 of the \s-1MIPS DSP ASE.\s0 ! This option defines the preprocessor macros \f(CW\*(C`_\|_mips_dsp\*(C'\fR and \f(CW\*(C`_\|_mips_dspr2\*(C'\fR. It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2. .IP "\fB\-msmartmips\fR" 4 --- 17344,17351 ---- .IP "\fB\-mno\-dspr2\fR" 4 .IX Item "-mno-dspr2" .PD ! Use (do not use) revision 2 of the \s-1MIPS DSP ASE. ! \s0 This option defines the preprocessor macros \f(CW\*(C`_\|_mips_dsp\*(C'\fR and \f(CW\*(C`_\|_mips_dspr2\*(C'\fR. It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2. .IP "\fB\-msmartmips\fR" 4 *************** hardware floating-point support to be en *** 17372,17378 **** .IP "\fB\-mno\-mips3d\fR" 4 .IX Item "-mno-mips3d" .PD ! Use (do not use) the \s-1MIPS\-3D ASE.\s0 The option \fB\-mips3d\fR implies \fB\-mpaired\-single\fR. .IP "\fB\-mmicromips\fR" 4 .IX Item "-mmicromips" --- 17379,17385 ---- .IP "\fB\-mno\-mips3d\fR" 4 .IX Item "-mno-mips3d" .PD ! Use (do not use) the \s-1MIPS\-3D ASE. \s0 The option \fB\-mips3d\fR implies \fB\-mpaired\-single\fR. .IP "\fB\-mmicromips\fR" 4 .IX Item "-mmicromips" *************** determined. *** 17429,17435 **** Force \f(CW\*(C`long\*(C'\fR, \f(CW\*(C`int\*(C'\fR, and pointer types to be 32 bits wide. .Sp The default size of \f(CW\*(C`int\*(C'\fRs, \f(CW\*(C`long\*(C'\fRs and pointers depends on ! the \s-1ABI.\s0 All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0 uses 64\-bit \f(CW\*(C`long\*(C'\fRs, as does the 64\-bit \s-1EABI\s0; the others use 32\-bit \f(CW\*(C`long\*(C'\fRs. Pointers are the same size as \f(CW\*(C`long\*(C'\fRs, or the same size as integer registers, whichever is smaller. --- 17436,17442 ---- Force \f(CW\*(C`long\*(C'\fR, \f(CW\*(C`int\*(C'\fR, and pointer types to be 32 bits wide. .Sp The default size of \f(CW\*(C`int\*(C'\fRs, \f(CW\*(C`long\*(C'\fRs and pointers depends on ! the \s-1ABI. \s0 All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0 uses 64\-bit \f(CW\*(C`long\*(C'\fRs, as does the 64\-bit \s-1EABI\s0; the others use 32\-bit \f(CW\*(C`long\*(C'\fRs. Pointers are the same size as \f(CW\*(C`long\*(C'\fRs, or the same size as integer registers, whichever is smaller. *************** or the same size as integer registers, w *** 17440,17446 **** .IX Item "-mno-sym32" .PD Assume (do not assume) that all symbols have 32\-bit values, regardless ! of the selected \s-1ABI.\s0 This option is useful in combination with \&\fB\-mabi=64\fR and \fB\-mno\-abicalls\fR because it allows \s-1GCC\s0 to generate shorter and faster references to symbolic addresses. .IP "\fB\-G\fR \fInum\fR" 4 --- 17447,17453 ---- .IX Item "-mno-sym32" .PD Assume (do not assume) that all symbols have 32\-bit values, regardless ! of the selected \s-1ABI. \s0 This option is useful in combination with \&\fB\-mabi=64\fR and \fB\-mno\-abicalls\fR because it allows \s-1GCC\s0 to generate shorter and faster references to symbolic addresses. .IP "\fB\-G\fR \fInum\fR" 4 *************** otherwise. *** 17729,17735 **** .IP "\fB\-mno\-fix\-rm7000\fR" 4 .IX Item "-mno-fix-rm7000" .PD ! Work around the \s-1RM7000\s0 \f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC.\s0 .IP "\fB\-mfix\-vr4120\fR" 4 .IX Item "-mfix-vr4120" --- 17736,17742 ---- .IP "\fB\-mno\-fix\-rm7000\fR" 4 .IX Item "-mno-fix-rm7000" .PD ! Work around the \s-1RM7000 \s0\f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC.\s0 .IP "\fB\-mfix\-vr4120\fR" 4 .IX Item "-mfix-vr4120" *************** instructions. These errata are handled *** 17756,17765 **** .RE .IP "\fB\-mfix\-vr4130\fR" 4 .IX Item "-mfix-vr4130" ! Work around the \s-1VR4130\s0 \f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC,\s0 although \s-1GCC\s0 avoids using \f(CW\*(C`mflo\*(C'\fR and \f(CW\*(C`mfhi\*(C'\fR if the ! \&\s-1VR4130\s0 \f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR instructions are available instead. .IP "\fB\-mfix\-sb1\fR" 4 .IX Item "-mfix-sb1" --- 17763,17772 ---- .RE .IP "\fB\-mfix\-vr4130\fR" 4 .IX Item "-mfix-vr4130" ! Work around the \s-1VR4130 \s0\f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC,\s0 although \s-1GCC\s0 avoids using \f(CW\*(C`mflo\*(C'\fR and \f(CW\*(C`mfhi\*(C'\fR if the ! \&\s-1VR4130 \s0\f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR instructions are available instead. .IP "\fB\-mfix\-sb1\fR" 4 .IX Item "-mfix-sb1" *************** The default is \fB\-mno\-mcount\-ra\-add *** 17986,17992 **** .IP "\fB\-mno\-frame\-header\-opt\fR" 4 .IX Item "-mno-frame-header-opt" .PD ! Enable (disable) frame header optimization in the o32 \s-1ABI.\s0 When using the o32 \s-1ABI,\s0 calling functions will allocate 16 bytes on the stack for the called function to write out register arguments. When enabled, this optimization will suppress the allocation of the frame header if it can be determined that --- 17993,17999 ---- .IP "\fB\-mno\-frame\-header\-opt\fR" 4 .IX Item "-mno-frame-header-opt" .PD ! Enable (disable) frame header optimization in the o32 \s-1ABI. \s0 When using the o32 \s-1ABI,\s0 calling functions will allocate 16 bytes on the stack for the called function to write out register arguments. When enabled, this optimization will suppress the allocation of the frame header if it can be determined that *************** header file. *** 18191,18197 **** The option also sets the \s-1ISA\s0 to use. If the \s-1MCU\s0 name is one that is known to only support the 430 \s-1ISA\s0 then that is selected, otherwise the 430X \s-1ISA\s0 is selected. A generic \s-1MCU\s0 name of \fBmsp430\fR can also be ! used to select the 430 \s-1ISA.\s0 Similarly the generic \fBmsp430x\fR \s-1MCU\s0 name selects the 430X \s-1ISA.\s0 .Sp In addition an MCU-specific linker script is added to the linker --- 18198,18204 ---- The option also sets the \s-1ISA\s0 to use. If the \s-1MCU\s0 name is one that is known to only support the 430 \s-1ISA\s0 then that is selected, otherwise the 430X \s-1ISA\s0 is selected. A generic \s-1MCU\s0 name of \fBmsp430\fR can also be ! used to select the 430 \s-1ISA. \s0 Similarly the generic \fBmsp430x\fR \s-1MCU\s0 name selects the 430X \s-1ISA.\s0 .Sp In addition an MCU-specific linker script is added to the linker *************** and not emit \f(CW\*(C`div\*(C'\fR and \ *** 18493,18500 **** .IP "\fB\-mno\-cdx\fR" 4 .IX Item "-mno-cdx" .PD ! Enable or disable generation of Nios \s-1II R2 BMX\s0 (bit manipulation) and ! \&\s-1CDX\s0 (code density) instructions. Enabling these instructions also requires \fB\-march=r2\fR. Since these instructions are optional extensions to the R2 architecture, the default is not to emit them. .IP "\fB\-mcustom\-\fR\fIinsn\fR\fB=\fR\fIN\fR" 4 --- 18500,18507 ---- .IP "\fB\-mno\-cdx\fR" 4 .IX Item "-mno-cdx" .PD ! Enable or disable generation of Nios \s-1II R2 BMX \s0(bit manipulation) and ! \&\s-1CDX \s0(code density) instructions. Enabling these instructions also requires \fB\-march=r2\fR. Since these instructions are optional extensions to the R2 architecture, the default is not to emit them. .IP "\fB\-mcustom\-\fR\fIinsn\fR\fB=\fR\fIN\fR" 4 *************** function attribute *** 18671,18680 **** or pragma. .PP These additional \fB\-m\fR options are available for the Altera Nios \s-1II ! ELF\s0 (bare-metal) target: .IP "\fB\-mhal\fR" 4 .IX Item "-mhal" ! Link with \s-1HAL BSP.\s0 This suppresses linking with the GCC-provided C runtime startup and termination code, and is typically used in conjunction with \&\fB\-msys\-crt0=\fR to specify the location of the alternate startup code provided by the \s-1HAL BSP.\s0 --- 18678,18687 ---- or pragma. .PP These additional \fB\-m\fR options are available for the Altera Nios \s-1II ! ELF \s0(bare-metal) target: .IP "\fB\-mhal\fR" 4 .IX Item "-mhal" ! Link with \s-1HAL BSP. \s0 This suppresses linking with the GCC-provided C runtime startup and termination code, and is typically used in conjunction with \&\fB\-msys\-crt0=\fR to specify the location of the alternate startup code provided by the \s-1HAL BSP.\s0 *************** Return floating-point results in memory. *** 18735,18741 **** Generate code for a \s-1PDP\-11/40.\s0 .IP "\fB\-m45\fR" 4 .IX Item "-m45" ! Generate code for a \s-1PDP\-11/45.\s0 This is the default. .IP "\fB\-m10\fR" 4 .IX Item "-m10" Generate code for a \s-1PDP\-11/10.\s0 --- 18742,18748 ---- Generate code for a \s-1PDP\-11/40.\s0 .IP "\fB\-m45\fR" 4 .IX Item "-m45" ! Generate code for a \s-1PDP\-11/45. \s0 This is the default. .IP "\fB\-m10\fR" 4 .IX Item "-m10" Generate code for a \s-1PDP\-11/10.\s0 *************** work properly on all types of \s-1AE.\s0 *** 18815,18821 **** \&\fB\-mae=MUL\fR selects a \s-1MUL AE\s0 type. This is the most useful \s-1AE\s0 type for compiled code, and is the default. .Sp ! \&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC AE.\s0 Code compiled with this option may suffer from poor performance of byte (char) manipulation, since the \s-1DSP AE\s0 does not provide hardware support for byte load/stores. .IP "\fB\-msymbol\-as\-address\fR" 4 --- 18822,18828 ---- \&\fB\-mae=MUL\fR selects a \s-1MUL AE\s0 type. This is the most useful \s-1AE\s0 type for compiled code, and is the default. .Sp ! \&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC AE. \s0 Code compiled with this option may suffer from poor performance of byte (char) manipulation, since the \s-1DSP AE\s0 does not provide hardware support for byte load/stores. .IP "\fB\-msymbol\-as\-address\fR" 4 *************** Specifies the type of hardware multiplic *** 18865,18873 **** be used. The simplest is \f(CW\*(C`none\*(C'\fR, which uses software for both multiplication and division. This is the default. The \f(CW\*(C`g13\*(C'\fR value is for the hardware multiply/divide peripheral found on the ! \&\s-1RL78/G13\s0 (S2 core) targets. The \f(CW\*(C`g14\*(C'\fR value selects the use of ! the multiplication and division instructions supported by the \s-1RL78/G14\s0 ! (S3 core) parts. The value \f(CW\*(C`rl78\*(C'\fR is an alias for \f(CW\*(C`g14\*(C'\fR and the value \f(CW\*(C`mg10\*(C'\fR is an alias for \f(CW\*(C`none\*(C'\fR. .Sp In addition a C preprocessor macro is defined, based upon the setting --- 18872,18880 ---- be used. The simplest is \f(CW\*(C`none\*(C'\fR, which uses software for both multiplication and division. This is the default. The \f(CW\*(C`g13\*(C'\fR value is for the hardware multiply/divide peripheral found on the ! \&\s-1RL78/G13 \s0(S2 core) targets. The \f(CW\*(C`g14\*(C'\fR value selects the use of ! the multiplication and division instructions supported by the \s-1RL78/G14 ! \&\s0(S3 core) parts. The value \f(CW\*(C`rl78\*(C'\fR is an alias for \f(CW\*(C`g14\*(C'\fR and the value \f(CW\*(C`mg10\*(C'\fR is an alias for \f(CW\*(C`none\*(C'\fR. .Sp In addition a C preprocessor macro is defined, based upon the setting *************** of this option. Possible values are: \f *** 18884,18890 **** .IX Item "-mcpu=rl78" .PD Specifies the \s-1RL78\s0 core to target. The default is the G14 core, also ! known as an S3 core or just \s-1RL78.\s0 The G13 or S2 core does not have multiply or divide instructions, instead it uses a hardware peripheral for these operations. The G10 or S1 core does not have register banks, so it uses a different calling convention. --- 18891,18897 ---- .IX Item "-mcpu=rl78" .PD Specifies the \s-1RL78\s0 core to target. The default is the G14 core, also ! known as an S3 core or just \s-1RL78. \s0 The G13 or S2 core does not have multiply or divide instructions, instead it uses a hardware peripheral for these operations. The G10 or S1 core does not have register banks, so it uses a different calling convention. *************** These \fB\-m\fR options are defined for *** 18984,18990 **** .PD You use these options to specify which instructions are available on the processor you are using. The default value of these options is ! determined when configuring \s-1GCC.\s0 Specifying the \&\fB\-mcpu=\fR\fIcpu_type\fR overrides the specification of these options. We recommend you use the \fB\-mcpu=\fR\fIcpu_type\fR option rather than the options listed above. --- 18991,18997 ---- .PD You use these options to specify which instructions are available on the processor you are using. The default value of these options is ! determined when configuring \s-1GCC. \s0 Specifying the \&\fB\-mcpu=\fR\fIcpu_type\fR overrides the specification of these options. We recommend you use the \fB\-mcpu=\fR\fIcpu_type\fR option rather than the options listed above. *************** following options: *** 19059,19066 **** \&\-mpowerpc\-gpopt \-mpowerpc\-gfxopt \-msingle\-float \-mdouble\-float \&\-msimple\-fpu \-mstring \-mmulhw \-mdlmzb \-mmfpgpr \-mvsx \&\-mcrypto \-mdirect\-move \-mhtm \-mpower8\-fusion \-mpower8\-vector ! \&\-mquad\-memory \-mquad\-memory\-atomic \-mmodulo \-mfloat128 \-mfloat128\-hardware ! \&\-mpower9\-fusion \-mpower9\-vector \-mpower9\-dform\fR .Sp The particular options set for any particular \s-1CPU\s0 varies between compiler versions, depending on what setting seems to produce optimal --- 19066,19072 ---- \&\-mpowerpc\-gpopt \-mpowerpc\-gfxopt \-msingle\-float \-mdouble\-float \&\-msimple\-fpu \-mstring \-mmulhw \-mdlmzb \-mmfpgpr \-mvsx \&\-mcrypto \-mdirect\-move \-mhtm \-mpower8\-fusion \-mpower8\-vector ! \&\-mquad\-memory \-mquad\-memory\-atomic \-mfloat128 \-mfloat128\-hardware\fR .Sp The particular options set for any particular \s-1CPU\s0 varies between compiler versions, depending on what setting seems to produce optimal *************** This is a PowerPC *** 19160,19166 **** 32\-bit \s-1SYSV ABI\s0 option. .IP "\fB\-mbss\-plt\fR" 4 .IX Item "-mbss-plt" ! Generate code that uses a \s-1BSS\s0 \f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR fills in, and requires \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR sections that are both writable and executable. --- 19166,19172 ---- 32\-bit \s-1SYSV ABI\s0 option. .IP "\fB\-mbss\-plt\fR" 4 .IX Item "-mbss-plt" ! Generate code that uses a \s-1BSS \s0\f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR fills in, and requires \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR sections that are both writable and executable. *************** later processors. *** 19253,19259 **** .IX Item "-mno-power8-vector" .PD Generate code that uses (does not use) the vector and scalar ! instructions that were added in version 2.07 of the PowerPC \s-1ISA.\s0 Also enable the use of built-in functions that allow more direct access to the vector instructions. .IP "\fB\-mquad\-memory\fR" 4 --- 19259,19265 ---- .IX Item "-mno-power8-vector" .PD Generate code that uses (does not use) the vector and scalar ! instructions that were added in version 2.07 of the PowerPC \s-1ISA. \s0 Also enable the use of built-in functions that allow more direct access to the vector instructions. .IP "\fB\-mquad\-memory\fR" 4 *************** instructions. The \fB\-mquad\-memory\-a *** 19283,19289 **** Generate code that uses (does not use) the scalar double precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.06 of the ! PowerPC \s-1ISA.\s0 \fB\-mupper\-regs\-df\fR is turned on by default if you use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or \&\fB\-mvsx\fR options. .IP "\fB\-mupper\-regs\-sf\fR" 4 --- 19289,19295 ---- Generate code that uses (does not use) the scalar double precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.06 of the ! PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-df\fR is turned on by default if you use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or \&\fB\-mvsx\fR options. .IP "\fB\-mupper\-regs\-sf\fR" 4 *************** use any of the \fB\-mcpu=power7\fR, \fB\ *** 19295,19303 **** Generate code that uses (does not use) the scalar single precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the ! PowerPC \s-1ISA.\s0 \fB\-mupper\-regs\-sf\fR is turned on by default if you ! use either of the \fB\-mcpu=power8\fR or \fB\-mpower8\-vector\fR ! options. .IP "\fB\-mupper\-regs\fR" 4 .IX Item "-mupper-regs" .PD 0 --- 19301,19309 ---- Generate code that uses (does not use) the scalar single precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the ! PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-sf\fR is turned on by default if you ! use either of the \fB\-mcpu=power8\fR, \fB\-mpower8\-vector\fR, or ! \&\fB\-mcpu=power9\fR options. .IP "\fB\-mupper\-regs\fR" 4 .IX Item "-mupper-regs" .PD 0 *************** If you use \fB\-mfloat128\-hardware\fR, *** 19344,19387 **** If you select \s-1ISA 3.0\s0 instructions with \fB\-mcpu=power9\fR, but do not use either \fB\-mfloat128\fR or \fB\-mfloat128\-hardware\fR, the \s-1IEEE\s0 128\-bit floating point support will not be enabled. - .IP "\fB\-mmodulo\fR" 4 - .IX Item "-mmodulo" - .PD 0 - .IP "\fB\-mno\-modulo\fR" 4 - .IX Item "-mno-modulo" - .PD - Generate code that uses (does not use) the \s-1ISA 3.0\s0 integer modulo - instructions. The \fB\-mmodulo\fR option is enabled by default - with the \fB\-mcpu=power9\fR option. - .IP "\fB\-mpower9\-fusion\fR" 4 - .IX Item "-mpower9-fusion" - .PD 0 - .IP "\fB\-mno\-power9\-fusion\fR" 4 - .IX Item "-mno-power9-fusion" - .PD - Generate code that keeps (does not keeps) some operations adjacent so - that the instructions can be fused together on power9 and later - processors. - .IP "\fB\-mpower9\-vector\fR" 4 - .IX Item "-mpower9-vector" - .PD 0 - .IP "\fB\-mno\-power9\-vector\fR" 4 - .IX Item "-mno-power9-vector" - .PD - Generate code that uses (does not use) the vector and scalar - instructions that were added in version 3.0 of the PowerPC \s-1ISA.\s0 Also - enable the use of built-in functions that allow more direct access to - the vector instructions. - .IP "\fB\-mpower9\-dform\fR" 4 - .IX Item "-mpower9-dform" - .PD 0 - .IP "\fB\-mno\-power9\-dform\fR" 4 - .IX Item "-mno-power9-dform" - .PD - Enable (disable) scalar d\-form (register + offset) memory instructions - to load/store traditional Altivec registers. If the \fI\s-1LRA\s0\fR register - allocator is enabled, also enable (disable) vector d\-form memory - instructions. .IP "\fB\-mfloat\-gprs=\fR\fIyes/single/double/no\fR" 4 .IX Item "-mfloat-gprs=yes/single/double/no" .PD 0 --- 19350,19355 ---- *************** pointer to 64 bits, and generates code f *** 19424,19434 **** .IP "\fB\-mminimal\-toc\fR" 4 .IX Item "-mminimal-toc" .PD ! Modify generation of the \s-1TOC\s0 (Table Of Contents), which is created for every executable file. The \fB\-mfull\-toc\fR option is selected by default. In that case, \s-1GCC\s0 allocates at least one \s-1TOC\s0 entry for each unique non-automatic variable reference in your program. \s-1GCC\s0 ! also places floating-point constants in the \s-1TOC.\s0 However, only 16,384 entries are available in the \s-1TOC.\s0 .Sp If you receive a linker error message that saying you have overflowed --- 19392,19402 ---- .IP "\fB\-mminimal\-toc\fR" 4 .IX Item "-mminimal-toc" .PD ! Modify generation of the \s-1TOC \s0(Table Of Contents), which is created for every executable file. The \fB\-mfull\-toc\fR option is selected by default. In that case, \s-1GCC\s0 allocates at least one \s-1TOC\s0 entry for each unique non-automatic variable reference in your program. \s-1GCC\s0 ! also places floating-point constants in the \s-1TOC. \s0 However, only 16,384 entries are available in the \s-1TOC.\s0 .Sp If you receive a linker error message that saying you have overflowed *************** with the \fB\-mno\-fp\-in\-toc\fR and \f *** 19437,19443 **** \&\fB\-mno\-fp\-in\-toc\fR prevents \s-1GCC\s0 from putting floating-point constants in the \s-1TOC\s0 and \fB\-mno\-sum\-in\-toc\fR forces \s-1GCC\s0 to generate code to calculate the sum of an address and a constant at ! run time instead of putting that sum into the \s-1TOC.\s0 You may specify one or both of these options. Each causes \s-1GCC\s0 to produce very slightly slower and larger code at the expense of conserving \s-1TOC\s0 space. .Sp --- 19405,19411 ---- \&\fB\-mno\-fp\-in\-toc\fR prevents \s-1GCC\s0 from putting floating-point constants in the \s-1TOC\s0 and \fB\-mno\-sum\-in\-toc\fR forces \s-1GCC\s0 to generate code to calculate the sum of an address and a constant at ! run time instead of putting that sum into the \s-1TOC. \s0 You may specify one or both of these options. Each causes \s-1GCC\s0 to produce very slightly slower and larger code at the expense of conserving \s-1TOC\s0 space. .Sp *************** implies \fB\-mno\-powerpc64\fR. \s-1GCC *** 19465,19471 **** .IX Item "-mno-xl-compat" .PD Produce code that conforms more closely to \s-1IBM XL\s0 compiler semantics ! when using AIX-compatible \s-1ABI.\s0 Pass floating-point arguments to prototyped functions beyond the register save area (\s-1RSA\s0) on the stack in addition to argument FPRs. Do not assume that most significant double in 128\-bit long double value is properly rounded when comparing --- 19433,19439 ---- .IX Item "-mno-xl-compat" .PD Produce code that conforms more closely to \s-1IBM XL\s0 compiler semantics ! when using AIX-compatible \s-1ABI. \s0 Pass floating-point arguments to prototyped functions beyond the register save area (\s-1RSA\s0) on the stack in addition to argument FPRs. Do not assume that most significant double in 128\-bit long double value is properly rounded when comparing *************** On Darwin/PPC systems, \f(CW\*(C`#pragma *** 19991,19997 **** callee, L42\*(C'\fR, plus a \fIbranch island\fR (glue code). The two target addresses represent the callee and the branch island. The Darwin/PPC linker prefers the first address and generates a \f(CW\*(C`bl ! callee\*(C'\fR if the \s-1PPC\s0 \f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly; otherwise, the linker generates \f(CW\*(C`bl L42\*(C'\fR to call the branch island. The branch island is appended to the body of the calling function; it computes the full 32\-bit address of the callee --- 19959,19965 ---- callee, L42\*(C'\fR, plus a \fIbranch island\fR (glue code). The two target addresses represent the callee and the branch island. The Darwin/PPC linker prefers the first address and generates a \f(CW\*(C`bl ! callee\*(C'\fR if the \s-1PPC \s0\f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly; otherwise, the linker generates \f(CW\*(C`bl L42\*(C'\fR to call the branch island. The branch island is appended to the body of the calling function; it computes the full 32\-bit address of the callee *************** which handle the double-precision recipr *** 20087,20093 **** .PD Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ! \&\s-1ABI.\s0 Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or \&\fB\-mcpu=power8\fR automatically selects \fB\-mrecip\-precision\fR. The double-precision square root estimate instructions are not generated by default on low-precision machines, since they do not provide an --- 20055,20061 ---- .PD Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ! \&\s-1ABI. \s0 Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or \&\fB\-mcpu=power8\fR automatically selects \fB\-mrecip\-precision\fR. The double-precision square root estimate instructions are not generated by default on low-precision machines, since they do not provide an *************** Generate (do not generate) code to pass *** 20162,20171 **** maximum alignment of 64 bits, for compatibility with older versions of \s-1GCC.\s0 .Sp ! Older versions of \s-1GCC\s0 (prior to 4.9.0) incorrectly did not align a structure parameter on a 128\-bit boundary when that structure contained a member requiring 128\-bit alignment. This is corrected in more ! recent versions of \s-1GCC.\s0 This option may be used to generate code that is compatible with functions compiled with older versions of \&\s-1GCC.\s0 .Sp --- 20130,20139 ---- maximum alignment of 64 bits, for compatibility with older versions of \s-1GCC.\s0 .Sp ! Older versions of \s-1GCC \s0(prior to 4.9.0) incorrectly did not align a structure parameter on a 128\-bit boundary when that structure contained a member requiring 128\-bit alignment. This is corrected in more ! recent versions of \s-1GCC. \s0 This option may be used to generate code that is compatible with functions compiled with older versions of \&\s-1GCC.\s0 .Sp *************** This is because the \s-1RX FPU\s0 instru *** 20207,20213 **** .IX Item "-mcpu=name" Selects the type of \s-1RX CPU\s0 to be targeted. Currently three types are supported, the generic \fB\s-1RX600\s0\fR and \fB\s-1RX200\s0\fR series hardware and ! the specific \fB\s-1RX610\s0\fR \s-1CPU.\s0 The default is \fB\s-1RX600\s0\fR. .Sp The only difference between \fB\s-1RX600\s0\fR and \fB\s-1RX610\s0\fR is that the \&\fB\s-1RX610\s0\fR does not support the \f(CW\*(C`MVTIPL\*(C'\fR instruction. --- 20175,20181 ---- .IX Item "-mcpu=name" Selects the type of \s-1RX CPU\s0 to be targeted. Currently three types are supported, the generic \fB\s-1RX600\s0\fR and \fB\s-1RX200\s0\fR series hardware and ! the specific \fB\s-1RX610\s0\fR \s-1CPU. \s0 The default is \fB\s-1RX600\s0\fR. .Sp The only difference between \fB\s-1RX600\s0\fR and \fB\s-1RX610\s0\fR is that the \&\fB\s-1RX610\s0\fR does not support the \f(CW\*(C`MVTIPL\*(C'\fR instruction. *************** which does not have this limitation. *** 20485,20492 **** .IX Item "-m31" .PD When \fB\-m31\fR is specified, generate code compliant to the ! GNU/Linux for S/390 \s-1ABI.\s0 When \fB\-m64\fR is specified, generate ! code compliant to the GNU/Linux for zSeries \s-1ABI.\s0 This allows \s-1GCC\s0 in particular to generate 64\-bit instructions. For the \fBs390\fR targets, the default is \fB\-m31\fR, while the \fBs390x\fR targets default to \fB\-m64\fR. --- 20453,20460 ---- .IX Item "-m31" .PD When \fB\-m31\fR is specified, generate code compliant to the ! GNU/Linux for S/390 \s-1ABI. \s0 When \fB\-m64\fR is specified, generate ! code compliant to the GNU/Linux for zSeries \s-1ABI. \s0 This allows \s-1GCC\s0 in particular to generate 64\-bit instructions. For the \fBs390\fR targets, the default is \fB\-m31\fR, while the \fBs390x\fR targets default to \fB\-m64\fR. *************** targets default to \fB\-m64\fR. *** 20499,20505 **** When \fB\-mzarch\fR is specified, generate code using the instructions available on z/Architecture. When \fB\-mesa\fR is specified, generate code using the ! instructions available on \s-1ESA/390.\s0 Note that \fB\-mesa\fR is not possible with \fB\-m64\fR. When generating code compliant to the GNU/Linux for S/390 \s-1ABI,\s0 the default is \fB\-mesa\fR. When generating code compliant --- 20467,20473 ---- When \fB\-mzarch\fR is specified, generate code using the instructions available on z/Architecture. When \fB\-mesa\fR is specified, generate code using the ! instructions available on \s-1ESA/390. \s0 Note that \fB\-mesa\fR is not possible with \fB\-m64\fR. When generating code compliant to the GNU/Linux for S/390 \s-1ABI,\s0 the default is \fB\-mesa\fR. When generating code compliant *************** available with the vector extension faci *** 20526,20532 **** z13 machine generation. This option changes the \s-1ABI\s0 for some vector type values with regard to alignment and calling conventions. In case vector type values are ! being used in an ABI-relevant context a \s-1GAS\s0 \fB.gnu_attribute\fR command will be added to mark the resulting binary with the \s-1ABI\s0 used. \&\fB\-mvx\fR is enabled by default when using \fB\-march=z13\fR. .IP "\fB\-mzvector\fR" 4 --- 20494,20500 ---- z13 machine generation. This option changes the \s-1ABI\s0 for some vector type values with regard to alignment and calling conventions. In case vector type values are ! being used in an ABI-relevant context a \s-1GAS \s0\fB.gnu_attribute\fR command will be added to mark the resulting binary with the \s-1ABI\s0 used. \&\fB\-mvx\fR is enabled by default when using \fB\-march=z13\fR. .IP "\fB\-mzvector\fR" 4 *************** Generate code for \s-1SH4\-300\s0 in suc *** 20770,20779 **** floating-point operations are used. .IP "\fB\-m4\-340\fR" 4 .IX Item "-m4-340" ! Generate code for \s-1SH4\-340\s0 (no \s-1MMU,\s0 no \s-1FPU\s0). .IP "\fB\-m4\-500\fR" 4 .IX Item "-m4-500" ! Generate code for \s-1SH4\-500\s0 (no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the assembler. .IP "\fB\-m4a\-nofpu\fR" 4 .IX Item "-m4a-nofpu" --- 20738,20747 ---- floating-point operations are used. .IP "\fB\-m4\-340\fR" 4 .IX Item "-m4-340" ! Generate code for \s-1SH4\-340 \s0(no \s-1MMU,\s0 no \s-1FPU\s0). .IP "\fB\-m4\-500\fR" 4 .IX Item "-m4-500" ! Generate code for \s-1SH4\-500 \s0(no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the assembler. .IP "\fB\-m4a\-nofpu\fR" 4 .IX Item "-m4a-nofpu" *************** SH2A\s0 and SHcompact. *** 20966,20979 **** .IX Item "call-fp" Calls a library function that performs the operation in double precision floating point. Division by zero causes a floating-point exception. This is ! the default for SHcompact with \s-1FPU.\s0 Specifying this for targets that do not have a double precision \s-1FPU\s0 defaults to \f(CW\*(C`call\-div1\*(C'\fR. .IP "\fBcall-table\fR" 4 .IX Item "call-table" Calls a library function that uses a lookup table for small divisors and the \f(CW\*(C`div1\*(C'\fR instruction with case distinction for larger divisors. Division by zero calculates an unspecified result and does not trap. This is the default ! for \s-1SH4.\s0 Specifying this for targets that do not have dynamic shift instructions defaults to \f(CW\*(C`call\-div1\*(C'\fR. .RE .RS 4 --- 20934,20947 ---- .IX Item "call-fp" Calls a library function that performs the operation in double precision floating point. Division by zero causes a floating-point exception. This is ! the default for SHcompact with \s-1FPU. \s0 Specifying this for targets that do not have a double precision \s-1FPU\s0 defaults to \f(CW\*(C`call\-div1\*(C'\fR. .IP "\fBcall-table\fR" 4 .IX Item "call-table" Calls a library function that uses a lookup table for small divisors and the \f(CW\*(C`div1\*(C'\fR instruction with case distinction for larger divisors. Division by zero calculates an unspecified result and does not trap. This is the default ! for \s-1SH4. \s0 Specifying this for targets that do not have dynamic shift instructions defaults to \f(CW\*(C`call\-div1\*(C'\fR. .RE .RS 4 *************** is being compiled for. *** 21017,21023 **** Assume (do not assume) that zero displacement conditional branch instructions \&\f(CW\*(C`bt\*(C'\fR and \f(CW\*(C`bf\*(C'\fR are fast. If \fB\-mzdcbranch\fR is specified, the compiler prefers zero displacement branch code sequences. This is ! enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A.\s0 It can be explicitly disabled by specifying \fB\-mno\-zdcbranch\fR. .IP "\fB\-mcbranch\-force\-delay\-slot\fR" 4 .IX Item "-mcbranch-force-delay-slot" --- 20985,20991 ---- Assume (do not assume) that zero displacement conditional branch instructions \&\f(CW\*(C`bt\*(C'\fR and \f(CW\*(C`bf\*(C'\fR are fast. If \fB\-mzdcbranch\fR is specified, the compiler prefers zero displacement branch code sequences. This is ! enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A. \s0 It can be explicitly disabled by specifying \fB\-mno\-zdcbranch\fR. .IP "\fB\-mcbranch\-force\-delay\-slot\fR" 4 .IX Item "-mcbranch-force-delay-slot" *************** mapped to \fB\-ffp\-contract=off\fR. *** 21046,21052 **** Allow or disallow the compiler to emit the \f(CW\*(C`fsca\*(C'\fR instruction for sine and cosine approximations. The option \fB\-mfsca\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR. It is enabled by default ! when generating code for \s-1SH4A.\s0 Using \fB\-mno\-fsca\fR disables sine and cosine approximations even if \fB\-funsafe\-math\-optimizations\fR is in effect. .IP "\fB\-mfsrra\fR" 4 .IX Item "-mfsrra" --- 21014,21020 ---- Allow or disallow the compiler to emit the \f(CW\*(C`fsca\*(C'\fR instruction for sine and cosine approximations. The option \fB\-mfsca\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR. It is enabled by default ! when generating code for \s-1SH4A. \s0 Using \fB\-mno\-fsca\fR disables sine and cosine approximations even if \fB\-funsafe\-math\-optimizations\fR is in effect. .IP "\fB\-mfsrra\fR" 4 .IX Item "-mfsrra" *************** Allow or disallow the compiler to emit t *** 21058,21064 **** reciprocal square root approximations. The option \fB\-mfsrra\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR and \&\fB\-ffinite\-math\-only\fR. It is enabled by default when generating code for ! \&\s-1SH4A.\s0 Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations even if \fB\-funsafe\-math\-optimizations\fR and \fB\-ffinite\-math\-only\fR are in effect. .IP "\fB\-mpretend\-cmove\fR" 4 --- 21026,21032 ---- reciprocal square root approximations. The option \fB\-mfsrra\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR and \&\fB\-ffinite\-math\-only\fR. It is enabled by default when generating code for ! \&\s-1SH4A. \s0 Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations even if \fB\-funsafe\-math\-optimizations\fR and \fB\-ffinite\-math\-only\fR are in effect. .IP "\fB\-mpretend\-cmove\fR" 4 *************** instructions. *** 21171,21177 **** .IX Item "-msoft-quad-float" Generate output containing library calls for quad-word (long double) floating-point instructions. The functions called are those specified ! in the \s-1SPARC ABI.\s0 This is the default. .Sp As of this writing, there are no \s-1SPARC\s0 implementations that have hardware support for the quad-word floating-point instructions. They all invoke --- 21139,21145 ---- .IX Item "-msoft-quad-float" Generate output containing library calls for quad-word (long double) floating-point instructions. The functions called are those specified ! in the \s-1SPARC ABI. \s0 This is the default. .Sp As of this writing, there are no \s-1SPARC\s0 implementations that have hardware support for the quad-word floating-point instructions. They all invoke *************** should have 8\-byte alignment. This ena *** 21213,21219 **** \&\f(CW\*(C`ldd\*(C'\fR and \f(CW\*(C`std\*(C'\fR instructions for copies in structure assignment, in place of twice as many \f(CW\*(C`ld\*(C'\fR and \f(CW\*(C`st\*(C'\fR pairs. However, the use of this changed alignment directly violates the \s-1SPARC ! ABI.\s0 Thus, it's intended only for use on targets where the developer acknowledges that their resulting code is not directly in line with the rules of the \s-1ABI.\s0 .IP "\fB\-mstd\-struct\-return\fR" 4 --- 21181,21187 ---- \&\f(CW\*(C`ldd\*(C'\fR and \f(CW\*(C`std\*(C'\fR instructions for copies in structure assignment, in place of twice as many \f(CW\*(C`ld\*(C'\fR and \f(CW\*(C`st\*(C'\fR pairs. However, the use of this changed alignment directly violates the \s-1SPARC ! ABI. \s0 Thus, it's intended only for use on targets where the developer acknowledges that their resulting code is not directly in line with the rules of the \s-1ABI.\s0 .IP "\fB\-mstd\-struct\-return\fR" 4 *************** SPARCStation 1, 2, \s-1IPX\s0 etc. *** 21277,21283 **** With \fB\-mcpu=v8\fR, \s-1GCC\s0 generates code for the V8 variant of the \s-1SPARC\s0 architecture. The only difference from V7 code is that the compiler emits the integer multiply and integer divide instructions which exist in \s-1SPARC\-V8\s0 ! but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=supersparc\fR, the compiler additionally optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000 series. .Sp --- 21245,21251 ---- With \fB\-mcpu=v8\fR, \s-1GCC\s0 generates code for the V8 variant of the \s-1SPARC\s0 architecture. The only difference from V7 code is that the compiler emits the integer multiply and integer divide instructions which exist in \s-1SPARC\-V8\s0 ! but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=supersparc\fR, the compiler additionally optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000 series. .Sp *************** With \fB\-mcpu=sparclite\fR, \s-1GCC\s0 *** 21285,21298 **** the \s-1SPARC\s0 architecture. This adds the integer multiply, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=f930\fR, the compiler additionally optimizes it for the ! Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU.\s0 With \&\fB\-mcpu=f934\fR, the compiler additionally optimizes it for the Fujitsu \&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU.\s0 .Sp With \fB\-mcpu=sparclet\fR, \s-1GCC\s0 generates code for the SPARClet variant of the \s-1SPARC\s0 architecture. This adds the integer multiply, multiply/accumulate, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClet ! but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=tsc701\fR, the compiler additionally optimizes it for the \s-1TEMIC\s0 SPARClet chip. .Sp With \fB\-mcpu=v9\fR, \s-1GCC\s0 generates code for the V9 variant of the \s-1SPARC\s0 --- 21253,21266 ---- the \s-1SPARC\s0 architecture. This adds the integer multiply, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=f930\fR, the compiler additionally optimizes it for the ! Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU. \s0 With \&\fB\-mcpu=f934\fR, the compiler additionally optimizes it for the Fujitsu \&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU.\s0 .Sp With \fB\-mcpu=sparclet\fR, \s-1GCC\s0 generates code for the SPARClet variant of the \s-1SPARC\s0 architecture. This adds the integer multiply, multiply/accumulate, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClet ! but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=tsc701\fR, the compiler additionally optimizes it for the \s-1TEMIC\s0 SPARClet chip. .Sp With \fB\-mcpu=v9\fR, \s-1GCC\s0 generates code for the V9 variant of the \s-1SPARC\s0 *************** GNU/Linux toolchains, \fBnative\fR can a *** 21332,21338 **** .IP "\fB\-mno\-v8plus\fR" 4 .IX Item "-mno-v8plus" .PD ! With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+ ABI.\s0 The difference from the V8 \s-1ABI\s0 is that the global and out registers are considered 64 bits wide. This is enabled by default on Solaris in 32\-bit mode for all \s-1SPARC\-V9\s0 processors. --- 21300,21306 ---- .IP "\fB\-mno\-v8plus\fR" 4 .IX Item "-mno-v8plus" .PD ! With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+ ABI. \s0 The difference from the V8 \s-1ABI\s0 is that the global and out registers are considered 64 bits wide. This is enabled by default on Solaris in 32\-bit mode for all \s-1SPARC\-V9\s0 processors. *************** selected because its use is still experi *** 21840,21846 **** .IP "\fB\-mghs\fR" 4 .IX Item "-mghs" .PD ! Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI.\s0 This is the default. With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 --- 21808,21814 ---- .IP "\fB\-mghs\fR" 4 .IX Item "-mghs" .PD ! Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI. \s0 This is the default. With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 *************** When this version of the \s-1ABI\s0 is e *** 21865,21871 **** .RE .IP "\fB\-mgcc\-abi\fR" 4 .IX Item "-mgcc-abi" ! Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI.\s0 With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 --- 21833,21839 ---- .RE .IP "\fB\-mgcc\-abi\fR" 4 .IX Item "-mgcc-abi" ! Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI. \s0 With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 *************** of the selected instruction set. *** 22075,22081 **** Original Intel i386 \s-1CPU.\s0 .IP "\fBi486\fR" 4 .IX Item "i486" ! Intel i486 \s-1CPU.\s0 (No scheduling is implemented for this chip.) .IP "\fBi586\fR" 4 .IX Item "i586" .PD 0 --- 22043,22049 ---- Original Intel i386 \s-1CPU.\s0 .IP "\fBi486\fR" 4 .IX Item "i486" ! Intel i486 \s-1CPU. \s0(No scheduling is implemented for this chip.) .IP "\fBi586\fR" 4 .IX Item "i586" .PD 0 *************** extensions.) *** 22259,22273 **** .IP "\fBbdver3\fR" 4 .IX Item "bdver3" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, XOP, LWP, AES,\s0 ! \&\s-1PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBbdver4\fR" 4 .IX Item "bdver4" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, BMI2, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, AVX2, XOP, LWP,\s0 ! \&\s-1AES, PCL_MUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1,\s0 ! \&\s-1SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBznver1\fR" 4 .IX Item "znver1" \&\s-1AMD\s0 Family 17h core based CPUs with x86\-64 instruction set support. (This --- 22227,22241 ---- .IP "\fBbdver3\fR" 4 .IX Item "bdver3" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, XOP, LWP, AES, ! PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBbdver4\fR" 4 .IX Item "bdver4" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, BMI2, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, AVX2, XOP, LWP, ! AES, PCL_MUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, ! SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBznver1\fR" 4 .IX Item "znver1" \&\s-1AMD\s0 Family 17h core based CPUs with x86\-64 instruction set support. (This *************** instruction set support. *** 22299,22305 **** implemented for this chip.) .IP "\fBc3\-2\fR" 4 .IX Item "c3-2" ! \&\s-1VIA C3\-2\s0 (Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support. (No scheduling is implemented for this chip.) .IP "\fBgeode\fR" 4 --- 22267,22273 ---- implemented for this chip.) .IP "\fBc3\-2\fR" 4 .IX Item "c3-2" ! \&\s-1VIA C3\-2 \s0(Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support. (No scheduling is implemented for this chip.) .IP "\fBgeode\fR" 4 *************** processors) for which the code is optimi *** 22345,22351 **** .IP "\fBintel\fR" 4 .IX Item "intel" Produce code optimized for the most current Intel processors, which are ! Haswell and Silvermont for this version of \s-1GCC.\s0 If you know the \s-1CPU\s0 on which your code will run, then you should use the corresponding \&\fB\-mtune\fR or \fB\-march\fR option instead of \fB\-mtune=intel\fR. But, if you want your application performs better on both Haswell and --- 22313,22319 ---- .IP "\fBintel\fR" 4 .IX Item "intel" Produce code optimized for the most current Intel processors, which are ! Haswell and Silvermont for this version of \s-1GCC. \s0 If you know the \s-1CPU\s0 on which your code will run, then you should use the corresponding \&\fB\-mtune\fR or \fB\-march\fR option instead of \fB\-mtune=intel\fR. But, if you want your application performs better on both Haswell and *************** Do not use the \s-1FPU\s0 registers for *** 22453,22459 **** .Sp The usual calling convention has functions return values of types \&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR in an \s-1FPU\s0 register, even if there ! is no \s-1FPU.\s0 The idea is that the operating system should emulate an \s-1FPU.\s0 .Sp The option \fB\-mno\-fp\-ret\-in\-387\fR causes such values to be returned --- 22421,22427 ---- .Sp The usual calling convention has functions return values of types \&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR in an \s-1FPU\s0 register, even if there ! is no \s-1FPU. \s0 The idea is that the operating system should emulate an \s-1FPU.\s0 .Sp The option \fB\-mno\-fp\-ret\-in\-387\fR causes such values to be returned *************** external library. Supported values for *** 22935,22941 **** for the Intel short vector math library and \fBacml\fR for the \s-1AMD\s0 math core library. To use this option, both \fB\-ftree\-vectorize\fR and ! \&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML\s0 ABI-compatible library must be specified at link time. .Sp \&\s-1GCC\s0 currently emits calls to \f(CW\*(C`vmldExp2\*(C'\fR, --- 22903,22909 ---- for the Intel short vector math library and \fBacml\fR for the \s-1AMD\s0 math core library. To use this option, both \fB\-ftree\-vectorize\fR and ! \&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML \s0 ABI-compatible library must be specified at link time. .Sp \&\s-1GCC\s0 currently emits calls to \f(CW\*(C`vmldExp2\*(C'\fR, *************** when \fB\-mveclibabi=acml\fR is used. *** 22958,22964 **** .IX Item "-mabi=name" Generate code for the specified calling convention. Permissible values are \fBsysv\fR for the \s-1ABI\s0 used on GNU/Linux and other systems, and ! \&\fBms\fR for the Microsoft \s-1ABI.\s0 The default is to use the Microsoft \&\s-1ABI\s0 when targeting Microsoft Windows and the SysV \s-1ABI\s0 on all other systems. You can control this behavior for specific functions by using the function attributes \f(CW\*(C`ms_abi\*(C'\fR and \f(CW\*(C`sysv_abi\*(C'\fR. --- 22926,22932 ---- .IX Item "-mabi=name" Generate code for the specified calling convention. Permissible values are \fBsysv\fR for the \s-1ABI\s0 used on GNU/Linux and other systems, and ! \&\fBms\fR for the Microsoft \s-1ABI. \s0 The default is to use the Microsoft \&\s-1ABI\s0 when targeting Microsoft Windows and the SysV \s-1ABI\s0 on all other systems. You can control this behavior for specific functions by using the function attributes \f(CW\*(C`ms_abi\*(C'\fR and \f(CW\*(C`sysv_abi\*(C'\fR. *************** See the Info entry for \fBgcc\fR, or *** 23772,23778 **** for contributors to \s-1GCC.\s0 .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1988\-2016 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or --- 23740,23746 ---- for contributors to \s-1GCC.\s0 .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1988\-2017 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or diff -Nrcpad gcc-6.3.0/gcc/doc/gc-analyze.1 gcc-6.4.0/gcc/doc/gc-analyze.1 *** gcc-6.3.0/gcc/doc/gc-analyze.1 Wed Dec 21 09:16:01 2016 --- gcc-6.4.0/gcc/doc/gc-analyze.1 Tue Jul 4 09:08:00 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GC-ANALYZE 1" ! .TH GC-ANALYZE 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GC-ANALYZE 1" ! .TH GC-ANALYZE 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/gcc.1 gcc-6.4.0/gcc/doc/gcc.1 *** gcc-6.3.0/gcc/doc/gcc.1 Wed Dec 21 09:34:11 2016 --- gcc-6.4.0/gcc/doc/gcc.1 Tue Jul 4 09:27:49 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GCC 1" ! .TH GCC 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GCC 1" ! .TH GCC 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** in the following sections. *** 278,284 **** \&\fB\-Wno\-attributes \-Wbool\-compare \-Wno\-builtin\-macro\-redefined \&\-Wc90\-c99\-compat \-Wc99\-c11\-compat \&\-Wc++\-compat \-Wc++11\-compat \-Wc++14\-compat \-Wcast\-align \-Wcast\-qual ! \&\-Wchar\-subscripts \-Wclobbered \-Wcomment \-Wconditionally\-supported \&\-Wconversion \-Wcoverage\-mismatch \-Wno\-cpp \-Wdate\-time \-Wdelete\-incomplete \&\-Wno\-deprecated \-Wno\-deprecated\-declarations \-Wno\-designated\-init \&\-Wdisabled\-optimization --- 282,288 ---- \&\fB\-Wno\-attributes \-Wbool\-compare \-Wno\-builtin\-macro\-redefined \&\-Wc90\-c99\-compat \-Wc99\-c11\-compat \&\-Wc++\-compat \-Wc++11\-compat \-Wc++14\-compat \-Wcast\-align \-Wcast\-qual ! \&\-Wchar\-subscripts \-Wchkp \-Wclobbered \-Wcomment \-Wconditionally\-supported \&\-Wconversion \-Wcoverage\-mismatch \-Wno\-cpp \-Wdate\-time \-Wdelete\-incomplete \&\-Wno\-deprecated \-Wno\-deprecated\-declarations \-Wno\-designated\-init \&\-Wdisabled\-optimization *************** See \s-1RS/6000\s0 and PowerPC Options. *** 1009,1018 **** \&\-mquad\-memory\-atomic \-mno\-quad\-memory\-atomic \&\-mcompat\-align\-parm \-mno\-compat\-align\-parm \&\-mupper\-regs\-df \-mno\-upper\-regs\-df \-mupper\-regs\-sf \-mno\-upper\-regs\-sf ! \&\-mupper\-regs \-mno\-upper\-regs \-mmodulo \-mno\-modulo \&\-mfloat128 \-mno\-float128 \-mfloat128\-hardware \-mno\-float128\-hardware ! \&\-mpower9\-fusion \-mno\-mpower9\-fusion \-mpower9\-vector \-mno\-power9\-vector ! \&\-mpower9\-dform \-mno\-power9\-dform \-mlra \-mno\-lra\fR .Sp \&\fI\s-1RX\s0 Options\fR \&\fB\-m64bit\-doubles \-m32bit\-doubles \-fpu \-nofpu --- 1013,1021 ---- \&\-mquad\-memory\-atomic \-mno\-quad\-memory\-atomic \&\-mcompat\-align\-parm \-mno\-compat\-align\-parm \&\-mupper\-regs\-df \-mno\-upper\-regs\-df \-mupper\-regs\-sf \-mno\-upper\-regs\-sf ! \&\-mupper\-regs \-mno\-upper\-regs \&\-mfloat128 \-mno\-float128 \-mfloat128\-hardware \-mno\-float128\-hardware ! \&\-mlra \-mno\-lra\fR .Sp \&\fI\s-1RX\s0 Options\fR \&\fB\-m64bit\-doubles \-m32bit\-doubles \-fpu \-nofpu *************** In C mode, this is equivalent to \fB\-st *** 1692,1698 **** equivalent to \fB\-std=c++98\fR. .Sp This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO ! C90\s0 (when compiling C code), or of standard \*(C+ (when compiling \*(C+ code), such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, and predefined macros such as \f(CW\*(C`unix\*(C'\fR and \f(CW\*(C`vax\*(C'\fR that identify the type of system you are using. It also enables the undesirable and --- 1695,1701 ---- equivalent to \fB\-std=c++98\fR. .Sp This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO ! C90 \s0(when compiling C code), or of standard \*(C+ (when compiling \*(C+ code), such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR keywords, and predefined macros such as \f(CW\*(C`unix\*(C'\fR and \f(CW\*(C`vax\*(C'\fR that identify the type of system you are using. It also enables the undesirable and *************** from declaring certain functions or defi *** 1719,1725 **** programs that might use these names for other things. .Sp Functions that are normally built in but do not have semantics ! defined by \s-1ISO C\s0 (such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in functions when \fB\-ansi\fR is used. .IP "\fB\-std=\fR" 4 .IX Item "-std=" --- 1722,1728 ---- programs that might use these names for other things. .Sp Functions that are normally built in but do not have semantics ! defined by \s-1ISO C \s0(such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in functions when \fB\-ansi\fR is used. .IP "\fB\-std=\fR" 4 .IX Item "-std=" *************** with \s-1ISO C90\s0 are disabled). Same *** 1769,1775 **** .IP "\fBiso9899:199x\fR" 4 .IX Item "iso9899:199x" .PD ! \&\s-1ISO C99.\s0 This standard is substantially completely supported, modulo bugs and floating-point issues (mainly but not entirely relating to optional C99 features from Annexes F and G). See --- 1772,1778 ---- .IP "\fBiso9899:199x\fR" 4 .IX Item "iso9899:199x" .PD ! \&\s-1ISO C99. \s0 This standard is substantially completely supported, modulo bugs and floating-point issues (mainly but not entirely relating to optional C99 features from Annexes F and G). See *************** interfaces) and L (Analyzability). The *** 1794,1814 **** .IP "\fBgnu89\fR" 4 .IX Item "gnu89" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C90\s0 (including some C99 features). .IP "\fBgnu99\fR" 4 .IX Item "gnu99" .PD 0 .IP "\fBgnu9x\fR" 4 .IX Item "gnu9x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C99.\s0 The name \fBgnu9x\fR is deprecated. .IP "\fBgnu11\fR" 4 .IX Item "gnu11" .PD 0 .IP "\fBgnu1x\fR" 4 .IX Item "gnu1x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C11.\s0 This is the default for C code. The name \fBgnu1x\fR is deprecated. .IP "\fBc++98\fR" 4 .IX Item "c++98" --- 1797,1817 ---- .IP "\fBgnu89\fR" 4 .IX Item "gnu89" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C90 \s0(including some C99 features). .IP "\fBgnu99\fR" 4 .IX Item "gnu99" .PD 0 .IP "\fBgnu9x\fR" 4 .IX Item "gnu9x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C99. \s0 The name \fBgnu9x\fR is deprecated. .IP "\fBgnu11\fR" 4 .IX Item "gnu11" .PD 0 .IP "\fBgnu1x\fR" 4 .IX Item "gnu1x" .PD ! \&\s-1GNU\s0 dialect of \s-1ISO C11. \s0 This is the default for C code. The name \fBgnu1x\fR is deprecated. .IP "\fBc++98\fR" 4 .IX Item "c++98" *************** relevant for \*(C+ programs. *** 2147,2153 **** Here is a list of options that are \fIonly\fR for compiling \*(C+ programs: .IP "\fB\-fabi\-version=\fR\fIn\fR" 4 .IX Item "-fabi-version=n" ! Use version \fIn\fR of the \*(C+ \s-1ABI.\s0 The default is version 0. .Sp Version 0 refers to the version conforming most closely to the \*(C+ \s-1ABI\s0 specification. Therefore, the \s-1ABI\s0 obtained using version 0 --- 2150,2156 ---- Here is a list of options that are \fIonly\fR for compiling \*(C+ programs: .IP "\fB\-fabi\-version=\fR\fIn\fR" 4 .IX Item "-fabi-version=n" ! Use version \fIn\fR of the \*(C+ \s-1ABI. \s0 The default is version 0. .Sp Version 0 refers to the version conforming most closely to the \*(C+ \s-1ABI\s0 specification. Therefore, the \s-1ABI\s0 obtained using version 0 *************** exhaustion is signalled by throwing \f(C *** 2223,2229 **** .IP "\fB\-fconcepts\fR" 4 .IX Item "-fconcepts" Enable support for the \*(C+ Extensions for Concepts Technical ! Specification, \s-1ISO 19217\s0 (2015), which allows code like .Sp .Vb 2 \& template concept bool Addable = requires (T t) { t + t; }; --- 2226,2232 ---- .IP "\fB\-fconcepts\fR" 4 .IX Item "-fconcepts" Enable support for the \*(C+ Extensions for Concepts Technical ! Specification, \s-1ISO 19217 \s0(2015), which allows code like .Sp .Vb 2 \& template concept bool Addable = requires (T t) { t + t; }; *************** int and getting a pointer to member func *** 2351,2357 **** .IP "\fB\-fno\-nonansi\-builtins\fR" 4 .IX Item "-fno-nonansi-builtins" Disable built-in declarations of functions that are not mandated by ! \&\s-1ANSI/ISO C.\s0 These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR, \&\f(CW\*(C`index\*(C'\fR, \f(CW\*(C`bzero\*(C'\fR, \f(CW\*(C`conjf\*(C'\fR, and other related functions. .IP "\fB\-fnothrow\-opt\fR" 4 .IX Item "-fnothrow-opt" --- 2354,2360 ---- .IP "\fB\-fno\-nonansi\-builtins\fR" 4 .IX Item "-fno-nonansi-builtins" Disable built-in declarations of functions that are not mandated by ! \&\s-1ANSI/ISO C. \s0 These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR, \&\f(CW\*(C`index\*(C'\fR, \f(CW\*(C`bzero\*(C'\fR, \f(CW\*(C`conjf\*(C'\fR, and other related functions. .IP "\fB\-fnothrow\-opt\fR" 4 .IX Item "-fnothrow-opt" *************** are taken in different shared objects. *** 2466,2472 **** The effect of this is that \s-1GCC\s0 may, effectively, mark inline methods with \&\f(CW\*(C`_\|_attribute_\|_ ((visibility ("hidden")))\*(C'\fR so that they do not appear in the export table of a \s-1DSO\s0 and do not require a \s-1PLT\s0 indirection ! when used within the \s-1DSO.\s0 Enabling this option can have a dramatic effect on load and link times of a \s-1DSO\s0 as it massively reduces the size of the dynamic export table when the library makes heavy use of templates. .Sp --- 2469,2475 ---- The effect of this is that \s-1GCC\s0 may, effectively, mark inline methods with \&\f(CW\*(C`_\|_attribute_\|_ ((visibility ("hidden")))\*(C'\fR so that they do not appear in the export table of a \s-1DSO\s0 and do not require a \s-1PLT\s0 indirection ! when used within the \s-1DSO. \s0 Enabling this option can have a dramatic effect on load and link times of a \s-1DSO\s0 as it massively reduces the size of the dynamic export table when the library makes heavy use of templates. .Sp *************** have meanings only for \*(C+ programs: *** 2536,2542 **** .IP "\fB\-Wabi\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wabi (C, Objective-C, and Objective- only)" Warn when G++ it generates code that is probably not compatible with ! the vendor-neutral \*(C+ \s-1ABI.\s0 Since G++ now defaults to updating the \&\s-1ABI\s0 with each major release, normally \fB\-Wabi\fR will warn only if there is a check added later in a release series for an \s-1ABI\s0 issue discovered since the initial release. \fB\-Wabi\fR will warn about --- 2539,2545 ---- .IP "\fB\-Wabi\fR (C, Objective-C, \*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wabi (C, Objective-C, and Objective- only)" Warn when G++ it generates code that is probably not compatible with ! the vendor-neutral \*(C+ \s-1ABI. \s0 Since G++ now defaults to updating the \&\s-1ABI\s0 with each major release, normally \fB\-Wabi\fR will warn only if there is a check added later in a release series for an \s-1ABI\s0 issue discovered since the initial release. \fB\-Wabi\fR will warn about *************** unsignedness, but the standard mandates *** 2851,2878 **** Warn when a primary template declaration is encountered. Some coding rules disallow templates, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so ! one can still use the \s-1STL.\s0 One may also instantiate or specialize templates. .IP "\fB\-Wmultiple\-inheritance\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wmultiple-inheritance ( and Objective- only)" Warn when a class is defined with multiple direct base classes. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL.\s0 One may also define classes that indirectly use multiple inheritance. .IP "\fB\-Wvirtual\-inheritance\fR" 4 .IX Item "-Wvirtual-inheritance" Warn when a class is defined with a virtual direct base classe. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL.\s0 One may also define classes that indirectly use virtual inheritance. .IP "\fB\-Wnamespaces\fR" 4 .IX Item "-Wnamespaces" Warn when a namespace definition is opened. Some coding rules disallow namespaces, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so one can still ! use the \s-1STL.\s0 One may also use using directives and qualified names. .IP "\fB\-Wno\-terminate\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wno-terminate ( and Objective- only)" Disable the warning about a throw-expression that will immediately --- 2854,2881 ---- Warn when a primary template declaration is encountered. Some coding rules disallow templates, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so ! one can still use the \s-1STL. \s0 One may also instantiate or specialize templates. .IP "\fB\-Wmultiple\-inheritance\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wmultiple-inheritance ( and Objective- only)" Warn when a class is defined with multiple direct base classes. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL. \s0 One may also define classes that indirectly use multiple inheritance. .IP "\fB\-Wvirtual\-inheritance\fR" 4 .IX Item "-Wvirtual-inheritance" Warn when a class is defined with a virtual direct base classe. Some coding rules disallow multiple inheritance, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the \s-1STL,\s0 so one can still use the \s-1STL. \s0 One may also define classes that indirectly use virtual inheritance. .IP "\fB\-Wnamespaces\fR" 4 .IX Item "-Wnamespaces" Warn when a namespace definition is opened. Some coding rules disallow namespaces, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the \s-1STL,\s0 so one can still ! use the \s-1STL. \s0 One may also use using directives and qualified names. .IP "\fB\-Wno\-terminate\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wno-terminate ( and Objective- only)" Disable the warning about a throw-expression that will immediately *************** runtime. This is the default for most t *** 2918,2924 **** .IP "\fB\-fnext\-runtime\fR" 4 .IX Item "-fnext-runtime" Generate output compatible with the NeXT runtime. This is the default ! for NeXT-based systems, including Darwin and Mac \s-1OS X.\s0 The macro \&\f(CW\*(C`_\|_NEXT_RUNTIME_\|_\*(C'\fR is predefined if (and only if) this option is used. .IP "\fB\-fno\-nil\-receivers\fR" 4 --- 2921,2927 ---- .IP "\fB\-fnext\-runtime\fR" 4 .IX Item "-fnext-runtime" Generate output compatible with the NeXT runtime. This is the default ! for NeXT-based systems, including Darwin and Mac \s-1OS X. \s0 The macro \&\f(CW\*(C`_\|_NEXT_RUNTIME_\|_\*(C'\fR is predefined if (and only if) this option is used. .IP "\fB\-fno\-nil\-receivers\fR" 4 *************** This option is currently supported only *** 2935,2941 **** case, Version 0 is the traditional (32\-bit) \s-1ABI\s0 without support for properties and other Objective-C 2.0 additions. Version 1 is the traditional (32\-bit) \s-1ABI\s0 with support for properties and other ! Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI.\s0 If nothing is specified, the default is Version 0 on 32\-bit target machines, and Version 2 on 64\-bit target machines. .IP "\fB\-fobjc\-call\-cxx\-cdtors\fR" 4 --- 2938,2944 ---- case, Version 0 is the traditional (32\-bit) \s-1ABI\s0 without support for properties and other Objective-C 2.0 additions. Version 1 is the traditional (32\-bit) \s-1ABI\s0 with support for properties and other ! Objective-C 2.0 additions. Version 2 is the modern (64\-bit) \s-1ABI. \s0 If nothing is specified, the default is Version 0 on 32\-bit target machines, and Version 2 on 64\-bit target machines. .IP "\fB\-fobjc\-call\-cxx\-cdtors\fR" 4 *************** version of the NeXT runtime \s-1ABI,\s0 *** 2993,2999 **** .IP "\fB\-fobjc\-std=objc1\fR" 4 .IX Item "-fobjc-std=objc1" Conform to the language syntax of Objective-C 1.0, the language ! recognized by \s-1GCC 4.0.\s0 This only affects the Objective-C additions to the C/\*(C+ language; it does not affect conformance to C/\*(C+ standards, which is controlled by the separate C/\*(C+ dialect option flags. When this option is used with the Objective-C or Objective\-\*(C+ compiler, --- 2996,3002 ---- .IP "\fB\-fobjc\-std=objc1\fR" 4 .IX Item "-fobjc-std=objc1" Conform to the language syntax of Objective-C 1.0, the language ! recognized by \s-1GCC 4.0. \s0 This only affects the Objective-C additions to the C/\*(C+ language; it does not affect conformance to C/\*(C+ standards, which is controlled by the separate C/\*(C+ dialect option flags. When this option is used with the Objective-C or Objective\-\*(C+ compiler, *************** warns that an unrecognized option is pre *** 3293,3299 **** .PD Issue all the warnings demanded by strict \s-1ISO C\s0 and \s-1ISO \*(C+\s0; reject all programs that use forbidden extensions, and some other ! programs that do not follow \s-1ISO C\s0 and \s-1ISO \*(C+.\s0 For \s-1ISO C,\s0 follows the version of the \s-1ISO C\s0 standard specified by any \fB\-std\fR option used. .Sp Valid \s-1ISO C\s0 and \s-1ISO \*(C+\s0 programs should compile properly with or without --- 3296,3302 ---- .PD Issue all the warnings demanded by strict \s-1ISO C\s0 and \s-1ISO \*(C+\s0; reject all programs that use forbidden extensions, and some other ! programs that do not follow \s-1ISO C\s0 and \s-1ISO \*(C+. \s0 For \s-1ISO C,\s0 follows the version of the \s-1ISO C\s0 standard specified by any \fB\-std\fR option used. .Sp Valid \s-1ISO C\s0 and \s-1ISO \*(C+\s0 programs should compile properly with or without *************** these escape routes; application program *** 3311,3317 **** Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO C\s0 conformance. They soon find that it does not do quite what they want: it finds some non-ISO practices, but not all\-\-\-only those for which ! \&\s-1ISO C\s0 \fIrequires\fR a diagnostic, and some others for which diagnostics have been added. .Sp A feature to report any failure to conform to \s-1ISO C\s0 might be useful in --- 3314,3320 ---- Some users try to use \fB\-Wpedantic\fR to check programs for strict \s-1ISO C\s0 conformance. They soon find that it does not do quite what they want: it finds some non-ISO practices, but not all\-\-\-only those for which ! \&\s-1ISO C \s0\fIrequires\fR a diagnostic, and some others for which diagnostics have been added. .Sp A feature to report any failure to conform to \s-1ISO C\s0 might be useful in *************** This warning is enabled by \fB\-Wall\fR. *** 3448,3453 **** --- 3451,3460 ---- Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR comment, or whenever a Backslash-Newline appears in a \fB//\fR comment. This warning is enabled by \fB\-Wall\fR. + .IP "\fB\-Wchkp\fR" 4 + .IX Item "-Wchkp" + Warn about an invalid memory access that is found by Pointer Bounds Checker + (\fB\-fcheck\-pointer\-bounds\fR). .IP "\fB\-Wno\-coverage\-mismatch\fR" 4 .IX Item "-Wno-coverage-mismatch" Warn if feedback profiles do not match when using the *************** This warning is enabled by \fB\-Wall\fR *** 4094,4100 **** .IP "\fB\-Wunknown\-pragmas\fR" 4 .IX Item "-Wunknown-pragmas" Warn when a \f(CW\*(C`#pragma\*(C'\fR directive is encountered that is not understood by ! \&\s-1GCC.\s0 If this command-line option is used, warnings are even issued for unknown pragmas in system header files. This is not the case if the warnings are only enabled by the \fB\-Wall\fR command-line option. .IP "\fB\-Wno\-pragmas\fR" 4 --- 4101,4107 ---- .IP "\fB\-Wunknown\-pragmas\fR" 4 .IX Item "-Wunknown-pragmas" Warn when a \f(CW\*(C`#pragma\*(C'\fR directive is encountered that is not understood by ! \&\s-1GCC. \s0 If this command-line option is used, warnings are even issued for unknown pragmas in system header files. This is not the case if the warnings are only enabled by the \fB\-Wall\fR command-line option. .IP "\fB\-Wno\-pragmas\fR" 4 *************** probably mistaken. *** 4398,4404 **** .IP "\fB\-Wtraditional\fR (C and Objective-C only)" 4 .IX Item "-Wtraditional (C and Objective-C only)" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C.\s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and/or problematic constructs that should be avoided. .RS 4 .IP "*" 4 --- 4405,4411 ---- .IP "\fB\-Wtraditional\fR (C and Objective-C only)" 4 .IX Item "-Wtraditional (C and Objective-C only)" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and/or problematic constructs that should be avoided. .RS 4 .IP "*" 4 *************** except when the same as the default prom *** 4480,4486 **** .IX Item "-Wdeclaration-after-statement (C and Objective-C only)" Warn when a declaration is found after a statement in a block. This construct, known from \*(C+, was introduced with \s-1ISO C99\s0 and is by default ! allowed in \s-1GCC.\s0 It is not supported by \s-1ISO C90.\s0 .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" Warn if an undefined identifier is evaluated in an \f(CW\*(C`#if\*(C'\fR directive. --- 4487,4493 ---- .IX Item "-Wdeclaration-after-statement (C and Objective-C only)" Warn when a declaration is found after a statement in a block. This construct, known from \*(C+, was introduced with \s-1ISO C99\s0 and is by default ! allowed in \s-1GCC. \s0 It is not supported by \s-1ISO C90. \s0 .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" Warn if an undefined identifier is evaluated in an \f(CW\*(C`#if\*(C'\fR directive. *************** Warn about \s-1ISO C\s0 constructs that *** 4652,4663 **** .IX Item "-Wc++11-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 1998\s0 and \s-1ISO \*(C+ 2011,\s0 e.g., identifiers in \s-1ISO \*(C+ 1998\s0 that are keywords ! in \s-1ISO \*(C+ 2011.\s0 This warning turns on \fB\-Wnarrowing\fR and is enabled by \fB\-Wall\fR. .IP "\fB\-Wc++14\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wc++14-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 2011\s0 ! and \s-1ISO \*(C+ 2014.\s0 This warning is enabled by \fB\-Wall\fR. .IP "\fB\-Wcast\-qual\fR" 4 .IX Item "-Wcast-qual" Warn whenever a pointer is cast so as to remove a type qualifier from --- 4659,4670 ---- .IX Item "-Wc++11-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 1998\s0 and \s-1ISO \*(C+ 2011,\s0 e.g., identifiers in \s-1ISO \*(C+ 1998\s0 that are keywords ! in \s-1ISO \*(C+ 2011. \s0 This warning turns on \fB\-Wnarrowing\fR and is enabled by \fB\-Wall\fR. .IP "\fB\-Wc++14\-compat\fR (\*(C+ and Objective\-\*(C+ only)" 4 .IX Item "-Wc++14-compat ( and Objective- only)" Warn about \*(C+ constructs whose meaning differs between \s-1ISO \*(C+ 2011\s0 ! and \s-1ISO \*(C+ 2014. \s0 This warning is enabled by \fB\-Wall\fR. .IP "\fB\-Wcast\-qual\fR" 4 .IX Item "-Wcast-qual" Warn whenever a pointer is cast so as to remove a type qualifier from *************** when applied ensure that two sequences t *** 4990,4996 **** the same sequence. \s-1GCC\s0 can warn you if you are using identifiers that have not been normalized; this option controls that warning. .Sp ! There are four levels of warning supported by \s-1GCC.\s0 The default is \&\fB\-Wnormalized=nfc\fR, which warns about any identifier that is not in the \s-1ISO 10646 \*(L"C\*(R"\s0 normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the recommended form for most uses. It is equivalent to --- 4997,5003 ---- the same sequence. \s-1GCC\s0 can warn you if you are using identifiers that have not been normalized; this option controls that warning. .Sp ! There are four levels of warning supported by \s-1GCC. \s0 The default is \&\fB\-Wnormalized=nfc\fR, which warns about any identifier that is not in the \s-1ISO 10646 \*(L"C\*(R"\s0 normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the recommended form for most uses. It is equivalent to *************** recommended form for most uses. It is e *** 4999,5006 **** Unfortunately, there are some characters allowed in identifiers by \&\s-1ISO C\s0 and \s-1ISO \*(C+\s0 that, when turned into \s-1NFC,\s0 are not allowed in identifiers. That is, there's no way to use these symbols in portable ! \&\s-1ISO C\s0 or \*(C+ and have all your identifiers in \s-1NFC.\s0 ! \&\fB\-Wnormalized=id\fR suppresses the warning for these characters. It is hoped that future versions of the standards involved will correct this, which is why this option is not the default. .Sp --- 5006,5013 ---- Unfortunately, there are some characters allowed in identifiers by \&\s-1ISO C\s0 and \s-1ISO \*(C+\s0 that, when turned into \s-1NFC,\s0 are not allowed in identifiers. That is, there's no way to use these symbols in portable ! \&\s-1ISO C\s0 or \*(C+ and have all your identifiers in \s-1NFC. ! \&\s0\fB\-Wnormalized=id\fR suppresses the warning for these characters. It is hoped that future versions of the standards involved will correct this, which is why this option is not the default. .Sp *************** standard's minimum limit, but very porta *** 5219,5225 **** using longer strings. .Sp The limit applies \fIafter\fR string constant concatenation, and does ! not count the trailing \s-1NUL.\s0 In C90, the limit was 509 characters; in C99, it was raised to 4095. \*(C+98 does not specify a normative minimum maximum, so we do not diagnose overlength strings in \*(C+. .Sp --- 5226,5232 ---- using longer strings. .Sp The limit applies \fIafter\fR string constant concatenation, and does ! not count the trailing \s-1NUL. \s0 In C90, the limit was 509 characters; in C99, it was raised to 4095. \*(C+98 does not specify a normative minimum maximum, so we do not diagnose overlength strings in \*(C+. .Sp *************** to generate the extra information, use \ *** 5276,5282 **** \&\fB\-gxcoff+\fR, \fB\-gxcoff\fR, or \fB\-gvms\fR (see below). .IP "\fB\-ggdb\fR" 4 .IX Item "-ggdb" ! Produce debugging information for use by \s-1GDB.\s0 This means to use the most expressive format available (\s-1DWARF,\s0 stabs, or the native format if neither of those are supported), including \s-1GDB\s0 extensions if at all possible. --- 5283,5289 ---- \&\fB\-gxcoff+\fR, \fB\-gxcoff\fR, or \fB\-gvms\fR (see below). .IP "\fB\-ggdb\fR" 4 .IX Item "-ggdb" ! Produce debugging information for use by \s-1GDB. \s0 This means to use the most expressive format available (\s-1DWARF,\s0 stabs, or the native format if neither of those are supported), including \s-1GDB\s0 extensions if at all possible. *************** be useful, this option requires a debugg *** 5419,5425 **** files. .IP "\fB\-gpubnames\fR" 4 .IX Item "-gpubnames" ! Generate \s-1DWARF\s0 \f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections. .IP "\fB\-ggnu\-pubnames\fR" 4 .IX Item "-ggnu-pubnames" Generate \f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections in a format --- 5426,5432 ---- files. .IP "\fB\-gpubnames\fR" 4 .IX Item "-gpubnames" ! Generate \s-1DWARF \s0\f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections. .IP "\fB\-ggnu\-pubnames\fR" 4 .IX Item "-ggnu-pubnames" Generate \f(CW\*(C`.debug_pubnames\*(C'\fR and \f(CW\*(C`.debug_pubtypes\*(C'\fR sections in a format *************** This option works only with \s-1DWARF\s0 *** 5547,5553 **** .IP "\fB\-fno\-dwarf2\-cfi\-asm\fR" 4 .IX Item "-fno-dwarf2-cfi-asm" Emit \s-1DWARF\s0 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section ! instead of using \s-1GAS\s0 \f(CW\*(C`.cfi_*\*(C'\fR directives. .IP "\fB\-fno\-eliminate\-unused\-debug\-types\fR" 4 .IX Item "-fno-eliminate-unused-debug-types" Normally, when producing \s-1DWARF\s0 output, \s-1GCC\s0 avoids producing debug symbol --- 5554,5560 ---- .IP "\fB\-fno\-dwarf2\-cfi\-asm\fR" 4 .IX Item "-fno-dwarf2-cfi-asm" Emit \s-1DWARF\s0 unwind info as compiler generated \f(CW\*(C`.eh_frame\*(C'\fR section ! instead of using \s-1GAS \s0\f(CW\*(C`.cfi_*\*(C'\fR directives. .IP "\fB\-fno\-eliminate\-unused\-debug\-types\fR" 4 .IX Item "-fno-eliminate-unused-debug-types" Normally, when producing \s-1DWARF\s0 output, \s-1GCC\s0 avoids producing debug symbol *************** function calls and pops them all at once *** 5758,5764 **** Disabled at levels \fB\-O\fR, \fB\-O2\fR, \fB\-O3\fR, \fB\-Os\fR. .IP "\fB\-fforward\-propagate\fR" 4 .IX Item "-fforward-propagate" ! Perform a forward propagation pass on \s-1RTL.\s0 The pass tries to combine two instructions and checks if the result can be simplified. If loop unrolling is active, two passes are performed and the second is scheduled after loop unrolling. --- 5765,5771 ---- Disabled at levels \fB\-O\fR, \fB\-O2\fR, \fB\-O3\fR, \fB\-Os\fR. .IP "\fB\-fforward\-propagate\fR" 4 .IX Item "-fforward-propagate" ! Perform a forward propagation pass on \s-1RTL. \s0 The pass tries to combine two instructions and checks if the result can be simplified. If loop unrolling is active, two passes are performed and the second is scheduled after loop unrolling. *************** attribute or declspec *** 5909,5915 **** In C, emit \f(CW\*(C`static\*(C'\fR functions that are declared \f(CW\*(C`inline\*(C'\fR into the object file, even if the function has been inlined into all of its callers. This switch does not affect functions using the ! \&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU C90.\s0 In \*(C+, emit any and all inline functions into the object file. .IP "\fB\-fkeep\-static\-functions\fR" 4 .IX Item "-fkeep-static-functions" --- 5916,5922 ---- In C, emit \f(CW\*(C`static\*(C'\fR functions that are declared \f(CW\*(C`inline\*(C'\fR into the object file, even if the function has been inlined into all of its callers. This switch does not affect functions using the ! \&\f(CW\*(C`extern inline\*(C'\fR extension in \s-1GNU C90. \s0 In \*(C+, emit any and all inline functions into the object file. .IP "\fB\-fkeep\-static\-functions\fR" 4 .IX Item "-fkeep-static-functions" *************** The default is \fB\-ffunction\-cse\fR *** 5983,5989 **** .IP "\fB\-fno\-zero\-initialized\-in\-bss\fR" 4 .IX Item "-fno-zero-initialized-in-bss" If the target supports a \s-1BSS\s0 section, \s-1GCC\s0 by default puts variables that ! are initialized to zero into \s-1BSS.\s0 This can save space in the resulting code. .Sp This option turns off this behavior because some programs explicitly --- 5990,5996 ---- .IP "\fB\-fno\-zero\-initialized\-in\-bss\fR" 4 .IX Item "-fno-zero-initialized-in-bss" If the target supports a \s-1BSS\s0 section, \s-1GCC\s0 by default puts variables that ! are initialized to zero into \s-1BSS. \s0 This can save space in the resulting code. .Sp This option turns off this behavior because some programs explicitly *************** pseudo-register that does not get a hard *** 6278,6284 **** stack slot, and as a result function stack frames are larger. .IP "\fB\-flra\-remat\fR" 4 .IX Item "-flra-remat" ! Enable CFG-sensitive rematerialization in \s-1LRA.\s0 Instead of loading values of spilled pseudos, \s-1LRA\s0 tries to rematerialize (recalculate) values if it is profitable. .Sp --- 6285,6291 ---- stack slot, and as a result function stack frames are larger. .IP "\fB\-flra\-remat\fR" 4 .IX Item "-flra-remat" ! Enable CFG-sensitive rematerialization in \s-1LRA. \s0 Instead of loading values of spilled pseudos, \s-1LRA\s0 tries to rematerialize (recalculate) values if it is profitable. .Sp *************** transformation infrastructure. *** 6691,6697 **** Enable the identity transformation for graphite. For every SCoP we generate the polyhedral representation and transform it back to gimple. Using \&\fB\-fgraphite\-identity\fR we can check the costs or benefits of the ! \&\s-1GIMPLE\s0 \-> \s-1GRAPHITE\s0 \-> \s-1GIMPLE\s0 transformation. Some minimal optimizations are also performed by the code generator isl, like index splitting and dead code elimination in loops. .IP "\fB\-floop\-nest\-optimize\fR" 4 --- 6698,6704 ---- Enable the identity transformation for graphite. For every SCoP we generate the polyhedral representation and transform it back to gimple. Using \&\fB\-fgraphite\-identity\fR we can check the costs or benefits of the ! \&\s-1GIMPLE \-\s0> \s-1GRAPHITE \-\s0> \s-1GIMPLE\s0 transformation. Some minimal optimizations are also performed by the code generator isl, like index splitting and dead code elimination in loops. .IP "\fB\-floop\-nest\-optimize\fR" 4 *************** information. *** 7207,7213 **** .IP "\fB\-flto[=\fR\fIn\fR\fB]\fR" 4 .IX Item "-flto[=n]" This option runs the standard link-time optimizer. When invoked ! with source code, it generates \s-1GIMPLE\s0 (one of \s-1GCC\s0's internal representations) and writes it to special \s-1ELF\s0 sections in the object file. When the object files are linked together, all the function bodies are read from these \s-1ELF\s0 sections and instantiated as if they --- 7214,7220 ---- .IP "\fB\-flto[=\fR\fIn\fR\fB]\fR" 4 .IX Item "-flto[=n]" This option runs the standard link-time optimizer. When invoked ! with source code, it generates \s-1GIMPLE \s0(one of \s-1GCC\s0's internal representations) and writes it to special \s-1ELF\s0 sections in the object file. When the object files are linked together, all the function bodies are read from these \s-1ELF\s0 sections and instantiated as if they *************** E.g. *** 7547,7553 **** .Ve .Sp Then use the \fBcreate_gcov\fR tool to convert the raw profile data ! to a format that can be used by \s-1GCC.\s0 You must also supply the unstripped binary for your program to this tool. See <\fBhttps://github.com/google/autofdo\fR>. .Sp --- 7554,7560 ---- .Ve .Sp Then use the \fBcreate_gcov\fR tool to convert the raw profile data ! to a format that can be used by \s-1GCC. \s0 You must also supply the unstripped binary for your program to this tool. See <\fBhttps://github.com/google/autofdo\fR>. .Sp *************** them to store all pertinent intermediate *** 7577,7584 **** .IP "\fB\-fexcess\-precision=\fR\fIstyle\fR" 4 .IX Item "-fexcess-precision=style" This option allows further control over excess precision on machines ! where floating-point registers have more precision than the \s-1IEEE\s0 ! \&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not support operations rounding to those types. By default, \&\fB\-fexcess\-precision=fast\fR is in effect; this means that operations are carried out in the precision of the registers and that --- 7584,7591 ---- .IP "\fB\-fexcess\-precision=\fR\fIstyle\fR" 4 .IX Item "-fexcess-precision=style" This option allows further control over excess precision on machines ! where floating-point registers have more precision than the \s-1IEEE ! \&\s0\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR types and the processor does not support operations rounding to those types. By default, \&\fB\-fexcess\-precision=fast\fR is in effect; this means that operations are carried out in the precision of the registers and that *************** whether the result of a complex multipli *** 7752,7759 **** default is \fB\-fno\-cx\-limited\-range\fR, but is enabled by \&\fB\-ffast\-math\fR. .Sp ! This option controls the default setting of the \s-1ISO C99\s0 ! \&\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to all languages. .IP "\fB\-fcx\-fortran\-rules\fR" 4 .IX Item "-fcx-fortran-rules" --- 7759,7766 ---- default is \fB\-fno\-cx\-limited\-range\fR, but is enabled by \&\fB\-ffast\-math\fR. .Sp ! This option controls the default setting of the \s-1ISO C99 ! \&\s0\f(CW\*(C`CX_LIMITED_RANGE\*(C'\fR pragma. Nevertheless, the option applies to all languages. .IP "\fB\-fcx\-fortran\-rules\fR" 4 .IX Item "-fcx-fortran-rules" *************** Tuning this may improve compilation spee *** 8358,8364 **** generation. .Sp The default is 30% + 70% * (\s-1RAM/1GB\s0) with an upper bound of 100% when ! \&\s-1RAM\s0 >= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\*(R"\s0 is the smallest of actual \s-1RAM\s0 and \f(CW\*(C`RLIMIT_DATA\*(C'\fR or \f(CW\*(C`RLIMIT_AS\*(C'\fR. If \&\s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower bound of 30% is used. Setting this parameter and --- 8365,8371 ---- generation. .Sp The default is 30% + 70% * (\s-1RAM/1GB\s0) with an upper bound of 100% when ! \&\s-1RAM \s0>= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\*(R"\s0 is the smallest of actual \s-1RAM\s0 and \f(CW\*(C`RLIMIT_DATA\*(C'\fR or \f(CW\*(C`RLIMIT_AS\*(C'\fR. If \&\s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower bound of 30% is used. Setting this parameter and *************** This value is the best found from numero *** 8582,8588 **** This optimization is called inheritance. \s-1EBB\s0 is used as a region to do this optimization. The parameter defines a minimal fall-through edge probability in percentage used to add \s-1BB\s0 to inheritance \s-1EBB\s0 in ! \&\s-1LRA.\s0 The default value of the parameter is 40. The value was chosen from numerous runs of \s-1SPEC2000\s0 on x86\-64. .IP "\fBloop-invariant-max-bbs-in-loop\fR" 4 .IX Item "loop-invariant-max-bbs-in-loop" --- 8589,8595 ---- This optimization is called inheritance. \s-1EBB\s0 is used as a region to do this optimization. The parameter defines a minimal fall-through edge probability in percentage used to add \s-1BB\s0 to inheritance \s-1EBB\s0 in ! \&\s-1LRA. \s0 The default value of the parameter is 40. The value was chosen from numerous runs of \s-1SPEC2000\s0 on x86\-64. .IP "\fBloop-invariant-max-bbs-in-loop\fR" 4 .IX Item "loop-invariant-max-bbs-in-loop" *************** The number of partitions should exceed t *** 8724,8730 **** The default value is 32. .IP "\fBlto-min-partition\fR" 4 .IX Item "lto-min-partition" ! Size of minimal partition for \s-1WHOPR\s0 (in estimated instructions). This prevents expenses of splitting very small programs into too many partitions. .IP "\fBcxx-max-namespaces-for-diagnostic-help\fR" 4 --- 8731,8737 ---- The default value is 32. .IP "\fBlto-min-partition\fR" 4 .IX Item "lto-min-partition" ! Size of minimal partition for \s-1WHOPR \s0(in estimated instructions). This prevents expenses of splitting very small programs into too many partitions. .IP "\fBcxx-max-namespaces-for-diagnostic-help\fR" 4 *************** get trigraph conversion without warnings *** 9647,9653 **** .IP "\fB\-Wtraditional\fR" 4 .IX Item "-Wtraditional" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C.\s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and problematic constructs which should be avoided. .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" --- 9654,9660 ---- .IP "\fB\-Wtraditional\fR" 4 .IX Item "-Wtraditional" Warn about certain constructs that behave differently in traditional and ! \&\s-1ISO C. \s0 Also warn about \s-1ISO C\s0 constructs that have no traditional C equivalent, and problematic constructs which should be avoided. .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" *************** When \fB\-fpreprocessed\fR is in use, \s *** 9843,9849 **** and loads the \s-1PCH.\s0 .Sp This option is off by default, because the resulting preprocessed output ! is only really suitable as input to \s-1GCC.\s0 It is switched on by \&\fB\-save\-temps\fR. .Sp You should not write this \f(CW\*(C`#pragma\*(C'\fR in your own code, but it is --- 9850,9856 ---- and loads the \s-1PCH.\s0 .Sp This option is off by default, because the resulting preprocessed output ! is only really suitable as input to \s-1GCC. \s0 It is switched on by \&\fB\-save\-temps\fR. .Sp You should not write this \f(CW\*(C`#pragma\*(C'\fR in your own code, but it is *************** line. If the value is less than 1 or gr *** 10115,10121 **** ignored. The default is 8. .IP "\fB\-fdebug\-cpp\fR" 4 .IX Item "-fdebug-cpp" ! This option is only useful for debugging \s-1GCC.\s0 When used with \&\fB\-E\fR, dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. The dump of the map holding the location of a token would --- 10122,10128 ---- ignored. The default is 8. .IP "\fB\-fdebug\-cpp\fR" 4 .IX Item "-fdebug-cpp" ! This option is only useful for debugging \s-1GCC. \s0 When used with \&\fB\-E\fR, dumps debugging information about location maps. Every token in the output is preceded by the dump of the map its location belongs to. The dump of the map holding the location of a token would *************** Note that \f(CW\*(C`\-ftrack\-macro\-exp *** 10148,10154 **** .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fexec-charset=charset" Set the execution character set, used for string and character ! constants. The default is \s-1UTF\-8.\s0 \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fwide-exec-charset=charset" --- 10155,10161 ---- .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fexec-charset=charset" Set the execution character set, used for string and character ! constants. The default is \s-1UTF\-8. \s0\fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. .IP "\fB\-fwide\-exec\-charset=\fR\fIcharset\fR" 4 .IX Item "-fwide-exec-charset=charset" *************** problems with encodings that do not fit *** 10161,10169 **** .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 .IX Item "-finput-charset=charset" Set the input character set, used for translation from the character ! set of the input file to the source character set used by \s-1GCC.\s0 If the locale does not specify, or \s-1GCC\s0 cannot get this information from the ! locale, the default is \s-1UTF\-8.\s0 This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. --- 10168,10176 ---- .IP "\fB\-finput\-charset=\fR\fIcharset\fR" 4 .IX Item "-finput-charset=charset" Set the input character set, used for translation from the character ! set of the input file to the source character set used by \s-1GCC. \s0 If the locale does not specify, or \s-1GCC\s0 cannot get this information from the ! locale, the default is \s-1UTF\-8. \s0 This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. \fIcharset\fR can be any encoding supported by the system's \f(CW\*(C`iconv\*(C'\fR library routine. *************** the \s-1GOT\s0 size for the linked execu *** 11039,11045 **** maximum size, you get an error message from the linker indicating that \&\fB\-fpic\fR does not work; in that case, recompile with \fB\-fPIC\fR instead. (These maximums are 8k on the \s-1SPARC,\s0 28k on AArch64 and 32k ! on the m68k and \s-1RS/6000.\s0 The x86 has no such limit.) .Sp Position-independent code requires special support, and therefore works only on certain machines. For the x86, \s-1GCC\s0 supports \s-1PIC\s0 for System V --- 11046,11052 ---- maximum size, you get an error message from the linker indicating that \&\fB\-fpic\fR does not work; in that case, recompile with \fB\-fPIC\fR instead. (These maximums are 8k on the \s-1SPARC,\s0 28k on AArch64 and 32k ! on the m68k and \s-1RS/6000. \s0 The x86 has no such limit.) .Sp Position-independent code requires special support, and therefore works only on certain machines. For the x86, \s-1GCC\s0 supports \s-1PIC\s0 for System V *************** Enable showing virtual operands for ever *** 11721,11727 **** Enable showing line numbers for statements. .IP "\fBuid\fR" 4 .IX Item "uid" ! Enable showing the unique \s-1ID\s0 (\f(CW\*(C`DECL_UID\*(C'\fR) for each variable. .IP "\fBverbose\fR" 4 .IX Item "verbose" Enable showing the tree dump for each statement. --- 11728,11734 ---- Enable showing line numbers for statements. .IP "\fBuid\fR" 4 .IX Item "uid" ! Enable showing the unique \s-1ID \s0(\f(CW\*(C`DECL_UID\*(C'\fR) for each variable. .IP "\fBverbose\fR" 4 .IX Item "verbose" Enable showing the tree dump for each statement. *************** Dump aliasing information for each funct *** 11803,11809 **** appending \fI.alias\fR to the source file name. .IP "\fBccp\fR" 4 .IX Item "ccp" ! Dump each function after \s-1CCP.\s0 The file name is made by appending \&\fI.ccp\fR to the source file name. .IP "\fBstoreccp\fR" 4 .IX Item "storeccp" --- 11810,11816 ---- appending \fI.alias\fR to the source file name. .IP "\fBccp\fR" 4 .IX Item "ccp" ! Dump each function after \s-1CCP. \s0 The file name is made by appending \&\fI.ccp\fR to the source file name. .IP "\fBstoreccp\fR" 4 .IX Item "storeccp" *************** values for \fIcpu\fR are *** 12825,12845 **** .IP "\fBarc600\fR" 4 .IX Item "arc600" .PD ! Compile for \s-1ARC600.\s0 Aliases: \fB\-mA6\fR, \fB\-mARC600\fR. .IP "\fB\s-1ARC601\s0\fR" 4 .IX Item "ARC601" .PD 0 .IP "\fBarc601\fR" 4 .IX Item "arc601" .PD ! Compile for \s-1ARC601.\s0 Alias: \fB\-mARC601\fR. .IP "\fB\s-1ARC700\s0\fR" 4 .IX Item "ARC700" .PD 0 .IP "\fBarc700\fR" 4 .IX Item "arc700" .PD ! Compile for \s-1ARC700.\s0 Aliases: \fB\-mA7\fR, \fB\-mARC700\fR. This is the default when configured with \fB\-\-with\-cpu=arc700\fR. .IP "\fB\s-1ARCEM\s0\fR" 4 .IX Item "ARCEM" --- 12832,12852 ---- .IP "\fBarc600\fR" 4 .IX Item "arc600" .PD ! Compile for \s-1ARC600. \s0 Aliases: \fB\-mA6\fR, \fB\-mARC600\fR. .IP "\fB\s-1ARC601\s0\fR" 4 .IX Item "ARC601" .PD 0 .IP "\fBarc601\fR" 4 .IX Item "arc601" .PD ! Compile for \s-1ARC601. \s0 Alias: \fB\-mARC601\fR. .IP "\fB\s-1ARC700\s0\fR" 4 .IX Item "ARC700" .PD 0 .IP "\fBarc700\fR" 4 .IX Item "arc700" .PD ! Compile for \s-1ARC700. \s0 Aliases: \fB\-mA7\fR, \fB\-mARC700\fR. This is the default when configured with \fB\-\-with\-cpu=arc700\fR. .IP "\fB\s-1ARCEM\s0\fR" 4 .IX Item "ARCEM" *************** Replaced by \fB\-mmultcost\fR. *** 13359,13365 **** These \fB\-m\fR options are defined for the \s-1ARM\s0 port: .IP "\fB\-mabi=\fR\fIname\fR" 4 .IX Item "-mabi=name" ! Generate code for the specified \s-1ABI.\s0 Permissible values are: \fBapcs-gnu\fR, \&\fBatpcs\fR, \fBaapcs\fR, \fBaapcs-linux\fR and \fBiwmmxt\fR. .IP "\fB\-mapcs\-frame\fR" 4 .IX Item "-mapcs-frame" --- 13366,13372 ---- These \fB\-m\fR options are defined for the \s-1ARM\s0 port: .IP "\fB\-mabi=\fR\fIname\fR" 4 .IX Item "-mabi=name" ! Generate code for the specified \s-1ABI. \s0 Permissible values are: \fBapcs-gnu\fR, \&\fBatpcs\fR, \fBaapcs\fR, \fBaapcs-linux\fR and \fBiwmmxt\fR. .IP "\fB\-mapcs\-frame\fR" 4 .IX Item "-mapcs-frame" *************** The default for this option is@tie{}\fBa *** 13822,13829 **** .ie n .IP """avrxmega5""" 4 .el .IP "\f(CWavrxmega5\fR" 4 .IX Item "avrxmega5" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.\s0 ! \&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR. .ie n .IP """avrxmega6""" 4 .el .IP "\f(CWavrxmega6\fR" 4 .IX Item "avrxmega6" --- 13829,13836 ---- .ie n .IP """avrxmega5""" 4 .el .IP "\f(CWavrxmega5\fR" 4 .IX Item "avrxmega5" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 64@tie{}KiB and up to 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM. ! \&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega64a1\*(C'\fR, \f(CW\*(C`atxmega64a1u\*(C'\fR. .ie n .IP """avrxmega6""" 4 .el .IP "\f(CWavrxmega6\fR" 4 .IX Item "avrxmega6" *************** The default for this option is@tie{}\fBa *** 13832,13839 **** .ie n .IP """avrxmega7""" 4 .el .IP "\f(CWavrxmega7\fR" 4 .IX Item "avrxmega7" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM.\s0 ! \&\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR. .ie n .IP """avrtiny""" 4 .el .IP "\f(CWavrtiny\fR" 4 .IX Item "avrtiny" --- 13839,13846 ---- .ie n .IP """avrxmega7""" 4 .el .IP "\f(CWavrxmega7\fR" 4 .IX Item "avrxmega7" ! \&\*(L"\s-1XMEGA\*(R"\s0 devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of \s-1RAM. ! \&\s0\fImcu\fR\f(CW@tie\fR{}= \f(CW\*(C`atxmega128a1\*(C'\fR, \f(CW\*(C`atxmega128a1u\*(C'\fR, \f(CW\*(C`atxmega128a4u\*(C'\fR. .ie n .IP """avrtiny""" 4 .el .IP "\f(CWavrtiny\fR" 4 .IX Item "avrtiny" *************** for \fImcu\fR=\f(CW\*(C`avrtiny\*(C'\fR, *** 14154,14160 **** If \fImcu\fR specifies a device, this built-in macro is set accordingly. For example, with \fB\-mmcu=atmega8\fR the macro is defined to \f(CW4\fR. ! .ie n .IP """_\|_AVR_\fIDevice\fP_\|_""" 4 .el .IP "\f(CW_\|_AVR_\f(CIDevice\f(CW_\|_\fR" 4 .IX Item "__AVR_Device__" Setting \fB\-mmcu=\fR\fIdevice\fR defines this built-in macro which reflects --- 14161,14167 ---- If \fImcu\fR specifies a device, this built-in macro is set accordingly. For example, with \fB\-mmcu=atmega8\fR the macro is defined to \f(CW4\fR. ! .ie n .IP """_\|_AVR_\f(CIDevice\f(CW_\|_""" 4 .el .IP "\f(CW_\|_AVR_\f(CIDevice\f(CW_\|_\fR" 4 .IX Item "__AVR_Device__" Setting \fB\-mmcu=\fR\fIdevice\fR defines this built-in macro which reflects *************** The definition of these macros is affect *** 14248,14254 **** .el .IP "\f(CW_\|_AVR_SP8_\|_\fR" 4 .IX Item "__AVR_SP8__" .PD ! The device has the \s-1SPH\s0 (high part of stack pointer) special function register or has an 8\-bit stack pointer, respectively. The definition of these macros is affected by \fB\-mmcu=\fR and in the cases of \fB\-mmcu=avr2\fR and \fB\-mmcu=avr25\fR also --- 14255,14261 ---- .el .IP "\f(CW_\|_AVR_SP8_\|_\fR" 4 .IX Item "__AVR_SP8__" .PD ! The device has the \s-1SPH \s0(high part of stack pointer) special function register or has an 8\-bit stack pointer, respectively. The definition of these macros is affected by \fB\-mmcu=\fR and in the cases of \fB\-mmcu=avr2\fR and \fB\-mmcu=avr25\fR also *************** set. *** 14290,14296 **** .el .IP "\f(CW_\|_AVR_ISA_RMW_\|_\fR" 4 .IX Item "__AVR_ISA_RMW__" The device has Read-Modify-Write instructions (\s-1XCH, LAC, LAS\s0 and \s-1LAT\s0). ! .ie n .IP """_\|_AVR_SFR_OFFSET_\|_=\fIoffset\fP""" 4 .el .IP "\f(CW_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW\fR" 4 .IX Item "__AVR_SFR_OFFSET__=offset" Instructions that can address I/O special function registers directly --- 14297,14303 ---- .el .IP "\f(CW_\|_AVR_ISA_RMW_\|_\fR" 4 .IX Item "__AVR_ISA_RMW__" The device has Read-Modify-Write instructions (\s-1XCH, LAC, LAS\s0 and \s-1LAT\s0). ! .ie n .IP """_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW""" 4 .el .IP "\f(CW_\|_AVR_SFR_OFFSET_\|_=\f(CIoffset\f(CW\fR" 4 .IX Item "__AVR_SFR_OFFSET__=offset" Instructions that can address I/O special function registers directly *************** or storage for local variables needs to *** 14626,14632 **** With \fB\-fpic\fR and \fB\-fPIC\fR, don't generate (do generate) instruction sequences that load addresses for functions from the \s-1PLT\s0 part of the \s-1GOT\s0 rather than (traditional on other architectures) calls to the ! \&\s-1PLT.\s0 The default is \fB\-mgotplt\fR. .IP "\fB\-melf\fR" 4 .IX Item "-melf" Legacy no-op option only recognized with the cris-axis-elf and --- 14633,14639 ---- With \fB\-fpic\fR and \fB\-fPIC\fR, don't generate (do generate) instruction sequences that load addresses for functions from the \s-1PLT\s0 part of the \s-1GOT\s0 rather than (traditional on other architectures) calls to the ! \&\s-1PLT. \s0 The default is \fB\-mgotplt\fR. .IP "\fB\-melf\fR" 4 .IX Item "-melf" Legacy no-op option only recognized with the cris-axis-elf and *************** compilers call this option \fB\-ieee_wit *** 14992,14998 **** .IP "\fB\-mieee\-with\-inexact\fR" 4 .IX Item "-mieee-with-inexact" This is like \fB\-mieee\fR except the generated code also maintains ! the \s-1IEEE\s0 \fIinexact-flag\fR. Turning on this option causes the generated code to implement fully-compliant \s-1IEEE\s0 math. In addition to \&\f(CW\*(C`_IEEE_FP\*(C'\fR, \f(CW\*(C`_IEEE_FP_EXACT\*(C'\fR is defined as a preprocessor macro. On some Alpha implementations the resulting code may execute --- 14999,15005 ---- .IP "\fB\-mieee\-with\-inexact\fR" 4 .IX Item "-mieee-with-inexact" This is like \fB\-mieee\fR except the generated code also maintains ! the \s-1IEEE \s0\fIinexact-flag\fR. Turning on this option causes the generated code to implement fully-compliant \s-1IEEE\s0 math. In addition to \&\f(CW\*(C`_IEEE_FP\*(C'\fR, \f(CW\*(C`_IEEE_FP_EXACT\*(C'\fR is defined as a preprocessor macro. On some Alpha implementations the resulting code may execute *************** These \fB\-m\fR options are defined for *** 15621,15627 **** .IP "\fB\-march=\fR\fIarchitecture-type\fR" 4 .IX Item "-march=architecture-type" Generate code for the specified architecture. The choices for ! \&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA 1.0,\s0 \fB1.1\fR for \s-1PA 1.1,\s0 and \fB2.0\fR for \s-1PA 2.0\s0 processors. Refer to \&\fI/usr/lib/sched.models\fR on an HP-UX system to determine the proper architecture option for your machine. Code compiled for lower numbered --- 15628,15634 ---- .IP "\fB\-march=\fR\fIarchitecture-type\fR" 4 .IX Item "-march=architecture-type" Generate code for the specified architecture. The choices for ! \&\fIarchitecture-type\fR are \fB1.0\fR for \s-1PA 1.0, \s0\fB1.1\fR for \s-1PA 1.1,\s0 and \fB2.0\fR for \s-1PA 2.0\s0 processors. Refer to \&\fI/usr/lib/sched.models\fR on an HP-UX system to determine the proper architecture option for your machine. Code compiled for lower numbered *************** library that comes with \s-1GCC,\s0 with *** 15709,15721 **** this to work. .IP "\fB\-msio\fR" 4 .IX Item "-msio" ! Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO.\s0 The default is \&\fB\-mwsio\fR. This generates the predefines, \f(CW\*(C`_\|_hp9000s700\*(C'\fR, ! \&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO.\s0 These options are available under HP-UX and HI-UX. .IP "\fB\-mgnu\-ld\fR" 4 .IX Item "-mgnu-ld" ! Use options specific to \s-1GNU\s0 \fBld\fR. This passes \fB\-shared\fR to \fBld\fR when building a shared library. It is the default when \s-1GCC\s0 is configured, explicitly or implicitly, with the \s-1GNU\s0 linker. This option does not --- 15716,15728 ---- this to work. .IP "\fB\-msio\fR" 4 .IX Item "-msio" ! Generate the predefine, \f(CW\*(C`_SIO\*(C'\fR, for server \s-1IO. \s0 The default is \&\fB\-mwsio\fR. This generates the predefines, \f(CW\*(C`_\|_hp9000s700\*(C'\fR, ! \&\f(CW\*(C`_\|_hp9000s700_\|_\*(C'\fR and \f(CW\*(C`_WSIO\*(C'\fR, for workstation \s-1IO. \s0 These options are available under HP-UX and HI-UX. .IP "\fB\-mgnu\-ld\fR" 4 .IX Item "-mgnu-ld" ! Use options specific to \s-1GNU \s0\fBld\fR. This passes \fB\-shared\fR to \fBld\fR when building a shared library. It is the default when \s-1GCC\s0 is configured, explicitly or implicitly, with the \s-1GNU\s0 linker. This option does not *************** using \fBwhich `gcc \-print\-prog\-name= *** 15728,15734 **** on the 64\-bit HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR. .IP "\fB\-mhp\-ld\fR" 4 .IX Item "-mhp-ld" ! Use options specific to \s-1HP\s0 \fBld\fR. This passes \fB\-b\fR to \fBld\fR when building a shared library and passes \fB+Accept TypeMismatch\fR to \fBld\fR on all links. It is the default when \s-1GCC\s0 is configured, explicitly or --- 15735,15741 ---- on the 64\-bit HP-UX \s-1GCC,\s0 i.e. configured with \fBhppa*64*\-*\-hpux*\fR. .IP "\fB\-mhp\-ld\fR" 4 .IX Item "-mhp-ld" ! Use options specific to \s-1HP \s0\fBld\fR. This passes \fB\-b\fR to \fBld\fR when building a shared library and passes \fB+Accept TypeMismatch\fR to \fBld\fR on all links. It is the default when \s-1GCC\s0 is configured, explicitly or *************** have to be emulated by software on the 6 *** 16395,16401 **** does not have code to emulate those instructions. .IP "\fB\-mcpu32\fR" 4 .IX Item "-mcpu32" ! Generate output for a \s-1CPU32.\s0 This is the default when the compiler is configured for CPU32\-based systems. It is equivalent to \fB\-march=cpu32\fR. .Sp --- 16402,16408 ---- does not have code to emulate those instructions. .IP "\fB\-mcpu32\fR" 4 .IX Item "-mcpu32" ! Generate output for a \s-1CPU32. \s0 This is the default when the compiler is configured for CPU32\-based systems. It is equivalent to \fB\-march=cpu32\fR. .Sp *************** Use this option for microcontrollers wit *** 16404,16410 **** 68336, 68340, 68341, 68349 and 68360. .IP "\fB\-m5200\fR" 4 .IX Item "-m5200" ! Generate output for a 520X ColdFire \s-1CPU.\s0 This is the default when the compiler is configured for 520X\-based systems. It is equivalent to \fB\-mcpu=5206\fR, and is now deprecated in favor of that option. --- 16411,16417 ---- 68336, 68340, 68341, 68349 and 68360. .IP "\fB\-m5200\fR" 4 .IX Item "-m5200" ! Generate output for a 520X ColdFire \s-1CPU. \s0 This is the default when the compiler is configured for 520X\-based systems. It is equivalent to \fB\-mcpu=5206\fR, and is now deprecated in favor of that option. *************** Use this option for microcontroller with *** 16413,16419 **** the \s-1MCF5202, MCF5203, MCF5204\s0 and \s-1MCF5206.\s0 .IP "\fB\-m5206e\fR" 4 .IX Item "-m5206e" ! Generate output for a 5206e ColdFire \s-1CPU.\s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5206e\fR. .IP "\fB\-m528x\fR" 4 .IX Item "-m528x" --- 16420,16426 ---- the \s-1MCF5202, MCF5203, MCF5204\s0 and \s-1MCF5206.\s0 .IP "\fB\-m5206e\fR" 4 .IX Item "-m5206e" ! Generate output for a 5206e ColdFire \s-1CPU. \s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5206e\fR. .IP "\fB\-m528x\fR" 4 .IX Item "-m528x" *************** The option is now deprecated in favor of *** 16422,16436 **** \&\fB\-mcpu=528x\fR. .IP "\fB\-m5307\fR" 4 .IX Item "-m5307" ! Generate output for a ColdFire 5307 \s-1CPU.\s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5307\fR. .IP "\fB\-m5407\fR" 4 .IX Item "-m5407" ! Generate output for a ColdFire 5407 \s-1CPU.\s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5407\fR. .IP "\fB\-mcfv4e\fR" 4 .IX Item "-mcfv4e" ! Generate output for a ColdFire V4e family \s-1CPU\s0 (e.g. 547x/548x). This includes use of hardware floating-point instructions. The option is equivalent to \fB\-mcpu=547x\fR, and is now deprecated in favor of that option. --- 16429,16443 ---- \&\fB\-mcpu=528x\fR. .IP "\fB\-m5307\fR" 4 .IX Item "-m5307" ! Generate output for a ColdFire 5307 \s-1CPU. \s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5307\fR. .IP "\fB\-m5407\fR" 4 .IX Item "-m5407" ! Generate output for a ColdFire 5407 \s-1CPU. \s0 The option is now deprecated in favor of the equivalent \fB\-mcpu=5407\fR. .IP "\fB\-mcfv4e\fR" 4 .IX Item "-mcfv4e" ! Generate output for a ColdFire V4e family \s-1CPU \s0(e.g. 547x/548x). This includes use of hardware floating-point instructions. The option is equivalent to \fB\-mcpu=547x\fR, and is now deprecated in favor of that option. *************** The option is equivalent to \fB\-march=6 *** 16457,16463 **** .IX Item "-m68881" .PD Generate floating-point instructions. This is the default for 68020 ! and above, and for ColdFire devices that have an \s-1FPU.\s0 It defines the macro \f(CW\*(C`_\|_HAVE_68881_\|_\*(C'\fR on M680x0 targets and \f(CW\*(C`_\|_mcffpu_\|_\*(C'\fR on ColdFire targets. .IP "\fB\-msoft\-float\fR" 4 --- 16464,16470 ---- .IX Item "-m68881" .PD Generate floating-point instructions. This is the default for 68020 ! and above, and for ColdFire devices that have an \s-1FPU. \s0 It defines the macro \f(CW\*(C`_\|_HAVE_68881_\|_\*(C'\fR on M680x0 targets and \f(CW\*(C`_\|_mcffpu_\|_\*(C'\fR on ColdFire targets. .IP "\fB\-msoft\-float\fR" 4 *************** the default for ColdFire devices that ha *** 16474,16481 **** Generate (do not generate) ColdFire hardware divide and remainder instructions. If \fB\-march\fR is used without \fB\-mcpu\fR, the default is \*(L"on\*(R" for ColdFire architectures and \*(L"off\*(R" for M680x0 ! architectures. Otherwise, the default is taken from the target \s-1CPU\s0 ! (either the default \s-1CPU,\s0 or the one specified by \fB\-mcpu\fR). For example, the default is \*(L"off\*(R" for \fB\-mcpu=5206\fR and \*(L"on\*(R" for \&\fB\-mcpu=5206e\fR. .Sp --- 16481,16488 ---- Generate (do not generate) ColdFire hardware divide and remainder instructions. If \fB\-march\fR is used without \fB\-mcpu\fR, the default is \*(L"on\*(R" for ColdFire architectures and \*(L"off\*(R" for M680x0 ! architectures. Otherwise, the default is taken from the target \s-1CPU ! \&\s0(either the default \s-1CPU,\s0 or the one specified by \fB\-mcpu\fR). For example, the default is \*(L"off\*(R" for \fB\-mcpu=5206\fR and \*(L"on\*(R" for \&\fB\-mcpu=5206e\fR. .Sp *************** The processor names are: *** 16960,16966 **** \&\fBvr5000\fR, \fBvr5400\fR, \fBvr5500\fR, \&\fBxlr\fR and \fBxlp\fR. The special value \fBfrom-abi\fR selects the ! most compatible architecture for the selected \s-1ABI\s0 (that is, \&\fBmips1\fR for 32\-bit ABIs and \fBmips3\fR for 64\-bit ABIs). .Sp The native Linux/GNU toolchain also supports the value \fBnative\fR, --- 16967,16973 ---- \&\fBvr5000\fR, \fBvr5400\fR, \fBvr5500\fR, \&\fBxlr\fR and \fBxlp\fR. The special value \fBfrom-abi\fR selects the ! most compatible architecture for the selected \s-1ABI \s0(that is, \&\fBmips1\fR for 32\-bit ABIs and \fBmips3\fR for 64\-bit ABIs). .Sp The native Linux/GNU toolchain also supports the value \fBnative\fR, *************** remains the same in that the even-number *** 17123,17130 **** are saved. .Sp Two additional variants of the o32 \s-1ABI\s0 are supported to enable ! a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX\s0 ! (\fB\-mfpxx\fR) and \s-1FP64A\s0 (\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR). The \s-1FPXX\s0 extension mandates that all code must execute correctly when run using 32\-bit or 64\-bit registers. The code can be interlinked with either \s-1FP32\s0 or \s-1FP64,\s0 but not both. --- 17130,17137 ---- are saved. .Sp Two additional variants of the o32 \s-1ABI\s0 are supported to enable ! a transition from 32\-bit to 64\-bit registers. These are \s-1FPXX ! \&\s0(\fB\-mfpxx\fR) and \s-1FP64A \s0(\fB\-mfp64\fR \fB\-mno\-odd\-spreg\fR). The \s-1FPXX\s0 extension mandates that all code must execute correctly when run using 32\-bit or 64\-bit registers. The code can be interlinked with either \s-1FP32\s0 or \s-1FP64,\s0 but not both. *************** operations. This is the default. *** 17257,17264 **** .IX Item "-mno-odd-spreg" .PD Enable the use of odd-numbered single-precision floating-point registers ! for the o32 \s-1ABI.\s0 This is the default for processors that are known to ! support these registers. When using the o32 \s-1FPXX ABI,\s0 \fB\-mno\-odd\-spreg\fR is set by default. .IP "\fB\-mabs=2008\fR" 4 .IX Item "-mabs=2008" --- 17264,17271 ---- .IX Item "-mno-odd-spreg" .PD Enable the use of odd-numbered single-precision floating-point registers ! for the o32 \s-1ABI. \s0 This is the default for processors that are known to ! support these registers. When using the o32 \s-1FPXX ABI, \s0\fB\-mno\-odd\-spreg\fR is set by default. .IP "\fB\-mabs=2008\fR" 4 .IX Item "-mabs=2008" *************** configurations; see the installation doc *** 17327,17334 **** .IP "\fB\-mno\-dsp\fR" 4 .IX Item "-mno-dsp" .PD ! Use (do not use) revision 1 of the \s-1MIPS DSP ASE.\s0 ! This option defines the preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines \&\f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 1. .IP "\fB\-mdspr2\fR" 4 --- 17334,17341 ---- .IP "\fB\-mno\-dsp\fR" 4 .IX Item "-mno-dsp" .PD ! Use (do not use) revision 1 of the \s-1MIPS DSP ASE. ! \s0 This option defines the preprocessor macro \f(CW\*(C`_\|_mips_dsp\*(C'\fR. It also defines \&\f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 1. .IP "\fB\-mdspr2\fR" 4 *************** preprocessor macro \f(CW\*(C`_\|_mips_ds *** 17337,17344 **** .IP "\fB\-mno\-dspr2\fR" 4 .IX Item "-mno-dspr2" .PD ! Use (do not use) revision 2 of the \s-1MIPS DSP ASE.\s0 ! This option defines the preprocessor macros \f(CW\*(C`_\|_mips_dsp\*(C'\fR and \f(CW\*(C`_\|_mips_dspr2\*(C'\fR. It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2. .IP "\fB\-msmartmips\fR" 4 --- 17344,17351 ---- .IP "\fB\-mno\-dspr2\fR" 4 .IX Item "-mno-dspr2" .PD ! Use (do not use) revision 2 of the \s-1MIPS DSP ASE. ! \s0 This option defines the preprocessor macros \f(CW\*(C`_\|_mips_dsp\*(C'\fR and \f(CW\*(C`_\|_mips_dspr2\*(C'\fR. It also defines \f(CW\*(C`_\|_mips_dsp_rev\*(C'\fR to 2. .IP "\fB\-msmartmips\fR" 4 *************** hardware floating-point support to be en *** 17372,17378 **** .IP "\fB\-mno\-mips3d\fR" 4 .IX Item "-mno-mips3d" .PD ! Use (do not use) the \s-1MIPS\-3D ASE.\s0 The option \fB\-mips3d\fR implies \fB\-mpaired\-single\fR. .IP "\fB\-mmicromips\fR" 4 .IX Item "-mmicromips" --- 17379,17385 ---- .IP "\fB\-mno\-mips3d\fR" 4 .IX Item "-mno-mips3d" .PD ! Use (do not use) the \s-1MIPS\-3D ASE. \s0 The option \fB\-mips3d\fR implies \fB\-mpaired\-single\fR. .IP "\fB\-mmicromips\fR" 4 .IX Item "-mmicromips" *************** determined. *** 17429,17435 **** Force \f(CW\*(C`long\*(C'\fR, \f(CW\*(C`int\*(C'\fR, and pointer types to be 32 bits wide. .Sp The default size of \f(CW\*(C`int\*(C'\fRs, \f(CW\*(C`long\*(C'\fRs and pointers depends on ! the \s-1ABI.\s0 All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0 uses 64\-bit \f(CW\*(C`long\*(C'\fRs, as does the 64\-bit \s-1EABI\s0; the others use 32\-bit \f(CW\*(C`long\*(C'\fRs. Pointers are the same size as \f(CW\*(C`long\*(C'\fRs, or the same size as integer registers, whichever is smaller. --- 17436,17442 ---- Force \f(CW\*(C`long\*(C'\fR, \f(CW\*(C`int\*(C'\fR, and pointer types to be 32 bits wide. .Sp The default size of \f(CW\*(C`int\*(C'\fRs, \f(CW\*(C`long\*(C'\fRs and pointers depends on ! the \s-1ABI. \s0 All the supported ABIs use 32\-bit \f(CW\*(C`int\*(C'\fRs. The n64 \s-1ABI\s0 uses 64\-bit \f(CW\*(C`long\*(C'\fRs, as does the 64\-bit \s-1EABI\s0; the others use 32\-bit \f(CW\*(C`long\*(C'\fRs. Pointers are the same size as \f(CW\*(C`long\*(C'\fRs, or the same size as integer registers, whichever is smaller. *************** or the same size as integer registers, w *** 17440,17446 **** .IX Item "-mno-sym32" .PD Assume (do not assume) that all symbols have 32\-bit values, regardless ! of the selected \s-1ABI.\s0 This option is useful in combination with \&\fB\-mabi=64\fR and \fB\-mno\-abicalls\fR because it allows \s-1GCC\s0 to generate shorter and faster references to symbolic addresses. .IP "\fB\-G\fR \fInum\fR" 4 --- 17447,17453 ---- .IX Item "-mno-sym32" .PD Assume (do not assume) that all symbols have 32\-bit values, regardless ! of the selected \s-1ABI. \s0 This option is useful in combination with \&\fB\-mabi=64\fR and \fB\-mno\-abicalls\fR because it allows \s-1GCC\s0 to generate shorter and faster references to symbolic addresses. .IP "\fB\-G\fR \fInum\fR" 4 *************** otherwise. *** 17729,17735 **** .IP "\fB\-mno\-fix\-rm7000\fR" 4 .IX Item "-mno-fix-rm7000" .PD ! Work around the \s-1RM7000\s0 \f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC.\s0 .IP "\fB\-mfix\-vr4120\fR" 4 .IX Item "-mfix-vr4120" --- 17736,17742 ---- .IP "\fB\-mno\-fix\-rm7000\fR" 4 .IX Item "-mno-fix-rm7000" .PD ! Work around the \s-1RM7000 \s0\f(CW\*(C`dmult\*(C'\fR/\f(CW\*(C`dmultu\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC.\s0 .IP "\fB\-mfix\-vr4120\fR" 4 .IX Item "-mfix-vr4120" *************** instructions. These errata are handled *** 17756,17765 **** .RE .IP "\fB\-mfix\-vr4130\fR" 4 .IX Item "-mfix-vr4130" ! Work around the \s-1VR4130\s0 \f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC,\s0 although \s-1GCC\s0 avoids using \f(CW\*(C`mflo\*(C'\fR and \f(CW\*(C`mfhi\*(C'\fR if the ! \&\s-1VR4130\s0 \f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR instructions are available instead. .IP "\fB\-mfix\-sb1\fR" 4 .IX Item "-mfix-sb1" --- 17763,17772 ---- .RE .IP "\fB\-mfix\-vr4130\fR" 4 .IX Item "-mfix-vr4130" ! Work around the \s-1VR4130 \s0\f(CW\*(C`mflo\*(C'\fR/\f(CW\*(C`mfhi\*(C'\fR errata. The workarounds are implemented by the assembler rather than by \s-1GCC,\s0 although \s-1GCC\s0 avoids using \f(CW\*(C`mflo\*(C'\fR and \f(CW\*(C`mfhi\*(C'\fR if the ! \&\s-1VR4130 \s0\f(CW\*(C`macc\*(C'\fR, \f(CW\*(C`macchi\*(C'\fR, \f(CW\*(C`dmacc\*(C'\fR and \f(CW\*(C`dmacchi\*(C'\fR instructions are available instead. .IP "\fB\-mfix\-sb1\fR" 4 .IX Item "-mfix-sb1" *************** The default is \fB\-mno\-mcount\-ra\-add *** 17986,17992 **** .IP "\fB\-mno\-frame\-header\-opt\fR" 4 .IX Item "-mno-frame-header-opt" .PD ! Enable (disable) frame header optimization in the o32 \s-1ABI.\s0 When using the o32 \s-1ABI,\s0 calling functions will allocate 16 bytes on the stack for the called function to write out register arguments. When enabled, this optimization will suppress the allocation of the frame header if it can be determined that --- 17993,17999 ---- .IP "\fB\-mno\-frame\-header\-opt\fR" 4 .IX Item "-mno-frame-header-opt" .PD ! Enable (disable) frame header optimization in the o32 \s-1ABI. \s0 When using the o32 \s-1ABI,\s0 calling functions will allocate 16 bytes on the stack for the called function to write out register arguments. When enabled, this optimization will suppress the allocation of the frame header if it can be determined that *************** header file. *** 18191,18197 **** The option also sets the \s-1ISA\s0 to use. If the \s-1MCU\s0 name is one that is known to only support the 430 \s-1ISA\s0 then that is selected, otherwise the 430X \s-1ISA\s0 is selected. A generic \s-1MCU\s0 name of \fBmsp430\fR can also be ! used to select the 430 \s-1ISA.\s0 Similarly the generic \fBmsp430x\fR \s-1MCU\s0 name selects the 430X \s-1ISA.\s0 .Sp In addition an MCU-specific linker script is added to the linker --- 18198,18204 ---- The option also sets the \s-1ISA\s0 to use. If the \s-1MCU\s0 name is one that is known to only support the 430 \s-1ISA\s0 then that is selected, otherwise the 430X \s-1ISA\s0 is selected. A generic \s-1MCU\s0 name of \fBmsp430\fR can also be ! used to select the 430 \s-1ISA. \s0 Similarly the generic \fBmsp430x\fR \s-1MCU\s0 name selects the 430X \s-1ISA.\s0 .Sp In addition an MCU-specific linker script is added to the linker *************** and not emit \f(CW\*(C`div\*(C'\fR and \ *** 18493,18500 **** .IP "\fB\-mno\-cdx\fR" 4 .IX Item "-mno-cdx" .PD ! Enable or disable generation of Nios \s-1II R2 BMX\s0 (bit manipulation) and ! \&\s-1CDX\s0 (code density) instructions. Enabling these instructions also requires \fB\-march=r2\fR. Since these instructions are optional extensions to the R2 architecture, the default is not to emit them. .IP "\fB\-mcustom\-\fR\fIinsn\fR\fB=\fR\fIN\fR" 4 --- 18500,18507 ---- .IP "\fB\-mno\-cdx\fR" 4 .IX Item "-mno-cdx" .PD ! Enable or disable generation of Nios \s-1II R2 BMX \s0(bit manipulation) and ! \&\s-1CDX \s0(code density) instructions. Enabling these instructions also requires \fB\-march=r2\fR. Since these instructions are optional extensions to the R2 architecture, the default is not to emit them. .IP "\fB\-mcustom\-\fR\fIinsn\fR\fB=\fR\fIN\fR" 4 *************** function attribute *** 18671,18680 **** or pragma. .PP These additional \fB\-m\fR options are available for the Altera Nios \s-1II ! ELF\s0 (bare-metal) target: .IP "\fB\-mhal\fR" 4 .IX Item "-mhal" ! Link with \s-1HAL BSP.\s0 This suppresses linking with the GCC-provided C runtime startup and termination code, and is typically used in conjunction with \&\fB\-msys\-crt0=\fR to specify the location of the alternate startup code provided by the \s-1HAL BSP.\s0 --- 18678,18687 ---- or pragma. .PP These additional \fB\-m\fR options are available for the Altera Nios \s-1II ! ELF \s0(bare-metal) target: .IP "\fB\-mhal\fR" 4 .IX Item "-mhal" ! Link with \s-1HAL BSP. \s0 This suppresses linking with the GCC-provided C runtime startup and termination code, and is typically used in conjunction with \&\fB\-msys\-crt0=\fR to specify the location of the alternate startup code provided by the \s-1HAL BSP.\s0 *************** Return floating-point results in memory. *** 18735,18741 **** Generate code for a \s-1PDP\-11/40.\s0 .IP "\fB\-m45\fR" 4 .IX Item "-m45" ! Generate code for a \s-1PDP\-11/45.\s0 This is the default. .IP "\fB\-m10\fR" 4 .IX Item "-m10" Generate code for a \s-1PDP\-11/10.\s0 --- 18742,18748 ---- Generate code for a \s-1PDP\-11/40.\s0 .IP "\fB\-m45\fR" 4 .IX Item "-m45" ! Generate code for a \s-1PDP\-11/45. \s0 This is the default. .IP "\fB\-m10\fR" 4 .IX Item "-m10" Generate code for a \s-1PDP\-11/10.\s0 *************** work properly on all types of \s-1AE.\s0 *** 18815,18821 **** \&\fB\-mae=MUL\fR selects a \s-1MUL AE\s0 type. This is the most useful \s-1AE\s0 type for compiled code, and is the default. .Sp ! \&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC AE.\s0 Code compiled with this option may suffer from poor performance of byte (char) manipulation, since the \s-1DSP AE\s0 does not provide hardware support for byte load/stores. .IP "\fB\-msymbol\-as\-address\fR" 4 --- 18822,18828 ---- \&\fB\-mae=MUL\fR selects a \s-1MUL AE\s0 type. This is the most useful \s-1AE\s0 type for compiled code, and is the default. .Sp ! \&\fB\-mae=MAC\fR selects a DSP-style \s-1MAC AE. \s0 Code compiled with this option may suffer from poor performance of byte (char) manipulation, since the \s-1DSP AE\s0 does not provide hardware support for byte load/stores. .IP "\fB\-msymbol\-as\-address\fR" 4 *************** Specifies the type of hardware multiplic *** 18865,18873 **** be used. The simplest is \f(CW\*(C`none\*(C'\fR, which uses software for both multiplication and division. This is the default. The \f(CW\*(C`g13\*(C'\fR value is for the hardware multiply/divide peripheral found on the ! \&\s-1RL78/G13\s0 (S2 core) targets. The \f(CW\*(C`g14\*(C'\fR value selects the use of ! the multiplication and division instructions supported by the \s-1RL78/G14\s0 ! (S3 core) parts. The value \f(CW\*(C`rl78\*(C'\fR is an alias for \f(CW\*(C`g14\*(C'\fR and the value \f(CW\*(C`mg10\*(C'\fR is an alias for \f(CW\*(C`none\*(C'\fR. .Sp In addition a C preprocessor macro is defined, based upon the setting --- 18872,18880 ---- be used. The simplest is \f(CW\*(C`none\*(C'\fR, which uses software for both multiplication and division. This is the default. The \f(CW\*(C`g13\*(C'\fR value is for the hardware multiply/divide peripheral found on the ! \&\s-1RL78/G13 \s0(S2 core) targets. The \f(CW\*(C`g14\*(C'\fR value selects the use of ! the multiplication and division instructions supported by the \s-1RL78/G14 ! \&\s0(S3 core) parts. The value \f(CW\*(C`rl78\*(C'\fR is an alias for \f(CW\*(C`g14\*(C'\fR and the value \f(CW\*(C`mg10\*(C'\fR is an alias for \f(CW\*(C`none\*(C'\fR. .Sp In addition a C preprocessor macro is defined, based upon the setting *************** of this option. Possible values are: \f *** 18884,18890 **** .IX Item "-mcpu=rl78" .PD Specifies the \s-1RL78\s0 core to target. The default is the G14 core, also ! known as an S3 core or just \s-1RL78.\s0 The G13 or S2 core does not have multiply or divide instructions, instead it uses a hardware peripheral for these operations. The G10 or S1 core does not have register banks, so it uses a different calling convention. --- 18891,18897 ---- .IX Item "-mcpu=rl78" .PD Specifies the \s-1RL78\s0 core to target. The default is the G14 core, also ! known as an S3 core or just \s-1RL78. \s0 The G13 or S2 core does not have multiply or divide instructions, instead it uses a hardware peripheral for these operations. The G10 or S1 core does not have register banks, so it uses a different calling convention. *************** These \fB\-m\fR options are defined for *** 18984,18990 **** .PD You use these options to specify which instructions are available on the processor you are using. The default value of these options is ! determined when configuring \s-1GCC.\s0 Specifying the \&\fB\-mcpu=\fR\fIcpu_type\fR overrides the specification of these options. We recommend you use the \fB\-mcpu=\fR\fIcpu_type\fR option rather than the options listed above. --- 18991,18997 ---- .PD You use these options to specify which instructions are available on the processor you are using. The default value of these options is ! determined when configuring \s-1GCC. \s0 Specifying the \&\fB\-mcpu=\fR\fIcpu_type\fR overrides the specification of these options. We recommend you use the \fB\-mcpu=\fR\fIcpu_type\fR option rather than the options listed above. *************** following options: *** 19059,19066 **** \&\-mpowerpc\-gpopt \-mpowerpc\-gfxopt \-msingle\-float \-mdouble\-float \&\-msimple\-fpu \-mstring \-mmulhw \-mdlmzb \-mmfpgpr \-mvsx \&\-mcrypto \-mdirect\-move \-mhtm \-mpower8\-fusion \-mpower8\-vector ! \&\-mquad\-memory \-mquad\-memory\-atomic \-mmodulo \-mfloat128 \-mfloat128\-hardware ! \&\-mpower9\-fusion \-mpower9\-vector \-mpower9\-dform\fR .Sp The particular options set for any particular \s-1CPU\s0 varies between compiler versions, depending on what setting seems to produce optimal --- 19066,19072 ---- \&\-mpowerpc\-gpopt \-mpowerpc\-gfxopt \-msingle\-float \-mdouble\-float \&\-msimple\-fpu \-mstring \-mmulhw \-mdlmzb \-mmfpgpr \-mvsx \&\-mcrypto \-mdirect\-move \-mhtm \-mpower8\-fusion \-mpower8\-vector ! \&\-mquad\-memory \-mquad\-memory\-atomic \-mfloat128 \-mfloat128\-hardware\fR .Sp The particular options set for any particular \s-1CPU\s0 varies between compiler versions, depending on what setting seems to produce optimal *************** This is a PowerPC *** 19160,19166 **** 32\-bit \s-1SYSV ABI\s0 option. .IP "\fB\-mbss\-plt\fR" 4 .IX Item "-mbss-plt" ! Generate code that uses a \s-1BSS\s0 \f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR fills in, and requires \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR sections that are both writable and executable. --- 19166,19172 ---- 32\-bit \s-1SYSV ABI\s0 option. .IP "\fB\-mbss\-plt\fR" 4 .IX Item "-mbss-plt" ! Generate code that uses a \s-1BSS \s0\f(CW\*(C`.plt\*(C'\fR section that \fBld.so\fR fills in, and requires \f(CW\*(C`.plt\*(C'\fR and \f(CW\*(C`.got\*(C'\fR sections that are both writable and executable. *************** later processors. *** 19253,19259 **** .IX Item "-mno-power8-vector" .PD Generate code that uses (does not use) the vector and scalar ! instructions that were added in version 2.07 of the PowerPC \s-1ISA.\s0 Also enable the use of built-in functions that allow more direct access to the vector instructions. .IP "\fB\-mquad\-memory\fR" 4 --- 19259,19265 ---- .IX Item "-mno-power8-vector" .PD Generate code that uses (does not use) the vector and scalar ! instructions that were added in version 2.07 of the PowerPC \s-1ISA. \s0 Also enable the use of built-in functions that allow more direct access to the vector instructions. .IP "\fB\-mquad\-memory\fR" 4 *************** instructions. The \fB\-mquad\-memory\-a *** 19283,19289 **** Generate code that uses (does not use) the scalar double precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.06 of the ! PowerPC \s-1ISA.\s0 \fB\-mupper\-regs\-df\fR is turned on by default if you use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or \&\fB\-mvsx\fR options. .IP "\fB\-mupper\-regs\-sf\fR" 4 --- 19289,19295 ---- Generate code that uses (does not use) the scalar double precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.06 of the ! PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-df\fR is turned on by default if you use any of the \fB\-mcpu=power7\fR, \fB\-mcpu=power8\fR, or \&\fB\-mvsx\fR options. .IP "\fB\-mupper\-regs\-sf\fR" 4 *************** use any of the \fB\-mcpu=power7\fR, \fB\ *** 19295,19303 **** Generate code that uses (does not use) the scalar single precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the ! PowerPC \s-1ISA.\s0 \fB\-mupper\-regs\-sf\fR is turned on by default if you ! use either of the \fB\-mcpu=power8\fR or \fB\-mpower8\-vector\fR ! options. .IP "\fB\-mupper\-regs\fR" 4 .IX Item "-mupper-regs" .PD 0 --- 19301,19309 ---- Generate code that uses (does not use) the scalar single precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the ! PowerPC \s-1ISA. \s0\fB\-mupper\-regs\-sf\fR is turned on by default if you ! use either of the \fB\-mcpu=power8\fR, \fB\-mpower8\-vector\fR, or ! \&\fB\-mcpu=power9\fR options. .IP "\fB\-mupper\-regs\fR" 4 .IX Item "-mupper-regs" .PD 0 *************** If you use \fB\-mfloat128\-hardware\fR, *** 19344,19387 **** If you select \s-1ISA 3.0\s0 instructions with \fB\-mcpu=power9\fR, but do not use either \fB\-mfloat128\fR or \fB\-mfloat128\-hardware\fR, the \s-1IEEE\s0 128\-bit floating point support will not be enabled. - .IP "\fB\-mmodulo\fR" 4 - .IX Item "-mmodulo" - .PD 0 - .IP "\fB\-mno\-modulo\fR" 4 - .IX Item "-mno-modulo" - .PD - Generate code that uses (does not use) the \s-1ISA 3.0\s0 integer modulo - instructions. The \fB\-mmodulo\fR option is enabled by default - with the \fB\-mcpu=power9\fR option. - .IP "\fB\-mpower9\-fusion\fR" 4 - .IX Item "-mpower9-fusion" - .PD 0 - .IP "\fB\-mno\-power9\-fusion\fR" 4 - .IX Item "-mno-power9-fusion" - .PD - Generate code that keeps (does not keeps) some operations adjacent so - that the instructions can be fused together on power9 and later - processors. - .IP "\fB\-mpower9\-vector\fR" 4 - .IX Item "-mpower9-vector" - .PD 0 - .IP "\fB\-mno\-power9\-vector\fR" 4 - .IX Item "-mno-power9-vector" - .PD - Generate code that uses (does not use) the vector and scalar - instructions that were added in version 3.0 of the PowerPC \s-1ISA.\s0 Also - enable the use of built-in functions that allow more direct access to - the vector instructions. - .IP "\fB\-mpower9\-dform\fR" 4 - .IX Item "-mpower9-dform" - .PD 0 - .IP "\fB\-mno\-power9\-dform\fR" 4 - .IX Item "-mno-power9-dform" - .PD - Enable (disable) scalar d\-form (register + offset) memory instructions - to load/store traditional Altivec registers. If the \fI\s-1LRA\s0\fR register - allocator is enabled, also enable (disable) vector d\-form memory - instructions. .IP "\fB\-mfloat\-gprs=\fR\fIyes/single/double/no\fR" 4 .IX Item "-mfloat-gprs=yes/single/double/no" .PD 0 --- 19350,19355 ---- *************** pointer to 64 bits, and generates code f *** 19424,19434 **** .IP "\fB\-mminimal\-toc\fR" 4 .IX Item "-mminimal-toc" .PD ! Modify generation of the \s-1TOC\s0 (Table Of Contents), which is created for every executable file. The \fB\-mfull\-toc\fR option is selected by default. In that case, \s-1GCC\s0 allocates at least one \s-1TOC\s0 entry for each unique non-automatic variable reference in your program. \s-1GCC\s0 ! also places floating-point constants in the \s-1TOC.\s0 However, only 16,384 entries are available in the \s-1TOC.\s0 .Sp If you receive a linker error message that saying you have overflowed --- 19392,19402 ---- .IP "\fB\-mminimal\-toc\fR" 4 .IX Item "-mminimal-toc" .PD ! Modify generation of the \s-1TOC \s0(Table Of Contents), which is created for every executable file. The \fB\-mfull\-toc\fR option is selected by default. In that case, \s-1GCC\s0 allocates at least one \s-1TOC\s0 entry for each unique non-automatic variable reference in your program. \s-1GCC\s0 ! also places floating-point constants in the \s-1TOC. \s0 However, only 16,384 entries are available in the \s-1TOC.\s0 .Sp If you receive a linker error message that saying you have overflowed *************** with the \fB\-mno\-fp\-in\-toc\fR and \f *** 19437,19443 **** \&\fB\-mno\-fp\-in\-toc\fR prevents \s-1GCC\s0 from putting floating-point constants in the \s-1TOC\s0 and \fB\-mno\-sum\-in\-toc\fR forces \s-1GCC\s0 to generate code to calculate the sum of an address and a constant at ! run time instead of putting that sum into the \s-1TOC.\s0 You may specify one or both of these options. Each causes \s-1GCC\s0 to produce very slightly slower and larger code at the expense of conserving \s-1TOC\s0 space. .Sp --- 19405,19411 ---- \&\fB\-mno\-fp\-in\-toc\fR prevents \s-1GCC\s0 from putting floating-point constants in the \s-1TOC\s0 and \fB\-mno\-sum\-in\-toc\fR forces \s-1GCC\s0 to generate code to calculate the sum of an address and a constant at ! run time instead of putting that sum into the \s-1TOC. \s0 You may specify one or both of these options. Each causes \s-1GCC\s0 to produce very slightly slower and larger code at the expense of conserving \s-1TOC\s0 space. .Sp *************** implies \fB\-mno\-powerpc64\fR. \s-1GCC *** 19465,19471 **** .IX Item "-mno-xl-compat" .PD Produce code that conforms more closely to \s-1IBM XL\s0 compiler semantics ! when using AIX-compatible \s-1ABI.\s0 Pass floating-point arguments to prototyped functions beyond the register save area (\s-1RSA\s0) on the stack in addition to argument FPRs. Do not assume that most significant double in 128\-bit long double value is properly rounded when comparing --- 19433,19439 ---- .IX Item "-mno-xl-compat" .PD Produce code that conforms more closely to \s-1IBM XL\s0 compiler semantics ! when using AIX-compatible \s-1ABI. \s0 Pass floating-point arguments to prototyped functions beyond the register save area (\s-1RSA\s0) on the stack in addition to argument FPRs. Do not assume that most significant double in 128\-bit long double value is properly rounded when comparing *************** On Darwin/PPC systems, \f(CW\*(C`#pragma *** 19991,19997 **** callee, L42\*(C'\fR, plus a \fIbranch island\fR (glue code). The two target addresses represent the callee and the branch island. The Darwin/PPC linker prefers the first address and generates a \f(CW\*(C`bl ! callee\*(C'\fR if the \s-1PPC\s0 \f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly; otherwise, the linker generates \f(CW\*(C`bl L42\*(C'\fR to call the branch island. The branch island is appended to the body of the calling function; it computes the full 32\-bit address of the callee --- 19959,19965 ---- callee, L42\*(C'\fR, plus a \fIbranch island\fR (glue code). The two target addresses represent the callee and the branch island. The Darwin/PPC linker prefers the first address and generates a \f(CW\*(C`bl ! callee\*(C'\fR if the \s-1PPC \s0\f(CW\*(C`bl\*(C'\fR instruction reaches the callee directly; otherwise, the linker generates \f(CW\*(C`bl L42\*(C'\fR to call the branch island. The branch island is appended to the body of the calling function; it computes the full 32\-bit address of the callee *************** which handle the double-precision recipr *** 20087,20093 **** .PD Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ! \&\s-1ABI.\s0 Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or \&\fB\-mcpu=power8\fR automatically selects \fB\-mrecip\-precision\fR. The double-precision square root estimate instructions are not generated by default on low-precision machines, since they do not provide an --- 20055,20061 ---- .PD Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ! \&\s-1ABI. \s0 Selecting \fB\-mcpu=power6\fR, \fB\-mcpu=power7\fR or \&\fB\-mcpu=power8\fR automatically selects \fB\-mrecip\-precision\fR. The double-precision square root estimate instructions are not generated by default on low-precision machines, since they do not provide an *************** Generate (do not generate) code to pass *** 20162,20171 **** maximum alignment of 64 bits, for compatibility with older versions of \s-1GCC.\s0 .Sp ! Older versions of \s-1GCC\s0 (prior to 4.9.0) incorrectly did not align a structure parameter on a 128\-bit boundary when that structure contained a member requiring 128\-bit alignment. This is corrected in more ! recent versions of \s-1GCC.\s0 This option may be used to generate code that is compatible with functions compiled with older versions of \&\s-1GCC.\s0 .Sp --- 20130,20139 ---- maximum alignment of 64 bits, for compatibility with older versions of \s-1GCC.\s0 .Sp ! Older versions of \s-1GCC \s0(prior to 4.9.0) incorrectly did not align a structure parameter on a 128\-bit boundary when that structure contained a member requiring 128\-bit alignment. This is corrected in more ! recent versions of \s-1GCC. \s0 This option may be used to generate code that is compatible with functions compiled with older versions of \&\s-1GCC.\s0 .Sp *************** This is because the \s-1RX FPU\s0 instru *** 20207,20213 **** .IX Item "-mcpu=name" Selects the type of \s-1RX CPU\s0 to be targeted. Currently three types are supported, the generic \fB\s-1RX600\s0\fR and \fB\s-1RX200\s0\fR series hardware and ! the specific \fB\s-1RX610\s0\fR \s-1CPU.\s0 The default is \fB\s-1RX600\s0\fR. .Sp The only difference between \fB\s-1RX600\s0\fR and \fB\s-1RX610\s0\fR is that the \&\fB\s-1RX610\s0\fR does not support the \f(CW\*(C`MVTIPL\*(C'\fR instruction. --- 20175,20181 ---- .IX Item "-mcpu=name" Selects the type of \s-1RX CPU\s0 to be targeted. Currently three types are supported, the generic \fB\s-1RX600\s0\fR and \fB\s-1RX200\s0\fR series hardware and ! the specific \fB\s-1RX610\s0\fR \s-1CPU. \s0 The default is \fB\s-1RX600\s0\fR. .Sp The only difference between \fB\s-1RX600\s0\fR and \fB\s-1RX610\s0\fR is that the \&\fB\s-1RX610\s0\fR does not support the \f(CW\*(C`MVTIPL\*(C'\fR instruction. *************** which does not have this limitation. *** 20485,20492 **** .IX Item "-m31" .PD When \fB\-m31\fR is specified, generate code compliant to the ! GNU/Linux for S/390 \s-1ABI.\s0 When \fB\-m64\fR is specified, generate ! code compliant to the GNU/Linux for zSeries \s-1ABI.\s0 This allows \s-1GCC\s0 in particular to generate 64\-bit instructions. For the \fBs390\fR targets, the default is \fB\-m31\fR, while the \fBs390x\fR targets default to \fB\-m64\fR. --- 20453,20460 ---- .IX Item "-m31" .PD When \fB\-m31\fR is specified, generate code compliant to the ! GNU/Linux for S/390 \s-1ABI. \s0 When \fB\-m64\fR is specified, generate ! code compliant to the GNU/Linux for zSeries \s-1ABI. \s0 This allows \s-1GCC\s0 in particular to generate 64\-bit instructions. For the \fBs390\fR targets, the default is \fB\-m31\fR, while the \fBs390x\fR targets default to \fB\-m64\fR. *************** targets default to \fB\-m64\fR. *** 20499,20505 **** When \fB\-mzarch\fR is specified, generate code using the instructions available on z/Architecture. When \fB\-mesa\fR is specified, generate code using the ! instructions available on \s-1ESA/390.\s0 Note that \fB\-mesa\fR is not possible with \fB\-m64\fR. When generating code compliant to the GNU/Linux for S/390 \s-1ABI,\s0 the default is \fB\-mesa\fR. When generating code compliant --- 20467,20473 ---- When \fB\-mzarch\fR is specified, generate code using the instructions available on z/Architecture. When \fB\-mesa\fR is specified, generate code using the ! instructions available on \s-1ESA/390. \s0 Note that \fB\-mesa\fR is not possible with \fB\-m64\fR. When generating code compliant to the GNU/Linux for S/390 \s-1ABI,\s0 the default is \fB\-mesa\fR. When generating code compliant *************** available with the vector extension faci *** 20526,20532 **** z13 machine generation. This option changes the \s-1ABI\s0 for some vector type values with regard to alignment and calling conventions. In case vector type values are ! being used in an ABI-relevant context a \s-1GAS\s0 \fB.gnu_attribute\fR command will be added to mark the resulting binary with the \s-1ABI\s0 used. \&\fB\-mvx\fR is enabled by default when using \fB\-march=z13\fR. .IP "\fB\-mzvector\fR" 4 --- 20494,20500 ---- z13 machine generation. This option changes the \s-1ABI\s0 for some vector type values with regard to alignment and calling conventions. In case vector type values are ! being used in an ABI-relevant context a \s-1GAS \s0\fB.gnu_attribute\fR command will be added to mark the resulting binary with the \s-1ABI\s0 used. \&\fB\-mvx\fR is enabled by default when using \fB\-march=z13\fR. .IP "\fB\-mzvector\fR" 4 *************** Generate code for \s-1SH4\-300\s0 in suc *** 20770,20779 **** floating-point operations are used. .IP "\fB\-m4\-340\fR" 4 .IX Item "-m4-340" ! Generate code for \s-1SH4\-340\s0 (no \s-1MMU,\s0 no \s-1FPU\s0). .IP "\fB\-m4\-500\fR" 4 .IX Item "-m4-500" ! Generate code for \s-1SH4\-500\s0 (no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the assembler. .IP "\fB\-m4a\-nofpu\fR" 4 .IX Item "-m4a-nofpu" --- 20738,20747 ---- floating-point operations are used. .IP "\fB\-m4\-340\fR" 4 .IX Item "-m4-340" ! Generate code for \s-1SH4\-340 \s0(no \s-1MMU,\s0 no \s-1FPU\s0). .IP "\fB\-m4\-500\fR" 4 .IX Item "-m4-500" ! Generate code for \s-1SH4\-500 \s0(no \s-1FPU\s0). Passes \fB\-isa=sh4\-nofpu\fR to the assembler. .IP "\fB\-m4a\-nofpu\fR" 4 .IX Item "-m4a-nofpu" *************** SH2A\s0 and SHcompact. *** 20966,20979 **** .IX Item "call-fp" Calls a library function that performs the operation in double precision floating point. Division by zero causes a floating-point exception. This is ! the default for SHcompact with \s-1FPU.\s0 Specifying this for targets that do not have a double precision \s-1FPU\s0 defaults to \f(CW\*(C`call\-div1\*(C'\fR. .IP "\fBcall-table\fR" 4 .IX Item "call-table" Calls a library function that uses a lookup table for small divisors and the \f(CW\*(C`div1\*(C'\fR instruction with case distinction for larger divisors. Division by zero calculates an unspecified result and does not trap. This is the default ! for \s-1SH4.\s0 Specifying this for targets that do not have dynamic shift instructions defaults to \f(CW\*(C`call\-div1\*(C'\fR. .RE .RS 4 --- 20934,20947 ---- .IX Item "call-fp" Calls a library function that performs the operation in double precision floating point. Division by zero causes a floating-point exception. This is ! the default for SHcompact with \s-1FPU. \s0 Specifying this for targets that do not have a double precision \s-1FPU\s0 defaults to \f(CW\*(C`call\-div1\*(C'\fR. .IP "\fBcall-table\fR" 4 .IX Item "call-table" Calls a library function that uses a lookup table for small divisors and the \f(CW\*(C`div1\*(C'\fR instruction with case distinction for larger divisors. Division by zero calculates an unspecified result and does not trap. This is the default ! for \s-1SH4. \s0 Specifying this for targets that do not have dynamic shift instructions defaults to \f(CW\*(C`call\-div1\*(C'\fR. .RE .RS 4 *************** is being compiled for. *** 21017,21023 **** Assume (do not assume) that zero displacement conditional branch instructions \&\f(CW\*(C`bt\*(C'\fR and \f(CW\*(C`bf\*(C'\fR are fast. If \fB\-mzdcbranch\fR is specified, the compiler prefers zero displacement branch code sequences. This is ! enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A.\s0 It can be explicitly disabled by specifying \fB\-mno\-zdcbranch\fR. .IP "\fB\-mcbranch\-force\-delay\-slot\fR" 4 .IX Item "-mcbranch-force-delay-slot" --- 20985,20991 ---- Assume (do not assume) that zero displacement conditional branch instructions \&\f(CW\*(C`bt\*(C'\fR and \f(CW\*(C`bf\*(C'\fR are fast. If \fB\-mzdcbranch\fR is specified, the compiler prefers zero displacement branch code sequences. This is ! enabled by default when generating code for \s-1SH4\s0 and \s-1SH4A. \s0 It can be explicitly disabled by specifying \fB\-mno\-zdcbranch\fR. .IP "\fB\-mcbranch\-force\-delay\-slot\fR" 4 .IX Item "-mcbranch-force-delay-slot" *************** mapped to \fB\-ffp\-contract=off\fR. *** 21046,21052 **** Allow or disallow the compiler to emit the \f(CW\*(C`fsca\*(C'\fR instruction for sine and cosine approximations. The option \fB\-mfsca\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR. It is enabled by default ! when generating code for \s-1SH4A.\s0 Using \fB\-mno\-fsca\fR disables sine and cosine approximations even if \fB\-funsafe\-math\-optimizations\fR is in effect. .IP "\fB\-mfsrra\fR" 4 .IX Item "-mfsrra" --- 21014,21020 ---- Allow or disallow the compiler to emit the \f(CW\*(C`fsca\*(C'\fR instruction for sine and cosine approximations. The option \fB\-mfsca\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR. It is enabled by default ! when generating code for \s-1SH4A. \s0 Using \fB\-mno\-fsca\fR disables sine and cosine approximations even if \fB\-funsafe\-math\-optimizations\fR is in effect. .IP "\fB\-mfsrra\fR" 4 .IX Item "-mfsrra" *************** Allow or disallow the compiler to emit t *** 21058,21064 **** reciprocal square root approximations. The option \fB\-mfsrra\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR and \&\fB\-ffinite\-math\-only\fR. It is enabled by default when generating code for ! \&\s-1SH4A.\s0 Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations even if \fB\-funsafe\-math\-optimizations\fR and \fB\-ffinite\-math\-only\fR are in effect. .IP "\fB\-mpretend\-cmove\fR" 4 --- 21026,21032 ---- reciprocal square root approximations. The option \fB\-mfsrra\fR must be used in combination with \fB\-funsafe\-math\-optimizations\fR and \&\fB\-ffinite\-math\-only\fR. It is enabled by default when generating code for ! \&\s-1SH4A. \s0 Using \fB\-mno\-fsrra\fR disables reciprocal square root approximations even if \fB\-funsafe\-math\-optimizations\fR and \fB\-ffinite\-math\-only\fR are in effect. .IP "\fB\-mpretend\-cmove\fR" 4 *************** instructions. *** 21171,21177 **** .IX Item "-msoft-quad-float" Generate output containing library calls for quad-word (long double) floating-point instructions. The functions called are those specified ! in the \s-1SPARC ABI.\s0 This is the default. .Sp As of this writing, there are no \s-1SPARC\s0 implementations that have hardware support for the quad-word floating-point instructions. They all invoke --- 21139,21145 ---- .IX Item "-msoft-quad-float" Generate output containing library calls for quad-word (long double) floating-point instructions. The functions called are those specified ! in the \s-1SPARC ABI. \s0 This is the default. .Sp As of this writing, there are no \s-1SPARC\s0 implementations that have hardware support for the quad-word floating-point instructions. They all invoke *************** should have 8\-byte alignment. This ena *** 21213,21219 **** \&\f(CW\*(C`ldd\*(C'\fR and \f(CW\*(C`std\*(C'\fR instructions for copies in structure assignment, in place of twice as many \f(CW\*(C`ld\*(C'\fR and \f(CW\*(C`st\*(C'\fR pairs. However, the use of this changed alignment directly violates the \s-1SPARC ! ABI.\s0 Thus, it's intended only for use on targets where the developer acknowledges that their resulting code is not directly in line with the rules of the \s-1ABI.\s0 .IP "\fB\-mstd\-struct\-return\fR" 4 --- 21181,21187 ---- \&\f(CW\*(C`ldd\*(C'\fR and \f(CW\*(C`std\*(C'\fR instructions for copies in structure assignment, in place of twice as many \f(CW\*(C`ld\*(C'\fR and \f(CW\*(C`st\*(C'\fR pairs. However, the use of this changed alignment directly violates the \s-1SPARC ! ABI. \s0 Thus, it's intended only for use on targets where the developer acknowledges that their resulting code is not directly in line with the rules of the \s-1ABI.\s0 .IP "\fB\-mstd\-struct\-return\fR" 4 *************** SPARCStation 1, 2, \s-1IPX\s0 etc. *** 21277,21283 **** With \fB\-mcpu=v8\fR, \s-1GCC\s0 generates code for the V8 variant of the \s-1SPARC\s0 architecture. The only difference from V7 code is that the compiler emits the integer multiply and integer divide instructions which exist in \s-1SPARC\-V8\s0 ! but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=supersparc\fR, the compiler additionally optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000 series. .Sp --- 21245,21251 ---- With \fB\-mcpu=v8\fR, \s-1GCC\s0 generates code for the V8 variant of the \s-1SPARC\s0 architecture. The only difference from V7 code is that the compiler emits the integer multiply and integer divide instructions which exist in \s-1SPARC\-V8\s0 ! but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=supersparc\fR, the compiler additionally optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000 series. .Sp *************** With \fB\-mcpu=sparclite\fR, \s-1GCC\s0 *** 21285,21298 **** the \s-1SPARC\s0 architecture. This adds the integer multiply, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=f930\fR, the compiler additionally optimizes it for the ! Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU.\s0 With \&\fB\-mcpu=f934\fR, the compiler additionally optimizes it for the Fujitsu \&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU.\s0 .Sp With \fB\-mcpu=sparclet\fR, \s-1GCC\s0 generates code for the SPARClet variant of the \s-1SPARC\s0 architecture. This adds the integer multiply, multiply/accumulate, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClet ! but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=tsc701\fR, the compiler additionally optimizes it for the \s-1TEMIC\s0 SPARClet chip. .Sp With \fB\-mcpu=v9\fR, \s-1GCC\s0 generates code for the V9 variant of the \s-1SPARC\s0 --- 21253,21266 ---- the \s-1SPARC\s0 architecture. This adds the integer multiply, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClite but not in \s-1SPARC\-V7.\s0 With \fB\-mcpu=f930\fR, the compiler additionally optimizes it for the ! Fujitsu \s-1MB86930\s0 chip, which is the original SPARClite, with no \s-1FPU. \s0 With \&\fB\-mcpu=f934\fR, the compiler additionally optimizes it for the Fujitsu \&\s-1MB86934\s0 chip, which is the more recent SPARClite with \s-1FPU.\s0 .Sp With \fB\-mcpu=sparclet\fR, \s-1GCC\s0 generates code for the SPARClet variant of the \s-1SPARC\s0 architecture. This adds the integer multiply, multiply/accumulate, integer divide step and scan (\f(CW\*(C`ffs\*(C'\fR) instructions which exist in SPARClet ! but not in \s-1SPARC\-V7. \s0 With \fB\-mcpu=tsc701\fR, the compiler additionally optimizes it for the \s-1TEMIC\s0 SPARClet chip. .Sp With \fB\-mcpu=v9\fR, \s-1GCC\s0 generates code for the V9 variant of the \s-1SPARC\s0 *************** GNU/Linux toolchains, \fBnative\fR can a *** 21332,21338 **** .IP "\fB\-mno\-v8plus\fR" 4 .IX Item "-mno-v8plus" .PD ! With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+ ABI.\s0 The difference from the V8 \s-1ABI\s0 is that the global and out registers are considered 64 bits wide. This is enabled by default on Solaris in 32\-bit mode for all \s-1SPARC\-V9\s0 processors. --- 21300,21306 ---- .IP "\fB\-mno\-v8plus\fR" 4 .IX Item "-mno-v8plus" .PD ! With \fB\-mv8plus\fR, \s-1GCC\s0 generates code for the \s-1SPARC\-V8+ ABI. \s0 The difference from the V8 \s-1ABI\s0 is that the global and out registers are considered 64 bits wide. This is enabled by default on Solaris in 32\-bit mode for all \s-1SPARC\-V9\s0 processors. *************** selected because its use is still experi *** 21840,21846 **** .IP "\fB\-mghs\fR" 4 .IX Item "-mghs" .PD ! Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI.\s0 This is the default. With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 --- 21808,21814 ---- .IP "\fB\-mghs\fR" 4 .IX Item "-mghs" .PD ! Enables support for the \s-1RH850\s0 version of the V850 \s-1ABI. \s0 This is the default. With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 *************** When this version of the \s-1ABI\s0 is e *** 21865,21871 **** .RE .IP "\fB\-mgcc\-abi\fR" 4 .IX Item "-mgcc-abi" ! Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI.\s0 With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 --- 21833,21839 ---- .RE .IP "\fB\-mgcc\-abi\fR" 4 .IX Item "-mgcc-abi" ! Enables support for the old \s-1GCC\s0 version of the V850 \s-1ABI. \s0 With this version of the \s-1ABI\s0 the following rules apply: .RS 4 .IP "*" 4 *************** of the selected instruction set. *** 22075,22081 **** Original Intel i386 \s-1CPU.\s0 .IP "\fBi486\fR" 4 .IX Item "i486" ! Intel i486 \s-1CPU.\s0 (No scheduling is implemented for this chip.) .IP "\fBi586\fR" 4 .IX Item "i586" .PD 0 --- 22043,22049 ---- Original Intel i386 \s-1CPU.\s0 .IP "\fBi486\fR" 4 .IX Item "i486" ! Intel i486 \s-1CPU. \s0(No scheduling is implemented for this chip.) .IP "\fBi586\fR" 4 .IX Item "i586" .PD 0 *************** extensions.) *** 22259,22273 **** .IP "\fBbdver3\fR" 4 .IX Item "bdver3" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, XOP, LWP, AES,\s0 ! \&\s-1PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBbdver4\fR" 4 .IX Item "bdver4" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, BMI2, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, AVX2, XOP, LWP,\s0 ! \&\s-1AES, PCL_MUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1,\s0 ! \&\s-1SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBznver1\fR" 4 .IX Item "znver1" \&\s-1AMD\s0 Family 17h core based CPUs with x86\-64 instruction set support. (This --- 22227,22241 ---- .IP "\fBbdver3\fR" 4 .IX Item "bdver3" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, XOP, LWP, AES, ! PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBbdver4\fR" 4 .IX Item "bdver4" \&\s-1AMD\s0 Family 15h core based CPUs with x86\-64 instruction set support. (This ! supersets \s-1BMI, BMI2, TBM, F16C, FMA, FMA4, FSGSBASE, AVX, AVX2, XOP, LWP, ! AES, PCL_MUL, CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, ! SSE4.2, ABM\s0 and 64\-bit instruction set extensions. .IP "\fBznver1\fR" 4 .IX Item "znver1" \&\s-1AMD\s0 Family 17h core based CPUs with x86\-64 instruction set support. (This *************** instruction set support. *** 22299,22305 **** implemented for this chip.) .IP "\fBc3\-2\fR" 4 .IX Item "c3-2" ! \&\s-1VIA C3\-2\s0 (Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support. (No scheduling is implemented for this chip.) .IP "\fBgeode\fR" 4 --- 22267,22273 ---- implemented for this chip.) .IP "\fBc3\-2\fR" 4 .IX Item "c3-2" ! \&\s-1VIA C3\-2 \s0(Nehemiah/C5XL) \s-1CPU\s0 with \s-1MMX\s0 and \s-1SSE\s0 instruction set support. (No scheduling is implemented for this chip.) .IP "\fBgeode\fR" 4 *************** processors) for which the code is optimi *** 22345,22351 **** .IP "\fBintel\fR" 4 .IX Item "intel" Produce code optimized for the most current Intel processors, which are ! Haswell and Silvermont for this version of \s-1GCC.\s0 If you know the \s-1CPU\s0 on which your code will run, then you should use the corresponding \&\fB\-mtune\fR or \fB\-march\fR option instead of \fB\-mtune=intel\fR. But, if you want your application performs better on both Haswell and --- 22313,22319 ---- .IP "\fBintel\fR" 4 .IX Item "intel" Produce code optimized for the most current Intel processors, which are ! Haswell and Silvermont for this version of \s-1GCC. \s0 If you know the \s-1CPU\s0 on which your code will run, then you should use the corresponding \&\fB\-mtune\fR or \fB\-march\fR option instead of \fB\-mtune=intel\fR. But, if you want your application performs better on both Haswell and *************** Do not use the \s-1FPU\s0 registers for *** 22453,22459 **** .Sp The usual calling convention has functions return values of types \&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR in an \s-1FPU\s0 register, even if there ! is no \s-1FPU.\s0 The idea is that the operating system should emulate an \s-1FPU.\s0 .Sp The option \fB\-mno\-fp\-ret\-in\-387\fR causes such values to be returned --- 22421,22427 ---- .Sp The usual calling convention has functions return values of types \&\f(CW\*(C`float\*(C'\fR and \f(CW\*(C`double\*(C'\fR in an \s-1FPU\s0 register, even if there ! is no \s-1FPU. \s0 The idea is that the operating system should emulate an \s-1FPU.\s0 .Sp The option \fB\-mno\-fp\-ret\-in\-387\fR causes such values to be returned *************** external library. Supported values for *** 22935,22941 **** for the Intel short vector math library and \fBacml\fR for the \s-1AMD\s0 math core library. To use this option, both \fB\-ftree\-vectorize\fR and ! \&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML\s0 ABI-compatible library must be specified at link time. .Sp \&\s-1GCC\s0 currently emits calls to \f(CW\*(C`vmldExp2\*(C'\fR, --- 22903,22909 ---- for the Intel short vector math library and \fBacml\fR for the \s-1AMD\s0 math core library. To use this option, both \fB\-ftree\-vectorize\fR and ! \&\fB\-funsafe\-math\-optimizations\fR have to be enabled, and an \s-1SVML\s0 or \s-1ACML \s0 ABI-compatible library must be specified at link time. .Sp \&\s-1GCC\s0 currently emits calls to \f(CW\*(C`vmldExp2\*(C'\fR, *************** when \fB\-mveclibabi=acml\fR is used. *** 22958,22964 **** .IX Item "-mabi=name" Generate code for the specified calling convention. Permissible values are \fBsysv\fR for the \s-1ABI\s0 used on GNU/Linux and other systems, and ! \&\fBms\fR for the Microsoft \s-1ABI.\s0 The default is to use the Microsoft \&\s-1ABI\s0 when targeting Microsoft Windows and the SysV \s-1ABI\s0 on all other systems. You can control this behavior for specific functions by using the function attributes \f(CW\*(C`ms_abi\*(C'\fR and \f(CW\*(C`sysv_abi\*(C'\fR. --- 22926,22932 ---- .IX Item "-mabi=name" Generate code for the specified calling convention. Permissible values are \fBsysv\fR for the \s-1ABI\s0 used on GNU/Linux and other systems, and ! \&\fBms\fR for the Microsoft \s-1ABI. \s0 The default is to use the Microsoft \&\s-1ABI\s0 when targeting Microsoft Windows and the SysV \s-1ABI\s0 on all other systems. You can control this behavior for specific functions by using the function attributes \f(CW\*(C`ms_abi\*(C'\fR and \f(CW\*(C`sysv_abi\*(C'\fR. *************** See the Info entry for \fBgcc\fR, or *** 23772,23778 **** for contributors to \s-1GCC.\s0 .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1988\-2016 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or --- 23740,23746 ---- for contributors to \s-1GCC.\s0 .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1988\-2017 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or diff -Nrcpad gcc-6.3.0/gcc/doc/gcc.info gcc-6.4.0/gcc/doc/gcc.info *** gcc-6.3.0/gcc/doc/gcc.info Wed Dec 21 09:33:55 2016 --- gcc-6.4.0/gcc/doc/gcc.info Tue Jul 4 09:27:45 2017 *************** *** 1,6 **** ! This is gcc.info, produced by makeinfo version 6.1 from gcc.texi. ! Copyright (C) 1988-2016 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 --- 1,7 ---- ! This is doc/gcc.info, produced by makeinfo version 4.13 from ! /space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/doc/gcc.texi. ! Copyright (C) 1988-2017 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 *************** Free Documentation License". *** 16,35 **** (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU software. ! Copies published by the Free Software Foundation raise funds for GNU ! development. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * gcc: (gcc). The GNU Compiler Collection. * g++: (gcc). The GNU C++ compiler. ! * gcov: (gcc) Gcov. 'gcov'--a test coverage program. ! * gcov-tool: (gcc) Gcov-tool. 'gcov-tool'--an offline gcda profile processing program. END-INFO-DIR-ENTRY - This file documents the use of the GNU compilers. ! Copyright (C) 1988-2016 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 --- 17,37 ---- (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. ! INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * gcc: (gcc). The GNU Compiler Collection. * g++: (gcc). The GNU C++ compiler. ! * gcov: (gcc) Gcov. `gcov'--a test coverage program. ! * gcov-tool: (gcc) Gcov-tool. `gcov-tool'--an offline gcda profile processing program. ! * gcov-dump: (gcc) Gcov-dump. `gcov-dump'--an offline gcda and gcno profile dump tool. END-INFO-DIR-ENTRY This file documents the use of the GNU compilers. ! Copyright (C) 1988-2017 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 *************** Free Documentation License". *** 45,53 **** (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU software. ! Copies published by the Free Software Foundation raise funds for GNU ! development.  File: gcc.info, Node: Top, Next: G++ and GCC, Up: (DIR) --- 47,56 ---- (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. !  File: gcc.info, Node: Top, Next: G++ and GCC, Up: (DIR) *************** Introduction *** 57,63 **** This manual documents how to use the GNU compilers, as well as their features and incompatibilities, and how to report bugs. It corresponds ! to the compilers (GCC) version 6.3.0. The internals of the GNU compilers, including how to port them to new targets and some information about how to write front ends for new languages, are documented in a separate manual. *Note Introduction: (gccint)Top. --- 60,66 ---- This manual documents how to use the GNU compilers, as well as their features and incompatibilities, and how to report bugs. It corresponds ! to the compilers (GCC) version 6.4.0. The internals of the GNU compilers, including how to port them to new targets and some information about how to write front ends for new languages, are documented in a separate manual. *Note Introduction: (gccint)Top. *************** documented in a separate manual. *Note *** 66,80 **** * G++ and GCC:: You can compile C or C++ programs. * Standards:: Language standards supported by GCC. ! * Invoking GCC:: Command options supported by 'gcc'. * C Implementation:: How GCC implements the ISO C specification. * C++ Implementation:: How GCC implements the ISO C++ specification. * C Extensions:: GNU extensions to the C language family. * C++ Extensions:: GNU extensions to the C++ language. * Objective-C:: GNU Objective-C runtime features. * Compatibility:: Binary Compatibility ! * Gcov:: 'gcov'--a test coverage program. ! * Gcov-tool:: 'gcov-tool'--an offline gcda profile processing program. * Trouble:: If you have trouble using GCC. * Bugs:: How, why and where to report bugs. * Service:: How To Get Help with GCC --- 69,84 ---- * G++ and GCC:: You can compile C or C++ programs. * Standards:: Language standards supported by GCC. ! * Invoking GCC:: Command options supported by `gcc'. * C Implementation:: How GCC implements the ISO C specification. * C++ Implementation:: How GCC implements the ISO C++ specification. * C Extensions:: GNU extensions to the C language family. * C++ Extensions:: GNU extensions to the C++ language. * Objective-C:: GNU Objective-C runtime features. * Compatibility:: Binary Compatibility ! * Gcov:: `gcov'---a test coverage program. ! * Gcov-tool:: `gcov-tool'---an offline gcda profile processing program. ! * Gcov-dump:: `gcov-dump'---an offline gcda and gcno profile dump tool. * Trouble:: If you have trouble using GCC. * Bugs:: How, why and where to report bugs. * Service:: How To Get Help with GCC *************** documented in a separate manual. *Note *** 92,98 **** * Keyword Index:: Index of concepts and symbol names.  ! File: gcc.info, Node: G++ and GCC, Next: Standards, Up: Top 1 Programming Languages Supported by GCC **************************************** --- 96,102 ---- * Keyword Index:: Index of concepts and symbol names.  ! File: gcc.info, Node: G++ and GCC, Next: Standards, Prev: Top, Up: Top 1 Programming Languages Supported by GCC **************************************** *************** were renumbered and became clauses in th *** 155,163 **** standard, but not the ISO standard, also came with a Rationale document. This standard, in both its forms, is commonly known as "C89", or occasionally as "C90", from the dates of ratification. To select this ! standard in GCC, use one of the options '-ansi', '-std=c90' or ! '-std=iso9899:1990'; to obtain all the diagnostics required by the ! standard, you should also specify '-pedantic' (or '-pedantic-errors' if you want them to be errors rather than warnings). *Note Options Controlling C Dialect: C Dialect Options. --- 159,167 ---- standard, but not the ISO standard, also came with a Rationale document. This standard, in both its forms, is commonly known as "C89", or occasionally as "C90", from the dates of ratification. To select this ! standard in GCC, use one of the options `-ansi', `-std=c90' or ! `-std=iso9899:1990'; to obtain all the diagnostics required by the ! standard, you should also specify `-pedantic' (or `-pedantic-errors' if you want them to be errors rather than warnings). *Note Options Controlling C Dialect: C Dialect Options. *************** Corrigenda published in 1994 and 1996. *** 166,184 **** uncorrected version. An amendment to the 1990 standard was published in 1995. This ! amendment added digraphs and '__STDC_VERSION__' to the language, but otherwise concerned the library. This amendment is commonly known as "AMD1"; the amended standard is sometimes known as "C94" or "C95". To ! select this standard in GCC, use the option '-std=iso9899:199409' (with, ! as for other standard versions, '-pedantic' to receive all required ! diagnostics). A new edition of the ISO C standard was published in 1999 as ISO/IEC 9899:1999, and is commonly known as "C99". (While in development, ! drafts of this standard version were referred to as "C9X".) GCC has substantially complete support for this standard version; see ! for details. To select this ! standard, use '-std=c99' or '-std=iso9899:1999'. Errors in the 1999 ISO C standard were corrected in three Technical Corrigenda published in 2001, 2004 and 2007. GCC does not support the --- 170,188 ---- uncorrected version. An amendment to the 1990 standard was published in 1995. This ! amendment added digraphs and `__STDC_VERSION__' to the language, but otherwise concerned the library. This amendment is commonly known as "AMD1"; the amended standard is sometimes known as "C94" or "C95". To ! select this standard in GCC, use the option `-std=iso9899:199409' ! (with, as for other standard versions, `-pedantic' to receive all ! required diagnostics). A new edition of the ISO C standard was published in 1999 as ISO/IEC 9899:1999, and is commonly known as "C99". (While in development, ! drafts of this standard version were referred to as "C9X".) GCC has substantially complete support for this standard version; see ! `http://gcc.gnu.org/c99status.html' for details. To select this ! standard, use `-std=c99' or `-std=iso9899:1999'. Errors in the 1999 ISO C standard were corrected in three Technical Corrigenda published in 2001, 2004 and 2007. GCC does not support the *************** uncorrected version. *** 186,218 **** A fourth version of the C standard, known as "C11", was published in 2011 as ISO/IEC 9899:2011. (While in development, drafts of this ! standard version were referred to as "C1X".) GCC has substantially ! complete support for this standard, enabled with '-std=c11' or ! '-std=iso9899:2011'. By default, GCC provides some extensions to the C language that, on rare occasions conflict with the C standard. *Note Extensions to the C Language Family: C Extensions. Some features that are part of the C99 standard are accepted as extensions in C90 mode, and some features that are part of the C11 standard are accepted as extensions in C90 and C99 ! modes. Use of the '-std' options listed above disables these extensions ! where they conflict with the C standard version selected. You may also ! select an extended version of the C language explicitly with ! '-std=gnu90' (for C90 with GNU extensions), '-std=gnu99' (for C99 with ! GNU extensions) or '-std=gnu11' (for C11 with GNU extensions). The default, if no C language dialect options are given, is ! '-std=gnu11'. The ISO C standard defines (in clause 4) two classes of conforming ! implementation. A "conforming hosted implementation" supports the whole ! standard including all the library facilities; a "conforming ! freestanding implementation" is only required to provide certain library ! facilities: those in '', '', '', and ! ''; since AMD1, also those in ''; since C99, also ! those in '' and ''; and since C11, also those in ! '' and ''. In addition, complex types, added ! in C99, are not required for freestanding implementations. The standard also defines two environments for programs, a "freestanding environment", required of all implementations and which --- 190,222 ---- A fourth version of the C standard, known as "C11", was published in 2011 as ISO/IEC 9899:2011. (While in development, drafts of this ! standard version were referred to as "C1X".) GCC has substantially ! complete support for this standard, enabled with `-std=c11' or ! `-std=iso9899:2011'. By default, GCC provides some extensions to the C language that, on rare occasions conflict with the C standard. *Note Extensions to the C Language Family: C Extensions. Some features that are part of the C99 standard are accepted as extensions in C90 mode, and some features that are part of the C11 standard are accepted as extensions in C90 and C99 ! modes. Use of the `-std' options listed above disables these ! extensions where they conflict with the C standard version selected. ! You may also select an extended version of the C language explicitly ! with `-std=gnu90' (for C90 with GNU extensions), `-std=gnu99' (for C99 ! with GNU extensions) or `-std=gnu11' (for C11 with GNU extensions). The default, if no C language dialect options are given, is ! `-std=gnu11'. The ISO C standard defines (in clause 4) two classes of conforming ! implementation. A "conforming hosted implementation" supports the ! whole standard including all the library facilities; a "conforming ! freestanding implementation" is only required to provide certain ! library facilities: those in `', `', `', ! and `'; since AMD1, also those in `'; since C99, ! also those in `' and `'; and since C11, also those ! in `' and `'. In addition, complex types, ! added in C99, are not required for freestanding implementations. The standard also defines two environments for programs, a "freestanding environment", required of all implementations and which *************** may not have library facilities beyond t *** 220,238 **** implementations, where the handling of program startup and termination are implementation-defined; and a "hosted environment", which is not required, in which all the library facilities are provided and startup ! is through a function 'int main (void)' or 'int main (int, char *[])'. An OS kernel is an example of a program running in a freestanding ! environment; a program using the facilities of an operating system is an ! example of a program running in a hosted environment. GCC aims towards being usable as a conforming freestanding implementation, or as the compiler for a conforming hosted implementation. By default, it acts as the compiler for a hosted ! implementation, defining '__STDC_HOSTED__' as '1' and presuming that when the names of ISO C functions are used, they have the semantics defined in the standard. To make it act as a conforming freestanding implementation for a freestanding environment, use the option ! '-ffreestanding'; it then defines '__STDC_HOSTED__' to '0' and does not make assumptions about the meanings of function names from the standard library, with exceptions noted below. To build an OS kernel, you may well still need to make your own arrangements for linking and startup. --- 224,242 ---- implementations, where the handling of program startup and termination are implementation-defined; and a "hosted environment", which is not required, in which all the library facilities are provided and startup ! is through a function `int main (void)' or `int main (int, char *[])'. An OS kernel is an example of a program running in a freestanding ! environment; a program using the facilities of an operating system is ! an example of a program running in a hosted environment. GCC aims towards being usable as a conforming freestanding implementation, or as the compiler for a conforming hosted implementation. By default, it acts as the compiler for a hosted ! implementation, defining `__STDC_HOSTED__' as `1' and presuming that when the names of ISO C functions are used, they have the semantics defined in the standard. To make it act as a conforming freestanding implementation for a freestanding environment, use the option ! `-ffreestanding'; it then defines `__STDC_HOSTED__' to `0' and does not make assumptions about the meanings of function names from the standard library, with exceptions noted below. To build an OS kernel, you may well still need to make your own arrangements for linking and startup. *************** well still need to make your own arrange *** 240,258 **** GCC does not provide the library facilities required only of hosted implementations, nor yet all the facilities required by C99 of ! freestanding implementations on all platforms. To use the facilities of ! a hosted environment, you need to find them elsewhere (for example, in ! the GNU C library). *Note Standard Libraries: Standard Libraries. Most of the compiler support routines used by GCC are present in ! 'libgcc', but there are a few exceptions. GCC requires the freestanding ! environment provide 'memcpy', 'memmove', 'memset' and 'memcmp'. ! Finally, if '__builtin_trap' is used, and the target does not implement ! the 'trap' pattern, then GCC emits a call to 'abort'. For references to Technical Corrigenda, Rationale documents and information concerning the history of C that is available online, see ! 2.2 C++ Language ================ --- 244,262 ---- GCC does not provide the library facilities required only of hosted implementations, nor yet all the facilities required by C99 of ! freestanding implementations on all platforms. To use the facilities ! of a hosted environment, you need to find them elsewhere (for example, ! in the GNU C library). *Note Standard Libraries: Standard Libraries. Most of the compiler support routines used by GCC are present in ! `libgcc', but there are a few exceptions. GCC requires the ! freestanding environment provide `memcpy', `memmove', `memset' and ! `memcmp'. Finally, if `__builtin_trap' is used, and the target does ! not implement the `trap' pattern, then GCC emits a call to `abort'. For references to Technical Corrigenda, Rationale documents and information concerning the history of C that is available online, see ! `http://gcc.gnu.org/readings.html' 2.2 C++ Language ================ *************** GCC supports the original ISO C++ standa *** 262,377 **** The original ISO C++ standard was published as the ISO standard (ISO/IEC 14882:1998) and amended by a Technical Corrigenda published in ! 2003 (ISO/IEC 14882:2003). These standards are referred to as C++98 and ! C++03, respectively. GCC implements the majority of C++98 ('export' is a notable exception) and most of the changes in C++03. To select this ! standard in GCC, use one of the options '-ansi', '-std=c++98', or ! '-std=c++03'; to obtain all the diagnostics required by the standard, ! you should also specify '-pedantic' (or '-pedantic-errors' if you want them to be errors rather than warnings). ! A revised ISO C++ standard was published in 2011 as ISO/IEC 14882:2011, ! and is referred to as C++11; before its publication it was commonly ! referred to as C++0x. C++11 contains several changes to the C++ ! language, all of which have been implemented in GCC. For details see ! . To select this standard in ! GCC, use the option '-std=c++11'. Another revised ISO C++ standard was published in 2014 as ISO/IEC 14882:2014, and is referred to as C++14; before its publication it was sometimes referred to as C++1y. C++14 contains several further changes to the C++ language, all of which have been implemented in GCC. For ! details see . To select this ! standard in GCC, use the option '-std=c++14'. GCC also supports the C++ Concepts Technical Specification, ISO/IEC TS 19217:2015, which allows constraints to be defined for templates, allowing template arguments to be checked and for templates to be ! overloaded or specialized based on the constraints. Support for C++ Concepts is included in an experimental C++1z mode that corresponds to the next revision of the ISO C++ standard, expected to be published in ! 2017. To enable C++1z support in GCC, use the option '-std=c++17' or ! '-std=c++1z'. More information about the C++ standards is available on the ISO C++ ! committee's web site at . To obtain all the diagnostics required by any of the standard versions ! described above you should specify '-pedantic' or '-pedantic-errors', ! otherwise GCC will allow some non-ISO C++ features as extensions. *Note Warning Options::. By default, GCC also provides some additional extensions to the C++ language that on rare occasions conflict with the C++ standard. *Note ! Options Controlling C++ Dialect: C++ Dialect Options. Use of the '-std' ! options listed above disables these extensions where they they conflict ! with the C++ standard version selected. You may also select an extended ! version of the C++ language explicitly with '-std=gnu++98' (for C++98 ! with GNU extensions), or '-std=gnu++11' (for C++11 with GNU extensions), ! or '-std=gnu++14' (for C++14 with GNU extensions), or '-std=gnu++1z' ! (for C++1z with GNU extensions). The default, if no C++ language dialect options are given, is ! '-std=gnu++14'. 2.3 Objective-C and Objective-C++ Languages =========================================== ! GCC supports "traditional" Objective-C (also known as "Objective-C 1.0") ! and contains support for the Objective-C exception and synchronization ! syntax. It has also support for a number of "Objective-C 2.0" language ! extensions, including properties, fast enumeration (only for ! Objective-C), method attributes and the @optional and @required keywords ! in protocols. GCC supports Objective-C++ and features available in ! Objective-C are also available in Objective-C++. GCC by default uses the GNU Objective-C runtime library, which is part ! of GCC and is not the same as the Apple/NeXT Objective-C runtime library ! used on Apple systems. There are a number of differences documented in ! this manual. The options '-fgnu-runtime' and '-fnext-runtime' allow you ! to switch between producing output that works with the GNU Objective-C ! runtime library and output that works with the Apple/NeXT Objective-C ! runtime library. There is no formal written standard for Objective-C or Objective-C++. The authoritative manual on traditional Objective-C (1.0) is "Object-Oriented Programming and the Objective-C Language": ! * is the original NeXTstep document; ! * is the same document in another format. The Objective-C exception and synchronization syntax (that is, the ! keywords '@try', '@throw', '@catch', '@finally' and '@synchronized') is ! supported by GCC and is enabled with the option '-fobjc-exceptions'. The syntax is briefly documented in this manual and in the Objective-C 2.0 manuals from Apple. The Objective-C 2.0 language extensions and features are automatically ! enabled; they include properties (via the '@property', '@synthesize' and ! '@dynamic keywords'), fast enumeration (not available in Objective-C++), ! attributes for methods (such as 'deprecated', 'noreturn', 'sentinel', ! 'format'), the 'unused' attribute for method arguments, the '@package' ! keyword for instance variables and the '@optional' and '@required' ! keywords in protocols. You can disable all these Objective-C 2.0 ! language extensions with the option '-fobjc-std=objc1', which causes the ! compiler to recognize the same Objective-C language syntax recognized by ! GCC 4.0, and to produce an error if one of the new features is used. GCC has currently no support for non-fragile instance variables. The authoritative manual on Objective-C 2.0 is available from Apple: ! * ! For more information concerning the history of Objective-C that is ! available online, see 2.4 Go Language =============== As of the GCC 4.7.1 release, GCC supports the Go 1 language standard, ! described at . 2.5 References for Other Languages ================================== --- 266,383 ---- The original ISO C++ standard was published as the ISO standard (ISO/IEC 14882:1998) and amended by a Technical Corrigenda published in ! 2003 (ISO/IEC 14882:2003). These standards are referred to as C++98 and ! C++03, respectively. GCC implements the majority of C++98 (`export' is a notable exception) and most of the changes in C++03. To select this ! standard in GCC, use one of the options `-ansi', `-std=c++98', or ! `-std=c++03'; to obtain all the diagnostics required by the standard, ! you should also specify `-pedantic' (or `-pedantic-errors' if you want them to be errors rather than warnings). ! A revised ISO C++ standard was published in 2011 as ISO/IEC ! 14882:2011, and is referred to as C++11; before its publication it was ! commonly referred to as C++0x. C++11 contains several changes to the ! C++ language, all of which have been implemented in GCC. For details ! see `https://gcc.gnu.org/projects/cxx0x.html'. To select this standard ! in GCC, use the option `-std=c++11'. Another revised ISO C++ standard was published in 2014 as ISO/IEC 14882:2014, and is referred to as C++14; before its publication it was sometimes referred to as C++1y. C++14 contains several further changes to the C++ language, all of which have been implemented in GCC. For ! details see `https://gcc.gnu.org/projects/cxx1y.html'. To select this ! standard in GCC, use the option `-std=c++14'. GCC also supports the C++ Concepts Technical Specification, ISO/IEC TS 19217:2015, which allows constraints to be defined for templates, allowing template arguments to be checked and for templates to be ! overloaded or specialized based on the constraints. Support for C++ Concepts is included in an experimental C++1z mode that corresponds to the next revision of the ISO C++ standard, expected to be published in ! 2017. To enable C++1z support in GCC, use the option `-std=c++17' or ! `-std=c++1z'. More information about the C++ standards is available on the ISO C++ ! committee's web site at `http://www.open-std.org/jtc1/sc22/wg21/'. To obtain all the diagnostics required by any of the standard versions ! described above you should specify `-pedantic' or `-pedantic-errors', ! otherwise GCC will allow some non-ISO C++ features as extensions. *Note Warning Options::. By default, GCC also provides some additional extensions to the C++ language that on rare occasions conflict with the C++ standard. *Note ! Options Controlling C++ Dialect: C++ Dialect Options. Use of the ! `-std' options listed above disables these extensions where they they ! conflict with the C++ standard version selected. You may also select ! an extended version of the C++ language explicitly with `-std=gnu++98' ! (for C++98 with GNU extensions), or `-std=gnu++11' (for C++11 with GNU ! extensions), or `-std=gnu++14' (for C++14 with GNU extensions), or ! `-std=gnu++1z' (for C++1z with GNU extensions). The default, if no C++ language dialect options are given, is ! `-std=gnu++14'. 2.3 Objective-C and Objective-C++ Languages =========================================== ! GCC supports "traditional" Objective-C (also known as "Objective-C ! 1.0") and contains support for the Objective-C exception and ! synchronization syntax. It has also support for a number of ! "Objective-C 2.0" language extensions, including properties, fast ! enumeration (only for Objective-C), method attributes and the @optional ! and @required keywords in protocols. GCC supports Objective-C++ and ! features available in Objective-C are also available in Objective-C++. GCC by default uses the GNU Objective-C runtime library, which is part ! of GCC and is not the same as the Apple/NeXT Objective-C runtime ! library used on Apple systems. There are a number of differences ! documented in this manual. The options `-fgnu-runtime' and ! `-fnext-runtime' allow you to switch between producing output that ! works with the GNU Objective-C runtime library and output that works ! with the Apple/NeXT Objective-C runtime library. There is no formal written standard for Objective-C or Objective-C++. The authoritative manual on traditional Objective-C (1.0) is "Object-Oriented Programming and the Objective-C Language": ! * `http://www.gnustep.org/resources/documentation/ObjectivCBook.pdf' is the original NeXTstep document; ! ! * `http://objc.toodarkpark.net' is the same document in another format. The Objective-C exception and synchronization syntax (that is, the ! keywords `@try', `@throw', `@catch', `@finally' and `@synchronized') is ! supported by GCC and is enabled with the option `-fobjc-exceptions'. The syntax is briefly documented in this manual and in the Objective-C 2.0 manuals from Apple. The Objective-C 2.0 language extensions and features are automatically ! enabled; they include properties (via the `@property', `@synthesize' and ! `@dynamic keywords'), fast enumeration (not available in ! Objective-C++), attributes for methods (such as `deprecated', ! `noreturn', `sentinel', `format'), the `unused' attribute for method ! arguments, the `@package' keyword for instance variables and the ! `@optional' and `@required' keywords in protocols. You can disable all ! these Objective-C 2.0 language extensions with the option ! `-fobjc-std=objc1', which causes the compiler to recognize the same ! Objective-C language syntax recognized by GCC 4.0, and to produce an ! error if one of the new features is used. GCC has currently no support for non-fragile instance variables. The authoritative manual on Objective-C 2.0 is available from Apple: ! * ! `https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/Introduction/Introduction.html' For more information concerning the history of Objective-C that is ! available online, see `http://gcc.gnu.org/readings.html' 2.4 Go Language =============== As of the GCC 4.7.1 release, GCC supports the Go 1 language standard, ! described at `http://golang.org/doc/go1.html'. 2.5 References for Other Languages ================================== *************** conformance and compatibility of the Ada *** 383,389 **** supported by GNU Fortran. *Note Compatibility with the Java Platform: (gcj)Compatibility, for ! details of compatibility between 'gcj' and the Java Platform.  File: gcc.info, Node: Invoking GCC, Next: C Implementation, Prev: Standards, Up: Top --- 389,395 ---- supported by GNU Fortran. *Note Compatibility with the Java Platform: (gcj)Compatibility, for ! details of compatibility between `gcj' and the Java Platform.  File: gcc.info, Node: Invoking GCC, Next: C Implementation, Prev: Standards, Up: Top *************** File: gcc.info, Node: Invoking GCC, Ne *** 393,402 **** When you invoke GCC, it normally does preprocessing, compilation, assembly and linking. The "overall options" allow you to stop this ! process at an intermediate stage. For example, the '-c' option says not ! to run the linker. Then the output consists of object files output by ! the assembler. *Note Options Controlling the Kind of Output: Overall ! Options. Other options are passed on to one or more stages of processing. Some options control the preprocessor and others the compiler itself. Yet --- 399,408 ---- When you invoke GCC, it normally does preprocessing, compilation, assembly and linking. The "overall options" allow you to stop this ! process at an intermediate stage. For example, the `-c' option says ! not to run the linker. Then the output consists of object files output ! by the assembler. *Note Options Controlling the Kind of Output: ! Overall Options. Other options are passed on to one or more stages of processing. Some options control the preprocessor and others the compiler itself. Yet *************** for C programs; when an option is only u *** 409,435 **** for a particular option does not mention a source language, you can use that option with all supported languages. ! The usual way to run GCC is to run the executable called 'gcc', or ! 'MACHINE-gcc' when cross-compiling, or 'MACHINE-gcc-VERSION' to run a ! specific version of GCC. When you compile C++ programs, you should ! invoke GCC as 'g++' instead. *Note Compiling C++ Programs: Invoking ! G++, for information about the differences in behavior between 'gcc' and ! 'g++' when compiling C++ programs. ! The 'gcc' program accepts options and file names as operands. Many options have multi-letter names; therefore multiple single-letter ! options may _not_ be grouped: '-dv' is very different from '-d -v'. You can mix options and other arguments. For the most part, the order you use doesn't matter. Order does matter when you use several options ! of the same kind; for example, if you specify '-L' more than once, the ! directories are searched in the order specified. Also, the placement of ! the '-l' option is significant. ! Many options have long names starting with '-f' or with '-W'--for ! example, '-fmove-loop-invariants', '-Wformat' and so on. Most of these ! have both positive and negative forms; the negative form of '-ffoo' is ! '-fno-foo'. This manual documents only one of these two forms, whichever one is not the default. *Note Option Index::, for an index to GCC's options. --- 415,441 ---- for a particular option does not mention a source language, you can use that option with all supported languages. ! The usual way to run GCC is to run the executable called `gcc', or ! `MACHINE-gcc' when cross-compiling, or `MACHINE-gcc-VERSION' to run a ! specific version of GCC. When you compile C++ programs, you should ! invoke GCC as `g++' instead. *Note Compiling C++ Programs: Invoking ! G++, for information about the differences in behavior between `gcc' ! and `g++' when compiling C++ programs. ! The `gcc' program accepts options and file names as operands. Many options have multi-letter names; therefore multiple single-letter ! options may _not_ be grouped: `-dv' is very different from `-d -v'. You can mix options and other arguments. For the most part, the order you use doesn't matter. Order does matter when you use several options ! of the same kind; for example, if you specify `-L' more than once, the ! directories are searched in the order specified. Also, the placement ! of the `-l' option is significant. ! Many options have long names starting with `-f' or with `-W'--for ! example, `-fmove-loop-invariants', `-Wformat' and so on. Most of these ! have both positive and negative forms; the negative form of `-ffoo' is ! `-fno-foo'. This manual documents only one of these two forms, whichever one is not the default. *Note Option Index::, for an index to GCC's options. *************** _Objective-C and Objective-C++ Language *** 550,557 **** -Wundeclared-selector _Diagnostic Message Formatting Options_ ! *Note Options to Control Diagnostic Messages Formatting: Diagnostic ! Message Formatting Options. -fmessage-length=N -fdiagnostics-show-location=[once|every-line] -fdiagnostics-color=[auto|never|always] --- 556,563 ---- -Wundeclared-selector _Diagnostic Message Formatting Options_ ! *Note Options to Control Diagnostic Messages Formatting: ! Diagnostic Message Formatting Options. -fmessage-length=N -fdiagnostics-show-location=[once|every-line] -fdiagnostics-color=[auto|never|always] *************** _Warning Options_ *** 566,572 **** -Wno-attributes -Wbool-compare -Wno-builtin-macro-redefined -Wc90-c99-compat -Wc99-c11-compat -Wc++-compat -Wc++11-compat -Wc++14-compat -Wcast-align -Wcast-qual ! -Wchar-subscripts -Wclobbered -Wcomment -Wconditionally-supported -Wconversion -Wcoverage-mismatch -Wno-cpp -Wdate-time -Wdelete-incomplete -Wno-deprecated -Wno-deprecated-declarations -Wno-designated-init -Wdisabled-optimization --- 572,578 ---- -Wno-attributes -Wbool-compare -Wno-builtin-macro-redefined -Wc90-c99-compat -Wc99-c11-compat -Wc++-compat -Wc++11-compat -Wc++14-compat -Wcast-align -Wcast-qual ! -Wchar-subscripts -Wchkp -Wclobbered -Wcomment -Wconditionally-supported -Wconversion -Wcoverage-mismatch -Wno-cpp -Wdate-time -Wdelete-incomplete -Wno-deprecated -Wno-deprecated-declarations -Wno-designated-init -Wdisabled-optimization *************** _Machine-Dependent Options_ *** 1307,1316 **** -mquad-memory-atomic -mno-quad-memory-atomic -mcompat-align-parm -mno-compat-align-parm -mupper-regs-df -mno-upper-regs-df -mupper-regs-sf -mno-upper-regs-sf ! -mupper-regs -mno-upper-regs -mmodulo -mno-modulo -mfloat128 -mno-float128 -mfloat128-hardware -mno-float128-hardware ! -mpower9-fusion -mno-mpower9-fusion -mpower9-vector -mno-power9-vector ! -mpower9-dform -mno-power9-dform -mlra -mno-lra _RX Options_ -m64bit-doubles -m32bit-doubles -fpu -nofpu --- 1313,1321 ---- -mquad-memory-atomic -mno-quad-memory-atomic -mcompat-align-parm -mno-compat-align-parm -mupper-regs-df -mno-upper-regs-df -mupper-regs-sf -mno-upper-regs-sf ! -mupper-regs -mno-upper-regs -mfloat128 -mno-float128 -mfloat128-hardware -mno-float128-hardware ! -mlra -mno-lra _RX Options_ -m64bit-doubles -m32bit-doubles -fpu -nofpu *************** File: gcc.info, Node: Overall Options, *** 1506,1635 **** Compilation can involve up to four stages: preprocessing, compilation proper, assembly and linking, always in that order. GCC is capable of preprocessing and compiling several files either into several assembler ! input files, or into one assembler input file; then each assembler input ! file produces an object file, and linking combines all the object files ! (those newly compiled, and those specified as input) into an executable ! file. For any given input file, the file name suffix determines what kind of compilation is done: ! 'FILE.c' C source code that must be preprocessed. ! 'FILE.i' C source code that should not be preprocessed. ! 'FILE.ii' C++ source code that should not be preprocessed. ! 'FILE.m' Objective-C source code. Note that you must link with the ! 'libobjc' library to make an Objective-C program work. ! 'FILE.mi' Objective-C source code that should not be preprocessed. ! 'FILE.mm' ! 'FILE.M' Objective-C++ source code. Note that you must link with the ! 'libobjc' library to make an Objective-C++ program work. Note that ! '.M' refers to a literal capital M. ! 'FILE.mii' Objective-C++ source code that should not be preprocessed. ! 'FILE.h' C, C++, Objective-C or Objective-C++ header file to be turned into a precompiled header (default), or C, C++ header file to be turned ! into an Ada spec (via the '-fdump-ada-spec' switch). ! 'FILE.cc' ! 'FILE.cp' ! 'FILE.cxx' ! 'FILE.cpp' ! 'FILE.CPP' ! 'FILE.c++' ! 'FILE.C' ! C++ source code that must be preprocessed. Note that in '.cxx', ! the last two letters must both be literally 'x'. Likewise, '.C' refers to a literal capital C. ! 'FILE.mm' ! 'FILE.M' Objective-C++ source code that must be preprocessed. ! 'FILE.mii' Objective-C++ source code that should not be preprocessed. ! 'FILE.hh' ! 'FILE.H' ! 'FILE.hp' ! 'FILE.hxx' ! 'FILE.hpp' ! 'FILE.HPP' ! 'FILE.h++' ! 'FILE.tcc' C++ header file to be turned into a precompiled header or Ada spec. ! 'FILE.f' ! 'FILE.for' ! 'FILE.ftn' Fixed form Fortran source code that should not be preprocessed. ! 'FILE.F' ! 'FILE.FOR' ! 'FILE.fpp' ! 'FILE.FPP' ! 'FILE.FTN' Fixed form Fortran source code that must be preprocessed (with the traditional preprocessor). ! 'FILE.f90' ! 'FILE.f95' ! 'FILE.f03' ! 'FILE.f08' Free form Fortran source code that should not be preprocessed. ! 'FILE.F90' ! 'FILE.F95' ! 'FILE.F03' ! 'FILE.F08' Free form Fortran source code that must be preprocessed (with the traditional preprocessor). ! 'FILE.go' Go source code. ! 'FILE.ads' Ada source code file that contains a library unit declaration (a declaration of a package, subprogram, or generic, or a generic instantiation), or a library unit renaming declaration (a package, generic, or subprogram renaming declaration). Such files are also called "specs". ! 'FILE.adb' Ada source code file containing a library unit body (a subprogram or package body). Such files are also called "bodies". ! 'FILE.s' Assembler code. ! 'FILE.S' ! 'FILE.sx' Assembler code that must be preprocessed. ! 'OTHER' ! An object file to be fed straight into linking. Any file name with ! no recognized suffix is treated this way. ! You can specify the input language explicitly with the '-x' option: ! '-x LANGUAGE' Specify explicitly the LANGUAGE for the following input files (rather than letting the compiler choose a default based on the file name suffix). This option applies to all following input ! files until the next '-x' option. Possible values for LANGUAGE are: c c-header cpp-output c++ c++-header c++-cpp-output --- 1511,1640 ---- Compilation can involve up to four stages: preprocessing, compilation proper, assembly and linking, always in that order. GCC is capable of preprocessing and compiling several files either into several assembler ! input files, or into one assembler input file; then each assembler ! input file produces an object file, and linking combines all the object ! files (those newly compiled, and those specified as input) into an ! executable file. For any given input file, the file name suffix determines what kind of compilation is done: ! `FILE.c' C source code that must be preprocessed. ! `FILE.i' C source code that should not be preprocessed. ! `FILE.ii' C++ source code that should not be preprocessed. ! `FILE.m' Objective-C source code. Note that you must link with the ! `libobjc' library to make an Objective-C program work. ! `FILE.mi' Objective-C source code that should not be preprocessed. ! `FILE.mm' ! `FILE.M' Objective-C++ source code. Note that you must link with the ! `libobjc' library to make an Objective-C++ program work. Note ! that `.M' refers to a literal capital M. ! `FILE.mii' Objective-C++ source code that should not be preprocessed. ! `FILE.h' C, C++, Objective-C or Objective-C++ header file to be turned into a precompiled header (default), or C, C++ header file to be turned ! into an Ada spec (via the `-fdump-ada-spec' switch). ! `FILE.cc' ! `FILE.cp' ! `FILE.cxx' ! `FILE.cpp' ! `FILE.CPP' ! `FILE.c++' ! `FILE.C' ! C++ source code that must be preprocessed. Note that in `.cxx', ! the last two letters must both be literally `x'. Likewise, `.C' refers to a literal capital C. ! `FILE.mm' ! `FILE.M' Objective-C++ source code that must be preprocessed. ! `FILE.mii' Objective-C++ source code that should not be preprocessed. ! `FILE.hh' ! `FILE.H' ! `FILE.hp' ! `FILE.hxx' ! `FILE.hpp' ! `FILE.HPP' ! `FILE.h++' ! `FILE.tcc' C++ header file to be turned into a precompiled header or Ada spec. ! `FILE.f' ! `FILE.for' ! `FILE.ftn' Fixed form Fortran source code that should not be preprocessed. ! `FILE.F' ! `FILE.FOR' ! `FILE.fpp' ! `FILE.FPP' ! `FILE.FTN' Fixed form Fortran source code that must be preprocessed (with the traditional preprocessor). ! `FILE.f90' ! `FILE.f95' ! `FILE.f03' ! `FILE.f08' Free form Fortran source code that should not be preprocessed. ! `FILE.F90' ! `FILE.F95' ! `FILE.F03' ! `FILE.F08' Free form Fortran source code that must be preprocessed (with the traditional preprocessor). ! `FILE.go' Go source code. ! `FILE.ads' Ada source code file that contains a library unit declaration (a declaration of a package, subprogram, or generic, or a generic instantiation), or a library unit renaming declaration (a package, generic, or subprogram renaming declaration). Such files are also called "specs". ! `FILE.adb' Ada source code file containing a library unit body (a subprogram or package body). Such files are also called "bodies". ! `FILE.s' Assembler code. ! `FILE.S' ! `FILE.sx' Assembler code that must be preprocessed. ! `OTHER' ! An object file to be fed straight into linking. Any file name ! with no recognized suffix is treated this way. ! You can specify the input language explicitly with the `-x' option: ! `-x LANGUAGE' Specify explicitly the LANGUAGE for the following input files (rather than letting the compiler choose a default based on the file name suffix). This option applies to all following input ! files until the next `-x' option. Possible values for LANGUAGE are: c c-header cpp-output c++ c++-header c++-cpp-output *************** compilation is done: *** 1641,1765 **** go java ! '-x none' Turn off any specification of a language, so that subsequent files are handled according to their file name suffixes (as they are if ! '-x' has not been used at all). ! If you only want some of the stages of compilation, you can use '-x' ! (or filename suffixes) to tell 'gcc' where to start, and one of the ! options '-c', '-S', or '-E' to say where 'gcc' is to stop. Note that ! some combinations (for example, '-x cpp-output -E') instruct 'gcc' to do ! nothing at all. ! '-c' Compile or assemble the source files, but do not link. The linking stage simply is not done. The ultimate output is in the form of an object file for each source file. By default, the object file name for a source file is made by ! replacing the suffix '.c', '.i', '.s', etc., with '.o'. Unrecognized input files, not requiring compilation or assembly, are ignored. ! '-S' Stop after the stage of compilation proper; do not assemble. The output is in the form of an assembler code file for each non-assembler input file specified. By default, the assembler file name for a source file is made by ! replacing the suffix '.c', '.i', etc., with '.s'. Input files that don't require compilation are ignored. ! '-E' ! Stop after the preprocessing stage; do not run the compiler proper. ! The output is in the form of preprocessed source code, which is ! sent to the standard output. Input files that don't require preprocessing are ignored. ! '-o FILE' ! Place output in file FILE. This applies to whatever sort of output ! is being produced, whether it be an executable file, an object ! file, an assembler file or preprocessed C code. ! If '-o' is not specified, the default is to put an executable file ! in 'a.out', the object file for 'SOURCE.SUFFIX' in 'SOURCE.o', its ! assembler file in 'SOURCE.s', a precompiled header file in ! 'SOURCE.SUFFIX.gch', and all preprocessed C source on standard output. ! '-v' Print (on standard error output) the commands executed to run the stages of compilation. Also print the version number of the compiler driver program and of the preprocessor and the compiler proper. ! '-###' ! Like '-v' except the commands are not executed and arguments are ! quoted unless they contain only alphanumeric characters or './-_'. This is useful for shell scripts to capture the driver-generated command lines. ! '--help' Print (on the standard output) a description of the command-line ! options understood by 'gcc'. If the '-v' option is also specified ! then '--help' is also passed on to the various processes invoked by ! 'gcc', so that they can display the command-line options they ! accept. If the '-Wextra' option has also been specified (prior to ! the '--help' option), then command-line options that have no documentation associated with them are also displayed. ! '--target-help' Print (on the standard output) a description of target-specific command-line options for each tool. For some targets extra target-specific information may also be printed. ! '--help={CLASS|[^]QUALIFIER}[,...]' Print (on the standard output) a description of the command-line options understood by the compiler that fit into all specified classes and qualifiers. These are the supported classes: ! 'optimizers' Display all of the optimization options supported by the compiler. ! 'warnings' Display all of the options controlling warning messages produced by the compiler. ! 'target' ! Display target-specific options. Unlike the '--target-help' option however, target-specific options of the linker and assembler are not displayed. This is because those tools do ! not currently support the extended '--help=' syntax. ! 'params' ! Display the values recognized by the '--param' option. ! LANGUAGE Display the options supported for LANGUAGE, where LANGUAGE is the name of one of the languages supported in this version of GCC. ! 'common' Display the options that are common to all languages. These are the supported qualifiers: ! 'undocumented' Display only those options that are undocumented. ! 'joined' Display options taking an argument that appears after an equal sign in the same continuous piece of text, such as: ! '--help=target'. ! 'separate' Display options taking an argument that appears as a separate ! word following the original option, such as: '-o output-file'. Thus for example to display all the undocumented target-specific switches supported by the compiler, use: --- 1646,1770 ---- go java ! `-x none' Turn off any specification of a language, so that subsequent files are handled according to their file name suffixes (as they are if ! `-x' has not been used at all). ! If you only want some of the stages of compilation, you can use `-x' ! (or filename suffixes) to tell `gcc' where to start, and one of the ! options `-c', `-S', or `-E' to say where `gcc' is to stop. Note that ! some combinations (for example, `-x cpp-output -E') instruct `gcc' to ! do nothing at all. ! `-c' Compile or assemble the source files, but do not link. The linking stage simply is not done. The ultimate output is in the form of an object file for each source file. By default, the object file name for a source file is made by ! replacing the suffix `.c', `.i', `.s', etc., with `.o'. Unrecognized input files, not requiring compilation or assembly, are ignored. ! `-S' Stop after the stage of compilation proper; do not assemble. The output is in the form of an assembler code file for each non-assembler input file specified. By default, the assembler file name for a source file is made by ! replacing the suffix `.c', `.i', etc., with `.s'. Input files that don't require compilation are ignored. ! `-E' ! Stop after the preprocessing stage; do not run the compiler ! proper. The output is in the form of preprocessed source code, ! which is sent to the standard output. Input files that don't require preprocessing are ignored. ! `-o FILE' ! Place output in file FILE. This applies to whatever sort of ! output is being produced, whether it be an executable file, an ! object file, an assembler file or preprocessed C code. ! If `-o' is not specified, the default is to put an executable file ! in `a.out', the object file for `SOURCE.SUFFIX' in `SOURCE.o', its ! assembler file in `SOURCE.s', a precompiled header file in ! `SOURCE.SUFFIX.gch', and all preprocessed C source on standard output. ! `-v' Print (on standard error output) the commands executed to run the stages of compilation. Also print the version number of the compiler driver program and of the preprocessor and the compiler proper. ! `-###' ! Like `-v' except the commands are not executed and arguments are ! quoted unless they contain only alphanumeric characters or `./-_'. This is useful for shell scripts to capture the driver-generated command lines. ! `--help' Print (on the standard output) a description of the command-line ! options understood by `gcc'. If the `-v' option is also specified ! then `--help' is also passed on to the various processes invoked ! by `gcc', so that they can display the command-line options they ! accept. If the `-Wextra' option has also been specified (prior to ! the `--help' option), then command-line options that have no documentation associated with them are also displayed. ! `--target-help' Print (on the standard output) a description of target-specific command-line options for each tool. For some targets extra target-specific information may also be printed. ! `--help={CLASS|[^]QUALIFIER}[,...]' Print (on the standard output) a description of the command-line options understood by the compiler that fit into all specified classes and qualifiers. These are the supported classes: ! `optimizers' Display all of the optimization options supported by the compiler. ! `warnings' Display all of the options controlling warning messages produced by the compiler. ! `target' ! Display target-specific options. Unlike the `--target-help' option however, target-specific options of the linker and assembler are not displayed. This is because those tools do ! not currently support the extended `--help=' syntax. ! `params' ! Display the values recognized by the `--param' option. ! LANGUAGE Display the options supported for LANGUAGE, where LANGUAGE is the name of one of the languages supported in this version of GCC. ! `common' Display the options that are common to all languages. These are the supported qualifiers: ! `undocumented' Display only those options that are undocumented. ! `joined' Display options taking an argument that appears after an equal sign in the same continuous piece of text, such as: ! `--help=target'. ! `separate' Display options taking an argument that appears as a separate ! word following the original option, such as: `-o output-file'. Thus for example to display all the undocumented target-specific switches supported by the compiler, use: *************** nothing at all. *** 1767,1779 **** --help=target,undocumented The sense of a qualifier can be inverted by prefixing it with the ! '^' character, so for example to display all binary warning options ! (i.e., ones that are either on or off and that do not take an ! argument) that have a description, use: --help=warnings,^joined,^undocumented ! The argument to '--help=' should not consist solely of inverted qualifiers. Combining several classes is possible, although this usually --- 1772,1784 ---- --help=target,undocumented The sense of a qualifier can be inverted by prefixing it with the ! `^' character, so for example to display all binary warning ! options (i.e., ones that are either on or off and that do not take ! an argument) that have a description, use: --help=warnings,^joined,^undocumented ! The argument to `--help=' should not consist solely of inverted qualifiers. Combining several classes is possible, although this usually *************** nothing at all. *** 1784,1801 **** --help=target,optimizers ! The '--help=' option can be repeated on the command line. Each successive use displays its requested class of options, skipping those that have already been displayed. ! If the '-Q' option appears on the command line before the '--help=' ! option, then the descriptive text displayed by '--help=' is ! changed. Instead of describing the displayed options, an indication is given as to whether the option is enabled, disabled or set to a specific value (assuming that the compiler knows this ! at the point where the '--help=' option is used). ! Here is a truncated example from the ARM port of 'gcc': % gcc -Q -mabi=2 --help=target -c The following options are target specific: --- 1789,1806 ---- --help=target,optimizers ! The `--help=' option can be repeated on the command line. Each successive use displays its requested class of options, skipping those that have already been displayed. ! If the `-Q' option appears on the command line before the ! `--help=' option, then the descriptive text displayed by `--help=' ! is changed. Instead of describing the displayed options, an indication is given as to whether the option is enabled, disabled or set to a specific value (assuming that the compiler knows this ! at the point where the `--help=' option is used). ! Here is a truncated example from the ARM port of `gcc': % gcc -Q -mabi=2 --help=target -c The following options are target specific: *************** nothing at all. *** 1805,1895 **** The output is sensitive to the effects of previous command-line options, so for example it is possible to find out which ! optimizations are enabled at '-O2' by using: -Q -O2 --help=optimizers Alternatively you can discover which binary optimizations are ! enabled by '-O3' by using: gcc -c -Q -O3 --help=optimizers > /tmp/O3-opts gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts diff /tmp/O2-opts /tmp/O3-opts | grep enabled ! '--version' Display the version number and copyrights of the invoked GCC. ! '-pass-exit-codes' ! Normally the 'gcc' program exits with the code of 1 if any phase of ! the compiler returns a non-success return code. If you specify ! '-pass-exit-codes', the 'gcc' program instead returns with the numerically highest error produced by any phase returning an error indication. The C, C++, and Fortran front ends return 4 if an internal compiler error is encountered. ! '-pipe' Use pipes rather than temporary files for communication between the various stages of compilation. This fails to work on some systems where the assembler is unable to read from a pipe; but the GNU assembler has no trouble. ! '-specs=FILE' ! Process FILE after the compiler reads in the standard 'specs' file, ! in order to override the defaults which the 'gcc' driver program ! uses when determining what switches to pass to 'cc1', 'cc1plus', ! 'as', 'ld', etc. More than one '-specs=FILE' can be specified on ! the command line, and they are processed in order, from left to ! right. *Note Spec Files::, for information about the format of the ! FILE. ! '-wrapper' Invoke all subcommands under a wrapper program. The name of the wrapper program and its parameters are passed as a comma separated list. gcc -c t.c -wrapper gdb,--args ! This invokes all subprograms of 'gcc' under 'gdb --args', thus the ! invocation of 'cc1' is 'gdb --args cc1 ...'. ! '-fplugin=NAME.so' ! Load the plugin code in file NAME.so, assumed to be a shared object ! to be dlopen'd by the compiler. The base name of the shared object ! file is used to identify the plugin for the purposes of argument ! parsing (See '-fplugin-arg-NAME-KEY=VALUE' below). Each plugin ! should define the callback functions specified in the Plugins API. ! '-fplugin-arg-NAME-KEY=VALUE' Define an argument called KEY with a value of VALUE for the plugin called NAME. ! '-fdump-ada-spec[-slim]' For C and C++ source and include files, generate corresponding Ada ! specs. *Note (gnat_ugn)Generating Ada Bindings for C and C++ ! headers::, which provides detailed documentation on this feature. ! '-fada-spec-parent=UNIT' ! In conjunction with '-fdump-ada-spec[-slim]' above, generate Ada specs as child units of parent UNIT. ! '-fdump-go-spec=FILE' For input files in any language, generate corresponding Go ! declarations in FILE. This generates Go 'const', 'type', 'var', ! and 'func' declarations which may be a useful way to start writing a Go interface to code written in some other language. ! '@FILE' ! Read command-line options from FILE. The options read are inserted ! in place of the original @FILE option. If FILE does not exist, or ! cannot be read, then the option will be treated literally, and not ! removed. Options in FILE are separated by whitespace. A whitespace character may be included in an option by surrounding the entire ! option in either single or double quotes. Any character (including ! a backslash) may be included by prefixing the character to be ! included with a backslash. The FILE may itself contain additional ! @FILE options; any such options will be processed recursively.  File: gcc.info, Node: Invoking G++, Next: C Dialect Options, Prev: Overall Options, Up: Invoking GCC --- 1810,1903 ---- The output is sensitive to the effects of previous command-line options, so for example it is possible to find out which ! optimizations are enabled at `-O2' by using: -Q -O2 --help=optimizers Alternatively you can discover which binary optimizations are ! enabled by `-O3' by using: gcc -c -Q -O3 --help=optimizers > /tmp/O3-opts gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts diff /tmp/O2-opts /tmp/O3-opts | grep enabled ! `--version' Display the version number and copyrights of the invoked GCC. ! `-pass-exit-codes' ! Normally the `gcc' program exits with the code of 1 if any phase ! of the compiler returns a non-success return code. If you specify ! `-pass-exit-codes', the `gcc' program instead returns with the numerically highest error produced by any phase returning an error indication. The C, C++, and Fortran front ends return 4 if an internal compiler error is encountered. ! `-pipe' Use pipes rather than temporary files for communication between the various stages of compilation. This fails to work on some systems where the assembler is unable to read from a pipe; but the GNU assembler has no trouble. ! `-specs=FILE' ! Process FILE after the compiler reads in the standard `specs' ! file, in order to override the defaults which the `gcc' driver ! program uses when determining what switches to pass to `cc1', ! `cc1plus', `as', `ld', etc. More than one `-specs=FILE' can be ! specified on the command line, and they are processed in order, ! from left to right. *Note Spec Files::, for information about the ! format of the FILE. ! `-wrapper' Invoke all subcommands under a wrapper program. The name of the wrapper program and its parameters are passed as a comma separated list. gcc -c t.c -wrapper gdb,--args ! This invokes all subprograms of `gcc' under `gdb --args', thus the ! invocation of `cc1' is `gdb --args cc1 ...'. ! `-fplugin=NAME.so' ! Load the plugin code in file NAME.so, assumed to be a shared ! object to be dlopen'd by the compiler. The base name of the ! shared object file is used to identify the plugin for the purposes ! of argument parsing (See `-fplugin-arg-NAME-KEY=VALUE' below). ! Each plugin should define the callback functions specified in the ! Plugins API. ! `-fplugin-arg-NAME-KEY=VALUE' Define an argument called KEY with a value of VALUE for the plugin called NAME. ! `-fdump-ada-spec[-slim]' For C and C++ source and include files, generate corresponding Ada ! specs. *Note Generating Ada Bindings for C and C++ headers: ! (gnat_ugn)Generating Ada Bindings for C and C++ headers, which ! provides detailed documentation on this feature. ! `-fada-spec-parent=UNIT' ! In conjunction with `-fdump-ada-spec[-slim]' above, generate Ada specs as child units of parent UNIT. ! `-fdump-go-spec=FILE' For input files in any language, generate corresponding Go ! declarations in FILE. This generates Go `const', `type', `var', ! and `func' declarations which may be a useful way to start writing a Go interface to code written in some other language. ! `@FILE' ! Read command-line options from FILE. The options read are ! inserted in place of the original @FILE option. If FILE does not ! exist, or cannot be read, then the option will be treated ! literally, and not removed. Options in FILE are separated by whitespace. A whitespace character may be included in an option by surrounding the entire ! option in either single or double quotes. Any character ! (including a backslash) may be included by prefixing the character ! to be included with a backslash. The FILE may itself contain ! additional @FILE options; any such options will be processed ! recursively.  File: gcc.info, Node: Invoking G++, Next: C Dialect Options, Prev: Overall Options, Up: Invoking GCC *************** File: gcc.info, Node: Invoking G++, Ne *** 1897,1917 **** 3.3 Compiling C++ Programs ========================== ! C++ source files conventionally use one of the suffixes '.C', '.cc', ! '.cpp', '.CPP', '.c++', '.cp', or '.cxx'; C++ header files often use ! '.hh', '.hpp', '.H', or (for shared template code) '.tcc'; and ! preprocessed C++ files use the suffix '.ii'. GCC recognizes files with these names and compiles them as C++ programs even if you call the ! compiler the same way as for compiling C programs (usually with the name ! 'gcc'). ! However, the use of 'gcc' does not add the C++ library. 'g++' is a program that calls GCC and automatically specifies linking against the ! C++ library. It treats '.c', '.h' and '.i' files as C++ source files ! instead of C source files unless '-x' is used. This program is also ! useful when precompiling a C header file with a '.h' extension for use ! in C++ compilations. On many systems, 'g++' is also installed with the ! name 'c++'. When you compile C++ programs, you may specify many of the same command-line options that you use for compiling programs in any --- 1905,1925 ---- 3.3 Compiling C++ Programs ========================== ! C++ source files conventionally use one of the suffixes `.C', `.cc', ! `.cpp', `.CPP', `.c++', `.cp', or `.cxx'; C++ header files often use ! `.hh', `.hpp', `.H', or (for shared template code) `.tcc'; and ! preprocessed C++ files use the suffix `.ii'. GCC recognizes files with these names and compiles them as C++ programs even if you call the ! compiler the same way as for compiling C programs (usually with the ! name `gcc'). ! However, the use of `gcc' does not add the C++ library. `g++' is a program that calls GCC and automatically specifies linking against the ! C++ library. It treats `.c', `.h' and `.i' files as C++ source files ! instead of C source files unless `-x' is used. This program is also ! useful when precompiling a C header file with a `.h' extension for use ! in C++ compilations. On many systems, `g++' is also installed with the ! name `c++'. When you compile C++ programs, you may specify many of the same command-line options that you use for compiling programs in any *************** The following options control the dialec *** 1932,2226 **** from C, such as C++, Objective-C and Objective-C++) that the compiler accepts: ! '-ansi' ! In C mode, this is equivalent to '-std=c90'. In C++ mode, it is ! equivalent to '-std=c++98'. This turns off certain features of GCC that are incompatible with ! ISO C90 (when compiling C code), or of standard C++ (when compiling ! C++ code), such as the 'asm' and 'typeof' keywords, and predefined ! macros such as 'unix' and 'vax' that identify the type of system ! you are using. It also enables the undesirable and rarely used ISO ! trigraph feature. For the C compiler, it disables recognition of ! C++ style '//' comments as well as the 'inline' keyword. ! The alternate keywords '__asm__', '__extension__', '__inline__' and ! '__typeof__' continue to work despite '-ansi'. You would not want ! to use them in an ISO C program, of course, but it is useful to put ! them in header files that might be included in compilations done ! with '-ansi'. Alternate predefined macros such as '__unix__' and ! '__vax__' are also available, with or without '-ansi'. ! The '-ansi' option does not cause non-ISO programs to be rejected ! gratuitously. For that, '-Wpedantic' is required in addition to ! '-ansi'. *Note Warning Options::. ! The macro '__STRICT_ANSI__' is predefined when the '-ansi' option is used. Some header files may notice this macro and refrain from ! declaring certain functions or defining certain macros that the ISO ! standard doesn't call for; this is to avoid interfering with any ! programs that might use these names for other things. Functions that are normally built in but do not have semantics ! defined by ISO C (such as 'alloca' and 'ffs') are not built-in ! functions when '-ansi' is used. *Note Other built-in functions provided by GCC: Other Builtins, for details of the functions affected. ! '-std=' ! Determine the language standard. *Note Language Standards Supported by GCC: Standards, for details of these standard ! versions. This option is currently only supported when compiling C ! or C++. ! The compiler can accept several base standards, such as 'c90' or ! 'c++98', and GNU dialects of those standards, such as 'gnu90' or ! 'gnu++98'. When a base standard is specified, the compiler accepts ! all programs following that standard plus those using GNU ! extensions that do not contradict it. For example, '-std=c90' turns off certain features of GCC that are incompatible with ISO ! C90, such as the 'asm' and 'typeof' keywords, but not other GNU extensions that do not have a meaning in ISO C90, such as omitting ! the middle term of a '?:' expression. On the other hand, when a GNU dialect of a standard is specified, all features supported by the compiler are enabled, even when those features change the meaning of the base standard. As a result, some strict-conforming programs may be rejected. The particular standard is used by ! '-Wpedantic' to identify which features are GNU extensions given ! that version of the standard. For example '-std=gnu90 -Wpedantic' ! warns about C++ style '//' comments, while '-std=gnu99 -Wpedantic' does not. A value for this option must be provided; possible values are ! 'c90' ! 'c89' ! 'iso9899:1990' Support all ISO C90 programs (certain GNU extensions that ! conflict with ISO C90 are disabled). Same as '-ansi' for C code. ! 'iso9899:199409' ISO C90 as modified in amendment 1. ! 'c99' ! 'c9x' ! 'iso9899:1999' ! 'iso9899:199x' ! ISO C99. This standard is substantially completely supported, ! modulo bugs and floating-point issues (mainly but not entirely ! relating to optional C99 features from Annexes F and G). See ! for more information. The ! names 'c9x' and 'iso9899:199x' are deprecated. ! 'c11' ! 'c1x' ! 'iso9899:2011' ISO C11, the 2011 revision of the ISO C standard. This standard is substantially completely supported, modulo bugs, floating-point issues (mainly but not entirely relating to optional C11 features from Annexes F and G) and the optional Annexes K (Bounds-checking interfaces) and L (Analyzability). ! The name 'c1x' is deprecated. ! 'gnu90' ! 'gnu89' GNU dialect of ISO C90 (including some C99 features). ! 'gnu99' ! 'gnu9x' ! GNU dialect of ISO C99. The name 'gnu9x' is deprecated. ! 'gnu11' ! 'gnu1x' GNU dialect of ISO C11. This is the default for C code. The ! name 'gnu1x' is deprecated. ! 'c++98' ! 'c++03' The 1998 ISO C++ standard plus the 2003 technical corrigendum ! and some additional defect reports. Same as '-ansi' for C++ code. ! 'gnu++98' ! 'gnu++03' ! GNU dialect of '-std=c++98'. ! 'c++11' ! 'c++0x' ! The 2011 ISO C++ standard plus amendments. The name 'c++0x' is deprecated. ! 'gnu++11' ! 'gnu++0x' ! GNU dialect of '-std=c++11'. The name 'gnu++0x' is deprecated. ! 'c++14' ! 'c++1y' ! The 2014 ISO C++ standard plus amendments. The name 'c++1y' is deprecated. ! 'gnu++14' ! 'gnu++1y' ! GNU dialect of '-std=c++14'. This is the default for C++ ! code. The name 'gnu++1y' is deprecated. ! 'c++1z' ! The next revision of the ISO C++ standard, tentatively planned ! for 2017. Support is highly experimental, and will almost ! certainly change in incompatible ways in future releases. ! 'gnu++1z' ! GNU dialect of '-std=c++1z'. Support is highly experimental, and will almost certainly change in incompatible ways in future releases. ! '-fgnu89-inline' ! The option '-fgnu89-inline' tells GCC to use the traditional GNU ! semantics for 'inline' functions when in C99 mode. *Note An Inline ! Function is As Fast As a Macro: Inline. Using this option is ! roughly equivalent to adding the 'gnu_inline' function attribute to ! all inline functions (*note Function Attributes::). ! The option '-fno-gnu89-inline' explicitly tells GCC to use the C99 ! semantics for 'inline' when in C99 or gnu99 mode (i.e., it specifies the default behavior). This option is not supported in ! '-std=c90' or '-std=gnu90' mode. ! The preprocessor macros '__GNUC_GNU_INLINE__' and ! '__GNUC_STDC_INLINE__' may be used to check which semantics are in ! effect for 'inline' functions. *Note (cpp)Common Predefined ! Macros::. ! '-aux-info FILENAME' Output to the given filename prototyped declarations for all functions declared and/or defined in a translation unit, including those in header files. This option is silently ignored in any language other than C. Besides declarations, the file indicates, in comments, the origin ! of each declaration (source file and line), whether the declaration ! was implicit, prototyped or unprototyped ('I', 'N' for new or 'O' ! for old, respectively, in the first character after the line number ! and the colon), and whether it came from a declaration or a ! definition ('C' or 'F', respectively, in the following character). ! In the case of function definitions, a K&R-style list of arguments ! followed by their declarations is also provided, inside comments, ! after the declaration. ! '-fallow-parameterless-variadic-functions' Accept variadic functions without named parameters. Although it is possible to define such a function, this is not very useful as it is not possible to read the arguments. This is only supported for C as this construct is allowed by C++. ! '-fno-asm' ! Do not recognize 'asm', 'inline' or 'typeof' as a keyword, so that code can use these words as identifiers. You can use the keywords ! '__asm__', '__inline__' and '__typeof__' instead. '-ansi' implies ! '-fno-asm'. ! In C++, this switch only affects the 'typeof' keyword, since 'asm' ! and 'inline' are standard keywords. You may want to use the ! '-fno-gnu-keywords' flag instead, which has the same effect. In ! C99 mode ('-std=c99' or '-std=gnu99'), this switch only affects the ! 'asm' and 'typeof' keywords, since 'inline' is a standard keyword ! in ISO C99. ! '-fno-builtin' ! '-fno-builtin-FUNCTION' Don't recognize built-in functions that do not begin with ! '__builtin_' as prefix. *Note Other built-in functions provided by ! GCC: Other Builtins, for details of the functions affected, ! including those which are not built-in functions when '-ansi' or ! '-std' options for strict ISO C conformance are used because they do not have an ISO standard meaning. GCC normally generates special code to handle certain built-in ! functions more efficiently; for instance, calls to 'alloca' may become single instructions which adjust the stack directly, and ! calls to 'memcpy' may become inline copy loops. The resulting code ! is often both smaller and faster, but since the function calls no ! longer appear as such, you cannot set a breakpoint on those calls, ! nor can you change the behavior of the functions by linking with a ! different library. In addition, when a function is recognized as a ! built-in function, GCC may use information about that function to ! warn about problems with calls to that function, or to generate ! more efficient code, even if the resulting code still contains ! calls to that function. For example, warnings are given with ! '-Wformat' for bad calls to 'printf' when 'printf' is built in and ! 'strlen' is known not to modify global memory. ! With the '-fno-builtin-FUNCTION' option only the built-in function ! FUNCTION is disabled. FUNCTION must not begin with '__builtin_'. ! If a function is named that is not built-in in this version of GCC, ! this option is ignored. There is no corresponding ! '-fbuiltin-FUNCTION' option; if you wish to enable built-in ! functions selectively when using '-fno-builtin' or ! '-ffreestanding', you may define macros such as: #define abs(n) __builtin_abs ((n)) #define strcpy(d, s) __builtin_strcpy ((d), (s)) ! '-fhosted' ! Assert that compilation targets a hosted environment. This implies ! '-fbuiltin'. A hosted environment is one in which the entire ! standard library is available, and in which 'main' has a return ! type of 'int'. Examples are nearly everything except a kernel. ! This is equivalent to '-fno-freestanding'. ! ! '-ffreestanding' Assert that compilation targets a freestanding environment. This ! implies '-fno-builtin'. A freestanding environment is one in which ! the standard library may not exist, and program startup may not ! necessarily be at 'main'. The most obvious example is an OS ! kernel. This is equivalent to '-fno-hosted'. *Note Language Standards Supported by GCC: Standards, for details of freestanding and hosted environments. ! '-fopenacc' ! Enable handling of OpenACC directives '#pragma acc' in C/C++ and ! '!$acc' in Fortran. When '-fopenacc' is specified, the compiler generates accelerated code according to the OpenACC Application ! Programming Interface v2.0 . This option ! implies '-pthread', and thus is only supported on targets that have ! support for '-pthread'. ! '-fopenacc-dim=GEOM' Specify default compute dimensions for parallel offload regions that do not explicitly specify. The GEOM value is a triple of ':'-separated sizes, in order 'gang', 'worker' and, 'vector'. A size can be omitted, to use a target-specific default value. ! '-fopenmp' ! Enable handling of OpenMP directives '#pragma omp' in C/C++ and ! '!$omp' in Fortran. When '-fopenmp' is specified, the compiler ! generates parallel code according to the OpenMP Application Program ! Interface v4.0 . This option implies ! '-pthread', and thus is only supported on targets that have support ! for '-pthread'. '-fopenmp' implies '-fopenmp-simd'. ! '-fopenmp-simd' ! Enable handling of OpenMP's SIMD directives with '#pragma omp' in ! C/C++ and '!$omp' in Fortran. Other OpenMP directives are ignored. ! '-fcilkplus' Enable the usage of Cilk Plus language extension features for ! C/C++. When the option '-fcilkplus' is specified, enable the usage ! of the Cilk Plus Language extension features for C/C++. The present implementation follows ABI version 1.2. This is an experimental feature that is only partially complete, and whose interface may change in future versions of GCC as the official ! specification changes. Currently, all features but '_Cilk_for' have been implemented. ! '-fgnu-tm' ! When the option '-fgnu-tm' is specified, the compiler generates code for the Linux variant of Intel's current Transactional Memory ABI specification document (Revision 1.1, May 6 2009). This is an experimental feature whose interface may change in future versions --- 1940,2235 ---- from C, such as C++, Objective-C and Objective-C++) that the compiler accepts: ! `-ansi' ! In C mode, this is equivalent to `-std=c90'. In C++ mode, it is ! equivalent to `-std=c++98'. This turns off certain features of GCC that are incompatible with ! ISO C90 (when compiling C code), or of standard C++ (when ! compiling C++ code), such as the `asm' and `typeof' keywords, and ! predefined macros such as `unix' and `vax' that identify the type ! of system you are using. It also enables the undesirable and ! rarely used ISO trigraph feature. For the C compiler, it disables ! recognition of C++ style `//' comments as well as the `inline' ! keyword. ! The alternate keywords `__asm__', `__extension__', `__inline__' ! and `__typeof__' continue to work despite `-ansi'. You would not ! want to use them in an ISO C program, of course, but it is useful ! to put them in header files that might be included in compilations ! done with `-ansi'. Alternate predefined macros such as `__unix__' ! and `__vax__' are also available, with or without `-ansi'. ! The `-ansi' option does not cause non-ISO programs to be rejected ! gratuitously. For that, `-Wpedantic' is required in addition to ! `-ansi'. *Note Warning Options::. ! The macro `__STRICT_ANSI__' is predefined when the `-ansi' option is used. Some header files may notice this macro and refrain from ! declaring certain functions or defining certain macros that the ! ISO standard doesn't call for; this is to avoid interfering with ! any programs that might use these names for other things. Functions that are normally built in but do not have semantics ! defined by ISO C (such as `alloca' and `ffs') are not built-in ! functions when `-ansi' is used. *Note Other built-in functions provided by GCC: Other Builtins, for details of the functions affected. ! `-std=' ! Determine the language standard. *Note Language Standards Supported by GCC: Standards, for details of these standard ! versions. This option is currently only supported when compiling ! C or C++. ! The compiler can accept several base standards, such as `c90' or ! `c++98', and GNU dialects of those standards, such as `gnu90' or ! `gnu++98'. When a base standard is specified, the compiler ! accepts all programs following that standard plus those using GNU ! extensions that do not contradict it. For example, `-std=c90' turns off certain features of GCC that are incompatible with ISO ! C90, such as the `asm' and `typeof' keywords, but not other GNU extensions that do not have a meaning in ISO C90, such as omitting ! the middle term of a `?:' expression. On the other hand, when a GNU dialect of a standard is specified, all features supported by the compiler are enabled, even when those features change the meaning of the base standard. As a result, some strict-conforming programs may be rejected. The particular standard is used by ! `-Wpedantic' to identify which features are GNU extensions given ! that version of the standard. For example `-std=gnu90 -Wpedantic' ! warns about C++ style `//' comments, while `-std=gnu99 -Wpedantic' does not. A value for this option must be provided; possible values are ! `c90' ! `c89' ! `iso9899:1990' Support all ISO C90 programs (certain GNU extensions that ! conflict with ISO C90 are disabled). Same as `-ansi' for C code. ! `iso9899:199409' ISO C90 as modified in amendment 1. ! `c99' ! `c9x' ! `iso9899:1999' ! `iso9899:199x' ! ISO C99. This standard is substantially completely ! supported, modulo bugs and floating-point issues (mainly but ! not entirely relating to optional C99 features from Annexes F ! and G). See `http://gcc.gnu.org/c99status.html' for more ! information. The names `c9x' and `iso9899:199x' are ! deprecated. ! `c11' ! `c1x' ! `iso9899:2011' ISO C11, the 2011 revision of the ISO C standard. This standard is substantially completely supported, modulo bugs, floating-point issues (mainly but not entirely relating to optional C11 features from Annexes F and G) and the optional Annexes K (Bounds-checking interfaces) and L (Analyzability). ! The name `c1x' is deprecated. ! `gnu90' ! `gnu89' GNU dialect of ISO C90 (including some C99 features). ! `gnu99' ! `gnu9x' ! GNU dialect of ISO C99. The name `gnu9x' is deprecated. ! `gnu11' ! `gnu1x' GNU dialect of ISO C11. This is the default for C code. The ! name `gnu1x' is deprecated. ! `c++98' ! `c++03' The 1998 ISO C++ standard plus the 2003 technical corrigendum ! and some additional defect reports. Same as `-ansi' for C++ code. ! `gnu++98' ! `gnu++03' ! GNU dialect of `-std=c++98'. ! `c++11' ! `c++0x' ! The 2011 ISO C++ standard plus amendments. The name `c++0x' is deprecated. ! `gnu++11' ! `gnu++0x' ! GNU dialect of `-std=c++11'. The name `gnu++0x' is deprecated. ! `c++14' ! `c++1y' ! The 2014 ISO C++ standard plus amendments. The name `c++1y' is deprecated. ! `gnu++14' ! `gnu++1y' ! GNU dialect of `-std=c++14'. This is the default for C++ ! code. The name `gnu++1y' is deprecated. ! `c++1z' ! The next revision of the ISO C++ standard, tentatively ! planned for 2017. Support is highly experimental, and will ! almost certainly change in incompatible ways in future ! releases. ! `gnu++1z' ! GNU dialect of `-std=c++1z'. Support is highly experimental, and will almost certainly change in incompatible ways in future releases. ! `-fgnu89-inline' ! The option `-fgnu89-inline' tells GCC to use the traditional GNU ! semantics for `inline' functions when in C99 mode. *Note An ! Inline Function is As Fast As a Macro: Inline. Using this option ! is roughly equivalent to adding the `gnu_inline' function ! attribute to all inline functions (*note Function Attributes::). ! The option `-fno-gnu89-inline' explicitly tells GCC to use the C99 ! semantics for `inline' when in C99 or gnu99 mode (i.e., it specifies the default behavior). This option is not supported in ! `-std=c90' or `-std=gnu90' mode. ! The preprocessor macros `__GNUC_GNU_INLINE__' and ! `__GNUC_STDC_INLINE__' may be used to check which semantics are in ! effect for `inline' functions. *Note Common Predefined Macros: ! (cpp)Common Predefined Macros. ! `-aux-info FILENAME' Output to the given filename prototyped declarations for all functions declared and/or defined in a translation unit, including those in header files. This option is silently ignored in any language other than C. Besides declarations, the file indicates, in comments, the origin ! of each declaration (source file and line), whether the ! declaration was implicit, prototyped or unprototyped (`I', `N' for ! new or `O' for old, respectively, in the first character after the ! line number and the colon), and whether it came from a declaration ! or a definition (`C' or `F', respectively, in the following ! character). In the case of function definitions, a K&R-style list ! of arguments followed by their declarations is also provided, ! inside comments, after the declaration. ! `-fallow-parameterless-variadic-functions' Accept variadic functions without named parameters. Although it is possible to define such a function, this is not very useful as it is not possible to read the arguments. This is only supported for C as this construct is allowed by C++. ! `-fno-asm' ! Do not recognize `asm', `inline' or `typeof' as a keyword, so that code can use these words as identifiers. You can use the keywords ! `__asm__', `__inline__' and `__typeof__' instead. `-ansi' implies ! `-fno-asm'. ! In C++, this switch only affects the `typeof' keyword, since `asm' ! and `inline' are standard keywords. You may want to use the ! `-fno-gnu-keywords' flag instead, which has the same effect. In ! C99 mode (`-std=c99' or `-std=gnu99'), this switch only affects ! the `asm' and `typeof' keywords, since `inline' is a standard ! keyword in ISO C99. ! `-fno-builtin' ! `-fno-builtin-FUNCTION' Don't recognize built-in functions that do not begin with ! `__builtin_' as prefix. *Note Other built-in functions provided ! by GCC: Other Builtins, for details of the functions affected, ! including those which are not built-in functions when `-ansi' or ! `-std' options for strict ISO C conformance are used because they do not have an ISO standard meaning. GCC normally generates special code to handle certain built-in ! functions more efficiently; for instance, calls to `alloca' may become single instructions which adjust the stack directly, and ! calls to `memcpy' may become inline copy loops. The resulting ! code is often both smaller and faster, but since the function ! calls no longer appear as such, you cannot set a breakpoint on ! those calls, nor can you change the behavior of the functions by ! linking with a different library. In addition, when a function is ! recognized as a built-in function, GCC may use information about ! that function to warn about problems with calls to that function, ! or to generate more efficient code, even if the resulting code ! still contains calls to that function. For example, warnings are ! given with `-Wformat' for bad calls to `printf' when `printf' is ! built in and `strlen' is known not to modify global memory. ! With the `-fno-builtin-FUNCTION' option only the built-in function ! FUNCTION is disabled. FUNCTION must not begin with `__builtin_'. ! If a function is named that is not built-in in this version of ! GCC, this option is ignored. There is no corresponding ! `-fbuiltin-FUNCTION' option; if you wish to enable built-in ! functions selectively when using `-fno-builtin' or ! `-ffreestanding', you may define macros such as: #define abs(n) __builtin_abs ((n)) #define strcpy(d, s) __builtin_strcpy ((d), (s)) ! `-fhosted' Assert that compilation targets a hosted environment. This implies ! `-fbuiltin'. A hosted environment is one in which the entire ! standard library is available, and in which `main' has a return ! type of `int'. Examples are nearly everything except a kernel. ! This is equivalent to `-fno-freestanding'. + `-ffreestanding' Assert that compilation targets a freestanding environment. This ! implies `-fno-builtin'. A freestanding environment is one in ! which the standard library may not exist, and program startup may ! not necessarily be at `main'. The most obvious example is an OS ! kernel. This is equivalent to `-fno-hosted'. *Note Language Standards Supported by GCC: Standards, for details of freestanding and hosted environments. ! `-fopenacc' ! Enable handling of OpenACC directives `#pragma acc' in C/C++ and ! `!$acc' in Fortran. When `-fopenacc' is specified, the compiler generates accelerated code according to the OpenACC Application ! Programming Interface v2.0 `http://www.openacc.org/'. This option ! implies `-pthread', and thus is only supported on targets that ! have support for `-pthread'. ! `-fopenacc-dim=GEOM' Specify default compute dimensions for parallel offload regions that do not explicitly specify. The GEOM value is a triple of ':'-separated sizes, in order 'gang', 'worker' and, 'vector'. A size can be omitted, to use a target-specific default value. ! `-fopenmp' ! Enable handling of OpenMP directives `#pragma omp' in C/C++ and ! `!$omp' in Fortran. When `-fopenmp' is specified, the compiler ! generates parallel code according to the OpenMP Application ! Program Interface v4.0 `http://www.openmp.org/'. This option ! implies `-pthread', and thus is only supported on targets that ! have support for `-pthread'. `-fopenmp' implies `-fopenmp-simd'. ! `-fopenmp-simd' ! Enable handling of OpenMP's SIMD directives with `#pragma omp' in ! C/C++ and `!$omp' in Fortran. Other OpenMP directives are ignored. ! `-fcilkplus' Enable the usage of Cilk Plus language extension features for ! C/C++. When the option `-fcilkplus' is specified, enable the ! usage of the Cilk Plus Language extension features for C/C++. The present implementation follows ABI version 1.2. This is an experimental feature that is only partially complete, and whose interface may change in future versions of GCC as the official ! specification changes. Currently, all features but `_Cilk_for' have been implemented. ! `-fgnu-tm' ! When the option `-fgnu-tm' is specified, the compiler generates code for the Linux variant of Intel's current Transactional Memory ABI specification document (Revision 1.1, May 6 2009). This is an experimental feature whose interface may change in future versions *************** accepts: *** 2232,2240 **** libitm. Note that the transactional memory feature is not supported with ! non-call exceptions ('-fnon-call-exceptions'). ! '-fms-extensions' Accept some non-standard constructs used in Microsoft header files. In C++ code, this allows member names in structures to be similar --- 2241,2249 ---- libitm. Note that the transactional memory feature is not supported with ! non-call exceptions (`-fnon-call-exceptions'). ! `-fms-extensions' Accept some non-standard constructs used in Microsoft header files. In C++ code, this allows member names in structures to be similar *************** accepts: *** 2252,2330 **** Note that this option is off for all targets but x86 targets using ms-abi. ! '-fplan9-extensions' Accept some non-standard constructs used in Plan 9 code. ! This enables '-fms-extensions', permits passing pointers to structures with anonymous fields to functions that expect pointers to elements of the type of the field, and permits referring to anonymous fields declared using a typedef. *Note Unnamed struct/union fields within structs/unions: Unnamed Fields, for details. This is only supported for C, not C++. ! '-trigraphs' ! Support ISO C trigraphs. The '-ansi' option (and '-std' options ! for strict ISO C conformance) implies '-trigraphs'. ! '-traditional' ! '-traditional-cpp' Formerly, these options caused GCC to attempt to emulate a ! pre-standard C compiler. They are now only supported with the '-E' ! switch. The preprocessor continues to support a pre-standard mode. ! See the GNU CPP manual for details. ! '-fcond-mismatch' Allow conditional expressions with mismatched types in the second and third arguments. The value of such an expression is void. This option is not supported for C++. ! '-flax-vector-conversions' Allow implicit conversions between vectors with differing numbers of elements and/or incompatible element types. This option should not be used for new code. ! '-funsigned-char' ! Let the type 'char' be unsigned, like 'unsigned char'. ! Each kind of machine has a default for what 'char' should be. It ! is either like 'unsigned char' by default or like 'signed char' by default. ! Ideally, a portable program should always use 'signed char' or ! 'unsigned char' when it depends on the signedness of an object. ! But many programs have been written to use plain 'char' and expect it to be signed, or expect it to be unsigned, depending on the machines they were written for. This option, and its inverse, let you make such a program work with the opposite default. ! The type 'char' is always a distinct type from each of 'signed ! char' or 'unsigned char', even though its behavior is always just like one of those two. ! '-fsigned-char' ! Let the type 'char' be signed, like 'signed char'. ! Note that this is equivalent to '-fno-unsigned-char', which is the ! negative form of '-funsigned-char'. Likewise, the option ! '-fno-signed-char' is equivalent to '-funsigned-char'. ! '-fsigned-bitfields' ! '-funsigned-bitfields' ! '-fno-signed-bitfields' ! '-fno-unsigned-bitfields' These options control whether a bit-field is signed or unsigned, ! when the declaration does not use either 'signed' or 'unsigned'. ! By default, such a bit-field is signed, because this is consistent: ! the basic integer types such as 'int' are signed types. ! '-fsso-struct=ENDIANNESS' Set the default scalar storage order of structures and unions to ! the specified endianness. The accepted values are 'big-endian' and ! 'little-endian'. If the option is not passed, the compiler uses the native endianness of the target. This option is not supported for C++. ! *Warning:* the '-fsso-struct' switch causes GCC to generate code that is not binary compatible with code generated without it if the specified endianness is not the native endianness of the target. --- 2261,2339 ---- Note that this option is off for all targets but x86 targets using ms-abi. ! `-fplan9-extensions' Accept some non-standard constructs used in Plan 9 code. ! This enables `-fms-extensions', permits passing pointers to structures with anonymous fields to functions that expect pointers to elements of the type of the field, and permits referring to anonymous fields declared using a typedef. *Note Unnamed struct/union fields within structs/unions: Unnamed Fields, for details. This is only supported for C, not C++. ! `-trigraphs' ! Support ISO C trigraphs. The `-ansi' option (and `-std' options ! for strict ISO C conformance) implies `-trigraphs'. ! `-traditional' ! `-traditional-cpp' Formerly, these options caused GCC to attempt to emulate a ! pre-standard C compiler. They are now only supported with the ! `-E' switch. The preprocessor continues to support a pre-standard ! mode. See the GNU CPP manual for details. ! `-fcond-mismatch' Allow conditional expressions with mismatched types in the second and third arguments. The value of such an expression is void. This option is not supported for C++. ! `-flax-vector-conversions' Allow implicit conversions between vectors with differing numbers of elements and/or incompatible element types. This option should not be used for new code. ! `-funsigned-char' ! Let the type `char' be unsigned, like `unsigned char'. ! Each kind of machine has a default for what `char' should be. It ! is either like `unsigned char' by default or like `signed char' by default. ! Ideally, a portable program should always use `signed char' or ! `unsigned char' when it depends on the signedness of an object. ! But many programs have been written to use plain `char' and expect it to be signed, or expect it to be unsigned, depending on the machines they were written for. This option, and its inverse, let you make such a program work with the opposite default. ! The type `char' is always a distinct type from each of `signed ! char' or `unsigned char', even though its behavior is always just like one of those two. ! `-fsigned-char' ! Let the type `char' be signed, like `signed char'. ! Note that this is equivalent to `-fno-unsigned-char', which is the ! negative form of `-funsigned-char'. Likewise, the option ! `-fno-signed-char' is equivalent to `-funsigned-char'. ! `-fsigned-bitfields' ! `-funsigned-bitfields' ! `-fno-signed-bitfields' ! `-fno-unsigned-bitfields' These options control whether a bit-field is signed or unsigned, ! when the declaration does not use either `signed' or `unsigned'. ! By default, such a bit-field is signed, because this is ! consistent: the basic integer types such as `int' are signed types. ! `-fsso-struct=ENDIANNESS' Set the default scalar storage order of structures and unions to ! the specified endianness. The accepted values are `big-endian' and ! `little-endian'. If the option is not passed, the compiler uses the native endianness of the target. This option is not supported for C++. ! *Warning:* the `-fsso-struct' switch causes GCC to generate code that is not binary compatible with code generated without it if the specified endianness is not the native endianness of the target. *************** File: gcc.info, Node: C++ Dialect Optio *** 2337,2357 **** This section describes the command-line options that are only meaningful for C++ programs. You can also use most of the GNU compiler options regardless of what language your program is in. For example, you might ! compile a file 'firstClass.C' like this: g++ -g -fstrict-enums -O -c firstClass.C ! In this example, only '-fstrict-enums' is an option meant only for C++ programs; you can use the other options with any language supported by GCC. ! Some options for compiling C programs, such as '-std', are also relevant for C++ programs. *Note Options Controlling C Dialect: C Dialect Options. Here is a list of options that are _only_ for compiling C++ programs: ! '-fabi-version=N' Use version N of the C++ ABI. The default is version 0. Version 0 refers to the version conforming most closely to the C++ --- 2346,2366 ---- This section describes the command-line options that are only meaningful for C++ programs. You can also use most of the GNU compiler options regardless of what language your program is in. For example, you might ! compile a file `firstClass.C' like this: g++ -g -fstrict-enums -O -c firstClass.C ! In this example, only `-fstrict-enums' is an option meant only for C++ programs; you can use the other options with any language supported by GCC. ! Some options for compiling C programs, such as `-std', are also relevant for C++ programs. *Note Options Controlling C Dialect: C Dialect Options. Here is a list of options that are _only_ for compiling C++ programs: ! `-fabi-version=N' Use version N of the C++ ABI. The default is version 0. Version 0 refers to the version conforming most closely to the C++ *************** Dialect Options. *** 2389,2448 **** function-cv-qualifiers. Version 9, which first appeared in G++ 5.2, corrects the alignment ! of 'nullptr_t'. Version 10, which first appeared in G++ 6.1, adds mangling of attributes that affect type identity, such as ia32 calling ! convention attributes (e.g. 'stdcall'). ! See also '-Wabi'. ! '-fabi-compat-version=N' On targets that support strong aliases, G++ works around mangling changes by creating an alias with the correct mangled name when defining a symbol with an incorrect mangled name. This switch specifies which ABI version to use for the alias. ! With '-fabi-version=0' (the default), this defaults to 8 (GCC 5 compatibility). If another ABI version is explicitly selected, this defaults to 0. For compatibility with GCC versions 3.2 ! through 4.9, use '-fabi-compat-version=2'. ! If this option is not provided but '-Wabi=N' is, that version is used for compatibility aliases. If this option is provided along ! with '-Wabi' (without the version), the version from this option is ! used for the warning. ! '-fno-access-control' Turn off all access checking. This switch is mainly useful for working around bugs in the access control code. ! '-fcheck-new' ! Check that the pointer returned by 'operator new' is non-null before attempting to modify the storage allocated. This check is normally unnecessary because the C++ standard specifies that ! 'operator new' only returns '0' if it is declared 'throw()', in ! which case the compiler always checks the return value even without ! this option. In all other cases, when 'operator new' has a ! non-empty exception specification, memory exhaustion is signalled ! by throwing 'std::bad_alloc'. See also 'new (nothrow)'. ! '-fconcepts' Enable support for the C++ Extensions for Concepts Technical Specification, ISO 19217 (2015), which allows code like template concept bool Addable = requires (T t) { t + t; }; template T add (T a, T b) { return a + b; } ! '-fconstexpr-depth=N' Set the maximum nested evaluation depth for C++11 constexpr functions to N. A limit is needed to detect endless recursion during constant expression evaluation. The minimum specified by the standard is 512. ! '-fdeduce-init-list' Enable deduction of a template type parameter as ! 'std::initializer_list' from a brace-enclosed initializer list, i.e. template auto forward(T t) -> decltype (realfn (t)) --- 2398,2457 ---- function-cv-qualifiers. Version 9, which first appeared in G++ 5.2, corrects the alignment ! of `nullptr_t'. Version 10, which first appeared in G++ 6.1, adds mangling of attributes that affect type identity, such as ia32 calling ! convention attributes (e.g. `stdcall'). ! See also `-Wabi'. ! `-fabi-compat-version=N' On targets that support strong aliases, G++ works around mangling changes by creating an alias with the correct mangled name when defining a symbol with an incorrect mangled name. This switch specifies which ABI version to use for the alias. ! With `-fabi-version=0' (the default), this defaults to 8 (GCC 5 compatibility). If another ABI version is explicitly selected, this defaults to 0. For compatibility with GCC versions 3.2 ! through 4.9, use `-fabi-compat-version=2'. ! If this option is not provided but `-Wabi=N' is, that version is used for compatibility aliases. If this option is provided along ! with `-Wabi' (without the version), the version from this option ! is used for the warning. ! `-fno-access-control' Turn off all access checking. This switch is mainly useful for working around bugs in the access control code. ! `-fcheck-new' ! Check that the pointer returned by `operator new' is non-null before attempting to modify the storage allocated. This check is normally unnecessary because the C++ standard specifies that ! `operator new' only returns `0' if it is declared `throw()', in ! which case the compiler always checks the return value even ! without this option. In all other cases, when `operator new' has ! a non-empty exception specification, memory exhaustion is ! signalled by throwing `std::bad_alloc'. See also `new (nothrow)'. ! `-fconcepts' Enable support for the C++ Extensions for Concepts Technical Specification, ISO 19217 (2015), which allows code like template concept bool Addable = requires (T t) { t + t; }; template T add (T a, T b) { return a + b; } ! `-fconstexpr-depth=N' Set the maximum nested evaluation depth for C++11 constexpr functions to N. A limit is needed to detect endless recursion during constant expression evaluation. The minimum specified by the standard is 512. ! `-fdeduce-init-list' Enable deduction of a template type parameter as ! `std::initializer_list' from a brace-enclosed initializer list, i.e. template auto forward(T t) -> decltype (realfn (t)) *************** Dialect Options. *** 2461,2519 **** option is deprecated, and may be removed in a future version of G++. ! '-ffriend-injection' Inject friend functions into the enclosing namespace, so that they are visible outside the scope of the class in which they are ! declared. Friend functions were documented to work this way in the ! old Annotated C++ Reference Manual. However, in ISO C++ a friend ! function that is not declared in an enclosing scope can only be ! found using argument dependent lookup. GCC defaults to the ! standard behavior. This option is for compatibility, and may be removed in a future release of G++. ! '-fno-elide-constructors' The C++ standard allows an implementation to omit creating a temporary that is only used to initialize another object of the same type. Specifying this option disables that optimization, and forces G++ to call the copy constructor in all cases. ! '-fno-enforce-eh-specs' Don't generate code to check for violation of exception ! specifications at run time. This option violates the C++ standard, ! but may be useful for reducing code size in production builds, much ! like defining 'NDEBUG'. This does not give user code permission to ! throw exceptions in violation of the exception specifications; the ! compiler still optimizes based on the specifications, so throwing ! an unexpected exception results in undefined behavior at run time. ! '-fextern-tls-init' ! '-fno-extern-tls-init' ! The C++11 and OpenMP standards allow 'thread_local' and ! 'threadprivate' variables to have dynamic (runtime) initialization. ! To support this, any use of such a variable goes through a wrapper ! function that performs any necessary initialization. When the use ! and definition of the variable are in the same translation unit, ! this overhead can be optimized away, but when the use is in a ! different translation unit there is significant overhead even if ! the variable doesn't actually need dynamic initialization. If the ! programmer can be sure that no use of the variable in a ! non-defining TU needs to trigger dynamic initialization (either ! because the variable is statically initialized, or a use of the ! variable in the defining TU will be executed before any uses in ! another TU), they can avoid this overhead with the ! '-fno-extern-tls-init' option. On targets that support symbol aliases, the default is ! '-fextern-tls-init'. On targets that do not support symbol ! aliases, the default is '-fno-extern-tls-init'. ! '-ffor-scope' ! '-fno-for-scope' ! If '-ffor-scope' is specified, the scope of variables declared in a ! for-init-statement is limited to the 'for' loop itself, as ! specified by the C++ standard. If '-fno-for-scope' is specified, the scope of variables declared in a for-init-statement extends to the end of the enclosing scope, as was the case in old versions of G++, and other (traditional) implementations of C++. --- 2470,2529 ---- option is deprecated, and may be removed in a future version of G++. ! `-ffriend-injection' Inject friend functions into the enclosing namespace, so that they are visible outside the scope of the class in which they are ! declared. Friend functions were documented to work this way in ! the old Annotated C++ Reference Manual. However, in ISO C++ a ! friend function that is not declared in an enclosing scope can ! only be found using argument dependent lookup. GCC defaults to ! the standard behavior. This option is for compatibility, and may be removed in a future release of G++. ! `-fno-elide-constructors' The C++ standard allows an implementation to omit creating a temporary that is only used to initialize another object of the same type. Specifying this option disables that optimization, and forces G++ to call the copy constructor in all cases. ! `-fno-enforce-eh-specs' Don't generate code to check for violation of exception ! specifications at run time. This option violates the C++ ! standard, but may be useful for reducing code size in production ! builds, much like defining `NDEBUG'. This does not give user code ! permission to throw exceptions in violation of the exception ! specifications; the compiler still optimizes based on the ! specifications, so throwing an unexpected exception results in ! undefined behavior at run time. ! `-fextern-tls-init' ! `-fno-extern-tls-init' ! The C++11 and OpenMP standards allow `thread_local' and ! `threadprivate' variables to have dynamic (runtime) ! initialization. To support this, any use of such a variable goes ! through a wrapper function that performs any necessary ! initialization. When the use and definition of the variable are ! in the same translation unit, this overhead can be optimized away, ! but when the use is in a different translation unit there is ! significant overhead even if the variable doesn't actually need ! dynamic initialization. If the programmer can be sure that no use ! of the variable in a non-defining TU needs to trigger dynamic ! initialization (either because the variable is statically ! initialized, or a use of the variable in the defining TU will be ! executed before any uses in another TU), they can avoid this ! overhead with the `-fno-extern-tls-init' option. On targets that support symbol aliases, the default is ! `-fextern-tls-init'. On targets that do not support symbol ! aliases, the default is `-fno-extern-tls-init'. ! `-ffor-scope' ! `-fno-for-scope' ! If `-ffor-scope' is specified, the scope of variables declared in ! a for-init-statement is limited to the `for' loop itself, as ! specified by the C++ standard. If `-fno-for-scope' is specified, the scope of variables declared in a for-init-statement extends to the end of the enclosing scope, as was the case in old versions of G++, and other (traditional) implementations of C++. *************** Dialect Options. *** 2522,2672 **** but to allow and give a warning for old-style code that would otherwise be invalid, or have different behavior. ! '-fno-gnu-keywords' ! Do not recognize 'typeof' as a keyword, so that code can use this ! word as an identifier. You can use the keyword '__typeof__' instead. This option is implied by the strict ISO C++ dialects: ! '-ansi', '-std=c++98', '-std=c++11', etc. ! '-fno-implicit-templates' Never emit code for non-inline templates that are instantiated implicitly (i.e. by use); only emit code for explicit instantiations. *Note Template Instantiation::, for more information. ! '-fno-implicit-inline-templates' Don't emit code for implicit instantiations of inline templates, either. The default is to handle inlines differently so that compiles with and without optimization need the same set of explicit instantiations. ! '-fno-implement-inlines' To save space, do not emit out-of-line copies of inline functions ! controlled by '#pragma implementation'. This causes linker errors if these functions are not inlined everywhere they are called. ! '-fms-extensions' Disable Wpedantic warnings about constructs used in MFC, such as implicit int and getting a pointer to member function via non-standard syntax. ! '-fno-nonansi-builtins' Disable built-in declarations of functions that are not mandated by ! ANSI/ISO C. These include 'ffs', 'alloca', '_exit', 'index', ! 'bzero', 'conjf', and other related functions. ! '-fnothrow-opt' ! Treat a 'throw()' exception specification as if it were a ! 'noexcept' specification to reduce or eliminate the text size overhead relative to a function with no exception specification. If the function has local variables of types with non-trivial destructors, the exception specification actually makes the function smaller because the EH cleanups for those variables can be optimized away. The semantic effect is that an exception thrown ! out of a function with such an exception specification results in a ! call to 'terminate' rather than 'unexpected'. ! '-fno-operator-names' ! Do not treat the operator name keywords 'and', 'bitand', 'bitor', ! 'compl', 'not', 'or' and 'xor' as synonyms as keywords. ! '-fno-optional-diags' ! Disable diagnostics that the standard says a compiler does not need ! to issue. Currently, the only such diagnostic issued by G++ is the ! one for a name having multiple meanings within a class. ! '-fpermissive' Downgrade some diagnostics about nonconformant code from errors to ! warnings. Thus, using '-fpermissive' allows some nonconforming code to compile. ! '-fno-pretty-templates' When an error message refers to a specialization of a function template, the compiler normally prints the signature of the template followed by the template arguments and any typedefs or ! typenames in the signature (e.g. 'void f(T) [with T = int]' rather ! than 'void f(int)') so that it's clear which template is involved. When an error message refers to a specialization of a class template, the compiler omits any template arguments that match the default template arguments for that template. If either of these behaviors make it harder to understand the error message rather ! than easier, you can use '-fno-pretty-templates' to disable them. ! '-frepo' Enable automatic template instantiation at link time. This option ! also implies '-fno-implicit-templates'. *Note Template Instantiation::, for more information. ! '-fno-rtti' Disable generation of information about every class with virtual functions for use by the C++ run-time type identification features ! ('dynamic_cast' and 'typeid'). If you don't use those parts of the ! language, you can save some space by using this flag. Note that ! exception handling uses the same information, but G++ generates it ! as needed. The 'dynamic_cast' operator can still be used for casts ! that do not require run-time type information, i.e. casts to 'void ! *' or to unambiguous base classes. ! '-fsized-deallocation' Enable the built-in global declarations void operator delete (void *, std::size_t) noexcept; void operator delete[] (void *, std::size_t) noexcept; as introduced in C++14. This is useful for user-defined replacement deallocation functions that, for example, use the size of the object to make deallocation faster. Enabled by default ! under '-std=c++14' and above. The flag '-Wsized-deallocation' warns about places that might want to add a definition. ! '-fstrict-enums' Allow the compiler to optimize using the assumption that a value of enumerated type can only be one of the values of the enumeration (as defined in the C++ standard; basically, a value that can be represented in the minimum number of bits needed to represent all the enumerators). This assumption may not be valid if the program ! uses a cast to convert an arbitrary integer value to the enumerated ! type. ! '-ftemplate-backtrace-limit=N' Set the maximum number of template instantiation notes for a single warning or error to N. The default value is 10. ! '-ftemplate-depth=N' Set the maximum instantiation depth for template classes to N. A limit on the template instantiation depth is needed to detect endless recursions during template class instantiation. ANSI/ISO C++ conforming programs must not rely on a maximum depth greater than 17 (changed to 1024 in C++11). The default value is 900, as ! the compiler can run out of stack space before hitting 1024 in some ! situations. ! '-fno-threadsafe-statics' Do not emit the extra code to use the routines specified in the C++ ABI for thread-safe initialization of local statics. You can use this option to reduce code size slightly in code that doesn't need to be thread-safe. ! '-fuse-cxa-atexit' Register destructors for objects with static storage duration with ! the '__cxa_atexit' function rather than the 'atexit' function. This option is required for fully standards-compliant handling of static destructors, but only works if your C library supports ! '__cxa_atexit'. ! '-fno-use-cxa-get-exception-ptr' ! Don't use the '__cxa_get_exception_ptr' runtime routine. This ! causes 'std::uncaught_exception' to be incorrect, but is necessary if the runtime routine is not available. ! '-fvisibility-inlines-hidden' This switch declares that the user does not attempt to compare pointers to inline functions or methods where the addresses of the two functions are taken in different shared objects. The effect of this is that GCC may, effectively, mark inline ! methods with '__attribute__ ((visibility ("hidden")))' so that they ! do not appear in the export table of a DSO and do not require a PLT ! indirection when used within the DSO. Enabling this option can ! have a dramatic effect on load and link times of a DSO as it massively reduces the size of the dynamic export table when the library makes heavy use of templates. --- 2532,2682 ---- but to allow and give a warning for old-style code that would otherwise be invalid, or have different behavior. ! `-fno-gnu-keywords' ! Do not recognize `typeof' as a keyword, so that code can use this ! word as an identifier. You can use the keyword `__typeof__' instead. This option is implied by the strict ISO C++ dialects: ! `-ansi', `-std=c++98', `-std=c++11', etc. ! `-fno-implicit-templates' Never emit code for non-inline templates that are instantiated implicitly (i.e. by use); only emit code for explicit instantiations. *Note Template Instantiation::, for more information. ! `-fno-implicit-inline-templates' Don't emit code for implicit instantiations of inline templates, either. The default is to handle inlines differently so that compiles with and without optimization need the same set of explicit instantiations. ! `-fno-implement-inlines' To save space, do not emit out-of-line copies of inline functions ! controlled by `#pragma implementation'. This causes linker errors if these functions are not inlined everywhere they are called. ! `-fms-extensions' Disable Wpedantic warnings about constructs used in MFC, such as implicit int and getting a pointer to member function via non-standard syntax. ! `-fno-nonansi-builtins' Disable built-in declarations of functions that are not mandated by ! ANSI/ISO C. These include `ffs', `alloca', `_exit', `index', ! `bzero', `conjf', and other related functions. ! `-fnothrow-opt' ! Treat a `throw()' exception specification as if it were a ! `noexcept' specification to reduce or eliminate the text size overhead relative to a function with no exception specification. If the function has local variables of types with non-trivial destructors, the exception specification actually makes the function smaller because the EH cleanups for those variables can be optimized away. The semantic effect is that an exception thrown ! out of a function with such an exception specification results in ! a call to `terminate' rather than `unexpected'. ! `-fno-operator-names' ! Do not treat the operator name keywords `and', `bitand', `bitor', ! `compl', `not', `or' and `xor' as synonyms as keywords. ! `-fno-optional-diags' ! Disable diagnostics that the standard says a compiler does not ! need to issue. Currently, the only such diagnostic issued by G++ ! is the one for a name having multiple meanings within a class. ! `-fpermissive' Downgrade some diagnostics about nonconformant code from errors to ! warnings. Thus, using `-fpermissive' allows some nonconforming code to compile. ! `-fno-pretty-templates' When an error message refers to a specialization of a function template, the compiler normally prints the signature of the template followed by the template arguments and any typedefs or ! typenames in the signature (e.g. `void f(T) [with T = int]' rather ! than `void f(int)') so that it's clear which template is involved. When an error message refers to a specialization of a class template, the compiler omits any template arguments that match the default template arguments for that template. If either of these behaviors make it harder to understand the error message rather ! than easier, you can use `-fno-pretty-templates' to disable them. ! `-frepo' Enable automatic template instantiation at link time. This option ! also implies `-fno-implicit-templates'. *Note Template Instantiation::, for more information. ! `-fno-rtti' Disable generation of information about every class with virtual functions for use by the C++ run-time type identification features ! (`dynamic_cast' and `typeid'). If you don't use those parts of ! the language, you can save some space by using this flag. Note ! that exception handling uses the same information, but G++ ! generates it as needed. The `dynamic_cast' operator can still be ! used for casts that do not require run-time type information, i.e. ! casts to `void *' or to unambiguous base classes. ! `-fsized-deallocation' Enable the built-in global declarations void operator delete (void *, std::size_t) noexcept; void operator delete[] (void *, std::size_t) noexcept; as introduced in C++14. This is useful for user-defined replacement deallocation functions that, for example, use the size of the object to make deallocation faster. Enabled by default ! under `-std=c++14' and above. The flag `-Wsized-deallocation' warns about places that might want to add a definition. ! `-fstrict-enums' Allow the compiler to optimize using the assumption that a value of enumerated type can only be one of the values of the enumeration (as defined in the C++ standard; basically, a value that can be represented in the minimum number of bits needed to represent all the enumerators). This assumption may not be valid if the program ! uses a cast to convert an arbitrary integer value to the ! enumerated type. ! `-ftemplate-backtrace-limit=N' Set the maximum number of template instantiation notes for a single warning or error to N. The default value is 10. ! `-ftemplate-depth=N' Set the maximum instantiation depth for template classes to N. A limit on the template instantiation depth is needed to detect endless recursions during template class instantiation. ANSI/ISO C++ conforming programs must not rely on a maximum depth greater than 17 (changed to 1024 in C++11). The default value is 900, as ! the compiler can run out of stack space before hitting 1024 in ! some situations. ! `-fno-threadsafe-statics' Do not emit the extra code to use the routines specified in the C++ ABI for thread-safe initialization of local statics. You can use this option to reduce code size slightly in code that doesn't need to be thread-safe. ! `-fuse-cxa-atexit' Register destructors for objects with static storage duration with ! the `__cxa_atexit' function rather than the `atexit' function. This option is required for fully standards-compliant handling of static destructors, but only works if your C library supports ! `__cxa_atexit'. ! `-fno-use-cxa-get-exception-ptr' ! Don't use the `__cxa_get_exception_ptr' runtime routine. This ! causes `std::uncaught_exception' to be incorrect, but is necessary if the runtime routine is not available. ! `-fvisibility-inlines-hidden' This switch declares that the user does not attempt to compare pointers to inline functions or methods where the addresses of the two functions are taken in different shared objects. The effect of this is that GCC may, effectively, mark inline ! methods with `__attribute__ ((visibility ("hidden")))' so that ! they do not appear in the export table of a DSO and do not require ! a PLT indirection when used within the DSO. Enabling this option ! can have a dramatic effect on load and link times of a DSO as it massively reduces the size of the dynamic export table when the library makes heavy use of templates. *************** Dialect Options. *** 2685,2698 **** option as their linkage might otherwise cross a shared library boundary. *Note Template Instantiation::. ! '-fvisibility-ms-compat' This flag attempts to use visibility settings to make GCC's C++ linkage model compatible with that of Microsoft Visual Studio. The flag makes these changes to GCC's linkage model: ! 1. It sets the default visibility to 'hidden', like ! '-fvisibility=hidden'. 2. Types, but not their members, are not hidden by default. --- 2695,2708 ---- option as their linkage might otherwise cross a shared library boundary. *Note Template Instantiation::. ! `-fvisibility-ms-compat' This flag attempts to use visibility settings to make GCC's C++ linkage model compatible with that of Microsoft Visual Studio. The flag makes these changes to GCC's linkage model: ! 1. It sets the default visibility to `hidden', like ! `-fvisibility=hidden'. 2. Types, but not their members, are not hidden by default. *************** Dialect Options. *** 2701,2707 **** shared object: those declarations are permitted if they are permitted when this option is not used. ! In new code it is better to use '-fvisibility=hidden' and export those classes that are intended to be externally visible. Unfortunately it is possible for code to rely, perhaps accidentally, on the Visual Studio behavior. --- 2711,2717 ---- shared object: those declarations are permitted if they are permitted when this option is not used. ! In new code it is better to use `-fvisibility=hidden' and export those classes that are intended to be externally visible. Unfortunately it is possible for code to rely, perhaps accidentally, on the Visual Studio behavior. *************** Dialect Options. *** 2714,2752 **** given, it is a violation of the ODR to define types with the same name differently. ! '-fno-weak' Do not use weak symbol support, even if it is provided by the linker. By default, G++ uses weak symbols if they are available. This option exists only for testing, and should not be used by end-users; it results in inferior code and has no benefits. This option may be removed in a future release of G++. ! '-nostdinc++' ! Do not search for header files in the standard directories specific ! to C++, but do still search the other standard directories. (This ! option is used when building the C++ library.) In addition, these optimization, warning, and code generation options have meanings only for C++ programs: ! '-Wabi (C, Objective-C, C++ and Objective-C++ only)' Warn when G++ it generates code that is probably not compatible with the vendor-neutral C++ ABI. Since G++ now defaults to ! updating the ABI with each major release, normally '-Wabi' will warn only if there is a check added later in a release series for ! an ABI issue discovered since the initial release. '-Wabi' will warn about more things if an older ABI version is selected (with ! '-fabi-version=N'). ! '-Wabi' can also be used with an explicit version number to warn ! about compatibility with a particular '-fabi-version' level, e.g. ! '-Wabi=2' to warn about changes relative to '-fabi-version=2'. If an explicit version number is provided and ! '-fabi-compat-version' is not specified, the version number from this option is used for compatibility aliases. If no explicit version number is provided with this option, but ! '-fabi-compat-version' is specified, that version number is used for ABI warnings. Although an effort has been made to warn about all such cases, --- 2724,2762 ---- given, it is a violation of the ODR to define types with the same name differently. ! `-fno-weak' Do not use weak symbol support, even if it is provided by the linker. By default, G++ uses weak symbols if they are available. This option exists only for testing, and should not be used by end-users; it results in inferior code and has no benefits. This option may be removed in a future release of G++. ! `-nostdinc++' ! Do not search for header files in the standard directories ! specific to C++, but do still search the other standard ! directories. (This option is used when building the C++ library.) In addition, these optimization, warning, and code generation options have meanings only for C++ programs: ! `-Wabi (C, Objective-C, C++ and Objective-C++ only)' Warn when G++ it generates code that is probably not compatible with the vendor-neutral C++ ABI. Since G++ now defaults to ! updating the ABI with each major release, normally `-Wabi' will warn only if there is a check added later in a release series for ! an ABI issue discovered since the initial release. `-Wabi' will warn about more things if an older ABI version is selected (with ! `-fabi-version=N'). ! `-Wabi' can also be used with an explicit version number to warn ! about compatibility with a particular `-fabi-version' level, e.g. ! `-Wabi=2' to warn about changes relative to `-fabi-version=2'. If an explicit version number is provided and ! `-fabi-compat-version' is not specified, the version number from this option is used for compatibility aliases. If no explicit version number is provided with this option, but ! `-fabi-compat-version' is specified, that version number is used for ABI warnings. Although an effort has been made to warn about all such cases, *************** have meanings only for C++ programs: *** 2759,2766 **** concerned about the fact that code generated by G++ may not be binary compatible with code generated by other compilers. ! Known incompatibilities in '-fabi-version=2' (which was the default ! from GCC 3.4 to 4.9) include: * A template with a non-type template parameter of reference type was mangled incorrectly: --- 2769,2776 ---- concerned about the fact that code generated by G++ may not be binary compatible with code generated by other compilers. ! Known incompatibilities in `-fabi-version=2' (which was the ! default from GCC 3.4 to 4.9) include: * A template with a non-type template parameter of reference type was mangled incorrectly: *************** have meanings only for C++ programs: *** 2768,2863 **** template struct S {}; void n (S) {2} ! This was fixed in '-fabi-version=3'. ! * SIMD vector types declared using '__attribute ((vector_size))' ! were mangled in a non-standard way that does not allow for ! overloading of functions taking vectors of different sizes. ! The mangling was changed in '-fabi-version=4'. ! * '__attribute ((const))' and 'noreturn' were mangled as type ! qualifiers, and 'decltype' of a plain declaration was folded away. ! These mangling issues were fixed in '-fabi-version=5'. * Scoped enumerators passed as arguments to a variadic function ! are promoted like unscoped enumerators, causing 'va_arg' to complain. On most targets this does not actually affect the parameter passing ABI, as there is no way to pass an argument ! smaller than 'int'. Also, the ABI changed the mangling of template argument packs, ! 'const_cast', 'static_cast', prefix increment/decrement, and a ! class scope function used as a template argument. ! These issues were corrected in '-fabi-version=6'. * Lambdas in default argument scope were mangled incorrectly, ! and the ABI changed the mangling of 'nullptr_t'. ! These issues were corrected in '-fabi-version=7'. * When mangling a function type with function-cv-qualifiers, the un-qualified function type was incorrectly treated as a substitution candidate. ! This was fixed in '-fabi-version=8', the default for GCC 5.1. ! * 'decltype(nullptr)' incorrectly had an alignment of 1, leading ! to unaligned accesses. Note that this did not affect the ABI ! of a function with a 'nullptr_t' parameter, as parameters have ! a minimum alignment. ! This was fixed in '-fabi-version=9', the default for GCC 5.2. ! * Target-specific attributes that affect the identity of a type, ! such as ia32 calling conventions on a function type (stdcall, ! regparm, etc.), did not affect the mangled name, leading to ! name collisions when function pointers were used as template ! arguments. ! This was fixed in '-fabi-version=10', the default for GCC 6.1. - It also warns about psABI-related changes. The known psABI changes - at this point include: ! * For SysV/x86-64, unions with 'long double' members are passed ! in memory as specified in psABI. For example: union U { long double ld; int i; }; ! 'union U' is always passed in memory. ! '-Wabi-tag (C++ and Objective-C++ only)' Warn when a type with an ABI tag is used in a context that does not have that ABI tag. See *note C++ Attributes:: for more information about ABI tags. ! '-Wctor-dtor-privacy (C++ and Objective-C++ only)' Warn when a class seems unusable because all the constructors or destructors in that class are private, and it has neither friends nor public static member functions. Also warn if there are no non-private methods, and there's at least one private member function that isn't a constructor or destructor. ! '-Wdelete-non-virtual-dtor (C++ and Objective-C++ only)' ! Warn when 'delete' is used to destroy an instance of a class that ! has virtual functions and non-virtual destructor. It is unsafe to delete an instance of a derived class through a pointer to a base class if the base class does not have a virtual destructor. This ! warning is enabled by '-Wall'. ! '-Wliteral-suffix (C++ and Objective-C++ only)' Warn when a string or character literal is followed by a ud-suffix which does not begin with an underscore. As a conforming extension, GCC treats such suffixes as separate preprocessing tokens in order to maintain backwards compatibility with code that ! uses formatting macros from ''. For example: #define __STDC_FORMAT_MACROS #include --- 2778,2876 ---- template struct S {}; void n (S) {2} ! This was fixed in `-fabi-version=3'. ! * SIMD vector types declared using `__attribute ! ((vector_size))' were mangled in a non-standard way that does ! not allow for overloading of functions taking vectors of ! different sizes. ! The mangling was changed in `-fabi-version=4'. ! * `__attribute ((const))' and `noreturn' were mangled as type ! qualifiers, and `decltype' of a plain declaration was folded away. ! These mangling issues were fixed in `-fabi-version=5'. * Scoped enumerators passed as arguments to a variadic function ! are promoted like unscoped enumerators, causing `va_arg' to complain. On most targets this does not actually affect the parameter passing ABI, as there is no way to pass an argument ! smaller than `int'. Also, the ABI changed the mangling of template argument packs, ! `const_cast', `static_cast', prefix increment/decrement, and ! a class scope function used as a template argument. ! These issues were corrected in `-fabi-version=6'. * Lambdas in default argument scope were mangled incorrectly, ! and the ABI changed the mangling of `nullptr_t'. ! These issues were corrected in `-fabi-version=7'. * When mangling a function type with function-cv-qualifiers, the un-qualified function type was incorrectly treated as a substitution candidate. ! This was fixed in `-fabi-version=8', the default for GCC 5.1. ! * `decltype(nullptr)' incorrectly had an alignment of 1, ! leading to unaligned accesses. Note that this did not affect ! the ABI of a function with a `nullptr_t' parameter, as ! parameters have a minimum alignment. ! This was fixed in `-fabi-version=9', the default for GCC 5.2. ! * Target-specific attributes that affect the identity of a ! type, such as ia32 calling conventions on a function type ! (stdcall, regparm, etc.), did not affect the mangled name, ! leading to name collisions when function pointers were used ! as template arguments. ! This was fixed in `-fabi-version=10', the default for GCC 6.1. ! It also warns about psABI-related changes. The known psABI ! changes at this point include: ! ! * For SysV/x86-64, unions with `long double' members are passed ! in memory as specified in psABI. For example: union U { long double ld; int i; }; ! `union U' is always passed in memory. ! ! `-Wabi-tag (C++ and Objective-C++ only)' Warn when a type with an ABI tag is used in a context that does not have that ABI tag. See *note C++ Attributes:: for more information about ABI tags. ! `-Wctor-dtor-privacy (C++ and Objective-C++ only)' Warn when a class seems unusable because all the constructors or destructors in that class are private, and it has neither friends nor public static member functions. Also warn if there are no non-private methods, and there's at least one private member function that isn't a constructor or destructor. ! `-Wdelete-non-virtual-dtor (C++ and Objective-C++ only)' ! Warn when `delete' is used to destroy an instance of a class that ! has virtual functions and non-virtual destructor. It is unsafe to delete an instance of a derived class through a pointer to a base class if the base class does not have a virtual destructor. This ! warning is enabled by `-Wall'. ! `-Wliteral-suffix (C++ and Objective-C++ only)' Warn when a string or character literal is followed by a ud-suffix which does not begin with an underscore. As a conforming extension, GCC treats such suffixes as separate preprocessing tokens in order to maintain backwards compatibility with code that ! uses formatting macros from `'. For example: #define __STDC_FORMAT_MACROS #include *************** have meanings only for C++ programs: *** 2868,2915 **** printf("My int64: %" PRId64"\n", i64); } ! In this case, 'PRId64' is treated as a separate preprocessing token. This warning is enabled by default. ! '-Wlto-type-mismatch' ! During the link-time optimization warn about type mismatches in global declarations from different compilation units. Requires ! '-flto' to be enabled. Enabled by default. ! '-Wnarrowing (C++ and Objective-C++ only)' ! With '-std=gnu++98' or '-std=c++98', warn when a narrowing ! conversion prohibited by C++11 occurs within '{ }', e.g. int i = { 2.2 }; // error: narrowing from double to int ! This flag is included in '-Wall' and '-Wc++11-compat'. ! When a later standard is in effect, e.g. when using '-std=c++11', narrowing conversions are diagnosed by default, as required by the standard. A narrowing conversion from a constant produces an error, and a narrowing conversion from a non-constant produces a ! warning, but '-Wno-narrowing' suppresses the diagnostic. Note that ! this does not affect the meaning of well-formed code; narrowing ! conversions are still considered ill-formed in SFINAE contexts. ! '-Wnoexcept (C++ and Objective-C++ only)' Warn when a noexcept-expression evaluates to false because of a call to a function that does not have a non-throwing exception ! specification (i.e. 'throw()' or 'noexcept') but is known by the compiler to never throw an exception. ! '-Wnon-virtual-dtor (C++ and Objective-C++ only)' Warn when a class has virtual functions and an accessible non-virtual destructor itself or in an accessible polymorphic base class, in which case it is possible but unsafe to delete an instance of a derived class through a pointer to the class itself ! or base class. This warning is automatically enabled if '-Weffc++' ! is specified. ! '-Wreorder (C++ and Objective-C++ only)' Warn when the order of member initializers given in the code does not match the order in which they must be executed. For instance: --- 2881,2928 ---- printf("My int64: %" PRId64"\n", i64); } ! In this case, `PRId64' is treated as a separate preprocessing token. This warning is enabled by default. ! `-Wlto-type-mismatch' During the link-time optimization warn about type mismatches in global declarations from different compilation units. Requires ! `-flto' to be enabled. Enabled by default. ! `-Wnarrowing (C++ and Objective-C++ only)' ! With `-std=gnu++98' or `-std=c++98', warn when a narrowing ! conversion prohibited by C++11 occurs within `{ }', e.g. int i = { 2.2 }; // error: narrowing from double to int ! This flag is included in `-Wall' and `-Wc++11-compat'. ! When a later standard is in effect, e.g. when using `-std=c++11', narrowing conversions are diagnosed by default, as required by the standard. A narrowing conversion from a constant produces an error, and a narrowing conversion from a non-constant produces a ! warning, but `-Wno-narrowing' suppresses the diagnostic. Note ! that this does not affect the meaning of well-formed code; ! narrowing conversions are still considered ill-formed in SFINAE ! contexts. ! `-Wnoexcept (C++ and Objective-C++ only)' Warn when a noexcept-expression evaluates to false because of a call to a function that does not have a non-throwing exception ! specification (i.e. `throw()' or `noexcept') but is known by the compiler to never throw an exception. ! `-Wnon-virtual-dtor (C++ and Objective-C++ only)' Warn when a class has virtual functions and an accessible non-virtual destructor itself or in an accessible polymorphic base class, in which case it is possible but unsafe to delete an instance of a derived class through a pointer to the class itself ! or base class. This warning is automatically enabled if ! `-Weffc++' is specified. ! `-Wreorder (C++ and Objective-C++ only)' Warn when the order of member initializers given in the code does not match the order in which they must be executed. For instance: *************** have meanings only for C++ programs: *** 2919,2949 **** A(): j (0), i (1) { } }; ! The compiler rearranges the member initializers for 'i' and 'j' to match the declaration order of the members, emitting a warning to ! that effect. This warning is enabled by '-Wall'. ! '-fext-numeric-literals (C++ and Objective-C++ only)' Accept imaginary, fixed-point, or machine-defined literal number suffixes as GNU extensions. When this option is turned off these suffixes are treated as C++11 user-defined literal numeric ! suffixes. This is on by default for all pre-C++11 dialects and all ! GNU dialects: '-std=c++98', '-std=gnu++98', '-std=gnu++11', ! '-std=gnu++14'. This option is off by default for ISO C++11 ! onwards ('-std=c++11', ...). ! The following '-W...' options are not affected by '-Wall'. ! '-Weffc++ (C++ and Objective-C++ only)' Warn about violations of the following style guidelines from Scott ! Meyers' 'Effective C++' series of books: * Define a copy constructor and an assignment operator for classes with dynamically-allocated memory. * Prefer initialization to assignment in constructors. ! * Have 'operator=' return a reference to '*this'. * Don't try to return a reference when you must return an object. --- 2932,2962 ---- A(): j (0), i (1) { } }; ! The compiler rearranges the member initializers for `i' and `j' to match the declaration order of the members, emitting a warning to ! that effect. This warning is enabled by `-Wall'. ! `-fext-numeric-literals (C++ and Objective-C++ only)' Accept imaginary, fixed-point, or machine-defined literal number suffixes as GNU extensions. When this option is turned off these suffixes are treated as C++11 user-defined literal numeric ! suffixes. This is on by default for all pre-C++11 dialects and ! all GNU dialects: `-std=c++98', `-std=gnu++98', `-std=gnu++11', ! `-std=gnu++14'. This option is off by default for ISO C++11 ! onwards (`-std=c++11', ...). ! The following `-W...' options are not affected by `-Wall'. ! `-Weffc++ (C++ and Objective-C++ only)' Warn about violations of the following style guidelines from Scott ! Meyers' `Effective C++' series of books: * Define a copy constructor and an assignment operator for classes with dynamically-allocated memory. * Prefer initialization to assignment in constructors. ! * Have `operator=' return a reference to `*this'. * Don't try to return a reference when you must return an object. *************** have meanings only for C++ programs: *** 2951,2997 **** * Distinguish between prefix and postfix forms of increment and decrement operators. ! * Never overload '&&', '||', or ','. ! This option also enables '-Wnon-virtual-dtor', which is also one of ! the effective C++ recommendations. However, the check is extended ! to warn about the lack of virtual destructor in accessible non-polymorphic bases classes too. When selecting this option, be aware that the standard library ! headers do not obey all of these guidelines; use 'grep -v' to filter out those warnings. ! '-Wstrict-null-sentinel (C++ and Objective-C++ only)' ! Warn about the use of an uncasted 'NULL' as sentinel. When ! compiling only with GCC this is a valid sentinel, as 'NULL' is ! defined to '__null'. Although it is a null pointer constant rather ! than a null pointer, it is guaranteed to be of the same size as a ! pointer. But this use is not portable across different compilers. ! '-Wno-non-template-friend (C++ and Objective-C++ only)' Disable warnings when non-templatized friend functions are declared within a template. Since the advent of explicit template specification support in G++, if the name of the friend is an ! unqualified-id (i.e., 'friend foo(int)'), the C++ language specification demands that the friend declare or define an ordinary, nontemplate function. (Section 14.5.3). Before G++ implemented explicit specification, unqualified-ids could be interpreted as a particular specialization of a templatized function. Because this non-conforming behavior is no longer the ! default behavior for G++, '-Wnon-template-friend' allows the compiler to check existing code for potential trouble spots and is on by default. This new compiler behavior can be turned off with ! '-Wno-non-template-friend', which keeps the conformant compiler code but disables the helpful warning. ! '-Wold-style-cast (C++ and Objective-C++ only)' Warn if an old-style (C-style) cast to a non-void type is used ! within a C++ program. The new-style casts ('dynamic_cast', ! 'static_cast', 'reinterpret_cast', and 'const_cast') are less vulnerable to unintended effects and much easier to search for. ! '-Woverloaded-virtual (C++ and Objective-C++ only)' Warn when a function declaration hides virtual functions from a base class. For example, in: --- 2964,3012 ---- * Distinguish between prefix and postfix forms of increment and decrement operators. ! * Never overload `&&', `||', or `,'. ! ! This option also enables `-Wnon-virtual-dtor', which is also one ! of the effective C++ recommendations. However, the check is ! extended to warn about the lack of virtual destructor in accessible non-polymorphic bases classes too. When selecting this option, be aware that the standard library ! headers do not obey all of these guidelines; use `grep -v' to filter out those warnings. ! `-Wstrict-null-sentinel (C++ and Objective-C++ only)' ! Warn about the use of an uncasted `NULL' as sentinel. When ! compiling only with GCC this is a valid sentinel, as `NULL' is ! defined to `__null'. Although it is a null pointer constant ! rather than a null pointer, it is guaranteed to be of the same ! size as a pointer. But this use is not portable across different ! compilers. ! `-Wno-non-template-friend (C++ and Objective-C++ only)' Disable warnings when non-templatized friend functions are declared within a template. Since the advent of explicit template specification support in G++, if the name of the friend is an ! unqualified-id (i.e., `friend foo(int)'), the C++ language specification demands that the friend declare or define an ordinary, nontemplate function. (Section 14.5.3). Before G++ implemented explicit specification, unqualified-ids could be interpreted as a particular specialization of a templatized function. Because this non-conforming behavior is no longer the ! default behavior for G++, `-Wnon-template-friend' allows the compiler to check existing code for potential trouble spots and is on by default. This new compiler behavior can be turned off with ! `-Wno-non-template-friend', which keeps the conformant compiler code but disables the helpful warning. ! `-Wold-style-cast (C++ and Objective-C++ only)' Warn if an old-style (C-style) cast to a non-void type is used ! within a C++ program. The new-style casts (`dynamic_cast', ! `static_cast', `reinterpret_cast', and `const_cast') are less vulnerable to unintended effects and much easier to search for. ! `-Woverloaded-virtual (C++ and Objective-C++ only)' Warn when a function declaration hides virtual functions from a base class. For example, in: *************** have meanings only for C++ programs: *** 3003,3056 **** void f(int); }; ! the 'A' class version of 'f' is hidden in 'B', and code like: B* b; b->f(); fails to compile. ! '-Wno-pmf-conversions (C++ and Objective-C++ only)' Disable the diagnostic for converting a bound pointer to member function to a plain pointer. ! '-Wsign-promo (C++ and Objective-C++ only)' Warn when overload resolution chooses a promotion from unsigned or enumerated type to a signed type, over a conversion to an unsigned type of the same size. Previous versions of G++ tried to preserve unsignedness, but the standard mandates the current behavior. ! '-Wtemplates (C++ and Objective-C++ only)' Warn when a primary template declaration is encountered. Some coding rules disallow templates, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the STL, so one can still use the STL. One may also instantiate or specialize templates. ! '-Wmultiple-inheritance (C++ and Objective-C++ only)' Warn when a class is defined with multiple direct base classes. Some coding rules disallow multiple inheritance, and this may be ! used to enforce that rule. The warning is inactive inside a system ! header file, such as the STL, so one can still use the STL. One may ! also define classes that indirectly use multiple inheritance. ! '-Wvirtual-inheritance' Warn when a class is defined with a virtual direct base classe. Some coding rules disallow multiple inheritance, and this may be ! used to enforce that rule. The warning is inactive inside a system ! header file, such as the STL, so one can still use the STL. One may ! also define classes that indirectly use virtual inheritance. ! '-Wnamespaces' Warn when a namespace definition is opened. Some coding rules disallow namespaces, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the ! STL, so one can still use the STL. One may also use using directives and qualified names. ! '-Wno-terminate (C++ and Objective-C++ only)' Disable the warning about a throw-expression that will immediately ! result in a call to 'terminate'.  File: gcc.info, Node: Objective-C and Objective-C++ Dialect Options, Next: Diagnostic Message Formatting Options, Prev: C++ Dialect Options, Up: Invoking GCC --- 3018,3073 ---- void f(int); }; ! the `A' class version of `f' is hidden in `B', and code like: B* b; b->f(); fails to compile. ! `-Wno-pmf-conversions (C++ and Objective-C++ only)' Disable the diagnostic for converting a bound pointer to member function to a plain pointer. ! `-Wsign-promo (C++ and Objective-C++ only)' Warn when overload resolution chooses a promotion from unsigned or enumerated type to a signed type, over a conversion to an unsigned type of the same size. Previous versions of G++ tried to preserve unsignedness, but the standard mandates the current behavior. ! `-Wtemplates (C++ and Objective-C++ only)' Warn when a primary template declaration is encountered. Some coding rules disallow templates, and this may be used to enforce that rule. The warning is inactive inside a system header file, ! such as the STL, so one can still use the STL. One may also instantiate or specialize templates. ! `-Wmultiple-inheritance (C++ and Objective-C++ only)' Warn when a class is defined with multiple direct base classes. Some coding rules disallow multiple inheritance, and this may be ! used to enforce that rule. The warning is inactive inside a ! system header file, such as the STL, so one can still use the STL. ! One may also define classes that indirectly use multiple ! inheritance. ! `-Wvirtual-inheritance' Warn when a class is defined with a virtual direct base classe. Some coding rules disallow multiple inheritance, and this may be ! used to enforce that rule. The warning is inactive inside a ! system header file, such as the STL, so one can still use the STL. ! One may also define classes that indirectly use virtual ! inheritance. ! `-Wnamespaces' Warn when a namespace definition is opened. Some coding rules disallow namespaces, and this may be used to enforce that rule. The warning is inactive inside a system header file, such as the ! STL, so one can still use the STL. One may also use using directives and qualified names. ! `-Wno-terminate (C++ and Objective-C++ only)' Disable the warning about a throw-expression that will immediately ! result in a call to `terminate'.  File: gcc.info, Node: Objective-C and Objective-C++ Dialect Options, Next: Diagnostic Message Formatting Options, Prev: C++ Dialect Options, Up: Invoking GCC *************** languages themselves. *Note Language St *** 3063,3277 **** Standards, for references.) This section describes the command-line options that are only ! meaningful for Objective-C and Objective-C++ programs. You can also use ! most of the language-independent GNU compiler options. For example, you ! might compile a file 'some_class.m' like this: gcc -g -fgnu-runtime -O -c some_class.m ! In this example, '-fgnu-runtime' is an option meant only for Objective-C ! and Objective-C++ programs; you can use the other options with any ! language supported by GCC. Note that since Objective-C is an extension of the C language, Objective-C compilations may also use options specific to the C ! front-end (e.g., '-Wtraditional'). Similarly, Objective-C++ ! compilations may use C++-specific options (e.g., '-Wabi'). ! Here is a list of options that are _only_ for compiling Objective-C and ! Objective-C++ programs: ! '-fconstant-string-class=CLASS-NAME' Use CLASS-NAME as the name of the class to instantiate for each ! literal string specified with the syntax '@"..."'. The default ! class name is 'NXConstantString' if the GNU runtime is being used, ! and 'NSConstantString' if the NeXT runtime is being used (see ! below). The '-fconstant-cfstrings' option, if also present, ! overrides the '-fconstant-string-class' setting and cause '@"..."' literals to be laid out as constant CoreFoundation strings. ! '-fgnu-runtime' Generate object code compatible with the standard GNU Objective-C runtime. This is the default for most types of systems. ! '-fnext-runtime' Generate output compatible with the NeXT runtime. This is the ! default for NeXT-based systems, including Darwin and Mac OS X. The ! macro '__NEXT_RUNTIME__' is predefined if (and only if) this option ! is used. ! '-fno-nil-receivers' ! Assume that all Objective-C message dispatches ('[receiver message:arg]') in this translation unit ensure that the receiver is ! not 'nil'. This allows for more efficient entry points in the runtime to be used. This option is only available in conjunction with the NeXT runtime and ABI version 0 or 1. ! '-fobjc-abi-version=N' Use version N of the Objective-C ABI for the selected runtime. This option is currently supported only for the NeXT runtime. In that case, Version 0 is the traditional (32-bit) ABI without support for properties and other Objective-C 2.0 additions. Version 1 is the traditional (32-bit) ABI with support for properties and other Objective-C 2.0 additions. Version 2 is the ! modern (64-bit) ABI. If nothing is specified, the default is ! Version 0 on 32-bit target machines, and Version 2 on 64-bit target ! machines. ! '-fobjc-call-cxx-cdtors' For each Objective-C class, check if any of its instance variables is a C++ object with a non-trivial default constructor. If so, ! synthesize a special '- (id) .cxx_construct' instance method which runs non-trivial default constructors on any such instance ! variables, in order, and then return 'self'. Similarly, check if any instance variable is a C++ object with a non-trivial ! destructor, and if so, synthesize a special '- (void) .cxx_destruct' method which runs all such default destructors, in reverse order. ! The '- (id) .cxx_construct' and '- (void) .cxx_destruct' methods ! thusly generated only operate on instance variables declared in the ! current Objective-C class, and not those inherited from superclasses. It is the responsibility of the Objective-C runtime to invoke all such methods in an object's inheritance hierarchy. ! The '- (id) .cxx_construct' methods are invoked by the runtime ! immediately after a new object instance is allocated; the '- (void) ! .cxx_destruct' methods are invoked immediately before the runtime ! deallocates an object instance. As of this writing, only the NeXT runtime on Mac OS X 10.4 and ! later has support for invoking the '- (id) .cxx_construct' and '- (void) .cxx_destruct' methods. ! '-fobjc-direct-dispatch' Allow fast jumps to the message dispatcher. On Darwin this is accomplished via the comm page. ! '-fobjc-exceptions' Enable syntactic support for structured exception handling in Objective-C, similar to what is offered by C++ and Java. This ! option is required to use the Objective-C keywords '@try', ! '@throw', '@catch', '@finally' and '@synchronized'. This option is ! available with both the GNU runtime and the NeXT runtime (but not ! available in conjunction with the NeXT runtime on Mac OS X 10.2 and ! earlier). ! '-fobjc-gc' Enable garbage collection (GC) in Objective-C and Objective-C++ programs. This option is only available with the NeXT runtime; the GNU runtime has a different garbage collection implementation that does not require special compiler flags. ! '-fobjc-nilcheck' For the NeXT runtime with version 2 of the ABI, check for a nil receiver in method invocations before doing the actual method call. ! This is the default and can be disabled using '-fno-objc-nilcheck'. ! Class methods and super calls are never checked for nil in this way ! no matter what this flag is set to. Currently this flag does ! nothing when the GNU runtime, or an older version of the NeXT ! runtime ABI, is used. ! '-fobjc-std=objc1' Conform to the language syntax of Objective-C 1.0, the language ! recognized by GCC 4.0. This only affects the Objective-C additions ! to the C/C++ language; it does not affect conformance to C/C++ ! standards, which is controlled by the separate C/C++ dialect option ! flags. When this option is used with the Objective-C or Objective-C++ compiler, any Objective-C syntax that is not recognized by GCC 4.0 is rejected. This is useful if you need to make sure that your Objective-C code can be compiled with older versions of GCC. ! '-freplace-objc-classes' ! Emit a special marker instructing 'ld(1)' not to statically link in ! the resulting object file, and allow 'dyld(1)' to load it in at run ! time instead. This is used in conjunction with the Fix-and-Continue debugging mode, where the object file in question ! may be recompiled and dynamically reloaded in the course of program ! execution, without the need to restart the program itself. Currently, Fix-and-Continue functionality is only available in conjunction with the NeXT runtime on Mac OS X 10.3 and later. ! '-fzero-link' When compiling for the NeXT runtime, the compiler ordinarily ! replaces calls to 'objc_getClass("...")' (when the name of the class is known at compile time) with static class references that get initialized at load time, which improves run-time performance. ! Specifying the '-fzero-link' flag suppresses this behavior and ! causes calls to 'objc_getClass("...")' to be retained. This is useful in Zero-Link debugging mode, since it allows for individual ! class implementations to be modified during program execution. The ! GNU runtime currently always retains calls to ! 'objc_get_class("...")' regardless of command-line options. ! '-fno-local-ivars' By default instance variables in Objective-C can be accessed as if they were local variables from within the methods of the class they're declared in. This can lead to shadowing between instance variables and other variables declared either locally inside a class method or globally with the same name. Specifying the ! '-fno-local-ivars' flag disables this behavior thus avoiding variable shadowing issues. ! '-fivar-visibility=[public|protected|private|package]' Set the default instance variable visibility to the specified ! option so that instance variables declared outside the scope of any ! access modifier directives default to the specified visibility. ! '-gen-decls' ! Dump interface declarations for all classes seen in the source file ! to a file named 'SOURCENAME.decl'. ! '-Wassign-intercept (Objective-C and Objective-C++ only)' Warn whenever an Objective-C assignment is being intercepted by the garbage collector. ! '-Wno-protocol (Objective-C and Objective-C++ only)' ! If a class is declared to implement a protocol, a warning is issued ! for every method in the protocol that is not implemented by the ! class. The default behavior is to issue a warning for every method ! not explicitly implemented in the class, even if a method implementation is inherited from the superclass. If you use the ! '-Wno-protocol' option, then methods inherited from the superclass are considered to be implemented, and no warning is issued for them. ! '-Wselector (Objective-C and Objective-C++ only)' Warn if multiple methods of different types for the same selector are found during compilation. The check is performed on the list of methods in the final stage of compilation. Additionally, a check is performed for each selector appearing in a ! '@selector(...)' expression, and a corresponding method for that selector has been found during compilation. Because these checks scan the method table only at the end of compilation, these warnings are not produced if the final stage of compilation is not reached, for example because an error is found during compilation, ! or because the '-fsyntax-only' option is being used. ! '-Wstrict-selector-match (Objective-C and Objective-C++ only)' Warn if multiple methods with differing argument and/or return types are found for a given selector when attempting to send a ! message using this selector to a receiver of type 'id' or 'Class'. ! When this flag is off (which is the default behavior), the compiler ! omits such warnings if any differences found are confined to types ! that share the same size and alignment. ! '-Wundeclared-selector (Objective-C and Objective-C++ only)' ! Warn if a '@selector(...)' expression referring to an undeclared selector is found. A selector is considered undeclared if no ! method with that name has been declared before the '@selector(...)' ! expression, either explicitly in an '@interface' or '@protocol' ! declaration, or implicitly in an '@implementation' section. This ! option always performs its checks as soon as a '@selector(...)' ! expression is found, while '-Wselector' only performs its checks in ! the final stage of compilation. This also enforces the coding ! style convention that methods and selectors must be declared before ! being used. ! '-print-objc-runtime-info' Generate C header describing the largest structure that is passed by value, if any.  File: gcc.info, Node: Diagnostic Message Formatting Options, Next: Warning Options, Prev: Objective-C and Objective-C++ Dialect Options, Up: Invoking GCC --- 3080,3295 ---- Standards, for references.) This section describes the command-line options that are only ! meaningful for Objective-C and Objective-C++ programs. You can also ! use most of the language-independent GNU compiler options. For ! example, you might compile a file `some_class.m' like this: gcc -g -fgnu-runtime -O -c some_class.m ! In this example, `-fgnu-runtime' is an option meant only for ! Objective-C and Objective-C++ programs; you can use the other options ! with any language supported by GCC. Note that since Objective-C is an extension of the C language, Objective-C compilations may also use options specific to the C ! front-end (e.g., `-Wtraditional'). Similarly, Objective-C++ ! compilations may use C++-specific options (e.g., `-Wabi'). ! Here is a list of options that are _only_ for compiling Objective-C ! and Objective-C++ programs: ! `-fconstant-string-class=CLASS-NAME' Use CLASS-NAME as the name of the class to instantiate for each ! literal string specified with the syntax `@"..."'. The default ! class name is `NXConstantString' if the GNU runtime is being used, ! and `NSConstantString' if the NeXT runtime is being used (see ! below). The `-fconstant-cfstrings' option, if also present, ! overrides the `-fconstant-string-class' setting and cause `@"..."' literals to be laid out as constant CoreFoundation strings. ! `-fgnu-runtime' Generate object code compatible with the standard GNU Objective-C runtime. This is the default for most types of systems. ! `-fnext-runtime' Generate output compatible with the NeXT runtime. This is the ! default for NeXT-based systems, including Darwin and Mac OS X. ! The macro `__NEXT_RUNTIME__' is predefined if (and only if) this ! option is used. ! `-fno-nil-receivers' ! Assume that all Objective-C message dispatches (`[receiver message:arg]') in this translation unit ensure that the receiver is ! not `nil'. This allows for more efficient entry points in the runtime to be used. This option is only available in conjunction with the NeXT runtime and ABI version 0 or 1. ! `-fobjc-abi-version=N' Use version N of the Objective-C ABI for the selected runtime. This option is currently supported only for the NeXT runtime. In that case, Version 0 is the traditional (32-bit) ABI without support for properties and other Objective-C 2.0 additions. Version 1 is the traditional (32-bit) ABI with support for properties and other Objective-C 2.0 additions. Version 2 is the ! modern (64-bit) ABI. If nothing is specified, the default is ! Version 0 on 32-bit target machines, and Version 2 on 64-bit ! target machines. ! `-fobjc-call-cxx-cdtors' For each Objective-C class, check if any of its instance variables is a C++ object with a non-trivial default constructor. If so, ! synthesize a special `- (id) .cxx_construct' instance method which runs non-trivial default constructors on any such instance ! variables, in order, and then return `self'. Similarly, check if any instance variable is a C++ object with a non-trivial ! destructor, and if so, synthesize a special `- (void) .cxx_destruct' method which runs all such default destructors, in reverse order. ! The `- (id) .cxx_construct' and `- (void) .cxx_destruct' methods ! thusly generated only operate on instance variables declared in ! the current Objective-C class, and not those inherited from superclasses. It is the responsibility of the Objective-C runtime to invoke all such methods in an object's inheritance hierarchy. ! The `- (id) .cxx_construct' methods are invoked by the runtime ! immediately after a new object instance is allocated; the `- ! (void) .cxx_destruct' methods are invoked immediately before the ! runtime deallocates an object instance. As of this writing, only the NeXT runtime on Mac OS X 10.4 and ! later has support for invoking the `- (id) .cxx_construct' and `- (void) .cxx_destruct' methods. ! `-fobjc-direct-dispatch' Allow fast jumps to the message dispatcher. On Darwin this is accomplished via the comm page. ! `-fobjc-exceptions' Enable syntactic support for structured exception handling in Objective-C, similar to what is offered by C++ and Java. This ! option is required to use the Objective-C keywords `@try', ! `@throw', `@catch', `@finally' and `@synchronized'. This option ! is available with both the GNU runtime and the NeXT runtime (but ! not available in conjunction with the NeXT runtime on Mac OS X ! 10.2 and earlier). ! `-fobjc-gc' Enable garbage collection (GC) in Objective-C and Objective-C++ programs. This option is only available with the NeXT runtime; the GNU runtime has a different garbage collection implementation that does not require special compiler flags. ! `-fobjc-nilcheck' For the NeXT runtime with version 2 of the ABI, check for a nil receiver in method invocations before doing the actual method call. ! This is the default and can be disabled using ! `-fno-objc-nilcheck'. Class methods and super calls are never ! checked for nil in this way no matter what this flag is set to. ! Currently this flag does nothing when the GNU runtime, or an older ! version of the NeXT runtime ABI, is used. ! `-fobjc-std=objc1' Conform to the language syntax of Objective-C 1.0, the language ! recognized by GCC 4.0. This only affects the Objective-C ! additions to the C/C++ language; it does not affect conformance to ! C/C++ standards, which is controlled by the separate C/C++ dialect ! option flags. When this option is used with the Objective-C or Objective-C++ compiler, any Objective-C syntax that is not recognized by GCC 4.0 is rejected. This is useful if you need to make sure that your Objective-C code can be compiled with older versions of GCC. ! `-freplace-objc-classes' ! Emit a special marker instructing `ld(1)' not to statically link in ! the resulting object file, and allow `dyld(1)' to load it in at ! run time instead. This is used in conjunction with the Fix-and-Continue debugging mode, where the object file in question ! may be recompiled and dynamically reloaded in the course of ! program execution, without the need to restart the program itself. Currently, Fix-and-Continue functionality is only available in conjunction with the NeXT runtime on Mac OS X 10.3 and later. ! `-fzero-link' When compiling for the NeXT runtime, the compiler ordinarily ! replaces calls to `objc_getClass("...")' (when the name of the class is known at compile time) with static class references that get initialized at load time, which improves run-time performance. ! Specifying the `-fzero-link' flag suppresses this behavior and ! causes calls to `objc_getClass("...")' to be retained. This is useful in Zero-Link debugging mode, since it allows for individual ! class implementations to be modified during program execution. ! The GNU runtime currently always retains calls to ! `objc_get_class("...")' regardless of command-line options. ! `-fno-local-ivars' By default instance variables in Objective-C can be accessed as if they were local variables from within the methods of the class they're declared in. This can lead to shadowing between instance variables and other variables declared either locally inside a class method or globally with the same name. Specifying the ! `-fno-local-ivars' flag disables this behavior thus avoiding variable shadowing issues. ! `-fivar-visibility=[public|protected|private|package]' Set the default instance variable visibility to the specified ! option so that instance variables declared outside the scope of ! any access modifier directives default to the specified visibility. ! `-gen-decls' ! Dump interface declarations for all classes seen in the source ! file to a file named `SOURCENAME.decl'. ! `-Wassign-intercept (Objective-C and Objective-C++ only)' Warn whenever an Objective-C assignment is being intercepted by the garbage collector. ! `-Wno-protocol (Objective-C and Objective-C++ only)' ! If a class is declared to implement a protocol, a warning is ! issued for every method in the protocol that is not implemented by ! the class. The default behavior is to issue a warning for every ! method not explicitly implemented in the class, even if a method implementation is inherited from the superclass. If you use the ! `-Wno-protocol' option, then methods inherited from the superclass are considered to be implemented, and no warning is issued for them. ! `-Wselector (Objective-C and Objective-C++ only)' Warn if multiple methods of different types for the same selector are found during compilation. The check is performed on the list of methods in the final stage of compilation. Additionally, a check is performed for each selector appearing in a ! `@selector(...)' expression, and a corresponding method for that selector has been found during compilation. Because these checks scan the method table only at the end of compilation, these warnings are not produced if the final stage of compilation is not reached, for example because an error is found during compilation, ! or because the `-fsyntax-only' option is being used. ! `-Wstrict-selector-match (Objective-C and Objective-C++ only)' Warn if multiple methods with differing argument and/or return types are found for a given selector when attempting to send a ! message using this selector to a receiver of type `id' or `Class'. ! When this flag is off (which is the default behavior), the ! compiler omits such warnings if any differences found are confined ! to types that share the same size and alignment. ! `-Wundeclared-selector (Objective-C and Objective-C++ only)' ! Warn if a `@selector(...)' expression referring to an undeclared selector is found. A selector is considered undeclared if no ! method with that name has been declared before the ! `@selector(...)' expression, either explicitly in an `@interface' ! or `@protocol' declaration, or implicitly in an `@implementation' ! section. This option always performs its checks as soon as a ! `@selector(...)' expression is found, while `-Wselector' only ! performs its checks in the final stage of compilation. This also ! enforces the coding style convention that methods and selectors ! must be declared before being used. ! `-print-objc-runtime-info' Generate C header describing the largest structure that is passed by value, if any. +  File: gcc.info, Node: Diagnostic Message Formatting Options, Next: Warning Options, Prev: Objective-C and Objective-C++ Dialect Options, Up: Invoking GCC *************** File: gcc.info, Node: Diagnostic Messag *** 3281,3378 **** Traditionally, diagnostic messages have been formatted irrespective of the output device's aspect (e.g. its width, ...). You can use the options described below to control the formatting algorithm for ! diagnostic messages, e.g. how many characters per line, how often source ! location information should be reported. Note that some language front ! ends may not honor these options. ! '-fmessage-length=N' Try to format error messages so that they fit on lines of about N characters. If N is zero, then no line-wrapping is done; each error message appears on a single line. This is the default for all front ends. ! '-fdiagnostics-show-location=once' Only meaningful in line-wrapping mode. Instructs the diagnostic messages reporter to emit source location information _once_; that is, in case the message is too long to fit on a single physical line and has to be wrapped, the source location won't be emitted ! (as prefix) again, over and over, in subsequent continuation lines. ! This is the default behavior. ! '-fdiagnostics-show-location=every-line' Only meaningful in line-wrapping mode. Instructs the diagnostic messages reporter to emit the same source location information (as prefix) for physical lines that result from the process of breaking a message which is too long to fit on a single line. ! '-fdiagnostics-color[=WHEN]' ! '-fno-diagnostics-color' ! Use color in diagnostics. WHEN is 'never', 'always', or 'auto'. ! The default depends on how the compiler has been configured, it can ! be any of the above WHEN options or also 'never' if 'GCC_COLORS' ! environment variable isn't present in the environment, and 'auto' ! otherwise. 'auto' means to use color only when the standard error ! is a terminal. The forms '-fdiagnostics-color' and ! '-fno-diagnostics-color' are aliases for ! '-fdiagnostics-color=always' and '-fdiagnostics-color=never', respectively. ! The colors are defined by the environment variable 'GCC_COLORS'. Its value is a colon-separated list of capabilities and Select ! Graphic Rendition (SGR) substrings. SGR commands are interpreted by the terminal or terminal emulator. (See the section in the documentation of your text terminal for permitted values and their meanings as character attributes.) These substring values are integers in decimal representation and can be concatenated with ! semicolons. Common values to concatenate include '1' for bold, '4' ! for underline, '5' for blink, '7' for inverse, '39' for default ! foreground color, '30' to '37' for foreground colors, '90' to '97' ! for 16-color mode foreground colors, '38;5;0' to '38;5;255' for ! 88-color and 256-color modes foreground colors, '49' for default ! background color, '40' to '47' for background colors, '100' to ! '107' for 16-color mode background colors, and '48;5;0' to ! '48;5;255' for 88-color and 256-color modes background colors. ! The default 'GCC_COLORS' is error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01 ! where '01;31' is bold red, '01;35' is bold magenta, '01;36' is bold ! cyan, '01;32' is bold green and '01' is bold. Setting 'GCC_COLORS' ! to the empty string disables colors. Supported capabilities are as ! follows. ! 'error=' SGR substring for error: markers. ! 'warning=' SGR substring for warning: markers. ! 'note=' SGR substring for note: markers. ! 'caret=' SGR substring for caret line. ! 'locus=' ! SGR substring for location information, 'file:line' or ! 'file:line:column' etc. ! 'quote=' SGR substring for information printed within quotes. ! '-fno-diagnostics-show-option' By default, each diagnostic emitted includes text indicating the command-line option that directly controls the diagnostic (if such an option is known to the diagnostic machinery). Specifying the ! '-fno-diagnostics-show-option' flag suppresses that behavior. ! '-fno-diagnostics-show-caret' By default, each diagnostic emitted includes the original source ! line and a caret '^' indicating the column. This option suppresses ! this information. The source line is truncated to N characters, if ! the '-fmessage-length=n' option is given. When the output is done ! to the terminal, the width is limited to the width given by the ! 'COLUMNS' environment variable or, if not set, to the terminal ! width.  File: gcc.info, Node: Warning Options, Next: Debugging Options, Prev: Diagnostic Message Formatting Options, Up: Invoking GCC --- 3299,3397 ---- Traditionally, diagnostic messages have been formatted irrespective of the output device's aspect (e.g. its width, ...). You can use the options described below to control the formatting algorithm for ! diagnostic messages, e.g. how many characters per line, how often ! source location information should be reported. Note that some ! language front ends may not honor these options. ! `-fmessage-length=N' Try to format error messages so that they fit on lines of about N characters. If N is zero, then no line-wrapping is done; each error message appears on a single line. This is the default for all front ends. ! `-fdiagnostics-show-location=once' Only meaningful in line-wrapping mode. Instructs the diagnostic messages reporter to emit source location information _once_; that is, in case the message is too long to fit on a single physical line and has to be wrapped, the source location won't be emitted ! (as prefix) again, over and over, in subsequent continuation ! lines. This is the default behavior. ! `-fdiagnostics-show-location=every-line' Only meaningful in line-wrapping mode. Instructs the diagnostic messages reporter to emit the same source location information (as prefix) for physical lines that result from the process of breaking a message which is too long to fit on a single line. ! `-fdiagnostics-color[=WHEN]' ! `-fno-diagnostics-color' ! Use color in diagnostics. WHEN is `never', `always', or `auto'. ! The default depends on how the compiler has been configured, it ! can be any of the above WHEN options or also `never' if ! `GCC_COLORS' environment variable isn't present in the environment, ! and `auto' otherwise. `auto' means to use color only when the ! standard error is a terminal. The forms `-fdiagnostics-color' and ! `-fno-diagnostics-color' are aliases for ! `-fdiagnostics-color=always' and `-fdiagnostics-color=never', respectively. ! The colors are defined by the environment variable `GCC_COLORS'. Its value is a colon-separated list of capabilities and Select ! Graphic Rendition (SGR) substrings. SGR commands are interpreted by the terminal or terminal emulator. (See the section in the documentation of your text terminal for permitted values and their meanings as character attributes.) These substring values are integers in decimal representation and can be concatenated with ! semicolons. Common values to concatenate include `1' for bold, ! `4' for underline, `5' for blink, `7' for inverse, `39' for ! default foreground color, `30' to `37' for foreground colors, `90' ! to `97' for 16-color mode foreground colors, `38;5;0' to `38;5;255' ! for 88-color and 256-color modes foreground colors, `49' for ! default background color, `40' to `47' for background colors, ! `100' to `107' for 16-color mode background colors, and `48;5;0' ! to `48;5;255' for 88-color and 256-color modes background colors. ! The default `GCC_COLORS' is error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01 ! where `01;31' is bold red, `01;35' is bold magenta, `01;36' is ! bold cyan, `01;32' is bold green and `01' is bold. Setting ! `GCC_COLORS' to the empty string disables colors. Supported ! capabilities are as follows. ! `error=' SGR substring for error: markers. ! `warning=' SGR substring for warning: markers. ! `note=' SGR substring for note: markers. ! `caret=' SGR substring for caret line. ! `locus=' ! SGR substring for location information, `file:line' or ! `file:line:column' etc. ! `quote=' SGR substring for information printed within quotes. ! `-fno-diagnostics-show-option' By default, each diagnostic emitted includes text indicating the command-line option that directly controls the diagnostic (if such an option is known to the diagnostic machinery). Specifying the ! `-fno-diagnostics-show-option' flag suppresses that behavior. ! `-fno-diagnostics-show-caret' By default, each diagnostic emitted includes the original source ! line and a caret `^' indicating the column. This option ! suppresses this information. The source line is truncated to N ! characters, if the `-fmessage-length=n' option is given. When the ! output is done to the terminal, the width is limited to the width ! given by the `COLUMNS' environment variable or, if not set, to the ! terminal width. !  File: gcc.info, Node: Warning Options, Next: Debugging Options, Prev: Diagnostic Message Formatting Options, Up: Invoking GCC *************** an error. *** 3387,3509 **** The following language-independent options do not enable specific warnings but control the kinds of diagnostics produced by GCC. ! '-fsyntax-only' Check the code for syntax errors, but don't do anything beyond that. ! '-fmax-errors=N' Limits the maximum number of error messages to N, at which point GCC bails out rather than attempting to continue processing the source code. If N is 0 (the default), there is no limit on the ! number of error messages produced. If '-Wfatal-errors' is also ! specified, then '-Wfatal-errors' takes precedence over this option. ! '-w' Inhibit all warning messages. ! '-Werror' Make all warnings into errors. ! '-Werror=' Make the specified warning into an error. The specifier for a ! warning is appended; for example '-Werror=switch' turns the ! warnings controlled by '-Wswitch' into errors. This switch takes a ! negative form, to be used to negate '-Werror' for specific ! warnings; for example '-Wno-error=switch' makes '-Wswitch' warnings ! not be errors, even when '-Werror' is in effect. The warning message for each controllable warning includes the option that controls the warning. That option can then be used ! with '-Werror=' and '-Wno-error=' as described above. (Printing of ! the option in the warning message can be disabled using the ! '-fno-diagnostics-show-option' flag.) ! Note that specifying '-Werror='FOO automatically implies '-W'FOO. ! However, '-Wno-error='FOO does not imply anything. ! '-Wfatal-errors' This option causes the compiler to abort compilation on the first error occurred rather than trying to keep going and printing further error messages. You can request many specific warnings with options beginning with ! '-W', for example '-Wimplicit' to request warnings on implicit declarations. Each of these specific warning options also has a ! negative form beginning '-Wno-' to turn off warnings; for example, ! '-Wno-implicit'. This manual lists only one of the two forms, whichever ! is not the default. For further language-specific options also refer to ! *note C++ Dialect Options:: and *note Objective-C and Objective-C++ ! Dialect Options::. ! Some options, such as '-Wall' and '-Wextra', turn on other options, ! such as '-Wunused', which may turn on further options, such as ! '-Wunused-value'. The combined effect of positive and negative forms is that more specific options have priority over less specific ones, ! independently of their position in the command-line. For options of the ! same specificity, the last one takes effect. Options enabled or ! disabled via pragmas (*note Diagnostic Pragmas::) take effect as if they ! appeared at the end of the command-line. When an unrecognized warning option is requested (e.g., ! '-Wunknown-warning'), GCC emits a diagnostic stating that the option is ! not recognized. However, if the '-Wno-' form is used, the behavior is ! slightly different: no diagnostic is produced for '-Wno-unknown-warning' ! unless other diagnostics are being produced. This allows the use of new ! '-Wno-' options with old compilers, but if something goes wrong, the ! compiler warns that an unrecognized option is present. ! '-Wpedantic' ! '-pedantic' ! Issue all the warnings demanded by strict ISO C and ISO C++; reject ! all programs that use forbidden extensions, and some other programs ! that do not follow ISO C and ISO C++. For ISO C, follows the ! version of the ISO C standard specified by any '-std' option used. Valid ISO C and ISO C++ programs should compile properly with or ! without this option (though a rare few require '-ansi' or a '-std' ! option specifying the required version of ISO C). However, without ! this option, certain GNU extensions and traditional C and C++ ! features are supported as well. With this option, they are rejected. ! '-Wpedantic' does not cause warning messages for use of the ! alternate keywords whose names begin and end with '__'. Pedantic warnings are also disabled in the expression that follows ! '__extension__'. However, only system header files should use ! these escape routes; application programs should avoid them. *Note ! Alternate Keywords::. ! Some users try to use '-Wpedantic' to check programs for strict ISO C conformance. They soon find that it does not do quite what they want: it finds some non-ISO practices, but not all--only those for which ISO C _requires_ a diagnostic, and some others for which diagnostics have been added. ! A feature to report any failure to conform to ISO C might be useful ! in some instances, but would require considerable additional work ! and would be quite different from '-Wpedantic'. We don't have ! plans to support such a feature in the near future. ! Where the standard specified with '-std' represents a GNU extended ! dialect of C, such as 'gnu90' or 'gnu99', there is a corresponding "base standard", the version of ISO C on which the GNU extended ! dialect is based. Warnings from '-Wpedantic' are given where they are required by the base standard. (It does not make sense for such warnings to be given only for features not in the specified GNU C dialect, since by definition the GNU dialects of C include ! all features the compiler supports with the given option, and there ! would be nothing to warn about.) ! '-pedantic-errors' ! Give an error whenever the "base standard" (see '-Wpedantic') requires a diagnostic, in some cases where there is undefined behavior at compile-time and in some other cases that do not prevent compilation of programs that are valid according to the ! standard. This is not equivalent to '-Werror=pedantic', since there are errors enabled by this option and not enabled by the latter and vice versa. ! '-Wall' This enables all the warnings about constructions that some users consider questionable, and that are easy to avoid (or modify to prevent the warning), even in conjunction with macros. This also --- 3406,3531 ---- The following language-independent options do not enable specific warnings but control the kinds of diagnostics produced by GCC. ! `-fsyntax-only' Check the code for syntax errors, but don't do anything beyond that. ! `-fmax-errors=N' Limits the maximum number of error messages to N, at which point GCC bails out rather than attempting to continue processing the source code. If N is 0 (the default), there is no limit on the ! number of error messages produced. If `-Wfatal-errors' is also ! specified, then `-Wfatal-errors' takes precedence over this option. ! `-w' Inhibit all warning messages. ! `-Werror' Make all warnings into errors. ! `-Werror=' Make the specified warning into an error. The specifier for a ! warning is appended; for example `-Werror=switch' turns the ! warnings controlled by `-Wswitch' into errors. This switch takes a ! negative form, to be used to negate `-Werror' for specific ! warnings; for example `-Wno-error=switch' makes `-Wswitch' ! warnings not be errors, even when `-Werror' is in effect. The warning message for each controllable warning includes the option that controls the warning. That option can then be used ! with `-Werror=' and `-Wno-error=' as described above. (Printing ! of the option in the warning message can be disabled using the ! `-fno-diagnostics-show-option' flag.) ! Note that specifying `-Werror='FOO automatically implies `-W'FOO. ! However, `-Wno-error='FOO does not imply anything. ! `-Wfatal-errors' This option causes the compiler to abort compilation on the first error occurred rather than trying to keep going and printing further error messages. + You can request many specific warnings with options beginning with ! `-W', for example `-Wimplicit' to request warnings on implicit declarations. Each of these specific warning options also has a ! negative form beginning `-Wno-' to turn off warnings; for example, ! `-Wno-implicit'. This manual lists only one of the two forms, ! whichever is not the default. For further language-specific options ! also refer to *note C++ Dialect Options:: and *note Objective-C and ! Objective-C++ Dialect Options::. ! Some options, such as `-Wall' and `-Wextra', turn on other options, ! such as `-Wunused', which may turn on further options, such as ! `-Wunused-value'. The combined effect of positive and negative forms is that more specific options have priority over less specific ones, ! independently of their position in the command-line. For options of the ! same specificity, the last one takes effect. Options enabled or ! disabled via pragmas (*note Diagnostic Pragmas::) take effect as if ! they appeared at the end of the command-line. When an unrecognized warning option is requested (e.g., ! `-Wunknown-warning'), GCC emits a diagnostic stating that the option is ! not recognized. However, if the `-Wno-' form is used, the behavior is ! slightly different: no diagnostic is produced for ! `-Wno-unknown-warning' unless other diagnostics are being produced. ! This allows the use of new `-Wno-' options with old compilers, but if ! something goes wrong, the compiler warns that an unrecognized option is ! present. ! `-Wpedantic' ! `-pedantic' ! Issue all the warnings demanded by strict ISO C and ISO C++; ! reject all programs that use forbidden extensions, and some other ! programs that do not follow ISO C and ISO C++. For ISO C, follows ! the version of the ISO C standard specified by any `-std' option ! used. Valid ISO C and ISO C++ programs should compile properly with or ! without this option (though a rare few require `-ansi' or a `-std' ! option specifying the required version of ISO C). However, ! without this option, certain GNU extensions and traditional C and ! C++ features are supported as well. With this option, they are rejected. ! `-Wpedantic' does not cause warning messages for use of the ! alternate keywords whose names begin and end with `__'. Pedantic warnings are also disabled in the expression that follows ! `__extension__'. However, only system header files should use ! these escape routes; application programs should avoid them. ! *Note Alternate Keywords::. ! Some users try to use `-Wpedantic' to check programs for strict ISO C conformance. They soon find that it does not do quite what they want: it finds some non-ISO practices, but not all--only those for which ISO C _requires_ a diagnostic, and some others for which diagnostics have been added. ! A feature to report any failure to conform to ISO C might be ! useful in some instances, but would require considerable ! additional work and would be quite different from `-Wpedantic'. ! We don't have plans to support such a feature in the near future. ! Where the standard specified with `-std' represents a GNU extended ! dialect of C, such as `gnu90' or `gnu99', there is a corresponding "base standard", the version of ISO C on which the GNU extended ! dialect is based. Warnings from `-Wpedantic' are given where they are required by the base standard. (It does not make sense for such warnings to be given only for features not in the specified GNU C dialect, since by definition the GNU dialects of C include ! all features the compiler supports with the given option, and ! there would be nothing to warn about.) ! `-pedantic-errors' ! Give an error whenever the "base standard" (see `-Wpedantic') requires a diagnostic, in some cases where there is undefined behavior at compile-time and in some other cases that do not prevent compilation of programs that are valid according to the ! standard. This is not equivalent to `-Werror=pedantic', since there are errors enabled by this option and not enabled by the latter and vice versa. ! `-Wall' This enables all the warnings about constructions that some users consider questionable, and that are easy to avoid (or modify to prevent the warning), even in conjunction with macros. This also *************** compiler warns that an unrecognized opti *** 3511,3520 **** Dialect Options:: and *note Objective-C and Objective-C++ Dialect Options::. ! '-Wall' turns on the following warning flags: -Waddress ! -Warray-bounds=1 (only with -O2) -Wbool-compare -Wc++11-compat -Wc++14-compat -Wchar-subscripts --- 3533,3542 ---- Dialect Options:: and *note Objective-C and Objective-C++ Dialect Options::. ! `-Wall' turns on the following warning flags: -Waddress ! -Warray-bounds=1 (only with `-O2') -Wbool-compare -Wc++11-compat -Wc++14-compat -Wchar-subscripts *************** compiler warns that an unrecognized opti *** 3526,3532 **** -Wimplicit-function-declaration (C and Objective-C only) -Winit-self (only for C++) -Wlogical-not-parentheses ! -Wmain (only for C/ObjC and unless -ffreestanding) -Wmaybe-uninitialized -Wmemset-transposed-args -Wmisleading-indentation (only for C/C++) --- 3548,3554 ---- -Wimplicit-function-declaration (C and Objective-C only) -Winit-self (only for C++) -Wlogical-not-parentheses ! -Wmain (only for C/ObjC and unless `-ffreestanding') -Wmaybe-uninitialized -Wmemset-transposed-args -Wmisleading-indentation (only for C/C++) *************** compiler warns that an unrecognized opti *** 3555,3572 **** -Wunused-variable -Wvolatile-register-var ! ! Note that some warning flags are not implied by '-Wall'. Some of them warn about constructions that users generally do not consider questionable, but which occasionally you might wish to check for; ! others warn about constructions that are necessary or hard to avoid ! in some cases, and there is no simple way to modify the code to ! suppress the warning. Some of them are enabled by '-Wextra' but many of them must be enabled individually. ! '-Wextra' This enables some extra warning flags that are not enabled by ! '-Wall'. (This option used to be called '-W'. The older name is still supported, but the newer name is more descriptive.) -Wclobbered --- 3577,3593 ---- -Wunused-variable -Wvolatile-register-var ! Note that some warning flags are not implied by `-Wall'. Some of them warn about constructions that users generally do not consider questionable, but which occasionally you might wish to check for; ! others warn about constructions that are necessary or hard to ! avoid in some cases, and there is no simple way to modify the code ! to suppress the warning. Some of them are enabled by `-Wextra' but many of them must be enabled individually. ! `-Wextra' This enables some extra warning flags that are not enabled by ! `-Wall'. (This option used to be called `-W'. The older name is still supported, but the newer name is more descriptive.) -Wclobbered *************** compiler warns that an unrecognized opti *** 3580,3594 **** -Wtype-limits -Wuninitialized -Wshift-negative-value (in C++03 and in C99 and newer) ! -Wunused-parameter (only with -Wunused or -Wall) ! -Wunused-but-set-parameter (only with -Wunused or -Wall) ! ! The option '-Wextra' also prints warning messages for the following ! cases: ! * A pointer is compared against integer zero with '<', '<=', ! '>', or '>='. * (C++ only) An enumerator and a non-enumerator both appear in a conditional expression. --- 3601,3614 ---- -Wtype-limits -Wuninitialized -Wshift-negative-value (in C++03 and in C99 and newer) ! -Wunused-parameter (only with `-Wunused' or `-Wall') ! -Wunused-but-set-parameter (only with `-Wunused' or `-Wall') ! The option `-Wextra' also prints warning messages for the ! following cases: ! * A pointer is compared against integer zero with `<', `<=', ! `>', or `>='. * (C++ only) An enumerator and a non-enumerator both appear in a conditional expression. *************** compiler warns that an unrecognized opti *** 3596,3824 **** * (C++ only) Ambiguous virtual bases. * (C++ only) Subscripting an array that has been declared ! 'register'. * (C++ only) Taking the address of a variable that has been ! declared 'register'. * (C++ only) A base class is not initialized in a derived class's copy constructor. ! '-Wchar-subscripts' ! Warn if an array subscript has type 'char'. This is a common cause of error, as programmers often forget that this type is signed on ! some machines. This warning is enabled by '-Wall'. ! '-Wcomment' ! Warn whenever a comment-start sequence '/*' appears in a '/*' ! comment, or whenever a Backslash-Newline appears in a '//' comment. ! This warning is enabled by '-Wall'. ! '-Wno-coverage-mismatch' Warn if feedback profiles do not match when using the ! '-fprofile-use' option. If a source file is changed between ! compiling with '-fprofile-gen' and with '-fprofile-use', the files ! with the profile feedback can fail to match the source file and GCC ! cannot use the profile feedback information. By default, this warning is enabled and is treated as an error. ! '-Wno-coverage-mismatch' can be used to disable the warning or ! '-Wno-error=coverage-mismatch' can be used to disable the error. ! Disabling the error for this warning can result in poorly optimized ! code and is useful only in the case of very minor changes such as ! bug fixes to an existing code-base. Completely disabling the ! warning is not recommended. ! '-Wno-cpp' (C, Objective-C, C++, Objective-C++ and Fortran only) ! Suppress warning messages emitted by '#warning' directives. ! '-Wdouble-promotion (C, C++, Objective-C and Objective-C++ only)' ! Give a warning when a value of type 'float' is implicitly promoted ! to 'double'. CPUs with a 32-bit "single-precision" floating-point ! unit implement 'float' in hardware, but emulate 'double' in ! software. On such a machine, doing computations using 'double' values is much more expensive because of the overhead required for software emulation. ! It is easy to accidentally do computations with 'double' because ! floating-point literals are implicitly of type 'double'. For example, in: float area(float radius) { return 3.14159 * radius * radius; } ! the compiler performs the entire computation with 'double' because ! the floating-point literal is a 'double'. ! '-Wformat' ! '-Wformat=N' ! Check calls to 'printf' and 'scanf', etc., to make sure that the arguments supplied have types appropriate to the format string specified, and that the conversions specified in the format string ! make sense. This includes standard functions, and others specified ! by format attributes (*note Function Attributes::), in the ! 'printf', 'scanf', 'strftime' and 'strfmon' (an X/Open extension, ! not in the C standard) families (or other target-specific ! families). Which functions are checked without format attributes ! having been specified depends on the standard version selected, and ! such checks of functions without the attribute specified are ! disabled by '-ffreestanding' or '-fno-builtin'. The formats are checked against the format features supported by GNU libc version 2.2. These include all ISO C90 and C99 features, ! as well as features from the Single Unix Specification and some BSD ! and GNU extensions. Other library implementations may not support ! all these features; GCC does not support warning about features ! that go beyond a particular library's limitations. However, if ! '-Wpedantic' is used with '-Wformat', warnings are given about ! format features not in the selected standard version (but not for ! 'strfmon' formats, since those are not in any version of the C ! standard). *Note Options Controlling C Dialect: C Dialect Options. ! '-Wformat=1' ! '-Wformat' ! Option '-Wformat' is equivalent to '-Wformat=1', and ! '-Wno-format' is equivalent to '-Wformat=0'. Since '-Wformat' ! also checks for null format arguments for several functions, ! '-Wformat' also implies '-Wnonnull'. Some aspects of this ! level of format checking can be disabled by the options: ! '-Wno-format-contains-nul', '-Wno-format-extra-args', and ! '-Wno-format-zero-length'. '-Wformat' is enabled by '-Wall'. ! '-Wno-format-contains-nul' ! If '-Wformat' is specified, do not warn about format strings that contain NUL bytes. ! '-Wno-format-extra-args' ! If '-Wformat' is specified, do not warn about excess arguments ! to a 'printf' or 'scanf' format function. The C standard ! specifies that such arguments are ignored. Where the unused arguments lie between used arguments that are ! specified with '$' operand number specifications, normally warnings are still given, since the implementation could not ! know what type to pass to 'va_arg' to skip the unused ! arguments. However, in the case of 'scanf' formats, this option suppresses the warning if the unused arguments are all pointers, since the Single Unix Specification says that such unused arguments are allowed. ! '-Wno-format-zero-length' ! If '-Wformat' is specified, do not warn about zero-length formats. The C standard specifies that zero-length formats are allowed. ! '-Wformat=2' ! Enable '-Wformat' plus additional format checks. Currently ! equivalent to '-Wformat -Wformat-nonliteral -Wformat-security -Wformat-y2k'. ! '-Wformat-nonliteral' ! If '-Wformat' is specified, also warn if the format string is not a string literal and so cannot be checked, unless the ! format function takes its format arguments as a 'va_list'. ! '-Wformat-security' ! If '-Wformat' is specified, also warn about uses of format functions that represent possible security problems. At ! present, this warns about calls to 'printf' and 'scanf' functions where the format string is not a string literal and ! there are no format arguments, as in 'printf (foo);'. This may be a security hole if the format string came from ! untrusted input and contains '%n'. (This is currently a ! subset of what '-Wformat-nonliteral' warns about, but in ! future warnings may be added to '-Wformat-security' that are ! not included in '-Wformat-nonliteral'.) ! '-Wformat-signedness' ! If '-Wformat' is specified, also warn if the format string requires an unsigned argument and the argument is signed and vice versa. ! '-Wformat-y2k' ! If '-Wformat' is specified, also warn about 'strftime' formats ! that may yield only a two-digit year. ! '-Wnonnull' ! Warn about passing a null pointer for arguments marked as requiring ! a non-null value by the 'nonnull' function attribute. ! '-Wnonnull' is included in '-Wall' and '-Wformat'. It can be ! disabled with the '-Wno-nonnull' option. ! '-Wnonnull-compare' ! Warn when comparing an argument marked with the 'nonnull' function attribute against null inside the function. ! '-Wnonnull-compare' is included in '-Wall'. It can be disabled ! with the '-Wno-nonnull-compare' option. ! '-Wnull-dereference' Warn if the compiler detects paths that trigger erroneous or undefined behavior due to dereferencing a null pointer. This ! option is only active when '-fdelete-null-pointer-checks' is active, which is enabled by optimizations in most targets. The precision of the warnings depends on the optimization options used. ! '-Winit-self (C, C++, Objective-C and Objective-C++ only)' Warn about uninitialized variables that are initialized with themselves. Note this option can only be used with the ! '-Wuninitialized' option. ! For example, GCC warns about 'i' being uninitialized in the ! following snippet only when '-Winit-self' has been specified: int f() { int i = i; return i; } ! This warning is enabled by '-Wall' in C++. ! '-Wimplicit-int (C and Objective-C only)' Warn when a declaration does not specify a type. This warning is ! enabled by '-Wall'. ! '-Wimplicit-function-declaration (C and Objective-C only)' Give a warning whenever a function is used before being declared. ! In C99 mode ('-std=c99' or '-std=gnu99'), this warning is enabled ! by default and it is made into an error by '-pedantic-errors'. ! This warning is also enabled by '-Wall'. ! '-Wimplicit (C and Objective-C only)' ! Same as '-Wimplicit-int' and '-Wimplicit-function-declaration'. ! This warning is enabled by '-Wall'. ! '-Wignored-qualifiers (C and C++ only)' Warn if the return type of a function has a type qualifier such as ! 'const'. For ISO C such a type qualifier has no effect, since the value returned by a function is not an lvalue. For C++, the ! warning is only emitted for scalar types or 'void'. ISO C ! prohibits qualified 'void' return types on function definitions, so ! such return types always receive a warning even without this option. ! This warning is also enabled by '-Wextra'. ! '-Wignored-attributes (C and C++ only)' Warn when an attribute is ignored. This is different from the ! '-Wattributes' option in that it warns whenever the compiler decides to drop an attribute, not that the attribute is either unknown, used in a wrong place, etc. This warning is enabled by default. ! '-Wmain' ! Warn if the type of 'main' is suspicious. 'main' should be a function with external linkage, returning int, taking either zero arguments, two, or three arguments of appropriate types. This warning is enabled by default in C++ and is enabled by either ! '-Wall' or '-Wpedantic'. ! '-Wmisleading-indentation (C and C++ only)' Warn when the indentation of the code does not reflect the block ! structure. Specifically, a warning is issued for 'if', 'else', ! 'while', and 'for' clauses with a guarded statement that does not use braces, followed by an unguarded statement with the same indentation. --- 3616,3852 ---- * (C++ only) Ambiguous virtual bases. * (C++ only) Subscripting an array that has been declared ! `register'. * (C++ only) Taking the address of a variable that has been ! declared `register'. * (C++ only) A base class is not initialized in a derived class's copy constructor. ! ! `-Wchar-subscripts' ! Warn if an array subscript has type `char'. This is a common cause of error, as programmers often forget that this type is signed on ! some machines. This warning is enabled by `-Wall'. ! `-Wcomment' ! Warn whenever a comment-start sequence `/*' appears in a `/*' ! comment, or whenever a Backslash-Newline appears in a `//' comment. ! This warning is enabled by `-Wall'. ! `-Wchkp' ! Warn about an invalid memory access that is found by Pointer ! Bounds Checker (`-fcheck-pointer-bounds'). ! ! `-Wno-coverage-mismatch' Warn if feedback profiles do not match when using the ! `-fprofile-use' option. If a source file is changed between ! compiling with `-fprofile-gen' and with `-fprofile-use', the files ! with the profile feedback can fail to match the source file and ! GCC cannot use the profile feedback information. By default, this warning is enabled and is treated as an error. ! `-Wno-coverage-mismatch' can be used to disable the warning or ! `-Wno-error=coverage-mismatch' can be used to disable the error. ! Disabling the error for this warning can result in poorly ! optimized code and is useful only in the case of very minor ! changes such as bug fixes to an existing code-base. Completely ! disabling the warning is not recommended. ! `-Wno-cpp' (C, Objective-C, C++, Objective-C++ and Fortran only) ! Suppress warning messages emitted by `#warning' directives. ! `-Wdouble-promotion (C, C++, Objective-C and Objective-C++ only)' ! Give a warning when a value of type `float' is implicitly promoted ! to `double'. CPUs with a 32-bit "single-precision" floating-point ! unit implement `float' in hardware, but emulate `double' in ! software. On such a machine, doing computations using `double' values is much more expensive because of the overhead required for software emulation. ! It is easy to accidentally do computations with `double' because ! floating-point literals are implicitly of type `double'. For example, in: float area(float radius) { return 3.14159 * radius * radius; } ! the compiler performs the entire computation with `double' because ! the floating-point literal is a `double'. ! `-Wformat' ! `-Wformat=N' ! Check calls to `printf' and `scanf', etc., to make sure that the arguments supplied have types appropriate to the format string specified, and that the conversions specified in the format string ! make sense. This includes standard functions, and others ! specified by format attributes (*note Function Attributes::), in ! the `printf', `scanf', `strftime' and `strfmon' (an X/Open ! extension, not in the C standard) families (or other ! target-specific families). Which functions are checked without ! format attributes having been specified depends on the standard ! version selected, and such checks of functions without the ! attribute specified are disabled by `-ffreestanding' or ! `-fno-builtin'. The formats are checked against the format features supported by GNU libc version 2.2. These include all ISO C90 and C99 features, ! as well as features from the Single Unix Specification and some ! BSD and GNU extensions. Other library implementations may not ! support all these features; GCC does not support warning about ! features that go beyond a particular library's limitations. ! However, if `-Wpedantic' is used with `-Wformat', warnings are ! given about format features not in the selected standard version ! (but not for `strfmon' formats, since those are not in any version ! of the C standard). *Note Options Controlling C Dialect: C ! Dialect Options. ! `-Wformat=1' ! `-Wformat' ! Option `-Wformat' is equivalent to `-Wformat=1', and ! `-Wno-format' is equivalent to `-Wformat=0'. Since ! `-Wformat' also checks for null format arguments for several ! functions, `-Wformat' also implies `-Wnonnull'. Some aspects ! of this level of format checking can be disabled by the ! options: `-Wno-format-contains-nul', ! `-Wno-format-extra-args', and `-Wno-format-zero-length'. ! `-Wformat' is enabled by `-Wall'. ! `-Wno-format-contains-nul' ! If `-Wformat' is specified, do not warn about format strings that contain NUL bytes. ! `-Wno-format-extra-args' ! If `-Wformat' is specified, do not warn about excess ! arguments to a `printf' or `scanf' format function. The C ! standard specifies that such arguments are ignored. Where the unused arguments lie between used arguments that are ! specified with `$' operand number specifications, normally warnings are still given, since the implementation could not ! know what type to pass to `va_arg' to skip the unused ! arguments. However, in the case of `scanf' formats, this option suppresses the warning if the unused arguments are all pointers, since the Single Unix Specification says that such unused arguments are allowed. ! `-Wno-format-zero-length' ! If `-Wformat' is specified, do not warn about zero-length formats. The C standard specifies that zero-length formats are allowed. ! `-Wformat=2' ! Enable `-Wformat' plus additional format checks. Currently ! equivalent to `-Wformat -Wformat-nonliteral -Wformat-security -Wformat-y2k'. ! `-Wformat-nonliteral' ! If `-Wformat' is specified, also warn if the format string is not a string literal and so cannot be checked, unless the ! format function takes its format arguments as a `va_list'. ! `-Wformat-security' ! If `-Wformat' is specified, also warn about uses of format functions that represent possible security problems. At ! present, this warns about calls to `printf' and `scanf' functions where the format string is not a string literal and ! there are no format arguments, as in `printf (foo);'. This may be a security hole if the format string came from ! untrusted input and contains `%n'. (This is currently a ! subset of what `-Wformat-nonliteral' warns about, but in ! future warnings may be added to `-Wformat-security' that are ! not included in `-Wformat-nonliteral'.) ! `-Wformat-signedness' ! If `-Wformat' is specified, also warn if the format string requires an unsigned argument and the argument is signed and vice versa. ! `-Wformat-y2k' ! If `-Wformat' is specified, also warn about `strftime' ! formats that may yield only a two-digit year. ! `-Wnonnull' ! Warn about passing a null pointer for arguments marked as ! requiring a non-null value by the `nonnull' function attribute. ! `-Wnonnull' is included in `-Wall' and `-Wformat'. It can be ! disabled with the `-Wno-nonnull' option. ! `-Wnonnull-compare' ! Warn when comparing an argument marked with the `nonnull' function attribute against null inside the function. ! `-Wnonnull-compare' is included in `-Wall'. It can be disabled ! with the `-Wno-nonnull-compare' option. ! `-Wnull-dereference' Warn if the compiler detects paths that trigger erroneous or undefined behavior due to dereferencing a null pointer. This ! option is only active when `-fdelete-null-pointer-checks' is active, which is enabled by optimizations in most targets. The precision of the warnings depends on the optimization options used. ! `-Winit-self (C, C++, Objective-C and Objective-C++ only)' Warn about uninitialized variables that are initialized with themselves. Note this option can only be used with the ! `-Wuninitialized' option. ! For example, GCC warns about `i' being uninitialized in the ! following snippet only when `-Winit-self' has been specified: int f() { int i = i; return i; } ! This warning is enabled by `-Wall' in C++. ! `-Wimplicit-int (C and Objective-C only)' Warn when a declaration does not specify a type. This warning is ! enabled by `-Wall'. ! `-Wimplicit-function-declaration (C and Objective-C only)' Give a warning whenever a function is used before being declared. ! In C99 mode (`-std=c99' or `-std=gnu99'), this warning is enabled ! by default and it is made into an error by `-pedantic-errors'. ! This warning is also enabled by `-Wall'. ! `-Wimplicit (C and Objective-C only)' ! Same as `-Wimplicit-int' and `-Wimplicit-function-declaration'. ! This warning is enabled by `-Wall'. ! `-Wignored-qualifiers (C and C++ only)' Warn if the return type of a function has a type qualifier such as ! `const'. For ISO C such a type qualifier has no effect, since the value returned by a function is not an lvalue. For C++, the ! warning is only emitted for scalar types or `void'. ISO C ! prohibits qualified `void' return types on function definitions, ! so such return types always receive a warning even without this option. ! This warning is also enabled by `-Wextra'. ! `-Wignored-attributes (C and C++ only)' Warn when an attribute is ignored. This is different from the ! `-Wattributes' option in that it warns whenever the compiler decides to drop an attribute, not that the attribute is either unknown, used in a wrong place, etc. This warning is enabled by default. ! `-Wmain' ! Warn if the type of `main' is suspicious. `main' should be a function with external linkage, returning int, taking either zero arguments, two, or three arguments of appropriate types. This warning is enabled by default in C++ and is enabled by either ! `-Wall' or `-Wpedantic'. ! `-Wmisleading-indentation (C and C++ only)' Warn when the indentation of the code does not reflect the block ! structure. Specifically, a warning is issued for `if', `else', ! `while', and `for' clauses with a guarded statement that does not use braces, followed by an unguarded statement with the same indentation. *************** compiler warns that an unrecognized opti *** 3830,3840 **** bar (); /* Gotcha: this is not guarded by the "if". */ In the case of mixed tabs and spaces, the warning uses the ! '-ftabstop=' option to determine if the statements line up (defaulting to 8). ! The warning is not issued for code involving multiline preprocessor ! logic such as the following example. if (flagA) foo (0); --- 3858,3868 ---- bar (); /* Gotcha: this is not guarded by the "if". */ In the case of mixed tabs and spaces, the warning uses the ! `-ftabstop=' option to determine if the statements line up (defaulting to 8). ! The warning is not issued for code involving multiline ! preprocessor logic such as the following example. if (flagA) foo (0); *************** compiler warns that an unrecognized opti *** 3843,3880 **** #endif foo (1); ! The warning is not issued after a '#line' directive, since this typically indicates autogenerated code, and no assumptions can be made about the layout of the file that the directive references. ! This warning is enabled by '-Wall' in C and C++. ! '-Wmissing-braces' Warn if an aggregate or union initializer is not fully bracketed. ! In the following example, the initializer for 'a' is not fully ! bracketed, but that for 'b' is fully bracketed. This warning is ! enabled by '-Wall' in C. int a[2][2] = { 0, 1, 2, 3 }; int b[2][2] = { { 0, 1 }, { 2, 3 } }; ! This warning is enabled by '-Wall'. ! '-Wmissing-include-dirs (C, C++, Objective-C and Objective-C++ only)' Warn if a user-supplied include directory does not exist. ! '-Wparentheses' Warn if parentheses are omitted in certain contexts, such as when there is an assignment in a context where a truth value is expected, or when operators are nested whose precedence people often get confused about. ! Also warn if a comparison like 'x<=y<=z' appears; this is ! equivalent to '(x<=y ? 1 : 0) <= z', which is a different interpretation from that of ordinary mathematical notation. Also warn about constructions where there may be confusion to which ! 'if' statement an 'else' branch belongs. Here is an example of such a case: { --- 3871,3908 ---- #endif foo (1); ! The warning is not issued after a `#line' directive, since this typically indicates autogenerated code, and no assumptions can be made about the layout of the file that the directive references. ! This warning is enabled by `-Wall' in C and C++. ! `-Wmissing-braces' Warn if an aggregate or union initializer is not fully bracketed. ! In the following example, the initializer for `a' is not fully ! bracketed, but that for `b' is fully bracketed. This warning is ! enabled by `-Wall' in C. int a[2][2] = { 0, 1, 2, 3 }; int b[2][2] = { { 0, 1 }, { 2, 3 } }; ! This warning is enabled by `-Wall'. ! `-Wmissing-include-dirs (C, C++, Objective-C and Objective-C++ only)' Warn if a user-supplied include directory does not exist. ! `-Wparentheses' Warn if parentheses are omitted in certain contexts, such as when there is an assignment in a context where a truth value is expected, or when operators are nested whose precedence people often get confused about. ! Also warn if a comparison like `x<=y<=z' appears; this is ! equivalent to `(x<=y ? 1 : 0) <= z', which is a different interpretation from that of ordinary mathematical notation. Also warn about constructions where there may be confusion to which ! `if' statement an `else' branch belongs. Here is an example of such a case: { *************** compiler warns that an unrecognized opti *** 3885,3898 **** bar (); } ! In C/C++, every 'else' branch belongs to the innermost possible ! 'if' statement, which in this example is 'if (b)'. This is often not what the programmer expected, as illustrated in the above example by indentation the programmer chose. When there is the potential for this confusion, GCC issues a warning when this flag is specified. To eliminate the warning, add explicit braces around ! the innermost 'if' statement so there is no way the 'else' can ! belong to the enclosing 'if'. The resulting code looks like this: { if (a) --- 3913,3926 ---- bar (); } ! In C/C++, every `else' branch belongs to the innermost possible ! `if' statement, which in this example is `if (b)'. This is often not what the programmer expected, as illustrated in the above example by indentation the programmer chose. When there is the potential for this confusion, GCC issues a warning when this flag is specified. To eliminate the warning, add explicit braces around ! the innermost `if' statement so there is no way the `else' can ! belong to the enclosing `if'. The resulting code looks like this: { if (a) *************** compiler warns that an unrecognized opti *** 3904,3918 **** } } ! Also warn for dangerous uses of the GNU extension to '?:' with ! omitted middle operand. When the condition in the '?': operator is a boolean expression, the omitted value is always 1. Often ! programmers expect it to be a value computed inside the conditional ! expression instead. ! This warning is enabled by '-Wall'. ! '-Wsequence-point' Warn about code that may have undefined semantics because of violations of sequence point rules in the C and C++ standards. --- 3932,3946 ---- } } ! Also warn for dangerous uses of the GNU extension to `?:' with ! omitted middle operand. When the condition in the `?': operator is a boolean expression, the omitted value is always 1. Often ! programmers expect it to be a value computed inside the ! conditional expression instead. ! This warning is enabled by `-Wall'. ! `-Wsequence-point' Warn about code that may have undefined semantics because of violations of sequence point rules in the C and C++ standards. *************** compiler warns that an unrecognized opti *** 3922,3951 **** program: those executed before the sequence point, and those executed after it. These occur after the evaluation of a full expression (one which is not part of a larger expression), after ! the evaluation of the first operand of a '&&', '||', '? :' or ',' (comma) operator, before a function is called (but after the evaluation of its arguments and the expression denoting the called ! function), and in certain other places. Other than as expressed by ! the sequence point rules, the order of evaluation of subexpressions ! of an expression is not specified. All these rules describe only a ! partial order rather than a total order, since, for example, if two ! functions are called within one expression with no sequence point ! between them, the order in which the functions are called is not ! specified. However, the standards committee have ruled that ! function calls do not overlap. It is not specified when between sequence points modifications to ! the values of objects take effect. Programs whose behavior depends ! on this have undefined behavior; the C and C++ standards specify ! that "Between the previous and next sequence point an object shall ! have its stored value modified at most once by the evaluation of an ! expression. Furthermore, the prior value shall be read only to ! determine the value to be stored.". If a program breaks these ! rules, the results on any particular implementation are entirely ! unpredictable. ! Examples of code with undefined behavior are 'a = a++;', 'a[n] = ! b[n++]' and 'a[i++] = i;'. Some more complicated cases are not diagnosed by this option, and it may give an occasional false positive result, but in general it has been found fairly effective at detecting this sort of problem in programs. --- 3950,3979 ---- program: those executed before the sequence point, and those executed after it. These occur after the evaluation of a full expression (one which is not part of a larger expression), after ! the evaluation of the first operand of a `&&', `||', `? :' or `,' (comma) operator, before a function is called (but after the evaluation of its arguments and the expression denoting the called ! function), and in certain other places. Other than as expressed ! by the sequence point rules, the order of evaluation of ! subexpressions of an expression is not specified. All these rules ! describe only a partial order rather than a total order, since, ! for example, if two functions are called within one expression ! with no sequence point between them, the order in which the ! functions are called is not specified. However, the standards ! committee have ruled that function calls do not overlap. It is not specified when between sequence points modifications to ! the values of objects take effect. Programs whose behavior ! depends on this have undefined behavior; the C and C++ standards ! specify that "Between the previous and next sequence point an ! object shall have its stored value modified at most once by the ! evaluation of an expression. Furthermore, the prior value shall ! be read only to determine the value to be stored.". If a program ! breaks these rules, the results on any particular implementation ! are entirely unpredictable. ! Examples of code with undefined behavior are `a = a++;', `a[n] = ! b[n++]' and `a[i++] = i;'. Some more complicated cases are not diagnosed by this option, and it may give an occasional false positive result, but in general it has been found fairly effective at detecting this sort of problem in programs. *************** compiler warns that an unrecognized opti *** 3954,4159 **** over the precise meaning of the sequence point rules in subtle cases. Links to discussions of the problem, including proposed formal definitions, may be found on the GCC readings page, at ! . ! This warning is enabled by '-Wall' for C and C++. ! '-Wno-return-local-addr' Do not warn about returning a pointer (or in C++, a reference) to a variable that goes out of scope after the function returns. ! '-Wreturn-type' Warn whenever a function is defined with a return type that ! defaults to 'int'. Also warn about any 'return' statement with no ! return value in a function whose return type is not 'void' (falling ! off the end of the function body is considered returning without a ! value), and about a 'return' statement with an expression in a ! function whose return type is 'void'. For C++, a function without return type always produces a ! diagnostic message, even when '-Wno-return-type' is specified. The ! only exceptions are 'main' and functions defined in system headers. ! This warning is enabled by '-Wall'. ! '-Wshift-count-negative' ! Warn if shift count is negative. This warning is enabled by default. ! '-Wshift-count-overflow' ! Warn if shift count >= width of type. This warning is enabled by default. ! '-Wshift-negative-value' Warn if left shifting a negative value. This warning is enabled by ! '-Wextra' in C99 and C++11 modes (and newer). ! '-Wshift-overflow' ! '-Wshift-overflow=N' Warn about left shift overflows. This warning is enabled by default in C99 and C++11 modes (and newer). ! '-Wshift-overflow=1' ! This is the warning level of '-Wshift-overflow' and is enabled by default in C99 and C++11 modes (and newer). This warning level does not warn about left-shifting 1 into the sign bit. ! (However, in C, such an overflow is still rejected in contexts ! where an integer constant expression is required.) ! '-Wshift-overflow=2' This warning level also warns about left-shifting 1 into the sign bit, unless C++14 mode is active. ! '-Wswitch' ! Warn whenever a 'switch' statement has an index of enumerated type ! and lacks a 'case' for one or more of the named codes of that ! enumeration. (The presence of a 'default' label prevents this ! warning.) 'case' labels outside the enumeration range also provoke ! warnings when this option is used (even if there is a 'default' ! label). This warning is enabled by '-Wall'. ! '-Wswitch-default' ! Warn whenever a 'switch' statement does not have a 'default' case. ! '-Wswitch-enum' ! Warn whenever a 'switch' statement has an index of enumerated type ! and lacks a 'case' for one or more of the named codes of that ! enumeration. 'case' labels outside the enumeration range also provoke warnings when this option is used. The only difference ! between '-Wswitch' and this option is that this option gives a warning about an omitted enumeration code even if there is a ! 'default' label. ! '-Wswitch-bool' ! Warn whenever a 'switch' statement has an index of boolean type and ! the case values are outside the range of a boolean type. It is ! possible to suppress this warning by casting the controlling ! expression to a type other than 'bool'. For example: switch ((int) (a == 4)) { ... } This warning is enabled by default for C and C++ programs. ! '-Wsync-nand (C and C++ only)' ! Warn when '__sync_fetch_and_nand' and '__sync_nand_and_fetch' built-in functions are used. These functions changed semantics in GCC 4.4. ! '-Wtrigraphs' ! Warn if any trigraphs are encountered that might change the meaning ! of the program (trigraphs within comments are not warned about). ! This warning is enabled by '-Wall'. ! '-Wunused-but-set-parameter' Warn whenever a function parameter is assigned to, but otherwise unused (aside from its declaration). ! To suppress this warning use the 'unused' attribute (*note Variable ! Attributes::). ! This warning is also enabled by '-Wunused' together with '-Wextra'. ! '-Wunused-but-set-variable' Warn whenever a local variable is assigned to, but otherwise unused ! (aside from its declaration). This warning is enabled by '-Wall'. ! To suppress this warning use the 'unused' attribute (*note Variable ! Attributes::). ! This warning is also enabled by '-Wunused', which is enabled by ! '-Wall'. ! '-Wunused-function' Warn whenever a static function is declared but not defined or a non-inline static function is unused. This warning is enabled by ! '-Wall'. ! '-Wunused-label' Warn whenever a label is declared but not used. This warning is ! enabled by '-Wall'. ! To suppress this warning use the 'unused' attribute (*note Variable ! Attributes::). ! '-Wunused-local-typedefs (C, Objective-C, C++ and Objective-C++ only)' Warn when a typedef locally defined in a function is not used. ! This warning is enabled by '-Wall'. ! '-Wunused-parameter' Warn whenever a function parameter is unused aside from its declaration. ! To suppress this warning use the 'unused' attribute (*note Variable ! Attributes::). ! '-Wno-unused-result' Do not warn if a caller of a function marked with attribute ! 'warn_unused_result' (*note Function Attributes::) does not use its ! return value. The default is '-Wunused-result'. ! '-Wunused-variable' Warn whenever a local or static variable is unused aside from its ! declaration. This option implies '-Wunused-const-variable=1' for ! C, but not for C++. This warning is enabled by '-Wall'. ! To suppress this warning use the 'unused' attribute (*note Variable ! Attributes::). ! '-Wunused-const-variable' ! '-Wunused-const-variable=N' Warn whenever a constant static variable is unused aside from its ! declaration. '-Wunused-const-variable=1' is enabled by ! '-Wunused-variable' for C, but not for C++. In C this declares variable storage, but in C++ this is not an error since const ! variables take the place of '#define's. ! To suppress this warning use the 'unused' attribute (*note Variable ! Attributes::). ! '-Wunused-const-variable=1' This is the warning level that is enabled by ! '-Wunused-variable' for C. It warns only about unused static const variables defined in the main compilation unit, but not about static const variables declared in any header included. ! '-Wunused-const-variable=2' This warning level also warns for unused constant static variables in headers (excluding system headers). This is the ! warning level of '-Wunused-const-variable' and must be ! explicitly requested since in C++ this isn't an error and in C ! it might be harder to clean up all headers included. ! '-Wunused-value' Warn whenever a statement computes a result that is explicitly not ! used. To suppress this warning cast the unused expression to ! 'void'. This includes an expression-statement or the left-hand ! side of a comma expression that contains no side effects. For ! example, an expression such as 'x[i,j]' causes a warning, while ! 'x[(void)i,j]' does not. ! This warning is enabled by '-Wall'. ! '-Wunused' ! All the above '-Wunused' options combined. In order to get a warning about an unused function parameter, you ! must either specify '-Wextra -Wunused' (note that '-Wall' implies ! '-Wunused'), or separately specify '-Wunused-parameter'. ! '-Wuninitialized' Warn if an automatic variable is used without first being ! initialized or if a variable may be clobbered by a 'setjmp' call. ! In C++, warn if a non-static reference or non-static 'const' member appears in a class without constructors. ! If you want to warn about code that uses the uninitialized value of ! the variable in its own initializer, use the '-Winit-self' option. These warnings occur for individual uninitialized or clobbered elements of structure, union or array variables as well as for variables that are uninitialized or clobbered as a whole. They do ! not occur for variables or elements declared 'volatile'. Because these warnings depend on optimization, the exact variables or elements for which there are warnings depends on the precise optimization options and version of GCC used. --- 3982,4189 ---- over the precise meaning of the sequence point rules in subtle cases. Links to discussions of the problem, including proposed formal definitions, may be found on the GCC readings page, at ! `http://gcc.gnu.org/readings.html'. ! This warning is enabled by `-Wall' for C and C++. ! `-Wno-return-local-addr' Do not warn about returning a pointer (or in C++, a reference) to a variable that goes out of scope after the function returns. ! `-Wreturn-type' Warn whenever a function is defined with a return type that ! defaults to `int'. Also warn about any `return' statement with no ! return value in a function whose return type is not `void' ! (falling off the end of the function body is considered returning ! without a value), and about a `return' statement with an ! expression in a function whose return type is `void'. For C++, a function without return type always produces a ! diagnostic message, even when `-Wno-return-type' is specified. ! The only exceptions are `main' and functions defined in system ! headers. ! This warning is enabled by `-Wall'. ! `-Wshift-count-negative' ! Warn if shift count is negative. This warning is enabled by default. ! `-Wshift-count-overflow' ! Warn if shift count >= width of type. This warning is enabled by default. ! `-Wshift-negative-value' Warn if left shifting a negative value. This warning is enabled by ! `-Wextra' in C99 and C++11 modes (and newer). ! `-Wshift-overflow' ! `-Wshift-overflow=N' Warn about left shift overflows. This warning is enabled by default in C99 and C++11 modes (and newer). ! `-Wshift-overflow=1' ! This is the warning level of `-Wshift-overflow' and is enabled by default in C99 and C++11 modes (and newer). This warning level does not warn about left-shifting 1 into the sign bit. ! (However, in C, such an overflow is still rejected in ! contexts where an integer constant expression is required.) ! `-Wshift-overflow=2' This warning level also warns about left-shifting 1 into the sign bit, unless C++14 mode is active. ! `-Wswitch' ! Warn whenever a `switch' statement has an index of enumerated type ! and lacks a `case' for one or more of the named codes of that ! enumeration. (The presence of a `default' label prevents this ! warning.) `case' labels outside the enumeration range also ! provoke warnings when this option is used (even if there is a ! `default' label). This warning is enabled by `-Wall'. ! `-Wswitch-default' ! Warn whenever a `switch' statement does not have a `default' case. ! `-Wswitch-enum' ! Warn whenever a `switch' statement has an index of enumerated type ! and lacks a `case' for one or more of the named codes of that ! enumeration. `case' labels outside the enumeration range also provoke warnings when this option is used. The only difference ! between `-Wswitch' and this option is that this option gives a warning about an omitted enumeration code even if there is a ! `default' label. ! `-Wswitch-bool' ! Warn whenever a `switch' statement has an index of boolean type ! and the case values are outside the range of a boolean type. It ! is possible to suppress this warning by casting the controlling ! expression to a type other than `bool'. For example: switch ((int) (a == 4)) { ... } This warning is enabled by default for C and C++ programs. ! `-Wsync-nand (C and C++ only)' ! Warn when `__sync_fetch_and_nand' and `__sync_nand_and_fetch' built-in functions are used. These functions changed semantics in GCC 4.4. ! `-Wtrigraphs' ! Warn if any trigraphs are encountered that might change the ! meaning of the program (trigraphs within comments are not warned ! about). This warning is enabled by `-Wall'. ! `-Wunused-but-set-parameter' Warn whenever a function parameter is assigned to, but otherwise unused (aside from its declaration). ! To suppress this warning use the `unused' attribute (*note ! Variable Attributes::). ! This warning is also enabled by `-Wunused' together with `-Wextra'. ! `-Wunused-but-set-variable' Warn whenever a local variable is assigned to, but otherwise unused ! (aside from its declaration). This warning is enabled by `-Wall'. ! To suppress this warning use the `unused' attribute (*note ! Variable Attributes::). ! This warning is also enabled by `-Wunused', which is enabled by ! `-Wall'. ! `-Wunused-function' Warn whenever a static function is declared but not defined or a non-inline static function is unused. This warning is enabled by ! `-Wall'. ! `-Wunused-label' Warn whenever a label is declared but not used. This warning is ! enabled by `-Wall'. ! To suppress this warning use the `unused' attribute (*note ! Variable Attributes::). ! `-Wunused-local-typedefs (C, Objective-C, C++ and Objective-C++ only)' Warn when a typedef locally defined in a function is not used. ! This warning is enabled by `-Wall'. ! `-Wunused-parameter' Warn whenever a function parameter is unused aside from its declaration. ! To suppress this warning use the `unused' attribute (*note ! Variable Attributes::). ! `-Wno-unused-result' Do not warn if a caller of a function marked with attribute ! `warn_unused_result' (*note Function Attributes::) does not use ! its return value. The default is `-Wunused-result'. ! `-Wunused-variable' Warn whenever a local or static variable is unused aside from its ! declaration. This option implies `-Wunused-const-variable=1' for C, ! but not for C++. This warning is enabled by `-Wall'. ! To suppress this warning use the `unused' attribute (*note ! Variable Attributes::). ! `-Wunused-const-variable' ! `-Wunused-const-variable=N' Warn whenever a constant static variable is unused aside from its ! declaration. `-Wunused-const-variable=1' is enabled by ! `-Wunused-variable' for C, but not for C++. In C this declares variable storage, but in C++ this is not an error since const ! variables take the place of `#define's. ! To suppress this warning use the `unused' attribute (*note ! Variable Attributes::). ! `-Wunused-const-variable=1' This is the warning level that is enabled by ! `-Wunused-variable' for C. It warns only about unused static const variables defined in the main compilation unit, but not about static const variables declared in any header included. ! `-Wunused-const-variable=2' This warning level also warns for unused constant static variables in headers (excluding system headers). This is the ! warning level of `-Wunused-const-variable' and must be ! explicitly requested since in C++ this isn't an error and in ! C it might be harder to clean up all headers included. ! `-Wunused-value' Warn whenever a statement computes a result that is explicitly not ! used. To suppress this warning cast the unused expression to ! `void'. This includes an expression-statement or the left-hand ! side of a comma expression that contains no side effects. For ! example, an expression such as `x[i,j]' causes a warning, while ! `x[(void)i,j]' does not. ! This warning is enabled by `-Wall'. ! `-Wunused' ! All the above `-Wunused' options combined. In order to get a warning about an unused function parameter, you ! must either specify `-Wextra -Wunused' (note that `-Wall' implies ! `-Wunused'), or separately specify `-Wunused-parameter'. ! `-Wuninitialized' Warn if an automatic variable is used without first being ! initialized or if a variable may be clobbered by a `setjmp' call. ! In C++, warn if a non-static reference or non-static `const' member appears in a class without constructors. ! If you want to warn about code that uses the uninitialized value ! of the variable in its own initializer, use the `-Winit-self' ! option. These warnings occur for individual uninitialized or clobbered elements of structure, union or array variables as well as for variables that are uninitialized or clobbered as a whole. They do ! not occur for variables or elements declared `volatile'. Because these warnings depend on optimization, the exact variables or elements for which there are warnings depends on the precise optimization options and version of GCC used. *************** compiler warns that an unrecognized opti *** 4163,4174 **** computations may be deleted by data flow analysis before the warnings are printed. ! '-Winvalid-memory-model' Warn for invocations of *note __atomic Builtins::, *note __sync Builtins::, and the C11 atomic generic functions with a memory consistency argument that is either invalid for the operation or ! outside the range of values of the 'memory_order' enumeration. For ! example, since the '__atomic_store' and '__atomic_store_n' built-ins are only defined for the relaxed, release, and sequentially consistent memory orders the following code is diagnosed: --- 4193,4204 ---- computations may be deleted by data flow analysis before the warnings are printed. ! `-Winvalid-memory-model' Warn for invocations of *note __atomic Builtins::, *note __sync Builtins::, and the C11 atomic generic functions with a memory consistency argument that is either invalid for the operation or ! outside the range of values of the `memory_order' enumeration. ! For example, since the `__atomic_store' and `__atomic_store_n' built-ins are only defined for the relaxed, release, and sequentially consistent memory orders the following code is diagnosed: *************** compiler warns that an unrecognized opti *** 4178,4194 **** __atomic_store_n (i, 0, memory_order_consume); } ! '-Winvalid-memory-model' is enabled by default. ! '-Wmaybe-uninitialized' For an automatic variable, if there exists a path from the function entry to a use of the variable that is initialized, but there exist some other paths for which the variable is not initialized, the ! compiler emits a warning if it cannot prove the uninitialized paths ! are not executed at run time. These warnings are made optional ! because GCC is not smart enough to see all the reasons why the code ! might be correct in spite of appearing to have an error. Here is ! one example of how this can happen: { int x; --- 4208,4224 ---- __atomic_store_n (i, 0, memory_order_consume); } ! `-Winvalid-memory-model' is enabled by default. ! `-Wmaybe-uninitialized' For an automatic variable, if there exists a path from the function entry to a use of the variable that is initialized, but there exist some other paths for which the variable is not initialized, the ! compiler emits a warning if it cannot prove the uninitialized ! paths are not executed at run time. These warnings are made ! optional because GCC is not smart enough to see all the reasons ! why the code might be correct in spite of appearing to have an ! error. Here is one example of how this can happen: { int x; *************** compiler warns that an unrecognized opti *** 4203,4281 **** foo (x); } ! If the value of 'y' is always 1, 2 or 3, then 'x' is always ! initialized, but GCC doesn't know this. To suppress the warning, you need to provide a default case with assert(0) or similar code. ! This option also warns when a non-volatile automatic variable might ! be changed by a call to 'longjmp'. These warnings as well are ! possible only in optimizing compilation. ! The compiler sees only the calls to 'setjmp'. It cannot know where ! 'longjmp' will be called; in fact, a signal handler could call it ! at any point in the code. As a result, you may get a warning even ! when there is in fact no problem because 'longjmp' cannot in fact ! be called at the place that would cause a problem. Some spurious warnings can be avoided if you declare all the ! functions you use that never return as 'noreturn'. *Note Function Attributes::. ! This warning is enabled by '-Wall' or '-Wextra'. ! '-Wunknown-pragmas' ! Warn when a '#pragma' directive is encountered that is not understood by GCC. If this command-line option is used, warnings are even issued for unknown pragmas in system header files. This ! is not the case if the warnings are only enabled by the '-Wall' command-line option. ! '-Wno-pragmas' Do not warn about misuses of pragmas, such as incorrect parameters, invalid syntax, or conflicts between pragmas. See also ! '-Wunknown-pragmas'. ! '-Wstrict-aliasing' ! This option is only active when '-fstrict-aliasing' is active. It warns about code that might break the strict aliasing rules that ! the compiler is using for optimization. The warning does not catch ! all cases, but does attempt to catch the more common pitfalls. It ! is included in '-Wall'. It is equivalent to '-Wstrict-aliasing=3' ! '-Wstrict-aliasing=n' ! This option is only active when '-fstrict-aliasing' is active. It warns about code that might break the strict aliasing rules that the compiler is using for optimization. Higher levels correspond to higher accuracy (fewer false positives). Higher levels also ! correspond to more effort, similar to the way '-O' works. ! '-Wstrict-aliasing' is equivalent to '-Wstrict-aliasing=3'. Level 1: Most aggressive, quick, least accurate. Possibly useful ! when higher levels do not warn but '-fstrict-aliasing' still breaks ! the code, as it has very few false negatives. However, it has many ! false positives. Warns for all pointer conversions between ! possibly incompatible types, even if never dereferenced. Runs in ! the front end only. Level 2: Aggressive, quick, not too precise. May still have many false positives (not as many as level 1 though), and few false negatives (but possibly more than level 1). Unlike level 1, it ! only warns when an address is taken. Warns about incomplete types. ! Runs in the front end only. ! Level 3 (default for '-Wstrict-aliasing'): Should have very few false positives and few false negatives. Slightly slower than levels 1 or 2 when optimization is enabled. Takes care of the common pun+dereference pattern in the front end: ! '*(int*)&some_float'. If optimization is enabled, it also runs in the back end, where it deals with multiple statement cases using flow-sensitive points-to information. Only warns when the converted pointer is dereferenced. Does not warn about incomplete types. ! '-Wstrict-overflow' ! '-Wstrict-overflow=N' ! This option is only active when '-fstrict-overflow' is active. It warns about cases where the compiler optimizes based on the assumption that signed overflow does not occur. Note that it does not warn about all cases where the code might overflow: it only --- 4233,4312 ---- foo (x); } ! If the value of `y' is always 1, 2 or 3, then `x' is always ! initialized, but GCC doesn't know this. To suppress the warning, you need to provide a default case with assert(0) or similar code. ! This option also warns when a non-volatile automatic variable ! might be changed by a call to `longjmp'. These warnings as well ! are possible only in optimizing compilation. ! The compiler sees only the calls to `setjmp'. It cannot know ! where `longjmp' will be called; in fact, a signal handler could ! call it at any point in the code. As a result, you may get a ! warning even when there is in fact no problem because `longjmp' ! cannot in fact be called at the place that would cause a problem. Some spurious warnings can be avoided if you declare all the ! functions you use that never return as `noreturn'. *Note Function Attributes::. ! This warning is enabled by `-Wall' or `-Wextra'. ! `-Wunknown-pragmas' ! Warn when a `#pragma' directive is encountered that is not understood by GCC. If this command-line option is used, warnings are even issued for unknown pragmas in system header files. This ! is not the case if the warnings are only enabled by the `-Wall' command-line option. ! `-Wno-pragmas' Do not warn about misuses of pragmas, such as incorrect parameters, invalid syntax, or conflicts between pragmas. See also ! `-Wunknown-pragmas'. ! `-Wstrict-aliasing' ! This option is only active when `-fstrict-aliasing' is active. It warns about code that might break the strict aliasing rules that ! the compiler is using for optimization. The warning does not ! catch all cases, but does attempt to catch the more common ! pitfalls. It is included in `-Wall'. It is equivalent to ! `-Wstrict-aliasing=3' ! `-Wstrict-aliasing=n' ! This option is only active when `-fstrict-aliasing' is active. It warns about code that might break the strict aliasing rules that the compiler is using for optimization. Higher levels correspond to higher accuracy (fewer false positives). Higher levels also ! correspond to more effort, similar to the way `-O' works. ! `-Wstrict-aliasing' is equivalent to `-Wstrict-aliasing=3'. Level 1: Most aggressive, quick, least accurate. Possibly useful ! when higher levels do not warn but `-fstrict-aliasing' still ! breaks the code, as it has very few false negatives. However, it ! has many false positives. Warns for all pointer conversions ! between possibly incompatible types, even if never dereferenced. ! Runs in the front end only. Level 2: Aggressive, quick, not too precise. May still have many false positives (not as many as level 1 though), and few false negatives (but possibly more than level 1). Unlike level 1, it ! only warns when an address is taken. Warns about incomplete ! types. Runs in the front end only. ! Level 3 (default for `-Wstrict-aliasing'): Should have very few false positives and few false negatives. Slightly slower than levels 1 or 2 when optimization is enabled. Takes care of the common pun+dereference pattern in the front end: ! `*(int*)&some_float'. If optimization is enabled, it also runs in the back end, where it deals with multiple statement cases using flow-sensitive points-to information. Only warns when the converted pointer is dereferenced. Does not warn about incomplete types. ! `-Wstrict-overflow' ! `-Wstrict-overflow=N' ! This option is only active when `-fstrict-overflow' is active. It warns about cases where the compiler optimizes based on the assumption that signed overflow does not occur. Note that it does not warn about all cases where the code might overflow: it only *************** compiler warns that an unrecognized opti *** 4292,4479 **** loop requires, in particular when determining whether a loop will be executed at all. ! '-Wstrict-overflow=1' ! Warn about cases that are both questionable and easy to avoid. ! For example, with '-fstrict-overflow', the compiler simplifies ! 'x + 1 > x' to '1'. This level of '-Wstrict-overflow' is ! enabled by '-Wall'; higher levels are not, and must be ! explicitly requested. ! '-Wstrict-overflow=2' Also warn about other cases where a comparison is simplified ! to a constant. For example: 'abs (x) >= 0'. This can only be ! simplified when '-fstrict-overflow' is in effect, because 'abs ! (INT_MIN)' overflows to 'INT_MIN', which is less than zero. ! '-Wstrict-overflow' (with no level) is the same as ! '-Wstrict-overflow=2'. ! '-Wstrict-overflow=3' Also warn about other cases where a comparison is simplified. ! For example: 'x + 1 > 1' is simplified to 'x > 0'. ! '-Wstrict-overflow=4' ! Also warn about other simplifications not covered by the above ! cases. For example: '(x * 10) / 5' is simplified to 'x * 2'. ! '-Wstrict-overflow=5' ! Also warn about cases where the compiler reduces the magnitude ! of a constant involved in a comparison. For example: 'x + 2 > ! y' is simplified to 'x + 1 >= y'. This is reported only at ! the highest warning level because this simplification applies ! to many comparisons, so this warning level gives a very large ! number of false positives. ! '-Wsuggest-attribute=[pure|const|noreturn|format]' ! Warn for cases where adding an attribute may be beneficial. The attributes currently supported are listed below. ! '-Wsuggest-attribute=pure' ! '-Wsuggest-attribute=const' ! '-Wsuggest-attribute=noreturn' ! Warn about functions that might be candidates for attributes ! 'pure', 'const' or 'noreturn'. The compiler only warns for functions visible in other compilation units or (in the case ! of 'pure' and 'const') if it cannot prove that the function ! returns normally. A function returns normally if it doesn't contain an infinite loop or return abnormally by throwing, ! calling 'abort' or trapping. This analysis requires option ! '-fipa-pure-const', which is enabled by default at '-O' and higher. Higher optimization levels improve the accuracy of the analysis. ! '-Wsuggest-attribute=format' ! '-Wmissing-format-attribute' ! Warn about function pointers that might be candidates for ! 'format' attributes. Note these are only possible candidates, ! not absolute ones. GCC guesses that function pointers with ! 'format' attributes that are used in assignment, ! initialization, parameter passing or return statements should ! have a corresponding 'format' attribute in the resulting type. ! I.e. the left-hand side of the assignment or initialization, ! the type of the parameter variable, or the return type of the ! containing function respectively should also have a 'format' ! attribute to avoid the warning. GCC also warns about function definitions that might be ! candidates for 'format' attributes. Again, these are only ! possible candidates. GCC guesses that 'format' attributes might be appropriate for any function that calls a function ! like 'vprintf' or 'vscanf', but this might not always be the ! case, and some functions for which 'format' attributes are appropriate may not be detected. ! '-Wsuggest-final-types' Warn about types with virtual methods where code quality would be ! improved if the type were declared with the C++11 'final' specifier, or, if possible, declared in an anonymous namespace. This allows GCC to more aggressively devirtualize the polymorphic ! calls. This warning is more effective with link time optimization, where the information about the class hierarchy graph is more complete. ! '-Wsuggest-final-methods' Warn about virtual methods where code quality would be improved if ! the method were declared with the C++11 'final' specifier, or, if possible, its type were declared in an anonymous namespace or with ! the 'final' specifier. This warning is more effective with link time optimization, where the information about the class hierarchy ! graph is more complete. It is recommended to first consider ! suggestions of '-Wsuggest-final-types' and then rebuild with new annotations. ! '-Wsuggest-override' Warn about overriding virtual functions that are not marked with the override keyword. ! '-Warray-bounds' ! '-Warray-bounds=N' ! This option is only active when '-ftree-vrp' is active (default for ! '-O2' and above). It warns about subscripts to arrays that are ! always out of bounds. This warning is enabled by '-Wall'. ! '-Warray-bounds=1' ! This is the warning level of '-Warray-bounds' and is enabled ! by '-Wall'; higher levels are not, and must be explicitly requested. ! '-Warray-bounds=2' This warning level also warns about out of bounds access for arrays at the end of a struct and for arrays accessed through ! pointers. This warning level may give a larger number of false positives and is deactivated by default. ! '-Wbool-compare' Warn about boolean expression compared with an integer value ! different from 'true'/'false'. For instance, the following comparison is always false: int n = 5; ... if ((n > 1) == 2) { ... } ! This warning is enabled by '-Wall'. ! '-Wduplicated-cond' Warn about duplicated conditions in an if-else-if chain. For instance, warn for the following code: if (p->q != NULL) { ... } else if (p->q != NULL) { ... } ! '-Wframe-address' ! Warn when the '__builtin_frame_address' or ! '__builtin_return_address' is called with an argument greater than 0. Such calls may return indeterminate values or crash the ! program. The warning is included in '-Wall'. ! '-Wno-discarded-qualifiers (C and Objective-C only)' Do not warn if type qualifiers on pointers are being discarded. ! Typically, the compiler warns if a 'const char *' variable is ! passed to a function that takes a 'char *' parameter. This option can be used to suppress such a warning. ! '-Wno-discarded-array-qualifiers (C and Objective-C only)' Do not warn if type qualifiers on arrays which are pointer targets ! are being discarded. Typically, the compiler warns if a 'const int ! (*)[]' variable is passed to a function that takes a 'int (*)[]' parameter. This option can be used to suppress such a warning. ! '-Wno-incompatible-pointer-types (C and Objective-C only)' Do not warn when there is a conversion between pointers that have incompatible types. This warning is for cases not covered by ! '-Wno-pointer-sign', which warns for pointer argument passing or assignment with different signedness. ! '-Wno-int-conversion (C and Objective-C only)' Do not warn about incompatible integer to pointer and pointer to integer conversions. This warning is about implicit conversions; ! for explicit conversions the warnings '-Wno-int-to-pointer-cast' ! and '-Wno-pointer-to-int-cast' may be used. ! '-Wno-div-by-zero' Do not warn about compile-time integer division by zero. ! Floating-point division by zero is not warned about, as it can be a ! legitimate way of obtaining infinities and NaNs. ! '-Wsystem-headers' Print warning messages for constructs found in system header files. Warnings from system headers are normally suppressed, on the assumption that they usually do not indicate real problems and would only make the compiler output harder to read. Using this command-line option tells GCC to emit warnings from system headers ! as if they occurred in user code. However, note that using '-Wall' ! in conjunction with this option does _not_ warn about unknown ! pragmas in system headers--for that, '-Wunknown-pragmas' must also ! be used. ! '-Wtautological-compare' Warn if a self-comparison always evaluates to true or false. This warning detects various mistakes such as: int i = 1; ... if (i > i) { ... } ! This warning is enabled by '-Wall'. ! '-Wtrampolines' Warn about trampolines generated for pointers to nested functions. A trampoline is a small piece of data or code that is created at run time on the stack when the address of a nested function is --- 4323,4510 ---- loop requires, in particular when determining whether a loop will be executed at all. ! `-Wstrict-overflow=1' ! Warn about cases that are both questionable and easy to ! avoid. For example, with `-fstrict-overflow', the compiler ! simplifies `x + 1 > x' to `1'. This level of ! `-Wstrict-overflow' is enabled by `-Wall'; higher levels are ! not, and must be explicitly requested. ! `-Wstrict-overflow=2' Also warn about other cases where a comparison is simplified ! to a constant. For example: `abs (x) >= 0'. This can only be ! simplified when `-fstrict-overflow' is in effect, because ! `abs (INT_MIN)' overflows to `INT_MIN', which is less than ! zero. `-Wstrict-overflow' (with no level) is the same as ! `-Wstrict-overflow=2'. ! `-Wstrict-overflow=3' Also warn about other cases where a comparison is simplified. ! For example: `x + 1 > 1' is simplified to `x > 0'. ! `-Wstrict-overflow=4' ! Also warn about other simplifications not covered by the ! above cases. For example: `(x * 10) / 5' is simplified to `x ! * 2'. ! `-Wstrict-overflow=5' ! Also warn about cases where the compiler reduces the ! magnitude of a constant involved in a comparison. For ! example: `x + 2 > y' is simplified to `x + 1 >= y'. This is ! reported only at the highest warning level because this ! simplification applies to many comparisons, so this warning ! level gives a very large number of false positives. ! `-Wsuggest-attribute=[pure|const|noreturn|format]' ! Warn for cases where adding an attribute may be beneficial. The attributes currently supported are listed below. ! `-Wsuggest-attribute=pure' ! `-Wsuggest-attribute=const' ! `-Wsuggest-attribute=noreturn' Warn about functions that might be candidates for attributes ! `pure', `const' or `noreturn'. The compiler only warns for functions visible in other compilation units or (in the case ! of `pure' and `const') if it cannot prove that the function ! returns normally. A function returns normally if it doesn't contain an infinite loop or return abnormally by throwing, ! calling `abort' or trapping. This analysis requires option ! `-fipa-pure-const', which is enabled by default at `-O' and higher. Higher optimization levels improve the accuracy of the analysis. ! `-Wsuggest-attribute=format' ! `-Wmissing-format-attribute' Warn about function pointers that might be candidates for ! `format' attributes. Note these are only possible ! candidates, not absolute ones. GCC guesses that function ! pointers with `format' attributes that are used in ! assignment, initialization, parameter passing or return ! statements should have a corresponding `format' attribute in ! the resulting type. I.e. the left-hand side of the ! assignment or initialization, the type of the parameter ! variable, or the return type of the containing function ! respectively should also have a `format' attribute to avoid ! the warning. GCC also warns about function definitions that might be ! candidates for `format' attributes. Again, these are only ! possible candidates. GCC guesses that `format' attributes might be appropriate for any function that calls a function ! like `vprintf' or `vscanf', but this might not always be the ! case, and some functions for which `format' attributes are appropriate may not be detected. ! `-Wsuggest-final-types' Warn about types with virtual methods where code quality would be ! improved if the type were declared with the C++11 `final' specifier, or, if possible, declared in an anonymous namespace. This allows GCC to more aggressively devirtualize the polymorphic ! calls. This warning is more effective with link time optimization, where the information about the class hierarchy graph is more complete. ! `-Wsuggest-final-methods' Warn about virtual methods where code quality would be improved if ! the method were declared with the C++11 `final' specifier, or, if possible, its type were declared in an anonymous namespace or with ! the `final' specifier. This warning is more effective with link time optimization, where the information about the class hierarchy ! graph is more complete. It is recommended to first consider ! suggestions of `-Wsuggest-final-types' and then rebuild with new annotations. ! `-Wsuggest-override' Warn about overriding virtual functions that are not marked with the override keyword. ! `-Warray-bounds' ! `-Warray-bounds=N' ! This option is only active when `-ftree-vrp' is active (default ! for `-O2' and above). It warns about subscripts to arrays that are ! always out of bounds. This warning is enabled by `-Wall'. ! `-Warray-bounds=1' ! This is the warning level of `-Warray-bounds' and is enabled ! by `-Wall'; higher levels are not, and must be explicitly requested. ! `-Warray-bounds=2' This warning level also warns about out of bounds access for arrays at the end of a struct and for arrays accessed through ! pointers. This warning level may give a larger number of false positives and is deactivated by default. ! `-Wbool-compare' Warn about boolean expression compared with an integer value ! different from `true'/`false'. For instance, the following comparison is always false: int n = 5; ... if ((n > 1) == 2) { ... } ! This warning is enabled by `-Wall'. ! `-Wduplicated-cond' Warn about duplicated conditions in an if-else-if chain. For instance, warn for the following code: if (p->q != NULL) { ... } else if (p->q != NULL) { ... } ! `-Wframe-address' ! Warn when the `__builtin_frame_address' or ! `__builtin_return_address' is called with an argument greater than 0. Such calls may return indeterminate values or crash the ! program. The warning is included in `-Wall'. ! `-Wno-discarded-qualifiers (C and Objective-C only)' Do not warn if type qualifiers on pointers are being discarded. ! Typically, the compiler warns if a `const char *' variable is ! passed to a function that takes a `char *' parameter. This option can be used to suppress such a warning. ! `-Wno-discarded-array-qualifiers (C and Objective-C only)' Do not warn if type qualifiers on arrays which are pointer targets ! are being discarded. Typically, the compiler warns if a `const int ! (*)[]' variable is passed to a function that takes a `int (*)[]' parameter. This option can be used to suppress such a warning. ! `-Wno-incompatible-pointer-types (C and Objective-C only)' Do not warn when there is a conversion between pointers that have incompatible types. This warning is for cases not covered by ! `-Wno-pointer-sign', which warns for pointer argument passing or assignment with different signedness. ! `-Wno-int-conversion (C and Objective-C only)' Do not warn about incompatible integer to pointer and pointer to integer conversions. This warning is about implicit conversions; ! for explicit conversions the warnings `-Wno-int-to-pointer-cast' ! and `-Wno-pointer-to-int-cast' may be used. ! `-Wno-div-by-zero' Do not warn about compile-time integer division by zero. ! Floating-point division by zero is not warned about, as it can be ! a legitimate way of obtaining infinities and NaNs. ! `-Wsystem-headers' Print warning messages for constructs found in system header files. Warnings from system headers are normally suppressed, on the assumption that they usually do not indicate real problems and would only make the compiler output harder to read. Using this command-line option tells GCC to emit warnings from system headers ! as if they occurred in user code. However, note that using ! `-Wall' in conjunction with this option does _not_ warn about ! unknown pragmas in system headers--for that, `-Wunknown-pragmas' ! must also be used. ! `-Wtautological-compare' Warn if a self-comparison always evaluates to true or false. This warning detects various mistakes such as: int i = 1; ... if (i > i) { ... } ! This warning is enabled by `-Wall'. ! `-Wtrampolines' Warn about trampolines generated for pointers to nested functions. A trampoline is a small piece of data or code that is created at run time on the stack when the address of a nested function is *************** compiler warns that an unrecognized opti *** 4483,4489 **** and thus requires the stack to be made executable in order for the program to work properly. ! '-Wfloat-equal' Warn if floating-point values are used in equality comparisons. The idea behind this is that sometimes it is convenient (for the --- 4514,4520 ---- and thus requires the stack to be made executable in order for the program to work properly. ! `-Wfloat-equal' Warn if floating-point values are used in equality comparisons. The idea behind this is that sometimes it is convenient (for the *************** compiler warns that an unrecognized opti *** 4492,4504 **** need to compute (by analyzing the code, or in some other way) the maximum or likely maximum error that the computation introduces, and allow for it when performing comparisons (and when producing ! output, but that's a different problem). In particular, instead of ! testing for equality, you should check to see whether the two values have ranges that overlap; and this is done with the relational operators, so equality comparisons are probably mistaken. ! '-Wtraditional (C and Objective-C only)' Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and/or problematic constructs that --- 4523,4535 ---- need to compute (by analyzing the code, or in some other way) the maximum or likely maximum error that the computation introduces, and allow for it when performing comparisons (and when producing ! output, but that's a different problem). In particular, instead ! of testing for equality, you should check to see whether the two values have ranges that overlap; and this is done with the relational operators, so equality comparisons are probably mistaken. ! `-Wtraditional (C and Objective-C only)' Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and/or problematic constructs that *************** compiler warns that an unrecognized opti *** 4510,4543 **** * In traditional C, some preprocessor directives did not exist. Traditional preprocessors only considered a line to be a ! directive if the '#' appeared in column 1 on the line. ! Therefore '-Wtraditional' warns about directives that ! traditional C understands but ignores because the '#' does not ! appear as the first character on the line. It also suggests ! you hide directives like '#pragma' not understood by traditional C by indenting them. Some traditional ! implementations do not recognize '#elif', so this option suggests avoiding it altogether. * A function-like macro that appears without arguments. * The unary plus operator. ! * The 'U' integer constant suffix, or the 'F' or 'L' ! floating-point constant suffixes. (Traditional C does support ! the 'L' suffix on integer constants.) Note, these suffixes ! appear in macros defined in the system headers of most modern ! systems, e.g. the '_MIN'/'_MAX' macros in ''. Use ! of these macros in user code might normally lead to spurious ! warnings, however GCC's integrated preprocessor has enough ! context to avoid warning in these cases. * A function declared external in one block and then used after the end of the block. ! * A 'switch' statement has an operand of type 'long'. ! * A non-'static' function declaration follows a 'static' one. This construct is not accepted by some traditional C compilers. --- 4541,4575 ---- * In traditional C, some preprocessor directives did not exist. Traditional preprocessors only considered a line to be a ! directive if the `#' appeared in column 1 on the line. ! Therefore `-Wtraditional' warns about directives that ! traditional C understands but ignores because the `#' does ! not appear as the first character on the line. It also ! suggests you hide directives like `#pragma' not understood by traditional C by indenting them. Some traditional ! implementations do not recognize `#elif', so this option suggests avoiding it altogether. * A function-like macro that appears without arguments. * The unary plus operator. ! * The `U' integer constant suffix, or the `F' or `L' ! floating-point constant suffixes. (Traditional C does ! support the `L' suffix on integer constants.) Note, these ! suffixes appear in macros defined in the system headers of ! most modern systems, e.g. the `_MIN'/`_MAX' macros in ! `'. Use of these macros in user code might ! normally lead to spurious warnings, however GCC's integrated ! preprocessor has enough context to avoid warning in these ! cases. * A function declared external in one block and then used after the end of the block. ! * A `switch' statement has an operand of type `long'. ! * A non-`static' function declaration follows a `static' one. This construct is not accepted by some traditional C compilers. *************** compiler warns that an unrecognized opti *** 4557,4753 **** * Initialization of unions. If the initializer is zero, the warning is omitted. This is done under the assumption that the zero initializer in user code appears conditioned on e.g. ! '__STDC__' to avoid missing initializer warnings and relies on ! default initialization to zero in the traditional C case. * Conversions by prototypes between fixed/floating-point values and vice versa. The absence of these prototypes when ! compiling with traditional C causes serious problems. This is ! a subset of the possible conversion warnings; for the full set ! use '-Wtraditional-conversion'. * Use of ISO C style function definitions. This warning intentionally is _not_ issued for prototype declarations or ! variadic functions because these ISO C features appear in your ! code when using libiberty's traditional C compatibility ! macros, 'PARAMS' and 'VPARAMS'. This warning is also bypassed ! for nested functions because that feature is already a GCC ! extension and thus not relevant to traditional C compatibility. ! '-Wtraditional-conversion (C and Objective-C only)' ! Warn if a prototype causes a type conversion that is different from ! what would happen to the same argument in the absence of a prototype. This includes conversions of fixed point to floating ! and vice versa, and conversions changing the width or signedness of ! a fixed-point argument except when the same as the default promotion. ! '-Wdeclaration-after-statement (C and Objective-C only)' Warn when a declaration is found after a statement in a block. This construct, known from C++, was introduced with ISO C99 and is by default allowed in GCC. It is not supported by ISO C90. *Note Mixed Declarations::. ! '-Wundef' ! Warn if an undefined identifier is evaluated in an '#if' directive. ! '-Wno-endif-labels' ! Do not warn whenever an '#else' or an '#endif' are followed by text. ! '-Wshadow' Warn whenever a local variable or type declaration shadows another variable, parameter, type, class member (in C++), or instance variable (in Objective-C) or whenever a built-in function is ! shadowed. Note that in C++, the compiler warns if a local variable shadows an explicit typedef, but not if it shadows a struct/class/enum. ! '-Wno-shadow-ivar (Objective-C only)' Do not warn whenever a local variable shadows an instance variable in an Objective-C method. ! '-Wlarger-than=LEN' Warn whenever an object of larger than LEN bytes is defined. ! '-Wframe-larger-than=LEN' ! Warn if the size of a function frame is larger than LEN bytes. The ! computation done to determine the stack frame size is approximate ! and not conservative. The actual requirements may be somewhat ! greater than LEN even if you do not get a warning. In addition, ! any space allocated via 'alloca', variable-length arrays, or ! related constructs is not included by the compiler when determining ! whether or not to issue a warning. ! '-Wno-free-nonheap-object' Do not warn when attempting to free an object that was not allocated on the heap. ! '-Wstack-usage=LEN' Warn if the stack usage of a function might be larger than LEN bytes. The computation done to determine the stack usage is ! conservative. Any space allocated via 'alloca', variable-length arrays, or related constructs is included by the compiler when determining whether or not to issue a warning. ! The message is in keeping with the output of '-fstack-usage'. * If the stack usage is fully static but exceeds the specified amount, it's: warning: stack usage is 1120 bytes * If the stack usage is (partly) dynamic but bounded, it's: warning: stack usage might be 1648 bytes * If the stack usage is (partly) dynamic and not bounded, it's: warning: stack usage might be unbounded ! '-Wunsafe-loop-optimizations' Warn if the loop cannot be optimized because the compiler cannot assume anything on the bounds of the loop indices. With ! '-funsafe-loop-optimizations' warn if the compiler makes such assumptions. ! '-Wno-pedantic-ms-format (MinGW targets only)' ! When used in combination with '-Wformat' and '-pedantic' without GNU extensions, this option disables the warnings about non-ISO ! 'printf' / 'scanf' format width specifiers 'I32', 'I64', and 'I' used on Windows targets, which depend on the MS runtime. ! '-Wplacement-new' ! '-Wplacement-new=N' Warn about placement new expressions with undefined behavior, such ! as constructing an object in a buffer that is smaller than the type ! of the object. For example, the placement new expression below is ! diagnosed because it attempts to construct an array of 64 integers ! in a buffer only 64 bytes large. char buf [64]; new (buf) int[64]; This warning is enabled by default. ! '-Wplacement-new=1' ! This is the default warning level of '-Wplacement-new'. At this level the warning is not issued for some strictly undefined constructs that GCC allows as extensions for compatibility with legacy code. For example, the following ! 'new' expression is not diagnosed at this level even though it ! has undefined behavior according to the C++ standard because ! it writes past the end of the one-element array. struct S { int n, a[1]; }; S *s = (S *)malloc (sizeof *s + 31 * sizeof s->a[0]); new (s->a)int [32](); ! '-Wplacement-new=2' At this level, in addition to diagnosing all the same constructs as at level 1, a diagnostic is also issued for ! placement new expressions that construct an object in the last ! member of structure whose type is an array of a single element ! and whose size is less than the size of the object being ! constructed. While the previous example would be diagnosed, ! the following construct makes use of the flexible member array ! extension to avoid the warning at level 2. struct S { int n, a[]; }; S *s = (S *)malloc (sizeof *s + 32 * sizeof s->a[0]); new (s->a)int [32](); ! '-Wpointer-arith' Warn about anything that depends on the "size of" a function type ! or of 'void'. GNU C assigns these types a size of 1, for ! convenience in calculations with 'void *' pointers and pointers to functions. In C++, warn also when an arithmetic operation involves ! 'NULL'. This warning is also enabled by '-Wpedantic'. ! '-Wtype-limits' Warn if a comparison is always true or always false due to the limited range of the data type, but do not warn for constant ! expressions. For example, warn if an unsigned variable is compared ! against zero with '<' or '>='. This warning is also enabled by ! '-Wextra'. ! '-Wbad-function-cast (C and Objective-C only)' Warn when a function call is cast to a non-matching type. For example, warn if a call to a function returning an integer type is cast to a pointer type. ! '-Wc90-c99-compat (C and Objective-C only)' Warn about features not present in ISO C90, but present in ISO C99. ! For instance, warn about use of variable length arrays, 'long long' ! type, 'bool' type, compound literals, designated initializers, and ! so on. This option is independent of the standards mode. Warnings ! are disabled in the expression that follows '__extension__'. ! '-Wc99-c11-compat (C and Objective-C only)' Warn about features not present in ISO C99, but present in ISO C11. For instance, warn about use of anonymous structures and unions, ! '_Atomic' type qualifier, '_Thread_local' storage-class specifier, ! '_Alignas' specifier, 'Alignof' operator, '_Generic' keyword, and ! so on. This option is independent of the standards mode. Warnings ! are disabled in the expression that follows '__extension__'. ! '-Wc++-compat (C and Objective-C only)' Warn about ISO C constructs that are outside of the common subset of ISO C and ISO C++, e.g. request for implicit conversion from ! 'void *' to a pointer to non-'void' type. ! '-Wc++11-compat (C++ and Objective-C++ only)' Warn about C++ constructs whose meaning differs between ISO C++ 1998 and ISO C++ 2011, e.g., identifiers in ISO C++ 1998 that are ! keywords in ISO C++ 2011. This warning turns on '-Wnarrowing' and ! is enabled by '-Wall'. ! '-Wc++14-compat (C++ and Objective-C++ only)' Warn about C++ constructs whose meaning differs between ISO C++ ! 2011 and ISO C++ 2014. This warning is enabled by '-Wall'. ! '-Wcast-qual' Warn whenever a pointer is cast so as to remove a type qualifier ! from the target type. For example, warn if a 'const char *' is ! cast to an ordinary 'char *'. Also warn when making a cast that introduces a type qualifier in an ! unsafe way. For example, casting 'char **' to 'const char **' is unsafe, as in this example: /* p is char ** value. */ --- 4589,4790 ---- * Initialization of unions. If the initializer is zero, the warning is omitted. This is done under the assumption that the zero initializer in user code appears conditioned on e.g. ! `__STDC__' to avoid missing initializer warnings and relies ! on default initialization to zero in the traditional C case. * Conversions by prototypes between fixed/floating-point values and vice versa. The absence of these prototypes when ! compiling with traditional C causes serious problems. This ! is a subset of the possible conversion warnings; for the full ! set use `-Wtraditional-conversion'. * Use of ISO C style function definitions. This warning intentionally is _not_ issued for prototype declarations or ! variadic functions because these ISO C features appear in ! your code when using libiberty's traditional C compatibility ! macros, `PARAMS' and `VPARAMS'. This warning is also ! bypassed for nested functions because that feature is already ! a GCC extension and thus not relevant to traditional C compatibility. ! `-Wtraditional-conversion (C and Objective-C only)' ! Warn if a prototype causes a type conversion that is different ! from what would happen to the same argument in the absence of a prototype. This includes conversions of fixed point to floating ! and vice versa, and conversions changing the width or signedness ! of a fixed-point argument except when the same as the default promotion. ! `-Wdeclaration-after-statement (C and Objective-C only)' Warn when a declaration is found after a statement in a block. This construct, known from C++, was introduced with ISO C99 and is by default allowed in GCC. It is not supported by ISO C90. *Note Mixed Declarations::. ! `-Wundef' ! Warn if an undefined identifier is evaluated in an `#if' directive. ! `-Wno-endif-labels' ! Do not warn whenever an `#else' or an `#endif' are followed by text. ! `-Wshadow' Warn whenever a local variable or type declaration shadows another variable, parameter, type, class member (in C++), or instance variable (in Objective-C) or whenever a built-in function is ! shadowed. Note that in C++, the compiler warns if a local variable shadows an explicit typedef, but not if it shadows a struct/class/enum. ! `-Wno-shadow-ivar (Objective-C only)' Do not warn whenever a local variable shadows an instance variable in an Objective-C method. ! `-Wlarger-than=LEN' Warn whenever an object of larger than LEN bytes is defined. ! `-Wframe-larger-than=LEN' ! Warn if the size of a function frame is larger than LEN bytes. ! The computation done to determine the stack frame size is ! approximate and not conservative. The actual requirements may be ! somewhat greater than LEN even if you do not get a warning. In ! addition, any space allocated via `alloca', variable-length ! arrays, or related constructs is not included by the compiler when ! determining whether or not to issue a warning. ! `-Wno-free-nonheap-object' Do not warn when attempting to free an object that was not allocated on the heap. ! `-Wstack-usage=LEN' Warn if the stack usage of a function might be larger than LEN bytes. The computation done to determine the stack usage is ! conservative. Any space allocated via `alloca', variable-length arrays, or related constructs is included by the compiler when determining whether or not to issue a warning. ! The message is in keeping with the output of `-fstack-usage'. * If the stack usage is fully static but exceeds the specified amount, it's: warning: stack usage is 1120 bytes + * If the stack usage is (partly) dynamic but bounded, it's: warning: stack usage might be 1648 bytes + * If the stack usage is (partly) dynamic and not bounded, it's: warning: stack usage might be unbounded ! `-Wunsafe-loop-optimizations' Warn if the loop cannot be optimized because the compiler cannot assume anything on the bounds of the loop indices. With ! `-funsafe-loop-optimizations' warn if the compiler makes such assumptions. ! `-Wno-pedantic-ms-format (MinGW targets only)' ! When used in combination with `-Wformat' and `-pedantic' without GNU extensions, this option disables the warnings about non-ISO ! `printf' / `scanf' format width specifiers `I32', `I64', and `I' used on Windows targets, which depend on the MS runtime. ! `-Wplacement-new' ! `-Wplacement-new=N' Warn about placement new expressions with undefined behavior, such ! as constructing an object in a buffer that is smaller than the ! type of the object. For example, the placement new expression ! below is diagnosed because it attempts to construct an array of 64 ! integers in a buffer only 64 bytes large. char buf [64]; new (buf) int[64]; This warning is enabled by default. ! `-Wplacement-new=1' ! This is the default warning level of `-Wplacement-new'. At this level the warning is not issued for some strictly undefined constructs that GCC allows as extensions for compatibility with legacy code. For example, the following ! `new' expression is not diagnosed at this level even though ! it has undefined behavior according to the C++ standard ! because it writes past the end of the one-element array. struct S { int n, a[1]; }; S *s = (S *)malloc (sizeof *s + 31 * sizeof s->a[0]); new (s->a)int [32](); ! `-Wplacement-new=2' At this level, in addition to diagnosing all the same constructs as at level 1, a diagnostic is also issued for ! placement new expressions that construct an object in the ! last member of structure whose type is an array of a single ! element and whose size is less than the size of the object ! being constructed. While the previous example would be ! diagnosed, the following construct makes use of the flexible ! member array extension to avoid the warning at level 2. struct S { int n, a[]; }; S *s = (S *)malloc (sizeof *s + 32 * sizeof s->a[0]); new (s->a)int [32](); ! ! `-Wpointer-arith' Warn about anything that depends on the "size of" a function type ! or of `void'. GNU C assigns these types a size of 1, for ! convenience in calculations with `void *' pointers and pointers to functions. In C++, warn also when an arithmetic operation involves ! `NULL'. This warning is also enabled by `-Wpedantic'. ! `-Wtype-limits' Warn if a comparison is always true or always false due to the limited range of the data type, but do not warn for constant ! expressions. For example, warn if an unsigned variable is ! compared against zero with `<' or `>='. This warning is also ! enabled by `-Wextra'. ! `-Wbad-function-cast (C and Objective-C only)' Warn when a function call is cast to a non-matching type. For example, warn if a call to a function returning an integer type is cast to a pointer type. ! `-Wc90-c99-compat (C and Objective-C only)' Warn about features not present in ISO C90, but present in ISO C99. ! For instance, warn about use of variable length arrays, `long long' ! type, `bool' type, compound literals, designated initializers, and ! so on. This option is independent of the standards mode. ! Warnings are disabled in the expression that follows ! `__extension__'. ! `-Wc99-c11-compat (C and Objective-C only)' Warn about features not present in ISO C99, but present in ISO C11. For instance, warn about use of anonymous structures and unions, ! `_Atomic' type qualifier, `_Thread_local' storage-class specifier, ! `_Alignas' specifier, `Alignof' operator, `_Generic' keyword, and ! so on. This option is independent of the standards mode. ! Warnings are disabled in the expression that follows ! `__extension__'. ! `-Wc++-compat (C and Objective-C only)' Warn about ISO C constructs that are outside of the common subset of ISO C and ISO C++, e.g. request for implicit conversion from ! `void *' to a pointer to non-`void' type. ! `-Wc++11-compat (C++ and Objective-C++ only)' Warn about C++ constructs whose meaning differs between ISO C++ 1998 and ISO C++ 2011, e.g., identifiers in ISO C++ 1998 that are ! keywords in ISO C++ 2011. This warning turns on `-Wnarrowing' and ! is enabled by `-Wall'. ! `-Wc++14-compat (C++ and Objective-C++ only)' Warn about C++ constructs whose meaning differs between ISO C++ ! 2011 and ISO C++ 2014. This warning is enabled by `-Wall'. ! `-Wcast-qual' Warn whenever a pointer is cast so as to remove a type qualifier ! from the target type. For example, warn if a `const char *' is ! cast to an ordinary `char *'. Also warn when making a cast that introduces a type qualifier in an ! unsafe way. For example, casting `char **' to `const char **' is unsafe, as in this example: /* p is char ** value. */ *************** compiler warns that an unrecognized opti *** 4757,4883 **** /* Now char** pointer points to read-only memory. */ **p = 'b'; ! '-Wcast-align' ! Warn whenever a pointer is cast such that the required alignment of ! the target is increased. For example, warn if a 'char *' is cast ! to an 'int *' on machines where integers can only be accessed at ! two- or four-byte boundaries. ! '-Wwrite-strings' ! When compiling C, give string constants the type 'const ! char[LENGTH]' so that copying the address of one into a non-'const' ! 'char *' pointer produces a warning. These warnings help you find ! at compile time code that can try to write into a string constant, ! but only if you have been very careful about using 'const' in ! declarations and prototypes. Otherwise, it is just a nuisance. ! This is why we did not make '-Wall' request these warnings. When compiling C++, warn about the deprecated conversion from ! string literals to 'char *'. This warning is enabled by default for C++ programs. ! '-Wclobbered' ! Warn for variables that might be changed by 'longjmp' or 'vfork'. ! This warning is also enabled by '-Wextra'. ! '-Wconditionally-supported (C++ and Objective-C++ only)' Warn for conditionally-supported (C++11 [intro.defs]) constructs. ! '-Wconversion' ! Warn for implicit conversions that may alter a value. This ! includes conversions between real and integer, like 'abs (x)' when ! 'x' is 'double'; conversions between signed and unsigned, like ! 'unsigned ui = -1'; and conversions to smaller types, like 'sqrtf ! (M_PI)'. Do not warn for explicit casts like 'abs ((int) x)' and ! 'ui = (unsigned) -1', or if the value is not changed by the ! conversion like in 'abs (2.0)'. Warnings about conversions between ! signed and unsigned integers can be disabled by using ! '-Wno-sign-conversion'. For C++, also warn for confusing overload resolution for user-defined conversions; and conversions that never use a type ! conversion operator: conversions to 'void', the same type, a base ! class or a reference to them. Warnings about conversions between signed and unsigned integers are disabled by default in C++ unless ! '-Wsign-conversion' is explicitly enabled. ! '-Wno-conversion-null (C++ and Objective-C++ only)' ! Do not warn for conversions between 'NULL' and non-pointer types. ! '-Wconversion-null' is enabled by default. ! '-Wzero-as-null-pointer-constant (C++ and Objective-C++ only)' ! Warn when a literal '0' is used as null pointer constant. This can ! be useful to facilitate the conversion to 'nullptr' in C++11. ! '-Wsubobject-linkage (C++ and Objective-C++ only)' Warn if a class type has a base or a field whose type uses the anonymous namespace or depends on a type with no linkage. If a ! type A depends on a type B with no or internal linkage, defining it ! in multiple translation units would be an ODR violation because the ! meaning of B is different in each translation unit. If A only appears in a single translation unit, the best way to silence the warning is to give it internal linkage by putting it in an anonymous namespace as well. The compiler doesn't give this warning for types defined in the main .C file, as those are ! unlikely to have multiple definitions. '-Wsubobject-linkage' is enabled by default. ! '-Wdate-time' ! Warn when macros '__TIME__', '__DATE__' or '__TIMESTAMP__' are encountered as they might prevent bit-wise-identical reproducible compilations. ! '-Wdelete-incomplete (C++ and Objective-C++ only)' Warn when deleting a pointer to incomplete type, which may cause undefined behavior at runtime. This warning is enabled by default. ! '-Wuseless-cast (C++ and Objective-C++ only)' Warn when an expression is casted to its own type. ! '-Wempty-body' ! Warn if an empty body occurs in an 'if', 'else' or 'do while' ! statement. This warning is also enabled by '-Wextra'. ! '-Wenum-compare' Warn about a comparison between values of different enumerated types. In C++ enumeral mismatches in conditional expressions are also diagnosed and the warning is enabled by default. In C this ! warning is enabled by '-Wall'. ! '-Wjump-misses-init (C, Objective-C only)' ! Warn if a 'goto' statement or a 'switch' statement jumps forward across the initialization of a variable, or jumps backward to a label after the variable has been initialized. This only warns about variables that are initialized when they are declared. This warning is only supported for C and Objective-C; in C++ this sort of branch is an error in any case. ! '-Wjump-misses-init' is included in '-Wc++-compat'. It can be ! disabled with the '-Wno-jump-misses-init' option. ! '-Wsign-compare' Warn when a comparison between signed and unsigned values could produce an incorrect result when the signed value is converted to ! unsigned. In C++, this warning is also enabled by '-Wall'. In C, ! it is also enabled by '-Wextra'. ! '-Wsign-conversion' Warn for implicit conversions that may change the sign of an integer value, like assigning a signed integer expression to an ! unsigned integer variable. An explicit cast silences the warning. ! In C, this option is enabled also by '-Wconversion'. ! '-Wfloat-conversion' Warn for implicit conversions that reduce the precision of a real value. This includes conversions from real to integer, and from higher precision real to lower precision real values. This option ! is also enabled by '-Wconversion'. ! '-Wno-scalar-storage-order' Do not warn on suspicious constructs involving reverse scalar storage order. ! '-Wsized-deallocation (C++ and Objective-C++ only)' Warn about a definition of an unsized deallocation function void operator delete (void *) noexcept; void operator delete[] (void *) noexcept; --- 4794,4921 ---- /* Now char** pointer points to read-only memory. */ **p = 'b'; ! `-Wcast-align' ! Warn whenever a pointer is cast such that the required alignment ! of the target is increased. For example, warn if a `char *' is ! cast to an `int *' on machines where integers can only be accessed ! at two- or four-byte boundaries. ! `-Wwrite-strings' ! When compiling C, give string constants the type `const ! char[LENGTH]' so that copying the address of one into a ! non-`const' `char *' pointer produces a warning. These warnings ! help you find at compile time code that can try to write into a ! string constant, but only if you have been very careful about ! using `const' in declarations and prototypes. Otherwise, it is ! just a nuisance. This is why we did not make `-Wall' request these ! warnings. When compiling C++, warn about the deprecated conversion from ! string literals to `char *'. This warning is enabled by default for C++ programs. ! `-Wclobbered' ! Warn for variables that might be changed by `longjmp' or `vfork'. ! This warning is also enabled by `-Wextra'. ! `-Wconditionally-supported (C++ and Objective-C++ only)' Warn for conditionally-supported (C++11 [intro.defs]) constructs. ! `-Wconversion' ! Warn for implicit conversions that may alter a value. This includes ! conversions between real and integer, like `abs (x)' when `x' is ! `double'; conversions between signed and unsigned, like `unsigned ! ui = -1'; and conversions to smaller types, like `sqrtf (M_PI)'. ! Do not warn for explicit casts like `abs ((int) x)' and `ui = ! (unsigned) -1', or if the value is not changed by the conversion ! like in `abs (2.0)'. Warnings about conversions between signed ! and unsigned integers can be disabled by using ! `-Wno-sign-conversion'. For C++, also warn for confusing overload resolution for user-defined conversions; and conversions that never use a type ! conversion operator: conversions to `void', the same type, a base ! class or a reference to them. Warnings about conversions between signed and unsigned integers are disabled by default in C++ unless ! `-Wsign-conversion' is explicitly enabled. ! `-Wno-conversion-null (C++ and Objective-C++ only)' ! Do not warn for conversions between `NULL' and non-pointer types. ! `-Wconversion-null' is enabled by default. ! `-Wzero-as-null-pointer-constant (C++ and Objective-C++ only)' ! Warn when a literal `0' is used as null pointer constant. This can ! be useful to facilitate the conversion to `nullptr' in C++11. ! `-Wsubobject-linkage (C++ and Objective-C++ only)' Warn if a class type has a base or a field whose type uses the anonymous namespace or depends on a type with no linkage. If a ! type A depends on a type B with no or internal linkage, defining ! it in multiple translation units would be an ODR violation because ! the meaning of B is different in each translation unit. If A only appears in a single translation unit, the best way to silence the warning is to give it internal linkage by putting it in an anonymous namespace as well. The compiler doesn't give this warning for types defined in the main .C file, as those are ! unlikely to have multiple definitions. `-Wsubobject-linkage' is enabled by default. ! `-Wdate-time' ! Warn when macros `__TIME__', `__DATE__' or `__TIMESTAMP__' are encountered as they might prevent bit-wise-identical reproducible compilations. ! `-Wdelete-incomplete (C++ and Objective-C++ only)' Warn when deleting a pointer to incomplete type, which may cause undefined behavior at runtime. This warning is enabled by default. ! `-Wuseless-cast (C++ and Objective-C++ only)' Warn when an expression is casted to its own type. ! `-Wempty-body' ! Warn if an empty body occurs in an `if', `else' or `do while' ! statement. This warning is also enabled by `-Wextra'. ! `-Wenum-compare' Warn about a comparison between values of different enumerated types. In C++ enumeral mismatches in conditional expressions are also diagnosed and the warning is enabled by default. In C this ! warning is enabled by `-Wall'. ! `-Wjump-misses-init (C, Objective-C only)' ! Warn if a `goto' statement or a `switch' statement jumps forward across the initialization of a variable, or jumps backward to a label after the variable has been initialized. This only warns about variables that are initialized when they are declared. This warning is only supported for C and Objective-C; in C++ this sort of branch is an error in any case. ! `-Wjump-misses-init' is included in `-Wc++-compat'. It can be ! disabled with the `-Wno-jump-misses-init' option. ! `-Wsign-compare' Warn when a comparison between signed and unsigned values could produce an incorrect result when the signed value is converted to ! unsigned. In C++, this warning is also enabled by `-Wall'. In C, ! it is also enabled by `-Wextra'. ! `-Wsign-conversion' Warn for implicit conversions that may change the sign of an integer value, like assigning a signed integer expression to an ! unsigned integer variable. An explicit cast silences the warning. ! In C, this option is enabled also by `-Wconversion'. ! `-Wfloat-conversion' Warn for implicit conversions that reduce the precision of a real value. This includes conversions from real to integer, and from higher precision real to lower precision real values. This option ! is also enabled by `-Wconversion'. ! `-Wno-scalar-storage-order' Do not warn on suspicious constructs involving reverse scalar storage order. ! `-Wsized-deallocation (C++ and Objective-C++ only)' Warn about a definition of an unsized deallocation function void operator delete (void *) noexcept; void operator delete[] (void *) noexcept; *************** compiler warns that an unrecognized opti *** 4885,4939 **** function void operator delete (void *, std::size_t) noexcept; void operator delete[] (void *, std::size_t) noexcept; ! or vice versa. Enabled by '-Wextra' along with ! '-fsized-deallocation'. ! '-Wsizeof-pointer-memaccess' Warn for suspicious length parameters to certain string and memory ! built-in functions if the argument uses 'sizeof'. This warning ! warns e.g. about 'memset (ptr, 0, sizeof (ptr));' if 'ptr' is not an array, but a pointer, and suggests a possible fix, or about ! 'memcpy (&foo, ptr, sizeof (&foo));'. This warning is enabled by ! '-Wall'. ! '-Wsizeof-array-argument' ! Warn when the 'sizeof' operator is applied to a parameter that is declared as an array in a function definition. This warning is enabled by default for C and C++ programs. ! '-Wmemset-transposed-args' ! Warn for suspicious calls to the 'memset' built-in function, if the second argument is not zero and the third argument is zero. This ! warns e.g. about 'memset (buf, sizeof buf, 0)' where most probably ! 'memset (buf, 0, sizeof buf)' was meant instead. The diagnostics is only emitted if the third argument is literal zero. If it is some expression that is folded to zero, a cast of zero to some type, etc., it is far less likely that the user has mistakenly ! exchanged the arguments and no warning is emitted. This warning is ! enabled by '-Wall'. ! '-Waddress' ! Warn about suspicious uses of memory addresses. These include ! using the address of a function in a conditional expression, such ! as 'void func(void); if (func)', and comparisons against the memory ! address of a string literal, such as 'if (x == "abc")'. Such uses typically indicate a programmer error: the address of a function always evaluates to true, so their use in a conditional usually indicate that the programmer forgot the parentheses in a function call; and comparisons against string literals result in unspecified behavior and are not portable in C, so they usually indicate that ! the programmer intended to use 'strcmp'. This warning is enabled ! by '-Wall'. ! '-Wlogical-op' Warn about suspicious uses of logical operators in expressions. This includes using logical operators in contexts where a bit-wise ! operator is likely to be expected. Also warns when the operands of ! a logical operator are the same: extern int a; if (a < 0 && a < 0) { ... } ! '-Wlogical-not-parentheses' Warn about logical not used on the left hand side operand of a comparison. This option does not warn if the RHS operand is of a boolean type. Its purpose is to detect suspicious code like the --- 4923,4977 ---- function void operator delete (void *, std::size_t) noexcept; void operator delete[] (void *, std::size_t) noexcept; ! or vice versa. Enabled by `-Wextra' along with ! `-fsized-deallocation'. ! `-Wsizeof-pointer-memaccess' Warn for suspicious length parameters to certain string and memory ! built-in functions if the argument uses `sizeof'. This warning ! warns e.g. about `memset (ptr, 0, sizeof (ptr));' if `ptr' is not an array, but a pointer, and suggests a possible fix, or about ! `memcpy (&foo, ptr, sizeof (&foo));'. This warning is enabled by ! `-Wall'. ! `-Wsizeof-array-argument' ! Warn when the `sizeof' operator is applied to a parameter that is declared as an array in a function definition. This warning is enabled by default for C and C++ programs. ! `-Wmemset-transposed-args' ! Warn for suspicious calls to the `memset' built-in function, if the second argument is not zero and the third argument is zero. This ! warns e.g. about `memset (buf, sizeof buf, 0)' where most probably ! `memset (buf, 0, sizeof buf)' was meant instead. The diagnostics is only emitted if the third argument is literal zero. If it is some expression that is folded to zero, a cast of zero to some type, etc., it is far less likely that the user has mistakenly ! exchanged the arguments and no warning is emitted. This warning ! is enabled by `-Wall'. ! `-Waddress' ! Warn about suspicious uses of memory addresses. These include using ! the address of a function in a conditional expression, such as ! `void func(void); if (func)', and comparisons against the memory ! address of a string literal, such as `if (x == "abc")'. Such uses typically indicate a programmer error: the address of a function always evaluates to true, so their use in a conditional usually indicate that the programmer forgot the parentheses in a function call; and comparisons against string literals result in unspecified behavior and are not portable in C, so they usually indicate that ! the programmer intended to use `strcmp'. This warning is enabled ! by `-Wall'. ! `-Wlogical-op' Warn about suspicious uses of logical operators in expressions. This includes using logical operators in contexts where a bit-wise ! operator is likely to be expected. Also warns when the operands ! of a logical operator are the same: extern int a; if (a < 0 && a < 0) { ... } ! `-Wlogical-not-parentheses' Warn about logical not used on the left hand side operand of a comparison. This option does not warn if the RHS operand is of a boolean type. Its purpose is to detect suspicious code like the *************** compiler warns that an unrecognized opti *** 4946,4999 **** parentheses: if ((!a) > 1) { ... } ! This warning is enabled by '-Wall'. ! '-Waggregate-return' Warn if any functions that return structures or unions are defined or called. (In languages where you can return an array, this also elicits a warning.) ! '-Wno-aggressive-loop-optimizations' Warn if in a loop with constant number of iterations the compiler detects undefined behavior in some statement during one or more of the iterations. ! '-Wno-attributes' ! Do not warn if an unexpected '__attribute__' is used, such as unrecognized attributes, function attributes applied to variables, etc. This does not stop errors for incorrect use of supported attributes. ! '-Wno-builtin-macro-redefined' Do not warn if certain built-in macros are redefined. This ! suppresses warnings for redefinition of '__TIMESTAMP__', ! '__TIME__', '__DATE__', '__FILE__', and '__BASE_FILE__'. ! '-Wstrict-prototypes (C and Objective-C only)' Warn if a function is declared or defined without specifying the argument types. (An old-style function definition is permitted without a warning if preceded by a declaration that specifies the argument types.) ! '-Wold-style-declaration (C and Objective-C only)' Warn for obsolescent usages, according to the C Standard, in a ! declaration. For example, warn if storage-class specifiers like ! 'static' are not the first things in a declaration. This warning ! is also enabled by '-Wextra'. ! '-Wold-style-definition (C and Objective-C only)' Warn if an old-style function definition is used. A warning is given even if there is a previous prototype. ! '-Wmissing-parameter-type (C and Objective-C only)' A function parameter is declared without a type specifier in K&R-style functions: void foo(bar) { } ! This warning is also enabled by '-Wextra'. ! '-Wmissing-prototypes (C and Objective-C only)' Warn if a global function is defined without a previous prototype declaration. This warning is issued even if the definition itself provides a prototype. Use this option to detect global functions --- 4984,5037 ---- parentheses: if ((!a) > 1) { ... } ! This warning is enabled by `-Wall'. ! `-Waggregate-return' Warn if any functions that return structures or unions are defined or called. (In languages where you can return an array, this also elicits a warning.) ! `-Wno-aggressive-loop-optimizations' Warn if in a loop with constant number of iterations the compiler detects undefined behavior in some statement during one or more of the iterations. ! `-Wno-attributes' ! Do not warn if an unexpected `__attribute__' is used, such as unrecognized attributes, function attributes applied to variables, etc. This does not stop errors for incorrect use of supported attributes. ! `-Wno-builtin-macro-redefined' Do not warn if certain built-in macros are redefined. This ! suppresses warnings for redefinition of `__TIMESTAMP__', ! `__TIME__', `__DATE__', `__FILE__', and `__BASE_FILE__'. ! `-Wstrict-prototypes (C and Objective-C only)' Warn if a function is declared or defined without specifying the argument types. (An old-style function definition is permitted without a warning if preceded by a declaration that specifies the argument types.) ! `-Wold-style-declaration (C and Objective-C only)' Warn for obsolescent usages, according to the C Standard, in a ! declaration. For example, warn if storage-class specifiers like ! `static' are not the first things in a declaration. This warning ! is also enabled by `-Wextra'. ! `-Wold-style-definition (C and Objective-C only)' Warn if an old-style function definition is used. A warning is given even if there is a previous prototype. ! `-Wmissing-parameter-type (C and Objective-C only)' A function parameter is declared without a type specifier in K&R-style functions: void foo(bar) { } ! This warning is also enabled by `-Wextra'. ! `-Wmissing-prototypes (C and Objective-C only)' Warn if a global function is defined without a previous prototype declaration. This warning is issued even if the definition itself provides a prototype. Use this option to detect global functions *************** compiler warns that an unrecognized opti *** 5001,5022 **** This option is not valid for C++ because all function declarations provide prototypes and a non-matching declaration declares an overload rather than conflict with an earlier declaration. Use ! '-Wmissing-declarations' to detect missing declarations in C++. ! '-Wmissing-declarations' Warn if a global function is defined without a previous declaration. Do so even if the definition itself provides a ! prototype. Use this option to detect global functions that are not ! declared in header files. In C, no warnings are issued for functions with previous non-prototype declarations; use ! '-Wmissing-prototypes' to detect missing prototypes. In C++, no warnings are issued for function templates, or for inline functions, or for functions in anonymous namespaces. ! '-Wmissing-field-initializers' Warn if a structure's initializer has some fields missing. For ! example, the following code causes such a warning, because 'x.h' is ! implicitly zero: struct s { int f, g, h; }; struct s x = { 3, 4 }; --- 5039,5060 ---- This option is not valid for C++ because all function declarations provide prototypes and a non-matching declaration declares an overload rather than conflict with an earlier declaration. Use ! `-Wmissing-declarations' to detect missing declarations in C++. ! `-Wmissing-declarations' Warn if a global function is defined without a previous declaration. Do so even if the definition itself provides a ! prototype. Use this option to detect global functions that are ! not declared in header files. In C, no warnings are issued for functions with previous non-prototype declarations; use ! `-Wmissing-prototypes' to detect missing prototypes. In C++, no warnings are issued for function templates, or for inline functions, or for functions in anonymous namespaces. ! `-Wmissing-field-initializers' Warn if a structure's initializer has some fields missing. For ! example, the following code causes such a warning, because `x.h' ! is implicitly zero: struct s { int f, g, h; }; struct s x = { 3, 4 }; *************** compiler warns that an unrecognized opti *** 5033,5134 **** struct s { int f, g, h; }; s x = { }; ! This warning is included in '-Wextra'. To get other '-Wextra' ! warnings without this one, use '-Wextra -Wno-missing-field-initializers'. ! '-Wno-multichar' ! Do not warn if a multicharacter constant (''FOOF'') is used. Usually they indicate a typo in the user's code, as they have implementation-defined values, and should not be used in portable code. ! '-Wnormalized[=]' In ISO C and ISO C++, two identifiers are different if they are different sequences of characters. However, sometimes when characters outside the basic ASCII character set are used, you can have two different character sequences that look the same. To avoid confusion, the ISO 10646 standard sets out some "normalization rules" which when applied ensure that two sequences ! that look the same are turned into the same sequence. GCC can warn ! you if you are using identifiers that have not been normalized; ! this option controls that warning. There are four levels of warning supported by GCC. The default is ! '-Wnormalized=nfc', which warns about any identifier that is not in ! the ISO 10646 "C" normalized form, "NFC". NFC is the recommended ! form for most uses. It is equivalent to '-Wnormalized'. Unfortunately, there are some characters allowed in identifiers by ISO C and ISO C++ that, when turned into NFC, are not allowed in identifiers. That is, there's no way to use these symbols in portable ISO C or C++ and have all your identifiers in NFC. ! '-Wnormalized=id' suppresses the warning for these characters. It is hoped that future versions of the standards involved will correct this, which is why this option is not the default. You can switch the warning off for all characters by writing ! '-Wnormalized=none' or '-Wno-normalized'. You should only do this if you are using some other normalization scheme (like "D"), because otherwise you can easily create bugs that are literally impossible to see. Some characters in ISO 10646 have distinct meanings but look identical in some fonts or display methodologies, especially once ! formatting has been applied. For instance '\u207F', "SUPERSCRIPT ! LATIN SMALL LETTER N", displays just like a regular 'n' that has been placed in a superscript. ISO 10646 defines the "NFKC" normalization scheme to convert all these into a standard form as well, and GCC warns if your code is not in NFKC if you use ! '-Wnormalized=nfkc'. This warning is comparable to warning about every identifier that contains the letter O because it might be confused with the digit 0, and so is not the default, but may be useful as a local coding convention if the programming environment cannot be fixed to display these characters distinctly. ! '-Wno-deprecated' Do not warn about usage of deprecated features. *Note Deprecated Features::. ! '-Wno-deprecated-declarations' Do not warn about uses of functions (*note Function Attributes::), variables (*note Variable Attributes::), and types (*note Type ! Attributes::) marked as deprecated by using the 'deprecated' attribute. ! '-Wno-overflow' Do not warn about compile-time overflow in constant expressions. ! '-Wno-odr' Warn about One Definition Rule violations during link-time ! optimization. Requires '-flto-odr-type-merging' to be enabled. Enabled by default. ! '-Wopenmp-simd' Warn if the vectorizer cost model overrides the OpenMP or the Cilk ! Plus simd directive set by user. The '-fsimd-cost-model=unlimited' option can be used to relax the cost model. ! '-Woverride-init (C and Objective-C only)' Warn if an initialized field without side effects is overridden when using designated initializers (*note Designated Initializers: Designated Inits.). ! This warning is included in '-Wextra'. To get other '-Wextra' ! warnings without this one, use '-Wextra -Wno-override-init'. ! '-Woverride-init-side-effects (C and Objective-C only)' Warn if an initialized field with side effects is overridden when using designated initializers (*note Designated Initializers: Designated Inits.). This warning is enabled by default. ! '-Wpacked' Warn if a structure is given the packed attribute, but the packed attribute has no effect on the layout or size of the structure. Such structures may be mis-aligned for little benefit. For ! instance, in this code, the variable 'f.x' in 'struct bar' is ! misaligned even though 'struct bar' does not itself have the packed ! attribute: struct foo { int x; --- 5071,5173 ---- struct s { int f, g, h; }; s x = { }; ! This warning is included in `-Wextra'. To get other `-Wextra' ! warnings without this one, use `-Wextra -Wno-missing-field-initializers'. ! `-Wno-multichar' ! Do not warn if a multicharacter constant (`'FOOF'') is used. Usually they indicate a typo in the user's code, as they have implementation-defined values, and should not be used in portable code. ! `-Wnormalized[=]' In ISO C and ISO C++, two identifiers are different if they are different sequences of characters. However, sometimes when characters outside the basic ASCII character set are used, you can have two different character sequences that look the same. To avoid confusion, the ISO 10646 standard sets out some "normalization rules" which when applied ensure that two sequences ! that look the same are turned into the same sequence. GCC can ! warn you if you are using identifiers that have not been ! normalized; this option controls that warning. There are four levels of warning supported by GCC. The default is ! `-Wnormalized=nfc', which warns about any identifier that is not ! in the ISO 10646 "C" normalized form, "NFC". NFC is the ! recommended form for most uses. It is equivalent to ! `-Wnormalized'. Unfortunately, there are some characters allowed in identifiers by ISO C and ISO C++ that, when turned into NFC, are not allowed in identifiers. That is, there's no way to use these symbols in portable ISO C or C++ and have all your identifiers in NFC. ! `-Wnormalized=id' suppresses the warning for these characters. It is hoped that future versions of the standards involved will correct this, which is why this option is not the default. You can switch the warning off for all characters by writing ! `-Wnormalized=none' or `-Wno-normalized'. You should only do this if you are using some other normalization scheme (like "D"), because otherwise you can easily create bugs that are literally impossible to see. Some characters in ISO 10646 have distinct meanings but look identical in some fonts or display methodologies, especially once ! formatting has been applied. For instance `\u207F', "SUPERSCRIPT ! LATIN SMALL LETTER N", displays just like a regular `n' that has been placed in a superscript. ISO 10646 defines the "NFKC" normalization scheme to convert all these into a standard form as well, and GCC warns if your code is not in NFKC if you use ! `-Wnormalized=nfkc'. This warning is comparable to warning about every identifier that contains the letter O because it might be confused with the digit 0, and so is not the default, but may be useful as a local coding convention if the programming environment cannot be fixed to display these characters distinctly. ! `-Wno-deprecated' Do not warn about usage of deprecated features. *Note Deprecated Features::. ! `-Wno-deprecated-declarations' Do not warn about uses of functions (*note Function Attributes::), variables (*note Variable Attributes::), and types (*note Type ! Attributes::) marked as deprecated by using the `deprecated' attribute. ! `-Wno-overflow' Do not warn about compile-time overflow in constant expressions. ! `-Wno-odr' Warn about One Definition Rule violations during link-time ! optimization. Requires `-flto-odr-type-merging' to be enabled. Enabled by default. ! `-Wopenmp-simd' Warn if the vectorizer cost model overrides the OpenMP or the Cilk ! Plus simd directive set by user. The `-fsimd-cost-model=unlimited' option can be used to relax the cost model. ! `-Woverride-init (C and Objective-C only)' Warn if an initialized field without side effects is overridden when using designated initializers (*note Designated Initializers: Designated Inits.). ! This warning is included in `-Wextra'. To get other `-Wextra' ! warnings without this one, use `-Wextra -Wno-override-init'. ! `-Woverride-init-side-effects (C and Objective-C only)' Warn if an initialized field with side effects is overridden when using designated initializers (*note Designated Initializers: Designated Inits.). This warning is enabled by default. ! `-Wpacked' Warn if a structure is given the packed attribute, but the packed attribute has no effect on the layout or size of the structure. Such structures may be mis-aligned for little benefit. For ! instance, in this code, the variable `f.x' in `struct bar' is ! misaligned even though `struct bar' does not itself have the ! packed attribute: struct foo { int x; *************** compiler warns that an unrecognized opti *** 5139,5151 **** struct foo f; }; ! '-Wpacked-bitfield-compat' ! The 4.1, 4.2 and 4.3 series of GCC ignore the 'packed' attribute on ! bit-fields of type 'char'. This has been fixed in GCC 4.4 but the ! change can lead to differences in the structure layout. GCC informs you when the offset of such a field has changed in GCC 4.4. ! For example there is no longer a 4-bit padding between field 'a' ! and 'b' in this structure: struct foo { --- 5178,5190 ---- struct foo f; }; ! `-Wpacked-bitfield-compat' ! The 4.1, 4.2 and 4.3 series of GCC ignore the `packed' attribute ! on bit-fields of type `char'. This has been fixed in GCC 4.4 but ! the change can lead to differences in the structure layout. GCC informs you when the offset of such a field has changed in GCC 4.4. ! For example there is no longer a 4-bit padding between field `a' ! and `b' in this structure: struct foo { *************** compiler warns that an unrecognized opti *** 5154,5181 **** } __attribute__ ((packed)); This warning is enabled by default. Use ! '-Wno-packed-bitfield-compat' to disable this warning. ! '-Wpadded' Warn if padding is included in a structure, either to align an element of the structure or to align the whole structure. Sometimes when this happens it is possible to rearrange the fields of the structure to reduce the padding and so make the structure smaller. ! '-Wredundant-decls' ! Warn if anything is declared more than once in the same scope, even ! in cases where multiple declaration is valid and changes nothing. ! '-Wnested-externs (C and Objective-C only)' ! Warn if an 'extern' declaration is encountered within a function. ! '-Wno-inherited-variadic-ctor' Suppress warnings about use of C++11 inheriting constructors when the base class inherited from has a C variadic constructor; the warning is on by default because the ellipsis is not inherited. ! '-Winline' Warn if a function that is declared as inline cannot be inlined. Even with this option, the compiler does not warn about failures to inline functions declared in system headers. --- 5193,5221 ---- } __attribute__ ((packed)); This warning is enabled by default. Use ! `-Wno-packed-bitfield-compat' to disable this warning. ! `-Wpadded' Warn if padding is included in a structure, either to align an element of the structure or to align the whole structure. Sometimes when this happens it is possible to rearrange the fields of the structure to reduce the padding and so make the structure smaller. ! `-Wredundant-decls' ! Warn if anything is declared more than once in the same scope, ! even in cases where multiple declaration is valid and changes ! nothing. ! `-Wnested-externs (C and Objective-C only)' ! Warn if an `extern' declaration is encountered within a function. ! `-Wno-inherited-variadic-ctor' Suppress warnings about use of C++11 inheriting constructors when the base class inherited from has a C variadic constructor; the warning is on by default because the ellipsis is not inherited. ! `-Winline' Warn if a function that is declared as inline cannot be inlined. Even with this option, the compiler does not warn about failures to inline functions declared in system headers. *************** compiler warns that an unrecognized opti *** 5185,5245 **** account the size of the function being inlined and the amount of inlining that has already been done in the current function. Therefore, seemingly insignificant changes in the source program ! can cause the warnings produced by '-Winline' to appear or disappear. ! '-Wno-invalid-offsetof (C++ and Objective-C++ only)' ! Suppress warnings from applying the 'offsetof' macro to a non-POD ! type. According to the 2014 ISO C++ standard, applying 'offsetof' to a non-standard-layout type is undefined. In existing C++ ! implementations, however, 'offsetof' typically gives meaningful results. This flag is for users who are aware that they are ! writing nonportable code and who have deliberately chosen to ignore ! the warning about it. ! The restrictions on 'offsetof' may be relaxed in a future version of the C++ standard. ! '-Wno-int-to-pointer-cast' Suppress warnings from casts to pointer type of an integer of a ! different size. In C++, casting to a pointer type of smaller size ! is an error. 'Wint-to-pointer-cast' is enabled by default. ! '-Wno-pointer-to-int-cast (C and Objective-C only)' Suppress warnings from casts from a pointer to an integer type of a different size. ! '-Winvalid-pch' ! Warn if a precompiled header (*note Precompiled Headers::) is found ! in the search path but can't be used. ! '-Wlong-long' ! Warn if 'long long' type is used. This is enabled by either ! '-Wpedantic' or '-Wtraditional' in ISO C90 and C++98 modes. To ! inhibit the warning messages, use '-Wno-long-long'. ! '-Wvariadic-macros' Warn if variadic macros are used in ISO C90 mode, or if the GNU alternate syntax is used in ISO C99 mode. This is enabled by ! either '-Wpedantic' or '-Wtraditional'. To inhibit the warning ! messages, use '-Wno-variadic-macros'. ! '-Wvarargs' Warn upon questionable usage of the macros used to handle variable ! arguments like 'va_start'. This is default. To inhibit the ! warning messages, use '-Wno-varargs'. ! '-Wvector-operation-performance' Warn if vector operation is not implemented via SIMD capabilities of the architecture. Mainly useful for the performance tuning. ! Vector operation can be implemented 'piecewise', which means that ! the scalar operation is performed on every vector element; 'in parallel', which means that the vector operation is implemented using scalars of wider type, which normally is more performance ! efficient; and 'as a single scalar', which means that vector fits into a scalar type. ! '-Wno-virtual-move-assign' Suppress warnings about inheriting from a virtual base with a non-trivial C++11 move assignment operator. This is dangerous because if the virtual base is reachable along more than one path, --- 5225,5285 ---- account the size of the function being inlined and the amount of inlining that has already been done in the current function. Therefore, seemingly insignificant changes in the source program ! can cause the warnings produced by `-Winline' to appear or disappear. ! `-Wno-invalid-offsetof (C++ and Objective-C++ only)' ! Suppress warnings from applying the `offsetof' macro to a non-POD ! type. According to the 2014 ISO C++ standard, applying `offsetof' to a non-standard-layout type is undefined. In existing C++ ! implementations, however, `offsetof' typically gives meaningful results. This flag is for users who are aware that they are ! writing nonportable code and who have deliberately chosen to ! ignore the warning about it. ! The restrictions on `offsetof' may be relaxed in a future version of the C++ standard. ! `-Wno-int-to-pointer-cast' Suppress warnings from casts to pointer type of an integer of a ! different size. In C++, casting to a pointer type of smaller size ! is an error. `Wint-to-pointer-cast' is enabled by default. ! `-Wno-pointer-to-int-cast (C and Objective-C only)' Suppress warnings from casts from a pointer to an integer type of a different size. ! `-Winvalid-pch' ! Warn if a precompiled header (*note Precompiled Headers::) is ! found in the search path but can't be used. ! `-Wlong-long' ! Warn if `long long' type is used. This is enabled by either ! `-Wpedantic' or `-Wtraditional' in ISO C90 and C++98 modes. To ! inhibit the warning messages, use `-Wno-long-long'. ! `-Wvariadic-macros' Warn if variadic macros are used in ISO C90 mode, or if the GNU alternate syntax is used in ISO C99 mode. This is enabled by ! either `-Wpedantic' or `-Wtraditional'. To inhibit the warning ! messages, use `-Wno-variadic-macros'. ! `-Wvarargs' Warn upon questionable usage of the macros used to handle variable ! arguments like `va_start'. This is default. To inhibit the ! warning messages, use `-Wno-varargs'. ! `-Wvector-operation-performance' Warn if vector operation is not implemented via SIMD capabilities of the architecture. Mainly useful for the performance tuning. ! Vector operation can be implemented `piecewise', which means that ! the scalar operation is performed on every vector element; `in parallel', which means that the vector operation is implemented using scalars of wider type, which normally is more performance ! efficient; and `as a single scalar', which means that vector fits into a scalar type. ! `-Wno-virtual-move-assign' Suppress warnings about inheriting from a virtual base with a non-trivial C++11 move assignment operator. This is dangerous because if the virtual base is reachable along more than one path, *************** compiler warns that an unrecognized opti *** 5248,5264 **** to avoid moving from a moved-from object, this warning can be disabled. ! '-Wvla' ! Warn if variable length array is used in the code. '-Wno-vla' ! prevents the '-Wpedantic' warning of the variable length array. ! '-Wvolatile-register-var' Warn if a register variable is declared volatile. The volatile modifier does not inhibit all optimizations that may eliminate ! reads and/or writes to register variables. This warning is enabled ! by '-Wall'. ! '-Wdisabled-optimization' Warn if a requested optimization pass is disabled. This warning does not generally indicate that there is anything wrong with your code; it merely indicates that GCC's optimizers are unable to --- 5288,5304 ---- to avoid moving from a moved-from object, this warning can be disabled. ! `-Wvla' ! Warn if variable length array is used in the code. `-Wno-vla' ! prevents the `-Wpedantic' warning of the variable length array. ! `-Wvolatile-register-var' Warn if a register variable is declared volatile. The volatile modifier does not inhibit all optimizations that may eliminate ! reads and/or writes to register variables. This warning is ! enabled by `-Wall'. ! `-Wdisabled-optimization' Warn if a requested optimization pass is disabled. This warning does not generally indicate that there is anything wrong with your code; it merely indicates that GCC's optimizers are unable to *************** compiler warns that an unrecognized opti *** 5267,5284 **** the optimization itself is likely to take inordinate amounts of time. ! '-Wpointer-sign (C and Objective-C only)' Warn for pointer argument passing or assignment with different signedness. This option is only supported for C and Objective-C. ! It is implied by '-Wall' and by '-Wpedantic', which can be disabled ! with '-Wno-pointer-sign'. ! '-Wstack-protector' ! This option is only active when '-fstack-protector' is active. It warns about functions that are not protected against stack smashing. ! '-Woverlength-strings' Warn about string constants that are longer than the "minimum maximum" length specified in the C standard. Modern compilers generally allow string constants that are much longer than the --- 5307,5324 ---- the optimization itself is likely to take inordinate amounts of time. ! `-Wpointer-sign (C and Objective-C only)' Warn for pointer argument passing or assignment with different signedness. This option is only supported for C and Objective-C. ! It is implied by `-Wall' and by `-Wpedantic', which can be ! disabled with `-Wno-pointer-sign'. ! `-Wstack-protector' ! This option is only active when `-fstack-protector' is active. It warns about functions that are not protected against stack smashing. ! `-Woverlength-strings' Warn about string constants that are longer than the "minimum maximum" length specified in the C standard. Modern compilers generally allow string constants that are much longer than the *************** compiler warns that an unrecognized opti *** 5290,5315 **** in C99, it was raised to 4095. C++98 does not specify a normative minimum maximum, so we do not diagnose overlength strings in C++. ! This option is implied by '-Wpedantic', and can be disabled with ! '-Wno-overlength-strings'. ! ! '-Wunsuffixed-float-constants (C and Objective-C only)' Issue a warning for any floating constant that does not have a ! suffix. When used together with '-Wsystem-headers' it warns about such constants in system header files. This can be useful when ! preparing code to use with the 'FLOAT_CONST_DECIMAL64' pragma from the decimal floating-point extension to C99. ! '-Wno-designated-init (C and Objective-C only)' Suppress warnings when a positional initializer is used to initialize a structure that has been marked with the ! 'designated_init' attribute. ! '-Whsa' Issue a warning when HSAIL cannot be emitted for the compiled function or OpenMP construct.  File: gcc.info, Node: Debugging Options, Next: Optimize Options, Prev: Warning Options, Up: Invoking GCC --- 5330,5355 ---- in C99, it was raised to 4095. C++98 does not specify a normative minimum maximum, so we do not diagnose overlength strings in C++. ! This option is implied by `-Wpedantic', and can be disabled with ! `-Wno-overlength-strings'. + `-Wunsuffixed-float-constants (C and Objective-C only)' Issue a warning for any floating constant that does not have a ! suffix. When used together with `-Wsystem-headers' it warns about such constants in system header files. This can be useful when ! preparing code to use with the `FLOAT_CONST_DECIMAL64' pragma from the decimal floating-point extension to C99. ! `-Wno-designated-init (C and Objective-C only)' Suppress warnings when a positional initializer is used to initialize a structure that has been marked with the ! `designated_init' attribute. ! `-Whsa' Issue a warning when HSAIL cannot be emitted for the compiled function or OpenMP construct. +  File: gcc.info, Node: Debugging Options, Next: Optimize Options, Prev: Warning Options, Up: Invoking GCC *************** File: gcc.info, Node: Debugging Options *** 5317,5360 **** ====================================== To tell GCC to emit extra information for use by a debugger, in almost ! all cases you need only to add '-g' to your other options. ! GCC allows you to use '-g' with '-O'. The shortcuts taken by optimized ! code may occasionally be surprising: some variables you declared may not ! exist at all; flow of control may briefly move where you did not expect ! it; some statements may not be executed because they compute constant ! results or their values are already at hand; some statements may execute ! in different places because they have been moved out of loops. ! Nevertheless it is possible to debug optimized output. This makes it ! reasonable to use the optimizer for programs that might have bugs. If you are not using some other optimization option, consider using ! '-Og' (*note Optimize Options::) with '-g'. With no '-O' option at all, ! some compiler passes that collect information useful for debugging do ! not run at all, so that '-Og' may result in a better debugging experience. ! '-g' Produce debugging information in the operating system's native format (stabs, COFF, XCOFF, or DWARF). GDB can work with this debugging information. ! On most systems that use stabs format, '-g' enables use of extra debugging information that only GDB can use; this extra information makes debugging work better in GDB but probably makes other debuggers crash or refuse to read the program. If you want to control for certain whether to generate the extra information, use ! '-gstabs+', '-gstabs', '-gxcoff+', '-gxcoff', or '-gvms' (see below). ! '-ggdb' Produce debugging information for use by GDB. This means to use the most expressive format available (DWARF, stabs, or the native ! format if neither of those are supported), including GDB extensions ! if at all possible. ! '-gdwarf' ! '-gdwarf-VERSION' Produce debugging information in DWARF format (if that is supported). The value of VERSION may be either 2, 3, 4 or 5; the default version for most targets is 4. DWARF Version 5 is only --- 5357,5401 ---- ====================================== To tell GCC to emit extra information for use by a debugger, in almost ! all cases you need only to add `-g' to your other options. ! GCC allows you to use `-g' with `-O'. The shortcuts taken by ! optimized code may occasionally be surprising: some variables you ! declared may not exist at all; flow of control may briefly move where ! you did not expect it; some statements may not be executed because they ! compute constant results or their values are already at hand; some ! statements may execute in different places because they have been moved ! out of loops. Nevertheless it is possible to debug optimized output. ! This makes it reasonable to use the optimizer for programs that might ! have bugs. If you are not using some other optimization option, consider using ! `-Og' (*note Optimize Options::) with `-g'. With no `-O' option at ! all, some compiler passes that collect information useful for debugging ! do not run at all, so that `-Og' may result in a better debugging experience. ! `-g' Produce debugging information in the operating system's native format (stabs, COFF, XCOFF, or DWARF). GDB can work with this debugging information. ! On most systems that use stabs format, `-g' enables use of extra debugging information that only GDB can use; this extra information makes debugging work better in GDB but probably makes other debuggers crash or refuse to read the program. If you want to control for certain whether to generate the extra information, use ! `-gstabs+', `-gstabs', `-gxcoff+', `-gxcoff', or `-gvms' (see below). ! `-ggdb' Produce debugging information for use by GDB. This means to use the most expressive format available (DWARF, stabs, or the native ! format if neither of those are supported), including GDB ! extensions if at all possible. ! `-gdwarf' ! `-gdwarf-VERSION' Produce debugging information in DWARF format (if that is supported). The value of VERSION may be either 2, 3, 4 or 5; the default version for most targets is 4. DWARF Version 5 is only *************** experience. *** 5363,5403 **** Note that with DWARF Version 2, some ports require and always use some non-conflicting DWARF 3 extensions in the unwind tables. ! Version 4 may require GDB 7.0 and '-fvar-tracking-assignments' for maximum benefit. GCC no longer supports DWARF Version 1, which is substantially different than Version 2 and later. For historical reasons, some ! other DWARF-related options (including '-feliminate-dwarf2-dups' ! and '-fno-dwarf2-cfi-asm') retain a reference to DWARF Version 2 in ! their names, but apply to all currently-supported versions of DWARF. ! '-gstabs' Produce debugging information in stabs format (if that is ! supported), without GDB extensions. This is the format used by DBX ! on most BSD systems. On MIPS, Alpha and System V Release 4 systems ! this option produces stabs debugging output that is not understood ! by DBX or SDB. On System V Release 4 systems this option requires ! the GNU assembler. ! '-gstabs+' Produce debugging information in stabs format (if that is supported), using GNU extensions understood only by the GNU debugger (GDB). The use of these extensions is likely to make other debuggers crash or refuse to read the program. ! '-gcoff' Produce debugging information in COFF format (if that is supported). This is the format used by SDB on most System V systems prior to System V Release 4. ! '-gxcoff' Produce debugging information in XCOFF format (if that is supported). This is the format used by the DBX debugger on IBM RS/6000 systems. ! '-gxcoff+' Produce debugging information in XCOFF format (if that is supported), using GNU extensions understood only by the GNU debugger (GDB). The use of these extensions is likely to make --- 5404,5444 ---- Note that with DWARF Version 2, some ports require and always use some non-conflicting DWARF 3 extensions in the unwind tables. ! Version 4 may require GDB 7.0 and `-fvar-tracking-assignments' for maximum benefit. GCC no longer supports DWARF Version 1, which is substantially different than Version 2 and later. For historical reasons, some ! other DWARF-related options (including `-feliminate-dwarf2-dups' ! and `-fno-dwarf2-cfi-asm') retain a reference to DWARF Version 2 ! in their names, but apply to all currently-supported versions of DWARF. ! `-gstabs' Produce debugging information in stabs format (if that is ! supported), without GDB extensions. This is the format used by ! DBX on most BSD systems. On MIPS, Alpha and System V Release 4 ! systems this option produces stabs debugging output that is not ! understood by DBX or SDB. On System V Release 4 systems this ! option requires the GNU assembler. ! `-gstabs+' Produce debugging information in stabs format (if that is supported), using GNU extensions understood only by the GNU debugger (GDB). The use of these extensions is likely to make other debuggers crash or refuse to read the program. ! `-gcoff' Produce debugging information in COFF format (if that is supported). This is the format used by SDB on most System V systems prior to System V Release 4. ! `-gxcoff' Produce debugging information in XCOFF format (if that is supported). This is the format used by the DBX debugger on IBM RS/6000 systems. ! `-gxcoff+' Produce debugging information in XCOFF format (if that is supported), using GNU extensions understood only by the GNU debugger (GDB). The use of these extensions is likely to make *************** experience. *** 5405,5557 **** assemblers other than the GNU assembler (GAS) to fail with an error. ! '-gvms' Produce debugging information in Alpha/VMS debug format (if that is supported). This is the format used by DEBUG on Alpha/VMS systems. ! '-gLEVEL' ! '-ggdbLEVEL' ! '-gstabsLEVEL' ! '-gcoffLEVEL' ! '-gxcoffLEVEL' ! '-gvmsLEVEL' Request debugging information and also use LEVEL to specify how much information. The default level is 2. ! Level 0 produces no debug information at all. Thus, '-g0' negates ! '-g'. Level 1 produces minimal information, enough for making backtraces in parts of the program that you don't plan to debug. This ! includes descriptions of functions and external variables, and line ! number tables, but no information about local variables. Level 3 includes extra information, such as all the macro definitions present in the program. Some debuggers support macro ! expansion when you use '-g3'. ! '-gdwarf' does not accept a concatenated debug level, to avoid ! confusion with '-gdwarf-LEVEL'. Instead use an additional ! '-gLEVEL' option to change the debug level for DWARF. ! '-feliminate-unused-debug-symbols' Produce debugging information in stabs format (if that is supported), for only symbols that are actually used. ! '-femit-class-debug-always' Instead of emitting debugging information for a C++ class in only ! one object file, emit it in all object files using the class. This ! option should be used only with debuggers that are unable to handle ! the way GCC normally emits debugging information for classes ! because using this option increases the size of debugging information by as much as a factor of two. ! '-fno-merge-debug-strings' Direct the linker to not merge together strings in the debugging information that are identical in different object files. Merging is not supported by all assemblers or linkers. Merging decreases ! the size of the debug information in the output file at the cost of ! increasing link processing time. Merging is enabled by default. ! '-fdebug-prefix-map=OLD=NEW' ! When compiling files in directory 'OLD', record debugging ! information describing them as in 'NEW' instead. ! '-fvar-tracking' ! Run variable tracking pass. It computes where variables are stored ! at each position in code. Better debugging information is then ! generated (if the debugging information format supports this information). ! It is enabled by default when compiling with optimization ('-Os', ! '-O', '-O2', ...), debugging information ('-g') and the debug info format supports it. ! '-fvar-tracking-assignments' Annotate assignments to user variables early in the compilation and attempt to carry the annotations over throughout the compilation all the way to the end, in an attempt to improve debug information ! while optimizing. Use of '-gdwarf-4' is recommended along with it. It can be enabled even if var-tracking is disabled, in which case annotations are created and maintained, but discarded at the end. ! By default, this flag is enabled together with '-fvar-tracking', except when selective scheduling is enabled. ! '-gsplit-dwarf' Separate as much DWARF debugging information as possible into a ! separate output file with the extension '.dwo'. This option allows the build system to avoid linking files with debug information. To be useful, this option requires a debugger capable of reading ! '.dwo' files. ! '-gpubnames' ! Generate DWARF '.debug_pubnames' and '.debug_pubtypes' sections. ! '-ggnu-pubnames' ! Generate '.debug_pubnames' and '.debug_pubtypes' sections in a format suitable for conversion into a GDB index. This option is only useful with a linker that can produce GDB index version 7. ! '-fdebug-types-section' When using DWARF Version 4 or higher, type DIEs can be put into ! their own '.debug_types' section instead of making them part of the ! '.debug_info' section. It is more efficient to put them in a separate comdat sections since the linker can then remove ! duplicates. But not all DWARF consumers support '.debug_types' ! sections yet and on some objects '.debug_types' produces larger instead of smaller debugging information. ! '-grecord-gcc-switches' ! '-gno-record-gcc-switches' This switch causes the command-line options used to invoke the compiler that may affect code generation to be appended to the DW_AT_producer attribute in DWARF debugging information. The options are concatenated with spaces separating them from each other and from the compiler version. It is enabled by default. ! See also '-frecord-gcc-switches' for another way of storing compiler options into the object file. ! '-gstrict-dwarf' Disallow using extensions of later DWARF standard version than ! selected with '-gdwarf-VERSION'. On most targets using non-conflicting DWARF extensions from later standard versions is allowed. ! '-gno-strict-dwarf' Allow using extensions of later DWARF standard version than ! selected with '-gdwarf-VERSION'. ! '-gz[=TYPE]' Produce compressed debug sections in DWARF format, if that is supported. If TYPE is not given, the default type depends on the capabilities of the assembler and linker used. TYPE may be one of ! 'none' (don't compress debug sections), 'zlib' (use zlib ! compression in ELF gABI format), or 'zlib-gnu' (use zlib compression in traditional GNU format). If the linker doesn't support writing compressed debug sections, the option is rejected. ! Otherwise, if the assembler does not support them, '-gz' is silently ignored when producing object files. ! '-feliminate-dwarf2-dups' Compress DWARF debugging information by eliminating duplicated information about each symbol. This option only makes sense when generating DWARF debugging information. ! '-femit-struct-debug-baseonly' Emit debug information for struct-like types only when the base name of the compilation source file matches the base name of file in which the struct is defined. This option substantially reduces the size of debugging information, but at significant potential loss in type information ! to the debugger. See '-femit-struct-debug-reduced' for a less ! aggressive option. See '-femit-struct-debug-detailed' for more detailed control. This option works only with DWARF debug output. ! '-femit-struct-debug-reduced' Emit debug information for struct-like types only when the base name of the compilation source file matches the base name of file in which the type is defined, unless the struct is a template or --- 5446,5599 ---- assemblers other than the GNU assembler (GAS) to fail with an error. ! `-gvms' Produce debugging information in Alpha/VMS debug format (if that is supported). This is the format used by DEBUG on Alpha/VMS systems. ! `-gLEVEL' ! `-ggdbLEVEL' ! `-gstabsLEVEL' ! `-gcoffLEVEL' ! `-gxcoffLEVEL' ! `-gvmsLEVEL' Request debugging information and also use LEVEL to specify how much information. The default level is 2. ! Level 0 produces no debug information at all. Thus, `-g0' negates ! `-g'. Level 1 produces minimal information, enough for making backtraces in parts of the program that you don't plan to debug. This ! includes descriptions of functions and external variables, and ! line number tables, but no information about local variables. Level 3 includes extra information, such as all the macro definitions present in the program. Some debuggers support macro ! expansion when you use `-g3'. ! `-gdwarf' does not accept a concatenated debug level, to avoid ! confusion with `-gdwarf-LEVEL'. Instead use an additional ! `-gLEVEL' option to change the debug level for DWARF. ! `-feliminate-unused-debug-symbols' Produce debugging information in stabs format (if that is supported), for only symbols that are actually used. ! `-femit-class-debug-always' Instead of emitting debugging information for a C++ class in only ! one object file, emit it in all object files using the class. ! This option should be used only with debuggers that are unable to ! handle the way GCC normally emits debugging information for ! classes because using this option increases the size of debugging information by as much as a factor of two. ! `-fno-merge-debug-strings' Direct the linker to not merge together strings in the debugging information that are identical in different object files. Merging is not supported by all assemblers or linkers. Merging decreases ! the size of the debug information in the output file at the cost ! of increasing link processing time. Merging is enabled by default. ! `-fdebug-prefix-map=OLD=NEW' ! When compiling files in directory `OLD', record debugging ! information describing them as in `NEW' instead. ! `-fvar-tracking' ! Run variable tracking pass. It computes where variables are ! stored at each position in code. Better debugging information is ! then generated (if the debugging information format supports this information). ! It is enabled by default when compiling with optimization (`-Os', ! `-O', `-O2', ...), debugging information (`-g') and the debug info format supports it. ! `-fvar-tracking-assignments' Annotate assignments to user variables early in the compilation and attempt to carry the annotations over throughout the compilation all the way to the end, in an attempt to improve debug information ! while optimizing. Use of `-gdwarf-4' is recommended along with it. It can be enabled even if var-tracking is disabled, in which case annotations are created and maintained, but discarded at the end. ! By default, this flag is enabled together with `-fvar-tracking', except when selective scheduling is enabled. ! `-gsplit-dwarf' Separate as much DWARF debugging information as possible into a ! separate output file with the extension `.dwo'. This option allows the build system to avoid linking files with debug information. To be useful, this option requires a debugger capable of reading ! `.dwo' files. ! `-gpubnames' ! Generate DWARF `.debug_pubnames' and `.debug_pubtypes' sections. ! `-ggnu-pubnames' ! Generate `.debug_pubnames' and `.debug_pubtypes' sections in a format suitable for conversion into a GDB index. This option is only useful with a linker that can produce GDB index version 7. ! `-fdebug-types-section' When using DWARF Version 4 or higher, type DIEs can be put into ! their own `.debug_types' section instead of making them part of the ! `.debug_info' section. It is more efficient to put them in a separate comdat sections since the linker can then remove ! duplicates. But not all DWARF consumers support `.debug_types' ! sections yet and on some objects `.debug_types' produces larger instead of smaller debugging information. ! `-grecord-gcc-switches' ! ! `-gno-record-gcc-switches' This switch causes the command-line options used to invoke the compiler that may affect code generation to be appended to the DW_AT_producer attribute in DWARF debugging information. The options are concatenated with spaces separating them from each other and from the compiler version. It is enabled by default. ! See also `-frecord-gcc-switches' for another way of storing compiler options into the object file. ! `-gstrict-dwarf' Disallow using extensions of later DWARF standard version than ! selected with `-gdwarf-VERSION'. On most targets using non-conflicting DWARF extensions from later standard versions is allowed. ! `-gno-strict-dwarf' Allow using extensions of later DWARF standard version than ! selected with `-gdwarf-VERSION'. ! `-gz[=TYPE]' Produce compressed debug sections in DWARF format, if that is supported. If TYPE is not given, the default type depends on the capabilities of the assembler and linker used. TYPE may be one of ! `none' (don't compress debug sections), `zlib' (use zlib ! compression in ELF gABI format), or `zlib-gnu' (use zlib compression in traditional GNU format). If the linker doesn't support writing compressed debug sections, the option is rejected. ! Otherwise, if the assembler does not support them, `-gz' is silently ignored when producing object files. ! `-feliminate-dwarf2-dups' Compress DWARF debugging information by eliminating duplicated information about each symbol. This option only makes sense when generating DWARF debugging information. ! `-femit-struct-debug-baseonly' Emit debug information for struct-like types only when the base name of the compilation source file matches the base name of file in which the struct is defined. This option substantially reduces the size of debugging information, but at significant potential loss in type information ! to the debugger. See `-femit-struct-debug-reduced' for a less ! aggressive option. See `-femit-struct-debug-detailed' for more detailed control. This option works only with DWARF debug output. ! `-femit-struct-debug-reduced' Emit debug information for struct-like types only when the base name of the compilation source file matches the base name of file in which the type is defined, unless the struct is a template or *************** experience. *** 5559,5626 **** This option significantly reduces the size of debugging information, with some potential loss in type information to the ! debugger. See '-femit-struct-debug-baseonly' for a more aggressive ! option. See '-femit-struct-debug-detailed' for more detailed ! control. This option works only with DWARF debug output. ! '-femit-struct-debug-detailed[=SPEC-LIST]' Specify the struct-like types for which the compiler generates debug information. The intent is to reduce duplicate struct debug information between different object files within the same program. ! This option is a detailed version of '-femit-struct-debug-reduced' ! and '-femit-struct-debug-baseonly', which serves for most needs. A specification has the syntax ! ['dir:'|'ind:']['ord:'|'gen:']('any'|'sys'|'base'|'none') The optional first word limits the specification to structs that ! are used directly ('dir:') or used indirectly ('ind:'). A struct type is used directly when it is the type of a variable, member. ! Indirect uses arise through pointers to structs. That is, when use ! of an incomplete struct is valid, the use is indirect. An example ! is 'struct one direct; struct two * indirect;'. The optional second word limits the specification to ordinary ! structs ('ord:') or generic structs ('gen:'). Generic structs are a bit complicated to explain. For C++, these are non-explicit ! specializations of template classes, or non-template classes within ! the above. Other programming languages have generics, but ! '-femit-struct-debug-detailed' does not yet implement them. The third word specifies the source files for those structs for which the compiler should emit debug information. The values ! 'none' and 'any' have the normal meaning. The value 'base' means that the base of name of the file in which the type declaration appears must match the base of the name of the main compilation ! file. In practice, this means that when compiling 'foo.c', debug information is generated for types declared in that file and ! 'foo.h', but not other header files. The value 'sys' means those ! types satisfying 'base' or declared in system or compiler headers. You may need to experiment to determine the best settings for your application. ! The default is '-femit-struct-debug-detailed=all'. This option works only with DWARF debug output. ! '-fno-dwarf2-cfi-asm' ! Emit DWARF unwind info as compiler generated '.eh_frame' section ! instead of using GAS '.cfi_*' directives. ! '-fno-eliminate-unused-debug-types' Normally, when producing DWARF output, GCC avoids producing debug symbol output for types that are nowhere used in the source file being compiled. Sometimes it is useful to have GCC emit debugging information for all types declared in a compilation unit, regardless of whether or not they are actually used in that ! compilation unit, for example if, in the debugger, you want to cast ! a value to a type that is not actually used in your program (but is ! declared). More often, however, this results in a significant ! amount of wasted space.  File: gcc.info, Node: Optimize Options, Next: Instrumentation Options, Prev: Debugging Options, Up: Invoking GCC --- 5601,5668 ---- This option significantly reduces the size of debugging information, with some potential loss in type information to the ! debugger. See `-femit-struct-debug-baseonly' for a more ! aggressive option. See `-femit-struct-debug-detailed' for more ! detailed control. This option works only with DWARF debug output. ! `-femit-struct-debug-detailed[=SPEC-LIST]' Specify the struct-like types for which the compiler generates debug information. The intent is to reduce duplicate struct debug information between different object files within the same program. ! This option is a detailed version of `-femit-struct-debug-reduced' ! and `-femit-struct-debug-baseonly', which serves for most needs. A specification has the syntax ! [`dir:'|`ind:'][`ord:'|`gen:'](`any'|`sys'|`base'|`none') The optional first word limits the specification to structs that ! are used directly (`dir:') or used indirectly (`ind:'). A struct type is used directly when it is the type of a variable, member. ! Indirect uses arise through pointers to structs. That is, when ! use of an incomplete struct is valid, the use is indirect. An ! example is `struct one direct; struct two * indirect;'. The optional second word limits the specification to ordinary ! structs (`ord:') or generic structs (`gen:'). Generic structs are a bit complicated to explain. For C++, these are non-explicit ! specializations of template classes, or non-template classes ! within the above. Other programming languages have generics, but ! `-femit-struct-debug-detailed' does not yet implement them. The third word specifies the source files for those structs for which the compiler should emit debug information. The values ! `none' and `any' have the normal meaning. The value `base' means that the base of name of the file in which the type declaration appears must match the base of the name of the main compilation ! file. In practice, this means that when compiling `foo.c', debug information is generated for types declared in that file and ! `foo.h', but not other header files. The value `sys' means those ! types satisfying `base' or declared in system or compiler headers. You may need to experiment to determine the best settings for your application. ! The default is `-femit-struct-debug-detailed=all'. This option works only with DWARF debug output. ! `-fno-dwarf2-cfi-asm' ! Emit DWARF unwind info as compiler generated `.eh_frame' section ! instead of using GAS `.cfi_*' directives. ! `-fno-eliminate-unused-debug-types' Normally, when producing DWARF output, GCC avoids producing debug symbol output for types that are nowhere used in the source file being compiled. Sometimes it is useful to have GCC emit debugging information for all types declared in a compilation unit, regardless of whether or not they are actually used in that ! compilation unit, for example if, in the debugger, you want to ! cast a value to a type that is not actually used in your program ! (but is declared). More often, however, this results in a ! significant amount of wasted space.  File: gcc.info, Node: Optimize Options, Next: Instrumentation Options, Prev: Debugging Options, Up: Invoking GCC *************** between statements, you can then assign *** 5637,5674 **** change the program counter to any other statement in the function and get exactly the results you expect from the source code. ! Turning on optimization flags makes the compiler attempt to improve the ! performance and/or code size at the expense of compilation time and possibly the ability to debug the program. The compiler performs optimization based on the knowledge it has of the program. Compiling multiple files at once to a single output file mode ! allows the compiler to use information gained from all of the files when ! compiling each of them. Not all optimizations are controlled directly by a flag. Only optimizations that have a flag are listed in this section. ! Most optimizations are only enabled if an '-O' level is set on the command line. Otherwise they are disabled, even if individual optimization flags are specified. Depending on the target and how GCC was configured, a slightly ! different set of optimizations may be enabled at each '-O' level than ! those listed here. You can invoke GCC with '-Q --help=optimizers' to find out the exact set of optimizations that are enabled at each level. *Note Overall Options::, for examples. ! '-O' ! '-O1' Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. ! With '-O', the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time. ! '-O' turns on the following optimization flags: -fauto-inc-dec -fbranch-count-reg -fcombine-stack-adjustments --- 5679,5716 ---- change the program counter to any other statement in the function and get exactly the results you expect from the source code. ! Turning on optimization flags makes the compiler attempt to improve ! the performance and/or code size at the expense of compilation time and possibly the ability to debug the program. The compiler performs optimization based on the knowledge it has of the program. Compiling multiple files at once to a single output file mode ! allows the compiler to use information gained from all of the files ! when compiling each of them. Not all optimizations are controlled directly by a flag. Only optimizations that have a flag are listed in this section. ! Most optimizations are only enabled if an `-O' level is set on the command line. Otherwise they are disabled, even if individual optimization flags are specified. Depending on the target and how GCC was configured, a slightly ! different set of optimizations may be enabled at each `-O' level than ! those listed here. You can invoke GCC with `-Q --help=optimizers' to find out the exact set of optimizations that are enabled at each level. *Note Overall Options::, for examples. ! `-O' ! `-O1' Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. ! With `-O', the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time. ! `-O' turns on the following optimization flags: -fauto-inc-dec -fbranch-count-reg -fcombine-stack-adjustments *************** find out the exact set of optimizations *** 5711,5726 **** -ftree-ter -funit-at-a-time ! '-O' also turns on '-fomit-frame-pointer' on machines where doing so does not interfere with debugging. ! '-O2' Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As ! compared to '-O', this option increases both compilation time and the performance of the generated code. ! '-O2' turns on all optimization flags specified by '-O'. It also turns on the following optimization flags: -fthread-jumps -falign-functions -falign-jumps --- 5753,5768 ---- -ftree-ter -funit-at-a-time ! `-O' also turns on `-fomit-frame-pointer' on machines where doing so does not interfere with debugging. ! `-O2' Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As ! compared to `-O', this option increases both compilation time and the performance of the generated code. ! `-O2' turns on all optimization flags specified by `-O'. It also turns on the following optimization flags: -fthread-jumps -falign-functions -falign-jumps *************** find out the exact set of optimizations *** 5757,5953 **** -ftree-vrp -fipa-ra ! Please note the warning under '-fgcse' about invoking '-O2' on programs that use computed gotos. ! '-O3' ! Optimize yet more. '-O3' turns on all optimizations specified by ! '-O2' and also turns on the '-finline-functions', ! '-funswitch-loops', '-fpredictive-commoning', ! '-fgcse-after-reload', '-ftree-loop-vectorize', ! '-ftree-loop-distribute-patterns', '-fsplit-paths' ! '-ftree-slp-vectorize', '-fvect-cost-model', '-ftree-partial-pre' ! and '-fipa-cp-clone' options. ! '-O0' Reduce compilation time and make debugging produce the expected results. This is the default. ! '-Os' ! Optimize for size. '-Os' enables all '-O2' optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size. ! '-Os' disables the following optimization flags: -falign-functions -falign-jumps -falign-loops -falign-labels -freorder-blocks -freorder-blocks-algorithm=stc -freorder-blocks-and-partition -fprefetch-loop-arrays ! '-Ofast' ! Disregard strict standards compliance. '-Ofast' enables all '-O3' optimizations. It also enables optimizations that are not valid ! for all standard-compliant programs. It turns on '-ffast-math' and ! the Fortran-specific '-fno-protect-parens' and '-fstack-arrays'. ! '-Og' ! Optimize debugging experience. '-Og' enables optimizations that do ! not interfere with debugging. It should be the optimization level ! of choice for the standard edit-compile-debug cycle, offering a ! reasonable level of optimization while maintaining fast compilation ! and a good debugging experience. ! If you use multiple '-O' options, with or without level numbers, the last such option is the one that is effective. ! Options of the form '-fFLAG' specify machine-independent flags. Most flags have both positive and negative forms; the negative form of ! '-ffoo' is '-fno-foo'. In the table below, only one of the forms is ! listed--the one you typically use. You can figure out the other form by ! either removing 'no-' or adding it. The following options control specific optimizations. They are either ! activated by '-O' options or are related to ones that are. You can use the following flags in the rare cases when "fine-tuning" of optimizations to be performed is desired. ! '-fno-defer-pop' Always pop the arguments to each function call as soon as that function returns. For machines that must pop arguments after a function call, the compiler normally lets arguments accumulate on the stack for several function calls and pops them all at once. ! Disabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fforward-propagate' Perform a forward propagation pass on RTL. The pass tries to combine two instructions and checks if the result can be simplified. If loop unrolling is active, two passes are performed and the second is scheduled after loop unrolling. ! This option is enabled by default at optimization levels '-O', ! '-O2', '-O3', '-Os'. ! '-ffp-contract=STYLE' ! '-ffp-contract=off' disables floating-point expression contraction. ! '-ffp-contract=fast' enables floating-point expression contraction such as forming of fused multiply-add operations if the target has ! native support for them. '-ffp-contract=on' enables floating-point ! expression contraction if allowed by the language standard. This ! is currently not implemented and treated equal to ! '-ffp-contract=off'. ! The default is '-ffp-contract=fast'. ! '-fomit-frame-pointer' ! Don't keep the frame pointer in a register for functions that don't ! need one. This avoids the instructions to save, set up and restore ! frame pointers; it also makes an extra register available in many ! functions. *It also makes debugging impossible on some machines.* On some machines, such as the VAX, this flag has no effect, because the standard calling sequence automatically handles the frame pointer and nothing is saved by pretending it doesn't exist. The ! machine-description macro 'FRAME_POINTER_REQUIRED' controls whether ! a target machine supports this flag. *Note Register Usage: ! (gccint)Registers. The default setting (when not optimizing for size) for 32-bit GNU/Linux x86 and 32-bit Darwin x86 targets is ! '-fomit-frame-pointer'. You can configure GCC with the ! '--enable-frame-pointer' configure option to change the default. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-foptimize-sibling-calls' Optimize sibling and tail recursive calls. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-foptimize-strlen' ! Optimize various standard C string functions (e.g. 'strlen', ! 'strchr' or 'strcpy') and their '_FORTIFY_SOURCE' counterparts into ! faster alternatives. ! Enabled at levels '-O2', '-O3'. ! '-fno-inline' ! Do not expand any functions inline apart from those marked with the ! 'always_inline' attribute. This is the default when not optimizing. ! Single functions can be exempted from inlining by marking them with ! the 'noinline' attribute. ! '-finline-small-functions' Integrate functions into their callers when their body is smaller than expected function call code (so overall size of program gets smaller). The compiler heuristically decides which functions are simple enough to be worth integrating in this way. This inlining applies to all functions, even those not declared inline. ! Enabled at level '-O2'. ! '-findirect-inlining' Inline also indirect calls that are discovered to be known at compile time thanks to previous inlining. This option has any effect only when inlining itself is turned on by the ! '-finline-functions' or '-finline-small-functions' options. ! Enabled at level '-O2'. ! '-finline-functions' Consider all functions for inlining, even if they are not declared inline. The compiler heuristically decides which functions are worth integrating in this way. If all calls to a given function are integrated, and the function ! is declared 'static', then the function is normally not output as assembler code in its own right. ! Enabled at level '-O3'. ! '-finline-functions-called-once' ! Consider all 'static' functions called once for inlining into their ! caller even if they are not marked 'inline'. If a call to a given function is integrated, then the function is not output as assembler code in its own right. ! Enabled at levels '-O1', '-O2', '-O3' and '-Os'. ! '-fearly-inlining' ! Inline functions marked by 'always_inline' and functions whose body ! seems smaller than the function call overhead early before doing ! '-fprofile-generate' instrumentation and real inlining pass. Doing ! so makes profiling significantly cheaper and usually inlining ! faster on programs having large chains of nested wrapper functions. Enabled by default. ! '-fipa-sra' Perform interprocedural scalar replacement of aggregates, removal of unused parameters and replacement of parameters passed by reference by parameters passed by value. ! Enabled at levels '-O2', '-O3' and '-Os'. ! '-finline-limit=N' By default, GCC limits the size of functions that can be inlined. This flag allows coarse control of this limit. N is the size of functions that can be inlined in number of pseudo instructions. Inlining is actually controlled by a number of parameters, which ! may be specified individually by using '--param NAME=VALUE'. The ! '-finline-limit=N' option sets some of these parameters as follows: ! 'max-inline-insns-single' is set to N/2. ! 'max-inline-insns-auto' is set to N/2. See below for a documentation of the individual parameters controlling inlining and for the defaults of these parameters. ! _Note:_ there may be no value to '-finline-limit' that results in default behavior. _Note:_ pseudo instruction represents, in this particular context, --- 5799,5999 ---- -ftree-vrp -fipa-ra ! Please note the warning under `-fgcse' about invoking `-O2' on programs that use computed gotos. ! `-O3' ! Optimize yet more. `-O3' turns on all optimizations specified by ! `-O2' and also turns on the `-finline-functions', ! `-funswitch-loops', `-fpredictive-commoning', ! `-fgcse-after-reload', `-ftree-loop-vectorize', ! `-ftree-loop-distribute-patterns', `-fsplit-paths' ! `-ftree-slp-vectorize', `-fvect-cost-model', `-ftree-partial-pre' ! and `-fipa-cp-clone' options. ! `-O0' Reduce compilation time and make debugging produce the expected results. This is the default. ! `-Os' ! Optimize for size. `-Os' enables all `-O2' optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size. ! `-Os' disables the following optimization flags: -falign-functions -falign-jumps -falign-loops -falign-labels -freorder-blocks -freorder-blocks-algorithm=stc -freorder-blocks-and-partition -fprefetch-loop-arrays ! `-Ofast' ! Disregard strict standards compliance. `-Ofast' enables all `-O3' optimizations. It also enables optimizations that are not valid ! for all standard-compliant programs. It turns on `-ffast-math' ! and the Fortran-specific `-fno-protect-parens' and ! `-fstack-arrays'. ! `-Og' ! Optimize debugging experience. `-Og' enables optimizations that ! do not interfere with debugging. It should be the optimization ! level of choice for the standard edit-compile-debug cycle, offering ! a reasonable level of optimization while maintaining fast ! compilation and a good debugging experience. ! If you use multiple `-O' options, with or without level numbers, the last such option is the one that is effective. ! Options of the form `-fFLAG' specify machine-independent flags. Most flags have both positive and negative forms; the negative form of ! `-ffoo' is `-fno-foo'. In the table below, only one of the forms is ! listed--the one you typically use. You can figure out the other form ! by either removing `no-' or adding it. The following options control specific optimizations. They are either ! activated by `-O' options or are related to ones that are. You can use the following flags in the rare cases when "fine-tuning" of optimizations to be performed is desired. ! `-fno-defer-pop' Always pop the arguments to each function call as soon as that function returns. For machines that must pop arguments after a function call, the compiler normally lets arguments accumulate on the stack for several function calls and pops them all at once. ! Disabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fforward-propagate' Perform a forward propagation pass on RTL. The pass tries to combine two instructions and checks if the result can be simplified. If loop unrolling is active, two passes are performed and the second is scheduled after loop unrolling. ! This option is enabled by default at optimization levels `-O', ! `-O2', `-O3', `-Os'. ! `-ffp-contract=STYLE' ! `-ffp-contract=off' disables floating-point expression contraction. ! `-ffp-contract=fast' enables floating-point expression contraction such as forming of fused multiply-add operations if the target has ! native support for them. `-ffp-contract=on' enables ! floating-point expression contraction if allowed by the language ! standard. This is currently not implemented and treated equal to ! `-ffp-contract=off'. ! The default is `-ffp-contract=fast'. ! `-fomit-frame-pointer' ! Don't keep the frame pointer in a register for functions that ! don't need one. This avoids the instructions to save, set up and ! restore frame pointers; it also makes an extra register available ! in many functions. *It also makes debugging impossible on some ! machines.* On some machines, such as the VAX, this flag has no effect, because the standard calling sequence automatically handles the frame pointer and nothing is saved by pretending it doesn't exist. The ! machine-description macro `FRAME_POINTER_REQUIRED' controls ! whether a target machine supports this flag. *Note Register ! Usage: (gccint)Registers. The default setting (when not optimizing for size) for 32-bit GNU/Linux x86 and 32-bit Darwin x86 targets is ! `-fomit-frame-pointer'. You can configure GCC with the ! `--enable-frame-pointer' configure option to change the default. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-foptimize-sibling-calls' Optimize sibling and tail recursive calls. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-foptimize-strlen' ! Optimize various standard C string functions (e.g. `strlen', ! `strchr' or `strcpy') and their `_FORTIFY_SOURCE' counterparts ! into faster alternatives. ! Enabled at levels `-O2', `-O3'. ! `-fno-inline' ! Do not expand any functions inline apart from those marked with ! the `always_inline' attribute. This is the default when not optimizing. ! Single functions can be exempted from inlining by marking them ! with the `noinline' attribute. ! `-finline-small-functions' Integrate functions into their callers when their body is smaller than expected function call code (so overall size of program gets smaller). The compiler heuristically decides which functions are simple enough to be worth integrating in this way. This inlining applies to all functions, even those not declared inline. ! Enabled at level `-O2'. ! `-findirect-inlining' Inline also indirect calls that are discovered to be known at compile time thanks to previous inlining. This option has any effect only when inlining itself is turned on by the ! `-finline-functions' or `-finline-small-functions' options. ! Enabled at level `-O2'. ! `-finline-functions' Consider all functions for inlining, even if they are not declared inline. The compiler heuristically decides which functions are worth integrating in this way. If all calls to a given function are integrated, and the function ! is declared `static', then the function is normally not output as assembler code in its own right. ! Enabled at level `-O3'. ! `-finline-functions-called-once' ! Consider all `static' functions called once for inlining into their ! caller even if they are not marked `inline'. If a call to a given function is integrated, then the function is not output as assembler code in its own right. ! Enabled at levels `-O1', `-O2', `-O3' and `-Os'. ! `-fearly-inlining' ! Inline functions marked by `always_inline' and functions whose ! body seems smaller than the function call overhead early before ! doing `-fprofile-generate' instrumentation and real inlining pass. ! Doing so makes profiling significantly cheaper and usually ! inlining faster on programs having large chains of nested wrapper ! functions. Enabled by default. ! `-fipa-sra' Perform interprocedural scalar replacement of aggregates, removal of unused parameters and replacement of parameters passed by reference by parameters passed by value. ! Enabled at levels `-O2', `-O3' and `-Os'. ! `-finline-limit=N' By default, GCC limits the size of functions that can be inlined. This flag allows coarse control of this limit. N is the size of functions that can be inlined in number of pseudo instructions. Inlining is actually controlled by a number of parameters, which ! may be specified individually by using `--param NAME=VALUE'. The ! `-finline-limit=N' option sets some of these parameters as follows: ! `max-inline-insns-single' is set to N/2. ! ! `max-inline-insns-auto' is set to N/2. See below for a documentation of the individual parameters controlling inlining and for the defaults of these parameters. ! _Note:_ there may be no value to `-finline-limit' that results in default behavior. _Note:_ pseudo instruction represents, in this particular context, *************** optimizations to be performed is desired *** 5955,6035 **** represent a count of assembly instructions and as such its exact meaning might change from one release to an another. ! '-fno-keep-inline-dllexport' ! This is a more fine-grained version of '-fkeep-inline-functions', which applies only to functions that are declared using the ! 'dllexport' attribute or declspec (*Note Declaring Attributes of Functions: Function Attributes.) ! '-fkeep-inline-functions' ! In C, emit 'static' functions that are declared 'inline' into the object file, even if the function has been inlined into all of its ! callers. This switch does not affect functions using the 'extern inline' extension in GNU C90. In C++, emit any and all inline functions into the object file. ! '-fkeep-static-functions' ! Emit 'static' functions into the object file, even if the function is never used. ! '-fkeep-static-consts' ! Emit variables declared 'static const' when optimization isn't turned on, even if the variables aren't referenced. GCC enables this option by default. If you want to force the compiler to check if a variable is referenced, regardless of whether or not optimization is turned on, use the ! '-fno-keep-static-consts' option. ! '-fmerge-constants' Attempt to merge identical constants (string constants and floating-point constants) across compilation units. This option is the default for optimized compilation if the ! assembler and linker support it. Use '-fno-merge-constants' to inhibit this behavior. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fmerge-all-constants' Attempt to merge identical constants and identical variables. ! This option implies '-fmerge-constants'. In addition to ! '-fmerge-constants' this considers e.g. even constant initialized arrays or initialized constant variables with integral or floating-point types. Languages like C or C++ require each variable, including multiple instances of the same variable in recursive calls, to have distinct locations, so using this option results in non-conforming behavior. ! '-fmodulo-sched' Perform swing modulo scheduling immediately before the first scheduling pass. This pass looks at innermost loops and reorders their instructions by overlapping different iterations. ! '-fmodulo-sched-allow-regmoves' Perform more aggressive SMS-based modulo scheduling with register ! moves allowed. By setting this flag certain anti-dependences edges ! are deleted, which triggers the generation of reg-moves based on ! the life-range analysis. This option is effective only with ! '-fmodulo-sched' enabled. ! '-fno-branch-count-reg' Avoid running a pass scanning for opportunities to use "decrement and branch" instructions on a count register instead of generating sequences of instructions that decrement a register, compare it against zero, and then branch based upon the result. This option ! is only meaningful on architectures that support such instructions, ! which include x86, PowerPC, IA-64 and S/390. Note that the ! '-fno-branch-count-reg' option doesn't remove the decrement and ! branch instructions from the generated instruction stream ! introduced by other optimization passes. ! Enabled by default at '-O1' and higher. ! The default is '-fbranch-count-reg'. ! '-fno-function-cse' Do not put function addresses in registers; make each instruction that calls a constant function contain the function's address explicitly. --- 6001,6081 ---- represent a count of assembly instructions and as such its exact meaning might change from one release to an another. ! `-fno-keep-inline-dllexport' ! This is a more fine-grained version of `-fkeep-inline-functions', which applies only to functions that are declared using the ! `dllexport' attribute or declspec (*Note Declaring Attributes of Functions: Function Attributes.) ! `-fkeep-inline-functions' ! In C, emit `static' functions that are declared `inline' into the object file, even if the function has been inlined into all of its ! callers. This switch does not affect functions using the `extern inline' extension in GNU C90. In C++, emit any and all inline functions into the object file. ! `-fkeep-static-functions' ! Emit `static' functions into the object file, even if the function is never used. ! `-fkeep-static-consts' ! Emit variables declared `static const' when optimization isn't turned on, even if the variables aren't referenced. GCC enables this option by default. If you want to force the compiler to check if a variable is referenced, regardless of whether or not optimization is turned on, use the ! `-fno-keep-static-consts' option. ! `-fmerge-constants' Attempt to merge identical constants (string constants and floating-point constants) across compilation units. This option is the default for optimized compilation if the ! assembler and linker support it. Use `-fno-merge-constants' to inhibit this behavior. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fmerge-all-constants' Attempt to merge identical constants and identical variables. ! This option implies `-fmerge-constants'. In addition to ! `-fmerge-constants' this considers e.g. even constant initialized arrays or initialized constant variables with integral or floating-point types. Languages like C or C++ require each variable, including multiple instances of the same variable in recursive calls, to have distinct locations, so using this option results in non-conforming behavior. ! `-fmodulo-sched' Perform swing modulo scheduling immediately before the first scheduling pass. This pass looks at innermost loops and reorders their instructions by overlapping different iterations. ! `-fmodulo-sched-allow-regmoves' Perform more aggressive SMS-based modulo scheduling with register ! moves allowed. By setting this flag certain anti-dependences ! edges are deleted, which triggers the generation of reg-moves ! based on the life-range analysis. This option is effective only ! with `-fmodulo-sched' enabled. ! `-fno-branch-count-reg' Avoid running a pass scanning for opportunities to use "decrement and branch" instructions on a count register instead of generating sequences of instructions that decrement a register, compare it against zero, and then branch based upon the result. This option ! is only meaningful on architectures that support such ! instructions, which include x86, PowerPC, IA-64 and S/390. Note ! that the `-fno-branch-count-reg' option doesn't remove the ! decrement and branch instructions from the generated instruction ! stream introduced by other optimization passes. ! Enabled by default at `-O1' and higher. ! The default is `-fbranch-count-reg'. ! `-fno-function-cse' Do not put function addresses in registers; make each instruction that calls a constant function contain the function's address explicitly. *************** optimizations to be performed is desired *** 6038,6198 **** that alter the assembler output may be confused by the optimizations performed when this option is not used. ! The default is '-ffunction-cse' ! '-fno-zero-initialized-in-bss' ! If the target supports a BSS section, GCC by default puts variables ! that are initialized to zero into BSS. This can save space in the ! resulting code. This option turns off this behavior because some programs explicitly rely on variables going to the data section--e.g., so that the resulting executable can find the beginning of that section and/or make assumptions based on that. ! The default is '-fzero-initialized-in-bss'. ! '-fthread-jumps' Perform optimizations that check to see if a jump branches to a location where another comparison subsumed by the first is found. If so, the first branch is redirected to either the destination of ! the second branch or a point immediately following it, depending on ! whether the condition is known to be true or false. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fsplit-wide-types' ! When using a type that occupies multiple registers, such as 'long long' on a 32-bit system, split the registers apart and allocate them independently. This normally generates better code for those types, but may make debugging more difficult. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fcse-follow-jumps' In common subexpression elimination (CSE), scan through jump instructions when the target of the jump is not reached by any ! other path. For example, when CSE encounters an 'if' statement ! with an 'else' clause, CSE follows the jump when the condition tested is false. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fcse-skip-blocks' ! This is similar to '-fcse-follow-jumps', but causes CSE to follow jumps that conditionally skip over blocks. When CSE encounters a ! simple 'if' statement with no else clause, '-fcse-skip-blocks' ! causes CSE to follow the jump around the body of the 'if'. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-frerun-cse-after-loop' Re-run common subexpression elimination after loop optimizations are performed. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fgcse' Perform a global common subexpression elimination pass. This pass also performs global constant and copy propagation. _Note:_ When compiling a program using computed gotos, a GCC extension, you may get better run-time performance if you disable the global common subexpression elimination pass by adding ! '-fno-gcse' to the command line. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fgcse-lm' ! When '-fgcse-lm' is enabled, global common subexpression elimination attempts to move loads that are only killed by stores into themselves. This allows a loop containing a load/store ! sequence to be changed to a load outside the loop, and a copy/store ! within the loop. ! Enabled by default when '-fgcse' is enabled. ! '-fgcse-sm' ! When '-fgcse-sm' is enabled, a store motion pass is run after global common subexpression elimination. This pass attempts to move stores out of loops. When used in conjunction with ! '-fgcse-lm', loops containing a load/store sequence can be changed to a load before the loop and a store after the loop. Not enabled at any optimization level. ! '-fgcse-las' ! When '-fgcse-las' is enabled, the global common subexpression elimination pass eliminates redundant loads that come after stores to the same memory location (both partial and full redundancies). Not enabled at any optimization level. ! '-fgcse-after-reload' ! When '-fgcse-after-reload' is enabled, a redundant load elimination pass is performed after reload. The purpose of this pass is to clean up redundant spilling. ! '-faggressive-loop-optimizations' This option tells the loop optimizer to use language constraints to ! derive bounds for the number of iterations of a loop. This assumes ! that loop code does not invoke undefined behavior by for example ! causing signed integer overflows or out-of-bound array accesses. ! The bounds for the number of iterations of a loop are used to guide ! loop unrolling and peeling and loop exit test optimizations. This ! option is enabled by default. ! '-funsafe-loop-optimizations' ! This option tells the loop optimizer to assume that loop indices do ! not overflow, and that loops with nontrivial exit condition are not ! infinite. This enables a wider range of loop optimizations even if ! the loop optimizer itself cannot prove that these assumptions are ! valid. If you use '-Wunsafe-loop-optimizations', the compiler ! warns you if it finds this kind of loop. ! '-funconstrained-commons' This option tells the compiler that variables declared in common ! blocks (e.g. Fortran) may later be overridden with longer trailing ! arrays. This prevents certain optimizations that depend on knowing the array bounds. ! '-fcrossjumping' Perform cross-jumping transformation. This transformation unifies ! equivalent code and saves code size. The resulting code may or may ! not perform better than without cross-jumping. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fauto-inc-dec' Combine increments or decrements of addresses with memory accesses. This pass is always skipped on architectures that do not have ! instructions to support this. Enabled by default at '-O' and higher on architectures that support this. ! '-fdce' Perform dead code elimination (DCE) on RTL. Enabled by default at ! '-O' and higher. ! '-fdse' ! Perform dead store elimination (DSE) on RTL. Enabled by default at ! '-O' and higher. ! '-fif-conversion' Attempt to transform conditional jumps into branch-less ! equivalents. This includes use of conditional moves, min, max, set ! flags and abs instructions, and some tricks doable by standard ! arithmetics. The use of conditional execution on chips where it is ! available is controlled by '-fif-conversion2'. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fif-conversion2' Use conditional execution (where available) to transform conditional jumps into branch-less equivalents. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fdeclone-ctor-dtor' The C++ ABI requires multiple entry points for constructors and destructors: one for a base subobject, one for a complete object, and one for a virtual destructor that calls operator delete --- 6084,6244 ---- that alter the assembler output may be confused by the optimizations performed when this option is not used. ! The default is `-ffunction-cse' ! `-fno-zero-initialized-in-bss' ! If the target supports a BSS section, GCC by default puts ! variables that are initialized to zero into BSS. This can save ! space in the resulting code. This option turns off this behavior because some programs explicitly rely on variables going to the data section--e.g., so that the resulting executable can find the beginning of that section and/or make assumptions based on that. ! The default is `-fzero-initialized-in-bss'. ! `-fthread-jumps' Perform optimizations that check to see if a jump branches to a location where another comparison subsumed by the first is found. If so, the first branch is redirected to either the destination of ! the second branch or a point immediately following it, depending ! on whether the condition is known to be true or false. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fsplit-wide-types' ! When using a type that occupies multiple registers, such as `long long' on a 32-bit system, split the registers apart and allocate them independently. This normally generates better code for those types, but may make debugging more difficult. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fcse-follow-jumps' In common subexpression elimination (CSE), scan through jump instructions when the target of the jump is not reached by any ! other path. For example, when CSE encounters an `if' statement ! with an `else' clause, CSE follows the jump when the condition tested is false. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fcse-skip-blocks' ! This is similar to `-fcse-follow-jumps', but causes CSE to follow jumps that conditionally skip over blocks. When CSE encounters a ! simple `if' statement with no else clause, `-fcse-skip-blocks' ! causes CSE to follow the jump around the body of the `if'. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-frerun-cse-after-loop' Re-run common subexpression elimination after loop optimizations are performed. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fgcse' Perform a global common subexpression elimination pass. This pass also performs global constant and copy propagation. _Note:_ When compiling a program using computed gotos, a GCC extension, you may get better run-time performance if you disable the global common subexpression elimination pass by adding ! `-fno-gcse' to the command line. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fgcse-lm' ! When `-fgcse-lm' is enabled, global common subexpression elimination attempts to move loads that are only killed by stores into themselves. This allows a loop containing a load/store ! sequence to be changed to a load outside the loop, and a ! copy/store within the loop. ! Enabled by default when `-fgcse' is enabled. ! `-fgcse-sm' ! When `-fgcse-sm' is enabled, a store motion pass is run after global common subexpression elimination. This pass attempts to move stores out of loops. When used in conjunction with ! `-fgcse-lm', loops containing a load/store sequence can be changed to a load before the loop and a store after the loop. Not enabled at any optimization level. ! `-fgcse-las' ! When `-fgcse-las' is enabled, the global common subexpression elimination pass eliminates redundant loads that come after stores to the same memory location (both partial and full redundancies). Not enabled at any optimization level. ! `-fgcse-after-reload' ! When `-fgcse-after-reload' is enabled, a redundant load elimination pass is performed after reload. The purpose of this pass is to clean up redundant spilling. ! `-faggressive-loop-optimizations' This option tells the loop optimizer to use language constraints to ! derive bounds for the number of iterations of a loop. This ! assumes that loop code does not invoke undefined behavior by for ! example causing signed integer overflows or out-of-bound array ! accesses. The bounds for the number of iterations of a loop are ! used to guide loop unrolling and peeling and loop exit test ! optimizations. This option is enabled by default. ! `-funsafe-loop-optimizations' ! This option tells the loop optimizer to assume that loop indices ! do not overflow, and that loops with nontrivial exit condition are ! not infinite. This enables a wider range of loop optimizations ! even if the loop optimizer itself cannot prove that these ! assumptions are valid. If you use `-Wunsafe-loop-optimizations', ! the compiler warns you if it finds this kind of loop. ! `-funconstrained-commons' This option tells the compiler that variables declared in common ! blocks (e.g. Fortran) may later be overridden with longer trailing ! arrays. This prevents certain optimizations that depend on knowing the array bounds. ! `-fcrossjumping' Perform cross-jumping transformation. This transformation unifies ! equivalent code and saves code size. The resulting code may or ! may not perform better than without cross-jumping. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fauto-inc-dec' Combine increments or decrements of addresses with memory accesses. This pass is always skipped on architectures that do not have ! instructions to support this. Enabled by default at `-O' and higher on architectures that support this. ! `-fdce' Perform dead code elimination (DCE) on RTL. Enabled by default at ! `-O' and higher. ! `-fdse' ! Perform dead store elimination (DSE) on RTL. Enabled by default ! at `-O' and higher. ! `-fif-conversion' Attempt to transform conditional jumps into branch-less ! equivalents. This includes use of conditional moves, min, max, ! set flags and abs instructions, and some tricks doable by standard ! arithmetics. The use of conditional execution on chips where it ! is available is controlled by `-fif-conversion2'. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fif-conversion2' Use conditional execution (where available) to transform conditional jumps into branch-less equivalents. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fdeclone-ctor-dtor' The C++ ABI requires multiple entry points for constructors and destructors: one for a base subobject, one for a complete object, and one for a virtual destructor that calls operator delete *************** optimizations to be performed is desired *** 6201,6209 **** function. With this option, the base and complete variants are changed to be thunks that call a common implementation. ! Enabled by '-Os'. ! '-fdelete-null-pointer-checks' Assume that programs cannot safely dereference null pointers, and that no code or data element resides at address zero. This option enables simple constant folding optimizations at all optimization --- 6247,6255 ---- function. With this option, the base and complete variants are changed to be thunks that call a common implementation. ! Enabled by `-Os'. ! `-fdelete-null-pointer-checks' Assume that programs cannot safely dereference null pointers, and that no code or data element resides at address zero. This option enables simple constant folding optimizations at all optimization *************** optimizations to be performed is desired *** 6214,6643 **** checked after it has already been dereferenced, it cannot be null. Note however that in some environments this assumption is not true. ! Use '-fno-delete-null-pointer-checks' to disable this optimization for programs that depend on that behavior. ! This option is enabled by default on most targets. On Nios II ELF, ! it defaults to off. On AVR and CR16, this option is completely ! disabled. Passes that use the dataflow information are enabled independently at different optimization levels. ! '-fdevirtualize' Attempt to convert calls to virtual functions to direct calls. This is done both within a procedure and interprocedurally as part ! of indirect inlining ('-findirect-inlining') and interprocedural ! constant propagation ('-fipa-cp'). Enabled at levels '-O2', '-O3', ! '-Os'. ! '-fdevirtualize-speculatively' ! Attempt to convert calls to virtual functions to speculative direct ! calls. Based on the analysis of the type inheritance graph, ! determine for a given call the set of likely targets. If the set ! is small, preferably of size 1, change the call into a conditional ! deciding between direct and indirect calls. The speculative calls ! enable more optimizations, such as inlining. When they seem ! useless after further optimization, they are converted back into ! original form. ! '-fdevirtualize-at-ltrans' Stream extra information needed for aggressive devirtualization when running the link-time optimizer in local transformation mode. This option enables more devirtualization but significantly ! increases the size of streamed data. For this reason it is disabled by default. ! '-fexpensive-optimizations' Perform a number of minor optimizations that are relatively expensive. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-free' Attempt to remove redundant extension instructions. This is especially helpful for the x86-64 architecture, which implicitly zero-extends in 64-bit registers after writing to their lower 32-bit half. ! Enabled for Alpha, AArch64 and x86 at levels '-O2', '-O3', '-Os'. ! '-fno-lifetime-dse' In C++ the value of an object is only affected by changes within its lifetime: when the constructor begins, the object has an indeterminate value, and any changes during the lifetime of the object are dead when the object is destroyed. Normally dead store ! elimination will take advantage of this; if your code relies on the ! value of the object storage persisting beyond the lifetime of the ! object, you can use this flag to disable this optimization. To ! preserve stores before the constructor starts (e.g. because your ! operator new clears the object storage) but still treat the object ! as dead after the destructor you, can use '-flifetime-dse=1'. The ! default behavior can be explicitly selected with ! '-flifetime-dse=2'. '-flifetime-dse=0' is equivalent to ! '-fno-lifetime-dse'. ! '-flive-range-shrinkage' Attempt to decrease register pressure through register live range shrinkage. This is helpful for fast processors with small or moderate size register sets. ! '-fira-algorithm=ALGORITHM' Use the specified coloring algorithm for the integrated register ! allocator. The ALGORITHM argument can be 'priority', which ! specifies Chow's priority coloring, or 'CB', which specifies Chaitin-Briggs coloring. Chaitin-Briggs coloring is not implemented for all architectures, but for those targets that do support it, it is the default because it generates better code. ! '-fira-region=REGION' Use specified regions for the integrated register allocator. The REGION argument should be one of the following: ! 'all' Use all loops as register allocation regions. This can give the best results for machines with a small and/or irregular register set. ! 'mixed' ! Use all loops except for loops with small register pressure as ! the regions. This value usually gives the best results in most cases and for most architectures, and is enabled by ! default when compiling with optimization for speed ('-O', ! '-O2', ...). ! 'one' Use all functions as a single region. This typically results ! in the smallest code size, and is enabled by default for '-Os' ! or '-O0'. ! '-fira-hoist-pressure' Use IRA to evaluate register pressure in the code hoisting pass for decisions to hoist expressions. This option usually results in smaller code, but it can slow the compiler down. ! This option is enabled at level '-Os' for all targets. ! '-fira-loop-pressure' Use IRA to evaluate register pressure in loops for decisions to ! move loop invariants. This option usually results in generation of ! faster and smaller code on machines with large register files (>= ! 32 registers), but it can slow the compiler down. ! This option is enabled at level '-O3' for some targets. ! '-fno-ira-share-save-slots' Disable sharing of stack slots used for saving call-used hard registers living through a call. Each hard register gets a separate stack slot, and as a result function stack frames are larger. ! '-fno-ira-share-spill-slots' Disable sharing of stack slots allocated for pseudo-registers. Each pseudo-register that does not get a hard register gets a separate stack slot, and as a result function stack frames are larger. ! '-flra-remat' ! Enable CFG-sensitive rematerialization in LRA. Instead of loading values of spilled pseudos, LRA tries to rematerialize (recalculate) values if it is profitable. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fdelayed-branch' If supported for the target machine, attempt to reorder instructions to exploit instruction slots available after delayed branch instructions. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fschedule-insns' If supported for the target machine, attempt to reorder instructions to eliminate execution stalls due to required data being unavailable. This helps machines that have slow floating ! point or memory load instructions by allowing other instructions to ! be issued until the result of the load or floating-point instruction is required. ! Enabled at levels '-O2', '-O3'. ! '-fschedule-insns2' ! Similar to '-fschedule-insns', but requests an additional pass of instruction scheduling after register allocation has been done. This is especially useful on machines with a relatively small number of registers and where memory load instructions take more than one cycle. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fno-sched-interblock' Don't schedule instructions across basic blocks. This is normally enabled by default when scheduling before register allocation, i.e. ! with '-fschedule-insns' or at '-O2' or higher. ! '-fno-sched-spec' Don't allow speculative motion of non-load instructions. This is normally enabled by default when scheduling before register ! allocation, i.e. with '-fschedule-insns' or at '-O2' or higher. ! '-fsched-pressure' Enable register pressure sensitive insn scheduling before register allocation. This only makes sense when scheduling before register ! allocation is enabled, i.e. with '-fschedule-insns' or at '-O2' or higher. Usage of this option can improve the generated code and decrease its size by preventing register pressure increase above the number of available hard registers and subsequent spills in register allocation. ! '-fsched-spec-load' Allow speculative motion of some load instructions. This only makes sense when scheduling before register allocation, i.e. with ! '-fschedule-insns' or at '-O2' or higher. ! '-fsched-spec-load-dangerous' Allow speculative motion of more load instructions. This only makes sense when scheduling before register allocation, i.e. with ! '-fschedule-insns' or at '-O2' or higher. ! '-fsched-stalled-insns' ! '-fsched-stalled-insns=N' Define how many insns (if any) can be moved prematurely from the queue of stalled insns into the ready list during the second ! scheduling pass. '-fno-sched-stalled-insns' means that no insns ! are moved prematurely, '-fsched-stalled-insns=0' means there is no limit on how many queued insns can be moved prematurely. ! '-fsched-stalled-insns' without a value is equivalent to ! '-fsched-stalled-insns=1'. ! '-fsched-stalled-insns-dep' ! '-fsched-stalled-insns-dep=N' Define how many insn groups (cycles) are examined for a dependency on a stalled insn that is a candidate for premature removal from the queue of stalled insns. This has an effect only during the ! second scheduling pass, and only if '-fsched-stalled-insns' is ! used. '-fno-sched-stalled-insns-dep' is equivalent to ! '-fsched-stalled-insns-dep=0'. '-fsched-stalled-insns-dep' without ! a value is equivalent to '-fsched-stalled-insns-dep=1'. ! '-fsched2-use-superblocks' When scheduling after register allocation, use superblock scheduling. This allows motion across basic block boundaries, ! resulting in faster schedules. This option is experimental, as not ! all machine descriptions used by GCC model the CPU closely enough ! to avoid unreliable results from the algorithm. This only makes sense when scheduling after register allocation, ! i.e. with '-fschedule-insns2' or at '-O2' or higher. ! '-fsched-group-heuristic' Enable the group heuristic in the scheduler. This heuristic favors the instruction that belongs to a schedule group. This is enabled ! by default when scheduling is enabled, i.e. with '-fschedule-insns' ! or '-fschedule-insns2' or at '-O2' or higher. ! '-fsched-critical-path-heuristic' Enable the critical-path heuristic in the scheduler. This heuristic favors instructions on the critical path. This is enabled by default when scheduling is enabled, i.e. with ! '-fschedule-insns' or '-fschedule-insns2' or at '-O2' or higher. ! '-fsched-spec-insn-heuristic' Enable the speculative instruction heuristic in the scheduler. This heuristic favors speculative instructions with greater ! dependency weakness. This is enabled by default when scheduling is ! enabled, i.e. with '-fschedule-insns' or '-fschedule-insns2' or at ! '-O2' or higher. ! '-fsched-rank-heuristic' Enable the rank heuristic in the scheduler. This heuristic favors the instruction belonging to a basic block with greater size or frequency. This is enabled by default when scheduling is enabled, ! i.e. with '-fschedule-insns' or '-fschedule-insns2' or at '-O2' or ! higher. ! '-fsched-last-insn-heuristic' Enable the last-instruction heuristic in the scheduler. This ! heuristic favors the instruction that is less dependent on the last ! instruction scheduled. This is enabled by default when scheduling ! is enabled, i.e. with '-fschedule-insns' or '-fschedule-insns2' or ! at '-O2' or higher. ! '-fsched-dep-count-heuristic' Enable the dependent-count heuristic in the scheduler. This heuristic favors the instruction that has more instructions depending on it. This is enabled by default when scheduling is ! enabled, i.e. with '-fschedule-insns' or '-fschedule-insns2' or at ! '-O2' or higher. ! '-freschedule-modulo-scheduled-loops' ! Modulo scheduling is performed before traditional scheduling. If a ! loop is modulo scheduled, later scheduling passes may change its schedule. Use this option to control that behavior. ! '-fselective-scheduling' Schedule instructions using selective scheduling algorithm. Selective scheduling runs instead of the first scheduler pass. ! '-fselective-scheduling2' Schedule instructions using selective scheduling algorithm. Selective scheduling runs instead of the second scheduler pass. ! '-fsel-sched-pipelining' Enable software pipelining of innermost loops during selective scheduling. This option has no effect unless one of ! '-fselective-scheduling' or '-fselective-scheduling2' is turned on. ! '-fsel-sched-pipelining-outer-loops' When pipelining loops during selective scheduling, also pipeline outer loops. This option has no effect unless ! '-fsel-sched-pipelining' is turned on. ! '-fsemantic-interposition' Some object formats, like ELF, allow interposing of symbols by the ! dynamic linker. This means that for symbols exported from the DSO, ! the compiler cannot perform interprocedural propagation, inlining ! and other optimizations in anticipation that the function or ! variable in question may change. While this feature is useful, for ! example, to rewrite memory allocation functions by a debugging ! implementation, it is expensive in the terms of code quality. With ! '-fno-semantic-interposition' the compiler assumes that if interposition happens for functions the overwriting function will ! have precisely the same semantics (and side effects). Similarly if ! interposition happens for variables, the constructor of the ! variable will be the same. The flag has no effect for functions explicitly declared inline (where it is never allowed for interposition to change semantics) and for symbols explicitly declared weak. ! '-fshrink-wrap' ! Emit function prologues only before parts of the function that need ! it, rather than at the top of the function. This flag is enabled ! by default at '-O' and higher. ! '-fcaller-saves' Enable allocation of values to registers that are clobbered by function calls, by emitting extra instructions to save and restore ! the registers around such calls. Such allocation is done only when ! it seems to result in better code. This option is always enabled by default on certain machines, usually those which have no call-preserved registers to use instead. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fcombine-stack-adjustments' Tracks stack adjustments (pushes and pops) and stack memory references and then tries to find ways to combine them. ! Enabled by default at '-O1' and higher. ! '-fipa-ra' ! Use caller save registers for allocation if those registers are not ! used by any called function. In that case it is not necessary to ! save and restore them around calls. This is only possible if called functions are part of same compilation unit as current function and they are compiled before it. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fconserve-stack' Attempt to minimize stack usage. The compiler attempts to use less stack space, even if that makes the program slower. This option ! implies setting the 'large-stack-frame' parameter to 100 and the ! 'large-stack-frame-growth' parameter to 400. ! '-ftree-reassoc' ! Perform reassociation on trees. This flag is enabled by default at ! '-O' and higher. ! '-ftree-pre' Perform partial redundancy elimination (PRE) on trees. This flag ! is enabled by default at '-O2' and '-O3'. ! '-ftree-partial-pre' Make partial redundancy elimination (PRE) more aggressive. This ! flag is enabled by default at '-O3'. ! '-ftree-forwprop' Perform forward propagation on trees. This flag is enabled by ! default at '-O' and higher. ! '-ftree-fre' Perform full redundancy elimination (FRE) on trees. The difference ! between FRE and PRE is that FRE only considers expressions that are ! computed on all paths leading to the redundant computation. This ! analysis is faster than PRE, though it exposes fewer redundancies. ! This flag is enabled by default at '-O' and higher. ! '-ftree-phiprop' Perform hoisting of loads from conditional pointers on trees. This ! pass is enabled by default at '-O' and higher. ! '-fhoist-adjacent-loads' Speculatively hoist loads from both branches of an if-then-else if ! the loads are from adjacent locations in the same structure and the ! target architecture has a conditional move instruction. This flag ! is enabled by default at '-O2' and higher. ! '-ftree-copy-prop' Perform copy propagation on trees. This pass eliminates unnecessary copy operations. This flag is enabled by default at ! '-O' and higher. ! '-fipa-pure-const' Discover which functions are pure or constant. Enabled by default ! at '-O' and higher. ! '-fipa-reference' Discover which static variables do not escape the compilation unit. ! Enabled by default at '-O' and higher. ! '-fipa-pta' Perform interprocedural pointer analysis and interprocedural modification and reference analysis. This option can cause ! excessive memory and compile-time usage on large compilation units. ! It is not enabled by default at any optimization level. ! '-fipa-profile' Perform interprocedural profile propagation. The functions called ! only from cold functions are marked as cold. Also functions ! executed once (such as 'cold', 'noreturn', static constructors or ! destructors) are identified. Cold functions and loop less parts of functions executed once are then optimized for size. Enabled by ! default at '-O' and higher. ! '-fipa-cp' Perform interprocedural constant propagation. This optimization analyzes the program to determine when values passed to functions are constants and then optimizes accordingly. This optimization can substantially increase performance if the application has constants passed to functions. This flag is enabled by default at ! '-O2', '-Os' and '-O3'. ! '-fipa-cp-clone' Perform function cloning to make interprocedural constant propagation stronger. When enabled, interprocedural constant propagation performs function cloning when externally visible function can be called with constant arguments. Because this optimization can create multiple copies of functions, it may ! significantly increase code size (see '--param ipcp-unit-growth=VALUE'). This flag is enabled by default at ! '-O3'. ! '-fipa-cp-alignment' When enabled, this optimization propagates alignment of function parameters to support better vectorization and string operations. ! This flag is enabled by default at '-O2' and '-Os'. It requires ! that '-fipa-cp' is enabled. ! '-fipa-icf' Perform Identical Code Folding for functions and read-only variables. The optimization reduces code size and may disturb unwind stacks by replacing a function by equivalent one with a ! different name. The optimization works more effectively with link time optimization enabled. Nevertheless the behavior is similar to Gold Linker ICF --- 6260,6690 ---- checked after it has already been dereferenced, it cannot be null. Note however that in some environments this assumption is not true. ! Use `-fno-delete-null-pointer-checks' to disable this optimization for programs that depend on that behavior. ! This option is enabled by default on most targets. On Nios II ! ELF, it defaults to off. On AVR and CR16, this option is ! completely disabled. Passes that use the dataflow information are enabled independently at different optimization levels. ! `-fdevirtualize' Attempt to convert calls to virtual functions to direct calls. This is done both within a procedure and interprocedurally as part ! of indirect inlining (`-findirect-inlining') and interprocedural ! constant propagation (`-fipa-cp'). Enabled at levels `-O2', ! `-O3', `-Os'. ! `-fdevirtualize-speculatively' ! Attempt to convert calls to virtual functions to speculative ! direct calls. Based on the analysis of the type inheritance ! graph, determine for a given call the set of likely targets. If ! the set is small, preferably of size 1, change the call into a ! conditional deciding between direct and indirect calls. The ! speculative calls enable more optimizations, such as inlining. ! When they seem useless after further optimization, they are ! converted back into original form. ! `-fdevirtualize-at-ltrans' Stream extra information needed for aggressive devirtualization when running the link-time optimizer in local transformation mode. This option enables more devirtualization but significantly ! increases the size of streamed data. For this reason it is disabled by default. ! `-fexpensive-optimizations' Perform a number of minor optimizations that are relatively expensive. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-free' Attempt to remove redundant extension instructions. This is especially helpful for the x86-64 architecture, which implicitly zero-extends in 64-bit registers after writing to their lower 32-bit half. ! Enabled for Alpha, AArch64 and x86 at levels `-O2', `-O3', `-Os'. ! `-fno-lifetime-dse' In C++ the value of an object is only affected by changes within its lifetime: when the constructor begins, the object has an indeterminate value, and any changes during the lifetime of the object are dead when the object is destroyed. Normally dead store ! elimination will take advantage of this; if your code relies on ! the value of the object storage persisting beyond the lifetime of ! the object, you can use this flag to disable this optimization. ! To preserve stores before the constructor starts (e.g. because ! your operator new clears the object storage) but still treat the ! object as dead after the destructor you, can use ! `-flifetime-dse=1'. The default behavior can be explicitly ! selected with `-flifetime-dse=2'. `-flifetime-dse=0' is ! equivalent to `-fno-lifetime-dse'. ! `-flive-range-shrinkage' Attempt to decrease register pressure through register live range shrinkage. This is helpful for fast processors with small or moderate size register sets. ! `-fira-algorithm=ALGORITHM' Use the specified coloring algorithm for the integrated register ! allocator. The ALGORITHM argument can be `priority', which ! specifies Chow's priority coloring, or `CB', which specifies Chaitin-Briggs coloring. Chaitin-Briggs coloring is not implemented for all architectures, but for those targets that do support it, it is the default because it generates better code. ! `-fira-region=REGION' Use specified regions for the integrated register allocator. The REGION argument should be one of the following: ! `all' Use all loops as register allocation regions. This can give the best results for machines with a small and/or irregular register set. ! `mixed' ! Use all loops except for loops with small register pressure ! as the regions. This value usually gives the best results in most cases and for most architectures, and is enabled by ! default when compiling with optimization for speed (`-O', ! `-O2', ...). ! `one' Use all functions as a single region. This typically results ! in the smallest code size, and is enabled by default for ! `-Os' or `-O0'. ! ! `-fira-hoist-pressure' Use IRA to evaluate register pressure in the code hoisting pass for decisions to hoist expressions. This option usually results in smaller code, but it can slow the compiler down. ! This option is enabled at level `-Os' for all targets. ! `-fira-loop-pressure' Use IRA to evaluate register pressure in loops for decisions to ! move loop invariants. This option usually results in generation ! of faster and smaller code on machines with large register files ! (>= 32 registers), but it can slow the compiler down. ! This option is enabled at level `-O3' for some targets. ! `-fno-ira-share-save-slots' Disable sharing of stack slots used for saving call-used hard registers living through a call. Each hard register gets a separate stack slot, and as a result function stack frames are larger. ! `-fno-ira-share-spill-slots' Disable sharing of stack slots allocated for pseudo-registers. Each pseudo-register that does not get a hard register gets a separate stack slot, and as a result function stack frames are larger. ! `-flra-remat' ! Enable CFG-sensitive rematerialization in LRA. Instead of loading values of spilled pseudos, LRA tries to rematerialize (recalculate) values if it is profitable. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fdelayed-branch' If supported for the target machine, attempt to reorder instructions to exploit instruction slots available after delayed branch instructions. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fschedule-insns' If supported for the target machine, attempt to reorder instructions to eliminate execution stalls due to required data being unavailable. This helps machines that have slow floating ! point or memory load instructions by allowing other instructions ! to be issued until the result of the load or floating-point instruction is required. ! Enabled at levels `-O2', `-O3'. ! `-fschedule-insns2' ! Similar to `-fschedule-insns', but requests an additional pass of instruction scheduling after register allocation has been done. This is especially useful on machines with a relatively small number of registers and where memory load instructions take more than one cycle. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fno-sched-interblock' Don't schedule instructions across basic blocks. This is normally enabled by default when scheduling before register allocation, i.e. ! with `-fschedule-insns' or at `-O2' or higher. ! `-fno-sched-spec' Don't allow speculative motion of non-load instructions. This is normally enabled by default when scheduling before register ! allocation, i.e. with `-fschedule-insns' or at `-O2' or higher. ! `-fsched-pressure' Enable register pressure sensitive insn scheduling before register allocation. This only makes sense when scheduling before register ! allocation is enabled, i.e. with `-fschedule-insns' or at `-O2' or higher. Usage of this option can improve the generated code and decrease its size by preventing register pressure increase above the number of available hard registers and subsequent spills in register allocation. ! `-fsched-spec-load' Allow speculative motion of some load instructions. This only makes sense when scheduling before register allocation, i.e. with ! `-fschedule-insns' or at `-O2' or higher. ! `-fsched-spec-load-dangerous' Allow speculative motion of more load instructions. This only makes sense when scheduling before register allocation, i.e. with ! `-fschedule-insns' or at `-O2' or higher. ! `-fsched-stalled-insns' ! `-fsched-stalled-insns=N' Define how many insns (if any) can be moved prematurely from the queue of stalled insns into the ready list during the second ! scheduling pass. `-fno-sched-stalled-insns' means that no insns ! are moved prematurely, `-fsched-stalled-insns=0' means there is no limit on how many queued insns can be moved prematurely. ! `-fsched-stalled-insns' without a value is equivalent to ! `-fsched-stalled-insns=1'. ! `-fsched-stalled-insns-dep' ! `-fsched-stalled-insns-dep=N' Define how many insn groups (cycles) are examined for a dependency on a stalled insn that is a candidate for premature removal from the queue of stalled insns. This has an effect only during the ! second scheduling pass, and only if `-fsched-stalled-insns' is ! used. `-fno-sched-stalled-insns-dep' is equivalent to ! `-fsched-stalled-insns-dep=0'. `-fsched-stalled-insns-dep' ! without a value is equivalent to `-fsched-stalled-insns-dep=1'. ! `-fsched2-use-superblocks' When scheduling after register allocation, use superblock scheduling. This allows motion across basic block boundaries, ! resulting in faster schedules. This option is experimental, as ! not all machine descriptions used by GCC model the CPU closely ! enough to avoid unreliable results from the algorithm. This only makes sense when scheduling after register allocation, ! i.e. with `-fschedule-insns2' or at `-O2' or higher. ! `-fsched-group-heuristic' Enable the group heuristic in the scheduler. This heuristic favors the instruction that belongs to a schedule group. This is enabled ! by default when scheduling is enabled, i.e. with `-fschedule-insns' ! or `-fschedule-insns2' or at `-O2' or higher. ! `-fsched-critical-path-heuristic' Enable the critical-path heuristic in the scheduler. This heuristic favors instructions on the critical path. This is enabled by default when scheduling is enabled, i.e. with ! `-fschedule-insns' or `-fschedule-insns2' or at `-O2' or higher. ! `-fsched-spec-insn-heuristic' Enable the speculative instruction heuristic in the scheduler. This heuristic favors speculative instructions with greater ! dependency weakness. This is enabled by default when scheduling ! is enabled, i.e. with `-fschedule-insns' or `-fschedule-insns2' ! or at `-O2' or higher. ! `-fsched-rank-heuristic' Enable the rank heuristic in the scheduler. This heuristic favors the instruction belonging to a basic block with greater size or frequency. This is enabled by default when scheduling is enabled, ! i.e. with `-fschedule-insns' or `-fschedule-insns2' or at `-O2' ! or higher. ! `-fsched-last-insn-heuristic' Enable the last-instruction heuristic in the scheduler. This ! heuristic favors the instruction that is less dependent on the ! last instruction scheduled. This is enabled by default when ! scheduling is enabled, i.e. with `-fschedule-insns' or ! `-fschedule-insns2' or at `-O2' or higher. ! `-fsched-dep-count-heuristic' Enable the dependent-count heuristic in the scheduler. This heuristic favors the instruction that has more instructions depending on it. This is enabled by default when scheduling is ! enabled, i.e. with `-fschedule-insns' or `-fschedule-insns2' or ! at `-O2' or higher. ! `-freschedule-modulo-scheduled-loops' ! Modulo scheduling is performed before traditional scheduling. If ! a loop is modulo scheduled, later scheduling passes may change its schedule. Use this option to control that behavior. ! `-fselective-scheduling' Schedule instructions using selective scheduling algorithm. Selective scheduling runs instead of the first scheduler pass. ! `-fselective-scheduling2' Schedule instructions using selective scheduling algorithm. Selective scheduling runs instead of the second scheduler pass. ! `-fsel-sched-pipelining' Enable software pipelining of innermost loops during selective scheduling. This option has no effect unless one of ! `-fselective-scheduling' or `-fselective-scheduling2' is turned on. ! `-fsel-sched-pipelining-outer-loops' When pipelining loops during selective scheduling, also pipeline outer loops. This option has no effect unless ! `-fsel-sched-pipelining' is turned on. ! `-fsemantic-interposition' Some object formats, like ELF, allow interposing of symbols by the ! dynamic linker. This means that for symbols exported from the ! DSO, the compiler cannot perform interprocedural propagation, ! inlining and other optimizations in anticipation that the function ! or variable in question may change. While this feature is useful, ! for example, to rewrite memory allocation functions by a debugging ! implementation, it is expensive in the terms of code quality. ! With `-fno-semantic-interposition' the compiler assumes that if interposition happens for functions the overwriting function will ! have precisely the same semantics (and side effects). Similarly ! if interposition happens for variables, the constructor of the ! variable will be the same. The flag has no effect for functions explicitly declared inline (where it is never allowed for interposition to change semantics) and for symbols explicitly declared weak. ! `-fshrink-wrap' ! Emit function prologues only before parts of the function that ! need it, rather than at the top of the function. This flag is ! enabled by default at `-O' and higher. ! `-fcaller-saves' Enable allocation of values to registers that are clobbered by function calls, by emitting extra instructions to save and restore ! the registers around such calls. Such allocation is done only ! when it seems to result in better code. This option is always enabled by default on certain machines, usually those which have no call-preserved registers to use instead. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fcombine-stack-adjustments' Tracks stack adjustments (pushes and pops) and stack memory references and then tries to find ways to combine them. ! Enabled by default at `-O1' and higher. ! `-fipa-ra' ! Use caller save registers for allocation if those registers are ! not used by any called function. In that case it is not necessary ! to save and restore them around calls. This is only possible if called functions are part of same compilation unit as current function and they are compiled before it. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fconserve-stack' Attempt to minimize stack usage. The compiler attempts to use less stack space, even if that makes the program slower. This option ! implies setting the `large-stack-frame' parameter to 100 and the ! `large-stack-frame-growth' parameter to 400. ! `-ftree-reassoc' ! Perform reassociation on trees. This flag is enabled by default ! at `-O' and higher. ! `-ftree-pre' Perform partial redundancy elimination (PRE) on trees. This flag ! is enabled by default at `-O2' and `-O3'. ! `-ftree-partial-pre' Make partial redundancy elimination (PRE) more aggressive. This ! flag is enabled by default at `-O3'. ! `-ftree-forwprop' Perform forward propagation on trees. This flag is enabled by ! default at `-O' and higher. ! `-ftree-fre' Perform full redundancy elimination (FRE) on trees. The difference ! between FRE and PRE is that FRE only considers expressions that ! are computed on all paths leading to the redundant computation. ! This analysis is faster than PRE, though it exposes fewer ! redundancies. This flag is enabled by default at `-O' and higher. ! `-ftree-phiprop' Perform hoisting of loads from conditional pointers on trees. This ! pass is enabled by default at `-O' and higher. ! `-fhoist-adjacent-loads' Speculatively hoist loads from both branches of an if-then-else if ! the loads are from adjacent locations in the same structure and ! the target architecture has a conditional move instruction. This ! flag is enabled by default at `-O2' and higher. ! `-ftree-copy-prop' Perform copy propagation on trees. This pass eliminates unnecessary copy operations. This flag is enabled by default at ! `-O' and higher. ! `-fipa-pure-const' Discover which functions are pure or constant. Enabled by default ! at `-O' and higher. ! `-fipa-reference' Discover which static variables do not escape the compilation unit. ! Enabled by default at `-O' and higher. ! `-fipa-pta' Perform interprocedural pointer analysis and interprocedural modification and reference analysis. This option can cause ! excessive memory and compile-time usage on large compilation ! units. It is not enabled by default at any optimization level. ! `-fipa-profile' Perform interprocedural profile propagation. The functions called ! only from cold functions are marked as cold. Also functions ! executed once (such as `cold', `noreturn', static constructors or ! destructors) are identified. Cold functions and loop less parts of functions executed once are then optimized for size. Enabled by ! default at `-O' and higher. ! `-fipa-cp' Perform interprocedural constant propagation. This optimization analyzes the program to determine when values passed to functions are constants and then optimizes accordingly. This optimization can substantially increase performance if the application has constants passed to functions. This flag is enabled by default at ! `-O2', `-Os' and `-O3'. ! `-fipa-cp-clone' Perform function cloning to make interprocedural constant propagation stronger. When enabled, interprocedural constant propagation performs function cloning when externally visible function can be called with constant arguments. Because this optimization can create multiple copies of functions, it may ! significantly increase code size (see `--param ipcp-unit-growth=VALUE'). This flag is enabled by default at ! `-O3'. ! `-fipa-cp-alignment' When enabled, this optimization propagates alignment of function parameters to support better vectorization and string operations. ! This flag is enabled by default at `-O2' and `-Os'. It requires ! that `-fipa-cp' is enabled. ! `-fipa-icf' Perform Identical Code Folding for functions and read-only variables. The optimization reduces code size and may disturb unwind stacks by replacing a function by equivalent one with a ! different name. The optimization works more effectively with link time optimization enabled. Nevertheless the behavior is similar to Gold Linker ICF *************** optimizations to be performed is desired *** 6645,6789 **** optimizations are not same - there are equivalences that are found only by GCC and equivalences found only by Gold. ! This flag is enabled by default at '-O2' and '-Os'. ! '-fisolate-erroneous-paths-dereference' Detect paths that trigger erroneous or undefined behavior due to dereferencing a null pointer. Isolate those paths from the main control flow and turn the statement with erroneous or undefined ! behavior into a trap. This flag is enabled by default at '-O2' and ! higher and depends on '-fdelete-null-pointer-checks' also being ! enabled. ! '-fisolate-erroneous-paths-attribute' Detect paths that trigger erroneous or undefined behavior due a ! null value being used in a way forbidden by a 'returns_nonnull' or ! 'nonnull' attribute. Isolate those paths from the main control flow and turn the statement with erroneous or undefined behavior into a trap. This is not currently enabled, but may be enabled by ! '-O2' in the future. ! '-ftree-sink' Perform forward store motion on trees. This flag is enabled by ! default at '-O' and higher. ! '-ftree-bit-ccp' Perform sparse conditional bit constant propagation on trees and propagate pointer alignment information. This pass only operates ! on local scalar variables and is enabled by default at '-O' and ! higher. It requires that '-ftree-ccp' is enabled. ! '-ftree-ccp' Perform sparse conditional constant propagation (CCP) on trees. ! This pass only operates on local scalar variables and is enabled by ! default at '-O' and higher. ! '-fssa-backprop' Propagate information about uses of a value up the definition chain in order to simplify the definitions. For example, this pass strips sign operations if the sign of a value never matters. The ! flag is enabled by default at '-O' and higher. ! '-fssa-phiopt' Perform pattern matching on SSA PHI nodes to optimize conditional ! code. This pass is enabled by default at '-O' and higher. ! '-ftree-switch-conversion' Perform conversion of simple initializations in a switch to initializations from a scalar array. This flag is enabled by ! default at '-O2' and higher. ! '-ftree-tail-merge' Look for identical code sequences. When found, replace one with a jump to the other. This optimization is known as tail merging or ! cross jumping. This flag is enabled by default at '-O2' and higher. The compilation time in this pass can be limited using ! 'max-tail-merge-comparisons' parameter and ! 'max-tail-merge-iterations' parameter. ! '-ftree-dce' ! Perform dead code elimination (DCE) on trees. This flag is enabled ! by default at '-O' and higher. ! '-ftree-builtin-call-dce' Perform conditional dead code elimination (DCE) for calls to ! built-in functions that may set 'errno' but are otherwise ! side-effect free. This flag is enabled by default at '-O2' and ! higher if '-Os' is not also specified. ! '-ftree-dominator-opts' Perform a variety of simple scalar cleanups (constant/copy propagation, redundancy elimination, range propagation and expression simplification) based on a dominator tree traversal. ! This also performs jump threading (to reduce jumps to jumps). This ! flag is enabled by default at '-O' and higher. ! '-ftree-dse' Perform dead store elimination (DSE) on trees. A dead store is a store into a memory location that is later overwritten by another store without any intervening loads. In this case the earlier ! store can be deleted. This flag is enabled by default at '-O' and higher. ! '-ftree-ch' Perform loop header copying on trees. This is beneficial since it increases effectiveness of code motion optimizations. It also ! saves one jump. This flag is enabled by default at '-O' and ! higher. It is not enabled for '-Os', since it usually increases code size. ! '-ftree-loop-optimize' Perform loop optimizations on trees. This flag is enabled by ! default at '-O' and higher. ! '-ftree-loop-linear' ! '-floop-interchange' ! '-floop-strip-mine' ! '-floop-block' ! '-floop-unroll-and-jam' ! Perform loop nest optimizations. Same as '-floop-nest-optimize'. To use this code transformation, GCC has to be configured with ! '--with-isl' to enable the Graphite loop transformation infrastructure. ! '-fgraphite-identity' ! Enable the identity transformation for graphite. For every SCoP we ! generate the polyhedral representation and transform it back to ! gimple. Using '-fgraphite-identity' we can check the costs or benefits of the GIMPLE -> GRAPHITE -> GIMPLE transformation. Some ! minimal optimizations are also performed by the code generator isl, ! like index splitting and dead code elimination in loops. ! '-floop-nest-optimize' Enable the isl based loop nest optimizer. This is a generic loop nest optimizer based on the Pluto optimization algorithms. It calculates a loop structure optimized for data-locality and parallelism. This option is experimental. ! '-floop-parallelize-all' Use the Graphite data dependence analysis to identify loops that can be parallelized. Parallelize all the loops that can be analyzed to not contain loop carried dependences without checking that it is profitable to parallelize the loops. ! '-ftree-coalesce-vars' While transforming the program out of the SSA representation, attempt to reduce copying by coalescing versions of different ! user-defined variables, instead of just compiler temporaries. This ! may severely limit the ability to debug an optimized program ! compiled with '-fno-var-tracking-assignments'. In the negated form, this flag prevents SSA coalescing of user variables. This option is enabled by default if optimization is enabled, and it does very little otherwise. ! '-ftree-loop-if-convert' Attempt to transform conditional jumps in the innermost loops to branch-less equivalents. The intent is to remove control-flow from the innermost loops in order to improve the ability of the vectorization pass to handle these loops. This is enabled by default if vectorization is enabled. ! '-ftree-loop-if-convert-stores' Attempt to also if-convert conditional jumps containing memory writes. This transformation can be unsafe for multi-threaded programs as it transforms conditional memory writes into --- 6692,6836 ---- optimizations are not same - there are equivalences that are found only by GCC and equivalences found only by Gold. ! This flag is enabled by default at `-O2' and `-Os'. ! `-fisolate-erroneous-paths-dereference' Detect paths that trigger erroneous or undefined behavior due to dereferencing a null pointer. Isolate those paths from the main control flow and turn the statement with erroneous or undefined ! behavior into a trap. This flag is enabled by default at `-O2' ! and higher and depends on `-fdelete-null-pointer-checks' also ! being enabled. ! `-fisolate-erroneous-paths-attribute' Detect paths that trigger erroneous or undefined behavior due a ! null value being used in a way forbidden by a `returns_nonnull' or ! `nonnull' attribute. Isolate those paths from the main control flow and turn the statement with erroneous or undefined behavior into a trap. This is not currently enabled, but may be enabled by ! `-O2' in the future. ! `-ftree-sink' Perform forward store motion on trees. This flag is enabled by ! default at `-O' and higher. ! `-ftree-bit-ccp' Perform sparse conditional bit constant propagation on trees and propagate pointer alignment information. This pass only operates ! on local scalar variables and is enabled by default at `-O' and ! higher. It requires that `-ftree-ccp' is enabled. ! `-ftree-ccp' Perform sparse conditional constant propagation (CCP) on trees. ! This pass only operates on local scalar variables and is enabled ! by default at `-O' and higher. ! `-fssa-backprop' Propagate information about uses of a value up the definition chain in order to simplify the definitions. For example, this pass strips sign operations if the sign of a value never matters. The ! flag is enabled by default at `-O' and higher. ! `-fssa-phiopt' Perform pattern matching on SSA PHI nodes to optimize conditional ! code. This pass is enabled by default at `-O' and higher. ! `-ftree-switch-conversion' Perform conversion of simple initializations in a switch to initializations from a scalar array. This flag is enabled by ! default at `-O2' and higher. ! `-ftree-tail-merge' Look for identical code sequences. When found, replace one with a jump to the other. This optimization is known as tail merging or ! cross jumping. This flag is enabled by default at `-O2' and higher. The compilation time in this pass can be limited using ! `max-tail-merge-comparisons' parameter and ! `max-tail-merge-iterations' parameter. ! `-ftree-dce' ! Perform dead code elimination (DCE) on trees. This flag is ! enabled by default at `-O' and higher. ! `-ftree-builtin-call-dce' Perform conditional dead code elimination (DCE) for calls to ! built-in functions that may set `errno' but are otherwise ! side-effect free. This flag is enabled by default at `-O2' and ! higher if `-Os' is not also specified. ! `-ftree-dominator-opts' Perform a variety of simple scalar cleanups (constant/copy propagation, redundancy elimination, range propagation and expression simplification) based on a dominator tree traversal. ! This also performs jump threading (to reduce jumps to jumps). This ! flag is enabled by default at `-O' and higher. ! `-ftree-dse' Perform dead store elimination (DSE) on trees. A dead store is a store into a memory location that is later overwritten by another store without any intervening loads. In this case the earlier ! store can be deleted. This flag is enabled by default at `-O' and higher. ! `-ftree-ch' Perform loop header copying on trees. This is beneficial since it increases effectiveness of code motion optimizations. It also ! saves one jump. This flag is enabled by default at `-O' and ! higher. It is not enabled for `-Os', since it usually increases code size. ! `-ftree-loop-optimize' Perform loop optimizations on trees. This flag is enabled by ! default at `-O' and higher. ! `-ftree-loop-linear' ! `-floop-interchange' ! `-floop-strip-mine' ! `-floop-block' ! `-floop-unroll-and-jam' ! Perform loop nest optimizations. Same as `-floop-nest-optimize'. To use this code transformation, GCC has to be configured with ! `--with-isl' to enable the Graphite loop transformation infrastructure. ! `-fgraphite-identity' ! Enable the identity transformation for graphite. For every SCoP ! we generate the polyhedral representation and transform it back to ! gimple. Using `-fgraphite-identity' we can check the costs or benefits of the GIMPLE -> GRAPHITE -> GIMPLE transformation. Some ! minimal optimizations are also performed by the code generator ! isl, like index splitting and dead code elimination in loops. ! `-floop-nest-optimize' Enable the isl based loop nest optimizer. This is a generic loop nest optimizer based on the Pluto optimization algorithms. It calculates a loop structure optimized for data-locality and parallelism. This option is experimental. ! `-floop-parallelize-all' Use the Graphite data dependence analysis to identify loops that can be parallelized. Parallelize all the loops that can be analyzed to not contain loop carried dependences without checking that it is profitable to parallelize the loops. ! `-ftree-coalesce-vars' While transforming the program out of the SSA representation, attempt to reduce copying by coalescing versions of different ! user-defined variables, instead of just compiler temporaries. ! This may severely limit the ability to debug an optimized program ! compiled with `-fno-var-tracking-assignments'. In the negated form, this flag prevents SSA coalescing of user variables. This option is enabled by default if optimization is enabled, and it does very little otherwise. ! `-ftree-loop-if-convert' Attempt to transform conditional jumps in the innermost loops to branch-less equivalents. The intent is to remove control-flow from the innermost loops in order to improve the ability of the vectorization pass to handle these loops. This is enabled by default if vectorization is enabled. ! `-ftree-loop-if-convert-stores' Attempt to also if-convert conditional jumps containing memory writes. This transformation can be unsafe for multi-threaded programs as it transforms conditional memory writes into *************** optimizations to be performed is desired *** 6796,6806 **** A[i] = cond ? expr : A[i]; potentially producing data races. ! '-ftree-loop-distribution' ! Perform loop distribution. This flag can improve cache performance ! on big loop bodies and allow further loop optimizations, like ! parallelization or vectorization, to take place. For example, the ! loop DO I = 1, N A(I) = B(I) + C D(I) = E(I) * F --- 6843,6853 ---- A[i] = cond ? expr : A[i]; potentially producing data races. ! `-ftree-loop-distribution' ! Perform loop distribution. This flag can improve cache ! performance on big loop bodies and allow further loop ! optimizations, like parallelization or vectorization, to take ! place. For example, the loop DO I = 1, N A(I) = B(I) + C D(I) = E(I) * F *************** optimizations to be performed is desired *** 6813,6824 **** D(I) = E(I) * F ENDDO ! '-ftree-loop-distribute-patterns' Perform loop distribution of patterns that can be code generated ! with calls to a library. This flag is enabled by default at '-O3'. ! This pass distributes the initialization loops and generates a call ! to memset zero. For example, the loop DO I = 1, N A(I) = 0 B(I) = A(I) + I --- 6860,6871 ---- D(I) = E(I) * F ENDDO ! `-ftree-loop-distribute-patterns' Perform loop distribution of patterns that can be code generated ! with calls to a library. This flag is enabled by default at `-O3'. ! This pass distributes the initialization loops and generates a ! call to memset zero. For example, the loop DO I = 1, N A(I) = 0 B(I) = A(I) + I *************** optimizations to be performed is desired *** 6833,6973 **** and the initialization loop is transformed into a call to memset zero. ! '-ftree-loop-im' Perform loop invariant motion on trees. This pass moves only invariants that are hard to handle at RTL level (function calls, operations that expand to nontrivial sequences of insns). With ! '-funswitch-loops' it also moves operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion. ! '-ftree-loop-ivcanon' Create a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily. Useful especially in connection with unrolling. ! '-fivopts' Perform induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees. ! '-ftree-parallelize-loops=n' Parallelize loops, i.e., split their iteration space to run in n threads. This is only possible for loops whose iterations are independent and can be arbitrarily reordered. The optimization is only profitable on multiprocessor machines, for loops that are CPU-intensive, rather than constrained e.g. by memory bandwidth. ! This option implies '-pthread', and thus is only supported on ! targets that have support for '-pthread'. ! '-ftree-pta' Perform function-local points-to analysis on trees. This flag is ! enabled by default at '-O' and higher. ! '-ftree-sra' Perform scalar replacement of aggregates. This pass replaces structure references with scalars to prevent committing structures ! to memory too early. This flag is enabled by default at '-O' and higher. ! '-ftree-ter' Perform temporary expression replacement during the SSA->normal ! phase. Single use/single def temporaries are replaced at their use ! location with their defining expression. This results in ! non-GIMPLE code, but gives the expanders much more complex trees to ! work on resulting in better RTL generation. This is enabled by ! default at '-O' and higher. ! '-ftree-slsr' ! Perform straight-line strength reduction on trees. This recognizes ! related expressions involving multiplications and replaces them by ! less expensive calculations when possible. This is enabled by ! default at '-O' and higher. ! '-ftree-vectorize' ! Perform vectorization on trees. This flag enables ! '-ftree-loop-vectorize' and '-ftree-slp-vectorize' if not explicitly specified. ! '-ftree-loop-vectorize' ! Perform loop vectorization on trees. This flag is enabled by ! default at '-O3' and when '-ftree-vectorize' is enabled. ! '-ftree-slp-vectorize' ! Perform basic block vectorization on trees. This flag is enabled ! by default at '-O3' and when '-ftree-vectorize' is enabled. ! '-fvect-cost-model=MODEL' Alter the cost model used for vectorization. The MODEL argument ! should be one of 'unlimited', 'dynamic' or 'cheap'. With the ! 'unlimited' model the vectorized code-path is assumed to be ! profitable while with the 'dynamic' model a runtime check guards the vectorized code-path to enable it only for iteration counts that will likely execute faster than when executing the original ! scalar loop. The 'cheap' model disables vectorization of loops where doing so would be cost prohibitive for example due to required runtime checks for data dependence or alignment but ! otherwise is equal to the 'dynamic' model. The default cost model ! depends on other optimization flags and is either 'dynamic' or ! 'cheap'. ! '-fsimd-cost-model=MODEL' Alter the cost model used for vectorization of loops marked with the OpenMP or Cilk Plus simd directive. The MODEL argument should ! be one of 'unlimited', 'dynamic', 'cheap'. All values of MODEL ! have the same meaning as described in '-fvect-cost-model' and by ! default a cost model defined with '-fvect-cost-model' is used. ! '-ftree-vrp' Perform Value Range Propagation on trees. This is similar to the constant propagation pass, but instead of values, ranges of values are propagated. This allows the optimizers to remove unnecessary ! range checks like array bound checks and null pointer checks. This ! is enabled by default at '-O2' and higher. Null pointer check ! elimination is only done if '-fdelete-null-pointer-checks' is enabled. ! '-fsplit-paths' Split paths leading to loop backedges. This can improve dead code elimination and common subexpression elimination. This is enabled ! by default at '-O2' and above. ! '-fsplit-ivs-in-unroller' Enables expression of values of induction variables in later iterations of the unrolled loop using the value in the first iteration. This breaks long dependency chains, thus improving efficiency of the scheduling passes. ! A combination of '-fweb' and CSE is often sufficient to obtain the ! same effect. However, that is not reliable in cases where the loop ! body is more complicated than a single basic block. It also does ! not work at all on some architectures due to restrictions in the ! CSE pass. This optimization is enabled by default. ! '-fvariable-expansion-in-unroller' With this option, the compiler creates multiple copies of some ! local variables when unrolling a loop, which can result in superior ! code. ! '-fpartial-inlining' Inline parts of functions. This option has any effect only when ! inlining itself is turned on by the '-finline-functions' or ! '-finline-small-functions' options. ! Enabled at level '-O2'. ! '-fpredictive-commoning' Perform predictive commoning optimization, i.e., reusing computations (especially memory loads and stores) performed in previous iterations of loops. ! This option is enabled at level '-O3'. ! '-fprefetch-loop-arrays' If supported by the target machine, generate instructions to prefetch memory to improve the performance of loops that access large arrays. --- 6880,7020 ---- and the initialization loop is transformed into a call to memset zero. ! `-ftree-loop-im' Perform loop invariant motion on trees. This pass moves only invariants that are hard to handle at RTL level (function calls, operations that expand to nontrivial sequences of insns). With ! `-funswitch-loops' it also moves operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion. ! `-ftree-loop-ivcanon' Create a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily. Useful especially in connection with unrolling. ! `-fivopts' Perform induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees. ! `-ftree-parallelize-loops=n' Parallelize loops, i.e., split their iteration space to run in n threads. This is only possible for loops whose iterations are independent and can be arbitrarily reordered. The optimization is only profitable on multiprocessor machines, for loops that are CPU-intensive, rather than constrained e.g. by memory bandwidth. ! This option implies `-pthread', and thus is only supported on ! targets that have support for `-pthread'. ! `-ftree-pta' Perform function-local points-to analysis on trees. This flag is ! enabled by default at `-O' and higher. ! `-ftree-sra' Perform scalar replacement of aggregates. This pass replaces structure references with scalars to prevent committing structures ! to memory too early. This flag is enabled by default at `-O' and higher. ! `-ftree-ter' Perform temporary expression replacement during the SSA->normal ! phase. Single use/single def temporaries are replaced at their ! use location with their defining expression. This results in ! non-GIMPLE code, but gives the expanders much more complex trees ! to work on resulting in better RTL generation. This is enabled by ! default at `-O' and higher. ! `-ftree-slsr' ! Perform straight-line strength reduction on trees. This ! recognizes related expressions involving multiplications and ! replaces them by less expensive calculations when possible. This ! is enabled by default at `-O' and higher. ! `-ftree-vectorize' ! Perform vectorization on trees. This flag enables ! `-ftree-loop-vectorize' and `-ftree-slp-vectorize' if not explicitly specified. ! `-ftree-loop-vectorize' ! Perform loop vectorization on trees. This flag is enabled by ! default at `-O3' and when `-ftree-vectorize' is enabled. ! `-ftree-slp-vectorize' ! Perform basic block vectorization on trees. This flag is enabled ! by default at `-O3' and when `-ftree-vectorize' is enabled. ! `-fvect-cost-model=MODEL' Alter the cost model used for vectorization. The MODEL argument ! should be one of `unlimited', `dynamic' or `cheap'. With the ! `unlimited' model the vectorized code-path is assumed to be ! profitable while with the `dynamic' model a runtime check guards the vectorized code-path to enable it only for iteration counts that will likely execute faster than when executing the original ! scalar loop. The `cheap' model disables vectorization of loops where doing so would be cost prohibitive for example due to required runtime checks for data dependence or alignment but ! otherwise is equal to the `dynamic' model. The default cost model ! depends on other optimization flags and is either `dynamic' or ! `cheap'. ! `-fsimd-cost-model=MODEL' Alter the cost model used for vectorization of loops marked with the OpenMP or Cilk Plus simd directive. The MODEL argument should ! be one of `unlimited', `dynamic', `cheap'. All values of MODEL ! have the same meaning as described in `-fvect-cost-model' and by ! default a cost model defined with `-fvect-cost-model' is used. ! `-ftree-vrp' Perform Value Range Propagation on trees. This is similar to the constant propagation pass, but instead of values, ranges of values are propagated. This allows the optimizers to remove unnecessary ! range checks like array bound checks and null pointer checks. ! This is enabled by default at `-O2' and higher. Null pointer check ! elimination is only done if `-fdelete-null-pointer-checks' is enabled. ! `-fsplit-paths' Split paths leading to loop backedges. This can improve dead code elimination and common subexpression elimination. This is enabled ! by default at `-O2' and above. ! `-fsplit-ivs-in-unroller' Enables expression of values of induction variables in later iterations of the unrolled loop using the value in the first iteration. This breaks long dependency chains, thus improving efficiency of the scheduling passes. ! A combination of `-fweb' and CSE is often sufficient to obtain the ! same effect. However, that is not reliable in cases where the ! loop body is more complicated than a single basic block. It also ! does not work at all on some architectures due to restrictions in ! the CSE pass. This optimization is enabled by default. ! `-fvariable-expansion-in-unroller' With this option, the compiler creates multiple copies of some ! local variables when unrolling a loop, which can result in ! superior code. ! `-fpartial-inlining' Inline parts of functions. This option has any effect only when ! inlining itself is turned on by the `-finline-functions' or ! `-finline-small-functions' options. ! Enabled at level `-O2'. ! `-fpredictive-commoning' Perform predictive commoning optimization, i.e., reusing computations (especially memory loads and stores) performed in previous iterations of loops. ! This option is enabled at level `-O3'. ! `-fprefetch-loop-arrays' If supported by the target machine, generate instructions to prefetch memory to improve the performance of loops that access large arrays. *************** optimizations to be performed is desired *** 6975,7061 **** This option may generate better or worse code; results are highly dependent on the structure of loops within the source code. ! Disabled at level '-Os'. ! '-fno-peephole' ! '-fno-peephole2' Disable any machine-specific peephole optimizations. The ! difference between '-fno-peephole' and '-fno-peephole2' is in how they are implemented in the compiler; some targets use one, some use the other, a few use both. ! '-fpeephole' is enabled by default. '-fpeephole2' enabled at ! levels '-O2', '-O3', '-Os'. ! '-fno-guess-branch-probability' Do not guess branch probabilities using heuristics. GCC uses heuristics to guess branch probabilities if they are not ! provided by profiling feedback ('-fprofile-arcs'). These heuristics are based on the control flow graph. If some branch ! probabilities are specified by '__builtin_expect', then the heuristics are used to guess branch probabilities for the rest of ! the control flow graph, taking the '__builtin_expect' info into account. The interactions between the heuristics and ! '__builtin_expect' can be complex, and in some cases, it may be useful to disable the heuristics so that the effects of ! '__builtin_expect' are easier to understand. ! The default is '-fguess-branch-probability' at levels '-O', '-O2', ! '-O3', '-Os'. ! '-freorder-blocks' Reorder basic blocks in the compiled function in order to reduce number of taken branches and improve code locality. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-freorder-blocks-algorithm=ALGORITHM' Use the specified algorithm for basic block reordering. The ! ALGORITHM argument can be 'simple', which does not increase code ! size (except sometimes due to secondary effects like alignment), or ! 'stc', the "software trace cache" algorithm, which tries to put all ! often executed code together, minimizing the number of branches executed by making extra copies of code. ! The default is 'simple' at levels '-O', '-Os', and 'stc' at levels ! '-O2', '-O3'. ! '-freorder-blocks-and-partition' ! In addition to reordering basic blocks in the compiled function, in ! order to reduce number of taken branches, partitions hot and cold ! basic blocks into separate sections of the assembly and '.o' files, ! to improve paging and cache locality performance. This optimization is automatically turned off in the presence of exception handling, for linkonce sections, for functions with a user-defined section attribute and on any architecture that does not support named sections. ! Enabled for x86 at levels '-O2', '-O3'. ! '-freorder-functions' Reorder functions in the object file in order to improve code locality. This is implemented by using special subsections ! '.text.hot' for most frequently executed functions and ! '.text.unlikely' for unlikely executed functions. Reordering is done by the linker so object file format must support named sections and linker must place them in a reasonable way. Also profile feedback must be available to make this option ! effective. See '-fprofile-arcs' for details. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-fstrict-aliasing' Allow the compiler to assume the strictest aliasing rules applicable to the language being compiled. For C (and C++), this activates optimizations based on the type of expressions. In ! particular, an object of one type is assumed never to reside at the ! same address as an object of a different type, unless the types are ! almost the same. For example, an 'unsigned int' can alias an ! 'int', but not a 'void*' or a 'double'. A character type may alias ! any other type. Pay special attention to code like this: union a_union { --- 7022,7108 ---- This option may generate better or worse code; results are highly dependent on the structure of loops within the source code. ! Disabled at level `-Os'. ! `-fno-peephole' ! `-fno-peephole2' Disable any machine-specific peephole optimizations. The ! difference between `-fno-peephole' and `-fno-peephole2' is in how they are implemented in the compiler; some targets use one, some use the other, a few use both. ! `-fpeephole' is enabled by default. `-fpeephole2' enabled at ! levels `-O2', `-O3', `-Os'. ! `-fno-guess-branch-probability' Do not guess branch probabilities using heuristics. GCC uses heuristics to guess branch probabilities if they are not ! provided by profiling feedback (`-fprofile-arcs'). These heuristics are based on the control flow graph. If some branch ! probabilities are specified by `__builtin_expect', then the heuristics are used to guess branch probabilities for the rest of ! the control flow graph, taking the `__builtin_expect' info into account. The interactions between the heuristics and ! `__builtin_expect' can be complex, and in some cases, it may be useful to disable the heuristics so that the effects of ! `__builtin_expect' are easier to understand. ! The default is `-fguess-branch-probability' at levels `-O', `-O2', ! `-O3', `-Os'. ! `-freorder-blocks' Reorder basic blocks in the compiled function in order to reduce number of taken branches and improve code locality. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-freorder-blocks-algorithm=ALGORITHM' Use the specified algorithm for basic block reordering. The ! ALGORITHM argument can be `simple', which does not increase code ! size (except sometimes due to secondary effects like alignment), ! or `stc', the "software trace cache" algorithm, which tries to put ! all often executed code together, minimizing the number of branches executed by making extra copies of code. ! The default is `simple' at levels `-O', `-Os', and `stc' at levels ! `-O2', `-O3'. ! `-freorder-blocks-and-partition' ! In addition to reordering basic blocks in the compiled function, ! in order to reduce number of taken branches, partitions hot and ! cold basic blocks into separate sections of the assembly and `.o' ! files, to improve paging and cache locality performance. This optimization is automatically turned off in the presence of exception handling, for linkonce sections, for functions with a user-defined section attribute and on any architecture that does not support named sections. ! Enabled for x86 at levels `-O2', `-O3'. ! `-freorder-functions' Reorder functions in the object file in order to improve code locality. This is implemented by using special subsections ! `.text.hot' for most frequently executed functions and ! `.text.unlikely' for unlikely executed functions. Reordering is done by the linker so object file format must support named sections and linker must place them in a reasonable way. Also profile feedback must be available to make this option ! effective. See `-fprofile-arcs' for details. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-fstrict-aliasing' Allow the compiler to assume the strictest aliasing rules applicable to the language being compiled. For C (and C++), this activates optimizations based on the type of expressions. In ! particular, an object of one type is assumed never to reside at ! the same address as an object of a different type, unless the ! types are almost the same. For example, an `unsigned int' can ! alias an `int', but not a `void*' or a `double'. A character type ! may alias any other type. Pay special attention to code like this: union a_union { *************** optimizations to be performed is desired *** 7070,7076 **** } The practice of reading from a different union member than the one most recently written to (called "type-punning") is common. Even ! with '-fstrict-aliasing', type-punning is allowed, provided the memory is accessed through the union type. So, the code above works as expected. *Note Structures unions enumerations and bit-fields implementation::. However, this code might not: --- 7117,7123 ---- } The practice of reading from a different union member than the one most recently written to (called "type-punning") is common. Even ! with `-fstrict-aliasing', type-punning is allowed, provided the memory is accessed through the union type. So, the code above works as expected. *Note Structures unions enumerations and bit-fields implementation::. However, this code might not: *************** optimizations to be performed is desired *** 7090,7107 **** return ((union a_union *) &d)->i; } ! The '-fstrict-aliasing' option is enabled at levels '-O2', '-O3', ! '-Os'. ! '-fstrict-overflow' Allow the compiler to assume strict signed overflow rules, depending on the language being compiled. For C (and C++) this means that overflow when doing arithmetic with signed numbers is undefined, which means that the compiler may assume that it does not happen. This permits various optimizations. For example, the ! compiler assumes that an expression like 'i + 10 > i' is always ! true for signed 'i'. This assumption is only valid if signed ! overflow is undefined, as the expression is false if 'i + 10' overflows when using twos complement arithmetic. When this option is in effect any attempt to determine whether an operation on signed numbers overflows must be written carefully to not actually --- 7137,7154 ---- return ((union a_union *) &d)->i; } ! The `-fstrict-aliasing' option is enabled at levels `-O2', `-O3', ! `-Os'. ! `-fstrict-overflow' Allow the compiler to assume strict signed overflow rules, depending on the language being compiled. For C (and C++) this means that overflow when doing arithmetic with signed numbers is undefined, which means that the compiler may assume that it does not happen. This permits various optimizations. For example, the ! compiler assumes that an expression like `i + 10 > i' is always ! true for signed `i'. This assumption is only valid if signed ! overflow is undefined, as the expression is false if `i + 10' overflows when using twos complement arithmetic. When this option is in effect any attempt to determine whether an operation on signed numbers overflows must be written carefully to not actually *************** optimizations to be performed is desired *** 7111,7215 **** semantics: given a pointer to an object, if adding an offset to that pointer does not produce a pointer to the same object, the addition is undefined. This permits the compiler to conclude that ! 'p + u > p' is always true for a pointer 'p' and unsigned integer ! 'u'. This assumption is only valid because pointer wraparound is ! undefined, as the expression is false if 'p + u' overflows using twos complement arithmetic. ! See also the '-fwrapv' option. Using '-fwrapv' means that integer ! signed overflow is fully defined: it wraps. When '-fwrapv' is ! used, there is no difference between '-fstrict-overflow' and ! '-fno-strict-overflow' for integers. With '-fwrapv' certain types of overflow are permitted. For example, if the compiler gets an overflow when doing arithmetic on constants, the overflowed value ! can still be used with '-fwrapv', but not otherwise. ! The '-fstrict-overflow' option is enabled at levels '-O2', '-O3', ! '-Os'. ! '-falign-functions' ! '-falign-functions=N' Align the start of functions to the next power-of-two greater than ! N, skipping up to N bytes. For instance, '-falign-functions=32' aligns functions to the next 32-byte boundary, but ! '-falign-functions=24' aligns to the next 32-byte boundary only if this can be done by skipping 23 bytes or less. ! '-fno-align-functions' and '-falign-functions=1' are equivalent and ! mean that functions are not aligned. ! Some assemblers only support this flag when N is a power of two; in ! that case, it is rounded up. If N is not specified or is zero, use a machine-dependent default. ! Enabled at levels '-O2', '-O3'. ! '-falign-labels' ! '-falign-labels=N' Align all branch targets to a power-of-two boundary, skipping up to ! N bytes like '-falign-functions'. This option can easily make code ! slower, because it must insert dummy operations for when the branch ! target is reached in the usual flow of the code. ! '-fno-align-labels' and '-falign-labels=1' are equivalent and mean that labels are not aligned. ! If '-falign-loops' or '-falign-jumps' are applicable and are greater than this value, then their values are used instead. If N is not specified or is zero, use a machine-dependent default ! which is very likely to be '1', meaning no alignment. ! Enabled at levels '-O2', '-O3'. ! '-falign-loops' ! '-falign-loops=N' ! Align loops to a power-of-two boundary, skipping up to N bytes like ! '-falign-functions'. If the loops are executed many times, this ! makes up for any execution of the dummy operations. ! '-fno-align-loops' and '-falign-loops=1' are equivalent and mean that loops are not aligned. If N is not specified or is zero, use a machine-dependent default. ! Enabled at levels '-O2', '-O3'. ! '-falign-jumps' ! '-falign-jumps=N' Align branch targets to a power-of-two boundary, for branch targets where the targets can only be reached by jumping, skipping up to N ! bytes like '-falign-functions'. In this case, no dummy operations need be executed. ! '-fno-align-jumps' and '-falign-jumps=1' are equivalent and mean that loops are not aligned. If N is not specified or is zero, use a machine-dependent default. ! Enabled at levels '-O2', '-O3'. ! '-funit-at-a-time' ! This option is left for compatibility reasons. '-funit-at-a-time' ! has no effect, while '-fno-unit-at-a-time' implies ! '-fno-toplevel-reorder' and '-fno-section-anchors'. Enabled by default. ! '-fno-toplevel-reorder' ! Do not reorder top-level functions, variables, and 'asm' statements. Output them in the same order that they appear in the input file. When this option is used, unreferenced static variables are not removed. This option is intended to support existing code that relies on a particular ordering. For new code, it is better to use attributes when possible. ! Enabled at level '-O0'. When disabled explicitly, it also implies ! '-fno-section-anchors', which is otherwise enabled at '-O0' on some targets. ! '-fweb' Constructs webs as commonly used for register allocation purposes and assign each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also --- 7158,7262 ---- semantics: given a pointer to an object, if adding an offset to that pointer does not produce a pointer to the same object, the addition is undefined. This permits the compiler to conclude that ! `p + u > p' is always true for a pointer `p' and unsigned integer ! `u'. This assumption is only valid because pointer wraparound is ! undefined, as the expression is false if `p + u' overflows using twos complement arithmetic. ! See also the `-fwrapv' option. Using `-fwrapv' means that integer ! signed overflow is fully defined: it wraps. When `-fwrapv' is ! used, there is no difference between `-fstrict-overflow' and ! `-fno-strict-overflow' for integers. With `-fwrapv' certain types of overflow are permitted. For example, if the compiler gets an overflow when doing arithmetic on constants, the overflowed value ! can still be used with `-fwrapv', but not otherwise. ! The `-fstrict-overflow' option is enabled at levels `-O2', `-O3', ! `-Os'. ! `-falign-functions' ! `-falign-functions=N' Align the start of functions to the next power-of-two greater than ! N, skipping up to N bytes. For instance, `-falign-functions=32' aligns functions to the next 32-byte boundary, but ! `-falign-functions=24' aligns to the next 32-byte boundary only if this can be done by skipping 23 bytes or less. ! `-fno-align-functions' and `-falign-functions=1' are equivalent ! and mean that functions are not aligned. ! Some assemblers only support this flag when N is a power of two; ! in that case, it is rounded up. If N is not specified or is zero, use a machine-dependent default. ! Enabled at levels `-O2', `-O3'. ! `-falign-labels' ! `-falign-labels=N' Align all branch targets to a power-of-two boundary, skipping up to ! N bytes like `-falign-functions'. This option can easily make ! code slower, because it must insert dummy operations for when the ! branch target is reached in the usual flow of the code. ! `-fno-align-labels' and `-falign-labels=1' are equivalent and mean that labels are not aligned. ! If `-falign-loops' or `-falign-jumps' are applicable and are greater than this value, then their values are used instead. If N is not specified or is zero, use a machine-dependent default ! which is very likely to be `1', meaning no alignment. ! Enabled at levels `-O2', `-O3'. ! `-falign-loops' ! `-falign-loops=N' ! Align loops to a power-of-two boundary, skipping up to N bytes ! like `-falign-functions'. If the loops are executed many times, ! this makes up for any execution of the dummy operations. ! `-fno-align-loops' and `-falign-loops=1' are equivalent and mean that loops are not aligned. If N is not specified or is zero, use a machine-dependent default. ! Enabled at levels `-O2', `-O3'. ! `-falign-jumps' ! `-falign-jumps=N' Align branch targets to a power-of-two boundary, for branch targets where the targets can only be reached by jumping, skipping up to N ! bytes like `-falign-functions'. In this case, no dummy operations need be executed. ! `-fno-align-jumps' and `-falign-jumps=1' are equivalent and mean that loops are not aligned. If N is not specified or is zero, use a machine-dependent default. ! Enabled at levels `-O2', `-O3'. ! `-funit-at-a-time' ! This option is left for compatibility reasons. `-funit-at-a-time' ! has no effect, while `-fno-unit-at-a-time' implies ! `-fno-toplevel-reorder' and `-fno-section-anchors'. Enabled by default. ! `-fno-toplevel-reorder' ! Do not reorder top-level functions, variables, and `asm' statements. Output them in the same order that they appear in the input file. When this option is used, unreferenced static variables are not removed. This option is intended to support existing code that relies on a particular ordering. For new code, it is better to use attributes when possible. ! Enabled at level `-O0'. When disabled explicitly, it also implies ! `-fno-section-anchors', which is otherwise enabled at `-O0' on some targets. ! `-fweb' Constructs webs as commonly used for register allocation purposes and assign each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also *************** optimizations to be performed is desired *** 7218,7237 **** debugging impossible, since variables no longer stay in a "home register". ! Enabled by default with '-funroll-loops'. ! '-fwhole-program' Assume that the current compilation unit represents the whole program being compiled. All public functions and variables with ! the exception of 'main' and those merged by attribute ! 'externally_visible' become static functions and in effect are optimized more aggressively by interprocedural optimizers. ! This option should not be used in combination with '-flto'. Instead relying on a linker plugin should provide safer and more precise information. ! '-flto[=N]' This option runs the standard link-time optimizer. When invoked with source code, it generates GIMPLE (one of GCC's internal representations) and writes it to special ELF sections in the --- 7265,7284 ---- debugging impossible, since variables no longer stay in a "home register". ! Enabled by default with `-funroll-loops'. ! `-fwhole-program' Assume that the current compilation unit represents the whole program being compiled. All public functions and variables with ! the exception of `main' and those merged by attribute ! `externally_visible' become static functions and in effect are optimized more aggressively by interprocedural optimizers. ! This option should not be used in combination with `-flto'. Instead relying on a linker plugin should provide safer and more precise information. ! `-flto[=N]' This option runs the standard link-time optimizer. When invoked with source code, it generates GIMPLE (one of GCC's internal representations) and writes it to special ELF sections in the *************** optimizations to be performed is desired *** 7239,7245 **** function bodies are read from these ELF sections and instantiated as if they had been part of the same translation unit. ! To use the link-time optimizer, '-flto' and optimization options should be specified at compile time and during the final link. It is recommended that you compile all the files participating in the same link with the same options and also specify those options at --- 7286,7292 ---- function bodies are read from these ELF sections and instantiated as if they had been part of the same translation unit. ! To use the link-time optimizer, `-flto' and optimization options should be specified at compile time and during the final link. It is recommended that you compile all the files participating in the same link with the same options and also specify those options at *************** optimizations to be performed is desired *** 7250,7303 **** gcc -o myprog -flto -O2 foo.o bar.o The first two invocations to GCC save a bytecode representation of ! GIMPLE into special ELF sections inside 'foo.o' and 'bar.o'. The ! final invocation reads the GIMPLE bytecode from 'foo.o' and ! 'bar.o', merges the two files into a single internal image, and ! compiles the result as usual. Since both 'foo.o' and 'bar.o' are merged into a single image, this causes all the interprocedural analyses and optimizations in GCC to work across the two files as if they were a single one. This means, for example, that the ! inliner is able to inline functions in 'bar.o' into functions in ! 'foo.o' and vice-versa. Another (simpler) way to enable link-time optimization is: gcc -o myprog -flto -O2 foo.c bar.c ! The above generates bytecode for 'foo.c' and 'bar.c', merges them together into a single GIMPLE representation and optimizes them as ! usual to produce 'myprog'. The only important thing to keep in mind is that to enable link-time optimizations you need to use the GCC driver to perform the link step. GCC then automatically performs link-time optimization if any of the objects involved were compiled with the ! '-flto' command-line option. You generally should specify the optimization options to be used for link-time optimization though GCC tries to be clever at guessing an optimization level to use ! from the options used at compile time if you fail to specify one at ! link time. You can always override the automatic decision to do ! link-time optimization at link time by passing '-fno-lto' to the ! link command. To make whole program optimization effective, it is necessary to make certain whole program assumptions. The compiler needs to know what functions and variables can be accessed by libraries and ! runtime outside of the link-time optimized unit. When supported by ! the linker, the linker plugin (see '-fuse-linker-plugin') passes ! information to the compiler about used and externally visible ! symbols. When the linker plugin is not available, ! '-fwhole-program' should be used to allow the compiler to make these assumptions, which leads to more aggressive optimization decisions. ! When '-fuse-linker-plugin' is not enabled, when a file is compiled ! with '-flto', the generated object file is larger than a regular object file because it contains GIMPLE bytecodes and the usual ! final code (see '-ffat-lto-objects'. This means that object files with LTO information can be linked as normal object files; if ! '-fno-lto' is passed to the linker, no interprocedural ! optimizations are applied. Note that when '-fno-fat-lto-objects' is enabled the compile stage is faster but you cannot perform a regular, non-LTO link on them. --- 7297,7350 ---- gcc -o myprog -flto -O2 foo.o bar.o The first two invocations to GCC save a bytecode representation of ! GIMPLE into special ELF sections inside `foo.o' and `bar.o'. The ! final invocation reads the GIMPLE bytecode from `foo.o' and ! `bar.o', merges the two files into a single internal image, and ! compiles the result as usual. Since both `foo.o' and `bar.o' are merged into a single image, this causes all the interprocedural analyses and optimizations in GCC to work across the two files as if they were a single one. This means, for example, that the ! inliner is able to inline functions in `bar.o' into functions in ! `foo.o' and vice-versa. Another (simpler) way to enable link-time optimization is: gcc -o myprog -flto -O2 foo.c bar.c ! The above generates bytecode for `foo.c' and `bar.c', merges them together into a single GIMPLE representation and optimizes them as ! usual to produce `myprog'. The only important thing to keep in mind is that to enable link-time optimizations you need to use the GCC driver to perform the link step. GCC then automatically performs link-time optimization if any of the objects involved were compiled with the ! `-flto' command-line option. You generally should specify the optimization options to be used for link-time optimization though GCC tries to be clever at guessing an optimization level to use ! from the options used at compile time if you fail to specify one ! at link time. You can always override the automatic decision to ! do link-time optimization at link time by passing `-fno-lto' to ! the link command. To make whole program optimization effective, it is necessary to make certain whole program assumptions. The compiler needs to know what functions and variables can be accessed by libraries and ! runtime outside of the link-time optimized unit. When supported ! by the linker, the linker plugin (see `-fuse-linker-plugin') ! passes information to the compiler about used and externally ! visible symbols. When the linker plugin is not available, ! `-fwhole-program' should be used to allow the compiler to make these assumptions, which leads to more aggressive optimization decisions. ! When `-fuse-linker-plugin' is not enabled, when a file is compiled ! with `-flto', the generated object file is larger than a regular object file because it contains GIMPLE bytecodes and the usual ! final code (see `-ffat-lto-objects'. This means that object files with LTO information can be linked as normal object files; if ! `-fno-lto' is passed to the linker, no interprocedural ! optimizations are applied. Note that when `-fno-fat-lto-objects' is enabled the compile stage is faster but you cannot perform a regular, non-LTO link on them. *************** optimizations to be performed is desired *** 7310,7352 **** gcc -o myprog -O3 foo.o bar.o This produces individual object files with unoptimized assembler ! code, but the resulting binary 'myprog' is optimized at '-O3'. If, ! instead, the final binary is generated with '-fno-lto', then ! 'myprog' is not optimized. When producing the final binary, GCC only applies link-time ! optimizations to those files that contain bytecode. Therefore, you ! can mix and match object files and libraries with GIMPLE bytecodes ! and final object code. GCC automatically selects which files to ! optimize in LTO mode and which files to link without further ! processing. There are some code generation flags preserved by GCC when generating bytecodes, as they need to be used during the final link stage. Generally options specified at link time override those specified at compile time. ! If you do not specify an optimization level option '-O' at link time, then GCC uses the highest optimization level used when compiling the object files. Currently, the following options and their settings are taken from ! the first object file that explicitly specifies them: '-fPIC', ! '-fpic', '-fpie', '-fcommon', '-fexceptions', ! '-fnon-call-exceptions', '-fgnu-tm' and all the '-m' target flags. ! Certain ABI-changing flags are required to match in all compilation ! units, and trying to override this at link time with a conflicting ! value is ignored. This includes options such as ! '-freg-struct-return' and '-fpcc-struct-return'. ! Other options such as '-ffp-contract', '-fno-strict-overflow', ! '-fwrapv', '-fno-trapv' or '-fno-strict-aliasing' are passed ! through to the link stage and merged conservatively for conflicting ! translation units. Specifically '-fno-strict-overflow', '-fwrapv' ! and '-fno-trapv' take precedence; and for example ! '-ffp-contract=off' takes precedence over '-ffp-contract=fast'. ! You can override them at link time. If LTO encounters objects with C linkage declared with incompatible types in separate translation units to be linked together --- 7357,7399 ---- gcc -o myprog -O3 foo.o bar.o This produces individual object files with unoptimized assembler ! code, but the resulting binary `myprog' is optimized at `-O3'. ! If, instead, the final binary is generated with `-fno-lto', then ! `myprog' is not optimized. When producing the final binary, GCC only applies link-time ! optimizations to those files that contain bytecode. Therefore, ! you can mix and match object files and libraries with GIMPLE ! bytecodes and final object code. GCC automatically selects which ! files to optimize in LTO mode and which files to link without ! further processing. There are some code generation flags preserved by GCC when generating bytecodes, as they need to be used during the final link stage. Generally options specified at link time override those specified at compile time. ! If you do not specify an optimization level option `-O' at link time, then GCC uses the highest optimization level used when compiling the object files. Currently, the following options and their settings are taken from ! the first object file that explicitly specifies them: `-fPIC', ! `-fpic', `-fpie', `-fcommon', `-fexceptions', ! `-fnon-call-exceptions', `-fgnu-tm' and all the `-m' target flags. ! Certain ABI-changing flags are required to match in all ! compilation units, and trying to override this at link time with a ! conflicting value is ignored. This includes options such as ! `-freg-struct-return' and `-fpcc-struct-return'. ! Other options such as `-ffp-contract', `-fno-strict-overflow', ! `-fwrapv', `-fno-trapv' or `-fno-strict-aliasing' are passed ! through to the link stage and merged conservatively for ! conflicting translation units. Specifically ! `-fno-strict-overflow', `-fwrapv' and `-fno-trapv' take ! precedence; and for example `-ffp-contract=off' takes precedence ! over `-ffp-contract=fast'. You can override them at link time. If LTO encounters objects with C linkage declared with incompatible types in separate translation units to be linked together *************** optimizations to be performed is desired *** 7363,7405 **** gfortran -c -flto baz.f90 g++ -o myprog -flto -O3 foo.o bar.o baz.o -lgfortran ! Notice that the final link is done with 'g++' to get the C++ ! runtime libraries and '-lgfortran' is added to get the Fortran runtime libraries. In general, when mixing languages in LTO mode, you should use the same link command options as when mixing languages in a regular (non-LTO) compilation. If object files containing GIMPLE bytecode are stored in a library ! archive, say 'libfoo.a', it is possible to extract and use them in an LTO link if you are using a linker with plugin support. To ! create static libraries suitable for LTO, use 'gcc-ar' and ! 'gcc-ranlib' instead of 'ar' and 'ranlib'; to show the symbols of ! object files with GIMPLE bytecode, use 'gcc-nm'. Those commands ! require that 'ar', 'ranlib' and 'nm' have been compiled with plugin ! support. At link time, use the the flag '-fuse-linker-plugin' to ! ensure that the library participates in the LTO optimization ! process: gcc -o myprog -O2 -flto -fuse-linker-plugin a.o b.o -lfoo With the linker plugin enabled, the linker extracts the needed ! GIMPLE files from 'libfoo.a' and passes them on to the running GCC to make them part of the aggregated GIMPLE image to be optimized. If you are not using a linker with plugin support and/or do not ! enable the linker plugin, then the objects inside 'libfoo.a' are extracted and linked as usual, but they do not participate in the LTO optimization process. In order to make a static library suitable for both LTO optimization and usual linkage, compile its ! object files with '-flto' '-ffat-lto-objects'. Link-time optimizations do not require the presence of the whole ! program to operate. If the program does not require any symbols to ! be exported, it is possible to combine '-flto' and ! '-fwhole-program' to allow the interprocedural optimizers to use ! more aggressive assumptions which may lead to improved optimization ! opportunities. Use of '-fwhole-program' is not needed when linker ! plugin is active (see '-fuse-linker-plugin'). The current implementation of LTO makes no attempt to generate bytecode that is portable between different types of hosts. The --- 7410,7452 ---- gfortran -c -flto baz.f90 g++ -o myprog -flto -O3 foo.o bar.o baz.o -lgfortran ! Notice that the final link is done with `g++' to get the C++ ! runtime libraries and `-lgfortran' is added to get the Fortran runtime libraries. In general, when mixing languages in LTO mode, you should use the same link command options as when mixing languages in a regular (non-LTO) compilation. If object files containing GIMPLE bytecode are stored in a library ! archive, say `libfoo.a', it is possible to extract and use them in an LTO link if you are using a linker with plugin support. To ! create static libraries suitable for LTO, use `gcc-ar' and ! `gcc-ranlib' instead of `ar' and `ranlib'; to show the symbols of ! object files with GIMPLE bytecode, use `gcc-nm'. Those commands ! require that `ar', `ranlib' and `nm' have been compiled with ! plugin support. At link time, use the the flag ! `-fuse-linker-plugin' to ensure that the library participates in ! the LTO optimization process: gcc -o myprog -O2 -flto -fuse-linker-plugin a.o b.o -lfoo With the linker plugin enabled, the linker extracts the needed ! GIMPLE files from `libfoo.a' and passes them on to the running GCC to make them part of the aggregated GIMPLE image to be optimized. If you are not using a linker with plugin support and/or do not ! enable the linker plugin, then the objects inside `libfoo.a' are extracted and linked as usual, but they do not participate in the LTO optimization process. In order to make a static library suitable for both LTO optimization and usual linkage, compile its ! object files with `-flto' `-ffat-lto-objects'. Link-time optimizations do not require the presence of the whole ! program to operate. If the program does not require any symbols ! to be exported, it is possible to combine `-flto' and ! `-fwhole-program' to allow the interprocedural optimizers to use ! more aggressive assumptions which may lead to improved ! optimization opportunities. Use of `-fwhole-program' is not ! needed when linker plugin is active (see `-fuse-linker-plugin'). The current implementation of LTO makes no attempt to generate bytecode that is portable between different types of hosts. The *************** optimizations to be performed is desired *** 7408,7492 **** an older or newer version of GCC. Link-time optimization does not work well with generation of ! debugging information. Combining '-flto' with '-g' is currently experimental and expected to produce unexpected results. ! If you specify the optional N, the optimization and code generation ! done at link time is executed in parallel using N parallel jobs by ! utilizing an installed 'make' program. The environment variable ! 'MAKE' may be used to override the program used. The default value ! for N is 1. ! You can also specify '-flto=jobserver' to use GNU make's job server ! mode to determine the number of parallel jobs. This is useful when ! the Makefile calling GCC is already executing in parallel. You ! must prepend a '+' to the command recipe in the parent Makefile for ! this to work. This option likely only works if 'MAKE' is GNU make. ! '-flto-partition=ALG' Specify the partitioning algorithm used by the link-time optimizer. ! The value is either '1to1' to specify a partitioning mirroring the ! original source files or 'balanced' to specify partitioning into ! equally sized chunks (whenever possible) or 'max' to create new ! partition for every symbol where possible. Specifying 'none' as an ! algorithm disables partitioning and streaming completely. The ! default value is 'balanced'. While '1to1' can be used as an ! workaround for various code ordering issues, the 'max' partitioning ! is intended for internal testing only. The value 'one' specifies ! that exactly one partition should be used while the value 'none' ! bypasses partitioning and executes the link-time optimization step ! directly from the WPA phase. ! '-flto-odr-type-merging' Enable streaming of mangled types names of C++ types and their ! unification at link time. This increases size of LTO object files, ! but enables diagnostics about One Definition Rule violations. ! '-flto-compression-level=N' This option specifies the level of compression used for intermediate language written to LTO object files, and is only ! meaningful in conjunction with LTO mode ('-flto'). Valid values are 0 (no compression) to 9 (maximum compression). Values outside this range are clamped to either 0 or 9. If the option is not given, a default balanced compression setting is used. ! '-fuse-linker-plugin' Enables the use of a linker plugin during link-time optimization. This option relies on plugin support in the linker, which is available in gold or in GNU ld 2.21 or newer. This option enables the extraction of object files with GIMPLE ! bytecode out of library archives. This improves the quality of optimization by exposing more code to the link-time optimizer. This information specifies what symbols can be accessed externally (by non-LTO object or during dynamic linking). Resulting code quality improvements on binaries (and shared libraries that use ! hidden visibility) are similar to '-fwhole-program'. See '-flto' for a description of the effect of this flag and how to use it. This option is enabled by default when LTO support in GCC is enabled and GCC was configured for use with a linker supporting plugins (GNU ld 2.21 or newer or gold). ! '-ffat-lto-objects' ! Fat LTO objects are object files that contain both the intermediate ! language and the object code. This makes them usable for both LTO ! linking and normal linking. This option is effective only when ! compiling with '-flto' and is ignored at link time. ! '-fno-fat-lto-objects' improves compilation time over plain LTO, ! but requires the complete toolchain to be aware of LTO. It requires ! a linker with linker plugin support for basic functionality. ! Additionally, 'nm', 'ar' and 'ranlib' need to support linker ! plugins to allow a full-featured build environment (capable of ! building static libraries etc). GCC provides the 'gcc-ar', ! 'gcc-nm', 'gcc-ranlib' wrappers to pass the right options to these ! tools. With non fat LTO makefiles need to be modified to use them. ! The default is '-fno-fat-lto-objects' on targets with linker plugin support. ! '-fcompare-elim' After register allocation and post-register allocation instruction splitting, identify arithmetic instructions that compute processor flags similar to a comparison operation based on that arithmetic. --- 7455,7542 ---- an older or newer version of GCC. Link-time optimization does not work well with generation of ! debugging information. Combining `-flto' with `-g' is currently experimental and expected to produce unexpected results. ! If you specify the optional N, the optimization and code ! generation done at link time is executed in parallel using N ! parallel jobs by utilizing an installed `make' program. The ! environment variable `MAKE' may be used to override the program ! used. The default value for N is 1. ! You can also specify `-flto=jobserver' to use GNU make's job ! server mode to determine the number of parallel jobs. This is ! useful when the Makefile calling GCC is already executing in ! parallel. You must prepend a `+' to the command recipe in the ! parent Makefile for this to work. This option likely only works ! if `MAKE' is GNU make. ! `-flto-partition=ALG' Specify the partitioning algorithm used by the link-time optimizer. ! The value is either `1to1' to specify a partitioning mirroring the ! original source files or `balanced' to specify partitioning into ! equally sized chunks (whenever possible) or `max' to create new ! partition for every symbol where possible. Specifying `none' as ! an algorithm disables partitioning and streaming completely. The ! default value is `balanced'. While `1to1' can be used as an ! workaround for various code ordering issues, the `max' ! partitioning is intended for internal testing only. The value ! `one' specifies that exactly one partition should be used while ! the value `none' bypasses partitioning and executes the link-time ! optimization step directly from the WPA phase. ! `-flto-odr-type-merging' Enable streaming of mangled types names of C++ types and their ! unification at link time. This increases size of LTO object ! files, but enables diagnostics about One Definition Rule ! violations. ! `-flto-compression-level=N' This option specifies the level of compression used for intermediate language written to LTO object files, and is only ! meaningful in conjunction with LTO mode (`-flto'). Valid values are 0 (no compression) to 9 (maximum compression). Values outside this range are clamped to either 0 or 9. If the option is not given, a default balanced compression setting is used. ! `-fuse-linker-plugin' Enables the use of a linker plugin during link-time optimization. This option relies on plugin support in the linker, which is available in gold or in GNU ld 2.21 or newer. This option enables the extraction of object files with GIMPLE ! bytecode out of library archives. This improves the quality of optimization by exposing more code to the link-time optimizer. This information specifies what symbols can be accessed externally (by non-LTO object or during dynamic linking). Resulting code quality improvements on binaries (and shared libraries that use ! hidden visibility) are similar to `-fwhole-program'. See `-flto' for a description of the effect of this flag and how to use it. This option is enabled by default when LTO support in GCC is enabled and GCC was configured for use with a linker supporting plugins (GNU ld 2.21 or newer or gold). ! `-ffat-lto-objects' ! Fat LTO objects are object files that contain both the ! intermediate language and the object code. This makes them usable ! for both LTO linking and normal linking. This option is effective ! only when compiling with `-flto' and is ignored at link time. ! `-fno-fat-lto-objects' improves compilation time over plain LTO, ! but requires the complete toolchain to be aware of LTO. It ! requires a linker with linker plugin support for basic ! functionality. Additionally, `nm', `ar' and `ranlib' need to ! support linker plugins to allow a full-featured build environment ! (capable of building static libraries etc). GCC provides the ! `gcc-ar', `gcc-nm', `gcc-ranlib' wrappers to pass the right options ! to these tools. With non fat LTO makefiles need to be modified to ! use them. ! The default is `-fno-fat-lto-objects' on targets with linker plugin support. ! `-fcompare-elim' After register allocation and post-register allocation instruction splitting, identify arithmetic instructions that compute processor flags similar to a comparison operation based on that arithmetic. *************** optimizations to be performed is desired *** 7496,7562 **** represent the comparison operation before register allocation is complete. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fcprop-registers' After register allocation and post-register allocation instruction splitting, perform a copy-propagation pass to try to reduce scheduling dependencies and occasionally eliminate the copy. ! Enabled at levels '-O', '-O2', '-O3', '-Os'. ! '-fprofile-correction' Profiles collected using an instrumented binary for multi-threaded ! programs may be inconsistent due to missed counter updates. When this option is specified, GCC uses heuristics to correct or smooth ! out such inconsistencies. By default, GCC emits an error message when an inconsistent profile is detected. ! '-fprofile-use' ! '-fprofile-use=PATH' Enable profile feedback-directed optimizations, and the following optimizations which are generally profitable only with profile ! feedback available: '-fbranch-probabilities', '-fvpt', ! '-funroll-loops', '-fpeel-loops', '-ftracer', '-ftree-vectorize', ! and 'ftree-loop-distribute-patterns'. Before you can use this option, you must first generate profiling information. *Note Optimize Options::, for information about the ! '-fprofile-generate' option. By default, GCC emits an error message if the feedback profiles do ! not match the source code. This error can be turned into a warning ! by using '-Wcoverage-mismatch'. Note this may result in poorly ! optimized code. If PATH is specified, GCC looks at the PATH to find the profile ! feedback data files. See '-fprofile-dir'. ! '-fauto-profile' ! '-fauto-profile=PATH' Enable sampling-based feedback-directed optimizations, and the following optimizations which are generally profitable only with ! profile feedback available: '-fbranch-probabilities', '-fvpt', ! '-funroll-loops', '-fpeel-loops', '-ftracer', '-ftree-vectorize', ! '-finline-functions', '-fipa-cp', '-fipa-cp-clone', ! '-fpredictive-commoning', '-funswitch-loops', ! '-fgcse-after-reload', and '-ftree-loop-distribute-patterns'. PATH is the name of a file containing AutoFDO profile information. ! If omitted, it defaults to 'fbdata.afdo' in the current directory. Producing an AutoFDO profile data file requires running your ! program with the 'perf' utility on a supported GNU/Linux target ! system. For more information, see . E.g. perf record -e br_inst_retired:near_taken -b -o perf.data \ -- your_program ! Then use the 'create_gcov' tool to convert the raw profile data to a format that can be used by GCC. You must also supply the unstripped binary for your program to this tool. See ! . E.g. create_gcov --binary=your_program.unstripped --profile=perf.data \ --- 7546,7612 ---- represent the comparison operation before register allocation is complete. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fcprop-registers' After register allocation and post-register allocation instruction splitting, perform a copy-propagation pass to try to reduce scheduling dependencies and occasionally eliminate the copy. ! Enabled at levels `-O', `-O2', `-O3', `-Os'. ! `-fprofile-correction' Profiles collected using an instrumented binary for multi-threaded ! programs may be inconsistent due to missed counter updates. When this option is specified, GCC uses heuristics to correct or smooth ! out such inconsistencies. By default, GCC emits an error message when an inconsistent profile is detected. ! `-fprofile-use' ! `-fprofile-use=PATH' Enable profile feedback-directed optimizations, and the following optimizations which are generally profitable only with profile ! feedback available: `-fbranch-probabilities', `-fvpt', ! `-funroll-loops', `-fpeel-loops', `-ftracer', `-ftree-vectorize', ! and `ftree-loop-distribute-patterns'. Before you can use this option, you must first generate profiling information. *Note Optimize Options::, for information about the ! `-fprofile-generate' option. By default, GCC emits an error message if the feedback profiles do ! not match the source code. This error can be turned into a ! warning by using `-Wcoverage-mismatch'. Note this may result in ! poorly optimized code. If PATH is specified, GCC looks at the PATH to find the profile ! feedback data files. See `-fprofile-dir'. ! `-fauto-profile' ! `-fauto-profile=PATH' Enable sampling-based feedback-directed optimizations, and the following optimizations which are generally profitable only with ! profile feedback available: `-fbranch-probabilities', `-fvpt', ! `-funroll-loops', `-fpeel-loops', `-ftracer', `-ftree-vectorize', ! `-finline-functions', `-fipa-cp', `-fipa-cp-clone', ! `-fpredictive-commoning', `-funswitch-loops', ! `-fgcse-after-reload', and `-ftree-loop-distribute-patterns'. PATH is the name of a file containing AutoFDO profile information. ! If omitted, it defaults to `fbdata.afdo' in the current directory. Producing an AutoFDO profile data file requires running your ! program with the `perf' utility on a supported GNU/Linux target ! system. For more information, see `https://perf.wiki.kernel.org/'. E.g. perf record -e br_inst_retired:near_taken -b -o perf.data \ -- your_program ! Then use the `create_gcov' tool to convert the raw profile data to a format that can be used by GCC. You must also supply the unstripped binary for your program to this tool. See ! `https://github.com/google/autofdo'. E.g. create_gcov --binary=your_program.unstripped --profile=perf.data \ *************** optimizations to be performed is desired *** 7566,7831 **** floating-point arithmetic. These options trade off between speed and correctness. All must be specifically enabled. ! '-ffloat-store' Do not store floating-point variables in registers, and inhibit other options that might change whether a floating-point value is taken from a register or memory. This option prevents undesirable excess precision on machines such as the 68000 where the floating registers (of the 68881) keep more ! precision than a 'double' is supposed to have. Similarly for the x86 architecture. For most programs, the excess precision does only good, but a few programs rely on the precise definition of ! IEEE floating point. Use '-ffloat-store' for such programs, after modifying them to store all pertinent intermediate computations into variables. ! '-fexcess-precision=STYLE' This option allows further control over excess precision on machines where floating-point registers have more precision than ! the IEEE 'float' and 'double' types and the processor does not support operations rounding to those types. By default, ! '-fexcess-precision=fast' is in effect; this means that operations are carried out in the precision of the registers and that it is unpredictable when rounding to the types specified in the source code takes place. When compiling C, if ! '-fexcess-precision=standard' is specified then excess precision follows the rules specified in ISO C99; in particular, both casts and assignments cause values to be rounded to their semantic types ! (whereas '-ffloat-store' only affects assignments). This option is ! enabled by default for C if a strict conformance option such as ! '-std=c99' is used. ! '-fexcess-precision=standard' is not implemented for languages ! other than C, and has no effect if '-funsafe-math-optimizations' or ! '-ffast-math' is specified. On the x86, it also has no effect if ! '-mfpmath=sse' or '-mfpmath=sse+387' is specified; in the former ! case, IEEE semantics apply without excess precision, and in the ! latter, rounding is unpredictable. ! '-ffast-math' ! Sets the options '-fno-math-errno', '-funsafe-math-optimizations', ! '-ffinite-math-only', '-fno-rounding-math', '-fno-signaling-nans' ! and '-fcx-limited-range'. ! This option causes the preprocessor macro '__FAST_MATH__' to be defined. ! This option is not turned on by any '-O' option besides '-Ofast' ! since it can result in incorrect output for programs that depend on ! an exact implementation of IEEE or ISO rules/specifications for ! math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. ! '-fno-math-errno' ! Do not set 'errno' after calling math functions that are executed ! with a single instruction, e.g., 'sqrt'. A program that relies on IEEE exceptions for math error handling may want to use this flag for speed while maintaining IEEE arithmetic compatibility. ! This option is not turned on by any '-O' option since it can result ! in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math ! functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. ! The default is '-fmath-errno'. ! On Darwin systems, the math library never sets 'errno'. There is therefore no reason for the compiler to consider the possibility ! that it might, and '-fno-math-errno' is the default. ! ! '-funsafe-math-optimizations' Allow optimizations for floating-point arithmetic that (a) assume that arguments and results are valid and (b) may violate IEEE or ANSI standards. When used at link time, it may include libraries or startup files that change the default FPU control word or other similar optimizations. ! This option is not turned on by any '-O' option since it can result ! in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math ! functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. Enables ! '-fno-signed-zeros', '-fno-trapping-math', '-fassociative-math' and ! '-freciprocal-math'. ! ! The default is '-fno-unsafe-math-optimizations'. ! '-fassociative-math' Allow re-association of operands in series of floating-point operations. This violates the ISO C and C++ language standard by ! possibly changing computation result. NOTE: re-ordering may change ! the sign of zero as well as ignore NaNs and inhibit or create ! underflow or overflow (and thus cannot be used on code that relies ! on rounding behavior like '(x + 2**52) - 2**52'. May also reorder ! floating-point comparisons and thus may not be used when ordered ! comparisons are required. This option requires that both ! '-fno-signed-zeros' and '-fno-trapping-math' be in effect. ! Moreover, it doesn't make much sense with '-frounding-math'. For Fortran the option is automatically enabled when both ! '-fno-signed-zeros' and '-fno-trapping-math' are in effect. ! ! The default is '-fno-associative-math'. ! '-freciprocal-math' Allow the reciprocal of a value to be used instead of dividing by ! the value if this enables optimizations. For example 'x / y' can ! be replaced with 'x * (1/y)', which is useful if '(1/y)' is subject ! to common subexpression elimination. Note that this loses precision and increases the number of flops operating on the value. ! The default is '-fno-reciprocal-math'. ! '-ffinite-math-only' Allow optimizations for floating-point arithmetic that assume that arguments and results are not NaNs or +-Infs. ! This option is not turned on by any '-O' option since it can result ! in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math ! functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. ! The default is '-fno-finite-math-only'. ! '-fno-signed-zeros' Allow optimizations for floating-point arithmetic that ignore the signedness of zero. IEEE arithmetic specifies the behavior of distinct +0.0 and -0.0 values, which then prohibits simplification of expressions such as x+0.0 or 0.0*x (even with ! '-ffinite-math-only'). This option implies that the sign of a zero ! result isn't significant. ! The default is '-fsigned-zeros'. ! '-fno-trapping-math' Compile code assuming that floating-point operations cannot ! generate user-visible traps. These traps include division by zero, ! overflow, underflow, inexact result and invalid operation. This ! option requires that '-fno-signaling-nans' be in effect. Setting ! this option may allow faster code if one relies on "non-stop" IEEE ! arithmetic, for example. ! This option should never be turned on by any '-O' option since it ! can result in incorrect output for programs that depend on an exact ! implementation of IEEE or ISO rules/specifications for math functions. ! The default is '-ftrapping-math'. ! '-frounding-math' Disable transformations and optimizations that assume default floating-point rounding behavior. This is round-to-zero for all ! floating point to integer conversions, and round-to-nearest for all ! other arithmetic truncations. This option should be specified for ! programs that change the FP rounding mode dynamically, or that may ! be executed with a non-default rounding mode. This option disables ! constant folding of floating-point expressions at compile time ! (which may be affected by rounding mode) and arithmetic transformations that are unsafe in the presence of sign-dependent rounding modes. ! The default is '-fno-rounding-math'. This option is experimental and does not currently guarantee to disable all GCC optimizations that are affected by rounding mode. Future versions of GCC may provide finer control of this setting ! using C99's 'FENV_ACCESS' pragma. This command-line option will be ! used to specify the default state for 'FENV_ACCESS'. ! '-fsignaling-nans' Compile code assuming that IEEE signaling NaNs may generate user-visible traps during floating-point operations. Setting this option disables optimizations that may change the number of exceptions visible with signaling NaNs. This option implies ! '-ftrapping-math'. ! This option causes the preprocessor macro '__SUPPORT_SNAN__' to be defined. ! The default is '-fno-signaling-nans'. This option is experimental and does not currently guarantee to disable all GCC optimizations that affect signaling NaN behavior. ! '-fsingle-precision-constant' Treat floating-point constants as single precision instead of implicitly converting them to double-precision constants. ! '-fcx-limited-range' When enabled, this option states that a range reduction step is not needed when performing complex division. Also, there is no ! checking whether the result of a complex multiplication or division ! is 'NaN + I*NaN', with an attempt to rescue the situation in that ! case. The default is '-fno-cx-limited-range', but is enabled by ! '-ffast-math'. This option controls the default setting of the ISO C99 ! 'CX_LIMITED_RANGE' pragma. Nevertheless, the option applies to all ! languages. ! '-fcx-fortran-rules' Complex multiplication and division follow Fortran rules. Range reduction is done as part of complex division, but there is no ! checking whether the result of a complex multiplication or division ! is 'NaN + I*NaN', with an attempt to rescue the situation in that ! case. - The default is '-fno-cx-fortran-rules'. The following options control optimizations that may improve ! performance, but are not enabled by any '-O' options. This section includes experimental options that may produce broken code. ! '-fbranch-probabilities' ! After running a program compiled with '-fprofile-arcs' (*note Instrumentation Options::), you can compile it a second time using ! '-fbranch-probabilities', to improve optimizations based on the number of times each branch was taken. When a program compiled ! with '-fprofile-arcs' exits, it saves arc execution counts to a ! file called 'SOURCENAME.gcda' for each source file. The ! information in this data file is very dependent on the structure of ! the generated code, so you must use the same source code and the ! same optimization options for both compilations. ! With '-fbranch-probabilities', GCC puts a 'REG_BR_PROB' note on ! each 'JUMP_INSN' and 'CALL_INSN'. These can be used to improve optimization. Currently, they are only used in one place: in ! 'reorg.c', instead of guessing which path a branch is most likely ! to take, the 'REG_BR_PROB' values are used to exactly determine which path is taken more often. ! '-fprofile-values' ! If combined with '-fprofile-arcs', it adds code so that some data about values of expressions in the program is gathered. ! With '-fbranch-probabilities', it reads back the data gathered from ! profiling values of expressions for usage in optimizations. ! Enabled with '-fprofile-generate' and '-fprofile-use'. ! '-fprofile-reorder-functions' ! Function reordering based on profile instrumentation collects first ! time of execution of a function and orders these functions in ! ascending order. ! Enabled with '-fprofile-use'. ! '-fvpt' ! If combined with '-fprofile-arcs', this option instructs the compiler to add code to gather information about values of expressions. ! With '-fbranch-probabilities', it reads back the data gathered and actually performs the optimizations based on them. Currently the optimizations include specialization of division operations using the knowledge about the value of the denominator. ! '-frename-registers' Attempt to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers. --- 7616,7879 ---- floating-point arithmetic. These options trade off between speed and correctness. All must be specifically enabled. ! `-ffloat-store' Do not store floating-point variables in registers, and inhibit other options that might change whether a floating-point value is taken from a register or memory. This option prevents undesirable excess precision on machines such as the 68000 where the floating registers (of the 68881) keep more ! precision than a `double' is supposed to have. Similarly for the x86 architecture. For most programs, the excess precision does only good, but a few programs rely on the precise definition of ! IEEE floating point. Use `-ffloat-store' for such programs, after modifying them to store all pertinent intermediate computations into variables. ! `-fexcess-precision=STYLE' This option allows further control over excess precision on machines where floating-point registers have more precision than ! the IEEE `float' and `double' types and the processor does not support operations rounding to those types. By default, ! `-fexcess-precision=fast' is in effect; this means that operations are carried out in the precision of the registers and that it is unpredictable when rounding to the types specified in the source code takes place. When compiling C, if ! `-fexcess-precision=standard' is specified then excess precision follows the rules specified in ISO C99; in particular, both casts and assignments cause values to be rounded to their semantic types ! (whereas `-ffloat-store' only affects assignments). This option ! is enabled by default for C if a strict conformance option such as ! `-std=c99' is used. ! `-fexcess-precision=standard' is not implemented for languages ! other than C, and has no effect if `-funsafe-math-optimizations' ! or `-ffast-math' is specified. On the x86, it also has no effect ! if `-mfpmath=sse' or `-mfpmath=sse+387' is specified; in the ! former case, IEEE semantics apply without excess precision, and in ! the latter, rounding is unpredictable. ! `-ffast-math' ! Sets the options `-fno-math-errno', `-funsafe-math-optimizations', ! `-ffinite-math-only', `-fno-rounding-math', `-fno-signaling-nans' ! and `-fcx-limited-range'. ! This option causes the preprocessor macro `__FAST_MATH__' to be defined. ! This option is not turned on by any `-O' option besides `-Ofast' ! since it can result in incorrect output for programs that depend ! on an exact implementation of IEEE or ISO rules/specifications for ! math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. ! `-fno-math-errno' ! Do not set `errno' after calling math functions that are executed ! with a single instruction, e.g., `sqrt'. A program that relies on IEEE exceptions for math error handling may want to use this flag for speed while maintaining IEEE arithmetic compatibility. ! This option is not turned on by any `-O' option since it can ! result in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math ! functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. ! The default is `-fmath-errno'. ! On Darwin systems, the math library never sets `errno'. There is therefore no reason for the compiler to consider the possibility ! that it might, and `-fno-math-errno' is the default. + `-funsafe-math-optimizations' Allow optimizations for floating-point arithmetic that (a) assume that arguments and results are valid and (b) may violate IEEE or ANSI standards. When used at link time, it may include libraries or startup files that change the default FPU control word or other similar optimizations. ! This option is not turned on by any `-O' option since it can ! result in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math ! functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. Enables ! `-fno-signed-zeros', `-fno-trapping-math', `-fassociative-math' ! and `-freciprocal-math'. ! The default is `-fno-unsafe-math-optimizations'. + `-fassociative-math' Allow re-association of operands in series of floating-point operations. This violates the ISO C and C++ language standard by ! possibly changing computation result. NOTE: re-ordering may ! change the sign of zero as well as ignore NaNs and inhibit or ! create underflow or overflow (and thus cannot be used on code that ! relies on rounding behavior like `(x + 2**52) - 2**52'. May also ! reorder floating-point comparisons and thus may not be used when ! ordered comparisons are required. This option requires that both ! `-fno-signed-zeros' and `-fno-trapping-math' be in effect. ! Moreover, it doesn't make much sense with `-frounding-math'. For Fortran the option is automatically enabled when both ! `-fno-signed-zeros' and `-fno-trapping-math' are in effect. ! The default is `-fno-associative-math'. + `-freciprocal-math' Allow the reciprocal of a value to be used instead of dividing by ! the value if this enables optimizations. For example `x / y' can ! be replaced with `x * (1/y)', which is useful if `(1/y)' is ! subject to common subexpression elimination. Note that this loses precision and increases the number of flops operating on the value. ! The default is `-fno-reciprocal-math'. ! `-ffinite-math-only' Allow optimizations for floating-point arithmetic that assume that arguments and results are not NaNs or +-Infs. ! This option is not turned on by any `-O' option since it can ! result in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math ! functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications. ! The default is `-fno-finite-math-only'. ! `-fno-signed-zeros' Allow optimizations for floating-point arithmetic that ignore the signedness of zero. IEEE arithmetic specifies the behavior of distinct +0.0 and -0.0 values, which then prohibits simplification of expressions such as x+0.0 or 0.0*x (even with ! `-ffinite-math-only'). This option implies that the sign of a ! zero result isn't significant. ! The default is `-fsigned-zeros'. ! `-fno-trapping-math' Compile code assuming that floating-point operations cannot ! generate user-visible traps. These traps include division by ! zero, overflow, underflow, inexact result and invalid operation. ! This option requires that `-fno-signaling-nans' be in effect. ! Setting this option may allow faster code if one relies on ! "non-stop" IEEE arithmetic, for example. ! This option should never be turned on by any `-O' option since it ! can result in incorrect output for programs that depend on an ! exact implementation of IEEE or ISO rules/specifications for math functions. ! The default is `-ftrapping-math'. ! `-frounding-math' Disable transformations and optimizations that assume default floating-point rounding behavior. This is round-to-zero for all ! floating point to integer conversions, and round-to-nearest for ! all other arithmetic truncations. This option should be specified ! for programs that change the FP rounding mode dynamically, or that ! may be executed with a non-default rounding mode. This option ! disables constant folding of floating-point expressions at compile ! time (which may be affected by rounding mode) and arithmetic transformations that are unsafe in the presence of sign-dependent rounding modes. ! The default is `-fno-rounding-math'. This option is experimental and does not currently guarantee to disable all GCC optimizations that are affected by rounding mode. Future versions of GCC may provide finer control of this setting ! using C99's `FENV_ACCESS' pragma. This command-line option will ! be used to specify the default state for `FENV_ACCESS'. ! `-fsignaling-nans' Compile code assuming that IEEE signaling NaNs may generate user-visible traps during floating-point operations. Setting this option disables optimizations that may change the number of exceptions visible with signaling NaNs. This option implies ! `-ftrapping-math'. ! This option causes the preprocessor macro `__SUPPORT_SNAN__' to be defined. ! The default is `-fno-signaling-nans'. This option is experimental and does not currently guarantee to disable all GCC optimizations that affect signaling NaN behavior. ! `-fsingle-precision-constant' Treat floating-point constants as single precision instead of implicitly converting them to double-precision constants. ! `-fcx-limited-range' When enabled, this option states that a range reduction step is not needed when performing complex division. Also, there is no ! checking whether the result of a complex multiplication or ! division is `NaN + I*NaN', with an attempt to rescue the situation ! in that case. The default is `-fno-cx-limited-range', but is ! enabled by `-ffast-math'. This option controls the default setting of the ISO C99 ! `CX_LIMITED_RANGE' pragma. Nevertheless, the option applies to ! all languages. ! `-fcx-fortran-rules' Complex multiplication and division follow Fortran rules. Range reduction is done as part of complex division, but there is no ! checking whether the result of a complex multiplication or ! division is `NaN + I*NaN', with an attempt to rescue the situation ! in that case. ! ! The default is `-fno-cx-fortran-rules'. The following options control optimizations that may improve ! performance, but are not enabled by any `-O' options. This section includes experimental options that may produce broken code. ! `-fbranch-probabilities' ! After running a program compiled with `-fprofile-arcs' (*note Instrumentation Options::), you can compile it a second time using ! `-fbranch-probabilities', to improve optimizations based on the number of times each branch was taken. When a program compiled ! with `-fprofile-arcs' exits, it saves arc execution counts to a ! file called `SOURCENAME.gcda' for each source file. The ! information in this data file is very dependent on the structure ! of the generated code, so you must use the same source code and ! the same optimization options for both compilations. ! With `-fbranch-probabilities', GCC puts a `REG_BR_PROB' note on ! each `JUMP_INSN' and `CALL_INSN'. These can be used to improve optimization. Currently, they are only used in one place: in ! `reorg.c', instead of guessing which path a branch is most likely ! to take, the `REG_BR_PROB' values are used to exactly determine which path is taken more often. ! `-fprofile-values' ! If combined with `-fprofile-arcs', it adds code so that some data about values of expressions in the program is gathered. ! With `-fbranch-probabilities', it reads back the data gathered ! from profiling values of expressions for usage in optimizations. ! Enabled with `-fprofile-generate' and `-fprofile-use'. ! `-fprofile-reorder-functions' ! Function reordering based on profile instrumentation collects ! first time of execution of a function and orders these functions ! in ascending order. ! Enabled with `-fprofile-use'. ! `-fvpt' ! If combined with `-fprofile-arcs', this option instructs the compiler to add code to gather information about values of expressions. ! With `-fbranch-probabilities', it reads back the data gathered and actually performs the optimizations based on them. Currently the optimizations include specialization of division operations using the knowledge about the value of the denominator. ! `-frename-registers' Attempt to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers. *************** includes experimental options that may p *** 7833,7890 **** however, it can make debugging impossible, since variables no longer stay in a "home register". ! Enabled by default with '-funroll-loops' and '-fpeel-loops'. ! '-fschedule-fusion' Performs a target dependent pass over the instruction stream to schedule instructions of same type together because target machine can execute them more efficiently if they are adjacent to each other in the instruction flow. ! Enabled at levels '-O2', '-O3', '-Os'. ! '-ftracer' Perform tail duplication to enlarge superblock size. This ! transformation simplifies the control flow of the function allowing ! other optimizations to do a better job. ! Enabled with '-fprofile-use'. ! '-funroll-loops' Unroll loops whose number of iterations can be determined at ! compile time or upon entry to the loop. '-funroll-loops' implies ! '-frerun-cse-after-loop', '-fweb' and '-frename-registers'. It ! also turns on complete loop peeling (i.e. complete removal of loops ! with a small constant number of iterations). This option makes ! code larger, and may or may not make it run faster. ! Enabled with '-fprofile-use'. ! '-funroll-all-loops' Unroll all loops, even if their number of iterations is uncertain when the loop is entered. This usually makes programs run more ! slowly. '-funroll-all-loops' implies the same options as ! '-funroll-loops'. ! '-fpeel-loops' Peels loops for which there is enough information that they do not roll much (from profile feedback). It also turns on complete loop peeling (i.e. complete removal of loops with small constant number of iterations). ! Enabled with '-fprofile-use'. ! '-fmove-loop-invariants' Enables the loop invariant motion pass in the RTL loop optimizer. ! Enabled at level '-O1' ! '-funswitch-loops' Move branches with loop invariant conditions out of the loop, with duplicates of the loop on both branches (modified according to result of the condition). ! '-ffunction-sections' ! '-fdata-sections' Place each function or data item into its own section in the output file if the target supports arbitrary sections. The name of the function or the name of the data item determines the section's name --- 7881,7938 ---- however, it can make debugging impossible, since variables no longer stay in a "home register". ! Enabled by default with `-funroll-loops' and `-fpeel-loops'. ! `-fschedule-fusion' Performs a target dependent pass over the instruction stream to schedule instructions of same type together because target machine can execute them more efficiently if they are adjacent to each other in the instruction flow. ! Enabled at levels `-O2', `-O3', `-Os'. ! `-ftracer' Perform tail duplication to enlarge superblock size. This ! transformation simplifies the control flow of the function ! allowing other optimizations to do a better job. ! Enabled with `-fprofile-use'. ! `-funroll-loops' Unroll loops whose number of iterations can be determined at ! compile time or upon entry to the loop. `-funroll-loops' implies ! `-frerun-cse-after-loop', `-fweb' and `-frename-registers'. It ! also turns on complete loop peeling (i.e. complete removal of ! loops with a small constant number of iterations). This option ! makes code larger, and may or may not make it run faster. ! Enabled with `-fprofile-use'. ! `-funroll-all-loops' Unroll all loops, even if their number of iterations is uncertain when the loop is entered. This usually makes programs run more ! slowly. `-funroll-all-loops' implies the same options as ! `-funroll-loops'. ! `-fpeel-loops' Peels loops for which there is enough information that they do not roll much (from profile feedback). It also turns on complete loop peeling (i.e. complete removal of loops with small constant number of iterations). ! Enabled with `-fprofile-use'. ! `-fmove-loop-invariants' Enables the loop invariant motion pass in the RTL loop optimizer. ! Enabled at level `-O1' ! `-funswitch-loops' Move branches with loop invariant conditions out of the loop, with duplicates of the loop on both branches (modified according to result of the condition). ! `-ffunction-sections' ! `-fdata-sections' Place each function or data item into its own section in the output file if the target supports arbitrary sections. The name of the function or the name of the data item determines the section's name *************** includes experimental options that may p *** 7898,7940 **** Only use these options when there are significant benefits from doing so. When you specify these options, the assembler and linker ! create larger object and executable files and are also slower. You ! cannot use 'gprof' on all systems if you specify this option, and ! you may have problems with debugging if you specify both this ! option and '-g'. ! '-fbranch-target-load-optimize' Perform branch target register load optimization before prologue / epilogue threading. The use of target registers can typically be exposed only during reload, thus hoisting loads out of loops and doing inter-block scheduling needs a separate optimization pass. ! '-fbranch-target-load-optimize2' Perform branch target register load optimization after prologue / epilogue threading. ! '-fbtr-bb-exclusive' When performing branch target register load optimization, don't reuse branch target registers within any basic block. ! '-fstdarg-opt' Optimize the prologue of variadic argument functions with respect to usage of those arguments. ! '-fsection-anchors' Try to reduce the number of symbolic address calculations by using shared "anchor" symbols to address nearby objects. This ! transformation can help to reduce the number of GOT entries and GOT ! accesses on some targets. ! For example, the implementation of the following function 'foo': static int a, b, c; int foo (void) { return a + b + c; } usually calculates the addresses of all three variables, but if you ! compile it with '-fsection-anchors', it accesses the variables from ! a common anchor point instead. The effect is similar to the following pseudocode (which isn't valid C): int foo (void) --- 7946,7988 ---- Only use these options when there are significant benefits from doing so. When you specify these options, the assembler and linker ! create larger object and executable files and are also slower. ! You cannot use `gprof' on all systems if you specify this option, ! and you may have problems with debugging if you specify both this ! option and `-g'. ! `-fbranch-target-load-optimize' Perform branch target register load optimization before prologue / epilogue threading. The use of target registers can typically be exposed only during reload, thus hoisting loads out of loops and doing inter-block scheduling needs a separate optimization pass. ! `-fbranch-target-load-optimize2' Perform branch target register load optimization after prologue / epilogue threading. ! `-fbtr-bb-exclusive' When performing branch target register load optimization, don't reuse branch target registers within any basic block. ! `-fstdarg-opt' Optimize the prologue of variadic argument functions with respect to usage of those arguments. ! `-fsection-anchors' Try to reduce the number of symbolic address calculations by using shared "anchor" symbols to address nearby objects. This ! transformation can help to reduce the number of GOT entries and ! GOT accesses on some targets. ! For example, the implementation of the following function `foo': static int a, b, c; int foo (void) { return a + b + c; } usually calculates the addresses of all three variables, but if you ! compile it with `-fsection-anchors', it accesses the variables ! from a common anchor point instead. The effect is similar to the following pseudocode (which isn't valid C): int foo (void) *************** includes experimental options that may p *** 7945,7956 **** Not all targets support this option. ! '--param NAME=VALUE' In some places, GCC uses various constants to control the amount of optimization that is done. For example, GCC does not inline functions that contain more than a certain number of instructions. You can control some of these constants on the command line using ! the '--param' option. The names of specific parameters, and the meaning of the values, are tied to the internals of the compiler, and are subject to --- 7993,8004 ---- Not all targets support this option. ! `--param NAME=VALUE' In some places, GCC uses various constants to control the amount of optimization that is done. For example, GCC does not inline functions that contain more than a certain number of instructions. You can control some of these constants on the command line using ! the `--param' option. The names of specific parameters, and the meaning of the values, are tied to the internals of the compiler, and are subject to *************** includes experimental options that may p *** 7959,7970 **** In each case, the VALUE is an integer. The allowable choices for NAME are: ! 'predictable-branch-outcome' When branch is predicted to be taken with probability lower than this threshold (in percent), then it is considered well ! predictable. The default is 10. ! 'max-rtl-if-conversion-insns' RTL if-conversion tries to remove conditional branches around a block and replace them with conditionally executed instructions. This parameter gives the maximum number of --- 8007,8018 ---- In each case, the VALUE is an integer. The allowable choices for NAME are: ! `predictable-branch-outcome' When branch is predicted to be taken with probability lower than this threshold (in percent), then it is considered well ! predictable. The default is 10. ! `max-rtl-if-conversion-insns' RTL if-conversion tries to remove conditional branches around a block and replace them with conditionally executed instructions. This parameter gives the maximum number of *************** includes experimental options that may p *** 7973,7999 **** also use other heuristics to decide whether if-conversion is likely to be profitable. ! 'max-crossjump-edges' The maximum number of incoming edges to consider for ! cross-jumping. The algorithm used by '-fcrossjumping' is O(N^2) in the number of edges incoming to each block. Increasing values mean more aggressive optimization, making the compilation time increase with probably small improvement in executable size. ! 'min-crossjump-insns' ! The minimum number of instructions that must be matched at the ! end of two blocks before cross-jumping is performed on them. ! This value is ignored in the case where all instructions in ! the block being cross-jumped from are matched. The default ! value is 5. ! 'max-grow-copy-bb-insns' The maximum code size expansion factor when copying basic blocks instead of jumping. The expansion is relative to a jump instruction. The default value is 8. ! 'max-goto-duplication-insns' The maximum number of instructions to duplicate to a block that jumps to a computed goto. To avoid O(N^2) behavior in a number of passes, GCC factors computed gotos early in the --- 8021,8047 ---- also use other heuristics to decide whether if-conversion is likely to be profitable. ! `max-crossjump-edges' The maximum number of incoming edges to consider for ! cross-jumping. The algorithm used by `-fcrossjumping' is O(N^2) in the number of edges incoming to each block. Increasing values mean more aggressive optimization, making the compilation time increase with probably small improvement in executable size. ! `min-crossjump-insns' ! The minimum number of instructions that must be matched at ! the end of two blocks before cross-jumping is performed on ! them. This value is ignored in the case where all ! instructions in the block being cross-jumped from are ! matched. The default value is 5. ! `max-grow-copy-bb-insns' The maximum code size expansion factor when copying basic blocks instead of jumping. The expansion is relative to a jump instruction. The default value is 8. ! `max-goto-duplication-insns' The maximum number of instructions to duplicate to a block that jumps to a computed goto. To avoid O(N^2) behavior in a number of passes, GCC factors computed gotos early in the *************** includes experimental options that may p *** 8002,8008 **** than max-goto-duplication-insns are unfactored. The default value is 8. ! 'max-delay-slot-insn-search' The maximum number of instructions to consider when looking for an instruction to fill a delay slot. If more than this arbitrary number of instructions are searched, the time --- 8050,8056 ---- than max-goto-duplication-insns are unfactored. The default value is 8. ! `max-delay-slot-insn-search' The maximum number of instructions to consider when looking for an instruction to fill a delay slot. If more than this arbitrary number of instructions are searched, the time *************** includes experimental options that may p *** 8011,8197 **** optimization, making the compilation time increase with probably small improvement in execution time. ! 'max-delay-slot-live-search' When trying to fill delay slots, the maximum number of ! instructions to consider when searching for a block with valid ! live register information. Increasing this arbitrarily chosen ! value means more aggressive optimization, increasing the ! compilation time. This parameter should be removed when the ! delay slot code is rewritten to maintain the control-flow graph. ! 'max-gcse-memory' ! The approximate maximum amount of memory that can be allocated ! in order to perform the global common subexpression elimination optimization. If more memory than specified is required, the optimization is not done. ! 'max-gcse-insertion-ratio' If the ratio of expression insertions to deletions is larger than this value for any expression, then RTL PRE inserts or removes the expression and thus leaves partially redundant computations in the instruction stream. The default value is 20. ! 'max-pending-list-length' The maximum number of pending dependencies scheduling allows before flushing the current state and starting over. Large functions with few branches or calls can create excessively large lists which needlessly consume memory and resources. ! 'max-modulo-backtrack-attempts' The maximum number of backtrack attempts the scheduler should make when modulo scheduling a loop. Larger values can exponentially increase compilation time. ! 'max-inline-insns-single' ! Several parameters control the tree inliner used in GCC. This ! number sets the maximum number of instructions (counted in ! GCC's internal representation) in a single function that the ! tree inliner considers for inlining. This only affects functions declared inline and methods implemented in a class declaration (C++). The default value is 400. ! 'max-inline-insns-auto' ! When you use '-finline-functions' (included in '-O3'), a lot of functions that would otherwise not be considered for inlining by the compiler are investigated. To those functions, a different (more restrictive) limit compared to functions declared inline can be applied. The default value is 40. ! 'inline-min-speedup' When estimated performance improvement of caller + callee runtime exceeds this threshold (in precent), the function can ! be inlined regardless the limit on '--param ! max-inline-insns-single' and '--param max-inline-insns-auto'. ! 'large-function-insns' The limit specifying really large functions. For functions ! larger than this limit after inlining, inlining is constrained ! by '--param large-function-growth'. This parameter is useful ! primarily to avoid extreme compilation time caused by ! non-linear algorithms used by the back end. The default value ! is 2700. ! 'large-function-growth' Specifies maximal growth of large function caused by inlining in percents. The default value is 100 which limits large function growth to 2.0 times the original size. ! 'large-unit-insns' ! The limit specifying large translation unit. Growth caused by ! inlining of units larger than this limit is limited by ! '--param inline-unit-growth'. For small units this might be too tight. For example, consider a unit consisting of ! function A that is inline and B that just calls A three times. ! If B is small relative to A, the growth of unit is 300\% and ! yet such inlining is very sane. For very large units ! consisting of small inlineable functions, however, the overall ! unit growth limit is needed to avoid exponential explosion of ! code size. Thus for smaller units, the size is increased to ! '--param large-unit-insns' before applying '--param ! inline-unit-growth'. The default is 10000. ! 'inline-unit-growth' Specifies maximal overall growth of the compilation unit ! caused by inlining. The default value is 20 which limits unit ! growth to 1.2 times the original size. Cold functions (either ! marked cold via an attribute or by profile feedback) are not ! accounted into the unit size. ! 'ipcp-unit-growth' Specifies maximal overall growth of the compilation unit caused by interprocedural constant propagation. The default ! value is 10 which limits unit growth to 1.1 times the original ! size. ! 'large-stack-frame' The limit specifying large stack frames. While inlining the ! algorithm is trying to not grow past this limit too much. The ! default value is 256 bytes. ! 'large-stack-frame-growth' Specifies maximal growth of large stack frames caused by inlining in percents. The default value is 1000 which limits large stack frame growth to 11 times the original size. ! 'max-inline-insns-recursive' ! 'max-inline-insns-recursive-auto' Specifies the maximum number of instructions an out-of-line copy of a self-recursive inline function can grow into by performing recursive inlining. ! '--param max-inline-insns-recursive' applies to functions ! declared inline. For functions not declared inline, recursive ! inlining happens only when '-finline-functions' (included in ! '-O3') is enabled; '--param max-inline-insns-recursive-auto' ! applies instead. The default value is 450. ! 'max-inline-recursive-depth' ! 'max-inline-recursive-depth-auto' Specifies the maximum recursion depth used for recursive inlining. ! '--param max-inline-recursive-depth' applies to functions ! declared inline. For functions not declared inline, recursive ! inlining happens only when '-finline-functions' (included in ! '-O3') is enabled; '--param max-inline-recursive-depth-auto' ! applies instead. The default value is 8. ! 'min-inline-recursive-probability' ! Recursive inlining is profitable only for function having deep ! recursion in average and can hurt for function having little ! recursion depth by increasing the prologue size or complexity ! of function body to other optimizers. ! When profile feedback is available (see '-fprofile-generate') the actual recursion depth can be guessed from probability that function recurses via a given call expression. This parameter limits inlining only to call expressions whose probability exceeds the given threshold (in percents). The default value is 10. ! 'early-inlining-insns' Specify growth that the early inliner can make. In effect it increases the amount of inlining for code having a large abstraction penalty. The default value is 14. ! 'max-early-inliner-iterations' Limit of iterations of the early inliner. This basically bounds the number of nested indirect calls the early inliner can resolve. Deeper chains are still handled by late inlining. ! 'comdat-sharing-probability' Probability (in percent) that C++ inline function with comdat visibility are shared across multiple compilation units. The default value is 20. ! 'profile-func-internal-id' A parameter to control whether to use function internal id in ! profile database lookup. If the value is 0, the compiler uses an id that is based on function assembler name and filename, which makes old profile data more tolerant to source changes such as function reordering etc. The default value is 0. ! 'min-vect-loop-bound' The minimum number of iterations under which loops are not ! vectorized when '-ftree-vectorize' is used. The number of iterations after vectorization needs to be greater than the value specified by this option to allow vectorization. The default value is 0. ! 'gcse-cost-distance-ratio' Scaling factor in calculation of maximum distance an expression can be moved by GCSE optimizations. This is currently supported only in the code hoisting pass. The bigger the ratio, the more aggressive code hoisting is with simple expressions, i.e., the expressions that have cost less ! than 'gcse-unrestricted-cost'. Specifying 0 disables hoisting ! of simple expressions. The default value is 10. ! 'gcse-unrestricted-cost' Cost, roughly measured as the cost of a single typical machine instruction, at which GCSE optimizations do not constrain the distance an expression can travel. This is currently --- 8059,8247 ---- optimization, making the compilation time increase with probably small improvement in execution time. ! `max-delay-slot-live-search' When trying to fill delay slots, the maximum number of ! instructions to consider when searching for a block with ! valid live register information. Increasing this arbitrarily ! chosen value means more aggressive optimization, increasing ! the compilation time. This parameter should be removed when ! the delay slot code is rewritten to maintain the control-flow graph. ! `max-gcse-memory' ! The approximate maximum amount of memory that can be ! allocated in order to perform the global common subexpression elimination optimization. If more memory than specified is required, the optimization is not done. ! `max-gcse-insertion-ratio' If the ratio of expression insertions to deletions is larger than this value for any expression, then RTL PRE inserts or removes the expression and thus leaves partially redundant computations in the instruction stream. The default value is 20. ! `max-pending-list-length' The maximum number of pending dependencies scheduling allows before flushing the current state and starting over. Large functions with few branches or calls can create excessively large lists which needlessly consume memory and resources. ! `max-modulo-backtrack-attempts' The maximum number of backtrack attempts the scheduler should make when modulo scheduling a loop. Larger values can exponentially increase compilation time. ! `max-inline-insns-single' ! Several parameters control the tree inliner used in GCC. ! This number sets the maximum number of instructions (counted ! in GCC's internal representation) in a single function that ! the tree inliner considers for inlining. This only affects functions declared inline and methods implemented in a class declaration (C++). The default value is 400. ! `max-inline-insns-auto' ! When you use `-finline-functions' (included in `-O3'), a lot of functions that would otherwise not be considered for inlining by the compiler are investigated. To those functions, a different (more restrictive) limit compared to functions declared inline can be applied. The default value is 40. ! `inline-min-speedup' When estimated performance improvement of caller + callee runtime exceeds this threshold (in precent), the function can ! be inlined regardless the limit on `--param ! max-inline-insns-single' and `--param max-inline-insns-auto'. ! `large-function-insns' The limit specifying really large functions. For functions ! larger than this limit after inlining, inlining is ! constrained by `--param large-function-growth'. This ! parameter is useful primarily to avoid extreme compilation ! time caused by non-linear algorithms used by the back end. ! The default value is 2700. ! `large-function-growth' Specifies maximal growth of large function caused by inlining in percents. The default value is 100 which limits large function growth to 2.0 times the original size. ! `large-unit-insns' ! The limit specifying large translation unit. Growth caused ! by inlining of units larger than this limit is limited by ! `--param inline-unit-growth'. For small units this might be too tight. For example, consider a unit consisting of ! function A that is inline and B that just calls A three ! times. If B is small relative to A, the growth of unit is ! 300\% and yet such inlining is very sane. For very large ! units consisting of small inlineable functions, however, the ! overall unit growth limit is needed to avoid exponential ! explosion of code size. Thus for smaller units, the size is ! increased to `--param large-unit-insns' before applying ! `--param inline-unit-growth'. The default is 10000. ! `inline-unit-growth' Specifies maximal overall growth of the compilation unit ! caused by inlining. The default value is 20 which limits ! unit growth to 1.2 times the original size. Cold functions ! (either marked cold via an attribute or by profile feedback) ! are not accounted into the unit size. ! `ipcp-unit-growth' Specifies maximal overall growth of the compilation unit caused by interprocedural constant propagation. The default ! value is 10 which limits unit growth to 1.1 times the ! original size. ! `large-stack-frame' The limit specifying large stack frames. While inlining the ! algorithm is trying to not grow past this limit too much. ! The default value is 256 bytes. ! `large-stack-frame-growth' Specifies maximal growth of large stack frames caused by inlining in percents. The default value is 1000 which limits large stack frame growth to 11 times the original size. ! `max-inline-insns-recursive' ! `max-inline-insns-recursive-auto' Specifies the maximum number of instructions an out-of-line copy of a self-recursive inline function can grow into by performing recursive inlining. ! `--param max-inline-insns-recursive' applies to functions ! declared inline. For functions not declared inline, ! recursive inlining happens only when `-finline-functions' ! (included in `-O3') is enabled; `--param ! max-inline-insns-recursive-auto' applies instead. The ! default value is 450. ! `max-inline-recursive-depth' ! `max-inline-recursive-depth-auto' Specifies the maximum recursion depth used for recursive inlining. ! `--param max-inline-recursive-depth' applies to functions ! declared inline. For functions not declared inline, ! recursive inlining happens only when `-finline-functions' ! (included in `-O3') is enabled; `--param ! max-inline-recursive-depth-auto' applies instead. The ! default value is 8. ! `min-inline-recursive-probability' ! Recursive inlining is profitable only for function having ! deep recursion in average and can hurt for function having ! little recursion depth by increasing the prologue size or ! complexity of function body to other optimizers. ! When profile feedback is available (see `-fprofile-generate') the actual recursion depth can be guessed from probability that function recurses via a given call expression. This parameter limits inlining only to call expressions whose probability exceeds the given threshold (in percents). The default value is 10. ! `early-inlining-insns' Specify growth that the early inliner can make. In effect it increases the amount of inlining for code having a large abstraction penalty. The default value is 14. ! `max-early-inliner-iterations' Limit of iterations of the early inliner. This basically bounds the number of nested indirect calls the early inliner can resolve. Deeper chains are still handled by late inlining. ! `comdat-sharing-probability' Probability (in percent) that C++ inline function with comdat visibility are shared across multiple compilation units. The default value is 20. ! `profile-func-internal-id' A parameter to control whether to use function internal id in ! profile database lookup. If the value is 0, the compiler uses an id that is based on function assembler name and filename, which makes old profile data more tolerant to source changes such as function reordering etc. The default value is 0. ! `min-vect-loop-bound' The minimum number of iterations under which loops are not ! vectorized when `-ftree-vectorize' is used. The number of iterations after vectorization needs to be greater than the value specified by this option to allow vectorization. The default value is 0. ! `gcse-cost-distance-ratio' Scaling factor in calculation of maximum distance an expression can be moved by GCSE optimizations. This is currently supported only in the code hoisting pass. The bigger the ratio, the more aggressive code hoisting is with simple expressions, i.e., the expressions that have cost less ! than `gcse-unrestricted-cost'. Specifying 0 disables ! hoisting of simple expressions. The default value is 10. ! `gcse-unrestricted-cost' Cost, roughly measured as the cost of a single typical machine instruction, at which GCSE optimizations do not constrain the distance an expression can travel. This is currently *************** includes experimental options that may p *** 8200,8321 **** allows all expressions to travel unrestricted distances. The default value is 3. ! 'max-hoist-depth' The depth of search in the dominator tree for expressions to hoist. This is used to avoid quadratic behavior in hoisting algorithm. The value of 0 does not limit on the search, but may slow down compilation of huge functions. The default value is 30. ! 'max-tail-merge-comparisons' The maximum amount of similar bbs to compare a bb with. This ! is used to avoid quadratic behavior in tree tail merging. The ! default value is 10. ! 'max-tail-merge-iterations' The maximum amount of iterations of the pass over the ! function. This is used to limit compilation time in tree tail ! merging. The default value is 2. ! 'max-unrolled-insns' The maximum number of instructions that a loop may have to be unrolled. If a loop is unrolled, this parameter also determines how many times the loop code is unrolled. ! 'max-average-unrolled-insns' The maximum number of instructions biased by probabilities of their execution that a loop may have to be unrolled. If a loop is unrolled, this parameter also determines how many times the loop code is unrolled. ! 'max-unroll-times' The maximum number of unrollings of a single loop. ! 'max-peeled-insns' The maximum number of instructions that a loop may have to be peeled. If a loop is peeled, this parameter also determines how many times the loop code is peeled. ! 'max-peel-times' The maximum number of peelings of a single loop. ! 'max-peel-branches' The maximum number of branches on the hot path through the peeled sequence. ! 'max-completely-peeled-insns' The maximum number of insns of a completely peeled loop. ! 'max-completely-peel-times' The maximum number of iterations of a loop to be suitable for complete peeling. ! 'max-completely-peel-loop-nest-depth' The maximum depth of a loop nest suitable for complete peeling. ! 'max-unswitch-insns' The maximum number of insns of an unswitched loop. ! 'max-unswitch-level' The maximum number of branches unswitched in a single loop. ! 'lim-expensive' The minimum cost of an expensive expression in the loop invariant motion. ! 'iv-consider-all-candidates-bound' Bound on number of candidates for induction variables, below which all candidates are considered for each use in induction variable optimizations. If there are more candidates than this, only the most relevant ones are considered to avoid quadratic time complexity. ! 'iv-max-considered-uses' The induction variable optimizations give up on loops that contain more induction variable uses. ! 'iv-always-prune-cand-set-bound' If the number of candidates in the set is smaller than this value, always try to remove unnecessary ivs from the set when adding a new one. ! 'scev-max-expr-size' Bound on size of expressions used in the scalar evolutions analyzer. Large expressions slow the analyzer. ! 'scev-max-expr-complexity' Bound on the complexity of the expressions in the scalar evolutions analyzer. Complex expressions slow the analyzer. ! 'vect-max-version-for-alignment-checks' The maximum number of run-time checks that can be performed when doing loop versioning for alignment in the vectorizer. ! 'vect-max-version-for-alias-checks' The maximum number of run-time checks that can be performed when doing loop versioning for alias in the vectorizer. ! 'vect-max-peeling-for-alignment' The maximum number of loop peels to enhance access alignment ! for vectorizer. Value -1 means no limit. ! 'max-iterations-to-track' The maximum number of iterations of a loop the brute-force ! algorithm for analysis of the number of iterations of the loop ! tries to evaluate. ! 'hot-bb-count-ws-permille' A basic block profile count is considered hot if it ! contributes to the given permillage (i.e. 0...1000) of the entire profiled execution. ! 'hot-bb-frequency-fraction' Select fraction of the entry block frequency of executions of basic block in function given basic block needs to have to be considered hot. ! 'max-predicted-iterations' The maximum number of loop iterations we predict statically. This is useful in cases where a function contains a single loop with known bound and another loop with unknown bound. --- 8250,8371 ---- allows all expressions to travel unrestricted distances. The default value is 3. ! `max-hoist-depth' The depth of search in the dominator tree for expressions to hoist. This is used to avoid quadratic behavior in hoisting algorithm. The value of 0 does not limit on the search, but may slow down compilation of huge functions. The default value is 30. ! `max-tail-merge-comparisons' The maximum amount of similar bbs to compare a bb with. This ! is used to avoid quadratic behavior in tree tail merging. ! The default value is 10. ! `max-tail-merge-iterations' The maximum amount of iterations of the pass over the ! function. This is used to limit compilation time in tree ! tail merging. The default value is 2. ! `max-unrolled-insns' The maximum number of instructions that a loop may have to be unrolled. If a loop is unrolled, this parameter also determines how many times the loop code is unrolled. ! `max-average-unrolled-insns' The maximum number of instructions biased by probabilities of their execution that a loop may have to be unrolled. If a loop is unrolled, this parameter also determines how many times the loop code is unrolled. ! `max-unroll-times' The maximum number of unrollings of a single loop. ! `max-peeled-insns' The maximum number of instructions that a loop may have to be peeled. If a loop is peeled, this parameter also determines how many times the loop code is peeled. ! `max-peel-times' The maximum number of peelings of a single loop. ! `max-peel-branches' The maximum number of branches on the hot path through the peeled sequence. ! `max-completely-peeled-insns' The maximum number of insns of a completely peeled loop. ! `max-completely-peel-times' The maximum number of iterations of a loop to be suitable for complete peeling. ! `max-completely-peel-loop-nest-depth' The maximum depth of a loop nest suitable for complete peeling. ! `max-unswitch-insns' The maximum number of insns of an unswitched loop. ! `max-unswitch-level' The maximum number of branches unswitched in a single loop. ! `lim-expensive' The minimum cost of an expensive expression in the loop invariant motion. ! `iv-consider-all-candidates-bound' Bound on number of candidates for induction variables, below which all candidates are considered for each use in induction variable optimizations. If there are more candidates than this, only the most relevant ones are considered to avoid quadratic time complexity. ! `iv-max-considered-uses' The induction variable optimizations give up on loops that contain more induction variable uses. ! `iv-always-prune-cand-set-bound' If the number of candidates in the set is smaller than this value, always try to remove unnecessary ivs from the set when adding a new one. ! `scev-max-expr-size' Bound on size of expressions used in the scalar evolutions analyzer. Large expressions slow the analyzer. ! `scev-max-expr-complexity' Bound on the complexity of the expressions in the scalar evolutions analyzer. Complex expressions slow the analyzer. ! `vect-max-version-for-alignment-checks' The maximum number of run-time checks that can be performed when doing loop versioning for alignment in the vectorizer. ! `vect-max-version-for-alias-checks' The maximum number of run-time checks that can be performed when doing loop versioning for alias in the vectorizer. ! `vect-max-peeling-for-alignment' The maximum number of loop peels to enhance access alignment ! for vectorizer. Value -1 means no limit. ! `max-iterations-to-track' The maximum number of iterations of a loop the brute-force ! algorithm for analysis of the number of iterations of the ! loop tries to evaluate. ! `hot-bb-count-ws-permille' A basic block profile count is considered hot if it ! contributes to the given permillage (i.e. 0...1000) of the entire profiled execution. ! `hot-bb-frequency-fraction' Select fraction of the entry block frequency of executions of basic block in function given basic block needs to have to be considered hot. ! `max-predicted-iterations' The maximum number of loop iterations we predict statically. This is useful in cases where a function contains a single loop with known bound and another loop with unknown bound. *************** includes experimental options that may p *** 8324,8392 **** means that the loop without bounds appears artificially cold relative to the other one. ! 'builtin-expect-probability' ! Control the probability of the expression having the specified ! value. This parameter takes a percentage (i.e. 0 ... 100) ! as input. The default probability of 90 is obtained empirically. ! 'align-threshold' ! Select fraction of the maximal frequency of executions of a basic block in a function to align the basic block. ! 'align-loop-iterations' ! A loop expected to iterate at least the selected number of iterations is aligned. ! 'tracer-dynamic-coverage' ! 'tracer-dynamic-coverage-feedback' ! This value is used to limit superblock formation once the given percentage of executed instructions is covered. This limits unnecessary code size expansion. ! The 'tracer-dynamic-coverage-feedback' parameter is used only when profile feedback is available. The real profiles (as opposed to statically estimated ones) are much less balanced allowing the threshold to be larger value. ! 'tracer-max-code-growth' Stop tail duplication once code growth has reached given ! percentage. This is a rather artificial limit, as most of the ! duplicates are eliminated later in cross jumping, so it may be ! set to much higher values than is the desired code growth. ! ! 'tracer-min-branch-ratio' Stop reverse growth when the reverse probability of best edge is less than this threshold (in percent). ! 'tracer-min-branch-probability' ! 'tracer-min-branch-probability-feedback' ! Stop forward growth if the best edge has probability lower than this threshold. ! Similarly to 'tracer-dynamic-coverage' two parameters are ! provided. 'tracer-min-branch-probability-feedback' is used for compilation with profile feedback and ! 'tracer-min-branch-probability' compilation without. The value for compilation with profile feedback needs to be more conservative (higher) in order to make tracer effective. ! 'max-cse-path-length' ! The maximum number of basic blocks on path that CSE considers. The default is 10. ! 'max-cse-insns' The maximum number of instructions CSE processes before flushing. The default is 1000. ! 'ggc-min-expand' ! GCC uses a garbage collector to manage its own memory allocation. This parameter specifies the minimum percentage by which the garbage collector's heap should be allowed to --- 8374,8436 ---- means that the loop without bounds appears artificially cold relative to the other one. ! `builtin-expect-probability' ! Control the probability of the expression having the ! specified value. This parameter takes a percentage (i.e. 0 ! ... 100) as input. The default probability of 90 is obtained empirically. ! `align-threshold' Select fraction of the maximal frequency of executions of a basic block in a function to align the basic block. ! `align-loop-iterations' A loop expected to iterate at least the selected number of iterations is aligned. ! `tracer-dynamic-coverage' ! `tracer-dynamic-coverage-feedback' This value is used to limit superblock formation once the given percentage of executed instructions is covered. This limits unnecessary code size expansion. ! The `tracer-dynamic-coverage-feedback' parameter is used only when profile feedback is available. The real profiles (as opposed to statically estimated ones) are much less balanced allowing the threshold to be larger value. ! `tracer-max-code-growth' Stop tail duplication once code growth has reached given ! percentage. This is a rather artificial limit, as most of ! the duplicates are eliminated later in cross jumping, so it ! may be set to much higher values than is the desired code ! growth. + `tracer-min-branch-ratio' Stop reverse growth when the reverse probability of best edge is less than this threshold (in percent). ! `tracer-min-branch-probability' ! `tracer-min-branch-probability-feedback' Stop forward growth if the best edge has probability lower than this threshold. ! Similarly to `tracer-dynamic-coverage' two parameters are ! provided. `tracer-min-branch-probability-feedback' is used for compilation with profile feedback and ! `tracer-min-branch-probability' compilation without. The value for compilation with profile feedback needs to be more conservative (higher) in order to make tracer effective. ! `max-cse-path-length' The maximum number of basic blocks on path that CSE considers. The default is 10. ! `max-cse-insns' The maximum number of instructions CSE processes before flushing. The default is 1000. ! `ggc-min-expand' GCC uses a garbage collector to manage its own memory allocation. This parameter specifies the minimum percentage by which the garbage collector's heap should be allowed to *************** includes experimental options that may p *** 8394,8413 **** compilation speed; it has no effect on code generation. The default is 30% + 70% * (RAM/1GB) with an upper bound of ! 100% when RAM >= 1GB. If 'getrlimit' is available, the notion ! of "RAM" is the smallest of actual RAM and 'RLIMIT_DATA' or ! 'RLIMIT_AS'. If GCC is not able to calculate RAM on a ! particular platform, the lower bound of 30% is used. Setting ! this parameter and 'ggc-min-heapsize' to zero causes a full ! collection to occur at every opportunity. This is extremely ! slow, but can be useful for debugging. ! ! 'ggc-min-heapsize' Minimum size of the garbage collector's heap before it begins bothering to collect garbage. The first collection occurs ! after the heap expands by 'ggc-min-expand'% beyond ! 'ggc-min-heapsize'. Again, tuning this may improve compilation speed, and has no effect on code generation. The default is the smaller of RAM/8, RLIMIT_RSS, or a limit --- 8438,8457 ---- compilation speed; it has no effect on code generation. The default is 30% + 70% * (RAM/1GB) with an upper bound of ! 100% when RAM >= 1GB. If `getrlimit' is available, the ! notion of "RAM" is the smallest of actual RAM and ! `RLIMIT_DATA' or `RLIMIT_AS'. If GCC is not able to ! calculate RAM on a particular platform, the lower bound of ! 30% is used. Setting this parameter and `ggc-min-heapsize' ! to zero causes a full collection to occur at every ! opportunity. This is extremely slow, but can be useful for ! debugging. + `ggc-min-heapsize' Minimum size of the garbage collector's heap before it begins bothering to collect garbage. The first collection occurs ! after the heap expands by `ggc-min-expand'% beyond ! `ggc-min-heapsize'. Again, tuning this may improve compilation speed, and has no effect on code generation. The default is the smaller of RAM/8, RLIMIT_RSS, or a limit *************** includes experimental options that may p *** 8417,8570 **** to calculate RAM on a particular platform, the lower bound is used. Setting this parameter very large effectively disables garbage collection. Setting this parameter and ! 'ggc-min-expand' to zero causes a full collection to occur at every opportunity. ! 'max-reload-search-insns' The maximum number of instruction reload should look backward for equivalent register. Increasing values mean more aggressive optimization, making the compilation time increase with probably slightly better performance. The default value is 100. ! 'max-cselib-memory-locations' ! The maximum number of memory locations cselib should take into ! account. Increasing values mean more aggressive optimization, ! making the compilation time increase with probably slightly ! better performance. The default value is 500. ! 'max-sched-ready-insns' The maximum number of instructions ready to be issued the scheduler should consider at any given time during the first scheduling pass. Increasing values mean more thorough searches, making the compilation time increase with probably little benefit. The default value is 100. ! 'max-sched-region-blocks' The maximum number of blocks in a region to be considered for interblock scheduling. The default value is 10. ! 'max-pipeline-region-blocks' The maximum number of blocks in a region to be considered for pipelining in the selective scheduler. The default value is 15. ! 'max-sched-region-insns' The maximum number of insns in a region to be considered for interblock scheduling. The default value is 100. ! 'max-pipeline-region-insns' The maximum number of insns in a region to be considered for pipelining in the selective scheduler. The default value is 200. ! 'min-spec-prob' The minimum probability (in percents) of reaching a source block for interblock speculative scheduling. The default value is 40. ! 'max-sched-extend-regions-iters' The maximum number of iterations through CFG to extend regions. A value of 0 (the default) disables region extensions. ! 'max-sched-insn-conflict-delay' The maximum conflict delay for an insn to be considered for speculative motion. The default value is 3. ! 'sched-spec-prob-cutoff' The minimal probability of speculation success (in percents), ! so that speculative insns are scheduled. The default value is ! 40. ! 'sched-state-edge-prob-cutoff' ! The minimum probability an edge must have for the scheduler to ! save its state across it. The default value is 10. ! 'sched-mem-true-dep-cost' Minimal distance (in CPU cycles) between store and load targeting same memory locations. The default value is 1. ! 'selsched-max-lookahead' The maximum size of the lookahead window of selective scheduling. It is a depth of search for available instructions. The default value is 50. ! 'selsched-max-sched-times' The maximum number of times that an instruction is scheduled during selective scheduling. This is the limit on the number of iterations through which the instruction may be pipelined. The default value is 2. ! 'selsched-insns-to-rename' ! The maximum number of best instructions in the ready list that ! are considered for renaming in the selective scheduler. The ! default value is 2. ! 'sms-min-sc' The minimum value of stage count that swing modulo scheduler generates. The default value is 2. ! 'max-last-value-rtl' The maximum size measured as number of RTLs that can be ! recorded in an expression in combiner for a pseudo register as ! last known value of that register. The default is 10000. ! 'max-combine-insns' The maximum number of instructions the RTL combiner tries to ! combine. The default value is 2 at '-Og' and 4 otherwise. ! 'integer-share-limit' Small integer constants can use a shared data structure, ! reducing the compiler's memory usage and increasing its speed. ! This sets the maximum value of a shared integer constant. The ! default value is 256. ! 'ssp-buffer-size' The minimum size of buffers (i.e. arrays) that receive stack ! smashing protection when '-fstack-protection' is used. ! 'min-size-for-stack-sharing' The minimum size of variables taking part in stack slot ! sharing when not optimizing. The default value is 32. ! 'max-jump-thread-duplication-stmts' Maximum number of statements allowed in a block that needs to be duplicated when threading jumps. ! 'max-fields-for-field-sensitive' Maximum number of fields in a structure treated in a field sensitive manner during pointer analysis. The default is zero ! for '-O0' and '-O1', and 100 for '-Os', '-O2', and '-O3'. ! 'prefetch-latency' Estimate on average number of instructions that are executed before prefetch finishes. The distance prefetched ahead is proportional to this constant. Increasing this number may also lead to less streams being prefetched (see ! 'simultaneous-prefetches'). ! 'simultaneous-prefetches' Maximum number of prefetches that can run at the same time. ! 'l1-cache-line-size' The size of cache line in L1 cache, in bytes. ! 'l1-cache-size' The size of L1 cache, in kilobytes. ! 'l2-cache-size' The size of L2 cache, in kilobytes. ! 'min-insn-to-prefetch-ratio' The minimum ratio between the number of instructions and the number of prefetches to enable prefetching in a loop. ! 'prefetch-min-insn-to-mem-ratio' The minimum ratio between the number of instructions and the number of memory references to enable prefetching in a loop. ! 'use-canonical-types' Whether the compiler should use the "canonical" type system. By default, this should always be 1, which uses a more efficient internal mechanism for comparing types in C++ and --- 8461,8615 ---- to calculate RAM on a particular platform, the lower bound is used. Setting this parameter very large effectively disables garbage collection. Setting this parameter and ! `ggc-min-expand' to zero causes a full collection to occur at every opportunity. ! `max-reload-search-insns' The maximum number of instruction reload should look backward for equivalent register. Increasing values mean more aggressive optimization, making the compilation time increase with probably slightly better performance. The default value is 100. ! `max-cselib-memory-locations' ! The maximum number of memory locations cselib should take ! into account. Increasing values mean more aggressive ! optimization, making the compilation time increase with ! probably slightly better performance. The default value is ! 500. ! `max-sched-ready-insns' The maximum number of instructions ready to be issued the scheduler should consider at any given time during the first scheduling pass. Increasing values mean more thorough searches, making the compilation time increase with probably little benefit. The default value is 100. ! `max-sched-region-blocks' The maximum number of blocks in a region to be considered for interblock scheduling. The default value is 10. ! `max-pipeline-region-blocks' The maximum number of blocks in a region to be considered for pipelining in the selective scheduler. The default value is 15. ! `max-sched-region-insns' The maximum number of insns in a region to be considered for interblock scheduling. The default value is 100. ! `max-pipeline-region-insns' The maximum number of insns in a region to be considered for pipelining in the selective scheduler. The default value is 200. ! `min-spec-prob' The minimum probability (in percents) of reaching a source block for interblock speculative scheduling. The default value is 40. ! `max-sched-extend-regions-iters' The maximum number of iterations through CFG to extend regions. A value of 0 (the default) disables region extensions. ! `max-sched-insn-conflict-delay' The maximum conflict delay for an insn to be considered for speculative motion. The default value is 3. ! `sched-spec-prob-cutoff' The minimal probability of speculation success (in percents), ! so that speculative insns are scheduled. The default value ! is 40. ! `sched-state-edge-prob-cutoff' ! The minimum probability an edge must have for the scheduler ! to save its state across it. The default value is 10. ! `sched-mem-true-dep-cost' Minimal distance (in CPU cycles) between store and load targeting same memory locations. The default value is 1. ! `selsched-max-lookahead' The maximum size of the lookahead window of selective scheduling. It is a depth of search for available instructions. The default value is 50. ! `selsched-max-sched-times' The maximum number of times that an instruction is scheduled during selective scheduling. This is the limit on the number of iterations through which the instruction may be pipelined. The default value is 2. ! `selsched-insns-to-rename' ! The maximum number of best instructions in the ready list ! that are considered for renaming in the selective scheduler. ! The default value is 2. ! `sms-min-sc' The minimum value of stage count that swing modulo scheduler generates. The default value is 2. ! `max-last-value-rtl' The maximum size measured as number of RTLs that can be ! recorded in an expression in combiner for a pseudo register ! as last known value of that register. The default is 10000. ! `max-combine-insns' The maximum number of instructions the RTL combiner tries to ! combine. The default value is 2 at `-Og' and 4 otherwise. ! `integer-share-limit' Small integer constants can use a shared data structure, ! reducing the compiler's memory usage and increasing its ! speed. This sets the maximum value of a shared integer ! constant. The default value is 256. ! `ssp-buffer-size' The minimum size of buffers (i.e. arrays) that receive stack ! smashing protection when `-fstack-protection' is used. ! `min-size-for-stack-sharing' The minimum size of variables taking part in stack slot ! sharing when not optimizing. The default value is 32. ! `max-jump-thread-duplication-stmts' Maximum number of statements allowed in a block that needs to be duplicated when threading jumps. ! `max-fields-for-field-sensitive' Maximum number of fields in a structure treated in a field sensitive manner during pointer analysis. The default is zero ! for `-O0' and `-O1', and 100 for `-Os', `-O2', and `-O3'. ! `prefetch-latency' Estimate on average number of instructions that are executed before prefetch finishes. The distance prefetched ahead is proportional to this constant. Increasing this number may also lead to less streams being prefetched (see ! `simultaneous-prefetches'). ! `simultaneous-prefetches' Maximum number of prefetches that can run at the same time. ! `l1-cache-line-size' The size of cache line in L1 cache, in bytes. ! `l1-cache-size' The size of L1 cache, in kilobytes. ! `l2-cache-size' The size of L2 cache, in kilobytes. ! `min-insn-to-prefetch-ratio' The minimum ratio between the number of instructions and the number of prefetches to enable prefetching in a loop. ! `prefetch-min-insn-to-mem-ratio' The minimum ratio between the number of instructions and the number of memory references to enable prefetching in a loop. ! `use-canonical-types' Whether the compiler should use the "canonical" type system. By default, this should always be 1, which uses a more efficient internal mechanism for comparing types in C++ and *************** includes experimental options that may p *** 8572,8586 **** are causing compilation failures, set this value to 0 to disable canonical types. ! 'switch-conversion-max-branch-ratio' ! Switch initialization conversion refuses to create arrays that ! are bigger than 'switch-conversion-max-branch-ratio' times the ! number of branches in the switch. ! 'max-partial-antic-length' Maximum length of the partial antic set computed during the tree partial redundancy elimination optimization ! ('-ftree-pre') when optimizing at '-O3' and above. For some sorts of source code the enhanced partial redundancy elimination optimization can run away, consuming all of the memory available on the host machine. This parameter sets a --- 8617,8631 ---- are causing compilation failures, set this value to 0 to disable canonical types. ! `switch-conversion-max-branch-ratio' ! Switch initialization conversion refuses to create arrays ! that are bigger than `switch-conversion-max-branch-ratio' ! times the number of branches in the switch. ! `max-partial-antic-length' Maximum length of the partial antic set computed during the tree partial redundancy elimination optimization ! (`-ftree-pre') when optimizing at `-O3' and above. For some sorts of source code the enhanced partial redundancy elimination optimization can run away, consuming all of the memory available on the host machine. This parameter sets a *************** includes experimental options that may p *** 8588,8616 **** prevents the runaway behavior. Setting a value of 0 for this parameter allows an unlimited set length. ! 'sccvn-max-scc-size' Maximum size of a strongly connected component (SCC) during SCCVN processing. If this limit is hit, SCCVN processing for the whole function is not done and optimizations depending on it are disabled. The default maximum SCC size is 10000. ! 'sccvn-max-alias-queries-per-access' ! Maximum number of alias-oracle queries we perform when looking ! for redundancies for loads and stores. If this limit is hit ! the search is aborted and the load or store is not considered ! redundant. The number of queries is algorithmically limited ! to the number of stores on all paths from the load to the ! function entry. The default maximum number of queries is ! 1000. ! 'ira-max-loops-num' IRA uses regional register allocation by default. If a function contains more loops than the number given by this parameter, only at most the given number of the most frequently-executed loops form regions for regional register allocation. The default value of the parameter is 100. ! 'ira-max-conflict-table-size' Although IRA uses a sophisticated algorithm to compress the conflict table, the table can still require excessive amounts of memory for huge functions. If the conflict table for a --- 8633,8661 ---- prevents the runaway behavior. Setting a value of 0 for this parameter allows an unlimited set length. ! `sccvn-max-scc-size' Maximum size of a strongly connected component (SCC) during SCCVN processing. If this limit is hit, SCCVN processing for the whole function is not done and optimizations depending on it are disabled. The default maximum SCC size is 10000. ! `sccvn-max-alias-queries-per-access' ! Maximum number of alias-oracle queries we perform when ! looking for redundancies for loads and stores. If this limit ! is hit the search is aborted and the load or store is not ! considered redundant. The number of queries is ! algorithmically limited to the number of stores on all paths ! from the load to the function entry. The default maximum ! number of queries is 1000. ! `ira-max-loops-num' IRA uses regional register allocation by default. If a function contains more loops than the number given by this parameter, only at most the given number of the most frequently-executed loops form regions for regional register allocation. The default value of the parameter is 100. ! `ira-max-conflict-table-size' Although IRA uses a sophisticated algorithm to compress the conflict table, the table can still require excessive amounts of memory for huge functions. If the conflict table for a *************** includes experimental options that may p *** 8620,8669 **** building a pseudo-register conflict table. The default value of the parameter is 2000. ! 'ira-loop-reserved-regs' ! IRA can be used to evaluate more accurate register pressure in ! loops for decisions to move loop invariants (see '-O3'). The ! number of available registers reserved for some other purposes ! is given by this parameter. The default value of the ! parameter is 2, which is the minimal number of registers needed by typical instructions. This value is the best found from numerous experiments. ! 'lra-inheritance-ebb-probability-cutoff' LRA tries to reuse values reloaded in registers in subsequent insns. This optimization is called inheritance. EBB is used as a region to do this optimization. The parameter defines a minimal fall-through edge probability in percentage used to ! add BB to inheritance EBB in LRA. The default value of the parameter is 40. The value was chosen from numerous runs of SPEC2000 on x86-64. ! 'loop-invariant-max-bbs-in-loop' Loop invariant motion can be very expensive, both in compilation time and in amount of needed compile-time memory, ! with very large loops. Loops with more basic blocks than this ! parameter won't have loop invariant motion optimization ! performed on them. The default value of the parameter is 1000 ! for '-O1' and 10000 for '-O2' and above. ! 'loop-max-datarefs-for-datadeps' Building data dependencies is expensive for very large loops. This parameter limits the number of data references in loops ! that are considered for data dependence analysis. These large ! loops are no handled by the optimizations using loop data ! dependencies. The default value is 1000. ! 'max-vartrack-size' Sets a maximum number of hash table slots to use during variable tracking dataflow analysis of any function. If this limit is exceeded with variable tracking at assignments enabled, analysis for that function is retried without it, after removing all debug insns from the function. If the limit is exceeded even without debug insns, var tracking ! analysis is completely disabled for the function. Setting the ! parameter to zero makes it unlimited. ! 'max-vartrack-expr-depth' Sets a maximum number of recursion levels when attempting to map variable names or debug temporaries to value expressions. This trades compilation time for more complete debug --- 8665,8714 ---- building a pseudo-register conflict table. The default value of the parameter is 2000. ! `ira-loop-reserved-regs' ! IRA can be used to evaluate more accurate register pressure ! in loops for decisions to move loop invariants (see `-O3'). ! The number of available registers reserved for some other ! purposes is given by this parameter. The default value of ! the parameter is 2, which is the minimal number of registers needed by typical instructions. This value is the best found from numerous experiments. ! `lra-inheritance-ebb-probability-cutoff' LRA tries to reuse values reloaded in registers in subsequent insns. This optimization is called inheritance. EBB is used as a region to do this optimization. The parameter defines a minimal fall-through edge probability in percentage used to ! add BB to inheritance EBB in LRA. The default value of the parameter is 40. The value was chosen from numerous runs of SPEC2000 on x86-64. ! `loop-invariant-max-bbs-in-loop' Loop invariant motion can be very expensive, both in compilation time and in amount of needed compile-time memory, ! with very large loops. Loops with more basic blocks than ! this parameter won't have loop invariant motion optimization ! performed on them. The default value of the parameter is ! 1000 for `-O1' and 10000 for `-O2' and above. ! `loop-max-datarefs-for-datadeps' Building data dependencies is expensive for very large loops. This parameter limits the number of data references in loops ! that are considered for data dependence analysis. These ! large loops are no handled by the optimizations using loop ! data dependencies. The default value is 1000. ! `max-vartrack-size' Sets a maximum number of hash table slots to use during variable tracking dataflow analysis of any function. If this limit is exceeded with variable tracking at assignments enabled, analysis for that function is retried without it, after removing all debug insns from the function. If the limit is exceeded even without debug insns, var tracking ! analysis is completely disabled for the function. Setting ! the parameter to zero makes it unlimited. ! `max-vartrack-expr-depth' Sets a maximum number of recursion levels when attempting to map variable names or debug temporaries to value expressions. This trades compilation time for more complete debug *************** includes experimental options that may p *** 8673,8929 **** compiler to find more complex debug expressions, but compile time and memory use may grow. The default is 12. ! 'min-nondebug-insn-uid' Use uids starting at this parameter for nondebug insns. The range below the parameter is reserved exclusively for debug ! insns created by '-fvar-tracking-assignments', but debug insns ! may get (non-overlapping) uids above it if the reserved range ! is exhausted. ! 'ipa-sra-ptr-growth-factor' IPA-SRA replaces a pointer to an aggregate with one or more new parameters only when their cumulative size is less or ! equal to 'ipa-sra-ptr-growth-factor' times the size of the original pointer parameter. ! 'sra-max-scalarization-size-Ospeed' ! 'sra-max-scalarization-size-Osize' The two Scalar Reduction of Aggregates passes (SRA and IPA-SRA) aim to replace scalar parts of aggregates with uses ! of independent scalar variables. These parameters control the ! maximum size, in storage units, of aggregate which is considered for replacement when compiling for speed ! ('sra-max-scalarization-size-Ospeed') or size ! ('sra-max-scalarization-size-Osize') respectively. ! 'tm-max-aggregate-size' ! When making copies of thread-local variables in a transaction, ! this parameter specifies the size in bytes after which ! variables are saved with the logging functions as opposed to ! save/restore code sequence pairs. This option only applies ! when using '-fgnu-tm'. ! 'graphite-max-nb-scop-params' To avoid exponential effects in the Graphite loop transforms, the number of parameters in a Static Control Part (SCoP) is bounded. The default value is 10 parameters. A variable ! whose value is unknown at compilation time and defined outside ! a SCoP is a parameter of the SCoP. ! 'graphite-max-bbs-per-function' To avoid exponential effects in the detection of SCoPs, the size of the functions analyzed by Graphite is bounded. The default value is 100 basic blocks. ! 'loop-block-tile-size' Loop blocking or strip mining transforms, enabled with ! '-floop-block' or '-floop-strip-mine', strip mine each loop in ! the loop nest by a given number of iterations. The strip ! length can be changed using the 'loop-block-tile-size' parameter. The default value is 51 iterations. ! 'loop-unroll-jam-size' ! Specify the unroll factor for the '-floop-unroll-and-jam' option. The default value is 4. ! 'loop-unroll-jam-depth' Specify the dimension to be unrolled (counting from the most ! inner loop) for the '-floop-unroll-and-jam'. The default value is 2. ! 'ipa-cp-value-list-size' IPA-CP attempts to track all possible values and types passed to a function's parameter in order to propagate them and ! perform devirtualization. 'ipa-cp-value-list-size' is the maximum number of values and types it stores per one formal parameter of a function. ! 'ipa-cp-eval-threshold' IPA-CP calculates its own score of cloning profitability heuristics and performs those cloning opportunities with ! scores that exceed 'ipa-cp-eval-threshold'. ! 'ipa-cp-recursion-penalty' Percentage penalty the recursive functions will receive when they are evaluated for cloning. ! 'ipa-cp-single-call-penalty' Percentage penalty functions containg a single call to another function will receive when they are evaluated for cloning. ! 'ipa-max-agg-items' IPA-CP is also capable to propagate a number of scalar values ! passed in an aggregate. 'ipa-max-agg-items' controls the maximum number of such values per one parameter. ! 'ipa-cp-loop-hint-bonus' ! When IPA-CP determines that a cloning candidate would make the ! number of iterations of a loop known, it adds a bonus of ! 'ipa-cp-loop-hint-bonus' to the profitability score of the candidate. ! 'ipa-cp-array-index-hint-bonus' ! When IPA-CP determines that a cloning candidate would make the ! index of an array access known, it adds a bonus of ! 'ipa-cp-array-index-hint-bonus' to the profitability score of the candidate. ! 'ipa-max-aa-steps' During its analysis of function bodies, IPA-CP employs alias analysis in order to track values pointed to by function parameters. In order not spend too much time analyzing huge ! functions, it gives up and consider all memory clobbered after ! examining 'ipa-max-aa-steps' statements modifying memory. ! 'lto-partitions' Specify desired number of partitions produced during WHOPR compilation. The number of partitions should exceed the number of CPUs used for compilation. The default value is 32. ! 'lto-min-partition' Size of minimal partition for WHOPR (in estimated ! instructions). This prevents expenses of splitting very small ! programs into too many partitions. ! 'cxx-max-namespaces-for-diagnostic-help' The maximum number of namespaces to consult for suggestions when C++ name lookup fails for an identifier. The default is 1000. ! 'sink-frequency-threshold' The maximum relative execution frequency (in percents) of the ! target block relative to a statement's original block to allow ! statement sinking of a statement. Larger numbers result in ! more aggressive statement sinking. The default value is 75. ! A small positive adjustment is applied for statements with ! memory operands as those are even more profitable so sink. ! 'max-stores-to-sink' The maximum number of conditional store pairs that can be ! sunk. Set to 0 if either vectorization ('-ftree-vectorize') ! or if-conversion ('-ftree-loop-if-convert') is disabled. The default is 2. ! 'allow-store-data-races' Allow optimizers to introduce new data races on stores. Set to 1 to allow, otherwise to 0. This option is enabled by ! default at optimization level '-Ofast'. ! 'case-values-threshold' The smallest number of different values for which it is best ! to use a jump-table instead of a tree of conditional branches. ! If the value is 0, use the default for the machine. The ! default is 0. ! 'tree-reassoc-width' Set the maximum number of instructions executed in parallel in ! reassociated tree. This parameter overrides target dependent heuristics used by default if has non zero value. ! 'sched-pressure-algorithm' Choose between the two available implementations of ! '-fsched-pressure'. Algorithm 1 is the original implementation and is the more likely to prevent instructions from being reordered. Algorithm 2 was designed to be a compromise between the relatively conservative approach taken ! by algorithm 1 and the rather aggressive approach taken by the ! default scheduler. It relies more heavily on having a regular ! register file and accurate register pressure classes. See ! 'haifa-sched.c' in the GCC sources for more details. The default choice depends on the target. ! 'max-slsr-cand-scan' Set the maximum number of existing candidates that are considered when seeking a basis for a new straight-line strength reduction candidate. ! 'asan-globals' Enable buffer overflow detection for global objects. This kind of protection is enabled by default if you are using ! '-fsanitize=address' option. To disable global objects ! protection use '--param asan-globals=0'. ! 'asan-stack' ! Enable buffer overflow detection for stack objects. This kind ! of protection is enabled by default when using ! '-fsanitize=address'. To disable stack protection use ! '--param asan-stack=0' option. ! 'asan-instrument-reads' Enable buffer overflow detection for memory reads. This kind of protection is enabled by default when using ! '-fsanitize=address'. To disable memory reads protection use ! '--param asan-instrument-reads=0'. ! 'asan-instrument-writes' ! Enable buffer overflow detection for memory writes. This kind ! of protection is enabled by default when using ! '-fsanitize=address'. To disable memory writes protection use ! '--param asan-instrument-writes=0' option. ! 'asan-memintrin' Enable detection for built-in functions. This kind of protection is enabled by default when using ! '-fsanitize=address'. To disable built-in functions ! protection use '--param asan-memintrin=0'. ! 'asan-use-after-return' Enable detection of use-after-return. This kind of protection ! is enabled by default when using '-fsanitize=address' option. ! To disable use-after-return detection use '--param asan-use-after-return=0'. ! 'asan-instrumentation-with-call-threshold' ! If number of memory accesses in function being instrumented is ! greater or equal to this number, use callbacks instead of ! inline checks. E.g. to disable inline code use '--param asan-instrumentation-with-call-threshold=0'. ! 'chkp-max-ctor-size' Static constructors generated by Pointer Bounds Checker may become very large and significantly increase compile time at ! optimization level '-O1' and higher. This parameter is a maximum nubmer of statements in a single generated constructor. Default value is 5000. ! 'max-fsm-thread-path-insns' ! Maximum number of instructions to copy when duplicating blocks ! on a finite state automaton jump thread path. The default is ! 100. ! 'max-fsm-thread-length' Maximum number of basic blocks on a finite state automaton jump thread path. The default is 10. ! 'max-fsm-thread-paths' ! Maximum number of new jump thread paths to create for a finite ! state automaton. The default is 50. ! 'parloops-chunk-size' ! Chunk size of omp schedule for loops parallelized by parloops. ! The default is 0. ! 'parloops-schedule' Schedule type of omp schedule for loops parallelized by parloops (static, dynamic, guided, auto, runtime). The default is static. ! 'max-ssa-name-query-depth' Maximum depth of recursion when querying properties of SSA names in things like fold routines. One level of recursion corresponds to following a use-def chain. ! 'hsa-gen-debug-stores' Enable emission of special debug stores within HSA kernels which are then read and reported by libgomp plugin. Generation of these stores is disabled by default, use ! '--param hsa-gen-debug-stores=1' to enable it. ! 'max-speculative-devirt-maydefs' The maximum number of may-defs we analyze when looking for a ! must-def specifying the dynamic type of an object that invokes ! a virtual call we may be able to devirtualize speculatively.  File: gcc.info, Node: Instrumentation Options, Next: Preprocessor Options, Prev: Optimize Options, Up: Invoking GCC --- 8718,8978 ---- compiler to find more complex debug expressions, but compile time and memory use may grow. The default is 12. ! `min-nondebug-insn-uid' Use uids starting at this parameter for nondebug insns. The range below the parameter is reserved exclusively for debug ! insns created by `-fvar-tracking-assignments', but debug ! insns may get (non-overlapping) uids above it if the reserved ! range is exhausted. ! `ipa-sra-ptr-growth-factor' IPA-SRA replaces a pointer to an aggregate with one or more new parameters only when their cumulative size is less or ! equal to `ipa-sra-ptr-growth-factor' times the size of the original pointer parameter. ! `sra-max-scalarization-size-Ospeed' ! ! `sra-max-scalarization-size-Osize' The two Scalar Reduction of Aggregates passes (SRA and IPA-SRA) aim to replace scalar parts of aggregates with uses ! of independent scalar variables. These parameters control ! the maximum size, in storage units, of aggregate which is considered for replacement when compiling for speed ! (`sra-max-scalarization-size-Ospeed') or size ! (`sra-max-scalarization-size-Osize') respectively. ! `tm-max-aggregate-size' ! When making copies of thread-local variables in a ! transaction, this parameter specifies the size in bytes after ! which variables are saved with the logging functions as ! opposed to save/restore code sequence pairs. This option ! only applies when using `-fgnu-tm'. ! `graphite-max-nb-scop-params' To avoid exponential effects in the Graphite loop transforms, the number of parameters in a Static Control Part (SCoP) is bounded. The default value is 10 parameters. A variable ! whose value is unknown at compilation time and defined ! outside a SCoP is a parameter of the SCoP. ! `graphite-max-bbs-per-function' To avoid exponential effects in the detection of SCoPs, the size of the functions analyzed by Graphite is bounded. The default value is 100 basic blocks. ! `loop-block-tile-size' Loop blocking or strip mining transforms, enabled with ! `-floop-block' or `-floop-strip-mine', strip mine each loop ! in the loop nest by a given number of iterations. The strip ! length can be changed using the `loop-block-tile-size' parameter. The default value is 51 iterations. ! `loop-unroll-jam-size' ! Specify the unroll factor for the `-floop-unroll-and-jam' option. The default value is 4. ! `loop-unroll-jam-depth' Specify the dimension to be unrolled (counting from the most ! inner loop) for the `-floop-unroll-and-jam'. The default value is 2. ! `ipa-cp-value-list-size' IPA-CP attempts to track all possible values and types passed to a function's parameter in order to propagate them and ! perform devirtualization. `ipa-cp-value-list-size' is the maximum number of values and types it stores per one formal parameter of a function. ! `ipa-cp-eval-threshold' IPA-CP calculates its own score of cloning profitability heuristics and performs those cloning opportunities with ! scores that exceed `ipa-cp-eval-threshold'. ! `ipa-cp-recursion-penalty' Percentage penalty the recursive functions will receive when they are evaluated for cloning. ! `ipa-cp-single-call-penalty' Percentage penalty functions containg a single call to another function will receive when they are evaluated for cloning. ! `ipa-max-agg-items' IPA-CP is also capable to propagate a number of scalar values ! passed in an aggregate. `ipa-max-agg-items' controls the maximum number of such values per one parameter. ! `ipa-cp-loop-hint-bonus' ! When IPA-CP determines that a cloning candidate would make ! the number of iterations of a loop known, it adds a bonus of ! `ipa-cp-loop-hint-bonus' to the profitability score of the candidate. ! `ipa-cp-array-index-hint-bonus' ! When IPA-CP determines that a cloning candidate would make ! the index of an array access known, it adds a bonus of ! `ipa-cp-array-index-hint-bonus' to the profitability score of the candidate. ! `ipa-max-aa-steps' During its analysis of function bodies, IPA-CP employs alias analysis in order to track values pointed to by function parameters. In order not spend too much time analyzing huge ! functions, it gives up and consider all memory clobbered ! after examining `ipa-max-aa-steps' statements modifying ! memory. ! `lto-partitions' Specify desired number of partitions produced during WHOPR compilation. The number of partitions should exceed the number of CPUs used for compilation. The default value is 32. ! `lto-min-partition' Size of minimal partition for WHOPR (in estimated ! instructions). This prevents expenses of splitting very ! small programs into too many partitions. ! `cxx-max-namespaces-for-diagnostic-help' The maximum number of namespaces to consult for suggestions when C++ name lookup fails for an identifier. The default is 1000. ! `sink-frequency-threshold' The maximum relative execution frequency (in percents) of the ! target block relative to a statement's original block to ! allow statement sinking of a statement. Larger numbers ! result in more aggressive statement sinking. The default ! value is 75. A small positive adjustment is applied for ! statements with memory operands as those are even more ! profitable so sink. ! `max-stores-to-sink' The maximum number of conditional store pairs that can be ! sunk. Set to 0 if either vectorization (`-ftree-vectorize') ! or if-conversion (`-ftree-loop-if-convert') is disabled. The default is 2. ! `allow-store-data-races' Allow optimizers to introduce new data races on stores. Set to 1 to allow, otherwise to 0. This option is enabled by ! default at optimization level `-Ofast'. ! `case-values-threshold' The smallest number of different values for which it is best ! to use a jump-table instead of a tree of conditional ! branches. If the value is 0, use the default for the ! machine. The default is 0. ! `tree-reassoc-width' Set the maximum number of instructions executed in parallel in ! reassociated tree. This parameter overrides target dependent heuristics used by default if has non zero value. ! `sched-pressure-algorithm' Choose between the two available implementations of ! `-fsched-pressure'. Algorithm 1 is the original implementation and is the more likely to prevent instructions from being reordered. Algorithm 2 was designed to be a compromise between the relatively conservative approach taken ! by algorithm 1 and the rather aggressive approach taken by ! the default scheduler. It relies more heavily on having a ! regular register file and accurate register pressure classes. ! See `haifa-sched.c' in the GCC sources for more details. The default choice depends on the target. ! `max-slsr-cand-scan' Set the maximum number of existing candidates that are considered when seeking a basis for a new straight-line strength reduction candidate. ! `asan-globals' Enable buffer overflow detection for global objects. This kind of protection is enabled by default if you are using ! `-fsanitize=address' option. To disable global objects ! protection use `--param asan-globals=0'. ! `asan-stack' ! Enable buffer overflow detection for stack objects. This ! kind of protection is enabled by default when using ! `-fsanitize=address'. To disable stack protection use ! `--param asan-stack=0' option. ! `asan-instrument-reads' Enable buffer overflow detection for memory reads. This kind of protection is enabled by default when using ! `-fsanitize=address'. To disable memory reads protection use ! `--param asan-instrument-reads=0'. ! `asan-instrument-writes' ! Enable buffer overflow detection for memory writes. This ! kind of protection is enabled by default when using ! `-fsanitize=address'. To disable memory writes protection use ! `--param asan-instrument-writes=0' option. ! `asan-memintrin' Enable detection for built-in functions. This kind of protection is enabled by default when using ! `-fsanitize=address'. To disable built-in functions ! protection use `--param asan-memintrin=0'. ! `asan-use-after-return' Enable detection of use-after-return. This kind of protection ! is enabled by default when using `-fsanitize=address' option. ! To disable use-after-return detection use `--param asan-use-after-return=0'. ! `asan-instrumentation-with-call-threshold' ! If number of memory accesses in function being instrumented ! is greater or equal to this number, use callbacks instead of ! inline checks. E.g. to disable inline code use `--param asan-instrumentation-with-call-threshold=0'. ! `chkp-max-ctor-size' Static constructors generated by Pointer Bounds Checker may become very large and significantly increase compile time at ! optimization level `-O1' and higher. This parameter is a maximum nubmer of statements in a single generated constructor. Default value is 5000. ! `max-fsm-thread-path-insns' ! Maximum number of instructions to copy when duplicating ! blocks on a finite state automaton jump thread path. The ! default is 100. ! `max-fsm-thread-length' Maximum number of basic blocks on a finite state automaton jump thread path. The default is 10. ! `max-fsm-thread-paths' ! Maximum number of new jump thread paths to create for a ! finite state automaton. The default is 50. ! `parloops-chunk-size' ! Chunk size of omp schedule for loops parallelized by ! parloops. The default is 0. ! `parloops-schedule' Schedule type of omp schedule for loops parallelized by parloops (static, dynamic, guided, auto, runtime). The default is static. ! `max-ssa-name-query-depth' Maximum depth of recursion when querying properties of SSA names in things like fold routines. One level of recursion corresponds to following a use-def chain. ! `hsa-gen-debug-stores' Enable emission of special debug stores within HSA kernels which are then read and reported by libgomp plugin. Generation of these stores is disabled by default, use ! `--param hsa-gen-debug-stores=1' to enable it. ! `max-speculative-devirt-maydefs' The maximum number of may-defs we analyze when looking for a ! must-def specifying the dynamic type of an object that ! invokes a virtual call we may be able to devirtualize ! speculatively.  File: gcc.info, Node: Instrumentation Options, Next: Preprocessor Options, Prev: Optimize Options, Up: Invoking GCC *************** hijacking. There is also a general hook *** 8943,9113 **** other forms of tracing or function-level instrumentation for debug or program analysis purposes. ! '-p' Generate extra code to write profile information suitable for the ! analysis program 'prof'. You must use this option when compiling the source files you want data about, and you must also use it when linking. ! '-pg' Generate extra code to write profile information suitable for the ! analysis program 'gprof'. You must use this option when compiling the source files you want data about, and you must also use it when linking. ! '-fprofile-arcs' Add code so that program flow "arcs" are instrumented. During execution the program records how many times each branch and call is executed and how many times it is taken or returns. When the compiled program exits it saves this data to a file called ! 'AUXNAME.gcda' for each source file. The data may be used for ! profile-directed optimizations ('-fbranch-probabilities'), or for ! test coverage analysis ('-ftest-coverage'). Each object file's AUXNAME is generated from the name of the output file, if explicitly specified and it is not the final executable, otherwise ! it is the basename of the source file. In both cases any suffix is ! removed (e.g. 'foo.gcda' for input file 'dir/foo.c', or ! 'dir/foo.gcda' for output file specified as '-o dir/foo.o'). *Note ! Cross-profiling::. ! ! '--coverage' This option is used to compile and link code instrumented for ! coverage analysis. The option is a synonym for '-fprofile-arcs' ! '-ftest-coverage' (when compiling) and '-lgcov' (when linking). See the documentation for those options for more details. ! * Compile the source files with '-fprofile-arcs' plus optimization and code generation options. For test coverage ! analysis, use the additional '-ftest-coverage' option. You do ! not need to profile every source file in a program. ! * Link your object files with '-lgcov' or '-fprofile-arcs' (the latter implies the former). * Run the program on a representative workload to generate the arc profile information. This may be repeated any number of times. You can run concurrent instances of your program, and ! provided that the file system supports locking, the data files ! will be correctly updated. Also 'fork' calls are detected and ! correctly handled (double counting will not happen). * For profile-directed optimizations, compile the source files again with the same optimization and code generation options ! plus '-fbranch-probabilities' (*note Options that Control Optimization: Optimize Options.). ! * For test coverage analysis, use 'gcov' to produce human ! readable information from the '.gcno' and '.gcda' files. ! Refer to the 'gcov' documentation for further information. ! With '-fprofile-arcs', for each function of your program GCC creates a program flow graph, then finds a spanning tree for the graph. Only arcs that are not on the spanning tree have to be instrumented: the compiler adds code to count the number of times ! that these arcs are executed. When an arc is the only exit or only ! entrance to a block, the instrumentation code can be added to the ! block; otherwise, a new basic block must be created to hold the ! instrumentation code. ! '-ftest-coverage' ! Produce a notes file that the 'gcov' code-coverage utility (*note ! 'gcov'--a Test Coverage Program: Gcov.) can use to show program ! coverage. Each source file's note file is called 'AUXNAME.gcno'. ! Refer to the '-fprofile-arcs' option above for a description of AUXNAME and instructions on how to generate test coverage data. Coverage data matches the source files more closely if you do not optimize. ! '-fprofile-dir=PATH' ! Set the directory to search for the profile data files in to PATH. This option affects only the profile data generated by ! '-fprofile-generate', '-ftest-coverage', '-fprofile-arcs' and used ! by '-fprofile-use' and '-fbranch-probabilities' and its related options. Both absolute and relative paths can be used. By default, GCC uses the current directory as PATH, thus the profile data file appears in the same directory as the object file. ! '-fprofile-generate' ! '-fprofile-generate=PATH' ! Enable options usually used for instrumenting application to produce profile useful for later recompilation with profile ! feedback based optimization. You must use '-fprofile-generate' both when compiling and when linking your program. ! The following options are enabled: '-fprofile-arcs', ! '-fprofile-values', '-fvpt'. If PATH is specified, GCC looks at the PATH to find the profile ! feedback data files. See '-fprofile-dir'. ! To optimize the program based on the collected profile information, ! use '-fprofile-use'. *Note Optimize Options::, for more ! information. ! '-fsanitize=address' Enable AddressSanitizer, a fast memory error detector. Memory access instructions are instrumented to detect out-of-bounds and use-after-free bugs. See ! for more details. The run-time behavior can be influenced using the ! 'ASAN_OPTIONS' environment variable. When set to 'help=1', the ! available options are shown at startup of the instrumented program. ! See ! for a list of supported options. ! '-fsanitize=kernel-address' Enable AddressSanitizer for Linux kernel. See ! for more details. ! '-fsanitize=thread' Enable ThreadSanitizer, a fast data race detector. Memory access instructions are instrumented to detect data race bugs. See ! for ! more details. The run-time behavior can be influenced using the ! 'TSAN_OPTIONS' environment variable; see ! for a list of supported options. ! '-fsanitize=leak' Enable LeakSanitizer, a memory leak detector. This option only matters for linking of executables and if neither ! '-fsanitize=address' nor '-fsanitize=thread' is used. In that case ! the executable is linked against a library that overrides 'malloc' ! and other allocator functions. See ! for more details. The run-time behavior can be influenced using ! the 'LSAN_OPTIONS' environment variable. ! '-fsanitize=undefined' Enable UndefinedBehaviorSanitizer, a fast undefined behavior detector. Various computations are instrumented to detect undefined behavior at runtime. Current suboptions are: ! '-fsanitize=shift' This option enables checking that the result of a shift operation is not undefined. Note that what exactly is considered undefined differs slightly between C and C++, as well as between ISO C90 and C99, etc. ! '-fsanitize=integer-divide-by-zero' ! Detect integer division by zero as well as 'INT_MIN / -1' division. ! '-fsanitize=unreachable' With this option, the compiler turns the ! '__builtin_unreachable' call into a diagnostics message call ! instead. When reaching the '__builtin_unreachable' call, the behavior is undefined. ! '-fsanitize=vla-bound' ! This option instructs the compiler to check that the size of a ! variable length array is positive. ! '-fsanitize=null' This option enables pointer checking. Particularly, the application built with this option turned on will issue an error message when it tries to dereference a NULL pointer, or --- 8992,9161 ---- other forms of tracing or function-level instrumentation for debug or program analysis purposes. ! `-p' Generate extra code to write profile information suitable for the ! analysis program `prof'. You must use this option when compiling the source files you want data about, and you must also use it when linking. ! `-pg' Generate extra code to write profile information suitable for the ! analysis program `gprof'. You must use this option when compiling the source files you want data about, and you must also use it when linking. ! `-fprofile-arcs' Add code so that program flow "arcs" are instrumented. During execution the program records how many times each branch and call is executed and how many times it is taken or returns. When the compiled program exits it saves this data to a file called ! `AUXNAME.gcda' for each source file. The data may be used for ! profile-directed optimizations (`-fbranch-probabilities'), or for ! test coverage analysis (`-ftest-coverage'). Each object file's AUXNAME is generated from the name of the output file, if explicitly specified and it is not the final executable, otherwise ! it is the basename of the source file. In both cases any suffix ! is removed (e.g. `foo.gcda' for input file `dir/foo.c', or ! `dir/foo.gcda' for output file specified as `-o dir/foo.o'). ! *Note Cross-profiling::. + `--coverage' This option is used to compile and link code instrumented for ! coverage analysis. The option is a synonym for `-fprofile-arcs' ! `-ftest-coverage' (when compiling) and `-lgcov' (when linking). See the documentation for those options for more details. ! * Compile the source files with `-fprofile-arcs' plus optimization and code generation options. For test coverage ! analysis, use the additional `-ftest-coverage' option. You ! do not need to profile every source file in a program. ! * Link your object files with `-lgcov' or `-fprofile-arcs' (the latter implies the former). * Run the program on a representative workload to generate the arc profile information. This may be repeated any number of times. You can run concurrent instances of your program, and ! provided that the file system supports locking, the data ! files will be correctly updated. Also `fork' calls are ! detected and correctly handled (double counting will not ! happen). * For profile-directed optimizations, compile the source files again with the same optimization and code generation options ! plus `-fbranch-probabilities' (*note Options that Control Optimization: Optimize Options.). ! * For test coverage analysis, use `gcov' to produce human ! readable information from the `.gcno' and `.gcda' files. ! Refer to the `gcov' documentation for further information. ! ! With `-fprofile-arcs', for each function of your program GCC creates a program flow graph, then finds a spanning tree for the graph. Only arcs that are not on the spanning tree have to be instrumented: the compiler adds code to count the number of times ! that these arcs are executed. When an arc is the only exit or ! only entrance to a block, the instrumentation code can be added to ! the block; otherwise, a new basic block must be created to hold ! the instrumentation code. ! `-ftest-coverage' ! Produce a notes file that the `gcov' code-coverage utility (*note ! `gcov'--a Test Coverage Program: Gcov.) can use to show program ! coverage. Each source file's note file is called `AUXNAME.gcno'. ! Refer to the `-fprofile-arcs' option above for a description of AUXNAME and instructions on how to generate test coverage data. Coverage data matches the source files more closely if you do not optimize. ! `-fprofile-dir=PATH' Set the directory to search for the profile data files in to PATH. This option affects only the profile data generated by ! `-fprofile-generate', `-ftest-coverage', `-fprofile-arcs' and used ! by `-fprofile-use' and `-fbranch-probabilities' and its related options. Both absolute and relative paths can be used. By default, GCC uses the current directory as PATH, thus the profile data file appears in the same directory as the object file. ! `-fprofile-generate' ! `-fprofile-generate=PATH' Enable options usually used for instrumenting application to produce profile useful for later recompilation with profile ! feedback based optimization. You must use `-fprofile-generate' both when compiling and when linking your program. ! The following options are enabled: `-fprofile-arcs', ! `-fprofile-values', `-fvpt'. If PATH is specified, GCC looks at the PATH to find the profile ! feedback data files. See `-fprofile-dir'. ! To optimize the program based on the collected profile ! information, use `-fprofile-use'. *Note Optimize Options::, for ! more information. ! `-fsanitize=address' Enable AddressSanitizer, a fast memory error detector. Memory access instructions are instrumented to detect out-of-bounds and use-after-free bugs. See ! `https://github.com/google/sanitizers/wiki/AddressSanitizer' for more details. The run-time behavior can be influenced using the ! `ASAN_OPTIONS' environment variable. When set to `help=1', the ! available options are shown at startup of the instrumented ! program. See ! `https://github.com/google/sanitizers/wiki/AddressSanitizerFlags#run-time-flags' for a list of supported options. ! `-fsanitize=kernel-address' Enable AddressSanitizer for Linux kernel. See ! `https://github.com/google/kasan/wiki' for more details. ! `-fsanitize=thread' Enable ThreadSanitizer, a fast data race detector. Memory access instructions are instrumented to detect data race bugs. See ! `https://github.com/google/sanitizers/wiki#threadsanitizer' for ! more details. The run-time behavior can be influenced using the ! `TSAN_OPTIONS' environment variable; see ! `https://github.com/google/sanitizers/wiki/ThreadSanitizerFlags' for a list of supported options. ! `-fsanitize=leak' Enable LeakSanitizer, a memory leak detector. This option only matters for linking of executables and if neither ! `-fsanitize=address' nor `-fsanitize=thread' is used. In that ! case the executable is linked against a library that overrides ! `malloc' and other allocator functions. See ! `https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSanitizer' for more details. The run-time behavior can be influenced using ! the `LSAN_OPTIONS' environment variable. ! `-fsanitize=undefined' Enable UndefinedBehaviorSanitizer, a fast undefined behavior detector. Various computations are instrumented to detect undefined behavior at runtime. Current suboptions are: ! `-fsanitize=shift' This option enables checking that the result of a shift operation is not undefined. Note that what exactly is considered undefined differs slightly between C and C++, as well as between ISO C90 and C99, etc. ! `-fsanitize=integer-divide-by-zero' ! Detect integer division by zero as well as `INT_MIN / -1' division. ! `-fsanitize=unreachable' With this option, the compiler turns the ! `__builtin_unreachable' call into a diagnostics message call ! instead. When reaching the `__builtin_unreachable' call, the behavior is undefined. ! `-fsanitize=vla-bound' ! This option instructs the compiler to check that the size of ! a variable length array is positive. ! `-fsanitize=null' This option enables pointer checking. Particularly, the application built with this option turned on will issue an error message when it tries to dereference a NULL pointer, or *************** program analysis purposes. *** 9115,9422 **** NULL pointer, or if a method is invoked on an object pointed by a NULL pointer. ! '-fsanitize=return' ! This option enables return statement checking. Programs built ! with this option turned on will issue an error message when ! the end of a non-void function is reached without actually ! returning a value. This option works in C++ only. ! '-fsanitize=signed-integer-overflow' This option enables signed integer overflow checking. We ! check that the result of '+', '*', and both unary and binary ! '-' does not overflow in the signed arithmetics. Note, integer promotion rules must be taken into account. That is, the following is not an overflow: signed char a = SCHAR_MAX; a++; ! '-fsanitize=bounds' This option enables instrumentation of array bounds. Various out of bounds accesses are detected. Flexible array members, flexible array member-like arrays, and initializers of variables with static storage are not instrumented. ! '-fsanitize=bounds-strict' This option enables strict instrumentation of array bounds. Most out of bounds accesses are detected, including flexible array members and flexible array member-like arrays. Initializers of variables with static storage are not instrumented. ! '-fsanitize=alignment' ! This option enables checking of alignment of pointers when they are dereferenced, or when a reference is bound to ! insufficiently aligned target, or when a method or constructor ! is invoked on insufficiently aligned object. ! '-fsanitize=object-size' ! This option enables instrumentation of memory references using ! the '__builtin_object_size' function. Various out of bounds ! pointer accesses are detected. ! '-fsanitize=float-divide-by-zero' Detect floating-point division by zero. Unlike other similar ! options, '-fsanitize=float-divide-by-zero' is not enabled by ! '-fsanitize=undefined', since floating-point division by zero can be a legitimate way of obtaining infinities and NaNs. ! '-fsanitize=float-cast-overflow' This option enables floating-point type to integer conversion ! checking. We check that the result of the conversion does not ! overflow. Unlike other similar options, ! '-fsanitize=float-cast-overflow' is not enabled by ! '-fsanitize=undefined'. This option does not work well with ! 'FE_INVALID' exceptions enabled. ! ! '-fsanitize=nonnull-attribute' ! ! This option enables instrumentation of calls, checking whether ! null values are not passed to arguments marked as requiring a ! non-null value by the 'nonnull' function attribute. ! '-fsanitize=returns-nonnull-attribute' This option enables instrumentation of return statements in ! functions marked with 'returns_nonnull' function attribute, to ! detect returning of null values from such functions. ! ! '-fsanitize=bool' This option enables instrumentation of loads from bool. If a value other than 0/1 is loaded, a run-time error is issued. ! '-fsanitize=enum' ! This option enables instrumentation of loads from an enum type. If a value outside the range of values for the enum type is loaded, a run-time error is issued. ! '-fsanitize=vptr' ! This option enables instrumentation of C++ member function calls, member accesses and some conversions between pointers to base and derived classes, to verify the referenced object has the correct dynamic type. - While '-ftrapv' causes traps for signed overflows to be emitted, - '-fsanitize=undefined' gives a diagnostic message. This currently - works only for the C family of languages. ! '-fno-sanitize=all' This option disables all previously enabled sanitizers. ! '-fsanitize=all' is not allowed, as some sanitizers cannot be used together. ! '-fasan-shadow-offset=NUMBER' This option forces GCC to use custom shadow offset in AddressSanitizer checks. It is useful for experimenting with different shadow memory layouts in Kernel AddressSanitizer. ! '-fsanitize-sections=S1,S2,...' Sanitize global variables in selected user-defined sections. SI may contain wildcards. ! '-fsanitize-recover[=OPTS]' ! '-fsanitize-recover=' controls error recovery mode for sanitizers mentioned in comma-separated list of OPTS. Enabling this option for a sanitizer component causes it to attempt to continue running the program as if no error happened. This means multiple runtime errors can be reported in a single program run, and the exit code of the program may indicate success even when errors have been ! reported. The '-fno-sanitize-recover=' option can be used to alter this behavior: only the first detected error is reported and program then exits with a non-zero exit code. ! Currently this feature only works for '-fsanitize=undefined' (and ! its suboptions except for '-fsanitize=unreachable' and ! '-fsanitize=return'), '-fsanitize=float-cast-overflow', ! '-fsanitize=float-divide-by-zero', '-fsanitize=kernel-address' and ! '-fsanitize=address'. For these sanitizers error recovery is ! turned on by default, except '-fsanitize=address', for which this ! feature is experimental. '-fsanitize-recover=all' and ! '-fno-sanitize-recover=all' is also accepted, the former enables recovery for all sanitizers that support it, the latter disables recovery for all sanitizers that support it. Syntax without explicit OPTS parameter is deprecated. It is equivalent to -fsanitize-recover=undefined,float-cast-overflow,float-divide-by-zero ! Similarly '-fno-sanitize-recover' is equivalent to -fno-sanitize-recover=undefined,float-cast-overflow,float-divide-by-zero ! '-fsanitize-undefined-trap-on-error' ! The '-fsanitize-undefined-trap-on-error' option instructs the ! compiler to report undefined behavior using '__builtin_trap' rather ! than a 'libubsan' library routine. The advantage of this is that ! the 'libubsan' library is not needed and is not linked in, so this ! is usable even in freestanding environments. ! '-fsanitize-coverage=trace-pc' Enable coverage-guided fuzzing code instrumentation. Inserts a ! call to '__sanitizer_cov_trace_pc' into every basic block. ! '-fbounds-check' For front ends that support it, generate additional code to check that indices used to access arrays are within the declared range. This is currently only supported by the Java and Fortran front ends, where this option defaults to true and false respectively. ! '-fcheck-pointer-bounds' Enable Pointer Bounds Checker instrumentation. Each memory reference is instrumented with checks of the pointer used for memory access against bounds associated with that pointer. Currently there is only an implementation for Intel MPX available, ! thus x86 GNU/Linux target and '-mmpx' are required to enable this feature. MPX-based instrumentation requires a runtime library to enable MPX in hardware and handle bounds violation signals. By ! default when '-fcheck-pointer-bounds' and '-mmpx' options are used ! to link a program, the GCC driver links against the 'libmpx' and ! 'libmpxwrappers' libraries. Bounds checking on calls to dynamic ! libraries requires a linker with '-z bndplt' support; if GCC was ! configured with a linker without support for this option (including ! the Gold linker and older versions of ld), a warning is given if ! you link with '-mmpx' without also specifying '-static', since the ! overall effectiveness of the bounds checking protection is reduced. ! See also '-static-libmpxwrappers'. ! MPX-based instrumentation may be used for debugging and also may be ! included in production code to increase program security. Depending on usage, you may have different requirements for the ! runtime library. The current version of the MPX runtime library is ! more oriented for use as a debugging tool. MPX runtime library ! usage implies '-lpthread'. See also '-static-libmpx'. The runtime ! library behavior can be influenced using various 'CHKP_RT_*' ! environment variables. See ! for more details. ! Generated instrumentation may be controlled by various '-fchkp-*' ! options and by the 'bnd_variable_size' structure field attribute ! (*note Type Attributes::) and 'bnd_legacy', and 'bnd_instrument' function attributes (*note Function Attributes::). GCC also ! provides a number of built-in functions for controlling the Pointer ! Bounds Checker. *Note Pointer Bounds Checker builtins::, for more ! information. ! '-fchkp-check-incomplete-type' Generate pointer bounds checks for variables with incomplete type. Enabled by default. ! '-fchkp-narrow-bounds' Controls bounds used by Pointer Bounds Checker for pointers to ! object fields. If narrowing is enabled then field bounds are used. ! Otherwise object bounds are used. See also ! '-fchkp-narrow-to-innermost-array' and ! '-fchkp-first-field-has-own-bounds'. Enabled by default. ! '-fchkp-first-field-has-own-bounds' Forces Pointer Bounds Checker to use narrowed bounds for the address of the first field in the structure. By default a pointer to the first field has the same bounds as a pointer to the whole structure. ! '-fchkp-narrow-to-innermost-array' ! Forces Pointer Bounds Checker to use bounds of the innermost arrays ! in case of nested static array access. By default this option is ! disabled and bounds of the outermost array are used. ! '-fchkp-optimize' Enables Pointer Bounds Checker optimizations. Enabled by default ! at optimization levels '-O', '-O2', '-O3'. ! '-fchkp-use-fast-string-functions' ! Enables use of '*_nobnd' versions of string functions (not copying bounds) by Pointer Bounds Checker. Disabled by default. ! '-fchkp-use-nochk-string-functions' ! Enables use of '*_nochk' versions of string functions (not checking ! bounds) by Pointer Bounds Checker. Disabled by default. ! '-fchkp-use-static-bounds' Allow Pointer Bounds Checker to generate static bounds holding bounds of static variables. Enabled by default. ! '-fchkp-use-static-const-bounds' Use statically-initialized bounds for constant bounds instead of generating them each time they are required. By default enabled ! when '-fchkp-use-static-bounds' is enabled. ! '-fchkp-treat-zero-dynamic-size-as-infinite' With this option, objects with incomplete type whose dynamically-obtained size is zero are treated as having infinite ! size instead by Pointer Bounds Checker. This option may be helpful ! if a program is linked with a library missing size information for ! some symbols. Disabled by default. ! '-fchkp-check-read' Instructs Pointer Bounds Checker to generate checks for all read accesses to memory. Enabled by default. ! '-fchkp-check-write' Instructs Pointer Bounds Checker to generate checks for all write accesses to memory. Enabled by default. ! '-fchkp-store-bounds' Instructs Pointer Bounds Checker to generate bounds stores for pointer writes. Enabled by default. ! '-fchkp-instrument-calls' Instructs Pointer Bounds Checker to pass pointer bounds to calls. Enabled by default. ! '-fchkp-instrument-marked-only' Instructs Pointer Bounds Checker to instrument only functions ! marked with the 'bnd_instrument' attribute (*note Function Attributes::). Disabled by default. ! '-fchkp-use-wrappers' Allows Pointer Bounds Checker to replace calls to built-in functions with calls to wrapper functions. When ! '-fchkp-use-wrappers' is used to link a program, the GCC driver ! automatically links against 'libmpxwrappers'. See also ! '-static-libmpxwrappers'. Enabled by default. ! '-fstack-protector' Emit extra code to check for buffer overflows, such as stack smashing attacks. This is done by adding a guard variable to functions with vulnerable objects. This includes functions that ! call 'alloca', and functions with buffers larger than 8 bytes. The ! guards are initialized when a function is entered and then checked ! when the function exits. If a guard check fails, an error message ! is printed and the program exits. ! '-fstack-protector-all' ! Like '-fstack-protector' except that all functions are protected. ! '-fstack-protector-strong' ! Like '-fstack-protector' but includes additional functions to be protected -- those that have local array definitions, or have references to local frame addresses. ! '-fstack-protector-explicit' ! Like '-fstack-protector' but only protects those functions which ! have the 'stack_protect' attribute. ! '-fstack-check' Generate code to verify that you do not go beyond the boundary of the stack. You should specify this flag if you are running in an environment with multiple threads, but you only rarely need to ! specify it in a single-threaded environment since stack overflow is ! automatically detected on nearly all systems if there is only one ! stack. Note that this switch does not actually cause checking to be done; the operating system or the language runtime must do that. The switch causes generation of code to ensure that they see the stack being extended. ! You can additionally specify a string parameter: 'no' means no ! checking, 'generic' means force the use of old-style checking, ! 'specific' means use the best checking method and is equivalent to ! bare '-fstack-check'. Old-style checking is a generic mechanism that requires no specific target support in the compiler but comes with the following --- 9163,9465 ---- NULL pointer, or if a method is invoked on an object pointed by a NULL pointer. ! `-fsanitize=return' ! This option enables return statement checking. Programs ! built with this option turned on will issue an error message ! when the end of a non-void function is reached without ! actually returning a value. This option works in C++ only. ! `-fsanitize=signed-integer-overflow' This option enables signed integer overflow checking. We ! check that the result of `+', `*', and both unary and binary ! `-' does not overflow in the signed arithmetics. Note, integer promotion rules must be taken into account. That is, the following is not an overflow: signed char a = SCHAR_MAX; a++; ! `-fsanitize=bounds' This option enables instrumentation of array bounds. Various out of bounds accesses are detected. Flexible array members, flexible array member-like arrays, and initializers of variables with static storage are not instrumented. ! `-fsanitize=bounds-strict' This option enables strict instrumentation of array bounds. Most out of bounds accesses are detected, including flexible array members and flexible array member-like arrays. Initializers of variables with static storage are not instrumented. ! `-fsanitize=alignment' This option enables checking of alignment of pointers when they are dereferenced, or when a reference is bound to ! insufficiently aligned target, or when a method or ! constructor is invoked on insufficiently aligned object. ! `-fsanitize=object-size' ! This option enables instrumentation of memory references ! using the `__builtin_object_size' function. Various out of ! bounds pointer accesses are detected. ! `-fsanitize=float-divide-by-zero' Detect floating-point division by zero. Unlike other similar ! options, `-fsanitize=float-divide-by-zero' is not enabled by ! `-fsanitize=undefined', since floating-point division by zero can be a legitimate way of obtaining infinities and NaNs. ! `-fsanitize=float-cast-overflow' This option enables floating-point type to integer conversion ! checking. We check that the result of the conversion does ! not overflow. Unlike other similar options, ! `-fsanitize=float-cast-overflow' is not enabled by ! `-fsanitize=undefined'. This option does not work well with ! `FE_INVALID' exceptions enabled. ! `-fsanitize=nonnull-attribute' ! This option enables instrumentation of calls, checking ! whether null values are not passed to arguments marked as ! requiring a non-null value by the `nonnull' function ! attribute. + `-fsanitize=returns-nonnull-attribute' This option enables instrumentation of return statements in ! functions marked with `returns_nonnull' function attribute, ! to detect returning of null values from such functions. + `-fsanitize=bool' This option enables instrumentation of loads from bool. If a value other than 0/1 is loaded, a run-time error is issued. ! `-fsanitize=enum' This option enables instrumentation of loads from an enum type. If a value outside the range of values for the enum type is loaded, a run-time error is issued. ! `-fsanitize=vptr' This option enables instrumentation of C++ member function calls, member accesses and some conversions between pointers to base and derived classes, to verify the referenced object has the correct dynamic type. ! While `-ftrapv' causes traps for signed overflows to be emitted, ! `-fsanitize=undefined' gives a diagnostic message. This currently ! works only for the C family of languages. + `-fno-sanitize=all' This option disables all previously enabled sanitizers. ! `-fsanitize=all' is not allowed, as some sanitizers cannot be used together. ! `-fasan-shadow-offset=NUMBER' This option forces GCC to use custom shadow offset in AddressSanitizer checks. It is useful for experimenting with different shadow memory layouts in Kernel AddressSanitizer. ! `-fsanitize-sections=S1,S2,...' Sanitize global variables in selected user-defined sections. SI may contain wildcards. ! `-fsanitize-recover[=OPTS]' ! `-fsanitize-recover=' controls error recovery mode for sanitizers mentioned in comma-separated list of OPTS. Enabling this option for a sanitizer component causes it to attempt to continue running the program as if no error happened. This means multiple runtime errors can be reported in a single program run, and the exit code of the program may indicate success even when errors have been ! reported. The `-fno-sanitize-recover=' option can be used to alter this behavior: only the first detected error is reported and program then exits with a non-zero exit code. ! Currently this feature only works for `-fsanitize=undefined' (and ! its suboptions except for `-fsanitize=unreachable' and ! `-fsanitize=return'), `-fsanitize=float-cast-overflow', ! `-fsanitize=float-divide-by-zero', `-fsanitize=kernel-address' and ! `-fsanitize=address'. For these sanitizers error recovery is ! turned on by default, except `-fsanitize=address', for which this ! feature is experimental. `-fsanitize-recover=all' and ! `-fno-sanitize-recover=all' is also accepted, the former enables recovery for all sanitizers that support it, the latter disables recovery for all sanitizers that support it. Syntax without explicit OPTS parameter is deprecated. It is equivalent to -fsanitize-recover=undefined,float-cast-overflow,float-divide-by-zero ! Similarly `-fno-sanitize-recover' is equivalent to -fno-sanitize-recover=undefined,float-cast-overflow,float-divide-by-zero ! `-fsanitize-undefined-trap-on-error' ! The `-fsanitize-undefined-trap-on-error' option instructs the ! compiler to report undefined behavior using `__builtin_trap' ! rather than a `libubsan' library routine. The advantage of this ! is that the `libubsan' library is not needed and is not linked in, ! so this is usable even in freestanding environments. ! `-fsanitize-coverage=trace-pc' Enable coverage-guided fuzzing code instrumentation. Inserts a ! call to `__sanitizer_cov_trace_pc' into every basic block. ! `-fbounds-check' For front ends that support it, generate additional code to check that indices used to access arrays are within the declared range. This is currently only supported by the Java and Fortran front ends, where this option defaults to true and false respectively. ! `-fcheck-pointer-bounds' Enable Pointer Bounds Checker instrumentation. Each memory reference is instrumented with checks of the pointer used for memory access against bounds associated with that pointer. Currently there is only an implementation for Intel MPX available, ! thus x86 GNU/Linux target and `-mmpx' are required to enable this feature. MPX-based instrumentation requires a runtime library to enable MPX in hardware and handle bounds violation signals. By ! default when `-fcheck-pointer-bounds' and `-mmpx' options are used ! to link a program, the GCC driver links against the `libmpx' and ! `libmpxwrappers' libraries. Bounds checking on calls to dynamic ! libraries requires a linker with `-z bndplt' support; if GCC was ! configured with a linker without support for this option ! (including the Gold linker and older versions of ld), a warning is ! given if you link with `-mmpx' without also specifying `-static', ! since the overall effectiveness of the bounds checking protection ! is reduced. See also `-static-libmpxwrappers'. ! MPX-based instrumentation may be used for debugging and also may ! be included in production code to increase program security. Depending on usage, you may have different requirements for the ! runtime library. The current version of the MPX runtime library ! is more oriented for use as a debugging tool. MPX runtime library ! usage implies `-lpthread'. See also `-static-libmpx'. The ! runtime library behavior can be influenced using various ! `CHKP_RT_*' environment variables. See ! `https://gcc.gnu.org/wiki/Intel%20MPX%20support%20in%20the%20GCC%20compiler' for more details. ! Generated instrumentation may be controlled by various `-fchkp-*' ! options and by the `bnd_variable_size' structure field attribute ! (*note Type Attributes::) and `bnd_legacy', and `bnd_instrument' function attributes (*note Function Attributes::). GCC also ! provides a number of built-in functions for controlling the ! Pointer Bounds Checker. *Note Pointer Bounds Checker builtins::, ! for more information. ! `-fchkp-check-incomplete-type' Generate pointer bounds checks for variables with incomplete type. Enabled by default. ! `-fchkp-narrow-bounds' Controls bounds used by Pointer Bounds Checker for pointers to ! object fields. If narrowing is enabled then field bounds are ! used. Otherwise object bounds are used. See also ! `-fchkp-narrow-to-innermost-array' and ! `-fchkp-first-field-has-own-bounds'. Enabled by default. ! `-fchkp-first-field-has-own-bounds' Forces Pointer Bounds Checker to use narrowed bounds for the address of the first field in the structure. By default a pointer to the first field has the same bounds as a pointer to the whole structure. ! `-fchkp-narrow-to-innermost-array' ! Forces Pointer Bounds Checker to use bounds of the innermost ! arrays in case of nested static array access. By default this ! option is disabled and bounds of the outermost array are used. ! `-fchkp-optimize' Enables Pointer Bounds Checker optimizations. Enabled by default ! at optimization levels `-O', `-O2', `-O3'. ! `-fchkp-use-fast-string-functions' ! Enables use of `*_nobnd' versions of string functions (not copying bounds) by Pointer Bounds Checker. Disabled by default. ! `-fchkp-use-nochk-string-functions' ! Enables use of `*_nochk' versions of string functions (not ! checking bounds) by Pointer Bounds Checker. Disabled by default. ! `-fchkp-use-static-bounds' Allow Pointer Bounds Checker to generate static bounds holding bounds of static variables. Enabled by default. ! `-fchkp-use-static-const-bounds' Use statically-initialized bounds for constant bounds instead of generating them each time they are required. By default enabled ! when `-fchkp-use-static-bounds' is enabled. ! `-fchkp-treat-zero-dynamic-size-as-infinite' With this option, objects with incomplete type whose dynamically-obtained size is zero are treated as having infinite ! size instead by Pointer Bounds Checker. This option may be ! helpful if a program is linked with a library missing size ! information for some symbols. Disabled by default. ! `-fchkp-check-read' Instructs Pointer Bounds Checker to generate checks for all read accesses to memory. Enabled by default. ! `-fchkp-check-write' Instructs Pointer Bounds Checker to generate checks for all write accesses to memory. Enabled by default. ! `-fchkp-store-bounds' Instructs Pointer Bounds Checker to generate bounds stores for pointer writes. Enabled by default. ! `-fchkp-instrument-calls' Instructs Pointer Bounds Checker to pass pointer bounds to calls. Enabled by default. ! `-fchkp-instrument-marked-only' Instructs Pointer Bounds Checker to instrument only functions ! marked with the `bnd_instrument' attribute (*note Function Attributes::). Disabled by default. ! `-fchkp-use-wrappers' Allows Pointer Bounds Checker to replace calls to built-in functions with calls to wrapper functions. When ! `-fchkp-use-wrappers' is used to link a program, the GCC driver ! automatically links against `libmpxwrappers'. See also ! `-static-libmpxwrappers'. Enabled by default. ! `-fstack-protector' Emit extra code to check for buffer overflows, such as stack smashing attacks. This is done by adding a guard variable to functions with vulnerable objects. This includes functions that ! call `alloca', and functions with buffers larger than 8 bytes. ! The guards are initialized when a function is entered and then ! checked when the function exits. If a guard check fails, an error ! message is printed and the program exits. ! `-fstack-protector-all' ! Like `-fstack-protector' except that all functions are protected. ! `-fstack-protector-strong' ! Like `-fstack-protector' but includes additional functions to be protected -- those that have local array definitions, or have references to local frame addresses. ! `-fstack-protector-explicit' ! Like `-fstack-protector' but only protects those functions which ! have the `stack_protect' attribute. ! `-fstack-check' Generate code to verify that you do not go beyond the boundary of the stack. You should specify this flag if you are running in an environment with multiple threads, but you only rarely need to ! specify it in a single-threaded environment since stack overflow ! is automatically detected on nearly all systems if there is only ! one stack. Note that this switch does not actually cause checking to be done; the operating system or the language runtime must do that. The switch causes generation of code to ensure that they see the stack being extended. ! You can additionally specify a string parameter: `no' means no ! checking, `generic' means force the use of old-style checking, ! `specific' means use the best checking method and is equivalent to ! bare `-fstack-check'. Old-style checking is a generic mechanism that requires no specific target support in the compiler but comes with the following *************** program analysis purposes. *** 9426,9444 **** always allocated dynamically if their size exceeds a fixed threshold. ! 2. Fixed limit on the size of the static frame of functions: when ! it is topped by a particular function, stack checking is not ! reliable and a warning is issued by the compiler. ! 3. Inefficiency: because of both the modified allocation strategy ! and the generic implementation, code performance is hampered. Note that old-style stack checking is also the fallback method for ! 'specific' if no target support has been added in the compiler. ! '-fstack-limit-register=REG' ! '-fstack-limit-symbol=SYM' ! '-fno-stack-limit' Generate code to ensure that the stack does not grow beyond a certain value, either the value of a register or the address of a symbol. If a larger stack is required, a signal is raised at run --- 9469,9488 ---- always allocated dynamically if their size exceeds a fixed threshold. ! 2. Fixed limit on the size of the static frame of functions: ! when it is topped by a particular function, stack checking is ! not reliable and a warning is issued by the compiler. ! 3. Inefficiency: because of both the modified allocation ! strategy and the generic implementation, code performance is ! hampered. Note that old-style stack checking is also the fallback method for ! `specific' if no target support has been added in the compiler. ! `-fstack-limit-register=REG' ! `-fstack-limit-symbol=SYM' ! `-fno-stack-limit' Generate code to ensure that the stack does not grow beyond a certain value, either the value of a register or the address of a symbol. If a larger stack is required, a signal is raised at run *************** program analysis purposes. *** 9446,9461 **** overruns the boundary, so it is possible to catch the signal without taking special precautions. ! For instance, if the stack starts at absolute address '0x80000000' and grows downwards, you can use the flags ! '-fstack-limit-symbol=__stack_limit' and ! '-Wl,--defsym,__stack_limit=0x7ffe0000' to enforce a stack limit of ! 128KB. Note that this may only work with the GNU linker. You can locally override stack limit checking by using the ! 'no_stack_limit' function attribute (*note Function Attributes::). ! '-fsplit-stack' Generate code to automatically split the stack before it overflows. The resulting program has a discontiguous stack which can only overflow if the program is unable to allocate any more memory. --- 9490,9505 ---- overruns the boundary, so it is possible to catch the signal without taking special precautions. ! For instance, if the stack starts at absolute address `0x80000000' and grows downwards, you can use the flags ! `-fstack-limit-symbol=__stack_limit' and ! `-Wl,--defsym,__stack_limit=0x7ffe0000' to enforce a stack limit ! of 128KB. Note that this may only work with the GNU linker. You can locally override stack limit checking by using the ! `no_stack_limit' function attribute (*note Function Attributes::). ! `-fsplit-stack' Generate code to automatically split the stack before it overflows. The resulting program has a discontiguous stack which can only overflow if the program is unable to allocate any more memory. *************** program analysis purposes. *** 9464,9537 **** thread. This is currently only implemented for the x86 targets running GNU/Linux. ! When code compiled with '-fsplit-stack' calls code compiled without ! '-fsplit-stack', there may not be much stack space available for ! the latter code to run. If compiling all code, including library ! code, with '-fsplit-stack' is not an option, then the linker can ! fix up these calls so that the code compiled without ! '-fsplit-stack' always has a large stack. Support for this is ! implemented in the gold linker in GNU binutils release 2.21 and ! later. ! '-fvtable-verify=[std|preinit|none]' ! This option is only available when compiling C++ code. It turns on ! (or off, if using '-fvtable-verify=none') the security feature that ! verifies at run time, for every virtual call, that the vtable ! pointer through which the call is made is valid for the type of the ! object, and has not been corrupted or overwritten. If an invalid ! vtable pointer is detected at run time, an error is reported and ! execution of the program is immediately halted. This option causes run-time data structures to be built at program startup, which are used for verifying the vtable pointers. The ! options 'std' and 'preinit' control the timing of when these data structures are built. In both cases the data structures are built ! before execution reaches 'main'. Using '-fvtable-verify=std' causes the data structures to be built after shared libraries have ! been loaded and initialized. '-fvtable-verify=preinit' causes them ! to be built before shared libraries have been loaded and initialized. If this option appears multiple times in the command line with ! different values specified, 'none' takes highest priority over both ! 'std' and 'preinit'; 'preinit' takes priority over 'std'. ! '-fvtv-debug' ! When used in conjunction with '-fvtable-verify=std' or ! '-fvtable-verify=preinit', causes debug versions of the runtime functions for the vtable verification feature to be called. This ! flag also causes the compiler to log information about which vtable ! pointers it finds for each class. This information is written to a ! file named 'vtv_set_ptr_data.log' in the directory named by the ! environment variable 'VTV_LOGS_DIR' if that is defined or the ! current working directory otherwise. ! Note: This feature _appends_ data to the log file. If you want a fresh log file, be sure to delete any existing one. ! '-fvtv-counts' This is a debugging flag. When used in conjunction with ! '-fvtable-verify=std' or '-fvtable-verify=preinit', this causes the ! compiler to keep track of the total number of virtual calls it encounters and the number of verifications it inserts. It also counts the number of calls to certain run-time library functions that it inserts and logs this information for each compilation unit. The compiler writes this information to a file named ! 'vtv_count_data.log' in the directory named by the environment ! variable 'VTV_LOGS_DIR' if that is defined or the current working ! directory otherwise. It also counts the size of the vtable pointer ! sets for each class, and writes this information to ! 'vtv_class_set_sizes.log' in the same directory. ! Note: This feature _appends_ data to the log files. To get fresh log files, be sure to delete any existing ones. ! '-finstrument-functions' Generate instrumentation calls for entry and exit to functions. Just after function entry and just before function exit, the following profiling functions are called with the address of the current function and its call site. (On some platforms, ! '__builtin_return_address' does not work beyond the current function, so the call site information may not be available to the profiling functions otherwise.) --- 9508,9581 ---- thread. This is currently only implemented for the x86 targets running GNU/Linux. ! When code compiled with `-fsplit-stack' calls code compiled ! without `-fsplit-stack', there may not be much stack space ! available for the latter code to run. If compiling all code, ! including library code, with `-fsplit-stack' is not an option, ! then the linker can fix up these calls so that the code compiled ! without `-fsplit-stack' always has a large stack. Support for ! this is implemented in the gold linker in GNU binutils release 2.21 ! and later. ! `-fvtable-verify=[std|preinit|none]' ! This option is only available when compiling C++ code. It turns ! on (or off, if using `-fvtable-verify=none') the security feature ! that verifies at run time, for every virtual call, that the vtable ! pointer through which the call is made is valid for the type of ! the object, and has not been corrupted or overwritten. If an ! invalid vtable pointer is detected at run time, an error is ! reported and execution of the program is immediately halted. This option causes run-time data structures to be built at program startup, which are used for verifying the vtable pointers. The ! options `std' and `preinit' control the timing of when these data structures are built. In both cases the data structures are built ! before execution reaches `main'. Using `-fvtable-verify=std' causes the data structures to be built after shared libraries have ! been loaded and initialized. `-fvtable-verify=preinit' causes ! them to be built before shared libraries have been loaded and initialized. If this option appears multiple times in the command line with ! different values specified, `none' takes highest priority over ! both `std' and `preinit'; `preinit' takes priority over `std'. ! `-fvtv-debug' ! When used in conjunction with `-fvtable-verify=std' or ! `-fvtable-verify=preinit', causes debug versions of the runtime functions for the vtable verification feature to be called. This ! flag also causes the compiler to log information about which ! vtable pointers it finds for each class. This information is ! written to a file named `vtv_set_ptr_data.log' in the directory ! named by the environment variable `VTV_LOGS_DIR' if that is ! defined or the current working directory otherwise. ! Note: This feature _appends_ data to the log file. If you want a fresh log file, be sure to delete any existing one. ! `-fvtv-counts' This is a debugging flag. When used in conjunction with ! `-fvtable-verify=std' or `-fvtable-verify=preinit', this causes ! the compiler to keep track of the total number of virtual calls it encounters and the number of verifications it inserts. It also counts the number of calls to certain run-time library functions that it inserts and logs this information for each compilation unit. The compiler writes this information to a file named ! `vtv_count_data.log' in the directory named by the environment ! variable `VTV_LOGS_DIR' if that is defined or the current working ! directory otherwise. It also counts the size of the vtable ! pointer sets for each class, and writes this information to ! `vtv_class_set_sizes.log' in the same directory. ! Note: This feature _appends_ data to the log files. To get fresh log files, be sure to delete any existing ones. ! `-finstrument-functions' Generate instrumentation calls for entry and exit to functions. Just after function entry and just before function exit, the following profiling functions are called with the address of the current function and its call site. (On some platforms, ! `__builtin_return_address' does not work beyond the current function, so the call site information may not be available to the profiling functions otherwise.) *************** program analysis purposes. *** 9544,9570 **** function, which may be looked up exactly in the symbol table. This instrumentation is also done for functions expanded inline in ! other functions. The profiling calls indicate where, conceptually, ! the inline function is entered and exited. This means that ! addressable versions of such functions must be available. If all ! your uses of a function are expanded inline, this may mean an ! additional expansion of code size. If you use 'extern inline' in ! your C code, an addressable version of such functions must be ! provided. (This is normally the case anyway, but if you get lucky ! and the optimizer always expands the functions inline, you might ! have gotten away without providing static copies.) ! A function may be given the attribute 'no_instrument_function', in which case this instrumentation is not done. This can be used, for example, for the profiling functions listed above, high-priority interrupt routines, and any functions from which the profiling functions cannot safely be called (perhaps signal handlers, if the profiling routines generate output or allocate memory). ! '-finstrument-functions-exclude-file-list=FILE,FILE,...' ! Set the list of functions that are excluded from instrumentation ! (see the description of '-finstrument-functions'). If the file that contains a function definition matches with one of FILE, then that function is not instrumented. The match is done on substrings: if the FILE parameter is a substring of the file name, --- 9588,9614 ---- function, which may be looked up exactly in the symbol table. This instrumentation is also done for functions expanded inline in ! other functions. The profiling calls indicate where, ! conceptually, the inline function is entered and exited. This ! means that addressable versions of such functions must be ! available. If all your uses of a function are expanded inline, ! this may mean an additional expansion of code size. If you use ! `extern inline' in your C code, an addressable version of such ! functions must be provided. (This is normally the case anyway, ! but if you get lucky and the optimizer always expands the ! functions inline, you might have gotten away without providing ! static copies.) ! A function may be given the attribute `no_instrument_function', in which case this instrumentation is not done. This can be used, for example, for the profiling functions listed above, high-priority interrupt routines, and any functions from which the profiling functions cannot safely be called (perhaps signal handlers, if the profiling routines generate output or allocate memory). ! `-finstrument-functions-exclude-file-list=FILE,FILE,...' Set the list of functions that are excluded from instrumentation ! (see the description of `-finstrument-functions'). If the file that contains a function definition matches with one of FILE, then that function is not instrumented. The match is done on substrings: if the FILE parameter is a substring of the file name, *************** program analysis purposes. *** 9575,9598 **** -finstrument-functions-exclude-file-list=/bits/stl,include/sys excludes any inline function defined in files whose pathnames ! contain '/bits/stl' or 'include/sys'. ! If, for some reason, you want to include letter ',' in one of SYM, ! write '\,'. For example, ! '-finstrument-functions-exclude-file-list='\,\,tmp'' (note the single quote surrounding the option). ! '-finstrument-functions-exclude-function-list=SYM,SYM,...' ! ! This is similar to '-finstrument-functions-exclude-file-list', but this option sets the list of function names to be excluded from instrumentation. The function name to be matched is its ! user-visible name, such as 'vector blah(const vector &)', ! not the internal mangled name (e.g., '_Z4blahRSt6vectorIiSaIiEE'). ! The match is done on substrings: if the SYM parameter is a ! substring of the function name, it is considered to be a match. ! For C99 and C++ extended identifiers, the function name must be ! given in UTF-8, not using universal character names.  File: gcc.info, Node: Preprocessor Options, Next: Assembler Options, Prev: Instrumentation Options, Up: Invoking GCC --- 9619,9643 ---- -finstrument-functions-exclude-file-list=/bits/stl,include/sys excludes any inline function defined in files whose pathnames ! contain `/bits/stl' or `include/sys'. ! If, for some reason, you want to include letter `,' in one of SYM, ! write `\,'. For example, ! `-finstrument-functions-exclude-file-list='\,\,tmp'' (note the single quote surrounding the option). ! `-finstrument-functions-exclude-function-list=SYM,SYM,...' ! This is similar to `-finstrument-functions-exclude-file-list', but this option sets the list of function names to be excluded from instrumentation. The function name to be matched is its ! user-visible name, such as `vector blah(const vector ! &)', not the internal mangled name (e.g., ! `_Z4blahRSt6vectorIiSaIiEE'). The match is done on substrings: if ! the SYM parameter is a substring of the function name, it is ! considered to be a match. For C99 and C++ extended identifiers, ! the function name must be given in UTF-8, not using universal ! character names. !  File: gcc.info, Node: Preprocessor Options, Next: Assembler Options, Prev: Instrumentation Options, Up: Invoking GCC *************** File: gcc.info, Node: Preprocessor Opti *** 9603,9652 **** These options control the C preprocessor, which is run on each C source file before actual compilation. ! If you use the '-E' option, nothing is done except preprocessing. Some ! of these options make sense only together with '-E' because they cause ! the preprocessor output to be unsuitable for actual compilation. ! '-Wp,OPTION' ! You can use '-Wp,OPTION' to bypass the compiler driver and pass OPTION directly through to the preprocessor. If OPTION contains commas, it is split into multiple options at the commas. However, many options are modified, translated or interpreted by the ! compiler driver before being passed to the preprocessor, and '-Wp' forcibly bypasses this phase. The preprocessor's direct interface is undocumented and subject to change, so whenever possible you ! should avoid using '-Wp' and let the driver handle the options instead. ! '-Xpreprocessor OPTION' Pass OPTION as an option to the preprocessor. You can use this to supply system-specific preprocessor options that GCC does not recognize. If you want to pass an option that takes an argument, you must use ! '-Xpreprocessor' twice, once for the option and once for the argument. ! '-no-integrated-cpp' Perform preprocessing as a separate pass before compilation. By default, GCC performs preprocessing as an integrated part of input tokenization and parsing. If this option is provided, the ! appropriate language front end ('cc1', 'cc1plus', or 'cc1obj' for C, C++, and Objective-C, respectively) is instead invoked twice, once for preprocessing only and once for actual compilation of the preprocessed input. This option may be useful in conjunction with ! the '-B' or '-wrapper' options to specify an alternate preprocessor ! or perform additional processing of the program source between ! normal preprocessing and compilation. ! '-D NAME' ! Predefine NAME as a macro, with definition '1'. ! '-D NAME=DEFINITION' The contents of DEFINITION are tokenized and processed as if they ! appeared during translation phase three in a '#define' directive. ! In particular, the definition will be truncated by embedded newline ! characters. If you are invoking the preprocessor from a shell or shell-like program you may need to use the shell's quoting syntax to protect --- 9648,9697 ---- These options control the C preprocessor, which is run on each C source file before actual compilation. ! If you use the `-E' option, nothing is done except preprocessing. ! Some of these options make sense only together with `-E' because they ! cause the preprocessor output to be unsuitable for actual compilation. ! `-Wp,OPTION' ! You can use `-Wp,OPTION' to bypass the compiler driver and pass OPTION directly through to the preprocessor. If OPTION contains commas, it is split into multiple options at the commas. However, many options are modified, translated or interpreted by the ! compiler driver before being passed to the preprocessor, and `-Wp' forcibly bypasses this phase. The preprocessor's direct interface is undocumented and subject to change, so whenever possible you ! should avoid using `-Wp' and let the driver handle the options instead. ! `-Xpreprocessor OPTION' Pass OPTION as an option to the preprocessor. You can use this to supply system-specific preprocessor options that GCC does not recognize. If you want to pass an option that takes an argument, you must use ! `-Xpreprocessor' twice, once for the option and once for the argument. ! `-no-integrated-cpp' Perform preprocessing as a separate pass before compilation. By default, GCC performs preprocessing as an integrated part of input tokenization and parsing. If this option is provided, the ! appropriate language front end (`cc1', `cc1plus', or `cc1obj' for C, C++, and Objective-C, respectively) is instead invoked twice, once for preprocessing only and once for actual compilation of the preprocessed input. This option may be useful in conjunction with ! the `-B' or `-wrapper' options to specify an alternate ! preprocessor or perform additional processing of the program ! source between normal preprocessing and compilation. ! `-D NAME' ! Predefine NAME as a macro, with definition `1'. ! `-D NAME=DEFINITION' The contents of DEFINITION are tokenized and processed as if they ! appeared during translation phase three in a `#define' directive. ! In particular, the definition will be truncated by embedded ! newline characters. If you are invoking the preprocessor from a shell or shell-like program you may need to use the shell's quoting syntax to protect *************** the preprocessor output to be unsuitable *** 9655,9728 **** If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the equals sign (if any). Parentheses are meaningful to most shells, ! so you will need to quote the option. With 'sh' and 'csh', ! '-D'NAME(ARGS...)=DEFINITION'' works. ! '-D' and '-U' options are processed in the order they are given on ! the command line. All '-imacros FILE' and '-include FILE' options ! are processed after all '-D' and '-U' options. ! '-U NAME' ! Cancel any previous definition of NAME, either built in or provided ! with a '-D' option. ! '-undef' Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. ! '-I DIR' ! Add the directory DIR to the list of directories to be searched for ! header files. Directories named by '-I' are searched before the ! standard system include directories. If the directory DIR is a ! standard system include directory, the option is ignored to ensure ! that the default search order for system directories and the ! special treatment of system headers are not defeated . If DIR ! begins with '=', then the '=' will be replaced by the sysroot ! prefix; see '--sysroot' and '-isysroot'. ! '-o FILE' Write output to FILE. This is the same as specifying FILE as the ! second non-option argument to 'cpp'. 'gcc' has a different interpretation of a second non-option argument, so you must use ! '-o' to specify the output file. ! '-Wall' Turns on all optional warnings which are desirable for normal code. ! At present this is '-Wcomment', '-Wtrigraphs', '-Wmultichar' and a ! warning about integer promotion causing a change of sign in '#if' expressions. Note that many of the preprocessor's warnings are on by default and have no options to control them. ! '-Wcomment' ! '-Wcomments' ! Warn whenever a comment-start sequence '/*' appears in a '/*' ! comment, or whenever a backslash-newline appears in a '//' comment. (Both forms have the same effect.) ! '-Wtrigraphs' Most trigraphs in comments cannot affect the meaning of the program. However, a trigraph that would form an escaped newline ! ('??/' at the end of a line) can, by changing where the comment begins or ends. Therefore, only trigraphs that would form escaped newlines produce warnings inside a comment. ! This option is implied by '-Wall'. If '-Wall' is not given, this option is still enabled unless trigraphs are enabled. To get ! trigraph conversion without warnings, but get the other '-Wall' ! warnings, use '-trigraphs -Wall -Wno-trigraphs'. ! '-Wtraditional' Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and problematic constructs which should be avoided. ! '-Wundef' Warn whenever an identifier which is not a macro is encountered in ! an '#if' directive, outside of 'defined'. Such identifiers are replaced with zero. ! '-Wunused-macros' Warn about macros defined in the main file that are unused. A macro is "used" if it is expanded or tested for existence at least once. The preprocessor will also warn if the macro has not been --- 9700,9773 ---- If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the equals sign (if any). Parentheses are meaningful to most shells, ! so you will need to quote the option. With `sh' and `csh', ! `-D'NAME(ARGS...)=DEFINITION'' works. ! `-D' and `-U' options are processed in the order they are given on ! the command line. All `-imacros FILE' and `-include FILE' options ! are processed after all `-D' and `-U' options. ! `-U NAME' ! Cancel any previous definition of NAME, either built in or ! provided with a `-D' option. ! `-undef' Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. ! `-I DIR' ! Add the directory DIR to the list of directories to be searched ! for header files. Directories named by `-I' are searched before ! the standard system include directories. If the directory DIR is ! a standard system include directory, the option is ignored to ! ensure that the default search order for system directories and ! the special treatment of system headers are not defeated . If DIR ! begins with `=', then the `=' will be replaced by the sysroot ! prefix; see `--sysroot' and `-isysroot'. ! `-o FILE' Write output to FILE. This is the same as specifying FILE as the ! second non-option argument to `cpp'. `gcc' has a different interpretation of a second non-option argument, so you must use ! `-o' to specify the output file. ! `-Wall' Turns on all optional warnings which are desirable for normal code. ! At present this is `-Wcomment', `-Wtrigraphs', `-Wmultichar' and a ! warning about integer promotion causing a change of sign in `#if' expressions. Note that many of the preprocessor's warnings are on by default and have no options to control them. ! `-Wcomment' ! `-Wcomments' ! Warn whenever a comment-start sequence `/*' appears in a `/*' ! comment, or whenever a backslash-newline appears in a `//' comment. (Both forms have the same effect.) ! `-Wtrigraphs' Most trigraphs in comments cannot affect the meaning of the program. However, a trigraph that would form an escaped newline ! (`??/' at the end of a line) can, by changing where the comment begins or ends. Therefore, only trigraphs that would form escaped newlines produce warnings inside a comment. ! This option is implied by `-Wall'. If `-Wall' is not given, this option is still enabled unless trigraphs are enabled. To get ! trigraph conversion without warnings, but get the other `-Wall' ! warnings, use `-trigraphs -Wall -Wno-trigraphs'. ! `-Wtraditional' Warn about certain constructs that behave differently in traditional and ISO C. Also warn about ISO C constructs that have no traditional C equivalent, and problematic constructs which should be avoided. ! `-Wundef' Warn whenever an identifier which is not a macro is encountered in ! an `#if' directive, outside of `defined'. Such identifiers are replaced with zero. ! `-Wunused-macros' Warn about macros defined in the main file that are unused. A macro is "used" if it is expanded or tested for existence at least once. The preprocessor will also warn if the macro has not been *************** the preprocessor output to be unsuitable *** 9741,9749 **** #if defined the_macro_causing_the_warning #endif ! '-Wendif-labels' ! Warn whenever an '#else' or an '#endif' are followed by text. This ! usually happens in code of the form #if FOO ... --- 9786,9794 ---- #if defined the_macro_causing_the_warning #endif ! `-Wendif-labels' ! Warn whenever an `#else' or an `#endif' are followed by text. ! This usually happens in code of the form #if FOO ... *************** the preprocessor output to be unsuitable *** 9751,9842 **** ... #endif FOO ! The second and third 'FOO' should be in comments, but often are not in older programs. This warning is on by default. ! '-Werror' Make all warnings into hard errors. Source code which triggers warnings will be rejected. ! '-Wsystem-headers' Issue warnings for code in system headers. These are normally unhelpful in finding bugs in your own code, therefore suppressed. If you are responsible for the system library, you may want to see them. ! '-w' Suppress all warnings, including those which GNU CPP issues by default. ! '-pedantic' ! Issue all the mandatory diagnostics listed in the C standard. Some ! of them are left out by default, since they trigger frequently on ! harmless code. ! '-pedantic-errors' Issue all the mandatory diagnostics, and make all mandatory diagnostics into errors. This includes mandatory diagnostics that ! GCC issues without '-pedantic' but treats as warnings. ! '-M' Instead of outputting the result of preprocessing, output a rule ! suitable for 'make' describing the dependencies of the main source ! file. The preprocessor outputs one 'make' rule containing the object file name for that source file, a colon, and the names of ! all the included files, including those coming from '-include' or ! '-imacros' command-line options. ! Unless specified explicitly (with '-MT' or '-MQ'), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is ! split into several lines using '\'-newline. The rule has no commands. ! This option does not suppress the preprocessor's debug output, such ! as '-dM'. To avoid mixing such debug output with the dependency ! rules you should explicitly specify the dependency output file with ! '-MF', or use an environment variable like 'DEPENDENCIES_OUTPUT' ! (*note Environment Variables::). Debug output will still be sent ! to the regular output stream as normal. ! Passing '-M' to the driver implies '-E', and suppresses warnings ! with an implicit '-w'. ! '-MM' ! Like '-M' but do not mention header files that are found in system ! header directories, nor header files that are included, directly or ! indirectly, from such a header. This implies that the choice of angle brackets or double quotes in ! an '#include' directive does not in itself determine whether that ! header will appear in '-MM' dependency output. This is a slight change in semantics from GCC versions 3.0 and earlier. ! '-MF FILE' ! When used with '-M' or '-MM', specifies a file to write the ! dependencies to. If no '-MF' switch is given the preprocessor sends the rules to the same place it would have sent preprocessed output. ! When used with the driver options '-MD' or '-MMD', '-MF' overrides the default dependency output file. ! '-MG' ! In conjunction with an option such as '-M' requesting dependency ! generation, '-MG' assumes missing header files are generated files ! and adds them to the dependency list without raising an error. The ! dependency filename is taken directly from the '#include' directive ! without prepending any path. '-MG' also suppresses preprocessed ! output, as a missing header file renders this useless. This feature is used in automatic updating of makefiles. ! '-MP' This option instructs CPP to add a phony target for each dependency other than the main file, causing each to depend on nothing. These ! dummy rules work around errors 'make' gives if you remove header ! files without updating the 'Makefile' to match. This is typical output: --- 9796,9887 ---- ... #endif FOO ! The second and third `FOO' should be in comments, but often are not in older programs. This warning is on by default. ! `-Werror' Make all warnings into hard errors. Source code which triggers warnings will be rejected. ! `-Wsystem-headers' Issue warnings for code in system headers. These are normally unhelpful in finding bugs in your own code, therefore suppressed. If you are responsible for the system library, you may want to see them. ! `-w' Suppress all warnings, including those which GNU CPP issues by default. ! `-pedantic' ! Issue all the mandatory diagnostics listed in the C standard. ! Some of them are left out by default, since they trigger ! frequently on harmless code. ! `-pedantic-errors' Issue all the mandatory diagnostics, and make all mandatory diagnostics into errors. This includes mandatory diagnostics that ! GCC issues without `-pedantic' but treats as warnings. ! `-M' Instead of outputting the result of preprocessing, output a rule ! suitable for `make' describing the dependencies of the main source ! file. The preprocessor outputs one `make' rule containing the object file name for that source file, a colon, and the names of ! all the included files, including those coming from `-include' or ! `-imacros' command-line options. ! Unless specified explicitly (with `-MT' or `-MQ'), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is ! split into several lines using `\'-newline. The rule has no commands. ! This option does not suppress the preprocessor's debug output, ! such as `-dM'. To avoid mixing such debug output with the ! dependency rules you should explicitly specify the dependency ! output file with `-MF', or use an environment variable like ! `DEPENDENCIES_OUTPUT' (*note Environment Variables::). Debug ! output will still be sent to the regular output stream as normal. ! Passing `-M' to the driver implies `-E', and suppresses warnings ! with an implicit `-w'. ! `-MM' ! Like `-M' but do not mention header files that are found in system ! header directories, nor header files that are included, directly ! or indirectly, from such a header. This implies that the choice of angle brackets or double quotes in ! an `#include' directive does not in itself determine whether that ! header will appear in `-MM' dependency output. This is a slight change in semantics from GCC versions 3.0 and earlier. ! `-MF FILE' ! When used with `-M' or `-MM', specifies a file to write the ! dependencies to. If no `-MF' switch is given the preprocessor sends the rules to the same place it would have sent preprocessed output. ! When used with the driver options `-MD' or `-MMD', `-MF' overrides the default dependency output file. ! `-MG' ! In conjunction with an option such as `-M' requesting dependency ! generation, `-MG' assumes missing header files are generated files ! and adds them to the dependency list without raising an error. ! The dependency filename is taken directly from the `#include' ! directive without prepending any path. `-MG' also suppresses ! preprocessed output, as a missing header file renders this useless. This feature is used in automatic updating of makefiles. ! `-MP' This option instructs CPP to add a phony target for each dependency other than the main file, causing each to depend on nothing. These ! dummy rules work around errors `make' gives if you remove header ! files without updating the `Makefile' to match. This is typical output: *************** the preprocessor output to be unsuitable *** 9844,9895 **** test.h: ! '-MT TARGET' ! Change the target of the rule emitted by dependency generation. By default CPP takes the name of the main input file, deletes any ! directory components and any file suffix such as '.c', and appends the platform's usual object suffix. The result is the target. ! An '-MT' option will set the target to be exactly the string you specify. If you want multiple targets, you can specify them as a ! single argument to '-MT', or use multiple '-MT' options. ! For example, '-MT '$(objpfx)foo.o'' might give $(objpfx)foo.o: foo.c ! '-MQ TARGET' ! ! Same as '-MT', but it quotes any characters which are special to ! Make. '-MQ '$(objpfx)foo.o'' gives $$(objpfx)foo.o: foo.c The default target is automatically quoted, as if it were given ! with '-MQ'. ! '-MD' ! '-MD' is equivalent to '-M -MF FILE', except that '-E' is not ! implied. The driver determines FILE based on whether an '-o' ! option is given. If it is, the driver uses its argument but with a ! suffix of '.d', otherwise it takes the name of the input file, ! removes any directory components and suffix, and applies a '.d' suffix. ! If '-MD' is used in conjunction with '-E', any '-o' switch is understood to specify the dependency output file (*note -MF: ! dashMF.), but if used without '-E', each '-o' is understood to specify a target object file. ! Since '-E' is not implied, '-MD' can be used to generate a dependency output file as a side-effect of the compilation process. ! '-MMD' ! Like '-MD' except mention only user header files, not system header ! files. ! '-fpch-deps' When using precompiled headers (*note Precompiled Headers::), this flag will cause the dependency-output flags to also list the files from the precompiled header's dependencies. If not specified only --- 9889,9938 ---- test.h: ! `-MT TARGET' Change the target of the rule emitted by dependency generation. By default CPP takes the name of the main input file, deletes any ! directory components and any file suffix such as `.c', and appends the platform's usual object suffix. The result is the target. ! An `-MT' option will set the target to be exactly the string you specify. If you want multiple targets, you can specify them as a ! single argument to `-MT', or use multiple `-MT' options. ! For example, `-MT '$(objpfx)foo.o'' might give $(objpfx)foo.o: foo.c ! `-MQ TARGET' ! Same as `-MT', but it quotes any characters which are special to ! Make. `-MQ '$(objpfx)foo.o'' gives $$(objpfx)foo.o: foo.c The default target is automatically quoted, as if it were given ! with `-MQ'. ! `-MD' ! `-MD' is equivalent to `-M -MF FILE', except that `-E' is not ! implied. The driver determines FILE based on whether an `-o' ! option is given. If it is, the driver uses its argument but with ! a suffix of `.d', otherwise it takes the name of the input file, ! removes any directory components and suffix, and applies a `.d' suffix. ! If `-MD' is used in conjunction with `-E', any `-o' switch is understood to specify the dependency output file (*note -MF: ! dashMF.), but if used without `-E', each `-o' is understood to specify a target object file. ! Since `-E' is not implied, `-MD' can be used to generate a dependency output file as a side-effect of the compilation process. ! `-MMD' ! Like `-MD' except mention only user header files, not system ! header files. ! `-fpch-deps' When using precompiled headers (*note Precompiled Headers::), this flag will cause the dependency-output flags to also list the files from the precompiled header's dependencies. If not specified only *************** the preprocessor output to be unsuitable *** 9897,10313 **** used to create it because those files are not consulted when a precompiled header is used. ! '-fpch-preprocess' This option allows use of a precompiled header (*note Precompiled ! Headers::) together with '-E'. It inserts a special '#pragma', ! '#pragma GCC pch_preprocess "FILENAME"' in the output to mark the place where the precompiled header was found, and its FILENAME. ! When '-fpreprocessed' is in use, GCC recognizes this '#pragma' and loads the PCH. This option is off by default, because the resulting preprocessed output is only really suitable as input to GCC. It is switched on ! by '-save-temps'. ! You should not write this '#pragma' in your own code, but it is safe to edit the filename if the PCH file is available in a different location. The filename may be absolute or it may be relative to GCC's current directory. ! '-x c' ! '-x c++' ! '-x objective-c' ! '-x assembler-with-cpp' Specify the source language: C, C++, Objective-C, or assembly. ! This has nothing to do with standards conformance or extensions; it ! merely selects which base syntax to expect. If you give none of ! these options, cpp will deduce the language from the extension of ! the source file: '.c', '.cc', '.m', or '.S'. Some other common extensions for C++ and assembly are also recognized. If cpp does not recognize the extension, it will treat the file as C; this is the most generic mode. ! _Note:_ Previous versions of cpp accepted a '-lang' option which selected both the language and the standards conformance level. ! This option has been removed, because it conflicts with the '-l' option. ! '-std=STANDARD' ! '-ansi' Specify the standard to which the code should conform. Currently CPP knows about C and C++ standards; others may be added in the future. STANDARD may be one of: ! 'c90' ! 'c89' ! 'iso9899:1990' ! The ISO C standard from 1990. 'c90' is the customary shorthand for this version of the standard. ! The '-ansi' option is equivalent to '-std=c90'. ! 'iso9899:199409' The 1990 C standard, as amended in 1994. ! 'iso9899:1999' ! 'c99' ! 'iso9899:199x' ! 'c9x' The revised ISO C standard, published in December 1999. Before publication, this was known as C9X. ! 'iso9899:2011' ! 'c11' ! 'c1x' The revised ISO C standard, published in December 2011. Before publication, this was known as C1X. ! 'gnu90' ! 'gnu89' The 1990 C standard plus GNU extensions. This is the default. ! 'gnu99' ! 'gnu9x' The 1999 C standard plus GNU extensions. ! 'gnu11' ! 'gnu1x' The 2011 C standard plus GNU extensions. ! 'c++98' The 1998 ISO C++ standard plus amendments. ! 'gnu++98' ! The same as '-std=c++98' plus GNU extensions. This is the default for C++ code. ! '-I-' ! Split the include path. Any directories specified with '-I' ! options before '-I-' are searched only for headers requested with ! '#include "FILE"'; they are not searched for '#include '. If ! additional directories are specified with '-I' options after the ! '-I-', those directories are searched for all '#include' directives. ! In addition, '-I-' inhibits the use of the directory of the current ! file directory as the first search directory for '#include "FILE"'. This option has been deprecated. ! '-nostdinc' Do not search the standard system directories for header files. ! Only the directories you have specified with '-I' options (and the directory of the current file, if appropriate) are searched. ! '-nostdinc++' Do not search for header files in the C++-specific standard directories, but do still search the other standard directories. (This option is used when building the C++ library.) ! '-include FILE' ! Process FILE as if '#include "file"' appeared as the first line of ! the primary source file. However, the first directory searched for ! FILE is the preprocessor's working directory _instead of_ the directory containing the main source file. If not found there, it ! is searched for in the remainder of the '#include "..."' search chain as normal. ! If multiple '-include' options are given, the files are included in ! the order they appear on the command line. ! '-imacros FILE' ! Exactly like '-include', except that any output produced by scanning FILE is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its declarations. ! All files specified by '-imacros' are processed before all files ! specified by '-include'. ! '-idirafter DIR' Search DIR for header files, but do it _after_ all directories ! specified with '-I' and the standard system directories have been exhausted. DIR is treated as a system include directory. If DIR ! begins with '=', then the '=' will be replaced by the sysroot ! prefix; see '--sysroot' and '-isysroot'. ! '-iprefix PREFIX' ! Specify PREFIX as the prefix for subsequent '-iwithprefix' options. ! If the prefix represents a directory, you should include the final ! '/'. ! '-iwithprefix DIR' ! '-iwithprefixbefore DIR' ! Append DIR to the prefix specified previously with '-iprefix', and add the resulting directory to the include search path. ! '-iwithprefixbefore' puts it in the same place '-I' would; ! '-iwithprefix' puts it where '-idirafter' would. ! '-isysroot DIR' ! This option is like the '--sysroot' option, but applies only to header files (except for Darwin targets, where it applies to both ! header files and libraries). See the '--sysroot' option for more information. ! '-imultilib DIR' Use DIR as a subdirectory of the directory containing target-specific C++ headers. ! '-isystem DIR' Search DIR for header files, after all directories specified by ! '-I' but before the standard system directories. Mark it as a system directory, so that it gets the same special treatment as is applied to the standard system directories. If DIR begins with ! '=', then the '=' will be replaced by the sysroot prefix; see ! '--sysroot' and '-isysroot'. ! '-iquote DIR' ! Search DIR only for header files requested with '#include "FILE"'; ! they are not searched for '#include ', before all directories ! specified by '-I' and before the standard system directories. If ! DIR begins with '=', then the '=' will be replaced by the sysroot ! prefix; see '--sysroot' and '-isysroot'. ! '-fdirectives-only' When preprocessing, handle directives, but do not expand macros. ! The option's behavior depends on the '-E' and '-fpreprocessed' options. ! With '-E', preprocessing is limited to the handling of directives ! such as '#define', '#ifdef', and '#error'. Other preprocessor ! operations, such as macro expansion and trigraph conversion are not ! performed. In addition, the '-dD' option is implicitly enabled. ! With '-fpreprocessed', predefinition of command line and most ! builtin macros is disabled. Macros such as '__LINE__', which are contextually dependent, are handled normally. This enables ! compilation of files previously preprocessed with '-E -fdirectives-only'. ! With both '-E' and '-fpreprocessed', the rules for '-fpreprocessed' ! take precedence. This enables full preprocessing of files ! previously preprocessed with '-E -fdirectives-only'. ! '-fdollars-in-identifiers' ! Accept '$' in identifiers. ! '-fextended-identifiers' Accept universal character names in identifiers. This option is enabled by default for C99 (and later C standard versions) and C++. ! '-fno-canonical-system-headers' When preprocessing, do not shorten system header paths with canonicalization. ! '-fpreprocessed' Indicate to the preprocessor that the input file has already been preprocessed. This suppresses things like macro expansion, trigraph conversion, escaped newline splicing, and processing of most directives. The preprocessor still recognizes and removes ! comments, so that you can pass a file preprocessed with '-C' to the ! compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends. ! '-fpreprocessed' is implicit if the input file has one of the ! extensions '.i', '.ii' or '.mi'. These are the extensions that GCC ! uses for preprocessed files created by '-save-temps'. ! '-ftabstop=WIDTH' Set the distance between tab stops. This helps the preprocessor report correct column numbers in warnings or errors, even if tabs appear on the line. If the value is less than 1 or greater than 100, the option is ignored. The default is 8. ! '-fdebug-cpp' ! This option is only useful for debugging GCC. When used with '-E', ! dumps debugging information about location maps. Every token in ! the output is preceded by the dump of the map its location belongs ! to. The dump of the map holding the location of a token would be: ! {'P':/file/path;'F':/includer/path;'L':LINE_NUM;'C':COL_NUM;'S':SYSTEM_HEADER_P;'M':MAP_ADDRESS;'E':MACRO_EXPANSION_P,'loc':LOCATION} ! When used without '-E', this option has no effect. ! '-ftrack-macro-expansion[=LEVEL]' ! Track locations of tokens across macro expansions. This allows the compiler to emit diagnostic about the current macro expansion stack ! when a compilation error occurs in a macro expansion. Using this ! option makes the preprocessor and the compiler consume more memory. ! The LEVEL parameter can be used to choose the level of precision of ! token location tracking thus decreasing the memory consumption if ! necessary. Value '0' of LEVEL de-activates this option just as if ! no '-ftrack-macro-expansion' was present on the command line. ! Value '1' tracks tokens locations in a degraded mode for the sake ! of minimal memory overhead. In this mode all tokens resulting from ! the expansion of an argument of a function-like macro have the same ! location. Value '2' tracks tokens locations completely. This ! value is the most memory hungry. When this option is given no ! argument, the default parameter value is '2'. ! Note that '-ftrack-macro-expansion=2' is activated by default. ! '-fexec-charset=CHARSET' Set the execution character set, used for string and character constants. The default is UTF-8. CHARSET can be any encoding ! supported by the system's 'iconv' library routine. ! '-fwide-exec-charset=CHARSET' Set the wide execution character set, used for wide string and character constants. The default is UTF-32 or UTF-16, whichever ! corresponds to the width of 'wchar_t'. As with '-fexec-charset', ! CHARSET can be any encoding supported by the system's 'iconv' library routine; however, you will have problems with encodings ! that do not fit exactly in 'wchar_t'. ! '-finput-charset=CHARSET' Set the input character set, used for translation from the ! character set of the input file to the source character set used by ! GCC. If the locale does not specify, or GCC cannot get this information from the locale, the default is UTF-8. This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. CHARSET can be any encoding supported by the system's ! 'iconv' library routine. ! '-fworking-directory' Enable generation of linemarkers in the preprocessor output that will let the compiler know the current working directory at the time of preprocessing. When this option is enabled, the preprocessor will emit, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC will use this directory, when it's present in the ! preprocessed input, as the directory emitted as the current working ! directory in some debugging information formats. This option is ! implicitly enabled if debugging information is enabled, but this ! can be inhibited with the negated form '-fno-working-directory'. ! If the '-P' flag is present in the command line, this option has no ! effect, since no '#line' directives are emitted whatsoever. ! '-fno-show-column' Do not print column numbers in diagnostics. This may be necessary if diagnostics are being scanned by a program that does not ! understand the column numbers, such as 'dejagnu'. ! '-A PREDICATE=ANSWER' Make an assertion with the predicate PREDICATE and answer ANSWER. ! This form is preferred to the older form '-A PREDICATE(ANSWER)', which is still supported, because it does not use shell special characters. ! '-A -PREDICATE=ANSWER' Cancel an assertion with the predicate PREDICATE and answer ANSWER. ! '-dCHARS' ! CHARS is a sequence of one or more of the following characters, and ! must not be preceded by a space. Other characters are interpreted ! by the compiler proper, or reserved for future versions of GCC, and ! so are silently ignored. If you specify characters whose behavior ! conflicts, the result is undefined. ! 'M' ! Instead of the normal output, generate a list of '#define' directives for all the macros defined during the execution of ! the preprocessor, including predefined macros. This gives you ! a way of finding out what is predefined in your version of the ! preprocessor. Assuming you have no file 'foo.h', the command touch foo.h; cpp -dM foo.h will show all the predefined macros. ! If you use '-dM' without the '-E' option, '-dM' is interpreted ! as a synonym for '-fdump-rtl-mach'. *Note (gcc)Developer ! Options::. ! 'D' ! Like 'M' except in two respects: it does _not_ include the ! predefined macros, and it outputs _both_ the '#define' directives and the result of preprocessing. Both kinds of output go to the standard output file. ! 'N' ! Like 'D', but emit only the macro names, not their expansions. ! 'I' ! Output '#include' directives in addition to the result of preprocessing. ! 'U' ! Like 'D' except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and ! '#undef' directives are also output for macros tested but undefined at the time. ! '-P' Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. ! '-C' Do not discard comments. All comments are passed through to the ! output file, except for comments in processed directives, which are ! deleted along with the directive. ! You should be prepared for side effects when using '-C'; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no ! longer a '#'. ! '-CC' Do not discard comments, including during macro expansion. This is ! like '-C', except that comments contained within macros are also passed through to the output file where the macro is expanded. ! In addition to the side-effects of the '-C' option, the '-CC' ! option causes all C++-style comments inside a macro to be converted ! to C-style comments. This is to prevent later use of that macro ! from inadvertently commenting out the remainder of the source line. ! The '-CC' option is generally used to support lint comments. ! '-traditional-cpp' Try to imitate the behavior of old-fashioned C preprocessors, as opposed to ISO C preprocessors. ! '-trigraphs' Process trigraph sequences. These are three-character sequences, ! all starting with '??', that are defined by ISO C to stand for ! single characters. For example, '??/' stands for '\', so ''??/n'' is a character constant for a newline. By default, GCC ignores trigraphs, but in standard-conforming modes it converts them. See ! the '-std' and '-ansi' options. The nine trigraphs and their replacements are Trigraph: ??( ??) ??< ??> ??= ??/ ??' ??! ??- Replacement: [ ] { } # \ ^ | ~ ! '-remap' Enable special code to work around file systems which only permit very short file names, such as MS-DOS. ! '--help' ! '--target-help' Print text describing all the command-line options instead of preprocessing anything. ! '-v' Verbose mode. Print out GNU CPP's version number at the beginning of execution, and report the final form of the include path. ! '-H' Print the name of each header file used, in addition to other normal activities. Each name is indented to show how deep in the ! '#include' stack it is. Precompiled header files are also printed, ! even if they are found to be invalid; an invalid precompiled header ! file is printed with '...x' and a valid one with '...!' . ! '-version' ! '--version' Print out GNU CPP's version number. With one dash, proceed to preprocess as normal. With two dashes, exit immediately. --- 9940,10362 ---- used to create it because those files are not consulted when a precompiled header is used. ! `-fpch-preprocess' This option allows use of a precompiled header (*note Precompiled ! Headers::) together with `-E'. It inserts a special `#pragma', ! `#pragma GCC pch_preprocess "FILENAME"' in the output to mark the place where the precompiled header was found, and its FILENAME. ! When `-fpreprocessed' is in use, GCC recognizes this `#pragma' and loads the PCH. This option is off by default, because the resulting preprocessed output is only really suitable as input to GCC. It is switched on ! by `-save-temps'. ! You should not write this `#pragma' in your own code, but it is safe to edit the filename if the PCH file is available in a different location. The filename may be absolute or it may be relative to GCC's current directory. ! `-x c' ! `-x c++' ! `-x objective-c' ! `-x assembler-with-cpp' Specify the source language: C, C++, Objective-C, or assembly. ! This has nothing to do with standards conformance or extensions; ! it merely selects which base syntax to expect. If you give none ! of these options, cpp will deduce the language from the extension ! of the source file: `.c', `.cc', `.m', or `.S'. Some other common extensions for C++ and assembly are also recognized. If cpp does not recognize the extension, it will treat the file as C; this is the most generic mode. ! _Note:_ Previous versions of cpp accepted a `-lang' option which selected both the language and the standards conformance level. ! This option has been removed, because it conflicts with the `-l' option. ! `-std=STANDARD' ! `-ansi' Specify the standard to which the code should conform. Currently CPP knows about C and C++ standards; others may be added in the future. STANDARD may be one of: ! `c90' ! `c89' ! `iso9899:1990' ! The ISO C standard from 1990. `c90' is the customary shorthand for this version of the standard. ! The `-ansi' option is equivalent to `-std=c90'. ! `iso9899:199409' The 1990 C standard, as amended in 1994. ! `iso9899:1999' ! `c99' ! `iso9899:199x' ! `c9x' The revised ISO C standard, published in December 1999. Before publication, this was known as C9X. ! `iso9899:2011' ! `c11' ! `c1x' The revised ISO C standard, published in December 2011. Before publication, this was known as C1X. ! `gnu90' ! `gnu89' The 1990 C standard plus GNU extensions. This is the default. ! `gnu99' ! `gnu9x' The 1999 C standard plus GNU extensions. ! `gnu11' ! `gnu1x' The 2011 C standard plus GNU extensions. ! `c++98' The 1998 ISO C++ standard plus amendments. ! `gnu++98' ! The same as `-std=c++98' plus GNU extensions. This is the default for C++ code. ! `-I-' ! Split the include path. Any directories specified with `-I' ! options before `-I-' are searched only for headers requested with ! `#include "FILE"'; they are not searched for `#include '. ! If additional directories are specified with `-I' options after ! the `-I-', those directories are searched for all `#include' directives. ! In addition, `-I-' inhibits the use of the directory of the current ! file directory as the first search directory for `#include "FILE"'. This option has been deprecated. ! `-nostdinc' Do not search the standard system directories for header files. ! Only the directories you have specified with `-I' options (and the directory of the current file, if appropriate) are searched. ! `-nostdinc++' Do not search for header files in the C++-specific standard directories, but do still search the other standard directories. (This option is used when building the C++ library.) ! `-include FILE' ! Process FILE as if `#include "file"' appeared as the first line of ! the primary source file. However, the first directory searched ! for FILE is the preprocessor's working directory _instead of_ the directory containing the main source file. If not found there, it ! is searched for in the remainder of the `#include "..."' search chain as normal. ! If multiple `-include' options are given, the files are included ! in the order they appear on the command line. ! `-imacros FILE' ! Exactly like `-include', except that any output produced by scanning FILE is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its declarations. ! All files specified by `-imacros' are processed before all files ! specified by `-include'. ! `-idirafter DIR' Search DIR for header files, but do it _after_ all directories ! specified with `-I' and the standard system directories have been exhausted. DIR is treated as a system include directory. If DIR ! begins with `=', then the `=' will be replaced by the sysroot ! prefix; see `--sysroot' and `-isysroot'. ! `-iprefix PREFIX' ! Specify PREFIX as the prefix for subsequent `-iwithprefix' ! options. If the prefix represents a directory, you should include ! the final `/'. ! `-iwithprefix DIR' ! `-iwithprefixbefore DIR' ! Append DIR to the prefix specified previously with `-iprefix', and add the resulting directory to the include search path. ! `-iwithprefixbefore' puts it in the same place `-I' would; ! `-iwithprefix' puts it where `-idirafter' would. ! `-isysroot DIR' ! This option is like the `--sysroot' option, but applies only to header files (except for Darwin targets, where it applies to both ! header files and libraries). See the `--sysroot' option for more information. ! `-imultilib DIR' Use DIR as a subdirectory of the directory containing target-specific C++ headers. ! `-isystem DIR' Search DIR for header files, after all directories specified by ! `-I' but before the standard system directories. Mark it as a system directory, so that it gets the same special treatment as is applied to the standard system directories. If DIR begins with ! `=', then the `=' will be replaced by the sysroot prefix; see ! `--sysroot' and `-isysroot'. ! `-iquote DIR' ! Search DIR only for header files requested with `#include "FILE"'; ! they are not searched for `#include ', before all ! directories specified by `-I' and before the standard system ! directories. If DIR begins with `=', then the `=' will be replaced ! by the sysroot prefix; see `--sysroot' and `-isysroot'. ! `-fdirectives-only' When preprocessing, handle directives, but do not expand macros. ! The option's behavior depends on the `-E' and `-fpreprocessed' options. ! With `-E', preprocessing is limited to the handling of directives ! such as `#define', `#ifdef', and `#error'. Other preprocessor ! operations, such as macro expansion and trigraph conversion are ! not performed. In addition, the `-dD' option is implicitly ! enabled. ! With `-fpreprocessed', predefinition of command line and most ! builtin macros is disabled. Macros such as `__LINE__', which are contextually dependent, are handled normally. This enables ! compilation of files previously preprocessed with `-E -fdirectives-only'. ! With both `-E' and `-fpreprocessed', the rules for ! `-fpreprocessed' take precedence. This enables full preprocessing ! of files previously preprocessed with `-E -fdirectives-only'. ! `-fdollars-in-identifiers' ! Accept `$' in identifiers. ! `-fextended-identifiers' Accept universal character names in identifiers. This option is enabled by default for C99 (and later C standard versions) and C++. ! `-fno-canonical-system-headers' When preprocessing, do not shorten system header paths with canonicalization. ! `-fpreprocessed' Indicate to the preprocessor that the input file has already been preprocessed. This suppresses things like macro expansion, trigraph conversion, escaped newline splicing, and processing of most directives. The preprocessor still recognizes and removes ! comments, so that you can pass a file preprocessed with `-C' to ! the compiler without problems. In this mode the integrated preprocessor is little more than a tokenizer for the front ends. ! `-fpreprocessed' is implicit if the input file has one of the ! extensions `.i', `.ii' or `.mi'. These are the extensions that ! GCC uses for preprocessed files created by `-save-temps'. ! `-ftabstop=WIDTH' Set the distance between tab stops. This helps the preprocessor report correct column numbers in warnings or errors, even if tabs appear on the line. If the value is less than 1 or greater than 100, the option is ignored. The default is 8. ! `-fdebug-cpp' ! This option is only useful for debugging GCC. When used with ! `-E', dumps debugging information about location maps. Every ! token in the output is preceded by the dump of the map its location ! belongs to. The dump of the map holding the location of a token ! would be: ! {`P':`/file/path';`F':`/includer/path';`L':LINE_NUM;`C':COL_NUM;`S':SYSTEM_HEADER_P;`M':MAP_ADDRESS;`E':MACRO_EXPANSION_P,`loc':LOCATION} ! When used without `-E', this option has no effect. ! `-ftrack-macro-expansion[=LEVEL]' ! Track locations of tokens across macro expansions. This allows the compiler to emit diagnostic about the current macro expansion stack ! when a compilation error occurs in a macro expansion. Using this ! option makes the preprocessor and the compiler consume more ! memory. The LEVEL parameter can be used to choose the level of ! precision of token location tracking thus decreasing the memory ! consumption if necessary. Value `0' of LEVEL de-activates this ! option just as if no `-ftrack-macro-expansion' was present on the ! command line. Value `1' tracks tokens locations in a degraded mode ! for the sake of minimal memory overhead. In this mode all tokens ! resulting from the expansion of an argument of a function-like ! macro have the same location. Value `2' tracks tokens locations ! completely. This value is the most memory hungry. When this ! option is given no argument, the default parameter value is `2'. ! Note that `-ftrack-macro-expansion=2' is activated by default. ! `-fexec-charset=CHARSET' Set the execution character set, used for string and character constants. The default is UTF-8. CHARSET can be any encoding ! supported by the system's `iconv' library routine. ! `-fwide-exec-charset=CHARSET' Set the wide execution character set, used for wide string and character constants. The default is UTF-32 or UTF-16, whichever ! corresponds to the width of `wchar_t'. As with `-fexec-charset', ! CHARSET can be any encoding supported by the system's `iconv' library routine; however, you will have problems with encodings ! that do not fit exactly in `wchar_t'. ! `-finput-charset=CHARSET' Set the input character set, used for translation from the ! character set of the input file to the source character set used ! by GCC. If the locale does not specify, or GCC cannot get this information from the locale, the default is UTF-8. This can be overridden by either the locale or this command-line option. Currently the command-line option takes precedence if there's a conflict. CHARSET can be any encoding supported by the system's ! `iconv' library routine. ! `-fworking-directory' Enable generation of linemarkers in the preprocessor output that will let the compiler know the current working directory at the time of preprocessing. When this option is enabled, the preprocessor will emit, after the initial linemarker, a second linemarker with the current working directory followed by two slashes. GCC will use this directory, when it's present in the ! preprocessed input, as the directory emitted as the current ! working directory in some debugging information formats. This ! option is implicitly enabled if debugging information is enabled, ! but this can be inhibited with the negated form ! `-fno-working-directory'. If the `-P' flag is present in the ! command line, this option has no effect, since no `#line' ! directives are emitted whatsoever. ! `-fno-show-column' Do not print column numbers in diagnostics. This may be necessary if diagnostics are being scanned by a program that does not ! understand the column numbers, such as `dejagnu'. ! `-A PREDICATE=ANSWER' Make an assertion with the predicate PREDICATE and answer ANSWER. ! This form is preferred to the older form `-A PREDICATE(ANSWER)', which is still supported, because it does not use shell special characters. ! `-A -PREDICATE=ANSWER' Cancel an assertion with the predicate PREDICATE and answer ANSWER. ! `-dCHARS' ! CHARS is a sequence of one or more of the following characters, ! and must not be preceded by a space. Other characters are ! interpreted by the compiler proper, or reserved for future ! versions of GCC, and so are silently ignored. If you specify ! characters whose behavior conflicts, the result is undefined. ! `M' ! Instead of the normal output, generate a list of `#define' directives for all the macros defined during the execution of ! the preprocessor, including predefined macros. This gives ! you a way of finding out what is predefined in your version ! of the preprocessor. Assuming you have no file `foo.h', the ! command touch foo.h; cpp -dM foo.h will show all the predefined macros. ! If you use `-dM' without the `-E' option, `-dM' is ! interpreted as a synonym for `-fdump-rtl-mach'. *Note ! Developer Options: (gcc)Developer Options. ! `D' ! Like `M' except in two respects: it does _not_ include the ! predefined macros, and it outputs _both_ the `#define' directives and the result of preprocessing. Both kinds of output go to the standard output file. ! `N' ! Like `D', but emit only the macro names, not their expansions. ! `I' ! Output `#include' directives in addition to the result of preprocessing. ! `U' ! Like `D' except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and ! `#undef' directives are also output for macros tested but undefined at the time. ! `-P' Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. ! `-C' Do not discard comments. All comments are passed through to the ! output file, except for comments in processed directives, which ! are deleted along with the directive. ! You should be prepared for side effects when using `-C'; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no ! longer a `#'. ! `-CC' Do not discard comments, including during macro expansion. This is ! like `-C', except that comments contained within macros are also passed through to the output file where the macro is expanded. ! In addition to the side-effects of the `-C' option, the `-CC' ! option causes all C++-style comments inside a macro to be ! converted to C-style comments. This is to prevent later use of ! that macro from inadvertently commenting out the remainder of the ! source line. ! The `-CC' option is generally used to support lint comments. ! `-traditional-cpp' Try to imitate the behavior of old-fashioned C preprocessors, as opposed to ISO C preprocessors. ! `-trigraphs' Process trigraph sequences. These are three-character sequences, ! all starting with `??', that are defined by ISO C to stand for ! single characters. For example, `??/' stands for `\', so `'??/n'' is a character constant for a newline. By default, GCC ignores trigraphs, but in standard-conforming modes it converts them. See ! the `-std' and `-ansi' options. The nine trigraphs and their replacements are Trigraph: ??( ??) ??< ??> ??= ??/ ??' ??! ??- Replacement: [ ] { } # \ ^ | ~ ! `-remap' Enable special code to work around file systems which only permit very short file names, such as MS-DOS. ! `--help' ! `--target-help' Print text describing all the command-line options instead of preprocessing anything. ! `-v' Verbose mode. Print out GNU CPP's version number at the beginning of execution, and report the final form of the include path. ! `-H' Print the name of each header file used, in addition to other normal activities. Each name is indented to show how deep in the ! `#include' stack it is. Precompiled header files are also ! printed, even if they are found to be invalid; an invalid ! precompiled header file is printed with `...x' and a valid one ! with `...!' . ! `-version' ! `--version' Print out GNU CPP's version number. With one dash, proceed to preprocess as normal. With two dashes, exit immediately. *************** File: gcc.info, Node: Assembler Options *** 10319,10335 **** You can pass options to the assembler. ! '-Wa,OPTION' Pass OPTION as an option to the assembler. If OPTION contains commas, it is split into multiple options at the commas. ! '-Xassembler OPTION' Pass OPTION as an option to the assembler. You can use this to supply system-specific assembler options that GCC does not recognize. If you want to pass an option that takes an argument, you must use ! '-Xassembler' twice, once for the option and once for the argument.  File: gcc.info, Node: Link Options, Next: Directory Options, Prev: Assembler Options, Up: Invoking GCC --- 10368,10385 ---- You can pass options to the assembler. ! `-Wa,OPTION' Pass OPTION as an option to the assembler. If OPTION contains commas, it is split into multiple options at the commas. ! `-Xassembler OPTION' Pass OPTION as an option to the assembler. You can use this to supply system-specific assembler options that GCC does not recognize. If you want to pass an option that takes an argument, you must use ! `-Xassembler' twice, once for the option and once for the argument. !  File: gcc.info, Node: Link Options, Next: Directory Options, Prev: Assembler Options, Up: Invoking GCC *************** These options come into play when the co *** 10341,10622 **** an executable output file. They are meaningless if the compiler is not doing a link step. ! 'OBJECT-FILE-NAME' A file name that does not end in a special recognized suffix is considered to name an object file or library. (Object files are distinguished from libraries by the linker according to the file contents.) If linking is done, these object files are used as input to the linker. ! '-c' ! '-S' ! '-E' If any of these options is used, then the linker is not run, and object file names should not be used as arguments. *Note Overall Options::. ! '-fuse-ld=bfd' ! Use the 'bfd' linker instead of the default linker. ! '-fuse-ld=gold' ! Use the 'gold' linker instead of the default linker. ! '-lLIBRARY' ! '-l LIBRARY' Search the library named LIBRARY when linking. (The second alternative with the library as a separate argument is only for POSIX compliance and is not recommended.) It makes a difference where in the command you write this option; ! the linker searches and processes libraries and object files in the ! order they are specified. Thus, 'foo.o -lz bar.o' searches library ! 'z' after file 'foo.o' but before 'bar.o'. If 'bar.o' refers to ! functions in 'z', those functions may not be loaded. The linker searches a standard list of directories for the library, ! which is actually a file named 'libLIBRARY.a'. The linker then uses this file as if it had been specified precisely by name. The directories searched include several standard system ! directories plus any that you specify with '-L'. Normally the files found this way are library files--archive files ! whose members are object files. The linker handles an archive file ! by scanning through it for members which define symbols that have ! so far been referenced but not defined. But if the file that is ! found is an ordinary object file, it is linked in the usual ! fashion. The only difference between using an '-l' option and ! specifying a file name is that '-l' surrounds LIBRARY with 'lib' ! and '.a' and searches several directories. ! '-lobjc' ! You need this special case of the '-l' option in order to link an Objective-C or Objective-C++ program. ! '-nostartfiles' Do not use the standard system startup files when linking. The ! standard system libraries are used normally, unless '-nostdlib' or ! '-nodefaultlibs' is used. ! '-nodefaultlibs' Do not use the standard system libraries when linking. Only the libraries you specify are passed to the linker, and options specifying linkage of the system libraries, such as ! '-static-libgcc' or '-shared-libgcc', are ignored. The standard ! startup files are used normally, unless '-nostartfiles' is used. ! The compiler may generate calls to 'memcmp', 'memset', 'memcpy' and ! 'memmove'. These entries are usually resolved by entries in libc. ! These entry points should be supplied through some other mechanism ! when this option is specified. ! '-nostdlib' Do not use the standard system startup files or libraries when linking. No startup files and only the libraries you specify are passed to the linker, and options specifying linkage of the system ! libraries, such as '-static-libgcc' or '-shared-libgcc', are ignored. ! The compiler may generate calls to 'memcmp', 'memset', 'memcpy' and ! 'memmove'. These entries are usually resolved by entries in libc. ! These entry points should be supplied through some other mechanism ! when this option is specified. ! One of the standard libraries bypassed by '-nostdlib' and ! '-nodefaultlibs' is 'libgcc.a', a library of internal subroutines which GCC uses to overcome shortcomings of particular machines, or special needs for some languages. (*Note Interfacing to GCC ! Output: (gccint)Interface, for more discussion of 'libgcc.a'.) In ! most cases, you need 'libgcc.a' even when you want to avoid other ! standard libraries. In other words, when you specify '-nostdlib' ! or '-nodefaultlibs' you should usually specify '-lgcc' as well. This ensures that you have no unresolved references to internal GCC ! library subroutines. (An example of such an internal subroutine is ! '__main', used to ensure C++ constructors are called; *note ! 'collect2': (gccint)Collect2.) ! '-pie' Produce a position independent executable on targets that support ! it. For predictable results, you must also specify the same set of ! options used for compilation ('-fpie', '-fPIE', or model suboptions) when you specify this linker option. ! '-no-pie' Don't produce a position independent executable. ! '-rdynamic' ! Pass the flag '-export-dynamic' to the ELF linker, on targets that ! support it. This instructs the linker to add all symbols, not only ! used ones, to the dynamic symbol table. This option is needed for ! some uses of 'dlopen' or to allow obtaining backtraces from within a program. ! '-s' Remove all symbol table and relocation information from the executable. ! '-static' ! On systems that support dynamic linking, this prevents linking with ! the shared libraries. On other systems, this option has no effect. ! '-shared' ! Produce a shared object which can then be linked with other objects ! to form an executable. Not all systems support this option. For ! predictable results, you must also specify the same set of options ! used for compilation ('-fpic', '-fPIC', or model suboptions) when ! you specify this linker option.(1) ! '-shared-libgcc' ! '-static-libgcc' ! On systems that provide 'libgcc' as a shared library, these options force the use of either the shared or static version, respectively. ! If no shared version of 'libgcc' was built when the compiler was configured, these options have no effect. There are several situations in which an application should use the ! shared 'libgcc' instead of the static version. The most common of these is when the application wishes to throw and catch exceptions across different shared libraries. In that case, each of the libraries as well as the application itself should use the shared ! 'libgcc'. Therefore, the G++ and GCJ drivers automatically add ! '-shared-libgcc' whenever you build a shared library or a main ! executable, because C++ and Java programs typically use exceptions, ! so this is the right thing to do. ! If, instead, you use the GCC driver to create shared libraries, you ! may find that they are not always linked with the shared 'libgcc'. ! If GCC finds, at its configuration time, that you have a non-GNU ! linker or a GNU linker that does not support option ! '--eh-frame-hdr', it links the shared version of 'libgcc' into shared libraries by default. Otherwise, it takes advantage of the linker and optimizes away the linking with the shared version of ! 'libgcc', linking with the static version of libgcc by default. This allows exceptions to propagate through such shared libraries, without incurring relocation costs at library load time. However, if a library or main executable is supposed to throw or catch exceptions, you must link it using the G++ or GCJ driver, as appropriate for the languages used in the program, or using the ! option '-shared-libgcc', such that it is linked with the shared ! 'libgcc'. ! '-static-libasan' ! When the '-fsanitize=address' option is used to link a program, the ! GCC driver automatically links against 'libasan'. If 'libasan' is ! available as a shared library, and the '-static' option is not ! used, then this links against the shared version of 'libasan'. The ! '-static-libasan' option directs the GCC driver to link 'libasan' ! statically, without necessarily linking other libraries statically. ! '-static-libtsan' ! When the '-fsanitize=thread' option is used to link a program, the ! GCC driver automatically links against 'libtsan'. If 'libtsan' is ! available as a shared library, and the '-static' option is not ! used, then this links against the shared version of 'libtsan'. The ! '-static-libtsan' option directs the GCC driver to link 'libtsan' ! statically, without necessarily linking other libraries statically. ! '-static-liblsan' ! When the '-fsanitize=leak' option is used to link a program, the ! GCC driver automatically links against 'liblsan'. If 'liblsan' is ! available as a shared library, and the '-static' option is not ! used, then this links against the shared version of 'liblsan'. The ! '-static-liblsan' option directs the GCC driver to link 'liblsan' ! statically, without necessarily linking other libraries statically. ! '-static-libubsan' ! When the '-fsanitize=undefined' option is used to link a program, ! the GCC driver automatically links against 'libubsan'. If ! 'libubsan' is available as a shared library, and the '-static' option is not used, then this links against the shared version of ! 'libubsan'. The '-static-libubsan' option directs the GCC driver ! to link 'libubsan' statically, without necessarily linking other libraries statically. ! '-static-libmpx' ! When the '-fcheck-pointer bounds' and '-mmpx' options are used to link a program, the GCC driver automatically links against ! 'libmpx'. If 'libmpx' is available as a shared library, and the ! '-static' option is not used, then this links against the shared ! version of 'libmpx'. The '-static-libmpx' option directs the GCC ! driver to link 'libmpx' statically, without necessarily linking other libraries statically. ! '-static-libmpxwrappers' ! When the '-fcheck-pointer bounds' and '-mmpx' options are used to ! link a program without also using '-fno-chkp-use-wrappers', the GCC ! driver automatically links against 'libmpxwrappers'. If ! 'libmpxwrappers' is available as a shared library, and the ! '-static' option is not used, then this links against the shared ! version of 'libmpxwrappers'. The '-static-libmpxwrappers' option ! directs the GCC driver to link 'libmpxwrappers' statically, without ! necessarily linking other libraries statically. ! '-static-libstdc++' ! When the 'g++' program is used to link a C++ program, it normally ! automatically links against 'libstdc++'. If 'libstdc++' is ! available as a shared library, and the '-static' option is not ! used, then this links against the shared version of 'libstdc++'. That is normally fine. However, it is sometimes useful to freeze ! the version of 'libstdc++' used by the program without going all ! the way to a fully static link. The '-static-libstdc++' option ! directs the 'g++' driver to link 'libstdc++' statically, without necessarily linking other libraries statically. ! '-symbolic' Bind references to global symbols when building a shared object. ! Warn about any unresolved references (unless overridden by the link ! editor option '-Xlinker -z -Xlinker defs'). Only a few systems ! support this option. ! '-T SCRIPT' Use SCRIPT as the linker script. This option is supported by most systems using the GNU linker. On some targets, such as bare-board ! targets without an operating system, the '-T' option may be required when linking to avoid references to undefined symbols. ! '-Xlinker OPTION' ! Pass OPTION as an option to the linker. You can use this to supply ! system-specific linker options that GCC does not recognize. If you want to pass an option that takes a separate argument, you ! must use '-Xlinker' twice, once for the option and once for the ! argument. For example, to pass '-assert definitions', you must ! write '-Xlinker -assert -Xlinker definitions'. It does not work to ! write '-Xlinker "-assert definitions"', because this passes the entire string as a single argument, which is not what the linker expects. When using the GNU linker, it is usually more convenient to pass ! arguments to linker options using the 'OPTION=VALUE' syntax than as ! separate arguments. For example, you can specify '-Xlinker ! -Map=output.map' rather than '-Xlinker -Map -Xlinker output.map'. Other linkers may not support this syntax for command-line options. ! '-Wl,OPTION' ! Pass OPTION as an option to the linker. If OPTION contains commas, ! it is split into multiple options at the commas. You can use this ! syntax to pass an argument to the option. For example, ! '-Wl,-Map,output.map' passes '-Map output.map' to the linker. When ! using the GNU linker, you can also get the same effect with ! '-Wl,-Map=output.map'. ! '-u SYMBOL' ! Pretend the symbol SYMBOL is undefined, to force linking of library ! modules to define it. You can use '-u' multiple times with different symbols to force loading of additional library modules. ! '-z KEYWORD' ! '-z' is passed directly on to the linker along with the keyword ! KEYWORD. See the section in the documentation of your linker for permitted values and their meanings. ! ---------- Footnotes ---------- ! (1) On some systems, 'gcc -shared' needs to build supplementary stub ! code for constructors to work. On multi-libbed systems, 'gcc -shared' must select the correct support libraries to link against. Failing to supply the correct flags may lead to subtle defects. Supplying them in cases where they are not necessary is innocuous. --- 10391,10676 ---- an executable output file. They are meaningless if the compiler is not doing a link step. ! `OBJECT-FILE-NAME' A file name that does not end in a special recognized suffix is considered to name an object file or library. (Object files are distinguished from libraries by the linker according to the file contents.) If linking is done, these object files are used as input to the linker. ! `-c' ! `-S' ! `-E' If any of these options is used, then the linker is not run, and object file names should not be used as arguments. *Note Overall Options::. ! `-fuse-ld=bfd' ! Use the `bfd' linker instead of the default linker. ! `-fuse-ld=gold' ! Use the `gold' linker instead of the default linker. ! `-lLIBRARY' ! `-l LIBRARY' Search the library named LIBRARY when linking. (The second alternative with the library as a separate argument is only for POSIX compliance and is not recommended.) It makes a difference where in the command you write this option; ! the linker searches and processes libraries and object files in ! the order they are specified. Thus, `foo.o -lz bar.o' searches ! library `z' after file `foo.o' but before `bar.o'. If `bar.o' ! refers to functions in `z', those functions may not be loaded. The linker searches a standard list of directories for the library, ! which is actually a file named `libLIBRARY.a'. The linker then uses this file as if it had been specified precisely by name. The directories searched include several standard system ! directories plus any that you specify with `-L'. Normally the files found this way are library files--archive files ! whose members are object files. The linker handles an archive ! file by scanning through it for members which define symbols that ! have so far been referenced but not defined. But if the file that ! is found is an ordinary object file, it is linked in the usual ! fashion. The only difference between using an `-l' option and ! specifying a file name is that `-l' surrounds LIBRARY with `lib' ! and `.a' and searches several directories. ! `-lobjc' ! You need this special case of the `-l' option in order to link an Objective-C or Objective-C++ program. ! `-nostartfiles' Do not use the standard system startup files when linking. The ! standard system libraries are used normally, unless `-nostdlib' or ! `-nodefaultlibs' is used. ! `-nodefaultlibs' Do not use the standard system libraries when linking. Only the libraries you specify are passed to the linker, and options specifying linkage of the system libraries, such as ! `-static-libgcc' or `-shared-libgcc', are ignored. The standard ! startup files are used normally, unless `-nostartfiles' is used. ! The compiler may generate calls to `memcmp', `memset', `memcpy' ! and `memmove'. These entries are usually resolved by entries in ! libc. These entry points should be supplied through some other ! mechanism when this option is specified. ! `-nostdlib' Do not use the standard system startup files or libraries when linking. No startup files and only the libraries you specify are passed to the linker, and options specifying linkage of the system ! libraries, such as `-static-libgcc' or `-shared-libgcc', are ignored. ! The compiler may generate calls to `memcmp', `memset', `memcpy' ! and `memmove'. These entries are usually resolved by entries in ! libc. These entry points should be supplied through some other ! mechanism when this option is specified. ! One of the standard libraries bypassed by `-nostdlib' and ! `-nodefaultlibs' is `libgcc.a', a library of internal subroutines which GCC uses to overcome shortcomings of particular machines, or special needs for some languages. (*Note Interfacing to GCC ! Output: (gccint)Interface, for more discussion of `libgcc.a'.) In ! most cases, you need `libgcc.a' even when you want to avoid other ! standard libraries. In other words, when you specify `-nostdlib' ! or `-nodefaultlibs' you should usually specify `-lgcc' as well. This ensures that you have no unresolved references to internal GCC ! library subroutines. (An example of such an internal subroutine ! is `__main', used to ensure C++ constructors are called; *note ! `collect2': (gccint)Collect2.) ! `-pie' Produce a position independent executable on targets that support ! it. For predictable results, you must also specify the same set ! of options used for compilation (`-fpie', `-fPIE', or model suboptions) when you specify this linker option. ! `-no-pie' Don't produce a position independent executable. ! `-rdynamic' ! Pass the flag `-export-dynamic' to the ELF linker, on targets that ! support it. This instructs the linker to add all symbols, not only ! used ones, to the dynamic symbol table. This option is needed for ! some uses of `dlopen' or to allow obtaining backtraces from within a program. ! `-s' Remove all symbol table and relocation information from the executable. ! `-static' ! On systems that support dynamic linking, this prevents linking ! with the shared libraries. On other systems, this option has no ! effect. ! `-shared' ! Produce a shared object which can then be linked with other ! objects to form an executable. Not all systems support this ! option. For predictable results, you must also specify the same ! set of options used for compilation (`-fpic', `-fPIC', or model ! suboptions) when you specify this linker option.(1) ! `-shared-libgcc' ! `-static-libgcc' ! On systems that provide `libgcc' as a shared library, these options force the use of either the shared or static version, respectively. ! If no shared version of `libgcc' was built when the compiler was configured, these options have no effect. There are several situations in which an application should use the ! shared `libgcc' instead of the static version. The most common of these is when the application wishes to throw and catch exceptions across different shared libraries. In that case, each of the libraries as well as the application itself should use the shared ! `libgcc'. Therefore, the G++ and GCJ drivers automatically add ! `-shared-libgcc' whenever you build a shared library or a main ! executable, because C++ and Java programs typically use ! exceptions, so this is the right thing to do. ! If, instead, you use the GCC driver to create shared libraries, ! you may find that they are not always linked with the shared ! `libgcc'. If GCC finds, at its configuration time, that you have ! a non-GNU linker or a GNU linker that does not support option ! `--eh-frame-hdr', it links the shared version of `libgcc' into shared libraries by default. Otherwise, it takes advantage of the linker and optimizes away the linking with the shared version of ! `libgcc', linking with the static version of libgcc by default. This allows exceptions to propagate through such shared libraries, without incurring relocation costs at library load time. However, if a library or main executable is supposed to throw or catch exceptions, you must link it using the G++ or GCJ driver, as appropriate for the languages used in the program, or using the ! option `-shared-libgcc', such that it is linked with the shared ! `libgcc'. ! `-static-libasan' ! When the `-fsanitize=address' option is used to link a program, ! the GCC driver automatically links against `libasan'. If ! `libasan' is available as a shared library, and the `-static' ! option is not used, then this links against the shared version of ! `libasan'. The `-static-libasan' option directs the GCC driver to ! link `libasan' statically, without necessarily linking other ! libraries statically. ! `-static-libtsan' ! When the `-fsanitize=thread' option is used to link a program, the ! GCC driver automatically links against `libtsan'. If `libtsan' is ! available as a shared library, and the `-static' option is not ! used, then this links against the shared version of `libtsan'. ! The `-static-libtsan' option directs the GCC driver to link ! `libtsan' statically, without necessarily linking other libraries ! statically. ! `-static-liblsan' ! When the `-fsanitize=leak' option is used to link a program, the ! GCC driver automatically links against `liblsan'. If `liblsan' is ! available as a shared library, and the `-static' option is not ! used, then this links against the shared version of `liblsan'. ! The `-static-liblsan' option directs the GCC driver to link ! `liblsan' statically, without necessarily linking other libraries ! statically. ! `-static-libubsan' ! When the `-fsanitize=undefined' option is used to link a program, ! the GCC driver automatically links against `libubsan'. If ! `libubsan' is available as a shared library, and the `-static' option is not used, then this links against the shared version of ! `libubsan'. The `-static-libubsan' option directs the GCC driver ! to link `libubsan' statically, without necessarily linking other libraries statically. ! `-static-libmpx' ! When the `-fcheck-pointer bounds' and `-mmpx' options are used to link a program, the GCC driver automatically links against ! `libmpx'. If `libmpx' is available as a shared library, and the ! `-static' option is not used, then this links against the shared ! version of `libmpx'. The `-static-libmpx' option directs the GCC ! driver to link `libmpx' statically, without necessarily linking other libraries statically. ! `-static-libmpxwrappers' ! When the `-fcheck-pointer bounds' and `-mmpx' options are used to ! link a program without also using `-fno-chkp-use-wrappers', the ! GCC driver automatically links against `libmpxwrappers'. If ! `libmpxwrappers' is available as a shared library, and the ! `-static' option is not used, then this links against the shared ! version of `libmpxwrappers'. The `-static-libmpxwrappers' option ! directs the GCC driver to link `libmpxwrappers' statically, ! without necessarily linking other libraries statically. ! `-static-libstdc++' ! When the `g++' program is used to link a C++ program, it normally ! automatically links against `libstdc++'. If `libstdc++' is ! available as a shared library, and the `-static' option is not ! used, then this links against the shared version of `libstdc++'. That is normally fine. However, it is sometimes useful to freeze ! the version of `libstdc++' used by the program without going all ! the way to a fully static link. The `-static-libstdc++' option ! directs the `g++' driver to link `libstdc++' statically, without necessarily linking other libraries statically. ! `-symbolic' Bind references to global symbols when building a shared object. ! Warn about any unresolved references (unless overridden by the ! link editor option `-Xlinker -z -Xlinker defs'). Only a few ! systems support this option. ! `-T SCRIPT' Use SCRIPT as the linker script. This option is supported by most systems using the GNU linker. On some targets, such as bare-board ! targets without an operating system, the `-T' option may be required when linking to avoid references to undefined symbols. ! `-Xlinker OPTION' ! Pass OPTION as an option to the linker. You can use this to ! supply system-specific linker options that GCC does not recognize. If you want to pass an option that takes a separate argument, you ! must use `-Xlinker' twice, once for the option and once for the ! argument. For example, to pass `-assert definitions', you must ! write `-Xlinker -assert -Xlinker definitions'. It does not work ! to write `-Xlinker "-assert definitions"', because this passes the entire string as a single argument, which is not what the linker expects. When using the GNU linker, it is usually more convenient to pass ! arguments to linker options using the `OPTION=VALUE' syntax than ! as separate arguments. For example, you can specify `-Xlinker ! -Map=output.map' rather than `-Xlinker -Map -Xlinker output.map'. Other linkers may not support this syntax for command-line options. ! `-Wl,OPTION' ! Pass OPTION as an option to the linker. If OPTION contains ! commas, it is split into multiple options at the commas. You can ! use this syntax to pass an argument to the option. For example, ! `-Wl,-Map,output.map' passes `-Map output.map' to the linker. ! When using the GNU linker, you can also get the same effect with ! `-Wl,-Map=output.map'. ! `-u SYMBOL' ! Pretend the symbol SYMBOL is undefined, to force linking of ! library modules to define it. You can use `-u' multiple times with different symbols to force loading of additional library modules. ! `-z KEYWORD' ! `-z' is passed directly on to the linker along with the keyword ! KEYWORD. See the section in the documentation of your linker for permitted values and their meanings. ! ---------- Footnotes ---------- ! (1) On some systems, `gcc -shared' needs to build supplementary stub ! code for constructors to work. On multi-libbed systems, `gcc -shared' must select the correct support libraries to link against. Failing to supply the correct flags may lead to subtle defects. Supplying them in cases where they are not necessary is innocuous. *************** File: gcc.info, Node: Directory Options *** 10630,10758 **** These options specify directories to search for header files, for libraries and for parts of the compiler: ! '-IDIR' Add the directory DIR to the head of the list of directories to be searched for header files. This can be used to override a system ! header file, substituting your own version, since these directories ! are searched before the system header file directories. However, ! you should not use this option to add directories that contain ! vendor-supplied system header files (use '-isystem' for that). If ! you use more than one '-I' option, the directories are scanned in ! left-to-right order; the standard system directories come after. If a standard system include directory, or a directory specified ! with '-isystem', is also specified with '-I', the '-I' option is ! ignored. The directory is still searched but as a system directory ! at its normal position in the system include chain. This is to ! ensure that GCC's procedure to fix buggy system headers and the ! ordering for the 'include_next' directive are not inadvertently ! changed. If you really need to change the search order for system ! directories, use the '-nostdinc' and/or '-isystem' options. ! '-iplugindir=DIR' Set the directory to search for plugins that are passed by ! '-fplugin=NAME' instead of '-fplugin=PATH/NAME.so'. This option is ! not meant to be used by the user, but only passed by the driver. ! '-iquoteDIR' Add the directory DIR to the head of the list of directories to be ! searched for header files only for the case of '#include "FILE"'; ! they are not searched for '#include ', otherwise just like ! '-I'. ! '-LDIR' Add directory DIR to the list of directories to be searched for ! '-l'. ! '-BPREFIX' This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. The compiler driver program runs one or more of the subprograms ! 'cpp', 'cc1', 'as' and 'ld'. It tries PREFIX as a prefix for each ! program it tries to run, both with and without 'MACHINE/VERSION/' for the corresponding target machine and compiler version. For each subprogram to be run, the compiler driver first tries the ! '-B' prefix, if any. If that name is not found, or if '-B' is not ! specified, the driver tries two standard prefixes, '/usr/lib/gcc/' ! and '/usr/local/lib/gcc/'. If neither of those results in a file name that is found, the unmodified program name is searched for ! using the directories specified in your 'PATH' environment variable. ! The compiler checks to see if the path provided by '-B' refers to a ! directory, and if necessary it adds a directory separator character ! at the end of the path. ! '-B' prefixes that effectively specify directory names also apply to libraries in the linker, because the compiler translates these ! options into '-L' options for the linker. They also apply to include files in the preprocessor, because the compiler translates ! these options into '-isystem' options for the preprocessor. In ! this case, the compiler appends 'include' to the prefix. ! The runtime support file 'libgcc.a' can also be searched for using ! the '-B' prefix, if needed. If it is not found there, the two standard prefixes above are tried, and that is all. The file is left out of the link if it is not found by those means. ! Another way to specify a prefix much like the '-B' prefix is to use ! the environment variable 'GCC_EXEC_PREFIX'. *Note Environment Variables::. ! As a special kludge, if the path provided by '-B' is ! '[dir/]stageN/', where N is a number in the range 0 to 9, then it ! is replaced by '[dir/]include'. This is to help with boot-strapping the compiler. ! '-no-canonical-prefixes' ! Do not expand any symbolic links, resolve references to '/../' or ! '/./', or make the path absolute when generating a relative prefix. ! '--sysroot=DIR' Use DIR as the logical root directory for headers and libraries. For example, if the compiler normally searches for headers in ! '/usr/include' and libraries in '/usr/lib', it instead searches ! 'DIR/usr/include' and 'DIR/usr/lib'. ! If you use both this option and the '-isysroot' option, then the ! '--sysroot' option applies to libraries, but the '-isysroot' option ! applies to header files. The GNU linker (beginning with version 2.16) has the necessary support for this option. If your linker does not support this ! option, the header file aspect of '--sysroot' still works, but the library aspect does not. ! '--no-sysroot-suffix' For some targets, a suffix is added to the root directory specified ! with '--sysroot', depending on the other options used, so that ! headers may for example be found in 'DIR/SUFFIX/usr/include' ! instead of 'DIR/usr/include'. This option disables the addition of such a suffix. ! '-I-' ! This option has been deprecated. Please use '-iquote' instead for ! '-I' directories before the '-I-' and remove the '-I-' option. Any ! directories you specify with '-I' options before the '-I-' option ! are searched only for the case of '#include "FILE"'; they are not ! searched for '#include '. ! If additional directories are specified with '-I' options after the ! '-I-' option, these directories are searched for all '#include' ! directives. (Ordinarily _all_ '-I' directories are used this way.) ! In addition, the '-I-' option inhibits the use of the current directory (where the current input file came from) as the first ! search directory for '#include "FILE"'. There is no way to ! override this effect of '-I-'. With '-I.' you can specify searching the directory that is current when the compiler is invoked. That is not exactly the same as what the preprocessor does by default, but it is often satisfactory. ! '-I-' does not inhibit the use of the standard system directories ! for header files. Thus, '-I-' and '-nostdinc' are independent.  File: gcc.info, Node: Code Gen Options, Next: Developer Options, Prev: Directory Options, Up: Invoking GCC --- 10684,10814 ---- These options specify directories to search for header files, for libraries and for parts of the compiler: ! `-IDIR' Add the directory DIR to the head of the list of directories to be searched for header files. This can be used to override a system ! header file, substituting your own version, since these ! directories are searched before the system header file ! directories. However, you should not use this option to add ! directories that contain vendor-supplied system header files (use ! `-isystem' for that). If you use more than one `-I' option, the ! directories are scanned in left-to-right order; the standard ! system directories come after. If a standard system include directory, or a directory specified ! with `-isystem', is also specified with `-I', the `-I' option is ! ignored. The directory is still searched but as a system ! directory at its normal position in the system include chain. ! This is to ensure that GCC's procedure to fix buggy system headers ! and the ordering for the `include_next' directive are not ! inadvertently changed. If you really need to change the search ! order for system directories, use the `-nostdinc' and/or ! `-isystem' options. ! `-iplugindir=DIR' Set the directory to search for plugins that are passed by ! `-fplugin=NAME' instead of `-fplugin=PATH/NAME.so'. This option ! is not meant to be used by the user, but only passed by the driver. ! `-iquoteDIR' Add the directory DIR to the head of the list of directories to be ! searched for header files only for the case of `#include "FILE"'; ! they are not searched for `#include ', otherwise just like ! `-I'. ! `-LDIR' Add directory DIR to the list of directories to be searched for ! `-l'. ! `-BPREFIX' This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. The compiler driver program runs one or more of the subprograms ! `cpp', `cc1', `as' and `ld'. It tries PREFIX as a prefix for each ! program it tries to run, both with and without `MACHINE/VERSION/' for the corresponding target machine and compiler version. For each subprogram to be run, the compiler driver first tries the ! `-B' prefix, if any. If that name is not found, or if `-B' is not ! specified, the driver tries two standard prefixes, `/usr/lib/gcc/' ! and `/usr/local/lib/gcc/'. If neither of those results in a file name that is found, the unmodified program name is searched for ! using the directories specified in your `PATH' environment variable. ! The compiler checks to see if the path provided by `-B' refers to ! a directory, and if necessary it adds a directory separator ! character at the end of the path. ! `-B' prefixes that effectively specify directory names also apply to libraries in the linker, because the compiler translates these ! options into `-L' options for the linker. They also apply to include files in the preprocessor, because the compiler translates ! these options into `-isystem' options for the preprocessor. In ! this case, the compiler appends `include' to the prefix. ! The runtime support file `libgcc.a' can also be searched for using ! the `-B' prefix, if needed. If it is not found there, the two standard prefixes above are tried, and that is all. The file is left out of the link if it is not found by those means. ! Another way to specify a prefix much like the `-B' prefix is to use ! the environment variable `GCC_EXEC_PREFIX'. *Note Environment Variables::. ! As a special kludge, if the path provided by `-B' is ! `[dir/]stageN/', where N is a number in the range 0 to 9, then it ! is replaced by `[dir/]include'. This is to help with boot-strapping the compiler. ! `-no-canonical-prefixes' ! Do not expand any symbolic links, resolve references to `/../' or ! `/./', or make the path absolute when generating a relative prefix. ! `--sysroot=DIR' Use DIR as the logical root directory for headers and libraries. For example, if the compiler normally searches for headers in ! `/usr/include' and libraries in `/usr/lib', it instead searches ! `DIR/usr/include' and `DIR/usr/lib'. ! If you use both this option and the `-isysroot' option, then the ! `--sysroot' option applies to libraries, but the `-isysroot' ! option applies to header files. The GNU linker (beginning with version 2.16) has the necessary support for this option. If your linker does not support this ! option, the header file aspect of `--sysroot' still works, but the library aspect does not. ! `--no-sysroot-suffix' For some targets, a suffix is added to the root directory specified ! with `--sysroot', depending on the other options used, so that ! headers may for example be found in `DIR/SUFFIX/usr/include' ! instead of `DIR/usr/include'. This option disables the addition of such a suffix. ! `-I-' ! This option has been deprecated. Please use `-iquote' instead for ! `-I' directories before the `-I-' and remove the `-I-' option. ! Any directories you specify with `-I' options before the `-I-' ! option are searched only for the case of `#include "FILE"'; they ! are not searched for `#include '. ! If additional directories are specified with `-I' options after ! the `-I-' option, these directories are searched for all `#include' ! directives. (Ordinarily _all_ `-I' directories are used this way.) ! In addition, the `-I-' option inhibits the use of the current directory (where the current input file came from) as the first ! search directory for `#include "FILE"'. There is no way to ! override this effect of `-I-'. With `-I.' you can specify searching the directory that is current when the compiler is invoked. That is not exactly the same as what the preprocessor does by default, but it is often satisfactory. ! `-I-' does not inhibit the use of the standard system directories ! for header files. Thus, `-I-' and `-nostdinc' are independent.  File: gcc.info, Node: Code Gen Options, Next: Developer Options, Prev: Directory Options, Up: Invoking GCC *************** File: gcc.info, Node: Code Gen Options, *** 10760,10788 **** 3.16 Options for Code Generation Conventions ============================================ ! These machine-independent options control the interface conventions used ! in code generation. Most of them have both positive and negative forms; the negative form ! of '-ffoo' is '-fno-foo'. In the table below, only one of the forms is listed--the one that is not the default. You can figure out the other ! form by either removing 'no-' or adding it. ! '-fstack-reuse=REUSE-LEVEL' ! This option controls stack space reuse for user declared local/auto ! variables and compiler generated temporaries. REUSE_LEVEL can be ! 'all', 'named_vars', or 'none'. 'all' enables stack reuse for all ! local variables and temporaries, 'named_vars' enables the reuse ! only for user defined local variables with names, and 'none' ! disables stack reuse completely. The default value is 'all'. The ! option is needed when the program extends the lifetime of a scoped ! local variable or a compiler generated temporary beyond the end ! point defined by the language. When a lifetime of a variable ends, ! and if the variable lives in memory, the optimizing compiler has ! the freedom to reuse its stack space with other temporaries or ! scoped local variables whose live range does not overlap with it. ! Legacy code extending local lifetime is likely to break with the ! stack reuse optimization. For example, --- 10816,10844 ---- 3.16 Options for Code Generation Conventions ============================================ ! These machine-independent options control the interface conventions ! used in code generation. Most of them have both positive and negative forms; the negative form ! of `-ffoo' is `-fno-foo'. In the table below, only one of the forms is listed--the one that is not the default. You can figure out the other ! form by either removing `no-' or adding it. ! `-fstack-reuse=REUSE-LEVEL' ! This option controls stack space reuse for user declared ! local/auto variables and compiler generated temporaries. ! REUSE_LEVEL can be `all', `named_vars', or `none'. `all' enables ! stack reuse for all local variables and temporaries, `named_vars' ! enables the reuse only for user defined local variables with ! names, and `none' disables stack reuse completely. The default ! value is `all'. The option is needed when the program extends the ! lifetime of a scoped local variable or a compiler generated ! temporary beyond the end point defined by the language. When a ! lifetime of a variable ends, and if the variable lives in memory, ! the optimizing compiler has the freedom to reuse its stack space ! with other temporaries or scoped local variables whose live range ! does not overlap with it. Legacy code extending local lifetime is ! likely to break with the stack reuse optimization. For example, *************** form by either removing 'no-' or adding *** 10833,10892 **** // is reused with a. What is the value of ap->i? } - The lifetime of a compiler generated temporary is well defined by ! the C++ standard. When a lifetime of a temporary ends, and if the temporary lives in memory, the optimizing compiler has the freedom to reuse its stack space with other temporaries or scoped local ! variables whose live range does not overlap with it. However some of the legacy code relies on the behavior of older compilers in which temporaries' stack space is not reused, the aggressive stack ! reuse can lead to runtime errors. This option is used to control the temporary stack reuse optimization. ! '-ftrapv' This option generates traps for signed overflow on addition, ! subtraction, multiplication operations. The options '-ftrapv' and ! '-fwrapv' override each other, so using '-ftrapv' '-fwrapv' on the ! command-line results in '-fwrapv' being effective. Note that only ! active options override, so using '-ftrapv' '-fwrapv' '-fno-wrapv' ! on the command-line results in '-ftrapv' being effective. ! '-fwrapv' This option instructs the compiler to assume that signed arithmetic overflow of addition, subtraction and multiplication wraps around using twos-complement representation. This flag enables some optimizations and disables others. This option is enabled by default for the Java front end, as required by the Java language ! specification. The options '-ftrapv' and '-fwrapv' override each ! other, so using '-ftrapv' '-fwrapv' on the command-line results in ! '-fwrapv' being effective. Note that only active options override, ! so using '-ftrapv' '-fwrapv' '-fno-wrapv' on the command-line ! results in '-ftrapv' being effective. ! '-fexceptions' Enable exception handling. Generates extra code needed to ! propagate exceptions. For some targets, this implies GCC generates ! frame unwind information for all functions, which can produce ! significant data size overhead, although it does not affect ! execution. If you do not specify this option, GCC enables it by ! default for languages like C++ that normally require exception ! handling, and disables it for languages like C that do not normally ! require it. However, you may need to enable this option when ! compiling C code that needs to interoperate properly with exception ! handlers written in C++. You may also wish to disable this option ! if you are compiling older C++ programs that don't use exception ! handling. ! '-fnon-call-exceptions' Generate code that allows trapping instructions to throw exceptions. Note that this requires platform-specific runtime support that does not exist everywhere. Moreover, it only allows ! _trapping_ instructions to throw exceptions, i.e. memory references ! or floating-point instructions. It does not allow exceptions to be ! thrown from arbitrary signal handlers such as 'SIGALRM'. ! '-fdelete-dead-exceptions' Consider that instructions that may throw exceptions but don't otherwise contribute to the execution of the program can be optimized away. This option is enabled by default for the Ada --- 10889,10948 ---- // is reused with a. What is the value of ap->i? } The lifetime of a compiler generated temporary is well defined by ! the C++ standard. When a lifetime of a temporary ends, and if the temporary lives in memory, the optimizing compiler has the freedom to reuse its stack space with other temporaries or scoped local ! variables whose live range does not overlap with it. However some of the legacy code relies on the behavior of older compilers in which temporaries' stack space is not reused, the aggressive stack ! reuse can lead to runtime errors. This option is used to control the temporary stack reuse optimization. ! `-ftrapv' This option generates traps for signed overflow on addition, ! subtraction, multiplication operations. The options `-ftrapv' and ! `-fwrapv' override each other, so using `-ftrapv' `-fwrapv' on the ! command-line results in `-fwrapv' being effective. Note that only ! active options override, so using `-ftrapv' `-fwrapv' `-fno-wrapv' ! on the command-line results in `-ftrapv' being effective. ! `-fwrapv' This option instructs the compiler to assume that signed arithmetic overflow of addition, subtraction and multiplication wraps around using twos-complement representation. This flag enables some optimizations and disables others. This option is enabled by default for the Java front end, as required by the Java language ! specification. The options `-ftrapv' and `-fwrapv' override each ! other, so using `-ftrapv' `-fwrapv' on the command-line results in ! `-fwrapv' being effective. Note that only active options ! override, so using `-ftrapv' `-fwrapv' `-fno-wrapv' on the ! command-line results in `-ftrapv' being effective. ! `-fexceptions' Enable exception handling. Generates extra code needed to ! propagate exceptions. For some targets, this implies GCC ! generates frame unwind information for all functions, which can ! produce significant data size overhead, although it does not ! affect execution. If you do not specify this option, GCC enables ! it by default for languages like C++ that normally require ! exception handling, and disables it for languages like C that do ! not normally require it. However, you may need to enable this ! option when compiling C code that needs to interoperate properly ! with exception handlers written in C++. You may also wish to ! disable this option if you are compiling older C++ programs that ! don't use exception handling. ! `-fnon-call-exceptions' Generate code that allows trapping instructions to throw exceptions. Note that this requires platform-specific runtime support that does not exist everywhere. Moreover, it only allows ! _trapping_ instructions to throw exceptions, i.e. memory ! references or floating-point instructions. It does not allow ! exceptions to be thrown from arbitrary signal handlers such as ! `SIGALRM'. ! `-fdelete-dead-exceptions' Consider that instructions that may throw exceptions but don't otherwise contribute to the execution of the program can be optimized away. This option is enabled by default for the Ada *************** form by either removing 'no-' or adding *** 10894,10931 **** Optimization passes that cause dead exceptions to be removed are enabled independently at different optimization levels. ! '-funwind-tables' ! Similar to '-fexceptions', except that it just generates any needed static data, but does not affect the generated code in any other way. You normally do not need to enable this option; instead, a language processor that needs this handling enables it on your behalf. ! '-fasynchronous-unwind-tables' Generate unwind table in DWARF format, if supported by target machine. The table is exact at each instruction boundary, so it can be used for stack unwinding from asynchronous events (such as debugger or garbage collector). ! '-fno-gnu-unique' On systems with recent GNU assembler and C library, the C++ ! compiler uses the 'STB_GNU_UNIQUE' binding to make sure that definitions of template static data members and static local variables in inline functions are unique even in the presence of ! 'RTLD_LOCAL'; this is necessary to avoid problems with a library ! used by two different 'RTLD_LOCAL' plugins depending on a definition in one of them and therefore disagreeing with the other ! one about the binding of the symbol. But this causes 'dlclose' to be ignored for affected DSOs; if your program relies on ! reinitialization of a DSO via 'dlclose' and 'dlopen', you can use ! '-fno-gnu-unique'. ! '-fpcc-struct-return' ! Return "short" 'struct' and 'union' values in memory like longer ! ones, rather than in registers. This convention is less efficient, ! but it has the advantage of allowing intercallability between ! GCC-compiled files and files compiled with other compilers, ! particularly the Portable C Compiler (pcc). The precise convention for returning structures in memory depends on the target configuration macros. --- 10950,10987 ---- Optimization passes that cause dead exceptions to be removed are enabled independently at different optimization levels. ! `-funwind-tables' ! Similar to `-fexceptions', except that it just generates any needed static data, but does not affect the generated code in any other way. You normally do not need to enable this option; instead, a language processor that needs this handling enables it on your behalf. ! `-fasynchronous-unwind-tables' Generate unwind table in DWARF format, if supported by target machine. The table is exact at each instruction boundary, so it can be used for stack unwinding from asynchronous events (such as debugger or garbage collector). ! `-fno-gnu-unique' On systems with recent GNU assembler and C library, the C++ ! compiler uses the `STB_GNU_UNIQUE' binding to make sure that definitions of template static data members and static local variables in inline functions are unique even in the presence of ! `RTLD_LOCAL'; this is necessary to avoid problems with a library ! used by two different `RTLD_LOCAL' plugins depending on a definition in one of them and therefore disagreeing with the other ! one about the binding of the symbol. But this causes `dlclose' to be ignored for affected DSOs; if your program relies on ! reinitialization of a DSO via `dlclose' and `dlopen', you can use ! `-fno-gnu-unique'. ! `-fpcc-struct-return' ! Return "short" `struct' and `union' values in memory like longer ! ones, rather than in registers. This convention is less ! efficient, but it has the advantage of allowing intercallability ! between GCC-compiled files and files compiled with other ! compilers, particularly the Portable C Compiler (pcc). The precise convention for returning structures in memory depends on the target configuration macros. *************** form by either removing 'no-' or adding *** 10933,11032 **** Short structures and unions are those whose size and alignment match that of some integer type. ! *Warning:* code compiled with the '-fpcc-struct-return' switch is not binary compatible with code compiled with the ! '-freg-struct-return' switch. Use it to conform to a non-default application binary interface. ! '-freg-struct-return' ! Return 'struct' and 'union' values in registers when possible. This is more efficient for small structures than ! '-fpcc-struct-return'. ! If you specify neither '-fpcc-struct-return' nor ! '-freg-struct-return', GCC defaults to whichever convention is standard for the target. If there is no standard convention, GCC ! defaults to '-fpcc-struct-return', except on targets where GCC is the principal compiler. In those cases, we can choose the standard, and we chose the more efficient register return alternative. ! *Warning:* code compiled with the '-freg-struct-return' switch is not binary compatible with code compiled with the ! '-fpcc-struct-return' switch. Use it to conform to a non-default application binary interface. ! '-fshort-enums' ! Allocate to an 'enum' type only as many bytes as it needs for the ! declared range of possible values. Specifically, the 'enum' type is equivalent to the smallest integer type that has enough room. ! *Warning:* the '-fshort-enums' switch causes GCC to generate code that is not binary compatible with code generated without that switch. Use it to conform to a non-default application binary interface. ! '-fshort-wchar' ! Override the underlying type for 'wchar_t' to be 'short unsigned int' instead of the default for the target. This option is useful for building programs to run under WINE. ! *Warning:* the '-fshort-wchar' switch causes GCC to generate code that is not binary compatible with code generated without that switch. Use it to conform to a non-default application binary interface. ! '-fno-common' In C code, controls the placement of uninitialized global variables. Unix C compilers have traditionally permitted multiple definitions of such variables in different compilation units by placing the variables in a common block. This is the behavior ! specified by '-fcommon', and is the default for GCC on most targets. On the other hand, this behavior is not required by ISO C, and on some targets may carry a speed or code size penalty on ! variable references. The '-fno-common' option specifies that the compiler should place uninitialized global variables in the data section of the object file, rather than generating them as common blocks. This has the effect that if the same variable is declared ! (without 'extern') in two different compilations, you get a multiple-definition error when you link them. In this case, you ! must compile with '-fcommon' instead. Compiling with '-fno-common' ! is useful on targets for which it provides better performance, or ! if you wish to verify that the program will work on other systems ! that always treat uninitialized variable declarations this way. ! '-fno-ident' ! Ignore the '#ident' directive. ! '-finhibit-size-directive' ! Don't output a '.size' assembler directive, or anything else that would cause trouble if the function is split in the middle, and the two halves are placed at locations far apart in memory. This ! option is used when compiling 'crtstuff.c'; you should not need to use it for anything else. ! '-fverbose-asm' Put extra commentary information in the generated assembly code to make it more readable. This option is generally only of use to those who actually need to read the generated assembly code (perhaps while debugging the compiler itself). ! '-fno-verbose-asm', the default, causes the extra information to be ! omitted and is useful when comparing two assembler files. ! '-frecord-gcc-switches' This switch causes the command line used to invoke the compiler to be recorded into the object file that is being created. This switch is only implemented on some targets and the exact format of the recording is target and binary file format dependent, but it usually takes the form of a section containing ASCII text. This ! switch is related to the '-fverbose-asm' switch, but that switch only records information in the assembler output file as comments, so it never reaches the object file. See also ! '-grecord-gcc-switches' for another way of storing compiler options ! into the object file. ! '-fpic' Generate position-independent code (PIC) suitable for use in a shared library, if supported for the target machine. Such code accesses all constant addresses through a global offset table --- 10989,11089 ---- Short structures and unions are those whose size and alignment match that of some integer type. ! *Warning:* code compiled with the `-fpcc-struct-return' switch is not binary compatible with code compiled with the ! `-freg-struct-return' switch. Use it to conform to a non-default application binary interface. ! `-freg-struct-return' ! Return `struct' and `union' values in registers when possible. This is more efficient for small structures than ! `-fpcc-struct-return'. ! If you specify neither `-fpcc-struct-return' nor ! `-freg-struct-return', GCC defaults to whichever convention is standard for the target. If there is no standard convention, GCC ! defaults to `-fpcc-struct-return', except on targets where GCC is the principal compiler. In those cases, we can choose the standard, and we chose the more efficient register return alternative. ! *Warning:* code compiled with the `-freg-struct-return' switch is not binary compatible with code compiled with the ! `-fpcc-struct-return' switch. Use it to conform to a non-default application binary interface. ! `-fshort-enums' ! Allocate to an `enum' type only as many bytes as it needs for the ! declared range of possible values. Specifically, the `enum' type is equivalent to the smallest integer type that has enough room. ! *Warning:* the `-fshort-enums' switch causes GCC to generate code that is not binary compatible with code generated without that switch. Use it to conform to a non-default application binary interface. ! `-fshort-wchar' ! Override the underlying type for `wchar_t' to be `short unsigned int' instead of the default for the target. This option is useful for building programs to run under WINE. ! *Warning:* the `-fshort-wchar' switch causes GCC to generate code that is not binary compatible with code generated without that switch. Use it to conform to a non-default application binary interface. ! `-fno-common' In C code, controls the placement of uninitialized global variables. Unix C compilers have traditionally permitted multiple definitions of such variables in different compilation units by placing the variables in a common block. This is the behavior ! specified by `-fcommon', and is the default for GCC on most targets. On the other hand, this behavior is not required by ISO C, and on some targets may carry a speed or code size penalty on ! variable references. The `-fno-common' option specifies that the compiler should place uninitialized global variables in the data section of the object file, rather than generating them as common blocks. This has the effect that if the same variable is declared ! (without `extern') in two different compilations, you get a multiple-definition error when you link them. In this case, you ! must compile with `-fcommon' instead. Compiling with ! `-fno-common' is useful on targets for which it provides better ! performance, or if you wish to verify that the program will work ! on other systems that always treat uninitialized variable ! declarations this way. ! `-fno-ident' ! Ignore the `#ident' directive. ! `-finhibit-size-directive' ! Don't output a `.size' assembler directive, or anything else that would cause trouble if the function is split in the middle, and the two halves are placed at locations far apart in memory. This ! option is used when compiling `crtstuff.c'; you should not need to use it for anything else. ! `-fverbose-asm' Put extra commentary information in the generated assembly code to make it more readable. This option is generally only of use to those who actually need to read the generated assembly code (perhaps while debugging the compiler itself). ! `-fno-verbose-asm', the default, causes the extra information to ! be omitted and is useful when comparing two assembler files. ! `-frecord-gcc-switches' This switch causes the command line used to invoke the compiler to be recorded into the object file that is being created. This switch is only implemented on some targets and the exact format of the recording is target and binary file format dependent, but it usually takes the form of a section containing ASCII text. This ! switch is related to the `-fverbose-asm' switch, but that switch only records information in the assembler output file as comments, so it never reaches the object file. See also ! `-grecord-gcc-switches' for another way of storing compiler ! options into the object file. ! `-fpic' Generate position-independent code (PIC) suitable for use in a shared library, if supported for the target machine. Such code accesses all constant addresses through a global offset table *************** form by either removing 'no-' or adding *** 11034,11041 **** program starts (the dynamic loader is not part of GCC; it is part of the operating system). If the GOT size for the linked executable exceeds a machine-specific maximum size, you get an ! error message from the linker indicating that '-fpic' does not ! work; in that case, recompile with '-fPIC' instead. (These maximums are 8k on the SPARC, 28k on AArch64 and 32k on the m68k and RS/6000. The x86 has no such limit.) --- 11091,11098 ---- program starts (the dynamic loader is not part of GCC; it is part of the operating system). If the GOT size for the linked executable exceeds a machine-specific maximum size, you get an ! error message from the linker indicating that `-fpic' does not ! work; in that case, recompile with `-fPIC' instead. (These maximums are 8k on the SPARC, 28k on AArch64 and 32k on the m68k and RS/6000. The x86 has no such limit.) *************** form by either removing 'no-' or adding *** 11044,11113 **** System V but not for the Sun 386i. Code generated for the IBM RS/6000 is always position-independent. ! When this flag is set, the macros '__pic__' and '__PIC__' are defined to 1. ! '-fPIC' If supported for the target machine, emit position-independent code, suitable for dynamic linking and avoiding any limit on the ! size of the global offset table. This option makes a difference on ! AArch64, m68k, PowerPC and SPARC. Position-independent code requires special support, and therefore works only on certain machines. ! When this flag is set, the macros '__pic__' and '__PIC__' are defined to 2. ! '-fpie' ! '-fPIE' ! These options are similar to '-fpic' and '-fPIC', but generated position independent code can be only linked into executables. ! Usually these options are used when '-pie' GCC option is used during linking. ! '-fpie' and '-fPIE' both define the macros '__pie__' and '__PIE__'. ! The macros have the value 1 for '-fpie' and 2 for '-fPIE'. ! '-fno-plt' Do not use the PLT for external function calls in position-independent code. Instead, load the callee address at call sites from the GOT and branch to it. This leads to more efficient code by eliminating PLT stubs and exposing GOT loads to ! optimizations. On architectures such as 32-bit x86 where PLT stubs ! expect the GOT pointer in a specific register, this gives more ! register allocation freedom to the compiler. Lazy binding requires ! use of the PLT; with '-fno-plt' all external symbols are resolved ! at load time. ! Alternatively, the function attribute 'noplt' can be used to avoid calls through the PLT for specific external functions. In position-dependent code, a few targets also convert calls to functions that are marked to not use the PLT to use the GOT instead. ! '-fno-jump-tables' Do not use jump tables for switch statements even where it would be more efficient than other code generation strategies. This option ! is of use in conjunction with '-fpic' or '-fPIC' for building code that forms part of a dynamic linker and cannot reference the address of a jump table. On some targets, jump tables do not require a GOT and this option is not needed. ! '-ffixed-REG' Treat the register named REG as a fixed register; generated code should never refer to it (except perhaps as a stack pointer, frame pointer or in some other fixed role). REG must be the name of a register. The register names accepted ! are machine-specific and are defined in the 'REGISTER_NAMES' macro in the machine description macro file. This flag does not have a negative form, because it specifies a three-way choice. ! '-fcall-used-REG' Treat the register named REG as an allocable register that is clobbered by function calls. It may be allocated for temporaries or variables that do not live across a call. Functions compiled --- 11101,11171 ---- System V but not for the Sun 386i. Code generated for the IBM RS/6000 is always position-independent. ! When this flag is set, the macros `__pic__' and `__PIC__' are defined to 1. ! `-fPIC' If supported for the target machine, emit position-independent code, suitable for dynamic linking and avoiding any limit on the ! size of the global offset table. This option makes a difference ! on AArch64, m68k, PowerPC and SPARC. Position-independent code requires special support, and therefore works only on certain machines. ! When this flag is set, the macros `__pic__' and `__PIC__' are defined to 2. ! `-fpie' ! `-fPIE' ! These options are similar to `-fpic' and `-fPIC', but generated position independent code can be only linked into executables. ! Usually these options are used when `-pie' GCC option is used during linking. ! `-fpie' and `-fPIE' both define the macros `__pie__' and ! `__PIE__'. The macros have the value 1 for `-fpie' and 2 for ! `-fPIE'. ! `-fno-plt' Do not use the PLT for external function calls in position-independent code. Instead, load the callee address at call sites from the GOT and branch to it. This leads to more efficient code by eliminating PLT stubs and exposing GOT loads to ! optimizations. On architectures such as 32-bit x86 where PLT ! stubs expect the GOT pointer in a specific register, this gives ! more register allocation freedom to the compiler. Lazy binding ! requires use of the PLT; with `-fno-plt' all external symbols are ! resolved at load time. ! Alternatively, the function attribute `noplt' can be used to avoid calls through the PLT for specific external functions. In position-dependent code, a few targets also convert calls to functions that are marked to not use the PLT to use the GOT instead. ! `-fno-jump-tables' Do not use jump tables for switch statements even where it would be more efficient than other code generation strategies. This option ! is of use in conjunction with `-fpic' or `-fPIC' for building code that forms part of a dynamic linker and cannot reference the address of a jump table. On some targets, jump tables do not require a GOT and this option is not needed. ! `-ffixed-REG' Treat the register named REG as a fixed register; generated code should never refer to it (except perhaps as a stack pointer, frame pointer or in some other fixed role). REG must be the name of a register. The register names accepted ! are machine-specific and are defined in the `REGISTER_NAMES' macro in the machine description macro file. This flag does not have a negative form, because it specifies a three-way choice. ! `-fcall-used-REG' Treat the register named REG as an allocable register that is clobbered by function calls. It may be allocated for temporaries or variables that do not live across a call. Functions compiled *************** form by either removing 'no-' or adding *** 11121,11127 **** This flag does not have a negative form, because it specifies a three-way choice. ! '-fcall-saved-REG' Treat the register named REG as an allocable register saved by functions. It may be allocated even for temporaries or variables that live across a call. Functions compiled this way save and --- 11179,11185 ---- This flag does not have a negative form, because it specifies a three-way choice. ! `-fcall-saved-REG' Treat the register named REG as an allocable register saved by functions. It may be allocated even for temporaries or variables that live across a call. Functions compiled this way save and *************** form by either removing 'no-' or adding *** 11138,11144 **** This flag does not have a negative form, because it specifies a three-way choice. ! '-fpack-struct[=N]' Without a value specified, pack all structure members together without holes. When a value is specified (which must be a small power of two), pack structure members according to this value, --- 11196,11202 ---- This flag does not have a negative form, because it specifies a three-way choice. ! `-fpack-struct[=N]' Without a value specified, pack all structure members together without holes. When a value is specified (which must be a small power of two), pack structure members according to this value, *************** form by either removing 'no-' or adding *** 11146,11179 **** alignment requirements larger than this are output potentially unaligned at the next fitting location. ! *Warning:* the '-fpack-struct' switch causes GCC to generate code that is not binary compatible with code generated without that switch. Additionally, it makes the code suboptimal. Use it to conform to a non-default application binary interface. ! '-fleading-underscore' ! This option and its counterpart, '-fno-leading-underscore', forcibly change the way C symbols are represented in the object file. One use is to help link with legacy assembly code. ! *Warning:* the '-fleading-underscore' switch causes GCC to generate ! code that is not binary compatible with code generated without that ! switch. Use it to conform to a non-default application binary ! interface. Not all targets provide complete support for this ! switch. ! '-ftls-model=MODEL' Alter the thread-local storage model to be used (*note Thread-Local::). The MODEL argument should be one of ! 'global-dynamic', 'local-dynamic', 'initial-exec' or 'local-exec'. Note that the choice is subject to optimization: the compiler may use a more efficient model for symbols not visible outside of the ! translation unit, or if '-fpic' is not given on the command line. ! The default without '-fpic' is 'initial-exec'; with '-fpic' the ! default is 'global-dynamic'. ! '-fvisibility=[default|internal|hidden|protected]' Set the default ELF image symbol visibility to the specified option--all symbols are marked with this unless overridden within the code. Using this feature can very substantially improve --- 11204,11237 ---- alignment requirements larger than this are output potentially unaligned at the next fitting location. ! *Warning:* the `-fpack-struct' switch causes GCC to generate code that is not binary compatible with code generated without that switch. Additionally, it makes the code suboptimal. Use it to conform to a non-default application binary interface. ! `-fleading-underscore' ! This option and its counterpart, `-fno-leading-underscore', forcibly change the way C symbols are represented in the object file. One use is to help link with legacy assembly code. ! *Warning:* the `-fleading-underscore' switch causes GCC to ! generate code that is not binary compatible with code generated ! without that switch. Use it to conform to a non-default ! application binary interface. Not all targets provide complete ! support for this switch. ! `-ftls-model=MODEL' Alter the thread-local storage model to be used (*note Thread-Local::). The MODEL argument should be one of ! `global-dynamic', `local-dynamic', `initial-exec' or `local-exec'. Note that the choice is subject to optimization: the compiler may use a more efficient model for symbols not visible outside of the ! translation unit, or if `-fpic' is not given on the command line. ! The default without `-fpic' is `initial-exec'; with `-fpic' the ! default is `global-dynamic'. ! `-fvisibility=[default|internal|hidden|protected]' Set the default ELF image symbol visibility to the specified option--all symbols are marked with this unless overridden within the code. Using this feature can very substantially improve *************** form by either removing 'no-' or adding *** 11182,11210 **** clashes. It is *strongly* recommended that you use this in any shared objects you distribute. ! Despite the nomenclature, 'default' always means public; i.e., available to be linked against from outside the shared object. ! 'protected' and 'internal' are pretty useless in real-world usage ! so the only other commonly used option is 'hidden'. The default if ! '-fvisibility' isn't specified is 'default', i.e., make every symbol public. A good explanation of the benefits offered by ensuring ELF symbols have the correct visibility is given by "How To Write Shared Libraries" by Ulrich Drepper (which can be found at ! )--however a superior solution made possible by this option to marking things hidden when the default is public is to make the default hidden and mark things public. This is the norm with DLLs on Windows and with ! '-fvisibility=hidden' and '__attribute__ ((visibility("default")))' ! instead of '__declspec(dllexport)' you get almost identical ! semantics with identical syntax. This is a great boon to those ! working with cross-platform projects. For those adding visibility support to existing code, you may find ! '#pragma GCC visibility' of use. This works by you enclosing the declarations you wish to set visibility for with (for example) ! '#pragma GCC visibility push(hidden)' and '#pragma GCC visibility pop'. Bear in mind that symbol visibility should be viewed *as part of the API interface contract* and thus all new code should always specify visibility when it is not the default; i.e., --- 11240,11268 ---- clashes. It is *strongly* recommended that you use this in any shared objects you distribute. ! Despite the nomenclature, `default' always means public; i.e., available to be linked against from outside the shared object. ! `protected' and `internal' are pretty useless in real-world usage ! so the only other commonly used option is `hidden'. The default ! if `-fvisibility' isn't specified is `default', i.e., make every symbol public. A good explanation of the benefits offered by ensuring ELF symbols have the correct visibility is given by "How To Write Shared Libraries" by Ulrich Drepper (which can be found at ! `http://www.akkadia.org/drepper/')--however a superior solution made possible by this option to marking things hidden when the default is public is to make the default hidden and mark things public. This is the norm with DLLs on Windows and with ! `-fvisibility=hidden' and `__attribute__ ! ((visibility("default")))' instead of `__declspec(dllexport)' you ! get almost identical semantics with identical syntax. This is a ! great boon to those working with cross-platform projects. For those adding visibility support to existing code, you may find ! `#pragma GCC visibility' of use. This works by you enclosing the declarations you wish to set visibility for with (for example) ! `#pragma GCC visibility push(hidden)' and `#pragma GCC visibility pop'. Bear in mind that symbol visibility should be viewed *as part of the API interface contract* and thus all new code should always specify visibility when it is not the default; i.e., *************** form by either removing 'no-' or adding *** 11212,11252 **** marked explicitly as hidden as so to avoid PLT indirection overheads--making this abundantly clear also aids readability and self-documentation of the code. Note that due to ISO C++ ! specification requirements, 'operator new' and 'operator delete' must always be of default visibility. Be aware that headers from outside your project, in particular system headers and headers from any other library you use, may not ! be expecting to be compiled with visibility other than the default. ! You may need to explicitly say '#pragma GCC visibility push(default)' before including any such headers. ! 'extern' declarations are not affected by '-fvisibility', so a lot ! of code can be recompiled with '-fvisibility=hidden' with no ! modifications. However, this means that calls to 'extern' functions with no explicit visibility use the PLT, so it is more ! effective to use '__attribute ((visibility))' and/or '#pragma GCC ! visibility' to tell the compiler which 'extern' declarations should ! be treated as hidden. ! Note that '-fvisibility' does affect C++ vague linkage entities. ! This means that, for instance, an exception class that is be thrown ! between DSOs must be explicitly marked with default visibility so ! that the 'type_info' nodes are unified between the DSOs. An overview of these techniques, their benefits and how to use them ! is at . ! '-fstrict-volatile-bitfields' This option should be used if accesses to volatile bit-fields (or other structure fields, although the compiler usually honors those types anyway) should use a single access of the width of the field's type, aligned to a natural alignment if possible. For example, targets with memory-mapped peripheral registers might require all such accesses to be 16 bits wide; with this flag you ! can declare all peripheral bit-fields as 'unsigned short' (assuming ! short is 16 bits on these targets) to force GCC to use 16-bit ! accesses instead of, perhaps, a more efficient 32-bit access. If this option is disabled, the compiler uses the most efficient instruction. In the previous example, that might be a 32-bit load --- 11270,11312 ---- marked explicitly as hidden as so to avoid PLT indirection overheads--making this abundantly clear also aids readability and self-documentation of the code. Note that due to ISO C++ ! specification requirements, `operator new' and `operator delete' must always be of default visibility. Be aware that headers from outside your project, in particular system headers and headers from any other library you use, may not ! be expecting to be compiled with visibility other than the ! default. You may need to explicitly say `#pragma GCC visibility push(default)' before including any such headers. ! `extern' declarations are not affected by `-fvisibility', so a lot ! of code can be recompiled with `-fvisibility=hidden' with no ! modifications. However, this means that calls to `extern' functions with no explicit visibility use the PLT, so it is more ! effective to use `__attribute ((visibility))' and/or `#pragma GCC ! visibility' to tell the compiler which `extern' declarations ! should be treated as hidden. ! Note that `-fvisibility' does affect C++ vague linkage entities. ! This means that, for instance, an exception class that is be ! thrown between DSOs must be explicitly marked with default ! visibility so that the `type_info' nodes are unified between the ! DSOs. An overview of these techniques, their benefits and how to use them ! is at `http://gcc.gnu.org/wiki/Visibility'. ! `-fstrict-volatile-bitfields' This option should be used if accesses to volatile bit-fields (or other structure fields, although the compiler usually honors those types anyway) should use a single access of the width of the field's type, aligned to a natural alignment if possible. For example, targets with memory-mapped peripheral registers might require all such accesses to be 16 bits wide; with this flag you ! can declare all peripheral bit-fields as `unsigned short' ! (assuming short is 16 bits on these targets) to force GCC to use ! 16-bit accesses instead of, perhaps, a more efficient 32-bit ! access. If this option is disabled, the compiler uses the most efficient instruction. In the previous example, that might be a 32-bit load *************** form by either removing 'no-' or adding *** 11254,11267 **** any portion of the bit-field, or memory-mapped registers unrelated to the one being updated. ! In some cases, such as when the 'packed' attribute is applied to a structure field, it may not be possible to access the field with a single read or write that is correctly aligned for the target machine. In this case GCC falls back to generating multiple ! accesses rather than code that will fault or truncate the result at ! run time. ! Note: Due to restrictions of the C/C++11 memory model, write accesses are not allowed to touch non bit-field members. It is therefore recommended to define all bits of the field's type as bit-field members. --- 11314,11327 ---- any portion of the bit-field, or memory-mapped registers unrelated to the one being updated. ! In some cases, such as when the `packed' attribute is applied to a structure field, it may not be possible to access the field with a single read or write that is correctly aligned for the target machine. In this case GCC falls back to generating multiple ! accesses rather than code that will fault or truncate the result ! at run time. ! Note: Due to restrictions of the C/C++11 memory model, write accesses are not allowed to touch non bit-field members. It is therefore recommended to define all bits of the field's type as bit-field members. *************** form by either removing 'no-' or adding *** 11269,11282 **** The default value of this option is determined by the application binary interface for the target processor. ! '-fsync-libcalls' This option controls whether any out-of-line instance of the ! '__sync' family of functions may be used to implement the C++11 ! '__atomic' family of functions. The default value of this option is enabled, thus the only useful ! form of the option is '-fno-sync-libcalls'. This option is used in ! the implementation of the 'libatomic' runtime library.  File: gcc.info, Node: Developer Options, Next: Submodel Options, Prev: Code Gen Options, Up: Invoking GCC --- 11329,11343 ---- The default value of this option is determined by the application binary interface for the target processor. ! `-fsync-libcalls' This option controls whether any out-of-line instance of the ! `__sync' family of functions may be used to implement the C++11 ! `__atomic' family of functions. The default value of this option is enabled, thus the only useful ! form of the option is `-fno-sync-libcalls'. This option is used in ! the implementation of the `libatomic' runtime library. !  File: gcc.info, Node: Developer Options, Next: Submodel Options, Prev: Code Gen Options, Up: Invoking GCC *************** execution time; and that print informati *** 11293,11627 **** such as where it searches for libraries. You should rarely need to use any of these options for ordinary compilation and linking tasks. ! '-dLETTERS' ! '-fdump-rtl-PASS' ! '-fdump-rtl-PASS=FILENAME' Says to make debugging dumps during compilation at times specified by LETTERS. This is used for debugging the RTL-based passes of the compiler. The file names for most of the dumps are made by appending a pass number and a word to the DUMPNAME, and the files are created in the directory of the output file. In case of ! '=FILENAME' option, the dump is output on the given file instead of ! the pass numbered dump files. Note that the pass number is assigned as passes are registered into the pass manager. Most passes are registered in the order that they will execute and for these passes the number corresponds to the pass execution order. However, passes registered by plugins, passes specific to compilation targets, or passes that are otherwise registered after ! all the other passes are numbered higher than a pass named "final", ! even if they are executed earlier. DUMPNAME is generated from the ! name of the output file if explicitly specified and not an ! executable, otherwise it is the basename of the source file. These ! switches may have different effects when '-E' is used for preprocessing. ! Debug dumps can be enabled with a '-fdump-rtl' switch or some '-d' option LETTERS. Here are the possible letters for use in PASS and LETTERS, and their meanings: ! '-fdump-rtl-alignments' Dump after branch alignments have been computed. ! '-fdump-rtl-asmcons' Dump after fixing rtl statements that have unsatisfied in/out constraints. ! '-fdump-rtl-auto_inc_dec' Dump after auto-inc-dec discovery. This pass is only run on architectures that have auto inc or auto dec instructions. ! '-fdump-rtl-barriers' Dump after cleaning up the barrier instructions. ! '-fdump-rtl-bbpart' Dump after partitioning hot and cold basic blocks. ! '-fdump-rtl-bbro' Dump after block reordering. ! '-fdump-rtl-btl1' ! '-fdump-rtl-btl2' ! '-fdump-rtl-btl1' and '-fdump-rtl-btl2' enable dumping after the two branch target load optimization passes. ! '-fdump-rtl-bypass' Dump after jump bypassing and control flow optimizations. ! '-fdump-rtl-combine' Dump after the RTL instruction combination pass. ! '-fdump-rtl-compgotos' Dump after duplicating the computed gotos. ! '-fdump-rtl-ce1' ! '-fdump-rtl-ce2' ! '-fdump-rtl-ce3' ! '-fdump-rtl-ce1', '-fdump-rtl-ce2', and '-fdump-rtl-ce3' enable dumping after the three if conversion passes. ! '-fdump-rtl-cprop_hardreg' Dump after hard register copy propagation. ! '-fdump-rtl-csa' Dump after combining stack adjustments. ! '-fdump-rtl-cse1' ! '-fdump-rtl-cse2' ! '-fdump-rtl-cse1' and '-fdump-rtl-cse2' enable dumping after the two common subexpression elimination passes. ! '-fdump-rtl-dce' Dump after the standalone dead code elimination passes. ! '-fdump-rtl-dbr' Dump after delayed branch scheduling. ! '-fdump-rtl-dce1' ! '-fdump-rtl-dce2' ! '-fdump-rtl-dce1' and '-fdump-rtl-dce2' enable dumping after the two dead store elimination passes. ! '-fdump-rtl-eh' Dump after finalization of EH handling code. ! '-fdump-rtl-eh_ranges' Dump after conversion of EH handling range regions. ! '-fdump-rtl-expand' Dump after RTL generation. ! '-fdump-rtl-fwprop1' ! '-fdump-rtl-fwprop2' ! '-fdump-rtl-fwprop1' and '-fdump-rtl-fwprop2' enable dumping after the two forward propagation passes. ! '-fdump-rtl-gcse1' ! '-fdump-rtl-gcse2' ! '-fdump-rtl-gcse1' and '-fdump-rtl-gcse2' enable dumping after ! global common subexpression elimination. ! '-fdump-rtl-init-regs' Dump after the initialization of the registers. ! '-fdump-rtl-initvals' Dump after the computation of the initial value sets. ! '-fdump-rtl-into_cfglayout' Dump after converting to cfglayout mode. ! '-fdump-rtl-ira' Dump after iterated register allocation. ! '-fdump-rtl-jump' Dump after the second jump optimization. ! '-fdump-rtl-loop2' ! '-fdump-rtl-loop2' enables dumping after the rtl loop optimization passes. ! '-fdump-rtl-mach' Dump after performing the machine dependent reorganization pass, if that pass exists. ! '-fdump-rtl-mode_sw' Dump after removing redundant mode switches. ! '-fdump-rtl-rnreg' Dump after register renumbering. ! '-fdump-rtl-outof_cfglayout' Dump after converting from cfglayout mode. ! '-fdump-rtl-peephole2' Dump after the peephole pass. ! '-fdump-rtl-postreload' Dump after post-reload optimizations. ! '-fdump-rtl-pro_and_epilogue' Dump after generating the function prologues and epilogues. ! '-fdump-rtl-sched1' ! '-fdump-rtl-sched2' ! '-fdump-rtl-sched1' and '-fdump-rtl-sched2' enable dumping after the basic block scheduling passes. ! '-fdump-rtl-ree' Dump after sign/zero extension elimination. ! '-fdump-rtl-seqabstr' Dump after common sequence discovery. ! '-fdump-rtl-shorten' Dump after shortening branches. ! '-fdump-rtl-sibling' Dump after sibling call optimizations. ! '-fdump-rtl-split1' ! '-fdump-rtl-split2' ! '-fdump-rtl-split3' ! '-fdump-rtl-split4' ! '-fdump-rtl-split5' These options enable dumping after five rounds of instruction splitting. ! '-fdump-rtl-sms' Dump after modulo scheduling. This pass is only run on some architectures. ! '-fdump-rtl-stack' Dump after conversion from GCC's "flat register file" registers to the x87's stack-like registers. This pass is only run on x86 variants. ! '-fdump-rtl-subreg1' ! '-fdump-rtl-subreg2' ! '-fdump-rtl-subreg1' and '-fdump-rtl-subreg2' enable dumping after the two subreg expansion passes. ! '-fdump-rtl-unshare' Dump after all rtl has been unshared. ! '-fdump-rtl-vartrack' Dump after variable tracking. ! '-fdump-rtl-vregs' Dump after converting virtual registers to hard registers. ! '-fdump-rtl-web' Dump after live range splitting. ! '-fdump-rtl-regclass' ! '-fdump-rtl-subregs_of_mode_init' ! '-fdump-rtl-subregs_of_mode_finish' ! '-fdump-rtl-dfinit' ! '-fdump-rtl-dfinish' These dumps are defined but always produce empty files. ! '-da' ! '-fdump-rtl-all' Produce all the dumps listed above. ! '-dA' Annotate the assembler output with miscellaneous debugging information. ! '-dD' Dump all macro definitions, at the end of preprocessing, in addition to normal output. ! '-dH' Produce a core dump whenever an error occurs. ! '-dp' Annotate the assembler output with a comment indicating which pattern and alternative is used. The length of each instruction is also printed. ! '-dP' Dump the RTL in the assembler output as a comment before each ! instruction. Also turns on '-dp' annotation. ! '-dx' Just generate RTL for a function instead of compiling it. ! Usually used with '-fdump-rtl-expand'. ! '-fdump-noaddr' ! When doing debugging dumps, suppress address output. This makes it ! more feasible to use diff on debugging dumps for compiler invocations with different compiler binaries and/or different text / bss / data / heap / stack / dso start locations. ! '-freport-bug' Collect and dump debug information into a temporary file if an internal compiler error (ICE) occurs. ! '-fdump-unnumbered' When doing debugging dumps, suppress instruction numbers and address output. This makes it more feasible to use diff on ! debugging dumps for compiler invocations with different options, in ! particular with and without '-g'. ! '-fdump-unnumbered-links' ! When doing debugging dumps (see '-d' option above), suppress instruction numbers for the links to the previous and next instructions in a sequence. ! '-fdump-translation-unit (C++ only)' ! '-fdump-translation-unit-OPTIONS (C++ only)' Dump a representation of the tree structure for the entire translation unit to a file. The file name is made by appending ! '.tu' to the source file name, and the file is created in the same ! directory as the output file. If the '-OPTIONS' form is used, OPTIONS controls the details of the dump as described for the ! '-fdump-tree' options. ! '-fdump-class-hierarchy (C++ only)' ! '-fdump-class-hierarchy-OPTIONS (C++ only)' Dump a representation of each class's hierarchy and virtual function table layout to a file. The file name is made by ! appending '.class' to the source file name, and the file is created ! in the same directory as the output file. If the '-OPTIONS' form ! is used, OPTIONS controls the details of the dump as described for ! the '-fdump-tree' options. ! '-fdump-ipa-SWITCH' Control the dumping at various stages of inter-procedural analysis language tree to a file. The file name is generated by appending a switch specific suffix to the source file name, and the file is created in the same directory as the output file. The following dumps are possible: ! 'all' Enables all inter-procedural analysis dumps. ! 'cgraph' Dumps information about call-graph optimization, unused function removal, and inlining decisions. ! 'inline' Dump after function inlining. ! '-fdump-passes' Dump the list of optimization passes that are turned on and off by the current command-line options. ! '-fdump-statistics-OPTION' Enable and control dumping of pass statistics in a separate file. The file name is generated by appending a suffix ending in ! '.statistics' to the source file name, and the file is created in ! the same directory as the output file. If the '-OPTION' form is ! used, '-stats' causes counters to be summed over the whole ! compilation unit while '-details' dumps every event as the passes generate them. The default with no option is to sum counters for each function compiled. ! '-fdump-tree-SWITCH' ! '-fdump-tree-SWITCH-OPTIONS' ! '-fdump-tree-SWITCH-OPTIONS=FILENAME' Control the dumping at various stages of processing the intermediate language tree to a file. The file name is generated by appending a switch-specific suffix to the source file name, and ! the file is created in the same directory as the output file. In ! case of '=FILENAME' option, the dump is output on the given file ! instead of the auto named dump files. If the '-OPTIONS' form is ! used, OPTIONS is a list of '-' separated options which control the details of the dump. Not all options are applicable to all dumps; those that are not meaningful are ignored. The following options are available ! 'address' Print the address of each node. Usually this is not meaningful as it changes according to the environment and ! source file. Its primary use is for tying up a dump file with ! a debug environment. ! 'asmname' ! If 'DECL_ASSEMBLER_NAME' has been set for a given decl, use ! that in the dump instead of 'DECL_NAME'. Its primary use is ease of use working backward from mangled names in the assembly file. ! 'slim' When dumping front-end intermediate representations, inhibit dumping of members of a scope or body of a function merely because that scope has been reached. Only dump such items --- 11354,11691 ---- such as where it searches for libraries. You should rarely need to use any of these options for ordinary compilation and linking tasks. ! `-dLETTERS' ! `-fdump-rtl-PASS' ! `-fdump-rtl-PASS=FILENAME' Says to make debugging dumps during compilation at times specified by LETTERS. This is used for debugging the RTL-based passes of the compiler. The file names for most of the dumps are made by appending a pass number and a word to the DUMPNAME, and the files are created in the directory of the output file. In case of ! `=FILENAME' option, the dump is output on the given file instead ! of the pass numbered dump files. Note that the pass number is assigned as passes are registered into the pass manager. Most passes are registered in the order that they will execute and for these passes the number corresponds to the pass execution order. However, passes registered by plugins, passes specific to compilation targets, or passes that are otherwise registered after ! all the other passes are numbered higher than a pass named ! "final", even if they are executed earlier. DUMPNAME is generated ! from the name of the output file if explicitly specified and not ! an executable, otherwise it is the basename of the source file. ! These switches may have different effects when `-E' is used for preprocessing. ! Debug dumps can be enabled with a `-fdump-rtl' switch or some `-d' option LETTERS. Here are the possible letters for use in PASS and LETTERS, and their meanings: ! `-fdump-rtl-alignments' Dump after branch alignments have been computed. ! `-fdump-rtl-asmcons' Dump after fixing rtl statements that have unsatisfied in/out constraints. ! `-fdump-rtl-auto_inc_dec' Dump after auto-inc-dec discovery. This pass is only run on architectures that have auto inc or auto dec instructions. ! `-fdump-rtl-barriers' Dump after cleaning up the barrier instructions. ! `-fdump-rtl-bbpart' Dump after partitioning hot and cold basic blocks. ! `-fdump-rtl-bbro' Dump after block reordering. ! `-fdump-rtl-btl1' ! `-fdump-rtl-btl2' ! `-fdump-rtl-btl1' and `-fdump-rtl-btl2' enable dumping after the two branch target load optimization passes. ! `-fdump-rtl-bypass' Dump after jump bypassing and control flow optimizations. ! `-fdump-rtl-combine' Dump after the RTL instruction combination pass. ! `-fdump-rtl-compgotos' Dump after duplicating the computed gotos. ! `-fdump-rtl-ce1' ! `-fdump-rtl-ce2' ! `-fdump-rtl-ce3' ! `-fdump-rtl-ce1', `-fdump-rtl-ce2', and `-fdump-rtl-ce3' enable dumping after the three if conversion passes. ! `-fdump-rtl-cprop_hardreg' Dump after hard register copy propagation. ! `-fdump-rtl-csa' Dump after combining stack adjustments. ! `-fdump-rtl-cse1' ! `-fdump-rtl-cse2' ! `-fdump-rtl-cse1' and `-fdump-rtl-cse2' enable dumping after the two common subexpression elimination passes. ! `-fdump-rtl-dce' Dump after the standalone dead code elimination passes. ! `-fdump-rtl-dbr' Dump after delayed branch scheduling. ! `-fdump-rtl-dce1' ! `-fdump-rtl-dce2' ! `-fdump-rtl-dce1' and `-fdump-rtl-dce2' enable dumping after the two dead store elimination passes. ! `-fdump-rtl-eh' Dump after finalization of EH handling code. ! `-fdump-rtl-eh_ranges' Dump after conversion of EH handling range regions. ! `-fdump-rtl-expand' Dump after RTL generation. ! `-fdump-rtl-fwprop1' ! `-fdump-rtl-fwprop2' ! `-fdump-rtl-fwprop1' and `-fdump-rtl-fwprop2' enable dumping after the two forward propagation passes. ! `-fdump-rtl-gcse1' ! `-fdump-rtl-gcse2' ! `-fdump-rtl-gcse1' and `-fdump-rtl-gcse2' enable dumping ! after global common subexpression elimination. ! `-fdump-rtl-init-regs' Dump after the initialization of the registers. ! `-fdump-rtl-initvals' Dump after the computation of the initial value sets. ! `-fdump-rtl-into_cfglayout' Dump after converting to cfglayout mode. ! `-fdump-rtl-ira' Dump after iterated register allocation. ! `-fdump-rtl-jump' Dump after the second jump optimization. ! `-fdump-rtl-loop2' ! `-fdump-rtl-loop2' enables dumping after the rtl loop optimization passes. ! `-fdump-rtl-mach' Dump after performing the machine dependent reorganization pass, if that pass exists. ! `-fdump-rtl-mode_sw' Dump after removing redundant mode switches. ! `-fdump-rtl-rnreg' Dump after register renumbering. ! `-fdump-rtl-outof_cfglayout' Dump after converting from cfglayout mode. ! `-fdump-rtl-peephole2' Dump after the peephole pass. ! `-fdump-rtl-postreload' Dump after post-reload optimizations. ! `-fdump-rtl-pro_and_epilogue' Dump after generating the function prologues and epilogues. ! `-fdump-rtl-sched1' ! `-fdump-rtl-sched2' ! `-fdump-rtl-sched1' and `-fdump-rtl-sched2' enable dumping after the basic block scheduling passes. ! `-fdump-rtl-ree' Dump after sign/zero extension elimination. ! `-fdump-rtl-seqabstr' Dump after common sequence discovery. ! `-fdump-rtl-shorten' Dump after shortening branches. ! `-fdump-rtl-sibling' Dump after sibling call optimizations. ! `-fdump-rtl-split1' ! `-fdump-rtl-split2' ! `-fdump-rtl-split3' ! `-fdump-rtl-split4' ! `-fdump-rtl-split5' These options enable dumping after five rounds of instruction splitting. ! `-fdump-rtl-sms' Dump after modulo scheduling. This pass is only run on some architectures. ! `-fdump-rtl-stack' Dump after conversion from GCC's "flat register file" registers to the x87's stack-like registers. This pass is only run on x86 variants. ! `-fdump-rtl-subreg1' ! `-fdump-rtl-subreg2' ! `-fdump-rtl-subreg1' and `-fdump-rtl-subreg2' enable dumping after the two subreg expansion passes. ! `-fdump-rtl-unshare' Dump after all rtl has been unshared. ! `-fdump-rtl-vartrack' Dump after variable tracking. ! `-fdump-rtl-vregs' Dump after converting virtual registers to hard registers. ! `-fdump-rtl-web' Dump after live range splitting. ! `-fdump-rtl-regclass' ! `-fdump-rtl-subregs_of_mode_init' ! `-fdump-rtl-subregs_of_mode_finish' ! `-fdump-rtl-dfinit' ! `-fdump-rtl-dfinish' These dumps are defined but always produce empty files. ! `-da' ! `-fdump-rtl-all' Produce all the dumps listed above. ! `-dA' Annotate the assembler output with miscellaneous debugging information. ! `-dD' Dump all macro definitions, at the end of preprocessing, in addition to normal output. ! `-dH' Produce a core dump whenever an error occurs. ! `-dp' Annotate the assembler output with a comment indicating which pattern and alternative is used. The length of each instruction is also printed. ! `-dP' Dump the RTL in the assembler output as a comment before each ! instruction. Also turns on `-dp' annotation. ! `-dx' Just generate RTL for a function instead of compiling it. ! Usually used with `-fdump-rtl-expand'. ! `-fdump-noaddr' ! When doing debugging dumps, suppress address output. This makes ! it more feasible to use diff on debugging dumps for compiler invocations with different compiler binaries and/or different text / bss / data / heap / stack / dso start locations. ! `-freport-bug' Collect and dump debug information into a temporary file if an internal compiler error (ICE) occurs. ! `-fdump-unnumbered' When doing debugging dumps, suppress instruction numbers and address output. This makes it more feasible to use diff on ! debugging dumps for compiler invocations with different options, ! in particular with and without `-g'. ! `-fdump-unnumbered-links' ! When doing debugging dumps (see `-d' option above), suppress instruction numbers for the links to the previous and next instructions in a sequence. ! `-fdump-translation-unit (C++ only)' ! `-fdump-translation-unit-OPTIONS (C++ only)' Dump a representation of the tree structure for the entire translation unit to a file. The file name is made by appending ! `.tu' to the source file name, and the file is created in the same ! directory as the output file. If the `-OPTIONS' form is used, OPTIONS controls the details of the dump as described for the ! `-fdump-tree' options. ! `-fdump-class-hierarchy (C++ only)' ! `-fdump-class-hierarchy-OPTIONS (C++ only)' Dump a representation of each class's hierarchy and virtual function table layout to a file. The file name is made by ! appending `.class' to the source file name, and the file is ! created in the same directory as the output file. If the ! `-OPTIONS' form is used, OPTIONS controls the details of the dump ! as described for the `-fdump-tree' options. ! `-fdump-ipa-SWITCH' Control the dumping at various stages of inter-procedural analysis language tree to a file. The file name is generated by appending a switch specific suffix to the source file name, and the file is created in the same directory as the output file. The following dumps are possible: ! `all' Enables all inter-procedural analysis dumps. ! `cgraph' Dumps information about call-graph optimization, unused function removal, and inlining decisions. ! `inline' Dump after function inlining. ! ! `-fdump-passes' Dump the list of optimization passes that are turned on and off by the current command-line options. ! `-fdump-statistics-OPTION' Enable and control dumping of pass statistics in a separate file. The file name is generated by appending a suffix ending in ! `.statistics' to the source file name, and the file is created in ! the same directory as the output file. If the `-OPTION' form is ! used, `-stats' causes counters to be summed over the whole ! compilation unit while `-details' dumps every event as the passes generate them. The default with no option is to sum counters for each function compiled. ! `-fdump-tree-SWITCH' ! `-fdump-tree-SWITCH-OPTIONS' ! `-fdump-tree-SWITCH-OPTIONS=FILENAME' Control the dumping at various stages of processing the intermediate language tree to a file. The file name is generated by appending a switch-specific suffix to the source file name, and ! the file is created in the same directory as the output file. In ! case of `=FILENAME' option, the dump is output on the given file ! instead of the auto named dump files. If the `-OPTIONS' form is ! used, OPTIONS is a list of `-' separated options which control the details of the dump. Not all options are applicable to all dumps; those that are not meaningful are ignored. The following options are available ! `address' Print the address of each node. Usually this is not meaningful as it changes according to the environment and ! source file. Its primary use is for tying up a dump file ! with a debug environment. ! ! `asmname' ! If `DECL_ASSEMBLER_NAME' has been set for a given decl, use ! that in the dump instead of `DECL_NAME'. Its primary use is ease of use working backward from mangled names in the assembly file. ! ! `slim' When dumping front-end intermediate representations, inhibit dumping of members of a scope or body of a function merely because that scope has been reached. Only dump such items *************** any of these options for ordinary compil *** 11632,11887 **** When dumping RTL, print the RTL in slim (condensed) form instead of the default LISP-like representation. ! 'raw' Print a raw representation of the tree. By default, trees are pretty-printed into a C-like representation. ! 'details' ! Enable more detailed dumps (not honored by every dump option). ! Also include information from the optimization passes. ! 'stats' Enable dumping various statistics about the pass (not honored by every dump option). ! 'blocks' Enable showing basic block boundaries (disabled in raw dumps). ! 'graph' For each of the other indicated dump files ! ('-fdump-rtl-PASS'), dump a representation of the control flow ! graph suitable for viewing with GraphViz to ! 'FILE.PASSID.PASS.dot'. Each function in the file is pretty-printed as a subgraph, so that GraphViz can render them all in a single plot. ! This option currently only works for RTL dumps, and the RTL is ! always dumped in slim form. ! 'vops' Enable showing virtual operands for every statement. ! 'lineno' Enable showing line numbers for statements. ! 'uid' ! Enable showing the unique ID ('DECL_UID') for each variable. ! 'verbose' Enable showing the tree dump for each statement. ! 'eh' Enable showing the EH region number holding each statement. ! 'scev' Enable showing scalar evolution analysis details. ! 'optimized' Enable showing optimization information (only available in certain passes). ! 'missed' ! Enable showing missed optimization information (only available ! in certain passes). ! 'note' ! Enable other detailed optimization information (only available ! in certain passes). ! '=FILENAME' Instead of an auto named dump file, output into the given file ! name. The file names 'stdout' and 'stderr' are treated specially and are considered already open standard streams. For example, gcc -O2 -ftree-vectorize -fdump-tree-vect-blocks=foo.dump -fdump-tree-pre=stderr file.c ! outputs vectorizer dump into 'foo.dump', while the PRE dump is ! output on to 'stderr'. If two conflicting dump filenames are given for the same pass, then the latter option overrides the earlier one. ! 'split-paths' Dump each function after splitting paths to loop backedges. ! The file name is made by appending '.split-paths' to the source file name. ! 'all' ! Turn on all options, except 'raw', 'slim', 'verbose' and ! 'lineno'. ! 'optall' ! Turn on all optimization options, i.e., 'optimized', 'missed', ! and 'note'. The following tree dumps are possible: ! 'original' ! Dump before any tree based optimization, to 'FILE.original'. ! ! 'optimized' ! Dump after all tree based optimization, to 'FILE.optimized'. ! 'gimple' ! Dump each function before and after the gimplification pass to ! a file. The file name is made by appending '.gimple' to the ! source file name. ! 'cfg' Dump the control flow graph of each function to a file. The ! file name is made by appending '.cfg' to the source file name. ! 'ch' Dump each function after copying loop headers. The file name ! is made by appending '.ch' to the source file name. ! 'ssa' ! Dump SSA related information to a file. The file name is made ! by appending '.ssa' to the source file name. ! 'alias' ! Dump aliasing information for each function. The file name is ! made by appending '.alias' to the source file name. ! 'ccp' Dump each function after CCP. The file name is made by ! appending '.ccp' to the source file name. ! 'storeccp' Dump each function after STORE-CCP. The file name is made by ! appending '.storeccp' to the source file name. ! 'pre' Dump trees after partial redundancy elimination. The file ! name is made by appending '.pre' to the source file name. ! 'fre' Dump trees after full redundancy elimination. The file name ! is made by appending '.fre' to the source file name. ! 'copyprop' Dump trees after copy propagation. The file name is made by ! appending '.copyprop' to the source file name. ! 'store_copyprop' Dump trees after store copy-propagation. The file name is ! made by appending '.store_copyprop' to the source file name. ! 'dce' ! Dump each function after dead code elimination. The file name ! is made by appending '.dce' to the source file name. ! 'sra' Dump each function after performing scalar replacement of ! aggregates. The file name is made by appending '.sra' to the source file name. ! 'sink' Dump each function after performing code sinking. The file ! name is made by appending '.sink' to the source file name. ! 'dom' Dump each function after applying dominator tree ! optimizations. The file name is made by appending '.dom' to the source file name. ! 'dse' ! Dump each function after applying dead store elimination. The ! file name is made by appending '.dse' to the source file name. ! 'phiopt' Dump each function after optimizing PHI nodes into straightline code. The file name is made by appending ! '.phiopt' to the source file name. ! 'backprop' Dump each function after back-propagating use information up the definition chain. The file name is made by appending ! '.backprop' to the source file name. ! 'forwprop' Dump each function after forward propagating single use ! variables. The file name is made by appending '.forwprop' to the source file name. ! 'nrv' Dump each function after applying the named return value optimization on generic trees. The file name is made by ! appending '.nrv' to the source file name. ! 'vect' ! Dump each function after applying vectorization of loops. The ! file name is made by appending '.vect' to the source file name. ! 'slp' Dump each function after applying vectorization of basic ! blocks. The file name is made by appending '.slp' to the source file name. ! 'vrp' ! Dump each function after Value Range Propagation (VRP). The ! file name is made by appending '.vrp' to the source file name. ! 'oaccdevlow' Dump each function after applying device-specific OpenACC transformations. The file name is made by appending ! '.oaccdevlow' to the source file name. ! 'all' ! Enable all the available tree dumps with the flags provided in ! this option. ! '-fopt-info' ! '-fopt-info-OPTIONS' ! '-fopt-info-OPTIONS=FILENAME' ! Controls optimization dumps from various optimization passes. If ! the '-OPTIONS' form is used, OPTIONS is a list of '-' separated option keywords to select the dump details and optimizations. The OPTIONS can be divided into two groups: options describing the verbosity of the dump, and options describing which optimizations ! should be included. The options from both the groups can be freely ! mixed as they are non-overlapping. However, in case of any conflicts, the later options override the earlier options on the command line. The following options control the dump verbosity: ! 'optimized' Print information when an optimization is successfully ! applied. It is up to a pass to decide which information is ! relevant. For example, the vectorizer passes print the source location of loops which are successfully vectorized. ! 'missed' ! Print information about missed optimizations. Individual passes control which information to include in the output. ! 'note' Print verbose information about optimizations, such as certain transformations, more detailed messages about decisions etc. ! 'all' ! Print detailed optimization information. This includes ! 'optimized', 'missed', and 'note'. One or more of the following option keywords can be used to describe a group of optimizations: ! 'ipa' Enable dumps from all interprocedural optimizations. ! 'loop' Enable dumps from all loop optimizations. ! 'inline' Enable dumps from all inlining optimizations. ! 'vec' Enable dumps from all vectorization optimizations. ! 'optall' ! Enable dumps from all optimizations. This is a superset of the optimization groups listed above. ! If OPTIONS is omitted, it defaults to 'optimized-optall', which means to dump all info about successful optimizations from all the passes. ! If the FILENAME is provided, then the dumps from all the applicable ! optimizations are concatenated into the FILENAME. Otherwise the ! dump is output onto 'stderr'. Though multiple '-fopt-info' options ! are accepted, only one of them can include a FILENAME. If other ! filenames are provided then all but the first such option are ! ignored. Note that the output FILENAME is overwritten in case of multiple ! translation units. If a combined output from multiple translation ! units is desired, 'stderr' should be used instead. In the following example, the optimization info is output to ! 'stderr': gcc -O3 -fopt-info --- 11696,11974 ---- When dumping RTL, print the RTL in slim (condensed) form instead of the default LISP-like representation. ! ! `raw' Print a raw representation of the tree. By default, trees are pretty-printed into a C-like representation. ! ! `details' ! Enable more detailed dumps (not honored by every dump ! option). Also include information from the optimization ! passes. ! ! `stats' Enable dumping various statistics about the pass (not honored by every dump option). ! ! `blocks' Enable showing basic block boundaries (disabled in raw dumps). ! ! `graph' For each of the other indicated dump files ! (`-fdump-rtl-PASS'), dump a representation of the control ! flow graph suitable for viewing with GraphViz to ! `FILE.PASSID.PASS.dot'. Each function in the file is pretty-printed as a subgraph, so that GraphViz can render them all in a single plot. ! This option currently only works for RTL dumps, and the RTL ! is always dumped in slim form. ! ! `vops' Enable showing virtual operands for every statement. ! ! `lineno' Enable showing line numbers for statements. ! ! `uid' ! Enable showing the unique ID (`DECL_UID') for each variable. ! ! `verbose' Enable showing the tree dump for each statement. ! ! `eh' Enable showing the EH region number holding each statement. ! ! `scev' Enable showing scalar evolution analysis details. ! ! `optimized' Enable showing optimization information (only available in certain passes). ! ! `missed' ! Enable showing missed optimization information (only ! available in certain passes). ! ! `note' ! Enable other detailed optimization information (only ! available in certain passes). ! ! `=FILENAME' Instead of an auto named dump file, output into the given file ! name. The file names `stdout' and `stderr' are treated specially and are considered already open standard streams. For example, gcc -O2 -ftree-vectorize -fdump-tree-vect-blocks=foo.dump -fdump-tree-pre=stderr file.c ! outputs vectorizer dump into `foo.dump', while the PRE dump is ! output on to `stderr'. If two conflicting dump filenames are given for the same pass, then the latter option overrides the earlier one. ! `split-paths' Dump each function after splitting paths to loop backedges. ! The file name is made by appending `.split-paths' to the source file name. ! `all' ! Turn on all options, except `raw', `slim', `verbose' and ! `lineno'. ! `optall' ! Turn on all optimization options, i.e., `optimized', ! `missed', and `note'. The following tree dumps are possible: + `original' + Dump before any tree based optimization, to `FILE.original'. ! `optimized' ! Dump after all tree based optimization, to `FILE.optimized'. ! `gimple' ! Dump each function before and after the gimplification pass ! to a file. The file name is made by appending `.gimple' to ! the source file name. ! `cfg' Dump the control flow graph of each function to a file. The ! file name is made by appending `.cfg' to the source file name. ! `ch' Dump each function after copying loop headers. The file name ! is made by appending `.ch' to the source file name. ! `ssa' ! Dump SSA related information to a file. The file name is ! made by appending `.ssa' to the source file name. ! `alias' ! Dump aliasing information for each function. The file name ! is made by appending `.alias' to the source file name. ! `ccp' Dump each function after CCP. The file name is made by ! appending `.ccp' to the source file name. ! `storeccp' Dump each function after STORE-CCP. The file name is made by ! appending `.storeccp' to the source file name. ! `pre' Dump trees after partial redundancy elimination. The file ! name is made by appending `.pre' to the source file name. ! `fre' Dump trees after full redundancy elimination. The file name ! is made by appending `.fre' to the source file name. ! `copyprop' Dump trees after copy propagation. The file name is made by ! appending `.copyprop' to the source file name. ! `store_copyprop' Dump trees after store copy-propagation. The file name is ! made by appending `.store_copyprop' to the source file name. ! `dce' ! Dump each function after dead code elimination. The file ! name is made by appending `.dce' to the source file name. ! `sra' Dump each function after performing scalar replacement of ! aggregates. The file name is made by appending `.sra' to the source file name. ! `sink' Dump each function after performing code sinking. The file ! name is made by appending `.sink' to the source file name. ! `dom' Dump each function after applying dominator tree ! optimizations. The file name is made by appending `.dom' to the source file name. ! `dse' ! Dump each function after applying dead store elimination. ! The file name is made by appending `.dse' to the source file ! name. ! `phiopt' Dump each function after optimizing PHI nodes into straightline code. The file name is made by appending ! `.phiopt' to the source file name. ! `backprop' Dump each function after back-propagating use information up the definition chain. The file name is made by appending ! `.backprop' to the source file name. ! `forwprop' Dump each function after forward propagating single use ! variables. The file name is made by appending `.forwprop' to the source file name. ! `nrv' Dump each function after applying the named return value optimization on generic trees. The file name is made by ! appending `.nrv' to the source file name. ! `vect' ! Dump each function after applying vectorization of loops. ! The file name is made by appending `.vect' to the source file name. ! `slp' Dump each function after applying vectorization of basic ! blocks. The file name is made by appending `.slp' to the source file name. ! `vrp' ! Dump each function after Value Range Propagation (VRP). The ! file name is made by appending `.vrp' to the source file name. ! `oaccdevlow' Dump each function after applying device-specific OpenACC transformations. The file name is made by appending ! `.oaccdevlow' to the source file name. ! `all' ! Enable all the available tree dumps with the flags provided ! in this option. ! `-fopt-info' ! `-fopt-info-OPTIONS' ! `-fopt-info-OPTIONS=FILENAME' ! Controls optimization dumps from various optimization passes. If ! the `-OPTIONS' form is used, OPTIONS is a list of `-' separated option keywords to select the dump details and optimizations. The OPTIONS can be divided into two groups: options describing the verbosity of the dump, and options describing which optimizations ! should be included. The options from both the groups can be freely ! mixed as they are non-overlapping. However, in case of any conflicts, the later options override the earlier options on the command line. The following options control the dump verbosity: ! `optimized' Print information when an optimization is successfully ! applied. It is up to a pass to decide which information is ! relevant. For example, the vectorizer passes print the source location of loops which are successfully vectorized. ! ! `missed' ! Print information about missed optimizations. Individual passes control which information to include in the output. ! ! `note' Print verbose information about optimizations, such as certain transformations, more detailed messages about decisions etc. ! ! `all' ! Print detailed optimization information. This includes ! `optimized', `missed', and `note'. One or more of the following option keywords can be used to describe a group of optimizations: ! `ipa' Enable dumps from all interprocedural optimizations. ! ! `loop' Enable dumps from all loop optimizations. ! ! `inline' Enable dumps from all inlining optimizations. ! ! `vec' Enable dumps from all vectorization optimizations. ! ! `optall' ! Enable dumps from all optimizations. This is a superset of the optimization groups listed above. ! If OPTIONS is omitted, it defaults to `optimized-optall', which means to dump all info about successful optimizations from all the passes. ! If the FILENAME is provided, then the dumps from all the ! applicable optimizations are concatenated into the FILENAME. ! Otherwise the dump is output onto `stderr'. Though multiple ! `-fopt-info' options are accepted, only one of them can include a ! FILENAME. If other filenames are provided then all but the first ! such option are ignored. Note that the output FILENAME is overwritten in case of multiple ! translation units. If a combined output from multiple translation ! units is desired, `stderr' should be used instead. In the following example, the optimization info is output to ! `stderr': gcc -O3 -fopt-info *************** any of these options for ordinary compil *** 11889,11981 **** gcc -O3 -fopt-info-missed=missed.all outputs missed optimization report from all the passes into ! 'missed.all', and this one: gcc -O2 -ftree-vectorize -fopt-info-vec-missed prints information about missed optimization opportunities from ! vectorization passes on 'stderr'. Note that ! '-fopt-info-vec-missed' is equivalent to '-fopt-info-missed-vec'. As another example, gcc -O3 -fopt-info-inline-optimized-missed=inline.txt ! outputs information about missed optimizations as well as optimized ! locations from all the inlining passes into 'inline.txt'. Finally, consider: gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt ! Here the two output filenames 'vec.miss' and 'loop.opt' are in ! conflict since only one output file is allowed. In this case, only the first option takes effect and the subsequent options are ! ignored. Thus only 'vec.miss' is produced which contains dumps from the vectorizer about missed opportunities. ! '-fsched-verbose=N' On targets that use instruction scheduling, this option controls the amount of debugging output the scheduler prints to the dump files. ! For N greater than zero, '-fsched-verbose' outputs the same ! information as '-fdump-rtl-sched1' and '-fdump-rtl-sched2'. For N greater than one, it also output basic block probabilities, detailed ready list information and unit/insn info. For N greater than two, it includes RTL at abort point, control-flow and regions ! info. And for N over four, '-fsched-verbose' also includes dependence info. ! '-fenable-KIND-PASS' ! '-fdisable-KIND-PASS=RANGE-LIST' ! This is a set of options that are used to explicitly disable/enable optimization passes. These options are intended for use for ! debugging GCC. Compiler users should use regular options for enabling/disabling passes instead. ! '-fdisable-ipa-PASS' ! Disable IPA pass PASS. PASS is the pass name. If the same ! pass is statically invoked in the compiler multiple times, the ! pass name should be appended with a sequential number starting ! from 1. ! '-fdisable-rtl-PASS' ! '-fdisable-rtl-PASS=RANGE-LIST' Disable RTL pass PASS. PASS is the pass name. If the same ! pass is statically invoked in the compiler multiple times, the ! pass name should be appended with a sequential number starting ! from 1. RANGE-LIST is a comma-separated list of function ! ranges or assembler names. Each range is a number pair ! separated by a colon. The range is inclusive in both ends. ! If the range is trivial, the number pair can be simplified as ! a single number. If the function's call graph node's UID ! falls within one of the specified ranges, the PASS is disabled ! for that function. The UID is shown in the function header of ! a dump file, and the pass names can be dumped by using option ! '-fdump-passes'. ! '-fdisable-tree-PASS' ! '-fdisable-tree-PASS=RANGE-LIST' ! Disable tree pass PASS. See '-fdisable-rtl' for the description of option arguments. ! '-fenable-ipa-PASS' Enable IPA pass PASS. PASS is the pass name. If the same ! pass is statically invoked in the compiler multiple times, the ! pass name should be appended with a sequential number starting ! from 1. ! '-fenable-rtl-PASS' ! '-fenable-rtl-PASS=RANGE-LIST' ! Enable RTL pass PASS. See '-fdisable-rtl' for option argument description and examples. ! '-fenable-tree-PASS' ! '-fenable-tree-PASS=RANGE-LIST' ! Enable tree pass PASS. See '-fdisable-rtl' for the description of option arguments. Here are some examples showing uses of these options. --- 11976,12068 ---- gcc -O3 -fopt-info-missed=missed.all outputs missed optimization report from all the passes into ! `missed.all', and this one: gcc -O2 -ftree-vectorize -fopt-info-vec-missed prints information about missed optimization opportunities from ! vectorization passes on `stderr'. Note that ! `-fopt-info-vec-missed' is equivalent to `-fopt-info-missed-vec'. As another example, gcc -O3 -fopt-info-inline-optimized-missed=inline.txt ! outputs information about missed optimizations as well as ! optimized locations from all the inlining passes into `inline.txt'. Finally, consider: gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt ! Here the two output filenames `vec.miss' and `loop.opt' are in ! conflict since only one output file is allowed. In this case, only the first option takes effect and the subsequent options are ! ignored. Thus only `vec.miss' is produced which contains dumps from the vectorizer about missed opportunities. ! `-fsched-verbose=N' On targets that use instruction scheduling, this option controls the amount of debugging output the scheduler prints to the dump files. ! For N greater than zero, `-fsched-verbose' outputs the same ! information as `-fdump-rtl-sched1' and `-fdump-rtl-sched2'. For N greater than one, it also output basic block probabilities, detailed ready list information and unit/insn info. For N greater than two, it includes RTL at abort point, control-flow and regions ! info. And for N over four, `-fsched-verbose' also includes dependence info. ! `-fenable-KIND-PASS' ! `-fdisable-KIND-PASS=RANGE-LIST' This is a set of options that are used to explicitly disable/enable optimization passes. These options are intended for use for ! debugging GCC. Compiler users should use regular options for enabling/disabling passes instead. ! `-fdisable-ipa-PASS' ! Disable IPA pass PASS. PASS is the pass name. If the same ! pass is statically invoked in the compiler multiple times, ! the pass name should be appended with a sequential number ! starting from 1. ! `-fdisable-rtl-PASS' ! `-fdisable-rtl-PASS=RANGE-LIST' Disable RTL pass PASS. PASS is the pass name. If the same ! pass is statically invoked in the compiler multiple times, ! the pass name should be appended with a sequential number ! starting from 1. RANGE-LIST is a comma-separated list of ! function ranges or assembler names. Each range is a number ! pair separated by a colon. The range is inclusive in both ! ends. If the range is trivial, the number pair can be ! simplified as a single number. If the function's call graph ! node's UID falls within one of the specified ranges, the PASS ! is disabled for that function. The UID is shown in the ! function header of a dump file, and the pass names can be ! dumped by using option `-fdump-passes'. ! `-fdisable-tree-PASS' ! `-fdisable-tree-PASS=RANGE-LIST' ! Disable tree pass PASS. See `-fdisable-rtl' for the description of option arguments. ! `-fenable-ipa-PASS' Enable IPA pass PASS. PASS is the pass name. If the same ! pass is statically invoked in the compiler multiple times, ! the pass name should be appended with a sequential number ! starting from 1. ! `-fenable-rtl-PASS' ! `-fenable-rtl-PASS=RANGE-LIST' ! Enable RTL pass PASS. See `-fdisable-rtl' for option argument description and examples. ! `-fenable-tree-PASS' ! `-fenable-tree-PASS=RANGE-LIST' ! Enable tree pass PASS. See `-fdisable-rtl' for the description of option arguments. + Here are some examples showing uses of these options. *************** any of these options for ordinary compil *** 11994,12010 **** # enable tree full unroll -fenable-tree-unroll ! ! '-fchecking' Enable internal consistency checking. The default depends on the compiler configuration. ! '-frandom-seed=STRING' This option provides a seed that GCC uses in place of random numbers in generating certain symbol names that have to be different in every compiled file. It is also used to place unique stamps in coverage data files and the object files that produce ! them. You can use the '-frandom-seed' option to produce reproducibly identical object files. The STRING can either be a number (decimal, octal or hex) or an --- 12081,12096 ---- # enable tree full unroll -fenable-tree-unroll ! `-fchecking' Enable internal consistency checking. The default depends on the compiler configuration. ! `-frandom-seed=STRING' This option provides a seed that GCC uses in place of random numbers in generating certain symbol names that have to be different in every compiled file. It is also used to place unique stamps in coverage data files and the object files that produce ! them. You can use the `-frandom-seed' option to produce reproducibly identical object files. The STRING can either be a number (decimal, octal or hex) or an *************** any of these options for ordinary compil *** 12013,12050 **** The STRING should be different for every file you compile. ! '-save-temps' ! '-save-temps=cwd' Store the usual "temporary" intermediate files permanently; place them in the current directory and name them based on the source ! file. Thus, compiling 'foo.c' with '-c -save-temps' produces files ! 'foo.i' and 'foo.s', as well as 'foo.o'. This creates a ! preprocessed 'foo.i' output file even though the compiler now normally uses an integrated preprocessor. ! When used in combination with the '-x' command-line option, ! '-save-temps' is sensible enough to avoid over writing an input source file with the same extension as an intermediate file. The corresponding intermediate file may be obtained by renaming the ! source file before using '-save-temps'. If you invoke GCC in parallel, compiling several different source files that share a common base name in different subdirectories or the same source file compiled for multiple output destinations, it ! is likely that the different parallel compilers will interfere with ! each other, and overwrite the temporary files. For instance: gcc -save-temps -o outdir1/foo.o indir1/foo.c& gcc -save-temps -o outdir2/foo.o indir2/foo.c& ! may result in 'foo.i' and 'foo.o' being written to simultaneously by both compilers. ! '-save-temps=obj' Store the usual "temporary" intermediate files permanently. If the ! '-o' option is used, the temporary files are based on the object ! file. If the '-o' option is not used, the '-save-temps=obj' switch ! behaves like '-save-temps'. For example: --- 12099,12136 ---- The STRING should be different for every file you compile. ! `-save-temps' ! `-save-temps=cwd' Store the usual "temporary" intermediate files permanently; place them in the current directory and name them based on the source ! file. Thus, compiling `foo.c' with `-c -save-temps' produces files ! `foo.i' and `foo.s', as well as `foo.o'. This creates a ! preprocessed `foo.i' output file even though the compiler now normally uses an integrated preprocessor. ! When used in combination with the `-x' command-line option, ! `-save-temps' is sensible enough to avoid over writing an input source file with the same extension as an intermediate file. The corresponding intermediate file may be obtained by renaming the ! source file before using `-save-temps'. If you invoke GCC in parallel, compiling several different source files that share a common base name in different subdirectories or the same source file compiled for multiple output destinations, it ! is likely that the different parallel compilers will interfere ! with each other, and overwrite the temporary files. For instance: gcc -save-temps -o outdir1/foo.o indir1/foo.c& gcc -save-temps -o outdir2/foo.o indir2/foo.c& ! may result in `foo.i' and `foo.o' being written to simultaneously by both compilers. ! `-save-temps=obj' Store the usual "temporary" intermediate files permanently. If the ! `-o' option is used, the temporary files are based on the object ! file. If the `-o' option is not used, the `-save-temps=obj' ! switch behaves like `-save-temps'. For example: *************** any of these options for ordinary compil *** 12052,12061 **** gcc -save-temps=obj -c bar.c -o dir/xbar.o gcc -save-temps=obj foobar.c -o dir2/yfoobar ! creates 'foo.i', 'foo.s', 'dir/xbar.i', 'dir/xbar.s', ! 'dir2/yfoobar.i', 'dir2/yfoobar.s', and 'dir2/yfoobar.o'. ! '-time[=FILE]' Report the CPU time taken by each subprocess in the compilation sequence. For C source files, this is the compiler proper and assembler (plus the linker if linking is done). --- 12138,12147 ---- gcc -save-temps=obj -c bar.c -o dir/xbar.o gcc -save-temps=obj foobar.c -o dir2/yfoobar ! creates `foo.i', `foo.s', `dir/xbar.i', `dir/xbar.s', ! `dir2/yfoobar.i', `dir2/yfoobar.s', and `dir2/yfoobar.o'. ! `-time[=FILE]' Report the CPU time taken by each subprocess in the compilation sequence. For C source files, this is the compiler proper and assembler (plus the linker if linking is done). *************** any of these options for ordinary compil *** 12071,12078 **** time", time spent executing operating system routines on behalf of the program. Both numbers are in seconds. ! With the specification of an output file, the output is appended to ! the named file, and it looks like this: 0.12 0.01 cc1 OPTIONS 0.00 0.01 as OPTIONS --- 12157,12164 ---- time", time spent executing operating system routines on behalf of the program. Both numbers are in seconds. ! With the specification of an output file, the output is appended ! to the named file, and it looks like this: 0.12 0.01 cc1 OPTIONS 0.00 0.01 as OPTIONS *************** any of these options for ordinary compil *** 12082,12310 **** one can later tell what file was being compiled, and with which options. ! '-fdump-final-insns[=FILE]' Dump the final internal representation (RTL) to FILE. If the ! optional argument is omitted (or if FILE is '.'), the name of the ! dump file is determined by appending '.gkd' to the compilation output file name. ! '-fcompare-debug[=OPTS]' If no error occurs during compilation, run the compiler a second ! time, adding OPTS and '-fcompare-debug-second' to the arguments passed to the second compilation. Dump the final internal representation in both compilations, and print an error if they differ. ! If the equal sign is omitted, the default '-gtoggle' is used. ! The environment variable 'GCC_COMPARE_DEBUG', if defined, non-empty ! and nonzero, implicitly enables '-fcompare-debug'. If ! 'GCC_COMPARE_DEBUG' is defined to a string starting with a dash, ! then it is used for OPTS, otherwise the default '-gtoggle' is used. ! '-fcompare-debug=', with the equal sign but without OPTS, is ! equivalent to '-fno-compare-debug', which disables the dumping of the final representation and the second compilation, preventing ! even 'GCC_COMPARE_DEBUG' from taking effect. ! To verify full coverage during '-fcompare-debug' testing, set ! 'GCC_COMPARE_DEBUG' to say '-fcompare-debug-not-overridden', which GCC rejects as an invalid option in any actual compilation (rather than preprocessing, assembly or linking). To get just a warning, ! setting 'GCC_COMPARE_DEBUG' to '-w%n-fcompare-debug not overridden' ! will do. ! '-fcompare-debug-second' This option is implicitly passed to the compiler for the second ! compilation requested by '-fcompare-debug', along with options to silence warnings, and omitting other options that would cause side-effect compiler outputs to files or to the standard output. Dump files and preserved temporary files are renamed so as to ! contain the '.gk' additional extension during the second compilation, to avoid overwriting those generated by the first. When this option is passed to the compiler driver, it causes the _first_ compilation to be skipped, which makes it useful for little other than debugging the compiler proper. ! '-gtoggle' Turn off generation of debug info, if leaving out this option generates it, or turn it on at level 2 otherwise. The position of this argument in the command line does not matter; it takes effect ! after all other options are processed, and it does so only once, no ! matter how many times it is given. This is mainly intended to be ! used with '-fcompare-debug'. ! '-fvar-tracking-assignments-toggle' ! Toggle '-fvar-tracking-assignments', in the same way that ! '-gtoggle' toggles '-g'. ! '-Q' Makes the compiler print out each function name as it is compiled, and print some statistics about each pass when it finishes. ! '-ftime-report' ! Makes the compiler print some statistics about the time consumed by ! each pass when it finishes. ! '-fira-verbose=N' Control the verbosity of the dump file for the integrated register allocator. The default value is 5. If the value N is greater or equal to 10, the dump output is sent to stderr using the same format as N minus 10. ! '-flto-report' Prints a report with internal details on the workings of the ! link-time optimizer. The contents of this report vary from version ! to version. It is meant to be useful to GCC developers when ! processing object files in LTO mode (via '-flto'). Disabled by default. ! '-flto-report-wpa' ! Like '-flto-report', but only print for the WPA phase of Link Time Optimization. ! '-fmem-report' Makes the compiler print some statistics about permanent memory allocation when it finishes. ! '-fmem-report-wpa' Makes the compiler print some statistics about permanent memory allocation for the WPA phase only. ! '-fpre-ipa-mem-report' ! '-fpost-ipa-mem-report' Makes the compiler print some statistics about permanent memory allocation before or after interprocedural optimization. ! '-fprofile-report' Makes the compiler print some statistics about consistency of the (estimated) profile and effect of individual passes. ! '-fstack-usage' Makes the compiler output stack usage information for the program, on a per-function basis. The filename for the dump is made by ! appending '.su' to the AUXNAME. AUXNAME is generated from the name ! of the output file, if explicitly specified and it is not an executable, otherwise it is the basename of the source file. An entry is made up of three fields: * The name of the function. * A number of bytes. - * One or more qualifiers: 'static', 'dynamic', 'bounded'. ! The qualifier 'static' means that the function manipulates the stack statically: a fixed number of bytes are allocated for the frame on function entry and released on function exit; no stack adjustments are otherwise made in the function. The second field is this fixed number of bytes. ! The qualifier 'dynamic' means that the function manipulates the stack dynamically: in addition to the static allocation described above, stack adjustments are made in the body of the function, for example to push/pop arguments around function calls. If the ! qualifier 'bounded' is also present, the amount of these adjustments is bounded at compile time and the second field is an upper bound of the total amount of stack used by the function. If it is not present, the amount of these adjustments is not bounded at compile time and the second field only represents the bounded part. ! '-fstats' Emit statistics about front-end processing at the end of the compilation. This option is supported only by the C++ front end, ! and the information is generally only useful to the G++ development ! team. ! '-fdbg-cnt-list' Print the name and the counter upper bound for all debug counters. ! '-fdbg-cnt=COUNTER-VALUE-LIST' Set the internal debug counter upper bound. COUNTER-VALUE-LIST is a comma-separated list of NAME:VALUE pairs which sets the upper ! bound of each debug counter NAME to VALUE. All debug counters have ! the initial upper bound of 'UINT_MAX'; thus 'dbg_cnt' returns true ! always unless the upper bound is set by this option. For example, ! with '-fdbg-cnt=dce:10,tail_call:0', 'dbg_cnt(dce)' returns true ! only for first 10 invocations. ! '-print-file-name=LIBRARY' ! Print the full absolute name of the library file LIBRARY that would ! be used when linking--and don't do anything else. With this option, GCC does not compile or link anything; it just prints the file name. ! '-print-multi-directory' Print the directory name corresponding to the multilib selected by any other switches present in the command line. This directory is ! supposed to exist in 'GCC_EXEC_PREFIX'. ! '-print-multi-lib' Print the mapping from multilib directory names to compiler switches that enable them. The directory name is separated from ! the switches by ';', and each switch starts with an '@' instead of ! the '-', without spaces between multiple switches. This is supposed to ease shell processing. ! '-print-multi-os-directory' Print the path to OS libraries for the selected multilib, relative ! to some 'lib' subdirectory. If OS libraries are present in the ! 'lib' subdirectory and no multilibs are used, this is usually just ! '.', if OS libraries are present in 'libSUFFIX' sibling directories ! this prints e.g. '../lib64', '../lib' or '../lib32', or if OS ! libraries are present in 'lib/SUBDIR' subdirectories it prints e.g. ! 'amd64', 'sparcv9' or 'ev6'. ! '-print-multiarch' ! Print the path to OS libraries for the selected multiarch, relative ! to some 'lib' subdirectory. ! '-print-prog-name=PROGRAM' ! Like '-print-file-name', but searches for a program such as 'cpp'. ! '-print-libgcc-file-name' ! Same as '-print-file-name=libgcc.a'. ! This is useful when you use '-nostdlib' or '-nodefaultlibs' but you ! do want to link with 'libgcc.a'. You can do: gcc -nostdlib FILES... `gcc -print-libgcc-file-name` ! '-print-search-dirs' Print the name of the configured installation directory and a list ! of program and library directories 'gcc' searches--and don't do anything else. ! This is useful when 'gcc' prints the error message 'installation problem, cannot exec cpp0: No such file or directory'. To resolve ! this you either need to put 'cpp0' and the other compiler ! components where 'gcc' expects to find them, or you can set the ! environment variable 'GCC_EXEC_PREFIX' to the directory where you ! installed them. Don't forget the trailing '/'. *Note Environment Variables::. ! '-print-sysroot' ! Print the target sysroot directory that is used during compilation. ! This is the target sysroot specified either at configure time or ! using the '--sysroot' option, possibly with an extra suffix that ! depends on compilation options. If no target sysroot is specified, ! the option prints nothing. ! '-print-sysroot-headers-suffix' Print the suffix added to the target sysroot when searching for headers, or give an error if the compiler is not configured with such a suffix--and don't do anything else. ! '-dumpmachine' Print the compiler's target machine (for example, ! 'i686-pc-linux-gnu')--and don't do anything else. ! '-dumpversion' ! Print the compiler version (for example, '3.0')--and don't do anything else. ! '-dumpspecs' Print the compiler's built-in specs--and don't do anything else. (This is used when GCC itself is being built.) *Note Spec Files::. --- 12168,12399 ---- one can later tell what file was being compiled, and with which options. ! `-fdump-final-insns[=FILE]' Dump the final internal representation (RTL) to FILE. If the ! optional argument is omitted (or if FILE is `.'), the name of the ! dump file is determined by appending `.gkd' to the compilation output file name. ! `-fcompare-debug[=OPTS]' If no error occurs during compilation, run the compiler a second ! time, adding OPTS and `-fcompare-debug-second' to the arguments passed to the second compilation. Dump the final internal representation in both compilations, and print an error if they differ. ! If the equal sign is omitted, the default `-gtoggle' is used. ! The environment variable `GCC_COMPARE_DEBUG', if defined, non-empty ! and nonzero, implicitly enables `-fcompare-debug'. If ! `GCC_COMPARE_DEBUG' is defined to a string starting with a dash, ! then it is used for OPTS, otherwise the default `-gtoggle' is used. ! `-fcompare-debug=', with the equal sign but without OPTS, is ! equivalent to `-fno-compare-debug', which disables the dumping of the final representation and the second compilation, preventing ! even `GCC_COMPARE_DEBUG' from taking effect. ! To verify full coverage during `-fcompare-debug' testing, set ! `GCC_COMPARE_DEBUG' to say `-fcompare-debug-not-overridden', which GCC rejects as an invalid option in any actual compilation (rather than preprocessing, assembly or linking). To get just a warning, ! setting `GCC_COMPARE_DEBUG' to `-w%n-fcompare-debug not ! overridden' will do. ! `-fcompare-debug-second' This option is implicitly passed to the compiler for the second ! compilation requested by `-fcompare-debug', along with options to silence warnings, and omitting other options that would cause side-effect compiler outputs to files or to the standard output. Dump files and preserved temporary files are renamed so as to ! contain the `.gk' additional extension during the second compilation, to avoid overwriting those generated by the first. When this option is passed to the compiler driver, it causes the _first_ compilation to be skipped, which makes it useful for little other than debugging the compiler proper. ! `-gtoggle' Turn off generation of debug info, if leaving out this option generates it, or turn it on at level 2 otherwise. The position of this argument in the command line does not matter; it takes effect ! after all other options are processed, and it does so only once, ! no matter how many times it is given. This is mainly intended to ! be used with `-fcompare-debug'. ! `-fvar-tracking-assignments-toggle' ! Toggle `-fvar-tracking-assignments', in the same way that ! `-gtoggle' toggles `-g'. ! `-Q' Makes the compiler print out each function name as it is compiled, and print some statistics about each pass when it finishes. ! `-ftime-report' ! Makes the compiler print some statistics about the time consumed ! by each pass when it finishes. ! `-fira-verbose=N' Control the verbosity of the dump file for the integrated register allocator. The default value is 5. If the value N is greater or equal to 10, the dump output is sent to stderr using the same format as N minus 10. ! `-flto-report' Prints a report with internal details on the workings of the ! link-time optimizer. The contents of this report vary from ! version to version. It is meant to be useful to GCC developers ! when processing object files in LTO mode (via `-flto'). Disabled by default. ! `-flto-report-wpa' ! Like `-flto-report', but only print for the WPA phase of Link Time Optimization. ! `-fmem-report' Makes the compiler print some statistics about permanent memory allocation when it finishes. ! `-fmem-report-wpa' Makes the compiler print some statistics about permanent memory allocation for the WPA phase only. ! `-fpre-ipa-mem-report' ! ! `-fpost-ipa-mem-report' Makes the compiler print some statistics about permanent memory allocation before or after interprocedural optimization. ! `-fprofile-report' Makes the compiler print some statistics about consistency of the (estimated) profile and effect of individual passes. ! `-fstack-usage' Makes the compiler output stack usage information for the program, on a per-function basis. The filename for the dump is made by ! appending `.su' to the AUXNAME. AUXNAME is generated from the ! name of the output file, if explicitly specified and it is not an executable, otherwise it is the basename of the source file. An entry is made up of three fields: * The name of the function. + * A number of bytes. ! * One or more qualifiers: `static', `dynamic', `bounded'. ! ! The qualifier `static' means that the function manipulates the stack statically: a fixed number of bytes are allocated for the frame on function entry and released on function exit; no stack adjustments are otherwise made in the function. The second field is this fixed number of bytes. ! The qualifier `dynamic' means that the function manipulates the stack dynamically: in addition to the static allocation described above, stack adjustments are made in the body of the function, for example to push/pop arguments around function calls. If the ! qualifier `bounded' is also present, the amount of these adjustments is bounded at compile time and the second field is an upper bound of the total amount of stack used by the function. If it is not present, the amount of these adjustments is not bounded at compile time and the second field only represents the bounded part. ! `-fstats' Emit statistics about front-end processing at the end of the compilation. This option is supported only by the C++ front end, ! and the information is generally only useful to the G++ ! development team. ! `-fdbg-cnt-list' Print the name and the counter upper bound for all debug counters. ! `-fdbg-cnt=COUNTER-VALUE-LIST' Set the internal debug counter upper bound. COUNTER-VALUE-LIST is a comma-separated list of NAME:VALUE pairs which sets the upper ! bound of each debug counter NAME to VALUE. All debug counters ! have the initial upper bound of `UINT_MAX'; thus `dbg_cnt' returns ! true always unless the upper bound is set by this option. For ! example, with `-fdbg-cnt=dce:10,tail_call:0', `dbg_cnt(dce)' ! returns true only for first 10 invocations. ! `-print-file-name=LIBRARY' ! Print the full absolute name of the library file LIBRARY that ! would be used when linking--and don't do anything else. With this option, GCC does not compile or link anything; it just prints the file name. ! `-print-multi-directory' Print the directory name corresponding to the multilib selected by any other switches present in the command line. This directory is ! supposed to exist in `GCC_EXEC_PREFIX'. ! `-print-multi-lib' Print the mapping from multilib directory names to compiler switches that enable them. The directory name is separated from ! the switches by `;', and each switch starts with an `@' instead of ! the `-', without spaces between multiple switches. This is supposed to ease shell processing. ! `-print-multi-os-directory' Print the path to OS libraries for the selected multilib, relative ! to some `lib' subdirectory. If OS libraries are present in the ! `lib' subdirectory and no multilibs are used, this is usually just ! `.', if OS libraries are present in `libSUFFIX' sibling ! directories this prints e.g. `../lib64', `../lib' or `../lib32', ! or if OS libraries are present in `lib/SUBDIR' subdirectories it ! prints e.g. `amd64', `sparcv9' or `ev6'. ! `-print-multiarch' ! Print the path to OS libraries for the selected multiarch, ! relative to some `lib' subdirectory. ! `-print-prog-name=PROGRAM' ! Like `-print-file-name', but searches for a program such as `cpp'. ! `-print-libgcc-file-name' ! Same as `-print-file-name=libgcc.a'. ! This is useful when you use `-nostdlib' or `-nodefaultlibs' but ! you do want to link with `libgcc.a'. You can do: gcc -nostdlib FILES... `gcc -print-libgcc-file-name` ! `-print-search-dirs' Print the name of the configured installation directory and a list ! of program and library directories `gcc' searches--and don't do anything else. ! This is useful when `gcc' prints the error message `installation problem, cannot exec cpp0: No such file or directory'. To resolve ! this you either need to put `cpp0' and the other compiler ! components where `gcc' expects to find them, or you can set the ! environment variable `GCC_EXEC_PREFIX' to the directory where you ! installed them. Don't forget the trailing `/'. *Note Environment Variables::. ! `-print-sysroot' ! Print the target sysroot directory that is used during ! compilation. This is the target sysroot specified either at ! configure time or using the `--sysroot' option, possibly with an ! extra suffix that depends on compilation options. If no target ! sysroot is specified, the option prints nothing. ! `-print-sysroot-headers-suffix' Print the suffix added to the target sysroot when searching for headers, or give an error if the compiler is not configured with such a suffix--and don't do anything else. ! `-dumpmachine' Print the compiler's target machine (for example, ! `i686-pc-linux-gnu')--and don't do anything else. ! `-dumpversion' ! Print the compiler version (for example, `3.0')--and don't do anything else. ! `-dumpspecs' Print the compiler's built-in specs--and don't do anything else. (This is used when GCC itself is being built.) *Note Spec Files::. *************** File: gcc.info, Node: Submodel Options, *** 12317,12323 **** Each target machine supported by GCC can have its own options--for example, to allow you to compile for a particular processor variant or ABI, or to control optimizations specific to that machine. By ! convention, the names of machine-specific options start with '-m'. Some configurations of the compiler also support additional target-specific options, usually for compatibility with other compilers --- 12406,12412 ---- Each target machine supported by GCC can have its own options--for example, to allow you to compile for a particular processor variant or ABI, or to control optimizations specific to that machine. By ! convention, the names of machine-specific options start with `-m'. Some configurations of the compiler also support additional target-specific options, usually for compatibility with other compilers *************** File: gcc.info, Node: AArch64 Options, *** 12392,12596 **** These options are defined for AArch64 implementations: ! '-mabi=NAME' ! Generate code for the specified data model. Permissible values are ! 'ilp32' for SysV-like data model where int, long int and pointer ! are 32-bit, and 'lp64' for SysV-like data model where int is ! 32-bit, but long int and pointer are 64-bit. The default depends on the specific target configuration. Note that the LP64 and ILP32 ABIs are not link-compatible; you must compile your entire program with the same ABI, and link with a compatible set of libraries. ! '-mbig-endian' Generate big-endian code. This is the default when GCC is ! configured for an 'aarch64_be-*-*' target. ! '-mgeneral-regs-only' Generate code which uses only the general-purpose registers. This will prevent the compiler from using floating-point and Advanced SIMD registers but will not impose any restrictions on the assembler. ! '-mlittle-endian' Generate little-endian code. This is the default when GCC is ! configured for an 'aarch64-*-*' but not an 'aarch64_be-*-*' target. ! '-mcmodel=tiny' Generate code for the tiny code model. The program and its statically defined symbols must be within 1GB of each other. Pointers are 64 bits. Programs can be statically or dynamically linked. This model is not fully implemented and mostly treated as ! 'small'. ! '-mcmodel=small' Generate code for the small code model. The program and its statically defined symbols must be within 4GB of each other. Pointers are 64 bits. Programs can be statically or dynamically linked. This is the default code model. ! '-mcmodel=large' Generate code for the large code model. This makes no assumptions about addresses and sizes of sections. Pointers are 64 bits. Programs can be statically linked only. ! '-mstrict-align' Do not assume that unaligned memory references are handled by the system. ! '-momit-leaf-frame-pointer' ! '-mno-omit-leaf-frame-pointer' Omit or keep the frame pointer in leaf functions. The former behavior is the default. ! '-mtls-dialect=desc' Use TLS descriptors as the thread-local storage mechanism for dynamic accesses of TLS variables. This is the default. ! '-mtls-dialect=traditional' Use traditional TLS as the thread-local storage mechanism for dynamic accesses of TLS variables. ! '-mtls-size=SIZE' Specify bit size of immediate TLS offsets. Valid values are 12, 24, 32, 48. This option depends on binutils higher than 2.25. ! '-mfix-cortex-a53-835769' ! '-mno-fix-cortex-a53-835769' Enable or disable the workaround for the ARM Cortex-A53 erratum number 835769. This involves inserting a NOP instruction between memory instructions and 64-bit integer multiply-accumulate instructions. ! '-mfix-cortex-a53-843419' ! '-mno-fix-cortex-a53-843419' Enable or disable the workaround for the ARM Cortex-A53 erratum number 843419. This erratum workaround is made at link time and this will only pass the corresponding flag to the linker. ! '-mlow-precision-recip-sqrt' ! '-mno-low-precision-recip-sqrt' ! When calculating the reciprocal square root approximation, uses one ! less step than otherwise, thus reducing latency and precision. ! This is only relevant if '-ffast-math' enables the reciprocal square root approximation, which in turn depends on the target processor. ! '-march=NAME' Specify the name of the target architecture and, optionally, one or more feature modifiers. This option has the form ! '-march=ARCH{+[no]FEATURE}*'. ! The permissible values for ARCH are 'armv8-a', 'armv8.1-a' or NATIVE. ! The value 'armv8.1-a' implies 'armv8-a' and enables compiler support for the ARMv8.1 architecture extension. In particular, it ! enables the '+crc' and '+lse' features. ! The value 'native' is available on native AArch64 GNU/Linux and causes the compiler to pick the architecture of the host system. This option has no effect if the compiler is unable to recognize the architecture of the host system, ! The permissible values for FEATURE are listed in the sub-section on ! *note '-march' and '-mcpu' Feature Modifiers: aarch64-feature-modifiers. Where conflicting feature modifiers are specified, the right-most feature is used. GCC uses NAME to determine what kind of instructions it can emit ! when generating assembly code. If '-march' is specified without ! either of '-mtune' or '-mcpu' also being specified, the code is tuned to perform well across a range of target processors implementing the target architecture. ! '-mtune=NAME' Specify the name of the target processor for which GCC should tune the performance of the code. Permissible values for this option ! are: 'generic', 'cortex-a35', 'cortex-a53', 'cortex-a57', ! 'cortex-a72', 'exynos-m1', 'qdf24xx', 'thunderx', 'xgene1'. Additionally, this option can specify that GCC should tune the performance of the code for a big.LITTLE system. Permissible ! values for this option are: 'cortex-a57.cortex-a53', ! 'cortex-a72.cortex-a53'. ! Additionally on native AArch64 GNU/Linux systems the value 'native' ! is available. This option causes the compiler to pick the ! architecture of and tune the performance of the code for the processor of the host system. This option has no effect if the compiler is unable to recognize the architecture of the host system. ! Where none of '-mtune=', '-mcpu=' or '-march=' are specified, the code is tuned to perform well across a range of target processors. This option cannot be suffixed by feature modifiers. ! '-mcpu=NAME' Specify the name of the target processor, optionally suffixed by one or more feature modifiers. This option has the form ! '-mcpu=CPU{+[no]FEATURE}*', where the permissible values for CPU ! are the same as those available for '-mtune'. The permissible values for FEATURE are documented in the sub-section on *note ! '-march' and '-mcpu' Feature Modifiers: aarch64-feature-modifiers. Where conflicting feature modifiers are specified, the right-most feature is used. ! Additionally on native AArch64 GNU/Linux systems the value 'native' ! is available. This option causes the compiler to tune the ! performance of the code for the processor of the host system. This ! option has no effect if the compiler is unable to recognize the ! architecture of the host system. GCC uses NAME to determine what kind of instructions it can emit ! when generating assembly code (as if by '-march') and to determine the target processor for which to tune for performance (as if by ! '-mtune'). Where this option is used in conjunction with '-march' ! or '-mtune', those options take precedence over the appropriate part of this option. ! '-moverride=STRING' Override tuning decisions made by the back-end in response to a ! '-mtune=' switch. The syntax, semantics, and accepted values for STRING in this option are not guaranteed to be consistent across releases. This option is only intended to be useful when developing GCC. ! '-mpc-relative-literal-loads' ! Enable PC relative literal loads. If this option is used, literal pools are assumed to have a range of up to 1MiB and an appropriate ! instruction sequence is used. This option has no impact when used ! with '-mcmodel=tiny'. ! 3.18.1.1 '-march' and '-mcpu' Feature Modifiers ............................................... ! Feature modifiers used with '-march' and '-mcpu' can be any of the ! following and their inverses 'noFEATURE': ! 'crc' Enable CRC extension. This is on by default for ! '-march=armv8.1-a'. ! 'crypto' Enable Crypto extension. This also enables Advanced SIMD and floating-point instructions. ! 'fp' Enable floating-point instructions. This is on by default for all ! possible values for options '-march' and '-mcpu'. ! 'simd' Enable Advanced SIMD instructions. This also enables floating-point instructions. This is on by default for all ! possible values for options '-march' and '-mcpu'. ! 'lse' Enable Large System Extension instructions. This is on by default ! for '-march=armv8.1-a'. ! That is, 'crypto' implies 'simd' implies 'fp'. Conversely, 'nofp' (or ! equivalently, '-mgeneral-regs-only') implies 'nosimd' implies ! 'nocrypto'.  File: gcc.info, Node: Adapteva Epiphany Options, Next: ARC Options, Prev: AArch64 Options, Up: Submodel Options --- 12481,12692 ---- These options are defined for AArch64 implementations: ! `-mabi=NAME' ! Generate code for the specified data model. Permissible values ! are `ilp32' for SysV-like data model where int, long int and ! pointer are 32-bit, and `lp64' for SysV-like data model where int ! is 32-bit, but long int and pointer are 64-bit. The default depends on the specific target configuration. Note that the LP64 and ILP32 ABIs are not link-compatible; you must compile your entire program with the same ABI, and link with a compatible set of libraries. ! `-mbig-endian' Generate big-endian code. This is the default when GCC is ! configured for an `aarch64_be-*-*' target. ! `-mgeneral-regs-only' Generate code which uses only the general-purpose registers. This will prevent the compiler from using floating-point and Advanced SIMD registers but will not impose any restrictions on the assembler. ! `-mlittle-endian' Generate little-endian code. This is the default when GCC is ! configured for an `aarch64-*-*' but not an `aarch64_be-*-*' target. ! `-mcmodel=tiny' Generate code for the tiny code model. The program and its statically defined symbols must be within 1GB of each other. Pointers are 64 bits. Programs can be statically or dynamically linked. This model is not fully implemented and mostly treated as ! `small'. ! `-mcmodel=small' Generate code for the small code model. The program and its statically defined symbols must be within 4GB of each other. Pointers are 64 bits. Programs can be statically or dynamically linked. This is the default code model. ! `-mcmodel=large' Generate code for the large code model. This makes no assumptions about addresses and sizes of sections. Pointers are 64 bits. Programs can be statically linked only. ! `-mstrict-align' Do not assume that unaligned memory references are handled by the system. ! `-momit-leaf-frame-pointer' ! `-mno-omit-leaf-frame-pointer' Omit or keep the frame pointer in leaf functions. The former behavior is the default. ! `-mtls-dialect=desc' Use TLS descriptors as the thread-local storage mechanism for dynamic accesses of TLS variables. This is the default. ! `-mtls-dialect=traditional' Use traditional TLS as the thread-local storage mechanism for dynamic accesses of TLS variables. ! `-mtls-size=SIZE' Specify bit size of immediate TLS offsets. Valid values are 12, 24, 32, 48. This option depends on binutils higher than 2.25. ! `-mfix-cortex-a53-835769' ! `-mno-fix-cortex-a53-835769' Enable or disable the workaround for the ARM Cortex-A53 erratum number 835769. This involves inserting a NOP instruction between memory instructions and 64-bit integer multiply-accumulate instructions. ! `-mfix-cortex-a53-843419' ! `-mno-fix-cortex-a53-843419' Enable or disable the workaround for the ARM Cortex-A53 erratum number 843419. This erratum workaround is made at link time and this will only pass the corresponding flag to the linker. ! `-mlow-precision-recip-sqrt' ! ! `-mno-low-precision-recip-sqrt' ! When calculating the reciprocal square root approximation, uses ! one less step than otherwise, thus reducing latency and precision. ! This is only relevant if `-ffast-math' enables the reciprocal square root approximation, which in turn depends on the target processor. ! `-march=NAME' Specify the name of the target architecture and, optionally, one or more feature modifiers. This option has the form ! `-march=ARCH{+[no]FEATURE}*'. ! The permissible values for ARCH are `armv8-a', `armv8.1-a' or NATIVE. ! The value `armv8.1-a' implies `armv8-a' and enables compiler support for the ARMv8.1 architecture extension. In particular, it ! enables the `+crc' and `+lse' features. ! The value `native' is available on native AArch64 GNU/Linux and causes the compiler to pick the architecture of the host system. This option has no effect if the compiler is unable to recognize the architecture of the host system, ! The permissible values for FEATURE are listed in the sub-section ! on *note `-march' and `-mcpu' Feature Modifiers: aarch64-feature-modifiers. Where conflicting feature modifiers are specified, the right-most feature is used. GCC uses NAME to determine what kind of instructions it can emit ! when generating assembly code. If `-march' is specified without ! either of `-mtune' or `-mcpu' also being specified, the code is tuned to perform well across a range of target processors implementing the target architecture. ! `-mtune=NAME' Specify the name of the target processor for which GCC should tune the performance of the code. Permissible values for this option ! are: `generic', `cortex-a35', `cortex-a53', `cortex-a57', ! `cortex-a72', `exynos-m1', `qdf24xx', `thunderx', `xgene1'. Additionally, this option can specify that GCC should tune the performance of the code for a big.LITTLE system. Permissible ! values for this option are: `cortex-a57.cortex-a53', ! `cortex-a72.cortex-a53'. ! Additionally on native AArch64 GNU/Linux systems the value ! `native' is available. This option causes the compiler to pick ! the architecture of and tune the performance of the code for the processor of the host system. This option has no effect if the compiler is unable to recognize the architecture of the host system. ! Where none of `-mtune=', `-mcpu=' or `-march=' are specified, the code is tuned to perform well across a range of target processors. This option cannot be suffixed by feature modifiers. ! `-mcpu=NAME' Specify the name of the target processor, optionally suffixed by one or more feature modifiers. This option has the form ! `-mcpu=CPU{+[no]FEATURE}*', where the permissible values for CPU ! are the same as those available for `-mtune'. The permissible values for FEATURE are documented in the sub-section on *note ! `-march' and `-mcpu' Feature Modifiers: aarch64-feature-modifiers. Where conflicting feature modifiers are specified, the right-most feature is used. ! Additionally on native AArch64 GNU/Linux systems the value ! `native' is available. This option causes the compiler to tune ! the performance of the code for the processor of the host system. ! This option has no effect if the compiler is unable to recognize ! the architecture of the host system. GCC uses NAME to determine what kind of instructions it can emit ! when generating assembly code (as if by `-march') and to determine the target processor for which to tune for performance (as if by ! `-mtune'). Where this option is used in conjunction with `-march' ! or `-mtune', those options take precedence over the appropriate part of this option. ! `-moverride=STRING' Override tuning decisions made by the back-end in response to a ! `-mtune=' switch. The syntax, semantics, and accepted values for STRING in this option are not guaranteed to be consistent across releases. This option is only intended to be useful when developing GCC. ! `-mpc-relative-literal-loads' ! Enable PC relative literal loads. If this option is used, literal pools are assumed to have a range of up to 1MiB and an appropriate ! instruction sequence is used. This option has no impact when used ! with `-mcmodel=tiny'. ! ! 3.18.1.1 `-march' and `-mcpu' Feature Modifiers ............................................... ! Feature modifiers used with `-march' and `-mcpu' can be any of the ! following and their inverses `noFEATURE': ! `crc' Enable CRC extension. This is on by default for ! `-march=armv8.1-a'. ! ! `crypto' Enable Crypto extension. This also enables Advanced SIMD and floating-point instructions. ! ! `fp' Enable floating-point instructions. This is on by default for all ! possible values for options `-march' and `-mcpu'. ! ! `simd' Enable Advanced SIMD instructions. This also enables floating-point instructions. This is on by default for all ! possible values for options `-march' and `-mcpu'. ! ! `lse' Enable Large System Extension instructions. This is on by default ! for `-march=armv8.1-a'. ! ! That is, `crypto' implies `simd' implies `fp'. Conversely, `nofp' (or ! equivalently, `-mgeneral-regs-only') implies `nosimd' implies ! `nocrypto'.  File: gcc.info, Node: Adapteva Epiphany Options, Next: ARC Options, Prev: AArch64 Options, Up: Submodel Options *************** File: gcc.info, Node: Adapteva Epiphany *** 12598,12638 **** 3.18.2 Adapteva Epiphany Options -------------------------------- ! These '-m' options are defined for Adapteva Epiphany: ! '-mhalf-reg-file' ! Don't allocate any register in the range 'r32'...'r63'. That allows code to run on hardware variants that lack these registers. ! '-mprefer-short-insn-regs' Preferentially allocate registers that allow short instruction generation. This can result in increased instruction count, so this may either reduce or increase overall code size. ! '-mbranch-cost=NUM' Set the cost of branches to roughly NUM "simple" instructions. This cost is only a heuristic and is not guaranteed to produce consistent results across releases. ! '-mcmove' Enable the generation of conditional moves. ! '-mnops=NUM' Emit NUM NOPs before every other generated instruction. ! '-mno-soft-cmpsf' ! For single-precision floating-point comparisons, emit an 'fsub' instruction and test the flags. This is faster than a software comparison, but can get incorrect results in the presence of NaNs, or when two different small numbers are compared such that their ! difference is calculated as zero. The default is '-msoft-cmpsf', which uses slower, but IEEE-compliant, software comparisons. ! '-mstack-offset=NUM' Set the offset between the top of the stack and the stack pointer. E.g., a value of 8 means that the eight bytes in the range ! 'sp+0...sp+7' can be used by leaf functions without stack ! allocation. Values other than '8' or '16' are untested and unlikely to work. Note also that this option changes the ABI; compiling a program with a different stack offset than the libraries have been compiled with generally does not work. This --- 12694,12734 ---- 3.18.2 Adapteva Epiphany Options -------------------------------- ! These `-m' options are defined for Adapteva Epiphany: ! `-mhalf-reg-file' ! Don't allocate any register in the range `r32'...`r63'. That allows code to run on hardware variants that lack these registers. ! `-mprefer-short-insn-regs' Preferentially allocate registers that allow short instruction generation. This can result in increased instruction count, so this may either reduce or increase overall code size. ! `-mbranch-cost=NUM' Set the cost of branches to roughly NUM "simple" instructions. This cost is only a heuristic and is not guaranteed to produce consistent results across releases. ! `-mcmove' Enable the generation of conditional moves. ! `-mnops=NUM' Emit NUM NOPs before every other generated instruction. ! `-mno-soft-cmpsf' ! For single-precision floating-point comparisons, emit an `fsub' instruction and test the flags. This is faster than a software comparison, but can get incorrect results in the presence of NaNs, or when two different small numbers are compared such that their ! difference is calculated as zero. The default is `-msoft-cmpsf', which uses slower, but IEEE-compliant, software comparisons. ! `-mstack-offset=NUM' Set the offset between the top of the stack and the stack pointer. E.g., a value of 8 means that the eight bytes in the range ! `sp+0...sp+7' can be used by leaf functions without stack ! allocation. Values other than `8' or `16' are untested and unlikely to work. Note also that this option changes the ABI; compiling a program with a different stack offset than the libraries have been compiled with generally does not work. This *************** These '-m' options are defined for Adapt *** 12640,12733 **** offset would give you better code, but to actually use a different stack offset to build working programs, it is recommended to configure the toolchain with the appropriate ! '--with-stack-offset=NUM' option. ! '-mno-round-nearest' Make the scheduler assume that the rounding mode has been set to ! truncating. The default is '-mround-nearest'. ! '-mlong-calls' If not otherwise specified by an attribute, assume all calls might ! be beyond the offset range of the 'b' / 'bl' instructions, and therefore load the function address into a register before performing a (otherwise direct) call. This is the default. ! '-mshort-calls' ! If not otherwise specified by an attribute, assume all direct calls ! are in the range of the 'b' / 'bl' instructions, so use these ! instructions for direct calls. The default is '-mlong-calls'. ! '-msmall16' Assume addresses can be loaded as 16-bit unsigned values. This ! does not apply to function addresses for which '-mlong-calls' semantics are in effect. ! '-mfp-mode=MODE' Set the prevailing mode of the floating-point unit. This ! determines the floating-point mode that is provided and expected at ! function call and return time. Making this mode match the mode you ! predominantly need at function start can make your programs smaller ! and faster by avoiding unnecessary mode switches. MODE can be set to one the following values: ! 'caller' Any mode at function entry is valid, and retained or restored when the function returns, and when it calls other functions. This mode is useful for compiling libraries or other ! compilation units you might want to incorporate into different ! programs with different prevailing FPU modes, and the ! convenience of being able to use a single object file outweighs the size and speed overhead for any extra mode switching that might be needed, compared with what would be needed with a more specific choice of prevailing FPU mode. ! 'truncate' This is the mode used for floating-point calculations with truncating (i.e. round towards zero) rounding mode. That includes conversion from floating point to integer. ! 'round-nearest' This is the mode used for floating-point calculations with round-to-nearest-or-even rounding mode. ! 'int' This is the mode used to perform integer calculations in the ! FPU, e.g. integer multiply, or integer multiply-and-accumulate. ! The default is '-mfp-mode=caller' ! '-mnosplit-lohi' ! '-mno-postinc' ! '-mno-postmodify' Code generation tweaks that disable, respectively, splitting of 32-bit loads, generation of post-increment addresses, and generation of post-modify addresses. The defaults are ! 'msplit-lohi', '-mpost-inc', and '-mpost-modify'. ! '-mnovect-double' Change the preferred SIMD mode to SImode. The default is ! '-mvect-double', which uses DImode as preferred SIMD mode. ! '-max-vect-align=NUM' The maximum alignment for SIMD vector mode types. NUM may be 4 or ! 8. The default is 8. Note that this is an ABI change, even though ! many library function interfaces are unaffected if they don't use ! SIMD vector modes in places that affect size and/or alignment of ! relevant types. ! '-msplit-vecmove-early' ! Split vector moves into single word moves before reload. In theory ! this can give better register allocation, but so far the reverse ! seems to be generally the case. ! '-m1reg-REG' Specify a register to hold the constant -1, which makes loading small negative constants and certain bitmasks faster. Allowable ! values for REG are 'r43' and 'r63', which specify use of that ! register as a fixed register, and 'none', which means that no ! register is used for this purpose. The default is '-m1reg-none'.  File: gcc.info, Node: ARC Options, Next: ARM Options, Prev: Adapteva Epiphany Options, Up: Submodel Options --- 12736,12831 ---- offset would give you better code, but to actually use a different stack offset to build working programs, it is recommended to configure the toolchain with the appropriate ! `--with-stack-offset=NUM' option. ! `-mno-round-nearest' Make the scheduler assume that the rounding mode has been set to ! truncating. The default is `-mround-nearest'. ! `-mlong-calls' If not otherwise specified by an attribute, assume all calls might ! be beyond the offset range of the `b' / `bl' instructions, and therefore load the function address into a register before performing a (otherwise direct) call. This is the default. ! `-mshort-calls' ! If not otherwise specified by an attribute, assume all direct ! calls are in the range of the `b' / `bl' instructions, so use ! these instructions for direct calls. The default is ! `-mlong-calls'. ! `-msmall16' Assume addresses can be loaded as 16-bit unsigned values. This ! does not apply to function addresses for which `-mlong-calls' semantics are in effect. ! `-mfp-mode=MODE' Set the prevailing mode of the floating-point unit. This ! determines the floating-point mode that is provided and expected ! at function call and return time. Making this mode match the mode ! you predominantly need at function start can make your programs ! smaller and faster by avoiding unnecessary mode switches. MODE can be set to one the following values: ! `caller' Any mode at function entry is valid, and retained or restored when the function returns, and when it calls other functions. This mode is useful for compiling libraries or other ! compilation units you might want to incorporate into ! different programs with different prevailing FPU modes, and ! the convenience of being able to use a single object file outweighs the size and speed overhead for any extra mode switching that might be needed, compared with what would be needed with a more specific choice of prevailing FPU mode. ! `truncate' This is the mode used for floating-point calculations with truncating (i.e. round towards zero) rounding mode. That includes conversion from floating point to integer. ! `round-nearest' This is the mode used for floating-point calculations with round-to-nearest-or-even rounding mode. ! `int' This is the mode used to perform integer calculations in the ! FPU, e.g. integer multiply, or integer multiply-and-accumulate. ! The default is `-mfp-mode=caller' ! `-mnosplit-lohi' ! `-mno-postinc' ! `-mno-postmodify' Code generation tweaks that disable, respectively, splitting of 32-bit loads, generation of post-increment addresses, and generation of post-modify addresses. The defaults are ! `msplit-lohi', `-mpost-inc', and `-mpost-modify'. ! `-mnovect-double' Change the preferred SIMD mode to SImode. The default is ! `-mvect-double', which uses DImode as preferred SIMD mode. ! `-max-vect-align=NUM' The maximum alignment for SIMD vector mode types. NUM may be 4 or ! 8. The default is 8. Note that this is an ABI change, even ! though many library function interfaces are unaffected if they ! don't use SIMD vector modes in places that affect size and/or ! alignment of relevant types. ! `-msplit-vecmove-early' ! Split vector moves into single word moves before reload. In ! theory this can give better register allocation, but so far the ! reverse seems to be generally the case. ! `-m1reg-REG' Specify a register to hold the constant -1, which makes loading small negative constants and certain bitmasks faster. Allowable ! values for REG are `r43' and `r63', which specify use of that ! register as a fixed register, and `none', which means that no ! register is used for this purpose. The default is `-m1reg-none'. !  File: gcc.info, Node: ARC Options, Next: ARM Options, Prev: Adapteva Epiphany Options, Up: Submodel Options *************** File: gcc.info, Node: ARC Options, Nex *** 12735,13112 **** 3.18.3 ARC Options ------------------ ! The following options control the architecture variant for which code is ! being compiled: ! '-mbarrel-shifter' Generate instructions supported by barrel shifter. This is the ! default unless '-mcpu=ARC601' or '-mcpu=ARCEM' is in effect. ! '-mcpu=CPU' Set architecture type, register usage, and instruction scheduling parameters for CPU. There are also shortcut alias options available for backward compatibility and convenience. Supported values for CPU are ! 'ARC600' ! 'arc600' ! Compile for ARC600. Aliases: '-mA6', '-mARC600'. ! 'ARC601' ! 'arc601' ! Compile for ARC601. Alias: '-mARC601'. ! 'ARC700' ! 'arc700' ! Compile for ARC700. Aliases: '-mA7', '-mARC700'. This is the ! default when configured with '--with-cpu=arc700'. ! 'ARCEM' ! 'arcem' Compile for ARC EM. ! 'ARCHS' ! 'archs' Compile for ARC HS. ! '-mdpfp' ! '-mdpfp-compact' FPX: Generate Double Precision FPX instructions, tuned for the compact implementation. ! '-mdpfp-fast' FPX: Generate Double Precision FPX instructions, tuned for the fast implementation. ! '-mno-dpfp-lrsr' Disable LR and SR instructions from using FPX extension aux registers. ! '-mea' ! Generate Extended arithmetic instructions. Currently only 'divaw', ! 'adds', 'subs', and 'sat16' are supported. This is always enabled ! for '-mcpu=ARC700'. ! '-mno-mpy' Do not generate mpy instructions for ARC700. ! '-mmul32x16' Generate 32x16 bit multiply and mac instructions. ! '-mmul64' Generate mul64 and mulu64 instructions. Only valid for ! '-mcpu=ARC600'. ! '-mnorm' ! Generate norm instruction. This is the default if '-mcpu=ARC700' is in effect. ! '-mspfp' ! '-mspfp-compact' FPX: Generate Single Precision FPX instructions, tuned for the compact implementation. ! '-mspfp-fast' FPX: Generate Single Precision FPX instructions, tuned for the fast implementation. ! '-msimd' Enable generation of ARC SIMD instructions via target-specific ! builtins. Only valid for '-mcpu=ARC700'. ! '-msoft-float' This option ignored; it is provided for compatibility purposes ! only. Software floating point code is emitted by default, and this ! default can overridden by FPX options; 'mspfp', 'mspfp-compact', or ! 'mspfp-fast' for single precision, and 'mdpfp', 'mdpfp-compact', or ! 'mdpfp-fast' for double precision. ! '-mswap' Generate swap instructions. ! '-matomic' This enables Locked Load/Store Conditional extension to implement atomic memopry built-in functions. Not available for ARC 6xx or ARC EM cores. ! '-mdiv-rem' Enable DIV/REM instructions for ARCv2 cores. ! '-mcode-density' Enable code density instructions for ARC EM, default on for ARC HS. ! '-mll64' Enable double load/store operations for ARC HS cores. ! '-mmpy-option=MULTO' ! Compile ARCv2 code with a multiplier design option. 'wlh1' is the default value. The recognized values for MULTO are: ! '0' No multiplier available. ! '1' The multiply option is set to w: 16x16 multiplier, fully pipelined. The following instructions are enabled: MPYW, and MPYUW. ! '2' The multiply option is set to wlh1: 32x32 multiplier, fully pipelined (1 stage). The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! '3' The multiply option is set to wlh2: 32x32 multiplier, fully pipelined (2 stages). The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! '4' The multiply option is set to wlh3: Two 16x16 multiplier, blocking, sequential. The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! '5' The multiply option is set to wlh4: One 16x16 multiplier, blocking, sequential. The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! '6' The multiply option is set to wlh5: One 32x4 multiplier, blocking, sequential. The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. This option is only available for ARCv2 cores. ! '-mfpu=FPU' Enables specific floating-point hardware extension for ARCv2 core. Supported values for FPU are: ! 'fpus' Enables support for single precision floating point hardware extensions. ! 'fpud' Enables support for double precision floating point hardware extensions. The single precision floating point extension is also enabled. Not available for ARC EM. ! 'fpuda' Enables support for double precision floating point hardware extensions using double precision assist instructions. The single precision floating point extension is also enabled. This option is only available for ARC EM. ! 'fpuda_div' Enables support for double precision floating point hardware extensions using double precision assist instructions, and simple precision square-root and divide hardware extensions. ! The single precision floating point extension is also enabled. ! This option is only available for ARC EM. ! 'fpuda_fma' Enables support for double precision floating point hardware extensions using double precision assist instructions, and simple precision fused multiple and add hardware extension. ! The single precision floating point extension is also enabled. ! This option is only available for ARC EM. ! 'fpuda_all' Enables support for double precision floating point hardware ! extensions using double precision assist instructions, and all ! simple precision hardware extensions. The single precision ! floating point extension is also enabled. This option is only ! available for ARC EM. ! 'fpus_div' Enables support for single precision floating point, and single precision square-root and divide hardware extensions. ! 'fpud_div' Enables support for double precision floating point, and double precision square-root and divide hardware extensions. ! This option includes option 'fpus_div'. Not available for ARC EM. ! 'fpus_fma' Enables support for single precision floating point, and single precision fused multiple and add hardware extensions. ! 'fpud_fma' Enables support for double precision floating point, and double precision fused multiple and add hardware extensions. ! This option includes option 'fpus_fma'. Not available for ARC ! EM. ! 'fpus_all' Enables support for all single precision floating point hardware extensions. ! 'fpud_all' Enables support for all single and double precision floating point hardware extensions. Not available for ARC EM. The following options are passed through to the assembler, and also define preprocessor macro symbols. ! '-mdsp-packa' Passed down to the assembler to enable the DSP Pack A extensions. ! Also sets the preprocessor symbol '__Xdsp_packa'. ! '-mdvbf' Passed down to the assembler to enable the dual viterbi butterfly ! extension. Also sets the preprocessor symbol '__Xdvbf'. ! '-mlock' Passed down to the assembler to enable the Locked Load/Store Conditional extension. Also sets the preprocessor symbol ! '__Xlock'. ! '-mmac-d16' Passed down to the assembler. Also sets the preprocessor symbol ! '__Xxmac_d16'. ! '-mmac-24' Passed down to the assembler. Also sets the preprocessor symbol ! '__Xxmac_24'. ! '-mrtsc' Passed down to the assembler to enable the 64-bit Time-Stamp Counter extension instruction. Also sets the preprocessor symbol ! '__Xrtsc'. ! '-mswape' Passed down to the assembler to enable the swap byte ordering extension instruction. Also sets the preprocessor symbol ! '__Xswape'. ! '-mtelephony' Passed down to the assembler to enable dual and single operand instructions for telephony. Also sets the preprocessor symbol ! '__Xtelephony'. ! '-mxy' Passed down to the assembler to enable the XY Memory extension. ! Also sets the preprocessor symbol '__Xxy'. The following options control how the assembly code is annotated: ! '-misize' Annotate assembler instructions with estimated addresses. ! '-mannotate-align' Explain what alignment considerations lead to the decision to make an instruction short or long. The following options are passed through to the linker: ! '-marclinux' ! Passed through to the linker, to specify use of the 'arclinux' emulation. This option is enabled by default in tool chains built ! for 'arc-linux-uclibc' and 'arceb-linux-uclibc' targets when profiling is not requested. ! '-marclinux_prof' ! Passed through to the linker, to specify use of the 'arclinux_prof' ! emulation. This option is enabled by default in tool chains built ! for 'arc-linux-uclibc' and 'arceb-linux-uclibc' targets when ! profiling is requested. The following options control the semantics of generated code: ! '-mlong-calls' Generate call insns as register indirect calls, thus providing access to the full 32-bit address range. ! '-mmedium-calls' Don't use less than 25 bit addressing range for calls, which is the offset available for an unconditional branch-and-link instruction. ! Conditional execution of function calls is suppressed, to allow use ! of the 25-bit range, rather than the 21-bit range with conditional ! branch-and-link. This is the default for tool chains built for ! 'arc-linux-uclibc' and 'arceb-linux-uclibc' targets. ! '-mno-sdata' Do not generate sdata references. This is the default for tool ! chains built for 'arc-linux-uclibc' and 'arceb-linux-uclibc' targets. ! '-mucb-mcount' ! Instrument with mcount calls as used in UCB code. I.e. do the counting in the callee, not the caller. By default ARC instrumentation counts in the caller. ! '-mvolatile-cache' Use ordinarily cached memory accesses for volatile references. This is the default. ! '-mno-volatile-cache' Enable cache bypass for volatile references. The following options fine tune code generation: ! '-malign-call' Do alignment optimizations for call instructions. ! '-mauto-modify-reg' Enable the use of pre/post modify with register displacement. ! '-mbbit-peephole' Enable bbit peephole2. ! '-mno-brcc' ! This option disables a target-specific pass in 'arc_reorg' to ! generate 'BRcc' instructions. It has no effect on 'BRcc' generation driven by the combiner pass. ! '-mcase-vector-pcrel' Use pc-relative switch case tables - this enables case table ! shortening. This is the default for '-Os'. ! '-mcompact-casesi' ! Enable compact casesi pattern. This is the default for '-Os'. ! '-mno-cond-exec' Disable ARCompact specific pass to generate conditional execution instructions. Due to delay slot scheduling and interactions between operand numbers, literal sizes, instruction lengths, and the support for conditional execution, the target-independent pass ! to generate conditional execution is often lacking, so the ARC port ! has kept a special pass around that tries to find more conditional ! execution generating opportunities after register allocation, ! branch shortening, and delay slot scheduling have been done. This ! pass generally, but not always, improves performance and code size, ! at the cost of extra compilation time, which is why there is an ! option to switch it off. If you have a problem with call ! instructions exceeding their allowable offset range because they ! are conditionalized, you should consider using '-mmedium-calls' ! instead. ! '-mearly-cbranchsi' Enable pre-reload use of the cbranchsi pattern. ! '-mexpand-adddi' ! Expand 'adddi3' and 'subdi3' at rtl generation time into 'add.f', ! 'adc' etc. ! '-mindexed-loads' Enable the use of indexed loads. This can be problematic because some optimizers then assume that indexed stores exist, which is not the case. Enable Local Register Allocation. This is still experimental for ARC, so by default the compiler uses standard reload (i.e. ! '-mno-lra'). ! '-mlra-priority-none' Don't indicate any priority for target registers. ! '-mlra-priority-compact' Indicate target register priority for r0..r3 / r12..r15. ! '-mlra-priority-noncompact' Reduce target register priority for r0..r3 / r12..r15. ! '-mno-millicode' ! When optimizing for size (using '-Os'), prologues and epilogues that have to save or restore a large number of registers are often shortened by using call to a special function in libgcc; this is referred to as a _millicode_ call. As these calls can pose --- 12833,13222 ---- 3.18.3 ARC Options ------------------ ! The following options control the architecture variant for which code ! is being compiled: ! `-mbarrel-shifter' Generate instructions supported by barrel shifter. This is the ! default unless `-mcpu=ARC601' or `-mcpu=ARCEM' is in effect. ! `-mcpu=CPU' Set architecture type, register usage, and instruction scheduling parameters for CPU. There are also shortcut alias options available for backward compatibility and convenience. Supported values for CPU are ! `ARC600' ! `arc600' ! Compile for ARC600. Aliases: `-mA6', `-mARC600'. ! `ARC601' ! `arc601' ! Compile for ARC601. Alias: `-mARC601'. ! ! `ARC700' ! ! `arc700' ! Compile for ARC700. Aliases: `-mA7', `-mARC700'. This is ! the default when configured with `--with-cpu=arc700'. ! ! `ARCEM' ! ! `arcem' Compile for ARC EM. ! `ARCHS' ! ! `archs' Compile for ARC HS. ! `-mdpfp' ! `-mdpfp-compact' FPX: Generate Double Precision FPX instructions, tuned for the compact implementation. ! `-mdpfp-fast' FPX: Generate Double Precision FPX instructions, tuned for the fast implementation. ! `-mno-dpfp-lrsr' Disable LR and SR instructions from using FPX extension aux registers. ! `-mea' ! Generate Extended arithmetic instructions. Currently only ! `divaw', `adds', `subs', and `sat16' are supported. This is ! always enabled for `-mcpu=ARC700'. ! `-mno-mpy' Do not generate mpy instructions for ARC700. ! `-mmul32x16' Generate 32x16 bit multiply and mac instructions. ! `-mmul64' Generate mul64 and mulu64 instructions. Only valid for ! `-mcpu=ARC600'. ! `-mnorm' ! Generate norm instruction. This is the default if `-mcpu=ARC700' is in effect. ! `-mspfp' ! `-mspfp-compact' FPX: Generate Single Precision FPX instructions, tuned for the compact implementation. ! `-mspfp-fast' FPX: Generate Single Precision FPX instructions, tuned for the fast implementation. ! `-msimd' Enable generation of ARC SIMD instructions via target-specific ! builtins. Only valid for `-mcpu=ARC700'. ! `-msoft-float' This option ignored; it is provided for compatibility purposes ! only. Software floating point code is emitted by default, and ! this default can overridden by FPX options; `mspfp', ! `mspfp-compact', or `mspfp-fast' for single precision, and `mdpfp', ! `mdpfp-compact', or `mdpfp-fast' for double precision. ! `-mswap' Generate swap instructions. ! `-matomic' This enables Locked Load/Store Conditional extension to implement atomic memopry built-in functions. Not available for ARC 6xx or ARC EM cores. ! `-mdiv-rem' Enable DIV/REM instructions for ARCv2 cores. ! `-mcode-density' Enable code density instructions for ARC EM, default on for ARC HS. ! `-mll64' Enable double load/store operations for ARC HS cores. ! `-mmpy-option=MULTO' ! Compile ARCv2 code with a multiplier design option. `wlh1' is the default value. The recognized values for MULTO are: ! `0' No multiplier available. ! `1' The multiply option is set to w: 16x16 multiplier, fully pipelined. The following instructions are enabled: MPYW, and MPYUW. ! `2' The multiply option is set to wlh1: 32x32 multiplier, fully pipelined (1 stage). The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! `3' The multiply option is set to wlh2: 32x32 multiplier, fully pipelined (2 stages). The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! `4' The multiply option is set to wlh3: Two 16x16 multiplier, blocking, sequential. The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! `5' The multiply option is set to wlh4: One 16x16 multiplier, blocking, sequential. The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. ! `6' The multiply option is set to wlh5: One 32x4 multiplier, blocking, sequential. The following instructions are additionally enabled: MPY, MPYU, MPYM, MPYMU, and MPY_S. + This option is only available for ARCv2 cores. ! `-mfpu=FPU' Enables specific floating-point hardware extension for ARCv2 core. Supported values for FPU are: ! `fpus' Enables support for single precision floating point hardware extensions. ! `fpud' Enables support for double precision floating point hardware extensions. The single precision floating point extension is also enabled. Not available for ARC EM. ! `fpuda' Enables support for double precision floating point hardware extensions using double precision assist instructions. The single precision floating point extension is also enabled. This option is only available for ARC EM. ! `fpuda_div' Enables support for double precision floating point hardware extensions using double precision assist instructions, and simple precision square-root and divide hardware extensions. ! The single precision floating point extension is also ! enabled. This option is only available for ARC EM. ! `fpuda_fma' Enables support for double precision floating point hardware extensions using double precision assist instructions, and simple precision fused multiple and add hardware extension. ! The single precision floating point extension is also ! enabled. This option is only available for ARC EM. ! `fpuda_all' Enables support for double precision floating point hardware ! extensions using double precision assist instructions, and ! all simple precision hardware extensions. The single ! precision floating point extension is also enabled. This ! option is only available for ARC EM. ! `fpus_div' Enables support for single precision floating point, and single precision square-root and divide hardware extensions. ! `fpud_div' Enables support for double precision floating point, and double precision square-root and divide hardware extensions. ! This option includes option `fpus_div'. Not available for ARC EM. ! `fpus_fma' Enables support for single precision floating point, and single precision fused multiple and add hardware extensions. ! `fpud_fma' Enables support for double precision floating point, and double precision fused multiple and add hardware extensions. ! This option includes option `fpus_fma'. Not available for ! ARC EM. ! `fpus_all' Enables support for all single precision floating point hardware extensions. ! `fpud_all' Enables support for all single and double precision floating point hardware extensions. Not available for ARC EM. + + The following options are passed through to the assembler, and also define preprocessor macro symbols. ! `-mdsp-packa' Passed down to the assembler to enable the DSP Pack A extensions. ! Also sets the preprocessor symbol `__Xdsp_packa'. ! `-mdvbf' Passed down to the assembler to enable the dual viterbi butterfly ! extension. Also sets the preprocessor symbol `__Xdvbf'. ! `-mlock' Passed down to the assembler to enable the Locked Load/Store Conditional extension. Also sets the preprocessor symbol ! `__Xlock'. ! `-mmac-d16' Passed down to the assembler. Also sets the preprocessor symbol ! `__Xxmac_d16'. ! `-mmac-24' Passed down to the assembler. Also sets the preprocessor symbol ! `__Xxmac_24'. ! `-mrtsc' Passed down to the assembler to enable the 64-bit Time-Stamp Counter extension instruction. Also sets the preprocessor symbol ! `__Xrtsc'. ! `-mswape' Passed down to the assembler to enable the swap byte ordering extension instruction. Also sets the preprocessor symbol ! `__Xswape'. ! `-mtelephony' Passed down to the assembler to enable dual and single operand instructions for telephony. Also sets the preprocessor symbol ! `__Xtelephony'. ! `-mxy' Passed down to the assembler to enable the XY Memory extension. ! Also sets the preprocessor symbol `__Xxy'. ! The following options control how the assembly code is annotated: ! `-misize' Annotate assembler instructions with estimated addresses. ! `-mannotate-align' Explain what alignment considerations lead to the decision to make an instruction short or long. + The following options are passed through to the linker: ! `-marclinux' ! Passed through to the linker, to specify use of the `arclinux' emulation. This option is enabled by default in tool chains built ! for `arc-linux-uclibc' and `arceb-linux-uclibc' targets when profiling is not requested. ! `-marclinux_prof' ! Passed through to the linker, to specify use of the ! `arclinux_prof' emulation. This option is enabled by default in ! tool chains built for `arc-linux-uclibc' and `arceb-linux-uclibc' ! targets when profiling is requested. ! The following options control the semantics of generated code: ! `-mlong-calls' Generate call insns as register indirect calls, thus providing access to the full 32-bit address range. ! `-mmedium-calls' Don't use less than 25 bit addressing range for calls, which is the offset available for an unconditional branch-and-link instruction. ! Conditional execution of function calls is suppressed, to allow ! use of the 25-bit range, rather than the 21-bit range with ! conditional branch-and-link. This is the default for tool chains ! built for `arc-linux-uclibc' and `arceb-linux-uclibc' targets. ! `-mno-sdata' Do not generate sdata references. This is the default for tool ! chains built for `arc-linux-uclibc' and `arceb-linux-uclibc' targets. ! `-mucb-mcount' ! Instrument with mcount calls as used in UCB code. I.e. do the counting in the callee, not the caller. By default ARC instrumentation counts in the caller. ! `-mvolatile-cache' Use ordinarily cached memory accesses for volatile references. This is the default. ! `-mno-volatile-cache' Enable cache bypass for volatile references. + The following options fine tune code generation: ! `-malign-call' Do alignment optimizations for call instructions. ! `-mauto-modify-reg' Enable the use of pre/post modify with register displacement. ! `-mbbit-peephole' Enable bbit peephole2. ! `-mno-brcc' ! This option disables a target-specific pass in `arc_reorg' to ! generate `BRcc' instructions. It has no effect on `BRcc' generation driven by the combiner pass. ! `-mcase-vector-pcrel' Use pc-relative switch case tables - this enables case table ! shortening. This is the default for `-Os'. ! `-mcompact-casesi' ! Enable compact casesi pattern. This is the default for `-Os'. ! `-mno-cond-exec' Disable ARCompact specific pass to generate conditional execution instructions. Due to delay slot scheduling and interactions between operand numbers, literal sizes, instruction lengths, and the support for conditional execution, the target-independent pass ! to generate conditional execution is often lacking, so the ARC ! port has kept a special pass around that tries to find more ! conditional execution generating opportunities after register ! allocation, branch shortening, and delay slot scheduling have been ! done. This pass generally, but not always, improves performance ! and code size, at the cost of extra compilation time, which is why ! there is an option to switch it off. If you have a problem with ! call instructions exceeding their allowable offset range because ! they are conditionalized, you should consider using ! `-mmedium-calls' instead. ! `-mearly-cbranchsi' Enable pre-reload use of the cbranchsi pattern. ! `-mexpand-adddi' ! Expand `adddi3' and `subdi3' at rtl generation time into `add.f', ! `adc' etc. ! `-mindexed-loads' Enable the use of indexed loads. This can be problematic because some optimizers then assume that indexed stores exist, which is not the case. Enable Local Register Allocation. This is still experimental for ARC, so by default the compiler uses standard reload (i.e. ! `-mno-lra'). ! `-mlra-priority-none' Don't indicate any priority for target registers. ! `-mlra-priority-compact' Indicate target register priority for r0..r3 / r12..r15. ! `-mlra-priority-noncompact' Reduce target register priority for r0..r3 / r12..r15. ! `-mno-millicode' ! When optimizing for size (using `-Os'), prologues and epilogues that have to save or restore a large number of registers are often shortened by using call to a special function in libgcc; this is referred to as a _millicode_ call. As these calls can pose *************** define preprocessor macro symbols. *** 13114,13247 **** nonstandard way, this option is provided to turn off millicode call generation. ! '-mmixed-code' Tweak register allocation to help 16-bit instruction generation. ! This generally has the effect of decreasing the average instruction ! size while increasing the instruction count. ! '-mq-class' Enable 'q' instruction alternatives. This is the default for ! '-Os'. ! '-mRcq' ! Enable Rcq constraint handling - most short code generation depends ! on this. This is the default. ! '-mRcw' Enable Rcw constraint handling - ccfsm condexec mostly depends on this. This is the default. ! '-msize-level=LEVEL' ! Fine-tune size optimization with regards to instruction lengths and ! alignment. The recognized values for LEVEL are: ! '0' No size optimization. This level is deprecated and treated ! like '1'. ! '1' Short instructions are used opportunistically. ! '2' ! In addition, alignment of loops and of code after barriers are ! dropped. ! '3' In addition, optional data alignment is dropped, and the ! option 'Os' is enabled. - This defaults to '3' when '-Os' is in effect. Otherwise, the - behavior when this is not set is equivalent to level '1'. ! '-mtune=CPU' Set instruction scheduling parameters for CPU, overriding any ! implied by '-mcpu='. Supported values for CPU are ! 'ARC600' Tune for ARC600 cpu. ! 'ARC601' Tune for ARC601 cpu. ! 'ARC700' Tune for ARC700 cpu with standard multiplier block. ! 'ARC700-xmac' Tune for ARC700 cpu with XMAC block. ! 'ARC725D' Tune for ARC725D cpu. ! 'ARC750D' Tune for ARC750D cpu. ! '-mmultcost=NUM' ! Cost to assume for a multiply instruction, with '4' being equal to a normal instruction. ! '-munalign-prob-threshold=PROBABILITY' ! Set probability threshold for unaligning branches. When tuning for ! 'ARC700' and optimizing for speed, branches without filled delay ! slot are preferably emitted unaligned and long, unless profiling ! indicates that the probability for the branch to be taken is below ! PROBABILITY. *Note Cross-profiling::. The default is (REG_BR_PROB_BASE/2), i.e. 5000. The following options are maintained for backward compatibility, but are now deprecated and will be removed in a future release: ! '-margonaut' Obsolete FPX. ! '-mbig-endian' ! '-EB' Compile code for big endian targets. Use of these options is now deprecated. Users wanting big-endian code, should use the ! 'arceb-elf32' and 'arceb-linux-uclibc' targets when building the tool chain, for which big-endian is the default. ! '-mlittle-endian' ! '-EL' Compile code for little endian targets. Use of these options is now deprecated. Users wanting little-endian code should use the ! 'arc-elf32' and 'arc-linux-uclibc' targets when building the tool chain, for which little-endian is the default. ! '-mbarrel_shifter' ! Replaced by '-mbarrel-shifter'. ! '-mdpfp_compact' ! Replaced by '-mdpfp-compact'. ! '-mdpfp_fast' ! Replaced by '-mdpfp-fast'. ! '-mdsp_packa' ! Replaced by '-mdsp-packa'. ! '-mEA' ! Replaced by '-mea'. ! '-mmac_24' ! Replaced by '-mmac-24'. ! '-mmac_d16' ! Replaced by '-mmac-d16'. ! '-mspfp_compact' ! Replaced by '-mspfp-compact'. ! '-mspfp_fast' ! Replaced by '-mspfp-fast'. ! '-mtune=CPU' ! Values 'arc600', 'arc601', 'arc700' and 'arc700-xmac' for CPU are ! replaced by 'ARC600', 'ARC601', 'ARC700' and 'ARC700-xmac' respectively ! '-multcost=NUM' ! Replaced by '-mmultcost'.  File: gcc.info, Node: ARM Options, Next: AVR Options, Prev: ARC Options, Up: Submodel Options --- 13224,13361 ---- nonstandard way, this option is provided to turn off millicode call generation. ! `-mmixed-code' Tweak register allocation to help 16-bit instruction generation. ! This generally has the effect of decreasing the average ! instruction size while increasing the instruction count. ! `-mq-class' Enable 'q' instruction alternatives. This is the default for ! `-Os'. ! `-mRcq' ! Enable Rcq constraint handling - most short code generation ! depends on this. This is the default. ! `-mRcw' Enable Rcw constraint handling - ccfsm condexec mostly depends on this. This is the default. ! `-msize-level=LEVEL' ! Fine-tune size optimization with regards to instruction lengths ! and alignment. The recognized values for LEVEL are: ! `0' No size optimization. This level is deprecated and treated ! like `1'. ! `1' Short instructions are used opportunistically. ! `2' ! In addition, alignment of loops and of code after barriers ! are dropped. ! `3' In addition, optional data alignment is dropped, and the ! option `Os' is enabled. ! This defaults to `3' when `-Os' is in effect. Otherwise, the ! behavior when this is not set is equivalent to level `1'. ! ! `-mtune=CPU' Set instruction scheduling parameters for CPU, overriding any ! implied by `-mcpu='. Supported values for CPU are ! `ARC600' Tune for ARC600 cpu. ! `ARC601' Tune for ARC601 cpu. ! `ARC700' Tune for ARC700 cpu with standard multiplier block. ! `ARC700-xmac' Tune for ARC700 cpu with XMAC block. ! `ARC725D' Tune for ARC725D cpu. ! `ARC750D' Tune for ARC750D cpu. ! ! `-mmultcost=NUM' ! Cost to assume for a multiply instruction, with `4' being equal to a normal instruction. ! `-munalign-prob-threshold=PROBABILITY' ! Set probability threshold for unaligning branches. When tuning ! for `ARC700' and optimizing for speed, branches without filled ! delay slot are preferably emitted unaligned and long, unless ! profiling indicates that the probability for the branch to be taken ! is below PROBABILITY. *Note Cross-profiling::. The default is (REG_BR_PROB_BASE/2), i.e. 5000. + The following options are maintained for backward compatibility, but are now deprecated and will be removed in a future release: ! `-margonaut' Obsolete FPX. ! `-mbig-endian' ! `-EB' Compile code for big endian targets. Use of these options is now deprecated. Users wanting big-endian code, should use the ! `arceb-elf32' and `arceb-linux-uclibc' targets when building the tool chain, for which big-endian is the default. ! `-mlittle-endian' ! `-EL' Compile code for little endian targets. Use of these options is now deprecated. Users wanting little-endian code should use the ! `arc-elf32' and `arc-linux-uclibc' targets when building the tool chain, for which little-endian is the default. ! `-mbarrel_shifter' ! Replaced by `-mbarrel-shifter'. ! `-mdpfp_compact' ! Replaced by `-mdpfp-compact'. ! `-mdpfp_fast' ! Replaced by `-mdpfp-fast'. ! `-mdsp_packa' ! Replaced by `-mdsp-packa'. ! `-mEA' ! Replaced by `-mea'. ! `-mmac_24' ! Replaced by `-mmac-24'. ! `-mmac_d16' ! Replaced by `-mmac-d16'. ! `-mspfp_compact' ! Replaced by `-mspfp-compact'. ! `-mspfp_fast' ! Replaced by `-mspfp-fast'. ! `-mtune=CPU' ! Values `arc600', `arc601', `arc700' and `arc700-xmac' for CPU are ! replaced by `ARC600', `ARC601', `ARC700' and `ARC700-xmac' respectively ! `-multcost=NUM' ! Replaced by `-mmultcost'. !  File: gcc.info, Node: ARM Options, Next: AVR Options, Prev: ARC Options, Up: Submodel Options *************** File: gcc.info, Node: ARM Options, Nex *** 13249,13296 **** 3.18.4 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 ! '-fomit-frame-pointer' with this option causes the stack frames not ! to be generated for leaf functions. The default is ! '-mno-apcs-frame'. This option is deprecated. ! '-mapcs' ! This is a synonym for '-mapcs-frame' and is deprecated. ! '-mthumb-interwork' Generate code that supports calling between the ARM and Thumb instruction sets. Without this option, on pre-v5 architectures, the two instruction sets cannot be reliably used inside one ! program. The default is '-mno-thumb-interwork', since slightly ! larger code is generated when '-mthumb-interwork' is specified. In ! AAPCS configurations this option is meaningless. ! '-mno-sched-prolog' ! Prevent the reordering of instructions in the function prologue, or ! the merging of those instruction with the instructions in the function's body. This means that all functions start with a ! recognizable set of instructions (or in fact one of a choice from a ! small set of different function prologues), and this information can be used to locate the start of functions inside an executable ! piece of code. The default is '-msched-prolog'. ! '-mfloat-abi=NAME' ! Specifies which floating-point ABI to use. Permissible values are: ! 'soft', 'softfp' and 'hard'. ! Specifying 'soft' causes GCC to generate output containing library ! calls for floating-point operations. 'softfp' allows the generation of code using hardware floating-point instructions, but ! still uses the soft-float calling conventions. 'hard' allows generation of floating-point instructions and uses FPU-specific calling conventions. --- 13363,13410 ---- 3.18.4 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 ! `-fomit-frame-pointer' with this option causes the stack frames ! not to be generated for leaf functions. The default is ! `-mno-apcs-frame'. This option is deprecated. ! `-mapcs' ! This is a synonym for `-mapcs-frame' and is deprecated. ! `-mthumb-interwork' Generate code that supports calling between the ARM and Thumb instruction sets. Without this option, on pre-v5 architectures, the two instruction sets cannot be reliably used inside one ! program. The default is `-mno-thumb-interwork', since slightly ! larger code is generated when `-mthumb-interwork' is specified. ! In AAPCS configurations this option is meaningless. ! `-mno-sched-prolog' ! Prevent the reordering of instructions in the function prologue, ! or the merging of those instruction with the instructions in the function's body. This means that all functions start with a ! recognizable set of instructions (or in fact one of a choice from ! a small set of different function prologues), and this information can be used to locate the start of functions inside an executable ! piece of code. The default is `-msched-prolog'. ! `-mfloat-abi=NAME' ! Specifies which floating-point ABI to use. Permissible values ! are: `soft', `softfp' and `hard'. ! Specifying `soft' causes GCC to generate output containing library ! calls for floating-point operations. `softfp' allows the generation of code using hardware floating-point instructions, but ! still uses the soft-float calling conventions. `hard' allows generation of floating-point instructions and uses FPU-specific calling conventions. *************** These '-m' options are defined for the A *** 13299,13494 **** you must compile your entire program with the same ABI, and link with a compatible set of libraries. ! '-mlittle-endian' Generate code for a processor running in little-endian mode. This is the default for all standard configurations. ! '-mbig-endian' Generate code for a processor running in big-endian mode; the default is to compile code for a little-endian processor. ! '-march=NAME' This specifies the name of the target ARM architecture. GCC uses this name to determine what kind of instructions it can emit when generating assembly code. This option can be used in conjunction ! with or instead of the '-mcpu=' option. Permissible names are: ! 'armv2', 'armv2a', 'armv3', 'armv3m', 'armv4', 'armv4t', 'armv5', ! 'armv5t', 'armv5e', 'armv5te', 'armv6', 'armv6j', 'armv6t2', ! 'armv6z', 'armv6kz', 'armv6-m', 'armv7', 'armv7-a', 'armv7-r', ! 'armv7-m', 'armv7e-m', 'armv7ve', 'armv8-a', 'armv8-a+crc', ! 'armv8.1-a', 'armv8.1-a+crc', 'iwmmxt', 'iwmmxt2', 'ep9312'. ! Architecture revisions older than 'armv4t' are deprecated. ! '-march=armv7ve' is the armv7-a architecture with virtualization extensions. ! '-march=armv8-a+crc' enables code generation for the ARMv8-A architecture together with the optional CRC32 extensions. ! '-march=native' causes the compiler to auto-detect the architecture of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect. ! '-mtune=NAME' This option specifies the name of the target ARM processor for which GCC should tune the performance of the code. For some ARM implementations better performance can be obtained by using this ! option. Permissible names are: 'arm2', 'arm250', 'arm3', 'arm6', ! 'arm60', 'arm600', 'arm610', 'arm620', 'arm7', 'arm7m', 'arm7d', ! 'arm7dm', 'arm7di', 'arm7dmi', 'arm70', 'arm700', 'arm700i', ! 'arm710', 'arm710c', 'arm7100', 'arm720', 'arm7500', 'arm7500fe', ! 'arm7tdmi', 'arm7tdmi-s', 'arm710t', 'arm720t', 'arm740t', ! 'strongarm', 'strongarm110', 'strongarm1100', 'strongarm1110', ! 'arm8', 'arm810', 'arm9', 'arm9e', 'arm920', 'arm920t', 'arm922t', ! 'arm946e-s', 'arm966e-s', 'arm968e-s', 'arm926ej-s', 'arm940t', ! 'arm9tdmi', 'arm10tdmi', 'arm1020t', 'arm1026ej-s', 'arm10e', ! 'arm1020e', 'arm1022e', 'arm1136j-s', 'arm1136jf-s', 'mpcore', ! 'mpcorenovfp', 'arm1156t2-s', 'arm1156t2f-s', 'arm1176jz-s', ! 'arm1176jzf-s', 'generic-armv7-a', 'cortex-a5', 'cortex-a7', ! 'cortex-a8', 'cortex-a9', 'cortex-a12', 'cortex-a15', 'cortex-a17', ! 'cortex-a32', 'cortex-a35', 'cortex-a53', 'cortex-a57', ! 'cortex-a72', 'cortex-r4', 'cortex-r4f', 'cortex-r5', 'cortex-r7', ! 'cortex-r8', 'cortex-m7', 'cortex-m4', 'cortex-m3', 'cortex-m1', ! 'cortex-m0', 'cortex-m0plus', 'cortex-m1.small-multiply', ! 'cortex-m0.small-multiply', 'cortex-m0plus.small-multiply', ! 'exynos-m1', 'qdf24xx', 'marvell-pj4', 'xscale', 'iwmmxt', ! 'iwmmxt2', 'ep9312', 'fa526', 'fa626', 'fa606te', 'fa626te', ! 'fmp626', 'fa726te', 'xgene1'. Additionally, this option can specify that GCC should tune the ! performance of the code for a big.LITTLE system. Permissible names ! are: 'cortex-a15.cortex-a7', 'cortex-a17.cortex-a7', ! 'cortex-a57.cortex-a53', 'cortex-a72.cortex-a53'. ! '-mtune=generic-ARCH' specifies that GCC should tune the performance for a blend of processors within architecture ARCH. The aim is to generate code that run well on the current most popular processors, balancing between optimizations that benefit some CPUs in the range, and avoiding performance pitfalls of other ! CPUs. The effects of this option may change in future GCC versions ! as CPU models come and go. ! '-mtune=native' causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect. ! '-mcpu=NAME' ! This specifies the name of the target ARM processor. GCC uses this ! name to derive the name of the target ARM architecture (as if ! specified by '-march') and the ARM processor type for which to tune ! for performance (as if specified by '-mtune'). Where this option ! is used in conjunction with '-march' or '-mtune', those options ! take precedence over the appropriate part of this option. Permissible names for this option are the same as those for ! '-mtune'. ! '-mcpu=generic-ARCH' is also permissible, and is equivalent to ! '-march=ARCH -mtune=generic-ARCH'. See '-mtune' for more information. ! '-mcpu=native' causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect. ! '-mfpu=NAME' ! This specifies what floating-point hardware (or hardware emulation) ! is available on the target. Permissible names are: 'vfp', 'vfpv3', ! 'vfpv3-fp16', 'vfpv3-d16', 'vfpv3-d16-fp16', 'vfpv3xd', ! 'vfpv3xd-fp16', 'neon', 'neon-fp16', 'vfpv4', 'vfpv4-d16', ! 'fpv4-sp-d16', 'neon-vfpv4', 'fpv5-d16', 'fpv5-sp-d16', 'fp-armv8', ! 'neon-fp-armv8' and 'crypto-neon-fp-armv8'. ! If '-msoft-float' is specified this specifies the format of floating-point values. If the selected floating-point hardware includes the NEON extension ! (e.g. '-mfpu'='neon'), note that floating-point operations are not generated by GCC's auto-vectorization pass unless ! '-funsafe-math-optimizations' is also specified. This is because NEON hardware does not fully implement the IEEE 754 standard for floating-point arithmetic (in particular denormal values are treated as zero), so the use of NEON instructions may lead to a loss of precision. You can also set the fpu name at function level by using the ! 'target("fpu=")' function attributes (*note ARM Function Attributes::) or pragmas (*note Function Specific Option Pragmas::). ! '-mfp16-format=NAME' ! Specify the format of the '__fp16' half-precision floating-point ! type. Permissible names are 'none', 'ieee', and 'alternative'; the ! default is 'none', in which case the '__fp16' type is not defined. ! *Note Half-Precision::, for more information. ! '-mstructure-size-boundary=N' The sizes of all structures and unions are rounded up to a multiple of the number of bits set by this option. Permissible values are 8, 32 and 64. The default value varies for different toolchains. ! For the COFF targeted toolchain the default value is 8. A value of ! 64 is only allowed if the underlying ABI supports it. ! Specifying a larger number can produce faster, more efficient code, ! but can also increase the size of the program. Different values ! are potentially incompatible. Code compiled with one value cannot ! necessarily expect to work with code or libraries compiled with ! another value, if they exchange information using structures or ! unions. ! '-mabort-on-noreturn' ! Generate a call to the function 'abort' at the end of a 'noreturn' function. It is executed if the function tries to return. ! '-mlong-calls' ! '-mno-long-calls' Tells the compiler to perform function calls by first loading the address of the function into a register and then performing a subroutine call on this register. This switch is needed if the ! target function lies outside of the 64-megabyte addressing range of ! the offset-based version of subroutine call instruction. Even if this switch is enabled, not all function calls are turned into long calls. The heuristic is that static functions, functions ! that have the 'short_call' attribute, functions that are inside the ! scope of a '#pragma no_long_calls' directive, and functions whose ! definitions have already been compiled within the current ! compilation unit are not turned into long calls. The exceptions to ! this rule are that weak function definitions, functions with the ! 'long_call' attribute or the 'section' attribute, and functions ! that are within the scope of a '#pragma long_calls' directive are ! always turned into long calls. This feature is not enabled by default. Specifying ! '-mno-long-calls' restores the default behavior, as does placing ! the function calls within the scope of a '#pragma long_calls_off' directive. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers. ! '-msingle-pic-base' Treat the register used for PIC addressing as read-only, rather than loading it in the prologue for each function. The runtime system is responsible for initializing this register with an appropriate value before execution begins. ! '-mpic-register=REG' Specify the register to be used for PIC addressing. For standard PIC base case, the default is any suitable register determined by ! compiler. For single PIC base case, the default is 'R9' if target is EABI based or stack-checking is enabled, otherwise the default ! is 'R10'. ! '-mpic-data-is-text-relative' ! Assume that each data segments are relative to text segment at load ! time. Therefore, it permits addressing data using PC-relative ! operations. This option is on by default for targets other than ! VxWorks RTP. ! '-mpoke-function-name' Write the name of each function into the text section, directly preceding the function prologue. The generated code is similar to this: --- 13413,13609 ---- you must compile your entire program with the same ABI, and link with a compatible set of libraries. ! `-mlittle-endian' Generate code for a processor running in little-endian mode. This is the default for all standard configurations. ! `-mbig-endian' Generate code for a processor running in big-endian mode; the default is to compile code for a little-endian processor. ! `-march=NAME' This specifies the name of the target ARM architecture. GCC uses this name to determine what kind of instructions it can emit when generating assembly code. This option can be used in conjunction ! with or instead of the `-mcpu=' option. Permissible names are: ! `armv2', `armv2a', `armv3', `armv3m', `armv4', `armv4t', `armv5', ! `armv5t', `armv5e', `armv5te', `armv6', `armv6j', `armv6t2', ! `armv6z', `armv6kz', `armv6-m', `armv7', `armv7-a', `armv7-r', ! `armv7-m', `armv7e-m', `armv7ve', `armv8-a', `armv8-a+crc', ! `armv8.1-a', `armv8.1-a+crc', `iwmmxt', `iwmmxt2', `ep9312'. ! Architecture revisions older than `armv4t' are deprecated. ! `-march=armv7ve' is the armv7-a architecture with virtualization extensions. ! `-march=armv8-a+crc' enables code generation for the ARMv8-A architecture together with the optional CRC32 extensions. ! `-march=native' causes the compiler to auto-detect the architecture of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect. ! `-mtune=NAME' This option specifies the name of the target ARM processor for which GCC should tune the performance of the code. For some ARM implementations better performance can be obtained by using this ! option. Permissible names are: `arm2', `arm250', `arm3', `arm6', ! `arm60', `arm600', `arm610', `arm620', `arm7', `arm7m', `arm7d', ! `arm7dm', `arm7di', `arm7dmi', `arm70', `arm700', `arm700i', ! `arm710', `arm710c', `arm7100', `arm720', `arm7500', `arm7500fe', ! `arm7tdmi', `arm7tdmi-s', `arm710t', `arm720t', `arm740t', ! `strongarm', `strongarm110', `strongarm1100', `strongarm1110', ! `arm8', `arm810', `arm9', `arm9e', `arm920', `arm920t', `arm922t', ! `arm946e-s', `arm966e-s', `arm968e-s', `arm926ej-s', `arm940t', ! `arm9tdmi', `arm10tdmi', `arm1020t', `arm1026ej-s', `arm10e', ! `arm1020e', `arm1022e', `arm1136j-s', `arm1136jf-s', `mpcore', ! `mpcorenovfp', `arm1156t2-s', `arm1156t2f-s', `arm1176jz-s', ! `arm1176jzf-s', `generic-armv7-a', `cortex-a5', `cortex-a7', ! `cortex-a8', `cortex-a9', `cortex-a12', `cortex-a15', `cortex-a17', ! `cortex-a32', `cortex-a35', `cortex-a53', `cortex-a57', ! `cortex-a72', `cortex-r4', `cortex-r4f', `cortex-r5', `cortex-r7', ! `cortex-r8', `cortex-m7', `cortex-m4', `cortex-m3', `cortex-m1', ! `cortex-m0', `cortex-m0plus', `cortex-m1.small-multiply', ! `cortex-m0.small-multiply', `cortex-m0plus.small-multiply', ! `exynos-m1', `qdf24xx', `marvell-pj4', `xscale', `iwmmxt', ! `iwmmxt2', `ep9312', `fa526', `fa626', `fa606te', `fa626te', ! `fmp626', `fa726te', `xgene1'. Additionally, this option can specify that GCC should tune the ! performance of the code for a big.LITTLE system. Permissible ! names are: `cortex-a15.cortex-a7', `cortex-a17.cortex-a7', ! `cortex-a57.cortex-a53', `cortex-a72.cortex-a53'. ! `-mtune=generic-ARCH' specifies that GCC should tune the performance for a blend of processors within architecture ARCH. The aim is to generate code that run well on the current most popular processors, balancing between optimizations that benefit some CPUs in the range, and avoiding performance pitfalls of other ! CPUs. The effects of this option may change in future GCC ! versions as CPU models come and go. ! `-mtune=native' causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect. ! `-mcpu=NAME' ! This specifies the name of the target ARM processor. GCC uses ! this name to derive the name of the target ARM architecture (as if ! specified by `-march') and the ARM processor type for which to ! tune for performance (as if specified by `-mtune'). Where this ! option is used in conjunction with `-march' or `-mtune', those ! options take precedence over the appropriate part of this option. Permissible names for this option are the same as those for ! `-mtune'. ! `-mcpu=generic-ARCH' is also permissible, and is equivalent to ! `-march=ARCH -mtune=generic-ARCH'. See `-mtune' for more information. ! `-mcpu=native' causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect. ! `-mfpu=NAME' ! This specifies what floating-point hardware (or hardware ! emulation) is available on the target. Permissible names are: ! `vfp', `vfpv3', `vfpv3-fp16', `vfpv3-d16', `vfpv3-d16-fp16', ! `vfpv3xd', `vfpv3xd-fp16', `neon', `neon-fp16', `vfpv4', ! `vfpv4-d16', `fpv4-sp-d16', `neon-vfpv4', `fpv5-d16', ! `fpv5-sp-d16', `fp-armv8', `neon-fp-armv8' and ! `crypto-neon-fp-armv8'. ! If `-msoft-float' is specified this specifies the format of floating-point values. If the selected floating-point hardware includes the NEON extension ! (e.g. `-mfpu'=`neon'), note that floating-point operations are not generated by GCC's auto-vectorization pass unless ! `-funsafe-math-optimizations' is also specified. This is because NEON hardware does not fully implement the IEEE 754 standard for floating-point arithmetic (in particular denormal values are treated as zero), so the use of NEON instructions may lead to a loss of precision. You can also set the fpu name at function level by using the ! `target("fpu=")' function attributes (*note ARM Function Attributes::) or pragmas (*note Function Specific Option Pragmas::). ! `-mfp16-format=NAME' ! Specify the format of the `__fp16' half-precision floating-point ! type. Permissible names are `none', `ieee', and `alternative'; ! the default is `none', in which case the `__fp16' type is not ! defined. *Note Half-Precision::, for more information. ! `-mstructure-size-boundary=N' The sizes of all structures and unions are rounded up to a multiple of the number of bits set by this option. Permissible values are 8, 32 and 64. The default value varies for different toolchains. ! For the COFF targeted toolchain the default value is 8. A value ! of 64 is only allowed if the underlying ABI supports it. ! Specifying a larger number can produce faster, more efficient ! code, but can also increase the size of the program. Different ! values are potentially incompatible. Code compiled with one value ! cannot necessarily expect to work with code or libraries compiled ! with another value, if they exchange information using structures ! or unions. ! `-mabort-on-noreturn' ! Generate a call to the function `abort' at the end of a `noreturn' function. It is executed if the function tries to return. ! `-mlong-calls' ! `-mno-long-calls' Tells the compiler to perform function calls by first loading the address of the function into a register and then performing a subroutine call on this register. This switch is needed if the ! target function lies outside of the 64-megabyte addressing range ! of the offset-based version of subroutine call instruction. Even if this switch is enabled, not all function calls are turned into long calls. The heuristic is that static functions, functions ! that have the `short_call' attribute, functions that are inside ! the scope of a `#pragma no_long_calls' directive, and functions ! whose definitions have already been compiled within the current ! compilation unit are not turned into long calls. The exceptions ! to this rule are that weak function definitions, functions with ! the `long_call' attribute or the `section' attribute, and ! functions that are within the scope of a `#pragma long_calls' ! directive are always turned into long calls. This feature is not enabled by default. Specifying ! `-mno-long-calls' restores the default behavior, as does placing ! the function calls within the scope of a `#pragma long_calls_off' directive. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers. ! `-msingle-pic-base' Treat the register used for PIC addressing as read-only, rather than loading it in the prologue for each function. The runtime system is responsible for initializing this register with an appropriate value before execution begins. ! `-mpic-register=REG' Specify the register to be used for PIC addressing. For standard PIC base case, the default is any suitable register determined by ! compiler. For single PIC base case, the default is `R9' if target is EABI based or stack-checking is enabled, otherwise the default ! is `R10'. ! `-mpic-data-is-text-relative' ! Assume that each data segments are relative to text segment at ! load time. Therefore, it permits addressing data using ! PC-relative operations. This option is on by default for targets ! other than VxWorks RTP. ! `-mpoke-function-name' Write the name of each function into the text section, directly preceding the function prologue. The generated code is similar to this: *************** These '-m' options are defined for the A *** 13504,13587 **** sub fp, ip, #4 When performing a stack backtrace, code can inspect the value of ! 'pc' stored at 'fp + 0'. If the trace function then looks at ! location 'pc - 12' and the top 8 bits are set, then we know that there is a function name embedded immediately preceding this ! location and has length '((pc[-3]) & 0xff000000)'. ! ! '-mthumb' ! '-marm' Select between generating code that executes in ARM and Thumb states. The default for most configurations is to generate code that executes in ARM state, but the default can be changed by ! configuring GCC with the '--with-mode='STATE configure option. You can also override the ARM and Thumb mode for each function by ! using the 'target("thumb")' and 'target("arm")' function attributes (*note ARM Function Attributes::) or pragmas (*note Function Specific Option Pragmas::). ! '-mtpcs-frame' Generate a stack frame that is compliant with the Thumb Procedure Call Standard for all non-leaf functions. (A leaf function is one that does not call any other functions.) The default is ! '-mno-tpcs-frame'. ! '-mtpcs-leaf-frame' Generate a stack frame that is compliant with the Thumb Procedure ! Call Standard for all leaf functions. (A leaf function is one that ! does not call any other functions.) The default is ! '-mno-apcs-leaf-frame'. ! '-mcallee-super-interworking' Gives all externally visible functions in the file being compiled an ARM instruction set header which switches to Thumb mode before ! executing the rest of the function. This allows these functions to ! be called from non-interworking code. This option is not valid in ! AAPCS configurations because interworking is enabled by default. ! '-mcaller-super-interworking' Allows calls via function pointers (including virtual functions) to execute correctly regardless of whether the target code has been ! compiled for interworking or not. There is a small overhead in the ! cost of executing a function pointer if this option is enabled. ! This option is not valid in AAPCS configurations because interworking is enabled by default. ! '-mtp=NAME' ! Specify the access model for the thread local storage pointer. The ! valid models are 'soft', which generates calls to ! '__aeabi_read_tp', 'cp15', which fetches the thread pointer from ! 'cp15' directly (supported in the arm6k architecture), and 'auto', which uses the best available method for the selected processor. ! The default setting is 'auto'. ! '-mtls-dialect=DIALECT' Specify the dialect to use for accessing thread local storage. Two ! DIALECTs are supported--'gnu' and 'gnu2'. The 'gnu' dialect selects the original GNU scheme for supporting local and global ! dynamic TLS models. The 'gnu2' dialect selects the GNU descriptor scheme, which provides better performance for shared libraries. The GNU descriptor scheme is compatible with the original scheme, but does require new assembler, linker and library support. ! Initial and local exec TLS models are unaffected by this option and ! always use the original scheme. ! '-mword-relocations' Only generate absolute relocations on word-sized values (i.e. R_ARM_ABS32). This is enabled by default on targets (uClinux, SymbianOS) where the runtime loader imposes this restriction, and ! when '-fpic' or '-fPIC' is specified. ! '-mfix-cortex-m3-ldrd' ! Some Cortex-M3 cores can cause data corruption when 'ldrd' instructions with overlapping destination and base registers are used. This option avoids generating these instructions. This ! option is enabled by default when '-mcpu=cortex-m3' is specified. ! '-munaligned-access' ! '-mno-unaligned-access' Enables (or disables) reading and writing of 16- and 32- bit values from addresses that are not 16- or 32- bit aligned. By default unaligned access is disabled for all pre-ARMv6 and all ARMv6-M --- 13619,13701 ---- sub fp, ip, #4 When performing a stack backtrace, code can inspect the value of ! `pc' stored at `fp + 0'. If the trace function then looks at ! location `pc - 12' and the top 8 bits are set, then we know that there is a function name embedded immediately preceding this ! location and has length `((pc[-3]) & 0xff000000)'. + `-mthumb' + `-marm' Select between generating code that executes in ARM and Thumb states. The default for most configurations is to generate code that executes in ARM state, but the default can be changed by ! configuring GCC with the `--with-mode='STATE configure option. You can also override the ARM and Thumb mode for each function by ! using the `target("thumb")' and `target("arm")' function attributes (*note ARM Function Attributes::) or pragmas (*note Function Specific Option Pragmas::). ! `-mtpcs-frame' Generate a stack frame that is compliant with the Thumb Procedure Call Standard for all non-leaf functions. (A leaf function is one that does not call any other functions.) The default is ! `-mno-tpcs-frame'. ! `-mtpcs-leaf-frame' Generate a stack frame that is compliant with the Thumb Procedure ! Call Standard for all leaf functions. (A leaf function is one ! that does not call any other functions.) The default is ! `-mno-apcs-leaf-frame'. ! `-mcallee-super-interworking' Gives all externally visible functions in the file being compiled an ARM instruction set header which switches to Thumb mode before ! executing the rest of the function. This allows these functions ! to be called from non-interworking code. This option is not valid ! in AAPCS configurations because interworking is enabled by default. ! `-mcaller-super-interworking' Allows calls via function pointers (including virtual functions) to execute correctly regardless of whether the target code has been ! compiled for interworking or not. There is a small overhead in ! the cost of executing a function pointer if this option is ! enabled. This option is not valid in AAPCS configurations because interworking is enabled by default. ! `-mtp=NAME' ! Specify the access model for the thread local storage pointer. ! The valid models are `soft', which generates calls to ! `__aeabi_read_tp', `cp15', which fetches the thread pointer from ! `cp15' directly (supported in the arm6k architecture), and `auto', which uses the best available method for the selected processor. ! The default setting is `auto'. ! `-mtls-dialect=DIALECT' Specify the dialect to use for accessing thread local storage. Two ! DIALECTs are supported--`gnu' and `gnu2'. The `gnu' dialect selects the original GNU scheme for supporting local and global ! dynamic TLS models. The `gnu2' dialect selects the GNU descriptor scheme, which provides better performance for shared libraries. The GNU descriptor scheme is compatible with the original scheme, but does require new assembler, linker and library support. ! Initial and local exec TLS models are unaffected by this option ! and always use the original scheme. ! `-mword-relocations' Only generate absolute relocations on word-sized values (i.e. R_ARM_ABS32). This is enabled by default on targets (uClinux, SymbianOS) where the runtime loader imposes this restriction, and ! when `-fpic' or `-fPIC' is specified. ! `-mfix-cortex-m3-ldrd' ! Some Cortex-M3 cores can cause data corruption when `ldrd' instructions with overlapping destination and base registers are used. This option avoids generating these instructions. This ! option is enabled by default when `-mcpu=cortex-m3' is specified. ! `-munaligned-access' ! `-mno-unaligned-access' Enables (or disables) reading and writing of 16- and 32- bit values from addresses that are not 16- or 32- bit aligned. By default unaligned access is disabled for all pre-ARMv6 and all ARMv6-M *************** These '-m' options are defined for the A *** 13589,13623 **** unaligned access is not enabled then words in packed data structures are accessed a byte at a time. ! The ARM attribute 'Tag_CPU_unaligned_access' is set in the generated object file to either true or false, depending upon the setting of this option. If unaligned access is enabled then the ! preprocessor symbol '__ARM_FEATURE_UNALIGNED' is also defined. ! '-mneon-for-64bits' ! Enables using Neon to handle scalar 64-bits operations. This is disabled by default since the cost of moving data from core registers to Neon is high. ! '-mslow-flash-data' Assume loading data from flash is slower than fetching instruction. Therefore literal load is minimized for better performance. This ! option is only supported when compiling for ARMv7 M-profile and off ! by default. ! '-masm-syntax-unified' Assume inline assembler is using unified asm syntax. The default is currently off which implies divided syntax. This option has no ! impact on Thumb2. However, this may change in future releases of ! GCC. Divided syntax should be considered deprecated. ! '-mrestrict-it' Restricts generation of IT blocks to conform to the rules of ARMv8. IT blocks can only contain a single 16-bit instruction from a ! select set of instructions. This option is on by default for ARMv8 Thumb mode. ! '-mprint-tune-info' Print CPU tuning information as comment in assembler file. This is an option used only for regression testing of the compiler and not intended for ordinary use in compiling code. This option is --- 13703,13737 ---- unaligned access is not enabled then words in packed data structures are accessed a byte at a time. ! The ARM attribute `Tag_CPU_unaligned_access' is set in the generated object file to either true or false, depending upon the setting of this option. If unaligned access is enabled then the ! preprocessor symbol `__ARM_FEATURE_UNALIGNED' is also defined. ! `-mneon-for-64bits' ! Enables using Neon to handle scalar 64-bits operations. This is disabled by default since the cost of moving data from core registers to Neon is high. ! `-mslow-flash-data' Assume loading data from flash is slower than fetching instruction. Therefore literal load is minimized for better performance. This ! option is only supported when compiling for ARMv7 M-profile and ! off by default. ! `-masm-syntax-unified' Assume inline assembler is using unified asm syntax. The default is currently off which implies divided syntax. This option has no ! impact on Thumb2. However, this may change in future releases of ! GCC. Divided syntax should be considered deprecated. ! `-mrestrict-it' Restricts generation of IT blocks to conform to the rules of ARMv8. IT blocks can only contain a single 16-bit instruction from a ! select set of instructions. This option is on by default for ARMv8 Thumb mode. ! `-mprint-tune-info' Print CPU tuning information as comment in assembler file. This is an option used only for regression testing of the compiler and not intended for ordinary use in compiling code. This option is *************** File: gcc.info, Node: AVR Options, Nex *** 13631,13776 **** These options are defined for AVR implementations: ! '-mmcu=MCU' Specify Atmel AVR instruction set architectures (ISA) or MCU type. ! The default for this option is 'avr2'. GCC supports the following AVR devices and ISAs: ! 'avr2' "Classic" devices with up to 8 KiB of program memory. ! MCU = 'attiny22', 'attiny26', 'at90c8534', 'at90s2313', ! 'at90s2323', 'at90s2333', 'at90s2343', 'at90s4414', ! 'at90s4433', 'at90s4434', 'at90s8515', 'at90s8535'. ! 'avr25' "Classic" devices with up to 8 KiB of program memory and with ! the 'MOVW' instruction. ! MCU = 'ata5272', 'ata6616c', 'attiny13', 'attiny13a', ! 'attiny2313', 'attiny2313a', 'attiny24', 'attiny24a', ! 'attiny25', 'attiny261', 'attiny261a', 'attiny43u', ! 'attiny4313', 'attiny44', 'attiny44a', 'attiny441', ! 'attiny45', 'attiny461', 'attiny461a', 'attiny48', ! 'attiny828', 'attiny84', 'attiny84a', 'attiny841', 'attiny85', ! 'attiny861', 'attiny861a', 'attiny87', 'attiny88', ! 'at86rf401'. ! 'avr3' ! "Classic" devices with 16 KiB up to 64 KiB of program memory. ! MCU = 'at43usb355', 'at76c711'. ! 'avr31' "Classic" devices with 128 KiB of program memory. ! MCU = 'atmega103', 'at43usb320'. ! 'avr35' "Classic" devices with 16 KiB up to 64 KiB of program memory ! and with the 'MOVW' instruction. ! MCU = 'ata5505', 'ata6617c', 'ata664251', 'atmega16u2', ! 'atmega32u2', 'atmega8u2', 'attiny1634', 'attiny167', ! 'at90usb162', 'at90usb82'. ! 'avr4' "Enhanced" devices with up to 8 KiB of program memory. ! MCU = 'ata6285', 'ata6286', 'ata6289', 'ata6612c', 'atmega48', ! 'atmega48a', 'atmega48p', 'atmega48pa', 'atmega48pb', ! 'atmega8', 'atmega8a', 'atmega8hva', 'atmega8515', ! 'atmega8535', 'atmega88', 'atmega88a', 'atmega88p', ! 'atmega88pa', 'atmega88pb', 'at90pwm1', 'at90pwm2', ! 'at90pwm2b', 'at90pwm3', 'at90pwm3b', 'at90pwm81'. ! 'avr5' "Enhanced" devices with 16 KiB up to 64 KiB of program memory. ! MCU = 'ata5702m322', 'ata5782', 'ata5790', 'ata5790n', ! 'ata5791', 'ata5795', 'ata5831', 'ata6613c', 'ata6614q', ! 'ata8210', 'ata8510', 'atmega16', 'atmega16a', 'atmega16hva', ! 'atmega16hva2', 'atmega16hvb', 'atmega16hvbrevb', ! 'atmega16m1', 'atmega16u4', 'atmega161', 'atmega162', ! 'atmega163', 'atmega164a', 'atmega164p', 'atmega164pa', ! 'atmega165', 'atmega165a', 'atmega165p', 'atmega165pa', ! 'atmega168', 'atmega168a', 'atmega168p', 'atmega168pa', ! 'atmega168pb', 'atmega169', 'atmega169a', 'atmega169p', ! 'atmega169pa', 'atmega32', 'atmega32a', 'atmega32c1', ! 'atmega32hvb', 'atmega32hvbrevb', 'atmega32m1', 'atmega32u4', ! 'atmega32u6', 'atmega323', 'atmega324a', 'atmega324p', ! 'atmega324pa', 'atmega325', 'atmega325a', 'atmega325p', ! 'atmega325pa', 'atmega3250', 'atmega3250a', 'atmega3250p', ! 'atmega3250pa', 'atmega328', 'atmega328p', 'atmega328pb', ! 'atmega329', 'atmega329a', 'atmega329p', 'atmega329pa', ! 'atmega3290', 'atmega3290a', 'atmega3290p', 'atmega3290pa', ! 'atmega406', 'atmega64', 'atmega64a', 'atmega64c1', ! 'atmega64hve', 'atmega64hve2', 'atmega64m1', 'atmega64rfr2', ! 'atmega640', 'atmega644', 'atmega644a', 'atmega644p', ! 'atmega644pa', 'atmega644rfr2', 'atmega645', 'atmega645a', ! 'atmega645p', 'atmega6450', 'atmega6450a', 'atmega6450p', ! 'atmega649', 'atmega649a', 'atmega649p', 'atmega6490', ! 'atmega6490a', 'atmega6490p', 'at90can32', 'at90can64', ! 'at90pwm161', 'at90pwm216', 'at90pwm316', 'at90scr100', ! 'at90usb646', 'at90usb647', 'at94k', 'm3000'. ! ! 'avr51' "Enhanced" devices with 128 KiB of program memory. ! MCU = 'atmega128', 'atmega128a', 'atmega128rfa1', ! 'atmega128rfr2', 'atmega1280', 'atmega1281', 'atmega1284', ! 'atmega1284p', 'atmega1284rfr2', 'at90can128', 'at90usb1286', ! 'at90usb1287'. ! 'avr6' ! "Enhanced" devices with 3-byte PC, i.e. with more than 128 KiB ! of program memory. ! MCU = 'atmega256rfr2', 'atmega2560', 'atmega2561', ! 'atmega2564rfr2'. ! 'avrxmega2' "XMEGA" devices with more than 8 KiB and up to 64 KiB of program memory. ! MCU = 'atxmega16a4', 'atxmega16a4u', 'atxmega16c4', ! 'atxmega16d4', 'atxmega16e5', 'atxmega32a4', 'atxmega32a4u', ! 'atxmega32c3', 'atxmega32c4', 'atxmega32d3', 'atxmega32d4', ! 'atxmega32e5', 'atxmega8e5'. ! 'avrxmega4' "XMEGA" devices with more than 64 KiB and up to 128 KiB of program memory. ! MCU = 'atxmega64a3', 'atxmega64a3u', 'atxmega64a4u', ! 'atxmega64b1', 'atxmega64b3', 'atxmega64c3', 'atxmega64d3', ! 'atxmega64d4'. ! 'avrxmega5' "XMEGA" devices with more than 64 KiB and up to 128 KiB of program memory and more than 64 KiB of RAM. ! MCU = 'atxmega64a1', 'atxmega64a1u'. ! 'avrxmega6' "XMEGA" devices with more than 128 KiB of program memory. ! MCU = 'atxmega128a3', 'atxmega128a3u', 'atxmega128b1', ! 'atxmega128b3', 'atxmega128c3', 'atxmega128d3', ! 'atxmega128d4', 'atxmega192a3', 'atxmega192a3u', ! 'atxmega192c3', 'atxmega192d3', 'atxmega256a3', ! 'atxmega256a3b', 'atxmega256a3bu', 'atxmega256a3u', ! 'atxmega256c3', 'atxmega256d3', 'atxmega384c3', ! 'atxmega384d3'. ! 'avrxmega7' "XMEGA" devices with more than 128 KiB of program memory and more than 64 KiB of RAM. ! MCU = 'atxmega128a1', 'atxmega128a1u', 'atxmega128a4u'. ! 'avrtiny' "TINY" Tiny core devices with 512 B up to 4 KiB of program memory. ! MCU = 'attiny10', 'attiny20', 'attiny4', 'attiny40', ! 'attiny5', 'attiny9'. ! 'avr1' This ISA is implemented by the minimal AVR core and supported for assembler only. ! MCU = 'attiny11', 'attiny12', 'attiny15', 'attiny28', ! 'at90s1200'. ! '-maccumulate-args' Accumulate outgoing function arguments and acquire/release the needed stack space for outgoing function arguments once in function prologue/epilogue. Without this option, outgoing arguments are --- 13745,13890 ---- These options are defined for AVR implementations: ! `-mmcu=MCU' Specify Atmel AVR instruction set architectures (ISA) or MCU type. ! The default for this option is `avr2'. GCC supports the following AVR devices and ISAs: ! `avr2' "Classic" devices with up to 8 KiB of program memory. ! MCU = `attiny22', `attiny26', `at90c8534', `at90s2313', ! `at90s2323', `at90s2333', `at90s2343', `at90s4414', ! `at90s4433', `at90s4434', `at90s8515', `at90s8535'. ! `avr25' "Classic" devices with up to 8 KiB of program memory and with ! the `MOVW' instruction. ! MCU = `ata5272', `ata6616c', `attiny13', `attiny13a', ! `attiny2313', `attiny2313a', `attiny24', `attiny24a', ! `attiny25', `attiny261', `attiny261a', `attiny43u', ! `attiny4313', `attiny44', `attiny44a', `attiny441', ! `attiny45', `attiny461', `attiny461a', `attiny48', ! `attiny828', `attiny84', `attiny84a', `attiny841', ! `attiny85', `attiny861', `attiny861a', `attiny87', ! `attiny88', `at86rf401'. ! `avr3' ! "Classic" devices with 16 KiB up to 64 KiB of program memory. ! MCU = `at43usb355', `at76c711'. ! `avr31' "Classic" devices with 128 KiB of program memory. ! MCU = `atmega103', `at43usb320'. ! `avr35' "Classic" devices with 16 KiB up to 64 KiB of program memory ! and with the `MOVW' instruction. ! MCU = `ata5505', `ata6617c', `ata664251', `atmega16u2', ! `atmega32u2', `atmega8u2', `attiny1634', `attiny167', ! `at90usb162', `at90usb82'. ! `avr4' "Enhanced" devices with up to 8 KiB of program memory. ! MCU = `ata6285', `ata6286', `ata6289', `ata6612c', ! `atmega48', `atmega48a', `atmega48p', `atmega48pa', ! `atmega48pb', `atmega8', `atmega8a', `atmega8hva', ! `atmega8515', `atmega8535', `atmega88', `atmega88a', ! `atmega88p', `atmega88pa', `atmega88pb', `at90pwm1', ! `at90pwm2', `at90pwm2b', `at90pwm3', `at90pwm3b', `at90pwm81'. ! `avr5' "Enhanced" devices with 16 KiB up to 64 KiB of program memory. + MCU = `ata5702m322', `ata5782', `ata5790', `ata5790n', + `ata5791', `ata5795', `ata5831', `ata6613c', `ata6614q', + `ata8210', `ata8510', `atmega16', `atmega16a', `atmega16hva', + `atmega16hva2', `atmega16hvb', `atmega16hvbrevb', + `atmega16m1', `atmega16u4', `atmega161', `atmega162', + `atmega163', `atmega164a', `atmega164p', `atmega164pa', + `atmega165', `atmega165a', `atmega165p', `atmega165pa', + `atmega168', `atmega168a', `atmega168p', `atmega168pa', + `atmega168pb', `atmega169', `atmega169a', `atmega169p', + `atmega169pa', `atmega32', `atmega32a', `atmega32c1', + `atmega32hvb', `atmega32hvbrevb', `atmega32m1', `atmega32u4', + `atmega32u6', `atmega323', `atmega324a', `atmega324p', + `atmega324pa', `atmega325', `atmega325a', `atmega325p', + `atmega325pa', `atmega3250', `atmega3250a', `atmega3250p', + `atmega3250pa', `atmega328', `atmega328p', `atmega328pb', + `atmega329', `atmega329a', `atmega329p', `atmega329pa', + `atmega3290', `atmega3290a', `atmega3290p', `atmega3290pa', + `atmega406', `atmega64', `atmega64a', `atmega64c1', + `atmega64hve', `atmega64hve2', `atmega64m1', `atmega64rfr2', + `atmega640', `atmega644', `atmega644a', `atmega644p', + `atmega644pa', `atmega644rfr2', `atmega645', `atmega645a', + `atmega645p', `atmega6450', `atmega6450a', `atmega6450p', + `atmega649', `atmega649a', `atmega649p', `atmega6490', + `atmega6490a', `atmega6490p', `at90can32', `at90can64', + `at90pwm161', `at90pwm216', `at90pwm316', `at90scr100', + `at90usb646', `at90usb647', `at94k', `m3000'. ! `avr51' "Enhanced" devices with 128 KiB of program memory. ! MCU = `atmega128', `atmega128a', `atmega128rfa1', ! `atmega128rfr2', `atmega1280', `atmega1281', `atmega1284', ! `atmega1284p', `atmega1284rfr2', `at90can128', `at90usb1286', ! `at90usb1287'. ! `avr6' ! "Enhanced" devices with 3-byte PC, i.e. with more than ! 128 KiB of program memory. ! MCU = `atmega256rfr2', `atmega2560', `atmega2561', ! `atmega2564rfr2'. ! `avrxmega2' "XMEGA" devices with more than 8 KiB and up to 64 KiB of program memory. ! MCU = `atxmega16a4', `atxmega16a4u', `atxmega16c4', ! `atxmega16d4', `atxmega16e5', `atxmega32a4', `atxmega32a4u', ! `atxmega32c3', `atxmega32c4', `atxmega32d3', `atxmega32d4', ! `atxmega32e5', `atxmega8e5'. ! `avrxmega4' "XMEGA" devices with more than 64 KiB and up to 128 KiB of program memory. ! MCU = `atxmega64a3', `atxmega64a3u', `atxmega64a4u', ! `atxmega64b1', `atxmega64b3', `atxmega64c3', `atxmega64d3', ! `atxmega64d4'. ! `avrxmega5' "XMEGA" devices with more than 64 KiB and up to 128 KiB of program memory and more than 64 KiB of RAM. ! MCU = `atxmega64a1', `atxmega64a1u'. ! `avrxmega6' "XMEGA" devices with more than 128 KiB of program memory. ! MCU = `atxmega128a3', `atxmega128a3u', `atxmega128b1', ! `atxmega128b3', `atxmega128c3', `atxmega128d3', ! `atxmega128d4', `atxmega192a3', `atxmega192a3u', ! `atxmega192c3', `atxmega192d3', `atxmega256a3', ! `atxmega256a3b', `atxmega256a3bu', `atxmega256a3u', ! `atxmega256c3', `atxmega256d3', `atxmega384c3', ! `atxmega384d3'. ! `avrxmega7' "XMEGA" devices with more than 128 KiB of program memory and more than 64 KiB of RAM. ! MCU = `atxmega128a1', `atxmega128a1u', `atxmega128a4u'. ! `avrtiny' "TINY" Tiny core devices with 512 B up to 4 KiB of program memory. ! MCU = `attiny10', `attiny20', `attiny4', `attiny40', ! `attiny5', `attiny9'. ! `avr1' This ISA is implemented by the minimal AVR core and supported for assembler only. ! MCU = `attiny11', `attiny12', `attiny15', `attiny28', ! `at90s1200'. ! ! `-maccumulate-args' Accumulate outgoing function arguments and acquire/release the needed stack space for outgoing function arguments once in function prologue/epilogue. Without this option, outgoing arguments are *************** These options are defined for AVR implem *** 13778,13869 **** Popping the arguments after the function call can be expensive on AVR so that accumulating the stack space might lead to smaller ! executables because arguments need not to be removed from the stack ! after such a function call. This option can lead to reduced code size for functions that perform several calls to functions that get their arguments on the stack like calls to printf-like functions. ! '-mbranch-cost=COST' Set the branch costs for conditional branch instructions to COST. ! Reasonable values for COST are small, non-negative integers. The default branch cost is 0. ! '-mcall-prologues' Functions prologues/epilogues are expanded as calls to appropriate subroutines. Code size is smaller. ! '-mint8' ! Assume 'int' to be 8-bit integer. This affects the sizes of all ! types: a 'char' is 1 byte, an 'int' is 1 byte, a 'long' is 2 bytes, ! and 'long long' is 4 bytes. Please note that this option does not conform to the C standards, but it results in smaller code size. ! '-mn-flash=NUM' Assume that the flash memory has a size of NUM times 64 KiB. ! '-mno-interrupts' Generated code is not compatible with hardware interrupts. Code size is smaller. ! '-mrelax' ! Try to replace 'CALL' resp. 'JMP' instruction by the shorter ! 'RCALL' resp. 'RJMP' instruction if applicable. Setting '-mrelax' ! just adds the '--mlink-relax' option to the assembler's command ! line and the '--relax' option to the linker's command line. Jump relaxing is performed by the linker because jump offsets are ! not known before code is located. Therefore, the assembler code generated by the compiler is the same, but the instructions in the executable may differ from instructions in the assembler code. Relaxing must be turned on if linker stubs are needed, see the ! section on 'EIND' and linker stubs below. ! '-mrmw' Assume that the device supports the Read-Modify-Write instructions ! 'XCH', 'LAC', 'LAS' and 'LAT'. ! '-msp8' Treat the stack pointer register as an 8-bit register, i.e. assume the high byte of the stack pointer is zero. In general, you don't need to set this option by hand. This option is used internally by the compiler to select and build ! multilibs for architectures 'avr2' and 'avr25'. These ! architectures mix devices with and without 'SPH'. For any setting ! other than '-mmcu=avr2' or '-mmcu=avr25' the compiler driver adds or removes this option from the compiler proper's command line, because the compiler then knows if the device or architecture has ! an 8-bit stack pointer and thus no 'SPH' register or not. ! '-mstrict-X' ! Use address register 'X' in a way proposed by the hardware. This ! means that 'X' is only used in indirect, post-increment or pre-decrement addressing. ! Without this option, the 'X' register may be used in the same way ! as 'Y' or 'Z' which then is emulated by additional instructions. ! For example, loading a value with 'X+const' addressing with a small ! non-negative 'const < 64' to a register RN is performed as adiw r26, const ; X += const ld RN, X ; RN = *X sbiw r26, const ; X -= const ! '-mtiny-stack' Only change the lower 8 bits of the stack pointer. ! '-nodevicelib' ! Don't link against AVR-LibC's device specific library 'libdev.a'. ! '-Waddr-space-convert' Warn about conversions between address spaces in the case where the resulting address space is not contained in the incoming address space. ! 3.18.5.1 'EIND' and Devices with More Than 128 Ki Bytes of Flash ................................................................ Pointers in the implementation are 16 bits wide. The address of a --- 13892,13983 ---- Popping the arguments after the function call can be expensive on AVR so that accumulating the stack space might lead to smaller ! executables because arguments need not to be removed from the ! stack after such a function call. This option can lead to reduced code size for functions that perform several calls to functions that get their arguments on the stack like calls to printf-like functions. ! `-mbranch-cost=COST' Set the branch costs for conditional branch instructions to COST. ! Reasonable values for COST are small, non-negative integers. The default branch cost is 0. ! `-mcall-prologues' Functions prologues/epilogues are expanded as calls to appropriate subroutines. Code size is smaller. ! `-mint8' ! Assume `int' to be 8-bit integer. This affects the sizes of all ! types: a `char' is 1 byte, an `int' is 1 byte, a `long' is 2 bytes, ! and `long long' is 4 bytes. Please note that this option does not conform to the C standards, but it results in smaller code size. ! `-mn-flash=NUM' Assume that the flash memory has a size of NUM times 64 KiB. ! `-mno-interrupts' Generated code is not compatible with hardware interrupts. Code size is smaller. ! `-mrelax' ! Try to replace `CALL' resp. `JMP' instruction by the shorter ! `RCALL' resp. `RJMP' instruction if applicable. Setting `-mrelax' ! just adds the `--mlink-relax' option to the assembler's command ! line and the `--relax' option to the linker's command line. Jump relaxing is performed by the linker because jump offsets are ! not known before code is located. Therefore, the assembler code generated by the compiler is the same, but the instructions in the executable may differ from instructions in the assembler code. Relaxing must be turned on if linker stubs are needed, see the ! section on `EIND' and linker stubs below. ! `-mrmw' Assume that the device supports the Read-Modify-Write instructions ! `XCH', `LAC', `LAS' and `LAT'. ! `-msp8' Treat the stack pointer register as an 8-bit register, i.e. assume the high byte of the stack pointer is zero. In general, you don't need to set this option by hand. This option is used internally by the compiler to select and build ! multilibs for architectures `avr2' and `avr25'. These ! architectures mix devices with and without `SPH'. For any setting ! other than `-mmcu=avr2' or `-mmcu=avr25' the compiler driver adds or removes this option from the compiler proper's command line, because the compiler then knows if the device or architecture has ! an 8-bit stack pointer and thus no `SPH' register or not. ! `-mstrict-X' ! Use address register `X' in a way proposed by the hardware. This ! means that `X' is only used in indirect, post-increment or pre-decrement addressing. ! Without this option, the `X' register may be used in the same way ! as `Y' or `Z' which then is emulated by additional instructions. ! For example, loading a value with `X+const' addressing with a ! small non-negative `const < 64' to a register RN is performed as adiw r26, const ; X += const ld RN, X ; RN = *X sbiw r26, const ; X -= const ! `-mtiny-stack' Only change the lower 8 bits of the stack pointer. ! `-nodevicelib' ! Don't link against AVR-LibC's device specific library `libdev.a'. ! `-Waddr-space-convert' Warn about conversions between address spaces in the case where the resulting address space is not contained in the incoming address space. ! 3.18.5.1 `EIND' and Devices with More Than 128 Ki Bytes of Flash ................................................................ Pointers in the implementation are 16 bits wide. The address of a *************** and calls can target any code address in *** 13872,13921 **** In order to facilitate indirect jump on devices with more than 128 Ki bytes of program memory space, there is a special function register ! called 'EIND' that serves as most significant part of the target address ! when 'EICALL' or 'EIJMP' instructions are used. ! Indirect jumps and calls on these devices are handled as follows by the ! compiler and are subject to some limitations: ! * The compiler never sets 'EIND'. ! * The compiler uses 'EIND' implicitly in 'EICALL'/'EIJMP' ! instructions or might read 'EIND' directly in order to emulate an ! indirect call/jump by means of a 'RET' instruction. ! * The compiler assumes that 'EIND' never changes during the startup ! code or during the application. In particular, 'EIND' is not saved/restored in function or interrupt service routine prologue/epilogue. * For indirect calls to functions and computed goto, the linker ! generates _stubs_. Stubs are jump pads sometimes also called ! _trampolines_. Thus, the indirect call/jump jumps to such a stub. The stub contains a direct jump to the desired address. * Linker relaxation must be turned on so that the linker generates ! the stubs correctly in all situations. See the compiler option ! '-mrelax' and the linker option '--relax'. There are corner cases where the linker is supposed to generate stubs but aborts without relaxation and without a helpful error message. ! * The default linker script is arranged for code with 'EIND = 0'. If ! code is supposed to work for a setup with 'EIND != 0', a custom linker script has to be used in order to place the sections whose ! name start with '.trampolines' into the segment where 'EIND' points ! to. ! * The startup code from libgcc never sets 'EIND'. Notice that ! startup code is a blend of code from libgcc and AVR-LibC. For the ! impact of AVR-LibC on 'EIND', see the AVR-LibC user manual (http://nongnu.org/avr-libc/user-manual/). ! * It is legitimate for user-specific startup code to set up 'EIND' early, for example by means of initialization code located in ! section '.init3'. Such code runs prior to general startup code that initializes RAM and calls constructors, but after the bit of ! startup code from AVR-LibC that sets 'EIND' to the segment where the vector table is located. #include --- 13986,14035 ---- In order to facilitate indirect jump on devices with more than 128 Ki bytes of program memory space, there is a special function register ! called `EIND' that serves as most significant part of the target address ! when `EICALL' or `EIJMP' instructions are used. ! Indirect jumps and calls on these devices are handled as follows by ! the compiler and are subject to some limitations: ! * The compiler never sets `EIND'. ! * The compiler uses `EIND' implicitly in `EICALL'/`EIJMP' ! instructions or might read `EIND' directly in order to emulate an ! indirect call/jump by means of a `RET' instruction. ! * The compiler assumes that `EIND' never changes during the startup ! code or during the application. In particular, `EIND' is not saved/restored in function or interrupt service routine prologue/epilogue. * For indirect calls to functions and computed goto, the linker ! generates _stubs_. Stubs are jump pads sometimes also called ! _trampolines_. Thus, the indirect call/jump jumps to such a stub. The stub contains a direct jump to the desired address. * Linker relaxation must be turned on so that the linker generates ! the stubs correctly in all situations. See the compiler option ! `-mrelax' and the linker option `--relax'. There are corner cases where the linker is supposed to generate stubs but aborts without relaxation and without a helpful error message. ! * The default linker script is arranged for code with `EIND = 0'. ! If code is supposed to work for a setup with `EIND != 0', a custom linker script has to be used in order to place the sections whose ! name start with `.trampolines' into the segment where `EIND' ! points to. ! * The startup code from libgcc never sets `EIND'. Notice that ! startup code is a blend of code from libgcc and AVR-LibC. For the ! impact of AVR-LibC on `EIND', see the AVR-LibC user manual (http://nongnu.org/avr-libc/user-manual/). ! * It is legitimate for user-specific startup code to set up `EIND' early, for example by means of initialization code located in ! section `.init3'. Such code runs prior to general startup code that initializes RAM and calls constructors, but after the bit of ! startup code from AVR-LibC that sets `EIND' to the segment where the vector table is located. #include *************** compiler and are subject to some limitat *** 13927,13956 **** "out %i0,r24" :: "n" (&EIND) : "r24","memory"); } ! The '__trampolines_start' symbol is defined in the linker script. * Stubs are generated automatically by the linker if the following two conditions are met: ! ! - The address of a label is taken by means of the 'gs' modifier (short for _generate stubs_) like so: LDI r24, lo8(gs(FUNC)) LDI r25, hi8(gs(FUNC)) - The final location of that label is in a code segment _outside_ the segment where the stubs are located. ! * The compiler emits such 'gs' modifiers for code labels in the following situations: - Taking address of a function or code label. - Computed goto. ! - If prologue-save function is used, see '-mcall-prologues' command-line option. ! - Switch/case dispatch tables. If you do not want such dispatch ! tables you can specify the '-fno-jump-tables' command-line option. - C and C++ constructors/destructors called during startup/shutdown. ! - If the tools hit a 'gs()' modifier explained above. * Jumping to non-symbolic addresses like so is _not_ supported: --- 14041,14075 ---- "out %i0,r24" :: "n" (&EIND) : "r24","memory"); } ! The `__trampolines_start' symbol is defined in the linker script. * Stubs are generated automatically by the linker if the following two conditions are met: ! - The address of a label is taken by means of the `gs' modifier (short for _generate stubs_) like so: LDI r24, lo8(gs(FUNC)) LDI r25, hi8(gs(FUNC)) + - The final location of that label is in a code segment _outside_ the segment where the stubs are located. ! * The compiler emits such `gs' modifiers for code labels in the following situations: - Taking address of a function or code label. + - Computed goto. ! ! - If prologue-save function is used, see `-mcall-prologues' command-line option. ! ! - Switch/case dispatch tables. If you do not want such dispatch ! tables you can specify the `-fno-jump-tables' command-line option. + - C and C++ constructors/destructors called during startup/shutdown. ! ! - If the tools hit a `gs()' modifier explained above. * Jumping to non-symbolic addresses like so is _not_ supported: *************** compiler and are subject to some limitat *** 13961,13967 **** } Instead, a stub has to be set up, i.e. the function has to be ! called through a symbol ('func_4' in the example): int main (void) { --- 14080,14086 ---- } Instead, a stub has to be set up, i.e. the function has to be ! called through a symbol (`func_4' in the example): int main (void) { *************** compiler and are subject to some limitat *** 13971,14009 **** return func_4(); } ! and the application be linked with '-Wl,--defsym,func_4=0x4'. ! Alternatively, 'func_4' can be defined in the linker script. ! 3.18.5.2 Handling of the 'RAMPD', 'RAMPX', 'RAMPY' and 'RAMPZ' Special Function Registers ......................................................................................... Some AVR devices support memories larger than the 64 KiB range that can be accessed with 16-bit pointers. To access memory locations outside ! this 64 KiB range, the contentent of a 'RAMP' register is used as high ! part of the address: The 'X', 'Y', 'Z' address register is concatenated ! with the 'RAMPX', 'RAMPY', 'RAMPZ' special function register, ! respectively, to get a wide address. Similarly, 'RAMPD' is used together with direct addressing. ! * The startup code initializes the 'RAMP' special function registers with zero. * If a *note named address space: AVR Named Address Spaces. other ! than generic or '__flash' is used, then 'RAMPZ' is set as needed before the operation. * If the device supports RAM larger than 64 KiB and the compiler ! needs to change 'RAMPZ' to accomplish an operation, 'RAMPZ' is reset to zero after the operation. ! * If the device comes with a specific 'RAMP' register, the ISR prologue/epilogue saves/restores that SFR and initializes it with zero in case the ISR code might (implicitly) use it. ! * RAM larger than 64 KiB is not supported by GCC for AVR targets. If ! you use inline assembler to read from locations outside the 16-bit ! address range and change one of the 'RAMP' registers, you must ! reset it to zero after the access. 3.18.5.3 AVR Built-in Macros ............................ --- 14090,14129 ---- return func_4(); } ! and the application be linked with `-Wl,--defsym,func_4=0x4'. ! Alternatively, `func_4' can be defined in the linker script. ! 3.18.5.2 Handling of the `RAMPD', `RAMPX', `RAMPY' and `RAMPZ' Special Function Registers ......................................................................................... Some AVR devices support memories larger than the 64 KiB range that can be accessed with 16-bit pointers. To access memory locations outside ! this 64 KiB range, the contentent of a `RAMP' register is used as high ! part of the address: The `X', `Y', `Z' address register is concatenated ! with the `RAMPX', `RAMPY', `RAMPZ' special function register, ! respectively, to get a wide address. Similarly, `RAMPD' is used together with direct addressing. ! * The startup code initializes the `RAMP' special function registers with zero. * If a *note named address space: AVR Named Address Spaces. other ! than generic or `__flash' is used, then `RAMPZ' is set as needed before the operation. * If the device supports RAM larger than 64 KiB and the compiler ! needs to change `RAMPZ' to accomplish an operation, `RAMPZ' is reset to zero after the operation. ! * If the device comes with a specific `RAMP' register, the ISR prologue/epilogue saves/restores that SFR and initializes it with zero in case the ISR code might (implicitly) use it. ! * RAM larger than 64 KiB is not supported by GCC for AVR targets. ! If you use inline assembler to read from locations outside the ! 16-bit address range and change one of the `RAMP' registers, you ! must reset it to zero after the access. ! 3.18.5.3 AVR Built-in Macros ............................ *************** together with direct addressing. *** 14011,14140 **** GCC defines several built-in macros so that the user code can test for the presence or absence of features. Almost any of the following built-in macros are deduced from device capabilities and thus triggered ! by the '-mmcu=' command-line option. For even more AVR-specific built-in macros see *note AVR Named Address Spaces:: and *note AVR Built-in Functions::. ! '__AVR_ARCH__' Build-in macro that resolves to a decimal number that identifies ! the architecture and depends on the '-mmcu=MCU' option. Possible values are: ! '2', '25', '3', '31', '35', '4', '5', '51', '6' ! for MCU='avr2', 'avr25', 'avr3', 'avr31', 'avr35', 'avr4', 'avr5', ! 'avr51', 'avr6', respectively and ! '100', '102', '104', '105', '106', '107' ! for MCU='avrtiny', 'avrxmega2', 'avrxmega4', 'avrxmega5', ! 'avrxmega6', 'avrxmega7', respectively. If MCU specifies a device, ! this built-in macro is set accordingly. For example, with ! '-mmcu=atmega8' the macro is defined to '4'. ! '__AVR_DEVICE__' ! Setting '-mmcu=DEVICE' defines this built-in macro which reflects ! the device's name. For example, '-mmcu=atmega8' defines the ! built-in macro '__AVR_ATmega8__', '-mmcu=attiny261a' defines ! '__AVR_ATtiny261A__', etc. ! The built-in macros' names follow the scheme '__AVR_DEVICE__' where ! DEVICE is the device name as from the AVR user manual. The difference between DEVICE in the built-in macro and DEVICE in ! '-mmcu=DEVICE' is that the latter is always lowercase. If DEVICE is not a device but only a core architecture like ! 'avr51', this macro is not defined. ! '__AVR_DEVICE_NAME__' ! Setting '-mmcu=DEVICE' defines this built-in macro to the device's ! name. For example, with '-mmcu=atmega8' the macro is defined to ! 'atmega8'. If DEVICE is not a device but only a core architecture like ! 'avr51', this macro is not defined. ! '__AVR_XMEGA__' The device / architecture belongs to the XMEGA family of devices. ! '__AVR_HAVE_ELPM__' ! The device has the 'ELPM' instruction. ! '__AVR_HAVE_ELPMX__' ! The device has the 'ELPM RN,Z' and 'ELPM RN,Z+' instructions. ! '__AVR_HAVE_MOVW__' ! The device has the 'MOVW' instruction to perform 16-bit register-register moves. ! '__AVR_HAVE_LPMX__' ! The device has the 'LPM RN,Z' and 'LPM RN,Z+' instructions. ! '__AVR_HAVE_MUL__' The device has a hardware multiplier. ! '__AVR_HAVE_JMP_CALL__' ! The device has the 'JMP' and 'CALL' instructions. This is the case ! for devices with at least 16 KiB of program memory. ! '__AVR_HAVE_EIJMP_EICALL__' ! '__AVR_3_BYTE_PC__' ! The device has the 'EIJMP' and 'EICALL' instructions. This is the case for devices with more than 128 KiB of program memory. This also means that the program counter (PC) is 3 bytes wide. ! '__AVR_2_BYTE_PC__' ! The program counter (PC) is 2 bytes wide. This is the case for devices with up to 128 KiB of program memory. ! '__AVR_HAVE_8BIT_SP__' ! '__AVR_HAVE_16BIT_SP__' The stack pointer (SP) register is treated as 8-bit respectively ! 16-bit register by the compiler. The definition of these macros is ! affected by '-mtiny-stack'. ! '__AVR_HAVE_SPH__' ! '__AVR_SP8__' The device has the SPH (high part of stack pointer) special ! function register or has an 8-bit stack pointer, respectively. The ! definition of these macros is affected by '-mmcu=' and in the cases ! of '-mmcu=avr2' and '-mmcu=avr25' also by '-msp8'. ! '__AVR_HAVE_RAMPD__' ! '__AVR_HAVE_RAMPX__' ! '__AVR_HAVE_RAMPY__' ! '__AVR_HAVE_RAMPZ__' ! The device has the 'RAMPD', 'RAMPX', 'RAMPY', 'RAMPZ' special function register, respectively. ! '__NO_INTERRUPTS__' ! This macro reflects the '-mno-interrupts' command-line option. ! '__AVR_ERRATA_SKIP__' ! '__AVR_ERRATA_SKIP_JMP_CALL__' Some AVR devices (AT90S8515, ATmega103) must not skip 32-bit instructions because of a hardware erratum. Skip instructions are ! 'SBRS', 'SBRC', 'SBIS', 'SBIC' and 'CPSE'. The second macro is ! only defined if '__AVR_HAVE_JMP_CALL__' is also set. ! '__AVR_ISA_RMW__' The device has Read-Modify-Write instructions (XCH, LAC, LAS and LAT). ! '__AVR_SFR_OFFSET__=OFFSET' Instructions that can address I/O special function registers ! directly like 'IN', 'OUT', 'SBI', etc. may use a different address ! as if addressed by an instruction to access RAM like 'LD' or 'STS'. ! This offset depends on the device architecture and has to be ! subtracted from the RAM address in order to get the respective I/O address. ! '__WITH_AVRLIBC__' The compiler is configured to be used together with AVR-Libc. See ! the '--with-avrlibc' configure option.  File: gcc.info, Node: Blackfin Options, Next: C6X Options, Prev: AVR Options, Up: Submodel Options --- 14131,14261 ---- GCC defines several built-in macros so that the user code can test for the presence or absence of features. Almost any of the following built-in macros are deduced from device capabilities and thus triggered ! by the `-mmcu=' command-line option. For even more AVR-specific built-in macros see *note AVR Named Address Spaces:: and *note AVR Built-in Functions::. ! `__AVR_ARCH__' Build-in macro that resolves to a decimal number that identifies ! the architecture and depends on the `-mmcu=MCU' option. Possible values are: ! `2', `25', `3', `31', `35', `4', `5', `51', `6' ! for MCU=`avr2', `avr25', `avr3', `avr31', `avr35', `avr4', `avr5', ! `avr51', `avr6', respectively and ! `100', `102', `104', `105', `106', `107' ! for MCU=`avrtiny', `avrxmega2', `avrxmega4', `avrxmega5', ! `avrxmega6', `avrxmega7', respectively. If MCU specifies a ! device, this built-in macro is set accordingly. For example, with ! `-mmcu=atmega8' the macro is defined to `4'. ! `__AVR_DEVICE__' ! Setting `-mmcu=DEVICE' defines this built-in macro which reflects ! the device's name. For example, `-mmcu=atmega8' defines the ! built-in macro `__AVR_ATmega8__', `-mmcu=attiny261a' defines ! `__AVR_ATtiny261A__', etc. ! The built-in macros' names follow the scheme `__AVR_DEVICE__' ! where DEVICE is the device name as from the AVR user manual. The difference between DEVICE in the built-in macro and DEVICE in ! `-mmcu=DEVICE' is that the latter is always lowercase. If DEVICE is not a device but only a core architecture like ! `avr51', this macro is not defined. ! `__AVR_DEVICE_NAME__' ! Setting `-mmcu=DEVICE' defines this built-in macro to the device's ! name. For example, with `-mmcu=atmega8' the macro is defined to ! `atmega8'. If DEVICE is not a device but only a core architecture like ! `avr51', this macro is not defined. ! `__AVR_XMEGA__' The device / architecture belongs to the XMEGA family of devices. ! `__AVR_HAVE_ELPM__' ! The device has the `ELPM' instruction. ! `__AVR_HAVE_ELPMX__' ! The device has the `ELPM RN,Z' and `ELPM RN,Z+' instructions. ! `__AVR_HAVE_MOVW__' ! The device has the `MOVW' instruction to perform 16-bit register-register moves. ! `__AVR_HAVE_LPMX__' ! The device has the `LPM RN,Z' and `LPM RN,Z+' instructions. ! `__AVR_HAVE_MUL__' The device has a hardware multiplier. ! `__AVR_HAVE_JMP_CALL__' ! The device has the `JMP' and `CALL' instructions. This is the ! case for devices with at least 16 KiB of program memory. ! `__AVR_HAVE_EIJMP_EICALL__' ! `__AVR_3_BYTE_PC__' ! The device has the `EIJMP' and `EICALL' instructions. This is the case for devices with more than 128 KiB of program memory. This also means that the program counter (PC) is 3 bytes wide. ! `__AVR_2_BYTE_PC__' ! The program counter (PC) is 2 bytes wide. This is the case for devices with up to 128 KiB of program memory. ! `__AVR_HAVE_8BIT_SP__' ! `__AVR_HAVE_16BIT_SP__' The stack pointer (SP) register is treated as 8-bit respectively ! 16-bit register by the compiler. The definition of these macros ! is affected by `-mtiny-stack'. ! `__AVR_HAVE_SPH__' ! `__AVR_SP8__' The device has the SPH (high part of stack pointer) special ! function register or has an 8-bit stack pointer, respectively. ! The definition of these macros is affected by `-mmcu=' and in the ! cases of `-mmcu=avr2' and `-mmcu=avr25' also by `-msp8'. ! `__AVR_HAVE_RAMPD__' ! `__AVR_HAVE_RAMPX__' ! `__AVR_HAVE_RAMPY__' ! `__AVR_HAVE_RAMPZ__' ! The device has the `RAMPD', `RAMPX', `RAMPY', `RAMPZ' special function register, respectively. ! `__NO_INTERRUPTS__' ! This macro reflects the `-mno-interrupts' command-line option. ! `__AVR_ERRATA_SKIP__' ! `__AVR_ERRATA_SKIP_JMP_CALL__' Some AVR devices (AT90S8515, ATmega103) must not skip 32-bit instructions because of a hardware erratum. Skip instructions are ! `SBRS', `SBRC', `SBIS', `SBIC' and `CPSE'. The second macro is ! only defined if `__AVR_HAVE_JMP_CALL__' is also set. ! `__AVR_ISA_RMW__' The device has Read-Modify-Write instructions (XCH, LAC, LAS and LAT). ! `__AVR_SFR_OFFSET__=OFFSET' Instructions that can address I/O special function registers ! directly like `IN', `OUT', `SBI', etc. may use a different address ! as if addressed by an instruction to access RAM like `LD' or ! `STS'. This offset depends on the device architecture and has to ! be subtracted from the RAM address in order to get the respective I/O address. ! `__WITH_AVRLIBC__' The compiler is configured to be used together with AVR-Libc. See ! the `--with-avrlibc' configure option. !  File: gcc.info, Node: Blackfin Options, Next: C6X Options, Prev: AVR Options, Up: Submodel Options *************** File: gcc.info, Node: Blackfin Options, *** 14142,14261 **** 3.18.6 Blackfin Options ----------------------- ! '-mcpu=CPU[-SIREVISION]' Specifies the name of the target Blackfin processor. Currently, ! CPU can be one of 'bf512', 'bf514', 'bf516', 'bf518', 'bf522', ! 'bf523', 'bf524', 'bf525', 'bf526', 'bf527', 'bf531', 'bf532', ! 'bf533', 'bf534', 'bf536', 'bf537', 'bf538', 'bf539', 'bf542', ! 'bf544', 'bf547', 'bf548', 'bf549', 'bf542m', 'bf544m', 'bf547m', ! 'bf548m', 'bf549m', 'bf561', 'bf592'. The optional SIREVISION specifies the silicon revision of the target Blackfin processor. Any workarounds available for the ! targeted silicon revision are enabled. If SIREVISION is 'none', no ! workarounds are enabled. If SIREVISION is 'any', all workarounds ! for the targeted processor are enabled. The '__SILICON_REVISION__' ! macro is defined to two hexadecimal digits representing the major ! and minor numbers in the silicon revision. If SIREVISION is ! 'none', the '__SILICON_REVISION__' is not defined. If SIREVISION ! is 'any', the '__SILICON_REVISION__' is defined to be '0xffff'. If ! this optional SIREVISION is not used, GCC assumes the latest known ! silicon revision of the targeted Blackfin processor. GCC defines a preprocessor macro for the specified CPU. For the ! 'bfin-elf' toolchain, this option causes the hardware BSP provided ! by libgloss to be linked in if '-msim' is not given. ! Without this option, 'bf532' is used as the processor by default. ! Note that support for 'bf561' is incomplete. For 'bf561', only the ! preprocessor macro is defined. ! '-msim' Specifies that the program will be run on the simulator. This causes the simulator BSP provided by libgloss to be linked in. ! This option has effect only for 'bfin-elf' toolchain. Certain ! other options, such as '-mid-shared-library' and '-mfdpic', imply ! '-msim'. ! '-momit-leaf-frame-pointer' Don't keep the frame pointer in a register for leaf functions. This avoids the instructions to save, set up and restore frame pointers and makes an extra register available in leaf functions. ! The option '-fomit-frame-pointer' removes the frame pointer for all ! functions, which might make debugging harder. ! '-mspecld-anomaly' When enabled, the compiler ensures that the generated code does not ! contain speculative loads after jump instructions. If this option ! is used, '__WORKAROUND_SPECULATIVE_LOADS' is defined. ! '-mno-specld-anomaly' Don't generate extra code to prevent speculative loads from occurring. ! '-mcsync-anomaly' When enabled, the compiler ensures that the generated code does not contain CSYNC or SSYNC instructions too soon after conditional ! branches. If this option is used, '__WORKAROUND_SPECULATIVE_SYNCS' ! is defined. ! '-mno-csync-anomaly' Don't generate extra code to prevent CSYNC or SSYNC instructions from occurring too soon after a conditional branch. ! '-mlow-64k' When enabled, the compiler is free to take advantage of the knowledge that the entire program fits into the low 64k of memory. ! '-mno-low-64k' Assume that the program is arbitrarily large. This is the default. ! '-mstack-check-l1' Do stack checking using information placed into L1 scratchpad memory by the uClinux kernel. ! '-mid-shared-library' Generate code that supports shared libraries via the library ID method. This allows for execute in place and shared libraries in an environment without virtual memory management. This option ! implies '-fPIC'. With a 'bfin-elf' target, this option implies ! '-msim'. ! '-mno-id-shared-library' Generate code that doesn't assume ID-based shared libraries are being used. This is the default. ! '-mleaf-id-shared-library' Generate code that supports shared libraries via the library ID method, but assumes that this library or executable won't link ! against any other ID shared libraries. That allows the compiler to ! use faster code for jumps and calls. ! '-mno-leaf-id-shared-library' Do not assume that the code being compiled won't link against any ID shared libraries. Slower code is generated for jump and call insns. ! '-mshared-library-id=n' Specifies the identification number of the ID-based shared library being compiled. Specifying a value of 0 generates more compact code; specifying other values forces the allocation of that number ! to the current library but is no more space- or time-efficient than ! omitting this option. ! '-msep-data' Generate code that allows the data segment to be located in a different area of memory from the text segment. This allows for execute in place in an environment without virtual memory management by eliminating relocations against the text section. ! '-mno-sep-data' Generate code that assumes that the data segment follows the text segment. This is the default. ! '-mlong-calls' ! '-mno-long-calls' Tells the compiler to perform function calls by first loading the address of the function into a register and then performing a subroutine call on this register. This switch is needed if the --- 14263,14383 ---- 3.18.6 Blackfin Options ----------------------- ! `-mcpu=CPU[-SIREVISION]' Specifies the name of the target Blackfin processor. Currently, ! CPU can be one of `bf512', `bf514', `bf516', `bf518', `bf522', ! `bf523', `bf524', `bf525', `bf526', `bf527', `bf531', `bf532', ! `bf533', `bf534', `bf536', `bf537', `bf538', `bf539', `bf542', ! `bf544', `bf547', `bf548', `bf549', `bf542m', `bf544m', `bf547m', ! `bf548m', `bf549m', `bf561', `bf592'. The optional SIREVISION specifies the silicon revision of the target Blackfin processor. Any workarounds available for the ! targeted silicon revision are enabled. If SIREVISION is `none', ! no workarounds are enabled. If SIREVISION is `any', all ! workarounds for the targeted processor are enabled. The ! `__SILICON_REVISION__' macro is defined to two hexadecimal digits ! representing the major and minor numbers in the silicon revision. ! If SIREVISION is `none', the `__SILICON_REVISION__' is not ! defined. If SIREVISION is `any', the `__SILICON_REVISION__' is ! defined to be `0xffff'. If this optional SIREVISION is not used, ! GCC assumes the latest known silicon revision of the targeted ! Blackfin processor. GCC defines a preprocessor macro for the specified CPU. For the ! `bfin-elf' toolchain, this option causes the hardware BSP provided ! by libgloss to be linked in if `-msim' is not given. ! Without this option, `bf532' is used as the processor by default. ! Note that support for `bf561' is incomplete. For `bf561', only ! the preprocessor macro is defined. ! `-msim' Specifies that the program will be run on the simulator. This causes the simulator BSP provided by libgloss to be linked in. ! This option has effect only for `bfin-elf' toolchain. Certain ! other options, such as `-mid-shared-library' and `-mfdpic', imply ! `-msim'. ! `-momit-leaf-frame-pointer' Don't keep the frame pointer in a register for leaf functions. This avoids the instructions to save, set up and restore frame pointers and makes an extra register available in leaf functions. ! The option `-fomit-frame-pointer' removes the frame pointer for ! all functions, which might make debugging harder. ! `-mspecld-anomaly' When enabled, the compiler ensures that the generated code does not ! contain speculative loads after jump instructions. If this option ! is used, `__WORKAROUND_SPECULATIVE_LOADS' is defined. ! `-mno-specld-anomaly' Don't generate extra code to prevent speculative loads from occurring. ! `-mcsync-anomaly' When enabled, the compiler ensures that the generated code does not contain CSYNC or SSYNC instructions too soon after conditional ! branches. If this option is used, ! `__WORKAROUND_SPECULATIVE_SYNCS' is defined. ! `-mno-csync-anomaly' Don't generate extra code to prevent CSYNC or SSYNC instructions from occurring too soon after a conditional branch. ! `-mlow-64k' When enabled, the compiler is free to take advantage of the knowledge that the entire program fits into the low 64k of memory. ! `-mno-low-64k' Assume that the program is arbitrarily large. This is the default. ! `-mstack-check-l1' Do stack checking using information placed into L1 scratchpad memory by the uClinux kernel. ! `-mid-shared-library' Generate code that supports shared libraries via the library ID method. This allows for execute in place and shared libraries in an environment without virtual memory management. This option ! implies `-fPIC'. With a `bfin-elf' target, this option implies ! `-msim'. ! `-mno-id-shared-library' Generate code that doesn't assume ID-based shared libraries are being used. This is the default. ! `-mleaf-id-shared-library' Generate code that supports shared libraries via the library ID method, but assumes that this library or executable won't link ! against any other ID shared libraries. That allows the compiler ! to use faster code for jumps and calls. ! `-mno-leaf-id-shared-library' Do not assume that the code being compiled won't link against any ID shared libraries. Slower code is generated for jump and call insns. ! `-mshared-library-id=n' Specifies the identification number of the ID-based shared library being compiled. Specifying a value of 0 generates more compact code; specifying other values forces the allocation of that number ! to the current library but is no more space- or time-efficient ! than omitting this option. ! `-msep-data' Generate code that allows the data segment to be located in a different area of memory from the text segment. This allows for execute in place in an environment without virtual memory management by eliminating relocations against the text section. ! `-mno-sep-data' Generate code that assumes that the data segment follows the text segment. This is the default. ! `-mlong-calls' ! `-mno-long-calls' Tells the compiler to perform function calls by first loading the address of the function into a register and then performing a subroutine call on this register. This switch is needed if the *************** File: gcc.info, Node: Blackfin Options, *** 14263,14318 **** offset-based version of subroutine call instruction. This feature is not enabled by default. Specifying ! '-mno-long-calls' restores the default behavior. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers. ! '-mfast-fp' ! Link with the fast floating-point library. This library relaxes some of the IEEE floating-point standard's rules for checking inputs against Not-a-Number (NAN), in the interest of performance. ! '-minline-plt' Enable inlining of PLT entries in function calls to functions that ! are not known to bind locally. It has no effect without '-mfdpic'. ! '-mmulticore' Build a standalone application for multicore Blackfin processors. This option causes proper start files and link scripts supporting ! multicore to be used, and defines the macro '__BFIN_MULTICORE'. It ! can only be used with '-mcpu=bf561[-SIREVISION]'. ! This option can be used with '-mcorea' or '-mcoreb', which selects ! the one-application-per-core programming model. Without '-mcorea' ! or '-mcoreb', the single-application/dual-core programming model is ! used. In this model, the main function of Core B should be named ! as 'coreb_main'. If this option is not used, the single-core application programming model is used. ! '-mcorea' Build a standalone application for Core A of BF561 when using the ! one-application-per-core programming model. Proper start files and link scripts are used to support Core A, and the macro ! '__BFIN_COREA' is defined. This option can only be used in ! conjunction with '-mmulticore'. ! '-mcoreb' Build a standalone application for Core B of BF561 when using the ! one-application-per-core programming model. Proper start files and link scripts are used to support Core B, and the macro ! '__BFIN_COREB' is defined. When this option is used, 'coreb_main' ! should be used instead of 'main'. This option can only be used in ! conjunction with '-mmulticore'. ! '-msdram' Build a standalone application for SDRAM. Proper start files and link scripts are used to put the application into SDRAM, and the ! macro '__BFIN_SDRAM' is defined. The loader should initialize SDRAM before loading the application. ! '-micplb' Assume that ICPLBs are enabled at run time. This has an effect on certain anomaly workarounds. For Linux targets, the default is to assume ICPLBs are enabled; for standalone applications the default --- 14385,14440 ---- offset-based version of subroutine call instruction. This feature is not enabled by default. Specifying ! `-mno-long-calls' restores the default behavior. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers. ! `-mfast-fp' ! Link with the fast floating-point library. This library relaxes some of the IEEE floating-point standard's rules for checking inputs against Not-a-Number (NAN), in the interest of performance. ! `-minline-plt' Enable inlining of PLT entries in function calls to functions that ! are not known to bind locally. It has no effect without `-mfdpic'. ! `-mmulticore' Build a standalone application for multicore Blackfin processors. This option causes proper start files and link scripts supporting ! multicore to be used, and defines the macro `__BFIN_MULTICORE'. ! It can only be used with `-mcpu=bf561[-SIREVISION]'. ! This option can be used with `-mcorea' or `-mcoreb', which selects ! the one-application-per-core programming model. Without `-mcorea' ! or `-mcoreb', the single-application/dual-core programming model ! is used. In this model, the main function of Core B should be ! named as `coreb_main'. If this option is not used, the single-core application programming model is used. ! `-mcorea' Build a standalone application for Core A of BF561 when using the ! one-application-per-core programming model. Proper start files and link scripts are used to support Core A, and the macro ! `__BFIN_COREA' is defined. This option can only be used in ! conjunction with `-mmulticore'. ! `-mcoreb' Build a standalone application for Core B of BF561 when using the ! one-application-per-core programming model. Proper start files and link scripts are used to support Core B, and the macro ! `__BFIN_COREB' is defined. When this option is used, `coreb_main' ! should be used instead of `main'. This option can only be used in ! conjunction with `-mmulticore'. ! `-msdram' Build a standalone application for SDRAM. Proper start files and link scripts are used to put the application into SDRAM, and the ! macro `__BFIN_SDRAM' is defined. The loader should initialize SDRAM before loading the application. ! `-micplb' Assume that ICPLBs are enabled at run time. This has an effect on certain anomaly workarounds. For Linux targets, the default is to assume ICPLBs are enabled; for standalone applications the default *************** File: gcc.info, Node: C6X Options, Nex *** 14324,14363 **** 3.18.7 C6X Options ------------------ ! '-march=NAME' This specifies the name of the target architecture. GCC uses this name to determine what kind of instructions it can emit when ! generating assembly code. Permissible names are: 'c62x', 'c64x', ! 'c64x+', 'c67x', 'c67x+', 'c674x'. ! '-mbig-endian' Generate code for a big-endian target. ! '-mlittle-endian' Generate code for a little-endian target. This is the default. ! '-msim' Choose startup files and linker script suitable for the simulator. ! '-msdata=default' ! Put small global and static data in the '.neardata' section, which ! is pointed to by register 'B14'. Put small uninitialized global ! and static data in the '.bss' section, which is adjacent to the ! '.neardata' section. Put small read-only data into the '.rodata' section. The corresponding sections used for large pieces of data ! are '.fardata', '.far' and '.const'. ! '-msdata=all' Put all data, not just small objects, into the sections reserved ! for small data, and use addressing relative to the 'B14' register to access them. ! '-msdata=none' Make no use of the sections reserved for small data, and use absolute addresses to access all data. Put all initialized global ! and static data in the '.fardata' section, and all uninitialized ! data in the '.far' section. Put all constant data into the ! '.const' section.  File: gcc.info, Node: CRIS Options, Next: CR16 Options, Prev: C6X Options, Up: Submodel Options --- 14446,14485 ---- 3.18.7 C6X Options ------------------ ! `-march=NAME' This specifies the name of the target architecture. GCC uses this name to determine what kind of instructions it can emit when ! generating assembly code. Permissible names are: `c62x', `c64x', ! `c64x+', `c67x', `c67x+', `c674x'. ! `-mbig-endian' Generate code for a big-endian target. ! `-mlittle-endian' Generate code for a little-endian target. This is the default. ! `-msim' Choose startup files and linker script suitable for the simulator. ! `-msdata=default' ! Put small global and static data in the `.neardata' section, which ! is pointed to by register `B14'. Put small uninitialized global ! and static data in the `.bss' section, which is adjacent to the ! `.neardata' section. Put small read-only data into the `.rodata' section. The corresponding sections used for large pieces of data ! are `.fardata', `.far' and `.const'. ! `-msdata=all' Put all data, not just small objects, into the sections reserved ! for small data, and use addressing relative to the `B14' register to access them. ! `-msdata=none' Make no use of the sections reserved for small data, and use absolute addresses to access all data. Put all initialized global ! and static data in the `.fardata' section, and all uninitialized ! data in the `.far' section. Put all constant data into the ! `.const' section.  File: gcc.info, Node: CRIS Options, Next: CR16 Options, Prev: C6X Options, Up: Submodel Options *************** File: gcc.info, Node: CRIS Options, Ne *** 14367,14465 **** These options are defined specifically for the CRIS ports. ! '-march=ARCHITECTURE-TYPE' ! '-mcpu=ARCHITECTURE-TYPE' Generate code for the specified architecture. The choices for ! ARCHITECTURE-TYPE are 'v3', 'v8' and 'v10' for respectively ! ETRAX 4, ETRAX 100, and ETRAX 100 LX. Default is 'v0' except for ! cris-axis-linux-gnu, where the default is 'v10'. ! '-mtune=ARCHITECTURE-TYPE' Tune to ARCHITECTURE-TYPE everything applicable about the generated code, except for the ABI and the set of available instructions. The choices for ARCHITECTURE-TYPE are the same as for ! '-march=ARCHITECTURE-TYPE'. ! '-mmax-stack-frame=N' Warn when the stack frame of a function exceeds N bytes. ! '-metrax4' ! '-metrax100' ! The options '-metrax4' and '-metrax100' are synonyms for ! '-march=v3' and '-march=v8' respectively. ! '-mmul-bug-workaround' ! '-mno-mul-bug-workaround' ! Work around a bug in the 'muls' and 'mulu' instructions for CPU models where it applies. This option is active by default. ! '-mpdebug' Enable CRIS-specific verbose debug-related information in the assembly code. This option also has the effect of turning off the ! '#NO_APP' formatted-code indicator to the assembler at the beginning of the assembly file. ! '-mcc-init' ! Do not use condition-code results from previous instruction; always ! emit compare and test instructions before use of condition codes. ! '-mno-side-effects' Do not emit instructions with side effects in addressing modes other than post-increment. ! '-mstack-align' ! '-mno-stack-align' ! '-mdata-align' ! '-mno-data-align' ! '-mconst-align' ! '-mno-const-align' ! These options ('no-' options) arrange (eliminate arrangements) for the stack frame, individual data and constants to be aligned for the maximum single data access size for the chosen CPU model. The default is to arrange for 32-bit alignment. ABI details such as structure layout are not affected by these options. ! '-m32-bit' ! '-m16-bit' ! '-m8-bit' Similar to the stack- data- and const-align options above, these ! options arrange for stack frame, writable data and constants to all ! be 32-bit, 16-bit or 8-bit aligned. The default is 32-bit alignment. ! '-mno-prologue-epilogue' ! '-mprologue-epilogue' ! With '-mno-prologue-epilogue', the normal function prologue and epilogue which set up the stack frame are omitted and no return instructions or return sequences are generated in the code. Use this option only together with visual inspection of the compiled ! code: no warnings or errors are generated when call-saved registers ! must be saved, or storage for local variables needs to be ! allocated. ! '-mno-gotplt' ! '-mgotplt' ! With '-fpic' and '-fPIC', don't generate (do generate) instruction sequences that load addresses for functions from the PLT part of the GOT rather than (traditional on other architectures) calls to ! the PLT. The default is '-mgotplt'. ! '-melf' Legacy no-op option only recognized with the cris-axis-elf and cris-axis-linux-gnu targets. ! '-mlinux' Legacy no-op option only recognized with the cris-axis-linux-gnu target. ! '-sim' This option, recognized for the cris-axis-elf, arranges to link with input-output functions from a simulator library. Code, initialized data and zero-initialized data are allocated consecutively. ! '-sim2' ! Like '-sim', but pass linker options to locate initialized data at 0x40000000 and zero-initialized data at 0x80000000.  --- 14489,14588 ---- These options are defined specifically for the CRIS ports. ! `-march=ARCHITECTURE-TYPE' ! `-mcpu=ARCHITECTURE-TYPE' Generate code for the specified architecture. The choices for ! ARCHITECTURE-TYPE are `v3', `v8' and `v10' for respectively ! ETRAX 4, ETRAX 100, and ETRAX 100 LX. Default is `v0' except for ! cris-axis-linux-gnu, where the default is `v10'. ! `-mtune=ARCHITECTURE-TYPE' Tune to ARCHITECTURE-TYPE everything applicable about the generated code, except for the ABI and the set of available instructions. The choices for ARCHITECTURE-TYPE are the same as for ! `-march=ARCHITECTURE-TYPE'. ! `-mmax-stack-frame=N' Warn when the stack frame of a function exceeds N bytes. ! `-metrax4' ! `-metrax100' ! The options `-metrax4' and `-metrax100' are synonyms for ! `-march=v3' and `-march=v8' respectively. ! `-mmul-bug-workaround' ! `-mno-mul-bug-workaround' ! Work around a bug in the `muls' and `mulu' instructions for CPU models where it applies. This option is active by default. ! `-mpdebug' Enable CRIS-specific verbose debug-related information in the assembly code. This option also has the effect of turning off the ! `#NO_APP' formatted-code indicator to the assembler at the beginning of the assembly file. ! `-mcc-init' ! Do not use condition-code results from previous instruction; ! always emit compare and test instructions before use of condition ! codes. ! `-mno-side-effects' Do not emit instructions with side effects in addressing modes other than post-increment. ! `-mstack-align' ! `-mno-stack-align' ! `-mdata-align' ! `-mno-data-align' ! `-mconst-align' ! `-mno-const-align' ! These options (`no-' options) arrange (eliminate arrangements) for the stack frame, individual data and constants to be aligned for the maximum single data access size for the chosen CPU model. The default is to arrange for 32-bit alignment. ABI details such as structure layout are not affected by these options. ! `-m32-bit' ! `-m16-bit' ! `-m8-bit' Similar to the stack- data- and const-align options above, these ! options arrange for stack frame, writable data and constants to ! all be 32-bit, 16-bit or 8-bit aligned. The default is 32-bit alignment. ! `-mno-prologue-epilogue' ! `-mprologue-epilogue' ! With `-mno-prologue-epilogue', the normal function prologue and epilogue which set up the stack frame are omitted and no return instructions or return sequences are generated in the code. Use this option only together with visual inspection of the compiled ! code: no warnings or errors are generated when call-saved ! registers must be saved, or storage for local variables needs to ! be allocated. ! `-mno-gotplt' ! `-mgotplt' ! With `-fpic' and `-fPIC', don't generate (do generate) instruction sequences that load addresses for functions from the PLT part of the GOT rather than (traditional on other architectures) calls to ! the PLT. The default is `-mgotplt'. ! `-melf' Legacy no-op option only recognized with the cris-axis-elf and cris-axis-linux-gnu targets. ! `-mlinux' Legacy no-op option only recognized with the cris-axis-linux-gnu target. ! `-sim' This option, recognized for the cris-axis-elf, arranges to link with input-output functions from a simulator library. Code, initialized data and zero-initialized data are allocated consecutively. ! `-sim2' ! Like `-sim', but pass linker options to locate initialized data at 0x40000000 and zero-initialized data at 0x80000000.  *************** File: gcc.info, Node: CR16 Options, Ne *** 14470,14498 **** These options are defined specifically for the CR16 ports. ! '-mmac' ! Enable the use of multiply-accumulate instructions. Disabled by default. ! '-mcr16cplus' ! '-mcr16c' ! Generate code for CR16C or CR16C+ architecture. CR16C+ ! architecture is default. ! '-msim' Links the library libsim.a which is in compatible with simulator. Applicable to ELF compiler only. ! '-mint32' Choose integer type as 32-bit wide. ! '-mbit-ops' ! Generates 'sbit'/'cbit' instructions for bit manipulations. ! '-mdata-model=MODEL' ! Choose a data model. The choices for MODEL are 'near', 'far' or ! 'medium'. 'medium' is default. However, 'far' is not valid with ! '-mcr16c', as the CR16C architecture does not support the far data model.  --- 14593,14621 ---- These options are defined specifically for the CR16 ports. ! `-mmac' ! Enable the use of multiply-accumulate instructions. Disabled by default. ! `-mcr16cplus' ! `-mcr16c' ! Generate code for CR16C or CR16C+ architecture. CR16C+ architecture ! is default. ! `-msim' Links the library libsim.a which is in compatible with simulator. Applicable to ELF compiler only. ! `-mint32' Choose integer type as 32-bit wide. ! `-mbit-ops' ! Generates `sbit'/`cbit' instructions for bit manipulations. ! `-mdata-model=MODEL' ! Choose a data model. The choices for MODEL are `near', `far' or ! `medium'. `medium' is default. However, `far' is not valid with ! `-mcr16c', as the CR16C architecture does not support the far data model.  *************** operating system. *** 14506,14544 **** FSF GCC on Darwin does not create "fat" object files; it creates an object file for the single architecture that GCC was built to target. ! Apple's GCC on Darwin does create "fat" files if multiple '-arch' options are used; it does so by running the compiler or linker multiple ! times and joining the results together with 'lipo'. ! The subtype of the file created (like 'ppc7400' or 'ppc970' or 'i686') is determined by the flags that specify the ISA that GCC is targeting, ! like '-mcpu' or '-march'. The '-force_cpusubtype_ALL' option can be used to override this. The Darwin tools vary in their behavior when presented with an ISA ! mismatch. The assembler, 'as', only permits instructions to be used that are valid for the subtype of the file it is generating, so you ! cannot put 64-bit instructions in a 'ppc750' object file. The linker ! for shared libraries, '/usr/bin/libtool', fails and prints an error if asked to create a shared library with a less restrictive subtype than ! its input files (for instance, trying to put a 'ppc970' object file in a ! 'ppc7400' library). The linker for executables, 'ld', quietly gives the ! executable the most restrictive subtype of any of its input files. ! '-FDIR' Add the framework directory DIR to the head of the list of directories to be searched for header files. These directories are ! interleaved with those specified by '-I' options and are scanned in ! a left-to-right order. A framework directory is a directory with frameworks in it. A ! framework is a directory with a 'Headers' and/or 'PrivateHeaders' ! directory contained directly in it that ends in '.framework'. The name of a framework is the name of this directory excluding the ! '.framework'. Headers associated with the framework are found in ! one of those two directories, with 'Headers' being searched first. A subframework is a framework directory that is in a framework's ! 'Frameworks' directory. Includes of subframework headers can only appear in a header of a framework that contains the subframework, or in a sibling subframework header. Two subframeworks are siblings if they occur in the same framework. A subframework --- 14629,14667 ---- FSF GCC on Darwin does not create "fat" object files; it creates an object file for the single architecture that GCC was built to target. ! Apple's GCC on Darwin does create "fat" files if multiple `-arch' options are used; it does so by running the compiler or linker multiple ! times and joining the results together with `lipo'. ! The subtype of the file created (like `ppc7400' or `ppc970' or `i686') is determined by the flags that specify the ISA that GCC is targeting, ! like `-mcpu' or `-march'. The `-force_cpusubtype_ALL' option can be used to override this. The Darwin tools vary in their behavior when presented with an ISA ! mismatch. The assembler, `as', only permits instructions to be used that are valid for the subtype of the file it is generating, so you ! cannot put 64-bit instructions in a `ppc750' object file. The linker ! for shared libraries, `/usr/bin/libtool', fails and prints an error if asked to create a shared library with a less restrictive subtype than ! its input files (for instance, trying to put a `ppc970' object file in ! a `ppc7400' library). The linker for executables, `ld', quietly gives ! the executable the most restrictive subtype of any of its input files. ! `-FDIR' Add the framework directory DIR to the head of the list of directories to be searched for header files. These directories are ! interleaved with those specified by `-I' options and are scanned ! in a left-to-right order. A framework directory is a directory with frameworks in it. A ! framework is a directory with a `Headers' and/or `PrivateHeaders' ! directory contained directly in it that ends in `.framework'. The name of a framework is the name of this directory excluding the ! `.framework'. Headers associated with the framework are found in ! one of those two directories, with `Headers' being searched first. A subframework is a framework directory that is in a framework's ! `Frameworks' directory. Includes of subframework headers can only appear in a header of a framework that contains the subframework, or in a sibling subframework header. Two subframeworks are siblings if they occur in the same framework. A subframework *************** executable the most restrictive subtype *** 14546,14696 **** if this is violated. Currently a subframework cannot have subframeworks; in the future, the mechanism may be extended to support this. The standard frameworks can be found in ! '/System/Library/Frameworks' and '/Library/Frameworks'. An example ! include looks like '#include ', where ! 'Framework' denotes the name of the framework and 'header.h' is ! found in the 'PrivateHeaders' or 'Headers' directory. ! '-iframeworkDIR' ! Like '-F' except the directory is a treated as a system directory. ! The main difference between this '-iframework' and '-F' is that ! with '-iframework' the compiler does not warn about constructs contained within header files found via DIR. This option is valid only for the C family of languages. ! '-gused' Emit debugging information for symbols that are used. For stabs ! debugging format, this enables '-feliminate-unused-debug-symbols'. This is by default ON. ! '-gfull' Emit debugging information for all symbols and types. ! '-mmacosx-version-min=VERSION' ! The earliest version of MacOS X that this executable will run on is ! VERSION. Typical values of VERSION include '10.1', '10.2', and ! '10.3.9'. If the compiler was built to use the system's headers by default, then the default for this option is the system version on which the compiler is running, otherwise the default is to make choices that are compatible with as many systems and code bases as possible. ! '-mkernel' ! Enable kernel development mode. The '-mkernel' option sets ! '-static', '-fno-common', '-fno-use-cxa-atexit', '-fno-exceptions', ! '-fno-non-call-exceptions', '-fapple-kext', '-fno-weak' and ! '-fno-rtti' where applicable. This mode also sets '-mno-altivec', ! '-msoft-float', '-fno-builtin' and '-mlong-branch' for PowerPC ! targets. ! '-mone-byte-bool' ! Override the defaults for 'bool' so that 'sizeof(bool)==1'. By ! default 'sizeof(bool)' is '4' when compiling for Darwin/PowerPC and ! '1' when compiling for Darwin/x86, so this option has no effect on ! x86. ! *Warning:* The '-mone-byte-bool' switch causes GCC to generate code ! that is not binary compatible with code generated without that ! switch. Using this switch may require recompiling all other modules in a program, including system libraries. Use this switch to conform to a non-default data model. ! '-mfix-and-continue' ! '-ffix-and-continue' ! '-findirect-data' Generate code suitable for fast turnaround development, such as to ! allow GDB to dynamically load '.o' files into already-running ! programs. '-findirect-data' and '-ffix-and-continue' are provided for backwards compatibility. ! '-all_load' Loads all members of static archive libraries. See man ld(1) for more information. ! '-arch_errors_fatal' Cause the errors having to do with files that have the wrong architecture to be fatal. ! '-bind_at_load' Causes the output file to be marked such that the dynamic linker will bind all undefined references when the file is loaded or launched. ! '-bundle' Produce a Mach-o bundle format file. See man ld(1) for more information. ! '-bundle_loader EXECUTABLE' This option specifies the EXECUTABLE that will load the build output file being linked. See man ld(1) for more information. ! '-dynamiclib' When passed this option, GCC produces a dynamic library instead of ! an executable when linking, using the Darwin 'libtool' command. ! '-force_cpusubtype_ALL' ! This causes GCC's output file to have the 'ALL' subtype, instead of ! one controlled by the '-mcpu' or '-march' option. ! '-allowable_client CLIENT_NAME' ! '-client_name' ! '-compatibility_version' ! '-current_version' ! '-dead_strip' ! '-dependency-file' ! '-dylib_file' ! '-dylinker_install_name' ! '-dynamic' ! '-exported_symbols_list' ! '-filelist' ! '-flat_namespace' ! '-force_flat_namespace' ! '-headerpad_max_install_names' ! '-image_base' ! '-init' ! '-install_name' ! '-keep_private_externs' ! '-multi_module' ! '-multiply_defined' ! '-multiply_defined_unused' ! '-noall_load' ! '-no_dead_strip_inits_and_terms' ! '-nofixprebinding' ! '-nomultidefs' ! '-noprebind' ! '-noseglinkedit' ! '-pagezero_size' ! '-prebind' ! '-prebind_all_twolevel_modules' ! '-private_bundle' ! '-read_only_relocs' ! '-sectalign' ! '-sectobjectsymbols' ! '-whyload' ! '-seg1addr' ! '-sectcreate' ! '-sectobjectsymbols' ! '-sectorder' ! '-segaddr' ! '-segs_read_only_addr' ! '-segs_read_write_addr' ! '-seg_addr_table' ! '-seg_addr_table_filename' ! '-seglinkedit' ! '-segprot' ! '-segs_read_only_addr' ! '-segs_read_write_addr' ! '-single_module' ! '-static' ! '-sub_library' ! '-sub_umbrella' ! '-twolevel_namespace' ! '-umbrella' ! '-undefined' ! '-unexported_symbols_list' ! '-weak_reference_mismatches' ! '-whatsloaded' These options are passed to the Darwin linker. The Darwin linker man page describes them in detail. --- 14669,14819 ---- if this is violated. Currently a subframework cannot have subframeworks; in the future, the mechanism may be extended to support this. The standard frameworks can be found in ! `/System/Library/Frameworks' and `/Library/Frameworks'. An ! example include looks like `#include ', where ! `Framework' denotes the name of the framework and `header.h' is ! found in the `PrivateHeaders' or `Headers' directory. ! `-iframeworkDIR' ! Like `-F' except the directory is a treated as a system directory. ! The main difference between this `-iframework' and `-F' is that ! with `-iframework' the compiler does not warn about constructs contained within header files found via DIR. This option is valid only for the C family of languages. ! `-gused' Emit debugging information for symbols that are used. For stabs ! debugging format, this enables `-feliminate-unused-debug-symbols'. This is by default ON. ! `-gfull' Emit debugging information for all symbols and types. ! `-mmacosx-version-min=VERSION' ! The earliest version of MacOS X that this executable will run on ! is VERSION. Typical values of VERSION include `10.1', `10.2', and ! `10.3.9'. If the compiler was built to use the system's headers by default, then the default for this option is the system version on which the compiler is running, otherwise the default is to make choices that are compatible with as many systems and code bases as possible. ! `-mkernel' ! Enable kernel development mode. The `-mkernel' option sets ! `-static', `-fno-common', `-fno-use-cxa-atexit', ! `-fno-exceptions', `-fno-non-call-exceptions', `-fapple-kext', ! `-fno-weak' and `-fno-rtti' where applicable. This mode also sets ! `-mno-altivec', `-msoft-float', `-fno-builtin' and `-mlong-branch' ! for PowerPC targets. ! `-mone-byte-bool' ! Override the defaults for `bool' so that `sizeof(bool)==1'. By ! default `sizeof(bool)' is `4' when compiling for Darwin/PowerPC ! and `1' when compiling for Darwin/x86, so this option has no ! effect on x86. ! *Warning:* The `-mone-byte-bool' switch causes GCC to generate ! code that is not binary compatible with code generated without ! that switch. Using this switch may require recompiling all other modules in a program, including system libraries. Use this switch to conform to a non-default data model. ! `-mfix-and-continue' ! `-ffix-and-continue' ! `-findirect-data' Generate code suitable for fast turnaround development, such as to ! allow GDB to dynamically load `.o' files into already-running ! programs. `-findirect-data' and `-ffix-and-continue' are provided for backwards compatibility. ! `-all_load' Loads all members of static archive libraries. See man ld(1) for more information. ! `-arch_errors_fatal' Cause the errors having to do with files that have the wrong architecture to be fatal. ! `-bind_at_load' Causes the output file to be marked such that the dynamic linker will bind all undefined references when the file is loaded or launched. ! `-bundle' Produce a Mach-o bundle format file. See man ld(1) for more information. ! `-bundle_loader EXECUTABLE' This option specifies the EXECUTABLE that will load the build output file being linked. See man ld(1) for more information. ! `-dynamiclib' When passed this option, GCC produces a dynamic library instead of ! an executable when linking, using the Darwin `libtool' command. ! `-force_cpusubtype_ALL' ! This causes GCC's output file to have the `ALL' subtype, instead of ! one controlled by the `-mcpu' or `-march' option. ! `-allowable_client CLIENT_NAME' ! `-client_name' ! `-compatibility_version' ! `-current_version' ! `-dead_strip' ! `-dependency-file' ! `-dylib_file' ! `-dylinker_install_name' ! `-dynamic' ! `-exported_symbols_list' ! `-filelist' ! `-flat_namespace' ! `-force_flat_namespace' ! `-headerpad_max_install_names' ! `-image_base' ! `-init' ! `-install_name' ! `-keep_private_externs' ! `-multi_module' ! `-multiply_defined' ! `-multiply_defined_unused' ! `-noall_load' ! `-no_dead_strip_inits_and_terms' ! `-nofixprebinding' ! `-nomultidefs' ! `-noprebind' ! `-noseglinkedit' ! `-pagezero_size' ! `-prebind' ! `-prebind_all_twolevel_modules' ! `-private_bundle' ! `-read_only_relocs' ! `-sectalign' ! `-sectobjectsymbols' ! `-whyload' ! `-seg1addr' ! `-sectcreate' ! `-sectobjectsymbols' ! `-sectorder' ! `-segaddr' ! `-segs_read_only_addr' ! `-segs_read_write_addr' ! `-seg_addr_table' ! `-seg_addr_table_filename' ! `-seglinkedit' ! `-segprot' ! `-segs_read_only_addr' ! `-segs_read_write_addr' ! `-single_module' ! `-static' ! `-sub_library' ! `-sub_umbrella' ! `-twolevel_namespace' ! `-umbrella' ! `-undefined' ! `-unexported_symbols_list' ! `-weak_reference_mismatches' ! `-whatsloaded' These options are passed to the Darwin linker. The Darwin linker man page describes them in detail. *************** File: gcc.info, Node: DEC Alpha Options *** 14700,14842 **** 3.18.11 DEC Alpha Options ------------------------- ! These '-m' options are defined for the DEC Alpha implementations: ! '-mno-soft-float' ! '-msoft-float' Use (do not use) the hardware floating-point instructions for ! floating-point operations. When '-msoft-float' is specified, ! functions in 'libgcc.a' are used to perform floating-point operations. Unless they are replaced by routines that emulate the floating-point operations, or compiled in such a way as to call such emulations routines, these routines issue floating-point ! operations. If you are compiling for an Alpha without floating-point operations, you must ensure that the library is built so as not to call them. Note that Alpha implementations without floating-point operations are required to have floating-point registers. ! '-mfp-reg' ! '-mno-fp-regs' Generate code that uses (does not use) the floating-point register ! set. '-mno-fp-regs' implies '-msoft-float'. If the floating-point register set is not used, floating-point operands are passed in integer registers as if they were integers and floating-point ! results are passed in '$0' instead of '$f0'. This is a non-standard calling sequence, so any function with a floating-point argument or return value called by code compiled ! with '-mno-fp-regs' must also be compiled with that option. A typical use of this option is building a kernel that does not use, and hence need not save and restore, any floating-point registers. ! '-mieee' ! The Alpha architecture implements floating-point hardware optimized ! for maximum performance. It is mostly compliant with the IEEE ! floating-point standard. However, for full compliance, software ! assistance is required. This option generates code fully IEEE-compliant code _except_ that the INEXACT-FLAG is not maintained (see below). If this option is turned on, the ! preprocessor macro '_IEEE_FP' is defined during compilation. The resulting code is less efficient but is able to correctly support denormalized numbers and exceptional IEEE values such as not-a-number and plus/minus infinity. Other Alpha compilers call ! this option '-ieee_with_no_inexact'. ! '-mieee-with-inexact' ! This is like '-mieee' except the generated code also maintains the IEEE INEXACT-FLAG. Turning on this option causes the generated code to implement fully-compliant IEEE math. In addition to ! '_IEEE_FP', '_IEEE_FP_EXACT' is defined as a preprocessor macro. On some Alpha implementations the resulting code may execute significantly slower than the code generated by default. Since there is very little code that depends on the INEXACT-FLAG, you should normally not specify this option. Other Alpha compilers ! call this option '-ieee_with_inexact'. ! '-mfp-trap-mode=TRAP-MODE' This option controls what floating-point related traps are enabled. ! Other Alpha compilers call this option '-fptm TRAP-MODE'. The trap ! mode can be set to one of four values: ! 'n' ! This is the default (normal) setting. The only traps that are ! enabled are the ones that cannot be disabled in software (e.g., division by zero trap). ! 'u' ! In addition to the traps enabled by 'n', underflow traps are enabled as well. ! 'su' ! Like 'u', but the instructions are marked to be safe for software completion (see Alpha architecture manual for details). ! 'sui' ! Like 'su', but inexact traps are enabled as well. ! '-mfp-rounding-mode=ROUNDING-MODE' Selects the IEEE rounding mode. Other Alpha compilers call this ! option '-fprm ROUNDING-MODE'. The ROUNDING-MODE can be one of: ! 'n' ! Normal IEEE rounding mode. Floating-point numbers are rounded ! towards the nearest machine number or towards the even machine ! number in case of a tie. ! 'm' Round towards minus infinity. ! 'c' Chopped rounding mode. Floating-point numbers are rounded towards zero. ! 'd' Dynamic rounding mode. A field in the floating-point control register (FPCR, see Alpha architecture reference manual) controls the rounding mode in effect. The C library initializes this register for rounding towards plus infinity. ! Thus, unless your program modifies the FPCR, 'd' corresponds to round towards plus infinity. ! '-mtrap-precision=TRAP-PRECISION' In the Alpha architecture, floating-point traps are imprecise. This means without software assistance it is impossible to recover from a floating trap and program execution normally needs to be ! terminated. GCC can generate code that can assist operating system ! trap handlers in determining the exact location that caused a ! floating-point trap. Depending on the requirements of an application, different levels of precisions can be selected: ! 'p' Program precision. This option is the default and means a trap handler can only identify which program caused a floating-point exception. ! 'f' Function precision. The trap handler can determine the function that caused a floating-point exception. ! 'i' Instruction precision. The trap handler can determine the exact instruction that caused a floating-point exception. Other Alpha compilers provide the equivalent options called ! '-scope_safe' and '-resumption_safe'. ! '-mieee-conformant' This option marks the generated code as IEEE conformant. You must ! not use this option unless you also specify '-mtrap-precision=i' ! and either '-mfp-trap-mode=su' or '-mfp-trap-mode=sui'. Its only ! effect is to emit the line '.eflag 48' in the function prologue of the generated assembly file. ! '-mbuild-constants' ! Normally GCC examines a 32- or 64-bit integer constant to see if it ! can construct it from smaller constants in two or three instructions. If it cannot, it outputs the constant as a literal and generates code to load it from the data segment at run time. --- 14823,14965 ---- 3.18.11 DEC Alpha Options ------------------------- ! These `-m' options are defined for the DEC Alpha implementations: ! `-mno-soft-float' ! `-msoft-float' Use (do not use) the hardware floating-point instructions for ! floating-point operations. When `-msoft-float' is specified, ! functions in `libgcc.a' are used to perform floating-point operations. Unless they are replaced by routines that emulate the floating-point operations, or compiled in such a way as to call such emulations routines, these routines issue floating-point ! operations. If you are compiling for an Alpha without floating-point operations, you must ensure that the library is built so as not to call them. Note that Alpha implementations without floating-point operations are required to have floating-point registers. ! `-mfp-reg' ! `-mno-fp-regs' Generate code that uses (does not use) the floating-point register ! set. `-mno-fp-regs' implies `-msoft-float'. If the floating-point register set is not used, floating-point operands are passed in integer registers as if they were integers and floating-point ! results are passed in `$0' instead of `$f0'. This is a non-standard calling sequence, so any function with a floating-point argument or return value called by code compiled ! with `-mno-fp-regs' must also be compiled with that option. A typical use of this option is building a kernel that does not use, and hence need not save and restore, any floating-point registers. ! `-mieee' ! The Alpha architecture implements floating-point hardware ! optimized for maximum performance. It is mostly compliant with ! the IEEE floating-point standard. However, for full compliance, ! software assistance is required. This option generates code fully IEEE-compliant code _except_ that the INEXACT-FLAG is not maintained (see below). If this option is turned on, the ! preprocessor macro `_IEEE_FP' is defined during compilation. The resulting code is less efficient but is able to correctly support denormalized numbers and exceptional IEEE values such as not-a-number and plus/minus infinity. Other Alpha compilers call ! this option `-ieee_with_no_inexact'. ! `-mieee-with-inexact' ! This is like `-mieee' except the generated code also maintains the IEEE INEXACT-FLAG. Turning on this option causes the generated code to implement fully-compliant IEEE math. In addition to ! `_IEEE_FP', `_IEEE_FP_EXACT' is defined as a preprocessor macro. On some Alpha implementations the resulting code may execute significantly slower than the code generated by default. Since there is very little code that depends on the INEXACT-FLAG, you should normally not specify this option. Other Alpha compilers ! call this option `-ieee_with_inexact'. ! `-mfp-trap-mode=TRAP-MODE' This option controls what floating-point related traps are enabled. ! Other Alpha compilers call this option `-fptm TRAP-MODE'. The ! trap mode can be set to one of four values: ! `n' ! This is the default (normal) setting. The only traps that ! are enabled are the ones that cannot be disabled in software (e.g., division by zero trap). ! `u' ! In addition to the traps enabled by `n', underflow traps are enabled as well. ! `su' ! Like `u', but the instructions are marked to be safe for software completion (see Alpha architecture manual for details). ! `sui' ! Like `su', but inexact traps are enabled as well. ! `-mfp-rounding-mode=ROUNDING-MODE' Selects the IEEE rounding mode. Other Alpha compilers call this ! option `-fprm ROUNDING-MODE'. The ROUNDING-MODE can be one of: ! `n' ! Normal IEEE rounding mode. Floating-point numbers are ! rounded towards the nearest machine number or towards the ! even machine number in case of a tie. ! `m' Round towards minus infinity. ! `c' Chopped rounding mode. Floating-point numbers are rounded towards zero. ! `d' Dynamic rounding mode. A field in the floating-point control register (FPCR, see Alpha architecture reference manual) controls the rounding mode in effect. The C library initializes this register for rounding towards plus infinity. ! Thus, unless your program modifies the FPCR, `d' corresponds to round towards plus infinity. ! `-mtrap-precision=TRAP-PRECISION' In the Alpha architecture, floating-point traps are imprecise. This means without software assistance it is impossible to recover from a floating trap and program execution normally needs to be ! terminated. GCC can generate code that can assist operating ! system trap handlers in determining the exact location that caused ! a floating-point trap. Depending on the requirements of an application, different levels of precisions can be selected: ! `p' Program precision. This option is the default and means a trap handler can only identify which program caused a floating-point exception. ! `f' Function precision. The trap handler can determine the function that caused a floating-point exception. ! `i' Instruction precision. The trap handler can determine the exact instruction that caused a floating-point exception. Other Alpha compilers provide the equivalent options called ! `-scope_safe' and `-resumption_safe'. ! `-mieee-conformant' This option marks the generated code as IEEE conformant. You must ! not use this option unless you also specify `-mtrap-precision=i' ! and either `-mfp-trap-mode=su' or `-mfp-trap-mode=sui'. Its only ! effect is to emit the line `.eflag 48' in the function prologue of the generated assembly file. ! `-mbuild-constants' ! Normally GCC examines a 32- or 64-bit integer constant to see if ! it can construct it from smaller constants in two or three instructions. If it cannot, it outputs the constant as a literal and generates code to load it from the data segment at run time. *************** These '-m' options are defined for the D *** 14849,14986 **** before it can find the variables and constants in its own data segment. ! '-mbwx' ! '-mno-bwx' ! '-mcix' ! '-mno-cix' ! '-mfix' ! '-mno-fix' ! '-mmax' ! '-mno-max' Indicate whether GCC should generate code to use the optional BWX, CIX, FIX and MAX instruction sets. The default is to use the ! instruction sets supported by the CPU type specified via '-mcpu=' option or that of the CPU on which GCC was built if none is specified. ! '-mfloat-vax' ! '-mfloat-ieee' Generate code that uses (does not use) VAX F and G floating-point arithmetic instead of IEEE single and double precision. ! '-mexplicit-relocs' ! '-mno-explicit-relocs' Older Alpha assemblers provided no way to generate symbol relocations except via assembler macros. Use of these macros does not allow optimal instruction scheduling. GNU binutils as of version 2.12 supports a new syntax that allows the compiler to explicitly mark which relocations should apply to which instructions. This option is mostly useful for debugging, as GCC ! detects the capabilities of the assembler when it is built and sets ! the default accordingly. ! '-msmall-data' ! '-mlarge-data' ! When '-mexplicit-relocs' is in effect, static data is accessed via ! "gp-relative" relocations. When '-msmall-data' is used, objects 8 bytes long or smaller are placed in a "small data area" (the ! '.sdata' and '.sbss' sections) and are accessed via 16-bit ! relocations off of the '$gp' register. This limits the size of the ! small data area to 64KB, but allows the variables to be directly ! accessed via a single instruction. ! The default is '-mlarge-data'. With this option the data area is limited to just below 2GB. Programs that require more than 2GB of ! data must use 'malloc' or 'mmap' to allocate the data in the heap instead of in the program's data segment. ! When generating code for shared libraries, '-fpic' implies ! '-msmall-data' and '-fPIC' implies '-mlarge-data'. ! '-msmall-text' ! '-mlarge-text' ! When '-msmall-text' is used, the compiler assumes that the code of the entire program (or shared library) fits in 4MB, and is thus ! reachable with a branch instruction. When '-msmall-data' is used, ! the compiler can assume that all local symbols share the same '$gp' ! value, and thus reduce the number of instructions required for a ! function call from 4 to 1. ! The default is '-mlarge-text'. ! '-mcpu=CPU_TYPE' Set the instruction set and instruction scheduling parameters for ! machine type CPU_TYPE. You can specify either the 'EV' style name or the corresponding chip number. GCC supports scheduling parameters for the EV4, EV5 and EV6 family of processors and chooses the default values for the instruction set from the ! processor you specify. If you do not specify a processor type, GCC ! defaults to the processor on which the compiler was built. Supported values for CPU_TYPE are ! 'ev4' ! 'ev45' ! '21064' Schedules as an EV4 and has no instruction set extensions. ! 'ev5' ! '21164' Schedules as an EV5 and has no instruction set extensions. ! 'ev56' ! '21164a' Schedules as an EV5 and supports the BWX extension. ! 'pca56' ! '21164pc' ! '21164PC' Schedules as an EV5 and supports the BWX and MAX extensions. ! 'ev6' ! '21264' Schedules as an EV6 and supports the BWX, FIX, and MAX extensions. ! 'ev67' ! '21264a' Schedules as an EV6 and supports the BWX, CIX, FIX, and MAX extensions. ! Native toolchains also support the value 'native', which selects the best architecture option for the host processor. ! '-mcpu=native' has no effect if GCC does not recognize the processor. ! '-mtune=CPU_TYPE' Set only the instruction scheduling parameters for machine type CPU_TYPE. The instruction set is not changed. ! Native toolchains also support the value 'native', which selects the best architecture option for the host processor. ! '-mtune=native' has no effect if GCC does not recognize the processor. ! '-mmemory-latency=TIME' Sets the latency the scheduler should assume for typical memory references as seen by the application. This number is highly ! dependent on the memory access patterns used by the application and ! the size of the external cache on the machine. Valid options for TIME are ! 'NUMBER' A decimal number representing clock cycles. ! 'L1' ! 'L2' ! 'L3' ! 'main' The compiler contains estimates of the number of clock cycles for "typical" EV4 & EV5 hardware for the Level 1, 2 & 3 caches (also called Dcache, Scache, and Bcache), as well as to main memory. Note that L3 is only valid for EV5.  File: gcc.info, Node: FR30 Options, Next: FT32 Options, Prev: DEC Alpha Options, Up: Submodel Options --- 14972,15110 ---- before it can find the variables and constants in its own data segment. ! `-mbwx' ! `-mno-bwx' ! `-mcix' ! `-mno-cix' ! `-mfix' ! `-mno-fix' ! `-mmax' ! `-mno-max' Indicate whether GCC should generate code to use the optional BWX, CIX, FIX and MAX instruction sets. The default is to use the ! instruction sets supported by the CPU type specified via `-mcpu=' option or that of the CPU on which GCC was built if none is specified. ! `-mfloat-vax' ! `-mfloat-ieee' Generate code that uses (does not use) VAX F and G floating-point arithmetic instead of IEEE single and double precision. ! `-mexplicit-relocs' ! `-mno-explicit-relocs' Older Alpha assemblers provided no way to generate symbol relocations except via assembler macros. Use of these macros does not allow optimal instruction scheduling. GNU binutils as of version 2.12 supports a new syntax that allows the compiler to explicitly mark which relocations should apply to which instructions. This option is mostly useful for debugging, as GCC ! detects the capabilities of the assembler when it is built and ! sets the default accordingly. ! `-msmall-data' ! `-mlarge-data' ! When `-mexplicit-relocs' is in effect, static data is accessed via ! "gp-relative" relocations. When `-msmall-data' is used, objects 8 bytes long or smaller are placed in a "small data area" (the ! `.sdata' and `.sbss' sections) and are accessed via 16-bit ! relocations off of the `$gp' register. This limits the size of ! the small data area to 64KB, but allows the variables to be ! directly accessed via a single instruction. ! The default is `-mlarge-data'. With this option the data area is limited to just below 2GB. Programs that require more than 2GB of ! data must use `malloc' or `mmap' to allocate the data in the heap instead of in the program's data segment. ! When generating code for shared libraries, `-fpic' implies ! `-msmall-data' and `-fPIC' implies `-mlarge-data'. ! `-msmall-text' ! `-mlarge-text' ! When `-msmall-text' is used, the compiler assumes that the code of the entire program (or shared library) fits in 4MB, and is thus ! reachable with a branch instruction. When `-msmall-data' is used, ! the compiler can assume that all local symbols share the same ! `$gp' value, and thus reduce the number of instructions required ! for a function call from 4 to 1. ! The default is `-mlarge-text'. ! `-mcpu=CPU_TYPE' Set the instruction set and instruction scheduling parameters for ! machine type CPU_TYPE. You can specify either the `EV' style name or the corresponding chip number. GCC supports scheduling parameters for the EV4, EV5 and EV6 family of processors and chooses the default values for the instruction set from the ! processor you specify. If you do not specify a processor type, ! GCC defaults to the processor on which the compiler was built. Supported values for CPU_TYPE are ! `ev4' ! `ev45' ! `21064' Schedules as an EV4 and has no instruction set extensions. ! `ev5' ! `21164' Schedules as an EV5 and has no instruction set extensions. ! `ev56' ! `21164a' Schedules as an EV5 and supports the BWX extension. ! `pca56' ! `21164pc' ! `21164PC' Schedules as an EV5 and supports the BWX and MAX extensions. ! `ev6' ! `21264' Schedules as an EV6 and supports the BWX, FIX, and MAX extensions. ! `ev67' ! `21264a' Schedules as an EV6 and supports the BWX, CIX, FIX, and MAX extensions. ! Native toolchains also support the value `native', which selects the best architecture option for the host processor. ! `-mcpu=native' has no effect if GCC does not recognize the processor. ! `-mtune=CPU_TYPE' Set only the instruction scheduling parameters for machine type CPU_TYPE. The instruction set is not changed. ! Native toolchains also support the value `native', which selects the best architecture option for the host processor. ! `-mtune=native' has no effect if GCC does not recognize the processor. ! `-mmemory-latency=TIME' Sets the latency the scheduler should assume for typical memory references as seen by the application. This number is highly ! dependent on the memory access patterns used by the application ! and the size of the external cache on the machine. Valid options for TIME are ! `NUMBER' A decimal number representing clock cycles. ! `L1' ! `L2' ! `L3' ! `main' The compiler contains estimates of the number of clock cycles for "typical" EV4 & EV5 hardware for the Level 1, 2 & 3 caches (also called Dcache, Scache, and Bcache), as well as to main memory. Note that L3 is only valid for EV5. +  File: gcc.info, Node: FR30 Options, Next: FT32 Options, Prev: DEC Alpha Options, Up: Submodel Options *************** File: gcc.info, Node: FR30 Options, Ne *** 14989,15004 **** These options are defined specifically for the FR30 port. ! '-msmall-model' Use the small address space model. This can produce smaller code, but it does assume that all symbolic values and addresses fit into a 20-bit range. ! '-mno-lsim' Assume that runtime support has been provided and so there is no ! need to include the simulator library ('libsim.a') on the linker command line.  File: gcc.info, Node: FT32 Options, Next: FRV Options, Prev: FR30 Options, Up: Submodel Options --- 15113,15129 ---- These options are defined specifically for the FR30 port. ! `-msmall-model' Use the small address space model. This can produce smaller code, but it does assume that all symbolic values and addresses fit into a 20-bit range. ! `-mno-lsim' Assume that runtime support has been provided and so there is no ! need to include the simulator library (`libsim.a') on the linker command line. +  File: gcc.info, Node: FT32 Options, Next: FRV Options, Prev: FR30 Options, Up: Submodel Options *************** File: gcc.info, Node: FT32 Options, Ne *** 15007,15288 **** These options are defined specifically for the FT32 port. ! '-msim' Specifies that the program will be run on the simulator. This causes an alternate runtime startup and library to be linked. You must not use this option when generating programs that will run on real hardware; you must provide your own runtime library for whatever I/O functions are needed. ! '-mlra' Enable Local Register Allocation. This is still experimental for FT32, so by default the compiler uses standard reload. ! '-mnodiv' Do not use div and mod instructions.  File: gcc.info, Node: FRV Options, Next: GNU/Linux Options, Prev: FT32 Options, Up: Submodel Options 3.18.14 FRV Options ------------------- ! '-mgpr-32' ! Only use the first 32 general-purpose registers. ! '-mgpr-64' ! Use all 64 general-purpose registers. ! '-mfpr-32' ! Use only the first 32 floating-point registers. ! '-mfpr-64' ! Use all 64 floating-point registers. ! '-mhard-float' ! Use hardware instructions for floating-point operations. ! '-msoft-float' ! Use library routines for floating-point operations. ! '-malloc-cc' ! Dynamically allocate condition code registers. ! '-mfixed-cc' ! Do not try to dynamically allocate condition code registers, only ! use 'icc0' and 'fcc0'. ! ! '-mdword' Change ABI to use double word insns. ! '-mno-dword' ! Do not use double word instructions. ! '-mdouble' ! Use floating-point double instructions. ! '-mno-double' ! Do not use floating-point double instructions. ! '-mmedia' ! Use media instructions. ! '-mno-media' ! Do not use media instructions. ! '-mmuladd' ! Use multiply and add/subtract instructions. ! '-mno-muladd' ! Do not use multiply and add/subtract instructions. ! '-mfdpic' ! Select the FDPIC ABI, which uses function descriptors to represent pointers to functions. Without any PIC/PIE-related options, it ! implies '-fPIE'. With '-fpic' or '-fpie', it assumes GOT entries ! and small data are within a 12-bit range from the GOT base address; ! with '-fPIC' or '-fPIE', GOT offsets are computed with 32 bits. ! With a 'bfin-elf' target, this option implies '-msim'. ! ! '-minline-plt' Enable inlining of PLT entries in function calls to functions that ! are not known to bind locally. It has no effect without '-mfdpic'. It's enabled by default if optimizing for speed and compiling for ! shared libraries (i.e., '-fPIC' or '-fpic'), or when an ! optimization option such as '-O3' or above is present in the command line. ! '-mTLS' ! Assume a large TLS segment when generating thread-local code. ! '-mtls' ! Do not assume a large TLS segment when generating thread-local code. ! '-mgprel-ro' ! ! Enable the use of 'GPREL' relocations in the FDPIC ABI for data that is known to be in read-only sections. It's enabled by ! default, except for '-fpic' or '-fpie': even though it may help make the global offset table smaller, it trades 1 instruction for ! 4. With '-fPIC' or '-fPIE', it trades 3 instructions for 4, one of ! which may be shared by multiple symbols, and it avoids the need for ! a GOT entry for the referenced symbol, so it's more likely to be a ! win. If it is not, '-mno-gprel-ro' can be used to disable it. ! ! '-multilib-library-pic' Link with the (library, not FD) pic libraries. It's implied by ! '-mlibrary-pic', as well as by '-fPIC' and '-fpic' without ! '-mfdpic'. You should never have to use it explicitly. ! ! '-mlinked-fp' Follow the EABI requirement of always creating a frame pointer whenever a stack frame is allocated. This option is enabled by ! default and can be disabled with '-mno-linked-fp'. ! ! '-mlong-calls' Use indirect addressing to call functions outside the current compilation unit. This allows the functions to be placed anywhere within the 32-bit address space. ! '-malign-labels' ! Try to align labels to an 8-byte boundary by inserting NOPs into the previous packet. This option only has an effect when VLIW packing is enabled. It doesn't create new packets; it merely adds NOPs to existing ones. ! '-mlibrary-pic' ! Generate position-independent EABI code. ! '-macc-4' ! Use only the first four media accumulator registers. ! '-macc-8' ! Use all eight media accumulator registers. ! '-mpack' ! Pack VLIW instructions. ! '-mno-pack' ! Do not pack VLIW instructions. ! '-mno-eflags' ! Do not mark ABI switches in e_flags. ! '-mcond-move' ! Enable the use of conditional-move instructions (default). ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mno-cond-move' Disable the use of conditional-move instructions. ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mscc' Enable the use of conditional set instructions (default). ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mno-scc' Disable the use of conditional set instructions. ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mcond-exec' Enable the use of conditional execution (default). ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mno-cond-exec' Disable the use of conditional execution. ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mvliw-branch' Run a pass to pack branches into VLIW instructions (default). ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mno-vliw-branch' Do not run a pass to pack branches into VLIW instructions. ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mmulti-cond-exec' ! Enable optimization of '&&' and '||' in conditional execution (default). ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mno-multi-cond-exec' ! ! Disable optimization of '&&' and '||' in conditional execution. ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! '-mnested-cond-exec' Enable nested conditional execution optimizations (default). ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-mno-nested-cond-exec' Disable nested conditional execution optimizations. ! This switch is mainly for debugging the compiler and will likely be ! removed in a future version. ! ! '-moptimize-membar' ! This switch removes redundant 'membar' instructions from the compiler-generated code. It is enabled by default. ! '-mno-optimize-membar' ! ! This switch disables the automatic removal of redundant 'membar' instructions from the generated code. ! '-mtomcat-stats' ! Cause gas to print out tomcat statistics. ! '-mcpu=CPU' ! Select the processor type for which to generate code. Possible ! values are 'frv', 'fr550', 'tomcat', 'fr500', 'fr450', 'fr405', ! 'fr400', 'fr300' and 'simple'.  File: gcc.info, Node: GNU/Linux Options, Next: H8/300 Options, Prev: FRV Options, Up: Submodel Options --- 15132,15368 ---- These options are defined specifically for the FT32 port. ! `-msim' Specifies that the program will be run on the simulator. This causes an alternate runtime startup and library to be linked. You must not use this option when generating programs that will run on real hardware; you must provide your own runtime library for whatever I/O functions are needed. ! `-mlra' Enable Local Register Allocation. This is still experimental for FT32, so by default the compiler uses standard reload. ! `-mnodiv' Do not use div and mod instructions. +  File: gcc.info, Node: FRV Options, Next: GNU/Linux Options, Prev: FT32 Options, Up: Submodel Options 3.18.14 FRV Options ------------------- ! `-mgpr-32' Only use the first 32 general-purpose registers. ! `-mgpr-64' Use all 64 general-purpose registers. ! `-mfpr-32' Use only the first 32 floating-point registers. ! `-mfpr-64' Use all 64 floating-point registers. ! `-mhard-float' Use hardware instructions for floating-point operations. ! `-msoft-float' Use library routines for floating-point operations. ! `-malloc-cc' Dynamically allocate condition code registers. ! `-mfixed-cc' Do not try to dynamically allocate condition code registers, only ! use `icc0' and `fcc0'. + `-mdword' Change ABI to use double word insns. ! `-mno-dword' Do not use double word instructions. ! `-mdouble' Use floating-point double instructions. ! `-mno-double' Do not use floating-point double instructions. ! `-mmedia' Use media instructions. ! `-mno-media' Do not use media instructions. ! `-mmuladd' Use multiply and add/subtract instructions. ! `-mno-muladd' Do not use multiply and add/subtract instructions. ! `-mfdpic' Select the FDPIC ABI, which uses function descriptors to represent pointers to functions. Without any PIC/PIE-related options, it ! implies `-fPIE'. With `-fpic' or `-fpie', it assumes GOT entries ! and small data are within a 12-bit range from the GOT base ! address; with `-fPIC' or `-fPIE', GOT offsets are computed with 32 ! bits. With a `bfin-elf' target, this option implies `-msim'. + `-minline-plt' Enable inlining of PLT entries in function calls to functions that ! are not known to bind locally. It has no effect without `-mfdpic'. It's enabled by default if optimizing for speed and compiling for ! shared libraries (i.e., `-fPIC' or `-fpic'), or when an ! optimization option such as `-O3' or above is present in the command line. ! `-mTLS' Assume a large TLS segment when generating thread-local code. ! `-mtls' Do not assume a large TLS segment when generating thread-local code. ! `-mgprel-ro' ! Enable the use of `GPREL' relocations in the FDPIC ABI for data that is known to be in read-only sections. It's enabled by ! default, except for `-fpic' or `-fpie': even though it may help make the global offset table smaller, it trades 1 instruction for ! 4. With `-fPIC' or `-fPIE', it trades 3 instructions for 4, one ! of which may be shared by multiple symbols, and it avoids the need ! for a GOT entry for the referenced symbol, so it's more likely to ! be a win. If it is not, `-mno-gprel-ro' can be used to disable it. + `-multilib-library-pic' Link with the (library, not FD) pic libraries. It's implied by ! `-mlibrary-pic', as well as by `-fPIC' and `-fpic' without ! `-mfdpic'. You should never have to use it explicitly. + `-mlinked-fp' Follow the EABI requirement of always creating a frame pointer whenever a stack frame is allocated. This option is enabled by ! default and can be disabled with `-mno-linked-fp'. + `-mlong-calls' Use indirect addressing to call functions outside the current compilation unit. This allows the functions to be placed anywhere within the 32-bit address space. ! `-malign-labels' Try to align labels to an 8-byte boundary by inserting NOPs into the previous packet. This option only has an effect when VLIW packing is enabled. It doesn't create new packets; it merely adds NOPs to existing ones. ! `-mlibrary-pic' Generate position-independent EABI code. ! `-macc-4' Use only the first four media accumulator registers. ! `-macc-8' Use all eight media accumulator registers. ! `-mpack' Pack VLIW instructions. ! `-mno-pack' Do not pack VLIW instructions. ! `-mno-eflags' Do not mark ABI switches in e_flags. ! `-mcond-move' Enable the use of conditional-move instructions (default). ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mno-cond-move' Disable the use of conditional-move instructions. ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mscc' Enable the use of conditional set instructions (default). ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mno-scc' Disable the use of conditional set instructions. ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mcond-exec' Enable the use of conditional execution (default). ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mno-cond-exec' Disable the use of conditional execution. ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mvliw-branch' Run a pass to pack branches into VLIW instructions (default). ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mno-vliw-branch' Do not run a pass to pack branches into VLIW instructions. ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. ! `-mmulti-cond-exec' ! Enable optimization of `&&' and `||' in conditional execution (default). ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. ! `-mno-multi-cond-exec' ! Disable optimization of `&&' and `||' in conditional execution. ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mnested-cond-exec' Enable nested conditional execution optimizations (default). ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. + `-mno-nested-cond-exec' Disable nested conditional execution optimizations. ! This switch is mainly for debugging the compiler and will likely ! be removed in a future version. ! `-moptimize-membar' ! This switch removes redundant `membar' instructions from the compiler-generated code. It is enabled by default. ! `-mno-optimize-membar' ! This switch disables the automatic removal of redundant `membar' instructions from the generated code. ! `-mtomcat-stats' Cause gas to print out tomcat statistics. ! `-mcpu=CPU' Select the processor type for which to generate code. Possible ! values are `frv', `fr550', `tomcat', `fr500', `fr450', `fr405', ! `fr400', `fr300' and `simple'. !  File: gcc.info, Node: GNU/Linux Options, Next: H8/300 Options, Prev: FRV Options, Up: Submodel Options *************** File: gcc.info, Node: GNU/Linux Options *** 15290,15376 **** 3.18.15 GNU/Linux Options ------------------------- ! These '-m' options are defined for GNU/Linux targets: ! '-mglibc' Use the GNU C library. This is the default except on ! '*-*-linux-*uclibc*', '*-*-linux-*musl*' and '*-*-linux-*android*' targets. ! '-muclibc' ! Use uClibc C library. This is the default on '*-*-linux-*uclibc*' targets. ! '-mmusl' ! Use the musl C library. This is the default on '*-*-linux-*musl*' targets. ! '-mbionic' ! Use Bionic C library. This is the default on '*-*-linux-*android*' ! targets. ! '-mandroid' ! Compile code compatible with Android platform. This is the default ! on '*-*-linux-*android*' targets. ! When compiling, this option enables '-mbionic', '-fPIC', ! '-fno-exceptions' and '-fno-rtti' by default. When linking, this option makes the GCC driver pass Android-specific options to the linker. Finally, this option causes the preprocessor macro ! '__ANDROID__' to be defined. ! '-tno-android-cc' ! Disable compilation effects of '-mandroid', i.e., do not enable ! '-mbionic', '-fPIC', '-fno-exceptions' and '-fno-rtti' by default. ! '-tno-android-ld' ! Disable linking effects of '-mandroid', i.e., pass standard Linux linking options to the linker.  File: gcc.info, Node: H8/300 Options, Next: HPPA Options, Prev: GNU/Linux Options, Up: Submodel Options 3.18.16 H8/300 Options ---------------------- ! These '-m' options are defined for the H8/300 implementations: ! '-mrelax' Shorten some address references at link time, when possible; uses ! the linker option '-relax'. *Note 'ld' and the H8/300: (ld)H8/300, ! for a fuller description. ! '-mh' Generate code for the H8/300H. ! '-ms' Generate code for the H8S. ! '-mn' Generate code for the H8S and H8/300H in the normal mode. This ! switch must be used either with '-mh' or '-ms'. ! '-ms2600' Generate code for the H8S/2600. This switch must be used with ! '-ms'. ! '-mexr' Extended registers are stored on stack before execution of function ! with monitor attribute. Default option is '-mexr'. This option is valid only for H8S targets. ! '-mno-exr' Extended registers are not stored on stack before execution of ! function with monitor attribute. Default option is '-mno-exr'. This option is valid only for H8S targets. ! '-mint32' ! Make 'int' data 32 bits by default. ! '-malign-300' On the H8/300H and H8S, use the same alignment rules as for the H8/300. The default for the H8/300H and H8S is to align longs and ! floats on 4-byte boundaries. '-malign-300' causes them to be aligned on 2-byte boundaries. This option has no effect on the H8/300. --- 15370,15457 ---- 3.18.15 GNU/Linux Options ------------------------- ! These `-m' options are defined for GNU/Linux targets: ! `-mglibc' Use the GNU C library. This is the default except on ! `*-*-linux-*uclibc*', `*-*-linux-*musl*' and `*-*-linux-*android*' targets. ! `-muclibc' ! Use uClibc C library. This is the default on `*-*-linux-*uclibc*' targets. ! `-mmusl' ! Use the musl C library. This is the default on `*-*-linux-*musl*' targets. ! `-mbionic' ! Use Bionic C library. This is the default on ! `*-*-linux-*android*' targets. ! `-mandroid' ! Compile code compatible with Android platform. This is the ! default on `*-*-linux-*android*' targets. ! When compiling, this option enables `-mbionic', `-fPIC', ! `-fno-exceptions' and `-fno-rtti' by default. When linking, this option makes the GCC driver pass Android-specific options to the linker. Finally, this option causes the preprocessor macro ! `__ANDROID__' to be defined. ! `-tno-android-cc' ! Disable compilation effects of `-mandroid', i.e., do not enable ! `-mbionic', `-fPIC', `-fno-exceptions' and `-fno-rtti' by default. ! `-tno-android-ld' ! Disable linking effects of `-mandroid', i.e., pass standard Linux linking options to the linker. +  File: gcc.info, Node: H8/300 Options, Next: HPPA Options, Prev: GNU/Linux Options, Up: Submodel Options 3.18.16 H8/300 Options ---------------------- ! These `-m' options are defined for the H8/300 implementations: ! `-mrelax' Shorten some address references at link time, when possible; uses ! the linker option `-relax'. *Note `ld' and the H8/300: ! (ld)H8/300, for a fuller description. ! `-mh' Generate code for the H8/300H. ! `-ms' Generate code for the H8S. ! `-mn' Generate code for the H8S and H8/300H in the normal mode. This ! switch must be used either with `-mh' or `-ms'. ! `-ms2600' Generate code for the H8S/2600. This switch must be used with ! `-ms'. ! `-mexr' Extended registers are stored on stack before execution of function ! with monitor attribute. Default option is `-mexr'. This option is valid only for H8S targets. ! `-mno-exr' Extended registers are not stored on stack before execution of ! function with monitor attribute. Default option is `-mno-exr'. This option is valid only for H8S targets. ! `-mint32' ! Make `int' data 32 bits by default. ! `-malign-300' On the H8/300H and H8S, use the same alignment rules as for the H8/300. The default for the H8/300H and H8S is to align longs and ! floats on 4-byte boundaries. `-malign-300' causes them to be aligned on 2-byte boundaries. This option has no effect on the H8/300. *************** File: gcc.info, Node: HPPA Options, Ne *** 15380,15520 **** 3.18.17 HPPA Options -------------------- ! These '-m' options are defined for the HPPA family of computers: ! '-march=ARCHITECTURE-TYPE' Generate code for the specified architecture. The choices for ! ARCHITECTURE-TYPE are '1.0' for PA 1.0, '1.1' for PA 1.1, and '2.0' ! for PA 2.0 processors. Refer to '/usr/lib/sched.models' on an ! HP-UX system to determine the proper architecture option for your ! machine. Code compiled for lower numbered architectures runs on ! higher numbered architectures, but not the other way around. ! '-mpa-risc-1-0' ! '-mpa-risc-1-1' ! '-mpa-risc-2-0' ! Synonyms for '-march=1.0', '-march=1.1', and '-march=2.0' respectively. ! '-mjump-in-delay' This option is ignored and provided for compatibility purposes only. ! '-mdisable-fpregs' Prevent floating-point registers from being used in any manner. This is necessary for compiling kernels that perform lazy context switching of floating-point registers. If you use this option and attempt to perform floating-point operations, the compiler aborts. ! '-mdisable-indexing' Prevent the compiler from using indexing address modes. This avoids some rather obscure problems when compiling MIG generated code under MACH. ! '-mno-space-regs' ! Generate code that assumes the target has no space registers. This ! allows GCC to generate faster indirect calls and use unscaled index ! address modes. Such code is suitable for level 0 PA systems and kernels. ! '-mfast-indirect-calls' Generate code that assumes calls never cross space boundaries. This allows GCC to emit code that performs faster indirect calls. This option does not work in the presence of shared libraries or nested functions. ! '-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! '-mlong-load-store' Generate 3-instruction load and store sequences as sometimes ! required by the HP-UX 10 linker. This is equivalent to the '+k' option to the HP compilers. ! '-mportable-runtime' Use the portable calling conventions proposed by HP for ELF systems. ! '-mgas' Enable the use of assembler directives only GAS understands. ! '-mschedule=CPU-TYPE' Schedule code according to the constraints for the machine type ! CPU-TYPE. The choices for CPU-TYPE are '700' '7100', '7100LC', ! '7200', '7300' and '8000'. Refer to '/usr/lib/sched.models' on an HP-UX system to determine the proper scheduling option for your ! machine. The default scheduling is '8000'. ! '-mlinker-opt' Enable the optimization pass in the HP-UX linker. Note this makes ! symbolic debugging impossible. It also triggers a bug in the HP-UX ! 8 and HP-UX 9 linkers in which they give bogus error messages when ! linking some programs. ! '-msoft-float' Generate output containing library calls for floating point. *Warning:* the requisite libraries are not available for all HPPA ! targets. Normally the facilities of the machine's usual C compiler ! are used, but this cannot be done directly in cross-compilation. ! You must make your own arrangements to provide suitable library ! functions for cross-compilation. ! '-msoft-float' changes the calling convention in the output file; therefore, it is only useful if you compile _all_ of a program with ! this option. In particular, you need to compile 'libgcc.a', the ! library that comes with GCC, with '-msoft-float' in order for this to work. ! '-msio' ! Generate the predefine, '_SIO', for server IO. The default is ! '-mwsio'. This generates the predefines, '__hp9000s700', ! '__hp9000s700__' and '_WSIO', for workstation IO. These options are available under HP-UX and HI-UX. ! '-mgnu-ld' ! Use options specific to GNU 'ld'. This passes '-shared' to 'ld' when building a shared library. It is the default when GCC is configured, explicitly or implicitly, with the GNU linker. This ! option does not affect which 'ld' is called; it only changes what ! parameters are passed to that 'ld'. The 'ld' that is called is ! determined by the '--with-ld' configure option, GCC's program ! search path, and finally by the user's 'PATH'. The linker used by ! GCC can be printed using 'which `gcc -print-prog-name=ld`'. This option is only available on the 64-bit HP-UX GCC, i.e. configured ! with 'hppa*64*-*-hpux*'. ! '-mhp-ld' ! Use options specific to HP 'ld'. This passes '-b' to 'ld' when ! building a shared library and passes '+Accept TypeMismatch' to 'ld' ! on all links. It is the default when GCC is configured, explicitly ! or implicitly, with the HP linker. This option does not affect ! which 'ld' is called; it only changes what parameters are passed to ! that 'ld'. The 'ld' that is called is determined by the ! '--with-ld' configure option, GCC's program search path, and ! finally by the user's 'PATH'. The linker used by GCC can be ! printed using 'which `gcc -print-prog-name=ld`'. This option is only available on the 64-bit HP-UX GCC, i.e. configured with ! 'hppa*64*-*-hpux*'. ! '-mlong-calls' Generate code that uses long call sequences. This ensures that a call is always able to reach linker generated stubs. The default ! is to generate long calls only when the distance from the call site ! to the beginning of the function or translation unit, as the case ! may be, exceeds a predefined limit set by the branch type being ! used. The limits for normal calls are 7,600,000 and 240,000 bytes, ! respectively for the PA 2.0 and PA 1.X architectures. Sibcalls are ! always limited at 240,000 bytes. Distances are measured from the beginning of functions when using ! the '-ffunction-sections' option, or when using the '-mgas' and ! '-mno-portable-runtime' options together under HP-UX with the SOM linker. It is normally not desirable to use this option as it degrades --- 15461,15601 ---- 3.18.17 HPPA Options -------------------- ! These `-m' options are defined for the HPPA family of computers: ! `-march=ARCHITECTURE-TYPE' Generate code for the specified architecture. The choices for ! ARCHITECTURE-TYPE are `1.0' for PA 1.0, `1.1' for PA 1.1, and ! `2.0' for PA 2.0 processors. Refer to `/usr/lib/sched.models' on ! an HP-UX system to determine the proper architecture option for ! your machine. Code compiled for lower numbered architectures runs ! on higher numbered architectures, but not the other way around. ! `-mpa-risc-1-0' ! `-mpa-risc-1-1' ! `-mpa-risc-2-0' ! Synonyms for `-march=1.0', `-march=1.1', and `-march=2.0' respectively. ! `-mjump-in-delay' This option is ignored and provided for compatibility purposes only. ! `-mdisable-fpregs' Prevent floating-point registers from being used in any manner. This is necessary for compiling kernels that perform lazy context switching of floating-point registers. If you use this option and attempt to perform floating-point operations, the compiler aborts. ! `-mdisable-indexing' Prevent the compiler from using indexing address modes. This avoids some rather obscure problems when compiling MIG generated code under MACH. ! `-mno-space-regs' ! Generate code that assumes the target has no space registers. ! This allows GCC to generate faster indirect calls and use unscaled ! index address modes. Such code is suitable for level 0 PA systems and kernels. ! `-mfast-indirect-calls' Generate code that assumes calls never cross space boundaries. This allows GCC to emit code that performs faster indirect calls. This option does not work in the presence of shared libraries or nested functions. ! `-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! `-mlong-load-store' Generate 3-instruction load and store sequences as sometimes ! required by the HP-UX 10 linker. This is equivalent to the `+k' option to the HP compilers. ! `-mportable-runtime' Use the portable calling conventions proposed by HP for ELF systems. ! `-mgas' Enable the use of assembler directives only GAS understands. ! `-mschedule=CPU-TYPE' Schedule code according to the constraints for the machine type ! CPU-TYPE. The choices for CPU-TYPE are `700' `7100', `7100LC', ! `7200', `7300' and `8000'. Refer to `/usr/lib/sched.models' on an HP-UX system to determine the proper scheduling option for your ! machine. The default scheduling is `8000'. ! `-mlinker-opt' Enable the optimization pass in the HP-UX linker. Note this makes ! symbolic debugging impossible. It also triggers a bug in the ! HP-UX 8 and HP-UX 9 linkers in which they give bogus error ! messages when linking some programs. ! `-msoft-float' Generate output containing library calls for floating point. *Warning:* the requisite libraries are not available for all HPPA ! targets. Normally the facilities of the machine's usual C ! compiler are used, but this cannot be done directly in ! cross-compilation. You must make your own arrangements to provide ! suitable library functions for cross-compilation. ! `-msoft-float' changes the calling convention in the output file; therefore, it is only useful if you compile _all_ of a program with ! this option. In particular, you need to compile `libgcc.a', the ! library that comes with GCC, with `-msoft-float' in order for this to work. ! `-msio' ! Generate the predefine, `_SIO', for server IO. The default is ! `-mwsio'. This generates the predefines, `__hp9000s700', ! `__hp9000s700__' and `_WSIO', for workstation IO. These options are available under HP-UX and HI-UX. ! `-mgnu-ld' ! Use options specific to GNU `ld'. This passes `-shared' to `ld' when building a shared library. It is the default when GCC is configured, explicitly or implicitly, with the GNU linker. This ! option does not affect which `ld' is called; it only changes what ! parameters are passed to that `ld'. The `ld' that is called is ! determined by the `--with-ld' configure option, GCC's program ! search path, and finally by the user's `PATH'. The linker used by ! GCC can be printed using `which `gcc -print-prog-name=ld`'. This option is only available on the 64-bit HP-UX GCC, i.e. configured ! with `hppa*64*-*-hpux*'. ! `-mhp-ld' ! Use options specific to HP `ld'. This passes `-b' to `ld' when ! building a shared library and passes `+Accept TypeMismatch' to ! `ld' on all links. It is the default when GCC is configured, ! explicitly or implicitly, with the HP linker. This option does ! not affect which `ld' is called; it only changes what parameters ! are passed to that `ld'. The `ld' that is called is determined by ! the `--with-ld' configure option, GCC's program search path, and ! finally by the user's `PATH'. The linker used by GCC can be ! printed using `which `gcc -print-prog-name=ld`'. This option is only available on the 64-bit HP-UX GCC, i.e. configured with ! `hppa*64*-*-hpux*'. ! `-mlong-calls' Generate code that uses long call sequences. This ensures that a call is always able to reach linker generated stubs. The default ! is to generate long calls only when the distance from the call ! site to the beginning of the function or translation unit, as the ! case may be, exceeds a predefined limit set by the branch type ! being used. The limits for normal calls are 7,600,000 and 240,000 ! bytes, respectively for the PA 2.0 and PA 1.X architectures. ! Sibcalls are always limited at 240,000 bytes. Distances are measured from the beginning of functions when using ! the `-ffunction-sections' option, or when using the `-mgas' and ! `-mno-portable-runtime' options together under HP-UX with the SOM linker. It is normally not desirable to use this option as it degrades *************** These '-m' options are defined for the H *** 15528,15577 **** However, an indirect call is used on 32-bit ELF systems in pic code and it is quite long. ! '-munix=UNIX-STD' Generate compiler predefines and select a startfile for the ! specified UNIX standard. The choices for UNIX-STD are '93', '95' ! and '98'. '93' is supported on all HP-UX versions. '95' is ! available on HP-UX 10.10 and later. '98' is available on HP-UX ! 11.11 and later. The default values are '93' for HP-UX 10.00, '95' ! for HP-UX 10.10 though to 11.00, and '98' for HP-UX 11.11 and later. ! '-munix=93' provides the same predefines as GCC 3.3 and 3.4. ! '-munix=95' provides additional predefines for 'XOPEN_UNIX' and ! '_XOPEN_SOURCE_EXTENDED', and the startfile 'unix95.o'. ! '-munix=98' provides additional predefines for '_XOPEN_UNIX', ! '_XOPEN_SOURCE_EXTENDED', '_INCLUDE__STDC_A1_SOURCE' and ! '_INCLUDE_XOPEN_SOURCE_500', and the startfile 'unix98.o'. It is _important_ to note that this option changes the interfaces for various library routines. It also affects the operational ! behavior of the C library. Thus, _extreme_ care is needed in using ! this option. Library code that is intended to operate with more than one UNIX standard must test, set and restore the variable ! '__xpg4_extended_mask' as appropriate. Most GNU software doesn't provide this capability. ! '-nolibdld' Suppress the generation of link options to search libdld.sl when ! the '-static' option is specified on HP-UX 10 and later. ! '-static' The HP-UX implementation of setlocale in libc has a dependency on libdld.sl. There isn't an archive version of libdld.sl. Thus, ! when the '-static' option is specified, special link options are needed to resolve this dependency. On HP-UX 10 and later, the GCC driver adds the necessary options to ! link with libdld.sl when the '-static' option is specified. This ! causes the resulting binary to be dynamic. On the 64-bit port, the ! linkers generate dynamic binaries by default in any case. The ! '-nolibdld' option can be used to prevent the GCC driver from adding these link options. ! '-threads' Add support for multithreading with the "dce thread" library under HP-UX. This option sets flags for both the preprocessor and linker. --- 15609,15658 ---- However, an indirect call is used on 32-bit ELF systems in pic code and it is quite long. ! `-munix=UNIX-STD' Generate compiler predefines and select a startfile for the ! specified UNIX standard. The choices for UNIX-STD are `93', `95' ! and `98'. `93' is supported on all HP-UX versions. `95' is ! available on HP-UX 10.10 and later. `98' is available on HP-UX ! 11.11 and later. The default values are `93' for HP-UX 10.00, ! `95' for HP-UX 10.10 though to 11.00, and `98' for HP-UX 11.11 and later. ! `-munix=93' provides the same predefines as GCC 3.3 and 3.4. ! `-munix=95' provides additional predefines for `XOPEN_UNIX' and ! `_XOPEN_SOURCE_EXTENDED', and the startfile `unix95.o'. ! `-munix=98' provides additional predefines for `_XOPEN_UNIX', ! `_XOPEN_SOURCE_EXTENDED', `_INCLUDE__STDC_A1_SOURCE' and ! `_INCLUDE_XOPEN_SOURCE_500', and the startfile `unix98.o'. It is _important_ to note that this option changes the interfaces for various library routines. It also affects the operational ! behavior of the C library. Thus, _extreme_ care is needed in ! using this option. Library code that is intended to operate with more than one UNIX standard must test, set and restore the variable ! `__xpg4_extended_mask' as appropriate. Most GNU software doesn't provide this capability. ! `-nolibdld' Suppress the generation of link options to search libdld.sl when ! the `-static' option is specified on HP-UX 10 and later. ! `-static' The HP-UX implementation of setlocale in libc has a dependency on libdld.sl. There isn't an archive version of libdld.sl. Thus, ! when the `-static' option is specified, special link options are needed to resolve this dependency. On HP-UX 10 and later, the GCC driver adds the necessary options to ! link with libdld.sl when the `-static' option is specified. This ! causes the resulting binary to be dynamic. On the 64-bit port, ! the linkers generate dynamic binaries by default in any case. The ! `-nolibdld' option can be used to prevent the GCC driver from adding these link options. ! `-threads' Add support for multithreading with the "dce thread" library under HP-UX. This option sets flags for both the preprocessor and linker. *************** File: gcc.info, Node: IA-64 Options, N *** 15582,15848 **** 3.18.18 IA-64 Options --------------------- ! These are the '-m' options defined for the Intel IA-64 architecture. ! '-mbig-endian' Generate code for a big-endian target. This is the default for HP-UX. ! '-mlittle-endian' Generate code for a little-endian target. This is the default for AIX5 and GNU/Linux. ! '-mgnu-as' ! '-mno-gnu-as' Generate (or don't) code for the GNU assembler. This is the default. ! '-mgnu-ld' ! '-mno-gnu-ld' Generate (or don't) code for the GNU linker. This is the default. ! '-mno-pic' Generate code that does not use a global pointer register. The result is not position independent code, and violates the IA-64 ABI. ! '-mvolatile-asm-stop' ! '-mno-volatile-asm-stop' Generate (or don't) a stop bit immediately before and after volatile asm statements. ! '-mregister-names' ! '-mno-register-names' ! Generate (or don't) 'in', 'loc', and 'out' register names for the stacked registers. This may make assembler output more readable. ! '-mno-sdata' ! '-msdata' Disable (or enable) optimizations that use the small data section. This may be useful for working around optimizer bugs. ! '-mconstant-gp' Generate code that uses a single constant global pointer value. This is useful when compiling kernel code. ! '-mauto-pic' Generate code that is self-relocatable. This implies ! '-mconstant-gp'. This is useful when compiling firmware code. ! '-minline-float-divide-min-latency' ! Generate code for inline divides of floating-point values using the ! minimum latency algorithm. ! '-minline-float-divide-max-throughput' ! Generate code for inline divides of floating-point values using the ! maximum throughput algorithm. ! '-mno-inline-float-divide' Do not generate inline code for divides of floating-point values. ! '-minline-int-divide-min-latency' Generate code for inline divides of integer values using the minimum latency algorithm. ! '-minline-int-divide-max-throughput' Generate code for inline divides of integer values using the maximum throughput algorithm. ! '-mno-inline-int-divide' Do not generate inline code for divides of integer values. ! '-minline-sqrt-min-latency' Generate code for inline square roots using the minimum latency algorithm. ! '-minline-sqrt-max-throughput' Generate code for inline square roots using the maximum throughput algorithm. ! '-mno-inline-sqrt' ! Do not generate inline code for 'sqrt'. ! '-mfused-madd' ! '-mno-fused-madd' Do (don't) generate code that uses the fused multiply/add or multiply/subtract instructions. The default is to use these instructions. ! '-mno-dwarf2-asm' ! '-mdwarf2-asm' Don't (or do) generate assembler code for the DWARF line number debugging info. This may be useful when not using the GNU assembler. ! '-mearly-stop-bits' ! '-mno-early-stop-bits' Allow stop bits to be placed earlier than immediately preceding the instruction that triggered the stop bit. This can improve instruction scheduling, but does not always do so. ! '-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! '-mtls-size=TLS-SIZE' Specify bit size of immediate TLS offsets. Valid values are 14, 22, and 64. ! '-mtune=CPU-TYPE' Tune the instruction scheduling for a particular CPU, Valid values ! are 'itanium', 'itanium1', 'merced', 'itanium2', and 'mckinley'. ! '-milp32' ! '-mlp64' Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. These are HP-UX specific flags. ! '-mno-sched-br-data-spec' ! '-msched-br-data-spec' (Dis/En)able data speculative scheduling before reload. This ! results in generation of 'ld.a' instructions and the corresponding ! check instructions ('ld.c' / 'chk.a'). The default setting is disabled. ! '-msched-ar-data-spec' ! '-mno-sched-ar-data-spec' (En/Dis)able data speculative scheduling after reload. This ! results in generation of 'ld.a' instructions and the corresponding ! check instructions ('ld.c' / 'chk.a'). The default setting is enabled. ! '-mno-sched-control-spec' ! '-msched-control-spec' (Dis/En)able control speculative scheduling. This feature is ! available only during region scheduling (i.e. before reload). This ! results in generation of the 'ld.s' instructions and the ! corresponding check instructions 'chk.s'. The default setting is disabled. ! '-msched-br-in-data-spec' ! '-mno-sched-br-in-data-spec' (En/Dis)able speculative scheduling of the instructions that are dependent on the data speculative loads before reload. This is ! effective only with '-msched-br-data-spec' enabled. The default setting is enabled. ! '-msched-ar-in-data-spec' ! '-mno-sched-ar-in-data-spec' (En/Dis)able speculative scheduling of the instructions that are dependent on the data speculative loads after reload. This is ! effective only with '-msched-ar-data-spec' enabled. The default setting is enabled. ! '-msched-in-control-spec' ! '-mno-sched-in-control-spec' (En/Dis)able speculative scheduling of the instructions that are ! dependent on the control speculative loads. This is effective only ! with '-msched-control-spec' enabled. The default setting is enabled. ! '-mno-sched-prefer-non-data-spec-insns' ! '-msched-prefer-non-data-spec-insns' If enabled, data-speculative instructions are chosen for schedule only if there are no other choices at the moment. This makes the use of the data speculation much more conservative. The default setting is disabled. ! '-mno-sched-prefer-non-control-spec-insns' ! '-msched-prefer-non-control-spec-insns' If enabled, control-speculative instructions are chosen for schedule only if there are no other choices at the moment. This makes the use of the control speculation much more conservative. The default setting is disabled. ! '-mno-sched-count-spec-in-critical-path' ! '-msched-count-spec-in-critical-path' If enabled, speculative dependencies are considered during computation of the instructions priorities. This makes the use of the speculation a bit more conservative. The default setting is disabled. ! '-msched-spec-ldc' Use a simple data speculation check. This option is on by default. ! '-msched-control-spec-ldc' Use a simple check for control speculation. This option is on by default. ! '-msched-stop-bits-after-every-cycle' ! Place a stop bit after every cycle when scheduling. This option is ! on by default. ! '-msched-fp-mem-deps-zero-cost' ! Assume that floating-point stores and loads are not likely to cause ! a conflict when placed into the same instruction group. This ! option is disabled by default. ! '-msel-sched-dont-check-control-spec' Generate checks for control speculation in selective scheduling. This flag is disabled by default. ! '-msched-max-memory-insns=MAX-INSNS' Limit on the number of memory insns per instruction group, giving ! lower priority to subsequent memory insns attempting to schedule in ! the same instruction group. Frequently useful to prevent cache bank conflicts. The default value is 1. ! '-msched-max-memory-insns-hard-limit' ! Makes the limit specified by 'msched-max-memory-insns' a hard limit, disallowing more than that number in an instruction group. Otherwise, the limit is "soft", meaning that non-memory operations are preferred when the limit is reached, but memory operations may still be scheduled.  File: gcc.info, Node: LM32 Options, Next: M32C Options, Prev: IA-64 Options, Up: Submodel Options 3.18.19 LM32 Options -------------------- ! These '-m' options are defined for the LatticeMico32 architecture: ! '-mbarrel-shift-enabled' Enable barrel-shift instructions. ! '-mdivide-enabled' Enable divide and modulus instructions. ! '-mmultiply-enabled' Enable multiply instructions. ! '-msign-extend-enabled' Enable sign extend instructions. ! '-muser-enabled' Enable user-defined instructions.  File: gcc.info, Node: M32C Options, Next: M32R/D Options, Prev: LM32 Options, Up: Submodel Options 3.18.20 M32C Options -------------------- ! '-mcpu=NAME' Select the CPU for which code is generated. NAME may be one of ! 'r8c' for the R8C/Tiny series, 'm16c' for the M16C (up to /60) ! series, 'm32cm' for the M16C/80 series, or 'm32c' for the M32C/80 series. ! '-msim' Specifies that the program will be run on the simulator. This ! causes an alternate runtime library to be linked in which supports, ! for example, file I/O. You must not use this option when ! generating programs that will run on real hardware; you must provide your own runtime library for whatever I/O functions are needed. ! '-memregs=NUMBER' Specifies the number of memory-based pseudo-registers GCC uses during code generation. These pseudo-registers are used like real registers, so there is a tradeoff between GCC's ability to fit the --- 15663,15931 ---- 3.18.18 IA-64 Options --------------------- ! These are the `-m' options defined for the Intel IA-64 architecture. ! `-mbig-endian' Generate code for a big-endian target. This is the default for HP-UX. ! `-mlittle-endian' Generate code for a little-endian target. This is the default for AIX5 and GNU/Linux. ! `-mgnu-as' ! `-mno-gnu-as' Generate (or don't) code for the GNU assembler. This is the default. ! `-mgnu-ld' ! `-mno-gnu-ld' Generate (or don't) code for the GNU linker. This is the default. ! `-mno-pic' Generate code that does not use a global pointer register. The result is not position independent code, and violates the IA-64 ABI. ! `-mvolatile-asm-stop' ! `-mno-volatile-asm-stop' Generate (or don't) a stop bit immediately before and after volatile asm statements. ! `-mregister-names' ! `-mno-register-names' ! Generate (or don't) `in', `loc', and `out' register names for the stacked registers. This may make assembler output more readable. ! `-mno-sdata' ! `-msdata' Disable (or enable) optimizations that use the small data section. This may be useful for working around optimizer bugs. ! `-mconstant-gp' Generate code that uses a single constant global pointer value. This is useful when compiling kernel code. ! `-mauto-pic' Generate code that is self-relocatable. This implies ! `-mconstant-gp'. This is useful when compiling firmware code. ! `-minline-float-divide-min-latency' ! Generate code for inline divides of floating-point values using ! the minimum latency algorithm. ! `-minline-float-divide-max-throughput' ! Generate code for inline divides of floating-point values using ! the maximum throughput algorithm. ! `-mno-inline-float-divide' Do not generate inline code for divides of floating-point values. ! `-minline-int-divide-min-latency' Generate code for inline divides of integer values using the minimum latency algorithm. ! `-minline-int-divide-max-throughput' Generate code for inline divides of integer values using the maximum throughput algorithm. ! `-mno-inline-int-divide' Do not generate inline code for divides of integer values. ! `-minline-sqrt-min-latency' Generate code for inline square roots using the minimum latency algorithm. ! `-minline-sqrt-max-throughput' Generate code for inline square roots using the maximum throughput algorithm. ! `-mno-inline-sqrt' ! Do not generate inline code for `sqrt'. ! `-mfused-madd' ! `-mno-fused-madd' Do (don't) generate code that uses the fused multiply/add or multiply/subtract instructions. The default is to use these instructions. ! `-mno-dwarf2-asm' ! `-mdwarf2-asm' Don't (or do) generate assembler code for the DWARF line number debugging info. This may be useful when not using the GNU assembler. ! `-mearly-stop-bits' ! `-mno-early-stop-bits' Allow stop bits to be placed earlier than immediately preceding the instruction that triggered the stop bit. This can improve instruction scheduling, but does not always do so. ! `-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! `-mtls-size=TLS-SIZE' Specify bit size of immediate TLS offsets. Valid values are 14, 22, and 64. ! `-mtune=CPU-TYPE' Tune the instruction scheduling for a particular CPU, Valid values ! are `itanium', `itanium1', `merced', `itanium2', and `mckinley'. ! `-milp32' ! `-mlp64' Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. These are HP-UX specific flags. ! `-mno-sched-br-data-spec' ! `-msched-br-data-spec' (Dis/En)able data speculative scheduling before reload. This ! results in generation of `ld.a' instructions and the corresponding ! check instructions (`ld.c' / `chk.a'). The default setting is disabled. ! `-msched-ar-data-spec' ! `-mno-sched-ar-data-spec' (En/Dis)able data speculative scheduling after reload. This ! results in generation of `ld.a' instructions and the corresponding ! check instructions (`ld.c' / `chk.a'). The default setting is enabled. ! `-mno-sched-control-spec' ! `-msched-control-spec' (Dis/En)able control speculative scheduling. This feature is ! available only during region scheduling (i.e. before reload). ! This results in generation of the `ld.s' instructions and the ! corresponding check instructions `chk.s'. The default setting is disabled. ! `-msched-br-in-data-spec' ! `-mno-sched-br-in-data-spec' (En/Dis)able speculative scheduling of the instructions that are dependent on the data speculative loads before reload. This is ! effective only with `-msched-br-data-spec' enabled. The default setting is enabled. ! `-msched-ar-in-data-spec' ! `-mno-sched-ar-in-data-spec' (En/Dis)able speculative scheduling of the instructions that are dependent on the data speculative loads after reload. This is ! effective only with `-msched-ar-data-spec' enabled. The default setting is enabled. ! `-msched-in-control-spec' ! `-mno-sched-in-control-spec' (En/Dis)able speculative scheduling of the instructions that are ! dependent on the control speculative loads. This is effective ! only with `-msched-control-spec' enabled. The default setting is enabled. ! `-mno-sched-prefer-non-data-spec-insns' ! `-msched-prefer-non-data-spec-insns' If enabled, data-speculative instructions are chosen for schedule only if there are no other choices at the moment. This makes the use of the data speculation much more conservative. The default setting is disabled. ! `-mno-sched-prefer-non-control-spec-insns' ! `-msched-prefer-non-control-spec-insns' If enabled, control-speculative instructions are chosen for schedule only if there are no other choices at the moment. This makes the use of the control speculation much more conservative. The default setting is disabled. ! `-mno-sched-count-spec-in-critical-path' ! `-msched-count-spec-in-critical-path' If enabled, speculative dependencies are considered during computation of the instructions priorities. This makes the use of the speculation a bit more conservative. The default setting is disabled. ! `-msched-spec-ldc' Use a simple data speculation check. This option is on by default. ! `-msched-control-spec-ldc' Use a simple check for control speculation. This option is on by default. ! `-msched-stop-bits-after-every-cycle' ! Place a stop bit after every cycle when scheduling. This option ! is on by default. ! `-msched-fp-mem-deps-zero-cost' ! Assume that floating-point stores and loads are not likely to ! cause a conflict when placed into the same instruction group. ! This option is disabled by default. ! `-msel-sched-dont-check-control-spec' Generate checks for control speculation in selective scheduling. This flag is disabled by default. ! `-msched-max-memory-insns=MAX-INSNS' Limit on the number of memory insns per instruction group, giving ! lower priority to subsequent memory insns attempting to schedule ! in the same instruction group. Frequently useful to prevent cache bank conflicts. The default value is 1. ! `-msched-max-memory-insns-hard-limit' ! Makes the limit specified by `msched-max-memory-insns' a hard limit, disallowing more than that number in an instruction group. Otherwise, the limit is "soft", meaning that non-memory operations are preferred when the limit is reached, but memory operations may still be scheduled. +  File: gcc.info, Node: LM32 Options, Next: M32C Options, Prev: IA-64 Options, Up: Submodel Options 3.18.19 LM32 Options -------------------- ! These `-m' options are defined for the LatticeMico32 architecture: ! `-mbarrel-shift-enabled' Enable barrel-shift instructions. ! `-mdivide-enabled' Enable divide and modulus instructions. ! `-mmultiply-enabled' Enable multiply instructions. ! `-msign-extend-enabled' Enable sign extend instructions. ! `-muser-enabled' Enable user-defined instructions. +  File: gcc.info, Node: M32C Options, Next: M32R/D Options, Prev: LM32 Options, Up: Submodel Options 3.18.20 M32C Options -------------------- ! `-mcpu=NAME' Select the CPU for which code is generated. NAME may be one of ! `r8c' for the R8C/Tiny series, `m16c' for the M16C (up to /60) ! series, `m32cm' for the M16C/80 series, or `m32c' for the M32C/80 series. ! `-msim' Specifies that the program will be run on the simulator. This ! causes an alternate runtime library to be linked in which ! supports, for example, file I/O. You must not use this option ! when generating programs that will run on real hardware; you must provide your own runtime library for whatever I/O functions are needed. ! `-memregs=NUMBER' Specifies the number of memory-based pseudo-registers GCC uses during code generation. These pseudo-registers are used like real registers, so there is a tradeoff between GCC's ability to fit the *************** File: gcc.info, Node: M32C Options, Ne *** 15852,16195 **** that, you must not use this option with GCC's default runtime libraries.  File: gcc.info, Node: M32R/D Options, Next: M680x0 Options, Prev: M32C Options, Up: Submodel Options 3.18.21 M32R/D Options ---------------------- ! These '-m' options are defined for Renesas M32R/D architectures: ! '-m32r2' Generate code for the M32R/2. ! '-m32rx' Generate code for the M32R/X. ! '-m32r' Generate code for the M32R. This is the default. ! '-mmodel=small' Assume all objects live in the lower 16MB of memory (so that their ! addresses can be loaded with the 'ld24' instruction), and assume ! all subroutines are reachable with the 'bl' instruction. This is the default. The addressability of a particular object can be set with the ! 'model' attribute. ! '-mmodel=medium' Assume objects may be anywhere in the 32-bit address space (the ! compiler generates 'seth/add3' instructions to load their ! addresses), and assume all subroutines are reachable with the 'bl' instruction. ! '-mmodel=large' Assume objects may be anywhere in the 32-bit address space (the ! compiler generates 'seth/add3' instructions to load their addresses), and assume subroutines may not be reachable with the ! 'bl' instruction (the compiler generates the much slower ! 'seth/add3/jl' instruction sequence). ! '-msdata=none' Disable use of the small data area. Variables are put into one of ! '.data', '.bss', or '.rodata' (unless the 'section' attribute has been specified). This is the default. ! The small data area consists of sections '.sdata' and '.sbss'. Objects may be explicitly put in the small data area with the ! 'section' attribute using one of these sections. ! '-msdata=sdata' Put small global and static data in the small data area, but do not generate special code to reference them. ! '-msdata=use' Put small global and static data in the small data area, and generate special instructions to reference them. ! '-G NUM' Put global and static objects less than or equal to NUM bytes into the small data or BSS sections instead of the normal data or BSS ! sections. The default value of NUM is 8. The '-msdata' option ! must be set to one of 'sdata' or 'use' for this option to have any effect. ! All modules should be compiled with the same '-G NUM' value. Compiling with different values of NUM may or may not work; if it doesn't the linker gives an error message--incorrect code is not generated. ! '-mdebug' Makes the M32R-specific code in the compiler display some statistics that might help in debugging programs. ! '-malign-loops' Align all loops to a 32-byte boundary. ! '-mno-align-loops' Do not enforce a 32-byte alignment for loops. This is the default. ! '-missue-rate=NUMBER' Issue NUMBER instructions per cycle. NUMBER can only be 1 or 2. ! '-mbranch-cost=NUMBER' NUMBER can only be 1 or 2. If it is 1 then branches are preferred over conditional code, if it is 2, then the opposite applies. ! '-mflush-trap=NUMBER' Specifies the trap number to use to flush the cache. The default is 12. Valid numbers are between 0 and 15 inclusive. ! '-mno-flush-trap' Specifies that the cache cannot be flushed by using a trap. ! '-mflush-func=NAME' Specifies the name of the operating system function to call to ! flush the cache. The default is '_flush_cache', but a function call is only used if a trap is not available. ! '-mno-flush-func' Indicates that there is no OS function for flushing the cache.  File: gcc.info, Node: M680x0 Options, Next: MCore Options, Prev: M32R/D Options, Up: Submodel Options 3.18.22 M680x0 Options ---------------------- ! These are the '-m' options defined for M680x0 and ColdFire processors. The default settings depend on which architecture was selected when the compiler was configured; the defaults for the most common choices are given below. ! '-march=ARCH' Generate code for a specific M680x0 or ColdFire instruction set architecture. Permissible values of ARCH for M680x0 architectures ! are: '68000', '68010', '68020', '68030', '68040', '68060' and ! 'cpu32'. ColdFire architectures are selected according to Freescale's ISA classification and the permissible values are: ! 'isaa', 'isaaplus', 'isab' and 'isac'. ! GCC defines a macro '__mcfARCH__' whenever it is generating code for a ColdFire target. The ARCH in this macro is one of the ! '-march' arguments given above. ! When used together, '-march' and '-mtune' select code that runs on a family of similar processors but that is optimized for a particular microarchitecture. ! '-mcpu=CPU' Generate code for a specific M680x0 or ColdFire processor. The ! M680x0 CPUs are: '68000', '68010', '68020', '68030', '68040', ! '68060', '68302', '68332' and 'cpu32'. The ColdFire CPUs are given ! by the table below, which also classifies the CPUs into families: ! *Family* *'-mcpu' arguments* ! '51' '51' '51ac' '51ag' '51cn' '51em' '51je' '51jf' '51jg' ! '51jm' '51mm' '51qe' '51qm' ! '5206' '5202' '5204' '5206' ! '5206e' '5206e' ! '5208' '5207' '5208' ! '5211a' '5210a' '5211a' ! '5213' '5211' '5212' '5213' ! '5216' '5214' '5216' ! '52235' '52230' '52231' '52232' '52233' '52234' '52235' ! '5225' '5224' '5225' ! '52259' '52252' '52254' '52255' '52256' '52258' '52259' ! '5235' '5232' '5233' '5234' '5235' '523x' ! '5249' '5249' ! '5250' '5250' ! '5271' '5270' '5271' ! '5272' '5272' ! '5275' '5274' '5275' ! '5282' '5280' '5281' '5282' '528x' ! '53017' '53011' '53012' '53013' '53014' '53015' '53016' '53017' ! '5307' '5307' ! '5329' '5327' '5328' '5329' '532x' ! '5373' '5372' '5373' '537x' ! '5407' '5407' ! '5475' '5470' '5471' '5472' '5473' '5474' '5475' '547x' '5480' ! '5481' '5482' '5483' '5484' '5485' ! '-mcpu=CPU' overrides '-march=ARCH' if ARCH is compatible with CPU. ! Other combinations of '-mcpu' and '-march' are rejected. ! GCC defines the macro '__mcf_cpu_CPU' when ColdFire target CPU is ! selected. It also defines '__mcf_family_FAMILY', where the value of FAMILY is given by the table above. ! '-mtune=TUNE' Tune the code for a particular microarchitecture within the ! constraints set by '-march' and '-mcpu'. The M680x0 ! microarchitectures are: '68000', '68010', '68020', '68030', ! '68040', '68060' and 'cpu32'. The ColdFire microarchitectures are: ! 'cfv1', 'cfv2', 'cfv3', 'cfv4' and 'cfv4e'. ! You can also use '-mtune=68020-40' for code that needs to run relatively well on 68020, 68030 and 68040 targets. ! '-mtune=68020-60' is similar but includes 68060 targets as well. ! These two options select the same tuning decisions as '-m68020-40' ! and '-m68020-60' respectively. ! GCC defines the macros '__mcARCH' and '__mcARCH__' when tuning for ! 680x0 architecture ARCH. It also defines 'mcARCH' unless either ! '-ansi' or a non-GNU '-std' option is used. If GCC is tuning for a ! range of architectures, as selected by '-mtune=68020-40' or ! '-mtune=68020-60', it defines the macros for every architecture in the range. ! GCC also defines the macro '__mUARCH__' when tuning for ColdFire microarchitecture UARCH, where UARCH is one of the arguments given above. ! '-m68000' ! '-mc68000' ! Generate output for a 68000. This is the default when the compiler ! is configured for 68000-based systems. It is equivalent to ! '-march=68000'. Use this option for microcontrollers with a 68000 or EC000 core, including the 68008, 68302, 68306, 68307, 68322, 68328 and 68356. ! '-m68010' ! Generate output for a 68010. This is the default when the compiler ! is configured for 68010-based systems. It is equivalent to ! '-march=68010'. ! '-m68020' ! '-mc68020' ! Generate output for a 68020. This is the default when the compiler ! is configured for 68020-based systems. It is equivalent to ! '-march=68020'. ! '-m68030' ! Generate output for a 68030. This is the default when the compiler ! is configured for 68030-based systems. It is equivalent to ! '-march=68030'. ! '-m68040' ! Generate output for a 68040. This is the default when the compiler ! is configured for 68040-based systems. It is equivalent to ! '-march=68040'. This option inhibits the use of 68881/68882 instructions that have to be emulated by software on the 68040. Use this option if your 68040 does not have code to emulate those instructions. ! '-m68060' ! Generate output for a 68060. This is the default when the compiler ! is configured for 68060-based systems. It is equivalent to ! '-march=68060'. This option inhibits the use of 68020 and 68881/68882 instructions ! that have to be emulated by software on the 68060. Use this option ! if your 68060 does not have code to emulate those instructions. ! '-mcpu32' ! Generate output for a CPU32. This is the default when the compiler ! is configured for CPU32-based systems. It is equivalent to ! '-march=cpu32'. Use this option for microcontrollers with a CPU32 or CPU32+ core, including the 68330, 68331, 68332, 68333, 68334, 68336, 68340, 68341, 68349 and 68360. ! '-m5200' Generate output for a 520X ColdFire CPU. This is the default when the compiler is configured for 520X-based systems. It is ! equivalent to '-mcpu=5206', and is now deprecated in favor of that option. ! Use this option for microcontroller with a 5200 core, including the ! MCF5202, MCF5203, MCF5204 and MCF5206. ! '-m5206e' Generate output for a 5206e ColdFire CPU. The option is now ! deprecated in favor of the equivalent '-mcpu=5206e'. ! '-m528x' Generate output for a member of the ColdFire 528X family. The ! option is now deprecated in favor of the equivalent '-mcpu=528x'. ! '-m5307' Generate output for a ColdFire 5307 CPU. The option is now ! deprecated in favor of the equivalent '-mcpu=5307'. ! '-m5407' Generate output for a ColdFire 5407 CPU. The option is now ! deprecated in favor of the equivalent '-mcpu=5407'. ! '-mcfv4e' Generate output for a ColdFire V4e family CPU (e.g. 547x/548x). This includes use of hardware floating-point instructions. The ! option is equivalent to '-mcpu=547x', and is now deprecated in favor of that option. ! '-m68020-40' Generate output for a 68040, without using any of the new instructions. This results in code that can run relatively efficiently on either a 68020/68881 or a 68030 or a 68040. The ! generated code does use the 68881 instructions that are emulated on ! the 68040. ! The option is equivalent to '-march=68020' '-mtune=68020-40'. ! '-m68020-60' Generate output for a 68060, without using any of the new instructions. This results in code that can run relatively efficiently on either a 68020/68881 or a 68030 or a 68040. The ! generated code does use the 68881 instructions that are emulated on ! the 68060. ! The option is equivalent to '-march=68020' '-mtune=68020-60'. ! '-mhard-float' ! '-m68881' Generate floating-point instructions. This is the default for 68020 and above, and for ColdFire devices that have an FPU. It ! defines the macro '__HAVE_68881__' on M680x0 targets and ! '__mcffpu__' on ColdFire targets. ! '-msoft-float' Do not generate floating-point instructions; use library calls instead. This is the default for 68000, 68010, and 68832 targets. It is also the default for ColdFire devices that have no FPU. ! '-mdiv' ! '-mno-div' Generate (do not generate) ColdFire hardware divide and remainder ! instructions. If '-march' is used without '-mcpu', the default is ! "on" for ColdFire architectures and "off" for M680x0 architectures. ! Otherwise, the default is taken from the target CPU (either the ! default CPU, or the one specified by '-mcpu'). For example, the ! default is "off" for '-mcpu=5206' and "on" for '-mcpu=5206e'. ! GCC defines the macro '__mcfhwdiv__' when this option is enabled. ! '-mshort' ! Consider type 'int' to be 16 bits wide, like 'short int'. Additionally, parameters passed on the stack are also aligned to a 16-bit boundary even on targets whose API mandates promotion to 32-bit. ! '-mno-short' ! Do not consider type 'int' to be 16 bits wide. This is the default. ! '-mnobitfield' ! '-mno-bitfield' ! Do not use the bit-field instructions. The '-m68000', '-mcpu32' ! and '-m5200' options imply '-mnobitfield'. ! '-mbitfield' ! Do use the bit-field instructions. The '-m68020' option implies ! '-mbitfield'. This is the default if you use a configuration designed for a 68020. ! '-mrtd' Use a different function-calling convention, in which functions ! that take a fixed number of arguments return with the 'rtd' instruction, which pops their arguments while returning. This saves one instruction in the caller since there is no need to pop the arguments there. --- 15935,16284 ---- that, you must not use this option with GCC's default runtime libraries. +  File: gcc.info, Node: M32R/D Options, Next: M680x0 Options, Prev: M32C Options, Up: Submodel Options 3.18.21 M32R/D Options ---------------------- ! These `-m' options are defined for Renesas M32R/D architectures: ! `-m32r2' Generate code for the M32R/2. ! `-m32rx' Generate code for the M32R/X. ! `-m32r' Generate code for the M32R. This is the default. ! `-mmodel=small' Assume all objects live in the lower 16MB of memory (so that their ! addresses can be loaded with the `ld24' instruction), and assume ! all subroutines are reachable with the `bl' instruction. This is the default. The addressability of a particular object can be set with the ! `model' attribute. ! `-mmodel=medium' Assume objects may be anywhere in the 32-bit address space (the ! compiler generates `seth/add3' instructions to load their ! addresses), and assume all subroutines are reachable with the `bl' instruction. ! `-mmodel=large' Assume objects may be anywhere in the 32-bit address space (the ! compiler generates `seth/add3' instructions to load their addresses), and assume subroutines may not be reachable with the ! `bl' instruction (the compiler generates the much slower ! `seth/add3/jl' instruction sequence). ! `-msdata=none' Disable use of the small data area. Variables are put into one of ! `.data', `.bss', or `.rodata' (unless the `section' attribute has been specified). This is the default. ! The small data area consists of sections `.sdata' and `.sbss'. Objects may be explicitly put in the small data area with the ! `section' attribute using one of these sections. ! `-msdata=sdata' Put small global and static data in the small data area, but do not generate special code to reference them. ! `-msdata=use' Put small global and static data in the small data area, and generate special instructions to reference them. ! `-G NUM' Put global and static objects less than or equal to NUM bytes into the small data or BSS sections instead of the normal data or BSS ! sections. The default value of NUM is 8. The `-msdata' option ! must be set to one of `sdata' or `use' for this option to have any effect. ! All modules should be compiled with the same `-G NUM' value. Compiling with different values of NUM may or may not work; if it doesn't the linker gives an error message--incorrect code is not generated. ! `-mdebug' Makes the M32R-specific code in the compiler display some statistics that might help in debugging programs. ! `-malign-loops' Align all loops to a 32-byte boundary. ! `-mno-align-loops' Do not enforce a 32-byte alignment for loops. This is the default. ! `-missue-rate=NUMBER' Issue NUMBER instructions per cycle. NUMBER can only be 1 or 2. ! `-mbranch-cost=NUMBER' NUMBER can only be 1 or 2. If it is 1 then branches are preferred over conditional code, if it is 2, then the opposite applies. ! `-mflush-trap=NUMBER' Specifies the trap number to use to flush the cache. The default is 12. Valid numbers are between 0 and 15 inclusive. ! `-mno-flush-trap' Specifies that the cache cannot be flushed by using a trap. ! `-mflush-func=NAME' Specifies the name of the operating system function to call to ! flush the cache. The default is `_flush_cache', but a function call is only used if a trap is not available. ! `-mno-flush-func' Indicates that there is no OS function for flushing the cache. +  File: gcc.info, Node: M680x0 Options, Next: MCore Options, Prev: M32R/D Options, Up: Submodel Options 3.18.22 M680x0 Options ---------------------- ! These are the `-m' options defined for M680x0 and ColdFire processors. The default settings depend on which architecture was selected when the compiler was configured; the defaults for the most common choices are given below. ! `-march=ARCH' Generate code for a specific M680x0 or ColdFire instruction set architecture. Permissible values of ARCH for M680x0 architectures ! are: `68000', `68010', `68020', `68030', `68040', `68060' and ! `cpu32'. ColdFire architectures are selected according to Freescale's ISA classification and the permissible values are: ! `isaa', `isaaplus', `isab' and `isac'. ! GCC defines a macro `__mcfARCH__' whenever it is generating code for a ColdFire target. The ARCH in this macro is one of the ! `-march' arguments given above. ! When used together, `-march' and `-mtune' select code that runs on a family of similar processors but that is optimized for a particular microarchitecture. ! `-mcpu=CPU' Generate code for a specific M680x0 or ColdFire processor. The ! M680x0 CPUs are: `68000', `68010', `68020', `68030', `68040', ! `68060', `68302', `68332' and `cpu32'. The ColdFire CPUs are ! given by the table below, which also classifies the CPUs into ! families: ! *Family* *`-mcpu' arguments* ! `51' `51' `51ac' `51ag' `51cn' `51em' `51je' `51jf' `51jg' ! `51jm' `51mm' `51qe' `51qm' ! `5206' `5202' `5204' `5206' ! `5206e' `5206e' ! `5208' `5207' `5208' ! `5211a' `5210a' `5211a' ! `5213' `5211' `5212' `5213' ! `5216' `5214' `5216' ! `52235' `52230' `52231' `52232' `52233' `52234' `52235' ! `5225' `5224' `5225' ! `52259' `52252' `52254' `52255' `52256' `52258' `52259' ! `5235' `5232' `5233' `5234' `5235' `523x' ! `5249' `5249' ! `5250' `5250' ! `5271' `5270' `5271' ! `5272' `5272' ! `5275' `5274' `5275' ! `5282' `5280' `5281' `5282' `528x' ! `53017' `53011' `53012' `53013' `53014' `53015' `53016' ! `53017' ! `5307' `5307' ! `5329' `5327' `5328' `5329' `532x' ! `5373' `5372' `5373' `537x' ! `5407' `5407' ! `5475' `5470' `5471' `5472' `5473' `5474' `5475' `547x' ! `5480' `5481' `5482' `5483' `5484' `5485' ! `-mcpu=CPU' overrides `-march=ARCH' if ARCH is compatible with ! CPU. Other combinations of `-mcpu' and `-march' are rejected. ! GCC defines the macro `__mcf_cpu_CPU' when ColdFire target CPU is ! selected. It also defines `__mcf_family_FAMILY', where the value of FAMILY is given by the table above. ! `-mtune=TUNE' Tune the code for a particular microarchitecture within the ! constraints set by `-march' and `-mcpu'. The M680x0 ! microarchitectures are: `68000', `68010', `68020', `68030', ! `68040', `68060' and `cpu32'. The ColdFire microarchitectures ! are: `cfv1', `cfv2', `cfv3', `cfv4' and `cfv4e'. ! You can also use `-mtune=68020-40' for code that needs to run relatively well on 68020, 68030 and 68040 targets. ! `-mtune=68020-60' is similar but includes 68060 targets as well. ! These two options select the same tuning decisions as `-m68020-40' ! and `-m68020-60' respectively. ! GCC defines the macros `__mcARCH' and `__mcARCH__' when tuning for ! 680x0 architecture ARCH. It also defines `mcARCH' unless either ! `-ansi' or a non-GNU `-std' option is used. If GCC is tuning for ! a range of architectures, as selected by `-mtune=68020-40' or ! `-mtune=68020-60', it defines the macros for every architecture in the range. ! GCC also defines the macro `__mUARCH__' when tuning for ColdFire microarchitecture UARCH, where UARCH is one of the arguments given above. ! `-m68000' ! `-mc68000' ! Generate output for a 68000. This is the default when the ! compiler is configured for 68000-based systems. It is equivalent ! to `-march=68000'. Use this option for microcontrollers with a 68000 or EC000 core, including the 68008, 68302, 68306, 68307, 68322, 68328 and 68356. ! `-m68010' ! Generate output for a 68010. This is the default when the ! compiler is configured for 68010-based systems. It is equivalent ! to `-march=68010'. ! `-m68020' ! `-mc68020' ! Generate output for a 68020. This is the default when the ! compiler is configured for 68020-based systems. It is equivalent ! to `-march=68020'. ! `-m68030' ! Generate output for a 68030. This is the default when the ! compiler is configured for 68030-based systems. It is equivalent ! to `-march=68030'. ! `-m68040' ! Generate output for a 68040. This is the default when the ! compiler is configured for 68040-based systems. It is equivalent ! to `-march=68040'. This option inhibits the use of 68881/68882 instructions that have to be emulated by software on the 68040. Use this option if your 68040 does not have code to emulate those instructions. ! `-m68060' ! Generate output for a 68060. This is the default when the ! compiler is configured for 68060-based systems. It is equivalent ! to `-march=68060'. This option inhibits the use of 68020 and 68881/68882 instructions ! that have to be emulated by software on the 68060. Use this ! option if your 68060 does not have code to emulate those ! instructions. ! `-mcpu32' ! Generate output for a CPU32. This is the default when the ! compiler is configured for CPU32-based systems. It is equivalent ! to `-march=cpu32'. Use this option for microcontrollers with a CPU32 or CPU32+ core, including the 68330, 68331, 68332, 68333, 68334, 68336, 68340, 68341, 68349 and 68360. ! `-m5200' Generate output for a 520X ColdFire CPU. This is the default when the compiler is configured for 520X-based systems. It is ! equivalent to `-mcpu=5206', and is now deprecated in favor of that option. ! Use this option for microcontroller with a 5200 core, including ! the MCF5202, MCF5203, MCF5204 and MCF5206. ! `-m5206e' Generate output for a 5206e ColdFire CPU. The option is now ! deprecated in favor of the equivalent `-mcpu=5206e'. ! `-m528x' Generate output for a member of the ColdFire 528X family. The ! option is now deprecated in favor of the equivalent `-mcpu=528x'. ! `-m5307' Generate output for a ColdFire 5307 CPU. The option is now ! deprecated in favor of the equivalent `-mcpu=5307'. ! `-m5407' Generate output for a ColdFire 5407 CPU. The option is now ! deprecated in favor of the equivalent `-mcpu=5407'. ! `-mcfv4e' Generate output for a ColdFire V4e family CPU (e.g. 547x/548x). This includes use of hardware floating-point instructions. The ! option is equivalent to `-mcpu=547x', and is now deprecated in favor of that option. ! `-m68020-40' Generate output for a 68040, without using any of the new instructions. This results in code that can run relatively efficiently on either a 68020/68881 or a 68030 or a 68040. The ! generated code does use the 68881 instructions that are emulated ! on the 68040. ! The option is equivalent to `-march=68020' `-mtune=68020-40'. ! `-m68020-60' Generate output for a 68060, without using any of the new instructions. This results in code that can run relatively efficiently on either a 68020/68881 or a 68030 or a 68040. The ! generated code does use the 68881 instructions that are emulated ! on the 68060. ! The option is equivalent to `-march=68020' `-mtune=68020-60'. ! `-mhard-float' ! `-m68881' Generate floating-point instructions. This is the default for 68020 and above, and for ColdFire devices that have an FPU. It ! defines the macro `__HAVE_68881__' on M680x0 targets and ! `__mcffpu__' on ColdFire targets. ! `-msoft-float' Do not generate floating-point instructions; use library calls instead. This is the default for 68000, 68010, and 68832 targets. It is also the default for ColdFire devices that have no FPU. ! `-mdiv' ! `-mno-div' Generate (do not generate) ColdFire hardware divide and remainder ! instructions. If `-march' is used without `-mcpu', the default is ! "on" for ColdFire architectures and "off" for M680x0 ! architectures. Otherwise, the default is taken from the target CPU ! (either the default CPU, or the one specified by `-mcpu'). For ! example, the default is "off" for `-mcpu=5206' and "on" for ! `-mcpu=5206e'. ! GCC defines the macro `__mcfhwdiv__' when this option is enabled. ! `-mshort' ! Consider type `int' to be 16 bits wide, like `short int'. Additionally, parameters passed on the stack are also aligned to a 16-bit boundary even on targets whose API mandates promotion to 32-bit. ! `-mno-short' ! Do not consider type `int' to be 16 bits wide. This is the default. ! `-mnobitfield' ! `-mno-bitfield' ! Do not use the bit-field instructions. The `-m68000', `-mcpu32' ! and `-m5200' options imply `-mnobitfield'. ! `-mbitfield' ! Do use the bit-field instructions. The `-m68020' option implies ! `-mbitfield'. This is the default if you use a configuration designed for a 68020. ! `-mrtd' Use a different function-calling convention, in which functions ! that take a fixed number of arguments return with the `rtd' instruction, which pops their arguments while returning. This saves one instruction in the caller since there is no need to pop the arguments there. *************** given below. *** 16199,16276 **** compiled with the Unix compiler. Also, you must provide function prototypes for all functions that ! take variable numbers of arguments (including 'printf'); otherwise incorrect code is generated for calls to those functions. In addition, seriously incorrect code results if you call a function with too many arguments. (Normally, extra arguments are harmlessly ignored.) ! The 'rtd' instruction is supported by the 68010, 68020, 68030, 68040, 68060 and CPU32 processors, but not by the 68000 or 5200. ! '-mno-rtd' ! Do not use the calling conventions selected by '-mrtd'. This is the default. ! '-malign-int' ! '-mno-align-int' ! Control whether GCC aligns 'int', 'long', 'long long', 'float', ! 'double', and 'long double' variables on a 32-bit boundary ! ('-malign-int') or a 16-bit boundary ('-mno-align-int'). Aligning variables on 32-bit boundaries produces code that runs somewhat faster on processors with 32-bit busses at the expense of more memory. ! *Warning:* if you use the '-malign-int' switch, GCC aligns structures containing the above types differently than most published application binary interface specifications for the m68k. ! '-mpcrel' Use the pc-relative addressing mode of the 68000 directly, instead of using a global offset table. At present, this option implies ! '-fpic', allowing at most a 16-bit offset for pc-relative ! addressing. '-fPIC' is not presently supported with '-mpcrel', though this could be supported for 68020 and higher processors. ! '-mno-strict-align' ! '-mstrict-align' Do not (do) assume that unaligned memory references are handled by the system. ! '-msep-data' Generate code that allows the data segment to be located in a different area of memory from the text segment. This allows for execute-in-place in an environment without virtual memory ! management. This option implies '-fPIC'. ! '-mno-sep-data' Generate code that assumes that the data segment follows the text segment. This is the default. ! '-mid-shared-library' Generate code that supports shared libraries via the library ID method. This allows for execute-in-place and shared libraries in an environment without virtual memory management. This option ! implies '-fPIC'. ! '-mno-id-shared-library' Generate code that doesn't assume ID-based shared libraries are being used. This is the default. ! '-mshared-library-id=n' Specifies the identification number of the ID-based shared library being compiled. Specifying a value of 0 generates more compact code; specifying other values forces the allocation of that number to the current library, but is no more space- or time-efficient than omitting this option. ! '-mxgot' ! '-mno-xgot' When generating position-independent code for ColdFire, generate code that works if the GOT has more than 8192 entries. This code is larger and slower than code generated without this option. On ! M680x0 processors, this option is not needed; '-fPIC' suffices. GCC normally uses a single instruction to load values from the GOT. While this is relatively efficient, it only works if the GOT is --- 16288,16365 ---- compiled with the Unix compiler. Also, you must provide function prototypes for all functions that ! take variable numbers of arguments (including `printf'); otherwise incorrect code is generated for calls to those functions. In addition, seriously incorrect code results if you call a function with too many arguments. (Normally, extra arguments are harmlessly ignored.) ! The `rtd' instruction is supported by the 68010, 68020, 68030, 68040, 68060 and CPU32 processors, but not by the 68000 or 5200. ! `-mno-rtd' ! Do not use the calling conventions selected by `-mrtd'. This is the default. ! `-malign-int' ! `-mno-align-int' ! Control whether GCC aligns `int', `long', `long long', `float', ! `double', and `long double' variables on a 32-bit boundary ! (`-malign-int') or a 16-bit boundary (`-mno-align-int'). Aligning variables on 32-bit boundaries produces code that runs somewhat faster on processors with 32-bit busses at the expense of more memory. ! *Warning:* if you use the `-malign-int' switch, GCC aligns structures containing the above types differently than most published application binary interface specifications for the m68k. ! `-mpcrel' Use the pc-relative addressing mode of the 68000 directly, instead of using a global offset table. At present, this option implies ! `-fpic', allowing at most a 16-bit offset for pc-relative ! addressing. `-fPIC' is not presently supported with `-mpcrel', though this could be supported for 68020 and higher processors. ! `-mno-strict-align' ! `-mstrict-align' Do not (do) assume that unaligned memory references are handled by the system. ! `-msep-data' Generate code that allows the data segment to be located in a different area of memory from the text segment. This allows for execute-in-place in an environment without virtual memory ! management. This option implies `-fPIC'. ! `-mno-sep-data' Generate code that assumes that the data segment follows the text segment. This is the default. ! `-mid-shared-library' Generate code that supports shared libraries via the library ID method. This allows for execute-in-place and shared libraries in an environment without virtual memory management. This option ! implies `-fPIC'. ! `-mno-id-shared-library' Generate code that doesn't assume ID-based shared libraries are being used. This is the default. ! `-mshared-library-id=n' Specifies the identification number of the ID-based shared library being compiled. Specifying a value of 0 generates more compact code; specifying other values forces the allocation of that number to the current library, but is no more space- or time-efficient than omitting this option. ! `-mxgot' ! `-mno-xgot' When generating position-independent code for ColdFire, generate code that works if the GOT has more than 8192 entries. This code is larger and slower than code generated without this option. On ! M680x0 processors, this option is not needed; `-fPIC' suffices. GCC normally uses a single instruction to load values from the GOT. While this is relatively efficient, it only works if the GOT is *************** given below. *** 16279,16483 **** relocation truncated to fit: R_68K_GOT16O foobar ! If this happens, you should recompile your code with '-mxgot'. It should then work with very large GOTs. However, code generated ! with '-mxgot' is less efficient, since it takes 4 instructions to fetch the value of a global symbol. Note that some linkers, including newer versions of the GNU linker, can create multiple GOTs and sort GOT entries. If you have such a ! linker, you should only need to use '-mxgot' when compiling a single object file that accesses more than 8192 GOT entries. Very few do. These options have no effect unless GCC is generating position-independent code.  File: gcc.info, Node: MCore Options, Next: MeP Options, Prev: M680x0 Options, Up: Submodel Options 3.18.23 MCore Options --------------------- ! These are the '-m' options defined for the Motorola M*Core processors. ! '-mhardlit' ! '-mno-hardlit' Inline constants into the code stream if it can be done in two instructions or less. ! '-mdiv' ! '-mno-div' Use the divide instruction. (Enabled by default). ! '-mrelax-immediate' ! '-mno-relax-immediate' Allow arbitrary-sized immediates in bit operations. ! '-mwide-bitfields' ! '-mno-wide-bitfields' ! Always treat bit-fields as 'int'-sized. ! '-m4byte-functions' ! '-mno-4byte-functions' Force all functions to be aligned to a 4-byte boundary. ! '-mcallgraph-data' ! '-mno-callgraph-data' Emit callgraph information. ! '-mslow-bytes' ! '-mno-slow-bytes' Prefer word access when reading byte quantities. ! '-mlittle-endian' ! '-mbig-endian' Generate code for a little-endian target. ! '-m210' ! '-m340' Generate code for the 210 processor. ! '-mno-lsim' Assume that runtime support has been provided and so omit the ! simulator library ('libsim.a)' from the linker command line. ! '-mstack-increment=SIZE' Set the maximum amount for a single stack increment operation. Large values can increase the speed of programs that contain functions that need a large amount of stack space, but they can also trigger a segmentation fault if the stack is extended too much. The default value is 0x1000.  File: gcc.info, Node: MeP Options, Next: MicroBlaze Options, Prev: MCore Options, Up: Submodel Options 3.18.24 MeP Options ------------------- ! '-mabsdiff' ! Enables the 'abs' instruction, which is the absolute difference between two registers. ! '-mall-opts' Enables all the optional instructions--average, multiply, divide, bit operations, leading zero, absolute difference, min/max, clip, and saturation. ! '-maverage' ! Enables the 'ave' instruction, which computes the average of two registers. ! '-mbased=N' ! Variables of size N bytes or smaller are placed in the '.based' ! section by default. Based variables use the '$tp' register as a ! base register, and there is a 128-byte limit to the '.based' section. ! '-mbitops' ! Enables the bit operation instructions--bit test ('btstm'), set ! ('bsetm'), clear ('bclrm'), invert ('bnotm'), and test-and-set ! ('tas'). ! '-mc=NAME' Selects which section constant data is placed in. NAME may be ! 'tiny', 'near', or 'far'. ! '-mclip' ! Enables the 'clip' instruction. Note that '-mclip' is not useful ! unless you also provide '-mminmax'. ! '-mconfig=NAME' Selects one of the built-in core configurations. Each MeP chip has ! one or more modules in it; each module has a core CPU and a variety ! of coprocessors, optional instructions, and peripherals. The ! 'MeP-Integrator' tool, not part of GCC, provides these configurations through this option; using this option is the same as using all the corresponding command-line options. The default ! configuration is 'default'. ! '-mcop' Enables the coprocessor instructions. By default, this is a 32-bit coprocessor. Note that the coprocessor is normally enabled via the ! '-mconfig=' option. ! '-mcop32' Enables the 32-bit coprocessor's instructions. ! '-mcop64' Enables the 64-bit coprocessor's instructions. ! '-mivc2' Enables IVC2 scheduling. IVC2 is a 64-bit VLIW coprocessor. ! '-mdc' ! Causes constant variables to be placed in the '.near' section. ! '-mdiv' ! Enables the 'div' and 'divu' instructions. ! '-meb' Generate big-endian code. ! '-mel' Generate little-endian code. ! '-mio-volatile' ! Tells the compiler that any variable marked with the 'io' attribute ! is to be considered volatile. ! '-ml' ! Causes variables to be assigned to the '.far' section by default. ! '-mleadz' ! Enables the 'leadz' (leading zero) instruction. ! '-mm' ! Causes variables to be assigned to the '.near' section by default. ! '-mminmax' ! Enables the 'min' and 'max' instructions. ! '-mmult' Enables the multiplication and multiply-accumulate instructions. ! '-mno-opts' ! Disables all the optional instructions enabled by '-mall-opts'. ! '-mrepeat' ! Enables the 'repeat' and 'erepeat' instructions, used for low-overhead looping. ! '-ms' ! Causes all variables to default to the '.tiny' section. Note that there is a 65536-byte limit to this section. Accesses to these ! variables use the '%gp' base register. ! '-msatur' Enables the saturation instructions. Note that the compiler does not currently generate these itself, but this option is included ! for compatibility with other tools, like 'as'. ! '-msdram' Link the SDRAM-based runtime instead of the default ROM-based runtime. ! '-msim' Link the simulator run-time libraries. ! '-msimnovec' Link the simulator runtime libraries, excluding built-in support for reset and exception vectors and tables. ! '-mtf' ! Causes all functions to default to the '.far' section. Without ! this option, functions default to the '.near' section. - '-mtiny=N' - Variables that are N bytes or smaller are allocated to the '.tiny' - section. These variables use the '$gp' base register. The default - for this option is 4, but note that there's a 65536-byte limit to - the '.tiny' section.  File: gcc.info, Node: MicroBlaze Options, Next: MIPS Options, Prev: MeP Options, Up: Submodel Options --- 16368,16575 ---- relocation truncated to fit: R_68K_GOT16O foobar ! If this happens, you should recompile your code with `-mxgot'. It should then work with very large GOTs. However, code generated ! with `-mxgot' is less efficient, since it takes 4 instructions to fetch the value of a global symbol. Note that some linkers, including newer versions of the GNU linker, can create multiple GOTs and sort GOT entries. If you have such a ! linker, you should only need to use `-mxgot' when compiling a single object file that accesses more than 8192 GOT entries. Very few do. These options have no effect unless GCC is generating position-independent code. +  File: gcc.info, Node: MCore Options, Next: MeP Options, Prev: M680x0 Options, Up: Submodel Options 3.18.23 MCore Options --------------------- ! These are the `-m' options defined for the Motorola M*Core processors. ! `-mhardlit' ! `-mno-hardlit' Inline constants into the code stream if it can be done in two instructions or less. ! `-mdiv' ! `-mno-div' Use the divide instruction. (Enabled by default). ! `-mrelax-immediate' ! `-mno-relax-immediate' Allow arbitrary-sized immediates in bit operations. ! `-mwide-bitfields' ! `-mno-wide-bitfields' ! Always treat bit-fields as `int'-sized. ! `-m4byte-functions' ! `-mno-4byte-functions' Force all functions to be aligned to a 4-byte boundary. ! `-mcallgraph-data' ! `-mno-callgraph-data' Emit callgraph information. ! `-mslow-bytes' ! `-mno-slow-bytes' Prefer word access when reading byte quantities. ! `-mlittle-endian' ! `-mbig-endian' Generate code for a little-endian target. ! `-m210' ! `-m340' Generate code for the 210 processor. ! `-mno-lsim' Assume that runtime support has been provided and so omit the ! simulator library (`libsim.a)' from the linker command line. ! `-mstack-increment=SIZE' Set the maximum amount for a single stack increment operation. Large values can increase the speed of programs that contain functions that need a large amount of stack space, but they can also trigger a segmentation fault if the stack is extended too much. The default value is 0x1000. +  File: gcc.info, Node: MeP Options, Next: MicroBlaze Options, Prev: MCore Options, Up: Submodel Options 3.18.24 MeP Options ------------------- ! `-mabsdiff' ! Enables the `abs' instruction, which is the absolute difference between two registers. ! `-mall-opts' Enables all the optional instructions--average, multiply, divide, bit operations, leading zero, absolute difference, min/max, clip, and saturation. ! `-maverage' ! Enables the `ave' instruction, which computes the average of two registers. ! `-mbased=N' ! Variables of size N bytes or smaller are placed in the `.based' ! section by default. Based variables use the `$tp' register as a ! base register, and there is a 128-byte limit to the `.based' section. ! `-mbitops' ! Enables the bit operation instructions--bit test (`btstm'), set ! (`bsetm'), clear (`bclrm'), invert (`bnotm'), and test-and-set ! (`tas'). ! `-mc=NAME' Selects which section constant data is placed in. NAME may be ! `tiny', `near', or `far'. ! `-mclip' ! Enables the `clip' instruction. Note that `-mclip' is not useful ! unless you also provide `-mminmax'. ! `-mconfig=NAME' Selects one of the built-in core configurations. Each MeP chip has ! one or more modules in it; each module has a core CPU and a ! variety of coprocessors, optional instructions, and peripherals. ! The `MeP-Integrator' tool, not part of GCC, provides these configurations through this option; using this option is the same as using all the corresponding command-line options. The default ! configuration is `default'. ! `-mcop' Enables the coprocessor instructions. By default, this is a 32-bit coprocessor. Note that the coprocessor is normally enabled via the ! `-mconfig=' option. ! `-mcop32' Enables the 32-bit coprocessor's instructions. ! `-mcop64' Enables the 64-bit coprocessor's instructions. ! `-mivc2' Enables IVC2 scheduling. IVC2 is a 64-bit VLIW coprocessor. ! `-mdc' ! Causes constant variables to be placed in the `.near' section. ! `-mdiv' ! Enables the `div' and `divu' instructions. ! `-meb' Generate big-endian code. ! `-mel' Generate little-endian code. ! `-mio-volatile' ! Tells the compiler that any variable marked with the `io' ! attribute is to be considered volatile. ! `-ml' ! Causes variables to be assigned to the `.far' section by default. ! `-mleadz' ! Enables the `leadz' (leading zero) instruction. ! `-mm' ! Causes variables to be assigned to the `.near' section by default. ! `-mminmax' ! Enables the `min' and `max' instructions. ! `-mmult' Enables the multiplication and multiply-accumulate instructions. ! `-mno-opts' ! Disables all the optional instructions enabled by `-mall-opts'. ! `-mrepeat' ! Enables the `repeat' and `erepeat' instructions, used for low-overhead looping. ! `-ms' ! Causes all variables to default to the `.tiny' section. Note that there is a 65536-byte limit to this section. Accesses to these ! variables use the `%gp' base register. ! `-msatur' Enables the saturation instructions. Note that the compiler does not currently generate these itself, but this option is included ! for compatibility with other tools, like `as'. ! `-msdram' Link the SDRAM-based runtime instead of the default ROM-based runtime. ! `-msim' Link the simulator run-time libraries. ! `-msimnovec' Link the simulator runtime libraries, excluding built-in support for reset and exception vectors and tables. ! `-mtf' ! Causes all functions to default to the `.far' section. Without ! this option, functions default to the `.near' section. ! ! `-mtiny=N' ! Variables that are N bytes or smaller are allocated to the `.tiny' ! section. These variables use the `$gp' base register. The ! default for this option is 4, but note that there's a 65536-byte ! limit to the `.tiny' section.  File: gcc.info, Node: MicroBlaze Options, Next: MIPS Options, Prev: MeP Options, Up: Submodel Options *************** File: gcc.info, Node: MicroBlaze Option *** 16485,16575 **** 3.18.25 MicroBlaze Options -------------------------- ! '-msoft-float' Use software emulation for floating point (default). ! '-mhard-float' Use hardware floating-point instructions. ! '-mmemcpy' ! Do not optimize block moves, use 'memcpy'. ! '-mno-clearbss' ! This option is deprecated. Use '-fno-zero-initialized-in-bss' instead. ! '-mcpu=CPU-TYPE' ! Use features of, and schedule code for, the given CPU. Supported ! values are in the format 'vX.YY.Z', where X is a major version, YY is the minor version, and Z is compatibility code. Example values ! are 'v3.00.a', 'v4.00.b', 'v5.00.a', 'v5.00.b', 'v5.00.b', ! 'v6.00.a'. ! '-mxl-soft-mul' Use software multiply emulation (default). ! '-mxl-soft-div' Use software emulation for divides (default). ! '-mxl-barrel-shift' Use the hardware barrel shifter. ! '-mxl-pattern-compare' Use pattern compare instructions. ! '-msmall-divides' Use table lookup optimization for small signed integer divisions. ! '-mxl-stack-check' ! This option is deprecated. Use '-fstack-check' instead. ! '-mxl-gp-opt' ! Use GP-relative '.sdata'/'.sbss' sections. ! '-mxl-multiply-high' Use multiply high instructions for high part of 32x32 multiply. ! '-mxl-float-convert' Use hardware floating-point conversion instructions. ! '-mxl-float-sqrt' Use hardware floating-point square root instruction. ! '-mbig-endian' Generate code for a big-endian target. ! '-mlittle-endian' Generate code for a little-endian target. ! '-mxl-reorder' Use reorder instructions (swap and byte reversed load/store). ! '-mxl-mode-APP-MODEL' Select application model APP-MODEL. Valid models are ! 'executable' ! normal executable (default), uses startup code 'crt0.o'. ! 'xmdstub' for use with Xilinx Microprocessor Debugger (XMD) based ! software intrusive debug agent called xmdstub. This uses ! startup file 'crt1.o' and sets the start address of the program to 0x800. ! 'bootstrap' for applications that are loaded using a bootloader. This ! model uses startup file 'crt2.o' which does not contain a ! processor reset vector handler. This is suitable for transferring control on a processor reset to the bootloader rather than the application. ! 'novectors' for applications that do not require any of the MicroBlaze ! vectors. This option may be useful for applications running ! within a monitoring application. This model uses 'crt3.o' as a startup file. ! Option '-xl-mode-APP-MODEL' is a deprecated alias for ! '-mxl-mode-APP-MODEL'.  File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Options, Up: Submodel Options --- 16577,16668 ---- 3.18.25 MicroBlaze Options -------------------------- ! `-msoft-float' Use software emulation for floating point (default). ! `-mhard-float' Use hardware floating-point instructions. ! `-mmemcpy' ! Do not optimize block moves, use `memcpy'. ! `-mno-clearbss' ! This option is deprecated. Use `-fno-zero-initialized-in-bss' instead. ! `-mcpu=CPU-TYPE' ! Use features of, and schedule code for, the given CPU. Supported ! values are in the format `vX.YY.Z', where X is a major version, YY is the minor version, and Z is compatibility code. Example values ! are `v3.00.a', `v4.00.b', `v5.00.a', `v5.00.b', `v5.00.b', ! `v6.00.a'. ! `-mxl-soft-mul' Use software multiply emulation (default). ! `-mxl-soft-div' Use software emulation for divides (default). ! `-mxl-barrel-shift' Use the hardware barrel shifter. ! `-mxl-pattern-compare' Use pattern compare instructions. ! `-msmall-divides' Use table lookup optimization for small signed integer divisions. ! `-mxl-stack-check' ! This option is deprecated. Use `-fstack-check' instead. ! `-mxl-gp-opt' ! Use GP-relative `.sdata'/`.sbss' sections. ! `-mxl-multiply-high' Use multiply high instructions for high part of 32x32 multiply. ! `-mxl-float-convert' Use hardware floating-point conversion instructions. ! `-mxl-float-sqrt' Use hardware floating-point square root instruction. ! `-mbig-endian' Generate code for a big-endian target. ! `-mlittle-endian' Generate code for a little-endian target. ! `-mxl-reorder' Use reorder instructions (swap and byte reversed load/store). ! `-mxl-mode-APP-MODEL' Select application model APP-MODEL. Valid models are ! `executable' ! normal executable (default), uses startup code `crt0.o'. ! `xmdstub' for use with Xilinx Microprocessor Debugger (XMD) based ! software intrusive debug agent called xmdstub. This uses ! startup file `crt1.o' and sets the start address of the program to 0x800. ! `bootstrap' for applications that are loaded using a bootloader. This ! model uses startup file `crt2.o' which does not contain a ! processor reset vector handler. This is suitable for transferring control on a processor reset to the bootloader rather than the application. ! `novectors' for applications that do not require any of the MicroBlaze ! vectors. This option may be useful for applications running ! within a monitoring application. This model uses `crt3.o' as a startup file. ! Option `-xl-mode-APP-MODEL' is a deprecated alias for ! `-mxl-mode-APP-MODEL'. !  File: gcc.info, Node: MIPS Options, Next: MMIX Options, Prev: MicroBlaze Options, Up: Submodel Options *************** File: gcc.info, Node: MIPS Options, Ne *** 16577,16804 **** 3.18.26 MIPS Options -------------------- ! '-EB' Generate big-endian code. ! '-EL' ! Generate little-endian code. This is the default for 'mips*el-*-*' configurations. ! '-march=ARCH' ! Generate code that runs on ARCH, which can be the name of a generic ! MIPS ISA, or the name of a particular processor. The ISA names ! are: 'mips1', 'mips2', 'mips3', 'mips4', 'mips32', 'mips32r2', ! 'mips32r3', 'mips32r5', 'mips32r6', 'mips64', 'mips64r2', ! 'mips64r3', 'mips64r5' and 'mips64r6'. The processor names are: ! '4kc', '4km', '4kp', '4ksc', '4kec', '4kem', '4kep', '4ksd', '5kc', ! '5kf', '20kc', '24kc', '24kf2_1', '24kf1_1', '24kec', '24kef2_1', ! '24kef1_1', '34kc', '34kf2_1', '34kf1_1', '34kn', '74kc', ! '74kf2_1', '74kf1_1', '74kf3_2', '1004kc', '1004kf2_1', ! '1004kf1_1', 'i6400', 'interaptiv', 'loongson2e', 'loongson2f', ! 'loongson3a', 'm4k', 'm14k', 'm14kc', 'm14ke', 'm14kec', 'm5100', ! 'm5101', 'octeon', 'octeon+', 'octeon2', 'octeon3', 'orion', ! 'p5600', 'r2000', 'r3000', 'r3900', 'r4000', 'r4400', 'r4600', ! 'r4650', 'r4700', 'r6000', 'r8000', 'rm7000', 'rm9000', 'r10000', ! 'r12000', 'r14000', 'r16000', 'sb1', 'sr71000', 'vr4100', 'vr4111', ! 'vr4120', 'vr4130', 'vr4300', 'vr5000', 'vr5400', 'vr5500', 'xlr' ! and 'xlp'. The special value 'from-abi' selects the most ! compatible architecture for the selected ABI (that is, 'mips1' for ! 32-bit ABIs and 'mips3' for 64-bit ABIs). ! The native Linux/GNU toolchain also supports the value 'native', which selects the best architecture option for the host processor. ! '-march=native' has no effect if GCC does not recognize the processor. ! In processor names, a final '000' can be abbreviated as 'k' (for ! example, '-march=r2k'). Prefixes are optional, and 'vr' may be ! written 'r'. ! Names of the form 'Nf2_1' refer to processors with FPUs clocked at ! half the rate of the core, names of the form 'Nf1_1' refer to processors with FPUs clocked at the same rate as the core, and ! names of the form 'Nf3_2' refer to processors with FPUs clocked a ratio of 3:2 with respect to the core. For compatibility reasons, ! 'Nf' is accepted as a synonym for 'Nf2_1' while 'Nx' and 'Bfx' are ! accepted as synonyms for 'Nf1_1'. GCC defines two macros based on the value of this option. The ! first is '_MIPS_ARCH', which gives the name of target architecture, ! as a string. The second has the form '_MIPS_ARCH_FOO', where FOO ! is the capitalized value of '_MIPS_ARCH'. For example, ! '-march=r2000' sets '_MIPS_ARCH' to '"r2000"' and defines the macro ! '_MIPS_ARCH_R2000'. ! Note that the '_MIPS_ARCH' macro uses the processor names given above. In other words, it has the full prefix and does not ! abbreviate '000' as 'k'. In the case of 'from-abi', the macro ! names the resolved architecture (either '"mips1"' or '"mips3"'). ! It names the default architecture when no '-march' option is given. ! '-mtune=ARCH' Optimize for ARCH. Among other things, this option controls the way instructions are scheduled, and the perceived cost of arithmetic operations. The list of ARCH values is the same as for ! '-march'. When this option is not used, GCC optimizes for the processor ! specified by '-march'. By using '-march' and '-mtune' together, it ! is possible to generate code that runs on a family of processors, ! but optimize the code for one particular member of that family. ! '-mtune' defines the macros '_MIPS_TUNE' and '_MIPS_TUNE_FOO', ! which work in the same way as the '-march' ones described above. ! '-mips1' ! Equivalent to '-march=mips1'. ! '-mips2' ! Equivalent to '-march=mips2'. ! '-mips3' ! Equivalent to '-march=mips3'. ! '-mips4' ! Equivalent to '-march=mips4'. ! '-mips32' ! Equivalent to '-march=mips32'. ! '-mips32r3' ! Equivalent to '-march=mips32r3'. ! '-mips32r5' ! Equivalent to '-march=mips32r5'. ! '-mips32r6' ! Equivalent to '-march=mips32r6'. ! '-mips64' ! Equivalent to '-march=mips64'. ! '-mips64r2' ! Equivalent to '-march=mips64r2'. ! '-mips64r3' ! Equivalent to '-march=mips64r3'. ! '-mips64r5' ! Equivalent to '-march=mips64r5'. ! '-mips64r6' ! Equivalent to '-march=mips64r6'. ! '-mips16' ! '-mno-mips16' Generate (do not generate) MIPS16 code. If GCC is targeting a MIPS32 or MIPS64 architecture, it makes use of the MIPS16e ASE. MIPS16 code generation can also be controlled on a per-function ! basis by means of 'mips16' and 'nomips16' attributes. *Note Function Attributes::, for more information. ! '-mflip-mips16' Generate MIPS16 code on alternating functions. This option is provided for regression testing of mixed MIPS16/non-MIPS16 code generation, and is not intended for ordinary use in compiling user code. ! '-minterlink-compressed' ! '-mno-interlink-compressed' Require (do not require) that code using the standard (uncompressed) MIPS ISA be link-compatible with MIPS16 and microMIPS code, and vice versa. For example, code using the standard ISA encoding cannot jump directly to MIPS16 or microMIPS code; it must either use a call or ! an indirect jump. '-minterlink-compressed' therefore disables direct jumps unless GCC knows that the target of the jump is not compressed. ! '-minterlink-mips16' ! '-mno-interlink-mips16' ! Aliases of '-minterlink-compressed' and ! '-mno-interlink-compressed'. These options predate the microMIPS ASE and are retained for backwards compatibility. ! '-mabi=32' ! '-mabi=o64' ! '-mabi=n32' ! '-mabi=64' ! '-mabi=eabi' Generate code for the given ABI. Note that the EABI has a 32-bit and a 64-bit variant. GCC normally generates 64-bit code when you select a 64-bit architecture, but ! you can use '-mgp32' to get 32-bit code instead. For information about the O64 ABI, see ! . GCC supports a variant of the o32 ABI in which floating-point registers are 64 rather than 32 bits wide. You can select this ! combination with '-mabi=32' '-mfp64'. This ABI relies on the ! 'mthc1' and 'mfhc1' instructions and is therefore only supported for MIPS32R2, MIPS32R3 and MIPS32R5 processors. The register assignments for arguments and return values remain the same, but each scalar value is passed in a single 64-bit register rather than a pair of 32-bit registers. For example, scalar ! floating-point values are returned in '$f0' only, not a '$f0'/'$f1' ! pair. The set of call-saved registers also remains the same in ! that the even-numbered double-precision registers are saved. Two additional variants of the o32 ABI are supported to enable a transition from 32-bit to 64-bit registers. These are FPXX ! ('-mfpxx') and FP64A ('-mfp64' '-mno-odd-spreg'). The FPXX extension mandates that all code must execute correctly when run ! using 32-bit or 64-bit registers. The code can be interlinked with ! either FP32 or FP64, but not both. The FP64A extension is similar ! to the FP64 extension but forbids the use of odd-numbered single-precision registers. This can be used in conjunction with ! the 'FRE' mode of FPUs in MIPS32R5 processors and allows both FP32 and FP64A code to interlink and run in the same process without changing FPU modes. ! '-mabicalls' ! '-mno-abicalls' Generate (do not generate) code that is suitable for SVR4-style ! dynamic objects. '-mabicalls' is the default for SVR4-based systems. ! '-mshared' ! '-mno-shared' Generate (do not generate) code that is fully position-independent, and that can therefore be linked into shared libraries. This ! option only affects '-mabicalls'. ! All '-mabicalls' code has traditionally been position-independent, ! regardless of options like '-fPIC' and '-fpic'. However, as an extension, the GNU toolchain allows executables to use absolute accesses for locally-binding symbols. It can also use shorter GP initialization sequences and generate direct calls to ! locally-defined functions. This mode is selected by '-mno-shared'. ! '-mno-shared' depends on binutils 2.16 or higher and generates objects that can only be linked by the GNU linker. However, the option does not affect the ABI of the final executable; it only ! affects the ABI of relocatable objects. Using '-mno-shared' generally makes executables both smaller and quicker. ! '-mshared' is the default. ! '-mplt' ! '-mno-plt' Assume (do not assume) that the static and dynamic linkers support ! PLTs and copy relocations. This option only affects '-mno-shared -mabicalls'. For the n64 ABI, this option has no effect without ! '-msym32'. ! You can make '-mplt' the default by configuring GCC with ! '--with-mips-plt'. The default is '-mno-plt' otherwise. ! '-mxgot' ! '-mno-xgot' Lift (do not lift) the usual restrictions on the size of the global offset table. --- 16670,16900 ---- 3.18.26 MIPS Options -------------------- ! `-EB' Generate big-endian code. ! `-EL' ! Generate little-endian code. This is the default for `mips*el-*-*' configurations. ! `-march=ARCH' ! Generate code that runs on ARCH, which can be the name of a ! generic MIPS ISA, or the name of a particular processor. The ISA ! names are: `mips1', `mips2', `mips3', `mips4', `mips32', ! `mips32r2', `mips32r3', `mips32r5', `mips32r6', `mips64', ! `mips64r2', `mips64r3', `mips64r5' and `mips64r6'. The processor ! names are: `4kc', `4km', `4kp', `4ksc', `4kec', `4kem', `4kep', ! `4ksd', `5kc', `5kf', `20kc', `24kc', `24kf2_1', `24kf1_1', ! `24kec', `24kef2_1', `24kef1_1', `34kc', `34kf2_1', `34kf1_1', ! `34kn', `74kc', `74kf2_1', `74kf1_1', `74kf3_2', `1004kc', ! `1004kf2_1', `1004kf1_1', `i6400', `interaptiv', `loongson2e', ! `loongson2f', `loongson3a', `m4k', `m14k', `m14kc', `m14ke', ! `m14kec', `m5100', `m5101', `octeon', `octeon+', `octeon2', ! `octeon3', `orion', `p5600', `r2000', `r3000', `r3900', `r4000', ! `r4400', `r4600', `r4650', `r4700', `r6000', `r8000', `rm7000', ! `rm9000', `r10000', `r12000', `r14000', `r16000', `sb1', `sr71000', ! `vr4100', `vr4111', `vr4120', `vr4130', `vr4300', `vr5000', ! `vr5400', `vr5500', `xlr' and `xlp'. The special value `from-abi' ! selects the most compatible architecture for the selected ABI ! (that is, `mips1' for 32-bit ABIs and `mips3' for 64-bit ABIs). ! The native Linux/GNU toolchain also supports the value `native', which selects the best architecture option for the host processor. ! `-march=native' has no effect if GCC does not recognize the processor. ! In processor names, a final `000' can be abbreviated as `k' (for ! example, `-march=r2k'). Prefixes are optional, and `vr' may be ! written `r'. ! Names of the form `Nf2_1' refer to processors with FPUs clocked at ! half the rate of the core, names of the form `Nf1_1' refer to processors with FPUs clocked at the same rate as the core, and ! names of the form `Nf3_2' refer to processors with FPUs clocked a ratio of 3:2 with respect to the core. For compatibility reasons, ! `Nf' is accepted as a synonym for `Nf2_1' while `Nx' and `Bfx' are ! accepted as synonyms for `Nf1_1'. GCC defines two macros based on the value of this option. The ! first is `_MIPS_ARCH', which gives the name of target ! architecture, as a string. The second has the form ! `_MIPS_ARCH_FOO', where FOO is the capitalized value of ! `_MIPS_ARCH'. For example, `-march=r2000' sets `_MIPS_ARCH' to ! `"r2000"' and defines the macro `_MIPS_ARCH_R2000'. ! Note that the `_MIPS_ARCH' macro uses the processor names given above. In other words, it has the full prefix and does not ! abbreviate `000' as `k'. In the case of `from-abi', the macro ! names the resolved architecture (either `"mips1"' or `"mips3"'). ! It names the default architecture when no `-march' option is given. ! `-mtune=ARCH' Optimize for ARCH. Among other things, this option controls the way instructions are scheduled, and the perceived cost of arithmetic operations. The list of ARCH values is the same as for ! `-march'. When this option is not used, GCC optimizes for the processor ! specified by `-march'. By using `-march' and `-mtune' together, ! it is possible to generate code that runs on a family of ! processors, but optimize the code for one particular member of ! that family. ! `-mtune' defines the macros `_MIPS_TUNE' and `_MIPS_TUNE_FOO', ! which work in the same way as the `-march' ones described above. ! `-mips1' ! Equivalent to `-march=mips1'. ! `-mips2' ! Equivalent to `-march=mips2'. ! `-mips3' ! Equivalent to `-march=mips3'. ! `-mips4' ! Equivalent to `-march=mips4'. ! `-mips32' ! Equivalent to `-march=mips32'. ! `-mips32r3' ! Equivalent to `-march=mips32r3'. ! `-mips32r5' ! Equivalent to `-march=mips32r5'. ! `-mips32r6' ! Equivalent to `-march=mips32r6'. ! `-mips64' ! Equivalent to `-march=mips64'. ! `-mips64r2' ! Equivalent to `-march=mips64r2'. ! `-mips64r3' ! Equivalent to `-march=mips64r3'. ! `-mips64r5' ! Equivalent to `-march=mips64r5'. ! `-mips64r6' ! Equivalent to `-march=mips64r6'. ! `-mips16' ! `-mno-mips16' Generate (do not generate) MIPS16 code. If GCC is targeting a MIPS32 or MIPS64 architecture, it makes use of the MIPS16e ASE. MIPS16 code generation can also be controlled on a per-function ! basis by means of `mips16' and `nomips16' attributes. *Note Function Attributes::, for more information. ! `-mflip-mips16' Generate MIPS16 code on alternating functions. This option is provided for regression testing of mixed MIPS16/non-MIPS16 code generation, and is not intended for ordinary use in compiling user code. ! `-minterlink-compressed' ! ! `-mno-interlink-compressed' Require (do not require) that code using the standard (uncompressed) MIPS ISA be link-compatible with MIPS16 and microMIPS code, and vice versa. For example, code using the standard ISA encoding cannot jump directly to MIPS16 or microMIPS code; it must either use a call or ! an indirect jump. `-minterlink-compressed' therefore disables direct jumps unless GCC knows that the target of the jump is not compressed. ! `-minterlink-mips16' ! `-mno-interlink-mips16' ! Aliases of `-minterlink-compressed' and ! `-mno-interlink-compressed'. These options predate the microMIPS ASE and are retained for backwards compatibility. ! `-mabi=32' ! `-mabi=o64' ! `-mabi=n32' ! `-mabi=64' ! `-mabi=eabi' Generate code for the given ABI. Note that the EABI has a 32-bit and a 64-bit variant. GCC normally generates 64-bit code when you select a 64-bit architecture, but ! you can use `-mgp32' to get 32-bit code instead. For information about the O64 ABI, see ! `http://gcc.gnu.org/projects/mipso64-abi.html'. GCC supports a variant of the o32 ABI in which floating-point registers are 64 rather than 32 bits wide. You can select this ! combination with `-mabi=32' `-mfp64'. This ABI relies on the ! `mthc1' and `mfhc1' instructions and is therefore only supported for MIPS32R2, MIPS32R3 and MIPS32R5 processors. The register assignments for arguments and return values remain the same, but each scalar value is passed in a single 64-bit register rather than a pair of 32-bit registers. For example, scalar ! floating-point values are returned in `$f0' only, not a ! `$f0'/`$f1' pair. The set of call-saved registers also remains ! the same in that the even-numbered double-precision registers are ! saved. Two additional variants of the o32 ABI are supported to enable a transition from 32-bit to 64-bit registers. These are FPXX ! (`-mfpxx') and FP64A (`-mfp64' `-mno-odd-spreg'). The FPXX extension mandates that all code must execute correctly when run ! using 32-bit or 64-bit registers. The code can be interlinked ! with either FP32 or FP64, but not both. The FP64A extension is ! similar to the FP64 extension but forbids the use of odd-numbered single-precision registers. This can be used in conjunction with ! the `FRE' mode of FPUs in MIPS32R5 processors and allows both FP32 and FP64A code to interlink and run in the same process without changing FPU modes. ! `-mabicalls' ! `-mno-abicalls' Generate (do not generate) code that is suitable for SVR4-style ! dynamic objects. `-mabicalls' is the default for SVR4-based systems. ! `-mshared' ! `-mno-shared' Generate (do not generate) code that is fully position-independent, and that can therefore be linked into shared libraries. This ! option only affects `-mabicalls'. ! All `-mabicalls' code has traditionally been position-independent, ! regardless of options like `-fPIC' and `-fpic'. However, as an extension, the GNU toolchain allows executables to use absolute accesses for locally-binding symbols. It can also use shorter GP initialization sequences and generate direct calls to ! locally-defined functions. This mode is selected by `-mno-shared'. ! `-mno-shared' depends on binutils 2.16 or higher and generates objects that can only be linked by the GNU linker. However, the option does not affect the ABI of the final executable; it only ! affects the ABI of relocatable objects. Using `-mno-shared' generally makes executables both smaller and quicker. ! `-mshared' is the default. ! `-mplt' ! `-mno-plt' Assume (do not assume) that the static and dynamic linkers support ! PLTs and copy relocations. This option only affects `-mno-shared -mabicalls'. For the n64 ABI, this option has no effect without ! `-msym32'. ! You can make `-mplt' the default by configuring GCC with ! `--with-mips-plt'. The default is `-mno-plt' otherwise. ! `-mxgot' ! `-mno-xgot' Lift (do not lift) the usual restrictions on the size of the global offset table. *************** File: gcc.info, Node: MIPS Options, Ne *** 16809,17091 **** relocation truncated to fit: R_MIPS_GOT16 foobar ! If this happens, you should recompile your code with '-mxgot'. This works with very large GOTs, although the code is also less efficient, since it takes three instructions to fetch the value of a global symbol. Note that some linkers can create multiple GOTs. If you have such ! a linker, you should only need to use '-mxgot' when a single object file accesses more than 64k's worth of GOT entries. Very few do. These options have no effect unless GCC is generating position independent code. ! '-mgp32' Assume that general-purpose registers are 32 bits wide. ! '-mgp64' Assume that general-purpose registers are 64 bits wide. ! '-mfp32' Assume that floating-point registers are 32 bits wide. ! '-mfp64' Assume that floating-point registers are 64 bits wide. ! '-mfpxx' Do not assume the width of floating-point registers. ! '-mhard-float' Use floating-point coprocessor instructions. ! '-msoft-float' Do not use floating-point coprocessor instructions. Implement floating-point calculations using library calls instead. ! '-mno-float' ! Equivalent to '-msoft-float', but additionally asserts that the program being compiled does not perform any floating-point operations. This option is presently supported only by some bare-metal MIPS configurations, where it may select a special set of libraries that lack all floating-point support (including, for ! example, the floating-point 'printf' formats). If code compiled ! with '-mno-float' accidentally contains floating-point operations, it is likely to suffer a link-time or run-time failure. ! '-msingle-float' Assume that the floating-point coprocessor only supports single-precision operations. ! '-mdouble-float' Assume that the floating-point coprocessor supports double-precision operations. This is the default. ! '-modd-spreg' ! '-mno-odd-spreg' Enable the use of odd-numbered single-precision floating-point ! registers for the o32 ABI. This is the default for processors that ! are known to support these registers. When using the o32 FPXX ABI, ! '-mno-odd-spreg' is set by default. ! '-mabs=2008' ! '-mabs=legacy' These options control the treatment of the special not-a-number ! (NaN) IEEE 754 floating-point data with the 'abs.fmt' and 'neg.fmt' ! machine instructions. ! By default or when '-mabs=legacy' is used the legacy treatment is selected. In this case these instructions are considered arithmetic and avoided where correct operation is required and the ! input operand might be a NaN. A longer sequence of instructions that manipulate the sign bit of floating-point datum manually is ! used instead unless the '-ffinite-math-only' option has also been specified. ! The '-mabs=2008' option selects the IEEE 754-2008 treatment. In this case these instructions are considered non-arithmetic and ! therefore operating correctly in all cases, including in particular ! where the input operand is a NaN. These instructions are therefore ! always used for the respective operations. ! '-mnan=2008' ! '-mnan=legacy' These options control the encoding of the special not-a-number (NaN) IEEE 754 floating-point data. ! The '-mnan=legacy' option selects the legacy encoding. In this case quiet NaNs (qNaNs) are denoted by the first bit of their ! trailing significand field being 0, whereas signalling NaNs (sNaNs) ! are denoted by the first bit of their trailing significand field ! being 1. ! The '-mnan=2008' option selects the IEEE 754-2008 encoding. In this case qNaNs are denoted by the first bit of their trailing significand field being 1, whereas sNaNs are denoted by the first bit of their trailing significand field being 0. ! The default is '-mnan=legacy' unless GCC has been configured with ! '--with-nan=2008'. ! '-mllsc' ! '-mno-llsc' ! Use (do not use) 'll', 'sc', and 'sync' instructions to implement atomic memory built-in functions. When neither option is specified, GCC uses the instructions if the target architecture supports them. ! '-mllsc' is useful if the runtime environment can emulate the ! instructions and '-mno-llsc' can be useful when compiling for nonstandard ISAs. You can make either option the default by ! configuring GCC with '--with-llsc' and '--without-llsc' ! respectively. '--with-llsc' is the default for some configurations; see the installation documentation for details. ! '-mdsp' ! '-mno-dsp' Use (do not use) revision 1 of the MIPS DSP ASE. *Note MIPS DSP Built-in Functions::. This option defines the preprocessor macro ! '__mips_dsp'. It also defines '__mips_dsp_rev' to 1. ! '-mdspr2' ! '-mno-dspr2' Use (do not use) revision 2 of the MIPS DSP ASE. *Note MIPS DSP Built-in Functions::. This option defines the preprocessor macros ! '__mips_dsp' and '__mips_dspr2'. It also defines '__mips_dsp_rev' to 2. ! '-msmartmips' ! '-mno-smartmips' Use (do not use) the MIPS SmartMIPS ASE. ! '-mpaired-single' ! '-mno-paired-single' Use (do not use) paired-single floating-point instructions. *Note MIPS Paired-Single Support::. This option requires hardware floating-point support to be enabled. ! '-mdmx' ! '-mno-mdmx' Use (do not use) MIPS Digital Media Extension instructions. This option can only be used when generating 64-bit code and requires hardware floating-point support to be enabled. ! '-mips3d' ! '-mno-mips3d' Use (do not use) the MIPS-3D ASE. *Note MIPS-3D Built-in ! Functions::. The option '-mips3d' implies '-mpaired-single'. ! '-mmicromips' ! '-mno-micromips' Generate (do not generate) microMIPS code. MicroMIPS code generation can also be controlled on a per-function ! basis by means of 'micromips' and 'nomicromips' attributes. *Note Function Attributes::, for more information. ! '-mmt' ! '-mno-mt' Use (do not use) MT Multithreading instructions. ! '-mmcu' ! '-mno-mcu' Use (do not use) the MIPS MCU ASE instructions. ! '-meva' ! '-mno-eva' Use (do not use) the MIPS Enhanced Virtual Addressing instructions. ! '-mvirt' ! '-mno-virt' Use (do not use) the MIPS Virtualization Application Specific instructions. ! '-mxpa' ! '-mno-xpa' Use (do not use) the MIPS eXtended Physical Address (XPA) instructions. ! '-mlong64' ! Force 'long' types to be 64 bits wide. See '-mlong32' for an explanation of the default and the way that the pointer size is determined. ! '-mlong32' ! Force 'long', 'int', and pointer types to be 32 bits wide. ! The default size of 'int's, 'long's and pointers depends on the ! ABI. All the supported ABIs use 32-bit 'int's. The n64 ABI uses ! 64-bit 'long's, as does the 64-bit EABI; the others use 32-bit ! 'long's. Pointers are the same size as 'long's, or the same size as integer registers, whichever is smaller. ! '-msym32' ! '-mno-sym32' Assume (do not assume) that all symbols have 32-bit values, regardless of the selected ABI. This option is useful in ! combination with '-mabi=64' and '-mno-abicalls' because it allows GCC to generate shorter and faster references to symbolic addresses. ! '-G NUM' Put definitions of externally-visible data in a small data section if that data is no bigger than NUM bytes. GCC can then generate ! more efficient accesses to the data; see '-mgpopt' for details. ! The default '-G' option depends on the configuration. ! '-mlocal-sdata' ! '-mno-local-sdata' ! Extend (do not extend) the '-G' behavior to local data too, such as ! to static variables in C. '-mlocal-sdata' is the default for all ! configurations. ! If the linker complains that an application is using too much small ! data, you might want to try rebuilding the less ! performance-critical parts with '-mno-local-sdata'. You might also ! want to build large libraries with '-mno-local-sdata', so that the ! libraries leave more room for the main program. ! '-mextern-sdata' ! '-mno-extern-sdata' Assume (do not assume) that externally-defined data is in a small ! data section if the size of that data is within the '-G' limit. ! '-mextern-sdata' is the default for all configurations. ! If you compile a module MOD with '-mextern-sdata' '-G NUM' ! '-mgpopt', and MOD references a variable VAR that is no bigger than ! NUM bytes, you must make sure that VAR is placed in a small data ! section. If VAR is defined by another module, you must either ! compile that module with a high-enough '-G' setting or attach a ! 'section' attribute to VAR's definition. If VAR is common, you ! must link the application with a high-enough '-G' setting. The easiest way of satisfying these restrictions is to compile and ! link every module with the same '-G' option. However, you may wish ! to build a library that supports several different small data limits. You can do this by compiling the library with the highest ! supported '-G' setting and additionally using '-mno-extern-sdata' to stop the library from making assumptions about externally-defined data. ! '-mgpopt' ! '-mno-gpopt' ! Use (do not use) GP-relative accesses for symbols that are known to ! be in a small data section; see '-G', '-mlocal-sdata' and ! '-mextern-sdata'. '-mgpopt' is the default for all configurations. ! '-mno-gpopt' is useful for cases where the '$gp' register might not ! hold the value of '_gp'. For example, if the code is part of a ! library that might be used in a boot monitor, programs that call ! boot monitor routines pass an unknown value in '$gp'. (In such situations, the boot monitor itself is usually compiled with ! '-G0'.) ! '-mno-gpopt' implies '-mno-local-sdata' and '-mno-extern-sdata'. ! '-membedded-data' ! '-mno-embedded-data' ! Allocate variables to the read-only data section first if possible, ! then next in the small data section if possible, otherwise in data. ! This gives slightly slower code than the default, but reduces the ! amount of RAM required when executing, and thus may be preferred ! for some embedded systems. ! '-muninit-const-in-rodata' ! '-mno-uninit-const-in-rodata' ! Put uninitialized 'const' variables in the read-only data section. This option is only meaningful in conjunction with ! '-membedded-data'. ! '-mcode-readable=SETTING' Specify whether GCC may generate code that reads from executable sections. There are three possible settings: ! '-mcode-readable=yes' Instructions may freely access executable sections. This is the default setting. ! '-mcode-readable=pcrel' MIPS16 PC-relative load instructions can access executable sections, but other instructions must not do so. This option is useful on 4KSc and 4KSd processors when the code TLBs have --- 16905,17188 ---- relocation truncated to fit: R_MIPS_GOT16 foobar ! If this happens, you should recompile your code with `-mxgot'. This works with very large GOTs, although the code is also less efficient, since it takes three instructions to fetch the value of a global symbol. Note that some linkers can create multiple GOTs. If you have such ! a linker, you should only need to use `-mxgot' when a single object file accesses more than 64k's worth of GOT entries. Very few do. These options have no effect unless GCC is generating position independent code. ! `-mgp32' Assume that general-purpose registers are 32 bits wide. ! `-mgp64' Assume that general-purpose registers are 64 bits wide. ! `-mfp32' Assume that floating-point registers are 32 bits wide. ! `-mfp64' Assume that floating-point registers are 64 bits wide. ! `-mfpxx' Do not assume the width of floating-point registers. ! `-mhard-float' Use floating-point coprocessor instructions. ! `-msoft-float' Do not use floating-point coprocessor instructions. Implement floating-point calculations using library calls instead. ! `-mno-float' ! Equivalent to `-msoft-float', but additionally asserts that the program being compiled does not perform any floating-point operations. This option is presently supported only by some bare-metal MIPS configurations, where it may select a special set of libraries that lack all floating-point support (including, for ! example, the floating-point `printf' formats). If code compiled ! with `-mno-float' accidentally contains floating-point operations, it is likely to suffer a link-time or run-time failure. ! `-msingle-float' Assume that the floating-point coprocessor only supports single-precision operations. ! `-mdouble-float' Assume that the floating-point coprocessor supports double-precision operations. This is the default. ! `-modd-spreg' ! `-mno-odd-spreg' Enable the use of odd-numbered single-precision floating-point ! registers for the o32 ABI. This is the default for processors ! that are known to support these registers. When using the o32 ! FPXX ABI, `-mno-odd-spreg' is set by default. ! `-mabs=2008' ! `-mabs=legacy' These options control the treatment of the special not-a-number ! (NaN) IEEE 754 floating-point data with the `abs.fmt' and ! `neg.fmt' machine instructions. ! By default or when `-mabs=legacy' is used the legacy treatment is selected. In this case these instructions are considered arithmetic and avoided where correct operation is required and the ! input operand might be a NaN. A longer sequence of instructions that manipulate the sign bit of floating-point datum manually is ! used instead unless the `-ffinite-math-only' option has also been specified. ! The `-mabs=2008' option selects the IEEE 754-2008 treatment. In this case these instructions are considered non-arithmetic and ! therefore operating correctly in all cases, including in ! particular where the input operand is a NaN. These instructions ! are therefore always used for the respective operations. ! `-mnan=2008' ! `-mnan=legacy' These options control the encoding of the special not-a-number (NaN) IEEE 754 floating-point data. ! The `-mnan=legacy' option selects the legacy encoding. In this case quiet NaNs (qNaNs) are denoted by the first bit of their ! trailing significand field being 0, whereas signalling NaNs ! (sNaNs) are denoted by the first bit of their trailing significand ! field being 1. ! The `-mnan=2008' option selects the IEEE 754-2008 encoding. In this case qNaNs are denoted by the first bit of their trailing significand field being 1, whereas sNaNs are denoted by the first bit of their trailing significand field being 0. ! The default is `-mnan=legacy' unless GCC has been configured with ! `--with-nan=2008'. ! `-mllsc' ! `-mno-llsc' ! Use (do not use) `ll', `sc', and `sync' instructions to implement atomic memory built-in functions. When neither option is specified, GCC uses the instructions if the target architecture supports them. ! `-mllsc' is useful if the runtime environment can emulate the ! instructions and `-mno-llsc' can be useful when compiling for nonstandard ISAs. You can make either option the default by ! configuring GCC with `--with-llsc' and `--without-llsc' ! respectively. `--with-llsc' is the default for some configurations; see the installation documentation for details. ! `-mdsp' ! `-mno-dsp' Use (do not use) revision 1 of the MIPS DSP ASE. *Note MIPS DSP Built-in Functions::. This option defines the preprocessor macro ! `__mips_dsp'. It also defines `__mips_dsp_rev' to 1. ! `-mdspr2' ! `-mno-dspr2' Use (do not use) revision 2 of the MIPS DSP ASE. *Note MIPS DSP Built-in Functions::. This option defines the preprocessor macros ! `__mips_dsp' and `__mips_dspr2'. It also defines `__mips_dsp_rev' to 2. ! `-msmartmips' ! `-mno-smartmips' Use (do not use) the MIPS SmartMIPS ASE. ! `-mpaired-single' ! `-mno-paired-single' Use (do not use) paired-single floating-point instructions. *Note MIPS Paired-Single Support::. This option requires hardware floating-point support to be enabled. ! `-mdmx' ! `-mno-mdmx' Use (do not use) MIPS Digital Media Extension instructions. This option can only be used when generating 64-bit code and requires hardware floating-point support to be enabled. ! `-mips3d' ! `-mno-mips3d' Use (do not use) the MIPS-3D ASE. *Note MIPS-3D Built-in ! Functions::. The option `-mips3d' implies `-mpaired-single'. ! `-mmicromips' ! `-mno-micromips' Generate (do not generate) microMIPS code. MicroMIPS code generation can also be controlled on a per-function ! basis by means of `micromips' and `nomicromips' attributes. *Note Function Attributes::, for more information. ! `-mmt' ! `-mno-mt' Use (do not use) MT Multithreading instructions. ! `-mmcu' ! `-mno-mcu' Use (do not use) the MIPS MCU ASE instructions. ! `-meva' ! `-mno-eva' Use (do not use) the MIPS Enhanced Virtual Addressing instructions. ! `-mvirt' ! `-mno-virt' Use (do not use) the MIPS Virtualization Application Specific instructions. ! `-mxpa' ! `-mno-xpa' Use (do not use) the MIPS eXtended Physical Address (XPA) instructions. ! `-mlong64' ! Force `long' types to be 64 bits wide. See `-mlong32' for an explanation of the default and the way that the pointer size is determined. ! `-mlong32' ! Force `long', `int', and pointer types to be 32 bits wide. ! The default size of `int's, `long's and pointers depends on the ! ABI. All the supported ABIs use 32-bit `int's. The n64 ABI uses ! 64-bit `long's, as does the 64-bit EABI; the others use 32-bit ! `long's. Pointers are the same size as `long's, or the same size as integer registers, whichever is smaller. ! `-msym32' ! `-mno-sym32' Assume (do not assume) that all symbols have 32-bit values, regardless of the selected ABI. This option is useful in ! combination with `-mabi=64' and `-mno-abicalls' because it allows GCC to generate shorter and faster references to symbolic addresses. ! `-G NUM' Put definitions of externally-visible data in a small data section if that data is no bigger than NUM bytes. GCC can then generate ! more efficient accesses to the data; see `-mgpopt' for details. ! The default `-G' option depends on the configuration. ! `-mlocal-sdata' ! `-mno-local-sdata' ! Extend (do not extend) the `-G' behavior to local data too, such ! as to static variables in C. `-mlocal-sdata' is the default for ! all configurations. ! If the linker complains that an application is using too much ! small data, you might want to try rebuilding the less ! performance-critical parts with `-mno-local-sdata'. You might ! also want to build large libraries with `-mno-local-sdata', so ! that the libraries leave more room for the main program. ! `-mextern-sdata' ! `-mno-extern-sdata' Assume (do not assume) that externally-defined data is in a small ! data section if the size of that data is within the `-G' limit. ! `-mextern-sdata' is the default for all configurations. ! If you compile a module MOD with `-mextern-sdata' `-G NUM' ! `-mgpopt', and MOD references a variable VAR that is no bigger ! than NUM bytes, you must make sure that VAR is placed in a small ! data section. If VAR is defined by another module, you must ! either compile that module with a high-enough `-G' setting or ! attach a `section' attribute to VAR's definition. If VAR is ! common, you must link the application with a high-enough `-G' ! setting. The easiest way of satisfying these restrictions is to compile and ! link every module with the same `-G' option. However, you may ! wish to build a library that supports several different small data limits. You can do this by compiling the library with the highest ! supported `-G' setting and additionally using `-mno-extern-sdata' to stop the library from making assumptions about externally-defined data. ! `-mgpopt' ! `-mno-gpopt' ! Use (do not use) GP-relative accesses for symbols that are known ! to be in a small data section; see `-G', `-mlocal-sdata' and ! `-mextern-sdata'. `-mgpopt' is the default for all configurations. ! `-mno-gpopt' is useful for cases where the `$gp' register might ! not hold the value of `_gp'. For example, if the code is part of ! a library that might be used in a boot monitor, programs that call ! boot monitor routines pass an unknown value in `$gp'. (In such situations, the boot monitor itself is usually compiled with ! `-G0'.) ! `-mno-gpopt' implies `-mno-local-sdata' and `-mno-extern-sdata'. ! `-membedded-data' ! `-mno-embedded-data' ! Allocate variables to the read-only data section first if ! possible, then next in the small data section if possible, ! otherwise in data. This gives slightly slower code than the ! default, but reduces the amount of RAM required when executing, ! and thus may be preferred for some embedded systems. ! `-muninit-const-in-rodata' ! `-mno-uninit-const-in-rodata' ! Put uninitialized `const' variables in the read-only data section. This option is only meaningful in conjunction with ! `-membedded-data'. ! `-mcode-readable=SETTING' Specify whether GCC may generate code that reads from executable sections. There are three possible settings: ! `-mcode-readable=yes' Instructions may freely access executable sections. This is the default setting. ! `-mcode-readable=pcrel' MIPS16 PC-relative load instructions can access executable sections, but other instructions must not do so. This option is useful on 4KSc and 4KSd processors when the code TLBs have *************** File: gcc.info, Node: MIPS Options, Ne *** 17094,17250 **** interface and that, like the M4K, automatically redirect PC-relative loads to the instruction RAM. ! '-mcode-readable=no' ! Instructions must not access executable sections. This option ! can be useful on targets that are configured to have a dual ! instruction/data SRAM interface but that (unlike the M4K) do ! not automatically redirect PC-relative loads to the instruction RAM. ! '-msplit-addresses' ! '-mno-split-addresses' ! Enable (disable) use of the '%hi()' and '%lo()' assembler relocation operators. This option has been superseded by ! '-mexplicit-relocs' but is retained for backwards compatibility. ! '-mexplicit-relocs' ! '-mno-explicit-relocs' Use (do not use) assembler relocation operators when dealing with symbolic addresses. The alternative, selected by ! '-mno-explicit-relocs', is to use assembler macros instead. ! '-mexplicit-relocs' is the default if GCC was configured to use an assembler that supports relocation operators. ! '-mcheck-zero-division' ! '-mno-check-zero-division' Trap (do not trap) on integer division by zero. ! The default is '-mcheck-zero-division'. ! '-mdivide-traps' ! '-mdivide-breaks' MIPS systems check for division by zero by generating either a conditional trap or a break instruction. Using traps results in smaller code, but is only supported on MIPS II and later. Also, some versions of the Linux kernel have a bug that prevents trap ! from generating the proper signal ('SIGFPE'). Use '-mdivide-traps' ! to allow conditional traps on architectures that support them and ! '-mdivide-breaks' to force the use of breaks. ! The default is usually '-mdivide-traps', but this can be overridden ! at configure time using '--with-divide=breaks'. Divide-by-zero ! checks can be completely disabled using '-mno-check-zero-division'. ! '-mmemcpy' ! '-mno-memcpy' ! Force (do not force) the use of 'memcpy' for non-trivial block ! moves. The default is '-mno-memcpy', which allows GCC to inline most constant-sized copies. ! '-mlong-calls' ! '-mno-long-calls' ! Disable (do not disable) use of the 'jal' instruction. Calling ! functions using 'jal' is more efficient but requires the caller and ! callee to be in the same 256 megabyte segment. This option has no effect on abicalls code. The default is ! '-mno-long-calls'. ! '-mmad' ! '-mno-mad' ! Enable (disable) use of the 'mad', 'madu' and 'mul' instructions, as provided by the R4650 ISA. ! '-mimadd' ! '-mno-imadd' ! Enable (disable) use of the 'madd' and 'msub' integer instructions. ! The default is '-mimadd' on architectures that support 'madd' and ! 'msub' except for the 74k architecture where it was found to ! generate slower code. ! '-mfused-madd' ! '-mno-fused-madd' Enable (disable) use of the floating-point multiply-accumulate instructions, when they are available. The default is ! '-mfused-madd'. On the R8000 CPU when multiply-accumulate instructions are used, ! the intermediate product is calculated to infinite precision and is ! not subject to the FCSR Flush to Zero bit. This may be undesirable ! in some circumstances. On other processors the result is ! numerically identical to the equivalent computation using separate ! multiply, add, subtract and negate instructions. ! '-nocpp' Tell the MIPS assembler to not run its preprocessor over user ! assembler files (with a '.s' suffix) when assembling them. ! '-mfix-24k' ! '-mno-fix-24k' Work around the 24K E48 (lost data on stores during refill) errata. The workarounds are implemented by the assembler rather than by GCC. ! '-mfix-r4000' ! '-mno-fix-r4000' Work around certain R4000 CPU errata: ! - A double-word or a variable shift may give an incorrect result ! if executed immediately after starting an integer division. ! - A double-word or a variable shift may give an incorrect result ! if executed while an integer multiplication is in progress. ! - An integer division may give an incorrect result if started in ! a delay slot of a taken branch or a jump. ! '-mfix-r4400' ! '-mno-fix-r4400' Work around certain R4400 CPU errata: ! - A double-word or a variable shift may give an incorrect result ! if executed immediately after starting an integer division. ! '-mfix-r10000' ! '-mno-fix-r10000' Work around certain R10000 errata: ! - 'll'/'sc' sequences may not behave atomically on revisions prior to 3.0. They may deadlock on revisions 2.6 and earlier. This option can only be used if the target architecture supports ! branch-likely instructions. '-mfix-r10000' is the default when ! '-march=r10000' is used; '-mno-fix-r10000' is the default otherwise. ! '-mfix-rm7000' ! '-mno-fix-rm7000' ! Work around the RM7000 'dmult'/'dmultu' errata. The workarounds are implemented by the assembler rather than by GCC. ! '-mfix-vr4120' ! '-mno-fix-vr4120' Work around certain VR4120 errata: ! - 'dmultu' does not always produce the correct result. ! - 'div' and 'ddiv' do not always produce the correct result if one of the operands is negative. The workarounds for the division errata rely on special functions ! in 'libgcc.a'. At present, these functions are only provided by ! the 'mips64vr*-elf' configurations. Other VR4120 errata require a NOP to be inserted between certain pairs of instructions. These errata are handled by the assembler, not by GCC itself. ! '-mfix-vr4130' ! Work around the VR4130 'mflo'/'mfhi' errata. The workarounds are implemented by the assembler rather than by GCC, although GCC ! avoids using 'mflo' and 'mfhi' if the VR4130 'macc', 'macchi', ! 'dmacc' and 'dmacchi' instructions are available instead. ! '-mfix-sb1' ! '-mno-fix-sb1' Work around certain SB-1 CPU core errata. (This flag currently works around the SB-1 revision 2 "F1" and "F2" floating-point errata.) ! '-mr10k-cache-barrier=SETTING' Specify whether GCC should insert cache barriers to avoid the side-effects of speculation on R10K processors. --- 17191,17355 ---- interface and that, like the M4K, automatically redirect PC-relative loads to the instruction RAM. ! `-mcode-readable=no' ! Instructions must not access executable sections. This ! option can be useful on targets that are configured to have a ! dual instruction/data SRAM interface but that (unlike the ! M4K) do not automatically redirect PC-relative loads to the instruction RAM. ! `-msplit-addresses' ! `-mno-split-addresses' ! Enable (disable) use of the `%hi()' and `%lo()' assembler relocation operators. This option has been superseded by ! `-mexplicit-relocs' but is retained for backwards compatibility. ! `-mexplicit-relocs' ! `-mno-explicit-relocs' Use (do not use) assembler relocation operators when dealing with symbolic addresses. The alternative, selected by ! `-mno-explicit-relocs', is to use assembler macros instead. ! `-mexplicit-relocs' is the default if GCC was configured to use an assembler that supports relocation operators. ! `-mcheck-zero-division' ! `-mno-check-zero-division' Trap (do not trap) on integer division by zero. ! The default is `-mcheck-zero-division'. ! `-mdivide-traps' ! `-mdivide-breaks' MIPS systems check for division by zero by generating either a conditional trap or a break instruction. Using traps results in smaller code, but is only supported on MIPS II and later. Also, some versions of the Linux kernel have a bug that prevents trap ! from generating the proper signal (`SIGFPE'). Use ! `-mdivide-traps' to allow conditional traps on architectures that ! support them and `-mdivide-breaks' to force the use of breaks. ! The default is usually `-mdivide-traps', but this can be ! overridden at configure time using `--with-divide=breaks'. ! Divide-by-zero checks can be completely disabled using ! `-mno-check-zero-division'. ! `-mmemcpy' ! `-mno-memcpy' ! Force (do not force) the use of `memcpy' for non-trivial block ! moves. The default is `-mno-memcpy', which allows GCC to inline most constant-sized copies. ! `-mlong-calls' ! `-mno-long-calls' ! Disable (do not disable) use of the `jal' instruction. Calling ! functions using `jal' is more efficient but requires the caller ! and callee to be in the same 256 megabyte segment. This option has no effect on abicalls code. The default is ! `-mno-long-calls'. ! `-mmad' ! `-mno-mad' ! Enable (disable) use of the `mad', `madu' and `mul' instructions, as provided by the R4650 ISA. ! `-mimadd' ! `-mno-imadd' ! Enable (disable) use of the `madd' and `msub' integer ! instructions. The default is `-mimadd' on architectures that ! support `madd' and `msub' except for the 74k architecture where it ! was found to generate slower code. ! `-mfused-madd' ! `-mno-fused-madd' Enable (disable) use of the floating-point multiply-accumulate instructions, when they are available. The default is ! `-mfused-madd'. On the R8000 CPU when multiply-accumulate instructions are used, ! the intermediate product is calculated to infinite precision and ! is not subject to the FCSR Flush to Zero bit. This may be ! undesirable in some circumstances. On other processors the result ! is numerically identical to the equivalent computation using ! separate multiply, add, subtract and negate instructions. ! `-nocpp' Tell the MIPS assembler to not run its preprocessor over user ! assembler files (with a `.s' suffix) when assembling them. ! `-mfix-24k' ! ! `-mno-fix-24k' Work around the 24K E48 (lost data on stores during refill) errata. The workarounds are implemented by the assembler rather than by GCC. ! `-mfix-r4000' ! `-mno-fix-r4000' Work around certain R4000 CPU errata: ! - A double-word or a variable shift may give an incorrect ! result if executed immediately after starting an integer ! division. ! - A double-word or a variable shift may give an incorrect ! result if executed while an integer multiplication is in ! progress. ! ! - An integer division may give an incorrect result if started ! in a delay slot of a taken branch or a jump. ! ! `-mfix-r4400' ! `-mno-fix-r4400' Work around certain R4400 CPU errata: ! - A double-word or a variable shift may give an incorrect ! result if executed immediately after starting an integer ! division. ! `-mfix-r10000' ! `-mno-fix-r10000' Work around certain R10000 errata: ! - `ll'/`sc' sequences may not behave atomically on revisions prior to 3.0. They may deadlock on revisions 2.6 and earlier. This option can only be used if the target architecture supports ! branch-likely instructions. `-mfix-r10000' is the default when ! `-march=r10000' is used; `-mno-fix-r10000' is the default otherwise. ! `-mfix-rm7000' ! `-mno-fix-rm7000' ! Work around the RM7000 `dmult'/`dmultu' errata. The workarounds are implemented by the assembler rather than by GCC. ! `-mfix-vr4120' ! `-mno-fix-vr4120' Work around certain VR4120 errata: ! - `dmultu' does not always produce the correct result. ! ! - `div' and `ddiv' do not always produce the correct result if one of the operands is negative. The workarounds for the division errata rely on special functions ! in `libgcc.a'. At present, these functions are only provided by ! the `mips64vr*-elf' configurations. Other VR4120 errata require a NOP to be inserted between certain pairs of instructions. These errata are handled by the assembler, not by GCC itself. ! `-mfix-vr4130' ! Work around the VR4130 `mflo'/`mfhi' errata. The workarounds are implemented by the assembler rather than by GCC, although GCC ! avoids using `mflo' and `mfhi' if the VR4130 `macc', `macchi', ! `dmacc' and `dmacchi' instructions are available instead. ! `-mfix-sb1' ! `-mno-fix-sb1' Work around certain SB-1 CPU core errata. (This flag currently works around the SB-1 revision 2 "F1" and "F2" floating-point errata.) ! `-mr10k-cache-barrier=SETTING' Specify whether GCC should insert cache barriers to avoid the side-effects of speculation on R10K processors. *************** File: gcc.info, Node: MIPS Options, Ne *** 17256,17274 **** This problem only affects kernel stores and, depending on the system, kernel loads. As an example, a speculatively-executed ! store may load the target memory into cache and mark the cache line ! as dirty, even if the store itself is later aborted. If a DMA ! operation writes to the same area of memory before the "dirty" line ! is flushed, the cached data overwrites the DMA-ed data. See the ! R10K processor manual for a full description, including other potential problems. ! One workaround is to insert cache barrier instructions before every ! memory access that might be speculatively executed and that might ! have side effects even if aborted. '-mr10k-cache-barrier=SETTING' ! controls GCC's implementation of this workaround. It assumes that ! aborted accesses to any byte in the following regions does not have ! side effects: 1. the memory occupied by the current function's stack frame; --- 17361,17379 ---- This problem only affects kernel stores and, depending on the system, kernel loads. As an example, a speculatively-executed ! store may load the target memory into cache and mark the cache ! line as dirty, even if the store itself is later aborted. If a ! DMA operation writes to the same area of memory before the "dirty" ! line is flushed, the cached data overwrites the DMA-ed data. See ! the R10K processor manual for a full description, including other potential problems. ! One workaround is to insert cache barrier instructions before ! every memory access that might be speculatively executed and that ! might have side effects even if aborted. ! `-mr10k-cache-barrier=SETTING' controls GCC's implementation of ! this workaround. It assumes that aborted accesses to any byte in ! the following regions does not have side effects: 1. the memory occupied by the current function's stack frame; *************** File: gcc.info, Node: MIPS Options, Ne *** 17284,17328 **** void foo (void); ! then the implementation of 'foo' must allow 'j foo' and 'jal foo' to be executed speculatively. GCC honors this restriction for functions it compiles itself. It expects non-GCC functions (such as hand-written assembly code) to do the same. The option has three forms: ! '-mr10k-cache-barrier=load-store' Insert a cache barrier before a load or store that might be speculatively executed and that might have side effects even if aborted. ! '-mr10k-cache-barrier=store' Insert a cache barrier before a store that might be speculatively executed and that might have side effects even if aborted. ! '-mr10k-cache-barrier=none' Disable the insertion of cache barriers. This is the default setting. ! '-mflush-func=FUNC' ! '-mno-flush-func' Specifies the function to call to flush the I and D caches, or to not call any such function. If called, the function must take the ! same arguments as the common '_flush_func', that is, the address of ! the memory range for which the cache is being flushed, the size of ! the memory range, and the number 3 (to flush both caches). The default depends on the target GCC was configured for, but commonly ! is either '_flush_func' or '__cpu_flush'. ! 'mbranch-cost=NUM' Set the cost of branches to roughly NUM "simple" instructions. This cost is only a heuristic and is not guaranteed to produce consistent results across releases. A zero cost redundantly ! selects the default, which is based on the '-mtune' setting. ! '-mbranch-likely' ! '-mno-branch-likely' Enable or disable use of Branch Likely instructions, regardless of the default for the selected architecture. By default, Branch Likely instructions may be generated if they are supported by the --- 17389,17433 ---- void foo (void); ! then the implementation of `foo' must allow `j foo' and `jal foo' to be executed speculatively. GCC honors this restriction for functions it compiles itself. It expects non-GCC functions (such as hand-written assembly code) to do the same. The option has three forms: ! `-mr10k-cache-barrier=load-store' Insert a cache barrier before a load or store that might be speculatively executed and that might have side effects even if aborted. ! `-mr10k-cache-barrier=store' Insert a cache barrier before a store that might be speculatively executed and that might have side effects even if aborted. ! `-mr10k-cache-barrier=none' Disable the insertion of cache barriers. This is the default setting. ! `-mflush-func=FUNC' ! `-mno-flush-func' Specifies the function to call to flush the I and D caches, or to not call any such function. If called, the function must take the ! same arguments as the common `_flush_func', that is, the address ! of the memory range for which the cache is being flushed, the size ! of the memory range, and the number 3 (to flush both caches). The default depends on the target GCC was configured for, but commonly ! is either `_flush_func' or `__cpu_flush'. ! `mbranch-cost=NUM' Set the cost of branches to roughly NUM "simple" instructions. This cost is only a heuristic and is not guaranteed to produce consistent results across releases. A zero cost redundantly ! selects the default, which is based on the `-mtune' setting. ! `-mbranch-likely' ! `-mno-branch-likely' Enable or disable use of Branch Likely instructions, regardless of the default for the selected architecture. By default, Branch Likely instructions may be generated if they are supported by the *************** File: gcc.info, Node: MIPS Options, Ne *** 17332,17360 **** default because the MIPS32 and MIPS64 architectures specifically deprecate their use. ! '-mcompact-branches=never' ! '-mcompact-branches=optimal' ! '-mcompact-branches=always' These options control which form of branches will be generated. ! The default is '-mcompact-branches=optimal'. ! The '-mcompact-branches=never' option ensures that compact branch instructions will never be generated. ! The '-mcompact-branches=always' option ensures that a compact branch instruction will be generated if available. If a compact branch instruction is not available, a delay slot form of the branch will be used instead. This option is supported from MIPS Release 6 onwards. ! The '-mcompact-branches=optimal' option will cause a delay slot branch to be used if one is available in the current ISA and the delay slot is successfully filled. If the delay slot is not filled, a compact branch will be chosen if one is available. ! '-mfp-exceptions' ! '-mno-fp-exceptions' Specifies whether FP exceptions are enabled. This affects how FP instructions are scheduled for some processors. The default is that FP exceptions are enabled. --- 17437,17465 ---- default because the MIPS32 and MIPS64 architectures specifically deprecate their use. ! `-mcompact-branches=never' ! `-mcompact-branches=optimal' ! `-mcompact-branches=always' These options control which form of branches will be generated. ! The default is `-mcompact-branches=optimal'. ! The `-mcompact-branches=never' option ensures that compact branch instructions will never be generated. ! The `-mcompact-branches=always' option ensures that a compact branch instruction will be generated if available. If a compact branch instruction is not available, a delay slot form of the branch will be used instead. This option is supported from MIPS Release 6 onwards. ! The `-mcompact-branches=optimal' option will cause a delay slot branch to be used if one is available in the current ISA and the delay slot is successfully filled. If the delay slot is not filled, a compact branch will be chosen if one is available. ! `-mfp-exceptions' ! `-mno-fp-exceptions' Specifies whether FP exceptions are enabled. This affects how FP instructions are scheduled for some processors. The default is that FP exceptions are enabled. *************** File: gcc.info, Node: MIPS Options, Ne *** 17363,17370 **** are emitting 64-bit code, then we can use both FP pipes. Otherwise, we can only use one FP pipe. ! '-mvr4130-align' ! '-mno-vr4130-align' The VR4130 pipeline is two-way superscalar, but can only issue two instructions together if the first one is 8-byte aligned. When this option is enabled, GCC aligns pairs of instructions that it --- 17468,17475 ---- are emitting 64-bit code, then we can use both FP pipes. Otherwise, we can only use one FP pipe. ! `-mvr4130-align' ! `-mno-vr4130-align' The VR4130 pipeline is two-way superscalar, but can only issue two instructions together if the first one is 8-byte aligned. When this option is enabled, GCC aligns pairs of instructions that it *************** File: gcc.info, Node: MIPS Options, Ne *** 17372,17429 **** This option only has an effect when optimizing for the VR4130. It normally makes code faster, but at the expense of making it bigger. ! It is enabled by default at optimization level '-O3'. ! '-msynci' ! '-mno-synci' ! Enable (disable) generation of 'synci' instructions on ! architectures that support it. The 'synci' instructions (if ! enabled) are generated when '__builtin___clear_cache' is compiled. ! This option defaults to '-mno-synci', but the default can be ! overridden by configuring GCC with '--with-synci'. When compiling code for single processor systems, it is generally ! safe to use 'synci'. However, on many multi-core (SMP) systems, it does not invalidate the instruction caches on all cores and may lead to undefined behavior. ! '-mrelax-pic-calls' ! '-mno-relax-pic-calls' Try to turn PIC calls that are normally dispatched via register ! '$25' into direct calls. This is only possible if the linker can resolve the destination at link time and if the destination is within range for a direct call. ! '-mrelax-pic-calls' is the default if GCC was configured to use an ! assembler and a linker that support the '.reloc' assembly directive ! and '-mexplicit-relocs' is in effect. With '-mno-explicit-relocs', ! this optimization can be performed by the assembler and the linker ! alone without help from the compiler. ! '-mmcount-ra-address' ! '-mno-mcount-ra-address' ! Emit (do not emit) code that allows '_mcount' to modify the calling ! function's return address. When enabled, this option extends the ! usual '_mcount' interface with a new RA-ADDRESS parameter, which ! has type 'intptr_t *' and is passed in register '$12'. '_mcount' ! can then modify the return address by doing both of the following: ! * Returning the new address in register '$31'. ! * Storing the new address in '*RA-ADDRESS', if RA-ADDRESS is nonnull. ! The default is '-mno-mcount-ra-address'. ! '-mframe-header-opt' ! '-mno-frame-header-opt' ! Enable (disable) frame header optimization in the o32 ABI. When using the o32 ABI, calling functions will allocate 16 bytes on the stack for the called function to write out register arguments. ! When enabled, this optimization will suppress the allocation of the ! frame header if it can be determined that it is unused. This optimization is off by default at all optimization levels.  File: gcc.info, Node: MMIX Options, Next: MN10300 Options, Prev: MIPS Options, Up: Submodel Options --- 17477,17537 ---- This option only has an effect when optimizing for the VR4130. It normally makes code faster, but at the expense of making it bigger. ! It is enabled by default at optimization level `-O3'. ! `-msynci' ! `-mno-synci' ! Enable (disable) generation of `synci' instructions on ! architectures that support it. The `synci' instructions (if ! enabled) are generated when `__builtin___clear_cache' is compiled. ! This option defaults to `-mno-synci', but the default can be ! overridden by configuring GCC with `--with-synci'. When compiling code for single processor systems, it is generally ! safe to use `synci'. However, on many multi-core (SMP) systems, it does not invalidate the instruction caches on all cores and may lead to undefined behavior. ! `-mrelax-pic-calls' ! `-mno-relax-pic-calls' Try to turn PIC calls that are normally dispatched via register ! `$25' into direct calls. This is only possible if the linker can resolve the destination at link time and if the destination is within range for a direct call. ! `-mrelax-pic-calls' is the default if GCC was configured to use an ! assembler and a linker that support the `.reloc' assembly ! directive and `-mexplicit-relocs' is in effect. With ! `-mno-explicit-relocs', this optimization can be performed by the ! assembler and the linker alone without help from the compiler. ! `-mmcount-ra-address' ! `-mno-mcount-ra-address' ! Emit (do not emit) code that allows `_mcount' to modify the ! calling function's return address. When enabled, this option ! extends the usual `_mcount' interface with a new RA-ADDRESS ! parameter, which has type `intptr_t *' and is passed in register ! `$12'. `_mcount' can then modify the return address by doing both ! of the following: ! * Returning the new address in register `$31'. ! ! * Storing the new address in `*RA-ADDRESS', if RA-ADDRESS is nonnull. ! The default is `-mno-mcount-ra-address'. ! `-mframe-header-opt' ! `-mno-frame-header-opt' ! Enable (disable) frame header optimization in the o32 ABI. When using the o32 ABI, calling functions will allocate 16 bytes on the stack for the called function to write out register arguments. ! When enabled, this optimization will suppress the allocation of ! the frame header if it can be determined that it is unused. This optimization is off by default at all optimization levels. +  File: gcc.info, Node: MMIX Options, Next: MN10300 Options, Prev: MIPS Options, Up: Submodel Options *************** File: gcc.info, Node: MMIX Options, Ne *** 17432,17482 **** These options are defined for the MMIX: ! '-mlibfuncs' ! '-mno-libfuncs' Specify that intrinsic library functions are being compiled, passing all values in registers, no matter the size. ! '-mepsilon' ! '-mno-epsilon' Generate floating-point comparison instructions that compare with ! respect to the 'rE' epsilon register. ! '-mabi=mmixware' ! '-mabi=gnu' Generate code that passes function parameters and return values ! that (in the called function) are seen as registers '$0' and up, as ! opposed to the GNU ABI which uses global registers '$231' and up. ! '-mzero-extend' ! '-mno-zero-extend' When reading data from memory in sizes shorter than 64 bits, use (do not use) zero-extending load instructions by default, rather than sign-extending ones. ! '-mknuthdiv' ! '-mno-knuthdiv' Make the result of a division yielding a remainder have the same ! sign as the divisor. With the default, '-mno-knuthdiv', the sign of the remainder follows the sign of the dividend. Both methods are arithmetically valid, the latter being almost exclusively used. ! '-mtoplevel-symbols' ! '-mno-toplevel-symbols' ! Prepend (do not prepend) a ':' to all global symbols, so the ! assembly code can be used with the 'PREFIX' assembly directive. ! '-melf' Generate an executable in the ELF format, rather than the default ! 'mmo' format used by the 'mmix' simulator. ! '-mbranch-predict' ! '-mno-branch-predict' Use (do not use) the probable-branch instructions, when static branch prediction indicates a probable branch. ! '-mbase-addresses' ! '-mno-base-addresses' Generate (do not generate) code that uses _base addresses_. Using a base address automatically generates a request (handled by the assembler and the linker) for a constant to be set up in a global --- 17540,17591 ---- These options are defined for the MMIX: ! `-mlibfuncs' ! `-mno-libfuncs' Specify that intrinsic library functions are being compiled, passing all values in registers, no matter the size. ! `-mepsilon' ! `-mno-epsilon' Generate floating-point comparison instructions that compare with ! respect to the `rE' epsilon register. ! `-mabi=mmixware' ! `-mabi=gnu' Generate code that passes function parameters and return values ! that (in the called function) are seen as registers `$0' and up, ! as opposed to the GNU ABI which uses global registers `$231' and ! up. ! `-mzero-extend' ! `-mno-zero-extend' When reading data from memory in sizes shorter than 64 bits, use (do not use) zero-extending load instructions by default, rather than sign-extending ones. ! `-mknuthdiv' ! `-mno-knuthdiv' Make the result of a division yielding a remainder have the same ! sign as the divisor. With the default, `-mno-knuthdiv', the sign of the remainder follows the sign of the dividend. Both methods are arithmetically valid, the latter being almost exclusively used. ! `-mtoplevel-symbols' ! `-mno-toplevel-symbols' ! Prepend (do not prepend) a `:' to all global symbols, so the ! assembly code can be used with the `PREFIX' assembly directive. ! `-melf' Generate an executable in the ELF format, rather than the default ! `mmo' format used by the `mmix' simulator. ! `-mbranch-predict' ! `-mno-branch-predict' Use (do not use) the probable-branch instructions, when static branch prediction indicates a probable branch. ! `-mbase-addresses' ! `-mno-base-addresses' Generate (do not generate) code that uses _base addresses_. Using a base address automatically generates a request (handled by the assembler and the linker) for a constant to be set up in a global *************** These options are defined for the MMIX: *** 17484,17494 **** requests within the range 0 to 255 from the value held in the register. The generally leads to short and fast code, but the number of different data items that can be addressed is limited. ! This means that a program that uses lots of static data may require ! '-mno-base-addresses'. ! '-msingle-exit' ! '-mno-single-exit' Force (do not force) generated code to have a single exit point in each function. --- 17593,17603 ---- requests within the range 0 to 255 from the value held in the register. The generally leads to short and fast code, but the number of different data items that can be addressed is limited. ! This means that a program that uses lots of static data may ! require `-mno-base-addresses'. ! `-msingle-exit' ! `-mno-single-exit' Force (do not force) generated code to have a single exit point in each function. *************** File: gcc.info, Node: MN10300 Options, *** 17498,17569 **** 3.18.28 MN10300 Options ----------------------- ! These '-m' options are defined for Matsushita MN10300 architectures: ! '-mmult-bug' Generate code to avoid bugs in the multiply instructions for the MN10300 processors. This is the default. ! '-mno-mult-bug' ! Do not generate code to avoid bugs in the multiply instructions for ! the MN10300 processors. ! '-mam33' Generate code using features specific to the AM33 processor. ! '-mno-am33' ! Do not generate code using features specific to the AM33 processor. ! This is the default. ! '-mam33-2' Generate code using features specific to the AM33/2.0 processor. ! '-mam34' Generate code using features specific to the AM34 processor. ! '-mtune=CPU-TYPE' Use the timing characteristics of the indicated CPU type when scheduling instructions. This does not change the targeted ! processor type. The CPU type must be one of 'mn10300', 'am33', ! 'am33-2' or 'am34'. ! '-mreturn-pointer-on-d0' When generating a function that returns a pointer, return the ! pointer in both 'a0' and 'd0'. Otherwise, the pointer is returned ! only in 'a0', and attempts to call such functions without a prototype result in errors. Note that this option is on by ! default; use '-mno-return-pointer-on-d0' to disable it. ! '-mno-crt0' Do not link in the C run-time initialization object file. ! '-mrelax' Indicate to the linker that it should perform a relaxation optimization pass to shorten branches, calls and absolute memory ! addresses. This option only has an effect when used on the command ! line for the final link step. This option makes symbolic debugging impossible. ! '-mliw' ! Allow the compiler to generate _Long Instruction Word_ instructions ! if the target is the 'AM33' or later. This is the default. This ! option defines the preprocessor macro '__LIW__'. ! '-mnoliw' Do not allow the compiler to generate _Long Instruction Word_ instructions. This option defines the preprocessor macro ! '__NO_LIW__'. ! '-msetlb' Allow the compiler to generate the _SETLB_ and _Lcc_ instructions ! if the target is the 'AM33' or later. This is the default. This ! option defines the preprocessor macro '__SETLB__'. ! '-mnosetlb' Do not allow the compiler to generate _SETLB_ or _Lcc_ instructions. This option defines the preprocessor macro ! '__NO_SETLB__'.  File: gcc.info, Node: Moxie Options, Next: MSP430 Options, Prev: MN10300 Options, Up: Submodel Options --- 17607,17679 ---- 3.18.28 MN10300 Options ----------------------- ! These `-m' options are defined for Matsushita MN10300 architectures: ! `-mmult-bug' Generate code to avoid bugs in the multiply instructions for the MN10300 processors. This is the default. ! `-mno-mult-bug' ! Do not generate code to avoid bugs in the multiply instructions ! for the MN10300 processors. ! `-mam33' Generate code using features specific to the AM33 processor. ! `-mno-am33' ! Do not generate code using features specific to the AM33 ! processor. This is the default. ! `-mam33-2' Generate code using features specific to the AM33/2.0 processor. ! `-mam34' Generate code using features specific to the AM34 processor. ! `-mtune=CPU-TYPE' Use the timing characteristics of the indicated CPU type when scheduling instructions. This does not change the targeted ! processor type. The CPU type must be one of `mn10300', `am33', ! `am33-2' or `am34'. ! `-mreturn-pointer-on-d0' When generating a function that returns a pointer, return the ! pointer in both `a0' and `d0'. Otherwise, the pointer is returned ! only in `a0', and attempts to call such functions without a prototype result in errors. Note that this option is on by ! default; use `-mno-return-pointer-on-d0' to disable it. ! `-mno-crt0' Do not link in the C run-time initialization object file. ! `-mrelax' Indicate to the linker that it should perform a relaxation optimization pass to shorten branches, calls and absolute memory ! addresses. This option only has an effect when used on the ! command line for the final link step. This option makes symbolic debugging impossible. ! `-mliw' ! Allow the compiler to generate _Long Instruction Word_ ! instructions if the target is the `AM33' or later. This is the ! default. This option defines the preprocessor macro `__LIW__'. ! `-mnoliw' Do not allow the compiler to generate _Long Instruction Word_ instructions. This option defines the preprocessor macro ! `__NO_LIW__'. ! `-msetlb' Allow the compiler to generate the _SETLB_ and _Lcc_ instructions ! if the target is the `AM33' or later. This is the default. This ! option defines the preprocessor macro `__SETLB__'. ! `-mnosetlb' Do not allow the compiler to generate _SETLB_ or _Lcc_ instructions. This option defines the preprocessor macro ! `__NO_SETLB__'. !  File: gcc.info, Node: Moxie Options, Next: MSP430 Options, Prev: MN10300 Options, Up: Submodel Options *************** File: gcc.info, Node: Moxie Options, N *** 17571,17590 **** 3.18.29 Moxie Options --------------------- ! '-meb' ! Generate big-endian code. This is the default for 'moxie-*-*' configurations. ! '-mel' Generate little-endian code. ! '-mmul.x' Generate mul.x and umul.x instructions. This is the default for ! 'moxiebox-*-*' configurations. ! '-mno-crt0' Do not link in the C run-time initialization object file.  File: gcc.info, Node: MSP430 Options, Next: NDS32 Options, Prev: Moxie Options, Up: Submodel Options --- 17681,17701 ---- 3.18.29 Moxie Options --------------------- ! `-meb' ! Generate big-endian code. This is the default for `moxie-*-*' configurations. ! `-mel' Generate little-endian code. ! `-mmul.x' Generate mul.x and umul.x instructions. This is the default for ! `moxiebox-*-*' configurations. ! `-mno-crt0' Do not link in the C run-time initialization object file. +  File: gcc.info, Node: MSP430 Options, Next: NDS32 Options, Prev: Moxie Options, Up: Submodel Options *************** File: gcc.info, Node: MSP430 Options, *** 17593,17667 **** These options are defined for the MSP430: ! '-masm-hex' Force assembly output to always use hex constants. Normally such constants are signed decimals, but this option is available for testsuite and/or aesthetic purposes. ! '-mmcu=' Select the MCU to target. This is used to create a C preprocessor symbol based upon the MCU name, converted to upper case and pre- ! and post-fixed with '__'. This in turn is used by the 'msp430.h' header file to select an MCU-specific supplementary header file. The option also sets the ISA to use. If the MCU name is one that is known to only support the 430 ISA then that is selected, ! otherwise the 430X ISA is selected. A generic MCU name of 'msp430' ! can also be used to select the 430 ISA. Similarly the generic ! 'msp430x' MCU name selects the 430X ISA. In addition an MCU-specific linker script is added to the linker ! command line. The script's name is the name of the MCU with '.ld' ! appended. Thus specifying '-mmcu=xxx' on the 'gcc' command line ! defines the C preprocessor symbol '__XXX__' and cause the linker to ! search for a script called 'xxx.ld'. This option is also passed on to the assembler. ! '-mwarn-mcu' ! '-mno-warn-mcu' This option enables or disables warnings about conflicts between ! the MCU name specified by the '-mmcu' option and the ISA set by the ! '-mcpu' option and/or the hardware multiply support set by the ! '-mhwmult' option. It also toggles warnings about unrecognized MCU ! names. This option is on by default. ! '-mcpu=' ! Specifies the ISA to use. Accepted values are 'msp430', 'msp430x' ! and 'msp430xv2'. This option is deprecated. The '-mmcu=' option should be used to select the ISA. ! '-msim' Link to the simulator runtime libraries and linker script. ! Overrides any scripts that would be selected by the '-mmcu=' option. ! '-mlarge' ! Use large-model addressing (20-bit pointers, 32-bit 'size_t'). ! '-msmall' ! Use small-model addressing (16-bit pointers, 16-bit 'size_t'). ! '-mrelax' This option is passed to the assembler and linker, and allows the linker to perform certain optimizations that cannot be done until the final link. ! 'mhwmult=' Describes the type of hardware multiply supported by the target. ! Accepted values are 'none' for no hardware multiply, '16bit' for ! the original 16-bit-only multiply supported by early MCUs. '32bit' ! for the 16/32-bit multiply supported by later MCUs and 'f5series' ! for the 16/32-bit multiply supported by F5-series MCUs. A value of ! 'auto' can also be given. This tells GCC to deduce the hardware ! multiply support based upon the MCU name provided by the '-mmcu' ! option. If no '-mmcu' option is specified or if the MCU name is ! not recognized then no hardware multiply support is assumed. ! 'auto' is the default setting. Hardware multiplies are normally performed by calling a library routine. This saves space in the generated code. When compiling ! at '-O3' or higher however the hardware multiplier is invoked inline. This makes for bigger, but faster code. The hardware multiply routines disable interrupts whilst running --- 17704,17778 ---- These options are defined for the MSP430: ! `-masm-hex' Force assembly output to always use hex constants. Normally such constants are signed decimals, but this option is available for testsuite and/or aesthetic purposes. ! `-mmcu=' Select the MCU to target. This is used to create a C preprocessor symbol based upon the MCU name, converted to upper case and pre- ! and post-fixed with `__'. This in turn is used by the `msp430.h' header file to select an MCU-specific supplementary header file. The option also sets the ISA to use. If the MCU name is one that is known to only support the 430 ISA then that is selected, ! otherwise the 430X ISA is selected. A generic MCU name of ! `msp430' can also be used to select the 430 ISA. Similarly the ! generic `msp430x' MCU name selects the 430X ISA. In addition an MCU-specific linker script is added to the linker ! command line. The script's name is the name of the MCU with `.ld' ! appended. Thus specifying `-mmcu=xxx' on the `gcc' command line ! defines the C preprocessor symbol `__XXX__' and cause the linker ! to search for a script called `xxx.ld'. This option is also passed on to the assembler. ! `-mwarn-mcu' ! `-mno-warn-mcu' This option enables or disables warnings about conflicts between ! the MCU name specified by the `-mmcu' option and the ISA set by the ! `-mcpu' option and/or the hardware multiply support set by the ! `-mhwmult' option. It also toggles warnings about unrecognized ! MCU names. This option is on by default. ! `-mcpu=' ! Specifies the ISA to use. Accepted values are `msp430', `msp430x' ! and `msp430xv2'. This option is deprecated. The `-mmcu=' option should be used to select the ISA. ! `-msim' Link to the simulator runtime libraries and linker script. ! Overrides any scripts that would be selected by the `-mmcu=' option. ! `-mlarge' ! Use large-model addressing (20-bit pointers, 32-bit `size_t'). ! `-msmall' ! Use small-model addressing (16-bit pointers, 16-bit `size_t'). ! `-mrelax' This option is passed to the assembler and linker, and allows the linker to perform certain optimizations that cannot be done until the final link. ! `mhwmult=' Describes the type of hardware multiply supported by the target. ! Accepted values are `none' for no hardware multiply, `16bit' for ! the original 16-bit-only multiply supported by early MCUs. ! `32bit' for the 16/32-bit multiply supported by later MCUs and ! `f5series' for the 16/32-bit multiply supported by F5-series MCUs. ! A value of `auto' can also be given. This tells GCC to deduce the ! hardware multiply support based upon the MCU name provided by the ! `-mmcu' option. If no `-mmcu' option is specified or if the MCU ! name is not recognized then no hardware multiply support is ! assumed. `auto' is the default setting. Hardware multiplies are normally performed by calling a library routine. This saves space in the generated code. When compiling ! at `-O3' or higher however the hardware multiplier is invoked inline. This makes for bigger, but faster code. The hardware multiply routines disable interrupts whilst running *************** These options are defined for the MSP430 *** 17669,17699 **** makes them safe to use inside interrupt handlers as well as in normal code. ! '-minrt' Enable the use of a minimum runtime environment - no static initializers or constructors. This is intended for memory-constrained devices. The compiler includes special symbols in some objects that tell the linker and runtime which code fragments are required. ! '-mcode-region=' ! '-mdata-region=' These options tell the compiler where to place functions and data ! that do not have one of the 'lower', 'upper', 'either' or 'section' ! attributes. Possible values are 'lower', 'upper', 'either' or ! 'any'. The first three behave like the corresponding attribute. ! The fourth possible value - 'any' - is the default. It leaves ! placement entirely up to the linker script and how it assigns the ! standard sections ('.text', '.data', etc) to the memory regions. ! '-msilicon-errata=' This option passes on a request to assembler to enable the fixes for the named silicon errata. ! '-msilicon-errata-warn=' This option passes on a request to the assembler to enable warning messages when a silicon errata might need to be applied.  File: gcc.info, Node: NDS32 Options, Next: Nios II Options, Prev: MSP430 Options, Up: Submodel Options --- 17780,17812 ---- makes them safe to use inside interrupt handlers as well as in normal code. ! `-minrt' Enable the use of a minimum runtime environment - no static initializers or constructors. This is intended for memory-constrained devices. The compiler includes special symbols in some objects that tell the linker and runtime which code fragments are required. ! `-mcode-region=' ! `-mdata-region=' These options tell the compiler where to place functions and data ! that do not have one of the `lower', `upper', `either' or ! `section' attributes. Possible values are `lower', `upper', ! `either' or `any'. The first three behave like the corresponding ! attribute. The fourth possible value - `any' - is the default. ! It leaves placement entirely up to the linker script and how it ! assigns the standard sections (`.text', `.data', etc) to the ! memory regions. ! `-msilicon-errata=' This option passes on a request to assembler to enable the fixes for the named silicon errata. ! `-msilicon-errata-warn=' This option passes on a request to the assembler to enable warning messages when a silicon errata might need to be applied. +  File: gcc.info, Node: NDS32 Options, Next: Nios II Options, Prev: MSP430 Options, Up: Submodel Options *************** File: gcc.info, Node: NDS32 Options, N *** 17702,17773 **** These options are defined for NDS32 implementations: ! '-mbig-endian' Generate code in big-endian mode. ! '-mlittle-endian' Generate code in little-endian mode. ! '-mreduced-regs' Use reduced-set registers for register allocation. ! '-mfull-regs' Use full-set registers for register allocation. ! '-mcmov' Generate conditional move instructions. ! '-mno-cmov' Do not generate conditional move instructions. ! '-mperf-ext' Generate performance extension instructions. ! '-mno-perf-ext' Do not generate performance extension instructions. ! '-mv3push' Generate v3 push25/pop25 instructions. ! '-mno-v3push' Do not generate v3 push25/pop25 instructions. ! '-m16-bit' Generate 16-bit instructions. ! '-mno-16-bit' Do not generate 16-bit instructions. ! '-misr-vector-size=NUM' Specify the size of each interrupt vector, which must be 4 or 16. ! '-mcache-block-size=NUM' Specify the size of each cache block, which must be a power of 2 between 4 and 512. ! '-march=ARCH' Specify the name of the target architecture. ! '-mcmodel=CODE-MODEL' Set the code model to one of ! 'small' All the data and read-only data segments must be within 512KB addressing space. The text segment must be within 16MB addressing space. ! 'medium' ! The data segment must be within 512KB while the read-only data ! segment can be within 4GB addressing space. The text segment ! should be still within 16MB addressing space. ! 'large' All the text and data segments can be within 4GB addressing space. ! '-mctor-dtor' Enable constructor/destructor feature. ! '-mrelax' Guide linker to relax instructions.  File: gcc.info, Node: Nios II Options, Next: Nvidia PTX Options, Prev: NDS32 Options, Up: Submodel Options --- 17815,17889 ---- These options are defined for NDS32 implementations: ! `-mbig-endian' Generate code in big-endian mode. ! `-mlittle-endian' Generate code in little-endian mode. ! `-mreduced-regs' Use reduced-set registers for register allocation. ! `-mfull-regs' Use full-set registers for register allocation. ! `-mcmov' Generate conditional move instructions. ! `-mno-cmov' Do not generate conditional move instructions. ! `-mperf-ext' Generate performance extension instructions. ! `-mno-perf-ext' Do not generate performance extension instructions. ! `-mv3push' Generate v3 push25/pop25 instructions. ! `-mno-v3push' Do not generate v3 push25/pop25 instructions. ! `-m16-bit' Generate 16-bit instructions. ! `-mno-16-bit' Do not generate 16-bit instructions. ! `-misr-vector-size=NUM' Specify the size of each interrupt vector, which must be 4 or 16. ! `-mcache-block-size=NUM' Specify the size of each cache block, which must be a power of 2 between 4 and 512. ! `-march=ARCH' Specify the name of the target architecture. ! `-mcmodel=CODE-MODEL' Set the code model to one of ! `small' All the data and read-only data segments must be within 512KB addressing space. The text segment must be within 16MB addressing space. ! ! `medium' ! The data segment must be within 512KB while the read-only ! data segment can be within 4GB addressing space. The text ! segment should be still within 16MB addressing space. ! ! `large' All the text and data segments can be within 4GB addressing space. ! `-mctor-dtor' Enable constructor/destructor feature. ! `-mrelax' Guide linker to relax instructions. +  File: gcc.info, Node: Nios II Options, Next: Nvidia PTX Options, Prev: NDS32 Options, Up: Submodel Options *************** File: gcc.info, Node: Nios II Options, *** 17776,17816 **** These are the options defined for the Altera Nios II processor. ! '-G NUM' Put global and static objects less than or equal to NUM bytes into the small data or BSS sections instead of the normal data or BSS sections. The default value of NUM is 8. ! '-mgpopt=OPTION' ! '-mgpopt' ! '-mno-gpopt' Generate (do not generate) GP-relative accesses. The following OPTION names are recognized: ! 'none' Do not generate GP-relative accesses. ! 'local' Generate GP-relative accesses for small data objects that are ! not external, weak, or uninitialized common symbols. Also use ! GP-relative addressing for objects that have been explicitly ! placed in a small data section via a 'section' attribute. ! 'global' ! As for 'local', but also generate GP-relative accesses for ! small data objects that are external, weak, or common. If you ! use this option, you must ensure that all parts of your ! program (including libraries) are compiled with the same '-G' setting. ! 'data' Generate GP-relative accesses for all data objects in the program. If you use this option, the entire data and BSS segments of your program must fit in 64K of memory and you must use an appropriate linker script to allocate them within the addressable range of the global pointer. ! 'all' Generate GP-relative addresses for function pointers as well as data pointers. If you use this option, the entire text, data, and BSS segments of your program must fit in 64K of --- 17892,17934 ---- These are the options defined for the Altera Nios II processor. ! `-G NUM' Put global and static objects less than or equal to NUM bytes into the small data or BSS sections instead of the normal data or BSS sections. The default value of NUM is 8. ! `-mgpopt=OPTION' ! ! `-mgpopt' ! `-mno-gpopt' Generate (do not generate) GP-relative accesses. The following OPTION names are recognized: ! `none' Do not generate GP-relative accesses. ! `local' Generate GP-relative accesses for small data objects that are ! not external, weak, or uninitialized common symbols. Also ! use GP-relative addressing for objects that have been ! explicitly placed in a small data section via a `section' ! attribute. ! `global' ! As for `local', but also generate GP-relative accesses for ! small data objects that are external, weak, or common. If ! you use this option, you must ensure that all parts of your ! program (including libraries) are compiled with the same `-G' setting. ! `data' Generate GP-relative accesses for all data objects in the program. If you use this option, the entire data and BSS segments of your program must fit in 64K of memory and you must use an appropriate linker script to allocate them within the addressable range of the global pointer. ! `all' Generate GP-relative addresses for function pointers as well as data pointers. If you use this option, the entire text, data, and BSS segments of your program must fit in 64K of *************** These are the options defined for the Al *** 17818,17891 **** allocate them within the addressable range of the global pointer. - '-mgpopt' is equivalent to '-mgpopt=local', and '-mno-gpopt' is - equivalent to '-mgpopt=none'. ! The default is '-mgpopt' except when '-fpic' or '-fPIC' is specified to generate position-independent code. Note that the Nios II ABI does not permit GP-relative accesses from shared libraries. ! You may need to specify '-mno-gpopt' explicitly when building programs that include large amounts of small data, including large GOT data sections. In this case, the 16-bit offset for GP-relative addressing may not be large enough to allow access to the entire small data section. ! '-mel' ! '-meb' Generate little-endian (default) or big-endian (experimental) code, respectively. ! '-march=ARCH' This specifies the name of the target Nios II architecture. GCC uses this name to determine what kind of instructions it can emit ! when generating assembly code. Permissible names are: 'r1', 'r2'. ! The preprocessor macro '__nios2_arch__' is available to programs, with value 1 or 2, indicating the targeted ISA level. ! '-mbypass-cache' ! '-mno-bypass-cache' Force all load and store instructions to always bypass cache by ! using I/O variants of the instructions. The default is not to bypass the cache. ! '-mno-cache-volatile' ! '-mcache-volatile' Volatile memory access bypass the cache using the I/O variants of ! the load and store instructions. The default is not to bypass the cache. ! '-mno-fast-sw-div' ! '-mfast-sw-div' ! Do not use table-based fast divide for small numbers. The default ! is to use the fast divide at '-O3' and above. ! '-mno-hw-mul' ! '-mhw-mul' ! '-mno-hw-mulx' ! '-mhw-mulx' ! '-mno-hw-div' ! '-mhw-div' ! Enable or disable emitting 'mul', 'mulx' and 'div' family of ! instructions by the compiler. The default is to emit 'mul' and not ! emit 'div' and 'mulx'. ! '-mbmx' ! '-mno-bmx' ! '-mcdx' ! '-mno-cdx' Enable or disable generation of Nios II R2 BMX (bit manipulation) and CDX (code density) instructions. Enabling these instructions ! also requires '-march=r2'. Since these instructions are optional extensions to the R2 architecture, the default is not to emit them. ! '-mcustom-INSN=N' ! '-mno-custom-INSN' ! Each '-mcustom-INSN=N' option enables use of a custom instruction with encoding N when generating code that uses INSN. For example, ! '-mcustom-fadds=253' generates custom instruction 253 for single-precision floating-point add operations instead of the default behavior of using a library call. --- 17936,18010 ---- allocate them within the addressable range of the global pointer. ! `-mgpopt' is equivalent to `-mgpopt=local', and `-mno-gpopt' is ! equivalent to `-mgpopt=none'. ! ! The default is `-mgpopt' except when `-fpic' or `-fPIC' is specified to generate position-independent code. Note that the Nios II ABI does not permit GP-relative accesses from shared libraries. ! You may need to specify `-mno-gpopt' explicitly when building programs that include large amounts of small data, including large GOT data sections. In this case, the 16-bit offset for GP-relative addressing may not be large enough to allow access to the entire small data section. ! `-mel' ! `-meb' Generate little-endian (default) or big-endian (experimental) code, respectively. ! `-march=ARCH' This specifies the name of the target Nios II architecture. GCC uses this name to determine what kind of instructions it can emit ! when generating assembly code. Permissible names are: `r1', `r2'. ! The preprocessor macro `__nios2_arch__' is available to programs, with value 1 or 2, indicating the targeted ISA level. ! `-mbypass-cache' ! `-mno-bypass-cache' Force all load and store instructions to always bypass cache by ! using I/O variants of the instructions. The default is not to bypass the cache. ! `-mno-cache-volatile' ! `-mcache-volatile' Volatile memory access bypass the cache using the I/O variants of ! the load and store instructions. The default is not to bypass the cache. ! `-mno-fast-sw-div' ! `-mfast-sw-div' ! Do not use table-based fast divide for small numbers. The default ! is to use the fast divide at `-O3' and above. ! `-mno-hw-mul' ! `-mhw-mul' ! `-mno-hw-mulx' ! `-mhw-mulx' ! `-mno-hw-div' ! `-mhw-div' ! Enable or disable emitting `mul', `mulx' and `div' family of ! instructions by the compiler. The default is to emit `mul' and not ! emit `div' and `mulx'. ! `-mbmx' ! `-mno-bmx' ! `-mcdx' ! `-mno-cdx' Enable or disable generation of Nios II R2 BMX (bit manipulation) and CDX (code density) instructions. Enabling these instructions ! also requires `-march=r2'. Since these instructions are optional extensions to the R2 architecture, the default is not to emit them. ! `-mcustom-INSN=N' ! `-mno-custom-INSN' ! Each `-mcustom-INSN=N' option enables use of a custom instruction with encoding N when generating code that uses INSN. For example, ! `-mcustom-fadds=253' generates custom instruction 253 for single-precision floating-point add operations instead of the default behavior of using a library call. *************** These are the options defined for the Al *** 17896,18027 **** Builtins::). Single-precision floating point: ! ! 'fadds', 'fsubs', 'fdivs', 'fmuls' Binary arithmetic operations. ! 'fnegs' Unary negation. ! 'fabss' Unary absolute value. ! 'fcmpeqs', 'fcmpges', 'fcmpgts', 'fcmples', 'fcmplts', 'fcmpnes' Comparison operations. ! 'fmins', 'fmaxs' Floating-point minimum and maximum. These instructions are ! only generated if '-ffinite-math-only' is specified. ! 'fsqrts' Unary square root operation. ! 'fcoss', 'fsins', 'ftans', 'fatans', 'fexps', 'flogs' ! Floating-point trigonometric and exponential functions. These ! instructions are only generated if ! '-funsafe-math-optimizations' is also specified. - Double-precision floating point: ! 'faddd', 'fsubd', 'fdivd', 'fmuld' Binary arithmetic operations. ! 'fnegd' Unary negation. ! 'fabsd' Unary absolute value. ! 'fcmpeqd', 'fcmpged', 'fcmpgtd', 'fcmpled', 'fcmpltd', 'fcmpned' Comparison operations. ! 'fmind', 'fmaxd' Double-precision minimum and maximum. These instructions are ! only generated if '-ffinite-math-only' is specified. ! 'fsqrtd' Unary square root operation. ! 'fcosd', 'fsind', 'ftand', 'fatand', 'fexpd', 'flogd' Double-precision trigonometric and exponential functions. These instructions are only generated if ! '-funsafe-math-optimizations' is also specified. Conversions: ! 'fextsd' Conversion from single precision to double precision. ! 'ftruncds' Conversion from double precision to single precision. ! 'fixsi', 'fixsu', 'fixdi', 'fixdu' Conversion from floating point to signed or unsigned integer types, with truncation towards zero. ! 'round' Conversion from single-precision floating point to signed integer, rounding to the nearest integer and ties away from ! zero. This corresponds to the '__builtin_lroundf' function ! when '-fno-math-errno' is used. ! 'floatis', 'floatus', 'floatid', 'floatud' Conversion from signed or unsigned integer types to floating-point types. In addition, all of the following transfer instructions for internal registers X and Y must be provided to use any of the double-precision floating-point instructions. Custom instructions taking two double-precision source operands expect the first ! operand in the 64-bit register X. The other operand (or only operand of a unary operation) is given to the custom arithmetic ! instruction with the least significant half in source register SRC1 ! and the most significant half in SRC2. A custom instruction that ! returns a double-precision result returns the most significant 32 ! bits in the destination register and the other half in 32-bit ! register Y. GCC automatically generates the necessary code ! sequences to write register X and/or read register Y when double-precision floating-point instructions are used. ! 'fwrx' Write SRC1 into the least significant half of X and SRC2 into the most significant half of X. ! 'fwry' Write SRC1 into Y. ! 'frdxhi', 'frdxlo' Read the most or least (respectively) significant half of X and store it in DEST. ! 'frdy' Read the value of Y and store it into DEST. Note that you can gain more local control over generation of Nios ! II custom instructions by using the 'target("custom-INSN=N")' and ! 'target("no-custom-INSN")' function attributes (*note Function Attributes::) or pragmas (*note Function Specific Option Pragmas::). ! '-mcustom-fpu-cfg=NAME' ! This option enables a predefined, named set of custom instruction ! encodings (see '-mcustom-INSN' above). Currently, the following sets are defined: ! '-mcustom-fpu-cfg=60-1' is equivalent to: -mcustom-fmuls=252 -mcustom-fadds=253 -mcustom-fsubs=254 -fsingle-precision-constant ! '-mcustom-fpu-cfg=60-2' is equivalent to: -mcustom-fmuls=252 -mcustom-fadds=253 -mcustom-fsubs=254 -mcustom-fdivs=255 -fsingle-precision-constant ! '-mcustom-fpu-cfg=72-3' is equivalent to: -mcustom-floatus=243 -mcustom-fixsi=244 -mcustom-floatis=245 --- 18015,18146 ---- Builtins::). Single-precision floating point: ! `fadds', `fsubs', `fdivs', `fmuls' Binary arithmetic operations. ! `fnegs' Unary negation. ! `fabss' Unary absolute value. ! `fcmpeqs', `fcmpges', `fcmpgts', `fcmples', `fcmplts', `fcmpnes' Comparison operations. ! `fmins', `fmaxs' Floating-point minimum and maximum. These instructions are ! only generated if `-ffinite-math-only' is specified. ! `fsqrts' Unary square root operation. ! `fcoss', `fsins', `ftans', `fatans', `fexps', `flogs' ! Floating-point trigonometric and exponential functions. ! These instructions are only generated if ! `-funsafe-math-optimizations' is also specified. ! Double-precision floating point: ! `faddd', `fsubd', `fdivd', `fmuld' Binary arithmetic operations. ! `fnegd' Unary negation. ! `fabsd' Unary absolute value. ! `fcmpeqd', `fcmpged', `fcmpgtd', `fcmpled', `fcmpltd', `fcmpned' Comparison operations. ! `fmind', `fmaxd' Double-precision minimum and maximum. These instructions are ! only generated if `-ffinite-math-only' is specified. ! `fsqrtd' Unary square root operation. ! `fcosd', `fsind', `ftand', `fatand', `fexpd', `flogd' Double-precision trigonometric and exponential functions. These instructions are only generated if ! `-funsafe-math-optimizations' is also specified. ! Conversions: ! `fextsd' Conversion from single precision to double precision. ! `ftruncds' Conversion from double precision to single precision. ! `fixsi', `fixsu', `fixdi', `fixdu' Conversion from floating point to signed or unsigned integer types, with truncation towards zero. ! `round' Conversion from single-precision floating point to signed integer, rounding to the nearest integer and ties away from ! zero. This corresponds to the `__builtin_lroundf' function ! when `-fno-math-errno' is used. ! `floatis', `floatus', `floatid', `floatud' Conversion from signed or unsigned integer types to floating-point types. + In addition, all of the following transfer instructions for internal registers X and Y must be provided to use any of the double-precision floating-point instructions. Custom instructions taking two double-precision source operands expect the first ! operand in the 64-bit register X. The other operand (or only operand of a unary operation) is given to the custom arithmetic ! instruction with the least significant half in source register ! SRC1 and the most significant half in SRC2. A custom instruction ! that returns a double-precision result returns the most ! significant 32 bits in the destination register and the other half ! in 32-bit register Y. GCC automatically generates the necessary ! code sequences to write register X and/or read register Y when double-precision floating-point instructions are used. ! `fwrx' Write SRC1 into the least significant half of X and SRC2 into the most significant half of X. ! `fwry' Write SRC1 into Y. ! `frdxhi', `frdxlo' Read the most or least (respectively) significant half of X and store it in DEST. ! `frdy' Read the value of Y and store it into DEST. Note that you can gain more local control over generation of Nios ! II custom instructions by using the `target("custom-INSN=N")' and ! `target("no-custom-INSN")' function attributes (*note Function Attributes::) or pragmas (*note Function Specific Option Pragmas::). ! `-mcustom-fpu-cfg=NAME' This option enables a predefined, named set of custom instruction ! encodings (see `-mcustom-INSN' above). Currently, the following sets are defined: ! `-mcustom-fpu-cfg=60-1' is equivalent to: -mcustom-fmuls=252 -mcustom-fadds=253 -mcustom-fsubs=254 -fsingle-precision-constant ! `-mcustom-fpu-cfg=60-2' is equivalent to: -mcustom-fmuls=252 -mcustom-fadds=253 -mcustom-fsubs=254 -mcustom-fdivs=255 -fsingle-precision-constant ! `-mcustom-fpu-cfg=72-3' is equivalent to: -mcustom-floatus=243 -mcustom-fixsi=244 -mcustom-floatis=245 *************** These are the options defined for the Al *** 18035,18072 **** -mcustom-fdivs=255 -fsingle-precision-constant ! Custom instruction assignments given by individual '-mcustom-INSN=' ! options override those given by '-mcustom-fpu-cfg=', regardless of ! the order of the options on the command line. Note that you can gain more local control over selection of a FPU ! configuration by using the 'target("custom-fpu-cfg=NAME")' function ! attribute (*note Function Attributes::) or pragma (*note Function ! Specific Option Pragmas::). ! These additional '-m' options are available for the Altera Nios II ELF (bare-metal) target: ! '-mhal' ! Link with HAL BSP. This suppresses linking with the GCC-provided C ! runtime startup and termination code, and is typically used in ! conjunction with '-msys-crt0=' to specify the location of the alternate startup code provided by the HAL BSP. ! '-msmallc' ! Link with a limited version of the C library, '-lsmallc', rather than Newlib. ! '-msys-crt0=STARTFILE' STARTFILE is the file name of the startfile (crt0) to use when ! linking. This option is only useful in conjunction with '-mhal'. ! '-msys-lib=SYSTEMLIB' SYSTEMLIB is the library name of the library that provides ! low-level system calls required by the C library, e.g. 'read' and ! 'write'. This option is typically used to link with a library provided by a HAL BSP.  File: gcc.info, Node: Nvidia PTX Options, Next: PDP-11 Options, Prev: Nios II Options, Up: Submodel Options --- 18154,18194 ---- -mcustom-fdivs=255 -fsingle-precision-constant ! Custom instruction assignments given by individual ! `-mcustom-INSN=' options override those given by ! `-mcustom-fpu-cfg=', regardless of the order of the options on the ! command line. Note that you can gain more local control over selection of a FPU ! configuration by using the `target("custom-fpu-cfg=NAME")' ! function attribute (*note Function Attributes::) or pragma (*note ! Function Specific Option Pragmas::). ! ! These additional `-m' options are available for the Altera Nios II ELF (bare-metal) target: ! `-mhal' ! Link with HAL BSP. This suppresses linking with the GCC-provided ! C runtime startup and termination code, and is typically used in ! conjunction with `-msys-crt0=' to specify the location of the alternate startup code provided by the HAL BSP. ! `-msmallc' ! Link with a limited version of the C library, `-lsmallc', rather than Newlib. ! `-msys-crt0=STARTFILE' STARTFILE is the file name of the startfile (crt0) to use when ! linking. This option is only useful in conjunction with `-mhal'. ! `-msys-lib=SYSTEMLIB' SYSTEMLIB is the library name of the library that provides ! low-level system calls required by the C library, e.g. `read' and ! `write'. This option is typically used to link with a library provided by a HAL BSP. +  File: gcc.info, Node: Nvidia PTX Options, Next: PDP-11 Options, Prev: Nios II Options, Up: Submodel Options *************** File: gcc.info, Node: Nvidia PTX Option *** 18075,18092 **** These options are defined for Nvidia PTX: ! '-m32' ! '-m64' Generate code for 32-bit or 64-bit ABI. ! '-mmainkernel' Link in code for a __main kernel. This is for stand-alone instead of offloading execution. ! '-moptimize' Apply partitioned execution optimizations. This is the default when any level of optimization is selected.  File: gcc.info, Node: PDP-11 Options, Next: picoChip Options, Prev: Nvidia PTX Options, Up: Submodel Options --- 18197,18215 ---- These options are defined for Nvidia PTX: ! `-m32' ! `-m64' Generate code for 32-bit or 64-bit ABI. ! `-mmainkernel' Link in code for a __main kernel. This is for stand-alone instead of offloading execution. ! `-moptimize' Apply partitioned execution optimizations. This is the default when any level of optimization is selected. +  File: gcc.info, Node: PDP-11 Options, Next: picoChip Options, Prev: Nvidia PTX Options, Up: Submodel Options *************** File: gcc.info, Node: PDP-11 Options, *** 18095,18166 **** These options are defined for the PDP-11: ! '-mfpu' Use hardware FPP floating point. This is the default. (FIS floating point on the PDP-11/40 is not supported.) ! '-msoft-float' Do not use hardware floating point. ! '-mac0' Return floating-point results in ac0 (fr0 in Unix assembler syntax). ! '-mno-ac0' Return floating-point results in memory. This is the default. ! '-m40' Generate code for a PDP-11/40. ! '-m45' Generate code for a PDP-11/45. This is the default. ! '-m10' Generate code for a PDP-11/10. ! '-mbcopy-builtin' ! Use inline 'movmemhi' patterns for copying memory. This is the default. ! '-mbcopy' ! Do not use inline 'movmemhi' patterns for copying memory. ! '-mint16' ! '-mno-int32' ! Use 16-bit 'int'. This is the default. ! '-mint32' ! '-mno-int16' ! Use 32-bit 'int'. ! '-mfloat64' ! '-mno-float32' ! Use 64-bit 'float'. This is the default. ! '-mfloat32' ! '-mno-float64' ! Use 32-bit 'float'. ! '-mabshi' ! Use 'abshi2' pattern. This is the default. ! '-mno-abshi' ! Do not use 'abshi2' pattern. ! '-mbranch-expensive' Pretend that branches are expensive. This is for experimenting with code generation only. ! '-mbranch-cheap' Do not pretend that branches are expensive. This is the default. ! '-munix-asm' Use Unix assembler syntax. This is the default when configured for ! 'pdp11-*-bsd'. ! '-mdec-asm' Use DEC assembler syntax. This is the default when configured for ! any PDP-11 target other than 'pdp11-*-bsd'.  File: gcc.info, Node: picoChip Options, Next: PowerPC Options, Prev: PDP-11 Options, Up: Submodel Options --- 18218,18289 ---- These options are defined for the PDP-11: ! `-mfpu' Use hardware FPP floating point. This is the default. (FIS floating point on the PDP-11/40 is not supported.) ! `-msoft-float' Do not use hardware floating point. ! `-mac0' Return floating-point results in ac0 (fr0 in Unix assembler syntax). ! `-mno-ac0' Return floating-point results in memory. This is the default. ! `-m40' Generate code for a PDP-11/40. ! `-m45' Generate code for a PDP-11/45. This is the default. ! `-m10' Generate code for a PDP-11/10. ! `-mbcopy-builtin' ! Use inline `movmemhi' patterns for copying memory. This is the default. ! `-mbcopy' ! Do not use inline `movmemhi' patterns for copying memory. ! `-mint16' ! `-mno-int32' ! Use 16-bit `int'. This is the default. ! `-mint32' ! `-mno-int16' ! Use 32-bit `int'. ! `-mfloat64' ! `-mno-float32' ! Use 64-bit `float'. This is the default. ! `-mfloat32' ! `-mno-float64' ! Use 32-bit `float'. ! `-mabshi' ! Use `abshi2' pattern. This is the default. ! `-mno-abshi' ! Do not use `abshi2' pattern. ! `-mbranch-expensive' Pretend that branches are expensive. This is for experimenting with code generation only. ! `-mbranch-cheap' Do not pretend that branches are expensive. This is the default. ! `-munix-asm' Use Unix assembler syntax. This is the default when configured for ! `pdp11-*-bsd'. ! `-mdec-asm' Use DEC assembler syntax. This is the default when configured for ! any PDP-11 target other than `pdp11-*-bsd'.  File: gcc.info, Node: picoChip Options, Next: PowerPC Options, Prev: PDP-11 Options, Up: Submodel Options *************** File: gcc.info, Node: picoChip Options, *** 18168,18212 **** 3.18.35 picoChip Options ------------------------ ! These '-m' options are defined for picoChip implementations: ! '-mae=AE_TYPE' Set the instruction set, register set, and instruction scheduling parameters for array element type AE_TYPE. Supported values for ! AE_TYPE are 'ANY', 'MUL', and 'MAC'. ! '-mae=ANY' selects a completely generic AE type. Code generated with this option runs on any of the other AE types. The code is ! not as efficient as it would be if compiled for a specific AE type, ! and some types of operation (e.g., multiplication) do not work ! properly on all types of AE. ! '-mae=MUL' selects a MUL AE type. This is the most useful AE type for compiled code, and is the default. ! '-mae=MAC' selects a DSP-style MAC AE. Code compiled with this option may suffer from poor performance of byte (char) manipulation, since the DSP AE does not provide hardware support for byte load/stores. ! '-msymbol-as-address' Enable the compiler to directly use a symbol name as an address in ! a load/store instruction, without first loading it into a register. ! Typically, the use of this option generates larger programs, which ! run faster than when the option isn't used. However, the results ! vary from program to program, so it is left as a user option, ! rather than being permanently enabled. ! '-mno-inefficient-warnings' Disables warnings about the generation of inefficient code. These warnings can be generated, for example, when compiling code that performs byte-level memory operations on the MAC AE type. The MAC ! AE has no hardware support for byte-level memory operations, so all ! byte load/stores must be synthesized from word load/store operations. This is inefficient and a warning is generated to ! indicate that you should rewrite the code to avoid byte operations, ! or to target an AE type that has the necessary hardware support. ! This option disables these warnings.  File: gcc.info, Node: PowerPC Options, Next: RL78 Options, Prev: picoChip Options, Up: Submodel Options --- 18291,18336 ---- 3.18.35 picoChip Options ------------------------ ! These `-m' options are defined for picoChip implementations: ! `-mae=AE_TYPE' Set the instruction set, register set, and instruction scheduling parameters for array element type AE_TYPE. Supported values for ! AE_TYPE are `ANY', `MUL', and `MAC'. ! `-mae=ANY' selects a completely generic AE type. Code generated with this option runs on any of the other AE types. The code is ! not as efficient as it would be if compiled for a specific AE ! type, and some types of operation (e.g., multiplication) do not ! work properly on all types of AE. ! `-mae=MUL' selects a MUL AE type. This is the most useful AE type for compiled code, and is the default. ! `-mae=MAC' selects a DSP-style MAC AE. Code compiled with this option may suffer from poor performance of byte (char) manipulation, since the DSP AE does not provide hardware support for byte load/stores. ! `-msymbol-as-address' Enable the compiler to directly use a symbol name as an address in ! a load/store instruction, without first loading it into a ! register. Typically, the use of this option generates larger ! programs, which run faster than when the option isn't used. ! However, the results vary from program to program, so it is left ! as a user option, rather than being permanently enabled. ! `-mno-inefficient-warnings' Disables warnings about the generation of inefficient code. These warnings can be generated, for example, when compiling code that performs byte-level memory operations on the MAC AE type. The MAC ! AE has no hardware support for byte-level memory operations, so ! all byte load/stores must be synthesized from word load/store operations. This is inefficient and a warning is generated to ! indicate that you should rewrite the code to avoid byte ! operations, or to target an AE type that has the necessary ! hardware support. This option disables these warnings. !  File: gcc.info, Node: PowerPC Options, Next: RL78 Options, Prev: picoChip Options, Up: Submodel Options *************** File: gcc.info, Node: RL78 Options, Ne *** 18222,18268 **** 3.18.37 RL78 Options -------------------- ! '-msim' Links in additional target libraries to support operation within a simulator. ! '-mmul=none' ! '-mmul=g10' ! '-mmul=g13' ! '-mmul=g14' ! '-mmul=rl78' Specifies the type of hardware multiplication and division support ! to be used. The simplest is 'none', which uses software for both ! multiplication and division. This is the default. The 'g13' value ! is for the hardware multiply/divide peripheral found on the ! RL78/G13 (S2 core) targets. The 'g14' value selects the use of the ! multiplication and division instructions supported by the RL78/G14 ! (S3 core) parts. The value 'rl78' is an alias for 'g14' and the ! value 'mg10' is an alias for 'none'. In addition a C preprocessor macro is defined, based upon the ! setting of this option. Possible values are: '__RL78_MUL_NONE__', ! '__RL78_MUL_G13__' or '__RL78_MUL_G14__'. ! '-mcpu=g10' ! '-mcpu=g13' ! '-mcpu=g14' ! '-mcpu=rl78' Specifies the RL78 core to target. The default is the G14 core, ! also known as an S3 core or just RL78. The G13 or S2 core does not ! have multiply or divide instructions, instead it uses a hardware ! peripheral for these operations. The G10 or S1 core does not have ! register banks, so it uses a different calling convention. If this option is set it also selects the type of hardware multiply support to use, unless this is overridden by an explicit ! '-mmul=none' option on the command line. Thus specifying ! '-mcpu=g13' enables the use of the G13 hardware multiply peripheral ! and specifying '-mcpu=g10' disables the use of hardware multiplications altogether. Note, although the RL78/G14 core is the default target, specifying ! '-mcpu=g14' or '-mcpu=rl78' on the command line does change the behavior of the toolchain since it also enables G14 hardware multiply support. If these options are not specified on the command line then software multiplication routines will be used --- 18346,18392 ---- 3.18.37 RL78 Options -------------------- ! `-msim' Links in additional target libraries to support operation within a simulator. ! `-mmul=none' ! `-mmul=g10' ! `-mmul=g13' ! `-mmul=g14' ! `-mmul=rl78' Specifies the type of hardware multiplication and division support ! to be used. The simplest is `none', which uses software for both ! multiplication and division. This is the default. The `g13' ! value is for the hardware multiply/divide peripheral found on the ! RL78/G13 (S2 core) targets. The `g14' value selects the use of ! the multiplication and division instructions supported by the ! RL78/G14 (S3 core) parts. The value `rl78' is an alias for `g14' ! and the value `mg10' is an alias for `none'. In addition a C preprocessor macro is defined, based upon the ! setting of this option. Possible values are: `__RL78_MUL_NONE__', ! `__RL78_MUL_G13__' or `__RL78_MUL_G14__'. ! `-mcpu=g10' ! `-mcpu=g13' ! `-mcpu=g14' ! `-mcpu=rl78' Specifies the RL78 core to target. The default is the G14 core, ! also known as an S3 core or just RL78. The G13 or S2 core does ! not have multiply or divide instructions, instead it uses a ! hardware peripheral for these operations. The G10 or S1 core does ! not have register banks, so it uses a different calling convention. If this option is set it also selects the type of hardware multiply support to use, unless this is overridden by an explicit ! `-mmul=none' option on the command line. Thus specifying ! `-mcpu=g13' enables the use of the G13 hardware multiply ! peripheral and specifying `-mcpu=g10' disables the use of hardware multiplications altogether. Note, although the RL78/G14 core is the default target, specifying ! `-mcpu=g14' or `-mcpu=rl78' on the command line does change the behavior of the toolchain since it also enables G14 hardware multiply support. If these options are not specified on the command line then software multiplication routines will be used *************** File: gcc.info, Node: RL78 Options, Ne *** 18271,18297 **** multiply and divide support. In addition a C preprocessor macro is defined, based upon the ! setting of this option. Possible values are: '__RL78_G10__', ! '__RL78_G13__' or '__RL78_G14__'. ! '-mg10' ! '-mg13' ! '-mg14' ! '-mrl78' ! These are aliases for the corresponding '-mcpu=' option. They are provided for backwards compatibility. ! '-mallregs' Allow the compiler to use all of the available registers. By ! default registers 'r24..r31' are reserved for use in interrupt handlers. With this option enabled these registers can be used in ordinary functions as well. ! '-m64bit-doubles' ! '-m32bit-doubles' ! Make the 'double' data type be 64 bits ('-m64bit-doubles') or 32 ! bits ('-m32bit-doubles') in size. The default is ! '-m32bit-doubles'.  File: gcc.info, Node: RS/6000 and PowerPC Options, Next: RX Options, Prev: RL78 Options, Up: Submodel Options --- 18395,18422 ---- multiply and divide support. In addition a C preprocessor macro is defined, based upon the ! setting of this option. Possible values are: `__RL78_G10__', ! `__RL78_G13__' or `__RL78_G14__'. ! `-mg10' ! `-mg13' ! `-mg14' ! `-mrl78' ! These are aliases for the corresponding `-mcpu=' option. They are provided for backwards compatibility. ! `-mallregs' Allow the compiler to use all of the available registers. By ! default registers `r24..r31' are reserved for use in interrupt handlers. With this option enabled these registers can be used in ordinary functions as well. ! `-m64bit-doubles' ! `-m32bit-doubles' ! Make the `double' data type be 64 bits (`-m64bit-doubles') or 32 ! bits (`-m32bit-doubles') in size. The default is ! `-m32bit-doubles'. !  File: gcc.info, Node: RS/6000 and PowerPC Options, Next: RX Options, Prev: RL78 Options, Up: Submodel Options *************** File: gcc.info, Node: RS/6000 and Power *** 18299,18388 **** 3.18.38 IBM RS/6000 and PowerPC Options --------------------------------------- ! These '-m' options are defined for the IBM RS/6000 and PowerPC: ! '-mpowerpc-gpopt' ! '-mno-powerpc-gpopt' ! '-mpowerpc-gfxopt' ! '-mno-powerpc-gfxopt' ! '-mpowerpc64' ! '-mno-powerpc64' ! '-mmfcrf' ! '-mno-mfcrf' ! '-mpopcntb' ! '-mno-popcntb' ! '-mpopcntd' ! '-mno-popcntd' ! '-mfprnd' ! '-mno-fprnd' ! '-mcmpb' ! '-mno-cmpb' ! '-mmfpgpr' ! '-mno-mfpgpr' ! '-mhard-dfp' ! '-mno-hard-dfp' You use these options to specify which instructions are available ! on the processor you are using. The default value of these options ! is determined when configuring GCC. Specifying the ! '-mcpu=CPU_TYPE' overrides the specification of these options. We ! recommend you use the '-mcpu=CPU_TYPE' option rather than the options listed above. ! Specifying '-mpowerpc-gpopt' allows GCC to use the optional PowerPC ! architecture instructions in the General Purpose group, including ! floating-point square root. Specifying '-mpowerpc-gfxopt' allows ! GCC to use the optional PowerPC architecture instructions in the ! Graphics group, including floating-point select. ! The '-mmfcrf' option allows GCC to generate the move from condition ! register field instruction implemented on the POWER4 processor and ! other processors that support the PowerPC V2.01 architecture. The ! '-mpopcntb' option allows GCC to generate the popcount and ! double-precision FP reciprocal estimate instruction implemented on ! the POWER5 processor and other processors that support the PowerPC ! V2.02 architecture. The '-mpopcntd' option allows GCC to generate ! the popcount instruction implemented on the POWER7 processor and ! other processors that support the PowerPC V2.06 architecture. The ! '-mfprnd' option allows GCC to generate the FP round to integer ! instructions implemented on the POWER5+ processor and other ! processors that support the PowerPC V2.03 architecture. The ! '-mcmpb' option allows GCC to generate the compare bytes ! instruction implemented on the POWER6 processor and other ! processors that support the PowerPC V2.05 architecture. The ! '-mmfpgpr' option allows GCC to generate the FP move to/from general-purpose register instructions implemented on the POWER6X processor and other processors that support the extended PowerPC ! V2.05 architecture. The '-mhard-dfp' option allows GCC to generate ! the decimal floating-point instructions implemented on some POWER ! processors. ! The '-mpowerpc64' option allows GCC to generate the additional 64-bit instructions that are found in the full PowerPC64 architecture and to treat GPRs as 64-bit, doubleword quantities. ! GCC defaults to '-mno-powerpc64'. ! '-mcpu=CPU_TYPE' Set architecture type, register usage, and instruction scheduling parameters for machine type CPU_TYPE. Supported values for ! CPU_TYPE are '401', '403', '405', '405fp', '440', '440fp', '464', ! '464fp', '476', '476fp', '505', '601', '602', '603', '603e', '604', ! '604e', '620', '630', '740', '7400', '7450', '750', '801', '821', ! '823', '860', '970', '8540', 'a2', 'e300c2', 'e300c3', 'e500mc', ! 'e500mc64', 'e5500', 'e6500', 'ec603e', 'G3', 'G4', 'G5', 'titan', ! 'power3', 'power4', 'power5', 'power5+', 'power6', 'power6x', ! 'power7', 'power8', 'power9', 'powerpc', 'powerpc64', ! 'powerpc64le', and 'rs64'. ! '-mcpu=powerpc', '-mcpu=powerpc64', and '-mcpu=powerpc64le' specify ! pure 32-bit PowerPC (either endian), 64-bit big endian PowerPC and ! 64-bit little endian PowerPC architecture machine types, with an ! appropriate, generic processor model assumed for scheduling ! purposes. The other options specify a specific processor. Code generated ! under those options runs best on that processor, and may not run at ! all on others. ! The '-mcpu' options automatically enable or disable the following options: -maltivec -mfprnd -mhard-float -mmfcrf -mmultiple --- 18424,18514 ---- 3.18.38 IBM RS/6000 and PowerPC Options --------------------------------------- ! These `-m' options are defined for the IBM RS/6000 and PowerPC: ! `-mpowerpc-gpopt' ! `-mno-powerpc-gpopt' ! `-mpowerpc-gfxopt' ! `-mno-powerpc-gfxopt' ! `-mpowerpc64' ! `-mno-powerpc64' ! `-mmfcrf' ! `-mno-mfcrf' ! `-mpopcntb' ! `-mno-popcntb' ! `-mpopcntd' ! `-mno-popcntd' ! `-mfprnd' ! `-mno-fprnd' ! `-mcmpb' ! `-mno-cmpb' ! `-mmfpgpr' ! `-mno-mfpgpr' ! `-mhard-dfp' ! `-mno-hard-dfp' You use these options to specify which instructions are available ! on the processor you are using. The default value of these ! options is determined when configuring GCC. Specifying the ! `-mcpu=CPU_TYPE' overrides the specification of these options. We ! recommend you use the `-mcpu=CPU_TYPE' option rather than the options listed above. ! Specifying `-mpowerpc-gpopt' allows GCC to use the optional ! PowerPC architecture instructions in the General Purpose group, ! including floating-point square root. Specifying ! `-mpowerpc-gfxopt' allows GCC to use the optional PowerPC ! architecture instructions in the Graphics group, including ! floating-point select. ! The `-mmfcrf' option allows GCC to generate the move from ! condition register field instruction implemented on the POWER4 ! processor and other processors that support the PowerPC V2.01 ! architecture. The `-mpopcntb' option allows GCC to generate the ! popcount and double-precision FP reciprocal estimate instruction ! implemented on the POWER5 processor and other processors that ! support the PowerPC V2.02 architecture. The `-mpopcntd' option ! allows GCC to generate the popcount instruction implemented on the ! POWER7 processor and other processors that support the PowerPC ! V2.06 architecture. The `-mfprnd' option allows GCC to generate ! the FP round to integer instructions implemented on the POWER5+ ! processor and other processors that support the PowerPC V2.03 ! architecture. The `-mcmpb' option allows GCC to generate the ! compare bytes instruction implemented on the POWER6 processor and ! other processors that support the PowerPC V2.05 architecture. The ! `-mmfpgpr' option allows GCC to generate the FP move to/from general-purpose register instructions implemented on the POWER6X processor and other processors that support the extended PowerPC ! V2.05 architecture. The `-mhard-dfp' option allows GCC to ! generate the decimal floating-point instructions implemented on ! some POWER processors. ! The `-mpowerpc64' option allows GCC to generate the additional 64-bit instructions that are found in the full PowerPC64 architecture and to treat GPRs as 64-bit, doubleword quantities. ! GCC defaults to `-mno-powerpc64'. ! `-mcpu=CPU_TYPE' Set architecture type, register usage, and instruction scheduling parameters for machine type CPU_TYPE. Supported values for ! CPU_TYPE are `401', `403', `405', `405fp', `440', `440fp', `464', ! `464fp', `476', `476fp', `505', `601', `602', `603', `603e', ! `604', `604e', `620', `630', `740', `7400', `7450', `750', `801', ! `821', `823', `860', `970', `8540', `a2', `e300c2', `e300c3', ! `e500mc', `e500mc64', `e5500', `e6500', `ec603e', `G3', `G4', `G5', ! `titan', `power3', `power4', `power5', `power5+', `power6', ! `power6x', `power7', `power8', `power9', `powerpc', `powerpc64', ! `powerpc64le', and `rs64'. ! `-mcpu=powerpc', `-mcpu=powerpc64', and `-mcpu=powerpc64le' ! specify pure 32-bit PowerPC (either endian), 64-bit big endian ! PowerPC and 64-bit little endian PowerPC architecture machine ! types, with an appropriate, generic processor model assumed for ! scheduling purposes. The other options specify a specific processor. Code generated ! under those options runs best on that processor, and may not run ! at all on others. ! The `-mcpu' options automatically enable or disable the following options: -maltivec -mfprnd -mhard-float -mmfcrf -mmultiple *************** These '-m' options are defined for the I *** 18390,18678 **** -mpowerpc-gpopt -mpowerpc-gfxopt -msingle-float -mdouble-float -msimple-fpu -mstring -mmulhw -mdlmzb -mmfpgpr -mvsx -mcrypto -mdirect-move -mhtm -mpower8-fusion -mpower8-vector ! -mquad-memory -mquad-memory-atomic -mmodulo -mfloat128 -mfloat128-hardware ! -mpower9-fusion -mpower9-vector -mpower9-dform The particular options set for any particular CPU varies between compiler versions, depending on what setting seems to produce optimal code for that CPU; it doesn't necessarily reflect the actual hardware's capabilities. If you wish to set an individual ! option to a particular value, you may specify it after the '-mcpu' ! option, like '-mcpu=970 -mno-altivec'. ! On AIX, the '-maltivec' and '-mpowerpc64' options are not enabled ! or disabled by the '-mcpu' option at present because AIX does not have full support for these options. You may still enable or disable them individually if you're sure it'll work in your environment. ! '-mtune=CPU_TYPE' Set the instruction scheduling parameters for machine type CPU_TYPE, but do not set the architecture type or register usage, ! as '-mcpu=CPU_TYPE' does. The same values for CPU_TYPE are used ! for '-mtune' as for '-mcpu'. If both are specified, the code ! generated uses the architecture and registers set by '-mcpu', but ! the scheduling parameters set by '-mtune'. ! '-mcmodel=small' Generate PowerPC64 code for the small model: The TOC is limited to 64k. ! '-mcmodel=medium' Generate PowerPC64 code for the medium model: The TOC and other static data may be up to a total of 4G in size. ! '-mcmodel=large' Generate PowerPC64 code for the large model: The TOC may be up to 4G in size. Other data and code is only limited by the 64-bit address space. ! '-maltivec' ! '-mno-altivec' Generate code that uses (does not use) AltiVec instructions, and also enable the use of built-in functions that allow more direct access to the AltiVec instruction set. You may also need to set ! '-mabi=altivec' to adjust the current ABI with AltiVec ABI enhancements. ! When '-maltivec' is used, rather than '-maltivec=le' or ! '-maltivec=be', the element order for AltiVec intrinsics such as ! 'vec_splat', 'vec_extract', and 'vec_insert' match array element order corresponding to the endianness of the target. That is, element zero identifies the leftmost element in a vector register when targeting a big-endian platform, and identifies the rightmost element in a vector register when targeting a little-endian platform. ! '-maltivec=be' Generate AltiVec instructions using big-endian element order, regardless of whether the target is big- or little-endian. This is the default when targeting a big-endian platform. The element order is used to interpret element numbers in AltiVec ! intrinsics such as 'vec_splat', 'vec_extract', and 'vec_insert'. By default, these match array element order corresponding to the endianness for the target. ! '-maltivec=le' Generate AltiVec instructions using little-endian element order, regardless of whether the target is big- or little-endian. This is the default when targeting a little-endian platform. This option is currently ignored when targeting a big-endian platform. The element order is used to interpret element numbers in AltiVec ! intrinsics such as 'vec_splat', 'vec_extract', and 'vec_insert'. By default, these match array element order corresponding to the endianness for the target. ! '-mvrsave' ! '-mno-vrsave' Generate VRSAVE instructions when generating AltiVec code. ! '-mgen-cell-microcode' Generate Cell microcode instructions. ! '-mwarn-cell-microcode' ! Warn when a Cell microcode instruction is emitted. An example of a ! Cell microcode instruction is a variable shift. ! '-msecure-plt' ! Generate code that allows 'ld' and 'ld.so' to build executables and ! shared libraries with non-executable '.plt' and '.got' sections. ! This is a PowerPC 32-bit SYSV ABI option. ! '-mbss-plt' ! Generate code that uses a BSS '.plt' section that 'ld.so' fills in, ! and requires '.plt' and '.got' sections that are both writable and ! executable. This is a PowerPC 32-bit SYSV ABI option. ! '-misel' ! '-mno-isel' This switch enables or disables the generation of ISEL instructions. ! '-misel=YES/NO' ! This switch has been deprecated. Use '-misel' and '-mno-isel' instead. ! '-mlra' Enable Local Register Allocation. This is still experimental for PowerPC, so by default the compiler uses standard reload (i.e. ! '-mno-lra'). ! '-mspe' ! '-mno-spe' This switch enables or disables the generation of SPE simd instructions. ! '-mpaired' ! '-mno-paired' This switch enables or disables the generation of PAIRED simd instructions. ! '-mspe=YES/NO' ! This option has been deprecated. Use '-mspe' and '-mno-spe' instead. ! '-mvsx' ! '-mno-vsx' Generate code that uses (does not use) vector/scalar (VSX) instructions, and also enable the use of built-in functions that allow more direct access to the VSX instruction set. ! '-mcrypto' ! '-mno-crypto' Enable the use (disable) of the built-in functions that allow direct access to the cryptographic instructions that were added in version 2.07 of the PowerPC ISA. ! '-mdirect-move' ! '-mno-direct-move' Generate code that uses (does not use) the instructions to move data between the general purpose registers and the vector/scalar (VSX) registers that were added in version 2.07 of the PowerPC ISA. ! '-mhtm' ! '-mno-htm' Enable (disable) the use of the built-in functions that allow direct access to the Hardware Transactional Memory (HTM) instructions that were added in version 2.07 of the PowerPC ISA. ! '-mpower8-fusion' ! '-mno-power8-fusion' Generate code that keeps (does not keeps) some integer operations adjacent so that the instructions can be fused together on power8 and later processors. ! '-mpower8-vector' ! '-mno-power8-vector' Generate code that uses (does not use) the vector and scalar instructions that were added in version 2.07 of the PowerPC ISA. Also enable the use of built-in functions that allow more direct access to the vector instructions. ! '-mquad-memory' ! '-mno-quad-memory' Generate code that uses (does not use) the non-atomic quad word ! memory instructions. The '-mquad-memory' option requires use of 64-bit mode. ! '-mquad-memory-atomic' ! '-mno-quad-memory-atomic' Generate code that uses (does not use) the atomic quad word memory ! instructions. The '-mquad-memory-atomic' option requires use of 64-bit mode. ! '-mupper-regs-df' ! '-mno-upper-regs-df' Generate code that uses (does not use) the scalar double precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.06 of the ! PowerPC ISA. '-mupper-regs-df' is turned on by default if you use ! any of the '-mcpu=power7', '-mcpu=power8', or '-mvsx' options. ! '-mupper-regs-sf' ! '-mno-upper-regs-sf' Generate code that uses (does not use) the scalar single precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the ! PowerPC ISA. '-mupper-regs-sf' is turned on by default if you use ! either of the '-mcpu=power8' or '-mpower8-vector' options. ! '-mupper-regs' ! '-mno-upper-regs' ! Generate code that uses (does not use) the scalar instructions that ! target all 64 registers in the vector/scalar floating point register set, depending on the model of the machine. ! If the '-mno-upper-regs' option is used, it turns off both ! '-mupper-regs-sf' and '-mupper-regs-df' options. ! '-mfloat128' ! '-mno-float128' Enable/disable the __FLOAT128 keyword for IEEE 128-bit floating point and use either software emulation for IEEE 128-bit floating point or hardware instructions. ! The VSX instruction set ('-mvsx', '-mcpu=power7', or ! '-mcpu=power8') must be enabled to use the '-mfloat128' option. ! The '-mfloat128' option only works on PowerPC 64-bit Linux systems. ! If you use the ISA 3.0 instruction set ('-mcpu=power9'), the ! '-mfloat128' option will also enable the generation of ISA 3.0 IEEE ! 128-bit floating point instructions. Otherwise, IEEE 128-bit floating point will be done with software emulation. ! '-mfloat128-hardware' ! '-mno-float128-hardware' Enable/disable using ISA 3.0 hardware instructions to support the __FLOAT128 data type. ! If you use '-mfloat128-hardware', it will enable the option ! '-mfloat128' as well. ! If you select ISA 3.0 instructions with '-mcpu=power9', but do not ! use either '-mfloat128' or '-mfloat128-hardware', the IEEE 128-bit floating point support will not be enabled. ! '-mmodulo' ! '-mno-modulo' ! Generate code that uses (does not use) the ISA 3.0 integer modulo ! instructions. The '-mmodulo' option is enabled by default with the ! '-mcpu=power9' option. ! ! '-mpower9-fusion' ! '-mno-power9-fusion' ! Generate code that keeps (does not keeps) some operations adjacent ! so that the instructions can be fused together on power9 and later ! processors. ! ! '-mpower9-vector' ! '-mno-power9-vector' ! Generate code that uses (does not use) the vector and scalar ! instructions that were added in version 3.0 of the PowerPC ISA. ! Also enable the use of built-in functions that allow more direct ! access to the vector instructions. ! ! '-mpower9-dform' ! '-mno-power9-dform' ! Enable (disable) scalar d-form (register + offset) memory ! instructions to load/store traditional Altivec registers. If the ! LRA register allocator is enabled, also enable (disable) vector ! d-form memory instructions. ! ! '-mfloat-gprs=YES/SINGLE/DOUBLE/NO' ! '-mfloat-gprs' This switch enables or disables the generation of floating-point operations on the general-purpose registers for architectures that support it. ! The argument 'yes' or 'single' enables the use of single-precision floating-point operations. ! The argument 'double' enables the use of single and double-precision floating-point operations. ! The argument 'no' disables floating-point operations on the general-purpose registers. This option is currently only available on the MPC854x. ! '-m32' ! '-m64' Generate code for 32-bit or 64-bit environments of Darwin and SVR4 targets (including GNU/Linux). The 32-bit environment sets int, long and pointer to 32 bits and generates code that runs on any PowerPC variant. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits, and generates code for PowerPC64, as ! for '-mpowerpc64'. ! '-mfull-toc' ! '-mno-fp-in-toc' ! '-mno-sum-in-toc' ! '-mminimal-toc' Modify generation of the TOC (Table Of Contents), which is created ! for every executable file. The '-mfull-toc' option is selected by default. In that case, GCC allocates at least one TOC entry for each unique non-automatic variable reference in your program. GCC also places floating-point constants in the TOC. However, only --- 18516,18778 ---- -mpowerpc-gpopt -mpowerpc-gfxopt -msingle-float -mdouble-float -msimple-fpu -mstring -mmulhw -mdlmzb -mmfpgpr -mvsx -mcrypto -mdirect-move -mhtm -mpower8-fusion -mpower8-vector ! -mquad-memory -mquad-memory-atomic -mfloat128 -mfloat128-hardware The particular options set for any particular CPU varies between compiler versions, depending on what setting seems to produce optimal code for that CPU; it doesn't necessarily reflect the actual hardware's capabilities. If you wish to set an individual ! option to a particular value, you may specify it after the `-mcpu' ! option, like `-mcpu=970 -mno-altivec'. ! On AIX, the `-maltivec' and `-mpowerpc64' options are not enabled ! or disabled by the `-mcpu' option at present because AIX does not have full support for these options. You may still enable or disable them individually if you're sure it'll work in your environment. ! `-mtune=CPU_TYPE' Set the instruction scheduling parameters for machine type CPU_TYPE, but do not set the architecture type or register usage, ! as `-mcpu=CPU_TYPE' does. The same values for CPU_TYPE are used ! for `-mtune' as for `-mcpu'. If both are specified, the code ! generated uses the architecture and registers set by `-mcpu', but ! the scheduling parameters set by `-mtune'. ! `-mcmodel=small' Generate PowerPC64 code for the small model: The TOC is limited to 64k. ! `-mcmodel=medium' Generate PowerPC64 code for the medium model: The TOC and other static data may be up to a total of 4G in size. ! `-mcmodel=large' Generate PowerPC64 code for the large model: The TOC may be up to 4G in size. Other data and code is only limited by the 64-bit address space. ! `-maltivec' ! `-mno-altivec' Generate code that uses (does not use) AltiVec instructions, and also enable the use of built-in functions that allow more direct access to the AltiVec instruction set. You may also need to set ! `-mabi=altivec' to adjust the current ABI with AltiVec ABI enhancements. ! When `-maltivec' is used, rather than `-maltivec=le' or ! `-maltivec=be', the element order for AltiVec intrinsics such as ! `vec_splat', `vec_extract', and `vec_insert' match array element order corresponding to the endianness of the target. That is, element zero identifies the leftmost element in a vector register when targeting a big-endian platform, and identifies the rightmost element in a vector register when targeting a little-endian platform. ! `-maltivec=be' Generate AltiVec instructions using big-endian element order, regardless of whether the target is big- or little-endian. This is the default when targeting a big-endian platform. The element order is used to interpret element numbers in AltiVec ! intrinsics such as `vec_splat', `vec_extract', and `vec_insert'. By default, these match array element order corresponding to the endianness for the target. ! `-maltivec=le' Generate AltiVec instructions using little-endian element order, regardless of whether the target is big- or little-endian. This is the default when targeting a little-endian platform. This option is currently ignored when targeting a big-endian platform. The element order is used to interpret element numbers in AltiVec ! intrinsics such as `vec_splat', `vec_extract', and `vec_insert'. By default, these match array element order corresponding to the endianness for the target. ! `-mvrsave' ! `-mno-vrsave' Generate VRSAVE instructions when generating AltiVec code. ! `-mgen-cell-microcode' Generate Cell microcode instructions. ! `-mwarn-cell-microcode' ! Warn when a Cell microcode instruction is emitted. An example of ! a Cell microcode instruction is a variable shift. ! `-msecure-plt' ! Generate code that allows `ld' and `ld.so' to build executables ! and shared libraries with non-executable `.plt' and `.got' ! sections. This is a PowerPC 32-bit SYSV ABI option. ! `-mbss-plt' ! Generate code that uses a BSS `.plt' section that `ld.so' fills ! in, and requires `.plt' and `.got' sections that are both writable ! and executable. This is a PowerPC 32-bit SYSV ABI option. ! `-misel' ! `-mno-isel' This switch enables or disables the generation of ISEL instructions. ! `-misel=YES/NO' ! This switch has been deprecated. Use `-misel' and `-mno-isel' instead. ! `-mlra' Enable Local Register Allocation. This is still experimental for PowerPC, so by default the compiler uses standard reload (i.e. ! `-mno-lra'). ! `-mspe' ! `-mno-spe' This switch enables or disables the generation of SPE simd instructions. ! `-mpaired' ! `-mno-paired' This switch enables or disables the generation of PAIRED simd instructions. ! `-mspe=YES/NO' ! This option has been deprecated. Use `-mspe' and `-mno-spe' instead. ! `-mvsx' ! `-mno-vsx' Generate code that uses (does not use) vector/scalar (VSX) instructions, and also enable the use of built-in functions that allow more direct access to the VSX instruction set. ! `-mcrypto' ! `-mno-crypto' Enable the use (disable) of the built-in functions that allow direct access to the cryptographic instructions that were added in version 2.07 of the PowerPC ISA. ! `-mdirect-move' ! `-mno-direct-move' Generate code that uses (does not use) the instructions to move data between the general purpose registers and the vector/scalar (VSX) registers that were added in version 2.07 of the PowerPC ISA. ! `-mhtm' ! `-mno-htm' Enable (disable) the use of the built-in functions that allow direct access to the Hardware Transactional Memory (HTM) instructions that were added in version 2.07 of the PowerPC ISA. ! `-mpower8-fusion' ! `-mno-power8-fusion' Generate code that keeps (does not keeps) some integer operations adjacent so that the instructions can be fused together on power8 and later processors. ! `-mpower8-vector' ! `-mno-power8-vector' Generate code that uses (does not use) the vector and scalar instructions that were added in version 2.07 of the PowerPC ISA. Also enable the use of built-in functions that allow more direct access to the vector instructions. ! `-mquad-memory' ! `-mno-quad-memory' Generate code that uses (does not use) the non-atomic quad word ! memory instructions. The `-mquad-memory' option requires use of 64-bit mode. ! `-mquad-memory-atomic' ! `-mno-quad-memory-atomic' Generate code that uses (does not use) the atomic quad word memory ! instructions. The `-mquad-memory-atomic' option requires use of 64-bit mode. ! `-mupper-regs-df' ! `-mno-upper-regs-df' Generate code that uses (does not use) the scalar double precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.06 of the ! PowerPC ISA. `-mupper-regs-df' is turned on by default if you use ! any of the `-mcpu=power7', `-mcpu=power8', or `-mvsx' options. ! `-mupper-regs-sf' ! `-mno-upper-regs-sf' Generate code that uses (does not use) the scalar single precision instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the ! PowerPC ISA. `-mupper-regs-sf' is turned on by default if you use ! either of the `-mcpu=power8', `-mpower8-vector', or `-mcpu=power9' ! options. ! `-mupper-regs' ! `-mno-upper-regs' ! Generate code that uses (does not use) the scalar instructions ! that target all 64 registers in the vector/scalar floating point register set, depending on the model of the machine. ! If the `-mno-upper-regs' option is used, it turns off both ! `-mupper-regs-sf' and `-mupper-regs-df' options. ! `-mfloat128' ! `-mno-float128' Enable/disable the __FLOAT128 keyword for IEEE 128-bit floating point and use either software emulation for IEEE 128-bit floating point or hardware instructions. ! The VSX instruction set (`-mvsx', `-mcpu=power7', or ! `-mcpu=power8') must be enabled to use the `-mfloat128' option. ! The `-mfloat128' option only works on PowerPC 64-bit Linux systems. ! If you use the ISA 3.0 instruction set (`-mcpu=power9'), the ! `-mfloat128' option will also enable the generation of ISA 3.0 ! IEEE 128-bit floating point instructions. Otherwise, IEEE 128-bit floating point will be done with software emulation. ! `-mfloat128-hardware' ! `-mno-float128-hardware' Enable/disable using ISA 3.0 hardware instructions to support the __FLOAT128 data type. ! If you use `-mfloat128-hardware', it will enable the option ! `-mfloat128' as well. ! If you select ISA 3.0 instructions with `-mcpu=power9', but do not ! use either `-mfloat128' or `-mfloat128-hardware', the IEEE 128-bit floating point support will not be enabled. ! `-mfloat-gprs=YES/SINGLE/DOUBLE/NO' ! `-mfloat-gprs' This switch enables or disables the generation of floating-point operations on the general-purpose registers for architectures that support it. ! The argument `yes' or `single' enables the use of single-precision floating-point operations. ! The argument `double' enables the use of single and double-precision floating-point operations. ! The argument `no' disables floating-point operations on the general-purpose registers. This option is currently only available on the MPC854x. ! `-m32' ! `-m64' Generate code for 32-bit or 64-bit environments of Darwin and SVR4 targets (including GNU/Linux). The 32-bit environment sets int, long and pointer to 32 bits and generates code that runs on any PowerPC variant. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits, and generates code for PowerPC64, as ! for `-mpowerpc64'. ! `-mfull-toc' ! `-mno-fp-in-toc' ! `-mno-sum-in-toc' ! `-mminimal-toc' Modify generation of the TOC (Table Of Contents), which is created ! for every executable file. The `-mfull-toc' option is selected by default. In that case, GCC allocates at least one TOC entry for each unique non-automatic variable reference in your program. GCC also places floating-point constants in the TOC. However, only *************** These '-m' options are defined for the I *** 18680,18711 **** If you receive a linker error message that saying you have overflowed the available TOC space, you can reduce the amount of ! TOC space used with the '-mno-fp-in-toc' and '-mno-sum-in-toc' ! options. '-mno-fp-in-toc' prevents GCC from putting floating-point ! constants in the TOC and '-mno-sum-in-toc' forces GCC to generate code to calculate the sum of an address and a constant at run time instead of putting that sum into the TOC. You may specify one or both of these options. Each causes GCC to produce very slightly slower and larger code at the expense of conserving TOC space. ! If you still run out of space in the TOC even when you specify both ! of these options, specify '-mminimal-toc' instead. This option ! causes GCC to make only one TOC entry for every file. When you ! specify this option, GCC produces code that is slower and larger ! but which uses extremely little TOC space. You may wish to use ! this option only on files that contain less frequently-executed ! code. ! '-maix64' ! '-maix32' Enable 64-bit AIX ABI and calling convention: 64-bit pointers, ! 64-bit 'long' type, and the infrastructure needed to support them. ! Specifying '-maix64' implies '-mpowerpc64', while '-maix32' ! disables the 64-bit ABI and implies '-mno-powerpc64'. GCC defaults ! to '-maix32'. ! '-mxl-compat' ! '-mno-xl-compat' Produce code that conforms more closely to IBM XL compiler semantics when using AIX-compatible ABI. Pass floating-point arguments to prototyped functions beyond the register save area --- 18780,18811 ---- If you receive a linker error message that saying you have overflowed the available TOC space, you can reduce the amount of ! TOC space used with the `-mno-fp-in-toc' and `-mno-sum-in-toc' ! options. `-mno-fp-in-toc' prevents GCC from putting floating-point ! constants in the TOC and `-mno-sum-in-toc' forces GCC to generate code to calculate the sum of an address and a constant at run time instead of putting that sum into the TOC. You may specify one or both of these options. Each causes GCC to produce very slightly slower and larger code at the expense of conserving TOC space. ! If you still run out of space in the TOC even when you specify ! both of these options, specify `-mminimal-toc' instead. This ! option causes GCC to make only one TOC entry for every file. When ! you specify this option, GCC produces code that is slower and ! larger but which uses extremely little TOC space. You may wish to ! use this option only on files that contain less ! frequently-executed code. ! `-maix64' ! `-maix32' Enable 64-bit AIX ABI and calling convention: 64-bit pointers, ! 64-bit `long' type, and the infrastructure needed to support them. ! Specifying `-maix64' implies `-mpowerpc64', while `-maix32' ! disables the 64-bit ABI and implies `-mno-powerpc64'. GCC ! defaults to `-maix32'. ! `-mxl-compat' ! `-mno-xl-compat' Produce code that conforms more closely to IBM XL compiler semantics when using AIX-compatible ABI. Pass floating-point arguments to prototyped functions beyond the register save area *************** These '-m' options are defined for the I *** 18717,19150 **** The AIX calling convention was extended but not initially documented to handle an obscure K&R C case of calling a function that takes the address of its arguments with fewer arguments than ! declared. IBM XL compilers access floating-point arguments that do ! not fit in the RSA from the stack when a subroutine is compiled without optimization. Because always storing floating-point arguments on the stack is inefficient and rarely needed, this ! option is not enabled by default and only is necessary when calling ! subroutines compiled by IBM XL compilers without optimization. ! '-mpe' Support "IBM RS/6000 SP" "Parallel Environment" (PE). Link an application written to use message passing with special startup code to enable the application to run. The system must have PE ! installed in the standard location ('/usr/lpp/ppe.poe/'), or the ! 'specs' file must be overridden with the '-specs=' option to specify the appropriate directory location. The Parallel ! Environment does not support threads, so the '-mpe' option and the ! '-pthread' option are incompatible. ! '-malign-natural' ! '-malign-power' On AIX, 32-bit Darwin, and 64-bit PowerPC GNU/Linux, the option ! '-malign-natural' overrides the ABI-defined alignment of larger types, such as floating-point doubles, on their natural size-based ! boundary. The option '-malign-power' instructs GCC to follow the ABI-specified alignment rules. GCC defaults to the standard alignment defined in the ABI. On 64-bit Darwin, natural alignment is the default, and ! '-malign-power' is not supported. ! '-msoft-float' ! '-mhard-float' Generate code that does not use (uses) the floating-point register set. Software floating-point emulation is provided if you use the ! '-msoft-float' option, and pass the option to GCC when linking. ! '-msingle-float' ! '-mdouble-float' Generate code for single- or double-precision floating-point ! operations. '-mdouble-float' implies '-msingle-float'. ! '-msimple-fpu' ! Do not generate 'sqrt' and 'div' instructions for hardware floating-point unit. ! '-mfpu=NAME' Specify type of floating-point unit. Valid values for NAME are ! 'sp_lite' (equivalent to '-msingle-float -msimple-fpu'), 'dp_lite' ! (equivalent to '-mdouble-float -msimple-fpu'), 'sp_full' ! (equivalent to '-msingle-float'), and 'dp_full' (equivalent to ! '-mdouble-float'). ! '-mxilinx-fpu' Perform optimizations for the floating-point unit on Xilinx PPC 405/440. ! '-mmultiple' ! '-mno-multiple' Generate code that uses (does not use) the load multiple word instructions and the store multiple word instructions. These instructions are generated by default on POWER systems, and not ! generated on PowerPC systems. Do not use '-mmultiple' on ! little-endian PowerPC systems, since those instructions do not work ! when the processor is in little-endian mode. The exceptions are ! PPC740 and PPC750 which permit these instructions in little-endian ! mode. ! '-mstring' ! '-mno-string' Generate code that uses (does not use) the load string instructions and the store string word instructions to save multiple registers and do small block moves. These instructions are generated by ! default on POWER systems, and not generated on PowerPC systems. Do ! not use '-mstring' on little-endian PowerPC systems, since those instructions do not work when the processor is in little-endian mode. The exceptions are PPC740 and PPC750 which permit these instructions in little-endian mode. ! '-mupdate' ! '-mno-update' Generate code that uses (does not use) the load or store instructions that update the base register to the address of the calculated memory location. These instructions are generated by ! default. If you use '-mno-update', there is a small window between ! the time that the stack pointer is updated and the address of the ! previous frame is stored, which means code that walks the stack ! frame across interrupts or signals may get corrupted data. ! '-mavoid-indexed-addresses' ! '-mno-avoid-indexed-addresses' Generate code that tries to avoid (not avoid) the use of indexed ! load or store instructions. These instructions can incur a performance penalty on Power6 processors in certain situations, such as when stepping through large arrays that cross a 16M boundary. This option is enabled by default when targeting Power6 and disabled otherwise. ! '-mfused-madd' ! '-mno-fused-madd' Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. The machine-dependent ! '-mfused-madd' option is now mapped to the machine-independent ! '-ffp-contract=fast' option, and '-mno-fused-madd' is mapped to ! '-ffp-contract=off'. ! '-mmulhw' ! '-mno-mulhw' Generate code that uses (does not use) the half-word multiply and multiply-accumulate instructions on the IBM 405, 440, 464 and 476 processors. These instructions are generated by default when targeting those processors. ! '-mdlmzb' ! '-mno-dlmzb' ! Generate code that uses (does not use) the string-search 'dlmzb' instruction on the IBM 405, 440, 464 and 476 processors. This instruction is generated by default when targeting those processors. ! '-mno-bit-align' ! '-mbit-align' On System V.4 and embedded PowerPC systems do not (do) force structures and unions that contain bit-fields to be aligned to the base type of the bit-field. For example, by default a structure containing nothing but 8 ! 'unsigned' bit-fields of length 1 is aligned to a 4-byte boundary ! and has a size of 4 bytes. By using '-mno-bit-align', the structure is aligned to a 1-byte boundary and is 1 byte in size. ! '-mno-strict-align' ! '-mstrict-align' On System V.4 and embedded PowerPC systems do not (do) assume that unaligned memory references are handled by the system. ! '-mrelocatable' ! '-mno-relocatable' Generate code that allows (does not allow) a static executable to be relocated to a different address at run time. A simple embedded PowerPC system loader should relocate the entire contents of ! '.got2' and 4-byte locations listed in the '.fixup' section, a table of 32-bit addresses generated by this option. For this to work, all objects linked together must be compiled with ! '-mrelocatable' or '-mrelocatable-lib'. '-mrelocatable' code aligns the stack to an 8-byte boundary. ! '-mrelocatable-lib' ! '-mno-relocatable-lib' ! Like '-mrelocatable', '-mrelocatable-lib' generates a '.fixup' section to allow static executables to be relocated at run time, ! but '-mrelocatable-lib' does not use the smaller stack alignment of ! '-mrelocatable'. Objects compiled with '-mrelocatable-lib' may be ! linked with objects compiled with any combination of the ! '-mrelocatable' options. ! '-mno-toc' ! '-mtoc' On System V.4 and embedded PowerPC systems do not (do) assume that register 2 contains a pointer to a global area pointing to the addresses used in the program. ! '-mlittle' ! '-mlittle-endian' On System V.4 and embedded PowerPC systems compile code for the ! processor in little-endian mode. The '-mlittle-endian' option is ! the same as '-mlittle'. ! '-mbig' ! '-mbig-endian' On System V.4 and embedded PowerPC systems compile code for the ! processor in big-endian mode. The '-mbig-endian' option is the ! same as '-mbig'. ! '-mdynamic-no-pic' On Darwin and Mac OS X systems, compile code so that it is not relocatable, but that its external references are relocatable. The resulting code is suitable for applications, but not shared libraries. ! '-msingle-pic-base' Treat the register used for PIC addressing as read-only, rather than loading it in the prologue for each function. The runtime system is responsible for initializing this register with an appropriate value before execution begins. ! '-mprioritize-restricted-insns=PRIORITY' ! This option controls the priority that is assigned to dispatch-slot ! restricted instructions during the second scheduling pass. The ! argument PRIORITY takes the value '0', '1', or '2' to assign no, ! highest, or second-highest (respectively) priority to dispatch-slot ! restricted instructions. ! '-msched-costly-dep=DEPENDENCE_TYPE' ! This option controls which dependences are considered costly by the ! target during instruction scheduling. The argument DEPENDENCE_TYPE ! takes one of the following values: ! 'no' No dependence is costly. ! 'all' All dependences are costly. ! 'true_store_to_load' A true dependence from store to load is costly. ! 'store_to_load' Any dependence from store to load is costly. ! NUMBER Any dependence for which the latency is greater than or equal to NUMBER is costly. ! '-minsert-sched-nops=SCHEME' This option controls which NOP insertion scheme is used during the second scheduling pass. The argument SCHEME takes one of the following values: ! 'no' Don't insert NOPs. ! 'pad' Pad with NOPs any dispatch group that has vacant issue slots, according to the scheduler's grouping. ! 'regroup_exact' Insert NOPs to force costly dependent insns into separate groups. Insert exactly as many NOPs as needed to force an insn to a new group, according to the estimated processor grouping. ! NUMBER Insert NOPs to force costly dependent insns into separate groups. Insert NUMBER NOPs to force an insn to a new group. ! '-mcall-sysv' On System V.4 and embedded PowerPC systems compile code using calling conventions that adhere to the March 1995 draft of the System V Application Binary Interface, PowerPC processor supplement. This is the default unless you configured GCC using ! 'powerpc-*-eabiaix'. ! '-mcall-sysv-eabi' ! '-mcall-eabi' ! Specify both '-mcall-sysv' and '-meabi' options. ! '-mcall-sysv-noeabi' ! Specify both '-mcall-sysv' and '-mno-eabi' options. ! '-mcall-aixdesc' On System V.4 and embedded PowerPC systems compile code for the AIX operating system. ! '-mcall-linux' On System V.4 and embedded PowerPC systems compile code for the Linux-based GNU system. ! '-mcall-freebsd' On System V.4 and embedded PowerPC systems compile code for the FreeBSD operating system. ! '-mcall-netbsd' On System V.4 and embedded PowerPC systems compile code for the NetBSD operating system. ! '-mcall-openbsd' On System V.4 and embedded PowerPC systems compile code for the OpenBSD operating system. ! '-maix-struct-return' Return all structures in memory (as specified by the AIX ABI). ! '-msvr4-struct-return' Return structures smaller than 8 bytes in registers (as specified by the SVR4 ABI). ! '-mabi=ABI-TYPE' Extend the current ABI with a particular extension, or remove such ! extension. Valid values are 'altivec', 'no-altivec', 'spe', ! 'no-spe', 'ibmlongdouble', 'ieeelongdouble', 'elfv1', 'elfv2'. ! '-mabi=spe' Extend the current ABI with SPE ABI extensions. This does not change the default ABI, instead it adds the SPE ABI extensions to the current ABI. ! '-mabi=no-spe' Disable Book-E SPE ABI extensions for the current ABI. ! '-mabi=ibmlongdouble' Change the current ABI to use IBM extended-precision long double. This is a PowerPC 32-bit SYSV ABI option. ! '-mabi=ieeelongdouble' Change the current ABI to use IEEE extended-precision long double. This is a PowerPC 32-bit Linux ABI option. ! '-mabi=elfv1' ! Change the current ABI to use the ELFv1 ABI. This is the default ABI for big-endian PowerPC 64-bit Linux. Overriding the default ABI requires special system support and is likely to fail in spectacular ways. ! '-mabi=elfv2' ! Change the current ABI to use the ELFv2 ABI. This is the default ! ABI for little-endian PowerPC 64-bit Linux. Overriding the default ! ABI requires special system support and is likely to fail in ! spectacular ways. ! '-mprototype' ! '-mno-prototype' On System V.4 and embedded PowerPC systems assume that all calls to variable argument functions are properly prototyped. Otherwise, ! the compiler must insert an instruction before every non-prototyped ! call to set or clear bit 6 of the condition code register ('CR') to ! indicate whether floating-point values are passed in the ! floating-point registers in case the function takes variable ! arguments. With '-mprototype', only calls to prototyped variable ! argument functions set or clear the bit. ! '-msim' On embedded PowerPC systems, assume that the startup module is ! called 'sim-crt0.o' and that the standard C libraries are ! 'libsim.a' and 'libc.a'. This is the default for ! 'powerpc-*-eabisim' configurations. ! '-mmvme' On embedded PowerPC systems, assume that the startup module is ! called 'crt0.o' and the standard C libraries are 'libmvme.a' and ! 'libc.a'. ! '-mads' On embedded PowerPC systems, assume that the startup module is ! called 'crt0.o' and the standard C libraries are 'libads.a' and ! 'libc.a'. ! '-myellowknife' On embedded PowerPC systems, assume that the startup module is ! called 'crt0.o' and the standard C libraries are 'libyk.a' and ! 'libc.a'. ! '-mvxworks' On System V.4 and embedded PowerPC systems, specify that you are compiling for a VxWorks system. ! '-memb' ! On embedded PowerPC systems, set the 'PPC_EMB' bit in the ELF flags ! header to indicate that 'eabi' extended relocations are used. ! '-meabi' ! '-mno-eabi' On System V.4 and embedded PowerPC systems do (do not) adhere to the Embedded Applications Binary Interface (EABI), which is a set of modifications to the System V.4 specifications. Selecting ! '-meabi' means that the stack is aligned to an 8-byte boundary, a ! function '__eabi' is called from 'main' to set up the EABI ! environment, and the '-msdata' option can use both 'r2' and 'r13' ! to point to two separate small data areas. Selecting '-mno-eabi' means that the stack is aligned to a 16-byte boundary, no EABI ! initialization function is called from 'main', and the '-msdata' ! option only uses 'r13' to point to a single small data area. The ! '-meabi' option is on by default if you configured GCC using one of ! the 'powerpc*-*-eabi*' options. ! '-msdata=eabi' On System V.4 and embedded PowerPC systems, put small initialized ! 'const' global and static data in the '.sdata2' section, which is ! pointed to by register 'r2'. Put small initialized non-'const' ! global and static data in the '.sdata' section, which is pointed to ! by register 'r13'. Put small uninitialized global and static data ! in the '.sbss' section, which is adjacent to the '.sdata' section. ! The '-msdata=eabi' option is incompatible with the '-mrelocatable' ! option. The '-msdata=eabi' option also sets the '-memb' option. ! '-msdata=sysv' On System V.4 and embedded PowerPC systems, put small global and ! static data in the '.sdata' section, which is pointed to by ! register 'r13'. Put small uninitialized global and static data in ! the '.sbss' section, which is adjacent to the '.sdata' section. ! The '-msdata=sysv' option is incompatible with the '-mrelocatable' option. ! '-msdata=default' ! '-msdata' ! On System V.4 and embedded PowerPC systems, if '-meabi' is used, ! compile code the same as '-msdata=eabi', otherwise compile code the ! same as '-msdata=sysv'. ! '-msdata=data' On System V.4 and embedded PowerPC systems, put small global data ! in the '.sdata' section. Put small uninitialized global data in ! the '.sbss' section. Do not use register 'r13' to address small ! data however. This is the default behavior unless other '-msdata' options are used. ! '-msdata=none' ! '-mno-sdata' On embedded PowerPC systems, put all initialized global and static ! data in the '.data' section, and all uninitialized data in the ! '.bss' section. ! '-mblock-move-inline-limit=NUM' ! Inline all block moves (such as calls to 'memcpy' or structure ! copies) less than or equal to NUM bytes. The minimum value for NUM ! is 32 bytes on 32-bit targets and 64 bytes on 64-bit targets. The ! default value is target-specific. ! '-G NUM' On embedded PowerPC systems, put global and static items less than or equal to NUM bytes into the small data or BSS sections instead ! of the normal data or BSS section. By default, NUM is 8. The '-G NUM' switch is also passed to the linker. All modules should be ! compiled with the same '-G NUM' value. ! '-mregnames' ! '-mno-regnames' On System V.4 and embedded PowerPC systems do (do not) emit register names in the assembly language output using symbolic forms. ! '-mlongcall' ! '-mno-longcall' By default assume that all calls are far away so that a longer and more expensive calling sequence is required. This is required for ! calls farther than 32 megabytes (33,554,432 bytes) from the current ! location. A short call is generated if the compiler knows the call ! cannot be that far away. This setting can be overridden by the ! 'shortcall' function attribute, or by '#pragma longcall(0)'. Some linkers are capable of detecting out-of-range calls and generating glue code on the fly. On these systems, long calls are --- 18817,19252 ---- The AIX calling convention was extended but not initially documented to handle an obscure K&R C case of calling a function that takes the address of its arguments with fewer arguments than ! declared. IBM XL compilers access floating-point arguments that ! do not fit in the RSA from the stack when a subroutine is compiled without optimization. Because always storing floating-point arguments on the stack is inefficient and rarely needed, this ! option is not enabled by default and only is necessary when ! calling subroutines compiled by IBM XL compilers without ! optimization. ! `-mpe' Support "IBM RS/6000 SP" "Parallel Environment" (PE). Link an application written to use message passing with special startup code to enable the application to run. The system must have PE ! installed in the standard location (`/usr/lpp/ppe.poe/'), or the ! `specs' file must be overridden with the `-specs=' option to specify the appropriate directory location. The Parallel ! Environment does not support threads, so the `-mpe' option and the ! `-pthread' option are incompatible. ! `-malign-natural' ! `-malign-power' On AIX, 32-bit Darwin, and 64-bit PowerPC GNU/Linux, the option ! `-malign-natural' overrides the ABI-defined alignment of larger types, such as floating-point doubles, on their natural size-based ! boundary. The option `-malign-power' instructs GCC to follow the ABI-specified alignment rules. GCC defaults to the standard alignment defined in the ABI. On 64-bit Darwin, natural alignment is the default, and ! `-malign-power' is not supported. ! `-msoft-float' ! `-mhard-float' Generate code that does not use (uses) the floating-point register set. Software floating-point emulation is provided if you use the ! `-msoft-float' option, and pass the option to GCC when linking. ! `-msingle-float' ! `-mdouble-float' Generate code for single- or double-precision floating-point ! operations. `-mdouble-float' implies `-msingle-float'. ! `-msimple-fpu' ! Do not generate `sqrt' and `div' instructions for hardware floating-point unit. ! `-mfpu=NAME' Specify type of floating-point unit. Valid values for NAME are ! `sp_lite' (equivalent to `-msingle-float -msimple-fpu'), `dp_lite' ! (equivalent to `-mdouble-float -msimple-fpu'), `sp_full' ! (equivalent to `-msingle-float'), and `dp_full' (equivalent to ! `-mdouble-float'). ! `-mxilinx-fpu' Perform optimizations for the floating-point unit on Xilinx PPC 405/440. ! `-mmultiple' ! `-mno-multiple' Generate code that uses (does not use) the load multiple word instructions and the store multiple word instructions. These instructions are generated by default on POWER systems, and not ! generated on PowerPC systems. Do not use `-mmultiple' on ! little-endian PowerPC systems, since those instructions do not ! work when the processor is in little-endian mode. The exceptions ! are PPC740 and PPC750 which permit these instructions in ! little-endian mode. ! `-mstring' ! `-mno-string' Generate code that uses (does not use) the load string instructions and the store string word instructions to save multiple registers and do small block moves. These instructions are generated by ! default on POWER systems, and not generated on PowerPC systems. ! Do not use `-mstring' on little-endian PowerPC systems, since those instructions do not work when the processor is in little-endian mode. The exceptions are PPC740 and PPC750 which permit these instructions in little-endian mode. ! `-mupdate' ! `-mno-update' Generate code that uses (does not use) the load or store instructions that update the base register to the address of the calculated memory location. These instructions are generated by ! default. If you use `-mno-update', there is a small window ! between the time that the stack pointer is updated and the address ! of the previous frame is stored, which means code that walks the ! stack frame across interrupts or signals may get corrupted data. ! `-mavoid-indexed-addresses' ! `-mno-avoid-indexed-addresses' Generate code that tries to avoid (not avoid) the use of indexed ! load or store instructions. These instructions can incur a performance penalty on Power6 processors in certain situations, such as when stepping through large arrays that cross a 16M boundary. This option is enabled by default when targeting Power6 and disabled otherwise. ! `-mfused-madd' ! `-mno-fused-madd' Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. The machine-dependent ! `-mfused-madd' option is now mapped to the machine-independent ! `-ffp-contract=fast' option, and `-mno-fused-madd' is mapped to ! `-ffp-contract=off'. ! `-mmulhw' ! `-mno-mulhw' Generate code that uses (does not use) the half-word multiply and multiply-accumulate instructions on the IBM 405, 440, 464 and 476 processors. These instructions are generated by default when targeting those processors. ! `-mdlmzb' ! `-mno-dlmzb' ! Generate code that uses (does not use) the string-search `dlmzb' instruction on the IBM 405, 440, 464 and 476 processors. This instruction is generated by default when targeting those processors. ! `-mno-bit-align' ! `-mbit-align' On System V.4 and embedded PowerPC systems do not (do) force structures and unions that contain bit-fields to be aligned to the base type of the bit-field. For example, by default a structure containing nothing but 8 ! `unsigned' bit-fields of length 1 is aligned to a 4-byte boundary ! and has a size of 4 bytes. By using `-mno-bit-align', the structure is aligned to a 1-byte boundary and is 1 byte in size. ! `-mno-strict-align' ! `-mstrict-align' On System V.4 and embedded PowerPC systems do not (do) assume that unaligned memory references are handled by the system. ! `-mrelocatable' ! `-mno-relocatable' Generate code that allows (does not allow) a static executable to be relocated to a different address at run time. A simple embedded PowerPC system loader should relocate the entire contents of ! `.got2' and 4-byte locations listed in the `.fixup' section, a table of 32-bit addresses generated by this option. For this to work, all objects linked together must be compiled with ! `-mrelocatable' or `-mrelocatable-lib'. `-mrelocatable' code aligns the stack to an 8-byte boundary. ! `-mrelocatable-lib' ! `-mno-relocatable-lib' ! Like `-mrelocatable', `-mrelocatable-lib' generates a `.fixup' section to allow static executables to be relocated at run time, ! but `-mrelocatable-lib' does not use the smaller stack alignment ! of `-mrelocatable'. Objects compiled with `-mrelocatable-lib' may ! be linked with objects compiled with any combination of the ! `-mrelocatable' options. ! `-mno-toc' ! `-mtoc' On System V.4 and embedded PowerPC systems do not (do) assume that register 2 contains a pointer to a global area pointing to the addresses used in the program. ! `-mlittle' ! `-mlittle-endian' On System V.4 and embedded PowerPC systems compile code for the ! processor in little-endian mode. The `-mlittle-endian' option is ! the same as `-mlittle'. ! `-mbig' ! `-mbig-endian' On System V.4 and embedded PowerPC systems compile code for the ! processor in big-endian mode. The `-mbig-endian' option is the ! same as `-mbig'. ! `-mdynamic-no-pic' On Darwin and Mac OS X systems, compile code so that it is not relocatable, but that its external references are relocatable. The resulting code is suitable for applications, but not shared libraries. ! `-msingle-pic-base' Treat the register used for PIC addressing as read-only, rather than loading it in the prologue for each function. The runtime system is responsible for initializing this register with an appropriate value before execution begins. ! `-mprioritize-restricted-insns=PRIORITY' ! This option controls the priority that is assigned to ! dispatch-slot restricted instructions during the second scheduling ! pass. The argument PRIORITY takes the value `0', `1', or `2' to ! assign no, highest, or second-highest (respectively) priority to ! dispatch-slot restricted instructions. ! `-msched-costly-dep=DEPENDENCE_TYPE' ! This option controls which dependences are considered costly by ! the target during instruction scheduling. The argument ! DEPENDENCE_TYPE takes one of the following values: ! `no' No dependence is costly. ! `all' All dependences are costly. ! `true_store_to_load' A true dependence from store to load is costly. ! `store_to_load' Any dependence from store to load is costly. ! NUMBER Any dependence for which the latency is greater than or equal to NUMBER is costly. ! `-minsert-sched-nops=SCHEME' This option controls which NOP insertion scheme is used during the second scheduling pass. The argument SCHEME takes one of the following values: ! `no' Don't insert NOPs. ! `pad' Pad with NOPs any dispatch group that has vacant issue slots, according to the scheduler's grouping. ! `regroup_exact' Insert NOPs to force costly dependent insns into separate groups. Insert exactly as many NOPs as needed to force an insn to a new group, according to the estimated processor grouping. ! NUMBER Insert NOPs to force costly dependent insns into separate groups. Insert NUMBER NOPs to force an insn to a new group. ! `-mcall-sysv' On System V.4 and embedded PowerPC systems compile code using calling conventions that adhere to the March 1995 draft of the System V Application Binary Interface, PowerPC processor supplement. This is the default unless you configured GCC using ! `powerpc-*-eabiaix'. ! `-mcall-sysv-eabi' ! `-mcall-eabi' ! Specify both `-mcall-sysv' and `-meabi' options. ! `-mcall-sysv-noeabi' ! Specify both `-mcall-sysv' and `-mno-eabi' options. ! `-mcall-aixdesc' On System V.4 and embedded PowerPC systems compile code for the AIX operating system. ! `-mcall-linux' On System V.4 and embedded PowerPC systems compile code for the Linux-based GNU system. ! `-mcall-freebsd' On System V.4 and embedded PowerPC systems compile code for the FreeBSD operating system. ! `-mcall-netbsd' On System V.4 and embedded PowerPC systems compile code for the NetBSD operating system. ! `-mcall-openbsd' On System V.4 and embedded PowerPC systems compile code for the OpenBSD operating system. ! `-maix-struct-return' Return all structures in memory (as specified by the AIX ABI). ! `-msvr4-struct-return' Return structures smaller than 8 bytes in registers (as specified by the SVR4 ABI). ! `-mabi=ABI-TYPE' Extend the current ABI with a particular extension, or remove such ! extension. Valid values are `altivec', `no-altivec', `spe', ! `no-spe', `ibmlongdouble', `ieeelongdouble', `elfv1', `elfv2'. ! `-mabi=spe' Extend the current ABI with SPE ABI extensions. This does not change the default ABI, instead it adds the SPE ABI extensions to the current ABI. ! `-mabi=no-spe' Disable Book-E SPE ABI extensions for the current ABI. ! `-mabi=ibmlongdouble' Change the current ABI to use IBM extended-precision long double. This is a PowerPC 32-bit SYSV ABI option. ! `-mabi=ieeelongdouble' Change the current ABI to use IEEE extended-precision long double. This is a PowerPC 32-bit Linux ABI option. ! `-mabi=elfv1' ! Change the current ABI to use the ELFv1 ABI. This is the default ABI for big-endian PowerPC 64-bit Linux. Overriding the default ABI requires special system support and is likely to fail in spectacular ways. ! `-mabi=elfv2' ! Change the current ABI to use the ELFv2 ABI. This is the default ! ABI for little-endian PowerPC 64-bit Linux. Overriding the ! default ABI requires special system support and is likely to fail ! in spectacular ways. ! `-mprototype' ! `-mno-prototype' On System V.4 and embedded PowerPC systems assume that all calls to variable argument functions are properly prototyped. Otherwise, ! the compiler must insert an instruction before every ! non-prototyped call to set or clear bit 6 of the condition code ! register (`CR') to indicate whether floating-point values are ! passed in the floating-point registers in case the function takes ! variable arguments. With `-mprototype', only calls to prototyped ! variable argument functions set or clear the bit. ! `-msim' On embedded PowerPC systems, assume that the startup module is ! called `sim-crt0.o' and that the standard C libraries are ! `libsim.a' and `libc.a'. This is the default for ! `powerpc-*-eabisim' configurations. ! `-mmvme' On embedded PowerPC systems, assume that the startup module is ! called `crt0.o' and the standard C libraries are `libmvme.a' and ! `libc.a'. ! `-mads' On embedded PowerPC systems, assume that the startup module is ! called `crt0.o' and the standard C libraries are `libads.a' and ! `libc.a'. ! `-myellowknife' On embedded PowerPC systems, assume that the startup module is ! called `crt0.o' and the standard C libraries are `libyk.a' and ! `libc.a'. ! `-mvxworks' On System V.4 and embedded PowerPC systems, specify that you are compiling for a VxWorks system. ! `-memb' ! On embedded PowerPC systems, set the `PPC_EMB' bit in the ELF flags ! header to indicate that `eabi' extended relocations are used. ! `-meabi' ! `-mno-eabi' On System V.4 and embedded PowerPC systems do (do not) adhere to the Embedded Applications Binary Interface (EABI), which is a set of modifications to the System V.4 specifications. Selecting ! `-meabi' means that the stack is aligned to an 8-byte boundary, a ! function `__eabi' is called from `main' to set up the EABI ! environment, and the `-msdata' option can use both `r2' and `r13' ! to point to two separate small data areas. Selecting `-mno-eabi' means that the stack is aligned to a 16-byte boundary, no EABI ! initialization function is called from `main', and the `-msdata' ! option only uses `r13' to point to a single small data area. The ! `-meabi' option is on by default if you configured GCC using one ! of the `powerpc*-*-eabi*' options. ! `-msdata=eabi' On System V.4 and embedded PowerPC systems, put small initialized ! `const' global and static data in the `.sdata2' section, which is ! pointed to by register `r2'. Put small initialized non-`const' ! global and static data in the `.sdata' section, which is pointed ! to by register `r13'. Put small uninitialized global and static ! data in the `.sbss' section, which is adjacent to the `.sdata' ! section. The `-msdata=eabi' option is incompatible with the ! `-mrelocatable' option. The `-msdata=eabi' option also sets the ! `-memb' option. ! `-msdata=sysv' On System V.4 and embedded PowerPC systems, put small global and ! static data in the `.sdata' section, which is pointed to by ! register `r13'. Put small uninitialized global and static data in ! the `.sbss' section, which is adjacent to the `.sdata' section. ! The `-msdata=sysv' option is incompatible with the `-mrelocatable' option. ! `-msdata=default' ! `-msdata' ! On System V.4 and embedded PowerPC systems, if `-meabi' is used, ! compile code the same as `-msdata=eabi', otherwise compile code the ! same as `-msdata=sysv'. ! `-msdata=data' On System V.4 and embedded PowerPC systems, put small global data ! in the `.sdata' section. Put small uninitialized global data in ! the `.sbss' section. Do not use register `r13' to address small ! data however. This is the default behavior unless other `-msdata' options are used. ! `-msdata=none' ! `-mno-sdata' On embedded PowerPC systems, put all initialized global and static ! data in the `.data' section, and all uninitialized data in the ! `.bss' section. ! `-mblock-move-inline-limit=NUM' ! Inline all block moves (such as calls to `memcpy' or structure ! copies) less than or equal to NUM bytes. The minimum value for ! NUM is 32 bytes on 32-bit targets and 64 bytes on 64-bit targets. ! The default value is target-specific. ! `-G NUM' On embedded PowerPC systems, put global and static items less than or equal to NUM bytes into the small data or BSS sections instead ! of the normal data or BSS section. By default, NUM is 8. The `-G NUM' switch is also passed to the linker. All modules should be ! compiled with the same `-G NUM' value. ! `-mregnames' ! `-mno-regnames' On System V.4 and embedded PowerPC systems do (do not) emit register names in the assembly language output using symbolic forms. ! `-mlongcall' ! `-mno-longcall' By default assume that all calls are far away so that a longer and more expensive calling sequence is required. This is required for ! calls farther than 32 megabytes (33,554,432 bytes) from the ! current location. A short call is generated if the compiler knows ! the call cannot be that far away. This setting can be overridden ! by the `shortcall' function attribute, or by `#pragma longcall(0)'. Some linkers are capable of detecting out-of-range calls and generating glue code on the fly. On these systems, long calls are *************** These '-m' options are defined for the I *** 19153,19166 **** planned to add this feature to the GNU linker for 32-bit PowerPC systems as well. ! On Darwin/PPC systems, '#pragma longcall' generates 'jbsr callee, ! L42', plus a "branch island" (glue code). The two target addresses ! represent the callee and the branch island. The Darwin/PPC linker ! prefers the first address and generates a 'bl callee' if the PPC ! 'bl' instruction reaches the callee directly; otherwise, the linker ! generates 'bl L42' to call the branch island. The branch island is ! appended to the body of the calling function; it computes the full ! 32-bit address of the callee and jumps to it. On Mach-O (Darwin) systems, this option directs the compiler emit to the glue for every direct call, and the Darwin linker decides --- 19255,19269 ---- planned to add this feature to the GNU linker for 32-bit PowerPC systems as well. ! On Darwin/PPC systems, `#pragma longcall' generates `jbsr callee, ! L42', plus a "branch island" (glue code). The two target ! addresses represent the callee and the branch island. The ! Darwin/PPC linker prefers the first address and generates a `bl ! callee' if the PPC `bl' instruction reaches the callee directly; ! otherwise, the linker generates `bl L42' to call the branch ! island. The branch island is appended to the body of the calling ! function; it computes the full 32-bit address of the callee and ! jumps to it. On Mach-O (Darwin) systems, this option directs the compiler emit to the glue for every direct call, and the Darwin linker decides *************** These '-m' options are defined for the I *** 19169,19302 **** In the future, GCC may ignore all longcall specifications when the linker is known to generate glue. ! '-mtls-markers' ! '-mno-tls-markers' ! Mark (do not mark) calls to '__tls_get_addr' with a relocation ! specifying the function argument. The relocation allows the linker ! to reliably associate function call with argument setup instructions for TLS optimization, which in turn allows GCC to better schedule the sequence. ! '-pthread' Adds support for multithreading with the "pthreads" library. This option sets flags for both the preprocessor and linker. ! '-mrecip' ! '-mno-recip' This option enables use of the reciprocal estimate and reciprocal square root estimate instructions with additional Newton-Raphson steps to increase precision instead of doing a divide or square root and divide for floating-point arguments. You should use the ! '-ffast-math' option when using '-mrecip' (or at least ! '-funsafe-math-optimizations', '-ffinite-math-only', ! '-freciprocal-math' and '-fno-trapping-math'). Note that while the ! throughput of the sequence is generally higher than the throughput ! of the non-reciprocal instruction, the precision of the sequence ! can be decreased by up to 2 ulp (i.e. the inverse of 1.0 equals ! 0.99999994) for reciprocal square roots. ! '-mrecip=OPT' This option controls which reciprocal estimate instructions may be used. OPT is a comma-separated list of options, which may be ! preceded by a '!' to invert the option: ! 'all' Enable all estimate instructions. ! 'default' ! Enable the default instructions, equivalent to '-mrecip'. ! 'none' ! Disable all estimate instructions, equivalent to '-mno-recip'. ! 'div' Enable the reciprocal approximation instructions for both single and double precision. ! 'divf' Enable the single-precision reciprocal approximation instructions. ! 'divd' Enable the double-precision reciprocal approximation instructions. ! 'rsqrt' Enable the reciprocal square root approximation instructions for both single and double precision. ! 'rsqrtf' Enable the single-precision reciprocal square root approximation instructions. ! 'rsqrtd' Enable the double-precision reciprocal square root approximation instructions. ! So, for example, '-mrecip=all,!rsqrtd' enables all of the ! reciprocal estimate instructions, except for the 'FRSQRTE', ! 'XSRSQRTEDP', and 'XVRSQRTEDP' instructions which handle the double-precision reciprocal square root calculations. ! '-mrecip-precision' ! '-mno-recip-precision' Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ! ABI. Selecting '-mcpu=power6', '-mcpu=power7' or '-mcpu=power8' ! automatically selects '-mrecip-precision'. The double-precision square root estimate instructions are not generated by default on low-precision machines, since they do not provide an estimate that converges after three steps. ! '-mveclibabi=TYPE' Specifies the ABI type to use for vectorizing intrinsics using an ! external library. The only type supported at present is 'mass', which specifies to use IBM's Mathematical Acceleration Subsystem (MASS) libraries for vectorizing intrinsics using external ! libraries. GCC currently emits calls to 'acosd2', 'acosf4', ! 'acoshd2', 'acoshf4', 'asind2', 'asinf4', 'asinhd2', 'asinhf4', ! 'atan2d2', 'atan2f4', 'atand2', 'atanf4', 'atanhd2', 'atanhf4', ! 'cbrtd2', 'cbrtf4', 'cosd2', 'cosf4', 'coshd2', 'coshf4', 'erfcd2', ! 'erfcf4', 'erfd2', 'erff4', 'exp2d2', 'exp2f4', 'expd2', 'expf4', ! 'expm1d2', 'expm1f4', 'hypotd2', 'hypotf4', 'lgammad2', 'lgammaf4', ! 'log10d2', 'log10f4', 'log1pd2', 'log1pf4', 'log2d2', 'log2f4', ! 'logd2', 'logf4', 'powd2', 'powf4', 'sind2', 'sinf4', 'sinhd2', ! 'sinhf4', 'sqrtd2', 'sqrtf4', 'tand2', 'tanf4', 'tanhd2', and ! 'tanhf4' when generating code for power7. Both '-ftree-vectorize' ! and '-funsafe-math-optimizations' must also be enabled. The MASS ! libraries must be specified at link time. ! '-mfriz' ! '-mno-friz' ! Generate (do not generate) the 'friz' instruction when the ! '-funsafe-math-optimizations' option is used to optimize rounding of floating-point values to 64-bit integer and back to floating ! point. The 'friz' instruction does not return the same value if the floating-point number is too large to fit in an integer. ! '-mpointers-to-nested-functions' ! '-mno-pointers-to-nested-functions' Generate (do not generate) code to load up the static chain ! register ('r11') when calling through a pointer on AIX and 64-bit Linux systems where a function pointer points to a 3-word descriptor giving the function address, TOC value to be loaded in ! register 'r2', and static chain value to be loaded in register ! 'r11'. The '-mpointers-to-nested-functions' is on by default. You ! cannot call through pointers to nested functions or pointers to ! functions compiled in other languages that use the static chain if ! you use '-mno-pointers-to-nested-functions'. ! '-msave-toc-indirect' ! '-mno-save-toc-indirect' Generate (do not generate) code to save the TOC value in the reserved stack location in the function prologue if the function calls through a pointer on AIX and 64-bit Linux systems. If the ! TOC value is not saved in the prologue, it is saved just before the ! call through the pointer. The '-mno-save-toc-indirect' option is ! the default. ! '-mcompat-align-parm' ! '-mno-compat-align-parm' Generate (do not generate) code to pass structure parameters with a maximum alignment of 64 bits, for compatibility with older versions of GCC. --- 19272,19406 ---- In the future, GCC may ignore all longcall specifications when the linker is known to generate glue. ! `-mtls-markers' ! `-mno-tls-markers' ! Mark (do not mark) calls to `__tls_get_addr' with a relocation ! specifying the function argument. The relocation allows the ! linker to reliably associate function call with argument setup instructions for TLS optimization, which in turn allows GCC to better schedule the sequence. ! `-pthread' Adds support for multithreading with the "pthreads" library. This option sets flags for both the preprocessor and linker. ! `-mrecip' ! `-mno-recip' This option enables use of the reciprocal estimate and reciprocal square root estimate instructions with additional Newton-Raphson steps to increase precision instead of doing a divide or square root and divide for floating-point arguments. You should use the ! `-ffast-math' option when using `-mrecip' (or at least ! `-funsafe-math-optimizations', `-ffinite-math-only', ! `-freciprocal-math' and `-fno-trapping-math'). Note that while ! the throughput of the sequence is generally higher than the ! throughput of the non-reciprocal instruction, the precision of the ! sequence can be decreased by up to 2 ulp (i.e. the inverse of 1.0 ! equals 0.99999994) for reciprocal square roots. ! `-mrecip=OPT' This option controls which reciprocal estimate instructions may be used. OPT is a comma-separated list of options, which may be ! preceded by a `!' to invert the option: ! `all' Enable all estimate instructions. ! `default' ! Enable the default instructions, equivalent to `-mrecip'. ! `none' ! Disable all estimate instructions, equivalent to `-mno-recip'. ! `div' Enable the reciprocal approximation instructions for both single and double precision. ! `divf' Enable the single-precision reciprocal approximation instructions. ! `divd' Enable the double-precision reciprocal approximation instructions. ! `rsqrt' Enable the reciprocal square root approximation instructions for both single and double precision. ! `rsqrtf' Enable the single-precision reciprocal square root approximation instructions. ! `rsqrtd' Enable the double-precision reciprocal square root approximation instructions. ! ! So, for example, `-mrecip=all,!rsqrtd' enables all of the ! reciprocal estimate instructions, except for the `FRSQRTE', ! `XSRSQRTEDP', and `XVRSQRTEDP' instructions which handle the double-precision reciprocal square root calculations. ! `-mrecip-precision' ! `-mno-recip-precision' Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ! ABI. Selecting `-mcpu=power6', `-mcpu=power7' or `-mcpu=power8' ! automatically selects `-mrecip-precision'. The double-precision square root estimate instructions are not generated by default on low-precision machines, since they do not provide an estimate that converges after three steps. ! `-mveclibabi=TYPE' Specifies the ABI type to use for vectorizing intrinsics using an ! external library. The only type supported at present is `mass', which specifies to use IBM's Mathematical Acceleration Subsystem (MASS) libraries for vectorizing intrinsics using external ! libraries. GCC currently emits calls to `acosd2', `acosf4', ! `acoshd2', `acoshf4', `asind2', `asinf4', `asinhd2', `asinhf4', ! `atan2d2', `atan2f4', `atand2', `atanf4', `atanhd2', `atanhf4', ! `cbrtd2', `cbrtf4', `cosd2', `cosf4', `coshd2', `coshf4', ! `erfcd2', `erfcf4', `erfd2', `erff4', `exp2d2', `exp2f4', `expd2', ! `expf4', `expm1d2', `expm1f4', `hypotd2', `hypotf4', `lgammad2', ! `lgammaf4', `log10d2', `log10f4', `log1pd2', `log1pf4', `log2d2', ! `log2f4', `logd2', `logf4', `powd2', `powf4', `sind2', `sinf4', ! `sinhd2', `sinhf4', `sqrtd2', `sqrtf4', `tand2', `tanf4', ! `tanhd2', and `tanhf4' when generating code for power7. Both ! `-ftree-vectorize' and `-funsafe-math-optimizations' must also be ! enabled. The MASS libraries must be specified at link time. ! `-mfriz' ! `-mno-friz' ! Generate (do not generate) the `friz' instruction when the ! `-funsafe-math-optimizations' option is used to optimize rounding of floating-point values to 64-bit integer and back to floating ! point. The `friz' instruction does not return the same value if the floating-point number is too large to fit in an integer. ! `-mpointers-to-nested-functions' ! `-mno-pointers-to-nested-functions' Generate (do not generate) code to load up the static chain ! register (`r11') when calling through a pointer on AIX and 64-bit Linux systems where a function pointer points to a 3-word descriptor giving the function address, TOC value to be loaded in ! register `r2', and static chain value to be loaded in register ! `r11'. The `-mpointers-to-nested-functions' is on by default. ! You cannot call through pointers to nested functions or pointers ! to functions compiled in other languages that use the static chain ! if you use `-mno-pointers-to-nested-functions'. ! `-msave-toc-indirect' ! `-mno-save-toc-indirect' Generate (do not generate) code to save the TOC value in the reserved stack location in the function prologue if the function calls through a pointer on AIX and 64-bit Linux systems. If the ! TOC value is not saved in the prologue, it is saved just before ! the call through the pointer. The `-mno-save-toc-indirect' option ! is the default. ! `-mcompat-align-parm' ! `-mno-compat-align-parm' Generate (do not generate) code to pass structure parameters with a maximum alignment of 64 bits, for compatibility with older versions of GCC. *************** These '-m' options are defined for the I *** 19304,19314 **** Older versions of GCC (prior to 4.9.0) incorrectly did not align a structure parameter on a 128-bit boundary when that structure contained a member requiring 128-bit alignment. This is corrected ! in more recent versions of GCC. This option may be used to generate ! code that is compatible with functions compiled with older versions ! of GCC. ! The '-mno-compat-align-parm' option is the default.  File: gcc.info, Node: RX Options, Next: S/390 and zSeries Options, Prev: RS/6000 and PowerPC Options, Up: Submodel Options --- 19408,19418 ---- Older versions of GCC (prior to 4.9.0) incorrectly did not align a structure parameter on a 128-bit boundary when that structure contained a member requiring 128-bit alignment. This is corrected ! in more recent versions of GCC. This option may be used to ! generate code that is compatible with functions compiled with ! older versions of GCC. ! The `-mno-compat-align-parm' option is the default.  File: gcc.info, Node: RX Options, Next: S/390 and zSeries Options, Prev: RS/6000 and PowerPC Options, Up: Submodel Options *************** File: gcc.info, Node: RX Options, Next *** 19318,19368 **** These command-line options are defined for RX targets: ! '-m64bit-doubles' ! '-m32bit-doubles' ! Make the 'double' data type be 64 bits ('-m64bit-doubles') or 32 ! bits ('-m32bit-doubles') in size. The default is ! '-m32bit-doubles'. _Note_ RX floating-point hardware only works on ! 32-bit values, which is why the default is '-m32bit-doubles'. ! '-fpu' ! '-nofpu' ! Enables ('-fpu') or disables ('-nofpu') the use of RX floating-point hardware. The default is enabled for the RX600 series and disabled for the RX200 series. Floating-point instructions are only generated for 32-bit ! floating-point values, however, so the FPU hardware is not used for ! doubles if the '-m64bit-doubles' option is used. ! _Note_ If the '-fpu' option is enabled then ! '-funsafe-math-optimizations' is also enabled automatically. This is because the RX FPU instructions are themselves unsafe. ! '-mcpu=NAME' Selects the type of RX CPU to be targeted. Currently three types ! are supported, the generic 'RX600' and 'RX200' series hardware and ! the specific 'RX610' CPU. The default is 'RX600'. ! The only difference between 'RX600' and 'RX610' is that the 'RX610' ! does not support the 'MVTIPL' instruction. ! The 'RX200' series does not have a hardware floating-point unit and ! so '-nofpu' is enabled by default when this type is selected. ! '-mbig-endian-data' ! '-mlittle-endian-data' Store data (but not code) in the big-endian format. The default is ! '-mlittle-endian-data', i.e. to store data in the little-endian format. ! '-msmall-data-limit=N' Specifies the maximum size in bytes of global and static variables which can be placed into the small data area. Using the small data area can lead to smaller and faster code, but the size of area is limited and it is up to the programmer to ensure that the area does not overflow. Also when the small data area is used one of the ! RX's registers (usually 'r13') is reserved for use pointing to this area, so it is no longer available for use by the compiler. This could result in slower and/or larger code if variables are pushed onto the stack instead of being held in this register. --- 19422,19472 ---- These command-line options are defined for RX targets: ! `-m64bit-doubles' ! `-m32bit-doubles' ! Make the `double' data type be 64 bits (`-m64bit-doubles') or 32 ! bits (`-m32bit-doubles') in size. The default is ! `-m32bit-doubles'. _Note_ RX floating-point hardware only works ! on 32-bit values, which is why the default is `-m32bit-doubles'. ! `-fpu' ! `-nofpu' ! Enables (`-fpu') or disables (`-nofpu') the use of RX floating-point hardware. The default is enabled for the RX600 series and disabled for the RX200 series. Floating-point instructions are only generated for 32-bit ! floating-point values, however, so the FPU hardware is not used ! for doubles if the `-m64bit-doubles' option is used. ! _Note_ If the `-fpu' option is enabled then ! `-funsafe-math-optimizations' is also enabled automatically. This is because the RX FPU instructions are themselves unsafe. ! `-mcpu=NAME' Selects the type of RX CPU to be targeted. Currently three types ! are supported, the generic `RX600' and `RX200' series hardware and ! the specific `RX610' CPU. The default is `RX600'. ! The only difference between `RX600' and `RX610' is that the ! `RX610' does not support the `MVTIPL' instruction. ! The `RX200' series does not have a hardware floating-point unit ! and so `-nofpu' is enabled by default when this type is selected. ! `-mbig-endian-data' ! `-mlittle-endian-data' Store data (but not code) in the big-endian format. The default is ! `-mlittle-endian-data', i.e. to store data in the little-endian format. ! `-msmall-data-limit=N' Specifies the maximum size in bytes of global and static variables which can be placed into the small data area. Using the small data area can lead to smaller and faster code, but the size of area is limited and it is up to the programmer to ensure that the area does not overflow. Also when the small data area is used one of the ! RX's registers (usually `r13') is reserved for use pointing to this area, so it is no longer available for use by the compiler. This could result in slower and/or larger code if variables are pushed onto the stack instead of being held in this register. *************** These command-line options are defined f *** 19373,19397 **** The default value is zero, which disables this feature. Note, this feature is not enabled by default with higher optimization levels ! ('-O2' etc) because of the potentially detrimental effects of reserving a register. It is up to the programmer to experiment and discover whether this feature is of benefit to their program. See ! the description of the '-mpid' option for a description of how the actual register to hold the small data area pointer is chosen. ! '-msim' ! '-mno-sim' Use the simulator runtime. The default is to use the libgloss board-specific runtime. ! '-mas100-syntax' ! '-mno-as100-syntax' When generating assembler output use a syntax that is compatible ! with Renesas's AS100 assembler. This syntax can also be handled by ! the GAS assembler, but it has some restrictions so it is not generated by default. ! '-mmax-constant-size=N' Specifies the maximum size, in bytes, of a constant that can be used as an operand in a RX instruction. Although the RX instruction set does allow constants of up to 4 bytes in length to --- 19477,19501 ---- The default value is zero, which disables this feature. Note, this feature is not enabled by default with higher optimization levels ! (`-O2' etc) because of the potentially detrimental effects of reserving a register. It is up to the programmer to experiment and discover whether this feature is of benefit to their program. See ! the description of the `-mpid' option for a description of how the actual register to hold the small data area pointer is chosen. ! `-msim' ! `-mno-sim' Use the simulator runtime. The default is to use the libgloss board-specific runtime. ! `-mas100-syntax' ! `-mno-as100-syntax' When generating assembler output use a syntax that is compatible ! with Renesas's AS100 assembler. This syntax can also be handled ! by the GAS assembler, but it has some restrictions so it is not generated by default. ! `-mmax-constant-size=N' Specifies the maximum size, in bytes, of a constant that can be used as an operand in a RX instruction. Although the RX instruction set does allow constants of up to 4 bytes in length to *************** These command-line options are defined f *** 19404,19432 **** The value N can be between 0 and 4. A value of 0 (the default) or 4 means that constants of any size are allowed. ! '-mrelax' Enable linker relaxation. Linker relaxation is a process whereby the linker attempts to reduce the size of a program by finding shorter versions of various instructions. Disabled by default. ! '-mint-register=N' Specify the number of registers to reserve for fast interrupt ! handler functions. The value N can be between 0 and 4. A value of ! 1 means that register 'r13' is reserved for the exclusive use of ! fast interrupt handlers. A value of 2 reserves 'r13' and 'r12'. A ! value of 3 reserves 'r13', 'r12' and 'r11', and a value of 4 ! reserves 'r13' through 'r10'. A value of 0, the default, does not ! reserve any registers. ! '-msave-acc-in-interrupts' Specifies that interrupt handler functions should preserve the accumulator register. This is only necessary if normal code might use the accumulator register, for example because it performs 64-bit multiplications. The default is to ignore the accumulator as this makes the interrupt handlers faster. ! '-mpid' ! '-mno-pid' Enables the generation of position independent data. When enabled any access to constant data is done via an offset from a base address held in a register. This allows the location of constant --- 19508,19536 ---- The value N can be between 0 and 4. A value of 0 (the default) or 4 means that constants of any size are allowed. ! `-mrelax' Enable linker relaxation. Linker relaxation is a process whereby the linker attempts to reduce the size of a program by finding shorter versions of various instructions. Disabled by default. ! `-mint-register=N' Specify the number of registers to reserve for fast interrupt ! handler functions. The value N can be between 0 and 4. A value ! of 1 means that register `r13' is reserved for the exclusive use ! of fast interrupt handlers. A value of 2 reserves `r13' and ! `r12'. A value of 3 reserves `r13', `r12' and `r11', and a value ! of 4 reserves `r13' through `r10'. A value of 0, the default, ! does not reserve any registers. ! `-msave-acc-in-interrupts' Specifies that interrupt handler functions should preserve the accumulator register. This is only necessary if normal code might use the accumulator register, for example because it performs 64-bit multiplications. The default is to ignore the accumulator as this makes the interrupt handlers faster. ! `-mpid' ! `-mno-pid' Enables the generation of position independent data. When enabled any access to constant data is done via an offset from a base address held in a register. This allows the location of constant *************** These command-line options are defined f *** 19435,19496 **** tight memory constraints. Data that can be modified is not affected by this option. ! Note, using this feature reserves a register, usually 'r13', for the constant data base address. This can result in slower and/or larger code, especially in complicated functions. The actual register chosen to hold the constant data base address ! depends upon whether the '-msmall-data-limit' and/or the ! '-mint-register' command-line options are enabled. Starting with ! register 'r13' and proceeding downwards, registers are allocated ! first to satisfy the requirements of '-mint-register', then '-mpid' ! and finally '-msmall-data-limit'. Thus it is possible for the ! small data area register to be 'r8' if both '-mint-register=4' and ! '-mpid' are specified on the command line. By default this feature is not enabled. The default can be ! restored via the '-mno-pid' command-line option. ! '-mno-warn-multiple-fast-interrupts' ! '-mwarn-multiple-fast-interrupts' Prevents GCC from issuing a warning message if it finds more than one fast interrupt handler when it is compiling a file. The ! default is to issue a warning for each extra fast interrupt handler ! found, as the RX only supports one such interrupt. ! '-mallow-string-insns' ! '-mno-allow-string-insns' Enables or disables the use of the string manipulation instructions ! 'SMOVF', 'SCMPU', 'SMOVB', 'SMOVU', 'SUNTIL' 'SWHILE' and also the ! 'RMPA' instruction. These instructions may prefetch data, which is ! not safe to do if accessing an I/O register. (See section 12.2.7 ! of the RX62N Group User's Manual for more information). The default is to allow these instructions, but it is not possible for GCC to reliably detect all circumstances where a string instruction might be used to access an I/O register, so their use cannot be disabled automatically. Instead it is reliant upon the ! programmer to use the '-mno-allow-string-insns' option if their program accesses I/O space. When the instructions are enabled GCC defines the C preprocessor ! symbol '__RX_ALLOW_STRING_INSNS__', otherwise it defines the symbol ! '__RX_DISALLOW_STRING_INSNS__'. ! '-mjsr' ! '-mno-jsr' ! Use only (or not only) 'JSR' instructions to access functions. ! This option can be used when code size exceeds the range of 'BSR' ! instructions. Note that '-mno-jsr' does not mean to not use 'JSR' but instead means that any type of branch may be used. ! _Note:_ The generic GCC command-line option '-ffixed-REG' has special ! significance to the RX port when used with the 'interrupt' function ! attribute. This attribute indicates a function intended to process fast ! interrupts. GCC ensures that it only uses the registers 'r10', 'r11', ! 'r12' and/or 'r13' and only provided that the normal use of the ! corresponding registers have been restricted via the '-ffixed-REG' or ! '-mint-register' command-line options.  File: gcc.info, Node: S/390 and zSeries Options, Next: Score Options, Prev: RX Options, Up: Submodel Options --- 19539,19600 ---- tight memory constraints. Data that can be modified is not affected by this option. ! Note, using this feature reserves a register, usually `r13', for the constant data base address. This can result in slower and/or larger code, especially in complicated functions. The actual register chosen to hold the constant data base address ! depends upon whether the `-msmall-data-limit' and/or the ! `-mint-register' command-line options are enabled. Starting with ! register `r13' and proceeding downwards, registers are allocated ! first to satisfy the requirements of `-mint-register', then ! `-mpid' and finally `-msmall-data-limit'. Thus it is possible for ! the small data area register to be `r8' if both `-mint-register=4' ! and `-mpid' are specified on the command line. By default this feature is not enabled. The default can be ! restored via the `-mno-pid' command-line option. ! `-mno-warn-multiple-fast-interrupts' ! `-mwarn-multiple-fast-interrupts' Prevents GCC from issuing a warning message if it finds more than one fast interrupt handler when it is compiling a file. The ! default is to issue a warning for each extra fast interrupt ! handler found, as the RX only supports one such interrupt. ! `-mallow-string-insns' ! `-mno-allow-string-insns' Enables or disables the use of the string manipulation instructions ! `SMOVF', `SCMPU', `SMOVB', `SMOVU', `SUNTIL' `SWHILE' and also the ! `RMPA' instruction. These instructions may prefetch data, which ! is not safe to do if accessing an I/O register. (See section ! 12.2.7 of the RX62N Group User's Manual for more information). The default is to allow these instructions, but it is not possible for GCC to reliably detect all circumstances where a string instruction might be used to access an I/O register, so their use cannot be disabled automatically. Instead it is reliant upon the ! programmer to use the `-mno-allow-string-insns' option if their program accesses I/O space. When the instructions are enabled GCC defines the C preprocessor ! symbol `__RX_ALLOW_STRING_INSNS__', otherwise it defines the ! symbol `__RX_DISALLOW_STRING_INSNS__'. ! `-mjsr' ! `-mno-jsr' ! Use only (or not only) `JSR' instructions to access functions. ! This option can be used when code size exceeds the range of `BSR' ! instructions. Note that `-mno-jsr' does not mean to not use `JSR' but instead means that any type of branch may be used. ! _Note:_ The generic GCC command-line option `-ffixed-REG' has special ! significance to the RX port when used with the `interrupt' function ! attribute. This attribute indicates a function intended to process ! fast interrupts. GCC ensures that it only uses the registers `r10', ! `r11', `r12' and/or `r13' and only provided that the normal use of the ! corresponding registers have been restricted via the `-ffixed-REG' or ! `-mint-register' command-line options.  File: gcc.info, Node: S/390 and zSeries Options, Next: Score Options, Prev: RX Options, Up: Submodel Options *************** File: gcc.info, Node: S/390 and zSeries *** 19498,19711 **** 3.18.40 S/390 and zSeries Options --------------------------------- ! These are the '-m' options defined for the S/390 and zSeries architecture. ! '-mhard-float' ! '-msoft-float' Use (do not use) the hardware floating-point instructions and ! registers for floating-point operations. When '-msoft-float' is ! specified, functions in 'libgcc.a' are used to perform ! floating-point operations. When '-mhard-float' is specified, the compiler generates IEEE floating-point instructions. This is the default. ! '-mhard-dfp' ! '-mno-hard-dfp' Use (do not use) the hardware decimal-floating-point instructions ! for decimal-floating-point operations. When '-mno-hard-dfp' is ! specified, functions in 'libgcc.a' are used to perform ! decimal-floating-point operations. When '-mhard-dfp' is specified, ! the compiler generates decimal-floating-point hardware ! instructions. This is the default for '-march=z9-ec' or higher. ! '-mlong-double-64' ! '-mlong-double-128' ! These switches control the size of 'long double' type. A size of ! 64 bits makes the 'long double' type equivalent to the 'double' ! type. This is the default. ! '-mbackchain' ! '-mno-backchain' ! Store (do not store) the address of the caller's frame as backchain ! pointer into the callee's stack frame. A backchain may be needed ! to allow debugging using tools that do not understand DWARF call ! frame information. When '-mno-packed-stack' is in effect, the ! backchain pointer is stored at the bottom of the stack frame; when ! '-mpacked-stack' is in effect, the backchain is placed into the ! topmost word of the 96/160 byte register save area. ! In general, code compiled with '-mbackchain' is call-compatible ! with code compiled with '-mmo-backchain'; however, use of the backchain for debugging purposes usually requires that the whole ! binary is built with '-mbackchain'. Note that the combination of ! '-mbackchain', '-mpacked-stack' and '-mhard-float' is not ! supported. In order to build a linux kernel use '-msoft-float'. The default is to not maintain the backchain. ! '-mpacked-stack' ! '-mno-packed-stack' ! Use (do not use) the packed stack layout. When '-mno-packed-stack' ! is specified, the compiler uses the all fields of the 96/160 byte ! register save area only for their default purpose; unused fields ! still take up stack space. When '-mpacked-stack' is specified, ! register save slots are densely packed at the top of the register ! save area; unused space is reused for other purposes, allowing for ! more efficient use of the available stack space. However, when ! '-mbackchain' is also in effect, the topmost word of the save area ! is always used to store the backchain, and the return address ! register is always saved two words below the backchain. As long as the stack frame backchain is not used, code generated ! with '-mpacked-stack' is call-compatible with code generated with ! '-mno-packed-stack'. Note that some non-FSF releases of GCC 2.95 for S/390 or zSeries generated code that uses the stack frame backchain at run time, not just for debugging purposes. Such code ! is not call-compatible with code compiled with '-mpacked-stack'. ! Also, note that the combination of '-mbackchain', '-mpacked-stack' ! and '-mhard-float' is not supported. In order to build a linux ! kernel use '-msoft-float'. The default is to not use the packed stack layout. ! '-msmall-exec' ! '-mno-small-exec' ! Generate (or do not generate) code using the 'bras' instruction to do subroutine calls. This only works reliably if the total executable size does not exceed 64k. The default is to use the ! 'basr' instruction instead, which does not have this limitation. ! '-m64' ! '-m31' ! When '-m31' is specified, generate code compliant to the GNU/Linux ! for S/390 ABI. When '-m64' is specified, generate code compliant ! to the GNU/Linux for zSeries ABI. This allows GCC in particular to ! generate 64-bit instructions. For the 's390' targets, the default ! is '-m31', while the 's390x' targets default to '-m64'. ! '-mzarch' ! '-mesa' ! When '-mzarch' is specified, generate code using the instructions ! available on z/Architecture. When '-mesa' is specified, generate code using the instructions available on ESA/390. Note that ! '-mesa' is not possible with '-m64'. When generating code ! compliant to the GNU/Linux for S/390 ABI, the default is '-mesa'. When generating code compliant to the GNU/Linux for zSeries ABI, ! the default is '-mzarch'. ! '-mhtm' ! '-mno-htm' ! The '-mhtm' option enables a set of builtins making use of instructions available with the transactional execution facility introduced with the IBM zEnterprise EC12 machine generation *note ! S/390 System z Built-in Functions::. '-mhtm' is enabled by default ! when using '-march=zEC12'. ! '-mvx' ! '-mno-vx' ! When '-mvx' is specified, generate code using the instructions available with the vector extension facility introduced with the IBM z13 machine generation. This option changes the ABI for some vector type values with regard to alignment and calling conventions. In case vector type values are being used in an ! ABI-relevant context a GAS '.gnu_attribute' command will be added ! to mark the resulting binary with the ABI used. '-mvx' is enabled ! by default when using '-march=z13'. ! '-mzvector' ! '-mno-zvector' ! The '-mzvector' option enables vector language extensions and builtins using instructions available with the vector extension facility introduced with the IBM z13 machine generation. This ! option adds support for 'vector' to be used as a keyword to define ! vector type variables and arguments. 'vector' is only available when GNU extensions are enabled. It will not be expanded when ! requesting strict standard compliance e.g. with '-std=c99'. In ! addition to the GCC low-level builtins '-mzvector' enables a set of ! builtins added for compatibility with AltiVec-style implementations ! like Power and Cell. In order to make use of these builtins the ! header file 'vecintrin.h' needs to be included. '-mzvector' is ! disabled by default. ! '-mmvcle' ! '-mno-mvcle' ! Generate (or do not generate) code using the 'mvcle' instruction to ! perform block moves. When '-mno-mvcle' is specified, use a 'mvc' ! loop instead. This is the default unless optimizing for size. ! '-mdebug' ! '-mno-debug' Print (or do not print) additional debug information when compiling. The default is to not print debug information. ! '-march=CPU-TYPE' Generate code that runs on CPU-TYPE, which is the name of a system representing a certain processor type. Possible values for ! CPU-TYPE are 'z900', 'z990', 'z9-109', 'z9-ec', 'z10', 'z196', ! 'zEC12', and 'z13'. The default is '-march=z900'. 'g5' and 'g6' are deprecated and will be removed with future releases. ! '-mtune=CPU-TYPE' Tune to CPU-TYPE everything applicable about the generated code, ! except for the ABI and the set of available instructions. The list ! of CPU-TYPE values is the same as for '-march'. The default is the ! value used for '-march'. ! '-mtpf-trace' ! '-mno-tpf-trace' Generate code that adds (does not add) in TPF OS specific branches to trace routines in the operating system. This option is off by default, even when compiling for the TPF OS. ! '-mfused-madd' ! '-mno-fused-madd' Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. ! '-mwarn-framesize=FRAMESIZE' Emit a warning if the current function exceeds the given frame ! size. Because this is a compile-time check it doesn't need to be a ! real problem when the program runs. It is intended to identify functions that most probably cause a stack overflow. It is useful ! to be used in an environment with limited stack size e.g. the linux ! kernel. ! '-mwarn-dynamicstack' ! Emit a warning if the function calls 'alloca' or uses dynamically-sized arrays. This is generally a bad idea with a limited stack size. ! '-mstack-guard=STACK-GUARD' ! '-mstack-size=STACK-SIZE' If these options are provided the S/390 back end emits additional instructions in the function prologue that trigger a trap if the ! stack size is STACK-GUARD bytes above the STACK-SIZE (remember that ! the stack on S/390 grows downward). If the STACK-GUARD option is ! omitted the smallest power of 2 larger than the frame size of the ! compiled function is chosen. These options are intended to be used ! to help debugging stack overflow problems. The additionally ! emitted code causes only little overhead and hence can also be used ! in production-like systems without greater performance degradation. ! The given values have to be exact powers of 2 and STACK-SIZE has to ! be greater than STACK-GUARD without exceeding 64k. In order to be ! efficient the extra code makes the assumption that the stack starts ! at an address aligned to the value given by STACK-SIZE. The ! STACK-GUARD option can only be used in conjunction with STACK-SIZE. ! '-mhotpatch=PRE-HALFWORDS,POST-HALFWORDS' If the hotpatch option is enabled, a "hot-patching" function prologue is generated for all functions in the compilation unit. The funtion label is prepended with the given number of two-byte NOP instructions (PRE-HALFWORDS, maximum 1000000). After the ! label, 2 * POST-HALFWORDS bytes are appended, using the largest NOP ! like instructions the architecture allows (maximum 1000000). If both arguments are zero, hotpatching is disabled. This option can be overridden for individual functions with the ! 'hotpatch' attribute.  File: gcc.info, Node: Score Options, Next: SH Options, Prev: S/390 and zSeries Options, Up: Submodel Options --- 19602,19818 ---- 3.18.40 S/390 and zSeries Options --------------------------------- ! These are the `-m' options defined for the S/390 and zSeries architecture. ! `-mhard-float' ! `-msoft-float' Use (do not use) the hardware floating-point instructions and ! registers for floating-point operations. When `-msoft-float' is ! specified, functions in `libgcc.a' are used to perform ! floating-point operations. When `-mhard-float' is specified, the compiler generates IEEE floating-point instructions. This is the default. ! `-mhard-dfp' ! `-mno-hard-dfp' Use (do not use) the hardware decimal-floating-point instructions ! for decimal-floating-point operations. When `-mno-hard-dfp' is ! specified, functions in `libgcc.a' are used to perform ! decimal-floating-point operations. When `-mhard-dfp' is ! specified, the compiler generates decimal-floating-point hardware ! instructions. This is the default for `-march=z9-ec' or higher. ! `-mlong-double-64' ! `-mlong-double-128' ! These switches control the size of `long double' type. A size of ! 64 bits makes the `long double' type equivalent to the `double' ! type. This is the default. ! `-mbackchain' ! `-mno-backchain' ! Store (do not store) the address of the caller's frame as ! backchain pointer into the callee's stack frame. A backchain may ! be needed to allow debugging using tools that do not understand ! DWARF call frame information. When `-mno-packed-stack' is in ! effect, the backchain pointer is stored at the bottom of the stack ! frame; when `-mpacked-stack' is in effect, the backchain is placed ! into the topmost word of the 96/160 byte register save area. ! In general, code compiled with `-mbackchain' is call-compatible ! with code compiled with `-mmo-backchain'; however, use of the backchain for debugging purposes usually requires that the whole ! binary is built with `-mbackchain'. Note that the combination of ! `-mbackchain', `-mpacked-stack' and `-mhard-float' is not ! supported. In order to build a linux kernel use `-msoft-float'. The default is to not maintain the backchain. ! `-mpacked-stack' ! `-mno-packed-stack' ! Use (do not use) the packed stack layout. When ! `-mno-packed-stack' is specified, the compiler uses the all fields ! of the 96/160 byte register save area only for their default ! purpose; unused fields still take up stack space. When ! `-mpacked-stack' is specified, register save slots are densely ! packed at the top of the register save area; unused space is ! reused for other purposes, allowing for more efficient use of the ! available stack space. However, when `-mbackchain' is also in ! effect, the topmost word of the save area is always used to store ! the backchain, and the return address register is always saved two ! words below the backchain. As long as the stack frame backchain is not used, code generated ! with `-mpacked-stack' is call-compatible with code generated with ! `-mno-packed-stack'. Note that some non-FSF releases of GCC 2.95 for S/390 or zSeries generated code that uses the stack frame backchain at run time, not just for debugging purposes. Such code ! is not call-compatible with code compiled with `-mpacked-stack'. ! Also, note that the combination of `-mbackchain', `-mpacked-stack' ! and `-mhard-float' is not supported. In order to build a linux ! kernel use `-msoft-float'. The default is to not use the packed stack layout. ! `-msmall-exec' ! `-mno-small-exec' ! Generate (or do not generate) code using the `bras' instruction to do subroutine calls. This only works reliably if the total executable size does not exceed 64k. The default is to use the ! `basr' instruction instead, which does not have this limitation. ! `-m64' ! `-m31' ! When `-m31' is specified, generate code compliant to the GNU/Linux ! for S/390 ABI. When `-m64' is specified, generate code compliant ! to the GNU/Linux for zSeries ABI. This allows GCC in particular ! to generate 64-bit instructions. For the `s390' targets, the ! default is `-m31', while the `s390x' targets default to `-m64'. ! `-mzarch' ! `-mesa' ! When `-mzarch' is specified, generate code using the instructions ! available on z/Architecture. When `-mesa' is specified, generate code using the instructions available on ESA/390. Note that ! `-mesa' is not possible with `-m64'. When generating code ! compliant to the GNU/Linux for S/390 ABI, the default is `-mesa'. When generating code compliant to the GNU/Linux for zSeries ABI, ! the default is `-mzarch'. ! `-mhtm' ! `-mno-htm' ! The `-mhtm' option enables a set of builtins making use of instructions available with the transactional execution facility introduced with the IBM zEnterprise EC12 machine generation *note ! S/390 System z Built-in Functions::. `-mhtm' is enabled by ! default when using `-march=zEC12'. ! `-mvx' ! `-mno-vx' ! When `-mvx' is specified, generate code using the instructions available with the vector extension facility introduced with the IBM z13 machine generation. This option changes the ABI for some vector type values with regard to alignment and calling conventions. In case vector type values are being used in an ! ABI-relevant context a GAS `.gnu_attribute' command will be added ! to mark the resulting binary with the ABI used. `-mvx' is enabled ! by default when using `-march=z13'. ! `-mzvector' ! `-mno-zvector' ! The `-mzvector' option enables vector language extensions and builtins using instructions available with the vector extension facility introduced with the IBM z13 machine generation. This ! option adds support for `vector' to be used as a keyword to define ! vector type variables and arguments. `vector' is only available when GNU extensions are enabled. It will not be expanded when ! requesting strict standard compliance e.g. with `-std=c99'. In ! addition to the GCC low-level builtins `-mzvector' enables a set ! of builtins added for compatibility with AltiVec-style ! implementations like Power and Cell. In order to make use of these ! builtins the header file `vecintrin.h' needs to be included. ! `-mzvector' is disabled by default. ! `-mmvcle' ! `-mno-mvcle' ! Generate (or do not generate) code using the `mvcle' instruction ! to perform block moves. When `-mno-mvcle' is specified, use a ! `mvc' loop instead. This is the default unless optimizing for ! size. ! `-mdebug' ! `-mno-debug' Print (or do not print) additional debug information when compiling. The default is to not print debug information. ! `-march=CPU-TYPE' Generate code that runs on CPU-TYPE, which is the name of a system representing a certain processor type. Possible values for ! CPU-TYPE are `z900', `z990', `z9-109', `z9-ec', `z10', `z196', ! `zEC12', and `z13'. The default is `-march=z900'. `g5' and `g6' are deprecated and will be removed with future releases. ! `-mtune=CPU-TYPE' Tune to CPU-TYPE everything applicable about the generated code, ! except for the ABI and the set of available instructions. The ! list of CPU-TYPE values is the same as for `-march'. The default ! is the value used for `-march'. ! `-mtpf-trace' ! `-mno-tpf-trace' Generate code that adds (does not add) in TPF OS specific branches to trace routines in the operating system. This option is off by default, even when compiling for the TPF OS. ! `-mfused-madd' ! `-mno-fused-madd' Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. ! `-mwarn-framesize=FRAMESIZE' Emit a warning if the current function exceeds the given frame ! size. Because this is a compile-time check it doesn't need to be ! a real problem when the program runs. It is intended to identify functions that most probably cause a stack overflow. It is useful ! to be used in an environment with limited stack size e.g. the ! linux kernel. ! `-mwarn-dynamicstack' ! Emit a warning if the function calls `alloca' or uses dynamically-sized arrays. This is generally a bad idea with a limited stack size. ! `-mstack-guard=STACK-GUARD' ! `-mstack-size=STACK-SIZE' If these options are provided the S/390 back end emits additional instructions in the function prologue that trigger a trap if the ! stack size is STACK-GUARD bytes above the STACK-SIZE (remember ! that the stack on S/390 grows downward). If the STACK-GUARD ! option is omitted the smallest power of 2 larger than the frame ! size of the compiled function is chosen. These options are ! intended to be used to help debugging stack overflow problems. ! The additionally emitted code causes only little overhead and ! hence can also be used in production-like systems without greater ! performance degradation. The given values have to be exact powers ! of 2 and STACK-SIZE has to be greater than STACK-GUARD without ! exceeding 64k. In order to be efficient the extra code makes the ! assumption that the stack starts at an address aligned to the ! value given by STACK-SIZE. The STACK-GUARD option can only be ! used in conjunction with STACK-SIZE. ! `-mhotpatch=PRE-HALFWORDS,POST-HALFWORDS' If the hotpatch option is enabled, a "hot-patching" function prologue is generated for all functions in the compilation unit. The funtion label is prepended with the given number of two-byte NOP instructions (PRE-HALFWORDS, maximum 1000000). After the ! label, 2 * POST-HALFWORDS bytes are appended, using the largest ! NOP like instructions the architecture allows (maximum 1000000). If both arguments are zero, hotpatching is disabled. This option can be overridden for individual functions with the ! `hotpatch' attribute.  File: gcc.info, Node: Score Options, Next: SH Options, Prev: S/390 and zSeries Options, Up: Submodel Options *************** File: gcc.info, Node: Score Options, N *** 19715,19747 **** These options are defined for Score implementations: ! '-meb' Compile code for big-endian mode. This is the default. ! '-mel' Compile code for little-endian mode. ! '-mnhwloop' ! Disable generation of 'bcnz' instructions. ! '-muls' Enable generation of unaligned load and store instructions. ! '-mmac' ! Enable the use of multiply-accumulate instructions. Disabled by default. ! '-mscore5' Specify the SCORE5 as the target architecture. ! '-mscore5u' Specify the SCORE5U of the target architecture. ! '-mscore7' ! Specify the SCORE7 as the target architecture. This is the ! default. ! '-mscore7d' Specify the SCORE7D as the target architecture.  --- 19822,19853 ---- These options are defined for Score implementations: ! `-meb' Compile code for big-endian mode. This is the default. ! `-mel' Compile code for little-endian mode. ! `-mnhwloop' ! Disable generation of `bcnz' instructions. ! `-muls' Enable generation of unaligned load and store instructions. ! `-mmac' ! Enable the use of multiply-accumulate instructions. Disabled by default. ! `-mscore5' Specify the SCORE5 as the target architecture. ! `-mscore5u' Specify the SCORE5U of the target architecture. ! `-mscore7' ! Specify the SCORE7 as the target architecture. This is the default. ! `-mscore7d' Specify the SCORE7D as the target architecture.  *************** File: gcc.info, Node: SH Options, Next *** 19750,19985 **** 3.18.42 SH Options ------------------ ! These '-m' options are defined for the SH implementations: ! '-m1' Generate code for the SH1. ! '-m2' Generate code for the SH2. ! '-m2e' Generate code for the SH2e. ! '-m2a-nofpu' ! Generate code for the SH2a without FPU, or for a SH2a-FPU in such a ! way that the floating-point unit is not used. ! '-m2a-single-only' Generate code for the SH2a-FPU, in such a way that no double-precision floating-point operations are used. ! '-m2a-single' Generate code for the SH2a-FPU assuming the floating-point unit is in single-precision mode by default. ! '-m2a' Generate code for the SH2a-FPU assuming the floating-point unit is in double-precision mode by default. ! '-m3' Generate code for the SH3. ! '-m3e' Generate code for the SH3e. ! '-m4-nofpu' Generate code for the SH4 without a floating-point unit. ! '-m4-single-only' Generate code for the SH4 with a floating-point unit that only supports single-precision arithmetic. ! '-m4-single' Generate code for the SH4 assuming the floating-point unit is in single-precision mode by default. ! '-m4' Generate code for the SH4. ! '-m4-100' Generate code for SH4-100. ! '-m4-100-nofpu' Generate code for SH4-100 in such a way that the floating-point unit is not used. ! '-m4-100-single' Generate code for SH4-100 assuming the floating-point unit is in single-precision mode by default. ! '-m4-100-single-only' Generate code for SH4-100 in such a way that no double-precision floating-point operations are used. ! '-m4-200' Generate code for SH4-200. ! '-m4-200-nofpu' Generate code for SH4-200 without in such a way that the floating-point unit is not used. ! '-m4-200-single' Generate code for SH4-200 assuming the floating-point unit is in single-precision mode by default. ! '-m4-200-single-only' Generate code for SH4-200 in such a way that no double-precision floating-point operations are used. ! '-m4-300' Generate code for SH4-300. ! '-m4-300-nofpu' Generate code for SH4-300 without in such a way that the floating-point unit is not used. ! '-m4-300-single' Generate code for SH4-300 in such a way that no double-precision floating-point operations are used. ! '-m4-300-single-only' Generate code for SH4-300 in such a way that no double-precision floating-point operations are used. ! '-m4-340' Generate code for SH4-340 (no MMU, no FPU). ! '-m4-500' ! Generate code for SH4-500 (no FPU). Passes '-isa=sh4-nofpu' to the assembler. ! '-m4a-nofpu' Generate code for the SH4al-dsp, or for a SH4a in such a way that the floating-point unit is not used. ! '-m4a-single-only' Generate code for the SH4a, in such a way that no double-precision floating-point operations are used. ! '-m4a-single' Generate code for the SH4a assuming the floating-point unit is in single-precision mode by default. ! '-m4a' Generate code for the SH4a. ! '-m4al' ! Same as '-m4a-nofpu', except that it implicitly passes '-dsp' to the assembler. GCC doesn't generate any DSP instructions at the moment. ! '-mb' Compile code for the processor in big-endian mode. ! '-ml' Compile code for the processor in little-endian mode. ! '-mdalign' Align doubles at 64-bit boundaries. Note that this changes the calling conventions, and thus some functions from the standard C ! library do not work unless you recompile it first with '-mdalign'. ! '-mrelax' Shorten some address references at link time, when possible; uses ! the linker option '-relax'. ! '-mbigtable' ! Use 32-bit offsets in 'switch' tables. The default is to use 16-bit offsets. ! '-mbitops' Enable the use of bit manipulation instructions on SH2A. ! '-mfmovd' ! Enable the use of the instruction 'fmovd'. Check '-mdalign' for alignment constraints. ! '-mrenesas' Comply with the calling conventions defined by Renesas. ! '-mno-renesas' Comply with the calling conventions defined for GCC before the ! Renesas conventions were available. This option is the default for ! all targets of the SH toolchain. ! '-mnomacsave' ! Mark the 'MAC' register as call-clobbered, even if '-mrenesas' is given. ! '-mieee' ! '-mno-ieee' Control the IEEE compliance of floating-point comparisons, which affects the handling of cases where the result of a comparison is ! unordered. By default '-mieee' is implicitly enabled. If ! '-ffinite-math-only' is enabled '-mno-ieee' is implicitly set, ! which results in faster floating-point greater-equal and less-equal ! comparisons. The implicit settings can be overridden by specifying ! either '-mieee' or '-mno-ieee'. ! '-minline-ic_invalidate' Inline code to invalidate instruction cache entries after setting up nested function trampolines. This option has no effect if ! '-musermode' is in effect and the selected code generation option ! (e.g. '-m4') does not allow the use of the 'icbi' instruction. If the selected code generation option does not allow the use of the ! 'icbi' instruction, and '-musermode' is not in effect, the inlined code manipulates the instruction cache address array directly with an associative write. This not only requires privileged mode at run time, but it also fails if the cache line had been mapped via the TLB and has become unmapped. ! '-misize' Dump instruction size and location in the assembly code. ! '-mpadstruct' This option is deprecated. It pads structures to multiple of 4 bytes, which is incompatible with the SH ABI. ! '-matomic-model=MODEL' Sets the model of atomic operations and additional parameters as a ! comma separated list. For details on the atomic built-in functions ! see *note __atomic Builtins::. The following models and parameters ! are supported: ! 'none' Disable compiler generated atomic sequences and emit library calls for atomic operations. This is the default if the ! target is not 'sh*-*-linux*'. ! 'soft-gusa' Generate GNU/Linux compatible gUSA software atomic sequences for the atomic built-in functions. The generated atomic sequences require additional support from the interrupt/exception handling code of the system and are only suitable for SH3* and SH4* single-core systems. This option ! is enabled by default when the target is 'sh*-*-linux*' and SH3* or SH4*. When the target is SH4A, this option also ! partially utilizes the hardware atomic instructions 'movli.l' ! and 'movco.l' to create more efficient code, unless 'strict' is specified. ! 'soft-tcb' Generate software atomic sequences that use a variable in the thread control block. This is a variation of the gUSA sequences which can also be used on SH1* and SH2* targets. ! The generated atomic sequences require additional support from ! the interrupt/exception handling code of the system and are ! only suitable for single-core systems. When using this model, ! the 'gbr-offset=' parameter has to be specified as well. ! 'soft-imask' Generate software atomic sequences that temporarily disable ! interrupts by setting 'SR.IMASK = 1111'. This model works only when the program runs in privileged mode and is only ! suitable for single-core systems. Additional support from the ! interrupt/exception handling code of the system is not required. This model is enabled by default when the target is ! 'sh*-*-linux*' and SH1* or SH2*. ! 'hard-llcs' ! Generate hardware atomic sequences using the 'movli.l' and ! 'movco.l' instructions only. This is only available on SH4A and is suitable for multi-core systems. Since the hardware instructions support only 32 bit atomic variables access to 8 or 16 bit variables is emulated with 32 bit accesses. Code --- 19856,20092 ---- 3.18.42 SH Options ------------------ ! These `-m' options are defined for the SH implementations: ! `-m1' Generate code for the SH1. ! `-m2' Generate code for the SH2. ! `-m2e' Generate code for the SH2e. ! `-m2a-nofpu' ! Generate code for the SH2a without FPU, or for a SH2a-FPU in such ! a way that the floating-point unit is not used. ! `-m2a-single-only' Generate code for the SH2a-FPU, in such a way that no double-precision floating-point operations are used. ! `-m2a-single' Generate code for the SH2a-FPU assuming the floating-point unit is in single-precision mode by default. ! `-m2a' Generate code for the SH2a-FPU assuming the floating-point unit is in double-precision mode by default. ! `-m3' Generate code for the SH3. ! `-m3e' Generate code for the SH3e. ! `-m4-nofpu' Generate code for the SH4 without a floating-point unit. ! `-m4-single-only' Generate code for the SH4 with a floating-point unit that only supports single-precision arithmetic. ! `-m4-single' Generate code for the SH4 assuming the floating-point unit is in single-precision mode by default. ! `-m4' Generate code for the SH4. ! `-m4-100' Generate code for SH4-100. ! `-m4-100-nofpu' Generate code for SH4-100 in such a way that the floating-point unit is not used. ! `-m4-100-single' Generate code for SH4-100 assuming the floating-point unit is in single-precision mode by default. ! `-m4-100-single-only' Generate code for SH4-100 in such a way that no double-precision floating-point operations are used. ! `-m4-200' Generate code for SH4-200. ! `-m4-200-nofpu' Generate code for SH4-200 without in such a way that the floating-point unit is not used. ! `-m4-200-single' Generate code for SH4-200 assuming the floating-point unit is in single-precision mode by default. ! `-m4-200-single-only' Generate code for SH4-200 in such a way that no double-precision floating-point operations are used. ! `-m4-300' Generate code for SH4-300. ! `-m4-300-nofpu' Generate code for SH4-300 without in such a way that the floating-point unit is not used. ! `-m4-300-single' Generate code for SH4-300 in such a way that no double-precision floating-point operations are used. ! `-m4-300-single-only' Generate code for SH4-300 in such a way that no double-precision floating-point operations are used. ! `-m4-340' Generate code for SH4-340 (no MMU, no FPU). ! `-m4-500' ! Generate code for SH4-500 (no FPU). Passes `-isa=sh4-nofpu' to the assembler. ! `-m4a-nofpu' Generate code for the SH4al-dsp, or for a SH4a in such a way that the floating-point unit is not used. ! `-m4a-single-only' Generate code for the SH4a, in such a way that no double-precision floating-point operations are used. ! `-m4a-single' Generate code for the SH4a assuming the floating-point unit is in single-precision mode by default. ! `-m4a' Generate code for the SH4a. ! `-m4al' ! Same as `-m4a-nofpu', except that it implicitly passes `-dsp' to the assembler. GCC doesn't generate any DSP instructions at the moment. ! `-mb' Compile code for the processor in big-endian mode. ! `-ml' Compile code for the processor in little-endian mode. ! `-mdalign' Align doubles at 64-bit boundaries. Note that this changes the calling conventions, and thus some functions from the standard C ! library do not work unless you recompile it first with `-mdalign'. ! `-mrelax' Shorten some address references at link time, when possible; uses ! the linker option `-relax'. ! `-mbigtable' ! Use 32-bit offsets in `switch' tables. The default is to use 16-bit offsets. ! `-mbitops' Enable the use of bit manipulation instructions on SH2A. ! `-mfmovd' ! Enable the use of the instruction `fmovd'. Check `-mdalign' for alignment constraints. ! `-mrenesas' Comply with the calling conventions defined by Renesas. ! `-mno-renesas' Comply with the calling conventions defined for GCC before the ! Renesas conventions were available. This option is the default ! for all targets of the SH toolchain. ! `-mnomacsave' ! Mark the `MAC' register as call-clobbered, even if `-mrenesas' is given. ! `-mieee' ! `-mno-ieee' Control the IEEE compliance of floating-point comparisons, which affects the handling of cases where the result of a comparison is ! unordered. By default `-mieee' is implicitly enabled. If ! `-ffinite-math-only' is enabled `-mno-ieee' is implicitly set, ! which results in faster floating-point greater-equal and ! less-equal comparisons. The implicit settings can be overridden ! by specifying either `-mieee' or `-mno-ieee'. ! `-minline-ic_invalidate' Inline code to invalidate instruction cache entries after setting up nested function trampolines. This option has no effect if ! `-musermode' is in effect and the selected code generation option ! (e.g. `-m4') does not allow the use of the `icbi' instruction. If the selected code generation option does not allow the use of the ! `icbi' instruction, and `-musermode' is not in effect, the inlined code manipulates the instruction cache address array directly with an associative write. This not only requires privileged mode at run time, but it also fails if the cache line had been mapped via the TLB and has become unmapped. ! `-misize' Dump instruction size and location in the assembly code. ! `-mpadstruct' This option is deprecated. It pads structures to multiple of 4 bytes, which is incompatible with the SH ABI. ! `-matomic-model=MODEL' Sets the model of atomic operations and additional parameters as a ! comma separated list. For details on the atomic built-in ! functions see *note __atomic Builtins::. The following models and ! parameters are supported: ! `none' Disable compiler generated atomic sequences and emit library calls for atomic operations. This is the default if the ! target is not `sh*-*-linux*'. ! `soft-gusa' Generate GNU/Linux compatible gUSA software atomic sequences for the atomic built-in functions. The generated atomic sequences require additional support from the interrupt/exception handling code of the system and are only suitable for SH3* and SH4* single-core systems. This option ! is enabled by default when the target is `sh*-*-linux*' and SH3* or SH4*. When the target is SH4A, this option also ! partially utilizes the hardware atomic instructions `movli.l' ! and `movco.l' to create more efficient code, unless `strict' is specified. ! `soft-tcb' Generate software atomic sequences that use a variable in the thread control block. This is a variation of the gUSA sequences which can also be used on SH1* and SH2* targets. ! The generated atomic sequences require additional support ! from the interrupt/exception handling code of the system and ! are only suitable for single-core systems. When using this ! model, the `gbr-offset=' parameter has to be specified as ! well. ! `soft-imask' Generate software atomic sequences that temporarily disable ! interrupts by setting `SR.IMASK = 1111'. This model works only when the program runs in privileged mode and is only ! suitable for single-core systems. Additional support from ! the interrupt/exception handling code of the system is not required. This model is enabled by default when the target is ! `sh*-*-linux*' and SH1* or SH2*. ! `hard-llcs' ! Generate hardware atomic sequences using the `movli.l' and ! `movco.l' instructions only. This is only available on SH4A and is suitable for multi-core systems. Since the hardware instructions support only 32 bit atomic variables access to 8 or 16 bit variables is emulated with 32 bit accesses. Code *************** These '-m' options are defined for the S *** 19989,20176 **** interrupt/exception handling code of the system is not required for this model. ! 'gbr-offset=' This parameter specifies the offset in bytes of the variable in the thread control block structure that should be used by ! the generated atomic sequences when the 'soft-tcb' model has been selected. For other models this parameter is ignored. ! The specified value must be an integer multiple of four and in ! the range 0-1020. ! 'strict' ! This parameter prevents mixed usage of multiple atomic models, ! even if they are compatible, and makes the compiler generate ! atomic sequences of the specified model only. ! '-mtas' ! Generate the 'tas.b' opcode for '__atomic_test_and_set'. Notice that depending on the particular hardware and software configuration this can degrade overall performance due to the ! operand cache line flushes that are implied by the 'tas.b' ! instruction. On multi-core SH4A processors the 'tas.b' instruction ! must be used with caution since it can result in data corruption ! for certain cache configurations. ! '-mprefergot' When generating position-independent code, emit function calls using the Global Offset Table instead of the Procedure Linkage Table. ! '-musermode' ! '-mno-usermode' Don't allow (allow) the compiler generating privileged mode code. ! Specifying '-musermode' also implies '-mno-inline-ic_invalidate' if ! the inlined code would not work in user mode. '-musermode' is the ! default when the target is 'sh*-*-linux*'. If the target is SH1* ! or SH2* '-musermode' has no effect, since there is no user mode. ! '-multcost=NUMBER' Set the cost to assume for a multiply insn. ! '-mdiv=STRATEGY' Set the division strategy to be used for integer division operations. STRATEGY can be one of: ! 'call-div1' Calls a library function that uses the single-step division ! instruction 'div1' to perform the operation. Division by zero ! calculates an unspecified result and does not trap. This is ! the default except for SH4, SH2A and SHcompact. ! 'call-fp' ! Calls a library function that performs the operation in double ! precision floating point. Division by zero causes a floating-point exception. This is the default for SHcompact ! with FPU. Specifying this for targets that do not have a ! double precision FPU defaults to 'call-div1'. ! 'call-table' Calls a library function that uses a lookup table for small ! divisors and the 'div1' instruction with case distinction for larger divisors. Division by zero calculates an unspecified result and does not trap. This is the default for SH4. Specifying this for targets that do not have dynamic shift ! instructions defaults to 'call-div1'. When a division strategy has not been specified the default strategy is selected based on the current target. For SH2A the ! default strategy is to use the 'divs' and 'divu' instructions instead of library function calls. ! '-maccumulate-outgoing-args' Reserve space once for outgoing arguments in the function prologue ! rather than around each call. Generally beneficial for performance ! and size. Also needed for unwinding to avoid changing the stack ! frame around conditional code. ! '-mdivsi3_libfunc=NAME' Set the name of the library function used for 32-bit signed ! division to NAME. This only affects the name used in the 'call' division strategies, and the compiler still expects the same sets of input/output/clobbered registers as if this option were not present. ! '-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator can not use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! '-mbranch-cost=NUM' Assume NUM to be the cost for a branch instruction. Higher numbers make the compiler try to generate more branch-free code if possible. If not specified the value is selected depending on the processor type that is being compiled for. ! '-mzdcbranch' ! '-mno-zdcbranch' Assume (do not assume) that zero displacement conditional branch ! instructions 'bt' and 'bf' are fast. If '-mzdcbranch' is specified, the compiler prefers zero displacement branch code ! sequences. This is enabled by default when generating code for SH4 ! and SH4A. It can be explicitly disabled by specifying ! '-mno-zdcbranch'. ! '-mcbranch-force-delay-slot' Force the usage of delay slots for conditional branches, which ! stuffs the delay slot with a 'nop' if a suitable instruction can't be found. By default this option is disabled. It can be enabled to work around hardware bugs as found in the original SH7055. ! '-mfused-madd' ! '-mno-fused-madd' Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. The machine-dependent ! '-mfused-madd' option is now mapped to the machine-independent ! '-ffp-contract=fast' option, and '-mno-fused-madd' is mapped to ! '-ffp-contract=off'. ! '-mfsca' ! '-mno-fsca' ! Allow or disallow the compiler to emit the 'fsca' instruction for ! sine and cosine approximations. The option '-mfsca' must be used ! in combination with '-funsafe-math-optimizations'. It is enabled ! by default when generating code for SH4A. Using '-mno-fsca' disables sine and cosine approximations even if ! '-funsafe-math-optimizations' is in effect. ! '-mfsrra' ! '-mno-fsrra' ! Allow or disallow the compiler to emit the 'fsrra' instruction for ! reciprocal square root approximations. The option '-mfsrra' must ! be used in combination with '-funsafe-math-optimizations' and ! '-ffinite-math-only'. It is enabled by default when generating ! code for SH4A. Using '-mno-fsrra' disables reciprocal square root ! approximations even if '-funsafe-math-optimizations' and ! '-ffinite-math-only' are in effect. ! '-mpretend-cmove' Prefer zero-displacement conditional branches for conditional move instruction patterns. This can result in faster code on the SH4 processor. ! '-mfdpic' Generate code using the FDPIC ABI.  File: gcc.info, Node: Solaris 2 Options, Next: SPARC Options, Prev: SH Options, Up: Submodel Options 3.18.43 Solaris 2 Options ------------------------- ! These '-m' options are supported on Solaris 2: ! '-mclear-hwcap' ! '-mclear-hwcap' tells the compiler to remove the hardware capabilities generated by the Solaris assembler. This is only ! necessary when object files use ISA extensions not supported by the ! current machine, but check at runtime whether or not to use them. ! '-mimpure-text' ! '-mimpure-text', used in addition to '-shared', tells the compiler ! to not pass '-z text' to the linker when linking a shared object. Using this option, you can link position-dependent code into a shared object. ! '-mimpure-text' suppresses the "relocations remain against allocatable but non-writable sections" linker error message. However, the necessary relocations trigger copy-on-write, and the shared object is not actually shared across processes. Instead of ! using '-mimpure-text', you should compile all source code with ! '-fpic' or '-fPIC'. These switches are supported in addition to the above on Solaris 2: ! '-pthreads' Add support for multithreading using the POSIX threads library. This option sets flags for both the preprocessor and linker. This ! option does not affect the thread safety of object code produced by ! the compiler or that of libraries supplied with it. ! '-pthread' ! This is a synonym for '-pthreads'.  File: gcc.info, Node: SPARC Options, Next: SPU Options, Prev: Solaris 2 Options, Up: Submodel Options --- 20096,20289 ---- interrupt/exception handling code of the system is not required for this model. ! `gbr-offset=' This parameter specifies the offset in bytes of the variable in the thread control block structure that should be used by ! the generated atomic sequences when the `soft-tcb' model has been selected. For other models this parameter is ignored. ! The specified value must be an integer multiple of four and ! in the range 0-1020. ! `strict' ! This parameter prevents mixed usage of multiple atomic ! models, even if they are compatible, and makes the compiler ! generate atomic sequences of the specified model only. ! ! `-mtas' ! Generate the `tas.b' opcode for `__atomic_test_and_set'. Notice that depending on the particular hardware and software configuration this can degrade overall performance due to the ! operand cache line flushes that are implied by the `tas.b' ! instruction. On multi-core SH4A processors the `tas.b' ! instruction must be used with caution since it can result in data ! corruption for certain cache configurations. ! `-mprefergot' When generating position-independent code, emit function calls using the Global Offset Table instead of the Procedure Linkage Table. ! `-musermode' ! `-mno-usermode' Don't allow (allow) the compiler generating privileged mode code. ! Specifying `-musermode' also implies `-mno-inline-ic_invalidate' ! if the inlined code would not work in user mode. `-musermode' is ! the default when the target is `sh*-*-linux*'. If the target is ! SH1* or SH2* `-musermode' has no effect, since there is no user ! mode. ! `-multcost=NUMBER' Set the cost to assume for a multiply insn. ! `-mdiv=STRATEGY' Set the division strategy to be used for integer division operations. STRATEGY can be one of: ! `call-div1' Calls a library function that uses the single-step division ! instruction `div1' to perform the operation. Division by ! zero calculates an unspecified result and does not trap. ! This is the default except for SH4, SH2A and SHcompact. ! `call-fp' ! Calls a library function that performs the operation in ! double precision floating point. Division by zero causes a floating-point exception. This is the default for SHcompact ! with FPU. Specifying this for targets that do not have a ! double precision FPU defaults to `call-div1'. ! `call-table' Calls a library function that uses a lookup table for small ! divisors and the `div1' instruction with case distinction for larger divisors. Division by zero calculates an unspecified result and does not trap. This is the default for SH4. Specifying this for targets that do not have dynamic shift ! instructions defaults to `call-div1'. ! When a division strategy has not been specified the default strategy is selected based on the current target. For SH2A the ! default strategy is to use the `divs' and `divu' instructions instead of library function calls. ! `-maccumulate-outgoing-args' Reserve space once for outgoing arguments in the function prologue ! rather than around each call. Generally beneficial for ! performance and size. Also needed for unwinding to avoid changing ! the stack frame around conditional code. ! `-mdivsi3_libfunc=NAME' Set the name of the library function used for 32-bit signed ! division to NAME. This only affects the name used in the `call' division strategies, and the compiler still expects the same sets of input/output/clobbered registers as if this option were not present. ! `-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator can not use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! `-mbranch-cost=NUM' Assume NUM to be the cost for a branch instruction. Higher numbers make the compiler try to generate more branch-free code if possible. If not specified the value is selected depending on the processor type that is being compiled for. ! `-mzdcbranch' ! `-mno-zdcbranch' Assume (do not assume) that zero displacement conditional branch ! instructions `bt' and `bf' are fast. If `-mzdcbranch' is specified, the compiler prefers zero displacement branch code ! sequences. This is enabled by default when generating code for ! SH4 and SH4A. It can be explicitly disabled by specifying ! `-mno-zdcbranch'. ! `-mcbranch-force-delay-slot' Force the usage of delay slots for conditional branches, which ! stuffs the delay slot with a `nop' if a suitable instruction can't be found. By default this option is disabled. It can be enabled to work around hardware bugs as found in the original SH7055. ! `-mfused-madd' ! `-mno-fused-madd' Generate code that uses (does not use) the floating-point multiply and accumulate instructions. These instructions are generated by default if hardware floating point is used. The machine-dependent ! `-mfused-madd' option is now mapped to the machine-independent ! `-ffp-contract=fast' option, and `-mno-fused-madd' is mapped to ! `-ffp-contract=off'. ! `-mfsca' ! `-mno-fsca' ! Allow or disallow the compiler to emit the `fsca' instruction for ! sine and cosine approximations. The option `-mfsca' must be used ! in combination with `-funsafe-math-optimizations'. It is enabled ! by default when generating code for SH4A. Using `-mno-fsca' disables sine and cosine approximations even if ! `-funsafe-math-optimizations' is in effect. ! `-mfsrra' ! `-mno-fsrra' ! Allow or disallow the compiler to emit the `fsrra' instruction for ! reciprocal square root approximations. The option `-mfsrra' must ! be used in combination with `-funsafe-math-optimizations' and ! `-ffinite-math-only'. It is enabled by default when generating ! code for SH4A. Using `-mno-fsrra' disables reciprocal square root ! approximations even if `-funsafe-math-optimizations' and ! `-ffinite-math-only' are in effect. ! `-mpretend-cmove' Prefer zero-displacement conditional branches for conditional move instruction patterns. This can result in faster code on the SH4 processor. ! `-mfdpic' Generate code using the FDPIC ABI. +  File: gcc.info, Node: Solaris 2 Options, Next: SPARC Options, Prev: SH Options, Up: Submodel Options 3.18.43 Solaris 2 Options ------------------------- ! These `-m' options are supported on Solaris 2: ! `-mclear-hwcap' ! `-mclear-hwcap' tells the compiler to remove the hardware capabilities generated by the Solaris assembler. This is only ! necessary when object files use ISA extensions not supported by ! the current machine, but check at runtime whether or not to use ! them. ! `-mimpure-text' ! `-mimpure-text', used in addition to `-shared', tells the compiler ! to not pass `-z text' to the linker when linking a shared object. Using this option, you can link position-dependent code into a shared object. ! `-mimpure-text' suppresses the "relocations remain against allocatable but non-writable sections" linker error message. However, the necessary relocations trigger copy-on-write, and the shared object is not actually shared across processes. Instead of ! using `-mimpure-text', you should compile all source code with ! `-fpic' or `-fPIC'. ! These switches are supported in addition to the above on Solaris 2: ! `-pthreads' Add support for multithreading using the POSIX threads library. This option sets flags for both the preprocessor and linker. This ! option does not affect the thread safety of object code produced ! by the compiler or that of libraries supplied with it. ! `-pthread' ! This is a synonym for `-pthreads'.  File: gcc.info, Node: SPARC Options, Next: SPU Options, Prev: Solaris 2 Options, Up: Submodel Options *************** File: gcc.info, Node: SPARC Options, N *** 20178,20236 **** 3.18.44 SPARC Options --------------------- ! These '-m' options are supported on the SPARC: ! '-mno-app-regs' ! '-mapp-regs' ! Specify '-mapp-regs' to generate output using the global registers 2 through 4, which the SPARC SVR4 ABI reserves for applications. Like the global register 1, each global register 2 through 4 is ! then treated as an allocable register that is clobbered by function ! calls. This is the default. To be fully SVR4 ABI-compliant at the cost of some performance ! loss, specify '-mno-app-regs'. You should compile libraries and system software with this option. ! '-mflat' ! '-mno-flat' ! With '-mflat', the compiler does not generate save/restore instructions and uses a "flat" or single register window model. This model is compatible with the regular register window model. ! The local registers and the input registers (0-5) are still treated ! as "call-saved" registers and are saved on the stack as needed. ! With '-mno-flat' (the default), the compiler generates save/restore instructions (except for leaf functions). This is the normal operating mode. ! '-mfpu' ! '-mhard-float' Generate output containing floating-point instructions. This is the default. ! '-mno-fpu' ! '-msoft-float' Generate output containing library calls for floating point. *Warning:* the requisite libraries are not available for all SPARC ! targets. Normally the facilities of the machine's usual C compiler ! are used, but this cannot be done directly in cross-compilation. ! You must make your own arrangements to provide suitable library ! functions for cross-compilation. The embedded targets ! 'sparc-*-aout' and 'sparclite-*-*' do provide software floating-point support. ! '-msoft-float' changes the calling convention in the output file; therefore, it is only useful if you compile _all_ of a program with ! this option. In particular, you need to compile 'libgcc.a', the ! library that comes with GCC, with '-msoft-float' in order for this to work. ! '-mhard-quad-float' Generate output containing quad-word (long double) floating-point instructions. ! '-msoft-quad-float' Generate output containing library calls for quad-word (long double) floating-point instructions. The functions called are those specified in the SPARC ABI. This is the default. --- 20291,20350 ---- 3.18.44 SPARC Options --------------------- ! These `-m' options are supported on the SPARC: ! `-mno-app-regs' ! `-mapp-regs' ! Specify `-mapp-regs' to generate output using the global registers 2 through 4, which the SPARC SVR4 ABI reserves for applications. Like the global register 1, each global register 2 through 4 is ! then treated as an allocable register that is clobbered by ! function calls. This is the default. To be fully SVR4 ABI-compliant at the cost of some performance ! loss, specify `-mno-app-regs'. You should compile libraries and system software with this option. ! `-mflat' ! `-mno-flat' ! With `-mflat', the compiler does not generate save/restore instructions and uses a "flat" or single register window model. This model is compatible with the regular register window model. ! The local registers and the input registers (0-5) are still ! treated as "call-saved" registers and are saved on the stack as ! needed. ! With `-mno-flat' (the default), the compiler generates save/restore instructions (except for leaf functions). This is the normal operating mode. ! `-mfpu' ! `-mhard-float' Generate output containing floating-point instructions. This is the default. ! `-mno-fpu' ! `-msoft-float' Generate output containing library calls for floating point. *Warning:* the requisite libraries are not available for all SPARC ! targets. Normally the facilities of the machine's usual C ! compiler are used, but this cannot be done directly in ! cross-compilation. You must make your own arrangements to provide ! suitable library functions for cross-compilation. The embedded ! targets `sparc-*-aout' and `sparclite-*-*' do provide software floating-point support. ! `-msoft-float' changes the calling convention in the output file; therefore, it is only useful if you compile _all_ of a program with ! this option. In particular, you need to compile `libgcc.a', the ! library that comes with GCC, with `-msoft-float' in order for this to work. ! `-mhard-quad-float' Generate output containing quad-word (long double) floating-point instructions. ! `-msoft-quad-float' Generate output containing library calls for quad-word (long double) floating-point instructions. The functions called are those specified in the SPARC ABI. This is the default. *************** These '-m' options are supported on the *** 20240,20253 **** They all invoke a trap handler for one of these instructions, and then the trap handler emulates the effect of the instruction. Because of the trap handler overhead, this is much slower than ! calling the ABI library routines. Thus the '-msoft-quad-float' option is the default. ! '-mno-unaligned-doubles' ! '-munaligned-doubles' Assume that doubles have 8-byte alignment. This is the default. ! With '-munaligned-doubles', GCC assumes that doubles have 8-byte alignment only if they are contained in another type, or if they have an absolute address. Otherwise, it assumes they have 4-byte alignment. Specifying this option avoids some rare compatibility --- 20354,20367 ---- They all invoke a trap handler for one of these instructions, and then the trap handler emulates the effect of the instruction. Because of the trap handler overhead, this is much slower than ! calling the ABI library routines. Thus the `-msoft-quad-float' option is the default. ! `-mno-unaligned-doubles' ! `-munaligned-doubles' Assume that doubles have 8-byte alignment. This is the default. ! With `-munaligned-doubles', GCC assumes that doubles have 8-byte alignment only if they are contained in another type, or if they have an absolute address. Otherwise, it assumes they have 4-byte alignment. Specifying this option avoids some rare compatibility *************** These '-m' options are supported on the *** 20255,20512 **** default because it results in a performance loss, especially for floating-point code. ! '-muser-mode' ! '-mno-user-mode' ! Do not generate code that can only run in supervisor mode. This is ! relevant only for the 'casa' instruction emitted for the LEON3 processor. This is the default. ! '-mfaster-structs' ! '-mno-faster-structs' ! With '-mfaster-structs', the compiler assumes that structures should have 8-byte alignment. This enables the use of pairs of ! 'ldd' and 'std' instructions for copies in structure assignment, in ! place of twice as many 'ld' and 'st' pairs. However, the use of ! this changed alignment directly violates the SPARC ABI. Thus, it's ! intended only for use on targets where the developer acknowledges ! that their resulting code is not directly in line with the rules of ! the ABI. ! '-mstd-struct-return' ! '-mno-std-struct-return' ! With '-mstd-struct-return', the compiler generates checking code in ! functions returning structures or unions to detect size mismatches ! between the two sides of function calls, as per the 32-bit ABI. ! The default is '-mno-std-struct-return'. This option has no effect in 64-bit mode. ! '-mcpu=CPU_TYPE' Set the instruction set, register set, and instruction scheduling parameters for machine type CPU_TYPE. Supported values for ! CPU_TYPE are 'v7', 'cypress', 'v8', 'supersparc', 'hypersparc', ! 'leon', 'leon3', 'leon3v7', 'sparclite', 'f930', 'f934', ! 'sparclite86x', 'sparclet', 'tsc701', 'v9', 'ultrasparc', ! 'ultrasparc3', 'niagara', 'niagara2', 'niagara3', 'niagara4' and ! 'niagara7'. Native Solaris and GNU/Linux toolchains also support the value ! 'native', which selects the best architecture option for the host ! processor. '-mcpu=native' has no effect if GCC does not recognize the processor. Default instruction scheduling parameters are used for values that ! select an architecture and not an implementation. These are 'v7', ! 'v8', 'sparclite', 'sparclet', 'v9'. Here is a list of each supported architecture and their supported implementations. ! v7 cypress, leon3v7 ! v8 supersparc, hypersparc, leon, leon3 ! sparclite f930, f934, sparclite86x ! sparclet tsc701 ! v9 ultrasparc, ultrasparc3, niagara, niagara2, niagara3, niagara4, niagara7 By default (unless configured otherwise), GCC generates code for ! the V7 variant of the SPARC architecture. With '-mcpu=cypress', the compiler additionally optimizes it for the Cypress CY7C602 chip, as used in the SPARCStation/SPARCServer 3xx series. This is also appropriate for the older SPARCStation 1, 2, IPX etc. ! With '-mcpu=v8', GCC generates code for the V8 variant of the SPARC architecture. The only difference from V7 code is that the ! compiler emits the integer multiply and integer divide instructions ! which exist in SPARC-V8 but not in SPARC-V7. With ! '-mcpu=supersparc', the compiler additionally optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000 series. ! With '-mcpu=sparclite', GCC generates code for the SPARClite ! variant of the SPARC architecture. This adds the integer multiply, ! integer divide step and scan ('ffs') instructions which exist in ! SPARClite but not in SPARC-V7. With '-mcpu=f930', the compiler ! additionally optimizes it for the Fujitsu MB86930 chip, which is ! the original SPARClite, with no FPU. With '-mcpu=f934', the ! compiler additionally optimizes it for the Fujitsu MB86934 chip, ! which is the more recent SPARClite with FPU. ! With '-mcpu=sparclet', GCC generates code for the SPARClet variant of the SPARC architecture. This adds the integer multiply, ! multiply/accumulate, integer divide step and scan ('ffs') instructions which exist in SPARClet but not in SPARC-V7. With ! '-mcpu=tsc701', the compiler additionally optimizes it for the TEMIC SPARClet chip. ! With '-mcpu=v9', GCC generates code for the V9 variant of the SPARC architecture. This adds 64-bit integer and floating-point move instructions, 3 additional floating-point condition code registers ! and conditional move instructions. With '-mcpu=ultrasparc', the compiler additionally optimizes it for the Sun UltraSPARC I/II/IIi ! chips. With '-mcpu=ultrasparc3', the compiler additionally optimizes it for the Sun UltraSPARC III/III+/IIIi/IIIi+/IV/IV+ ! chips. With '-mcpu=niagara', the compiler additionally optimizes ! it for Sun UltraSPARC T1 chips. With '-mcpu=niagara2', the compiler additionally optimizes it for Sun UltraSPARC T2 chips. ! With '-mcpu=niagara3', the compiler additionally optimizes it for ! Sun UltraSPARC T3 chips. With '-mcpu=niagara4', the compiler additionally optimizes it for Sun UltraSPARC T4 chips. With ! '-mcpu=niagara7', the compiler additionally optimizes it for Oracle ! SPARC M7 chips. ! '-mtune=CPU_TYPE' Set the instruction scheduling parameters for machine type CPU_TYPE, but do not set the instruction set or register set that ! the option '-mcpu=CPU_TYPE' does. ! The same values for '-mcpu=CPU_TYPE' can be used for ! '-mtune=CPU_TYPE', but the only useful values are those that select ! a particular CPU implementation. Those are 'cypress', ! 'supersparc', 'hypersparc', 'leon', 'leon3', 'leon3v7', 'f930', ! 'f934', 'sparclite86x', 'tsc701', 'ultrasparc', 'ultrasparc3', ! 'niagara', 'niagara2', 'niagara3', 'niagara4' and 'niagara7'. With ! native Solaris and GNU/Linux toolchains, 'native' can also be used. ! '-mv8plus' ! '-mno-v8plus' ! With '-mv8plus', GCC generates code for the SPARC-V8+ ABI. The difference from the V8 ABI is that the global and out registers are considered 64 bits wide. This is enabled by default on Solaris in 32-bit mode for all SPARC-V9 processors. ! '-mvis' ! '-mno-vis' ! With '-mvis', GCC generates code that takes advantage of the UltraSPARC Visual Instruction Set extensions. The default is ! '-mno-vis'. ! '-mvis2' ! '-mno-vis2' ! With '-mvis2', GCC generates code that takes advantage of version 2.0 of the UltraSPARC Visual Instruction Set extensions. The ! default is '-mvis2' when targeting a cpu that supports such ! instructions, such as UltraSPARC-III and later. Setting '-mvis2' ! also sets '-mvis'. ! '-mvis3' ! '-mno-vis3' ! With '-mvis3', GCC generates code that takes advantage of version 3.0 of the UltraSPARC Visual Instruction Set extensions. The ! default is '-mvis3' when targeting a cpu that supports such ! instructions, such as niagara-3 and later. Setting '-mvis3' also ! sets '-mvis2' and '-mvis'. ! '-mvis4' ! '-mno-vis4' ! With '-mvis4', GCC generates code that takes advantage of version 4.0 of the UltraSPARC Visual Instruction Set extensions. The ! default is '-mvis4' when targeting a cpu that supports such ! instructions, such as niagara-7 and later. Setting '-mvis4' also ! sets '-mvis3', '-mvis2' and '-mvis'. ! '-mcbcond' ! '-mno-cbcond' ! With '-mcbcond', GCC generates code that takes advantage of compare-and-branch instructions, as defined in the Sparc ! Architecture 2011. The default is '-mcbcond' when targeting a cpu that supports such instructions, such as niagara-4 and later. ! '-mpopc' ! '-mno-popc' ! With '-mpopc', GCC generates code that takes advantage of the ! UltraSPARC population count instruction. The default is '-mpopc' when targeting a cpu that supports such instructions, such as Niagara-2 and later. ! '-mfmaf' ! '-mno-fmaf' ! With '-mfmaf', GCC generates code that takes advantage of the UltraSPARC Fused Multiply-Add Floating-point extensions. The ! default is '-mfmaf' when targeting a cpu that supports such instructions, such as Niagara-3 and later. ! '-mfix-at697f' Enable the documented workaround for the single erratum of the Atmel AT697F processor (which corresponds to erratum #13 of the AT697E processor). ! '-mfix-ut699' ! Enable the documented workarounds for the floating-point errata and ! the data cache nullify errata of the UT699 processor. ! These '-m' options are supported in addition to the above on SPARC-V9 processors in 64-bit environments: ! '-m32' ! '-m64' Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. ! '-mcmodel=WHICH' Set the code model to one of ! 'medlow' The Medium/Low code model: 64-bit addresses, programs must be linked in the low 32 bits of memory. Programs can be statically or dynamically linked. ! 'medmid' The Medium/Middle code model: 64-bit addresses, programs must be linked in the low 44 bits of memory, the text and data segments must be less than 2GB in size and the data segment must be located within 2GB of the text segment. ! 'medany' ! The Medium/Anywhere code model: 64-bit addresses, programs may ! be linked anywhere in memory, the text and data segments must ! be less than 2GB in size and the data segment must be located ! within 2GB of the text segment. ! 'embmedany' The Medium/Anywhere code model for embedded systems: 64-bit addresses, the text and data segments must be less than 2GB in size, both starting anywhere in memory (determined at link ! time). The global register %g4 points to the base of the data ! segment. Programs are statically linked and PIC is not supported. ! '-mmemory-model=MEM-MODEL' Set the memory model in force on the processor to one of ! 'default' The default memory model for the processor and operating system. ! 'rmo' Relaxed Memory Order ! 'pso' Partial Store Order ! 'tso' Total Store Order ! 'sc' Sequential Consistency ! These memory models are formally defined in Appendix D of the Sparc ! V9 architecture manual, as set in the processor's 'PSTATE.MM' ! field. ! '-mstack-bias' ! '-mno-stack-bias' ! With '-mstack-bias', GCC assumes that the stack pointer, and frame pointer if present, are offset by -2047 which must be added back when making stack frame references. This is the default in 64-bit mode. Otherwise, assume no such offset is present. --- 20369,20628 ---- default because it results in a performance loss, especially for floating-point code. ! `-muser-mode' ! `-mno-user-mode' ! Do not generate code that can only run in supervisor mode. This ! is relevant only for the `casa' instruction emitted for the LEON3 processor. This is the default. ! `-mfaster-structs' ! `-mno-faster-structs' ! With `-mfaster-structs', the compiler assumes that structures should have 8-byte alignment. This enables the use of pairs of ! `ldd' and `std' instructions for copies in structure assignment, ! in place of twice as many `ld' and `st' pairs. However, the use ! of this changed alignment directly violates the SPARC ABI. Thus, ! it's intended only for use on targets where the developer ! acknowledges that their resulting code is not directly in line with ! the rules of the ABI. ! `-mstd-struct-return' ! `-mno-std-struct-return' ! With `-mstd-struct-return', the compiler generates checking code ! in functions returning structures or unions to detect size ! mismatches between the two sides of function calls, as per the ! 32-bit ABI. ! The default is `-mno-std-struct-return'. This option has no effect in 64-bit mode. ! `-mcpu=CPU_TYPE' Set the instruction set, register set, and instruction scheduling parameters for machine type CPU_TYPE. Supported values for ! CPU_TYPE are `v7', `cypress', `v8', `supersparc', `hypersparc', ! `leon', `leon3', `leon3v7', `sparclite', `f930', `f934', ! `sparclite86x', `sparclet', `tsc701', `v9', `ultrasparc', ! `ultrasparc3', `niagara', `niagara2', `niagara3', `niagara4' and ! `niagara7'. Native Solaris and GNU/Linux toolchains also support the value ! `native', which selects the best architecture option for the host ! processor. `-mcpu=native' has no effect if GCC does not recognize the processor. Default instruction scheduling parameters are used for values that ! select an architecture and not an implementation. These are `v7', ! `v8', `sparclite', `sparclet', `v9'. Here is a list of each supported architecture and their supported implementations. ! v7 cypress, leon3v7 ! v8 supersparc, hypersparc, leon, leon3 ! sparclite f930, f934, sparclite86x ! sparclet tsc701 ! v9 ultrasparc, ultrasparc3, niagara, niagara2, niagara3, niagara4, niagara7 By default (unless configured otherwise), GCC generates code for ! the V7 variant of the SPARC architecture. With `-mcpu=cypress', the compiler additionally optimizes it for the Cypress CY7C602 chip, as used in the SPARCStation/SPARCServer 3xx series. This is also appropriate for the older SPARCStation 1, 2, IPX etc. ! With `-mcpu=v8', GCC generates code for the V8 variant of the SPARC architecture. The only difference from V7 code is that the ! compiler emits the integer multiply and integer divide ! instructions which exist in SPARC-V8 but not in SPARC-V7. With ! `-mcpu=supersparc', the compiler additionally optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and 2000 series. ! With `-mcpu=sparclite', GCC generates code for the SPARClite ! variant of the SPARC architecture. This adds the integer ! multiply, integer divide step and scan (`ffs') instructions which ! exist in SPARClite but not in SPARC-V7. With `-mcpu=f930', the ! compiler additionally optimizes it for the Fujitsu MB86930 chip, ! which is the original SPARClite, with no FPU. With `-mcpu=f934', ! the compiler additionally optimizes it for the Fujitsu MB86934 ! chip, which is the more recent SPARClite with FPU. ! With `-mcpu=sparclet', GCC generates code for the SPARClet variant of the SPARC architecture. This adds the integer multiply, ! multiply/accumulate, integer divide step and scan (`ffs') instructions which exist in SPARClet but not in SPARC-V7. With ! `-mcpu=tsc701', the compiler additionally optimizes it for the TEMIC SPARClet chip. ! With `-mcpu=v9', GCC generates code for the V9 variant of the SPARC architecture. This adds 64-bit integer and floating-point move instructions, 3 additional floating-point condition code registers ! and conditional move instructions. With `-mcpu=ultrasparc', the compiler additionally optimizes it for the Sun UltraSPARC I/II/IIi ! chips. With `-mcpu=ultrasparc3', the compiler additionally optimizes it for the Sun UltraSPARC III/III+/IIIi/IIIi+/IV/IV+ ! chips. With `-mcpu=niagara', the compiler additionally optimizes ! it for Sun UltraSPARC T1 chips. With `-mcpu=niagara2', the compiler additionally optimizes it for Sun UltraSPARC T2 chips. ! With `-mcpu=niagara3', the compiler additionally optimizes it for ! Sun UltraSPARC T3 chips. With `-mcpu=niagara4', the compiler additionally optimizes it for Sun UltraSPARC T4 chips. With ! `-mcpu=niagara7', the compiler additionally optimizes it for ! Oracle SPARC M7 chips. ! `-mtune=CPU_TYPE' Set the instruction scheduling parameters for machine type CPU_TYPE, but do not set the instruction set or register set that ! the option `-mcpu=CPU_TYPE' does. ! The same values for `-mcpu=CPU_TYPE' can be used for ! `-mtune=CPU_TYPE', but the only useful values are those that ! select a particular CPU implementation. Those are `cypress', ! `supersparc', `hypersparc', `leon', `leon3', `leon3v7', `f930', ! `f934', `sparclite86x', `tsc701', `ultrasparc', `ultrasparc3', ! `niagara', `niagara2', `niagara3', `niagara4' and `niagara7'. ! With native Solaris and GNU/Linux toolchains, `native' can also be ! used. ! `-mv8plus' ! `-mno-v8plus' ! With `-mv8plus', GCC generates code for the SPARC-V8+ ABI. The difference from the V8 ABI is that the global and out registers are considered 64 bits wide. This is enabled by default on Solaris in 32-bit mode for all SPARC-V9 processors. ! `-mvis' ! `-mno-vis' ! With `-mvis', GCC generates code that takes advantage of the UltraSPARC Visual Instruction Set extensions. The default is ! `-mno-vis'. ! `-mvis2' ! `-mno-vis2' ! With `-mvis2', GCC generates code that takes advantage of version 2.0 of the UltraSPARC Visual Instruction Set extensions. The ! default is `-mvis2' when targeting a cpu that supports such ! instructions, such as UltraSPARC-III and later. Setting `-mvis2' ! also sets `-mvis'. ! `-mvis3' ! `-mno-vis3' ! With `-mvis3', GCC generates code that takes advantage of version 3.0 of the UltraSPARC Visual Instruction Set extensions. The ! default is `-mvis3' when targeting a cpu that supports such ! instructions, such as niagara-3 and later. Setting `-mvis3' also ! sets `-mvis2' and `-mvis'. ! `-mvis4' ! `-mno-vis4' ! With `-mvis4', GCC generates code that takes advantage of version 4.0 of the UltraSPARC Visual Instruction Set extensions. The ! default is `-mvis4' when targeting a cpu that supports such ! instructions, such as niagara-7 and later. Setting `-mvis4' also ! sets `-mvis3', `-mvis2' and `-mvis'. ! `-mcbcond' ! `-mno-cbcond' ! With `-mcbcond', GCC generates code that takes advantage of compare-and-branch instructions, as defined in the Sparc ! Architecture 2011. The default is `-mcbcond' when targeting a cpu that supports such instructions, such as niagara-4 and later. ! `-mpopc' ! `-mno-popc' ! With `-mpopc', GCC generates code that takes advantage of the ! UltraSPARC population count instruction. The default is `-mpopc' when targeting a cpu that supports such instructions, such as Niagara-2 and later. ! `-mfmaf' ! `-mno-fmaf' ! With `-mfmaf', GCC generates code that takes advantage of the UltraSPARC Fused Multiply-Add Floating-point extensions. The ! default is `-mfmaf' when targeting a cpu that supports such instructions, such as Niagara-3 and later. ! `-mfix-at697f' Enable the documented workaround for the single erratum of the Atmel AT697F processor (which corresponds to erratum #13 of the AT697E processor). ! `-mfix-ut699' ! Enable the documented workarounds for the floating-point errata ! and the data cache nullify errata of the UT699 processor. ! These `-m' options are supported in addition to the above on SPARC-V9 processors in 64-bit environments: ! `-m32' ! `-m64' Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. ! `-mcmodel=WHICH' Set the code model to one of ! `medlow' The Medium/Low code model: 64-bit addresses, programs must be linked in the low 32 bits of memory. Programs can be statically or dynamically linked. ! `medmid' The Medium/Middle code model: 64-bit addresses, programs must be linked in the low 44 bits of memory, the text and data segments must be less than 2GB in size and the data segment must be located within 2GB of the text segment. ! `medany' ! The Medium/Anywhere code model: 64-bit addresses, programs ! may be linked anywhere in memory, the text and data segments ! must be less than 2GB in size and the data segment must be ! located within 2GB of the text segment. ! `embmedany' The Medium/Anywhere code model for embedded systems: 64-bit addresses, the text and data segments must be less than 2GB in size, both starting anywhere in memory (determined at link ! time). The global register %g4 points to the base of the ! data segment. Programs are statically linked and PIC is not supported. ! `-mmemory-model=MEM-MODEL' Set the memory model in force on the processor to one of ! `default' The default memory model for the processor and operating system. ! `rmo' Relaxed Memory Order ! `pso' Partial Store Order ! `tso' Total Store Order ! `sc' Sequential Consistency ! These memory models are formally defined in Appendix D of the ! Sparc V9 architecture manual, as set in the processor's ! `PSTATE.MM' field. ! `-mstack-bias' ! `-mno-stack-bias' ! With `-mstack-bias', GCC assumes that the stack pointer, and frame pointer if present, are offset by -2047 which must be added back when making stack frame references. This is the default in 64-bit mode. Otherwise, assume no such offset is present. *************** File: gcc.info, Node: SPU Options, Nex *** 20517,20632 **** 3.18.45 SPU Options ------------------- ! These '-m' options are supported on the SPU: ! ! '-mwarn-reloc' ! '-merror-reloc' The loader for SPU does not handle dynamic relocations. By default, GCC gives an error when it generates code that requires a ! dynamic relocation. '-mno-error-reloc' disables the error, ! '-mwarn-reloc' generates a warning instead. ! ! '-msafe-dma' ! '-munsafe-dma' Instructions that initiate or test completion of DMA must not be reordered with respect to loads and stores of the memory that is ! being accessed. With '-munsafe-dma' you must use the 'volatile' keyword to protect memory accesses, but that can lead to ! inefficient code in places where the memory is known to not change. ! Rather than mark the memory as volatile, you can use '-msafe-dma' ! to tell the compiler to treat the DMA instructions as potentially ! affecting all memory. ! ! '-mbranch-hints' By default, GCC generates a branch hint instruction to avoid pipeline stalls for always-taken or probably-taken branches. A hint is not generated closer than 8 instructions away from its branch. There is little reason to disable them, except for debugging purposes, or to make an object a little bit smaller. ! '-msmall-mem' ! '-mlarge-mem' ! By default, GCC generates code assuming that addresses are never ! larger than 18 bits. With '-mlarge-mem' code is generated that assumes a full 32-bit address. ! '-mstdmain' ! By default, GCC links against startup code that assumes the SPU-style main function interface (which has an unconventional ! parameter list). With '-mstdmain', GCC links your program against ! startup code that assumes a C99-style interface to 'main', ! including a local copy of 'argv' strings. ! '-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! '-mea32' ! '-mea64' Compile code assuming that pointers to the PPU address space ! accessed via the '__ea' named address space qualifier are either 32 ! or 64 bits wide. The default is 32 bits. As this is an ABI-changing option, all object code in an executable must be compiled with the same setting. ! '-maddress-space-conversion' ! '-mno-address-space-conversion' ! Allow/disallow treating the '__ea' address space as superset of the ! generic address space. This enables explicit type casts between ! '__ea' and generic pointer as well as implicit conversions of ! generic pointers to '__ea' pointers. The default is to allow address space pointer conversions. ! '-mcache-size=CACHE-SIZE' This option controls the version of libgcc that the compiler links ! to an executable and selects a software-managed cache for accessing ! variables in the '__ea' address space with a particular cache size. ! Possible options for CACHE-SIZE are '8', '16', '32', '64' and ! '128'. The default cache size is 64KB. ! '-matomic-updates' ! '-mno-atomic-updates' This option controls the version of libgcc that the compiler links to an executable and selects whether atomic updates to the software-managed cache of PPU-side variables are used. If you use atomic updates, changes to a PPU variable from SPU code using the ! '__ea' named address space qualifier do not interfere with changes to other PPU variables residing in the same cache line from PPU code. If you do not use atomic updates, such interference may occur; however, writing back cache lines is more efficient. The default behavior is to use atomic updates. ! '-mdual-nops' ! '-mdual-nops=N' By default, GCC inserts nops to increase dual issue when it expects it to increase performance. N can be a value from 0 to 10. A smaller N inserts fewer nops. 10 is the default, 0 is the same as ! '-mno-dual-nops'. Disabled with '-Os'. ! '-mhint-max-nops=N' Maximum number of nops to insert for a branch hint. A branch hint must be at least 8 instructions away from the branch it is affecting. GCC inserts up to N nops to enforce this, otherwise it does not generate the branch hint. ! '-mhint-max-distance=N' The encoding of the branch hint instruction limits the hint to be ! within 256 instructions of the branch it is affecting. By default, ! GCC makes sure it is within 125. ! '-msafe-hints' Work around a hardware bug that causes the SPU to stall ! indefinitely. By default, GCC inserts the 'hbrp' instruction to make sure this stall won't happen.  File: gcc.info, Node: System V Options, Next: TILE-Gx Options, Prev: SPU Options, Up: Submodel Options --- 20633,20744 ---- 3.18.45 SPU Options ------------------- ! These `-m' options are supported on the SPU: + `-mwarn-reloc' + `-merror-reloc' The loader for SPU does not handle dynamic relocations. By default, GCC gives an error when it generates code that requires a ! dynamic relocation. `-mno-error-reloc' disables the error, ! `-mwarn-reloc' generates a warning instead. + `-msafe-dma' + `-munsafe-dma' Instructions that initiate or test completion of DMA must not be reordered with respect to loads and stores of the memory that is ! being accessed. With `-munsafe-dma' you must use the `volatile' keyword to protect memory accesses, but that can lead to ! inefficient code in places where the memory is known to not ! change. Rather than mark the memory as volatile, you can use ! `-msafe-dma' to tell the compiler to treat the DMA instructions as ! potentially affecting all memory. + `-mbranch-hints' By default, GCC generates a branch hint instruction to avoid pipeline stalls for always-taken or probably-taken branches. A hint is not generated closer than 8 instructions away from its branch. There is little reason to disable them, except for debugging purposes, or to make an object a little bit smaller. ! `-msmall-mem' ! `-mlarge-mem' By default, GCC generates code assuming that addresses are never ! larger than 18 bits. With `-mlarge-mem' code is generated that assumes a full 32-bit address. ! `-mstdmain' By default, GCC links against startup code that assumes the SPU-style main function interface (which has an unconventional ! parameter list). With `-mstdmain', GCC links your program against ! startup code that assumes a C99-style interface to `main', ! including a local copy of `argv' strings. ! `-mfixed-range=REGISTER-RANGE' Generate code treating the given register range as fixed registers. A fixed register is one that the register allocator cannot use. This is useful when compiling kernel code. A register range is specified as two registers separated by a dash. Multiple register ranges can be specified separated by a comma. ! `-mea32' ! `-mea64' Compile code assuming that pointers to the PPU address space ! accessed via the `__ea' named address space qualifier are either ! 32 or 64 bits wide. The default is 32 bits. As this is an ABI-changing option, all object code in an executable must be compiled with the same setting. ! `-maddress-space-conversion' ! `-mno-address-space-conversion' ! Allow/disallow treating the `__ea' address space as superset of ! the generic address space. This enables explicit type casts ! between `__ea' and generic pointer as well as implicit conversions ! of generic pointers to `__ea' pointers. The default is to allow address space pointer conversions. ! `-mcache-size=CACHE-SIZE' This option controls the version of libgcc that the compiler links ! to an executable and selects a software-managed cache for ! accessing variables in the `__ea' address space with a particular ! cache size. Possible options for CACHE-SIZE are `8', `16', `32', ! `64' and `128'. The default cache size is 64KB. ! `-matomic-updates' ! `-mno-atomic-updates' This option controls the version of libgcc that the compiler links to an executable and selects whether atomic updates to the software-managed cache of PPU-side variables are used. If you use atomic updates, changes to a PPU variable from SPU code using the ! `__ea' named address space qualifier do not interfere with changes to other PPU variables residing in the same cache line from PPU code. If you do not use atomic updates, such interference may occur; however, writing back cache lines is more efficient. The default behavior is to use atomic updates. ! `-mdual-nops' ! `-mdual-nops=N' By default, GCC inserts nops to increase dual issue when it expects it to increase performance. N can be a value from 0 to 10. A smaller N inserts fewer nops. 10 is the default, 0 is the same as ! `-mno-dual-nops'. Disabled with `-Os'. ! `-mhint-max-nops=N' Maximum number of nops to insert for a branch hint. A branch hint must be at least 8 instructions away from the branch it is affecting. GCC inserts up to N nops to enforce this, otherwise it does not generate the branch hint. ! `-mhint-max-distance=N' The encoding of the branch hint instruction limits the hint to be ! within 256 instructions of the branch it is affecting. By ! default, GCC makes sure it is within 125. ! `-msafe-hints' Work around a hardware bug that causes the SPU to stall ! indefinitely. By default, GCC inserts the `hbrp' instruction to make sure this stall won't happen. +  File: gcc.info, Node: System V Options, Next: TILE-Gx Options, Prev: SPU Options, Up: Submodel Options *************** File: gcc.info, Node: System V Options, *** 20636,20658 **** These additional options are available on System V Release 4 for compatibility with other compilers on those systems: ! '-G' ! Create a shared object. It is recommended that '-symbolic' or ! '-shared' be used instead. ! '-Qy' Identify the versions of each tool used by the compiler, in a ! '.ident' assembler directive in the output. ! '-Qn' ! Refrain from adding '.ident' directives to the output file (this is the default). ! '-YP,DIRS' ! Search the directories DIRS, and no others, for libraries specified ! with '-l'. ! '-Ym,DIR' Look in the directory DIR to find the M4 preprocessor. The assembler uses this option. --- 20748,20770 ---- These additional options are available on System V Release 4 for compatibility with other compilers on those systems: ! `-G' ! Create a shared object. It is recommended that `-symbolic' or ! `-shared' be used instead. ! `-Qy' Identify the versions of each tool used by the compiler, in a ! `.ident' assembler directive in the output. ! `-Qn' ! Refrain from adding `.ident' directives to the output file (this is the default). ! `-YP,DIRS' ! Search the directories DIRS, and no others, for libraries ! specified with `-l'. ! `-Ym,DIR' Look in the directory DIR to find the M4 preprocessor. The assembler uses this option. *************** File: gcc.info, Node: TILE-Gx Options, *** 20662,20690 **** 3.18.47 TILE-Gx Options ----------------------- ! These '-m' options are supported on the TILE-Gx: ! '-mcmodel=small' Generate code for the small model. The distance for direct calls is limited to 500M in either direction. PC-relative addresses are 32 bits. Absolute addresses support the full address range. ! '-mcmodel=large' Generate code for the large model. There is no limitation on call distance, pc-relative addresses, or absolute addresses. ! '-mcpu=NAME' Selects the type of CPU to be targeted. Currently the only ! supported type is 'tilegx'. ! '-m32' ! '-m64' Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long, and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. ! '-mbig-endian' ! '-mlittle-endian' Generate code in big/little endian mode, respectively.  --- 20774,20802 ---- 3.18.47 TILE-Gx Options ----------------------- ! These `-m' options are supported on the TILE-Gx: ! `-mcmodel=small' Generate code for the small model. The distance for direct calls is limited to 500M in either direction. PC-relative addresses are 32 bits. Absolute addresses support the full address range. ! `-mcmodel=large' Generate code for the large model. There is no limitation on call distance, pc-relative addresses, or absolute addresses. ! `-mcpu=NAME' Selects the type of CPU to be targeted. Currently the only ! supported type is `tilegx'. ! `-m32' ! `-m64' Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long, and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. ! `-mbig-endian' ! `-mlittle-endian' Generate code in big/little endian mode, respectively.  *************** File: gcc.info, Node: TILEPro Options, *** 20693,20705 **** 3.18.48 TILEPro Options ----------------------- ! These '-m' options are supported on the TILEPro: ! '-mcpu=NAME' Selects the type of CPU to be targeted. Currently the only ! supported type is 'tilepro'. ! '-m32' Generate code for a 32-bit environment, which sets int, long, and pointer to 32 bits. This is the only supported behavior so the flag is essentially ignored. --- 20805,20817 ---- 3.18.48 TILEPro Options ----------------------- ! These `-m' options are supported on the TILEPro: ! `-mcpu=NAME' Selects the type of CPU to be targeted. Currently the only ! supported type is `tilepro'. ! `-m32' Generate code for a 32-bit environment, which sets int, long, and pointer to 32 bits. This is the only supported behavior so the flag is essentially ignored. *************** File: gcc.info, Node: V850 Options, Ne *** 20710,20837 **** 3.18.49 V850 Options -------------------- ! These '-m' options are defined for V850 implementations: ! '-mlong-calls' ! '-mno-long-calls' Treat all calls as being far away (near). If calls are assumed to be far away, the compiler always loads the function's address into a register, and calls indirect through the pointer. ! '-mno-ep' ! '-mep' Do not optimize (do optimize) basic blocks that use the same index ! pointer 4 or more times to copy pointer into the 'ep' register, and ! use the shorter 'sld' and 'sst' instructions. The '-mep' option is ! on by default if you optimize. ! '-mno-prolog-function' ! '-mprolog-function' Do not use (do use) external functions to save and restore ! registers at the prologue and epilogue of a function. The external ! functions are slower, but use less code space if more than one ! function saves the same number of registers. The ! '-mprolog-function' option is on by default if you optimize. ! '-mspace' Try to make the code as small as possible. At present, this just ! turns on the '-mep' and '-mprolog-function' options. ! '-mtda=N' Put static or global variables whose size is N bytes or less into ! the tiny data area that register 'ep' points to. The tiny data area can hold up to 256 bytes in total (128 bytes for byte references). ! '-msda=N' Put static or global variables whose size is N bytes or less into ! the small data area that register 'gp' points to. The small data area can hold up to 64 kilobytes. ! '-mzda=N' Put static or global variables whose size is N bytes or less into the first 32 kilobytes of memory. ! '-mv850' Specify that the target processor is the V850. ! '-mv850e3v5' Specify that the target processor is the V850E3V5. The ! preprocessor constant '__v850e3v5__' is defined if this option is used. ! '-mv850e2v4' Specify that the target processor is the V850E3V5. This is an ! alias for the '-mv850e3v5' option. ! '-mv850e2v3' Specify that the target processor is the V850E2V3. The ! preprocessor constant '__v850e2v3__' is defined if this option is used. ! '-mv850e2' Specify that the target processor is the V850E2. The preprocessor ! constant '__v850e2__' is defined if this option is used. ! '-mv850e1' Specify that the target processor is the V850E1. The preprocessor ! constants '__v850e1__' and '__v850e__' are defined if this option is used. ! '-mv850es' ! Specify that the target processor is the V850ES. This is an alias ! for the '-mv850e1' option. ! '-mv850e' Specify that the target processor is the V850E. The preprocessor ! constant '__v850e__' is defined if this option is used. ! If neither '-mv850' nor '-mv850e' nor '-mv850e1' nor '-mv850e2' nor ! '-mv850e2v3' nor '-mv850e3v5' are defined then a default target ! processor is chosen and the relevant '__v850*__' preprocessor ! constant is defined. ! The preprocessor constants '__v850' and '__v851__' are always defined, regardless of which processor variant is the target. ! '-mdisable-callt' ! '-mno-disable-callt' ! This option suppresses generation of the 'CALLT' instruction for the v850e, v850e1, v850e2, v850e2v3 and v850e3v5 flavors of the v850 architecture. ! This option is enabled by default when the RH850 ABI is in use (see ! '-mrh850-abi'), and disabled by default when the GCC ABI is in use. ! If 'CALLT' instructions are being generated then the C preprocessor ! symbol '__V850_CALLT__' is defined. ! '-mrelax' ! '-mno-relax' ! Pass on (or do not pass on) the '-mrelax' command-line option to the assembler. ! '-mlong-jumps' ! '-mno-long-jumps' Disable (or re-enable) the generation of PC-relative jump instructions. ! '-msoft-float' ! '-mhard-float' Disable (or re-enable) the generation of hardware floating point instructions. This option is only significant when the target ! architecture is 'V850E2V3' or higher. If hardware floating point instructions are being generated then the C preprocessor symbol ! '__FPU_OK__' is defined, otherwise the symbol '__NO_FPU__' is defined. ! '-mloop' Enables the use of the e3v5 LOOP instruction. The use of this instruction is not enabled by default when the e3v5 architecture is selected because its use is still experimental. ! '-mrh850-abi' ! '-mghs' ! Enables support for the RH850 version of the V850 ABI. This is the default. With this version of the ABI the following rules apply: * Integer sized structures and unions are returned via a memory --- 20822,20949 ---- 3.18.49 V850 Options -------------------- ! These `-m' options are defined for V850 implementations: ! `-mlong-calls' ! `-mno-long-calls' Treat all calls as being far away (near). If calls are assumed to be far away, the compiler always loads the function's address into a register, and calls indirect through the pointer. ! `-mno-ep' ! `-mep' Do not optimize (do optimize) basic blocks that use the same index ! pointer 4 or more times to copy pointer into the `ep' register, and ! use the shorter `sld' and `sst' instructions. The `-mep' option ! is on by default if you optimize. ! `-mno-prolog-function' ! `-mprolog-function' Do not use (do use) external functions to save and restore ! registers at the prologue and epilogue of a function. The ! external functions are slower, but use less code space if more ! than one function saves the same number of registers. The ! `-mprolog-function' option is on by default if you optimize. ! `-mspace' Try to make the code as small as possible. At present, this just ! turns on the `-mep' and `-mprolog-function' options. ! `-mtda=N' Put static or global variables whose size is N bytes or less into ! the tiny data area that register `ep' points to. The tiny data area can hold up to 256 bytes in total (128 bytes for byte references). ! `-msda=N' Put static or global variables whose size is N bytes or less into ! the small data area that register `gp' points to. The small data area can hold up to 64 kilobytes. ! `-mzda=N' Put static or global variables whose size is N bytes or less into the first 32 kilobytes of memory. ! `-mv850' Specify that the target processor is the V850. ! `-mv850e3v5' Specify that the target processor is the V850E3V5. The ! preprocessor constant `__v850e3v5__' is defined if this option is used. ! `-mv850e2v4' Specify that the target processor is the V850E3V5. This is an ! alias for the `-mv850e3v5' option. ! `-mv850e2v3' Specify that the target processor is the V850E2V3. The ! preprocessor constant `__v850e2v3__' is defined if this option is used. ! `-mv850e2' Specify that the target processor is the V850E2. The preprocessor ! constant `__v850e2__' is defined if this option is used. ! `-mv850e1' Specify that the target processor is the V850E1. The preprocessor ! constants `__v850e1__' and `__v850e__' are defined if this option is used. ! `-mv850es' ! Specify that the target processor is the V850ES. This is an alias ! for the `-mv850e1' option. ! `-mv850e' Specify that the target processor is the V850E. The preprocessor ! constant `__v850e__' is defined if this option is used. ! If neither `-mv850' nor `-mv850e' nor `-mv850e1' nor `-mv850e2' ! nor `-mv850e2v3' nor `-mv850e3v5' are defined then a default ! target processor is chosen and the relevant `__v850*__' ! preprocessor constant is defined. ! The preprocessor constants `__v850' and `__v851__' are always defined, regardless of which processor variant is the target. ! `-mdisable-callt' ! `-mno-disable-callt' ! This option suppresses generation of the `CALLT' instruction for the v850e, v850e1, v850e2, v850e2v3 and v850e3v5 flavors of the v850 architecture. ! This option is enabled by default when the RH850 ABI is in use ! (see `-mrh850-abi'), and disabled by default when the GCC ABI is ! in use. If `CALLT' instructions are being generated then the C ! preprocessor symbol `__V850_CALLT__' is defined. ! `-mrelax' ! `-mno-relax' ! Pass on (or do not pass on) the `-mrelax' command-line option to the assembler. ! `-mlong-jumps' ! `-mno-long-jumps' Disable (or re-enable) the generation of PC-relative jump instructions. ! `-msoft-float' ! `-mhard-float' Disable (or re-enable) the generation of hardware floating point instructions. This option is only significant when the target ! architecture is `V850E2V3' or higher. If hardware floating point instructions are being generated then the C preprocessor symbol ! `__FPU_OK__' is defined, otherwise the symbol `__NO_FPU__' is defined. ! `-mloop' Enables the use of the e3v5 LOOP instruction. The use of this instruction is not enabled by default when the e3v5 architecture is selected because its use is still experimental. ! `-mrh850-abi' ! `-mghs' ! Enables support for the RH850 version of the V850 ABI. This is the default. With this version of the ABI the following rules apply: * Integer sized structures and unions are returned via a memory *************** These '-m' options are defined for V850 *** 20842,20862 **** * Functions are aligned to 16-bit boundaries. ! * The '-m8byte-align' command-line option is supported. ! * The '-mdisable-callt' command-line option is enabled by ! default. The '-mno-disable-callt' command-line option is not supported. When this version of the ABI is enabled the C preprocessor symbol ! '__V850_RH850_ABI__' is defined. ! '-mgcc-abi' ! Enables support for the old GCC version of the V850 ABI. With this version of the ABI the following rules apply: * Integer sized structures and unions are returned in register ! 'r10'. * Large structures and unions (more than 8 bytes in size) are passed by reference. --- 20954,20974 ---- * Functions are aligned to 16-bit boundaries. ! * The `-m8byte-align' command-line option is supported. ! * The `-mdisable-callt' command-line option is enabled by ! default. The `-mno-disable-callt' command-line option is not supported. When this version of the ABI is enabled the C preprocessor symbol ! `__V850_RH850_ABI__' is defined. ! `-mgcc-abi' ! Enables support for the old GCC version of the V850 ABI. With this version of the ABI the following rules apply: * Integer sized structures and unions are returned in register ! `r10'. * Large structures and unions (more than 8 bytes in size) are passed by reference. *************** These '-m' options are defined for V850 *** 20864,20913 **** * Functions are aligned to 32-bit boundaries, unless optimizing for size. ! * The '-m8byte-align' command-line option is not supported. ! * The '-mdisable-callt' command-line option is supported but not enabled by default. When this version of the ABI is enabled the C preprocessor symbol ! '__V850_GCC_ABI__' is defined. ! '-m8byte-align' ! '-mno-8byte-align' ! Enables support for 'double' and 'long long' types to be aligned on ! 8-byte boundaries. The default is to restrict the alignment of all ! objects to at most 4-bytes. When '-m8byte-align' is in effect the ! C preprocessor symbol '__V850_8BYTE_ALIGN__' is defined. ! '-mbig-switch' ! Generate code suitable for big switch tables. Use this option only ! if the assembler/linker complain about out of range branches within ! a switch table. ! '-mapp-regs' This option causes r2 and r5 to be used in the code generated by the compiler. This setting is the default. ! '-mno-app-regs' This option causes r2 and r5 to be treated as fixed registers.  File: gcc.info, Node: VAX Options, Next: Visium Options, Prev: V850 Options, Up: Submodel Options 3.18.50 VAX Options ------------------- ! These '-m' options are defined for the VAX: ! '-munix' ! Do not output certain jump instructions ('aobleq' and so on) that the Unix assembler for the VAX cannot handle across long ranges. ! '-mgnu' Do output those jump instructions, on the assumption that the GNU assembler is being used. ! '-mg' Output code for G-format floating-point numbers instead of D-format. --- 20976,21026 ---- * Functions are aligned to 32-bit boundaries, unless optimizing for size. ! * The `-m8byte-align' command-line option is not supported. ! * The `-mdisable-callt' command-line option is supported but not enabled by default. When this version of the ABI is enabled the C preprocessor symbol ! `__V850_GCC_ABI__' is defined. ! `-m8byte-align' ! `-mno-8byte-align' ! Enables support for `double' and `long long' types to be aligned ! on 8-byte boundaries. The default is to restrict the alignment of ! all objects to at most 4-bytes. When `-m8byte-align' is in effect ! the C preprocessor symbol `__V850_8BYTE_ALIGN__' is defined. ! `-mbig-switch' ! Generate code suitable for big switch tables. Use this option ! only if the assembler/linker complain about out of range branches ! within a switch table. ! `-mapp-regs' This option causes r2 and r5 to be used in the code generated by the compiler. This setting is the default. ! `-mno-app-regs' This option causes r2 and r5 to be treated as fixed registers. +  File: gcc.info, Node: VAX Options, Next: Visium Options, Prev: V850 Options, Up: Submodel Options 3.18.50 VAX Options ------------------- ! These `-m' options are defined for the VAX: ! `-munix' ! Do not output certain jump instructions (`aobleq' and so on) that the Unix assembler for the VAX cannot handle across long ranges. ! `-mgnu' Do output those jump instructions, on the assumption that the GNU assembler is being used. ! `-mg' Output code for G-format floating-point numbers instead of D-format. *************** File: gcc.info, Node: Visium Options, *** 20917,20973 **** 3.18.51 Visium Options ---------------------- ! '-mdebug' A program which performs file I/O and is destined to run on an MCM target should be linked with this option. It causes the libraries libc.a and libdebug.a to be linked. The program should be run on the target under the control of the GDB remote debugging stub. ! '-msim' A program which performs file I/O and is destined to run on the simulator should be linked with option. This causes libraries libc.a and libsim.a to be linked. ! '-mfpu' ! '-mhard-float' Generate code containing floating-point instructions. This is the default. ! '-mno-fpu' ! '-msoft-float' Generate code containing library calls for floating-point. ! '-msoft-float' changes the calling convention in the output file; therefore, it is only useful if you compile _all_ of a program with ! this option. In particular, you need to compile 'libgcc.a', the ! library that comes with GCC, with '-msoft-float' in order for this to work. ! '-mcpu=CPU_TYPE' Set the instruction set, register set, and instruction scheduling parameters for machine type CPU_TYPE. Supported values for ! CPU_TYPE are 'mcm', 'gr5' and 'gr6'. ! 'mcm' is a synonym of 'gr5' present for backward compatibility. By default (unless configured otherwise), GCC generates code for the GR5 variant of the Visium architecture. ! With '-mcpu=gr6', GCC generates code for the GR6 variant of the ! Visium architecture. The only difference from GR5 code is that the ! compiler will generate block move instructions. ! '-mtune=CPU_TYPE' Set the instruction scheduling parameters for machine type CPU_TYPE, but do not set the instruction set or register set that ! the option '-mcpu=CPU_TYPE' would. ! '-msv-mode' Generate code for the supervisor mode, where there are no restrictions on the access to general registers. This is the default. ! '-muser-mode' Generate code for the user mode, where the access to some general registers is forbidden: on the GR5, registers r24 to r31 cannot be accessed in this mode; on the GR6, only registers r29 to r31 are --- 21030,21086 ---- 3.18.51 Visium Options ---------------------- ! `-mdebug' A program which performs file I/O and is destined to run on an MCM target should be linked with this option. It causes the libraries libc.a and libdebug.a to be linked. The program should be run on the target under the control of the GDB remote debugging stub. ! `-msim' A program which performs file I/O and is destined to run on the simulator should be linked with option. This causes libraries libc.a and libsim.a to be linked. ! `-mfpu' ! `-mhard-float' Generate code containing floating-point instructions. This is the default. ! `-mno-fpu' ! `-msoft-float' Generate code containing library calls for floating-point. ! `-msoft-float' changes the calling convention in the output file; therefore, it is only useful if you compile _all_ of a program with ! this option. In particular, you need to compile `libgcc.a', the ! library that comes with GCC, with `-msoft-float' in order for this to work. ! `-mcpu=CPU_TYPE' Set the instruction set, register set, and instruction scheduling parameters for machine type CPU_TYPE. Supported values for ! CPU_TYPE are `mcm', `gr5' and `gr6'. ! `mcm' is a synonym of `gr5' present for backward compatibility. By default (unless configured otherwise), GCC generates code for the GR5 variant of the Visium architecture. ! With `-mcpu=gr6', GCC generates code for the GR6 variant of the ! Visium architecture. The only difference from GR5 code is that ! the compiler will generate block move instructions. ! `-mtune=CPU_TYPE' Set the instruction scheduling parameters for machine type CPU_TYPE, but do not set the instruction set or register set that ! the option `-mcpu=CPU_TYPE' would. ! `-msv-mode' Generate code for the supervisor mode, where there are no restrictions on the access to general registers. This is the default. ! `-muser-mode' Generate code for the user mode, where the access to some general registers is forbidden: on the GR5, registers r24 to r31 cannot be accessed in this mode; on the GR6, only registers r29 to r31 are *************** File: gcc.info, Node: VMS Options, Nex *** 20979,21002 **** 3.18.52 VMS Options ------------------- ! These '-m' options are defined for the VMS implementations: ! '-mvms-return-codes' ! Return VMS condition codes from 'main'. The default is to return POSIX-style condition (e.g. error) codes. ! '-mdebug-main=PREFIX' Flag the first routine whose name starts with PREFIX as the main routine for the debugger. ! '-mmalloc64' Default to 64-bit memory allocation routines. ! '-mpointer-size=SIZE' ! Set the default size of pointers. Possible options for SIZE are ! '32' or 'short' for 32 bit pointers, '64' or 'long' for 64 bit ! pointers, and 'no' for supporting only 32 bit pointers. The later ! option disables 'pragma pointer_size'.  File: gcc.info, Node: VxWorks Options, Next: x86 Options, Prev: VMS Options, Up: Submodel Options --- 21092,21115 ---- 3.18.52 VMS Options ------------------- ! These `-m' options are defined for the VMS implementations: ! `-mvms-return-codes' ! Return VMS condition codes from `main'. The default is to return POSIX-style condition (e.g. error) codes. ! `-mdebug-main=PREFIX' Flag the first routine whose name starts with PREFIX as the main routine for the debugger. ! `-mmalloc64' Default to 64-bit memory allocation routines. ! `-mpointer-size=SIZE' ! Set the default size of pointers. Possible options for SIZE are ! `32' or `short' for 32 bit pointers, `64' or `long' for 64 bit ! pointers, and `no' for supporting only 32 bit pointers. The later ! option disables `pragma pointer_size'.  File: gcc.info, Node: VxWorks Options, Next: x86 Options, Prev: VMS Options, Up: Submodel Options *************** The options in this section are defined *** 21008,21035 **** Options specific to the target hardware are listed with the other options for that target. ! '-mrtp' GCC can generate code for both VxWorks kernels and real time processes (RTPs). This option switches from the former to the ! latter. It also defines the preprocessor macro '__RTP__'. ! '-non-static' Link an RTP executable against shared libraries rather than static ! libraries. The options '-static' and '-shared' can also be used ! for RTPs (*note Link Options::); '-static' is the default. ! '-Bstatic' ! '-Bdynamic' These options are passed down to the linker. They are defined for compatibility with Diab. ! '-Xbind-lazy' Enable lazy binding of function calls. This option is equivalent ! to '-Wl,-z,now' and is defined for compatibility with Diab. ! '-Xbind-now' ! Disable lazy binding of function calls. This option is the default ! and is defined for compatibility with Diab.  File: gcc.info, Node: x86 Options, Next: x86 Windows Options, Prev: VxWorks Options, Up: Submodel Options --- 21121,21148 ---- Options specific to the target hardware are listed with the other options for that target. ! `-mrtp' GCC can generate code for both VxWorks kernels and real time processes (RTPs). This option switches from the former to the ! latter. It also defines the preprocessor macro `__RTP__'. ! `-non-static' Link an RTP executable against shared libraries rather than static ! libraries. The options `-static' and `-shared' can also be used ! for RTPs (*note Link Options::); `-static' is the default. ! `-Bstatic' ! `-Bdynamic' These options are passed down to the linker. They are defined for compatibility with Diab. ! `-Xbind-lazy' Enable lazy binding of function calls. This option is equivalent ! to `-Wl,-z,now' and is defined for compatibility with Diab. ! `-Xbind-now' ! Disable lazy binding of function calls. This option is the ! default and is defined for compatibility with Diab.  File: gcc.info, Node: x86 Options, Next: x86 Windows Options, Prev: VxWorks Options, Up: Submodel Options *************** File: gcc.info, Node: x86 Options, Nex *** 21037,21174 **** 3.18.54 x86 Options ------------------- ! These '-m' options are defined for the x86 family of computers. ! '-march=CPU-TYPE' Generate instructions for the machine type CPU-TYPE. In contrast ! to '-mtune=CPU-TYPE', which merely tunes the generated code for the ! specified CPU-TYPE, '-march=CPU-TYPE' allows GCC to generate code ! that may not run at all on processors other than the one indicated. ! Specifying '-march=CPU-TYPE' implies '-mtune=CPU-TYPE'. The choices for CPU-TYPE are: ! 'native' This selects the CPU to generate code for at compilation time by determining the processor type of the compiling machine. ! Using '-march=native' enables all instruction subsets ! supported by the local machine (hence the result might not run ! on different machines). Using '-mtune=native' produces code ! optimized for the local machine under the constraints of the ! selected instruction set. ! 'i386' Original Intel i386 CPU. ! 'i486' Intel i486 CPU. (No scheduling is implemented for this chip.) ! 'i586' ! 'pentium' Intel Pentium CPU with no MMX support. ! 'lakemont' Intel Lakemont MCU, based on Intel Pentium CPU. ! 'pentium-mmx' Intel Pentium MMX CPU, based on Pentium core with MMX instruction set support. ! 'pentiumpro' Intel Pentium Pro CPU. ! 'i686' ! When used with '-march', the Pentium Pro instruction set is used, so the code runs on all i686 family chips. When used ! with '-mtune', it has the same meaning as 'generic'. ! 'pentium2' Intel Pentium II CPU, based on Pentium Pro core with MMX instruction set support. ! 'pentium3' ! 'pentium3m' Intel Pentium III CPU, based on Pentium Pro core with MMX and SSE instruction set support. ! 'pentium-m' Intel Pentium M; low-power version of Intel Pentium III CPU with MMX, SSE and SSE2 instruction set support. Used by Centrino notebooks. ! 'pentium4' ! 'pentium4m' Intel Pentium 4 CPU with MMX, SSE and SSE2 instruction set support. ! 'prescott' Improved version of Intel Pentium 4 CPU with MMX, SSE, SSE2 and SSE3 instruction set support. ! 'nocona' Improved version of Intel Pentium 4 CPU with 64-bit extensions, MMX, SSE, SSE2 and SSE3 instruction set support. ! 'core2' Intel Core 2 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. ! 'nehalem' Intel Nehalem CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2 and POPCNT instruction set support. ! 'westmere' Intel Westmere CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES and PCLMUL instruction set support. ! 'sandybridge' ! Intel Sandy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2, ! SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES and PCLMUL ! instruction set support. ! 'ivybridge' Intel Ivy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES, PCLMUL, FSGSBASE, RDRND and F16C instruction set support. ! 'haswell' Intel Haswell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2 and F16C instruction set support. ! 'broadwell' Intel Broadwell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED, ADCX and PREFETCHW instruction set support. ! 'skylake' Intel Skylake CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED, ADCX, PREFETCHW, CLFLUSHOPT, XSAVEC and XSAVES instruction set support. ! 'bonnell' Intel Bonnell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. ! 'silvermont' Intel Silvermont CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES, PCLMUL and RDRND instruction set support. ! 'knl' ! Intel Knight's Landing CPU with 64-bit extensions, MOVBE, MMX, ! SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, ! AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED, ! ADCX, PREFETCHW, AVX512F, AVX512PF, AVX512ER and AVX512CD ! instruction set support. ! 'skylake-avx512' Intel Skylake Server CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, PKU, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, --- 21150,21287 ---- 3.18.54 x86 Options ------------------- ! These `-m' options are defined for the x86 family of computers. ! `-march=CPU-TYPE' Generate instructions for the machine type CPU-TYPE. In contrast ! to `-mtune=CPU-TYPE', which merely tunes the generated code for ! the specified CPU-TYPE, `-march=CPU-TYPE' allows GCC to generate ! code that may not run at all on processors other than the one ! indicated. Specifying `-march=CPU-TYPE' implies `-mtune=CPU-TYPE'. The choices for CPU-TYPE are: ! `native' This selects the CPU to generate code for at compilation time by determining the processor type of the compiling machine. ! Using `-march=native' enables all instruction subsets ! supported by the local machine (hence the result might not ! run on different machines). Using `-mtune=native' produces ! code optimized for the local machine under the constraints of ! the selected instruction set. ! `i386' Original Intel i386 CPU. ! `i486' Intel i486 CPU. (No scheduling is implemented for this chip.) ! `i586' ! `pentium' Intel Pentium CPU with no MMX support. ! `lakemont' Intel Lakemont MCU, based on Intel Pentium CPU. ! `pentium-mmx' Intel Pentium MMX CPU, based on Pentium core with MMX instruction set support. ! `pentiumpro' Intel Pentium Pro CPU. ! `i686' ! When used with `-march', the Pentium Pro instruction set is used, so the code runs on all i686 family chips. When used ! with `-mtune', it has the same meaning as `generic'. ! `pentium2' Intel Pentium II CPU, based on Pentium Pro core with MMX instruction set support. ! `pentium3' ! `pentium3m' Intel Pentium III CPU, based on Pentium Pro core with MMX and SSE instruction set support. ! `pentium-m' Intel Pentium M; low-power version of Intel Pentium III CPU with MMX, SSE and SSE2 instruction set support. Used by Centrino notebooks. ! `pentium4' ! `pentium4m' Intel Pentium 4 CPU with MMX, SSE and SSE2 instruction set support. ! `prescott' Improved version of Intel Pentium 4 CPU with MMX, SSE, SSE2 and SSE3 instruction set support. ! `nocona' Improved version of Intel Pentium 4 CPU with 64-bit extensions, MMX, SSE, SSE2 and SSE3 instruction set support. ! `core2' Intel Core 2 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. ! `nehalem' Intel Nehalem CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2 and POPCNT instruction set support. ! `westmere' Intel Westmere CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES and PCLMUL instruction set support. ! `sandybridge' ! Intel Sandy Bridge CPU with 64-bit extensions, MMX, SSE, ! SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES and ! PCLMUL instruction set support. ! `ivybridge' Intel Ivy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES, PCLMUL, FSGSBASE, RDRND and F16C instruction set support. ! `haswell' Intel Haswell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2 and F16C instruction set support. ! `broadwell' Intel Broadwell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED, ADCX and PREFETCHW instruction set support. ! `skylake' Intel Skylake CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, RDSEED, ADCX, PREFETCHW, CLFLUSHOPT, XSAVEC and XSAVES instruction set support. ! `bonnell' Intel Bonnell CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3 and SSSE3 instruction set support. ! `silvermont' Intel Silvermont CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES, PCLMUL and RDRND instruction set support. ! `knl' ! Intel Knight's Landing CPU with 64-bit extensions, MOVBE, ! MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, ! AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, ! RDSEED, ADCX, PREFETCHW, AVX512F, AVX512PF, AVX512ER and ! AVX512CD instruction set support. ! `skylake-avx512' Intel Skylake Server CPU with 64-bit extensions, MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, PKU, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C, *************** These '-m' options are defined for the x *** 21176,21303 **** AVX512VL, AVX512BW, AVX512DQ and AVX512CD instruction set support. ! 'k6' AMD K6 CPU with MMX instruction set support. ! 'k6-2' ! 'k6-3' Improved versions of AMD K6 CPU with MMX and 3DNow! instruction set support. ! 'athlon' ! 'athlon-tbird' AMD Athlon CPU with MMX, 3dNOW!, enhanced 3DNow! and SSE prefetch instructions support. ! 'athlon-4' ! 'athlon-xp' ! 'athlon-mp' Improved AMD Athlon CPU with MMX, 3DNow!, enhanced 3DNow! and full SSE instruction set support. ! 'k8' ! 'opteron' ! 'athlon64' ! 'athlon-fx' Processors based on the AMD K8 core with x86-64 instruction set support, including the AMD Opteron, Athlon 64, and Athlon 64 FX processors. (This supersets MMX, SSE, SSE2, 3DNow!, enhanced 3DNow! and 64-bit instruction set extensions.) ! 'k8-sse3' ! 'opteron-sse3' ! 'athlon64-sse3' Improved versions of AMD K8 cores with SSE3 instruction set support. ! 'amdfam10' ! 'barcelona' ! CPUs based on AMD Family 10h cores with x86-64 instruction set ! support. (This supersets MMX, SSE, SSE2, SSE3, SSE4A, 3DNow!, ! enhanced 3DNow!, ABM and 64-bit instruction set extensions.) ! 'bdver1' ! CPUs based on AMD Family 15h cores with x86-64 instruction set ! support. (This supersets FMA4, AVX, XOP, LWP, AES, PCL_MUL, ! CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM ! and 64-bit instruction set extensions.) ! 'bdver2' AMD Family 15h core based CPUs with x86-64 instruction set ! support. (This supersets BMI, TBM, F16C, FMA, FMA4, AVX, XOP, ! LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, ! SSE4.1, SSE4.2, ABM and 64-bit instruction set extensions.) ! 'bdver3' AMD Family 15h core based CPUs with x86-64 instruction set ! support. (This supersets BMI, TBM, F16C, FMA, FMA4, FSGSBASE, ! AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, ! SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit instruction set ! extensions. ! 'bdver4' AMD Family 15h core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, TBM, F16C, FMA, FMA4, ! FSGSBASE, AVX, AVX2, XOP, LWP, AES, PCL_MUL, CX16, MOVBE, MMX, ! SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit ! instruction set extensions. ! 'znver1' AMD Family 17h core based CPUs with x86-64 instruction set ! support. (This supersets BMI, BMI2, F16C, FMA, FSGSBASE, AVX, ! AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCL_MUL, CX16, ! MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ! ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, and 64-bit instruction set extensions. ! 'btver1' ! CPUs based on AMD Family 14h cores with x86-64 instruction set ! support. (This supersets MMX, SSE, SSE2, SSE3, SSSE3, SSE4A, ! CX16, ABM and 64-bit instruction set extensions.) ! 'btver2' ! CPUs based on AMD Family 16h cores with x86-64 instruction set ! support. This includes MOVBE, F16C, BMI, AVX, PCL_MUL, AES, ! SSE4.2, SSE4.1, CX16, ABM, SSE4A, SSSE3, SSE3, SSE2, SSE, MMX ! and 64-bit instruction set extensions. ! 'winchip-c6' IDT WinChip C6 CPU, dealt in same way as i486 with additional MMX instruction set support. ! 'winchip2' IDT WinChip 2 CPU, dealt in same way as i486 with additional ! MMX and 3DNow! instruction set support. ! 'c3' VIA C3 CPU with MMX and 3DNow! instruction set support. (No scheduling is implemented for this chip.) ! 'c3-2' VIA C3-2 (Nehemiah/C5XL) CPU with MMX and SSE instruction set support. (No scheduling is implemented for this chip.) ! 'geode' AMD Geode embedded processor with MMX and 3DNow! instruction set support. ! '-mtune=CPU-TYPE' Tune to CPU-TYPE everything applicable about the generated code, except for the ABI and the set of available instructions. While ! picking a specific CPU-TYPE schedules things appropriately for that ! particular chip, the compiler does not generate any code that cannot run on the default machine type unless you use a ! '-march=CPU-TYPE' option. For example, if GCC is configured for ! i686-pc-linux-gnu then '-mtune=pentium4' generates code that is tuned for Pentium 4 but still runs on i686 machines. ! The choices for CPU-TYPE are the same as for '-march'. In ! addition, '-mtune' supports 2 extra choices for CPU-TYPE: ! 'generic' Produce code optimized for the most common IA32/AMD64/EM64T processors. If you know the CPU on which your code will run, ! then you should use the corresponding '-mtune' or '-march' ! option instead of '-mtune=generic'. But, if you do not know ! exactly what CPU users of your application will have, then you ! should use this option. As new processors are deployed in the marketplace, the behavior of this option will change. Therefore, if you --- 21289,21421 ---- AVX512VL, AVX512BW, AVX512DQ and AVX512CD instruction set support. ! `k6' AMD K6 CPU with MMX instruction set support. ! `k6-2' ! `k6-3' Improved versions of AMD K6 CPU with MMX and 3DNow! instruction set support. ! `athlon' ! `athlon-tbird' AMD Athlon CPU with MMX, 3dNOW!, enhanced 3DNow! and SSE prefetch instructions support. ! `athlon-4' ! `athlon-xp' ! `athlon-mp' Improved AMD Athlon CPU with MMX, 3DNow!, enhanced 3DNow! and full SSE instruction set support. ! `k8' ! `opteron' ! `athlon64' ! `athlon-fx' Processors based on the AMD K8 core with x86-64 instruction set support, including the AMD Opteron, Athlon 64, and Athlon 64 FX processors. (This supersets MMX, SSE, SSE2, 3DNow!, enhanced 3DNow! and 64-bit instruction set extensions.) ! `k8-sse3' ! `opteron-sse3' ! `athlon64-sse3' Improved versions of AMD K8 cores with SSE3 instruction set support. ! `amdfam10' ! `barcelona' ! CPUs based on AMD Family 10h cores with x86-64 instruction ! set support. (This supersets MMX, SSE, SSE2, SSE3, SSE4A, ! 3DNow!, enhanced 3DNow!, ABM and 64-bit instruction set ! extensions.) ! `bdver1' ! CPUs based on AMD Family 15h cores with x86-64 instruction ! set support. (This supersets FMA4, AVX, XOP, LWP, AES, ! PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, ! SSE4.2, ABM and 64-bit instruction set extensions.) ! ! `bdver2' AMD Family 15h core based CPUs with x86-64 instruction set ! support. (This supersets BMI, TBM, F16C, FMA, FMA4, AVX, ! XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, SSE3, SSE4A, ! SSSE3, SSE4.1, SSE4.2, ABM and 64-bit instruction set ! extensions.) ! ! `bdver3' AMD Family 15h core based CPUs with x86-64 instruction set ! support. (This supersets BMI, TBM, F16C, FMA, FMA4, ! FSGSBASE, AVX, XOP, LWP, AES, PCL_MUL, CX16, MMX, SSE, SSE2, ! SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and 64-bit ! instruction set extensions. ! ! `bdver4' AMD Family 15h core based CPUs with x86-64 instruction set support. (This supersets BMI, BMI2, TBM, F16C, FMA, FMA4, ! FSGSBASE, AVX, AVX2, XOP, LWP, AES, PCL_MUL, CX16, MOVBE, ! MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, SSE4.2, ABM and ! 64-bit instruction set extensions. ! `znver1' AMD Family 17h core based CPUs with x86-64 instruction set ! support. (This supersets BMI, BMI2, F16C, FMA, FSGSBASE, ! AVX, AVX2, ADCX, RDSEED, MWAITX, SHA, CLZERO, AES, PCL_MUL, ! CX16, MOVBE, MMX, SSE, SSE2, SSE3, SSE4A, SSSE3, SSE4.1, ! SSE4.2, ABM, XSAVEC, XSAVES, CLFLUSHOPT, POPCNT, and 64-bit instruction set extensions. ! `btver1' ! CPUs based on AMD Family 14h cores with x86-64 instruction ! set support. (This supersets MMX, SSE, SSE2, SSE3, SSSE3, ! SSE4A, CX16, ABM and 64-bit instruction set extensions.) ! `btver2' ! CPUs based on AMD Family 16h cores with x86-64 instruction ! set support. This includes MOVBE, F16C, BMI, AVX, PCL_MUL, ! AES, SSE4.2, SSE4.1, CX16, ABM, SSE4A, SSSE3, SSE3, SSE2, ! SSE, MMX and 64-bit instruction set extensions. ! `winchip-c6' IDT WinChip C6 CPU, dealt in same way as i486 with additional MMX instruction set support. ! `winchip2' IDT WinChip 2 CPU, dealt in same way as i486 with additional ! MMX and 3DNow! instruction set support. ! `c3' VIA C3 CPU with MMX and 3DNow! instruction set support. (No scheduling is implemented for this chip.) ! `c3-2' VIA C3-2 (Nehemiah/C5XL) CPU with MMX and SSE instruction set support. (No scheduling is implemented for this chip.) ! `geode' AMD Geode embedded processor with MMX and 3DNow! instruction set support. ! `-mtune=CPU-TYPE' Tune to CPU-TYPE everything applicable about the generated code, except for the ABI and the set of available instructions. While ! picking a specific CPU-TYPE schedules things appropriately for ! that particular chip, the compiler does not generate any code that cannot run on the default machine type unless you use a ! `-march=CPU-TYPE' option. For example, if GCC is configured for ! i686-pc-linux-gnu then `-mtune=pentium4' generates code that is tuned for Pentium 4 but still runs on i686 machines. ! The choices for CPU-TYPE are the same as for `-march'. In ! addition, `-mtune' supports 2 extra choices for CPU-TYPE: ! `generic' Produce code optimized for the most common IA32/AMD64/EM64T processors. If you know the CPU on which your code will run, ! then you should use the corresponding `-mtune' or `-march' ! option instead of `-mtune=generic'. But, if you do not know ! exactly what CPU users of your application will have, then ! you should use this option. As new processors are deployed in the marketplace, the behavior of this option will change. Therefore, if you *************** These '-m' options are defined for the x *** 21305,21322 **** by this option will change to reflect the processors that are most common at the time that version of GCC is released. ! There is no '-march=generic' option because '-march' indicates ! the instruction set the compiler can use, and there is no ! generic instruction set applicable to all processors. In ! contrast, '-mtune' indicates the processor (or, in this case, ! collection of processors) for which the code is optimized. ! 'intel' Produce code optimized for the most current Intel processors, ! which are Haswell and Silvermont for this version of GCC. If you know the CPU on which your code will run, then you should ! use the corresponding '-mtune' or '-march' option instead of ! '-mtune=intel'. But, if you want your application performs better on both Haswell and Silvermont, then you should use this option. --- 21423,21441 ---- by this option will change to reflect the processors that are most common at the time that version of GCC is released. ! There is no `-march=generic' option because `-march' ! indicates the instruction set the compiler can use, and there ! is no generic instruction set applicable to all processors. ! In contrast, `-mtune' indicates the processor (or, in this ! case, collection of processors) for which the code is ! optimized. ! `intel' Produce code optimized for the most current Intel processors, ! which are Haswell and Silvermont for this version of GCC. If you know the CPU on which your code will run, then you should ! use the corresponding `-mtune' or `-march' option instead of ! `-mtune=intel'. But, if you want your application performs better on both Haswell and Silvermont, then you should use this option. *************** These '-m' options are defined for the x *** 21326,21381 **** by this option will change to reflect the most current Intel processors at the time that version of GCC is released. ! There is no '-march=intel' option because '-march' indicates the instruction set the compiler can use, and there is no common instruction set applicable to all processors. In ! contrast, '-mtune' indicates the processor (or, in this case, collection of processors) for which the code is optimized. ! '-mcpu=CPU-TYPE' ! A deprecated synonym for '-mtune'. ! '-mfpmath=UNIT' Generate floating-point arithmetic for selected unit UNIT. The choices for UNIT are: ! '387' ! Use the standard 387 floating-point coprocessor present on the ! majority of chips and emulated otherwise. Code compiled with ! this option runs almost everywhere. The temporary results are ! computed in 80-bit precision instead of the precision ! specified by the type, resulting in slightly different results ! compared to most of other chips. See '-ffloat-store' for more ! detailed description. This is the default choice for x86-32 targets. ! 'sse' Use scalar floating-point instructions present in the SSE ! instruction set. This instruction set is supported by Pentium ! III and newer chips, and in the AMD line by Athlon-4, Athlon ! XP and Athlon MP chips. The earlier version of the SSE instruction set supports only single-precision arithmetic, thus the double and extended-precision arithmetic are still done using 387. A later version, present only in Pentium 4 and AMD x86-64 chips, supports double-precision arithmetic too. ! For the x86-32 compiler, you must use '-march=CPU-TYPE', ! '-msse' or '-msse2' switches to enable SSE extensions and make ! this option effective. For the x86-64 compiler, these extensions are enabled by default. The resulting code should be considerably faster in the ! majority of cases and avoid the numerical instability problems ! of 387 code, but may break some existing code that expects ! temporaries to be 80 bits. This is the default choice for the x86-64 compiler. ! 'sse,387' ! 'sse+387' ! 'both' Attempt to utilize both instruction sets at once. This effectively doubles the amount of available registers, and on chips with separate execution units for 387 and SSE the --- 21445,21500 ---- by this option will change to reflect the most current Intel processors at the time that version of GCC is released. ! There is no `-march=intel' option because `-march' indicates the instruction set the compiler can use, and there is no common instruction set applicable to all processors. In ! contrast, `-mtune' indicates the processor (or, in this case, collection of processors) for which the code is optimized. ! `-mcpu=CPU-TYPE' ! A deprecated synonym for `-mtune'. ! `-mfpmath=UNIT' Generate floating-point arithmetic for selected unit UNIT. The choices for UNIT are: ! `387' ! Use the standard 387 floating-point coprocessor present on ! the majority of chips and emulated otherwise. Code compiled ! with this option runs almost everywhere. The temporary ! results are computed in 80-bit precision instead of the ! precision specified by the type, resulting in slightly ! different results compared to most of other chips. See ! `-ffloat-store' for more detailed description. This is the default choice for x86-32 targets. ! `sse' Use scalar floating-point instructions present in the SSE ! instruction set. This instruction set is supported by ! Pentium III and newer chips, and in the AMD line by Athlon-4, ! Athlon XP and Athlon MP chips. The earlier version of the SSE instruction set supports only single-precision arithmetic, thus the double and extended-precision arithmetic are still done using 387. A later version, present only in Pentium 4 and AMD x86-64 chips, supports double-precision arithmetic too. ! For the x86-32 compiler, you must use `-march=CPU-TYPE', ! `-msse' or `-msse2' switches to enable SSE extensions and ! make this option effective. For the x86-64 compiler, these extensions are enabled by default. The resulting code should be considerably faster in the ! majority of cases and avoid the numerical instability ! problems of 387 code, but may break some existing code that ! expects temporaries to be 80 bits. This is the default choice for the x86-64 compiler. ! `sse,387' ! `sse+387' ! `both' Attempt to utilize both instruction sets at once. This effectively doubles the amount of available registers, and on chips with separate execution units for 387 and SSE the *************** These '-m' options are defined for the x *** 21384,21568 **** not model separate functional units well, resulting in unstable performance. ! '-masm=DIALECT' Output assembly instructions using selected DIALECT. Also affects ! which dialect is used for basic 'asm' (*note Basic Asm::) and ! extended 'asm' (*note Extended Asm::). Supported choices (in ! dialect order) are 'att' or 'intel'. The default is 'att'. Darwin ! does not support 'intel'. ! '-mieee-fp' ! '-mno-ieee-fp' Control whether or not the compiler uses IEEE floating-point comparisons. These correctly handle the case where the result of a comparison is unordered. ! '-msoft-float' Generate output containing library calls for floating point. *Warning:* the requisite libraries are not part of GCC. Normally ! the facilities of the machine's usual C compiler are used, but this ! can't be done directly in cross-compilation. You must make your ! own arrangements to provide suitable library functions for cross-compilation. On machines where a function returns floating-point results in the 80387 register stack, some floating-point opcodes may be emitted ! even if '-msoft-float' is used. ! '-mno-fp-ret-in-387' Do not use the FPU registers for return values of functions. The usual calling convention has functions return values of types ! 'float' and 'double' in an FPU register, even if there is no FPU. The idea is that the operating system should emulate an FPU. ! The option '-mno-fp-ret-in-387' causes such values to be returned in ordinary CPU registers instead. ! '-mno-fancy-math-387' ! Some 387 emulators do not support the 'sin', 'cos' and 'sqrt' instructions for the 387. Specify this option to avoid generating those instructions. This option is the default on OpenBSD and ! NetBSD. This option is overridden when '-march' indicates that the ! target CPU always has an FPU and so the instruction does not need ! emulation. These instructions are not generated unless you also ! use the '-funsafe-math-optimizations' switch. ! '-malign-double' ! '-mno-align-double' ! Control whether GCC aligns 'double', 'long double', and 'long long' ! variables on a two-word boundary or a one-word boundary. Aligning ! 'double' variables on a two-word boundary produces code that runs ! somewhat faster on a Pentium at the expense of more memory. ! On x86-64, '-malign-double' is enabled by default. ! *Warning:* if you use the '-malign-double' switch, structures containing the above types are aligned differently than the published application binary interface specifications for the x86-32 and are not binary compatible with structures in code compiled without that switch. ! '-m96bit-long-double' ! '-m128bit-long-double' ! These switches control the size of 'long double' type. The x86-32 application binary interface specifies the size to be 96 bits, so ! '-m96bit-long-double' is the default in 32-bit mode. ! Modern architectures (Pentium and newer) prefer 'long double' to be ! aligned to an 8- or 16-byte boundary. In arrays or structures conforming to the ABI, this is not possible. So specifying ! '-m128bit-long-double' aligns 'long double' to a 16-byte boundary ! by padding the 'long double' with an additional 32-bit zero. ! In the x86-64 compiler, '-m128bit-long-double' is the default ! choice as its ABI specifies that 'long double' is aligned on 16-byte boundary. Notice that neither of these options enable any extra precision ! over the x87 standard of 80 bits for a 'long double'. *Warning:* if you override the default value for your target ABI, ! this changes the size of structures and arrays containing 'long double' variables, as well as modifying the function calling ! convention for functions taking 'long double'. Hence they are not binary-compatible with code compiled without that switch. ! '-mlong-double-64' ! '-mlong-double-80' ! '-mlong-double-128' ! These switches control the size of 'long double' type. A size of ! 64 bits makes the 'long double' type equivalent to the 'double' ! type. This is the default for 32-bit Bionic C library. A size of ! 128 bits makes the 'long double' type equivalent to the ! '__float128' type. This is the default for 64-bit Bionic C ! library. *Warning:* if you override the default value for your target ABI, ! this changes the size of structures and arrays containing 'long double' variables, as well as modifying the function calling ! convention for functions taking 'long double'. Hence they are not binary-compatible with code compiled without that switch. ! '-malign-data=TYPE' Control how GCC aligns variables. Supported values for TYPE are ! 'compat' uses increased alignment value compatible uses GCC 4.8 and ! earlier, 'abi' uses alignment value as specified by the psABI, and ! 'cacheline' uses increased alignment value to match the cache line ! size. 'compat' is the default. ! '-mlarge-data-threshold=THRESHOLD' ! When '-mcmodel=medium' is specified, data objects larger than ! THRESHOLD are placed in the large data section. This value must be ! the same across all objects linked into the binary, and defaults to ! 65535. ! '-mrtd' Use a different function-calling convention, in which functions ! that take a fixed number of arguments return with the 'ret NUM' instruction, which pops their arguments while returning. This saves one instruction in the caller since there is no need to pop the arguments there. You can specify that an individual function is called with this ! calling sequence with the function attribute 'stdcall'. You can ! also override the '-mrtd' option by using the function attribute ! 'cdecl'. *Note Function Attributes::. *Warning:* this calling convention is incompatible with the one normally used on Unix, so you cannot use it if you need to call libraries compiled with the Unix compiler. Also, you must provide function prototypes for all functions that ! take variable numbers of arguments (including 'printf'); otherwise incorrect code is generated for calls to those functions. In addition, seriously incorrect code results if you call a function with too many arguments. (Normally, extra arguments are harmlessly ignored.) ! '-mregparm=NUM' Control how many registers are used to pass integer arguments. By default, no registers are used to pass arguments, and at most 3 registers can be used. You can control this behavior for a ! specific function by using the function attribute 'regparm'. *Note ! Function Attributes::. *Warning:* if you use this switch, and NUM is nonzero, then you must build all modules with the same value, including any libraries. This includes the system libraries and startup modules. ! '-msseregparm' Use SSE register passing conventions for float and double arguments and return values. You can control this behavior for a specific ! function by using the function attribute 'sseregparm'. *Note Function Attributes::. *Warning:* if you use this switch then you must build all modules with the same value, including any libraries. This includes the system libraries and startup modules. ! '-mvect8-ret-in-mem' Return 8-byte vectors in memory instead of MMX registers. This is the default on Solaris 8 and 9 and VxWorks to match the ABI of the Sun Studio compilers until version 12. Later compiler versions ! (starting with Studio 12 Update 1) follow the ABI used by other x86 ! targets, which is the default on Solaris 10 and later. _Only_ use ! this option if you need to remain compatible with existing code ! produced by those previous compiler versions or older versions of ! GCC. ! ! '-mpc32' ! '-mpc64' ! '-mpc80' Set 80387 floating-point precision to 32, 64 or 80 bits. When ! '-mpc32' is specified, the significands of results of floating-point operations are rounded to 24 bits (single ! precision); '-mpc64' rounds the significands of results of floating-point operations to 53 bits (double precision) and ! '-mpc80' rounds the significands of results of floating-point operations to 64 bits (extended double precision), which is the default. When this option is used, floating-point operations in higher precisions are not available to the programmer without --- 21503,21686 ---- not model separate functional units well, resulting in unstable performance. ! `-masm=DIALECT' Output assembly instructions using selected DIALECT. Also affects ! which dialect is used for basic `asm' (*note Basic Asm::) and ! extended `asm' (*note Extended Asm::). Supported choices (in ! dialect order) are `att' or `intel'. The default is `att'. Darwin ! does not support `intel'. ! `-mieee-fp' ! `-mno-ieee-fp' Control whether or not the compiler uses IEEE floating-point comparisons. These correctly handle the case where the result of a comparison is unordered. ! `-msoft-float' Generate output containing library calls for floating point. *Warning:* the requisite libraries are not part of GCC. Normally ! the facilities of the machine's usual C compiler are used, but ! this can't be done directly in cross-compilation. You must make ! your own arrangements to provide suitable library functions for cross-compilation. On machines where a function returns floating-point results in the 80387 register stack, some floating-point opcodes may be emitted ! even if `-msoft-float' is used. ! `-mno-fp-ret-in-387' Do not use the FPU registers for return values of functions. The usual calling convention has functions return values of types ! `float' and `double' in an FPU register, even if there is no FPU. The idea is that the operating system should emulate an FPU. ! The option `-mno-fp-ret-in-387' causes such values to be returned in ordinary CPU registers instead. ! `-mno-fancy-math-387' ! Some 387 emulators do not support the `sin', `cos' and `sqrt' instructions for the 387. Specify this option to avoid generating those instructions. This option is the default on OpenBSD and ! NetBSD. This option is overridden when `-march' indicates that ! the target CPU always has an FPU and so the instruction does not ! need emulation. These instructions are not generated unless you ! also use the `-funsafe-math-optimizations' switch. ! `-malign-double' ! `-mno-align-double' ! Control whether GCC aligns `double', `long double', and `long ! long' variables on a two-word boundary or a one-word boundary. ! Aligning `double' variables on a two-word boundary produces code ! that runs somewhat faster on a Pentium at the expense of more ! memory. ! On x86-64, `-malign-double' is enabled by default. ! *Warning:* if you use the `-malign-double' switch, structures containing the above types are aligned differently than the published application binary interface specifications for the x86-32 and are not binary compatible with structures in code compiled without that switch. ! `-m96bit-long-double' ! `-m128bit-long-double' ! These switches control the size of `long double' type. The x86-32 application binary interface specifies the size to be 96 bits, so ! `-m96bit-long-double' is the default in 32-bit mode. ! Modern architectures (Pentium and newer) prefer `long double' to ! be aligned to an 8- or 16-byte boundary. In arrays or structures conforming to the ABI, this is not possible. So specifying ! `-m128bit-long-double' aligns `long double' to a 16-byte boundary ! by padding the `long double' with an additional 32-bit zero. ! In the x86-64 compiler, `-m128bit-long-double' is the default ! choice as its ABI specifies that `long double' is aligned on 16-byte boundary. Notice that neither of these options enable any extra precision ! over the x87 standard of 80 bits for a `long double'. *Warning:* if you override the default value for your target ABI, ! this changes the size of structures and arrays containing `long double' variables, as well as modifying the function calling ! convention for functions taking `long double'. Hence they are not binary-compatible with code compiled without that switch. ! `-mlong-double-64' ! `-mlong-double-80' ! `-mlong-double-128' ! These switches control the size of `long double' type. A size of ! 64 bits makes the `long double' type equivalent to the `double' ! type. This is the default for 32-bit Bionic C library. A size of ! 128 bits makes the `long double' type equivalent to the ! `__float128' type. This is the default for 64-bit Bionic C library. *Warning:* if you override the default value for your target ABI, ! this changes the size of structures and arrays containing `long double' variables, as well as modifying the function calling ! convention for functions taking `long double'. Hence they are not binary-compatible with code compiled without that switch. ! `-malign-data=TYPE' Control how GCC aligns variables. Supported values for TYPE are ! `compat' uses increased alignment value compatible uses GCC 4.8 ! and earlier, `abi' uses alignment value as specified by the psABI, ! and `cacheline' uses increased alignment value to match the cache ! line size. `compat' is the default. ! `-mlarge-data-threshold=THRESHOLD' ! When `-mcmodel=medium' is specified, data objects larger than ! THRESHOLD are placed in the large data section. This value must ! be the same across all objects linked into the binary, and ! defaults to 65535. ! `-mrtd' Use a different function-calling convention, in which functions ! that take a fixed number of arguments return with the `ret NUM' instruction, which pops their arguments while returning. This saves one instruction in the caller since there is no need to pop the arguments there. You can specify that an individual function is called with this ! calling sequence with the function attribute `stdcall'. You can ! also override the `-mrtd' option by using the function attribute ! `cdecl'. *Note Function Attributes::. *Warning:* this calling convention is incompatible with the one normally used on Unix, so you cannot use it if you need to call libraries compiled with the Unix compiler. Also, you must provide function prototypes for all functions that ! take variable numbers of arguments (including `printf'); otherwise incorrect code is generated for calls to those functions. In addition, seriously incorrect code results if you call a function with too many arguments. (Normally, extra arguments are harmlessly ignored.) ! `-mregparm=NUM' Control how many registers are used to pass integer arguments. By default, no registers are used to pass arguments, and at most 3 registers can be used. You can control this behavior for a ! specific function by using the function attribute `regparm'. ! *Note Function Attributes::. *Warning:* if you use this switch, and NUM is nonzero, then you must build all modules with the same value, including any libraries. This includes the system libraries and startup modules. ! `-msseregparm' Use SSE register passing conventions for float and double arguments and return values. You can control this behavior for a specific ! function by using the function attribute `sseregparm'. *Note Function Attributes::. *Warning:* if you use this switch then you must build all modules with the same value, including any libraries. This includes the system libraries and startup modules. ! `-mvect8-ret-in-mem' Return 8-byte vectors in memory instead of MMX registers. This is the default on Solaris 8 and 9 and VxWorks to match the ABI of the Sun Studio compilers until version 12. Later compiler versions ! (starting with Studio 12 Update 1) follow the ABI used by other ! x86 targets, which is the default on Solaris 10 and later. _Only_ ! use this option if you need to remain compatible with existing ! code produced by those previous compiler versions or older ! versions of GCC. + `-mpc32' + `-mpc64' + `-mpc80' Set 80387 floating-point precision to 32, 64 or 80 bits. When ! `-mpc32' is specified, the significands of results of floating-point operations are rounded to 24 bits (single ! precision); `-mpc64' rounds the significands of results of floating-point operations to 53 bits (double precision) and ! `-mpc80' rounds the significands of results of floating-point operations to 64 bits (extended double precision), which is the default. When this option is used, floating-point operations in higher precisions are not available to the programmer without *************** These '-m' options are defined for the x *** 21570,21598 **** Setting the rounding of floating-point operations to less than the default 80 bits can speed some programs by 2% or more. Note that ! some mathematical libraries assume that extended-precision (80-bit) ! floating-point operations are enabled by default; routines in such ! libraries could suffer significant loss of accuracy, typically ! through so-called "catastrophic cancellation", when this option is ! used to set the precision to less than extended precision. ! '-mstackrealign' ! Realign the stack at entry. On the x86, the '-mstackrealign' option generates an alternate prologue and epilogue that realigns ! the run-time stack if necessary. This supports mixing legacy codes ! that keep 4-byte stack alignment with modern codes that keep 16-byte stack alignment for SSE compatibility. See also the ! attribute 'force_align_arg_pointer', applicable to individual functions. ! '-mpreferred-stack-boundary=NUM' Attempt to keep the stack boundary aligned to a 2 raised to NUM ! byte boundary. If '-mpreferred-stack-boundary' is not specified, the default is 4 (16 bytes or 128 bits). *Warning:* When generating code for the x86-64 architecture with ! SSE extensions disabled, '-mpreferred-stack-boundary=3' can be used ! to keep the stack boundary aligned to 8 byte boundary. Since x86-64 ABI require 16 byte stack alignment, this is ABI incompatible and intended to be used in controlled environment where stack space is important limitation. This option leads to --- 21688,21717 ---- Setting the rounding of floating-point operations to less than the default 80 bits can speed some programs by 2% or more. Note that ! some mathematical libraries assume that extended-precision ! (80-bit) floating-point operations are enabled by default; ! routines in such libraries could suffer significant loss of ! accuracy, typically through so-called "catastrophic cancellation", ! when this option is used to set the precision to less than ! extended precision. ! `-mstackrealign' ! Realign the stack at entry. On the x86, the `-mstackrealign' option generates an alternate prologue and epilogue that realigns ! the run-time stack if necessary. This supports mixing legacy ! codes that keep 4-byte stack alignment with modern codes that keep 16-byte stack alignment for SSE compatibility. See also the ! attribute `force_align_arg_pointer', applicable to individual functions. ! `-mpreferred-stack-boundary=NUM' Attempt to keep the stack boundary aligned to a 2 raised to NUM ! byte boundary. If `-mpreferred-stack-boundary' is not specified, the default is 4 (16 bytes or 128 bits). *Warning:* When generating code for the x86-64 architecture with ! SSE extensions disabled, `-mpreferred-stack-boundary=3' can be ! used to keep the stack boundary aligned to 8 byte boundary. Since x86-64 ABI require 16 byte stack alignment, this is ABI incompatible and intended to be used in controlled environment where stack space is important limitation. This option leads to *************** These '-m' options are defined for the x *** 21602,21731 **** misaligned memory access traps. In addition, variable arguments are handled incorrectly for 16 byte aligned objects (including x87 long double and __int128), leading to wrong results. You must ! build all modules with '-mpreferred-stack-boundary=3', including any libraries. This includes the system libraries and startup modules. ! '-mincoming-stack-boundary=NUM' Assume the incoming stack is aligned to a 2 raised to NUM byte ! boundary. If '-mincoming-stack-boundary' is not specified, the one ! specified by '-mpreferred-stack-boundary' is used. ! On Pentium and Pentium Pro, 'double' and 'long double' values ! should be aligned to an 8-byte boundary (see '-malign-double') or ! suffer significant run time performance penalties. On Pentium III, ! the Streaming SIMD Extension (SSE) data type '__m128' may not work ! properly if it is not 16-byte aligned. To ensure proper alignment of this values on the stack, the stack ! boundary must be as aligned as that required by any value stored on ! the stack. Further, every function must be generated such that it ! keeps the stack aligned. Thus calling a function compiled with a ! higher preferred stack boundary from a function compiled with a ! lower preferred stack boundary most likely misaligns the stack. It ! is recommended that libraries that use callbacks always use the default setting. This extra alignment does consume extra stack space, and generally increases code size. Code that is sensitive to stack space usage, such as embedded systems and operating system kernels, may want to ! reduce the preferred alignment to '-mpreferred-stack-boundary=2'. ! '-mmmx' ! '-msse' ! '-msse2' ! '-msse3' ! '-mssse3' ! '-msse4' ! '-msse4a' ! '-msse4.1' ! '-msse4.2' ! '-mavx' ! '-mavx2' ! '-mavx512f' ! '-mavx512pf' ! '-mavx512er' ! '-mavx512cd' ! '-mavx512vl' ! '-mavx512bw' ! '-mavx512dq' ! '-mavx512ifma' ! '-mavx512vbmi' ! '-msha' ! '-maes' ! '-mpclmul' ! '-mclfushopt' ! '-mfsgsbase' ! '-mrdrnd' ! '-mf16c' ! '-mfma' ! '-mfma4' ! '-mprefetchwt1' ! '-mxop' ! '-mlwp' ! '-m3dnow' ! '-mpopcnt' ! '-mabm' ! '-mbmi' ! '-mbmi2' ! '-mlzcnt' ! '-mfxsr' ! '-mxsave' ! '-mxsaveopt' ! '-mxsavec' ! '-mxsaves' ! '-mrtm' ! '-mtbm' ! '-mmpx' ! '-mmwaitx' ! '-mclzero' ! '-mpku' These switches enable the use of instructions in the MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, AVX, AVX2, AVX512F, AVX512PF, AVX512ER, AVX512CD, SHA, AES, PCLMUL, FSGSBASE, RDRND, F16C, FMA, SSE4A, FMA4, XOP, LWP, ABM, AVX512VL, AVX512BW, AVX512DQ, AVX512IFMA AVX512VBMI, BMI, BMI2, FXSR, XSAVE, XSAVEOPT, LZCNT, RTM, MPX, ! MWAITX, PKU or 3DNow! extended instruction sets. Each has a ! corresponding '-mno-' option to disable use of these instructions. These extensions are also available as built-in functions: see *note x86 Built-in Functions::, for details of the functions enabled and disabled by these switches. To generate SSE/SSE2 instructions automatically from floating-point ! code (as opposed to 387 instructions), see '-mfpmath=sse'. ! GCC depresses SSEx instructions when '-mavx' is used. Instead, it generates new AVX instructions or AVX equivalence for all SSEx instructions when needed. These options enable GCC to use these extended instructions in ! generated code, even without '-mfpmath=sse'. Applications that perform run-time CPU detection must compile separate files for each supported architecture, using the appropriate flags. In particular, the file containing the CPU detection code should be compiled without these options. ! '-mdump-tune-features' This option instructs GCC to dump the names of the x86 performance ! tuning features and default settings. The names can be used in ! '-mtune-ctrl=FEATURE-LIST'. ! '-mtune-ctrl=FEATURE-LIST' ! This option is used to do fine grain control of x86 code generation ! features. FEATURE-LIST is a comma separated list of FEATURE names. ! See also '-mdump-tune-features'. When specified, the FEATURE is ! turned on if it is not preceded with '^', otherwise, it is turned ! off. '-mtune-ctrl=FEATURE-LIST' is intended to be used by GCC ! developers. Using it may lead to code paths not covered by testing ! and can potentially result in compiler ICEs or runtime errors. ! '-mno-default' ! This option instructs GCC to turn off all tunable features. See ! also '-mtune-ctrl=FEATURE-LIST' and '-mdump-tune-features'. ! '-mcld' ! This option instructs GCC to emit a 'cld' instruction in the prologue of functions that use string instructions. String instructions depend on the DF flag to select between autoincrement or autodecrement mode. While the ABI specifies the DF flag to be --- 21721,21851 ---- misaligned memory access traps. In addition, variable arguments are handled incorrectly for 16 byte aligned objects (including x87 long double and __int128), leading to wrong results. You must ! build all modules with `-mpreferred-stack-boundary=3', including any libraries. This includes the system libraries and startup modules. ! `-mincoming-stack-boundary=NUM' Assume the incoming stack is aligned to a 2 raised to NUM byte ! boundary. If `-mincoming-stack-boundary' is not specified, the ! one specified by `-mpreferred-stack-boundary' is used. ! On Pentium and Pentium Pro, `double' and `long double' values ! should be aligned to an 8-byte boundary (see `-malign-double') or ! suffer significant run time performance penalties. On Pentium ! III, the Streaming SIMD Extension (SSE) data type `__m128' may not ! work properly if it is not 16-byte aligned. To ensure proper alignment of this values on the stack, the stack ! boundary must be as aligned as that required by any value stored ! on the stack. Further, every function must be generated such that ! it keeps the stack aligned. Thus calling a function compiled with ! a higher preferred stack boundary from a function compiled with a ! lower preferred stack boundary most likely misaligns the stack. ! It is recommended that libraries that use callbacks always use the default setting. This extra alignment does consume extra stack space, and generally increases code size. Code that is sensitive to stack space usage, such as embedded systems and operating system kernels, may want to ! reduce the preferred alignment to `-mpreferred-stack-boundary=2'. ! `-mmmx' ! `-msse' ! `-msse2' ! `-msse3' ! `-mssse3' ! `-msse4' ! `-msse4a' ! `-msse4.1' ! `-msse4.2' ! `-mavx' ! `-mavx2' ! `-mavx512f' ! `-mavx512pf' ! `-mavx512er' ! `-mavx512cd' ! `-mavx512vl' ! `-mavx512bw' ! `-mavx512dq' ! `-mavx512ifma' ! `-mavx512vbmi' ! `-msha' ! `-maes' ! `-mpclmul' ! `-mclfushopt' ! `-mfsgsbase' ! `-mrdrnd' ! `-mf16c' ! `-mfma' ! `-mfma4' ! `-mprefetchwt1' ! `-mxop' ! `-mlwp' ! `-m3dnow' ! `-mpopcnt' ! `-mabm' ! `-mbmi' ! `-mbmi2' ! `-mlzcnt' ! `-mfxsr' ! `-mxsave' ! `-mxsaveopt' ! `-mxsavec' ! `-mxsaves' ! `-mrtm' ! `-mtbm' ! `-mmpx' ! `-mmwaitx' ! `-mclzero' ! `-mpku' These switches enable the use of instructions in the MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, AVX, AVX2, AVX512F, AVX512PF, AVX512ER, AVX512CD, SHA, AES, PCLMUL, FSGSBASE, RDRND, F16C, FMA, SSE4A, FMA4, XOP, LWP, ABM, AVX512VL, AVX512BW, AVX512DQ, AVX512IFMA AVX512VBMI, BMI, BMI2, FXSR, XSAVE, XSAVEOPT, LZCNT, RTM, MPX, ! MWAITX, PKU or 3DNow! extended instruction sets. Each has a ! corresponding `-mno-' option to disable use of these instructions. These extensions are also available as built-in functions: see *note x86 Built-in Functions::, for details of the functions enabled and disabled by these switches. To generate SSE/SSE2 instructions automatically from floating-point ! code (as opposed to 387 instructions), see `-mfpmath=sse'. ! GCC depresses SSEx instructions when `-mavx' is used. Instead, it generates new AVX instructions or AVX equivalence for all SSEx instructions when needed. These options enable GCC to use these extended instructions in ! generated code, even without `-mfpmath=sse'. Applications that perform run-time CPU detection must compile separate files for each supported architecture, using the appropriate flags. In particular, the file containing the CPU detection code should be compiled without these options. ! `-mdump-tune-features' This option instructs GCC to dump the names of the x86 performance ! tuning features and default settings. The names can be used in ! `-mtune-ctrl=FEATURE-LIST'. ! `-mtune-ctrl=FEATURE-LIST' ! This option is used to do fine grain control of x86 code ! generation features. FEATURE-LIST is a comma separated list of ! FEATURE names. See also `-mdump-tune-features'. When specified, ! the FEATURE is turned on if it is not preceded with `^', ! otherwise, it is turned off. `-mtune-ctrl=FEATURE-LIST' is ! intended to be used by GCC developers. Using it may lead to code ! paths not covered by testing and can potentially result in ! compiler ICEs or runtime errors. ! `-mno-default' ! This option instructs GCC to turn off all tunable features. See ! also `-mtune-ctrl=FEATURE-LIST' and `-mdump-tune-features'. ! `-mcld' ! This option instructs GCC to emit a `cld' instruction in the prologue of functions that use string instructions. String instructions depend on the DF flag to select between autoincrement or autodecrement mode. While the ABI specifies the DF flag to be *************** These '-m' options are defined for the x *** 21734,21906 **** dispatchers. The exception handler can be invoked with the DF flag set, which leads to wrong direction mode when string instructions are used. This option can be enabled by default on 32-bit x86 ! targets by configuring GCC with the '--enable-cld' configure ! option. Generation of 'cld' instructions can be suppressed with ! the '-mno-cld' compiler option in this case. ! '-mvzeroupper' ! This option instructs GCC to emit a 'vzeroupper' instruction before ! a transfer of control flow out of the function to minimize the AVX ! to SSE transition penalty as well as remove unnecessary 'zeroupper' ! intrinsics. ! '-mprefer-avx128' This option instructs GCC to use 128-bit AVX instructions instead of 256-bit AVX instructions in the auto-vectorizer. ! '-mcx16' ! This option enables GCC to generate 'CMPXCHG16B' instructions. ! 'CMPXCHG16B' allows for atomic operations on 128-bit double ! quadword (or oword) data types. This is useful for high-resolution ! counters that can be updated by multiple processors (or cores). ! This instruction is generated as part of atomic built-in functions: ! see *note __sync Builtins:: or *note __atomic Builtins:: for ! details. ! '-msahf' ! This option enables generation of 'SAHF' instructions in 64-bit code. Early Intel Pentium 4 CPUs with Intel 64 support, prior to the introduction of Pentium 4 G1 step in December 2005, lacked the ! 'LAHF' and 'SAHF' instructions which are supported by AMD64. These ! are load and store instructions, respectively, for certain status ! flags. In 64-bit mode, the 'SAHF' instruction is used to optimize ! 'fmod', 'drem', and 'remainder' built-in functions; see *note Other ! Builtins:: for details. ! '-mmovbe' ! This option enables use of the 'movbe' instruction to implement ! '__builtin_bswap32' and '__builtin_bswap64'. ! '-mcrc32' ! This option enables built-in functions '__builtin_ia32_crc32qi', ! '__builtin_ia32_crc32hi', '__builtin_ia32_crc32si' and ! '__builtin_ia32_crc32di' to generate the 'crc32' machine instruction. ! '-mrecip' ! This option enables use of 'RCPSS' and 'RSQRTSS' instructions (and ! their vectorized variants 'RCPPS' and 'RSQRTPS') with an additional ! Newton-Raphson step to increase precision instead of 'DIVSS' and ! 'SQRTSS' (and their vectorized variants) for single-precision ! floating-point arguments. These instructions are generated only ! when '-funsafe-math-optimizations' is enabled together with ! '-ffinite-math-only' and '-fno-trapping-math'. Note that while the ! throughput of the sequence is higher than the throughput of the ! non-reciprocal instruction, the precision of the sequence can be ! decreased by up to 2 ulp (i.e. the inverse of 1.0 equals ! 0.99999994). ! Note that GCC implements '1.0f/sqrtf(X)' in terms of 'RSQRTSS' (or ! 'RSQRTPS') already with '-ffast-math' (or the above option ! combination), and doesn't need '-mrecip'. Also note that GCC emits the above sequence with additional Newton-Raphson step for vectorized single-float division and ! vectorized 'sqrtf(X)' already with '-ffast-math' (or the above ! option combination), and doesn't need '-mrecip'. ! '-mrecip=OPT' This option controls which reciprocal estimate instructions may be used. OPT is a comma-separated list of options, which may be ! preceded by a '!' to invert the option: ! 'all' Enable all estimate instructions. ! 'default' ! Enable the default instructions, equivalent to '-mrecip'. ! 'none' ! Disable all estimate instructions, equivalent to '-mno-recip'. ! 'div' Enable the approximation for scalar division. ! 'vec-div' Enable the approximation for vectorized division. ! 'sqrt' Enable the approximation for scalar square root. ! 'vec-sqrt' Enable the approximation for vectorized square root. ! So, for example, '-mrecip=all,!sqrt' enables all of the reciprocal approximations, except for square root. ! '-mveclibabi=TYPE' Specifies the ABI type to use for vectorizing intrinsics using an ! external library. Supported values for TYPE are 'svml' for the ! Intel short vector math library and 'acml' for the AMD math core ! library. To use this option, both '-ftree-vectorize' and ! '-funsafe-math-optimizations' have to be enabled, and an SVML or ACML ABI-compatible library must be specified at link time. ! GCC currently emits calls to 'vmldExp2', 'vmldLn2', 'vmldLog102', ! 'vmldLog102', 'vmldPow2', 'vmldTanh2', 'vmldTan2', 'vmldAtan2', ! 'vmldAtanh2', 'vmldCbrt2', 'vmldSinh2', 'vmldSin2', 'vmldAsinh2', ! 'vmldAsin2', 'vmldCosh2', 'vmldCos2', 'vmldAcosh2', 'vmldAcos2', ! 'vmlsExp4', 'vmlsLn4', 'vmlsLog104', 'vmlsLog104', 'vmlsPow4', ! 'vmlsTanh4', 'vmlsTan4', 'vmlsAtan4', 'vmlsAtanh4', 'vmlsCbrt4', ! 'vmlsSinh4', 'vmlsSin4', 'vmlsAsinh4', 'vmlsAsin4', 'vmlsCosh4', ! 'vmlsCos4', 'vmlsAcosh4' and 'vmlsAcos4' for corresponding function ! type when '-mveclibabi=svml' is used, and '__vrd2_sin', ! '__vrd2_cos', '__vrd2_exp', '__vrd2_log', '__vrd2_log2', ! '__vrd2_log10', '__vrs4_sinf', '__vrs4_cosf', '__vrs4_expf', ! '__vrs4_logf', '__vrs4_log2f', '__vrs4_log10f' and '__vrs4_powf' ! for the corresponding function type when '-mveclibabi=acml' is used. ! '-mabi=NAME' Generate code for the specified calling convention. Permissible ! values are 'sysv' for the ABI used on GNU/Linux and other systems, ! and 'ms' for the Microsoft ABI. The default is to use the Microsoft ! ABI when targeting Microsoft Windows and the SysV ABI on all other ! systems. You can control this behavior for specific functions by ! using the function attributes 'ms_abi' and 'sysv_abi'. *Note ! Function Attributes::. ! '-mtls-dialect=TYPE' ! Generate code to access thread-local storage using the 'gnu' or ! 'gnu2' conventions. 'gnu' is the conservative default; 'gnu2' is more efficient, but it may add compile- and run-time requirements that cannot be satisfied on all systems. ! '-mpush-args' ! '-mno-push-args' Use PUSH operations to store outgoing parameters. This method is ! shorter and usually equally fast as method using SUB/MOV operations ! and is enabled by default. In some cases disabling it may improve ! performance because of improved scheduling and reduced dependencies. ! '-maccumulate-outgoing-args' If enabled, the maximum amount of space required for outgoing arguments is computed in the function prologue. This is faster on most modern CPUs because of reduced dependencies, improved scheduling and reduced stack usage when the preferred stack boundary is not equal to 2. The drawback is a notable increase in ! code size. This switch implies '-mno-push-args'. ! ! '-mthreads' ! Support thread-safe exception handling on MinGW. Programs that rely ! on thread-safe exception handling must compile and link all code ! with the '-mthreads' option. When compiling, '-mthreads' defines ! '-D_MT'; when linking, it links in a special thread helper library ! '-lmingwthrd' which cleans up per-thread exception-handling data. ! '-mms-bitfields' ! '-mno-ms-bitfields' Enable/disable bit-field layout compatible with the native Microsoft Windows compiler. ! If 'packed' is used on a structure, or if bit-fields are used, it may be that the Microsoft ABI lays out the structure differently than the way GCC normally does. Particularly when moving packed data between functions compiled with GCC and the native Microsoft ! compiler (either via function call or as data in a file), it may be ! necessary to access either format. This option is enabled by default for Microsoft Windows targets. This behavior can also be controlled locally by use of variable or --- 21854,22026 ---- dispatchers. The exception handler can be invoked with the DF flag set, which leads to wrong direction mode when string instructions are used. This option can be enabled by default on 32-bit x86 ! targets by configuring GCC with the `--enable-cld' configure ! option. Generation of `cld' instructions can be suppressed with ! the `-mno-cld' compiler option in this case. ! `-mvzeroupper' ! This option instructs GCC to emit a `vzeroupper' instruction ! before a transfer of control flow out of the function to minimize ! the AVX to SSE transition penalty as well as remove unnecessary ! `zeroupper' intrinsics. ! `-mprefer-avx128' This option instructs GCC to use 128-bit AVX instructions instead of 256-bit AVX instructions in the auto-vectorizer. ! `-mcx16' ! This option enables GCC to generate `CMPXCHG16B' instructions. ! `CMPXCHG16B' allows for atomic operations on 128-bit double ! quadword (or oword) data types. This is useful for ! high-resolution counters that can be updated by multiple ! processors (or cores). This instruction is generated as part of ! atomic built-in functions: see *note __sync Builtins:: or *note ! __atomic Builtins:: for details. ! `-msahf' ! This option enables generation of `SAHF' instructions in 64-bit code. Early Intel Pentium 4 CPUs with Intel 64 support, prior to the introduction of Pentium 4 G1 step in December 2005, lacked the ! `LAHF' and `SAHF' instructions which are supported by AMD64. ! These are load and store instructions, respectively, for certain ! status flags. In 64-bit mode, the `SAHF' instruction is used to ! optimize `fmod', `drem', and `remainder' built-in functions; see ! *note Other Builtins:: for details. ! `-mmovbe' ! This option enables use of the `movbe' instruction to implement ! `__builtin_bswap32' and `__builtin_bswap64'. ! `-mcrc32' ! This option enables built-in functions `__builtin_ia32_crc32qi', ! `__builtin_ia32_crc32hi', `__builtin_ia32_crc32si' and ! `__builtin_ia32_crc32di' to generate the `crc32' machine instruction. ! `-mrecip' ! This option enables use of `RCPSS' and `RSQRTSS' instructions (and ! their vectorized variants `RCPPS' and `RSQRTPS') with an ! additional Newton-Raphson step to increase precision instead of ! `DIVSS' and `SQRTSS' (and their vectorized variants) for ! single-precision floating-point arguments. These instructions are ! generated only when `-funsafe-math-optimizations' is enabled ! together with `-ffinite-math-only' and `-fno-trapping-math'. Note ! that while the throughput of the sequence is higher than the ! throughput of the non-reciprocal instruction, the precision of the ! sequence can be decreased by up to 2 ulp (i.e. the inverse of 1.0 ! equals 0.99999994). ! Note that GCC implements `1.0f/sqrtf(X)' in terms of `RSQRTSS' (or ! `RSQRTPS') already with `-ffast-math' (or the above option ! combination), and doesn't need `-mrecip'. Also note that GCC emits the above sequence with additional Newton-Raphson step for vectorized single-float division and ! vectorized `sqrtf(X)' already with `-ffast-math' (or the above ! option combination), and doesn't need `-mrecip'. ! `-mrecip=OPT' This option controls which reciprocal estimate instructions may be used. OPT is a comma-separated list of options, which may be ! preceded by a `!' to invert the option: ! `all' Enable all estimate instructions. ! `default' ! Enable the default instructions, equivalent to `-mrecip'. ! `none' ! Disable all estimate instructions, equivalent to `-mno-recip'. ! `div' Enable the approximation for scalar division. ! `vec-div' Enable the approximation for vectorized division. ! `sqrt' Enable the approximation for scalar square root. ! `vec-sqrt' Enable the approximation for vectorized square root. ! So, for example, `-mrecip=all,!sqrt' enables all of the reciprocal approximations, except for square root. ! `-mveclibabi=TYPE' Specifies the ABI type to use for vectorizing intrinsics using an ! external library. Supported values for TYPE are `svml' for the ! Intel short vector math library and `acml' for the AMD math core ! library. To use this option, both `-ftree-vectorize' and ! `-funsafe-math-optimizations' have to be enabled, and an SVML or ACML ABI-compatible library must be specified at link time. ! GCC currently emits calls to `vmldExp2', `vmldLn2', `vmldLog102', ! `vmldLog102', `vmldPow2', `vmldTanh2', `vmldTan2', `vmldAtan2', ! `vmldAtanh2', `vmldCbrt2', `vmldSinh2', `vmldSin2', `vmldAsinh2', ! `vmldAsin2', `vmldCosh2', `vmldCos2', `vmldAcosh2', `vmldAcos2', ! `vmlsExp4', `vmlsLn4', `vmlsLog104', `vmlsLog104', `vmlsPow4', ! `vmlsTanh4', `vmlsTan4', `vmlsAtan4', `vmlsAtanh4', `vmlsCbrt4', ! `vmlsSinh4', `vmlsSin4', `vmlsAsinh4', `vmlsAsin4', `vmlsCosh4', ! `vmlsCos4', `vmlsAcosh4' and `vmlsAcos4' for corresponding ! function type when `-mveclibabi=svml' is used, and `__vrd2_sin', ! `__vrd2_cos', `__vrd2_exp', `__vrd2_log', `__vrd2_log2', ! `__vrd2_log10', `__vrs4_sinf', `__vrs4_cosf', `__vrs4_expf', ! `__vrs4_logf', `__vrs4_log2f', `__vrs4_log10f' and `__vrs4_powf' ! for the corresponding function type when `-mveclibabi=acml' is used. ! `-mabi=NAME' Generate code for the specified calling convention. Permissible ! values are `sysv' for the ABI used on GNU/Linux and other systems, ! and `ms' for the Microsoft ABI. The default is to use the ! Microsoft ABI when targeting Microsoft Windows and the SysV ABI on ! all other systems. You can control this behavior for specific ! functions by using the function attributes `ms_abi' and `sysv_abi'. ! *Note Function Attributes::. ! `-mtls-dialect=TYPE' ! Generate code to access thread-local storage using the `gnu' or ! `gnu2' conventions. `gnu' is the conservative default; `gnu2' is more efficient, but it may add compile- and run-time requirements that cannot be satisfied on all systems. ! `-mpush-args' ! `-mno-push-args' Use PUSH operations to store outgoing parameters. This method is ! shorter and usually equally fast as method using SUB/MOV ! operations and is enabled by default. In some cases disabling it ! may improve performance because of improved scheduling and reduced dependencies. ! `-maccumulate-outgoing-args' If enabled, the maximum amount of space required for outgoing arguments is computed in the function prologue. This is faster on most modern CPUs because of reduced dependencies, improved scheduling and reduced stack usage when the preferred stack boundary is not equal to 2. The drawback is a notable increase in ! code size. This switch implies `-mno-push-args'. ! `-mthreads' ! Support thread-safe exception handling on MinGW. Programs that ! rely on thread-safe exception handling must compile and link all ! code with the `-mthreads' option. When compiling, `-mthreads' ! defines `-D_MT'; when linking, it links in a special thread helper ! library `-lmingwthrd' which cleans up per-thread ! exception-handling data. + `-mms-bitfields' + `-mno-ms-bitfields' Enable/disable bit-field layout compatible with the native Microsoft Windows compiler. ! If `packed' is used on a structure, or if bit-fields are used, it may be that the Microsoft ABI lays out the structure differently than the way GCC normally does. Particularly when moving packed data between functions compiled with GCC and the native Microsoft ! compiler (either via function call or as data in a file), it may ! be necessary to access either format. This option is enabled by default for Microsoft Windows targets. This behavior can also be controlled locally by use of variable or *************** These '-m' options are defined for the x *** 21916,21937 **** which they are declared: the first member has the lowest memory address and the last member the highest. ! 2. Every data object has an alignment requirement. The alignment ! requirement for all data except structures, unions, and arrays ! is either the size of the object or the current packing size ! (specified with either the 'aligned' attribute or the 'pack' ! pragma), whichever is less. For structures, unions, and ! arrays, the alignment requirement is the largest alignment ! requirement of its members. Every object is allocated an ! offset so that: offset % alignment_requirement == 0 ! 3. Adjacent bit-fields are packed into the same 1-, 2-, or 4-byte ! allocation unit if the integral types are the same size and if ! the next bit-field fits into the current allocation unit ! without crossing the boundary imposed by the common alignment ! requirements of the bit-fields. MSVC interprets zero-length bit-fields in the following ways: --- 22036,22057 ---- which they are declared: the first member has the lowest memory address and the last member the highest. ! 2. Every data object has an alignment requirement. The ! alignment requirement for all data except structures, unions, ! and arrays is either the size of the object or the current ! packing size (specified with either the `aligned' attribute ! or the `pack' pragma), whichever is less. For structures, ! unions, and arrays, the alignment requirement is the largest ! alignment requirement of its members. Every object is ! allocated an offset so that: offset % alignment_requirement == 0 ! 3. Adjacent bit-fields are packed into the same 1-, 2-, or ! 4-byte allocation unit if the integral types are the same ! size and if the next bit-field fits into the current ! allocation unit without crossing the boundary imposed by the ! common alignment requirements of the bit-fields. MSVC interprets zero-length bit-fields in the following ways: *************** These '-m' options are defined for the x *** 21947,21959 **** unsigned long bf_2 : 12; } t1; ! The size of 't1' is 8 bytes with the zero-length bit-field. ! If the zero-length bit-field were removed, 't1''s size would be 4 bytes. 2. If a zero-length bit-field is inserted after a bit-field, ! 'foo', and the alignment of the zero-length bit-field is ! greater than the member that follows it, 'bar', 'bar' is aligned as the type of the zero-length bit-field. For example: --- 22067,22079 ---- unsigned long bf_2 : 12; } t1; ! The size of `t1' is 8 bytes with the zero-length bit-field. ! If the zero-length bit-field were removed, `t1''s size would be 4 bytes. 2. If a zero-length bit-field is inserted after a bit-field, ! `foo', and the alignment of the zero-length bit-field is ! greater than the member that follows it, `bar', `bar' is aligned as the type of the zero-length bit-field. For example: *************** These '-m' options are defined for the x *** 21972,21980 **** double bar; } t3; ! For 't2', 'bar' is placed at offset 2, rather than offset 1. ! Accordingly, the size of 't2' is 4. For 't3', the zero-length ! bit-field does not affect the alignment of 'bar' or, as a result, the size of the structure. Taking this into account, it is important to note the --- 22092,22100 ---- double bar; } t3; ! For `t2', `bar' is placed at offset 2, rather than offset 1. ! Accordingly, the size of `t2' is 4. For `t3', the zero-length ! bit-field does not affect the alignment of `bar' or, as a result, the size of the structure. Taking this into account, it is important to note the *************** These '-m' options are defined for the x *** 21982,21988 **** 1. If a zero-length bit-field follows a normal bit-field, the type of the zero-length bit-field may affect the ! alignment of the structure as whole. For example, 't2' has a size of 4 bytes, since the zero-length bit-field follows a normal bit-field, and is of type short. --- 22102,22108 ---- 1. If a zero-length bit-field follows a normal bit-field, the type of the zero-length bit-field may affect the ! alignment of the structure as whole. For example, `t2' has a size of 4 bytes, since the zero-length bit-field follows a normal bit-field, and is of type short. *************** These '-m' options are defined for the x *** 21996,22002 **** long : 0; } t4; ! Here, 't4' takes up 4 bytes. 3. Zero-length bit-fields following non-bit-field members are ignored: --- 22116,22122 ---- long : 0; } t4; ! Here, `t4' takes up 4 bytes. 3. Zero-length bit-fields following non-bit-field members are ignored: *************** These '-m' options are defined for the x *** 22008,22207 **** char bar; } t5; ! Here, 't5' takes up 2 bytes. ! '-mno-align-stringops' Do not align the destination of inlined string operations. This switch reduces code size and improves performance in case the destination is already aligned, but GCC doesn't know about it. ! '-minline-all-stringops' By default GCC inlines string operations only when the destination is known to be aligned to least a 4-byte boundary. This enables more inlining and increases code size, but may improve performance ! of code that depends on fast 'memcpy', 'strlen', and 'memset' for short lengths. ! '-minline-stringops-dynamically' For string operations of unknown size, use run-time checks with inline code for small blocks and a library call for large blocks. ! '-mstringop-strategy=ALG' Override the internal decision heuristic for the particular algorithm to use for inlining string operations. The allowed values for ALG are: ! 'rep_byte' ! 'rep_4byte' ! 'rep_8byte' ! Expand using i386 'rep' prefix of the specified size. ! 'byte_loop' ! 'loop' ! 'unrolled_loop' Expand into an inline loop. ! 'libcall' Always use a library call. ! '-mmemcpy-strategy=STRATEGY' Override the internal decision heuristic to decide if ! '__builtin_memcpy' should be inlined and what inline algorithm to ! use when the expected size of the copy operation is known. ! STRATEGY is a comma-separated list of ALG:MAX_SIZE:DEST_ALIGN ! triplets. ALG is specified in '-mstringop-strategy', MAX_SIZE ! specifies the max byte size with which inline algorithm ALG is ! allowed. For the last triplet, the MAX_SIZE must be '-1'. The ! MAX_SIZE of the triplets in the list must be specified in ! increasing order. The minimal byte size for ALG is '0' for the ! first triplet and 'MAX_SIZE + 1' of the preceding range. ! '-mmemset-strategy=STRATEGY' ! The option is similar to '-mmemcpy-strategy=' except that it is to ! control '__builtin_memset' expansion. ! '-momit-leaf-frame-pointer' Don't keep the frame pointer in a register for leaf functions. This avoids the instructions to save, set up, and restore frame pointers and makes an extra register available in leaf functions. ! The option '-fomit-leaf-frame-pointer' removes the frame pointer for leaf functions, which might make debugging harder. ! '-mtls-direct-seg-refs' ! '-mno-tls-direct-seg-refs' Controls whether TLS variables may be accessed with offsets from ! the TLS segment register ('%gs' for 32-bit, '%fs' for 64-bit), or whether the thread base pointer must be added. Whether or not this is valid depends on the operating system, and whether it maps the segment to cover the entire TLS area. For systems that use the GNU C Library, the default is on. ! '-msse2avx' ! '-mno-sse2avx' Specify that the assembler should encode SSE instructions with VEX ! prefix. The option '-mavx' turns this on by default. ! '-mfentry' ! '-mno-fentry' ! If profiling is active ('-pg'), put the profiling counter call before the prologue. Note: On x86 architectures the attribute ! 'ms_hook_prologue' isn't possible at the moment for '-mfentry' and ! '-pg'. ! '-mrecord-mcount' ! '-mno-record-mcount' ! If profiling is active ('-pg'), generate a __mcount_loc section ! that contains pointers to each profiling call. This is useful for automatically patching and out calls. ! '-mnop-mcount' ! '-mno-nop-mcount' ! If profiling is active ('-pg'), generate the calls to the profiling ! functions as nops. This is useful when they should be patched in ! later dynamically. This is likely only useful together with ! '-mrecord-mcount'. ! '-mskip-rax-setup' ! '-mno-skip-rax-setup' When generating code for the x86-64 architecture with SSE ! extensions disabled, '-mskip-rax-setup' can be used to skip setting ! up RAX register when there are no variable arguments passed in ! vector registers. ! *Warning:* Since RAX register is used to avoid unnecessarily saving ! vector registers on stack when passing variable arguments, the ! impacts of this option are callees may waste some stack space, misbehave or jump to a random location. GCC 4.4 or newer don't have those issues, regardless the RAX register value. ! '-m8bit-idiv' ! '-mno-8bit-idiv' On some processors, like Intel Atom, 8-bit unsigned integer divide is much faster than 32-bit/64-bit integer divide. This option generates a run-time check. If both dividend and divisor are within range of 0 to 255, 8-bit unsigned integer divide is used instead of 32-bit/64-bit integer divide. ! '-mavx256-split-unaligned-load' ! '-mavx256-split-unaligned-store' Split 32-byte AVX unaligned load and store. ! '-mstack-protector-guard=GUARD' Generate stack protection code using canary at GUARD. Supported ! locations are 'global' for global canary or 'tls' for per-thread ! canary in the TLS block (the default). This option has effect only ! when '-fstack-protector' or '-fstack-protector-all' is specified. ! '-mmitigate-rop' Try to avoid generating code sequences that contain unintended ! return opcodes, to mitigate against certain forms of attack. At ! the moment, this option is limited in what it can do and should not ! be relied on to provide serious protection. ! These '-m' switches are supported in addition to the above on x86-64 processors in 64-bit environments. ! '-m32' ! '-m64' ! '-mx32' ! '-m16' ! '-miamcu' Generate code for a 16-bit, 32-bit or 64-bit environment. The ! '-m32' option sets 'int', 'long', and pointer types to 32 bits, and generates code that runs on any i386 system. ! The '-m64' option sets 'int' to 32 bits and 'long' and pointer types to 64 bits, and generates code for the x86-64 architecture. ! For Darwin only the '-m64' option also turns off the '-fno-pic' and ! '-mdynamic-no-pic' options. ! The '-mx32' option sets 'int', 'long', and pointer types to 32 bits, and generates code for the x86-64 architecture. ! The '-m16' option is the same as '-m32', except for that it outputs ! the '.code16gcc' assembly directive at the beginning of the ! assembly output so that the binary can run in 16-bit mode. ! The '-miamcu' option generates code which conforms to Intel MCU ! psABI. It requires the '-m32' option to be turned on. ! '-mno-red-zone' ! Do not use a so-called "red zone" for x86-64 code. The red zone is ! mandated by the x86-64 ABI; it is a 128-byte area beyond the location of the stack pointer that is not modified by signal or interrupt handlers and therefore can be used for temporary data ! without adjusting the stack pointer. The flag '-mno-red-zone' disables this red zone. ! '-mcmodel=small' ! Generate code for the small code model: the program and its symbols ! must be linked in the lower 2 GB of the address space. Pointers ! are 64 bits. Programs can be statically or dynamically linked. ! This is the default code model. ! '-mcmodel=kernel' Generate code for the kernel code model. The kernel runs in the negative 2 GB of the address space. This model has to be used for Linux kernel code. ! '-mcmodel=medium' Generate code for the medium model: the program is linked in the lower 2 GB of the address space. Small symbols are also placed ! there. Symbols with sizes larger than '-mlarge-data-threshold' are ! put into large data or BSS sections and can be located above 2GB. ! Programs can be statically or dynamically linked. ! '-mcmodel=large' Generate code for the large model. This model makes no assumptions about addresses and sizes of sections. ! '-maddress-mode=long' Generate code for long address mode. This is only supported for 64-bit and x32 environments. It is the default address mode for 64-bit environments. ! '-maddress-mode=short' Generate code for short address mode. This is only supported for 32-bit and x32 environments. It is the default address mode for 32-bit and x32 environments. --- 22128,22329 ---- char bar; } t5; ! Here, `t5' takes up 2 bytes. ! `-mno-align-stringops' Do not align the destination of inlined string operations. This switch reduces code size and improves performance in case the destination is already aligned, but GCC doesn't know about it. ! `-minline-all-stringops' By default GCC inlines string operations only when the destination is known to be aligned to least a 4-byte boundary. This enables more inlining and increases code size, but may improve performance ! of code that depends on fast `memcpy', `strlen', and `memset' for short lengths. ! `-minline-stringops-dynamically' For string operations of unknown size, use run-time checks with inline code for small blocks and a library call for large blocks. ! `-mstringop-strategy=ALG' Override the internal decision heuristic for the particular algorithm to use for inlining string operations. The allowed values for ALG are: ! `rep_byte' ! `rep_4byte' ! `rep_8byte' ! Expand using i386 `rep' prefix of the specified size. ! `byte_loop' ! `loop' ! `unrolled_loop' Expand into an inline loop. ! `libcall' Always use a library call. ! `-mmemcpy-strategy=STRATEGY' Override the internal decision heuristic to decide if ! `__builtin_memcpy' should be inlined and what inline algorithm to ! use when the expected size of the copy operation is known. STRATEGY ! is a comma-separated list of ALG:MAX_SIZE:DEST_ALIGN triplets. ! ALG is specified in `-mstringop-strategy', MAX_SIZE specifies the ! max byte size with which inline algorithm ALG is allowed. For the ! last triplet, the MAX_SIZE must be `-1'. The MAX_SIZE of the ! triplets in the list must be specified in increasing order. The ! minimal byte size for ALG is `0' for the first triplet and ! `MAX_SIZE + 1' of the preceding range. ! `-mmemset-strategy=STRATEGY' ! The option is similar to `-mmemcpy-strategy=' except that it is to ! control `__builtin_memset' expansion. ! `-momit-leaf-frame-pointer' Don't keep the frame pointer in a register for leaf functions. This avoids the instructions to save, set up, and restore frame pointers and makes an extra register available in leaf functions. ! The option `-fomit-leaf-frame-pointer' removes the frame pointer for leaf functions, which might make debugging harder. ! `-mtls-direct-seg-refs' ! `-mno-tls-direct-seg-refs' Controls whether TLS variables may be accessed with offsets from ! the TLS segment register (`%gs' for 32-bit, `%fs' for 64-bit), or whether the thread base pointer must be added. Whether or not this is valid depends on the operating system, and whether it maps the segment to cover the entire TLS area. For systems that use the GNU C Library, the default is on. ! `-msse2avx' ! `-mno-sse2avx' Specify that the assembler should encode SSE instructions with VEX ! prefix. The option `-mavx' turns this on by default. ! `-mfentry' ! `-mno-fentry' ! If profiling is active (`-pg'), put the profiling counter call before the prologue. Note: On x86 architectures the attribute ! `ms_hook_prologue' isn't possible at the moment for `-mfentry' and ! `-pg'. ! `-mrecord-mcount' ! `-mno-record-mcount' ! If profiling is active (`-pg'), generate a __mcount_loc section ! that contains pointers to each profiling call. This is useful for automatically patching and out calls. ! `-mnop-mcount' ! `-mno-nop-mcount' ! If profiling is active (`-pg'), generate the calls to the ! profiling functions as nops. This is useful when they should be ! patched in later dynamically. This is likely only useful together ! with `-mrecord-mcount'. ! `-mskip-rax-setup' ! `-mno-skip-rax-setup' When generating code for the x86-64 architecture with SSE ! extensions disabled, `-mskip-rax-setup' can be used to skip ! setting up RAX register when there are no variable arguments ! passed in vector registers. ! *Warning:* Since RAX register is used to avoid unnecessarily ! saving vector registers on stack when passing variable arguments, ! the impacts of this option are callees may waste some stack space, misbehave or jump to a random location. GCC 4.4 or newer don't have those issues, regardless the RAX register value. ! `-m8bit-idiv' ! `-mno-8bit-idiv' On some processors, like Intel Atom, 8-bit unsigned integer divide is much faster than 32-bit/64-bit integer divide. This option generates a run-time check. If both dividend and divisor are within range of 0 to 255, 8-bit unsigned integer divide is used instead of 32-bit/64-bit integer divide. ! `-mavx256-split-unaligned-load' ! `-mavx256-split-unaligned-store' Split 32-byte AVX unaligned load and store. ! `-mstack-protector-guard=GUARD' Generate stack protection code using canary at GUARD. Supported ! locations are `global' for global canary or `tls' for per-thread ! canary in the TLS block (the default). This option has effect ! only when `-fstack-protector' or `-fstack-protector-all' is ! specified. ! `-mmitigate-rop' Try to avoid generating code sequences that contain unintended ! return opcodes, to mitigate against certain forms of attack. At ! the moment, this option is limited in what it can do and should ! not be relied on to provide serious protection. ! ! These `-m' switches are supported in addition to the above on x86-64 processors in 64-bit environments. ! `-m32' ! `-m64' ! `-mx32' ! `-m16' ! `-miamcu' Generate code for a 16-bit, 32-bit or 64-bit environment. The ! `-m32' option sets `int', `long', and pointer types to 32 bits, and generates code that runs on any i386 system. ! The `-m64' option sets `int' to 32 bits and `long' and pointer types to 64 bits, and generates code for the x86-64 architecture. ! For Darwin only the `-m64' option also turns off the `-fno-pic' ! and `-mdynamic-no-pic' options. ! The `-mx32' option sets `int', `long', and pointer types to 32 bits, and generates code for the x86-64 architecture. ! The `-m16' option is the same as `-m32', except for that it ! outputs the `.code16gcc' assembly directive at the beginning of ! the assembly output so that the binary can run in 16-bit mode. ! The `-miamcu' option generates code which conforms to Intel MCU ! psABI. It requires the `-m32' option to be turned on. ! `-mno-red-zone' ! Do not use a so-called "red zone" for x86-64 code. The red zone ! is mandated by the x86-64 ABI; it is a 128-byte area beyond the location of the stack pointer that is not modified by signal or interrupt handlers and therefore can be used for temporary data ! without adjusting the stack pointer. The flag `-mno-red-zone' disables this red zone. ! `-mcmodel=small' ! Generate code for the small code model: the program and its ! symbols must be linked in the lower 2 GB of the address space. ! Pointers are 64 bits. Programs can be statically or dynamically ! linked. This is the default code model. ! `-mcmodel=kernel' Generate code for the kernel code model. The kernel runs in the negative 2 GB of the address space. This model has to be used for Linux kernel code. ! `-mcmodel=medium' Generate code for the medium model: the program is linked in the lower 2 GB of the address space. Small symbols are also placed ! there. Symbols with sizes larger than `-mlarge-data-threshold' ! are put into large data or BSS sections and can be located above ! 2GB. Programs can be statically or dynamically linked. ! `-mcmodel=large' Generate code for the large model. This model makes no assumptions about addresses and sizes of sections. ! `-maddress-mode=long' Generate code for long address mode. This is only supported for 64-bit and x32 environments. It is the default address mode for 64-bit environments. ! `-maddress-mode=short' Generate code for short address mode. This is only supported for 32-bit and x32 environments. It is the default address mode for 32-bit and x32 environments. *************** File: gcc.info, Node: x86 Windows Optio *** 22214,22275 **** These additional options are available for Microsoft Windows targets: ! '-mconsole' This option specifies that a console application is to be ! generated, by instructing the linker to set the PE header subsystem ! type required for console applications. This option is available ! for Cygwin and MinGW targets and is enabled by default on those ! targets. ! '-mdll' This option is available for Cygwin and MinGW targets. It specifies that a DLL--a dynamic link library--is to be generated, enabling the selection of the required runtime startup object and entry point. ! '-mnop-fun-dllimport' This option is available for Cygwin and MinGW targets. It ! specifies that the 'dllimport' attribute should be ignored. ! '-mthread' ! This option is available for MinGW targets. It specifies that MinGW-specific thread support is to be used. ! '-municode' This option is available for MinGW-w64 targets. It causes the ! 'UNICODE' preprocessor macro to be predefined, and chooses Unicode-capable runtime startup code. ! '-mwin32' This option is available for Cygwin and MinGW targets. It specifies that the typical Microsoft Windows predefined macros are to be set in the pre-processor, but does not influence the choice of runtime library/startup code. ! '-mwindows' This option is available for Cygwin and MinGW targets. It specifies that a GUI application is to be generated by instructing the linker to set the PE header subsystem type appropriately. ! '-fno-set-stack-executable' ! This option is available for MinGW targets. It specifies that the executable flag for the stack used by nested functions isn't set. This is necessary for binaries running in kernel mode of Microsoft Windows, as there the User32 API, which is used to set executable privileges, isn't available. ! '-fwritable-relocated-rdata' This option is available for MinGW and Cygwin targets. It specifies that relocated-data in read-only section is put into the ! '.data' section. This is a necessary for older runtimes not ! supporting modification of '.rdata' sections for pseudo-relocation. ! '-mpe-aligned-commons' This option is available for Cygwin and MinGW targets. It ! specifies that the GNU extension to the PE file format that permits ! the correct alignment of COMMON variables should be used when ! generating code. It is enabled by default if GCC detects that the ! target assembler found during configuration supports the feature. See also under *note x86 Options:: for standard options. --- 22336,22398 ---- These additional options are available for Microsoft Windows targets: ! `-mconsole' This option specifies that a console application is to be ! generated, by instructing the linker to set the PE header ! subsystem type required for console applications. This option is ! available for Cygwin and MinGW targets and is enabled by default ! on those targets. ! `-mdll' This option is available for Cygwin and MinGW targets. It specifies that a DLL--a dynamic link library--is to be generated, enabling the selection of the required runtime startup object and entry point. ! `-mnop-fun-dllimport' This option is available for Cygwin and MinGW targets. It ! specifies that the `dllimport' attribute should be ignored. ! `-mthread' ! This option is available for MinGW targets. It specifies that MinGW-specific thread support is to be used. ! `-municode' This option is available for MinGW-w64 targets. It causes the ! `UNICODE' preprocessor macro to be predefined, and chooses Unicode-capable runtime startup code. ! `-mwin32' This option is available for Cygwin and MinGW targets. It specifies that the typical Microsoft Windows predefined macros are to be set in the pre-processor, but does not influence the choice of runtime library/startup code. ! `-mwindows' This option is available for Cygwin and MinGW targets. It specifies that a GUI application is to be generated by instructing the linker to set the PE header subsystem type appropriately. ! `-fno-set-stack-executable' ! This option is available for MinGW targets. It specifies that the executable flag for the stack used by nested functions isn't set. This is necessary for binaries running in kernel mode of Microsoft Windows, as there the User32 API, which is used to set executable privileges, isn't available. ! `-fwritable-relocated-rdata' This option is available for MinGW and Cygwin targets. It specifies that relocated-data in read-only section is put into the ! `.data' section. This is a necessary for older runtimes not ! supporting modification of `.rdata' sections for pseudo-relocation. ! `-mpe-aligned-commons' This option is available for Cygwin and MinGW targets. It ! specifies that the GNU extension to the PE file format that ! permits the correct alignment of COMMON variables should be used ! when generating code. It is enabled by default if GCC detects ! that the target assembler found during configuration supports the ! feature. See also under *note x86 Options:: for standard options. *************** File: gcc.info, Node: Xstormy16 Options *** 22281,22287 **** These options are defined for Xstormy16: ! '-msim' Choose startup files and linker script suitable for the simulator.  --- 22404,22410 ---- These options are defined for Xstormy16: ! `-msim' Choose startup files and linker script suitable for the simulator.  *************** File: gcc.info, Node: Xtensa Options, *** 22292,22390 **** These options are supported for Xtensa targets: ! '-mconst16' ! '-mno-const16' ! Enable or disable use of 'CONST16' instructions for loading ! constant values. The 'CONST16' instruction is currently not a ! standard option from Tensilica. When enabled, 'CONST16' ! instructions are always used in place of the standard 'L32R' ! instructions. The use of 'CONST16' is enabled by default only if ! the 'L32R' instruction is not available. ! '-mfused-madd' ! '-mno-fused-madd' Enable or disable use of fused multiply/add and multiply/subtract instructions in the floating-point option. This has no effect if the floating-point option is not also enabled. Disabling fused ! multiply/add and multiply/subtract instructions forces the compiler ! to use separate instructions for the multiply and add/subtract ! operations. This may be desirable in some cases where strict IEEE ! 754-compliant results are required: the fused multiply add/subtract ! instructions do not round the intermediate result, thereby ! producing results with _more_ bits of precision than specified by ! the IEEE standard. Disabling fused multiply add/subtract ! instructions also ensures that the program output is not sensitive ! to the compiler's ability to combine multiply and add/subtract ! operations. ! '-mserialize-volatile' ! '-mno-serialize-volatile' ! When this option is enabled, GCC inserts 'MEMW' instructions before ! 'volatile' memory references to guarantee sequential consistency. ! The default is '-mserialize-volatile'. Use ! '-mno-serialize-volatile' to omit the 'MEMW' instructions. ! '-mforce-no-pic' For targets, like GNU/Linux, where all user-mode Xtensa code must be position-independent code (PIC), this option disables PIC for compiling kernel code. ! '-mtext-section-literals' ! '-mno-text-section-literals' These options control the treatment of literal pools. The default ! is '-mno-text-section-literals', which places literals in a separate section in the output file. This allows the literal pool to be placed in a data RAM/ROM, and it also allows the linker to combine literal pools from separate object files to remove redundant literals and improve code size. With ! '-mtext-section-literals', the literals are interspersed in the text section in order to keep them as close as possible to their references. This may be necessary for large assembly files. Literals for each function are placed right before that function. ! '-mauto-litpools' ! '-mno-auto-litpools' These options control the treatment of literal pools. The default ! is '-mno-auto-litpools', which places literals in a separate ! section in the output file unless '-mtext-section-literals' is ! used. With '-mauto-litpools' the literals are interspersed in the text section by the assembler. Compiler does not produce explicit ! '.literal' directives and loads literals into registers with 'MOVI' ! instructions instead of 'L32R' to let the assembler do relaxation ! and place literals as necessary. This option allows assembler to ! create several literal pools per function and assemble very big ! functions, which may not be possible with ! '-mtext-section-literals'. ! '-mtarget-align' ! '-mno-target-align' When this option is enabled, GCC instructs the assembler to automatically align instructions to reduce branch penalties at the expense of some code density. The assembler attempts to widen density instructions to align branch targets and the instructions following call instructions. If there are not enough preceding safe density instructions to align a target, no widening is ! performed. The default is '-mtarget-align'. These options do not ! affect the treatment of auto-aligned instructions like 'LOOP', which the assembler always aligns, either by widening density instructions or by inserting NOP instructions. ! '-mlongcalls' ! '-mno-longcalls' When this option is enabled, GCC instructs the assembler to translate direct calls to indirect calls unless it can determine that the target of a direct call is in the range allowed by the call instruction. This translation typically occurs for calls to functions in other source files. Specifically, the assembler ! translates a direct 'CALL' instruction into an 'L32R' followed by a ! 'CALLX' instruction. The default is '-mno-longcalls'. This option ! should be used in programs where the call target can potentially be ! out of range. This option is implemented in the assembler, not the ! compiler, so the assembly code generated by GCC still shows direct ! call instructions--look at the disassembled object code to see the ! actual instructions. Note that the assembler uses an indirect call ! for every cross-file call, not just those that really are out of ! range.  File: gcc.info, Node: zSeries Options, Prev: Xtensa Options, Up: Submodel Options --- 22415,22513 ---- These options are supported for Xtensa targets: ! `-mconst16' ! `-mno-const16' ! Enable or disable use of `CONST16' instructions for loading ! constant values. The `CONST16' instruction is currently not a ! standard option from Tensilica. When enabled, `CONST16' ! instructions are always used in place of the standard `L32R' ! instructions. The use of `CONST16' is enabled by default only if ! the `L32R' instruction is not available. ! `-mfused-madd' ! `-mno-fused-madd' Enable or disable use of fused multiply/add and multiply/subtract instructions in the floating-point option. This has no effect if the floating-point option is not also enabled. Disabling fused ! multiply/add and multiply/subtract instructions forces the ! compiler to use separate instructions for the multiply and ! add/subtract operations. This may be desirable in some cases ! where strict IEEE 754-compliant results are required: the fused ! multiply add/subtract instructions do not round the intermediate ! result, thereby producing results with _more_ bits of precision ! than specified by the IEEE standard. Disabling fused multiply ! add/subtract instructions also ensures that the program output is ! not sensitive to the compiler's ability to combine multiply and ! add/subtract operations. ! `-mserialize-volatile' ! `-mno-serialize-volatile' ! When this option is enabled, GCC inserts `MEMW' instructions before ! `volatile' memory references to guarantee sequential consistency. ! The default is `-mserialize-volatile'. Use ! `-mno-serialize-volatile' to omit the `MEMW' instructions. ! `-mforce-no-pic' For targets, like GNU/Linux, where all user-mode Xtensa code must be position-independent code (PIC), this option disables PIC for compiling kernel code. ! `-mtext-section-literals' ! `-mno-text-section-literals' These options control the treatment of literal pools. The default ! is `-mno-text-section-literals', which places literals in a separate section in the output file. This allows the literal pool to be placed in a data RAM/ROM, and it also allows the linker to combine literal pools from separate object files to remove redundant literals and improve code size. With ! `-mtext-section-literals', the literals are interspersed in the text section in order to keep them as close as possible to their references. This may be necessary for large assembly files. Literals for each function are placed right before that function. ! `-mauto-litpools' ! `-mno-auto-litpools' These options control the treatment of literal pools. The default ! is `-mno-auto-litpools', which places literals in a separate ! section in the output file unless `-mtext-section-literals' is ! used. With `-mauto-litpools' the literals are interspersed in the text section by the assembler. Compiler does not produce explicit ! `.literal' directives and loads literals into registers with ! `MOVI' instructions instead of `L32R' to let the assembler do ! relaxation and place literals as necessary. This option allows ! assembler to create several literal pools per function and assemble ! very big functions, which may not be possible with ! `-mtext-section-literals'. ! `-mtarget-align' ! `-mno-target-align' When this option is enabled, GCC instructs the assembler to automatically align instructions to reduce branch penalties at the expense of some code density. The assembler attempts to widen density instructions to align branch targets and the instructions following call instructions. If there are not enough preceding safe density instructions to align a target, no widening is ! performed. The default is `-mtarget-align'. These options do not ! affect the treatment of auto-aligned instructions like `LOOP', which the assembler always aligns, either by widening density instructions or by inserting NOP instructions. ! `-mlongcalls' ! `-mno-longcalls' When this option is enabled, GCC instructs the assembler to translate direct calls to indirect calls unless it can determine that the target of a direct call is in the range allowed by the call instruction. This translation typically occurs for calls to functions in other source files. Specifically, the assembler ! translates a direct `CALL' instruction into an `L32R' followed by ! a `CALLX' instruction. The default is `-mno-longcalls'. This ! option should be used in programs where the call target can ! potentially be out of range. This option is implemented in the ! assembler, not the compiler, so the assembly code generated by GCC ! still shows direct call instructions--look at the disassembled ! object code to see the actual instructions. Note that the ! assembler uses an indirect call for every cross-file call, not ! just those that really are out of range.  File: gcc.info, Node: zSeries Options, Prev: Xtensa Options, Up: Submodel Options *************** File: gcc.info, Node: Spec Files, Next *** 22400,22436 **** 3.19 Specifying Subprocesses and the Switches to Pass to Them ============================================================= ! 'gcc' is a driver program. It performs its job by invoking a sequence of other programs to do the work of compiling, assembling and linking. GCC interprets its command-line parameters and uses these to deduce ! which programs it should invoke, and which command-line options it ought ! to place on their command lines. This behavior is controlled by "spec ! strings". In most cases there is one spec string for each program that ! GCC can invoke, but a few programs have multiple spec strings to control ! their behavior. The spec strings built into GCC can be overridden by ! using the '-specs=' command-line switch to specify a spec file. "Spec files" are plain-text files that are used to construct spec strings. They consist of a sequence of directives separated by blank lines. The type of directive is determined by the first non-whitespace character on the line, which can be one of the following: ! '%COMMAND' Issues a COMMAND to the spec file processor. The commands that can appear here are: ! '%include ' Search for FILE and insert its text at the current point in the specs file. ! '%include_noerr ' ! Just like '%include', but do not generate an error message if the include file cannot be found. ! '%rename OLD_NAME NEW_NAME' Rename the spec string OLD_NAME to NEW_NAME. ! '*[SPEC_NAME]:' This tells the compiler to create, override or delete the named spec string. All lines after this directive up to the next directive or blank line are considered to be the text for the spec --- 22523,22561 ---- 3.19 Specifying Subprocesses and the Switches to Pass to Them ============================================================= ! `gcc' is a driver program. It performs its job by invoking a sequence of other programs to do the work of compiling, assembling and linking. GCC interprets its command-line parameters and uses these to deduce ! which programs it should invoke, and which command-line options it ! ought to place on their command lines. This behavior is controlled by ! "spec strings". In most cases there is one spec string for each ! program that GCC can invoke, but a few programs have multiple spec ! strings to control their behavior. The spec strings built into GCC can ! be overridden by using the `-specs=' command-line switch to specify a ! spec file. "Spec files" are plain-text files that are used to construct spec strings. They consist of a sequence of directives separated by blank lines. The type of directive is determined by the first non-whitespace character on the line, which can be one of the following: ! `%COMMAND' Issues a COMMAND to the spec file processor. The commands that can appear here are: ! `%include ' Search for FILE and insert its text at the current point in the specs file. ! `%include_noerr ' ! Just like `%include', but do not generate an error message if the include file cannot be found. ! `%rename OLD_NAME NEW_NAME' Rename the spec string OLD_NAME to NEW_NAME. ! ! `*[SPEC_NAME]:' This tells the compiler to create, override or delete the named spec string. All lines after this directive up to the next directive or blank line are considered to be the text for the spec *************** character on the line, which can be one *** 22439,22449 **** Otherwise, if the spec does not currently exist a new spec is created. If the spec does exist then its contents are overridden by the text of this directive, unless the first character of that ! text is the '+' character, in which case the text is appended to the spec. ! '[SUFFIX]:' ! Creates a new '[SUFFIX] spec' pair. All lines after this directive and up to the next directive or blank line are considered to make up the spec string for the indicated suffix. When the compiler encounters an input file with the named suffix, it processes the --- 22564,22574 ---- Otherwise, if the spec does not currently exist a new spec is created. If the spec does exist then its contents are overridden by the text of this directive, unless the first character of that ! text is the `+' character, in which case the text is appended to the spec. ! `[SUFFIX]:' ! Creates a new `[SUFFIX] spec' pair. All lines after this directive and up to the next directive or blank line are considered to make up the spec string for the indicated suffix. When the compiler encounters an input file with the named suffix, it processes the *************** character on the line, which can be one *** 22453,22469 **** .ZZ: z-compile -input %i ! This says that any input file whose name ends in '.ZZ' should be ! passed to the program 'z-compile', which should be invoked with the ! command-line switch '-input' and with the result of performing the ! '%i' substitution. (See below.) As an alternative to providing a spec string, the text following a suffix directive can be one of the following: ! '@LANGUAGE' This says that the suffix is an alias for a known LANGUAGE. ! This is similar to using the '-x' command-line switch to GCC to specify a language explicitly. For example: .ZZ: --- 22578,22594 ---- .ZZ: z-compile -input %i ! This says that any input file whose name ends in `.ZZ' should be ! passed to the program `z-compile', which should be invoked with the ! command-line switch `-input' and with the result of performing the ! `%i' substitution. (See below.) As an alternative to providing a spec string, the text following a suffix directive can be one of the following: ! `@LANGUAGE' This says that the suffix is an alias for a known LANGUAGE. ! This is similar to using the `-x' command-line switch to GCC to specify a language explicitly. For example: .ZZ: *************** character on the line, which can be one *** 22471,22477 **** Says that .ZZ files are, in fact, C++ source files. ! '#NAME' This causes an error messages saying: NAME compiler not installed on this system. --- 22596,22602 ---- Says that .ZZ files are, in fact, C++ source files. ! `#NAME' This causes an error messages saying: NAME compiler not installed on this system. *************** character on the line, which can be one *** 22482,22487 **** --- 22607,22613 ---- effectively possible to override earlier entries using this technique. + GCC has the following spec strings built into it. Spec files can override these strings or create their own. Note that individual targets can also add their own spec strings to this list. *************** targets can also add their own spec stri *** 22497,22503 **** libgcc Decides which GCC support library to pass to the linker linker Sets the name of the linker predefines Defines to be passed to the C preprocessor ! signed_char Defines to pass to CPP to say whether char is signed by default startfile Object files to include at the start of the link --- 22623,22629 ---- libgcc Decides which GCC support library to pass to the linker linker Sets the name of the linker predefines Defines to be passed to the C preprocessor ! signed_char Defines to pass to CPP to say whether `char' is signed by default startfile Object files to include at the start of the link *************** targets can also add their own spec stri *** 22508,22799 **** *lib: --start-group -lgcc -lc -leval1 --end-group %(old_lib) ! This example renames the spec called 'lib' to 'old_lib' and then ! overrides the previous definition of 'lib' with a new one. The new definition adds in some extra command-line options before including the text of the old definition. "Spec strings" are a list of command-line options to be passed to their corresponding program. In addition, the spec strings can contain ! '%'-prefixed sequences to substitute variable text or to conditionally insert text into the command line. Using these constructs it is possible to generate quite complex command lines. ! Here is a table of all defined '%'-sequences for spec strings. Note that spaces are not generated automatically around the results of expanding these sequences. Therefore you can concatenate them together or combine them with constant text in a single argument. ! '%%' ! Substitute one '%' into the program name or argument. ! '%i' Substitute the name of the input file being processed. ! '%b' ! Substitute the basename of the input file being processed. This is ! the substring up to (and not including) the last period and not including the directory. ! '%B' ! This is the same as '%b', but include the file suffix (text after the last period). ! '%d' ! Marks the argument containing or following the '%d' as a temporary file name, so that that file is deleted if GCC exits successfully. ! Unlike '%g', this contributes no text to the argument. ! '%gSUFFIX' Substitute a file name that has suffix SUFFIX and is chosen once ! per compilation, and mark the argument in the same way as '%d'. To ! reduce exposure to denial-of-service attacks, the file name is now ! chosen in a way that is hard to predict even when previously chosen ! file names are known. For example, '%g.s ... %g.o ... %g.s' might ! turn into 'ccUVUUAU.s ccXYAXZ12.o ccUVUUAU.s'. SUFFIX matches the ! regexp '[.A-Za-z]*' or the special string '%O', which is treated ! exactly as if '%O' had been preprocessed. Previously, '%g' was ! simply substituted with a file name chosen once per compilation, ! without regard to any appended suffix (which was therefore treated ! just like ordinary text), making such attacks more likely to ! succeed. ! '%uSUFFIX' ! Like '%g', but generates a new temporary file name each time it appears instead of once per compilation. ! '%USUFFIX' ! Substitutes the last file name generated with '%uSUFFIX', generating a new one if there is no such last file name. In the ! absence of any '%uSUFFIX', this is just like '%gSUFFIX', except ! they don't share the same suffix _space_, so '%g.s ... %U.s ... %g.s ... %U.s' involves the generation of two distinct file names, ! one for each '%g.s' and another for each '%U.s'. Previously, '%U' was simply substituted with a file name chosen for the previous ! '%u', without regard to any appended suffix. ! '%jSUFFIX' ! Substitutes the name of the 'HOST_BIT_BUCKET', if any, and if it is ! writable, and if '-save-temps' is not used; otherwise, substitute ! the name of a temporary file, just like '%u'. This temporary file is not meant for communication between processes, but rather as a junk disposal mechanism. ! '%|SUFFIX' ! '%mSUFFIX' ! Like '%g', except if '-pipe' is in effect. In that case '%|' ! substitutes a single dash and '%m' substitutes nothing at all. These are the two most common ways to instruct a program that it should read from standard input or write to standard output. If ! you need something more elaborate you can use an '%{pipe:'X'}' ! construct: see for example 'f/lang-specs.h'. ! '%.SUFFIX' Substitutes .SUFFIX for the suffixes of a matched switch's args ! when it is subsequently output with '%*'. SUFFIX is terminated by the next space or %. ! '%w' ! Marks the argument containing or following the '%w' as the designated output file of this compilation. This puts the argument ! into the sequence of arguments that '%o' substitutes. ! '%o' Substitutes the names of all the output files, with spaces automatically placed around them. You should write spaces around ! the '%o' as well or the results are undefined. '%o' is for use in the specs for running the linker. Input files whose names have no recognized suffix are not compiled at all, but they are included among the output files, so they are linked. ! '%O' ! Substitutes the suffix for object files. Note that this is handled ! specially when it immediately follows '%g, %u, or %U', because of ! the need for those to form complete file names. The handling is ! such that '%O' is treated exactly as if it had already been ! substituted, except that '%g, %u, and %U' do not currently support ! additional SUFFIX characters following '%O' as they do following, ! for example, '.o'. ! '%p' Substitutes the standard macro predefinitions for the current ! target machine. Use this when running 'cpp'. ! '%P' ! Like '%p', but puts '__' before and after the name of each ! predefined macro, except for macros that start with '__' or with ! '_L', where L is an uppercase letter. This is for ISO C. ! '%I' ! Substitute any of '-iprefix' (made from 'GCC_EXEC_PREFIX'), ! '-isysroot' (made from 'TARGET_SYSTEM_ROOT'), '-isystem' (made from ! 'COMPILER_PATH' and '-B' options) and '-imultilib' as necessary. ! '%s' Current argument is the name of a library or startup file of some sort. Search for that file in a standard list of directories and substitute the full name found. The current working directory is included in the list of directories scanned. ! '%T' Current argument is the name of a linker script. Search for that ! file in the current list of directories to scan for libraries. If ! the file is located insert a '--script' option into the command line followed by the full path name found. If the file is not found then generate an error message. Note: the current working directory is not searched. ! '%eSTR' Print STR as an error message. STR is terminated by a newline. Use this when inconsistent options are detected. ! '%(NAME)' Substitute the contents of spec string NAME at this point. ! '%x{OPTION}' ! Accumulate an option for '%X'. ! '%X' ! Output the accumulated linker options specified by '-Wl' or a '%x' spec string. ! '%Y' ! Output the accumulated assembler options specified by '-Wa'. ! '%Z' ! Output the accumulated preprocessor options specified by '-Wp'. ! '%a' ! Process the 'asm' spec. This is used to compute the switches to be ! passed to the assembler. ! '%A' ! Process the 'asm_final' spec. This is a spec string for passing switches to an assembler post-processor, if such a program is needed. ! '%l' ! Process the 'link' spec. This is the spec for computing the command line passed to the linker. Typically it makes use of the ! '%L %G %S %D and %E' sequences. ! '%D' ! Dump out a '-L' option for each directory that GCC believes might contain startup files. If the target supports multilibs then the current multilib directory is prepended to each of these paths. ! '%L' ! Process the 'lib' spec. This is a spec string for deciding which libraries are included on the command line to the linker. ! '%G' ! Process the 'libgcc' spec. This is a spec string for deciding which GCC support library is included on the command line to the linker. ! '%S' ! Process the 'startfile' spec. This is a spec for deciding which object files are the first ones passed to the linker. Typically ! this might be a file named 'crt0.o'. ! '%E' ! Process the 'endfile' spec. This is a spec string that specifies the last object files that are passed to the linker. ! '%C' ! Process the 'cpp' spec. This is used to construct the arguments to ! be passed to the C preprocessor. ! '%1' ! Process the 'cc1' spec. This is used to construct the options to ! be passed to the actual C compiler ('cc1'). ! '%2' ! Process the 'cc1plus' spec. This is used to construct the options ! to be passed to the actual C++ compiler ('cc1plus'). ! '%*' ! Substitute the variable part of a matched option. See below. Note ! that each comma in the substituted string is replaced by a single ! space. ! '%. Some choices are ! documented in the preprocessor manual. *Note Implementation-defined ! behavior: (cpp)Implementation-defined behavior. Some choices are made ! by the library and operating system (or other environment when compiling ! for a freestanding environment); refer to their documentation for ! details. * Menu: --- 23368,23379 ---- Some choices depend on the externally determined ABI for the platform (including standard character encodings) which GCC follows; these are listed as "determined by ABI" below. *Note Binary Compatibility: ! Compatibility, and `http://gcc.gnu.org/readings.html'. Some choices ! are documented in the preprocessor manual. *Note ! Implementation-defined behavior: (cpp)Implementation-defined behavior. ! Some choices are made by the library and operating system (or other ! environment when compiling for a freestanding environment); refer to ! their documentation for details. * Menu: *************** File: gcc.info, Node: Translation imple *** 23268,23285 **** 4.1 Translation =============== ! * 'How a diagnostic is identified (C90 3.7, C99 and C11 3.10, C90, C99 and C11 5.1.1.3).' Diagnostics consist of all the output sent to stderr by GCC. ! * 'Whether each nonempty sequence of white-space characters other than new-line is retained or replaced by one space character in translation phase 3 (C90, C99 and C11 5.1.1.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior.  File: gcc.info, Node: Environment implementation, Next: Identifiers implementation, Prev: Translation implementation, Up: C Implementation --- 23400,23418 ---- 4.1 Translation =============== ! * `How a diagnostic is identified (C90 3.7, C99 and C11 3.10, C90, C99 and C11 5.1.1.3).' Diagnostics consist of all the output sent to stderr by GCC. ! * `Whether each nonempty sequence of white-space characters other than new-line is retained or replaced by one space character in translation phase 3 (C90, C99 and C11 5.1.1.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. +  File: gcc.info, Node: Environment implementation, Next: Identifiers implementation, Prev: Translation implementation, Up: C Implementation *************** File: gcc.info, Node: Environment imple *** 23289,23423 **** The behavior of most of these points are dependent on the implementation of the C library, and are not defined by GCC itself. ! * 'The mapping between physical source file multibyte characters and the source character set in translation phase 1 (C90, C99 and C11 5.1.1.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior.  File: gcc.info, Node: Identifiers implementation, Next: Characters implementation, Prev: Environment implementation, Up: C Implementation 4.3 Identifiers =============== ! * 'Which additional multibyte characters may appear in identifiers and their correspondence to universal character names (C99 and C11 6.4.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * 'The number of significant initial characters in an identifier (C90 ! 6.1.2, C90, C99 and C11 5.2.4.1, C99 and C11 6.4.2).' For internal names, all characters are significant. For external names, the number of significant characters are defined by the linker; for almost all targets, all characters are significant. ! * 'Whether case distinctions are significant in an identifier with external linkage (C90 6.1.2).' This is a property of the linker. C99 and C11 require that case distinctions are always significant in identifiers with external linkage and systems without this property are not supported by GCC.  File: gcc.info, Node: Characters implementation, Next: Integers implementation, Prev: Identifiers implementation, Up: C Implementation 4.4 Characters ============== ! * 'The number of bits in a byte (C90 3.4, C99 and C11 3.6).' Determined by ABI. ! * 'The values of the members of the execution character set (C90, C99 ! and C11 5.2.1).' Determined by ABI. ! * 'The unique value of the member of the execution character set ! produced for each of the standard alphabetic escape sequences (C90, ! C99 and C11 5.2.2).' Determined by ABI. ! * 'The value of a 'char' object into which has been stored any character other than a member of the basic execution character set (C90 6.1.2.5, C99 and C11 6.2.5).' Determined by ABI. ! * 'Which of 'signed char' or 'unsigned char' has the same range, ! representation, and behavior as "plain" 'char' (C90 6.1.2.5, C90 6.2.1.1, C99 and C11 6.2.5, C99 and C11 6.3.1.1).' ! Determined by ABI. The options '-funsigned-char' and ! '-fsigned-char' change the default. *Note Options Controlling C Dialect: C Dialect Options. ! * 'The mapping of members of the source character set (in character constants and string literals) to members of the execution character set (C90 6.1.3.4, C99 and C11 6.4.4.4, C90, C99 and C11 5.1.1.2).' Determined by ABI. ! * 'The value of an integer character constant containing more than one character or containing a character or escape sequence that ! does not map to a single-byte execution character (C90 6.1.3.4, C99 ! and C11 6.4.4.4).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * 'The value of a wide character constant containing more than one multibyte character or a single multibyte character that maps to multiple members of the extended execution character set, or ! containing a multibyte character or escape sequence not represented ! in the extended execution character set (C90 6.1.3.4, C99 and C11 ! 6.4.4.4).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * 'The current locale used to convert a wide character constant ! consisting of a single multibyte character that maps to a member of ! the extended execution character set into a corresponding wide character code (C90 6.1.3.4, C99 and C11 6.4.4.4).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * 'Whether differently-prefixed wide string literal tokens can be concatenated and, if so, the treatment of the resulting multibyte character sequence (C11 6.4.5).' Such tokens may not be concatenated. ! * 'The current locale used to convert a wide string literal into corresponding wide character codes (C90 6.1.4, C99 and C11 6.4.5).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * 'The value of a string literal containing a multibyte character or ! escape sequence not represented in the execution character set (C90 ! 6.1.4, C99 and C11 6.4.5).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * 'The encoding of any of 'wchar_t', 'char16_t', and 'char32_t' where ! the corresponding standard encoding macro ('__STDC_ISO_10646__', ! '__STDC_UTF_16__', or '__STDC_UTF_32__') is not defined (C11 ! 6.10.8.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined ! behavior. 'char16_t' and 'char32_t' literals are always encoded in ! UTF-16 and UTF-32 respectively.  File: gcc.info, Node: Integers implementation, Next: Floating point implementation, Prev: Characters implementation, Up: C Implementation --- 23422,23559 ---- The behavior of most of these points are dependent on the implementation of the C library, and are not defined by GCC itself. ! * `The mapping between physical source file multibyte characters and the source character set in translation phase 1 (C90, C99 and C11 5.1.1.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. +  File: gcc.info, Node: Identifiers implementation, Next: Characters implementation, Prev: Environment implementation, Up: C Implementation 4.3 Identifiers =============== ! * `Which additional multibyte characters may appear in identifiers and their correspondence to universal character names (C99 and C11 6.4.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * `The number of significant initial characters in an identifier ! (C90 6.1.2, C90, C99 and C11 5.2.4.1, C99 and C11 6.4.2).' For internal names, all characters are significant. For external names, the number of significant characters are defined by the linker; for almost all targets, all characters are significant. ! * `Whether case distinctions are significant in an identifier with external linkage (C90 6.1.2).' This is a property of the linker. C99 and C11 require that case distinctions are always significant in identifiers with external linkage and systems without this property are not supported by GCC. +  File: gcc.info, Node: Characters implementation, Next: Integers implementation, Prev: Identifiers implementation, Up: C Implementation 4.4 Characters ============== ! * `The number of bits in a byte (C90 3.4, C99 and C11 3.6).' Determined by ABI. ! * `The values of the members of the execution character set (C90, ! C99 and C11 5.2.1).' Determined by ABI. ! * `The unique value of the member of the execution character set ! produced for each of the standard alphabetic escape sequences ! (C90, C99 and C11 5.2.2).' Determined by ABI. ! * `The value of a `char' object into which has been stored any character other than a member of the basic execution character set (C90 6.1.2.5, C99 and C11 6.2.5).' Determined by ABI. ! * `Which of `signed char' or `unsigned char' has the same range, ! representation, and behavior as "plain" `char' (C90 6.1.2.5, C90 6.2.1.1, C99 and C11 6.2.5, C99 and C11 6.3.1.1).' ! Determined by ABI. The options `-funsigned-char' and ! `-fsigned-char' change the default. *Note Options Controlling C Dialect: C Dialect Options. ! * `The mapping of members of the source character set (in character constants and string literals) to members of the execution character set (C90 6.1.3.4, C99 and C11 6.4.4.4, C90, C99 and C11 5.1.1.2).' Determined by ABI. ! * `The value of an integer character constant containing more than one character or containing a character or escape sequence that ! does not map to a single-byte execution character (C90 6.1.3.4, ! C99 and C11 6.4.4.4).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * `The value of a wide character constant containing more than one multibyte character or a single multibyte character that maps to multiple members of the extended execution character set, or ! containing a multibyte character or escape sequence not ! represented in the extended execution character set (C90 6.1.3.4, ! C99 and C11 6.4.4.4).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * `The current locale used to convert a wide character constant ! consisting of a single multibyte character that maps to a member ! of the extended execution character set into a corresponding wide character code (C90 6.1.3.4, C99 and C11 6.4.4.4).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * `Whether differently-prefixed wide string literal tokens can be concatenated and, if so, the treatment of the resulting multibyte character sequence (C11 6.4.5).' Such tokens may not be concatenated. ! * `The current locale used to convert a wide string literal into corresponding wide character codes (C90 6.1.4, C99 and C11 6.4.5).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * `The value of a string literal containing a multibyte character or ! escape sequence not represented in the execution character set ! (C90 6.1.4, C99 and C11 6.4.5).' *Note Implementation-defined behavior: (cpp)Implementation-defined behavior. ! * `The encoding of any of `wchar_t', `char16_t', and `char32_t' ! where the corresponding standard encoding macro ! (`__STDC_ISO_10646__', `__STDC_UTF_16__', or `__STDC_UTF_32__') is ! not defined (C11 6.10.8.2).' *Note Implementation-defined behavior: (cpp)Implementation-defined ! behavior. `char16_t' and `char32_t' literals are always encoded ! in UTF-16 and UTF-32 respectively. !  File: gcc.info, Node: Integers implementation, Next: Floating point implementation, Prev: Characters implementation, Up: C Implementation *************** File: gcc.info, Node: Integers implemen *** 23425,23436 **** 4.5 Integers ============ ! * 'Any extended integer types that exist in the implementation (C99 and C11 6.2.5).' GCC does not support any extended integer types. ! * 'Whether signed integer types are represented using sign and magnitude, two's complement, or one's complement, and whether the extraordinary value is a trap representation or an ordinary value (C99 and C11 6.2.6.2).' --- 23561,23572 ---- 4.5 Integers ============ ! * `Any extended integer types that exist in the implementation (C99 and C11 6.2.5).' GCC does not support any extended integer types. ! * `Whether signed integer types are represented using sign and magnitude, two's complement, or one's complement, and whether the extraordinary value is a trap representation or an ordinary value (C99 and C11 6.2.6.2).' *************** File: gcc.info, Node: Integers implemen *** 23438,23563 **** GCC supports only two's complement integer types, and all bit patterns are ordinary values. ! * 'The rank of any extended integer type relative to another extended integer type with the same precision (C99 and C11 6.3.1.1).' GCC does not support any extended integer types. ! * 'The result of, or the signal raised by, converting an integer to a signed integer type when the value cannot be represented in an object of that type (C90 6.2.1.2, C99 and C11 6.3.1.3).' For conversion to a type of width N, the value is reduced modulo 2^N to be within range of the type; no signal is raised. ! * 'The results of some bitwise operations on signed integers (C90 6.3, C99 and C11 6.5).' Bitwise operators act on the representation of the value including both the sign and value bits, where the sign bit is considered ! immediately above the highest-value value bit. Signed '>>' acts on ! negative numbers by sign extension. As an extension to the C language, GCC does not use the latitude ! given in C99 and C11 only to treat certain aspects of signed '<<' ! as undefined. However, '-fsanitize=shift' (and ! '-fsanitize=undefined') will diagnose such cases. They are also diagnosed where constant expressions are required. ! * 'The sign of the remainder on integer division (C90 6.3.5).' GCC always follows the C99 and C11 requirement that the result of division is truncated towards zero.  File: gcc.info, Node: Floating point implementation, Next: Arrays and pointers implementation, Prev: Integers implementation, Up: C Implementation 4.6 Floating Point ================== ! * 'The accuracy of the floating-point operations and of the library ! functions in '' and '' that return floating-point results (C90, C99 and C11 5.2.4.2.2).' The accuracy is unknown. ! * 'The rounding behaviors characterized by non-standard values of ! 'FLT_ROUNDS' (C90, C99 and C11 5.2.4.2.2).' GCC does not use such values. ! * 'The evaluation methods characterized by non-standard negative ! values of 'FLT_EVAL_METHOD' (C99 and C11 5.2.4.2.2).' GCC does not use such values. ! * 'The direction of rounding when an integer is converted to a floating-point number that cannot exactly represent the original value (C90 6.2.1.3, C99 and C11 6.3.1.4).' C99 Annex F is followed. ! * 'The direction of rounding when a floating-point number is ! converted to a narrower floating-point number (C90 6.2.1.4, C99 and ! C11 6.3.1.5).' C99 Annex F is followed. ! * 'How the nearest representable value or the larger or smaller representable value immediately adjacent to the nearest representable value is chosen for certain floating constants (C90 6.1.3.1, C99 and C11 6.4.4.2).' C99 Annex F is followed. ! * 'Whether and how floating expressions are contracted when not ! disallowed by the 'FP_CONTRACT' pragma (C99 and C11 6.5).' ! Expressions are currently only contracted if '-ffp-contract=fast', ! '-funsafe-math-optimizations' or '-ffast-math' are used. This is subject to change. ! * 'The default state for the 'FENV_ACCESS' pragma (C99 and C11 7.6.1).' This pragma is not implemented, but the default is to "off" unless ! '-frounding-math' is used in which case it is "on". ! * 'Additional floating-point exceptions, rounding modes, environments, and classifications, and their macro names (C99 and C11 7.6, C99 and C11 7.12).' This is dependent on the implementation of the C library, and is not defined by GCC itself. ! * 'The default state for the 'FP_CONTRACT' pragma (C99 and C11 7.12.2).' This pragma is not implemented. Expressions are currently only ! contracted if '-ffp-contract=fast', '-funsafe-math-optimizations' ! or '-ffast-math' are used. This is subject to change. ! * 'Whether the "inexact" floating-point exception can be raised when the rounded result actually does equal the mathematical result in an IEC 60559 conformant implementation (C99 F.9).' This is dependent on the implementation of the C library, and is not defined by GCC itself. ! * 'Whether the "underflow" (and "inexact") floating-point exception ! can be raised when a result is tiny but not inexact in an IEC 60559 ! conformant implementation (C99 F.9).' This is dependent on the implementation of the C library, and is not defined by GCC itself.  File: gcc.info, Node: Arrays and pointers implementation, Next: Hints implementation, Prev: Floating point implementation, Up: C Implementation 4.7 Arrays and Pointers ======================= ! * 'The result of converting a pointer to an integer or vice versa (C90 6.3.4, C99 and C11 6.3.2.3).' A cast from pointer to integer discards most-significant bits if --- 23574,23701 ---- GCC supports only two's complement integer types, and all bit patterns are ordinary values. ! * `The rank of any extended integer type relative to another extended integer type with the same precision (C99 and C11 6.3.1.1).' GCC does not support any extended integer types. ! * `The result of, or the signal raised by, converting an integer to a signed integer type when the value cannot be represented in an object of that type (C90 6.2.1.2, C99 and C11 6.3.1.3).' For conversion to a type of width N, the value is reduced modulo 2^N to be within range of the type; no signal is raised. ! * `The results of some bitwise operations on signed integers (C90 6.3, C99 and C11 6.5).' Bitwise operators act on the representation of the value including both the sign and value bits, where the sign bit is considered ! immediately above the highest-value value bit. Signed `>>' acts ! on negative numbers by sign extension. As an extension to the C language, GCC does not use the latitude ! given in C99 and C11 only to treat certain aspects of signed `<<' ! as undefined. However, `-fsanitize=shift' (and ! `-fsanitize=undefined') will diagnose such cases. They are also diagnosed where constant expressions are required. ! * `The sign of the remainder on integer division (C90 6.3.5).' GCC always follows the C99 and C11 requirement that the result of division is truncated towards zero. +  File: gcc.info, Node: Floating point implementation, Next: Arrays and pointers implementation, Prev: Integers implementation, Up: C Implementation 4.6 Floating Point ================== ! * `The accuracy of the floating-point operations and of the library ! functions in `' and `' that return floating-point results (C90, C99 and C11 5.2.4.2.2).' The accuracy is unknown. ! * `The rounding behaviors characterized by non-standard values of ! `FLT_ROUNDS' (C90, C99 and C11 5.2.4.2.2).' GCC does not use such values. ! * `The evaluation methods characterized by non-standard negative ! values of `FLT_EVAL_METHOD' (C99 and C11 5.2.4.2.2).' GCC does not use such values. ! * `The direction of rounding when an integer is converted to a floating-point number that cannot exactly represent the original value (C90 6.2.1.3, C99 and C11 6.3.1.4).' C99 Annex F is followed. ! * `The direction of rounding when a floating-point number is ! converted to a narrower floating-point number (C90 6.2.1.4, C99 ! and C11 6.3.1.5).' C99 Annex F is followed. ! * `How the nearest representable value or the larger or smaller representable value immediately adjacent to the nearest representable value is chosen for certain floating constants (C90 6.1.3.1, C99 and C11 6.4.4.2).' C99 Annex F is followed. ! * `Whether and how floating expressions are contracted when not ! disallowed by the `FP_CONTRACT' pragma (C99 and C11 6.5).' ! Expressions are currently only contracted if `-ffp-contract=fast', ! `-funsafe-math-optimizations' or `-ffast-math' are used. This is subject to change. ! * `The default state for the `FENV_ACCESS' pragma (C99 and C11 7.6.1).' This pragma is not implemented, but the default is to "off" unless ! `-frounding-math' is used in which case it is "on". ! * `Additional floating-point exceptions, rounding modes, environments, and classifications, and their macro names (C99 and C11 7.6, C99 and C11 7.12).' This is dependent on the implementation of the C library, and is not defined by GCC itself. ! * `The default state for the `FP_CONTRACT' pragma (C99 and C11 7.12.2).' This pragma is not implemented. Expressions are currently only ! contracted if `-ffp-contract=fast', `-funsafe-math-optimizations' ! or `-ffast-math' are used. This is subject to change. ! * `Whether the "inexact" floating-point exception can be raised when the rounded result actually does equal the mathematical result in an IEC 60559 conformant implementation (C99 F.9).' This is dependent on the implementation of the C library, and is not defined by GCC itself. ! * `Whether the "underflow" (and "inexact") floating-point exception ! can be raised when a result is tiny but not inexact in an IEC ! 60559 conformant implementation (C99 F.9).' This is dependent on the implementation of the C library, and is not defined by GCC itself. +  File: gcc.info, Node: Arrays and pointers implementation, Next: Hints implementation, Prev: Floating point implementation, Up: C Implementation 4.7 Arrays and Pointers ======================= ! * `The result of converting a pointer to an integer or vice versa (C90 6.3.4, C99 and C11 6.3.2.3).' A cast from pointer to integer discards most-significant bits if *************** File: gcc.info, Node: Arrays and pointe *** 23577,23592 **** integer arithmetic to avoid the undefined behavior of pointer arithmetic as proscribed in C99 and C11 6.5.6/8. ! * 'The size of the result of subtracting two pointers to elements of the same array (C90 6.3.6, C99 and C11 6.5.6).' The value is as specified in the standard and the type is determined by the ABI. - ---------- Footnotes ---------- ! (1) Future versions of GCC may zero-extend, or use a target-defined ! 'ptr_extend' pattern. Do not rely on sign extension.  File: gcc.info, Node: Hints implementation, Next: Structures unions enumerations and bit-fields implementation, Prev: Arrays and pointers implementation, Up: C Implementation --- 23715,23731 ---- integer arithmetic to avoid the undefined behavior of pointer arithmetic as proscribed in C99 and C11 6.5.6/8. ! * `The size of the result of subtracting two pointers to elements of the same array (C90 6.3.6, C99 and C11 6.5.6).' The value is as specified in the standard and the type is determined by the ABI. ! ---------- Footnotes ---------- ! ! (1) Future versions of GCC may zero-extend, or use a target-defined ! `ptr_extend' pattern. Do not rely on sign extension.  File: gcc.info, Node: Hints implementation, Next: Structures unions enumerations and bit-fields implementation, Prev: Arrays and pointers implementation, Up: C Implementation *************** File: gcc.info, Node: Hints implementat *** 23594,23684 **** 4.8 Hints ========= ! * 'The extent to which suggestions made by using the 'register' storage-class specifier are effective (C90 6.5.1, C99 and C11 6.7.1).' ! The 'register' specifier affects code generation only in these ways: * When used as part of the register variable extension, see *note Explicit Register Variables::. ! * When '-O0' is in use, the compiler allocates distinct stack ! memory for all variables that do not have the 'register' ! storage-class specifier; if 'register' is specified, the variable may have a shorter lifespan than the code would indicate and may never be placed in memory. ! * On some rare x86 targets, 'setjmp' doesn't save the registers in all circumstances. In those cases, GCC doesn't allocate ! any variables in registers unless they are marked 'register'. ! * 'The extent to which suggestions made by using the inline function specifier are effective (C99 and C11 6.7.4).' ! GCC will not inline any functions if the '-fno-inline' option is ! used or if '-O0' is used. Otherwise, GCC may still be unable to ! inline a function for many reasons; the '-Winline' option may be used to determine if a function has not been inlined and why not.  File: gcc.info, Node: Structures unions enumerations and bit-fields implementation, Next: Qualifiers implementation, Prev: Hints implementation, Up: C Implementation 4.9 Structures, Unions, Enumerations, and Bit-Fields ==================================================== ! * 'A member of a union object is accessed using a member of a different type (C90 6.3.2.3).' The relevant bytes of the representation of the object are treated as an object of the type used for the access. *Note Type-punning::. This may be a trap representation. ! * 'Whether a "plain" 'int' bit-field is treated as a 'signed int' ! bit-field or as an 'unsigned int' bit-field (C90 6.5.2, C90 6.5.2.1, C99 and C11 6.7.2, C99 and C11 6.7.2.1).' ! By default it is treated as 'signed int' but this may be changed by ! the '-funsigned-bitfields' option. ! * 'Allowable bit-field types other than '_Bool', 'signed int', and ! 'unsigned int' (C99 and C11 6.7.2.1).' ! Other integer types, such as 'long int', and enumerated types are permitted even in strictly conforming mode. ! * 'Whether atomic types are permitted for bit-fields (C11 6.7.2.1).' Atomic types are not permitted for bit-fields. ! * 'Whether a bit-field can straddle a storage-unit boundary (C90 6.5.2.1, C99 and C11 6.7.2.1).' Determined by ABI. ! * 'The order of allocation of bit-fields within a unit (C90 6.5.2.1, C99 and C11 6.7.2.1).' Determined by ABI. ! * 'The alignment of non-bit-field members of structures (C90 6.5.2.1, ! C99 and C11 6.7.2.1).' Determined by ABI. ! * 'The integer type compatible with each enumerated type (C90 6.5.2.2, C99 and C11 6.7.2.2).' ! Normally, the type is 'unsigned int' if there are no negative ! values in the enumeration, otherwise 'int'. If '-fshort-enums' is specified, then if there are negative values it is the first of ! 'signed char', 'short' and 'int' that can represent all the values, ! otherwise it is the first of 'unsigned char', 'unsigned short' and ! 'unsigned int' that can represent all the values. - On some targets, '-fshort-enums' is the default; this is determined - by the ABI.  File: gcc.info, Node: Qualifiers implementation, Next: Declarators implementation, Prev: Structures unions enumerations and bit-fields implementation, Up: C Implementation --- 23733,23826 ---- 4.8 Hints ========= ! * `The extent to which suggestions made by using the `register' storage-class specifier are effective (C90 6.5.1, C99 and C11 6.7.1).' ! The `register' specifier affects code generation only in these ways: * When used as part of the register variable extension, see *note Explicit Register Variables::. ! * When `-O0' is in use, the compiler allocates distinct stack ! memory for all variables that do not have the `register' ! storage-class specifier; if `register' is specified, the variable may have a shorter lifespan than the code would indicate and may never be placed in memory. ! * On some rare x86 targets, `setjmp' doesn't save the registers in all circumstances. In those cases, GCC doesn't allocate ! any variables in registers unless they are marked `register'. ! ! * `The extent to which suggestions made by using the inline function specifier are effective (C99 and C11 6.7.4).' ! GCC will not inline any functions if the `-fno-inline' option is ! used or if `-O0' is used. Otherwise, GCC may still be unable to ! inline a function for many reasons; the `-Winline' option may be used to determine if a function has not been inlined and why not. +  File: gcc.info, Node: Structures unions enumerations and bit-fields implementation, Next: Qualifiers implementation, Prev: Hints implementation, Up: C Implementation 4.9 Structures, Unions, Enumerations, and Bit-Fields ==================================================== ! * `A member of a union object is accessed using a member of a different type (C90 6.3.2.3).' The relevant bytes of the representation of the object are treated as an object of the type used for the access. *Note Type-punning::. This may be a trap representation. ! * `Whether a "plain" `int' bit-field is treated as a `signed int' ! bit-field or as an `unsigned int' bit-field (C90 6.5.2, C90 6.5.2.1, C99 and C11 6.7.2, C99 and C11 6.7.2.1).' ! By default it is treated as `signed int' but this may be changed ! by the `-funsigned-bitfields' option. ! * `Allowable bit-field types other than `_Bool', `signed int', and ! `unsigned int' (C99 and C11 6.7.2.1).' ! Other integer types, such as `long int', and enumerated types are permitted even in strictly conforming mode. ! * `Whether atomic types are permitted for bit-fields (C11 6.7.2.1).' Atomic types are not permitted for bit-fields. ! * `Whether a bit-field can straddle a storage-unit boundary (C90 6.5.2.1, C99 and C11 6.7.2.1).' Determined by ABI. ! * `The order of allocation of bit-fields within a unit (C90 6.5.2.1, C99 and C11 6.7.2.1).' Determined by ABI. ! * `The alignment of non-bit-field members of structures (C90 ! 6.5.2.1, C99 and C11 6.7.2.1).' Determined by ABI. ! * `The integer type compatible with each enumerated type (C90 6.5.2.2, C99 and C11 6.7.2.2).' ! Normally, the type is `unsigned int' if there are no negative ! values in the enumeration, otherwise `int'. If `-fshort-enums' is specified, then if there are negative values it is the first of ! `signed char', `short' and `int' that can represent all the ! values, otherwise it is the first of `unsigned char', `unsigned ! short' and `unsigned int' that can represent all the values. ! ! On some targets, `-fshort-enums' is the default; this is ! determined by the ABI.  File: gcc.info, Node: Qualifiers implementation, Next: Declarators implementation, Prev: Structures unions enumerations and bit-fields implementation, Up: C Implementation *************** File: gcc.info, Node: Qualifiers implem *** 23686,23697 **** 4.10 Qualifiers =============== ! * 'What constitutes an access to an object that has volatile-qualified type (C90 6.5.3, C99 and C11 6.7.3).' Such an object is normally accessed by pointers and used for ! accessing hardware. In most expressions, it is intuitively obvious ! what is a read and what is a write. For example volatile int *dst = SOMEVALUE; volatile int *src = SOMEOTHERVALUE; --- 23828,23839 ---- 4.10 Qualifiers =============== ! * `What constitutes an access to an object that has volatile-qualified type (C90 6.5.3, C99 and C11 6.7.3).' Such an object is normally accessed by pointers and used for ! accessing hardware. In most expressions, it is intuitively ! obvious what is a read and what is a write. For example volatile int *dst = SOMEVALUE; volatile int *src = SOMEOTHERVALUE; *************** File: gcc.info, Node: Qualifiers implem *** 23700,23706 **** will cause a read of the volatile object pointed to by SRC and store the value into the volatile object pointed to by DST. There is no guarantee that these reads and writes are atomic, especially ! for objects larger than 'int'. However, if the volatile storage is not being modified, and the value of the volatile storage is not used, then the situation is --- 23842,23848 ---- will cause a read of the volatile object pointed to by SRC and store the value into the volatile object pointed to by DST. There is no guarantee that these reads and writes are atomic, especially ! for objects larger than `int'. However, if the volatile storage is not being modified, and the value of the volatile storage is not used, then the situation is *************** File: gcc.info, Node: Qualifiers implem *** 23710,23716 **** *src; According to the C standard, such an expression is an rvalue whose ! type is the unqualified version of its original type, i.e. 'int'. Whether GCC interprets this as a read of the volatile object being pointed to or only as a request to evaluate the expression for its side-effects depends on this type. --- 23852,23858 ---- *src; According to the C standard, such an expression is an rvalue whose ! type is the unqualified version of its original type, i.e. `int'. Whether GCC interprets this as a read of the volatile object being pointed to or only as a request to evaluate the expression for its side-effects depends on this type. *************** File: gcc.info, Node: Qualifiers implem *** 23721,23748 **** by GCC as a read of the volatile object; in the other cases, the expression is only evaluated for its side-effects.  File: gcc.info, Node: Declarators implementation, Next: Statements implementation, Prev: Qualifiers implementation, Up: C Implementation 4.11 Declarators ================ ! * 'The maximum number of declarators that may modify an arithmetic, structure or union type (C90 6.5.4).' GCC is only limited by available memory.  File: gcc.info, Node: Statements implementation, Next: Preprocessing directives implementation, Prev: Declarators implementation, Up: C Implementation 4.12 Statements =============== ! * 'The maximum number of 'case' values in a 'switch' statement (C90 6.6.4.2).' GCC is only limited by available memory.  File: gcc.info, Node: Preprocessing directives implementation, Next: Library functions implementation, Prev: Statements implementation, Up: C Implementation --- 23863,23893 ---- by GCC as a read of the volatile object; in the other cases, the expression is only evaluated for its side-effects. +  File: gcc.info, Node: Declarators implementation, Next: Statements implementation, Prev: Qualifiers implementation, Up: C Implementation 4.11 Declarators ================ ! * `The maximum number of declarators that may modify an arithmetic, structure or union type (C90 6.5.4).' GCC is only limited by available memory. +  File: gcc.info, Node: Statements implementation, Next: Preprocessing directives implementation, Prev: Declarators implementation, Up: C Implementation 4.12 Statements =============== ! * `The maximum number of `case' values in a `switch' statement (C90 6.6.4.2).' GCC is only limited by available memory. +  File: gcc.info, Node: Preprocessing directives implementation, Next: Library functions implementation, Prev: Statements implementation, Up: C Implementation *************** File: gcc.info, Node: Preprocessing dir *** 23753,23802 **** behavior, for details of these aspects of implementation-defined behavior. ! * 'The locations within '#pragma' directives where header name preprocessing tokens are recognized (C11 6.4, C11 6.4.7).' ! * 'How sequences in both forms of header names are mapped to headers or external source file names (C90 6.1.7, C99 and C11 6.4.7).' ! * 'Whether the value of a character constant in a constant expression that controls conditional inclusion matches the value of the same character constant in the execution character set (C90 6.8.1, C99 and C11 6.10.1).' ! * 'Whether the value of a single-character character constant in a constant expression that controls conditional inclusion may have a negative value (C90 6.8.1, C99 and C11 6.10.1).' ! * 'The places that are searched for an included '<>' delimited header, and how the places are specified or the header is identified (C90 6.8.2, C99 and C11 6.10.2).' ! * 'How the named source file is searched for in an included '""' delimited header (C90 6.8.2, C99 and C11 6.10.2).' ! * 'The method by which preprocessing tokens (possibly resulting from ! macro expansion) in a '#include' directive are combined into a header name (C90 6.8.2, C99 and C11 6.10.2).' ! * 'The nesting limit for '#include' processing (C90 6.8.2, C99 and C11 6.10.2).' ! * 'Whether the '#' operator inserts a '\' character before the '\' character that begins a universal character name in a character constant or string literal (C99 and C11 6.10.3.2).' ! * 'The behavior on each recognized non-'STDC #pragma' directive (C90 6.8.6, C99 and C11 6.10.6).' ! *Note Pragmas: (cpp)Pragmas, for details of pragmas accepted by GCC ! on all targets. *Note Pragmas Accepted by GCC: Pragmas, for details of target-specific pragmas. ! * 'The definitions for '__DATE__' and '__TIME__' when respectively, the date and time of translation are not available (C90 6.8.8, C99 6.10.8, C11 6.10.8.1).'  File: gcc.info, Node: Library functions implementation, Next: Architecture implementation, Prev: Preprocessing directives implementation, Up: C Implementation --- 23898,23948 ---- behavior, for details of these aspects of implementation-defined behavior. ! * `The locations within `#pragma' directives where header name preprocessing tokens are recognized (C11 6.4, C11 6.4.7).' ! * `How sequences in both forms of header names are mapped to headers or external source file names (C90 6.1.7, C99 and C11 6.4.7).' ! * `Whether the value of a character constant in a constant expression that controls conditional inclusion matches the value of the same character constant in the execution character set (C90 6.8.1, C99 and C11 6.10.1).' ! * `Whether the value of a single-character character constant in a constant expression that controls conditional inclusion may have a negative value (C90 6.8.1, C99 and C11 6.10.1).' ! * `The places that are searched for an included `<>' delimited header, and how the places are specified or the header is identified (C90 6.8.2, C99 and C11 6.10.2).' ! * `How the named source file is searched for in an included `""' delimited header (C90 6.8.2, C99 and C11 6.10.2).' ! * `The method by which preprocessing tokens (possibly resulting from ! macro expansion) in a `#include' directive are combined into a header name (C90 6.8.2, C99 and C11 6.10.2).' ! * `The nesting limit for `#include' processing (C90 6.8.2, C99 and C11 6.10.2).' ! * `Whether the `#' operator inserts a `\' character before the `\' character that begins a universal character name in a character constant or string literal (C99 and C11 6.10.3.2).' ! * `The behavior on each recognized non-`STDC #pragma' directive (C90 6.8.6, C99 and C11 6.10.6).' ! *Note Pragmas: (cpp)Pragmas, for details of pragmas accepted by ! GCC on all targets. *Note Pragmas Accepted by GCC: Pragmas, for details of target-specific pragmas. ! * `The definitions for `__DATE__' and `__TIME__' when respectively, the date and time of translation are not available (C90 6.8.8, C99 6.10.8, C11 6.10.8.1).' +  File: gcc.info, Node: Library functions implementation, Next: Architecture implementation, Prev: Preprocessing directives implementation, Up: C Implementation *************** File: gcc.info, Node: Library functions *** 23806,23831 **** The behavior of most of these points are dependent on the implementation of the C library, and are not defined by GCC itself. ! * 'The null pointer constant to which the macro 'NULL' expands (C90 7.1.6, C99 7.17, C11 7.19).' ! In '', 'NULL' expands to '((void *)0)'. GCC does not ! provide the other headers which define 'NULL' and some library implementations may use other definitions in those headers.  File: gcc.info, Node: Architecture implementation, Next: Locale-specific behavior implementation, Prev: Library functions implementation, Up: C Implementation 4.15 Architecture ================= ! * 'The values or expressions assigned to the macros specified in the ! headers '', '', and '' (C90, C99 and C11 5.2.4.2, C99 7.18.2, C99 7.18.3, C11 7.20.2, C11 7.20.3).' Determined by ABI. ! * 'The result of attempting to indirectly access an object with automatic or thread storage duration from a thread other than the one with which it is associated (C11 6.2.4).' --- 23952,23978 ---- The behavior of most of these points are dependent on the implementation of the C library, and are not defined by GCC itself. ! * `The null pointer constant to which the macro `NULL' expands (C90 7.1.6, C99 7.17, C11 7.19).' ! In `', `NULL' expands to `((void *)0)'. GCC does not ! provide the other headers which define `NULL' and some library implementations may use other definitions in those headers. +  File: gcc.info, Node: Architecture implementation, Next: Locale-specific behavior implementation, Prev: Library functions implementation, Up: C Implementation 4.15 Architecture ================= ! * `The values or expressions assigned to the macros specified in the ! headers `', `', and `' (C90, C99 and C11 5.2.4.2, C99 7.18.2, C99 7.18.3, C11 7.20.2, C11 7.20.3).' Determined by ABI. ! * `The result of attempting to indirectly access an object with automatic or thread storage duration from a thread other than the one with which it is associated (C11 6.2.4).' *************** File: gcc.info, Node: Architecture impl *** 23833,23861 **** synchronization for concurrent accesses as for concurrent accesses to any object. ! * 'The number, order, and encoding of bytes in any object (when not explicitly specified in this International Standard) (C99 and C11 6.2.6.1).' Determined by ABI. ! * 'Whether any extended alignments are supported and the contexts in which they are supported (C11 6.2.8).' ! Extended alignments up to 2^{28} (bytes) are supported for objects ! of automatic storage duration. Alignments supported for objects of ! static and thread storage duration are determined by the ABI. ! * 'Valid alignment values other than those returned by an _Alignof expression for fundamental types, if any (C11 6.2.8).' ! Valid alignments are powers of 2 up to and including 2^{28}. ! * 'The value of the result of the 'sizeof' and '_Alignof' operators (C90 6.3.3.4, C99 and C11 6.5.3.4).' Determined by ABI.  File: gcc.info, Node: Locale-specific behavior implementation, Prev: Architecture implementation, Up: C Implementation --- 23980,24009 ---- synchronization for concurrent accesses as for concurrent accesses to any object. ! * `The number, order, and encoding of bytes in any object (when not explicitly specified in this International Standard) (C99 and C11 6.2.6.1).' Determined by ABI. ! * `Whether any extended alignments are supported and the contexts in which they are supported (C11 6.2.8).' ! Extended alignments up to 2^28 (bytes) are supported for objects ! of automatic storage duration. Alignments supported for objects ! of static and thread storage duration are determined by the ABI. ! * `Valid alignment values other than those returned by an _Alignof expression for fundamental types, if any (C11 6.2.8).' ! Valid alignments are powers of 2 up to and including 2^28. ! * `The value of the result of the `sizeof' and `_Alignof' operators (C90 6.3.3.4, C99 and C11 6.5.3.4).' Determined by ABI. +  File: gcc.info, Node: Locale-specific behavior implementation, Prev: Architecture implementation, Up: C Implementation *************** A conforming implementation of ISO C++ i *** 23875,23893 **** choice of behavior in each of the areas that are designated "implementation defined". The following lists all such areas, along with the section numbers from the ISO/IEC 14882:1998 and ISO/IEC ! 14882:2003 standards. Some areas are only implementation-defined in one ! version of the standard. Some choices depend on the externally determined ABI for the platform (including standard character encodings) which GCC follows; these are listed as "determined by ABI" below. *Note Binary Compatibility: ! Compatibility, and . Some choices are ! documented in the preprocessor manual. *Note Implementation-defined ! behavior: (cpp)Implementation-defined behavior. Some choices are ! documented in the corresponding document for the C language. *Note C ! Implementation::. Some choices are made by the library and operating ! system (or other environment when compiling for a freestanding ! environment); refer to their documentation for details. * Menu: --- 24023,24041 ---- choice of behavior in each of the areas that are designated "implementation defined". The following lists all such areas, along with the section numbers from the ISO/IEC 14882:1998 and ISO/IEC ! 14882:2003 standards. Some areas are only implementation-defined in ! one version of the standard. Some choices depend on the externally determined ABI for the platform (including standard character encodings) which GCC follows; these are listed as "determined by ABI" below. *Note Binary Compatibility: ! Compatibility, and `http://gcc.gnu.org/readings.html'. Some choices ! are documented in the preprocessor manual. *Note ! Implementation-defined behavior: (cpp)Implementation-defined behavior. ! Some choices are documented in the corresponding document for the C ! language. *Note C Implementation::. Some choices are made by the ! library and operating system (or other environment when compiling for a ! freestanding environment); refer to their documentation for details. * Menu: *************** File: gcc.info, Node: Conditionally-sup *** 23900,23928 **** 5.1 Conditionally-Supported Behavior ==================================== ! 'Each implementation shall include documentation that identifies all conditionally-supported constructs that it does not support (C++0x 1.4).' ! * 'Whether an argument of class type with a non-trivial copy constructor or destructor can be passed to ... (C++0x 5.2.2).' Such argument passing is supported, using the same pass-by-invisible-reference approach used for normal function arguments of such types.  File: gcc.info, Node: Exception handling, Prev: Conditionally-supported behavior, Up: C++ Implementation 5.2 Exception Handling ====================== ! * 'In the situation where no matching handler is found, it is implementation-defined whether or not the stack is unwound before std::terminate() is called (C++98 15.5.1).' The stack is not unwound before std::terminate is called.  File: gcc.info, Node: C Extensions, Next: C++ Extensions, Prev: C++ Implementation, Up: Top --- 24048,24078 ---- 5.1 Conditionally-Supported Behavior ==================================== ! `Each implementation shall include documentation that identifies all conditionally-supported constructs that it does not support (C++0x 1.4).' ! * `Whether an argument of class type with a non-trivial copy constructor or destructor can be passed to ... (C++0x 5.2.2).' Such argument passing is supported, using the same pass-by-invisible-reference approach used for normal function arguments of such types. +  File: gcc.info, Node: Exception handling, Prev: Conditionally-supported behavior, Up: C++ Implementation 5.2 Exception Handling ====================== ! * `In the situation where no matching handler is found, it is implementation-defined whether or not the stack is unwound before std::terminate() is called (C++98 15.5.1).' The stack is not unwound before std::terminate is called. +  File: gcc.info, Node: C Extensions, Next: C++ Extensions, Prev: C++ Implementation, Up: Top *************** File: gcc.info, Node: C Extensions, Ne *** 23930,23939 **** ************************************* 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 Objective-C. Most of them are also available in C++. *Note Extensions to the C++ Language: C++ --- 24080,24089 ---- ************************************* 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 Objective-C. Most of them are also available in C++. *Note Extensions to the C++ Language: C++ *************** extensions, accepted by GCC in C90 mode *** 23949,23958 **** * Labels as Values:: Getting pointers to labels, and computed gotos. * Nested Functions:: As in Algol and Pascal, lexical scoping of functions. * Constructing Calls:: Dispatching a call to another function. ! * Typeof:: 'typeof': referring to the type of an expression. ! * Conditionals:: Omitting the middle operand of a '?:' expression. ! * __int128:: 128-bit integers--'__int128'. ! * Long Long:: Double-word integers--'long long int'. * Complex:: Data types for complex numbers. * Floating Types:: Additional Floating Types. * Half-Precision:: Half-Precision Floating Point. --- 24099,24108 ---- * Labels as Values:: Getting pointers to labels, and computed gotos. * Nested Functions:: As in Algol and Pascal, lexical scoping of functions. * Constructing Calls:: Dispatching a call to another function. ! * Typeof:: `typeof': referring to the type of an expression. ! * Conditionals:: Omitting the middle operand of a `?:' expression. ! * __int128:: 128-bit integers---`__int128'. ! * Long Long:: Double-word integers---`long long int'. * Complex:: Data types for complex numbers. * Floating Types:: Additional Floating Types. * Half-Precision:: Half-Precision Floating Point. *************** extensions, accepted by GCC in C90 mode *** 23966,23978 **** * Variadic Macros:: Macros with a variable number of arguments. * Escaped Newlines:: Slightly looser rules for escaped newlines. * Subscripting:: Any array can be subscripted, even if not an lvalue. ! * Pointer Arith:: Arithmetic on 'void'-pointers and function pointers. * Pointers to Arrays:: Pointers to arrays with qualifiers work as expected. * Initializers:: Non-constant initializers. * Compound Literals:: Compound literals give structures, unions or arrays as values. * Designated Inits:: Labeling elements of initializers. ! * Case Ranges:: 'case 1 ... 9' and such. * Cast to Union:: Casting to union type from any member of the union. * Mixed Declarations:: Mixing declarations and code. * Function Attributes:: Declaring that functions have no side effects, --- 24116,24128 ---- * Variadic Macros:: Macros with a variable number of arguments. * Escaped Newlines:: Slightly looser rules for escaped newlines. * Subscripting:: Any array can be subscripted, even if not an lvalue. ! * Pointer Arith:: Arithmetic on `void'-pointers and function pointers. * Pointers to Arrays:: Pointers to arrays with qualifiers work as expected. * Initializers:: Non-constant initializers. * Compound Literals:: Compound literals give structures, unions or arrays as values. * Designated Inits:: Labeling elements of initializers. ! * Case Ranges:: `case 1 ... 9' and such. * Cast to Union:: Casting to union type from any member of the union. * Mixed Declarations:: Mixing declarations and code. * Function Attributes:: Declaring that functions have no side effects, *************** extensions, accepted by GCC in C90 mode *** 23985,24002 **** * Function Prototypes:: Prototype declarations and old-style definitions. * C++ Comments:: C++ comments are recognized. * Dollar Signs:: Dollar sign is allowed in identifiers. ! * Character Escapes:: '\e' stands for the character . * Alignment:: Inquiring about the alignment of a type or variable. * Inline:: Defining inline functions (as fast as macros). * Volatiles:: What constitutes an access to a volatile object. * Using Assembly Language with C:: Instructions and extensions for interfacing C with assembler. ! * Alternate Keywords:: '__const__', '__asm__', etc., for header files. ! * Incomplete Enums:: 'enum foo;', with details to follow. * Function Names:: Printable strings which are the name of the current function. * Return Address:: Getting the return or frame address of a function. * Vector Extensions:: Using vector instructions through built-in functions. ! * Offsetof:: Special syntax for implementing 'offsetof'. * __sync Builtins:: Legacy built-in functions for atomic memory access. * __atomic Builtins:: Atomic built-in functions with memory model. * Integer Overflow Builtins:: Built-in functions to perform arithmetics and --- 24135,24152 ---- * Function Prototypes:: Prototype declarations and old-style definitions. * C++ Comments:: C++ comments are recognized. * Dollar Signs:: Dollar sign is allowed in identifiers. ! * Character Escapes:: `\e' stands for the character . * Alignment:: Inquiring about the alignment of a type or variable. * Inline:: Defining inline functions (as fast as macros). * Volatiles:: What constitutes an access to a volatile object. * Using Assembly Language with C:: Instructions and extensions for interfacing C with assembler. ! * Alternate Keywords:: `__const__', `__asm__', etc., for header files. ! * Incomplete Enums:: `enum foo;', with details to follow. * Function Names:: Printable strings which are the name of the current function. * Return Address:: Getting the return or frame address of a function. * Vector Extensions:: Using vector instructions through built-in functions. ! * Offsetof:: Special syntax for implementing `offsetof'. * __sync Builtins:: Legacy built-in functions for atomic memory access. * __atomic Builtins:: Atomic built-in functions with memory model. * Integer Overflow Builtins:: Built-in functions to perform arithmetics and *************** extensions, accepted by GCC in C90 mode *** 24012,24018 **** * Pragmas:: Pragmas accepted by GCC. * Unnamed Fields:: Unnamed struct/union fields within structs/unions. * Thread-Local:: Per-thread variables. ! * Binary constants:: Binary constants using the '0b' prefix.  File: gcc.info, Node: Statement Exprs, Next: Local Labels, Up: C Extensions --- 24162,24168 ---- * Pragmas:: Pragmas accepted by GCC. * Unnamed Fields:: Unnamed struct/union fields within structs/unions. * Thread-Local:: Per-thread variables. ! * Binary constants:: Binary constants using the `0b' prefix.  File: gcc.info, Node: Statement Exprs, Next: Local Labels, Up: C Extensions *************** example: *** 24034,24045 **** z; }) is a valid (though slightly more complex than necessary) expression for ! the absolute value of 'foo ()'. The last thing in the compound statement should be an expression followed by a semicolon; the value of this subexpression serves as the value of the entire construct. (If you use some other kind of statement ! last within the braces, the construct has type 'void', and thus effectively no value.) This feature is especially useful in making macro definitions "safe" --- 24184,24195 ---- z; }) is a valid (though slightly more complex than necessary) expression for ! the absolute value of `foo ()'. The last thing in the compound statement should be an expression followed by a semicolon; the value of this subexpression serves as the value of the entire construct. (If you use some other kind of statement ! last within the braces, the construct has type `void', and thus effectively no value.) This feature is especially useful in making macro definitions "safe" *************** follows: *** 24051,24057 **** But this definition computes either A or B twice, with bad results if the operand has side effects. In GNU C, if you know the type of the ! operands (here taken as 'int'), you can define the macro safely as follows: #define maxint(a,b) \ --- 24201,24207 ---- But this definition computes either A or B twice, with bad results if the operand has side effects. In GNU C, if you know the type of the ! operands (here taken as `int'), you can define the macro safely as follows: #define maxint(a,b) \ *************** the value of an enumeration constant, th *** 24062,24088 **** initial value of a static variable. If you don't know the type of the operand, you can still do this, but ! you must use 'typeof' or '__auto_type' (*note Typeof::). In G++, the result value of a statement expression undergoes array and function pointer decay, and is returned by value to the enclosing ! expression. For instance, if 'A' is a class, then A a; ({a;}).Foo () ! constructs a temporary 'A' object to hold the result of the statement ! expression, and that is used to invoke 'Foo'. Therefore the 'this' ! pointer observed by 'Foo' is not the address of 'a'. In a statement expression, any temporaries created within a statement ! are destroyed at that statement's end. This makes statement expressions ! inside macros slightly different from function calls. In the latter ! case temporaries introduced during argument evaluation are destroyed at ! the end of the statement that includes the function call. In the ! statement expression case they are destroyed during the statement ! expression. For instance, #define macro(a) ({__typeof__(a) b = (a); b + 3; }) template T function(T a) { T b = a; return b + 3; } --- 24212,24238 ---- initial value of a static variable. If you don't know the type of the operand, you can still do this, but ! you must use `typeof' or `__auto_type' (*note Typeof::). In G++, the result value of a statement expression undergoes array and function pointer decay, and is returned by value to the enclosing ! expression. For instance, if `A' is a class, then A a; ({a;}).Foo () ! constructs a temporary `A' object to hold the result of the statement ! expression, and that is used to invoke `Foo'. Therefore the `this' ! pointer observed by `Foo' is not the address of `a'. In a statement expression, any temporaries created within a statement ! are destroyed at that statement's end. This makes statement ! expressions inside macros slightly different from function calls. In ! the latter case temporaries introduced during argument evaluation are ! destroyed at the end of the statement that includes the function call. ! In the statement expression case they are destroyed during the ! statement expression. For instance, #define macro(a) ({__typeof__(a) b = (a); b + 3; }) template T function(T a) { T b = a; return b + 3; } *************** expression. For instance, *** 24093,24101 **** function (X ()); } ! has different places where temporaries are destroyed. For the 'macro' ! case, the temporary 'X' is destroyed just after the initialization of ! 'b'. In the 'function' case that temporary is destroyed when the function returns. These considerations mean that it is probably a bad idea to use --- 24243,24251 ---- function (X ()); } ! has different places where temporaries are destroyed. For the `macro' ! case, the temporary `X' is destroyed just after the initialization of ! `b'. In the `function' case that temporary is destroyed when the function returns. These considerations mean that it is probably a bad idea to use *************** work with C++. (Note that some versions *** 24104,24113 **** header files using statement expressions that lead to precisely this bug.) ! Jumping into a statement expression with 'goto' or using a 'switch' ! statement outside the statement expression with a 'case' or 'default' label inside the statement expression is not permitted. Jumping into a ! statement expression with a computed 'goto' (*note Labels as Values::) has undefined behavior. Jumping out of a statement expression is permitted, but if the statement expression is part of a larger expression then it is unspecified which other subexpressions of that --- 24254,24263 ---- header files using statement expressions that lead to precisely this bug.) ! Jumping into a statement expression with `goto' or using a `switch' ! statement outside the statement expression with a `case' or `default' label inside the statement expression is not permitted. Jumping into a ! statement expression with a computed `goto' (*note Labels as Values::) has undefined behavior. Jumping out of a statement expression is permitted, but if the statement expression is part of a larger expression then it is unspecified which other subexpressions of that *************** evaluation of other parts of the contain *** 24119,24127 **** foo (), (({ bar1 (); goto a; 0; }) + bar2 ()), baz(); ! calls 'foo' and 'bar1' and does not call 'baz' but may or may not call ! 'bar2'. If 'bar2' is called, it is called after 'foo' and before ! 'bar1'.  File: gcc.info, Node: Local Labels, Next: Labels as Values, Prev: Statement Exprs, Up: C Extensions --- 24269,24277 ---- foo (), (({ bar1 (); goto a; 0; }) + bar2 ()), baz(); ! calls `foo' and `bar1' and does not call `baz' but may or may not call ! `bar2'. If `bar2' is called, it is called after `foo' and before ! `bar1'.  File: gcc.info, Node: Local Labels, Next: Labels as Values, Prev: Statement Exprs, Up: C Extensions *************** File: gcc.info, Node: Local Labels, Ne *** 24131,24137 **** GCC allows you to declare "local labels" in any nested block scope. A local label is just like an ordinary label, but you can only reference ! it (with a 'goto' statement, or by taking its address) within the block in which it is declared. A local label declaration looks like this: --- 24281,24287 ---- GCC allows you to declare "local labels" in any nested block scope. A local label is just like an ordinary label, but you can only reference ! it (with a `goto' statement, or by taking its address) within the block in which it is declared. A local label declaration looks like this: *************** or *** 24145,24156 **** Local label declarations must come at the beginning of the block, before any ordinary declarations or statements. ! The label declaration defines the label _name_, but does not define the ! label itself. You must do this in the usual way, with 'LABEL:', within ! the statements of the statement expression. The local label feature is useful for complex macros. If a macro ! contains nested loops, a 'goto' can be useful for breaking out of them. However, an ordinary label whose scope is the whole function cannot be used: if the macro can be expanded several times in one function, the label is multiply defined in that function. A local label avoids this --- 24295,24306 ---- Local label declarations must come at the beginning of the block, before any ordinary declarations or statements. ! The label declaration defines the label _name_, but does not define ! the label itself. You must do this in the usual way, with `LABEL:', ! within the statements of the statement expression. The local label feature is useful for complex macros. If a macro ! contains nested loops, a `goto' can be useful for breaking out of them. However, an ordinary label whose scope is the whole function cannot be used: if the macro can be expanded several times in one function, the label is multiply defined in that function. A local label avoids this *************** File: gcc.info, Node: Labels as Values, *** 24199,24219 **** 6.3 Labels as Values ==================== ! You can get the address of a label defined in the current function (or a ! containing function) with the unary operator '&&'. The value has type ! 'void *'. This value is a constant and can be used wherever a constant ! of that type is valid. For example: void *ptr; /* ... */ ptr = &&foo; To use these values, you need to be able to jump to one. This is done ! with the computed goto statement(1), 'goto *EXP;'. For example, goto *ptr; ! Any expression of type 'void *' is allowed. One way of using these constants is in initializing a static array that serves as a jump table: --- 24349,24369 ---- 6.3 Labels as Values ==================== ! You can get the address of a label defined in the current function (or ! a containing function) with the unary operator `&&'. The value has ! type `void *'. This value is a constant and can be used wherever a ! constant of that type is valid. For example: void *ptr; /* ... */ ptr = &&foo; To use these values, you need to be able to jump to one. This is done ! with the computed goto statement(1), `goto *EXP;'. For example, goto *ptr; ! Any expression of type `void *' is allowed. One way of using these constants is in initializing a static array that serves as a jump table: *************** Note that this does not check whether th *** 24228,24240 **** indexing in C never does that. Such an array of label values serves a purpose much like that of the ! 'switch' statement. The 'switch' statement is cleaner, so use that ! rather than an array unless the problem does not fit a 'switch' statement very well. Another use of label values is in an interpreter for threaded code. ! The labels within the interpreter function can be stored in the threaded ! code for super-fast dispatching. You may not use this mechanism to jump to code in a different function. If you do that, totally unpredictable things happen. The best way to --- 24378,24390 ---- indexing in C never does that. Such an array of label values serves a purpose much like that of the ! `switch' statement. The `switch' statement is cleaner, so use that ! rather than an array unless the problem does not fit a `switch' statement very well. Another use of label values is in an interpreter for threaded code. ! The labels within the interpreter function can be stored in the ! threaded code for super-fast dispatching. You may not use this mechanism to jump to code in a different function. If you do that, totally unpredictable things happen. The best way to *************** allows the data to be read-only. This a *** 24253,24267 **** differences is not supported for the AVR target, please use the first approach for AVR programs. ! The '&&foo' expressions for the same label might have different values ! if the containing function is inlined or cloned. If a program relies on ! them being always the same, '__attribute__((__noinline__,__noclone__))' ! should be used to prevent inlining and cloning. If '&&foo' is used in a ! static variable initializer, inlining and cloning is forbidden. ! ---------- Footnotes ---------- ! (1) The analogous feature in Fortran is called an assigned goto, but that name seems inappropriate in C, where one can do more than simply store label addresses in label variables. --- 24403,24418 ---- differences is not supported for the AVR target, please use the first approach for AVR programs. ! The `&&foo' expressions for the same label might have different values ! if the containing function is inlined or cloned. If a program relies ! on them being always the same, ! `__attribute__((__noinline__,__noclone__))' should be used to prevent ! inlining and cloning. If `&&foo' is used in a static variable ! initializer, inlining and cloning is forbidden. ! ---------- Footnotes ---------- ! (1) The analogous feature in Fortran is called an assigned goto, but that name seems inappropriate in C, where one can do more than simply store label addresses in label variables. *************** Nested functions are supported as an ext *** 24276,24282 **** supported by GNU C++. The nested function's name is local to the block where it is defined. ! For example, here we define a nested function named 'square', and call it twice: foo (double a, double b) --- 24427,24433 ---- supported by GNU C++. The nested function's name is local to the block where it is defined. ! For example, here we define a nested function named `square', and call it twice: foo (double a, double b) *************** it twice: *** 24289,24295 **** The nested function can access all the variables of the containing function that are visible at the point of its definition. This is called "lexical scoping". For example, here we show a nested function ! which uses an inherited variable named 'offset': bar (int *array, int offset, int size) { --- 24440,24446 ---- The nested function can access all the variables of the containing function that are visible at the point of its definition. This is called "lexical scoping". For example, here we show a nested function ! which uses an inherited variable named `offset': bar (int *array, int offset, int size) { *************** function: *** 24317,24345 **** intermediate (store, size); } ! Here, the function 'intermediate' receives the address of 'store' as an ! argument. If 'intermediate' calls 'store', the arguments given to ! 'store' are used to store into 'array'. But this technique works only ! so long as the containing function ('hack', in this example) does not exit. If you try to call the nested function through its address after the ! containing function exits, all hell breaks loose. If you try to call it ! after a containing scope level exits, and if it refers to some of the ! variables that are no longer in scope, you may be lucky, but it's not ! wise to take the risk. If, however, the nested function does not refer ! to anything that has gone out of scope, you should be safe. GCC implements taking the address of a nested function using a technique called "trampolines". This technique was described in ! 'Lexical Closures for C++' (Thomas M. Breuel, USENIX C++ Conference Proceedings, October 17-21, 1988). A nested function can jump to a label inherited from a containing function, provided the label is explicitly declared in the containing function (*note Local Labels::). Such a jump returns instantly to the ! containing function, exiting the nested function that did the 'goto' and ! any intermediate functions as well. Here is an example: bar (int *array, int offset, int size) { --- 24468,24496 ---- intermediate (store, size); } ! Here, the function `intermediate' receives the address of `store' as ! an argument. If `intermediate' calls `store', the arguments given to ! `store' are used to store into `array'. But this technique works only ! so long as the containing function (`hack', in this example) does not exit. If you try to call the nested function through its address after the ! containing function exits, all hell breaks loose. If you try to call ! it after a containing scope level exits, and if it refers to some of ! the variables that are no longer in scope, you may be lucky, but it's ! not wise to take the risk. If, however, the nested function does not ! refer to anything that has gone out of scope, you should be safe. GCC implements taking the address of a nested function using a technique called "trampolines". This technique was described in ! `Lexical Closures for C++' (Thomas M. Breuel, USENIX C++ Conference Proceedings, October 17-21, 1988). A nested function can jump to a label inherited from a containing function, provided the label is explicitly declared in the containing function (*note Local Labels::). Such a jump returns instantly to the ! containing function, exiting the nested function that did the `goto' ! and any intermediate functions as well. Here is an example: bar (int *array, int offset, int size) { *************** any intermediate functions as well. Her *** 24357,24371 **** /* ... */ return 0; ! /* Control comes here from 'access' if it detects an error. */ failure: return -1; } ! A nested function always has no linkage. Declaring one with 'extern' ! or 'static' is erroneous. If you need to declare the nested function ! before its definition, use 'auto' (which is otherwise meaningless for function declarations). bar (int *array, int offset, int size) --- 24508,24522 ---- /* ... */ return 0; ! /* Control comes here from `access' if it detects an error. */ failure: return -1; } ! A nested function always has no linkage. Declaring one with `extern' ! or `static' is erroneous. If you need to declare the nested function ! before its definition, use `auto' (which is otherwise meaningless for function declarations). bar (int *array, int offset, int size) *************** acting as mere forwarders for their argu *** 24403,24410 **** -- Built-in Function: void * __builtin_apply_args () This built-in function returns a pointer to data describing how to ! perform a call with the same arguments as are passed to the current ! function. The function saves the arg pointer register, structure value address, and all registers that might be used to pass arguments to --- 24554,24561 ---- -- Built-in Function: void * __builtin_apply_args () This built-in function returns a pointer to data describing how to ! perform a call with the same arguments as are passed to the ! current function. The function saves the arg pointer register, structure value address, and all registers that might be used to pass arguments to *************** acting as mere forwarders for their argu *** 24417,24423 **** parameters described by ARGUMENTS and SIZE. The value of ARGUMENTS should be the value returned by ! '__builtin_apply_args'. The argument SIZE specifies the size of the stack argument data, in bytes. This function returns a pointer to data describing how to return --- 24568,24574 ---- parameters described by ARGUMENTS and SIZE. The value of ARGUMENTS should be the value returned by ! `__builtin_apply_args'. The argument SIZE specifies the size of the stack argument data, in bytes. This function returns a pointer to data describing how to return *************** acting as mere forwarders for their argu *** 24425,24449 **** block of memory allocated on the stack. It is not always simple to compute the proper value for SIZE. The ! value is used by '__builtin_apply' to compute the amount of data that should be pushed on the stack and copied from the incoming argument area. -- Built-in Function: void __builtin_return (void *RESULT) This built-in function returns the value described by RESULT from the containing function. You should specify, for RESULT, a value ! returned by '__builtin_apply'. ! -- Built-in Function: __builtin_va_arg_pack () This built-in function represents all anonymous arguments of an inline function. It can be used only in inline functions that are always inlined, never compiled as a separate function, such as ! those using '__attribute__ ((__always_inline__))' or '__attribute__ ! ((__gnu_inline__))' extern inline functions. It must be only ! passed as last argument to some other function with variable ! arguments. This is useful for writing small wrapper inlines for ! variable argument functions, when using preprocessor macros is ! undesirable. For example: extern int myprintf (FILE *f, const char *format, ...); extern inline __attribute__ ((__gnu_inline__)) int myprintf (FILE *f, const char *format, ...) --- 24576,24600 ---- block of memory allocated on the stack. It is not always simple to compute the proper value for SIZE. The ! value is used by `__builtin_apply' to compute the amount of data that should be pushed on the stack and copied from the incoming argument area. -- Built-in Function: void __builtin_return (void *RESULT) This built-in function returns the value described by RESULT from the containing function. You should specify, for RESULT, a value ! returned by `__builtin_apply'. ! -- Built-in Function: __builtin_va_arg_pack () This built-in function represents all anonymous arguments of an inline function. It can be used only in inline functions that are always inlined, never compiled as a separate function, such as ! those using `__attribute__ ((__always_inline__))' or ! `__attribute__ ((__gnu_inline__))' extern inline functions. It ! must be only passed as last argument to some other function with ! variable arguments. This is useful for writing small wrapper ! inlines for variable argument functions, when using preprocessor ! macros is undesirable. For example: extern int myprintf (FILE *f, const char *format, ...); extern inline __attribute__ ((__gnu_inline__)) int myprintf (FILE *f, const char *format, ...) *************** acting as mere forwarders for their argu *** 24461,24470 **** This built-in function returns the number of anonymous arguments of an inline function. It can be used only in inline functions that are always inlined, never compiled as a separate function, such as ! those using '__attribute__ ((__always_inline__))' or '__attribute__ ! ((__gnu_inline__))' extern inline functions. For example following ! does link- or run-time checking of open arguments for optimized ! code: #ifdef __OPTIMIZE__ extern inline __attribute__((__gnu_inline__)) int myopen (const char *path, int oflag, ...) --- 24612,24621 ---- This built-in function returns the number of anonymous arguments of an inline function. It can be used only in inline functions that are always inlined, never compiled as a separate function, such as ! those using `__attribute__ ((__always_inline__))' or ! `__attribute__ ((__gnu_inline__))' extern inline functions. For ! example following does link- or run-time checking of open ! arguments for optimized code: #ifdef __OPTIMIZE__ extern inline __attribute__((__gnu_inline__)) int myopen (const char *path, int oflag, ...) *************** acting as mere forwarders for their argu *** 24492,24531 ****  File: gcc.info, Node: Typeof, Next: Conditionals, Prev: Constructing Calls, Up: C Extensions ! 6.6 Referring to a Type with 'typeof' ===================================== ! Another way to refer to the type of an expression is with 'typeof'. The ! syntax of using of this keyword looks like 'sizeof', but the construct ! acts semantically like a type name defined with 'typedef'. ! There are two ways of writing the argument to 'typeof': with an expression or with a type. Here is an example with an expression: typeof (x[0](1)) ! This assumes that 'x' is an array of pointers to functions; the type described is that of the values of the functions. Here is an example with a typename as the argument: typeof (int *) ! Here the type described is that of pointers to 'int'. If you are writing a header file that must work when included in ISO C ! programs, write '__typeof__' instead of 'typeof'. *Note Alternate Keywords::. ! A 'typeof' construct can be used anywhere a typedef name can be used. For example, you can use it in a declaration, in a cast, or inside of ! 'sizeof' or 'typeof'. ! The operand of 'typeof' is evaluated for its side effects if and only if it is an expression of variably modified type or the name of such a type. ! 'typeof' is often useful in conjunction with statement expressions (*note Statement Exprs::). Here is how the two together can be used to define a safe "maximum" macro which operates on any arithmetic type and evaluates each of its arguments exactly once: --- 24643,24682 ----  File: gcc.info, Node: Typeof, Next: Conditionals, Prev: Constructing Calls, Up: C Extensions ! 6.6 Referring to a Type with `typeof' ===================================== ! Another way to refer to the type of an expression is with `typeof'. ! The syntax of using of this keyword looks like `sizeof', but the ! construct acts semantically like a type name defined with `typedef'. ! There are two ways of writing the argument to `typeof': with an expression or with a type. Here is an example with an expression: typeof (x[0](1)) ! This assumes that `x' is an array of pointers to functions; the type described is that of the values of the functions. Here is an example with a typename as the argument: typeof (int *) ! Here the type described is that of pointers to `int'. If you are writing a header file that must work when included in ISO C ! programs, write `__typeof__' instead of `typeof'. *Note Alternate Keywords::. ! A `typeof' construct can be used anywhere a typedef name can be used. For example, you can use it in a declaration, in a cast, or inside of ! `sizeof' or `typeof'. ! The operand of `typeof' is evaluated for its side effects if and only if it is an expression of variably modified type or the name of such a type. ! `typeof' is often useful in conjunction with statement expressions (*note Statement Exprs::). Here is how the two together can be used to define a safe "maximum" macro which operates on any arithmetic type and evaluates each of its arguments exactly once: *************** evaluates each of its arguments exactly *** 24537,24558 **** The reason for using names that start with underscores for the local variables is to avoid conflicts with variable names that occur within ! the expressions that are substituted for 'a' and 'b'. Eventually we hope to design a new form of declaration syntax that allows you to ! declare variables whose scopes start only after their initializers; this ! will be a more reliable way to prevent such conflicts. ! Some more examples of the use of 'typeof': ! * This declares 'y' with the type of what 'x' points to. typeof (*x) y; ! * This declares 'y' as an array of such values. typeof (*x) y[4]; ! * This declares 'y' as an array of pointers to characters: typeof (typeof (char *)[4]) y; --- 24688,24709 ---- The reason for using names that start with underscores for the local variables is to avoid conflicts with variable names that occur within ! the expressions that are substituted for `a' and `b'. Eventually we hope to design a new form of declaration syntax that allows you to ! declare variables whose scopes start only after their initializers; ! this will be a more reliable way to prevent such conflicts. ! Some more examples of the use of `typeof': ! * This declares `y' with the type of what `x' points to. typeof (*x) y; ! * This declares `y' as an array of such values. typeof (*x) y[4]; ! * This declares `y' as an array of pointers to characters: typeof (typeof (char *)[4]) y; *************** Some more examples of the use of 'typeof *** 24560,24566 **** char *y[4]; ! To see the meaning of the declaration using 'typeof', and why it might be a useful way to write, rewrite it with these macros: #define pointer(T) typeof(T *) --- 24711,24717 ---- char *y[4]; ! To see the meaning of the declaration using `typeof', and why it might be a useful way to write, rewrite it with these macros: #define pointer(T) typeof(T *) *************** Some more examples of the use of 'typeof *** 24570,24601 **** array (pointer (char), 4) y; ! Thus, 'array (pointer (char), 4)' is the type of arrays of 4 ! pointers to 'char'. In GNU C, but not GNU C++, you may also declare the type of a variable ! as '__auto_type'. In that case, the declaration must declare only one variable, whose declarator must just be an identifier, the declaration must be initialized, and the type of the variable is determined by the initializer; the name of the variable is not in scope until after the ! initializer. (In C++, you should use C++11 'auto' for this purpose.) ! Using '__auto_type', the "maximum" macro above could be written as: #define max(a,b) \ ({ __auto_type _a = (a); \ __auto_type _b = (b); \ _a > _b ? _a : _b; }) ! Using '__auto_type' instead of 'typeof' has two advantages: * Each argument to the macro appears only once in the expansion of the macro. This prevents the size of the macro expansion growing ! exponentially when calls to such macros are nested inside arguments ! of such macros. * If the argument to the macro has variably modified type, it is ! evaluated only once when using '__auto_type', but twice if 'typeof' ! is used.  File: gcc.info, Node: Conditionals, Next: __int128, Prev: Typeof, Up: C Extensions --- 24721,24752 ---- array (pointer (char), 4) y; ! Thus, `array (pointer (char), 4)' is the type of arrays of 4 ! pointers to `char'. In GNU C, but not GNU C++, you may also declare the type of a variable ! as `__auto_type'. In that case, the declaration must declare only one variable, whose declarator must just be an identifier, the declaration must be initialized, and the type of the variable is determined by the initializer; the name of the variable is not in scope until after the ! initializer. (In C++, you should use C++11 `auto' for this purpose.) ! Using `__auto_type', the "maximum" macro above could be written as: #define max(a,b) \ ({ __auto_type _a = (a); \ __auto_type _b = (b); \ _a > _b ? _a : _b; }) ! Using `__auto_type' instead of `typeof' has two advantages: * Each argument to the macro appears only once in the expansion of the macro. This prevents the size of the macro expansion growing ! exponentially when calls to such macros are nested inside ! arguments of such macros. * If the argument to the macro has variably modified type, it is ! evaluated only once when using `__auto_type', but twice if ! `typeof' is used.  File: gcc.info, Node: Conditionals, Next: __int128, Prev: Typeof, Up: C Extensions *************** expression. *** 24611,24617 **** x ? : y ! has the value of 'x' if that is nonzero; otherwise, the value of 'y'. This example is perfectly equivalent to --- 24762,24768 ---- x ? : y ! has the value of `x' if that is nonzero; otherwise, the value of `y'. This example is perfectly equivalent to *************** has the value of 'x' if that is nonzero; *** 24620,24628 **** In this simple case, the ability to omit the middle operand is not especially useful. When it becomes useful is when the first operand does, or may (if it is a macro argument), contain a side effect. Then ! repeating the operand in the middle would perform the side effect twice. ! Omitting the middle operand uses the value already computed without the ! undesirable effects of recomputing it.  File: gcc.info, Node: __int128, Next: Long Long, Prev: Conditionals, Up: C Extensions --- 24771,24779 ---- In this simple case, the ability to omit the middle operand is not especially useful. When it becomes useful is when the first operand does, or may (if it is a macro argument), contain a side effect. Then ! repeating the operand in the middle would perform the side effect ! twice. Omitting the middle operand uses the value already computed ! without the undesirable effects of recomputing it.  File: gcc.info, Node: __int128, Next: Long Long, Prev: Conditionals, Up: C Extensions *************** File: gcc.info, Node: __int128, Next: *** 24630,24641 **** 6.8 128-bit Integers ==================== ! As an extension the integer scalar type '__int128' is supported for ! targets which have an integer mode wide enough to hold 128 bits. Simply ! write '__int128' for a signed 128-bit integer, or 'unsigned __int128' ! for an unsigned 128-bit integer. There is no support in GCC for ! expressing an integer constant of type '__int128' for targets with 'long ! long' integer less than 128 bits wide.  File: gcc.info, Node: Long Long, Next: Complex, Prev: __int128, Up: C Extensions --- 24781,24792 ---- 6.8 128-bit Integers ==================== ! As an extension the integer scalar type `__int128' is supported for ! targets which have an integer mode wide enough to hold 128 bits. ! Simply write `__int128' for a signed 128-bit integer, or `unsigned ! __int128' for an unsigned 128-bit integer. There is no support in GCC ! for expressing an integer constant of type `__int128' for targets with ! `long long' integer less than 128 bits wide.  File: gcc.info, Node: Long Long, Next: Complex, Prev: __int128, Up: C Extensions *************** File: gcc.info, Node: Long Long, Next: *** 24645,24670 **** ISO C99 supports data types for integers that are at least 64 bits wide, and as an extension GCC supports them in C90 mode and in C++. Simply ! write 'long long int' for a signed integer, or 'unsigned long long int' ! for an unsigned integer. To make an integer constant of type 'long long ! int', add the suffix 'LL' to the integer. To make an integer constant ! of type 'unsigned long long int', add the suffix 'ULL' to the integer. You can use these types in arithmetic like any other integer types. ! Addition, subtraction, and bitwise boolean operations on these types are ! open-coded on all types of machines. Multiplication is open-coded if ! the machine supports a fullword-to-doubleword widening multiply instruction. Division and shifts are open-coded only on machines that provide special support. The operations that are not open-coded use special library routines that come with GCC. ! There may be pitfalls when you use 'long long' types for function ! arguments without function prototypes. If a function expects type 'int' ! for its argument, and you pass a value of type 'long long int', confusion results because the caller and the subroutine disagree about ! the number of bytes for the argument. Likewise, if the function expects ! 'long long int' and you pass 'int'. The best way to avoid such problems ! is to use prototypes.  File: gcc.info, Node: Complex, Next: Floating Types, Prev: Long Long, Up: C Extensions --- 24796,24822 ---- ISO C99 supports data types for integers that are at least 64 bits wide, and as an extension GCC supports them in C90 mode and in C++. Simply ! write `long long int' for a signed integer, or `unsigned long long int' ! for an unsigned integer. To make an integer constant of type `long ! long int', add the suffix `LL' to the integer. To make an integer ! constant of type `unsigned long long int', add the suffix `ULL' to the ! integer. You can use these types in arithmetic like any other integer types. ! Addition, subtraction, and bitwise boolean operations on these types ! are open-coded on all types of machines. Multiplication is open-coded ! if the machine supports a fullword-to-doubleword widening multiply instruction. Division and shifts are open-coded only on machines that provide special support. The operations that are not open-coded use special library routines that come with GCC. ! There may be pitfalls when you use `long long' types for function ! arguments without function prototypes. If a function expects type ! `int' for its argument, and you pass a value of type `long long int', confusion results because the caller and the subroutine disagree about ! the number of bytes for the argument. Likewise, if the function ! expects `long long int' and you pass `int'. The best way to avoid such ! problems is to use prototypes.  File: gcc.info, Node: Complex, Next: Floating Types, Prev: Long Long, Up: C Extensions *************** File: gcc.info, Node: Complex, Next: F *** 24673,24709 **** ==================== ISO C99 supports complex floating data types, and as an extension GCC ! supports them in C90 mode and in C++. GCC also supports complex integer ! data types which are not part of ISO C99. You can declare complex types ! using the keyword '_Complex'. As an extension, the older GNU keyword ! '__complex__' is also supported. ! For example, '_Complex double x;' declares 'x' as a variable whose real ! part and imaginary part are both of type 'double'. '_Complex short int ! y;' declares 'y' to have real and imaginary parts of type 'short int'; ! this is not likely to be useful, but it shows that the set of complex ! types is complete. ! To write a constant with a complex data type, use the suffix 'i' or 'j' ! (either one; they are equivalent). For example, '2.5fi' has type ! '_Complex float' and '3i' has type '_Complex int'. Such a constant always has a pure imaginary value, but you can form any complex value you like by adding one to a real constant. This is a GNU extension; if you have an ISO C99 conforming C library (such as the GNU C Library), and want to construct complex constants of floating type, you should ! include '' and use the macros 'I' or '_Complex_I' instead. To extract the real part of a complex-valued expression EXP, write ! '__real__ EXP'. Likewise, use '__imag__' to extract the imaginary part. ! This is a GNU extension; for values of floating type, you should use the ! ISO C99 functions 'crealf', 'creal', 'creall', 'cimagf', 'cimag' and ! 'cimagl', declared in '' and also provided as built-in ! functions by GCC. ! The operator '~' performs complex conjugation when used on a value with ! a complex type. This is a GNU extension; for values of floating type, ! you should use the ISO C99 functions 'conjf', 'conj' and 'conjl', ! declared in '' and also provided as built-in functions by GCC. GCC can allocate complex automatic variables in a noncontiguous --- 24825,24861 ---- ==================== ISO C99 supports complex floating data types, and as an extension GCC ! supports them in C90 mode and in C++. GCC also supports complex ! integer data types which are not part of ISO C99. You can declare ! complex types using the keyword `_Complex'. As an extension, the older ! GNU keyword `__complex__' is also supported. ! For example, `_Complex double x;' declares `x' as a variable whose ! real part and imaginary part are both of type `double'. `_Complex ! short int y;' declares `y' to have real and imaginary parts of type ! `short int'; this is not likely to be useful, but it shows that the set ! of complex types is complete. ! To write a constant with a complex data type, use the suffix `i' or ! `j' (either one; they are equivalent). For example, `2.5fi' has type ! `_Complex float' and `3i' has type `_Complex int'. Such a constant always has a pure imaginary value, but you can form any complex value you like by adding one to a real constant. This is a GNU extension; if you have an ISO C99 conforming C library (such as the GNU C Library), and want to construct complex constants of floating type, you should ! include `' and use the macros `I' or `_Complex_I' instead. To extract the real part of a complex-valued expression EXP, write ! `__real__ EXP'. Likewise, use `__imag__' to extract the imaginary ! part. This is a GNU extension; for values of floating type, you should ! use the ISO C99 functions `crealf', `creal', `creall', `cimagf', ! `cimag' and `cimagl', declared in `' and also provided as ! built-in functions by GCC. ! The operator `~' performs complex conjugation when used on a value ! with a complex type. This is a GNU extension; for values of floating ! type, you should use the ISO C99 functions `conjf', `conj' and `conjl', ! declared in `' and also provided as built-in functions by GCC. GCC can allocate complex automatic variables in a noncontiguous *************** the imaginary part is on the stack (or v *** 24712,24719 **** debug info format can represent this, so use of DWARF is recommended. If you are using the stabs debug info format, GCC describes a noncontiguous complex variable as if it were two separate variables of ! noncomplex type. If the variable's actual name is 'foo', the two ! fictitious variables are named 'foo$real' and 'foo$imag'. You can examine and set these two fictitious variables with your debugger.  --- 24864,24871 ---- debug info format can represent this, so use of DWARF is recommended. If you are using the stabs debug info format, GCC describes a noncontiguous complex variable as if it were two separate variables of ! noncomplex type. If the variable's actual name is `foo', the two ! fictitious variables are named `foo$real' and `foo$imag'. You can examine and set these two fictitious variables with your debugger.  *************** File: gcc.info, Node: Floating Types, *** 24722,24764 **** 6.11 Additional Floating Types ============================== ! As an extension, GNU C supports additional floating types, '__float80' ! and '__float128' to support 80-bit ('XFmode') and 128-bit ('TFmode') floating types. Support for additional types includes the arithmetic operators: add, subtract, multiply, divide; unary arithmetic operators; relational operators; equality operators; and conversions to and from ! integer and other floating types. Use a suffix 'w' or 'W' in a literal ! constant of type '__float80' or type '__ibm128'. Use a suffix 'q' or ! 'Q' for '_float128'. On the i386, x86_64, IA-64, and HP-UX targets, you can declare complex ! types using the corresponding internal complex type, 'XCmode' for ! '__float80' type and 'TCmode' for '__float128' type: typedef _Complex float __attribute__((mode(TC))) _Complex128; typedef _Complex float __attribute__((mode(XC))) _Complex80; ! In order to use '__float128' and '__ibm128' on PowerPC Linux systems, ! you must use the '-mfloat128'. It is expected in future versions of GCC ! that '__float128' will be enabled automatically. In addition, there are ! currently problems in using the complex '__float128' type. When these ! problems are fixed, you would use the following syntax to declare ! '_Complex128' to be a complex '__float128' type: On the PowerPC Linux VSX targets, you can declare complex types using ! the corresponding internal complex type, 'KCmode' for '__float128' type ! and 'ICmode' for '__ibm128' type: typedef _Complex float __attribute__((mode(KC))) _Complex_float128; typedef _Complex float __attribute__((mode(IC))) _Complex_ibm128; ! Not all targets support additional floating-point types. '__float80' ! and '__float128' types are supported on x86 and IA-64 targets. The ! '__float128' type is supported on hppa HP-UX. The '__float128' type is supported on PowerPC 64-bit Linux systems by default if the vector scalar instruction set (VSX) is enabled. ! On the PowerPC, '__ibm128' provides access to the IBM extended double format, and it is intended to be used by the library functions that handle conversions if/when long double is changed to be IEEE 128-bit floating point. --- 24874,24916 ---- 6.11 Additional Floating Types ============================== ! As an extension, GNU C supports additional floating types, `__float80' ! and `__float128' to support 80-bit (`XFmode') and 128-bit (`TFmode') floating types. Support for additional types includes the arithmetic operators: add, subtract, multiply, divide; unary arithmetic operators; relational operators; equality operators; and conversions to and from ! integer and other floating types. Use a suffix `w' or `W' in a literal ! constant of type `__float80' or type `__ibm128'. Use a suffix `q' or ! `Q' for `_float128'. On the i386, x86_64, IA-64, and HP-UX targets, you can declare complex ! types using the corresponding internal complex type, `XCmode' for ! `__float80' type and `TCmode' for `__float128' type: typedef _Complex float __attribute__((mode(TC))) _Complex128; typedef _Complex float __attribute__((mode(XC))) _Complex80; ! In order to use `__float128' and `__ibm128' on PowerPC Linux systems, ! you must use the `-mfloat128'. It is expected in future versions of GCC ! that `__float128' will be enabled automatically. In addition, there ! are currently problems in using the complex `__float128' type. When ! these problems are fixed, you would use the following syntax to declare ! `_Complex128' to be a complex `__float128' type: On the PowerPC Linux VSX targets, you can declare complex types using ! the corresponding internal complex type, `KCmode' for `__float128' type ! and `ICmode' for `__ibm128' type: typedef _Complex float __attribute__((mode(KC))) _Complex_float128; typedef _Complex float __attribute__((mode(IC))) _Complex_ibm128; ! Not all targets support additional floating-point types. `__float80' ! and `__float128' types are supported on x86 and IA-64 targets. The ! `__float128' type is supported on hppa HP-UX. The `__float128' type is supported on PowerPC 64-bit Linux systems by default if the vector scalar instruction set (VSX) is enabled. ! On the PowerPC, `__ibm128' provides access to the IBM extended double format, and it is intended to be used by the library functions that handle conversions if/when long double is changed to be IEEE 128-bit floating point. *************** File: gcc.info, Node: Half-Precision, *** 24770,24813 **** ================================== On ARM targets, GCC supports half-precision (16-bit) floating point via ! the '__fp16' type. You must enable this type explicitly with the ! '-mfp16-format' command-line option in order to use it. ARM supports two incompatible representations for half-precision floating-point values. You must choose one of the representations and use it consistently in your program. ! Specifying '-mfp16-format=ieee' selects the IEEE 754-2008 format. This ! format can represent normalized values in the range of 2^{-14} to 65504. ! There are 11 bits of significand precision, approximately 3 decimal ! digits. ! Specifying '-mfp16-format=alternative' selects the ARM alternative ! format. This representation is similar to the IEEE format, but does not ! support infinities or NaNs. Instead, the range of exponents is extended, so that this format can represent normalized values in the ! range of 2^{-14} to 131008. ! The '__fp16' type is a storage format only. For purposes of arithmetic ! and other operations, '__fp16' values in C or C++ expressions are ! automatically promoted to 'float'. In addition, you cannot declare a ! function with a return value or parameters of type '__fp16'. ! Note that conversions from 'double' to '__fp16' involve an intermediate ! conversion to 'float'. Because of rounding, this can sometimes produce ! a different result than a direct conversion. ! ARM provides hardware support for conversions between '__fp16' and ! 'float' values as an extension to VFP and NEON (Advanced SIMD). GCC generates code using these hardware instructions if you compile with options to select an FPU that provides them; for example, ! '-mfpu=neon-fp16 -mfloat-abi=softfp', in addition to the '-mfp16-format' ! option to select a half-precision format. ! Language-level support for the '__fp16' data type is independent of whether GCC generates code using hardware floating-point instructions. In cases where hardware support is not specified, GCC implements ! conversions between '__fp16' and 'float' values as library calls.  File: gcc.info, Node: Decimal Float, Next: Hex Floats, Prev: Half-Precision, Up: C Extensions --- 24922,24966 ---- ================================== On ARM targets, GCC supports half-precision (16-bit) floating point via ! the `__fp16' type. You must enable this type explicitly with the ! `-mfp16-format' command-line option in order to use it. ARM supports two incompatible representations for half-precision floating-point values. You must choose one of the representations and use it consistently in your program. ! Specifying `-mfp16-format=ieee' selects the IEEE 754-2008 format. ! This format can represent normalized values in the range of 2^-14 to ! 65504. There are 11 bits of significand precision, approximately 3 ! decimal digits. ! Specifying `-mfp16-format=alternative' selects the ARM alternative ! format. This representation is similar to the IEEE format, but does ! not support infinities or NaNs. Instead, the range of exponents is extended, so that this format can represent normalized values in the ! range of 2^-14 to 131008. ! The `__fp16' type is a storage format only. For purposes of ! arithmetic and other operations, `__fp16' values in C or C++ ! expressions are automatically promoted to `float'. In addition, you ! cannot declare a function with a return value or parameters of type ! `__fp16'. ! Note that conversions from `double' to `__fp16' involve an ! intermediate conversion to `float'. Because of rounding, this can ! sometimes produce a different result than a direct conversion. ! ARM provides hardware support for conversions between `__fp16' and ! `float' values as an extension to VFP and NEON (Advanced SIMD). GCC generates code using these hardware instructions if you compile with options to select an FPU that provides them; for example, ! `-mfpu=neon-fp16 -mfloat-abi=softfp', in addition to the ! `-mfp16-format' option to select a half-precision format. ! Language-level support for the `__fp16' data type is independent of whether GCC generates code using hardware floating-point instructions. In cases where hardware support is not specified, GCC implements ! conversions between `__fp16' and `float' values as library calls.  File: gcc.info, Node: Decimal Float, Next: Hex Floats, Prev: Half-Precision, Up: C Extensions *************** File: gcc.info, Node: Decimal Float, N *** 24815,24837 **** 6.13 Decimal Floating Types =========================== ! As an extension, GNU C supports decimal floating types as defined in the ! N1312 draft of ISO/IEC WDTR24732. Support for decimal floating types in ! GCC will evolve as the draft technical report changes. Calling ! conventions for any target might also change. Not all targets support ! decimal floating types. ! The decimal floating types are '_Decimal32', '_Decimal64', and ! '_Decimal128'. They use a radix of ten, unlike the floating types ! 'float', 'double', and 'long double' whose radix is not specified by the ! C standard but is usually two. Support for decimal floating types includes the arithmetic operators add, subtract, multiply, divide; unary arithmetic operators; relational operators; equality operators; and conversions to and from integer and ! other floating types. Use a suffix 'df' or 'DF' in a literal constant ! of type '_Decimal32', 'dd' or 'DD' for '_Decimal64', and 'dl' or 'DL' ! for '_Decimal128'. GCC support of decimal float as specified by the draft technical report is incomplete: --- 24968,24990 ---- 6.13 Decimal Floating Types =========================== ! As an extension, GNU C supports decimal floating types as defined in ! the N1312 draft of ISO/IEC WDTR24732. Support for decimal floating ! types in GCC will evolve as the draft technical report changes. ! Calling conventions for any target might also change. Not all targets ! support decimal floating types. ! The decimal floating types are `_Decimal32', `_Decimal64', and ! `_Decimal128'. They use a radix of ten, unlike the floating types ! `float', `double', and `long double' whose radix is not specified by ! the C standard but is usually two. Support for decimal floating types includes the arithmetic operators add, subtract, multiply, divide; unary arithmetic operators; relational operators; equality operators; and conversions to and from integer and ! other floating types. Use a suffix `df' or `DF' in a literal constant ! of type `_Decimal32', `dd' or `DD' for `_Decimal64', and `dl' or `DL' ! for `_Decimal128'. GCC support of decimal float as specified by the draft technical report is incomplete: *************** is incomplete: *** 24842,24853 **** technical report. * GCC does not provide the C library functionality associated with ! 'math.h', 'fenv.h', 'stdio.h', 'stdlib.h', and 'wchar.h', which must come from a separate C library implementation. Because of ! this the GNU C compiler does not define macro '__STDC_DEC_FP__' to indicate that the implementation conforms to the technical report. ! Types '_Decimal32', '_Decimal64', and '_Decimal128' are supported by the DWARF debug information format.  --- 24995,25006 ---- technical report. * GCC does not provide the C library functionality associated with ! `math.h', `fenv.h', `stdio.h', `stdlib.h', and `wchar.h', which must come from a separate C library implementation. Because of ! this the GNU C compiler does not define macro `__STDC_DEC_FP__' to indicate that the implementation conforms to the technical report. ! Types `_Decimal32', `_Decimal64', and `_Decimal128' are supported by the DWARF debug information format.  *************** File: gcc.info, Node: Hex Floats, Next *** 24857,24876 **** =============== ISO C99 supports floating-point numbers written not only in the usual ! decimal notation, such as '1.55e1', but also numbers such as '0x1.fp3' ! written in hexadecimal format. As a GNU extension, GCC supports this in ! C90 mode (except in some cases when strictly conforming) and in C++. In ! that format the '0x' hex introducer and the 'p' or 'P' exponent field ! are mandatory. The exponent is a decimal number that indicates the ! power of 2 by which the significant part is multiplied. Thus '0x1.f' is ! 1 15/16, 'p3' multiplies it by 8, and the value of '0x1.fp3' is the same ! as '1.55e1'. Unlike for floating-point numbers in the decimal notation the exponent is always required in the hexadecimal notation. Otherwise the compiler ! would not be able to resolve the ambiguity of, e.g., '0x1.f'. This ! could mean '1.0f' or '1.9375' since 'f' is also the extension for ! floating-point constants of type 'float'.  File: gcc.info, Node: Fixed-Point, Next: Named Address Spaces, Prev: Hex Floats, Up: C Extensions --- 25010,25029 ---- =============== ISO C99 supports floating-point numbers written not only in the usual ! decimal notation, such as `1.55e1', but also numbers such as `0x1.fp3' ! written in hexadecimal format. As a GNU extension, GCC supports this ! in C90 mode (except in some cases when strictly conforming) and in C++. ! In that format the `0x' hex introducer and the `p' or `P' exponent ! field are mandatory. The exponent is a decimal number that indicates ! the power of 2 by which the significant part is multiplied. Thus ! `0x1.f' is 1 15/16, `p3' multiplies it by 8, and the value of `0x1.fp3' ! is the same as `1.55e1'. Unlike for floating-point numbers in the decimal notation the exponent is always required in the hexadecimal notation. Otherwise the compiler ! would not be able to resolve the ambiguity of, e.g., `0x1.f'. This ! could mean `1.0f' or `1.9375' since `f' is also the extension for ! floating-point constants of type `float'.  File: gcc.info, Node: Fixed-Point, Next: Named Address Spaces, Prev: Hex Floats, Up: C Extensions *************** will evolve as the draft technical repor *** 24884,24938 **** for any target might also change. Not all targets support fixed-point types. ! The fixed-point types are 'short _Fract', '_Fract', 'long _Fract', ! 'long long _Fract', 'unsigned short _Fract', 'unsigned _Fract', ! 'unsigned long _Fract', 'unsigned long long _Fract', '_Sat short ! _Fract', '_Sat _Fract', '_Sat long _Fract', '_Sat long long _Fract', ! '_Sat unsigned short _Fract', '_Sat unsigned _Fract', '_Sat unsigned ! long _Fract', '_Sat unsigned long long _Fract', 'short _Accum', ! '_Accum', 'long _Accum', 'long long _Accum', 'unsigned short _Accum', ! 'unsigned _Accum', 'unsigned long _Accum', 'unsigned long long _Accum', ! '_Sat short _Accum', '_Sat _Accum', '_Sat long _Accum', '_Sat long long ! _Accum', '_Sat unsigned short _Accum', '_Sat unsigned _Accum', '_Sat ! unsigned long _Accum', '_Sat unsigned long long _Accum'. Fixed-point data values contain fractional and optional integral parts. The format of fixed-point data varies and depends on the target machine. Support for fixed-point types includes: ! * prefix and postfix increment and decrement operators ('++', '--') ! * unary arithmetic operators ('+', '-', '!') ! * binary arithmetic operators ('+', '-', '*', '/') ! * binary shift operators ('<<', '>>') ! * relational operators ('<', '<=', '>=', '>') ! * equality operators ('==', '!=') ! * assignment operators ('+=', '-=', '*=', '/=', '<<=', '>>=') * conversions to and from integer, floating-point, or fixed-point types Use a suffix in a fixed-point literal constant: ! * 'hr' or 'HR' for 'short _Fract' and '_Sat short _Fract' ! * 'r' or 'R' for '_Fract' and '_Sat _Fract' ! * 'lr' or 'LR' for 'long _Fract' and '_Sat long _Fract' ! * 'llr' or 'LLR' for 'long long _Fract' and '_Sat long long _Fract' ! * 'uhr' or 'UHR' for 'unsigned short _Fract' and '_Sat unsigned short ! _Fract' ! * 'ur' or 'UR' for 'unsigned _Fract' and '_Sat unsigned _Fract' ! * 'ulr' or 'ULR' for 'unsigned long _Fract' and '_Sat unsigned long _Fract' ! * 'ullr' or 'ULLR' for 'unsigned long long _Fract' and '_Sat unsigned ! long long _Fract' ! * 'hk' or 'HK' for 'short _Accum' and '_Sat short _Accum' ! * 'k' or 'K' for '_Accum' and '_Sat _Accum' ! * 'lk' or 'LK' for 'long _Accum' and '_Sat long _Accum' ! * 'llk' or 'LLK' for 'long long _Accum' and '_Sat long long _Accum' ! * 'uhk' or 'UHK' for 'unsigned short _Accum' and '_Sat unsigned short ! _Accum' ! * 'uk' or 'UK' for 'unsigned _Accum' and '_Sat unsigned _Accum' ! * 'ulk' or 'ULK' for 'unsigned long _Accum' and '_Sat unsigned long _Accum' ! * 'ullk' or 'ULLK' for 'unsigned long long _Accum' and '_Sat unsigned ! long long _Accum' GCC support of fixed-point types as specified by the draft technical report is incomplete: --- 25037,25113 ---- for any target might also change. Not all targets support fixed-point types. ! The fixed-point types are `short _Fract', `_Fract', `long _Fract', ! `long long _Fract', `unsigned short _Fract', `unsigned _Fract', ! `unsigned long _Fract', `unsigned long long _Fract', `_Sat short ! _Fract', `_Sat _Fract', `_Sat long _Fract', `_Sat long long _Fract', ! `_Sat unsigned short _Fract', `_Sat unsigned _Fract', `_Sat unsigned ! long _Fract', `_Sat unsigned long long _Fract', `short _Accum', ! `_Accum', `long _Accum', `long long _Accum', `unsigned short _Accum', ! `unsigned _Accum', `unsigned long _Accum', `unsigned long long _Accum', ! `_Sat short _Accum', `_Sat _Accum', `_Sat long _Accum', `_Sat long long ! _Accum', `_Sat unsigned short _Accum', `_Sat unsigned _Accum', `_Sat ! unsigned long _Accum', `_Sat unsigned long long _Accum'. Fixed-point data values contain fractional and optional integral parts. The format of fixed-point data varies and depends on the target machine. Support for fixed-point types includes: ! * prefix and postfix increment and decrement operators (`++', `--') ! ! * unary arithmetic operators (`+', `-', `!') ! ! * binary arithmetic operators (`+', `-', `*', `/') ! ! * binary shift operators (`<<', `>>') ! ! * relational operators (`<', `<=', `>=', `>') ! ! * equality operators (`==', `!=') ! ! * assignment operators (`+=', `-=', `*=', `/=', `<<=', `>>=') ! * conversions to and from integer, floating-point, or fixed-point types Use a suffix in a fixed-point literal constant: ! * `hr' or `HR' for `short _Fract' and `_Sat short _Fract' ! ! * `r' or `R' for `_Fract' and `_Sat _Fract' ! ! * `lr' or `LR' for `long _Fract' and `_Sat long _Fract' ! ! * `llr' or `LLR' for `long long _Fract' and `_Sat long long _Fract' ! ! * `uhr' or `UHR' for `unsigned short _Fract' and `_Sat unsigned ! short _Fract' ! ! * `ur' or `UR' for `unsigned _Fract' and `_Sat unsigned _Fract' ! ! * `ulr' or `ULR' for `unsigned long _Fract' and `_Sat unsigned long _Fract' ! ! * `ullr' or `ULLR' for `unsigned long long _Fract' and `_Sat ! unsigned long long _Fract' ! ! * `hk' or `HK' for `short _Accum' and `_Sat short _Accum' ! ! * `k' or `K' for `_Accum' and `_Sat _Accum' ! ! * `lk' or `LK' for `long _Accum' and `_Sat long _Accum' ! ! * `llk' or `LLK' for `long long _Accum' and `_Sat long long _Accum' ! ! * `uhk' or `UHK' for `unsigned short _Accum' and `_Sat unsigned ! short _Accum' ! ! * `uk' or `UK' for `unsigned _Accum' and `_Sat unsigned _Accum' ! ! * `ulk' or `ULK' for `unsigned long _Accum' and `_Sat unsigned long _Accum' ! ! * `ullk' or `ULLK' for `unsigned long long _Accum' and `_Sat ! unsigned long long _Accum' GCC support of fixed-point types as specified by the draft technical report is incomplete: *************** File: gcc.info, Node: Named Address Spa *** 24951,24962 **** As an extension, GNU C supports named address spaces as defined in the N1275 draft of ISO/IEC DTR 18037. Support for named address spaces in GCC will evolve as the draft technical report changes. Calling ! conventions for any target might also change. At present, only the AVR, ! SPU, M32C, RL78, and x86 targets support address spaces other than the ! generic address space. Address space identifiers may be used exactly like any other C type ! qualifier (e.g., 'const' or 'volatile'). See the N1275 document for more details. 6.16.1 AVR Named Address Spaces --- 25126,25137 ---- As an extension, GNU C supports named address spaces as defined in the N1275 draft of ISO/IEC DTR 18037. Support for named address spaces in GCC will evolve as the draft technical report changes. Calling ! conventions for any target might also change. At present, only the ! AVR, SPU, M32C, RL78, and x86 targets support address spaces other than ! the generic address space. Address space identifiers may be used exactly like any other C type ! qualifier (e.g., `const' or `volatile'). See the N1275 document for more details. 6.16.1 AVR Named Address Spaces *************** more details. *** 24964,25001 **** On the AVR target, there are several address spaces that can be used in order to put read-only data into the flash memory and access that data ! by means of the special instructions 'LPM' or 'ELPM' needed to read from ! flash. Per default, any data including read-only data is located in RAM (the generic address space) so that non-generic address spaces are needed to locate read-only data in flash memory _and_ to generate the right instructions to access this data without using (inline) assembler code. ! '__flash' ! The '__flash' qualifier locates data in the '.progmem.data' ! section. Data is read using the 'LPM' instruction. Pointers to this address space are 16 bits wide. ! '__flash1' ! '__flash2' ! '__flash3' ! '__flash4' ! '__flash5' These are 16-bit address spaces locating data in section ! '.progmemN.data' where N refers to address space '__flashN'. The ! compiler sets the 'RAMPZ' segment register appropriately before ! reading data by means of the 'ELPM' instruction. ! '__memx' This is a 24-bit address space that linearizes flash and RAM: If ! the high bit of the address is set, data is read from RAM using the ! lower two bytes as RAM address. If the high bit of the address is ! clear, data is read from flash with 'RAMPZ' set according to the ! high byte of the address. *Note '__builtin_avr_flash_segment': AVR ! Built-in Functions. ! Objects in this address space are located in '.progmemx.data'. Example --- 25139,25176 ---- On the AVR target, there are several address spaces that can be used in order to put read-only data into the flash memory and access that data ! by means of the special instructions `LPM' or `ELPM' needed to read ! from flash. Per default, any data including read-only data is located in RAM (the generic address space) so that non-generic address spaces are needed to locate read-only data in flash memory _and_ to generate the right instructions to access this data without using (inline) assembler code. ! `__flash' ! The `__flash' qualifier locates data in the `.progmem.data' ! section. Data is read using the `LPM' instruction. Pointers to this address space are 16 bits wide. ! `__flash1' ! `__flash2' ! `__flash3' ! `__flash4' ! `__flash5' These are 16-bit address spaces locating data in section ! `.progmemN.data' where N refers to address space `__flashN'. The ! compiler sets the `RAMPZ' segment register appropriately before ! reading data by means of the `ELPM' instruction. ! `__memx' This is a 24-bit address space that linearizes flash and RAM: If ! the high bit of the address is set, data is read from RAM using ! the lower two bytes as RAM address. If the high bit of the ! address is clear, data is read from flash with `RAMPZ' set ! according to the high byte of the address. *Note ! `__builtin_avr_flash_segment': AVR Built-in Functions. ! Objects in this address space are located in `.progmemx.data'. Example *************** not: *** 25043,25075 **** } #endif /* __FLASH */ ! Notice that attribute *note 'progmem': AVR Variable Attributes. locates ! data in flash but accesses to these data read from generic address ! space, i.e. from RAM, so that you need special accessors like ! 'pgm_read_byte' from AVR-LibC (http://nongnu.org/avr-libc/user-manual/) ! together with attribute 'progmem'. Limitations and caveats ! * Reading across the 64 KiB section boundary of the '__flash' or ! '__flashN' address spaces shows undefined behavior. The only ! address space that supports reading across the 64 KiB flash segment ! boundaries is '__memx'. ! * If you use one of the '__flashN' address spaces you must arrange ! your linker script to locate the '.progmemN.data' sections according to your needs. * Any data or pointers to the non-generic address spaces must be ! qualified as 'const', i.e. as read-only data. This still applies if the data in one of these address spaces like software version ! number or calibration lookup table are intended to be changed after ! load time by, say, a boot loader. In this case the right ! qualification is 'const' 'volatile' so that the compiler must not optimize away known values or insert them as immediates into operands of instructions. ! * The following code initializes a variable 'pfoo' located in static storage with a 24-bit address: extern const __memx char foo; const __memx void *pfoo = &foo; --- 25218,25250 ---- } #endif /* __FLASH */ ! Notice that attribute *note `progmem': AVR Variable Attributes. ! locates data in flash but accesses to these data read from generic ! address space, i.e. from RAM, so that you need special accessors like ! `pgm_read_byte' from AVR-LibC (http://nongnu.org/avr-libc/user-manual/) ! together with attribute `progmem'. Limitations and caveats ! * Reading across the 64 KiB section boundary of the `__flash' or ! `__flashN' address spaces shows undefined behavior. The only ! address space that supports reading across the 64 KiB flash ! segment boundaries is `__memx'. ! * If you use one of the `__flashN' address spaces you must arrange ! your linker script to locate the `.progmemN.data' sections according to your needs. * Any data or pointers to the non-generic address spaces must be ! qualified as `const', i.e. as read-only data. This still applies if the data in one of these address spaces like software version ! number or calibration lookup table are intended to be changed ! after load time by, say, a boot loader. In this case the right ! qualification is `const' `volatile' so that the compiler must not optimize away known values or insert them as immediates into operands of instructions. ! * The following code initializes a variable `pfoo' located in static storage with a 24-bit address: extern const __memx char foo; const __memx void *pfoo = &foo; *************** Limitations and caveats *** 25077,25094 **** Such code requires at least binutils 2.23, see PR13503 (http://sourceware.org/PR13503). 6.16.2 M32C Named Address Spaces -------------------------------- On the M32C target, with the R8C and M16C CPU variants, variables ! qualified with '__far' are accessed using 32-bit addresses in order to ! access memory beyond the first 64 Ki bytes. If '__far' is used with the ! M32CM or M32C CPU variants, it has no effect. 6.16.3 RL78 Named Address Spaces -------------------------------- ! On the RL78 target, variables qualified with '__far' are accessed with 32-bit pointers (20-bit addresses) rather than the default 16-bit addresses. Non-far variables are assumed to appear in the topmost 64 KiB of the address space. --- 25252,25270 ---- Such code requires at least binutils 2.23, see PR13503 (http://sourceware.org/PR13503). + 6.16.2 M32C Named Address Spaces -------------------------------- On the M32C target, with the R8C and M16C CPU variants, variables ! qualified with `__far' are accessed using 32-bit addresses in order to ! access memory beyond the first 64 Ki bytes. If `__far' is used with ! the M32CM or M32C CPU variants, it has no effect. 6.16.3 RL78 Named Address Spaces -------------------------------- ! On the RL78 target, variables qualified with `__far' are accessed with 32-bit pointers (20-bit addresses) rather than the default 16-bit addresses. Non-far variables are assumed to appear in the topmost 64 KiB of the address space. *************** addresses. Non-far variables are assume *** 25097,25119 **** ------------------------------- On the SPU target variables may be declared as belonging to another ! address space by qualifying the type with the '__ea' address space identifier: extern int __ea i; ! The compiler generates special code to access the variable 'i'. It may ! use runtime library support, or generate special machine instructions to ! access that address space. 6.16.5 x86 Named Address Spaces ------------------------------- On the x86 target, variables may be declared as being relative to the ! '%fs' or '%gs' segments. ! '__seg_fs' ! '__seg_gs' The object is accessed with the respective segment override prefix. The respective segment base must be set via some method specific to --- 25273,25295 ---- ------------------------------- On the SPU target variables may be declared as belonging to another ! address space by qualifying the type with the `__ea' address space identifier: extern int __ea i; ! The compiler generates special code to access the variable `i'. It may ! use runtime library support, or generate special machine instructions ! to access that address space. 6.16.5 x86 Named Address Spaces ------------------------------- On the x86 target, variables may be declared as being relative to the ! `%fs' or `%gs' segments. ! `__seg_fs' ! `__seg_gs' The object is accessed with the respective segment override prefix. The respective segment base must be set via some method specific to *************** On the x86 target, variables may be decl *** 25122,25132 **** considered to be subspaces of the generic (flat) address space. This means that explicit casts are required to convert pointers between these address spaces and the generic address space. In ! practice the application should cast to 'uintptr_t' and apply the segment base offset that it installed previously. ! The preprocessor symbols '__SEG_FS' and '__SEG_GS' are defined when ! these address spaces are supported.  File: gcc.info, Node: Zero Length, Next: Empty Structures, Prev: Named Address Spaces, Up: C Extensions --- 25298,25308 ---- considered to be subspaces of the generic (flat) address space. This means that explicit casts are required to convert pointers between these address spaces and the generic address space. In ! practice the application should cast to `uintptr_t' and apply the segment base offset that it installed previously. ! The preprocessor symbols `__SEG_FS' and `__SEG_GS' are defined ! when these address spaces are supported.  File: gcc.info, Node: Zero Length, Next: Empty Structures, Prev: Named Address Spaces, Up: C Extensions *************** variable-length object: *** 25147,25181 **** malloc (sizeof (struct line) + this_length); thisline->length = this_length; ! In ISO C90, you would have to give 'contents' a length of 1, which ! means either you waste space or complicate the argument to 'malloc'. In ISO C99, you would use a "flexible array member", which is slightly different in syntax and semantics: ! * Flexible array members are written as 'contents[]' without the '0'. ! * Flexible array members have incomplete type, and so the 'sizeof' operator may not be applied. As a quirk of the original ! implementation of zero-length arrays, 'sizeof' evaluates to zero. * Flexible array members may only appear as the last member of a ! 'struct' that is otherwise non-empty. * A structure containing a flexible array member, or a union containing such a structure (possibly recursively), may not be a member of a structure or an element of an array. (However, these uses are permitted by GCC as extensions.) ! Non-empty initialization of zero-length arrays is treated like any case ! where there are more initializer elements than the array holds, in that ! a suitable warning about "excess elements in array" is given, and the ! excess elements (all of them, in this case) are ignored. GCC allows static initialization of flexible array members. This is ! equivalent to defining a new structure containing the original structure ! followed by an array of sufficient size to contain the data. E.g. in ! the following, 'f1' is constructed as if it were declared like 'f2'. struct f1 { int x; int y[]; --- 25323,25358 ---- malloc (sizeof (struct line) + this_length); thisline->length = this_length; ! In ISO C90, you would have to give `contents' a length of 1, which ! means either you waste space or complicate the argument to `malloc'. In ISO C99, you would use a "flexible array member", which is slightly different in syntax and semantics: ! * Flexible array members are written as `contents[]' without the `0'. ! * Flexible array members have incomplete type, and so the `sizeof' operator may not be applied. As a quirk of the original ! implementation of zero-length arrays, `sizeof' evaluates to zero. * Flexible array members may only appear as the last member of a ! `struct' that is otherwise non-empty. * A structure containing a flexible array member, or a union containing such a structure (possibly recursively), may not be a member of a structure or an element of an array. (However, these uses are permitted by GCC as extensions.) ! Non-empty initialization of zero-length arrays is treated like any ! case where there are more initializer elements than the array holds, in ! that a suitable warning about "excess elements in array" is given, and ! the excess elements (all of them, in this case) are ignored. GCC allows static initialization of flexible array members. This is ! equivalent to defining a new structure containing the original ! structure followed by an array of sufficient size to contain the data. ! E.g. in the following, `f1' is constructed as if it were declared like ! `f2'. struct f1 { int x; int y[]; *************** the following, 'f1' is constructed as if *** 25185,25202 **** struct f1 f1; int data[3]; } f2 = { { 1 }, { 2, 3, 4 } }; ! The convenience of this extension is that 'f1' has the desired type, ! eliminating the need to consistently refer to 'f2.f1'. This has symmetry with normal static arrays, in that an array of ! unknown size is also written with '[]'. Of course, this extension only makes sense if the extra data comes at ! the end of a top-level object, as otherwise we would be overwriting data ! at subsequent offsets. To avoid undue complication and confusion with ! initialization of deeply nested arrays, we simply disallow any non-empty ! initialization except when the structure is the top-level object. For ! example: struct foo { int x; int y[]; }; struct bar { struct foo z; }; --- 25362,25379 ---- struct f1 f1; int data[3]; } f2 = { { 1 }, { 2, 3, 4 } }; ! The convenience of this extension is that `f1' has the desired type, ! eliminating the need to consistently refer to `f2.f1'. This has symmetry with normal static arrays, in that an array of ! unknown size is also written with `[]'. Of course, this extension only makes sense if the extra data comes at ! the end of a top-level object, as otherwise we would be overwriting ! data at subsequent offsets. To avoid undue complication and confusion ! with initialization of deeply nested arrays, we simply disallow any ! non-empty initialization except when the structure is the top-level ! object. For example: struct foo { int x; int y[]; }; struct bar { struct foo z; }; *************** GCC permits a C structure to have no mem *** 25218,25225 **** }; The structure has size zero. In C++, empty structures are part of the ! language. G++ treats empty structures as if they had a single member of ! type 'char'.  File: gcc.info, Node: Variable Length, Next: Variadic Macros, Prev: Empty Structures, Up: C Extensions --- 25395,25402 ---- }; The structure has size zero. In C++, empty structures are part of the ! language. G++ treats empty structures as if they had a single member ! of type `char'.  File: gcc.info, Node: Variable Length, Next: Variadic Macros, Prev: Empty Structures, Up: C Extensions *************** structure or a union. For example: *** 25256,25270 **** struct S { int x[n]; }; } ! You can use the function 'alloca' to get an effect much like ! variable-length arrays. The function 'alloca' is available in many other C implementations (but not in all). On the other hand, variable-length arrays are more elegant. There are other differences between these two methods. Space allocated ! with 'alloca' exists until the containing _function_ returns. The space ! for a variable-length array is deallocated as soon as the array name's ! scope ends, unless you also use 'alloca' in this scope. You can also use variable-length arrays as arguments to functions: --- 25433,25447 ---- struct S { int x[n]; }; } ! You can use the function `alloca' to get an effect much like ! variable-length arrays. The function `alloca' is available in many other C implementations (but not in all). On the other hand, variable-length arrays are more elegant. There are other differences between these two methods. Space allocated ! with `alloca' exists until the containing _function_ returns. The ! space for a variable-length array is deallocated as soon as the array ! name's scope ends, unless you also use `alloca' in this scope. You can also use variable-length arrays as arguments to functions: *************** scope ends, unless you also use 'alloca' *** 25276,25282 **** The length of an array is computed once when the storage is allocated and is remembered for the scope of the array in case you access it with ! 'sizeof'. If you want to pass the array first and the length afterward, you can use a forward declaration in the parameter list--another GNU extension. --- 25453,25459 ---- The length of an array is computed once when the storage is allocated and is remembered for the scope of the array in case you access it with ! `sizeof'. If you want to pass the array first and the length afterward, you can use a forward declaration in the parameter list--another GNU extension. *************** use a forward declaration in the paramet *** 25287,25295 **** /* ... */ } ! The 'int len' before the semicolon is a "parameter forward ! declaration", and it serves the purpose of making the name 'len' known ! when the declaration of 'data' is parsed. You can write any number of such parameter forward declarations in the parameter list. They can be separated by commas or semicolons, but the --- 25464,25472 ---- /* ... */ } ! The `int len' before the semicolon is a "parameter forward ! declaration", and it serves the purpose of making the name `len' known ! when the declaration of `data' is parsed. You can write any number of such parameter forward declarations in the parameter list. They can be separated by commas or semicolons, but the *************** example: *** 25311,25321 **** #define debug(format, ...) fprintf (stderr, format, __VA_ARGS__) ! Here '...' is a "variable argument". In the invocation of such a macro, ! it represents the zero or more tokens until the closing parenthesis that ! ends the invocation, including any commas. This set of tokens replaces ! the identifier '__VA_ARGS__' in the macro body wherever it appears. See ! the CPP manual for more information. GCC has long supported variadic macros, and used a different syntax that allowed you to give a name to the variable arguments just like any --- 25488,25498 ---- #define debug(format, ...) fprintf (stderr, format, __VA_ARGS__) ! Here `...' is a "variable argument". In the invocation of such a ! macro, it represents the zero or more tokens until the closing ! parenthesis that ends the invocation, including any commas. This set of ! tokens replaces the identifier `__VA_ARGS__' in the macro body wherever ! it appears. See the CPP manual for more information. GCC has long supported variadic macros, and used a different syntax that allowed you to give a name to the variable arguments just like any *************** be used with either of the above forms o *** 25331,25338 **** In standard C, you are not allowed to leave the variable argument out entirely; but you are allowed to pass an empty argument. For example, ! this invocation is invalid in ISO C, because there is no comma after the ! string: debug ("A message") --- 25508,25515 ---- In standard C, you are not allowed to leave the variable argument out entirely; but you are allowed to pass an empty argument. For example, ! this invocation is invalid in ISO C, because there is no comma after ! the string: debug ("A message") *************** the expansion of the macro still has the *** 25342,25353 **** string. To help solve this problem, CPP behaves specially for variable ! arguments used with the token paste operator, '##'. If instead you write #define debug(format, ...) fprintf (stderr, format, ## __VA_ARGS__) ! and if the variable arguments are omitted or empty, the '##' operator causes the preprocessor to remove the comma before it. If you do provide some variable arguments in your macro invocation, GNU CPP does not complain about the paste operation and instead places the variable --- 25519,25530 ---- string. To help solve this problem, CPP behaves specially for variable ! arguments used with the token paste operator, `##'. If instead you write #define debug(format, ...) fprintf (stderr, format, ## __VA_ARGS__) ! and if the variable arguments are omitted or empty, the `##' operator causes the preprocessor to remove the comma before it. If you do provide some variable arguments in your macro invocation, GNU CPP does not complain about the paste operation and instead places the variable *************** File: gcc.info, Node: Escaped Newlines, *** 25360,25375 **** 6.21 Slightly Looser Rules for Escaped Newlines =============================================== ! The preprocessor treatment of escaped newlines is more relaxed than that ! specified by the C90 standard, which requires the newline to immediately ! follow a backslash. GCC's implementation allows whitespace in the form ! of spaces, horizontal and vertical tabs, and form feeds between the ! backslash and the subsequent newline. The preprocessor issues a ! warning, but treats it as a valid escaped newline and combines the two ! lines to form a single logical line. This works within comments and ! tokens, as well as between tokens. Comments are _not_ treated as ! whitespace for the purposes of this relaxation, since they have not yet ! been replaced with spaces.  File: gcc.info, Node: Subscripting, Next: Pointer Arith, Prev: Escaped Newlines, Up: C Extensions --- 25537,25552 ---- 6.21 Slightly Looser Rules for Escaped Newlines =============================================== ! The preprocessor treatment of escaped newlines is more relaxed than ! that specified by the C90 standard, which requires the newline to ! immediately follow a backslash. GCC's implementation allows whitespace ! in the form of spaces, horizontal and vertical tabs, and form feeds ! between the backslash and the subsequent newline. The preprocessor ! issues a warning, but treats it as a valid escaped newline and combines ! the two lines to form a single logical line. This works within ! comments and tokens, as well as between tokens. Comments are _not_ ! treated as whitespace for the purposes of this relaxation, since they ! have not yet been replaced with spaces.  File: gcc.info, Node: Subscripting, Next: Pointer Arith, Prev: Escaped Newlines, Up: C Extensions *************** File: gcc.info, Node: Subscripting, Ne *** 25377,25388 **** 6.22 Non-Lvalue Arrays May Have Subscripts ========================================== ! In ISO C99, arrays that are not lvalues still decay to pointers, and may ! be subscripted, although they may not be modified or used after the next ! sequence point and the unary '&' operator may not be applied to them. ! As an extension, GNU C allows such arrays to be subscripted in C90 mode, ! though otherwise they do not decay to pointers outside C99 mode. For ! example, this is valid in GNU C though not valid in C90: struct foo {int a[4];}; --- 25554,25565 ---- 6.22 Non-Lvalue Arrays May Have Subscripts ========================================== ! In ISO C99, arrays that are not lvalues still decay to pointers, and ! may be subscripted, although they may not be modified or used after the ! next sequence point and the unary `&' operator may not be applied to ! them. As an extension, GNU C allows such arrays to be subscripted in ! C90 mode, though otherwise they do not decay to pointers outside C99 ! mode. For example, this is valid in GNU C though not valid in C90: struct foo {int a[4];}; *************** example, this is valid in GNU C though n *** 25396,25413 ****  File: gcc.info, Node: Pointer Arith, Next: Pointers to Arrays, Prev: Subscripting, Up: C Extensions ! 6.23 Arithmetic on 'void'- and Function-Pointers ================================================ In GNU C, addition and subtraction operations are supported on pointers ! to 'void' and on pointers to functions. This is done by treating the ! size of a 'void' or of a function as 1. ! A consequence of this is that 'sizeof' is also allowed on 'void' and on ! function types, and returns 1. ! The option '-Wpointer-arith' requests a warning if these extensions are ! used.  File: gcc.info, Node: Pointers to Arrays, Next: Initializers, Prev: Pointer Arith, Up: C Extensions --- 25573,25590 ----  File: gcc.info, Node: Pointer Arith, Next: Pointers to Arrays, Prev: Subscripting, Up: C Extensions ! 6.23 Arithmetic on `void'- and Function-Pointers ================================================ In GNU C, addition and subtraction operations are supported on pointers ! to `void' and on pointers to functions. This is done by treating the ! size of a `void' or of a function as 1. ! A consequence of this is that `sizeof' is also allowed on `void' and ! on function types, and returns 1. ! The option `-Wpointer-arith' requests a warning if these extensions ! are used.  File: gcc.info, Node: Pointers to Arrays, Next: Initializers, Prev: Pointer Arith, Up: C Extensions *************** File: gcc.info, Node: Pointers to Array *** 25415,25425 **** 6.24 Pointers to Arrays with Qualifiers Work as Expected ======================================================== ! In GNU C, pointers to arrays with qualifiers work similar to pointers to ! other qualified types. For example, a value of type 'int (*)[5]' can be ! used to initialize a variable of type 'const int (*)[5]'. These types ! are incompatible in ISO C because the 'const' qualifier is formally ! attached to the element type of the array and not the array itself. extern void transpose (int N, int M, double out[M][N], const double in[N][M]); --- 25592,25603 ---- 6.24 Pointers to Arrays with Qualifiers Work as Expected ======================================================== ! In GNU C, pointers to arrays with qualifiers work similar to pointers ! to other qualified types. For example, a value of type `int (*)[5]' can ! be used to initialize a variable of type `const int (*)[5]'. These ! types are incompatible in ISO C because the `const' qualifier is ! formally attached to the element type of the array and not the array ! itself. extern void transpose (int N, int M, double out[M][N], const double in[N][M]); *************** File: gcc.info, Node: Initializers, Ne *** 25434,25443 **** 6.25 Non-Constant Initializers ============================== ! As in standard C++ and ISO C99, the elements of an aggregate initializer ! for an automatic variable are not required to be constant expressions in ! GNU C. Here is an example of an initializer with run-time varying ! elements: foo (float f, float g) { --- 25612,25621 ---- 6.25 Non-Constant Initializers ============================== ! As in standard C++ and ISO C99, the elements of an aggregate ! initializer for an automatic variable are not required to be constant ! expressions in GNU C. Here is an example of an initializer with ! run-time varying elements: foo (float f, float g) { *************** initializer; it is an lvalue. As an ext *** 25458,25469 **** literals in C90 mode and in C++, though the semantics are somewhat different in C++. ! Usually, the specified type is a structure. Assume that 'struct foo' ! and 'structure' are declared as shown: struct foo {int a; char b[2];} structure; ! Here is an example of constructing a 'struct foo' with a compound literal: structure = ((struct foo) {x + y, 'a', 0}); --- 25636,25647 ---- literals in C90 mode and in C++, though the semantics are somewhat different in C++. ! Usually, the specified type is a structure. Assume that `struct foo' ! and `structure' are declared as shown: struct foo {int a; char b[2];} structure; ! Here is an example of constructing a `struct foo' with a compound literal: structure = ((struct foo) {x + y, 'a', 0}); *************** initializer, as shown here: *** 25488,25500 **** but then the compound literal is equivalent to a cast. As a GNU extension, GCC allows initialization of objects with static ! storage duration by compound literals (which is not possible in ISO C99, ! because the initializer is not a constant). It is handled as if the ! object is initialized only with the bracket enclosed list if the types ! of the compound literal and the object match. The initializer list of ! the compound literal must be constant. If the object being initialized ! has array type of unknown size, the size is determined by compound ! literal size. static struct foo x = (struct foo) {1, 'a', 'b'}; static int y[] = (int []) {1, 2, 3}; --- 25666,25678 ---- but then the compound literal is equivalent to a cast. As a GNU extension, GCC allows initialization of objects with static ! storage duration by compound literals (which is not possible in ISO ! C99, because the initializer is not a constant). It is handled as if ! the object is initialized only with the bracket enclosed list if the ! types of the compound literal and the object match. The initializer ! list of the compound literal must be constant. If the object being ! initialized has array type of unknown size, the size is determined by ! compound literal size. static struct foo x = (struct foo) {1, 'a', 'b'}; static int y[] = (int []) {1, 2, 3}; *************** The above lines are equivalent to the fo *** 25507,25524 **** In C, a compound literal designates an unnamed object with static or automatic storage duration. In C++, a compound literal designates a ! temporary object, which only lives until the end of its full-expression. ! As a result, well-defined C code that takes the address of a subobject ! of a compound literal can be undefined in C++, so the C++ compiler ! rejects the conversion of a temporary array to a pointer. For instance, ! if the array compound literal example above appeared inside a function, ! any subsequent use of 'foo' in C++ has undefined behavior because the ! lifetime of the array ends after the declaration of 'foo'. As an optimization, the C++ compiler sometimes gives array compound literals longer lifetimes: when the array either appears outside a ! function or has const-qualified type. If 'foo' and its initializer had ! elements of 'char *const' type rather than 'char *', or if 'foo' were a global variable, the array would have static storage duration. But it is probably safest just to avoid the use of array compound literals in code compiled as C++. --- 25685,25703 ---- In C, a compound literal designates an unnamed object with static or automatic storage duration. In C++, a compound literal designates a ! temporary object, which only lives until the end of its ! full-expression. As a result, well-defined C code that takes the ! address of a subobject of a compound literal can be undefined in C++, ! so the C++ compiler rejects the conversion of a temporary array to a ! pointer. For instance, if the array compound literal example above ! appeared inside a function, any subsequent use of `foo' in C++ has ! undefined behavior because the lifetime of the array ends after the ! declaration of `foo'. As an optimization, the C++ compiler sometimes gives array compound literals longer lifetimes: when the array either appears outside a ! function or has const-qualified type. If `foo' and its initializer had ! elements of `char *const' type rather than `char *', or if `foo' were a global variable, the array would have static storage duration. But it is probably safest just to avoid the use of array compound literals in code compiled as C++. *************** indices or structure field names they ap *** 25538,25544 **** an extension in C90 mode as well. This extension is not implemented in GNU C++. ! To specify an array index, write '[INDEX] =' before the element value. For example, int a[6] = { [4] = 29, [2] = 15 }; --- 25717,25723 ---- an extension in C90 mode as well. This extension is not implemented in GNU C++. ! To specify an array index, write `[INDEX] =' before the element value. For example, int a[6] = { [4] = 29, [2] = 15 }; *************** The index values must be constant expres *** 25551,25560 **** initialized is automatic. An alternative syntax for this that has been obsolete since GCC 2.5 but ! GCC still accepts is to write '[INDEX]' before the element value, with ! no '='. ! To initialize a range of elements to the same value, write '[FIRST ... LAST] = VALUE'. This is a GNU extension. For example, int widths[] = { [0 ... 9] = 1, [10 ... 99] = 2, [100] = 3 }; --- 25730,25739 ---- initialized is automatic. An alternative syntax for this that has been obsolete since GCC 2.5 but ! GCC still accepts is to write `[INDEX]' before the element value, with ! no `='. ! To initialize a range of elements to the same value, write `[FIRST ... LAST] = VALUE'. This is a GNU extension. For example, int widths[] = { [0 ... 9] = 1, [10 ... 99] = 2, [100] = 3 }; *************** Note that the length of the array is the *** 25566,25572 **** one. In a structure initializer, specify the name of a field to initialize ! with '.FIELDNAME =' before the element value. For example, given the following structure, struct point { int x, y; }; --- 25745,25751 ---- one. In a structure initializer, specify the name of a field to initialize ! with `.FIELDNAME =' before the element value. For example, given the following structure, struct point { int x, y; }; *************** is equivalent to *** 25580,25604 **** struct point p = { xvalue, yvalue }; Another syntax that has the same meaning, obsolete since GCC 2.5, is ! 'FIELDNAME:', as shown here: struct point p = { y: yvalue, x: xvalue }; Omitted field members are implicitly initialized the same as objects that have static storage duration. ! The '[INDEX]' or '.FIELDNAME' is known as a "designator". You can also ! use a designator (or the obsolete colon syntax) when initializing a ! union, to specify which element of the union should be used. For example, union foo { int i; double d; }; union foo f = { .d = 4 }; ! converts 4 to a 'double' to store it in the union using the second ! element. By contrast, casting 4 to type 'union foo' stores it into the ! union as the integer 'i', since it is an integer. (*Note Cast to Union::.) You can combine this technique of naming elements with ordinary C --- 25759,25783 ---- struct point p = { xvalue, yvalue }; Another syntax that has the same meaning, obsolete since GCC 2.5, is ! `FIELDNAME:', as shown here: struct point p = { y: yvalue, x: xvalue }; Omitted field members are implicitly initialized the same as objects that have static storage duration. ! The `[INDEX]' or `.FIELDNAME' is known as a "designator". You can ! also use a designator (or the obsolete colon syntax) when initializing ! a union, to specify which element of the union should be used. For example, union foo { int i; double d; }; union foo f = { .d = 4 }; ! converts 4 to a `double' to store it in the union using the second ! element. By contrast, casting 4 to type `union foo' stores it into the ! union as the integer `i', since it is an integer. (*Note Cast to Union::.) You can combine this technique of naming elements with ordinary C *************** is equivalent to *** 25612,25628 **** int a[6] = { 0, v1, v2, 0, v4, 0 }; ! Labeling the elements of an array initializer is especially useful when ! the indices are characters or belong to an 'enum' type. For example: int whitespace[256] = { [' '] = 1, ['\t'] = 1, ['\h'] = 1, ['\f'] = 1, ['\n'] = 1, ['\r'] = 1 }; ! You can also write a series of '.FIELDNAME' and '[INDEX]' designators ! before an '=' to specify a nested subobject to initialize; the list is ! taken relative to the subobject corresponding to the closest surrounding ! brace pair. For example, with the 'struct point' declaration above: struct point ptarray[10] = { [2].y = yv2, [2].x = xv2, [0].x = xv0 }; --- 25791,25809 ---- int a[6] = { 0, v1, v2, 0, v4, 0 }; ! Labeling the elements of an array initializer is especially useful ! when the indices are characters or belong to an `enum' type. For ! example: int whitespace[256] = { [' '] = 1, ['\t'] = 1, ['\h'] = 1, ['\f'] = 1, ['\n'] = 1, ['\r'] = 1 }; ! You can also write a series of `.FIELDNAME' and `[INDEX]' designators ! before an `=' to specify a nested subobject to initialize; the list is ! taken relative to the subobject corresponding to the closest ! surrounding brace pair. For example, with the `struct point' ! declaration above: struct point ptarray[10] = { [2].y = yv2, [2].x = xv2, [0].x = xv0 }; *************** File: gcc.info, Node: Case Ranges, Nex *** 25637,25655 **** 6.28 Case Ranges ================ ! You can specify a range of consecutive values in a single 'case' label, like this: case LOW ... HIGH: ! This has the same effect as the proper number of individual 'case' labels, one for each integer value from LOW to HIGH, inclusive. This feature is especially useful for ranges of ASCII character codes: case 'A' ... 'Z': ! *Be careful:* Write spaces around the '...', for otherwise it may be parsed wrong when you use it with integer values. For example, write this: --- 25818,25836 ---- 6.28 Case Ranges ================ ! You can specify a range of consecutive values in a single `case' label, like this: case LOW ... HIGH: ! This has the same effect as the proper number of individual `case' labels, one for each integer value from LOW to HIGH, inclusive. This feature is especially useful for ranges of ASCII character codes: case 'A' ... 'Z': ! *Be careful:* Write spaces around the `...', for otherwise it may be parsed wrong when you use it with integer values. For example, write this: *************** File: gcc.info, Node: Cast to Union, N *** 25666,25675 **** ========================= A cast to union type is similar to other casts, except that the type ! specified is a union type. You can specify the type either with 'union ! TAG' or with a typedef name. A cast to union is actually a constructor, ! not a cast, and hence does not yield an lvalue like normal casts. ! (*Note Compound Literals::.) The types that may be cast to the union type are those of the members of the union. Thus, given the following union and variables: --- 25847,25856 ---- ========================= A cast to union type is similar to other casts, except that the type ! specified is a union type. You can specify the type either with `union ! TAG' or with a typedef name. A cast to union is actually a ! constructor, not a cast, and hence does not yield an lvalue like normal ! casts. (*Note Compound Literals::.) The types that may be cast to the union type are those of the members of the union. Thus, given the following union and variables: *************** of the union. Thus, given the following *** 25678,25684 **** int x; double y; ! both 'x' and 'y' can be cast to type 'union foo'. Using the cast as the right-hand side of an assignment to a variable of union type is equivalent to storing in a member of the union: --- 25859,25865 ---- int x; double y; ! both `x' and `y' can be cast to type `union foo'. Using the cast as the right-hand side of an assignment to a variable of union type is equivalent to storing in a member of the union: *************** File: gcc.info, Node: Function Attribut *** 25721,25755 **** In GNU C, you can use function attributes to declare certain things about functions called in your program which help the compiler optimize calls and check your code more carefully. For example, you can use ! attributes to declare that a function never returns ('noreturn'), ! returns a value depending only on its arguments ('pure'), or has ! 'printf'-style arguments ('format'). You can also use attributes to control memory placement, code generation options or call/return conventions within the function being annotated. Many of these attributes are target-specific. For example, many targets support attributes for defining interrupt handler ! functions, which typically must follow special register usage and return ! conventions. ! Function attributes are introduced by the '__attribute__' keyword on a declaration, followed by an attribute specification inside double parentheses. You can specify multiple attributes in a declaration by separating them by commas within the double parentheses or by immediately following an attribute declaration with another attribute ! declaration. *Note Attribute Syntax::, for the exact rules on attribute ! syntax and placement. GCC also supports attributes on variable declarations (*note Variable Attributes::), labels (*note Label Attributes::), enumerators (*note Enumerator Attributes::), and types (*note Type Attributes::). There is some overlap between the purposes of attributes and pragmas ! (*note Pragmas Accepted by GCC: Pragmas.). It has been found convenient ! to use '__attribute__' to achieve a natural attachment of attributes to ! their corresponding declarations, whereas '#pragma' is of use for ! compatibility with other compilers or constructs that do not naturally ! form part of the grammar. In addition to the attributes documented here, GCC plugins may provide their own attributes. --- 25902,25936 ---- In GNU C, you can use function attributes to declare certain things about functions called in your program which help the compiler optimize calls and check your code more carefully. For example, you can use ! attributes to declare that a function never returns (`noreturn'), ! returns a value depending only on its arguments (`pure'), or has ! `printf'-style arguments (`format'). You can also use attributes to control memory placement, code generation options or call/return conventions within the function being annotated. Many of these attributes are target-specific. For example, many targets support attributes for defining interrupt handler ! functions, which typically must follow special register usage and ! return conventions. ! Function attributes are introduced by the `__attribute__' keyword on a declaration, followed by an attribute specification inside double parentheses. You can specify multiple attributes in a declaration by separating them by commas within the double parentheses or by immediately following an attribute declaration with another attribute ! declaration. *Note Attribute Syntax::, for the exact rules on ! attribute syntax and placement. GCC also supports attributes on variable declarations (*note Variable Attributes::), labels (*note Label Attributes::), enumerators (*note Enumerator Attributes::), and types (*note Type Attributes::). There is some overlap between the purposes of attributes and pragmas ! (*note Pragmas Accepted by GCC: Pragmas.). It has been found ! convenient to use `__attribute__' to achieve a natural attachment of ! attributes to their corresponding declarations, whereas `#pragma' is of ! use for compatibility with other compilers or constructs that do not ! naturally form part of the grammar. In addition to the attributes documented here, GCC plugins may provide their own attributes. *************** File: gcc.info, Node: Common Function A *** 25798,25842 **** The following attributes are supported on most targets. ! 'alias ("TARGET")' ! The 'alias' attribute causes the declaration to be emitted as an alias for another symbol, which must be specified. For instance, void __f () { /* Do something. */; } void f () __attribute__ ((weak, alias ("__f"))); ! defines 'f' to be a weak alias for '__f'. In C++, the mangled name ! for the target must be used. It is an error if '__f' is not defined in the same translation unit. This attribute requires assembler and object file support, and may not be available on all targets. ! 'aligned (ALIGNMENT)' This attribute specifies a minimum alignment for the function, measured in bytes. You cannot use this attribute to decrease the alignment of a function, only to increase it. However, when you explicitly specify a function alignment this overrides the effect of the ! '-falign-functions' (*note Optimize Options::) option for this function. ! Note that the effectiveness of 'aligned' attributes may be limited by inherent limitations in your linker. On many systems, the linker is only able to arrange for functions to be aligned up to a certain maximum alignment. (For some linkers, the maximum supported alignment may be very very small.) See your linker documentation for further information. ! The 'aligned' attribute can also be used for variables and fields (*note Variable Attributes::.) ! 'alloc_align' ! The 'alloc_align' attribute is used to tell the compiler that the function return value points to memory, where the returned pointer ! minimum alignment is given by one of the functions parameters. GCC ! uses this information to improve pointer alignment analysis. The function parameter denoting the allocated alignment is specified by one integer argument, whose number is the argument of --- 25979,26023 ---- The following attributes are supported on most targets. ! `alias ("TARGET")' ! The `alias' attribute causes the declaration to be emitted as an alias for another symbol, which must be specified. For instance, void __f () { /* Do something. */; } void f () __attribute__ ((weak, alias ("__f"))); ! defines `f' to be a weak alias for `__f'. In C++, the mangled ! name for the target must be used. It is an error if `__f' is not defined in the same translation unit. This attribute requires assembler and object file support, and may not be available on all targets. ! `aligned (ALIGNMENT)' This attribute specifies a minimum alignment for the function, measured in bytes. You cannot use this attribute to decrease the alignment of a function, only to increase it. However, when you explicitly specify a function alignment this overrides the effect of the ! `-falign-functions' (*note Optimize Options::) option for this function. ! Note that the effectiveness of `aligned' attributes may be limited by inherent limitations in your linker. On many systems, the linker is only able to arrange for functions to be aligned up to a certain maximum alignment. (For some linkers, the maximum supported alignment may be very very small.) See your linker documentation for further information. ! The `aligned' attribute can also be used for variables and fields (*note Variable Attributes::.) ! `alloc_align' ! The `alloc_align' attribute is used to tell the compiler that the function return value points to memory, where the returned pointer ! minimum alignment is given by one of the functions parameters. ! GCC uses this information to improve pointer alignment analysis. The function parameter denoting the allocated alignment is specified by one integer argument, whose number is the argument of *************** The following attributes are supported o *** 25846,25876 **** void* my_memalign(size_t, size_t) __attribute__((alloc_align(1))) ! declares that 'my_memalign' returns memory with minimum alignment given by parameter 1. ! 'alloc_size' ! The 'alloc_size' attribute is used to tell the compiler that the function return value points to memory, where the size is given by one or two of the functions parameters. GCC uses this information ! to improve the correctness of '__builtin_object_size'. ! The function parameter(s) denoting the allocated size are specified ! by one or two integer arguments supplied to the attribute. The ! allocated size is either the value of the single function argument ! specified or the product of the two function arguments specified. ! Argument numbering starts at one. For instance, void* my_calloc(size_t, size_t) __attribute__((alloc_size(1,2))) void* my_realloc(void*, size_t) __attribute__((alloc_size(2))) ! declares that 'my_calloc' returns memory of the size given by the ! product of parameter 1 and 2 and that 'my_realloc' returns memory of the size given by parameter 2. ! 'always_inline' Generally, functions are not inlined unless optimization is specified. For functions declared inline, this attribute inlines the function independent of any restrictions that otherwise apply --- 26027,26057 ---- void* my_memalign(size_t, size_t) __attribute__((alloc_align(1))) ! declares that `my_memalign' returns memory with minimum alignment given by parameter 1. ! `alloc_size' ! The `alloc_size' attribute is used to tell the compiler that the function return value points to memory, where the size is given by one or two of the functions parameters. GCC uses this information ! to improve the correctness of `__builtin_object_size'. ! The function parameter(s) denoting the allocated size are ! specified by one or two integer arguments supplied to the ! attribute. The allocated size is either the value of the single ! function argument specified or the product of the two function ! arguments specified. Argument numbering starts at one. For instance, void* my_calloc(size_t, size_t) __attribute__((alloc_size(1,2))) void* my_realloc(void*, size_t) __attribute__((alloc_size(2))) ! declares that `my_calloc' returns memory of the size given by the ! product of parameter 1 and 2 and that `my_realloc' returns memory of the size given by parameter 2. ! `always_inline' Generally, functions are not inlined unless optimization is specified. For functions declared inline, this attribute inlines the function independent of any restrictions that otherwise apply *************** The following attributes are supported o *** 25880,25894 **** and a failure to inline an indirect call may or may not be diagnosed. ! 'artificial' This attribute is useful for small inline wrappers that if possible should appear during debugging as a unit. Depending on the debug info format it either means marking the function as artificial or using the caller location for all instructions within the inlined body. ! 'assume_aligned' ! The 'assume_aligned' attribute is used to tell the compiler that the function return value points to memory, where the returned pointer minimum alignment is given by the first argument. If the attribute has two arguments, the second argument is misalignment --- 26061,26075 ---- and a failure to inline an indirect call may or may not be diagnosed. ! `artificial' This attribute is useful for small inline wrappers that if possible should appear during debugging as a unit. Depending on the debug info format it either means marking the function as artificial or using the caller location for all instructions within the inlined body. ! `assume_aligned' ! The `assume_aligned' attribute is used to tell the compiler that the function return value points to memory, where the returned pointer minimum alignment is given by the first argument. If the attribute has two arguments, the second argument is misalignment *************** The following attributes are supported o *** 25899,25919 **** void* my_alloc1(size_t) __attribute__((assume_aligned(16))) void* my_alloc2(size_t) __attribute__((assume_aligned(32, 8))) ! declares that 'my_alloc1' returns 16-byte aligned pointer and that ! 'my_alloc2' returns a pointer whose value modulo 32 is equal to 8. ! 'bnd_instrument' ! The 'bnd_instrument' attribute on functions is used to inform the compiler that the function should be instrumented when compiled ! with the '-fchkp-instrument-marked-only' option. ! 'bnd_legacy' ! The 'bnd_legacy' attribute on functions is used to inform the compiler that the function should not be instrumented when compiled ! with the '-fcheck-pointer-bounds' option. ! 'cold' ! The 'cold' attribute on functions is used to inform the compiler that the function is unlikely to be executed. The function is optimized for size rather than speed and on many targets it is placed into a special subsection of the text section so all cold --- 26080,26100 ---- void* my_alloc1(size_t) __attribute__((assume_aligned(16))) void* my_alloc2(size_t) __attribute__((assume_aligned(32, 8))) ! declares that `my_alloc1' returns 16-byte aligned pointer and that ! `my_alloc2' returns a pointer whose value modulo 32 is equal to 8. ! `bnd_instrument' ! The `bnd_instrument' attribute on functions is used to inform the compiler that the function should be instrumented when compiled ! with the `-fchkp-instrument-marked-only' option. ! `bnd_legacy' ! The `bnd_legacy' attribute on functions is used to inform the compiler that the function should not be instrumented when compiled ! with the `-fcheck-pointer-bounds' option. ! `cold' ! The `cold' attribute on functions is used to inform the compiler that the function is unlikely to be executed. The function is optimized for size rather than speed and on many targets it is placed into a special subsection of the text section so all cold *************** The following attributes are supported o *** 25921,25953 **** non-cold parts of program. The paths leading to calls of cold functions within code are marked as unlikely by the branch prediction mechanism. It is thus useful to mark functions used to ! handle unlikely conditions, such as 'perror', as cold to improve ! optimization of hot functions that do call marked functions in rare ! occasions. ! When profile feedback is available, via '-fprofile-use', cold functions are automatically detected and this attribute is ignored. ! 'const' Many functions do not examine any values except their arguments, and have no effects except the return value. Basically this is ! just slightly more strict class than the 'pure' attribute below, since function is not allowed to read global memory. Note that a function that has pointer arguments and examines the ! data pointed to must _not_ be declared 'const'. Likewise, a ! function that calls a non-'const' function usually must not be ! 'const'. It does not make sense for a 'const' function to return ! 'void'. ! 'constructor' ! 'destructor' ! 'constructor (PRIORITY)' ! 'destructor (PRIORITY)' ! The 'constructor' attribute causes the function to be called ! automatically before execution enters 'main ()'. Similarly, the ! 'destructor' attribute causes the function to be called ! automatically after 'main ()' completes or 'exit ()' is called. Functions with these attributes are useful for initializing data that is used implicitly during the execution of the program. --- 26102,26134 ---- non-cold parts of program. The paths leading to calls of cold functions within code are marked as unlikely by the branch prediction mechanism. It is thus useful to mark functions used to ! handle unlikely conditions, such as `perror', as cold to improve ! optimization of hot functions that do call marked functions in ! rare occasions. ! When profile feedback is available, via `-fprofile-use', cold functions are automatically detected and this attribute is ignored. ! `const' Many functions do not examine any values except their arguments, and have no effects except the return value. Basically this is ! just slightly more strict class than the `pure' attribute below, since function is not allowed to read global memory. Note that a function that has pointer arguments and examines the ! data pointed to must _not_ be declared `const'. Likewise, a ! function that calls a non-`const' function usually must not be ! `const'. It does not make sense for a `const' function to return ! `void'. ! `constructor' ! `destructor' ! `constructor (PRIORITY)' ! `destructor (PRIORITY)' ! The `constructor' attribute causes the function to be called ! automatically before execution enters `main ()'. Similarly, the ! `destructor' attribute causes the function to be called ! automatically after `main ()' completes or `exit ()' is called. Functions with these attributes are useful for initializing data that is used implicitly during the execution of the program. *************** The following attributes are supported o *** 25964,25972 **** These attributes are not currently implemented for Objective-C. ! 'deprecated' ! 'deprecated (MSG)' ! The 'deprecated' attribute results in a warning if the function is used anywhere in the source file. This is useful when identifying functions that are expected to be removed in a future version of a program. The warning also includes the location of the declaration --- 26145,26153 ---- These attributes are not currently implemented for Objective-C. ! `deprecated' ! `deprecated (MSG)' ! The `deprecated' attribute results in a warning if the function is used anywhere in the source file. This is useful when identifying functions that are expected to be removed in a future version of a program. The warning also includes the location of the declaration *************** The following attributes are supported o *** 25982,26031 **** argument, which must be a string, is printed in the warning if present. ! The 'deprecated' attribute can also be used for variables and types ! (*note Variable Attributes::, *note Type Attributes::.) ! 'error ("MESSAGE")' ! 'warning ("MESSAGE")' ! If the 'error' or 'warning' attribute is used on a function ! declaration and a call to such a function is not eliminated through ! dead code elimination or other optimizations, an error or warning ! (respectively) that includes MESSAGE is diagnosed. This is useful ! for compile-time checking, especially together with ! '__builtin_constant_p' and inline functions where checking the ! inline function arguments is not possible through 'extern char [(condition) ? 1 : -1];' tricks. While it is possible to leave the function undefined and thus invoke a link failure (to define the function with a message in ! '.gnu.warning*' section), when using these attributes the problem is diagnosed earlier and with exact location of the call even in presence of inline functions or when not emitting debugging information. ! 'externally_visible' This attribute, attached to a global variable or function, ! nullifies the effect of the '-fwhole-program' command-line option, so the object remains visible outside the current compilation unit. ! If '-fwhole-program' is used together with '-flto' and 'gold' is ! used as the linker plugin, 'externally_visible' attributes are ! automatically added to functions (not variable yet due to a current ! 'gold' issue) that are accessed outside of LTO objects according to ! resolution file produced by 'gold'. For other linkers that cannot ! generate resolution file, explicit 'externally_visible' attributes ! are still necessary. ! 'flatten' Generally, inlining into a function is limited. For a function marked with this attribute, every call inside this function is inlined, if possible. Whether the function itself is considered for inlining depends on its size and the current inlining parameters. ! 'format (ARCHETYPE, STRING-INDEX, FIRST-TO-CHECK)' ! The 'format' attribute specifies that a function takes 'printf', ! 'scanf', 'strftime' or 'strfmon' style arguments that should be type-checked against a format string. For example, the declaration: --- 26163,26212 ---- argument, which must be a string, is printed in the warning if present. ! The `deprecated' attribute can also be used for variables and ! types (*note Variable Attributes::, *note Type Attributes::.) ! `error ("MESSAGE")' ! `warning ("MESSAGE")' ! If the `error' or `warning' attribute is used on a function ! declaration and a call to such a function is not eliminated ! through dead code elimination or other optimizations, an error or ! warning (respectively) that includes MESSAGE is diagnosed. This ! is useful for compile-time checking, especially together with ! `__builtin_constant_p' and inline functions where checking the ! inline function arguments is not possible through `extern char [(condition) ? 1 : -1];' tricks. While it is possible to leave the function undefined and thus invoke a link failure (to define the function with a message in ! `.gnu.warning*' section), when using these attributes the problem is diagnosed earlier and with exact location of the call even in presence of inline functions or when not emitting debugging information. ! `externally_visible' This attribute, attached to a global variable or function, ! nullifies the effect of the `-fwhole-program' command-line option, so the object remains visible outside the current compilation unit. ! If `-fwhole-program' is used together with `-flto' and `gold' is ! used as the linker plugin, `externally_visible' attributes are ! automatically added to functions (not variable yet due to a ! current `gold' issue) that are accessed outside of LTO objects ! according to resolution file produced by `gold'. For other ! linkers that cannot generate resolution file, explicit ! `externally_visible' attributes are still necessary. ! `flatten' Generally, inlining into a function is limited. For a function marked with this attribute, every call inside this function is inlined, if possible. Whether the function itself is considered for inlining depends on its size and the current inlining parameters. ! `format (ARCHETYPE, STRING-INDEX, FIRST-TO-CHECK)' ! The `format' attribute specifies that a function takes `printf', ! `scanf', `strftime' or `strfmon' style arguments that should be type-checked against a format string. For example, the declaration: *************** The following attributes are supported o *** 26033,26198 **** my_printf (void *my_object, const char *my_format, ...) __attribute__ ((format (printf, 2, 3))); ! causes the compiler to check the arguments in calls to 'my_printf' ! for consistency with the 'printf' style format string argument ! 'my_format'. The parameter ARCHETYPE determines how the format string is ! interpreted, and should be 'printf', 'scanf', 'strftime', ! 'gnu_printf', 'gnu_scanf', 'gnu_strftime' or 'strfmon'. (You can ! also use '__printf__', '__scanf__', '__strftime__' or ! '__strfmon__'.) On MinGW targets, 'ms_printf', 'ms_scanf', and ! 'ms_strftime' are also present. ARCHETYPE values such as 'printf' refer to the formats accepted by the system's C runtime library, ! while values prefixed with 'gnu_' always refer to the formats accepted by the GNU C Library. On Microsoft Windows targets, ! values prefixed with 'ms_' refer to the formats accepted by the ! 'msvcrt.dll' library. The parameter STRING-INDEX specifies which argument is the format string argument (starting from 1), while ! FIRST-TO-CHECK is the number of the first argument to check against ! the format string. For functions where the arguments are not ! available to be checked (such as 'vprintf'), specify the third parameter as zero. In this case the compiler only checks the ! format string for consistency. For 'strftime' formats, the third parameter is required to be zero. Since non-static C++ methods ! have an implicit 'this' argument, the arguments of such methods should be counted from two, not one, when giving values for STRING-INDEX and FIRST-TO-CHECK. ! In the example above, the format string ('my_format') is the second ! argument of the function 'my_print', and the arguments to check start with the third argument, so the correct parameters for the format attribute are 2 and 3. ! The 'format' attribute allows you to identify your own functions that take format strings as arguments, so that GCC can check the calls to these functions for errors. The compiler always (unless ! '-ffreestanding' or '-fno-builtin' is used) checks formats for the ! standard library functions 'printf', 'fprintf', 'sprintf', 'scanf', ! 'fscanf', 'sscanf', 'strftime', 'vprintf', 'vfprintf' and ! 'vsprintf' whenever such warnings are requested (using '-Wformat'), ! so there is no need to modify the header file 'stdio.h'. In C99 ! mode, the functions 'snprintf', 'vsnprintf', 'vscanf', 'vfscanf' ! and 'vsscanf' are also checked. Except in strictly conforming C ! standard modes, the X/Open function 'strfmon' is also checked as ! are 'printf_unlocked' and 'fprintf_unlocked'. *Note Options ! Controlling C Dialect: C Dialect Options. ! For Objective-C dialects, 'NSString' (or '__NSString__') is recognized in the same context. Declarations including these ! format attributes are parsed for correct syntax, however the result ! of checking of such format strings is not yet defined, and is not ! carried out by this version of the compiler. The target may also provide additional types of format checks. *Note Format Checks Specific to Particular Target Machines: Target Format Checks. ! 'format_arg (STRING-INDEX)' ! The 'format_arg' attribute specifies that a function takes a format ! string for a 'printf', 'scanf', 'strftime' or 'strfmon' style ! function and modifies it (for example, to translate it into another ! language), so the result can be passed to a 'printf', 'scanf', ! 'strftime' or 'strfmon' style function (with the remaining ! arguments to the format function the same as they would have been ! for the unmodified string). For example, the declaration: extern char * my_dgettext (char *my_domain, const char *my_format) __attribute__ ((format_arg (2))); ! causes the compiler to check the arguments in calls to a 'printf', ! 'scanf', 'strftime' or 'strfmon' type function, whose format string ! argument is a call to the 'my_dgettext' function, for consistency ! with the format string argument 'my_format'. If the 'format_arg' ! attribute had not been specified, all the compiler could tell in ! such calls to format functions would be that the format string ! argument is not constant; this would generate a warning when ! '-Wformat-nonliteral' is used, but the calls could not be checked ! without the attribute. The parameter STRING-INDEX specifies which argument is the format string argument (starting from one). Since non-static C++ methods ! have an implicit 'this' argument, the arguments of such methods should be counted from two. ! The 'format_arg' attribute allows you to identify your own functions that modify format strings, so that GCC can check the ! calls to 'printf', 'scanf', 'strftime' or 'strfmon' type function whose operands are a call to one of your own function. The ! compiler always treats 'gettext', 'dgettext', and 'dcgettext' in this manner except when strict ISO C support is requested by ! '-ansi' or an appropriate '-std' option, or '-ffreestanding' or ! '-fno-builtin' is used. *Note Options Controlling C Dialect: C Dialect Options. ! For Objective-C dialects, the 'format-arg' attribute may refer to ! an 'NSString' reference for compatibility with the 'format' attribute above. ! The target may also allow additional types in 'format-arg' attributes. *Note Format Checks Specific to Particular Target Machines: Target Format Checks. ! 'gnu_inline' This attribute should be used with a function that is also declared ! with the 'inline' keyword. It directs GCC to treat the function as ! if it were defined in gnu90 mode even when compiling in C99 or gnu99 mode. ! If the function is declared 'extern', then this definition of the function is used only for inlining. In no case is the function compiled as a standalone function, not even if you take its address explicitly. Such an address becomes an external reference, as if you had only declared the function, and had not defined it. This has almost the effect of a macro. The way to use this is to put a function definition in a header file with this attribute, and put ! another copy of the function, without 'extern', in a library file. ! The definition in the header file causes most calls to the function ! to be inlined. If any uses of the function remain, they refer to ! the single copy in the library. Note that the two definitions of ! the functions need not be precisely the same, although if they do ! not have the same effect your program may behave oddly. ! In C, if the function is neither 'extern' nor 'static', then the function is compiled as a standalone function, as well as being inlined where possible. ! This is how GCC traditionally handled functions declared 'inline'. ! Since ISO C99 specifies a different semantics for 'inline', this function attribute is provided as a transition measure and as a useful feature in its own right. This attribute is available in ! GCC 4.1.3 and later. It is available if either of the preprocessor ! macros '__GNUC_GNU_INLINE__' or '__GNUC_STDC_INLINE__' are defined. ! *Note An Inline Function is As Fast As a Macro: Inline. ! In C++, this attribute does not depend on 'extern' in any way, but ! it still requires the 'inline' keyword to enable its special behavior. ! 'hot' ! The 'hot' attribute on a function is used to inform the compiler that the function is a hot spot of the compiled program. The function is optimized more aggressively and on many targets it is placed into a special subsection of the text section so all hot functions appear close together, improving locality. ! When profile feedback is available, via '-fprofile-use', hot functions are automatically detected and this attribute is ignored. ! 'ifunc ("RESOLVER")' ! The 'ifunc' attribute is used to mark a function as an indirect function using the STT_GNU_IFUNC symbol type extension to the ELF standard. This allows the resolution of the symbol value to be determined dynamically at load time, and an optimized version of the routine can be selected for the particular processor or other system characteristics determined then. To use this attribute, ! first define the implementation functions available, and a resolver ! function that returns a pointer to the selected implementation ! function. The implementation functions' declarations must match ! the API of the function being implemented, the resolver's ! declaration is be a function returning pointer to void function ! returning void: void *my_memcpy (void *dst, const void *src, size_t len) { --- 26214,26383 ---- my_printf (void *my_object, const char *my_format, ...) __attribute__ ((format (printf, 2, 3))); ! causes the compiler to check the arguments in calls to `my_printf' ! for consistency with the `printf' style format string argument ! `my_format'. The parameter ARCHETYPE determines how the format string is ! interpreted, and should be `printf', `scanf', `strftime', ! `gnu_printf', `gnu_scanf', `gnu_strftime' or `strfmon'. (You can ! also use `__printf__', `__scanf__', `__strftime__' or ! `__strfmon__'.) On MinGW targets, `ms_printf', `ms_scanf', and ! `ms_strftime' are also present. ARCHETYPE values such as `printf' refer to the formats accepted by the system's C runtime library, ! while values prefixed with `gnu_' always refer to the formats accepted by the GNU C Library. On Microsoft Windows targets, ! values prefixed with `ms_' refer to the formats accepted by the ! `msvcrt.dll' library. The parameter STRING-INDEX specifies which argument is the format string argument (starting from 1), while ! FIRST-TO-CHECK is the number of the first argument to check ! against the format string. For functions where the arguments are ! not available to be checked (such as `vprintf'), specify the third parameter as zero. In this case the compiler only checks the ! format string for consistency. For `strftime' formats, the third parameter is required to be zero. Since non-static C++ methods ! have an implicit `this' argument, the arguments of such methods should be counted from two, not one, when giving values for STRING-INDEX and FIRST-TO-CHECK. ! In the example above, the format string (`my_format') is the second ! argument of the function `my_print', and the arguments to check start with the third argument, so the correct parameters for the format attribute are 2 and 3. ! The `format' attribute allows you to identify your own functions that take format strings as arguments, so that GCC can check the calls to these functions for errors. The compiler always (unless ! `-ffreestanding' or `-fno-builtin' is used) checks formats for the ! standard library functions `printf', `fprintf', `sprintf', ! `scanf', `fscanf', `sscanf', `strftime', `vprintf', `vfprintf' and ! `vsprintf' whenever such warnings are requested (using ! `-Wformat'), so there is no need to modify the header file ! `stdio.h'. In C99 mode, the functions `snprintf', `vsnprintf', ! `vscanf', `vfscanf' and `vsscanf' are also checked. Except in ! strictly conforming C standard modes, the X/Open function ! `strfmon' is also checked as are `printf_unlocked' and ! `fprintf_unlocked'. *Note Options Controlling C Dialect: C ! Dialect Options. ! For Objective-C dialects, `NSString' (or `__NSString__') is recognized in the same context. Declarations including these ! format attributes are parsed for correct syntax, however the ! result of checking of such format strings is not yet defined, and ! is not carried out by this version of the compiler. The target may also provide additional types of format checks. *Note Format Checks Specific to Particular Target Machines: Target Format Checks. ! `format_arg (STRING-INDEX)' ! The `format_arg' attribute specifies that a function takes a format ! string for a `printf', `scanf', `strftime' or `strfmon' style ! function and modifies it (for example, to translate it into ! another language), so the result can be passed to a `printf', ! `scanf', `strftime' or `strfmon' style function (with the ! remaining arguments to the format function the same as they would ! have been for the unmodified string). For example, the ! declaration: extern char * my_dgettext (char *my_domain, const char *my_format) __attribute__ ((format_arg (2))); ! causes the compiler to check the arguments in calls to a `printf', ! `scanf', `strftime' or `strfmon' type function, whose format ! string argument is a call to the `my_dgettext' function, for ! consistency with the format string argument `my_format'. If the ! `format_arg' attribute had not been specified, all the compiler ! could tell in such calls to format functions would be that the ! format string argument is not constant; this would generate a ! warning when `-Wformat-nonliteral' is used, but the calls could ! not be checked without the attribute. The parameter STRING-INDEX specifies which argument is the format string argument (starting from one). Since non-static C++ methods ! have an implicit `this' argument, the arguments of such methods should be counted from two. ! The `format_arg' attribute allows you to identify your own functions that modify format strings, so that GCC can check the ! calls to `printf', `scanf', `strftime' or `strfmon' type function whose operands are a call to one of your own function. The ! compiler always treats `gettext', `dgettext', and `dcgettext' in this manner except when strict ISO C support is requested by ! `-ansi' or an appropriate `-std' option, or `-ffreestanding' or ! `-fno-builtin' is used. *Note Options Controlling C Dialect: C Dialect Options. ! For Objective-C dialects, the `format-arg' attribute may refer to ! an `NSString' reference for compatibility with the `format' attribute above. ! The target may also allow additional types in `format-arg' attributes. *Note Format Checks Specific to Particular Target Machines: Target Format Checks. ! `gnu_inline' This attribute should be used with a function that is also declared ! with the `inline' keyword. It directs GCC to treat the function ! as if it were defined in gnu90 mode even when compiling in C99 or gnu99 mode. ! If the function is declared `extern', then this definition of the function is used only for inlining. In no case is the function compiled as a standalone function, not even if you take its address explicitly. Such an address becomes an external reference, as if you had only declared the function, and had not defined it. This has almost the effect of a macro. The way to use this is to put a function definition in a header file with this attribute, and put ! another copy of the function, without `extern', in a library file. ! The definition in the header file causes most calls to the ! function to be inlined. If any uses of the function remain, they ! refer to the single copy in the library. Note that the two ! definitions of the functions need not be precisely the same, ! although if they do not have the same effect your program may ! behave oddly. ! In C, if the function is neither `extern' nor `static', then the function is compiled as a standalone function, as well as being inlined where possible. ! This is how GCC traditionally handled functions declared `inline'. ! Since ISO C99 specifies a different semantics for `inline', this function attribute is provided as a transition measure and as a useful feature in its own right. This attribute is available in ! GCC 4.1.3 and later. It is available if either of the ! preprocessor macros `__GNUC_GNU_INLINE__' or ! `__GNUC_STDC_INLINE__' are defined. *Note An Inline Function is ! As Fast As a Macro: Inline. ! In C++, this attribute does not depend on `extern' in any way, but ! it still requires the `inline' keyword to enable its special behavior. ! `hot' ! The `hot' attribute on a function is used to inform the compiler that the function is a hot spot of the compiled program. The function is optimized more aggressively and on many targets it is placed into a special subsection of the text section so all hot functions appear close together, improving locality. ! When profile feedback is available, via `-fprofile-use', hot functions are automatically detected and this attribute is ignored. ! `ifunc ("RESOLVER")' ! The `ifunc' attribute is used to mark a function as an indirect function using the STT_GNU_IFUNC symbol type extension to the ELF standard. This allows the resolution of the symbol value to be determined dynamically at load time, and an optimized version of the routine can be selected for the particular processor or other system characteristics determined then. To use this attribute, ! first define the implementation functions available, and a ! resolver function that returns a pointer to the selected ! implementation function. The implementation functions' ! declarations must match the API of the function being implemented, ! the resolver's declaration is be a function returning pointer to ! void function returning void: void *my_memcpy (void *dst, const void *src, size_t len) { *************** The following attributes are supported o *** 26220,26263 **** higher and GNU C Library version 2.11.1 are required to use this feature. ! 'interrupt' ! 'interrupt_handler' Many GCC back ends support attributes to indicate that a function is an interrupt handler, which tells the compiler to generate function entry and exit sequences that differ from those from regular functions. The exact syntax and behavior are target-specific; refer to the following subsections for details. ! 'leaf' Calls to external functions with this attribute must return to the current compilation unit only by return or by exception handling. In particular, a leaf function is not allowed to invoke callback functions passed to it from the current compilation unit, directly ! call functions exported by the unit, or 'longjmp' into the unit. Leaf functions might still call functions from other compilation ! units and thus they are not necessarily leaf in the sense that they ! contain no function calls at all. The attribute is intended for library functions to improve dataflow analysis. The compiler takes the hint that any data not escaping the current compilation unit cannot be used or modified by the leaf ! function. For example, the 'sin' function is a leaf function, but ! 'qsort' is not. Note that leaf functions might indirectly run a signal handler ! defined in the current compilation unit that uses static variables. ! Similarly, when lazy symbol resolution is in effect, leaf functions ! might invoke indirect functions whose resolver function or ! implementation function is defined in the current compilation unit ! and uses static variables. There is no standard-compliant way to ! write such a signal handler, resolver function, or implementation ! function, and the best that you can do is to remove the 'leaf' ! attribute or mark all such static variables 'volatile'. Lastly, ! for ELF-based systems that support symbol interposition, care ! should be taken that functions defined in the current compilation ! unit do not unexpectedly interpose other symbols based on the ! defined standards mode and defined feature test macros; otherwise ! an inadvertent callback would be added. The attribute has no effect on functions defined within the current compilation unit. This is to allow easy merging of multiple --- 26405,26448 ---- higher and GNU C Library version 2.11.1 are required to use this feature. ! `interrupt' ! `interrupt_handler' Many GCC back ends support attributes to indicate that a function is an interrupt handler, which tells the compiler to generate function entry and exit sequences that differ from those from regular functions. The exact syntax and behavior are target-specific; refer to the following subsections for details. ! `leaf' Calls to external functions with this attribute must return to the current compilation unit only by return or by exception handling. In particular, a leaf function is not allowed to invoke callback functions passed to it from the current compilation unit, directly ! call functions exported by the unit, or `longjmp' into the unit. Leaf functions might still call functions from other compilation ! units and thus they are not necessarily leaf in the sense that ! they contain no function calls at all. The attribute is intended for library functions to improve dataflow analysis. The compiler takes the hint that any data not escaping the current compilation unit cannot be used or modified by the leaf ! function. For example, the `sin' function is a leaf function, but ! `qsort' is not. Note that leaf functions might indirectly run a signal handler ! defined in the current compilation unit that uses static ! variables. Similarly, when lazy symbol resolution is in effect, ! leaf functions might invoke indirect functions whose resolver ! function or implementation function is defined in the current ! compilation unit and uses static variables. There is no ! standard-compliant way to write such a signal handler, resolver ! function, or implementation function, and the best that you can do ! is to remove the `leaf' attribute or mark all such static variables ! `volatile'. Lastly, for ELF-based systems that support symbol ! interposition, care should be taken that functions defined in the ! current compilation unit do not unexpectedly interpose other ! symbols based on the defined standards mode and defined feature ! test macros; otherwise an inadvertent callback would be added. The attribute has no effect on functions defined within the current compilation unit. This is to allow easy merging of multiple *************** The following attributes are supported o *** 26265,26337 **** optimization. For this reason the attribute is not allowed on types to annotate indirect calls. ! 'malloc' ! This tells the compiler that a function is 'malloc'-like, i.e., that the pointer P returned by the function cannot alias any other pointer valid when the function returns, and moreover no pointers to valid objects occur in any storage addressed by P. Using this attribute can improve optimization. Functions like ! 'malloc' and 'calloc' have this property because they return a pointer to uninitialized or zeroed-out storage. However, functions ! like 'realloc' do not have this property, as they can return a pointer to storage containing pointers. ! 'no_icf' ! This function attribute prevents a functions from being merged with ! another semantically equivalent function. ! 'no_instrument_function' ! If '-finstrument-functions' is given, profiling function calls are generated at entry and exit of most user-compiled functions. Functions with this attribute are not so instrumented. ! 'no_reorder' ! Do not reorder functions or variables marked 'no_reorder' against each other or top level assembler statements the executable. The ! actual order in the program will depend on the linker command line. ! Static variables marked like this are also not removed. This has a ! similar effect as the '-fno-toplevel-reorder' option, but only ! applies to the marked symbols. ! 'no_sanitize_address' ! 'no_address_safety_analysis' ! The 'no_sanitize_address' attribute on functions is used to inform the compiler that it should not instrument memory accesses in the ! function when compiling with the '-fsanitize=address' option. The ! 'no_address_safety_analysis' is a deprecated alias of the ! 'no_sanitize_address' attribute, new code should use ! 'no_sanitize_address'. ! 'no_sanitize_thread' ! The 'no_sanitize_thread' attribute on functions is used to inform the compiler that it should not instrument memory accesses in the ! function when compiling with the '-fsanitize=thread' option. ! 'no_sanitize_undefined' ! The 'no_sanitize_undefined' attribute on functions is used to inform the compiler that it should not check for undefined behavior ! in the function when compiling with the '-fsanitize=undefined' option. ! 'no_split_stack' ! If '-fsplit-stack' is given, functions have a small prologue which decides whether to split the stack. Functions with the ! 'no_split_stack' attribute do not have that prologue, and thus may run with only a small amount of stack space available. ! 'no_stack_limit' ! This attribute locally overrides the '-fstack-limit-register' and ! '-fstack-limit-symbol' command-line options; it has the effect of disabling stack limit checking in the function it applies to. ! 'noclone' This function attribute prevents a function from being considered for cloning--a mechanism that produces specialized copies of functions and which is (currently) performed by interprocedural constant propagation. ! 'noinline' This function attribute prevents a function from being considered for inlining. If the function does not have side-effects, there are optimizations other than inlining that cause function calls to --- 26450,26522 ---- optimization. For this reason the attribute is not allowed on types to annotate indirect calls. ! `malloc' ! This tells the compiler that a function is `malloc'-like, i.e., that the pointer P returned by the function cannot alias any other pointer valid when the function returns, and moreover no pointers to valid objects occur in any storage addressed by P. Using this attribute can improve optimization. Functions like ! `malloc' and `calloc' have this property because they return a pointer to uninitialized or zeroed-out storage. However, functions ! like `realloc' do not have this property, as they can return a pointer to storage containing pointers. ! `no_icf' ! This function attribute prevents a functions from being merged ! with another semantically equivalent function. ! `no_instrument_function' ! If `-finstrument-functions' is given, profiling function calls are generated at entry and exit of most user-compiled functions. Functions with this attribute are not so instrumented. ! `no_reorder' ! Do not reorder functions or variables marked `no_reorder' against each other or top level assembler statements the executable. The ! actual order in the program will depend on the linker command ! line. Static variables marked like this are also not removed. ! This has a similar effect as the `-fno-toplevel-reorder' option, ! but only applies to the marked symbols. ! `no_sanitize_address' ! `no_address_safety_analysis' ! The `no_sanitize_address' attribute on functions is used to inform the compiler that it should not instrument memory accesses in the ! function when compiling with the `-fsanitize=address' option. The ! `no_address_safety_analysis' is a deprecated alias of the ! `no_sanitize_address' attribute, new code should use ! `no_sanitize_address'. ! `no_sanitize_thread' ! The `no_sanitize_thread' attribute on functions is used to inform the compiler that it should not instrument memory accesses in the ! function when compiling with the `-fsanitize=thread' option. ! `no_sanitize_undefined' ! The `no_sanitize_undefined' attribute on functions is used to inform the compiler that it should not check for undefined behavior ! in the function when compiling with the `-fsanitize=undefined' option. ! `no_split_stack' ! If `-fsplit-stack' is given, functions have a small prologue which decides whether to split the stack. Functions with the ! `no_split_stack' attribute do not have that prologue, and thus may run with only a small amount of stack space available. ! `no_stack_limit' ! This attribute locally overrides the `-fstack-limit-register' and ! `-fstack-limit-symbol' command-line options; it has the effect of disabling stack limit checking in the function it applies to. ! `noclone' This function attribute prevents a function from being considered for cloning--a mechanism that produces specialized copies of functions and which is (currently) performed by interprocedural constant propagation. ! `noinline' This function attribute prevents a function from being considered for inlining. If the function does not have side-effects, there are optimizations other than inlining that cause function calls to *************** The following attributes are supported o *** 26342,26364 **** (*note Extended Asm::) in the called function, to serve as a special side-effect. ! 'nonnull (ARG-INDEX, ...)' ! The 'nonnull' attribute specifies that some function parameters should be non-null pointers. For instance, the declaration: extern void * my_memcpy (void *dest, const void *src, size_t len) __attribute__((nonnull (1, 2))); ! causes the compiler to check that, in calls to 'my_memcpy', arguments DEST and SRC are non-null. If the compiler determines that a null pointer is passed in an argument slot marked as ! non-null, and the '-Wnonnull' option is enabled, a warning is issued. The compiler may also choose to make optimizations based on the knowledge that certain function arguments will never be null. ! If no argument index list is given to the 'nonnull' attribute, all pointer arguments are marked as non-null. To illustrate, the following declaration is equivalent to the previous example: --- 26527,26549 ---- (*note Extended Asm::) in the called function, to serve as a special side-effect. ! `nonnull (ARG-INDEX, ...)' ! The `nonnull' attribute specifies that some function parameters should be non-null pointers. For instance, the declaration: extern void * my_memcpy (void *dest, const void *src, size_t len) __attribute__((nonnull (1, 2))); ! causes the compiler to check that, in calls to `my_memcpy', arguments DEST and SRC are non-null. If the compiler determines that a null pointer is passed in an argument slot marked as ! non-null, and the `-Wnonnull' option is enabled, a warning is issued. The compiler may also choose to make optimizations based on the knowledge that certain function arguments will never be null. ! If no argument index list is given to the `nonnull' attribute, all pointer arguments are marked as non-null. To illustrate, the following declaration is equivalent to the previous example: *************** The following attributes are supported o *** 26366,26373 **** my_memcpy (void *dest, const void *src, size_t len) __attribute__((nonnull)); ! 'noplt' ! The 'noplt' attribute is the counterpart to option '-fno-plt'. Calls to functions marked with this attribute in position-independent code do not use the PLT. --- 26551,26558 ---- my_memcpy (void *dest, const void *src, size_t len) __attribute__((nonnull)); ! `noplt' ! The `noplt' attribute is the counterpart to option `-fno-plt'. Calls to functions marked with this attribute in position-independent code do not use the PLT. *************** The following attributes are supported o *** 26382,26400 **** /* ... */ } ! The 'noplt' attribute on function 'foo' tells the compiler to ! assume that the function 'foo' is externally defined and that the ! call to 'foo' must avoid the PLT in position-independent code. In position-dependent code, a few targets also convert calls to functions that are marked to not use the PLT to use the GOT instead. ! 'noreturn' ! A few standard library functions, such as 'abort' and 'exit', cannot return. GCC knows this automatically. Some programs define their own functions that never return. You can declare them ! 'noreturn' to tell the compiler this fact. For example, void fatal () __attribute__ ((noreturn)); --- 26567,26585 ---- /* ... */ } ! The `noplt' attribute on function `foo' tells the compiler to ! assume that the function `foo' is externally defined and that the ! call to `foo' must avoid the PLT in position-independent code. In position-dependent code, a few targets also convert calls to functions that are marked to not use the PLT to use the GOT instead. ! `noreturn' ! A few standard library functions, such as `abort' and `exit', cannot return. GCC knows this automatically. Some programs define their own functions that never return. You can declare them ! `noreturn' to tell the compiler this fact. For example, void fatal () __attribute__ ((noreturn)); *************** The following attributes are supported o *** 26405,26443 **** exit (1); } ! The 'noreturn' keyword tells the compiler to assume that 'fatal' cannot return. It can then optimize without regard to what would ! happen if 'fatal' ever did return. This makes slightly better code. More importantly, it helps avoid spurious warnings of uninitialized variables. ! The 'noreturn' keyword does not affect the exceptional path when ! that applies: a 'noreturn'-marked function may still return to the ! caller by throwing an exception or calling 'longjmp'. Do not assume that registers saved by the calling function are ! restored before calling the 'noreturn' function. ! It does not make sense for a 'noreturn' function to have a return ! type other than 'void'. ! 'nothrow' ! The 'nothrow' attribute is used to inform the compiler that a function cannot throw an exception. For example, most functions in the standard C library can be guaranteed not to throw an exception ! with the notable exceptions of 'qsort' and 'bsearch' that take function pointer arguments. ! 'optimize' ! The 'optimize' attribute is used to specify that a function is to be compiled with different optimization options than specified on the command line. Arguments can either be numbers or strings. Numbers are assumed to be an optimization level. Strings that ! begin with 'O' are assumed to be an optimization option, while ! other options are assumed to be used with a '-f' prefix. You can ! also use the '#pragma GCC optimize' pragma to set the optimization options that affect more than one function. *Note Function ! Specific Option Pragmas::, for details about the '#pragma GCC optimize' pragma. This can be used for instance to have frequently-executed functions --- 26590,26628 ---- exit (1); } ! The `noreturn' keyword tells the compiler to assume that `fatal' cannot return. It can then optimize without regard to what would ! happen if `fatal' ever did return. This makes slightly better code. More importantly, it helps avoid spurious warnings of uninitialized variables. ! The `noreturn' keyword does not affect the exceptional path when ! that applies: a `noreturn'-marked function may still return to the ! caller by throwing an exception or calling `longjmp'. Do not assume that registers saved by the calling function are ! restored before calling the `noreturn' function. ! It does not make sense for a `noreturn' function to have a return ! type other than `void'. ! `nothrow' ! The `nothrow' attribute is used to inform the compiler that a function cannot throw an exception. For example, most functions in the standard C library can be guaranteed not to throw an exception ! with the notable exceptions of `qsort' and `bsearch' that take function pointer arguments. ! `optimize' ! The `optimize' attribute is used to specify that a function is to be compiled with different optimization options than specified on the command line. Arguments can either be numbers or strings. Numbers are assumed to be an optimization level. Strings that ! begin with `O' are assumed to be an optimization option, while ! other options are assumed to be used with a `-f' prefix. You can ! also use the `#pragma GCC optimize' pragma to set the optimization options that affect more than one function. *Note Function ! Specific Option Pragmas::, for details about the `#pragma GCC optimize' pragma. This can be used for instance to have frequently-executed functions *************** The following attributes are supported o *** 26445,26471 **** faster and larger code, while other functions can be compiled with less aggressive options. ! 'pure' Many functions have no effects except the return value and their return value depends only on the parameters and/or global variables. Such a function can be subject to common subexpression elimination and loop optimization just as an arithmetic operator would be. These functions should be declared with the attribute ! 'pure'. For example, int square (int) __attribute__ ((pure)); ! says that the hypothetical function 'square' is safe to call fewer times than the program says. ! Some common examples of pure functions are 'strlen' or 'memcmp'. ! Interesting non-pure functions are functions with infinite loops or ! those depending on volatile memory or other system resource, that ! may change between two consecutive calls (such as 'feof' in a multithreading environment). ! 'returns_nonnull' ! The 'returns_nonnull' attribute specifies that the function return value should be a non-null pointer. For instance, the declaration: extern void * --- 26630,26656 ---- faster and larger code, while other functions can be compiled with less aggressive options. ! `pure' Many functions have no effects except the return value and their return value depends only on the parameters and/or global variables. Such a function can be subject to common subexpression elimination and loop optimization just as an arithmetic operator would be. These functions should be declared with the attribute ! `pure'. For example, int square (int) __attribute__ ((pure)); ! says that the hypothetical function `square' is safe to call fewer times than the program says. ! Some common examples of pure functions are `strlen' or `memcmp'. ! Interesting non-pure functions are functions with infinite loops ! or those depending on volatile memory or other system resource, ! that may change between two consecutive calls (such as `feof' in a multithreading environment). ! `returns_nonnull' ! The `returns_nonnull' attribute specifies that the function return value should be a non-null pointer. For instance, the declaration: extern void * *************** The following attributes are supported o *** 26474,26531 **** lets the compiler optimize callers based on the knowledge that the return value will never be null. ! 'returns_twice' ! The 'returns_twice' attribute tells the compiler that a function may return more than one time. The compiler ensures that all registers are dead before calling such a function and emits a warning about the variables that may be clobbered after the second ! return from the function. Examples of such functions are 'setjmp' ! and 'vfork'. The 'longjmp'-like counterpart of such function, if ! any, might need to be marked with the 'noreturn' attribute. ! 'section ("SECTION-NAME")' ! Normally, the compiler places the code it generates in the 'text' section. Sometimes, however, you need additional sections, or you need certain particular functions to appear in special sections. ! The 'section' attribute specifies that a function lives in a particular section. For example, the declaration: extern void foobar (void) __attribute__ ((section ("bar"))); ! puts the function 'foobar' in the 'bar' section. Some file formats do not support arbitrary sections so the ! 'section' attribute is not available on all platforms. If you need ! to map the entire contents of a module to a particular section, ! consider using the facilities of the linker instead. ! 'sentinel' ! This function attribute ensures that a parameter in a function call ! is an explicit 'NULL'. The attribute is only valid on variadic ! functions. By default, the sentinel is located at position zero, ! the last parameter of the function call. If an optional integer ! position argument P is supplied to the attribute, the sentinel must ! be located at position P counting backwards from the end of the ! argument list. __attribute__ ((sentinel)) is equivalent to __attribute__ ((sentinel(0))) The attribute is automatically set with a position of 0 for the ! built-in functions 'execl' and 'execlp'. The built-in function ! 'execle' has the attribute set with a position of 1. ! A valid 'NULL' in this context is defined as zero with any pointer ! type. If your system defines the 'NULL' macro with an integer type ! then you need to add an explicit cast. GCC replaces 'stddef.h' with a copy that redefines NULL appropriately. The warnings for missing or incorrect sentinels are enabled with ! '-Wformat'. ! 'simd' ! 'simd("MASK")' This attribute enables creation of one or more function versions that can process multiple arguments using SIMD instructions from a single invocation. Specifying this attribute allows compiler to --- 26659,26716 ---- lets the compiler optimize callers based on the knowledge that the return value will never be null. ! `returns_twice' ! The `returns_twice' attribute tells the compiler that a function may return more than one time. The compiler ensures that all registers are dead before calling such a function and emits a warning about the variables that may be clobbered after the second ! return from the function. Examples of such functions are `setjmp' ! and `vfork'. The `longjmp'-like counterpart of such function, if ! any, might need to be marked with the `noreturn' attribute. ! `section ("SECTION-NAME")' ! Normally, the compiler places the code it generates in the `text' section. Sometimes, however, you need additional sections, or you need certain particular functions to appear in special sections. ! The `section' attribute specifies that a function lives in a particular section. For example, the declaration: extern void foobar (void) __attribute__ ((section ("bar"))); ! puts the function `foobar' in the `bar' section. Some file formats do not support arbitrary sections so the ! `section' attribute is not available on all platforms. If you ! need to map the entire contents of a module to a particular ! section, consider using the facilities of the linker instead. ! `sentinel' ! This function attribute ensures that a parameter in a function ! call is an explicit `NULL'. The attribute is only valid on ! variadic functions. By default, the sentinel is located at ! position zero, the last parameter of the function call. If an ! optional integer position argument P is supplied to the attribute, ! the sentinel must be located at position P counting backwards from ! the end of the argument list. __attribute__ ((sentinel)) is equivalent to __attribute__ ((sentinel(0))) The attribute is automatically set with a position of 0 for the ! built-in functions `execl' and `execlp'. The built-in function ! `execle' has the attribute set with a position of 1. ! A valid `NULL' in this context is defined as zero with any pointer ! type. If your system defines the `NULL' macro with an integer type ! then you need to add an explicit cast. GCC replaces `stddef.h' with a copy that redefines NULL appropriately. The warnings for missing or incorrect sentinels are enabled with ! `-Wformat'. ! `simd' ! `simd("MASK")' This attribute enables creation of one or more function versions that can process multiple arguments using SIMD instructions from a single invocation. Specifying this attribute allows compiler to *************** The following attributes are supported o *** 26535,26622 **** document. For x86_64 target this document can be found here (https://sourceware.org/glibc/wiki/libmvec?action=AttachFile&do=view&target=VectorABI.txt). ! The optional argument MASK may have the value 'notinbranch' or ! 'inbranch', and instructs the compiler to generate non-masked or ! masked clones correspondingly. By default, all clones are generated. ! The attribute should not be used together with Cilk Plus 'vector' attribute on the same function. ! If the attribute is specified and '#pragma omp declare simd' is ! present on a declaration and the '-fopenmp' or '-fopenmp-simd' switch is specified, then the attribute is ignored. ! 'stack_protect' This attribute adds stack protection code to the function if flags ! '-fstack-protector', '-fstack-protector-strong' or ! '-fstack-protector-explicit' are set. ! 'target (OPTIONS)' ! Multiple target back ends implement the 'target' attribute to specify that a function is to be compiled with different target options than specified on the command line. This can be used for instance to have functions compiled with a different ISA (instruction set architecture) than the default. You can also use ! the '#pragma GCC target' pragma to set more than one function to be ! compiled with specific target options. *Note Function Specific ! Option Pragmas::, for details about the '#pragma GCC target' pragma. For instance, on an x86, you could declare one function with the ! 'target("sse4.1,arch=core2")' attribute and another with ! 'target("sse4a,arch=amdfam10")'. This is equivalent to compiling ! the first function with '-msse4.1' and '-march=core2' options, and ! the second function with '-msse4a' and '-march=amdfam10' options. It is up to you to make sure that a function is only invoked on a machine that supports the particular ISA it is compiled for (for ! example by using 'cpuid' on x86 to determine what feature bits and architecture family are used). int core2_func (void) __attribute__ ((__target__ ("arch=core2"))); int sse3_func (void) __attribute__ ((__target__ ("sse3"))); You can either use multiple strings separated by commas to specify ! multiple options, or separate the options with a comma (',') within ! a single string. The options supported are specific to each target; refer to *note x86 Function Attributes::, *note PowerPC Function Attributes::, *note ARM Function Attributes::,and *note Nios II Function Attributes::, for details. ! 'target_clones (OPTIONS)' ! The 'target_clones' attribute is used to specify that a function be ! cloned into multiple versions compiled with different target options than specified on the command line. The supported options ! and restrictions are the same as for 'target' attribute. For instance, on an x86, you could compile a function with ! 'target_clones("sse4.1,avx")'. GCC creates two function clones, ! one compiled with '-msse4.1' and another with '-mavx'. It also ! creates a resolver function (see the 'ifunc' attribute above) that dynamically selects a clone suitable for current architecture. ! 'unused' This attribute, attached to a function, means that the function is meant to be possibly unused. GCC does not produce a warning for this function. ! 'used' This attribute, attached to a function, means that code must be emitted for the function even if it appears that the function is not referenced. This is useful, for example, when the function is referenced only in inline assembly. When applied to a member function of a C++ class template, the ! attribute also means that the function is instantiated if the class ! itself is instantiated. ! 'visibility ("VISIBILITY_TYPE")' This attribute affects the linkage of the declaration to which it ! is attached. It can be applied to variables (*note Common Variable ! Attributes::) and types (*note Common Type Attributes::) as well as ! functions. There are four supported VISIBILITY_TYPE values: default, hidden, protected or internal visibility. --- 26720,26807 ---- document. For x86_64 target this document can be found here (https://sourceware.org/glibc/wiki/libmvec?action=AttachFile&do=view&target=VectorABI.txt). ! The optional argument MASK may have the value `notinbranch' or ! `inbranch', and instructs the compiler to generate non-masked or ! masked clones correspondingly. By default, all clones are generated. ! The attribute should not be used together with Cilk Plus `vector' attribute on the same function. ! If the attribute is specified and `#pragma omp declare simd' is ! present on a declaration and the `-fopenmp' or `-fopenmp-simd' switch is specified, then the attribute is ignored. ! `stack_protect' This attribute adds stack protection code to the function if flags ! `-fstack-protector', `-fstack-protector-strong' or ! `-fstack-protector-explicit' are set. ! `target (OPTIONS)' ! Multiple target back ends implement the `target' attribute to specify that a function is to be compiled with different target options than specified on the command line. This can be used for instance to have functions compiled with a different ISA (instruction set architecture) than the default. You can also use ! the `#pragma GCC target' pragma to set more than one function to ! be compiled with specific target options. *Note Function Specific ! Option Pragmas::, for details about the `#pragma GCC target' pragma. For instance, on an x86, you could declare one function with the ! `target("sse4.1,arch=core2")' attribute and another with ! `target("sse4a,arch=amdfam10")'. This is equivalent to compiling ! the first function with `-msse4.1' and `-march=core2' options, and ! the second function with `-msse4a' and `-march=amdfam10' options. It is up to you to make sure that a function is only invoked on a machine that supports the particular ISA it is compiled for (for ! example by using `cpuid' on x86 to determine what feature bits and architecture family are used). int core2_func (void) __attribute__ ((__target__ ("arch=core2"))); int sse3_func (void) __attribute__ ((__target__ ("sse3"))); You can either use multiple strings separated by commas to specify ! multiple options, or separate the options with a comma (`,') ! within a single string. The options supported are specific to each target; refer to *note x86 Function Attributes::, *note PowerPC Function Attributes::, *note ARM Function Attributes::,and *note Nios II Function Attributes::, for details. ! `target_clones (OPTIONS)' ! The `target_clones' attribute is used to specify that a function ! be cloned into multiple versions compiled with different target options than specified on the command line. The supported options ! and restrictions are the same as for `target' attribute. For instance, on an x86, you could compile a function with ! `target_clones("sse4.1,avx")'. GCC creates two function clones, ! one compiled with `-msse4.1' and another with `-mavx'. It also ! creates a resolver function (see the `ifunc' attribute above) that dynamically selects a clone suitable for current architecture. ! `unused' This attribute, attached to a function, means that the function is meant to be possibly unused. GCC does not produce a warning for this function. ! `used' This attribute, attached to a function, means that code must be emitted for the function even if it appears that the function is not referenced. This is useful, for example, when the function is referenced only in inline assembly. When applied to a member function of a C++ class template, the ! attribute also means that the function is instantiated if the ! class itself is instantiated. ! `visibility ("VISIBILITY_TYPE")' This attribute affects the linkage of the declaration to which it ! is attached. It can be applied to variables (*note Common ! Variable Attributes::) and types (*note Common Type Attributes::) ! as well as functions. There are four supported VISIBILITY_TYPE values: default, hidden, protected or internal visibility. *************** The following attributes are supported o *** 26625,26634 **** f () { /* Do something. */; } int i __attribute__ ((visibility ("hidden"))); ! The possible values of VISIBILITY_TYPE correspond to the visibility ! settings in the ELF gABI. ! 'default' Default visibility is the normal case for the object file format. This value is available for the visibility attribute to override other options that may change the assumed --- 26810,26819 ---- f () { /* Do something. */; } int i __attribute__ ((visibility ("hidden"))); ! The possible values of VISIBILITY_TYPE correspond to the ! visibility settings in the ELF gABI. ! `default' Default visibility is the normal case for the object file format. This value is available for the visibility attribute to override other options that may change the assumed *************** The following attributes are supported o *** 26644,26675 **** Default visibility corresponds to "external linkage" in the language. ! 'hidden' Hidden visibility indicates that the entity declared has a new form of linkage, which we call "hidden linkage". Two declarations of an object with hidden linkage refer to the same object if they are in the same shared object. ! 'internal' Internal visibility is like hidden visibility, but with additional processor specific semantics. Unless otherwise specified by the psABI, GCC defines internal visibility to mean that a function is _never_ called from another module. ! Compare this with hidden functions which, while they cannot be ! referenced directly by other modules, can be referenced indirectly via function pointers. By indicating that a ! function cannot be called from outside the module, GCC may for ! instance omit the load of a PIC register since it is known that the calling function loaded the correct value. ! 'protected' Protected visibility is like default visibility except that it indicates that references within the defining module bind to the definition in that module. That is, the declared entity cannot be overridden by another module. All visibilities are supported on many, but not all, ELF targets ! (supported when the assembler supports the '.visibility' pseudo-op). Default visibility is supported everywhere. Hidden visibility is supported on Darwin targets. --- 26829,26861 ---- Default visibility corresponds to "external linkage" in the language. ! `hidden' Hidden visibility indicates that the entity declared has a new form of linkage, which we call "hidden linkage". Two declarations of an object with hidden linkage refer to the same object if they are in the same shared object. ! `internal' Internal visibility is like hidden visibility, but with additional processor specific semantics. Unless otherwise specified by the psABI, GCC defines internal visibility to mean that a function is _never_ called from another module. ! Compare this with hidden functions which, while they cannot ! be referenced directly by other modules, can be referenced indirectly via function pointers. By indicating that a ! function cannot be called from outside the module, GCC may ! for instance omit the load of a PIC register since it is known that the calling function loaded the correct value. ! `protected' Protected visibility is like default visibility except that it indicates that references within the defining module bind to the definition in that module. That is, the declared entity cannot be overridden by another module. + All visibilities are supported on many, but not all, ELF targets ! (supported when the assembler supports the `.visibility' pseudo-op). Default visibility is supported everywhere. Hidden visibility is supported on Darwin targets. *************** The following attributes are supported o *** 26701,26707 **** This attribute applies only to the particular namespace body, not to other definitions of the same namespace; it is equivalent to ! using '#pragma GCC visibility' before and after the namespace definition (*note Visibility Pragmas::). In C++, if a template argument has limited visibility, this --- 26887,26893 ---- This attribute applies only to the particular namespace body, not to other definitions of the same namespace; it is equivalent to ! using `#pragma GCC visibility' before and after the namespace definition (*note Visibility Pragmas::). In C++, if a template argument has limited visibility, this *************** The following attributes are supported o *** 26712,26723 **** If both the template and enclosing class have explicit visibility, the visibility from the template is used. ! 'warn_unused_result' ! The 'warn_unused_result' attribute causes a warning to be emitted if a caller of the function with this attribute does not use its return value. This is useful for functions where not checking the result is either a security problem or always a bug, such as ! 'realloc'. int fn () __attribute__ ((warn_unused_result)); int foo () --- 26898,26909 ---- If both the template and enclosing class have explicit visibility, the visibility from the template is used. ! `warn_unused_result' ! The `warn_unused_result' attribute causes a warning to be emitted if a caller of the function with this attribute does not use its return value. This is useful for functions where not checking the result is either a security problem or always a bug, such as ! `realloc'. int fn () __attribute__ ((warn_unused_result)); int foo () *************** The following attributes are supported o *** 26729,26751 **** results in warning on line 5. ! 'weak' ! The 'weak' attribute causes the declaration to be emitted as a weak symbol rather than a global. This is primarily useful in defining library functions that can be overridden in user code, though it can also be used with non-function declarations. Weak symbols are supported for ELF targets, and also for a.out targets when using the GNU assembler and linker. ! 'weakref' ! 'weakref ("TARGET")' ! The 'weakref' attribute marks a declaration as a weak reference. ! Without arguments, it should be accompanied by an 'alias' attribute naming the target symbol. Optionally, the TARGET may be given as ! an argument to 'weakref' itself. In either case, 'weakref' ! implicitly marks the declaration as 'weak'. Without a TARGET, ! given as an argument to 'weakref' or to 'alias', 'weakref' is ! equivalent to 'weak'. static int x() __attribute__ ((weakref ("y"))); /* is equivalent to... */ --- 26915,26937 ---- results in warning on line 5. ! `weak' ! The `weak' attribute causes the declaration to be emitted as a weak symbol rather than a global. This is primarily useful in defining library functions that can be overridden in user code, though it can also be used with non-function declarations. Weak symbols are supported for ELF targets, and also for a.out targets when using the GNU assembler and linker. ! `weakref' ! `weakref ("TARGET")' ! The `weakref' attribute marks a declaration as a weak reference. ! Without arguments, it should be accompanied by an `alias' attribute naming the target symbol. Optionally, the TARGET may be given as ! an argument to `weakref' itself. In either case, `weakref' ! implicitly marks the declaration as `weak'. Without a TARGET, ! given as an argument to `weakref' or to `alias', `weakref' is ! equivalent to `weak'. static int x() __attribute__ ((weakref ("y"))); /* is equivalent to... */ *************** The following attributes are supported o *** 26755,26763 **** static int x() __attribute__ ((alias ("y"))); A weak reference is an alias that does not by itself require a ! definition to be given for the target symbol. If the target symbol ! is only referenced through weak references, then it becomes a ! 'weak' undefined symbol. If it is directly referenced, however, then such strong references prevail, and a definition is required for the symbol, not necessarily in the same translation unit. --- 26941,26949 ---- static int x() __attribute__ ((alias ("y"))); A weak reference is an alias that does not by itself require a ! definition to be given for the target symbol. If the target ! symbol is only referenced through weak references, then it becomes ! a `weak' undefined symbol. If it is directly referenced, however, then such strong references prevail, and a definition is required for the symbol, not necessarily in the same translation unit. *************** The following attributes are supported o *** 26766,26773 **** symbol, declaring it as weak, compiling the two separate translation units and performing a reloadable link on them. ! At present, a declaration to which 'weakref' is attached can only ! be 'static'.  File: gcc.info, Node: AArch64 Function Attributes, Next: ARC Function Attributes, Prev: Common Function Attributes, Up: Function Attributes --- 26952,26960 ---- symbol, declaring it as weak, compiling the two separate translation units and performing a reloadable link on them. ! At present, a declaration to which `weakref' is attached can only ! be `static'. !  File: gcc.info, Node: AArch64 Function Attributes, Next: ARC Function Attributes, Prev: Common Function Attributes, Up: Function Attributes *************** AArch64 target. For the most part, thes *** 26780,26838 **** similar command-line options (*note AArch64 Options::), but on a per-function basis. ! 'general-regs-only' Indicates that no floating-point or Advanced SIMD registers should be used when generating code for this function. If the function explicitly uses floating-point code, then the compiler gives an error. This is the same behavior as that of the command-line ! option '-mgeneral-regs-only'. ! 'fix-cortex-a53-835769' Indicates that the workaround for the Cortex-A53 erratum 835769 should be applied to this function. To explicitly disable the workaround for this function specify the negated form: ! 'no-fix-cortex-a53-835769'. This corresponds to the behavior of ! the command line options '-mfix-cortex-a53-835769' and ! '-mno-fix-cortex-a53-835769'. ! 'cmodel=' ! Indicates that code should be generated for a particular code model ! for this function. The behavior and permissible arguments are the ! same as for the command line option '-mcmodel='. ! 'strict-align' ! Indicates that the compiler should not assume that unaligned memory ! references are handled by the system. The behavior is the same as ! for the command-line option '-mstrict-align'. ! 'omit-leaf-frame-pointer' Indicates that the frame pointer should be omitted for a leaf function call. To keep the frame pointer, the inverse attribute ! 'no-omit-leaf-frame-pointer' can be specified. These attributes have the same behavior as the command-line options ! '-momit-leaf-frame-pointer' and '-mno-omit-leaf-frame-pointer'. ! 'tls-dialect=' Specifies the TLS dialect to use for this function. The behavior and permissible arguments are the same as for the command-line ! option '-mtls-dialect='. ! 'arch=' Specifies the architecture version and architectural extensions to use for this function. The behavior and permissible arguments are ! the same as for the '-march=' command-line option. ! 'tune=' Specifies the core for which to tune the performance of this function. The behavior and permissible arguments are the same as ! for the '-mtune=' command-line option. ! 'cpu=' Specifies the core for which to tune the performance of this function and also whose architectural features to use. The ! behavior and valid arguments are the same as for the '-mcpu=' command-line option. The above target attributes can be specified as follows: __attribute__((target("ATTR-STRING"))) --- 26967,27026 ---- similar command-line options (*note AArch64 Options::), but on a per-function basis. ! `general-regs-only' Indicates that no floating-point or Advanced SIMD registers should be used when generating code for this function. If the function explicitly uses floating-point code, then the compiler gives an error. This is the same behavior as that of the command-line ! option `-mgeneral-regs-only'. ! `fix-cortex-a53-835769' Indicates that the workaround for the Cortex-A53 erratum 835769 should be applied to this function. To explicitly disable the workaround for this function specify the negated form: ! `no-fix-cortex-a53-835769'. This corresponds to the behavior of ! the command line options `-mfix-cortex-a53-835769' and ! `-mno-fix-cortex-a53-835769'. ! `cmodel=' ! Indicates that code should be generated for a particular code ! model for this function. The behavior and permissible arguments ! are the same as for the command line option `-mcmodel='. ! `strict-align' ! Indicates that the compiler should not assume that unaligned ! memory references are handled by the system. The behavior is the ! same as for the command-line option `-mstrict-align'. ! `omit-leaf-frame-pointer' Indicates that the frame pointer should be omitted for a leaf function call. To keep the frame pointer, the inverse attribute ! `no-omit-leaf-frame-pointer' can be specified. These attributes have the same behavior as the command-line options ! `-momit-leaf-frame-pointer' and `-mno-omit-leaf-frame-pointer'. ! `tls-dialect=' Specifies the TLS dialect to use for this function. The behavior and permissible arguments are the same as for the command-line ! option `-mtls-dialect='. ! `arch=' Specifies the architecture version and architectural extensions to use for this function. The behavior and permissible arguments are ! the same as for the `-march=' command-line option. ! `tune=' Specifies the core for which to tune the performance of this function. The behavior and permissible arguments are the same as ! for the `-mtune=' command-line option. ! `cpu=' Specifies the core for which to tune the performance of this function and also whose architectural features to use. The ! behavior and valid arguments are the same as for the `-mcpu=' command-line option. + The above target attributes can be specified as follows: __attribute__((target("ATTR-STRING"))) *************** per-function basis. *** 26842,26848 **** return a + 5; } ! where 'ATTR-STRING' is one of the attribute strings specified above. Additionally, the architectural extension string may be specified on its own. This can be used to turn on and off particular architectural --- 27030,27036 ---- return a + 5; } ! where `ATTR-STRING' is one of the attribute strings specified above. Additionally, the architectural extension string may be specified on its own. This can be used to turn on and off particular architectural *************** or core. Example: *** 26856,26867 **** return a + 5; } ! In this example 'target("+crc+nocrypto")' enables the 'crc' extension ! and disables the 'crypto' extension for the function 'foo' without ! modifying an existing '-march=' or '-mcpu' option. ! Multiple target function attributes can be specified by separating them ! with a comma. For example: __attribute__((target("arch=armv8-a+crc+crypto,tune=cortex-a53"))) int foo (int a) --- 27044,27055 ---- return a + 5; } ! In this example `target("+crc+nocrypto")' enables the `crc' extension ! and disables the `crypto' extension for the function `foo' without ! modifying an existing `-march=' or `-mcpu' option. ! Multiple target function attributes can be specified by separating ! them with a comma. For example: __attribute__((target("arch=armv8-a+crc+crypto,tune=cortex-a53"))) int foo (int a) *************** with a comma. For example: *** 26869,26876 **** return a + 5; } ! is valid and compiles function 'foo' for ARMv8-A with 'crc' and ! 'crypto' extensions and tunes it for 'cortex-a53'. 6.31.2.1 Inlining rules ....................... --- 27057,27064 ---- return a + 5; } ! is valid and compiles function `foo' for ARMv8-A with `crc' and ! `crypto' extensions and tunes it for `cortex-a53'. 6.31.2.1 Inlining rules ....................... *************** target options can affect function inlin *** 26881,26902 **** In particular, a caller function can inline a callee function only if the architectural features available to the callee are a subset of the ! features available to the caller. For example: A function 'foo' ! compiled with '-march=armv8-a+crc', or tagged with the equivalent ! 'arch=armv8-a+crc' attribute, can inline a function 'bar' compiled with ! '-march=armv8-a+nocrc' because the all the architectural features that ! function 'bar' requires are available to function 'foo'. Conversely, ! function 'bar' cannot inline function 'foo'. ! Additionally inlining a function compiled with '-mstrict-align' into a ! function compiled without '-mstrict-align' is not allowed. However, ! inlining a function compiled without '-mstrict-align' into a function ! compiled with '-mstrict-align' is allowed. ! Note that CPU tuning options and attributes such as the '-mcpu=', ! '-mtune=' do not inhibit inlining unless the CPU specified by the ! '-mcpu=' option or the 'cpu=' attribute conflicts with the architectural ! feature rules specified above.  File: gcc.info, Node: ARC Function Attributes, Next: ARM Function Attributes, Prev: AArch64 Function Attributes, Up: Function Attributes --- 27069,27090 ---- In particular, a caller function can inline a callee function only if the architectural features available to the callee are a subset of the ! features available to the caller. For example: A function `foo' ! compiled with `-march=armv8-a+crc', or tagged with the equivalent ! `arch=armv8-a+crc' attribute, can inline a function `bar' compiled with ! `-march=armv8-a+nocrc' because the all the architectural features that ! function `bar' requires are available to function `foo'. Conversely, ! function `bar' cannot inline function `foo'. ! Additionally inlining a function compiled with `-mstrict-align' into a ! function compiled without `-mstrict-align' is not allowed. However, ! inlining a function compiled without `-mstrict-align' into a function ! compiled with `-mstrict-align' is allowed. ! Note that CPU tuning options and attributes such as the `-mcpu=', ! `-mtune=' do not inhibit inlining unless the CPU specified by the ! `-mcpu=' option or the `cpu=' attribute conflicts with the ! architectural feature rules specified above.  File: gcc.info, Node: ARC Function Attributes, Next: ARM Function Attributes, Prev: AArch64 Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: ARC Function Attr *** 26906,26939 **** These function attributes are supported by the ARC back end: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! On the ARC, you must specify the kind of interrupt to be handled in ! a parameter to the interrupt attribute like this: void f () __attribute__ ((interrupt ("ilink1"))); ! Permissible values for this parameter are: 'ilink1' and 'ilink2'. ! 'long_call' ! 'medium_call' ! 'short_call' These attributes specify how a particular function is called. ! These attributes override the '-mlong-calls' and '-mmedium-calls' ! (*note ARC Options::) command-line switches and '#pragma long_calls' settings. ! For ARC, a function marked with the 'long_call' attribute is always ! called using register-indirect jump-and-link instructions, thereby ! enabling the called function to be placed anywhere within the ! 32-bit address space. A function marked with the 'medium_call' attribute will always be close enough to be called with an unconditional branch-and-link instruction, which has a 25-bit ! offset from the call site. A function marked with the 'short_call' attribute will always be close enough to be called with a conditional branch-and-link instruction, which has a 21-bit offset from the call site. --- 27094,27127 ---- These function attributes are supported by the ARC back end: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! On the ARC, you must specify the kind of interrupt to be handled ! in a parameter to the interrupt attribute like this: void f () __attribute__ ((interrupt ("ilink1"))); ! Permissible values for this parameter are: `ilink1' and `ilink2'. ! `long_call' ! `medium_call' ! `short_call' These attributes specify how a particular function is called. ! These attributes override the `-mlong-calls' and `-mmedium-calls' ! (*note ARC Options::) command-line switches and `#pragma long_calls' settings. ! For ARC, a function marked with the `long_call' attribute is ! always called using register-indirect jump-and-link instructions, ! thereby enabling the called function to be placed anywhere within ! the 32-bit address space. A function marked with the `medium_call' attribute will always be close enough to be called with an unconditional branch-and-link instruction, which has a 25-bit ! offset from the call site. A function marked with the `short_call' attribute will always be close enough to be called with a conditional branch-and-link instruction, which has a 21-bit offset from the call site. *************** File: gcc.info, Node: ARM Function Attr *** 26946,26952 **** These function attributes are supported for ARM targets: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 27134,27140 ---- These function attributes are supported for ARM targets: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** These function attributes are supported *** 26957,27032 **** void f () __attribute__ ((interrupt ("IRQ"))); ! Permissible values for this parameter are: 'IRQ', 'FIQ', 'SWI', ! 'ABORT' and 'UNDEF'. On ARMv7-M the interrupt type is ignored, and the attribute means the function may be called with a word-aligned stack pointer. ! 'isr' Use this attribute on ARM to write Interrupt Service Routines. ! This is an alias to the 'interrupt' attribute above. ! 'long_call' ! 'short_call' These attributes specify how a particular function is called. ! These attributes override the '-mlong-calls' (*note ARM Options::) ! command-line switch and '#pragma long_calls' settings. For ARM, ! the 'long_call' attribute indicates that the function might be far away from the call site and require a different (more expensive) ! calling sequence. The 'short_call' attribute always places the ! offset to the function from the call site into the 'BL' instruction ! directly. ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! 'pcs' ! ! The 'pcs' attribute can be used to control the calling convention ! used for a function on ARM. The attribute takes an argument that specifies the calling convention to use. When compiling using the AAPCS ABI (or a variant of it) then valid ! values for the argument are '"aapcs"' and '"aapcs-vfp"'. In order ! to use a variant other than '"aapcs"' then the compiler must be permitted to use the appropriate co-processor registers (i.e., the ! VFP registers must be available in order to use '"aapcs-vfp"'). For example, /* Argument passed in r0, and result returned in r0+r1. */ double f2d (float) __attribute__((pcs("aapcs"))); ! Variadic functions always use the '"aapcs"' calling convention and the compiler rejects attempts to specify an alternative. ! 'target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On ARM, the following options are allowed: ! 'thumb' ! Force code generation in the Thumb (T16/T32) ISA, depending on ! the architecture level. ! 'arm' Force code generation in the ARM (A32) ISA. Functions from different modes can be inlined in the caller's mode. ! 'fpu=' Specifies the fpu for which to tune the performance of this ! function. The behavior and permissible arguments are the same ! as for the '-mfpu=' command-line option.  File: gcc.info, Node: AVR Function Attributes, Next: Blackfin Function Attributes, Prev: ARM Function Attributes, Up: Function Attributes --- 27145,27221 ---- void f () __attribute__ ((interrupt ("IRQ"))); ! Permissible values for this parameter are: `IRQ', `FIQ', `SWI', ! `ABORT' and `UNDEF'. On ARMv7-M the interrupt type is ignored, and the attribute means the function may be called with a word-aligned stack pointer. ! `isr' Use this attribute on ARM to write Interrupt Service Routines. ! This is an alias to the `interrupt' attribute above. ! `long_call' ! `short_call' These attributes specify how a particular function is called. ! These attributes override the `-mlong-calls' (*note ARM Options::) ! command-line switch and `#pragma long_calls' settings. For ARM, ! the `long_call' attribute indicates that the function might be far away from the call site and require a different (more expensive) ! calling sequence. The `short_call' attribute always places the ! offset to the function from the call site into the `BL' ! instruction directly. ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! `pcs' ! The `pcs' attribute can be used to control the calling convention ! used for a function on ARM. The attribute takes an argument that specifies the calling convention to use. When compiling using the AAPCS ABI (or a variant of it) then valid ! values for the argument are `"aapcs"' and `"aapcs-vfp"'. In order ! to use a variant other than `"aapcs"' then the compiler must be permitted to use the appropriate co-processor registers (i.e., the ! VFP registers must be available in order to use `"aapcs-vfp"'). For example, /* Argument passed in r0, and result returned in r0+r1. */ double f2d (float) __attribute__((pcs("aapcs"))); ! Variadic functions always use the `"aapcs"' calling convention and the compiler rejects attempts to specify an alternative. ! `target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On ARM, the following options are allowed: ! `thumb' ! Force code generation in the Thumb (T16/T32) ISA, depending ! on the architecture level. ! `arm' Force code generation in the ARM (A32) ISA. Functions from different modes can be inlined in the caller's mode. ! `fpu=' Specifies the fpu for which to tune the performance of this ! function. The behavior and permissible arguments are the ! same as for the `-mfpu=' command-line option. ! !  File: gcc.info, Node: AVR Function Attributes, Next: Blackfin Function Attributes, Prev: ARM Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: AVR Function Attr *** 27036,27042 **** These function attributes are supported by the AVR back end: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 27225,27231 ---- These function attributes are supported by the AVR back end: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** These function attributes are supported *** 27044,27107 **** On the AVR, the hardware globally disables interrupts when an interrupt is executed. The first instruction of an interrupt ! handler declared with this attribute is a 'SEI' instruction to ! re-enable interrupts. See also the 'signal' function attribute ! that does not insert a 'SEI' instruction. If both 'signal' and ! 'interrupt' are specified for the same function, 'signal' is silently ignored. ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! 'OS_main' ! 'OS_task' ! On AVR, functions with the 'OS_main' or 'OS_task' attribute do not save/restore any call-saved register in their prologue/epilogue. ! The 'OS_main' attribute can be used when there _is guarantee_ that interrupts are disabled at the time when the function is entered. This saves resources when the stack pointer has to be changed to set up a frame for local variables. ! The 'OS_task' attribute can be used when there is _no guarantee_ that interrupts are disabled at that time when the function is ! entered like for, e.g. task functions in a multi-threading ! operating system. In that case, changing the stack pointer register is guarded by save/clear/restore of the global interrupt enable flag. ! The differences to the 'naked' function attribute are: ! * 'naked' functions do not have a return instruction whereas ! 'OS_main' and 'OS_task' functions have a 'RET' or 'RETI' return instruction. ! * 'naked' functions do not set up a frame for local variables or ! a frame pointer whereas 'OS_main' and 'OS_task' do this as needed. ! 'signal' Use this attribute on the AVR to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! See also the 'interrupt' function attribute. The AVR hardware globally disables interrupts when an interrupt is ! executed. Interrupt handler functions defined with the 'signal' attribute do not re-enable interrupts. It is save to enable ! interrupts in a 'signal' handler. This "save" only applies to the code generated by the compiler and not to the IRQ layout of the application which is responsibility of the application. ! If both 'signal' and 'interrupt' are specified for the same ! function, 'signal' is silently ignored.  File: gcc.info, Node: Blackfin Function Attributes, Next: CR16 Function Attributes, Prev: AVR Function Attributes, Up: Function Attributes --- 27233,27297 ---- On the AVR, the hardware globally disables interrupts when an interrupt is executed. The first instruction of an interrupt ! handler declared with this attribute is a `SEI' instruction to ! re-enable interrupts. See also the `signal' function attribute ! that does not insert a `SEI' instruction. If both `signal' and ! `interrupt' are specified for the same function, `signal' is silently ignored. ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! `OS_main' ! `OS_task' ! On AVR, functions with the `OS_main' or `OS_task' attribute do not save/restore any call-saved register in their prologue/epilogue. ! The `OS_main' attribute can be used when there _is guarantee_ that interrupts are disabled at the time when the function is entered. This saves resources when the stack pointer has to be changed to set up a frame for local variables. ! The `OS_task' attribute can be used when there is _no guarantee_ that interrupts are disabled at that time when the function is ! entered like for, e.g. task functions in a multi-threading ! operating system. In that case, changing the stack pointer register is guarded by save/clear/restore of the global interrupt enable flag. ! The differences to the `naked' function attribute are: ! * `naked' functions do not have a return instruction whereas ! `OS_main' and `OS_task' functions have a `RET' or `RETI' return instruction. ! ! * `naked' functions do not set up a frame for local variables ! or a frame pointer whereas `OS_main' and `OS_task' do this as needed. ! `signal' Use this attribute on the AVR to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! See also the `interrupt' function attribute. The AVR hardware globally disables interrupts when an interrupt is ! executed. Interrupt handler functions defined with the `signal' attribute do not re-enable interrupts. It is save to enable ! interrupts in a `signal' handler. This "save" only applies to the code generated by the compiler and not to the IRQ layout of the application which is responsibility of the application. ! If both `signal' and `interrupt' are specified for the same ! function, `signal' is silently ignored.  File: gcc.info, Node: Blackfin Function Attributes, Next: CR16 Function Attributes, Prev: AVR Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: Blackfin Function *** 27111,27164 **** These function attributes are supported by the Blackfin back end: ! 'exception_handler' Use this attribute on the Blackfin to indicate that the specified function is an exception handler. The compiler generates function entry and exit sequences suitable for use in an exception handler when this attribute is present. ! 'interrupt_handler' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! 'kspisusp' ! When used together with 'interrupt_handler', 'exception_handler' or ! 'nmi_handler', code is generated to load the stack pointer from the ! USP register in the function prologue. ! 'l1_text' This attribute specifies a function to be placed into L1 ! Instruction SRAM. The function is put into a specific section ! named '.l1.text'. With '-mfdpic', function calls with a such function as the callee or caller uses inlined PLT. ! 'l2' This attribute specifies a function to be placed into L2 SRAM. The ! function is put into a specific section named '.l2.text'. With ! '-mfdpic', callers of such functions use an inlined PLT. ! 'longcall' ! 'shortcall' ! The 'longcall' attribute indicates that the function might be far away from the call site and require a different (more expensive) ! calling sequence. The 'shortcall' attribute indicates that the ! function is always close enough for the shorter calling sequence to ! be used. These attributes override the '-mlongcall' switch. ! 'nesting' ! Use this attribute together with 'interrupt_handler', ! 'exception_handler' or 'nmi_handler' to indicate that the function entry code should enable nested interrupts or exceptions. ! 'nmi_handler' Use this attribute on the Blackfin to indicate that the specified function is an NMI handler. The compiler generates function entry and exit sequences suitable for use in an NMI handler when this attribute is present. ! 'saveall' Use this attribute to indicate that all registers except the stack pointer should be saved in the prologue regardless of whether they are used or not. --- 27301,27354 ---- These function attributes are supported by the Blackfin back end: ! `exception_handler' Use this attribute on the Blackfin to indicate that the specified function is an exception handler. The compiler generates function entry and exit sequences suitable for use in an exception handler when this attribute is present. ! `interrupt_handler' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! `kspisusp' ! When used together with `interrupt_handler', `exception_handler' ! or `nmi_handler', code is generated to load the stack pointer from ! the USP register in the function prologue. ! `l1_text' This attribute specifies a function to be placed into L1 ! Instruction SRAM. The function is put into a specific section ! named `.l1.text'. With `-mfdpic', function calls with a such function as the callee or caller uses inlined PLT. ! `l2' This attribute specifies a function to be placed into L2 SRAM. The ! function is put into a specific section named `.l2.text'. With ! `-mfdpic', callers of such functions use an inlined PLT. ! `longcall' ! `shortcall' ! The `longcall' attribute indicates that the function might be far away from the call site and require a different (more expensive) ! calling sequence. The `shortcall' attribute indicates that the ! function is always close enough for the shorter calling sequence ! to be used. These attributes override the `-mlongcall' switch. ! `nesting' ! Use this attribute together with `interrupt_handler', ! `exception_handler' or `nmi_handler' to indicate that the function entry code should enable nested interrupts or exceptions. ! `nmi_handler' Use this attribute on the Blackfin to indicate that the specified function is an NMI handler. The compiler generates function entry and exit sequences suitable for use in an NMI handler when this attribute is present. ! `saveall' Use this attribute to indicate that all registers except the stack pointer should be saved in the prologue regardless of whether they are used or not. *************** File: gcc.info, Node: CR16 Function Att *** 27171,27177 **** These function attributes are supported by the CR16 back end: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 27361,27367 ---- These function attributes are supported by the CR16 back end: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** File: gcc.info, Node: Epiphany Function *** 27185,27202 **** These function attributes are supported by the Epiphany back end: ! 'disinterrupt' This attribute causes the compiler to emit instructions to disable interrupts for the duration of the given function. ! 'forwarder_section' This attribute modifies the behavior of an interrupt handler. The ! interrupt handler may be in external memory which cannot be reached ! by a branch instruction, so generate a local memory trampoline to ! transfer control. The single parameter identifies the section ! where the trampoline is placed. ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 27375,27392 ---- These function attributes are supported by the Epiphany back end: ! `disinterrupt' This attribute causes the compiler to emit instructions to disable interrupts for the duration of the given function. ! `forwarder_section' This attribute modifies the behavior of an interrupt handler. The ! interrupt handler may be in external memory which cannot be ! reached by a branch instruction, so generate a local memory ! trampoline to transfer control. The single parameter identifies ! the section where the trampoline is placed. ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** These function attributes are supported *** 27208,27224 **** void __attribute__ ((interrupt ("dma0, dma1"))) universal_dma_handler (); ! Permissible values for these parameters are: 'reset', ! 'software_exception', 'page_miss', 'timer0', 'timer1', 'message', ! 'dma0', 'dma1', 'wand' and 'swi'. Multiple parameters indicate that multiple entries in the interrupt vector table should be ! initialized for this function, i.e. for each parameter NAME, a jump ! to the function is emitted in the section ivt_entry_NAME. The ! parameter(s) may be omitted entirely, in which case no interrupt ! vector table entry is provided. Note that interrupts are enabled inside the function unless the ! 'disinterrupt' attribute is also specified. The following examples are all valid uses of these attributes on Epiphany targets: --- 27398,27414 ---- void __attribute__ ((interrupt ("dma0, dma1"))) universal_dma_handler (); ! Permissible values for these parameters are: `reset', ! `software_exception', `page_miss', `timer0', `timer1', `message', ! `dma0', `dma1', `wand' and `swi'. Multiple parameters indicate that multiple entries in the interrupt vector table should be ! initialized for this function, i.e. for each parameter NAME, a ! jump to the function is emitted in the section ivt_entry_NAME. ! The parameter(s) may be omitted entirely, in which case no ! interrupt vector table entry is provided. Note that interrupts are enabled inside the function unless the ! `disinterrupt' attribute is also specified. The following examples are all valid uses of these attributes on Epiphany targets: *************** These function attributes are supported *** 27232,27242 **** forwarder_section ("tramp"))) external_dma_handler (); ! 'long_call' ! 'short_call' These attributes specify how a particular function is called. ! These attributes override the '-mlong-calls' (*note Adapteva ! Epiphany Options::) command-line switch and '#pragma long_calls' settings.  --- 27422,27432 ---- forwarder_section ("tramp"))) external_dma_handler (); ! `long_call' ! `short_call' These attributes specify how a particular function is called. ! These attributes override the `-mlong-calls' (*note Adapteva ! Epiphany Options::) command-line switch and `#pragma long_calls' settings.  *************** File: gcc.info, Node: H8/300 Function A *** 27247,27267 **** These function attributes are available for H8/300 targets: ! 'function_vector' ! Use this attribute on the H8/300, H8/300H, and H8S to indicate that ! the specified function should be called through the function vector. Calling a function through the function vector reduces ! code size; however, the function vector has a limited size (maximum ! 128 entries on the H8/300 and 64 entries on the H8/300H and H8S) ! and shares space with the interrupt vector. ! 'interrupt_handler' ! Use this attribute on the H8/300, H8/300H, and H8S to indicate that ! the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! 'saveall' Use this attribute on the H8/300, H8/300H, and H8S to indicate that all registers except the stack pointer should be saved in the prologue regardless of whether they are used or not. --- 27437,27457 ---- These function attributes are available for H8/300 targets: ! `function_vector' ! Use this attribute on the H8/300, H8/300H, and H8S to indicate ! that the specified function should be called through the function vector. Calling a function through the function vector reduces ! code size; however, the function vector has a limited size ! (maximum 128 entries on the H8/300 and 64 entries on the H8/300H ! and H8S) and shares space with the interrupt vector. ! `interrupt_handler' ! Use this attribute on the H8/300, H8/300H, and H8S to indicate ! that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! `saveall' Use this attribute on the H8/300, H8/300H, and H8S to indicate that all registers except the stack pointer should be saved in the prologue regardless of whether they are used or not. *************** File: gcc.info, Node: IA-64 Function At *** 27274,27287 **** These function attributes are supported on IA-64 targets: ! 'syscall_linkage' This attribute is used to modify the IA-64 calling convention by marking all input registers as live at all function exits. This makes it possible to restart a system call after an interrupt without having to save/restore the input registers. This also prevents kernel data from leaking into application code. ! 'version_id' This IA-64 HP-UX attribute, attached to a global variable or function, renames a symbol to contain a version string, thus allowing for function level versioning. HP-UX system header files --- 27464,27477 ---- These function attributes are supported on IA-64 targets: ! `syscall_linkage' This attribute is used to modify the IA-64 calling convention by marking all input registers as live at all function exits. This makes it possible to restart a system call after an interrupt without having to save/restore the input registers. This also prevents kernel data from leaking into application code. ! `version_id' This IA-64 HP-UX attribute, attached to a global variable or function, renames a symbol to contain a version string, thus allowing for function level versioning. HP-UX system header files *************** These function attributes are supported *** 27289,27295 **** extern int foo () __attribute__((version_id ("20040821"))); ! Calls to 'foo' are mapped to calls to 'foo{20040821}'.  File: gcc.info, Node: M32C Function Attributes, Next: M32R/D Function Attributes, Prev: IA-64 Function Attributes, Up: Function Attributes --- 27479,27485 ---- extern int foo () __attribute__((version_id ("20040821"))); ! Calls to `foo' are mapped to calls to `foo{20040821}'.  File: gcc.info, Node: M32C Function Attributes, Next: M32R/D Function Attributes, Prev: IA-64 Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: M32C Function Att *** 27299,27323 **** These function attributes are supported by the M32C back end: ! 'bank_switch' When added to an interrupt handler with the M32C port, causes the prologue and epilogue to use bank switching to preserve the registers rather than saving them on the stack. ! 'fast_interrupt' Use this attribute on the M32C port to indicate that the specified function is a fast interrupt handler. This is just like the ! 'interrupt' attribute, except that 'freit' is used to return ! instead of 'reit'. ! 'function_vector' ! On M16C/M32C targets, the 'function_vector' attribute declares a ! special page subroutine call function. Use of this attribute reduces the code size by 2 bytes for each call generated to the ! subroutine. The argument to the attribute is the vector number entry from the special page vector table which contains the 16 ! low-order bits of the subroutine's entry address. Each vector ! table has special page number (18 to 255) that is used in 'jsrs' instructions. Jump addresses of the routines are generated by adding 0x0F0000 (in case of M16C targets) or 0xFF0000 (in case of M32C targets), to the 2-byte addresses set in the vector table. --- 27489,27513 ---- These function attributes are supported by the M32C back end: ! `bank_switch' When added to an interrupt handler with the M32C port, causes the prologue and epilogue to use bank switching to preserve the registers rather than saving them on the stack. ! `fast_interrupt' Use this attribute on the M32C port to indicate that the specified function is a fast interrupt handler. This is just like the ! `interrupt' attribute, except that `freit' is used to return ! instead of `reit'. ! `function_vector' ! On M16C/M32C targets, the `function_vector' attribute declares a ! special page subroutine call function. Use of this attribute reduces the code size by 2 bytes for each call generated to the ! subroutine. The argument to the attribute is the vector number entry from the special page vector table which contains the 16 ! low-order bits of the subroutine's entry address. Each vector ! table has special page number (18 to 255) that is used in `jsrs' instructions. Jump addresses of the routines are generated by adding 0x0F0000 (in case of M16C targets) or 0xFF0000 (in case of M32C targets), to the 2-byte addresses set in the vector table. *************** These function attributes are supported *** 27326,27332 **** 0x0FFFFF (for M16C) and 0xFF0000 to 0xFFFFFF (for M32C). In the following example 2 bytes are saved for each call to ! function 'foo'. void foo (void) __attribute__((function_vector(0x18))); void foo (void) --- 27516,27522 ---- 0x0FFFFF (for M16C) and 0xFF0000 to 0xFFFFFF (for M32C). In the following example 2 bytes are saved for each call to ! function `foo'. void foo (void) __attribute__((function_vector(0x18))); void foo (void) *************** These function attributes are supported *** 27343,27349 **** This attribute is ignored for R8C target. ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 27533,27539 ---- This attribute is ignored for R8C target. ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** File: gcc.info, Node: M32R/D Function A *** 27357,27387 **** These function attributes are supported by the M32R/D back end: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! 'model (MODEL-NAME)' ! On the M32R/D, use this attribute to set the addressability of an object, and of the code generated for a function. The identifier ! MODEL-NAME is one of 'small', 'medium', or 'large', representing each of the code models. Small model objects live in the lower 16MB of memory (so that their ! addresses can be loaded with the 'ld24' instruction), and are ! callable with the 'bl' instruction. Medium model objects may live anywhere in the 32-bit address space ! (the compiler generates 'seth/add3' instructions to load their ! addresses), and are callable with the 'bl' instruction. Large model objects may live anywhere in the 32-bit address space ! (the compiler generates 'seth/add3' instructions to load their ! addresses), and may not be reachable with the 'bl' instruction (the ! compiler generates the much slower 'seth/add3/jl' instruction sequence).  --- 27547,27576 ---- These function attributes are supported by the M32R/D back end: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! `model (MODEL-NAME)' On the M32R/D, use this attribute to set the addressability of an object, and of the code generated for a function. The identifier ! MODEL-NAME is one of `small', `medium', or `large', representing each of the code models. Small model objects live in the lower 16MB of memory (so that their ! addresses can be loaded with the `ld24' instruction), and are ! callable with the `bl' instruction. Medium model objects may live anywhere in the 32-bit address space ! (the compiler generates `seth/add3' instructions to load their ! addresses), and are callable with the `bl' instruction. Large model objects may live anywhere in the 32-bit address space ! (the compiler generates `seth/add3' instructions to load their ! addresses), and may not be reachable with the `bl' instruction ! (the compiler generates the much slower `seth/add3/jl' instruction sequence).  *************** File: gcc.info, Node: m68k Function Att *** 27392,27410 **** These function attributes are supported by the m68k back end: ! 'interrupt' ! 'interrupt_handler' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. Either name may be used. ! 'interrupt_thread' Use this attribute on fido, a subarchitecture of the m68k, to indicate that the specified function is an interrupt handler that is designed to run as a thread. The compiler omits generate prologue/epilogue sequences and replaces the return instruction ! with a 'sleep' instruction. This attribute is available only on fido.  --- 27581,27599 ---- These function attributes are supported by the m68k back end: ! `interrupt' ! `interrupt_handler' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. Either name may be used. ! `interrupt_thread' Use this attribute on fido, a subarchitecture of the m68k, to indicate that the specified function is an interrupt handler that is designed to run as a thread. The compiler omits generate prologue/epilogue sequences and replaces the return instruction ! with a `sleep' instruction. This attribute is available only on fido.  *************** File: gcc.info, Node: MCORE Function At *** 27415,27428 **** These function attributes are supported by the MCORE back end: ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported.  --- 27604,27617 ---- These function attributes are supported by the MCORE back end: ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported.  *************** File: gcc.info, Node: MeP Function Attr *** 27433,27461 **** These function attributes are supported by the MeP back end: ! 'disinterrupt' On MeP targets, this attribute causes the compiler to emit instructions to disable interrupts for the duration of the given function. ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! 'near' ! This attribute causes the compiler to assume the called function is ! close enough to use the normal calling convention, overriding the ! '-mtf' command-line option. ! 'far' On MeP targets this causes the compiler to use a calling convention that assumes the called function is too far away for the built-in addressing modes. ! 'vliw' ! The 'vliw' attribute tells the compiler to emit instructions in VLIW mode instead of core mode. Note that this attribute is not allowed unless a VLIW coprocessor has been configured and enabled through command-line options. --- 27622,27650 ---- These function attributes are supported by the MeP back end: ! `disinterrupt' On MeP targets, this attribute causes the compiler to emit instructions to disable interrupts for the duration of the given function. ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! `near' ! This attribute causes the compiler to assume the called function ! is close enough to use the normal calling convention, overriding ! the `-mtf' command-line option. ! `far' On MeP targets this causes the compiler to use a calling convention that assumes the called function is too far away for the built-in addressing modes. ! `vliw' ! The `vliw' attribute tells the compiler to emit instructions in VLIW mode instead of core mode. Note that this attribute is not allowed unless a VLIW coprocessor has been configured and enabled through command-line options. *************** File: gcc.info, Node: MicroBlaze Functi *** 27468,27474 **** These function attributes are supported on MicroBlaze targets: ! 'save_volatiles' Use this attribute to indicate that the function is an interrupt handler. All volatile registers (in addition to non-volatile registers) are saved in the function prologue. If the function is --- 27657,27663 ---- These function attributes are supported on MicroBlaze targets: ! `save_volatiles' Use this attribute to indicate that the function is an interrupt handler. All volatile registers (in addition to non-volatile registers) are saved in the function prologue. If the function is *************** These function attributes are supported *** 27476,27498 **** normal function return is generated instead of a return from interrupt. ! 'break_handler' Use this attribute to indicate that the specified function is a break handler. The compiler generates function entry and exit sequences suitable for use in an break handler when this attribute ! is present. The return from 'break_handler' is done through the ! 'rtbd' instead of 'rtsd'. void f () __attribute__ ((break_handler)); ! 'interrupt_handler' ! 'fast_interrupt' These attributes indicate that the specified function is an ! interrupt handler. Use the 'fast_interrupt' attribute to indicate handlers used in low-latency interrupt mode, and ! 'interrupt_handler' for interrupts that do not use low-latency handlers. In both cases, GCC emits appropriate prologue code and ! generates a return from the handler using 'rtid' instead of 'rtsd'.  File: gcc.info, Node: Microsoft Windows Function Attributes, Next: MIPS Function Attributes, Prev: MicroBlaze Function Attributes, Up: Function Attributes --- 27665,27687 ---- normal function return is generated instead of a return from interrupt. ! `break_handler' Use this attribute to indicate that the specified function is a break handler. The compiler generates function entry and exit sequences suitable for use in an break handler when this attribute ! is present. The return from `break_handler' is done through the ! `rtbd' instead of `rtsd'. void f () __attribute__ ((break_handler)); ! `interrupt_handler' ! `fast_interrupt' These attributes indicate that the specified function is an ! interrupt handler. Use the `fast_interrupt' attribute to indicate handlers used in low-latency interrupt mode, and ! `interrupt_handler' for interrupts that do not use low-latency handlers. In both cases, GCC emits appropriate prologue code and ! generates a return from the handler using `rtid' instead of `rtsd'.  File: gcc.info, Node: Microsoft Windows Function Attributes, Next: MIPS Function Attributes, Prev: MicroBlaze Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: Microsoft Windows *** 27503,27527 **** The following attributes are available on Microsoft Windows and Symbian OS targets. ! 'dllexport' ! On Microsoft Windows targets and Symbian OS targets the 'dllexport' ! attribute causes the compiler to provide a global pointer to a ! pointer in a DLL, so that it can be referenced with the 'dllimport' ! attribute. On Microsoft Windows targets, the pointer name is ! formed by combining '_imp__' and the function or variable name. ! You can use '__declspec(dllexport)' as a synonym for '__attribute__ ! ((dllexport))' for compatibility with other compilers. ! On systems that support the 'visibility' attribute, this attribute also implies "default" visibility. It is an error to explicitly specify any other visibility. GCC's default behavior is to emit all inline functions with the ! 'dllexport' attribute. Since this can cause object file-size ! bloat, you can use '-fno-keep-inline-dllexport', which tells GCC to ignore the attribute for inlined functions unless the ! '-fkeep-inline-functions' flag is used instead. The attribute is ignored for undefined symbols. --- 27692,27718 ---- The following attributes are available on Microsoft Windows and Symbian OS targets. ! `dllexport' ! On Microsoft Windows targets and Symbian OS targets the ! `dllexport' attribute causes the compiler to provide a global ! pointer to a pointer in a DLL, so that it can be referenced with ! the `dllimport' attribute. On Microsoft Windows targets, the ! pointer name is formed by combining `_imp__' and the function or ! variable name. ! You can use `__declspec(dllexport)' as a synonym for ! `__attribute__ ((dllexport))' for compatibility with other ! compilers. ! On systems that support the `visibility' attribute, this attribute also implies "default" visibility. It is an error to explicitly specify any other visibility. GCC's default behavior is to emit all inline functions with the ! `dllexport' attribute. Since this can cause object file-size ! bloat, you can use `-fno-keep-inline-dllexport', which tells GCC to ignore the attribute for inlined functions unless the ! `-fkeep-inline-functions' flag is used instead. The attribute is ignored for undefined symbols. *************** OS targets. *** 27532,27590 **** For Microsoft Windows targets there are alternative methods for including the symbol in the DLL's export table such as using a ! '.def' file with an 'EXPORTS' section or, with GNU ld, using the ! '--export-all' linker flag. ! 'dllimport' ! On Microsoft Windows and Symbian OS targets, the 'dllimport' attribute causes the compiler to reference a function or variable via a global pointer to a pointer that is set up by the DLL ! exporting the symbol. The attribute implies 'extern'. On Microsoft Windows targets, the pointer name is formed by combining ! '_imp__' and the function or variable name. ! You can use '__declspec(dllimport)' as a synonym for '__attribute__ ! ((dllimport))' for compatibility with other compilers. ! On systems that support the 'visibility' attribute, this attribute also implies "default" visibility. It is an error to explicitly specify any other visibility. Currently, the attribute is ignored for inlined functions. If the attribute is applied to a symbol _definition_, an error is ! reported. If a symbol previously declared 'dllimport' is later defined, the attribute is ignored in subsequent references, and a warning is emitted. The attribute is also overridden by a ! subsequent declaration as 'dllexport'. ! When applied to C++ classes, the attribute marks non-inlined member ! functions and static data members as imports. However, the attribute is ignored for virtual methods to allow creation of vtables using thunks. ! On the SH Symbian OS target the 'dllimport' attribute also has another affect--it can cause the vtable and run-time type information for a class to be exported. This happens when the class has a dllimported constructor or a non-inline, non-pure ! virtual function and, for either of those two conditions, the class ! also has an inline constructor or destructor and has a key function ! that is defined in the current translation unit. ! For Microsoft Windows targets the use of the 'dllimport' attribute on functions is not necessary, but provides a small performance benefit by eliminating a thunk in the DLL. The use of the ! 'dllimport' attribute on imported variables can be avoided by ! passing the '--enable-auto-import' switch to the GNU linker. As with functions, using the attribute for a variable eliminates a thunk in the DLL. One drawback to using this attribute is that a pointer to a ! _variable_ marked as 'dllimport' cannot be used as a constant ! address. However, a pointer to a _function_ with the 'dllimport' attribute can be used as a constant initializer; in this case, the address of a stub function in the import lib is referenced. On Microsoft Windows targets, the attribute can be disabled for ! functions by setting the '-mnop-fun-dllimport' flag.  File: gcc.info, Node: MIPS Function Attributes, Next: MSP430 Function Attributes, Prev: Microsoft Windows Function Attributes, Up: Function Attributes --- 27723,27782 ---- For Microsoft Windows targets there are alternative methods for including the symbol in the DLL's export table such as using a ! `.def' file with an `EXPORTS' section or, with GNU ld, using the ! `--export-all' linker flag. ! `dllimport' ! On Microsoft Windows and Symbian OS targets, the `dllimport' attribute causes the compiler to reference a function or variable via a global pointer to a pointer that is set up by the DLL ! exporting the symbol. The attribute implies `extern'. On Microsoft Windows targets, the pointer name is formed by combining ! `_imp__' and the function or variable name. ! You can use `__declspec(dllimport)' as a synonym for ! `__attribute__ ((dllimport))' for compatibility with other ! compilers. ! On systems that support the `visibility' attribute, this attribute also implies "default" visibility. It is an error to explicitly specify any other visibility. Currently, the attribute is ignored for inlined functions. If the attribute is applied to a symbol _definition_, an error is ! reported. If a symbol previously declared `dllimport' is later defined, the attribute is ignored in subsequent references, and a warning is emitted. The attribute is also overridden by a ! subsequent declaration as `dllexport'. ! When applied to C++ classes, the attribute marks non-inlined ! member functions and static data members as imports. However, the attribute is ignored for virtual methods to allow creation of vtables using thunks. ! On the SH Symbian OS target the `dllimport' attribute also has another affect--it can cause the vtable and run-time type information for a class to be exported. This happens when the class has a dllimported constructor or a non-inline, non-pure ! virtual function and, for either of those two conditions, the ! class also has an inline constructor or destructor and has a key ! function that is defined in the current translation unit. ! For Microsoft Windows targets the use of the `dllimport' attribute on functions is not necessary, but provides a small performance benefit by eliminating a thunk in the DLL. The use of the ! `dllimport' attribute on imported variables can be avoided by ! passing the `--enable-auto-import' switch to the GNU linker. As with functions, using the attribute for a variable eliminates a thunk in the DLL. One drawback to using this attribute is that a pointer to a ! _variable_ marked as `dllimport' cannot be used as a constant ! address. However, a pointer to a _function_ with the `dllimport' attribute can be used as a constant initializer; in this case, the address of a stub function in the import lib is referenced. On Microsoft Windows targets, the attribute can be disabled for ! functions by setting the `-mnop-fun-dllimport' flag.  File: gcc.info, Node: MIPS Function Attributes, Next: MSP430 Function Attributes, Prev: Microsoft Windows Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: MIPS Function Att *** 27594,27600 **** These function attributes are supported by the MIPS back end: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 27786,27792 ---- These function attributes are supported by the MIPS back end: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** These function attributes are supported *** 27602,27632 **** interrupt attribute which allows the interrupt mode to be described. By default GCC assumes the external interrupt controller (EIC) mode is in use, this can be explicitly set using ! 'eic'. When interrupts are non-masked then the requested Interrupt Priority Level (IPL) is copied to the current IPL which has the effect of only enabling higher priority interrupts. To use vectored interrupt mode use the argument ! 'vector=[sw0|sw1|hw0|hw1|hw2|hw3|hw4|hw5]', this will change the behavior of the non-masked interrupt support and GCC will arrange to mask all interrupts from sw0 up to and including the specified interrupt vector. You can use the following attributes to modify the behavior of an interrupt handler: ! 'use_shadow_register_set' Assume that the handler uses a shadow register set, instead of the main general-purpose registers. An optional argument ! 'intstack' is supported to indicate that the shadow register set contains a valid stack pointer. ! 'keep_interrupts_masked' Keep interrupts masked for the whole function. Without this ! attribute, GCC tries to reenable interrupts for as much of the ! function as it can. ! 'use_debug_exception_return' ! Return using the 'deret' instruction. Interrupt handlers that ! don't have this attribute return using 'eret' instead. You can use any combination of these attributes, as shown below: void __attribute__ ((interrupt)) v0 (); --- 27794,27824 ---- interrupt attribute which allows the interrupt mode to be described. By default GCC assumes the external interrupt controller (EIC) mode is in use, this can be explicitly set using ! `eic'. When interrupts are non-masked then the requested Interrupt Priority Level (IPL) is copied to the current IPL which has the effect of only enabling higher priority interrupts. To use vectored interrupt mode use the argument ! `vector=[sw0|sw1|hw0|hw1|hw2|hw3|hw4|hw5]', this will change the behavior of the non-masked interrupt support and GCC will arrange to mask all interrupts from sw0 up to and including the specified interrupt vector. You can use the following attributes to modify the behavior of an interrupt handler: ! `use_shadow_register_set' Assume that the handler uses a shadow register set, instead of the main general-purpose registers. An optional argument ! `intstack' is supported to indicate that the shadow register set contains a valid stack pointer. ! `keep_interrupts_masked' Keep interrupts masked for the whole function. Without this ! attribute, GCC tries to reenable interrupts for as much of ! the function as it can. ! `use_debug_exception_return' ! Return using the `deret' instruction. Interrupt handlers ! that don't have this attribute return using `eret' instead. You can use any combination of these attributes, as shown below: void __attribute__ ((interrupt)) v0 (); *************** These function attributes are supported *** 27645,27700 **** void __attribute__ ((interrupt("eic"))) v8 (); void __attribute__ ((interrupt("vector=hw3"))) v9 (); ! 'long_call' ! 'near' ! 'far' These attributes specify how a particular function is called on ! MIPS. The attributes override the '-mlong-calls' (*note MIPS ! Options::) command-line switch. The 'long_call' and 'far' attributes are synonyms, and cause the compiler to always call the function by first loading its address into a register, and then ! using the contents of that register. The 'near' attribute has the opposite effect; it specifies that non-PIC calls should be made ! using the more efficient 'jal' instruction. ! ! 'mips16' ! 'nomips16' ! On MIPS targets, you can use the 'mips16' and 'nomips16' function ! attributes to locally select or turn off MIPS16 code generation. A ! function with the 'mips16' attribute is emitted as MIPS16 code, while MIPS16 code generation is disabled for functions with the ! 'nomips16' attribute. These attributes override the '-mips16' and ! '-mno-mips16' options on the command line (*note MIPS Options::). When compiling files containing mixed MIPS16 and non-MIPS16 code, ! the preprocessor symbol '__mips16' reflects the setting on the command line, not that within individual functions. Mixed MIPS16 and non-MIPS16 code may interact badly with some GCC extensions ! such as '__builtin_apply' (*note Constructing Calls::). ! ! 'micromips, MIPS' ! 'nomicromips, MIPS' ! On MIPS targets, you can use the 'micromips' and 'nomicromips' function attributes to locally select or turn off microMIPS code ! generation. A function with the 'micromips' attribute is emitted as microMIPS code, while microMIPS code generation is disabled for ! functions with the 'nomicromips' attribute. These attributes ! override the '-mmicromips' and '-mno-micromips' options on the command line (*note MIPS Options::). When compiling files containing mixed microMIPS and non-microMIPS ! code, the preprocessor symbol '__mips_micromips' reflects the setting on the command line, not that within individual functions. ! Mixed microMIPS and non-microMIPS code may interact badly with some ! GCC extensions such as '__builtin_apply' (*note Constructing Calls::). ! 'nocompression' ! On MIPS targets, you can use the 'nocompression' function attribute to locally turn off MIPS16 and microMIPS code generation. This ! attribute overrides the '-mips16' and '-mmicromips' options on the command line (*note MIPS Options::).  --- 27837,27890 ---- void __attribute__ ((interrupt("eic"))) v8 (); void __attribute__ ((interrupt("vector=hw3"))) v9 (); ! `long_call' ! `near' ! `far' These attributes specify how a particular function is called on ! MIPS. The attributes override the `-mlong-calls' (*note MIPS ! Options::) command-line switch. The `long_call' and `far' attributes are synonyms, and cause the compiler to always call the function by first loading its address into a register, and then ! using the contents of that register. The `near' attribute has the opposite effect; it specifies that non-PIC calls should be made ! using the more efficient `jal' instruction. ! `mips16' ! `nomips16' ! On MIPS targets, you can use the `mips16' and `nomips16' function ! attributes to locally select or turn off MIPS16 code generation. ! A function with the `mips16' attribute is emitted as MIPS16 code, while MIPS16 code generation is disabled for functions with the ! `nomips16' attribute. These attributes override the `-mips16' and ! `-mno-mips16' options on the command line (*note MIPS Options::). When compiling files containing mixed MIPS16 and non-MIPS16 code, ! the preprocessor symbol `__mips16' reflects the setting on the command line, not that within individual functions. Mixed MIPS16 and non-MIPS16 code may interact badly with some GCC extensions ! such as `__builtin_apply' (*note Constructing Calls::). ! `micromips, MIPS' ! `nomicromips, MIPS' ! On MIPS targets, you can use the `micromips' and `nomicromips' function attributes to locally select or turn off microMIPS code ! generation. A function with the `micromips' attribute is emitted as microMIPS code, while microMIPS code generation is disabled for ! functions with the `nomicromips' attribute. These attributes ! override the `-mmicromips' and `-mno-micromips' options on the command line (*note MIPS Options::). When compiling files containing mixed microMIPS and non-microMIPS ! code, the preprocessor symbol `__mips_micromips' reflects the setting on the command line, not that within individual functions. ! Mixed microMIPS and non-microMIPS code may interact badly with ! some GCC extensions such as `__builtin_apply' (*note Constructing Calls::). ! `nocompression' ! On MIPS targets, you can use the `nocompression' function attribute to locally turn off MIPS16 and microMIPS code generation. This ! attribute overrides the `-mips16' and `-mmicromips' options on the command line (*note MIPS Options::).  *************** File: gcc.info, Node: MSP430 Function A *** 27705,27717 **** These function attributes are supported by the MSP430 back end: ! 'critical' Critical functions disable interrupts upon entry and restore the previous interrupt state upon exit. Critical functions cannot also ! have the 'naked' or 'reentrant' attributes. They can have the ! 'interrupt' attribute. ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 27895,27907 ---- These function attributes are supported by the MSP430 back end: ! `critical' Critical functions disable interrupts upon entry and restore the previous interrupt state upon exit. Critical functions cannot also ! have the `naked' or `reentrant' attributes. They can have the ! `interrupt' attribute. ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** These function attributes are supported *** 27723,27755 **** this handler should be assigned. If the argument is a name it is treated as a symbolic name for the vector slot. These names should match up with appropriate entries in the linker script. By default ! the names 'watchdog' for vector 26, 'nmi' for vector 30 and 'reset' ! for vector 31 are recognized. ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! 'reentrant' Reentrant functions disable interrupts upon entry and enable them ! upon exit. Reentrant functions cannot also have the 'naked' or ! 'critical' attributes. They can have the 'interrupt' attribute. ! 'wakeup' This attribute only applies to interrupt functions. It is silently ignored if applied to a non-interrupt function. A wakeup interrupt function will rouse the processor from any low-power state that it might be in when the function exits. ! 'lower' ! 'upper' ! 'either' On the MSP430 target these attributes can be used to specify whether the function or variable should be placed into low memory, high memory, or the placement should be left to the linker to --- 27913,27945 ---- this handler should be assigned. If the argument is a name it is treated as a symbolic name for the vector slot. These names should match up with appropriate entries in the linker script. By default ! the names `watchdog' for vector 26, `nmi' for vector 30 and ! `reset' for vector 31 are recognized. ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! `reentrant' Reentrant functions disable interrupts upon entry and enable them ! upon exit. Reentrant functions cannot also have the `naked' or ! `critical' attributes. They can have the `interrupt' attribute. ! `wakeup' This attribute only applies to interrupt functions. It is silently ignored if applied to a non-interrupt function. A wakeup interrupt function will rouse the processor from any low-power state that it might be in when the function exits. ! `lower' ! `upper' ! `either' On the MSP430 target these attributes can be used to specify whether the function or variable should be placed into low memory, high memory, or the placement should be left to the linker to *************** These function attributes are supported *** 27757,27780 **** MSP430X architecture. The attributes work in conjunction with a linker script that has ! been augmented to specify where to place sections with a '.lower' ! and a '.upper' prefix. So, for example, as well as placing the ! '.data' section, the script also specifies the placement of a ! '.lower.data' and a '.upper.data' section. The intention is that ! 'lower' sections are placed into a small but easier to access memory region and the upper sections are placed into a larger, but slower to access, region. ! The 'either' attribute is special. It tells the linker to place ! the object into the corresponding 'lower' section if there is room for it. If there is insufficient room then the object is placed ! into the corresponding 'upper' section instead. Note that the ! placement algorithm is not very sophisticated. It does not attempt ! to find an optimal packing of the 'lower' sections. It just makes ! one pass over the objects and does the best that it can. Using the ! '-ffunction-sections' and '-fdata-sections' command-line options ! can help the packing, however, since they produce smaller, easier ! to pack regions.  File: gcc.info, Node: NDS32 Function Attributes, Next: Nios II Function Attributes, Prev: MSP430 Function Attributes, Up: Function Attributes --- 27947,27970 ---- MSP430X architecture. The attributes work in conjunction with a linker script that has ! been augmented to specify where to place sections with a `.lower' ! and a `.upper' prefix. So, for example, as well as placing the ! `.data' section, the script also specifies the placement of a ! `.lower.data' and a `.upper.data' section. The intention is that ! `lower' sections are placed into a small but easier to access memory region and the upper sections are placed into a larger, but slower to access, region. ! The `either' attribute is special. It tells the linker to place ! the object into the corresponding `lower' section if there is room for it. If there is insufficient room then the object is placed ! into the corresponding `upper' section instead. Note that the ! placement algorithm is not very sophisticated. It does not ! attempt to find an optimal packing of the `lower' sections. It ! just makes one pass over the objects and does the best that it ! can. Using the `-ffunction-sections' and `-fdata-sections' ! command-line options can help the packing, however, since they ! produce smaller, easier to pack regions.  File: gcc.info, Node: NDS32 Function Attributes, Next: Nios II Function Attributes, Prev: MSP430 Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: NDS32 Function At *** 27784,27833 **** These function attributes are supported by the NDS32 back end: ! 'exception' Use this attribute on the NDS32 target to indicate that the specified function is an exception handler. The compiler will generate corresponding sections for use in an exception handler. ! 'interrupt' On NDS32 target, this attribute indicates that the specified function is an interrupt handler. The compiler generates corresponding sections for use in an interrupt handler. You can use the following attributes to modify the behavior: ! 'nested' This interrupt service routine is interruptible. ! 'not_nested' This interrupt service routine is not interruptible. ! 'nested_ready' This interrupt service routine is interruptible after ! 'PSW.GIE' (global interrupt enable) is set. This allows interrupt service routine to finish some short critical code before enabling interrupts. ! 'save_all' The system will help save all registers into stack before entering interrupt handler. ! 'partial_save' The system will help save caller registers into stack before entering interrupt handler. ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! 'reset' Use this attribute on the NDS32 target to indicate that the specified function is a reset handler. The compiler will generate ! corresponding sections for use in a reset handler. You can use the ! following attributes to provide extra exception handling: ! 'nmi' Provide a user-defined function to handle NMI exception. ! 'warm' Provide a user-defined function to handle warm reset exception. --- 27974,28028 ---- These function attributes are supported by the NDS32 back end: ! `exception' Use this attribute on the NDS32 target to indicate that the specified function is an exception handler. The compiler will generate corresponding sections for use in an exception handler. ! `interrupt' On NDS32 target, this attribute indicates that the specified function is an interrupt handler. The compiler generates corresponding sections for use in an interrupt handler. You can use the following attributes to modify the behavior: ! `nested' This interrupt service routine is interruptible. ! ! `not_nested' This interrupt service routine is not interruptible. ! ! `nested_ready' This interrupt service routine is interruptible after ! `PSW.GIE' (global interrupt enable) is set. This allows interrupt service routine to finish some short critical code before enabling interrupts. ! ! `save_all' The system will help save all registers into stack before entering interrupt handler. ! ! `partial_save' The system will help save caller registers into stack before entering interrupt handler. ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! `reset' Use this attribute on the NDS32 target to indicate that the specified function is a reset handler. The compiler will generate ! corresponding sections for use in a reset handler. You can use ! the following attributes to provide extra exception handling: ! `nmi' Provide a user-defined function to handle NMI exception. ! ! `warm' Provide a user-defined function to handle warm reset exception. *************** File: gcc.info, Node: Nios II Function *** 27839,27862 **** These function attributes are supported by the Nios II back end: ! 'target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. When compiling for Nios II, the following options are allowed: ! 'custom-INSN=N' ! 'no-custom-INSN' ! Each 'custom-INSN=N' attribute locally enables use of a custom ! instruction with encoding N when generating code that uses ! INSN. Similarly, 'no-custom-INSN' locally inhibits use of the ! custom instruction INSN. These target attributes correspond ! to the '-mcustom-INSN=N' and '-mno-custom-INSN' command-line ! options, and support the same set of INSN keywords. *Note ! Nios II Options::, for more information. ! 'custom-fpu-cfg=NAME' ! This attribute corresponds to the '-mcustom-fpu-cfg=NAME' command-line option, to select a predefined set of custom instructions named NAME. *Note Nios II Options::, for more information. --- 28034,28057 ---- These function attributes are supported by the Nios II back end: ! `target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. When compiling for Nios II, the following options are allowed: ! `custom-INSN=N' ! `no-custom-INSN' ! Each `custom-INSN=N' attribute locally enables use of a ! custom instruction with encoding N when generating code that ! uses INSN. Similarly, `no-custom-INSN' locally inhibits use ! of the custom instruction INSN. These target attributes ! correspond to the `-mcustom-INSN=N' and `-mno-custom-INSN' ! command-line options, and support the same set of INSN ! keywords. *Note Nios II Options::, for more information. ! `custom-fpu-cfg=NAME' ! This attribute corresponds to the `-mcustom-fpu-cfg=NAME' command-line option, to select a predefined set of custom instructions named NAME. *Note Nios II Options::, for more information. *************** File: gcc.info, Node: Nvidia PTX Functi *** 27869,27881 **** These function attributes are supported by the Nvidia PTX back end: ! 'kernel' This attribute indicates that the corresponding function should be compiled as a kernel function, which can be invoked from the host via the CUDA RT library. By default functions are only callable only from other PTX functions. ! Kernel functions must have 'void' return type.  File: gcc.info, Node: PowerPC Function Attributes, Next: RL78 Function Attributes, Prev: Nvidia PTX Function Attributes, Up: Function Attributes --- 28064,28076 ---- These function attributes are supported by the Nvidia PTX back end: ! `kernel' This attribute indicates that the corresponding function should be compiled as a kernel function, which can be invoked from the host via the CUDA RT library. By default functions are only callable only from other PTX functions. ! Kernel functions must have `void' return type.  File: gcc.info, Node: PowerPC Function Attributes, Next: RL78 Function Attributes, Prev: Nvidia PTX Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: PowerPC Function *** 27885,28058 **** These function attributes are supported by the PowerPC back end: ! 'longcall' ! 'shortcall' ! The 'longcall' attribute indicates that the function might be far away from the call site and require a different (more expensive) ! calling sequence. The 'shortcall' attribute indicates that the ! function is always close enough for the shorter calling sequence to ! be used. These attributes override both the '-mlongcall' switch ! and the '#pragma longcall' setting. *Note RS/6000 and PowerPC Options::, for more information on whether long calls are necessary. ! 'target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On the PowerPC, the following options are allowed: ! 'altivec' ! 'no-altivec' Generate code that uses (does not use) AltiVec instructions. In 32-bit code, you cannot enable AltiVec instructions unless ! '-mabi=altivec' is used on the command line. ! 'cmpb' ! 'no-cmpb' Generate code that uses (does not use) the compare bytes instruction implemented on the POWER6 processor and other processors that support the PowerPC V2.05 architecture. ! 'dlmzb' ! 'no-dlmzb' Generate code that uses (does not use) the string-search ! 'dlmzb' instruction on the IBM 405, 440, 464 and 476 processors. This instruction is generated by default when targeting those processors. ! 'fprnd' ! 'no-fprnd' Generate code that uses (does not use) the FP round to integer instructions implemented on the POWER5+ processor and other processors that support the PowerPC V2.03 architecture. ! 'hard-dfp' ! 'no-hard-dfp' Generate code that uses (does not use) the decimal floating-point instructions implemented on some POWER processors. ! 'isel' ! 'no-isel' Generate code that uses (does not use) ISEL instruction. ! 'mfcrf' ! 'no-mfcrf' Generate code that uses (does not use) the move from condition ! register field instruction implemented on the POWER4 processor ! and other processors that support the PowerPC V2.01 architecture. ! 'mfpgpr' ! 'no-mfpgpr' Generate code that uses (does not use) the FP move to/from general purpose register instructions implemented on the POWER6X processor and other processors that support the extended PowerPC V2.05 architecture. ! 'mulhw' ! 'no-mulhw' Generate code that uses (does not use) the half-word multiply and multiply-accumulate instructions on the IBM 405, 440, 464 and 476 processors. These instructions are generated by default when targeting those processors. ! 'multiple' ! 'no-multiple' Generate code that uses (does not use) the load multiple word instructions and the store multiple word instructions. ! 'update' ! 'no-update' Generate code that uses (does not use) the load or store instructions that update the base register to the address of the calculated memory location. ! 'popcntb' ! 'no-popcntb' Generate code that uses (does not use) the popcount and double-precision FP reciprocal estimate instruction implemented on the POWER5 processor and other processors that support the PowerPC V2.02 architecture. ! 'popcntd' ! 'no-popcntd' Generate code that uses (does not use) the popcount instruction implemented on the POWER7 processor and other processors that support the PowerPC V2.06 architecture. ! 'powerpc-gfxopt' ! 'no-powerpc-gfxopt' Generate code that uses (does not use) the optional PowerPC architecture instructions in the Graphics group, including floating-point select. ! 'powerpc-gpopt' ! 'no-powerpc-gpopt' Generate code that uses (does not use) the optional PowerPC architecture instructions in the General Purpose group, including floating-point square root. ! 'recip-precision' ! 'no-recip-precision' Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ABI. ! 'string' ! 'no-string' Generate code that uses (does not use) the load string instructions and the store string word instructions to save multiple registers and do small block moves. ! 'vsx' ! 'no-vsx' Generate code that uses (does not use) vector/scalar (VSX) instructions, and also enable the use of built-in functions that allow more direct access to the VSX instruction set. In 32-bit code, you cannot enable VSX or AltiVec instructions ! unless '-mabi=altivec' is used on the command line. ! 'friz' ! 'no-friz' ! Generate (do not generate) the 'friz' instruction when the ! '-funsafe-math-optimizations' option is used to optimize rounding a floating-point value to 64-bit integer and back to ! floating point. The 'friz' instruction does not return the ! same value if the floating-point number is too large to fit in ! an integer. ! 'avoid-indexed-addresses' ! 'no-avoid-indexed-addresses' Generate code that tries to avoid (not avoid) the use of indexed load or store instructions. ! 'paired' ! 'no-paired' Generate code that uses (does not use) the generation of PAIRED simd instructions. ! 'longcall' ! 'no-longcall' Generate code that assumes (does not assume) that all calls are far away so that a longer more expensive calling sequence is required. ! 'cpu=CPU' Specify the architecture to generate code for when compiling ! the function. If you select the 'target("cpu=power7")' attribute when generating 32-bit code, VSX and AltiVec instructions are not generated unless you use the ! '-mabi=altivec' option on the command line. ! 'tune=TUNE' Specify the architecture to tune for when compiling the ! function. If you do not specify the 'target("tune=TUNE")' ! attribute and you do specify the 'target("cpu=CPU")' ! attribute, compilation tunes for the CPU architecture, and not ! the default tuning specified on the command line. On the PowerPC, the inliner does not inline a function that has different target options than the caller, unless the callee has a --- 28080,28253 ---- These function attributes are supported by the PowerPC back end: ! `longcall' ! `shortcall' ! The `longcall' attribute indicates that the function might be far away from the call site and require a different (more expensive) ! calling sequence. The `shortcall' attribute indicates that the ! function is always close enough for the shorter calling sequence ! to be used. These attributes override both the `-mlongcall' ! switch and the `#pragma longcall' setting. *Note RS/6000 and PowerPC Options::, for more information on whether long calls are necessary. ! `target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On the PowerPC, the following options are allowed: ! `altivec' ! `no-altivec' Generate code that uses (does not use) AltiVec instructions. In 32-bit code, you cannot enable AltiVec instructions unless ! `-mabi=altivec' is used on the command line. ! `cmpb' ! `no-cmpb' Generate code that uses (does not use) the compare bytes instruction implemented on the POWER6 processor and other processors that support the PowerPC V2.05 architecture. ! `dlmzb' ! `no-dlmzb' Generate code that uses (does not use) the string-search ! `dlmzb' instruction on the IBM 405, 440, 464 and 476 processors. This instruction is generated by default when targeting those processors. ! `fprnd' ! `no-fprnd' Generate code that uses (does not use) the FP round to integer instructions implemented on the POWER5+ processor and other processors that support the PowerPC V2.03 architecture. ! `hard-dfp' ! `no-hard-dfp' Generate code that uses (does not use) the decimal floating-point instructions implemented on some POWER processors. ! `isel' ! `no-isel' Generate code that uses (does not use) ISEL instruction. ! `mfcrf' ! `no-mfcrf' Generate code that uses (does not use) the move from condition ! register field instruction implemented on the POWER4 ! processor and other processors that support the PowerPC V2.01 architecture. ! `mfpgpr' ! `no-mfpgpr' Generate code that uses (does not use) the FP move to/from general purpose register instructions implemented on the POWER6X processor and other processors that support the extended PowerPC V2.05 architecture. ! `mulhw' ! `no-mulhw' Generate code that uses (does not use) the half-word multiply and multiply-accumulate instructions on the IBM 405, 440, 464 and 476 processors. These instructions are generated by default when targeting those processors. ! `multiple' ! `no-multiple' Generate code that uses (does not use) the load multiple word instructions and the store multiple word instructions. ! `update' ! `no-update' Generate code that uses (does not use) the load or store instructions that update the base register to the address of the calculated memory location. ! `popcntb' ! `no-popcntb' Generate code that uses (does not use) the popcount and double-precision FP reciprocal estimate instruction implemented on the POWER5 processor and other processors that support the PowerPC V2.02 architecture. ! `popcntd' ! `no-popcntd' Generate code that uses (does not use) the popcount instruction implemented on the POWER7 processor and other processors that support the PowerPC V2.06 architecture. ! `powerpc-gfxopt' ! `no-powerpc-gfxopt' Generate code that uses (does not use) the optional PowerPC architecture instructions in the Graphics group, including floating-point select. ! `powerpc-gpopt' ! `no-powerpc-gpopt' Generate code that uses (does not use) the optional PowerPC architecture instructions in the General Purpose group, including floating-point square root. ! `recip-precision' ! `no-recip-precision' Assume (do not assume) that the reciprocal estimate instructions provide higher-precision estimates than is mandated by the PowerPC ABI. ! `string' ! `no-string' Generate code that uses (does not use) the load string instructions and the store string word instructions to save multiple registers and do small block moves. ! `vsx' ! `no-vsx' Generate code that uses (does not use) vector/scalar (VSX) instructions, and also enable the use of built-in functions that allow more direct access to the VSX instruction set. In 32-bit code, you cannot enable VSX or AltiVec instructions ! unless `-mabi=altivec' is used on the command line. ! `friz' ! `no-friz' ! Generate (do not generate) the `friz' instruction when the ! `-funsafe-math-optimizations' option is used to optimize rounding a floating-point value to 64-bit integer and back to ! floating point. The `friz' instruction does not return the ! same value if the floating-point number is too large to fit ! in an integer. ! `avoid-indexed-addresses' ! `no-avoid-indexed-addresses' Generate code that tries to avoid (not avoid) the use of indexed load or store instructions. ! `paired' ! `no-paired' Generate code that uses (does not use) the generation of PAIRED simd instructions. ! `longcall' ! `no-longcall' Generate code that assumes (does not assume) that all calls are far away so that a longer more expensive calling sequence is required. ! `cpu=CPU' Specify the architecture to generate code for when compiling ! the function. If you select the `target("cpu=power7")' attribute when generating 32-bit code, VSX and AltiVec instructions are not generated unless you use the ! `-mabi=altivec' option on the command line. ! `tune=TUNE' Specify the architecture to tune for when compiling the ! function. If you do not specify the `target("tune=TUNE")' ! attribute and you do specify the `target("cpu=CPU")' ! attribute, compilation tunes for the CPU architecture, and ! not the default tuning specified on the command line. On the PowerPC, the inliner does not inline a function that has different target options than the caller, unless the callee has a *************** File: gcc.info, Node: RL78 Function Att *** 28066,28090 **** These function attributes are supported by the RL78 back end: ! 'interrupt' ! 'brk_interrupt' These attributes indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! Use 'brk_interrupt' instead of 'interrupt' for handlers intended to ! be used with the 'BRK' opcode (i.e. those that must end with 'RETB' ! instead of 'RETI'). ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported.  --- 28261,28285 ---- These function attributes are supported by the RL78 back end: ! `interrupt' ! `brk_interrupt' These attributes indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! Use `brk_interrupt' instead of `interrupt' for handlers intended ! to be used with the `BRK' opcode (i.e. those that must end with ! `RETB' instead of `RETI'). ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported.  *************** File: gcc.info, Node: RX Function Attri *** 28095,28107 **** These function attributes are supported by the RX back end: ! 'fast_interrupt' Use this attribute on the RX port to indicate that the specified function is a fast interrupt handler. This is just like the ! 'interrupt' attribute, except that 'freit' is used to return ! instead of 'reit'. ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 28290,28302 ---- These function attributes are supported by the RX back end: ! `fast_interrupt' Use this attribute on the RX port to indicate that the specified function is a fast interrupt handler. This is just like the ! `interrupt' attribute, except that `freit' is used to return ! instead of `reit'. ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** These function attributes are supported *** 28110,28118 **** On RX targets, you may specify one or more vector numbers as arguments to the attribute, as well as naming an alternate table name. Parameters are handled sequentially, so one handler can be ! assigned to multiple entries in multiple tables. One may also pass ! the magic string '"$default"' which causes the function to be used ! for any unfilled slots in the current table. This example shows a simple assignment of a function to one vector in the default table (note that preprocessor macros may be used for --- 28305,28313 ---- On RX targets, you may specify one or more vector numbers as arguments to the attribute, as well as naming an alternate table name. Parameters are handled sequentially, so one handler can be ! assigned to multiple entries in multiple tables. One may also ! pass the magic string `"$default"' which causes the function to be ! used for any unfilled slots in the current table. This example shows a simple assignment of a function to one vector in the default table (note that preprocessor macros may be used for *************** These function attributes are supported *** 28121,28145 **** This example assigns a function to two slots in the default table (using preprocessor macros defined elsewhere) and makes it the ! default for the 'dct' table: void __attribute__ ((interrupt (RXD1_VECT,RXD2_VECT,"dct","$default"))) txd1_handler (); ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! 'vector' ! This RX attribute is similar to the 'interrupt' attribute, including its parameters, but does not make the function an ! interrupt-handler type function (i.e. it retains the normal C ! function calling ABI). See the 'interrupt' attribute for a description of its arguments.  --- 28316,28340 ---- This example assigns a function to two slots in the default table (using preprocessor macros defined elsewhere) and makes it the ! default for the `dct' table: void __attribute__ ((interrupt (RXD1_VECT,RXD2_VECT,"dct","$default"))) txd1_handler (); ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported. ! `vector' ! This RX attribute is similar to the `interrupt' attribute, including its parameters, but does not make the function an ! interrupt-handler type function (i.e. it retains the normal C ! function calling ABI). See the `interrupt' attribute for a description of its arguments.  *************** File: gcc.info, Node: S/390 Function At *** 28150,28206 **** These function attributes are supported on the S/390: ! 'hotpatch (HALFWORDS-BEFORE-FUNCTION-LABEL,HALFWORDS-AFTER-FUNCTION-LABEL)' ! On S/390 System z targets, you can use this function attribute to make GCC generate a "hot-patching" function prologue. If the ! '-mhotpatch=' command-line option is used at the same time, the ! 'hotpatch' attribute takes precedence. The first of the two arguments specifies the number of halfwords to be added before the function label. A second argument can be used to specify the ! number of halfwords to be added after the function label. For both ! arguments the maximum allowed value is 1000000. If both arguments are zero, hotpatching is disabled. ! 'target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On S/390, the following options are supported: ! 'arch=' ! 'tune=' ! 'stack-guard=' ! 'stack-size=' ! 'branch-cost=' ! 'warn-framesize=' ! 'backchain' ! 'no-backchain' ! 'hard-dfp' ! 'no-hard-dfp' ! 'hard-float' ! 'soft-float' ! 'htm' ! 'no-htm' ! 'vx' ! 'no-vx' ! 'packed-stack' ! 'no-packed-stack' ! 'small-exec' ! 'no-small-exec' ! 'mvcle' ! 'no-mvcle' ! 'warn-dynamicstack' ! 'no-warn-dynamicstack' The options work exactly like the S/390 specific command line ! options (without the prefix '-m') except that they do not change any feature macros. For example, ! target("no-vx") ! does not undefine the '__VEC__' macro.  File: gcc.info, Node: SH Function Attributes, Next: SPU Function Attributes, Prev: S/390 Function Attributes, Up: Function Attributes --- 28345,28414 ---- These function attributes are supported on the S/390: ! `hotpatch (HALFWORDS-BEFORE-FUNCTION-LABEL,HALFWORDS-AFTER-FUNCTION-LABEL)' On S/390 System z targets, you can use this function attribute to make GCC generate a "hot-patching" function prologue. If the ! `-mhotpatch=' command-line option is used at the same time, the ! `hotpatch' attribute takes precedence. The first of the two arguments specifies the number of halfwords to be added before the function label. A second argument can be used to specify the ! number of halfwords to be added after the function label. For ! both arguments the maximum allowed value is 1000000. If both arguments are zero, hotpatching is disabled. ! `target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On S/390, the following options are supported: ! `arch=' ! ! `tune=' ! ! `stack-guard=' ! ! `stack-size=' ! ! `branch-cost=' ! ! `warn-framesize=' ! ! `backchain' ! `no-backchain' ! ! `hard-dfp' ! `no-hard-dfp' ! ! `hard-float' ! `soft-float' ! ! `htm' ! `no-htm' ! ! `vx' ! `no-vx' ! ! `packed-stack' ! `no-packed-stack' ! ! `small-exec' ! `no-small-exec' ! ! `mvcle' ! `no-mvcle' ! ! `warn-dynamicstack' ! `no-warn-dynamicstack' The options work exactly like the S/390 specific command line ! options (without the prefix `-m') except that they do not change any feature macros. For example, ! `target("no-vx")' ! does not undefine the `__VEC__' macro.  File: gcc.info, Node: SH Function Attributes, Next: SPU Function Attributes, Prev: S/390 Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: SH Function Attri *** 28210,28266 **** These function attributes are supported on the SH family of processors: ! 'function_vector' On SH2A targets, this attribute declares a function to be called using the TBR relative addressing mode. The argument to this attribute is the entry number of the same function in a vector table containing all the TBR relative addressable functions. For ! correct operation the TBR must be setup accordingly to point to the ! start of the vector table before any functions with this attribute ! are invoked. Usually a good place to do the initialization is the ! startup routine. The TBR relative vector table can have at max 256 ! function entries. The jumps to these functions are generated using ! a SH2A specific, non delayed branch instruction JSR/N @(disp8,TBR). ! You must use GAS and GLD from GNU binutils version 2.7 or later for ! this attribute to work correctly. In an application, for a function being called once, this attribute saves at least 8 bytes of code; and if other successive calls are being made to the same function, it saves 2 bytes of code per each of these calls. ! 'interrupt_handler' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! 'nosave_low_regs' Use this attribute on SH targets to indicate that an ! 'interrupt_handler' function should not save and restore registers R0..R7. This can be used on SH3* and SH4* targets that have a second R0..R7 register bank for non-reentrant interrupt handlers. ! 'renesas' On SH targets this attribute specifies that the function or struct follows the Renesas ABI. ! 'resbank' On the SH2A target, this attribute enables the high-speed register saving and restoration using a register bank for ! 'interrupt_handler' routines. Saving to the bank is performed automatically after the CPU accepts an interrupt that uses a register bank. The nineteen 32-bit registers comprising general register R0 to R14, control register GBR, and system registers MACH, MACL, and PR ! and the vector table address offset are saved into a register bank. ! Register banks are stacked in first-in last-out (FILO) sequence. ! Restoration from the bank is executed by issuing a RESBANK ! instruction. ! 'sp_switch' ! Use this attribute on the SH to indicate an 'interrupt_handler' function should switch to an alternate stack. It expects a string argument that names a global variable holding the address of the alternate stack. --- 28418,28474 ---- These function attributes are supported on the SH family of processors: ! `function_vector' On SH2A targets, this attribute declares a function to be called using the TBR relative addressing mode. The argument to this attribute is the entry number of the same function in a vector table containing all the TBR relative addressable functions. For ! correct operation the TBR must be setup accordingly to point to ! the start of the vector table before any functions with this ! attribute are invoked. Usually a good place to do the ! initialization is the startup routine. The TBR relative vector ! table can have at max 256 function entries. The jumps to these ! functions are generated using a SH2A specific, non delayed branch ! instruction JSR/N @(disp8,TBR). You must use GAS and GLD from GNU ! binutils version 2.7 or later for this attribute to work correctly. In an application, for a function being called once, this attribute saves at least 8 bytes of code; and if other successive calls are being made to the same function, it saves 2 bytes of code per each of these calls. ! `interrupt_handler' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this attribute is present. ! `nosave_low_regs' Use this attribute on SH targets to indicate that an ! `interrupt_handler' function should not save and restore registers R0..R7. This can be used on SH3* and SH4* targets that have a second R0..R7 register bank for non-reentrant interrupt handlers. ! `renesas' On SH targets this attribute specifies that the function or struct follows the Renesas ABI. ! `resbank' On the SH2A target, this attribute enables the high-speed register saving and restoration using a register bank for ! `interrupt_handler' routines. Saving to the bank is performed automatically after the CPU accepts an interrupt that uses a register bank. The nineteen 32-bit registers comprising general register R0 to R14, control register GBR, and system registers MACH, MACL, and PR ! and the vector table address offset are saved into a register ! bank. Register banks are stacked in first-in last-out (FILO) ! sequence. Restoration from the bank is executed by issuing a ! RESBANK instruction. ! `sp_switch' ! Use this attribute on the SH to indicate an `interrupt_handler' function should switch to an alternate stack. It expects a string argument that names a global variable holding the address of the alternate stack. *************** These function attributes are supported *** 28269,28282 **** void f () __attribute__ ((interrupt_handler, sp_switch ("alt_stack"))); ! 'trap_exit' ! Use this attribute on the SH for an 'interrupt_handler' to return ! using 'trapa' instead of 'rte'. This attribute expects an integer argument specifying the trap number to be used. ! 'trapa_handler' On SH targets this function attribute is similar to ! 'interrupt_handler' but it does not save and restore all registers.  File: gcc.info, Node: SPU Function Attributes, Next: Symbian OS Function Attributes, Prev: SH Function Attributes, Up: Function Attributes --- 28477,28490 ---- void f () __attribute__ ((interrupt_handler, sp_switch ("alt_stack"))); ! `trap_exit' ! Use this attribute on the SH for an `interrupt_handler' to return ! using `trapa' instead of `rte'. This attribute expects an integer argument specifying the trap number to be used. ! `trapa_handler' On SH targets this function attribute is similar to ! `interrupt_handler' but it does not save and restore all registers.  File: gcc.info, Node: SPU Function Attributes, Next: Symbian OS Function Attributes, Prev: SH Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: SPU Function Attr *** 28286,28299 **** These function attributes are supported by the SPU back end: ! 'naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to be ! assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! 'asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended 'asm' or a mixture of basic ! 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported.  --- 28494,28507 ---- These function attributes are supported by the SPU back end: ! `naked' This attribute allows the compiler to construct the requisite ! function declaration, while allowing the body of the function to ! be assembly code. The specified function will not have ! prologue/epilogue sequences generated by the compiler. Only basic ! `asm' statements can safely be included in naked functions (*note ! Basic Asm::). While using extended `asm' or a mixture of basic ! `asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported.  *************** File: gcc.info, Node: Symbian OS Functi *** 28303,28309 **** -------------------------------------- *Note Microsoft Windows Function Attributes::, for discussion of the ! 'dllexport' and 'dllimport' attributes.  File: gcc.info, Node: V850 Function Attributes, Next: Visium Function Attributes, Prev: Symbian OS Function Attributes, Up: Function Attributes --- 28511,28517 ---- -------------------------------------- *Note Microsoft Windows Function Attributes::, for discussion of the ! `dllexport' and `dllimport' attributes.  File: gcc.info, Node: V850 Function Attributes, Next: Visium Function Attributes, Prev: Symbian OS Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: V850 Function Att *** 28313,28320 **** The V850 back end supports these function attributes: ! 'interrupt' ! 'interrupt_handler' Use these attributes to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when either --- 28521,28528 ---- The V850 back end supports these function attributes: ! `interrupt' ! `interrupt_handler' Use these attributes to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when either *************** File: gcc.info, Node: Visium Function A *** 28328,28334 **** These function attributes are supported by the Visium back end: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 28536,28542 ---- These function attributes are supported by the Visium back end: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** File: gcc.info, Node: x86 Function Attr *** 28342,28387 **** These function attributes are supported by the x86 back end: ! 'cdecl' ! On the x86-32 targets, the 'cdecl' attribute causes the compiler to assume that the calling function pops off the stack space used to pass arguments. This is useful to override the effects of the ! '-mrtd' switch. ! 'fastcall' ! On x86-32 targets, the 'fastcall' attribute causes the compiler to pass the first argument (if of integral type) in the register ECX and the second argument (if of integral type) in the register EDX. Subsequent and other typed arguments are passed on the stack. The ! called function pops the arguments off the stack. If the number of ! arguments is variable all arguments are pushed on the stack. ! 'thiscall' ! On x86-32 targets, the 'thiscall' attribute causes the compiler to pass the first argument (if of integral type) in the register ECX. ! Subsequent and other typed arguments are passed on the stack. The ! called function pops the arguments off the stack. If the number of ! arguments is variable all arguments are pushed on the stack. The ! 'thiscall' attribute is intended for C++ non-static member ! functions. As a GCC extension, this calling convention can be used ! for C functions and for static member methods. ! ! 'ms_abi' ! 'sysv_abi' On 32-bit and 64-bit x86 targets, you can use an ABI attribute to indicate which calling convention should be used for a function. ! The 'ms_abi' attribute tells the compiler to use the Microsoft ABI, ! while the 'sysv_abi' attribute tells the compiler to use the ABI used on GNU/Linux and other systems. The default is to use the Microsoft ABI when targeting Windows. On all other systems, the default is the x86/AMD ABI. ! Note, the 'ms_abi' attribute for Microsoft Windows 64-bit targets ! currently requires the '-maccumulate-outgoing-args' option. ! ! 'callee_pop_aggregate_return (NUMBER)' On x86-32 targets, you can use this attribute to control how aggregates are returned in memory. If the caller is responsible for popping the hidden pointer together with the rest of the --- 28550,28593 ---- These function attributes are supported by the x86 back end: ! `cdecl' ! On the x86-32 targets, the `cdecl' attribute causes the compiler to assume that the calling function pops off the stack space used to pass arguments. This is useful to override the effects of the ! `-mrtd' switch. ! `fastcall' ! On x86-32 targets, the `fastcall' attribute causes the compiler to pass the first argument (if of integral type) in the register ECX and the second argument (if of integral type) in the register EDX. Subsequent and other typed arguments are passed on the stack. The ! called function pops the arguments off the stack. If the number ! of arguments is variable all arguments are pushed on the stack. ! `thiscall' ! On x86-32 targets, the `thiscall' attribute causes the compiler to pass the first argument (if of integral type) in the register ECX. ! Subsequent and other typed arguments are passed on the stack. The ! called function pops the arguments off the stack. If the number ! of arguments is variable all arguments are pushed on the stack. ! The `thiscall' attribute is intended for C++ non-static member ! functions. As a GCC extension, this calling convention can be ! used for C functions and for static member methods. + `ms_abi' + `sysv_abi' On 32-bit and 64-bit x86 targets, you can use an ABI attribute to indicate which calling convention should be used for a function. ! The `ms_abi' attribute tells the compiler to use the Microsoft ABI, ! while the `sysv_abi' attribute tells the compiler to use the ABI used on GNU/Linux and other systems. The default is to use the Microsoft ABI when targeting Windows. On all other systems, the default is the x86/AMD ABI. ! Note, the `ms_abi' attribute for Microsoft Windows 64-bit targets ! currently requires the `-maccumulate-outgoing-args' option. + `callee_pop_aggregate_return (NUMBER)' On x86-32 targets, you can use this attribute to control how aggregates are returned in memory. If the caller is responsible for popping the hidden pointer together with the rest of the *************** These function attributes are supported *** 28392,28574 **** hidden pointer. However, on x86-32 Microsoft Windows targets, the compiler assumes that the caller pops the stack for hidden pointer. ! 'ms_hook_prologue' ! On 32-bit and 64-bit x86 targets, you can use this function ! attribute to make GCC generate the "hot-patching" function prologue ! used in Win32 API functions in Microsoft Windows XP Service Pack 2 ! and newer. ! 'regparm (NUMBER)' ! On x86-32 targets, the 'regparm' attribute causes the compiler to ! pass arguments number one to NUMBER if they are of integral type in ! registers EAX, EDX, and ECX instead of on the stack. Functions that take a variable number of arguments continue to be passed all of their arguments on the stack. Beware that on some ELF systems this attribute is unsuitable for global functions in shared libraries with lazy binding (which is ! the default). Lazy binding sends the first call via resolving code ! in the loader, which might assume EAX, EDX and ECX can be clobbered, as per the standard calling conventions. Solaris 8 is affected by this. Systems with the GNU C Library version 2.1 or higher and FreeBSD are believed to be safe since the loaders there ! save EAX, EDX and ECX. (Lazy binding can be disabled with the linker or the loader if desired, to avoid the problem.) ! 'sseregparm' ! On x86-32 targets with SSE support, the 'sseregparm' attribute ! causes the compiler to pass up to 3 floating-point arguments in SSE ! registers instead of on the stack. Functions that take a variable ! number of arguments continue to pass all of their floating-point ! arguments on the stack. ! 'force_align_arg_pointer' ! On x86 targets, the 'force_align_arg_pointer' attribute may be applied to individual function definitions, generating an alternate prologue and epilogue that realigns the run-time stack if necessary. This supports mixing legacy codes that run with a 4-byte aligned stack with modern codes that keep a 16-byte stack for SSE compatibility. ! 'stdcall' ! On x86-32 targets, the 'stdcall' attribute causes the compiler to assume that the called function pops off the stack space used to pass arguments, unless it takes a variable number of arguments. ! 'target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On the x86, the following options are allowed: ! 'abm' ! 'no-abm' Enable/disable the generation of the advanced bit instructions. ! 'aes' ! 'no-aes' Enable/disable the generation of the AES instructions. ! 'default' *Note Function Multiversioning::, where it is used to specify the default function version. ! 'mmx' ! 'no-mmx' Enable/disable the generation of the MMX instructions. ! 'pclmul' ! 'no-pclmul' Enable/disable the generation of the PCLMUL instructions. ! 'popcnt' ! 'no-popcnt' Enable/disable the generation of the POPCNT instruction. ! 'sse' ! 'no-sse' Enable/disable the generation of the SSE instructions. ! 'sse2' ! 'no-sse2' Enable/disable the generation of the SSE2 instructions. ! 'sse3' ! 'no-sse3' Enable/disable the generation of the SSE3 instructions. ! 'sse4' ! 'no-sse4' Enable/disable the generation of the SSE4 instructions (both SSE4.1 and SSE4.2). ! 'sse4.1' ! 'no-sse4.1' Enable/disable the generation of the sse4.1 instructions. ! 'sse4.2' ! 'no-sse4.2' Enable/disable the generation of the sse4.2 instructions. ! 'sse4a' ! 'no-sse4a' Enable/disable the generation of the SSE4A instructions. ! 'fma4' ! 'no-fma4' Enable/disable the generation of the FMA4 instructions. ! 'xop' ! 'no-xop' Enable/disable the generation of the XOP instructions. ! 'lwp' ! 'no-lwp' Enable/disable the generation of the LWP instructions. ! 'ssse3' ! 'no-ssse3' Enable/disable the generation of the SSSE3 instructions. ! 'cld' ! 'no-cld' Enable/disable the generation of the CLD before string moves. ! 'fancy-math-387' ! 'no-fancy-math-387' ! Enable/disable the generation of the 'sin', 'cos', and 'sqrt' instructions on the 387 floating-point unit. ! 'fused-madd' ! 'no-fused-madd' Enable/disable the generation of the fused multiply/add instructions. ! 'ieee-fp' ! 'no-ieee-fp' Enable/disable the generation of floating point that depends on IEEE arithmetic. ! 'inline-all-stringops' ! 'no-inline-all-stringops' Enable/disable inlining of string operations. ! 'inline-stringops-dynamically' ! 'no-inline-stringops-dynamically' Enable/disable the generation of the inline code to do small string operations and calling the library routines for large operations. ! 'align-stringops' ! 'no-align-stringops' Do/do not align destination of inlined string operations. ! 'recip' ! 'no-recip' Enable/disable the generation of RCPSS, RCPPS, RSQRTSS and RSQRTPS instructions followed an additional Newton-Raphson step instead of doing a floating-point division. ! 'arch=ARCH' ! Specify the architecture to generate code for in compiling the ! function. ! 'tune=TUNE' Specify the architecture to tune for in compiling the function. ! 'fpmath=FPMATH' Specify which floating-point unit to use. You must specify ! the 'target("fpmath=sse,387")' option as ! 'target("fpmath=sse+387")' because the comma would separate different options. On the x86, the inliner does not inline a function that has different target options than the caller, unless the callee has a ! subset of the target options of the caller. For example a function ! declared with 'target("sse3")' can inline a function with ! 'target("sse2")', since '-msse3' implies '-msse2'.  File: gcc.info, Node: Xstormy16 Function Attributes, Prev: x86 Function Attributes, Up: Function Attributes --- 28598,28779 ---- hidden pointer. However, on x86-32 Microsoft Windows targets, the compiler assumes that the caller pops the stack for hidden pointer. ! `ms_hook_prologue' On 32-bit and 64-bit x86 targets, you can use this function ! attribute to make GCC generate the "hot-patching" function ! prologue used in Win32 API functions in Microsoft Windows XP ! Service Pack 2 and newer. ! `regparm (NUMBER)' ! On x86-32 targets, the `regparm' attribute causes the compiler to ! pass arguments number one to NUMBER if they are of integral type ! in registers EAX, EDX, and ECX instead of on the stack. Functions that take a variable number of arguments continue to be passed all of their arguments on the stack. Beware that on some ELF systems this attribute is unsuitable for global functions in shared libraries with lazy binding (which is ! the default). Lazy binding sends the first call via resolving ! code in the loader, which might assume EAX, EDX and ECX can be clobbered, as per the standard calling conventions. Solaris 8 is affected by this. Systems with the GNU C Library version 2.1 or higher and FreeBSD are believed to be safe since the loaders there ! save EAX, EDX and ECX. (Lazy binding can be disabled with the linker or the loader if desired, to avoid the problem.) ! `sseregparm' ! On x86-32 targets with SSE support, the `sseregparm' attribute ! causes the compiler to pass up to 3 floating-point arguments in ! SSE registers instead of on the stack. Functions that take a ! variable number of arguments continue to pass all of their ! floating-point arguments on the stack. ! `force_align_arg_pointer' ! On x86 targets, the `force_align_arg_pointer' attribute may be applied to individual function definitions, generating an alternate prologue and epilogue that realigns the run-time stack if necessary. This supports mixing legacy codes that run with a 4-byte aligned stack with modern codes that keep a 16-byte stack for SSE compatibility. ! `stdcall' ! On x86-32 targets, the `stdcall' attribute causes the compiler to assume that the called function pops off the stack space used to pass arguments, unless it takes a variable number of arguments. ! `target (OPTIONS)' As discussed in *note Common Function Attributes::, this attribute allows specification of target-specific compilation options. On the x86, the following options are allowed: ! `abm' ! `no-abm' Enable/disable the generation of the advanced bit instructions. ! `aes' ! `no-aes' Enable/disable the generation of the AES instructions. ! `default' *Note Function Multiversioning::, where it is used to specify the default function version. ! `mmx' ! `no-mmx' Enable/disable the generation of the MMX instructions. ! `pclmul' ! `no-pclmul' Enable/disable the generation of the PCLMUL instructions. ! `popcnt' ! `no-popcnt' Enable/disable the generation of the POPCNT instruction. ! `sse' ! `no-sse' Enable/disable the generation of the SSE instructions. ! `sse2' ! `no-sse2' Enable/disable the generation of the SSE2 instructions. ! `sse3' ! `no-sse3' Enable/disable the generation of the SSE3 instructions. ! `sse4' ! `no-sse4' Enable/disable the generation of the SSE4 instructions (both SSE4.1 and SSE4.2). ! `sse4.1' ! `no-sse4.1' Enable/disable the generation of the sse4.1 instructions. ! `sse4.2' ! `no-sse4.2' Enable/disable the generation of the sse4.2 instructions. ! `sse4a' ! `no-sse4a' Enable/disable the generation of the SSE4A instructions. ! `fma4' ! `no-fma4' Enable/disable the generation of the FMA4 instructions. ! `xop' ! `no-xop' Enable/disable the generation of the XOP instructions. ! `lwp' ! `no-lwp' Enable/disable the generation of the LWP instructions. ! `ssse3' ! `no-ssse3' Enable/disable the generation of the SSSE3 instructions. ! `cld' ! `no-cld' Enable/disable the generation of the CLD before string moves. ! `fancy-math-387' ! `no-fancy-math-387' ! Enable/disable the generation of the `sin', `cos', and `sqrt' instructions on the 387 floating-point unit. ! `fused-madd' ! `no-fused-madd' Enable/disable the generation of the fused multiply/add instructions. ! `ieee-fp' ! `no-ieee-fp' Enable/disable the generation of floating point that depends on IEEE arithmetic. ! `inline-all-stringops' ! `no-inline-all-stringops' Enable/disable inlining of string operations. ! `inline-stringops-dynamically' ! `no-inline-stringops-dynamically' Enable/disable the generation of the inline code to do small string operations and calling the library routines for large operations. ! `align-stringops' ! `no-align-stringops' Do/do not align destination of inlined string operations. ! `recip' ! `no-recip' Enable/disable the generation of RCPSS, RCPPS, RSQRTSS and RSQRTPS instructions followed an additional Newton-Raphson step instead of doing a floating-point division. ! `arch=ARCH' ! Specify the architecture to generate code for in compiling ! the function. ! `tune=TUNE' Specify the architecture to tune for in compiling the function. ! `fpmath=FPMATH' Specify which floating-point unit to use. You must specify ! the `target("fpmath=sse,387")' option as ! `target("fpmath=sse+387")' because the comma would separate different options. On the x86, the inliner does not inline a function that has different target options than the caller, unless the callee has a ! subset of the target options of the caller. For example a ! function declared with `target("sse3")' can inline a function with ! `target("sse2")', since `-msse3' implies `-msse2'.  File: gcc.info, Node: Xstormy16 Function Attributes, Prev: x86 Function Attributes, Up: Function Attributes *************** File: gcc.info, Node: Xstormy16 Functio *** 28578,28584 **** These function attributes are supported by the Xstormy16 back end: ! 'interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this --- 28783,28789 ---- These function attributes are supported by the Xstormy16 back end: ! `interrupt' Use this attribute to indicate that the specified function is an interrupt handler. The compiler generates function entry and exit sequences suitable for use in an interrupt handler when this *************** File: gcc.info, Node: Variable Attribut *** 28590,28604 **** 6.32 Specifying Attributes of Variables ======================================= ! The keyword '__attribute__' allows you to specify special attributes of ! variables or structure fields. This keyword is followed by an attribute ! specification inside double parentheses. Some attributes are currently ! defined generically for variables. Other attributes are defined for ! variables on particular target systems. Other attributes are available ! for functions (*note Function Attributes::), labels (*note Label ! Attributes::), enumerators (*note Enumerator Attributes::), and for ! types (*note Type Attributes::). Other front ends might define more ! attributes (*note Extensions to the C++ Language: C++ Extensions.). *Note Attribute Syntax::, for details of the exact syntax for using attributes. --- 28795,28810 ---- 6.32 Specifying Attributes of Variables ======================================= ! The keyword `__attribute__' allows you to specify special attributes of ! variables or structure fields. This keyword is followed by an ! attribute specification inside double parentheses. Some attributes are ! currently defined generically for variables. Other attributes are ! defined for variables on particular target systems. Other attributes ! are available for functions (*note Function Attributes::), labels ! (*note Label Attributes::), enumerators (*note Enumerator ! Attributes::), and for types (*note Type Attributes::). Other front ! ends might define more attributes (*note Extensions to the C++ ! Language: C++ Extensions.). *Note Attribute Syntax::, for details of the exact syntax for using attributes. *************** File: gcc.info, Node: Common Variable A *** 28629,28652 **** The following attributes are supported on most targets. ! 'aligned (ALIGNMENT)' This attribute specifies a minimum alignment for the variable or structure field, measured in bytes. For example, the declaration: int x __attribute__ ((aligned (16))) = 0; ! causes the compiler to allocate the global variable 'x' on a 16-byte boundary. On a 68040, this could be used in conjunction ! with an 'asm' expression to access the 'move16' instruction which requires 16-byte aligned operands. You can also specify the alignment of structure fields. For ! example, to create a double-word aligned 'int' pair, you could write: struct foo { int x[2] __attribute__ ((aligned (8))); }; ! This is an alternative to creating a union with a 'double' member, which forces the union to be double-word aligned. As in the preceding examples, you can explicitly specify the --- 28835,28858 ---- The following attributes are supported on most targets. ! `aligned (ALIGNMENT)' This attribute specifies a minimum alignment for the variable or structure field, measured in bytes. For example, the declaration: int x __attribute__ ((aligned (16))) = 0; ! causes the compiler to allocate the global variable `x' on a 16-byte boundary. On a 68040, this could be used in conjunction ! with an `asm' expression to access the `move16' instruction which requires 16-byte aligned operands. You can also specify the alignment of structure fields. For ! example, to create a double-word aligned `int' pair, you could write: struct foo { int x[2] __attribute__ ((aligned (8))); }; ! This is an alternative to creating a union with a `double' member, which forces the union to be double-word aligned. As in the preceding examples, you can explicitly specify the *************** The following attributes are supported o *** 28659,28665 **** supports vector operations. The default alignment is fixed for a particular target ABI. ! GCC also provides a target specific macro '__BIGGEST_ALIGNMENT__', which is the largest alignment ever used for any data type on the target machine you are compiling for. For example, you could write: --- 28865,28871 ---- supports vector operations. The default alignment is fixed for a particular target ABI. ! GCC also provides a target specific macro `__BIGGEST_ALIGNMENT__', which is the largest alignment ever used for any data type on the target machine you are compiling for. For example, you could write: *************** The following attributes are supported o *** 28667,28725 **** short array[3] __attribute__ ((aligned (__BIGGEST_ALIGNMENT__))); The compiler automatically sets the alignment for the declared ! variable or field to '__BIGGEST_ALIGNMENT__'. Doing this can often ! make copy operations more efficient, because the compiler can use ! whatever instructions copy the biggest chunks of memory when performing copies to or from the variables or fields that you have ! aligned this way. Note that the value of '__BIGGEST_ALIGNMENT__' may change depending on command-line options. ! When used on a struct, or struct member, the 'aligned' attribute can only increase the alignment; in order to decrease it, the ! 'packed' attribute must be specified as well. When used as part of ! a typedef, the 'aligned' attribute can both increase and decrease ! alignment, and specifying the 'packed' attribute generates a ! warning. ! Note that the effectiveness of 'aligned' attributes may be limited by inherent limitations in your linker. On many systems, the linker is only able to arrange for variables to be aligned up to a certain maximum alignment. (For some linkers, the maximum supported alignment may be very very small.) If your linker is only able to align variables up to a maximum of 8-byte alignment, ! then specifying 'aligned(16)' in an '__attribute__' still only provides you with 8-byte alignment. See your linker documentation for further information. ! The 'aligned' attribute can also be used for functions (*note Common Function Attributes::.) ! 'cleanup (CLEANUP_FUNCTION)' ! The 'cleanup' attribute runs a function when the variable goes out of scope. This attribute can only be applied to auto function scope variables; it may not be applied to parameters or variables with static storage duration. The function must take one parameter, a pointer to a type compatible with the variable. The return value of the function (if any) is ignored. ! If '-fexceptions' is enabled, then CLEANUP_FUNCTION is run during the stack unwinding that happens during the processing of the ! exception. Note that the 'cleanup' attribute does not allow the ! exception to be caught, only to perform an action. It is undefined ! what happens if CLEANUP_FUNCTION does not return normally. ! 'common' ! 'nocommon' ! The 'common' attribute requests GCC to place a variable in "common" ! storage. The 'nocommon' attribute requests the opposite--to ! allocate space for it directly. ! These attributes override the default chosen by the '-fno-common' ! and '-fcommon' flags respectively. ! 'deprecated' ! 'deprecated (MSG)' ! The 'deprecated' attribute results in a warning if the variable is used anywhere in the source file. This is useful when identifying variables that are expected to be removed in a future version of a program. The warning also includes the location of the declaration --- 28873,28932 ---- short array[3] __attribute__ ((aligned (__BIGGEST_ALIGNMENT__))); The compiler automatically sets the alignment for the declared ! variable or field to `__BIGGEST_ALIGNMENT__'. Doing this can ! often make copy operations more efficient, because the compiler can ! use whatever instructions copy the biggest chunks of memory when performing copies to or from the variables or fields that you have ! aligned this way. Note that the value of `__BIGGEST_ALIGNMENT__' may change depending on command-line options. ! When used on a struct, or struct member, the `aligned' attribute can only increase the alignment; in order to decrease it, the ! `packed' attribute must be specified as well. When used as part ! of a typedef, the `aligned' attribute can both increase and ! decrease alignment, and specifying the `packed' attribute ! generates a warning. ! Note that the effectiveness of `aligned' attributes may be limited by inherent limitations in your linker. On many systems, the linker is only able to arrange for variables to be aligned up to a certain maximum alignment. (For some linkers, the maximum supported alignment may be very very small.) If your linker is only able to align variables up to a maximum of 8-byte alignment, ! then specifying `aligned(16)' in an `__attribute__' still only provides you with 8-byte alignment. See your linker documentation for further information. ! The `aligned' attribute can also be used for functions (*note Common Function Attributes::.) ! `cleanup (CLEANUP_FUNCTION)' ! The `cleanup' attribute runs a function when the variable goes out of scope. This attribute can only be applied to auto function scope variables; it may not be applied to parameters or variables with static storage duration. The function must take one parameter, a pointer to a type compatible with the variable. The return value of the function (if any) is ignored. ! If `-fexceptions' is enabled, then CLEANUP_FUNCTION is run during the stack unwinding that happens during the processing of the ! exception. Note that the `cleanup' attribute does not allow the ! exception to be caught, only to perform an action. It is ! undefined what happens if CLEANUP_FUNCTION does not return ! normally. ! `common' ! `nocommon' ! The `common' attribute requests GCC to place a variable in ! "common" storage. The `nocommon' attribute requests the ! opposite--to allocate space for it directly. ! These attributes override the default chosen by the `-fno-common' ! and `-fcommon' flags respectively. ! `deprecated' ! `deprecated (MSG)' ! The `deprecated' attribute results in a warning if the variable is used anywhere in the source file. This is useful when identifying variables that are expected to be removed in a future version of a program. The warning also includes the location of the declaration *************** The following attributes are supported o *** 28735,28763 **** argument, which must be a string, is printed in the warning if present. ! The 'deprecated' attribute can also be used for functions and types ! (*note Common Function Attributes::, *note Common Type Attributes::). ! 'mode (MODE)' This attribute specifies the data type for the declaration--whichever type corresponds to the mode MODE. This in ! effect lets you request an integer or floating-point type according ! to its width. ! You may also specify a mode of 'byte' or '__byte__' to indicate the ! mode corresponding to a one-byte integer, 'word' or '__word__' for ! the mode of a one-word integer, and 'pointer' or '__pointer__' for ! the mode used to represent pointers. ! 'packed' ! The 'packed' attribute specifies that a variable or structure field should have the smallest possible alignment--one byte for a variable, and one bit for a field, unless you specify a larger ! value with the 'aligned' attribute. ! Here is a structure in which the field 'x' is packed, so that it ! immediately follows 'a': struct foo { --- 28942,28970 ---- argument, which must be a string, is printed in the warning if present. ! The `deprecated' attribute can also be used for functions and ! types (*note Common Function Attributes::, *note Common Type Attributes::). ! `mode (MODE)' This attribute specifies the data type for the declaration--whichever type corresponds to the mode MODE. This in ! effect lets you request an integer or floating-point type ! according to its width. ! You may also specify a mode of `byte' or `__byte__' to indicate ! the mode corresponding to a one-byte integer, `word' or `__word__' ! for the mode of a one-word integer, and `pointer' or `__pointer__' ! for the mode used to represent pointers. ! `packed' ! The `packed' attribute specifies that a variable or structure field should have the smallest possible alignment--one byte for a variable, and one bit for a field, unless you specify a larger ! value with the `aligned' attribute. ! Here is a structure in which the field `x' is packed, so that it ! immediately follows `a': struct foo { *************** The following attributes are supported o *** 28765,28782 **** int x[2] __attribute__ ((packed)); }; ! _Note:_ The 4.1, 4.2 and 4.3 series of GCC ignore the 'packed' ! attribute on bit-fields of type 'char'. This has been fixed in GCC ! 4.4 but the change can lead to differences in the structure layout. ! See the documentation of '-Wpacked-bitfield-compat' for more ! information. ! 'section ("SECTION-NAME")' Normally, the compiler places the objects it generates in sections ! like 'data' and 'bss'. Sometimes, however, you need additional sections, or you need certain particular variables to appear in special sections, for example to map to special hardware. The ! 'section' attribute specifies that a variable (or function) lives in a particular section. For example, this small program uses several specific section names: --- 28972,28989 ---- int x[2] __attribute__ ((packed)); }; ! _Note:_ The 4.1, 4.2 and 4.3 series of GCC ignore the `packed' ! attribute on bit-fields of type `char'. This has been fixed in ! GCC 4.4 but the change can lead to differences in the structure ! layout. See the documentation of `-Wpacked-bitfield-compat' for ! more information. ! `section ("SECTION-NAME")' Normally, the compiler places the objects it generates in sections ! like `data' and `bss'. Sometimes, however, you need additional sections, or you need certain particular variables to appear in special sections, for example to map to special hardware. The ! `section' attribute specifies that a variable (or function) lives in a particular section. For example, this small program uses several specific section names: *************** The following attributes are supported o *** 28798,28836 **** init_duart (&b); } ! Use the 'section' attribute with _global_ variables and not _local_ ! variables, as shown in the example. ! You may use the 'section' attribute with initialized or uninitialized global variables but the linker requires each object be defined once, with the exception that uninitialized variables ! tentatively go in the 'common' (or 'bss') section and can be ! multiply "defined". Using the 'section' attribute changes what ! section the variable goes into and may cause the linker to issue an ! error if an uninitialized variable has multiple definitions. You ! can force a variable to be initialized with the '-fno-common' flag ! or the 'nocommon' attribute. Some file formats do not support arbitrary sections so the ! 'section' attribute is not available on all platforms. If you need ! to map the entire contents of a module to a particular section, ! consider using the facilities of the linker instead. ! 'tls_model ("TLS_MODEL")' ! The 'tls_model' attribute sets thread-local storage model (*note ! Thread-Local::) of a particular '__thread' variable, overriding ! '-ftls-model=' command-line switch on a per-variable basis. The ! TLS_MODEL argument should be one of 'global-dynamic', ! 'local-dynamic', 'initial-exec' or 'local-exec'. Not all targets support this attribute. ! 'unused' This attribute, attached to a variable, means that the variable is meant to be possibly unused. GCC does not produce a warning for this variable. ! 'used' This attribute, attached to a variable with static storage, means that the variable must be emitted even if it appears that the variable is not referenced. --- 29005,29043 ---- init_duart (&b); } ! Use the `section' attribute with _global_ variables and not ! _local_ variables, as shown in the example. ! You may use the `section' attribute with initialized or uninitialized global variables but the linker requires each object be defined once, with the exception that uninitialized variables ! tentatively go in the `common' (or `bss') section and can be ! multiply "defined". Using the `section' attribute changes what ! section the variable goes into and may cause the linker to issue ! an error if an uninitialized variable has multiple definitions. ! You can force a variable to be initialized with the `-fno-common' ! flag or the `nocommon' attribute. Some file formats do not support arbitrary sections so the ! `section' attribute is not available on all platforms. If you ! need to map the entire contents of a module to a particular ! section, consider using the facilities of the linker instead. ! `tls_model ("TLS_MODEL")' ! The `tls_model' attribute sets thread-local storage model (*note ! Thread-Local::) of a particular `__thread' variable, overriding ! `-ftls-model=' command-line switch on a per-variable basis. The ! TLS_MODEL argument should be one of `global-dynamic', ! `local-dynamic', `initial-exec' or `local-exec'. Not all targets support this attribute. ! `unused' This attribute, attached to a variable, means that the variable is meant to be possibly unused. GCC does not produce a warning for this variable. ! `used' This attribute, attached to a variable with static storage, means that the variable must be emitted even if it appears that the variable is not referenced. *************** The following attributes are supported o *** 28839,28895 **** attribute also means that the member is instantiated if the class itself is instantiated. ! 'vector_size (BYTES)' ! This attribute specifies the vector size for the variable, measured ! in bytes. For example, the declaration: int foo __attribute__ ((vector_size (16))); ! causes the compiler to set the mode for 'foo', to be 16 bytes, ! divided into 'int' sized units. Assuming a 32-bit int (a vector of ! 4 units of 4 bytes), the corresponding mode of 'foo' is V4SI. This attribute is only applicable to integral and float scalars, although arrays, pointers, and function return values are allowed in conjunction with this construct. ! Aggregates with this attribute are invalid, even if they are of the ! same size as a corresponding scalar. For example, the declaration: struct S { int a; }; struct S __attribute__ ((vector_size (16))) foo; is invalid even if the size of the structure is the same as the ! size of the 'int'. ! 'visibility ("VISIBILITY_TYPE")' This attribute affects the linkage of the declaration to which it ! is attached. The 'visibility' attribute is described in *note Common Function Attributes::. ! 'weak' ! The 'weak' attribute is described in *note Common Function Attributes::.  File: gcc.info, Node: AVR Variable Attributes, Next: Blackfin Variable Attributes, Prev: Common Variable Attributes, Up: Variable Attributes 6.32.2 AVR Variable Attributes ------------------------------ ! 'progmem' ! The 'progmem' attribute is used on the AVR to place read-only data ! in the non-volatile program memory (flash). The 'progmem' attribute accomplishes this by putting respective variables into a ! section whose name starts with '.progmem'. ! This attribute works similar to the 'section' attribute but adds ! additional checking. Notice that just like the 'section' ! attribute, 'progmem' affects the location of the data but not how this data is accessed. ! In order to read data located with the 'progmem' attribute (inline) ! assembler must be used. /* Use custom macros from AVR-LibC (http://nongnu.org/avr-libc/user-manual/) */ #include --- 29046,29104 ---- attribute also means that the member is instantiated if the class itself is instantiated. ! `vector_size (BYTES)' ! This attribute specifies the vector size for the variable, ! measured in bytes. For example, the declaration: int foo __attribute__ ((vector_size (16))); ! causes the compiler to set the mode for `foo', to be 16 bytes, ! divided into `int' sized units. Assuming a 32-bit int (a vector of ! 4 units of 4 bytes), the corresponding mode of `foo' is V4SI. This attribute is only applicable to integral and float scalars, although arrays, pointers, and function return values are allowed in conjunction with this construct. ! Aggregates with this attribute are invalid, even if they are of ! the same size as a corresponding scalar. For example, the ! declaration: struct S { int a; }; struct S __attribute__ ((vector_size (16))) foo; is invalid even if the size of the structure is the same as the ! size of the `int'. ! `visibility ("VISIBILITY_TYPE")' This attribute affects the linkage of the declaration to which it ! is attached. The `visibility' attribute is described in *note Common Function Attributes::. ! `weak' ! The `weak' attribute is described in *note Common Function Attributes::. +  File: gcc.info, Node: AVR Variable Attributes, Next: Blackfin Variable Attributes, Prev: Common Variable Attributes, Up: Variable Attributes 6.32.2 AVR Variable Attributes ------------------------------ ! `progmem' ! The `progmem' attribute is used on the AVR to place read-only data ! in the non-volatile program memory (flash). The `progmem' attribute accomplishes this by putting respective variables into a ! section whose name starts with `.progmem'. ! This attribute works similar to the `section' attribute but adds ! additional checking. Notice that just like the `section' ! attribute, `progmem' affects the location of the data but not how this data is accessed. ! In order to read data located with the `progmem' attribute ! (inline) assembler must be used. /* Use custom macros from AVR-LibC (http://nongnu.org/avr-libc/user-manual/) */ #include *************** File: gcc.info, Node: AVR Variable Attr *** 28908,28919 **** See also the *note AVR Named Address Spaces:: section for an alternate way to locate and access data in flash memory. ! 'io' ! 'io (ADDR)' ! Variables with the 'io' attribute are used to address memory-mapped ! peripherals in the io address range. If an address is specified, ! the variable is assigned that address, and the value is interpreted ! as an address in the data address space. Example: volatile int porta __attribute__((io (0x22))); --- 29117,29128 ---- See also the *note AVR Named Address Spaces:: section for an alternate way to locate and access data in flash memory. ! `io' ! `io (ADDR)' ! Variables with the `io' attribute are used to address ! memory-mapped peripherals in the io address range. If an address ! is specified, the variable is assigned that address, and the value ! is interpreted as an address in the data address space. Example: volatile int porta __attribute__((io (0x22))); *************** File: gcc.info, Node: AVR Variable Attr *** 28926,28945 **** extern volatile int porta __attribute__((io)); ! 'io_low' ! 'io_low (ADDR)' ! This is like the 'io' attribute, but additionally it informs the compiler that the object lies in the lower half of the I/O area, ! allowing the use of 'cbi', 'sbi', 'sbic' and 'sbis' instructions. ! 'address' ! 'address (ADDR)' ! Variables with the 'address' attribute are used to address memory-mapped peripherals that may lie outside the io address range. volatile int porta __attribute__((address (0x600)));  File: gcc.info, Node: Blackfin Variable Attributes, Next: H8/300 Variable Attributes, Prev: AVR Variable Attributes, Up: Variable Attributes --- 29135,29155 ---- extern volatile int porta __attribute__((io)); ! `io_low' ! `io_low (ADDR)' ! This is like the `io' attribute, but additionally it informs the compiler that the object lies in the lower half of the I/O area, ! allowing the use of `cbi', `sbi', `sbic' and `sbis' instructions. ! `address' ! `address (ADDR)' ! Variables with the `address' attribute are used to address memory-mapped peripherals that may lie outside the io address range. volatile int porta __attribute__((address (0x600))); +  File: gcc.info, Node: Blackfin Variable Attributes, Next: H8/300 Variable Attributes, Prev: AVR Variable Attributes, Up: Variable Attributes *************** File: gcc.info, Node: Blackfin Variable *** 28948,28967 **** Three attributes are currently defined for the Blackfin. ! 'l1_data' ! 'l1_data_A' ! 'l1_data_B' Use these attributes on the Blackfin to place the variable into L1 ! Data SRAM. Variables with 'l1_data' attribute are put into the ! specific section named '.l1.data'. Those with 'l1_data_A' ! attribute are put into the specific section named '.l1.data.A'. ! Those with 'l1_data_B' attribute are put into the specific section ! named '.l1.data.B'. ! 'l2' Use this attribute on the Blackfin to place the variable into L2 ! SRAM. Variables with 'l2' attribute are put into the specific ! section named '.l2.data'.  File: gcc.info, Node: H8/300 Variable Attributes, Next: IA-64 Variable Attributes, Prev: Blackfin Variable Attributes, Up: Variable Attributes --- 29158,29177 ---- Three attributes are currently defined for the Blackfin. ! `l1_data' ! `l1_data_A' ! `l1_data_B' Use these attributes on the Blackfin to place the variable into L1 ! Data SRAM. Variables with `l1_data' attribute are put into the ! specific section named `.l1.data'. Those with `l1_data_A' ! attribute are put into the specific section named `.l1.data.A'. ! Those with `l1_data_B' attribute are put into the specific section ! named `.l1.data.B'. ! `l2' Use this attribute on the Blackfin to place the variable into L2 ! SRAM. Variables with `l2' attribute are put into the specific ! section named `.l2.data'.  File: gcc.info, Node: H8/300 Variable Attributes, Next: IA-64 Variable Attributes, Prev: Blackfin Variable Attributes, Up: Variable Attributes *************** File: gcc.info, Node: H8/300 Variable A *** 28971,28993 **** These variable attributes are available for H8/300 targets: ! 'eightbit_data' ! Use this attribute on the H8/300, H8/300H, and H8S to indicate that ! the specified variable should be placed into the eight-bit data ! section. The compiler generates more efficient code for certain ! operations on data in the eight-bit data area. Note the eight-bit ! data area is limited to 256 bytes of data. You must use GAS and GLD from GNU binutils version 2.7 or later for this attribute to work correctly. ! 'tiny_data' Use this attribute on the H8/300H and H8S to indicate that the specified variable should be placed into the tiny data section. The compiler generates more efficient code for loads and stores on data in the tiny data section. Note the tiny data area is limited to slightly under 32KB of data.  File: gcc.info, Node: IA-64 Variable Attributes, Next: M32R/D Variable Attributes, Prev: H8/300 Variable Attributes, Up: Variable Attributes --- 29181,29204 ---- These variable attributes are available for H8/300 targets: ! `eightbit_data' ! Use this attribute on the H8/300, H8/300H, and H8S to indicate ! that the specified variable should be placed into the eight-bit ! data section. The compiler generates more efficient code for ! certain operations on data in the eight-bit data area. Note the ! eight-bit data area is limited to 256 bytes of data. You must use GAS and GLD from GNU binutils version 2.7 or later for this attribute to work correctly. ! `tiny_data' Use this attribute on the H8/300H and H8S to indicate that the specified variable should be placed into the tiny data section. The compiler generates more efficient code for loads and stores on data in the tiny data section. Note the tiny data area is limited to slightly under 32KB of data. +  File: gcc.info, Node: IA-64 Variable Attributes, Next: M32R/D Variable Attributes, Prev: H8/300 Variable Attributes, Up: Variable Attributes *************** File: gcc.info, Node: IA-64 Variable At *** 28996,29011 **** The IA-64 back end supports the following variable attribute: ! 'model (MODEL-NAME)' ! On IA-64, use this attribute to set the addressability of an object. At present, the only supported identifier for MODEL-NAME ! is 'small', indicating addressability via "small" (22-bit) ! addresses (so that their addresses can be loaded with the 'addl' instruction). Caveat: such addressing is by definition not position independent and hence this attribute must not be used for objects defined by shared libraries.  File: gcc.info, Node: M32R/D Variable Attributes, Next: MeP Variable Attributes, Prev: IA-64 Variable Attributes, Up: Variable Attributes --- 29207,29222 ---- The IA-64 back end supports the following variable attribute: ! `model (MODEL-NAME)' On IA-64, use this attribute to set the addressability of an object. At present, the only supported identifier for MODEL-NAME ! is `small', indicating addressability via "small" (22-bit) ! addresses (so that their addresses can be loaded with the `addl' instruction). Caveat: such addressing is by definition not position independent and hence this attribute must not be used for objects defined by shared libraries. +  File: gcc.info, Node: M32R/D Variable Attributes, Next: MeP Variable Attributes, Prev: IA-64 Variable Attributes, Up: Variable Attributes *************** File: gcc.info, Node: M32R/D Variable A *** 29014,29029 **** One attribute is currently defined for the M32R/D. ! 'model (MODEL-NAME)' Use this attribute on the M32R/D to set the addressability of an ! object. The identifier MODEL-NAME is one of 'small', 'medium', or ! 'large', representing each of the code models. Small model objects live in the lower 16MB of memory (so that their ! addresses can be loaded with the 'ld24' instruction). Medium and large model objects may live anywhere in the 32-bit ! address space (the compiler generates 'seth/add3' instructions to load their addresses).  --- 29225,29240 ---- One attribute is currently defined for the M32R/D. ! `model (MODEL-NAME)' Use this attribute on the M32R/D to set the addressability of an ! object. The identifier MODEL-NAME is one of `small', `medium', or ! `large', representing each of the code models. Small model objects live in the lower 16MB of memory (so that their ! addresses can be loaded with the `ld24' instruction). Medium and large model objects may live anywhere in the 32-bit ! address space (the compiler generates `seth/add3' instructions to load their addresses).  *************** File: gcc.info, Node: MeP Variable Attr *** 29032,29083 **** 6.32.7 MeP Variable Attributes ------------------------------ ! The MeP target has a number of addressing modes and busses. The 'near' space spans the standard memory space's first 16 megabytes (24 bits). ! The 'far' space spans the entire 32-bit memory space. The 'based' space ! is a 128-byte region in the memory space that is addressed relative to ! the '$tp' register. The 'tiny' space is a 65536-byte region relative to ! the '$gp' register. In addition to these memory regions, the MeP target ! has a separate 16-bit control bus which is specified with 'cb' ! attributes. ! 'based' ! Any variable with the 'based' attribute is assigned to the '.based' ! section, and is accessed with relative to the '$tp' register. ! 'tiny' ! Likewise, the 'tiny' attribute assigned variables to the '.tiny' ! section, relative to the '$gp' register. ! 'near' ! Variables with the 'near' attribute are assumed to have addresses that fit in a 24-bit addressing mode. This is the default for ! large variables ('-mtiny=4' is the default) but this attribute can ! override '-mtiny=' for small variables, or override '-ml'. ! 'far' ! Variables with the 'far' attribute are addressed using a full 32-bit address. Since this covers the entire memory space, this allows modules to make no assumptions about where variables might be stored. ! 'io' ! 'io (ADDR)' ! Variables with the 'io' attribute are used to address memory-mapped ! peripherals. If an address is specified, the variable is assigned ! that address, else it is not assigned an address (it is assumed ! some other module assigns an address). Example: int timer_count __attribute__((io(0x123))); ! 'cb' ! 'cb (ADDR)' ! Variables with the 'cb' attribute are used to access the control ! bus, using special instructions. 'addr' indicates the control bus address. Example: int cpu_clock __attribute__((cb(0x123)));  File: gcc.info, Node: Microsoft Windows Variable Attributes, Next: MSP430 Variable Attributes, Prev: MeP Variable Attributes, Up: Variable Attributes --- 29243,29297 ---- 6.32.7 MeP Variable Attributes ------------------------------ ! The MeP target has a number of addressing modes and busses. The `near' space spans the standard memory space's first 16 megabytes (24 bits). ! The `far' space spans the entire 32-bit memory space. The `based' ! space is a 128-byte region in the memory space that is addressed ! relative to the `$tp' register. The `tiny' space is a 65536-byte ! region relative to the `$gp' register. In addition to these memory ! regions, the MeP target has a separate 16-bit control bus which is ! specified with `cb' attributes. ! `based' ! Any variable with the `based' attribute is assigned to the ! `.based' section, and is accessed with relative to the `$tp' ! register. ! `tiny' ! Likewise, the `tiny' attribute assigned variables to the `.tiny' ! section, relative to the `$gp' register. ! `near' ! Variables with the `near' attribute are assumed to have addresses that fit in a 24-bit addressing mode. This is the default for ! large variables (`-mtiny=4' is the default) but this attribute can ! override `-mtiny=' for small variables, or override `-ml'. ! `far' ! Variables with the `far' attribute are addressed using a full 32-bit address. Since this covers the entire memory space, this allows modules to make no assumptions about where variables might be stored. ! `io' ! `io (ADDR)' ! Variables with the `io' attribute are used to address ! memory-mapped peripherals. If an address is specified, the ! variable is assigned that address, else it is not assigned an ! address (it is assumed some other module assigns an address). ! Example: int timer_count __attribute__((io(0x123))); ! `cb' ! `cb (ADDR)' ! Variables with the `cb' attribute are used to access the control ! bus, using special instructions. `addr' indicates the control bus address. Example: int cpu_clock __attribute__((cb(0x123))); +  File: gcc.info, Node: Microsoft Windows Variable Attributes, Next: MSP430 Variable Attributes, Prev: MeP Variable Attributes, Up: Variable Attributes *************** You can use these attributes on Microsof *** 29088,29100 **** Variable Attributes:: for additional Windows compatibility attributes available on all x86 targets. ! 'dllimport' ! 'dllexport' ! The 'dllimport' and 'dllexport' attributes are described in *note Microsoft Windows Function Attributes::. ! 'selectany' ! The 'selectany' attribute causes an initialized global variable to have link-once semantics. When multiple definitions of the variable are encountered by the linker, the first is selected and the remainder are discarded. Following usage by the Microsoft --- 29302,29314 ---- Variable Attributes:: for additional Windows compatibility attributes available on all x86 targets. ! `dllimport' ! `dllexport' ! The `dllimport' and `dllexport' attributes are described in *note Microsoft Windows Function Attributes::. ! `selectany' ! The `selectany' attribute causes an initialized global variable to have link-once semantics. When multiple definitions of the variable are encountered by the linker, the first is selected and the remainder are discarded. Following usage by the Microsoft *************** available on all x86 targets. *** 29109,29125 **** constructor and destructor are protected by a link-once guard variable. ! The 'selectany' attribute is only available on Microsoft Windows ! targets. You can use '__declspec (selectany)' as a synonym for ! '__attribute__ ((selectany))' for compatibility with other compilers. ! 'shared' On Microsoft Windows, in addition to putting variable definitions in a named section, the section can also be shared among all running copies of an executable or DLL. For example, this small program defines shared data by putting it in a named section ! 'shared' and marking the section shareable: int foo __attribute__((section ("shared"), shared)) = 0; --- 29323,29339 ---- constructor and destructor are protected by a link-once guard variable. ! The `selectany' attribute is only available on Microsoft Windows ! targets. You can use `__declspec (selectany)' as a synonym for ! `__attribute__ ((selectany))' for compatibility with other compilers. ! `shared' On Microsoft Windows, in addition to putting variable definitions in a named section, the section can also be shared among all running copies of an executable or DLL. For example, this small program defines shared data by putting it in a named section ! `shared' and marking the section shareable: int foo __attribute__((section ("shared"), shared)) = 0; *************** available on all x86 targets. *** 29131,29141 **** return 0; } ! You may only use the 'shared' attribute along with 'section' ! attribute with a fully-initialized global definition because of the ! way linkers work. See 'section' attribute for more information. - The 'shared' attribute is only available on Microsoft Windows.  File: gcc.info, Node: MSP430 Variable Attributes, Next: PowerPC Variable Attributes, Prev: Microsoft Windows Variable Attributes, Up: Variable Attributes --- 29345,29357 ---- return 0; } ! You may only use the `shared' attribute along with `section' ! attribute with a fully-initialized global definition because of ! the way linkers work. See `section' attribute for more ! information. ! ! The `shared' attribute is only available on Microsoft Windows.  File: gcc.info, Node: MSP430 Variable Attributes, Next: PowerPC Variable Attributes, Prev: Microsoft Windows Variable Attributes, Up: Variable Attributes *************** File: gcc.info, Node: MSP430 Variable A *** 29143,29166 **** 6.32.9 MSP430 Variable Attributes --------------------------------- ! 'noinit' ! Any data with the 'noinit' attribute will not be initialised by the ! C runtime startup code, or the program loader. Not initialising ! data in this way can reduce program startup times. ! 'persistent' ! Any variable with the 'persistent' attribute will not be initialised by the C runtime startup code. Instead its value will be set once, when the application is loaded, and then never initialised again, even if the processor is reset or the program ! restarts. Persistent data is intended to be placed into FLASH RAM, ! where its value will be retained across resets. The linker script ! being used to create the application should ensure that persistent ! data is correctly placed. ! 'lower' ! 'upper' ! 'either' These attributes are the same as the MSP430 function attributes of the same name (*note MSP430 Function Attributes::). These attributes can be applied to both functions and variables. --- 29359,29382 ---- 6.32.9 MSP430 Variable Attributes --------------------------------- ! `noinit' ! Any data with the `noinit' attribute will not be initialised by ! the C runtime startup code, or the program loader. Not ! initialising data in this way can reduce program startup times. ! `persistent' ! Any variable with the `persistent' attribute will not be initialised by the C runtime startup code. Instead its value will be set once, when the application is loaded, and then never initialised again, even if the processor is reset or the program ! restarts. Persistent data is intended to be placed into FLASH ! RAM, where its value will be retained across resets. The linker ! script being used to create the application should ensure that ! persistent data is correctly placed. ! `lower' ! `upper' ! `either' These attributes are the same as the MSP430 function attributes of the same name (*note MSP430 Function Attributes::). These attributes can be applied to both functions and variables. *************** File: gcc.info, Node: PowerPC Variable *** 29172,29183 **** ----------------------------------- Three attributes currently are defined for PowerPC configurations: ! 'altivec', 'ms_struct' and 'gcc_struct'. For full documentation of the struct attributes please see the documentation in *note x86 Variable Attributes::. ! For documentation of 'altivec' attribute please see the documentation in *note PowerPC Type Attributes::.  --- 29388,29399 ---- ----------------------------------- Three attributes currently are defined for PowerPC configurations: ! `altivec', `ms_struct' and `gcc_struct'. For full documentation of the struct attributes please see the documentation in *note x86 Variable Attributes::. ! For documentation of `altivec' attribute please see the documentation in *note PowerPC Type Attributes::.  *************** File: gcc.info, Node: RL78 Variable Att *** 29186,29192 **** 6.32.11 RL78 Variable Attributes -------------------------------- ! The RL78 back end supports the 'saddr' variable attribute. This specifies placement of the corresponding variable in the SADDR area, which can be accessed more efficiently than the default memory region. --- 29402,29408 ---- 6.32.11 RL78 Variable Attributes -------------------------------- ! The RL78 back end supports the `saddr' variable attribute. This specifies placement of the corresponding variable in the SADDR area, which can be accessed more efficiently than the default memory region. *************** File: gcc.info, Node: SPU Variable Attr *** 29196,29202 **** 6.32.12 SPU Variable Attributes ------------------------------- ! The SPU supports the 'spu_vector' attribute for variables. For documentation of this attribute please see the documentation in *note SPU Type Attributes::. --- 29412,29418 ---- 6.32.12 SPU Variable Attributes ------------------------------- ! The SPU supports the `spu_vector' attribute for variables. For documentation of this attribute please see the documentation in *note SPU Type Attributes::. *************** File: gcc.info, Node: V850 Variable Att *** 29208,29222 **** These variable attributes are supported by the V850 back end: ! 'sda' ! Use this attribute to explicitly place a variable in the small data ! area, which can hold up to 64 kilobytes. ! 'tda' Use this attribute to explicitly place a variable in the tiny data area, which can hold up to 256 bytes in total. ! 'zda' Use this attribute to explicitly place a variable in the first 32 kilobytes of memory. --- 29424,29438 ---- These variable attributes are supported by the V850 back end: ! `sda' ! Use this attribute to explicitly place a variable in the small ! data area, which can hold up to 64 kilobytes. ! `tda' Use this attribute to explicitly place a variable in the tiny data area, which can hold up to 256 bytes in total. ! `zda' Use this attribute to explicitly place a variable in the first 32 kilobytes of memory. *************** File: gcc.info, Node: x86 Variable Attr *** 29226,29249 **** 6.32.14 x86 Variable Attributes ------------------------------- ! Two attributes are currently defined for x86 configurations: 'ms_struct' ! and 'gcc_struct'. ! ! 'ms_struct' ! 'gcc_struct' ! If 'packed' is used on a structure, or if bit-fields are used, it may be that the Microsoft ABI lays out the structure differently than the way GCC normally does. Particularly when moving packed data between functions compiled with GCC and the native Microsoft ! compiler (either via function call or as data in a file), it may be ! necessary to access either format. - The 'ms_struct' and 'gcc_struct' attributes correspond to the - '-mms-bitfields' and '-mno-ms-bitfields' command-line options, - respectively; see *note x86 Options::, for details of how structure - layout is affected. *Note x86 Type Attributes::, for information - about the corresponding attributes on types.  File: gcc.info, Node: Xstormy16 Variable Attributes, Prev: x86 Variable Attributes, Up: Variable Attributes --- 29442,29465 ---- 6.32.14 x86 Variable Attributes ------------------------------- ! Two attributes are currently defined for x86 configurations: ! `ms_struct' and `gcc_struct'. ! `ms_struct' ! `gcc_struct' ! If `packed' is used on a structure, or if bit-fields are used, it may be that the Microsoft ABI lays out the structure differently than the way GCC normally does. Particularly when moving packed data between functions compiled with GCC and the native Microsoft ! compiler (either via function call or as data in a file), it may ! be necessary to access either format. ! ! The `ms_struct' and `gcc_struct' attributes correspond to the ! `-mms-bitfields' and `-mno-ms-bitfields' command-line options, ! respectively; see *note x86 Options::, for details of how ! structure layout is affected. *Note x86 Type Attributes::, for ! information about the corresponding attributes on types.  File: gcc.info, Node: Xstormy16 Variable Attributes, Prev: x86 Variable Attributes, Up: Variable Attributes *************** File: gcc.info, Node: Xstormy16 Variabl *** 29252,29265 **** ------------------------------------- One attribute is currently defined for xstormy16 configurations: ! 'below100'. ! ! 'below100' ! If a variable has the 'below100' attribute ('BELOW100' is allowed also), GCC places the variable in the first 0x100 bytes of memory ! and use special opcodes to access it. Such variables are placed in ! either the '.bss_below100' section or the '.data_below100' section.  File: gcc.info, Node: Type Attributes, Next: Label Attributes, Prev: Variable Attributes, Up: C Extensions --- 29468,29482 ---- ------------------------------------- One attribute is currently defined for xstormy16 configurations: ! `below100'. ! `below100' ! If a variable has the `below100' attribute (`BELOW100' is allowed also), GCC places the variable in the first 0x100 bytes of memory ! and use special opcodes to access it. Such variables are placed ! in either the `.bss_below100' section or the `.data_below100' ! section. !  File: gcc.info, Node: Type Attributes, Next: Label Attributes, Prev: Variable Attributes, Up: C Extensions *************** File: gcc.info, Node: Type Attributes, *** 29267,29290 **** 6.33 Specifying Attributes of Types =================================== ! The keyword '__attribute__' allows you to specify special attributes of ! types. Some type attributes apply only to 'struct' and 'union' types, ! while others can apply to any type defined via a 'typedef' declaration. Other attributes are defined for functions (*note Function Attributes::), labels (*note Label Attributes::), enumerators (*note Enumerator Attributes::), and for variables (*note Variable Attributes::). ! The '__attribute__' keyword is followed by an attribute specification inside double parentheses. You may specify type attributes in an enum, struct or union type declaration or definition by placing them immediately after the ! 'struct', 'union' or 'enum' keyword. A less preferred syntax is to place them just past the closing curly brace of the definition. ! You can also include type attributes in a 'typedef' declaration. *Note ! Attribute Syntax::, for details of the exact syntax for using attributes. * Menu: --- 29484,29507 ---- 6.33 Specifying Attributes of Types =================================== ! The keyword `__attribute__' allows you to specify special attributes of ! types. Some type attributes apply only to `struct' and `union' types, ! while others can apply to any type defined via a `typedef' declaration. Other attributes are defined for functions (*note Function Attributes::), labels (*note Label Attributes::), enumerators (*note Enumerator Attributes::), and for variables (*note Variable Attributes::). ! The `__attribute__' keyword is followed by an attribute specification inside double parentheses. You may specify type attributes in an enum, struct or union type declaration or definition by placing them immediately after the ! `struct', `union' or `enum' keyword. A less preferred syntax is to place them just past the closing curly brace of the definition. ! You can also include type attributes in a `typedef' declaration. ! *Note Attribute Syntax::, for details of the exact syntax for using attributes. * Menu: *************** File: gcc.info, Node: Common Type Attri *** 29304,29310 **** The following type attributes are supported on most targets. ! 'aligned (ALIGNMENT)' This attribute specifies a minimum alignment (in bytes) for variables of the specified type. For example, the declarations: --- 29521,29527 ---- The following type attributes are supported on most targets. ! `aligned (ALIGNMENT)' This attribute specifies a minimum alignment (in bytes) for variables of the specified type. For example, the declarations: *************** The following type attributes are suppor *** 29312,29385 **** typedef int more_aligned_int __attribute__ ((aligned (8))); force the compiler to ensure (as far as it can) that each variable ! whose type is 'struct S' or 'more_aligned_int' is allocated and aligned _at least_ on a 8-byte boundary. On a SPARC, having all ! variables of type 'struct S' aligned to 8-byte boundaries allows ! the compiler to use the 'ldd' and 'std' (doubleword load and store) ! instructions when copying one variable of type 'struct S' to another, thus improving run-time efficiency. ! Note that the alignment of any given 'struct' or 'union' type is required by the ISO C standard to be at least a perfect multiple of the lowest common multiple of the alignments of all of the members ! of the 'struct' or 'union' in question. This means that you _can_ ! effectively adjust the alignment of a 'struct' or 'union' type by ! attaching an 'aligned' attribute to any one of the members of such ! a type, but the notation illustrated in the example above is a more ! obvious, intuitive, and readable way to request the compiler to ! adjust the alignment of an entire 'struct' or 'union' type. As in the preceding example, you can explicitly specify the alignment (in bytes) that you wish the compiler to use for a given ! 'struct' or 'union' type. Alternatively, you can leave out the alignment factor and just ask the compiler to align a type to the maximum useful alignment for the target machine you are compiling for. For example, you could write: struct S { short f[3]; } __attribute__ ((aligned)); ! Whenever you leave out the alignment factor in an 'aligned' attribute specification, the compiler automatically sets the alignment for the type to the largest alignment that is ever used for any data type on the target machine you are compiling for. Doing this can often make copy operations more efficient, because the compiler can use whatever instructions copy the biggest chunks ! of memory when performing copies to or from the variables that have ! types that you have aligned this way. ! In the example above, if the size of each 'short' is 2 bytes, then ! the size of the entire 'struct S' type is 6 bytes. The smallest power of two that is greater than or equal to that is 8, so the ! compiler sets the alignment for the entire 'struct S' type to 8 bytes. Note that although you can ask the compiler to select a time-efficient alignment for a given type and then declare only ! individual stand-alone objects of that type, the compiler's ability ! to select a time-efficient alignment is primarily useful only when ! you plan to create arrays of variables having the relevant ! (efficiently aligned) type. If you declare or use arrays of ! variables of an efficiently-aligned type, then it is likely that ! your program also does pointer arithmetic (or subscripting, which ! amounts to the same thing) on pointers to the relevant type, and ! the code that the compiler generates for these pointer arithmetic ! operations is often more efficient for efficiently-aligned types ! than for other types. ! Note that the effectiveness of 'aligned' attributes may be limited by inherent limitations in your linker. On many systems, the linker is only able to arrange for variables to be aligned up to a certain maximum alignment. (For some linkers, the maximum supported alignment may be very very small.) If your linker is only able to align variables up to a maximum of 8-byte alignment, ! then specifying 'aligned(16)' in an '__attribute__' still only provides you with 8-byte alignment. See your linker documentation for further information. ! The 'aligned' attribute can only increase alignment. Alignment can ! be decreased by specifying the 'packed' attribute. See below. ! 'bnd_variable_size' When applied to a structure field, this attribute tells Pointer Bounds Checker that the size of this field should not be computed using static type information. It may be used to mark --- 29529,29602 ---- typedef int more_aligned_int __attribute__ ((aligned (8))); force the compiler to ensure (as far as it can) that each variable ! whose type is `struct S' or `more_aligned_int' is allocated and aligned _at least_ on a 8-byte boundary. On a SPARC, having all ! variables of type `struct S' aligned to 8-byte boundaries allows ! the compiler to use the `ldd' and `std' (doubleword load and ! store) instructions when copying one variable of type `struct S' to another, thus improving run-time efficiency. ! Note that the alignment of any given `struct' or `union' type is required by the ISO C standard to be at least a perfect multiple of the lowest common multiple of the alignments of all of the members ! of the `struct' or `union' in question. This means that you _can_ ! effectively adjust the alignment of a `struct' or `union' type by ! attaching an `aligned' attribute to any one of the members of such ! a type, but the notation illustrated in the example above is a ! more obvious, intuitive, and readable way to request the compiler ! to adjust the alignment of an entire `struct' or `union' type. As in the preceding example, you can explicitly specify the alignment (in bytes) that you wish the compiler to use for a given ! `struct' or `union' type. Alternatively, you can leave out the alignment factor and just ask the compiler to align a type to the maximum useful alignment for the target machine you are compiling for. For example, you could write: struct S { short f[3]; } __attribute__ ((aligned)); ! Whenever you leave out the alignment factor in an `aligned' attribute specification, the compiler automatically sets the alignment for the type to the largest alignment that is ever used for any data type on the target machine you are compiling for. Doing this can often make copy operations more efficient, because the compiler can use whatever instructions copy the biggest chunks ! of memory when performing copies to or from the variables that ! have types that you have aligned this way. ! In the example above, if the size of each `short' is 2 bytes, then ! the size of the entire `struct S' type is 6 bytes. The smallest power of two that is greater than or equal to that is 8, so the ! compiler sets the alignment for the entire `struct S' type to 8 bytes. Note that although you can ask the compiler to select a time-efficient alignment for a given type and then declare only ! individual stand-alone objects of that type, the compiler's ! ability to select a time-efficient alignment is primarily useful ! only when you plan to create arrays of variables having the ! relevant (efficiently aligned) type. If you declare or use arrays ! of variables of an efficiently-aligned type, then it is likely ! that your program also does pointer arithmetic (or subscripting, ! which amounts to the same thing) on pointers to the relevant type, ! and the code that the compiler generates for these pointer ! arithmetic operations is often more efficient for ! efficiently-aligned types than for other types. ! Note that the effectiveness of `aligned' attributes may be limited by inherent limitations in your linker. On many systems, the linker is only able to arrange for variables to be aligned up to a certain maximum alignment. (For some linkers, the maximum supported alignment may be very very small.) If your linker is only able to align variables up to a maximum of 8-byte alignment, ! then specifying `aligned(16)' in an `__attribute__' still only provides you with 8-byte alignment. See your linker documentation for further information. ! The `aligned' attribute can only increase alignment. Alignment ! can be decreased by specifying the `packed' attribute. See below. ! `bnd_variable_size' When applied to a structure field, this attribute tells Pointer Bounds Checker that the size of this field should not be computed using static type information. It may be used to mark *************** The following type attributes are suppor *** 29405,29421 **** S *p = (S *)malloc (sizeof(S) + 100); p->data[10] = 0; //OK ! 'deprecated' ! 'deprecated (MSG)' ! The 'deprecated' attribute results in a warning if the type is used ! anywhere in the source file. This is useful when identifying types ! that are expected to be removed in a future version of a program. ! If possible, the warning also includes the location of the ! declaration of the deprecated type, to enable users to easily find ! further information about why the type is deprecated, or what they ! should do instead. Note that the warnings only occur for uses and ! then only if the type is being applied to an identifier that itself ! is not being declared as deprecated. typedef int T1 __attribute__ ((deprecated)); T1 x; --- 29622,29638 ---- S *p = (S *)malloc (sizeof(S) + 100); p->data[10] = 0; //OK ! `deprecated' ! `deprecated (MSG)' ! The `deprecated' attribute results in a warning if the type is ! used anywhere in the source file. This is useful when identifying ! types that are expected to be removed in a future version of a ! program. If possible, the warning also includes the location of ! the declaration of the deprecated type, to enable users to easily ! find further information about why the type is deprecated, or what ! they should do instead. Note that the warnings only occur for ! uses and then only if the type is being applied to an identifier ! that itself is not being declared as deprecated. typedef int T1 __attribute__ ((deprecated)); T1 x; *************** The following type attributes are suppor *** 29430,29457 **** deprecated. Similarly for line 6. The optional MSG argument, which must be a string, is printed in the warning if present. ! The 'deprecated' attribute can also be used for functions and variables (*note Function Attributes::, *note Variable Attributes::.) ! 'designated_init' This attribute may only be applied to structure types. It indicates that any initialization of an object of this type must use designated initializers rather than positional initializers. ! The intent of this attribute is to allow the programmer to indicate ! that a structure's layout may change, and that therefore relying on ! positional initialization will result in future breakage. GCC emits warnings based on this attribute by default; use ! '-Wno-designated-init' to suppress them. ! 'may_alias' Accesses through pointers to types with this attribute are not ! subject to type-based alias analysis, but are instead assumed to be ! able to alias any other type of objects. In the context of section ! 6.5 paragraph 7 of the C99 standard, an lvalue expression dereferencing such a pointer is treated like having a character ! type. See '-fstrict-aliasing' for more information on aliasing issues. This extension exists to support some vector APIs, in which pointers to one vector type are permitted to alias pointers to a different vector type. --- 29647,29675 ---- deprecated. Similarly for line 6. The optional MSG argument, which must be a string, is printed in the warning if present. ! The `deprecated' attribute can also be used for functions and variables (*note Function Attributes::, *note Variable Attributes::.) ! `designated_init' This attribute may only be applied to structure types. It indicates that any initialization of an object of this type must use designated initializers rather than positional initializers. ! The intent of this attribute is to allow the programmer to ! indicate that a structure's layout may change, and that therefore ! relying on positional initialization will result in future ! breakage. GCC emits warnings based on this attribute by default; use ! `-Wno-designated-init' to suppress them. ! `may_alias' Accesses through pointers to types with this attribute are not ! subject to type-based alias analysis, but are instead assumed to ! be able to alias any other type of objects. In the context of ! section 6.5 paragraph 7 of the C99 standard, an lvalue expression dereferencing such a pointer is treated like having a character ! type. See `-fstrict-aliasing' for more information on aliasing issues. This extension exists to support some vector APIs, in which pointers to one vector type are permitted to alias pointers to a different vector type. *************** The following type attributes are suppor *** 29477,29502 **** exit(0); } ! If you replaced 'short_a' with 'short' in the variable declaration, ! the above program would abort when compiled with ! '-fstrict-aliasing', which is on by default at '-O2' or above. ! 'packed' ! This attribute, attached to 'struct' or 'union' type definition, specifies that each member (other than zero-width bit-fields) of the structure or union is placed to minimize the memory required. ! When attached to an 'enum' definition, it indicates that the smallest integral type should be used. ! Specifying the 'packed' attribute for 'struct' and 'union' types is ! equivalent to specifying the 'packed' attribute on each of the ! structure or union members. Specifying the '-fshort-enums' flag on ! the command line is equivalent to specifying the 'packed' attribute ! on all 'enum' definitions. ! In the following example 'struct my_packed_struct''s members are ! packed closely together, but the internal layout of its 's' member ! is not packed--to do that, 'struct my_unpacked_struct' needs to be packed too. struct my_unpacked_struct --- 29695,29720 ---- exit(0); } ! If you replaced `short_a' with `short' in the variable ! declaration, the above program would abort when compiled with ! `-fstrict-aliasing', which is on by default at `-O2' or above. ! `packed' ! This attribute, attached to `struct' or `union' type definition, specifies that each member (other than zero-width bit-fields) of the structure or union is placed to minimize the memory required. ! When attached to an `enum' definition, it indicates that the smallest integral type should be used. ! Specifying the `packed' attribute for `struct' and `union' types ! is equivalent to specifying the `packed' attribute on each of the ! structure or union members. Specifying the `-fshort-enums' flag ! on the command line is equivalent to specifying the `packed' ! attribute on all `enum' definitions. ! In the following example `struct my_packed_struct''s members are ! packed closely together, but the internal layout of its `s' member ! is not packed--to do that, `struct my_unpacked_struct' needs to be packed too. struct my_unpacked_struct *************** The following type attributes are suppor *** 29512,29528 **** struct my_unpacked_struct s; }; ! You may only specify the 'packed' attribute attribute on the ! definition of an 'enum', 'struct' or 'union', not on a 'typedef' that does not also define the enumerated type, structure or union. ! 'scalar_storage_order ("ENDIANNESS")' ! When attached to a 'union' or a 'struct', this attribute sets the storage order, aka endianness, of the scalar fields of the type, as well as the array fields whose component is scalar. The supported ! endiannesses are 'big-endian' and 'little-endian'. The attribute ! has no effects on fields which are themselves a 'union', a 'struct' ! or an array whose component is a 'union' or a 'struct', and it is possible for these fields to have a different scalar storage order than the enclosing type. --- 29730,29746 ---- struct my_unpacked_struct s; }; ! You may only specify the `packed' attribute attribute on the ! definition of an `enum', `struct' or `union', not on a `typedef' that does not also define the enumerated type, structure or union. ! `scalar_storage_order ("ENDIANNESS")' ! When attached to a `union' or a `struct', this attribute sets the storage order, aka endianness, of the scalar fields of the type, as well as the array fields whose component is scalar. The supported ! endiannesses are `big-endian' and `little-endian'. The attribute ! has no effects on fields which are themselves a `union', a `struct' ! or an array whose component is a `union' or a `struct', and it is possible for these fields to have a different scalar storage order than the enclosing type. *************** The following type attributes are suppor *** 29532,29548 **** little-endian. Additional restrictions are enforced for types with the reverse ! scalar storage order with regard to the scalar storage order of the ! target: ! * Taking the address of a scalar field of a 'union' or a ! 'struct' with reverse scalar storage order is not permitted and yields an error. * Taking the address of an array field, whose component is ! scalar, of a 'union' or a 'struct' with reverse scalar storage ! order is permitted but yields a warning, unless ! '-Wno-scalar-storage-order' is specified. ! * Taking the address of a 'union' or a 'struct' with reverse scalar storage order is permitted. These restrictions exist because the storage order attribute is --- 29750,29768 ---- little-endian. Additional restrictions are enforced for types with the reverse ! scalar storage order with regard to the scalar storage order of ! the target: ! * Taking the address of a scalar field of a `union' or a ! `struct' with reverse scalar storage order is not permitted and yields an error. + * Taking the address of an array field, whose component is ! scalar, of a `union' or a `struct' with reverse scalar ! storage order is permitted but yields a warning, unless ! `-Wno-scalar-storage-order' is specified. ! ! * Taking the address of a `union' or a `struct' with reverse scalar storage order is permitted. These restrictions exist because the storage order attribute is *************** The following type attributes are suppor *** 29551,29564 **** address generally does not work. The second case is nevertheless allowed to be able to perform a block copy from or to the array. ! Moreover, the use of type punning or aliasing to toggle the storage ! order is not supported; that is to say, a given scalar object ! cannot be accessed through distinct types that assign a different ! storage order to it. ! ! 'transparent_union' ! This attribute, attached to a 'union' type definition, indicates that any function parameter having that union type causes calls to that function to be treated in a special way. --- 29771,29783 ---- address generally does not work. The second case is nevertheless allowed to be able to perform a block copy from or to the array. ! Moreover, the use of type punning or aliasing to toggle the ! storage order is not supported; that is to say, a given scalar ! object cannot be accessed through distinct types that assign a ! different storage order to it. ! `transparent_union' ! This attribute, attached to a `union' type definition, indicates that any function parameter having that union type causes calls to that function to be treated in a special way. *************** The following type attributes are suppor *** 29568,29574 **** null pointer constant or a void pointer expression; and if the union contains a void pointer type, the corresponding argument can be any pointer expression. If the union member type is a pointer, ! qualifiers like 'const' on the referenced type must be respected, just as with normal pointer conversions. Second, the argument is passed to the function using the calling --- 29787,29793 ---- null pointer constant or a void pointer expression; and if the union contains a void pointer type, the corresponding argument can be any pointer expression. If the union member type is a pointer, ! qualifiers like `const' on the referenced type must be respected, just as with normal pointer conversions. Second, the argument is passed to the function using the calling *************** The following type attributes are suppor *** 29579,29591 **** Transparent unions are designed for library functions that have multiple interfaces for compatibility reasons. For example, ! suppose the 'wait' function must accept either a value of type 'int ! *' to comply with POSIX, or a value of type 'union wait *' to ! comply with the 4.1BSD interface. If 'wait''s parameter were 'void ! *', 'wait' would accept both kinds of arguments, but it would also ! accept any other pointer type and this would make argument type ! checking less useful. Instead, '' might define the ! interface as follows: typedef union __attribute__ ((__transparent_union__)) { --- 29798,29810 ---- Transparent unions are designed for library functions that have multiple interfaces for compatibility reasons. For example, ! suppose the `wait' function must accept either a value of type ! `int *' to comply with POSIX, or a value of type `union wait *' to ! comply with the 4.1BSD interface. If `wait''s parameter were ! `void *', `wait' would accept both kinds of arguments, but it ! would also accept any other pointer type and this would make ! argument type checking less useful. Instead, `' might ! define the interface as follows: typedef union __attribute__ ((__transparent_union__)) { *************** The following type attributes are suppor *** 29595,29616 **** pid_t wait (wait_status_ptr_t); ! This interface allows either 'int *' or 'union wait *' arguments to ! be passed, using the 'int *' calling convention. The program can ! call 'wait' with arguments of either type: int w1 () { int w; return wait (&w); } int w2 () { union wait w; return wait (&w); } ! With this interface, 'wait''s implementation might look like this: pid_t wait (wait_status_ptr_t p) { return waitpid (-1, p.__ip, 0); } ! 'unused' ! When attached to a type (including a 'union' or a 'struct'), this attribute means that variables of that type are meant to appear possibly unused. GCC does not produce a warning for any variables of that type, even if the variable appears to do nothing. This is --- 29814,29835 ---- pid_t wait (wait_status_ptr_t); ! This interface allows either `int *' or `union wait *' arguments ! to be passed, using the `int *' calling convention. The program ! can call `wait' with arguments of either type: int w1 () { int w; return wait (&w); } int w2 () { union wait w; return wait (&w); } ! With this interface, `wait''s implementation might look like this: pid_t wait (wait_status_ptr_t p) { return waitpid (-1, p.__ip, 0); } ! `unused' ! When attached to a type (including a `union' or a `struct'), this attribute means that variables of that type are meant to appear possibly unused. GCC does not produce a warning for any variables of that type, even if the variable appears to do nothing. This is *************** The following type attributes are suppor *** 29618,29639 **** defined and then not referenced, but contain constructors and destructors that have nontrivial bookkeeping functions. ! 'visibility' ! In C++, attribute visibility (*note Function Attributes::) can also ! be applied to class, struct, union and enum types. Unlike other ! type attributes, the attribute must appear between the initial ! keyword and the name of the type; it cannot appear after the body ! of the type. Note that the type visibility is applied to vague linkage entities associated with the class (vtable, typeinfo node, etc.). In particular, if a class is thrown as an exception in one shared object and caught in another, the class must have default ! visibility. Otherwise the two shared objects are unable to use the ! same typeinfo node and exception handling will break. To specify multiple attributes, separate them by commas within the ! double parentheses: for example, '__attribute__ ((aligned (16), packed))'.  --- 29837,29859 ---- defined and then not referenced, but contain constructors and destructors that have nontrivial bookkeeping functions. ! `visibility' ! In C++, attribute visibility (*note Function Attributes::) can ! also be applied to class, struct, union and enum types. Unlike ! other type attributes, the attribute must appear between the ! initial keyword and the name of the type; it cannot appear after ! the body of the type. Note that the type visibility is applied to vague linkage entities associated with the class (vtable, typeinfo node, etc.). In particular, if a class is thrown as an exception in one shared object and caught in another, the class must have default ! visibility. Otherwise the two shared objects are unable to use ! the same typeinfo node and exception handling will break. ! To specify multiple attributes, separate them by commas within the ! double parentheses: for example, `__attribute__ ((aligned (16), packed))'.  *************** File: gcc.info, Node: ARM Type Attribut *** 29642,29651 **** 6.33.2 ARM Type Attributes -------------------------- ! On those ARM targets that support 'dllimport' (such as Symbian OS), you ! can use the 'notshared' attribute to indicate that the virtual table and ! other similar data for a class should not be exported from a DLL. For ! example: class __declspec(notshared) C { public: --- 29862,29871 ---- 6.33.2 ARM Type Attributes -------------------------- ! On those ARM targets that support `dllimport' (such as Symbian OS), you ! can use the `notshared' attribute to indicate that the virtual table ! and other similar data for a class should not be exported from a DLL. ! For example: class __declspec(notshared) C { public: *************** example: *** 29656,29664 **** __declspec(dllexport) C::C() {} ! In this code, 'C::C' is exported from the current DLL, but the virtual ! table for 'C' is not exported. (You can use '__attribute__' instead of ! '__declspec' if you prefer, but most Symbian OS code uses '__declspec'.)  File: gcc.info, Node: MeP Type Attributes, Next: PowerPC Type Attributes, Prev: ARM Type Attributes, Up: Type Attributes --- 29876,29884 ---- __declspec(dllexport) C::C() {} ! In this code, `C::C' is exported from the current DLL, but the virtual ! table for `C' is not exported. (You can use `__attribute__' instead of ! `__declspec' if you prefer, but most Symbian OS code uses `__declspec'.)  File: gcc.info, Node: MeP Type Attributes, Next: PowerPC Type Attributes, Prev: ARM Type Attributes, Up: Type Attributes *************** File: gcc.info, Node: MeP Type Attribut *** 29667,29674 **** -------------------------- Many of the MeP variable attributes may be applied to types as well. ! Specifically, the 'based', 'tiny', 'near', and 'far' attributes may be ! applied to either. The 'io' and 'cb' attributes may not be applied to types.  --- 29887,29894 ---- -------------------------- Many of the MeP variable attributes may be applied to types as well. ! Specifically, the `based', `tiny', `near', and `far' attributes may be ! applied to either. The `io' and `cb' attributes may not be applied to types.  *************** File: gcc.info, Node: PowerPC Type Attr *** 29678,29700 **** ------------------------------ Three attributes currently are defined for PowerPC configurations: ! 'altivec', 'ms_struct' and 'gcc_struct'. ! For full documentation of the 'ms_struct' and 'gcc_struct' attributes please see the documentation in *note x86 Type Attributes::. ! The 'altivec' attribute allows one to declare AltiVec vector data types ! supported by the AltiVec Programming Interface Manual. The attribute ! requires an argument to specify one of three vector types: 'vector__', ! 'pixel__' (always followed by unsigned short), and 'bool__' (always ! followed by unsigned). __attribute__((altivec(vector__))) __attribute__((altivec(pixel__))) unsigned short __attribute__((altivec(bool__))) unsigned ! These attributes mainly are intended to support the '__vector', ! '__pixel', and '__bool' AltiVec keywords.  File: gcc.info, Node: SPU Type Attributes, Next: x86 Type Attributes, Prev: PowerPC Type Attributes, Up: Type Attributes --- 29898,29920 ---- ------------------------------ Three attributes currently are defined for PowerPC configurations: ! `altivec', `ms_struct' and `gcc_struct'. ! For full documentation of the `ms_struct' and `gcc_struct' attributes please see the documentation in *note x86 Type Attributes::. ! The `altivec' attribute allows one to declare AltiVec vector data ! types supported by the AltiVec Programming Interface Manual. The ! attribute requires an argument to specify one of three vector types: ! `vector__', `pixel__' (always followed by unsigned short), and `bool__' ! (always followed by unsigned). __attribute__((altivec(vector__))) __attribute__((altivec(pixel__))) unsigned short __attribute__((altivec(bool__))) unsigned ! These attributes mainly are intended to support the `__vector', ! `__pixel', and `__bool' AltiVec keywords.  File: gcc.info, Node: SPU Type Attributes, Next: x86 Type Attributes, Prev: PowerPC Type Attributes, Up: Type Attributes *************** File: gcc.info, Node: SPU Type Attribut *** 29702,29711 **** 6.33.5 SPU Type Attributes -------------------------- ! The SPU supports the 'spu_vector' attribute for types. This attribute allows one to declare vector data types supported by the Sony/Toshiba/IBM SPU Language Extensions Specification. It is intended ! to support the '__vector' keyword.  File: gcc.info, Node: x86 Type Attributes, Prev: SPU Type Attributes, Up: Type Attributes --- 29922,29931 ---- 6.33.5 SPU Type Attributes -------------------------- ! The SPU supports the `spu_vector' attribute for types. This attribute allows one to declare vector data types supported by the Sony/Toshiba/IBM SPU Language Extensions Specification. It is intended ! to support the `__vector' keyword.  File: gcc.info, Node: x86 Type Attributes, Prev: SPU Type Attributes, Up: Type Attributes *************** File: gcc.info, Node: x86 Type Attribut *** 29713,29736 **** 6.33.6 x86 Type Attributes -------------------------- ! Two attributes are currently defined for x86 configurations: 'ms_struct' ! and 'gcc_struct'. ! ! 'ms_struct' ! 'gcc_struct' ! If 'packed' is used on a structure, or if bit-fields are used it may be that the Microsoft ABI packs them differently than GCC normally packs them. Particularly when moving packed data between functions compiled with GCC and the native Microsoft compiler (either via function call or as data in a file), it may be necessary to access either format. ! The 'ms_struct' and 'gcc_struct' attributes correspond to the ! '-mms-bitfields' and '-mno-ms-bitfields' command-line options, ! respectively; see *note x86 Options::, for details of how structure ! layout is affected. *Note x86 Variable Attributes::, for ! information about the corresponding attributes on variables.  File: gcc.info, Node: Label Attributes, Next: Enumerator Attributes, Prev: Type Attributes, Up: C Extensions --- 29933,29956 ---- 6.33.6 x86 Type Attributes -------------------------- ! Two attributes are currently defined for x86 configurations: ! `ms_struct' and `gcc_struct'. ! `ms_struct' ! `gcc_struct' ! If `packed' is used on a structure, or if bit-fields are used it may be that the Microsoft ABI packs them differently than GCC normally packs them. Particularly when moving packed data between functions compiled with GCC and the native Microsoft compiler (either via function call or as data in a file), it may be necessary to access either format. ! The `ms_struct' and `gcc_struct' attributes correspond to the ! `-mms-bitfields' and `-mno-ms-bitfields' command-line options, ! respectively; see *note x86 Options::, for details of how ! structure layout is affected. *Note x86 Variable Attributes::, ! for information about the corresponding attributes on variables. !  File: gcc.info, Node: Label Attributes, Next: Enumerator Attributes, Prev: Type Attributes, Up: C Extensions *************** are available for functions (*note Funct *** 29744,29752 **** (*note Variable Attributes::), enumerators (*note Enumerator Attributes::), and for types (*note Type Attributes::). ! This example uses the 'cold' label attribute to indicate the ! 'ErrorHandling' branch is unlikely to be taken and that the ! 'ErrorHandling' label is unused: asm goto ("some asm" : : : : NoError); --- 29964,29972 ---- (*note Variable Attributes::), enumerators (*note Enumerator Attributes::), and for types (*note Type Attributes::). ! This example uses the `cold' label attribute to indicate the ! `ErrorHandling' branch is unlikely to be taken and that the ! `ErrorHandling' label is unused: asm goto ("some asm" : : : : NoError); *************** Attributes::), and for types (*note Type *** 29761,29785 **** printf("no error\n"); return 1; ! 'unused' This feature is intended for program-generated code that may ! contain unused labels, but which is compiled with '-Wall'. It is not normally appropriate to use in it human-written code, though it could be useful in cases where the code that jumps to the label is ! contained within an '#ifdef' conditional. ! 'hot' ! The 'hot' attribute on a label is used to inform the compiler that ! the path following the label is more likely than paths that are not ! so annotated. This attribute is used in cases where ! '__builtin_expect' cannot be used, for instance with computed goto ! or 'asm goto'. ! 'cold' ! The 'cold' attribute on labels is used to inform the compiler that the path following the label is unlikely to be executed. This ! attribute is used in cases where '__builtin_expect' cannot be used, ! for instance with computed goto or 'asm goto'.  File: gcc.info, Node: Enumerator Attributes, Next: Attribute Syntax, Prev: Label Attributes, Up: C Extensions --- 29981,30006 ---- printf("no error\n"); return 1; ! `unused' This feature is intended for program-generated code that may ! contain unused labels, but which is compiled with `-Wall'. It is not normally appropriate to use in it human-written code, though it could be useful in cases where the code that jumps to the label is ! contained within an `#ifdef' conditional. ! `hot' ! The `hot' attribute on a label is used to inform the compiler that ! the path following the label is more likely than paths that are ! not so annotated. This attribute is used in cases where ! `__builtin_expect' cannot be used, for instance with computed goto ! or `asm goto'. ! `cold' ! The `cold' attribute on labels is used to inform the compiler that the path following the label is unlikely to be executed. This ! attribute is used in cases where `__builtin_expect' cannot be ! used, for instance with computed goto or `asm goto'. !  File: gcc.info, Node: Enumerator Attributes, Next: Attribute Syntax, Prev: Label Attributes, Up: C Extensions *************** attributes are available for functions ( *** 29793,29800 **** variables (*note Variable Attributes::), labels (*note Label Attributes::), and for types (*note Type Attributes::). ! This example uses the 'deprecated' enumerator attribute to indicate the ! 'oldval' enumerator is deprecated: enum E { oldval __attribute__((deprecated)), --- 30014,30021 ---- variables (*note Variable Attributes::), labels (*note Label Attributes::), and for types (*note Type Attributes::). ! This example uses the `deprecated' enumerator attribute to indicate the ! `oldval' enumerator is deprecated: enum E { oldval __attribute__((deprecated)), *************** Attributes::), and for types (*note Type *** 29807,29821 **** return oldval; } ! 'deprecated' ! The 'deprecated' attribute results in a warning if the enumerator is used anywhere in the source file. This is useful when ! identifying enumerators that are expected to be removed in a future ! version of a program. The warning also includes the location of ! the declaration of the deprecated enumerator, to enable users to ! easily find further information about why the enumerator is ! deprecated, or what they should do instead. Note that the warnings ! only occurs for uses.  File: gcc.info, Node: Attribute Syntax, Next: Function Prototypes, Prev: Enumerator Attributes, Up: C Extensions --- 30028,30043 ---- return oldval; } ! `deprecated' ! The `deprecated' attribute results in a warning if the enumerator is used anywhere in the source file. This is useful when ! identifying enumerators that are expected to be removed in a ! future version of a program. The warning also includes the ! location of the declaration of the deprecated enumerator, to ! enable users to easily find further information about why the ! enumerator is deprecated, or what they should do instead. Note ! that the warnings only occurs for uses. !  File: gcc.info, Node: Attribute Syntax, Next: Function Prototypes, Prev: Enumerator Attributes, Up: C Extensions *************** File: gcc.info, Node: Attribute Syntax, *** 29823,29829 **** 6.36 Attribute Syntax ===================== ! This section describes the syntax with which '__attribute__' may be used, and the constructs to which attribute specifiers bind, for the C language. Some details may vary for C++ and Objective-C. Because of infelicities in the grammar for attributes, some forms described here --- 30045,30051 ---- 6.36 Attribute Syntax ===================== ! This section describes the syntax with which `__attribute__' may be used, and the constructs to which attribute specifiers bind, for the C language. Some details may vary for C++ and Objective-C. Because of infelicities in the grammar for attributes, some forms described here *************** may not be successfully parsed in all ca *** 29832,29839 **** There are some problems with the semantics of attributes in C++. For example, there are no manglings for attributes, although they may affect code generation, so problems may arise when attributed types are used in ! conjunction with templates or overloading. Similarly, 'typeid' does not ! distinguish between types with different attributes. Support for attributes in C++ may be restricted in future to attributes on declarations only, but not on nested declarators. --- 30054,30061 ---- There are some problems with the semantics of attributes in C++. For example, there are no manglings for attributes, although they may affect code generation, so problems may arise when attributed types are used in ! conjunction with templates or overloading. Similarly, `typeid' does ! not distinguish between types with different attributes. Support for attributes in C++ may be restricted in future to attributes on declarations only, but not on nested declarators. *************** semantics of attributes applying to labe *** 29846,29912 **** Attributes::, for details of the semantics of attributes applying to enumerators. ! An "attribute specifier" is of the form '__attribute__ ((ATTRIBUTE-LIST))'. An "attribute list" is a possibly empty ! comma-separated sequence of "attributes", where each attribute is one of ! the following: * Empty. Empty attributes are ignored. ! * An attribute name (which may be an identifier such as 'unused', or ! a reserved word such as 'const'). * An attribute name followed by a parenthesized list of parameters for the attribute. These parameters take one of the following forms: ! * An identifier. For example, 'mode' attributes use this form. * An identifier followed by a comma and a non-empty ! comma-separated list of expressions. For example, 'format' attributes use this form. * A possibly empty comma-separated list of expressions. For ! example, 'format_arg' attributes use this form with the list ! being a single integer constant expression, and 'alias' attributes use this form with the list being a single string constant. An "attribute specifier list" is a sequence of one or more attribute specifiers, not separated by any other tokens. ! You may optionally specify attribute names with '__' preceding and following the name. This allows you to use them in header files without being concerned about a possible macro of the same name. For example, ! you may use the attribute name '__noreturn__' instead of 'noreturn'. Label Attributes ................ In GNU C, an attribute specifier list may appear after the colon ! following a label, other than a 'case' or 'default' label. GNU C++ only ! permits attributes on labels if the attribute specifier is immediately ! followed by a semicolon (i.e., the label applies to an empty statement). ! If the semicolon is missing, C++ label attributes are ambiguous, as it ! is permissible for a declaration, which could begin with an attribute ! list, to be labelled in C++. Declarations cannot be labelled in C90 or ! C99, so the ambiguity does not arise there. Enumerator Attributes ..................... In GNU C, an attribute specifier list may appear as part of an enumerator. The attribute goes after the enumeration constant, before ! '=', if present. The optional attribute in the enumerator appertains to ! the enumeration constant. It is not possible to place the attribute after the constant expression, if present. Type Attributes ............... ! An attribute specifier list may appear as part of a 'struct', 'union' or ! 'enum' specifier. It may go either immediately after the 'struct', ! 'union' or 'enum' keyword, or after the closing brace. The former syntax is preferred. Where attribute specifiers follow the closing brace, they are considered to relate to the structure, union or enumerated type defined, not to any enclosing declaration the type --- 30068,30134 ---- Attributes::, for details of the semantics of attributes applying to enumerators. ! An "attribute specifier" is of the form `__attribute__ ((ATTRIBUTE-LIST))'. An "attribute list" is a possibly empty ! comma-separated sequence of "attributes", where each attribute is one ! of the following: * Empty. Empty attributes are ignored. ! * An attribute name (which may be an identifier such as `unused', or ! a reserved word such as `const'). * An attribute name followed by a parenthesized list of parameters for the attribute. These parameters take one of the following forms: ! * An identifier. For example, `mode' attributes use this form. * An identifier followed by a comma and a non-empty ! comma-separated list of expressions. For example, `format' attributes use this form. * A possibly empty comma-separated list of expressions. For ! example, `format_arg' attributes use this form with the list ! being a single integer constant expression, and `alias' attributes use this form with the list being a single string constant. An "attribute specifier list" is a sequence of one or more attribute specifiers, not separated by any other tokens. ! You may optionally specify attribute names with `__' preceding and following the name. This allows you to use them in header files without being concerned about a possible macro of the same name. For example, ! you may use the attribute name `__noreturn__' instead of `noreturn'. Label Attributes ................ In GNU C, an attribute specifier list may appear after the colon ! following a label, other than a `case' or `default' label. GNU C++ ! only permits attributes on labels if the attribute specifier is ! immediately followed by a semicolon (i.e., the label applies to an empty ! statement). If the semicolon is missing, C++ label attributes are ! ambiguous, as it is permissible for a declaration, which could begin ! with an attribute list, to be labelled in C++. Declarations cannot be ! labelled in C90 or C99, so the ambiguity does not arise there. Enumerator Attributes ..................... In GNU C, an attribute specifier list may appear as part of an enumerator. The attribute goes after the enumeration constant, before ! `=', if present. The optional attribute in the enumerator appertains ! to the enumeration constant. It is not possible to place the attribute after the constant expression, if present. Type Attributes ............... ! An attribute specifier list may appear as part of a `struct', `union' ! or `enum' specifier. It may go either immediately after the `struct', ! `union' or `enum' keyword, or after the closing brace. The former syntax is preferred. Where attribute specifiers follow the closing brace, they are considered to relate to the structure, union or enumerated type defined, not to any enclosing declaration the type *************** contain attribute specifiers, whether or *** 29931,29950 **** context contain storage class specifiers. (Some attributes, however, are essentially in the nature of storage class specifiers, and only make sense where storage class specifiers may be used; for example, ! 'section'.) There is one necessary limitation to this syntax: the first ! old-style parameter declaration in a function definition cannot begin ! with an attribute specifier, because such an attribute applies to the ! function instead by syntax described below (which, however, is not yet ! implemented in this case). In some other cases, attribute specifiers ! are permitted by this grammar but not yet supported by the compiler. ! All attribute specifiers in this place relate to the declaration as a ! whole. In the obsolescent usage where a type of 'int' is implied by the ! absence of type specifiers, such a list of specifiers and qualifiers may ! be an attribute specifier list with no other specifiers or qualifiers. At present, the first parameter in a function prototype must have some type specifier that is not an attribute specifier; this resolves an ! ambiguity in the interpretation of 'void f(int (__attribute__((foo)) x))', but is subject to change. At present, if the parentheses of a function declarator contain only attributes then those attributes are ignored, rather than yielding an error or warning or implying a single --- 30153,30173 ---- context contain storage class specifiers. (Some attributes, however, are essentially in the nature of storage class specifiers, and only make sense where storage class specifiers may be used; for example, ! `section'.) There is one necessary limitation to this syntax: the ! first old-style parameter declaration in a function definition cannot ! begin with an attribute specifier, because such an attribute applies to ! the function instead by syntax described below (which, however, is not ! yet implemented in this case). In some other cases, attribute ! specifiers are permitted by this grammar but not yet supported by the ! compiler. All attribute specifiers in this place relate to the ! declaration as a whole. In the obsolescent usage where a type of `int' ! is implied by the absence of type specifiers, such a list of specifiers ! and qualifiers may be an attribute specifier list with no other ! specifiers or qualifiers. At present, the first parameter in a function prototype must have some type specifier that is not an attribute specifier; this resolves an ! ambiguity in the interpretation of `void f(int (__attribute__((foo)) x))', but is subject to change. At present, if the parentheses of a function declarator contain only attributes then those attributes are ignored, rather than yielding an error or warning or implying a single *************** identifier before whose declarator they *** 29960,29981 **** __attribute__((format(printf, 1, 2))) d1 (const char *, ...), d2 (void); ! the 'noreturn' attribute applies to all the functions declared; the ! 'format' attribute only applies to 'd1'. An attribute specifier list may appear immediately before the comma, ! '=' or semicolon terminating the declaration of an identifier other than ! a function definition. Such attribute specifiers apply to the declared ! object or function. Where an assembler name for an object or function ! is specified (*note Asm Labels::), the attribute must follow the 'asm' ! specification. An attribute specifier list may, in future, be permitted to appear after the declarator in a function definition (before any old-style parameter declarations or the function body). Attribute specifiers may be mixed with type qualifiers appearing inside ! the '[]' of a parameter array declarator, in the C99 construct by which such qualifiers are applied to the pointer to which the array is implicitly converted. Such attribute specifiers apply to the pointer, not to the array, but at present this is not implemented and they are --- 30183,30204 ---- __attribute__((format(printf, 1, 2))) d1 (const char *, ...), d2 (void); ! the `noreturn' attribute applies to all the functions declared; the ! `format' attribute only applies to `d1'. An attribute specifier list may appear immediately before the comma, ! `=' or semicolon terminating the declaration of an identifier other ! than a function definition. Such attribute specifiers apply to the ! declared object or function. Where an assembler name for an object or ! function is specified (*note Asm Labels::), the attribute must follow ! the `asm' specification. An attribute specifier list may, in future, be permitted to appear after the declarator in a function definition (before any old-style parameter declarations or the function body). Attribute specifiers may be mixed with type qualifiers appearing inside ! the `[]' of a parameter array declarator, in the C99 construct by which such qualifiers are applied to the pointer to which the array is implicitly converted. Such attribute specifiers apply to the pointer, not to the array, but at present this is not implemented and they are *************** ignored. *** 29985,30011 **** declarator. At present, there are some limitations in this usage: the attributes correctly apply to the declarator, but for most individual attributes the semantics this implies are not implemented. When ! attribute specifiers follow the '*' of a pointer declarator, they may be ! mixed with any type qualifiers present. The following describes the formal semantics of this syntax. It makes the most sense if you are familiar with the formal specification of declarators in the ISO C standard. ! Consider (as in C99 subclause 6.7.5 paragraph 4) a declaration 'T D1', ! where 'T' contains declaration specifiers that specify a type TYPE (such ! as 'int') and 'D1' is a declarator that contains an identifier IDENT. ! The type specified for IDENT for derived declarators whose type does not ! include an attribute specifier is as in the ISO C standard. ! If 'D1' has the form '( ATTRIBUTE-SPECIFIER-LIST D )', and the ! declaration 'T D' specifies the type "DERIVED-DECLARATOR-TYPE-LIST TYPE" ! for IDENT, then 'T D1' specifies the type "DERIVED-DECLARATOR-TYPE-LIST ! ATTRIBUTE-SPECIFIER-LIST TYPE" for IDENT. ! If 'D1' has the form '* TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST D', ! and the declaration 'T D' specifies the type ! "DERIVED-DECLARATOR-TYPE-LIST TYPE" for IDENT, then 'T D1' specifies the ! type "DERIVED-DECLARATOR-TYPE-LIST TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST pointer to TYPE" for IDENT. For example, --- 30208,30234 ---- declarator. At present, there are some limitations in this usage: the attributes correctly apply to the declarator, but for most individual attributes the semantics this implies are not implemented. When ! attribute specifiers follow the `*' of a pointer declarator, they may ! be mixed with any type qualifiers present. The following describes the formal semantics of this syntax. It makes the most sense if you are familiar with the formal specification of declarators in the ISO C standard. ! Consider (as in C99 subclause 6.7.5 paragraph 4) a declaration `T D1', ! where `T' contains declaration specifiers that specify a type TYPE ! (such as `int') and `D1' is a declarator that contains an identifier ! IDENT. The type specified for IDENT for derived declarators whose type ! does not include an attribute specifier is as in the ISO C standard. ! If `D1' has the form `( ATTRIBUTE-SPECIFIER-LIST D )', and the ! declaration `T D' specifies the type "DERIVED-DECLARATOR-TYPE-LIST ! TYPE" for IDENT, then `T D1' specifies the type ! "DERIVED-DECLARATOR-TYPE-LIST ATTRIBUTE-SPECIFIER-LIST TYPE" for IDENT. ! If `D1' has the form `* TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST ! D', and the declaration `T D' specifies the type ! "DERIVED-DECLARATOR-TYPE-LIST TYPE" for IDENT, then `T D1' specifies ! the type "DERIVED-DECLARATOR-TYPE-LIST TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST pointer to TYPE" for IDENT. For example, *************** TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-L *** 30013,30025 **** void (__attribute__((noreturn)) ****f) (void); specifies the type "pointer to pointer to pointer to pointer to ! non-returning function returning 'void'". As another example, char *__attribute__((aligned(8))) *f; ! specifies the type "pointer to 8-byte-aligned pointer to 'char'". Note again that this does not work with most attributes; for example, the ! usage of 'aligned' and 'noreturn' attributes given above is not yet supported. For compatibility with existing code written for compiler versions that --- 30236,30248 ---- void (__attribute__((noreturn)) ****f) (void); specifies the type "pointer to pointer to pointer to pointer to ! non-returning function returning `void'". As another example, char *__attribute__((aligned(8))) *f; ! specifies the type "pointer to 8-byte-aligned pointer to `char'". Note again that this does not work with most attributes; for example, the ! usage of `aligned' and `noreturn' attributes given above is not yet supported. For compatibility with existing code written for compiler versions that *************** the attributes immediately before the id *** 30033,30040 **** attribute applied to a function return type is treated as applying to the function type, and such an attribute applied to an array element type is treated as applying to the array type. If an attribute that ! only applies to function types is applied to a pointer-to-function type, ! it is treated as applying to the pointer target type; if such an attribute is applied to a function return type that is not a pointer-to-function type, it is treated as applying to the function type. --- 30256,30263 ---- attribute applied to a function return type is treated as applying to the function type, and such an attribute applied to an array element type is treated as applying to the array type. If an attribute that ! only applies to function types is applied to a pointer-to-function ! type, it is treated as applying to the pointer target type; if such an attribute is applied to a function return type that is not a pointer-to-function type, it is treated as applying to the function type. *************** old-style non-prototype definition. Con *** 30066,30085 **** return x == 0; } ! Suppose the type 'uid_t' happens to be 'short'. ISO C does not allow this example, because subword arguments in old-style non-prototype definitions are promoted. Therefore in this example the function ! definition's argument is really an 'int', which does not match the ! prototype argument type of 'short'. This restriction of ISO C makes it hard to write code that is portable ! to traditional C compilers, because the programmer does not know whether ! the 'uid_t' type is 'short', 'int', or 'long'. Therefore, in cases like ! these GNU C allows a prototype to override a later old-style definition. ! More precisely, in GNU C, a function prototype argument type overrides ! the argument type specified by a later old-style definition if the ! former type is the same as the latter type before promotion. Thus in ! GNU C the above example is equivalent to the following: int isroot (uid_t); --- 30289,30309 ---- return x == 0; } ! Suppose the type `uid_t' happens to be `short'. ISO C does not allow this example, because subword arguments in old-style non-prototype definitions are promoted. Therefore in this example the function ! definition's argument is really an `int', which does not match the ! prototype argument type of `short'. This restriction of ISO C makes it hard to write code that is portable ! to traditional C compilers, because the programmer does not know ! whether the `uid_t' type is `short', `int', or `long'. Therefore, in ! cases like these GNU C allows a prototype to override a later old-style ! definition. More precisely, in GNU C, a function prototype argument ! type overrides the argument type specified by a later old-style ! definition if the former type is the same as the latter type before ! promotion. Thus in GNU C the above example is equivalent to the ! following: int isroot (uid_t); *************** File: gcc.info, Node: C++ Comments, Ne *** 30098,30109 **** 6.38 C++ Style Comments ======================= ! In GNU C, you may use C++ style comments, which start with '//' and continue until the end of the line. Many other C implementations allow such comments, and they are included in the 1999 C standard. However, ! C++ style comments are not recognized if you specify an '-std' option ! specifying a version of ISO C before C99, or '-ansi' (equivalent to ! '-std=c90').  File: gcc.info, Node: Dollar Signs, Next: Character Escapes, Prev: C++ Comments, Up: C Extensions --- 30322,30333 ---- 6.38 C++ Style Comments ======================= ! In GNU C, you may use C++ style comments, which start with `//' and continue until the end of the line. Many other C implementations allow such comments, and they are included in the 1999 C standard. However, ! C++ style comments are not recognized if you specify an `-std' option ! specifying a version of ISO C before C99, or `-ansi' (equivalent to ! `-std=c90').  File: gcc.info, Node: Dollar Signs, Next: Character Escapes, Prev: C++ Comments, Up: C Extensions *************** File: gcc.info, Node: Character Escapes *** 30122,30129 **** 6.40 The Character in Constants ===================================== ! You can use the sequence '\e' in a string or character constant to stand ! for the ASCII character .  File: gcc.info, Node: Alignment, Next: Inline, Prev: Character Escapes, Up: C Extensions --- 30346,30353 ---- 6.40 The Character in Constants ===================================== ! You can use the sequence `\e' in a string or character constant to ! stand for the ASCII character .  File: gcc.info, Node: Alignment, Next: Inline, Prev: Character Escapes, Up: C Extensions *************** File: gcc.info, Node: Alignment, Next: *** 30131,30159 **** 6.41 Inquiring on Alignment of Types or Variables ================================================= ! The keyword '__alignof__' allows you to inquire about how an object is aligned, or the minimum alignment usually required by a type. Its ! syntax is just like 'sizeof'. ! For example, if the target machine requires a 'double' value to be ! aligned on an 8-byte boundary, then '__alignof__ (double)' is 8. This is true on many RISC machines. On more traditional machine designs, ! '__alignof__ (double)' is 4 or even 2. ! Some machines never actually require alignment; they allow reference to ! any data type even at an odd address. For these machines, '__alignof__' ! reports the smallest alignment that GCC gives the data type, usually as ! mandated by the target ABI. ! If the operand of '__alignof__' is an lvalue rather than a type, its value is the required alignment for its type, taking into account any ! minimum alignment specified with GCC's '__attribute__' extension (*note Variable Attributes::). For example, after this declaration: struct foo { int x; char y; } foo1; ! the value of '__alignof__ (foo1.y)' is 1, even though its actual ! alignment is probably 2 or 4, the same as '__alignof__ (int)'. It is an error to ask for the alignment of an incomplete type. --- 30355,30383 ---- 6.41 Inquiring on Alignment of Types or Variables ================================================= ! The keyword `__alignof__' allows you to inquire about how an object is aligned, or the minimum alignment usually required by a type. Its ! syntax is just like `sizeof'. ! For example, if the target machine requires a `double' value to be ! aligned on an 8-byte boundary, then `__alignof__ (double)' is 8. This is true on many RISC machines. On more traditional machine designs, ! `__alignof__ (double)' is 4 or even 2. ! Some machines never actually require alignment; they allow reference ! to any data type even at an odd address. For these machines, ! `__alignof__' reports the smallest alignment that GCC gives the data ! type, usually as mandated by the target ABI. ! If the operand of `__alignof__' is an lvalue rather than a type, its value is the required alignment for its type, taking into account any ! minimum alignment specified with GCC's `__attribute__' extension (*note Variable Attributes::). For example, after this declaration: struct foo { int x; char y; } foo1; ! the value of `__alignof__ (foo1.y)' is 1, even though its actual ! alignment is probably 2 or 4, the same as `__alignof__ (int)'. It is an error to ask for the alignment of an incomplete type. *************** File: gcc.info, Node: Inline, Next: Vo *** 30163,30187 **** 6.42 An Inline Function is As Fast As a Macro ============================================= ! By declaring a function inline, you can direct GCC to make calls to that ! function faster. One way GCC can achieve this is to integrate that ! function's code into the code for its callers. This makes execution ! faster by eliminating the function-call overhead; in addition, if any of ! the actual argument values are constant, their known values may permit ! simplifications at compile time so that not all of the inline function's ! code needs to be included. The effect on code size is less predictable; ! object code may be larger or smaller with function inlining, depending ! on the particular case. You can also direct GCC to try to integrate all ! "simple enough" functions into their callers with the option ! '-finline-functions'. GCC implements three different semantics of declaring a function ! inline. One is available with '-std=gnu89' or '-fgnu89-inline' or when ! 'gnu_inline' attribute is present on all inline declarations, another ! when '-std=c99', '-std=c11', '-std=gnu99' or '-std=gnu11' (without ! '-fgnu89-inline'), and the third is used when compiling C++. ! To declare a function inline, use the 'inline' keyword in its declaration, like this: static inline int --- 30387,30411 ---- 6.42 An Inline Function is As Fast As a Macro ============================================= ! By declaring a function inline, you can direct GCC to make calls to ! that function faster. One way GCC can achieve this is to integrate ! that function's code into the code for its callers. This makes ! execution faster by eliminating the function-call overhead; in ! addition, if any of the actual argument values are constant, their ! known values may permit simplifications at compile time so that not all ! of the inline function's code needs to be included. The effect on code ! size is less predictable; object code may be larger or smaller with ! function inlining, depending on the particular case. You can also ! direct GCC to try to integrate all "simple enough" functions into their ! callers with the option `-finline-functions'. GCC implements three different semantics of declaring a function ! inline. One is available with `-std=gnu89' or `-fgnu89-inline' or when ! `gnu_inline' attribute is present on all inline declarations, another ! when `-std=c99', `-std=c11', `-std=gnu99' or `-std=gnu11' (without ! `-fgnu89-inline'), and the third is used when compiling C++. ! To declare a function inline, use the `inline' keyword in its declaration, like this: static inline int *************** declaration, like this: *** 30191,30202 **** } If you are writing a header file to be included in ISO C90 programs, ! write '__inline__' instead of 'inline'. *Note Alternate Keywords::. The three types of inlining behave similarly in two important cases: ! when the 'inline' keyword is used on a 'static' function, like the example above, and when a function is first declared without using the ! 'inline' keyword and then is defined with 'inline', like this: extern int inc (int *a); inline int --- 30415,30426 ---- } If you are writing a header file to be included in ISO C90 programs, ! write `__inline__' instead of `inline'. *Note Alternate Keywords::. The three types of inlining behave similarly in two important cases: ! when the `inline' keyword is used on a `static' function, like the example above, and when a function is first declared without using the ! `inline' keyword and then is defined with `inline', like this: extern int inc (int *a); inline int *************** example above, and when a function is fi *** 30206,30263 **** } In both of these common cases, the program behaves the same as if you ! had not used the 'inline' keyword, except for its speed. ! When a function is both inline and 'static', if all calls to the function are integrated into the caller, and the function's address is never used, then the function's own assembler code is never referenced. In this case, GCC does not actually output assembler code for the ! function, unless you specify the option '-fkeep-inline-functions'. If there is a nonintegrated call, then the function is compiled to assembler code as usual. The function must also be compiled as usual if the program refers to its address, because that can't be inlined. Note that certain usages in a function definition can make it unsuitable for inline substitution. Among these usages are: variadic ! functions, use of 'alloca', use of computed goto (*note Labels as Values::), use of nonlocal goto, use of nested functions, use of ! 'setjmp', use of '__builtin_longjmp' and use of '__builtin_return' or ! '__builtin_apply_args'. Using '-Winline' warns when a function marked ! 'inline' could not be substituted, and gives the reason for the failure. As required by ISO C++, GCC considers member functions defined within the body of a class to be marked inline even if they are not explicitly ! declared with the 'inline' keyword. You can override this with ! '-fno-default-inline'; *note Options Controlling C++ Dialect: C++ Dialect Options. GCC does not inline any functions when not optimizing unless you ! specify the 'always_inline' attribute for the function, like this: /* Prototype. */ inline void foo (const char) __attribute__((always_inline)); The remainder of this section is specific to GNU C90 inlining. ! When an inline function is not 'static', then the compiler must assume that there may be calls from other source files; since a global symbol can be defined only once in any program, the function must not be defined in the other source files, so the calls therein cannot be ! integrated. Therefore, a non-'static' inline function is always compiled on its own in the usual fashion. ! If you specify both 'inline' and 'extern' in the function definition, then the definition is used only for inlining. In no case is the function compiled on its own, not even if you refer to its address explicitly. Such an address becomes an external reference, as if you had only declared the function, and had not defined it. ! This combination of 'inline' and 'extern' has almost the effect of a macro. The way to use it is to put a function definition in a header file with these keywords, and put another copy of the definition ! (lacking 'inline' and 'extern') in a library file. The definition in ! the header file causes most calls to the function to be inlined. If any ! uses of the function remain, they refer to the single copy in the library.  --- 30430,30487 ---- } In both of these common cases, the program behaves the same as if you ! had not used the `inline' keyword, except for its speed. ! When a function is both inline and `static', if all calls to the function are integrated into the caller, and the function's address is never used, then the function's own assembler code is never referenced. In this case, GCC does not actually output assembler code for the ! function, unless you specify the option `-fkeep-inline-functions'. If there is a nonintegrated call, then the function is compiled to assembler code as usual. The function must also be compiled as usual if the program refers to its address, because that can't be inlined. Note that certain usages in a function definition can make it unsuitable for inline substitution. Among these usages are: variadic ! functions, use of `alloca', use of computed goto (*note Labels as Values::), use of nonlocal goto, use of nested functions, use of ! `setjmp', use of `__builtin_longjmp' and use of `__builtin_return' or ! `__builtin_apply_args'. Using `-Winline' warns when a function marked ! `inline' could not be substituted, and gives the reason for the failure. As required by ISO C++, GCC considers member functions defined within the body of a class to be marked inline even if they are not explicitly ! declared with the `inline' keyword. You can override this with ! `-fno-default-inline'; *note Options Controlling C++ Dialect: C++ Dialect Options. GCC does not inline any functions when not optimizing unless you ! specify the `always_inline' attribute for the function, like this: /* Prototype. */ inline void foo (const char) __attribute__((always_inline)); The remainder of this section is specific to GNU C90 inlining. ! When an inline function is not `static', then the compiler must assume that there may be calls from other source files; since a global symbol can be defined only once in any program, the function must not be defined in the other source files, so the calls therein cannot be ! integrated. Therefore, a non-`static' inline function is always compiled on its own in the usual fashion. ! If you specify both `inline' and `extern' in the function definition, then the definition is used only for inlining. In no case is the function compiled on its own, not even if you refer to its address explicitly. Such an address becomes an external reference, as if you had only declared the function, and had not defined it. ! This combination of `inline' and `extern' has almost the effect of a macro. The way to use it is to put a function definition in a header file with these keywords, and put another copy of the definition ! (lacking `inline' and `extern') in a library file. The definition in ! the header file causes most calls to the function to be inlined. If ! any uses of the function remain, they refer to the single copy in the library.  *************** allow you to violate the restriction on *** 30280,30296 **** between two sequence points. Accesses to non-volatile objects are not ordered with respect to ! volatile accesses. You cannot use a volatile object as a memory barrier ! to order a sequence of writes to non-volatile memory. For instance: int *ptr = SOMETHING; volatile int vobj; *ptr = SOMETHING; vobj = 1; ! Unless *PTR and VOBJ can be aliased, it is not guaranteed that the write ! to *PTR occurs by the time the update of VOBJ happens. If you need this ! guarantee, you must use a stronger memory barrier such as: int *ptr = SOMETHING; volatile int vobj; --- 30504,30521 ---- between two sequence points. Accesses to non-volatile objects are not ordered with respect to ! volatile accesses. You cannot use a volatile object as a memory ! barrier to order a sequence of writes to non-volatile memory. For ! instance: int *ptr = SOMETHING; volatile int vobj; *ptr = SOMETHING; vobj = 1; ! Unless *PTR and VOBJ can be aliased, it is not guaranteed that the ! write to *PTR occurs by the time the update of VOBJ happens. If you ! need this guarantee, you must use a stronger memory barrier such as: int *ptr = SOMETHING; volatile int vobj; *************** volatile object being pointed to. *** 30308,30316 **** Assignments are also expressions and have an rvalue. However when assigning to a scalar volatile, the volatile object is not reread, ! regardless of whether the assignment expression's rvalue is used or not. ! If the assignment's rvalue is used, the value is that assigned to the ! volatile object. For instance, there is no read of VOBJ in all the following cases: int obj; --- 30533,30541 ---- Assignments are also expressions and have an rvalue. However when assigning to a scalar volatile, the volatile object is not reread, ! regardless of whether the assignment expression's rvalue is used or ! not. If the assignment's rvalue is used, the value is that assigned to ! the volatile object. For instance, there is no read of VOBJ in all the following cases: int obj; *************** File: gcc.info, Node: Using Assembly La *** 30337,30362 **** 6.44 How to Use Inline Assembly Language in C Code ================================================== ! The 'asm' keyword allows you to embed assembler instructions within C ! code. GCC provides two forms of inline 'asm' statements. A "basic ! 'asm'" statement is one with no operands (*note Basic Asm::), while an ! "extended 'asm'" statement (*note Extended Asm::) includes one or more operands. The extended form is preferred for mixing C and assembly language within a function, but to include assembly language at top ! level you must use basic 'asm'. ! You can also use the 'asm' keyword to override the assembler name for a ! C symbol, or to place a C variable in a specific register. * Menu: * Basic Asm:: Inline assembler without operands. * Extended Asm:: Inline assembler with operands. ! * Constraints:: Constraints for 'asm' operands * Asm Labels:: Specifying the assembler name to use for a C symbol. * Explicit Register Variables:: Defining variables residing in specified registers. ! * Size of an asm:: How GCC calculates the size of an 'asm' block.  File: gcc.info, Node: Basic Asm, Next: Extended Asm, Up: Using Assembly Language with C --- 30562,30587 ---- 6.44 How to Use Inline Assembly Language in C Code ================================================== ! The `asm' keyword allows you to embed assembler instructions within C ! code. GCC provides two forms of inline `asm' statements. A "basic ! `asm'" statement is one with no operands (*note Basic Asm::), while an ! "extended `asm'" statement (*note Extended Asm::) includes one or more operands. The extended form is preferred for mixing C and assembly language within a function, but to include assembly language at top ! level you must use basic `asm'. ! You can also use the `asm' keyword to override the assembler name for ! a C symbol, or to place a C variable in a specific register. * Menu: * Basic Asm:: Inline assembler without operands. * Extended Asm:: Inline assembler with operands. ! * Constraints:: Constraints for `asm' operands * Asm Labels:: Specifying the assembler name to use for a C symbol. * Explicit Register Variables:: Defining variables residing in specified registers. ! * Size of an asm:: How GCC calculates the size of an `asm' block.  File: gcc.info, Node: Basic Asm, Next: Extended Asm, Up: Using Assembly Language with C *************** File: gcc.info, Node: Basic Asm, Next: *** 30364,30471 **** 6.44.1 Basic Asm -- Assembler Instructions Without Operands ----------------------------------------------------------- ! A basic 'asm' statement has the following syntax: asm [ volatile ] ( ASSEMBLERINSTRUCTIONS ) ! The 'asm' keyword is a GNU extension. When writing code that can be ! compiled with '-ansi' and the various '-std' options, use '__asm__' ! instead of 'asm' (*note Alternate Keywords::). Qualifiers .......... ! 'volatile' ! The optional 'volatile' qualifier has no effect. All basic 'asm' blocks are implicitly volatile. Parameters .......... ASSEMBLERINSTRUCTIONS ! This is a literal string that specifies the assembler code. The string can contain any instructions recognized by the assembler, including directives. GCC does not parse the assembler instructions themselves and does not know what they mean or even whether they are valid assembler input. You may place multiple assembler instructions together in a single ! 'asm' string, separated by the characters normally used in assembly ! code for the system. A combination that works in most places is a ! newline to break the line, plus a tab character (written as ! '\n\t'). Some assemblers allow semicolons as a line separator. ! However, note that some assembler dialects use semicolons to start ! a comment. Remarks ....... ! Using extended 'asm' (*note Extended Asm::) typically produces smaller, safer, and more efficient code, and in most cases it is a better ! solution than basic 'asm'. However, there are two situations where only ! basic 'asm' can be used: ! * Extended 'asm' statements have to be inside a C function, so to ! write inline assembly language at file scope ("top-level"), outside ! of C functions, you must use basic 'asm'. You can use this ! technique to emit assembler directives, define assembly language ! macros that can be invoked elsewhere in the file, or write entire ! functions in assembly language. ! * Functions declared with the 'naked' attribute also require basic ! 'asm' (*note Function Attributes::). ! Safely accessing C data and calling functions from basic 'asm' is more ! complex than it may appear. To access C data, it is better to use ! extended 'asm'. ! Do not expect a sequence of 'asm' statements to remain perfectly ! consecutive after compilation. If certain instructions need to remain ! consecutive in the output, put them in a single multi-instruction 'asm' ! statement. Note that GCC's optimizers can move 'asm' statements relative to other code, including across jumps. ! 'asm' statements may not perform jumps into other 'asm' statements. GCC does not know about these jumps, and therefore cannot take account ! of them when deciding how to optimize. Jumps from 'asm' to C labels are ! only supported in extended 'asm'. Under certain circumstances, GCC may duplicate (or remove duplicates ! of) your assembly code when optimizing. This can lead to unexpected ! duplicate symbol errors during compilation if your assembly code defines ! symbols or labels. ! *Warning:* The C standards do not specify semantics for 'asm', making it a potential source of incompatibilities between compilers. These incompatibilities may not produce compiler warnings/errors. ! GCC does not parse basic 'asm''s ASSEMBLERINSTRUCTIONS, which means there is no way to communicate to the compiler what is happening inside ! them. GCC has no visibility of symbols in the 'asm' and may discard them as unreferenced. It also does not know about side effects of the assembler code, such as modifications to memory or registers. Unlike some compilers, GCC assumes that no changes to either memory or registers occur. This assumption may change in a future release. To avoid complications from future changes to the semantics and the ! compatibility issues between compilers, consider replacing basic 'asm' ! with extended 'asm'. See How to convert from basic asm to extended asm (https://gcc.gnu.org/wiki/ConvertBasicAsmToExtended) for information about how to perform this conversion. ! The compiler copies the assembler instructions in a basic 'asm' verbatim to the assembly language output file, without processing ! dialects or any of the '%' operators that are available with extended ! 'asm'. This results in minor differences between basic 'asm' strings ! and extended 'asm' templates. For example, to refer to registers you ! might use '%eax' in basic 'asm' and '%%eax' in extended 'asm'. On targets such as x86 that support multiple assembler dialects, all ! basic 'asm' blocks use the assembler dialect specified by the '-masm' ! command-line option (*note x86 Options::). Basic 'asm' provides no mechanism to provide different assembler strings for different dialects. ! Here is an example of basic 'asm' for i386: /* Note that this code will not compile with -masm=intel */ #define DebugBreak() asm("int $3") --- 30589,30696 ---- 6.44.1 Basic Asm -- Assembler Instructions Without Operands ----------------------------------------------------------- ! A basic `asm' statement has the following syntax: asm [ volatile ] ( ASSEMBLERINSTRUCTIONS ) ! The `asm' keyword is a GNU extension. When writing code that can be ! compiled with `-ansi' and the various `-std' options, use `__asm__' ! instead of `asm' (*note Alternate Keywords::). Qualifiers .......... ! `volatile' ! The optional `volatile' qualifier has no effect. All basic `asm' blocks are implicitly volatile. Parameters .......... ASSEMBLERINSTRUCTIONS ! This is a literal string that specifies the assembler code. The string can contain any instructions recognized by the assembler, including directives. GCC does not parse the assembler instructions themselves and does not know what they mean or even whether they are valid assembler input. You may place multiple assembler instructions together in a single ! `asm' string, separated by the characters normally used in ! assembly code for the system. A combination that works in most ! places is a newline to break the line, plus a tab character ! (written as `\n\t'). Some assemblers allow semicolons as a line ! separator. However, note that some assembler dialects use ! semicolons to start a comment. Remarks ....... ! Using extended `asm' (*note Extended Asm::) typically produces smaller, safer, and more efficient code, and in most cases it is a better ! solution than basic `asm'. However, there are two situations where ! only basic `asm' can be used: ! * Extended `asm' statements have to be inside a C function, so to ! write inline assembly language at file scope ("top-level"), ! outside of C functions, you must use basic `asm'. You can use ! this technique to emit assembler directives, define assembly ! language macros that can be invoked elsewhere in the file, or ! write entire functions in assembly language. ! * Functions declared with the `naked' attribute also require basic ! `asm' (*note Function Attributes::). ! Safely accessing C data and calling functions from basic `asm' is more ! complex than it may appear. To access C data, it is better to use ! extended `asm'. ! Do not expect a sequence of `asm' statements to remain perfectly ! consecutive after compilation. If certain instructions need to remain ! consecutive in the output, put them in a single multi-instruction `asm' ! statement. Note that GCC's optimizers can move `asm' statements relative to other code, including across jumps. ! `asm' statements may not perform jumps into other `asm' statements. GCC does not know about these jumps, and therefore cannot take account ! of them when deciding how to optimize. Jumps from `asm' to C labels are ! only supported in extended `asm'. Under certain circumstances, GCC may duplicate (or remove duplicates ! of) your assembly code when optimizing. This can lead to unexpected ! duplicate symbol errors during compilation if your assembly code ! defines symbols or labels. ! *Warning:* The C standards do not specify semantics for `asm', making it a potential source of incompatibilities between compilers. These incompatibilities may not produce compiler warnings/errors. ! GCC does not parse basic `asm''s ASSEMBLERINSTRUCTIONS, which means there is no way to communicate to the compiler what is happening inside ! them. GCC has no visibility of symbols in the `asm' and may discard them as unreferenced. It also does not know about side effects of the assembler code, such as modifications to memory or registers. Unlike some compilers, GCC assumes that no changes to either memory or registers occur. This assumption may change in a future release. To avoid complications from future changes to the semantics and the ! compatibility issues between compilers, consider replacing basic `asm' ! with extended `asm'. See How to convert from basic asm to extended asm (https://gcc.gnu.org/wiki/ConvertBasicAsmToExtended) for information about how to perform this conversion. ! The compiler copies the assembler instructions in a basic `asm' verbatim to the assembly language output file, without processing ! dialects or any of the `%' operators that are available with extended ! `asm'. This results in minor differences between basic `asm' strings ! and extended `asm' templates. For example, to refer to registers you ! might use `%eax' in basic `asm' and `%%eax' in extended `asm'. On targets such as x86 that support multiple assembler dialects, all ! basic `asm' blocks use the assembler dialect specified by the `-masm' ! command-line option (*note x86 Options::). Basic `asm' provides no mechanism to provide different assembler strings for different dialects. ! Here is an example of basic `asm' for i386: /* Note that this code will not compile with -masm=intel */ #define DebugBreak() asm("int $3") *************** File: gcc.info, Node: Extended Asm, Ne *** 30476,30484 **** 6.44.2 Extended Asm - Assembler Instructions with C Expression Operands ----------------------------------------------------------------------- ! With extended 'asm' you can read and write C variables from assembler ! and perform jumps from assembler code to C labels. Extended 'asm' ! syntax uses colons (':') to delimit the operand parameters after the assembler template: asm [volatile] ( ASSEMBLERTEMPLATE --- 30701,30709 ---- 6.44.2 Extended Asm - Assembler Instructions with C Expression Operands ----------------------------------------------------------------------- ! With extended `asm' you can read and write C variables from assembler ! and perform jumps from assembler code to C labels. Extended `asm' ! syntax uses colons (`:') to delimit the operand parameters after the assembler template: asm [volatile] ( ASSEMBLERTEMPLATE *************** assembler template: *** 30492,30513 **** : CLOBBERS : GOTOLABELS) ! The 'asm' keyword is a GNU extension. When writing code that can be ! compiled with '-ansi' and the various '-std' options, use '__asm__' ! instead of 'asm' (*note Alternate Keywords::). Qualifiers .......... ! 'volatile' ! The typical use of extended 'asm' statements is to manipulate input ! values to produce output values. However, your 'asm' statements ! may also produce side effects. If so, you may need to use the ! 'volatile' qualifier to disable certain optimizations. *Note Volatile::. ! 'goto' ! This qualifier informs the compiler that the 'asm' statement may perform a jump to one of the labels listed in the GOTOLABELS. *Note GotoLabels::. --- 30717,30738 ---- : CLOBBERS : GOTOLABELS) ! The `asm' keyword is a GNU extension. When writing code that can be ! compiled with `-ansi' and the various `-std' options, use `__asm__' ! instead of `asm' (*note Alternate Keywords::). Qualifiers .......... ! `volatile' ! The typical use of extended `asm' statements is to manipulate input ! values to produce output values. However, your `asm' statements may ! also produce side effects. If so, you may need to use the ! `volatile' qualifier to disable certain optimizations. *Note Volatile::. ! `goto' ! This qualifier informs the compiler that the `asm' statement may perform a jump to one of the labels listed in the GOTOLABELS. *Note GotoLabels::. *************** Parameters *** 30516,30532 **** ASSEMBLERTEMPLATE This is a literal string that is the template for the assembler ! code. It is a combination of fixed text and tokens that refer to ! the input, output, and goto parameters. *Note AssemblerTemplate::. OUTPUTOPERANDS A comma-separated list of the C variables modified by the ! instructions in the ASSEMBLERTEMPLATE. An empty list is permitted. ! *Note OutputOperands::. INPUTOPERANDS ! A comma-separated list of C expressions read by the instructions in ! the ASSEMBLERTEMPLATE. An empty list is permitted. *Note InputOperands::. CLOBBERS --- 30741,30757 ---- ASSEMBLERTEMPLATE This is a literal string that is the template for the assembler ! code. It is a combination of fixed text and tokens that refer to ! the input, output, and goto parameters. *Note AssemblerTemplate::. OUTPUTOPERANDS A comma-separated list of the C variables modified by the ! instructions in the ASSEMBLERTEMPLATE. An empty list is ! permitted. *Note OutputOperands::. INPUTOPERANDS ! A comma-separated list of C expressions read by the instructions ! in the ASSEMBLERTEMPLATE. An empty list is permitted. *Note InputOperands::. CLOBBERS *************** CLOBBERS *** 30535,30545 **** is permitted. *Note Clobbers::. GOTOLABELS ! When you are using the 'goto' form of 'asm', this section contains ! the list of all C labels to which the code in the ASSEMBLERTEMPLATE ! may jump. *Note GotoLabels::. ! 'asm' statements may not perform jumps into other 'asm' statements, only to the listed GOTOLABELS. GCC's optimizers do not know about other jumps; therefore they cannot take account of them when deciding how to optimize. --- 30760,30770 ---- is permitted. *Note Clobbers::. GOTOLABELS ! When you are using the `goto' form of `asm', this section contains ! the list of all C labels to which the code in the ! ASSEMBLERTEMPLATE may jump. *Note GotoLabels::. ! `asm' statements may not perform jumps into other `asm' statements, only to the listed GOTOLABELS. GCC's optimizers do not know about other jumps; therefore they cannot take account of them when deciding how to optimize. *************** GOTOLABELS *** 30549,30568 **** Remarks ....... ! The 'asm' statement allows you to include assembly instructions directly ! within C code. This may help you to maximize performance in time-sensitive code or to access assembly instructions that are not readily available to C programs. ! Note that extended 'asm' statements must be inside a function. Only ! basic 'asm' may be outside functions (*note Basic Asm::). Functions ! declared with the 'naked' attribute also require basic 'asm' (*note Function Attributes::). ! While the uses of 'asm' are many and varied, it may help to think of an ! 'asm' statement as a series of low-level instructions that convert input ! parameters to output parameters. So a simple (if not particularly ! useful) example for i386 using 'asm' might look like this: int src = 1; int dst; --- 30774,30793 ---- Remarks ....... ! The `asm' statement allows you to include assembly instructions directly ! within C code. This may help you to maximize performance in time-sensitive code or to access assembly instructions that are not readily available to C programs. ! Note that extended `asm' statements must be inside a function. Only ! basic `asm' may be outside functions (*note Basic Asm::). Functions ! declared with the `naked' attribute also require basic `asm' (*note Function Attributes::). ! While the uses of `asm' are many and varied, it may help to think of an ! `asm' statement as a series of low-level instructions that convert input ! parameters to output parameters. So a simple (if not particularly ! useful) example for i386 using `asm' might look like this: int src = 1; int dst; *************** useful) example for i386 using 'asm' mig *** 30574,30599 **** printf("%d\n", dst); ! This code copies 'src' to 'dst' and add 1 to 'dst'. 6.44.2.1 Volatile ................. ! GCC's optimizers sometimes discard 'asm' statements if they determine ! there is no need for the output variables. Also, the optimizers may ! move code out of loops if they believe that the code will always return ! the same result (i.e. none of its input values change between calls). ! Using the 'volatile' qualifier disables these optimizations. 'asm' ! statements that have no output operands, including 'asm goto' ! statements, are implicitly volatile. This i386 code demonstrates a case that does not use (or require) the ! 'volatile' qualifier. If it is performing assertion checking, this code ! uses 'asm' to perform the validation. Otherwise, 'dwRes' is ! unreferenced by any code. As a result, the optimizers can discard the ! 'asm' statement, which in turn removes the need for the entire 'DoCheck' ! routine. By omitting the 'volatile' qualifier when it isn't needed you ! allow the optimizers to produce the most efficient code possible. void DoCheck(uint32_t dwSomeValue) { --- 30799,30825 ---- printf("%d\n", dst); ! This code copies `src' to `dst' and add 1 to `dst'. 6.44.2.1 Volatile ................. ! GCC's optimizers sometimes discard `asm' statements if they determine ! there is no need for the output variables. Also, the optimizers may move ! code out of loops if they believe that the code will always return the ! same result (i.e. none of its input values change between calls). Using ! the `volatile' qualifier disables these optimizations. `asm' statements ! that have no output operands, including `asm goto' statements, are ! implicitly volatile. This i386 code demonstrates a case that does not use (or require) the ! `volatile' qualifier. If it is performing assertion checking, this code ! uses `asm' to perform the validation. Otherwise, `dwRes' is ! unreferenced by any code. As a result, the optimizers can discard the ! `asm' statement, which in turn removes the need for the entire ! `DoCheck' routine. By omitting the `volatile' qualifier when it isn't ! needed you allow the optimizers to produce the most efficient code ! possible. void DoCheck(uint32_t dwSomeValue) { *************** allow the optimizers to produce the most *** 30609,30617 **** } The next example shows a case where the optimizers can recognize that ! the input ('dwSomeValue') never changes during the execution of the ! function and can therefore move the 'asm' outside the loop to produce ! more efficient code. Again, using 'volatile' disables this type of optimization. void do_print(uint32_t dwSomeValue) --- 30835,30843 ---- } The next example shows a case where the optimizers can recognize that ! the input (`dwSomeValue') never changes during the execution of the ! function and can therefore move the `asm' outside the loop to produce ! more efficient code. Again, using `volatile' disables this type of optimization. void do_print(uint32_t dwSomeValue) *************** optimization. *** 30631,30639 **** } The following example demonstrates a case where you need to use the ! 'volatile' qualifier. It uses the x86 'rdtsc' instruction, which reads ! the computer's time-stamp counter. Without the 'volatile' qualifier, ! the optimizers might assume that the 'asm' block will always return the same value and therefore optimize away the second call. uint64_t msr; --- 30857,30865 ---- } The following example demonstrates a case where you need to use the ! `volatile' qualifier. It uses the x86 `rdtsc' instruction, which reads ! the computer's time-stamp counter. Without the `volatile' qualifier, ! the optimizers might assume that the `asm' block will always return the same value and therefore optimize away the second call. uint64_t msr; *************** same value and therefore optimize away t *** 30660,30688 **** printf("msr: %llx\n", msr); GCC's optimizers do not treat this code like the non-volatile code in ! the earlier examples. They do not move it out of loops or omit it on ! the assumption that the result from a previous call is still valid. ! Note that the compiler can move even volatile 'asm' instructions ! relative to other code, including across jump instructions. For example, on many targets there is a system register that controls the ! rounding mode of floating-point operations. Setting it with a volatile ! 'asm', as in the following PowerPC example, does not work reliably. asm volatile("mtfsf 255, %0" : : "f" (fpenv)); sum = x + y; ! The compiler may move the addition back before the volatile 'asm'. To ! make it work as expected, add an artificial dependency to the 'asm' by referencing a variable in the subsequent code, for example: asm volatile ("mtfsf 255,%1" : "=X" (sum) : "f" (fpenv)); sum = x + y; Under certain circumstances, GCC may duplicate (or remove duplicates ! of) your assembly code when optimizing. This can lead to unexpected duplicate symbol errors during compilation if your asm code defines ! symbols or labels. Using '%=' (*note AssemblerTemplate::) may help resolve this problem. 6.44.2.2 Assembler Template --- 30886,30914 ---- printf("msr: %llx\n", msr); GCC's optimizers do not treat this code like the non-volatile code in ! the earlier examples. They do not move it out of loops or omit it on the ! assumption that the result from a previous call is still valid. ! Note that the compiler can move even volatile `asm' instructions ! relative to other code, including across jump instructions. For example, on many targets there is a system register that controls the ! rounding mode of floating-point operations. Setting it with a volatile ! `asm', as in the following PowerPC example, does not work reliably. asm volatile("mtfsf 255, %0" : : "f" (fpenv)); sum = x + y; ! The compiler may move the addition back before the volatile `asm'. To ! make it work as expected, add an artificial dependency to the `asm' by referencing a variable in the subsequent code, for example: asm volatile ("mtfsf 255,%1" : "=X" (sum) : "f" (fpenv)); sum = x + y; Under certain circumstances, GCC may duplicate (or remove duplicates ! of) your assembly code when optimizing. This can lead to unexpected duplicate symbol errors during compilation if your asm code defines ! symbols or labels. Using `%=' (*note AssemblerTemplate::) may help resolve this problem. 6.44.2.2 Assembler Template *************** resolve this problem. *** 30691,30725 **** An assembler template is a literal string containing assembler instructions. The compiler replaces tokens in the template that refer to inputs, outputs, and goto labels, and then outputs the resulting ! string to the assembler. The string can contain any instructions ! recognized by the assembler, including directives. GCC does not parse the assembler instructions themselves and does not know what they mean ! or even whether they are valid assembler input. However, it does count the statements (*note Size of an asm::). You may place multiple assembler instructions together in a single ! 'asm' string, separated by the characters normally used in assembly code ! for the system. A combination that works in most places is a newline to ! break the line, plus a tab character to move to the instruction field ! (written as '\n\t'). Some assemblers allow semicolons as a line ! separator. However, note that some assembler dialects use semicolons to ! start a comment. ! Do not expect a sequence of 'asm' statements to remain perfectly ! consecutive after compilation, even when you are using the 'volatile' ! qualifier. If certain instructions need to remain consecutive in the output, put them in a single multi-instruction asm statement. Accessing data from C programs without using input/output operands (such as by using global symbols directly from the assembler template) ! may not work as expected. Similarly, calling functions directly from an assembler template requires a detailed understanding of the target assembler and ABI. Since GCC does not parse the assembler template, it has no visibility ! of any symbols it references. This may result in GCC discarding those ! symbols as unreferenced unless they are also listed as input, output, or ! goto operands. Special format strings ...................... --- 30917,30951 ---- An assembler template is a literal string containing assembler instructions. The compiler replaces tokens in the template that refer to inputs, outputs, and goto labels, and then outputs the resulting ! string to the assembler. The string can contain any instructions ! recognized by the assembler, including directives. GCC does not parse the assembler instructions themselves and does not know what they mean ! or even whether they are valid assembler input. However, it does count the statements (*note Size of an asm::). You may place multiple assembler instructions together in a single ! `asm' string, separated by the characters normally used in assembly ! code for the system. A combination that works in most places is a ! newline to break the line, plus a tab character to move to the ! instruction field (written as `\n\t'). Some assemblers allow ! semicolons as a line separator. However, note that some assembler ! dialects use semicolons to start a comment. ! Do not expect a sequence of `asm' statements to remain perfectly ! consecutive after compilation, even when you are using the `volatile' ! qualifier. If certain instructions need to remain consecutive in the output, put them in a single multi-instruction asm statement. Accessing data from C programs without using input/output operands (such as by using global symbols directly from the assembler template) ! may not work as expected. Similarly, calling functions directly from an assembler template requires a detailed understanding of the target assembler and ABI. Since GCC does not parse the assembler template, it has no visibility ! of any symbols it references. This may result in GCC discarding those ! symbols as unreferenced unless they are also listed as input, output, ! or goto operands. Special format strings ...................... *************** Special format strings *** 30727,30774 **** In addition to the tokens described by the input, output, and goto operands, these tokens have special meanings in the assembler template: ! '%%' ! Outputs a single '%' into the assembler code. ! '%=' ! Outputs a number that is unique to each instance of the 'asm' ! statement in the entire compilation. This option is useful when creating local labels and referring to them multiple times in a single template that generates multiple assembler instructions. ! '%{' ! '%|' ! '%}' ! Outputs '{', '|', and '}' characters (respectively) into the assembler code. When unescaped, these characters have special meaning to indicate multiple assembler dialects, as described below. ! Multiple assembler dialects in 'asm' templates .............................................. On targets such as x86, GCC supports multiple assembler dialects. The ! '-masm' option controls which dialect GCC uses as its default for inline ! assembler. The target-specific documentation for the '-masm' option ! contains the list of supported dialects, as well as the default dialect ! if the option is not specified. This information may be important to ! understand, since assembler code that works correctly when compiled ! using one dialect will likely fail if compiled using another. *Note x86 ! Options::. ! If your code needs to support multiple assembler dialects (for example, ! if you are writing public headers that need to support a variety of ! compilation options), use constructs of this form: { dialect0 | dialect1 | dialect2... } ! This construct outputs 'dialect0' when using dialect #0 to compile the ! code, 'dialect1' for dialect #1, etc. If there are fewer alternatives ! within the braces than the number of dialects the compiler supports, the ! construct outputs nothing. ! For example, if an x86 compiler supports two dialects ('att', 'intel'), ! an assembler template such as this: "bt{l %[Offset],%[Base] | %[Base],%[Offset]}; jc %l2" --- 30953,31000 ---- In addition to the tokens described by the input, output, and goto operands, these tokens have special meanings in the assembler template: ! `%%' ! Outputs a single `%' into the assembler code. ! `%=' ! Outputs a number that is unique to each instance of the `asm' ! statement in the entire compilation. This option is useful when creating local labels and referring to them multiple times in a single template that generates multiple assembler instructions. ! `%{' ! `%|' ! `%}' ! Outputs `{', `|', and `}' characters (respectively) into the assembler code. When unescaped, these characters have special meaning to indicate multiple assembler dialects, as described below. ! Multiple assembler dialects in `asm' templates .............................................. On targets such as x86, GCC supports multiple assembler dialects. The ! `-masm' option controls which dialect GCC uses as its default for ! inline assembler. The target-specific documentation for the `-masm' ! option contains the list of supported dialects, as well as the default ! dialect if the option is not specified. This information may be ! important to understand, since assembler code that works correctly when ! compiled using one dialect will likely fail if compiled using another. ! *Note x86 Options::. ! If your code needs to support multiple assembler dialects (for ! example, if you are writing public headers that need to support a ! variety of compilation options), use constructs of this form: { dialect0 | dialect1 | dialect2... } ! This construct outputs `dialect0' when using dialect #0 to compile the ! code, `dialect1' for dialect #1, etc. If there are fewer alternatives ! within the braces than the number of dialects the compiler supports, ! the construct outputs nothing. ! For example, if an x86 compiler supports two dialects (`att', ! `intel'), an assembler template such as this: "bt{l %[Offset],%[Base] | %[Base],%[Offset]}; jc %l2" *************** corresponds to either *** 30791,30801 **** 6.44.2.3 Output Operands ........................ ! An 'asm' statement has zero or more output operands indicating the names of C variables modified by the assembler code. ! In this i386 example, 'old' (referred to in the template string as ! '%0') and '*Base' (as '%1') are outputs and 'Offset' ('%2') is an input: bool old; --- 31017,31027 ---- 6.44.2.3 Output Operands ........................ ! An `asm' statement has zero or more output operands indicating the names of C variables modified by the assembler code. ! In this i386 example, `old' (referred to in the template string as ! `%0') and `*Base' (as `%1') are outputs and `Offset' (`%2') is an input: bool old; *************** of C variables modified by the assembler *** 30814,30850 **** ASMSYMBOLICNAME Specifies a symbolic name for the operand. Reference the name in the assembler template by enclosing it in square brackets (i.e. ! '%[Value]'). The scope of the name is the 'asm' statement that ! contains the definition. Any valid C variable name is acceptable, ! including names already defined in the surrounding code. No two ! operands within the same 'asm' statement can use the same symbolic name. ! When not using an ASMSYMBOLICNAME, use the (zero-based) position of ! the operand in the list of operands in the assembler template. For ! example if there are three output operands, use '%0' in the ! template to refer to the first, '%1' for the second, and '%2' for the third. CONSTRAINT A string constant specifying constraints on the placement of the operand; *Note Constraints::, for details. ! Output constraints must begin with either '=' (a variable ! overwriting an existing value) or '+' (when reading and writing). ! When using '=', do not assume the location contains the existing ! value on entry to the 'asm', except when the operand is tied to an input; *note Input Operands: InputOperands. After the prefix, there must be one or more additional constraints ! (*note Constraints::) that describe where the value resides. ! Common constraints include 'r' for register and 'm' for memory. ! When you list more than one possible location (for example, ! '"=rm"'), the compiler chooses the most efficient one based on the ! current context. If you list as many alternates as the 'asm' ! statement allows, you permit the optimizers to produce the best ! possible code. If you must use a specific register, but your ! Machine Constraints do not provide sufficient control to select the specific register you want, local register variables may provide a solution (*note Local Register Variables::). --- 31040,31076 ---- ASMSYMBOLICNAME Specifies a symbolic name for the operand. Reference the name in the assembler template by enclosing it in square brackets (i.e. ! `%[Value]'). The scope of the name is the `asm' statement that ! contains the definition. Any valid C variable name is acceptable, ! including names already defined in the surrounding code. No two ! operands within the same `asm' statement can use the same symbolic name. ! When not using an ASMSYMBOLICNAME, use the (zero-based) position ! of the operand in the list of operands in the assembler template. ! For example if there are three output operands, use `%0' in the ! template to refer to the first, `%1' for the second, and `%2' for the third. CONSTRAINT A string constant specifying constraints on the placement of the operand; *Note Constraints::, for details. ! Output constraints must begin with either `=' (a variable ! overwriting an existing value) or `+' (when reading and writing). ! When using `=', do not assume the location contains the existing ! value on entry to the `asm', except when the operand is tied to an input; *note Input Operands: InputOperands. After the prefix, there must be one or more additional constraints ! (*note Constraints::) that describe where the value resides. Common ! constraints include `r' for register and `m' for memory. When you ! list more than one possible location (for example, `"=rm"'), the ! compiler chooses the most efficient one based on the current ! context. If you list as many alternates as the `asm' statement ! allows, you permit the optimizers to produce the best possible ! code. If you must use a specific register, but your Machine ! Constraints do not provide sufficient control to select the specific register you want, local register variables may provide a solution (*note Local Register Variables::). *************** CVARIABLENAME *** 30853,30907 **** variable name. The enclosing parentheses are a required part of the syntax. When the compiler selects the registers to use to represent the output operands, it does not use any of the clobbered registers (*note Clobbers::). ! Output operand expressions must be lvalues. The compiler cannot check whether the operands have data types that are reasonable for the ! instruction being executed. For output expressions that are not directly addressable (for example a bit-field), the constraint must ! allow a register. In that case, GCC uses the register as the output of ! the 'asm', and then stores that register into the output. ! Operands using the '+' constraint modifier count as two operands (that is, both as input and output) towards the total maximum of 30 operands ! per 'asm' statement. ! Use the '&' constraint modifier (*note Modifiers::) on all output operands that must not overlap an input. Otherwise, GCC may allocate the output operand in the same register as an unrelated input operand, on the assumption that the assembler code consumes its inputs before ! producing outputs. This assumption may be false if the assembler code actually consists of more than one instruction. The same problem can occur if one output parameter (A) allows a register constraint and another output parameter (B) allows a memory ! constraint. The code generated by GCC to access the memory address in B ! can contain registers which _might_ be shared by A, and GCC considers ! those registers to be inputs to the asm. As above, GCC assumes that ! such input registers are consumed before any outputs are written. This assumption may result in incorrect behavior if the asm writes to A ! before using B. Combining the '&' modifier with the register constraint on A ensures that modifying A does not affect the address referenced by ! B. Otherwise, the location of B is undefined if A is modified before using B. ! 'asm' supports operand modifiers on operands (for example '%k2' instead ! of simply '%2'). Typically these qualifiers are hardware dependent. ! The list of supported modifiers for x86 is found at *note x86 Operand ! modifiers: x86Operandmodifiers. ! If the C code that follows the 'asm' makes no use of any of the output ! operands, use 'volatile' for the 'asm' statement to prevent the ! optimizers from discarding the 'asm' statement as unneeded (see *note Volatile::). ! This code makes no use of the optional ASMSYMBOLICNAME. Therefore it ! references the first output operand as '%0' (were there a second, it ! would be '%1', etc). The number of the first input operand is one ! greater than that of the last output operand. In this i386 example, ! that makes 'Mask' referenced as '%1': uint32_t Mask = 1234; uint32_t Index; --- 31079,31134 ---- variable name. The enclosing parentheses are a required part of the syntax. + When the compiler selects the registers to use to represent the output operands, it does not use any of the clobbered registers (*note Clobbers::). ! Output operand expressions must be lvalues. The compiler cannot check whether the operands have data types that are reasonable for the ! instruction being executed. For output expressions that are not directly addressable (for example a bit-field), the constraint must ! allow a register. In that case, GCC uses the register as the output of ! the `asm', and then stores that register into the output. ! Operands using the `+' constraint modifier count as two operands (that is, both as input and output) towards the total maximum of 30 operands ! per `asm' statement. ! Use the `&' constraint modifier (*note Modifiers::) on all output operands that must not overlap an input. Otherwise, GCC may allocate the output operand in the same register as an unrelated input operand, on the assumption that the assembler code consumes its inputs before ! producing outputs. This assumption may be false if the assembler code actually consists of more than one instruction. The same problem can occur if one output parameter (A) allows a register constraint and another output parameter (B) allows a memory ! constraint. The code generated by GCC to access the memory address in ! B can contain registers which _might_ be shared by A, and GCC considers ! those registers to be inputs to the asm. As above, GCC assumes that ! such input registers are consumed before any outputs are written. This assumption may result in incorrect behavior if the asm writes to A ! before using B. Combining the `&' modifier with the register constraint on A ensures that modifying A does not affect the address referenced by ! B. Otherwise, the location of B is undefined if A is modified before using B. ! `asm' supports operand modifiers on operands (for example `%k2' ! instead of simply `%2'). Typically these qualifiers are hardware ! dependent. The list of supported modifiers for x86 is found at *note ! x86 Operand modifiers: x86Operandmodifiers. ! If the C code that follows the `asm' makes no use of any of the output ! operands, use `volatile' for the `asm' statement to prevent the ! optimizers from discarding the `asm' statement as unneeded (see *note Volatile::). ! This code makes no use of the optional ASMSYMBOLICNAME. Therefore it ! references the first output operand as `%0' (were there a second, it ! would be `%1', etc). The number of the first input operand is one ! greater than that of the last output operand. In this i386 example, ! that makes `Mask' referenced as `%1': uint32_t Mask = 1234; uint32_t Index; *************** that makes 'Mask' referenced as '%1': *** 30911,30928 **** : "r" (Mask) : "cc"); ! That code overwrites the variable 'Index' ('='), placing the value in a ! register ('r'). Using the generic 'r' constraint instead of a constraint for a specific register allows the compiler to pick the ! register to use, which can result in more efficient code. This may not be possible if an assembler instruction requires a specific register. The following i386 example uses the ASMSYMBOLICNAME syntax. It produces the same result as the code above, but some may consider it ! more readable or more maintainable since reordering index numbers is not ! necessary when adding or removing operands. The names 'aIndex' and ! 'aMask' are only used in this example to emphasize which names get used ! where. It is acceptable to reuse the names 'Index' and 'Mask'. uint32_t Mask = 1234; uint32_t Index; --- 31138,31155 ---- : "r" (Mask) : "cc"); ! That code overwrites the variable `Index' (`='), placing the value in ! a register (`r'). Using the generic `r' constraint instead of a constraint for a specific register allows the compiler to pick the ! register to use, which can result in more efficient code. This may not be possible if an assembler instruction requires a specific register. The following i386 example uses the ASMSYMBOLICNAME syntax. It produces the same result as the code above, but some may consider it ! more readable or more maintainable since reordering index numbers is ! not necessary when adding or removing operands. The names `aIndex' and ! `aMask' are only used in this example to emphasize which names get used ! where. It is acceptable to reuse the names `Index' and `Mask'. uint32_t Mask = 1234; uint32_t Index; *************** where. It is acceptable to reuse the na *** 30942,30951 **** : [d] "=rm" (d) : [e] "rm" (*e)); ! Here, 'd' may either be in a register or in memory. Since the compiler ! might already have the current value of the 'uint32_t' location pointed ! to by 'e' in a register, you can enable it to choose the best location ! for 'd' by specifying both constraints. 6.44.2.4 Flag Output Operands ............................. --- 31169,31178 ---- : [d] "=rm" (d) : [e] "rm" (*e)); ! Here, `d' may either be in a register or in memory. Since the compiler ! might already have the current value of the `uint32_t' location pointed ! to by `e' in a register, you can enable it to choose the best location ! for `d' by specifying both constraints. 6.44.2.4 Flag Output Operands ............................. *************** conditions in the flags register may be *** 30960,31028 **** conditions supported are target specific, but the general rule is that the output variable must be a scalar integer, and the value is boolean. When supported, the target defines the preprocessor symbol ! '__GCC_ASM_FLAG_OUTPUTS__'. Because of the special nature of the flag output operands, the constraint may not include alternatives. Most often, the target has only one flags register, and thus is an implied operand of many instructions. In this case, the operand should ! not be referenced within the assembler template via '%0' etc, as there's no corresponding text in the assembly language. x86 family The flag output constraints for the x86 family are of the form ! '=@ccCOND' where COND is one of the standard conditions defined in ! the ISA manual for 'jCC' or 'setCC'. ! 'a' "above" or unsigned greater than ! 'ae' "above or equal" or unsigned greater than or equal ! 'b' "below" or unsigned less than ! 'be' "below or equal" or unsigned less than or equal ! 'c' carry flag set ! 'e' ! 'z' "equal" or zero flag set ! 'g' signed greater than ! 'ge' signed greater than or equal ! 'l' signed less than ! 'le' signed less than or equal ! 'o' overflow flag set ! 'p' parity flag set ! 's' sign flag set ! 'na' ! 'nae' ! 'nb' ! 'nbe' ! 'nc' ! 'ne' ! 'ng' ! 'nge' ! 'nl' ! 'nle' ! 'no' ! 'np' ! 'ns' ! 'nz' "not" FLAG, or inverted versions of those above 6.44.2.5 Input Operands ....................... ! Input operands make values from C variables and expressions available to ! the assembly code. Operands are separated by commas. Each operand has this format: --- 31187,31269 ---- conditions supported are target specific, but the general rule is that the output variable must be a scalar integer, and the value is boolean. When supported, the target defines the preprocessor symbol ! `__GCC_ASM_FLAG_OUTPUTS__'. Because of the special nature of the flag output operands, the constraint may not include alternatives. Most often, the target has only one flags register, and thus is an implied operand of many instructions. In this case, the operand should ! not be referenced within the assembler template via `%0' etc, as there's no corresponding text in the assembly language. x86 family The flag output constraints for the x86 family are of the form ! `=@ccCOND' where COND is one of the standard conditions defined in ! the ISA manual for `jCC' or `setCC'. ! `a' "above" or unsigned greater than ! ! `ae' "above or equal" or unsigned greater than or equal ! ! `b' "below" or unsigned less than ! ! `be' "below or equal" or unsigned less than or equal ! ! `c' carry flag set ! ! `e' ! `z' "equal" or zero flag set ! ! `g' signed greater than ! ! `ge' signed greater than or equal ! ! `l' signed less than ! ! `le' signed less than or equal ! ! `o' overflow flag set ! ! `p' parity flag set ! ! `s' sign flag set ! ! `na' ! `nae' ! `nb' ! `nbe' ! `nc' ! `ne' ! `ng' ! `nge' ! `nl' ! `nle' ! `no' ! `np' ! `ns' ! `nz' "not" FLAG, or inverted versions of those above + 6.44.2.5 Input Operands ....................... ! Input operands make values from C variables and expressions available ! to the assembly code. Operands are separated by commas. Each operand has this format: *************** the assembly code. *** 31031,31072 **** ASMSYMBOLICNAME Specifies a symbolic name for the operand. Reference the name in the assembler template by enclosing it in square brackets (i.e. ! '%[Value]'). The scope of the name is the 'asm' statement that ! contains the definition. Any valid C variable name is acceptable, ! including names already defined in the surrounding code. No two ! operands within the same 'asm' statement can use the same symbolic name. ! When not using an ASMSYMBOLICNAME, use the (zero-based) position of ! the operand in the list of operands in the assembler template. For ! example if there are two output operands and three inputs, use '%2' ! in the template to refer to the first input operand, '%3' for the ! second, and '%4' for the third. CONSTRAINT A string constant specifying constraints on the placement of the operand; *Note Constraints::, for details. ! Input constraint strings may not begin with either '=' or '+'. When you list more than one possible location (for example, ! '"irm"'), the compiler chooses the most efficient one based on the current context. If you must use a specific register, but your ! Machine Constraints do not provide sufficient control to select the ! specific register you want, local register variables may provide a ! solution (*note Local Register Variables::). ! Input constraints can also be digits (for example, '"0"'). This ! indicates that the specified input must be in the same place as the ! output constraint at the (zero-based) index in the output constraint list. When using ASMSYMBOLICNAME syntax for the output ! operands, you may use these names (enclosed in brackets '[]') instead of digits. CEXPRESSION ! This is the C variable or expression being passed to the 'asm' statement as input. The enclosing parentheses are a required part of the syntax. When the compiler selects the registers to use to represent the input operands, it does not use any of the clobbered registers (*note Clobbers::). --- 31272,31314 ---- ASMSYMBOLICNAME Specifies a symbolic name for the operand. Reference the name in the assembler template by enclosing it in square brackets (i.e. ! `%[Value]'). The scope of the name is the `asm' statement that ! contains the definition. Any valid C variable name is acceptable, ! including names already defined in the surrounding code. No two ! operands within the same `asm' statement can use the same symbolic name. ! When not using an ASMSYMBOLICNAME, use the (zero-based) position ! of the operand in the list of operands in the assembler template. ! For example if there are two output operands and three inputs, use ! `%2' in the template to refer to the first input operand, `%3' for ! the second, and `%4' for the third. CONSTRAINT A string constant specifying constraints on the placement of the operand; *Note Constraints::, for details. ! Input constraint strings may not begin with either `=' or `+'. When you list more than one possible location (for example, ! `"irm"'), the compiler chooses the most efficient one based on the current context. If you must use a specific register, but your ! Machine Constraints do not provide sufficient control to select ! the specific register you want, local register variables may ! provide a solution (*note Local Register Variables::). ! Input constraints can also be digits (for example, `"0"'). This ! indicates that the specified input must be in the same place as ! the output constraint at the (zero-based) index in the output constraint list. When using ASMSYMBOLICNAME syntax for the output ! operands, you may use these names (enclosed in brackets `[]') instead of digits. CEXPRESSION ! This is the C variable or expression being passed to the `asm' statement as input. The enclosing parentheses are a required part of the syntax. + When the compiler selects the registers to use to represent the input operands, it does not use any of the clobbered registers (*note Clobbers::). *************** consecutive colons where the output oper *** 31079,31107 **** : "r" (Offset / 8)); *Warning:* Do _not_ modify the contents of input-only operands (except ! for inputs tied to outputs). The compiler assumes that on exit from the ! 'asm' statement these operands contain the same values as they had ! before executing the statement. It is _not_ possible to use clobbers to ! inform the compiler that the values in these inputs are changing. One common work-around is to tie the changing input variable to an output ! variable that never gets used. Note, however, that if the code that ! follows the 'asm' statement makes no use of any of the output operands, ! the GCC optimizers may discard the 'asm' statement as unneeded (see *note Volatile::). ! 'asm' supports operand modifiers on operands (for example '%k2' instead ! of simply '%2'). Typically these qualifiers are hardware dependent. ! The list of supported modifiers for x86 is found at *note x86 Operand ! modifiers: x86Operandmodifiers. ! In this example using the fictitious 'combine' instruction, the ! constraint '"0"' for input operand 1 says that it must occupy the same ! location as output operand 0. Only input operands may use numbers in ! constraints, and they must each refer to an output operand. Only a number (or the symbolic assembler name) in the constraint can guarantee ! that one operand is in the same place as another. The mere fact that ! 'foo' is the value of both operands is not enough to guarantee that they ! are in the same place in the generated assembler code. asm ("combine %2, %0" : "=r" (foo) --- 31321,31349 ---- : "r" (Offset / 8)); *Warning:* Do _not_ modify the contents of input-only operands (except ! for inputs tied to outputs). The compiler assumes that on exit from the ! `asm' statement these operands contain the same values as they had ! before executing the statement. It is _not_ possible to use clobbers ! to inform the compiler that the values in these inputs are changing. One common work-around is to tie the changing input variable to an output ! variable that never gets used. Note, however, that if the code that ! follows the `asm' statement makes no use of any of the output operands, ! the GCC optimizers may discard the `asm' statement as unneeded (see *note Volatile::). ! `asm' supports operand modifiers on operands (for example `%k2' ! instead of simply `%2'). Typically these qualifiers are hardware ! dependent. The list of supported modifiers for x86 is found at *note ! x86 Operand modifiers: x86Operandmodifiers. ! In this example using the fictitious `combine' instruction, the ! constraint `"0"' for input operand 1 says that it must occupy the same ! location as output operand 0. Only input operands may use numbers in ! constraints, and they must each refer to an output operand. Only a number (or the symbolic assembler name) in the constraint can guarantee ! that one operand is in the same place as another. The mere fact that ! `foo' is the value of both operands is not enough to guarantee that ! they are in the same place in the generated assembler code. asm ("combine %2, %0" : "=r" (foo) *************** are in the same place in the generated a *** 31117,31144 **** ................. While the compiler is aware of changes to entries listed in the output ! operands, the inline 'asm' code may modify more than just the outputs. For example, calculations may require additional registers, or the processor may overwrite a register as a side effect of a particular assembler instruction. In order to inform the compiler of these ! changes, list them in the clobber list. Clobber list items are either ! register names or the special clobbers (listed below). Each clobber list item is a string constant enclosed in double quotes and separated by commas. Clobber descriptions may not in any way overlap with an input or output ! operand. For example, you may not have an operand describing a register class with one member when listing that register in the clobber list. Variables declared to live in specific registers (*note Explicit ! Register Variables::) and used as 'asm' input or output operands must ! have no part mentioned in the clobber description. In particular, there is no way to specify that input operands get modified without also specifying them as output operands. ! When the compiler selects which registers to use to represent input and ! output operands, it does not use any of the clobbered registers. As a ! result, clobbered registers are available for any use in the assembler ! code. Here is a realistic example for the VAX showing the use of clobbered registers: --- 31359,31386 ---- ................. While the compiler is aware of changes to entries listed in the output ! operands, the inline `asm' code may modify more than just the outputs. For example, calculations may require additional registers, or the processor may overwrite a register as a side effect of a particular assembler instruction. In order to inform the compiler of these ! changes, list them in the clobber list. Clobber list items are either ! register names or the special clobbers (listed below). Each clobber list item is a string constant enclosed in double quotes and separated by commas. Clobber descriptions may not in any way overlap with an input or output ! operand. For example, you may not have an operand describing a register class with one member when listing that register in the clobber list. Variables declared to live in specific registers (*note Explicit ! Register Variables::) and used as `asm' input or output operands must ! have no part mentioned in the clobber description. In particular, there is no way to specify that input operands get modified without also specifying them as output operands. ! When the compiler selects which registers to use to represent input ! and output operands, it does not use any of the clobbered registers. As ! a result, clobbered registers are available for any use in the ! assembler code. Here is a realistic example for the VAX showing the use of clobbered registers: *************** registers: *** 31150,31219 **** Also, there are two special clobber arguments: ! '"cc"' ! The '"cc"' clobber indicates that the assembler code modifies the ! flags register. On some machines, GCC represents the condition ! codes as a specific hardware register; '"cc"' serves to name this register. On other machines, condition code handling is different, ! and specifying '"cc"' has no effect. But it is valid no matter what the target. ! '"memory"' ! The '"memory"' clobber tells the compiler that the assembly code ! performs memory reads or writes to items other than those listed in ! the input and output operands (for example, accessing the memory ! pointed to by one of the input parameters). To ensure memory ! contains correct values, GCC may need to flush specific register ! values to memory before executing the 'asm'. Further, the compiler ! does not assume that any values read from memory before an 'asm' ! remain unchanged after that 'asm'; it reloads them as needed. ! Using the '"memory"' clobber effectively forms a read/write memory barrier for the compiler. Note that this clobber does not prevent the _processor_ from doing ! speculative reads past the 'asm' statement. To prevent that, you need processor-specific fence instructions. Flushing registers to memory has performance implications and may be an issue for time-sensitive code. You can use a trick to avoid this if the size of the memory being accessed is known at compile ! time. For example, if accessing ten bytes of a string, use a memory input like: ! '{"m"( ({ struct { char x[10]; } *p = (void *)ptr ; *p; }) )}'. 6.44.2.7 Goto Labels .................... ! 'asm goto' allows assembly code to jump to one or more C labels. The ! GOTOLABELS section in an 'asm goto' statement contains a comma-separated ! list of all C labels to which the assembler code may jump. GCC assumes ! that 'asm' execution falls through to the next statement (if this is not ! the case, consider using the '__builtin_unreachable' intrinsic after the ! 'asm' statement). Optimization of 'asm goto' may be improved by using ! the 'hot' and 'cold' label attributes (*note Label Attributes::). ! An 'asm goto' statement cannot have outputs. This is due to an internal restriction of the compiler: control transfer instructions cannot have outputs. If the assembler code does modify anything, use ! the '"memory"' clobber to force the optimizers to flush all register ! values to memory and reload them if necessary after the 'asm' statement. ! Also note that an 'asm goto' statement is always implicitly considered volatile. ! To reference a label in the assembler template, prefix it with '%l' ! (lowercase 'L') followed by its (zero-based) position in GOTOLABELS plus ! the number of input operands. For example, if the 'asm' has three ! inputs and references two labels, refer to the first label as '%l3' and ! the second as '%l4'). Alternately, you can reference labels using the actual C label name ! enclosed in brackets. For example, to reference a label named 'carry', ! you can use '%l[carry]'. The label must still be listed in the GOTOLABELS section when using this approach. ! Here is an example of 'asm goto' for i386: asm goto ( "btl %1, %0\n\t" --- 31392,31463 ---- Also, there are two special clobber arguments: ! `"cc"' ! The `"cc"' clobber indicates that the assembler code modifies the ! flags register. On some machines, GCC represents the condition ! codes as a specific hardware register; `"cc"' serves to name this register. On other machines, condition code handling is different, ! and specifying `"cc"' has no effect. But it is valid no matter what the target. ! `"memory"' ! The `"memory"' clobber tells the compiler that the assembly code ! performs memory reads or writes to items other than those listed ! in the input and output operands (for example, accessing the ! memory pointed to by one of the input parameters). To ensure ! memory contains correct values, GCC may need to flush specific ! register values to memory before executing the `asm'. Further, the ! compiler does not assume that any values read from memory before an ! `asm' remain unchanged after that `asm'; it reloads them as needed. ! Using the `"memory"' clobber effectively forms a read/write memory barrier for the compiler. Note that this clobber does not prevent the _processor_ from doing ! speculative reads past the `asm' statement. To prevent that, you need processor-specific fence instructions. Flushing registers to memory has performance implications and may be an issue for time-sensitive code. You can use a trick to avoid this if the size of the memory being accessed is known at compile ! time. For example, if accessing ten bytes of a string, use a memory input like: ! `{"m"( ({ struct { char x[10]; } *p = (void *)ptr ; *p; }) )}'. ! 6.44.2.7 Goto Labels .................... ! `asm goto' allows assembly code to jump to one or more C labels. The ! GOTOLABELS section in an `asm goto' statement contains a comma-separated ! list of all C labels to which the assembler code may jump. GCC assumes ! that `asm' execution falls through to the next statement (if this is ! not the case, consider using the `__builtin_unreachable' intrinsic ! after the `asm' statement). Optimization of `asm goto' may be improved ! by using the `hot' and `cold' label attributes (*note Label ! Attributes::). ! An `asm goto' statement cannot have outputs. This is due to an internal restriction of the compiler: control transfer instructions cannot have outputs. If the assembler code does modify anything, use ! the `"memory"' clobber to force the optimizers to flush all register ! values to memory and reload them if necessary after the `asm' statement. ! Also note that an `asm goto' statement is always implicitly considered volatile. ! To reference a label in the assembler template, prefix it with `%l' ! (lowercase `L') followed by its (zero-based) position in GOTOLABELS ! plus the number of input operands. For example, if the `asm' has three ! inputs and references two labels, refer to the first label as `%l3' and ! the second as `%l4'). Alternately, you can reference labels using the actual C label name ! enclosed in brackets. For example, to reference a label named `carry', ! you can use `%l[carry]'. The label must still be listed in the GOTOLABELS section when using this approach. ! Here is an example of `asm goto' for i386: asm goto ( "btl %1, %0\n\t" *************** GOTOLABELS section when using this appro *** 31228,31234 **** carry: return 1; ! The following example shows an 'asm goto' that uses a memory clobber. int frob(int x) { --- 31472,31478 ---- carry: return 1; ! The following example shows an `asm goto' that uses a memory clobber. int frob(int x) { *************** GOTOLABELS section when using this appro *** 31247,31255 **** .............................. References to input, output, and goto operands in the assembler template ! of extended 'asm' statements can use modifiers to affect the way the ! operands are formatted in the code output to the assembler. For ! example, the following code uses the 'h' and 'b' modifiers for x86: uint16_t num; asm volatile ("xchg %h0, %b0" : "+a" (num) ); --- 31491,31499 ---- .............................. References to input, output, and goto operands in the assembler template ! of extended `asm' statements can use modifiers to affect the way the ! operands are formatted in the code output to the assembler. For ! example, the following code uses the `h' and `b' modifiers for x86: uint16_t num; asm volatile ("xchg %h0, %b0" : "+a" (num) ); *************** purposes. *** 31275,31346 **** } With no modifiers, this is what the output from the operands would be ! for the 'att' and 'intel' dialects of assembler: Operand masm=att masm=intel ! --------------------------------------- ! '%0' '%eax' 'eax' ! '%1' '$2' '2' ! '%2' '$.L2' 'OFFSET ! FLAT:.L2' The table below shows the list of supported modifiers and their effects. ! Modifier Description Operand 'masm=att' 'masm=intel' ! ------------------------------------------------------------------------------------------ ! 'z' Print the opcode suffix for the size of '%z0' 'l' ! the current integer operand (one of ! 'b'/'w'/'l'/'q'). ! 'b' Print the QImode name of the register. '%b0' '%al' 'al' ! 'h' Print the QImode name for a "high" '%h0' '%ah' 'ah' ! register. ! 'w' Print the HImode name of the register. '%w0' '%ax' 'ax' ! 'k' Print the SImode name of the register. '%k0' '%eax' 'eax' ! 'q' Print the DImode name of the register. '%q0' '%rax' 'rax' ! 'l' Print the label name with no punctuation. '%l2' '.L2' '.L2' ! 'c' Require a constant operand and print the '%c1' '2' '2' ! constant expression with no punctuation. ! 6.44.2.9 x86 Floating-Point 'asm' Operands .......................................... On x86 targets, there are several rules on the usage of stack-like ! registers in the operands of an 'asm'. These rules apply only to the operands that are stack-like registers: ! 1. Given a set of input registers that die in an 'asm', it is ! necessary to know which are implicitly popped by the 'asm', and which must be explicitly popped by GCC. ! An input register that is implicitly popped by the 'asm' must be explicitly clobbered, unless it is constrained to match an output operand. ! 2. For any input register that is implicitly popped by an 'asm', it is necessary to know how to adjust the stack to compensate for the ! pop. If any non-popped input is closer to the top of the reg-stack ! than the implicitly popped register, it would not be possible to ! know what the stack looked like--it's not clear how the rest of the ! stack "slides up". All implicitly popped input registers must be closer to the top of the reg-stack than any input that is not implicitly popped. ! It is possible that if an input dies in an 'asm', the compiler might use the input register for an output reload. Consider this example: asm ("foo" : "=t" (a) : "f" (b)); ! This code says that input 'b' is not popped by the 'asm', and that ! the 'asm' pushes a result onto the reg-stack, i.e., the stack is ! one deeper after the 'asm' than it was before. But, it is possible ! that reload may think that it can use the same register for both ! the input and the output. ! To prevent this from happening, if any input operand uses the 'f' ! constraint, all output register constraints must use the '&' early-clobber modifier. The example above is correctly written as: --- 31519,31588 ---- } With no modifiers, this is what the output from the operands would be ! for the `att' and `intel' dialects of assembler: Operand masm=att masm=intel ! --------------------------------------- ! `%0' `%eax' `eax' ! `%1' `$2' `2' ! `%2' `$.L2' `OFFSET FLAT:.L2' The table below shows the list of supported modifiers and their effects. ! Modifier Description Operand `masm=att' `masm=intel' ! ------------------------------------------------------------------------------------------ ! `z' Print the opcode suffix for the size of the `%z0' `l' ! current integer operand (one of ! `b'/`w'/`l'/`q'). ! `b' Print the QImode name of the register. `%b0' `%al' `al' ! `h' Print the QImode name for a "high" register. `%h0' `%ah' `ah' ! `w' Print the HImode name of the register. `%w0' `%ax' `ax' ! `k' Print the SImode name of the register. `%k0' `%eax' `eax' ! `q' Print the DImode name of the register. `%q0' `%rax' `rax' ! `l' Print the label name with no punctuation. `%l2' `.L2' `.L2' ! `c' Require a constant operand and print the `%c1' `2' `2' ! constant expression with no punctuation. ! 6.44.2.9 x86 Floating-Point `asm' Operands .......................................... On x86 targets, there are several rules on the usage of stack-like ! registers in the operands of an `asm'. These rules apply only to the operands that are stack-like registers: ! 1. Given a set of input registers that die in an `asm', it is ! necessary to know which are implicitly popped by the `asm', and which must be explicitly popped by GCC. ! An input register that is implicitly popped by the `asm' must be explicitly clobbered, unless it is constrained to match an output operand. ! 2. For any input register that is implicitly popped by an `asm', it is necessary to know how to adjust the stack to compensate for the ! pop. If any non-popped input is closer to the top of the ! reg-stack than the implicitly popped register, it would not be ! possible to know what the stack looked like--it's not clear how ! the rest of the stack "slides up". All implicitly popped input registers must be closer to the top of the reg-stack than any input that is not implicitly popped. ! It is possible that if an input dies in an `asm', the compiler might use the input register for an output reload. Consider this example: asm ("foo" : "=t" (a) : "f" (b)); ! This code says that input `b' is not popped by the `asm', and that ! the `asm' pushes a result onto the reg-stack, i.e., the stack is ! one deeper after the `asm' than it was before. But, it is ! possible that reload may think that it can use the same register ! for both the input and the output. ! To prevent this from happening, if any input operand uses the `f' ! constraint, all output register constraints must use the `&' early-clobber modifier. The example above is correctly written as: *************** operands that are stack-like registers: *** 31348,31400 **** asm ("foo" : "=&t" (a) : "f" (b)); 3. Some operands need to be in particular places on the stack. All ! output operands fall in this category--GCC has no other way to know ! which registers the outputs appear in unless you indicate this in ! the constraints. Output operands must specifically indicate which register an output ! appears in after an 'asm'. '=f' is not allowed: the operand constraints must select a class with a single register. 4. Output operands may not be "inserted" between existing stack registers. Since no 387 opcode uses a read/write operand, all ! output operands are dead before the 'asm', and are pushed by the ! 'asm'. It makes no sense to push anywhere but the top of the reg-stack. Output operands must start at the top of the reg-stack: output operands may not "skip" a register. ! 5. Some 'asm' statements may need extra stack space for internal calculations. This can be guaranteed by clobbering stack registers unrelated to the inputs and outputs. ! This 'asm' takes one input, which is internally popped, and produces two outputs. asm ("fsincos" : "=t" (cos), "=u" (sin) : "0" (inp)); ! This 'asm' takes two inputs, which are popped by the 'fyl2xp1' opcode, ! and replaces them with one output. The 'st(1)' clobber is necessary for ! the compiler to know that 'fyl2xp1' pops both inputs. asm ("fyl2xp1" : "=t" (result) : "0" (x), "u" (y) : "st(1)");  File: gcc.info, Node: Constraints, Next: Asm Labels, Prev: Extended Asm, Up: Using Assembly Language with C ! 6.44.3 Constraints for 'asm' Operands ------------------------------------- Here are specific details on what constraint letters you can use with ! 'asm' operands. Constraints can say whether an operand may be in a register, and which kinds of register; whether the operand can be a ! memory reference, and which kinds of address; whether the operand may be ! an immediate constant, and which possible values it may have. ! Constraints can also require two operands to match. Side-effects aren't ! allowed in operands of inline 'asm', unless '<' or '>' constraints are ! used, because there is no guarantee that the side-effects will happen ! exactly once in an instruction that can update the addressing register. * Menu: --- 31590,31644 ---- asm ("foo" : "=&t" (a) : "f" (b)); 3. Some operands need to be in particular places on the stack. All ! output operands fall in this category--GCC has no other way to ! know which registers the outputs appear in unless you indicate ! this in the constraints. Output operands must specifically indicate which register an output ! appears in after an `asm'. `=f' is not allowed: the operand constraints must select a class with a single register. 4. Output operands may not be "inserted" between existing stack registers. Since no 387 opcode uses a read/write operand, all ! output operands are dead before the `asm', and are pushed by the ! `asm'. It makes no sense to push anywhere but the top of the reg-stack. Output operands must start at the top of the reg-stack: output operands may not "skip" a register. ! 5. Some `asm' statements may need extra stack space for internal calculations. This can be guaranteed by clobbering stack registers unrelated to the inputs and outputs. ! ! This `asm' takes one input, which is internally popped, and produces two outputs. asm ("fsincos" : "=t" (cos), "=u" (sin) : "0" (inp)); ! This `asm' takes two inputs, which are popped by the `fyl2xp1' opcode, ! and replaces them with one output. The `st(1)' clobber is necessary ! for the compiler to know that `fyl2xp1' pops both inputs. asm ("fyl2xp1" : "=t" (result) : "0" (x), "u" (y) : "st(1)");  File: gcc.info, Node: Constraints, Next: Asm Labels, Prev: Extended Asm, Up: Using Assembly Language with C ! 6.44.3 Constraints for `asm' Operands ------------------------------------- Here are specific details on what constraint letters you can use with ! `asm' operands. Constraints can say whether an operand may be in a register, and which kinds of register; whether the operand can be a ! memory reference, and which kinds of address; whether the operand may ! be an immediate constant, and which possible values it may have. ! Constraints can also require two operands to match. Side-effects ! aren't allowed in operands of inline `asm', unless `<' or `>' ! constraints are used, because there is no guarantee that the ! side-effects will happen exactly once in an instruction that can update ! the addressing register. * Menu: *************** whitespace *** 31420,31432 **** description even if they have different number of constraints and modifiers. ! 'm' A memory operand is allowed, with any kind of address that the machine supports in general. Note that the letter used for the ! general memory constraint can be re-defined by a back end using the ! 'TARGET_MEM_CONSTRAINT' macro. ! 'o' A memory operand is allowed, but only if the address is "offsettable". This means that adding a small integer (actually, the width in bytes of the operand, as determined by its machine --- 31664,31676 ---- description even if they have different number of constraints and modifiers. ! `m' A memory operand is allowed, with any kind of address that the machine supports in general. Note that the letter used for the ! general memory constraint can be re-defined by a back end using ! the `TARGET_MEM_CONSTRAINT' macro. ! `o' A memory operand is allowed, but only if the address is "offsettable". This means that adding a small integer (actually, the width in bytes of the operand, as determined by its machine *************** whitespace *** 31442,31551 **** on the other addressing modes that the machine supports. Note that in an output operand which can be matched by another ! operand, the constraint letter 'o' is valid only when accompanied ! by both '<' (if the target machine has predecrement addressing) and ! '>' (if the target machine has preincrement addressing). ! 'V' ! A memory operand that is not offsettable. In other words, anything ! that would fit the 'm' constraint but not the 'o' constraint. ! '<' ! A memory operand with autodecrement addressing (either predecrement ! or postdecrement) is allowed. In inline 'asm' this constraint is ! only allowed if the operand is used exactly once in an instruction ! that can handle the side-effects. Not using an operand with '<' in ! constraint string in the inline 'asm' pattern at all or using it in ! multiple instructions isn't valid, because the side-effects ! wouldn't be performed or would be performed more than once. ! Furthermore, on some targets the operand with '<' in constraint ! string must be accompanied by special instruction suffixes like ! '%U0' instruction suffix on PowerPC or '%P0' on IA-64. ! '>' ! A memory operand with autoincrement addressing (either preincrement ! or postincrement) is allowed. In inline 'asm' the same ! restrictions as for '<' apply. ! 'r' A register operand is allowed provided that it is in a general register. ! 'i' An immediate integer operand (one with constant value) is allowed. This includes symbolic constants whose values will be known only at assembly time or later. ! 'n' An immediate integer operand with a known numeric value is allowed. Many systems cannot support assembly-time constants for operands less than a word wide. Constraints for these operands should use ! 'n' rather than 'i'. ! 'I', 'J', 'K', ... 'P' ! Other letters in the range 'I' through 'P' may be defined in a machine-dependent fashion to permit immediate integer operands with explicit integer values in specified ranges. For example, on the ! 68000, 'I' is defined to stand for the range of values 1 to 8. This is the range permitted as a shift count in the shift instructions. ! 'E' ! An immediate floating operand (expression code 'const_double') is allowed, but only if the target floating point format is the same as that of the host machine (on which the compiler is running). ! 'F' ! An immediate floating operand (expression code 'const_double' or ! 'const_vector') is allowed. ! 'G', 'H' ! 'G' and 'H' may be defined in a machine-dependent fashion to permit ! immediate floating operands in particular ranges of values. ! 's' ! An immediate integer operand whose value is not an explicit integer ! is allowed. This might appear strange; if an insn allows a constant operand ! with a value not known at compile time, it certainly must allow any ! known value. So why use 's' instead of 'i'? Sometimes it allows ! better code to be generated. For example, on the 68000 in a fullword instruction it is possible to use an immediate operand; but if the immediate value is between -128 and 127, better code results from loading the value into a ! register and using the register. This is because the load into the ! register can be done with a 'moveq' instruction. We arrange for ! this to happen by defining the letter 'K' to mean "any integer ! outside the range -128 to 127", and then specifying 'Ks' in the operand constraints. ! 'g' Any register, memory or immediate integer operand is allowed, except for registers that are not general registers. ! 'X' Any operand whatsoever is allowed. ! '0', '1', '2', ... '9' An operand that matches the specified operand number is allowed. If a digit is used together with letters within the same alternative, the digit should come last. This number is allowed to be more than a single digit. If multiple digits are encountered consecutively, they are interpreted as a ! single decimal integer. There is scant chance for ambiguity, since ! to-date it has never been desirable that '10' be interpreted as ! matching either operand 1 _or_ operand 0. Should this be desired, ! one can use multiple alternatives instead. This is called a "matching constraint" and what it really means is that the assembler has only a single operand that fills two roles ! which 'asm' distinguishes. For example, an add instruction uses ! two input operands and an output operand, but on most CISC machines ! an add instruction really has only two operands, one of them an ! input-output operand: addl #35,r12 --- 31686,31797 ---- on the other addressing modes that the machine supports. Note that in an output operand which can be matched by another ! operand, the constraint letter `o' is valid only when accompanied ! by both `<' (if the target machine has predecrement addressing) ! and `>' (if the target machine has preincrement addressing). ! `V' ! A memory operand that is not offsettable. In other words, ! anything that would fit the `m' constraint but not the `o' ! constraint. ! `<' ! A memory operand with autodecrement addressing (either ! predecrement or postdecrement) is allowed. In inline `asm' this ! constraint is only allowed if the operand is used exactly once in ! an instruction that can handle the side-effects. Not using an ! operand with `<' in constraint string in the inline `asm' pattern ! at all or using it in multiple instructions isn't valid, because ! the side-effects wouldn't be performed or would be performed more ! than once. Furthermore, on some targets the operand with `<' in ! constraint string must be accompanied by special instruction ! suffixes like `%U0' instruction suffix on PowerPC or `%P0' on ! IA-64. ! `>' ! A memory operand with autoincrement addressing (either ! preincrement or postincrement) is allowed. In inline `asm' the ! same restrictions as for `<' apply. ! `r' A register operand is allowed provided that it is in a general register. ! `i' An immediate integer operand (one with constant value) is allowed. This includes symbolic constants whose values will be known only at assembly time or later. ! `n' An immediate integer operand with a known numeric value is allowed. Many systems cannot support assembly-time constants for operands less than a word wide. Constraints for these operands should use ! `n' rather than `i'. ! `I', `J', `K', ... `P' ! Other letters in the range `I' through `P' may be defined in a machine-dependent fashion to permit immediate integer operands with explicit integer values in specified ranges. For example, on the ! 68000, `I' is defined to stand for the range of values 1 to 8. This is the range permitted as a shift count in the shift instructions. ! `E' ! An immediate floating operand (expression code `const_double') is allowed, but only if the target floating point format is the same as that of the host machine (on which the compiler is running). ! `F' ! An immediate floating operand (expression code `const_double' or ! `const_vector') is allowed. ! `G', `H' ! `G' and `H' may be defined in a machine-dependent fashion to ! permit immediate floating operands in particular ranges of values. ! `s' ! An immediate integer operand whose value is not an explicit ! integer is allowed. This might appear strange; if an insn allows a constant operand ! with a value not known at compile time, it certainly must allow ! any known value. So why use `s' instead of `i'? Sometimes it ! allows better code to be generated. For example, on the 68000 in a fullword instruction it is possible to use an immediate operand; but if the immediate value is between -128 and 127, better code results from loading the value into a ! register and using the register. This is because the load into ! the register can be done with a `moveq' instruction. We arrange ! for this to happen by defining the letter `K' to mean "any integer ! outside the range -128 to 127", and then specifying `Ks' in the operand constraints. ! `g' Any register, memory or immediate integer operand is allowed, except for registers that are not general registers. ! `X' Any operand whatsoever is allowed. ! `0', `1', `2', ... `9' An operand that matches the specified operand number is allowed. If a digit is used together with letters within the same alternative, the digit should come last. This number is allowed to be more than a single digit. If multiple digits are encountered consecutively, they are interpreted as a ! single decimal integer. There is scant chance for ambiguity, ! since to-date it has never been desirable that `10' be interpreted ! as matching either operand 1 _or_ operand 0. Should this be ! desired, one can use multiple alternatives instead. This is called a "matching constraint" and what it really means is that the assembler has only a single operand that fills two roles ! which `asm' distinguishes. For example, an add instruction uses ! two input operands and an output operand, but on most CISC ! machines an add instruction really has only two operands, one of ! them an input-output operand: addl #35,r12 *************** whitespace *** 31555,31573 **** smaller number than the number of the operand that uses it in the constraint. ! 'p' An operand that is a valid memory address is allowed. This is for "load address" and "push address" instructions. ! 'p' in the constraint must be accompanied by 'address_operand' as ! the predicate in the 'match_operand'. This predicate interprets ! the mode specified in the 'match_operand' as the mode of the memory reference for which the address would be valid. OTHER-LETTERS Other letters can be defined in machine-dependent fashion to stand for particular classes of registers or other arbitrary operand ! types. 'd', 'a' and 'f' are defined on the 68000/68020 to stand for data, address and floating point registers.  --- 31801,31819 ---- smaller number than the number of the operand that uses it in the constraint. ! `p' An operand that is a valid memory address is allowed. This is for "load address" and "push address" instructions. ! `p' in the constraint must be accompanied by `address_operand' as ! the predicate in the `match_operand'. This predicate interprets ! the mode specified in the `match_operand' as the mode of the memory reference for which the address would be valid. OTHER-LETTERS Other letters can be defined in machine-dependent fashion to stand for particular classes of registers or other arbitrary operand ! types. `d', `a' and `f' are defined on the 68000/68020 to stand for data, address and floating point registers.  *************** alternative. All operands for a single *** 31591,31607 **** number of alternatives. So the first alternative for the 68000's logical-or could be written as ! '"+m" (output) : "ir" (input)'. The second could be '"+r" (output): "irm" (input)'. However, the fact that two memory locations cannot be ! used in a single instruction prevents simply using '"+rm" (output) : "irm" (input)'. Using multi-alternatives, this might be written as ! '"+m,r" (output) : "ir,irm" (input)'. This describes all the available alternatives to the compiler, allowing it to choose the most efficient one for the current conditions. There is no way within the template to determine which alternative was ! chosen. However you may be able to wrap your 'asm' statements with ! builtins such as '__builtin_constant_p' to achieve the desired results.  File: gcc.info, Node: Modifiers, Next: Machine Constraints, Prev: Multi-Alternative, Up: Constraints --- 31837,31853 ---- number of alternatives. So the first alternative for the 68000's logical-or could be written as ! `"+m" (output) : "ir" (input)'. The second could be `"+r" (output): "irm" (input)'. However, the fact that two memory locations cannot be ! used in a single instruction prevents simply using `"+rm" (output) : "irm" (input)'. Using multi-alternatives, this might be written as ! `"+m,r" (output) : "ir,irm" (input)'. This describes all the available alternatives to the compiler, allowing it to choose the most efficient one for the current conditions. There is no way within the template to determine which alternative was ! chosen. However you may be able to wrap your `asm' statements with ! builtins such as `__builtin_constant_p' to achieve the desired results.  File: gcc.info, Node: Modifiers, Next: Machine Constraints, Prev: Multi-Alternative, Up: Constraints *************** File: gcc.info, Node: Modifiers, Next: *** 31611,31672 **** Here are constraint modifier characters. ! '=' Means that this operand is written to by this instruction: the previous value is discarded and replaced by new data. ! '+' Means that this operand is both read and written by the instruction. When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are read by the instruction and ! which are written by it. '=' identifies an operand which is only ! written; '+' identifies an operand that is both read and written; all other operands are assumed to only be read. ! If you specify '=' or '+' in a constraint, you put it in the first character of the constraint string. ! '&' Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is written before the instruction is ! finished using the input operands. Therefore, this operand may not ! lie in a register that is read by the instruction or as part of any ! memory address. ! '&' applies only to the alternative in which it is written. In constraints with multiple alternatives, sometimes one alternative ! requires '&' while others do not. See, for example, the 'movdf' insn of the 68000. A operand which is read by the instruction can be tied to an earlyclobber operand if its only use as an input occurs before the early result is written. Adding alternatives of this form often allows GCC to produce better code when only some of the read ! operands can be affected by the earlyclobber. See, for example, ! the 'mulsi3' insn of the ARM. Furthermore, if the "earlyclobber" operand is also a read/write operand, then that operand is written only after it's used. ! '&' does not obviate the need to write '=' or '+'. As "earlyclobber" operands are always written, a read-only "earlyclobber" operand is ill-formed and will be rejected by the compiler. ! '%' Declares the instruction to be commutative for this operand and the following operand. This means that the compiler may interchange the two operands if that is the cheapest way to make all operands ! fit the constraints. '%' applies to all alternatives and must appear as the first character in the constraint. Only read-only ! operands can use '%'. GCC can only handle one commutative pair in an asm; if you use more, the compiler may fail. Note that you need not use the ! modifier if the two alternatives are strictly identical; this would ! only waste time in the reload pass.  File: gcc.info, Node: Machine Constraints, Prev: Modifiers, Up: Constraints --- 31857,31918 ---- Here are constraint modifier characters. ! `=' Means that this operand is written to by this instruction: the previous value is discarded and replaced by new data. ! `+' Means that this operand is both read and written by the instruction. When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are read by the instruction and ! which are written by it. `=' identifies an operand which is only ! written; `+' identifies an operand that is both read and written; all other operands are assumed to only be read. ! If you specify `=' or `+' in a constraint, you put it in the first character of the constraint string. ! `&' Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is written before the instruction is ! finished using the input operands. Therefore, this operand may ! not lie in a register that is read by the instruction or as part ! of any memory address. ! `&' applies only to the alternative in which it is written. In constraints with multiple alternatives, sometimes one alternative ! requires `&' while others do not. See, for example, the `movdf' insn of the 68000. A operand which is read by the instruction can be tied to an earlyclobber operand if its only use as an input occurs before the early result is written. Adding alternatives of this form often allows GCC to produce better code when only some of the read ! operands can be affected by the earlyclobber. See, for example, ! the `mulsi3' insn of the ARM. Furthermore, if the "earlyclobber" operand is also a read/write operand, then that operand is written only after it's used. ! `&' does not obviate the need to write `=' or `+'. As "earlyclobber" operands are always written, a read-only "earlyclobber" operand is ill-formed and will be rejected by the compiler. ! `%' Declares the instruction to be commutative for this operand and the following operand. This means that the compiler may interchange the two operands if that is the cheapest way to make all operands ! fit the constraints. `%' applies to all alternatives and must appear as the first character in the constraint. Only read-only ! operands can use `%'. GCC can only handle one commutative pair in an asm; if you use more, the compiler may fail. Note that you need not use the ! modifier if the two alternatives are strictly identical; this ! would only waste time in the reload pass.  File: gcc.info, Node: Machine Constraints, Prev: Modifiers, Up: Constraints *************** File: gcc.info, Node: Machine Constrain *** 31675,33050 **** ............................................ Whenever possible, you should use the general-purpose constraint letters ! in 'asm' arguments, since they will convey meaning more readily to ! people reading your code. Failing that, use the constraint letters that ! usually have very similar meanings across architectures. The most ! commonly used constraints are 'm' and 'r' (for memory and general-purpose registers respectively; *note Simple Constraints::), and ! 'I', usually the letter indicating the most common immediate-constant format. Each architecture defines additional constraints. These constraints are used by the compiler itself for instruction generation, as well as ! for 'asm' statements; therefore, some of the constraints are not ! particularly useful for 'asm'. Here is a summary of some of the machine-dependent constraints available on some particular machines; it ! includes both constraints that are useful for 'asm' and constraints that ! aren't. The compiler source file mentioned in the table heading for ! each architecture is the definitive reference for the meanings of that ! architecture's constraints. ! _AArch64 family--'config/aarch64/constraints.md'_ ! 'k' ! The stack pointer register ('SP') ! 'w' Floating point or SIMD vector register ! 'I' Integer constant that is valid as an immediate operand in an ! 'ADD' instruction ! 'J' Integer constant that is valid as an immediate operand in a ! 'SUB' instruction (once negated) ! 'K' Integer constant that can be used with a 32-bit logical instruction ! 'L' Integer constant that can be used with a 64-bit logical instruction ! 'M' Integer constant that is valid as an immediate operand in a ! 32-bit 'MOV' pseudo instruction. The 'MOV' may be assembled to one of several different machine instructions depending on the value ! 'N' Integer constant that is valid as an immediate operand in a ! 64-bit 'MOV' pseudo instruction ! 'S' An absolute symbolic address or a label reference ! 'Y' Floating point constant zero ! 'Z' Integer constant zero ! 'Ush' ! The high part (bits 12 and upwards) of the pc-relative address ! of a symbol within 4GB of the instruction ! 'Q' A memory address which uses a single base register with no offset ! 'Ump' ! A memory address suitable for a load/store pair instruction in ! SI, DI, SF and DF modes ! _ARC --'config/arc/constraints.md'_ ! 'q' ! Registers usable in ARCompact 16-bit instructions: 'r0'-'r3', ! 'r12'-'r15'. This constraint can only match when the '-mq' option is in effect. ! 'e' ! Registers usable as base-regs of memory addresses in ARCompact ! 16-bit memory instructions: 'r0'-'r3', 'r12'-'r15', 'sp'. ! This constraint can only match when the '-mq' option is in ! effect. ! 'D' ! ARC FPX (dpfp) 64-bit registers. 'D0', 'D1'. ! 'I' A signed 12-bit integer constant. ! 'Cal' ! constant for arithmetic/logical operations. This might be any ! constant that can be put into a long immediate by the assmbler ! or linker without involving a PIC relocation. ! 'K' A 3-bit unsigned integer constant. ! 'L' A 6-bit unsigned integer constant. ! 'CnL' One's complement of a 6-bit unsigned integer constant. ! 'CmL' Two's complement of a 6-bit unsigned integer constant. ! 'M' A 5-bit unsigned integer constant. ! 'O' A 7-bit unsigned integer constant. ! 'P' A 8-bit unsigned integer constant. ! 'H' Any const_double value. ! _ARM family--'config/arm/constraints.md'_ ! 'h' ! In Thumb state, the core registers 'r8'-'r15'. ! 'k' The stack pointer register. ! 'l' ! In Thumb State the core registers 'r0'-'r7'. In ARM state ! this is an alias for the 'r' constraint. ! 't' ! VFP floating-point registers 's0'-'s31'. Used for 32 bit values. ! 'w' ! VFP floating-point registers 'd0'-'d31' and the appropriate ! subset 'd0'-'d15' based on command line options. Used for 64 bit values only. Not valid for Thumb1. ! 'y' The iWMMX co-processor registers. ! 'z' The iWMMX GR registers. ! 'G' The floating-point constant 0.0 ! 'I' Integer that is valid as an immediate operand in a data ! processing instruction. That is, an integer in the range 0 to ! 255 rotated by a multiple of 2 ! 'J' Integer in the range -4095 to 4095 ! 'K' ! Integer that satisfies constraint 'I' when inverted (ones complement) ! 'L' ! Integer that satisfies constraint 'I' when negated (twos complement) ! 'M' Integer in the range 0 to 32 ! 'Q' A memory reference where the exact address is in a single ! register (''m'' is preferable for 'asm' statements) ! 'R' An item in the constant pool ! 'S' A symbol in the text segment of the current file ! 'Uv' A memory reference suitable for VFP load/store insns (reg+constant offset) ! 'Uy' A memory reference suitable for iWMMXt load/store instructions. ! 'Uq' A memory reference suitable for the ARMv4 ldrsb instruction. ! _AVR family--'config/avr/constraints.md'_ ! 'l' Registers from r0 to r15 ! 'a' Registers from r16 to r23 ! 'd' Registers from r16 to r31 ! 'w' Registers from r24 to r31. These registers can be used in ! 'adiw' command ! 'e' Pointer register (r26-r31) ! 'b' Base pointer register (r28-r31) ! 'q' Stack pointer register (SPH:SPL) ! 't' Temporary register r0 ! 'x' Register pair X (r27:r26) ! 'y' Register pair Y (r29:r28) ! 'z' Register pair Z (r31:r30) ! 'I' Constant greater than -1, less than 64 ! 'J' Constant greater than -64, less than 1 ! 'K' Constant integer 2 ! 'L' Constant integer 0 ! 'M' Constant that fits in 8 bits ! 'N' Constant integer -1 ! 'O' Constant integer 8, 16, or 24 ! 'P' Constant integer 1 ! 'G' A floating point constant 0.0 ! 'Q' A memory address based on Y or Z pointer with displacement. ! _Blackfin family--'config/bfin/constraints.md'_ ! 'a' P register ! 'd' D register ! 'z' A call clobbered P register. ! 'qN' A single register. If N is in the range 0 to 7, the ! corresponding D register. If it is 'A', then the register P0. ! 'D' Even-numbered D register ! 'W' Odd-numbered D register ! 'e' Accumulator register. ! 'A' Even-numbered accumulator register. ! 'B' Odd-numbered accumulator register. ! 'b' I register ! 'v' B register ! 'f' M register ! 'c' ! Registers used for circular buffering, i.e. I, B, or L registers. ! 'C' The CC register. ! 't' LT0 or LT1. ! 'k' LC0 or LC1. ! 'u' LB0 or LB1. ! 'x' Any D, P, B, M, I or L register. ! 'y' Additional registers typically used only in prologues and epilogues: RETS, RETN, RETI, RETX, RETE, ASTAT, SEQSTAT and USP. ! 'w' Any register except accumulators or CC. ! 'Ksh' Signed 16 bit integer (in the range -32768 to 32767) ! 'Kuh' Unsigned 16 bit integer (in the range 0 to 65535) ! 'Ks7' Signed 7 bit integer (in the range -64 to 63) ! 'Ku7' Unsigned 7 bit integer (in the range 0 to 127) ! 'Ku5' Unsigned 5 bit integer (in the range 0 to 31) ! 'Ks4' Signed 4 bit integer (in the range -8 to 7) ! 'Ks3' Signed 3 bit integer (in the range -3 to 4) ! 'Ku3' Unsigned 3 bit integer (in the range 0 to 7) ! 'PN' Constant N, where N is a single-digit constant in the range 0 to 4. ! 'PA' An integer equal to one of the MACFLAG_XXX constants that is suitable for use with either accumulator. ! 'PB' An integer equal to one of the MACFLAG_XXX constants that is suitable for use only with accumulator A1. ! 'M1' Constant 255. ! 'M2' Constant 65535. ! 'J' An integer constant with exactly a single bit set. ! 'L' An integer constant with all bits set except exactly one. ! 'H' ! 'Q' Any SYMBOL_REF. ! _CR16 Architecture--'config/cr16/cr16.h'_ ! 'b' Registers from r0 to r14 (registers without stack pointer) ! 't' Register from r0 to r11 (all 16-bit registers) ! 'p' Register from r12 to r15 (all 32-bit registers) ! 'I' Signed constant that fits in 4 bits ! 'J' Signed constant that fits in 5 bits ! 'K' Signed constant that fits in 6 bits ! 'L' Unsigned constant that fits in 4 bits ! 'M' Signed constant that fits in 32 bits ! 'N' Check for 64 bits wide constants for add/sub instructions ! 'G' Floating point constant that is legal for store immediate ! _Epiphany--'config/epiphany/constraints.md'_ ! 'U16' An unsigned 16-bit constant. ! 'K' An unsigned 5-bit constant. ! 'L' A signed 11-bit constant. ! 'Cm1' ! A signed 11-bit constant added to -1. Can only match when the ! '-m1reg-REG' option is active. ! 'Cl1' Left-shift of -1, i.e., a bit mask with a block of leading ones, the rest being a block of trailing zeroes. Can only ! match when the '-m1reg-REG' option is active. ! 'Cr1' Right-shift of -1, i.e., a bit mask with a trailing block of ones, the rest being zeroes. Or to put it another way, one less than a power of two. Can only match when the ! '-m1reg-REG' option is active. ! 'Cal' ! Constant for arithmetic/logical operations. This is like 'i', ! except that for position independent code, no symbols / expressions needing relocations are allowed. ! 'Csy' Symbolic constant for call/jump instruction. ! 'Rcs' The register class usable in short insns. This is a register class constraint, and can thus drive register allocation. ! This constraint won't match unless '-mprefer-short-insn-regs' is in effect. ! 'Rsc' The the register class of registers that can be used to hold a sibcall call address. I.e., a caller-saved register. ! 'Rct' Core control register class. ! 'Rgs' The register group usable in short insns. This constraint does not use a register class, so that it only passively matches suitable registers, and doesn't drive register allocation. ! 'Rra' ! Matches the return address if it can be replaced with the link ! register. ! 'Rcc' Matches the integer condition code register. ! 'Sra' Matches the return address if it is in a stack slot. ! 'Cfm' Matches control register values to switch fp mode, which are ! encapsulated in 'UNSPEC_FP_MODE'. ! _FRV--'config/frv/frv.h'_ ! 'a' ! Register in the class 'ACC_REGS' ('acc0' to 'acc7'). ! 'b' ! Register in the class 'EVEN_ACC_REGS' ('acc0' to 'acc7'). ! 'c' ! Register in the class 'CC_REGS' ('fcc0' to 'fcc3' and 'icc0' ! to 'icc3'). ! 'd' ! Register in the class 'GPR_REGS' ('gr0' to 'gr63'). ! 'e' ! Register in the class 'EVEN_REGS' ('gr0' to 'gr63'). Odd ! registers are excluded not in the class but through the use of ! a machine mode larger than 4 bytes. ! 'f' ! Register in the class 'FPR_REGS' ('fr0' to 'fr63'). ! 'h' ! Register in the class 'FEVEN_REGS' ('fr0' to 'fr63'). Odd ! registers are excluded not in the class but through the use of ! a machine mode larger than 4 bytes. ! 'l' ! Register in the class 'LR_REG' (the 'lr' register). ! 'q' ! Register in the class 'QUAD_REGS' ('gr2' to 'gr63'). Register ! numbers not divisible by 4 are excluded not in the class but ! through the use of a machine mode larger than 8 bytes. ! 't' ! Register in the class 'ICC_REGS' ('icc0' to 'icc3'). ! 'u' ! Register in the class 'FCC_REGS' ('fcc0' to 'fcc3'). ! 'v' ! Register in the class 'ICR_REGS' ('cc4' to 'cc7'). ! 'w' ! Register in the class 'FCR_REGS' ('cc0' to 'cc3'). ! 'x' ! Register in the class 'QUAD_FPR_REGS' ('fr0' to 'fr63'). Register numbers not divisible by 4 are excluded not in the class but through the use of a machine mode larger than 8 bytes. ! 'z' ! Register in the class 'SPR_REGS' ('lcr' and 'lr'). ! 'A' ! Register in the class 'QUAD_ACC_REGS' ('acc0' to 'acc7'). ! 'B' ! Register in the class 'ACCG_REGS' ('accg0' to 'accg7'). ! 'C' ! Register in the class 'CR_REGS' ('cc0' to 'cc7'). ! 'G' Floating point constant zero ! 'I' 6-bit signed integer constant ! 'J' 10-bit signed integer constant ! 'L' 16-bit signed integer constant ! 'M' 16-bit unsigned integer constant ! 'N' 12-bit signed integer constant that is negative--i.e. in the range of -2048 to -1 ! 'O' Constant zero ! 'P' ! 12-bit signed integer constant that is greater than zero--i.e. ! in the range of 1 to 2047. ! _FT32--'config/ft32/constraints.md'_ ! 'A' An absolute address ! 'B' An offset address ! 'W' A register indirect memory operand ! 'e' An offset address. ! 'f' An offset address. ! 'O' The constant zero or one ! 'I' A 16-bit signed constant (-32768 ... 32767) ! 'w' A bitfield mask suitable for bext or bins ! 'x' An inverted bitfield mask suitable for bext or bins ! 'L' A 16-bit unsigned constant, multiple of 4 (0 ... 65532) ! 'S' A 20-bit signed constant (-524288 ... 524287) ! 'b' A constant for a bitfield width (1 ... 16) ! 'KA' A 10-bit signed constant (-512 ... 511) ! _Hewlett-Packard PA-RISC--'config/pa/pa.h'_ ! 'a' General register 1 ! 'f' Floating point register ! 'q' Shift amount register ! 'x' Floating point register (deprecated) ! 'y' Upper floating point register (32-bit), floating point register (64-bit) ! 'Z' Any register ! 'I' Signed 11-bit integer constant ! 'J' Signed 14-bit integer constant ! 'K' ! Integer constant that can be deposited with a 'zdepi' instruction ! 'L' Signed 5-bit integer constant ! 'M' Integer constant 0 ! 'N' ! Integer constant that can be loaded with a 'ldil' instruction ! 'O' Integer constant whose value plus one is a power of 2 ! 'P' ! Integer constant that can be used for 'and' operations in ! 'depi' and 'extru' instructions ! 'S' Integer constant 31 ! 'U' Integer constant 63 ! 'G' Floating-point constant 0.0 ! 'A' ! A 'lo_sum' data-linkage-table memory operand ! 'Q' A memory operand that can be used as the destination operand of an integer store instruction ! 'R' A scaled or unscaled indexed memory operand ! 'T' A memory operand for floating-point loads and stores ! 'W' A register indirect memory operand ! _Intel IA-64--'config/ia64/ia64.h'_ ! 'a' ! General register 'r0' to 'r3' for 'addl' instruction ! 'b' Branch register ! 'c' ! Predicate register ('c' as in "conditional") ! 'd' Application register residing in M-unit ! 'e' Application register residing in I-unit ! 'f' Floating-point register ! 'm' ! Memory operand. If used together with '<' or '>', the operand ! can have postincrement and postdecrement which require ! printing with '%Pn' on IA-64. ! 'G' Floating-point constant 0.0 or 1.0 ! 'I' 14-bit signed integer constant ! 'J' 22-bit signed integer constant ! 'K' 8-bit signed integer constant for logical instructions ! 'L' 8-bit adjusted signed integer constant for compare pseudo-ops ! 'M' 6-bit unsigned integer constant for shift counts ! 'N' 9-bit signed integer constant for load and store postincrements ! 'O' The constant zero ! 'P' ! 0 or -1 for 'dep' instruction ! 'Q' Non-volatile memory for floating-point loads and stores ! 'R' ! Integer constant in the range 1 to 4 for 'shladd' instruction ! 'S' Memory operand except postincrement and postdecrement. This ! is now roughly the same as 'm' when not used together with '<' ! or '>'. ! _M32C--'config/m32c/m32c.c'_ ! 'Rsp' ! 'Rfb' ! 'Rsb' ! '$sp', '$fb', '$sb'. ! 'Rcr' Any control register, when they're 16 bits wide (nothing if control registers are 24 bits wide) ! 'Rcl' Any control register, when they're 24 bits wide. ! 'R0w' ! 'R1w' ! 'R2w' ! 'R3w' $r0, $r1, $r2, $r3. ! 'R02' $r0 or $r2, or $r2r0 for 32 bit values. ! 'R13' $r1 or $r3, or $r3r1 for 32 bit values. ! 'Rdi' A register that can hold a 64 bit value. ! 'Rhl' $r0 or $r1 (registers with addressable high/low bytes) ! 'R23' $r2 or $r3 ! 'Raa' Address registers ! 'Raw' Address registers when they're 16 bits wide. ! 'Ral' Address registers when they're 24 bits wide. ! 'Rqi' Registers that can hold QI values. ! 'Rad' Registers that can be used with displacements ($a0, $a1, $sb). ! 'Rsi' Registers that can hold 32 bit values. ! 'Rhi' Registers that can hold 16 bit values. ! 'Rhc' Registers chat can hold 16 bit values, including all control registers. ! 'Rra' $r0 through R1, plus $a0 and $a1. ! 'Rfl' The flags register. ! 'Rmm' The memory-based pseudo-registers $mem0 through $mem15. ! 'Rpi' Registers that can hold pointers (16 bit registers for r8c, m16c; 24 bit registers for m32cm, m32c). ! 'Rpa' Matches multiple registers in a PARALLEL to form a larger register. Used to match function return values. ! 'Is3' -8 ... 7 ! 'IS1' -128 ... 127 ! 'IS2' -32768 ... 32767 ! 'IU2' 0 ... 65535 ! 'In4' -8 ... -1 or 1 ... 8 ! 'In5' -16 ... -1 or 1 ... 16 ! 'In6' -32 ... -1 or 1 ... 32 ! 'IM2' -65536 ... -1 ! 'Ilb' An 8 bit value with exactly one bit set. ! 'Ilw' A 16 bit value with exactly one bit set. ! 'Sd' The common src/dest memory addressing modes. ! 'Sa' Memory addressed using $a0 or $a1. ! 'Si' Memory addressed with immediate addresses. ! 'Ss' Memory addressed using the stack pointer ($sp). ! 'Sf' Memory addressed using the frame base register ($fb). ! 'Ss' Memory addressed using the small base register ($sb). ! 'S1' $r1h ! _MeP--'config/mep/constraints.md'_ ! 'a' The $sp register. ! 'b' The $tp register. ! 'c' Any control register. ! 'd' Either the $hi or the $lo register. ! 'em' Coprocessor registers that can be directly loaded ($c0-$c15). ! 'ex' Coprocessor registers that can be moved to each other. ! 'er' Coprocessor registers that can be moved to core registers. ! 'h' The $hi register. ! 'j' The $rpc register. ! 'l' The $lo register. ! 't' Registers which can be used in $tp-relative addressing. ! 'v' The $gp register. ! 'x' The coprocessor registers. ! 'y' The coprocessor control registers. ! 'z' The $0 register. ! 'A' User-defined register set A. ! 'B' User-defined register set B. ! 'C' User-defined register set C. ! 'D' User-defined register set D. ! 'I' Offsets for $gp-rel addressing. ! 'J' Constants that can be used directly with boolean insns. ! 'K' Constants that can be moved directly to registers. ! 'L' Small constants that can be added to registers. ! 'M' Long shift counts. ! 'N' Small constants that can be compared to registers. ! 'O' Constants that can be loaded into the top half of registers. ! 'S' Signed 8-bit immediates. ! 'T' Symbols encoded for $tp-rel or $gp-rel addressing. ! 'U' Non-constant addresses for loading/saving coprocessor registers. ! 'W' The top half of a symbol's value. ! 'Y' A register indirect address without offset. ! 'Z' Symbolic references to the control bus. - _MicroBlaze--'config/microblaze/constraints.md'_ - 'd' - A general register ('r0' to 'r31'). ! 'z' ! A status register ('rmsr', '$fcc1' to '$fcc7'). ! _MIPS--'config/mips/constraints.md'_ ! 'd' ! An address register. This is equivalent to 'r' unless generating MIPS16 code. ! 'f' A floating-point register (if available). ! 'h' ! Formerly the 'hi' register. This constraint is no longer supported. ! 'l' ! The 'lo' register. Use this register to store values that are no bigger than a word. ! 'x' ! The concatenated 'hi' and 'lo' registers. Use this register to store doubleword values. ! 'c' A register suitable for use in an indirect jump. This will ! always be '$25' for '-mabicalls'. ! 'v' ! Register '$3'. Do not use this constraint in new code; it is retained only for compatibility with glibc. ! 'y' ! Equivalent to 'r'; retained for backwards compatibility. ! 'z' A floating-point condition code register. ! 'I' A signed 16-bit constant (for arithmetic instructions). ! 'J' Integer zero. ! 'K' An unsigned 16-bit constant (for logic instructions). ! 'L' A signed 32-bit constant in which the lower 16 bits are zero. ! Such constants can be loaded using 'lui'. ! 'M' ! A constant that cannot be loaded using 'lui', 'addiu' or ! 'ori'. ! 'N' A constant in the range -65535 to -1 (inclusive). ! 'O' A signed 15-bit constant. ! 'P' A constant in the range 1 to 65535 (inclusive). ! 'G' Floating-point zero. ! 'R' An address that can be used in a non-macro load or store. ! 'ZC' A memory operand whose address is formed by a base register and offset that is suitable for use in instructions with the ! same addressing mode as 'll' and 'sc'. ! 'ZD' ! An address suitable for a 'prefetch' instruction, or for any ! other instruction with the same addressing mode as 'prefetch'. ! _Motorola 680x0--'config/m68k/constraints.md'_ ! 'a' Address register ! 'd' Data register ! 'f' 68881 floating-point register, if available ! 'I' Integer in the range 1 to 8 ! 'J' 16-bit signed number ! 'K' Signed number whose magnitude is greater than 0x80 ! 'L' Integer in the range -8 to -1 ! 'M' Signed number whose magnitude is greater than 0x100 ! 'N' Range 24 to 31, rotatert:SI 8 to 1 expressed as rotate ! 'O' 16 (for rotate using swap) ! 'P' Range 8 to 15, rotatert:HI 8 to 1 expressed as rotate ! 'R' Numbers that mov3q can handle ! 'G' Floating point constant that is not a 68881 constant ! 'S' Operands that satisfy 'm' when -mpcrel is in effect ! 'T' Operands that satisfy 's' when -mpcrel is not in effect ! 'Q' Address register indirect addressing mode ! 'U' Register offset addressing ! 'W' const_call_operand ! 'Cs' symbol_ref or const ! 'Ci' const_int ! 'C0' const_int 0 ! 'Cj' Range of signed numbers that don't fit in 16 bits ! 'Cmvq' Integers valid for mvq ! 'Capsw' Integers valid for a moveq followed by a swap ! 'Cmvz' Integers valid for mvz ! 'Cmvs' Integers valid for mvs ! 'Ap' push_operand ! 'Ac' Non-register operands allowed in clr ! _Moxie--'config/moxie/constraints.md'_ ! 'A' An absolute address ! 'B' An offset address ! 'W' A register indirect memory operand ! 'I' A constant in the range of 0 to 255. ! 'N' A constant in the range of 0 to -255. - _MSP430-'config/msp430/constraints.md'_ ! 'R12' Register R12. ! 'R13' Register R13. ! 'K' Integer constant 1. ! 'L' Integer constant -1^20..1^19. ! 'M' Integer constant 1-4. ! 'Ya' Memory references which do not require an extended MOVX instruction. ! 'Yl' Memory reference, labels only. ! 'Ys' Memory reference, stack only. ! _NDS32--'config/nds32/constraints.md'_ ! 'w' LOW register class $r0 to $r7 constraint for V3/V3M ISA. ! 'l' LOW register class $r0 to $r7. ! 'd' MIDDLE register class $r0 to $r11, $r16 to $r19. ! 'h' HIGH register class $r12 to $r14, $r20 to $r31. ! 't' Temporary assist register $ta (i.e. $r15). ! 'k' Stack register $sp. ! 'Iu03' Unsigned immediate 3-bit value. ! 'In03' Negative immediate 3-bit value in the range of -7-0. ! 'Iu04' Unsigned immediate 4-bit value. ! 'Is05' Signed immediate 5-bit value. ! 'Iu05' Unsigned immediate 5-bit value. ! 'In05' Negative immediate 5-bit value in the range of -31-0. ! 'Ip05' Unsigned immediate 5-bit value for movpi45 instruction with range 16-47. ! 'Iu06' Unsigned immediate 6-bit value constraint for addri36.sp instruction. ! 'Iu08' Unsigned immediate 8-bit value. ! 'Iu09' Unsigned immediate 9-bit value. ! 'Is10' Signed immediate 10-bit value. ! 'Is11' Signed immediate 11-bit value. ! 'Is15' Signed immediate 15-bit value. ! 'Iu15' Unsigned immediate 15-bit value. ! 'Ic15' ! A constant which is not in the range of imm15u but ok for bclr ! instruction. ! 'Ie15' ! A constant which is not in the range of imm15u but ok for bset ! instruction. ! 'It15' ! A constant which is not in the range of imm15u but ok for btgl ! instruction. ! 'Ii15' A constant whose compliment value is in the range of imm15u and ok for bitci instruction. ! 'Is16' Signed immediate 16-bit value. ! 'Is17' Signed immediate 17-bit value. ! 'Is19' Signed immediate 19-bit value. ! 'Is20' Signed immediate 20-bit value. ! 'Ihig' The immediate value that can be simply set high 20-bit. ! 'Izeb' The immediate value 0xff. ! 'Izeh' The immediate value 0xffff. ! 'Ixls' The immediate value 0x01. ! 'Ix11' The immediate value 0x7ff. ! 'Ibms' The immediate value with power of 2. ! 'Ifex' The immediate value with power of 2 minus 1. ! 'U33' Memory constraint for 333 format. ! 'U45' Memory constraint for 45 format. ! 'U37' Memory constraint for 37 format. ! _Nios II family--'config/nios2/constraints.md'_ ! 'I' Integer that is valid as an immediate operand in an ! instruction taking a signed 16-bit number. Range -32768 to 32767. ! 'J' Integer that is valid as an immediate operand in an ! instruction taking an unsigned 16-bit number. Range 0 to 65535. ! 'K' Integer that is valid as an immediate operand in an instruction taking only the upper 16-bits of a 32-bit number. Range 32-bit numbers with the lower 16-bits being 0. ! 'L' Integer that is valid as an immediate operand for a shift ! instruction. Range 0 to 31. ! 'M' Integer that is valid as an immediate operand for only the ! value 0. Can be used in conjunction with the format modifier ! 'z' to use 'r0' instead of '0' in the assembly output. ! 'N' Integer that is valid as an immediate operand for a custom ! instruction opcode. Range 0 to 255. ! 'P' An immediate operand for R2 andchi/andci instructions. ! 'S' Matches immediates which are addresses in the small data ! section and therefore can be added to 'gp' as a 16-bit immediate to re-create their 32-bit value. ! 'U' Matches constants suitable as an operand for the rdprs and cache instructions. ! 'v' A memory operand suitable for Nios II R2 load/store exclusive instructions. ! 'w' A memory operand suitable for load/store IO and cache instructions. - _PDP-11--'config/pdp11/constraints.md'_ - 'a' - Floating point registers AC0 through AC3. These can be loaded - from/to memory with a single instruction. ! 'd' Odd numbered general registers (R1, R3, R5). These are used for 16-bit multiply operations. ! 'f' Any of the floating point registers (AC0 through AC5). ! 'G' Floating point constant 0. ! 'I' An integer constant that fits in 16 bits. ! 'J' An integer constant whose low order 16 bits are zero. ! 'K' An integer constant that does not meet the constraints for ! codes 'I' or 'J'. ! 'L' The integer constant 1. ! 'M' The integer constant -1. ! 'N' The integer constant 0. ! 'O' Integer constants -4 through -1 and 1 through 4; shifts by ! these amounts are handled as multiple single-bit shifts rather ! than a single variable-length shift. ! 'Q' A memory reference which requires an additional word (address or offset) after the opcode. ! 'R' A memory reference that is encoded within the opcode. ! _PowerPC and IBM RS6000--'config/rs6000/constraints.md'_ ! 'b' Address base register ! 'd' Floating point register (containing 64-bit value) ! 'f' Floating point register (containing 32-bit value) ! 'v' Altivec vector register ! 'wa' Any VSX register if the -mvsx option was used or NO_REGS. ! When using any of the register constraints ('wa', 'wd', 'wf', ! 'wg', 'wh', 'wi', 'wj', 'wk', 'wl', 'wm', 'wo', 'wp', 'wq', ! 'ws', 'wt', 'wu', 'wv', 'ww', or 'wy') that take VSX ! registers, you must use '%x' in the template so that the correct register is used. Otherwise the register number output in the assembly file will be incorrect if an Altivec register is an operand of a VSX instruction that expects VSX --- 31921,33362 ---- ............................................ Whenever possible, you should use the general-purpose constraint letters ! in `asm' arguments, since they will convey meaning more readily to ! people reading your code. Failing that, use the constraint letters ! that usually have very similar meanings across architectures. The most ! commonly used constraints are `m' and `r' (for memory and general-purpose registers respectively; *note Simple Constraints::), and ! `I', usually the letter indicating the most common immediate-constant format. Each architecture defines additional constraints. These constraints are used by the compiler itself for instruction generation, as well as ! for `asm' statements; therefore, some of the constraints are not ! particularly useful for `asm'. Here is a summary of some of the machine-dependent constraints available on some particular machines; it ! includes both constraints that are useful for `asm' and constraints ! that aren't. The compiler source file mentioned in the table heading ! for each architecture is the definitive reference for the meanings of ! that architecture's constraints. ! _AArch64 family--`config/aarch64/constraints.md'_ ! `k' ! The stack pointer register (`SP') ! ! `w' Floating point or SIMD vector register ! `I' Integer constant that is valid as an immediate operand in an ! `ADD' instruction ! `J' Integer constant that is valid as an immediate operand in a ! `SUB' instruction (once negated) ! `K' Integer constant that can be used with a 32-bit logical instruction ! `L' Integer constant that can be used with a 64-bit logical instruction ! `M' Integer constant that is valid as an immediate operand in a ! 32-bit `MOV' pseudo instruction. The `MOV' may be assembled to one of several different machine instructions depending on the value ! `N' Integer constant that is valid as an immediate operand in a ! 64-bit `MOV' pseudo instruction ! `S' An absolute symbolic address or a label reference ! `Y' Floating point constant zero ! `Z' Integer constant zero ! `Ush' ! The high part (bits 12 and upwards) of the pc-relative ! address of a symbol within 4GB of the instruction ! `Q' A memory address which uses a single base register with no offset ! `Ump' ! A memory address suitable for a load/store pair instruction ! in SI, DI, SF and DF modes ! ! _ARC --`config/arc/constraints.md'_ ! ! `q' ! Registers usable in ARCompact 16-bit instructions: `r0'-`r3', ! `r12'-`r15'. This constraint can only match when the `-mq' option is in effect. ! `e' ! Registers usable as base-regs of memory addresses in ! ARCompact 16-bit memory instructions: `r0'-`r3', `r12'-`r15', ! `sp'. This constraint can only match when the `-mq' option ! is in effect. ! `D' ! ARC FPX (dpfp) 64-bit registers. `D0', `D1'. ! ! `I' A signed 12-bit integer constant. ! `Cal' ! constant for arithmetic/logical operations. This might be ! any constant that can be put into a long immediate by the ! assmbler or linker without involving a PIC relocation. ! `K' A 3-bit unsigned integer constant. ! `L' A 6-bit unsigned integer constant. ! `CnL' One's complement of a 6-bit unsigned integer constant. ! `CmL' Two's complement of a 6-bit unsigned integer constant. ! `M' A 5-bit unsigned integer constant. ! `O' A 7-bit unsigned integer constant. ! `P' A 8-bit unsigned integer constant. ! `H' Any const_double value. ! _ARM family--`config/arm/constraints.md'_ ! `h' ! In Thumb state, the core registers `r8'-`r15'. ! `k' The stack pointer register. ! `l' ! In Thumb State the core registers `r0'-`r7'. In ARM state ! this is an alias for the `r' constraint. ! `t' ! VFP floating-point registers `s0'-`s31'. Used for 32 bit values. ! `w' ! VFP floating-point registers `d0'-`d31' and the appropriate ! subset `d0'-`d15' based on command line options. Used for 64 bit values only. Not valid for Thumb1. ! `y' The iWMMX co-processor registers. ! `z' The iWMMX GR registers. ! `G' The floating-point constant 0.0 ! `I' Integer that is valid as an immediate operand in a data ! processing instruction. That is, an integer in the range 0 ! to 255 rotated by a multiple of 2 ! `J' Integer in the range -4095 to 4095 ! `K' ! Integer that satisfies constraint `I' when inverted (ones complement) ! `L' ! Integer that satisfies constraint `I' when negated (twos complement) ! `M' Integer in the range 0 to 32 ! `Q' A memory reference where the exact address is in a single ! register (``m'' is preferable for `asm' statements) ! `R' An item in the constant pool ! `S' A symbol in the text segment of the current file ! `Uv' A memory reference suitable for VFP load/store insns (reg+constant offset) ! `Uy' A memory reference suitable for iWMMXt load/store instructions. ! `Uq' A memory reference suitable for the ARMv4 ldrsb instruction. ! _AVR family--`config/avr/constraints.md'_ ! ! `l' Registers from r0 to r15 ! `a' Registers from r16 to r23 ! `d' Registers from r16 to r31 ! `w' Registers from r24 to r31. These registers can be used in ! `adiw' command ! `e' Pointer register (r26-r31) ! `b' Base pointer register (r28-r31) ! `q' Stack pointer register (SPH:SPL) ! `t' Temporary register r0 ! `x' Register pair X (r27:r26) ! `y' Register pair Y (r29:r28) ! `z' Register pair Z (r31:r30) ! `I' Constant greater than -1, less than 64 ! `J' Constant greater than -64, less than 1 ! `K' Constant integer 2 ! `L' Constant integer 0 ! `M' Constant that fits in 8 bits ! `N' Constant integer -1 ! `O' Constant integer 8, 16, or 24 ! `P' Constant integer 1 ! `G' A floating point constant 0.0 ! `Q' A memory address based on Y or Z pointer with displacement. ! _Blackfin family--`config/bfin/constraints.md'_ ! ! `a' P register ! `d' D register ! `z' A call clobbered P register. ! `qN' A single register. If N is in the range 0 to 7, the ! corresponding D register. If it is `A', then the register P0. ! `D' Even-numbered D register ! `W' Odd-numbered D register ! `e' Accumulator register. ! `A' Even-numbered accumulator register. ! `B' Odd-numbered accumulator register. ! `b' I register ! `v' B register ! `f' M register ! `c' ! Registers used for circular buffering, i.e. I, B, or L registers. ! `C' The CC register. ! `t' LT0 or LT1. ! `k' LC0 or LC1. ! `u' LB0 or LB1. ! `x' Any D, P, B, M, I or L register. ! `y' Additional registers typically used only in prologues and epilogues: RETS, RETN, RETI, RETX, RETE, ASTAT, SEQSTAT and USP. ! `w' Any register except accumulators or CC. ! `Ksh' Signed 16 bit integer (in the range -32768 to 32767) ! `Kuh' Unsigned 16 bit integer (in the range 0 to 65535) ! `Ks7' Signed 7 bit integer (in the range -64 to 63) ! `Ku7' Unsigned 7 bit integer (in the range 0 to 127) ! `Ku5' Unsigned 5 bit integer (in the range 0 to 31) ! `Ks4' Signed 4 bit integer (in the range -8 to 7) ! `Ks3' Signed 3 bit integer (in the range -3 to 4) ! `Ku3' Unsigned 3 bit integer (in the range 0 to 7) ! `PN' Constant N, where N is a single-digit constant in the range 0 to 4. ! `PA' An integer equal to one of the MACFLAG_XXX constants that is suitable for use with either accumulator. ! `PB' An integer equal to one of the MACFLAG_XXX constants that is suitable for use only with accumulator A1. ! `M1' Constant 255. ! `M2' Constant 65535. ! `J' An integer constant with exactly a single bit set. ! `L' An integer constant with all bits set except exactly one. ! `H' ! `Q' Any SYMBOL_REF. ! _CR16 Architecture--`config/cr16/cr16.h'_ ! `b' Registers from r0 to r14 (registers without stack pointer) ! `t' Register from r0 to r11 (all 16-bit registers) ! `p' Register from r12 to r15 (all 32-bit registers) ! `I' Signed constant that fits in 4 bits ! `J' Signed constant that fits in 5 bits ! `K' Signed constant that fits in 6 bits ! `L' Unsigned constant that fits in 4 bits ! `M' Signed constant that fits in 32 bits ! `N' Check for 64 bits wide constants for add/sub instructions ! `G' Floating point constant that is legal for store immediate ! _Epiphany--`config/epiphany/constraints.md'_ ! ! `U16' An unsigned 16-bit constant. ! `K' An unsigned 5-bit constant. ! `L' A signed 11-bit constant. ! `Cm1' ! A signed 11-bit constant added to -1. Can only match when ! the `-m1reg-REG' option is active. ! `Cl1' Left-shift of -1, i.e., a bit mask with a block of leading ones, the rest being a block of trailing zeroes. Can only ! match when the `-m1reg-REG' option is active. ! `Cr1' Right-shift of -1, i.e., a bit mask with a trailing block of ones, the rest being zeroes. Or to put it another way, one less than a power of two. Can only match when the ! `-m1reg-REG' option is active. ! `Cal' ! Constant for arithmetic/logical operations. This is like ! `i', except that for position independent code, no symbols / expressions needing relocations are allowed. ! `Csy' Symbolic constant for call/jump instruction. ! `Rcs' The register class usable in short insns. This is a register class constraint, and can thus drive register allocation. ! This constraint won't match unless `-mprefer-short-insn-regs' is in effect. ! `Rsc' The the register class of registers that can be used to hold a sibcall call address. I.e., a caller-saved register. ! `Rct' Core control register class. ! `Rgs' The register group usable in short insns. This constraint does not use a register class, so that it only passively matches suitable registers, and doesn't drive register allocation. ! `Rra' ! Matches the return address if it can be replaced with the ! link register. ! `Rcc' Matches the integer condition code register. ! `Sra' Matches the return address if it is in a stack slot. ! `Cfm' Matches control register values to switch fp mode, which are ! encapsulated in `UNSPEC_FP_MODE'. ! _FRV--`config/frv/frv.h'_ ! `a' ! Register in the class `ACC_REGS' (`acc0' to `acc7'). ! `b' ! Register in the class `EVEN_ACC_REGS' (`acc0' to `acc7'). ! `c' ! Register in the class `CC_REGS' (`fcc0' to `fcc3' and `icc0' ! to `icc3'). ! `d' ! Register in the class `GPR_REGS' (`gr0' to `gr63'). ! `e' ! Register in the class `EVEN_REGS' (`gr0' to `gr63'). Odd ! registers are excluded not in the class but through the use ! of a machine mode larger than 4 bytes. ! `f' ! Register in the class `FPR_REGS' (`fr0' to `fr63'). ! `h' ! Register in the class `FEVEN_REGS' (`fr0' to `fr63'). Odd ! registers are excluded not in the class but through the use ! of a machine mode larger than 4 bytes. ! `l' ! Register in the class `LR_REG' (the `lr' register). ! `q' ! Register in the class `QUAD_REGS' (`gr2' to `gr63'). ! Register numbers not divisible by 4 are excluded not in the ! class but through the use of a machine mode larger than 8 ! bytes. ! `t' ! Register in the class `ICC_REGS' (`icc0' to `icc3'). ! `u' ! Register in the class `FCC_REGS' (`fcc0' to `fcc3'). ! `v' ! Register in the class `ICR_REGS' (`cc4' to `cc7'). ! `w' ! Register in the class `FCR_REGS' (`cc0' to `cc3'). ! ! `x' ! Register in the class `QUAD_FPR_REGS' (`fr0' to `fr63'). Register numbers not divisible by 4 are excluded not in the class but through the use of a machine mode larger than 8 bytes. ! `z' ! Register in the class `SPR_REGS' (`lcr' and `lr'). ! `A' ! Register in the class `QUAD_ACC_REGS' (`acc0' to `acc7'). ! `B' ! Register in the class `ACCG_REGS' (`accg0' to `accg7'). ! `C' ! Register in the class `CR_REGS' (`cc0' to `cc7'). ! `G' Floating point constant zero ! `I' 6-bit signed integer constant ! `J' 10-bit signed integer constant ! `L' 16-bit signed integer constant ! `M' 16-bit unsigned integer constant ! `N' 12-bit signed integer constant that is negative--i.e. in the range of -2048 to -1 ! `O' Constant zero ! `P' ! 12-bit signed integer constant that is greater than ! zero--i.e. in the range of 1 to 2047. ! ! _FT32--`config/ft32/constraints.md'_ ! ! `A' An absolute address ! `B' An offset address ! `W' A register indirect memory operand ! `e' An offset address. ! `f' An offset address. ! `O' The constant zero or one ! `I' A 16-bit signed constant (-32768 ... 32767) ! `w' A bitfield mask suitable for bext or bins ! `x' An inverted bitfield mask suitable for bext or bins ! `L' A 16-bit unsigned constant, multiple of 4 (0 ... 65532) ! `S' A 20-bit signed constant (-524288 ... 524287) ! `b' A constant for a bitfield width (1 ... 16) ! `KA' A 10-bit signed constant (-512 ... 511) ! ! _Hewlett-Packard PA-RISC--`config/pa/pa.h'_ ! ! `a' General register 1 ! `f' Floating point register ! `q' Shift amount register ! `x' Floating point register (deprecated) ! `y' Upper floating point register (32-bit), floating point register (64-bit) ! `Z' Any register ! `I' Signed 11-bit integer constant ! `J' Signed 14-bit integer constant ! `K' ! Integer constant that can be deposited with a `zdepi' instruction ! `L' Signed 5-bit integer constant ! `M' Integer constant 0 ! `N' ! Integer constant that can be loaded with a `ldil' instruction ! `O' Integer constant whose value plus one is a power of 2 ! `P' ! Integer constant that can be used for `and' operations in ! `depi' and `extru' instructions ! `S' Integer constant 31 ! `U' Integer constant 63 ! `G' Floating-point constant 0.0 ! `A' ! A `lo_sum' data-linkage-table memory operand ! `Q' A memory operand that can be used as the destination operand of an integer store instruction ! `R' A scaled or unscaled indexed memory operand ! `T' A memory operand for floating-point loads and stores ! `W' A register indirect memory operand ! _Intel IA-64--`config/ia64/ia64.h'_ ! `a' ! General register `r0' to `r3' for `addl' instruction ! ! `b' Branch register ! `c' ! Predicate register (`c' as in "conditional") ! `d' Application register residing in M-unit ! `e' Application register residing in I-unit ! `f' Floating-point register ! `m' ! Memory operand. If used together with `<' or `>', the ! operand can have postincrement and postdecrement which ! require printing with `%Pn' on IA-64. ! `G' Floating-point constant 0.0 or 1.0 ! `I' 14-bit signed integer constant ! `J' 22-bit signed integer constant ! `K' 8-bit signed integer constant for logical instructions ! `L' 8-bit adjusted signed integer constant for compare pseudo-ops ! `M' 6-bit unsigned integer constant for shift counts ! `N' 9-bit signed integer constant for load and store postincrements ! `O' The constant zero ! `P' ! 0 or -1 for `dep' instruction ! `Q' Non-volatile memory for floating-point loads and stores ! `R' ! Integer constant in the range 1 to 4 for `shladd' instruction ! `S' Memory operand except postincrement and postdecrement. This ! is now roughly the same as `m' when not used together with `<' ! or `>'. ! _M32C--`config/m32c/m32c.c'_ ! `Rsp' ! `Rfb' ! `Rsb' ! `$sp', `$fb', `$sb'. ! ! `Rcr' Any control register, when they're 16 bits wide (nothing if control registers are 24 bits wide) ! `Rcl' Any control register, when they're 24 bits wide. ! `R0w' ! `R1w' ! `R2w' ! `R3w' $r0, $r1, $r2, $r3. ! `R02' $r0 or $r2, or $r2r0 for 32 bit values. ! `R13' $r1 or $r3, or $r3r1 for 32 bit values. ! `Rdi' A register that can hold a 64 bit value. ! `Rhl' $r0 or $r1 (registers with addressable high/low bytes) ! `R23' $r2 or $r3 ! `Raa' Address registers ! `Raw' Address registers when they're 16 bits wide. ! `Ral' Address registers when they're 24 bits wide. ! `Rqi' Registers that can hold QI values. ! `Rad' Registers that can be used with displacements ($a0, $a1, $sb). ! `Rsi' Registers that can hold 32 bit values. ! `Rhi' Registers that can hold 16 bit values. ! `Rhc' Registers chat can hold 16 bit values, including all control registers. ! `Rra' $r0 through R1, plus $a0 and $a1. ! `Rfl' The flags register. ! `Rmm' The memory-based pseudo-registers $mem0 through $mem15. ! `Rpi' Registers that can hold pointers (16 bit registers for r8c, m16c; 24 bit registers for m32cm, m32c). ! `Rpa' Matches multiple registers in a PARALLEL to form a larger register. Used to match function return values. ! `Is3' -8 ... 7 ! `IS1' -128 ... 127 ! `IS2' -32768 ... 32767 ! `IU2' 0 ... 65535 ! `In4' -8 ... -1 or 1 ... 8 ! `In5' -16 ... -1 or 1 ... 16 ! `In6' -32 ... -1 or 1 ... 32 ! `IM2' -65536 ... -1 ! `Ilb' An 8 bit value with exactly one bit set. ! `Ilw' A 16 bit value with exactly one bit set. ! `Sd' The common src/dest memory addressing modes. ! `Sa' Memory addressed using $a0 or $a1. ! `Si' Memory addressed with immediate addresses. ! `Ss' Memory addressed using the stack pointer ($sp). ! `Sf' Memory addressed using the frame base register ($fb). ! `Ss' Memory addressed using the small base register ($sb). ! `S1' $r1h ! _MeP--`config/mep/constraints.md'_ ! `a' The $sp register. ! `b' The $tp register. ! `c' Any control register. ! `d' Either the $hi or the $lo register. ! `em' Coprocessor registers that can be directly loaded ($c0-$c15). ! `ex' Coprocessor registers that can be moved to each other. ! `er' Coprocessor registers that can be moved to core registers. ! `h' The $hi register. ! `j' The $rpc register. ! `l' The $lo register. ! `t' Registers which can be used in $tp-relative addressing. ! `v' The $gp register. ! `x' The coprocessor registers. ! `y' The coprocessor control registers. ! `z' The $0 register. ! `A' User-defined register set A. ! `B' User-defined register set B. ! `C' User-defined register set C. ! `D' User-defined register set D. ! `I' Offsets for $gp-rel addressing. ! `J' Constants that can be used directly with boolean insns. ! `K' Constants that can be moved directly to registers. ! `L' Small constants that can be added to registers. ! `M' Long shift counts. ! `N' Small constants that can be compared to registers. ! `O' Constants that can be loaded into the top half of registers. ! `S' Signed 8-bit immediates. ! `T' Symbols encoded for $tp-rel or $gp-rel addressing. ! `U' Non-constant addresses for loading/saving coprocessor registers. ! `W' The top half of a symbol's value. ! `Y' A register indirect address without offset. ! `Z' Symbolic references to the control bus. ! _MicroBlaze--`config/microblaze/constraints.md'_ ! `d' ! A general register (`r0' to `r31'). ! ! `z' ! A status register (`rmsr', `$fcc1' to `$fcc7'). ! ! ! _MIPS--`config/mips/constraints.md'_ ! ! `d' ! An address register. This is equivalent to `r' unless generating MIPS16 code. ! `f' A floating-point register (if available). ! `h' ! Formerly the `hi' register. This constraint is no longer supported. ! `l' ! The `lo' register. Use this register to store values that are no bigger than a word. ! `x' ! The concatenated `hi' and `lo' registers. Use this register to store doubleword values. ! `c' A register suitable for use in an indirect jump. This will ! always be `$25' for `-mabicalls'. ! `v' ! Register `$3'. Do not use this constraint in new code; it is retained only for compatibility with glibc. ! `y' ! Equivalent to `r'; retained for backwards compatibility. ! `z' A floating-point condition code register. ! `I' A signed 16-bit constant (for arithmetic instructions). ! `J' Integer zero. ! `K' An unsigned 16-bit constant (for logic instructions). ! `L' A signed 32-bit constant in which the lower 16 bits are zero. ! Such constants can be loaded using `lui'. ! `M' ! A constant that cannot be loaded using `lui', `addiu' or ! `ori'. ! `N' A constant in the range -65535 to -1 (inclusive). ! `O' A signed 15-bit constant. ! `P' A constant in the range 1 to 65535 (inclusive). ! `G' Floating-point zero. ! `R' An address that can be used in a non-macro load or store. ! `ZC' A memory operand whose address is formed by a base register and offset that is suitable for use in instructions with the ! same addressing mode as `ll' and `sc'. ! `ZD' ! An address suitable for a `prefetch' instruction, or for any ! other instruction with the same addressing mode as `prefetch'. ! _Motorola 680x0--`config/m68k/constraints.md'_ ! ! `a' Address register ! `d' Data register ! `f' 68881 floating-point register, if available ! `I' Integer in the range 1 to 8 ! `J' 16-bit signed number ! `K' Signed number whose magnitude is greater than 0x80 ! `L' Integer in the range -8 to -1 ! `M' Signed number whose magnitude is greater than 0x100 ! `N' Range 24 to 31, rotatert:SI 8 to 1 expressed as rotate ! `O' 16 (for rotate using swap) ! `P' Range 8 to 15, rotatert:HI 8 to 1 expressed as rotate ! `R' Numbers that mov3q can handle ! `G' Floating point constant that is not a 68881 constant ! `S' Operands that satisfy 'm' when -mpcrel is in effect ! `T' Operands that satisfy 's' when -mpcrel is not in effect ! `Q' Address register indirect addressing mode ! `U' Register offset addressing ! `W' const_call_operand ! `Cs' symbol_ref or const ! `Ci' const_int ! `C0' const_int 0 ! `Cj' Range of signed numbers that don't fit in 16 bits ! `Cmvq' Integers valid for mvq ! `Capsw' Integers valid for a moveq followed by a swap ! `Cmvz' Integers valid for mvz ! `Cmvs' Integers valid for mvs ! `Ap' push_operand ! `Ac' Non-register operands allowed in clr ! ! _Moxie--`config/moxie/constraints.md'_ ! ! `A' An absolute address ! `B' An offset address ! `W' A register indirect memory operand ! `I' A constant in the range of 0 to 255. ! `N' A constant in the range of 0 to -255. ! _MSP430-`config/msp430/constraints.md'_ ! ! `R12' Register R12. ! `R13' Register R13. ! `K' Integer constant 1. ! `L' Integer constant -1^20..1^19. ! `M' Integer constant 1-4. ! `Ya' Memory references which do not require an extended MOVX instruction. ! `Yl' Memory reference, labels only. ! `Ys' Memory reference, stack only. ! ! _NDS32--`config/nds32/constraints.md'_ ! ! `w' LOW register class $r0 to $r7 constraint for V3/V3M ISA. ! ! `l' LOW register class $r0 to $r7. ! ! `d' MIDDLE register class $r0 to $r11, $r16 to $r19. ! ! `h' HIGH register class $r12 to $r14, $r20 to $r31. ! ! `t' Temporary assist register $ta (i.e. $r15). ! ! `k' Stack register $sp. ! ! `Iu03' Unsigned immediate 3-bit value. ! ! `In03' Negative immediate 3-bit value in the range of -7-0. ! ! `Iu04' Unsigned immediate 4-bit value. ! ! `Is05' Signed immediate 5-bit value. ! ! `Iu05' Unsigned immediate 5-bit value. ! ! `In05' Negative immediate 5-bit value in the range of -31-0. ! ! `Ip05' Unsigned immediate 5-bit value for movpi45 instruction with range 16-47. ! ! `Iu06' Unsigned immediate 6-bit value constraint for addri36.sp instruction. ! ! `Iu08' Unsigned immediate 8-bit value. ! ! `Iu09' Unsigned immediate 9-bit value. ! ! `Is10' Signed immediate 10-bit value. ! ! `Is11' Signed immediate 11-bit value. ! ! `Is15' Signed immediate 15-bit value. ! ! `Iu15' Unsigned immediate 15-bit value. ! ! `Ic15' ! A constant which is not in the range of imm15u but ok for ! bclr instruction. ! ! `Ie15' ! A constant which is not in the range of imm15u but ok for ! bset instruction. ! ! `It15' ! A constant which is not in the range of imm15u but ok for ! btgl instruction. ! ! `Ii15' A constant whose compliment value is in the range of imm15u and ok for bitci instruction. ! ! `Is16' Signed immediate 16-bit value. ! ! `Is17' Signed immediate 17-bit value. ! ! `Is19' Signed immediate 19-bit value. ! ! `Is20' Signed immediate 20-bit value. ! ! `Ihig' The immediate value that can be simply set high 20-bit. ! ! `Izeb' The immediate value 0xff. ! ! `Izeh' The immediate value 0xffff. ! ! `Ixls' The immediate value 0x01. ! ! `Ix11' The immediate value 0x7ff. ! ! `Ibms' The immediate value with power of 2. ! ! `Ifex' The immediate value with power of 2 minus 1. ! ! `U33' Memory constraint for 333 format. ! ! `U45' Memory constraint for 45 format. ! ! `U37' Memory constraint for 37 format. ! _Nios II family--`config/nios2/constraints.md'_ ! `I' Integer that is valid as an immediate operand in an ! instruction taking a signed 16-bit number. Range -32768 to 32767. ! `J' Integer that is valid as an immediate operand in an ! instruction taking an unsigned 16-bit number. Range 0 to 65535. ! `K' Integer that is valid as an immediate operand in an instruction taking only the upper 16-bits of a 32-bit number. Range 32-bit numbers with the lower 16-bits being 0. ! `L' Integer that is valid as an immediate operand for a shift ! instruction. Range 0 to 31. ! `M' Integer that is valid as an immediate operand for only the ! value 0. Can be used in conjunction with the format modifier ! `z' to use `r0' instead of `0' in the assembly output. ! `N' Integer that is valid as an immediate operand for a custom ! instruction opcode. Range 0 to 255. ! `P' An immediate operand for R2 andchi/andci instructions. ! `S' Matches immediates which are addresses in the small data ! section and therefore can be added to `gp' as a 16-bit immediate to re-create their 32-bit value. ! `U' Matches constants suitable as an operand for the rdprs and cache instructions. ! `v' A memory operand suitable for Nios II R2 load/store exclusive instructions. ! `w' A memory operand suitable for load/store IO and cache instructions. ! _PDP-11--`config/pdp11/constraints.md'_ ! ! `a' ! Floating point registers AC0 through AC3. These can be ! loaded from/to memory with a single instruction. ! ! `d' Odd numbered general registers (R1, R3, R5). These are used for 16-bit multiply operations. ! `f' Any of the floating point registers (AC0 through AC5). ! `G' Floating point constant 0. ! `I' An integer constant that fits in 16 bits. ! `J' An integer constant whose low order 16 bits are zero. ! `K' An integer constant that does not meet the constraints for ! codes `I' or `J'. ! `L' The integer constant 1. ! `M' The integer constant -1. ! `N' The integer constant 0. ! `O' Integer constants -4 through -1 and 1 through 4; shifts by ! these amounts are handled as multiple single-bit shifts ! rather than a single variable-length shift. ! `Q' A memory reference which requires an additional word (address or offset) after the opcode. ! `R' A memory reference that is encoded within the opcode. ! ! _PowerPC and IBM RS6000--`config/rs6000/constraints.md'_ ! ! `b' Address base register ! `d' Floating point register (containing 64-bit value) ! `f' Floating point register (containing 32-bit value) ! `v' Altivec vector register ! `wa' Any VSX register if the -mvsx option was used or NO_REGS. ! When using any of the register constraints (`wa', `wd', `wf', ! `wg', `wh', `wi', `wj', `wk', `wl', `wm', `wo', `wp', `wq', ! `ws', `wt', `wu', `wv', `ww', or `wy') that take VSX ! registers, you must use `%x' in the template so that the correct register is used. Otherwise the register number output in the assembly file will be incorrect if an Altivec register is an operand of a VSX instruction that expects VSX *************** _PowerPC and IBM RS6000--'config/rs6000/ *** 33059,33254 **** is not correct. If an instruction only takes Altivec registers, you do not ! want to use '%x'. asm ("xsaddqp %0,%1,%2" : "=v" (v1) : "v" (v2), "v" (v3)); ! is correct because the 'xsaddqp' instruction only takes Altivec registers, while: asm ("xsaddqp %x0,%x1,%x2" : "=v" (v1) : "v" (v2), "v" (v3)); is incorrect. ! 'wb' ! Altivec register if '-mpower9-dform' is used or NO_REGS. ! 'wd' VSX vector register to hold vector double data or NO_REGS. ! 'we' ! VSX register if the '-mpower9-vector' and '-m64' options were used or NO_REGS. ! 'wf' VSX vector register to hold vector float data or NO_REGS. ! 'wg' ! If '-mmfpgpr' was used, a floating point register or NO_REGS. ! 'wh' Floating point register if direct moves are available, or NO_REGS. ! 'wi' FP or VSX register to hold 64-bit integers for VSX insns or NO_REGS. ! 'wj' ! FP or VSX register to hold 64-bit integers for direct moves or ! NO_REGS. ! 'wk' FP or VSX register to hold 64-bit doubles for direct moves or NO_REGS. ! 'wl' Floating point register if the LFIWAX instruction is enabled or NO_REGS. ! 'wm' VSX register if direct move instructions are enabled, or NO_REGS. ! 'wn' No register (NO_REGS). ! 'wo' VSX register to use for ISA 3.0 vector instructions, or NO_REGS. ! 'wp' ! VSX register to use for IEEE 128-bit floating point TFmode, or ! NO_REGS. ! 'wq' VSX register to use for IEEE 128-bit floating point, or NO_REGS. ! 'wr' ! General purpose register if 64-bit instructions are enabled or ! NO_REGS. ! 'ws' VSX vector register to hold scalar double values or NO_REGS. ! 'wt' VSX vector register to hold 128 bit integer or NO_REGS. ! 'wu' ! Altivec register to use for float/32-bit int loads/stores or NO_REGS. ! 'wv' ! Altivec register to use for double loads/stores or NO_REGS. ! 'ww' ! FP or VSX register to perform float operations under '-mvsx' or NO_REGS. ! 'wx' Floating point register if the STFIWX instruction is enabled or NO_REGS. ! 'wy' FP or VSX register to perform ISA 2.07 float ops or NO_REGS. ! 'wz' Floating point register if the LFIWZX instruction is enabled or NO_REGS. ! 'wD' Int constant that is the element number of the 64-bit scalar in a vector. ! 'wE' Vector constant that can be loaded with the XXSPLTIB instruction. ! 'wF' Memory operand suitable for power9 fusion load/stores. ! 'wG' Memory operand suitable for TOC fusion memory references. ! 'wL' Int constant that is the element number that the MFVSRLD instruction. targets. ! 'wM' Match vector constant with all 1's if the XXLORC instruction is available. ! 'wO' A memory operand suitable for the ISA 3.0 vector d-form instructions. ! 'wQ' ! A memory address that will work with the 'lq' and 'stq' instructions. ! 'wS' Vector constant that can be loaded with XXSPLTIB & sign extension. ! 'h' ! 'MQ', 'CTR', or 'LINK' register ! 'c' ! 'CTR' register ! 'l' ! 'LINK' register ! 'x' ! 'CR' register (condition register) number 0 ! 'y' ! 'CR' register (condition register) ! 'z' ! 'XER[CA]' carry bit (part of the XER register) ! 'I' Signed 16-bit constant ! 'J' ! Unsigned 16-bit constant shifted left 16 bits (use 'L' instead ! for 'SImode' constants) ! 'K' Unsigned 16-bit constant ! 'L' Signed 16-bit constant shifted left 16 bits ! 'M' Constant larger than 31 ! 'N' Exact power of 2 ! 'O' Zero ! 'P' Constant whose negation is a signed 16-bit constant ! 'G' Floating point constant that can be loaded into a register with one instruction per word ! 'H' Integer/Floating point constant that can be loaded into a register using three instructions ! 'm' ! Memory operand. Normally, 'm' does not allow addresses that ! update the base register. If '<' or '>' constraint is also used, they are allowed and therefore on PowerPC targets in ! that case it is only safe to use 'm<>' in an 'asm' statement ! if that 'asm' statement accesses the operand exactly once. ! The 'asm' statement must also use '%U' as a placeholder for the "update" flag in the corresponding load or store instruction. For example: --- 33371,33570 ---- is not correct. If an instruction only takes Altivec registers, you do not ! want to use `%x'. asm ("xsaddqp %0,%1,%2" : "=v" (v1) : "v" (v2), "v" (v3)); ! is correct because the `xsaddqp' instruction only takes Altivec registers, while: asm ("xsaddqp %x0,%x1,%x2" : "=v" (v1) : "v" (v2), "v" (v3)); is incorrect. ! `wb' ! Altivec register if `-mcpu=power9' is used or NO_REGS. ! `wd' VSX vector register to hold vector double data or NO_REGS. ! `we' ! VSX register if the `-mcpu=power9' and `-m64' options were used or NO_REGS. ! `wf' VSX vector register to hold vector float data or NO_REGS. ! `wg' ! If `-mmfpgpr' was used, a floating point register or NO_REGS. ! `wh' Floating point register if direct moves are available, or NO_REGS. ! `wi' FP or VSX register to hold 64-bit integers for VSX insns or NO_REGS. ! `wj' ! FP or VSX register to hold 64-bit integers for direct moves ! or NO_REGS. ! `wk' FP or VSX register to hold 64-bit doubles for direct moves or NO_REGS. ! `wl' Floating point register if the LFIWAX instruction is enabled or NO_REGS. ! `wm' VSX register if direct move instructions are enabled, or NO_REGS. ! `wn' No register (NO_REGS). ! `wo' VSX register to use for ISA 3.0 vector instructions, or NO_REGS. ! `wp' ! VSX register to use for IEEE 128-bit floating point TFmode, ! or NO_REGS. ! `wq' VSX register to use for IEEE 128-bit floating point, or NO_REGS. ! `wr' ! General purpose register if 64-bit instructions are enabled ! or NO_REGS. ! `ws' VSX vector register to hold scalar double values or NO_REGS. ! `wt' VSX vector register to hold 128 bit integer or NO_REGS. ! `wu' ! Altivec register to use for float/32-bit int loads/stores or NO_REGS. ! `wv' ! Altivec register to use for double loads/stores or NO_REGS. ! `ww' ! FP or VSX register to perform float operations under `-mvsx' or NO_REGS. ! `wx' Floating point register if the STFIWX instruction is enabled or NO_REGS. ! `wy' FP or VSX register to perform ISA 2.07 float ops or NO_REGS. ! `wz' Floating point register if the LFIWZX instruction is enabled or NO_REGS. ! `wA' ! Address base register if 64-bit instructions are enabled or ! NO_REGS. ! ! `wD' Int constant that is the element number of the 64-bit scalar in a vector. ! `wE' Vector constant that can be loaded with the XXSPLTIB instruction. ! `wF' Memory operand suitable for power9 fusion load/stores. ! `wG' Memory operand suitable for TOC fusion memory references. ! `wL' Int constant that is the element number that the MFVSRLD instruction. targets. ! `wM' Match vector constant with all 1's if the XXLORC instruction is available. ! `wO' A memory operand suitable for the ISA 3.0 vector d-form instructions. ! `wQ' ! A memory address that will work with the `lq' and `stq' instructions. ! `wS' Vector constant that can be loaded with XXSPLTIB & sign extension. ! `h' ! `MQ', `CTR', or `LINK' register ! `c' ! `CTR' register ! `l' ! `LINK' register ! `x' ! `CR' register (condition register) number 0 ! `y' ! `CR' register (condition register) ! `z' ! `XER[CA]' carry bit (part of the XER register) ! `I' Signed 16-bit constant ! `J' ! Unsigned 16-bit constant shifted left 16 bits (use `L' ! instead for `SImode' constants) ! `K' Unsigned 16-bit constant ! `L' Signed 16-bit constant shifted left 16 bits ! `M' Constant larger than 31 ! `N' Exact power of 2 ! `O' Zero ! `P' Constant whose negation is a signed 16-bit constant ! `G' Floating point constant that can be loaded into a register with one instruction per word ! `H' Integer/Floating point constant that can be loaded into a register using three instructions ! `m' ! Memory operand. Normally, `m' does not allow addresses that ! update the base register. If `<' or `>' constraint is also used, they are allowed and therefore on PowerPC targets in ! that case it is only safe to use `m<>' in an `asm' statement ! if that `asm' statement accesses the operand exactly once. ! The `asm' statement must also use `%U' as a placeholder for the "update" flag in the corresponding load or store instruction. For example: *************** _PowerPC and IBM RS6000--'config/rs6000/ *** 33260,33948 **** is not. ! 'es' ! A "stable" memory operand; that is, one which does not include ! any automodification of the base register. This used to be ! useful when 'm' allowed automodification of the base register, ! but as those are now only allowed when '<' or '>' is used, ! 'es' is basically the same as 'm' without '<' and '>'. ! 'Q' Memory operand that is an offset from a register (it is ! usually better to use 'm' or 'es' in 'asm' statements) ! 'Z' Memory operand that is an indexed or indirect from a register ! (it is usually better to use 'm' or 'es' in 'asm' statements) ! 'R' AIX TOC entry ! 'a' ! Address operand that is an indexed or indirect from a register ! ('p' is preferable for 'asm' statements) ! 'U' System V Release 4 small data area reference ! 'W' Vector constant that does not require memory ! 'j' Vector constant that is all zeros. - _RL78--'config/rl78/constraints.md'_ ! 'Int3' An integer constant in the range 1 ... 7. ! 'Int8' An integer constant in the range 0 ... 255. ! 'J' An integer constant in the range -255 ... 0 ! 'K' The integer constant 1. ! 'L' The integer constant -1. ! 'M' The integer constant 0. ! 'N' The integer constant 2. ! 'O' The integer constant -2. ! 'P' An integer constant in the range 1 ... 15. ! 'Qbi' The built-in compare types-eq, ne, gtu, ltu, geu, and leu. ! 'Qsc' The synthetic compare types-gt, lt, ge, and le. ! 'Wab' A memory reference with an absolute address. ! 'Wbc' ! A memory reference using 'BC' as a base register, with an optional offset. ! 'Wca' ! A memory reference using 'AX', 'BC', 'DE', or 'HL' for the address, for calls. ! 'Wcv' A memory reference using any 16-bit register pair for the address, for calls. ! 'Wd2' ! A memory reference using 'DE' as a base register, with an optional offset. ! 'Wde' ! A memory reference using 'DE' as a base register, without any offset. ! 'Wfr' Any memory reference to an address in the far address space. ! 'Wh1' ! A memory reference using 'HL' as a base register, with an optional one-byte offset. ! 'Whb' ! A memory reference using 'HL' as a base register, with 'B' or ! 'C' as the index register. ! 'Whl' ! A memory reference using 'HL' as a base register, without any offset. ! 'Ws1' ! A memory reference using 'SP' as a base register, with an optional one-byte offset. ! 'Y' Any memory reference to an address in the near address space. ! 'A' ! The 'AX' register. ! 'B' ! The 'BC' register. ! 'D' ! The 'DE' register. ! 'R' ! 'A' through 'L' registers. ! 'S' ! The 'SP' register. ! 'T' ! The 'HL' register. ! 'Z08W' ! The 16-bit 'R8' register. ! 'Z10W' ! The 16-bit 'R10' register. ! 'Zint' ! The registers reserved for interrupts ('R24' to 'R31'). ! 'a' ! The 'A' register. ! 'b' ! The 'B' register. ! 'c' ! The 'C' register. ! 'd' ! The 'D' register. ! 'e' ! The 'E' register. ! 'h' ! The 'H' register. ! 'l' ! The 'L' register. ! 'v' The virtual registers. - 'w' - The 'PSW' register. - 'x' - The 'X' register. ! _RX--'config/rx/constraints.md'_ ! 'Q' ! An address which does not involve register indirect addressing ! or pre/post increment/decrement addressing. ! 'Symbol' A symbol reference. ! 'Int08' A constant in the range -256 to 255, inclusive. ! 'Sint08' A constant in the range -128 to 127, inclusive. ! 'Sint16' A constant in the range -32768 to 32767, inclusive. ! 'Sint24' A constant in the range -8388608 to 8388607, inclusive. ! 'Uint04' A constant in the range 0 to 15, inclusive. ! _S/390 and zSeries--'config/s390/s390.h'_ ! 'a' Address register (general purpose register except r0) ! 'c' Condition code register ! 'd' Data register (arbitrary general purpose register) ! 'f' Floating-point register ! 'I' Unsigned 8-bit constant (0-255) ! 'J' Unsigned 12-bit constant (0-4095) ! 'K' Signed 16-bit constant (-32768-32767) ! 'L' Value appropriate as displacement. ! '(0..4095)' for short displacement ! '(-524288..524287)' for long displacement ! 'M' Constant integer with a value of 0x7fffffff. ! 'N' Multiple letter constraint followed by 4 parameter letters. ! '0..9:' number of the part counting from most to least significant ! 'H,Q:' mode of the part ! 'D,S,H:' mode of the containing operand ! '0,F:' value of the other parts (F--all bits set) ! The constraint matches if the specified part of a constant has ! a value different from its other parts. ! 'Q' Memory reference without index register and with short displacement. ! 'R' Memory reference with index register and short displacement. ! 'S' Memory reference without index register but with long displacement. ! 'T' Memory reference with index register and long displacement. ! 'U' Pointer with short displacement. ! 'W' Pointer with long displacement. ! 'Y' Shift count operand. - _SPARC--'config/sparc/sparc.h'_ - 'f' - Floating-point register on the SPARC-V8 architecture and lower - floating-point register on the SPARC-V9 architecture. ! 'e' ! Floating-point register. It is equivalent to 'f' on the SPARC-V8 architecture and contains both lower and upper floating-point registers on the SPARC-V9 architecture. ! 'c' Floating-point condition code register. ! 'd' Lower floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! 'b' Floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! 'h' 64-bit global or out register for the SPARC-V8+ architecture. ! 'C' The constant all-ones, for floating-point. ! 'A' Signed 5-bit constant ! 'D' A vector constant ! 'I' Signed 13-bit constant ! 'J' Zero ! 'K' 32-bit constant with the low 12 bits clear (a constant that ! can be loaded with the 'sethi' instruction) ! 'L' ! A constant in the range supported by 'movcc' instructions (11-bit signed immediate) ! 'M' ! A constant in the range supported by 'movrcc' instructions (10-bit signed immediate) ! 'N' ! Same as 'K', except that it verifies that bits that are not in ! the lower 32-bit range are all zero. Must be used instead of ! 'K' for modes wider than 'SImode' ! 'O' The constant 4096 ! 'G' Floating-point zero ! 'H' Signed 13-bit constant, sign-extended to 32 or 64 bits ! 'P' The constant -1 ! 'Q' Floating-point constant whose integral representation can be moved into an integer register using a single sethi instruction ! 'R' Floating-point constant whose integral representation can be moved into an integer register using a single mov instruction ! 'S' Floating-point constant whose integral representation can be ! moved into an integer register using a high/lo_sum instruction ! sequence ! 'T' Memory address aligned to an 8-byte boundary ! 'U' Even register ! 'W' ! Memory address for 'e' constraint registers ! 'w' Memory address with only a base register ! 'Y' Vector zero ! _SPU--'config/spu/spu.h'_ ! 'a' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 64 bit value. ! 'c' An immediate for and/xor/or instructions. const_int is treated as a 64 bit value. ! 'd' ! An immediate for the 'iohl' instruction. const_int is treated ! as a 64 bit value. ! 'f' ! An immediate which can be loaded with 'fsmbi'. ! 'A' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 32 bit value. ! 'B' An immediate for most arithmetic instructions. const_int is treated as a 32 bit value. ! 'C' An immediate for and/xor/or instructions. const_int is treated as a 32 bit value. ! 'D' ! An immediate for the 'iohl' instruction. const_int is treated ! as a 32 bit value. ! 'I' A constant in the range [-64, 63] for shift/rotate instructions. ! 'J' An unsigned 7-bit constant for conversion/nop/channel instructions. ! 'K' A signed 10-bit constant for most arithmetic instructions. ! 'M' ! A signed 16 bit immediate for 'stop'. ! 'N' ! An unsigned 16-bit constant for 'iohl' and 'fsmbi'. ! 'O' An unsigned 7-bit constant whose 3 least significant bits are 0. ! 'P' An unsigned 3-bit constant for 16-byte rotates and shifts ! 'R' Call operand, reg, for indirect calls ! 'S' Call operand, symbol, for relative calls. ! 'T' Call operand, const_int, for absolute calls. ! 'U' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is sign extended to 128 bit. ! 'W' An immediate for shift and rotate instructions. const_int is treated as a 32 bit value. ! 'Y' An immediate for and/xor/or instructions. const_int is sign extended as a 128 bit. ! 'Z' ! An immediate for the 'iohl' instruction. const_int is sign extended to 128 bit. ! _TI C6X family--'config/c6x/constraints.md'_ ! 'a' Register file A (A0-A31). ! 'b' Register file B (B0-B31). ! 'A' Predicate registers in register file A (A0-A2 on C64X and higher, A1 and A2 otherwise). ! 'B' Predicate registers in register file B (B0-B2). ! 'C' A call-used register in register file B (B0-B9, B16-B31). ! 'Da' Register file A, excluding predicate registers (A3-A31, plus A0 if not C64X or higher). ! 'Db' Register file B, excluding predicate registers (B3-B31). ! 'Iu4' Integer constant in the range 0 ... 15. ! 'Iu5' Integer constant in the range 0 ... 31. ! 'In5' Integer constant in the range -31 ... 0. ! 'Is5' Integer constant in the range -16 ... 15. ! 'I5x' Integer constant that can be the operand of an ADDA or a SUBA insn. ! 'IuB' Integer constant in the range 0 ... 65535. ! 'IsB' Integer constant in the range -32768 ... 32767. ! 'IsC' ! Integer constant in the range -2^{20} ... 2^{20} - 1. ! 'Jc' Integer constant that is a valid mask for the clr instruction. ! 'Js' Integer constant that is a valid mask for the set instruction. ! 'Q' Memory location with A base register. ! 'R' Memory location with B base register. ! 'Z' Register B14 (aka DP). ! _TILE-Gx--'config/tilegx/constraints.md'_ ! 'R00' ! 'R01' ! 'R02' ! 'R03' ! 'R04' ! 'R05' ! 'R06' ! 'R07' ! 'R08' ! 'R09' ! 'R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! 'I' Signed 8-bit integer constant. ! 'J' Signed 16-bit integer constant. ! 'K' Unsigned 16-bit integer constant. ! 'L' ! Integer constant that fits in one signed byte when incremented ! by one (-129 ... 126). ! 'm' ! Memory operand. If used together with '<' or '>', the operand ! can have postincrement which requires printing with '%In' and ! '%in' on TILE-Gx. For example: asm ("st_add %I0,%1,%i0" : "=m<>" (*mem) : "r" (val)); ! 'M' A bit mask suitable for the BFINS instruction. ! 'N' Integer constant that is a byte tiled out eight times. ! 'O' The integer zero constant. ! 'P' Integer constant that is a sign-extended byte tiled out as four shorts. ! 'Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! 'S' Integer constant that has all 1 bits consecutive and starting at bit 0. ! 'T' A 16-bit fragment of a got, tls, or pc-relative reference. ! 'U' ! Memory operand except postincrement. This is roughly the same ! as 'm' when not used together with '<' or '>'. ! 'W' An 8-element vector constant with identical elements. ! 'Y' A 4-element vector constant with identical elements. ! 'Z0' The integer constant 0xffffffff. ! 'Z1' The integer constant 0xffffffff00000000. ! _TILEPro--'config/tilepro/constraints.md'_ ! 'R00' ! 'R01' ! 'R02' ! 'R03' ! 'R04' ! 'R05' ! 'R06' ! 'R07' ! 'R08' ! 'R09' ! 'R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! 'I' Signed 8-bit integer constant. ! 'J' Signed 16-bit integer constant. ! 'K' Nonzero integer constant with low 16 bits zero. ! 'L' ! Integer constant that fits in one signed byte when incremented ! by one (-129 ... 126). ! 'm' ! Memory operand. If used together with '<' or '>', the operand ! can have postincrement which requires printing with '%In' and ! '%in' on TILEPro. For example: asm ("swadd %I0,%1,%i0" : "=m<>" (mem) : "r" (val)); ! 'M' A bit mask suitable for the MM instruction. ! 'N' Integer constant that is a byte tiled out four times. ! 'O' The integer zero constant. ! 'P' ! Integer constant that is a sign-extended byte tiled out as two ! shorts. ! 'Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! 'T' A symbolic operand, or a 16-bit fragment of a got, tls, or pc-relative reference. ! 'U' ! Memory operand except postincrement. This is roughly the same ! as 'm' when not used together with '<' or '>'. ! 'W' A 4-element vector constant with identical elements. ! 'Y' A 2-element vector constant with identical elements. - _Visium--'config/visium/constraints.md'_ - 'b' - EAM register 'mdb' ! 'c' ! EAM register 'mdc' ! 'f' Floating point register ! 'l' ! General register, but not 'r29', 'r30' and 'r31' ! 't' ! Register 'r1' ! 'u' ! Register 'r2' ! 'v' ! Register 'r3' ! 'G' Floating-point constant 0.0 ! 'J' ! Integer constant in the range 0 .. 65535 (16-bit immediate) ! 'K' ! Integer constant in the range 1 .. 31 (5-bit immediate) ! 'L' ! Integer constant in the range -65535 .. -1 (16-bit negative immediate) ! 'M' Integer constant -1 ! 'O' Integer constant 0 ! 'P' Integer constant 32 ! _x86 family--'config/i386/constraints.md'_ ! 'R' Legacy register--the eight integer registers available on all ! i386 processors ('a', 'b', 'c', 'd', 'si', 'di', 'bp', 'sp'). ! 'q' ! Any register accessible as 'Rl'. In 32-bit mode, 'a', 'b', ! 'c', and 'd'; in 64-bit mode, any integer register. ! 'Q' ! Any register accessible as 'Rh': 'a', 'b', 'c', and 'd'. ! 'a' ! The 'a' register. ! 'b' ! The 'b' register. ! 'c' ! The 'c' register. ! 'd' ! The 'd' register. ! 'S' ! The 'si' register. ! 'D' ! The 'di' register. ! 'A' ! The 'a' and 'd' registers. This class is used for ! instructions that return double word results in the 'ax:dx' ! register pair. Single word values will be allocated either in ! 'ax' or 'dx'. For example on i386 the following implements ! 'rdtsc': unsigned long long rdtsc (void) { --- 33576,34328 ---- is not. ! `es' ! A "stable" memory operand; that is, one which does not ! include any automodification of the base register. This used ! to be useful when `m' allowed automodification of the base ! register, but as those are now only allowed when `<' or `>' ! is used, `es' is basically the same as `m' without `<' and ! `>'. ! `Q' Memory operand that is an offset from a register (it is ! usually better to use `m' or `es' in `asm' statements) ! `Z' Memory operand that is an indexed or indirect from a register ! (it is usually better to use `m' or `es' in `asm' statements) ! `R' AIX TOC entry ! `a' ! Address operand that is an indexed or indirect from a ! register (`p' is preferable for `asm' statements) ! `U' System V Release 4 small data area reference ! `W' Vector constant that does not require memory ! `j' Vector constant that is all zeros. ! _RL78--`config/rl78/constraints.md'_ ! ! `Int3' An integer constant in the range 1 ... 7. ! ! `Int8' An integer constant in the range 0 ... 255. ! ! `J' An integer constant in the range -255 ... 0 ! ! `K' The integer constant 1. ! ! `L' The integer constant -1. ! ! `M' The integer constant 0. ! ! `N' The integer constant 2. ! ! `O' The integer constant -2. ! ! `P' An integer constant in the range 1 ... 15. ! ! `Qbi' The built-in compare types-eq, ne, gtu, ltu, geu, and leu. ! ! `Qsc' The synthetic compare types-gt, lt, ge, and le. ! ! `Wab' A memory reference with an absolute address. ! ! `Wbc' ! A memory reference using `BC' as a base register, with an optional offset. ! ! `Wca' ! A memory reference using `AX', `BC', `DE', or `HL' for the address, for calls. ! ! `Wcv' A memory reference using any 16-bit register pair for the address, for calls. ! ! `Wd2' ! A memory reference using `DE' as a base register, with an optional offset. ! ! `Wde' ! A memory reference using `DE' as a base register, without any offset. ! ! `Wfr' Any memory reference to an address in the far address space. ! ! `Wh1' ! A memory reference using `HL' as a base register, with an optional one-byte offset. ! ! `Whb' ! A memory reference using `HL' as a base register, with `B' or ! `C' as the index register. ! ! `Whl' ! A memory reference using `HL' as a base register, without any offset. ! ! `Ws1' ! A memory reference using `SP' as a base register, with an optional one-byte offset. ! ! `Y' Any memory reference to an address in the near address space. ! ! `A' ! The `AX' register. ! ! `B' ! The `BC' register. ! ! `D' ! The `DE' register. ! ! `R' ! `A' through `L' registers. ! ! `S' ! The `SP' register. ! ! `T' ! The `HL' register. ! ! `Z08W' ! The 16-bit `R8' register. ! ! `Z10W' ! The 16-bit `R10' register. ! ! `Zint' ! The registers reserved for interrupts (`R24' to `R31'). ! ! `a' ! The `A' register. ! ! `b' ! The `B' register. ! ! `c' ! The `C' register. ! ! `d' ! The `D' register. ! ! `e' ! The `E' register. ! ! `h' ! The `H' register. ! ! `l' ! The `L' register. ! ! `v' The virtual registers. ! `w' ! The `PSW' register. ! `x' ! The `X' register. ! ! ! _RX--`config/rx/constraints.md'_ ! ! `Q' ! An address which does not involve register indirect ! addressing or pre/post increment/decrement addressing. ! ! `Symbol' A symbol reference. ! `Int08' A constant in the range -256 to 255, inclusive. ! `Sint08' A constant in the range -128 to 127, inclusive. ! `Sint16' A constant in the range -32768 to 32767, inclusive. ! `Sint24' A constant in the range -8388608 to 8388607, inclusive. ! `Uint04' A constant in the range 0 to 15, inclusive. ! ! _S/390 and zSeries--`config/s390/s390.h'_ ! ! `a' Address register (general purpose register except r0) ! `c' Condition code register ! `d' Data register (arbitrary general purpose register) ! `f' Floating-point register ! `I' Unsigned 8-bit constant (0-255) ! `J' Unsigned 12-bit constant (0-4095) ! `K' Signed 16-bit constant (-32768-32767) ! `L' Value appropriate as displacement. ! `(0..4095)' for short displacement ! ! `(-524288..524287)' for long displacement ! `M' Constant integer with a value of 0x7fffffff. ! `N' Multiple letter constraint followed by 4 parameter letters. ! `0..9:' number of the part counting from most to least significant ! ! `H,Q:' mode of the part ! ! `D,S,H:' mode of the containing operand ! ! `0,F:' value of the other parts (F--all bits set) ! The constraint matches if the specified part of a constant ! has a value different from its other parts. ! `Q' Memory reference without index register and with short displacement. ! `R' Memory reference with index register and short displacement. ! `S' Memory reference without index register but with long displacement. ! `T' Memory reference with index register and long displacement. ! `U' Pointer with short displacement. ! `W' Pointer with long displacement. ! `Y' Shift count operand. ! _SPARC--`config/sparc/sparc.h'_ ! ! `f' ! Floating-point register on the SPARC-V8 architecture and ! lower floating-point register on the SPARC-V9 architecture. ! ! `e' ! Floating-point register. It is equivalent to `f' on the SPARC-V8 architecture and contains both lower and upper floating-point registers on the SPARC-V9 architecture. ! `c' Floating-point condition code register. ! `d' Lower floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! `b' Floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! `h' 64-bit global or out register for the SPARC-V8+ architecture. ! `C' The constant all-ones, for floating-point. ! `A' Signed 5-bit constant ! `D' A vector constant ! `I' Signed 13-bit constant ! `J' Zero ! `K' 32-bit constant with the low 12 bits clear (a constant that ! can be loaded with the `sethi' instruction) ! `L' ! A constant in the range supported by `movcc' instructions (11-bit signed immediate) ! `M' ! A constant in the range supported by `movrcc' instructions (10-bit signed immediate) ! `N' ! Same as `K', except that it verifies that bits that are not ! in the lower 32-bit range are all zero. Must be used instead ! of `K' for modes wider than `SImode' ! `O' The constant 4096 ! `G' Floating-point zero ! `H' Signed 13-bit constant, sign-extended to 32 or 64 bits ! `P' The constant -1 ! `Q' Floating-point constant whose integral representation can be moved into an integer register using a single sethi instruction ! `R' Floating-point constant whose integral representation can be moved into an integer register using a single mov instruction ! `S' Floating-point constant whose integral representation can be ! moved into an integer register using a high/lo_sum ! instruction sequence ! `T' Memory address aligned to an 8-byte boundary ! `U' Even register ! `W' ! Memory address for `e' constraint registers ! `w' Memory address with only a base register ! `Y' Vector zero ! ! _SPU--`config/spu/spu.h'_ ! ! `a' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 64 bit value. ! `c' An immediate for and/xor/or instructions. const_int is treated as a 64 bit value. ! `d' ! An immediate for the `iohl' instruction. const_int is ! treated as a 64 bit value. ! `f' ! An immediate which can be loaded with `fsmbi'. ! `A' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 32 bit value. ! `B' An immediate for most arithmetic instructions. const_int is treated as a 32 bit value. ! `C' An immediate for and/xor/or instructions. const_int is treated as a 32 bit value. ! `D' ! An immediate for the `iohl' instruction. const_int is ! treated as a 32 bit value. ! `I' A constant in the range [-64, 63] for shift/rotate instructions. ! `J' An unsigned 7-bit constant for conversion/nop/channel instructions. ! `K' A signed 10-bit constant for most arithmetic instructions. ! `M' ! A signed 16 bit immediate for `stop'. ! `N' ! An unsigned 16-bit constant for `iohl' and `fsmbi'. ! `O' An unsigned 7-bit constant whose 3 least significant bits are 0. ! `P' An unsigned 3-bit constant for 16-byte rotates and shifts ! `R' Call operand, reg, for indirect calls ! `S' Call operand, symbol, for relative calls. ! `T' Call operand, const_int, for absolute calls. ! `U' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is sign extended to 128 bit. ! `W' An immediate for shift and rotate instructions. const_int is treated as a 32 bit value. ! `Y' An immediate for and/xor/or instructions. const_int is sign extended as a 128 bit. ! `Z' ! An immediate for the `iohl' instruction. const_int is sign extended to 128 bit. ! ! _TI C6X family--`config/c6x/constraints.md'_ ! ! `a' Register file A (A0-A31). ! `b' Register file B (B0-B31). ! `A' Predicate registers in register file A (A0-A2 on C64X and higher, A1 and A2 otherwise). ! `B' Predicate registers in register file B (B0-B2). ! `C' A call-used register in register file B (B0-B9, B16-B31). ! `Da' Register file A, excluding predicate registers (A3-A31, plus A0 if not C64X or higher). ! `Db' Register file B, excluding predicate registers (B3-B31). ! `Iu4' Integer constant in the range 0 ... 15. ! `Iu5' Integer constant in the range 0 ... 31. ! `In5' Integer constant in the range -31 ... 0. ! `Is5' Integer constant in the range -16 ... 15. ! `I5x' Integer constant that can be the operand of an ADDA or a SUBA insn. ! `IuB' Integer constant in the range 0 ... 65535. ! `IsB' Integer constant in the range -32768 ... 32767. ! `IsC' ! Integer constant in the range -2^20 ... 2^20 - 1. ! `Jc' Integer constant that is a valid mask for the clr instruction. ! `Js' Integer constant that is a valid mask for the set instruction. ! `Q' Memory location with A base register. ! `R' Memory location with B base register. ! `Z' Register B14 (aka DP). ! ! _TILE-Gx--`config/tilegx/constraints.md'_ ! ! `R00' ! `R01' ! `R02' ! `R03' ! `R04' ! `R05' ! `R06' ! `R07' ! `R08' ! `R09' ! `R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! `I' Signed 8-bit integer constant. ! `J' Signed 16-bit integer constant. ! `K' Unsigned 16-bit integer constant. ! `L' ! Integer constant that fits in one signed byte when ! incremented by one (-129 ... 126). ! `m' ! Memory operand. If used together with `<' or `>', the ! operand can have postincrement which requires printing with ! `%In' and `%in' on TILE-Gx. For example: asm ("st_add %I0,%1,%i0" : "=m<>" (*mem) : "r" (val)); ! `M' A bit mask suitable for the BFINS instruction. ! `N' Integer constant that is a byte tiled out eight times. ! `O' The integer zero constant. ! `P' Integer constant that is a sign-extended byte tiled out as four shorts. ! `Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! `S' Integer constant that has all 1 bits consecutive and starting at bit 0. ! `T' A 16-bit fragment of a got, tls, or pc-relative reference. ! `U' ! Memory operand except postincrement. This is roughly the ! same as `m' when not used together with `<' or `>'. ! `W' An 8-element vector constant with identical elements. ! `Y' A 4-element vector constant with identical elements. ! `Z0' The integer constant 0xffffffff. ! `Z1' The integer constant 0xffffffff00000000. ! ! _TILEPro--`config/tilepro/constraints.md'_ ! ! `R00' ! `R01' ! `R02' ! `R03' ! `R04' ! `R05' ! `R06' ! `R07' ! `R08' ! `R09' ! `R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! `I' Signed 8-bit integer constant. ! `J' Signed 16-bit integer constant. ! `K' Nonzero integer constant with low 16 bits zero. ! `L' ! Integer constant that fits in one signed byte when ! incremented by one (-129 ... 126). ! `m' ! Memory operand. If used together with `<' or `>', the ! operand can have postincrement which requires printing with ! `%In' and `%in' on TILEPro. For example: asm ("swadd %I0,%1,%i0" : "=m<>" (mem) : "r" (val)); ! `M' A bit mask suitable for the MM instruction. ! `N' Integer constant that is a byte tiled out four times. ! `O' The integer zero constant. ! `P' ! Integer constant that is a sign-extended byte tiled out as ! two shorts. ! `Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! `T' A symbolic operand, or a 16-bit fragment of a got, tls, or pc-relative reference. ! `U' ! Memory operand except postincrement. This is roughly the ! same as `m' when not used together with `<' or `>'. ! `W' A 4-element vector constant with identical elements. ! `Y' A 2-element vector constant with identical elements. ! _Visium--`config/visium/constraints.md'_ ! `b' ! EAM register `mdb' ! ! `c' ! EAM register `mdc' ! ! `f' Floating point register ! `l' ! General register, but not `r29', `r30' and `r31' ! `t' ! Register `r1' ! `u' ! Register `r2' ! `v' ! Register `r3' ! `G' Floating-point constant 0.0 ! `J' ! Integer constant in the range 0 .. 65535 (16-bit immediate) ! `K' ! Integer constant in the range 1 .. 31 (5-bit immediate) ! `L' ! Integer constant in the range -65535 .. -1 (16-bit negative immediate) ! `M' Integer constant -1 ! `O' Integer constant 0 ! `P' Integer constant 32 ! _x86 family--`config/i386/constraints.md'_ ! ! `R' Legacy register--the eight integer registers available on all ! i386 processors (`a', `b', `c', `d', `si', `di', `bp', `sp'). ! `q' ! Any register accessible as `Rl'. In 32-bit mode, `a', `b', ! `c', and `d'; in 64-bit mode, any integer register. ! `Q' ! Any register accessible as `Rh': `a', `b', `c', and `d'. ! `a' ! The `a' register. ! `b' ! The `b' register. ! `c' ! The `c' register. ! `d' ! The `d' register. ! `S' ! The `si' register. ! `D' ! The `di' register. ! `A' ! The `a' and `d' registers. This class is used for ! instructions that return double word results in the `ax:dx' ! register pair. Single word values will be allocated either ! in `ax' or `dx'. For example on i386 the following ! implements `rdtsc': unsigned long long rdtsc (void) { *************** _x86 family--'config/i386/constraints.md *** 33952,33958 **** } This is not correct on x86-64 as it would allocate tick in ! either 'ax' or 'dx'. You have to use the following variant instead: unsigned long long rdtsc (void) --- 34332,34338 ---- } This is not correct on x86-64 as it would allocate tick in ! either `ax' or `dx'. You have to use the following variant instead: unsigned long long rdtsc (void) *************** _x86 family--'config/i386/constraints.md *** 33962,34110 **** return ((unsigned long long)tickh << 32)|tickl; } ! 'f' Any 80387 floating-point (stack) register. ! 't' ! Top of 80387 floating-point stack ('%st(0)'). ! 'u' ! Second from top of 80387 floating-point stack ('%st(1)'). ! 'y' Any MMX register. ! 'x' Any SSE register. ! 'Yz' ! First SSE register ('%xmm0'). ! 'I' Integer constant in the range 0 ... 31, for 32-bit shifts. ! 'J' Integer constant in the range 0 ... 63, for 64-bit shifts. ! 'K' Signed 8-bit integer constant. ! 'L' ! '0xFF' or '0xFFFF', for andsi as a zero-extending move. ! 'M' ! 0, 1, 2, or 3 (shifts for the 'lea' instruction). ! 'N' ! Unsigned 8-bit integer constant (for 'in' and 'out' instructions). ! 'G' Standard 80387 floating point constant. ! 'C' SSE constant zero operand. ! 'e' 32-bit signed integer constant, or a symbolic reference known to fit that range (for immediate operands in sign-extending x86-64 instructions). ! 'Z' 32-bit unsigned integer constant, or a symbolic reference known to fit that range (for immediate operands in zero-extending x86-64 instructions). ! _Xstormy16--'config/stormy16/stormy16.h'_ ! 'a' Register r0. ! 'b' Register r1. ! 'c' Register r2. ! 'd' Register r8. ! 'e' Registers r0 through r7. ! 't' Registers r0 and r1. ! 'y' The carry register. ! 'z' Registers r8 and r9. ! 'I' A constant between 0 and 3 inclusive. ! 'J' A constant that has exactly one bit set. ! 'K' A constant that has exactly one bit clear. ! 'L' A constant between 0 and 255 inclusive. ! 'M' A constant between -255 and 0 inclusive. ! 'N' A constant between -3 and 0 inclusive. ! 'O' A constant between 1 and 4 inclusive. ! 'P' A constant between -4 and -1 inclusive. ! 'Q' A memory reference that is a stack push. ! 'R' A memory reference that is a stack pop. ! 'S' A memory reference that refers to a constant address of known value. ! 'T' The register indicated by Rx (not implemented yet). ! 'U' A constant that is not between 2 and 15 inclusive. ! 'Z' The constant 0. ! _Xtensa--'config/xtensa/constraints.md'_ ! 'a' General-purpose 32-bit register ! 'b' One-bit boolean register ! 'A' MAC16 40-bit accumulator register ! 'I' Signed 12-bit integer constant, for use in MOVI instructions ! 'J' Signed 8-bit integer constant, for use in ADDI instructions ! 'K' Integer constant valid for BccI instructions ! 'L' Unsigned constant valid for BccUI instructions  File: gcc.info, Node: Asm Labels, Next: Explicit Register Variables, Prev: Constraints, Up: Using Assembly Language with C --- 34342,34496 ---- return ((unsigned long long)tickh << 32)|tickl; } ! `f' Any 80387 floating-point (stack) register. ! `t' ! Top of 80387 floating-point stack (`%st(0)'). ! `u' ! Second from top of 80387 floating-point stack (`%st(1)'). ! `y' Any MMX register. ! `x' Any SSE register. ! `Yz' ! First SSE register (`%xmm0'). ! `I' Integer constant in the range 0 ... 31, for 32-bit shifts. ! `J' Integer constant in the range 0 ... 63, for 64-bit shifts. ! `K' Signed 8-bit integer constant. ! `L' ! `0xFF' or `0xFFFF', for andsi as a zero-extending move. ! `M' ! 0, 1, 2, or 3 (shifts for the `lea' instruction). ! `N' ! Unsigned 8-bit integer constant (for `in' and `out' instructions). ! `G' Standard 80387 floating point constant. ! `C' SSE constant zero operand. ! `e' 32-bit signed integer constant, or a symbolic reference known to fit that range (for immediate operands in sign-extending x86-64 instructions). ! `Z' 32-bit unsigned integer constant, or a symbolic reference known to fit that range (for immediate operands in zero-extending x86-64 instructions). ! ! _Xstormy16--`config/stormy16/stormy16.h'_ ! ! `a' Register r0. ! `b' Register r1. ! `c' Register r2. ! `d' Register r8. ! `e' Registers r0 through r7. ! `t' Registers r0 and r1. ! `y' The carry register. ! `z' Registers r8 and r9. ! `I' A constant between 0 and 3 inclusive. ! `J' A constant that has exactly one bit set. ! `K' A constant that has exactly one bit clear. ! `L' A constant between 0 and 255 inclusive. ! `M' A constant between -255 and 0 inclusive. ! `N' A constant between -3 and 0 inclusive. ! `O' A constant between 1 and 4 inclusive. ! `P' A constant between -4 and -1 inclusive. ! `Q' A memory reference that is a stack push. ! `R' A memory reference that is a stack pop. ! `S' A memory reference that refers to a constant address of known value. ! `T' The register indicated by Rx (not implemented yet). ! `U' A constant that is not between 2 and 15 inclusive. ! `Z' The constant 0. ! ! _Xtensa--`config/xtensa/constraints.md'_ ! ! `a' General-purpose 32-bit register ! `b' One-bit boolean register ! `A' MAC16 40-bit accumulator register ! `I' Signed 12-bit integer constant, for use in MOVI instructions ! `J' Signed 8-bit integer constant, for use in ADDI instructions ! `K' Integer constant valid for BccI instructions ! `L' Unsigned constant valid for BccUI instructions + +  File: gcc.info, Node: Asm Labels, Next: Explicit Register Variables, Prev: Constraints, Up: Using Assembly Language with C *************** File: gcc.info, Node: Asm Labels, Next *** 34112,34118 **** ----------------------------------------------- You can specify the name to be used in the assembler code for a C ! function or variable by writing the 'asm' (or '__asm__') keyword after the declarator. It is up to you to make sure that the assembler names you choose do not conflict with any other assembler symbols, or reference registers. --- 34498,34504 ---- ----------------------------------------------- You can specify the name to be used in the assembler code for a C ! function or variable by writing the `asm' (or `__asm__') keyword after the declarator. It is up to you to make sure that the assembler names you choose do not conflict with any other assembler symbols, or reference registers. *************** This sample shows how to specify the ass *** 34124,34135 **** int foo asm ("myfoo") = 2; ! This specifies that the name to be used for the variable 'foo' in the ! assembler code should be 'myfoo' rather than the usual '_foo'. On systems where an underscore is normally prepended to the name of a C ! variable, this feature allows you to define names for the linker that do ! not start with an underscore. GCC does not support using this feature with a non-static local variable since such variables do not have assembler names. If you are --- 34510,34521 ---- int foo asm ("myfoo") = 2; ! This specifies that the name to be used for the variable `foo' in the ! assembler code should be `myfoo' rather than the usual `_foo'. On systems where an underscore is normally prepended to the name of a C ! variable, this feature allows you to define names for the linker that ! do not start with an underscore. GCC does not support using this feature with a non-static local variable since such variables do not have assembler names. If you are *************** Assembler names for functions: *** 34140,34146 **** .............................. To specify the assembler name for functions, write a declaration for the ! function before its definition and put 'asm' there, like this: int func (int x, int y) asm ("MYFUNC"); --- 34526,34532 ---- .............................. To specify the assembler name for functions, write a declaration for the ! function before its definition and put `asm' there, like this: int func (int x, int y) asm ("MYFUNC"); *************** function before its definition and put ' *** 34148,34155 **** { /* ... */ ! This specifies that the name to be used for the function 'func' in the ! assembler code should be 'MYFUNC'.  File: gcc.info, Node: Explicit Register Variables, Next: Size of an asm, Prev: Asm Labels, Up: Using Assembly Language with C --- 34534,34541 ---- { /* ... */ ! This specifies that the name to be used for the function `func' in the ! assembler code should be `MYFUNC'.  File: gcc.info, Node: Explicit Register Variables, Next: Size of an asm, Prev: Asm Labels, Up: Using Assembly Language with C *************** specified register like this: *** 34183,34219 **** register int *foo asm ("r12"); ! Here 'r12' is the name of the register that should be used. Note that this is the same syntax used for defining local register variables, but ! for a global variable the declaration appears outside a function. The ! 'register' keyword is required, and cannot be combined with 'static'. The register name must be a valid register name for the target platform. Registers are a scarce resource on most systems and allowing the compiler to manage their usage usually results in the best code. However, under special circumstances it can make sense to reserve some globally. For example this may be useful in programs such as ! programming language interpreters that have a couple of global variables ! that are accessed very often. After defining a global register variable, for the current compilation unit: * The register is reserved entirely for this use, and will not be allocated for any other purpose. * The register is not saved and restored by any functions. * Stores into this register are never deleted even if they appear to be dead, but references may be deleted, moved or simplified. Note that these points _only_ apply to code that is compiled with the ! definition. The behavior of code that is merely linked in (for example code from libraries) is not affected. If you want to recompile source files that do not actually use your global register variable so they do not use the specified register for any other purpose, you need not actually add the global register ! declaration to their source code. It suffices to specify the compiler ! option '-ffixed-REG' (*note Code Gen Options::) to reserve the register. Declaring the variable ...................... --- 34569,34607 ---- register int *foo asm ("r12"); ! Here `r12' is the name of the register that should be used. Note that this is the same syntax used for defining local register variables, but ! for a global variable the declaration appears outside a function. The ! `register' keyword is required, and cannot be combined with `static'. The register name must be a valid register name for the target platform. Registers are a scarce resource on most systems and allowing the compiler to manage their usage usually results in the best code. However, under special circumstances it can make sense to reserve some globally. For example this may be useful in programs such as ! programming language interpreters that have a couple of global ! variables that are accessed very often. After defining a global register variable, for the current compilation unit: * The register is reserved entirely for this use, and will not be allocated for any other purpose. + * The register is not saved and restored by any functions. + * Stores into this register are never deleted even if they appear to be dead, but references may be deleted, moved or simplified. Note that these points _only_ apply to code that is compiled with the ! definition. The behavior of code that is merely linked in (for example code from libraries) is not affected. If you want to recompile source files that do not actually use your global register variable so they do not use the specified register for any other purpose, you need not actually add the global register ! declaration to their source code. It suffices to specify the compiler ! option `-ffixed-REG' (*note Code Gen Options::) to reserve the register. Declaring the variable ...................... *************** Global register variables can not have i *** 34222,34228 **** executable file has no means to supply initial contents for a register. When selecting a register, choose one that is normally saved and ! restored by function calls on your machine. This ensures that code which is unaware of this reservation (such as library routines) will restore it before returning. --- 34610,34616 ---- executable file has no means to supply initial contents for a register. When selecting a register, choose one that is normally saved and ! restored by function calls on your machine. This ensures that code which is unaware of this reservation (such as library routines) will restore it before returning. *************** that is not affected magically by the fu *** 34232,34258 **** Using the variable .................. ! When calling routines that are not aware of the reservation, be cautious ! if those routines call back into code which uses them. As an example, ! if you call the system library version of 'qsort', it may clobber your ! registers during execution, but (if you have selected appropriate ! registers) it will restore them before returning. However it will _not_ ! restore them before calling 'qsort''s comparison function. As a result, ! global values will not reliably be available to the comparison function ! unless the 'qsort' function itself is rebuilt. Similarly, it is not safe to access the global register variables from ! signal handlers or from more than one thread of control. Unless you recompile them specially for the task at hand, the system library routines may temporarily use the register for other things. ! On most machines, 'longjmp' restores to each global register variable ! the value it had at the time of the 'setjmp'. On some machines, ! however, 'longjmp' does not change the value of global register ! variables. To be portable, the function that called 'setjmp' should make other arrangements to save the values of the global register ! variables, and to restore them in a 'longjmp'. This way, the same thing ! happens regardless of what 'longjmp' does. Eventually there may be a way of asking the compiler to choose a register automatically, but first we need to figure out how it should --- 34620,34646 ---- Using the variable .................. ! When calling routines that are not aware of the reservation, be ! cautious if those routines call back into code which uses them. As an ! example, if you call the system library version of `qsort', it may ! clobber your registers during execution, but (if you have selected ! appropriate registers) it will restore them before returning. However ! it will _not_ restore them before calling `qsort''s comparison ! function. As a result, global values will not reliably be available to ! the comparison function unless the `qsort' function itself is rebuilt. Similarly, it is not safe to access the global register variables from ! signal handlers or from more than one thread of control. Unless you recompile them specially for the task at hand, the system library routines may temporarily use the register for other things. ! On most machines, `longjmp' restores to each global register variable ! the value it had at the time of the `setjmp'. On some machines, ! however, `longjmp' does not change the value of global register ! variables. To be portable, the function that called `setjmp' should make other arrangements to save the values of the global register ! variables, and to restore them in a `longjmp'. This way, the same thing ! happens regardless of what `longjmp' does. Eventually there may be a way of asking the compiler to choose a register automatically, but first we need to figure out how it should *************** specified register like this: *** 34270,34279 **** register int *foo asm ("r12"); ! Here 'r12' is the name of the register that should be used. Note that ! this is the same syntax used for defining global register variables, but ! for a local variable the declaration appears within a function. The ! 'register' keyword is required, and cannot be combined with 'static'. The register name must be a valid register name for the target platform. As with global register variables, it is recommended that you choose a --- 34658,34667 ---- register int *foo asm ("r12"); ! Here `r12' is the name of the register that should be used. Note that ! this is the same syntax used for defining global register variables, ! but for a local variable the declaration appears within a function. The ! `register' keyword is required, and cannot be combined with `static'. The register name must be a valid register name for the target platform. As with global register variables, it is recommended that you choose a *************** register that is normally saved and rest *** 34281,34293 **** machine, so that calls to library routines will not clobber it. The only supported use for this feature is to specify registers for ! input and output operands when calling Extended 'asm' (*note Extended Asm::). This may be necessary if the constraints for a particular ! machine don't provide sufficient control to select the desired register. ! To force an operand into a register, create a local variable and specify ! the register name after the variable's declaration. Then use the local ! variable for the 'asm' operand and specify any constraint letter that ! matches the register: register int *p1 asm ("r0") = ...; register int *p2 asm ("r1") = ...; --- 34669,34681 ---- machine, so that calls to library routines will not clobber it. The only supported use for this feature is to specify registers for ! input and output operands when calling Extended `asm' (*note Extended Asm::). This may be necessary if the constraints for a particular ! machine don't provide sufficient control to select the desired ! register. To force an operand into a register, create a local variable ! and specify the register name after the variable's declaration. Then ! use the local variable for the `asm' operand and specify any constraint ! letter that matches the register: register int *p1 asm ("r0") = ...; register int *p2 asm ("r1") = ...; *************** matches the register: *** 34295,34303 **** asm ("sysint" : "=r" (result) : "0" (p1), "r" (p2)); _Warning:_ In the above example, be aware that a register (for example ! 'r0') can be call-clobbered by subsequent code, including function calls ! and library calls for arithmetic operators on other variables (for ! example the initialization of 'p2'). In this case, use temporary variables for expressions between the register assignments: int t1 = ...; --- 34683,34691 ---- asm ("sysint" : "=r" (result) : "0" (p1), "r" (p2)); _Warning:_ In the above example, be aware that a register (for example ! `r0') can be call-clobbered by subsequent code, including function ! calls and library calls for arithmetic operators on other variables (for ! example the initialization of `p2'). In this case, use temporary variables for expressions between the register assignments: int t1 = ...; *************** variables for expressions between the re *** 34307,34322 **** asm ("sysint" : "=r" (result) : "0" (p1), "r" (p2)); Defining a register variable does not reserve the register. Other than ! when invoking the Extended 'asm', the contents of the specified register ! are not guaranteed. For this reason, the following uses are explicitly ! _not_ supported. If they appear to work, it is only happenstance, and ! may stop working as intended due to (seemingly) unrelated changes in ! surrounding code, or even minor changes in the optimization of a future ! version of gcc: - * Passing parameters to or from Basic 'asm' - * Passing parameters to or from Extended 'asm' without using input or - output operands. * Passing parameters to or from routines written in assembler (or other languages) using non-standard calling conventions. --- 34695,34712 ---- asm ("sysint" : "=r" (result) : "0" (p1), "r" (p2)); Defining a register variable does not reserve the register. Other than ! when invoking the Extended `asm', the contents of the specified ! register are not guaranteed. For this reason, the following uses are ! explicitly _not_ supported. If they appear to work, it is only ! happenstance, and may stop working as intended due to (seemingly) ! unrelated changes in surrounding code, or even minor changes in the ! optimization of a future version of gcc: ! ! * Passing parameters to or from Basic `asm' ! ! * Passing parameters to or from Extended `asm' without using input ! or output operands. * Passing parameters to or from routines written in assembler (or other languages) using non-standard calling conventions. *************** specifics for MIPS targets: (gccint)MIPS *** 34335,34353 ****  File: gcc.info, Node: Size of an asm, Prev: Explicit Register Variables, Up: Using Assembly Language with C ! 6.44.6 Size of an 'asm' ----------------------- ! Some targets require that GCC track the size of each instruction used in ! order to generate correct code. Because the final length of the code ! produced by an 'asm' statement is only known by the assembler, GCC must ! make an estimate as to how big it will be. It does this by counting the ! number of instructions in the pattern of the 'asm' and multiplying that ! by the length of the longest instruction supported by that processor. ! (When working out the number of instructions, it assumes that any ! occurrence of a newline or of whatever statement separator character is ! supported by the assembler - typically ';' -- indicates the end of an ! instruction.) Normally, GCC's estimate is adequate to ensure that correct code is generated, but it is possible to confuse the compiler if you use pseudo --- 34725,34743 ----  File: gcc.info, Node: Size of an asm, Prev: Explicit Register Variables, Up: Using Assembly Language with C ! 6.44.6 Size of an `asm' ----------------------- ! Some targets require that GCC track the size of each instruction used ! in order to generate correct code. Because the final length of the ! code produced by an `asm' statement is only known by the assembler, GCC ! must make an estimate as to how big it will be. It does this by ! counting the number of instructions in the pattern of the `asm' and ! multiplying that by the length of the longest instruction supported by ! that processor. (When working out the number of instructions, it ! assumes that any occurrence of a newline or of whatever statement ! separator character is supported by the assembler - typically `;' -- ! indicates the end of an instruction.) Normally, GCC's estimate is adequate to ensure that correct code is generated, but it is possible to confuse the compiler if you use pseudo *************** File: gcc.info, Node: Alternate Keyword *** 34363,34382 **** 6.45 Alternate Keywords ======================= ! '-ansi' and the various '-std' options disable certain keywords. This causes trouble when you want to use GNU C extensions, or a general-purpose header file that should be usable by all programs, ! including ISO C programs. The keywords 'asm', 'typeof' and 'inline' are ! not available in programs compiled with '-ansi' or '-std' (although ! 'inline' can be used in a program compiled with '-std=c99' or ! '-std=c11'). The ISO C99 keyword 'restrict' is only available when ! '-std=gnu99' (which will eventually be the default) or '-std=c99' (or ! the equivalent '-std=iso9899:1999'), or an option for a later standard version, is used. ! The way to solve these problems is to put '__' at the beginning and end ! of each problematical keyword. For example, use '__asm__' instead of ! 'asm', and '__inline__' instead of 'inline'. Other C compilers won't accept these alternative keywords; if you want to compile with another compiler, you can define the alternate keywords --- 34753,34772 ---- 6.45 Alternate Keywords ======================= ! `-ansi' and the various `-std' options disable certain keywords. This causes trouble when you want to use GNU C extensions, or a general-purpose header file that should be usable by all programs, ! including ISO C programs. The keywords `asm', `typeof' and `inline' ! are not available in programs compiled with `-ansi' or `-std' (although ! `inline' can be used in a program compiled with `-std=c99' or ! `-std=c11'). The ISO C99 keyword `restrict' is only available when ! `-std=gnu99' (which will eventually be the default) or `-std=c99' (or ! the equivalent `-std=iso9899:1999'), or an option for a later standard version, is used. ! The way to solve these problems is to put `__' at the beginning and ! end of each problematical keyword. For example, use `__asm__' instead ! of `asm', and `__inline__' instead of `inline'. Other C compilers won't accept these alternative keywords; if you want to compile with another compiler, you can define the alternate keywords *************** this: *** 34387,34413 **** #define __asm__ asm #endif ! '-pedantic' and other options cause warnings for many GNU C extensions. You can prevent such warnings within one expression by writing ! '__extension__' before the expression. '__extension__' has no effect aside from this.  File: gcc.info, Node: Incomplete Enums, Next: Function Names, Prev: Alternate Keywords, Up: C Extensions ! 6.46 Incomplete 'enum' Types ============================ ! You can define an 'enum' tag without specifying its possible values. This results in an incomplete type, much like what you get if you write ! 'struct foo' without describing the elements. A later declaration that does specify the possible values completes the type. You can't allocate variables or storage using the type while it is incomplete. However, you can work with pointers to that type. This extension may not be very useful, but it makes the handling of ! 'enum' more consistent with the way 'struct' and 'union' are handled. This extension is not supported by GNU C++. --- 34777,34803 ---- #define __asm__ asm #endif ! `-pedantic' and other options cause warnings for many GNU C extensions. You can prevent such warnings within one expression by writing ! `__extension__' before the expression. `__extension__' has no effect aside from this.  File: gcc.info, Node: Incomplete Enums, Next: Function Names, Prev: Alternate Keywords, Up: C Extensions ! 6.46 Incomplete `enum' Types ============================ ! You can define an `enum' tag without specifying its possible values. This results in an incomplete type, much like what you get if you write ! `struct foo' without describing the elements. A later declaration that does specify the possible values completes the type. You can't allocate variables or storage using the type while it is incomplete. However, you can work with pointers to that type. This extension may not be very useful, but it makes the handling of ! `enum' more consistent with the way `struct' and `union' are handled. This extension is not supported by GNU C++. *************** File: gcc.info, Node: Function Names, *** 34418,34440 **** ============================== GCC provides three magic variables that hold the name of the current ! function, as a string. The first of these is '__func__', which is part of the C99 standard: ! The identifier '__func__' is implicitly declared by the translator as ! if, immediately following the opening brace of each function definition, ! the declaration static const char __func__[] = "function-name"; appeared, where function-name is the name of the lexically-enclosing function. This name is the unadorned name of the function. ! '__FUNCTION__' is another name for '__func__', provided for backward compatibility with old versions of GCC. ! In C, '__PRETTY_FUNCTION__' is yet another name for '__func__'. ! However, in C++, '__PRETTY_FUNCTION__' contains the type signature of the function as well as its bare name. For example, this program: extern "C" { --- 34808,34830 ---- ============================== GCC provides three magic variables that hold the name of the current ! function, as a string. The first of these is `__func__', which is part of the C99 standard: ! The identifier `__func__' is implicitly declared by the translator as ! if, immediately following the opening brace of each function ! definition, the declaration static const char __func__[] = "function-name"; appeared, where function-name is the name of the lexically-enclosing function. This name is the unadorned name of the function. ! `__FUNCTION__' is another name for `__func__', provided for backward compatibility with old versions of GCC. ! In C, `__PRETTY_FUNCTION__' is yet another name for `__func__'. ! However, in C++, `__PRETTY_FUNCTION__' contains the type signature of the function as well as its bare name. For example, this program: extern "C" { *************** gives this output: *** 34464,34470 **** __PRETTY_FUNCTION__ = void a::sub(int) These identifiers are variables, not preprocessor macros, and may not ! be used to initialize 'char' arrays or be concatenated with other string literals.  --- 34854,34860 ---- __PRETTY_FUNCTION__ = void a::sub(int) These identifiers are variables, not preprocessor macros, and may not ! be used to initialize `char' arrays or be concatenated with other string literals.  *************** function. *** 34480,34529 **** 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 ! address of the current function, a value of '1' yields the return address of the caller of the current function, and so forth. When inlining the expected behavior is that the function returns the address of the function that is returned to. To work around this ! behavior use the 'noinline' function attribute. The LEVEL argument must be a constant integer. On some machines it may be impossible to determine the return address of any function other than the current one; in such cases, or when the top of the stack has been reached, this function ! returns '0' or a random value. In addition, ! '__builtin_frame_address' may be used to determine if the top of the stack has been reached. Additional post-processing of the returned value may be needed, see ! '__builtin_extract_return_addr'. Calling this function with a nonzero argument can have unpredictable effects, including crashing the calling program. As a result, calls that are considered unsafe are diagnosed when the ! '-Wframe-address' option is in effect. Such calls should only be made in debugging situations. -- Built-in Function: void * __builtin_extract_return_addr (void *ADDR) ! The address as returned by '__builtin_return_address' may have to be fed through this function to get the actual encoded address. ! For example, on the 31-bit S/390 platform the highest bit has to be ! masked out, or on SPARC platforms an offset has to be added for the ! true next instruction to be executed. If no fixup is needed, this function simply passes through ADDR. -- Built-in Function: void * __builtin_frob_return_address (void *ADDR) ! This function does the reverse of '__builtin_extract_return_addr'. -- Built-in Function: void * __builtin_frame_address (unsigned int LEVEL) ! This function is similar to '__builtin_return_address', but it returns the address of the function frame rather than the return ! address of the function. Calling '__builtin_frame_address' with a ! value of '0' yields the frame address of the current function, a ! value of '1' yields the frame address of the caller of the current function, and so forth. The frame is the area on the stack that holds local variables and --- 34870,34919 ---- 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 ! address of the current function, a value of `1' yields the return address of the caller of the current function, and so forth. When inlining the expected behavior is that the function returns the address of the function that is returned to. To work around this ! behavior use the `noinline' function attribute. The LEVEL argument must be a constant integer. On some machines it may be impossible to determine the return address of any function other than the current one; in such cases, or when the top of the stack has been reached, this function ! returns `0' or a random value. In addition, ! `__builtin_frame_address' may be used to determine if the top of the stack has been reached. Additional post-processing of the returned value may be needed, see ! `__builtin_extract_return_addr'. Calling this function with a nonzero argument can have unpredictable effects, including crashing the calling program. As a result, calls that are considered unsafe are diagnosed when the ! `-Wframe-address' option is in effect. Such calls should only be made in debugging situations. -- Built-in Function: void * __builtin_extract_return_addr (void *ADDR) ! The address as returned by `__builtin_return_address' may have to be fed through this function to get the actual encoded address. ! For example, on the 31-bit S/390 platform the highest bit has to ! be masked out, or on SPARC platforms an offset has to be added for ! the true next instruction to be executed. If no fixup is needed, this function simply passes through ADDR. -- Built-in Function: void * __builtin_frob_return_address (void *ADDR) ! This function does the reverse of `__builtin_extract_return_addr'. -- Built-in Function: void * __builtin_frame_address (unsigned int LEVEL) ! This function is similar to `__builtin_return_address', but it returns the address of the function frame rather than the return ! address of the function. Calling `__builtin_frame_address' with a ! value of `0' yields the frame address of the current function, a ! value of `1' yields the frame address of the caller of the current function, and so forth. The frame is the area on the stack that holds local variables and *************** function. *** 34532,34550 **** exact definition depends upon the processor and the calling convention. If the processor has a dedicated frame pointer register, and the function has a frame, then ! '__builtin_frame_address' returns the value of the frame pointer register. On some machines it may be impossible to determine the frame address of any function other than the current one; in such cases, or when the top of the stack has been reached, this function ! returns '0' if the first frame pointer is properly initialized by the startup code. Calling this function with a nonzero argument can have unpredictable effects, including crashing the calling program. As a result, calls that are considered unsafe are diagnosed when the ! '-Wframe-address' option is in effect. Such calls should only be made in debugging situations.  --- 34922,34940 ---- exact definition depends upon the processor and the calling convention. If the processor has a dedicated frame pointer register, and the function has a frame, then ! `__builtin_frame_address' returns the value of the frame pointer register. On some machines it may be impossible to determine the frame address of any function other than the current one; in such cases, or when the top of the stack has been reached, this function ! returns `0' if the first frame pointer is properly initialized by the startup code. Calling this function with a nonzero argument can have unpredictable effects, including crashing the calling program. As a result, calls that are considered unsafe are diagnosed when the ! `-Wframe-address' option is in effect. Such calls should only be made in debugging situations.  *************** same time. For example, on the x86 the *** 34559,34598 **** can be used this way. The first step in using these extensions is to provide the necessary ! data types. This should be done using an appropriate 'typedef': typedef int v4si __attribute__ ((vector_size (16))); ! The 'int' type specifies the base type, while the attribute specifies the vector size for the variable, measured in bytes. For example, the ! declaration above causes the compiler to set the mode for the 'v4si' ! type to be 16 bytes wide and divided into 'int' sized units. For a ! 32-bit 'int' this means a vector of 4 units of 4 bytes, and the ! corresponding mode of 'foo' is V4SI. ! The 'vector_size' attribute is only applicable to integral and float scalars, although arrays, pointers, and function return values are ! allowed in conjunction with this construct. Only sizes that are a power of two are currently allowed. All the basic integer types can be used as base types, both as signed ! and as unsigned: 'char', 'short', 'int', 'long', 'long long'. In ! addition, 'float' and 'double' can be used to build floating-point vector types. Specifying a combination that is not valid for the current architecture causes GCC to synthesize the instructions using a narrower mode. For ! example, if you specify a variable of type 'V4SI' and your architecture does not allow for this specific SIMD type, GCC produces code that uses ! 4 'SIs'. The types defined in this manner can be used with a subset of normal C operations. Currently, GCC allows using the following operators on ! these types: '+, -, *, /, unary minus, ^, |, &, ~, %'. ! The operations behave like C++ 'valarrays'. Addition is defined as the ! addition of the corresponding elements of the operands. For example, in ! the code below, each of the 4 elements in A is added to the corresponding 4 elements in B and the resulting vector is stored in C. typedef int v4si __attribute__ ((vector_size (16))); --- 34949,34988 ---- can be used this way. The first step in using these extensions is to provide the necessary ! data types. This should be done using an appropriate `typedef': typedef int v4si __attribute__ ((vector_size (16))); ! The `int' type specifies the base type, while the attribute specifies the vector size for the variable, measured in bytes. For example, the ! declaration above causes the compiler to set the mode for the `v4si' ! type to be 16 bytes wide and divided into `int' sized units. For a ! 32-bit `int' this means a vector of 4 units of 4 bytes, and the ! corresponding mode of `foo' is V4SI. ! The `vector_size' attribute is only applicable to integral and float scalars, although arrays, pointers, and function return values are ! allowed in conjunction with this construct. Only sizes that are a power of two are currently allowed. All the basic integer types can be used as base types, both as signed ! and as unsigned: `char', `short', `int', `long', `long long'. In ! addition, `float' and `double' can be used to build floating-point vector types. Specifying a combination that is not valid for the current architecture causes GCC to synthesize the instructions using a narrower mode. For ! example, if you specify a variable of type `V4SI' and your architecture does not allow for this specific SIMD type, GCC produces code that uses ! 4 `SIs'. The types defined in this manner can be used with a subset of normal C operations. Currently, GCC allows using the following operators on ! these types: `+, -, *, /, unary minus, ^, |, &, ~, %'. ! The operations behave like C++ `valarrays'. Addition is defined as ! the addition of the corresponding elements of the operands. For ! example, in the code below, each of the 4 elements in A is added to the corresponding 4 elements in B and the resulting vector is stored in C. typedef int v4si __attribute__ ((vector_size (16))); *************** minus or complement operators on a vecto *** 34607,34621 **** elements are the negative or complemented values of the corresponding elements in the operand. ! It is possible to use shifting operators '<<', '>>' on integer-type ! vectors. The operation is defined as following: '{a0, a1, ..., an} >> ! {b0, b1, ..., bn} == {a0 >> b0, a1 >> b1, ..., an >> bn}'. Vector operands must have the same number of elements. For convenience, it is allowed to use a binary vector operation where ! one operand is a scalar. In that case the compiler transforms the scalar operand into a vector where each element is the scalar from the ! operation. The transformation happens only if the scalar could be safely converted to the vector-element type. Consider the following code. --- 34997,35011 ---- elements are the negative or complemented values of the corresponding elements in the operand. ! It is possible to use shifting operators `<<', `>>' on integer-type ! vectors. The operation is defined as following: `{a0, a1, ..., an} >> ! {b0, b1, ..., bn} == {a0 >> b0, a1 >> b1, ..., an >> bn}'. Vector operands must have the same number of elements. For convenience, it is allowed to use a binary vector operation where ! one operand is a scalar. In that case the compiler transforms the scalar operand into a vector where each element is the scalar from the ! operation. The transformation happens only if the scalar could be safely converted to the vector-element type. Consider the following code. *************** code. *** 34629,34649 **** a = l + a; /* Error, cannot convert long to int. */ ! Vectors can be subscripted as if the vector were an array with the same ! number of elements and base type. Out of bound accesses invoke undefined behavior at run time. Warnings for out of bound accesses for ! vector subscription can be enabled with '-Warray-bounds'. ! Vector comparison is supported with standard comparison operators: '==, ! !=, <, <=, >, >='. Comparison operands can be vector expressions of ! integer-type or real-type. Comparison between integer-type vectors and ! real-type vectors are not supported. The result of the comparison is a ! vector of the same width and number of elements as the comparison operands with a signed integral element type. Vectors are compared element-wise producing 0 when comparison is false and -1 (constant of the appropriate type where all bits are set) ! otherwise. Consider the following example. typedef int v4si __attribute__ ((vector_size (16))); --- 35019,35039 ---- a = l + a; /* Error, cannot convert long to int. */ ! Vectors can be subscripted as if the vector were an array with the ! same number of elements and base type. Out of bound accesses invoke undefined behavior at run time. Warnings for out of bound accesses for ! vector subscription can be enabled with `-Warray-bounds'. ! Vector comparison is supported with standard comparison operators: ! `==, !=, <, <=, >, >='. Comparison operands can be vector expressions ! of integer-type or real-type. Comparison between integer-type vectors ! and real-type vectors are not supported. The result of the comparison ! is a vector of the same width and number of elements as the comparison operands with a signed integral element type. Vectors are compared element-wise producing 0 when comparison is false and -1 (constant of the appropriate type where all bits are set) ! otherwise. Consider the following example. typedef int v4si __attribute__ ((vector_size (16))); *************** otherwise. Consider the following examp *** 34654,34684 **** c = a > b; /* The result would be {0, 0,-1, 0} */ c = a == b; /* The result would be {0,-1, 0,-1} */ ! In C++, the ternary operator '?:' is available. 'a?b:c', where 'b' and ! 'c' are vectors of the same type and 'a' is an integer vector with the ! same number of elements of the same size as 'b' and 'c', computes all ! three arguments and creates a vector '{a[0]?b[0]:c[0], a[1]?b[1]:c[1], ! ...}'. Note that unlike in OpenCL, 'a' is thus interpreted as 'a != 0' ! and not 'a < 0'. As in the case of binary operations, this syntax is ! also accepted when one of 'b' or 'c' is a scalar that is then ! transformed into a vector. If both 'b' and 'c' are scalars and the type ! of 'true?b:c' has the same size as the element type of 'a', then 'b' and ! 'c' are converted to a vector type whose elements have this type and ! with the same number of elements as 'a'. ! In C++, the logic operators '!, &&, ||' are available for vectors. ! '!v' is equivalent to 'v == 0', 'a && b' is equivalent to 'a!=0 & b!=0' ! and 'a || b' is equivalent to 'a!=0 | b!=0'. For mixed operations ! between a scalar 's' and a vector 'v', 's && v' is equivalent to ! 's?v!=0:0' (the evaluation is short-circuit) and 'v && s' is equivalent ! to 'v!=0 & (s?-1:0)'. ! Vector shuffling is available using functions '__builtin_shuffle (vec, ! mask)' and '__builtin_shuffle (vec0, vec1, mask)'. Both functions ! construct a permutation of elements from one or two vectors and return a ! vector of the same type as the input vector(s). The MASK is an integral ! vector with the same width (W) and element count (N) as the output ! vector. The elements of the input vectors are numbered in memory ordering of VEC0 beginning at 0 and VEC1 beginning at N. The elements of MASK are --- 35044,35074 ---- c = a > b; /* The result would be {0, 0,-1, 0} */ c = a == b; /* The result would be {0,-1, 0,-1} */ ! In C++, the ternary operator `?:' is available. `a?b:c', where `b' and ! `c' are vectors of the same type and `a' is an integer vector with the ! same number of elements of the same size as `b' and `c', computes all ! three arguments and creates a vector `{a[0]?b[0]:c[0], a[1]?b[1]:c[1], ! ...}'. Note that unlike in OpenCL, `a' is thus interpreted as `a != 0' ! and not `a < 0'. As in the case of binary operations, this syntax is ! also accepted when one of `b' or `c' is a scalar that is then ! transformed into a vector. If both `b' and `c' are scalars and the type ! of `true?b:c' has the same size as the element type of `a', then `b' ! and `c' are converted to a vector type whose elements have this type ! and with the same number of elements as `a'. ! In C++, the logic operators `!, &&, ||' are available for vectors. ! `!v' is equivalent to `v == 0', `a && b' is equivalent to `a!=0 & b!=0' ! and `a || b' is equivalent to `a!=0 | b!=0'. For mixed operations ! between a scalar `s' and a vector `v', `s && v' is equivalent to ! `s?v!=0:0' (the evaluation is short-circuit) and `v && s' is equivalent ! to `v!=0 & (s?-1:0)'. ! Vector shuffling is available using functions `__builtin_shuffle (vec, ! mask)' and `__builtin_shuffle (vec0, vec1, mask)'. Both functions ! construct a permutation of elements from one or two vectors and return ! a vector of the same type as the input vector(s). The MASK is an ! integral vector with the same width (W) and element count (N) as the ! output vector. The elements of the input vectors are numbered in memory ordering of VEC0 beginning at 0 and VEC1 beginning at N. The elements of MASK are *************** two-operand case. *** 34698,34709 **** res = __builtin_shuffle (a, mask1); /* res is {1,2,2,4} */ res = __builtin_shuffle (a, b, mask2); /* res is {1,5,3,6} */ ! Note that '__builtin_shuffle' is intentionally semantically compatible ! with the OpenCL 'shuffle' and 'shuffle2' functions. You can declare variables and use them in function calls and returns, ! as well as in assignments and some casts. You can specify a vector type ! as a return type for a function. Vector types can also be used as function arguments. It is possible to cast from one vector type to another, provided they are of the same size (in fact, you can also cast vectors to and from other datatypes of the same size). --- 35088,35099 ---- res = __builtin_shuffle (a, mask1); /* res is {1,2,2,4} */ res = __builtin_shuffle (a, b, mask2); /* res is {1,5,3,6} */ ! Note that `__builtin_shuffle' is intentionally semantically compatible ! with the OpenCL `shuffle' and `shuffle2' functions. You can declare variables and use them in function calls and returns, ! as well as in assignments and some casts. You can specify a vector ! type as a return type for a function. Vector types can also be used as function arguments. It is possible to cast from one vector type to another, provided they are of the same size (in fact, you can also cast vectors to and from other datatypes of the same size). *************** signedness without a cast. *** 34714,34770 ****  File: gcc.info, Node: Offsetof, Next: __sync Builtins, Prev: Vector Extensions, Up: C Extensions ! 6.50 Support for 'offsetof' =========================== ! GCC implements for both C and C++ a syntactic extension to implement the ! 'offsetof' macro. primary: ! "__builtin_offsetof" "(" typename "," offsetof_member_designator ")" offsetof_member_designator: ! identifier ! | offsetof_member_designator "." identifier ! | offsetof_member_designator "[" expr "]" This extension is sufficient such that #define offsetof(TYPE, MEMBER) __builtin_offsetof (TYPE, MEMBER) ! is a suitable definition of the 'offsetof' macro. In C++, TYPE may be dependent. In either case, MEMBER may consist of a single identifier, or a sequence of member accesses and array references.  File: gcc.info, Node: __sync Builtins, Next: __atomic Builtins, Prev: Offsetof, Up: C Extensions ! 6.51 Legacy '__sync' Built-in Functions for Atomic Memory Access ================================================================ The following built-in functions 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 normal GCC ! practice by not using the '__builtin_' prefix and also by being overloaded so that they work on multiple types. ! The definition given in the Intel documentation allows only for the use ! of the types 'int', 'long', 'long long' or their unsigned counterparts. ! GCC allows any scalar type that is 1, 2, 4 or 8 bytes in size other than ! the C type '_Bool' or the C++ type 'bool'. Operations on pointer ! arguments are performed as if the operands were of the 'uintptr_t' type. ! That is, they are not scaled by the size of the type to which the ! pointer points. ! These functions are implemented in terms of the '__atomic' builtins ! (*note __atomic Builtins::). They should not be used for new code which ! should use the '__atomic' builtins instead. Not all operations are supported by all target processors. If a particular operation cannot be implemented on the target processor, a warning is generated and a call to an external function is generated. The external function carries the same name as the built-in version, ! with an additional suffix '_N' where N is the size of the data type. In most cases, these built-in functions are considered a "full barrier". That is, no memory operand is moved across the operation, --- 35104,35160 ----  File: gcc.info, Node: Offsetof, Next: __sync Builtins, Prev: Vector Extensions, Up: C Extensions ! 6.50 Support for `offsetof' =========================== ! GCC implements for both C and C++ a syntactic extension to implement ! the `offsetof' macro. primary: ! "__builtin_offsetof" "(" `typename' "," offsetof_member_designator ")" offsetof_member_designator: ! `identifier' ! | offsetof_member_designator "." `identifier' ! | offsetof_member_designator "[" `expr' "]" This extension is sufficient such that #define offsetof(TYPE, MEMBER) __builtin_offsetof (TYPE, MEMBER) ! is a suitable definition of the `offsetof' macro. In C++, TYPE may be dependent. In either case, MEMBER may consist of a single identifier, or a sequence of member accesses and array references.  File: gcc.info, Node: __sync Builtins, Next: __atomic Builtins, Prev: Offsetof, Up: C Extensions ! 6.51 Legacy `__sync' Built-in Functions for Atomic Memory Access ================================================================ The following built-in functions 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 normal GCC ! practice by not using the `__builtin_' prefix and also by being overloaded so that they work on multiple types. ! The definition given in the Intel documentation allows only for the ! use of the types `int', `long', `long long' or their unsigned ! counterparts. GCC allows any scalar type that is 1, 2, 4 or 8 bytes in ! size other than the C type `_Bool' or the C++ type `bool'. Operations ! on pointer arguments are performed as if the operands were of the ! `uintptr_t' type. That is, they are not scaled by the size of the type ! to which the pointer points. ! These functions are implemented in terms of the `__atomic' builtins ! (*note __atomic Builtins::). They should not be used for new code ! which should use the `__atomic' builtins instead. Not all operations are supported by all target processors. If a particular operation cannot be implemented on the target processor, a warning is generated and a call to an external function is generated. The external function carries the same name as the built-in version, ! with an additional suffix `_N' where N is the size of the data type. In most cases, these built-in functions are considered a "full barrier". That is, no memory operand is moved across the operation, *************** operation and from queuing stores after *** 34775,34796 **** All of the routines are described in the Intel documentation to take "an optional list of variables protected by the memory barrier". It's not clear what is meant by that; it could mean that _only_ the listed ! variables are protected, or it could mean a list of additional variables ! to be protected. The list is ignored by GCC which treats it as empty. ! GCC interprets an empty list as meaning that all globally accessible ! variables should be protected. ! 'TYPE __sync_fetch_and_add (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_fetch_and_sub (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_fetch_and_or (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_fetch_and_and (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_fetch_and_xor (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_fetch_and_nand (TYPE *ptr, TYPE value, ...)' These built-in functions perform the operation suggested by the name, and returns the value that had previously been in memory. That is, operations on integer operands have the following ! semantics. Operations on pointer arguments are performed as if the ! operands were of the 'uintptr_t' type. That is, they are not scaled by the size of the type to which the pointer points. { tmp = *ptr; *ptr OP= value; return tmp; } --- 35165,35186 ---- All of the routines are described in the Intel documentation to take "an optional list of variables protected by the memory barrier". It's not clear what is meant by that; it could mean that _only_ the listed ! variables are protected, or it could mean a list of additional ! variables to be protected. The list is ignored by GCC which treats it ! as empty. GCC interprets an empty list as meaning that all globally ! accessible variables should be protected. ! `TYPE __sync_fetch_and_add (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_fetch_and_sub (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_fetch_and_or (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_fetch_and_and (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_fetch_and_xor (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_fetch_and_nand (TYPE *ptr, TYPE value, ...)' These built-in functions perform the operation suggested by the name, and returns the value that had previously been in memory. That is, operations on integer operands have the following ! semantics. Operations on pointer arguments are performed as if ! the operands were of the `uintptr_t' type. That is, they are not scaled by the size of the type to which the pointer points. { tmp = *ptr; *ptr OP= value; return tmp; } *************** variables should be protected. *** 34799,34851 **** The object pointed to by the first argument must be of integer or pointer type. It must not be a Boolean type. ! _Note:_ GCC 4.4 and later implement '__sync_fetch_and_nand' as ! '*ptr = ~(tmp & value)' instead of '*ptr = ~tmp & value'. ! 'TYPE __sync_add_and_fetch (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_sub_and_fetch (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_or_and_fetch (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_and_and_fetch (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_xor_and_fetch (TYPE *ptr, TYPE value, ...)' ! 'TYPE __sync_nand_and_fetch (TYPE *ptr, TYPE value, ...)' These built-in functions perform the operation suggested by the name, and return the new value. That is, operations on integer operands have the following semantics. Operations on pointer ! operands are performed as if the operand's type were 'uintptr_t'. { *ptr OP= value; return *ptr; } { *ptr = ~(*ptr & value); return *ptr; } // nand The same constraints on arguments apply as for the corresponding ! '__sync_op_and_fetch' built-in functions. ! _Note:_ GCC 4.4 and later implement '__sync_nand_and_fetch' as ! '*ptr = ~(*ptr & value)' instead of '*ptr = ~*ptr & value'. ! 'bool __sync_bool_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)' ! 'TYPE __sync_val_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)' These built-in functions perform an atomic compare and swap. That ! is, if the current value of '*PTR' is OLDVAL, then write NEWVAL ! into '*PTR'. The "bool" version returns true if the comparison is successful and NEWVAL is written. The "val" version returns the contents of ! '*PTR' before the operation. ! '__sync_synchronize (...)' This built-in function issues a full memory barrier. ! 'TYPE __sync_lock_test_and_set (TYPE *ptr, TYPE value, ...)' ! This built-in function, as described by Intel, is not a traditional ! test-and-set operation, but rather an atomic exchange operation. ! It writes VALUE into '*PTR', and returns the previous contents of ! '*PTR'. Many targets have only minimal support for such locks, and do not support a full exchange operation. In this case, a target may support reduced functionality here by which the _only_ valid value to store is the immediate constant 1. The exact value actually ! stored in '*PTR' is implementation defined. This built-in function is not a full barrier, but rather an "acquire barrier". This means that references after the operation --- 35189,35241 ---- The object pointed to by the first argument must be of integer or pointer type. It must not be a Boolean type. ! _Note:_ GCC 4.4 and later implement `__sync_fetch_and_nand' as ! `*ptr = ~(tmp & value)' instead of `*ptr = ~tmp & value'. ! `TYPE __sync_add_and_fetch (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_sub_and_fetch (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_or_and_fetch (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_and_and_fetch (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_xor_and_fetch (TYPE *ptr, TYPE value, ...)' ! `TYPE __sync_nand_and_fetch (TYPE *ptr, TYPE value, ...)' These built-in functions perform the operation suggested by the name, and return the new value. That is, operations on integer operands have the following semantics. Operations on pointer ! operands are performed as if the operand's type were `uintptr_t'. { *ptr OP= value; return *ptr; } { *ptr = ~(*ptr & value); return *ptr; } // nand The same constraints on arguments apply as for the corresponding ! `__sync_op_and_fetch' built-in functions. ! _Note:_ GCC 4.4 and later implement `__sync_nand_and_fetch' as ! `*ptr = ~(*ptr & value)' instead of `*ptr = ~*ptr & value'. ! `bool __sync_bool_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)' ! `TYPE __sync_val_compare_and_swap (TYPE *ptr, TYPE oldval, TYPE newval, ...)' These built-in functions perform an atomic compare and swap. That ! is, if the current value of `*PTR' is OLDVAL, then write NEWVAL ! into `*PTR'. The "bool" version returns true if the comparison is successful and NEWVAL is written. The "val" version returns the contents of ! `*PTR' before the operation. ! `__sync_synchronize (...)' This built-in function issues a full memory barrier. ! `TYPE __sync_lock_test_and_set (TYPE *ptr, TYPE value, ...)' ! This built-in function, as described by Intel, is not a ! traditional test-and-set operation, but rather an atomic exchange ! operation. It writes VALUE into `*PTR', and returns the previous ! contents of `*PTR'. Many targets have only minimal support for such locks, and do not support a full exchange operation. In this case, a target may support reduced functionality here by which the _only_ valid value to store is the immediate constant 1. The exact value actually ! stored in `*PTR' is implementation defined. This built-in function is not a full barrier, but rather an "acquire barrier". This means that references after the operation *************** variables should be protected. *** 34853,34868 **** previous memory stores may not be globally visible yet, and previous memory loads may not yet be satisfied. ! 'void __sync_lock_release (TYPE *ptr, ...)' This built-in function releases the lock acquired by ! '__sync_lock_test_and_set'. Normally this means writing the ! constant 0 to '*PTR'. ! This built-in function is not a full barrier, but rather a "release ! barrier". This means that all previous memory stores are globally ! visible, and all previous memory loads have been satisfied, but ! following memory reads are not prevented from being speculated to ! before the barrier.  File: gcc.info, Node: __atomic Builtins, Next: Integer Overflow Builtins, Prev: __sync Builtins, Up: C Extensions --- 35243,35258 ---- previous memory stores may not be globally visible yet, and previous memory loads may not yet be satisfied. ! `void __sync_lock_release (TYPE *ptr, ...)' This built-in function releases the lock acquired by ! `__sync_lock_test_and_set'. Normally this means writing the ! constant 0 to `*PTR'. ! This built-in function is not a full barrier, but rather a ! "release barrier". This means that all previous memory stores are ! globally visible, and all previous memory loads have been ! satisfied, but following memory reads are not prevented from being ! speculated to before the barrier.  File: gcc.info, Node: __atomic Builtins, Next: Integer Overflow Builtins, Prev: __sync Builtins, Up: C Extensions *************** File: gcc.info, Node: __atomic Builtins *** 34872,34900 **** The following built-in functions approximately match the requirements for the C++11 memory model. They are all identified by being prefixed ! with '__atomic' and most are overloaded so that they work with multiple types. ! These functions are intended to replace the legacy '__sync' builtins. The main difference is that the memory order that is requested is a ! parameter to the functions. New code should always use the '__atomic' ! builtins rather than the '__sync' builtins. ! Note that the '__atomic' builtins assume that programs will conform to the C++11 memory model. In particular, they assume that programs are free of data races. See the C++11 standard for detailed requirements. ! The '__atomic' builtins can be used with any integral scalar or pointer ! type that is 1, 2, 4, or 8 bytes in length. 16-byte integral types are ! also allowed if '__int128' (*note __int128::) is supported by the ! architecture. The four non-arithmetic functions (load, store, exchange, and compare_exchange) all have a generic version as well. This generic version works on any data type. It uses the lock-free built-in function if the specific data type size makes that possible; otherwise, an external call is left to be resolved at run time. This external call is ! the same format with the addition of a 'size_t' parameter inserted as the first parameter indicating the size of the object being pointed to. All objects must be the same size. --- 35262,35290 ---- The following built-in functions approximately match the requirements for the C++11 memory model. They are all identified by being prefixed ! with `__atomic' and most are overloaded so that they work with multiple types. ! These functions are intended to replace the legacy `__sync' builtins. The main difference is that the memory order that is requested is a ! parameter to the functions. New code should always use the `__atomic' ! builtins rather than the `__sync' builtins. ! Note that the `__atomic' builtins assume that programs will conform to the C++11 memory model. In particular, they assume that programs are free of data races. See the C++11 standard for detailed requirements. ! The `__atomic' builtins can be used with any integral scalar or ! pointer type that is 1, 2, 4, or 8 bytes in length. 16-byte integral ! types are also allowed if `__int128' (*note __int128::) is supported by ! the architecture. The four non-arithmetic functions (load, store, exchange, and compare_exchange) all have a generic version as well. This generic version works on any data type. It uses the lock-free built-in function if the specific data type size makes that possible; otherwise, an external call is left to be resolved at run time. This external call is ! the same format with the addition of a `size_t' parameter inserted as the first parameter indicating the size of the object being pointed to. All objects must be the same size. *************** strength. The description of each memor *** 34914,34949 **** illustrate the effects and is not a specification; see the C++11 memory model for precise semantics. ! '__ATOMIC_RELAXED' Implies no inter-thread ordering constraints. ! '__ATOMIC_CONSUME' ! This is currently implemented using the stronger '__ATOMIC_ACQUIRE' memory order because of a deficiency in C++11's semantics for ! 'memory_order_consume'. ! '__ATOMIC_ACQUIRE' Creates an inter-thread happens-before constraint from the release (or stronger) semantic store to this acquire load. Can prevent hoisting of code to before the operation. ! '__ATOMIC_RELEASE' Creates an inter-thread happens-before constraint to acquire (or stronger) semantic loads that read from this release store. Can prevent sinking of code to after the operation. ! '__ATOMIC_ACQ_REL' ! Combines the effects of both '__ATOMIC_ACQUIRE' and ! '__ATOMIC_RELEASE'. ! '__ATOMIC_SEQ_CST' ! Enforces total ordering with all other '__ATOMIC_SEQ_CST' operations. Note that in the C++11 memory model, _fences_ (e.g., ! '__atomic_thread_fence') take effect in combination with other atomic ! operations on specific memory locations (e.g., atomic loads); operations ! on specific memory locations do not necessarily affect other operations ! in the same way. Target architectures are encouraged to provide their own patterns for each of the atomic built-in functions. If no target is provided, the ! original non-memory model set of '__sync' atomic built-in functions are used, along with any required synchronization fences surrounding it in order to achieve the proper behavior. Execution in this case is subject to the same restrictions as those built-in functions. --- 35304,35344 ---- illustrate the effects and is not a specification; see the C++11 memory model for precise semantics. ! `__ATOMIC_RELAXED' Implies no inter-thread ordering constraints. ! ! `__ATOMIC_CONSUME' ! This is currently implemented using the stronger `__ATOMIC_ACQUIRE' memory order because of a deficiency in C++11's semantics for ! `memory_order_consume'. ! ! `__ATOMIC_ACQUIRE' Creates an inter-thread happens-before constraint from the release (or stronger) semantic store to this acquire load. Can prevent hoisting of code to before the operation. ! ! `__ATOMIC_RELEASE' Creates an inter-thread happens-before constraint to acquire (or stronger) semantic loads that read from this release store. Can prevent sinking of code to after the operation. ! ! `__ATOMIC_ACQ_REL' ! Combines the effects of both `__ATOMIC_ACQUIRE' and ! `__ATOMIC_RELEASE'. ! ! `__ATOMIC_SEQ_CST' ! Enforces total ordering with all other `__ATOMIC_SEQ_CST' operations. Note that in the C++11 memory model, _fences_ (e.g., ! `__atomic_thread_fence') take effect in combination with other atomic ! operations on specific memory locations (e.g., atomic loads); ! operations on specific memory locations do not necessarily affect other ! operations in the same way. Target architectures are encouraged to provide their own patterns for each of the atomic built-in functions. If no target is provided, the ! original non-memory model set of `__sync' atomic built-in functions are used, along with any required synchronization fences surrounding it in order to achieve the proper behavior. Execution in this case is subject to the same restrictions as those built-in functions. *************** to be resolved at run time. *** 34954,34967 **** When implementing patterns for these built-in functions, the memory order parameter can be ignored as long as the pattern implements the ! most restrictive '__ATOMIC_SEQ_CST' memory order. Any of the other memory orders execute correctly with this memory order but they may not execute as efficiently as they could with a more appropriate implementation of the relaxed requirements. Note that the C++11 standard allows for the memory order parameter to be determined at run time rather than at compile time. These built-in ! functions map any run-time value to '__ATOMIC_SEQ_CST' rather than invoke a runtime library call or inline a switch statement. This is standard compliant, safe, and the simplest approach for now. --- 35349,35362 ---- When implementing patterns for these built-in functions, the memory order parameter can be ignored as long as the pattern implements the ! most restrictive `__ATOMIC_SEQ_CST' memory order. Any of the other memory orders execute correctly with this memory order but they may not execute as efficiently as they could with a more appropriate implementation of the relaxed requirements. Note that the C++11 standard allows for the memory order parameter to be determined at run time rather than at compile time. These built-in ! functions map any run-time value to `__ATOMIC_SEQ_CST' rather than invoke a runtime library call or inline a switch statement. This is standard compliant, safe, and the simplest approach for now. *************** values ensures proper usage. *** 34972,35056 **** -- Built-in Function: TYPE __atomic_load_n (TYPE *ptr, int memorder) This built-in function implements an atomic load operation. It ! returns the contents of '*PTR'. - The valid memory order variants are '__ATOMIC_RELAXED', - '__ATOMIC_SEQ_CST', '__ATOMIC_ACQUIRE', and '__ATOMIC_CONSUME'. -- Built-in Function: void __atomic_load (TYPE *ptr, TYPE *ret, int memorder) This is the generic version of an atomic load. It returns the ! contents of '*PTR' in '*RET'. -- Built-in Function: void __atomic_store_n (TYPE *ptr, TYPE val, int memorder) This built-in function implements an atomic store operation. It ! writes 'VAL' into '*PTR'. - The valid memory order variants are '__ATOMIC_RELAXED', - '__ATOMIC_SEQ_CST', and '__ATOMIC_RELEASE'. -- Built-in Function: void __atomic_store (TYPE *ptr, TYPE *val, int memorder) This is the generic version of an atomic store. It stores the ! value of '*VAL' into '*PTR'. -- Built-in Function: TYPE __atomic_exchange_n (TYPE *ptr, TYPE val, int memorder) ! This built-in function implements an atomic exchange operation. It ! writes VAL into '*PTR', and returns the previous contents of ! '*PTR'. - The valid memory order variants are '__ATOMIC_RELAXED', - '__ATOMIC_SEQ_CST', '__ATOMIC_ACQUIRE', '__ATOMIC_RELEASE', and - '__ATOMIC_ACQ_REL'. -- Built-in Function: void __atomic_exchange (TYPE *ptr, TYPE *val, TYPE *ret, int memorder) This is the generic version of an atomic exchange. It stores the ! contents of '*VAL' into '*PTR'. The original value of '*PTR' is ! copied into '*RET'. ! -- Built-in Function: bool __atomic_compare_exchange_n (TYPE *ptr, TYPE ! *expected, TYPE desired, bool weak, int success_memorder, int ! failure_memorder) This built-in function implements an atomic compare and exchange ! operation. This compares the contents of '*PTR' with the contents ! of '*EXPECTED'. If equal, the operation is a _read-modify-write_ ! operation that writes DESIRED into '*PTR'. If they are not equal, ! the operation is a _read_ and the current contents of '*PTR' are ! written into '*EXPECTED'. WEAK is true for weak compare_exchange, which may fail spuriously, and false for the strong variation, which never fails spuriously. Many targets only offer the strong variation and ignore the parameter. When in doubt, use the strong variation. ! If DESIRED is written into '*PTR' then true is returned and memory is affected according to the memory order specified by SUCCESS_MEMORDER. There are no restrictions on what memory order can be used here. Otherwise, false is returned and memory is affected according to ! FAILURE_MEMORDER. This memory order cannot be '__ATOMIC_RELEASE' ! nor '__ATOMIC_ACQ_REL'. It also cannot be a stronger order than that specified by SUCCESS_MEMORDER. -- Built-in Function: bool __atomic_compare_exchange (TYPE *ptr, TYPE ! *expected, TYPE *desired, bool weak, int success_memorder, int ! failure_memorder) This built-in function implements the generic version of ! '__atomic_compare_exchange'. The function is virtually identical ! to '__atomic_compare_exchange_n', except the desired value is also a pointer. ! -- Built-in Function: TYPE __atomic_add_fetch (TYPE *ptr, TYPE val, int ! memorder) ! -- Built-in Function: TYPE __atomic_sub_fetch (TYPE *ptr, TYPE val, int ! memorder) ! -- Built-in Function: TYPE __atomic_and_fetch (TYPE *ptr, TYPE val, int ! memorder) ! -- Built-in Function: TYPE __atomic_xor_fetch (TYPE *ptr, TYPE val, int ! memorder) -- Built-in Function: TYPE __atomic_or_fetch (TYPE *ptr, TYPE val, int memorder) -- Built-in Function: TYPE __atomic_nand_fetch (TYPE *ptr, TYPE val, --- 35367,35459 ---- -- Built-in Function: TYPE __atomic_load_n (TYPE *ptr, int memorder) This built-in function implements an atomic load operation. It ! returns the contents of `*PTR'. ! ! The valid memory order variants are `__ATOMIC_RELAXED', ! `__ATOMIC_SEQ_CST', `__ATOMIC_ACQUIRE', and `__ATOMIC_CONSUME'. -- Built-in Function: void __atomic_load (TYPE *ptr, TYPE *ret, int memorder) This is the generic version of an atomic load. It returns the ! contents of `*PTR' in `*RET'. ! -- Built-in Function: void __atomic_store_n (TYPE *ptr, TYPE val, int memorder) This built-in function implements an atomic store operation. It ! writes `VAL' into `*PTR'. ! ! The valid memory order variants are `__ATOMIC_RELAXED', ! `__ATOMIC_SEQ_CST', and `__ATOMIC_RELEASE'. -- Built-in Function: void __atomic_store (TYPE *ptr, TYPE *val, int memorder) This is the generic version of an atomic store. It stores the ! value of `*VAL' into `*PTR'. ! -- Built-in Function: TYPE __atomic_exchange_n (TYPE *ptr, TYPE val, int memorder) ! This built-in function implements an atomic exchange operation. ! It writes VAL into `*PTR', and returns the previous contents of ! `*PTR'. ! ! The valid memory order variants are `__ATOMIC_RELAXED', ! `__ATOMIC_SEQ_CST', `__ATOMIC_ACQUIRE', `__ATOMIC_RELEASE', and ! `__ATOMIC_ACQ_REL'. -- Built-in Function: void __atomic_exchange (TYPE *ptr, TYPE *val, TYPE *ret, int memorder) This is the generic version of an atomic exchange. It stores the ! contents of `*VAL' into `*PTR'. The original value of `*PTR' is ! copied into `*RET'. ! ! -- Built-in Function: bool __atomic_compare_exchange_n (TYPE *ptr, ! TYPE *expected, TYPE desired, bool weak, int ! success_memorder, int failure_memorder) This built-in function implements an atomic compare and exchange ! operation. This compares the contents of `*PTR' with the contents ! of `*EXPECTED'. If equal, the operation is a _read-modify-write_ ! operation that writes DESIRED into `*PTR'. If they are not equal, ! the operation is a _read_ and the current contents of `*PTR' are ! written into `*EXPECTED'. WEAK is true for weak compare_exchange, which may fail spuriously, and false for the strong variation, which never fails spuriously. Many targets only offer the strong variation and ignore the parameter. When in doubt, use the strong variation. ! If DESIRED is written into `*PTR' then true is returned and memory is affected according to the memory order specified by SUCCESS_MEMORDER. There are no restrictions on what memory order can be used here. Otherwise, false is returned and memory is affected according to ! FAILURE_MEMORDER. This memory order cannot be `__ATOMIC_RELEASE' ! nor `__ATOMIC_ACQ_REL'. It also cannot be a stronger order than that specified by SUCCESS_MEMORDER. + -- Built-in Function: bool __atomic_compare_exchange (TYPE *ptr, TYPE ! *expected, TYPE *desired, bool weak, int success_memorder, ! int failure_memorder) This built-in function implements the generic version of ! `__atomic_compare_exchange'. The function is virtually identical ! to `__atomic_compare_exchange_n', except the desired value is also a pointer. ! ! -- Built-in Function: TYPE __atomic_add_fetch (TYPE *ptr, TYPE val, ! int memorder) ! -- Built-in Function: TYPE __atomic_sub_fetch (TYPE *ptr, TYPE val, ! int memorder) ! -- Built-in Function: TYPE __atomic_and_fetch (TYPE *ptr, TYPE val, ! int memorder) ! -- Built-in Function: TYPE __atomic_xor_fetch (TYPE *ptr, TYPE val, ! int memorder) -- Built-in Function: TYPE __atomic_or_fetch (TYPE *ptr, TYPE val, int memorder) -- Built-in Function: TYPE __atomic_nand_fetch (TYPE *ptr, TYPE val, *************** values ensures proper usage. *** 35058,35064 **** These built-in functions perform the operation suggested by the name, and return the result of the operation. Operations on pointer arguments are performed as if the operands were of the ! 'uintptr_t' type. That is, they are not scaled by the size of the type to which the pointer points. { *ptr OP= val; return *ptr; } --- 35461,35467 ---- These built-in functions perform the operation suggested by the name, and return the result of the operation. Operations on pointer arguments are performed as if the operands were of the ! `uintptr_t' type. That is, they are not scaled by the size of the type to which the pointer points. { *ptr OP= val; return *ptr; } *************** values ensures proper usage. *** 35067,35137 **** pointer type. It must not be a Boolean type. All memory orders are valid. ! -- Built-in Function: TYPE __atomic_fetch_add (TYPE *ptr, TYPE val, int ! memorder) ! -- Built-in Function: TYPE __atomic_fetch_sub (TYPE *ptr, TYPE val, int ! memorder) ! -- Built-in Function: TYPE __atomic_fetch_and (TYPE *ptr, TYPE val, int ! memorder) ! -- Built-in Function: TYPE __atomic_fetch_xor (TYPE *ptr, TYPE val, int ! memorder) -- Built-in Function: TYPE __atomic_fetch_or (TYPE *ptr, TYPE val, int memorder) -- Built-in Function: TYPE __atomic_fetch_nand (TYPE *ptr, TYPE val, int memorder) These built-in functions perform the operation suggested by the ! name, and return the value that had previously been in '*PTR'. Operations on pointer arguments are performed as if the operands ! were of the 'uintptr_t' type. That is, they are not scaled by the size of the type to which the pointer points. { tmp = *ptr; *ptr OP= val; return tmp; } The same constraints on arguments apply as for the corresponding ! '__atomic_op_fetch' built-in functions. All memory orders are valid. -- Built-in Function: bool __atomic_test_and_set (void *ptr, int memorder) - This built-in function performs an atomic test-and-set operation on ! the byte at '*PTR'. The byte is set to some implementation defined ! nonzero "set" value and the return value is 'true' if and only if ! the previous contents were "set". It should be only used for ! operands of type 'bool' or 'char'. For other types only part of ! the value may be set. All memory orders are valid. - -- Built-in Function: void __atomic_clear (bool *ptr, int memorder) This built-in function performs an atomic clear operation on ! '*PTR'. After the operation, '*PTR' contains 0. It should be only ! used for operands of type 'bool' or 'char' and in conjunction with ! '__atomic_test_and_set'. For other types it may only clear ! partially. If the type is not 'bool' prefer using ! '__atomic_store'. ! The valid memory order variants are '__ATOMIC_RELAXED', ! '__ATOMIC_SEQ_CST', and '__ATOMIC_RELEASE'. - -- Built-in Function: void __atomic_thread_fence (int memorder) This built-in function acts as a synchronization fence between threads based on the specified memory order. All memory orders are valid. - -- Built-in Function: void __atomic_signal_fence (int memorder) This built-in function acts as a synchronization fence between a thread and signal handlers based in the same thread. All memory orders are valid. - -- Built-in Function: bool __atomic_always_lock_free (size_t size, void - *ptr) This built-in function returns true if objects of SIZE bytes always generate lock-free atomic instructions for the target architecture. SIZE must resolve to a compile-time constant and the result also --- 35470,35540 ---- pointer type. It must not be a Boolean type. All memory orders are valid. ! ! -- Built-in Function: TYPE __atomic_fetch_add (TYPE *ptr, TYPE val, ! int memorder) ! -- Built-in Function: TYPE __atomic_fetch_sub (TYPE *ptr, TYPE val, ! int memorder) ! -- Built-in Function: TYPE __atomic_fetch_and (TYPE *ptr, TYPE val, ! int memorder) ! -- Built-in Function: TYPE __atomic_fetch_xor (TYPE *ptr, TYPE val, ! int memorder) -- Built-in Function: TYPE __atomic_fetch_or (TYPE *ptr, TYPE val, int memorder) -- Built-in Function: TYPE __atomic_fetch_nand (TYPE *ptr, TYPE val, int memorder) These built-in functions perform the operation suggested by the ! name, and return the value that had previously been in `*PTR'. Operations on pointer arguments are performed as if the operands ! were of the `uintptr_t' type. That is, they are not scaled by the size of the type to which the pointer points. { tmp = *ptr; *ptr OP= val; return tmp; } The same constraints on arguments apply as for the corresponding ! `__atomic_op_fetch' built-in functions. All memory orders are valid. + -- Built-in Function: bool __atomic_test_and_set (void *ptr, int memorder) This built-in function performs an atomic test-and-set operation on ! the byte at `*PTR'. The byte is set to some implementation ! defined nonzero "set" value and the return value is `true' if and ! only if the previous contents were "set". It should be only used ! for operands of type `bool' or `char'. For other types only part ! of the value may be set. All memory orders are valid. + -- Built-in Function: void __atomic_clear (bool *ptr, int memorder) This built-in function performs an atomic clear operation on ! `*PTR'. After the operation, `*PTR' contains 0. It should be ! only used for operands of type `bool' or `char' and in conjunction ! with `__atomic_test_and_set'. For other types it may only clear ! partially. If the type is not `bool' prefer using `__atomic_store'. ! The valid memory order variants are `__ATOMIC_RELAXED', ! `__ATOMIC_SEQ_CST', and `__ATOMIC_RELEASE'. + -- Built-in Function: void __atomic_thread_fence (int memorder) This built-in function acts as a synchronization fence between threads based on the specified memory order. All memory orders are valid. + -- Built-in Function: void __atomic_signal_fence (int memorder) This built-in function acts as a synchronization fence between a thread and signal handlers based in the same thread. All memory orders are valid. + -- Built-in Function: bool __atomic_always_lock_free (size_t size, + void *ptr) This built-in function returns true if objects of SIZE bytes always generate lock-free atomic instructions for the target architecture. SIZE must resolve to a compile-time constant and the result also *************** values ensures proper usage. *** 35143,35155 **** if (__atomic_always_lock_free (sizeof (long long), 0)) -- Built-in Function: bool __atomic_is_lock_free (size_t size, void *ptr) - This built-in function returns true if objects of SIZE bytes always ! generate lock-free atomic instructions for the target architecture. ! If the built-in function is not known to be lock-free, a call is ! made to a runtime routine named '__atomic_is_lock_free'. PTR is an optional pointer to the object that may be used to determine alignment. A value of 0 indicates typical alignment --- 35546,35559 ---- if (__atomic_always_lock_free (sizeof (long long), 0)) + -- Built-in Function: bool __atomic_is_lock_free (size_t size, void *ptr) This built-in function returns true if objects of SIZE bytes always ! generate lock-free atomic instructions for the target ! architecture. If the built-in function is not known to be ! lock-free, a call is made to a runtime routine named ! `__atomic_is_lock_free'. PTR is an optional pointer to the object that may be used to determine alignment. A value of 0 indicates typical alignment *************** operations together with checking whethe *** 35179,35185 **** -- Built-in Function: bool __builtin_uaddll_overflow (unsigned long long int a, unsigned long long int b, unsigned long long int *res) - These built-in functions promote the first two operands into infinite precision signed type and perform addition on those promoted operands. The result is then cast to the type the third --- 35583,35588 ---- *************** operations together with checking whethe *** 35197,35202 **** --- 35600,35606 ---- these built-in functions where possible, like conditional jump on overflow after addition, conditional jump on carry etc. + -- Built-in Function: bool __builtin_sub_overflow (TYPE1 a, TYPE2 b, TYPE3 *res) -- Built-in Function: bool __builtin_ssub_overflow (int a, int b, int *************** operations together with checking whethe *** 35212,35221 **** -- Built-in Function: bool __builtin_usubll_overflow (unsigned long long int a, unsigned long long int b, unsigned long long int *res) - These built-in functions are similar to the add overflow checking ! built-in functions above, except they perform subtraction, subtract ! the second argument from the first one, instead of addition. -- Built-in Function: bool __builtin_mul_overflow (TYPE1 a, TYPE2 b, TYPE3 *res) --- 35616,35626 ---- -- Built-in Function: bool __builtin_usubll_overflow (unsigned long long int a, unsigned long long int b, unsigned long long int *res) These built-in functions are similar to the add overflow checking ! built-in functions above, except they perform subtraction, ! subtract the second argument from the first one, instead of ! addition. ! -- Built-in Function: bool __builtin_mul_overflow (TYPE1 a, TYPE2 b, TYPE3 *res) *************** operations together with checking whethe *** 35232,35242 **** -- Built-in Function: bool __builtin_umulll_overflow (unsigned long long int a, unsigned long long int b, unsigned long long int *res) - These built-in functions are similar to the add overflow checking built-in functions above, except they perform multiplication, instead of addition.  File: gcc.info, Node: x86 specific memory model extensions for transactional memory, Next: Object Size Checking, Prev: Integer Overflow Builtins, Up: C Extensions --- 35637,35647 ---- -- Built-in Function: bool __builtin_umulll_overflow (unsigned long long int a, unsigned long long int b, unsigned long long int *res) These built-in functions are similar to the add overflow checking built-in functions above, except they perform multiplication, instead of addition. +  File: gcc.info, Node: x86 specific memory model extensions for transactional memory, Next: Object Size Checking, Prev: Integer Overflow Builtins, Up: C Extensions *************** The x86 architecture supports additional *** 35247,35261 **** lock critical sections for hardware lock elision. These must be specified in addition to an existing memory order to atomic intrinsics. ! '__ATOMIC_HLE_ACQUIRE' Start lock elision on a lock variable. Memory order must be ! '__ATOMIC_ACQUIRE' or stronger. ! '__ATOMIC_HLE_RELEASE' End lock elision on a lock variable. Memory order must be ! '__ATOMIC_RELEASE' or stronger. When a lock acquire fails, it is required for good performance to abort ! the transaction quickly. This can be done with a '_mm_pause'. #include // For _mm_pause --- 35652,35667 ---- lock critical sections for hardware lock elision. These must be specified in addition to an existing memory order to atomic intrinsics. ! `__ATOMIC_HLE_ACQUIRE' Start lock elision on a lock variable. Memory order must be ! `__ATOMIC_ACQUIRE' or stronger. ! ! `__ATOMIC_HLE_RELEASE' End lock elision on a lock variable. Memory order must be ! `__ATOMIC_RELEASE' or stronger. When a lock acquire fails, it is required for good performance to abort ! the transaction quickly. This can be done with a `_mm_pause'. #include // For _mm_pause *************** prevent some buffer overflow attacks. *** 35281,35296 **** TYPE) is a built-in construct that returns a constant number of bytes from PTR to the end of the object PTR pointer points to (if known ! at compile time). '__builtin_object_size' never evaluates its ! arguments for side-effects. If there are any side-effects in them, ! it returns '(size_t) -1' for TYPE 0 or 1 and '(size_t) 0' for TYPE ! 2 or 3. If there are multiple objects PTR can point to and all of ! them are known at compile time, the returned number is the maximum ! of remaining byte counts in those objects if TYPE & 2 is 0 and ! minimum if nonzero. If it is not possible to determine which ! objects PTR points to at compile time, '__builtin_object_size' ! should return '(size_t) -1' for TYPE 0 or 1 and '(size_t) 0' for ! TYPE 2 or 3. TYPE is an integer constant from 0 to 3. If the least significant bit is clear, objects are whole variables, if it is set, a closest --- 35687,35702 ---- TYPE) is a built-in construct that returns a constant number of bytes from PTR to the end of the object PTR pointer points to (if known ! at compile time). `__builtin_object_size' never evaluates its ! arguments for side-effects. If there are any side-effects in ! them, it returns `(size_t) -1' for TYPE 0 or 1 and `(size_t) 0' ! for TYPE 2 or 3. If there are multiple objects PTR can point to ! and all of them are known at compile time, the returned number is ! the maximum of remaining byte counts in those objects if TYPE & 2 ! is 0 and minimum if nonzero. If it is not possible to determine ! which objects PTR points to at compile time, ! `__builtin_object_size' should return `(size_t) -1' for TYPE 0 or ! 1 and `(size_t) 0' for TYPE 2 or 3. TYPE is an integer constant from 0 to 3. If the least significant bit is clear, objects are whole variables, if it is set, a closest *************** prevent some buffer overflow attacks. *** 35312,35326 **** assert (__builtin_object_size (q, 1) == sizeof (var.b)); There are built-in functions added for many common string operation ! functions, e.g., for 'memcpy' '__builtin___memcpy_chk' built-in is provided. This built-in has an additional last argument, which is the number of bytes remaining in object the DEST argument points to or ! '(size_t) -1' if the size is not known. The built-in functions are optimized into the normal string functions ! like 'memcpy' if the last argument is '(size_t) -1' or if it is known at ! compile time that the destination object will not be overflown. If the ! compiler can determine at compile time the object will be always overflown, it issues a warning. The intended use can be e.g. --- 35718,35732 ---- assert (__builtin_object_size (q, 1) == sizeof (var.b)); There are built-in functions added for many common string operation ! functions, e.g., for `memcpy' `__builtin___memcpy_chk' built-in is provided. This built-in has an additional last argument, which is the number of bytes remaining in object the DEST argument points to or ! `(size_t) -1' if the size is not known. The built-in functions are optimized into the normal string functions ! like `memcpy' if the last argument is `(size_t) -1' or if it is known ! at compile time that the destination object will not be overflown. If ! the compiler can determine at compile time the object will be always overflown, it issues a warning. The intended use can be e.g. *************** overflown, it issues a warning. *** 35347,35355 **** will abort the program at run time. */ memcpy (&buf[6], "abcde", 5); ! Such built-in functions are provided for 'memcpy', 'mempcpy', ! 'memmove', 'memset', 'strcpy', 'stpcpy', 'strncpy', 'strcat' and ! 'strncat'. There are also checking built-in functions for formatted output functions. --- 35753,35761 ---- will abort the program at run time. */ memcpy (&buf[6], "abcde", 5); ! Such built-in functions are provided for `memcpy', `mempcpy', ! `memmove', `memset', `strcpy', `stpcpy', `strncpy', `strcat' and ! `strncat'. There are also checking built-in functions for formatted output functions. *************** functions. *** 35361,35382 **** int __builtin___vsnprintf_chk (char *s, size_t maxlen, int flag, size_t os, const char *fmt, va_list ap); ! The added FLAG argument is passed unchanged to '__sprintf_chk' etc. functions and can contain implementation specific flags on what additional security measures the checking function might take, such as ! handling '%n' differently. The OS argument is the object size S points to, like in the other ! built-in functions. There is a small difference in the behavior though, ! if OS is '(size_t) -1', the built-in functions are optimized into the ! non-checking functions only if FLAG is 0, otherwise the checking ! function is called with OS argument set to '(size_t) -1'. In addition to this, there are checking built-in functions ! '__builtin___printf_chk', '__builtin___vprintf_chk', ! '__builtin___fprintf_chk' and '__builtin___vfprintf_chk'. These have just one additional argument, FLAG, right before format string FMT. If ! the compiler is able to optimize them to 'fputc' etc. functions, it does, otherwise the checking function is called and the FLAG argument passed to it. --- 35767,35788 ---- int __builtin___vsnprintf_chk (char *s, size_t maxlen, int flag, size_t os, const char *fmt, va_list ap); ! The added FLAG argument is passed unchanged to `__sprintf_chk' etc. functions and can contain implementation specific flags on what additional security measures the checking function might take, such as ! handling `%n' differently. The OS argument is the object size S points to, like in the other ! built-in functions. There is a small difference in the behavior ! though, if OS is `(size_t) -1', the built-in functions are optimized ! into the non-checking functions only if FLAG is 0, otherwise the ! checking function is called with OS argument set to `(size_t) -1'. In addition to this, there are checking built-in functions ! `__builtin___printf_chk', `__builtin___vprintf_chk', ! `__builtin___fprintf_chk' and `__builtin___vfprintf_chk'. These have just one additional argument, FLAG, right before format string FMT. If ! the compiler is able to optimize them to `fputc' etc. functions, it does, otherwise the checking function is called and the FLAG argument passed to it. *************** File: gcc.info, Node: Pointer Bounds Ch *** 35389,35400 **** GCC provides a set of built-in functions to control Pointer Bounds Checker instrumentation. Note that all Pointer Bounds Checker builtins can be used even if you compile with Pointer Bounds Checker off ! ('-fno-check-pointer-bounds'). The behavior may differ in such case as documented below. ! -- Built-in Function: void * __builtin___bnd_set_ptr_bounds (const void ! *Q, size_t SIZE) ! This built-in function returns a new pointer with the value of Q, and associate it with the bounds [Q, Q+SIZE-1]. With Pointer Bounds Checker off, the built-in function just returns the first --- 35795,35805 ---- GCC provides a set of built-in functions to control Pointer Bounds Checker instrumentation. Note that all Pointer Bounds Checker builtins can be used even if you compile with Pointer Bounds Checker off ! (`-fno-check-pointer-bounds'). The behavior may differ in such case as documented below. ! -- Built-in Function: void * __builtin___bnd_set_ptr_bounds (const ! void *Q, size_t SIZE) This built-in function returns a new pointer with the value of Q, and associate it with the bounds [Q, Q+SIZE-1]. With Pointer Bounds Checker off, the built-in function just returns the first *************** documented below. *** 35407,35415 **** return __builtin___bnd_set_ptr_bounds (p, n); } -- Built-in Function: void * __builtin___bnd_narrow_ptr_bounds (const void *P, const void *Q, size_t SIZE) - This built-in function returns a new pointer with the value of P and associates it with the narrowed bounds formed by the intersection of bounds associated with Q and the bounds [P, P + --- 35812,35820 ---- return __builtin___bnd_set_ptr_bounds (p, n); } + -- Built-in Function: void * __builtin___bnd_narrow_ptr_bounds (const void *P, const void *Q, size_t SIZE) This built-in function returns a new pointer with the value of P and associates it with the narrowed bounds formed by the intersection of bounds associated with Q and the bounds [P, P + *************** documented below. *** 35426,35434 **** sizeof(object))); } -- Built-in Function: void * __builtin___bnd_copy_ptr_bounds (const void *Q, const void *R) - This built-in function returns a new pointer with the value of Q, and associates it with the bounds already associated with pointer R. With Pointer Bounds Checker off, the built-in function just --- 35831,35839 ---- sizeof(object))); } + -- Built-in Function: void * __builtin___bnd_copy_ptr_bounds (const void *Q, const void *R) This built-in function returns a new pointer with the value of Q, and associates it with the bounds already associated with pointer R. With Pointer Bounds Checker off, the built-in function just *************** documented below. *** 35439,35463 **** int *field_ptr = __builtin___bnd_copy_ptr_bounds (&objptr->int_field, objptr); -- Built-in Function: void * __builtin___bnd_init_ptr_bounds (const void *Q) - This built-in function returns a new pointer with the value of Q, and associates it with INIT (allowing full memory access) bounds. ! With Pointer Bounds Checker off, the built-in function just returns ! the first argument. -- Built-in Function: void * __builtin___bnd_null_ptr_bounds (const void *Q) - This built-in function returns a new pointer with the value of Q, and associates it with NULL (allowing no memory access) bounds. ! With Pointer Bounds Checker off, the built-in function just returns ! the first argument. - -- Built-in Function: void __builtin___bnd_store_ptr_bounds (const void - **PTR_ADDR, const void *PTR_VAL) This built-in function stores the bounds associated with pointer PTR_VAL and location PTR_ADDR into Bounds Table. This can be useful to propagate bounds from legacy code without touching the --- 35844,35868 ---- int *field_ptr = __builtin___bnd_copy_ptr_bounds (&objptr->int_field, objptr); + -- Built-in Function: void * __builtin___bnd_init_ptr_bounds (const void *Q) This built-in function returns a new pointer with the value of Q, and associates it with INIT (allowing full memory access) bounds. ! With Pointer Bounds Checker off, the built-in function just ! returns the first argument. ! -- Built-in Function: void * __builtin___bnd_null_ptr_bounds (const void *Q) This built-in function returns a new pointer with the value of Q, and associates it with NULL (allowing no memory access) bounds. ! With Pointer Bounds Checker off, the built-in function just ! returns the first argument. + -- Built-in Function: void __builtin___bnd_store_ptr_bounds (const + void **PTR_ADDR, const void *PTR_VAL) This built-in function stores the bounds associated with pointer PTR_VAL and location PTR_ADDR into Bounds Table. This can be useful to propagate bounds from legacy code without touching the *************** documented below. *** 35465,35473 **** With Pointer Bounds Checker off, the built-in function call is ignored. -- Built-in Function: void __builtin___bnd_chk_ptr_lbounds (const void *Q) - This built-in function checks if the pointer Q is within the lower bound of its associated bounds. With Pointer Bounds Checker off, the built-in function call is ignored. --- 35870,35878 ---- With Pointer Bounds Checker off, the built-in function call is ignored. + -- Built-in Function: void __builtin___bnd_chk_ptr_lbounds (const void *Q) This built-in function checks if the pointer Q is within the lower bound of its associated bounds. With Pointer Bounds Checker off, the built-in function call is ignored. *************** documented below. *** 35483,35498 **** return dst; } -- Built-in Function: void __builtin___bnd_chk_ptr_ubounds (const void *Q) - This built-in function checks if the pointer Q is within the upper bound of its associated bounds. With Pointer Bounds Checker off, the built-in function call is ignored. -- Built-in Function: void __builtin___bnd_chk_ptr_bounds (const void *Q, size_t SIZE) - This built-in function checks if [Q, Q + SIZE - 1] is within the lower and upper bounds associated with Q. With Pointer Bounds Checker off, the built-in function call is ignored. --- 35888,35903 ---- return dst; } + -- Built-in Function: void __builtin___bnd_chk_ptr_ubounds (const void *Q) This built-in function checks if the pointer Q is within the upper bound of its associated bounds. With Pointer Bounds Checker off, the built-in function call is ignored. + -- Built-in Function: void __builtin___bnd_chk_ptr_bounds (const void *Q, size_t SIZE) This built-in function checks if [Q, Q + SIZE - 1] is within the lower and upper bounds associated with Q. With Pointer Bounds Checker off, the built-in function call is ignored. *************** documented below. *** 35508,35531 **** return dst; } -- Built-in Function: const void * __builtin___bnd_get_ptr_lbound (const void *Q) - This built-in function returns the lower bound associated with the pointer Q, as a pointer value. This is useful for debugging using ! 'printf'. With Pointer Bounds Checker off, the built-in function returns 0. void *lb = __builtin___bnd_get_ptr_lbound (q); void *ub = __builtin___bnd_get_ptr_ubound (q); printf ("q = %p lb(q) = %p ub(q) = %p", q, lb, ub); -- Built-in Function: const void * __builtin___bnd_get_ptr_ubound (const void *Q) - This built-in function returns the upper bound (which is a pointer) - associated with the pointer Q. With Pointer Bounds Checker off, - the built-in function returns -1.  File: gcc.info, Node: Cilk Plus Builtins, Next: Other Builtins, Prev: Pointer Bounds Checker builtins, Up: C Extensions --- 35913,35937 ---- return dst; } + -- Built-in Function: const void * __builtin___bnd_get_ptr_lbound (const void *Q) This built-in function returns the lower bound associated with the pointer Q, as a pointer value. This is useful for debugging using ! `printf'. With Pointer Bounds Checker off, the built-in function returns 0. void *lb = __builtin___bnd_get_ptr_lbound (q); void *ub = __builtin___bnd_get_ptr_ubound (q); printf ("q = %p lb(q) = %p ub(q) = %p", q, lb, ub); + -- Built-in Function: const void * __builtin___bnd_get_ptr_ubound (const void *Q) + This built-in function returns the upper bound (which is a + pointer) associated with the pointer Q. With Pointer Bounds + Checker off, the built-in function returns -1.  File: gcc.info, Node: Cilk Plus Builtins, Next: Other Builtins, Prev: Pointer Bounds Checker builtins, Up: C Extensions *************** File: gcc.info, Node: Cilk Plus Builtin *** 35534,35559 **** ========================================================== GCC provides support for the following built-in reduction functions if ! Cilk Plus is enabled. Cilk Plus can be enabled using the '-fcilkplus' flag. ! * '__sec_implicit_index' ! * '__sec_reduce' ! * '__sec_reduce_add' ! * '__sec_reduce_all_nonzero' ! * '__sec_reduce_all_zero' ! * '__sec_reduce_any_nonzero' ! * '__sec_reduce_any_zero' ! * '__sec_reduce_max' ! * '__sec_reduce_min' ! * '__sec_reduce_max_ind' ! * '__sec_reduce_min_ind' ! * '__sec_reduce_mul' ! * '__sec_reduce_mutating' Further details and examples about these built-in functions are described in the Cilk Plus language manual which can be found at ! .  File: gcc.info, Node: Other Builtins, Next: Target Builtins, Prev: Cilk Plus Builtins, Up: C Extensions --- 35940,35977 ---- ========================================================== GCC provides support for the following built-in reduction functions if ! Cilk Plus is enabled. Cilk Plus can be enabled using the `-fcilkplus' flag. ! * `__sec_implicit_index' ! ! * `__sec_reduce' ! ! * `__sec_reduce_add' ! ! * `__sec_reduce_all_nonzero' ! ! * `__sec_reduce_all_zero' ! ! * `__sec_reduce_any_nonzero' ! ! * `__sec_reduce_any_zero' ! ! * `__sec_reduce_max' ! ! * `__sec_reduce_min' ! ! * `__sec_reduce_max_ind' ! ! * `__sec_reduce_min_ind' ! ! * `__sec_reduce_mul' ! ! * `__sec_reduce_mutating' Further details and examples about these built-in functions are described in the Cilk Plus language manual which can be found at ! `https://www.cilkplus.org'.  File: gcc.info, Node: Other Builtins, Next: Target Builtins, Prev: Cilk Plus Builtins, Up: C Extensions *************** general use of these functions. *** 35573,35698 **** the standard C library functions discussed below, or that expand to library calls, GCC built-in functions are always expanded inline and thus do not have corresponding entry points and their address cannot be ! obtained. Attempting to use them in an expression other than a function ! call results in a compile-time error. GCC includes built-in versions of many of the functions in the standard C library. These functions come in two forms: one whose names start ! with the '__builtin_' prefix, and the other without. Both forms have the same type (including prototype), the same address (when their address is taken), and the same meaning as the C library functions even ! if you specify the '-fno-builtin' option *note C Dialect Options::). ! Many of these functions are only optimized in certain cases; if they are ! not optimized in a particular case, a call to the library function is ! emitted. ! Outside strict ISO C mode ('-ansi', '-std=c90', '-std=c99' or ! '-std=c11'), the functions '_exit', 'alloca', 'bcmp', 'bzero', ! 'dcgettext', 'dgettext', 'dremf', 'dreml', 'drem', 'exp10f', 'exp10l', ! 'exp10', 'ffsll', 'ffsl', 'ffs', 'fprintf_unlocked', 'fputs_unlocked', ! 'gammaf', 'gammal', 'gamma', 'gammaf_r', 'gammal_r', 'gamma_r', ! 'gettext', 'index', 'isascii', 'j0f', 'j0l', 'j0', 'j1f', 'j1l', 'j1', ! 'jnf', 'jnl', 'jn', 'lgammaf_r', 'lgammal_r', 'lgamma_r', 'mempcpy', ! 'pow10f', 'pow10l', 'pow10', 'printf_unlocked', 'rindex', 'scalbf', ! 'scalbl', 'scalb', 'signbit', 'signbitf', 'signbitl', 'signbitd32', ! 'signbitd64', 'signbitd128', 'significandf', 'significandl', ! 'significand', 'sincosf', 'sincosl', 'sincos', 'stpcpy', 'stpncpy', ! 'strcasecmp', 'strdup', 'strfmon', 'strncasecmp', 'strndup', 'toascii', ! 'y0f', 'y0l', 'y0', 'y1f', 'y1l', 'y1', 'ynf', 'ynl' and 'yn' may be handled as built-in functions. All these functions have corresponding ! versions prefixed with '__builtin_', which may be used even in strict C90 mode. ! The ISO C99 functions '_Exit', 'acoshf', 'acoshl', 'acosh', 'asinhf', ! 'asinhl', 'asinh', 'atanhf', 'atanhl', 'atanh', 'cabsf', 'cabsl', ! 'cabs', 'cacosf', 'cacoshf', 'cacoshl', 'cacosh', 'cacosl', 'cacos', ! 'cargf', 'cargl', 'carg', 'casinf', 'casinhf', 'casinhl', 'casinh', ! 'casinl', 'casin', 'catanf', 'catanhf', 'catanhl', 'catanh', 'catanl', ! 'catan', 'cbrtf', 'cbrtl', 'cbrt', 'ccosf', 'ccoshf', 'ccoshl', 'ccosh', ! 'ccosl', 'ccos', 'cexpf', 'cexpl', 'cexp', 'cimagf', 'cimagl', 'cimag', ! 'clogf', 'clogl', 'clog', 'conjf', 'conjl', 'conj', 'copysignf', ! 'copysignl', 'copysign', 'cpowf', 'cpowl', 'cpow', 'cprojf', 'cprojl', ! 'cproj', 'crealf', 'creall', 'creal', 'csinf', 'csinhf', 'csinhl', ! 'csinh', 'csinl', 'csin', 'csqrtf', 'csqrtl', 'csqrt', 'ctanf', ! 'ctanhf', 'ctanhl', 'ctanh', 'ctanl', 'ctan', 'erfcf', 'erfcl', 'erfc', ! 'erff', 'erfl', 'erf', 'exp2f', 'exp2l', 'exp2', 'expm1f', 'expm1l', ! 'expm1', 'fdimf', 'fdiml', 'fdim', 'fmaf', 'fmal', 'fmaxf', 'fmaxl', ! 'fmax', 'fma', 'fminf', 'fminl', 'fmin', 'hypotf', 'hypotl', 'hypot', ! 'ilogbf', 'ilogbl', 'ilogb', 'imaxabs', 'isblank', 'iswblank', ! 'lgammaf', 'lgammal', 'lgamma', 'llabs', 'llrintf', 'llrintl', 'llrint', ! 'llroundf', 'llroundl', 'llround', 'log1pf', 'log1pl', 'log1p', 'log2f', ! 'log2l', 'log2', 'logbf', 'logbl', 'logb', 'lrintf', 'lrintl', 'lrint', ! 'lroundf', 'lroundl', 'lround', 'nearbyintf', 'nearbyintl', 'nearbyint', ! 'nextafterf', 'nextafterl', 'nextafter', 'nexttowardf', 'nexttowardl', ! 'nexttoward', 'remainderf', 'remainderl', 'remainder', 'remquof', ! 'remquol', 'remquo', 'rintf', 'rintl', 'rint', 'roundf', 'roundl', ! 'round', 'scalblnf', 'scalblnl', 'scalbln', 'scalbnf', 'scalbnl', ! 'scalbn', 'snprintf', 'tgammaf', 'tgammal', 'tgamma', 'truncf', ! 'truncl', 'trunc', 'vfscanf', 'vscanf', 'vsnprintf' and 'vsscanf' are ! handled as built-in functions except in strict ISO C90 mode ('-ansi' or ! '-std=c90'). ! There are also built-in versions of the ISO C99 functions 'acosf', ! 'acosl', 'asinf', 'asinl', 'atan2f', 'atan2l', 'atanf', 'atanl', ! 'ceilf', 'ceill', 'cosf', 'coshf', 'coshl', 'cosl', 'expf', 'expl', ! 'fabsf', 'fabsl', 'floorf', 'floorl', 'fmodf', 'fmodl', 'frexpf', ! 'frexpl', 'ldexpf', 'ldexpl', 'log10f', 'log10l', 'logf', 'logl', ! 'modfl', 'modf', 'powf', 'powl', 'sinf', 'sinhf', 'sinhl', 'sinl', ! 'sqrtf', 'sqrtl', 'tanf', 'tanhf', 'tanhl' and 'tanl' that are recognized in any mode since ISO C90 reserves these names for the purpose to which ISO C99 puts them. All these functions have ! corresponding versions prefixed with '__builtin_'. ! There are also GNU extension functions 'clog10', 'clog10f' and ! 'clog10l' which names are reserved by ISO C99 for future use. All these ! functions have versions prefixed with '__builtin_'. ! The ISO C94 functions 'iswalnum', 'iswalpha', 'iswcntrl', 'iswdigit', ! 'iswgraph', 'iswlower', 'iswprint', 'iswpunct', 'iswspace', 'iswupper', ! 'iswxdigit', 'towlower' and 'towupper' are handled as built-in functions ! except in strict ISO C90 mode ('-ansi' or '-std=c90'). ! The ISO C90 functions 'abort', 'abs', 'acos', 'asin', 'atan2', 'atan', ! 'calloc', 'ceil', 'cosh', 'cos', 'exit', 'exp', 'fabs', 'floor', 'fmod', ! 'fprintf', 'fputs', 'frexp', 'fscanf', 'isalnum', 'isalpha', 'iscntrl', ! 'isdigit', 'isgraph', 'islower', 'isprint', 'ispunct', 'isspace', ! 'isupper', 'isxdigit', 'tolower', 'toupper', 'labs', 'ldexp', 'log10', ! 'log', 'malloc', 'memchr', 'memcmp', 'memcpy', 'memset', 'modf', 'pow', ! 'printf', 'putchar', 'puts', 'scanf', 'sinh', 'sin', 'snprintf', ! 'sprintf', 'sqrt', 'sscanf', 'strcat', 'strchr', 'strcmp', 'strcpy', ! 'strcspn', 'strlen', 'strncat', 'strncmp', 'strncpy', 'strpbrk', ! 'strrchr', 'strspn', 'strstr', 'tanh', 'tan', 'vfprintf', 'vprintf' and ! 'vsprintf' are all recognized as built-in functions unless ! '-fno-builtin' is specified (or '-fno-builtin-FUNCTION' is specified for ! an individual function). All of these functions have corresponding ! versions prefixed with '__builtin_'. GCC provides built-in versions of the ISO C99 floating-point comparison macros that avoid raising exceptions for unordered operands. They have ! the same names as the standard macros ( 'isgreater', 'isgreaterequal', ! 'isless', 'islessequal', 'islessgreater', and 'isunordered') , with ! '__builtin_' prefixed. We intend for a library implementor to be able ! to simply '#define' each standard macro to its built-in equivalent. In ! the same fashion, GCC provides 'fpclassify', 'isfinite', 'isinf_sign', ! 'isnormal' and 'signbit' built-ins used with '__builtin_' prefixed. The ! 'isinf' and 'isnan' built-in functions appear both with and without the ! '__builtin_' prefix. -- Built-in Function: void *__builtin_alloca (size_t size) ! The '__builtin_alloca' function must be called at block scope. The ! function allocates an object SIZE bytes large on the stack of the ! calling function. The object is aligned on the default stack alignment boundary for the target determined by the ! '__BIGGEST_ALIGNMENT__' macro. The '__builtin_alloca' function returns a pointer to the first byte of the allocated object. The lifetime of the allocated object ends just before the calling ! function returns to its caller. This is so even when ! '__builtin_alloca' is called within a nested block. ! For example, the following function allocates eight objects of 'n' bytes each on the stack, storing a pointer to each in consecutive ! elements of the array 'a'. It then passes the array to function ! 'g' which can safely use the storage pointed to by each of the array elements. void f (unsigned n) --- 35991,36116 ---- the standard C library functions discussed below, or that expand to library calls, GCC built-in functions are always expanded inline and thus do not have corresponding entry points and their address cannot be ! obtained. Attempting to use them in an expression other than a ! function call results in a compile-time error. GCC includes built-in versions of many of the functions in the standard C library. These functions come in two forms: one whose names start ! with the `__builtin_' prefix, and the other without. Both forms have the same type (including prototype), the same address (when their address is taken), and the same meaning as the C library functions even ! if you specify the `-fno-builtin' option *note C Dialect Options::). ! Many of these functions are only optimized in certain cases; if they ! are not optimized in a particular case, a call to the library function ! is emitted. ! Outside strict ISO C mode (`-ansi', `-std=c90', `-std=c99' or ! `-std=c11'), the functions `_exit', `alloca', `bcmp', `bzero', ! `dcgettext', `dgettext', `dremf', `dreml', `drem', `exp10f', `exp10l', ! `exp10', `ffsll', `ffsl', `ffs', `fprintf_unlocked', `fputs_unlocked', ! `gammaf', `gammal', `gamma', `gammaf_r', `gammal_r', `gamma_r', ! `gettext', `index', `isascii', `j0f', `j0l', `j0', `j1f', `j1l', `j1', ! `jnf', `jnl', `jn', `lgammaf_r', `lgammal_r', `lgamma_r', `mempcpy', ! `pow10f', `pow10l', `pow10', `printf_unlocked', `rindex', `scalbf', ! `scalbl', `scalb', `signbit', `signbitf', `signbitl', `signbitd32', ! `signbitd64', `signbitd128', `significandf', `significandl', ! `significand', `sincosf', `sincosl', `sincos', `stpcpy', `stpncpy', ! `strcasecmp', `strdup', `strfmon', `strncasecmp', `strndup', `toascii', ! `y0f', `y0l', `y0', `y1f', `y1l', `y1', `ynf', `ynl' and `yn' may be handled as built-in functions. All these functions have corresponding ! versions prefixed with `__builtin_', which may be used even in strict C90 mode. ! The ISO C99 functions `_Exit', `acoshf', `acoshl', `acosh', `asinhf', ! `asinhl', `asinh', `atanhf', `atanhl', `atanh', `cabsf', `cabsl', ! `cabs', `cacosf', `cacoshf', `cacoshl', `cacosh', `cacosl', `cacos', ! `cargf', `cargl', `carg', `casinf', `casinhf', `casinhl', `casinh', ! `casinl', `casin', `catanf', `catanhf', `catanhl', `catanh', `catanl', ! `catan', `cbrtf', `cbrtl', `cbrt', `ccosf', `ccoshf', `ccoshl', ! `ccosh', `ccosl', `ccos', `cexpf', `cexpl', `cexp', `cimagf', `cimagl', ! `cimag', `clogf', `clogl', `clog', `conjf', `conjl', `conj', ! `copysignf', `copysignl', `copysign', `cpowf', `cpowl', `cpow', ! `cprojf', `cprojl', `cproj', `crealf', `creall', `creal', `csinf', ! `csinhf', `csinhl', `csinh', `csinl', `csin', `csqrtf', `csqrtl', ! `csqrt', `ctanf', `ctanhf', `ctanhl', `ctanh', `ctanl', `ctan', ! `erfcf', `erfcl', `erfc', `erff', `erfl', `erf', `exp2f', `exp2l', ! `exp2', `expm1f', `expm1l', `expm1', `fdimf', `fdiml', `fdim', `fmaf', ! `fmal', `fmaxf', `fmaxl', `fmax', `fma', `fminf', `fminl', `fmin', ! `hypotf', `hypotl', `hypot', `ilogbf', `ilogbl', `ilogb', `imaxabs', ! `isblank', `iswblank', `lgammaf', `lgammal', `lgamma', `llabs', ! `llrintf', `llrintl', `llrint', `llroundf', `llroundl', `llround', ! `log1pf', `log1pl', `log1p', `log2f', `log2l', `log2', `logbf', ! `logbl', `logb', `lrintf', `lrintl', `lrint', `lroundf', `lroundl', ! `lround', `nearbyintf', `nearbyintl', `nearbyint', `nextafterf', ! `nextafterl', `nextafter', `nexttowardf', `nexttowardl', `nexttoward', ! `remainderf', `remainderl', `remainder', `remquof', `remquol', ! `remquo', `rintf', `rintl', `rint', `roundf', `roundl', `round', ! `scalblnf', `scalblnl', `scalbln', `scalbnf', `scalbnl', `scalbn', ! `snprintf', `tgammaf', `tgammal', `tgamma', `truncf', `truncl', `trunc', ! `vfscanf', `vscanf', `vsnprintf' and `vsscanf' are handled as built-in ! functions except in strict ISO C90 mode (`-ansi' or `-std=c90'). ! There are also built-in versions of the ISO C99 functions `acosf', ! `acosl', `asinf', `asinl', `atan2f', `atan2l', `atanf', `atanl', ! `ceilf', `ceill', `cosf', `coshf', `coshl', `cosl', `expf', `expl', ! `fabsf', `fabsl', `floorf', `floorl', `fmodf', `fmodl', `frexpf', ! `frexpl', `ldexpf', `ldexpl', `log10f', `log10l', `logf', `logl', ! `modfl', `modf', `powf', `powl', `sinf', `sinhf', `sinhl', `sinl', ! `sqrtf', `sqrtl', `tanf', `tanhf', `tanhl' and `tanl' that are recognized in any mode since ISO C90 reserves these names for the purpose to which ISO C99 puts them. All these functions have ! corresponding versions prefixed with `__builtin_'. ! There are also GNU extension functions `clog10', `clog10f' and ! `clog10l' which names are reserved by ISO C99 for future use. All ! these functions have versions prefixed with `__builtin_'. ! The ISO C94 functions `iswalnum', `iswalpha', `iswcntrl', `iswdigit', ! `iswgraph', `iswlower', `iswprint', `iswpunct', `iswspace', `iswupper', ! `iswxdigit', `towlower' and `towupper' are handled as built-in functions ! except in strict ISO C90 mode (`-ansi' or `-std=c90'). ! The ISO C90 functions `abort', `abs', `acos', `asin', `atan2', `atan', ! `calloc', `ceil', `cosh', `cos', `exit', `exp', `fabs', `floor', `fmod', ! `fprintf', `fputs', `frexp', `fscanf', `isalnum', `isalpha', `iscntrl', ! `isdigit', `isgraph', `islower', `isprint', `ispunct', `isspace', ! `isupper', `isxdigit', `tolower', `toupper', `labs', `ldexp', `log10', ! `log', `malloc', `memchr', `memcmp', `memcpy', `memset', `modf', `pow', ! `printf', `putchar', `puts', `scanf', `sinh', `sin', `snprintf', ! `sprintf', `sqrt', `sscanf', `strcat', `strchr', `strcmp', `strcpy', ! `strcspn', `strlen', `strncat', `strncmp', `strncpy', `strpbrk', ! `strrchr', `strspn', `strstr', `tanh', `tan', `vfprintf', `vprintf' and ! `vsprintf' are all recognized as built-in functions unless ! `-fno-builtin' is specified (or `-fno-builtin-FUNCTION' is specified ! for an individual function). All of these functions have corresponding ! versions prefixed with `__builtin_'. GCC provides built-in versions of the ISO C99 floating-point comparison macros that avoid raising exceptions for unordered operands. They have ! the same names as the standard macros ( `isgreater', `isgreaterequal', ! `isless', `islessequal', `islessgreater', and `isunordered') , with ! `__builtin_' prefixed. We intend for a library implementor to be able ! to simply `#define' each standard macro to its built-in equivalent. In ! the same fashion, GCC provides `fpclassify', `isfinite', `isinf_sign', ! `isnormal' and `signbit' built-ins used with `__builtin_' prefixed. ! The `isinf' and `isnan' built-in functions appear both with and without ! the `__builtin_' prefix. -- Built-in Function: void *__builtin_alloca (size_t size) ! The `__builtin_alloca' function must be called at block scope. ! The function allocates an object SIZE bytes large on the stack of ! the calling function. The object is aligned on the default stack alignment boundary for the target determined by the ! `__BIGGEST_ALIGNMENT__' macro. The `__builtin_alloca' function returns a pointer to the first byte of the allocated object. The lifetime of the allocated object ends just before the calling ! function returns to its caller. This is so even when ! `__builtin_alloca' is called within a nested block. ! For example, the following function allocates eight objects of `n' bytes each on the stack, storing a pointer to each in consecutive ! elements of the array `a'. It then passes the array to function ! `g' which can safely use the storage pointed to by each of the array elements. void f (unsigned n) *************** the same fashion, GCC provides 'fpclassi *** 35704,35713 **** g (a, n); // safe } ! Since the '__builtin_alloca' function doesn't validate its argument it is the responsibility of its caller to make sure the argument doesn't cause it to exceed the stack size limit. The ! '__builtin_alloca' function is provided to make it possible to allocate on the stack arrays of bytes with an upper bound that may be computed at run time. Since C99 Variable Length Arrays offer similar functionality under a portable, more convenient, and safer --- 36122,36131 ---- g (a, n); // safe } ! Since the `__builtin_alloca' function doesn't validate its argument it is the responsibility of its caller to make sure the argument doesn't cause it to exceed the stack size limit. The ! `__builtin_alloca' function is provided to make it possible to allocate on the stack arrays of bytes with an upper bound that may be computed at run time. Since C99 Variable Length Arrays offer similar functionality under a portable, more convenient, and safer *************** the same fashion, GCC provides 'fpclassi *** 35715,35742 **** programs where GCC provides them as an extension. *Note Variable Length::, for details. -- Built-in Function: void *__builtin_alloca_with_align (size_t size, size_t alignment) ! The '__builtin_alloca_with_align' function must be called at block scope. The function allocates an object SIZE bytes large on the stack of the calling function. The allocated object is aligned on the boundary specified by the argument ALIGNMENT whose unit is given in bits (not bytes). The SIZE argument must be positive and not exceed the stack size limit. The ALIGNMENT argument must be a constant integer expression that evaluates to a power of 2 greater ! than or equal to 'CHAR_BIT' and less than some unspecified maximum. ! Invocations with other values are rejected with an error indicating ! the valid bounds. The function returns a pointer to the first byte ! of the allocated object. The lifetime of the allocated object ends ! at the end of the block in which the function was called. The ! allocated storage is released no later than just before the calling ! function returns to its caller, but may be released at the end of ! the block in which the function was called. ! For example, in the following function the call to 'g' is unsafe ! because when 'overalign' is non-zero, the space allocated by ! '__builtin_alloca_with_align' may have been released at the end of ! the 'if' statement in which it was called. void f (unsigned n, bool overalign) { --- 36133,36162 ---- programs where GCC provides them as an extension. *Note Variable Length::, for details. + -- Built-in Function: void *__builtin_alloca_with_align (size_t size, size_t alignment) ! The `__builtin_alloca_with_align' function must be called at block scope. The function allocates an object SIZE bytes large on the stack of the calling function. The allocated object is aligned on the boundary specified by the argument ALIGNMENT whose unit is given in bits (not bytes). The SIZE argument must be positive and not exceed the stack size limit. The ALIGNMENT argument must be a constant integer expression that evaluates to a power of 2 greater ! than or equal to `CHAR_BIT' and less than some unspecified ! maximum. Invocations with other values are rejected with an error ! indicating the valid bounds. The function returns a pointer to ! the first byte of the allocated object. The lifetime of the ! allocated object ends at the end of the block in which the ! function was called. The allocated storage is released no later ! than just before the calling function returns to its caller, but ! may be released at the end of the block in which the function was ! called. ! For example, in the following function the call to `g' is unsafe ! because when `overalign' is non-zero, the space allocated by ! `__builtin_alloca_with_align' may have been released at the end of ! the `if' statement in which it was called. void f (unsigned n, bool overalign) { *************** the same fashion, GCC provides 'fpclassi *** 35749,35768 **** g (p, n); // unsafe } ! Since the '__builtin_alloca_with_align' function doesn't validate its SIZE argument it is the responsibility of its caller to make sure the argument doesn't cause it to exceed the stack size limit. ! The '__builtin_alloca_with_align' function is provided to make it possible to allocate on the stack overaligned arrays of bytes with an upper bound that may be computed at run time. Since C99 Variable Length Arrays offer the same functionality under a portable, more convenient, and safer interface they are recommended ! instead, in both C99 and C++ programs where GCC provides them as an ! extension. *Note Variable Length::, for details. - -- Built-in Function: int __builtin_types_compatible_p (TYPE1, TYPE2) ! You can use the built-in function '__builtin_types_compatible_p' to determine whether two types are the same. This built-in function returns 1 if the unqualified versions of the --- 36169,36188 ---- g (p, n); // unsafe } ! Since the `__builtin_alloca_with_align' function doesn't validate its SIZE argument it is the responsibility of its caller to make sure the argument doesn't cause it to exceed the stack size limit. ! The `__builtin_alloca_with_align' function is provided to make it possible to allocate on the stack overaligned arrays of bytes with an upper bound that may be computed at run time. Since C99 Variable Length Arrays offer the same functionality under a portable, more convenient, and safer interface they are recommended ! instead, in both C99 and C++ programs where GCC provides them as ! an extension. *Note Variable Length::, for details. ! -- Built-in Function: int __builtin_types_compatible_p (TYPE1, TYPE2) ! You can use the built-in function `__builtin_types_compatible_p' to determine whether two types are the same. This built-in function returns 1 if the unqualified versions of the *************** the same fashion, GCC provides 'fpclassi *** 35770,35790 **** compatible, 0 otherwise. The result of this built-in function can be used in integer constant expressions. ! This built-in function ignores top level qualifiers (e.g., 'const', ! 'volatile'). For example, 'int' is equivalent to 'const int'. ! The type 'int[]' and 'int[5]' are compatible. On the other hand, ! 'int' and 'char *' are not compatible, even if the size of their types, on the particular architecture are the same. Also, the amount of pointer indirection is taken into account when ! determining similarity. Consequently, 'short *' is not similar to ! 'short **'. Furthermore, two types that are typedefed are considered compatible if their underlying types are compatible. ! An 'enum' type is not considered to be compatible with another ! 'enum' type even if both are compatible with the same integer type; ! this is what the C standard specifies. For example, 'enum {foo, ! bar}' is not similar to 'enum {hot, dog}'. You typically use this function in code whose execution varies depending on the arguments' types. For example: --- 36190,36210 ---- compatible, 0 otherwise. The result of this built-in function can be used in integer constant expressions. ! This built-in function ignores top level qualifiers (e.g., `const', ! `volatile'). For example, `int' is equivalent to `const int'. ! The type `int[]' and `int[5]' are compatible. On the other hand, ! `int' and `char *' are not compatible, even if the size of their types, on the particular architecture are the same. Also, the amount of pointer indirection is taken into account when ! determining similarity. Consequently, `short *' is not similar to ! `short **'. Furthermore, two types that are typedefed are considered compatible if their underlying types are compatible. ! An `enum' type is not considered to be compatible with another ! `enum' type even if both are compatible with the same integer ! type; this is what the C standard specifies. For example, `enum ! {foo, bar}' is not similar to `enum {hot, dog}'. You typically use this function in code whose execution varies depending on the arguments' types. For example: *************** the same fashion, GCC provides 'fpclassi *** 35805,35813 **** _Note:_ This construct is only available for C. -- Built-in Function: TYPE __builtin_call_with_static_chain (CALL_EXP, POINTER_EXP) - The CALL_EXP expression must be a function call, and the POINTER_EXP expression must be a pointer. The POINTER_EXP is passed to the function call in the target's static chain location. --- 36225,36233 ---- _Note:_ This construct is only available for C. + -- Built-in Function: TYPE __builtin_call_with_static_chain (CALL_EXP, POINTER_EXP) The CALL_EXP expression must be a function call, and the POINTER_EXP expression must be a pointer. The POINTER_EXP is passed to the function call in the target's static chain location. *************** the same fashion, GCC provides 'fpclassi *** 35816,35835 **** _Note:_ This builtin is only available for C. This builtin can be used to call Go closures from C. -- Built-in Function: TYPE __builtin_choose_expr (CONST_EXP, EXP1, EXP2) ! ! You can use the built-in function '__builtin_choose_expr' to evaluate code depending on the value of a constant expression. This built-in function returns EXP1 if CONST_EXP, which is an integer constant expression, is nonzero. Otherwise it returns EXP2. ! This built-in function is analogous to the '? :' operator in C, except that the expression returned has its type unaltered by ! promotion rules. Also, the built-in function does not evaluate the ! expression that is not chosen. For example, if CONST_EXP evaluates ! to true, EXP2 is not evaluated even if it has side-effects. This built-in function can return an lvalue if the chosen argument is an lvalue. --- 36236,36256 ---- _Note:_ This builtin is only available for C. This builtin can be used to call Go closures from C. + -- Built-in Function: TYPE __builtin_choose_expr (CONST_EXP, EXP1, EXP2) ! You can use the built-in function `__builtin_choose_expr' to evaluate code depending on the value of a constant expression. This built-in function returns EXP1 if CONST_EXP, which is an integer constant expression, is nonzero. Otherwise it returns EXP2. ! This built-in function is analogous to the `? :' operator in C, except that the expression returned has its type unaltered by ! promotion rules. Also, the built-in function does not evaluate ! the expression that is not chosen. For example, if CONST_EXP ! evaluates to true, EXP2 is not evaluated even if it has ! side-effects. This built-in function can return an lvalue if the chosen argument is an lvalue. *************** the same fashion, GCC provides 'fpclassi *** 35856,35885 **** CONST_EXP) may still generate syntax errors. This may change in future revisions. -- Built-in Function: TYPE __builtin_complex (REAL, IMAG) - The built-in function '__builtin_complex' is provided for use in - implementing the ISO C11 macros 'CMPLXF', 'CMPLX' and 'CMPLXL'. - REAL and IMAG must have the same type, a real binary floating-point - type, and the result has the corresponding complex type with real - and imaginary parts REAL and IMAG. Unlike 'REAL + I * IMAG', this - works even when infinities, NaNs and negative zeros are involved. -- Built-in Function: int __builtin_constant_p (EXP) ! You can use the built-in function '__builtin_constant_p' to determine if a value is known to be constant at compile time and hence that GCC can perform constant-folding on expressions ! involving that value. The argument of the function is the value to ! test. The function returns the integer 1 if the argument is known ! to be a compile-time constant and 0 if it is not known to be a ! compile-time constant. A return of 0 does not indicate that the ! value is _not_ a constant, but merely that GCC cannot prove it is a ! constant with the specified value of the '-O' option. You typically use this function in an embedded application where memory is a critical resource. If you have some complex ! calculation, you may want it to be folded if it involves constants, ! but need to call a function if it does not. For example: #define Scale_Value(X) \ (__builtin_constant_p (X) \ --- 36277,36309 ---- CONST_EXP) may still generate syntax errors. This may change in future revisions. + -- Built-in Function: TYPE __builtin_complex (REAL, IMAG) + The built-in function `__builtin_complex' is provided for use in + implementing the ISO C11 macros `CMPLXF', `CMPLX' and `CMPLXL'. + REAL and IMAG must have the same type, a real binary + floating-point type, and the result has the corresponding complex + type with real and imaginary parts REAL and IMAG. Unlike `REAL + + I * IMAG', this works even when infinities, NaNs and negative + zeros are involved. -- Built-in Function: int __builtin_constant_p (EXP) ! You can use the built-in function `__builtin_constant_p' to determine if a value is known to be constant at compile time and hence that GCC can perform constant-folding on expressions ! involving that value. The argument of the function is the value ! to test. The function returns the integer 1 if the argument is ! known to be a compile-time constant and 0 if it is not known to be ! a compile-time constant. A return of 0 does not indicate that the ! value is _not_ a constant, but merely that GCC cannot prove it is ! a constant with the specified value of the `-O' option. You typically use this function in an embedded application where memory is a critical resource. If you have some complex ! calculation, you may want it to be folded if it involves ! constants, but need to call a function if it does not. For ! example: #define Scale_Value(X) \ (__builtin_constant_p (X) \ *************** the same fashion, GCC provides 'fpclassi *** 35891,35899 **** never returns 1 when you call the inline function with a string constant or compound literal (*note Compound Literals::) and does not return 1 when you pass a constant numeric value to the inline ! function unless you specify the '-O' option. ! You may also use '__builtin_constant_p' in initializers for static data. For instance, you can write static const int table[] = { --- 36315,36323 ---- never returns 1 when you call the inline function with a string constant or compound literal (*note Compound Literals::) and does not return 1 when you pass a constant numeric value to the inline ! function unless you specify the `-O' option. ! You may also use `__builtin_constant_p' in initializers for static data. For instance, you can write static const int table[] = { *************** the same fashion, GCC provides 'fpclassi *** 35903,35922 **** This is an acceptable initializer even if EXPRESSION is not a constant expression, including the case where ! '__builtin_constant_p' returns 1 because EXPRESSION can be folded to a constant but EXPRESSION contains operands that are not ! otherwise permitted in a static initializer (for example, '0 && foo ! ()'). GCC must be more conservative about evaluating the built-in ! in this case, because it has no opportunity to perform optimization. -- Built-in Function: long __builtin_expect (long EXP, long C) ! You may use '__builtin_expect' to provide the compiler with branch prediction information. In general, you should prefer to use ! actual profile feedback for this ('-fprofile-arcs'), as programmers ! are notoriously bad at predicting how their programs actually ! perform. However, there are applications in which this data is ! hard to collect. The return value is the value of EXP, which should be an integral expression. The semantics of the built-in are that it is expected --- 36327,36346 ---- This is an acceptable initializer even if EXPRESSION is not a constant expression, including the case where ! `__builtin_constant_p' returns 1 because EXPRESSION can be folded to a constant but EXPRESSION contains operands that are not ! otherwise permitted in a static initializer (for example, `0 && ! foo ()'). GCC must be more conservative about evaluating the ! built-in in this case, because it has no opportunity to perform optimization. -- Built-in Function: long __builtin_expect (long EXP, long C) ! You may use `__builtin_expect' to provide the compiler with branch prediction information. In general, you should prefer to use ! actual profile feedback for this (`-fprofile-arcs'), as ! programmers are notoriously bad at predicting how their programs ! actually perform. However, there are applications in which this ! data is hard to collect. The return value is the value of EXP, which should be an integral expression. The semantics of the built-in are that it is expected *************** the same fashion, GCC provides 'fpclassi *** 35925,35933 **** if (__builtin_expect (x, 0)) foo (); ! indicates that we do not expect to call 'foo', since we expect 'x' ! to be zero. Since you are limited to integral expressions for EXP, ! you should use constructions such as if (__builtin_expect (ptr != NULL, 1)) foo (*ptr); --- 36349,36357 ---- if (__builtin_expect (x, 0)) foo (); ! indicates that we do not expect to call `foo', since we expect `x' ! to be zero. Since you are limited to integral expressions for ! EXP, you should use constructions such as if (__builtin_expect (ptr != NULL, 1)) foo (*ptr); *************** the same fashion, GCC provides 'fpclassi *** 35938,35957 **** This function causes the program to exit abnormally. GCC implements this function by using a target-dependent mechanism (such as intentionally executing an illegal instruction) or by ! calling 'abort'. The mechanism used may vary from release to release so you should not rely on any particular implementation. -- Built-in Function: void __builtin_unreachable (void) ! If control flow reaches the point of the '__builtin_unreachable', the program is undefined. It is useful in situations where the compiler cannot deduce the unreachability of the code. ! One such case is immediately following an 'asm' statement that either never terminates, or one that transfers control elsewhere and never returns. In this example, without the ! '__builtin_unreachable', GCC issues a warning that control reaches the end of a non-void function. It also generates code to return ! after the 'asm'. int f (int c, int v) { --- 36362,36381 ---- This function causes the program to exit abnormally. GCC implements this function by using a target-dependent mechanism (such as intentionally executing an illegal instruction) or by ! calling `abort'. The mechanism used may vary from release to release so you should not rely on any particular implementation. -- Built-in Function: void __builtin_unreachable (void) ! If control flow reaches the point of the `__builtin_unreachable', the program is undefined. It is useful in situations where the compiler cannot deduce the unreachability of the code. ! One such case is immediately following an `asm' statement that either never terminates, or one that transfers control elsewhere and never returns. In this example, without the ! `__builtin_unreachable', GCC issues a warning that control reaches the end of a non-void function. It also generates code to return ! after the `asm'. int f (int c, int v) { *************** the same fashion, GCC provides 'fpclassi *** 35966,35979 **** } } ! Because the 'asm' statement unconditionally transfers control out of the function, control never reaches the end of the function ! body. The '__builtin_unreachable' is in fact unreachable and communicates this fact to the compiler. ! Another use for '__builtin_unreachable' is following a call a function that never returns but that is not declared ! '__attribute__((noreturn))', as in this example: void function_that_never_returns (void); --- 36390,36403 ---- } } ! Because the `asm' statement unconditionally transfers control out of the function, control never reaches the end of the function ! body. The `__builtin_unreachable' is in fact unreachable and communicates this fact to the compiler. ! Another use for `__builtin_unreachable' is following a call a function that never returns but that is not declared ! `__attribute__((noreturn))', as in this example: void function_that_never_returns (void); *************** the same fashion, GCC provides 'fpclassi *** 35990,35997 **** } } ! -- Built-in Function: void * __builtin_assume_aligned (const void *EXP, ! size_t ALIGN, ...) This function returns its first argument, and allows the compiler to assume that the returned pointer is at least ALIGN bytes aligned. This built-in can have either two or three arguments, if --- 36414,36422 ---- } } ! ! -- Built-in Function: void * __builtin_assume_aligned (const void ! *EXP, size_t ALIGN, ...) This function returns its first argument, and allows the compiler to assume that the returned pointer is at least ALIGN bytes aligned. This built-in can have either two or three arguments, if *************** the same fashion, GCC provides 'fpclassi *** 36000,36026 **** void *x = __builtin_assume_aligned (arg, 16); ! means that the compiler can assume 'x', set to 'arg', is at least 16-byte aligned, while: void *x = __builtin_assume_aligned (arg, 32, 8); ! means that the compiler can assume for 'x', set to 'arg', that ! '(char *) x - 8' is 32-byte aligned. -- Built-in Function: int __builtin_LINE () ! This function is the equivalent to the preprocessor '__LINE__' macro and returns the line number of the invocation of the built-in. In a C++ default argument for a function F, it gets the line number of the call to F. -- Built-in Function: const char * __builtin_FUNCTION () ! This function is the equivalent to the preprocessor '__FUNCTION__' macro and returns the function name the invocation of the built-in is in. -- Built-in Function: const char * __builtin_FILE () ! This function is the equivalent to the preprocessor '__FILE__' macro and returns the file name the invocation of the built-in is in. In a C++ default argument for a function F, it gets the file name of the call to F. --- 36425,36451 ---- void *x = __builtin_assume_aligned (arg, 16); ! means that the compiler can assume `x', set to `arg', is at least 16-byte aligned, while: void *x = __builtin_assume_aligned (arg, 32, 8); ! means that the compiler can assume for `x', set to `arg', that ! `(char *) x - 8' is 32-byte aligned. -- Built-in Function: int __builtin_LINE () ! This function is the equivalent to the preprocessor `__LINE__' macro and returns the line number of the invocation of the built-in. In a C++ default argument for a function F, it gets the line number of the call to F. -- Built-in Function: const char * __builtin_FUNCTION () ! This function is the equivalent to the preprocessor `__FUNCTION__' macro and returns the function name the invocation of the built-in is in. -- Built-in Function: const char * __builtin_FILE () ! This function is the equivalent to the preprocessor `__FILE__' macro and returns the file name the invocation of the built-in is in. In a C++ default argument for a function F, it gets the file name of the call to F. *************** the same fashion, GCC provides 'fpclassi *** 36028,36048 **** -- Built-in Function: void __builtin___clear_cache (char *BEGIN, char *END) This function is used to flush the processor's instruction cache ! for the region of memory between BEGIN inclusive and END exclusive. ! Some targets require that the instruction cache be flushed, after ! modifying memory containing code, in order to obtain deterministic ! behavior. If the target does not require instruction cache flushes, ! '__builtin___clear_cache' has no effect. Otherwise either instructions are emitted in-line to clear the instruction cache or ! a call to the '__clear_cache' function in libgcc is made. -- Built-in Function: void __builtin_prefetch (const void *ADDR, ...) ! This function is used to minimize cache-miss latency by moving data ! into a cache before it is accessed. You can insert calls to ! '__builtin_prefetch' into code for which you know addresses of data ! in memory that is likely to be accessed soon. If the target supports them, data prefetch instructions are generated. If the prefetch is done early enough before the access then the data will be in the cache by the time it is accessed. --- 36453,36473 ---- -- Built-in Function: void __builtin___clear_cache (char *BEGIN, char *END) This function is used to flush the processor's instruction cache ! for the region of memory between BEGIN inclusive and END ! exclusive. Some targets require that the instruction cache be ! flushed, after modifying memory containing code, in order to obtain ! deterministic behavior. If the target does not require instruction cache flushes, ! `__builtin___clear_cache' has no effect. Otherwise either instructions are emitted in-line to clear the instruction cache or ! a call to the `__clear_cache' function in libgcc is made. -- Built-in Function: void __builtin_prefetch (const void *ADDR, ...) ! This function is used to minimize cache-miss latency by moving ! data into a cache before it is accessed. You can insert calls to ! `__builtin_prefetch' into code for which you know addresses of ! data in memory that is likely to be accessed soon. If the target supports them, data prefetch instructions are generated. If the prefetch is done early enough before the access then the data will be in the cache by the time it is accessed. *************** the same fashion, GCC provides 'fpclassi *** 36070,36077 **** Data prefetch does not generate faults if ADDR is invalid, but the address expression itself must be valid. For example, a prefetch ! of 'p->next' does not fault if 'p->next' is not a valid address, ! but evaluation faults if 'p' is not a valid address. If the target does not support data prefetch, the address expression is evaluated if it includes side effects but no other --- 36495,36502 ---- Data prefetch does not generate faults if ADDR is invalid, but the address expression itself must be valid. For example, a prefetch ! of `p->next' does not fault if `p->next' is not a valid address, ! but evaluation faults if `p' is not a valid address. If the target does not support data prefetch, the address expression is evaluated if it includes side effects but no other *************** the same fashion, GCC provides 'fpclassi *** 36079,36092 **** -- Built-in Function: double __builtin_huge_val (void) Returns a positive infinity, if supported by the floating-point ! format, else 'DBL_MAX'. This function is suitable for implementing ! the ISO C macro 'HUGE_VAL'. -- Built-in Function: float __builtin_huge_valf (void) ! Similar to '__builtin_huge_val', except the return type is 'float'. -- Built-in Function: long double __builtin_huge_vall (void) ! Similar to '__builtin_huge_val', except the return type is 'long double'. -- Built-in Function: int __builtin_fpclassify (int, int, int, int, --- 36504,36517 ---- -- Built-in Function: double __builtin_huge_val (void) Returns a positive infinity, if supported by the floating-point ! format, else `DBL_MAX'. This function is suitable for ! implementing the ISO C macro `HUGE_VAL'. -- Built-in Function: float __builtin_huge_valf (void) ! Similar to `__builtin_huge_val', except the return type is `float'. -- Built-in Function: long double __builtin_huge_vall (void) ! Similar to `__builtin_huge_val', except the return type is `long double'. -- Built-in Function: int __builtin_fpclassify (int, int, int, int, *************** the same fashion, GCC provides 'fpclassi *** 36094,36178 **** This built-in implements the C99 fpclassify functionality. The first five int arguments should be the target library's notion of the possible FP classes and are used for return values. They must ! be constant values and they must appear in this order: 'FP_NAN', ! 'FP_INFINITE', 'FP_NORMAL', 'FP_SUBNORMAL' and 'FP_ZERO'. The ellipsis is for exactly one floating-point value to classify. GCC treats the last argument as type-generic, which means it does not do default promotion from float to double. -- Built-in Function: double __builtin_inf (void) ! Similar to '__builtin_huge_val', except a warning is generated if the target floating-point format does not support infinities. -- Built-in Function: _Decimal32 __builtin_infd32 (void) ! Similar to '__builtin_inf', except the return type is '_Decimal32'. -- Built-in Function: _Decimal64 __builtin_infd64 (void) ! Similar to '__builtin_inf', except the return type is '_Decimal64'. -- Built-in Function: _Decimal128 __builtin_infd128 (void) ! Similar to '__builtin_inf', except the return type is ! '_Decimal128'. -- Built-in Function: float __builtin_inff (void) ! Similar to '__builtin_inf', except the return type is 'float'. This function is suitable for implementing the ISO C99 macro ! 'INFINITY'. -- Built-in Function: long double __builtin_infl (void) ! Similar to '__builtin_inf', except the return type is 'long double'. -- Built-in Function: int __builtin_isinf_sign (...) ! Similar to 'isinf', except the return value is -1 for an argument ! of '-Inf' and 1 for an argument of '+Inf'. Note while the parameter list is an ellipsis, this function only accepts exactly one floating-point argument. GCC treats this parameter as type-generic, which means it does not do default promotion from float to double. -- Built-in Function: double __builtin_nan (const char *str) ! This is an implementation of the ISO C99 function 'nan'. ! Since ISO C99 defines this function in terms of 'strtod', which we do not implement, a description of the parsing is in order. The ! string is parsed as by 'strtol'; that is, the base is recognized by ! leading '0' or '0x' prefixes. The number parsed is placed in the ! significand such that the least significant bit of the number is at ! the least significant bit of the significand. The number is truncated to fit the significand field provided. The significand is forced to be a quiet NaN. This function, if given a string literal all of which would have ! been consumed by 'strtol', is evaluated early enough that it is considered a compile-time constant. -- Built-in Function: _Decimal32 __builtin_nand32 (const char *str) ! Similar to '__builtin_nan', except the return type is '_Decimal32'. -- Built-in Function: _Decimal64 __builtin_nand64 (const char *str) ! Similar to '__builtin_nan', except the return type is '_Decimal64'. -- Built-in Function: _Decimal128 __builtin_nand128 (const char *str) ! Similar to '__builtin_nan', except the return type is ! '_Decimal128'. -- Built-in Function: float __builtin_nanf (const char *str) ! Similar to '__builtin_nan', except the return type is 'float'. -- Built-in Function: long double __builtin_nanl (const char *str) ! Similar to '__builtin_nan', except the return type is 'long double'. -- Built-in Function: double __builtin_nans (const char *str) ! Similar to '__builtin_nan', except the significand is forced to be ! a signaling NaN. The 'nans' function is proposed by WG14 N965. -- Built-in Function: float __builtin_nansf (const char *str) ! Similar to '__builtin_nans', except the return type is 'float'. -- Built-in Function: long double __builtin_nansl (const char *str) ! Similar to '__builtin_nans', except the return type is 'long double'. -- Built-in Function: int __builtin_ffs (int x) --- 36519,36603 ---- This built-in implements the C99 fpclassify functionality. The first five int arguments should be the target library's notion of the possible FP classes and are used for return values. They must ! be constant values and they must appear in this order: `FP_NAN', ! `FP_INFINITE', `FP_NORMAL', `FP_SUBNORMAL' and `FP_ZERO'. The ellipsis is for exactly one floating-point value to classify. GCC treats the last argument as type-generic, which means it does not do default promotion from float to double. -- Built-in Function: double __builtin_inf (void) ! Similar to `__builtin_huge_val', except a warning is generated if the target floating-point format does not support infinities. -- Built-in Function: _Decimal32 __builtin_infd32 (void) ! Similar to `__builtin_inf', except the return type is `_Decimal32'. -- Built-in Function: _Decimal64 __builtin_infd64 (void) ! Similar to `__builtin_inf', except the return type is `_Decimal64'. -- Built-in Function: _Decimal128 __builtin_infd128 (void) ! Similar to `__builtin_inf', except the return type is ! `_Decimal128'. -- Built-in Function: float __builtin_inff (void) ! Similar to `__builtin_inf', except the return type is `float'. This function is suitable for implementing the ISO C99 macro ! `INFINITY'. -- Built-in Function: long double __builtin_infl (void) ! Similar to `__builtin_inf', except the return type is `long double'. -- Built-in Function: int __builtin_isinf_sign (...) ! Similar to `isinf', except the return value is -1 for an argument ! of `-Inf' and 1 for an argument of `+Inf'. Note while the parameter list is an ellipsis, this function only accepts exactly one floating-point argument. GCC treats this parameter as type-generic, which means it does not do default promotion from float to double. -- Built-in Function: double __builtin_nan (const char *str) ! This is an implementation of the ISO C99 function `nan'. ! Since ISO C99 defines this function in terms of `strtod', which we do not implement, a description of the parsing is in order. The ! string is parsed as by `strtol'; that is, the base is recognized by ! leading `0' or `0x' prefixes. The number parsed is placed in the ! significand such that the least significant bit of the number is ! at the least significant bit of the significand. The number is truncated to fit the significand field provided. The significand is forced to be a quiet NaN. This function, if given a string literal all of which would have ! been consumed by `strtol', is evaluated early enough that it is considered a compile-time constant. -- Built-in Function: _Decimal32 __builtin_nand32 (const char *str) ! Similar to `__builtin_nan', except the return type is `_Decimal32'. -- Built-in Function: _Decimal64 __builtin_nand64 (const char *str) ! Similar to `__builtin_nan', except the return type is `_Decimal64'. -- Built-in Function: _Decimal128 __builtin_nand128 (const char *str) ! Similar to `__builtin_nan', except the return type is ! `_Decimal128'. -- Built-in Function: float __builtin_nanf (const char *str) ! Similar to `__builtin_nan', except the return type is `float'. -- Built-in Function: long double __builtin_nanl (const char *str) ! Similar to `__builtin_nan', except the return type is `long double'. -- Built-in Function: double __builtin_nans (const char *str) ! Similar to `__builtin_nan', except the significand is forced to be ! a signaling NaN. The `nans' function is proposed by WG14 N965. -- Built-in Function: float __builtin_nansf (const char *str) ! Similar to `__builtin_nans', except the return type is `float'. -- Built-in Function: long double __builtin_nansl (const char *str) ! Similar to `__builtin_nans', except the return type is `long double'. -- Built-in Function: int __builtin_ffs (int x) *************** the same fashion, GCC provides 'fpclassi *** 36199,36272 **** Returns the parity of X, i.e. the number of 1-bits in X modulo 2. -- Built-in Function: int __builtin_ffsl (long) ! Similar to '__builtin_ffs', except the argument type is 'long'. -- Built-in Function: int __builtin_clzl (unsigned long) ! Similar to '__builtin_clz', except the argument type is 'unsigned long'. -- Built-in Function: int __builtin_ctzl (unsigned long) ! Similar to '__builtin_ctz', except the argument type is 'unsigned long'. -- Built-in Function: int __builtin_clrsbl (long) ! Similar to '__builtin_clrsb', except the argument type is 'long'. -- Built-in Function: int __builtin_popcountl (unsigned long) ! Similar to '__builtin_popcount', except the argument type is ! 'unsigned long'. -- Built-in Function: int __builtin_parityl (unsigned long) ! Similar to '__builtin_parity', except the argument type is ! 'unsigned long'. -- Built-in Function: int __builtin_ffsll (long long) ! Similar to '__builtin_ffs', except the argument type is 'long long'. -- Built-in Function: int __builtin_clzll (unsigned long long) ! Similar to '__builtin_clz', except the argument type is 'unsigned long long'. -- Built-in Function: int __builtin_ctzll (unsigned long long) ! Similar to '__builtin_ctz', except the argument type is 'unsigned long long'. -- Built-in Function: int __builtin_clrsbll (long long) ! Similar to '__builtin_clrsb', except the argument type is 'long long'. -- Built-in Function: int __builtin_popcountll (unsigned long long) ! Similar to '__builtin_popcount', except the argument type is ! 'unsigned long long'. -- Built-in Function: int __builtin_parityll (unsigned long long) ! Similar to '__builtin_parity', except the argument type is ! 'unsigned long long'. -- Built-in Function: double __builtin_powi (double, int) Returns the first argument raised to the power of the second. ! Unlike the 'pow' function no guarantees about precision and rounding are made. -- Built-in Function: float __builtin_powif (float, int) ! Similar to '__builtin_powi', except the argument and return types ! are 'float'. -- Built-in Function: long double __builtin_powil (long double, int) ! Similar to '__builtin_powi', except the argument and return types ! are 'long double'. -- Built-in Function: uint16_t __builtin_bswap16 (uint16_t x) Returns X with the order of the bytes reversed; for example, ! '0xaabb' becomes '0xbbaa'. Byte here always means exactly 8 bits. -- Built-in Function: uint32_t __builtin_bswap32 (uint32_t x) ! Similar to '__builtin_bswap16', except the argument and return types are 32 bit. -- Built-in Function: uint64_t __builtin_bswap64 (uint64_t x) ! Similar to '__builtin_bswap32', except the argument and return types are 64 bit.  --- 36624,36697 ---- Returns the parity of X, i.e. the number of 1-bits in X modulo 2. -- Built-in Function: int __builtin_ffsl (long) ! Similar to `__builtin_ffs', except the argument type is `long'. -- Built-in Function: int __builtin_clzl (unsigned long) ! Similar to `__builtin_clz', except the argument type is `unsigned long'. -- Built-in Function: int __builtin_ctzl (unsigned long) ! Similar to `__builtin_ctz', except the argument type is `unsigned long'. -- Built-in Function: int __builtin_clrsbl (long) ! Similar to `__builtin_clrsb', except the argument type is `long'. -- Built-in Function: int __builtin_popcountl (unsigned long) ! Similar to `__builtin_popcount', except the argument type is ! `unsigned long'. -- Built-in Function: int __builtin_parityl (unsigned long) ! Similar to `__builtin_parity', except the argument type is ! `unsigned long'. -- Built-in Function: int __builtin_ffsll (long long) ! Similar to `__builtin_ffs', except the argument type is `long long'. -- Built-in Function: int __builtin_clzll (unsigned long long) ! Similar to `__builtin_clz', except the argument type is `unsigned long long'. -- Built-in Function: int __builtin_ctzll (unsigned long long) ! Similar to `__builtin_ctz', except the argument type is `unsigned long long'. -- Built-in Function: int __builtin_clrsbll (long long) ! Similar to `__builtin_clrsb', except the argument type is `long long'. -- Built-in Function: int __builtin_popcountll (unsigned long long) ! Similar to `__builtin_popcount', except the argument type is ! `unsigned long long'. -- Built-in Function: int __builtin_parityll (unsigned long long) ! Similar to `__builtin_parity', except the argument type is ! `unsigned long long'. -- Built-in Function: double __builtin_powi (double, int) Returns the first argument raised to the power of the second. ! Unlike the `pow' function no guarantees about precision and rounding are made. -- Built-in Function: float __builtin_powif (float, int) ! Similar to `__builtin_powi', except the argument and return types ! are `float'. -- Built-in Function: long double __builtin_powil (long double, int) ! Similar to `__builtin_powi', except the argument and return types ! are `long double'. -- Built-in Function: uint16_t __builtin_bswap16 (uint16_t x) Returns X with the order of the bytes reversed; for example, ! `0xaabb' becomes `0xbbaa'. Byte here always means exactly 8 bits. -- Built-in Function: uint32_t __builtin_bswap32 (uint32_t x) ! Similar to `__builtin_bswap16', except the argument and return types are 32 bit. -- Built-in Function: uint64_t __builtin_bswap64 (uint64_t x) ! Similar to `__builtin_bswap32', except the argument and return types are 64 bit.  *************** generate the machine instruction that is *** 36367,36375 **** long __builtin_alpha_zap (long, long) long __builtin_alpha_zapnot (long, long) ! The following built-in functions are always with '-mmax' or '-mcpu=CPU' ! where CPU is 'pca56' or later. They all generate the machine ! instruction that is part of the name. long __builtin_alpha_pklb (long) long __builtin_alpha_pkwb (long) --- 36792,36800 ---- long __builtin_alpha_zap (long, long) long __builtin_alpha_zapnot (long, long) ! The following built-in functions are always with `-mmax' or ! `-mcpu=CPU' where CPU is `pca56' or later. They all generate the ! machine instruction that is part of the name. long __builtin_alpha_pklb (long) long __builtin_alpha_pkwb (long) *************** instruction that is part of the name. *** 36385,36402 **** long __builtin_alpha_maxsw4 (long, long) long __builtin_alpha_perr (long, long) ! The following built-in functions are always with '-mcix' or '-mcpu=CPU' ! where CPU is 'ev67' or later. They all generate the machine instruction ! that is part of the name. long __builtin_alpha_cttz (long) long __builtin_alpha_ctlz (long) long __builtin_alpha_ctpop (long) The following built-in functions are available on systems that use the ! OSF/1 PALcode. Normally they invoke the 'rduniq' and 'wruniq' PAL ! calls, but when invoked with '-mtls-kernel', they invoke 'rdval' and ! 'wrval'. void *__builtin_thread_pointer (void) void __builtin_set_thread_pointer (void *) --- 36810,36827 ---- long __builtin_alpha_maxsw4 (long, long) long __builtin_alpha_perr (long, long) ! The following built-in functions are always with `-mcix' or ! `-mcpu=CPU' where CPU is `ev67' or later. They all generate the ! machine instruction that is part of the name. long __builtin_alpha_cttz (long) long __builtin_alpha_ctlz (long) long __builtin_alpha_ctpop (long) The following built-in functions are available on systems that use the ! OSF/1 PALcode. Normally they invoke the `rduniq' and `wruniq' PAL ! calls, but when invoked with `-mtls-kernel', they invoke `rdval' and ! `wrval'. void *__builtin_thread_pointer (void) void __builtin_set_thread_pointer (void *) *************** generate the machine instruction that is *** 36435,36459 **** int __builtin_stsex (volatile void *, int) The following built-in functions are always available. They all ! generate a Nios II Custom Instruction. The name of the function ! represents the types that the function takes and returns. The letter ! before the 'n' is the return type or void if absent. The 'n' represents the first parameter to all the custom instructions, the custom ! instruction number. The two letters after the 'n' represent the up to two parameters to the function. The letters represent the following data types: ! '' ! 'void' for return type and no parameter for parameter types. ! 'i' ! 'int' for return type and parameter type ! 'f' ! 'float' for return type and parameter type - 'p' - 'void *' for return type and parameter type And the function names are: void __builtin_custom_n (void) --- 36860,36885 ---- int __builtin_stsex (volatile void *, int) The following built-in functions are always available. They all ! generate a Nios II Custom Instruction. The name of the function ! represents the types that the function takes and returns. The letter ! before the `n' is the return type or void if absent. The `n' represents the first parameter to all the custom instructions, the custom ! instruction number. The two letters after the `n' represent the up to two parameters to the function. The letters represent the following data types: ! `' ! `void' for return type and no parameter for parameter types. ! `i' ! `int' for return type and parameter type ! `f' ! `float' for return type and parameter type ! ! `p' ! `void *' for return type and parameter type And the function names are: void __builtin_custom_n (void) *************** generated to ensure this is true, but fo *** 36523,36529 **** in each case. _Note:_ Using a built-in to generate an instruction not supported by a ! target may cause problems. At present the compiler is not guaranteed to detect such misuse, and as a result an internal compiler error may be generated. --- 36949,36955 ---- in each case. _Note:_ Using a built-in to generate an instruction not supported by a ! target may cause problems. At present the compiler is not guaranteed to detect such misuse, and as a result an internal compiler error may be generated. *************** generated. *** 36556,36562 **** mov rREGNO, VAL -- Built-in Function: int __builtin_arc_divaw (int A, int B) ! Only available if either '-mcpu=ARC700' or '-meA' is set. Generates: divaw DEST, A, B where the value in DEST will be the result returned from the --- 36982,36988 ---- mov rREGNO, VAL -- Built-in Function: int __builtin_arc_divaw (int A, int B) ! Only available if either `-mcpu=ARC700' or `-meA' is set. Generates: divaw DEST, A, B where the value in DEST will be the result returned from the *************** generated. *** 36567,36585 **** flag A -- Built-in Function: unsigned int __builtin_arc_lr (unsigned int AUXR) ! The operand, AUXV, is the address of an auxiliary register and must ! be a compile time constant. Generates: lr DEST, [AUXR] Where the value in DEST will be the result returned from the built-in. -- Built-in Function: void __builtin_arc_mul64 (int A, int B) ! Only available with '-mmul64'. Generates: mul64 A, B -- Built-in Function: void __builtin_arc_mulu64 (unsigned int A, unsigned int B) ! Only available with '-mmul64'. Generates: mulu64 A, B -- Built-in Function: void __builtin_arc_nop (void) --- 36993,37011 ---- flag A -- Built-in Function: unsigned int __builtin_arc_lr (unsigned int AUXR) ! The operand, AUXV, is the address of an auxiliary register and ! must be a compile time constant. Generates: lr DEST, [AUXR] Where the value in DEST will be the result returned from the built-in. -- Built-in Function: void __builtin_arc_mul64 (int A, int B) ! Only available with `-mmul64'. Generates: mul64 A, B -- Built-in Function: void __builtin_arc_mulu64 (unsigned int A, unsigned int B) ! Only available with `-mmul64'. Generates: mulu64 A, B -- Built-in Function: void __builtin_arc_nop (void) *************** generated. *** 36587,36601 **** nop -- Built-in Function: int __builtin_arc_norm (int SRC) ! Only valid if the 'norm' instruction is available through the ! '-mnorm' option or by default with '-mcpu=ARC700'. Generates: norm DEST, SRC Where the value in DEST will be the result returned from the built-in. -- Built-in Function: short int __builtin_arc_normw (short int SRC) ! Only valid if the 'normw' instruction is available through the ! '-mnorm' option or by default with '-mcpu=ARC700'. Generates: normw DEST, SRC Where the value in DEST will be the result returned from the built-in. --- 37013,37027 ---- nop -- Built-in Function: int __builtin_arc_norm (int SRC) ! Only valid if the `norm' instruction is available through the ! `-mnorm' option or by default with `-mcpu=ARC700'. Generates: norm DEST, SRC Where the value in DEST will be the result returned from the built-in. -- Built-in Function: short int __builtin_arc_normw (short int SRC) ! Only valid if the `normw' instruction is available through the ! `-mnorm' option or by default with `-mcpu=ARC700'. Generates: normw DEST, SRC Where the value in DEST will be the result returned from the built-in. *************** generated. *** 36616,36622 **** sr AUXR, [VAL] -- Built-in Function: int __builtin_arc_swap (int SRC) ! Only valid with '-mswap'. Generates: swap DEST, SRC Where the value in DEST will be the result returned from the built-in. --- 37042,37048 ---- sr AUXR, [VAL] -- Built-in Function: int __builtin_arc_swap (int SRC) ! Only valid with `-mswap'. Generates: swap DEST, SRC Where the value in DEST will be the result returned from the built-in. *************** generated. *** 36626,36646 **** swi -- Built-in Function: void __builtin_arc_sync (void) ! Only available with '-mcpu=ARC700'. Generates: sync -- Built-in Function: void __builtin_arc_trap_s (unsigned int C) ! Only available with '-mcpu=ARC700'. Generates: trap_s C -- Built-in Function: void __builtin_arc_unimp_s (void) ! Only available with '-mcpu=ARC700'. Generates: unimp_s ! The instructions generated by the following builtins are not considered ! as candidates for scheduling. They are not moved around by the compiler ! during scheduling, and thus can be expected to appear where they are put ! in the C code: __builtin_arc_brk() __builtin_arc_core_read() __builtin_arc_core_write() --- 37052,37072 ---- swi -- Built-in Function: void __builtin_arc_sync (void) ! Only available with `-mcpu=ARC700'. Generates: sync -- Built-in Function: void __builtin_arc_trap_s (unsigned int C) ! Only available with `-mcpu=ARC700'. Generates: trap_s C -- Built-in Function: void __builtin_arc_unimp_s (void) ! Only available with `-mcpu=ARC700'. Generates: unimp_s ! The instructions generated by the following builtins are not ! considered as candidates for scheduling. They are not moved around by ! the compiler during scheduling, and thus can be expected to appear ! where they are put in the C code: __builtin_arc_brk() __builtin_arc_core_read() __builtin_arc_core_write() *************** File: gcc.info, Node: ARC SIMD Built-in *** 36658,36685 **** SIMD builtins provided by the compiler can be used to generate the vector instructions. This section describes the available builtins and ! their usage in programs. With the '-msimd' option, the compiler provides 128-bit vector types, which can be specified using the ! 'vector_size' attribute. The header file 'arc-simd.h' can be included to use the following predefined types: typedef int __v4si __attribute__((vector_size(16))); typedef short __v8hi __attribute__((vector_size(16))); These types can be used to define 128-bit variables. The built-in ! functions listed in the following section can be used on these variables ! to generate the vector operations. ! For all builtins, '__builtin_arc_SOMEINSN', the header file ! 'arc-simd.h' also provides equivalent macros called '_SOMEINSN' that can ! be used for programming ease and improved readability. The following ! macros for DMA control are also provided: #define _setup_dma_in_channel_reg _vdiwr #define _setup_dma_out_channel_reg _vdowr ! The following is a complete list of all the SIMD built-ins provided for ! ARC, grouped by calling signature. ! The following take two '__v8hi' arguments and return a '__v8hi' result: __v8hi __builtin_arc_vaddaw (__v8hi, __v8hi) __v8hi __builtin_arc_vaddw (__v8hi, __v8hi) __v8hi __builtin_arc_vand (__v8hi, __v8hi) --- 37084,37111 ---- SIMD builtins provided by the compiler can be used to generate the vector instructions. This section describes the available builtins and ! their usage in programs. With the `-msimd' option, the compiler provides 128-bit vector types, which can be specified using the ! `vector_size' attribute. The header file `arc-simd.h' can be included to use the following predefined types: typedef int __v4si __attribute__((vector_size(16))); typedef short __v8hi __attribute__((vector_size(16))); These types can be used to define 128-bit variables. The built-in ! functions listed in the following section can be used on these ! variables to generate the vector operations. ! For all builtins, `__builtin_arc_SOMEINSN', the header file ! `arc-simd.h' also provides equivalent macros called `_SOMEINSN' that ! can be used for programming ease and improved readability. The ! following macros for DMA control are also provided: #define _setup_dma_in_channel_reg _vdiwr #define _setup_dma_out_channel_reg _vdowr ! The following is a complete list of all the SIMD built-ins provided ! for ARC, grouped by calling signature. ! The following take two `__v8hi' arguments and return a `__v8hi' result: __v8hi __builtin_arc_vaddaw (__v8hi, __v8hi) __v8hi __builtin_arc_vaddw (__v8hi, __v8hi) __v8hi __builtin_arc_vand (__v8hi, __v8hi) *************** ARC, grouped by calling signature. *** 36729,36736 **** __v8hi __builtin_arc_vxor (__v8hi, __v8hi) __v8hi __builtin_arc_vxoraw (__v8hi, __v8hi) ! The following take one '__v8hi' and one 'int' argument and return a ! '__v8hi' result: __v8hi __builtin_arc_vbaddw (__v8hi, int) __v8hi __builtin_arc_vbmaxw (__v8hi, int) --- 37155,37162 ---- __v8hi __builtin_arc_vxor (__v8hi, __v8hi) __v8hi __builtin_arc_vxoraw (__v8hi, __v8hi) ! The following take one `__v8hi' and one `int' argument and return a ! `__v8hi' result: __v8hi __builtin_arc_vbaddw (__v8hi, int) __v8hi __builtin_arc_vbmaxw (__v8hi, int) *************** ARC, grouped by calling signature. *** 36741,36755 **** __v8hi __builtin_arc_vbrsubw (__v8hi, int) __v8hi __builtin_arc_vbsubw (__v8hi, int) ! The following take one '__v8hi' argument and one 'int' argument which must be a 3-bit compile time constant indicating a register number ! I0-I7. They return a '__v8hi' result. __v8hi __builtin_arc_vasrw (__v8hi, const int) __v8hi __builtin_arc_vsr8 (__v8hi, const int) __v8hi __builtin_arc_vsr8aw (__v8hi, const int) ! The following take one '__v8hi' argument and one 'int' argument which ! must be a 6-bit compile time constant. They return a '__v8hi' result. __v8hi __builtin_arc_vasrpwbi (__v8hi, const int) __v8hi __builtin_arc_vasrrpwbi (__v8hi, const int) __v8hi __builtin_arc_vasrrwi (__v8hi, const int) --- 37167,37181 ---- __v8hi __builtin_arc_vbrsubw (__v8hi, int) __v8hi __builtin_arc_vbsubw (__v8hi, int) ! The following take one `__v8hi' argument and one `int' argument which must be a 3-bit compile time constant indicating a register number ! I0-I7. They return a `__v8hi' result. __v8hi __builtin_arc_vasrw (__v8hi, const int) __v8hi __builtin_arc_vsr8 (__v8hi, const int) __v8hi __builtin_arc_vsr8aw (__v8hi, const int) ! The following take one `__v8hi' argument and one `int' argument which ! must be a 6-bit compile time constant. They return a `__v8hi' result. __v8hi __builtin_arc_vasrpwbi (__v8hi, const int) __v8hi __builtin_arc_vasrrpwbi (__v8hi, const int) __v8hi __builtin_arc_vasrrwi (__v8hi, const int) *************** must be a 6-bit compile time constant. *** 36758,36777 **** __v8hi __builtin_arc_vsr8awi (__v8hi, const int) __v8hi __builtin_arc_vsr8i (__v8hi, const int) ! The following take one '__v8hi' argument and one 'int' argument which ! must be a 8-bit compile time constant. They return a '__v8hi' result. __v8hi __builtin_arc_vd6tapf (__v8hi, const int) __v8hi __builtin_arc_vmvaw (__v8hi, const int) __v8hi __builtin_arc_vmvw (__v8hi, const int) __v8hi __builtin_arc_vmvzw (__v8hi, const int) ! The following take two 'int' arguments, the second of which which must ! be a 8-bit compile time constant. They return a '__v8hi' result: __v8hi __builtin_arc_vmovaw (int, const int) __v8hi __builtin_arc_vmovw (int, const int) __v8hi __builtin_arc_vmovzw (int, const int) ! The following take a single '__v8hi' argument and return a '__v8hi' result: __v8hi __builtin_arc_vabsaw (__v8hi) __v8hi __builtin_arc_vabsw (__v8hi) --- 37184,37203 ---- __v8hi __builtin_arc_vsr8awi (__v8hi, const int) __v8hi __builtin_arc_vsr8i (__v8hi, const int) ! The following take one `__v8hi' argument and one `int' argument which ! must be a 8-bit compile time constant. They return a `__v8hi' result. __v8hi __builtin_arc_vd6tapf (__v8hi, const int) __v8hi __builtin_arc_vmvaw (__v8hi, const int) __v8hi __builtin_arc_vmvw (__v8hi, const int) __v8hi __builtin_arc_vmvzw (__v8hi, const int) ! The following take two `int' arguments, the second of which which must ! be a 8-bit compile time constant. They return a `__v8hi' result: __v8hi __builtin_arc_vmovaw (int, const int) __v8hi __builtin_arc_vmovw (int, const int) __v8hi __builtin_arc_vmovzw (int, const int) ! The following take a single `__v8hi' argument and return a `__v8hi' result: __v8hi __builtin_arc_vabsaw (__v8hi) __v8hi __builtin_arc_vabsw (__v8hi) *************** result: *** 36785,36822 **** __v8hi __builtin_arc_vupsbaw (__v8hi) __v8hi __builtin_arc_vupsbw (__v8hi) ! The following take two 'int' arguments and return no result: void __builtin_arc_vdirun (int, int) void __builtin_arc_vdorun (int, int) ! The following take two 'int' arguments and return no result. The first ! argument must a 3-bit compile time constant indicating one of the DR0-DR7 DMA setup channels: void __builtin_arc_vdiwr (const int, int) void __builtin_arc_vdowr (const int, int) ! The following take an 'int' argument and return no result: void __builtin_arc_vendrec (int) void __builtin_arc_vrec (int) void __builtin_arc_vrecrun (int) void __builtin_arc_vrun (int) ! The following take a '__v8hi' argument and two 'int' arguments and ! return a '__v8hi' result. The second argument must be a 3-bit compile time constants, indicating one the registers I0-I7, and the third argument must be an 8-bit compile time constant. _Note:_ Although the equivalent hardware instructions do not take an SIMD register as an operand, these builtins overwrite the relevant bits ! of the '__v8hi' register provided as the first argument with the value ! loaded from the '[Ib, u8]' location in the SDM. __v8hi __builtin_arc_vld32 (__v8hi, const int, const int) __v8hi __builtin_arc_vld32wh (__v8hi, const int, const int) __v8hi __builtin_arc_vld32wl (__v8hi, const int, const int) __v8hi __builtin_arc_vld64 (__v8hi, const int, const int) ! The following take two 'int' arguments and return a '__v8hi' result. The first argument must be a 3-bit compile time constants, indicating one the registers I0-I7, and the second argument must be an 8-bit compile time constant. --- 37211,37248 ---- __v8hi __builtin_arc_vupsbaw (__v8hi) __v8hi __builtin_arc_vupsbw (__v8hi) ! The following take two `int' arguments and return no result: void __builtin_arc_vdirun (int, int) void __builtin_arc_vdorun (int, int) ! The following take two `int' arguments and return no result. The ! first argument must a 3-bit compile time constant indicating one of the DR0-DR7 DMA setup channels: void __builtin_arc_vdiwr (const int, int) void __builtin_arc_vdowr (const int, int) ! The following take an `int' argument and return no result: void __builtin_arc_vendrec (int) void __builtin_arc_vrec (int) void __builtin_arc_vrecrun (int) void __builtin_arc_vrun (int) ! The following take a `__v8hi' argument and two `int' arguments and ! return a `__v8hi' result. The second argument must be a 3-bit compile time constants, indicating one the registers I0-I7, and the third argument must be an 8-bit compile time constant. _Note:_ Although the equivalent hardware instructions do not take an SIMD register as an operand, these builtins overwrite the relevant bits ! of the `__v8hi' register provided as the first argument with the value ! loaded from the `[Ib, u8]' location in the SDM. __v8hi __builtin_arc_vld32 (__v8hi, const int, const int) __v8hi __builtin_arc_vld32wh (__v8hi, const int, const int) __v8hi __builtin_arc_vld32wl (__v8hi, const int, const int) __v8hi __builtin_arc_vld64 (__v8hi, const int, const int) ! The following take two `int' arguments and return a `__v8hi' result. The first argument must be a 3-bit compile time constants, indicating one the registers I0-I7, and the second argument must be an 8-bit compile time constant. *************** compile time constant. *** 36824,36830 **** __v8hi __builtin_arc_vld128 (const int, const int) __v8hi __builtin_arc_vld64w (const int, const int) ! The following take a '__v8hi' argument and two 'int' arguments and return no result. The second argument must be a 3-bit compile time constants, indicating one the registers I0-I7, and the third argument must be an 8-bit compile time constant. --- 37250,37256 ---- __v8hi __builtin_arc_vld128 (const int, const int) __v8hi __builtin_arc_vld64w (const int, const int) ! The following take a `__v8hi' argument and two `int' arguments and return no result. The second argument must be a 3-bit compile time constants, indicating one the registers I0-I7, and the third argument must be an 8-bit compile time constant. *************** must be an 8-bit compile time constant. *** 36832,36838 **** void __builtin_arc_vst128 (__v8hi, const int, const int) void __builtin_arc_vst64 (__v8hi, const int, const int) ! The following take a '__v8hi' argument and three 'int' arguments and return no result. The second argument must be a 3-bit compile-time constant, identifying the 16-bit sub-register to be stored, the third argument must be a 3-bit compile time constants, indicating one the --- 37258,37264 ---- void __builtin_arc_vst128 (__v8hi, const int, const int) void __builtin_arc_vst64 (__v8hi, const int, const int) ! The following take a `__v8hi' argument and three `int' arguments and return no result. The second argument must be a 3-bit compile-time constant, identifying the 16-bit sub-register to be stored, the third argument must be a 3-bit compile time constants, indicating one the *************** File: gcc.info, Node: ARM iWMMXt Built- *** 36849,36855 **** ------------------------------------ These built-in functions are available for the ARM family of processors ! when the '-mcpu=iwmmxt' switch is used: typedef int v2si __attribute__ ((vector_size (8))); typedef short v4hi __attribute__ ((vector_size (8))); --- 37275,37281 ---- ------------------------------------ These built-in functions are available for the ARM family of processors ! when the `-mcpu=iwmmxt' switch is used: typedef int v2si __attribute__ ((vector_size (8))); typedef short v4hi __attribute__ ((vector_size (8))); *************** File: gcc.info, Node: ARM C Language Ex *** 37004,37023 **** GCC implements extensions for C as described in the ARM C Language Extensions (ACLE) specification, which can be found at ! . As a part of ACLE, GCC implements extensions for Advanced SIMD as described in the ARM C Language Extensions Specification. The complete list of Advanced SIMD intrinsics can be found at ! . The built-in intrinsics for the Advanced SIMD extension are available when NEON is enabled. Currently, ARM and AArch64 back ends do not support ACLE 2.0 fully. ! Both back ends support CRC32 intrinsics from 'arm_acle.h'. The ARM back ! end's 16-bit floating-point Advanced SIMD intrinsics currently comply to ! ACLE v1.1. AArch64's back end does not have support for 16-bit floating ! point Advanced SIMD intrinsics yet. See *note ARM Options:: and *note AArch64 Options:: for more information on the availability of extensions. --- 37430,37449 ---- GCC implements extensions for C as described in the ARM C Language Extensions (ACLE) specification, which can be found at ! `http://infocenter.arm.com/help/topic/com.arm.doc.ihi0053c/IHI0053C_acle_2_0.pdf'. As a part of ACLE, GCC implements extensions for Advanced SIMD as described in the ARM C Language Extensions Specification. The complete list of Advanced SIMD intrinsics can be found at ! `http://infocenter.arm.com/help/topic/com.arm.doc.ihi0073a/IHI0073A_arm_neon_intrinsics_ref.pdf'. The built-in intrinsics for the Advanced SIMD extension are available when NEON is enabled. Currently, ARM and AArch64 back ends do not support ACLE 2.0 fully. ! Both back ends support CRC32 intrinsics from `arm_acle.h'. The ARM ! back end's 16-bit floating-point Advanced SIMD intrinsics currently ! comply to ACLE v1.1. AArch64's back end does not have support for ! 16-bit floating point Advanced SIMD intrinsics yet. See *note ARM Options:: and *note AArch64 Options:: for more information on the availability of extensions. *************** File: gcc.info, Node: AVR Built-in Func *** 37040,37054 **** 6.59.9 AVR Built-in Functions ----------------------------- ! For each built-in function for AVR, there is an equally named, uppercase ! built-in macro defined. That way users can easily query if or if not a ! specific built-in is implemented or not. For example, if ! '__builtin_avr_nop' is available the macro '__BUILTIN_AVR_NOP' is ! defined to '1' and undefined otherwise. The following built-in functions map to the respective machine ! instruction, i.e. 'nop', 'sei', 'cli', 'sleep', 'wdr', 'swap', 'fmul', ! 'fmuls' resp. 'fmulsu'. The three 'fmul*' built-ins are implemented as library call if no hardware multiplier is available. void __builtin_avr_nop (void) --- 37466,37480 ---- 6.59.9 AVR Built-in Functions ----------------------------- ! For each built-in function for AVR, there is an equally named, ! uppercase built-in macro defined. That way users can easily query if or ! if not a specific built-in is implemented or not. For example, if ! `__builtin_avr_nop' is available the macro `__BUILTIN_AVR_NOP' is ! defined to `1' and undefined otherwise. The following built-in functions map to the respective machine ! instruction, i.e. `nop', `sei', `cli', `sleep', `wdr', `swap', `fmul', ! `fmuls' resp. `fmulsu'. The three `fmul*' built-ins are implemented as library call if no hardware multiplier is available. void __builtin_avr_nop (void) *************** library call if no hardware multiplier i *** 37065,37097 **** implements void __builtin_avr_delay_cycles (unsigned long ticks) ! 'ticks' is the number of ticks to delay execution. Note that this built-in does not take into account the effect of interrupts that might ! increase delay time. 'ticks' must be a compile-time integer constant; delays with a variable number of cycles are not supported. char __builtin_avr_flash_segment (const __memx void*) This built-in takes a byte address to the 24-bit *note address space: ! AVR Named Address Spaces. '__memx' and returns the number of the flash ! segment (the 64 KiB chunk) where the address points to. Counting starts ! at '0'. If the address does not point to flash memory, return '-1'. unsigned char __builtin_avr_insert_bits (unsigned long map, unsigned char bits, unsigned char val) ! Insert bits from BITS into VAL and return the resulting value. The nibbles of MAP determine how the insertion is performed: Let X be the N-th nibble of MAP ! 1. If X is '0xf', then the N-th bit of VAL is returned unaltered. 2. If X is in the range 0...7, then the N-th result bit is set to the X-th bit of BITS ! 3. If X is in the range 8...'0xe', then the N-th result bit is undefined. One typical use case for this built-in is adjusting input and output ! values to non-contiguous port layouts. Some examples: // same as val, bits is unused __builtin_avr_insert_bits (0xffffffff, bits, val) --- 37491,37524 ---- implements void __builtin_avr_delay_cycles (unsigned long ticks) ! `ticks' is the number of ticks to delay execution. Note that this built-in does not take into account the effect of interrupts that might ! increase delay time. `ticks' must be a compile-time integer constant; delays with a variable number of cycles are not supported. char __builtin_avr_flash_segment (const __memx void*) This built-in takes a byte address to the 24-bit *note address space: ! AVR Named Address Spaces. `__memx' and returns the number of the flash ! segment (the 64 KiB chunk) where the address points to. Counting ! starts at `0'. If the address does not point to flash memory, return ! `-1'. unsigned char __builtin_avr_insert_bits (unsigned long map, unsigned char bits, unsigned char val) ! Insert bits from BITS into VAL and return the resulting value. The nibbles of MAP determine how the insertion is performed: Let X be the N-th nibble of MAP ! 1. If X is `0xf', then the N-th bit of VAL is returned unaltered. 2. If X is in the range 0...7, then the N-th result bit is set to the X-th bit of BITS ! 3. If X is in the range 8...`0xe', then the N-th result bit is undefined. One typical use case for this built-in is adjusting input and output ! values to non-contiguous port layouts. Some examples: // same as val, bits is unused __builtin_avr_insert_bits (0xffffffff, bits, val) *************** File: gcc.info, Node: Blackfin Built-in *** 37116,37122 **** ----------------------------------- Currently, there are two Blackfin-specific built-in functions. These ! are used for generating 'CSYNC' and 'SSYNC' machine insns without using inline assembly; by using these built-in functions the compiler can automatically add workarounds for hardware errata involving these instructions. These functions are named as follows: --- 37543,37549 ---- ----------------------------------- Currently, there are two Blackfin-specific built-in functions. These ! are used for generating `CSYNC' and `SSYNC' machine insns without using inline assembly; by using these built-in functions the compiler can automatically add workarounds for hardware errata involving these instructions. These functions are named as follows: *************** File: gcc.info, Node: FR-V Built-in Fun *** 37131,37144 **** ------------------------------- GCC provides many FR-V-specific built-in functions. In general, these ! functions are intended to be compatible with those described by 'FR-V ! Family, Softune C/C++ Compiler Manual (V6), Fujitsu Semiconductor'. The ! two exceptions are '__MDUNPACKH' and '__MBTOHE', the GCC forms of which ! pass 128-bit values by pointer rather than by value. ! Most of the functions are named after specific FR-V instructions. Such ! functions are said to be "directly mapped" and are summarized here in ! tabular form. * Menu: --- 37558,37571 ---- ------------------------------- GCC provides many FR-V-specific built-in functions. In general, these ! functions are intended to be compatible with those described by `FR-V ! Family, Softune C/C++ Compiler Manual (V6), Fujitsu Semiconductor'. ! The two exceptions are `__MDUNPACKH' and `__MBTOHE', the GCC forms of ! which pass 128-bit values by pointer rather than by value. ! Most of the functions are named after specific FR-V instructions. ! Such functions are said to be "directly mapped" and are summarized here ! in tabular form. * Menu: *************** In order to make this classification cle *** 37160,37189 **** and return values are given the following pseudo types: Pseudo type Real C type Constant? Description ! 'uh' 'unsigned short' No an unsigned halfword ! 'uw1' 'unsigned int' No an unsigned word ! 'sw1' 'int' No a signed word ! 'uw2' 'unsigned long long' No an unsigned doubleword ! 'sw2' 'long long' No a signed doubleword ! 'const' 'int' Yes an integer constant ! 'acc' 'int' Yes an ACC register number ! 'iacc' 'int' Yes an IACC register number These pseudo types are not defined by GCC, they are simply a notational convenience used in this manual. ! Arguments of type 'uh', 'uw1', 'sw1', 'uw2' and 'sw2' are evaluated at run time. They correspond to register operands in the underlying FR-V instructions. ! 'const' arguments represent immediate operands in the underlying FR-V instructions. They must be compile-time constants. ! 'acc' arguments are evaluated at compile time and specify the number of ! an accumulator register. For example, an 'acc' argument of 2 selects ! the ACC2 register. ! 'iacc' arguments are similar to 'acc' arguments but specify the number of an IACC register. See *note Other Built-in Functions:: for more details. --- 37587,37616 ---- and return values are given the following pseudo types: Pseudo type Real C type Constant? Description ! `uh' `unsigned short' No an unsigned halfword ! `uw1' `unsigned int' No an unsigned word ! `sw1' `int' No a signed word ! `uw2' `unsigned long long' No an unsigned doubleword ! `sw2' `long long' No a signed doubleword ! `const' `int' Yes an integer constant ! `acc' `int' Yes an ACC register number ! `iacc' `int' Yes an IACC register number These pseudo types are not defined by GCC, they are simply a notational convenience used in this manual. ! Arguments of type `uh', `uw1', `sw1', `uw2' and `sw2' are evaluated at run time. They correspond to register operands in the underlying FR-V instructions. ! `const' arguments represent immediate operands in the underlying FR-V instructions. They must be compile-time constants. ! `acc' arguments are evaluated at compile time and specify the number ! of an accumulator register. For example, an `acc' argument of 2 ! selects the ACC2 register. ! `iacc' arguments are similar to `acc' arguments but specify the number of an IACC register. See *note Other Built-in Functions:: for more details. *************** File: gcc.info, Node: Directly-mapped I *** 37196,37211 **** The functions listed below map directly to FR-V I-type instructions. Function prototype Example usage Assembly output ! 'sw1 __ADDSS (sw1, sw1)' 'C = __ADDSS (A, B)' 'ADDSS A,B,C' ! 'sw1 __SCAN (sw1, sw1)' 'C = __SCAN (A, B)' 'SCAN A,B,C' ! 'sw1 __SCUTSS (sw1)' 'B = __SCUTSS (A)' 'SCUTSS A,B' ! 'sw1 __SLASS (sw1, sw1)' 'C = __SLASS (A, B)' 'SLASS A,B,C' ! 'void __SMASS (sw1, sw1)' '__SMASS (A, B)' 'SMASS A,B' ! 'void __SMSSS (sw1, sw1)' '__SMSSS (A, B)' 'SMSSS A,B' ! 'void __SMU (sw1, sw1)' '__SMU (A, B)' 'SMU A,B' ! 'sw2 __SMUL (sw1, sw1)' 'C = __SMUL (A, B)' 'SMUL A,B,C' ! 'sw1 __SUBSS (sw1, sw1)' 'C = __SUBSS (A, B)' 'SUBSS A,B,C' ! 'uw2 __UMUL (uw1, uw1)' 'C = __UMUL (A, B)' 'UMUL A,B,C'  File: gcc.info, Node: Directly-mapped Media Functions, Next: Raw read/write Functions, Prev: Directly-mapped Integer Functions, Up: FR-V Built-in Functions --- 37623,37638 ---- The functions listed below map directly to FR-V I-type instructions. Function prototype Example usage Assembly output ! `sw1 __ADDSS (sw1, sw1)' `C = __ADDSS (A, B)' `ADDSS A,B,C' ! `sw1 __SCAN (sw1, sw1)' `C = __SCAN (A, B)' `SCAN A,B,C' ! `sw1 __SCUTSS (sw1)' `B = __SCUTSS (A)' `SCUTSS A,B' ! `sw1 __SLASS (sw1, sw1)' `C = __SLASS (A, B)' `SLASS A,B,C' ! `void __SMASS (sw1, sw1)' `__SMASS (A, B)' `SMASS A,B' ! `void __SMSSS (sw1, sw1)' `__SMSSS (A, B)' `SMSSS A,B' ! `void __SMU (sw1, sw1)' `__SMU (A, B)' `SMU A,B' ! `sw2 __SMUL (sw1, sw1)' `C = __SMUL (A, B)' `SMUL A,B,C' ! `sw1 __SUBSS (sw1, sw1)' `C = __SUBSS (A, B)' `SUBSS A,B,C' ! `uw2 __UMUL (uw1, uw1)' `C = __UMUL (A, B)' `UMUL A,B,C'  File: gcc.info, Node: Directly-mapped Media Functions, Next: Raw read/write Functions, Prev: Directly-mapped Integer Functions, Up: FR-V Built-in Functions *************** File: gcc.info, Node: Directly-mapped M *** 37216,37358 **** The functions listed below map directly to FR-V M-type instructions. Function prototype Example usage Assembly output ! 'uw1 __MABSHS (sw1)' 'B = __MABSHS (A)' 'MABSHS A,B' ! 'void __MADDACCS (acc, acc)' '__MADDACCS (B, A)' 'MADDACCS A,B' ! 'sw1 __MADDHSS (sw1, sw1)' 'C = __MADDHSS (A, 'MADDHSS A,B,C' ! B)' ! 'uw1 __MADDHUS (uw1, uw1)' 'C = __MADDHUS (A, 'MADDHUS A,B,C' ! B)' ! 'uw1 __MAND (uw1, uw1)' 'C = __MAND (A, B)' 'MAND A,B,C' ! 'void __MASACCS (acc, acc)' '__MASACCS (B, A)' 'MASACCS A,B' ! 'uw1 __MAVEH (uw1, uw1)' 'C = __MAVEH (A, B)' 'MAVEH A,B,C' ! 'uw2 __MBTOH (uw1)' 'B = __MBTOH (A)' 'MBTOH A,B' ! 'void __MBTOHE (uw1 *, uw1)' '__MBTOHE (&B, A)' 'MBTOHE A,B' ! 'void __MCLRACC (acc)' '__MCLRACC (A)' 'MCLRACC A' ! 'void __MCLRACCA (void)' '__MCLRACCA ()' 'MCLRACCA' ! 'uw1 __Mcop1 (uw1, uw1)' 'C = __Mcop1 (A, B)' 'Mcop1 A,B,C' ! 'uw1 __Mcop2 (uw1, uw1)' 'C = __Mcop2 (A, B)' 'Mcop2 A,B,C' ! 'uw1 __MCPLHI (uw2, const)' 'C = __MCPLHI (A, B)' 'MCPLHI A,#B,C' ! 'uw1 __MCPLI (uw2, const)' 'C = __MCPLI (A, B)' 'MCPLI A,#B,C' ! 'void __MCPXIS (acc, sw1, '__MCPXIS (C, A, B)' 'MCPXIS A,B,C' ! sw1)' ! 'void __MCPXIU (acc, uw1, '__MCPXIU (C, A, B)' 'MCPXIU A,B,C' ! uw1)' ! 'void __MCPXRS (acc, sw1, '__MCPXRS (C, A, B)' 'MCPXRS A,B,C' ! sw1)' ! 'void __MCPXRU (acc, uw1, '__MCPXRU (C, A, B)' 'MCPXRU A,B,C' ! uw1)' ! 'uw1 __MCUT (acc, uw1)' 'C = __MCUT (A, B)' 'MCUT A,B,C' ! 'uw1 __MCUTSS (acc, sw1)' 'C = __MCUTSS (A, B)' 'MCUTSS A,B,C' ! 'void __MDADDACCS (acc, acc)' '__MDADDACCS (B, A)' 'MDADDACCS A,B' ! 'void __MDASACCS (acc, acc)' '__MDASACCS (B, A)' 'MDASACCS A,B' ! 'uw2 __MDCUTSSI (acc, const)' 'C = __MDCUTSSI (A, 'MDCUTSSI ! B)' A,#B,C' ! 'uw2 __MDPACKH (uw2, uw2)' 'C = __MDPACKH (A, 'MDPACKH A,B,C' ! B)' ! 'uw2 __MDROTLI (uw2, const)' 'C = __MDROTLI (A, 'MDROTLI ! B)' A,#B,C' ! 'void __MDSUBACCS (acc, acc)' '__MDSUBACCS (B, A)' 'MDSUBACCS A,B' ! 'void __MDUNPACKH (uw1 *, '__MDUNPACKH (&B, A)' 'MDUNPACKH A,B' ! uw2)' ! 'uw2 __MEXPDHD (uw1, const)' 'C = __MEXPDHD (A, 'MEXPDHD ! B)' A,#B,C' ! 'uw1 __MEXPDHW (uw1, const)' 'C = __MEXPDHW (A, 'MEXPDHW ! B)' A,#B,C' ! 'uw1 __MHDSETH (uw1, const)' 'C = __MHDSETH (A, 'MHDSETH ! B)' A,#B,C' ! 'sw1 __MHDSETS (const)' 'B = __MHDSETS (A)' 'MHDSETS #A,B' ! 'uw1 __MHSETHIH (uw1, const)' 'B = __MHSETHIH (B, 'MHSETHIH #A,B' ! A)' ! 'sw1 __MHSETHIS (sw1, const)' 'B = __MHSETHIS (B, 'MHSETHIS #A,B' ! A)' ! 'uw1 __MHSETLOH (uw1, const)' 'B = __MHSETLOH (B, 'MHSETLOH #A,B' ! A)' ! 'sw1 __MHSETLOS (sw1, const)' 'B = __MHSETLOS (B, 'MHSETLOS #A,B' ! A)' ! 'uw1 __MHTOB (uw2)' 'B = __MHTOB (A)' 'MHTOB A,B' ! 'void __MMACHS (acc, sw1, '__MMACHS (C, A, B)' 'MMACHS A,B,C' ! sw1)' ! 'void __MMACHU (acc, uw1, '__MMACHU (C, A, B)' 'MMACHU A,B,C' ! uw1)' ! 'void __MMRDHS (acc, sw1, '__MMRDHS (C, A, B)' 'MMRDHS A,B,C' ! sw1)' ! 'void __MMRDHU (acc, uw1, '__MMRDHU (C, A, B)' 'MMRDHU A,B,C' ! uw1)' ! 'void __MMULHS (acc, sw1, '__MMULHS (C, A, B)' 'MMULHS A,B,C' ! sw1)' ! 'void __MMULHU (acc, uw1, '__MMULHU (C, A, B)' 'MMULHU A,B,C' ! uw1)' ! 'void __MMULXHS (acc, sw1, '__MMULXHS (C, A, B)' 'MMULXHS A,B,C' ! sw1)' ! 'void __MMULXHU (acc, uw1, '__MMULXHU (C, A, B)' 'MMULXHU A,B,C' ! uw1)' ! 'uw1 __MNOT (uw1)' 'B = __MNOT (A)' 'MNOT A,B' ! 'uw1 __MOR (uw1, uw1)' 'C = __MOR (A, B)' 'MOR A,B,C' ! 'uw1 __MPACKH (uh, uh)' 'C = __MPACKH (A, B)' 'MPACKH A,B,C' ! 'sw2 __MQADDHSS (sw2, sw2)' 'C = __MQADDHSS (A, 'MQADDHSS ! B)' A,B,C' ! 'uw2 __MQADDHUS (uw2, uw2)' 'C = __MQADDHUS (A, 'MQADDHUS ! B)' A,B,C' ! 'void __MQCPXIS (acc, sw2, '__MQCPXIS (C, A, B)' 'MQCPXIS A,B,C' ! sw2)' ! 'void __MQCPXIU (acc, uw2, '__MQCPXIU (C, A, B)' 'MQCPXIU A,B,C' ! uw2)' ! 'void __MQCPXRS (acc, sw2, '__MQCPXRS (C, A, B)' 'MQCPXRS A,B,C' ! sw2)' ! 'void __MQCPXRU (acc, uw2, '__MQCPXRU (C, A, B)' 'MQCPXRU A,B,C' ! uw2)' ! 'sw2 __MQLCLRHS (sw2, sw2)' 'C = __MQLCLRHS (A, 'MQLCLRHS ! B)' A,B,C' ! 'sw2 __MQLMTHS (sw2, sw2)' 'C = __MQLMTHS (A, 'MQLMTHS A,B,C' ! B)' ! 'void __MQMACHS (acc, sw2, '__MQMACHS (C, A, B)' 'MQMACHS A,B,C' ! sw2)' ! 'void __MQMACHU (acc, uw2, '__MQMACHU (C, A, B)' 'MQMACHU A,B,C' ! uw2)' ! 'void __MQMACXHS (acc, sw2, '__MQMACXHS (C, A, 'MQMACXHS ! sw2)' B)' A,B,C' ! 'void __MQMULHS (acc, sw2, '__MQMULHS (C, A, B)' 'MQMULHS A,B,C' ! sw2)' ! 'void __MQMULHU (acc, uw2, '__MQMULHU (C, A, B)' 'MQMULHU A,B,C' ! uw2)' ! 'void __MQMULXHS (acc, sw2, '__MQMULXHS (C, A, 'MQMULXHS ! sw2)' B)' A,B,C' ! 'void __MQMULXHU (acc, uw2, '__MQMULXHU (C, A, 'MQMULXHU ! uw2)' B)' A,B,C' ! 'sw2 __MQSATHS (sw2, sw2)' 'C = __MQSATHS (A, 'MQSATHS A,B,C' ! B)' ! 'uw2 __MQSLLHI (uw2, int)' 'C = __MQSLLHI (A, 'MQSLLHI A,B,C' ! B)' ! 'sw2 __MQSRAHI (sw2, int)' 'C = __MQSRAHI (A, 'MQSRAHI A,B,C' ! B)' ! 'sw2 __MQSUBHSS (sw2, sw2)' 'C = __MQSUBHSS (A, 'MQSUBHSS ! B)' A,B,C' ! 'uw2 __MQSUBHUS (uw2, uw2)' 'C = __MQSUBHUS (A, 'MQSUBHUS ! B)' A,B,C' ! 'void __MQXMACHS (acc, sw2, '__MQXMACHS (C, A, 'MQXMACHS ! sw2)' B)' A,B,C' ! 'void __MQXMACXHS (acc, sw2, '__MQXMACXHS (C, A, 'MQXMACXHS ! sw2)' B)' A,B,C' ! 'uw1 __MRDACC (acc)' 'B = __MRDACC (A)' 'MRDACC A,B' ! 'uw1 __MRDACCG (acc)' 'B = __MRDACCG (A)' 'MRDACCG A,B' ! 'uw1 __MROTLI (uw1, const)' 'C = __MROTLI (A, B)' 'MROTLI A,#B,C' ! 'uw1 __MROTRI (uw1, const)' 'C = __MROTRI (A, B)' 'MROTRI A,#B,C' ! 'sw1 __MSATHS (sw1, sw1)' 'C = __MSATHS (A, B)' 'MSATHS A,B,C' ! 'uw1 __MSATHU (uw1, uw1)' 'C = __MSATHU (A, B)' 'MSATHU A,B,C' ! 'uw1 __MSLLHI (uw1, const)' 'C = __MSLLHI (A, B)' 'MSLLHI A,#B,C' ! 'sw1 __MSRAHI (sw1, const)' 'C = __MSRAHI (A, B)' 'MSRAHI A,#B,C' ! 'uw1 __MSRLHI (uw1, const)' 'C = __MSRLHI (A, B)' 'MSRLHI A,#B,C' ! 'void __MSUBACCS (acc, acc)' '__MSUBACCS (B, A)' 'MSUBACCS A,B' ! 'sw1 __MSUBHSS (sw1, sw1)' 'C = __MSUBHSS (A, 'MSUBHSS A,B,C' ! B)' ! 'uw1 __MSUBHUS (uw1, uw1)' 'C = __MSUBHUS (A, 'MSUBHUS A,B,C' ! B)' ! 'void __MTRAP (void)' '__MTRAP ()' 'MTRAP' ! 'uw2 __MUNPACKH (uw1)' 'B = __MUNPACKH (A)' 'MUNPACKH A,B' ! 'uw1 __MWCUT (uw2, uw1)' 'C = __MWCUT (A, B)' 'MWCUT A,B,C' ! 'void __MWTACC (acc, uw1)' '__MWTACC (B, A)' 'MWTACC A,B' ! 'void __MWTACCG (acc, uw1)' '__MWTACCG (B, A)' 'MWTACCG A,B' ! 'uw1 __MXOR (uw1, uw1)' 'C = __MXOR (A, B)' 'MXOR A,B,C'  File: gcc.info, Node: Raw read/write Functions, Next: Other Built-in Functions, Prev: Directly-mapped Media Functions, Up: FR-V Built-in Functions --- 37643,37741 ---- The functions listed below map directly to FR-V M-type instructions. Function prototype Example usage Assembly output ! `uw1 __MABSHS (sw1)' `B = __MABSHS (A)' `MABSHS A,B' ! `void __MADDACCS (acc, acc)' `__MADDACCS (B, A)' `MADDACCS A,B' ! `sw1 __MADDHSS (sw1, sw1)' `C = __MADDHSS (A, B)' `MADDHSS A,B,C' ! `uw1 __MADDHUS (uw1, uw1)' `C = __MADDHUS (A, B)' `MADDHUS A,B,C' ! `uw1 __MAND (uw1, uw1)' `C = __MAND (A, B)' `MAND A,B,C' ! `void __MASACCS (acc, acc)' `__MASACCS (B, A)' `MASACCS A,B' ! `uw1 __MAVEH (uw1, uw1)' `C = __MAVEH (A, B)' `MAVEH A,B,C' ! `uw2 __MBTOH (uw1)' `B = __MBTOH (A)' `MBTOH A,B' ! `void __MBTOHE (uw1 *, uw1)' `__MBTOHE (&B, A)' `MBTOHE A,B' ! `void __MCLRACC (acc)' `__MCLRACC (A)' `MCLRACC A' ! `void __MCLRACCA (void)' `__MCLRACCA ()' `MCLRACCA' ! `uw1 __Mcop1 (uw1, uw1)' `C = __Mcop1 (A, B)' `Mcop1 A,B,C' ! `uw1 __Mcop2 (uw1, uw1)' `C = __Mcop2 (A, B)' `Mcop2 A,B,C' ! `uw1 __MCPLHI (uw2, const)' `C = __MCPLHI (A, B)' `MCPLHI A,#B,C' ! `uw1 __MCPLI (uw2, const)' `C = __MCPLI (A, B)' `MCPLI A,#B,C' ! `void __MCPXIS (acc, sw1, sw1)' `__MCPXIS (C, A, B)' `MCPXIS A,B,C' ! `void __MCPXIU (acc, uw1, uw1)' `__MCPXIU (C, A, B)' `MCPXIU A,B,C' ! `void __MCPXRS (acc, sw1, sw1)' `__MCPXRS (C, A, B)' `MCPXRS A,B,C' ! `void __MCPXRU (acc, uw1, uw1)' `__MCPXRU (C, A, B)' `MCPXRU A,B,C' ! `uw1 __MCUT (acc, uw1)' `C = __MCUT (A, B)' `MCUT A,B,C' ! `uw1 __MCUTSS (acc, sw1)' `C = __MCUTSS (A, B)' `MCUTSS A,B,C' ! `void __MDADDACCS (acc, acc)' `__MDADDACCS (B, A)' `MDADDACCS A,B' ! `void __MDASACCS (acc, acc)' `__MDASACCS (B, A)' `MDASACCS A,B' ! `uw2 __MDCUTSSI (acc, const)' `C = __MDCUTSSI (A, B)' `MDCUTSSI A,#B,C' ! `uw2 __MDPACKH (uw2, uw2)' `C = __MDPACKH (A, B)' `MDPACKH A,B,C' ! `uw2 __MDROTLI (uw2, const)' `C = __MDROTLI (A, B)' `MDROTLI A,#B,C' ! `void __MDSUBACCS (acc, acc)' `__MDSUBACCS (B, A)' `MDSUBACCS A,B' ! `void __MDUNPACKH (uw1 *, uw2)' `__MDUNPACKH (&B, A)' `MDUNPACKH A,B' ! `uw2 __MEXPDHD (uw1, const)' `C = __MEXPDHD (A, B)' `MEXPDHD A,#B,C' ! `uw1 __MEXPDHW (uw1, const)' `C = __MEXPDHW (A, B)' `MEXPDHW A,#B,C' ! `uw1 __MHDSETH (uw1, const)' `C = __MHDSETH (A, B)' `MHDSETH A,#B,C' ! `sw1 __MHDSETS (const)' `B = __MHDSETS (A)' `MHDSETS #A,B' ! `uw1 __MHSETHIH (uw1, const)' `B = __MHSETHIH (B, A)' `MHSETHIH #A,B' ! `sw1 __MHSETHIS (sw1, const)' `B = __MHSETHIS (B, A)' `MHSETHIS #A,B' ! `uw1 __MHSETLOH (uw1, const)' `B = __MHSETLOH (B, A)' `MHSETLOH #A,B' ! `sw1 __MHSETLOS (sw1, const)' `B = __MHSETLOS (B, A)' `MHSETLOS #A,B' ! `uw1 __MHTOB (uw2)' `B = __MHTOB (A)' `MHTOB A,B' ! `void __MMACHS (acc, sw1, sw1)' `__MMACHS (C, A, B)' `MMACHS A,B,C' ! `void __MMACHU (acc, uw1, uw1)' `__MMACHU (C, A, B)' `MMACHU A,B,C' ! `void __MMRDHS (acc, sw1, sw1)' `__MMRDHS (C, A, B)' `MMRDHS A,B,C' ! `void __MMRDHU (acc, uw1, uw1)' `__MMRDHU (C, A, B)' `MMRDHU A,B,C' ! `void __MMULHS (acc, sw1, sw1)' `__MMULHS (C, A, B)' `MMULHS A,B,C' ! `void __MMULHU (acc, uw1, uw1)' `__MMULHU (C, A, B)' `MMULHU A,B,C' ! `void __MMULXHS (acc, sw1, sw1)' `__MMULXHS (C, A, B)' `MMULXHS A,B,C' ! `void __MMULXHU (acc, uw1, uw1)' `__MMULXHU (C, A, B)' `MMULXHU A,B,C' ! `uw1 __MNOT (uw1)' `B = __MNOT (A)' `MNOT A,B' ! `uw1 __MOR (uw1, uw1)' `C = __MOR (A, B)' `MOR A,B,C' ! `uw1 __MPACKH (uh, uh)' `C = __MPACKH (A, B)' `MPACKH A,B,C' ! `sw2 __MQADDHSS (sw2, sw2)' `C = __MQADDHSS (A, B)' `MQADDHSS A,B,C' ! `uw2 __MQADDHUS (uw2, uw2)' `C = __MQADDHUS (A, B)' `MQADDHUS A,B,C' ! `void __MQCPXIS (acc, sw2, sw2)' `__MQCPXIS (C, A, B)' `MQCPXIS A,B,C' ! `void __MQCPXIU (acc, uw2, uw2)' `__MQCPXIU (C, A, B)' `MQCPXIU A,B,C' ! `void __MQCPXRS (acc, sw2, sw2)' `__MQCPXRS (C, A, B)' `MQCPXRS A,B,C' ! `void __MQCPXRU (acc, uw2, uw2)' `__MQCPXRU (C, A, B)' `MQCPXRU A,B,C' ! `sw2 __MQLCLRHS (sw2, sw2)' `C = __MQLCLRHS (A, B)' `MQLCLRHS A,B,C' ! `sw2 __MQLMTHS (sw2, sw2)' `C = __MQLMTHS (A, B)' `MQLMTHS A,B,C' ! `void __MQMACHS (acc, sw2, sw2)' `__MQMACHS (C, A, B)' `MQMACHS A,B,C' ! `void __MQMACHU (acc, uw2, uw2)' `__MQMACHU (C, A, B)' `MQMACHU A,B,C' ! `void __MQMACXHS (acc, sw2, `__MQMACXHS (C, A, B)' `MQMACXHS A,B,C' ! sw2)' ! `void __MQMULHS (acc, sw2, sw2)' `__MQMULHS (C, A, B)' `MQMULHS A,B,C' ! `void __MQMULHU (acc, uw2, uw2)' `__MQMULHU (C, A, B)' `MQMULHU A,B,C' ! `void __MQMULXHS (acc, sw2, `__MQMULXHS (C, A, B)' `MQMULXHS A,B,C' ! sw2)' ! `void __MQMULXHU (acc, uw2, `__MQMULXHU (C, A, B)' `MQMULXHU A,B,C' ! uw2)' ! `sw2 __MQSATHS (sw2, sw2)' `C = __MQSATHS (A, B)' `MQSATHS A,B,C' ! `uw2 __MQSLLHI (uw2, int)' `C = __MQSLLHI (A, B)' `MQSLLHI A,B,C' ! `sw2 __MQSRAHI (sw2, int)' `C = __MQSRAHI (A, B)' `MQSRAHI A,B,C' ! `sw2 __MQSUBHSS (sw2, sw2)' `C = __MQSUBHSS (A, B)' `MQSUBHSS A,B,C' ! `uw2 __MQSUBHUS (uw2, uw2)' `C = __MQSUBHUS (A, B)' `MQSUBHUS A,B,C' ! `void __MQXMACHS (acc, sw2, `__MQXMACHS (C, A, B)' `MQXMACHS A,B,C' ! sw2)' ! `void __MQXMACXHS (acc, sw2, `__MQXMACXHS (C, A, B)' `MQXMACXHS A,B,C' ! sw2)' ! `uw1 __MRDACC (acc)' `B = __MRDACC (A)' `MRDACC A,B' ! `uw1 __MRDACCG (acc)' `B = __MRDACCG (A)' `MRDACCG A,B' ! `uw1 __MROTLI (uw1, const)' `C = __MROTLI (A, B)' `MROTLI A,#B,C' ! `uw1 __MROTRI (uw1, const)' `C = __MROTRI (A, B)' `MROTRI A,#B,C' ! `sw1 __MSATHS (sw1, sw1)' `C = __MSATHS (A, B)' `MSATHS A,B,C' ! `uw1 __MSATHU (uw1, uw1)' `C = __MSATHU (A, B)' `MSATHU A,B,C' ! `uw1 __MSLLHI (uw1, const)' `C = __MSLLHI (A, B)' `MSLLHI A,#B,C' ! `sw1 __MSRAHI (sw1, const)' `C = __MSRAHI (A, B)' `MSRAHI A,#B,C' ! `uw1 __MSRLHI (uw1, const)' `C = __MSRLHI (A, B)' `MSRLHI A,#B,C' ! `void __MSUBACCS (acc, acc)' `__MSUBACCS (B, A)' `MSUBACCS A,B' ! `sw1 __MSUBHSS (sw1, sw1)' `C = __MSUBHSS (A, B)' `MSUBHSS A,B,C' ! `uw1 __MSUBHUS (uw1, uw1)' `C = __MSUBHUS (A, B)' `MSUBHUS A,B,C' ! `void __MTRAP (void)' `__MTRAP ()' `MTRAP' ! `uw2 __MUNPACKH (uw1)' `B = __MUNPACKH (A)' `MUNPACKH A,B' ! `uw1 __MWCUT (uw2, uw1)' `C = __MWCUT (A, B)' `MWCUT A,B,C' ! `void __MWTACC (acc, uw1)' `__MWTACC (B, A)' `MWTACC A,B' ! `void __MWTACCG (acc, uw1)' `__MWTACCG (B, A)' `MWTACCG A,B' ! `uw1 __MXOR (uw1, uw1)' `C = __MXOR (A, B)' `MXOR A,B,C'  File: gcc.info, Node: Raw read/write Functions, Next: Other Built-in Functions, Prev: Directly-mapped Media Functions, Up: FR-V Built-in Functions *************** File: gcc.info, Node: Raw read/write Fu *** 37361,37379 **** .................................. This sections describes built-in functions related to read and write ! instructions to access memory. These functions generate 'membar' instructions to flush the I/O load and stores where appropriate, as described in Fujitsu's manual described above. ! 'unsigned char __builtin_read8 (void *DATA)' ! 'unsigned short __builtin_read16 (void *DATA)' ! 'unsigned long __builtin_read32 (void *DATA)' ! 'unsigned long long __builtin_read64 (void *DATA)' ! 'void __builtin_write8 (void *DATA, unsigned char DATUM)' ! 'void __builtin_write16 (void *DATA, unsigned short DATUM)' ! 'void __builtin_write32 (void *DATA, unsigned long DATUM)' ! 'void __builtin_write64 (void *DATA, unsigned long long DATUM)'  File: gcc.info, Node: Other Built-in Functions, Prev: Raw read/write Functions, Up: FR-V Built-in Functions --- 37744,37768 ---- .................................. This sections describes built-in functions related to read and write ! instructions to access memory. These functions generate `membar' instructions to flush the I/O load and stores where appropriate, as described in Fujitsu's manual described above. ! `unsigned char __builtin_read8 (void *DATA)' ! `unsigned short __builtin_read16 (void *DATA)' ! ! `unsigned long __builtin_read32 (void *DATA)' ! ! `unsigned long long __builtin_read64 (void *DATA)' ! ! `void __builtin_write8 (void *DATA, unsigned char DATUM)' ! ! `void __builtin_write16 (void *DATA, unsigned short DATUM)' ! ! `void __builtin_write32 (void *DATA, unsigned long DATUM)' ! ! `void __builtin_write64 (void *DATA, unsigned long long DATUM)'  File: gcc.info, Node: Other Built-in Functions, Prev: Raw read/write Functions, Up: FR-V Built-in Functions *************** File: gcc.info, Node: Other Built-in Fu *** 37384,37411 **** This section describes built-in functions that are not named after a specific FR-V instruction. ! 'sw2 __IACCreadll (iacc REG)' Return the full 64-bit value of IACC0. The REG argument is reserved for future expansion and must be 0. ! 'sw1 __IACCreadl (iacc REG)' Return the value of IACC0H if REG is 0 and IACC0L if REG is 1. Other values of REG are rejected as invalid. ! 'void __IACCsetll (iacc REG, sw2 X)' Set the full 64-bit value of IACC0 to X. The REG argument is reserved for future expansion and must be 0. ! 'void __IACCsetl (iacc REG, sw1 X)' Set IACC0H to X if REG is 0 and IACC0L to X if REG is 1. Other values of REG are rejected as invalid. ! 'void __data_prefetch0 (const void *X)' ! Use the 'dcpl' instruction to load the contents of address X into the data cache. ! 'void __data_prefetch (const void *X)' ! Use the 'nldub' instruction to load the contents of address X into the data cache. The instruction is issued in slot I1.  --- 37773,37800 ---- This section describes built-in functions that are not named after a specific FR-V instruction. ! `sw2 __IACCreadll (iacc REG)' Return the full 64-bit value of IACC0. The REG argument is reserved for future expansion and must be 0. ! `sw1 __IACCreadl (iacc REG)' Return the value of IACC0H if REG is 0 and IACC0L if REG is 1. Other values of REG are rejected as invalid. ! `void __IACCsetll (iacc REG, sw2 X)' Set the full 64-bit value of IACC0 to X. The REG argument is reserved for future expansion and must be 0. ! `void __IACCsetl (iacc REG, sw1 X)' Set IACC0H to X if REG is 0 and IACC0L to X if REG is 1. Other values of REG are rejected as invalid. ! `void __data_prefetch0 (const void *X)' ! Use the `dcpl' instruction to load the contents of address X into the data cache. ! `void __data_prefetch (const void *X)' ! Use the `nldub' instruction to load the contents of address X into the data cache. The instruction is issued in slot I1.  *************** media applications. It provides instruc *** 37420,37453 **** 8-bit/16-bit integer data, Q7, Q15 and Q31 fractional data. GCC supports MIPS DSP operations using both the generic vector ! extensions (*note Vector Extensions::) and a collection of MIPS-specific ! built-in functions. Both kinds of support are enabled by the '-mdsp' ! command-line option. Revision 2 of the ASE was introduced in the second half of 2006. This revision adds extra instructions to the original ASE, but is otherwise backwards-compatible with it. You can select revision 2 using the ! command-line option '-mdspr2'; this option implies '-mdsp'. The SCOUNT and POS bits of the DSP control register are global. The ! WRDSP, EXTPDP, EXTPDPV and MTHLIP instructions modify the SCOUNT and POS ! bits. During optimization, the compiler does not delete these instructions and it does not delete calls to functions containing these instructions. ! At present, GCC only provides support for operations on 32-bit vectors. ! The vector type associated with 8-bit integer data is usually called ! 'v4i8', the vector type associated with Q7 is usually called 'v4q7', the ! vector type associated with 16-bit integer data is usually called ! 'v2i16', and the vector type associated with Q15 is usually called ! 'v2q15'. They can be defined in C as follows: typedef signed char v4i8 __attribute__ ((vector_size(4))); typedef signed char v4q7 __attribute__ ((vector_size(4))); typedef short v2i16 __attribute__ ((vector_size(4))); typedef short v2q15 __attribute__ ((vector_size(4))); ! 'v4i8', 'v4q7', 'v2i16' and 'v2q15' values are initialized in the same way as aggregates. For example: v4i8 a = {1, 2, 3, 4}; --- 37809,37842 ---- 8-bit/16-bit integer data, Q7, Q15 and Q31 fractional data. GCC supports MIPS DSP operations using both the generic vector ! extensions (*note Vector Extensions::) and a collection of ! MIPS-specific built-in functions. Both kinds of support are enabled by ! the `-mdsp' command-line option. Revision 2 of the ASE was introduced in the second half of 2006. This revision adds extra instructions to the original ASE, but is otherwise backwards-compatible with it. You can select revision 2 using the ! command-line option `-mdspr2'; this option implies `-mdsp'. The SCOUNT and POS bits of the DSP control register are global. The ! WRDSP, EXTPDP, EXTPDPV and MTHLIP instructions modify the SCOUNT and ! POS bits. During optimization, the compiler does not delete these instructions and it does not delete calls to functions containing these instructions. ! At present, GCC only provides support for operations on 32-bit ! vectors. The vector type associated with 8-bit integer data is usually ! called `v4i8', the vector type associated with Q7 is usually called ! `v4q7', the vector type associated with 16-bit integer data is usually ! called `v2i16', and the vector type associated with Q15 is usually ! called `v2q15'. They can be defined in C as follows: typedef signed char v4i8 __attribute__ ((vector_size(4))); typedef signed char v4q7 __attribute__ ((vector_size(4))); typedef short v2i16 __attribute__ ((vector_size(4))); typedef short v2q15 __attribute__ ((vector_size(4))); ! `v4i8', `v4q7', `v2i16' and `v2q15' values are initialized in the same way as aggregates. For example: v4i8 a = {1, 2, 3, 4}; *************** way as aggregates. For example: *** 37462,37491 **** packed. On little-endian targets, the first value is the least significant and the last value is the most significant. The opposite order applies to big-endian targets. For example, the code above sets ! the lowest byte of 'a' to '1' on little-endian targets and '4' on big-endian targets. _Note:_ Q7, Q15 and Q31 values must be initialized with their integer ! representation. As shown in this example, the integer representation of ! a Q7 value can be obtained by multiplying the fractional value by ! '0x1.0p7'. The equivalent for Q15 values is to multiply by '0x1.0p15'. ! The equivalent for Q31 values is to multiply by '0x1.0p31'. ! The table below lists the 'v4i8' and 'v2q15' operations for which ! hardware support exists. 'a' and 'b' are 'v4i8' values, and 'c' and 'd' ! are 'v2q15' values. C code MIPS instruction ! 'a + b' 'addu.qb' ! 'c + d' 'addq.ph' ! 'a - b' 'subu.qb' ! 'c - d' 'subq.ph' ! The table below lists the 'v2i16' operation for which hardware support ! exists for the DSP ASE REV 2. 'e' and 'f' are 'v2i16' values. C code MIPS instruction ! 'e * f' 'mul.ph' It is easier to describe the DSP built-in functions if we first define the following types: --- 37851,37880 ---- packed. On little-endian targets, the first value is the least significant and the last value is the most significant. The opposite order applies to big-endian targets. For example, the code above sets ! the lowest byte of `a' to `1' on little-endian targets and `4' on big-endian targets. _Note:_ Q7, Q15 and Q31 values must be initialized with their integer ! representation. As shown in this example, the integer representation ! of a Q7 value can be obtained by multiplying the fractional value by ! `0x1.0p7'. The equivalent for Q15 values is to multiply by `0x1.0p15'. ! The equivalent for Q31 values is to multiply by `0x1.0p31'. ! The table below lists the `v4i8' and `v2q15' operations for which ! hardware support exists. `a' and `b' are `v4i8' values, and `c' and ! `d' are `v2q15' values. C code MIPS instruction ! `a + b' `addu.qb' ! `c + d' `addq.ph' ! `a - b' `subu.qb' ! `c - d' `subq.ph' ! The table below lists the `v2i16' operation for which hardware support ! exists for the DSP ASE REV 2. `e' and `f' are `v2i16' values. C code MIPS instruction ! `e * f' `mul.ph' It is easier to describe the DSP built-in functions if we first define the following types: *************** the following types: *** 37495,37505 **** typedef unsigned int ui32; typedef long long a64; ! 'q31' and 'i32' are actually the same as 'int', but we use 'q31' to ! indicate a Q31 fractional value and 'i32' to indicate a 32-bit integer ! value. Similarly, 'a64' is the same as 'long long', but we use 'a64' to ! indicate values that are placed in one of the four DSP accumulators ! ('$ac0', '$ac1', '$ac2' or '$ac3'). Also, some built-in functions prefer or require immediate numbers as parameters, because the corresponding DSP instructions accept both --- 37884,37894 ---- typedef unsigned int ui32; typedef long long a64; ! `q31' and `i32' are actually the same as `int', but we use `q31' to ! indicate a Q31 fractional value and `i32' to indicate a 32-bit integer ! value. Similarly, `a64' is the same as `long long', but we use `a64' ! to indicate values that are placed in one of the four DSP accumulators ! (`$ac0', `$ac1', `$ac2' or `$ac3'). Also, some built-in functions prefer or require immediate numbers as parameters, because the corresponding DSP instructions accept both *************** only. The immediate parameters are list *** 37516,37523 **** imm_n512_511: -512 to 511. The following built-in functions map directly to a particular MIPS DSP ! instruction. Please refer to the architecture specification for details ! on what each instruction does. v2q15 __builtin_mips_addq_ph (v2q15, v2q15) v2q15 __builtin_mips_addq_s_ph (v2q15, v2q15) --- 37905,37912 ---- imm_n512_511: -512 to 511. The following built-in functions map directly to a particular MIPS DSP ! instruction. Please refer to the architecture specification for ! details on what each instruction does. v2q15 __builtin_mips_addq_ph (v2q15, v2q15) v2q15 __builtin_mips_addq_s_ph (v2q15, v2q15) *************** File: gcc.info, Node: MIPS Paired-Singl *** 37688,37708 **** ---------------------------------- The MIPS64 architecture includes a number of instructions that operate ! on pairs of single-precision floating-point values. Each pair is packed ! into a 64-bit floating-point register, with one element being designated ! the "upper half" and the other being designated the "lower half". GCC supports paired-single operations using both the generic vector ! extensions (*note Vector Extensions::) and a collection of MIPS-specific ! built-in functions. Both kinds of support are enabled by the ! '-mpaired-single' command-line option. The vector type associated with paired-single values is usually called ! 'v2sf'. It can be defined in C as follows: typedef float v2sf __attribute__ ((vector_size (8))); ! 'v2sf' values are initialized in the same way as aggregates. For example: v2sf a = {1.5, 9.1}; --- 38077,38098 ---- ---------------------------------- The MIPS64 architecture includes a number of instructions that operate ! on pairs of single-precision floating-point values. Each pair is ! packed into a 64-bit floating-point register, with one element being ! designated the "upper half" and the other being designated the "lower ! half". GCC supports paired-single operations using both the generic vector ! extensions (*note Vector Extensions::) and a collection of ! MIPS-specific built-in functions. Both kinds of support are enabled by ! the `-mpaired-single' command-line option. The vector type associated with paired-single values is usually called ! `v2sf'. It can be defined in C as follows: typedef float v2sf __attribute__ ((vector_size (8))); ! `v2sf' values are initialized in the same way as aggregates. For example: v2sf a = {1.5, 9.1}; *************** example: *** 37713,37721 **** _Note:_ The CPU's endianness determines which value is stored in the upper half of a register and which value is stored in the lower half. On little-endian targets, the first value is the lower one and the ! second value is the upper one. The opposite order applies to big-endian ! targets. For example, the code above sets the lower half of 'a' to ! '1.5' on little-endian targets and '9.1' on big-endian targets.  File: gcc.info, Node: MIPS Loongson Built-in Functions, Next: Other MIPS Built-in Functions, Prev: MIPS Paired-Single Support, Up: Target Builtins --- 38103,38111 ---- _Note:_ The CPU's endianness determines which value is stored in the upper half of a register and which value is stored in the lower half. On little-endian targets, the first value is the lower one and the ! second value is the upper one. The opposite order applies to ! big-endian targets. For example, the code above sets the lower half of ! `a' to `1.5' on little-endian targets and `9.1' on big-endian targets.  File: gcc.info, Node: MIPS Loongson Built-in Functions, Next: Other MIPS Built-in Functions, Prev: MIPS Paired-Single Support, Up: Target Builtins *************** File: gcc.info, Node: MIPS Loongson Bui *** 37725,37739 **** GCC provides intrinsics to access the SIMD instructions provided by the ST Microelectronics Loongson-2E and -2F processors. These intrinsics, ! available after inclusion of the 'loongson.h' header file, operate on the following 64-bit vector types: ! * 'uint8x8_t', a vector of eight unsigned 8-bit integers; ! * 'uint16x4_t', a vector of four unsigned 16-bit integers; ! * 'uint32x2_t', a vector of two unsigned 32-bit integers; ! * 'int8x8_t', a vector of eight signed 8-bit integers; ! * 'int16x4_t', a vector of four signed 16-bit integers; ! * 'int32x2_t', a vector of two signed 32-bit integers. The intrinsics provided are listed below; each is named after the machine instruction to which it corresponds, with suffixes added as --- 38115,38134 ---- GCC provides intrinsics to access the SIMD instructions provided by the ST Microelectronics Loongson-2E and -2F processors. These intrinsics, ! available after inclusion of the `loongson.h' header file, operate on the following 64-bit vector types: ! * `uint8x8_t', a vector of eight unsigned 8-bit integers; ! ! * `uint16x4_t', a vector of four unsigned 16-bit integers; ! ! * `uint32x2_t', a vector of two unsigned 32-bit integers; ! ! * `int8x8_t', a vector of eight signed 8-bit integers; ! ! * `int16x4_t', a vector of four signed 16-bit integers; ! ! * `int32x2_t', a vector of two signed 32-bit integers. The intrinsics provided are listed below; each is named after the machine instruction to which it corresponds, with suffixes added as *************** File: gcc.info, Node: Paired-Single Ari *** 37854,37876 **** 6.59.14.1 Paired-Single Arithmetic .................................. ! The table below lists the 'v2sf' operations for which hardware support ! exists. 'a', 'b' and 'c' are 'v2sf' values and 'x' is an integral value. C code MIPS instruction ! 'a + b' 'add.ps' ! 'a - b' 'sub.ps' ! '-a' 'neg.ps' ! 'a * b' 'mul.ps' ! 'a * b + c' 'madd.ps' ! 'a * b - c' 'msub.ps' ! '-(a * b + c)' 'nmadd.ps' ! '-(a * b - c)' 'nmsub.ps' ! 'x ? a : b' 'movn.ps'/'movz.ps' Note that the multiply-accumulate instructions can be disabled using ! the command-line option '-mno-fused-madd'.  File: gcc.info, Node: Paired-Single Built-in Functions, Next: MIPS-3D Built-in Functions, Prev: Paired-Single Arithmetic, Up: MIPS Loongson Built-in Functions --- 38249,38271 ---- 6.59.14.1 Paired-Single Arithmetic .................................. ! The table below lists the `v2sf' operations for which hardware support ! exists. `a', `b' and `c' are `v2sf' values and `x' is an integral value. C code MIPS instruction ! `a + b' `add.ps' ! `a - b' `sub.ps' ! `-a' `neg.ps' ! `a * b' `mul.ps' ! `a * b + c' `madd.ps' ! `a * b - c' `msub.ps' ! `-(a * b + c)' `nmadd.ps' ! `-(a * b - c)' `nmsub.ps' ! `x ? a : b' `movn.ps'/`movz.ps' Note that the multiply-accumulate instructions can be disabled using ! the command-line option `-mno-fused-madd'.  File: gcc.info, Node: Paired-Single Built-in Functions, Next: MIPS-3D Built-in Functions, Prev: Paired-Single Arithmetic, Up: MIPS Loongson Built-in Functions *************** File: gcc.info, Node: Paired-Single Bui *** 37879,37944 **** .......................................... The following paired-single functions map directly to a particular MIPS ! instruction. Please refer to the architecture specification for details ! on what each instruction does. ! 'v2sf __builtin_mips_pll_ps (v2sf, v2sf)' ! Pair lower lower ('pll.ps'). ! 'v2sf __builtin_mips_pul_ps (v2sf, v2sf)' ! Pair upper lower ('pul.ps'). ! 'v2sf __builtin_mips_plu_ps (v2sf, v2sf)' ! Pair lower upper ('plu.ps'). ! 'v2sf __builtin_mips_puu_ps (v2sf, v2sf)' ! Pair upper upper ('puu.ps'). ! 'v2sf __builtin_mips_cvt_ps_s (float, float)' ! Convert pair to paired single ('cvt.ps.s'). ! 'float __builtin_mips_cvt_s_pl (v2sf)' ! Convert pair lower to single ('cvt.s.pl'). ! 'float __builtin_mips_cvt_s_pu (v2sf)' ! Convert pair upper to single ('cvt.s.pu'). ! 'v2sf __builtin_mips_abs_ps (v2sf)' ! Absolute value ('abs.ps'). ! 'v2sf __builtin_mips_alnv_ps (v2sf, v2sf, int)' ! Align variable ('alnv.ps'). _Note:_ The value of the third parameter must be 0 or 4 modulo 8, ! otherwise the result is unpredictable. Please read the instruction ! description for details. The following multi-instruction functions are also available. In each ! case, COND can be any of the 16 floating-point conditions: 'f', 'un', ! 'eq', 'ueq', 'olt', 'ult', 'ole', 'ule', 'sf', 'ngle', 'seq', 'ngl', ! 'lt', 'nge', 'le' or 'ngt'. ! 'v2sf __builtin_mips_movt_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! 'v2sf __builtin_mips_movf_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! Conditional move based on floating-point comparison ('c.COND.ps', ! 'movt.ps'/'movf.ps'). ! The 'movt' functions return the value X computed by: c.COND.ps CC,A,B mov.ps X,C movt.ps X,D,CC ! The 'movf' functions are similar but use 'movf.ps' instead of ! 'movt.ps'. ! 'int __builtin_mips_upper_c_COND_ps (v2sf A, v2sf B)' ! 'int __builtin_mips_lower_c_COND_ps (v2sf A, v2sf B)' ! Comparison of two paired-single values ('c.COND.ps', ! 'bc1t'/'bc1f'). ! These functions compare A and B using 'c.COND.ps' and return either ! the upper or lower half of the result. For example: v2sf a, b; if (__builtin_mips_upper_c_eq_ps (a, b)) --- 38274,38339 ---- .......................................... The following paired-single functions map directly to a particular MIPS ! instruction. Please refer to the architecture specification for ! details on what each instruction does. ! `v2sf __builtin_mips_pll_ps (v2sf, v2sf)' ! Pair lower lower (`pll.ps'). ! `v2sf __builtin_mips_pul_ps (v2sf, v2sf)' ! Pair upper lower (`pul.ps'). ! `v2sf __builtin_mips_plu_ps (v2sf, v2sf)' ! Pair lower upper (`plu.ps'). ! `v2sf __builtin_mips_puu_ps (v2sf, v2sf)' ! Pair upper upper (`puu.ps'). ! `v2sf __builtin_mips_cvt_ps_s (float, float)' ! Convert pair to paired single (`cvt.ps.s'). ! `float __builtin_mips_cvt_s_pl (v2sf)' ! Convert pair lower to single (`cvt.s.pl'). ! `float __builtin_mips_cvt_s_pu (v2sf)' ! Convert pair upper to single (`cvt.s.pu'). ! `v2sf __builtin_mips_abs_ps (v2sf)' ! Absolute value (`abs.ps'). ! `v2sf __builtin_mips_alnv_ps (v2sf, v2sf, int)' ! Align variable (`alnv.ps'). _Note:_ The value of the third parameter must be 0 or 4 modulo 8, ! otherwise the result is unpredictable. Please read the ! instruction description for details. The following multi-instruction functions are also available. In each ! case, COND can be any of the 16 floating-point conditions: `f', `un', ! `eq', `ueq', `olt', `ult', `ole', `ule', `sf', `ngle', `seq', `ngl', ! `lt', `nge', `le' or `ngt'. ! `v2sf __builtin_mips_movt_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! `v2sf __builtin_mips_movf_c_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! Conditional move based on floating-point comparison (`c.COND.ps', ! `movt.ps'/`movf.ps'). ! The `movt' functions return the value X computed by: c.COND.ps CC,A,B mov.ps X,C movt.ps X,D,CC ! The `movf' functions are similar but use `movf.ps' instead of ! `movt.ps'. ! `int __builtin_mips_upper_c_COND_ps (v2sf A, v2sf B)' ! `int __builtin_mips_lower_c_COND_ps (v2sf A, v2sf B)' ! Comparison of two paired-single values (`c.COND.ps', ! `bc1t'/`bc1f'). ! These functions compare A and B using `c.COND.ps' and return ! either the upper or lower half of the result. For example: v2sf a, b; if (__builtin_mips_upper_c_eq_ps (a, b)) *************** File: gcc.info, Node: MIPS-3D Built-in *** 37960,38017 **** The MIPS-3D Application-Specific Extension (ASE) includes additional paired-single instructions that are designed to improve the performance of 3D graphics operations. Support for these instructions is controlled ! by the '-mips3d' command-line option. The functions listed below map directly to a particular MIPS-3D instruction. Please refer to the architecture specification for more details on what each instruction does. ! 'v2sf __builtin_mips_addr_ps (v2sf, v2sf)' ! Reduction add ('addr.ps'). ! 'v2sf __builtin_mips_mulr_ps (v2sf, v2sf)' ! Reduction multiply ('mulr.ps'). ! 'v2sf __builtin_mips_cvt_pw_ps (v2sf)' ! Convert paired single to paired word ('cvt.pw.ps'). ! 'v2sf __builtin_mips_cvt_ps_pw (v2sf)' ! Convert paired word to paired single ('cvt.ps.pw'). ! 'float __builtin_mips_recip1_s (float)' ! 'double __builtin_mips_recip1_d (double)' ! 'v2sf __builtin_mips_recip1_ps (v2sf)' ! Reduced-precision reciprocal (sequence step 1) ('recip1.FMT'). ! 'float __builtin_mips_recip2_s (float, float)' ! 'double __builtin_mips_recip2_d (double, double)' ! 'v2sf __builtin_mips_recip2_ps (v2sf, v2sf)' ! Reduced-precision reciprocal (sequence step 2) ('recip2.FMT'). ! 'float __builtin_mips_rsqrt1_s (float)' ! 'double __builtin_mips_rsqrt1_d (double)' ! 'v2sf __builtin_mips_rsqrt1_ps (v2sf)' Reduced-precision reciprocal square root (sequence step 1) ! ('rsqrt1.FMT'). ! 'float __builtin_mips_rsqrt2_s (float, float)' ! 'double __builtin_mips_rsqrt2_d (double, double)' ! 'v2sf __builtin_mips_rsqrt2_ps (v2sf, v2sf)' Reduced-precision reciprocal square root (sequence step 2) ! ('rsqrt2.FMT'). The following multi-instruction functions are also available. In each ! case, COND can be any of the 16 floating-point conditions: 'f', 'un', ! 'eq', 'ueq', 'olt', 'ult', 'ole', 'ule', 'sf', 'ngle', 'seq', 'ngl', ! 'lt', 'nge', 'le' or 'ngt'. ! 'int __builtin_mips_cabs_COND_s (float A, float B)' ! 'int __builtin_mips_cabs_COND_d (double A, double B)' ! Absolute comparison of two scalar values ('cabs.COND.FMT', ! 'bc1t'/'bc1f'). ! These functions compare A and B using 'cabs.COND.s' or ! 'cabs.COND.d' and return the result as a boolean value. For example: float a, b; --- 38355,38412 ---- The MIPS-3D Application-Specific Extension (ASE) includes additional paired-single instructions that are designed to improve the performance of 3D graphics operations. Support for these instructions is controlled ! by the `-mips3d' command-line option. The functions listed below map directly to a particular MIPS-3D instruction. Please refer to the architecture specification for more details on what each instruction does. ! `v2sf __builtin_mips_addr_ps (v2sf, v2sf)' ! Reduction add (`addr.ps'). ! `v2sf __builtin_mips_mulr_ps (v2sf, v2sf)' ! Reduction multiply (`mulr.ps'). ! `v2sf __builtin_mips_cvt_pw_ps (v2sf)' ! Convert paired single to paired word (`cvt.pw.ps'). ! `v2sf __builtin_mips_cvt_ps_pw (v2sf)' ! Convert paired word to paired single (`cvt.ps.pw'). ! `float __builtin_mips_recip1_s (float)' ! `double __builtin_mips_recip1_d (double)' ! `v2sf __builtin_mips_recip1_ps (v2sf)' ! Reduced-precision reciprocal (sequence step 1) (`recip1.FMT'). ! `float __builtin_mips_recip2_s (float, float)' ! `double __builtin_mips_recip2_d (double, double)' ! `v2sf __builtin_mips_recip2_ps (v2sf, v2sf)' ! Reduced-precision reciprocal (sequence step 2) (`recip2.FMT'). ! `float __builtin_mips_rsqrt1_s (float)' ! `double __builtin_mips_rsqrt1_d (double)' ! `v2sf __builtin_mips_rsqrt1_ps (v2sf)' Reduced-precision reciprocal square root (sequence step 1) ! (`rsqrt1.FMT'). ! `float __builtin_mips_rsqrt2_s (float, float)' ! `double __builtin_mips_rsqrt2_d (double, double)' ! `v2sf __builtin_mips_rsqrt2_ps (v2sf, v2sf)' Reduced-precision reciprocal square root (sequence step 2) ! (`rsqrt2.FMT'). The following multi-instruction functions are also available. In each ! case, COND can be any of the 16 floating-point conditions: `f', `un', ! `eq', `ueq', `olt', `ult', `ole', `ule', `sf', `ngle', `seq', `ngl', ! `lt', `nge', `le' or `ngt'. ! `int __builtin_mips_cabs_COND_s (float A, float B)' ! `int __builtin_mips_cabs_COND_d (double A, double B)' ! Absolute comparison of two scalar values (`cabs.COND.FMT', ! `bc1t'/`bc1f'). ! These functions compare A and B using `cabs.COND.s' or ! `cabs.COND.d' and return the result as a boolean value. For example: float a, b; *************** case, COND can be any of the 16 floating *** 38020,38031 **** else false (); ! 'int __builtin_mips_upper_cabs_COND_ps (v2sf A, v2sf B)' ! 'int __builtin_mips_lower_cabs_COND_ps (v2sf A, v2sf B)' ! Absolute comparison of two paired-single values ('cabs.COND.ps', ! 'bc1t'/'bc1f'). ! These functions compare A and B using 'cabs.COND.ps' and return either the upper or lower half of the result. For example: v2sf a, b; --- 38415,38426 ---- else false (); ! `int __builtin_mips_upper_cabs_COND_ps (v2sf A, v2sf B)' ! `int __builtin_mips_lower_cabs_COND_ps (v2sf A, v2sf B)' ! Absolute comparison of two paired-single values (`cabs.COND.ps', ! `bc1t'/`bc1f'). ! These functions compare A and B using `cabs.COND.ps' and return either the upper or lower half of the result. For example: v2sf a, b; *************** case, COND can be any of the 16 floating *** 38039,38069 **** else lower_halves_are_unequal (); ! 'v2sf __builtin_mips_movt_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! 'v2sf __builtin_mips_movf_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! Conditional move based on absolute comparison ('cabs.COND.ps', ! 'movt.ps'/'movf.ps'). ! The 'movt' functions return the value X computed by: cabs.COND.ps CC,A,B mov.ps X,C movt.ps X,D,CC ! The 'movf' functions are similar but use 'movf.ps' instead of ! 'movt.ps'. ! 'int __builtin_mips_any_c_COND_ps (v2sf A, v2sf B)' ! 'int __builtin_mips_all_c_COND_ps (v2sf A, v2sf B)' ! 'int __builtin_mips_any_cabs_COND_ps (v2sf A, v2sf B)' ! 'int __builtin_mips_all_cabs_COND_ps (v2sf A, v2sf B)' ! Comparison of two paired-single values ('c.COND.ps'/'cabs.COND.ps', ! 'bc1any2t'/'bc1any2f'). ! These functions compare A and B using 'c.COND.ps' or ! 'cabs.COND.ps'. The 'any' forms return true if either result is ! true and the 'all' forms return true if both results are true. For ! example: v2sf a, b; if (__builtin_mips_any_c_eq_ps (a, b)) --- 38434,38464 ---- else lower_halves_are_unequal (); ! `v2sf __builtin_mips_movt_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! `v2sf __builtin_mips_movf_cabs_COND_ps (v2sf A, v2sf B, v2sf C, v2sf D)' ! Conditional move based on absolute comparison (`cabs.COND.ps', ! `movt.ps'/`movf.ps'). ! The `movt' functions return the value X computed by: cabs.COND.ps CC,A,B mov.ps X,C movt.ps X,D,CC ! The `movf' functions are similar but use `movf.ps' instead of ! `movt.ps'. ! `int __builtin_mips_any_c_COND_ps (v2sf A, v2sf B)' ! `int __builtin_mips_all_c_COND_ps (v2sf A, v2sf B)' ! `int __builtin_mips_any_cabs_COND_ps (v2sf A, v2sf B)' ! `int __builtin_mips_all_cabs_COND_ps (v2sf A, v2sf B)' ! Comparison of two paired-single values (`c.COND.ps'/`cabs.COND.ps', ! `bc1any2t'/`bc1any2f'). ! These functions compare A and B using `c.COND.ps' or ! `cabs.COND.ps'. The `any' forms return true if either result is ! true and the `all' forms return true if both results are true. ! For example: v2sf a, b; if (__builtin_mips_any_c_eq_ps (a, b)) *************** case, COND can be any of the 16 floating *** 38076,38092 **** else one_is_false (); ! 'int __builtin_mips_any_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' ! 'int __builtin_mips_all_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' ! 'int __builtin_mips_any_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' ! 'int __builtin_mips_all_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' Comparison of four paired-single values ! ('c.COND.ps'/'cabs.COND.ps', 'bc1any4t'/'bc1any4f'). ! These functions use 'c.COND.ps' or 'cabs.COND.ps' to compare A with ! B and to compare C with D. The 'any' forms return true if any of ! the four results are true and the 'all' forms return true if all ! four results are true. For example: v2sf a, b, c, d; if (__builtin_mips_any_c_eq_4s (a, b, c, d)) --- 38471,38487 ---- else one_is_false (); ! `int __builtin_mips_any_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' ! `int __builtin_mips_all_c_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' ! `int __builtin_mips_any_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' ! `int __builtin_mips_all_cabs_COND_4s (v2sf A, v2sf B, v2sf C, v2sf D)' Comparison of four paired-single values ! (`c.COND.ps'/`cabs.COND.ps', `bc1any4t'/`bc1any4f'). ! These functions use `c.COND.ps' or `cabs.COND.ps' to compare A ! with B and to compare C with D. The `any' forms return true if ! any of the four results are true and the `all' forms return true ! if all four results are true. For example: v2sf a, b, c, d; if (__builtin_mips_any_c_eq_4s (a, b, c, d)) *************** File: gcc.info, Node: Other MIPS Built- *** 38107,38125 **** GCC provides other MIPS-specific built-in functions: ! 'void __builtin_mips_cache (int OP, const volatile void *ADDR)' ! Insert a 'cache' instruction with operands OP and ADDR. GCC ! defines the preprocessor macro '___GCC_HAVE_BUILTIN_MIPS_CACHE' when this function is available. ! 'unsigned int __builtin_mips_get_fcsr (void)' ! 'void __builtin_mips_set_fcsr (unsigned int VALUE)' Get and set the contents of the floating-point control and status register (FPU control register 31). These functions are only available in hard-float code but can be called in both MIPS16 and non-MIPS16 contexts. ! '__builtin_mips_set_fcsr' can be used to change any bit of the register except the condition codes, which GCC assumes are preserved. --- 38502,38520 ---- GCC provides other MIPS-specific built-in functions: ! `void __builtin_mips_cache (int OP, const volatile void *ADDR)' ! Insert a `cache' instruction with operands OP and ADDR. GCC ! defines the preprocessor macro `___GCC_HAVE_BUILTIN_MIPS_CACHE' when this function is available. ! `unsigned int __builtin_mips_get_fcsr (void)' ! `void __builtin_mips_set_fcsr (unsigned int VALUE)' Get and set the contents of the floating-point control and status register (FPU control register 31). These functions are only available in hard-float code but can be called in both MIPS16 and non-MIPS16 contexts. ! `__builtin_mips_set_fcsr' can be used to change any bit of the register except the condition codes, which GCC assumes are preserved. *************** File: gcc.info, Node: MSP430 Built-in F *** 38129,38150 **** 6.59.16 MSP430 Built-in Functions --------------------------------- ! GCC provides a couple of special builtin functions to aid in the writing ! of interrupt handlers in C. ! '__bic_SR_register_on_exit (int MASK)' This clears the indicated bits in the saved copy of the status register currently residing on the stack. This only works inside ! interrupt handlers and the changes to the status register will only ! take affect once the handler returns. ! '__bis_SR_register_on_exit (int MASK)' This sets the indicated bits in the saved copy of the status register currently residing on the stack. This only works inside ! interrupt handlers and the changes to the status register will only ! take affect once the handler returns. ! '__delay_cycles (long long CYCLES)' This inserts an instruction sequence that takes exactly CYCLES cycles (between 0 and about 17E9) to complete. The inserted sequence may use jumps, loops, or no-ops, and does not interfere --- 38524,38545 ---- 6.59.16 MSP430 Built-in Functions --------------------------------- ! GCC provides a couple of special builtin functions to aid in the ! writing of interrupt handlers in C. ! `__bic_SR_register_on_exit (int MASK)' This clears the indicated bits in the saved copy of the status register currently residing on the stack. This only works inside ! interrupt handlers and the changes to the status register will ! only take affect once the handler returns. ! `__bis_SR_register_on_exit (int MASK)' This sets the indicated bits in the saved copy of the status register currently residing on the stack. This only works inside ! interrupt handlers and the changes to the status register will ! only take affect once the handler returns. ! `__delay_cycles (long long CYCLES)' This inserts an instruction sequence that takes exactly CYCLES cycles (between 0 and about 17E9) to complete. The inserted sequence may use jumps, loops, or no-ops, and does not interfere *************** File: gcc.info, Node: picoChip Built-in *** 38195,38227 **** GCC provides an interface to selected machine instructions from the picoChip instruction set. ! 'int __builtin_sbc (int VALUE)' Sign bit count. Return the number of consecutive bits in VALUE ! that have the same value as the sign bit. The result is the number ! of leading sign bits minus one, giving the number of redundant sign ! bits in VALUE. ! 'int __builtin_byteswap (int VALUE)' ! Byte swap. Return the result of swapping the upper and lower bytes ! of VALUE. ! 'int __builtin_brev (int VALUE)' Bit reversal. Return the result of reversing the bits in VALUE. Bit 15 is swapped with bit 0, bit 14 is swapped with bit 1, and so on. ! 'int __builtin_adds (int X, int Y)' Saturating addition. Return the result of adding X and Y, storing the value 32767 if the result overflows. ! 'int __builtin_subs (int X, int Y)' ! Saturating subtraction. Return the result of subtracting Y from X, ! storing the value -32768 if the result overflows. ! 'void __builtin_halt (void)' Halt. The processor stops execution. This built-in is useful for implementing assertions.  File: gcc.info, Node: PowerPC Built-in Functions, Next: PowerPC AltiVec/VSX Built-in Functions, Prev: picoChip Built-in Functions, Up: Target Builtins --- 38590,38623 ---- GCC provides an interface to selected machine instructions from the picoChip instruction set. ! `int __builtin_sbc (int VALUE)' Sign bit count. Return the number of consecutive bits in VALUE ! that have the same value as the sign bit. The result is the ! number of leading sign bits minus one, giving the number of ! redundant sign bits in VALUE. ! `int __builtin_byteswap (int VALUE)' ! Byte swap. Return the result of swapping the upper and lower ! bytes of VALUE. ! `int __builtin_brev (int VALUE)' Bit reversal. Return the result of reversing the bits in VALUE. Bit 15 is swapped with bit 0, bit 14 is swapped with bit 1, and so on. ! `int __builtin_adds (int X, int Y)' Saturating addition. Return the result of adding X and Y, storing the value 32767 if the result overflows. ! `int __builtin_subs (int X, int Y)' ! Saturating subtraction. Return the result of subtracting Y from ! X, storing the value -32768 if the result overflows. ! `void __builtin_halt (void)' Halt. The processor stops execution. This built-in is useful for implementing assertions. +  File: gcc.info, Node: PowerPC Built-in Functions, Next: PowerPC AltiVec/VSX Built-in Functions, Prev: picoChip Built-in Functions, Up: Target Builtins *************** The following built-in functions are alw *** 38232,38274 **** check the PowerPC target platform type: -- Built-in Function: void __builtin_cpu_init (void) ! This function is a 'nop' on the PowerPC platform and is included solely to maintain API compatibility with the x86 builtins. -- Built-in Function: int __builtin_cpu_is (const char *CPUNAME) ! This function returns a value of '1' if the run-time CPU is of type ! CPUNAME and returns '0' otherwise. The following CPU names can be detected: ! 'power9' IBM POWER9 Server CPU. ! 'power8' IBM POWER8 Server CPU. ! 'power7' IBM POWER7 Server CPU. ! 'power6x' IBM POWER6 Server CPU (RAW mode). ! 'power6' IBM POWER6 Server CPU (Architected mode). ! 'power5+' IBM POWER5+ Server CPU. ! 'power5' IBM POWER5 Server CPU. ! 'ppc970' IBM 970 Server CPU (ie, Apple G5). ! 'power4' IBM POWER4 Server CPU. ! 'ppca2' IBM A2 64-bit Embedded CPU ! 'ppc476' IBM PowerPC 476FP 32-bit Embedded CPU. ! 'ppc464' IBM PowerPC 464 32-bit Embedded CPU. ! 'ppc440' PowerPC 440 32-bit Embedded CPU. ! 'ppc405' PowerPC 405 32-bit Embedded CPU. ! 'ppc-cell-be' IBM PowerPC Cell Broadband Engine Architecture CPU. Here is an example: --- 38628,38684 ---- check the PowerPC target platform type: -- Built-in Function: void __builtin_cpu_init (void) ! This function is a `nop' on the PowerPC platform and is included solely to maintain API compatibility with the x86 builtins. -- Built-in Function: int __builtin_cpu_is (const char *CPUNAME) ! This function returns a value of `1' if the run-time CPU is of type ! CPUNAME and returns `0' otherwise. The following CPU names can be detected: ! `power9' IBM POWER9 Server CPU. ! ! `power8' IBM POWER8 Server CPU. ! ! `power7' IBM POWER7 Server CPU. ! ! `power6x' IBM POWER6 Server CPU (RAW mode). ! ! `power6' IBM POWER6 Server CPU (Architected mode). ! ! `power5+' IBM POWER5+ Server CPU. ! ! `power5' IBM POWER5 Server CPU. ! ! `ppc970' IBM 970 Server CPU (ie, Apple G5). ! ! `power4' IBM POWER4 Server CPU. ! ! `ppca2' IBM A2 64-bit Embedded CPU ! ! `ppc476' IBM PowerPC 476FP 32-bit Embedded CPU. ! ! `ppc464' IBM PowerPC 464 32-bit Embedded CPU. ! ! `ppc440' PowerPC 440 32-bit Embedded CPU. ! ! `ppc405' PowerPC 405 32-bit Embedded CPU. ! ! `ppc-cell-be' IBM PowerPC Cell Broadband Engine Architecture CPU. Here is an example: *************** check the PowerPC target platform type: *** 38282,38368 **** } -- Built-in Function: int __builtin_cpu_supports (const char *FEATURE) ! This function returns a value of '1' if the run-time CPU supports ! the HWCAP feature FEATURE and returns '0' otherwise. The following features can be detected: ! '4xxmac' 4xx CPU has a Multiply Accumulator. ! 'altivec' CPU has a SIMD/Vector Unit. ! 'arch_2_05' CPU supports ISA 2.05 (eg, POWER6) ! 'arch_2_06' CPU supports ISA 2.06 (eg, POWER7) ! 'arch_2_07' CPU supports ISA 2.07 (eg, POWER8) ! 'arch_3_00' CPU supports ISA 3.00 (eg, POWER9) ! 'archpmu' CPU supports the set of compatible performance monitoring events. ! 'booke' CPU supports the Embedded ISA category. ! 'cellbe' CPU has a CELL broadband engine. ! 'dfp' CPU has a decimal floating point unit. ! 'dscr' CPU supports the data stream control register. ! 'ebb' CPU supports event base branching. ! 'efpdouble' CPU has a SPE double precision floating point unit. ! 'efpsingle' CPU has a SPE single precision floating point unit. ! 'fpu' CPU has a floating point unit. ! 'htm' CPU has hardware transaction memory instructions. ! 'htm-nosc' Kernel aborts hardware transactions when a syscall is made. ! 'ic_snoop' CPU supports icache snooping capabilities. ! 'ieee128' CPU supports 128-bit IEEE binary floating point instructions. ! 'isel' CPU supports the integer select instruction. ! 'mmu' CPU has a memory management unit. ! 'notb' CPU does not have a timebase (eg, 601 and 403gx). ! 'pa6t' CPU supports the PA Semi 6T CORE ISA. ! 'power4' CPU supports ISA 2.00 (eg, POWER4) ! 'power5' CPU supports ISA 2.02 (eg, POWER5) ! 'power5+' CPU supports ISA 2.03 (eg, POWER5+) ! 'power6x' ! CPU supports ISA 2.05 (eg, POWER6) extended opcodes mffgpr and ! mftgpr. ! 'ppc32' CPU supports 32-bit mode execution. ! 'ppc601' CPU supports the old POWER ISA (eg, 601) ! 'ppc64' CPU supports 64-bit mode execution. ! 'ppcle' CPU supports a little-endian mode that uses address swizzling. ! 'smt' CPU support simultaneous multi-threading. ! 'spe' CPU has a signal processing extension unit. ! 'tar' CPU supports the target address register. ! 'true_le' CPU supports true little-endian mode. ! 'ucache' CPU has unified I/D cache. ! 'vcrypto' CPU supports the vector cryptography instructions. ! 'vsx' CPU supports the vector-scalar extension. Here is an example: --- 38692,38815 ---- } -- Built-in Function: int __builtin_cpu_supports (const char *FEATURE) ! This function returns a value of `1' if the run-time CPU supports ! the HWCAP feature FEATURE and returns `0' otherwise. The following features can be detected: ! `4xxmac' 4xx CPU has a Multiply Accumulator. ! ! `altivec' CPU has a SIMD/Vector Unit. ! ! `arch_2_05' CPU supports ISA 2.05 (eg, POWER6) ! ! `arch_2_06' CPU supports ISA 2.06 (eg, POWER7) ! ! `arch_2_07' CPU supports ISA 2.07 (eg, POWER8) ! ! `arch_3_00' CPU supports ISA 3.00 (eg, POWER9) ! ! `archpmu' CPU supports the set of compatible performance monitoring events. ! ! `booke' CPU supports the Embedded ISA category. ! ! `cellbe' CPU has a CELL broadband engine. ! ! `dfp' CPU has a decimal floating point unit. ! ! `dscr' CPU supports the data stream control register. ! ! `ebb' CPU supports event base branching. ! ! `efpdouble' CPU has a SPE double precision floating point unit. ! ! `efpsingle' CPU has a SPE single precision floating point unit. ! ! `fpu' CPU has a floating point unit. ! ! `htm' CPU has hardware transaction memory instructions. ! ! `htm-nosc' Kernel aborts hardware transactions when a syscall is made. ! ! `ic_snoop' CPU supports icache snooping capabilities. ! ! `ieee128' CPU supports 128-bit IEEE binary floating point instructions. ! ! `isel' CPU supports the integer select instruction. ! ! `mmu' CPU has a memory management unit. ! ! `notb' CPU does not have a timebase (eg, 601 and 403gx). ! ! `pa6t' CPU supports the PA Semi 6T CORE ISA. ! ! `power4' CPU supports ISA 2.00 (eg, POWER4) ! ! `power5' CPU supports ISA 2.02 (eg, POWER5) ! ! `power5+' CPU supports ISA 2.03 (eg, POWER5+) ! ! `power6x' ! CPU supports ISA 2.05 (eg, POWER6) extended opcodes mffgpr ! and mftgpr. ! ! `ppc32' CPU supports 32-bit mode execution. ! ! `ppc601' CPU supports the old POWER ISA (eg, 601) ! ! `ppc64' CPU supports 64-bit mode execution. ! ! `ppcle' CPU supports a little-endian mode that uses address swizzling. ! ! `smt' CPU support simultaneous multi-threading. ! ! `spe' CPU has a signal processing extension unit. ! ! `tar' CPU supports the target address register. ! ! `true_le' CPU supports true little-endian mode. ! ! `ucache' CPU has unified I/D cache. ! ! `vcrypto' CPU supports the vector cryptography instructions. ! ! `vsx' CPU supports the vector-scalar extension. Here is an example: *************** processors: *** 38386,38438 **** double __builtin_unpack_longdouble (long double, int); long double __builtin_pack_longdouble (double, double); ! The 'vec_rsqrt', '__builtin_rsqrt', and '__builtin_rsqrtf' functions generate multiple instructions to implement the reciprocal sqrt functionality using reciprocal sqrt estimate instructions. ! The '__builtin_recipdiv', and '__builtin_recipdivf' functions generate multiple instructions to implement division using the reciprocal estimate instructions. ! The '__builtin_ppc_get_timebase' and '__builtin_ppc_mftb' functions generate instructions to read the Time Base Register. The ! '__builtin_ppc_get_timebase' function may generate multiple instructions ! and always returns the 64 bits of the Time Base Register. The ! '__builtin_ppc_mftb' function always generates one instruction and returns the Time Base Register value as an unsigned long, throwing away the most significant word on 32-bit environments. Additional built-in functions are available for the 64-bit PowerPC family of processors, for efficient use of 128-bit floating point ! ('__float128') values. The following floating-point built-in functions are available with ! '-mfloat128' and Altivec support. All of them implement the function that is part of the name. __float128 __builtin_fabsq (__float128) __float128 __builtin_copysignq (__float128, __float128) ! The following built-in functions are available with '-mfloat128' and Altivec support. ! '__float128 __builtin_infq (void)' ! Similar to '__builtin_inf', except the return type is '__float128'. ! '__float128 __builtin_huge_valq (void)' ! Similar to '__builtin_huge_val', except the return type is ! '__float128'. ! '__float128 __builtin_nanq (void)' ! Similar to '__builtin_nan', except the return type is '__float128'. ! '__float128 __builtin_nansq (void)' ! Similar to '__builtin_nans', except the return type is ! '__float128'. The following built-in functions are available for the PowerPC family ! of processors, starting with ISA 2.06 or later ('-mcpu=power7' or ! '-mpopcntd'): long __builtin_bpermd (long, long); int __builtin_divwe (int, int); int __builtin_divweo (int, int); --- 38833,38885 ---- double __builtin_unpack_longdouble (long double, int); long double __builtin_pack_longdouble (double, double); ! The `vec_rsqrt', `__builtin_rsqrt', and `__builtin_rsqrtf' functions generate multiple instructions to implement the reciprocal sqrt functionality using reciprocal sqrt estimate instructions. ! The `__builtin_recipdiv', and `__builtin_recipdivf' functions generate multiple instructions to implement division using the reciprocal estimate instructions. ! The `__builtin_ppc_get_timebase' and `__builtin_ppc_mftb' functions generate instructions to read the Time Base Register. The ! `__builtin_ppc_get_timebase' function may generate multiple ! instructions and always returns the 64 bits of the Time Base Register. ! The `__builtin_ppc_mftb' function always generates one instruction and returns the Time Base Register value as an unsigned long, throwing away the most significant word on 32-bit environments. Additional built-in functions are available for the 64-bit PowerPC family of processors, for efficient use of 128-bit floating point ! (`__float128') values. The following floating-point built-in functions are available with ! `-mfloat128' and Altivec support. All of them implement the function that is part of the name. __float128 __builtin_fabsq (__float128) __float128 __builtin_copysignq (__float128, __float128) ! The following built-in functions are available with `-mfloat128' and Altivec support. ! `__float128 __builtin_infq (void)' ! Similar to `__builtin_inf', except the return type is `__float128'. ! `__float128 __builtin_huge_valq (void)' ! Similar to `__builtin_huge_val', except the return type is ! `__float128'. ! `__float128 __builtin_nanq (void)' ! Similar to `__builtin_nan', except the return type is `__float128'. ! `__float128 __builtin_nansq (void)' ! Similar to `__builtin_nans', except the return type is ! `__float128'. The following built-in functions are available for the PowerPC family ! of processors, starting with ISA 2.06 or later (`-mcpu=power7' or ! `-mpopcntd'): long __builtin_bpermd (long, long); int __builtin_divwe (int, int); int __builtin_divweo (int, int); *************** of processors, starting with ISA 2.06 or *** 38446,38457 **** unsigned int cbcdtd (unsigned int); unsigned int addg6s (unsigned int, unsigned int); ! The '__builtin_divde', '__builtin_divdeo', '__builtin_divdeu', ! '__builtin_divdeou' functions require a 64-bit environment support ISA 2.06 or later. The following built-in functions are available for the PowerPC family ! of processors, starting with ISA 3.0 or later ('-mcpu=power9'): long long __builtin_darn (void); long long __builtin_darn_raw (void); int __builtin_darn_32 (void); --- 38893,38904 ---- unsigned int cbcdtd (unsigned int); unsigned int addg6s (unsigned int, unsigned int); ! The `__builtin_divde', `__builtin_divdeo', `__builtin_divdeu', ! `__builtin_divdeou' functions require a 64-bit environment support ISA 2.06 or later. The following built-in functions are available for the PowerPC family ! of processors, starting with ISA 3.0 or later (`-mcpu=power9'): long long __builtin_darn (void); long long __builtin_darn_raw (void); int __builtin_darn_32 (void); *************** of processors, starting with ISA 3.0 or *** 38476,38526 **** int __builtin_dfp_dtstsfi_ov_dd (unsigned int comparison, _Decimal64 value); int __builtin_dfp_dtstsfi_ov_td (unsigned int comparison, _Decimal128 value); ! The '__builtin_darn' and '__builtin_darn_raw' functions require a ! 64-bit environment supporting ISA 3.0 or later. The '__builtin_darn' function provides a 64-bit conditioned random number. The ! '__builtin_darn_raw' function provides a 64-bit raw random number. The ! '__builtin_darn_32' function provides a 32-bit random number. ! The '__builtin_dfp_dtstsfi_lt' function returns a non-zero value if and ! only if the number of signficant digits of its 'value' argument is less ! than its 'comparison' argument. The '__builtin_dfp_dtstsfi_lt_dd' and ! '__builtin_dfp_dtstsfi_lt_td' functions behave similarly, but require ! that the type of the 'value' argument be '__Decimal64' and ! '__Decimal128' respectively. ! The '__builtin_dfp_dtstsfi_gt' function returns a non-zero value if and ! only if the number of signficant digits of its 'value' argument is ! greater than its 'comparison' argument. The ! '__builtin_dfp_dtstsfi_gt_dd' and '__builtin_dfp_dtstsfi_gt_td' ! functions behave similarly, but require that the type of the 'value' ! argument be '__Decimal64' and '__Decimal128' respectively. ! The '__builtin_dfp_dtstsfi_eq' function returns a non-zero value if and ! only if the number of signficant digits of its 'value' argument equals ! its 'comparison' argument. The '__builtin_dfp_dtstsfi_eq_dd' and ! '__builtin_dfp_dtstsfi_eq_td' functions behave similarly, but require ! that the type of the 'value' argument be '__Decimal64' and ! '__Decimal128' respectively. ! The '__builtin_dfp_dtstsfi_ov' function returns a non-zero value if and ! only if its 'value' argument has an undefined number of significant ! digits, such as when 'value' is an encoding of 'NaN'. The ! '__builtin_dfp_dtstsfi_ov_dd' and '__builtin_dfp_dtstsfi_ov_td' ! functions behave similarly, but require that the type of the 'value' ! argument be '__Decimal64' and '__Decimal128' respectively. The following built-in functions are available for the PowerPC family ! of processors when hardware decimal floating point ('-mhard-dfp') is available: ! _Decimal64 __builtin_dxex (_Decimal64); ! _Decimal128 __builtin_dxexq (_Decimal128); _Decimal64 __builtin_ddedpd (int, _Decimal64); _Decimal128 __builtin_ddedpdq (int, _Decimal128); _Decimal64 __builtin_denbcd (int, _Decimal64); _Decimal128 __builtin_denbcdq (int, _Decimal128); ! _Decimal64 __builtin_diex (_Decimal64, _Decimal64); ! _Decimal128 _builtin_diexq (_Decimal128, _Decimal128); _Decimal64 __builtin_dscli (_Decimal64, int); _Decimal128 __builtin_dscliq (_Decimal128, int); _Decimal64 __builtin_dscri (_Decimal64, int); --- 38923,38973 ---- int __builtin_dfp_dtstsfi_ov_dd (unsigned int comparison, _Decimal64 value); int __builtin_dfp_dtstsfi_ov_td (unsigned int comparison, _Decimal128 value); ! The `__builtin_darn' and `__builtin_darn_raw' functions require a ! 64-bit environment supporting ISA 3.0 or later. The `__builtin_darn' function provides a 64-bit conditioned random number. The ! `__builtin_darn_raw' function provides a 64-bit raw random number. The ! `__builtin_darn_32' function provides a 32-bit random number. ! The `__builtin_dfp_dtstsfi_lt' function returns a non-zero value if ! and only if the number of signficant digits of its `value' argument is ! less than its `comparison' argument. The `__builtin_dfp_dtstsfi_lt_dd' ! and `__builtin_dfp_dtstsfi_lt_td' functions behave similarly, but ! require that the type of the `value' argument be `__Decimal64' and ! `__Decimal128' respectively. ! The `__builtin_dfp_dtstsfi_gt' function returns a non-zero value if ! and only if the number of signficant digits of its `value' argument is ! greater than its `comparison' argument. The ! `__builtin_dfp_dtstsfi_gt_dd' and `__builtin_dfp_dtstsfi_gt_td' ! functions behave similarly, but require that the type of the `value' ! argument be `__Decimal64' and `__Decimal128' respectively. ! The `__builtin_dfp_dtstsfi_eq' function returns a non-zero value if ! and only if the number of signficant digits of its `value' argument ! equals its `comparison' argument. The `__builtin_dfp_dtstsfi_eq_dd' and ! `__builtin_dfp_dtstsfi_eq_td' functions behave similarly, but require ! that the type of the `value' argument be `__Decimal64' and ! `__Decimal128' respectively. ! The `__builtin_dfp_dtstsfi_ov' function returns a non-zero value if ! and only if its `value' argument has an undefined number of significant ! digits, such as when `value' is an encoding of `NaN'. The ! `__builtin_dfp_dtstsfi_ov_dd' and `__builtin_dfp_dtstsfi_ov_td' ! functions behave similarly, but require that the type of the `value' ! argument be `__Decimal64' and `__Decimal128' respectively. The following built-in functions are available for the PowerPC family ! of processors when hardware decimal floating point (`-mhard-dfp') is available: ! long long __builtin_dxex (_Decimal64); ! long long __builtin_dxexq (_Decimal128); _Decimal64 __builtin_ddedpd (int, _Decimal64); _Decimal128 __builtin_ddedpdq (int, _Decimal128); _Decimal64 __builtin_denbcd (int, _Decimal64); _Decimal128 __builtin_denbcdq (int, _Decimal128); ! _Decimal64 __builtin_diex (long long, _Decimal64); ! _Decimal128 _builtin_diexq (long long, _Decimal128); _Decimal64 __builtin_dscli (_Decimal64, int); _Decimal128 __builtin_dscliq (_Decimal128, int); _Decimal64 __builtin_dscri (_Decimal64, int); *************** File: gcc.info, Node: PowerPC AltiVec/V *** 38543,38549 **** GCC provides an interface for the PowerPC family of processors to access the AltiVec operations described in Motorola's AltiVec Programming Interface Manual. The interface is made available by including ! '' and using '-maltivec' and '-mabi=altivec'. The interface supports the following vector types. vector unsigned char --- 38990,38996 ---- GCC provides an interface for the PowerPC family of processors to access the AltiVec operations described in Motorola's AltiVec Programming Interface Manual. The interface is made available by including ! `' and using `-maltivec' and `-mabi=altivec'. The interface supports the following vector types. vector unsigned char *************** supports the following vector types. *** 38560,38574 **** vector bool int vector float ! If '-mvsx' is used the following additional vector types are implemented. vector unsigned long vector signed long vector double ! The long types are only implemented for 64-bit code generation, and the ! long type is only used in the floating point/integer conversion instructions. GCC's implementation of the high-level language interface available --- 39007,39021 ---- vector bool int vector float ! If `-mvsx' is used the following additional vector types are implemented. vector unsigned long vector signed long vector double ! The long types are only implemented for 64-bit code generation, and ! the long type is only used in the floating point/integer conversion instructions. GCC's implementation of the high-level language interface available *************** ways. *** 38581,38598 **** * A vector initializer requires no cast if the vector constant is of the same type as the variable it is initializing. ! * If 'signed' or 'unsigned' is omitted, the signedness of the vector type is the default signedness of the base type. The default varies depending on the operating system, so a portable program should always specify the signedness. ! * Compiling with '-maltivec' adds keywords '__vector', 'vector', ! '__pixel', 'pixel', '__bool' and 'bool'. When compiling ISO C, the ! context-sensitive substitution of the keywords 'vector', 'pixel' ! and 'bool' is disabled. To use them, you must include ! '' instead. ! * GCC allows using a 'typedef' name as the type specifier for a vector type. * For C, overloaded functions are implemented with macros so the --- 39028,39045 ---- * A vector initializer requires no cast if the vector constant is of the same type as the variable it is initializing. ! * If `signed' or `unsigned' is omitted, the signedness of the vector type is the default signedness of the base type. The default varies depending on the operating system, so a portable program should always specify the signedness. ! * Compiling with `-maltivec' adds keywords `__vector', `vector', ! `__pixel', `pixel', `__bool' and `bool'. When compiling ISO C, ! the context-sensitive substitution of the keywords `vector', ! `pixel' and `bool' is disabled. To use them, you must include ! `' instead. ! * GCC allows using a `typedef' name as the type specifier for a vector type. * For C, overloaded functions are implemented with macros so the *************** ways. *** 38600,38611 **** vec_add ((vector signed int){1, 2, 3, 4}, foo); ! Since 'vec_add' is a macro, the vector constant in the example is treated as four separate arguments. Wrap the entire argument in parentheses for this to work. ! _Note:_ Only the '' interface is supported. Internally, GCC ! uses built-in functions to achieve the functionality in the aforementioned header file, but they are not supported and are subject to change without notice. --- 39047,39058 ---- vec_add ((vector signed int){1, 2, 3, 4}, foo); ! Since `vec_add' is a macro, the vector constant in the example is treated as four separate arguments. Wrap the entire argument in parentheses for this to work. ! _Note:_ Only the `' interface is supported. Internally, ! GCC uses built-in functions to achieve the functionality in the aforementioned header file, but they are not supported and are subject to change without notice. *************** a direct mapping between generic and spe *** 38615,38621 **** generic names are shown here, although the specific operations can also be used. ! Arguments that are documented as 'const int' require literal integral values within the range required for that operation. vector signed char vec_abs (vector signed char); --- 39062,39068 ---- generic names are shown here, although the specific operations can also be used. ! Arguments that are documented as `const int' require literal integral values within the range required for that operation. vector signed char vec_abs (vector signed char); *************** additional functions are available: *** 40670,40689 **** void vec_vsx_st (vector bool char, int, unsigned char *); void vec_vsx_st (vector bool char, int, signed char *); ! vector double vec_xxpermdi (vector double, vector double, int); ! vector float vec_xxpermdi (vector float, vector float, int); ! vector long long vec_xxpermdi (vector long long, vector long long, int); vector unsigned long long vec_xxpermdi (vector unsigned long long, ! vector unsigned long long, int); ! vector int vec_xxpermdi (vector int, vector int, int); vector unsigned int vec_xxpermdi (vector unsigned int, ! vector unsigned int, int); ! vector short vec_xxpermdi (vector short, vector short, int); vector unsigned short vec_xxpermdi (vector unsigned short, ! vector unsigned short, int); ! vector signed char vec_xxpermdi (vector signed char, vector signed char, int); vector unsigned char vec_xxpermdi (vector unsigned char, ! vector unsigned char, int); vector double vec_xxsldi (vector double, vector double, int); vector float vec_xxsldi (vector float, vector float, int); --- 41117,41137 ---- void vec_vsx_st (vector bool char, int, unsigned char *); void vec_vsx_st (vector bool char, int, signed char *); ! vector double vec_xxpermdi (vector double, vector double, const int); ! vector float vec_xxpermdi (vector float, vector float, const int); ! vector long long vec_xxpermdi (vector long long, vector long long, const int); vector unsigned long long vec_xxpermdi (vector unsigned long long, ! vector unsigned long long, const int); ! vector int vec_xxpermdi (vector int, vector int, const int); vector unsigned int vec_xxpermdi (vector unsigned int, ! vector unsigned int, const int); ! vector short vec_xxpermdi (vector short, vector short, const int); vector unsigned short vec_xxpermdi (vector unsigned short, ! vector unsigned short, const int); ! vector signed char vec_xxpermdi (vector signed char, vector signed char, ! const int); vector unsigned char vec_xxpermdi (vector unsigned char, ! vector unsigned char, const int); vector double vec_xxsldi (vector double, vector double, int); vector float vec_xxsldi (vector float, vector float, int); *************** additional functions are available: *** 40699,40708 **** vector unsigned char vec_xxsldi (vector unsigned char, vector unsigned char, int); ! Note that the 'vec_ld' and 'vec_st' built-in functions always generate ! the AltiVec 'LVX' and 'STVX' instructions even if the VSX instruction ! set is available. The 'vec_vsx_ld' and 'vec_vsx_st' built-in functions ! always generate the VSX 'LXVD2X', 'LXVW4X', 'STXVD2X', and 'STXVW4X' instructions. If the ISA 2.07 additions to the vector/scalar (power8-vector) --- 41147,41156 ---- vector unsigned char vec_xxsldi (vector unsigned char, vector unsigned char, int); ! Note that the `vec_ld' and `vec_st' built-in functions always generate ! the AltiVec `LVX' and `STVX' instructions even if the VSX instruction ! set is available. The `vec_vsx_ld' and `vec_vsx_st' built-in functions ! always generate the VSX `LXVD2X', `LXVW4X', `STXVD2X', and `STXVW4X' instructions. If the ISA 2.07 additions to the vector/scalar (power8-vector) *************** VECTOR UNSIGNED LONG LONG. *** 41019,41029 **** If the ISA 2.07 additions to the vector/scalar (power8-vector) instruction set are available, the following additional functions are available for 64-bit targets. New vector types (VECTOR __INT128_T and ! VECTOR __UINT128_T) are available to hold the __INT128_T and __UINT128_T ! types to use these builtins. ! The normal vector extract, and set operations work on VECTOR __INT128_T ! and VECTOR __UINT128_T types, but the index value must be 0. vector __int128_t vec_vaddcuq (vector __int128_t, vector __int128_t); vector __uint128_t vec_vaddcuq (vector __uint128_t, vector __uint128_t); --- 41467,41477 ---- If the ISA 2.07 additions to the vector/scalar (power8-vector) instruction set are available, the following additional functions are available for 64-bit targets. New vector types (VECTOR __INT128_T and ! VECTOR __UINT128_T) are available to hold the __INT128_T and ! __UINT128_T types to use these builtins. ! The normal vector extract, and set operations work on VECTOR ! __INT128_T and VECTOR __UINT128_T types, but the index value must be 0. vector __int128_t vec_vaddcuq (vector __int128_t, vector __int128_t); vector __uint128_t vec_vaddcuq (vector __uint128_t, vector __uint128_t); *************** and VECTOR __UINT128_T types, but the in *** 41068,41075 **** int __builtin_bcdsub_gt (vector __int128_t, vector__int128_t); int __builtin_bcdsub_ov (vector __int128_t, vector__int128_t); ! If the ISA 3.00 additions to the vector/scalar (power9-vector) ! instruction set are available: vector long long vec_vctz (vector long long); vector unsigned long long vec_vctz (vector unsigned long long); --- 41516,41523 ---- int __builtin_bcdsub_gt (vector __int128_t, vector__int128_t); int __builtin_bcdsub_ov (vector __int128_t, vector__int128_t); ! If the ISA 3.0 instruction set additions (`-mcpu=power9') are ! available: vector long long vec_vctz (vector long long); vector unsigned long long vec_vctz (vector unsigned long long); *************** instruction set are available: *** 41103,41110 **** vector long long vec_vprtybd (vector long long); vector unsigned long long vec_vprtybd (vector unsigned long long); ! If the ISA 3.00 additions to the vector/scalar (power9-vector) ! instruction set are available for 64-bit targets: vector long vec_vprtyb (vector long); vector unsigned long vec_vprtyb (vector unsigned long); --- 41551,41558 ---- vector long long vec_vprtybd (vector long long); vector unsigned long long vec_vprtybd (vector unsigned long long); ! On 64-bit targets, if the ISA 3.0 additions (`-mcpu=power9') are ! available: vector long vec_vprtyb (vector long); vector unsigned long vec_vprtyb (vector unsigned long); *************** instruction set are available for 64-bit *** 41118,41126 **** vector __uint128_t vec_vprtybd (vector __uint128_t); The following built-in vector functions are available for the PowerPC ! family of processors, starting with ISA 3.0 or later ('-mcpu=power9') or ! with '-mpower9-vector': ! __vector unsigned char vec_absd (__vector unsigned char arg1, __vector unsigned char arg2); __vector unsigned short --- 41566,41572 ---- vector __uint128_t vec_vprtybd (vector __uint128_t); The following built-in vector functions are available for the PowerPC ! family of processors, starting with ISA 3.0 or later (`-mcpu=power9'): __vector unsigned char vec_absd (__vector unsigned char arg1, __vector unsigned char arg2); __vector unsigned short *************** with '-mpower9-vector': *** 41140,41170 **** __vector unsigned char vec_srv (__vector unsigned char src, __vector unsigned char shift_distance); ! The 'vec_absd', 'vec_absdb', 'vec_absdh', and 'vec_absdw' built-in functions each computes the absolute differences of the pairs of vector elements supplied in its two vector arguments, placing the absolute differences into the corresponding elements of the vector result. ! The 'vec_slv' and 'vec_srv' functions operate on all of the bytes of ! their 'src' and 'shift_distance' arguments in parallel. The behavior of ! the 'vec_slv' is as if there existed a temporary array of 17 unsigned ! characters 'slv_array' within which elements 0 through 15 are the same ! as the entries in the 'src' array and element 16 equals 0. The result ! returned from the 'vec_slv' function is a '__vector' of 16 unsigned ! characters within which element 'i' is computed using the C expression ! '0xff & (*((unsigned short *)(slv_array + i)) << (0x07 & ! shift_distance[i]))', with this resulting value coerced to the 'unsigned ! char' type. The behavior of the 'vec_srv' is as if there existed a ! temporary array of 17 unsigned characters 'srv_array' within which ! element 0 equals zero and elements 1 through 16 equal the elements 0 ! through 15 of the 'src' array. The result returned from the 'vec_srv' ! function is a '__vector' of 16 unsigned characters within which element ! 'i' is computed using the C expression '0xff & (*((unsigned short ! *)(srv_array + i)) >> (0x07 & shift_distance[i]))', with this resulting ! value coerced to the 'unsigned char' type. ! If the cryptographic instructions are enabled ('-mcrypto' or ! '-mcpu=power8'), the following builtins are enabled. vector unsigned long long __builtin_crypto_vsbox (vector unsigned long long); --- 41586,41616 ---- __vector unsigned char vec_srv (__vector unsigned char src, __vector unsigned char shift_distance); ! The `vec_absd', `vec_absdb', `vec_absdh', and `vec_absdw' built-in functions each computes the absolute differences of the pairs of vector elements supplied in its two vector arguments, placing the absolute differences into the corresponding elements of the vector result. ! The `vec_slv' and `vec_srv' functions operate on all of the bytes of ! their `src' and `shift_distance' arguments in parallel. The behavior ! of the `vec_slv' is as if there existed a temporary array of 17 ! unsigned characters `slv_array' within which elements 0 through 15 are ! the same as the entries in the `src' array and element 16 equals 0. The ! result returned from the `vec_slv' function is a `__vector' of 16 ! unsigned characters within which element `i' is computed using the C ! expression `0xff & (*((unsigned short *)(slv_array + i)) << (0x07 & ! shift_distance[i]))', with this resulting value coerced to the ! `unsigned char' type. The behavior of the `vec_srv' is as if there ! existed a temporary array of 17 unsigned characters `srv_array' within ! which element 0 equals zero and elements 1 through 16 equal the ! elements 0 through 15 of the `src' array. The result returned from the ! `vec_srv' function is a `__vector' of 16 unsigned characters within ! which element `i' is computed using the C expression `0xff & ! (*((unsigned short *)(srv_array + i)) >> (0x07 & shift_distance[i]))', ! with this resulting value coerced to the `unsigned char' type. ! If the cryptographic instructions are enabled (`-mcrypto' or ! `-mcpu=power8'), the following builtins are enabled. vector unsigned long long __builtin_crypto_vsbox (vector unsigned long long); *************** value coerced to the 'unsigned char' typ *** 41217,41236 **** int, int); The second argument to the __BUILTIN_CRYPTO_VSHASIGMAD and ! __BUILTIN_CRYPTO_VSHASIGMAW builtin functions must be a constant integer ! that is 0 or 1. The third argument to these builtin functions must be a ! constant integer in the range of 0 to 15. ! If the ISA 3.00 additions to the vector/scalar (power9-vector) ! instruction set are available, the following additional functions are ! available for both 32-bit and 64-bit targets. vector short vec_xl (int, vector short *); vector short vec_xl (int, short *); vector unsigned short vec_xl (int, vector unsigned short *); ! vector unsigned short vec_xl (int, unsigned short *); vector char vec_xl ! (int, vector char *); vector char vec_xl (int, char *); vector unsigned ! char vec_xl (int, vector unsigned char *); vector unsigned char vec_xl ! (int, unsigned char *); void vec_xst (vector short, int, vector short *); void vec_xst (vector short, int, short *); void vec_xst (vector unsigned short, int, vector --- 41663,41682 ---- int, int); The second argument to the __BUILTIN_CRYPTO_VSHASIGMAD and ! __BUILTIN_CRYPTO_VSHASIGMAW builtin functions must be a constant ! integer that is 0 or 1. The third argument to these builtin functions ! must be a constant integer in the range of 0 to 15. ! If the ISA 3.0 instruction set additions are enabled (`-mcpu=power9'), ! the following additional functions are available for both 32-bit and ! 64-bit targets. vector short vec_xl (int, vector short *); vector short vec_xl (int, short *); vector unsigned short vec_xl (int, vector unsigned short *); ! vector unsigned short vec_xl (int, unsigned short *); vector char ! vec_xl (int, vector char *); vector char vec_xl (int, char *); vector ! unsigned char vec_xl (int, vector unsigned char *); vector unsigned ! char vec_xl (int, unsigned char *); void vec_xst (vector short, int, vector short *); void vec_xst (vector short, int, short *); void vec_xst (vector unsigned short, int, vector *************** between PowerPC and S/390. *** 41256,41275 **** 6.59.21.1 PowerPC HTM Low Level Built-in Functions .................................................. ! The following low level built-in functions are available with '-mhtm' or ! '-mcpu=CPU' where CPU is 'power8' or later. They all generate the machine instruction that is part of the name. ! The HTM builtins (with the exception of '__builtin_tbegin') return the full 4-bit condition register value set by their associated hardware ! instruction. The header file 'htmintrin.h' defines some macros that can ! be used to decipher the return value. The '__builtin_tbegin' builtin returns a simple true or false value depending on whether a transaction was successfully started or not. The arguments of the builtins match exactly the type and order of the associated hardware instruction's ! operands, except for the '__builtin_tcheck' builtin, which does not take ! any input arguments. Refer to the ISA manual for a description of each ! instruction's operands. unsigned int __builtin_tbegin (unsigned int) unsigned int __builtin_tend (unsigned int) --- 41702,41721 ---- 6.59.21.1 PowerPC HTM Low Level Built-in Functions .................................................. ! The following low level built-in functions are available with `-mhtm' ! or `-mcpu=CPU' where CPU is `power8' or later. They all generate the machine instruction that is part of the name. ! The HTM builtins (with the exception of `__builtin_tbegin') return the full 4-bit condition register value set by their associated hardware ! instruction. The header file `htmintrin.h' defines some macros that can ! be used to decipher the return value. The `__builtin_tbegin' builtin returns a simple true or false value depending on whether a transaction was successfully started or not. The arguments of the builtins match exactly the type and order of the associated hardware instruction's ! operands, except for the `__builtin_tcheck' builtin, which does not ! take any input arguments. Refer to the ISA manual for a description of ! each instruction's operands. unsigned int __builtin_tbegin (unsigned int) unsigned int __builtin_tend (unsigned int) *************** some common extended mnemonics of the HT *** 41294,41302 **** Note that the semantics of the above HTM builtins are required to mimic the locking semantics used for critical sections. Builtins that are ! used to create a new transaction or restart a suspended transaction must ! have lock acquisition like semantics while those builtins that end or ! suspend a transaction must have lock release like semantics. Specifically, this must mimic lock semantics as specified by C++11, for example: Lock acquisition is as-if an execution of __atomic_exchange_n(&globallock,1,__ATOMIC_ACQUIRE) that returns 0, and --- 41740,41748 ---- Note that the semantics of the above HTM builtins are required to mimic the locking semantics used for critical sections. Builtins that are ! used to create a new transaction or restart a suspended transaction ! must have lock acquisition like semantics while those builtins that end ! or suspend a transaction must have lock release like semantics. Specifically, this must mimic lock semantics as specified by C++11, for example: Lock acquisition is as-if an execution of __atomic_exchange_n(&globallock,1,__ATOMIC_ACQUIRE) that returns 0, and *************** the builtins in a way that would violate *** 41310,41323 **** accomplished by adding memory barriers to the associated HTM instructions (which is a conservative approach to provide acquire and release semantics). Earlier versions of the compiler did not treat the ! HTM instructions as memory barriers. A '__TM_FENCE__' macro has been added, which can be used to determine whether the current compiler ! treats HTM instructions as memory barriers or not. This allows the user ! to explicitly add memory barriers to their code when using an older ! version of the compiler. ! The following set of built-in functions are available to gain access to ! the HTM specific special purpose registers. unsigned long __builtin_get_texasr (void) unsigned long __builtin_get_texasru (void) --- 41756,41769 ---- accomplished by adding memory barriers to the associated HTM instructions (which is a conservative approach to provide acquire and release semantics). Earlier versions of the compiler did not treat the ! HTM instructions as memory barriers. A `__TM_FENCE__' macro has been added, which can be used to determine whether the current compiler ! treats HTM instructions as memory barriers or not. This allows the ! user to explicitly add memory barriers to their code when using an ! older version of the compiler. ! The following set of built-in functions are available to gain access ! to the HTM specific special purpose registers. unsigned long __builtin_get_texasr (void) unsigned long __builtin_get_texasru (void) *************** the HTM specific special purpose registe *** 41363,41369 **** One final built-in function has been added that returns the value of the 2-bit Transaction State field of the Machine Status Register (MSR) ! as stored in 'CR0'. unsigned long __builtin_ttest (void) --- 41809,41815 ---- One final built-in function has been added that returns the value of the 2-bit Transaction State field of the Machine Status Register (MSR) ! as stored in `CR0'. unsigned long __builtin_ttest (void) *************** using the following code example: *** 41391,41400 **** ................................................. The following high level HTM interface is made available by including ! '' and using '-mhtm' or '-mcpu=CPU' where CPU is 'power8' ! or later. This interface is common between PowerPC and S/390, allowing ! users to write one HTM source implementation that can be compiled and ! executed on either system. long __TM_simple_begin (void) long __TM_begin (void* const TM_buff) --- 41837,41846 ---- ................................................. The following high level HTM interface is made available by including ! `' and using `-mhtm' or `-mcpu=CPU' where CPU is ! `power8' or later. This interface is common between PowerPC and S/390, ! allowing users to write one HTM source implementation that can be ! compiled and executed on either system. long __TM_simple_begin (void) long __TM_begin (void* const TM_buff) *************** the C programming language via the use o *** 41461,41552 **** following functions are supported: -- Built-in Function: void __builtin_rx_brk (void) ! Generates the 'brk' machine instruction. -- Built-in Function: void __builtin_rx_clrpsw (int) ! Generates the 'clrpsw' machine instruction to clear the specified bit in the processor status word. -- Built-in Function: void __builtin_rx_int (int) ! Generates the 'int' machine instruction to generate an interrupt with the specified value. -- Built-in Function: void __builtin_rx_machi (int, int) ! Generates the 'machi' machine instruction to add the result of multiplying the top 16 bits of the two arguments into the accumulator. -- Built-in Function: void __builtin_rx_maclo (int, int) ! Generates the 'maclo' machine instruction to add the result of multiplying the bottom 16 bits of the two arguments into the accumulator. -- Built-in Function: void __builtin_rx_mulhi (int, int) ! Generates the 'mulhi' machine instruction to place the result of multiplying the top 16 bits of the two arguments into the accumulator. -- Built-in Function: void __builtin_rx_mullo (int, int) ! Generates the 'mullo' machine instruction to place the result of multiplying the bottom 16 bits of the two arguments into the accumulator. -- Built-in Function: int __builtin_rx_mvfachi (void) ! Generates the 'mvfachi' machine instruction to read the top 32 bits ! of the accumulator. -- Built-in Function: int __builtin_rx_mvfacmi (void) ! Generates the 'mvfacmi' machine instruction to read the middle 32 bits of the accumulator. -- Built-in Function: int __builtin_rx_mvfc (int) ! Generates the 'mvfc' machine instruction which reads the control register specified in its argument and returns its value. -- Built-in Function: void __builtin_rx_mvtachi (int) ! Generates the 'mvtachi' machine instruction to set the top 32 bits of the accumulator. -- Built-in Function: void __builtin_rx_mvtaclo (int) ! Generates the 'mvtaclo' machine instruction to set the bottom 32 bits of the accumulator. -- Built-in Function: void __builtin_rx_mvtc (int reg, int val) ! Generates the 'mvtc' machine instruction which sets control ! register number 'reg' to 'val'. -- Built-in Function: void __builtin_rx_mvtipl (int) ! Generates the 'mvtipl' machine instruction set the interrupt priority level. -- Built-in Function: void __builtin_rx_racw (int) ! Generates the 'racw' machine instruction to round the accumulator according to the specified mode. -- Built-in Function: int __builtin_rx_revw (int) ! Generates the 'revw' machine instruction which swaps the bytes in the argument so that bits 0-7 now occupy bits 8-15 and vice versa, and also bits 16-23 occupy bits 24-31 and vice versa. -- Built-in Function: void __builtin_rx_rmpa (void) ! Generates the 'rmpa' machine instruction which initiates a repeated ! multiply and accumulate sequence. -- Built-in Function: void __builtin_rx_round (float) ! Generates the 'round' machine instruction which returns the floating-point argument rounded according to the current rounding mode set in the floating-point status word register. -- Built-in Function: int __builtin_rx_sat (int) ! Generates the 'sat' machine instruction which returns the saturated ! value of the argument. -- Built-in Function: void __builtin_rx_setpsw (int) ! Generates the 'setpsw' machine instruction to set the specified bit ! in the processor status word. -- Built-in Function: void __builtin_rx_wait (void) ! Generates the 'wait' machine instruction.  File: gcc.info, Node: S/390 System z Built-in Functions, Next: SH Built-in Functions, Prev: RX Built-in Functions, Up: Target Builtins --- 41907,41998 ---- following functions are supported: -- Built-in Function: void __builtin_rx_brk (void) ! Generates the `brk' machine instruction. -- Built-in Function: void __builtin_rx_clrpsw (int) ! Generates the `clrpsw' machine instruction to clear the specified bit in the processor status word. -- Built-in Function: void __builtin_rx_int (int) ! Generates the `int' machine instruction to generate an interrupt with the specified value. -- Built-in Function: void __builtin_rx_machi (int, int) ! Generates the `machi' machine instruction to add the result of multiplying the top 16 bits of the two arguments into the accumulator. -- Built-in Function: void __builtin_rx_maclo (int, int) ! Generates the `maclo' machine instruction to add the result of multiplying the bottom 16 bits of the two arguments into the accumulator. -- Built-in Function: void __builtin_rx_mulhi (int, int) ! Generates the `mulhi' machine instruction to place the result of multiplying the top 16 bits of the two arguments into the accumulator. -- Built-in Function: void __builtin_rx_mullo (int, int) ! Generates the `mullo' machine instruction to place the result of multiplying the bottom 16 bits of the two arguments into the accumulator. -- Built-in Function: int __builtin_rx_mvfachi (void) ! Generates the `mvfachi' machine instruction to read the top 32 ! bits of the accumulator. -- Built-in Function: int __builtin_rx_mvfacmi (void) ! Generates the `mvfacmi' machine instruction to read the middle 32 bits of the accumulator. -- Built-in Function: int __builtin_rx_mvfc (int) ! Generates the `mvfc' machine instruction which reads the control register specified in its argument and returns its value. -- Built-in Function: void __builtin_rx_mvtachi (int) ! Generates the `mvtachi' machine instruction to set the top 32 bits of the accumulator. -- Built-in Function: void __builtin_rx_mvtaclo (int) ! Generates the `mvtaclo' machine instruction to set the bottom 32 bits of the accumulator. -- Built-in Function: void __builtin_rx_mvtc (int reg, int val) ! Generates the `mvtc' machine instruction which sets control ! register number `reg' to `val'. -- Built-in Function: void __builtin_rx_mvtipl (int) ! Generates the `mvtipl' machine instruction set the interrupt priority level. -- Built-in Function: void __builtin_rx_racw (int) ! Generates the `racw' machine instruction to round the accumulator according to the specified mode. -- Built-in Function: int __builtin_rx_revw (int) ! Generates the `revw' machine instruction which swaps the bytes in the argument so that bits 0-7 now occupy bits 8-15 and vice versa, and also bits 16-23 occupy bits 24-31 and vice versa. -- Built-in Function: void __builtin_rx_rmpa (void) ! Generates the `rmpa' machine instruction which initiates a ! repeated multiply and accumulate sequence. -- Built-in Function: void __builtin_rx_round (float) ! Generates the `round' machine instruction which returns the floating-point argument rounded according to the current rounding mode set in the floating-point status word register. -- Built-in Function: int __builtin_rx_sat (int) ! Generates the `sat' machine instruction which returns the ! saturated value of the argument. -- Built-in Function: void __builtin_rx_setpsw (int) ! Generates the `setpsw' machine instruction to set the specified ! bit in the processor status word. -- Built-in Function: void __builtin_rx_wait (void) ! Generates the `wait' machine instruction.  File: gcc.info, Node: S/390 System z Built-in Functions, Next: SH Built-in Functions, Prev: RX Built-in Functions, Up: Target Builtins *************** File: gcc.info, Node: S/390 System z Bu *** 41555,41655 **** ----------------------------------------- -- Built-in Function: int __builtin_tbegin (void*) ! Generates the 'tbegin' machine instruction starting a ! non-constrained hardware transaction. If the parameter is non-NULL ! the memory area is used to store the transaction diagnostic buffer ! and will be passed as first operand to 'tbegin'. This buffer can ! be defined using the 'struct __htm_tdb' C struct defined in ! 'htmintrin.h' and must reside on a double-word boundary. The ! second tbegin operand is set to '0xff0c'. This enables ! save/restore of all GPRs and disables aborts for FPR and AR manipulations inside the transaction body. The condition code set by the tbegin instruction is returned as integer value. The tbegin instruction by definition overwrites the content of all FPRs. The compiler will generate code which saves and restores the FPRs. For ! soft-float code it is recommended to used the '*_nofloat' variant. ! In order to prevent a TDB from being written it is required to pass ! a constant zero value as parameter. Passing a zero value through a ! variable is not sufficient. Although modifications of access ! registers inside the transaction will not trigger an transaction ! abort it is not supported to actually modify them. Access ! registers do not get saved when entering a transaction. They will ! have undefined state when reaching the abort code. Macros for the possible return codes of tbegin are defined in the ! 'htmintrin.h' header file: ! '_HTM_TBEGIN_STARTED' ! 'tbegin' has been executed as part of normal processing. The transaction body is supposed to be executed. ! '_HTM_TBEGIN_INDETERMINATE' The transaction was aborted due to an indeterminate condition which might be persistent. ! '_HTM_TBEGIN_TRANSIENT' The transaction aborted due to a transient failure. The transaction should be re-executed in that case. ! '_HTM_TBEGIN_PERSISTENT' The transaction aborted due to a persistent failure. Re-execution under same circumstances will not be productive. -- Macro: _HTM_FIRST_USER_ABORT_CODE ! The '_HTM_FIRST_USER_ABORT_CODE' defined in 'htmintrin.h' specifies ! the first abort code which can be used for '__builtin_tabort'. ! Values below this threshold are reserved for machine use. -- Data type: struct __htm_tdb ! The 'struct __htm_tdb' defined in 'htmintrin.h' describes the structure of the transaction diagnostic block as specified in the Principles of Operation manual chapter 5-91. -- Built-in Function: int __builtin_tbegin_nofloat (void*) ! Same as '__builtin_tbegin' but without FPR saves and restores. Using this variant in code making use of FPRs will leave the FPRs in undefined state when entering the transaction abort handler code. -- Built-in Function: int __builtin_tbegin_retry (void*, int) ! In addition to '__builtin_tbegin' a loop for transient failures is generated. If tbegin returns a condition code of 2 the transaction will be retried as often as specified in the second argument. The perform processor assist instruction is used to tell the CPU about the number of fails so far. -- Built-in Function: int __builtin_tbegin_retry_nofloat (void*, int) ! Same as '__builtin_tbegin_retry' but without FPR saves and restores. Using this variant in code making use of FPRs will leave the FPRs in undefined state when entering the transaction abort handler code. -- Built-in Function: void __builtin_tbeginc (void) ! Generates the 'tbeginc' machine instruction starting a constrained ! hardware transaction. The second operand is set to '0xff08'. -- Built-in Function: int __builtin_tend (void) ! Generates the 'tend' machine instruction finishing a transaction and making the changes visible to other threads. The condition code generated by tend is returned as integer value. -- Built-in Function: void __builtin_tabort (int) ! Generates the 'tabort' machine instruction with the specified abort ! code. Abort codes from 0 through 255 are reserved and will result ! in an error message. -- Built-in Function: void __builtin_tx_assist (int) ! Generates the 'ppa rX,rY,1' machine instruction. Where the integer ! parameter is loaded into rX and a value of zero is loaded into rY. ! The integer parameter specifies the number of times the transaction ! repeatedly aborted. -- Built-in Function: int __builtin_tx_nesting_depth (void) ! Generates the 'etnd' machine instruction. The current nesting depth is returned as integer value. For a nesting depth of 0 the code is not executed as part of an transaction. -- Built-in Function: void __builtin_non_tx_store (uint64_t *, uint64_t) ! ! Generates the 'ntstg' machine instruction. The second argument is written to the first arguments location. The store operation will not be rolled-back in case of an transaction abort. --- 42001,42104 ---- ----------------------------------------- -- Built-in Function: int __builtin_tbegin (void*) ! Generates the `tbegin' machine instruction starting a ! non-constrained hardware transaction. If the parameter is ! non-NULL the memory area is used to store the transaction ! diagnostic buffer and will be passed as first operand to `tbegin'. ! This buffer can be defined using the `struct __htm_tdb' C struct ! defined in `htmintrin.h' and must reside on a double-word ! boundary. The second tbegin operand is set to `0xff0c'. This ! enables save/restore of all GPRs and disables aborts for FPR and AR manipulations inside the transaction body. The condition code set by the tbegin instruction is returned as integer value. The tbegin instruction by definition overwrites the content of all FPRs. The compiler will generate code which saves and restores the FPRs. For ! soft-float code it is recommended to used the `*_nofloat' variant. ! In order to prevent a TDB from being written it is required to ! pass a constant zero value as parameter. Passing a zero value ! through a variable is not sufficient. Although modifications of ! access registers inside the transaction will not trigger an ! transaction abort it is not supported to actually modify them. ! Access registers do not get saved when entering a transaction. ! They will have undefined state when reaching the abort code. Macros for the possible return codes of tbegin are defined in the ! `htmintrin.h' header file: ! `_HTM_TBEGIN_STARTED' ! `tbegin' has been executed as part of normal processing. The transaction body is supposed to be executed. ! ! `_HTM_TBEGIN_INDETERMINATE' The transaction was aborted due to an indeterminate condition which might be persistent. ! ! `_HTM_TBEGIN_TRANSIENT' The transaction aborted due to a transient failure. The transaction should be re-executed in that case. ! ! `_HTM_TBEGIN_PERSISTENT' The transaction aborted due to a persistent failure. Re-execution under same circumstances will not be productive. -- Macro: _HTM_FIRST_USER_ABORT_CODE ! The `_HTM_FIRST_USER_ABORT_CODE' defined in `htmintrin.h' ! specifies the first abort code which can be used for ! `__builtin_tabort'. Values below this threshold are reserved for ! machine use. -- Data type: struct __htm_tdb ! The `struct __htm_tdb' defined in `htmintrin.h' describes the structure of the transaction diagnostic block as specified in the Principles of Operation manual chapter 5-91. -- Built-in Function: int __builtin_tbegin_nofloat (void*) ! Same as `__builtin_tbegin' but without FPR saves and restores. Using this variant in code making use of FPRs will leave the FPRs in undefined state when entering the transaction abort handler code. -- Built-in Function: int __builtin_tbegin_retry (void*, int) ! In addition to `__builtin_tbegin' a loop for transient failures is generated. If tbegin returns a condition code of 2 the transaction will be retried as often as specified in the second argument. The perform processor assist instruction is used to tell the CPU about the number of fails so far. -- Built-in Function: int __builtin_tbegin_retry_nofloat (void*, int) ! Same as `__builtin_tbegin_retry' but without FPR saves and restores. Using this variant in code making use of FPRs will leave the FPRs in undefined state when entering the transaction abort handler code. -- Built-in Function: void __builtin_tbeginc (void) ! Generates the `tbeginc' machine instruction starting a constrained ! hardware transaction. The second operand is set to `0xff08'. -- Built-in Function: int __builtin_tend (void) ! Generates the `tend' machine instruction finishing a transaction and making the changes visible to other threads. The condition code generated by tend is returned as integer value. -- Built-in Function: void __builtin_tabort (int) ! Generates the `tabort' machine instruction with the specified ! abort code. Abort codes from 0 through 255 are reserved and will ! result in an error message. -- Built-in Function: void __builtin_tx_assist (int) ! Generates the `ppa rX,rY,1' machine instruction. Where the ! integer parameter is loaded into rX and a value of zero is loaded ! into rY. The integer parameter specifies the number of times the ! transaction repeatedly aborted. -- Built-in Function: int __builtin_tx_nesting_depth (void) ! Generates the `etnd' machine instruction. The current nesting depth is returned as integer value. For a nesting depth of 0 the code is not executed as part of an transaction. -- Built-in Function: void __builtin_non_tx_store (uint64_t *, uint64_t) ! Generates the `ntstg' machine instruction. The second argument is written to the first arguments location. The store operation will not be rolled-back in case of an transaction abort. *************** The following built-in functions are sup *** 41663,41680 **** SH4 families of processors: -- Built-in Function: void __builtin_set_thread_pointer (void *PTR) ! Sets the 'GBR' register to the specified value PTR. This is usually used by system code that manages threads and execution contexts. The compiler normally does not generate code that ! modifies the contents of 'GBR' and thus the value is preserved ! across function calls. Changing the 'GBR' value in user code must ! be done with caution, since the compiler might use 'GBR' in order to access thread local variables. -- Built-in Function: void * __builtin_thread_pointer (void) ! Returns the value that is currently set in the 'GBR' register. Memory loads and stores that use the thread pointer as a base ! address are turned into 'GBR' based displacement loads and stores, if possible. For example: struct my_tcb { --- 42112,42130 ---- SH4 families of processors: -- Built-in Function: void __builtin_set_thread_pointer (void *PTR) ! Sets the `GBR' register to the specified value PTR. This is usually used by system code that manages threads and execution contexts. The compiler normally does not generate code that ! modifies the contents of `GBR' and thus the value is preserved ! across function calls. Changing the `GBR' value in user code must ! be done with caution, since the compiler might use `GBR' in order to access thread local variables. + -- Built-in Function: void * __builtin_thread_pointer (void) ! Returns the value that is currently set in the `GBR' register. Memory loads and stores that use the thread pointer as a base ! address are turned into `GBR' based displacement loads and stores, if possible. For example: struct my_tcb { *************** SH4 families of processors: *** 41683,41698 **** int get_tcb_value (void) { ! // Generate 'mov.l @(8,gbr),r0' instruction return ((my_tcb*)__builtin_thread_pointer ())->c; } - -- Built-in Function: unsigned int __builtin_sh_get_fpscr (void) ! Returns the value that is currently set in the 'FPSCR' register. -- Built-in Function: void __builtin_sh_set_fpscr (unsigned int VAL) ! Sets the 'FPSCR' register to the specified value VAL, while preserving the current values of the FR, SZ and PR bits.  --- 42133,42147 ---- int get_tcb_value (void) { ! // Generate `mov.l @(8,gbr),r0' instruction return ((my_tcb*)__builtin_thread_pointer ())->c; } -- Built-in Function: unsigned int __builtin_sh_get_fpscr (void) ! Returns the value that is currently set in the `FPSCR' register. -- Built-in Function: void __builtin_sh_set_fpscr (unsigned int VAL) ! Sets the `FPSCR' register to the specified value VAL, while preserving the current values of the FR, SZ and PR bits.  *************** File: gcc.info, Node: SPARC VIS Built-i *** 41703,41710 **** GCC supports SIMD operations on the SPARC using both the generic vector extensions (*note Vector Extensions::) as well as built-in functions for ! the SPARC Visual Instruction Set (VIS). When you use the '-mvis' switch, ! the VIS extension is exposed as the following built-in functions: typedef int v1si __attribute__ ((vector_size (4))); typedef int v2si __attribute__ ((vector_size (8))); --- 42152,42160 ---- GCC supports SIMD operations on the SPARC using both the generic vector extensions (*note Vector Extensions::) as well as built-in functions for ! the SPARC Visual Instruction Set (VIS). When you use the `-mvis' ! switch, the VIS extension is exposed as the following built-in ! functions: typedef int v1si __attribute__ ((vector_size (4))); typedef int v2si __attribute__ ((vector_size (8))); *************** the VIS extension is exposed as the foll *** 41769,41775 **** long __builtin_vis_array16 (long, long); long __builtin_vis_array32 (long, long); ! When you use the '-mvis2' switch, the VIS version 2.0 built-in functions also become available: long __builtin_vis_bmask (long, long); --- 42219,42225 ---- long __builtin_vis_array16 (long, long); long __builtin_vis_array32 (long, long); ! When you use the `-mvis2' switch, the VIS version 2.0 built-in functions also become available: long __builtin_vis_bmask (long, long); *************** functions also become available: *** 41785,41791 **** long __builtin_vis_edge32n (void *, void *); long __builtin_vis_edge32ln (void *, void *); ! When you use the '-mvis3' switch, the VIS version 3.0 built-in functions also become available: void __builtin_vis_cmask8 (long); --- 42235,42241 ---- long __builtin_vis_edge32n (void *, void *); long __builtin_vis_edge32ln (void *, void *); ! When you use the `-mvis3' switch, the VIS version 3.0 built-in functions also become available: void __builtin_vis_cmask8 (long); *************** functions also become available: *** 41835,41841 **** int64_t __builtin_vis_xmulx (int64_t, int64_t); int64_t __builtin_vis_xmulxhi (int64_t, int64_t); ! When you use the '-mvis4' switch, the VIS version 4.0 built-in functions also become available: v8qi __builtin_vis_fpadd8 (v8qi, v8qi); --- 42285,42291 ---- int64_t __builtin_vis_xmulx (int64_t, int64_t); int64_t __builtin_vis_xmulxhi (int64_t, int64_t); ! When you use the `-mvis4' switch, the VIS version 4.0 built-in functions also become available: v8qi __builtin_vis_fpadd8 (v8qi, v8qi); *************** implementation differs in several ways. *** 41888,41902 **** * A vector initializer requires no cast if the vector constant is of the same type as the variable it is initializing. ! * If 'signed' or 'unsigned' is omitted, the signedness of the vector type is the default signedness of the base type. The default varies depending on the operating system, so a portable program should always specify the signedness. ! * By default, the keyword '__vector' is added. The macro 'vector' is ! defined in '' and can be undefined. ! * GCC allows using a 'typedef' name as the type specifier for a vector type. * For C, overloaded functions are implemented with macros so the --- 42338,42352 ---- * A vector initializer requires no cast if the vector constant is of the same type as the variable it is initializing. ! * If `signed' or `unsigned' is omitted, the signedness of the vector type is the default signedness of the base type. The default varies depending on the operating system, so a portable program should always specify the signedness. ! * By default, the keyword `__vector' is added. The macro `vector' is ! defined in `' and can be undefined. ! * GCC allows using a `typedef' name as the type specifier for a vector type. * For C, overloaded functions are implemented with macros so the *************** implementation differs in several ways. *** 41904,41917 **** spu_add ((vector signed int){1, 2, 3, 4}, foo); ! Since 'spu_add' is a macro, the vector constant in the example is treated as four separate arguments. Wrap the entire argument in parentheses for this to work. ! * The extended version of '__builtin_expect' is not supported. _Note:_ Only the interface described in the aforementioned ! specification is supported. Internally, GCC uses built-in functions to implement the required functionality, but these are not supported and are subject to change without notice. --- 42354,42368 ---- spu_add ((vector signed int){1, 2, 3, 4}, foo); ! Since `spu_add' is a macro, the vector constant in the example is treated as four separate arguments. Wrap the entire argument in parentheses for this to work. ! * The extended version of `__builtin_expect' is not supported. ! _Note:_ Only the interface described in the aforementioned ! specification is supported. Internally, GCC uses built-in functions to implement the required functionality, but these are not supported and are subject to change without notice. *************** File: gcc.info, Node: TI C6X Built-in F *** 41923,41929 **** GCC provides intrinsics to access certain instructions of the TI C6X processors. These intrinsics, listed below, are available after ! inclusion of the 'c6x_intrinsics.h' header file. They map directly to C6X instructions. --- 42374,42380 ---- GCC provides intrinsics to access certain instructions of the TI C6X processors. These intrinsics, listed below, are available after ! inclusion of the `c6x_intrinsics.h' header file. They map directly to C6X instructions. *************** C6X instructions. *** 41954,41960 **** int _abs (int) int _abs2 (int) -  File: gcc.info, Node: TILE-Gx Built-in Functions, Next: TILEPro Built-in Functions, Prev: TI C6X Built-in Functions, Up: Target Builtins --- 42405,42410 ---- *************** processor. The intrinsics are of the fo *** 41967,41973 **** unsigned long long __insn_OP (...) - Where OP is the name of the instruction. Refer to the ISA manual for the complete list of instructions. --- 42417,42422 ---- *************** The intrinsics are: *** 41984,41992 **** void __tile_idn_send (unsigned long long) void __tile_udn_send (unsigned long long) ! ! The intrinsic 'void __tile_network_barrier (void)' is used to guarantee ! that no network operations before it are reordered with those after it.  File: gcc.info, Node: TILEPro Built-in Functions, Next: x86 Built-in Functions, Prev: TILE-Gx Built-in Functions, Up: Target Builtins --- 42433,42441 ---- void __tile_idn_send (unsigned long long) void __tile_udn_send (unsigned long long) ! The intrinsic `void __tile_network_barrier (void)' is used to ! guarantee that no network operations before it are reordered with those ! after it.  File: gcc.info, Node: TILEPro Built-in Functions, Next: x86 Built-in Functions, Prev: TILE-Gx Built-in Functions, Up: Target Builtins *************** processor. The intrinsics are of the fo *** 42000,42006 **** unsigned __insn_OP (...) - where OP is the name of the instruction. Refer to the ISA manual for the complete list of instructions. --- 42449,42454 ---- *************** The intrinsics are: *** 42019,42027 **** void __tile_sn_send (unsigned) void __tile_udn_send (unsigned) ! ! The intrinsic 'void __tile_network_barrier (void)' is used to guarantee ! that no network operations before it are reordered with those after it.  File: gcc.info, Node: x86 Built-in Functions, Next: x86 transactional memory intrinsics, Prev: TILEPro Built-in Functions, Up: Target Builtins --- 42467,42475 ---- void __tile_sn_send (unsigned) void __tile_udn_send (unsigned) ! The intrinsic `void __tile_network_barrier (void)' is used to ! guarantee that no network operations before it are reordered with those ! after it.  File: gcc.info, Node: x86 Built-in Functions, Next: x86 transactional memory intrinsics, Prev: TILEPro Built-in Functions, Up: Target Builtins *************** File: gcc.info, Node: x86 Built-in Func *** 42032,42064 **** These built-in functions are available for the x86-32 and x86-64 family of computers, depending on the command-line switches used. ! If you specify command-line switches such as '-msse', the compiler could use the extended instruction sets even if the built-ins are not used explicitly in the program. For this reason, applications that perform run-time CPU detection must compile separate files for each ! supported architecture, using the appropriate flags. In particular, the ! file containing the CPU detection code should be compiled without these ! options. The following machine modes are available for use with MMX built-in ! functions (*note Vector Extensions::): 'V2SI' for a vector of two 32-bit ! integers, 'V4HI' for a vector of four 16-bit integers, and 'V8QI' for a ! vector of eight 8-bit integers. Some of the built-in functions operate ! on MMX registers as a whole 64-bit entity, these use 'V1DI' as their ! mode. ! If 3DNow! extensions are enabled, 'V2SF' is used as a mode for a vector of two 32-bit floating-point values. ! If SSE extensions are enabled, 'V4SF' is used for a vector of four 32-bit floating-point values. Some instructions use a vector of four ! 32-bit integers, these use 'V4SI'. Finally, some instructions operate on an entire vector register, interpreting it as a 128-bit integer, ! these use mode 'TI'. In 64-bit mode, the x86-64 family of processors uses additional ! built-in functions for efficient use of 'TF' ('__float128') 128-bit ! floating point and 'TC' 128-bit complex floating-point values. The following floating-point built-in functions are available in 64-bit mode. All of them implement the function that is part of the name. --- 42480,42512 ---- These built-in functions are available for the x86-32 and x86-64 family of computers, depending on the command-line switches used. ! If you specify command-line switches such as `-msse', the compiler could use the extended instruction sets even if the built-ins are not used explicitly in the program. For this reason, applications that perform run-time CPU detection must compile separate files for each ! supported architecture, using the appropriate flags. In particular, ! the file containing the CPU detection code should be compiled without ! these options. The following machine modes are available for use with MMX built-in ! functions (*note Vector Extensions::): `V2SI' for a vector of two ! 32-bit integers, `V4HI' for a vector of four 16-bit integers, and ! `V8QI' for a vector of eight 8-bit integers. Some of the built-in ! functions operate on MMX registers as a whole 64-bit entity, these use ! `V1DI' as their mode. ! If 3DNow! extensions are enabled, `V2SF' is used as a mode for a vector of two 32-bit floating-point values. ! If SSE extensions are enabled, `V4SF' is used for a vector of four 32-bit floating-point values. Some instructions use a vector of four ! 32-bit integers, these use `V4SI'. Finally, some instructions operate on an entire vector register, interpreting it as a 128-bit integer, ! these use mode `TI'. In 64-bit mode, the x86-64 family of processors uses additional ! built-in functions for efficient use of `TF' (`__float128') 128-bit ! floating point and `TC' 128-bit complex floating-point values. The following floating-point built-in functions are available in 64-bit mode. All of them implement the function that is part of the name. *************** mode. All of them implement the functio *** 42068,42086 **** The following built-in function is always available. ! 'void __builtin_ia32_pause (void)' ! Generates the 'pause' machine instruction with a compiler memory barrier. The following floating-point built-in functions are made available in the 64-bit mode. ! '__float128 __builtin_infq (void)' ! Similar to '__builtin_inf', except the return type is '__float128'. ! '__float128 __builtin_huge_valq (void)' ! Similar to '__builtin_huge_val', except the return type is ! '__float128'. The following built-in functions are always available and can be used to check the target platform type. --- 42516,42534 ---- The following built-in function is always available. ! `void __builtin_ia32_pause (void)' ! Generates the `pause' machine instruction with a compiler memory barrier. The following floating-point built-in functions are made available in the 64-bit mode. ! `__float128 __builtin_infq (void)' ! Similar to `__builtin_inf', except the return type is `__float128'. ! `__float128 __builtin_huge_valq (void)' ! Similar to `__builtin_huge_val', except the return type is ! `__float128'. The following built-in functions are always available and can be used to check the target platform type. *************** to check the target platform type. *** 42089,42102 **** This function runs the CPU detection code to check the type of CPU and the features supported. This built-in function needs to be invoked along with the built-in functions to check CPU type and ! features, '__builtin_cpu_is' and '__builtin_cpu_supports', only when used in a function that is executed before any constructors are called. The CPU detection code is automatically executed in a very high priority constructor. ! For example, this function has to be used in 'ifunc' resolvers that ! check for CPU type using the built-in functions '__builtin_cpu_is' ! and '__builtin_cpu_supports', or in constructors on targets that don't support constructor priority. static void (*resolve_memcpy (void)) (void) --- 42537,42550 ---- This function runs the CPU detection code to check the type of CPU and the features supported. This built-in function needs to be invoked along with the built-in functions to check CPU type and ! features, `__builtin_cpu_is' and `__builtin_cpu_supports', only when used in a function that is executed before any constructors are called. The CPU detection code is automatically executed in a very high priority constructor. ! For example, this function has to be used in `ifunc' resolvers that ! check for CPU type using the built-in functions `__builtin_cpu_is' ! and `__builtin_cpu_supports', or in constructors on targets that don't support constructor priority. static void (*resolve_memcpy (void)) (void) *************** to check the target platform type. *** 42113,42181 **** void *memcpy (void *, const void *, size_t) __attribute__ ((ifunc ("resolve_memcpy"))); -- Built-in Function: int __builtin_cpu_is (const char *CPUNAME) This function returns a positive integer if the run-time CPU is of ! type CPUNAME and returns '0' otherwise. The following CPU names can be detected: ! 'intel' Intel CPU. ! 'atom' Intel Atom CPU. ! 'core2' Intel Core 2 CPU. ! 'corei7' Intel Core i7 CPU. ! 'nehalem' Intel Core i7 Nehalem CPU. ! 'westmere' Intel Core i7 Westmere CPU. ! 'sandybridge' Intel Core i7 Sandy Bridge CPU. ! 'amd' AMD CPU. ! 'amdfam10h' AMD Family 10h CPU. ! 'barcelona' AMD Family 10h Barcelona CPU. ! 'shanghai' AMD Family 10h Shanghai CPU. ! 'istanbul' AMD Family 10h Istanbul CPU. ! 'btver1' AMD Family 14h CPU. ! 'amdfam15h' AMD Family 15h CPU. ! 'bdver1' AMD Family 15h Bulldozer version 1. ! 'bdver2' AMD Family 15h Bulldozer version 2. ! 'bdver3' AMD Family 15h Bulldozer version 3. ! 'bdver4' AMD Family 15h Bulldozer version 4. ! 'btver2' AMD Family 16h CPU. ! 'znver1' AMD Family 17h CPU. Here is an example: --- 42561,42630 ---- void *memcpy (void *, const void *, size_t) __attribute__ ((ifunc ("resolve_memcpy"))); + -- Built-in Function: int __builtin_cpu_is (const char *CPUNAME) This function returns a positive integer if the run-time CPU is of ! type CPUNAME and returns `0' otherwise. The following CPU names can be detected: ! `intel' Intel CPU. ! `atom' Intel Atom CPU. ! `core2' Intel Core 2 CPU. ! `corei7' Intel Core i7 CPU. ! `nehalem' Intel Core i7 Nehalem CPU. ! `westmere' Intel Core i7 Westmere CPU. ! `sandybridge' Intel Core i7 Sandy Bridge CPU. ! `amd' AMD CPU. ! `amdfam10h' AMD Family 10h CPU. ! `barcelona' AMD Family 10h Barcelona CPU. ! `shanghai' AMD Family 10h Shanghai CPU. ! `istanbul' AMD Family 10h Istanbul CPU. ! `btver1' AMD Family 14h CPU. ! `amdfam15h' AMD Family 15h CPU. ! `bdver1' AMD Family 15h Bulldozer version 1. ! `bdver2' AMD Family 15h Bulldozer version 2. ! `bdver3' AMD Family 15h Bulldozer version 3. ! `bdver4' AMD Family 15h Bulldozer version 4. ! `btver2' AMD Family 16h CPU. ! `znver1' AMD Family 17h CPU. Here is an example: *************** to check the target platform type. *** 42190,42221 **** -- Built-in Function: int __builtin_cpu_supports (const char *FEATURE) This function returns a positive integer if the run-time CPU ! supports FEATURE and returns '0' otherwise. The following features can be detected: ! 'cmov' CMOV instruction. ! 'mmx' MMX instructions. ! 'popcnt' POPCNT instruction. ! 'sse' SSE instructions. ! 'sse2' SSE2 instructions. ! 'sse3' SSE3 instructions. ! 'ssse3' SSSE3 instructions. ! 'sse4.1' SSE4.1 instructions. ! 'sse4.2' SSE4.2 instructions. ! 'avx' AVX instructions. ! 'avx2' AVX2 instructions. ! 'avx512f' AVX512F instructions. Here is an example: --- 42639,42681 ---- -- Built-in Function: int __builtin_cpu_supports (const char *FEATURE) This function returns a positive integer if the run-time CPU ! supports FEATURE and returns `0' otherwise. The following features can be detected: ! `cmov' CMOV instruction. ! ! `mmx' MMX instructions. ! ! `popcnt' POPCNT instruction. ! ! `sse' SSE instructions. ! ! `sse2' SSE2 instructions. ! ! `sse3' SSE3 instructions. ! ! `ssse3' SSSE3 instructions. ! ! `sse4.1' SSE4.1 instructions. ! ! `sse4.2' SSE4.2 instructions. ! ! `avx' AVX instructions. ! ! `avx2' AVX2 instructions. ! ! `avx512f' AVX512F instructions. Here is an example: *************** to check the target platform type. *** 42228,42235 **** count = generic_countbits (n); //generic implementation. } ! The following built-in functions are made available by '-mmmx'. All of ! them generate the machine instruction that is part of the name. v8qi __builtin_ia32_paddb (v8qi, v8qi) v4hi __builtin_ia32_paddw (v4hi, v4hi) --- 42688,42695 ---- count = generic_countbits (n); //generic implementation. } ! The following built-in functions are made available by `-mmmx'. All ! of them generate the machine instruction that is part of the name. v8qi __builtin_ia32_paddb (v8qi, v8qi) v4hi __builtin_ia32_paddw (v4hi, v4hi) *************** them generate the machine instruction th *** 42284,42293 **** v4hi __builtin_ia32_psrawi (v4hi, int) v2si __builtin_ia32_psradi (v2si, int) - The following built-in functions are made available either with ! '-msse', or with a combination of '-m3dnow' and '-march=athlon'. All of ! them generate the machine instruction that is part of the name. v4hi __builtin_ia32_pmulhuw (v4hi, v4hi) v8qi __builtin_ia32_pavgb (v8qi, v8qi) --- 42744,42752 ---- v4hi __builtin_ia32_psrawi (v4hi, int) v2si __builtin_ia32_psradi (v2si, int) The following built-in functions are made available either with ! `-msse', or with a combination of `-m3dnow' and `-march=athlon'. All ! of them generate the machine instruction that is part of the name. v4hi __builtin_ia32_pmulhuw (v4hi, v4hi) v8qi __builtin_ia32_pavgb (v8qi, v8qi) *************** them generate the machine instruction th *** 42302,42308 **** void __builtin_ia32_movntq (di *, di) void __builtin_ia32_sfence (void) ! The following built-in functions are available when '-msse' is used. All of them generate the machine instruction that is part of the name. int __builtin_ia32_comieq (v4sf, v4sf) --- 42761,42767 ---- void __builtin_ia32_movntq (di *, di) void __builtin_ia32_sfence (void) ! The following built-in functions are available when `-msse' is used. All of them generate the machine instruction that is part of the name. int __builtin_ia32_comieq (v4sf, v4sf) *************** All of them generate the machine instruc *** 42374,42397 **** void __builtin_ia32_movntps (float *, v4sf) int __builtin_ia32_movmskps (v4sf) ! The following built-in functions are available when '-msse' is used. ! 'v4sf __builtin_ia32_loadups (float *)' ! Generates the 'movups' machine instruction as a load from memory. ! 'void __builtin_ia32_storeups (float *, v4sf)' ! Generates the 'movups' machine instruction as a store to memory. ! 'v4sf __builtin_ia32_loadss (float *)' ! Generates the 'movss' machine instruction as a load from memory. ! 'v4sf __builtin_ia32_loadhps (v4sf, const v2sf *)' ! Generates the 'movhps' machine instruction as a load from memory. ! 'v4sf __builtin_ia32_loadlps (v4sf, const v2sf *)' ! Generates the 'movlps' machine instruction as a load from memory ! 'void __builtin_ia32_storehps (v2sf *, v4sf)' ! Generates the 'movhps' machine instruction as a store to memory. ! 'void __builtin_ia32_storelps (v2sf *, v4sf)' ! Generates the 'movlps' machine instruction as a store to memory. ! The following built-in functions are available when '-msse2' is used. All of them generate the machine instruction that is part of the name. int __builtin_ia32_comisdeq (v2df, v2df) --- 42833,42862 ---- void __builtin_ia32_movntps (float *, v4sf) int __builtin_ia32_movmskps (v4sf) ! The following built-in functions are available when `-msse' is used. ! `v4sf __builtin_ia32_loadups (float *)' ! Generates the `movups' machine instruction as a load from memory. ! `void __builtin_ia32_storeups (float *, v4sf)' ! Generates the `movups' machine instruction as a store to memory. ! ! `v4sf __builtin_ia32_loadss (float *)' ! Generates the `movss' machine instruction as a load from memory. ! ! `v4sf __builtin_ia32_loadhps (v4sf, const v2sf *)' ! Generates the `movhps' machine instruction as a load from memory. ! ! `v4sf __builtin_ia32_loadlps (v4sf, const v2sf *)' ! Generates the `movlps' machine instruction as a load from memory ! ! `void __builtin_ia32_storehps (v2sf *, v4sf)' ! Generates the `movhps' machine instruction as a store to memory. ! ! `void __builtin_ia32_storelps (v2sf *, v4sf)' ! Generates the `movlps' machine instruction as a store to memory. ! ! The following built-in functions are available when `-msse2' is used. All of them generate the machine instruction that is part of the name. int __builtin_ia32_comisdeq (v2df, v2df) *************** All of them generate the machine instruc *** 42550,42556 **** v4si __builtin_ia32_pmaddwd128 (v8hi, v8hi) v2di __builtin_ia32_movq128 (v2di) ! The following built-in functions are available when '-msse3' is used. All of them generate the machine instruction that is part of the name. v2df __builtin_ia32_addsubpd (v2df, v2df) --- 43015,43021 ---- v4si __builtin_ia32_pmaddwd128 (v8hi, v8hi) v2di __builtin_ia32_movq128 (v2di) ! The following built-in functions are available when `-msse3' is used. All of them generate the machine instruction that is part of the name. v2df __builtin_ia32_addsubpd (v2df, v2df) *************** All of them generate the machine instruc *** 42565,42571 **** v4sf __builtin_ia32_movsldup (v4sf) void __builtin_ia32_mwait (unsigned int, unsigned int) ! The following built-in functions are available when '-mssse3' is used. All of them generate the machine instruction that is part of the name. v2si __builtin_ia32_phaddd (v2si, v2si) --- 43030,43036 ---- v4sf __builtin_ia32_movsldup (v4sf) void __builtin_ia32_mwait (unsigned int, unsigned int) ! The following built-in functions are available when `-mssse3' is used. All of them generate the machine instruction that is part of the name. v2si __builtin_ia32_phaddd (v2si, v2si) *************** All of them generate the machine instruc *** 42585,42591 **** v2si __builtin_ia32_pabsd (v2si) v4hi __builtin_ia32_pabsw (v4hi) ! The following built-in functions are available when '-mssse3' is used. All of them generate the machine instruction that is part of the name. v4si __builtin_ia32_phaddd128 (v4si, v4si) --- 43050,43056 ---- v2si __builtin_ia32_pabsd (v2si) v4hi __builtin_ia32_pabsw (v4hi) ! The following built-in functions are available when `-mssse3' is used. All of them generate the machine instruction that is part of the name. v4si __builtin_ia32_phaddd128 (v4si, v4si) *************** All of them generate the machine instruc *** 42605,42612 **** v4si __builtin_ia32_pabsd128 (v4si) v8hi __builtin_ia32_pabsw128 (v8hi) ! The following built-in functions are available when '-msse4.1' is used. ! All of them generate the machine instruction that is part of the name. v2df __builtin_ia32_blendpd (v2df, v2df, const int) v4sf __builtin_ia32_blendps (v4sf, v4sf, const int) --- 43070,43078 ---- v4si __builtin_ia32_pabsd128 (v4si) v8hi __builtin_ia32_pabsw128 (v8hi) ! The following built-in functions are available when `-msse4.1' is ! used. All of them generate the machine instruction that is part of the ! name. v2df __builtin_ia32_blendpd (v2df, v2df, const int) v4sf __builtin_ia32_blendps (v4sf, v4sf, const int) *************** All of them generate the machine instruc *** 42652,42682 **** v2df __builtin_ia32_roundsd (v2df, v2df, const int) v4sf __builtin_ia32_roundss (v4sf, v4sf, const int) ! The following built-in functions are available when '-msse4.1' is used. ! 'v4sf __builtin_ia32_vec_set_v4sf (v4sf, float, const int)' ! Generates the 'insertps' machine instruction. ! 'int __builtin_ia32_vec_ext_v16qi (v16qi, const int)' ! Generates the 'pextrb' machine instruction. ! 'v16qi __builtin_ia32_vec_set_v16qi (v16qi, int, const int)' ! Generates the 'pinsrb' machine instruction. ! 'v4si __builtin_ia32_vec_set_v4si (v4si, int, const int)' ! Generates the 'pinsrd' machine instruction. ! 'v2di __builtin_ia32_vec_set_v2di (v2di, long long, const int)' ! Generates the 'pinsrq' machine instruction in 64bit mode. The following built-in functions are changed to generate new SSE4.1 ! instructions when '-msse4.1' is used. ! 'float __builtin_ia32_vec_ext_v4sf (v4sf, const int)' ! Generates the 'extractps' machine instruction. ! 'int __builtin_ia32_vec_ext_v4si (v4si, const int)' ! Generates the 'pextrd' machine instruction. ! 'long long __builtin_ia32_vec_ext_v2di (v2di, const int)' ! Generates the 'pextrq' machine instruction in 64bit mode. ! The following built-in functions are available when '-msse4.2' is used. ! All of them generate the machine instruction that is part of the name. v16qi __builtin_ia32_pcmpestrm128 (v16qi, int, v16qi, int, const int) int __builtin_ia32_pcmpestri128 (v16qi, int, v16qi, int, const int) --- 43118,43155 ---- v2df __builtin_ia32_roundsd (v2df, v2df, const int) v4sf __builtin_ia32_roundss (v4sf, v4sf, const int) ! The following built-in functions are available when `-msse4.1' is used. ! `v4sf __builtin_ia32_vec_set_v4sf (v4sf, float, const int)' ! Generates the `insertps' machine instruction. ! ! `int __builtin_ia32_vec_ext_v16qi (v16qi, const int)' ! Generates the `pextrb' machine instruction. ! ! `v16qi __builtin_ia32_vec_set_v16qi (v16qi, int, const int)' ! Generates the `pinsrb' machine instruction. ! ! `v4si __builtin_ia32_vec_set_v4si (v4si, int, const int)' ! Generates the `pinsrd' machine instruction. ! ! `v2di __builtin_ia32_vec_set_v2di (v2di, long long, const int)' ! Generates the `pinsrq' machine instruction in 64bit mode. The following built-in functions are changed to generate new SSE4.1 ! instructions when `-msse4.1' is used. ! `float __builtin_ia32_vec_ext_v4sf (v4sf, const int)' ! Generates the `extractps' machine instruction. ! `int __builtin_ia32_vec_ext_v4si (v4si, const int)' ! Generates the `pextrd' machine instruction. ! ! `long long __builtin_ia32_vec_ext_v2di (v2di, const int)' ! Generates the `pextrq' machine instruction in 64bit mode. ! ! The following built-in functions are available when `-msse4.2' is ! used. All of them generate the machine instruction that is part of the ! name. v16qi __builtin_ia32_pcmpestrm128 (v16qi, int, v16qi, int, const int) int __builtin_ia32_pcmpestri128 (v16qi, int, v16qi, int, const int) *************** All of them generate the machine instruc *** 42694,42722 **** int __builtin_ia32_pcmpistriz128 (v16qi, v16qi, const int) v2di __builtin_ia32_pcmpgtq (v2di, v2di) ! The following built-in functions are available when '-msse4.2' is used. ! 'unsigned int __builtin_ia32_crc32qi (unsigned int, unsigned char)' ! Generates the 'crc32b' machine instruction. ! 'unsigned int __builtin_ia32_crc32hi (unsigned int, unsigned short)' ! Generates the 'crc32w' machine instruction. ! 'unsigned int __builtin_ia32_crc32si (unsigned int, unsigned int)' ! Generates the 'crc32l' machine instruction. ! 'unsigned long long __builtin_ia32_crc32di (unsigned long long, unsigned long long)' ! Generates the 'crc32q' machine instruction. The following built-in functions are changed to generate new SSE4.2 ! instructions when '-msse4.2' is used. ! 'int __builtin_popcount (unsigned int)' ! Generates the 'popcntl' machine instruction. ! 'int __builtin_popcountl (unsigned long)' ! Generates the 'popcntl' or 'popcntq' machine instruction, depending ! on the size of 'unsigned long'. ! 'int __builtin_popcountll (unsigned long long)' ! Generates the 'popcntq' machine instruction. ! The following built-in functions are available when '-mavx' is used. All of them generate the machine instruction that is part of the name. v4df __builtin_ia32_addpd256 (v4df,v4df) --- 43167,43200 ---- int __builtin_ia32_pcmpistriz128 (v16qi, v16qi, const int) v2di __builtin_ia32_pcmpgtq (v2di, v2di) ! The following built-in functions are available when `-msse4.2' is used. ! `unsigned int __builtin_ia32_crc32qi (unsigned int, unsigned char)' ! Generates the `crc32b' machine instruction. ! ! `unsigned int __builtin_ia32_crc32hi (unsigned int, unsigned short)' ! Generates the `crc32w' machine instruction. ! ! `unsigned int __builtin_ia32_crc32si (unsigned int, unsigned int)' ! Generates the `crc32l' machine instruction. ! ! `unsigned long long __builtin_ia32_crc32di (unsigned long long, unsigned long long)' ! Generates the `crc32q' machine instruction. The following built-in functions are changed to generate new SSE4.2 ! instructions when `-msse4.2' is used. ! `int __builtin_popcount (unsigned int)' ! Generates the `popcntl' machine instruction. ! `int __builtin_popcountl (unsigned long)' ! Generates the `popcntl' or `popcntq' machine instruction, ! depending on the size of `unsigned long'. ! ! `int __builtin_popcountll (unsigned long long)' ! Generates the `popcntq' machine instruction. ! ! The following built-in functions are available when `-mavx' is used. All of them generate the machine instruction that is part of the name. v4df __builtin_ia32_addpd256 (v4df,v4df) *************** All of them generate the machine instruc *** 42848,42854 **** v4df __builtin_ia32_xorpd256 (v4df,v4df) v8sf __builtin_ia32_xorps256 (v8sf,v8sf) ! The following built-in functions are available when '-mavx2' is used. All of them generate the machine instruction that is part of the name. v32qi __builtin_ia32_mpsadbw256 (v32qi,v32qi,int) --- 43326,43332 ---- v4df __builtin_ia32_xorpd256 (v4df,v4df) v8sf __builtin_ia32_xorps256 (v8sf,v8sf) ! The following built-in functions are available when `-mavx2' is used. All of them generate the machine instruction that is part of the name. v32qi __builtin_ia32_mpsadbw256 (v32qi,v32qi,int) *************** All of them generate the machine instruc *** 43023,43029 **** v4si __builtin_ia32_gatherdiv4si (v4si, pcint,v2di,v4si,int) v4si __builtin_ia32_gatherdiv4si256 (v4si, pcint,v4di,v4si,int) ! The following built-in functions are available when '-maes' is used. All of them generate the machine instruction that is part of the name. v2di __builtin_ia32_aesenc128 (v2di, v2di) --- 43501,43507 ---- v4si __builtin_ia32_gatherdiv4si (v4si, pcint,v2di,v4si,int) v4si __builtin_ia32_gatherdiv4si256 (v4si, pcint,v4di,v4si,int) ! The following built-in functions are available when `-maes' is used. All of them generate the machine instruction that is part of the name. v2di __builtin_ia32_aesenc128 (v2di, v2di) *************** All of them generate the machine instruc *** 43033,43045 **** v2di __builtin_ia32_aeskeygenassist128 (v2di, const int) v2di __builtin_ia32_aesimc128 (v2di) ! The following built-in function is available when '-mpclmul' is used. ! 'v2di __builtin_ia32_pclmulqdq128 (v2di, v2di, const int)' ! Generates the 'pclmulqdq' machine instruction. ! The following built-in function is available when '-mfsgsbase' is used. ! All of them generate the machine instruction that is part of the name. unsigned int __builtin_ia32_rdfsbase32 (void) unsigned long long __builtin_ia32_rdfsbase64 (void) --- 43511,43524 ---- v2di __builtin_ia32_aeskeygenassist128 (v2di, const int) v2di __builtin_ia32_aesimc128 (v2di) ! The following built-in function is available when `-mpclmul' is used. ! `v2di __builtin_ia32_pclmulqdq128 (v2di, v2di, const int)' ! Generates the `pclmulqdq' machine instruction. ! The following built-in function is available when `-mfsgsbase' is ! used. All of them generate the machine instruction that is part of the ! name. unsigned int __builtin_ia32_rdfsbase32 (void) unsigned long long __builtin_ia32_rdfsbase64 (void) *************** All of them generate the machine instruc *** 43050,43063 **** void _writegsbase_u32 (unsigned int) void _writegsbase_u64 (unsigned long long) ! The following built-in function is available when '-mrdrnd' is used. All of them generate the machine instruction that is part of the name. unsigned int __builtin_ia32_rdrand16_step (unsigned short *) unsigned int __builtin_ia32_rdrand32_step (unsigned int *) unsigned int __builtin_ia32_rdrand64_step (unsigned long long *) ! The following built-in functions are available when '-msse4a' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_movntsd (double *, v2df) --- 43529,43542 ---- void _writegsbase_u32 (unsigned int) void _writegsbase_u64 (unsigned long long) ! The following built-in function is available when `-mrdrnd' is used. All of them generate the machine instruction that is part of the name. unsigned int __builtin_ia32_rdrand16_step (unsigned short *) unsigned int __builtin_ia32_rdrand32_step (unsigned int *) unsigned int __builtin_ia32_rdrand64_step (unsigned long long *) ! The following built-in functions are available when `-msse4a' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_movntsd (double *, v2df) *************** All of them generate the machine instruc *** 43067,43073 **** v2di __builtin_ia32_insertq (v2di, v2di) v2di __builtin_ia32_insertqi (v2di, v2di, const unsigned int, const unsigned int) ! The following built-in functions are available when '-mxop' is used. v2df __builtin_ia32_vfrczpd (v2df) v4sf __builtin_ia32_vfrczps (v4sf) v2df __builtin_ia32_vfrczsd (v2df) --- 43546,43552 ---- v2di __builtin_ia32_insertq (v2di, v2di) v2di __builtin_ia32_insertqi (v2di, v2di, const unsigned int, const unsigned int) ! The following built-in functions are available when `-mxop' is used. v2df __builtin_ia32_vfrczpd (v2df) v4sf __builtin_ia32_vfrczps (v4sf) v2df __builtin_ia32_vfrczsd (v2df) *************** All of them generate the machine instruc *** 43193,43199 **** v2di __builtin_ia32_vpshlq (v2di, v2di) v8hi __builtin_ia32_vpshlw (v8hi, v8hi) ! The following built-in functions are available when '-mfma4' is used. All of them generate the machine instruction that is part of the name. v2df __builtin_ia32_vfmaddpd (v2df, v2df, v2df) --- 43672,43678 ---- v2di __builtin_ia32_vpshlq (v2di, v2di) v8hi __builtin_ia32_vpshlw (v8hi, v8hi) ! The following built-in functions are available when `-mfma4' is used. All of them generate the machine instruction that is part of the name. v2df __builtin_ia32_vfmaddpd (v2df, v2df, v2df) *************** All of them generate the machine instruc *** 43229,43236 **** v4df __builtin_ia32_vfmsubaddpd256 (v4df, v4df, v4df) v8sf __builtin_ia32_vfmsubaddps256 (v8sf, v8sf, v8sf) ! ! The following built-in functions are available when '-mlwp' is used. void __builtin_ia32_llwpcb16 (void *); void __builtin_ia32_llwpcb32 (void *); --- 43708,43714 ---- v4df __builtin_ia32_vfmsubaddpd256 (v4df, v4df, v4df) v8sf __builtin_ia32_vfmsubaddps256 (v8sf, v8sf, v8sf) ! The following built-in functions are available when `-mlwp' is used. void __builtin_ia32_llwpcb16 (void *); void __builtin_ia32_llwpcb32 (void *); *************** All of them generate the machine instruc *** 43245,43256 **** unsigned char __builtin_ia32_lwpins32 (unsigned int, unsigned int, unsigned int) unsigned char __builtin_ia32_lwpins64 (unsigned __int64, unsigned int, unsigned int) ! The following built-in functions are available when '-mbmi' is used. All of them generate the machine instruction that is part of the name. unsigned int __builtin_ia32_bextr_u32(unsigned int, unsigned int); unsigned long long __builtin_ia32_bextr_u64 (unsigned long long, unsigned long long); ! The following built-in functions are available when '-mbmi2' is used. All of them generate the machine instruction that is part of the name. unsigned int _bzhi_u32 (unsigned int, unsigned int) unsigned int _pdep_u32 (unsigned int, unsigned int) --- 43723,43734 ---- unsigned char __builtin_ia32_lwpins32 (unsigned int, unsigned int, unsigned int) unsigned char __builtin_ia32_lwpins64 (unsigned __int64, unsigned int, unsigned int) ! The following built-in functions are available when `-mbmi' is used. All of them generate the machine instruction that is part of the name. unsigned int __builtin_ia32_bextr_u32(unsigned int, unsigned int); unsigned long long __builtin_ia32_bextr_u64 (unsigned long long, unsigned long long); ! The following built-in functions are available when `-mbmi2' is used. All of them generate the machine instruction that is part of the name. unsigned int _bzhi_u32 (unsigned int, unsigned int) unsigned int _pdep_u32 (unsigned int, unsigned int) *************** All of them generate the machine instruc *** 43259,43297 **** unsigned long long _pdep_u64 (unsigned long long, unsigned long long) unsigned long long _pext_u64 (unsigned long long, unsigned long long) ! The following built-in functions are available when '-mlzcnt' is used. All of them generate the machine instruction that is part of the name. unsigned short __builtin_ia32_lzcnt_16(unsigned short); unsigned int __builtin_ia32_lzcnt_u32(unsigned int); unsigned long long __builtin_ia32_lzcnt_u64 (unsigned long long); ! The following built-in functions are available when '-mfxsr' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_fxsave (void *) void __builtin_ia32_fxrstor (void *) void __builtin_ia32_fxsave64 (void *) void __builtin_ia32_fxrstor64 (void *) ! The following built-in functions are available when '-mxsave' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_xsave (void *, long long) void __builtin_ia32_xrstor (void *, long long) void __builtin_ia32_xsave64 (void *, long long) void __builtin_ia32_xrstor64 (void *, long long) ! The following built-in functions are available when '-mxsaveopt' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_xsaveopt (void *, long long) void __builtin_ia32_xsaveopt64 (void *, long long) ! The following built-in functions are available when '-mtbm' is used. Both of them generate the immediate form of the bextr machine instruction. unsigned int __builtin_ia32_bextri_u32 (unsigned int, const unsigned int); unsigned long long __builtin_ia32_bextri_u64 (unsigned long long, const unsigned long long); ! The following built-in functions are available when '-m3dnow' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_femms (void) --- 43737,43775 ---- unsigned long long _pdep_u64 (unsigned long long, unsigned long long) unsigned long long _pext_u64 (unsigned long long, unsigned long long) ! The following built-in functions are available when `-mlzcnt' is used. All of them generate the machine instruction that is part of the name. unsigned short __builtin_ia32_lzcnt_16(unsigned short); unsigned int __builtin_ia32_lzcnt_u32(unsigned int); unsigned long long __builtin_ia32_lzcnt_u64 (unsigned long long); ! The following built-in functions are available when `-mfxsr' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_fxsave (void *) void __builtin_ia32_fxrstor (void *) void __builtin_ia32_fxsave64 (void *) void __builtin_ia32_fxrstor64 (void *) ! The following built-in functions are available when `-mxsave' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_xsave (void *, long long) void __builtin_ia32_xrstor (void *, long long) void __builtin_ia32_xsave64 (void *, long long) void __builtin_ia32_xrstor64 (void *, long long) ! The following built-in functions are available when `-mxsaveopt' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_xsaveopt (void *, long long) void __builtin_ia32_xsaveopt64 (void *, long long) ! The following built-in functions are available when `-mtbm' is used. Both of them generate the immediate form of the bextr machine instruction. unsigned int __builtin_ia32_bextri_u32 (unsigned int, const unsigned int); unsigned long long __builtin_ia32_bextri_u64 (unsigned long long, const unsigned long long); ! The following built-in functions are available when `-m3dnow' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_femms (void) *************** All of them generate the machine instruc *** 43314,43321 **** v2sf __builtin_ia32_pi2fd (v2si) v4hi __builtin_ia32_pmulhrw (v4hi, v4hi) ! The following built-in functions are available when both '-m3dnow' and ! '-march=athlon' are used. All of them generate the machine instruction that is part of the name. v2si __builtin_ia32_pf2iw (v2sf) --- 43792,43799 ---- v2sf __builtin_ia32_pi2fd (v2si) v4hi __builtin_ia32_pmulhrw (v4hi, v4hi) ! The following built-in functions are available when both `-m3dnow' and ! `-march=athlon' are used. All of them generate the machine instruction that is part of the name. v2si __builtin_ia32_pf2iw (v2sf) *************** that is part of the name. *** 43325,43333 **** v2sf __builtin_ia32_pswapdsf (v2sf) v2si __builtin_ia32_pswapdsi (v2si) ! The following built-in functions are available when '-mrtm' is used ! They are used for restricted transactional memory. These are the ! internal low level functions. Normally the functions in *note x86 transactional memory intrinsics:: should be used instead. int __builtin_ia32_xbegin () --- 43803,43811 ---- v2sf __builtin_ia32_pswapdsf (v2sf) v2si __builtin_ia32_pswapdsi (v2si) ! The following built-in functions are available when `-mrtm' is used ! They are used for restricted transactional memory. These are the ! internal low level functions. Normally the functions in *note x86 transactional memory intrinsics:: should be used instead. int __builtin_ia32_xbegin () *************** transactional memory intrinsics:: should *** 43335,43350 **** void __builtin_ia32_xabort (status) int __builtin_ia32_xtest () ! The following built-in functions are available when '-mmwaitx' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_monitorx (void *, unsigned int, unsigned int) void __builtin_ia32_mwaitx (unsigned int, unsigned int, unsigned int) ! The following built-in functions are available when '-mclzero' is used. All of them generate the machine instruction that is part of the name. void __builtin_i32_clzero (void *) ! The following built-in functions are available when '-mpku' is used. They generate reads and writes to PKRU. void __builtin_ia32_wrpkru (unsigned int) unsigned int __builtin_ia32_rdpkru () --- 43813,43828 ---- void __builtin_ia32_xabort (status) int __builtin_ia32_xtest () ! The following built-in functions are available when `-mmwaitx' is used. All of them generate the machine instruction that is part of the name. void __builtin_ia32_monitorx (void *, unsigned int, unsigned int) void __builtin_ia32_mwaitx (unsigned int, unsigned int, unsigned int) ! The following built-in functions are available when `-mclzero' is used. All of them generate the machine instruction that is part of the name. void __builtin_i32_clzero (void *) ! The following built-in functions are available when `-mpku' is used. They generate reads and writes to PKRU. void __builtin_ia32_wrpkru (unsigned int) unsigned int __builtin_ia32_rdpkru () *************** File: gcc.info, Node: x86 transactional *** 43357,43404 **** These hardware transactional memory intrinsics for x86 allow you to use memory transactions with RTM (Restricted Transactional Memory). This ! support is enabled with the '-mrtm' option. For using HLE (Hardware Lock Elision) see *note x86 specific memory model extensions for transactional memory:: instead. ! A memory transaction commits all changes to memory in an atomic way, as ! visible to other threads. If the transaction fails it is rolled back and all side effects discarded. Generally there is no guarantee that a memory transaction ever succeeds and suitable fallback code always needs to be supplied. -- RTM Function: unsigned _xbegin () ! Start a RTM (Restricted Transactional Memory) transaction. Returns ! '_XBEGIN_STARTED' when the transaction started successfully (note ! this is not 0, so the constant has to be explicitly tested). ! If the transaction aborts, all side-effects are undone and an abort ! code encoded as a bit mask is returned. The following macros are ! defined: ! '_XABORT_EXPLICIT' ! Transaction was explicitly aborted with '_xabort'. The ! parameter passed to '_xabort' is available with ! '_XABORT_CODE(status)'. ! '_XABORT_RETRY' Transaction retry is possible. ! '_XABORT_CONFLICT' Transaction abort due to a memory conflict with another thread. ! '_XABORT_CAPACITY' Transaction abort due to the transaction using too much memory. ! '_XABORT_DEBUG' Transaction abort due to a debug trap. ! '_XABORT_NESTED' Transaction abort in an inner nested transaction. There is no guarantee any transaction ever succeeds, so there always needs to be a valid fallback path. -- RTM Function: void _xend () ! Commit the current transaction. When no transaction is active this faults. All memory side-effects of the transaction become visible to other threads in an atomic manner. --- 43835,43888 ---- These hardware transactional memory intrinsics for x86 allow you to use memory transactions with RTM (Restricted Transactional Memory). This ! support is enabled with the `-mrtm' option. For using HLE (Hardware Lock Elision) see *note x86 specific memory model extensions for transactional memory:: instead. ! A memory transaction commits all changes to memory in an atomic way, ! as visible to other threads. If the transaction fails it is rolled back and all side effects discarded. Generally there is no guarantee that a memory transaction ever succeeds and suitable fallback code always needs to be supplied. -- RTM Function: unsigned _xbegin () ! Start a RTM (Restricted Transactional Memory) transaction. ! Returns `_XBEGIN_STARTED' when the transaction started ! successfully (note this is not 0, so the constant has to be ! explicitly tested). ! If the transaction aborts, all side-effects are undone and an ! abort code encoded as a bit mask is returned. The following ! macros are defined: ! `_XABORT_EXPLICIT' ! Transaction was explicitly aborted with `_xabort'. The ! parameter passed to `_xabort' is available with ! `_XABORT_CODE(status)'. ! ! `_XABORT_RETRY' Transaction retry is possible. ! ! `_XABORT_CONFLICT' Transaction abort due to a memory conflict with another thread. ! ! `_XABORT_CAPACITY' Transaction abort due to the transaction using too much memory. ! ! `_XABORT_DEBUG' Transaction abort due to a debug trap. ! ! `_XABORT_NESTED' Transaction abort in an inner nested transaction. There is no guarantee any transaction ever succeeds, so there always needs to be a valid fallback path. -- RTM Function: void _xend () ! Commit the current transaction. When no transaction is active this faults. All memory side-effects of the transaction become visible to other threads in an atomic manner. *************** and suitable fallback code always needs *** 43407,43417 **** otherwise 0. -- RTM Function: void _xabort (status) ! Abort the current transaction. When no transaction is active this is a no-op. The STATUS is an 8-bit constant; its value is encoded ! in the return value from '_xbegin'. ! Here is an example showing handling for '_XABORT_RETRY' and a fallback path for other failures: #include --- 43891,43901 ---- otherwise 0. -- RTM Function: void _xabort (status) ! Abort the current transaction. When no transaction is active this is a no-op. The STATUS is an 8-bit constant; its value is encoded ! in the return value from `_xbegin'. ! Here is an example showing handling for `_XABORT_RETRY' and a fallback path for other failures: #include *************** File: gcc.info, Node: Solaris Format Ch *** 43460,43469 **** 6.60.1 Solaris Format Checks ---------------------------- ! Solaris targets support the 'cmn_err' (or '__cmn_err__') format check. ! 'cmn_err' accepts a subset of the standard 'printf' conversions, and the ! two-argument '%b' conversion for displaying bit-fields. See the Solaris ! man page for 'cmn_err' for more information.  File: gcc.info, Node: Darwin Format Checks, Prev: Solaris Format Checks, Up: Target Format Checks --- 43944,43953 ---- 6.60.1 Solaris Format Checks ---------------------------- ! Solaris targets support the `cmn_err' (or `__cmn_err__') format check. ! `cmn_err' accepts a subset of the standard `printf' conversions, and ! the two-argument `%b' conversion for displaying bit-fields. See the ! Solaris man page for `cmn_err' for more information.  File: gcc.info, Node: Darwin Format Checks, Prev: Solaris Format Checks, Up: Target Format Checks *************** File: gcc.info, Node: Darwin Format Che *** 43471,43487 **** 6.60.2 Darwin Format Checks --------------------------- ! Darwin targets support the 'CFString' (or '__CFString__') in the format attribute context. Declarations made with such attribution are parsed for correct syntax and format argument types. However, parsing of the format string itself is currently undefined and is not carried out by this version of the compiler. ! Additionally, 'CFStringRefs' (defined by the 'CoreFoundation' headers) may also be used as format arguments. Note that the relevant headers are only likely to be available on Darwin (OSX) installations. On such installations, the XCode and system documentation provide descriptions ! of 'CFString', 'CFStringRefs' and associated functions.  File: gcc.info, Node: Pragmas, Next: Unnamed Fields, Prev: Target Format Checks, Up: C Extensions --- 43955,43971 ---- 6.60.2 Darwin Format Checks --------------------------- ! Darwin targets support the `CFString' (or `__CFString__') in the format attribute context. Declarations made with such attribution are parsed for correct syntax and format argument types. However, parsing of the format string itself is currently undefined and is not carried out by this version of the compiler. ! Additionally, `CFStringRefs' (defined by the `CoreFoundation' headers) may also be used as format arguments. Note that the relevant headers are only likely to be available on Darwin (OSX) installations. On such installations, the XCode and system documentation provide descriptions ! of `CFString', `CFStringRefs' and associated functions.  File: gcc.info, Node: Pragmas, Next: Unnamed Fields, Prev: Target Format Checks, Up: C Extensions *************** File: gcc.info, Node: Pragmas, Next: U *** 43490,43497 **** ============================ GCC supports several types of pragmas, primarily in order to compile ! code originally written for other compilers. Note that in general we do ! not recommend the use of pragmas; *Note Function Attributes::, for further explanation. * Menu: --- 43974,43981 ---- ============================ GCC supports several types of pragmas, primarily in order to compile ! code originally written for other compilers. Note that in general we ! do not recommend the use of pragmas; *Note Function Attributes::, for further explanation. * Menu: *************** The pragmas defined by the AArch64 targe *** 43523,43531 **** target function attributes. They can be specified as below: #pragma GCC target("string") ! where 'STRING' can be any string accepted as an AArch64 target ! attribute. *Note AArch64 Function Attributes::, for more details on the ! permissible values of 'string'.  File: gcc.info, Node: ARM Pragmas, Next: M32C Pragmas, Prev: AArch64 Pragmas, Up: Pragmas --- 44007,44015 ---- target function attributes. They can be specified as below: #pragma GCC target("string") ! where `STRING' can be any string accepted as an AArch64 target ! attribute. *Note AArch64 Function Attributes::, for more details on ! the permissible values of `string'.  File: gcc.info, Node: ARM Pragmas, Next: M32C Pragmas, Prev: AArch64 Pragmas, Up: Pragmas *************** File: gcc.info, Node: ARM Pragmas, Nex *** 43534,43550 **** ------------------ The ARM target defines pragmas for controlling the default addition of ! 'long_call' and 'short_call' attributes to functions. *Note Function Attributes::, for information about the effects of these attributes. ! 'long_calls' ! Set all subsequent functions to have the 'long_call' attribute. ! 'no_long_calls' ! Set all subsequent functions to have the 'short_call' attribute. ! 'long_calls_off' ! Do not affect the 'long_call' or 'short_call' attributes of subsequent functions.  --- 44018,44034 ---- ------------------ The ARM target defines pragmas for controlling the default addition of ! `long_call' and `short_call' attributes to functions. *Note Function Attributes::, for information about the effects of these attributes. ! `long_calls' ! Set all subsequent functions to have the `long_call' attribute. ! `no_long_calls' ! Set all subsequent functions to have the `short_call' attribute. ! `long_calls_off' ! Do not affect the `long_call' or `short_call' attributes of subsequent functions.  *************** File: gcc.info, Node: M32C Pragmas, Ne *** 43553,43598 **** 6.61.3 M32C Pragmas ------------------- ! 'GCC memregs NUMBER' ! Overrides the command-line option '-memregs=' for the current file. ! Use with care! This pragma must be before any function in the ! file, and mixing different memregs values in different objects may ! make them incompatible. This pragma is useful when a performance-critical function uses a memreg for temporary values, as it may allow you to reduce the number of memregs used. ! 'ADDRESS NAME ADDRESS' For any declared symbols matching NAME, this does three things to that symbol: it forces the symbol to be located at the given address (a number), it forces the symbol to be volatile, and it changes the symbol's scope to be static. This pragma exists for compatibility with other compilers, but note that the common ! '1234H' numeric syntax is not supported (use '0x1234' instead). Example: #pragma ADDRESS port3 0x103 char port3;  File: gcc.info, Node: MeP Pragmas, Next: RS/6000 and PowerPC Pragmas, Prev: M32C Pragmas, Up: Pragmas 6.61.4 MeP Pragmas ------------------ ! 'custom io_volatile (on|off)' ! Overrides the command-line option '-mio-volatile' for the current file. Note that for compatibility with future GCC releases, this ! option should only be used once before any 'io' variables in each file. ! 'GCC coprocessor available REGISTERS' Specifies which coprocessor registers are available to the register allocator. REGISTERS may be a single register, register range separated by ellipses, or comma-separated list of those. Example: #pragma GCC coprocessor available $c0...$c10, $c28 ! 'GCC coprocessor call_saved REGISTERS' Specifies which coprocessor registers are to be saved and restored by any function using them. REGISTERS may be a single register, register range separated by ellipses, or comma-separated list of --- 44037,44083 ---- 6.61.3 M32C Pragmas ------------------- ! `GCC memregs NUMBER' ! Overrides the command-line option `-memregs=' for the current ! file. Use with care! This pragma must be before any function in ! the file, and mixing different memregs values in different objects ! may make them incompatible. This pragma is useful when a performance-critical function uses a memreg for temporary values, as it may allow you to reduce the number of memregs used. ! `ADDRESS NAME ADDRESS' For any declared symbols matching NAME, this does three things to that symbol: it forces the symbol to be located at the given address (a number), it forces the symbol to be volatile, and it changes the symbol's scope to be static. This pragma exists for compatibility with other compilers, but note that the common ! `1234H' numeric syntax is not supported (use `0x1234' instead). Example: #pragma ADDRESS port3 0x103 char port3; +  File: gcc.info, Node: MeP Pragmas, Next: RS/6000 and PowerPC Pragmas, Prev: M32C Pragmas, Up: Pragmas 6.61.4 MeP Pragmas ------------------ ! `custom io_volatile (on|off)' ! Overrides the command-line option `-mio-volatile' for the current file. Note that for compatibility with future GCC releases, this ! option should only be used once before any `io' variables in each file. ! `GCC coprocessor available REGISTERS' Specifies which coprocessor registers are available to the register allocator. REGISTERS may be a single register, register range separated by ellipses, or comma-separated list of those. Example: #pragma GCC coprocessor available $c0...$c10, $c28 ! `GCC coprocessor call_saved REGISTERS' Specifies which coprocessor registers are to be saved and restored by any function using them. REGISTERS may be a single register, register range separated by ellipses, or comma-separated list of *************** File: gcc.info, Node: MeP Pragmas, Nex *** 43600,43608 **** #pragma GCC coprocessor call_saved $c4...$c6, $c31 ! 'GCC coprocessor subclass '(A|B|C|D)' = REGISTERS' Creates and defines a register class. These register classes can ! be used by inline 'asm' constructs. REGISTERS may be a single register, register range separated by ellipses, or comma-separated list of those. Example: --- 44085,44093 ---- #pragma GCC coprocessor call_saved $c4...$c6, $c31 ! `GCC coprocessor subclass '(A|B|C|D)' = REGISTERS' Creates and defines a register class. These register classes can ! be used by inline `asm' constructs. REGISTERS may be a single register, register range separated by ellipses, or comma-separated list of those. Example: *************** File: gcc.info, Node: MeP Pragmas, Nex *** 43610,43616 **** asm ("cpfoo %0" : "=B" (x)); ! 'GCC disinterrupt NAME , NAME ...' For the named functions, the compiler adds code to disable interrupts for the duration of those functions. If any functions so named are not encountered in the source, a warning is emitted --- 44095,44101 ---- asm ("cpfoo %0" : "=B" (x)); ! `GCC disinterrupt NAME , NAME ...' For the named functions, the compiler adds code to disable interrupts for the duration of those functions. If any functions so named are not encountered in the source, a warning is emitted *************** File: gcc.info, Node: MeP Pragmas, Nex *** 43620,43626 **** #pragma disinterrupt bar, grill int foo () { ... } ! 'GCC call NAME , NAME ...' For the named functions, the compiler always uses a register-indirect call model when calling the named functions. Examples: --- 44105,44111 ---- #pragma disinterrupt bar, grill int foo () { ... } ! `GCC call NAME , NAME ...' For the named functions, the compiler always uses a register-indirect call model when calling the named functions. Examples: *************** File: gcc.info, Node: MeP Pragmas, Nex *** 43628,43633 **** --- 44113,44119 ---- extern int foo (); #pragma call foo +  File: gcc.info, Node: RS/6000 and PowerPC Pragmas, Next: S/390 Pragmas, Prev: MeP Pragmas, Up: Pragmas *************** File: gcc.info, Node: RS/6000 and Power *** 43635,43652 **** ---------------------------------- The RS/6000 and PowerPC targets define one pragma for controlling ! whether or not the 'longcall' attribute is added to function ! declarations by default. This pragma overrides the '-mlongcall' option, ! but not the 'longcall' and 'shortcall' attributes. *Note RS/6000 and ! PowerPC Options::, for more information about when long calls are and ! are not necessary. ! 'longcall (1)' ! Apply the 'longcall' attribute to all subsequent function declarations. ! 'longcall (0)' ! Do not apply the 'longcall' attribute to subsequent function declarations.  --- 44121,44138 ---- ---------------------------------- The RS/6000 and PowerPC targets define one pragma for controlling ! whether or not the `longcall' attribute is added to function ! declarations by default. This pragma overrides the `-mlongcall' ! option, but not the `longcall' and `shortcall' attributes. *Note ! RS/6000 and PowerPC Options::, for more information about when long ! calls are and are not necessary. ! `longcall (1)' ! Apply the `longcall' attribute to all subsequent function declarations. ! `longcall (0)' ! Do not apply the `longcall' attribute to subsequent function declarations.  *************** File: gcc.info, Node: S/390 Pragmas, N *** 43658,43668 **** The pragmas defined by the S/390 target correspond to the S/390 target function attributes and some the additional options: ! 'zvector' ! 'no-zvector' Note that options of the pragma, unlike options of the target ! attribute, do change the value of preprocessor macros like '__VEC__'. They can be specified as below: #pragma GCC target("string[,string]...") --- 44144,44154 ---- The pragmas defined by the S/390 target correspond to the S/390 target function attributes and some the additional options: ! `zvector' ! `no-zvector' Note that options of the pragma, unlike options of the target ! attribute, do change the value of preprocessor macros like `__VEC__'. They can be specified as below: #pragma GCC target("string[,string]...") *************** The following pragmas are available for *** 43678,43700 **** Darwin operating system. These are useful for compatibility with other Mac OS compilers. ! 'mark TOKENS...' This pragma is accepted, but has no effect. ! 'options align=ALIGNMENT' ! This pragma sets the alignment of fields in structures. The values ! of ALIGNMENT may be 'mac68k', to emulate m68k alignment, or ! 'power', to emulate PowerPC alignment. Uses of this pragma nest ! properly; to restore the previous setting, use 'reset' for the ALIGNMENT. ! 'segment TOKENS...' This pragma is accepted, but has no effect. ! 'unused (VAR [, VAR]...)' This pragma declares variables to be possibly unused. GCC does not produce warnings for the listed variables. The effect is similar ! to that of the 'unused' attribute, except that this pragma may appear anywhere within the variables' scopes.  --- 44164,44186 ---- Darwin operating system. These are useful for compatibility with other Mac OS compilers. ! `mark TOKENS...' This pragma is accepted, but has no effect. ! `options align=ALIGNMENT' ! This pragma sets the alignment of fields in structures. The ! values of ALIGNMENT may be `mac68k', to emulate m68k alignment, or ! `power', to emulate PowerPC alignment. Uses of this pragma nest ! properly; to restore the previous setting, use `reset' for the ALIGNMENT. ! `segment TOKENS...' This pragma is accepted, but has no effect. ! `unused (VAR [, VAR]...)' This pragma declares variables to be possibly unused. GCC does not produce warnings for the listed variables. The effect is similar ! to that of the `unused' attribute, except that this pragma may appear anywhere within the variables' scopes.  *************** File: gcc.info, Node: Solaris Pragmas, *** 43703,43732 **** 6.61.8 Solaris Pragmas ---------------------- ! The Solaris target supports '#pragma redefine_extname' (*note ! Symbol-Renaming Pragmas::). It also supports additional '#pragma' directives for compatibility with the system compiler. ! 'align ALIGNMENT (VARIABLE [, VARIABLE]...)' ! ! Increase the minimum alignment of each VARIABLE to ALIGNMENT. This ! is the same as GCC's 'aligned' attribute *note Variable Attributes::). Macro expansion occurs on the arguments to this pragma when compiling C and Objective-C. It does not currently ! occur when compiling C++, but this is a bug which may be fixed in a ! future release. ! ! 'fini (FUNCTION [, FUNCTION]...)' ! This pragma causes each listed FUNCTION to be called after main, or ! during shared module unloading, by adding a call to the '.fini' section. ! 'init (FUNCTION [, FUNCTION]...)' ! This pragma causes each listed FUNCTION to be called during ! initialization (before 'main') or during shared module loading, by ! adding a call to the '.init' section.  File: gcc.info, Node: Symbol-Renaming Pragmas, Next: Structure-Layout Pragmas, Prev: Solaris Pragmas, Up: Pragmas --- 44189,44216 ---- 6.61.8 Solaris Pragmas ---------------------- ! The Solaris target supports `#pragma redefine_extname' (*note ! Symbol-Renaming Pragmas::). It also supports additional `#pragma' directives for compatibility with the system compiler. ! `align ALIGNMENT (VARIABLE [, VARIABLE]...)' ! Increase the minimum alignment of each VARIABLE to ALIGNMENT. ! This is the same as GCC's `aligned' attribute *note Variable Attributes::). Macro expansion occurs on the arguments to this pragma when compiling C and Objective-C. It does not currently ! occur when compiling C++, but this is a bug which may be fixed in ! a future release. ! `fini (FUNCTION [, FUNCTION]...)' ! This pragma causes each listed FUNCTION to be called after main, ! or during shared module unloading, by adding a call to the `.fini' section. ! `init (FUNCTION [, FUNCTION]...)' This pragma causes each listed FUNCTION to be called during ! initialization (before `main') or during shared module loading, by ! adding a call to the `.init' section. !  File: gcc.info, Node: Symbol-Renaming Pragmas, Next: Structure-Layout Pragmas, Prev: Solaris Pragmas, Up: Pragmas *************** File: gcc.info, Node: Symbol-Renaming P *** 43734,43749 **** 6.61.9 Symbol-Renaming Pragmas ------------------------------ ! GCC supports a '#pragma' directive that changes the name used in ! assembly for a given declaration. While this pragma is supported on all platforms, it is intended primarily to provide compatibility with the ! Solaris system headers. This effect can also be achieved using the asm labels extension (*note Asm Labels::). ! 'redefine_extname OLDNAME NEWNAME' ! This pragma gives the C function OLDNAME the assembly symbol ! NEWNAME. The preprocessor macro '__PRAGMA_REDEFINE_EXTNAME' is defined if this pragma is available (currently on all platforms). This pragma and the asm labels extension interact in a complicated --- 44218,44232 ---- 6.61.9 Symbol-Renaming Pragmas ------------------------------ ! GCC supports a `#pragma' directive that changes the name used in ! assembly for a given declaration. While this pragma is supported on all platforms, it is intended primarily to provide compatibility with the ! Solaris system headers. This effect can also be achieved using the asm labels extension (*note Asm Labels::). ! `redefine_extname OLDNAME NEWNAME' This pragma gives the C function OLDNAME the assembly symbol ! NEWNAME. The preprocessor macro `__PRAGMA_REDEFINE_EXTNAME' is defined if this pragma is available (currently on all platforms). This pragma and the asm labels extension interact in a complicated *************** manner. Here are some corner cases you *** 43758,43768 **** 3. If either of the ways of changing the assembly name of a declaration are applied to a declaration whose assembly name has already been determined (either by a previous use of one of these ! features, or because the compiler needed the assembly name in order ! to generate code), and the new name is different, a warning issues ! and the name does not change. ! 4. The OLDNAME used by '#pragma redefine_extname' is always the C-language name.  --- 44241,44251 ---- 3. If either of the ways of changing the assembly name of a declaration are applied to a declaration whose assembly name has already been determined (either by a previous use of one of these ! features, or because the compiler needed the assembly name in ! order to generate code), and the new name is different, a warning ! issues and the name does not change. ! 4. The OLDNAME used by `#pragma redefine_extname' is always the C-language name.  *************** File: gcc.info, Node: Structure-Layout *** 43772,43814 **** -------------------------------- For compatibility with Microsoft Windows compilers, GCC supports a set ! of '#pragma' directives that change the maximum alignment of members of structures (other than zero-width bit-fields), unions, and classes ! subsequently defined. The N value below always is required to be a small power of two and specifies the new alignment in bytes. ! 1. '#pragma pack(N)' simply sets the new alignment. ! 2. '#pragma pack()' sets the alignment to the one that was in effect when compilation started (see also command-line option ! '-fpack-struct[=N]' *note Code Gen Options::). ! 3. '#pragma pack(push[,N])' pushes the current alignment setting on an ! internal stack and then optionally sets the new alignment. ! 4. '#pragma pack(pop)' restores the alignment setting to the one saved ! at the top of the internal stack (and removes that stack entry). ! Note that '#pragma pack([N])' does not influence this internal ! stack; thus it is possible to have '#pragma pack(push)' followed by ! multiple '#pragma pack(N)' instances and finalized by a single ! '#pragma pack(pop)'. ! Some targets, e.g. x86 and PowerPC, support the '#pragma ms_struct' directive which lays out structures and unions subsequently defined as ! the documented '__attribute__ ((ms_struct))'. ! 1. '#pragma ms_struct on' turns on the Microsoft layout. ! 2. '#pragma ms_struct off' turns off the Microsoft layout. ! 3. '#pragma ms_struct reset' goes back to the default layout. ! Most targets also support the '#pragma scalar_storage_order' directive which lays out structures and unions subsequently defined as the ! documented '__attribute__ ((scalar_storage_order))'. ! 1. '#pragma scalar_storage_order big-endian' sets the storage order of ! the scalar fields to big-endian. ! 2. '#pragma scalar_storage_order little-endian' sets the storage order of the scalar fields to little-endian. ! 3. '#pragma scalar_storage_order default' goes back to the endianness that was in effect when compilation started (see also command-line ! option '-fsso-struct=ENDIANNESS' *note C Dialect Options::).  File: gcc.info, Node: Weak Pragmas, Next: Diagnostic Pragmas, Prev: Structure-Layout Pragmas, Up: Pragmas --- 44255,44304 ---- -------------------------------- For compatibility with Microsoft Windows compilers, GCC supports a set ! of `#pragma' directives that change the maximum alignment of members of structures (other than zero-width bit-fields), unions, and classes ! subsequently defined. The N value below always is required to be a small power of two and specifies the new alignment in bytes. ! 1. `#pragma pack(N)' simply sets the new alignment. ! ! 2. `#pragma pack()' sets the alignment to the one that was in effect when compilation started (see also command-line option ! `-fpack-struct[=N]' *note Code Gen Options::). ! 3. `#pragma pack(push[,N])' pushes the current alignment setting on ! an internal stack and then optionally sets the new alignment. ! ! 4. `#pragma pack(pop)' restores the alignment setting to the one ! saved at the top of the internal stack (and removes that stack ! entry). Note that `#pragma pack([N])' does not influence this ! internal stack; thus it is possible to have `#pragma pack(push)' ! followed by multiple `#pragma pack(N)' instances and finalized by ! a single `#pragma pack(pop)'. ! ! Some targets, e.g. x86 and PowerPC, support the `#pragma ms_struct' directive which lays out structures and unions subsequently defined as ! the documented `__attribute__ ((ms_struct))'. ! 1. `#pragma ms_struct on' turns on the Microsoft layout. ! 2. `#pragma ms_struct off' turns off the Microsoft layout. ! ! 3. `#pragma ms_struct reset' goes back to the default layout. ! ! Most targets also support the `#pragma scalar_storage_order' directive which lays out structures and unions subsequently defined as the ! documented `__attribute__ ((scalar_storage_order))'. ! 1. `#pragma scalar_storage_order big-endian' sets the storage order ! of the scalar fields to big-endian. ! ! 2. `#pragma scalar_storage_order little-endian' sets the storage order of the scalar fields to little-endian. ! ! 3. `#pragma scalar_storage_order default' goes back to the endianness that was in effect when compilation started (see also command-line ! option `-fsso-struct=ENDIANNESS' *note C Dialect Options::).  File: gcc.info, Node: Weak Pragmas, Next: Diagnostic Pragmas, Prev: Structure-Layout Pragmas, Up: Pragmas *************** File: gcc.info, Node: Weak Pragmas, Ne *** 43816,43831 **** 6.61.11 Weak Pragmas -------------------- ! For compatibility with SVR4, GCC supports a set of '#pragma' directives for declaring symbols to be weak, and defining weak aliases. ! '#pragma weak SYMBOL' This pragma declares SYMBOL to be weak, as if the declaration had the attribute of the same name. The pragma may appear before or after the declaration of SYMBOL. It is not an error for SYMBOL to never be defined at all. ! '#pragma weak SYMBOL1 = SYMBOL2' This pragma declares SYMBOL1 to be a weak alias of SYMBOL2. It is an error if SYMBOL2 is not defined in the current translation unit. --- 44306,44321 ---- 6.61.11 Weak Pragmas -------------------- ! For compatibility with SVR4, GCC supports a set of `#pragma' directives for declaring symbols to be weak, and defining weak aliases. ! `#pragma weak SYMBOL' This pragma declares SYMBOL to be weak, as if the declaration had the attribute of the same name. The pragma may appear before or after the declaration of SYMBOL. It is not an error for SYMBOL to never be defined at all. ! `#pragma weak SYMBOL1 = SYMBOL2' This pragma declares SYMBOL1 to be a weak alias of SYMBOL2. It is an error if SYMBOL2 is not defined in the current translation unit. *************** File: gcc.info, Node: Diagnostic Pragma *** 43837,43858 **** GCC allows the user to selectively enable or disable certain types of diagnostics, and change the kind of the diagnostic. For example, a ! project's policy might require that all sources compile with '-Werror' but certain files might have exceptions allowing specific types of warnings. Or, a project might selectively enable diagnostics and treat them as errors depending on which preprocessor macros are defined. ! '#pragma GCC diagnostic KIND OPTION' ! Modifies the disposition of a diagnostic. Note that not all diagnostics are modifiable; at the moment only warnings (normally ! controlled by '-W...') can be controlled, and not all of them. Use ! '-fdiagnostics-show-option' to determine which diagnostics are controllable and which option controls them. ! KIND is 'error' to treat this diagnostic as an error, 'warning' to ! treat it like a warning (even if '-Werror' is in effect), or ! 'ignored' if the diagnostic is to be ignored. OPTION is a double quoted string that matches the command-line option. #pragma GCC diagnostic warning "-Wformat" --- 44327,44347 ---- GCC allows the user to selectively enable or disable certain types of diagnostics, and change the kind of the diagnostic. For example, a ! project's policy might require that all sources compile with `-Werror' but certain files might have exceptions allowing specific types of warnings. Or, a project might selectively enable diagnostics and treat them as errors depending on which preprocessor macros are defined. ! `#pragma GCC diagnostic KIND OPTION' Modifies the disposition of a diagnostic. Note that not all diagnostics are modifiable; at the moment only warnings (normally ! controlled by `-W...') can be controlled, and not all of them. ! Use `-fdiagnostics-show-option' to determine which diagnostics are controllable and which option controls them. ! KIND is `error' to treat this diagnostic as an error, `warning' to ! treat it like a warning (even if `-Werror' is in effect), or ! `ignored' if the diagnostic is to be ignored. OPTION is a double quoted string that matches the command-line option. #pragma GCC diagnostic warning "-Wformat" *************** them as errors depending on which prepro *** 43865,43876 **** pragmas occurring after a line do not affect diagnostics caused by that line. ! '#pragma GCC diagnostic push' ! '#pragma GCC diagnostic pop' ! Causes GCC to remember the state of the diagnostics as of each ! 'push', and restore to that point at each 'pop'. If a 'pop' has no ! matching 'push', the command-line options are restored. #pragma GCC diagnostic error "-Wuninitialized" foo(a); /* error is given for this one */ --- 44354,44364 ---- pragmas occurring after a line do not affect diagnostics caused by that line. ! `#pragma GCC diagnostic push' ! `#pragma GCC diagnostic pop' Causes GCC to remember the state of the diagnostics as of each ! `push', and restore to that point at each `pop'. If a `pop' has ! no matching `push', the command-line options are restored. #pragma GCC diagnostic error "-Wuninitialized" foo(a); /* error is given for this one */ *************** them as errors depending on which prepro *** 43882,43894 **** #pragma GCC diagnostic pop foo(d); /* depends on command-line options */ GCC also offers a simple mechanism for printing messages during compilation. ! '#pragma message STRING' ! ! Prints STRING as a compiler message on compilation. The message is ! informational only, and is neither a compilation warning nor an error. #pragma message "Compiling " __FILE__ "..." --- 44370,44382 ---- #pragma GCC diagnostic pop foo(d); /* depends on command-line options */ + GCC also offers a simple mechanism for printing messages during compilation. ! `#pragma message STRING' ! Prints STRING as a compiler message on compilation. The message ! is informational only, and is neither a compilation warning nor an error. #pragma message "Compiling " __FILE__ "..." *************** compilation. *** 43901,43927 **** TODO(Remember to fix this) ! prints '/tmp/file.c:4: note: #pragma message: TODO - Remember to fix this'.  File: gcc.info, Node: Visibility Pragmas, Next: Push/Pop Macro Pragmas, Prev: Diagnostic Pragmas, Up: Pragmas 6.61.13 Visibility Pragmas -------------------------- ! '#pragma GCC visibility push(VISIBILITY)' ! '#pragma GCC visibility pop' ! This pragma allows the user to set the visibility for multiple declarations without having to give each a visibility attribute (*note Function Attributes::). ! In C++, '#pragma GCC visibility' affects only namespace-scope declarations. Class members and template specializations are not affected; if you want to override the visibility for a particular member or instantiation, you must use an attribute.  File: gcc.info, Node: Push/Pop Macro Pragmas, Next: Function Specific Option Pragmas, Prev: Visibility Pragmas, Up: Pragmas --- 44389,44416 ---- TODO(Remember to fix this) ! prints `/tmp/file.c:4: note: #pragma message: TODO - Remember to fix this'. +  File: gcc.info, Node: Visibility Pragmas, Next: Push/Pop Macro Pragmas, Prev: Diagnostic Pragmas, Up: Pragmas 6.61.13 Visibility Pragmas -------------------------- ! `#pragma GCC visibility push(VISIBILITY)' ! `#pragma GCC visibility pop' This pragma allows the user to set the visibility for multiple declarations without having to give each a visibility attribute (*note Function Attributes::). ! In C++, `#pragma GCC visibility' affects only namespace-scope declarations. Class members and template specializations are not affected; if you want to override the visibility for a particular member or instantiation, you must use an attribute. +  File: gcc.info, Node: Push/Pop Macro Pragmas, Next: Function Specific Option Pragmas, Prev: Visibility Pragmas, Up: Pragmas *************** File: gcc.info, Node: Push/Pop Macro Pr *** 43929,43944 **** ------------------------------ For compatibility with Microsoft Windows compilers, GCC supports ! '#pragma push_macro("MACRO_NAME")' and '#pragma pop_macro("MACRO_NAME")'. ! '#pragma push_macro("MACRO_NAME")' ! This pragma saves the value of the macro named as MACRO_NAME to the ! top of the stack for this macro. ! '#pragma pop_macro("MACRO_NAME")' This pragma sets the value of the macro named as MACRO_NAME to the ! value on top of the stack for this macro. If the stack for MACRO_NAME is empty, the value of the macro remains unchanged. For example: --- 44418,44433 ---- ------------------------------ For compatibility with Microsoft Windows compilers, GCC supports ! `#pragma push_macro("MACRO_NAME")' and `#pragma pop_macro("MACRO_NAME")'. ! `#pragma push_macro("MACRO_NAME")' ! This pragma saves the value of the macro named as MACRO_NAME to ! the top of the stack for this macro. ! `#pragma pop_macro("MACRO_NAME")' This pragma sets the value of the macro named as MACRO_NAME to the ! value on top of the stack for this macro. If the stack for MACRO_NAME is empty, the value of the macro remains unchanged. For example: *************** pop_macro("MACRO_NAME")'. *** 43950,43957 **** #pragma pop_macro("X") int x [X]; ! In this example, the definition of X as 1 is saved by '#pragma ! push_macro' and restored by '#pragma pop_macro'.  File: gcc.info, Node: Function Specific Option Pragmas, Next: Loop-Specific Pragmas, Prev: Push/Pop Macro Pragmas, Up: Pragmas --- 44439,44446 ---- #pragma pop_macro("X") int x [X]; ! In this example, the definition of X as 1 is saved by `#pragma ! push_macro' and restored by `#pragma pop_macro'.  File: gcc.info, Node: Function Specific Option Pragmas, Next: Loop-Specific Pragmas, Prev: Push/Pop Macro Pragmas, Up: Pragmas *************** File: gcc.info, Node: Function Specific *** 43959,43999 **** 6.61.15 Function Specific Option Pragmas ---------------------------------------- ! '#pragma GCC target ("STRING"...)' ! This pragma allows you to set target specific options for functions defined later in the source file. One or more strings can be ! specified. Each function that is defined after this point is as if ! 'attribute((target("STRING")))' was specified for that function. ! The parenthesis around the options is optional. *Note Function ! Attributes::, for more information about the 'target' attribute and ! the attribute syntax. ! The '#pragma GCC target' pragma is presently implemented for x86, PowerPC, and Nios II targets only. ! '#pragma GCC optimize ("STRING"...)' ! This pragma allows you to set global optimization options for functions defined later in the source file. One or more strings can be specified. Each function that is defined after this point ! is as if 'attribute((optimize("STRING")))' was specified for that function. The parenthesis around the options is optional. *Note ! Function Attributes::, for more information about the 'optimize' attribute and the attribute syntax. ! '#pragma GCC push_options' ! '#pragma GCC pop_options' ! These pragmas maintain a stack of the current target and optimization options. It is intended for include files where you ! temporarily want to switch to using a different '#pragma GCC ! target' or '#pragma GCC optimize' and then to pop back to the previous options. ! '#pragma GCC reset_options' ! ! This pragma clears the current '#pragma GCC target' and '#pragma GCC optimize' to use the default switches as specified on the command line. --- 44448,44484 ---- 6.61.15 Function Specific Option Pragmas ---------------------------------------- ! `#pragma GCC target ("STRING"...)' This pragma allows you to set target specific options for functions defined later in the source file. One or more strings can be ! specified. Each function that is defined after this point is as ! if `attribute((target("STRING")))' was specified for that ! function. The parenthesis around the options is optional. *Note ! Function Attributes::, for more information about the `target' ! attribute and the attribute syntax. ! The `#pragma GCC target' pragma is presently implemented for x86, PowerPC, and Nios II targets only. ! `#pragma GCC optimize ("STRING"...)' This pragma allows you to set global optimization options for functions defined later in the source file. One or more strings can be specified. Each function that is defined after this point ! is as if `attribute((optimize("STRING")))' was specified for that function. The parenthesis around the options is optional. *Note ! Function Attributes::, for more information about the `optimize' attribute and the attribute syntax. ! `#pragma GCC push_options' ! `#pragma GCC pop_options' These pragmas maintain a stack of the current target and optimization options. It is intended for include files where you ! temporarily want to switch to using a different `#pragma GCC ! target' or `#pragma GCC optimize' and then to pop back to the previous options. ! `#pragma GCC reset_options' ! This pragma clears the current `#pragma GCC target' and `#pragma GCC optimize' to use the default switches as specified on the command line. *************** File: gcc.info, Node: Loop-Specific Pra *** 44003,44014 **** 6.61.16 Loop-Specific Pragmas ----------------------------- ! '#pragma GCC ivdep' With this pragma, the programmer asserts that there are no loop-carried ! dependencies which would prevent consecutive iterations of the following ! loop from executing concurrently with SIMD (single instruction multiple ! data) instructions. For example, the compiler can only unconditionally vectorize the following loop with the pragma: --- 44488,44499 ---- 6.61.16 Loop-Specific Pragmas ----------------------------- ! `#pragma GCC ivdep' With this pragma, the programmer asserts that there are no loop-carried ! dependencies which would prevent consecutive iterations of the ! following loop from executing concurrently with SIMD (single ! instruction multiple data) instructions. For example, the compiler can only unconditionally vectorize the following loop with the pragma: *************** following loop with the pragma: *** 44021,44029 **** a[i] = b[i] + c[i]; } ! In this example, using the 'restrict' qualifier had the same effect. In ! the following example, that would not be possible. Assume k < -m or k ! >= m. Only with the pragma, the compiler knows that it can unconditionally vectorize the following loop: void ignore_vec_dep (int *a, int k, int c, int m) --- 44506,44514 ---- a[i] = b[i] + c[i]; } ! In this example, using the `restrict' qualifier had the same effect. In ! the following example, that would not be possible. Assume k < -m or k ! >= m. Only with the pragma, the compiler knows that it can unconditionally vectorize the following loop: void ignore_vec_dep (int *a, int k, int c, int m) *************** structures and unions without names. Fo *** 44053,44060 **** } foo; In this example, you are able to access members of the unnamed union ! with code like 'foo.b'. Note that only unnamed structs and unions are ! allowed, you may not have, for example, an unnamed 'int'. You must never create such structures that cause ambiguous field definitions. For example, in this structure: --- 44538,44545 ---- } foo; In this example, you are able to access members of the unnamed union ! with code like `foo.b'. Note that only unnamed structs and unions are ! allowed, you may not have, for example, an unnamed `int'. You must never create such structures that cause ambiguous field definitions. For example, in this structure: *************** definitions. For example, in this struc *** 44066,44082 **** }; } foo; ! it is ambiguous which 'a' is being referred to with 'foo.a'. The compiler gives errors for such constructs. ! Unless '-fms-extensions' is used, the unnamed field must be a structure ! or union definition without a tag (for example, 'struct { int a; };'). ! If '-fms-extensions' is used, the field may also be a definition with a ! tag such as 'struct foo { int a; };', a reference to a previously ! defined structure or union such as 'struct foo;', or a reference to a ! 'typedef' name for a previously defined structure or union type. ! The option '-fplan9-extensions' enables '-fms-extensions' as well as two other extensions. First, a pointer to a structure is automatically converted to a pointer to an anonymous field for assignments and function calls. For example: --- 44551,44568 ---- }; } foo; ! it is ambiguous which `a' is being referred to with `foo.a'. The compiler gives errors for such constructs. ! Unless `-fms-extensions' is used, the unnamed field must be a ! structure or union definition without a tag (for example, `struct { int ! a; };'). If `-fms-extensions' is used, the field may also be a ! definition with a tag such as `struct foo { int a; };', a reference to ! a previously defined structure or union such as `struct foo;', or a ! reference to a `typedef' name for a previously defined structure or ! union type. ! The option `-fplan9-extensions' enables `-fms-extensions' as well as two other extensions. First, a pointer to a structure is automatically converted to a pointer to an anonymous field for assignments and function calls. For example: *************** function calls. For example: *** 44086,44097 **** extern void f1 (struct s1 *); void f2 (struct s2 *p) { f1 (p); } ! In the call to 'f1' inside 'f2', the pointer 'p' is converted into a pointer to the anonymous field. ! Second, when the type of an anonymous field is a 'typedef' for a ! 'struct' or 'union', code may refer to the field using the name of the ! 'typedef'. typedef struct { int a; } s1; struct s2 { s1; }; --- 44572,44583 ---- extern void f1 (struct s1 *); void f2 (struct s2 *p) { f1 (p); } ! In the call to `f1' inside `f2', the pointer `p' is converted into a pointer to the anonymous field. ! Second, when the type of an anonymous field is a `typedef' for a ! `struct' or `union', code may refer to the field using the name of the ! `typedef'. typedef struct { int a; } s1; struct s2 { s1; }; *************** allocated such that there is one instanc *** 44110,44131 **** thread. The runtime model GCC uses to implement this originates in the IA-64 processor-specific ABI, but has since been migrated to other processors as well. It requires significant support from the linker ! ('ld'), dynamic linker ('ld.so'), and system libraries ('libc.so' and ! 'libpthread.so'), so it is not available everywhere. At the user level, the extension is visible with a new storage class ! keyword: '__thread'. For example: __thread int i; extern __thread struct state s; static __thread char *p; ! The '__thread' specifier may be used alone, with the 'extern' or ! 'static' specifiers, but with no other storage class specifier. When ! used with 'extern' or 'static', '__thread' must appear immediately after ! the other storage class specifier. ! The '__thread' specifier may be applied to any global, file-scoped static, function-scoped static, or static data member of a class. It may not be applied to block-scoped automatic or non-static data member. --- 44596,44617 ---- thread. The runtime model GCC uses to implement this originates in the IA-64 processor-specific ABI, but has since been migrated to other processors as well. It requires significant support from the linker ! (`ld'), dynamic linker (`ld.so'), and system libraries (`libc.so' and ! `libpthread.so'), so it is not available everywhere. At the user level, the extension is visible with a new storage class ! keyword: `__thread'. For example: __thread int i; extern __thread struct state s; static __thread char *p; ! The `__thread' specifier may be used alone, with the `extern' or ! `static' specifiers, but with no other storage class specifier. When ! used with `extern' or `static', `__thread' must appear immediately ! after the other storage class specifier. ! The `__thread' specifier may be applied to any global, file-scoped static, function-scoped static, or static data member of a class. It may not be applied to block-scoped automatic or non-static data member. *************** File: gcc.info, Node: C99 Thread-Local *** 44161,44167 **** The following are a set of changes to ISO/IEC 9899:1999 (aka C99) that document the exact semantics of the language extension. ! * '5.1.2 Execution environments' Add new text after paragraph 1 --- 44647,44653 ---- The following are a set of changes to ISO/IEC 9899:1999 (aka C99) that document the exact semantics of the language extension. ! * `5.1.2 Execution environments' Add new text after paragraph 1 *************** document the exact semantics of the lang *** 44174,44210 **** terminated. However, objects with thread storage duration shall be initialized before thread startup. ! * '6.2.4 Storage durations of objects' Add new text before paragraph 3 An object whose identifier is declared with the storage-class ! specifier '__thread' has "thread storage duration". Its ! lifetime is the entire execution of the thread, and its stored ! value is initialized only once, prior to thread startup. ! * '6.4.1 Keywords' ! Add '__thread'. ! * '6.7.1 Storage-class specifiers' ! Add '__thread' to the list of storage class specifiers in paragraph ! 1. Change paragraph 2 to ! With the exception of '__thread', at most one storage-class ! specifier may be given [...]. The '__thread' specifier may be ! used alone, or immediately following 'extern' or 'static'. Add new text after paragraph 6 ! The declaration of an identifier for a variable that has block ! scope that specifies '__thread' shall also specify either ! 'extern' or 'static'. ! The '__thread' specifier shall be used only with variables.  File: gcc.info, Node: C++98 Thread-Local Edits, Prev: C99 Thread-Local Edits, Up: Thread-Local --- 44660,44697 ---- terminated. However, objects with thread storage duration shall be initialized before thread startup. ! * `6.2.4 Storage durations of objects' Add new text before paragraph 3 An object whose identifier is declared with the storage-class ! specifier `__thread' has "thread storage duration". Its ! lifetime is the entire execution of the thread, and its ! stored value is initialized only once, prior to thread ! startup. ! * `6.4.1 Keywords' ! Add `__thread'. ! * `6.7.1 Storage-class specifiers' ! Add `__thread' to the list of storage class specifiers in ! paragraph 1. Change paragraph 2 to ! With the exception of `__thread', at most one storage-class ! specifier may be given [...]. The `__thread' specifier may ! be used alone, or immediately following `extern' or `static'. Add new text after paragraph 6 ! The declaration of an identifier for a variable that has ! block scope that specifies `__thread' shall also specify ! either `extern' or `static'. ! The `__thread' specifier shall be used only with variables.  File: gcc.info, Node: C++98 Thread-Local Edits, Prev: C99 Thread-Local Edits, Up: Thread-Local *************** that document the exact semantics of the *** 44231,44250 **** * [lex.key] ! Add '__thread'. * [basic.start.main] Add after paragraph 5 ! The thread that begins execution at the 'main' function is called the "main thread". It is implementation defined how functions beginning threads other than the main thread are ! designated or typed. A function so designated, as well as the ! 'main' function, is called a "thread startup function". It is ! implementation defined what happens if a thread startup function returns. It is implementation defined what happens ! to other threads when any thread calls 'exit'. * [basic.start.init] --- 44718,44737 ---- * [lex.key] ! Add `__thread'. * [basic.start.main] Add after paragraph 5 ! The thread that begins execution at the `main' function is called the "main thread". It is implementation defined how functions beginning threads other than the main thread are ! designated or typed. A function so designated, as well as ! the `main' function, is called a "thread startup function". ! It is implementation defined what happens if a thread startup function returns. It is implementation defined what happens ! to other threads when any thread calls `exit'. * [basic.start.init] *************** that document the exact semantics of the *** 44252,44259 **** The storage for an object of thread storage duration shall be statically initialized before the first statement of the ! thread startup function. An object of thread storage duration ! shall not require dynamic initialization. * [basic.start.term] --- 44739,44746 ---- The storage for an object of thread storage duration shall be statically initialized before the first statement of the ! thread startup function. An object of thread storage ! duration shall not require dynamic initialization. * [basic.start.term] *************** that document the exact semantics of the *** 44270,44289 **** Change paragraph 2 ! Thread, static, and automatic storage durations are associated ! with objects introduced by declarations [...]. ! Add '__thread' to the list of specifiers in paragraph 3. * [basic.stc.thread] New section before [basic.stc.static] ! The keyword '__thread' applied to a non-local object gives the object thread storage duration. ! A local variable or class data member declared both 'static' ! and '__thread' gives the variable or member thread storage duration. * [basic.stc.static] --- 44757,44776 ---- Change paragraph 2 ! Thread, static, and automatic storage durations are ! associated with objects introduced by declarations [...]. ! Add `__thread' to the list of specifiers in paragraph 3. * [basic.stc.thread] New section before [basic.stc.static] ! The keyword `__thread' applied to a non-local object gives the object thread storage duration. ! A local variable or class data member declared both `static' ! and `__thread' gives the variable or member thread storage duration. * [basic.stc.static] *************** that document the exact semantics of the *** 44295,44329 **** * [dcl.stc] ! Add '__thread' to the list in paragraph 1. Change paragraph 1 ! With the exception of '__thread', at most one STORAGE-CLASS-SPECIFIER shall appear in a given ! DECL-SPECIFIER-SEQ. The '__thread' specifier may be used ! alone, or immediately following the 'extern' or 'static' specifiers. [...] Add after paragraph 5 ! The '__thread' specifier can be applied only to the names of objects and to anonymous unions. * [class.mem] Add after paragraph 6 ! Non-'static' members shall not be '__thread'.  File: gcc.info, Node: Binary constants, Prev: Thread-Local, Up: C Extensions ! 6.64 Binary Constants using the '0b' Prefix =========================================== Integer constants can be written as binary constants, consisting of a ! sequence of '0' and '1' digits, prefixed by '0b' or '0B'. This is particularly useful in environments that operate a lot on the bit level (like microcontrollers). --- 44782,44816 ---- * [dcl.stc] ! Add `__thread' to the list in paragraph 1. Change paragraph 1 ! With the exception of `__thread', at most one STORAGE-CLASS-SPECIFIER shall appear in a given ! DECL-SPECIFIER-SEQ. The `__thread' specifier may be used ! alone, or immediately following the `extern' or `static' specifiers. [...] Add after paragraph 5 ! The `__thread' specifier can be applied only to the names of objects and to anonymous unions. * [class.mem] Add after paragraph 6 ! Non-`static' members shall not be `__thread'.  File: gcc.info, Node: Binary constants, Prev: Thread-Local, Up: C Extensions ! 6.64 Binary Constants using the `0b' Prefix =========================================== Integer constants can be written as binary constants, consisting of a ! sequence of `0' and `1' digits, prefixed by `0b' or `0B'. This is particularly useful in environments that operate a lot on the bit level (like microcontrollers). *************** particularly useful in environments that *** 44335,44341 **** i = 0b101010; The type of these constants follows the same rules as for octal or ! hexadecimal integer constants, so suffixes like 'L' or 'UL' can be applied.  --- 44822,44828 ---- i = 0b101010; The type of these constants follows the same rules as for octal or ! hexadecimal integer constants, so suffixes like `L' or `UL' can be applied.  *************** The GNU compiler provides these extensio *** 44348,44355 **** can also use most of the C language extensions in your C++ programs). If you want to write code that checks whether these features are available, you can test for the GNU compiler the same way as for C ! programs: check for a predefined macro '__GNUC__'. You can also use ! '__GNUG__' to test specifically for GNU C++ (*note Predefined Macros: (cpp)Common Predefined Macros.). * Menu: --- 44835,44842 ---- can also use most of the C language extensions in your C++ programs). If you want to write code that checks whether these features are available, you can test for the GNU compiler the same way as for C ! programs: check for a predefined macro `__GNUC__'. You can also use ! `__GNUG__' to test specifically for GNU C++ (*note Predefined Macros: (cpp)Common Predefined Macros.). * Menu: *************** programs: check for a predefined macro ' *** 44362,44368 **** * Template Instantiation:: Methods for ensuring that exactly one copy of each needed template instantiation is emitted. * Bound member functions:: You can extract a function pointer to the ! method denoted by a '->*' or '.*' expression. * C++ Attributes:: Variable, function, and type attributes for C++ only. * Function Multiversioning:: Declaring multiple function versions. * Namespace Association:: Strong using-directives for namespace association. --- 44849,44855 ---- * Template Instantiation:: Methods for ensuring that exactly one copy of each needed template instantiation is emitted. * Bound member functions:: You can extract a function pointer to the ! method denoted by a `->*' or `.*' expression. * C++ Attributes:: Variable, function, and type attributes for C++ only. * Function Multiversioning:: Declaring multiple function versions. * Namespace Association:: Strong using-directives for namespace association. *************** lvalueness of expressions between C and *** 44386,44393 **** G++ behaves the same as GCC for volatile access, *Note Volatiles: C Extensions, for a description of GCC's behavior. ! The C and C++ language specifications differ when an object is accessed ! in a void context: volatile int *src = SOMEVALUE; *src; --- 44873,44880 ---- G++ behaves the same as GCC for volatile access, *Note Volatiles: C Extensions, for a description of GCC's behavior. ! The C and C++ language specifications differ when an object is ! accessed in a void context: volatile int *src = SOMEVALUE; *src; *************** File: gcc.info, Node: Restricted Pointe *** 44429,44437 **** ================================ As with the C front end, G++ understands the C99 feature of restricted ! pointers, specified with the '__restrict__', or '__restrict' type ! qualifier. Because you cannot compile C++ by specifying the '-std=c99' ! language flag, 'restrict' is not a keyword in C++. In addition to allowing restricted pointers, you can specify restricted references, which indicate that the reference is not aliased in the --- 44916,44924 ---- ================================ As with the C front end, G++ understands the C99 feature of restricted ! pointers, specified with the `__restrict__', or `__restrict' type ! qualifier. Because you cannot compile C++ by specifying the `-std=c99' ! language flag, `restrict' is not a keyword in C++. In addition to allowing restricted pointers, you can specify restricted references, which indicate that the reference is not aliased in the *************** local context. *** 44442,44468 **** /* ... */ } ! In the body of 'fn', RPTR points to an unaliased integer and RREF refers ! to a (different) unaliased integer. You may also specify whether a member function's THIS pointer is ! unaliased by using '__restrict__' as a member function qualifier. void T::fn () __restrict__ { /* ... */ } ! Within the body of 'T::fn', THIS has the effective definition 'T *__restrict__ const this'. Notice that the interpretation of a ! '__restrict__' member function qualifier is different to that of 'const' ! or 'volatile' qualifier, in that it is applied to the pointer rather ! than the object. This is consistent with other compilers that implement ! restricted pointers. ! As with all outermost parameter qualifiers, '__restrict__' is ignored in function definition matching. This means you only need to specify ! '__restrict__' in a function definition, rather than in a function prototype as well.  --- 44929,44955 ---- /* ... */ } ! In the body of `fn', RPTR points to an unaliased integer and RREF ! refers to a (different) unaliased integer. You may also specify whether a member function's THIS pointer is ! unaliased by using `__restrict__' as a member function qualifier. void T::fn () __restrict__ { /* ... */ } ! Within the body of `T::fn', THIS has the effective definition `T *__restrict__ const this'. Notice that the interpretation of a ! `__restrict__' member function qualifier is different to that of ! `const' or `volatile' qualifier, in that it is applied to the pointer ! rather than the object. This is consistent with other compilers that ! implement restricted pointers. ! As with all outermost parameter qualifiers, `__restrict__' is ignored in function definition matching. This means you only need to specify ! `__restrict__' in a function definition, rather than in a function prototype as well.  *************** clever. *** 44480,44495 **** Inline Functions Inline functions are typically defined in a header file which can be included in many different compilations. Hopefully they can ! usually be inlined, but sometimes an out-of-line copy is necessary, ! if the address of the function is taken or if inlining fails. In ! general, we emit an out-of-line copy in all translation units where ! one is needed. As an exception, we only emit inline virtual ! functions with the vtable, since it always requires a copy. Local static variables and string constants used in an inline ! function are also considered to have vague linkage, since they must ! be shared between all inlined and out-of-line instances of the ! function. VTables C++ virtual functions are implemented in most compilers using a --- 44967,44982 ---- Inline Functions Inline functions are typically defined in a header file which can be included in many different compilations. Hopefully they can ! usually be inlined, but sometimes an out-of-line copy is ! necessary, if the address of the function is taken or if inlining ! fails. In general, we emit an out-of-line copy in all translation ! units where one is needed. As an exception, we only emit inline ! virtual functions with the vtable, since it always requires a copy. Local static variables and string constants used in an inline ! function are also considered to have vague linkage, since they ! must be shared between all inlined and out-of-line instances of ! the function. VTables C++ virtual functions are implemented in most compilers using a *************** VTables *** 44506,44526 **** Make sure that any inline virtuals are declared inline in the class body, even if they are not defined there. ! 'type_info' objects C++ requires information about types to be written out in order to ! implement 'dynamic_cast', 'typeid' and exception handling. For polymorphic classes (classes with virtual functions), the ! 'type_info' object is written out along with the vtable so that ! 'dynamic_cast' can determine the dynamic type of a class object at ! run time. For all other types, we write out the 'type_info' object ! when it is used: when applying 'typeid' to an expression, throwing ! an object, or referring to a type in a catch clause or exception ! specification. Template Instantiations Most everything in this section also applies to template ! instantiations, but there are other options as well. *Note Where's ! the Template?: Template Instantiation. When used with GNU ld version 2.8 or later on an ELF system such as GNU/Linux or Solaris 2, or on Microsoft Windows, duplicate copies of --- 44993,45014 ---- Make sure that any inline virtuals are declared inline in the class body, even if they are not defined there. ! `type_info' objects C++ requires information about types to be written out in order to ! implement `dynamic_cast', `typeid' and exception handling. For polymorphic classes (classes with virtual functions), the ! `type_info' object is written out along with the vtable so that ! `dynamic_cast' can determine the dynamic type of a class object at ! run time. For all other types, we write out the `type_info' ! object when it is used: when applying `typeid' to an expression, ! throwing an object, or referring to a type in a catch clause or ! exception specification. Template Instantiations Most everything in this section also applies to template ! instantiations, but there are other options as well. *Note ! Where's the Template?: Template Instantiation. ! When used with GNU ld version 2.8 or later on an ELF system such as GNU/Linux or Solaris 2, or on Microsoft Windows, duplicate copies of *************** File: gcc.info, Node: C++ Interface, N *** 44546,44623 **** 7.4 C++ Interface and Implementation Pragmas ============================================ ! '#pragma interface' and '#pragma implementation' provide the user with a ! way of explicitly directing the compiler to emit entities with vague linkage (and debugging information) in a particular translation unit. ! _Note:_ These '#pragma's have been superceded as of GCC 2.7.2 by COMDAT ! support and the "key method" heuristic mentioned in *note Vague Linkage::. Using them can actually cause your program to grow due to unnecessary out-of-line copies of inline functions. ! '#pragma interface' ! '#pragma interface "SUBDIR/OBJECTS.h"' ! Use this directive in _header files_ that define object classes, to ! save space in most of the object files that use those classes. Normally, local copies of certain information (backup copies of inline member functions, debugging information, and the internal tables that implement virtual functions) must be kept in each object file that includes class definitions. You can use this pragma to avoid such duplication. When a header file containing ! '#pragma interface' is included in a compilation, this auxiliary information is not generated (unless the main input source file ! itself uses '#pragma implementation'). Instead, the object files contain references to be resolved at link time. The second form of this directive is useful for the case where you have multiple headers with the same name in different directories. ! If you use this form, you must specify the same string to '#pragma implementation'. ! '#pragma implementation' ! '#pragma implementation "OBJECTS.h"' Use this pragma in a _main input file_, when you want full output from included header files to be generated (and made globally ! visible). The included header file, in turn, should use '#pragma interface'. Backup copies of inline member functions, debugging information, and the internal tables used to implement virtual functions are all generated in implementation files. ! If you use '#pragma implementation' with no argument, it applies to ! an include file with the same basename(1) as your source file. For ! example, in 'allclass.cc', giving just '#pragma implementation' by ! itself is equivalent to '#pragma implementation "allclass.h"'. Use the string argument if you want a single implementation file to include code from multiple header files. (You must also use ! '#include' to include the header file; '#pragma implementation' only specifies how to use the file--it doesn't actually include it.) There is no way to split up the contents of a single header file into multiple implementation files. ! '#pragma implementation' and '#pragma interface' also have an effect on ! function inlining. ! If you define a class in a header file marked with '#pragma interface', ! the effect on an inline function defined in that class is similar to an ! explicit 'extern' declaration--the compiler emits no code at all to ! define an independent version of the function. Its definition is used ! only for inlining with its callers. Conversely, when you include the same header file in a main source file ! that declares it as '#pragma implementation', the compiler emits code ! for the function itself; this defines a version of the function that can ! be found via pointers (or by callers compiled without inlining). If all ! calls to the function can be inlined, you can avoid emitting the ! function by compiling with '-fno-implement-inlines'. If any calls are not inlined, you will get linker errors. ! ---------- Footnotes ---------- ! (1) A file's "basename" is the name stripped of all leading path ! information and of trailing suffixes, such as '.h' or '.C' or '.cc'.  File: gcc.info, Node: Template Instantiation, Next: Bound member functions, Prev: C++ Interface, Up: C++ Extensions --- 45034,45111 ---- 7.4 C++ Interface and Implementation Pragmas ============================================ ! `#pragma interface' and `#pragma implementation' provide the user with ! a way of explicitly directing the compiler to emit entities with vague linkage (and debugging information) in a particular translation unit. ! _Note:_ These `#pragma's have been superceded as of GCC 2.7.2 by ! COMDAT support and the "key method" heuristic mentioned in *note Vague Linkage::. Using them can actually cause your program to grow due to unnecessary out-of-line copies of inline functions. ! `#pragma interface' ! `#pragma interface "SUBDIR/OBJECTS.h"' ! Use this directive in _header files_ that define object classes, ! to save space in most of the object files that use those classes. Normally, local copies of certain information (backup copies of inline member functions, debugging information, and the internal tables that implement virtual functions) must be kept in each object file that includes class definitions. You can use this pragma to avoid such duplication. When a header file containing ! `#pragma interface' is included in a compilation, this auxiliary information is not generated (unless the main input source file ! itself uses `#pragma implementation'). Instead, the object files contain references to be resolved at link time. The second form of this directive is useful for the case where you have multiple headers with the same name in different directories. ! If you use this form, you must specify the same string to `#pragma implementation'. ! `#pragma implementation' ! `#pragma implementation "OBJECTS.h"' Use this pragma in a _main input file_, when you want full output from included header files to be generated (and made globally ! visible). The included header file, in turn, should use `#pragma interface'. Backup copies of inline member functions, debugging information, and the internal tables used to implement virtual functions are all generated in implementation files. ! If you use `#pragma implementation' with no argument, it applies to ! an include file with the same basename(1) as your source file. ! For example, in `allclass.cc', giving just `#pragma implementation' ! by itself is equivalent to `#pragma implementation "allclass.h"'. Use the string argument if you want a single implementation file to include code from multiple header files. (You must also use ! `#include' to include the header file; `#pragma implementation' only specifies how to use the file--it doesn't actually include it.) There is no way to split up the contents of a single header file into multiple implementation files. ! `#pragma implementation' and `#pragma interface' also have an effect ! on function inlining. ! If you define a class in a header file marked with `#pragma ! interface', the effect on an inline function defined in that class is ! similar to an explicit `extern' declaration--the compiler emits no code ! at all to define an independent version of the function. Its ! definition is used only for inlining with its callers. Conversely, when you include the same header file in a main source file ! that declares it as `#pragma implementation', the compiler emits code ! for the function itself; this defines a version of the function that ! can be found via pointers (or by callers compiled without inlining). ! If all calls to the function can be inlined, you can avoid emitting the ! function by compiling with `-fno-implement-inlines'. If any calls are not inlined, you will get linker errors. ! ---------- Footnotes ---------- ! (1) A file's "basename" is the name stripped of all leading path ! information and of trailing suffixes, such as `.h' or `.C' or `.cc'.  File: gcc.info, Node: Template Instantiation, Next: Bound member functions, Prev: C++ Interface, Up: C++ Extensions *************** problem, which are referred to as the Bo *** 44634,44641 **** model. Borland model ! Borland C++ solved the template instantiation problem by adding the ! code equivalent of common blocks to their linker; the compiler emits template instances in each translation unit that uses them, and the linker collapses them together. The advantage of this model is that the linker only has to consider the object files --- 45122,45129 ---- model. Borland model ! Borland C++ solved the template instantiation problem by adding ! the code equivalent of common blocks to their linker; the compiler emits template instances in each translation unit that uses them, and the linker collapses them together. The advantage of this model is that the linker only has to consider the object files *************** Borland model *** 44648,44669 **** Cfront model The AT&T C++ translator, Cfront, solved the template instantiation problem by creating the notion of a template repository, an ! automatically maintained place where template instances are stored. ! A more modern version of the repository works as follows: As ! individual object files are built, the compiler places any template ! definitions and instantiations encountered in the repository. At ! link time, the link wrapper adds in the objects in the repository ! and compiles any needed instances that were not previously emitted. ! The advantages of this model are more optimal compilation speed and ! the ability to use the system linker; to implement the Borland ! model a compiler vendor also needs to replace the linker. The ! disadvantages are vastly increased complexity, and thus potential ! for error; for some code this can be just as transparent, but in ! practice it can been very difficult to build multiple programs in ! one directory and one program in multiple directories. Code ! written for this model tends to separate definitions of non-inline ! member templates into a separate file, which should be compiled ! separately. G++ implements the Borland model on targets where the linker supports it, including ELF targets (such as GNU/Linux), Mac OS X and Microsoft --- 45136,45157 ---- Cfront model The AT&T C++ translator, Cfront, solved the template instantiation problem by creating the notion of a template repository, an ! automatically maintained place where template instances are ! stored. A more modern version of the repository works as follows: ! As individual object files are built, the compiler places any ! template definitions and instantiations encountered in the ! repository. At link time, the link wrapper adds in the objects in ! the repository and compiles any needed instances that were not ! previously emitted. The advantages of this model are more optimal ! compilation speed and the ability to use the system linker; to ! implement the Borland model a compiler vendor also needs to ! replace the linker. The disadvantages are vastly increased ! complexity, and thus potential for error; for some code this can be ! just as transparent, but in practice it can been very difficult to ! build multiple programs in one directory and one program in ! multiple directories. Code written for this model tends to ! separate definitions of non-inline member templates into a ! separate file, which should be compiled separately. G++ implements the Borland model on targets where the linker supports it, including ELF targets (such as GNU/Linux), Mac OS X and Microsoft *************** instantiations: *** 44682,44688 **** explicit instantiation in one object file, and preventing the compiler from doing implicit instantiations in any other object files by using an explicit instantiation declaration, using the ! 'extern template' syntax: extern template int max (int, int); --- 45170,45176 ---- explicit instantiation in one object file, and preventing the compiler from doing implicit instantiations in any other object files by using an explicit instantiation declaration, using the ! `extern template' syntax: extern template int max (int, int); *************** instantiations: *** 44691,44702 **** Explicit instantiations can be used for the largest or most frequently duplicated instances, without having to know exactly ! which other instances are used in the rest of the program. You can ! scatter the explicit instantiations throughout your program, perhaps putting them in the translation units where the instances are used or the translation units that define the templates ! themselves; you can put all of the explicit instantiations you need ! into one big file; or you can create small files like #include "Foo.h" #include "Foo.cc" --- 45179,45190 ---- Explicit instantiations can be used for the largest or most frequently duplicated instances, without having to know exactly ! which other instances are used in the rest of the program. You ! can scatter the explicit instantiations throughout your program, perhaps putting them in the translation units where the instances are used or the translation units that define the templates ! themselves; you can put all of the explicit instantiations you ! need into one big file; or you can create small files like #include "Foo.h" #include "Foo.cc" *************** instantiations: *** 44709,44723 **** instantiation library from those. This is the simplest option, but also offers flexibility and ! fine-grained control when necessary. It is also the most portable alternative and programs using this approach will work with most modern compilers. ! 2. Compile your template-using code with '-frepo'. The compiler ! generates files with the extension '.rpo' listing all of the template instantiations used in the corresponding object files that ! could be instantiated there; the link wrapper, 'collect2', then ! updates the '.rpo' files to tell the compiler where to place those instantiations and rebuild any affected object files. The link-time overhead is negligible after the first pass, as the compiler continues to place the instantiations in the same files. --- 45197,45211 ---- instantiation library from those. This is the simplest option, but also offers flexibility and ! fine-grained control when necessary. It is also the most portable alternative and programs using this approach will work with most modern compilers. ! 2. Compile your template-using code with `-frepo'. The compiler ! generates files with the extension `.rpo' listing all of the template instantiations used in the corresponding object files that ! could be instantiated there; the link wrapper, `collect2', then ! updates the `.rpo' files to tell the compiler where to place those instantiations and rebuild any affected object files. The link-time overhead is negligible after the first pass, as the compiler continues to place the instantiations in the same files. *************** instantiations: *** 44726,44743 **** Borland model, as it usually just works. Code written for the Cfront model needs to be modified so that the template definitions are available at one or more points of instantiation; usually this ! is as simple as adding '#include ' to the end of each template header. For library code, if you want the library to provide all of the template instantiations it needs, just try to link all of its object files together; the link will fail, but cause the instantiations to be generated as a side effect. Be warned, ! however, that this may cause conflicts if multiple libraries try to ! provide the same instantiations. For greater control, use explicit ! instantiation as described in the next option. ! 3. Compile your code with '-fno-implicit-templates' to disable the implicit generation of template instances, and explicitly instantiate all the ones you use. This approach requires more knowledge of exactly which instances you need than do the others, --- 45214,45231 ---- Borland model, as it usually just works. Code written for the Cfront model needs to be modified so that the template definitions are available at one or more points of instantiation; usually this ! is as simple as adding `#include ' to the end of each template header. For library code, if you want the library to provide all of the template instantiations it needs, just try to link all of its object files together; the link will fail, but cause the instantiations to be generated as a side effect. Be warned, ! however, that this may cause conflicts if multiple libraries try ! to provide the same instantiations. For greater control, use ! explicit instantiation as described in the next option. ! 3. Compile your code with `-fno-implicit-templates' to disable the implicit generation of template instances, and explicitly instantiate all the ones you use. This approach requires more knowledge of exactly which instances you need than do the others, *************** instantiations: *** 44745,44765 **** ensure that only the intended instances are used. If you are using Cfront-model code, you can probably get away with ! not using '-fno-implicit-templates' when compiling files that don't ! '#include' the member template definitions. If you use one big file to do the instantiations, you may want to ! compile it without '-fno-implicit-templates' so you get all of the instances required by your explicit instantiations (but not by any other files) without having to specify them as well. ! In addition to forward declaration of explicit instantiations (with ! 'extern'), G++ has extended the template instantiation syntax to ! support instantiation of the compiler support data for a template ! class (i.e. the vtable) without instantiating any of its members ! (with 'inline'), and instantiation of only the static data members ! of a template class, without the support data or member functions ! (with 'static'): inline template class Foo; static template class Foo; --- 45233,45253 ---- ensure that only the intended instances are used. If you are using Cfront-model code, you can probably get away with ! not using `-fno-implicit-templates' when compiling files that don't ! `#include' the member template definitions. If you use one big file to do the instantiations, you may want to ! compile it without `-fno-implicit-templates' so you get all of the instances required by your explicit instantiations (but not by any other files) without having to specify them as well. ! In addition to forward declaration of explicit instantiations ! (with `extern'), G++ has extended the template instantiation ! syntax to support instantiation of the compiler support data for a ! template class (i.e. the vtable) without instantiating any of its ! members (with `inline'), and instantiation of only the static data ! members of a template class, without the support data or member ! functions (with `static'): inline template class Foo; static template class Foo; *************** File: gcc.info, Node: Bound member func *** 44772,44778 **** In C++, pointer to member functions (PMFs) are implemented using a wide pointer of sorts to handle all the possible call mechanisms; the PMF ! needs to store information about how to adjust the 'this' pointer, and if the function pointed to is virtual, where to find the vtable, and where in the vtable to look for the member function. If you are using PMFs in an inner loop, you should really reconsider that decision. If --- 45260,45266 ---- In C++, pointer to member functions (PMFs) are implemented using a wide pointer of sorts to handle all the possible call mechanisms; the PMF ! needs to store information about how to adjust the `this' pointer, and if the function pointed to is virtual, where to find the vtable, and where in the vtable to look for the member function. If you are using PMFs in an inner loop, you should really reconsider that decision. If *************** function calls. *** 44793,44805 **** fptr p = (fptr)(a.*fp); ! For PMF constants (i.e. expressions of the form '&Klasse::Member'), no object is needed to obtain the address of the function. They can be converted to function pointers directly: fptr p1 = (fptr)(&A::foo); ! You must specify '-Wno-pmf-conversions' to use this extension.  File: gcc.info, Node: C++ Attributes, Next: Function Multiversioning, Prev: Bound member functions, Up: C++ Extensions --- 45281,45293 ---- fptr p = (fptr)(a.*fp); ! For PMF constants (i.e. expressions of the form `&Klasse::Member'), no object is needed to obtain the address of the function. They can be converted to function pointers directly: fptr p1 = (fptr)(&A::foo); ! You must specify `-Wno-pmf-conversions' to use this extension.  File: gcc.info, Node: C++ Attributes, Next: Function Multiversioning, Prev: Bound member functions, Up: C++ Extensions *************** File: gcc.info, Node: C++ Attributes, *** 44809,44825 **** Some attributes only make sense for C++ programs. ! 'abi_tag ("TAG", ...)' ! The 'abi_tag' attribute can be applied to a function, variable, or class declaration. It modifies the mangled name of the entity to incorporate the tag name, in order to distinguish the function or class from an earlier version with a different ABI; perhaps the ! class has changed size, or the function has a different return type ! that is not encoded in the mangled name. The attribute can also be applied to an inline namespace, but does not affect the mangled name of the namespace; in this case it is ! only used for '-Wabi-tag' warnings and automatic tagging of functions and variables. Tagging inline namespaces is generally preferable to tagging individual declarations, but the latter is sometimes necessary, such as when only certain members of a class --- 45297,45313 ---- Some attributes only make sense for C++ programs. ! `abi_tag ("TAG", ...)' ! The `abi_tag' attribute can be applied to a function, variable, or class declaration. It modifies the mangled name of the entity to incorporate the tag name, in order to distinguish the function or class from an earlier version with a different ABI; perhaps the ! class has changed size, or the function has a different return ! type that is not encoded in the mangled name. The attribute can also be applied to an inline namespace, but does not affect the mangled name of the namespace; in this case it is ! only used for `-Wabi-tag' warnings and automatic tagging of functions and variables. Tagging inline namespaces is generally preferable to tagging individual declarations, but the latter is sometimes necessary, such as when only certain members of a class *************** Some attributes only make sense for C++ *** 44829,44869 **** strings are sorted on output, so the order of the list is unimportant. ! A redeclaration of an entity must not add new ABI tags, since doing ! so would change the mangled name. The ABI tags apply to a name, so all instantiations and specializations of a template have the same tags. The attribute will be ignored if applied to an explicit specialization or instantiation. ! The '-Wabi-tag' flag enables a warning about a class which does not ! have all the ABI tags used by its subobjects and virtual functions; ! for users with code that needs to coexist with an earlier ABI, ! using this option can help to find all affected types that need to ! be tagged. When a type involving an ABI tag is used as the type of a variable or return type of a function where that tag is not already present in the signature of the function, the tag is automatically applied ! to the variable or function. '-Wabi-tag' also warns about this situation; this warning can be avoided by explicitly tagging the variable or function or moving it into a tagged inline namespace. ! 'init_priority (PRIORITY)' ! In Standard C++, objects defined at namespace scope are guaranteed to be initialized in an order in strict accordance with that of their definitions _in a given translation unit_. No guarantee is made for initializations across translation units. However, GNU C++ allows users to control the order of initialization of objects ! defined at namespace scope with the 'init_priority' attribute by specifying a relative PRIORITY, a constant integral expression currently bounded between 101 and 65535 inclusive. Lower numbers indicate a higher priority. ! In the following example, 'A' would normally be created before 'B', ! but the 'init_priority' attribute reverses that order: Some_Class A __attribute__ ((init_priority (2000))); Some_Class B __attribute__ ((init_priority (543))); --- 45317,45356 ---- strings are sorted on output, so the order of the list is unimportant. ! A redeclaration of an entity must not add new ABI tags, since ! doing so would change the mangled name. The ABI tags apply to a name, so all instantiations and specializations of a template have the same tags. The attribute will be ignored if applied to an explicit specialization or instantiation. ! The `-Wabi-tag' flag enables a warning about a class which does ! not have all the ABI tags used by its subobjects and virtual ! functions; for users with code that needs to coexist with an ! earlier ABI, using this option can help to find all affected types ! that need to be tagged. When a type involving an ABI tag is used as the type of a variable or return type of a function where that tag is not already present in the signature of the function, the tag is automatically applied ! to the variable or function. `-Wabi-tag' also warns about this situation; this warning can be avoided by explicitly tagging the variable or function or moving it into a tagged inline namespace. ! `init_priority (PRIORITY)' In Standard C++, objects defined at namespace scope are guaranteed to be initialized in an order in strict accordance with that of their definitions _in a given translation unit_. No guarantee is made for initializations across translation units. However, GNU C++ allows users to control the order of initialization of objects ! defined at namespace scope with the `init_priority' attribute by specifying a relative PRIORITY, a constant integral expression currently bounded between 101 and 65535 inclusive. Lower numbers indicate a higher priority. ! In the following example, `A' would normally be created before ! `B', but the `init_priority' attribute reverses that order: Some_Class A __attribute__ ((init_priority (2000))); Some_Class B __attribute__ ((init_priority (543))); *************** Some attributes only make sense for C++ *** 44871,44899 **** Note that the particular values of PRIORITY do not matter; only their relative ordering. ! 'java_interface' ! ! This type attribute informs C++ that the class is a Java interface. ! It may only be applied to classes declared within an 'extern ! "Java"' block. Calls to methods declared in this interface are ! dispatched using GCJ's interface table mechanism, instead of ! regular virtual table dispatch. ! ! 'warn_unused' For C++ types with non-trivial constructors and/or destructors it is impossible for the compiler to determine whether a variable of ! this type is truly unused if it is not referenced. This type attribute informs the compiler that variables of this type should ! be warned about if they appear to be unused, just like variables of ! fundamental types. This attribute is appropriate for types which just represent a ! value, such as 'std::string'; it is not appropriate for types which ! control a resource, such as 'std::lock_guard'. - This attribute is also accepted in C, but it is unnecessary because - C does not have constructors or destructors. See also *note Namespace Association::. --- 45358,45385 ---- Note that the particular values of PRIORITY do not matter; only their relative ordering. ! `java_interface' ! This type attribute informs C++ that the class is a Java ! interface. It may only be applied to classes declared within an ! `extern "Java"' block. Calls to methods declared in this ! interface are dispatched using GCJ's interface table mechanism, ! instead of regular virtual table dispatch. + `warn_unused' For C++ types with non-trivial constructors and/or destructors it is impossible for the compiler to determine whether a variable of ! this type is truly unused if it is not referenced. This type attribute informs the compiler that variables of this type should ! be warned about if they appear to be unused, just like variables ! of fundamental types. This attribute is appropriate for types which just represent a ! value, such as `std::string'; it is not appropriate for types which ! control a resource, such as `std::lock_guard'. ! ! This attribute is also accepted in C, but it is unnecessary ! because C does not have constructors or destructors. See also *note Namespace Association::. *************** the execution platform. Here is an exam *** 44944,44958 **** return 0; } ! In the above example, four versions of function foo are created. The first version of foo with the target attribute "default" is the default version. This version gets executed when no other target specific ! version qualifies for execution on a particular platform. A new version of foo is created by using the same function signature but with a different target string. Function foo is called or a pointer to it is taken just like a regular function. GCC takes care of doing the ! dispatching to call the right version at runtime. Refer to the GCC wiki ! on Function Multiversioning (http://gcc.gnu.org/wiki/FunctionMultiVersioning) for more details.  --- 45430,45444 ---- return 0; } ! In the above example, four versions of function foo are created. The first version of foo with the target attribute "default" is the default version. This version gets executed when no other target specific ! version qualifies for execution on a particular platform. A new version of foo is created by using the same function signature but with a different target string. Function foo is called or a pointer to it is taken just like a regular function. GCC takes care of doing the ! dispatching to call the right version at runtime. Refer to the GCC ! wiki on Function Multiversioning (http://gcc.gnu.org/wiki/FunctionMultiVersioning) for more details.  *************** File: gcc.info, Node: Namespace Associa *** 44965,44971 **** inline namespaces. Users should use inline namespaces instead as this extension will be removed in future versions of G++. ! A using-directive with '__attribute ((strong))' is stronger than a normal using-directive in two ways: * Templates from the used namespace can be specialized and explicitly --- 45451,45457 ---- inline namespaces. Users should use inline namespaces instead as this extension will be removed in future versions of G++. ! A using-directive with `__attribute ((strong))' is stronger than a normal using-directive in two ways: * Templates from the used namespace can be specialized and explicitly *************** The C++ front end implements syntactic e *** 45007,45180 **** compile-time determination of various characteristics of a type (or of a pair of types). ! '__has_nothrow_assign (type)' ! If 'type' is const qualified or is a reference type then the trait ! is false. Otherwise if '__has_trivial_assign (type)' is true then ! the trait is true, else if 'type' is a cv class or union type with copy assignment operators that are known not to throw an exception ! then the trait is true, else it is false. Requires: 'type' shall ! be a complete type, (possibly cv-qualified) 'void', or an array of unknown bound. ! '__has_nothrow_copy (type)' ! If '__has_trivial_copy (type)' is true then the trait is true, else ! if 'type' is a cv class or union type with copy constructors that ! are known not to throw an exception then the trait is true, else it ! is false. Requires: 'type' shall be a complete type, (possibly ! cv-qualified) 'void', or an array of unknown bound. ! '__has_nothrow_constructor (type)' ! If '__has_trivial_constructor (type)' is true then the trait is ! true, else if 'type' is a cv class or union type (or array thereof) ! with a default constructor that is known not to throw an exception ! then the trait is true, else it is false. Requires: 'type' shall ! be a complete type, (possibly cv-qualified) 'void', or an array of ! unknown bound. ! '__has_trivial_assign (type)' ! If 'type' is const qualified or is a reference type then the trait ! is false. Otherwise if '__is_pod (type)' is true then the trait is ! true, else if 'type' is a cv class or union type with a trivial copy assignment ([class.copy]) then the trait is true, else it is ! false. Requires: 'type' shall be a complete type, (possibly ! cv-qualified) 'void', or an array of unknown bound. ! '__has_trivial_copy (type)' ! If '__is_pod (type)' is true or 'type' is a reference type then the ! trait is true, else if 'type' is a cv class or union type with a ! trivial copy constructor ([class.copy]) then the trait is true, ! else it is false. Requires: 'type' shall be a complete type, ! (possibly cv-qualified) 'void', or an array of unknown bound. ! '__has_trivial_constructor (type)' ! If '__is_pod (type)' is true then the trait is true, else if 'type' ! is a cv class or union type (or array thereof) with a trivial ! default constructor ([class.ctor]) then the trait is true, else it ! is false. Requires: 'type' shall be a complete type, (possibly ! cv-qualified) 'void', or an array of unknown bound. ! '__has_trivial_destructor (type)' ! If '__is_pod (type)' is true or 'type' is a reference type then the ! trait is true, else if 'type' is a cv class or union type (or array ! thereof) with a trivial destructor ([class.dtor]) then the trait is ! true, else it is false. Requires: 'type' shall be a complete type, ! (possibly cv-qualified) 'void', or an array of unknown bound. ! '__has_virtual_destructor (type)' ! If 'type' is a class type with a virtual destructor ([class.dtor]) ! then the trait is true, else it is false. Requires: 'type' shall ! be a complete type, (possibly cv-qualified) 'void', or an array of unknown bound. ! '__is_abstract (type)' ! If 'type' is an abstract class ([class.abstract]) then the trait is ! true, else it is false. Requires: 'type' shall be a complete type, ! (possibly cv-qualified) 'void', or an array of unknown bound. ! '__is_base_of (base_type, derived_type)' ! If 'base_type' is a base class of 'derived_type' ([class.derived]) then the trait is true, otherwise it is false. Top-level cv ! qualifications of 'base_type' and 'derived_type' are ignored. For ! the purposes of this trait, a class type is considered is own base. ! Requires: if '__is_class (base_type)' and '__is_class ! (derived_type)' are true and 'base_type' and 'derived_type' are not ! the same type (disregarding cv-qualifiers), 'derived_type' shall be ! a complete type. A diagnostic is produced if this requirement is ! not met. ! '__is_class (type)' ! If 'type' is a cv class type, and not a union type ([basic.compound]) the trait is true, else it is false. ! '__is_empty (type)' ! If '__is_class (type)' is false then the trait is false. Otherwise ! 'type' is considered empty if and only if: 'type' has no non-static ! data members, or all non-static data members, if any, are ! bit-fields of length 0, and 'type' has no virtual members, and ! 'type' has no virtual base classes, and 'type' has no base classes ! 'base_type' for which '__is_empty (base_type)' is false. Requires: ! 'type' shall be a complete type, (possibly cv-qualified) 'void', or ! an array of unknown bound. ! '__is_enum (type)' ! If 'type' is a cv enumeration type ([basic.compound]) the trait is true, else it is false. ! '__is_literal_type (type)' ! If 'type' is a literal type ([basic.types]) the trait is true, else ! it is false. Requires: 'type' shall be a complete type, (possibly ! cv-qualified) 'void', or an array of unknown bound. ! '__is_pod (type)' ! If 'type' is a cv POD type ([basic.types]) then the trait is true, ! else it is false. Requires: 'type' shall be a complete type, ! (possibly cv-qualified) 'void', or an array of unknown bound. ! '__is_polymorphic (type)' ! If 'type' is a polymorphic class ([class.virtual]) then the trait ! is true, else it is false. Requires: 'type' shall be a complete ! type, (possibly cv-qualified) 'void', or an array of unknown bound. ! '__is_standard_layout (type)' ! If 'type' is a standard-layout type ([basic.types]) the trait is ! true, else it is false. Requires: 'type' shall be a complete type, ! (possibly cv-qualified) 'void', or an array of unknown bound. ! '__is_trivial (type)' ! If 'type' is a trivial type ([basic.types]) the trait is true, else ! it is false. Requires: 'type' shall be a complete type, (possibly ! cv-qualified) 'void', or an array of unknown bound. ! '__is_union (type)' ! If 'type' is a cv union type ([basic.compound]) the trait is true, else it is false. ! '__underlying_type (type)' ! The underlying type of 'type'. Requires: 'type' shall be an enumeration type ([dcl.enum]).  File: gcc.info, Node: C++ Concepts, Next: Java Exceptions, Prev: Type Traits, Up: C++ Extensions 7.11 C++ Concepts ================= ! C++ concepts provide much-improved support for generic programming. In particular, they allow the specification of constraints on template ! arguments. The constraints are used to extend the usual overloading and ! partial specialization capabilities of the language, allowing generic ! data structures and algorithms to be "refined" based on their properties ! rather than their type names. The following keywords are reserved for concepts. ! 'assumes' States an expression as an assumption, and if possible, verifies ! that the assumption is valid. For example, 'assume(n > 0)'. ! 'axiom' ! Introduces an axiom definition. Axioms introduce requirements on values. ! 'forall' ! Introduces a universally quantified object in an axiom. For ! example, 'forall (int n) n + 0 == n'). ! 'concept' ! Introduces a concept definition. Concepts are sets of syntactic and semantic requirements on types and their values. ! 'requires' Introduces constraints on template arguments or requirements for a member function of a class template. The front end also exposes a number of internal mechanism that can be ! used to simplify the writing of type traits. Note that some of these traits are likely to be removed in the future. ! '__is_same (type1, type2)' A binary type trait: true whenever the type arguments are the same.  File: gcc.info, Node: Java Exceptions, Next: Deprecated Features, Prev: C++ Concepts, Up: C++ Extensions --- 45493,45670 ---- compile-time determination of various characteristics of a type (or of a pair of types). ! `__has_nothrow_assign (type)' ! If `type' is const qualified or is a reference type then the trait ! is false. Otherwise if `__has_trivial_assign (type)' is true then ! the trait is true, else if `type' is a cv class or union type with copy assignment operators that are known not to throw an exception ! then the trait is true, else it is false. Requires: `type' shall ! be a complete type, (possibly cv-qualified) `void', or an array of unknown bound. ! `__has_nothrow_copy (type)' ! If `__has_trivial_copy (type)' is true then the trait is true, ! else if `type' is a cv class or union type with copy constructors ! that are known not to throw an exception then the trait is true, ! else it is false. Requires: `type' shall be a complete type, ! (possibly cv-qualified) `void', or an array of unknown bound. ! `__has_nothrow_constructor (type)' ! If `__has_trivial_constructor (type)' is true then the trait is ! true, else if `type' is a cv class or union type (or array ! thereof) with a default constructor that is known not to throw an ! exception then the trait is true, else it is false. Requires: ! `type' shall be a complete type, (possibly cv-qualified) `void', ! or an array of unknown bound. ! `__has_trivial_assign (type)' ! If `type' is const qualified or is a reference type then the trait ! is false. Otherwise if `__is_pod (type)' is true then the trait is ! true, else if `type' is a cv class or union type with a trivial copy assignment ([class.copy]) then the trait is true, else it is ! false. Requires: `type' shall be a complete type, (possibly ! cv-qualified) `void', or an array of unknown bound. ! `__has_trivial_copy (type)' ! If `__is_pod (type)' is true or `type' is a reference type then ! the trait is true, else if `type' is a cv class or union type with ! a trivial copy constructor ([class.copy]) then the trait is true, ! else it is false. Requires: `type' shall be a complete type, ! (possibly cv-qualified) `void', or an array of unknown bound. ! `__has_trivial_constructor (type)' ! If `__is_pod (type)' is true then the trait is true, else if ! `type' is a cv class or union type (or array thereof) with a ! trivial default constructor ([class.ctor]) then the trait is true, ! else it is false. Requires: `type' shall be a complete type, ! (possibly cv-qualified) `void', or an array of unknown bound. ! `__has_trivial_destructor (type)' ! If `__is_pod (type)' is true or `type' is a reference type then ! the trait is true, else if `type' is a cv class or union type (or ! array thereof) with a trivial destructor ([class.dtor]) then the ! trait is true, else it is false. Requires: `type' shall be a ! complete type, (possibly cv-qualified) `void', or an array of ! unknown bound. ! `__has_virtual_destructor (type)' ! If `type' is a class type with a virtual destructor ([class.dtor]) ! then the trait is true, else it is false. Requires: `type' shall ! be a complete type, (possibly cv-qualified) `void', or an array of unknown bound. ! `__is_abstract (type)' ! If `type' is an abstract class ([class.abstract]) then the trait ! is true, else it is false. Requires: `type' shall be a complete ! type, (possibly cv-qualified) `void', or an array of unknown bound. ! `__is_base_of (base_type, derived_type)' ! If `base_type' is a base class of `derived_type' ([class.derived]) then the trait is true, otherwise it is false. Top-level cv ! qualifications of `base_type' and `derived_type' are ignored. For ! the purposes of this trait, a class type is considered is own ! base. Requires: if `__is_class (base_type)' and `__is_class ! (derived_type)' are true and `base_type' and `derived_type' are ! not the same type (disregarding cv-qualifiers), `derived_type' ! shall be a complete type. A diagnostic is produced if this ! requirement is not met. ! `__is_class (type)' ! If `type' is a cv class type, and not a union type ([basic.compound]) the trait is true, else it is false. ! `__is_empty (type)' ! If `__is_class (type)' is false then the trait is false. ! Otherwise `type' is considered empty if and only if: `type' has no ! non-static data members, or all non-static data members, if any, ! are bit-fields of length 0, and `type' has no virtual members, and ! `type' has no virtual base classes, and `type' has no base classes ! `base_type' for which `__is_empty (base_type)' is false. ! Requires: `type' shall be a complete type, (possibly cv-qualified) ! `void', or an array of unknown bound. ! `__is_enum (type)' ! If `type' is a cv enumeration type ([basic.compound]) the trait is true, else it is false. ! `__is_literal_type (type)' ! If `type' is a literal type ([basic.types]) the trait is true, ! else it is false. Requires: `type' shall be a complete type, ! (possibly cv-qualified) `void', or an array of unknown bound. ! `__is_pod (type)' ! If `type' is a cv POD type ([basic.types]) then the trait is true, ! else it is false. Requires: `type' shall be a complete type, ! (possibly cv-qualified) `void', or an array of unknown bound. ! `__is_polymorphic (type)' ! If `type' is a polymorphic class ([class.virtual]) then the trait ! is true, else it is false. Requires: `type' shall be a complete ! type, (possibly cv-qualified) `void', or an array of unknown bound. ! `__is_standard_layout (type)' ! If `type' is a standard-layout type ([basic.types]) the trait is ! true, else it is false. Requires: `type' shall be a complete ! type, (possibly cv-qualified) `void', or an array of unknown bound. ! `__is_trivial (type)' ! If `type' is a trivial type ([basic.types]) the trait is true, ! else it is false. Requires: `type' shall be a complete type, ! (possibly cv-qualified) `void', or an array of unknown bound. ! `__is_union (type)' ! If `type' is a cv union type ([basic.compound]) the trait is true, else it is false. ! `__underlying_type (type)' ! The underlying type of `type'. Requires: `type' shall be an enumeration type ([dcl.enum]). +  File: gcc.info, Node: C++ Concepts, Next: Java Exceptions, Prev: Type Traits, Up: C++ Extensions 7.11 C++ Concepts ================= ! C++ concepts provide much-improved support for generic programming. In particular, they allow the specification of constraints on template ! arguments. The constraints are used to extend the usual overloading ! and partial specialization capabilities of the language, allowing ! generic data structures and algorithms to be "refined" based on their ! properties rather than their type names. The following keywords are reserved for concepts. ! `assumes' States an expression as an assumption, and if possible, verifies ! that the assumption is valid. For example, `assume(n > 0)'. ! `axiom' ! Introduces an axiom definition. Axioms introduce requirements on values. ! `forall' ! Introduces a universally quantified object in an axiom. For ! example, `forall (int n) n + 0 == n'). ! `concept' ! Introduces a concept definition. Concepts are sets of syntactic and semantic requirements on types and their values. ! `requires' Introduces constraints on template arguments or requirements for a member function of a class template. + The front end also exposes a number of internal mechanism that can be ! used to simplify the writing of type traits. Note that some of these traits are likely to be removed in the future. ! `__is_same (type1, type2)' A binary type trait: true whenever the type arguments are the same. +  File: gcc.info, Node: Java Exceptions, Next: Deprecated Features, Prev: C++ Concepts, Up: C++ Extensions *************** problematic code is: *** 45197,45207 **** } The usual effect of an incorrect guess is a link failure, complaining of ! a missing routine called '__gxx_personality_v0'. You can inform the compiler that Java exceptions are to be used in a translation unit, irrespective of what it might think, by writing ! '#pragma GCC java_exceptions' at the head of the file. This '#pragma' must appear before any functions that throw or catch exceptions, or run destructors when exceptions are thrown through them. --- 45687,45697 ---- } The usual effect of an incorrect guess is a link failure, complaining of ! a missing routine called `__gxx_personality_v0'. You can inform the compiler that Java exceptions are to be used in a translation unit, irrespective of what it might think, by writing ! `#pragma GCC java_exceptions' at the head of the file. This `#pragma' must appear before any functions that throw or catch exceptions, or run destructors when exceptions are thrown through them. *************** cases, the feature might be gone already *** 45226,45256 **** While the list below is not exhaustive, it documents some of the options that are now deprecated: ! '-fexternal-templates' ! '-falt-external-templates' These are two of the many ways for G++ to implement template instantiation. *Note Template Instantiation::. The C++ standard clearly defines how template definitions have to be organized across implementation units. G++ has an implicit instantiation mechanism that should work just fine for standard-conforming code. ! '-fstrict-prototype' ! '-fno-strict-prototype' ! Previously it was possible to use an empty prototype parameter list ! to indicate an unspecified number of parameters (like C), rather ! than no parameters, as C++ demands. This feature has been removed, ! except where it is required for backwards compatibility. *Note ! Backwards Compatibility::. ! G++ allows a virtual function returning 'void *' to be overridden by ! one returning a different pointer type. This extension to the covariant ! return type rules is now deprecated and will be removed from a future ! version. ! The G++ minimum and maximum operators ('?') and their ! compound forms ('?=') have been deprecated and are now removed from G++. Code using these operators should be modified to use ! 'std::min' and 'std::max' instead. The named return value extension has been deprecated, and is now removed from G++. --- 45716,45746 ---- While the list below is not exhaustive, it documents some of the options that are now deprecated: ! `-fexternal-templates' ! `-falt-external-templates' These are two of the many ways for G++ to implement template instantiation. *Note Template Instantiation::. The C++ standard clearly defines how template definitions have to be organized across implementation units. G++ has an implicit instantiation mechanism that should work just fine for standard-conforming code. ! `-fstrict-prototype' ! `-fno-strict-prototype' ! Previously it was possible to use an empty prototype parameter ! list to indicate an unspecified number of parameters (like C), ! rather than no parameters, as C++ demands. This feature has been ! removed, except where it is required for backwards compatibility. ! *Note Backwards Compatibility::. ! G++ allows a virtual function returning `void *' to be overridden by ! one returning a different pointer type. This extension to the ! covariant return type rules is now deprecated and will be removed from a ! future version. ! The G++ minimum and maximum operators (`?') and their ! compound forms (`?=') have been deprecated and are now removed from G++. Code using these operators should be modified to use ! `std::min' and `std::max' instead. The named return value extension has been deprecated, and is now removed from G++. *************** and other places where they are not perm *** 45269,45279 **** deprecated and will be removed from a future version of G++. G++ allows floating-point literals to appear in integral constant ! expressions, e.g. ' enum E { e = int(2.2 * 3.7) } ' This extension is deprecated and will be removed from a future version. G++ allows static data members of const floating-point type to be ! declared with an initializer in a class definition. The standard only allows initializers for static members of const integral types and const enumeration types so this extension has been deprecated and will be removed from a future version. --- 45759,45769 ---- deprecated and will be removed from a future version of G++. G++ allows floating-point literals to appear in integral constant ! expressions, e.g. ` enum E { e = int(2.2 * 3.7) } ' This extension is deprecated and will be removed from a future version. G++ allows static data members of const floating-point type to be ! declared with an initializer in a class definition. The standard only allows initializers for static members of const integral types and const enumeration types so this extension has been deprecated and will be removed from a future version. *************** used to be acceptable in previous drafts *** 45290,45309 **** ARM [Annotated C++ Reference Manual], are no longer accepted. In order to allow compilation of C++ written to such drafts, G++ contains some backwards compatibilities. _All such backwards compatibility features ! are liable to disappear in future versions of G++._ They should be ! considered deprecated. *Note Deprecated Features::. ! 'For scope' If a variable is declared at for scope, it used to remain in scope ! until the end of the scope that contained the for statement (rather ! than just within the for scope). G++ retains this, but issues a ! warning, if such a variable is accessed outside the for scope. ! 'Implicit C language' ! Old C system header files did not contain an 'extern "C" {...}' scope to set the language. On such systems, all header files are implicitly scoped inside a C language scope. Also, an empty ! prototype '()' is treated as an unspecified number of arguments, rather than no arguments, as C++ demands.  --- 45780,45800 ---- ARM [Annotated C++ Reference Manual], are no longer accepted. In order to allow compilation of C++ written to such drafts, G++ contains some backwards compatibilities. _All such backwards compatibility features ! are liable to disappear in future versions of G++._ They should be ! considered deprecated. *Note Deprecated Features::. ! `For scope' If a variable is declared at for scope, it used to remain in scope ! until the end of the scope that contained the for statement ! (rather than just within the for scope). G++ retains this, but ! issues a warning, if such a variable is accessed outside the for ! scope. ! `Implicit C language' ! Old C system header files did not contain an `extern "C" {...}' scope to set the language. On such systems, all header files are implicitly scoped inside a C language scope. Also, an empty ! prototype `()' is treated as an unspecified number of arguments, rather than no arguments, as C++ demands.  *************** File: gcc.info, Node: Objective-C, Nex *** 45312,45320 **** 8 GNU Objective-C Features ************************** ! This document is meant to describe some of the GNU Objective-C features. ! It is not intended to teach you Objective-C. There are several resources ! on the Internet that present the language. * Menu: --- 45803,45811 ---- 8 GNU Objective-C Features ************************** ! This document is meant to describe some of the GNU Objective-C ! features. It is not intended to teach you Objective-C. There are ! several resources on the Internet that present the language. * Menu: *************** File: gcc.info, Node: GNU Objective-C r *** 45338,45345 **** This section is specific for the GNU Objective-C runtime. If you are using a different runtime, you can skip it. ! The GNU Objective-C runtime provides an API that allows you to interact ! with the Objective-C runtime system, querying the live runtime structures and even manipulating them. This allows you for example to inspect and navigate classes, methods and protocols; to define new classes or new methods, and even to modify existing classes or --- 45829,45836 ---- This section is specific for the GNU Objective-C runtime. If you are using a different runtime, you can skip it. ! The GNU Objective-C runtime provides an API that allows you to ! interact with the Objective-C runtime system, querying the live runtime structures and even manipulating them. This allows you for example to inspect and navigate classes, methods and protocols; to define new classes or new methods, and even to modify existing classes or *************** provided by the "Objective-C 2.0" Apple/ *** 45366,45407 **** API is documented in the public header files of the GNU Objective-C runtime: ! * 'objc/objc.h': this is the basic Objective-C header file, defining ! the basic Objective-C types such as 'id', 'Class' and 'BOOL'. You have to include this header to do almost anything with Objective-C. ! * 'objc/runtime.h': this header declares most of the public runtime API functions allowing you to inspect and manipulate the Objective-C runtime data structures. These functions are fairly standardized across Objective-C runtimes and are almost identical to the Apple/NeXT Objective-C runtime ones. It does not declare functions in some specialized areas (constructing and forwarding message invocations, threading) which are in the other headers ! below. You have to include 'objc/objc.h' and 'objc/runtime.h' to ! use any of the functions, such as 'class_getName()', declared in ! 'objc/runtime.h'. ! * 'objc/message.h': this header declares public functions used to construct, deconstruct and forward message invocations. Because messaging is done in quite a different way on different runtimes, functions in this header are specific to the GNU Objective-C runtime implementation. ! * 'objc/objc-exception.h': this header declares some public functions ! related to Objective-C exceptions. For example functions in this ! header allow you to throw an Objective-C exception from plain C/C++ ! code. ! * 'objc/objc-sync.h': this header declares some public functions ! related to the Objective-C '@synchronized()' syntax, allowing you ! to emulate an Objective-C '@synchronized()' block in plain C/C++ code. ! * 'objc/thr.h': this header declares a public runtime API threading layer that is only provided by the GNU Objective-C runtime. It ! declares functions such as 'objc_mutex_lock()', which provide a platform-independent set of threading functions. The header files contain detailed documentation for each function in the GNU Objective-C runtime API. --- 45857,45899 ---- API is documented in the public header files of the GNU Objective-C runtime: ! * `objc/objc.h': this is the basic Objective-C header file, defining ! the basic Objective-C types such as `id', `Class' and `BOOL'. You have to include this header to do almost anything with Objective-C. ! * `objc/runtime.h': this header declares most of the public runtime API functions allowing you to inspect and manipulate the Objective-C runtime data structures. These functions are fairly standardized across Objective-C runtimes and are almost identical to the Apple/NeXT Objective-C runtime ones. It does not declare functions in some specialized areas (constructing and forwarding message invocations, threading) which are in the other headers ! below. You have to include `objc/objc.h' and `objc/runtime.h' to ! use any of the functions, such as `class_getName()', declared in ! `objc/runtime.h'. ! * `objc/message.h': this header declares public functions used to construct, deconstruct and forward message invocations. Because messaging is done in quite a different way on different runtimes, functions in this header are specific to the GNU Objective-C runtime implementation. ! * `objc/objc-exception.h': this header declares some public ! functions related to Objective-C exceptions. For example ! functions in this header allow you to throw an Objective-C ! exception from plain C/C++ code. ! * `objc/objc-sync.h': this header declares some public functions ! related to the Objective-C `@synchronized()' syntax, allowing you ! to emulate an Objective-C `@synchronized()' block in plain C/C++ code. ! * `objc/thr.h': this header declares a public runtime API threading layer that is only provided by the GNU Objective-C runtime. It ! declares functions such as `objc_mutex_lock()', which provide a platform-independent set of threading functions. + The header files contain detailed documentation for each function in the GNU Objective-C runtime API. *************** File: gcc.info, Node: Traditional GNU O *** 45412,45422 **** --------------------------------------------- The GNU Objective-C runtime used to provide a different API, which we ! call the "traditional" GNU Objective-C runtime API. Functions belonging ! to this API are easy to recognize because they use a different naming ! convention, such as 'class_get_super_class()' (traditional API) instead ! of 'class_getSuperclass()' (modern API). Software using this API ! includes the file 'objc/objc-api.h' where it is declared. Starting with GCC 4.7.0, the traditional GNU runtime API is no longer available. --- 45904,45915 ---- --------------------------------------------- The GNU Objective-C runtime used to provide a different API, which we ! call the "traditional" GNU Objective-C runtime API. Functions ! belonging to this API are easy to recognize because they use a ! different naming convention, such as `class_get_super_class()' ! (traditional API) instead of `class_getSuperclass()' (modern API). ! Software using this API includes the file `objc/objc-api.h' where it is ! declared. Starting with GCC 4.7.0, the traditional GNU runtime API is no longer available. *************** available. *** 45424,45449 ****  File: gcc.info, Node: Executing code before main, Next: Type encoding, Prev: GNU Objective-C runtime API, Up: Objective-C ! 8.2 '+load': Executing Code before 'main' ========================================= This section is specific for the GNU Objective-C runtime. If you are using a different runtime, you can skip it. The GNU Objective-C runtime provides a way that allows you to execute ! code before the execution of the program enters the 'main' function. The code is executed on a per-class and a per-category basis, through a ! special class method '+load'. This facility is very useful if you want to initialize global variables which can be accessed by the program directly, without sending a message to the class first. The usual way to initialize global variables, in ! the '+initialize' method, might not be useful because '+initialize' is only called when the first message is sent to a class object, which in some cases could be too late. ! Suppose for example you have a 'FileStream' class that declares ! 'Stdin', 'Stdout' and 'Stderr' as global variables, like below: FileStream *Stdin = nil; --- 45917,45942 ----  File: gcc.info, Node: Executing code before main, Next: Type encoding, Prev: GNU Objective-C runtime API, Up: Objective-C ! 8.2 `+load': Executing Code before `main' ========================================= This section is specific for the GNU Objective-C runtime. If you are using a different runtime, you can skip it. The GNU Objective-C runtime provides a way that allows you to execute ! code before the execution of the program enters the `main' function. The code is executed on a per-class and a per-category basis, through a ! special class method `+load'. This facility is very useful if you want to initialize global variables which can be accessed by the program directly, without sending a message to the class first. The usual way to initialize global variables, in ! the `+initialize' method, might not be useful because `+initialize' is only called when the first message is sent to a class object, which in some cases could be too late. ! Suppose for example you have a `FileStream' class that declares ! `Stdin', `Stdout' and `Stderr' as global variables, like below: FileStream *Stdin = nil; *************** some cases could be too late. *** 45462,45478 **** /* Other methods here */ @end ! In this example, the initialization of 'Stdin', 'Stdout' and 'Stderr' ! in '+initialize' occurs too late. The programmer can send a message to ! one of these objects before the variables are actually initialized, thus ! sending messages to the 'nil' object. The '+initialize' method which ! actually initializes the global variables is not invoked until the first ! message is sent to the class object. The solution would require these ! variables to be initialized just before entering 'main'. ! ! The correct solution of the above problem is to use the '+load' method ! instead of '+initialize': @implementation FileStream --- 45955,45970 ---- /* Other methods here */ @end + In this example, the initialization of `Stdin', `Stdout' and `Stderr' + in `+initialize' occurs too late. The programmer can send a message to + one of these objects before the variables are actually initialized, + thus sending messages to the `nil' object. The `+initialize' method + which actually initializes the global variables is not invoked until + the first message is sent to the class object. The solution would + require these variables to be initialized just before entering `main'. ! The correct solution of the above problem is to use the `+load' method ! instead of `+initialize': @implementation FileStream *************** instead of '+initialize': *** 45487,45501 **** /* Other methods here */ @end ! ! The '+load' is a method that is not overridden by categories. If a ! class and a category of it both implement '+load', both methods are invoked. This allows some additional initializations to be performed in a category. ! This mechanism is not intended to be a replacement for '+initialize'. ! You should be aware of its limitations when you decide to use it instead ! of '+initialize'. * Menu: --- 45979,45992 ---- /* Other methods here */ @end ! The `+load' is a method that is not overridden by categories. If a ! class and a category of it both implement `+load', both methods are invoked. This allows some additional initializations to be performed in a category. ! This mechanism is not intended to be a replacement for `+initialize'. ! You should be aware of its limitations when you decide to use it ! instead of `+initialize'. * Menu: *************** of '+initialize'. *** 45504,45518 ****  File: gcc.info, Node: What you can and what you cannot do in +load, Up: Executing code before main ! 8.2.1 What You Can and Cannot Do in '+load' ------------------------------------------- ! '+load' is to be used only as a last resort. Because it is executed very early, most of the Objective-C runtime machinery will not be ready ! when '+load' is executed; hence '+load' works best for executing C code that is independent on the Objective-C runtime. ! The '+load' implementation in the GNU runtime guarantees you the following things: * you can write whatever C code you like; --- 45995,46009 ----  File: gcc.info, Node: What you can and what you cannot do in +load, Up: Executing code before main ! 8.2.1 What You Can and Cannot Do in `+load' ------------------------------------------- ! `+load' is to be used only as a last resort. Because it is executed very early, most of the Objective-C runtime machinery will not be ready ! when `+load' is executed; hence `+load' works best for executing C code that is independent on the Objective-C runtime. ! The `+load' implementation in the GNU runtime guarantees you the following things: * you can write whatever C code you like; *************** following things: *** 45520,45530 **** * you can allocate and send messages to objects whose class is implemented in the same file; ! * the '+load' implementation of all super classes of a class are ! executed before the '+load' of that class is executed; - * the '+load' implementation of a class is executed before the - '+load' implementation of any category. In particular, the following things, even if they can work in a particular case, are not guaranteed: --- 46011,46022 ---- * you can allocate and send messages to objects whose class is implemented in the same file; ! * the `+load' implementation of all super classes of a class are ! executed before the `+load' of that class is executed; ! ! * the `+load' implementation of a class is executed before the ! `+load' implementation of any category. In particular, the following things, even if they can work in a particular case, are not guaranteed: *************** particular case, are not guaranteed: *** 45534,45558 **** * allocation of or sending messages to objects whose classes have a category implemented in the same file; ! * sending messages to Objective-C constant strings ('@"this is a constant string"'); - You should make no assumptions about receiving '+load' in sibling - classes when you write '+load' of a class. The order in which sibling - classes receive '+load' is not guaranteed. ! The order in which '+load' and '+initialize' are called could be problematic if this matters. If you don't allocate objects inside ! '+load', it is guaranteed that '+load' is called before '+initialize'. ! If you create an object inside '+load' the '+initialize' method of ! object's class is invoked even if '+load' was not invoked. Note if you ! explicitly call '+load' on a class, '+initialize' will be called first. To avoid possible problems try to implement only one of these methods. ! The '+load' method is also invoked when a bundle is dynamically loaded into your running program. This happens automatically without any intervening operation from you. When you write bundles and you need to ! write '+load' you can safely create and send messages to objects whose classes already exist in the running program. The same restrictions as above apply to classes defined in bundle. --- 46026,46051 ---- * allocation of or sending messages to objects whose classes have a category implemented in the same file; ! * sending messages to Objective-C constant strings (`@"this is a constant string"'); ! You should make no assumptions about receiving `+load' in sibling ! classes when you write `+load' of a class. The order in which sibling ! classes receive `+load' is not guaranteed. ! ! The order in which `+load' and `+initialize' are called could be problematic if this matters. If you don't allocate objects inside ! `+load', it is guaranteed that `+load' is called before `+initialize'. ! If you create an object inside `+load' the `+initialize' method of ! object's class is invoked even if `+load' was not invoked. Note if you ! explicitly call `+load' on a class, `+initialize' will be called first. To avoid possible problems try to implement only one of these methods. ! The `+load' method is also invoked when a bundle is dynamically loaded into your running program. This happens automatically without any intervening operation from you. When you write bundles and you need to ! write `+load' you can safely create and send messages to objects whose classes already exist in the running program. The same restrictions as above apply to classes defined in bundle. *************** File: gcc.info, Node: Type encoding, N *** 45562,45570 **** 8.3 Type Encoding ================= ! This is an advanced section. Type encodings are used extensively by the ! compiler and by the runtime, but you generally do not need to know about ! them to use Objective-C. The Objective-C compiler generates type encodings for all the types. These type encodings are used at runtime to find out information about --- 46055,46063 ---- 8.3 Type Encoding ================= ! This is an advanced section. Type encodings are used extensively by ! the compiler and by the runtime, but you generally do not need to know ! about them to use Objective-C. The Objective-C compiler generates type encodings for all the types. These type encodings are used at runtime to find out information about *************** selectors and methods and about objects *** 45572,45605 **** The types are encoded in the following way: ! '_Bool' 'B' ! 'char' 'c' ! 'unsigned char' 'C' ! 'short' 's' ! 'unsigned short' 'S' ! 'int' 'i' ! 'unsigned int' 'I' ! 'long' 'l' ! 'unsigned long' 'L' ! 'long long' 'q' ! 'unsigned long 'Q' ! long' ! 'float' 'f' ! 'double' 'd' ! 'long double' 'D' ! 'void' 'v' ! 'id' '@' ! 'Class' '#' ! 'SEL' ':' ! 'char*' '*' ! 'enum' an 'enum' is encoded exactly as the integer type ! that the compiler uses for it, which depends on the enumeration values. Often the compiler users ! 'unsigned int', which is then encoded as 'I'. ! unknown type '?' ! Complex types 'j' followed by the inner type. For example ! '_Complex double' is encoded as "jd". ! bit-fields 'b' followed by the starting position of the bit-field, the type of the bit-field and the size of the bit-field (the bit-fields encoding was changed from the NeXT's compiler encoding, see below) --- 46065,46098 ---- The types are encoded in the following way: ! `_Bool' `B' ! `char' `c' ! `unsigned char' `C' ! `short' `s' ! `unsigned short' `S' ! `int' `i' ! `unsigned int' `I' ! `long' `l' ! `unsigned long' `L' ! `long long' `q' ! `unsigned long `Q' ! long' ! `float' `f' ! `double' `d' ! `long double' `D' ! `void' `v' ! `id' `@' ! `Class' `#' ! `SEL' `:' ! `char*' `*' ! `enum' an `enum' is encoded exactly as the integer type that ! the compiler uses for it, which depends on the enumeration values. Often the compiler users ! `unsigned int', which is then encoded as `I'. ! unknown type `?' ! Complex types `j' followed by the inner type. For example ! `_Complex double' is encoded as "jd". ! bit-fields `b' followed by the starting position of the bit-field, the type of the bit-field and the size of the bit-field (the bit-fields encoding was changed from the NeXT's compiler encoding, see below) *************** bit closest to the beginning of the stru *** 45620,45696 **** The non-atomic types are encoded as follows: ! pointers '^' followed by the pointed type. ! arrays '[' followed by the number of elements in the array ! followed by the type of the elements followed by ']' ! structures '{' followed by the name of the structure (or '?' if the ! structure is unnamed), the '=' sign, the type of the ! members and by '}' ! unions '(' followed by the name of the structure (or '?' if the ! union is unnamed), the '=' sign, the type of the members ! followed by ')' ! vectors '![' followed by the vector_size (the number of bytes composing the vector) followed by a comma, followed by the alignment (in bytes) of the vector, followed by the ! type of the elements followed by ']' Here are some types and their encodings, as they are generated by the compiler on an i386 machine: Objective-C type Compiler encoding ! int a[10]; '[10i]' ! struct { '{?=i[3f]b128i3b131i2c}' ! int i; ! float f[3]; ! int a:3; ! int b:2; ! char c; ! } ! int a __attribute__ ((vector_size (16)));'![16,16i]' (alignment would depend on the machine) ! In addition to the types the compiler also encodes the type specifiers. ! The table below describes the encoding of the current Objective-C type ! specifiers: Specifier Encoding ! 'const' 'r' ! 'in' 'n' ! 'inout' 'N' ! 'out' 'o' ! 'bycopy' 'O' ! 'byref' 'R' ! 'oneway' 'V' The type specifiers are encoded just before the type. Unlike types however, the type specifiers are only encoded when they appear in method argument types. ! Note how 'const' interacts with pointers: Objective-C type Compiler encoding ! const int 'ri' ! const int* '^ri' ! int *const 'r^i' ! 'const int*' is a pointer to a 'const int', and so is encoded as '^ri'. ! 'int* const', instead, is a 'const' pointer to an 'int', and so is ! encoded as 'r^i'. ! Finally, there is a complication when encoding 'const char *' versus ! 'char * const'. Because 'char *' is encoded as '*' and not as '^c', ! there is no way to express the fact that 'r' applies to the pointer or to the pointee. ! Hence, it is assumed as a convention that 'r*' means 'const char *' (since it is what is most often meant), and there is no way to encode ! 'char *const'. 'char *const' would simply be encoded as '*', and the ! 'const' is lost. * Menu: --- 46113,46189 ---- The non-atomic types are encoded as follows: ! pointers `^' followed by the pointed type. ! arrays `[' followed by the number of elements in the array ! followed by the type of the elements followed by `]' ! structures `{' followed by the name of the structure (or `?' if the ! structure is unnamed), the `=' sign, the type of the ! members and by `}' ! unions `(' followed by the name of the structure (or `?' if the ! union is unnamed), the `=' sign, the type of the members ! followed by `)' ! vectors `![' followed by the vector_size (the number of bytes composing the vector) followed by a comma, followed by the alignment (in bytes) of the vector, followed by the ! type of the elements followed by `]' Here are some types and their encodings, as they are generated by the compiler on an i386 machine: Objective-C type Compiler encoding ! int a[10]; `[10i]' ! struct { `{?=i[3f]b128i3b131i2c}' ! int i; ! float f[3]; ! int a:3; ! int b:2; ! char c; ! } ! int a __attribute__ ((vector_size (16)));`![16,16i]' (alignment would depend on the machine) ! In addition to the types the compiler also encodes the type ! specifiers. The table below describes the encoding of the current ! Objective-C type specifiers: Specifier Encoding ! `const' `r' ! `in' `n' ! `inout' `N' ! `out' `o' ! `bycopy' `O' ! `byref' `R' ! `oneway' `V' The type specifiers are encoded just before the type. Unlike types however, the type specifiers are only encoded when they appear in method argument types. ! Note how `const' interacts with pointers: Objective-C type Compiler encoding ! const int `ri' ! const int* `^ri' ! int *const `r^i' ! `const int*' is a pointer to a `const int', and so is encoded as ! `^ri'. `int* const', instead, is a `const' pointer to an `int', and so ! is encoded as `r^i'. ! Finally, there is a complication when encoding `const char *' versus ! `char * const'. Because `char *' is encoded as `*' and not as `^c', ! there is no way to express the fact that `r' applies to the pointer or to the pointee. ! Hence, it is assumed as a convention that `r*' means `const char *' (since it is what is most often meant), and there is no way to encode ! `char *const'. `char *const' would simply be encoded as `*', and the ! `const' is lost. * Menu: *************** File: gcc.info, Node: Legacy type encod *** 45706,45713 **** Unfortunately, historically GCC used to have a number of bugs in its encoding code. The NeXT runtime expects GCC to emit type encodings in ! this historical format (compatible with GCC-3.3), so when using the NeXT ! runtime, GCC will introduce on purpose a number of incorrect encodings: * the read-only qualifier of the pointee gets emitted before the '^'. The read-only qualifier of the pointer itself gets ignored, unless --- 46199,46207 ---- Unfortunately, historically GCC used to have a number of bugs in its encoding code. The NeXT runtime expects GCC to emit type encodings in ! this historical format (compatible with GCC-3.3), so when using the ! NeXT runtime, GCC will introduce on purpose a number of incorrect ! encodings: * the read-only qualifier of the pointee gets emitted before the '^'. The read-only qualifier of the pointer itself gets ignored, unless *************** runtime, GCC will introduce on purpose a *** 45715,45743 **** type. * 32-bit longs are encoded as 'l' or 'L', but not always. For ! typedefs, the compiler uses 'i' or 'I' instead if encoding a struct ! field or a pointer. ! * 'enum's are always encoded as 'i' (int) even if they are actually unsigned or long. In addition to that, the NeXT runtime uses a different encoding for ! bitfields. It encodes them as 'b' followed by the size, without a bit offset or the underlying field type.  File: gcc.info, Node: @encode, Next: Method signatures, Prev: Legacy type encoding, Up: Type encoding ! 8.3.2 '@encode' --------------- ! GNU Objective-C supports the '@encode' syntax that allows you to create ! a type encoding from a C/Objective-C type. For example, '@encode(int)' ! is compiled by the compiler into '"i"'. ! '@encode' does not support type qualifiers other than 'const'. For ! example, '@encode(const char*)' is valid and is compiled into '"r*"', ! while '@encode(bycopy char *)' is invalid and will cause a compilation error.  --- 46209,46238 ---- type. * 32-bit longs are encoded as 'l' or 'L', but not always. For ! typedefs, the compiler uses 'i' or 'I' instead if encoding a ! struct field or a pointer. ! * `enum's are always encoded as 'i' (int) even if they are actually unsigned or long. + In addition to that, the NeXT runtime uses a different encoding for ! bitfields. It encodes them as `b' followed by the size, without a bit offset or the underlying field type.  File: gcc.info, Node: @encode, Next: Method signatures, Prev: Legacy type encoding, Up: Type encoding ! 8.3.2 `@encode' --------------- ! GNU Objective-C supports the `@encode' syntax that allows you to create ! a type encoding from a C/Objective-C type. For example, `@encode(int)' ! is compiled by the compiler into `"i"'. ! `@encode' does not support type qualifiers other than `const'. For ! example, `@encode(const char*)' is valid and is compiled into `"r*"', ! while `@encode(bycopy char *)' is invalid and will cause a compilation error.  *************** File: gcc.info, Node: Method signatures *** 45747,45753 **** ----------------------- This section documents the encoding of method types, which is rarely ! needed to use Objective-C. You should skip it at a first reading; the runtime provides functions that will work on methods and can walk through the list of parameters and interpret them for you. These functions are part of the public "API" and are the preferred way to --- 46242,46248 ---- ----------------------- This section documents the encoding of method types, which is rarely ! needed to use Objective-C. You should skip it at a first reading; the runtime provides functions that will work on methods and can walk through the list of parameters and interpret them for you. These functions are part of the public "API" and are the preferred way to *************** arguments. *** 45764,45789 **** The "signature" is a null-terminated string, composed of the following: * The return type, including type qualifiers. For example, a method ! returning 'int' would have 'i' here. * The total size (in bytes) required to pass all the parameters. ! This includes the two hidden parameters (the object 'self' and the ! method selector '_cmd'). * Each argument, with the type encoding, followed by the offset (in bytes) of the argument in the list of parameters. ! For example, a method with no arguments and returning 'int' would have ! the signature 'i8@0:4' if the size of a pointer is 4. The signature is ! interpreted as follows: the 'i' is the return type (an 'int'), the '8' is the total size of the parameters in bytes (two pointers each of size ! 4), the '@0' is the first parameter (an object at byte offset '0') and ! ':4' is the second parameter (a 'SEL' at byte offset '4'). You can easily find more examples by running the "strings" program on ! an Objective-C object file compiled by GCC. You'll see a lot of strings ! that look very much like 'i8@0:4'. They are signatures of Objective-C ! methods.  File: gcc.info, Node: Garbage Collection, Next: Constant string objects, Prev: Type encoding, Up: Objective-C --- 46259,46285 ---- The "signature" is a null-terminated string, composed of the following: * The return type, including type qualifiers. For example, a method ! returning `int' would have `i' here. * The total size (in bytes) required to pass all the parameters. ! This includes the two hidden parameters (the object `self' and the ! method selector `_cmd'). * Each argument, with the type encoding, followed by the offset (in bytes) of the argument in the list of parameters. ! ! For example, a method with no arguments and returning `int' would have ! the signature `i8@0:4' if the size of a pointer is 4. The signature is ! interpreted as follows: the `i' is the return type (an `int'), the `8' is the total size of the parameters in bytes (two pointers each of size ! 4), the `@0' is the first parameter (an object at byte offset `0') and ! `:4' is the second parameter (a `SEL' at byte offset `4'). You can easily find more examples by running the "strings" program on ! an Objective-C object file compiled by GCC. You'll see a lot of ! strings that look very much like `i8@0:4'. They are signatures of ! Objective-C methods.  File: gcc.info, Node: Garbage Collection, Next: Constant string objects, Prev: Type encoding, Up: Objective-C *************** using a powerful conservative garbage co *** 45799,45808 **** Boehm-Demers-Weiser conservative garbage collector. To enable the support for it you have to configure the compiler using ! an additional argument, '--enable-objc-gc'. This will build the boehm-gc library, and build an additional runtime library which has several enhancements to support the garbage collector. The new library ! has a new name, 'libobjc_gc.a' to not conflict with the non-garbage-collected library. When the garbage collector is used, the objects are allocated using the --- 46295,46304 ---- Boehm-Demers-Weiser conservative garbage collector. To enable the support for it you have to configure the compiler using ! an additional argument, `--enable-objc-gc'. This will build the boehm-gc library, and build an additional runtime library which has several enhancements to support the garbage collector. The new library ! has a new name, `libobjc_gc.a' to not conflict with the non-garbage-collected library. When the garbage collector is used, the objects are allocated using the *************** on where pointers are located inside obj *** 45812,45825 **** computed once per class, immediately after the class has been initialized. ! There is a new runtime function 'class_ivar_set_gcinvisible()' which can be used to declare a so-called "weak pointer" reference. Such a pointer is basically hidden for the garbage collector; this can be useful in certain situations, especially when you want to keep track of the allocated objects, yet allow them to be collected. This kind of pointers can only be members of objects, you cannot declare a global pointer as a weak reference. Every type which is a pointer type can be ! declared a weak pointer, including 'id', 'Class' and 'SEL'. Here is an example of how to use this feature. Suppose you want to implement a class whose instances hold a weak pointer reference; the --- 46308,46321 ---- computed once per class, immediately after the class has been initialized. ! There is a new runtime function `class_ivar_set_gcinvisible()' which can be used to declare a so-called "weak pointer" reference. Such a pointer is basically hidden for the garbage collector; this can be useful in certain situations, especially when you want to keep track of the allocated objects, yet allow them to be collected. This kind of pointers can only be members of objects, you cannot declare a global pointer as a weak reference. Every type which is a pointer type can be ! declared a weak pointer, including `id', `Class' and `SEL'. Here is an example of how to use this feature. Suppose you want to implement a class whose instances hold a weak pointer reference; the *************** following class does this: *** 45857,45865 **** @end - Weak pointers are supported through a new type character specifier ! represented by the '!' character. The 'class_ivar_set_gcinvisible()' function adds or removes this specifier to the string type description of the instance variable named as argument. --- 46353,46360 ---- @end Weak pointers are supported through a new type character specifier ! represented by the `!' character. The `class_ivar_set_gcinvisible()' function adds or removes this specifier to the string type description of the instance variable named as argument. *************** File: gcc.info, Node: Constant string o *** 45871,45890 **** GNU Objective-C provides constant string objects that are generated directly by the compiler. You declare a constant string object by ! prefixing a C constant string with the character '@': id myString = @"this is a constant string object"; The constant string objects are by default instances of the ! 'NXConstantString' class which is provided by the GNU Objective-C runtime. To get the definition of this class you must include the ! 'objc/NXConstStr.h' header file. User defined libraries may want to implement their own constant string class. To be able to support them, the GNU Objective-C compiler provides a new command line options ! '-fconstant-string-class=CLASS-NAME'. The provided class should adhere ! to a strict structure, the same as 'NXConstantString''s structure: @interface MyConstantStringClass --- 46366,46385 ---- GNU Objective-C provides constant string objects that are generated directly by the compiler. You declare a constant string object by ! prefixing a C constant string with the character `@': id myString = @"this is a constant string object"; The constant string objects are by default instances of the ! `NXConstantString' class which is provided by the GNU Objective-C runtime. To get the definition of this class you must include the ! `objc/NXConstStr.h' header file. User defined libraries may want to implement their own constant string class. To be able to support them, the GNU Objective-C compiler provides a new command line options ! `-fconstant-string-class=CLASS-NAME'. The provided class should adhere ! to a strict structure, the same as `NXConstantString''s structure: @interface MyConstantStringClass *************** to a strict structure, the same as 'NXCo *** 45895,45946 **** } @end ! ! 'NXConstantString' inherits from 'Object'; user class libraries may choose to inherit the customized constant string class from a different ! class than 'Object'. There is no requirement in the methods the ! constant string class has to implement, but the final ivar layout of the ! class must be the compatible with the given structure. When the compiler creates the statically allocated constant string ! object, the 'c_string' field will be filled by the compiler with the ! string; the 'length' field will be filled by the compiler with the ! string length; the 'isa' pointer will be filled with 'NULL' by the compiler, and it will later be fixed up automatically at runtime by the GNU Objective-C runtime library to point to the class which was set by ! the '-fconstant-string-class' option when the object file is loaded (if ! you wonder how it works behind the scenes, the name of the class to use, ! and the list of static objects to fixup, are stored by the compiler in ! the object file in a place where the GNU runtime library will find them ! at runtime). ! As a result, when a file is compiled with the '-fconstant-string-class' ! option, all the constant string objects will be instances of the class ! specified as argument to this option. It is possible to have multiple ! compilation units referring to different constant string classes, ! neither the compiler nor the linker impose any restrictions in doing ! this.  File: gcc.info, Node: compatibility_alias, Next: Exceptions, Prev: Constant string objects, Up: Objective-C ! 8.6 'compatibility_alias' ========================= ! The keyword '@compatibility_alias' allows you to define a class name as equivalent to another class name. For example: @compatibility_alias WOApplication GSWApplication; ! tells the compiler that each time it encounters 'WOApplication' as a ! class name, it should replace it with 'GSWApplication' (that is, ! 'WOApplication' is just an alias for 'GSWApplication'). There are some constraints on how this can be used-- ! * 'WOApplication' (the alias) must not be an existing class; - * 'GSWApplication' (the real class) must be an existing class.  File: gcc.info, Node: Exceptions, Next: Synchronization, Prev: compatibility_alias, Up: Objective-C --- 46390,46441 ---- } @end ! `NXConstantString' inherits from `Object'; user class libraries may choose to inherit the customized constant string class from a different ! class than `Object'. There is no requirement in the methods the ! constant string class has to implement, but the final ivar layout of ! the class must be the compatible with the given structure. When the compiler creates the statically allocated constant string ! object, the `c_string' field will be filled by the compiler with the ! string; the `length' field will be filled by the compiler with the ! string length; the `isa' pointer will be filled with `NULL' by the compiler, and it will later be fixed up automatically at runtime by the GNU Objective-C runtime library to point to the class which was set by ! the `-fconstant-string-class' option when the object file is loaded (if ! you wonder how it works behind the scenes, the name of the class to ! use, and the list of static objects to fixup, are stored by the ! compiler in the object file in a place where the GNU runtime library ! will find them at runtime). ! As a result, when a file is compiled with the ! `-fconstant-string-class' option, all the constant string objects will ! be instances of the class specified as argument to this option. It is ! possible to have multiple compilation units referring to different ! constant string classes, neither the compiler nor the linker impose any ! restrictions in doing this.  File: gcc.info, Node: compatibility_alias, Next: Exceptions, Prev: Constant string objects, Up: Objective-C ! 8.6 `compatibility_alias' ========================= ! The keyword `@compatibility_alias' allows you to define a class name as equivalent to another class name. For example: @compatibility_alias WOApplication GSWApplication; ! tells the compiler that each time it encounters `WOApplication' as a ! class name, it should replace it with `GSWApplication' (that is, ! `WOApplication' is just an alias for `GSWApplication'). There are some constraints on how this can be used-- ! * `WOApplication' (the alias) must not be an existing class; ! ! * `GSWApplication' (the real class) must be an existing class.  File: gcc.info, Node: Exceptions, Next: Synchronization, Prev: compatibility_alias, Up: Objective-C *************** in the following example: *** 45975,46019 **** ... } ! The '@throw' statement may appear anywhere in an Objective-C or ! Objective-C++ program; when used inside of a '@catch' block, the ! '@throw' may appear without an argument (as shown above), in which case ! the object caught by the '@catch' will be rethrown. Note that only (pointers to) Objective-C objects may be thrown and caught using this scheme. When an object is thrown, it will be caught ! by the nearest '@catch' clause capable of handling objects of that type, ! analogously to how 'catch' blocks work in C++ and Java. A '@catch(id ! ...)' clause (as shown above) may also be provided to catch any and all ! Objective-C exceptions not caught by previous '@catch' clauses (if any). ! The '@finally' clause, if present, will be executed upon exit from the ! immediately preceding '@try ... @catch' section. This will happen regardless of whether any exceptions are thrown, caught or rethrown ! inside the '@try ... @catch' section, analogously to the behavior of the ! 'finally' clause in Java. There are several caveats to using the new exception mechanism: ! * The '-fobjc-exceptions' command line option must be used when compiling Objective-C files that use exceptions. * With the GNU runtime, exceptions are always implemented as "native" ! exceptions and it is recommended that the '-fexceptions' and ! '-shared-libgcc' options are used when linking. * With the NeXT runtime, although currently designed to be binary ! compatible with 'NS_HANDLER'-style idioms provided by the ! 'NSException' class, the new exceptions can only be used on Mac OS X 10.3 (Panther) and later systems, due to additional functionality needed in the NeXT Objective-C runtime. * As mentioned above, the new exceptions do not support handling ! types other than Objective-C objects. Furthermore, when used from Objective-C++, the Objective-C exception model does not interoperate with C++ exceptions at this time. This means you ! cannot '@throw' an exception from Objective-C and 'catch' it in ! C++, or vice versa (i.e., 'throw ... @catch').  File: gcc.info, Node: Synchronization, Next: Fast enumeration, Prev: Exceptions, Up: Objective-C --- 46470,46515 ---- ... } ! The `@throw' statement may appear anywhere in an Objective-C or ! Objective-C++ program; when used inside of a `@catch' block, the ! `@throw' may appear without an argument (as shown above), in which case ! the object caught by the `@catch' will be rethrown. Note that only (pointers to) Objective-C objects may be thrown and caught using this scheme. When an object is thrown, it will be caught ! by the nearest `@catch' clause capable of handling objects of that ! type, analogously to how `catch' blocks work in C++ and Java. A ! `@catch(id ...)' clause (as shown above) may also be provided to catch ! any and all Objective-C exceptions not caught by previous `@catch' ! clauses (if any). ! The `@finally' clause, if present, will be executed upon exit from the ! immediately preceding `@try ... @catch' section. This will happen regardless of whether any exceptions are thrown, caught or rethrown ! inside the `@try ... @catch' section, analogously to the behavior of ! the `finally' clause in Java. There are several caveats to using the new exception mechanism: ! * The `-fobjc-exceptions' command line option must be used when compiling Objective-C files that use exceptions. * With the GNU runtime, exceptions are always implemented as "native" ! exceptions and it is recommended that the `-fexceptions' and ! `-shared-libgcc' options are used when linking. * With the NeXT runtime, although currently designed to be binary ! compatible with `NS_HANDLER'-style idioms provided by the ! `NSException' class, the new exceptions can only be used on Mac OS X 10.3 (Panther) and later systems, due to additional functionality needed in the NeXT Objective-C runtime. * As mentioned above, the new exceptions do not support handling ! types other than Objective-C objects. Furthermore, when used from Objective-C++, the Objective-C exception model does not interoperate with C++ exceptions at this time. This means you ! cannot `@throw' an exception from Objective-C and `catch' it in ! C++, or vice versa (i.e., `throw ... @catch').  File: gcc.info, Node: Synchronization, Next: Fast enumeration, Prev: Exceptions, Up: Objective-C *************** GNU Objective-C provides support for syn *** 46027,46049 **** ... } ! Upon entering the '@synchronized' block, a thread of execution shall ! first check whether a lock has been placed on the corresponding 'guard' object by another thread. If it has, the current thread shall wait ! until the other thread relinquishes its lock. Once 'guard' becomes ! available, the current thread will place its own lock on it, execute the ! code contained in the '@synchronized' block, and finally relinquish the ! lock (thereby making 'guard' available to other threads). ! Unlike Java, Objective-C does not allow for entire methods to be marked ! '@synchronized'. Note that throwing exceptions out of '@synchronized' ! blocks is allowed, and will cause the guarding object to be unlocked ! properly. Because of the interactions between synchronization and exception ! handling, you can only use '@synchronized' when compiling with exceptions enabled, that is with the command line option ! '-fobjc-exceptions'.  File: gcc.info, Node: Fast enumeration, Next: Messaging with the GNU Objective-C runtime, Prev: Synchronization, Up: Objective-C --- 46523,46545 ---- ... } ! Upon entering the `@synchronized' block, a thread of execution shall ! first check whether a lock has been placed on the corresponding `guard' object by another thread. If it has, the current thread shall wait ! until the other thread relinquishes its lock. Once `guard' becomes ! available, the current thread will place its own lock on it, execute ! the code contained in the `@synchronized' block, and finally relinquish ! the lock (thereby making `guard' available to other threads). ! Unlike Java, Objective-C does not allow for entire methods to be ! marked `@synchronized'. Note that throwing exceptions out of ! `@synchronized' blocks is allowed, and will cause the guarding object ! to be unlocked properly. Because of the interactions between synchronization and exception ! handling, you can only use `@synchronized' when compiling with exceptions enabled, that is with the command line option ! `-fobjc-exceptions'.  File: gcc.info, Node: Fast enumeration, Next: Messaging with the GNU Objective-C runtime, Prev: Synchronization, Up: Objective-C *************** GNU Objective-C provides support for the *** 46074,46092 **** /* Do something with 'object' */ } ! 'array' needs to be an Objective-C object (usually a collection object, ! for example an array, a dictionary or a set) which implements the "Fast ! Enumeration Protocol" (see below). If you are using a Foundation ! library such as GNUstep Base or Apple Cocoa Foundation, all collection ! objects in the library implement this protocol and can be used in this ! way. ! The code above would iterate over all objects in 'array'. For each of ! them, it assigns it to 'object', then executes the 'Do something with 'object'' statements. Here is a fully worked-out example using a Foundation library (which ! provides the implementation of 'NSArray', 'NSString' and 'NSLog'): NSArray *array = [NSArray arrayWithObjects: @"1", @"2", @"3", nil]; NSString *object; --- 46570,46588 ---- /* Do something with 'object' */ } ! `array' needs to be an Objective-C object (usually a collection ! object, for example an array, a dictionary or a set) which implements ! the "Fast Enumeration Protocol" (see below). If you are using a ! Foundation library such as GNUstep Base or Apple Cocoa Foundation, all ! collection objects in the library implement this protocol and can be ! used in this way. ! The code above would iterate over all objects in `array'. For each of ! them, it assigns it to `object', then executes the `Do something with 'object'' statements. Here is a fully worked-out example using a Foundation library (which ! provides the implementation of `NSArray', `NSString' and `NSLog'): NSArray *array = [NSArray arrayWithObjects: @"1", @"2", @"3", nil]; NSString *object; *************** A c99-like declaration syntax is also al *** 46123,46130 **** but can save some typing. ! Note that the option '-std=c99' is not required to allow this syntax in ! Objective-C.  File: gcc.info, Node: Fast enumeration details, Next: Fast enumeration protocol, Prev: c99-like fast enumeration syntax, Up: Fast enumeration --- 46619,46626 ---- but can save some typing. ! Note that the option `-std=c99' is not required to allow this syntax ! in Objective-C.  File: gcc.info, Node: Fast enumeration details, Next: Fast enumeration protocol, Prev: c99-like fast enumeration syntax, Up: Fast enumeration *************** the code *** 46142,46150 **** here is what happens when you run it: ! * 'COLLECTION EXPRESSION' is evaluated exactly once and the result is ! used as the collection object to iterate over. This means it is ! safe to write code such as 'for (object in [NSDictionary keyEnumerator]) ...'. * the iteration is implemented by the compiler by repeatedly getting --- 46638,46646 ---- here is what happens when you run it: ! * `COLLECTION EXPRESSION' is evaluated exactly once and the result ! is used as the collection object to iterate over. This means it ! is safe to write code such as `for (object in [NSDictionary keyEnumerator]) ...'. * the iteration is implemented by the compiler by repeatedly getting *************** the code *** 46154,46185 **** objects are retrieved one by one (hence the name "fast enumeration"). ! * if there are no objects in the collection, then 'OBJECT EXPRESSION' ! is set to 'nil' and the loop immediately terminates. * if there are objects in the collection, then for each object in the ! collection (in the order they are returned) 'OBJECT EXPRESSION' is ! set to the object, then 'STATEMENTS' are executed. ! * 'STATEMENTS' can contain 'break' and 'continue' commands, which will abort the iteration or skip to the next loop iteration as expected. * when the iteration ends because there are no more objects to ! iterate over, 'OBJECT EXPRESSION' is set to 'nil'. This allows you ! to determine whether the iteration finished because a 'break' ! command was used (in which case 'OBJECT EXPRESSION' will remain set ! to the last object that was iterated over) or because it iterated ! over all the objects (in which case 'OBJECT EXPRESSION' will be set ! to 'nil'). ! * 'STATEMENTS' must not make any changes to the collection object; if ! they do, it is a hard error and the fast enumeration terminates by ! invoking 'objc_enumerationMutation', a runtime function that normally aborts the program but which can be customized by ! Foundation libraries via 'objc_set_mutation_handler' to do something different, such as raising an exception.  File: gcc.info, Node: Fast enumeration protocol, Prev: Fast enumeration details, Up: Fast enumeration --- 46650,46682 ---- objects are retrieved one by one (hence the name "fast enumeration"). ! * if there are no objects in the collection, then `OBJECT ! EXPRESSION' is set to `nil' and the loop immediately terminates. * if there are objects in the collection, then for each object in the ! collection (in the order they are returned) `OBJECT EXPRESSION' is ! set to the object, then `STATEMENTS' are executed. ! * `STATEMENTS' can contain `break' and `continue' commands, which will abort the iteration or skip to the next loop iteration as expected. * when the iteration ends because there are no more objects to ! iterate over, `OBJECT EXPRESSION' is set to `nil'. This allows ! you to determine whether the iteration finished because a `break' ! command was used (in which case `OBJECT EXPRESSION' will remain ! set to the last object that was iterated over) or because it ! iterated over all the objects (in which case `OBJECT EXPRESSION' ! will be set to `nil'). ! * `STATEMENTS' must not make any changes to the collection object; ! if they do, it is a hard error and the fast enumeration terminates ! by invoking `objc_enumerationMutation', a runtime function that normally aborts the program but which can be customized by ! Foundation libraries via `objc_set_mutation_handler' to do something different, such as raising an exception. +  File: gcc.info, Node: Fast enumeration protocol, Prev: Fast enumeration details, Up: Fast enumeration *************** enumeration, you need to have it impleme *** 46193,46199 **** objects: (id *)objects count: (unsigned long)len; ! where 'NSFastEnumerationState' must be defined in your code as follows: typedef struct { --- 46690,46696 ---- objects: (id *)objects count: (unsigned long)len; ! where `NSFastEnumerationState' must be defined in your code as follows: typedef struct { *************** enumeration, you need to have it impleme *** 46203,46213 **** unsigned long extra[5]; } NSFastEnumerationState; ! If no 'NSFastEnumerationState' is defined in your code, the compiler ! will automatically replace 'NSFastEnumerationState *' with 'struct __objcFastEnumerationState *', where that type is silently defined by the compiler in an identical way. This can be confusing and we ! recommend that you define 'NSFastEnumerationState' (as shown above) instead. The method is called repeatedly during a fast enumeration to retrieve --- 46700,46710 ---- unsigned long extra[5]; } NSFastEnumerationState; ! If no `NSFastEnumerationState' is defined in your code, the compiler ! will automatically replace `NSFastEnumerationState *' with `struct __objcFastEnumerationState *', where that type is silently defined by the compiler in an identical way. This can be confusing and we ! recommend that you define `NSFastEnumerationState' (as shown above) instead. The method is called repeatedly during a fast enumeration to retrieve *************** batches of objects. Each invocation of *** 46215,46252 **** next batch of objects. The return value of the method is the number of objects in the current ! batch; this should not exceed 'len', which is the maximum size of a batch as requested by the caller. The batch itself is returned in the ! 'itemsPtr' field of the 'NSFastEnumerationState' struct. ! To help with returning the objects, the 'objects' array is a C array ! preallocated by the caller (on the stack) of size 'len'. In many cases ! you can put the objects you want to return in that 'objects' array, then ! do 'itemsPtr = objects'. But you don't have to; if your collection ! already has the objects to return in some form of C array, it could ! return them from there instead. ! The 'state' and 'extra' fields of the 'NSFastEnumerationState' structure allows your collection object to keep track of the state of ! the enumeration. In a simple array implementation, 'state' may keep ! track of the index of the last object that was returned, and 'extra' may ! be unused. ! The 'mutationsPtr' field of the 'NSFastEnumerationState' is used to ! keep track of mutations. It should point to a number; before working on ! each object, the fast enumeration loop will check that this number has ! not changed. If it has, a mutation has happened and the fast ! enumeration will abort. So, 'mutationsPtr' could be set to point to some sort of version number of your collection, which is increased by ! one every time there is a change (for example when an object is added or ! removed). Or, if you are content with less strict mutation checks, it ! could point to the number of objects in your collection or some other ! value that can be checked to perform an approximate check that the ! collection has not been mutated. ! Finally, note how we declared the 'len' argument and the return value ! to be of type 'unsigned long'. They could also be declared to be of ! type 'unsigned int' and everything would still work.  File: gcc.info, Node: Messaging with the GNU Objective-C runtime, Prev: Fast enumeration, Up: Objective-C --- 46712,46749 ---- next batch of objects. The return value of the method is the number of objects in the current ! batch; this should not exceed `len', which is the maximum size of a batch as requested by the caller. The batch itself is returned in the ! `itemsPtr' field of the `NSFastEnumerationState' struct. ! To help with returning the objects, the `objects' array is a C array ! preallocated by the caller (on the stack) of size `len'. In many cases ! you can put the objects you want to return in that `objects' array, ! then do `itemsPtr = objects'. But you don't have to; if your ! collection already has the objects to return in some form of C array, ! it could return them from there instead. ! The `state' and `extra' fields of the `NSFastEnumerationState' structure allows your collection object to keep track of the state of ! the enumeration. In a simple array implementation, `state' may keep ! track of the index of the last object that was returned, and `extra' ! may be unused. ! The `mutationsPtr' field of the `NSFastEnumerationState' is used to ! keep track of mutations. It should point to a number; before working ! on each object, the fast enumeration loop will check that this number ! has not changed. If it has, a mutation has happened and the fast ! enumeration will abort. So, `mutationsPtr' could be set to point to some sort of version number of your collection, which is increased by ! one every time there is a change (for example when an object is added ! or removed). Or, if you are content with less strict mutation checks, ! it could point to the number of objects in your collection or some ! other value that can be checked to perform an approximate check that ! the collection has not been mutated. ! Finally, note how we declared the `len' argument and the return value ! to be of type `unsigned long'. They could also be declared to be of ! type `unsigned int' and everything would still work.  File: gcc.info, Node: Messaging with the GNU Objective-C runtime, Prev: Fast enumeration, Up: Objective-C *************** designed to be portable, and so is based *** 46262,46279 **** Sending a message in the GNU Objective-C runtime is composed of two separate steps. First, there is a call to the lookup function, ! 'objc_msg_lookup ()' (or, in the case of messages to super, ! 'objc_msg_lookup_super ()'). This runtime function takes as argument ! the receiver and the selector of the method to be called; it returns the ! 'IMP', that is a pointer to the function implementing the method. The ! second step of method invocation consists of casting this pointer function to the appropriate function pointer type, and calling the function pointed to it with the right arguments. For example, when the compiler encounters a method invocation such as ! '[object init]', it compiles it into a call to 'objc_msg_lookup (object, ! @selector(init))' followed by a cast of the returned value to the ! appropriate function pointer type, and then it calls it. * Menu: --- 46759,46776 ---- Sending a message in the GNU Objective-C runtime is composed of two separate steps. First, there is a call to the lookup function, ! `objc_msg_lookup ()' (or, in the case of messages to super, ! `objc_msg_lookup_super ()'). This runtime function takes as argument ! the receiver and the selector of the method to be called; it returns ! the `IMP', that is a pointer to the function implementing the method. ! The second step of method invocation consists of casting this pointer function to the appropriate function pointer type, and calling the function pointed to it with the right arguments. For example, when the compiler encounters a method invocation such as ! `[object init]', it compiles it into a call to `objc_msg_lookup ! (object, @selector(init))' followed by a cast of the returned value to ! the appropriate function pointer type, and then it calls it. * Menu: *************** File: gcc.info, Node: Dynamically regis *** 46286,46294 **** 8.10.1 Dynamically Registering Methods -------------------------------------- ! If 'objc_msg_lookup()' does not find a suitable method implementation, ! because the receiver does not implement the required method, it tries to ! see if the class can dynamically register the method. To do so, the runtime checks if the class of the receiver implements the method --- 46783,46791 ---- 8.10.1 Dynamically Registering Methods -------------------------------------- ! If `objc_msg_lookup()' does not find a suitable method implementation, ! because the receiver does not implement the required method, it tries ! to see if the class can dynamically register the method. To do so, the runtime checks if the class of the receiver implements the method *************** the method *** 46299,46322 **** + (BOOL) resolveClassMethod: (SEL)selector; ! in the case of a class method. If the class implements it, the runtime ! invokes it, passing as argument the selector of the original method, and ! if it returns 'YES', the runtime tries the lookup again, which could now ! succeed if a matching method was added dynamically by ! '+resolveInstanceMethod:' or '+resolveClassMethod:'. This allows classes to dynamically register methods (by adding them to ! the class using 'class_addMethod') when they are first called. To do ! so, a class should implement '+resolveInstanceMethod:' (or, depending on ! the case, '+resolveClassMethod:') and have it recognize the selectors of ! methods that can be registered dynamically at runtime, register them, ! and return 'YES'. It should return 'NO' for methods that it does not ! dynamically registered at runtime. ! If '+resolveInstanceMethod:' (or '+resolveClassMethod:') is not ! implemented or returns 'NO', the runtime then tries the forwarding hook. ! Support for '+resolveInstanceMethod:' and 'resolveClassMethod:' was added to the GNU Objective-C runtime in GCC version 4.6.  --- 46796,46819 ---- + (BOOL) resolveClassMethod: (SEL)selector; ! in the case of a class method. If the class implements it, the ! runtime invokes it, passing as argument the selector of the original ! method, and if it returns `YES', the runtime tries the lookup again, ! which could now succeed if a matching method was added dynamically by ! `+resolveInstanceMethod:' or `+resolveClassMethod:'. This allows classes to dynamically register methods (by adding them to ! the class using `class_addMethod') when they are first called. To do ! so, a class should implement `+resolveInstanceMethod:' (or, depending ! on the case, `+resolveClassMethod:') and have it recognize the ! selectors of methods that can be registered dynamically at runtime, ! register them, and return `YES'. It should return `NO' for methods ! that it does not dynamically registered at runtime. ! If `+resolveInstanceMethod:' (or `+resolveClassMethod:') is not ! implemented or returns `NO', the runtime then tries the forwarding hook. ! Support for `+resolveInstanceMethod:' and `resolveClassMethod:' was added to the GNU Objective-C runtime in GCC version 4.6.  *************** File: gcc.info, Node: Forwarding hook, *** 46326,46378 **** ---------------------- The GNU Objective-C runtime provides a hook, called ! '__objc_msg_forward2', which is called by 'objc_msg_lookup()' when it can't find a method implementation in the runtime tables and after ! calling '+resolveInstanceMethod:' and '+resolveClassMethod:' has been attempted and did not succeed in dynamically registering the method. To configure the hook, you set the global variable ! '__objc_msg_forward2' to a function with the same argument and return ! types of 'objc_msg_lookup()'. When 'objc_msg_lookup()' can not find a method implementation, it invokes the hook function you provided to get a method implementation to return. So, in practice ! '__objc_msg_forward2' allows you to extend 'objc_msg_lookup()' by adding ! some custom code that is called to do a further lookup when no standard ! method implementation can be found using the normal lookup. This hook is generally reserved for "Foundation" libraries such as GNUstep Base, which use it to implement their high-level method ! forwarding API, typically based around the 'forwardInvocation:' method. So, unless you are implementing your own "Foundation" library, you should not set this hook. ! In a typical forwarding implementation, the '__objc_msg_forward2' hook function determines the argument and return type of the method that is being looked up, and then creates a function that takes these arguments and has that return type, and returns it to the caller. Creating this function is non-trivial and is typically performed using a dedicated ! library such as 'libffi'. The forwarding method implementation thus created is returned by ! 'objc_msg_lookup()' and is executed as if it was a normal method ! implementation. When the forwarding method implementation is called, it ! is usually expected to pack all arguments into some sort of object ! (typically, an 'NSInvocation' in a "Foundation" library), and hand it ! over to the programmer ('forwardInvocation:') who is then allowed to manipulate the method invocation using a high-level API provided by the "Foundation" library. For example, the programmer may want to examine the method invocation arguments and name and potentially change them before forwarding the method invocation to one or more local objects ! ('performInvocation:') or even to remote objects (by using Distributed Objects or some other mechanism). When all this completes, the return value is passed back and must be returned correctly to the original caller. ! Note that the GNU Objective-C runtime currently provides no support for ! method forwarding or method invocations other than the ! '__objc_msg_forward2' hook. ! If the forwarding hook does not exist or returns 'NULL', the runtime currently attempts forwarding using an older, deprecated API, and if that fails, it aborts the program. In future versions of the GNU Objective-C runtime, the runtime will immediately abort. --- 46823,46875 ---- ---------------------- The GNU Objective-C runtime provides a hook, called ! `__objc_msg_forward2', which is called by `objc_msg_lookup()' when it can't find a method implementation in the runtime tables and after ! calling `+resolveInstanceMethod:' and `+resolveClassMethod:' has been attempted and did not succeed in dynamically registering the method. To configure the hook, you set the global variable ! `__objc_msg_forward2' to a function with the same argument and return ! types of `objc_msg_lookup()'. When `objc_msg_lookup()' can not find a method implementation, it invokes the hook function you provided to get a method implementation to return. So, in practice ! `__objc_msg_forward2' allows you to extend `objc_msg_lookup()' by ! adding some custom code that is called to do a further lookup when no ! standard method implementation can be found using the normal lookup. This hook is generally reserved for "Foundation" libraries such as GNUstep Base, which use it to implement their high-level method ! forwarding API, typically based around the `forwardInvocation:' method. So, unless you are implementing your own "Foundation" library, you should not set this hook. ! In a typical forwarding implementation, the `__objc_msg_forward2' hook function determines the argument and return type of the method that is being looked up, and then creates a function that takes these arguments and has that return type, and returns it to the caller. Creating this function is non-trivial and is typically performed using a dedicated ! library such as `libffi'. The forwarding method implementation thus created is returned by ! `objc_msg_lookup()' and is executed as if it was a normal method ! implementation. When the forwarding method implementation is called, ! it is usually expected to pack all arguments into some sort of object ! (typically, an `NSInvocation' in a "Foundation" library), and hand it ! over to the programmer (`forwardInvocation:') who is then allowed to manipulate the method invocation using a high-level API provided by the "Foundation" library. For example, the programmer may want to examine the method invocation arguments and name and potentially change them before forwarding the method invocation to one or more local objects ! (`performInvocation:') or even to remote objects (by using Distributed Objects or some other mechanism). When all this completes, the return value is passed back and must be returned correctly to the original caller. ! Note that the GNU Objective-C runtime currently provides no support ! for method forwarding or method invocations other than the ! `__objc_msg_forward2' hook. ! If the forwarding hook does not exist or returns `NULL', the runtime currently attempts forwarding using an older, deprecated API, and if that fails, it aborts the program. In future versions of the GNU Objective-C runtime, the runtime will immediately abort. *************** Binary compatibility encompasses several *** 46387,46402 **** "application binary interface (ABI)" The set of runtime conventions followed by all of the tools that ! deal with binary representations of a program, including compilers, ! assemblers, linkers, and language runtime support. Some ABIs are ! formal with a written specification, possibly designed by multiple ! interested parties. Others are simply the way things are actually ! done by a particular set of tools. "ABI conformance" ! A compiler conforms to an ABI if it generates code that follows all ! of the specifications enumerated by that ABI. A library conforms ! to an ABI if it is implemented according to that ABI. An application conforms to an ABI if it is built using tools that conform to that ABI and does not contain source code that specifically changes behavior specified by the ABI. --- 46884,46899 ---- "application binary interface (ABI)" The set of runtime conventions followed by all of the tools that ! deal with binary representations of a program, including ! compilers, assemblers, linkers, and language runtime support. ! Some ABIs are formal with a written specification, possibly ! designed by multiple interested parties. Others are simply the ! way things are actually done by a particular set of tools. "ABI conformance" ! A compiler conforms to an ABI if it generates code that follows ! all of the specifications enumerated by that ABI. A library ! conforms to an ABI if it is implemented according to that ABI. An application conforms to an ABI if it is built using tools that conform to that ABI and does not contain source code that specifically changes behavior specified by the ABI. *************** Binary compatibility encompasses several *** 46409,46418 **** Different sets of tools are interoperable if they generate files that can be used in the same program. The set of tools includes compilers, assemblers, linkers, libraries, header files, startup ! files, and debuggers. Binaries produced by different sets of tools ! are not interoperable unless they implement the same ABI. This ! applies to different versions of the same tools as well as tools ! from different vendors. "intercallability" Whether a function in a binary built by one set of tools can call a --- 46906,46915 ---- Different sets of tools are interoperable if they generate files that can be used in the same program. The set of tools includes compilers, assemblers, linkers, libraries, header files, startup ! files, and debuggers. Binaries produced by different sets of ! tools are not interoperable unless they implement the same ABI. ! This applies to different versions of the same tools as well as ! tools from different vendors. "intercallability" Whether a function in a binary built by one set of tools can call a *************** Binary compatibility encompasses several *** 46420,46430 **** of interoperability. "implementation-defined features" ! Language standards include lists of implementation-defined features ! whose behavior can vary from one implementation to another. Some ! of these features are normally covered by a platform's ABI and ! others are not. The features that are not covered by an ABI ! generally affect how a program behaves, but not intercallability. "compatibility" Conformance to the same ABI and the same behavior of --- 46917,46928 ---- of interoperability. "implementation-defined features" ! Language standards include lists of implementation-defined ! features whose behavior can vary from one implementation to ! another. Some of these features are normally covered by a ! platform's ABI and others are not. The features that are not ! covered by an ABI generally affect how a program behaves, but not ! intercallability. "compatibility" Conformance to the same ABI and the same behavior of *************** Binary compatibility encompasses several *** 46435,46452 **** --- 46933,46959 ---- affects code generation and runtime support for: * size and alignment of data types + * layout of structured types + * calling conventions + * register usage conventions + * interfaces for runtime arithmetic support + * object file formats In addition, the application binary interface implemented by a C++ compiler affects code generation and runtime support for: * name mangling + * exception handling + * invoking constructors and destructors + * layout, alignment, and padding of classes + * layout and alignment of virtual tables Some GCC compilation options cause the compiler to generate code that *************** GCC releases, but it is possible that we *** 46470,46476 **** make this difficult. Such problems could include different interpretations of the C++ ABI by different vendors, bugs in the ABI, or bugs in the implementation of the ABI in different compilers. GCC's ! '-Wabi' switch warns when G++ generates code that is probably not compatible with the C++ ABI. The C++ library used with a C++ compiler includes the Standard C++ --- 46977,46983 ---- make this difficult. Such problems could include different interpretations of the C++ ABI by different vendors, bugs in the ABI, or bugs in the implementation of the ABI in different compilers. GCC's ! `-Wabi' switch warns when G++ generates code that is probably not compatible with the C++ ABI. The C++ library used with a C++ compiler includes the Standard C++ *************** compiler and runtime support. *** 46484,46497 **** When G++ and another C++ compiler conform to the same C++ ABI, but the implementations of the Standard C++ Library that they normally use do ! not follow the same ABI for the Standard C++ Library, object files built ! with those compilers can be used in the same program only if they use ! the same C++ library. This requires specifying the location of the C++ ! library header files when invoking the compiler whose usual library is ! not being used. The location of GCC's C++ header files depends on how ! the GCC build was configured, but can be seen by using the G++ '-v' ! option. With default configuration options for G++ 3.3 the compile line ! for a different C++ compiler needs to include -IGCC_INSTALL_DIRECTORY/include/c++/3.3 --- 46991,47004 ---- When G++ and another C++ compiler conform to the same C++ ABI, but the implementations of the Standard C++ Library that they normally use do ! not follow the same ABI for the Standard C++ Library, object files ! built with those compilers can be used in the same program only if they ! use the same C++ library. This requires specifying the location of the ! C++ library header files when invoking the compiler whose usual library ! is not being used. The location of GCC's C++ header files depends on ! how the GCC build was configured, but can be seen by using the G++ `-v' ! option. With default configuration options for G++ 3.3 the compile ! line for a different C++ compiler needs to include -IGCC_INSTALL_DIRECTORY/include/c++/3.3 *************** files for that other library. *** 46501,46525 **** The most straightforward way to link a program to use a particular C++ library is to use a C++ driver that specifies that C++ library by ! default. The 'g++' driver, for example, tells the linker where to find ! GCC's C++ library ('libstdc++') plus the other libraries and startup files it needs, in the proper order. If a program must use a different C++ library and it's not possible to do the final link using a C++ driver that uses that library by default, ! it is necessary to tell 'g++' the location and name of that library. It ! might also be necessary to specify different startup files and other runtime support libraries, and to suppress the use of GCC's support ! libraries with one or more of the options '-nostdlib', '-nostartfiles', ! and '-nodefaultlibs'.  File: gcc.info, Node: Gcov, Next: Gcov-tool, Prev: Compatibility, Up: Top ! 10 'gcov'--a Test Coverage Program ********************************** ! 'gcov' is a tool you can use in conjunction with GCC to test code coverage in your programs. * Menu: --- 47008,47032 ---- The most straightforward way to link a program to use a particular C++ library is to use a C++ driver that specifies that C++ library by ! default. The `g++' driver, for example, tells the linker where to find ! GCC's C++ library (`libstdc++') plus the other libraries and startup files it needs, in the proper order. If a program must use a different C++ library and it's not possible to do the final link using a C++ driver that uses that library by default, ! it is necessary to tell `g++' the location and name of that library. ! It might also be necessary to specify different startup files and other runtime support libraries, and to suppress the use of GCC's support ! libraries with one or more of the options `-nostdlib', `-nostartfiles', ! and `-nodefaultlibs'.  File: gcc.info, Node: Gcov, Next: Gcov-tool, Prev: Compatibility, Up: Top ! 10 `gcov'--a Test Coverage Program ********************************** ! `gcov' is a tool you can use in conjunction with GCC to test code coverage in your programs. * Menu: *************** coverage in your programs. *** 46533,46551 ****  File: gcc.info, Node: Gcov Intro, Next: Invoking Gcov, Up: Gcov ! 10.1 Introduction to 'gcov' =========================== ! 'gcov' is a test coverage program. Use it in concert with GCC to ! analyze your programs to help create more efficient, faster running code ! and to discover untested parts of your program. You can use 'gcov' as a ! profiling tool to help discover where your optimization efforts will ! best affect your code. You can also use 'gcov' along with the other ! profiling tool, 'gprof', to assess which parts of your code use the ! greatest amount of computing time. Profiling tools help you analyze your code's performance. Using a ! profiler such as 'gcov' or 'gprof', you can find out some basic performance statistics, such as: * how often each line of code executes --- 47040,47058 ----  File: gcc.info, Node: Gcov Intro, Next: Invoking Gcov, Up: Gcov ! 10.1 Introduction to `gcov' =========================== ! `gcov' is a test coverage program. Use it in concert with GCC to ! analyze your programs to help create more efficient, faster running ! code and to discover untested parts of your program. You can use ! `gcov' as a profiling tool to help discover where your optimization ! efforts will best affect your code. You can also use `gcov' along with ! the other profiling tool, `gprof', to assess which parts of your code ! use the greatest amount of computing time. Profiling tools help you analyze your code's performance. Using a ! profiler such as `gcov' or `gprof', you can find out some basic performance statistics, such as: * how often each line of code executes *************** performance statistics, such as: *** 46556,46562 **** Once you know these things about how your code works when compiled, you can look at each module to see which modules should be optimized. ! 'gcov' helps you determine where to work on optimization. Software developers also use coverage testing in concert with testsuites, to make sure software is actually good enough for a release. --- 47063,47069 ---- Once you know these things about how your code works when compiled, you can look at each module to see which modules should be optimized. ! `gcov' helps you determine where to work on optimization. Software developers also use coverage testing in concert with testsuites, to make sure software is actually good enough for a release. *************** to be added to the testsuites to create *** 46567,46702 **** final product. You should compile your code without optimization if you plan to use ! 'gcov' because the optimization, by combining some lines of code into one function, may not give you as much information as you need to look ! for 'hot spots' where the code is using a great deal of computer time. ! Likewise, because 'gcov' accumulates statistics by line (at the lowest ! resolution), it works best with a programming style that places only one ! statement on each line. If you use complicated macros that expand to ! loops or to other control structures, the statistics are less helpful--they only report on the line where the macro call appears. If your complex macros behave like functions, you can replace them with inline functions to solve this problem. ! 'gcov' creates a logfile called 'SOURCEFILE.gcov' which indicates how ! many times each line of a source file 'SOURCEFILE.c' has executed. You ! can use these logfiles along with 'gprof' to aid in fine-tuning the ! performance of your programs. 'gprof' gives timing information you can ! use along with the information you get from 'gcov'. ! 'gcov' works only on code compiled with GCC. It is not compatible with ! any other profiling or test coverage mechanism.  File: gcc.info, Node: Invoking Gcov, Next: Gcov and Optimization, Prev: Gcov Intro, Up: Gcov ! 10.2 Invoking 'gcov' ==================== gcov [OPTIONS] FILES ! 'gcov' accepts the following options: ! ! '-h' ! '--help' ! Display help about using 'gcov' (on the standard output), and exit ! without doing any further processing. ! ! '-v' ! '--version' ! Display the 'gcov' version number (on the standard output), and ! exit without doing any further processing. ! '-a' ! '--all-blocks' Write individual execution counts for every basic block. Normally gcov outputs execution counts only for the main blocks of a line. With this option you can determine if blocks within a single line are not being executed. ! '-b' ! '--branch-probabilities' Write branch frequencies to the output file, and write branch ! summary info to the standard output. This option allows you to see ! how often each branch in your program was taken. Unconditional ! branches will not be shown, unless the '-u' option is given. ! '-c' ! '--branch-counts' Write branch frequencies as the number of branches taken, rather than the percentage of branches taken. ! '-n' ! '--no-output' ! Do not create the 'gcov' output file. ! ! '-l' ! '--long-file-names' ! Create long file names for included source files. For example, if ! the header file 'x.h' contains code, and was included in the file ! 'a.c', then running 'gcov' on the file 'a.c' will produce an output ! file called 'a.c##x.h.gcov' instead of 'x.h.gcov'. This can be ! useful if 'x.h' is included in multiple source files and you want ! to see the individual contributions. If you use the '-p' option, ! both the including and included file names will be complete path ! names. ! ! '-p' ! '--preserve-paths' ! Preserve complete path information in the names of generated ! '.gcov' files. Without this option, just the filename component is ! used. With this option, all directories are used, with '/' ! characters translated to '#' characters, '.' directory components ! removed and unremoveable '..' components renamed to '^'. This is ! useful if sourcefiles are in several different directories. ! ! '-r' ! '--relative-only' ! Only output information about source files with a relative pathname ! (after source prefix elision). Absolute paths are usually system ! header files and coverage of any inline functions therein is ! normally uninteresting. ! '-f' ! '--function-summaries' Output summaries for each function in addition to the file level summary. ! '-o DIRECTORY|FILE' ! '--object-directory DIRECTORY' ! '--object-file FILE' ! Specify either the directory containing the gcov data files, or the ! object path name. The '.gcno', and '.gcda' data files are searched ! for using this option. If a directory is specified, the data files ! are in that directory and named after the input file name, without ! its extension. If a file is specified here, the data files are ! named after that file, without its extension. ! ! '-s DIRECTORY' ! '--source-prefix DIRECTORY' ! A prefix for source file names to remove when generating the output ! coverage files. This option is useful when building in a separate ! directory, and the pathname to the source directory is not wanted ! when determining the output file names. Note that this prefix ! detection is applied before determining whether the source file is ! absolute. ! ! '-u' ! '--unconditional-branches' ! When branch probabilities are given, include those of unconditional ! branches. Unconditional branches are normally not interesting. ! ! '-d' ! '--display-progress' ! Display the progress on the standard output. ! '-i' ! '--intermediate-format' Output gcov file in an easy-to-parse intermediate text format that ! can be used by 'lcov' or other tools. The output is a single ! '.gcov' file per '.gcda' file. No source code is required. ! The format of the intermediate '.gcov' file is plain text with one entry per line file:SOURCE_FILE_NAME --- 47074,47150 ---- final product. You should compile your code without optimization if you plan to use ! `gcov' because the optimization, by combining some lines of code into one function, may not give you as much information as you need to look ! for `hot spots' where the code is using a great deal of computer time. ! Likewise, because `gcov' accumulates statistics by line (at the lowest ! resolution), it works best with a programming style that places only ! one statement on each line. If you use complicated macros that expand ! to loops or to other control structures, the statistics are less helpful--they only report on the line where the macro call appears. If your complex macros behave like functions, you can replace them with inline functions to solve this problem. ! `gcov' creates a logfile called `SOURCEFILE.gcov' which indicates how ! many times each line of a source file `SOURCEFILE.c' has executed. You ! can use these logfiles along with `gprof' to aid in fine-tuning the ! performance of your programs. `gprof' gives timing information you can ! use along with the information you get from `gcov'. ! `gcov' works only on code compiled with GCC. It is not compatible ! with any other profiling or test coverage mechanism.  File: gcc.info, Node: Invoking Gcov, Next: Gcov and Optimization, Prev: Gcov Intro, Up: Gcov ! 10.2 Invoking `gcov' ==================== gcov [OPTIONS] FILES ! `gcov' accepts the following options: ! `-a' ! `--all-blocks' Write individual execution counts for every basic block. Normally gcov outputs execution counts only for the main blocks of a line. With this option you can determine if blocks within a single line are not being executed. ! `-b' ! `--branch-probabilities' Write branch frequencies to the output file, and write branch ! summary info to the standard output. This option allows you to ! see how often each branch in your program was taken. ! Unconditional branches will not be shown, unless the `-u' option ! is given. ! `-c' ! `--branch-counts' Write branch frequencies as the number of branches taken, rather than the percentage of branches taken. ! `-d' ! `--display-progress' ! Display the progress on the standard output. ! `-f' ! `--function-summaries' Output summaries for each function in addition to the file level summary. ! `-h' ! `--help' ! Display help about using `gcov' (on the standard output), and exit ! without doing any further processing. ! `-i' ! `--intermediate-format' Output gcov file in an easy-to-parse intermediate text format that ! can be used by `lcov' or other tools. The output is a single ! `.gcov' file per `.gcda' file. No source code is required. ! The format of the intermediate `.gcov' file is plain text with one entry per line file:SOURCE_FILE_NAME *************** File: gcc.info, Node: Invoking Gcov, N *** 46713,46719 **** file. All entries following a FILE pertain to that source file until the next FILE entry. ! Here is a sample when '-i' is used in conjunction with '-b' option: file:array.cc function:11,1,_Z3sumRKSt6vectorIPiSaIS0_EE --- 47161,47167 ---- file. All entries following a FILE pertain to that source file until the next FILE entry. ! Here is a sample when `-i' is used in conjunction with `-b' option: file:array.cc function:11,1,_Z3sumRKSt6vectorIPiSaIS0_EE *************** File: gcc.info, Node: Invoking Gcov, N *** 46725,46797 **** lcount:26,1 branch:28,nottaken ! '-m' ! '--demangled-names' ! Display demangled function names in output. The default is to show mangled function names. ! 'gcov' should be run with the current directory the same as that when you invoked the compiler. Otherwise it will not be able to locate the ! source files. 'gcov' produces files called 'MANGLEDNAME.gcov' in the ! current directory. These contain the coverage information of the source ! file they correspond to. One '.gcov' file is produced for each source ! (or header) file containing code, which was compiled to produce the data ! files. The MANGLEDNAME part of the output file name is usually simply ! the source file name, but can be something more complicated if the '-l' ! or '-p' options are given. Refer to those options for details. ! If you invoke 'gcov' with multiple input files, the contributions from ! each input file are summed. Typically you would invoke it with the same ! list of files as the final link of your executable. ! The '.gcov' files contain the ':' separated fields along with program source code. The format is EXECUTION_COUNT:LINE_NUMBER:SOURCE LINE TEXT Additional block information may succeed each line, when requested by ! command line option. The EXECUTION_COUNT is '-' for lines containing no ! code. Unexecuted lines are marked '#####' or '====', depending on whether they are reachable by non-exceptional paths or only exceptional ! paths such as C++ exception handlers, respectively. ! Some lines of information at the start have LINE_NUMBER of zero. These ! preamble lines are of the form -:0:TAG:VALUE The ordering and number of these preamble lines will be augmented as ! 'gcov' development progresses -- do not rely on them remaining unchanged. Use TAG to locate a particular preamble line. The additional block information is of the form TAG INFORMATION ! The INFORMATION is human readable, but designed to be simple enough for ! machine parsing too. When printing percentages, 0% and 100% are only printed when the values are _exactly_ 0% and 100% respectively. Other values which would conventionally be rounded to 0% or 100% are instead printed as the nearest non-boundary value. ! When using 'gcov', you must first compile your program with two special ! GCC options: '-fprofile-arcs -ftest-coverage'. This tells the compiler ! to generate additional information needed by gcov (basically a flow ! graph of the program) and also includes additional code in the object ! files for generating the extra profiling information needed by gcov. ! These additional files are placed in the directory where the object file ! is located. Running the program will cause profile output to be generated. For ! each source file compiled with '-fprofile-arcs', an accompanying '.gcda' ! file will be placed in the object file directory. ! Running 'gcov' with your program's source file names as arguments will now produce a listing of the code along with frequency of execution for ! each line. For example, if your program is called 'tmp.c', this is what ! you see when you use the basic 'gcov' facility: $ gcc -fprofile-arcs -ftest-coverage tmp.c $ a.out --- 47173,47323 ---- lcount:26,1 branch:28,nottaken ! `-l' ! `--long-file-names' ! Create long file names for included source files. For example, if ! the header file `x.h' contains code, and was included in the file ! `a.c', then running `gcov' on the file `a.c' will produce an ! output file called `a.c##x.h.gcov' instead of `x.h.gcov'. This ! can be useful if `x.h' is included in multiple source files and ! you want to see the individual contributions. If you use the `-p' ! option, both the including and included file names will be ! complete path names. ! ! `-m' ! `--demangled-names' ! Display demangled function names in output. The default is to show mangled function names. ! `-n' ! `--no-output' ! Do not create the `gcov' output file. ! ! `-o DIRECTORY|FILE' ! `--object-directory DIRECTORY' ! `--object-file FILE' ! Specify either the directory containing the gcov data files, or the ! object path name. The `.gcno', and `.gcda' data files are ! searched for using this option. If a directory is specified, the ! data files are in that directory and named after the input file ! name, without its extension. If a file is specified here, the ! data files are named after that file, without its extension. ! ! `-p' ! `--preserve-paths' ! Preserve complete path information in the names of generated ! `.gcov' files. Without this option, just the filename component is ! used. With this option, all directories are used, with `/' ! characters translated to `#' characters, `.' directory components ! removed and unremoveable `..' components renamed to `^'. This is ! useful if sourcefiles are in several different directories. ! ! `-r' ! `--relative-only' ! Only output information about source files with a relative pathname ! (after source prefix elision). Absolute paths are usually system ! header files and coverage of any inline functions therein is ! normally uninteresting. ! ! `-s DIRECTORY' ! `--source-prefix DIRECTORY' ! A prefix for source file names to remove when generating the output ! coverage files. This option is useful when building in a separate ! directory, and the pathname to the source directory is not wanted ! when determining the output file names. Note that this prefix ! detection is applied before determining whether the source file is ! absolute. ! ! `-u' ! `--unconditional-branches' ! When branch probabilities are given, include those of ! unconditional branches. Unconditional branches are normally not ! interesting. ! ! `-v' ! `--version' ! Display the `gcov' version number (on the standard output), and ! exit without doing any further processing. ! ! `-w' ! `--verbose' ! Print verbose informations related to basic blocks and arcs. ! ! `-x' ! `--hash-filenames' ! By default, gcov uses the full pathname of the source files to to ! create an output filename. This can lead to long filenames that ! can overflow filesystem limits. This option creates names of the ! form `SOURCE-FILE##MD5.gcov', where the SOURCE-FILE component is ! the final filename part and the MD5 component is calculated from ! the full mangled name that would have been used otherwise. ! ! ! `gcov' should be run with the current directory the same as that when you invoked the compiler. Otherwise it will not be able to locate the ! source files. `gcov' produces files called `MANGLEDNAME.gcov' in the ! current directory. These contain the coverage information of the ! source file they correspond to. One `.gcov' file is produced for each ! source (or header) file containing code, which was compiled to produce ! the data files. The MANGLEDNAME part of the output file name is ! usually simply the source file name, but can be something more ! complicated if the `-l' or `-p' options are given. Refer to those ! options for details. ! If you invoke `gcov' with multiple input files, the contributions from ! each input file are summed. Typically you would invoke it with the ! same list of files as the final link of your executable. ! The `.gcov' files contain the `:' separated fields along with program source code. The format is EXECUTION_COUNT:LINE_NUMBER:SOURCE LINE TEXT Additional block information may succeed each line, when requested by ! command line option. The EXECUTION_COUNT is `-' for lines containing ! no code. Unexecuted lines are marked `#####' or `====', depending on whether they are reachable by non-exceptional paths or only exceptional ! paths such as C++ exception handlers, respectively. Given `-a' option, ! unexecuted blocks are marked `$$$$$' or `%%%%%', depending on whether a ! basic block is reachable via non-exceptional or exceptional paths. ! Some lines of information at the start have LINE_NUMBER of zero. ! These preamble lines are of the form -:0:TAG:VALUE The ordering and number of these preamble lines will be augmented as ! `gcov' development progresses -- do not rely on them remaining unchanged. Use TAG to locate a particular preamble line. The additional block information is of the form TAG INFORMATION ! The INFORMATION is human readable, but designed to be simple enough ! for machine parsing too. When printing percentages, 0% and 100% are only printed when the values are _exactly_ 0% and 100% respectively. Other values which would conventionally be rounded to 0% or 100% are instead printed as the nearest non-boundary value. ! When using `gcov', you must first compile your program with two ! special GCC options: `-fprofile-arcs -ftest-coverage'. This tells the ! compiler to generate additional information needed by gcov (basically a ! flow graph of the program) and also includes additional code in the ! object files for generating the extra profiling information needed by ! gcov. These additional files are placed in the directory where the ! object file is located. Running the program will cause profile output to be generated. For ! each source file compiled with `-fprofile-arcs', an accompanying ! `.gcda' file will be placed in the object file directory. ! Running `gcov' with your program's source file names as arguments will now produce a listing of the code along with frequency of execution for ! each line. For example, if your program is called `tmp.c', this is ! what you see when you use the basic `gcov' facility: $ gcc -fprofile-arcs -ftest-coverage tmp.c $ a.out *************** you see when you use the basic 'gcov' fa *** 46799,46805 **** 90.00% of 10 source lines executed in file tmp.c Creating tmp.c.gcov. ! The file 'tmp.c.gcov' contains output from 'gcov'. Here is a sample: -: 0:Source:tmp.c -: 0:Graph:tmp.gcno --- 47325,47331 ---- 90.00% of 10 source lines executed in file tmp.c Creating tmp.c.gcov. ! The file `tmp.c.gcov' contains output from `gcov'. Here is a sample: -: 0:Source:tmp.c -: 0:Graph:tmp.gcno *************** you see when you use the basic 'gcov' fa *** 46824,46831 **** 1: 16: return 0; -: 17:} ! When you use the '-a' option, you will get individual block counts, and ! the output looks like this: -: 0:Source:tmp.c -: 0:Graph:tmp.gcno --- 47350,47357 ---- 1: 16: return 0; -: 17:} ! When you use the `-a' option, you will get individual block counts, ! and the output looks like this: -: 0:Source:tmp.c -: 0:Graph:tmp.gcno *************** contain code, unless previous blocks end *** 46864,46876 **** execution count of a line is shown and subsequent lines show the execution counts for individual blocks that end on that line. After each block, the branch and call counts of the block will be shown, if ! the '-b' option is given. Because of the way GCC instruments calls, a call count can be shown after a line with no individual blocks. As you can see, line 13 contains a basic block that was not executed. ! When you use the '-b' option, your output looks like this: $ gcov -b tmp.c 90.00% of 10 source lines executed in file tmp.c --- 47390,47402 ---- execution count of a line is shown and subsequent lines show the execution counts for individual blocks that end on that line. After each block, the branch and call counts of the block will be shown, if ! the `-b' option is given. Because of the way GCC instruments calls, a call count can be shown after a line with no individual blocks. As you can see, line 13 contains a basic block that was not executed. ! When you use the `-b' option, your output looks like this: $ gcov -b tmp.c 90.00% of 10 source lines executed in file tmp.c *************** contains a basic block that was not exec *** 46879,46885 **** 50.00% of 2 calls executed in file tmp.c Creating tmp.c.gcov. ! Here is a sample of a resulting 'tmp.c.gcov' file: -: 0:Source:tmp.c -: 0:Graph:tmp.gcno --- 47405,47411 ---- 50.00% of 2 calls executed in file tmp.c Creating tmp.c.gcov. ! Here is a sample of a resulting `tmp.c.gcov' file: -: 0:Source:tmp.c -: 0:Graph:tmp.gcno *************** function's blocks were executed. *** 46917,46928 **** For each basic block, a line is printed after the last line of the basic block describing the branch or call that ends the basic block. ! There can be multiple branches and calls listed for a single source line ! if there are multiple basic blocks that end on that line. In this case, ! the branches and calls are each given a number. There is no simple way ! to map these branches and calls back to source constructs. In general, ! though, the lowest numbered branch or call will correspond to the ! leftmost construct on the source line. For a branch, if it was executed at least once, then a percentage indicating the number of times the branch was taken divided by the --- 47443,47454 ---- For each basic block, a line is printed after the last line of the basic block describing the branch or call that ends the basic block. ! There can be multiple branches and calls listed for a single source ! line if there are multiple basic blocks that end on that line. In this ! case, the branches and calls are each given a number. There is no ! simple way to map these branches and calls back to source constructs. ! In general, though, the lowest numbered branch or call will correspond ! to the leftmost construct on the source line. For a branch, if it was executed at least once, then a percentage indicating the number of times the branch was taken divided by the *************** message "never executed" is printed. *** 46932,46942 **** For a call, if it was executed at least once, then a percentage indicating the number of times the call returned divided by the number of times the call was executed will be printed. This will usually be ! 100%, but may be less for functions that call 'exit' or 'longjmp', and thus may not return every time they are called. The execution counts are cumulative. If the example program were ! executed again without removing the '.gcda' file, the count for the number of times each line in the source was executed would be added to the results of the previous run(s). This is potentially useful in several ways. For example, it could be used to accumulate data over a --- 47458,47468 ---- For a call, if it was executed at least once, then a percentage indicating the number of times the call returned divided by the number of times the call was executed will be printed. This will usually be ! 100%, but may be less for functions that call `exit' or `longjmp', and thus may not return every time they are called. The execution counts are cumulative. If the example program were ! executed again without removing the `.gcda' file, the count for the number of times each line in the source was executed would be added to the results of the previous run(s). This is potentially useful in several ways. For example, it could be used to accumulate data over a *************** number of program runs as part of a test *** 46944,46952 **** provide more accurate long-term information over a large number of program runs. ! The data in the '.gcda' files is saved immediately before the program ! exits. For each source file compiled with '-fprofile-arcs', the ! profiling code first attempts to read in an existing '.gcda' file; if the file doesn't match the executable (differing number of basic block counts) it will ignore the contents of the file. It then adds in the new execution counts and finally writes the data to the file. --- 47470,47478 ---- provide more accurate long-term information over a large number of program runs. ! The data in the `.gcda' files is saved immediately before the program ! exits. For each source file compiled with `-fprofile-arcs', the ! profiling code first attempts to read in an existing `.gcda' file; if the file doesn't match the executable (differing number of basic block counts) it will ignore the contents of the file. It then adds in the new execution counts and finally writes the data to the file. *************** new execution counts and finally writes *** 46954,46968 ****  File: gcc.info, Node: Gcov and Optimization, Next: Gcov Data Files, Prev: Invoking Gcov, Up: Gcov ! 10.3 Using 'gcov' with GCC Optimization ======================================= ! If you plan to use 'gcov' to help optimize your code, you must first ! compile your program with two special GCC options: '-fprofile-arcs -ftest-coverage'. Aside from that, you can use any other GCC options; but if you want to prove that every single line in your program was ! executed, you should not compile with optimization at the same time. On ! some machines the optimizer can eliminate some simple code lines by combining them with other lines. For example, code like this: if (a != b) --- 47480,47494 ----  File: gcc.info, Node: Gcov and Optimization, Next: Gcov Data Files, Prev: Invoking Gcov, Up: Gcov ! 10.3 Using `gcov' with GCC Optimization ======================================= ! If you plan to use `gcov' to help optimize your code, you must first ! compile your program with two special GCC options: `-fprofile-arcs -ftest-coverage'. Aside from that, you can use any other GCC options; but if you want to prove that every single line in your program was ! executed, you should not compile with optimization at the same time. ! On some machines the optimizer can eliminate some simple code lines by combining them with other lines. For example, code like this: if (a != b) *************** combining them with other lines. For ex *** 46971,46979 **** c = 0; can be compiled into one instruction on some machines. In this case, ! there is no way for 'gcov' to calculate separate execution counts for each line because there isn't separate code for each line. Hence the ! 'gcov' output looks like this if you compiled the program with optimization: 100: 12:if (a != b) --- 47497,47505 ---- c = 0; can be compiled into one instruction on some machines. In this case, ! there is no way for `gcov' to calculate separate execution counts for each line because there isn't separate code for each line. Hence the ! `gcov' output looks like this if you compiled the program with optimization: 100: 12:if (a != b) *************** shown depends on where the function is i *** 46993,47007 **** at all. If the function is not inlined, the compiler must emit an out of line ! copy of the function, in any object file that needs it. If 'fileA.o' ! and 'fileB.o' both contain out of line bodies of a particular inlineable ! function, they will also both contain coverage counts for that function. ! When 'fileA.o' and 'fileB.o' are linked together, the linker will, on ! many systems, select one of those out of line bodies for all calls to ! that function, and remove or ignore the other. Unfortunately, it will ! not remove the coverage counters for the unused function body. Hence ! when instrumented, all but one use of that function will show zero ! counts. If the function is inlined in several places, the block structure in each location might not be the same. For instance, a condition might --- 47519,47533 ---- at all. If the function is not inlined, the compiler must emit an out of line ! copy of the function, in any object file that needs it. If `fileA.o' ! and `fileB.o' both contain out of line bodies of a particular ! inlineable function, they will also both contain coverage counts for ! that function. When `fileA.o' and `fileB.o' are linked together, the ! linker will, on many systems, select one of those out of line bodies ! for all calls to that function, and remove or ignore the other. ! Unfortunately, it will not remove the coverage counters for the unused ! function body. Hence when instrumented, all but one use of that ! function will show zero counts. If the function is inlined in several places, the block structure in each location might not be the same. For instance, a condition might *************** now be calculable at compile time in som *** 47009,47048 **** coverage of all the uses of the inline function will be shown for the same source lines, the line counts themselves might seem inconsistent. ! Long-running applications can use the '_gcov_reset' and '_gcov_dump' facilities to restrict profile collection to the program region of ! interest. Calling '_gcov_reset(void)' will clear all profile counters ! to zero, and calling '_gcov_dump(void)' will cause the profile ! information collected at that point to be dumped to '.gcda' output files.  File: gcc.info, Node: Gcov Data Files, Next: Cross-profiling, Prev: Gcov and Optimization, Up: Gcov ! 10.4 Brief Description of 'gcov' Data Files =========================================== ! 'gcov' uses two files for profiling. The names of these files are derived from the original _object_ file by substituting the file suffix ! with either '.gcno', or '.gcda'. The files contain coverage and profile ! data stored in a platform-independent format. The '.gcno' files are ! placed in the same directory as the object file. By default, the ! '.gcda' files are also stored in the same directory as the object file, ! but the GCC '-fprofile-dir' option may be used to store the '.gcda' ! files in a separate directory. ! The '.gcno' notes file is generated when the source file is compiled ! with the GCC '-ftest-coverage' option. It contains information to reconstruct the basic block graphs and assign source line numbers to blocks. ! The '.gcda' count data file is generated when a program containing ! object files built with the GCC '-fprofile-arcs' option is executed. A ! separate '.gcda' file is created for each object file compiled with this ! option. It contains arc transition counts, value profile counts, and ! some summary information. ! The full details of the file format is specified in 'gcov-io.h', and functions provided in that header file should be used to access the coverage files. --- 47535,47574 ---- coverage of all the uses of the inline function will be shown for the same source lines, the line counts themselves might seem inconsistent. ! Long-running applications can use the `_gcov_reset' and `_gcov_dump' facilities to restrict profile collection to the program region of ! interest. Calling `_gcov_reset(void)' will clear all profile counters ! to zero, and calling `_gcov_dump(void)' will cause the profile ! information collected at that point to be dumped to `.gcda' output files.  File: gcc.info, Node: Gcov Data Files, Next: Cross-profiling, Prev: Gcov and Optimization, Up: Gcov ! 10.4 Brief Description of `gcov' Data Files =========================================== ! `gcov' uses two files for profiling. The names of these files are derived from the original _object_ file by substituting the file suffix ! with either `.gcno', or `.gcda'. The files contain coverage and ! profile data stored in a platform-independent format. The `.gcno' ! files are placed in the same directory as the object file. By default, ! the `.gcda' files are also stored in the same directory as the object ! file, but the GCC `-fprofile-dir' option may be used to store the ! `.gcda' files in a separate directory. ! The `.gcno' notes file is generated when the source file is compiled ! with the GCC `-ftest-coverage' option. It contains information to reconstruct the basic block graphs and assign source line numbers to blocks. ! The `.gcda' count data file is generated when a program containing ! object files built with the GCC `-fprofile-arcs' option is executed. A ! separate `.gcda' file is created for each object file compiled with ! this option. It contains arc transition counts, value profile counts, ! and some summary information. ! The full details of the file format is specified in `gcov-io.h', and functions provided in that header file should be used to access the coverage files. *************** File: gcc.info, Node: Cross-profiling, *** 47053,47098 **** ==================================================== Running the program will cause profile output to be generated. For each ! source file compiled with '-fprofile-arcs', an accompanying '.gcda' file ! will be placed in the object file directory. That implicitly requires ! running the program on the same system as it was built or having the ! same absolute directory structure on the target system. The program ! will try to create the needed directory structure, if it is not already ! present. ! To support cross-profiling, a program compiled with '-fprofile-arcs' can relocate the data files based on two environment variables: ! * GCOV_PREFIX contains the prefix to add to the absolute paths in the ! object file. Prefix can be absolute, or relative. The default is ! no prefix. ! * GCOV_PREFIX_STRIP indicates the how many initial directory names to ! strip off the hardwired absolute paths. Default value is 0. _Note:_ If GCOV_PREFIX_STRIP is set without GCOV_PREFIX is ! undefined, then a relative path is made out of the hardwired absolute paths. ! For example, if the object file '/user/build/foo.o' was built with ! '-fprofile-arcs', the final executable will try to create the data file ! '/user/build/foo.gcda' when running on the target system. This will fail if the corresponding directory does not exist and it is unable to create it. This can be overcome by, for example, setting the ! environment as 'GCOV_PREFIX=/target/run' and 'GCOV_PREFIX_STRIP=1'. ! Such a setting will name the data file '/target/run/build/foo.gcda'. You must move the data files to the expected directory tree in order to ! use them for profile directed optimizations ('--use-profile'), or to use ! the 'gcov' tool.  ! File: gcc.info, Node: Gcov-tool, Next: Trouble, Prev: Gcov, Up: Top ! 11 'gcov-tool'--an Offline Gcda Profile Processing Tool ******************************************************* ! 'gcov-tool' is a tool you can use in conjunction with GCC to manipulate or process gcda profile files offline. * Menu: --- 47579,47624 ---- ==================================================== Running the program will cause profile output to be generated. For each ! source file compiled with `-fprofile-arcs', an accompanying `.gcda' ! file will be placed in the object file directory. That implicitly ! requires running the program on the same system as it was built or ! having the same absolute directory structure on the target system. The ! program will try to create the needed directory structure, if it is not ! already present. ! To support cross-profiling, a program compiled with `-fprofile-arcs' can relocate the data files based on two environment variables: ! * GCOV_PREFIX contains the prefix to add to the absolute paths in ! the object file. Prefix can be absolute, or relative. The default ! is no prefix. ! * GCOV_PREFIX_STRIP indicates the how many initial directory names ! to strip off the hardwired absolute paths. Default value is 0. _Note:_ If GCOV_PREFIX_STRIP is set without GCOV_PREFIX is ! undefined, then a relative path is made out of the hardwired absolute paths. ! For example, if the object file `/user/build/foo.o' was built with ! `-fprofile-arcs', the final executable will try to create the data file ! `/user/build/foo.gcda' when running on the target system. This will fail if the corresponding directory does not exist and it is unable to create it. This can be overcome by, for example, setting the ! environment as `GCOV_PREFIX=/target/run' and `GCOV_PREFIX_STRIP=1'. ! Such a setting will name the data file `/target/run/build/foo.gcda'. You must move the data files to the expected directory tree in order to ! use them for profile directed optimizations (`-fprofile-use'), or to ! use the `gcov' tool.  ! File: gcc.info, Node: Gcov-tool, Next: Gcov-dump, Prev: Gcov, Up: Top ! 11 `gcov-tool'--an Offline Gcda Profile Processing Tool ******************************************************* ! `gcov-tool' is a tool you can use in conjunction with GCC to manipulate or process gcda profile files offline. * Menu: *************** or process gcda profile files offline. *** 47103,47123 ****  File: gcc.info, Node: Gcov-tool Intro, Next: Invoking Gcov-tool, Up: Gcov-tool ! 11.1 Introduction to 'gcov-tool' ================================ ! 'gcov-tool' is an offline tool to process gcc's gcda profile files. Current gcov-tool supports the following functionalities: * merge two sets of profiles with weights. ! * read one set of profile and rewrite profile contents. One can scale or normalize the count values. Examples of the use cases for this tool are: ! * Collect the profiles for different set of inputs, and use this tool ! to merge them. One can specify the weight to factor in the relative importance of each input. * Rewrite the profile after removing a subset of the gcda files, --- 47629,47649 ----  File: gcc.info, Node: Gcov-tool Intro, Next: Invoking Gcov-tool, Up: Gcov-tool ! 11.1 Introduction to `gcov-tool' ================================ ! `gcov-tool' is an offline tool to process gcc's gcda profile files. Current gcov-tool supports the following functionalities: * merge two sets of profiles with weights. ! * read one set of profile and rewrite profile contents. One can scale or normalize the count values. Examples of the use cases for this tool are: ! * Collect the profiles for different set of inputs, and use this ! tool to merge them. One can specify the weight to factor in the relative importance of each input. * Rewrite the profile after removing a subset of the gcda files, *************** File: gcc.info, Node: Gcov-tool Intro, *** 47127,47255 **** the majority code as the runtime library. Note that for the merging operation, this profile generated offline may ! contain slight different values from the online merged profile. Here ! are a list of typical differences: * histogram difference: This offline tool recomputes the histogram ! after merging the counters. The resulting histogram, therefore, is ! precise. The online merging does not have this capability - the histogram is merged from two histograms and the result is an approximation. * summary checksum difference: Summary checksum uses a CRC32 ! operation. The value depends on the link list order of gcov-info ! objects. This order is different in gcov-tool from that in the ! online merge. It's expected to have different summary checksums. It does not really matter as the compiler does not use this checksum anywhere. * value profile counter values difference: Some counter values for ! value profile are runtime dependent, like heap addresses. It's normal to see some difference in these kind of counters.  File: gcc.info, Node: Invoking Gcov-tool, Prev: Gcov-tool Intro, Up: Gcov-tool ! 11.2 Invoking 'gcov-tool' ========================= gcov-tool [GLOBAL-OPTIONS] SUB_COMMAND [SUB_COMMAND-OPTIONS] PROFILE_DIR ! 'gcov-tool' accepts the following options: ! '-h' ! '--help' ! Display help about using 'gcov-tool' (on the standard output), and exit without doing any further processing. ! '-v' ! '--version' ! Display the 'gcov-tool' version number (on the standard output), and exit without doing any further processing. ! 'merge' Merge two profile directories. ! '-v' ! '--verbose' Set the verbose mode. ! '-o DIRECTORY' ! '--output DIRECTORY' ! Set the output profile directory. Default output directory ! name is MERGED_PROFILE. ! ! '-w W1,W2' ! '--weight W1,W2' Set the merge weights of the DIRECTORY1 and DIRECTORY2, ! respectively. The default weights are 1 for both. ! 'rewrite' Read the specified profile directory and rewrite to a new directory. ! '-v' ! '--verbose' ! Set the verbose mode. ! ! '-o DIRECTORY' ! '--output DIRECTORY' ! Set the output profile directory. Default output name is REWRITE_PROFILE. ! '-s FLOAT_OR_SIMPLE-FRAC_VALUE' ! '--scale FLOAT_OR_SIMPLE-FRAC_VALUE' ! Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such 1, 2, 2/3, and 5/3. ! '-n LONG_LONG_VALUE' ! '--normalize ' ! Normalize the profile. The specified value is the max counter ! value in the new profile. ! 'overlap' Computer the overlap score between the two specified profile directories. The overlap score is computed based on the arc ! profiles. It is defined as the sum of min (p1_counter[i] / p1_sum_all, p2_counter[i] / p2_sum_all), for all arc counter i, where p1_counter[i] and p2_counter[i] are two matched counters and p1_sum_all and p2_sum_all are the sum of counter values in profile 1 and profile 2, respectively. ! '-v' ! '--verbose' ! Set the verbose mode. ! ! '-h' ! '--hotonly' ! Only print info for hot objects/functions. ! ! '-f' ! '--function' Print function level overlap score. ! '-F' ! '--fullname' Print full gcda filename. ! '-o' ! '--object' Print object level overlap score. ! '-t FLOAT' ! '--hot_threshold ' Set the threshold for hot counter value.  ! File: gcc.info, Node: Trouble, Next: Bugs, Prev: Gcov-tool, Up: Top ! 12 Known Causes of Trouble with GCC *********************************** ! This section describes known problems that affect users of GCC. Most of ! these are not GCC bugs per se--if they were, we would fix them. But the ! result for a user may be like the result of a bug. Some of these problems are due to bugs in other software, some are missing features that are too much work to add, and some are places --- 47653,47832 ---- the majority code as the runtime library. Note that for the merging operation, this profile generated offline may ! contain slight different values from the online merged profile. Here are ! a list of typical differences: * histogram difference: This offline tool recomputes the histogram ! after merging the counters. The resulting histogram, therefore, is ! precise. The online merging does not have this capability - the histogram is merged from two histograms and the result is an approximation. * summary checksum difference: Summary checksum uses a CRC32 ! operation. The value depends on the link list order of gcov-info ! objects. This order is different in gcov-tool from that in the ! online merge. It's expected to have different summary checksums. It does not really matter as the compiler does not use this checksum anywhere. * value profile counter values difference: Some counter values for ! value profile are runtime dependent, like heap addresses. It's normal to see some difference in these kind of counters.  File: gcc.info, Node: Invoking Gcov-tool, Prev: Gcov-tool Intro, Up: Gcov-tool ! 11.2 Invoking `gcov-tool' ========================= gcov-tool [GLOBAL-OPTIONS] SUB_COMMAND [SUB_COMMAND-OPTIONS] PROFILE_DIR ! `gcov-tool' accepts the following options: ! `-h' ! `--help' ! Display help about using `gcov-tool' (on the standard output), and exit without doing any further processing. ! `-v' ! `--version' ! Display the `gcov-tool' version number (on the standard output), and exit without doing any further processing. ! `merge' Merge two profile directories. + `-o DIRECTORY' + `--output DIRECTORY' + Set the output profile directory. Default output directory + name is MERGED_PROFILE. ! `-v' ! `--verbose' Set the verbose mode. ! `-w W1,W2' ! `--weight W1,W2' Set the merge weights of the DIRECTORY1 and DIRECTORY2, ! respectively. The default weights are 1 for both. ! `rewrite' Read the specified profile directory and rewrite to a new directory. + `-n LONG_LONG_VALUE' + `--normalize ' + Normalize the profile. The specified value is the max counter + value in the new profile. ! `-o DIRECTORY' ! `--output DIRECTORY' ! Set the output profile directory. Default output name is REWRITE_PROFILE. ! `-s FLOAT_OR_SIMPLE-FRAC_VALUE' ! `--scale FLOAT_OR_SIMPLE-FRAC_VALUE' ! Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such 1, 2, 2/3, and 5/3. ! `-v' ! `--verbose' ! Set the verbose mode. ! `overlap' Computer the overlap score between the two specified profile directories. The overlap score is computed based on the arc ! profiles. It is defined as the sum of min (p1_counter[i] / p1_sum_all, p2_counter[i] / p2_sum_all), for all arc counter i, where p1_counter[i] and p2_counter[i] are two matched counters and p1_sum_all and p2_sum_all are the sum of counter values in profile 1 and profile 2, respectively. ! `-f' ! `--function' Print function level overlap score. ! `-F' ! `--fullname' Print full gcda filename. ! `-h' ! `--hotonly' ! Only print info for hot objects/functions. ! ! `-o' ! `--object' Print object level overlap score. ! `-t FLOAT' ! `--hot_threshold ' Set the threshold for hot counter value. + `-v' + `--verbose' + Set the verbose mode. + +  ! File: gcc.info, Node: Gcov-dump, Next: Trouble, Prev: Gcov-tool, Up: Top ! 12 `gcov-dump'--an Offline Gcda and Gcno Profile Dump Tool ! ********************************************************** ! ! * Menu: ! ! * Gcov-dump Intro:: Introduction to gcov-dump. ! * Invoking Gcov-dump:: How to use gcov-dump. ! !  ! File: gcc.info, Node: Gcov-dump Intro, Next: Invoking Gcov-dump, Up: Gcov-dump ! ! 12.1 Introduction to `gcov-dump' ! ================================ ! ! `gcov-dump' is a tool you can use in conjunction with GCC to dump ! content of gcda and gcno profile files offline. ! !  ! File: gcc.info, Node: Invoking Gcov-dump, Prev: Gcov-dump Intro, Up: Gcov-dump ! ! 12.2 Invoking `gcov-dump' ! ========================= ! ! Usage: gcov-dump [OPTION] ... GCOVFILES ! ! `gcov-dump' accepts the following options: ! ! `-h' ! `--help' ! Display help about using `gcov-dump' (on the standard output), and ! exit without doing any further processing. ! ! `-l' ! `--long' ! Dump content of records. ! ! `-p' ! `--positions' ! Dump positions of records. ! ! `-v' ! `--version' ! Display the `gcov-dump' version number (on the standard output), ! and exit without doing any further processing. ! ! `-w' ! `--working-sets' ! Dump working set computed from summary. ! !  ! File: gcc.info, Node: Trouble, Next: Bugs, Prev: Gcov-dump, Up: Top ! ! 13 Known Causes of Trouble with GCC *********************************** ! This section describes known problems that affect users of GCC. Most ! of these are not GCC bugs per se--if they were, we would fix them. But ! the result for a user may be like the result of a bug. Some of these problems are due to bugs in other software, some are missing features that are too much work to add, and some are places *************** where people's opinions differ as to wha *** 47274,47301 ****  File: gcc.info, Node: Actual Bugs, Next: Interoperation, Up: Trouble ! 12.1 Actual Bugs We Haven't Fixed Yet ===================================== ! * The 'fixincludes' script interacts badly with automounters; if the directory of system header files is automounted, it tends to be ! unmounted while 'fixincludes' is running. This would seem to be a bug in the automounter. We don't know any good way to work around it.  File: gcc.info, Node: Interoperation, Next: Incompatibilities, Prev: Actual Bugs, Up: Trouble ! 12.2 Interoperation =================== This section lists various difficulties encountered in using GCC ! together with other compilers or with the assemblers, linkers, libraries ! and debuggers on certain systems. * On many platforms, GCC supports a different ABI for C++ than do ! other compilers, so the object files compiled by GCC cannot be used ! with object files generated by another C++ compiler. An area where the difference is most apparent is name mangling. The use of different name mangling is intentional, to protect you --- 47851,47878 ----  File: gcc.info, Node: Actual Bugs, Next: Interoperation, Up: Trouble ! 13.1 Actual Bugs We Haven't Fixed Yet ===================================== ! * The `fixincludes' script interacts badly with automounters; if the directory of system header files is automounted, it tends to be ! unmounted while `fixincludes' is running. This would seem to be a bug in the automounter. We don't know any good way to work around it.  File: gcc.info, Node: Interoperation, Next: Incompatibilities, Prev: Actual Bugs, Up: Trouble ! 13.2 Interoperation =================== This section lists various difficulties encountered in using GCC ! together with other compilers or with the assemblers, linkers, ! libraries and debuggers on certain systems. * On many platforms, GCC supports a different ABI for C++ than do ! other compilers, so the object files compiled by GCC cannot be ! used with object files generated by another C++ compiler. An area where the difference is most apparent is name mangling. The use of different name mangling is intentional, to protect you *************** and debuggers on certain systems. *** 47312,47325 **** profiling causes static variable destructors (currently used only in C++) not to be run. ! * On a SPARC, GCC aligns all values of type 'double' on an 8-byte ! boundary, and it expects every 'double' to be so aligned. The Sun ! compiler usually gives 'double' values 8-byte alignment, with one ! exception: function arguments of type 'double' may not be aligned. As a result, if a function compiled with Sun CC takes the address ! of an argument of type 'double' and passes this pointer of type ! 'double *' to a function compiled with GCC, dereferencing the pointer may cause a fatal signal. One way to solve this problem is to compile your entire program --- 47889,47902 ---- profiling causes static variable destructors (currently used only in C++) not to be run. ! * On a SPARC, GCC aligns all values of type `double' on an 8-byte ! boundary, and it expects every `double' to be so aligned. The Sun ! compiler usually gives `double' values 8-byte alignment, with one ! exception: function arguments of type `double' may not be aligned. As a result, if a function compiled with Sun CC takes the address ! of an argument of type `double' and passes this pointer of type ! `double *' to a function compiled with GCC, dereferencing the pointer may cause a fatal signal. One way to solve this problem is to compile your entire program *************** and debuggers on certain systems. *** 47327,47334 **** compiled with Sun CC to copy the argument into a local variable; local variables are always properly aligned. A third solution is to modify the function that uses the pointer to dereference it via ! the following function 'access_double' instead of directly with ! '*': inline double access_double (double *unaligned_ptr) --- 47904,47911 ---- compiled with Sun CC to copy the argument into a local variable; local variables are always properly aligned. A third solution is to modify the function that uses the pointer to dereference it via ! the following function `access_double' instead of directly with ! `*': inline double access_double (double *unaligned_ptr) *************** and debuggers on certain systems. *** 47346,47372 **** Storing into the pointer can be done likewise with the same union. ! * On Solaris, the 'malloc' function in the 'libmalloc.a' library may allocate memory that is only 4 byte aligned. Since GCC on the SPARC assumes that doubles are 8 byte aligned, this may result in a fatal signal if doubles are stored in memory allocated by the ! 'libmalloc.a' library. ! The solution is to not use the 'libmalloc.a' library. Use instead ! 'malloc' and related functions from 'libc.a'; they do not have this ! problem. * On the HP PA machine, ADB sometimes fails to work on functions compiled with GCC. Specifically, it fails to work on functions ! that use 'alloca' or variable-size arrays. This is because GCC doesn't generate HP-UX unwind descriptors for such functions. It may even be impossible to generate them. ! * Debugging ('-g') is not supported on the HP PA machine, unless you use the preliminary GNU tools. ! * Taking the address of a label may generate errors from the HP-UX PA ! assembler. GAS for the PA does not have this problem. * Using floating point parameters for indirect calls to static functions will not work when using the HP assembler. There simply --- 47923,47949 ---- Storing into the pointer can be done likewise with the same union. ! * On Solaris, the `malloc' function in the `libmalloc.a' library may allocate memory that is only 4 byte aligned. Since GCC on the SPARC assumes that doubles are 8 byte aligned, this may result in a fatal signal if doubles are stored in memory allocated by the ! `libmalloc.a' library. ! The solution is to not use the `libmalloc.a' library. Use instead ! `malloc' and related functions from `libc.a'; they do not have ! this problem. * On the HP PA machine, ADB sometimes fails to work on functions compiled with GCC. Specifically, it fails to work on functions ! that use `alloca' or variable-size arrays. This is because GCC doesn't generate HP-UX unwind descriptors for such functions. It may even be impossible to generate them. ! * Debugging (`-g') is not supported on the HP PA machine, unless you use the preliminary GNU tools. ! * Taking the address of a label may generate errors from the HP-UX ! PA assembler. GAS for the PA does not have this problem. * Using floating point parameters for indirect calls to static functions will not work when using the HP assembler. There simply *************** and debuggers on certain systems. *** 47377,47388 **** * In extremely rare cases involving some very large functions you may receive errors from the HP linker complaining about an out of bounds unconditional branch offset. This used to occur more often ! in previous versions of GCC, but is now exceptionally rare. If you ! should run into it, you can work around by making your function ! smaller. ! * GCC compiled code sometimes emits warnings from the HP-UX assembler ! of the form: (warning) Use of GR3 when frame >= 8192 may cause conflict. --- 47954,47965 ---- * In extremely rare cases involving some very large functions you may receive errors from the HP linker complaining about an out of bounds unconditional branch offset. This used to occur more often ! in previous versions of GCC, but is now exceptionally rare. If ! you should run into it, you can work around by making your ! function smaller. ! * GCC compiled code sometimes emits warnings from the HP-UX ! assembler of the form: (warning) Use of GR3 when frame >= 8192 may cause conflict. *************** and debuggers on certain systems. *** 47391,47437 **** * In extremely rare cases involving some very large functions you may receive errors from the AIX Assembler complaining about a ! displacement that is too large. If you should run into it, you can ! work around by making your function smaller. ! * The 'libstdc++.a' library in GCC relies on the SVR4 dynamic linker semantics which merges global symbols between libraries and applications, especially necessary for C++ streams functionality. This is not the default behavior of AIX shared libraries and ! dynamic linking. 'libstdc++.a' is built on AIX with "runtime-linking" enabled so that symbol merging can occur. To ! utilize this feature, the application linked with 'libstdc++.a' ! must include the '-Wl,-brtl' flag on the link line. G++ cannot ! impose this because this option may interfere with the semantics of ! the user program and users may not always use 'g++' to link his or ! her application. Applications are not required to use the ! '-Wl,-brtl' flag on the link line--the rest of the 'libstdc++.a' ! library which is not dependent on the symbol merging semantics will ! continue to function correctly. * An application can interpose its own definition of functions for ! functions invoked by 'libstdc++.a' with "runtime-linking" enabled on AIX. To accomplish this the application must be linked with "runtime-linking" option and the functions explicitly must be ! exported by the application ('-Wl,-brtl,-bE:exportfile'). * AIX on the RS/6000 provides support (NLS) for environments outside of the United States. Compilers and assemblers use NLS to support locale-specific representations of various objects including ! floating-point numbers ('.' vs ',' for separating decimal fractions). There have been problems reported where the library linked with GCC does not produce the same floating-point formats that the assembler accepts. If you have this problem, set the ! 'LANG' environment variable to 'C' or 'En_US'. ! * Even if you specify '-fdollars-in-identifiers', you cannot ! successfully use '$' in identifiers on the RS/6000 due to a restriction in the IBM assembler. GAS supports these identifiers.  File: gcc.info, Node: Incompatibilities, Next: Fixed Headers, Prev: Interoperation, Up: Trouble ! 12.3 Incompatibilities of GCC ============================= There are several noteworthy incompatibilities between GNU C and K&R --- 47968,48015 ---- * In extremely rare cases involving some very large functions you may receive errors from the AIX Assembler complaining about a ! displacement that is too large. If you should run into it, you ! can work around by making your function smaller. ! * The `libstdc++.a' library in GCC relies on the SVR4 dynamic linker semantics which merges global symbols between libraries and applications, especially necessary for C++ streams functionality. This is not the default behavior of AIX shared libraries and ! dynamic linking. `libstdc++.a' is built on AIX with "runtime-linking" enabled so that symbol merging can occur. To ! utilize this feature, the application linked with `libstdc++.a' ! must include the `-Wl,-brtl' flag on the link line. G++ cannot ! impose this because this option may interfere with the semantics ! of the user program and users may not always use `g++' to link his ! or her application. Applications are not required to use the ! `-Wl,-brtl' flag on the link line--the rest of the `libstdc++.a' ! library which is not dependent on the symbol merging semantics ! will continue to function correctly. * An application can interpose its own definition of functions for ! functions invoked by `libstdc++.a' with "runtime-linking" enabled on AIX. To accomplish this the application must be linked with "runtime-linking" option and the functions explicitly must be ! exported by the application (`-Wl,-brtl,-bE:exportfile'). * AIX on the RS/6000 provides support (NLS) for environments outside of the United States. Compilers and assemblers use NLS to support locale-specific representations of various objects including ! floating-point numbers (`.' vs `,' for separating decimal fractions). There have been problems reported where the library linked with GCC does not produce the same floating-point formats that the assembler accepts. If you have this problem, set the ! `LANG' environment variable to `C' or `En_US'. ! * Even if you specify `-fdollars-in-identifiers', you cannot ! successfully use `$' in identifiers on the RS/6000 due to a restriction in the IBM assembler. GAS supports these identifiers. +  File: gcc.info, Node: Incompatibilities, Next: Fixed Headers, Prev: Interoperation, Up: Trouble ! 13.3 Incompatibilities of GCC ============================= There are several noteworthy incompatibilities between GNU C and K&R *************** There are several noteworthy incompatibi *** 47441,47463 **** identical-looking string constants are used, GCC stores only one copy of the string. ! One consequence is that you cannot call 'mktemp' with a string ! constant argument. The function 'mktemp' always alters the string its argument points to. ! Another consequence is that 'sscanf' does not work on some very old ! systems when passed a string constant as its format control string ! or input. This is because 'sscanf' incorrectly tries to write into ! the string constant. Likewise 'fscanf' and 'scanf'. The solution to these problems is to change the program to use ! 'char'-array variables with initialization strings for these purposes instead of string constants. ! * '-2147483648' is positive. ! This is because 2147483648 cannot fit in the type 'int', so ! (following the ISO C rules) its data type is 'unsigned long int'. Negating this value yields 2147483648 again. * GCC does not substitute macro arguments when they appear inside of --- 48019,48041 ---- identical-looking string constants are used, GCC stores only one copy of the string. ! One consequence is that you cannot call `mktemp' with a string ! constant argument. The function `mktemp' always alters the string its argument points to. ! Another consequence is that `sscanf' does not work on some very ! old systems when passed a string constant as its format control ! string or input. This is because `sscanf' incorrectly tries to ! write into the string constant. Likewise `fscanf' and `scanf'. The solution to these problems is to change the program to use ! `char'-array variables with initialization strings for these purposes instead of string constants. ! * `-2147483648' is positive. ! This is because 2147483648 cannot fit in the type `int', so ! (following the ISO C rules) its data type is `unsigned long int'. Negating this value yields 2147483648 again. * GCC does not substitute macro arguments when they appear inside of *************** There are several noteworthy incompatibi *** 47465,47474 **** #define foo(a) "a" ! will produce output '"a"' regardless of what the argument A is. ! * When you use 'setjmp' and 'longjmp', the only automatic variables ! guaranteed to remain valid are those declared 'volatile'. This is a consequence of automatic register allocation. Consider this function: --- 48043,48052 ---- #define foo(a) "a" ! will produce output `"a"' regardless of what the argument A is. ! * When you use `setjmp' and `longjmp', the only automatic variables ! guaranteed to remain valid are those declared `volatile'. This is a consequence of automatic register allocation. Consider this function: *************** There are several noteworthy incompatibi *** 47483,47498 **** return a; a = fun2 (); ! /* 'longjmp (j)' may occur in 'fun3'. */ return a + fun3 (); } ! Here 'a' may or may not be restored to its first value when the ! 'longjmp' occurs. If 'a' is allocated in a register, then its first value is restored; otherwise, it keeps the last value stored in it. ! If you use the '-W' option with the '-O' option, you will get a warning when GCC thinks such a problem might be possible. * Programs that use preprocessing directives in the middle of macro --- 48061,48076 ---- return a; a = fun2 (); ! /* `longjmp (j)' may occur in `fun3'. */ return a + fun3 (); } ! Here `a' may or may not be restored to its first value when the ! `longjmp' occurs. If `a' is allocated in a register, then its first value is restored; otherwise, it keeps the last value stored in it. ! If you use the `-W' option with the `-O' option, you will get a warning when GCC thinks such a problem might be possible. * Programs that use preprocessing directives in the middle of macro *************** There are several noteworthy incompatibi *** 47513,47529 **** words, they have the same scope as any other declaration in the same place. ! In some other C compilers, an 'extern' declaration affects all the rest of the file even if it happens within a block. ! * In traditional C, you can combine 'long', etc., with a typedef name, as shown here: typedef int foo; typedef long foo bar; ! In ISO C, this is not allowed: 'long' and other type modifiers ! require an explicit 'int'. * PCC allows typedef names to be used as function parameters. --- 48091,48107 ---- words, they have the same scope as any other declaration in the same place. ! In some other C compilers, an `extern' declaration affects all the rest of the file even if it happens within a block. ! * In traditional C, you can combine `long', etc., with a typedef name, as shown here: typedef int foo; typedef long foo bar; ! In ISO C, this is not allowed: `long' and other type modifiers ! require an explicit `int'. * PCC allows typedef names to be used as function parameters. *************** There are several noteworthy incompatibi *** 47533,47547 **** typedef int foo; typedef foo foo; ! * GCC treats all characters of identifiers as significant. According ! to K&R-1 (2.2), "No more than the first eight characters are ! significant, although more may be used.". Also according to K&R-1 ! (2.2), "An identifier is a sequence of letters and digits; the ! first character must be a letter. The underscore _ counts as a ! letter.", but GCC also allows dollar signs in identifiers. * PCC allows whitespace in the middle of compound assignment ! operators such as '+='. GCC, following the ISO standard, does not allow this. * GCC complains about unterminated character constants inside of --- 48111,48125 ---- typedef int foo; typedef foo foo; ! * GCC treats all characters of identifiers as significant. ! According to K&R-1 (2.2), "No more than the first eight characters ! are significant, although more may be used.". Also according to ! K&R-1 (2.2), "An identifier is a sequence of letters and digits; ! the first character must be a letter. The underscore _ counts as ! a letter.", but GCC also allows dollar signs in identifiers. * PCC allows whitespace in the middle of compound assignment ! operators such as `+='. GCC, following the ISO standard, does not allow this. * GCC complains about unterminated character constants inside of *************** There are several noteworthy incompatibi *** 47555,47578 **** #endif The best solution to such a problem is to put the text into an ! actual C comment delimited by '/*...*/'. ! * Many user programs contain the declaration 'long time ();'. In the past, the system header files on many systems did not actually ! declare 'time', so it did not matter what type your program ! declared it to return. But in systems with ISO C headers, 'time' ! is declared to return 'time_t', and if that is not the same as ! 'long', then 'long time ();' is erroneous. The solution is to change your program to use appropriate system ! headers ('' on systems with ISO C headers) and not to ! declare 'time' if the system header files declare it, or failing ! that to use 'time_t' as the return type of 'time'. ! * When compiling functions that return 'float', PCC converts it to a ! double. GCC actually returns a 'float'. If you are concerned with ! PCC compatibility, you should declare your functions to return ! 'double'; you might as well say what you mean. * When compiling functions that return structures or unions, GCC output code normally uses a method different from that used on most --- 48133,48156 ---- #endif The best solution to such a problem is to put the text into an ! actual C comment delimited by `/*...*/'. ! * Many user programs contain the declaration `long time ();'. In the past, the system header files on many systems did not actually ! declare `time', so it did not matter what type your program ! declared it to return. But in systems with ISO C headers, `time' ! is declared to return `time_t', and if that is not the same as ! `long', then `long time ();' is erroneous. The solution is to change your program to use appropriate system ! headers (`' on systems with ISO C headers) and not to ! declare `time' if the system header files declare it, or failing ! that to use `time_t' as the return type of `time'. ! * When compiling functions that return `float', PCC converts it to a ! double. GCC actually returns a `float'. If you are concerned ! with PCC compatibility, you should declare your functions to return ! `double'; you might as well say what you mean. * When compiling functions that return structures or unions, GCC output code normally uses a method different from that used on most *************** There are several noteworthy incompatibi *** 47581,47590 **** The method used by GCC is as follows: a structure or union which is 1, 2, 4 or 8 bytes long is returned like a scalar. A structure or ! union with any other size is stored into an address supplied by the ! caller (usually in a special, fixed register, but on some machines ! it is passed on the stack). The target hook ! 'TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address. By contrast, PCC on most target machines returns structures and unions of any size by copying the data into an area of static --- 48159,48168 ---- The method used by GCC is as follows: a structure or union which is 1, 2, 4 or 8 bytes long is returned like a scalar. A structure or ! union with any other size is stored into an address supplied by ! the caller (usually in a special, fixed register, but on some ! machines it is passed on the stack). The target hook ! `TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address. By contrast, PCC on most target machines returns structures and unions of any size by copying the data into an area of static *************** There are several noteworthy incompatibi *** 47599,47628 **** memory, but still returns small structures and unions in registers. You can tell GCC to use a compatible convention for all structure ! and union returning with the option '-fpcc-struct-return'. ! * GCC complains about program fragments such as '0x74ae-0x4000' which ! appear to be two hexadecimal constants separated by the minus operator. Actually, this string is a single "preprocessing token". ! Each such token must correspond to one token in C. Since this does ! not, GCC prints an error message. Although it may appear obvious ! that what is meant is an operator and two values, the ISO C ! standard specifically requires that this be treated as erroneous. A "preprocessing token" is a "preprocessing number" if it begins with a digit and is followed by letters, underscores, digits, ! periods and 'e+', 'e-', 'E+', 'E-', 'p+', 'p-', 'P+', or 'P-' ! character sequences. (In strict C90 mode, the sequences 'p+', ! 'p-', 'P+' and 'P-' cannot appear in preprocessing numbers.) ! To make the above program fragment valid, place whitespace in front ! of the minus sign. This whitespace will end the preprocessing ! number.  File: gcc.info, Node: Fixed Headers, Next: Standard Libraries, Prev: Incompatibilities, Up: Trouble ! 12.4 Fixed Header Files ======================= GCC needs to install corrected versions of some system header files. --- 48177,48206 ---- memory, but still returns small structures and unions in registers. You can tell GCC to use a compatible convention for all structure ! and union returning with the option `-fpcc-struct-return'. ! * GCC complains about program fragments such as `0x74ae-0x4000' ! which appear to be two hexadecimal constants separated by the minus operator. Actually, this string is a single "preprocessing token". ! Each such token must correspond to one token in C. Since this ! does not, GCC prints an error message. Although it may appear ! obvious that what is meant is an operator and two values, the ISO ! C standard specifically requires that this be treated as erroneous. A "preprocessing token" is a "preprocessing number" if it begins with a digit and is followed by letters, underscores, digits, ! periods and `e+', `e-', `E+', `E-', `p+', `p-', `P+', or `P-' ! character sequences. (In strict C90 mode, the sequences `p+', ! `p-', `P+' and `P-' cannot appear in preprocessing numbers.) ! To make the above program fragment valid, place whitespace in ! front of the minus sign. This whitespace will end the ! preprocessing number.  File: gcc.info, Node: Fixed Headers, Next: Standard Libraries, Prev: Incompatibilities, Up: Trouble ! 13.4 Fixed Header Files ======================= GCC needs to install corrected versions of some system header files. *************** incompatible with ISO C, and some depend *** 47632,47645 **** compilers. Installing GCC automatically creates and installs the fixed header ! files, by running a program called 'fixincludes'. Normally, you don't need to pay attention to this. But there are cases where it doesn't do the right thing automatically. * If you update the system's header files, such as by installing a new system version, the fixed header files of GCC are not ! automatically updated. They can be updated using the 'mkheaders' ! script installed in 'LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'. * On some systems, header file directories contain machine-specific symbolic links in certain places. This makes it possible to share --- 48210,48223 ---- compilers. Installing GCC automatically creates and installs the fixed header ! files, by running a program called `fixincludes'. Normally, you don't need to pay attention to this. But there are cases where it doesn't do the right thing automatically. * If you update the system's header files, such as by installing a new system version, the fixed header files of GCC are not ! automatically updated. They can be updated using the `mkheaders' ! script installed in `LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'. * On some systems, header file directories contain machine-specific symbolic links in certain places. This makes it possible to share *************** the right thing automatically. *** 47648,47664 **** The programs that fix the header files do not understand this special way of using symbolic links; therefore, the directory of ! fixed header files is good only for the machine model used to build ! it. It is possible to make separate sets of fixed header files for the ! different machine models, and arrange a structure of symbolic links ! so as to use the proper set, but you'll have to do this by hand.  File: gcc.info, Node: Standard Libraries, Next: Disappointments, Prev: Fixed Headers, Up: Trouble ! 12.5 Standard Libraries ======================= GCC by itself attempts to be a conforming freestanding implementation. --- 48226,48243 ---- The programs that fix the header files do not understand this special way of using symbolic links; therefore, the directory of ! fixed header files is good only for the machine model used to ! build it. It is possible to make separate sets of fixed header files for the ! different machine models, and arrange a structure of symbolic ! links so as to use the proper set, but you'll have to do this by ! hand.  File: gcc.info, Node: Standard Libraries, Next: Disappointments, Prev: Fixed Headers, Up: Trouble ! 13.5 Standard Libraries ======================= GCC by itself attempts to be a conforming freestanding implementation. *************** what this means. Beyond the library fac *** 47667,47692 **** implementation, the rest of the C library is supplied by the vendor of the operating system. If that C library doesn't conform to the C standards, then your programs might get warnings (especially when using ! '-Wall') that you don't expect. ! For example, the 'sprintf' function on SunOS 4.1.3 returns 'char *' ! while the C standard says that 'sprintf' returns an 'int'. The ! 'fixincludes' program could make the prototype for this function match the Standard, but that would be wrong, since the function will still ! return 'char *'. If you need a Standard compliant library, then you need to find one, as ! GCC does not provide one. The GNU C library (called 'glibc') provides ISO C, POSIX, BSD, SystemV and X/Open compatibility for GNU/Linux and HURD-based GNU systems; no recent version of it supports other systems, though some very old versions did. Version 2.2 of the GNU C library ! includes nearly complete C99 support. You could also ask your operating ! system vendor if newer libraries are available.  File: gcc.info, Node: Disappointments, Next: C++ Misunderstandings, Prev: Standard Libraries, Up: Trouble ! 12.6 Disappointments and Misunderstandings ========================================== These problems are perhaps regrettable, but we don't know any practical --- 48246,48271 ---- implementation, the rest of the C library is supplied by the vendor of the operating system. If that C library doesn't conform to the C standards, then your programs might get warnings (especially when using ! `-Wall') that you don't expect. ! For example, the `sprintf' function on SunOS 4.1.3 returns `char *' ! while the C standard says that `sprintf' returns an `int'. The ! `fixincludes' program could make the prototype for this function match the Standard, but that would be wrong, since the function will still ! return `char *'. If you need a Standard compliant library, then you need to find one, as ! GCC does not provide one. The GNU C library (called `glibc') provides ISO C, POSIX, BSD, SystemV and X/Open compatibility for GNU/Linux and HURD-based GNU systems; no recent version of it supports other systems, though some very old versions did. Version 2.2 of the GNU C library ! includes nearly complete C99 support. You could also ask your ! operating system vendor if newer libraries are available.  File: gcc.info, Node: Disappointments, Next: C++ Misunderstandings, Prev: Standard Libraries, Up: Trouble ! 13.6 Disappointments and Misunderstandings ========================================== These problems are perhaps regrettable, but we don't know any practical *************** way around them. *** 47714,47740 **** int foo (struct mumble *x) { ... } ! This code really is erroneous, because the scope of 'struct mumble' ! in the prototype is limited to the argument list containing it. It ! does not refer to the 'struct mumble' defined with file scope ! immediately below--they are two unrelated types with similar names ! in different scopes. ! But in the definition of 'foo', the file-scope type is used because ! that is available to be inherited. Thus, the definition and the ! prototype do not match, and you get an error. This behavior may seem silly, but it's what the ISO standard specifies. It is easy enough for you to make your code work by ! moving the definition of 'struct mumble' above the prototype. It's ! not worth being incompatible with ISO C just to avoid an error for ! the example shown above. * Accesses to bit-fields even in volatile objects works by accessing larger objects, such as a byte or a word. You cannot rely on what ! size of object is accessed in order to read or write the bit-field; ! it may even vary for a given bit-field according to the precise ! usage. If you care about controlling the amount of memory that is accessed, use volatile but do not use bit-fields. --- 48293,48319 ---- int foo (struct mumble *x) { ... } ! This code really is erroneous, because the scope of `struct ! mumble' in the prototype is limited to the argument list ! containing it. It does not refer to the `struct mumble' defined ! with file scope immediately below--they are two unrelated types ! with similar names in different scopes. ! But in the definition of `foo', the file-scope type is used ! because that is available to be inherited. Thus, the definition ! and the prototype do not match, and you get an error. This behavior may seem silly, but it's what the ISO standard specifies. It is easy enough for you to make your code work by ! moving the definition of `struct mumble' above the prototype. ! It's not worth being incompatible with ISO C just to avoid an ! error for the example shown above. * Accesses to bit-fields even in volatile objects works by accessing larger objects, such as a byte or a word. You cannot rely on what ! size of object is accessed in order to read or write the ! bit-field; it may even vary for a given bit-field according to the ! precise usage. If you care about controlling the amount of memory that is accessed, use volatile but do not use bit-fields. *************** way around them. *** 47747,47766 **** about. If new system header files are installed, nothing automatically ! arranges to update the corrected header files. They can be updated ! using the 'mkheaders' script installed in ! 'LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'. * On 68000 and x86 systems, for instance, you can get paradoxical results if you test the precise values of floating point numbers. For example, you can find that a floating point value which is not a NaN is not equal to itself. This results from the fact that the ! floating point registers hold a few more bits of precision than fit ! in a 'double' in memory. Compiled code moves values between memory ! and floating point registers at its convenience, and moving them ! into memory truncates them. ! You can partially avoid this problem by using the '-ffloat-store' option (*note Optimize Options::). * On AIX and other platforms without weak symbol support, templates --- 48326,48345 ---- about. If new system header files are installed, nothing automatically ! arranges to update the corrected header files. They can be ! updated using the `mkheaders' script installed in ! `LIBEXECDIR/gcc/TARGET/VERSION/install-tools/'. * On 68000 and x86 systems, for instance, you can get paradoxical results if you test the precise values of floating point numbers. For example, you can find that a floating point value which is not a NaN is not equal to itself. This results from the fact that the ! floating point registers hold a few more bits of precision than ! fit in a `double' in memory. Compiled code moves values between ! memory and floating point registers at its convenience, and moving ! them into memory truncates them. ! You can partially avoid this problem by using the `-ffloat-store' option (*note Optimize Options::). * On AIX and other platforms without weak symbol support, templates *************** way around them. *** 47780,47786 ****  File: gcc.info, Node: C++ Misunderstandings, Next: Non-bugs, Prev: Disappointments, Up: Trouble ! 12.7 Common Misunderstandings with GNU C++ ========================================== C++ is a complex language and an evolving one, and its standard --- 48359,48365 ----  File: gcc.info, Node: C++ Misunderstandings, Next: Non-bugs, Prev: Disappointments, Up: Trouble ! 13.7 Common Misunderstandings with GNU C++ ========================================== C++ is a complex language and an evolving one, and its standard *************** give rise to questions of this sort. *** 47799,47805 ****  File: gcc.info, Node: Static Definitions, Next: Name lookup, Up: C++ Misunderstandings ! 12.7.1 Declare _and_ Define Static Members ------------------------------------------ When a class has static data members, it is not enough to _declare_ the --- 48378,48384 ----  File: gcc.info, Node: Static Definitions, Next: Name lookup, Up: C++ Misunderstandings ! 13.7.1 Declare _and_ Define Static Members ------------------------------------------ When a class has static data members, it is not enough to _declare_ the *************** static member; you must also _define_ it *** 47812,47835 **** static int bar; }; ! This declaration only establishes that the class 'Foo' has an 'int' ! named 'Foo::bar', and a member function named 'Foo::method'. But you ! still need to define _both_ 'method' and 'bar' elsewhere. According to the ISO standard, you must supply an initializer in one (and only one) source file, such as: int Foo::bar = 0; Other C++ compilers may not correctly implement the standard behavior. ! As a result, when you switch to 'g++' from one of these compilers, you ! may discover that a program that appeared to work correctly in fact does ! not conform to the standard: 'g++' reports as undefined symbols any ! static data members that lack definitions.  File: gcc.info, Node: Name lookup, Next: Temporaries, Prev: Static Definitions, Up: C++ Misunderstandings ! 12.7.2 Name Lookup, Templates, and Accessing Members of Base Classes -------------------------------------------------------------------- The C++ standard prescribes that all names that are not dependent on --- 48391,48414 ---- static int bar; }; ! This declaration only establishes that the class `Foo' has an `int' ! named `Foo::bar', and a member function named `Foo::method'. But you ! still need to define _both_ `method' and `bar' elsewhere. According to the ISO standard, you must supply an initializer in one (and only one) source file, such as: int Foo::bar = 0; Other C++ compilers may not correctly implement the standard behavior. ! As a result, when you switch to `g++' from one of these compilers, you ! may discover that a program that appeared to work correctly in fact ! does not conform to the standard: `g++' reports as undefined symbols ! any static data members that lack definitions.  File: gcc.info, Node: Name lookup, Next: Temporaries, Prev: Static Definitions, Up: C++ Misunderstandings ! 13.7.2 Name Lookup, Templates, and Accessing Members of Base Classes -------------------------------------------------------------------- The C++ standard prescribes that all names that are not dependent on *************** looked up at the point of instantiation. *** 47852,47871 **** static const int N; }; ! Here, the names 'foo' and 'N' appear in a context that does not depend ! on the type of 'T'. The compiler will thus require that they are ! defined in the context of use in the template, not only before the point ! of instantiation, and will here use '::foo(double)' and 'A::N', respectively. In particular, it will convert the integer value to a ! 'double' when passing it to '::foo(double)'. ! Conversely, 'bar' and the call to 'foo' in the fourth marked line are ! used in contexts that do depend on the type of 'T', so they are only looked up at the point of instantiation, and you can provide declarations for them after declaring the template, but before ! instantiating it. In particular, if you instantiate 'A::f', the ! last line will call an overloaded '::foo(int)' if one was provided, even ! if after the declaration of 'struct A'. This distinction between lookup of dependent and non-dependent names is called two-stage (or dependent) name lookup. G++ implements it since --- 48431,48450 ---- static const int N; }; ! Here, the names `foo' and `N' appear in a context that does not depend ! on the type of `T'. The compiler will thus require that they are ! defined in the context of use in the template, not only before the ! point of instantiation, and will here use `::foo(double)' and `A::N', respectively. In particular, it will convert the integer value to a ! `double' when passing it to `::foo(double)'. ! Conversely, `bar' and the call to `foo' in the fourth marked line are ! used in contexts that do depend on the type of `T', so they are only looked up at the point of instantiation, and you can provide declarations for them after declaring the template, but before ! instantiating it. In particular, if you instantiate `A::f', the ! last line will call an overloaded `::foo(int)' if one was provided, ! even if after the declaration of `struct A'. This distinction between lookup of dependent and non-dependent names is called two-stage (or dependent) name lookup. G++ implements it since *************** different from non-template codes. The *** 47882,47902 **** int get_i() { return i; } }; ! In 'get_i()', 'i' is not used in a dependent context, so the compiler ! will look for a name declared at the enclosing namespace scope (which is ! the global scope here). It will not look into the base class, since ! that is dependent and you may declare specializations of 'Base' even ! after declaring 'Derived', so the compiler can't really know what 'i' ! would refer to. If there is no global variable 'i', then you will get an error message. In order to make it clear that you want the member of the base class, you need to defer lookup until instantiation time, at which the base ! class is known. For this, you need to access 'i' in a dependent ! context, by either using 'this->i' (remember that 'this' is of type ! 'Derived*', so is obviously dependent), or using 'Base::i'. ! Alternatively, 'Base::i' might be brought into scope by a ! 'using'-declaration. Another, similar example involves calling member functions of a base class: --- 48461,48481 ---- int get_i() { return i; } }; ! In `get_i()', `i' is not used in a dependent context, so the compiler ! will look for a name declared at the enclosing namespace scope (which ! is the global scope here). It will not look into the base class, since ! that is dependent and you may declare specializations of `Base' even ! after declaring `Derived', so the compiler can't really know what `i' ! would refer to. If there is no global variable `i', then you will get an error message. In order to make it clear that you want the member of the base class, you need to defer lookup until instantiation time, at which the base ! class is known. For this, you need to access `i' in a dependent ! context, by either using `this->i' (remember that `this' is of type ! `Derived*', so is obviously dependent), or using `Base::i'. ! Alternatively, `Base::i' might be brought into scope by a ! `using'-declaration. Another, similar example involves calling member functions of a base class: *************** class: *** 47909,47916 **** int g() { return f(); }; }; ! Again, the call to 'f()' is not dependent on template arguments (there ! are no arguments that depend on the type 'T', and it is also not otherwise specified that the call should be in a dependent context). Thus a global declaration of such a function must be available, since the one in the base class is not visible until instantiation time. The --- 48488,48495 ---- int g() { return f(); }; }; ! Again, the call to `f()' is not dependent on template arguments (there ! are no arguments that depend on the type `T', and it is also not otherwise specified that the call should be in a dependent context). Thus a global declaration of such a function must be available, since the one in the base class is not visible until instantiation time. The *************** compiler will consequently produce the f *** 47922,47965 **** x.cc:6: error: (if you use `-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated) ! To make the code valid either use 'this->f()', or 'Base::f()'. ! Using the '-fpermissive' flag will also let the compiler accept the code, by marking all function calls for which no declaration is visible at the time of definition of the template for later lookup at ! instantiation time, as if it were a dependent call. We do not recommend ! using '-fpermissive' to work around invalid code, and it will also only ! catch cases where functions in base classes are called, not where ! variables in base classes are used (as in the example above). Note that some compilers (including G++ versions prior to 3.4) get these examples wrong and accept above code without an error. Those compilers do not implement two-stage name lookup correctly. ! ---------- Footnotes ---------- ! (1) The C++ standard just uses the term "dependent" for names that depend on the type or value of template parameters. This shorter term will also be used in the rest of this section.  File: gcc.info, Node: Temporaries, Next: Copy Assignment, Prev: Name lookup, Up: C++ Misunderstandings ! 12.7.3 Temporaries May Vanish Before You Expect ----------------------------------------------- It is dangerous to use pointers or references to _portions_ of a temporary object. The compiler may very well delete the object before you expect it to, leaving a pointer to garbage. The most common place where this problem crops up is in classes like string classes, ! especially ones that define a conversion function to type 'char *' or ! 'const char *'--which is one reason why the standard 'string' class ! requires you to call the 'c_str' member function. However, any class ! that returns a pointer to some internal structure is potentially subject ! to this problem. ! For example, a program may use a function 'strfunc' that returns ! 'string' objects, and another function 'charfunc' that operates on ! pointers to 'char': string strfunc (); void charfunc (const char *); --- 48501,48544 ---- x.cc:6: error: (if you use `-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated) ! To make the code valid either use `this->f()', or `Base::f()'. ! Using the `-fpermissive' flag will also let the compiler accept the code, by marking all function calls for which no declaration is visible at the time of definition of the template for later lookup at ! instantiation time, as if it were a dependent call. We do not ! recommend using `-fpermissive' to work around invalid code, and it will ! also only catch cases where functions in base classes are called, not ! where variables in base classes are used (as in the example above). Note that some compilers (including G++ versions prior to 3.4) get these examples wrong and accept above code without an error. Those compilers do not implement two-stage name lookup correctly. ! ---------- Footnotes ---------- ! (1) The C++ standard just uses the term "dependent" for names that depend on the type or value of template parameters. This shorter term will also be used in the rest of this section.  File: gcc.info, Node: Temporaries, Next: Copy Assignment, Prev: Name lookup, Up: C++ Misunderstandings ! 13.7.3 Temporaries May Vanish Before You Expect ----------------------------------------------- It is dangerous to use pointers or references to _portions_ of a temporary object. The compiler may very well delete the object before you expect it to, leaving a pointer to garbage. The most common place where this problem crops up is in classes like string classes, ! especially ones that define a conversion function to type `char *' or ! `const char *'--which is one reason why the standard `string' class ! requires you to call the `c_str' member function. However, any class ! that returns a pointer to some internal structure is potentially ! subject to this problem. ! For example, a program may use a function `strfunc' that returns ! `string' objects, and another function `charfunc' that operates on ! pointers to `char': string strfunc (); void charfunc (const char *); *************** pointers to 'char': *** 47975,47984 **** } In this situation, it may seem reasonable to save a pointer to the C ! string returned by the 'c_str' member function and use that rather than ! call 'c_str' repeatedly. However, the temporary string created by the ! call to 'strfunc' is destroyed after 'p' is initialized, at which point ! 'p' is left pointing to freed memory. Code like this may run successfully under some other compilers, particularly obsolete cfront-based compilers that delete temporaries --- 48554,48563 ---- } In this situation, it may seem reasonable to save a pointer to the C ! string returned by the `c_str' member function and use that rather than ! call `c_str' repeatedly. However, the temporary string created by the ! call to `strfunc' is destroyed after `p' is initialized, at which point ! `p' is left pointing to freed memory. Code like this may run successfully under some other compilers, particularly obsolete cfront-based compilers that delete temporaries *************** example: *** 47996,48002 ****  File: gcc.info, Node: Copy Assignment, Prev: Temporaries, Up: C++ Misunderstandings ! 12.7.4 Implicit Copy-Assignment for Virtual Bases ------------------------------------------------- When a base class is virtual, only one subobject of the base class --- 48575,48581 ----  File: gcc.info, Node: Copy Assignment, Prev: Temporaries, Up: C++ Misunderstandings ! 13.7.4 Implicit Copy-Assignment for Virtual Bases ------------------------------------------------- When a base class is virtual, only one subobject of the base class *************** such objects behave unspecified when bei *** 48032,48048 **** d1 = d2; } ! The C++ standard specifies that 'Base::Base' is only called once when constructing or copy-constructing a Derived object. It is unspecified ! whether 'Base::operator=' is called more than once when the implicit ! copy-assignment for Derived objects is invoked (as it is inside 'func' in the example). G++ implements the "intuitive" algorithm for copy-assignment: assign all direct bases, then assign all members. In that algorithm, the virtual base subobject can be encountered more than once. In the ! example, copying proceeds in the following order: 'val', 'name' (via ! 'strdup'), 'bval', and 'name' again. If application code relies on copy-assignment, a user-defined copy-assignment operator removes any uncertainties. With such an --- 48611,48627 ---- d1 = d2; } ! The C++ standard specifies that `Base::Base' is only called once when constructing or copy-constructing a Derived object. It is unspecified ! whether `Base::operator=' is called more than once when the implicit ! copy-assignment for Derived objects is invoked (as it is inside `func' in the example). G++ implements the "intuitive" algorithm for copy-assignment: assign all direct bases, then assign all members. In that algorithm, the virtual base subobject can be encountered more than once. In the ! example, copying proceeds in the following order: `val', `name' (via ! `strdup'), `bval', and `name' again. If application code relies on copy-assignment, a user-defined copy-assignment operator removes any uncertainties. With such an *************** subobject is assigned. *** 48052,48058 ****  File: gcc.info, Node: Non-bugs, Next: Warnings and Errors, Prev: C++ Misunderstandings, Up: Trouble ! 12.8 Certain Changes We Don't Want to Make ========================================== This section lists changes that people frequently request, but which we --- 48631,48637 ----  File: gcc.info, Node: Non-bugs, Next: Warnings and Errors, Prev: C++ Misunderstandings, Up: Trouble ! 13.8 Certain Changes We Don't Want to Make ========================================== This section lists changes that people frequently request, but which we *************** do not make because we think GCC is bett *** 48081,48097 **** * Warning when a non-void function value is ignored. C contains many standard functions that return a value that most ! programs choose to ignore. One obvious example is 'printf'. Warning about this practice only leads the defensive programmer to ! clutter programs with dozens of casts to 'void'. Such casts are required so frequently that they become visual noise. Writing those casts becomes so automatic that they no longer convey useful information about the intentions of the programmer. For functions where the return value should never be ignored, use the ! 'warn_unused_result' function attribute (*note Function Attributes::). ! * Making '-fshort-enums' the default. This would cause storage layout to be incompatible with most other C compilers. And it doesn't seem very important, given that you --- 48660,48676 ---- * Warning when a non-void function value is ignored. C contains many standard functions that return a value that most ! programs choose to ignore. One obvious example is `printf'. Warning about this practice only leads the defensive programmer to ! clutter programs with dozens of casts to `void'. Such casts are required so frequently that they become visual noise. Writing those casts becomes so automatic that they no longer convey useful information about the intentions of the programmer. For functions where the return value should never be ignored, use the ! `warn_unused_result' function attribute (*note Function Attributes::). ! * Making `-fshort-enums' the default. This would cause storage layout to be incompatible with most other C compilers. And it doesn't seem very important, given that you *************** do not make because we think GCC is bett *** 48103,48118 **** "the ABI standard" says to do so. The ISO C standard leaves it up to the implementation whether a ! bit-field declared plain 'int' is signed or not. This in effect creates two alternative dialects of C. The GNU C compiler supports both dialects; you can specify the ! signed dialect with '-fsigned-bitfields' and the unsigned dialect ! with '-funsigned-bitfields'. However, this leaves open the question of which dialect to use by default. Currently, the preferred dialect makes plain bit-fields signed, ! because this is simplest. Since 'int' is the same as 'signed int' in every other context, it is cleanest for them to be the same in bit-fields as well. --- 48682,48697 ---- "the ABI standard" says to do so. The ISO C standard leaves it up to the implementation whether a ! bit-field declared plain `int' is signed or not. This in effect creates two alternative dialects of C. The GNU C compiler supports both dialects; you can specify the ! signed dialect with `-fsigned-bitfields' and the unsigned dialect ! with `-funsigned-bitfields'. However, this leaves open the question of which dialect to use by default. Currently, the preferred dialect makes plain bit-fields signed, ! because this is simplest. Since `int' is the same as `signed int' in every other context, it is cleanest for them to be the same in bit-fields as well. *************** do not make because we think GCC is bett *** 48133,48147 **** Many users appreciate the GNU C compiler because it provides an environment that is uniform across machines. These users would be ! inconvenienced if the compiler treated plain bit-fields differently ! on certain machines. Occasionally users write programs intended only for a particular machine type. On these occasions, the users would benefit if the GNU C compiler were to support by default the same dialect as the other compilers on that machine. But such applications are rare. ! And users writing a program to run on more than one type of machine ! cannot possibly benefit from this kind of compatibility. This is why GCC does and will treat plain bit-fields in the same fashion on all types of machines (by default). --- 48712,48726 ---- Many users appreciate the GNU C compiler because it provides an environment that is uniform across machines. These users would be ! inconvenienced if the compiler treated plain bit-fields ! differently on certain machines. Occasionally users write programs intended only for a particular machine type. On these occasions, the users would benefit if the GNU C compiler were to support by default the same dialect as the other compilers on that machine. But such applications are rare. ! And users writing a program to run on more than one type of ! machine cannot possibly benefit from this kind of compatibility. This is why GCC does and will treat plain bit-fields in the same fashion on all types of machines (by default). *************** do not make because we think GCC is bett *** 48156,48215 **** In this way, they write programs which have the same meaning in both C dialects.) ! * Undefining '__STDC__' when '-ansi' is not used. ! Currently, GCC defines '__STDC__' unconditionally. This provides good results in practice. ! Programmers normally use conditionals on '__STDC__' to ask whether it is safe to use certain features of ISO C, such as function ! prototypes or ISO token concatenation. Since plain 'gcc' supports all the features of ISO C, the correct answer to these questions is "yes". ! Some users try to use '__STDC__' to check for the availability of ! certain library facilities. This is actually incorrect usage in an ! ISO C program, because the ISO C standard says that a conforming ! freestanding implementation should define '__STDC__' even though it ! does not have the library facilities. 'gcc -ansi -pedantic' is a conforming freestanding implementation, and it is therefore ! required to define '__STDC__', even though it does not come with an ! ISO C library. ! Sometimes people say that defining '__STDC__' in a compiler that does not completely conform to the ISO C standard somehow violates the standard. This is illogical. The standard is a standard for ! compilers that claim to support ISO C, such as 'gcc -ansi'--not for ! other compilers such as plain 'gcc'. Whatever the ISO C standard ! says is relevant to the design of plain 'gcc' without '-ansi' only ! for pragmatic reasons, not as a requirement. ! GCC normally defines '__STDC__' to be 1, and in addition defines ! '__STRICT_ANSI__' if you specify the '-ansi' option, or a '-std' option for strict conformance to some version of ISO C. On some hosts, system include files use a different convention, where ! '__STDC__' is normally 0, but is 1 if the user specifies strict conformance to the C Standard. GCC follows the host convention when processing system include files, but when processing user files it follows the usual GNU C convention. ! * Undefining '__STDC__' in C++. ! Programs written to compile with C++-to-C translators get the value ! of '__STDC__' that goes with the C compiler that is subsequently ! used. These programs must test '__STDC__' to determine what kind ! of C preprocessor that compiler uses: whether they should ! concatenate tokens in the ISO C fashion or in the traditional ! fashion. ! These programs work properly with GNU C++ if '__STDC__' is defined. They would not work otherwise. ! In addition, many header files are written to provide prototypes in ! ISO C but not in traditional C. Many of these header files can ! work without change in C++ provided '__STDC__' is defined. If ! '__STDC__' is not defined, they will all fail, and will all need to ! be changed to test explicitly for C++ as well. * Deleting "empty" loops. --- 48735,48794 ---- In this way, they write programs which have the same meaning in both C dialects.) ! * Undefining `__STDC__' when `-ansi' is not used. ! Currently, GCC defines `__STDC__' unconditionally. This provides good results in practice. ! Programmers normally use conditionals on `__STDC__' to ask whether it is safe to use certain features of ISO C, such as function ! prototypes or ISO token concatenation. Since plain `gcc' supports all the features of ISO C, the correct answer to these questions is "yes". ! Some users try to use `__STDC__' to check for the availability of ! certain library facilities. This is actually incorrect usage in ! an ISO C program, because the ISO C standard says that a conforming ! freestanding implementation should define `__STDC__' even though it ! does not have the library facilities. `gcc -ansi -pedantic' is a conforming freestanding implementation, and it is therefore ! required to define `__STDC__', even though it does not come with ! an ISO C library. ! Sometimes people say that defining `__STDC__' in a compiler that does not completely conform to the ISO C standard somehow violates the standard. This is illogical. The standard is a standard for ! compilers that claim to support ISO C, such as `gcc -ansi'--not ! for other compilers such as plain `gcc'. Whatever the ISO C ! standard says is relevant to the design of plain `gcc' without ! `-ansi' only for pragmatic reasons, not as a requirement. ! GCC normally defines `__STDC__' to be 1, and in addition defines ! `__STRICT_ANSI__' if you specify the `-ansi' option, or a `-std' option for strict conformance to some version of ISO C. On some hosts, system include files use a different convention, where ! `__STDC__' is normally 0, but is 1 if the user specifies strict conformance to the C Standard. GCC follows the host convention when processing system include files, but when processing user files it follows the usual GNU C convention. ! * Undefining `__STDC__' in C++. ! Programs written to compile with C++-to-C translators get the ! value of `__STDC__' that goes with the C compiler that is ! subsequently used. These programs must test `__STDC__' to ! determine what kind of C preprocessor that compiler uses: whether ! they should concatenate tokens in the ISO C fashion or in the ! traditional fashion. ! These programs work properly with GNU C++ if `__STDC__' is defined. They would not work otherwise. ! In addition, many header files are written to provide prototypes ! in ISO C but not in traditional C. Many of these header files can ! work without change in C++ provided `__STDC__' is defined. If ! `__STDC__' is not defined, they will all fail, and will all need ! to be changed to test explicitly for C++ as well. * Deleting "empty" loops. *************** do not make because we think GCC is bett *** 48219,48225 **** programs run any faster. However, the rationale here is that optimization of a nonempty loop ! cannot produce an empty one. This held for carefully written C compiled with less powerful optimizers but is not always the case for carefully written C++ or with more powerful optimizers. Thus GCC will remove operations from loops whenever it can determine --- 48798,48804 ---- programs run any faster. However, the rationale here is that optimization of a nonempty loop ! cannot produce an empty one. This held for carefully written C compiled with less powerful optimizers but is not always the case for carefully written C++ or with more powerful optimizers. Thus GCC will remove operations from loops whenever it can determine *************** do not make because we think GCC is bett *** 48229,48235 **** Be aware of this when performing timing tests, for instance the following loop can be completely removed, provided ! 'some_expression' can provably not change any global state. { int sum = 0; --- 48808,48814 ---- Be aware of this when performing timing tests, for instance the following loop can be completely removed, provided ! `some_expression' can provably not change any global state. { int sum = 0; *************** do not make because we think GCC is bett *** 48239,48245 **** sum += some_expression; } ! Even though 'sum' is accumulated in the loop, no use is made of that summation, so the accumulation can be removed. * Making side effects happen in the same order as in some other --- 48818,48824 ---- sum += some_expression; } ! Even though `sum' is accumulated in the loop, no use is made of that summation, so the accumulation can be removed. * Making side effects happen in the same order as in some other *************** do not make because we think GCC is bett *** 48256,48264 **** There is no guarantee (in either the C or the C++ standard language definitions) that the increments will be evaluated in any ! particular order. Either increment might happen first. 'func' ! might get the arguments '2, 3', or it might get '3, 2', or even '2, ! 2'. * Making certain warnings into errors by default. --- 48835,48843 ---- There is no guarantee (in either the C or the C++ standard language definitions) that the increments will be evaluated in any ! particular order. Either increment might happen first. `func' ! might get the arguments `2, 3', or it might get `3, 2', or even ! `2, 2'. * Making certain warnings into errors by default. *************** do not make because we think GCC is bett *** 48266,48281 **** produce an error message for a certain program. ISO C requires a "diagnostic" message for certain kinds of invalid ! programs, but a warning is defined by GCC to count as a diagnostic. ! If GCC produces a warning but not an error, that is correct ISO C ! support. If testsuites call this "failure", they should be run ! with the GCC option '-pedantic-errors', which will turn these ! warnings into errors.  File: gcc.info, Node: Warnings and Errors, Prev: Non-bugs, Up: Trouble ! 12.9 Warning Messages and Error Messages ======================================== The GNU compiler can produce two kinds of diagnostics: errors and --- 48845,48861 ---- produce an error message for a certain program. ISO C requires a "diagnostic" message for certain kinds of invalid ! programs, but a warning is defined by GCC to count as a ! diagnostic. If GCC produces a warning but not an error, that is ! correct ISO C support. If testsuites call this "failure", they ! should be run with the GCC option `-pedantic-errors', which will ! turn these warnings into errors. !  File: gcc.info, Node: Warnings and Errors, Prev: Non-bugs, Up: Trouble ! 13.9 Warning Messages and Error Messages ======================================== The GNU compiler can produce two kinds of diagnostics: errors and *************** warnings. Each kind has a different pur *** 48288,48310 **** "Warnings" report other unusual conditions in your code that _may_ indicate a problem, although compilation can (and does) proceed. Warning messages also report the source file name and line number, ! but include the text 'warning:' to distinguish them from error messages. Warnings may indicate danger points where you should check to make sure that your program really does what you intend; or the use of obsolete features; or the use of nonstandard features of GNU C or C++. Many ! warnings are issued only if you ask for them, with one of the '-W' ! options (for instance, '-Wall' requests a variety of useful warnings). GCC always tries to compile your program if possible; it never gratuitously rejects a program whose meaning is clear merely because (for instance) it fails to conform to a standard. In some cases, however, the C and C++ standards specify that certain extensions are forbidden, and a diagnostic _must_ be issued by a conforming compiler. ! The '-pedantic' option tells GCC to issue warnings in such cases; ! '-pedantic-errors' says to make them errors instead. This does not mean ! that _all_ non-ISO constructs get warnings or errors. *Note Options to Request or Suppress Warnings: Warning Options, for more detail on these and related command-line options. --- 48868,48890 ---- "Warnings" report other unusual conditions in your code that _may_ indicate a problem, although compilation can (and does) proceed. Warning messages also report the source file name and line number, ! but include the text `warning:' to distinguish them from error messages. Warnings may indicate danger points where you should check to make sure that your program really does what you intend; or the use of obsolete features; or the use of nonstandard features of GNU C or C++. Many ! warnings are issued only if you ask for them, with one of the `-W' ! options (for instance, `-Wall' requests a variety of useful warnings). GCC always tries to compile your program if possible; it never gratuitously rejects a program whose meaning is clear merely because (for instance) it fails to conform to a standard. In some cases, however, the C and C++ standards specify that certain extensions are forbidden, and a diagnostic _must_ be issued by a conforming compiler. ! The `-pedantic' option tells GCC to issue warnings in such cases; ! `-pedantic-errors' says to make them errors instead. This does not ! mean that _all_ non-ISO constructs get warnings or errors. *Note Options to Request or Suppress Warnings: Warning Options, for more detail on these and related command-line options. *************** more detail on these and related command *** 48312,48318 ****  File: gcc.info, Node: Bugs, Next: Service, Prev: Trouble, Up: Top ! 13 Reporting Bugs ***************** Your bug reports play an essential role in making GCC reliable. --- 48892,48898 ----  File: gcc.info, Node: Bugs, Next: Service, Prev: Trouble, Up: Top ! 14 Reporting Bugs ***************** Your bug reports play an essential role in making GCC reliable. *************** report the problem. *** 48329,48335 ****  File: gcc.info, Node: Bug Criteria, Next: Bug Reporting, Up: Bugs ! 13.1 Have You Found a Bug? ========================== If you are not sure whether you have found a bug, here are some --- 48909,48915 ----  File: gcc.info, Node: Bug Criteria, Next: Bug Reporting, Up: Bugs ! 14.1 Have You Found a Bug? ========================== If you are not sure whether you have found a bug, here are some *************** guidelines: *** 48339,48345 **** is a compiler bug. Reliable compilers never crash. * If the compiler produces invalid assembly code, for any input ! whatever (except an 'asm' statement), that is a compiler bug, unless the compiler reports errors (not just warnings) which would ordinarily prevent the assembler from being run. --- 48919,48925 ---- is a compiler bug. Reliable compilers never crash. * If the compiler produces invalid assembly code, for any input ! whatever (except an `asm' statement), that is a compiler bug, unless the compiler reports errors (not just warnings) which would ordinarily prevent the assembler from being run. *************** guidelines: *** 48350,48362 **** program whose behavior is undefined, which happened by chance to give the desired results with another C or C++ compiler. ! For example, in many nonoptimizing compilers, you can write 'x;' at ! the end of a function instead of 'return x;', with the same ! results. But the value of the function is undefined if 'return' is ! omitted; it is not a bug when GCC produces different results. Problems often result from expressions with two increment ! operators, as in 'f (*p++, *p++)'. Your previous compiler might have interpreted that expression the way you intended; GCC might interpret it another way. Neither compiler is wrong. The bug is in your code. --- 48930,48942 ---- program whose behavior is undefined, which happened by chance to give the desired results with another C or C++ compiler. ! For example, in many nonoptimizing compilers, you can write `x;' ! at the end of a function instead of `return x;', with the same ! results. But the value of the function is undefined if `return' ! is omitted; it is not a bug when GCC produces different results. Problems often result from expressions with two increment ! operators, as in `f (*p++, *p++)'. Your previous compiler might have interpreted that expression the way you intended; GCC might interpret it another way. Neither compiler is wrong. The bug is in your code. *************** guidelines: *** 48380,48395 ****  File: gcc.info, Node: Bug Reporting, Prev: Bug Criteria, Up: Bugs ! 13.2 How and Where to Report Bugs ================================= Bugs should be reported to the bug database at ! .  File: gcc.info, Node: Service, Next: Contributing, Prev: Bugs, Up: Top ! 14 How To Get Help with GCC *************************** If you need help installing, using or changing GCC, there are two ways --- 48960,48975 ----  File: gcc.info, Node: Bug Reporting, Prev: Bug Criteria, Up: Bugs ! 14.2 How and Where to Report Bugs ================================= Bugs should be reported to the bug database at ! `http://gcc.gnu.org/bugs.html'.  File: gcc.info, Node: Service, Next: Contributing, Prev: Bugs, Up: Top ! 15 How To Get Help with GCC *************************** If you need help installing, using or changing GCC, there are two ways *************** to find it: *** 48404,48433 **** * Look in the service directory for someone who might help you for a fee. The service directory is found at ! . ! For further information, see .  File: gcc.info, Node: Contributing, Next: Funding, Prev: Service, Up: Top ! 15 Contributing to GCC Development ********************************** If you would like to help pretest GCC releases to assure they work well, current development sources are available by SVN (see ! ). Source and binary snapshots are also ! available for FTP; see . If you would like to work on improvements to GCC, please read the advice at these URLs: ! ! for information on how to make useful contributions and avoid duplication of effort. Suggested projects are listed at ! .  File: gcc.info, Node: Funding, Next: GNU Project, Prev: Contributing, Up: Top --- 48984,49013 ---- * Look in the service directory for someone who might help you for a fee. The service directory is found at ! `http://www.fsf.org/resources/service'. ! For further information, see `http://gcc.gnu.org/faq.html#support'.  File: gcc.info, Node: Contributing, Next: Funding, Prev: Service, Up: Top ! 16 Contributing to GCC Development ********************************** If you would like to help pretest GCC releases to assure they work well, current development sources are available by SVN (see ! `http://gcc.gnu.org/svn.html'). Source and binary snapshots are also ! available for FTP; see `http://gcc.gnu.org/snapshots.html'. If you would like to work on improvements to GCC, please read the advice at these URLs: ! `http://gcc.gnu.org/contribute.html' ! `http://gcc.gnu.org/contributewhy.html' for information on how to make useful contributions and avoid duplication of effort. Suggested projects are listed at ! `http://gcc.gnu.org/projects/'.  File: gcc.info, Node: Funding, Next: GNU Project, Prev: Contributing, Up: Top *************** to free software developers--the Free So *** 48446,48453 **** The way to convince distributors to do this is to demand it and expect it from them. So when you compare distributors, judge them partly by ! how much they give to free software development. Show distributors they ! must compete to be the one who gives the most. To make this approach work, you must insist on numbers that you can compare, such as, "We will donate ten dollars to the Frobnitz project --- 49026,49033 ---- The way to convince distributors to do this is to demand it and expect it from them. So when you compare distributors, judge them partly by ! how much they give to free software development. Show distributors ! they must compete to be the one who gives the most. To make this approach work, you must insist on numbers that you can compare, such as, "We will donate ten dollars to the Frobnitz project *************** for comparison. *** 48457,48464 **** Even a precise fraction "of the profits from this disk" is not very meaningful, since creative accounting and unrelated business decisions ! can greatly alter what fraction of the sales price counts as profit. If ! the price you pay is $50, ten percent of the profit is probably less than a dollar; it might be a few cents, or nothing at all. Some redistributors do development work themselves. This is useful --- 49037,49044 ---- Even a precise fraction "of the profits from this disk" is not very meaningful, since creative accounting and unrelated business decisions ! can greatly alter what fraction of the sales price counts as profit. ! If the price you pay is $50, ten percent of the profit is probably less than a dollar; it might be a few cents, or nothing at all. Some redistributors do development work themselves. This is useful *************** difference than others. For example, ma *** 48468,48475 **** a program contributes very little; maintaining the standard version of a program for the whole community contributes much. Easy new ports contribute little, since someone else would surely do them; difficult ! ports such as adding a new CPU to the GNU Compiler Collection contribute ! more; major new features or packages contribute the most. By establishing the idea that supporting further development is "the proper thing to do" when distributing free software for a fee, we can --- 49048,49055 ---- a program contributes very little; maintaining the standard version of a program for the whole community contributes much. Easy new ports contribute little, since someone else would surely do them; difficult ! ports such as adding a new CPU to the GNU Compiler Collection ! contribute more; major new features or packages contribute the most. By establishing the idea that supporting further development is "the proper thing to do" when distributing free software for a fee, we can *************** now widely used; though these systems ar *** 48493,48500 **** they are more accurately called GNU/Linux systems. For more information, see: ! !  File: gcc.info, Node: Copying, Next: GNU Free Documentation License, Prev: GNU Project, Up: Top --- 49073,49080 ---- they are more accurately called GNU/Linux systems. For more information, see: ! `http://www.gnu.org/' ! `http://www.gnu.org/gnu/linux-and-gnu.html'  File: gcc.info, Node: Copying, Next: GNU Free Documentation License, Prev: GNU Project, Up: Top *************** GNU General Public License *** 48504,48510 **** Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 49084,49090 ---- Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU General Public License for most of o *** 48524,48550 **** any other work released this way by its authors. You can apply it to your programs, too. ! When we speak of free software, we are referring to freedom, not price. ! Our General Public Licenses are designed to make sure that you have the ! freedom to distribute copies of free software (and charge for them if ! you wish), that you receive source code or can get it if you want it, ! that you can change the software or use pieces of it in new free ! programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you have ! certain responsibilities if you distribute copies of the software, or if ! you modify it: responsibilities to respect the freedom of others. ! For example, if you distribute copies of such a program, whether gratis ! or for a fee, you must pass on to the recipients the same freedoms that ! you received. You must make sure that they, too, receive or can get the ! source code. And you must show them these terms so they know their ! rights. ! Developers that use the GNU GPL protect your rights with two steps: (1) ! assert copyright on the software, and (2) offer you this License giving ! you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and --- 49104,49130 ---- any other work released this way by its authors. You can apply it to your programs, too. ! When we speak of free software, we are referring to freedom, not ! price. Our General Public Licenses are designed to make sure that you ! have the freedom to distribute copies of free software (and charge for ! them if you wish), that you receive source code or can get it if you ! want it, that you can change the software or use pieces of it in new ! free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you ! have certain responsibilities if you distribute copies of the software, ! or if you modify it: responsibilities to respect the freedom of others. ! For example, if you distribute copies of such a program, whether ! gratis or for a fee, you must pass on to the recipients the same ! freedoms that you received. You must make sure that they, too, receive ! or can get the source code. And you must show them these terms so they ! know their rights. ! Developers that use the GNU GPL protect your rights with two steps: ! (1) assert copyright on the software, and (2) offer you this License ! giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and *************** changed, so that their problems will not *** 48553,48567 **** authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the manufacturer ! can do so. This is fundamentally incompatible with the aim of ! protecting users' freedom to change the software. The systematic ! pattern of such abuse occurs in the area of products for individuals to ! use, which is precisely where it is most unacceptable. Therefore, we ! have designed this version of the GPL to prohibit the practice for those ! products. If such problems arise substantially in other domains, we ! stand ready to extend this provision to those domains in future versions ! of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of --- 49133,49148 ---- authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the ! manufacturer can do so. This is fundamentally incompatible with the ! aim of protecting users' freedom to change the software. The ! systematic pattern of such abuse occurs in the area of products for ! individuals to use, which is precisely where it is most unacceptable. ! Therefore, we have designed this version of the GPL to prohibit the ! practice for those products. If such problems arise substantially in ! other domains, we stand ready to extend this provision to those domains ! in future versions of the GPL, as needed to protect the freedom of ! users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of *************** TERMS AND CONDITIONS *** 48598,48605 **** To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it on ! a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. --- 49179,49186 ---- To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it ! on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. *************** TERMS AND CONDITIONS *** 48613,48620 **** to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may convey ! the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. --- 49194,49201 ---- to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may ! convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. *************** TERMS AND CONDITIONS *** 48622,48629 **** 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any non-source ! form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in --- 49203,49210 ---- 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any ! non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in *************** TERMS AND CONDITIONS *** 48634,48643 **** The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work with ! that Major Component, or to implement a Standard Interface for ! which an implementation is available to the public in source code ! form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code --- 49215,49224 ---- The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work ! with that Major Component, or to implement a Standard Interface ! for which an implementation is available to the public in source ! code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code *************** TERMS AND CONDITIONS *** 48645,48659 **** The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including scripts ! to control those activities. However, it does not include the ! work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files associated ! with source files for the work, and the source code for shared ! libraries and dynamically linked subprograms that the work is ! specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. --- 49226,49240 ---- The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including ! scripts to control those activities. However, it does not include ! the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files ! associated with source files for the work, and the source code for ! shared libraries and dynamically linked subprograms that the work ! is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. *************** TERMS AND CONDITIONS *** 48670,48691 **** copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, given ! its content, constitutes a covered work. This License acknowledges ! your rights of fair use or other equivalent, as provided by ! copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for you, ! or provide you with facilities for running those works, provided ! that you comply with the terms of this License in conveying all ! material for which you do not control copyright. Those thus making ! or running the covered works for you must do so exclusively on your ! behalf, under your direction and control, on terms that prohibit ! them from making any copies of your copyrighted material outside ! their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section --- 49251,49272 ---- copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, ! given its content, constitutes a covered work. This License ! acknowledges your rights of fair use or other equivalent, as ! provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for ! you, or provide you with facilities for running those works, ! provided that you comply with the terms of this License in ! conveying all material for which you do not control copyright. ! Those thus making or running the covered works for you must do so ! exclusively on your behalf, under your direction and control, on ! terms that prohibit them from making any copies of your ! copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section *************** TERMS AND CONDITIONS *** 48702,48709 **** When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention to ! limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. --- 49283,49290 ---- When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention ! to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. *************** TERMS AND CONDITIONS *** 48773,48780 **** b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for as ! long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a --- 49354,49361 ---- b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for ! as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a *************** TERMS AND CONDITIONS *** 48784,48814 **** to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of the ! written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access to ! the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated by ! you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to the ! object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long as ! needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. --- 49365,49396 ---- to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of ! the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access ! to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated ! by you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to ! the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long ! as needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. + A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. *************** TERMS AND CONDITIONS *** 48816,48823 **** A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product is ! a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the --- 49398,49405 ---- A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product ! is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the *************** TERMS AND CONDITIONS *** 48848,48858 **** The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or installed ! by the recipient, or for the User Product in which it has been ! modified or installed. Access to a network may be denied when the ! modification itself materially and adversely affects the operation ! of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information --- 49430,49440 ---- The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or ! installed by the recipient, or for the User Product in which it ! has been modified or installed. Access to a network may be denied ! when the modification itself materially and adversely affects the ! operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information *************** TERMS AND CONDITIONS *** 48882,48889 **** Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License with ! terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or --- 49464,49471 ---- Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License ! with terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or *************** TERMS AND CONDITIONS *** 48893,48900 **** Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be marked ! in reasonable ways as different from the original version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or --- 49475,49483 ---- Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be ! marked in reasonable ways as different from the original ! version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or *************** TERMS AND CONDITIONS *** 48913,48922 **** you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or conveying ! under this License, you may add to a covered work material governed ! by the terms of that license document, provided that the further ! restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the --- 49496,49506 ---- you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or ! conveying under this License, you may add to a covered work ! material governed by the terms of that license document, provided ! that the further restriction does not survive such relicensing or ! conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the *************** TERMS AND CONDITIONS *** 48932,48944 **** You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under the ! third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 49516,49528 ---- You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under ! the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** TERMS AND CONDITIONS *** 48950,48959 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, you do not qualify to receive new licenses ! for the same material under section 10. 9. Acceptance Not Required for Having Copies. --- 49534,49543 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, you do not qualify to receive new ! licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. *************** TERMS AND CONDITIONS *** 48967,48973 **** by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and --- 49551,49557 ---- by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and *************** TERMS AND CONDITIONS *** 48981,49001 **** covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to possession ! of the Corresponding Source of the work from the predecessor in ! interest, if the predecessor has it or can get it with reasonable ! efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for exercise ! of rights granted under this License, and you may not initiate ! litigation (including a cross-claim or counterclaim in a lawsuit) ! alleging that any patent claim is infringed by making, using, ! selling, offering for sale, or importing the Program or any portion ! of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. --- 49565,49585 ---- covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to ! possession of the Corresponding Source of the work from the ! predecessor in interest, if the predecessor has it or can get it ! with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for ! exercise of rights granted under this License, and you may not ! initiate litigation (including a cross-claim or counterclaim in a ! lawsuit) alleging that any patent claim is infringed by making, ! using, selling, offering for sale, or importing the Program or any ! portion of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. *************** TERMS AND CONDITIONS *** 49015,49029 **** Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its contributor ! version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To "grant" ! such a patent license to a party means to make such an agreement or ! commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available --- 49599,49613 ---- Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its ! contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To ! "grant" such a patent license to a party means to make such an ! agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available *************** TERMS AND CONDITIONS *** 49053,49087 **** conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under which ! you make payment to the third party based on the extent of your ! activity of conveying the work, and under which the third party ! grants, to any of the parties who would receive the covered work ! from you, a discriminatory patent license (a) in connection with ! copies of the covered work conveyed by you (or copies made from ! those copies), or (b) primarily for and in connection with specific ! products or compilations that contain the covered work, unless you ! entered into that arrangement, or that patent license was granted, ! prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, agreement ! or otherwise) that contradict the conditions of this License, they ! do not excuse you from the conditions of this License. If you ! cannot convey a covered work so as to satisfy simultaneously your ! obligations under this License and any other pertinent obligations, ! then as a consequence you may not convey it at all. For example, ! if you agree to terms that obligate you to collect a royalty for ! further conveying from those to whom you convey the Program, the ! only way you could satisfy both those terms and this License would ! be to refrain entirely from conveying the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed --- 49637,49672 ---- conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under ! which you make payment to the third party based on the extent of ! your activity of conveying the work, and under which the third ! party grants, to any of the parties who would receive the covered ! work from you, a discriminatory patent license (a) in connection ! with copies of the covered work conveyed by you (or copies made ! from those copies), or (b) primarily for and in connection with ! specific products or compilations that contain the covered work, ! unless you entered into that arrangement, or that patent license ! was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, ! agreement or otherwise) that contradict the conditions of this ! License, they do not excuse you from the conditions of this ! License. If you cannot convey a covered work so as to satisfy ! simultaneously your obligations under this License and any other ! pertinent obligations, then as a consequence you may not convey it ! at all. For example, if you agree to terms that obligate you to ! collect a royalty for further conveying from those to whom you ! convey the Program, the only way you could satisfy both those ! terms and this License would be to refrain entirely from conveying ! the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed *************** TERMS AND CONDITIONS *** 49092,49112 **** General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. Such ! new versions will be similar in spirit to the present version, but ! may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the Free ! Software Foundation. If the Program does not specify a version ! number of the GNU General Public License, you may choose any ! version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that --- 49677,49698 ---- General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. ! Such new versions will be similar in spirit to the present ! version, but may differ in detail to address new problems or ! concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the ! Free Software Foundation. If the Program does not specify a ! version number of the GNU General Public License, you may choose ! any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that *************** TERMS AND CONDITIONS *** 49118,49141 **** author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR ! DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD --- 49704,49727 ---- author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU ! FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD *************** TERMS AND CONDITIONS *** 49143,49149 **** PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, --- 49729,49735 ---- PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, *************** TERMS AND CONDITIONS *** 49152,49157 **** --- 49738,49744 ---- connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. + END OF TERMS AND CONDITIONS =========================== *************** possible use to the public, the best way *** 49163,49171 **** free software which everyone can redistribute and change under these terms. ! To do so, attach the following notices to the program. It is safest to ! attach them to the start of each source file to most effectively state ! the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES. --- 49750,49758 ---- free software which everyone can redistribute and change under these terms. ! To do so, attach the following notices to the program. It is safest ! to attach them to the start of each source file to most effectively ! state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES. *************** the exclusion of warranty; and each file *** 49182,49201 **** General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. ! If the program does terminal interaction, make it output a short notice ! like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type 'show c' for details. ! The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". --- 49769,49788 ---- General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see `http://www.gnu.org/licenses/'. Also add information on how to contact you by electronic and paper mail. ! If the program does terminal interaction, make it output a short ! notice like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type `show c' for details. ! The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". *************** use an "about box". *** 49203,49216 **** You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read .  File: gcc.info, Node: GNU Free Documentation License, Next: Contributors, Prev: Copying, Up: Top --- 49790,49803 ---- You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see `http://www.gnu.org/licenses/'. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.  File: gcc.info, Node: GNU Free Documentation License, Next: Contributors, Prev: Copying, Up: Top *************** GNU Free Documentation License *** 49221,49227 **** Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 49808,49814 ---- Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU Free Documentation License *** 49246,49266 **** free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. We ! recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it can ! be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You accept ! the license if you copy, modify or distribute the work in a way ! requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with --- 49833,49853 ---- free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. ! We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it ! can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You ! accept the license if you copy, modify or distribute the work in a ! way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with *************** GNU Free Documentation License *** 49278,49289 **** regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in the ! notice that says that the Document is released under this License. ! If a section does not fit the above definition of Secondary then it ! is not allowed to be designated as Invariant. The Document may ! contain zero Invariant Sections. If the Document does not identify ! any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice --- 49865,49876 ---- regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in ! the notice that says that the Document is released under this ! License. If a section does not fit the above definition of ! Secondary then it is not allowed to be designated as Invariant. ! The Document may contain zero Invariant Sections. If the Document ! does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice *************** GNU Free Documentation License *** 49294,49320 **** A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images composed ! of pixels) generic paint programs or (for drawings) some widely ! available drawing editor, and that is suitable for input to text ! formatters or for automatic translation to a variety of formats ! suitable for input to text formatters. A copy made in an otherwise ! Transparent file format whose markup, or absence of markup, has ! been arranged to thwart or discourage subsequent modification by ! readers is not Transparent. An image format is not Transparent if ! used for any substantial amount of text. A copy that is not ! "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and standard-conforming ! simple HTML, PostScript or PDF designed for human modification. ! Examples of transparent image formats include PNG, XCF and JPG. ! Opaque formats include proprietary formats that can be read and ! edited only by proprietary word processors, SGML or XML for which ! the DTD and/or processing tools are not generally available, and ! the machine-generated HTML, PostScript or PDF produced by some word ! processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the --- 49881,49907 ---- A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images ! composed of pixels) generic paint programs or (for drawings) some ! widely available drawing editor, and that is suitable for input to ! text formatters or for automatic translation to a variety of ! formats suitable for input to text formatters. A copy made in an ! otherwise Transparent file format whose markup, or absence of ! markup, has been arranged to thwart or discourage subsequent ! modification by readers is not Transparent. An image format is ! not Transparent if used for any substantial amount of text. A ! copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and ! standard-conforming simple HTML, PostScript or PDF designed for ! human modification. Examples of transparent image formats include ! PNG, XCF and JPG. Opaque formats include proprietary formats that ! can be read and edited only by proprietary word processors, SGML or ! XML for which the DTD and/or processing tools are not generally ! available, and the machine-generated HTML, PostScript or PDF ! produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the *************** GNU Free Documentation License *** 49352,49359 **** may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow the ! conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. --- 49939,49946 ---- may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow ! the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. *************** GNU Free Documentation License *** 49367,49377 **** these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the title ! equally prominent and visible. You may add other material on the ! covers in addition. Copying with changes limited to the covers, as ! long as they preserve the title of the Document and satisfy these ! conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit --- 49954,49965 ---- these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the ! title equally prominent and visible. You may add other material ! on the covers in addition. Copying with changes limited to the ! covers, as long as they preserve the title of the Document and ! satisfy these conditions, can be treated as verbatim copying in ! other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit *************** GNU Free Documentation License *** 49379,49417 **** adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a machine-readable ! Transparent copy along with each Opaque copy, or state in or with ! each Opaque copy a computer-network location from which the general ! network-using public has access to download using public-standard ! network protocols a complete Transparent copy of the Document, free ! of added material. If you use the latter option, you must take ! reasonably prudent steps, when you begin distribution of Opaque ! copies in quantity, to ensure that this Transparent copy will ! remain thus accessible at the stated location until at least one ! year after the last time you distribute an Opaque copy (directly or ! through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of copies, ! to give them a chance to provide you with an updated version of the ! Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with the ! Modified Version filling the role of the Document, thus licensing ! distribution and modification of the Modified Version to whoever ! possesses a copy of it. In addition, you must do these things in ! the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of previous ! versions (which should, if there were any, be listed in the ! History section of the Document). You may use the same title ! as a previous version if the original publisher of that ! version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in --- 49967,50006 ---- adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a ! machine-readable Transparent copy along with each Opaque copy, or ! state in or with each Opaque copy a computer-network location from ! which the general network-using public has access to download ! using public-standard network protocols a complete Transparent ! copy of the Document, free of added material. If you use the ! latter option, you must take reasonably prudent steps, when you ! begin distribution of Opaque copies in quantity, to ensure that ! this Transparent copy will remain thus accessible at the stated ! location until at least one year after the last time you ! distribute an Opaque copy (directly or through your agents or ! retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of ! copies, to give them a chance to provide you with an updated ! version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with ! the Modified Version filling the role of the Document, thus ! licensing distribution and modification of the Modified Version to ! whoever possesses a copy of it. In addition, you must do these ! things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of ! previous versions (which should, if there were any, be listed ! in the History section of the Document). You may use the ! same title as a previous version if the original publisher of ! that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in *************** GNU Free Documentation License *** 49441,49470 **** I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on the ! Title Page. If there is no section Entitled "History" in the ! Document, create one stating the title, year, authors, and ! publisher of the Document as given on its Title Page, then add ! an item describing the Modified Version as stated in the ! previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in the ! "History" section. You may omit a network location for a work ! that was published at least four years before the Document ! itself, or if the original publisher of the version it refers ! to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the section ! all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, unaltered ! in their text and in their titles. Section numbers or the ! equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. --- 50030,50060 ---- I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on ! the Title Page. If there is no section Entitled "History" in ! the Document, create one stating the title, year, authors, ! and publisher of the Document as given on its Title Page, ! then add an item describing the Modified Version as stated in ! the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in ! the "History" section. You may omit a network location for a ! work that was published at least four years before the ! Document itself, or if the original publisher of the version ! it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the ! section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, ! unaltered in their text and in their titles. Section numbers ! or the equivalent are not considered part of the section ! titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. *************** GNU Free Documentation License *** 49477,49487 **** If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option designate ! some or all of these sections as invariant. To do this, add their ! titles to the list of Invariant Sections in the Modified Version's ! license notice. These titles must be distinct from any other ! section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various --- 50067,50077 ---- If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option ! designate some or all of these sections as invariant. To do this, ! add their titles to the list of Invariant Sections in the Modified ! Version's license notice. These titles must be distinct from any ! other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various *************** GNU Free Documentation License *** 49490,49504 **** definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end of ! the list of Cover Texts in the Modified Version. Only one passage ! of Front-Cover Text and one of Back-Cover Text may be added by (or ! through arrangements made by) any one entity. If the Document ! already includes a cover text for the same cover, previously added ! by you or by arrangement made by the same entity you are acting on ! behalf of, you may not add another; but you may replace the old ! one, on explicit permission from the previous publisher that added ! the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to --- 50080,50094 ---- definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end ! of the list of Cover Texts in the Modified Version. Only one ! passage of Front-Cover Text and one of Back-Cover Text may be ! added by (or through arrangements made by) any one entity. If the ! Document already includes a cover text for the same cover, ! previously added by you or by arrangement made by the same entity ! you are acting on behalf of, you may not add another; but you may ! replace the old one, on explicit permission from the previous ! publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to *************** GNU Free Documentation License *** 49508,49515 **** You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination all ! of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. --- 50098,50105 ---- You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination ! all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. *************** GNU Free Documentation License *** 49536,49555 **** documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the documents ! in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow this ! License in all other respects regarding verbatim copying of that ! document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of a ! storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this --- 50126,50145 ---- documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the ! documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow ! this License in all other respects regarding verbatim copying of ! that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of ! a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this *************** GNU Free Documentation License *** 49594,49601 **** However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 50184,50191 ---- However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** GNU Free Documentation License *** 49607,49639 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, receipt of a copy of some or all of the ! same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! . Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If the ! Document does not specify a version number of this License, you may ! choose any version ever published (not as a draft) by the Free ! Software Foundation. If the Document specifies that a proxy can ! decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also --- 50197,50229 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, receipt of a copy of some or all of ! the same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! `http://www.gnu.org/copyleft/'. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If ! the Document does not specify a version number of this License, ! you may choose any version ever published (not as a draft) by the ! Free Software Foundation. If the Document specifies that a proxy ! can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also *************** GNU Free Documentation License *** 49663,49668 **** --- 50253,50259 ---- site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. + ADDENDUM: How to use this License for your documents ==================================================== *************** notices just after the title page: *** 49679,49685 **** Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, ! replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts --- 50270,50276 ---- Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, ! replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts *************** combination of the three, merge those tw *** 49690,49698 **** situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of free ! software license, such as the GNU General Public License, to permit ! their use in free software.  File: gcc.info, Node: Contributors, Next: Option Index, Prev: GNU Free Documentation License, Up: Top --- 50281,50289 ---- situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of ! free software license, such as the GNU General Public License, to ! permit their use in free software.  File: gcc.info, Node: Contributors, Next: Option Index, Prev: GNU Free Documentation License, Up: Top *************** File: gcc.info, Node: Contributors, Ne *** 49700,49708 **** Contributors to GCC ******************* ! The GCC project would like to thank its many contributors. Without them ! the project would not have been nearly as successful as it has been. ! Any omissions in this list are accidental. Feel free to contact or if you have been left out or some of your contributions are not listed. Please keep this list in alphabetical order. --- 50291,50299 ---- Contributors to GCC ******************* ! The GCC project would like to thank its many contributors. Without ! them the project would not have been nearly as successful as it has ! been. Any omissions in this list are accidental. Feel free to contact or if you have been left out or some of your contributions are not listed. Please keep this list in alphabetical order. *************** alphabetical order. *** 49837,49843 **** * The GNU Classpath project for all of their merged runtime code. * Nick Clifton for arm, mcore, fr30, v850, m32r, msp430 rx work, ! '--help', and other random hacking. * Michael Cook for libstdc++ cleanup patches to reduce warnings. --- 50428,50434 ---- * The GNU Classpath project for all of their merged runtime code. * Nick Clifton for arm, mcore, fr30, v850, m32r, msp430 rx work, ! `--help', and other random hacking. * Michael Cook for libstdc++ cleanup patches to reduce warnings. *************** alphabetical order. *** 49857,49864 **** * Paul Dale for his work to add uClinux platform support to the m68k backend. ! * Dario Dariol contributed the four varieties of sample programs that ! print a copy of their source. * Russell Davidson for fstream and stringstream fixes in libstdc++. --- 50448,50455 ---- * Paul Dale for his work to add uClinux platform support to the m68k backend. ! * Dario Dariol contributed the four varieties of sample programs ! that print a copy of their source. * Russell Davidson for fstream and stringstream fixes in libstdc++. *************** alphabetical order. *** 49873,49891 **** * Gabriel Dos Reis for contributions to G++, contributions and maintenance of GCC diagnostics infrastructure, libstdc++-v3, ! including 'valarray<>', 'complex<>', maintaining the numerics ! library (including that pesky '' :-) and keeping up-to-date ! anything to do with numbers. * Ulrich Drepper for his work on glibc, testing of GCC using glibc, ! ISO C99 support, CFG dumping support, etc., plus support of the C++ ! runtime libraries including for all kinds of C interface issues, ! contributing and maintaining 'complex<>', sanity checking and ! disbursement, configuration architecture, libio maintenance, and ! early math work. * Franc,ois Dumont for his work on libstdc++-v3, especially ! maintaining and improving 'debug-mode' and associative and unordered containers. * Zdenek Dvorak for a new loop unroller and various fixes. --- 50464,50482 ---- * Gabriel Dos Reis for contributions to G++, contributions and maintenance of GCC diagnostics infrastructure, libstdc++-v3, ! including `valarray<>', `complex<>', maintaining the numerics ! library (including that pesky `' :-) and keeping ! up-to-date anything to do with numbers. * Ulrich Drepper for his work on glibc, testing of GCC using glibc, ! ISO C99 support, CFG dumping support, etc., plus support of the ! C++ runtime libraries including for all kinds of C interface ! issues, contributing and maintaining `complex<>', sanity checking ! and disbursement, configuration architecture, libio maintenance, ! and early math work. * Franc,ois Dumont for his work on libstdc++-v3, especially ! maintaining and improving `debug-mode' and associative and unordered containers. * Zdenek Dvorak for a new loop unroller and various fixes. *************** alphabetical order. *** 49937,49946 **** * Peter Gerwinski for various bug fixes and the Pascal front end. * Kaveh R. Ghazi for his direction via the steering committee, ! amazing work to make '-W -Wall -W* -Werror' useful, and testing GCC ! on a plethora of platforms. Kaveh extends his gratitude to the ! CAIP Center at Rutgers University for providing him with computing ! resources to work on Free Software from the late 1980s to 2010. * John Gilmore for a donation to the FSF earmarked improving GNU Java. --- 50528,50538 ---- * Peter Gerwinski for various bug fixes and the Pascal front end. * Kaveh R. Ghazi for his direction via the steering committee, ! amazing work to make `-W -Wall -W* -Werror' useful, and testing ! GCC on a plethora of platforms. Kaveh extends his gratitude to ! the CAIP Center at Rutgers University for providing him with ! computing resources to work on Free Software from the late 1980s ! to 2010. * John Gilmore for a donation to the FSF earmarked improving GNU Java. *************** alphabetical order. *** 49952,49972 **** support, improved leaf function register allocation, and his direction via the steering committee. ! * Jonny Grant for improvements to 'collect2's' '--help' documentation. ! * Anthony Green for his '-Os' contributions, the moxie port, and Java ! front end work. ! * Stu Grossman for gdb hacking, allowing GCJ developers to debug Java ! code. * Michael K. Gschwind contributed the port to the PDP-11. * Richard Biener for his ongoing middle-end contributions and bug fixes and for release management. ! * Ron Guilmette implemented the 'protoize' and 'unprotoize' tools, the support for DWARF 1 symbolic debugging information, and much of the support for System V Release 4. He has also worked heavily on the Intel 386 and 860 support. --- 50544,50564 ---- support, improved leaf function register allocation, and his direction via the steering committee. ! * Jonny Grant for improvements to `collect2's' `--help' documentation. ! * Anthony Green for his `-Os' contributions, the moxie port, and ! Java front end work. ! * Stu Grossman for gdb hacking, allowing GCJ developers to debug ! Java code. * Michael K. Gschwind contributed the port to the PDP-11. * Richard Biener for his ongoing middle-end contributions and bug fixes and for release management. ! * Ron Guilmette implemented the `protoize' and `unprotoize' tools, the support for DWARF 1 symbolic debugging information, and much of the support for System V Release 4. He has also worked heavily on the Intel 386 and 860 support. *************** alphabetical order. *** 49985,49992 **** series 300. * Michael Hayes for various thankless work he's done trying to get ! the c30/c40 ports functional. Lots of loop and unroll improvements ! and fixes. * Dara Hazeghi for wading through myriads of target-specific bug reports. --- 50577,50584 ---- series 300. * Michael Hayes for various thankless work he's done trying to get ! the c30/c40 ports functional. Lots of loop and unroll ! improvements and fixes. * Dara Hazeghi for wading through myriads of target-specific bug reports. *************** alphabetical order. *** 50020,50027 **** * Falk Hueffner for working on C and optimization bug reports. ! * Bernardo Innocenti for his m68k work, including merging of ColdFire ! improvements and uClinux support. * Christian Iseli for various bug fixes. --- 50612,50619 ---- * Falk Hueffner for working on C and optimization bug reports. ! * Bernardo Innocenti for his m68k work, including merging of ! ColdFire improvements and uClinux support. * Christian Iseli for various bug fixes. *************** alphabetical order. *** 50074,50086 **** * Richard Kenner of the New York University Ultracomputer Research Laboratory wrote the machine descriptions for the AMD 29000, the DEC Alpha, the IBM RT PC, and the IBM RS/6000 as well as the ! support for instruction attributes. He also made changes to better ! support RISC processors including changes to common subexpression ! elimination, strength reduction, function calling sequence ! handling, and condition code support, in addition to generalizing ! the code for frame pointer elimination and delay slot scheduling. ! Richard Kenner was also the head maintainer of GCC for several ! years. * Mumit Khan for various contributions to the Cygwin and Mingw32 ports and maintaining binary releases for Microsoft Windows hosts, --- 50666,50678 ---- * Richard Kenner of the New York University Ultracomputer Research Laboratory wrote the machine descriptions for the AMD 29000, the DEC Alpha, the IBM RT PC, and the IBM RS/6000 as well as the ! support for instruction attributes. He also made changes to ! better support RISC processors including changes to common ! subexpression elimination, strength reduction, function calling ! sequence handling, and condition code support, in addition to ! generalizing the code for frame pointer elimination and delay slot ! scheduling. Richard Kenner was also the head maintainer of GCC ! for several years. * Mumit Khan for various contributions to the Cygwin and Mingw32 ports and maintaining binary releases for Microsoft Windows hosts, *************** alphabetical order. *** 50106,50116 **** * Asher Langton and Mike Kumbera for contributing Cray pointer support to GNU Fortran, and for other GNU Fortran improvements. ! * Jeff Law for his direction via the steering committee, coordinating ! the entire egcs project and GCC 2.95, rolling out snapshots and ! releases, handling merges from GCC2, reviewing tons of patches that ! might have fallen through the cracks else, and random but extensive ! hacking. * Walter Lee for work on the TILE-Gx and TILEPro ports. --- 50698,50708 ---- * Asher Langton and Mike Kumbera for contributing Cray pointer support to GNU Fortran, and for other GNU Fortran improvements. ! * Jeff Law for his direction via the steering committee, ! coordinating the entire egcs project and GCC 2.95, rolling out ! snapshots and releases, handling merges from GCC2, reviewing tons ! of patches that might have fallen through the cracks else, and ! random but extensive hacking. * Walter Lee for work on the TILE-Gx and TILEPro ports. *************** alphabetical order. *** 50139,50145 **** * Weiwen Liu for testing and various bug fixes. ! * Manuel Lo'pez-Iba'n~ez for improving '-Wconversion' and many other diagnostics fixes and improvements. * Dave Love for his ongoing work with the Fortran front end and --- 50731,50737 ---- * Weiwen Liu for testing and various bug fixes. ! * Manuel Lo'pez-Iba'n~ez for improving `-Wconversion' and many other diagnostics fixes and improvements. * Dave Love for his ongoing work with the Fortran front end and *************** alphabetical order. *** 50156,50168 **** * Greg McGary for random fixes and (someday) bounded pointers. * Andrew MacLeod for his ongoing work in building a real EH system, ! various code generation improvements, work on the global optimizer, ! etc. * Vladimir Makarov for hacking some ugly i960 problems, PowerPC ! hacking improvements to compile-time performance, overall knowledge ! and direction in the area of instruction scheduling, and design and ! implementation of the automaton based instruction scheduler. * Bob Manson for his behind the scenes work on dejagnu. --- 50748,50761 ---- * Greg McGary for random fixes and (someday) bounded pointers. * Andrew MacLeod for his ongoing work in building a real EH system, ! various code generation improvements, work on the global ! optimizer, etc. * Vladimir Makarov for hacking some ugly i960 problems, PowerPC ! hacking improvements to compile-time performance, overall ! knowledge and direction in the area of instruction scheduling, and ! design and implementation of the automaton based instruction ! scheduler. * Bob Manson for his behind the scenes work on dejagnu. *************** alphabetical order. *** 50201,50207 **** * Mark Mitchell for his direction via the steering committee, mountains of C++ work, load/store hoisting out of loops, alias ! analysis improvements, ISO C 'restrict' support, and serving as release manager from 2000 to 2011. * Alan Modra for various GNU/Linux bits and testing. --- 50794,50800 ---- * Mark Mitchell for his direction via the steering committee, mountains of C++ work, load/store hoisting out of loops, alias ! analysis improvements, ISO C `restrict' support, and serving as release manager from 2000 to 2011. * Alan Modra for various GNU/Linux bits and testing. *************** alphabetical order. *** 50211,50219 **** * Jason Molenda for major help in the care and feeding of all the services on the gcc.gnu.org (formerly egcs.cygnus.com) ! machine--mail, web services, ftp services, etc etc. Doing all this ! work on scrap paper and the backs of envelopes would have been... ! difficult. * Catherine Moore for fixing various ugly problems we have sent her way, including the haifa bug which was killing the Alpha & PowerPC --- 50804,50812 ---- * Jason Molenda for major help in the care and feeding of all the services on the gcc.gnu.org (formerly egcs.cygnus.com) ! machine--mail, web services, ftp services, etc etc. Doing all ! this work on scrap paper and the backs of envelopes would have ! been... difficult. * Catherine Moore for fixing various ugly problems we have sent her way, including the haifa bug which was killing the Alpha & PowerPC *************** alphabetical order. *** 50225,50232 **** initial IA-64 port. * Stephen Moshier contributed the floating point emulator that ! assists in cross-compilation and permits support for floating point ! numbers wider than 64 bits and for ISO C99 support. * Bill Moyer for his behind the scenes work on various issues. --- 50818,50825 ---- initial IA-64 port. * Stephen Moshier contributed the floating point emulator that ! assists in cross-compilation and permits support for floating ! point numbers wider than 64 bits and for ISO C99 support. * Bill Moyer for his behind the scenes work on various issues. *************** alphabetical order. *** 50249,50257 **** * NeXT, Inc. donated the front end that supports the Objective-C language. ! * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to the ! search engine setup, various documentation fixes and other small ! fixes. * Geoff Noer for his work on getting cygwin native builds working. --- 50842,50850 ---- * NeXT, Inc. donated the front end that supports the Objective-C language. ! * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to ! the search engine setup, various documentation fixes and other ! small fixes. * Geoff Noer for his work on getting cygwin native builds working. *************** alphabetical order. *** 50259,50266 **** tracking web pages, GIMPLE tuples, and assorted fixes. * David O'Brien for the FreeBSD/alpha, FreeBSD/AMD x86-64, ! FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and related ! infrastructure improvements. * Alexandre Oliva for various build infrastructure improvements, scripts and amazing testing work, including keeping libtool issues --- 50852,50859 ---- tracking web pages, GIMPLE tuples, and assorted fixes. * David O'Brien for the FreeBSD/alpha, FreeBSD/AMD x86-64, ! FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and ! related infrastructure improvements. * Alexandre Oliva for various build infrastructure improvements, scripts and amazing testing work, including keeping libtool issues *************** alphabetical order. *** 50272,50279 **** * Rainer Orth for random MIPS work, including improvements to GCC's o32 ABI support, improvements to dejagnu's MIPS support, Java ! configuration clean-ups and porting work, and maintaining the IRIX, ! Solaris 2, and Tru64 UNIX ports. * Hartmut Penner for work on the s390 port. --- 50865,50872 ---- * Rainer Orth for random MIPS work, including improvements to GCC's o32 ABI support, improvements to dejagnu's MIPS support, Java ! configuration clean-ups and porting work, and maintaining the ! IRIX, Solaris 2, and Tru64 UNIX ports. * Hartmut Penner for work on the s390 port. *************** alphabetical order. *** 50323,50329 **** * David Ronis inspired and encouraged Craig to rewrite the G77 documentation in texinfo format by contributing a first pass at a ! translation of the old 'g77-0.5.16/f/DOC' file. * Ken Rose for fixes to GCC's delay slot filling code. --- 50916,50922 ---- * David Ronis inspired and encouraged Craig to rewrite the G77 documentation in texinfo format by contributing a first pass at a ! translation of the old `g77-0.5.16/f/DOC' file. * Ken Rose for fixes to GCC's delay slot filling code. *************** alphabetical order. *** 50355,50362 **** * Tobias Schlu"ter for work on GNU Fortran. * Bernd Schmidt for various code generation improvements and major ! work in the reload pass, serving as release manager for GCC 2.95.3, ! and work on the Blackfin and C6X ports. * Peter Schmid for constant testing of libstdc++--especially application testing, going above and beyond what was requested for --- 50948,50955 ---- * Tobias Schlu"ter for work on GNU Fortran. * Bernd Schmidt for various code generation improvements and major ! work in the reload pass, serving as release manager for GCC ! 2.95.3, and work on the Blackfin and C6X ports. * Peter Schmid for constant testing of libstdc++--especially application testing, going above and beyond what was requested for *************** alphabetical order. *** 50371,50377 **** * Dodji Seketeli for numerous C++ bug fixes and debug info improvements. ! * Tim Shen for major work on ''. * Joel Sherrill for his direction via the steering committee, RTEMS contributions and RTEMS testing. --- 50964,50970 ---- * Dodji Seketeli for numerous C++ bug fixes and debug info improvements. ! * Tim Shen for major work on `'. * Joel Sherrill for his direction via the steering committee, RTEMS contributions and RTEMS testing. *************** alphabetical order. *** 50386,50393 **** from the LWG (thereby keeping GCC in line with updates from the ISO). ! * Franz Sirl for his ongoing work with making the PPC port stable for ! GNU/Linux. * Andrey Slepuhin for assorted AIX hacking. --- 50979,50986 ---- from the LWG (thereby keeping GCC in line with updates from the ISO). ! * Franz Sirl for his ongoing work with making the PPC port stable ! for GNU/Linux. * Andrey Slepuhin for assorted AIX hacking. *************** alphabetical order. *** 50402,50413 **** * Randy Smith finished the Sun FPA support. * Ed Smith-Rowland for his continuous work on libstdc++-v3, special ! functions, '', and various improvements to C++11 features. * Scott Snyder for queue, iterator, istream, and string fixes and libstdc++ testsuite entries. Also for providing the patch to G77 ! to add rudimentary support for 'INTEGER*1', 'INTEGER*2', and ! 'LOGICAL*1'. * Zdenek Sojka for running automated regression testing of GCC and reporting numerous bugs. --- 50995,51006 ---- * Randy Smith finished the Sun FPA support. * Ed Smith-Rowland for his continuous work on libstdc++-v3, special ! functions, `', and various improvements to C++11 features. * Scott Snyder for queue, iterator, istream, and string fixes and libstdc++ testsuite entries. Also for providing the patch to G77 ! to add rudimentary support for `INTEGER*1', `INTEGER*2', and ! `LOGICAL*1'. * Zdenek Sojka for running automated regression testing of GCC and reporting numerous bugs. *************** alphabetical order. *** 50431,50438 **** * John Stracke for his Java HTTP protocol fixes. ! * Mike Stump for his Elxsi port, G++ contributions over the years and ! more recently his vxworks contributions * Jeff Sturm for Java porting help, bug fixes, and encouragement. --- 51024,51031 ---- * John Stracke for his Java HTTP protocol fixes. ! * Mike Stump for his Elxsi port, G++ contributions over the years ! and more recently his vxworks contributions * Jeff Sturm for Java porting help, bug fixes, and encouragement. *************** alphabetical order. *** 50486,50493 **** * Jonathan Wakely for contributing libstdc++ Doxygen notes and XHTML guidance. ! * Dean Wakerley for converting the install documentation from HTML to ! texinfo in time for GCC 3.0. * Krister Walfridsson for random bug fixes. --- 51079,51086 ---- * Jonathan Wakely for contributing libstdc++ Doxygen notes and XHTML guidance. ! * Dean Wakerley for converting the install documentation from HTML ! to texinfo in time for GCC 3.0. * Krister Walfridsson for random bug fixes. *************** alphabetical order. *** 50495,50502 **** * Stephen M. Webb for time and effort on making libstdc++ shadow files work with the tricky Solaris 8+ headers, and for pushing the ! build-time header tree. Also, for starting and driving the ! '' effort. * John Wehle for various improvements for the x86 code generator, related infrastructure improvements to help x86 code generation, --- 51088,51095 ---- * Stephen M. Webb for time and effort on making libstdc++ shadow files work with the tricky Solaris 8+ headers, and for pushing the ! build-time header tree. Also, for starting and driving the ! `' effort. * John Wehle for various improvements for the x86 code generator, related infrastructure improvements to help x86 code generation, *************** alphabetical order. *** 50518,50525 **** * Bob Wilson from Tensilica, Inc. for the Xtensa port. * Jim Wilson for his direction via the steering committee, tackling ! hard problems in various places that nobody else wanted to work on, ! strength reduction and other loop optimizations. * Paul Woegerer and Tal Agmon for the CRX port. --- 51111,51118 ---- * Bob Wilson from Tensilica, Inc. for the Xtensa port. * Jim Wilson for his direction via the steering committee, tackling ! hard problems in various places that nobody else wanted to work ! on, strength reduction and other loop optimizations. * Paul Woegerer and Tal Agmon for the CRX port. *************** alphabetical order. *** 50542,50547 **** --- 51135,51141 ---- * Gilles Zunino for help porting Java to Irix. + The following people are recognized for their contributions to GNAT, the Ada front end of GCC: * Bernard Banner *************** the Ada front end of GCC: *** 50638,50739 **** * Samuel Tardieu The following people are recognized for their contributions of new features, bug reports, testing and integration of classpath/libgcj for GCC version 4.1: ! * Lillian Angel for 'JTree' implementation and lots Free Swing additions and bug fixes. ! * Wolfgang Baer for 'GapContent' bug fixes. ! * Anthony Balkissoon for 'JList', Free Swing 1.5 updates and mouse ! event fixes, lots of Free Swing work including 'JTable' editing. * Stuart Ballard for RMI constant fixes. ! * Goffredo Baroncelli for 'HTTPURLConnection' fixes. ! * Gary Benson for 'MessageFormat' fixes. ! * Daniel Bonniot for 'Serialization' fixes. ! * Chris Burdess for lots of gnu.xml and http protocol fixes, 'StAX' ! and 'DOM xml:id' support. ! * Ka-Hing Cheung for 'TreePath' and 'TreeSelection' fixes. * Archie Cobbs for build fixes, VM interface updates, ! 'URLClassLoader' updates. * Kelley Cook for build fixes. ! * Martin Cordova for Suggestions for better 'SocketTimeoutException'. ! * David Daney for 'BitSet' bug fixes, 'HttpURLConnection' rewrite and ! improvements. * Thomas Fitzsimmons for lots of upgrades to the gtk+ AWT and Cairo ! 2D support. Lots of imageio framework additions, lots of AWT and Free Swing bug fixes. ! * Jeroen Frijters for 'ClassLoader' and nio cleanups, serialization ! fixes, better 'Proxy' support, bug fixes and IKVM integration. ! * Santiago Gala for 'AccessControlContext' fixes. ! * Nicolas Geoffray for 'VMClassLoader' and 'AccessController' improvements. ! * David Gilbert for 'basic' and 'metal' icon and plaf support and lots of documenting, Lots of Free Swing and metal theme additions. ! 'MetalIconFactory' implementation. ! * Anthony Green for 'MIDI' framework, 'ALSA' and 'DSSI' providers. ! * Andrew Haley for 'Serialization' and 'URLClassLoader' fixes, gcj build speedups. ! * Kim Ho for 'JFileChooser' implementation. ! * Andrew John Hughes for 'Locale' and net fixes, URI RFC2986 updates, ! 'Serialization' fixes, 'Properties' XML support and generic branch ! work, VMIntegration guide update. ! * Bastiaan Huisman for 'TimeZone' bug fixing. * Andreas Jaeger for mprec updates. ! * Paul Jenner for better '-Werror' support. ! * Ito Kazumitsu for 'NetworkInterface' implementation and updates. ! * Roman Kennke for 'BoxLayout', 'GrayFilter' and 'SplitPane', plus ! bug fixes all over. Lots of Free Swing work including styled text. ! * Simon Kitching for 'String' cleanups and optimization suggestions. ! * Michael Koch for configuration fixes, 'Locale' updates, bug and build fixes. * Guilhem Lavaux for configuration, thread and channel fixes and ! Kaffe integration. JCL native 'Pointer' updates. Logger bug ! fixes. * David Lichteblau for JCL support library global/local reference cleanups. * Aaron Luchko for JDWP updates and documentation fixes. ! * Ziga Mahkovec for 'Graphics2D' upgraded to Cairo 0.5 and new regex features. ! * Sven de Marothy for BMP imageio support, CSS and 'TextLayout' ! fixes. 'GtkImage' rewrite, 2D, awt, free swing and date/time fixes and implementing the Qt4 peers. ! * Casey Marshall for crypto algorithm fixes, 'FileChannel' lock, ! 'SystemLogger' and 'FileHandler' rotate implementations, NIO ! 'FileChannel.map' support, security and policy updates. * Bryce McKinlay for RMI work. --- 51232,51333 ---- * Samuel Tardieu + The following people are recognized for their contributions of new features, bug reports, testing and integration of classpath/libgcj for GCC version 4.1: ! * Lillian Angel for `JTree' implementation and lots Free Swing additions and bug fixes. ! * Wolfgang Baer for `GapContent' bug fixes. ! * Anthony Balkissoon for `JList', Free Swing 1.5 updates and mouse ! event fixes, lots of Free Swing work including `JTable' editing. * Stuart Ballard for RMI constant fixes. ! * Goffredo Baroncelli for `HTTPURLConnection' fixes. ! * Gary Benson for `MessageFormat' fixes. ! * Daniel Bonniot for `Serialization' fixes. ! * Chris Burdess for lots of gnu.xml and http protocol fixes, `StAX' ! and `DOM xml:id' support. ! * Ka-Hing Cheung for `TreePath' and `TreeSelection' fixes. * Archie Cobbs for build fixes, VM interface updates, ! `URLClassLoader' updates. * Kelley Cook for build fixes. ! * Martin Cordova for Suggestions for better `SocketTimeoutException'. ! * David Daney for `BitSet' bug fixes, `HttpURLConnection' rewrite ! and improvements. * Thomas Fitzsimmons for lots of upgrades to the gtk+ AWT and Cairo ! 2D support. Lots of imageio framework additions, lots of AWT and Free Swing bug fixes. ! * Jeroen Frijters for `ClassLoader' and nio cleanups, serialization ! fixes, better `Proxy' support, bug fixes and IKVM integration. ! * Santiago Gala for `AccessControlContext' fixes. ! * Nicolas Geoffray for `VMClassLoader' and `AccessController' improvements. ! * David Gilbert for `basic' and `metal' icon and plaf support and lots of documenting, Lots of Free Swing and metal theme additions. ! `MetalIconFactory' implementation. ! * Anthony Green for `MIDI' framework, `ALSA' and `DSSI' providers. ! * Andrew Haley for `Serialization' and `URLClassLoader' fixes, gcj build speedups. ! * Kim Ho for `JFileChooser' implementation. ! * Andrew John Hughes for `Locale' and net fixes, URI RFC2986 ! updates, `Serialization' fixes, `Properties' XML support and ! generic branch work, VMIntegration guide update. ! * Bastiaan Huisman for `TimeZone' bug fixing. * Andreas Jaeger for mprec updates. ! * Paul Jenner for better `-Werror' support. ! * Ito Kazumitsu for `NetworkInterface' implementation and updates. ! * Roman Kennke for `BoxLayout', `GrayFilter' and `SplitPane', plus ! bug fixes all over. Lots of Free Swing work including styled text. ! * Simon Kitching for `String' cleanups and optimization suggestions. ! * Michael Koch for configuration fixes, `Locale' updates, bug and build fixes. * Guilhem Lavaux for configuration, thread and channel fixes and ! Kaffe integration. JCL native `Pointer' updates. Logger bug fixes. * David Lichteblau for JCL support library global/local reference cleanups. * Aaron Luchko for JDWP updates and documentation fixes. ! * Ziga Mahkovec for `Graphics2D' upgraded to Cairo 0.5 and new regex features. ! * Sven de Marothy for BMP imageio support, CSS and `TextLayout' ! fixes. `GtkImage' rewrite, 2D, awt, free swing and date/time fixes and implementing the Qt4 peers. ! * Casey Marshall for crypto algorithm fixes, `FileChannel' lock, ! `SystemLogger' and `FileHandler' rotate implementations, NIO ! `FileChannel.map' support, security and policy updates. * Bryce McKinlay for RMI work. *************** GCC version 4.1: *** 50744,50788 **** * Rainer Orth for build fixes. ! * Andrew Overholt for 'File' locking fixes. ! * Ingo Proetel for 'Image', 'Logger' and 'URLClassLoader' updates. ! * Olga Rodimina for 'MenuSelectionManager' implementation. ! * Jan Roehrich for 'BasicTreeUI' and 'JTree' fixes. * Julian Scheid for documentation updates and gjdoc support. * Christian Schlichtherle for zip fixes and cleanups. * Robert Schuster for documentation updates and beans fixes, ! 'TreeNode' enumerations and 'ActionCommand' and various fixes, XML and URL, AWT and Free Swing bug fixes. * Keith Seitz for lots of JDWP work. * Christian Thalinger for 64-bit cleanups, Configuration and VM ! interface fixes and 'CACAO' integration, 'fdlibm' updates. ! * Gael Thomas for 'VMClassLoader' boot packages support suggestions. ! * Andreas Tobler for Darwin and Solaris testing and fixing, 'Qt4' ! support for Darwin/OS X, 'Graphics2D' support, 'gtk+' updates. ! * Dalibor Topic for better 'DEBUG' support, build cleanups and Kaffe ! integration. 'Qt4' build infrastructure, 'SHA1PRNG' and ! 'GdkPixbugDecoder' updates. * Tom Tromey for Eclipse integration, generics work, lots of bug fixes and gcj integration including coordinating The Big Merge. * Mark Wielaard for bug fixes, packaging and release management, ! 'Clipboard' implementation, system call interrupts and network ! timeouts and 'GdkPixpufDecoder' fixes. ! In addition to the above, all of which also contributed time and energy ! in testing GCC, we would like to thank the following for their contributions to testing: * Michael Abd-El-Malek --- 51338,51383 ---- * Rainer Orth for build fixes. ! * Andrew Overholt for `File' locking fixes. ! * Ingo Proetel for `Image', `Logger' and `URLClassLoader' updates. ! * Olga Rodimina for `MenuSelectionManager' implementation. ! * Jan Roehrich for `BasicTreeUI' and `JTree' fixes. * Julian Scheid for documentation updates and gjdoc support. * Christian Schlichtherle for zip fixes and cleanups. * Robert Schuster for documentation updates and beans fixes, ! `TreeNode' enumerations and `ActionCommand' and various fixes, XML and URL, AWT and Free Swing bug fixes. * Keith Seitz for lots of JDWP work. * Christian Thalinger for 64-bit cleanups, Configuration and VM ! interface fixes and `CACAO' integration, `fdlibm' updates. ! * Gael Thomas for `VMClassLoader' boot packages support suggestions. ! * Andreas Tobler for Darwin and Solaris testing and fixing, `Qt4' ! support for Darwin/OS X, `Graphics2D' support, `gtk+' updates. ! * Dalibor Topic for better `DEBUG' support, build cleanups and Kaffe ! integration. `Qt4' build infrastructure, `SHA1PRNG' and ! `GdkPixbugDecoder' updates. * Tom Tromey for Eclipse integration, generics work, lots of bug fixes and gcj integration including coordinating The Big Merge. * Mark Wielaard for bug fixes, packaging and release management, ! `Clipboard' implementation, system call interrupts and network ! timeouts and `GdkPixpufDecoder' fixes. ! ! In addition to the above, all of which also contributed time and ! energy in testing GCC, we would like to thank the following for their contributions to testing: * Michael Abd-El-Malek *************** File: gcc.info, Node: Option Index, Ne *** 50951,50959 **** Option Index ************ ! GCC's command line options are indexed here without any initial '-' or ! '--'. Where an option has both positive and negative forms (such as ! '-fOPTION' and '-fno-OPTION'), relevant entries in the manual are indexed under the most appropriate form; it may sometimes be useful to look up both forms. --- 51546,51554 ---- Option Index ************ ! GCC's command line options are indexed here without any initial `-' or ! `--'. Where an option has both positive and negative forms (such as ! `-fOPTION' and `-fno-OPTION'), relevant entries in the manual are indexed under the most appropriate form; it may sometimes be useful to look up both forms. *************** look up both forms. *** 50961,51139 **** * Menu: * ###: Overall Options. (line 201) ! * -fipa-cp-alignment: Optimize Options. (line 1005) ! * -mlow-precision-recip-sqrt: AArch64 Options. (line 87) ! * -mno-low-precision-recip-sqrt: AArch64 Options. (line 87) * -Wabi-tag: C++ Dialect Options. ! (line 506) ! * -Wno-scalar-storage-order: Warning Options. (line 1500) ! * -Wscalar-storage-order: Warning Options. (line 1500) * A: Preprocessor Options. ! (line 595) ! * allowable_client: Darwin Options. (line 196) * all_load: Darwin Options. (line 110) * ansi: Standards. (line 13) - * ansi <1>: C Dialect Options. (line 11) - * ansi <2>: Preprocessor Options. - (line 340) - * ansi <3>: Other Builtins. (line 31) - * ansi <4>: Non-bugs. (line 107) * arch_errors_fatal: Darwin Options. (line 114) ! * aux-info: C Dialect Options. (line 172) ! * B: Directory Options. (line 44) * Bdynamic: VxWorks Options. (line 22) * bind_at_load: Darwin Options. (line 118) * Bstatic: VxWorks Options. (line 22) * bundle: Darwin Options. (line 123) * bundle_loader: Darwin Options. (line 127) ! * c: Overall Options. (line 156) * C: Preprocessor Options. ! (line 652) ! * c <1>: Link Options. (line 20) * client_name: Darwin Options. (line 196) * compatibility_version: Darwin Options. (line 196) * coverage: Instrumentation Options. (line 46) * current_version: Darwin Options. (line 196) * D: Preprocessor Options. (line 46) - * d: Developer Options. (line 18) - * da: Developer Options. (line 223) * dA: Developer Options. (line 226) ! * dD: Preprocessor Options. ! (line 626) * dD <1>: Developer Options. (line 230) * dead_strip: Darwin Options. (line 196) * dependency-file: Darwin Options. (line 196) * dH: Developer Options. (line 234) * dI: Preprocessor Options. ! (line 635) * dM: Preprocessor Options. ! (line 611) * dN: Preprocessor Options. ! (line 632) ! * dp: Developer Options. (line 237) * dP: Developer Options. (line 242) * dU: Preprocessor Options. ! (line 639) ! * dumpmachine: Developer Options. (line 1019) ! * dumpspecs: Developer Options. (line 1027) ! * dumpversion: Developer Options. (line 1023) * dx: Developer Options. (line 246) * dylib_file: Darwin Options. (line 196) * dylinker_install_name: Darwin Options. (line 196) * dynamic: Darwin Options. (line 196) * dynamiclib: Darwin Options. (line 131) - * E: Overall Options. (line 177) * E <1>: Link Options. (line 20) ! * EB: ARC Options. (line 469) * EB <1>: MIPS Options. (line 7) ! * EL: ARC Options. (line 477) * EL <1>: MIPS Options. (line 10) * exported_symbols_list: Darwin Options. (line 196) * F: Darwin Options. (line 31) * fabi-compat-version: C++ Dialect Options. (line 70) * fabi-version: C++ Dialect Options. (line 24) ! * fada-spec-parent: Overall Options. (line 372) ! * faggressive-loop-optimizations: Optimize Options. (line 512) ! * falign-functions: Optimize Options. (line 1507) ! * falign-jumps: Optimize Options. (line 1556) ! * falign-labels: Optimize Options. (line 1525) ! * falign-loops: Optimize Options. (line 1543) * fallow-parameterless-variadic-functions: C Dialect Options. ! (line 188) * fasan-shadow-offset: Instrumentation Options. ! (line 285) ! * fassociative-math: Optimize Options. (line 2032) * fasynchronous-unwind-tables: Code Gen Options. (line 148) ! * fauto-inc-dec: Optimize Options. (line 542) ! * fauto-profile: Optimize Options. (line 1912) * fbounds-check: Instrumentation Options. ! (line 333) ! * fbranch-probabilities: Optimize Options. (line 2160) ! * fbranch-target-load-optimize: Optimize Options. (line 2282) ! * fbranch-target-load-optimize2: Optimize Options. (line 2288) ! * fbtr-bb-exclusive: Optimize Options. (line 2292) ! * fcall-saved: Code Gen Options. (line 368) ! * fcall-used: Code Gen Options. (line 354) ! * fcaller-saves: Optimize Options. (line 894) * fcheck-new: C++ Dialect Options. (line 90) * fcheck-pointer-bounds: Instrumentation Options. ! (line 339) ! * fchecking: Developer Options. (line 718) * fchkp-check-incomplete-type: Instrumentation Options. ! (line 377) * fchkp-check-read: Instrumentation Options. ! (line 427) * fchkp-check-write: Instrumentation Options. ! (line 431) * fchkp-first-field-has-own-bounds: Instrumentation Options. ! (line 388) * fchkp-instrument-calls: Instrumentation Options. ! (line 439) * fchkp-instrument-marked-only: Instrumentation Options. ! (line 443) * fchkp-narrow-bounds: Instrumentation Options. ! (line 381) * fchkp-narrow-to-innermost-array: Instrumentation Options. ! (line 394) * fchkp-optimize: Instrumentation Options. ! (line 399) * fchkp-store-bounds: Instrumentation Options. ! (line 435) * fchkp-treat-zero-dynamic-size-as-infinite: Instrumentation Options. ! (line 420) * fchkp-use-fast-string-functions: Instrumentation Options. ! (line 403) * fchkp-use-nochk-string-functions: Instrumentation Options. ! (line 407) * fchkp-use-static-bounds: Instrumentation Options. ! (line 411) * fchkp-use-static-const-bounds: Instrumentation Options. ! (line 415) * fchkp-use-wrappers: Instrumentation Options. ! (line 448) ! * fcilkplus: C Dialect Options. (line 290) ! * fcombine-stack-adjustments: Optimize Options. (line 906) * fcommon: Common Variable Attributes. ! (line 89) ! * fcompare-debug: Developer Options. (line 811) ! * fcompare-debug-second: Developer Options. (line 837) ! * fcompare-elim: Optimize Options. (line 1865) * fconcepts: C++ Dialect Options. (line 100) ! * fcond-mismatch: C Dialect Options. (line 354) ! * fconserve-stack: Optimize Options. (line 921) * fconstant-string-class: Objective-C and Objective-C++ Dialect Options. (line 30) * fconstexpr-depth: C++ Dialect Options. (line 107) ! * fcprop-registers: Optimize Options. (line 1877) ! * fcrossjumping: Optimize Options. (line 535) ! * fcse-follow-jumps: Optimize Options. (line 448) ! * fcse-skip-blocks: Optimize Options. (line 457) ! * fcx-fortran-rules: Optimize Options. (line 2147) ! * fcx-limited-range: Optimize Options. (line 2135) ! * fdata-sections: Optimize Options. (line 2263) ! * fdbg-cnt: Developer Options. (line 943) ! * fdbg-cnt-list: Developer Options. (line 940) ! * fdce: Optimize Options. (line 548) * fdebug-cpp: Preprocessor Options. ! (line 526) ! * fdebug-prefix-map: Debugging Options. (line 144) ! * fdebug-types-section: Debugging Options. (line 184) ! * fdeclone-ctor-dtor: Optimize Options. (line 571) * fdeduce-init-list: C++ Dialect Options. (line 113) ! * fdelayed-branch: Optimize Options. (line 724) * fdelete-dead-exceptions: Code Gen Options. (line 133) ! * fdelete-null-pointer-checks: Optimize Options. (line 582) ! * fdevirtualize: Optimize Options. (line 603) ! * fdevirtualize-at-ltrans: Optimize Options. (line 620) ! * fdevirtualize-speculatively: Optimize Options. (line 610) * fdiagnostics-color: Diagnostic Message Formatting Options. (line 35) * fdiagnostics-show-caret: Diagnostic Message Formatting Options. --- 51556,51734 ---- * Menu: * ###: Overall Options. (line 201) ! * -fipa-cp-alignment: Optimize Options. (line 1010) ! * -mlow-precision-recip-sqrt: AArch64 Options. (line 88) ! * -mno-low-precision-recip-sqrt: AArch64 Options. (line 88) * -Wabi-tag: C++ Dialect Options. ! (line 510) ! * -Wno-scalar-storage-order: Warning Options. (line 1519) ! * -Wscalar-storage-order: Warning Options. (line 1519) * A: Preprocessor Options. ! (line 596) * all_load: Darwin Options. (line 110) + * allowable_client: Darwin Options. (line 196) + * ansi <1>: Non-bugs. (line 107) + * ansi <2>: Other Builtins. (line 31) + * ansi <3>: Preprocessor Options. + (line 338) + * ansi <4>: C Dialect Options. (line 11) * ansi: Standards. (line 13) * arch_errors_fatal: Darwin Options. (line 114) ! * aux-info: C Dialect Options. (line 175) ! * B: Directory Options. (line 46) * Bdynamic: VxWorks Options. (line 22) * bind_at_load: Darwin Options. (line 118) * Bstatic: VxWorks Options. (line 22) * bundle: Darwin Options. (line 123) * bundle_loader: Darwin Options. (line 127) ! * c: Link Options. (line 20) * C: Preprocessor Options. ! (line 654) ! * c: Overall Options. (line 156) * client_name: Darwin Options. (line 196) * compatibility_version: Darwin Options. (line 196) * coverage: Instrumentation Options. (line 46) * current_version: Darwin Options. (line 196) + * d: Developer Options. (line 18) * D: Preprocessor Options. (line 46) * dA: Developer Options. (line 226) ! * da: Developer Options. (line 223) * dD <1>: Developer Options. (line 230) + * dD: Preprocessor Options. + (line 628) * dead_strip: Darwin Options. (line 196) * dependency-file: Darwin Options. (line 196) * dH: Developer Options. (line 234) * dI: Preprocessor Options. ! (line 637) * dM: Preprocessor Options. ! (line 612) * dN: Preprocessor Options. ! (line 634) * dP: Developer Options. (line 242) + * dp: Developer Options. (line 237) * dU: Preprocessor Options. ! (line 641) ! * dumpmachine: Developer Options. (line 1047) ! * dumpspecs: Developer Options. (line 1055) ! * dumpversion: Developer Options. (line 1051) * dx: Developer Options. (line 246) * dylib_file: Darwin Options. (line 196) * dylinker_install_name: Darwin Options. (line 196) * dynamic: Darwin Options. (line 196) * dynamiclib: Darwin Options. (line 131) * E <1>: Link Options. (line 20) ! * E: Overall Options. (line 177) * EB <1>: MIPS Options. (line 7) ! * EB: ARC Options. (line 482) * EL <1>: MIPS Options. (line 10) + * EL: ARC Options. (line 489) * exported_symbols_list: Darwin Options. (line 196) * F: Darwin Options. (line 31) * fabi-compat-version: C++ Dialect Options. (line 70) * fabi-version: C++ Dialect Options. (line 24) ! * fada-spec-parent: Overall Options. (line 374) ! * faggressive-loop-optimizations: Optimize Options. (line 516) ! * falign-functions: Optimize Options. (line 1512) ! * falign-jumps: Optimize Options. (line 1561) ! * falign-labels: Optimize Options. (line 1530) ! * falign-loops: Optimize Options. (line 1548) * fallow-parameterless-variadic-functions: C Dialect Options. ! (line 191) * fasan-shadow-offset: Instrumentation Options. ! (line 279) ! * fassociative-math: Optimize Options. (line 2039) * fasynchronous-unwind-tables: Code Gen Options. (line 148) ! * fauto-inc-dec: Optimize Options. (line 546) ! * fauto-profile: Optimize Options. (line 1920) * fbounds-check: Instrumentation Options. ! (line 327) ! * fbranch-probabilities: Optimize Options. (line 2166) ! * fbranch-target-load-optimize: Optimize Options. (line 2288) ! * fbranch-target-load-optimize2: Optimize Options. (line 2294) ! * fbtr-bb-exclusive: Optimize Options. (line 2298) ! * fcall-saved: Code Gen Options. (line 370) ! * fcall-used: Code Gen Options. (line 356) ! * fcaller-saves: Optimize Options. (line 899) * fcheck-new: C++ Dialect Options. (line 90) * fcheck-pointer-bounds: Instrumentation Options. ! (line 333) ! * fchecking: Developer Options. (line 743) * fchkp-check-incomplete-type: Instrumentation Options. ! (line 371) * fchkp-check-read: Instrumentation Options. ! (line 421) * fchkp-check-write: Instrumentation Options. ! (line 425) * fchkp-first-field-has-own-bounds: Instrumentation Options. ! (line 382) * fchkp-instrument-calls: Instrumentation Options. ! (line 433) * fchkp-instrument-marked-only: Instrumentation Options. ! (line 437) * fchkp-narrow-bounds: Instrumentation Options. ! (line 375) * fchkp-narrow-to-innermost-array: Instrumentation Options. ! (line 388) * fchkp-optimize: Instrumentation Options. ! (line 393) * fchkp-store-bounds: Instrumentation Options. ! (line 429) * fchkp-treat-zero-dynamic-size-as-infinite: Instrumentation Options. ! (line 414) * fchkp-use-fast-string-functions: Instrumentation Options. ! (line 397) * fchkp-use-nochk-string-functions: Instrumentation Options. ! (line 401) * fchkp-use-static-bounds: Instrumentation Options. ! (line 405) * fchkp-use-static-const-bounds: Instrumentation Options. ! (line 409) * fchkp-use-wrappers: Instrumentation Options. ! (line 442) ! * fcilkplus: C Dialect Options. (line 289) ! * fcombine-stack-adjustments: Optimize Options. (line 911) * fcommon: Common Variable Attributes. ! (line 90) ! * fcompare-debug: Developer Options. (line 836) ! * fcompare-debug-second: Developer Options. (line 862) ! * fcompare-elim: Optimize Options. (line 1873) * fconcepts: C++ Dialect Options. (line 100) ! * fcond-mismatch: C Dialect Options. (line 353) ! * fconserve-stack: Optimize Options. (line 926) * fconstant-string-class: Objective-C and Objective-C++ Dialect Options. (line 30) * fconstexpr-depth: C++ Dialect Options. (line 107) ! * fcprop-registers: Optimize Options. (line 1885) ! * fcrossjumping: Optimize Options. (line 539) ! * fcse-follow-jumps: Optimize Options. (line 452) ! * fcse-skip-blocks: Optimize Options. (line 461) ! * fcx-fortran-rules: Optimize Options. (line 2152) ! * fcx-limited-range: Optimize Options. (line 2140) ! * fdata-sections: Optimize Options. (line 2269) ! * fdbg-cnt: Developer Options. (line 971) ! * fdbg-cnt-list: Developer Options. (line 968) ! * fdce: Optimize Options. (line 552) * fdebug-cpp: Preprocessor Options. ! (line 525) ! * fdebug-prefix-map: Debugging Options. (line 145) ! * fdebug-types-section: Debugging Options. (line 185) ! * fdeclone-ctor-dtor: Optimize Options. (line 575) * fdeduce-init-list: C++ Dialect Options. (line 113) ! * fdelayed-branch: Optimize Options. (line 729) * fdelete-dead-exceptions: Code Gen Options. (line 133) ! * fdelete-null-pointer-checks: Optimize Options. (line 586) ! * fdevirtualize: Optimize Options. (line 607) ! * fdevirtualize-at-ltrans: Optimize Options. (line 624) ! * fdevirtualize-speculatively: Optimize Options. (line 614) * fdiagnostics-color: Diagnostic Message Formatting Options. (line 35) * fdiagnostics-show-caret: Diagnostic Message Formatting Options. *************** look up both forms. *** 51143,51162 **** * fdiagnostics-show-option: Diagnostic Message Formatting Options. (line 88) * fdirectives-only: Preprocessor Options. ! (line 475) ! * fdisable-: Developer Options. (line 650) ! * fdollars-in-identifiers: Preprocessor Options. ! (line 496) * fdollars-in-identifiers <1>: Interoperation. (line 141) ! * fdpic: SH Options. (line 388) ! * fdse: Optimize Options. (line 552) ! * fdump-ada-spec: Overall Options. (line 367) * fdump-class-hierarchy: Developer Options. (line 281) ! * fdump-final-insns: Developer Options. (line 805) ! * fdump-go-spec: Overall Options. (line 376) * fdump-ipa: Developer Options. (line 289) * fdump-noaddr: Developer Options. (line 250) ! * fdump-passes: Developer Options. (line 306) * fdump-rtl-alignments: Developer Options. (line 42) * fdump-rtl-all: Developer Options. (line 223) * fdump-rtl-asmcons: Developer Options. (line 45) --- 51738,51757 ---- * fdiagnostics-show-option: Diagnostic Message Formatting Options. (line 88) * fdirectives-only: Preprocessor Options. ! (line 473) ! * fdisable-: Developer Options. (line 676) * fdollars-in-identifiers <1>: Interoperation. (line 141) ! * fdollars-in-identifiers: Preprocessor Options. ! (line 495) ! * fdpic: SH Options. (line 392) ! * fdse: Optimize Options. (line 556) ! * fdump-ada-spec: Overall Options. (line 368) * fdump-class-hierarchy: Developer Options. (line 281) ! * fdump-final-insns: Developer Options. (line 830) ! * fdump-go-spec: Overall Options. (line 378) * fdump-ipa: Developer Options. (line 289) * fdump-noaddr: Developer Options. (line 250) ! * fdump-passes: Developer Options. (line 307) * fdump-rtl-alignments: Developer Options. (line 42) * fdump-rtl-all: Developer Options. (line 223) * fdump-rtl-asmcons: Developer Options. (line 45) *************** look up both forms. *** 51165,51171 **** * fdump-rtl-bbpart: Developer Options. (line 56) * fdump-rtl-bbro: Developer Options. (line 59) * fdump-rtl-btl2: Developer Options. (line 63) - * fdump-rtl-btl2 <1>: Developer Options. (line 63) * fdump-rtl-bypass: Developer Options. (line 67) * fdump-rtl-ce1: Developer Options. (line 78) * fdump-rtl-ce2: Developer Options. (line 78) --- 51760,51765 ---- *************** look up both forms. *** 51225,51536 **** * fdump-rtl-vartrack: Developer Options. (line 206) * fdump-rtl-vregs: Developer Options. (line 209) * fdump-rtl-web: Developer Options. (line 212) ! * fdump-statistics: Developer Options. (line 310) * fdump-translation-unit: Developer Options. (line 272) ! * fdump-tree: Developer Options. (line 322) ! * fdump-tree-alias: Developer Options. (line 449) ! * fdump-tree-all: Developer Options. (line 538) ! * fdump-tree-backprop: Developer Options. (line 504) ! * fdump-tree-ccp: Developer Options. (line 453) ! * fdump-tree-cfg: Developer Options. (line 437) ! * fdump-tree-ch: Developer Options. (line 441) ! * fdump-tree-copyprop: Developer Options. (line 469) ! * fdump-tree-dce: Developer Options. (line 477) ! * fdump-tree-dom: Developer Options. (line 490) ! * fdump-tree-dse: Developer Options. (line 495) ! * fdump-tree-forwprop: Developer Options. (line 509) ! * fdump-tree-fre: Developer Options. (line 465) ! * fdump-tree-gimple: Developer Options. (line 432) ! * fdump-tree-nrv: Developer Options. (line 514) ! * fdump-tree-oaccdevlow: Developer Options. (line 533) ! * fdump-tree-optimized: Developer Options. (line 429) ! * fdump-tree-original: Developer Options. (line 426) ! * fdump-tree-phiopt: Developer Options. (line 499) ! * fdump-tree-pre: Developer Options. (line 461) ! * fdump-tree-sink: Developer Options. (line 486) ! * fdump-tree-slp: Developer Options. (line 524) ! * fdump-tree-split-paths: Developer Options. (line 411) ! * fdump-tree-sra: Developer Options. (line 481) ! * fdump-tree-ssa: Developer Options. (line 445) ! * fdump-tree-storeccp: Developer Options. (line 457) ! * fdump-tree-store_copyprop: Developer Options. (line 473) ! * fdump-tree-vect: Developer Options. (line 519) ! * fdump-tree-vrp: Developer Options. (line 529) * fdump-unnumbered: Developer Options. (line 260) * fdump-unnumbered-links: Developer Options. (line 266) ! * fdwarf2-cfi-asm: Debugging Options. (line 298) ! * fearly-inlining: Optimize Options. (line 293) ! * feliminate-dwarf2-dups: Debugging Options. (line 224) ! * feliminate-unused-debug-symbols: Debugging Options. (line 125) ! * feliminate-unused-debug-types: Debugging Options. (line 302) ! * femit-class-debug-always: Debugging Options. (line 129) ! * femit-struct-debug-baseonly: Debugging Options. (line 229) ! * femit-struct-debug-detailed: Debugging Options. (line 256) ! * femit-struct-debug-reduced: Debugging Options. (line 242) ! * fenable-: Developer Options. (line 650) ! * fexceptions: Code Gen Options. (line 111) ! * fexcess-precision: Optimize Options. (line 1959) * fexec-charset: Preprocessor Options. (line 553) ! * fexpensive-optimizations: Optimize Options. (line 627) * fext-numeric-literals: C++ Dialect Options. ! (line 596) * fextended-identifiers: Preprocessor Options. ! (line 499) * fextern-tls-init: C++ Dialect Options. ! (line 162) ! * ffast-math: Optimize Options. (line 1982) ! * ffat-lto-objects: Optimize Options. (line 1847) ! * ffinite-math-only: Optimize Options. (line 2059) * ffix-and-continue: Darwin Options. (line 104) ! * ffixed: Code Gen Options. (line 342) ! * ffloat-store: Optimize Options. (line 1945) * ffloat-store <1>: Disappointments. (line 77) * ffor-scope: C++ Dialect Options. ! (line 183) ! * fforward-propagate: Optimize Options. (line 197) ! * ffp-contract: Optimize Options. (line 206) ! * ffreestanding: Standards. (line 91) ! * ffreestanding <1>: C Dialect Options. (line 251) ! * ffreestanding <2>: Warning Options. (line 279) ! * ffreestanding <3>: Common Function Attributes. (line 274) * ffriend-injection: C++ Dialect Options. (line 134) ! * ffunction-sections: Optimize Options. (line 2263) ! * fgcse: Optimize Options. (line 471) ! * fgcse-after-reload: Optimize Options. (line 507) ! * fgcse-las: Optimize Options. (line 500) ! * fgcse-lm: Optimize Options. (line 482) ! * fgcse-sm: Optimize Options. (line 491) * fgnu-runtime: Objective-C and Objective-C++ Dialect Options. (line 39) ! * fgnu-tm: C Dialect Options. (line 300) ! * fgnu89-inline: C Dialect Options. (line 155) ! * fgraphite-identity: Optimize Options. (line 1125) ! * fhoist-adjacent-loads: Optimize Options. (line 954) ! * fhosted: C Dialect Options. (line 243) ! * fif-conversion: Optimize Options. (line 556) ! * fif-conversion2: Optimize Options. (line 565) * filelist: Darwin Options. (line 196) * findirect-data: Darwin Options. (line 104) ! * findirect-inlining: Optimize Options. (line 266) ! * finhibit-size-directive: Code Gen Options. (line 245) ! * finline-functions: Optimize Options. (line 274) ! * finline-functions-called-once: Optimize Options. (line 285) ! * finline-limit: Optimize Options. (line 309) ! * finline-small-functions: Optimize Options. (line 257) * finput-charset: Preprocessor Options. (line 566) - * finstrument-functions: Instrumentation Options. - (line 602) * finstrument-functions <1>: Common Function Attributes. ! (line 492) * finstrument-functions-exclude-file-list: Instrumentation Options. ! (line 637) * finstrument-functions-exclude-function-list: Instrumentation Options. ! (line 658) ! * fipa-cp: Optimize Options. (line 987) ! * fipa-cp-clone: Optimize Options. (line 995) ! * fipa-icf: Optimize Options. (line 1012) ! * fipa-profile: Optimize Options. (line 979) ! * fipa-pta: Optimize Options. (line 973) ! * fipa-pure-const: Optimize Options. (line 965) ! * fipa-ra: Optimize Options. (line 912) ! * fipa-reference: Optimize Options. (line 969) ! * fipa-sra: Optimize Options. (line 302) ! * fira-algorithm: Optimize Options. (line 661) ! * fira-hoist-pressure: Optimize Options. (line 690) ! * fira-loop-pressure: Optimize Options. (line 697) ! * fira-region: Optimize Options. (line 669) ! * fira-verbose: Developer Options. (line 870) ! * fisolate-erroneous-paths-attribute: Optimize Options. (line 1034) ! * fisolate-erroneous-paths-dereference: Optimize Options. (line 1026) * fivar-visibility: Objective-C and Objective-C++ Dialect Options. (line 162) ! * fivopts: Optimize Options. (line 1227) ! * fkeep-inline-functions: Optimize Options. (line 340) * fkeep-inline-functions <1>: Inline. (line 51) ! * fkeep-static-consts: Optimize Options. (line 351) ! * fkeep-static-functions: Optimize Options. (line 347) * flat_namespace: Darwin Options. (line 196) ! * flax-vector-conversions: C Dialect Options. (line 359) ! * fleading-underscore: Code Gen Options. (line 398) ! * flive-range-shrinkage: Optimize Options. (line 656) * flocal-ivars: Objective-C and Objective-C++ Dialect Options. (line 153) ! * floop-block: Optimize Options. (line 1119) ! * floop-interchange: Optimize Options. (line 1119) ! * floop-nest-optimize: Optimize Options. (line 1133) ! * floop-parallelize-all: Optimize Options. (line 1139) ! * floop-strip-mine: Optimize Options. (line 1119) ! * floop-unroll-and-jam: Optimize Options. (line 1119) ! * flra-remat: Optimize Options. (line 717) ! * flto: Optimize Options. (line 1610) ! * flto-compression-level: Optimize Options. (line 1821) ! * flto-odr-type-merging: Optimize Options. (line 1816) ! * flto-partition: Optimize Options. (line 1802) ! * flto-report: Developer Options. (line 876) ! * flto-report-wpa: Developer Options. (line 884) * fmax-errors: Warning Options. (line 18) ! * fmem-report: Developer Options. (line 888) ! * fmem-report-wpa: Developer Options. (line 892) ! * fmerge-all-constants: Optimize Options. (line 370) ! * fmerge-constants: Optimize Options. (line 360) ! * fmerge-debug-strings: Debugging Options. (line 137) * fmessage-length: Diagnostic Message Formatting Options. (line 14) ! * fmodulo-sched: Optimize Options. (line 381) ! * fmodulo-sched-allow-regmoves: Optimize Options. (line 386) ! * fmove-loop-invariants: Optimize Options. (line 2253) ! * fms-extensions: C Dialect Options. (line 315) ! * fms-extensions <1>: C++ Dialect Options. ! (line 218) ! * fms-extensions <2>: Unnamed Fields. (line 36) * fnext-runtime: Objective-C and Objective-C++ Dialect Options. (line 43) * fno-access-control: C++ Dialect Options. (line 86) ! * fno-asm: C Dialect Options. (line 195) ! * fno-branch-count-reg: Optimize Options. (line 393) ! * fno-builtin: C Dialect Options. (line 209) ! * fno-builtin <1>: Warning Options. (line 279) * fno-builtin <2>: Common Function Attributes. (line 274) ! * fno-builtin <3>: Other Builtins. (line 21) * fno-canonical-system-headers: Preprocessor Options. ! (line 503) * fno-check-pointer-bounds: Instrumentation Options. ! (line 339) ! * fno-checking: Developer Options. (line 718) * fno-chkp-check-incomplete-type: Instrumentation Options. ! (line 377) * fno-chkp-check-read: Instrumentation Options. ! (line 427) * fno-chkp-check-write: Instrumentation Options. ! (line 431) * fno-chkp-first-field-has-own-bounds: Instrumentation Options. ! (line 388) * fno-chkp-instrument-calls: Instrumentation Options. ! (line 439) * fno-chkp-instrument-marked-only: Instrumentation Options. ! (line 443) * fno-chkp-narrow-bounds: Instrumentation Options. ! (line 381) * fno-chkp-narrow-to-innermost-array: Instrumentation Options. ! (line 394) * fno-chkp-optimize: Instrumentation Options. ! (line 399) * fno-chkp-store-bounds: Instrumentation Options. ! (line 435) * fno-chkp-treat-zero-dynamic-size-as-infinite: Instrumentation Options. ! (line 420) * fno-chkp-use-fast-string-functions: Instrumentation Options. ! (line 403) * fno-chkp-use-nochk-string-functions: Instrumentation Options. ! (line 407) * fno-chkp-use-static-bounds: Instrumentation Options. ! (line 411) * fno-chkp-use-static-const-bounds: Instrumentation Options. ! (line 415) * fno-chkp-use-wrappers: Instrumentation Options. ! (line 448) ! * fno-common: Code Gen Options. (line 223) * fno-common <1>: Common Variable Attributes. ! (line 89) ! * fno-compare-debug: Developer Options. (line 811) ! * fno-debug-types-section: Debugging Options. (line 184) * fno-default-inline: Inline. (line 68) ! * fno-defer-pop: Optimize Options. (line 189) * fno-diagnostics-show-caret: Diagnostic Message Formatting Options. (line 94) * fno-diagnostics-show-option: Diagnostic Message Formatting Options. (line 88) ! * fno-dwarf2-cfi-asm: Debugging Options. (line 298) * fno-elide-constructors: C++ Dialect Options. (line 146) ! * fno-eliminate-unused-debug-types: Debugging Options. (line 302) * fno-enforce-eh-specs: C++ Dialect Options. (line 152) * fno-ext-numeric-literals: C++ Dialect Options. ! (line 596) * fno-extern-tls-init: C++ Dialect Options. ! (line 162) * fno-for-scope: C++ Dialect Options. ! (line 183) ! * fno-function-cse: Optimize Options. (line 408) * fno-gnu-keywords: C++ Dialect Options. ! (line 195) * fno-gnu-unique: Code Gen Options. (line 154) ! * fno-guess-branch-probability: Optimize Options. (line 1366) ! * fno-ident: Code Gen Options. (line 242) ! * fno-implement-inlines: C++ Dialect Options. ! (line 213) * fno-implement-inlines <1>: C++ Interface. (line 66) * fno-implicit-inline-templates: C++ Dialect Options. ! (line 207) ! * fno-implicit-templates: C++ Dialect Options. ! (line 201) * fno-implicit-templates <1>: Template Instantiation. (line 118) ! * fno-inline: Optimize Options. (line 249) ! * fno-ira-share-save-slots: Optimize Options. (line 705) ! * fno-ira-share-spill-slots: Optimize Options. (line 711) ! * fno-jump-tables: Code Gen Options. (line 334) ! * fno-keep-inline-dllexport: Optimize Options. (line 334) ! * fno-lifetime-dse: Optimize Options. (line 641) * fno-local-ivars: Objective-C and Objective-C++ Dialect Options. (line 153) ! * fno-math-errno: Optimize Options. (line 1996) ! * fno-merge-debug-strings: Debugging Options. (line 137) * fno-nil-receivers: Objective-C and Objective-C++ Dialect Options. (line 49) * fno-nonansi-builtins: C++ Dialect Options. ! (line 223) * fno-operator-names: C++ Dialect Options. ! (line 239) * fno-optional-diags: C++ Dialect Options. ! (line 243) ! * fno-peephole: Optimize Options. (line 1357) ! * fno-peephole2: Optimize Options. (line 1357) ! * fno-plt: Code Gen Options. (line 316) * fno-pretty-templates: C++ Dialect Options. ! (line 253) * fno-rtti: C++ Dialect Options. ! (line 270) * fno-sanitize-recover: Instrumentation Options. ! (line 294) * fno-sanitize=all: Instrumentation Options. ! (line 279) ! * fno-sched-interblock: Optimize Options. (line 750) ! * fno-sched-spec: Optimize Options. (line 755) * fno-set-stack-executable: x86 Windows Options. (line 46) * fno-show-column: Preprocessor Options. ! (line 590) ! * fno-signed-bitfields: C Dialect Options. (line 392) ! * fno-signed-zeros: Optimize Options. (line 2071) * fno-stack-limit: Instrumentation Options. ! (line 514) * fno-threadsafe-statics: C++ Dialect Options. ! (line 312) ! * fno-toplevel-reorder: Optimize Options. (line 1576) ! * fno-trapping-math: Optimize Options. (line 2081) ! * fno-unsigned-bitfields: C Dialect Options. (line 392) * fno-use-cxa-get-exception-ptr: C++ Dialect Options. ! (line 325) ! * fno-var-tracking-assignments: Debugging Options. (line 158) ! * fno-var-tracking-assignments-toggle: Developer Options. (line 858) * fno-weak: C++ Dialect Options. ! (line 387) * fno-working-directory: Preprocessor Options. (line 576) * fno-writable-relocated-rdata: x86 Windows Options. (line 53) ! * fno-zero-initialized-in-bss: Optimize Options. (line 419) ! * fnon-call-exceptions: Code Gen Options. (line 125) * fnothrow-opt: C++ Dialect Options. ! (line 228) * fobjc-abi-version: Objective-C and Objective-C++ Dialect Options. (line 56) * fobjc-call-cxx-cdtors: Objective-C and Objective-C++ Dialect Options. --- 51819,52130 ---- * fdump-rtl-vartrack: Developer Options. (line 206) * fdump-rtl-vregs: Developer Options. (line 209) * fdump-rtl-web: Developer Options. (line 212) ! * fdump-statistics: Developer Options. (line 311) * fdump-translation-unit: Developer Options. (line 272) ! * fdump-tree: Developer Options. (line 323) ! * fdump-tree-alias: Developer Options. (line 467) ! * fdump-tree-all: Developer Options. (line 557) ! * fdump-tree-backprop: Developer Options. (line 523) ! * fdump-tree-ccp: Developer Options. (line 471) ! * fdump-tree-cfg: Developer Options. (line 455) ! * fdump-tree-ch: Developer Options. (line 459) ! * fdump-tree-copyprop: Developer Options. (line 487) ! * fdump-tree-dce: Developer Options. (line 495) ! * fdump-tree-dom: Developer Options. (line 508) ! * fdump-tree-dse: Developer Options. (line 513) ! * fdump-tree-forwprop: Developer Options. (line 528) ! * fdump-tree-fre: Developer Options. (line 483) ! * fdump-tree-gimple: Developer Options. (line 450) ! * fdump-tree-nrv: Developer Options. (line 533) ! * fdump-tree-oaccdevlow: Developer Options. (line 552) ! * fdump-tree-optimized: Developer Options. (line 447) ! * fdump-tree-original: Developer Options. (line 444) ! * fdump-tree-phiopt: Developer Options. (line 518) ! * fdump-tree-pre: Developer Options. (line 479) ! * fdump-tree-sink: Developer Options. (line 504) ! * fdump-tree-slp: Developer Options. (line 543) ! * fdump-tree-split-paths: Developer Options. (line 430) ! * fdump-tree-sra: Developer Options. (line 499) ! * fdump-tree-ssa: Developer Options. (line 463) ! * fdump-tree-store_copyprop: Developer Options. (line 491) ! * fdump-tree-storeccp: Developer Options. (line 475) ! * fdump-tree-vect: Developer Options. (line 538) ! * fdump-tree-vrp: Developer Options. (line 548) * fdump-unnumbered: Developer Options. (line 260) * fdump-unnumbered-links: Developer Options. (line 266) ! * fdwarf2-cfi-asm: Debugging Options. (line 300) ! * fearly-inlining: Optimize Options. (line 295) ! * feliminate-dwarf2-dups: Debugging Options. (line 226) ! * feliminate-unused-debug-symbols: Debugging Options. (line 126) ! * feliminate-unused-debug-types: Debugging Options. (line 304) ! * femit-class-debug-always: Debugging Options. (line 130) ! * femit-struct-debug-baseonly: Debugging Options. (line 231) ! * femit-struct-debug-detailed: Debugging Options. (line 258) ! * femit-struct-debug-reduced: Debugging Options. (line 244) ! * fenable-: Developer Options. (line 676) ! * fexceptions: Code Gen Options. (line 110) ! * fexcess-precision: Optimize Options. (line 1967) * fexec-charset: Preprocessor Options. (line 553) ! * fexpensive-optimizations: Optimize Options. (line 631) * fext-numeric-literals: C++ Dialect Options. ! (line 600) * fextended-identifiers: Preprocessor Options. ! (line 498) * fextern-tls-init: C++ Dialect Options. ! (line 163) ! * ffast-math: Optimize Options. (line 1990) ! * ffat-lto-objects: Optimize Options. (line 1854) ! * ffinite-math-only: Optimize Options. (line 2064) * ffix-and-continue: Darwin Options. (line 104) ! * ffixed: Code Gen Options. (line 344) * ffloat-store <1>: Disappointments. (line 77) + * ffloat-store: Optimize Options. (line 1953) * ffor-scope: C++ Dialect Options. ! (line 184) ! * fforward-propagate: Optimize Options. (line 198) ! * ffp-contract: Optimize Options. (line 207) ! * ffreestanding <1>: Common Function Attributes. (line 274) + * ffreestanding <2>: Warning Options. (line 285) + * ffreestanding <3>: C Dialect Options. (line 253) + * ffreestanding: Standards. (line 91) * ffriend-injection: C++ Dialect Options. (line 134) ! * ffunction-sections: Optimize Options. (line 2269) ! * fgcse: Optimize Options. (line 475) ! * fgcse-after-reload: Optimize Options. (line 511) ! * fgcse-las: Optimize Options. (line 504) ! * fgcse-lm: Optimize Options. (line 486) ! * fgcse-sm: Optimize Options. (line 495) * fgnu-runtime: Objective-C and Objective-C++ Dialect Options. (line 39) ! * fgnu-tm: C Dialect Options. (line 299) ! * fgnu89-inline: C Dialect Options. (line 158) ! * fgraphite-identity: Optimize Options. (line 1130) ! * fhoist-adjacent-loads: Optimize Options. (line 959) ! * fhosted: C Dialect Options. (line 246) ! * fif-conversion: Optimize Options. (line 560) ! * fif-conversion2: Optimize Options. (line 569) * filelist: Darwin Options. (line 196) * findirect-data: Darwin Options. (line 104) ! * findirect-inlining: Optimize Options. (line 268) ! * finhibit-size-directive: Code Gen Options. (line 246) ! * finline-functions: Optimize Options. (line 276) ! * finline-functions-called-once: Optimize Options. (line 287) ! * finline-limit: Optimize Options. (line 312) ! * finline-small-functions: Optimize Options. (line 259) * finput-charset: Preprocessor Options. (line 566) * finstrument-functions <1>: Common Function Attributes. ! (line 496) ! * finstrument-functions: Instrumentation Options. ! (line 597) * finstrument-functions-exclude-file-list: Instrumentation Options. ! (line 633) * finstrument-functions-exclude-function-list: Instrumentation Options. ! (line 653) ! * fipa-cp: Optimize Options. (line 992) ! * fipa-cp-clone: Optimize Options. (line 1000) ! * fipa-icf: Optimize Options. (line 1017) ! * fipa-profile: Optimize Options. (line 984) ! * fipa-pta: Optimize Options. (line 978) ! * fipa-pure-const: Optimize Options. (line 970) ! * fipa-ra: Optimize Options. (line 917) ! * fipa-reference: Optimize Options. (line 974) ! * fipa-sra: Optimize Options. (line 305) ! * fira-algorithm: Optimize Options. (line 665) ! * fira-hoist-pressure: Optimize Options. (line 695) ! * fira-loop-pressure: Optimize Options. (line 702) ! * fira-region: Optimize Options. (line 673) ! * fira-verbose: Developer Options. (line 895) ! * fisolate-erroneous-paths-attribute: Optimize Options. (line 1039) ! * fisolate-erroneous-paths-dereference: Optimize Options. (line 1031) * fivar-visibility: Objective-C and Objective-C++ Dialect Options. (line 162) ! * fivopts: Optimize Options. (line 1232) * fkeep-inline-functions <1>: Inline. (line 51) ! * fkeep-inline-functions: Optimize Options. (line 344) ! * fkeep-static-consts: Optimize Options. (line 355) ! * fkeep-static-functions: Optimize Options. (line 351) * flat_namespace: Darwin Options. (line 196) ! * flax-vector-conversions: C Dialect Options. (line 358) ! * fleading-underscore: Code Gen Options. (line 400) ! * flive-range-shrinkage: Optimize Options. (line 660) * flocal-ivars: Objective-C and Objective-C++ Dialect Options. (line 153) ! * floop-block: Optimize Options. (line 1124) ! * floop-interchange: Optimize Options. (line 1124) ! * floop-nest-optimize: Optimize Options. (line 1138) ! * floop-parallelize-all: Optimize Options. (line 1144) ! * floop-strip-mine: Optimize Options. (line 1124) ! * floop-unroll-and-jam: Optimize Options. (line 1124) ! * flra-remat: Optimize Options. (line 722) ! * flto: Optimize Options. (line 1615) ! * flto-compression-level: Optimize Options. (line 1828) ! * flto-odr-type-merging: Optimize Options. (line 1822) ! * flto-partition: Optimize Options. (line 1808) ! * flto-report: Developer Options. (line 901) ! * flto-report-wpa: Developer Options. (line 909) * fmax-errors: Warning Options. (line 18) ! * fmem-report: Developer Options. (line 913) ! * fmem-report-wpa: Developer Options. (line 917) ! * fmerge-all-constants: Optimize Options. (line 374) ! * fmerge-constants: Optimize Options. (line 364) ! * fmerge-debug-strings: Debugging Options. (line 138) * fmessage-length: Diagnostic Message Formatting Options. (line 14) ! * fmodulo-sched: Optimize Options. (line 385) ! * fmodulo-sched-allow-regmoves: Optimize Options. (line 390) ! * fmove-loop-invariants: Optimize Options. (line 2259) ! * fms-extensions <1>: Unnamed Fields. (line 36) ! * fms-extensions <2>: C++ Dialect Options. ! (line 219) ! * fms-extensions: C Dialect Options. (line 314) * fnext-runtime: Objective-C and Objective-C++ Dialect Options. (line 43) * fno-access-control: C++ Dialect Options. (line 86) ! * fno-asm: C Dialect Options. (line 198) ! * fno-branch-count-reg: Optimize Options. (line 397) ! * fno-builtin <1>: Other Builtins. (line 21) * fno-builtin <2>: Common Function Attributes. (line 274) ! * fno-builtin <3>: Warning Options. (line 285) ! * fno-builtin: C Dialect Options. (line 212) * fno-canonical-system-headers: Preprocessor Options. ! (line 502) * fno-check-pointer-bounds: Instrumentation Options. ! (line 333) ! * fno-checking: Developer Options. (line 743) * fno-chkp-check-incomplete-type: Instrumentation Options. ! (line 371) * fno-chkp-check-read: Instrumentation Options. ! (line 421) * fno-chkp-check-write: Instrumentation Options. ! (line 425) * fno-chkp-first-field-has-own-bounds: Instrumentation Options. ! (line 382) * fno-chkp-instrument-calls: Instrumentation Options. ! (line 433) * fno-chkp-instrument-marked-only: Instrumentation Options. ! (line 437) * fno-chkp-narrow-bounds: Instrumentation Options. ! (line 375) * fno-chkp-narrow-to-innermost-array: Instrumentation Options. ! (line 388) * fno-chkp-optimize: Instrumentation Options. ! (line 393) * fno-chkp-store-bounds: Instrumentation Options. ! (line 429) * fno-chkp-treat-zero-dynamic-size-as-infinite: Instrumentation Options. ! (line 414) * fno-chkp-use-fast-string-functions: Instrumentation Options. ! (line 397) * fno-chkp-use-nochk-string-functions: Instrumentation Options. ! (line 401) * fno-chkp-use-static-bounds: Instrumentation Options. ! (line 405) * fno-chkp-use-static-const-bounds: Instrumentation Options. ! (line 409) * fno-chkp-use-wrappers: Instrumentation Options. ! (line 442) * fno-common <1>: Common Variable Attributes. ! (line 90) ! * fno-common: Code Gen Options. (line 223) ! * fno-compare-debug: Developer Options. (line 836) ! * fno-debug-types-section: Debugging Options. (line 185) * fno-default-inline: Inline. (line 68) ! * fno-defer-pop: Optimize Options. (line 190) * fno-diagnostics-show-caret: Diagnostic Message Formatting Options. (line 94) * fno-diagnostics-show-option: Diagnostic Message Formatting Options. (line 88) ! * fno-dwarf2-cfi-asm: Debugging Options. (line 300) * fno-elide-constructors: C++ Dialect Options. (line 146) ! * fno-eliminate-unused-debug-types: Debugging Options. (line 304) * fno-enforce-eh-specs: C++ Dialect Options. (line 152) * fno-ext-numeric-literals: C++ Dialect Options. ! (line 600) * fno-extern-tls-init: C++ Dialect Options. ! (line 163) * fno-for-scope: C++ Dialect Options. ! (line 184) ! * fno-function-cse: Optimize Options. (line 412) * fno-gnu-keywords: C++ Dialect Options. ! (line 196) * fno-gnu-unique: Code Gen Options. (line 154) ! * fno-guess-branch-probability: Optimize Options. (line 1371) ! * fno-ident: Code Gen Options. (line 243) * fno-implement-inlines <1>: C++ Interface. (line 66) + * fno-implement-inlines: C++ Dialect Options. + (line 214) * fno-implicit-inline-templates: C++ Dialect Options. ! (line 208) * fno-implicit-templates <1>: Template Instantiation. (line 118) ! * fno-implicit-templates: C++ Dialect Options. ! (line 202) ! * fno-inline: Optimize Options. (line 251) ! * fno-ira-share-save-slots: Optimize Options. (line 710) ! * fno-ira-share-spill-slots: Optimize Options. (line 716) ! * fno-jump-tables: Code Gen Options. (line 336) ! * fno-keep-inline-dllexport: Optimize Options. (line 338) ! * fno-lifetime-dse: Optimize Options. (line 645) * fno-local-ivars: Objective-C and Objective-C++ Dialect Options. (line 153) ! * fno-math-errno: Optimize Options. (line 2004) ! * fno-merge-debug-strings: Debugging Options. (line 138) * fno-nil-receivers: Objective-C and Objective-C++ Dialect Options. (line 49) * fno-nonansi-builtins: C++ Dialect Options. ! (line 224) * fno-operator-names: C++ Dialect Options. ! (line 240) * fno-optional-diags: C++ Dialect Options. ! (line 244) ! * fno-peephole: Optimize Options. (line 1362) ! * fno-peephole2: Optimize Options. (line 1362) ! * fno-plt: Code Gen Options. (line 318) * fno-pretty-templates: C++ Dialect Options. ! (line 254) * fno-rtti: C++ Dialect Options. ! (line 271) * fno-sanitize-recover: Instrumentation Options. ! (line 288) * fno-sanitize=all: Instrumentation Options. ! (line 274) ! * fno-sched-interblock: Optimize Options. (line 755) ! * fno-sched-spec: Optimize Options. (line 760) * fno-set-stack-executable: x86 Windows Options. (line 46) * fno-show-column: Preprocessor Options. ! (line 591) ! * fno-signed-bitfields: C Dialect Options. (line 391) ! * fno-signed-zeros: Optimize Options. (line 2076) * fno-stack-limit: Instrumentation Options. ! (line 509) * fno-threadsafe-statics: C++ Dialect Options. ! (line 313) ! * fno-toplevel-reorder: Optimize Options. (line 1581) ! * fno-trapping-math: Optimize Options. (line 2086) ! * fno-unsigned-bitfields: C Dialect Options. (line 391) * fno-use-cxa-get-exception-ptr: C++ Dialect Options. ! (line 326) ! * fno-var-tracking-assignments: Debugging Options. (line 159) ! * fno-var-tracking-assignments-toggle: Developer Options. (line 883) * fno-weak: C++ Dialect Options. ! (line 388) * fno-working-directory: Preprocessor Options. (line 576) * fno-writable-relocated-rdata: x86 Windows Options. (line 53) ! * fno-zero-initialized-in-bss: Optimize Options. (line 423) ! * fnon-call-exceptions: Code Gen Options. (line 124) * fnothrow-opt: C++ Dialect Options. ! (line 229) * fobjc-abi-version: Objective-C and Objective-C++ Dialect Options. (line 56) * fobjc-call-cxx-cdtors: Objective-C and Objective-C++ Dialect Options. *************** look up both forms. *** 51545,51938 **** (line 111) * fobjc-std: Objective-C and Objective-C++ Dialect Options. (line 120) ! * fomit-frame-pointer: Optimize Options. (line 217) ! * fopenacc: C Dialect Options. (line 262) * fopenacc-dim: C Dialect Options. (line 271) * fopenmp: C Dialect Options. (line 277) ! * fopenmp-simd: C Dialect Options. (line 286) ! * fopt-info: Developer Options. (line 544) ! * foptimize-sibling-calls: Optimize Options. (line 237) ! * foptimize-strlen: Optimize Options. (line 242) * force_cpusubtype_ALL: Darwin Options. (line 135) * force_flat_namespace: Darwin Options. (line 196) ! * fpack-struct: Code Gen Options. (line 385) ! * fpartial-inlining: Optimize Options. (line 1332) ! * fpcc-struct-return: Code Gen Options. (line 167) * fpcc-struct-return <1>: Incompatibilities. (line 170) * fpch-deps: Preprocessor Options. ! (line 296) * fpch-preprocess: Preprocessor Options. ! (line 304) ! * fpeel-loops: Optimize Options. (line 2245) * fpermissive: C++ Dialect Options. ! (line 248) ! * fpic: Code Gen Options. (line 273) ! * fPIC: Code Gen Options. (line 294) ! * fpie: Code Gen Options. (line 307) ! * fPIE: Code Gen Options. (line 307) ! * fplan9-extensions: C Dialect Options. (line 333) ! * fplan9-extensions <1>: Unnamed Fields. (line 43) * fplugin: Overall Options. (line 356) ! * fplugin-arg: Overall Options. (line 363) ! * fpost-ipa-mem-report: Developer Options. (line 897) ! * fpre-ipa-mem-report: Developer Options. (line 896) ! * fpredictive-commoning: Optimize Options. (line 1339) ! * fprefetch-loop-arrays: Optimize Options. (line 1346) * fpreprocessed: Preprocessor Options. ! (line 507) * fprofile-arcs: Instrumentation Options. (line 31) ! * fprofile-arcs <1>: Other Builtins. (line 356) ! * fprofile-correction: Optimize Options. (line 1884) * fprofile-dir: Instrumentation Options. ! (line 95) * fprofile-generate: Instrumentation Options. (line 106) ! * fprofile-reorder-functions: Optimize Options. (line 2187) ! * fprofile-report: Developer Options. (line 901) ! * fprofile-use: Optimize Options. (line 1892) ! * fprofile-values: Optimize Options. (line 2178) * fpu: RX Options. (line 17) ! * fpud: ARC Options. (line 157) ! * fpuda: ARC Options. (line 162) ! * fpuda_all: ARC Options. (line 182) ! * fpuda_div: ARC Options. (line 168) ! * fpuda_fma: ARC Options. (line 175) ! * fpud_all: ARC Options. (line 213) ! * fpud_div: ARC Options. (line 193) ! * fpud_fma: ARC Options. (line 203) ! * fpus: ARC Options. (line 153) ! * fpus_all: ARC Options. (line 209) ! * fpus_div: ARC Options. (line 189) ! * fpus_fma: ARC Options. (line 199) ! * frandom-seed: Developer Options. (line 722) ! * freciprocal-math: Optimize Options. (line 2049) ! * frecord-gcc-switches: Code Gen Options. (line 261) ! * free: Optimize Options. (line 633) * freg-struct-return: Code Gen Options. (line 185) ! * frename-registers: Optimize Options. (line 2204) ! * freorder-blocks: Optimize Options. (line 1383) ! * freorder-blocks-algorithm: Optimize Options. (line 1389) ! * freorder-blocks-and-partition: Optimize Options. (line 1400) ! * freorder-functions: Optimize Options. (line 1413) * freplace-objc-classes: Objective-C and Objective-C++ Dialect Options. (line 131) - * frepo: C++ Dialect Options. - (line 265) * frepo <1>: Template Instantiation. (line 94) * freport-bug: Developer Options. (line 256) ! * frerun-cse-after-loop: Optimize Options. (line 465) ! * freschedule-modulo-scheduled-loops: Optimize Options. (line 849) ! * frounding-math: Optimize Options. (line 2096) * fsanitize-coverage=trace-pc: Instrumentation Options. ! (line 329) * fsanitize-recover: Instrumentation Options. ! (line 294) * fsanitize-sections: Instrumentation Options. ! (line 290) * fsanitize-undefined-trap-on-error: Instrumentation Options. ! (line 322) * fsanitize=address: Instrumentation Options. ! (line 123) * fsanitize=alignment: Instrumentation Options. ! (line 219) * fsanitize=bool: Instrumentation Options. ! (line 257) * fsanitize=bounds: Instrumentation Options. ! (line 206) * fsanitize=bounds-strict: Instrumentation Options. ! (line 212) * fsanitize=enum: Instrumentation Options. ! (line 262) * fsanitize=float-cast-overflow: Instrumentation Options. ! (line 237) * fsanitize=float-divide-by-zero: Instrumentation Options. ! (line 231) * fsanitize=integer-divide-by-zero: Instrumentation Options. ! (line 169) * fsanitize=kernel-address: Instrumentation Options. ! (line 135) * fsanitize=leak: Instrumentation Options. ! (line 148) * fsanitize=nonnull-attribute: Instrumentation Options. ! (line 245) * fsanitize=null: Instrumentation Options. ! (line 183) * fsanitize=object-size: Instrumentation Options. ! (line 226) * fsanitize=return: Instrumentation Options. ! (line 191) * fsanitize=returns-nonnull-attribute: Instrumentation Options. ! (line 251) * fsanitize=shift: Instrumentation Options. ! (line 163) * fsanitize=signed-integer-overflow: Instrumentation Options. ! (line 197) * fsanitize=thread: Instrumentation Options. ! (line 139) * fsanitize=undefined: Instrumentation Options. ! (line 158) * fsanitize=unreachable: Instrumentation Options. ! (line 173) * fsanitize=vla-bound: Instrumentation Options. ! (line 179) * fsanitize=vptr: Instrumentation Options. ! (line 268) ! * fsched-critical-path-heuristic: Optimize Options. (line 815) ! * fsched-dep-count-heuristic: Optimize Options. (line 842) ! * fsched-group-heuristic: Optimize Options. (line 809) ! * fsched-last-insn-heuristic: Optimize Options. (line 835) ! * fsched-pressure: Optimize Options. (line 760) ! * fsched-rank-heuristic: Optimize Options. (line 828) ! * fsched-spec-insn-heuristic: Optimize Options. (line 821) ! * fsched-spec-load: Optimize Options. (line 769) ! * fsched-spec-load-dangerous: Optimize Options. (line 774) ! * fsched-stalled-insns: Optimize Options. (line 780) ! * fsched-stalled-insns-dep: Optimize Options. (line 790) ! * fsched-verbose: Developer Options. (line 636) ! * fsched2-use-superblocks: Optimize Options. (line 799) ! * fschedule-fusion: Optimize Options. (line 2214) ! * fschedule-insns: Optimize Options. (line 731) ! * fschedule-insns2: Optimize Options. (line 741) ! * fsection-anchors: Optimize Options. (line 2300) ! * fsel-sched-pipelining: Optimize Options. (line 862) ! * fsel-sched-pipelining-outer-loops: Optimize Options. (line 867) ! * fselective-scheduling: Optimize Options. (line 854) ! * fselective-scheduling2: Optimize Options. (line 858) ! * fsemantic-interposition: Optimize Options. (line 872) ! * fshort-enums: Code Gen Options. (line 203) ! * fshort-enums <1>: Structures unions enumerations and bit-fields implementation. ! (line 48) * fshort-enums <2>: Common Type Attributes. ! (line 192) ! * fshort-enums <3>: Non-bugs. (line 42) * fshort-wchar: Code Gen Options. (line 213) ! * fshrink-wrap: Optimize Options. (line 889) ! * fsignaling-nans: Optimize Options. (line 2116) ! * fsigned-bitfields: C Dialect Options. (line 392) * fsigned-bitfields <1>: Non-bugs. (line 57) ! * fsigned-char: C Dialect Options. (line 382) * fsigned-char <1>: Characters implementation. (line 31) ! * fsimd-cost-model: Optimize Options. (line 1292) ! * fsingle-precision-constant: Optimize Options. (line 2131) * fsized-deallocation: C++ Dialect Options. ! (line 280) ! * fsplit-ivs-in-unroller: Optimize Options. (line 1313) ! * fsplit-paths: Optimize Options. (line 1308) ! * fsplit-stack: Instrumentation Options. ! (line 531) * fsplit-stack <1>: Common Function Attributes. ! (line 525) ! * fsplit-wide-types: Optimize Options. (line 440) ! * fssa-backprop: Optimize Options. (line 1057) ! * fssa-phiopt: Optimize Options. (line 1063) ! * fsso-struct: C Dialect Options. (line 398) * fstack-check: Instrumentation Options. ! (line 476) * fstack-limit-register: Instrumentation Options. ! (line 514) * fstack-limit-symbol: Instrumentation Options. ! (line 514) * fstack-protector: Instrumentation Options. ! (line 455) * fstack-protector-all: Instrumentation Options. ! (line 464) * fstack-protector-explicit: Instrumentation Options. ! (line 472) * fstack-protector-strong: Instrumentation Options. ! (line 467) ! * fstack-usage: Developer Options. (line 905) * fstack_reuse: Code Gen Options. (line 15) ! * fstats: Developer Options. (line 934) ! * fstdarg-opt: Optimize Options. (line 2296) ! * fstrict-aliasing: Optimize Options. (line 1426) * fstrict-enums: C++ Dialect Options. ! (line 290) ! * fstrict-overflow: Optimize Options. (line 1472) ! * fstrict-volatile-bitfields: Code Gen Options. (line 485) ! * fsync-libcalls: Code Gen Options. (line 517) * fsyntax-only: Warning Options. (line 14) * ftabstop: Preprocessor Options. ! (line 520) * ftemplate-backtrace-limit: C++ Dialect Options. ! (line 299) * ftemplate-depth: C++ Dialect Options. ! (line 303) * ftest-coverage: Instrumentation Options. ! (line 86) ! * fthread-jumps: Optimize Options. (line 431) ! * ftime-report: Developer Options. (line 866) ! * ftls-model: Code Gen Options. (line 409) ! * ftracer: Optimize Options. (line 2222) * ftrack-macro-expansion: Preprocessor Options. (line 535) ! * ftrapv: Code Gen Options. (line 91) ! * ftree-bit-ccp: Optimize Options. (line 1046) ! * ftree-builtin-call-dce: Optimize Options. (line 1084) ! * ftree-ccp: Optimize Options. (line 1052) ! * ftree-ch: Optimize Options. (line 1104) ! * ftree-coalesce-vars: Optimize Options. (line 1145) ! * ftree-copy-prop: Optimize Options. (line 960) ! * ftree-dce: Optimize Options. (line 1080) ! * ftree-dominator-opts: Optimize Options. (line 1090) ! * ftree-dse: Optimize Options. (line 1097) ! * ftree-forwprop: Optimize Options. (line 939) ! * ftree-fre: Optimize Options. (line 943) ! * ftree-loop-distribute-patterns: Optimize Options. (line 1192) ! * ftree-loop-distribution: Optimize Options. (line 1175) ! * ftree-loop-if-convert: Optimize Options. (line 1155) ! * ftree-loop-if-convert-stores: Optimize Options. (line 1162) ! * ftree-loop-im: Optimize Options. (line 1212) ! * ftree-loop-ivcanon: Optimize Options. (line 1221) ! * ftree-loop-linear: Optimize Options. (line 1119) ! * ftree-loop-optimize: Optimize Options. (line 1111) ! * ftree-loop-vectorize: Optimize Options. (line 1270) ! * ftree-parallelize-loops: Optimize Options. (line 1232) ! * ftree-partial-pre: Optimize Options. (line 935) ! * ftree-phiprop: Optimize Options. (line 950) ! * ftree-pre: Optimize Options. (line 931) ! * ftree-pta: Optimize Options. (line 1241) ! * ftree-reassoc: Optimize Options. (line 927) ! * ftree-sink: Optimize Options. (line 1042) ! * ftree-slp-vectorize: Optimize Options. (line 1274) ! * ftree-slsr: Optimize Options. (line 1259) ! * ftree-sra: Optimize Options. (line 1245) ! * ftree-switch-conversion: Optimize Options. (line 1067) ! * ftree-tail-merge: Optimize Options. (line 1072) ! * ftree-ter: Optimize Options. (line 1251) ! * ftree-vectorize: Optimize Options. (line 1265) ! * ftree-vrp: Optimize Options. (line 1299) ! * funconstrained-commons: Optimize Options. (line 529) ! * funit-at-a-time: Optimize Options. (line 1569) ! * funroll-all-loops: Optimize Options. (line 2239) ! * funroll-loops: Optimize Options. (line 2229) ! * funsafe-loop-optimizations: Optimize Options. (line 521) ! * funsafe-math-optimizations: Optimize Options. (line 2014) ! * funsigned-bitfields: C Dialect Options. (line 392) ! * funsigned-bitfields <1>: Structures unions enumerations and bit-fields implementation. (line 17) ! * funsigned-bitfields <2>: Non-bugs. (line 57) ! * funsigned-char: C Dialect Options. (line 364) * funsigned-char <1>: Characters implementation. (line 31) ! * funswitch-loops: Optimize Options. (line 2257) * funwind-tables: Code Gen Options. (line 141) * fuse-cxa-atexit: C++ Dialect Options. ! (line 318) * fuse-ld=bfd: Link Options. (line 25) * fuse-ld=gold: Link Options. (line 28) ! * fuse-linker-plugin: Optimize Options. (line 1829) ! * fvar-tracking: Debugging Options. (line 148) ! * fvar-tracking-assignments: Debugging Options. (line 158) ! * fvar-tracking-assignments-toggle: Developer Options. (line 858) ! * fvariable-expansion-in-unroller: Optimize Options. (line 1327) ! * fvect-cost-model: Optimize Options. (line 1278) ! * fverbose-asm: Code Gen Options. (line 252) ! * fvisibility: Code Gen Options. (line 420) * fvisibility-inlines-hidden: C++ Dialect Options. ! (line 330) * fvisibility-ms-compat: C++ Dialect Options. ! (line 358) ! * fvpt: Optimize Options. (line 2194) * fvtable-verify: Instrumentation Options. ! (line 549) * fvtv-counts: Instrumentation Options. ! (line 585) * fvtv-debug: Instrumentation Options. ! (line 572) ! * fweb: Optimize Options. (line 1588) ! * fwhole-program: Optimize Options. (line 1599) * fwide-exec-charset: Preprocessor Options. (line 558) * fworking-directory: Preprocessor Options. (line 576) ! * fwrapv: Code Gen Options. (line 99) * fzero-link: Objective-C and Objective-C++ Dialect Options. (line 141) ! * g: Debugging Options. (line 25) * G: M32R/D Options. (line 57) ! * G <1>: MIPS Options. (line 437) ! * G <2>: Nios II Options. (line 9) ! * G <3>: RS/6000 and PowerPC Options. ! (line 832) ! * G <4>: System V Options. (line 10) ! * gcoff: Debugging Options. (line 78) ! * gdwarf: Debugging Options. (line 45) * gen-decls: Objective-C and Objective-C++ Dialect Options. (line 167) * gfull: Darwin Options. (line 69) ! * ggdb: Debugging Options. (line 38) ! * ggnu-pubnames: Debugging Options. (line 179) ! * gno-record-gcc-switches: Debugging Options. (line 194) ! * gno-strict-dwarf: Debugging Options. (line 209) ! * gpubnames: Debugging Options. (line 176) ! * grecord-gcc-switches: Debugging Options. (line 194) ! * gsplit-dwarf: Debugging Options. (line 169) ! * gstabs: Debugging Options. (line 64) ! * gstabs+: Debugging Options. (line 72) ! * gstrict-dwarf: Debugging Options. (line 203) ! * gtoggle: Developer Options. (line 850) * gused: Darwin Options. (line 64) ! * gvms: Debugging Options. (line 96) ! * gxcoff: Debugging Options. (line 83) ! * gxcoff+: Debugging Options. (line 88) ! * gz: Debugging Options. (line 213) * H: Preprocessor Options. ! (line 706) * headerpad_max_install_names: Darwin Options. (line 196) - * help: Overall Options. (line 207) * help <1>: Preprocessor Options. ! (line 698) * I: Preprocessor Options. (line 77) ! * I <1>: Directory Options. (line 10) * I-: Preprocessor Options. ! (line 389) ! * I- <1>: Directory Options. (line 112) * idirafter: Preprocessor Options. ! (line 431) * iframework: Darwin Options. (line 57) * imacros: Preprocessor Options. ! (line 422) * image_base: Darwin Options. (line 196) * imultilib: Preprocessor Options. ! (line 456) * include: Preprocessor Options. ! (line 411) * init: Darwin Options. (line 196) * install_name: Darwin Options. (line 196) ! * iplugindir=: Directory Options. (line 29) * iprefix: Preprocessor Options. ! (line 438) * iquote: Preprocessor Options. ! (line 468) ! * iquote <1>: Directory Options. (line 34) * isysroot: Preprocessor Options. ! (line 450) * isystem: Preprocessor Options. ! (line 460) * iwithprefix: Preprocessor Options. ! (line 444) * iwithprefixbefore: Preprocessor Options. ! (line 444) * keep_private_externs: Darwin Options. (line 196) * l: Link Options. (line 32) - * L: Directory Options. (line 40) * lobjc: Link Options. (line 59) * M: Preprocessor Options. (line 185) - * m: RS/6000 and PowerPC Options. - (line 674) * m1: SH Options. (line 9) * m10: PDP-11 Options. (line 29) ! * m128bit-long-double: x86 Options. (line 415) ! * m16: x86 Options. (line 1116) ! * m16-bit: CRIS Options. (line 64) * m16-bit <1>: NDS32 Options. (line 39) * m1reg-: Adapteva Epiphany Options. ! (line 131) * m2: SH Options. (line 12) * m210: MCore Options. (line 43) * m2a: SH Options. (line 30) --- 52139,52532 ---- (line 111) * fobjc-std: Objective-C and Objective-C++ Dialect Options. (line 120) ! * fomit-frame-pointer: Optimize Options. (line 218) ! * fopenacc: C Dialect Options. (line 263) * fopenacc-dim: C Dialect Options. (line 271) * fopenmp: C Dialect Options. (line 277) ! * fopenmp-simd: C Dialect Options. (line 285) ! * fopt-info: Developer Options. (line 563) ! * foptimize-sibling-calls: Optimize Options. (line 239) ! * foptimize-strlen: Optimize Options. (line 244) * force_cpusubtype_ALL: Darwin Options. (line 135) * force_flat_namespace: Darwin Options. (line 196) ! * fpack-struct: Code Gen Options. (line 387) ! * fpartial-inlining: Optimize Options. (line 1337) * fpcc-struct-return <1>: Incompatibilities. (line 170) + * fpcc-struct-return: Code Gen Options. (line 167) * fpch-deps: Preprocessor Options. ! (line 294) * fpch-preprocess: Preprocessor Options. ! (line 302) ! * fpeel-loops: Optimize Options. (line 2251) * fpermissive: C++ Dialect Options. ! (line 249) ! * fPIC: Code Gen Options. (line 295) ! * fpic: Code Gen Options. (line 274) ! * fPIE: Code Gen Options. (line 308) ! * fpie: Code Gen Options. (line 308) ! * fplan9-extensions <1>: Unnamed Fields. (line 44) ! * fplan9-extensions: C Dialect Options. (line 332) * fplugin: Overall Options. (line 356) ! * fplugin-arg: Overall Options. (line 364) ! * fpost-ipa-mem-report: Developer Options. (line 923) ! * fpre-ipa-mem-report: Developer Options. (line 921) ! * fpredictive-commoning: Optimize Options. (line 1344) ! * fprefetch-loop-arrays: Optimize Options. (line 1351) * fpreprocessed: Preprocessor Options. ! (line 506) ! * fprofile-arcs <1>: Other Builtins. (line 362) * fprofile-arcs: Instrumentation Options. (line 31) ! * fprofile-correction: Optimize Options. (line 1892) * fprofile-dir: Instrumentation Options. ! (line 96) * fprofile-generate: Instrumentation Options. (line 106) ! * fprofile-reorder-functions: Optimize Options. (line 2193) ! * fprofile-report: Developer Options. (line 927) ! * fprofile-use: Optimize Options. (line 1900) ! * fprofile-values: Optimize Options. (line 2184) * fpu: RX Options. (line 17) ! * fpud: ARC Options. (line 163) ! * fpud_all: ARC Options. (line 219) ! * fpud_div: ARC Options. (line 199) ! * fpud_fma: ARC Options. (line 209) ! * fpuda: ARC Options. (line 168) ! * fpuda_all: ARC Options. (line 188) ! * fpuda_div: ARC Options. (line 174) ! * fpuda_fma: ARC Options. (line 181) ! * fpus: ARC Options. (line 159) ! * fpus_all: ARC Options. (line 215) ! * fpus_div: ARC Options. (line 195) ! * fpus_fma: ARC Options. (line 205) ! * frandom-seed: Developer Options. (line 747) ! * freciprocal-math: Optimize Options. (line 2055) ! * frecord-gcc-switches: Code Gen Options. (line 262) ! * free: Optimize Options. (line 637) * freg-struct-return: Code Gen Options. (line 185) ! * frename-registers: Optimize Options. (line 2210) ! * freorder-blocks: Optimize Options. (line 1388) ! * freorder-blocks-algorithm: Optimize Options. (line 1394) ! * freorder-blocks-and-partition: Optimize Options. (line 1405) ! * freorder-functions: Optimize Options. (line 1418) * freplace-objc-classes: Objective-C and Objective-C++ Dialect Options. (line 131) * frepo <1>: Template Instantiation. (line 94) + * frepo: C++ Dialect Options. + (line 266) * freport-bug: Developer Options. (line 256) ! * frerun-cse-after-loop: Optimize Options. (line 469) ! * freschedule-modulo-scheduled-loops: Optimize Options. (line 854) ! * frounding-math: Optimize Options. (line 2101) * fsanitize-coverage=trace-pc: Instrumentation Options. ! (line 323) * fsanitize-recover: Instrumentation Options. ! (line 288) * fsanitize-sections: Instrumentation Options. ! (line 284) * fsanitize-undefined-trap-on-error: Instrumentation Options. ! (line 316) * fsanitize=address: Instrumentation Options. ! (line 122) * fsanitize=alignment: Instrumentation Options. ! (line 218) * fsanitize=bool: Instrumentation Options. ! (line 254) * fsanitize=bounds: Instrumentation Options. ! (line 205) * fsanitize=bounds-strict: Instrumentation Options. ! (line 211) * fsanitize=enum: Instrumentation Options. ! (line 258) * fsanitize=float-cast-overflow: Instrumentation Options. ! (line 235) * fsanitize=float-divide-by-zero: Instrumentation Options. ! (line 229) * fsanitize=integer-divide-by-zero: Instrumentation Options. ! (line 168) * fsanitize=kernel-address: Instrumentation Options. ! (line 134) * fsanitize=leak: Instrumentation Options. ! (line 147) * fsanitize=nonnull-attribute: Instrumentation Options. ! (line 243) * fsanitize=null: Instrumentation Options. ! (line 182) * fsanitize=object-size: Instrumentation Options. ! (line 224) * fsanitize=return: Instrumentation Options. ! (line 190) * fsanitize=returns-nonnull-attribute: Instrumentation Options. ! (line 249) * fsanitize=shift: Instrumentation Options. ! (line 162) * fsanitize=signed-integer-overflow: Instrumentation Options. ! (line 196) * fsanitize=thread: Instrumentation Options. ! (line 138) * fsanitize=undefined: Instrumentation Options. ! (line 157) * fsanitize=unreachable: Instrumentation Options. ! (line 172) * fsanitize=vla-bound: Instrumentation Options. ! (line 178) * fsanitize=vptr: Instrumentation Options. ! (line 263) ! * fsched-critical-path-heuristic: Optimize Options. (line 820) ! * fsched-dep-count-heuristic: Optimize Options. (line 847) ! * fsched-group-heuristic: Optimize Options. (line 814) ! * fsched-last-insn-heuristic: Optimize Options. (line 840) ! * fsched-pressure: Optimize Options. (line 765) ! * fsched-rank-heuristic: Optimize Options. (line 833) ! * fsched-spec-insn-heuristic: Optimize Options. (line 826) ! * fsched-spec-load: Optimize Options. (line 774) ! * fsched-spec-load-dangerous: Optimize Options. (line 779) ! * fsched-stalled-insns: Optimize Options. (line 785) ! * fsched-stalled-insns-dep: Optimize Options. (line 795) ! * fsched-verbose: Developer Options. (line 662) ! * fsched2-use-superblocks: Optimize Options. (line 804) ! * fschedule-fusion: Optimize Options. (line 2220) ! * fschedule-insns: Optimize Options. (line 736) ! * fschedule-insns2: Optimize Options. (line 746) ! * fsection-anchors: Optimize Options. (line 2306) ! * fsel-sched-pipelining: Optimize Options. (line 867) ! * fsel-sched-pipelining-outer-loops: Optimize Options. (line 872) ! * fselective-scheduling: Optimize Options. (line 859) ! * fselective-scheduling2: Optimize Options. (line 863) ! * fsemantic-interposition: Optimize Options. (line 877) ! * fshort-enums <1>: Non-bugs. (line 42) * fshort-enums <2>: Common Type Attributes. ! (line 193) ! * fshort-enums <3>: Structures unions enumerations and bit-fields implementation. ! (line 48) ! * fshort-enums: Code Gen Options. (line 203) * fshort-wchar: Code Gen Options. (line 213) ! * fshrink-wrap: Optimize Options. (line 894) ! * fsignaling-nans: Optimize Options. (line 2121) * fsigned-bitfields <1>: Non-bugs. (line 57) ! * fsigned-bitfields: C Dialect Options. (line 391) * fsigned-char <1>: Characters implementation. (line 31) ! * fsigned-char: C Dialect Options. (line 381) ! * fsimd-cost-model: Optimize Options. (line 1297) ! * fsingle-precision-constant: Optimize Options. (line 2136) * fsized-deallocation: C++ Dialect Options. ! (line 281) ! * fsplit-ivs-in-unroller: Optimize Options. (line 1318) ! * fsplit-paths: Optimize Options. (line 1313) * fsplit-stack <1>: Common Function Attributes. ! (line 529) ! * fsplit-stack: Instrumentation Options. ! (line 526) ! * fsplit-wide-types: Optimize Options. (line 444) ! * fssa-backprop: Optimize Options. (line 1062) ! * fssa-phiopt: Optimize Options. (line 1068) ! * fsso-struct: C Dialect Options. (line 397) * fstack-check: Instrumentation Options. ! (line 470) * fstack-limit-register: Instrumentation Options. ! (line 509) * fstack-limit-symbol: Instrumentation Options. ! (line 509) * fstack-protector: Instrumentation Options. ! (line 449) * fstack-protector-all: Instrumentation Options. ! (line 458) * fstack-protector-explicit: Instrumentation Options. ! (line 466) * fstack-protector-strong: Instrumentation Options. ! (line 461) ! * fstack-usage: Developer Options. (line 931) * fstack_reuse: Code Gen Options. (line 15) ! * fstats: Developer Options. (line 962) ! * fstdarg-opt: Optimize Options. (line 2302) ! * fstrict-aliasing: Optimize Options. (line 1431) * fstrict-enums: C++ Dialect Options. ! (line 291) ! * fstrict-overflow: Optimize Options. (line 1477) ! * fstrict-volatile-bitfields: Code Gen Options. (line 487) ! * fsync-libcalls: Code Gen Options. (line 520) * fsyntax-only: Warning Options. (line 14) * ftabstop: Preprocessor Options. ! (line 519) * ftemplate-backtrace-limit: C++ Dialect Options. ! (line 300) * ftemplate-depth: C++ Dialect Options. ! (line 304) * ftest-coverage: Instrumentation Options. ! (line 87) ! * fthread-jumps: Optimize Options. (line 435) ! * ftime-report: Developer Options. (line 891) ! * ftls-model: Code Gen Options. (line 411) ! * ftracer: Optimize Options. (line 2228) * ftrack-macro-expansion: Preprocessor Options. (line 535) ! * ftrapv: Code Gen Options. (line 90) ! * ftree-bit-ccp: Optimize Options. (line 1051) ! * ftree-builtin-call-dce: Optimize Options. (line 1089) ! * ftree-ccp: Optimize Options. (line 1057) ! * ftree-ch: Optimize Options. (line 1109) ! * ftree-coalesce-vars: Optimize Options. (line 1150) ! * ftree-copy-prop: Optimize Options. (line 965) ! * ftree-dce: Optimize Options. (line 1085) ! * ftree-dominator-opts: Optimize Options. (line 1095) ! * ftree-dse: Optimize Options. (line 1102) ! * ftree-forwprop: Optimize Options. (line 944) ! * ftree-fre: Optimize Options. (line 948) ! * ftree-loop-distribute-patterns: Optimize Options. (line 1197) ! * ftree-loop-distribution: Optimize Options. (line 1180) ! * ftree-loop-if-convert: Optimize Options. (line 1160) ! * ftree-loop-if-convert-stores: Optimize Options. (line 1167) ! * ftree-loop-im: Optimize Options. (line 1217) ! * ftree-loop-ivcanon: Optimize Options. (line 1226) ! * ftree-loop-linear: Optimize Options. (line 1124) ! * ftree-loop-optimize: Optimize Options. (line 1116) ! * ftree-loop-vectorize: Optimize Options. (line 1275) ! * ftree-parallelize-loops: Optimize Options. (line 1237) ! * ftree-partial-pre: Optimize Options. (line 940) ! * ftree-phiprop: Optimize Options. (line 955) ! * ftree-pre: Optimize Options. (line 936) ! * ftree-pta: Optimize Options. (line 1246) ! * ftree-reassoc: Optimize Options. (line 932) ! * ftree-sink: Optimize Options. (line 1047) ! * ftree-slp-vectorize: Optimize Options. (line 1279) ! * ftree-slsr: Optimize Options. (line 1264) ! * ftree-sra: Optimize Options. (line 1250) ! * ftree-switch-conversion: Optimize Options. (line 1072) ! * ftree-tail-merge: Optimize Options. (line 1077) ! * ftree-ter: Optimize Options. (line 1256) ! * ftree-vectorize: Optimize Options. (line 1270) ! * ftree-vrp: Optimize Options. (line 1304) ! * funconstrained-commons: Optimize Options. (line 533) ! * funit-at-a-time: Optimize Options. (line 1574) ! * funroll-all-loops: Optimize Options. (line 2245) ! * funroll-loops: Optimize Options. (line 2235) ! * funsafe-loop-optimizations: Optimize Options. (line 525) ! * funsafe-math-optimizations: Optimize Options. (line 2022) ! * funsigned-bitfields <1>: Non-bugs. (line 57) ! * funsigned-bitfields <2>: Structures unions enumerations and bit-fields implementation. (line 17) ! * funsigned-bitfields: C Dialect Options. (line 391) * funsigned-char <1>: Characters implementation. (line 31) ! * funsigned-char: C Dialect Options. (line 363) ! * funswitch-loops: Optimize Options. (line 2263) * funwind-tables: Code Gen Options. (line 141) * fuse-cxa-atexit: C++ Dialect Options. ! (line 319) * fuse-ld=bfd: Link Options. (line 25) * fuse-ld=gold: Link Options. (line 28) ! * fuse-linker-plugin: Optimize Options. (line 1836) ! * fvar-tracking: Debugging Options. (line 149) ! * fvar-tracking-assignments: Debugging Options. (line 159) ! * fvar-tracking-assignments-toggle: Developer Options. (line 883) ! * fvariable-expansion-in-unroller: Optimize Options. (line 1332) ! * fvect-cost-model: Optimize Options. (line 1283) ! * fverbose-asm: Code Gen Options. (line 253) ! * fvisibility: Code Gen Options. (line 422) * fvisibility-inlines-hidden: C++ Dialect Options. ! (line 331) * fvisibility-ms-compat: C++ Dialect Options. ! (line 359) ! * fvpt: Optimize Options. (line 2200) * fvtable-verify: Instrumentation Options. ! (line 544) * fvtv-counts: Instrumentation Options. ! (line 580) * fvtv-debug: Instrumentation Options. ! (line 567) ! * fweb: Optimize Options. (line 1593) ! * fwhole-program: Optimize Options. (line 1604) * fwide-exec-charset: Preprocessor Options. (line 558) * fworking-directory: Preprocessor Options. (line 576) ! * fwrapv: Code Gen Options. (line 98) * fzero-link: Objective-C and Objective-C++ Dialect Options. (line 141) ! * G <1>: System V Options. (line 10) ! * G <2>: RS/6000 and PowerPC Options. ! (line 809) ! * G <3>: Nios II Options. (line 9) ! * G <4>: MIPS Options. (line 440) * G: M32R/D Options. (line 57) ! * g: Debugging Options. (line 26) ! * gcoff: Debugging Options. (line 79) ! * gdwarf: Debugging Options. (line 46) * gen-decls: Objective-C and Objective-C++ Dialect Options. (line 167) * gfull: Darwin Options. (line 69) ! * ggdb: Debugging Options. (line 39) ! * ggnu-pubnames: Debugging Options. (line 180) ! * gno-record-gcc-switches: Debugging Options. (line 196) ! * gno-strict-dwarf: Debugging Options. (line 211) ! * gpubnames: Debugging Options. (line 177) ! * grecord-gcc-switches: Debugging Options. (line 196) ! * gsplit-dwarf: Debugging Options. (line 170) ! * gstabs: Debugging Options. (line 65) ! * gstabs+: Debugging Options. (line 73) ! * gstrict-dwarf: Debugging Options. (line 205) ! * gtoggle: Developer Options. (line 875) * gused: Darwin Options. (line 64) ! * gvms: Debugging Options. (line 97) ! * gxcoff: Debugging Options. (line 84) ! * gxcoff+: Debugging Options. (line 89) ! * gz: Debugging Options. (line 215) * H: Preprocessor Options. ! (line 709) * headerpad_max_install_names: Darwin Options. (line 196) * help <1>: Preprocessor Options. ! (line 701) ! * help: Overall Options. (line 207) ! * I <1>: Directory Options. (line 10) * I: Preprocessor Options. (line 77) ! * I- <1>: Directory Options. (line 114) * I-: Preprocessor Options. ! (line 387) * idirafter: Preprocessor Options. ! (line 429) * iframework: Darwin Options. (line 57) * imacros: Preprocessor Options. ! (line 420) * image_base: Darwin Options. (line 196) * imultilib: Preprocessor Options. ! (line 454) * include: Preprocessor Options. ! (line 409) * init: Darwin Options. (line 196) * install_name: Darwin Options. (line 196) ! * iplugindir=: Directory Options. (line 31) * iprefix: Preprocessor Options. ! (line 436) ! * iquote <1>: Directory Options. (line 36) * iquote: Preprocessor Options. ! (line 466) * isysroot: Preprocessor Options. ! (line 448) * isystem: Preprocessor Options. ! (line 458) * iwithprefix: Preprocessor Options. ! (line 442) * iwithprefixbefore: Preprocessor Options. ! (line 442) * keep_private_externs: Darwin Options. (line 196) + * L: Directory Options. (line 42) * l: Link Options. (line 32) * lobjc: Link Options. (line 59) + * m: RS/6000 and PowerPC Options. + (line 650) * M: Preprocessor Options. (line 185) * m1: SH Options. (line 9) * m10: PDP-11 Options. (line 29) ! * m128bit-long-double: x86 Options. (line 422) ! * m16: x86 Options. (line 1125) * m16-bit <1>: NDS32 Options. (line 39) + * m16-bit: CRIS Options. (line 64) * m1reg-: Adapteva Epiphany Options. ! (line 132) * m2: SH Options. (line 12) * m210: MCore Options. (line 43) * m2a: SH Options. (line 30) *************** look up both forms. *** 51941,51962 **** * m2a-single-only: SH Options. (line 22) * m3: SH Options. (line 34) * m31: S/390 and zSeries Options. ! (line 86) ! * m32: Nvidia PTX Options. (line 10) ! * m32 <1>: RS/6000 and PowerPC Options. ! (line 367) ! * m32 <2>: SPARC Options. (line 277) * m32 <3>: TILE-Gx Options. (line 23) ! * m32 <4>: TILEPro Options. (line 13) ! * m32 <5>: x86 Options. (line 1116) * m32-bit: CRIS Options. (line 64) - * m32bit-doubles: RL78 Options. (line 73) * m32bit-doubles <1>: RX Options. (line 10) * m32r: M32R/D Options. (line 15) * m32r2: M32R/D Options. (line 9) * m32rx: M32R/D Options. (line 12) * m340: MCore Options. (line 43) ! * m3dnow: x86 Options. (line 633) * m3e: SH Options. (line 37) * m4: SH Options. (line 51) * m4-100: SH Options. (line 54) --- 52535,52556 ---- * m2a-single-only: SH Options. (line 22) * m3: SH Options. (line 34) * m31: S/390 and zSeries Options. ! (line 87) ! * m32 <1>: x86 Options. (line 1125) ! * m32 <2>: TILEPro Options. (line 13) * m32 <3>: TILE-Gx Options. (line 23) ! * m32 <4>: SPARC Options. (line 280) ! * m32 <5>: RS/6000 and PowerPC Options. ! (line 342) ! * m32: Nvidia PTX Options. (line 10) * m32-bit: CRIS Options. (line 64) * m32bit-doubles <1>: RX Options. (line 10) + * m32bit-doubles: RL78 Options. (line 73) * m32r: M32R/D Options. (line 15) * m32r2: M32R/D Options. (line 9) * m32rx: M32R/D Options. (line 12) * m340: MCore Options. (line 43) ! * m3dnow: x86 Options. (line 639) * m3e: SH Options. (line 37) * m4: SH Options. (line 51) * m4-100: SH Options. (line 54) *************** look up both forms. *** 51984,52081 **** * m4a-single-only: SH Options. (line 110) * m4al: SH Options. (line 121) * m4byte-functions: MCore Options. (line 27) ! * m5200: M680x0 Options. (line 144) ! * m5206e: M680x0 Options. (line 153) ! * m528x: M680x0 Options. (line 157) ! * m5307: M680x0 Options. (line 161) ! * m5407: M680x0 Options. (line 165) * m64: Nvidia PTX Options. (line 10) - * m64 <1>: RS/6000 and PowerPC Options. - (line 367) - * m64 <2>: S/390 and zSeries Options. - (line 86) - * m64 <3>: SPARC Options. (line 277) - * m64 <4>: TILE-Gx Options. (line 23) - * m64 <5>: x86 Options. (line 1116) - * m64bit-doubles: RL78 Options. (line 73) * m64bit-doubles <1>: RX Options. (line 10) ! * m68000: M680x0 Options. (line 93) ! * m68010: M680x0 Options. (line 101) ! * m68020: M680x0 Options. (line 107) ! * m68020-40: M680x0 Options. (line 175) ! * m68020-60: M680x0 Options. (line 184) ! * m68030: M680x0 Options. (line 112) ! * m68040: M680x0 Options. (line 117) ! * m68060: M680x0 Options. (line 126) ! * m68881: M680x0 Options. (line 194) * m8-bit: CRIS Options. (line 64) ! * m8bit-idiv: x86 Options. (line 1086) * m8byte-align: V850 Options. (line 170) ! * m96bit-long-double: x86 Options. (line 415) * mA6: ARC Options. (line 19) ! * mA7: ARC Options. (line 29) ! * mabi: AArch64 Options. (line 9) ! * mabi <1>: ARM Options. (line 9) * mabi <2>: RS/6000 and PowerPC Options. ! (line 701) ! * mabi <3>: x86 Options. (line 821) ! * mabi=32: MIPS Options. (line 155) ! * mabi=64: MIPS Options. (line 155) ! * mabi=eabi: MIPS Options. (line 155) * mabi=elfv1: RS/6000 and PowerPC Options. ! (line 722) * mabi=elfv2: RS/6000 and PowerPC Options. ! (line 728) * mabi=gnu: MMIX Options. (line 20) * mabi=ibmlongdouble: RS/6000 and PowerPC Options. ! (line 714) * mabi=ieeelongdouble: RS/6000 and PowerPC Options. ! (line 718) * mabi=mmixware: MMIX Options. (line 20) ! * mabi=n32: MIPS Options. (line 155) * mabi=no-spe: RS/6000 and PowerPC Options. ! (line 711) ! * mabi=o64: MIPS Options. (line 155) * mabi=spe: RS/6000 and PowerPC Options. ! (line 706) ! * mabicalls: MIPS Options. (line 191) ! * mabm: x86 Options. (line 635) ! * mabort-on-noreturn: ARM Options. (line 198) ! * mabs=2008: MIPS Options. (line 299) ! * mabs=legacy: MIPS Options. (line 299) * mabsdiff: MeP Options. (line 7) * mabshi: PDP-11 Options. (line 55) * mac0: PDP-11 Options. (line 16) ! * macc-4: FRV Options. (line 139) ! * macc-8: FRV Options. (line 143) ! * maccumulate-args: AVR Options. (line 150) ! * maccumulate-outgoing-args: SH Options. (line 314) ! * maccumulate-outgoing-args <1>: x86 Options. (line 844) ! * maddress-mode=long: x86 Options. (line 1166) ! * maddress-mode=short: x86 Options. (line 1171) ! * maddress-space-conversion: SPU Options. (line 68) * mads: RS/6000 and PowerPC Options. ! (line 756) ! * maes: x86 Options. (line 622) * maix-struct-return: RS/6000 and PowerPC Options. ! (line 694) * maix32: RS/6000 and PowerPC Options. ! (line 405) * maix64: RS/6000 and PowerPC Options. ! (line 405) * malign-300: H8/300 Options. (line 41) ! * malign-call: ARC Options. (line 317) ! * malign-data: x86 Options. (line 455) ! * malign-double: x86 Options. (line 400) ! * malign-int: M680x0 Options. (line 263) ! * malign-labels: FRV Options. (line 128) * malign-loops: M32R/D Options. (line 73) * malign-natural: RS/6000 and PowerPC Options. ! (line 443) * malign-power: RS/6000 and PowerPC Options. ! (line 443) * mall-opts: MeP Options. (line 11) ! * malloc-cc: FRV Options. (line 31) * mallow-string-insns: RX Options. (line 150) * mallregs: RL78 Options. (line 66) * maltivec: RS/6000 and PowerPC Options. --- 52578,52675 ---- * m4a-single-only: SH Options. (line 110) * m4al: SH Options. (line 121) * m4byte-functions: MCore Options. (line 27) ! * m5200: M680x0 Options. (line 147) ! * m5206e: M680x0 Options. (line 156) ! * m528x: M680x0 Options. (line 160) ! * m5307: M680x0 Options. (line 164) ! * m5407: M680x0 Options. (line 168) ! * m64 <1>: x86 Options. (line 1125) ! * m64 <2>: TILE-Gx Options. (line 23) ! * m64 <3>: SPARC Options. (line 280) ! * m64 <4>: S/390 and zSeries Options. ! (line 87) ! * m64 <5>: RS/6000 and PowerPC Options. ! (line 342) * m64: Nvidia PTX Options. (line 10) * m64bit-doubles <1>: RX Options. (line 10) ! * m64bit-doubles: RL78 Options. (line 73) ! * m68000: M680x0 Options. (line 95) ! * m68010: M680x0 Options. (line 103) ! * m68020: M680x0 Options. (line 109) ! * m68020-40: M680x0 Options. (line 178) ! * m68020-60: M680x0 Options. (line 187) ! * m68030: M680x0 Options. (line 114) ! * m68040: M680x0 Options. (line 119) ! * m68060: M680x0 Options. (line 128) ! * m68881: M680x0 Options. (line 197) * m8-bit: CRIS Options. (line 64) ! * m8bit-idiv: x86 Options. (line 1093) * m8byte-align: V850 Options. (line 170) ! * m96bit-long-double: x86 Options. (line 422) * mA6: ARC Options. (line 19) ! * mA7: ARC Options. (line 32) ! * mabi <1>: x86 Options. (line 828) * mabi <2>: RS/6000 and PowerPC Options. ! (line 677) ! * mabi <3>: ARM Options. (line 9) ! * mabi: AArch64 Options. (line 9) ! * mabi=32: MIPS Options. (line 157) ! * mabi=64: MIPS Options. (line 157) ! * mabi=eabi: MIPS Options. (line 157) * mabi=elfv1: RS/6000 and PowerPC Options. ! (line 698) * mabi=elfv2: RS/6000 and PowerPC Options. ! (line 704) * mabi=gnu: MMIX Options. (line 20) * mabi=ibmlongdouble: RS/6000 and PowerPC Options. ! (line 690) * mabi=ieeelongdouble: RS/6000 and PowerPC Options. ! (line 694) * mabi=mmixware: MMIX Options. (line 20) ! * mabi=n32: MIPS Options. (line 157) * mabi=no-spe: RS/6000 and PowerPC Options. ! (line 687) ! * mabi=o64: MIPS Options. (line 157) * mabi=spe: RS/6000 and PowerPC Options. ! (line 682) ! * mabicalls: MIPS Options. (line 194) ! * mabm: x86 Options. (line 641) ! * mabort-on-noreturn: ARM Options. (line 199) ! * mabs=2008: MIPS Options. (line 302) ! * mabs=legacy: MIPS Options. (line 302) * mabsdiff: MeP Options. (line 7) * mabshi: PDP-11 Options. (line 55) * mac0: PDP-11 Options. (line 16) ! * macc-4: FRV Options. (line 113) ! * macc-8: FRV Options. (line 116) ! * maccumulate-args: AVR Options. (line 148) ! * maccumulate-outgoing-args <1>: x86 Options. (line 851) ! * maccumulate-outgoing-args: SH Options. (line 318) ! * maddress-mode=long: x86 Options. (line 1175) ! * maddress-mode=short: x86 Options. (line 1180) ! * maddress-space-conversion: SPU Options. (line 63) * mads: RS/6000 and PowerPC Options. ! (line 732) ! * maes: x86 Options. (line 628) * maix-struct-return: RS/6000 and PowerPC Options. ! (line 670) * maix32: RS/6000 and PowerPC Options. ! (line 380) * maix64: RS/6000 and PowerPC Options. ! (line 380) * malign-300: H8/300 Options. (line 41) ! * malign-call: ARC Options. (line 327) ! * malign-data: x86 Options. (line 461) ! * malign-double: x86 Options. (line 406) ! * malign-int: M680x0 Options. (line 267) ! * malign-labels: FRV Options. (line 104) * malign-loops: M32R/D Options. (line 73) * malign-natural: RS/6000 and PowerPC Options. ! (line 419) * malign-power: RS/6000 and PowerPC Options. ! (line 419) * mall-opts: MeP Options. (line 11) ! * malloc-cc: FRV Options. (line 25) * mallow-string-insns: RX Options. (line 150) * mallregs: RL78 Options. (line 66) * maltivec: RS/6000 and PowerPC Options. *************** look up both forms. *** 52088,52270 **** * mam33-2: MN10300 Options. (line 24) * mam34: MN10300 Options. (line 27) * mandroid: GNU/Linux Options. (line 26) ! * mannotate-align: ARC Options. (line 265) * mapcs: ARM Options. (line 21) * mapcs-frame: ARM Options. (line 13) - * mapp-regs: SPARC Options. (line 10) * mapp-regs <1>: V850 Options. (line 181) * mARC600: ARC Options. (line 19) ! * mARC601: ARC Options. (line 25) ! * mARC700: ARC Options. (line 29) ! * march: AArch64 Options. (line 94) ! * march <1>: ARM Options. (line 65) ! * march <2>: C6X Options. (line 7) ! * march <3>: CRIS Options. (line 10) ! * march <4>: HPPA Options. (line 9) ! * march <5>: HPPA Options. (line 155) * march <6>: M680x0 Options. (line 12) ! * march <7>: MIPS Options. (line 14) ! * march <8>: NDS32 Options. (line 52) ! * march <9>: Nios II Options. (line 70) ! * march <10>: S/390 and zSeries Options. ! (line 148) ! * march <11>: x86 Options. (line 9) ! * marclinux: ARC Options. (line 271) ! * marclinux_prof: ARC Options. (line 278) ! * margonaut: ARC Options. (line 465) ! * marm: ARM Options. (line 268) * mas100-syntax: RX Options. (line 76) * masm-hex: MSP430 Options. (line 9) * masm-syntax-unified: ARM Options. (line 363) ! * masm=DIALECT: x86 Options. (line 354) ! * matomic: ARC Options. (line 96) * matomic-model=MODEL: SH Options. (line 193) ! * matomic-updates: SPU Options. (line 83) * mauto-litpools: Xtensa Options. (line 60) ! * mauto-modify-reg: ARC Options. (line 320) * mauto-pic: IA-64 Options. (line 50) * maverage: MeP Options. (line 16) * mavoid-indexed-addresses: RS/6000 and PowerPC Options. ! (line 513) ! * mavx: x86 Options. (line 610) ! * mavx2: x86 Options. (line 611) ! * mavx256-split-unaligned-load: x86 Options. (line 1094) ! * mavx256-split-unaligned-store: x86 Options. (line 1094) ! * mavx512bw: x86 Options. (line 617) ! * mavx512cd: x86 Options. (line 615) ! * mavx512dq: x86 Options. (line 618) ! * mavx512er: x86 Options. (line 614) ! * mavx512f: x86 Options. (line 612) ! * mavx512ifma: x86 Options. (line 619) ! * mavx512pf: x86 Options. (line 613) ! * mavx512vbmi: x86 Options. (line 620) ! * mavx512vl: x86 Options. (line 616) * max-vect-align: Adapteva Epiphany Options. ! (line 119) * mb: SH Options. (line 126) * mbackchain: S/390 and zSeries Options. (line 35) * mbarrel-shift-enabled: LM32 Options. (line 9) * mbarrel-shifter: ARC Options. (line 10) ! * mbarrel_shifter: ARC Options. (line 483) ! * mbase-addresses: MMIX Options. (line 53) * mbased=: MeP Options. (line 20) ! * mbbit-peephole: ARC Options. (line 323) * mbcopy: PDP-11 Options. (line 36) * mbcopy-builtin: PDP-11 Options. (line 32) * mbig: RS/6000 and PowerPC Options. ! (line 593) ! * mbig-endian: AArch64 Options. (line 20) ! * mbig-endian <1>: ARC Options. (line 468) ! * mbig-endian <2>: ARM Options. (line 61) ! * mbig-endian <3>: C6X Options. (line 13) ! * mbig-endian <4>: IA-64 Options. (line 9) * mbig-endian <5>: MCore Options. (line 39) ! * mbig-endian <6>: MicroBlaze Options. (line 57) ! * mbig-endian <7>: NDS32 Options. (line 9) ! * mbig-endian <8>: RS/6000 and PowerPC Options. ! (line 593) ! * mbig-endian <9>: TILE-Gx Options. (line 29) * mbig-endian-data: RX Options. (line 42) * mbig-switch: V850 Options. (line 176) * mbigtable: SH Options. (line 141) * mbionic: GNU/Linux Options. (line 22) * mbit-align: RS/6000 and PowerPC Options. ! (line 545) * mbit-ops: CR16 Options. (line 25) ! * mbitfield: M680x0 Options. (line 231) ! * mbitops: MeP Options. (line 26) * mbitops <1>: SH Options. (line 145) * mblock-move-inline-limit: RS/6000 and PowerPC Options. ! (line 826) ! * mbmi: x86 Options. (line 636) * mbranch-cheap: PDP-11 Options. (line 65) * mbranch-cost: Adapteva Epiphany Options. (line 18) ! * mbranch-cost <1>: AVR Options. (line 165) ! * mbranch-cost <2>: MIPS Options. (line 745) ! * mbranch-cost=NUM: SH Options. (line 334) * mbranch-cost=NUMBER: M32R/D Options. (line 82) * mbranch-expensive: PDP-11 Options. (line 61) ! * mbranch-hints: SPU Options. (line 29) ! * mbranch-likely: MIPS Options. (line 752) ! * mbranch-predict: MMIX Options. (line 48) * mbss-plt: RS/6000 and PowerPC Options. (line 189) * mbuild-constants: DEC Alpha Options. (line 141) * mbwx: DEC Alpha Options. (line 163) ! * mbypass-cache: Nios II Options. (line 79) ! * mc68000: M680x0 Options. (line 93) ! * mc68020: M680x0 Options. (line 107) * mc=: MeP Options. (line 31) * mcache-block-size: NDS32 Options. (line 48) ! * mcache-size: SPU Options. (line 75) ! * mcache-volatile: Nios II Options. (line 85) * mcall-eabi: RS/6000 and PowerPC Options. ! (line 668) * mcall-freebsd: RS/6000 and PowerPC Options. ! (line 682) * mcall-linux: RS/6000 and PowerPC Options. ! (line 678) * mcall-netbsd: RS/6000 and PowerPC Options. ! (line 686) ! * mcall-netbsd <1>: RS/6000 and PowerPC Options. ! (line 690) ! * mcall-prologues: AVR Options. (line 170) * mcall-sysv: RS/6000 and PowerPC Options. ! (line 660) * mcall-sysv-eabi: RS/6000 and PowerPC Options. ! (line 668) * mcall-sysv-noeabi: RS/6000 and PowerPC Options. ! (line 671) * mcallee-super-interworking: ARM Options. (line 292) * mcaller-super-interworking: ARM Options. (line 299) * mcallgraph-data: MCore Options. (line 31) ! * mcase-vector-pcrel: ARC Options. (line 331) ! * mcbcond: SPARC Options. (line 244) ! * mcbranch-force-delay-slot: SH Options. (line 349) ! * mcc-init: CRIS Options. (line 42) ! * mcfv4e: M680x0 Options. (line 169) ! * mcheck-zero-division: MIPS Options. (line 547) * mcix: DEC Alpha Options. (line 163) ! * mcld: x86 Options. (line 694) * mclear-hwcap: Solaris 2 Options. (line 9) ! * mclfushopt: x86 Options. (line 624) * mclip: MeP Options. (line 35) ! * mclzero: x86 Options. (line 648) * mcmodel: NDS32 Options. (line 55) ! * mcmodel <1>: SPARC Options. (line 282) ! * mcmodel=kernel: x86 Options. (line 1150) ! * mcmodel=large: AArch64 Options. (line 47) ! * mcmodel=large <1>: RS/6000 and PowerPC Options. ! (line 130) * mcmodel=large <2>: TILE-Gx Options. (line 14) ! * mcmodel=large <3>: x86 Options. (line 1162) * mcmodel=medium: RS/6000 and PowerPC Options. (line 126) ! * mcmodel=medium <1>: x86 Options. (line 1155) ! * mcmodel=small: AArch64 Options. (line 41) ! * mcmodel=small <1>: RS/6000 and PowerPC Options. ! (line 122) * mcmodel=small <2>: TILE-Gx Options. (line 9) ! * mcmodel=small <3>: x86 Options. (line 1144) * mcmodel=tiny: AArch64 Options. (line 34) * mcmov: NDS32 Options. (line 21) * mcmove: Adapteva Epiphany Options. (line 23) * mcmpb: RS/6000 and PowerPC Options. (line 27) ! * mcode-density: ARC Options. (line 104) ! * mcode-readable: MIPS Options. (line 507) * mcode-region: MSP430 Options. (line 93) ! * mcompact-branches=always: MIPS Options. (line 764) ! * mcompact-branches=never: MIPS Options. (line 764) ! * mcompact-branches=optimal: MIPS Options. (line 764) ! * mcompact-casesi: ARC Options. (line 335) * mcompat-align-parm: RS/6000 and PowerPC Options. ! (line 1004) ! * mcond-exec: FRV Options. (line 187) ! * mcond-move: FRV Options. (line 159) * mconfig=: MeP Options. (line 39) * mconsole: x86 Windows Options. (line 9) --- 52682,52861 ---- * mam33-2: MN10300 Options. (line 24) * mam34: MN10300 Options. (line 27) * mandroid: GNU/Linux Options. (line 26) ! * mannotate-align: ARC Options. (line 274) * mapcs: ARM Options. (line 21) * mapcs-frame: ARM Options. (line 13) * mapp-regs <1>: V850 Options. (line 181) + * mapp-regs: SPARC Options. (line 10) * mARC600: ARC Options. (line 19) ! * mARC601: ARC Options. (line 27) ! * mARC700: ARC Options. (line 32) ! * march <1>: x86 Options. (line 9) ! * march <2>: S/390 and zSeries Options. ! (line 150) ! * march <3>: Nios II Options. (line 73) ! * march <4>: NDS32 Options. (line 52) ! * march <5>: MIPS Options. (line 14) * march <6>: M680x0 Options. (line 12) ! * march <7>: HPPA Options. (line 9) ! * march <8>: CRIS Options. (line 10) ! * march <9>: C6X Options. (line 7) ! * march <10>: ARM Options. (line 65) ! * march: AArch64 Options. (line 95) ! * marclinux: ARC Options. (line 281) ! * marclinux_prof: ARC Options. (line 287) ! * margonaut: ARC Options. (line 478) ! * marm: ARM Options. (line 269) * mas100-syntax: RX Options. (line 76) * masm-hex: MSP430 Options. (line 9) * masm-syntax-unified: ARM Options. (line 363) ! * masm=DIALECT: x86 Options. (line 360) ! * matomic: ARC Options. (line 101) * matomic-model=MODEL: SH Options. (line 193) ! * matomic-updates: SPU Options. (line 78) * mauto-litpools: Xtensa Options. (line 60) ! * mauto-modify-reg: ARC Options. (line 330) * mauto-pic: IA-64 Options. (line 50) * maverage: MeP Options. (line 16) * mavoid-indexed-addresses: RS/6000 and PowerPC Options. ! (line 489) ! * mavx: x86 Options. (line 616) ! * mavx2: x86 Options. (line 617) ! * mavx256-split-unaligned-load: x86 Options. (line 1101) ! * mavx256-split-unaligned-store: x86 Options. (line 1101) ! * mavx512bw: x86 Options. (line 623) ! * mavx512cd: x86 Options. (line 621) ! * mavx512dq: x86 Options. (line 624) ! * mavx512er: x86 Options. (line 620) ! * mavx512f: x86 Options. (line 618) ! * mavx512ifma: x86 Options. (line 625) ! * mavx512pf: x86 Options. (line 619) ! * mavx512vbmi: x86 Options. (line 626) ! * mavx512vl: x86 Options. (line 622) * max-vect-align: Adapteva Epiphany Options. ! (line 120) * mb: SH Options. (line 126) * mbackchain: S/390 and zSeries Options. (line 35) * mbarrel-shift-enabled: LM32 Options. (line 9) * mbarrel-shifter: ARC Options. (line 10) ! * mbarrel_shifter: ARC Options. (line 495) ! * mbase-addresses: MMIX Options. (line 54) * mbased=: MeP Options. (line 20) ! * mbbit-peephole: ARC Options. (line 333) * mbcopy: PDP-11 Options. (line 36) * mbcopy-builtin: PDP-11 Options. (line 32) * mbig: RS/6000 and PowerPC Options. ! (line 569) ! * mbig-endian <1>: TILE-Gx Options. (line 29) ! * mbig-endian <2>: RS/6000 and PowerPC Options. ! (line 569) ! * mbig-endian <3>: NDS32 Options. (line 9) ! * mbig-endian <4>: MicroBlaze Options. (line 57) * mbig-endian <5>: MCore Options. (line 39) ! * mbig-endian <6>: IA-64 Options. (line 9) ! * mbig-endian <7>: C6X Options. (line 13) ! * mbig-endian <8>: ARM Options. (line 61) ! * mbig-endian <9>: ARC Options. (line 481) ! * mbig-endian: AArch64 Options. (line 20) * mbig-endian-data: RX Options. (line 42) * mbig-switch: V850 Options. (line 176) * mbigtable: SH Options. (line 141) * mbionic: GNU/Linux Options. (line 22) * mbit-align: RS/6000 and PowerPC Options. ! (line 521) * mbit-ops: CR16 Options. (line 25) ! * mbitfield: M680x0 Options. (line 235) * mbitops <1>: SH Options. (line 145) + * mbitops: MeP Options. (line 26) * mblock-move-inline-limit: RS/6000 and PowerPC Options. ! (line 803) ! * mbmi: x86 Options. (line 642) * mbranch-cheap: PDP-11 Options. (line 65) + * mbranch-cost <1>: MIPS Options. (line 757) + * mbranch-cost <2>: AVR Options. (line 163) * mbranch-cost: Adapteva Epiphany Options. (line 18) ! * mbranch-cost=NUM: SH Options. (line 338) * mbranch-cost=NUMBER: M32R/D Options. (line 82) * mbranch-expensive: PDP-11 Options. (line 61) ! * mbranch-hints: SPU Options. (line 27) ! * mbranch-likely: MIPS Options. (line 764) ! * mbranch-predict: MMIX Options. (line 49) * mbss-plt: RS/6000 and PowerPC Options. (line 189) * mbuild-constants: DEC Alpha Options. (line 141) * mbwx: DEC Alpha Options. (line 163) ! * mbypass-cache: Nios II Options. (line 82) ! * mc68000: M680x0 Options. (line 95) ! * mc68020: M680x0 Options. (line 109) * mc=: MeP Options. (line 31) * mcache-block-size: NDS32 Options. (line 48) ! * mcache-size: SPU Options. (line 70) ! * mcache-volatile: Nios II Options. (line 88) * mcall-eabi: RS/6000 and PowerPC Options. ! (line 644) * mcall-freebsd: RS/6000 and PowerPC Options. ! (line 658) * mcall-linux: RS/6000 and PowerPC Options. ! (line 654) * mcall-netbsd: RS/6000 and PowerPC Options. ! (line 662) ! * mcall-prologues: AVR Options. (line 168) * mcall-sysv: RS/6000 and PowerPC Options. ! (line 636) * mcall-sysv-eabi: RS/6000 and PowerPC Options. ! (line 644) * mcall-sysv-noeabi: RS/6000 and PowerPC Options. ! (line 647) * mcallee-super-interworking: ARM Options. (line 292) * mcaller-super-interworking: ARM Options. (line 299) * mcallgraph-data: MCore Options. (line 31) ! * mcase-vector-pcrel: ARC Options. (line 341) ! * mcbcond: SPARC Options. (line 247) ! * mcbranch-force-delay-slot: SH Options. (line 353) ! * mcc-init: CRIS Options. (line 41) ! * mcfv4e: M680x0 Options. (line 172) ! * mcheck-zero-division: MIPS Options. (line 551) * mcix: DEC Alpha Options. (line 163) ! * mcld: x86 Options. (line 701) * mclear-hwcap: Solaris 2 Options. (line 9) ! * mclfushopt: x86 Options. (line 630) * mclip: MeP Options. (line 35) ! * mclzero: x86 Options. (line 654) ! * mcmodel <1>: SPARC Options. (line 285) * mcmodel: NDS32 Options. (line 55) ! * mcmodel=kernel: x86 Options. (line 1159) ! * mcmodel=large <1>: x86 Options. (line 1171) * mcmodel=large <2>: TILE-Gx Options. (line 14) ! * mcmodel=large <3>: RS/6000 and PowerPC Options. ! (line 130) ! * mcmodel=large: AArch64 Options. (line 47) ! * mcmodel=medium <1>: x86 Options. (line 1164) * mcmodel=medium: RS/6000 and PowerPC Options. (line 126) ! * mcmodel=small <1>: x86 Options. (line 1153) * mcmodel=small <2>: TILE-Gx Options. (line 9) ! * mcmodel=small <3>: RS/6000 and PowerPC Options. ! (line 122) ! * mcmodel=small: AArch64 Options. (line 41) * mcmodel=tiny: AArch64 Options. (line 34) * mcmov: NDS32 Options. (line 21) * mcmove: Adapteva Epiphany Options. (line 23) * mcmpb: RS/6000 and PowerPC Options. (line 27) ! * mcode-density: ARC Options. (line 109) ! * mcode-readable: MIPS Options. (line 511) * mcode-region: MSP430 Options. (line 93) ! * mcompact-branches=always: MIPS Options. (line 776) ! * mcompact-branches=never: MIPS Options. (line 776) ! * mcompact-branches=optimal: MIPS Options. (line 776) ! * mcompact-casesi: ARC Options. (line 345) * mcompat-align-parm: RS/6000 and PowerPC Options. ! (line 983) ! * mcond-exec: FRV Options. (line 152) ! * mcond-move: FRV Options. (line 128) * mconfig=: MeP Options. (line 39) * mconsole: x86 Windows Options. (line 9) *************** look up both forms. *** 52274,52324 **** * mcop: MeP Options. (line 48) * mcop32: MeP Options. (line 53) * mcop64: MeP Options. (line 56) ! * mcorea: Blackfin Options. (line 156) ! * mcoreb: Blackfin Options. (line 163) ! * mcpu: AArch64 Options. (line 145) ! * mcpu <1>: ARC Options. (line 14) ! * mcpu <2>: ARM Options. (line 133) ! * mcpu <3>: CRIS Options. (line 10) ! * mcpu <4>: DEC Alpha Options. (line 215) ! * mcpu <5>: FRV Options. (line 258) ! * mcpu <6>: M680x0 Options. (line 28) ! * mcpu <7>: picoChip Options. (line 9) * mcpu <8>: RL78 Options. (line 32) ! * mcpu <9>: RS/6000 and PowerPC Options. ! (line 68) ! * mcpu <10>: RX Options. (line 30) ! * mcpu <11>: SPARC Options. (line 110) ! * mcpu <12>: TILE-Gx Options. (line 18) ! * mcpu <13>: TILEPro Options. (line 9) ! * mcpu <14>: Visium Options. (line 33) ! * mcpu <15>: x86 Options. (line 302) ! * mcpu32: M680x0 Options. (line 135) ! * mcpu=: Blackfin Options. (line 7) ! * mcpu= <1>: M32C Options. (line 7) * mcpu= <2>: MicroBlaze Options. (line 20) ! * mcpu= <3>: MSP430 Options. (line 42) * mcr16c: CR16 Options. (line 14) * mcr16cplus: CR16 Options. (line 14) ! * mcrc32: x86 Options. (line 741) * mcrypto: RS/6000 and PowerPC Options. (line 229) ! * mcsync-anomaly: Blackfin Options. (line 59) ! * mctor-dtor: NDS32 Options. (line 69) ! * mcustom-fpu-cfg: Nios II Options. (line 235) ! * mcustom-INSN: Nios II Options. (line 115) ! * mcx16: x86 Options. (line 718) * MD: Preprocessor Options. ! (line 276) * mdalign: SH Options. (line 132) * mdata-align: CRIS Options. (line 55) * mdata-model: CR16 Options. (line 28) * mdata-region: MSP430 Options. (line 93) * mdc: MeP Options. (line 62) * mdebug: M32R/D Options. (line 69) - * mdebug <1>: S/390 and zSeries Options. - (line 144) - * mdebug <2>: Visium Options. (line 7) * mdebug-main=PREFIX: VMS Options. (line 13) * mdec-asm: PDP-11 Options. (line 72) * mdirect-move: RS/6000 and PowerPC Options. --- 52865,52915 ---- * mcop: MeP Options. (line 48) * mcop32: MeP Options. (line 53) * mcop64: MeP Options. (line 56) ! * mcorea: Blackfin Options. (line 157) ! * mcoreb: Blackfin Options. (line 164) ! * mcpu <1>: x86 Options. (line 308) ! * mcpu <2>: Visium Options. (line 33) ! * mcpu <3>: TILEPro Options. (line 9) ! * mcpu <4>: TILE-Gx Options. (line 18) ! * mcpu <5>: SPARC Options. (line 112) ! * mcpu <6>: RX Options. (line 30) ! * mcpu <7>: RS/6000 and PowerPC Options. ! (line 69) * mcpu <8>: RL78 Options. (line 32) ! * mcpu <9>: picoChip Options. (line 9) ! * mcpu <10>: M680x0 Options. (line 28) ! * mcpu <11>: FRV Options. (line 212) ! * mcpu <12>: DEC Alpha Options. (line 215) ! * mcpu <13>: CRIS Options. (line 10) ! * mcpu <14>: ARM Options. (line 133) ! * mcpu <15>: ARC Options. (line 14) ! * mcpu: AArch64 Options. (line 146) ! * mcpu32: M680x0 Options. (line 138) ! * mcpu= <1>: MSP430 Options. (line 42) * mcpu= <2>: MicroBlaze Options. (line 20) ! * mcpu= <3>: M32C Options. (line 7) ! * mcpu=: Blackfin Options. (line 7) * mcr16c: CR16 Options. (line 14) * mcr16cplus: CR16 Options. (line 14) ! * mcrc32: x86 Options. (line 748) * mcrypto: RS/6000 and PowerPC Options. (line 229) ! * mcsync-anomaly: Blackfin Options. (line 60) ! * mctor-dtor: NDS32 Options. (line 71) ! * mcustom-fpu-cfg: Nios II Options. (line 239) ! * mcustom-INSN: Nios II Options. (line 118) ! * mcx16: x86 Options. (line 725) * MD: Preprocessor Options. ! (line 274) * mdalign: SH Options. (line 132) * mdata-align: CRIS Options. (line 55) * mdata-model: CR16 Options. (line 28) * mdata-region: MSP430 Options. (line 93) * mdc: MeP Options. (line 62) + * mdebug <1>: Visium Options. (line 7) + * mdebug <2>: S/390 and zSeries Options. + (line 146) * mdebug: M32R/D Options. (line 69) * mdebug-main=PREFIX: VMS Options. (line 13) * mdec-asm: PDP-11 Options. (line 72) * mdirect-move: RS/6000 and PowerPC Options. *************** look up both forms. *** 52326,52494 **** * mdisable-callt: V850 Options. (line 92) * mdisable-fpregs: HPPA Options. (line 27) * mdisable-indexing: HPPA Options. (line 33) ! * mdiv: M680x0 Options. (line 206) ! * mdiv <1>: MCore Options. (line 15) ! * mdiv <2>: MeP Options. (line 65) ! * mdiv-rem: ARC Options. (line 101) ! * mdiv=STRATEGY: SH Options. (line 284) ! * mdivide-breaks: MIPS Options. (line 553) * mdivide-enabled: LM32 Options. (line 12) ! * mdivide-traps: MIPS Options. (line 553) ! * mdivsi3_libfunc=NAME: SH Options. (line 320) * mdll: x86 Windows Options. (line 16) * mdlmzb: RS/6000 and PowerPC Options. ! (line 538) ! * mdmx: MIPS Options. (line 375) ! * mdouble: FRV Options. (line 48) ! * mdouble-float: MIPS Options. (line 287) * mdouble-float <1>: RS/6000 and PowerPC Options. ! (line 461) ! * mdpfp: ARC Options. (line 41) ! * mdpfp-compact: ARC Options. (line 42) ! * mdpfp-fast: ARC Options. (line 46) ! * mdpfp_compact: ARC Options. (line 486) ! * mdpfp_fast: ARC Options. (line 489) ! * mdsp: MIPS Options. (line 352) ! * mdsp-packa: ARC Options. (line 220) ! * mdspr2: MIPS Options. (line 358) ! * mdsp_packa: ARC Options. (line 492) ! * mdual-nops: SPU Options. (line 95) ! * mdump-tune-features: x86 Options. (line 676) ! * mdvbf: ARC Options. (line 224) * mdwarf2-asm: IA-64 Options. (line 94) ! * mdword: FRV Options. (line 40) * mdynamic-no-pic: RS/6000 and PowerPC Options. ! (line 598) ! * mea: ARC Options. (line 54) ! * mEA: ARC Options. (line 495) ! * mea32: SPU Options. (line 60) ! * mea64: SPU Options. (line 60) * meabi: RS/6000 and PowerPC Options. ! (line 775) ! * mearly-cbranchsi: ARC Options. (line 354) * mearly-stop-bits: IA-64 Options. (line 100) * meb: MeP Options. (line 68) ! * meb <1>: Moxie Options. (line 7) ! * meb <2>: Nios II Options. (line 66) ! * meb <3>: Score Options. (line 9) * mel: MeP Options. (line 71) ! * mel <1>: Moxie Options. (line 11) ! * mel <2>: Nios II Options. (line 66) ! * mel <3>: Score Options. (line 12) * melf: CRIS Options. (line 87) - * melf <1>: MMIX Options. (line 43) * memb: RS/6000 and PowerPC Options. ! (line 770) ! * membedded-data: MIPS Options. (line 494) * memregs=: M32C Options. (line 21) * mep: V850 Options. (line 16) * mepsilon: MMIX Options. (line 15) * merror-reloc: SPU Options. (line 10) * mesa: S/390 and zSeries Options. ! (line 94) ! * metrax100: CRIS Options. (line 27) ! * metrax4: CRIS Options. (line 27) ! * meva: MIPS Options. (line 402) ! * mexpand-adddi: ARC Options. (line 357) * mexplicit-relocs: DEC Alpha Options. (line 176) - * mexplicit-relocs <1>: MIPS Options. (line 538) * mexr: H8/300 Options. (line 28) ! * mextern-sdata: MIPS Options. (line 457) * MF: Preprocessor Options. (line 220) ! * mf16c: x86 Options. (line 627) ! * mfast-fp: Blackfin Options. (line 132) * mfast-indirect-calls: HPPA Options. (line 45) ! * mfast-sw-div: Nios II Options. (line 91) ! * mfaster-structs: SPARC Options. (line 91) ! * mfdpic: FRV Options. (line 72) ! * mfentry: x86 Options. (line 1053) * mfix: DEC Alpha Options. (line 163) ! * mfix-24k: MIPS Options. (line 611) * mfix-and-continue: Darwin Options. (line 104) ! * mfix-at697f: SPARC Options. (line 264) * mfix-cortex-a53-835769: AArch64 Options. (line 74) * mfix-cortex-a53-843419: AArch64 Options. (line 81) * mfix-cortex-m3-ldrd: ARM Options. (line 332) ! * mfix-r10000: MIPS Options. (line 633) ! * mfix-r4000: MIPS Options. (line 617) ! * mfix-r4400: MIPS Options. (line 627) ! * mfix-rm7000: MIPS Options. (line 644) ! * mfix-sb1: MIPS Options. (line 669) ! * mfix-ut699: SPARC Options. (line 269) ! * mfix-vr4120: MIPS Options. (line 649) ! * mfix-vr4130: MIPS Options. (line 662) ! * mfixed-cc: FRV Options. (line 35) * mfixed-range: HPPA Options. (line 52) - * mfixed-range <1>: IA-64 Options. (line 105) - * mfixed-range <2>: SH Options. (line 327) - * mfixed-range <3>: SPU Options. (line 52) * mflat: SPARC Options. (line 22) ! * mflip-mips16: MIPS Options. (line 127) * mfloat-abi: ARM Options. (line 41) * mfloat-gprs: RS/6000 and PowerPC Options. ! (line 350) * mfloat-ieee: DEC Alpha Options. (line 171) * mfloat-vax: DEC Alpha Options. (line 171) * mfloat128: RS/6000 and PowerPC Options. ! (line 297) * mfloat128-hardware: RS/6000 and PowerPC Options. ! (line 312) * mfloat32: PDP-11 Options. (line 52) * mfloat64: PDP-11 Options. (line 48) ! * mflush-func: MIPS Options. (line 736) * mflush-func=NAME: M32R/D Options. (line 93) * mflush-trap=NUMBER: M32R/D Options. (line 86) ! * mfma: x86 Options. (line 628) ! * mfma4: x86 Options. (line 629) ! * mfmaf: SPARC Options. (line 258) * mfmovd: SH Options. (line 148) * mforce-no-pic: Xtensa Options. (line 41) ! * mfp-exceptions: MIPS Options. (line 784) * mfp-mode: Adapteva Epiphany Options. ! (line 71) * mfp-reg: DEC Alpha Options. (line 25) * mfp-rounding-mode: DEC Alpha Options. (line 85) * mfp-trap-mode: DEC Alpha Options. (line 63) ! * mfp16-format: ARM Options. (line 178) ! * mfp32: MIPS Options. (line 257) ! * mfp64: MIPS Options. (line 260) ! * mfpmath: Optimize Options. (line 1974) ! * mfpmath <1>: x86 Options. (line 305) ! * mfpr-32: FRV Options. (line 15) ! * mfpr-64: FRV Options. (line 19) * mfprnd: RS/6000 and PowerPC Options. (line 27) ! * mfpu: ARC Options. (line 149) ! * mfpu <1>: ARM Options. (line 153) ! * mfpu <2>: PDP-11 Options. (line 9) * mfpu <3>: RS/6000 and PowerPC Options. ! (line 469) ! * mfpu <4>: SPARC Options. (line 34) ! * mfpu <5>: Visium Options. (line 19) ! * mfpxx: MIPS Options. (line 263) ! * mframe-header-opt: MIPS Options. (line 845) * mfriz: RS/6000 and PowerPC Options. ! (line 975) ! * mfsca: SH Options. (line 365) ! * mfsgsbase: x86 Options. (line 625) ! * mfsrra: SH Options. (line 374) * mfull-regs: NDS32 Options. (line 18) * mfull-toc: RS/6000 and PowerPC Options. ! (line 378) ! * mfused-madd: IA-64 Options. (line 88) ! * mfused-madd <1>: MIPS Options. (line 594) ! * mfused-madd <2>: RS/6000 and PowerPC Options. ! (line 522) * mfused-madd <3>: S/390 and zSeries Options. ! (line 168) ! * mfused-madd <4>: SH Options. (line 356) ! * mfused-madd <5>: Xtensa Options. (line 19) ! * mfxsr: x86 Options. (line 639) * MG: Preprocessor Options. (line 229) - * mg: VAX Options. (line 17) * mg10: RL78 Options. (line 62) * mg13: RL78 Options. (line 62) * mg14: RL78 Options. (line 62) --- 52917,53085 ---- * mdisable-callt: V850 Options. (line 92) * mdisable-fpregs: HPPA Options. (line 27) * mdisable-indexing: HPPA Options. (line 33) ! * mdiv <1>: MeP Options. (line 65) ! * mdiv <2>: MCore Options. (line 15) ! * mdiv: M680x0 Options. (line 209) ! * mdiv-rem: ARC Options. (line 106) ! * mdiv=STRATEGY: SH Options. (line 287) ! * mdivide-breaks: MIPS Options. (line 557) * mdivide-enabled: LM32 Options. (line 12) ! * mdivide-traps: MIPS Options. (line 557) ! * mdivsi3_libfunc=NAME: SH Options. (line 324) * mdll: x86 Windows Options. (line 16) * mdlmzb: RS/6000 and PowerPC Options. ! (line 514) ! * mdmx: MIPS Options. (line 378) ! * mdouble: FRV Options. (line 38) * mdouble-float <1>: RS/6000 and PowerPC Options. ! (line 437) ! * mdouble-float: MIPS Options. (line 290) ! * mdpfp: ARC Options. (line 46) ! * mdpfp-compact: ARC Options. (line 47) ! * mdpfp-fast: ARC Options. (line 51) ! * mdpfp_compact: ARC Options. (line 498) ! * mdpfp_fast: ARC Options. (line 501) ! * mdsp: MIPS Options. (line 355) ! * mdsp-packa: ARC Options. (line 228) ! * mdsp_packa: ARC Options. (line 504) ! * mdspr2: MIPS Options. (line 361) ! * mdual-nops: SPU Options. (line 90) ! * mdump-tune-features: x86 Options. (line 682) ! * mdvbf: ARC Options. (line 232) * mdwarf2-asm: IA-64 Options. (line 94) ! * mdword: FRV Options. (line 32) * mdynamic-no-pic: RS/6000 and PowerPC Options. ! (line 574) ! * mEA: ARC Options. (line 507) ! * mea: ARC Options. (line 59) ! * mea32: SPU Options. (line 55) ! * mea64: SPU Options. (line 55) * meabi: RS/6000 and PowerPC Options. ! (line 751) ! * mearly-cbranchsi: ARC Options. (line 364) * mearly-stop-bits: IA-64 Options. (line 100) + * meb <1>: Score Options. (line 9) + * meb <2>: Nios II Options. (line 69) + * meb <3>: Moxie Options. (line 7) * meb: MeP Options. (line 68) ! * mel <1>: Score Options. (line 12) ! * mel <2>: Nios II Options. (line 69) ! * mel <3>: Moxie Options. (line 11) * mel: MeP Options. (line 71) ! * melf <1>: MMIX Options. (line 44) * melf: CRIS Options. (line 87) * memb: RS/6000 and PowerPC Options. ! (line 746) ! * membedded-data: MIPS Options. (line 498) * memregs=: M32C Options. (line 21) * mep: V850 Options. (line 16) * mepsilon: MMIX Options. (line 15) * merror-reloc: SPU Options. (line 10) * mesa: S/390 and zSeries Options. ! (line 95) ! * metrax100: CRIS Options. (line 26) ! * metrax4: CRIS Options. (line 26) ! * meva: MIPS Options. (line 405) ! * mexpand-adddi: ARC Options. (line 367) ! * mexplicit-relocs <1>: MIPS Options. (line 542) * mexplicit-relocs: DEC Alpha Options. (line 176) * mexr: H8/300 Options. (line 28) ! * mextern-sdata: MIPS Options. (line 460) * MF: Preprocessor Options. (line 220) ! * mf16c: x86 Options. (line 633) ! * mfast-fp: Blackfin Options. (line 133) * mfast-indirect-calls: HPPA Options. (line 45) ! * mfast-sw-div: Nios II Options. (line 94) ! * mfaster-structs: SPARC Options. (line 92) ! * mfdpic: FRV Options. (line 56) ! * mfentry: x86 Options. (line 1060) * mfix: DEC Alpha Options. (line 163) ! * mfix-24k: MIPS Options. (line 617) * mfix-and-continue: Darwin Options. (line 104) ! * mfix-at697f: SPARC Options. (line 267) * mfix-cortex-a53-835769: AArch64 Options. (line 74) * mfix-cortex-a53-843419: AArch64 Options. (line 81) * mfix-cortex-m3-ldrd: ARM Options. (line 332) ! * mfix-r10000: MIPS Options. (line 644) ! * mfix-r4000: MIPS Options. (line 623) ! * mfix-r4400: MIPS Options. (line 637) ! * mfix-rm7000: MIPS Options. (line 655) ! * mfix-sb1: MIPS Options. (line 681) ! * mfix-ut699: SPARC Options. (line 272) ! * mfix-vr4120: MIPS Options. (line 660) ! * mfix-vr4130: MIPS Options. (line 674) ! * mfixed-cc: FRV Options. (line 28) ! * mfixed-range <1>: SPU Options. (line 47) ! * mfixed-range <2>: SH Options. (line 331) ! * mfixed-range <3>: IA-64 Options. (line 105) * mfixed-range: HPPA Options. (line 52) * mflat: SPARC Options. (line 22) ! * mflip-mips16: MIPS Options. (line 128) * mfloat-abi: ARM Options. (line 41) * mfloat-gprs: RS/6000 and PowerPC Options. ! (line 325) * mfloat-ieee: DEC Alpha Options. (line 171) * mfloat-vax: DEC Alpha Options. (line 171) * mfloat128: RS/6000 and PowerPC Options. ! (line 298) * mfloat128-hardware: RS/6000 and PowerPC Options. ! (line 313) * mfloat32: PDP-11 Options. (line 52) * mfloat64: PDP-11 Options. (line 48) ! * mflush-func: MIPS Options. (line 748) * mflush-func=NAME: M32R/D Options. (line 93) * mflush-trap=NUMBER: M32R/D Options. (line 86) ! * mfma: x86 Options. (line 634) ! * mfma4: x86 Options. (line 635) ! * mfmaf: SPARC Options. (line 261) * mfmovd: SH Options. (line 148) * mforce-no-pic: Xtensa Options. (line 41) ! * mfp-exceptions: MIPS Options. (line 796) * mfp-mode: Adapteva Epiphany Options. ! (line 72) * mfp-reg: DEC Alpha Options. (line 25) * mfp-rounding-mode: DEC Alpha Options. (line 85) * mfp-trap-mode: DEC Alpha Options. (line 63) ! * mfp16-format: ARM Options. (line 179) ! * mfp32: MIPS Options. (line 260) ! * mfp64: MIPS Options. (line 263) ! * mfpmath <1>: x86 Options. (line 311) ! * mfpmath: Optimize Options. (line 1982) ! * mfpr-32: FRV Options. (line 13) ! * mfpr-64: FRV Options. (line 16) * mfprnd: RS/6000 and PowerPC Options. (line 27) ! * mfpu <1>: Visium Options. (line 19) ! * mfpu <2>: SPARC Options. (line 35) * mfpu <3>: RS/6000 and PowerPC Options. ! (line 445) ! * mfpu <4>: PDP-11 Options. (line 9) ! * mfpu <5>: ARM Options. (line 153) ! * mfpu: ARC Options. (line 155) ! * mfpxx: MIPS Options. (line 266) ! * mframe-header-opt: MIPS Options. (line 859) * mfriz: RS/6000 and PowerPC Options. ! (line 954) ! * mfsca: SH Options. (line 369) ! * mfsgsbase: x86 Options. (line 631) ! * mfsrra: SH Options. (line 378) * mfull-regs: NDS32 Options. (line 18) * mfull-toc: RS/6000 and PowerPC Options. ! (line 353) ! * mfused-madd <1>: Xtensa Options. (line 19) ! * mfused-madd <2>: SH Options. (line 360) * mfused-madd <3>: S/390 and zSeries Options. ! (line 170) ! * mfused-madd <4>: RS/6000 and PowerPC Options. ! (line 498) ! * mfused-madd <5>: MIPS Options. (line 599) ! * mfused-madd: IA-64 Options. (line 88) ! * mfxsr: x86 Options. (line 645) ! * mg: VAX Options. (line 17) * MG: Preprocessor Options. (line 229) * mg10: RL78 Options. (line 62) * mg13: RL78 Options. (line 62) * mg14: RL78 Options. (line 62) *************** look up both forms. *** 52501,52991 **** * mglibc: GNU/Linux Options. (line 9) * mgnu: VAX Options. (line 13) * mgnu-as: IA-64 Options. (line 18) - * mgnu-ld: HPPA Options. (line 104) * mgnu-ld <1>: IA-64 Options. (line 23) * mgotplt: CRIS Options. (line 81) ! * mgp32: MIPS Options. (line 251) ! * mgp64: MIPS Options. (line 254) ! * mgpopt: MIPS Options. (line 479) ! * mgpopt <1>: Nios II Options. (line 16) * mgpr-32: FRV Options. (line 7) ! * mgpr-64: FRV Options. (line 11) ! * mgprel-ro: FRV Options. (line 99) * mh: H8/300 Options. (line 14) ! * mhal: Nios II Options. (line 280) * mhalf-reg-file: Adapteva Epiphany Options. (line 9) - * mhard-dfp: RS/6000 and PowerPC Options. - (line 27) * mhard-dfp <1>: S/390 and zSeries Options. (line 20) ! * mhard-float: FRV Options. (line 23) ! * mhard-float <1>: M680x0 Options. (line 194) ! * mhard-float <2>: MicroBlaze Options. (line 10) ! * mhard-float <3>: MIPS Options. (line 266) ! * mhard-float <4>: RS/6000 and PowerPC Options. ! (line 455) ! * mhard-float <5>: S/390 and zSeries Options. (line 11) ! * mhard-float <6>: SPARC Options. (line 34) ! * mhard-float <7>: V850 Options. (line 113) ! * mhard-float <8>: Visium Options. (line 19) ! * mhard-quad-float: SPARC Options. (line 55) * mhardlit: MCore Options. (line 10) ! * mhint-max-distance: SPU Options. (line 107) ! * mhint-max-nops: SPU Options. (line 101) * mhotpatch: S/390 and zSeries Options. ! (line 203) * mhp-ld: HPPA Options. (line 116) * mhtm: RS/6000 and PowerPC Options. (line 241) ! * mhtm <1>: S/390 and zSeries Options. ! (line 104) ! * mhw-div: Nios II Options. (line 100) ! * mhw-mul: Nios II Options. (line 100) ! * mhw-mulx: Nios II Options. (line 100) * mhwmult=: MSP430 Options. (line 63) ! * miamcu: x86 Options. (line 1116) ! * micplb: Blackfin Options. (line 177) ! * mid-shared-library: Blackfin Options. (line 80) ! * mieee: DEC Alpha Options. (line 39) * mieee <1>: SH Options. (line 165) * mieee-conformant: DEC Alpha Options. (line 134) ! * mieee-fp: x86 Options. (line 362) * mieee-with-inexact: DEC Alpha Options. (line 52) * milp32: IA-64 Options. (line 121) ! * mimadd: MIPS Options. (line 587) ! * mimpure-text: Solaris 2 Options. (line 15) ! * mincoming-stack-boundary: x86 Options. (line 576) ! * mindexed-loads: ARC Options. (line 361) ! * minline-all-stringops: x86 Options. (line 985) * minline-float-divide-max-throughput: IA-64 Options. (line 58) * minline-float-divide-min-latency: IA-64 Options. (line 54) * minline-ic_invalidate: SH Options. (line 174) * minline-int-divide-max-throughput: IA-64 Options. (line 69) * minline-int-divide-min-latency: IA-64 Options. (line 65) ! * minline-plt: Blackfin Options. (line 137) ! * minline-plt <1>: FRV Options. (line 81) * minline-sqrt-max-throughput: IA-64 Options. (line 80) * minline-sqrt-min-latency: IA-64 Options. (line 76) ! * minline-stringops-dynamically: x86 Options. (line 992) * minrt: MSP430 Options. (line 85) * minsert-sched-nops: RS/6000 and PowerPC Options. ! (line 638) * mint-register: RX Options. (line 100) * mint16: PDP-11 Options. (line 40) * mint32: CR16 Options. (line 22) ! * mint32 <1>: H8/300 Options. (line 38) ! * mint32 <2>: PDP-11 Options. (line 44) ! * mint8: AVR Options. (line 174) ! * minterlink-compressed: MIPS Options. (line 134) ! * minterlink-mips16: MIPS Options. (line 146) * mio-volatile: MeP Options. (line 74) ! * mips1: MIPS Options. (line 79) ! * mips16: MIPS Options. (line 119) ! * mips2: MIPS Options. (line 82) ! * mips3: MIPS Options. (line 85) ! * mips32: MIPS Options. (line 91) ! * mips32r3: MIPS Options. (line 94) ! * mips32r5: MIPS Options. (line 97) ! * mips32r6: MIPS Options. (line 100) ! * mips3d: MIPS Options. (line 381) ! * mips4: MIPS Options. (line 88) ! * mips64: MIPS Options. (line 103) ! * mips64r2: MIPS Options. (line 106) ! * mips64r3: MIPS Options. (line 109) ! * mips64r5: MIPS Options. (line 112) ! * mips64r6: MIPS Options. (line 115) * misel: RS/6000 and PowerPC Options. (line 195) - * misize: ARC Options. (line 262) * misize <1>: SH Options. (line 186) * misr-vector-size: NDS32 Options. (line 45) * missue-rate=NUMBER: M32R/D Options. (line 79) * mivc2: MeP Options. (line 59) * mjsr: RX Options. (line 169) * mjump-in-delay: HPPA Options. (line 23) * mkernel: Darwin Options. (line 82) ! * mknuthdiv: MMIX Options. (line 32) ! * ml: MeP Options. (line 78) * ml <1>: SH Options. (line 129) * mlarge: MSP430 Options. (line 52) * mlarge-data: DEC Alpha Options. (line 187) ! * mlarge-data-threshold: x86 Options. (line 462) ! * mlarge-mem: SPU Options. (line 38) * mlarge-text: DEC Alpha Options. (line 205) * mleadz: MeP Options. (line 81) ! * mleaf-id-shared-library: Blackfin Options. (line 91) * mlibfuncs: MMIX Options. (line 10) ! * mlibrary-pic: FRV Options. (line 135) ! * mlinked-fp: FRV Options. (line 116) * mlinker-opt: HPPA Options. (line 78) * mlinux: CRIS Options. (line 91) * mlittle: RS/6000 and PowerPC Options. ! (line 587) ! * mlittle-endian: AArch64 Options. (line 30) ! * mlittle-endian <1>: ARC Options. (line 476) ! * mlittle-endian <2>: ARM Options. (line 57) ! * mlittle-endian <3>: C6X Options. (line 16) ! * mlittle-endian <4>: IA-64 Options. (line 13) * mlittle-endian <5>: MCore Options. (line 39) ! * mlittle-endian <6>: MicroBlaze Options. (line 60) ! * mlittle-endian <7>: NDS32 Options. (line 12) ! * mlittle-endian <8>: RS/6000 and PowerPC Options. ! (line 587) ! * mlittle-endian <9>: TILE-Gx Options. (line 29) * mlittle-endian-data: RX Options. (line 42) * mliw: MN10300 Options. (line 54) ! * mll64: ARC Options. (line 107) ! * mllsc: MIPS Options. (line 338) ! * mlocal-sdata: MIPS Options. (line 445) ! * mlock: ARC Options. (line 228) * mlong-calls: Adapteva Epiphany Options. (line 55) ! * mlong-calls <1>: ARC Options. (line 287) ! * mlong-calls <2>: ARM Options. (line 203) ! * mlong-calls <3>: Blackfin Options. (line 120) ! * mlong-calls <4>: FRV Options. (line 122) ! * mlong-calls <5>: MIPS Options. (line 573) ! * mlong-calls <6>: V850 Options. (line 10) * mlong-double-128: S/390 and zSeries Options. (line 29) ! * mlong-double-128 <1>: x86 Options. (line 441) * mlong-double-64: S/390 and zSeries Options. (line 29) ! * mlong-double-64 <1>: x86 Options. (line 441) ! * mlong-double-80: x86 Options. (line 441) * mlong-jumps: V850 Options. (line 108) * mlong-load-store: HPPA Options. (line 59) ! * mlong32: MIPS Options. (line 420) ! * mlong64: MIPS Options. (line 415) * mlongcall: RS/6000 and PowerPC Options. ! (line 846) * mlongcalls: Xtensa Options. (line 87) * mloop: V850 Options. (line 121) ! * mlow-64k: Blackfin Options. (line 69) * mlp64: IA-64 Options. (line 121) ! * mlra: ARC Options. (line 365) ! * mlra <1>: FT32 Options. (line 16) ! * mlra <2>: RS/6000 and PowerPC Options. (line 203) ! * mlra-priority-compact: ARC Options. (line 373) ! * mlra-priority-noncompact: ARC Options. (line 376) ! * mlra-priority-none: ARC Options. (line 370) ! * mlwp: x86 Options. (line 632) ! * mlzcnt: x86 Options. (line 638) * MM: Preprocessor Options. (line 210) - * mm: MeP Options. (line 84) - * mmac: CR16 Options. (line 9) * mmac <1>: Score Options. (line 21) ! * mmac-24: ARC Options. (line 237) ! * mmac-d16: ARC Options. (line 233) ! * mmac_24: ARC Options. (line 498) ! * mmac_d16: ARC Options. (line 501) ! * mmad: MIPS Options. (line 582) * mmainkernel: Nvidia PTX Options. (line 13) * mmalloc64: VMS Options. (line 17) * mmax: DEC Alpha Options. (line 163) * mmax-constant-size: RX Options. (line 82) ! * mmax-stack-frame: CRIS Options. (line 23) ! * mmcount-ra-address: MIPS Options. (line 832) * mmcu: AVR Options. (line 9) - * mmcu <1>: MIPS Options. (line 398) * mmcu=: MSP430 Options. (line 14) * MMD: Preprocessor Options. ! (line 292) ! * mmedia: FRV Options. (line 56) ! * mmedium-calls: ARC Options. (line 291) * mmemcpy: MicroBlaze Options. (line 13) ! * mmemcpy <1>: MIPS Options. (line 567) ! * mmemcpy-strategy=STRATEGY: x86 Options. (line 1014) * mmemory-latency: DEC Alpha Options. (line 268) ! * mmemory-model: SPARC Options. (line 310) ! * mmemset-strategy=STRATEGY: x86 Options. (line 1026) * mmfcrf: RS/6000 and PowerPC Options. (line 27) * mmfpgpr: RS/6000 and PowerPC Options. (line 27) ! * mmicromips: MIPS Options. (line 386) * mminimal-toc: RS/6000 and PowerPC Options. ! (line 378) * mminmax: MeP Options. (line 87) ! * mmitigate-rop: x86 Options. (line 1103) ! * mmixed-code: ARC Options. (line 388) ! * mmmx: x86 Options. (line 601) * mmodel=large: M32R/D Options. (line 33) * mmodel=medium: M32R/D Options. (line 27) * mmodel=small: M32R/D Options. (line 18) ! * mmodulo: RS/6000 and PowerPC Options. ! (line 324) ! * mmovbe: x86 Options. (line 737) ! * mmpx: x86 Options. (line 646) ! * mmpy-option: ARC Options. (line 110) ! * mms-bitfields: x86 Options. (line 860) ! * mmt: MIPS Options. (line 394) * mmul: RL78 Options. (line 15) ! * mmul-bug-workaround: CRIS Options. (line 32) * mmul.x: Moxie Options. (line 14) ! * mmul32x16: ARC Options. (line 62) ! * mmul64: ARC Options. (line 65) ! * mmuladd: FRV Options. (line 64) * mmulhw: RS/6000 and PowerPC Options. ! (line 531) * mmult: MeP Options. (line 90) * mmult-bug: MN10300 Options. (line 9) ! * mmultcost: ARC Options. (line 450) ! * mmulti-cond-exec: FRV Options. (line 215) ! * mmulticore: Blackfin Options. (line 141) * mmultiple: RS/6000 and PowerPC Options. ! (line 481) * mmusl: GNU/Linux Options. (line 18) * mmvcle: S/390 and zSeries Options. ! (line 138) * mmvme: RS/6000 and PowerPC Options. ! (line 751) ! * mmwaitx: x86 Options. (line 647) * mn: H8/300 Options. (line 20) ! * mn-flash: AVR Options. (line 180) ! * mnan=2008: MIPS Options. (line 319) ! * mnan=legacy: MIPS Options. (line 319) * mneon-for-64bits: ARM Options. (line 352) ! * mnested-cond-exec: FRV Options. (line 230) * mnhwloop: Score Options. (line 15) * mno-16-bit: NDS32 Options. (line 42) * mno-4byte-functions: MCore Options. (line 27) * mno-8byte-align: V850 Options. (line 170) ! * mno-abicalls: MIPS Options. (line 191) * mno-abshi: PDP-11 Options. (line 58) * mno-ac0: PDP-11 Options. (line 20) ! * mno-address-space-conversion: SPU Options. (line 68) ! * mno-align-double: x86 Options. (line 400) ! * mno-align-int: M680x0 Options. (line 263) * mno-align-loops: M32R/D Options. (line 76) ! * mno-align-stringops: x86 Options. (line 980) * mno-allow-string-insns: RX Options. (line 150) * mno-altivec: RS/6000 and PowerPC Options. (line 136) * mno-am33: MN10300 Options. (line 20) - * mno-app-regs: SPARC Options. (line 10) * mno-app-regs <1>: V850 Options. (line 185) * mno-as100-syntax: RX Options. (line 76) ! * mno-atomic-updates: SPU Options. (line 83) * mno-auto-litpools: Xtensa Options. (line 60) * mno-avoid-indexed-addresses: RS/6000 and PowerPC Options. ! (line 513) * mno-backchain: S/390 and zSeries Options. (line 35) ! * mno-base-addresses: MMIX Options. (line 53) * mno-bit-align: RS/6000 and PowerPC Options. ! (line 545) ! * mno-bitfield: M680x0 Options. (line 227) ! * mno-branch-likely: MIPS Options. (line 752) ! * mno-branch-predict: MMIX Options. (line 48) ! * mno-brcc: ARC Options. (line 326) * mno-bwx: DEC Alpha Options. (line 163) ! * mno-bypass-cache: Nios II Options. (line 79) ! * mno-cache-volatile: Nios II Options. (line 85) * mno-callgraph-data: MCore Options. (line 31) ! * mno-cbcond: SPARC Options. (line 244) ! * mno-check-zero-division: MIPS Options. (line 547) * mno-cix: DEC Alpha Options. (line 163) * mno-clearbss: MicroBlaze Options. (line 16) * mno-cmov: NDS32 Options. (line 24) * mno-cmpb: RS/6000 and PowerPC Options. (line 27) ! * mno-cond-exec: ARC Options. (line 338) ! * mno-cond-exec <1>: FRV Options. (line 194) ! * mno-cond-move: FRV Options. (line 166) * mno-const-align: CRIS Options. (line 55) * mno-const16: Xtensa Options. (line 10) - * mno-crt0: MN10300 Options. (line 43) * mno-crt0 <1>: Moxie Options. (line 18) * mno-crypto: RS/6000 and PowerPC Options. (line 229) ! * mno-csync-anomaly: Blackfin Options. (line 65) ! * mno-custom-INSN: Nios II Options. (line 115) * mno-data-align: CRIS Options. (line 55) * mno-debug: S/390 and zSeries Options. ! (line 144) ! * mno-default: x86 Options. (line 690) * mno-direct-move: RS/6000 and PowerPC Options. (line 235) * mno-disable-callt: V850 Options. (line 92) - * mno-div: M680x0 Options. (line 206) * mno-div <1>: MCore Options. (line 15) * mno-dlmzb: RS/6000 and PowerPC Options. ! (line 538) ! * mno-double: FRV Options. (line 52) ! * mno-dpfp-lrsr: ARC Options. (line 50) ! * mno-dsp: MIPS Options. (line 352) ! * mno-dspr2: MIPS Options. (line 358) * mno-dwarf2-asm: IA-64 Options. (line 94) ! * mno-dword: FRV Options. (line 44) * mno-eabi: RS/6000 and PowerPC Options. ! (line 775) * mno-early-stop-bits: IA-64 Options. (line 100) ! * mno-eflags: FRV Options. (line 155) ! * mno-embedded-data: MIPS Options. (line 494) * mno-ep: V850 Options. (line 16) * mno-epsilon: MMIX Options. (line 15) ! * mno-eva: MIPS Options. (line 402) * mno-explicit-relocs: DEC Alpha Options. (line 176) - * mno-explicit-relocs <1>: MIPS Options. (line 538) * mno-exr: H8/300 Options. (line 33) ! * mno-extern-sdata: MIPS Options. (line 457) ! * mno-fancy-math-387: x86 Options. (line 390) ! * mno-fast-sw-div: Nios II Options. (line 91) ! * mno-faster-structs: SPARC Options. (line 91) * mno-fix: DEC Alpha Options. (line 163) ! * mno-fix-24k: MIPS Options. (line 611) * mno-fix-cortex-a53-835769: AArch64 Options. (line 74) * mno-fix-cortex-a53-843419: AArch64 Options. (line 81) ! * mno-fix-r10000: MIPS Options. (line 633) ! * mno-fix-r4000: MIPS Options. (line 617) ! * mno-fix-r4400: MIPS Options. (line 627) * mno-flat: SPARC Options. (line 22) ! * mno-float: MIPS Options. (line 273) * mno-float128: RS/6000 and PowerPC Options. ! (line 297) * mno-float128-hardware: RS/6000 and PowerPC Options. ! (line 312) * mno-float32: PDP-11 Options. (line 48) * mno-float64: PDP-11 Options. (line 52) * mno-flush-func: M32R/D Options. (line 98) * mno-flush-trap: M32R/D Options. (line 90) ! * mno-fmaf: SPARC Options. (line 258) * mno-fp-in-toc: RS/6000 and PowerPC Options. ! (line 378) * mno-fp-regs: DEC Alpha Options. (line 25) ! * mno-fp-ret-in-387: x86 Options. (line 380) * mno-fprnd: RS/6000 and PowerPC Options. (line 27) - * mno-fpu: SPARC Options. (line 39) * mno-fpu <1>: Visium Options. (line 24) ! * mno-fsca: SH Options. (line 365) ! * mno-fsrra: SH Options. (line 374) ! * mno-fused-madd: IA-64 Options. (line 88) ! * mno-fused-madd <1>: MIPS Options. (line 594) ! * mno-fused-madd <2>: RS/6000 and PowerPC Options. ! (line 522) * mno-fused-madd <3>: S/390 and zSeries Options. ! (line 168) ! * mno-fused-madd <4>: SH Options. (line 356) ! * mno-fused-madd <5>: Xtensa Options. (line 19) * mno-gnu-as: IA-64 Options. (line 18) * mno-gnu-ld: IA-64 Options. (line 23) * mno-gotplt: CRIS Options. (line 81) ! * mno-gpopt: MIPS Options. (line 479) ! * mno-gpopt <1>: Nios II Options. (line 16) ! * mno-hard-dfp: RS/6000 and PowerPC Options. ! (line 27) * mno-hard-dfp <1>: S/390 and zSeries Options. (line 20) * mno-hardlit: MCore Options. (line 10) * mno-htm: RS/6000 and PowerPC Options. (line 241) ! * mno-htm <1>: S/390 and zSeries Options. ! (line 104) ! * mno-hw-div: Nios II Options. (line 100) ! * mno-hw-mul: Nios II Options. (line 100) ! * mno-hw-mulx: Nios II Options. (line 100) ! * mno-id-shared-library: Blackfin Options. (line 87) * mno-ieee: SH Options. (line 165) ! * mno-ieee-fp: x86 Options. (line 362) ! * mno-imadd: MIPS Options. (line 587) * mno-inline-float-divide: IA-64 Options. (line 62) * mno-inline-int-divide: IA-64 Options. (line 73) * mno-inline-sqrt: IA-64 Options. (line 84) * mno-int16: PDP-11 Options. (line 44) * mno-int32: PDP-11 Options. (line 40) ! * mno-interlink-compressed: MIPS Options. (line 134) ! * mno-interlink-mips16: MIPS Options. (line 146) ! * mno-interrupts: AVR Options. (line 183) * mno-isel: RS/6000 and PowerPC Options. (line 195) * mno-jsr: RX Options. (line 169) ! * mno-knuthdiv: MMIX Options. (line 32) ! * mno-leaf-id-shared-library: Blackfin Options. (line 97) * mno-libfuncs: MMIX Options. (line 10) ! * mno-llsc: MIPS Options. (line 338) ! * mno-local-sdata: MIPS Options. (line 445) ! * mno-long-calls: ARM Options. (line 203) ! * mno-long-calls <1>: Blackfin Options. (line 120) ! * mno-long-calls <2>: HPPA Options. (line 129) ! * mno-long-calls <3>: MIPS Options. (line 573) ! * mno-long-calls <4>: V850 Options. (line 10) * mno-long-jumps: V850 Options. (line 108) * mno-longcall: RS/6000 and PowerPC Options. ! (line 846) * mno-longcalls: Xtensa Options. (line 87) ! * mno-low-64k: Blackfin Options. (line 73) ! * mno-lsim: FR30 Options. (line 14) * mno-lsim <1>: MCore Options. (line 46) ! * mno-mad: MIPS Options. (line 582) * mno-max: DEC Alpha Options. (line 163) ! * mno-mcount-ra-address: MIPS Options. (line 832) ! * mno-mcu: MIPS Options. (line 398) ! * mno-mdmx: MIPS Options. (line 375) ! * mno-media: FRV Options. (line 60) ! * mno-memcpy: MIPS Options. (line 567) * mno-mfcrf: RS/6000 and PowerPC Options. (line 27) * mno-mfpgpr: RS/6000 and PowerPC Options. (line 27) ! * mno-millicode: ARC Options. (line 379) ! * mno-mips16: MIPS Options. (line 119) ! * mno-mips3d: MIPS Options. (line 381) ! * mno-mmicromips: MIPS Options. (line 386) ! * mno-module: RS/6000 and PowerPC Options. ! (line 324) ! * mno-mpy: ARC Options. (line 59) ! * mno-ms-bitfields: x86 Options. (line 860) ! * mno-mt: MIPS Options. (line 394) ! * mno-mul-bug-workaround: CRIS Options. (line 32) ! * mno-muladd: FRV Options. (line 68) * mno-mulhw: RS/6000 and PowerPC Options. ! (line 531) * mno-mult-bug: MN10300 Options. (line 13) ! * mno-multi-cond-exec: FRV Options. (line 223) * mno-multiple: RS/6000 and PowerPC Options. ! (line 481) * mno-mvcle: S/390 and zSeries Options. ! (line 138) ! * mno-nested-cond-exec: FRV Options. (line 237) ! * mno-odd-spreg: MIPS Options. (line 292) * mno-omit-leaf-frame-pointer: AArch64 Options. (line 57) ! * mno-optimize-membar: FRV Options. (line 249) * mno-opts: MeP Options. (line 93) ! * mno-pack: FRV Options. (line 151) * mno-packed-stack: S/390 and zSeries Options. (line 54) * mno-paired: RS/6000 and PowerPC Options. (line 214) ! * mno-paired-single: MIPS Options. (line 369) * mno-perf-ext: NDS32 Options. (line 30) * mno-pic: IA-64 Options. (line 26) * mno-pid: RX Options. (line 117) ! * mno-plt: MIPS Options. (line 218) ! * mno-popc: SPARC Options. (line 251) * mno-popcntb: RS/6000 and PowerPC Options. (line 27) * mno-popcntd: RS/6000 and PowerPC Options. (line 27) * mno-postinc: Adapteva Epiphany Options. ! (line 109) * mno-postmodify: Adapteva Epiphany Options. ! (line 109) * mno-power8-fusion: RS/6000 and PowerPC Options. (line 247) * mno-power8-vector: RS/6000 and PowerPC Options. (line 253) - * mno-power9-dform: RS/6000 and PowerPC Options. - (line 343) - * mno-power9-fusion: RS/6000 and PowerPC Options. - (line 330) - * mno-power9-vector: RS/6000 and PowerPC Options. - (line 336) * mno-powerpc-gfxopt: RS/6000 and PowerPC Options. (line 27) * mno-powerpc-gpopt: RS/6000 and PowerPC Options. --- 53092,53572 ---- * mglibc: GNU/Linux Options. (line 9) * mgnu: VAX Options. (line 13) * mgnu-as: IA-64 Options. (line 18) * mgnu-ld <1>: IA-64 Options. (line 23) + * mgnu-ld: HPPA Options. (line 104) * mgotplt: CRIS Options. (line 81) ! * mgp32: MIPS Options. (line 254) ! * mgp64: MIPS Options. (line 257) ! * mgpopt <1>: Nios II Options. (line 17) ! * mgpopt: MIPS Options. (line 483) * mgpr-32: FRV Options. (line 7) ! * mgpr-64: FRV Options. (line 10) ! * mgprel-ro: FRV Options. (line 79) * mh: H8/300 Options. (line 14) ! * mhal: Nios II Options. (line 285) * mhalf-reg-file: Adapteva Epiphany Options. (line 9) * mhard-dfp <1>: S/390 and zSeries Options. (line 20) ! * mhard-dfp: RS/6000 and PowerPC Options. ! (line 27) ! * mhard-float <1>: Visium Options. (line 19) ! * mhard-float <2>: V850 Options. (line 113) ! * mhard-float <3>: SPARC Options. (line 35) ! * mhard-float <4>: S/390 and zSeries Options. (line 11) ! * mhard-float <5>: RS/6000 and PowerPC Options. ! (line 431) ! * mhard-float <6>: MIPS Options. (line 269) ! * mhard-float <7>: MicroBlaze Options. (line 10) ! * mhard-float <8>: M680x0 Options. (line 197) ! * mhard-float: FRV Options. (line 19) ! * mhard-quad-float: SPARC Options. (line 56) * mhardlit: MCore Options. (line 10) ! * mhint-max-distance: SPU Options. (line 102) ! * mhint-max-nops: SPU Options. (line 96) * mhotpatch: S/390 and zSeries Options. ! (line 206) * mhp-ld: HPPA Options. (line 116) + * mhtm <1>: S/390 and zSeries Options. + (line 105) * mhtm: RS/6000 and PowerPC Options. (line 241) ! * mhw-div: Nios II Options. (line 103) ! * mhw-mul: Nios II Options. (line 103) ! * mhw-mulx: Nios II Options. (line 103) * mhwmult=: MSP430 Options. (line 63) ! * miamcu: x86 Options. (line 1125) ! * micplb: Blackfin Options. (line 178) ! * mid-shared-library: Blackfin Options. (line 81) * mieee <1>: SH Options. (line 165) + * mieee: DEC Alpha Options. (line 39) * mieee-conformant: DEC Alpha Options. (line 134) ! * mieee-fp: x86 Options. (line 368) * mieee-with-inexact: DEC Alpha Options. (line 52) * milp32: IA-64 Options. (line 121) ! * mimadd: MIPS Options. (line 592) ! * mimpure-text: Solaris 2 Options. (line 16) ! * mincoming-stack-boundary: x86 Options. (line 582) ! * mindexed-loads: ARC Options. (line 371) ! * minline-all-stringops: x86 Options. (line 992) * minline-float-divide-max-throughput: IA-64 Options. (line 58) * minline-float-divide-min-latency: IA-64 Options. (line 54) * minline-ic_invalidate: SH Options. (line 174) * minline-int-divide-max-throughput: IA-64 Options. (line 69) * minline-int-divide-min-latency: IA-64 Options. (line 65) ! * minline-plt <1>: FRV Options. (line 64) ! * minline-plt: Blackfin Options. (line 138) * minline-sqrt-max-throughput: IA-64 Options. (line 80) * minline-sqrt-min-latency: IA-64 Options. (line 76) ! * minline-stringops-dynamically: x86 Options. (line 999) * minrt: MSP430 Options. (line 85) * minsert-sched-nops: RS/6000 and PowerPC Options. ! (line 614) * mint-register: RX Options. (line 100) * mint16: PDP-11 Options. (line 40) + * mint32 <1>: PDP-11 Options. (line 44) + * mint32 <2>: H8/300 Options. (line 38) * mint32: CR16 Options. (line 22) ! * mint8: AVR Options. (line 172) ! * minterlink-compressed: MIPS Options. (line 136) ! * minterlink-mips16: MIPS Options. (line 148) * mio-volatile: MeP Options. (line 74) ! * mips1: MIPS Options. (line 80) ! * mips16: MIPS Options. (line 120) ! * mips2: MIPS Options. (line 83) ! * mips3: MIPS Options. (line 86) ! * mips32: MIPS Options. (line 92) ! * mips32r3: MIPS Options. (line 95) ! * mips32r5: MIPS Options. (line 98) ! * mips32r6: MIPS Options. (line 101) ! * mips3d: MIPS Options. (line 384) ! * mips4: MIPS Options. (line 89) ! * mips64: MIPS Options. (line 104) ! * mips64r2: MIPS Options. (line 107) ! * mips64r3: MIPS Options. (line 110) ! * mips64r5: MIPS Options. (line 113) ! * mips64r6: MIPS Options. (line 116) * misel: RS/6000 and PowerPC Options. (line 195) * misize <1>: SH Options. (line 186) + * misize: ARC Options. (line 271) * misr-vector-size: NDS32 Options. (line 45) * missue-rate=NUMBER: M32R/D Options. (line 79) * mivc2: MeP Options. (line 59) * mjsr: RX Options. (line 169) * mjump-in-delay: HPPA Options. (line 23) * mkernel: Darwin Options. (line 82) ! * mknuthdiv: MMIX Options. (line 33) * ml <1>: SH Options. (line 129) + * ml: MeP Options. (line 78) * mlarge: MSP430 Options. (line 52) * mlarge-data: DEC Alpha Options. (line 187) ! * mlarge-data-threshold: x86 Options. (line 468) ! * mlarge-mem: SPU Options. (line 35) * mlarge-text: DEC Alpha Options. (line 205) * mleadz: MeP Options. (line 81) ! * mleaf-id-shared-library: Blackfin Options. (line 92) * mlibfuncs: MMIX Options. (line 10) ! * mlibrary-pic: FRV Options. (line 110) ! * mlinked-fp: FRV Options. (line 94) * mlinker-opt: HPPA Options. (line 78) * mlinux: CRIS Options. (line 91) * mlittle: RS/6000 and PowerPC Options. ! (line 563) ! * mlittle-endian <1>: TILE-Gx Options. (line 29) ! * mlittle-endian <2>: RS/6000 and PowerPC Options. ! (line 563) ! * mlittle-endian <3>: NDS32 Options. (line 12) ! * mlittle-endian <4>: MicroBlaze Options. (line 60) * mlittle-endian <5>: MCore Options. (line 39) ! * mlittle-endian <6>: IA-64 Options. (line 13) ! * mlittle-endian <7>: C6X Options. (line 16) ! * mlittle-endian <8>: ARM Options. (line 57) ! * mlittle-endian <9>: ARC Options. (line 488) ! * mlittle-endian: AArch64 Options. (line 30) * mlittle-endian-data: RX Options. (line 42) * mliw: MN10300 Options. (line 54) ! * mll64: ARC Options. (line 112) ! * mllsc: MIPS Options. (line 341) ! * mlocal-sdata: MIPS Options. (line 448) ! * mlock: ARC Options. (line 236) ! * mlong-calls <1>: V850 Options. (line 10) ! * mlong-calls <2>: MIPS Options. (line 578) ! * mlong-calls <3>: FRV Options. (line 99) ! * mlong-calls <4>: Blackfin Options. (line 121) ! * mlong-calls <5>: ARM Options. (line 204) ! * mlong-calls <6>: ARC Options. (line 296) * mlong-calls: Adapteva Epiphany Options. (line 55) ! * mlong-double-128 <1>: x86 Options. (line 448) * mlong-double-128: S/390 and zSeries Options. (line 29) ! * mlong-double-64 <1>: x86 Options. (line 448) * mlong-double-64: S/390 and zSeries Options. (line 29) ! * mlong-double-80: x86 Options. (line 448) * mlong-jumps: V850 Options. (line 108) * mlong-load-store: HPPA Options. (line 59) ! * mlong32: MIPS Options. (line 423) ! * mlong64: MIPS Options. (line 418) * mlongcall: RS/6000 and PowerPC Options. ! (line 823) * mlongcalls: Xtensa Options. (line 87) * mloop: V850 Options. (line 121) ! * mlow-64k: Blackfin Options. (line 70) * mlp64: IA-64 Options. (line 121) ! * mlra <1>: RS/6000 and PowerPC Options. (line 203) ! * mlra <2>: FT32 Options. (line 16) ! * mlra: ARC Options. (line 375) ! * mlra-priority-compact: ARC Options. (line 383) ! * mlra-priority-noncompact: ARC Options. (line 386) ! * mlra-priority-none: ARC Options. (line 380) ! * mlwp: x86 Options. (line 638) ! * mlzcnt: x86 Options. (line 644) ! * mm: MeP Options. (line 84) * MM: Preprocessor Options. (line 210) * mmac <1>: Score Options. (line 21) ! * mmac: CR16 Options. (line 9) ! * mmac-24: ARC Options. (line 245) ! * mmac-d16: ARC Options. (line 241) ! * mmac_24: ARC Options. (line 510) ! * mmac_d16: ARC Options. (line 513) ! * mmad: MIPS Options. (line 587) * mmainkernel: Nvidia PTX Options. (line 13) * mmalloc64: VMS Options. (line 17) * mmax: DEC Alpha Options. (line 163) * mmax-constant-size: RX Options. (line 82) ! * mmax-stack-frame: CRIS Options. (line 22) ! * mmcount-ra-address: MIPS Options. (line 844) ! * mmcu <1>: MIPS Options. (line 401) * mmcu: AVR Options. (line 9) * mmcu=: MSP430 Options. (line 14) * MMD: Preprocessor Options. ! (line 290) ! * mmedia: FRV Options. (line 44) ! * mmedium-calls: ARC Options. (line 300) ! * mmemcpy <1>: MIPS Options. (line 572) * mmemcpy: MicroBlaze Options. (line 13) ! * mmemcpy-strategy=STRATEGY: x86 Options. (line 1021) * mmemory-latency: DEC Alpha Options. (line 268) ! * mmemory-model: SPARC Options. (line 313) ! * mmemset-strategy=STRATEGY: x86 Options. (line 1033) * mmfcrf: RS/6000 and PowerPC Options. (line 27) * mmfpgpr: RS/6000 and PowerPC Options. (line 27) ! * mmicromips: MIPS Options. (line 389) * mminimal-toc: RS/6000 and PowerPC Options. ! (line 353) * mminmax: MeP Options. (line 87) ! * mmitigate-rop: x86 Options. (line 1111) ! * mmixed-code: ARC Options. (line 398) ! * mmmx: x86 Options. (line 607) * mmodel=large: M32R/D Options. (line 33) * mmodel=medium: M32R/D Options. (line 27) * mmodel=small: M32R/D Options. (line 18) ! * mmovbe: x86 Options. (line 744) ! * mmpx: x86 Options. (line 652) ! * mmpy-option: ARC Options. (line 115) ! * mms-bitfields: x86 Options. (line 868) ! * mmt: MIPS Options. (line 397) * mmul: RL78 Options. (line 15) ! * mmul-bug-workaround: CRIS Options. (line 31) * mmul.x: Moxie Options. (line 14) ! * mmul32x16: ARC Options. (line 67) ! * mmul64: ARC Options. (line 70) ! * mmuladd: FRV Options. (line 50) * mmulhw: RS/6000 and PowerPC Options. ! (line 507) * mmult: MeP Options. (line 90) * mmult-bug: MN10300 Options. (line 9) ! * mmultcost: ARC Options. (line 462) ! * mmulti-cond-exec: FRV Options. (line 176) ! * mmulticore: Blackfin Options. (line 142) * mmultiple: RS/6000 and PowerPC Options. ! (line 457) * mmusl: GNU/Linux Options. (line 18) * mmvcle: S/390 and zSeries Options. ! (line 139) * mmvme: RS/6000 and PowerPC Options. ! (line 727) ! * mmwaitx: x86 Options. (line 653) * mn: H8/300 Options. (line 20) ! * mn-flash: AVR Options. (line 178) ! * mnan=2008: MIPS Options. (line 322) ! * mnan=legacy: MIPS Options. (line 322) * mneon-for-64bits: ARM Options. (line 352) ! * mnested-cond-exec: FRV Options. (line 189) * mnhwloop: Score Options. (line 15) * mno-16-bit: NDS32 Options. (line 42) * mno-4byte-functions: MCore Options. (line 27) * mno-8byte-align: V850 Options. (line 170) ! * mno-abicalls: MIPS Options. (line 194) * mno-abshi: PDP-11 Options. (line 58) * mno-ac0: PDP-11 Options. (line 20) ! * mno-address-space-conversion: SPU Options. (line 63) ! * mno-align-double: x86 Options. (line 406) ! * mno-align-int: M680x0 Options. (line 267) * mno-align-loops: M32R/D Options. (line 76) ! * mno-align-stringops: x86 Options. (line 987) * mno-allow-string-insns: RX Options. (line 150) * mno-altivec: RS/6000 and PowerPC Options. (line 136) * mno-am33: MN10300 Options. (line 20) * mno-app-regs <1>: V850 Options. (line 185) + * mno-app-regs: SPARC Options. (line 10) * mno-as100-syntax: RX Options. (line 76) ! * mno-atomic-updates: SPU Options. (line 78) * mno-auto-litpools: Xtensa Options. (line 60) * mno-avoid-indexed-addresses: RS/6000 and PowerPC Options. ! (line 489) * mno-backchain: S/390 and zSeries Options. (line 35) ! * mno-base-addresses: MMIX Options. (line 54) * mno-bit-align: RS/6000 and PowerPC Options. ! (line 521) ! * mno-bitfield: M680x0 Options. (line 231) ! * mno-branch-likely: MIPS Options. (line 764) ! * mno-branch-predict: MMIX Options. (line 49) ! * mno-brcc: ARC Options. (line 336) * mno-bwx: DEC Alpha Options. (line 163) ! * mno-bypass-cache: Nios II Options. (line 82) ! * mno-cache-volatile: Nios II Options. (line 88) * mno-callgraph-data: MCore Options. (line 31) ! * mno-cbcond: SPARC Options. (line 247) ! * mno-check-zero-division: MIPS Options. (line 551) * mno-cix: DEC Alpha Options. (line 163) * mno-clearbss: MicroBlaze Options. (line 16) * mno-cmov: NDS32 Options. (line 24) * mno-cmpb: RS/6000 and PowerPC Options. (line 27) ! * mno-cond-exec <1>: FRV Options. (line 158) ! * mno-cond-exec: ARC Options. (line 348) ! * mno-cond-move: FRV Options. (line 134) * mno-const-align: CRIS Options. (line 55) * mno-const16: Xtensa Options. (line 10) * mno-crt0 <1>: Moxie Options. (line 18) + * mno-crt0: MN10300 Options. (line 43) * mno-crypto: RS/6000 and PowerPC Options. (line 229) ! * mno-csync-anomaly: Blackfin Options. (line 66) ! * mno-custom-INSN: Nios II Options. (line 118) * mno-data-align: CRIS Options. (line 55) * mno-debug: S/390 and zSeries Options. ! (line 146) ! * mno-default: x86 Options. (line 697) * mno-direct-move: RS/6000 and PowerPC Options. (line 235) * mno-disable-callt: V850 Options. (line 92) * mno-div <1>: MCore Options. (line 15) + * mno-div: M680x0 Options. (line 209) * mno-dlmzb: RS/6000 and PowerPC Options. ! (line 514) ! * mno-double: FRV Options. (line 41) ! * mno-dpfp-lrsr: ARC Options. (line 55) ! * mno-dsp: MIPS Options. (line 355) ! * mno-dspr2: MIPS Options. (line 361) * mno-dwarf2-asm: IA-64 Options. (line 94) ! * mno-dword: FRV Options. (line 35) * mno-eabi: RS/6000 and PowerPC Options. ! (line 751) * mno-early-stop-bits: IA-64 Options. (line 100) ! * mno-eflags: FRV Options. (line 125) ! * mno-embedded-data: MIPS Options. (line 498) * mno-ep: V850 Options. (line 16) * mno-epsilon: MMIX Options. (line 15) ! * mno-eva: MIPS Options. (line 405) ! * mno-explicit-relocs <1>: MIPS Options. (line 542) * mno-explicit-relocs: DEC Alpha Options. (line 176) * mno-exr: H8/300 Options. (line 33) ! * mno-extern-sdata: MIPS Options. (line 460) ! * mno-fancy-math-387: x86 Options. (line 396) ! * mno-fast-sw-div: Nios II Options. (line 94) ! * mno-faster-structs: SPARC Options. (line 92) * mno-fix: DEC Alpha Options. (line 163) ! * mno-fix-24k: MIPS Options. (line 617) * mno-fix-cortex-a53-835769: AArch64 Options. (line 74) * mno-fix-cortex-a53-843419: AArch64 Options. (line 81) ! * mno-fix-r10000: MIPS Options. (line 644) ! * mno-fix-r4000: MIPS Options. (line 623) ! * mno-fix-r4400: MIPS Options. (line 637) * mno-flat: SPARC Options. (line 22) ! * mno-float: MIPS Options. (line 276) * mno-float128: RS/6000 and PowerPC Options. ! (line 298) * mno-float128-hardware: RS/6000 and PowerPC Options. ! (line 313) * mno-float32: PDP-11 Options. (line 48) * mno-float64: PDP-11 Options. (line 52) * mno-flush-func: M32R/D Options. (line 98) * mno-flush-trap: M32R/D Options. (line 90) ! * mno-fmaf: SPARC Options. (line 261) * mno-fp-in-toc: RS/6000 and PowerPC Options. ! (line 353) * mno-fp-regs: DEC Alpha Options. (line 25) ! * mno-fp-ret-in-387: x86 Options. (line 386) * mno-fprnd: RS/6000 and PowerPC Options. (line 27) * mno-fpu <1>: Visium Options. (line 24) ! * mno-fpu: SPARC Options. (line 40) ! * mno-fsca: SH Options. (line 369) ! * mno-fsrra: SH Options. (line 378) ! * mno-fused-madd <1>: Xtensa Options. (line 19) ! * mno-fused-madd <2>: SH Options. (line 360) * mno-fused-madd <3>: S/390 and zSeries Options. ! (line 170) ! * mno-fused-madd <4>: RS/6000 and PowerPC Options. ! (line 498) ! * mno-fused-madd <5>: MIPS Options. (line 599) ! * mno-fused-madd: IA-64 Options. (line 88) * mno-gnu-as: IA-64 Options. (line 18) * mno-gnu-ld: IA-64 Options. (line 23) * mno-gotplt: CRIS Options. (line 81) ! * mno-gpopt <1>: Nios II Options. (line 17) ! * mno-gpopt: MIPS Options. (line 483) * mno-hard-dfp <1>: S/390 and zSeries Options. (line 20) + * mno-hard-dfp: RS/6000 and PowerPC Options. + (line 27) * mno-hardlit: MCore Options. (line 10) + * mno-htm <1>: S/390 and zSeries Options. + (line 105) * mno-htm: RS/6000 and PowerPC Options. (line 241) ! * mno-hw-div: Nios II Options. (line 103) ! * mno-hw-mul: Nios II Options. (line 103) ! * mno-hw-mulx: Nios II Options. (line 103) ! * mno-id-shared-library: Blackfin Options. (line 88) * mno-ieee: SH Options. (line 165) ! * mno-ieee-fp: x86 Options. (line 368) ! * mno-imadd: MIPS Options. (line 592) * mno-inline-float-divide: IA-64 Options. (line 62) * mno-inline-int-divide: IA-64 Options. (line 73) * mno-inline-sqrt: IA-64 Options. (line 84) * mno-int16: PDP-11 Options. (line 44) * mno-int32: PDP-11 Options. (line 40) ! * mno-interlink-compressed: MIPS Options. (line 136) ! * mno-interlink-mips16: MIPS Options. (line 148) ! * mno-interrupts: AVR Options. (line 181) * mno-isel: RS/6000 and PowerPC Options. (line 195) * mno-jsr: RX Options. (line 169) ! * mno-knuthdiv: MMIX Options. (line 33) ! * mno-leaf-id-shared-library: Blackfin Options. (line 98) * mno-libfuncs: MMIX Options. (line 10) ! * mno-llsc: MIPS Options. (line 341) ! * mno-local-sdata: MIPS Options. (line 448) ! * mno-long-calls <1>: V850 Options. (line 10) ! * mno-long-calls <2>: MIPS Options. (line 578) ! * mno-long-calls <3>: HPPA Options. (line 129) ! * mno-long-calls <4>: Blackfin Options. (line 121) ! * mno-long-calls: ARM Options. (line 204) * mno-long-jumps: V850 Options. (line 108) * mno-longcall: RS/6000 and PowerPC Options. ! (line 823) * mno-longcalls: Xtensa Options. (line 87) ! * mno-low-64k: Blackfin Options. (line 74) * mno-lsim <1>: MCore Options. (line 46) ! * mno-lsim: FR30 Options. (line 14) ! * mno-mad: MIPS Options. (line 587) * mno-max: DEC Alpha Options. (line 163) ! * mno-mcount-ra-address: MIPS Options. (line 844) ! * mno-mcu: MIPS Options. (line 401) ! * mno-mdmx: MIPS Options. (line 378) ! * mno-media: FRV Options. (line 47) ! * mno-memcpy: MIPS Options. (line 572) * mno-mfcrf: RS/6000 and PowerPC Options. (line 27) * mno-mfpgpr: RS/6000 and PowerPC Options. (line 27) ! * mno-millicode: ARC Options. (line 389) ! * mno-mips16: MIPS Options. (line 120) ! * mno-mips3d: MIPS Options. (line 384) ! * mno-mmicromips: MIPS Options. (line 389) ! * mno-mpy: ARC Options. (line 64) ! * mno-ms-bitfields: x86 Options. (line 868) ! * mno-mt: MIPS Options. (line 397) ! * mno-mul-bug-workaround: CRIS Options. (line 31) ! * mno-muladd: FRV Options. (line 53) * mno-mulhw: RS/6000 and PowerPC Options. ! (line 507) * mno-mult-bug: MN10300 Options. (line 13) ! * mno-multi-cond-exec: FRV Options. (line 183) * mno-multiple: RS/6000 and PowerPC Options. ! (line 457) * mno-mvcle: S/390 and zSeries Options. ! (line 139) ! * mno-nested-cond-exec: FRV Options. (line 195) ! * mno-odd-spreg: MIPS Options. (line 295) * mno-omit-leaf-frame-pointer: AArch64 Options. (line 57) ! * mno-optimize-membar: FRV Options. (line 205) * mno-opts: MeP Options. (line 93) ! * mno-pack: FRV Options. (line 122) * mno-packed-stack: S/390 and zSeries Options. (line 54) * mno-paired: RS/6000 and PowerPC Options. (line 214) ! * mno-paired-single: MIPS Options. (line 372) * mno-perf-ext: NDS32 Options. (line 30) * mno-pic: IA-64 Options. (line 26) * mno-pid: RX Options. (line 117) ! * mno-plt: MIPS Options. (line 221) ! * mno-popc: SPARC Options. (line 254) * mno-popcntb: RS/6000 and PowerPC Options. (line 27) * mno-popcntd: RS/6000 and PowerPC Options. (line 27) * mno-postinc: Adapteva Epiphany Options. ! (line 110) * mno-postmodify: Adapteva Epiphany Options. ! (line 110) * mno-power8-fusion: RS/6000 and PowerPC Options. (line 247) * mno-power8-vector: RS/6000 and PowerPC Options. (line 253) * mno-powerpc-gfxopt: RS/6000 and PowerPC Options. (line 27) * mno-powerpc-gpopt: RS/6000 and PowerPC Options. *************** look up both forms. *** 52995,53021 **** * mno-prolog-function: V850 Options. (line 23) * mno-prologue-epilogue: CRIS Options. (line 71) * mno-prototype: RS/6000 and PowerPC Options. ! (line 735) ! * mno-push-args: x86 Options. (line 837) * mno-quad-memory: RS/6000 and PowerPC Options. (line 260) * mno-quad-memory-atomic: RS/6000 and PowerPC Options. (line 266) ! * mno-red-zone: x86 Options. (line 1136) * mno-register-names: IA-64 Options. (line 37) * mno-regnames: RS/6000 and PowerPC Options. ! (line 840) * mno-relax: V850 Options. (line 103) * mno-relax-immediate: MCore Options. (line 19) * mno-relocatable: RS/6000 and PowerPC Options. ! (line 561) * mno-relocatable-lib: RS/6000 and PowerPC Options. ! (line 572) * mno-renesas: SH Options. (line 155) * mno-round-nearest: Adapteva Epiphany Options. (line 51) ! * mno-rtd: M680x0 Options. (line 258) ! * mno-scc: FRV Options. (line 180) * mno-sched-ar-data-spec: IA-64 Options. (line 135) * mno-sched-ar-in-data-spec: IA-64 Options. (line 157) * mno-sched-br-data-spec: IA-64 Options. (line 128) --- 53576,53602 ---- * mno-prolog-function: V850 Options. (line 23) * mno-prologue-epilogue: CRIS Options. (line 71) * mno-prototype: RS/6000 and PowerPC Options. ! (line 711) ! * mno-push-args: x86 Options. (line 844) * mno-quad-memory: RS/6000 and PowerPC Options. (line 260) * mno-quad-memory-atomic: RS/6000 and PowerPC Options. (line 266) ! * mno-red-zone: x86 Options. (line 1145) * mno-register-names: IA-64 Options. (line 37) * mno-regnames: RS/6000 and PowerPC Options. ! (line 817) * mno-relax: V850 Options. (line 103) * mno-relax-immediate: MCore Options. (line 19) * mno-relocatable: RS/6000 and PowerPC Options. ! (line 537) * mno-relocatable-lib: RS/6000 and PowerPC Options. ! (line 548) * mno-renesas: SH Options. (line 155) * mno-round-nearest: Adapteva Epiphany Options. (line 51) ! * mno-rtd: M680x0 Options. (line 262) ! * mno-scc: FRV Options. (line 146) * mno-sched-ar-data-spec: IA-64 Options. (line 135) * mno-sched-ar-in-data-spec: IA-64 Options. (line 157) * mno-sched-br-data-spec: IA-64 Options. (line 128) *************** look up both forms. *** 53026,53172 **** * mno-sched-prefer-non-control-spec-insns: IA-64 Options. (line 178) * mno-sched-prefer-non-data-spec-insns: IA-64 Options. (line 171) * mno-sched-prolog: ARM Options. (line 32) ! * mno-sdata: ARC Options. (line 299) ! * mno-sdata <1>: IA-64 Options. (line 42) ! * mno-sdata <2>: RS/6000 and PowerPC Options. ! (line 821) ! * mno-sep-data: Blackfin Options. (line 115) * mno-serialize-volatile: Xtensa Options. (line 35) ! * mno-short: M680x0 Options. (line 222) * mno-side-effects: CRIS Options. (line 46) * mno-sim: RX Options. (line 71) ! * mno-single-exit: MMIX Options. (line 65) * mno-slow-bytes: MCore Options. (line 35) * mno-small-exec: S/390 and zSeries Options. ! (line 79) ! * mno-smartmips: MIPS Options. (line 365) * mno-soft-cmpsf: Adapteva Epiphany Options. (line 29) * mno-soft-float: DEC Alpha Options. (line 10) * mno-space-regs: HPPA Options. (line 38) * mno-spe: RS/6000 and PowerPC Options. (line 209) ! * mno-specld-anomaly: Blackfin Options. (line 55) ! * mno-split-addresses: MIPS Options. (line 532) * mno-stack-align: CRIS Options. (line 55) ! * mno-stack-bias: SPARC Options. (line 334) ! * mno-std-struct-return: SPARC Options. (line 102) ! * mno-strict-align: M680x0 Options. (line 283) * mno-strict-align <1>: RS/6000 and PowerPC Options. ! (line 556) * mno-string: RS/6000 and PowerPC Options. ! (line 492) * mno-sum-in-toc: RS/6000 and PowerPC Options. ! (line 378) ! * mno-sym32: MIPS Options. (line 430) * mno-target-align: Xtensa Options. (line 74) * mno-text-section-literals: Xtensa Options. (line 47) * mno-tls-markers: RS/6000 and PowerPC Options. ! (line 878) * mno-toc: RS/6000 and PowerPC Options. ! (line 581) ! * mno-toplevel-symbols: MMIX Options. (line 39) * mno-tpf-trace: S/390 and zSeries Options. ! (line 162) * mno-unaligned-access: ARM Options. (line 339) ! * mno-unaligned-doubles: SPARC Options. (line 73) ! * mno-uninit-const-in-rodata: MIPS Options. (line 502) * mno-update: RS/6000 and PowerPC Options. ! (line 503) * mno-upper-regs: RS/6000 and PowerPC Options. ! (line 288) * mno-upper-regs-df: RS/6000 and PowerPC Options. (line 272) * mno-upper-regs-sf: RS/6000 and PowerPC Options. (line 280) ! * mno-user-mode: SPARC Options. (line 85) ! * mno-usermode: SH Options. (line 274) * mno-v3push: NDS32 Options. (line 36) ! * mno-v8plus: SPARC Options. (line 207) * mno-vect-double: Adapteva Epiphany Options. ! (line 115) ! * mno-virt: MIPS Options. (line 406) ! * mno-vis: SPARC Options. (line 214) ! * mno-vis2: SPARC Options. (line 220) ! * mno-vis3: SPARC Options. (line 228) ! * mno-vis4: SPARC Options. (line 236) ! * mno-vliw-branch: FRV Options. (line 208) * mno-volatile-asm-stop: IA-64 Options. (line 32) ! * mno-volatile-cache: ARC Options. (line 313) * mno-vrsave: RS/6000 and PowerPC Options. (line 174) * mno-vsx: RS/6000 and PowerPC Options. (line 223) * mno-vx: S/390 and zSeries Options. ! (line 112) * mno-warn-mcu: MSP430 Options. (line 35) * mno-warn-multiple-fast-interrupts: RX Options. (line 143) * mno-wide-bitfields: MCore Options. (line 23) ! * mno-xgot: M680x0 Options. (line 315) ! * mno-xgot <1>: MIPS Options. (line 228) * mno-xl-compat: RS/6000 and PowerPC Options. ! (line 413) ! * mno-xpa: MIPS Options. (line 411) ! * mno-zdcbranch: SH Options. (line 341) ! * mno-zero-extend: MMIX Options. (line 26) * mno-zvector: S/390 and zSeries Options. ! (line 123) ! * mnobitfield: M680x0 Options. (line 227) * mnodiv: FT32 Options. (line 20) * mnoliw: MN10300 Options. (line 59) * mnomacsave: SH Options. (line 160) * mnop-fun-dllimport: x86 Windows Options. (line 22) ! * mnop-mcount: x86 Options. (line 1066) * mnops: Adapteva Epiphany Options. (line 26) ! * mnorm: ARC Options. (line 69) * mnosetlb: MN10300 Options. (line 69) * mnosplit-lohi: Adapteva Epiphany Options. ! (line 109) ! * modd-spreg: MIPS Options. (line 292) * momit-leaf-frame-pointer: AArch64 Options. (line 57) - * momit-leaf-frame-pointer <1>: Blackfin Options. (line 43) - * momit-leaf-frame-pointer <2>: x86 Options. (line 1030) * mone-byte-bool: Darwin Options. (line 90) * moptimize: Nvidia PTX Options. (line 17) ! * moptimize-membar: FRV Options. (line 244) ! * moverride: AArch64 Options. (line 168) * MP: Preprocessor Options. (line 239) * mpa-risc-1-0: HPPA Options. (line 19) * mpa-risc-1-1: HPPA Options. (line 19) * mpa-risc-2-0: HPPA Options. (line 19) ! * mpack: FRV Options. (line 147) * mpacked-stack: S/390 and zSeries Options. (line 54) * mpadstruct: SH Options. (line 189) * mpaired: RS/6000 and PowerPC Options. (line 214) ! * mpaired-single: MIPS Options. (line 369) ! * mpc32: x86 Options. (line 525) ! * mpc64: x86 Options. (line 525) ! * mpc80: x86 Options. (line 525) ! * mpclmul: x86 Options. (line 623) ! * mpcrel: M680x0 Options. (line 275) ! * mpcrelativeliteralloads: AArch64 Options. (line 176) ! * mpdebug: CRIS Options. (line 36) * mpe: RS/6000 and PowerPC Options. ! (line 432) * mpe-aligned-commons: x86 Windows Options. (line 59) * mperf-ext: NDS32 Options. (line 27) ! * mpic-data-is-text-relative: ARM Options. (line 240) ! * mpic-register: ARM Options. (line 233) * mpid: RX Options. (line 117) ! * mpku: x86 Options. (line 649) ! * mplt: MIPS Options. (line 218) * mpointer-size=SIZE: VMS Options. (line 20) * mpointers-to-nested-functions: RS/6000 and PowerPC Options. ! (line 983) ! * mpoke-function-name: ARM Options. (line 246) ! * mpopc: SPARC Options. (line 251) ! * mpopcnt: x86 Options. (line 634) * mpopcntb: RS/6000 and PowerPC Options. (line 27) * mpopcntd: RS/6000 and PowerPC Options. --- 53607,53753 ---- * mno-sched-prefer-non-control-spec-insns: IA-64 Options. (line 178) * mno-sched-prefer-non-data-spec-insns: IA-64 Options. (line 171) * mno-sched-prolog: ARM Options. (line 32) ! * mno-sdata <1>: RS/6000 and PowerPC Options. ! (line 798) ! * mno-sdata <2>: IA-64 Options. (line 42) ! * mno-sdata: ARC Options. (line 308) ! * mno-sep-data: Blackfin Options. (line 116) * mno-serialize-volatile: Xtensa Options. (line 35) ! * mno-short: M680x0 Options. (line 226) * mno-side-effects: CRIS Options. (line 46) * mno-sim: RX Options. (line 71) ! * mno-single-exit: MMIX Options. (line 66) * mno-slow-bytes: MCore Options. (line 35) * mno-small-exec: S/390 and zSeries Options. ! (line 80) ! * mno-smartmips: MIPS Options. (line 368) * mno-soft-cmpsf: Adapteva Epiphany Options. (line 29) * mno-soft-float: DEC Alpha Options. (line 10) * mno-space-regs: HPPA Options. (line 38) * mno-spe: RS/6000 and PowerPC Options. (line 209) ! * mno-specld-anomaly: Blackfin Options. (line 56) ! * mno-split-addresses: MIPS Options. (line 536) * mno-stack-align: CRIS Options. (line 55) ! * mno-stack-bias: SPARC Options. (line 337) ! * mno-std-struct-return: SPARC Options. (line 103) * mno-strict-align <1>: RS/6000 and PowerPC Options. ! (line 532) ! * mno-strict-align: M680x0 Options. (line 287) * mno-string: RS/6000 and PowerPC Options. ! (line 468) * mno-sum-in-toc: RS/6000 and PowerPC Options. ! (line 353) ! * mno-sym32: MIPS Options. (line 433) * mno-target-align: Xtensa Options. (line 74) * mno-text-section-literals: Xtensa Options. (line 47) * mno-tls-markers: RS/6000 and PowerPC Options. ! (line 856) * mno-toc: RS/6000 and PowerPC Options. ! (line 557) ! * mno-toplevel-symbols: MMIX Options. (line 40) * mno-tpf-trace: S/390 and zSeries Options. ! (line 164) * mno-unaligned-access: ARM Options. (line 339) ! * mno-unaligned-doubles: SPARC Options. (line 74) ! * mno-uninit-const-in-rodata: MIPS Options. (line 506) * mno-update: RS/6000 and PowerPC Options. ! (line 479) * mno-upper-regs: RS/6000 and PowerPC Options. ! (line 289) * mno-upper-regs-df: RS/6000 and PowerPC Options. (line 272) * mno-upper-regs-sf: RS/6000 and PowerPC Options. (line 280) ! * mno-user-mode: SPARC Options. (line 86) ! * mno-usermode: SH Options. (line 276) * mno-v3push: NDS32 Options. (line 36) ! * mno-v8plus: SPARC Options. (line 210) * mno-vect-double: Adapteva Epiphany Options. ! (line 116) ! * mno-virt: MIPS Options. (line 409) ! * mno-vis: SPARC Options. (line 217) ! * mno-vis2: SPARC Options. (line 223) ! * mno-vis3: SPARC Options. (line 231) ! * mno-vis4: SPARC Options. (line 239) ! * mno-vliw-branch: FRV Options. (line 170) * mno-volatile-asm-stop: IA-64 Options. (line 32) ! * mno-volatile-cache: ARC Options. (line 322) * mno-vrsave: RS/6000 and PowerPC Options. (line 174) * mno-vsx: RS/6000 and PowerPC Options. (line 223) * mno-vx: S/390 and zSeries Options. ! (line 113) * mno-warn-mcu: MSP430 Options. (line 35) * mno-warn-multiple-fast-interrupts: RX Options. (line 143) * mno-wide-bitfields: MCore Options. (line 23) ! * mno-xgot <1>: MIPS Options. (line 231) ! * mno-xgot: M680x0 Options. (line 319) * mno-xl-compat: RS/6000 and PowerPC Options. ! (line 388) ! * mno-xpa: MIPS Options. (line 414) ! * mno-zdcbranch: SH Options. (line 345) ! * mno-zero-extend: MMIX Options. (line 27) * mno-zvector: S/390 and zSeries Options. ! (line 124) ! * mnobitfield: M680x0 Options. (line 231) * mnodiv: FT32 Options. (line 20) * mnoliw: MN10300 Options. (line 59) * mnomacsave: SH Options. (line 160) * mnop-fun-dllimport: x86 Windows Options. (line 22) ! * mnop-mcount: x86 Options. (line 1073) * mnops: Adapteva Epiphany Options. (line 26) ! * mnorm: ARC Options. (line 74) * mnosetlb: MN10300 Options. (line 69) * mnosplit-lohi: Adapteva Epiphany Options. ! (line 110) ! * modd-spreg: MIPS Options. (line 295) ! * momit-leaf-frame-pointer <1>: x86 Options. (line 1037) ! * momit-leaf-frame-pointer <2>: Blackfin Options. (line 44) * momit-leaf-frame-pointer: AArch64 Options. (line 57) * mone-byte-bool: Darwin Options. (line 90) * moptimize: Nvidia PTX Options. (line 17) ! * moptimize-membar: FRV Options. (line 201) ! * moverride: AArch64 Options. (line 169) * MP: Preprocessor Options. (line 239) * mpa-risc-1-0: HPPA Options. (line 19) * mpa-risc-1-1: HPPA Options. (line 19) * mpa-risc-2-0: HPPA Options. (line 19) ! * mpack: FRV Options. (line 119) * mpacked-stack: S/390 and zSeries Options. (line 54) * mpadstruct: SH Options. (line 189) * mpaired: RS/6000 and PowerPC Options. (line 214) ! * mpaired-single: MIPS Options. (line 372) ! * mpc32: x86 Options. (line 531) ! * mpc64: x86 Options. (line 531) ! * mpc80: x86 Options. (line 531) ! * mpclmul: x86 Options. (line 629) ! * mpcrel: M680x0 Options. (line 279) ! * mpcrelativeliteralloads: AArch64 Options. (line 177) ! * mpdebug: CRIS Options. (line 35) * mpe: RS/6000 and PowerPC Options. ! (line 408) * mpe-aligned-commons: x86 Windows Options. (line 59) * mperf-ext: NDS32 Options. (line 27) ! * mpic-data-is-text-relative: ARM Options. (line 241) ! * mpic-register: ARM Options. (line 234) * mpid: RX Options. (line 117) ! * mpku: x86 Options. (line 655) ! * mplt: MIPS Options. (line 221) * mpointer-size=SIZE: VMS Options. (line 20) * mpointers-to-nested-functions: RS/6000 and PowerPC Options. ! (line 962) ! * mpoke-function-name: ARM Options. (line 247) ! * mpopc: SPARC Options. (line 254) ! * mpopcnt: x86 Options. (line 640) * mpopcntb: RS/6000 and PowerPC Options. (line 27) * mpopcntd: RS/6000 and PowerPC Options. *************** look up both forms. *** 53176,53279 **** (line 247) * mpower8-vector: RS/6000 and PowerPC Options. (line 253) - * mpower9-dform: RS/6000 and PowerPC Options. - (line 343) - * mpower9-fusion: RS/6000 and PowerPC Options. - (line 330) - * mpower9-vector: RS/6000 and PowerPC Options. - (line 336) * mpowerpc-gfxopt: RS/6000 and PowerPC Options. (line 27) * mpowerpc-gpopt: RS/6000 and PowerPC Options. (line 27) * mpowerpc64: RS/6000 and PowerPC Options. (line 27) ! * mprefer-avx128: x86 Options. (line 714) * mprefer-short-insn-regs: Adapteva Epiphany Options. (line 13) ! * mprefergot: SH Options. (line 268) ! * mpreferred-stack-boundary: x86 Options. (line 555) ! * mprefetchwt1: x86 Options. (line 630) ! * mpretend-cmove: SH Options. (line 383) * mprint-tune-info: ARM Options. (line 375) * mprioritize-restricted-insns: RS/6000 and PowerPC Options. ! (line 610) * mprolog-function: V850 Options. (line 23) * mprologue-epilogue: CRIS Options. (line 71) * mprototype: RS/6000 and PowerPC Options. ! (line 735) ! * mpush-args: x86 Options. (line 837) * MQ: Preprocessor Options. ! (line 266) ! * mq-class: ARC Options. (line 393) * mquad-memory: RS/6000 and PowerPC Options. (line 260) * mquad-memory-atomic: RS/6000 and PowerPC Options. (line 266) ! * mr10k-cache-barrier: MIPS Options. (line 674) ! * mRcq: ARC Options. (line 397) ! * mRcw: ARC Options. (line 401) ! * mrdrnd: x86 Options. (line 626) * mrecip: RS/6000 and PowerPC Options. ! (line 890) ! * mrecip <1>: x86 Options. (line 747) * mrecip-precision: RS/6000 and PowerPC Options. ! (line 947) * mrecip=opt: RS/6000 and PowerPC Options. ! (line 903) ! * mrecip=opt <1>: x86 Options. (line 769) ! * mrecord-mcount: x86 Options. (line 1060) * mreduced-regs: NDS32 Options. (line 15) * mregister-names: IA-64 Options. (line 37) * mregnames: RS/6000 and PowerPC Options. ! (line 840) ! * mregparm: x86 Options. (line 492) ! * mrelax: AVR Options. (line 187) ! * mrelax <1>: H8/300 Options. (line 9) ! * mrelax <2>: MN10300 Options. (line 46) ! * mrelax <3>: MSP430 Options. (line 58) ! * mrelax <4>: NDS32 Options. (line 72) ! * mrelax <5>: RX Options. (line 95) ! * mrelax <6>: SH Options. (line 137) ! * mrelax <7>: V850 Options. (line 103) * mrelax-immediate: MCore Options. (line 19) ! * mrelax-pic-calls: MIPS Options. (line 819) * mrelocatable: RS/6000 and PowerPC Options. ! (line 561) * mrelocatable-lib: RS/6000 and PowerPC Options. ! (line 572) * mrenesas: SH Options. (line 152) * mrepeat: MeP Options. (line 96) * mrestrict-it: ARM Options. (line 369) * mreturn-pointer-on-d0: MN10300 Options. (line 36) * mrh850-abi: V850 Options. (line 127) * mrl78: RL78 Options. (line 62) ! * mrmw: AVR Options. (line 201) ! * mrtd: M680x0 Options. (line 236) ! * mrtd <1>: x86 Options. (line 468) ! * mrtd <2>: x86 Function Attributes. (line 9) ! * mrtm: x86 Options. (line 644) * mrtp: VxWorks Options. (line 11) ! * mrtsc: ARC Options. (line 241) ! * ms: H8/300 Options. (line 17) * ms <1>: MeP Options. (line 100) * ms2600: H8/300 Options. (line 24) ! * msafe-dma: SPU Options. (line 18) ! * msafe-hints: SPU Options. (line 112) ! * msahf: x86 Options. (line 727) * msatur: MeP Options. (line 105) * msave-acc-in-interrupts: RX Options. (line 109) * msave-toc-indirect: RS/6000 and PowerPC Options. ! (line 995) ! * mscc: FRV Options. (line 173) * msched-ar-data-spec: IA-64 Options. (line 135) * msched-ar-in-data-spec: IA-64 Options. (line 157) * msched-br-data-spec: IA-64 Options. (line 128) * msched-br-in-data-spec: IA-64 Options. (line 150) * msched-control-spec: IA-64 Options. (line 142) * msched-costly-dep: RS/6000 and PowerPC Options. ! (line 617) * msched-count-spec-in-critical-path: IA-64 Options. (line 185) * msched-fp-mem-deps-zero-cost: IA-64 Options. (line 202) * msched-in-control-spec: IA-64 Options. (line 164) --- 53757,53854 ---- (line 247) * mpower8-vector: RS/6000 and PowerPC Options. (line 253) * mpowerpc-gfxopt: RS/6000 and PowerPC Options. (line 27) * mpowerpc-gpopt: RS/6000 and PowerPC Options. (line 27) * mpowerpc64: RS/6000 and PowerPC Options. (line 27) ! * mprefer-avx128: x86 Options. (line 721) * mprefer-short-insn-regs: Adapteva Epiphany Options. (line 13) ! * mprefergot: SH Options. (line 270) ! * mpreferred-stack-boundary: x86 Options. (line 561) ! * mprefetchwt1: x86 Options. (line 636) ! * mpretend-cmove: SH Options. (line 387) * mprint-tune-info: ARM Options. (line 375) * mprioritize-restricted-insns: RS/6000 and PowerPC Options. ! (line 586) * mprolog-function: V850 Options. (line 23) * mprologue-epilogue: CRIS Options. (line 71) * mprototype: RS/6000 and PowerPC Options. ! (line 711) ! * mpush-args: x86 Options. (line 844) * MQ: Preprocessor Options. ! (line 265) ! * mq-class: ARC Options. (line 403) * mquad-memory: RS/6000 and PowerPC Options. (line 260) * mquad-memory-atomic: RS/6000 and PowerPC Options. (line 266) ! * mr10k-cache-barrier: MIPS Options. (line 686) ! * mRcq: ARC Options. (line 407) ! * mRcw: ARC Options. (line 411) ! * mrdrnd: x86 Options. (line 632) ! * mrecip <1>: x86 Options. (line 754) * mrecip: RS/6000 and PowerPC Options. ! (line 868) * mrecip-precision: RS/6000 and PowerPC Options. ! (line 926) ! * mrecip=opt <1>: x86 Options. (line 776) * mrecip=opt: RS/6000 and PowerPC Options. ! (line 881) ! * mrecord-mcount: x86 Options. (line 1067) * mreduced-regs: NDS32 Options. (line 15) * mregister-names: IA-64 Options. (line 37) * mregnames: RS/6000 and PowerPC Options. ! (line 817) ! * mregparm: x86 Options. (line 498) ! * mrelax <1>: V850 Options. (line 103) ! * mrelax <2>: SH Options. (line 137) ! * mrelax <3>: RX Options. (line 95) ! * mrelax <4>: NDS32 Options. (line 74) ! * mrelax <5>: MSP430 Options. (line 58) ! * mrelax <6>: MN10300 Options. (line 46) ! * mrelax <7>: H8/300 Options. (line 9) ! * mrelax: AVR Options. (line 185) * mrelax-immediate: MCore Options. (line 19) ! * mrelax-pic-calls: MIPS Options. (line 831) * mrelocatable: RS/6000 and PowerPC Options. ! (line 537) * mrelocatable-lib: RS/6000 and PowerPC Options. ! (line 548) * mrenesas: SH Options. (line 152) * mrepeat: MeP Options. (line 96) * mrestrict-it: ARM Options. (line 369) * mreturn-pointer-on-d0: MN10300 Options. (line 36) * mrh850-abi: V850 Options. (line 127) * mrl78: RL78 Options. (line 62) ! * mrmw: AVR Options. (line 199) ! * mrtd <1>: x86 Function Attributes. (line 9) ! * mrtd <2>: x86 Options. (line 474) ! * mrtd: M680x0 Options. (line 240) ! * mrtm: x86 Options. (line 650) * mrtp: VxWorks Options. (line 11) ! * mrtsc: ARC Options. (line 249) * ms <1>: MeP Options. (line 100) + * ms: H8/300 Options. (line 17) * ms2600: H8/300 Options. (line 24) ! * msafe-dma: SPU Options. (line 17) ! * msafe-hints: SPU Options. (line 107) ! * msahf: x86 Options. (line 734) * msatur: MeP Options. (line 105) * msave-acc-in-interrupts: RX Options. (line 109) * msave-toc-indirect: RS/6000 and PowerPC Options. ! (line 974) ! * mscc: FRV Options. (line 140) * msched-ar-data-spec: IA-64 Options. (line 135) * msched-ar-in-data-spec: IA-64 Options. (line 157) * msched-br-data-spec: IA-64 Options. (line 128) * msched-br-in-data-spec: IA-64 Options. (line 150) * msched-control-spec: IA-64 Options. (line 142) * msched-costly-dep: RS/6000 and PowerPC Options. ! (line 593) * msched-count-spec-in-critical-path: IA-64 Options. (line 185) * msched-fp-mem-deps-zero-cost: IA-64 Options. (line 202) * msched-in-control-spec: IA-64 Options. (line 164) *************** look up both forms. *** 53282,53355 **** * msched-prefer-non-control-spec-insns: IA-64 Options. (line 178) * msched-prefer-non-data-spec-insns: IA-64 Options. (line 171) * msched-spec-ldc: IA-64 Options. (line 191) - * msched-spec-ldc <1>: IA-64 Options. (line 194) * msched-stop-bits-after-every-cycle: IA-64 Options. (line 198) * mschedule: HPPA Options. (line 71) * mscore5: Score Options. (line 25) * mscore5u: Score Options. (line 28) * mscore7: Score Options. (line 31) ! * mscore7d: Score Options. (line 35) * msda: V850 Options. (line 40) - * msdata: IA-64 Options. (line 42) * msdata <1>: RS/6000 and PowerPC Options. ! (line 808) * msdata=all: C6X Options. (line 30) * msdata=data: RS/6000 and PowerPC Options. ! (line 813) ! * msdata=default: C6X Options. (line 22) * msdata=default <1>: RS/6000 and PowerPC Options. ! (line 808) * msdata=eabi: RS/6000 and PowerPC Options. ! (line 789) * msdata=none: C6X Options. (line 35) - * msdata=none <1>: M32R/D Options. (line 40) - * msdata=none <2>: RS/6000 and PowerPC Options. - (line 821) * msdata=sdata: M32R/D Options. (line 49) * msdata=sysv: RS/6000 and PowerPC Options. ! (line 799) * msdata=use: M32R/D Options. (line 53) - * msdram: Blackfin Options. (line 171) * msdram <1>: MeP Options. (line 110) * msecure-plt: RS/6000 and PowerPC Options. (line 184) * msel-sched-dont-check-control-spec: IA-64 Options. (line 207) ! * msep-data: Blackfin Options. (line 109) * mserialize-volatile: Xtensa Options. (line 35) * msetlb: MN10300 Options. (line 64) ! * msha: x86 Options. (line 621) ! * mshared-library-id: Blackfin Options. (line 102) ! * mshort: M680x0 Options. (line 216) * msign-extend-enabled: LM32 Options. (line 18) ! * msilicon-errata: MSP430 Options. (line 102) ! * msilicon-errata-warn: MSP430 Options. (line 106) ! * msim: Blackfin Options. (line 36) ! * msim <1>: C6X Options. (line 19) ! * msim <2>: CR16 Options. (line 18) ! * msim <3>: FT32 Options. (line 9) ! * msim <4>: M32C Options. (line 13) ! * msim <5>: MeP Options. (line 114) * msim <6>: MSP430 Options. (line 47) ! * msim <7>: RL78 Options. (line 7) ! * msim <8>: RS/6000 and PowerPC Options. ! (line 745) ! * msim <9>: RX Options. (line 71) ! * msim <10>: Visium Options. (line 13) ! * msim <11>: Xstormy16 Options. (line 9) ! * msimd: ARC Options. (line 82) * msimnovec: MeP Options. (line 117) * msimple-fpu: RS/6000 and PowerPC Options. ! (line 465) ! * msingle-exit: MMIX Options. (line 65) ! * msingle-float: MIPS Options. (line 283) * msingle-float <1>: RS/6000 and PowerPC Options. ! (line 461) ! * msingle-pic-base: ARM Options. (line 227) * msingle-pic-base <1>: RS/6000 and PowerPC Options. ! (line 604) * msio: HPPA Options. (line 98) ! * msize-level: ARC Options. (line 405) ! * mskip-rax-setup: x86 Options. (line 1073) * mslow-bytes: MCore Options. (line 35) * mslow-flash-data: ARM Options. (line 357) * msmall: MSP430 Options. (line 55) --- 53857,53929 ---- * msched-prefer-non-control-spec-insns: IA-64 Options. (line 178) * msched-prefer-non-data-spec-insns: IA-64 Options. (line 171) * msched-spec-ldc: IA-64 Options. (line 191) * msched-stop-bits-after-every-cycle: IA-64 Options. (line 198) * mschedule: HPPA Options. (line 71) * mscore5: Score Options. (line 25) * mscore5u: Score Options. (line 28) * mscore7: Score Options. (line 31) ! * mscore7d: Score Options. (line 34) * msda: V850 Options. (line 40) * msdata <1>: RS/6000 and PowerPC Options. ! (line 785) ! * msdata: IA-64 Options. (line 42) * msdata=all: C6X Options. (line 30) * msdata=data: RS/6000 and PowerPC Options. ! (line 790) * msdata=default <1>: RS/6000 and PowerPC Options. ! (line 785) ! * msdata=default: C6X Options. (line 22) * msdata=eabi: RS/6000 and PowerPC Options. ! (line 765) ! * msdata=none <1>: RS/6000 and PowerPC Options. ! (line 798) ! * msdata=none <2>: M32R/D Options. (line 40) * msdata=none: C6X Options. (line 35) * msdata=sdata: M32R/D Options. (line 49) * msdata=sysv: RS/6000 and PowerPC Options. ! (line 776) * msdata=use: M32R/D Options. (line 53) * msdram <1>: MeP Options. (line 110) + * msdram: Blackfin Options. (line 172) * msecure-plt: RS/6000 and PowerPC Options. (line 184) * msel-sched-dont-check-control-spec: IA-64 Options. (line 207) ! * msep-data: Blackfin Options. (line 110) * mserialize-volatile: Xtensa Options. (line 35) * msetlb: MN10300 Options. (line 64) ! * msha: x86 Options. (line 627) ! * mshared-library-id: Blackfin Options. (line 103) ! * mshort: M680x0 Options. (line 220) * msign-extend-enabled: LM32 Options. (line 18) ! * msilicon-errata: MSP430 Options. (line 103) ! * msilicon-errata-warn: MSP430 Options. (line 107) ! * msim <1>: Xstormy16 Options. (line 9) ! * msim <2>: Visium Options. (line 13) ! * msim <3>: RX Options. (line 71) ! * msim <4>: RS/6000 and PowerPC Options. ! (line 721) ! * msim <5>: RL78 Options. (line 7) * msim <6>: MSP430 Options. (line 47) ! * msim <7>: MeP Options. (line 114) ! * msim <8>: M32C Options. (line 13) ! * msim <9>: FT32 Options. (line 9) ! * msim <10>: CR16 Options. (line 18) ! * msim <11>: C6X Options. (line 19) ! * msim: Blackfin Options. (line 37) ! * msimd: ARC Options. (line 87) * msimnovec: MeP Options. (line 117) * msimple-fpu: RS/6000 and PowerPC Options. ! (line 441) ! * msingle-exit: MMIX Options. (line 66) * msingle-float <1>: RS/6000 and PowerPC Options. ! (line 437) ! * msingle-float: MIPS Options. (line 286) * msingle-pic-base <1>: RS/6000 and PowerPC Options. ! (line 580) ! * msingle-pic-base: ARM Options. (line 228) * msio: HPPA Options. (line 98) ! * msize-level: ARC Options. (line 415) ! * mskip-rax-setup: x86 Options. (line 1080) * mslow-bytes: MCore Options. (line 35) * mslow-flash-data: ARM Options. (line 357) * msmall: MSP430 Options. (line 55) *************** look up both forms. *** 53357,53528 **** * msmall-data-limit: RX Options. (line 47) * msmall-divides: MicroBlaze Options. (line 39) * msmall-exec: S/390 and zSeries Options. ! (line 79) ! * msmall-mem: SPU Options. (line 38) * msmall-model: FR30 Options. (line 9) * msmall-text: DEC Alpha Options. (line 205) * msmall16: Adapteva Epiphany Options. ! (line 66) ! * msmallc: Nios II Options. (line 286) ! * msmartmips: MIPS Options. (line 365) ! * msoft-float: ARC Options. (line 86) ! * msoft-float <1>: DEC Alpha Options. (line 10) ! * msoft-float <2>: FRV Options. (line 27) ! * msoft-float <3>: HPPA Options. (line 84) ! * msoft-float <4>: M680x0 Options. (line 200) ! * msoft-float <5>: MicroBlaze Options. (line 7) ! * msoft-float <6>: MIPS Options. (line 269) ! * msoft-float <7>: PDP-11 Options. (line 13) ! * msoft-float <8>: RS/6000 and PowerPC Options. ! (line 455) ! * msoft-float <9>: S/390 and zSeries Options. (line 11) ! * msoft-float <10>: SPARC Options. (line 39) ! * msoft-float <11>: V850 Options. (line 113) ! * msoft-float <12>: Visium Options. (line 24) ! * msoft-float <13>: x86 Options. (line 367) ! * msoft-quad-float: SPARC Options. (line 59) ! * msp8: AVR Options. (line 205) * mspace: V850 Options. (line 30) * mspe: RS/6000 and PowerPC Options. (line 209) ! * mspecld-anomaly: Blackfin Options. (line 50) ! * mspfp: ARC Options. (line 73) ! * mspfp-compact: ARC Options. (line 74) ! * mspfp-fast: ARC Options. (line 78) ! * mspfp_compact: ARC Options. (line 504) ! * mspfp_fast: ARC Options. (line 507) ! * msplit-addresses: MIPS Options. (line 532) * msplit-vecmove-early: Adapteva Epiphany Options. ! (line 126) ! * msse: x86 Options. (line 602) ! * msse2: x86 Options. (line 603) ! * msse2avx: x86 Options. (line 1048) ! * msse3: x86 Options. (line 604) ! * msse4: x86 Options. (line 606) ! * msse4.1: x86 Options. (line 608) ! * msse4.2: x86 Options. (line 609) ! * msse4a: x86 Options. (line 607) ! * msseregparm: x86 Options. (line 503) ! * mssse3: x86 Options. (line 605) * mstack-align: CRIS Options. (line 55) ! * mstack-bias: SPARC Options. (line 334) ! * mstack-check-l1: Blackfin Options. (line 76) * mstack-guard: S/390 and zSeries Options. ! (line 187) * mstack-increment: MCore Options. (line 50) * mstack-offset: Adapteva Epiphany Options. (line 37) ! * mstack-protector-guard=GUARD: x86 Options. (line 1097) * mstack-size: S/390 and zSeries Options. ! (line 187) ! * mstackrealign: x86 Options. (line 546) ! * mstd-struct-return: SPARC Options. (line 102) ! * mstdmain: SPU Options. (line 44) * mstrict-align: AArch64 Options. (line 52) ! * mstrict-align <1>: M680x0 Options. (line 283) ! * mstrict-align <2>: RS/6000 and PowerPC Options. ! (line 556) ! * mstrict-X: AVR Options. (line 218) * mstring: RS/6000 and PowerPC Options. ! (line 492) ! * mstringop-strategy=ALG: x86 Options. (line 996) ! * mstructure-size-boundary: ARM Options. (line 184) * msv-mode: Visium Options. (line 52) * msvr4-struct-return: RS/6000 and PowerPC Options. ! (line 697) ! * mswap: ARC Options. (line 93) ! * mswape: ARC Options. (line 246) ! * msym32: MIPS Options. (line 430) ! * msynci: MIPS Options. (line 805) ! * msys-crt0: Nios II Options. (line 290) ! * msys-lib: Nios II Options. (line 294) * MT: Preprocessor Options. (line 251) * mtarget-align: Xtensa Options. (line 74) ! * mtas: SH Options. (line 259) ! * mtbm: x86 Options. (line 645) * mtda: V850 Options. (line 34) ! * mtelephony: ARC Options. (line 251) * mtext-section-literals: Xtensa Options. (line 47) * mtf: MeP Options. (line 121) * mthread: x86 Windows Options. (line 26) ! * mthreads: x86 Options. (line 852) ! * mthumb: ARM Options. (line 268) * mthumb-interwork: ARM Options. (line 24) ! * mtiny-stack: AVR Options. (line 232) * mtiny=: MeP Options. (line 125) ! * mTLS: FRV Options. (line 90) ! * mtls: FRV Options. (line 94) * mtls-dialect: ARM Options. (line 315) - * mtls-dialect <1>: x86 Options. (line 830) * mtls-dialect=desc: AArch64 Options. (line 61) * mtls-dialect=traditional: AArch64 Options. (line 65) ! * mtls-direct-seg-refs: x86 Options. (line 1038) * mtls-markers: RS/6000 and PowerPC Options. ! (line 878) ! * mtls-size: AArch64 Options. (line 69) * mtls-size <1>: IA-64 Options. (line 112) * mtoc: RS/6000 and PowerPC Options. ! (line 581) ! * mtomcat-stats: FRV Options. (line 254) ! * mtoplevel-symbols: MMIX Options. (line 39) * mtp: ARM Options. (line 307) * mtpcs-frame: ARM Options. (line 280) * mtpcs-leaf-frame: ARM Options. (line 286) * mtpf-trace: S/390 and zSeries Options. ! (line 162) * mtrap-precision: DEC Alpha Options. (line 109) ! * mtune: AArch64 Options. (line 122) ! * mtune <1>: ARC Options. (line 426) ! * mtune <2>: ARC Options. (line 510) ! * mtune <3>: ARM Options. (line 89) ! * mtune <4>: CRIS Options. (line 17) ! * mtune <5>: DEC Alpha Options. (line 259) ! * mtune <6>: IA-64 Options. (line 116) ! * mtune <7>: M680x0 Options. (line 68) ! * mtune <8>: MIPS Options. (line 65) ! * mtune <9>: MN10300 Options. (line 30) ! * mtune <10>: RS/6000 and PowerPC Options. (line 114) ! * mtune <11>: S/390 and zSeries Options. ! (line 155) ! * mtune <12>: SPARC Options. (line 193) ! * mtune <13>: Visium Options. (line 47) ! * mtune <14>: x86 Options. (line 248) ! * mtune-ctrl=FEATURE-LIST: x86 Options. (line 681) ! * mucb-mcount: ARC Options. (line 304) * muclibc: GNU/Linux Options. (line 14) * muls: Score Options. (line 18) ! * multcost: ARC Options. (line 515) ! * multcost=NUMBER: SH Options. (line 281) ! * multilib-library-pic: FRV Options. (line 110) * multiply-enabled: LM32 Options. (line 15) * multiply_defined: Darwin Options. (line 196) * multiply_defined_unused: Darwin Options. (line 196) ! * multi_module: Darwin Options. (line 196) ! * munalign-prob-threshold: ARC Options. (line 454) * munaligned-access: ARM Options. (line 339) ! * munaligned-doubles: SPARC Options. (line 73) * municode: x86 Windows Options. (line 30) ! * muninit-const-in-rodata: MIPS Options. (line 502) * munix: VAX Options. (line 9) * munix-asm: PDP-11 Options. (line 68) ! * munsafe-dma: SPU Options. (line 18) * mupdate: RS/6000 and PowerPC Options. ! (line 503) * mupper-regs: RS/6000 and PowerPC Options. ! (line 288) * mupper-regs-df: RS/6000 and PowerPC Options. (line 272) * mupper-regs-sf: RS/6000 and PowerPC Options. (line 280) * muser-enabled: LM32 Options. (line 21) - * muser-mode: SPARC Options. (line 85) * muser-mode <1>: Visium Options. (line 57) ! * musermode: SH Options. (line 274) * mv3push: NDS32 Options. (line 33) * mv850: V850 Options. (line 49) * mv850e: V850 Options. (line 79) --- 53931,54101 ---- * msmall-data-limit: RX Options. (line 47) * msmall-divides: MicroBlaze Options. (line 39) * msmall-exec: S/390 and zSeries Options. ! (line 80) ! * msmall-mem: SPU Options. (line 35) * msmall-model: FR30 Options. (line 9) * msmall-text: DEC Alpha Options. (line 205) * msmall16: Adapteva Epiphany Options. ! (line 67) ! * msmallc: Nios II Options. (line 291) ! * msmartmips: MIPS Options. (line 368) ! * msoft-float <1>: x86 Options. (line 373) ! * msoft-float <2>: Visium Options. (line 24) ! * msoft-float <3>: V850 Options. (line 113) ! * msoft-float <4>: SPARC Options. (line 40) ! * msoft-float <5>: S/390 and zSeries Options. (line 11) ! * msoft-float <6>: RS/6000 and PowerPC Options. ! (line 431) ! * msoft-float <7>: PDP-11 Options. (line 13) ! * msoft-float <8>: MIPS Options. (line 272) ! * msoft-float <9>: MicroBlaze Options. (line 7) ! * msoft-float <10>: M680x0 Options. (line 203) ! * msoft-float <11>: HPPA Options. (line 84) ! * msoft-float <12>: FRV Options. (line 22) ! * msoft-float <13>: DEC Alpha Options. (line 10) ! * msoft-float: ARC Options. (line 91) ! * msoft-quad-float: SPARC Options. (line 60) ! * msp8: AVR Options. (line 203) * mspace: V850 Options. (line 30) * mspe: RS/6000 and PowerPC Options. (line 209) ! * mspecld-anomaly: Blackfin Options. (line 51) ! * mspfp: ARC Options. (line 78) ! * mspfp-compact: ARC Options. (line 79) ! * mspfp-fast: ARC Options. (line 83) ! * mspfp_compact: ARC Options. (line 516) ! * mspfp_fast: ARC Options. (line 519) ! * msplit-addresses: MIPS Options. (line 536) * msplit-vecmove-early: Adapteva Epiphany Options. ! (line 127) ! * msse: x86 Options. (line 608) ! * msse2: x86 Options. (line 609) ! * msse2avx: x86 Options. (line 1055) ! * msse3: x86 Options. (line 610) ! * msse4: x86 Options. (line 612) ! * msse4.1: x86 Options. (line 614) ! * msse4.2: x86 Options. (line 615) ! * msse4a: x86 Options. (line 613) ! * msseregparm: x86 Options. (line 509) ! * mssse3: x86 Options. (line 611) * mstack-align: CRIS Options. (line 55) ! * mstack-bias: SPARC Options. (line 337) ! * mstack-check-l1: Blackfin Options. (line 77) * mstack-guard: S/390 and zSeries Options. ! (line 189) * mstack-increment: MCore Options. (line 50) * mstack-offset: Adapteva Epiphany Options. (line 37) ! * mstack-protector-guard=GUARD: x86 Options. (line 1104) * mstack-size: S/390 and zSeries Options. ! (line 189) ! * mstackrealign: x86 Options. (line 552) ! * mstd-struct-return: SPARC Options. (line 103) ! * mstdmain: SPU Options. (line 40) ! * mstrict-align <1>: RS/6000 and PowerPC Options. ! (line 532) ! * mstrict-align <2>: M680x0 Options. (line 287) * mstrict-align: AArch64 Options. (line 52) ! * mstrict-X: AVR Options. (line 216) * mstring: RS/6000 and PowerPC Options. ! (line 468) ! * mstringop-strategy=ALG: x86 Options. (line 1003) ! * mstructure-size-boundary: ARM Options. (line 185) * msv-mode: Visium Options. (line 52) * msvr4-struct-return: RS/6000 and PowerPC Options. ! (line 673) ! * mswap: ARC Options. (line 98) ! * mswape: ARC Options. (line 254) ! * msym32: MIPS Options. (line 433) ! * msynci: MIPS Options. (line 817) ! * msys-crt0: Nios II Options. (line 295) ! * msys-lib: Nios II Options. (line 299) * MT: Preprocessor Options. (line 251) * mtarget-align: Xtensa Options. (line 74) ! * mtas: SH Options. (line 261) ! * mtbm: x86 Options. (line 651) * mtda: V850 Options. (line 34) ! * mtelephony: ARC Options. (line 259) * mtext-section-literals: Xtensa Options. (line 47) * mtf: MeP Options. (line 121) * mthread: x86 Windows Options. (line 26) ! * mthreads: x86 Options. (line 859) ! * mthumb: ARM Options. (line 269) * mthumb-interwork: ARM Options. (line 24) ! * mtiny-stack: AVR Options. (line 230) * mtiny=: MeP Options. (line 125) ! * mtls: FRV Options. (line 75) ! * mTLS: FRV Options. (line 72) ! * mtls-dialect <1>: x86 Options. (line 837) * mtls-dialect: ARM Options. (line 315) * mtls-dialect=desc: AArch64 Options. (line 61) * mtls-dialect=traditional: AArch64 Options. (line 65) ! * mtls-direct-seg-refs: x86 Options. (line 1045) * mtls-markers: RS/6000 and PowerPC Options. ! (line 856) * mtls-size <1>: IA-64 Options. (line 112) + * mtls-size: AArch64 Options. (line 69) * mtoc: RS/6000 and PowerPC Options. ! (line 557) ! * mtomcat-stats: FRV Options. (line 209) ! * mtoplevel-symbols: MMIX Options. (line 40) * mtp: ARM Options. (line 307) * mtpcs-frame: ARM Options. (line 280) * mtpcs-leaf-frame: ARM Options. (line 286) * mtpf-trace: S/390 and zSeries Options. ! (line 164) * mtrap-precision: DEC Alpha Options. (line 109) ! * mtune <1>: x86 Options. (line 253) ! * mtune <2>: Visium Options. (line 47) ! * mtune <3>: SPARC Options. (line 195) ! * mtune <4>: S/390 and zSeries Options. ! (line 157) ! * mtune <5>: RS/6000 and PowerPC Options. (line 114) ! * mtune <6>: MN10300 Options. (line 30) ! * mtune <7>: MIPS Options. (line 65) ! * mtune <8>: M680x0 Options. (line 70) ! * mtune <9>: IA-64 Options. (line 116) ! * mtune <10>: DEC Alpha Options. (line 259) ! * mtune <11>: CRIS Options. (line 16) ! * mtune <12>: ARM Options. (line 89) ! * mtune <13>: ARC Options. (line 437) ! * mtune: AArch64 Options. (line 123) ! * mtune-ctrl=FEATURE-LIST: x86 Options. (line 687) ! * mucb-mcount: ARC Options. (line 313) * muclibc: GNU/Linux Options. (line 14) * muls: Score Options. (line 18) ! * multcost: ARC Options. (line 527) ! * multcost=NUMBER: SH Options. (line 284) ! * multi_module: Darwin Options. (line 196) ! * multilib-library-pic: FRV Options. (line 89) * multiply-enabled: LM32 Options. (line 15) * multiply_defined: Darwin Options. (line 196) * multiply_defined_unused: Darwin Options. (line 196) ! * munalign-prob-threshold: ARC Options. (line 466) * munaligned-access: ARM Options. (line 339) ! * munaligned-doubles: SPARC Options. (line 74) * municode: x86 Windows Options. (line 30) ! * muninit-const-in-rodata: MIPS Options. (line 506) * munix: VAX Options. (line 9) * munix-asm: PDP-11 Options. (line 68) ! * munsafe-dma: SPU Options. (line 17) * mupdate: RS/6000 and PowerPC Options. ! (line 479) * mupper-regs: RS/6000 and PowerPC Options. ! (line 289) * mupper-regs-df: RS/6000 and PowerPC Options. (line 272) * mupper-regs-sf: RS/6000 and PowerPC Options. (line 280) * muser-enabled: LM32 Options. (line 21) * muser-mode <1>: Visium Options. (line 57) ! * muser-mode: SPARC Options. (line 86) ! * musermode: SH Options. (line 276) * mv3push: NDS32 Options. (line 33) * mv850: V850 Options. (line 49) * mv850e: V850 Options. (line 79) *************** look up both forms. *** 53532,53567 **** * mv850e2v4: V850 Options. (line 57) * mv850e3v5: V850 Options. (line 52) * mv850es: V850 Options. (line 75) ! * mv8plus: SPARC Options. (line 207) * mveclibabi: RS/6000 and PowerPC Options. ! (line 956) ! * mveclibabi <1>: x86 Options. (line 798) ! * mvect8-ret-in-mem: x86 Options. (line 513) ! * mvirt: MIPS Options. (line 406) ! * mvis: SPARC Options. (line 214) ! * mvis2: SPARC Options. (line 220) ! * mvis3: SPARC Options. (line 228) ! * mvis4: SPARC Options. (line 236) ! * mvliw-branch: FRV Options. (line 201) * mvms-return-codes: VMS Options. (line 9) * mvolatile-asm-stop: IA-64 Options. (line 32) ! * mvolatile-cache: ARC Options. (line 309) ! * mvr4130-align: MIPS Options. (line 794) * mvrsave: RS/6000 and PowerPC Options. (line 174) * mvsx: RS/6000 and PowerPC Options. (line 223) * mvx: S/390 and zSeries Options. ! (line 112) * mvxworks: RS/6000 and PowerPC Options. ! (line 766) ! * mvzeroupper: x86 Options. (line 708) * mwarn-cell-microcode: RS/6000 and PowerPC Options. (line 180) * mwarn-dynamicstack: S/390 and zSeries Options. ! (line 181) * mwarn-framesize: S/390 and zSeries Options. ! (line 173) * mwarn-mcu: MSP430 Options. (line 35) * mwarn-multiple-fast-interrupts: RX Options. (line 143) * mwarn-reloc: SPU Options. (line 10) --- 54105,54140 ---- * mv850e2v4: V850 Options. (line 57) * mv850e3v5: V850 Options. (line 52) * mv850es: V850 Options. (line 75) ! * mv8plus: SPARC Options. (line 210) ! * mveclibabi <1>: x86 Options. (line 805) * mveclibabi: RS/6000 and PowerPC Options. ! (line 935) ! * mvect8-ret-in-mem: x86 Options. (line 519) ! * mvirt: MIPS Options. (line 409) ! * mvis: SPARC Options. (line 217) ! * mvis2: SPARC Options. (line 223) ! * mvis3: SPARC Options. (line 231) ! * mvis4: SPARC Options. (line 239) ! * mvliw-branch: FRV Options. (line 164) * mvms-return-codes: VMS Options. (line 9) * mvolatile-asm-stop: IA-64 Options. (line 32) ! * mvolatile-cache: ARC Options. (line 318) ! * mvr4130-align: MIPS Options. (line 806) * mvrsave: RS/6000 and PowerPC Options. (line 174) * mvsx: RS/6000 and PowerPC Options. (line 223) * mvx: S/390 and zSeries Options. ! (line 113) * mvxworks: RS/6000 and PowerPC Options. ! (line 742) ! * mvzeroupper: x86 Options. (line 715) * mwarn-cell-microcode: RS/6000 and PowerPC Options. (line 180) * mwarn-dynamicstack: S/390 and zSeries Options. ! (line 183) * mwarn-framesize: S/390 and zSeries Options. ! (line 175) * mwarn-mcu: MSP430 Options. (line 35) * mwarn-multiple-fast-interrupts: RX Options. (line 143) * mwarn-reloc: SPU Options. (line 10) *************** look up both forms. *** 53571,53584 **** * mwindows: x86 Windows Options. (line 41) * mword-relocations: ARM Options. (line 326) ! * mx32: x86 Options. (line 1116) ! * mxgot: M680x0 Options. (line 315) ! * mxgot <1>: MIPS Options. (line 228) * mxilinx-fpu: RS/6000 and PowerPC Options. ! (line 476) * mxl-barrel-shift: MicroBlaze Options. (line 33) * mxl-compat: RS/6000 and PowerPC Options. ! (line 413) * mxl-float-convert: MicroBlaze Options. (line 51) * mxl-float-sqrt: MicroBlaze Options. (line 54) * mxl-gp-opt: MicroBlaze Options. (line 45) --- 54144,54157 ---- * mwindows: x86 Windows Options. (line 41) * mword-relocations: ARM Options. (line 326) ! * mx32: x86 Options. (line 1125) ! * mxgot <1>: MIPS Options. (line 231) ! * mxgot: M680x0 Options. (line 319) * mxilinx-fpu: RS/6000 and PowerPC Options. ! (line 452) * mxl-barrel-shift: MicroBlaze Options. (line 33) * mxl-compat: RS/6000 and PowerPC Options. ! (line 388) * mxl-float-convert: MicroBlaze Options. (line 51) * mxl-float-sqrt: MicroBlaze Options. (line 54) * mxl-gp-opt: MicroBlaze Options. (line 45) *************** look up both forms. *** 53588,53618 **** * mxl-soft-div: MicroBlaze Options. (line 30) * mxl-soft-mul: MicroBlaze Options. (line 27) * mxl-stack-check: MicroBlaze Options. (line 42) ! * mxop: x86 Options. (line 631) ! * mxpa: MIPS Options. (line 411) ! * mxsave: x86 Options. (line 640) ! * mxsavec: x86 Options. (line 642) ! * mxsaveopt: x86 Options. (line 641) ! * mxsaves: x86 Options. (line 643) ! * mxy: ARC Options. (line 256) * myellowknife: RS/6000 and PowerPC Options. ! (line 761) * mzarch: S/390 and zSeries Options. ! (line 94) * mzda: V850 Options. (line 45) ! * mzdcbranch: SH Options. (line 341) ! * mzero-extend: MMIX Options. (line 26) * mzvector: S/390 and zSeries Options. ! (line 123) ! * no-canonical-prefixes: Directory Options. (line 86) * no-integrated-cpp: Preprocessor Options. (line 34) * no-pie: Link Options. (line 111) ! * no-sysroot-suffix: Directory Options. (line 105) * noall_load: Darwin Options. (line 196) ! * nocpp: MIPS Options. (line 606) * nodefaultlibs: Link Options. (line 68) ! * nodevicelib: AVR Options. (line 235) * nofixprebinding: Darwin Options. (line 196) * nofpu: RX Options. (line 17) * nolibdld: HPPA Options. (line 181) --- 54161,54192 ---- * mxl-soft-div: MicroBlaze Options. (line 30) * mxl-soft-mul: MicroBlaze Options. (line 27) * mxl-stack-check: MicroBlaze Options. (line 42) ! * mxop: x86 Options. (line 637) ! * mxpa: MIPS Options. (line 414) ! * mxsave: x86 Options. (line 646) ! * mxsavec: x86 Options. (line 648) ! * mxsaveopt: x86 Options. (line 647) ! * mxsaves: x86 Options. (line 649) ! * mxy: ARC Options. (line 264) * myellowknife: RS/6000 and PowerPC Options. ! (line 737) * mzarch: S/390 and zSeries Options. ! (line 95) * mzda: V850 Options. (line 45) ! * mzdcbranch: SH Options. (line 345) ! * mzero-extend: MMIX Options. (line 27) * mzvector: S/390 and zSeries Options. ! (line 124) ! * no-canonical-prefixes: Directory Options. (line 88) * no-integrated-cpp: Preprocessor Options. (line 34) * no-pie: Link Options. (line 111) ! * no-sysroot-suffix: Directory Options. (line 107) ! * no_dead_strip_inits_and_terms: Darwin Options. (line 196) * noall_load: Darwin Options. (line 196) ! * nocpp: MIPS Options. (line 611) * nodefaultlibs: Link Options. (line 68) ! * nodevicelib: AVR Options. (line 233) * nofixprebinding: Darwin Options. (line 196) * nofpu: RX Options. (line 17) * nolibdld: HPPA Options. (line 181) *************** look up both forms. *** 53622,54288 **** * noseglinkedit: Darwin Options. (line 196) * nostartfiles: Link Options. (line 63) * nostdinc: Preprocessor Options. ! (line 401) ! * nostdinc++: C++ Dialect Options. ! (line 394) * nostdinc++ <1>: Preprocessor Options. ! (line 406) * nostdlib: Link Options. (line 80) ! * no_dead_strip_inits_and_terms: Darwin Options. (line 196) ! * o: Overall Options. (line 184) ! * O: Optimize Options. (line 39) ! * o <1>: Preprocessor Options. (line 87) * O0: Optimize Options. (line 148) * O1: Optimize Options. (line 39) * O2: Optimize Options. (line 93) * O3: Optimize Options. (line 139) * Ofast: Optimize Options. (line 162) ! * Og: Optimize Options. (line 168) * Os: Optimize Options. (line 152) * p: Instrumentation Options. (line 19) - * P: Preprocessor Options. - (line 646) * pagezero_size: Darwin Options. (line 196) ! * param: Optimize Options. (line 2324) * pass-exit-codes: Overall Options. (line 323) ! * pedantic: Standards. (line 13) ! * pedantic <1>: Warning Options. (line 80) ! * pedantic <2>: Preprocessor Options. ! (line 175) * pedantic <3>: C Extensions. (line 6) ! * pedantic <4>: Alternate Keywords. (line 30) ! * pedantic <5>: Warnings and Errors. (line 25) ! * pedantic-errors: Standards. (line 13) ! * pedantic-errors <1>: Warning Options. (line 121) ! * pedantic-errors <2>: Preprocessor Options. (line 180) ! * pedantic-errors <3>: Non-bugs. (line 216) ! * pedantic-errors <4>: Warnings and Errors. ! (line 25) * pg: Instrumentation Options. (line 25) * pie: Link Options. (line 105) * pipe: Overall Options. (line 331) * prebind: Darwin Options. (line 196) * prebind_all_twolevel_modules: Darwin Options. (line 196) ! * print-file-name: Developer Options. (line 952) ! * print-libgcc-file-name: Developer Options. (line 986) ! * print-multi-directory: Developer Options. (line 958) ! * print-multi-lib: Developer Options. (line 963) ! * print-multi-os-directory: Developer Options. (line 970) ! * print-multiarch: Developer Options. (line 979) * print-objc-runtime-info: Objective-C and Objective-C++ Dialect Options. (line 217) ! * print-prog-name: Developer Options. (line 983) ! * print-search-dirs: Developer Options. (line 994) ! * print-sysroot: Developer Options. (line 1007) ! * print-sysroot-headers-suffix: Developer Options. (line 1014) * private_bundle: Darwin Options. (line 196) * pthread: RS/6000 and PowerPC Options. ! (line 885) ! * pthread <1>: Solaris 2 Options. (line 36) ! * pthreads: Solaris 2 Options. (line 30) ! * Q: Developer Options. (line 862) * Qn: System V Options. (line 18) * Qy: System V Options. (line 14) * rdynamic: Link Options. (line 114) * read_only_relocs: Darwin Options. (line 196) * remap: Preprocessor Options. ! (line 693) ! * S: Overall Options. (line 167) ! * S <1>: Link Options. (line 20) * s: Link Options. (line 121) ! * save-temps: Developer Options. (line 737) ! * save-temps=obj: Developer Options. (line 763) * sectalign: Darwin Options. (line 196) * sectcreate: Darwin Options. (line 196) * sectobjectsymbols: Darwin Options. (line 196) - * sectobjectsymbols <1>: Darwin Options. (line 196) * sectorder: Darwin Options. (line 196) * seg1addr: Darwin Options. (line 196) * segaddr: Darwin Options. (line 196) * seglinkedit: Darwin Options. (line 196) * segprot: Darwin Options. (line 196) * segs_read_only_addr: Darwin Options. (line 196) - * segs_read_only_addr <1>: Darwin Options. (line 196) * segs_read_write_addr: Darwin Options. (line 196) ! * segs_read_write_addr <1>: Darwin Options. (line 196) ! * seg_addr_table: Darwin Options. (line 196) ! * seg_addr_table_filename: Darwin Options. (line 196) ! * shared: Link Options. (line 129) ! * shared-libgcc: Link Options. (line 137) * short-calls: Adapteva Epiphany Options. (line 61) * sim: CRIS Options. (line 95) * sim2: CRIS Options. (line 101) * single_module: Darwin Options. (line 196) * specs: Overall Options. (line 337) * static: Link Options. (line 125) ! * static <1>: Darwin Options. (line 196) ! * static <2>: HPPA Options. (line 185) ! * static-libasan: Link Options. (line 172) ! * static-libgcc: Link Options. (line 137) ! * static-liblsan: Link Options. (line 188) ! * static-libmpx: Link Options. (line 205) ! * static-libmpxwrappers: Link Options. (line 214) ! * static-libstdc++: Link Options. (line 224) ! * static-libtsan: Link Options. (line 180) ! * static-libubsan: Link Options. (line 196) ! * std: Standards. (line 13) ! * std <1>: C Dialect Options. (line 46) * std <2>: Other Builtins. (line 31) ! * std <3>: Non-bugs. (line 107) * std=: Preprocessor Options. ! (line 340) * sub_library: Darwin Options. (line 196) * sub_umbrella: Darwin Options. (line 196) ! * symbolic: Link Options. (line 235) ! * sysroot: Directory Options. (line 90) ! * T: Link Options. (line 241) ! * target-help: Overall Options. (line 216) * target-help <1>: Preprocessor Options. ! (line 698) * threads: HPPA Options. (line 198) ! * time: Developer Options. (line 778) * tno-android-cc: GNU/Linux Options. (line 36) * tno-android-ld: GNU/Linux Options. (line 40) - * traditional: C Dialect Options. (line 348) * traditional <1>: Incompatibilities. (line 6) ! * traditional-cpp: C Dialect Options. (line 348) * traditional-cpp <1>: Preprocessor Options. ! (line 676) ! * trigraphs: C Dialect Options. (line 343) * trigraphs <1>: Preprocessor Options. ! (line 680) * twolevel_namespace: Darwin Options. (line 196) * U: Preprocessor Options. (line 69) - * u: Link Options. (line 273) * umbrella: Darwin Options. (line 196) * undef: Preprocessor Options. (line 73) * undefined: Darwin Options. (line 196) * unexported_symbols_list: Darwin Options. (line 196) - * v: Overall Options. (line 195) * v <1>: Preprocessor Options. ! (line 702) ! * version: Overall Options. (line 320) * version <1>: Preprocessor Options. ! (line 714) ! * w: Warning Options. (line 25) ! * W: Warning Options. (line 191) ! * W <1>: Warning Options. (line 1640) ! * W <2>: Warning Options. (line 1736) ! * w <1>: Preprocessor Options. (line 171) ! * w <2>: ARC Options. (line 117) ! * W <3>: Incompatibilities. (line 64) * Wa: Assembler Options. (line 9) * Wabi: C++ Dialect Options. ! (line 402) * Wabi-tag: C++ Dialect Options. ! (line 506) ! * Waddr-space-convert: AVR Options. (line 238) ! * Waddress: Warning Options. (line 1539) ! * Waggregate-return: Warning Options. (line 1575) ! * Waggressive-loop-optimizations: Warning Options. (line 1580) ! * Wall: Warning Options. (line 130) ! * Wall <1>: Preprocessor Options. (line 93) ! * Wall <2>: Standard Libraries. (line 6) ! * Warray-bounds: Warning Options. (line 1015) * Wassign-intercept: Objective-C and Objective-C++ Dialect Options. (line 171) ! * Wattributes: Warning Options. (line 1585) ! * Wbad-function-cast: Warning Options. (line 1333) ! * Wbool-compare: Warning Options. (line 1031) ! * Wbuiltin-macro-redefined: Warning Options. (line 1591) ! * Wc++-compat: Warning Options. (line 1353) ! * Wc++11-compat: Warning Options. (line 1358) ! * Wc++14-compat: Warning Options. (line 1364) ! * Wc90-c99-compat: Warning Options. (line 1338) ! * Wc99-c11-compat: Warning Options. (line 1345) ! * Wcast-align: Warning Options. (line 1384) ! * Wcast-qual: Warning Options. (line 1368) ! * Wchar-subscripts: Warning Options. (line 231) ! * Wclobbered: Warning Options. (line 1403) ! * Wcomment: Warning Options. (line 236) * Wcomment <1>: Preprocessor Options. (line 101) * Wcomments: Preprocessor Options. (line 101) ! * Wconditionally-supported: Warning Options. (line 1407) ! * Wconversion: Warning Options. (line 1410) ! * Wconversion-null: Warning Options. (line 1428) * Wctor-dtor-privacy: C++ Dialect Options. ! (line 511) ! * Wdate-time: Warning Options. (line 1449) ! * Wdeclaration-after-statement: Warning Options. (line 1210) ! * Wdelete-incomplete: Warning Options. (line 1454) * Wdelete-non-virtual-dtor: C++ Dialect Options. ! (line 518) ! * Wdeprecated: Warning Options. (line 1713) ! * Wdeprecated-declarations: Warning Options. (line 1717) ! * Wdisabled-optimization: Warning Options. (line 1885) ! * Wdiscarded-array-qualifiers: Warning Options. (line 1058) ! * Wdiscarded-qualifiers: Warning Options. (line 1052) ! * Wdiv-by-zero: Warning Options. (line 1076) ! * Wdouble-promotion: Warning Options. (line 260) ! * Wduplicated-cond: Warning Options. (line 1040) * weak_reference_mismatches: Darwin Options. (line 196) * Weffc++: C++ Dialect Options. ! (line 607) ! * Wempty-body: Warning Options. (line 1461) ! * Wendif-labels: Warning Options. (line 1219) * Wendif-labels <1>: Preprocessor Options. (line 148) ! * Wenum-compare: Warning Options. (line 1465) ! * Werror: Warning Options. (line 28) * Werror <1>: Preprocessor Options. (line 161) * Werror=: Warning Options. (line 31) ! * Wextra: Warning Options. (line 191) ! * Wextra <1>: Warning Options. (line 1640) ! * Wextra <2>: Warning Options. (line 1736) * Wfatal-errors: Warning Options. (line 48) ! * Wfloat-conversion: Warning Options. (line 1494) ! * Wfloat-equal: Warning Options. (line 1110) ! * Wformat: Warning Options. (line 279) ! * Wformat <1>: Warning Options. (line 304) ! * Wformat <2>: Warning Options. (line 970) ! * Wformat <3>: Common Function Attributes. (line 234) ! * Wformat-contains-nul: Warning Options. (line 313) ! * Wformat-extra-args: Warning Options. (line 317) ! * Wformat-nonliteral: Warning Options. (line 341) * Wformat-nonliteral <1>: Common Function Attributes. ! (line 299) ! * Wformat-security: Warning Options. (line 346) ! * Wformat-signedness: Warning Options. (line 358) ! * Wformat-y2k: Warning Options. (line 363) ! * Wformat-zero-length: Warning Options. (line 331) ! * Wformat=: Warning Options. (line 279) ! * Wformat=1: Warning Options. (line 304) ! * Wformat=2: Warning Options. (line 336) ! * Wframe-address: Warning Options. (line 1046) ! * Wframe-larger-than: Warning Options. (line 1238) ! * Wfree-nonheap-object: Warning Options. (line 1247) * whatsloaded: Darwin Options. (line 196) * whyload: Darwin Options. (line 196) ! * Wignored-attributes: Warning Options. (line 428) ! * Wignored-qualifiers: Warning Options. (line 417) ! * Wimplicit: Warning Options. (line 413) ! * Wimplicit-function-declaration: Warning Options. (line 407) ! * Wimplicit-int: Warning Options. (line 403) ! * Wincompatible-pointer-types: Warning Options. (line 1064) ! * Winherited-variadic-ctor: Warning Options. (line 1797) ! * Winit-self: Warning Options. (line 388) ! * Winline: Warning Options. (line 1802) * Winline <1>: Inline. (line 60) ! * Wint-conversion: Warning Options. (line 1070) ! * Wint-to-pointer-cast: Warning Options. (line 1827) ! * Winvalid-memory-model: Warning Options. (line 790) ! * Winvalid-offsetof: Warning Options. (line 1815) ! * Winvalid-pch: Warning Options. (line 1836) ! * Wjump-misses-init: Warning Options. (line 1471) ! * Wl: Link Options. (line 265) ! * Wlarger-than-LEN: Warning Options. (line 1235) ! * Wlarger-than=LEN: Warning Options. (line 1235) ! * wlh1: ARC Options. (line 122) ! * wlh2: ARC Options. (line 127) ! * wlh3: ARC Options. (line 132) ! * wlh4: ARC Options. (line 137) ! * wlh5: ARC Options. (line 142) * Wliteral-suffix: C++ Dialect Options. ! (line 525) ! * Wlogical-not-parentheses: Warning Options. (line 1560) ! * Wlogical-op: Warning Options. (line 1552) ! * Wlong-long: Warning Options. (line 1840) * Wlto-type-mismatch: C++ Dialect Options. ! (line 546) ! * Wmain: Warning Options. (line 435) ! * Wmaybe-uninitialized: Warning Options. (line 807) ! * Wmemset-transposed-args: Warning Options. (line 1528) ! * Wmisleading-indentation: Warning Options. (line 442) ! * Wmissing-braces: Warning Options. (line 476) ! * Wmissing-declarations: Warning Options. (line 1630) ! * Wmissing-field-initializers: Warning Options. (line 1640) ! * Wmissing-format-attribute: Warning Options. (line 970) ! * Wmissing-include-dirs: Warning Options. (line 487) ! * Wmissing-parameter-type: Warning Options. (line 1612) ! * Wmissing-prototypes: Warning Options. (line 1620) ! * Wmultichar: Warning Options. (line 1664) * Wmultiple-inheritance: C++ Dialect Options. ! (line 700) * Wnamespaces: C++ Dialect Options. ! (line 714) * Wnarrowing: C++ Dialect Options. ! (line 552) ! * Wnested-externs: Warning Options. (line 1794) * Wno-abi: C++ Dialect Options. ! (line 402) ! * Wno-address: Warning Options. (line 1539) ! * Wno-aggregate-return: Warning Options. (line 1575) ! * Wno-aggressive-loop-optimizations: Warning Options. (line 1580) ! * Wno-all: Warning Options. (line 130) ! * Wno-array-bounds: Warning Options. (line 1015) * Wno-assign-intercept: Objective-C and Objective-C++ Dialect Options. (line 171) ! * Wno-attributes: Warning Options. (line 1585) ! * Wno-bad-function-cast: Warning Options. (line 1333) ! * Wno-bool-compare: Warning Options. (line 1031) ! * Wno-builtin-macro-redefined: Warning Options. (line 1591) ! * Wno-c90-c99-compat: Warning Options. (line 1338) ! * Wno-c99-c11-compat: Warning Options. (line 1345) ! * Wno-cast-align: Warning Options. (line 1384) ! * Wno-cast-qual: Warning Options. (line 1368) ! * Wno-char-subscripts: Warning Options. (line 231) ! * Wno-clobbered: Warning Options. (line 1403) ! * Wno-comment: Warning Options. (line 236) ! * Wno-conditionally-supported: Warning Options. (line 1407) ! * Wno-conversion: Warning Options. (line 1410) ! * Wno-conversion-null: Warning Options. (line 1428) ! * Wno-coverage-mismatch: Warning Options. (line 241) * Wno-ctor-dtor-privacy: C++ Dialect Options. ! (line 511) ! * Wno-date-time: Warning Options. (line 1449) ! * Wno-declaration-after-statement: Warning Options. (line 1210) ! * Wno-delete-incomplete: Warning Options. (line 1454) * Wno-delete-non-virtual-dtor: C++ Dialect Options. ! (line 518) ! * Wno-deprecated: Warning Options. (line 1713) ! * Wno-deprecated-declarations: Warning Options. (line 1717) ! * Wno-disabled-optimization: Warning Options. (line 1885) ! * Wno-discarded-array-qualifiers: Warning Options. (line 1058) ! * Wno-discarded-qualifiers: Warning Options. (line 1052) ! * Wno-div-by-zero: Warning Options. (line 1076) ! * Wno-double-promotion: Warning Options. (line 260) ! * Wno-duplicated-cond: Warning Options. (line 1040) * Wno-effc++: C++ Dialect Options. ! (line 607) ! * Wno-empty-body: Warning Options. (line 1461) ! * Wno-endif-labels: Warning Options. (line 1219) ! * Wno-enum-compare: Warning Options. (line 1465) * Wno-error: Warning Options. (line 28) * Wno-error=: Warning Options. (line 31) ! * Wno-extra: Warning Options. (line 191) ! * Wno-extra <1>: Warning Options. (line 1640) ! * Wno-extra <2>: Warning Options. (line 1736) * Wno-fatal-errors: Warning Options. (line 48) ! * Wno-float-conversion: Warning Options. (line 1494) ! * Wno-float-equal: Warning Options. (line 1110) ! * Wno-format: Warning Options. (line 279) ! * Wno-format <1>: Warning Options. (line 970) ! * Wno-format-contains-nul: Warning Options. (line 313) ! * Wno-format-extra-args: Warning Options. (line 317) ! * Wno-format-nonliteral: Warning Options. (line 341) ! * Wno-format-security: Warning Options. (line 346) ! * Wno-format-signedness: Warning Options. (line 358) ! * Wno-format-y2k: Warning Options. (line 363) ! * Wno-format-zero-length: Warning Options. (line 331) ! * Wno-frame-address: Warning Options. (line 1046) ! * Wno-free-nonheap-object: Warning Options. (line 1247) ! * Wno-ignored-attributes: Warning Options. (line 428) ! * Wno-ignored-qualifiers: Warning Options. (line 417) ! * Wno-implicit: Warning Options. (line 413) ! * Wno-implicit-function-declaration: Warning Options. (line 407) ! * Wno-implicit-int: Warning Options. (line 403) ! * Wno-incompatible-pointer-types: Warning Options. (line 1064) ! * Wno-inherited-variadic-ctor: Warning Options. (line 1797) ! * Wno-init-self: Warning Options. (line 388) ! * Wno-inline: Warning Options. (line 1802) ! * Wno-int-conversion: Warning Options. (line 1070) ! * Wno-int-to-pointer-cast: Warning Options. (line 1827) ! * Wno-invalid-memory-model: Warning Options. (line 790) ! * Wno-invalid-offsetof: Warning Options. (line 1815) ! * Wno-invalid-pch: Warning Options. (line 1836) ! * Wno-jump-misses-init: Warning Options. (line 1471) * Wno-literal-suffix: C++ Dialect Options. ! (line 525) ! * Wno-logical-not-parentheses: Warning Options. (line 1560) ! * Wno-logical-op: Warning Options. (line 1552) ! * Wno-long-long: Warning Options. (line 1840) * Wno-lto-type-mismatch: C++ Dialect Options. ! (line 546) ! * Wno-main: Warning Options. (line 435) ! * Wno-maybe-uninitialized: Warning Options. (line 807) ! * Wno-memset-transposed-args: Warning Options. (line 1528) ! * Wno-misleading-indentation: Warning Options. (line 442) ! * Wno-missing-braces: Warning Options. (line 476) ! * Wno-missing-declarations: Warning Options. (line 1630) ! * Wno-missing-field-initializers: Warning Options. (line 1640) ! * Wno-missing-format-attribute: Warning Options. (line 970) ! * Wno-missing-include-dirs: Warning Options. (line 487) ! * Wno-missing-parameter-type: Warning Options. (line 1612) ! * Wno-missing-prototypes: Warning Options. (line 1620) ! * Wno-multichar: Warning Options. (line 1664) * Wno-narrowing: C++ Dialect Options. ! (line 552) ! * Wno-nested-externs: Warning Options. (line 1794) * Wno-noexcept: C++ Dialect Options. ! (line 568) * Wno-non-template-friend: C++ Dialect Options. ! (line 642) * Wno-non-virtual-dtor: C++ Dialect Options. ! (line 574) ! * Wno-nonnull: Warning Options. (line 367) ! * Wno-nonnull-compare: Warning Options. (line 374) ! * Wno-normalized: Warning Options. (line 1670) ! * Wno-null-dereference: Warning Options. (line 381) ! * Wno-odr: Warning Options. (line 1726) * Wno-old-style-cast: C++ Dialect Options. - (line 658) - * Wno-old-style-declaration: Warning Options. (line 1602) - * Wno-old-style-definition: Warning Options. (line 1608) - * Wno-overflow: Warning Options. (line 1723) - * Wno-overlength-strings: Warning Options. (line 1905) - * Wno-overloaded-virtual: C++ Dialect Options. (line 664) ! * Wno-override-init: Warning Options. (line 1736) ! * Wno-override-init-side-effects: Warning Options. (line 1744) ! * Wno-packed: Warning Options. (line 1749) ! * Wno-packed-bitfield-compat: Warning Options. (line 1766) ! * Wno-padded: Warning Options. (line 1783) ! * Wno-parentheses: Warning Options. (line 490) ! * Wno-pedantic-ms-format: Warning Options. (line 1277) ! * Wno-placement-new: Warning Options. (line 1284) ! * Wno-pmf-conversions: C++ Dialect Options. ! (line 683) * Wno-pmf-conversions <1>: Bound member functions. (line 35) ! * Wno-pointer-arith: Warning Options. (line 1319) ! * Wno-pointer-sign: Warning Options. (line 1894) ! * Wno-pointer-to-int-cast: Warning Options. (line 1832) ! * Wno-pragmas: Warning Options. (line 857) * Wno-protocol: Objective-C and Objective-C++ Dialect Options. (line 175) ! * Wno-redundant-decls: Warning Options. (line 1790) * Wno-reorder: C++ Dialect Options. ! (line 582) ! * Wno-return-local-addr: Warning Options. (line 585) ! * Wno-return-type: Warning Options. (line 589) * Wno-selector: Objective-C and Objective-C++ Dialect Options. (line 185) ! * Wno-sequence-point: Warning Options. (line 539) ! * Wno-shadow: Warning Options. (line 1223) ! * Wno-shadow-ivar: Warning Options. (line 1231) ! * Wno-shift-count-negative: Warning Options. (line 603) ! * Wno-shift-count-overflow: Warning Options. (line 607) ! * Wno-shift-negative-value: Warning Options. (line 611) ! * Wno-shift-overflow: Warning Options. (line 616) ! * Wno-sign-compare: Warning Options. (line 1482) ! * Wno-sign-conversion: Warning Options. (line 1488) * Wno-sign-promo: C++ Dialect Options. ! (line 687) ! * Wno-sized-deallocation: Warning Options. (line 1504) ! * Wno-sizeof-array-argument: Warning Options. (line 1523) ! * Wno-sizeof-pointer-memaccess: Warning Options. (line 1515) ! * Wno-stack-protector: Warning Options. (line 1900) ! * Wno-strict-aliasing: Warning Options. (line 862) * Wno-strict-null-sentinel: C++ Dialect Options. ! (line 635) ! * Wno-strict-overflow: Warning Options. (line 901) ! * Wno-strict-prototypes: Warning Options. (line 1596) * Wno-strict-selector-match: Objective-C and Objective-C++ Dialect Options. (line 197) ! * Wno-subobject-linkage: Warning Options. (line 1436) ! * Wno-suggest-attribute=: Warning Options. (line 950) ! * Wno-suggest-attribute=const: Warning Options. (line 956) ! * Wno-suggest-attribute=format: Warning Options. (line 970) ! * Wno-suggest-attribute=noreturn: Warning Options. (line 956) ! * Wno-suggest-attribute=pure: Warning Options. (line 956) ! * Wno-suggest-final-methods: Warning Options. (line 1000) ! * Wno-suggest-final-types: Warning Options. (line 991) ! * Wno-switch: Warning Options. (line 631) ! * Wno-switch-bool: Warning Options. (line 651) ! * Wno-switch-default: Warning Options. (line 639) ! * Wno-switch-enum: Warning Options. (line 642) ! * Wno-sync-nand: Warning Options. (line 662) ! * Wno-system-headers: Warning Options. (line 1081) ! * Wno-tautological-compare: Warning Options. (line 1092) * Wno-terminate: C++ Dialect Options. ! (line 721) ! * Wno-traditional: Warning Options. (line 1125) ! * Wno-traditional-conversion: Warning Options. (line 1202) ! * Wno-trampolines: Warning Options. (line 1100) ! * Wno-trigraphs: Warning Options. (line 667) ! * Wno-type-limits: Warning Options. (line 1326) * Wno-undeclared-selector: Objective-C and Objective-C++ Dialect Options. (line 205) ! * Wno-undef: Warning Options. (line 1216) ! * Wno-uninitialized: Warning Options. (line 768) ! * Wno-unknown-pragmas: Warning Options. (line 850) ! * Wno-unsafe-loop-optimizations: Warning Options. (line 1271) ! * Wno-unused: Warning Options. (line 761) ! * Wno-unused-but-set-parameter: Warning Options. (line 672) ! * Wno-unused-but-set-variable: Warning Options. (line 681) ! * Wno-unused-const-variable: Warning Options. (line 728) ! * Wno-unused-function: Warning Options. (line 691) ! * Wno-unused-label: Warning Options. (line 696) ! * Wno-unused-parameter: Warning Options. (line 707) ! * Wno-unused-result: Warning Options. (line 714) ! * Wno-unused-value: Warning Options. (line 751) ! * Wno-unused-variable: Warning Options. (line 719) ! * Wno-useless-cast: Warning Options. (line 1458) ! * Wno-varargs: Warning Options. (line 1851) ! * Wno-variadic-macros: Warning Options. (line 1845) ! * Wno-vector-operation-performance: Warning Options. (line 1856) ! * Wno-virtual-move-assign: Warning Options. (line 1866) ! * Wno-vla: Warning Options. (line 1875) ! * Wno-volatile-register-var: Warning Options. (line 1879) ! * Wno-write-strings: Warning Options. (line 1390) ! * Wno-zero-as-null-pointer-constant: Warning Options. (line 1432) * Wnoexcept: C++ Dialect Options. ! (line 568) * Wnon-template-friend: C++ Dialect Options. ! (line 642) * Wnon-virtual-dtor: C++ Dialect Options. ! (line 574) ! * Wnonnull: Warning Options. (line 367) ! * Wnonnull-compare: Warning Options. (line 374) ! * Wnormalized: Warning Options. (line 1670) ! * Wnormalized=: Warning Options. (line 1670) ! * Wnull-dereference: Warning Options. (line 381) ! * Wodr: Warning Options. (line 1726) * Wold-style-cast: C++ Dialect Options. - (line 658) - * Wold-style-declaration: Warning Options. (line 1602) - * Wold-style-definition: Warning Options. (line 1608) - * Wopenm-simd: Warning Options. (line 1731) - * Woverflow: Warning Options. (line 1723) - * Woverlength-strings: Warning Options. (line 1905) - * Woverloaded-virtual: C++ Dialect Options. (line 664) ! * Woverride-init: Warning Options. (line 1736) ! * Woverride-init-side-effects: Warning Options. (line 1744) * Wp: Preprocessor Options. (line 14) ! * Wpacked: Warning Options. (line 1749) ! * Wpacked-bitfield-compat: Warning Options. (line 1766) ! * Wpadded: Warning Options. (line 1783) ! * Wparentheses: Warning Options. (line 490) ! * Wpedantic: Warning Options. (line 80) ! * Wpedantic-ms-format: Warning Options. (line 1277) ! * Wplacement-new: Warning Options. (line 1284) * Wpmf-conversions: C++ Dialect Options. ! (line 683) ! * Wpointer-arith: Warning Options. (line 1319) * Wpointer-arith <1>: Pointer Arith. (line 13) ! * Wpointer-sign: Warning Options. (line 1894) ! * Wpointer-to-int-cast: Warning Options. (line 1832) ! * Wpragmas: Warning Options. (line 857) * Wprotocol: Objective-C and Objective-C++ Dialect Options. (line 175) * wrapper: Overall Options. (line 346) ! * Wredundant-decls: Warning Options. (line 1790) * Wreorder: C++ Dialect Options. ! (line 582) ! * Wreturn-local-addr: Warning Options. (line 585) ! * Wreturn-type: Warning Options. (line 589) * Wselector: Objective-C and Objective-C++ Dialect Options. (line 185) ! * Wsequence-point: Warning Options. (line 539) ! * Wshadow: Warning Options. (line 1223) ! * Wshadow-ivar: Warning Options. (line 1231) ! * Wshift-count-negative: Warning Options. (line 603) ! * Wshift-count-overflow: Warning Options. (line 607) ! * Wshift-negative-value: Warning Options. (line 611) ! * Wshift-overflow: Warning Options. (line 616) ! * Wsign-compare: Warning Options. (line 1482) ! * Wsign-conversion: Warning Options. (line 1488) * Wsign-promo: C++ Dialect Options. ! (line 687) ! * Wsized-deallocation: Warning Options. (line 1504) ! * Wsizeof-array-argument: Warning Options. (line 1523) ! * Wsizeof-pointer-memaccess: Warning Options. (line 1515) ! * Wstack-protector: Warning Options. (line 1900) ! * Wstack-usage: Warning Options. (line 1251) ! * Wstrict-aliasing: Warning Options. (line 862) ! * Wstrict-aliasing=n: Warning Options. (line 869) * Wstrict-null-sentinel: C++ Dialect Options. ! (line 635) ! * Wstrict-overflow: Warning Options. (line 901) ! * Wstrict-prototypes: Warning Options. (line 1596) * Wstrict-selector-match: Objective-C and Objective-C++ Dialect Options. (line 197) ! * Wsubobject-linkage: Warning Options. (line 1436) ! * Wsuggest-attribute=: Warning Options. (line 950) ! * Wsuggest-attribute=const: Warning Options. (line 956) ! * Wsuggest-attribute=format: Warning Options. (line 970) ! * Wsuggest-attribute=noreturn: Warning Options. (line 956) ! * Wsuggest-attribute=pure: Warning Options. (line 956) ! * Wsuggest-final-methods: Warning Options. (line 1000) ! * Wsuggest-final-types: Warning Options. (line 991) ! * Wswitch: Warning Options. (line 631) ! * Wswitch-bool: Warning Options. (line 651) ! * Wswitch-default: Warning Options. (line 639) ! * Wswitch-enum: Warning Options. (line 642) ! * Wsync-nand: Warning Options. (line 662) ! * Wsystem-headers: Warning Options. (line 1081) * Wsystem-headers <1>: Preprocessor Options. (line 165) ! * Wtautological-compare: Warning Options. (line 1092) * Wtemplates: C++ Dialect Options. ! (line 693) * Wterminate: C++ Dialect Options. ! (line 721) ! * Wtraditional: Warning Options. (line 1125) * Wtraditional <1>: Preprocessor Options. (line 118) ! * Wtraditional-conversion: Warning Options. (line 1202) ! * Wtrampolines: Warning Options. (line 1100) ! * Wtrigraphs: Warning Options. (line 667) * Wtrigraphs <1>: Preprocessor Options. (line 106) ! * Wtype-limits: Warning Options. (line 1326) * Wundeclared-selector: Objective-C and Objective-C++ Dialect Options. (line 205) - * Wundef: Warning Options. (line 1216) * Wundef <1>: Preprocessor Options. (line 124) ! * Wuninitialized: Warning Options. (line 768) ! * Wunknown-pragmas: Warning Options. (line 850) ! * Wunsafe-loop-optimizations: Warning Options. (line 1271) ! * Wunsuffixed-float-constants: Warning Options. (line 1920) ! * Wunused: Warning Options. (line 761) ! * Wunused-but-set-parameter: Warning Options. (line 672) ! * Wunused-but-set-variable: Warning Options. (line 681) ! * Wunused-const-variable: Warning Options. (line 728) ! * Wunused-function: Warning Options. (line 691) ! * Wunused-label: Warning Options. (line 696) ! * Wunused-local-typedefs: Warning Options. (line 703) * Wunused-macros: Preprocessor Options. (line 129) ! * Wunused-parameter: Warning Options. (line 707) ! * Wunused-result: Warning Options. (line 714) ! * Wunused-value: Warning Options. (line 751) ! * Wunused-variable: Warning Options. (line 719) ! * Wuseless-cast: Warning Options. (line 1458) ! * Wvarargs: Warning Options. (line 1851) ! * Wvariadic-macros: Warning Options. (line 1845) ! * Wvector-operation-performance: Warning Options. (line 1856) * Wvirtual-inheritance: C++ Dialect Options. ! (line 707) ! * Wvirtual-move-assign: Warning Options. (line 1866) ! * Wvla: Warning Options. (line 1875) ! * Wvolatile-register-var: Warning Options. (line 1879) ! * Wwrite-strings: Warning Options. (line 1390) ! * Wzero-as-null-pointer-constant: Warning Options. (line 1432) ! * x: Overall Options. (line 126) * x <1>: Preprocessor Options. ! (line 324) * Xassembler: Assembler Options. (line 13) * Xbind-lazy: VxWorks Options. (line 26) * Xbind-now: VxWorks Options. (line 30) ! * Xlinker: Link Options. (line 247) * Xpreprocessor: Preprocessor Options. (line 25) * Ym: System V Options. (line 26) * YP: System V Options. (line 22) ! * z: Link Options. (line 278)  File: gcc.info, Node: Keyword Index, Prev: Option Index, Up: Top --- 54196,54850 ---- * noseglinkedit: Darwin Options. (line 196) * nostartfiles: Link Options. (line 63) * nostdinc: Preprocessor Options. ! (line 399) * nostdinc++ <1>: Preprocessor Options. ! (line 404) ! * nostdinc++: C++ Dialect Options. ! (line 395) * nostdlib: Link Options. (line 80) ! * o: Preprocessor Options. (line 87) + * O: Optimize Options. (line 39) + * o: Overall Options. (line 184) * O0: Optimize Options. (line 148) * O1: Optimize Options. (line 39) * O2: Optimize Options. (line 93) * O3: Optimize Options. (line 139) * Ofast: Optimize Options. (line 162) ! * Og: Optimize Options. (line 169) * Os: Optimize Options. (line 152) + * P: Preprocessor Options. + (line 648) * p: Instrumentation Options. (line 19) * pagezero_size: Darwin Options. (line 196) ! * param: Optimize Options. (line 2330) * pass-exit-codes: Overall Options. (line 323) ! * pedantic <1>: Warnings and Errors. ! (line 25) ! * pedantic <2>: Alternate Keywords. (line 30) * pedantic <3>: C Extensions. (line 6) ! * pedantic <4>: Preprocessor Options. ! (line 175) ! * pedantic <5>: Warning Options. (line 82) ! * pedantic: Standards. (line 13) ! * pedantic-errors <1>: Warnings and Errors. (line 25) ! * pedantic-errors <2>: Non-bugs. (line 216) ! * pedantic-errors <3>: Preprocessor Options. (line 180) ! * pedantic-errors <4>: Warning Options. (line 124) ! * pedantic-errors: Standards. (line 13) * pg: Instrumentation Options. (line 25) * pie: Link Options. (line 105) * pipe: Overall Options. (line 331) * prebind: Darwin Options. (line 196) * prebind_all_twolevel_modules: Darwin Options. (line 196) ! * print-file-name: Developer Options. (line 980) ! * print-libgcc-file-name: Developer Options. (line 1014) ! * print-multi-directory: Developer Options. (line 986) ! * print-multi-lib: Developer Options. (line 991) ! * print-multi-os-directory: Developer Options. (line 998) ! * print-multiarch: Developer Options. (line 1007) * print-objc-runtime-info: Objective-C and Objective-C++ Dialect Options. (line 217) ! * print-prog-name: Developer Options. (line 1011) ! * print-search-dirs: Developer Options. (line 1022) ! * print-sysroot: Developer Options. (line 1035) ! * print-sysroot-headers-suffix: Developer Options. (line 1042) * private_bundle: Darwin Options. (line 196) + * pthread <1>: Solaris 2 Options. (line 38) * pthread: RS/6000 and PowerPC Options. ! (line 863) ! * pthreads: Solaris 2 Options. (line 32) ! * Q: Developer Options. (line 887) * Qn: System V Options. (line 18) * Qy: System V Options. (line 14) * rdynamic: Link Options. (line 114) * read_only_relocs: Darwin Options. (line 196) * remap: Preprocessor Options. ! (line 696) * s: Link Options. (line 121) ! * S <1>: Link Options. (line 20) ! * S: Overall Options. (line 167) ! * save-temps: Developer Options. (line 762) ! * save-temps=obj: Developer Options. (line 788) * sectalign: Darwin Options. (line 196) * sectcreate: Darwin Options. (line 196) * sectobjectsymbols: Darwin Options. (line 196) * sectorder: Darwin Options. (line 196) * seg1addr: Darwin Options. (line 196) + * seg_addr_table: Darwin Options. (line 196) + * seg_addr_table_filename: Darwin Options. (line 196) * segaddr: Darwin Options. (line 196) * seglinkedit: Darwin Options. (line 196) * segprot: Darwin Options. (line 196) * segs_read_only_addr: Darwin Options. (line 196) * segs_read_write_addr: Darwin Options. (line 196) ! * shared: Link Options. (line 130) ! * shared-libgcc: Link Options. (line 138) * short-calls: Adapteva Epiphany Options. (line 61) * sim: CRIS Options. (line 95) * sim2: CRIS Options. (line 101) * single_module: Darwin Options. (line 196) * specs: Overall Options. (line 337) + * static <1>: HPPA Options. (line 185) + * static <2>: Darwin Options. (line 196) * static: Link Options. (line 125) ! * static-libasan: Link Options. (line 173) ! * static-libgcc: Link Options. (line 138) ! * static-liblsan: Link Options. (line 191) ! * static-libmpx: Link Options. (line 209) ! * static-libmpxwrappers: Link Options. (line 218) ! * static-libstdc++: Link Options. (line 228) ! * static-libtsan: Link Options. (line 182) ! * static-libubsan: Link Options. (line 200) ! * std <1>: Non-bugs. (line 107) * std <2>: Other Builtins. (line 31) ! * std <3>: C Dialect Options. (line 47) ! * std: Standards. (line 13) * std=: Preprocessor Options. ! (line 338) * sub_library: Darwin Options. (line 196) * sub_umbrella: Darwin Options. (line 196) ! * symbolic: Link Options. (line 239) ! * sysroot: Directory Options. (line 92) ! * T: Link Options. (line 245) * target-help <1>: Preprocessor Options. ! (line 701) ! * target-help: Overall Options. (line 216) * threads: HPPA Options. (line 198) ! * time: Developer Options. (line 803) * tno-android-cc: GNU/Linux Options. (line 36) * tno-android-ld: GNU/Linux Options. (line 40) * traditional <1>: Incompatibilities. (line 6) ! * traditional: C Dialect Options. (line 347) * traditional-cpp <1>: Preprocessor Options. ! (line 679) ! * traditional-cpp: C Dialect Options. (line 347) * trigraphs <1>: Preprocessor Options. ! (line 683) ! * trigraphs: C Dialect Options. (line 342) * twolevel_namespace: Darwin Options. (line 196) + * u: Link Options. (line 277) * U: Preprocessor Options. (line 69) * umbrella: Darwin Options. (line 196) * undef: Preprocessor Options. (line 73) * undefined: Darwin Options. (line 196) * unexported_symbols_list: Darwin Options. (line 196) * v <1>: Preprocessor Options. ! (line 705) ! * v: Overall Options. (line 195) * version <1>: Preprocessor Options. ! (line 718) ! * version: Overall Options. (line 320) ! * W: Incompatibilities. (line 64) ! * w <1>: ARC Options. (line 122) ! * w: Preprocessor Options. (line 171) ! * W: Warning Options. (line 193) ! * w: Warning Options. (line 25) * Wa: Assembler Options. (line 9) * Wabi: C++ Dialect Options. ! (line 403) * Wabi-tag: C++ Dialect Options. ! (line 510) ! * Waddr-space-convert: AVR Options. (line 236) ! * Waddress: Warning Options. (line 1558) ! * Waggregate-return: Warning Options. (line 1594) ! * Waggressive-loop-optimizations: Warning Options. (line 1599) ! * Wall <1>: Standard Libraries. (line 6) ! * Wall <2>: Preprocessor Options. (line 93) ! * Wall: Warning Options. (line 133) ! * Warray-bounds: Warning Options. (line 1027) * Wassign-intercept: Objective-C and Objective-C++ Dialect Options. (line 171) ! * Wattributes: Warning Options. (line 1604) ! * Wbad-function-cast: Warning Options. (line 1349) ! * Wbool-compare: Warning Options. (line 1043) ! * Wbuiltin-macro-redefined: Warning Options. (line 1610) ! * Wc++-compat: Warning Options. (line 1371) ! * Wc++11-compat: Warning Options. (line 1376) ! * Wc++14-compat: Warning Options. (line 1382) ! * Wc90-c99-compat: Warning Options. (line 1354) ! * Wc99-c11-compat: Warning Options. (line 1362) ! * Wcast-align: Warning Options. (line 1402) ! * Wcast-qual: Warning Options. (line 1386) ! * Wchar-subscripts: Warning Options. (line 233) ! * Wchkp: Warning Options. (line 243) ! * Wclobbered: Warning Options. (line 1422) * Wcomment <1>: Preprocessor Options. (line 101) + * Wcomment: Warning Options. (line 238) * Wcomments: Preprocessor Options. (line 101) ! * Wconditionally-supported: Warning Options. (line 1426) ! * Wconversion: Warning Options. (line 1429) ! * Wconversion-null: Warning Options. (line 1447) * Wctor-dtor-privacy: C++ Dialect Options. ! (line 515) ! * Wdate-time: Warning Options. (line 1468) ! * Wdeclaration-after-statement: Warning Options. (line 1223) ! * Wdelete-incomplete: Warning Options. (line 1473) * Wdelete-non-virtual-dtor: C++ Dialect Options. ! (line 522) ! * Wdeprecated: Warning Options. (line 1733) ! * Wdeprecated-declarations: Warning Options. (line 1737) ! * Wdisabled-optimization: Warning Options. (line 1906) ! * Wdiscarded-array-qualifiers: Warning Options. (line 1070) ! * Wdiscarded-qualifiers: Warning Options. (line 1064) ! * Wdiv-by-zero: Warning Options. (line 1088) ! * Wdouble-promotion: Warning Options. (line 266) ! * Wduplicated-cond: Warning Options. (line 1052) * weak_reference_mismatches: Darwin Options. (line 196) * Weffc++: C++ Dialect Options. ! (line 611) ! * Wempty-body: Warning Options. (line 1480) * Wendif-labels <1>: Preprocessor Options. (line 148) ! * Wendif-labels: Warning Options. (line 1232) ! * Wenum-compare: Warning Options. (line 1484) * Werror <1>: Preprocessor Options. (line 161) + * Werror: Warning Options. (line 28) * Werror=: Warning Options. (line 31) ! * Wextra: Warning Options. (line 193) * Wfatal-errors: Warning Options. (line 48) ! * Wfloat-conversion: Warning Options. (line 1513) ! * Wfloat-equal: Warning Options. (line 1122) ! * Wformat <1>: Common Function Attributes. (line 234) ! * Wformat: Warning Options. (line 285) ! * Wformat-contains-nul: Warning Options. (line 322) ! * Wformat-extra-args: Warning Options. (line 326) * Wformat-nonliteral <1>: Common Function Attributes. ! (line 300) ! * Wformat-nonliteral: Warning Options. (line 350) ! * Wformat-security: Warning Options. (line 355) ! * Wformat-signedness: Warning Options. (line 367) ! * Wformat-y2k: Warning Options. (line 372) ! * Wformat-zero-length: Warning Options. (line 340) ! * Wformat=: Warning Options. (line 285) ! * Wformat=1: Warning Options. (line 312) ! * Wformat=2: Warning Options. (line 345) ! * Wframe-address: Warning Options. (line 1058) ! * Wframe-larger-than: Warning Options. (line 1251) ! * Wfree-nonheap-object: Warning Options. (line 1260) * whatsloaded: Darwin Options. (line 196) * whyload: Darwin Options. (line 196) ! * Wignored-attributes: Warning Options. (line 437) ! * Wignored-qualifiers: Warning Options. (line 426) ! * Wimplicit: Warning Options. (line 422) ! * Wimplicit-function-declaration: Warning Options. (line 416) ! * Wimplicit-int: Warning Options. (line 412) ! * Wincompatible-pointer-types: Warning Options. (line 1076) ! * Winherited-variadic-ctor: Warning Options. (line 1818) ! * Winit-self: Warning Options. (line 397) * Winline <1>: Inline. (line 60) ! * Winline: Warning Options. (line 1823) ! * Wint-conversion: Warning Options. (line 1082) ! * Wint-to-pointer-cast: Warning Options. (line 1848) ! * Winvalid-memory-model: Warning Options. (line 801) ! * Winvalid-offsetof: Warning Options. (line 1836) ! * Winvalid-pch: Warning Options. (line 1857) ! * Wjump-misses-init: Warning Options. (line 1490) ! * Wl: Link Options. (line 269) ! * Wlarger-than-LEN: Warning Options. (line 1248) ! * Wlarger-than=LEN: Warning Options. (line 1248) ! * wlh1: ARC Options. (line 127) ! * wlh2: ARC Options. (line 132) ! * wlh3: ARC Options. (line 137) ! * wlh4: ARC Options. (line 142) ! * wlh5: ARC Options. (line 147) * Wliteral-suffix: C++ Dialect Options. ! (line 529) ! * Wlogical-not-parentheses: Warning Options. (line 1579) ! * Wlogical-op: Warning Options. (line 1571) ! * Wlong-long: Warning Options. (line 1861) * Wlto-type-mismatch: C++ Dialect Options. ! (line 550) ! * Wmain: Warning Options. (line 444) ! * Wmaybe-uninitialized: Warning Options. (line 818) ! * Wmemset-transposed-args: Warning Options. (line 1547) ! * Wmisleading-indentation: Warning Options. (line 451) ! * Wmissing-braces: Warning Options. (line 485) ! * Wmissing-declarations: Warning Options. (line 1649) ! * Wmissing-field-initializers: Warning Options. (line 1659) ! * Wmissing-format-attribute: Warning Options. (line 982) ! * Wmissing-include-dirs: Warning Options. (line 496) ! * Wmissing-parameter-type: Warning Options. (line 1631) ! * Wmissing-prototypes: Warning Options. (line 1639) ! * Wmultichar: Warning Options. (line 1683) * Wmultiple-inheritance: C++ Dialect Options. ! (line 706) * Wnamespaces: C++ Dialect Options. ! (line 722) * Wnarrowing: C++ Dialect Options. ! (line 555) ! * Wnested-externs: Warning Options. (line 1815) * Wno-abi: C++ Dialect Options. ! (line 403) ! * Wno-address: Warning Options. (line 1558) ! * Wno-aggregate-return: Warning Options. (line 1594) ! * Wno-aggressive-loop-optimizations: Warning Options. (line 1599) ! * Wno-all: Warning Options. (line 133) ! * Wno-array-bounds: Warning Options. (line 1027) * Wno-assign-intercept: Objective-C and Objective-C++ Dialect Options. (line 171) ! * Wno-attributes: Warning Options. (line 1604) ! * Wno-bad-function-cast: Warning Options. (line 1349) ! * Wno-bool-compare: Warning Options. (line 1043) ! * Wno-builtin-macro-redefined: Warning Options. (line 1610) ! * Wno-c90-c99-compat: Warning Options. (line 1354) ! * Wno-c99-c11-compat: Warning Options. (line 1362) ! * Wno-cast-align: Warning Options. (line 1402) ! * Wno-cast-qual: Warning Options. (line 1386) ! * Wno-char-subscripts: Warning Options. (line 233) ! * Wno-clobbered: Warning Options. (line 1422) ! * Wno-comment: Warning Options. (line 238) ! * Wno-conditionally-supported: Warning Options. (line 1426) ! * Wno-conversion: Warning Options. (line 1429) ! * Wno-conversion-null: Warning Options. (line 1447) ! * Wno-coverage-mismatch: Warning Options. (line 247) * Wno-ctor-dtor-privacy: C++ Dialect Options. ! (line 515) ! * Wno-date-time: Warning Options. (line 1468) ! * Wno-declaration-after-statement: Warning Options. (line 1223) ! * Wno-delete-incomplete: Warning Options. (line 1473) * Wno-delete-non-virtual-dtor: C++ Dialect Options. ! (line 522) ! * Wno-deprecated: Warning Options. (line 1733) ! * Wno-deprecated-declarations: Warning Options. (line 1737) ! * Wno-disabled-optimization: Warning Options. (line 1906) ! * Wno-discarded-array-qualifiers: Warning Options. (line 1070) ! * Wno-discarded-qualifiers: Warning Options. (line 1064) ! * Wno-div-by-zero: Warning Options. (line 1088) ! * Wno-double-promotion: Warning Options. (line 266) ! * Wno-duplicated-cond: Warning Options. (line 1052) * Wno-effc++: C++ Dialect Options. ! (line 611) ! * Wno-empty-body: Warning Options. (line 1480) ! * Wno-endif-labels: Warning Options. (line 1232) ! * Wno-enum-compare: Warning Options. (line 1484) * Wno-error: Warning Options. (line 28) * Wno-error=: Warning Options. (line 31) ! * Wno-extra: Warning Options. (line 193) * Wno-fatal-errors: Warning Options. (line 48) ! * Wno-float-conversion: Warning Options. (line 1513) ! * Wno-float-equal: Warning Options. (line 1122) ! * Wno-format: Warning Options. (line 285) ! * Wno-format-contains-nul: Warning Options. (line 322) ! * Wno-format-extra-args: Warning Options. (line 326) ! * Wno-format-nonliteral: Warning Options. (line 350) ! * Wno-format-security: Warning Options. (line 355) ! * Wno-format-signedness: Warning Options. (line 367) ! * Wno-format-y2k: Warning Options. (line 372) ! * Wno-format-zero-length: Warning Options. (line 340) ! * Wno-frame-address: Warning Options. (line 1058) ! * Wno-free-nonheap-object: Warning Options. (line 1260) ! * Wno-ignored-attributes: Warning Options. (line 437) ! * Wno-ignored-qualifiers: Warning Options. (line 426) ! * Wno-implicit: Warning Options. (line 422) ! * Wno-implicit-function-declaration: Warning Options. (line 416) ! * Wno-implicit-int: Warning Options. (line 412) ! * Wno-incompatible-pointer-types: Warning Options. (line 1076) ! * Wno-inherited-variadic-ctor: Warning Options. (line 1818) ! * Wno-init-self: Warning Options. (line 397) ! * Wno-inline: Warning Options. (line 1823) ! * Wno-int-conversion: Warning Options. (line 1082) ! * Wno-int-to-pointer-cast: Warning Options. (line 1848) ! * Wno-invalid-memory-model: Warning Options. (line 801) ! * Wno-invalid-offsetof: Warning Options. (line 1836) ! * Wno-invalid-pch: Warning Options. (line 1857) ! * Wno-jump-misses-init: Warning Options. (line 1490) * Wno-literal-suffix: C++ Dialect Options. ! (line 529) ! * Wno-logical-not-parentheses: Warning Options. (line 1579) ! * Wno-logical-op: Warning Options. (line 1571) ! * Wno-long-long: Warning Options. (line 1861) * Wno-lto-type-mismatch: C++ Dialect Options. ! (line 550) ! * Wno-main: Warning Options. (line 444) ! * Wno-maybe-uninitialized: Warning Options. (line 818) ! * Wno-memset-transposed-args: Warning Options. (line 1547) ! * Wno-misleading-indentation: Warning Options. (line 451) ! * Wno-missing-braces: Warning Options. (line 485) ! * Wno-missing-declarations: Warning Options. (line 1649) ! * Wno-missing-field-initializers: Warning Options. (line 1659) ! * Wno-missing-format-attribute: Warning Options. (line 982) ! * Wno-missing-include-dirs: Warning Options. (line 496) ! * Wno-missing-parameter-type: Warning Options. (line 1631) ! * Wno-missing-prototypes: Warning Options. (line 1639) ! * Wno-multichar: Warning Options. (line 1683) * Wno-narrowing: C++ Dialect Options. ! (line 555) ! * Wno-nested-externs: Warning Options. (line 1815) * Wno-noexcept: C++ Dialect Options. ! (line 572) * Wno-non-template-friend: C++ Dialect Options. ! (line 648) * Wno-non-virtual-dtor: C++ Dialect Options. ! (line 578) ! * Wno-nonnull: Warning Options. (line 376) ! * Wno-nonnull-compare: Warning Options. (line 383) ! * Wno-normalized: Warning Options. (line 1689) ! * Wno-null-dereference: Warning Options. (line 390) ! * Wno-odr: Warning Options. (line 1746) * Wno-old-style-cast: C++ Dialect Options. (line 664) ! * Wno-old-style-declaration: Warning Options. (line 1621) ! * Wno-old-style-definition: Warning Options. (line 1627) ! * Wno-overflow: Warning Options. (line 1743) ! * Wno-overlength-strings: Warning Options. (line 1926) ! * Wno-overloaded-virtual: C++ Dialect Options. ! (line 670) ! * Wno-override-init: Warning Options. (line 1756) ! * Wno-override-init-side-effects: Warning Options. (line 1764) ! * Wno-packed: Warning Options. (line 1769) ! * Wno-packed-bitfield-compat: Warning Options. (line 1786) ! * Wno-padded: Warning Options. (line 1803) ! * Wno-parentheses: Warning Options. (line 499) ! * Wno-pedantic-ms-format: Warning Options. (line 1292) ! * Wno-placement-new: Warning Options. (line 1299) * Wno-pmf-conversions <1>: Bound member functions. (line 35) ! * Wno-pmf-conversions: C++ Dialect Options. ! (line 689) ! * Wno-pointer-arith: Warning Options. (line 1335) ! * Wno-pointer-sign: Warning Options. (line 1915) ! * Wno-pointer-to-int-cast: Warning Options. (line 1853) ! * Wno-pragmas: Warning Options. (line 868) * Wno-protocol: Objective-C and Objective-C++ Dialect Options. (line 175) ! * Wno-redundant-decls: Warning Options. (line 1810) * Wno-reorder: C++ Dialect Options. ! (line 586) ! * Wno-return-local-addr: Warning Options. (line 594) ! * Wno-return-type: Warning Options. (line 598) * Wno-selector: Objective-C and Objective-C++ Dialect Options. (line 185) ! * Wno-sequence-point: Warning Options. (line 548) ! * Wno-shadow: Warning Options. (line 1236) ! * Wno-shadow-ivar: Warning Options. (line 1244) ! * Wno-shift-count-negative: Warning Options. (line 613) ! * Wno-shift-count-overflow: Warning Options. (line 617) ! * Wno-shift-negative-value: Warning Options. (line 621) ! * Wno-shift-overflow: Warning Options. (line 626) ! * Wno-sign-compare: Warning Options. (line 1501) ! * Wno-sign-conversion: Warning Options. (line 1507) * Wno-sign-promo: C++ Dialect Options. ! (line 693) ! * Wno-sized-deallocation: Warning Options. (line 1523) ! * Wno-sizeof-array-argument: Warning Options. (line 1542) ! * Wno-sizeof-pointer-memaccess: Warning Options. (line 1534) ! * Wno-stack-protector: Warning Options. (line 1921) ! * Wno-strict-aliasing: Warning Options. (line 873) * Wno-strict-null-sentinel: C++ Dialect Options. ! (line 640) ! * Wno-strict-overflow: Warning Options. (line 913) ! * Wno-strict-prototypes: Warning Options. (line 1615) * Wno-strict-selector-match: Objective-C and Objective-C++ Dialect Options. (line 197) ! * Wno-subobject-linkage: Warning Options. (line 1455) ! * Wno-suggest-attribute=: Warning Options. (line 963) ! * Wno-suggest-attribute=const: Warning Options. (line 969) ! * Wno-suggest-attribute=format: Warning Options. (line 982) ! * Wno-suggest-attribute=noreturn: Warning Options. (line 969) ! * Wno-suggest-attribute=pure: Warning Options. (line 969) ! * Wno-suggest-final-methods: Warning Options. (line 1012) ! * Wno-suggest-final-types: Warning Options. (line 1003) ! * Wno-switch: Warning Options. (line 641) ! * Wno-switch-bool: Warning Options. (line 661) ! * Wno-switch-default: Warning Options. (line 649) ! * Wno-switch-enum: Warning Options. (line 652) ! * Wno-sync-nand: Warning Options. (line 672) ! * Wno-system-headers: Warning Options. (line 1093) ! * Wno-tautological-compare: Warning Options. (line 1104) * Wno-terminate: C++ Dialect Options. ! (line 729) ! * Wno-traditional: Warning Options. (line 1137) ! * Wno-traditional-conversion: Warning Options. (line 1215) ! * Wno-trampolines: Warning Options. (line 1112) ! * Wno-trigraphs: Warning Options. (line 677) ! * Wno-type-limits: Warning Options. (line 1342) * Wno-undeclared-selector: Objective-C and Objective-C++ Dialect Options. (line 205) ! * Wno-undef: Warning Options. (line 1229) ! * Wno-uninitialized: Warning Options. (line 778) ! * Wno-unknown-pragmas: Warning Options. (line 861) ! * Wno-unsafe-loop-optimizations: Warning Options. (line 1286) ! * Wno-unused: Warning Options. (line 771) ! * Wno-unused-but-set-parameter: Warning Options. (line 682) ! * Wno-unused-but-set-variable: Warning Options. (line 691) ! * Wno-unused-const-variable: Warning Options. (line 738) ! * Wno-unused-function: Warning Options. (line 701) ! * Wno-unused-label: Warning Options. (line 706) ! * Wno-unused-parameter: Warning Options. (line 717) ! * Wno-unused-result: Warning Options. (line 724) ! * Wno-unused-value: Warning Options. (line 761) ! * Wno-unused-variable: Warning Options. (line 729) ! * Wno-useless-cast: Warning Options. (line 1477) ! * Wno-varargs: Warning Options. (line 1872) ! * Wno-variadic-macros: Warning Options. (line 1866) ! * Wno-vector-operation-performance: Warning Options. (line 1877) ! * Wno-virtual-move-assign: Warning Options. (line 1887) ! * Wno-vla: Warning Options. (line 1896) ! * Wno-volatile-register-var: Warning Options. (line 1900) ! * Wno-write-strings: Warning Options. (line 1408) ! * Wno-zero-as-null-pointer-constant: Warning Options. (line 1451) * Wnoexcept: C++ Dialect Options. ! (line 572) * Wnon-template-friend: C++ Dialect Options. ! (line 648) * Wnon-virtual-dtor: C++ Dialect Options. ! (line 578) ! * Wnonnull: Warning Options. (line 376) ! * Wnonnull-compare: Warning Options. (line 383) ! * Wnormalized: Warning Options. (line 1689) ! * Wnormalized=: Warning Options. (line 1689) ! * Wnull-dereference: Warning Options. (line 390) ! * Wodr: Warning Options. (line 1746) * Wold-style-cast: C++ Dialect Options. (line 664) ! * Wold-style-declaration: Warning Options. (line 1621) ! * Wold-style-definition: Warning Options. (line 1627) ! * Wopenm-simd: Warning Options. (line 1751) ! * Woverflow: Warning Options. (line 1743) ! * Woverlength-strings: Warning Options. (line 1926) ! * Woverloaded-virtual: C++ Dialect Options. ! (line 670) ! * Woverride-init: Warning Options. (line 1756) ! * Woverride-init-side-effects: Warning Options. (line 1764) * Wp: Preprocessor Options. (line 14) ! * Wpacked: Warning Options. (line 1769) ! * Wpacked-bitfield-compat: Warning Options. (line 1786) ! * Wpadded: Warning Options. (line 1803) ! * Wparentheses: Warning Options. (line 499) ! * Wpedantic: Warning Options. (line 82) ! * Wpedantic-ms-format: Warning Options. (line 1292) ! * Wplacement-new: Warning Options. (line 1299) * Wpmf-conversions: C++ Dialect Options. ! (line 689) * Wpointer-arith <1>: Pointer Arith. (line 13) ! * Wpointer-arith: Warning Options. (line 1335) ! * Wpointer-sign: Warning Options. (line 1915) ! * Wpointer-to-int-cast: Warning Options. (line 1853) ! * Wpragmas: Warning Options. (line 868) * Wprotocol: Objective-C and Objective-C++ Dialect Options. (line 175) * wrapper: Overall Options. (line 346) ! * Wredundant-decls: Warning Options. (line 1810) * Wreorder: C++ Dialect Options. ! (line 586) ! * Wreturn-local-addr: Warning Options. (line 594) ! * Wreturn-type: Warning Options. (line 598) * Wselector: Objective-C and Objective-C++ Dialect Options. (line 185) ! * Wsequence-point: Warning Options. (line 548) ! * Wshadow: Warning Options. (line 1236) ! * Wshadow-ivar: Warning Options. (line 1244) ! * Wshift-count-negative: Warning Options. (line 613) ! * Wshift-count-overflow: Warning Options. (line 617) ! * Wshift-negative-value: Warning Options. (line 621) ! * Wshift-overflow: Warning Options. (line 626) ! * Wsign-compare: Warning Options. (line 1501) ! * Wsign-conversion: Warning Options. (line 1507) * Wsign-promo: C++ Dialect Options. ! (line 693) ! * Wsized-deallocation: Warning Options. (line 1523) ! * Wsizeof-array-argument: Warning Options. (line 1542) ! * Wsizeof-pointer-memaccess: Warning Options. (line 1534) ! * Wstack-protector: Warning Options. (line 1921) ! * Wstack-usage: Warning Options. (line 1264) ! * Wstrict-aliasing: Warning Options. (line 873) ! * Wstrict-aliasing=n: Warning Options. (line 881) * Wstrict-null-sentinel: C++ Dialect Options. ! (line 640) ! * Wstrict-overflow: Warning Options. (line 913) ! * Wstrict-prototypes: Warning Options. (line 1615) * Wstrict-selector-match: Objective-C and Objective-C++ Dialect Options. (line 197) ! * Wsubobject-linkage: Warning Options. (line 1455) ! * Wsuggest-attribute=: Warning Options. (line 963) ! * Wsuggest-attribute=const: Warning Options. (line 969) ! * Wsuggest-attribute=format: Warning Options. (line 982) ! * Wsuggest-attribute=noreturn: Warning Options. (line 969) ! * Wsuggest-attribute=pure: Warning Options. (line 969) ! * Wsuggest-final-methods: Warning Options. (line 1012) ! * Wsuggest-final-types: Warning Options. (line 1003) ! * Wswitch: Warning Options. (line 641) ! * Wswitch-bool: Warning Options. (line 661) ! * Wswitch-default: Warning Options. (line 649) ! * Wswitch-enum: Warning Options. (line 652) ! * Wsync-nand: Warning Options. (line 672) * Wsystem-headers <1>: Preprocessor Options. (line 165) ! * Wsystem-headers: Warning Options. (line 1093) ! * Wtautological-compare: Warning Options. (line 1104) * Wtemplates: C++ Dialect Options. ! (line 699) * Wterminate: C++ Dialect Options. ! (line 729) * Wtraditional <1>: Preprocessor Options. (line 118) ! * Wtraditional: Warning Options. (line 1137) ! * Wtraditional-conversion: Warning Options. (line 1215) ! * Wtrampolines: Warning Options. (line 1112) * Wtrigraphs <1>: Preprocessor Options. (line 106) ! * Wtrigraphs: Warning Options. (line 677) ! * Wtype-limits: Warning Options. (line 1342) * Wundeclared-selector: Objective-C and Objective-C++ Dialect Options. (line 205) * Wundef <1>: Preprocessor Options. (line 124) ! * Wundef: Warning Options. (line 1229) ! * Wuninitialized: Warning Options. (line 778) ! * Wunknown-pragmas: Warning Options. (line 861) ! * Wunsafe-loop-optimizations: Warning Options. (line 1286) ! * Wunsuffixed-float-constants: Warning Options. (line 1941) ! * Wunused: Warning Options. (line 771) ! * Wunused-but-set-parameter: Warning Options. (line 682) ! * Wunused-but-set-variable: Warning Options. (line 691) ! * Wunused-const-variable: Warning Options. (line 738) ! * Wunused-function: Warning Options. (line 701) ! * Wunused-label: Warning Options. (line 706) ! * Wunused-local-typedefs: Warning Options. (line 713) * Wunused-macros: Preprocessor Options. (line 129) ! * Wunused-parameter: Warning Options. (line 717) ! * Wunused-result: Warning Options. (line 724) ! * Wunused-value: Warning Options. (line 761) ! * Wunused-variable: Warning Options. (line 729) ! * Wuseless-cast: Warning Options. (line 1477) ! * Wvarargs: Warning Options. (line 1872) ! * Wvariadic-macros: Warning Options. (line 1866) ! * Wvector-operation-performance: Warning Options. (line 1877) * Wvirtual-inheritance: C++ Dialect Options. ! (line 714) ! * Wvirtual-move-assign: Warning Options. (line 1887) ! * Wvla: Warning Options. (line 1896) ! * Wvolatile-register-var: Warning Options. (line 1900) ! * Wwrite-strings: Warning Options. (line 1408) ! * Wzero-as-null-pointer-constant: Warning Options. (line 1451) * x <1>: Preprocessor Options. ! (line 322) ! * x: Overall Options. (line 126) * Xassembler: Assembler Options. (line 13) * Xbind-lazy: VxWorks Options. (line 26) * Xbind-now: VxWorks Options. (line 30) ! * Xlinker: Link Options. (line 251) * Xpreprocessor: Preprocessor Options. (line 25) * Ym: System V Options. (line 26) * YP: System V Options. (line 22) ! * z: Link Options. (line 282)  File: gcc.info, Node: Keyword Index, Prev: Option Index, Up: Top *************** Keyword Index *** 54299,54741 **** * #pragma interface: C++ Interface. (line 17) * $: Dollar Signs. (line 6) * % in constraint: Modifiers. (line 52) ! * %include: Spec Files. (line 26) ! * %include_noerr: Spec Files. (line 30) ! * %rename: Spec Files. (line 34) * & in constraint: Modifiers. (line 25) * ': Incompatibilities. (line 116) ! * *__builtin_alloca: Other Builtins. (line 123) ! * *__builtin_alloca_with_align: Other Builtins. (line 160) * + in constraint: Modifiers. (line 12) * -lgcc, use with -nodefaultlibs: Link Options. (line 91) * -lgcc, use with -nostdlib: Link Options. (line 91) ! * -march feature modifiers: AArch64 Options. (line 184) ! * -mcpu feature modifiers: AArch64 Options. (line 184) * -nodefaultlibs and unresolved references: Link Options. (line 91) * -nostdlib and unresolved references: Link Options. (line 91) * .sdata/.sdata2 references (PowerPC): RS/6000 and PowerPC Options. ! (line 832) * //: C++ Comments. (line 6) ! * 0 in constraint: Simple Constraints. (line 125) ! * < in constraint: Simple Constraints. (line 47) * = in constraint: Modifiers. (line 8) ! * > in constraint: Simple Constraints. (line 59) * ?: extensions: Conditionals. (line 6) * ?: side effect: Conditionals. (line 20) * _ in variables in macros: Typeof. (line 46) ! * _Accum data type: Fixed-Point. (line 6) ! * _Complex keyword: Complex. (line 6) ! * _Decimal128 data type: Decimal Float. (line 6) ! * _Decimal32 data type: Decimal Float. (line 6) ! * _Decimal64 data type: Decimal Float. (line 6) ! * _Exit: Other Builtins. (line 6) ! * _exit: Other Builtins. (line 6) ! * _Fract data type: Fixed-Point. (line 6) ! * _HTM_FIRST_USER_ABORT_CODE: S/390 System z Built-in Functions. ! (line 44) ! * _Sat data type: Fixed-Point. (line 6) ! * _xabort: x86 transactional memory intrinsics. ! (line 57) ! * _xbegin: x86 transactional memory intrinsics. ! (line 19) ! * _xend: x86 transactional memory intrinsics. ! (line 48) ! * _xtest: x86 transactional memory intrinsics. ! (line 53) ! * __atomic_add_fetch: __atomic Builtins. (line 179) ! * __atomic_always_lock_free: __atomic Builtins. (line 265) ! * __atomic_and_fetch: __atomic Builtins. (line 183) ! * __atomic_clear: __atomic Builtins. (line 239) ! * __atomic_compare_exchange: __atomic Builtins. (line 171) ! * __atomic_compare_exchange_n: __atomic Builtins. (line 147) ! * __atomic_exchange: __atomic Builtins. (line 141) ! * __atomic_exchange_n: __atomic Builtins. (line 131) ! * __atomic_fetch_add: __atomic Builtins. (line 203) ! * __atomic_fetch_and: __atomic Builtins. (line 207) ! * __atomic_fetch_nand: __atomic Builtins. (line 213) ! * __atomic_fetch_or: __atomic Builtins. (line 211) ! * __atomic_fetch_sub: __atomic Builtins. (line 205) ! * __atomic_fetch_xor: __atomic Builtins. (line 209) ! * __atomic_is_lock_free: __atomic Builtins. (line 279) ! * __atomic_load: __atomic Builtins. (line 113) ! * __atomic_load_n: __atomic Builtins. (line 106) ! * __atomic_nand_fetch: __atomic Builtins. (line 189) ! * __atomic_or_fetch: __atomic Builtins. (line 187) ! * __atomic_signal_fence: __atomic Builtins. (line 258) ! * __atomic_store: __atomic Builtins. (line 126) ! * __atomic_store_n: __atomic Builtins. (line 118) ! * __atomic_sub_fetch: __atomic Builtins. (line 181) ! * __atomic_test_and_set: __atomic Builtins. (line 227) ! * __atomic_thread_fence: __atomic Builtins. (line 251) ! * __atomic_xor_fetch: __atomic Builtins. (line 185) * __builtin_add_overflow: Integer Overflow Builtins. ! (line 9) * __builtin_alloca: Other Builtins. (line 6) * __builtin_alloca_with_align: Other Builtins. (line 6) ! * __builtin_apply: Constructing Calls. (line 29) ! * __builtin_apply_args: Constructing Calls. (line 19) * __builtin_arc_aligned: ARC Built-in Functions. ! (line 18) * __builtin_arc_brk: ARC Built-in Functions. ! (line 28) * __builtin_arc_core_read: ARC Built-in Functions. ! (line 32) * __builtin_arc_core_write: ARC Built-in Functions. ! (line 39) * __builtin_arc_divaw: ARC Built-in Functions. ! (line 46) * __builtin_arc_flag: ARC Built-in Functions. ! (line 53) * __builtin_arc_lr: ARC Built-in Functions. ! (line 57) * __builtin_arc_mul64: ARC Built-in Functions. ! (line 64) * __builtin_arc_mulu64: ARC Built-in Functions. ! (line 68) * __builtin_arc_nop: ARC Built-in Functions. ! (line 73) * __builtin_arc_norm: ARC Built-in Functions. ! (line 77) * __builtin_arc_normw: ARC Built-in Functions. ! (line 84) * __builtin_arc_rtie: ARC Built-in Functions. ! (line 91) * __builtin_arc_sleep: ARC Built-in Functions. ! (line 95) * __builtin_arc_sr: ARC Built-in Functions. ! (line 99) * __builtin_arc_swap: ARC Built-in Functions. ! (line 106) * __builtin_arc_swi: ARC Built-in Functions. ! (line 112) * __builtin_arc_sync: ARC Built-in Functions. ! (line 116) * __builtin_arc_trap_s: ARC Built-in Functions. ! (line 120) * __builtin_arc_unimp_s: ARC Built-in Functions. ! (line 124) ! * __builtin_assume_aligned: Other Builtins. (line 435) ! * __builtin_bswap16: Other Builtins. (line 702) ! * __builtin_bswap32: Other Builtins. (line 706) ! * __builtin_bswap64: Other Builtins. (line 710) * __builtin_call_with_static_chain: Other Builtins. (line 6) ! * __builtin_call_with_static_chain <1>: Other Builtins. (line 250) ! * __builtin_choose_expr: Other Builtins. (line 261) ! * __builtin_clrsb: Other Builtins. (line 632) ! * __builtin_clrsbl: Other Builtins. (line 654) ! * __builtin_clrsbll: Other Builtins. (line 677) ! * __builtin_clz: Other Builtins. (line 624) ! * __builtin_clzl: Other Builtins. (line 646) ! * __builtin_clzll: Other Builtins. (line 669) ! * __builtin_complex: Other Builtins. (line 301) ! * __builtin_constant_p: Other Builtins. (line 310) ! * __builtin_cpu_init: PowerPC Built-in Functions. ! (line 9) * __builtin_cpu_init <1>: x86 Built-in Functions. ! (line 62) ! * __builtin_cpu_is: PowerPC Built-in Functions. ! (line 13) * __builtin_cpu_is <1>: x86 Built-in Functions. ! (line 90) ! * __builtin_cpu_supports: PowerPC Built-in Functions. ! (line 59) * __builtin_cpu_supports <1>: x86 Built-in Functions. ! (line 165) ! * __builtin_ctz: Other Builtins. (line 628) ! * __builtin_ctzl: Other Builtins. (line 650) ! * __builtin_ctzll: Other Builtins. (line 673) ! * __builtin_expect: Other Builtins. (line 355) ! * __builtin_extract_return_addr: Return Address. (line 38) ! * __builtin_ffs: Other Builtins. (line 620) ! * __builtin_ffsl: Other Builtins. (line 643) ! * __builtin_ffsll: Other Builtins. (line 665) ! * __builtin_FILE: Other Builtins. (line 464) * __builtin_fpclassify: Other Builtins. (line 6) ! * __builtin_fpclassify <1>: Other Builtins. (line 534) ! * __builtin_frame_address: Return Address. (line 50) ! * __builtin_frob_return_address: Return Address. (line 47) ! * __builtin_FUNCTION: Other Builtins. (line 459) ! * __builtin_huge_val: Other Builtins. (line 522) ! * __builtin_huge_valf: Other Builtins. (line 527) ! * __builtin_huge_vall: Other Builtins. (line 530) ! * __builtin_huge_valq: PowerPC Built-in Functions. ! (line 199) * __builtin_huge_valq <1>: x86 Built-in Functions. (line 57) ! * __builtin_inf: Other Builtins. (line 545) ! * __builtin_infd128: Other Builtins. (line 555) ! * __builtin_infd32: Other Builtins. (line 549) ! * __builtin_infd64: Other Builtins. (line 552) ! * __builtin_inff: Other Builtins. (line 559) ! * __builtin_infl: Other Builtins. (line 564) ! * __builtin_infq: PowerPC Built-in Functions. ! (line 196) * __builtin_infq <1>: x86 Built-in Functions. ! (line 54) * __builtin_isfinite: Other Builtins. (line 6) * __builtin_isgreater: Other Builtins. (line 6) * __builtin_isgreaterequal: Other Builtins. (line 6) * __builtin_isinf_sign: Other Builtins. (line 6) - * __builtin_isinf_sign <1>: Other Builtins. (line 568) * __builtin_isless: Other Builtins. (line 6) * __builtin_islessequal: Other Builtins. (line 6) * __builtin_islessgreater: Other Builtins. (line 6) * __builtin_isnormal: Other Builtins. (line 6) * __builtin_isunordered: Other Builtins. (line 6) ! * __builtin_LINE: Other Builtins. (line 453) * __builtin_mul_overflow: Integer Overflow Builtins. ! (line 62) ! * __builtin_nan: Other Builtins. (line 576) ! * __builtin_nand128: Other Builtins. (line 598) ! * __builtin_nand32: Other Builtins. (line 592) ! * __builtin_nand64: Other Builtins. (line 595) ! * __builtin_nanf: Other Builtins. (line 602) ! * __builtin_nanl: Other Builtins. (line 605) * __builtin_nanq: PowerPC Built-in Functions. ! (line 203) ! * __builtin_nans: Other Builtins. (line 609) ! * __builtin_nansf: Other Builtins. (line 613) ! * __builtin_nansl: Other Builtins. (line 616) * __builtin_nansq: PowerPC Built-in Functions. ! (line 206) * __builtin_nds32_isb: NDS32 Built-in Functions. ! (line 12) * __builtin_nds32_isync: NDS32 Built-in Functions. ! (line 8) * __builtin_nds32_mfsr: NDS32 Built-in Functions. ! (line 15) * __builtin_nds32_mfusr: NDS32 Built-in Functions. ! (line 18) * __builtin_nds32_mtsr: NDS32 Built-in Functions. ! (line 21) * __builtin_nds32_mtusr: NDS32 Built-in Functions. ! (line 24) * __builtin_nds32_setgie_dis: NDS32 Built-in Functions. ! (line 30) * __builtin_nds32_setgie_en: NDS32 Built-in Functions. ! (line 27) * __builtin_non_tx_store: S/390 System z Built-in Functions. ! (line 98) * __builtin_object_size: Object Size Checking. (line 6) - * __builtin_object_size <1>: Object Size Checking. - (line 9) * __builtin_offsetof: Offsetof. (line 6) ! * __builtin_parity: Other Builtins. (line 640) ! * __builtin_parityl: Other Builtins. (line 661) ! * __builtin_parityll: Other Builtins. (line 685) ! * __builtin_popcount: Other Builtins. (line 637) ! * __builtin_popcountl: Other Builtins. (line 657) ! * __builtin_popcountll: Other Builtins. (line 681) * __builtin_powi: Other Builtins. (line 6) - * __builtin_powi <1>: Other Builtins. (line 689) * __builtin_powif: Other Builtins. (line 6) - * __builtin_powif <1>: Other Builtins. (line 694) * __builtin_powil: Other Builtins. (line 6) ! * __builtin_powil <1>: Other Builtins. (line 698) ! * __builtin_prefetch: Other Builtins. (line 483) ! * __builtin_return: Constructing Calls. (line 47) ! * __builtin_return_address: Return Address. (line 9) * __builtin_rx_brk: RX Built-in Functions. ! (line 10) * __builtin_rx_clrpsw: RX Built-in Functions. ! (line 13) * __builtin_rx_int: RX Built-in Functions. ! (line 17) * __builtin_rx_machi: RX Built-in Functions. ! (line 21) * __builtin_rx_maclo: RX Built-in Functions. ! (line 26) * __builtin_rx_mulhi: RX Built-in Functions. ! (line 31) * __builtin_rx_mullo: RX Built-in Functions. ! (line 36) * __builtin_rx_mvfachi: RX Built-in Functions. ! (line 41) * __builtin_rx_mvfacmi: RX Built-in Functions. ! (line 45) * __builtin_rx_mvfc: RX Built-in Functions. ! (line 49) * __builtin_rx_mvtachi: RX Built-in Functions. ! (line 53) * __builtin_rx_mvtaclo: RX Built-in Functions. ! (line 57) * __builtin_rx_mvtc: RX Built-in Functions. ! (line 61) * __builtin_rx_mvtipl: RX Built-in Functions. ! (line 65) * __builtin_rx_racw: RX Built-in Functions. ! (line 69) * __builtin_rx_revw: RX Built-in Functions. ! (line 73) * __builtin_rx_rmpa: RX Built-in Functions. ! (line 78) * __builtin_rx_round: RX Built-in Functions. ! (line 82) * __builtin_rx_sat: RX Built-in Functions. ! (line 87) * __builtin_rx_setpsw: RX Built-in Functions. ! (line 91) * __builtin_rx_wait: RX Built-in Functions. ! (line 95) ! * __builtin_saddll_overflow: Integer Overflow Builtins. ! (line 15) ! * __builtin_saddl_overflow: Integer Overflow Builtins. ! (line 13) * __builtin_sadd_overflow: Integer Overflow Builtins. ! (line 11) * __builtin_set_thread_pointer: SH Built-in Functions. ! (line 9) * __builtin_sh_get_fpscr: SH Built-in Functions. ! (line 35) * __builtin_sh_set_fpscr: SH Built-in Functions. ! (line 38) ! * __builtin_smulll_overflow: Integer Overflow Builtins. ! (line 68) ! * __builtin_smull_overflow: Integer Overflow Builtins. ! (line 66) * __builtin_smul_overflow: Integer Overflow Builtins. ! (line 64) ! * __builtin_ssubll_overflow: Integer Overflow Builtins. ! (line 48) ! * __builtin_ssubl_overflow: Integer Overflow Builtins. ! (line 46) * __builtin_ssub_overflow: Integer Overflow Builtins. ! (line 44) * __builtin_sub_overflow: Integer Overflow Builtins. ! (line 42) * __builtin_tabort: S/390 System z Built-in Functions. ! (line 82) * __builtin_tbegin: S/390 System z Built-in Functions. ! (line 6) ! * __builtin_tbeginc: S/390 System z Built-in Functions. ! (line 73) * __builtin_tbegin_nofloat: S/390 System z Built-in Functions. ! (line 54) * __builtin_tbegin_retry: S/390 System z Built-in Functions. ! (line 60) * __builtin_tbegin_retry_nofloat: S/390 System z Built-in Functions. ! (line 67) * __builtin_tend: S/390 System z Built-in Functions. ! (line 77) * __builtin_thread_pointer: SH Built-in Functions. ! (line 18) ! * __builtin_trap: Other Builtins. (line 379) * __builtin_tx_assist: S/390 System z Built-in Functions. ! (line 87) * __builtin_tx_nesting_depth: S/390 System z Built-in Functions. ! (line 93) ! * __builtin_types_compatible_p: Other Builtins. (line 205) ! * __builtin_uaddll_overflow: Integer Overflow Builtins. ! (line 21) ! * __builtin_uaddl_overflow: Integer Overflow Builtins. ! (line 19) * __builtin_uadd_overflow: Integer Overflow Builtins. ! (line 17) ! * __builtin_umulll_overflow: Integer Overflow Builtins. ! (line 74) ! * __builtin_umull_overflow: Integer Overflow Builtins. ! (line 72) * __builtin_umul_overflow: Integer Overflow Builtins. ! (line 70) ! * __builtin_unreachable: Other Builtins. (line 386) ! * __builtin_usubll_overflow: Integer Overflow Builtins. ! (line 54) ! * __builtin_usubl_overflow: Integer Overflow Builtins. ! (line 52) ! * __builtin_usub_overflow: Integer Overflow Builtins. ! (line 50) ! * __builtin_va_arg_pack: Constructing Calls. (line 52) ! * __builtin_va_arg_pack_len: Constructing Calls. (line 75) ! * __builtin___bnd_chk_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_chk_ptr_bounds <1>: Pointer Bounds Checker builtins. ! (line 110) ! * __builtin___bnd_chk_ptr_lbounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_chk_ptr_lbounds <1>: Pointer Bounds Checker builtins. ! (line 85) ! * __builtin___bnd_chk_ptr_ubounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_chk_ptr_ubounds <1>: Pointer Bounds Checker builtins. ! (line 103) ! * __builtin___bnd_copy_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_copy_ptr_bounds <1>: Pointer Bounds Checker builtins. ! (line 46) ! * __builtin___bnd_get_ptr_lbound: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_get_ptr_lbound <1>: Pointer Bounds Checker builtins. ! (line 128) ! * __builtin___bnd_get_ptr_ubound: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_get_ptr_ubound <1>: Pointer Bounds Checker builtins. ! (line 140) ! * __builtin___bnd_init_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_init_ptr_bounds <1>: Pointer Bounds Checker builtins. ! (line 59) ! * __builtin___bnd_narrow_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_narrow_ptr_bounds <1>: Pointer Bounds Checker builtins. ! (line 27) ! * __builtin___bnd_null_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_null_ptr_bounds <1>: Pointer Bounds Checker builtins. ! (line 67) ! * __builtin___bnd_set_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_set_ptr_bounds <1>: Pointer Bounds Checker builtins. ! (line 12) ! * __builtin___bnd_store_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_store_ptr_bounds <1>: Pointer Bounds Checker builtins. (line 75) ! * __builtin___clear_cache: Other Builtins. (line 470) ! * __builtin___fprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___memcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___memmove_chk: Object Size Checking. ! (line 6) ! * __builtin___mempcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___memset_chk: Object Size Checking. ! (line 6) ! * __builtin___printf_chk: Object Size Checking. ! (line 6) ! * __builtin___snprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___sprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___stpcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___strcat_chk: Object Size Checking. ! (line 6) ! * __builtin___strcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___strncat_chk: Object Size Checking. ! (line 6) ! * __builtin___strncpy_chk: Object Size Checking. ! (line 6) ! * __builtin___vfprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___vprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___vsnprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___vsprintf_chk: Object Size Checking. ! (line 6) * __complex__ keyword: Complex. (line 6) * __declspec(dllexport): Microsoft Windows Function Attributes. (line 10) * __declspec(dllimport): Microsoft Windows Function Attributes. ! (line 42) * __ea SPU Named Address Spaces: Named Address Spaces. (line 155) * __extension__: Alternate Keywords. (line 30) * __far M32C Named Address Spaces: Named Address Spaces. ! (line 138) * __far RL78 Named Address Spaces: Named Address Spaces. (line 147) * __flash AVR Named Address Spaces: Named Address Spaces. --- 54861,55254 ---- * #pragma interface: C++ Interface. (line 17) * $: Dollar Signs. (line 6) * % in constraint: Modifiers. (line 52) ! * %include: Spec Files. (line 27) ! * %include_noerr: Spec Files. (line 31) ! * %rename: Spec Files. (line 35) * & in constraint: Modifiers. (line 25) * ': Incompatibilities. (line 116) ! * *__builtin_alloca: Other Builtins. (line 124) ! * *__builtin_alloca_with_align: Other Builtins. (line 163) * + in constraint: Modifiers. (line 12) * -lgcc, use with -nodefaultlibs: Link Options. (line 91) * -lgcc, use with -nostdlib: Link Options. (line 91) ! * -march feature modifiers: AArch64 Options. (line 186) ! * -mcpu feature modifiers: AArch64 Options. (line 186) * -nodefaultlibs and unresolved references: Link Options. (line 91) * -nostdlib and unresolved references: Link Options. (line 91) * .sdata/.sdata2 references (PowerPC): RS/6000 and PowerPC Options. ! (line 809) * //: C++ Comments. (line 6) ! * 0 in constraint: Simple Constraints. (line 127) ! * < in constraint: Simple Constraints. (line 48) * = in constraint: Modifiers. (line 8) ! * > in constraint: Simple Constraints. (line 61) * ?: extensions: Conditionals. (line 6) * ?: side effect: Conditionals. (line 20) * _ in variables in macros: Typeof. (line 46) ! * __atomic_add_fetch: __atomic Builtins. (line 194) ! * __atomic_always_lock_free: __atomic Builtins. (line 281) ! * __atomic_and_fetch: __atomic Builtins. (line 198) ! * __atomic_clear: __atomic Builtins. (line 255) ! * __atomic_compare_exchange: __atomic Builtins. (line 186) ! * __atomic_compare_exchange_n: __atomic Builtins. (line 161) ! * __atomic_exchange: __atomic Builtins. (line 153) ! * __atomic_exchange_n: __atomic Builtins. (line 142) ! * __atomic_fetch_add: __atomic Builtins. (line 219) ! * __atomic_fetch_and: __atomic Builtins. (line 223) ! * __atomic_fetch_nand: __atomic Builtins. (line 229) ! * __atomic_fetch_or: __atomic Builtins. (line 227) ! * __atomic_fetch_sub: __atomic Builtins. (line 221) ! * __atomic_fetch_xor: __atomic Builtins. (line 225) ! * __atomic_is_lock_free: __atomic Builtins. (line 295) ! * __atomic_load: __atomic Builtins. (line 121) ! * __atomic_load_n: __atomic Builtins. (line 112) ! * __atomic_nand_fetch: __atomic Builtins. (line 204) ! * __atomic_or_fetch: __atomic Builtins. (line 202) ! * __atomic_signal_fence: __atomic Builtins. (line 273) ! * __atomic_store: __atomic Builtins. (line 136) ! * __atomic_store_n: __atomic Builtins. (line 127) ! * __atomic_sub_fetch: __atomic Builtins. (line 196) ! * __atomic_test_and_set: __atomic Builtins. (line 244) ! * __atomic_thread_fence: __atomic Builtins. (line 266) ! * __atomic_xor_fetch: __atomic Builtins. (line 200) ! * __builtin___bnd_chk_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_chk_ptr_lbounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_chk_ptr_ubounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_copy_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_get_ptr_lbound: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_get_ptr_ubound: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_init_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_narrow_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_null_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_set_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___bnd_store_ptr_bounds: Pointer Bounds Checker builtins. ! (line 6) ! * __builtin___clear_cache: Other Builtins. (line 479) ! * __builtin___fprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___memcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___memmove_chk: Object Size Checking. ! (line 6) ! * __builtin___mempcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___memset_chk: Object Size Checking. ! (line 6) ! * __builtin___printf_chk: Object Size Checking. ! (line 6) ! * __builtin___snprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___sprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___stpcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___strcat_chk: Object Size Checking. ! (line 6) ! * __builtin___strcpy_chk: Object Size Checking. ! (line 6) ! * __builtin___strncat_chk: Object Size Checking. ! (line 6) ! * __builtin___strncpy_chk: Object Size Checking. ! (line 6) ! * __builtin___vfprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___vprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___vsnprintf_chk: Object Size Checking. ! (line 6) ! * __builtin___vsprintf_chk: Object Size Checking. ! (line 6) * __builtin_add_overflow: Integer Overflow Builtins. ! (line 11) * __builtin_alloca: Other Builtins. (line 6) * __builtin_alloca_with_align: Other Builtins. (line 6) ! * __builtin_apply: Constructing Calls. (line 31) ! * __builtin_apply_args: Constructing Calls. (line 20) * __builtin_arc_aligned: ARC Built-in Functions. ! (line 20) * __builtin_arc_brk: ARC Built-in Functions. ! (line 29) * __builtin_arc_core_read: ARC Built-in Functions. ! (line 34) * __builtin_arc_core_write: ARC Built-in Functions. ! (line 41) * __builtin_arc_divaw: ARC Built-in Functions. ! (line 47) * __builtin_arc_flag: ARC Built-in Functions. ! (line 54) * __builtin_arc_lr: ARC Built-in Functions. ! (line 58) * __builtin_arc_mul64: ARC Built-in Functions. ! (line 65) * __builtin_arc_mulu64: ARC Built-in Functions. ! (line 70) * __builtin_arc_nop: ARC Built-in Functions. ! (line 74) * __builtin_arc_norm: ARC Built-in Functions. ! (line 78) * __builtin_arc_normw: ARC Built-in Functions. ! (line 85) * __builtin_arc_rtie: ARC Built-in Functions. ! (line 92) * __builtin_arc_sleep: ARC Built-in Functions. ! (line 96) * __builtin_arc_sr: ARC Built-in Functions. ! (line 101) * __builtin_arc_swap: ARC Built-in Functions. ! (line 107) * __builtin_arc_swi: ARC Built-in Functions. ! (line 113) * __builtin_arc_sync: ARC Built-in Functions. ! (line 117) * __builtin_arc_trap_s: ARC Built-in Functions. ! (line 121) * __builtin_arc_unimp_s: ARC Built-in Functions. ! (line 125) ! * __builtin_assume_aligned: Other Builtins. (line 444) ! * __builtin_bswap16: Other Builtins. (line 710) ! * __builtin_bswap32: Other Builtins. (line 714) ! * __builtin_bswap64: Other Builtins. (line 718) * __builtin_call_with_static_chain: Other Builtins. (line 6) ! * __builtin_choose_expr: Other Builtins. (line 266) ! * __builtin_clrsb: Other Builtins. (line 640) ! * __builtin_clrsbl: Other Builtins. (line 662) ! * __builtin_clrsbll: Other Builtins. (line 685) ! * __builtin_clz: Other Builtins. (line 632) ! * __builtin_clzl: Other Builtins. (line 654) ! * __builtin_clzll: Other Builtins. (line 677) ! * __builtin_complex: Other Builtins. (line 306) ! * __builtin_constant_p: Other Builtins. (line 316) * __builtin_cpu_init <1>: x86 Built-in Functions. ! (line 63) ! * __builtin_cpu_init: PowerPC Built-in Functions. ! (line 10) * __builtin_cpu_is <1>: x86 Built-in Functions. ! (line 92) ! * __builtin_cpu_is: PowerPC Built-in Functions. ! (line 14) * __builtin_cpu_supports <1>: x86 Built-in Functions. ! (line 167) ! * __builtin_cpu_supports: PowerPC Built-in Functions. ! (line 74) ! * __builtin_ctz: Other Builtins. (line 636) ! * __builtin_ctzl: Other Builtins. (line 658) ! * __builtin_ctzll: Other Builtins. (line 681) ! * __builtin_expect: Other Builtins. (line 362) ! * __builtin_extract_return_addr: Return Address. (line 39) ! * __builtin_ffs: Other Builtins. (line 628) ! * __builtin_ffsl: Other Builtins. (line 651) ! * __builtin_ffsll: Other Builtins. (line 673) ! * __builtin_FILE: Other Builtins. (line 472) * __builtin_fpclassify: Other Builtins. (line 6) ! * __builtin_frame_address: Return Address. (line 52) ! * __builtin_frob_return_address: Return Address. (line 48) ! * __builtin_FUNCTION: Other Builtins. (line 467) ! * __builtin_huge_val: Other Builtins. (line 530) ! * __builtin_huge_valf: Other Builtins. (line 535) ! * __builtin_huge_vall: Other Builtins. (line 538) * __builtin_huge_valq <1>: x86 Built-in Functions. (line 57) ! * __builtin_huge_valq: PowerPC Built-in Functions. ! (line 250) ! * __builtin_inf: Other Builtins. (line 553) ! * __builtin_infd128: Other Builtins. (line 563) ! * __builtin_infd32: Other Builtins. (line 557) ! * __builtin_infd64: Other Builtins. (line 560) ! * __builtin_inff: Other Builtins. (line 567) ! * __builtin_infl: Other Builtins. (line 572) * __builtin_infq <1>: x86 Built-in Functions. ! (line 53) ! * __builtin_infq: PowerPC Built-in Functions. ! (line 246) * __builtin_isfinite: Other Builtins. (line 6) * __builtin_isgreater: Other Builtins. (line 6) * __builtin_isgreaterequal: Other Builtins. (line 6) * __builtin_isinf_sign: Other Builtins. (line 6) * __builtin_isless: Other Builtins. (line 6) * __builtin_islessequal: Other Builtins. (line 6) * __builtin_islessgreater: Other Builtins. (line 6) * __builtin_isnormal: Other Builtins. (line 6) * __builtin_isunordered: Other Builtins. (line 6) ! * __builtin_LINE: Other Builtins. (line 461) * __builtin_mul_overflow: Integer Overflow Builtins. ! (line 65) ! * __builtin_nan: Other Builtins. (line 584) ! * __builtin_nand128: Other Builtins. (line 606) ! * __builtin_nand32: Other Builtins. (line 600) ! * __builtin_nand64: Other Builtins. (line 603) ! * __builtin_nanf: Other Builtins. (line 610) ! * __builtin_nanl: Other Builtins. (line 613) * __builtin_nanq: PowerPC Built-in Functions. ! (line 253) ! * __builtin_nans: Other Builtins. (line 617) ! * __builtin_nansf: Other Builtins. (line 621) ! * __builtin_nansl: Other Builtins. (line 624) * __builtin_nansq: PowerPC Built-in Functions. ! (line 257) * __builtin_nds32_isb: NDS32 Built-in Functions. ! (line 13) * __builtin_nds32_isync: NDS32 Built-in Functions. ! (line 9) * __builtin_nds32_mfsr: NDS32 Built-in Functions. ! (line 16) * __builtin_nds32_mfusr: NDS32 Built-in Functions. ! (line 19) * __builtin_nds32_mtsr: NDS32 Built-in Functions. ! (line 22) * __builtin_nds32_mtusr: NDS32 Built-in Functions. ! (line 25) * __builtin_nds32_setgie_dis: NDS32 Built-in Functions. ! (line 31) * __builtin_nds32_setgie_en: NDS32 Built-in Functions. ! (line 28) * __builtin_non_tx_store: S/390 System z Built-in Functions. ! (line 104) * __builtin_object_size: Object Size Checking. (line 6) * __builtin_offsetof: Offsetof. (line 6) ! * __builtin_parity: Other Builtins. (line 648) ! * __builtin_parityl: Other Builtins. (line 669) ! * __builtin_parityll: Other Builtins. (line 693) ! * __builtin_popcount: Other Builtins. (line 645) ! * __builtin_popcountl: Other Builtins. (line 665) ! * __builtin_popcountll: Other Builtins. (line 689) * __builtin_powi: Other Builtins. (line 6) * __builtin_powif: Other Builtins. (line 6) * __builtin_powil: Other Builtins. (line 6) ! * __builtin_prefetch: Other Builtins. (line 491) ! * __builtin_return: Constructing Calls. (line 48) ! * __builtin_return_address: Return Address. (line 11) * __builtin_rx_brk: RX Built-in Functions. ! (line 11) * __builtin_rx_clrpsw: RX Built-in Functions. ! (line 14) * __builtin_rx_int: RX Built-in Functions. ! (line 18) * __builtin_rx_machi: RX Built-in Functions. ! (line 22) * __builtin_rx_maclo: RX Built-in Functions. ! (line 27) * __builtin_rx_mulhi: RX Built-in Functions. ! (line 32) * __builtin_rx_mullo: RX Built-in Functions. ! (line 37) * __builtin_rx_mvfachi: RX Built-in Functions. ! (line 42) * __builtin_rx_mvfacmi: RX Built-in Functions. ! (line 46) * __builtin_rx_mvfc: RX Built-in Functions. ! (line 50) * __builtin_rx_mvtachi: RX Built-in Functions. ! (line 54) * __builtin_rx_mvtaclo: RX Built-in Functions. ! (line 58) * __builtin_rx_mvtc: RX Built-in Functions. ! (line 62) * __builtin_rx_mvtipl: RX Built-in Functions. ! (line 66) * __builtin_rx_racw: RX Built-in Functions. ! (line 70) * __builtin_rx_revw: RX Built-in Functions. ! (line 74) * __builtin_rx_rmpa: RX Built-in Functions. ! (line 79) * __builtin_rx_round: RX Built-in Functions. ! (line 83) * __builtin_rx_sat: RX Built-in Functions. ! (line 88) * __builtin_rx_setpsw: RX Built-in Functions. ! (line 92) * __builtin_rx_wait: RX Built-in Functions. ! (line 96) * __builtin_sadd_overflow: Integer Overflow Builtins. ! (line 13) ! * __builtin_saddl_overflow: Integer Overflow Builtins. ! (line 15) ! * __builtin_saddll_overflow: Integer Overflow Builtins. ! (line 17) * __builtin_set_thread_pointer: SH Built-in Functions. ! (line 10) * __builtin_sh_get_fpscr: SH Built-in Functions. ! (line 36) * __builtin_sh_set_fpscr: SH Built-in Functions. ! (line 39) * __builtin_smul_overflow: Integer Overflow Builtins. ! (line 67) ! * __builtin_smull_overflow: Integer Overflow Builtins. ! (line 69) ! * __builtin_smulll_overflow: Integer Overflow Builtins. ! (line 71) * __builtin_ssub_overflow: Integer Overflow Builtins. ! (line 46) ! * __builtin_ssubl_overflow: Integer Overflow Builtins. ! (line 48) ! * __builtin_ssubll_overflow: Integer Overflow Builtins. ! (line 50) * __builtin_sub_overflow: Integer Overflow Builtins. ! (line 44) * __builtin_tabort: S/390 System z Built-in Functions. ! (line 87) * __builtin_tbegin: S/390 System z Built-in Functions. ! (line 7) * __builtin_tbegin_nofloat: S/390 System z Built-in Functions. ! (line 59) * __builtin_tbegin_retry: S/390 System z Built-in Functions. ! (line 65) * __builtin_tbegin_retry_nofloat: S/390 System z Built-in Functions. ! (line 72) ! * __builtin_tbeginc: S/390 System z Built-in Functions. ! (line 78) * __builtin_tend: S/390 System z Built-in Functions. ! (line 82) * __builtin_thread_pointer: SH Built-in Functions. ! (line 20) ! * __builtin_trap: Other Builtins. (line 386) * __builtin_tx_assist: S/390 System z Built-in Functions. ! (line 92) * __builtin_tx_nesting_depth: S/390 System z Built-in Functions. ! (line 98) ! * __builtin_types_compatible_p: Other Builtins. (line 209) * __builtin_uadd_overflow: Integer Overflow Builtins. ! (line 19) ! * __builtin_uaddl_overflow: Integer Overflow Builtins. ! (line 21) ! * __builtin_uaddll_overflow: Integer Overflow Builtins. ! (line 24) * __builtin_umul_overflow: Integer Overflow Builtins. ! (line 73) ! * __builtin_umull_overflow: Integer Overflow Builtins. (line 75) ! * __builtin_umulll_overflow: Integer Overflow Builtins. ! (line 78) ! * __builtin_unreachable: Other Builtins. (line 393) ! * __builtin_usub_overflow: Integer Overflow Builtins. ! (line 52) ! * __builtin_usubl_overflow: Integer Overflow Builtins. ! (line 54) ! * __builtin_usubll_overflow: Integer Overflow Builtins. ! (line 57) ! * __builtin_va_arg_pack: Constructing Calls. (line 53) ! * __builtin_va_arg_pack_len: Constructing Calls. (line 76) * __complex__ keyword: Complex. (line 6) * __declspec(dllexport): Microsoft Windows Function Attributes. (line 10) * __declspec(dllimport): Microsoft Windows Function Attributes. ! (line 44) * __ea SPU Named Address Spaces: Named Address Spaces. (line 155) * __extension__: Alternate Keywords. (line 30) * __far M32C Named Address Spaces: Named Address Spaces. ! (line 139) * __far RL78 Named Address Spaces: Named Address Spaces. (line 147) * __flash AVR Named Address Spaces: Named Address Spaces. *************** Keyword Index *** 54753,54760 **** * __float128 data type: Floating Types. (line 6) * __float80 data type: Floating Types. (line 6) * __fp16 data type: Half-Precision. (line 6) - * __FUNCTION__ identifier: Function Names. (line 6) * __func__ identifier: Function Names. (line 6) * __ibm128 data type: Floating Types. (line 6) * __imag__ keyword: Complex. (line 27) * __int128 data types: __int128. (line 6) --- 55266,55273 ---- * __float128 data type: Floating Types. (line 6) * __float80 data type: Floating Types. (line 6) * __fp16 data type: Half-Precision. (line 6) * __func__ identifier: Function Names. (line 6) + * __FUNCTION__ identifier: Function Names. (line 6) * __ibm128 data type: Floating Types. (line 6) * __imag__ keyword: Complex. (line 27) * __int128 data types: __int128. (line 6) *************** Keyword Index *** 54785,54790 **** --- 55298,55322 ---- * __sync_val_compare_and_swap: __sync Builtins. (line 88) * __sync_xor_and_fetch: __sync Builtins. (line 72) * __thread: Thread-Local. (line 6) + * _Accum data type: Fixed-Point. (line 6) + * _Complex keyword: Complex. (line 6) + * _Decimal128 data type: Decimal Float. (line 6) + * _Decimal32 data type: Decimal Float. (line 6) + * _Decimal64 data type: Decimal Float. (line 6) + * _exit: Other Builtins. (line 6) + * _Exit: Other Builtins. (line 6) + * _Fract data type: Fixed-Point. (line 6) + * _HTM_FIRST_USER_ABORT_CODE: S/390 System z Built-in Functions. + (line 48) + * _Sat data type: Fixed-Point. (line 6) + * _xabort: x86 transactional memory intrinsics. + (line 64) + * _xbegin: x86 transactional memory intrinsics. + (line 20) + * _xend: x86 transactional memory intrinsics. + (line 55) + * _xtest: x86 transactional memory intrinsics. + (line 60) * AArch64 Options: AArch64 Options. (line 6) * ABI: Compatibility. (line 6) * abi_tag function attribute: C++ Attributes. (line 9) *************** Keyword Index *** 54792,54799 **** * abi_tag variable attribute: C++ Attributes. (line 9) * abort: Other Builtins. (line 6) * abs: Other Builtins. (line 6) - * accessing volatiles: Volatiles. (line 6) * accessing volatiles <1>: C++ Volatiles. (line 6) * acos: Other Builtins. (line 6) * acosf: Other Builtins. (line 6) * acosh: Other Builtins. (line 6) --- 55324,55331 ---- * abi_tag variable attribute: C++ Attributes. (line 9) * abort: Other Builtins. (line 6) * abs: Other Builtins. (line 6) * accessing volatiles <1>: C++ Volatiles. (line 6) + * accessing volatiles: Volatiles. (line 6) * acos: Other Builtins. (line 6) * acosf: Other Builtins. (line 6) * acosh: Other Builtins. (line 6) *************** Keyword Index *** 54801,54813 **** * acoshl: Other Builtins. (line 6) * acosl: Other Builtins. (line 6) * Ada: G++ and GCC. (line 6) - * Ada <1>: G++ and GCC. (line 30) * additional floating types: Floating Types. (line 6) ! * address constraints: Simple Constraints. (line 152) * address of a label: Labels as Values. (line 6) * address variable attribute, AVR: AVR Variable Attributes. (line 63) ! * address_operand: Simple Constraints. (line 156) * alias function attribute: Common Function Attributes. (line 9) * aligned function attribute: Common Function Attributes. --- 55333,55344 ---- * acoshl: Other Builtins. (line 6) * acosl: Other Builtins. (line 6) * Ada: G++ and GCC. (line 6) * additional floating types: Floating Types. (line 6) ! * address constraints: Simple Constraints. (line 154) * address of a label: Labels as Values. (line 6) * address variable attribute, AVR: AVR Variable Attributes. (line 63) ! * address_operand: Simple Constraints. (line 158) * alias function attribute: Common Function Attributes. (line 9) * aligned function attribute: Common Function Attributes. *************** Keyword Index *** 54817,54828 **** * aligned variable attribute: Common Variable Attributes. (line 8) * alignment: Alignment. (line 6) - * alloca: Other Builtins. (line 6) - * alloca vs variable-length arrays: Variable Length. (line 35) * alloc_align function attribute: Common Function Attributes. (line 43) * alloc_size function attribute: Common Function Attributes. (line 60) * Allow nesting in an interrupt handler on the Blackfin processor: Blackfin Function Attributes. (line 45) * Altera Nios II options: Nios II Options. (line 6) --- 55348,55359 ---- * aligned variable attribute: Common Variable Attributes. (line 8) * alignment: Alignment. (line 6) * alloc_align function attribute: Common Function Attributes. (line 43) * alloc_size function attribute: Common Function Attributes. (line 60) + * alloca: Other Builtins. (line 6) + * alloca vs variable-length arrays: Variable Length. (line 35) * Allow nesting in an interrupt handler on the Blackfin processor: Blackfin Function Attributes. (line 45) * Altera Nios II options: Nios II Options. (line 6) *************** Keyword Index *** 54844,54852 **** * ARC options: ARC Options. (line 6) * arch= function attribute, AArch64: AArch64 Function Attributes. (line 49) - * ARM options: ARM Options. (line 6) * ARM [Annotated C++ Reference Manual]: Backwards Compatibility. (line 6) * arrays of length zero: Zero Length. (line 6) * arrays of variable length: Variable Length. (line 6) * arrays, non-lvalue: Subscripting. (line 6) --- 55375,55383 ---- * ARC options: ARC Options. (line 6) * arch= function attribute, AArch64: AArch64 Function Attributes. (line 49) * ARM [Annotated C++ Reference Manual]: Backwards Compatibility. (line 6) + * ARM options: ARM Options. (line 6) * arrays of length zero: Zero Length. (line 6) * arrays of variable length: Variable Length. (line 6) * arrays, non-lvalue: Subscripting. (line 6) *************** Keyword Index *** 54858,54873 **** * asinhf: Other Builtins. (line 6) * asinhl: Other Builtins. (line 6) * asinl: Other Builtins. (line 6) ! * asm assembler template: Extended Asm. (line 218) ! * asm clobbers: Extended Asm. (line 646) * asm constraints: Constraints. (line 6) ! * asm expressions: Extended Asm. (line 551) ! * asm flag output operands: Extended Asm. (line 480) ! * asm goto labels: Extended Asm. (line 715) ! * asm input operands: Extended Asm. (line 551) * asm keyword: Using Assembly Language with C. (line 6) ! * asm output operands: Extended Asm. (line 321) * asm volatile: Extended Asm. (line 109) * assembler names for identifiers: Asm Labels. (line 6) * assembly code, invalid: Bug Criteria. (line 12) --- 55389,55404 ---- * asinhf: Other Builtins. (line 6) * asinhl: Other Builtins. (line 6) * asinl: Other Builtins. (line 6) ! * asm assembler template: Extended Asm. (line 219) ! * asm clobbers: Extended Asm. (line 663) * asm constraints: Constraints. (line 6) ! * asm expressions: Extended Asm. (line 567) ! * asm flag output operands: Extended Asm. (line 482) ! * asm goto labels: Extended Asm. (line 733) ! * asm input operands: Extended Asm. (line 567) * asm keyword: Using Assembly Language with C. (line 6) ! * asm output operands: Extended Asm. (line 322) * asm volatile: Extended Asm. (line 109) * assembler names for identifiers: Asm Labels. (line 6) * assembly code, invalid: Bug Criteria. (line 12) *************** Keyword Index *** 54926,54938 **** * bug criteria: Bug Criteria. (line 6) * bugs: Bugs. (line 6) * bugs, known: Trouble. (line 6) - * built-in functions: C Dialect Options. (line 209) * built-in functions <1>: Other Builtins. (line 6) * bzero: Other Builtins. (line 6) * C compilation options: Invoking GCC. (line 18) * C intermediate output, nonexistent: G++ and GCC. (line 35) * C language extensions: C Extensions. (line 6) ! * C language, traditional: C Dialect Options. (line 346) * C standard: Standards. (line 13) * C standards: Standards. (line 13) * c++: Invoking G++. (line 14) --- 55457,55469 ---- * bug criteria: Bug Criteria. (line 6) * bugs: Bugs. (line 6) * bugs, known: Trouble. (line 6) * built-in functions <1>: Other Builtins. (line 6) + * built-in functions: C Dialect Options. (line 212) * bzero: Other Builtins. (line 6) * C compilation options: Invoking GCC. (line 18) * C intermediate output, nonexistent: G++ and GCC. (line 35) * C language extensions: C Extensions. (line 6) ! * C language, traditional: C Dialect Options. (line 345) * C standard: Standards. (line 13) * C standards: Standards. (line 13) * c++: Invoking G++. (line 14) *************** Keyword Index *** 54958,54963 **** --- 55489,55496 ---- * C95: Standards. (line 13) * C99: Standards. (line 13) * C9X: Standards. (line 13) + * C_INCLUDE_PATH: Environment Variables. + (line 130) * cabs: Other Builtins. (line 6) * cabsf: Other Builtins. (line 6) * cabsl: Other Builtins. (line 6) *************** Keyword Index *** 54968,54974 **** * cacoshl: Other Builtins. (line 6) * cacosl: Other Builtins. (line 6) * callee_pop_aggregate_return function attribute, x86: x86 Function Attributes. ! (line 47) * calling functions through the function vector on SH2A: SH Function Attributes. (line 9) * calloc: Other Builtins. (line 6) --- 55501,55507 ---- * cacoshl: Other Builtins. (line 6) * cacosl: Other Builtins. (line 6) * callee_pop_aggregate_return function attribute, x86: x86 Function Attributes. ! (line 46) * calling functions through the function vector on SH2A: SH Function Attributes. (line 9) * calloc: Other Builtins. (line 6) *************** Keyword Index *** 54993,54999 **** * catanhl: Other Builtins. (line 6) * catanl: Other Builtins. (line 6) * cb variable attribute, MeP: MeP Variable Attributes. ! (line 46) * cbrt: Other Builtins. (line 6) * cbrtf: Other Builtins. (line 6) * cbrtl: Other Builtins. (line 6) --- 55526,55532 ---- * catanhl: Other Builtins. (line 6) * catanl: Other Builtins. (line 6) * cb variable attribute, MeP: MeP Variable Attributes. ! (line 48) * cbrt: Other Builtins. (line 6) * cbrtf: Other Builtins. (line 6) * cbrtl: Other Builtins. (line 6) *************** Keyword Index *** 55015,55021 **** (line 553) * character set, input: Preprocessor Options. (line 566) ! * character set, input normalization: Warning Options. (line 1670) * character set, wide execution: Preprocessor Options. (line 558) * cimag: Other Builtins. (line 6) --- 55548,55554 ---- (line 553) * character set, input: Preprocessor Options. (line 566) ! * character set, input normalization: Warning Options. (line 1689) * character set, wide execution: Preprocessor Options. (line 558) * cimag: Other Builtins. (line 6) *************** Keyword Index *** 55040,55048 **** * command options: Invoking GCC. (line 6) * comments, C++ style: C++ Comments. (line 6) * common variable attribute: Common Variable Attributes. ! (line 89) * comparison of signed and unsigned values, warning: Warning Options. ! (line 1482) * compilation statistics: Developer Options. (line 6) * compiler bugs, reporting: Bug Reporting. (line 6) * compiler compared to C++ preprocessor: G++ and GCC. (line 35) --- 55573,55581 ---- * command options: Invoking GCC. (line 6) * comments, C++ style: C++ Comments. (line 6) * common variable attribute: Common Variable Attributes. ! (line 90) * comparison of signed and unsigned values, warning: Warning Options. ! (line 1501) * compilation statistics: Developer Options. (line 6) * compiler bugs, reporting: Bug Reporting. (line 6) * compiler compared to C++ preprocessor: G++ and GCC. (line 35) *************** Keyword Index *** 55067,55075 **** * const function attribute: Common Function Attributes. (line 139) * const qualifier: Pointers to Arrays. (line 6) ! * constants in constraints: Simple Constraints. (line 68) * constraint modifier characters: Modifiers. (line 6) ! * constraint, matching: Simple Constraints. (line 137) * constraints, asm: Constraints. (line 6) * constraints, machine specific: Machine Constraints. (line 6) --- 55600,55608 ---- * const function attribute: Common Function Attributes. (line 139) * const qualifier: Pointers to Arrays. (line 6) ! * constants in constraints: Simple Constraints. (line 70) * constraint modifier characters: Modifiers. (line 6) ! * constraint, matching: Simple Constraints. (line 139) * constraints, asm: Constraints. (line 6) * constraints, machine specific: Machine Constraints. (line 6) *************** Keyword Index *** 55089,55097 **** * coshl: Other Builtins. (line 6) * cosl: Other Builtins. (line 6) * CPATH: Environment Variables. - (line 127) - * CPLUS_INCLUDE_PATH: Environment Variables. (line 129) * cpow: Other Builtins. (line 6) * cpowf: Other Builtins. (line 6) * cpowl: Other Builtins. (line 6) --- 55622,55630 ---- * coshl: Other Builtins. (line 6) * cosl: Other Builtins. (line 6) * CPATH: Environment Variables. (line 129) + * CPLUS_INCLUDE_PATH: Environment Variables. + (line 131) * cpow: Other Builtins. (line 6) * cpowf: Other Builtins. (line 6) * cpowl: Other Builtins. (line 6) *************** Keyword Index *** 55123,55134 **** * ctanhf: Other Builtins. (line 6) * ctanhl: Other Builtins. (line 6) * ctanl: Other Builtins. (line 6) - * C_INCLUDE_PATH: Environment Variables. - (line 128) * Darwin options: Darwin Options. (line 6) * dcgettext: Other Builtins. (line 6) - * dd integer suffix: Decimal Float. (line 6) * DD integer suffix: Decimal Float. (line 6) * deallocating variable length arrays: Variable Length. (line 22) * debug dump options: Developer Options. (line 6) * debugging GCC: Developer Options. (line 6) --- 55656,55665 ---- * ctanhf: Other Builtins. (line 6) * ctanhl: Other Builtins. (line 6) * ctanl: Other Builtins. (line 6) * Darwin options: Darwin Options. (line 6) * dcgettext: Other Builtins. (line 6) * DD integer suffix: Decimal Float. (line 6) + * dd integer suffix: Decimal Float. (line 6) * deallocating variable length arrays: Variable Length. (line 22) * debug dump options: Developer Options. (line 6) * debugging GCC: Developer Options. (line 6) *************** Keyword Index *** 55142,55154 **** * declaring static data in C++: Static Definitions. (line 6) * defining static data in C++: Static Definitions. (line 6) * dependencies for make as output: Environment Variables. ! (line 156) ! * dependencies for make as output <1>: Environment Variables. ! (line 172) * dependencies, make: Preprocessor Options. (line 185) * DEPENDENCIES_OUTPUT: Environment Variables. ! (line 155) * dependent name lookup: Name lookup. (line 6) * deprecated enumerator attribute: Enumerator Attributes. (line 27) --- 55673,55683 ---- * declaring static data in C++: Static Definitions. (line 6) * defining static data in C++: Static Definitions. (line 6) * dependencies for make as output: Environment Variables. ! (line 157) * dependencies, make: Preprocessor Options. (line 185) * DEPENDENCIES_OUTPUT: Environment Variables. ! (line 156) * dependent name lookup: Name lookup. (line 6) * deprecated enumerator attribute: Enumerator Attributes. (line 27) *************** Keyword Index *** 55157,55191 **** * deprecated type attribute: Common Type Attributes. (line 111) * deprecated variable attribute: Common Variable Attributes. ! (line 98) * designated initializers: Designated Inits. (line 6) * designated_init type attribute: Common Type Attributes. (line 139) ! * designator lists: Designated Inits. (line 96) * designators: Designated Inits. (line 64) * destructor function attribute: Common Function Attributes. (line 154) * developer options: Developer Options. (line 6) - * df integer suffix: Decimal Float. (line 6) * DF integer suffix: Decimal Float. (line 6) * dgettext: Other Builtins. (line 6) * diagnostic messages: Diagnostic Message Formatting Options. (line 6) * dialect options: C Dialect Options. (line 6) ! * digits in constraint: Simple Constraints. (line 125) * directory options: Directory Options. (line 6) * disinterrupt function attribute, Epiphany: Epiphany Function Attributes. (line 9) * disinterrupt function attribute, MeP: MeP Function Attributes. (line 9) - * dl integer suffix: Decimal Float. (line 6) * DL integer suffix: Decimal Float. (line 6) * dllexport function attribute: Microsoft Windows Function Attributes. (line 10) * dllexport variable attribute: Microsoft Windows Variable Attributes. (line 12) * dllimport function attribute: Microsoft Windows Function Attributes. ! (line 42) * dllimport variable attribute: Microsoft Windows Variable Attributes. (line 12) * dollar signs in identifier names: Dollar Signs. (line 6) --- 55686,55720 ---- * deprecated type attribute: Common Type Attributes. (line 111) * deprecated variable attribute: Common Variable Attributes. ! (line 99) * designated initializers: Designated Inits. (line 6) * designated_init type attribute: Common Type Attributes. (line 139) ! * designator lists: Designated Inits. (line 97) * designators: Designated Inits. (line 64) * destructor function attribute: Common Function Attributes. (line 154) * developer options: Developer Options. (line 6) * DF integer suffix: Decimal Float. (line 6) + * df integer suffix: Decimal Float. (line 6) * dgettext: Other Builtins. (line 6) * diagnostic messages: Diagnostic Message Formatting Options. (line 6) * dialect options: C Dialect Options. (line 6) ! * digits in constraint: Simple Constraints. (line 127) * directory options: Directory Options. (line 6) * disinterrupt function attribute, Epiphany: Epiphany Function Attributes. (line 9) * disinterrupt function attribute, MeP: MeP Function Attributes. (line 9) * DL integer suffix: Decimal Float. (line 6) + * dl integer suffix: Decimal Float. (line 6) * dllexport function attribute: Microsoft Windows Function Attributes. (line 10) * dllexport variable attribute: Microsoft Windows Variable Attributes. (line 12) * dllimport function attribute: Microsoft Windows Function Attributes. ! (line 44) * dllimport variable attribute: Microsoft Windows Variable Attributes. (line 12) * dollar signs in identifier names: Dollar Signs. (line 6) *************** Keyword Index *** 55195,55213 **** * dremf: Other Builtins. (line 6) * dreml: Other Builtins. (line 6) * dump options: Developer Options. (line 6) ! * E in constraint: Simple Constraints. (line 87) * earlyclobber operand: Modifiers. (line 25) * eight-bit data on the H8/300, H8/300H, and H8S: H8/300 Variable Attributes. (line 9) * eightbit_data variable attribute, H8/300: H8/300 Variable Attributes. (line 9) ! * EIND: AVR Options. (line 245) * either function attribute, MSP430: MSP430 Function Attributes. (line 53) * either variable attribute, MSP430: MSP430 Variable Attributes. (line 24) * empty structures: Empty Structures. (line 6) ! * Enable Cilk Plus: C Dialect Options. (line 290) * Enumerator Attributes: Enumerator Attributes. (line 6) * environment variables: Environment Variables. --- 55724,55742 ---- * dremf: Other Builtins. (line 6) * dreml: Other Builtins. (line 6) * dump options: Developer Options. (line 6) ! * E in constraint: Simple Constraints. (line 89) * earlyclobber operand: Modifiers. (line 25) * eight-bit data on the H8/300, H8/300H, and H8S: H8/300 Variable Attributes. (line 9) * eightbit_data variable attribute, H8/300: H8/300 Variable Attributes. (line 9) ! * EIND: AVR Options. (line 243) * either function attribute, MSP430: MSP430 Function Attributes. (line 53) * either variable attribute, MSP430: MSP430 Variable Attributes. (line 24) * empty structures: Empty Structures. (line 6) ! * Enable Cilk Plus: C Dialect Options. (line 289) * Enumerator Attributes: Enumerator Attributes. (line 6) * environment variables: Environment Variables. *************** Keyword Index *** 55251,55264 **** * expressions containing statements: Statement Exprs. (line 6) * expressions, constructor: Compound Literals. (line 6) * extended asm: Extended Asm. (line 6) ! * extensible constraints: Simple Constraints. (line 161) * extensions, ?:: Conditionals. (line 6) * extensions, C language: C Extensions. (line 6) * extensions, C++ language: C++ Extensions. (line 6) * external declaration scope: Incompatibilities. (line 80) * externally_visible function attribute: Common Function Attributes. (line 214) ! * F in constraint: Simple Constraints. (line 92) * fabs: Other Builtins. (line 6) * fabsf: Other Builtins. (line 6) * fabsl: Other Builtins. (line 6) --- 55780,55793 ---- * expressions containing statements: Statement Exprs. (line 6) * expressions, constructor: Compound Literals. (line 6) * extended asm: Extended Asm. (line 6) ! * extensible constraints: Simple Constraints. (line 163) * extensions, ?:: Conditionals. (line 6) * extensions, C language: C Extensions. (line 6) * extensions, C++ language: C++ Extensions. (line 6) * external declaration scope: Incompatibilities. (line 80) * externally_visible function attribute: Common Function Attributes. (line 214) ! * F in constraint: Simple Constraints. (line 94) * fabs: Other Builtins. (line 6) * fabsf: Other Builtins. (line 6) * fabsl: Other Builtins. (line 6) *************** Keyword Index *** 55269,55283 **** * far type attribute, MeP: MeP Type Attributes. (line 6) * far variable attribute, MeP: MeP Variable Attributes. ! (line 30) ! * fastcall function attribute, x86-32: x86 Function Attributes. ! (line 15) * fast_interrupt function attribute, M32C: M32C Function Attributes. (line 14) * fast_interrupt function attribute, MicroBlaze: MicroBlaze Function Attributes. (line 27) * fast_interrupt function attribute, RX: RX Function Attributes. (line 9) * fatal signal: Bug Criteria. (line 9) * fdim: Other Builtins. (line 6) * fdimf: Other Builtins. (line 6) --- 55798,55812 ---- * far type attribute, MeP: MeP Type Attributes. (line 6) * far variable attribute, MeP: MeP Variable Attributes. ! (line 31) * fast_interrupt function attribute, M32C: M32C Function Attributes. (line 14) * fast_interrupt function attribute, MicroBlaze: MicroBlaze Function Attributes. (line 27) * fast_interrupt function attribute, RX: RX Function Attributes. (line 9) + * fastcall function attribute, x86-32: x86 Function Attributes. + (line 15) * fatal signal: Bug Criteria. (line 9) * fdim: Other Builtins. (line 6) * fdimf: Other Builtins. (line 6) *************** Keyword Index *** 55295,55301 **** * flexible array members: Zero Length. (line 6) * float as function value type: Incompatibilities. (line 141) * floating point precision: Disappointments. (line 68) ! * floating-point precision: Optimize Options. (line 1949) * floor: Other Builtins. (line 6) * floorf: Other Builtins. (line 6) * floorl: Other Builtins. (line 6) --- 55824,55830 ---- * flexible array members: Zero Length. (line 6) * float as function value type: Incompatibilities. (line 141) * floating point precision: Disappointments. (line 68) ! * floating-point precision: Optimize Options. (line 1957) * floor: Other Builtins. (line 6) * floorf: Other Builtins. (line 6) * floorl: Other Builtins. (line 6) *************** Keyword Index *** 55312,55322 **** * fmodf: Other Builtins. (line 6) * fmodl: Other Builtins. (line 6) * force_align_arg_pointer function attribute, x86: x86 Function Attributes. ! (line 90) * format function attribute: Common Function Attributes. (line 234) * format_arg function attribute: Common Function Attributes. ! (line 299) * Fortran: G++ and GCC. (line 6) * forwarder_section function attribute, Epiphany: Epiphany Function Attributes. (line 13) --- 55841,55851 ---- * fmodf: Other Builtins. (line 6) * fmodl: Other Builtins. (line 6) * force_align_arg_pointer function attribute, x86: x86 Function Attributes. ! (line 87) * format function attribute: Common Function Attributes. (line 234) * format_arg function attribute: Common Function Attributes. ! (line 300) * Fortran: G++ and GCC. (line 6) * forwarder_section function attribute, Epiphany: Epiphany Function Attributes. (line 13) *************** Keyword Index *** 55345,55394 **** * function versions: Function Multiversioning. (line 6) * function, size of pointer to: Pointer Arith. (line 6) * functions in arbitrary sections: Common Function Attributes. ! (line 694) * functions that are dynamically resolved: Common Function Attributes. ! (line 391) * functions that are passed arguments in registers on x86-32: x86 Function Attributes. ! (line 66) * functions that behave like malloc: Common Function Attributes. ! (line 476) * functions that have no side effects: Common Function Attributes. (line 139) - * functions that have no side effects <1>: Common Function Attributes. - (line 656) * functions that never return: Common Function Attributes. ! (line 601) * functions that pop the argument stack on x86-32: x86 Function Attributes. (line 9) - * functions that pop the argument stack on x86-32 <1>: x86 Function Attributes. - (line 15) - * functions that pop the argument stack on x86-32 <2>: x86 Function Attributes. - (line 23) - * functions that pop the argument stack on x86-32 <3>: x86 Function Attributes. - (line 98) * functions that return more than once: Common Function Attributes. ! (line 685) * functions with non-null pointer arguments: Common Function Attributes. ! (line 553) * functions with printf, scanf, strftime or strfmon style arguments: Common Function Attributes. (line 234) ! * function_vector function attribute, H8/300: H8/300 Function Attributes. ! (line 9) ! * function_vector function attribute, M16C/M32C: M32C Function Attributes. ! (line 20) ! * function_vector function attribute, SH: SH Function Attributes. ! (line 9) ! * G in constraint: Simple Constraints. (line 96) ! * g in constraint: Simple Constraints. (line 118) * g++: Invoking G++. (line 14) * G++: G++ and GCC. (line 30) * gamma: Other Builtins. (line 6) * gammaf: Other Builtins. (line 6) * gammaf_r: Other Builtins. (line 6) * gammal: Other Builtins. (line 6) * gammal_r: Other Builtins. (line 6) - * gamma_r: Other Builtins. (line 6) * GCC: G++ and GCC. (line 6) * GCC command options: Invoking GCC. (line 6) * GCC_COLORS environment variable: Diagnostic Message Formatting Options. --- 55874,55915 ---- * function versions: Function Multiversioning. (line 6) * function, size of pointer to: Pointer Arith. (line 6) + * function_vector function attribute, H8/300: H8/300 Function Attributes. + (line 9) + * function_vector function attribute, M16C/M32C: M32C Function Attributes. + (line 20) + * function_vector function attribute, SH: SH Function Attributes. + (line 9) * functions in arbitrary sections: Common Function Attributes. ! (line 698) * functions that are dynamically resolved: Common Function Attributes. ! (line 395) * functions that are passed arguments in registers on x86-32: x86 Function Attributes. ! (line 63) * functions that behave like malloc: Common Function Attributes. ! (line 480) * functions that have no side effects: Common Function Attributes. (line 139) * functions that never return: Common Function Attributes. ! (line 605) * functions that pop the argument stack on x86-32: x86 Function Attributes. (line 9) * functions that return more than once: Common Function Attributes. ! (line 689) * functions with non-null pointer arguments: Common Function Attributes. ! (line 557) * functions with printf, scanf, strftime or strfmon style arguments: Common Function Attributes. (line 234) ! * g in constraint: Simple Constraints. (line 120) ! * G in constraint: Simple Constraints. (line 98) * g++: Invoking G++. (line 14) * G++: G++ and GCC. (line 30) * gamma: Other Builtins. (line 6) + * gamma_r: Other Builtins. (line 6) * gammaf: Other Builtins. (line 6) * gammaf_r: Other Builtins. (line 6) * gammal: Other Builtins. (line 6) * gammal_r: Other Builtins. (line 6) * GCC: G++ and GCC. (line 6) * GCC command options: Invoking GCC. (line 6) * GCC_COLORS environment variable: Diagnostic Message Formatting Options. *************** Keyword Index *** 55410,55463 **** * general-regs-only function attribute, AArch64: AArch64 Function Attributes. (line 12) * gettext: Other Builtins. (line 6) ! * global offset table: Code Gen Options. (line 273) * global register after longjmp: Global Register Variables. ! (line 74) * global register variables: Global Register Variables. (line 6) * GNAT: G++ and GCC. (line 30) * GNU C Compiler: G++ and GCC. (line 6) * GNU Compiler Collection: G++ and GCC. (line 6) * gnu_inline function attribute: Common Function Attributes. ! (line 345) * Go: G++ and GCC. (line 6) * goto with computed label: Labels as Values. (line 6) * gprof: Instrumentation Options. (line 24) * grouping options: Invoking GCC. (line 31) ! * H in constraint: Simple Constraints. (line 96) * half-precision floating point: Half-Precision. (line 6) * hardware models and configurations, specifying: Submodel Options. (line 6) * hex floats: Hex Floats. (line 6) * highlight, color: Diagnostic Message Formatting Options. (line 35) - * hk fixed-suffix: Fixed-Point. (line 6) * HK fixed-suffix: Fixed-Point. (line 6) * hosted environment: Standards. (line 13) - * hosted environment <1>: C Dialect Options. (line 243) - * hosted environment <2>: C Dialect Options. (line 251) * hosted implementation: Standards. (line 13) * hot function attribute: Common Function Attributes. ! (line 381) * hot label attribute: Label Attributes. (line 37) * hotpatch function attribute, S/390: S/390 Function Attributes. (line 9) * HPPA Options: HPPA Options. (line 6) - * hr fixed-suffix: Fixed-Point. (line 6) * HR fixed-suffix: Fixed-Point. (line 6) * hypot: Other Builtins. (line 6) * hypotf: Other Builtins. (line 6) * hypotl: Other Builtins. (line 6) ! * i in constraint: Simple Constraints. (line 68) ! * I in constraint: Simple Constraints. (line 79) * IA-64 Options: IA-64 Options. (line 6) * IBM RS/6000 and PowerPC Options: RS/6000 and PowerPC Options. (line 6) * identifier names, dollar signs in: Dollar Signs. (line 6) * identifiers, names in assembler code: Asm Labels. (line 6) * ifunc function attribute: Common Function Attributes. ! (line 391) * ilogb: Other Builtins. (line 6) * ilogbf: Other Builtins. (line 6) * ilogbl: Other Builtins. (line 6) --- 55931,55983 ---- * general-regs-only function attribute, AArch64: AArch64 Function Attributes. (line 12) * gettext: Other Builtins. (line 6) ! * global offset table: Code Gen Options. (line 274) * global register after longjmp: Global Register Variables. ! (line 76) * global register variables: Global Register Variables. (line 6) * GNAT: G++ and GCC. (line 30) * GNU C Compiler: G++ and GCC. (line 6) * GNU Compiler Collection: G++ and GCC. (line 6) * gnu_inline function attribute: Common Function Attributes. ! (line 347) * Go: G++ and GCC. (line 6) * goto with computed label: Labels as Values. (line 6) * gprof: Instrumentation Options. (line 24) * grouping options: Invoking GCC. (line 31) ! * H in constraint: Simple Constraints. (line 98) * half-precision floating point: Half-Precision. (line 6) * hardware models and configurations, specifying: Submodel Options. (line 6) * hex floats: Hex Floats. (line 6) * highlight, color: Diagnostic Message Formatting Options. (line 35) * HK fixed-suffix: Fixed-Point. (line 6) + * hk fixed-suffix: Fixed-Point. (line 6) + * hosted environment <1>: C Dialect Options. (line 246) * hosted environment: Standards. (line 13) * hosted implementation: Standards. (line 13) * hot function attribute: Common Function Attributes. ! (line 385) * hot label attribute: Label Attributes. (line 37) * hotpatch function attribute, S/390: S/390 Function Attributes. (line 9) * HPPA Options: HPPA Options. (line 6) * HR fixed-suffix: Fixed-Point. (line 6) + * hr fixed-suffix: Fixed-Point. (line 6) * hypot: Other Builtins. (line 6) * hypotf: Other Builtins. (line 6) * hypotl: Other Builtins. (line 6) ! * I in constraint: Simple Constraints. (line 81) ! * i in constraint: Simple Constraints. (line 70) * IA-64 Options: IA-64 Options. (line 6) * IBM RS/6000 and PowerPC Options: RS/6000 and PowerPC Options. (line 6) * identifier names, dollar signs in: Dollar Signs. (line 6) * identifiers, names in assembler code: Asm Labels. (line 6) * ifunc function attribute: Common Function Attributes. ! (line 395) * ilogb: Other Builtins. (line 6) * ilogbf: Other Builtins. (line 6) * ilogbl: Other Builtins. (line 6) *************** Keyword Index *** 55483,55493 **** * indirect calls, PowerPC: PowerPC Function Attributes. (line 10) * indirect functions: Common Function Attributes. ! (line 391) * initializations in expressions: Compound Literals. (line 6) * initializers with labeled elements: Designated Inits. (line 6) * initializers, non-constant: Initializers. (line 6) - * init_priority variable attribute: C++ Attributes. (line 50) * inline assembly language: Using Assembly Language with C. (line 6) * inline automatic for C++ member fns: Inline. (line 68) --- 56003,56013 ---- * indirect calls, PowerPC: PowerPC Function Attributes. (line 10) * indirect functions: Common Function Attributes. ! (line 395) ! * init_priority variable attribute: C++ Attributes. (line 50) * initializations in expressions: Compound Literals. (line 6) * initializers with labeled elements: Designated Inits. (line 6) * initializers, non-constant: Initializers. (line 6) * inline assembly language: Using Assembly Language with C. (line 6) * inline automatic for C++ member fns: Inline. (line 68) *************** Keyword Index *** 55555,55561 **** * io variable attribute, AVR: AVR Variable Attributes. (line 39) * io variable attribute, MeP: MeP Variable Attributes. ! (line 36) * io_low variable attribute, AVR: AVR Variable Attributes. (line 57) * isalnum: Other Builtins. (line 6) --- 56075,56081 ---- * io variable attribute, AVR: AVR Variable Attributes. (line 39) * io variable attribute, MeP: MeP Variable Attributes. ! (line 37) * io_low variable attribute, AVR: AVR Variable Attributes. (line 57) * isalnum: Other Builtins. (line 6) *************** Keyword Index *** 55604,55615 **** * j1f: Other Builtins. (line 6) * j1l: Other Builtins. (line 6) * Java: G++ and GCC. (line 6) ! * java_interface type attribute: C++ Attributes. (line 71) * jn: Other Builtins. (line 6) * jnf: Other Builtins. (line 6) * jnl: Other Builtins. (line 6) - * k fixed-suffix: Fixed-Point. (line 6) * K fixed-suffix: Fixed-Point. (line 6) * keep_interrupts_masked function attribute, MIPS: MIPS Function Attributes. (line 34) * kernel attribute, Nvidia PTX: Nvidia PTX Function Attributes. --- 56124,56135 ---- * j1f: Other Builtins. (line 6) * j1l: Other Builtins. (line 6) * Java: G++ and GCC. (line 6) ! * java_interface type attribute: C++ Attributes. (line 70) * jn: Other Builtins. (line 6) * jnf: Other Builtins. (line 6) * jnl: Other Builtins. (line 6) * K fixed-suffix: Fixed-Point. (line 6) + * k fixed-suffix: Fixed-Point. (line 6) * keep_interrupts_masked function attribute, MIPS: MIPS Function Attributes. (line 34) * kernel attribute, Nvidia PTX: Nvidia PTX Function Attributes. *************** Keyword Index *** 55636,55643 **** * labs: Other Builtins. (line 6) * LANG: Environment Variables. (line 21) - * LANG <1>: Environment Variables. - (line 106) * language dialect options: C Dialect Options. (line 6) * LC_ALL: Environment Variables. (line 21) --- 56156,56161 ---- *************** Keyword Index *** 55649,55675 **** * ldexpf: Other Builtins. (line 6) * ldexpl: Other Builtins. (line 6) * leaf function attribute: Common Function Attributes. ! (line 439) * length-zero arrays: Zero Length. (line 6) * lgamma: Other Builtins. (line 6) * lgammaf: Other Builtins. (line 6) * lgammaf_r: Other Builtins. (line 6) * lgammal: Other Builtins. (line 6) * lgammal_r: Other Builtins. (line 6) - * lgamma_r: Other Builtins. (line 6) * Libraries: Link Options. (line 30) * LIBRARY_PATH: Environment Variables. (line 97) * link options: Link Options. (line 6) ! * linker script: Link Options. (line 241) ! * lk fixed-suffix: Fixed-Point. (line 6) * LK fixed-suffix: Fixed-Point. (line 6) * LL integer suffix: Long Long. (line 6) * llabs: Other Builtins. (line 6) - * llk fixed-suffix: Fixed-Point. (line 6) * LLK fixed-suffix: Fixed-Point. (line 6) ! * llr fixed-suffix: Fixed-Point. (line 6) * LLR fixed-suffix: Fixed-Point. (line 6) * llrint: Other Builtins. (line 6) * llrintf: Other Builtins. (line 6) * llrintl: Other Builtins. (line 6) --- 56167,56193 ---- * ldexpf: Other Builtins. (line 6) * ldexpl: Other Builtins. (line 6) * leaf function attribute: Common Function Attributes. ! (line 443) * length-zero arrays: Zero Length. (line 6) * lgamma: Other Builtins. (line 6) + * lgamma_r: Other Builtins. (line 6) * lgammaf: Other Builtins. (line 6) * lgammaf_r: Other Builtins. (line 6) * lgammal: Other Builtins. (line 6) * lgammal_r: Other Builtins. (line 6) * Libraries: Link Options. (line 30) * LIBRARY_PATH: Environment Variables. (line 97) * link options: Link Options. (line 6) ! * linker script: Link Options. (line 245) * LK fixed-suffix: Fixed-Point. (line 6) + * lk fixed-suffix: Fixed-Point. (line 6) * LL integer suffix: Long Long. (line 6) * llabs: Other Builtins. (line 6) * LLK fixed-suffix: Fixed-Point. (line 6) ! * llk fixed-suffix: Fixed-Point. (line 6) * LLR fixed-suffix: Fixed-Point. (line 6) + * llr fixed-suffix: Fixed-Point. (line 6) * llrint: Other Builtins. (line 6) * llrintf: Other Builtins. (line 6) * llrintl: Other Builtins. (line 6) *************** Keyword Index *** 55677,55683 **** * llroundf: Other Builtins. (line 6) * llroundl: Other Builtins. (line 6) * LM32 options: LM32 Options. (line 6) ! * load address instruction: Simple Constraints. (line 152) * local labels: Local Labels. (line 6) * local variables in macros: Typeof. (line 46) * local variables, specifying registers: Local Register Variables. --- 56195,56201 ---- * llroundf: Other Builtins. (line 6) * llroundl: Other Builtins. (line 6) * LM32 options: LM32 Options. (line 6) ! * load address instruction: Simple Constraints. (line 154) * local labels: Local Labels. (line 6) * local variables in macros: Typeof. (line 46) * local variables, specifying registers: Local Register Variables. *************** Keyword Index *** 55704,55717 **** * logf: Other Builtins. (line 6) * logl: Other Builtins. (line 6) * long long data types: Long Long. (line 6) - * longcall function attribute, Blackfin: Blackfin Function Attributes. - (line 38) - * longcall function attribute, PowerPC: PowerPC Function Attributes. - (line 10) - * longjmp: Global Register Variables. - (line 74) - * longjmp incompatibilities: Incompatibilities. (line 39) - * longjmp warnings: Warning Options. (line 833) * long_call function attribute, ARC: ARC Function Attributes. (line 24) * long_call function attribute, ARM: ARM Function Attributes. --- 56222,56227 ---- *************** Keyword Index *** 55720,55731 **** (line 57) * long_call function attribute, MIPS: MIPS Function Attributes. (line 62) * lower function attribute, MSP430: MSP430 Function Attributes. (line 53) * lower variable attribute, MSP430: MSP430 Variable Attributes. (line 24) - * lr fixed-suffix: Fixed-Point. (line 6) * LR fixed-suffix: Fixed-Point. (line 6) * lrint: Other Builtins. (line 6) * lrintf: Other Builtins. (line 6) * lrintl: Other Builtins. (line 6) --- 56230,56249 ---- (line 57) * long_call function attribute, MIPS: MIPS Function Attributes. (line 62) + * longcall function attribute, Blackfin: Blackfin Function Attributes. + (line 38) + * longcall function attribute, PowerPC: PowerPC Function Attributes. + (line 10) + * longjmp: Global Register Variables. + (line 76) + * longjmp incompatibilities: Incompatibilities. (line 39) + * longjmp warnings: Warning Options. (line 844) * lower function attribute, MSP430: MSP430 Function Attributes. (line 53) * lower variable attribute, MSP430: MSP430 Variable Attributes. (line 24) * LR fixed-suffix: Fixed-Point. (line 6) + * lr fixed-suffix: Fixed-Point. (line 6) * lrint: Other Builtins. (line 6) * lrintf: Other Builtins. (line 6) * lrintl: Other Builtins. (line 6) *************** Keyword Index *** 55749,55758 **** (line 185) * malloc: Other Builtins. (line 6) * malloc function attribute: Common Function Attributes. ! (line 476) ! * matching constraint: Simple Constraints. (line 137) * may_alias type attribute: Common Type Attributes. ! (line 150) * MCore options: MCore Options. (line 6) * medium_call function attribute, ARC: ARC Function Attributes. (line 24) --- 56267,56276 ---- (line 185) * malloc: Other Builtins. (line 6) * malloc function attribute: Common Function Attributes. ! (line 480) ! * matching constraint: Simple Constraints. (line 139) * may_alias type attribute: Common Type Attributes. ! (line 151) * MCore options: MCore Options. (line 6) * medium_call function attribute, ARC: ARC Function Attributes. (line 24) *************** Keyword Index *** 55772,55778 **** (line 6) * MicroBlaze Options: MicroBlaze Options. (line 6) * micromips function attribute: MIPS Function Attributes. ! (line 89) * middle-operands, omitted: Conditionals. (line 6) * MIPS options: MIPS Options. (line 6) * mips16 function attribute, MIPS: MIPS Function Attributes. --- 56290,56296 ---- (line 6) * MicroBlaze Options: MicroBlaze Options. (line 6) * micromips function attribute: MIPS Function Attributes. ! (line 88) * middle-operands, omitted: Conditionals. (line 6) * MIPS options: MIPS Options. (line 6) * mips16 function attribute, MIPS: MIPS Function Attributes. *************** Keyword Index *** 55786,55792 **** * MMIX Options: MMIX Options. (line 6) * MN10300 options: MN10300 Options. (line 6) * mode variable attribute: Common Variable Attributes. ! (line 119) * model function attribute, M32R/D: M32R/D Function Attributes. (line 15) * model variable attribute, IA-64: IA-64 Variable Attributes. --- 56304,56310 ---- * MMIX Options: MMIX Options. (line 6) * MN10300 options: MN10300 Options. (line 6) * mode variable attribute: Common Variable Attributes. ! (line 120) * model function attribute, M32R/D: M32R/D Function Attributes. (line 15) * model variable attribute, IA-64: IA-64 Variable Attributes. *************** Keyword Index *** 55798,55808 **** * modfl: Other Builtins. (line 6) * modifiers in constraints: Modifiers. (line 6) * Moxie Options: Moxie Options. (line 6) - * MSP430 Options: MSP430 Options. (line 6) * ms_abi function attribute, x86: x86 Function Attributes. (line 34) * ms_hook_prologue function attribute, x86: x86 Function Attributes. ! (line 59) * ms_struct type attribute, PowerPC: PowerPC Type Attributes. (line 9) * ms_struct type attribute, x86: x86 Type Attributes. --- 56316,56325 ---- * modfl: Other Builtins. (line 6) * modifiers in constraints: Modifiers. (line 6) * Moxie Options: Moxie Options. (line 6) * ms_abi function attribute, x86: x86 Function Attributes. (line 34) * ms_hook_prologue function attribute, x86: x86 Function Attributes. ! (line 57) * ms_struct type attribute, PowerPC: PowerPC Type Attributes. (line 9) * ms_struct type attribute, x86: x86 Type Attributes. *************** Keyword Index *** 55811,55819 **** (line 9) * ms_struct variable attribute, x86: x86 Variable Attributes. (line 11) * multiple alternative constraints: Multi-Alternative. (line 6) * multiprecision arithmetic: Long Long. (line 6) ! * n in constraint: Simple Constraints. (line 73) * naked function attribute, ARM: ARM Function Attributes. (line 41) * naked function attribute, AVR: AVR Function Attributes. --- 56328,56337 ---- (line 9) * ms_struct variable attribute, x86: x86 Variable Attributes. (line 11) + * MSP430 Options: MSP430 Options. (line 6) * multiple alternative constraints: Multi-Alternative. (line 6) * multiprecision arithmetic: Long Long. (line 6) ! * n in constraint: Simple Constraints. (line 75) * naked function attribute, ARM: ARM Function Attributes. (line 41) * naked function attribute, AVR: AVR Function Attributes. *************** Keyword Index *** 55823,55829 **** * naked function attribute, MSP430: MSP430 Function Attributes. (line 30) * naked function attribute, NDS32: NDS32 Function Attributes. ! (line 35) * naked function attribute, RL78: RL78 Function Attributes. (line 20) * naked function attribute, RX: RX Function Attributes. --- 56341,56347 ---- * naked function attribute, MSP430: MSP430 Function Attributes. (line 30) * naked function attribute, NDS32: NDS32 Function Attributes. ! (line 39) * naked function attribute, RL78: RL78 Function Attributes. (line 20) * naked function attribute, RX: RX Function Attributes. *************** Keyword Index *** 55842,55848 **** * near type attribute, MeP: MeP Type Attributes. (line 6) * near variable attribute, MeP: MeP Variable Attributes. ! (line 24) * nearbyint: Other Builtins. (line 6) * nearbyintf: Other Builtins. (line 6) * nearbyintl: Other Builtins. (line 6) --- 56360,56366 ---- * near type attribute, MeP: MeP Type Attributes. (line 6) * near variable attribute, MeP: MeP Variable Attributes. ! (line 25) * nearbyint: Other Builtins. (line 6) * nearbyintf: Other Builtins. (line 6) * nearbyintl: Other Builtins. (line 6) *************** Keyword Index *** 55850,55856 **** (line 19) * nested functions: Nested Functions. (line 6) * nested_ready function attribute, NDS32: NDS32 Function Attributes. ! (line 23) * nesting function attribute, Blackfin: Blackfin Function Attributes. (line 45) * newlines (escaped): Escaped Newlines. (line 6) --- 56368,56374 ---- (line 19) * nested functions: Nested Functions. (line 6) * nested_ready function attribute, NDS32: NDS32 Function Attributes. ! (line 25) * nesting function attribute, Blackfin: Blackfin Function Attributes. (line 45) * newlines (escaped): Escaped Newlines. (line 6) *************** Keyword Index *** 55860,55933 **** * nexttoward: Other Builtins. (line 6) * nexttowardf: Other Builtins. (line 6) * nexttowardl: Other Builtins. (line 6) ! * NFC: Warning Options. (line 1670) ! * NFKC: Warning Options. (line 1670) * Nios II options: Nios II Options. (line 6) * nmi function attribute, NDS32: NDS32 Function Attributes. ! (line 50) * NMI handler functions on the Blackfin processor: Blackfin Function Attributes. (line 50) * nmi_handler function attribute, Blackfin: Blackfin Function Attributes. (line 50) * noclone function attribute: Common Function Attributes. ! (line 536) * nocommon variable attribute: Common Variable Attributes. ! (line 89) * nocompression function attribute, MIPS: MIPS Function Attributes. ! (line 106) * noinit variable attribute, MSP430: MSP430 Variable Attributes. (line 7) * noinline function attribute: Common Function Attributes. ! (line 542) * nomicromips function attribute: MIPS Function Attributes. ! (line 89) * nomips16 function attribute, MIPS: MIPS Function Attributes. (line 73) * non-constant initializers: Initializers. (line 6) * non-static inline function: Inline. (line 82) * nonnull function attribute: Common Function Attributes. ! (line 553) * noplt function attribute: Common Function Attributes. ! (line 577) * noreturn function attribute: Common Function Attributes. ! (line 601) * nosave_low_regs function attribute, SH: SH Function Attributes. (line 34) * note GCC_COLORS capability: Diagnostic Message Formatting Options. (line 75) * nothrow function attribute: Common Function Attributes. ! (line 632) * notshared type attribute, ARM: ARM Type Attributes. (line 6) - * not_nested function attribute, NDS32: NDS32 Function Attributes. - (line 21) - * no_icf function attribute: Common Function Attributes. - (line 488) - * no_instrument_function function attribute: Common Function Attributes. - (line 492) - * no_reorder function attribute: Common Function Attributes. - (line 497) - * no_sanitize_address function attribute: Common Function Attributes. - (line 506) - * no_sanitize_thread function attribute: Common Function Attributes. - (line 514) - * no_sanitize_undefined function attribute: Common Function Attributes. - (line 519) - * no_split_stack function attribute: Common Function Attributes. - (line 525) - * no_stack_limit function attribute: Common Function Attributes. - (line 531) * Nvidia PTX options: Nvidia PTX Options. (line 6) * nvptx options: Nvidia PTX Options. (line 6) * o in constraint: Simple Constraints. (line 23) * OBJC_INCLUDE_PATH: Environment Variables. ! (line 130) ! * Objective-C: G++ and GCC. (line 6) * Objective-C <1>: Standards. (line 183) * Objective-C and Objective-C++ options, command-line: Objective-C and Objective-C++ Dialect Options. (line 6) - * Objective-C++: G++ and GCC. (line 6) * Objective-C++ <1>: Standards. (line 183) * offsettable address: Simple Constraints. (line 23) * old-style function definitions: Function Prototypes. (line 6) --- 56378,56451 ---- * nexttoward: Other Builtins. (line 6) * nexttowardf: Other Builtins. (line 6) * nexttowardl: Other Builtins. (line 6) ! * NFC: Warning Options. (line 1689) ! * NFKC: Warning Options. (line 1689) * Nios II options: Nios II Options. (line 6) * nmi function attribute, NDS32: NDS32 Function Attributes. ! (line 54) * NMI handler functions on the Blackfin processor: Blackfin Function Attributes. (line 50) * nmi_handler function attribute, Blackfin: Blackfin Function Attributes. (line 50) + * no_icf function attribute: Common Function Attributes. + (line 492) + * no_instrument_function function attribute: Common Function Attributes. + (line 496) + * no_reorder function attribute: Common Function Attributes. + (line 501) + * no_sanitize_address function attribute: Common Function Attributes. + (line 510) + * no_sanitize_thread function attribute: Common Function Attributes. + (line 518) + * no_sanitize_undefined function attribute: Common Function Attributes. + (line 523) + * no_split_stack function attribute: Common Function Attributes. + (line 529) + * no_stack_limit function attribute: Common Function Attributes. + (line 535) * noclone function attribute: Common Function Attributes. ! (line 540) * nocommon variable attribute: Common Variable Attributes. ! (line 90) * nocompression function attribute, MIPS: MIPS Function Attributes. ! (line 104) * noinit variable attribute, MSP430: MSP430 Variable Attributes. (line 7) * noinline function attribute: Common Function Attributes. ! (line 546) * nomicromips function attribute: MIPS Function Attributes. ! (line 88) * nomips16 function attribute, MIPS: MIPS Function Attributes. (line 73) * non-constant initializers: Initializers. (line 6) * non-static inline function: Inline. (line 82) * nonnull function attribute: Common Function Attributes. ! (line 557) * noplt function attribute: Common Function Attributes. ! (line 581) * noreturn function attribute: Common Function Attributes. ! (line 605) * nosave_low_regs function attribute, SH: SH Function Attributes. (line 34) + * not_nested function attribute, NDS32: NDS32 Function Attributes. + (line 22) * note GCC_COLORS capability: Diagnostic Message Formatting Options. (line 75) * nothrow function attribute: Common Function Attributes. ! (line 636) * notshared type attribute, ARM: ARM Type Attributes. (line 6) * Nvidia PTX options: Nvidia PTX Options. (line 6) * nvptx options: Nvidia PTX Options. (line 6) * o in constraint: Simple Constraints. (line 23) * OBJC_INCLUDE_PATH: Environment Variables. ! (line 132) * Objective-C <1>: Standards. (line 183) + * Objective-C: G++ and GCC. (line 6) * Objective-C and Objective-C++ options, command-line: Objective-C and Objective-C++ Dialect Options. (line 6) * Objective-C++ <1>: Standards. (line 183) + * Objective-C++: G++ and GCC. (line 6) * offsettable address: Simple Constraints. (line 23) * old-style function definitions: Function Prototypes. (line 6) *************** Keyword Index *** 55935,55947 **** (line 37) * omitted middle-operands: Conditionals. (line 6) * open coding: Inline. (line 6) ! * OpenACC accelerator programming: C Dialect Options. (line 262) ! * OpenACC accelerator programming <1>: C Dialect Options. (line 271) * OpenMP parallel: C Dialect Options. (line 277) ! * OpenMP SIMD: C Dialect Options. (line 286) * operand constraints, asm: Constraints. (line 6) * optimize function attribute: Common Function Attributes. ! (line 639) * optimize options: Optimize Options. (line 6) * options to control diagnostics formatting: Diagnostic Message Formatting Options. (line 6) --- 56453,56464 ---- (line 37) * omitted middle-operands: Conditionals. (line 6) * open coding: Inline. (line 6) ! * OpenACC accelerator programming: C Dialect Options. (line 263) * OpenMP parallel: C Dialect Options. (line 277) ! * OpenMP SIMD: C Dialect Options. (line 285) * operand constraints, asm: Constraints. (line 6) * optimize function attribute: Common Function Attributes. ! (line 643) * optimize options: Optimize Options. (line 6) * options to control diagnostics formatting: Diagnostic Message Formatting Options. (line 6) *************** Keyword Index *** 55973,56010 **** (line 34) * OS_task function attribute, AVR: AVR Function Attributes. (line 34) ! * other register constraints: Simple Constraints. (line 161) * output file option: Overall Options. (line 183) * overloaded virtual function, warning: C++ Dialect Options. ! (line 664) ! * p in constraint: Simple Constraints. (line 152) * packed type attribute: Common Type Attributes. ! (line 186) * packed variable attribute: Common Variable Attributes. ! (line 130) * parameter forward declaration: Variable Length. (line 66) * partial_save function attribute, NDS32: NDS32 Function Attributes. ! (line 31) * Pascal: G++ and GCC. (line 23) * pcs function attribute, ARM: ARM Function Attributes. (line 51) * PDP-11 Options: PDP-11 Options. (line 6) * persistent variable attribute, MSP430: MSP430 Variable Attributes. (line 12) ! * PIC: Code Gen Options. (line 273) * picoChip options: picoChip Options. (line 6) * pmf: Bound member functions. (line 6) * pointer arguments: Common Function Attributes. (line 144) - * Pointer Bounds Checker attributes: Common Function Attributes. - (line 118) * Pointer Bounds Checker attributes <1>: Common Type Attributes. (line 84) * Pointer Bounds Checker builtins: Pointer Bounds Checker builtins. (line 6) * Pointer Bounds Checker options: Instrumentation Options. ! (line 339) * pointer to member function: Bound member functions. (line 6) * pointers to arrays: Pointers to Arrays. (line 6) --- 56490,56527 ---- (line 34) * OS_task function attribute, AVR: AVR Function Attributes. (line 34) ! * other register constraints: Simple Constraints. (line 163) * output file option: Overall Options. (line 183) * overloaded virtual function, warning: C++ Dialect Options. ! (line 670) ! * p in constraint: Simple Constraints. (line 154) * packed type attribute: Common Type Attributes. ! (line 187) * packed variable attribute: Common Variable Attributes. ! (line 131) * parameter forward declaration: Variable Length. (line 66) * partial_save function attribute, NDS32: NDS32 Function Attributes. ! (line 35) * Pascal: G++ and GCC. (line 23) * pcs function attribute, ARM: ARM Function Attributes. (line 51) * PDP-11 Options: PDP-11 Options. (line 6) * persistent variable attribute, MSP430: MSP430 Variable Attributes. (line 12) ! * PIC: Code Gen Options. (line 274) * picoChip options: picoChip Options. (line 6) * pmf: Bound member functions. (line 6) * pointer arguments: Common Function Attributes. (line 144) * Pointer Bounds Checker attributes <1>: Common Type Attributes. (line 84) + * Pointer Bounds Checker attributes: Common Function Attributes. + (line 118) * Pointer Bounds Checker builtins: Pointer Bounds Checker builtins. (line 6) * Pointer Bounds Checker options: Instrumentation Options. ! (line 333) * pointer to member function: Bound member functions. (line 6) * pointers to arrays: Pointers to Arrays. (line 6) *************** Keyword Index *** 56019,56031 **** * pragma GCC ivdep: Loop-Specific Pragmas. (line 7) * pragma GCC optimize: Function Specific Option Pragmas. ! (line 20) * pragma GCC pop_options: Function Specific Option Pragmas. ! (line 31) * pragma GCC push_options: Function Specific Option Pragmas. ! (line 31) * pragma GCC reset_options: Function Specific Option Pragmas. ! (line 39) * pragma GCC target: Function Specific Option Pragmas. (line 7) * pragma, address: M32C Pragmas. (line 15) --- 56536,56548 ---- * pragma GCC ivdep: Loop-Specific Pragmas. (line 7) * pragma GCC optimize: Function Specific Option Pragmas. ! (line 19) * pragma GCC pop_options: Function Specific Option Pragmas. ! (line 29) * pragma GCC push_options: Function Specific Option Pragmas. ! (line 29) * pragma GCC reset_options: Function Specific Option Pragmas. ! (line 36) * pragma GCC target: Function Specific Option Pragmas. (line 7) * pragma, address: M32C Pragmas. (line 15) *************** Keyword Index *** 56036,56049 **** * pragma, coprocessor subclass: MeP Pragmas. (line 28) * pragma, custom io_volatile: MeP Pragmas. (line 7) * pragma, diagnostic: Diagnostic Pragmas. (line 14) - * pragma, diagnostic <1>: Diagnostic Pragmas. (line 57) * pragma, disinterrupt: MeP Pragmas. (line 38) ! * pragma, fini: Solaris Pragmas. (line 20) ! * pragma, init: Solaris Pragmas. (line 26) ! * pragma, longcall: RS/6000 and PowerPC Pragmas. ! (line 14) * pragma, long_calls: ARM Pragmas. (line 11) * pragma, long_calls_off: ARM Pragmas. (line 17) * pragma, mark: Darwin Pragmas. (line 11) * pragma, memregs: M32C Pragmas. (line 7) * pragma, no_long_calls: ARM Pragmas. (line 14) --- 56553,56565 ---- * pragma, coprocessor subclass: MeP Pragmas. (line 28) * pragma, custom io_volatile: MeP Pragmas. (line 7) * pragma, diagnostic: Diagnostic Pragmas. (line 14) * pragma, disinterrupt: MeP Pragmas. (line 38) ! * pragma, fini: Solaris Pragmas. (line 19) ! * pragma, init: Solaris Pragmas. (line 24) * pragma, long_calls: ARM Pragmas. (line 11) * pragma, long_calls_off: ARM Pragmas. (line 17) + * pragma, longcall: RS/6000 and PowerPC Pragmas. + (line 14) * pragma, mark: Darwin Pragmas. (line 11) * pragma, memregs: M32C Pragmas. (line 7) * pragma, no_long_calls: ARM Pragmas. (line 14) *************** Keyword Index *** 56061,56067 **** * pragmas: Pragmas. (line 6) * pragmas in C++, effect on inlining: C++ Interface. (line 57) * pragmas, interface and implementation: C++ Interface. (line 6) ! * pragmas, warning of unknown: Warning Options. (line 850) * precompiled headers: Precompiled Headers. (line 6) * preprocessing numbers: Incompatibilities. (line 173) --- 56577,56583 ---- * pragmas: Pragmas. (line 6) * pragmas in C++, effect on inlining: C++ Interface. (line 57) * pragmas, interface and implementation: C++ Interface. (line 6) ! * pragmas, warning of unknown: Warning Options. (line 861) * precompiled headers: Precompiled Headers. (line 6) * preprocessing numbers: Incompatibilities. (line 173) *************** Keyword Index *** 56081,56120 **** * promotion of formal parameters: Function Prototypes. (line 6) * pure function attribute: Common Function Attributes. ! (line 656) ! * push address instruction: Simple Constraints. (line 152) * putchar: Other Builtins. (line 6) * puts: Other Builtins. (line 6) - * q floating point suffix: Floating Types. (line 6) * Q floating point suffix: Floating Types. (line 6) * qsort, and global register variables: Global Register Variables. ! (line 60) * quote GCC_COLORS capability: Diagnostic Message Formatting Options. (line 85) - * r fixed-suffix: Fixed-Point. (line 6) * R fixed-suffix: Fixed-Point. (line 6) ! * r in constraint: Simple Constraints. (line 64) ! * RAMPD: AVR Options. (line 356) ! * RAMPX: AVR Options. (line 356) ! * RAMPY: AVR Options. (line 356) ! * RAMPZ: AVR Options. (line 356) * ranges in case statements: Case Ranges. (line 6) * read-only strings: Incompatibilities. (line 9) * reentrant function attribute, MSP430: MSP430 Function Attributes. (line 40) * register variable after longjmp: Global Register Variables. ! (line 74) * registers for local variables: Local Register Variables. (line 6) ! * registers in constraints: Simple Constraints. (line 64) * registers, global allocation: Global Register Variables. (line 6) * registers, global variables in: Global Register Variables. (line 6) * regparm function attribute, x86: x86 Function Attributes. ! (line 66) ! * relocation truncated to fit (ColdFire): M680x0 Options. (line 325) ! * relocation truncated to fit (MIPS): MIPS Options. (line 236) * remainder: Other Builtins. (line 6) * remainderf: Other Builtins. (line 6) * remainderl: Other Builtins. (line 6) --- 56597,56636 ---- * promotion of formal parameters: Function Prototypes. (line 6) * pure function attribute: Common Function Attributes. ! (line 660) ! * push address instruction: Simple Constraints. (line 154) * putchar: Other Builtins. (line 6) * puts: Other Builtins. (line 6) * Q floating point suffix: Floating Types. (line 6) + * q floating point suffix: Floating Types. (line 6) * qsort, and global register variables: Global Register Variables. ! (line 62) * quote GCC_COLORS capability: Diagnostic Message Formatting Options. (line 85) * R fixed-suffix: Fixed-Point. (line 6) ! * r fixed-suffix: Fixed-Point. (line 6) ! * r in constraint: Simple Constraints. (line 66) ! * RAMPD: AVR Options. (line 359) ! * RAMPX: AVR Options. (line 359) ! * RAMPY: AVR Options. (line 359) ! * RAMPZ: AVR Options. (line 359) * ranges in case statements: Case Ranges. (line 6) * read-only strings: Incompatibilities. (line 9) * reentrant function attribute, MSP430: MSP430 Function Attributes. (line 40) * register variable after longjmp: Global Register Variables. ! (line 76) * registers for local variables: Local Register Variables. (line 6) ! * registers in constraints: Simple Constraints. (line 66) * registers, global allocation: Global Register Variables. (line 6) * registers, global variables in: Global Register Variables. (line 6) * regparm function attribute, x86: x86 Function Attributes. ! (line 63) ! * relocation truncated to fit (ColdFire): M680x0 Options. (line 329) ! * relocation truncated to fit (MIPS): MIPS Options. (line 239) * remainder: Other Builtins. (line 6) * remainderf: Other Builtins. (line 6) * remainderl: Other Builtins. (line 6) *************** Keyword Index *** 56124,56137 **** * renesas function attribute, SH: SH Function Attributes. (line 40) * reordering, warning: C++ Dialect Options. ! (line 582) * reporting bugs: Bugs. (line 6) * resbank function attribute, SH: SH Function Attributes. (line 44) * reset function attribute, NDS32: NDS32 Function Attributes. ! (line 45) * reset handler functions: NDS32 Function Attributes. ! (line 45) * rest argument (in macro): Variadic Macros. (line 6) * restricted pointers: Restricted Pointers. (line 6) --- 56640,56653 ---- * renesas function attribute, SH: SH Function Attributes. (line 40) * reordering, warning: C++ Dialect Options. ! (line 586) * reporting bugs: Bugs. (line 6) * resbank function attribute, SH: SH Function Attributes. (line 44) * reset function attribute, NDS32: NDS32 Function Attributes. ! (line 49) * reset handler functions: NDS32 Function Attributes. ! (line 49) * rest argument (in macro): Variadic Macros. (line 6) * restricted pointers: Restricted Pointers. (line 6) *************** Keyword Index *** 56140,56148 **** * restricted this pointer: Restricted Pointers. (line 6) * returns_nonnull function attribute: Common Function Attributes. ! (line 675) * returns_twice function attribute: Common Function Attributes. ! (line 685) * rindex: Other Builtins. (line 6) * rint: Other Builtins. (line 6) * rintf: Other Builtins. (line 6) --- 56656,56664 ---- * restricted this pointer: Restricted Pointers. (line 6) * returns_nonnull function attribute: Common Function Attributes. ! (line 679) * returns_twice function attribute: Common Function Attributes. ! (line 689) * rindex: Other Builtins. (line 6) * rint: Other Builtins. (line 6) * rintf: Other Builtins. (line 6) *************** Keyword Index *** 56158,56164 **** (line 6) * run-time options: Code Gen Options. (line 6) * RX Options: RX Options. (line 6) ! * s in constraint: Simple Constraints. (line 100) * S/390 and zSeries Options: S/390 and zSeries Options. (line 6) * saddr variable attribute, RL78: RL78 Variable Attributes. --- 56674,56680 ---- (line 6) * run-time options: Code Gen Options. (line 6) * RX Options: RX Options. (line 6) ! * s in constraint: Simple Constraints. (line 102) * S/390 and zSeries Options: S/390 and zSeries Options. (line 6) * saddr variable attribute, RL78: RL78 Variable Attributes. *************** Keyword Index *** 56167,56188 **** (line 56) * save all registers on the H8/300, H8/300H, and H8S: H8/300 Function Attributes. (line 23) * saveall function attribute, Blackfin: Blackfin Function Attributes. (line 56) * saveall function attribute, H8/300: H8/300 Function Attributes. (line 23) - * save_all function attribute, NDS32: NDS32 Function Attributes. - (line 28) - * save_volatiles function attribute, MicroBlaze: MicroBlaze Function Attributes. - (line 9) * scalar_storage_order type attribute: Common Type Attributes. ! (line 221) * scalb: Other Builtins. (line 6) * scalbf: Other Builtins. (line 6) * scalbl: Other Builtins. (line 6) * scalbln: Other Builtins. (line 6) * scalblnf: Other Builtins. (line 6) - * scalblnf <1>: Other Builtins. (line 6) * scalbn: Other Builtins. (line 6) * scalbnf: Other Builtins. (line 6) * scanf, and constant strings: Incompatibilities. (line 17) --- 56683,56703 ---- (line 56) * save all registers on the H8/300, H8/300H, and H8S: H8/300 Function Attributes. (line 23) + * save_all function attribute, NDS32: NDS32 Function Attributes. + (line 31) + * save_volatiles function attribute, MicroBlaze: MicroBlaze Function Attributes. + (line 9) * saveall function attribute, Blackfin: Blackfin Function Attributes. (line 56) * saveall function attribute, H8/300: H8/300 Function Attributes. (line 23) * scalar_storage_order type attribute: Common Type Attributes. ! (line 222) * scalb: Other Builtins. (line 6) * scalbf: Other Builtins. (line 6) * scalbl: Other Builtins. (line 6) * scalbln: Other Builtins. (line 6) * scalblnf: Other Builtins. (line 6) * scalbn: Other Builtins. (line 6) * scalbnf: Other Builtins. (line 6) * scanf, and constant strings: Incompatibilities. (line 17) *************** Keyword Index *** 56195,56228 **** (line 9) * search path: Directory Options. (line 6) * section function attribute: Common Function Attributes. ! (line 694) * section variable attribute: Common Variable Attributes. ! (line 151) * selectany variable attribute: Microsoft Windows Variable Attributes. (line 16) * sentinel function attribute: Common Function Attributes. ! (line 710) * setjmp: Global Register Variables. ! (line 74) * setjmp incompatibilities: Incompatibilities. (line 39) * shared strings: Incompatibilities. (line 9) * shared variable attribute: Microsoft Windows Variable Attributes. (line 37) - * shortcall function attribute, Blackfin: Blackfin Function Attributes. - (line 38) - * shortcall function attribute, PowerPC: PowerPC Function Attributes. - (line 10) * short_call function attribute, ARC: ARC Function Attributes. (line 24) * short_call function attribute, ARM: ARM Function Attributes. (line 31) * short_call function attribute, Epiphany: Epiphany Function Attributes. (line 57) * side effect in ?:: Conditionals. (line 20) * side effects, macro argument: Statement Exprs. (line 35) * side effects, order of evaluation: Non-bugs. (line 196) * signal function attribute, AVR: AVR Function Attributes. ! (line 58) * signbit: Other Builtins. (line 6) * signbitd128: Other Builtins. (line 6) * signbitd32: Other Builtins. (line 6) --- 56710,56743 ---- (line 9) * search path: Directory Options. (line 6) * section function attribute: Common Function Attributes. ! (line 698) * section variable attribute: Common Variable Attributes. ! (line 152) * selectany variable attribute: Microsoft Windows Variable Attributes. (line 16) * sentinel function attribute: Common Function Attributes. ! (line 714) * setjmp: Global Register Variables. ! (line 76) * setjmp incompatibilities: Incompatibilities. (line 39) * shared strings: Incompatibilities. (line 9) * shared variable attribute: Microsoft Windows Variable Attributes. (line 37) * short_call function attribute, ARC: ARC Function Attributes. (line 24) * short_call function attribute, ARM: ARM Function Attributes. (line 31) * short_call function attribute, Epiphany: Epiphany Function Attributes. (line 57) + * shortcall function attribute, Blackfin: Blackfin Function Attributes. + (line 38) + * shortcall function attribute, PowerPC: PowerPC Function Attributes. + (line 10) * side effect in ?:: Conditionals. (line 20) * side effects, macro argument: Statement Exprs. (line 35) * side effects, order of evaluation: Non-bugs. (line 196) * signal function attribute, AVR: AVR Function Attributes. ! (line 59) * signbit: Other Builtins. (line 6) * signbitd128: Other Builtins. (line 6) * signbitd32: Other Builtins. (line 6) *************** Keyword Index *** 56230,56242 **** * signbitf: Other Builtins. (line 6) * signbitl: Other Builtins. (line 6) * signed and unsigned values, comparison warning: Warning Options. ! (line 1482) * significand: Other Builtins. (line 6) * significandf: Other Builtins. (line 6) * significandl: Other Builtins. (line 6) ! * SIMD: C Dialect Options. (line 286) * simd function attribute: Common Function Attributes. ! (line 736) * simple constraints: Simple Constraints. (line 6) * sin: Other Builtins. (line 6) * sincos: Other Builtins. (line 6) --- 56745,56757 ---- * signbitf: Other Builtins. (line 6) * signbitl: Other Builtins. (line 6) * signed and unsigned values, comparison warning: Warning Options. ! (line 1501) * significand: Other Builtins. (line 6) * significandf: Other Builtins. (line 6) * significandl: Other Builtins. (line 6) ! * SIMD: C Dialect Options. (line 285) * simd function attribute: Common Function Attributes. ! (line 740) * simple constraints: Simple Constraints. (line 6) * sin: Other Builtins. (line 6) * sincos: Other Builtins. (line 6) *************** Keyword Index *** 56248,56259 **** * sinhl: Other Builtins. (line 6) * sinl: Other Builtins. (line 6) * sizeof: Typeof. (line 6) - * smaller data references: M32R/D Options. (line 57) * smaller data references <1>: Nios II Options. (line 9) * smaller data references (PowerPC): RS/6000 and PowerPC Options. ! (line 832) * snprintf: Other Builtins. (line 6) * Solaris 2 options: Solaris 2 Options. (line 6) * SPARC options: SPARC Options. (line 6) * Spec Files: Spec Files. (line 6) * specified registers: Explicit Register Variables. --- 56763,56776 ---- * sinhl: Other Builtins. (line 6) * sinl: Other Builtins. (line 6) * sizeof: Typeof. (line 6) * smaller data references <1>: Nios II Options. (line 9) + * smaller data references: M32R/D Options. (line 57) * smaller data references (PowerPC): RS/6000 and PowerPC Options. ! (line 809) * snprintf: Other Builtins. (line 6) * Solaris 2 options: Solaris 2 Options. (line 6) + * sp_switch function attribute, SH: SH Function Attributes. + (line 58) * SPARC options: SPARC Options. (line 6) * Spec Files: Spec Files. (line 6) * specified registers: Explicit Register Variables. *************** Keyword Index *** 56272,56293 **** (line 6) * spu_vector variable attribute, SPU: SPU Variable Attributes. (line 6) - * sp_switch function attribute, SH: SH Function Attributes. - (line 58) * sqrt: Other Builtins. (line 6) * sqrtf: Other Builtins. (line 6) * sqrtl: Other Builtins. (line 6) * sscanf: Other Builtins. (line 6) * sscanf, and constant strings: Incompatibilities. (line 17) * sseregparm function attribute, x86: x86 Function Attributes. ! (line 83) * stack_protect function attribute: Common Function Attributes. ! (line 758) * statements inside expressions: Statement Exprs. (line 6) * static data in C++, declaring and defining: Static Definitions. (line 6) * stdcall function attribute, x86-32: x86 Function Attributes. ! (line 98) * stpcpy: Other Builtins. (line 6) * stpncpy: Other Builtins. (line 6) * strcasecmp: Other Builtins. (line 6) --- 56789,56808 ---- (line 6) * spu_vector variable attribute, SPU: SPU Variable Attributes. (line 6) * sqrt: Other Builtins. (line 6) * sqrtf: Other Builtins. (line 6) * sqrtl: Other Builtins. (line 6) * sscanf: Other Builtins. (line 6) * sscanf, and constant strings: Incompatibilities. (line 17) * sseregparm function attribute, x86: x86 Function Attributes. ! (line 80) * stack_protect function attribute: Common Function Attributes. ! (line 762) * statements inside expressions: Statement Exprs. (line 6) * static data in C++, declaring and defining: Static Definitions. (line 6) * stdcall function attribute, x86-32: x86 Function Attributes. ! (line 95) * stpcpy: Other Builtins. (line 6) * stpncpy: Other Builtins. (line 6) * strcasecmp: Other Builtins. (line 6) *************** Keyword Index *** 56314,56320 **** * strstr: Other Builtins. (line 6) * struct: Unnamed Fields. (line 6) * struct __htm_tdb: S/390 System z Built-in Functions. ! (line 49) * structures: Incompatibilities. (line 146) * structures, constructor expression: Compound Literals. (line 6) * submodel options: Submodel Options. (line 6) --- 56829,56835 ---- * strstr: Other Builtins. (line 6) * struct: Unnamed Fields. (line 6) * struct __htm_tdb: S/390 System z Built-in Functions. ! (line 54) * structures: Incompatibilities. (line 146) * structures, constructor expression: Compound Literals. (line 6) * submodel options: Submodel Options. (line 6) *************** Keyword Index *** 56322,56335 **** * subscripting and function values: Subscripting. (line 6) * suffixes for C++ source: Invoking G++. (line 6) * SUNPRO_DEPENDENCIES: Environment Variables. ! (line 171) * suppressing warnings: Warning Options. (line 6) * surprises in C++: C++ Misunderstandings. (line 6) * syntax checking: Warning Options. (line 13) * syscall_linkage function attribute, IA-64: IA-64 Function Attributes. (line 9) ! * system headers, warnings from: Warning Options. (line 1081) * sysv_abi function attribute, x86: x86 Function Attributes. (line 34) * tan: Other Builtins. (line 6) --- 56837,56850 ---- * subscripting and function values: Subscripting. (line 6) * suffixes for C++ source: Invoking G++. (line 6) * SUNPRO_DEPENDENCIES: Environment Variables. ! (line 172) * suppressing warnings: Warning Options. (line 6) * surprises in C++: C++ Misunderstandings. (line 6) * syntax checking: Warning Options. (line 13) * syscall_linkage function attribute, IA-64: IA-64 Function Attributes. (line 9) ! * system headers, warnings from: Warning Options. (line 1093) * sysv_abi function attribute, x86: x86 Function Attributes. (line 34) * tan: Other Builtins. (line 6) *************** Keyword Index *** 56338,56372 **** * tanhf: Other Builtins. (line 6) * tanhl: Other Builtins. (line 6) * tanl: Other Builtins. (line 6) ! * target function attribute: Common Function Attributes. ! (line 763) ! * target function attribute <1>: ARM Function Attributes. ! (line 70) ! * target function attribute <2>: Nios II Function Attributes. ! (line 9) * target function attribute <3>: PowerPC Function Attributes. (line 21) ! * target function attribute <4>: S/390 Function Attributes. ! (line 22) ! * target function attribute <5>: x86 Function Attributes. ! (line 103) * target machine, specifying: Invoking GCC. (line 24) * target("abm") function attribute, x86: x86 Function Attributes. ! (line 109) * target("aes") function attribute, x86: x86 Function Attributes. ! (line 114) * target("align-stringops") function attribute, x86: x86 Function Attributes. ! (line 208) * target("altivec") function attribute, PowerPC: PowerPC Function Attributes. (line 28) * target("arch=ARCH") function attribute, x86: x86 Function Attributes. ! (line 217) * target("arm") function attribute, ARM: ARM Function Attributes. ! (line 80) * target("avoid-indexed-addresses") function attribute, PowerPC: PowerPC Function Attributes. (line 149) * target("cld") function attribute, x86: x86 Function Attributes. ! (line 179) * target("cmpb") function attribute, PowerPC: PowerPC Function Attributes. (line 34) * target("cpu=CPU") function attribute, PowerPC: PowerPC Function Attributes. --- 56853,56887 ---- * tanhf: Other Builtins. (line 6) * tanhl: Other Builtins. (line 6) * tanl: Other Builtins. (line 6) ! * target function attribute <1>: x86 Function Attributes. ! (line 100) ! * target function attribute <2>: S/390 Function Attributes. ! (line 21) * target function attribute <3>: PowerPC Function Attributes. (line 21) ! * target function attribute <4>: Nios II Function Attributes. ! (line 9) ! * target function attribute <5>: ARM Function Attributes. ! (line 69) ! * target function attribute: Common Function Attributes. ! (line 767) * target machine, specifying: Invoking GCC. (line 24) * target("abm") function attribute, x86: x86 Function Attributes. ! (line 106) * target("aes") function attribute, x86: x86 Function Attributes. ! (line 111) * target("align-stringops") function attribute, x86: x86 Function Attributes. ! (line 205) * target("altivec") function attribute, PowerPC: PowerPC Function Attributes. (line 28) * target("arch=ARCH") function attribute, x86: x86 Function Attributes. ! (line 214) * target("arm") function attribute, ARM: ARM Function Attributes. ! (line 79) * target("avoid-indexed-addresses") function attribute, PowerPC: PowerPC Function Attributes. (line 149) * target("cld") function attribute, x86: x86 Function Attributes. ! (line 176) * target("cmpb") function attribute, PowerPC: PowerPC Function Attributes. (line 34) * target("cpu=CPU") function attribute, PowerPC: PowerPC Function Attributes. *************** Keyword Index *** 56376,56418 **** * target("custom-INSN=N") function attribute, Nios II: Nios II Function Attributes. (line 16) * target("default") function attribute, x86: x86 Function Attributes. ! (line 117) * target("dlmzb") function attribute, PowerPC: PowerPC Function Attributes. (line 40) * target("fancy-math-387") function attribute, x86: x86 Function Attributes. ! (line 183) * target("fma4") function attribute, x86: x86 Function Attributes. ! (line 163) * target("fpmath=FPMATH") function attribute, x86: x86 Function Attributes. ! (line 225) * target("fprnd") function attribute, PowerPC: PowerPC Function Attributes. (line 47) * target("fpu=") function attribute, ARM: ARM Function Attributes. ! (line 86) * target("friz") function attribute, PowerPC: PowerPC Function Attributes. (line 140) * target("fused-madd") function attribute, x86: x86 Function Attributes. ! (line 188) * target("hard-dfp") function attribute, PowerPC: PowerPC Function Attributes. (line 53) * target("ieee-fp") function attribute, x86: x86 Function Attributes. ! (line 193) * target("inline-all-stringops") function attribute, x86: x86 Function Attributes. ! (line 198) * target("inline-stringops-dynamically") function attribute, x86: x86 Function Attributes. ! (line 202) * target("isel") function attribute, PowerPC: PowerPC Function Attributes. (line 59) * target("longcall") function attribute, PowerPC: PowerPC Function Attributes. (line 159) * target("lwp") function attribute, x86: x86 Function Attributes. ! (line 171) * target("mfcrf") function attribute, PowerPC: PowerPC Function Attributes. (line 63) * target("mfpgpr") function attribute, PowerPC: PowerPC Function Attributes. (line 70) * target("mmx") function attribute, x86: x86 Function Attributes. ! (line 122) * target("mulhw") function attribute, PowerPC: PowerPC Function Attributes. (line 77) * target("multiple") function attribute, PowerPC: PowerPC Function Attributes. --- 56891,56933 ---- * target("custom-INSN=N") function attribute, Nios II: Nios II Function Attributes. (line 16) * target("default") function attribute, x86: x86 Function Attributes. ! (line 114) * target("dlmzb") function attribute, PowerPC: PowerPC Function Attributes. (line 40) * target("fancy-math-387") function attribute, x86: x86 Function Attributes. ! (line 180) * target("fma4") function attribute, x86: x86 Function Attributes. ! (line 160) * target("fpmath=FPMATH") function attribute, x86: x86 Function Attributes. ! (line 222) * target("fprnd") function attribute, PowerPC: PowerPC Function Attributes. (line 47) * target("fpu=") function attribute, ARM: ARM Function Attributes. ! (line 85) * target("friz") function attribute, PowerPC: PowerPC Function Attributes. (line 140) * target("fused-madd") function attribute, x86: x86 Function Attributes. ! (line 185) * target("hard-dfp") function attribute, PowerPC: PowerPC Function Attributes. (line 53) * target("ieee-fp") function attribute, x86: x86 Function Attributes. ! (line 190) * target("inline-all-stringops") function attribute, x86: x86 Function Attributes. ! (line 195) * target("inline-stringops-dynamically") function attribute, x86: x86 Function Attributes. ! (line 199) * target("isel") function attribute, PowerPC: PowerPC Function Attributes. (line 59) * target("longcall") function attribute, PowerPC: PowerPC Function Attributes. (line 159) * target("lwp") function attribute, x86: x86 Function Attributes. ! (line 168) * target("mfcrf") function attribute, PowerPC: PowerPC Function Attributes. (line 63) * target("mfpgpr") function attribute, PowerPC: PowerPC Function Attributes. (line 70) * target("mmx") function attribute, x86: x86 Function Attributes. ! (line 119) * target("mulhw") function attribute, PowerPC: PowerPC Function Attributes. (line 77) * target("multiple") function attribute, PowerPC: PowerPC Function Attributes. *************** Keyword Index *** 56422,56430 **** * target("paired") function attribute, PowerPC: PowerPC Function Attributes. (line 154) * target("pclmul") function attribute, x86: x86 Function Attributes. ! (line 126) * target("popcnt") function attribute, x86: x86 Function Attributes. ! (line 130) * target("popcntb") function attribute, PowerPC: PowerPC Function Attributes. (line 95) * target("popcntd") function attribute, PowerPC: PowerPC Function Attributes. --- 56937,56945 ---- * target("paired") function attribute, PowerPC: PowerPC Function Attributes. (line 154) * target("pclmul") function attribute, x86: x86 Function Attributes. ! (line 123) * target("popcnt") function attribute, x86: x86 Function Attributes. ! (line 127) * target("popcntb") function attribute, PowerPC: PowerPC Function Attributes. (line 95) * target("popcntd") function attribute, PowerPC: PowerPC Function Attributes. *************** Keyword Index *** 56434,56475 **** * target("powerpc-gpopt") function attribute, PowerPC: PowerPC Function Attributes. (line 114) * target("recip") function attribute, x86: x86 Function Attributes. ! (line 212) * target("recip-precision") function attribute, PowerPC: PowerPC Function Attributes. (line 120) * target("sse") function attribute, x86: x86 Function Attributes. ! (line 134) * target("sse2") function attribute, x86: x86 Function Attributes. ! (line 138) * target("sse3") function attribute, x86: x86 Function Attributes. ! (line 142) * target("sse4") function attribute, x86: x86 Function Attributes. ! (line 146) * target("sse4.1") function attribute, x86: x86 Function Attributes. ! (line 151) * target("sse4.2") function attribute, x86: x86 Function Attributes. ! (line 155) * target("sse4a") function attribute, x86: x86 Function Attributes. ! (line 159) * target("ssse3") function attribute, x86: x86 Function Attributes. ! (line 175) * target("string") function attribute, PowerPC: PowerPC Function Attributes. (line 126) * target("thumb") function attribute, ARM: ARM Function Attributes. ! (line 76) * target("tune=TUNE") function attribute, PowerPC: PowerPC Function Attributes. (line 171) * target("tune=TUNE") function attribute, x86: x86 Function Attributes. ! (line 221) * target("update") function attribute, PowerPC: PowerPC Function Attributes. (line 89) * target("vsx") function attribute, PowerPC: PowerPC Function Attributes. (line 132) * target("xop") function attribute, x86: x86 Function Attributes. ! (line 167) * target-dependent options: Submodel Options. (line 6) * target_clones function attribute: Common Function Attributes. ! (line 796) * TC1: Standards. (line 13) * TC2: Standards. (line 13) * TC3: Standards. (line 13) --- 56949,56990 ---- * target("powerpc-gpopt") function attribute, PowerPC: PowerPC Function Attributes. (line 114) * target("recip") function attribute, x86: x86 Function Attributes. ! (line 209) * target("recip-precision") function attribute, PowerPC: PowerPC Function Attributes. (line 120) * target("sse") function attribute, x86: x86 Function Attributes. ! (line 131) * target("sse2") function attribute, x86: x86 Function Attributes. ! (line 135) * target("sse3") function attribute, x86: x86 Function Attributes. ! (line 139) * target("sse4") function attribute, x86: x86 Function Attributes. ! (line 143) * target("sse4.1") function attribute, x86: x86 Function Attributes. ! (line 148) * target("sse4.2") function attribute, x86: x86 Function Attributes. ! (line 152) * target("sse4a") function attribute, x86: x86 Function Attributes. ! (line 156) * target("ssse3") function attribute, x86: x86 Function Attributes. ! (line 172) * target("string") function attribute, PowerPC: PowerPC Function Attributes. (line 126) * target("thumb") function attribute, ARM: ARM Function Attributes. ! (line 75) * target("tune=TUNE") function attribute, PowerPC: PowerPC Function Attributes. (line 171) * target("tune=TUNE") function attribute, x86: x86 Function Attributes. ! (line 218) * target("update") function attribute, PowerPC: PowerPC Function Attributes. (line 89) * target("vsx") function attribute, PowerPC: PowerPC Function Attributes. (line 132) * target("xop") function attribute, x86: x86 Function Attributes. ! (line 164) * target-dependent options: Submodel Options. (line 6) * target_clones function attribute: Common Function Attributes. ! (line 800) * TC1: Standards. (line 13) * TC2: Standards. (line 13) * TC3: Standards. (line 13) *************** Keyword Index *** 56496,56509 **** * tiny type attribute, MeP: MeP Type Attributes. (line 6) * tiny variable attribute, MeP: MeP Variable Attributes. ! (line 20) * tiny_data variable attribute, H8/300: H8/300 Variable Attributes. (line 19) * TLS: Thread-Local. (line 6) * tls-dialect= function attribute, AArch64: AArch64 Function Attributes. (line 44) * tls_model variable attribute: Common Variable Attributes. ! (line 196) * TMPDIR: Environment Variables. (line 45) * toascii: Other Builtins. (line 6) --- 57011,57024 ---- * tiny type attribute, MeP: MeP Type Attributes. (line 6) * tiny variable attribute, MeP: MeP Variable Attributes. ! (line 21) * tiny_data variable attribute, H8/300: H8/300 Variable Attributes. (line 19) * TLS: Thread-Local. (line 6) * tls-dialect= function attribute, AArch64: AArch64 Function Attributes. (line 44) * tls_model variable attribute: Common Variable Attributes. ! (line 197) * TMPDIR: Environment Variables. (line 45) * toascii: Other Builtins. (line 6) *************** Keyword Index *** 56511,56523 **** * toupper: Other Builtins. (line 6) * towlower: Other Builtins. (line 6) * towupper: Other Builtins. (line 6) ! * traditional C language: C Dialect Options. (line 346) * transparent_union type attribute: Common Type Attributes. ! (line 261) ! * trapa_handler function attribute, SH: SH Function Attributes. ! (line 73) * trap_exit function attribute, SH: SH Function Attributes. (line 68) * trunc: Other Builtins. (line 6) * truncf: Other Builtins. (line 6) * truncl: Other Builtins. (line 6) --- 57026,57038 ---- * toupper: Other Builtins. (line 6) * towlower: Other Builtins. (line 6) * towupper: Other Builtins. (line 6) ! * traditional C language: C Dialect Options. (line 345) * transparent_union type attribute: Common Type Attributes. ! (line 264) * trap_exit function attribute, SH: SH Function Attributes. (line 68) + * trapa_handler function attribute, SH: SH Function Attributes. + (line 73) * trunc: Other Builtins. (line 6) * truncf: Other Builtins. (line 6) * truncl: Other Builtins. (line 6) *************** Keyword Index *** 56526,56586 **** * two-stage name lookup: Name lookup. (line 6) * type alignment: Alignment. (line 6) * type attributes: Type Attributes. (line 6) * typedef names as function parameters: Incompatibilities. (line 97) * typeof: Typeof. (line 6) - * type_info: Vague Linkage. (line 42) - * uhk fixed-suffix: Fixed-Point. (line 6) * UHK fixed-suffix: Fixed-Point. (line 6) ! * uhr fixed-suffix: Fixed-Point. (line 6) * UHR fixed-suffix: Fixed-Point. (line 6) ! * uk fixed-suffix: Fixed-Point. (line 6) * UK fixed-suffix: Fixed-Point. (line 6) ! * ulk fixed-suffix: Fixed-Point. (line 6) * ULK fixed-suffix: Fixed-Point. (line 6) * ULL integer suffix: Long Long. (line 6) - * ullk fixed-suffix: Fixed-Point. (line 6) * ULLK fixed-suffix: Fixed-Point. (line 6) ! * ullr fixed-suffix: Fixed-Point. (line 6) * ULLR fixed-suffix: Fixed-Point. (line 6) ! * ulr fixed-suffix: Fixed-Point. (line 6) * ULR fixed-suffix: Fixed-Point. (line 6) * undefined behavior: Bug Criteria. (line 17) * undefined function value: Bug Criteria. (line 17) * underscores in variables in macros: Typeof. (line 46) * union: Unnamed Fields. (line 6) * union, casting to a: Cast to Union. (line 6) * unions: Incompatibilities. (line 146) ! * unknown pragmas, warning: Warning Options. (line 850) * unresolved references and -nodefaultlibs: Link Options. (line 91) * unresolved references and -nostdlib: Link Options. (line 91) * unused function attribute: Common Function Attributes. ! (line 808) * unused label attribute: Label Attributes. (line 30) * unused type attribute: Common Type Attributes. ! (line 314) * unused variable attribute: Common Variable Attributes. ! (line 205) * upper function attribute, MSP430: MSP430 Function Attributes. (line 53) * upper variable attribute, MSP430: MSP430 Variable Attributes. (line 24) - * ur fixed-suffix: Fixed-Point. (line 6) * UR fixed-suffix: Fixed-Point. (line 6) ! * used function attribute: Common Function Attributes. ! (line 813) ! * used variable attribute: Common Variable Attributes. ! (line 210) ! * User stack pointer in interrupts on the Blackfin: Blackfin Function Attributes. ! (line 21) * use_debug_exception_return function attribute, MIPS: MIPS Function Attributes. (line 39) * use_shadow_register_set function attribute, MIPS: MIPS Function Attributes. (line 28) * V in constraint: Simple Constraints. (line 43) * V850 Options: V850 Options. (line 6) * vague linkage: Vague Linkage. (line 6) * value after longjmp: Global Register Variables. ! (line 74) * variable addressability on the M32R/D: M32R/D Variable Attributes. (line 9) * variable alignment: Alignment. (line 6) --- 57041,57101 ---- * two-stage name lookup: Name lookup. (line 6) * type alignment: Alignment. (line 6) * type attributes: Type Attributes. (line 6) + * type_info: Vague Linkage. (line 42) * typedef names as function parameters: Incompatibilities. (line 97) * typeof: Typeof. (line 6) * UHK fixed-suffix: Fixed-Point. (line 6) ! * uhk fixed-suffix: Fixed-Point. (line 6) * UHR fixed-suffix: Fixed-Point. (line 6) ! * uhr fixed-suffix: Fixed-Point. (line 6) * UK fixed-suffix: Fixed-Point. (line 6) ! * uk fixed-suffix: Fixed-Point. (line 6) * ULK fixed-suffix: Fixed-Point. (line 6) + * ulk fixed-suffix: Fixed-Point. (line 6) * ULL integer suffix: Long Long. (line 6) * ULLK fixed-suffix: Fixed-Point. (line 6) ! * ullk fixed-suffix: Fixed-Point. (line 6) * ULLR fixed-suffix: Fixed-Point. (line 6) ! * ullr fixed-suffix: Fixed-Point. (line 6) * ULR fixed-suffix: Fixed-Point. (line 6) + * ulr fixed-suffix: Fixed-Point. (line 6) * undefined behavior: Bug Criteria. (line 17) * undefined function value: Bug Criteria. (line 17) * underscores in variables in macros: Typeof. (line 46) * union: Unnamed Fields. (line 6) * union, casting to a: Cast to Union. (line 6) * unions: Incompatibilities. (line 146) ! * unknown pragmas, warning: Warning Options. (line 861) * unresolved references and -nodefaultlibs: Link Options. (line 91) * unresolved references and -nostdlib: Link Options. (line 91) * unused function attribute: Common Function Attributes. ! (line 812) * unused label attribute: Label Attributes. (line 30) * unused type attribute: Common Type Attributes. ! (line 316) * unused variable attribute: Common Variable Attributes. ! (line 206) * upper function attribute, MSP430: MSP430 Function Attributes. (line 53) * upper variable attribute, MSP430: MSP430 Variable Attributes. (line 24) * UR fixed-suffix: Fixed-Point. (line 6) ! * ur fixed-suffix: Fixed-Point. (line 6) * use_debug_exception_return function attribute, MIPS: MIPS Function Attributes. (line 39) * use_shadow_register_set function attribute, MIPS: MIPS Function Attributes. (line 28) + * used function attribute: Common Function Attributes. + (line 817) + * used variable attribute: Common Variable Attributes. + (line 211) + * User stack pointer in interrupts on the Blackfin: Blackfin Function Attributes. + (line 21) * V in constraint: Simple Constraints. (line 43) * V850 Options: V850 Options. (line 6) * vague linkage: Vague Linkage. (line 6) * value after longjmp: Global Register Variables. ! (line 76) * variable addressability on the M32R/D: M32R/D Variable Attributes. (line 9) * variable alignment: Alignment. (line 6) *************** Keyword Index *** 56598,56629 **** * vector function attribute, RX: RX Function Attributes. (line 49) * vector_size variable attribute: Common Variable Attributes. ! (line 219) * version_id function attribute, IA-64: IA-64 Function Attributes. (line 16) * vfprintf: Other Builtins. (line 6) * vfscanf: Other Builtins. (line 6) * visibility function attribute: Common Function Attributes. ! (line 823) * visibility type attribute: Common Type Attributes. ! (line 323) * visibility variable attribute: Common Variable Attributes. ! (line 242) * Visium options: Visium Options. (line 6) * VLAs: Variable Length. (line 6) * vliw function attribute, MeP: MeP Function Attributes. (line 30) * void pointers, arithmetic: Pointer Arith. (line 6) * void, size of pointer to: Pointer Arith. (line 6) - * volatile access: Volatiles. (line 6) * volatile access <1>: C++ Volatiles. (line 6) * volatile applied to function: Function Attributes. (line 6) * volatile asm: Extended Asm. (line 109) - * volatile read: Volatiles. (line 6) * volatile read <1>: C++ Volatiles. (line 6) ! * volatile write: Volatiles. (line 6) * volatile write <1>: C++ Volatiles. (line 6) * vprintf: Other Builtins. (line 6) * vscanf: Other Builtins. (line 6) * vsnprintf: Other Builtins. (line 6) --- 57113,57144 ---- * vector function attribute, RX: RX Function Attributes. (line 49) * vector_size variable attribute: Common Variable Attributes. ! (line 220) * version_id function attribute, IA-64: IA-64 Function Attributes. (line 16) * vfprintf: Other Builtins. (line 6) * vfscanf: Other Builtins. (line 6) * visibility function attribute: Common Function Attributes. ! (line 827) * visibility type attribute: Common Type Attributes. ! (line 325) * visibility variable attribute: Common Variable Attributes. ! (line 244) * Visium options: Visium Options. (line 6) * VLAs: Variable Length. (line 6) * vliw function attribute, MeP: MeP Function Attributes. (line 30) * void pointers, arithmetic: Pointer Arith. (line 6) * void, size of pointer to: Pointer Arith. (line 6) * volatile access <1>: C++ Volatiles. (line 6) + * volatile access: Volatiles. (line 6) * volatile applied to function: Function Attributes. (line 6) * volatile asm: Extended Asm. (line 109) * volatile read <1>: C++ Volatiles. (line 6) ! * volatile read: Volatiles. (line 6) * volatile write <1>: C++ Volatiles. (line 6) + * volatile write: Volatiles. (line 6) * vprintf: Other Builtins. (line 6) * vscanf: Other Builtins. (line 6) * vsnprintf: Other Builtins. (line 6) *************** Keyword Index *** 56631,56670 **** * vsscanf: Other Builtins. (line 6) * vtable: Vague Linkage. (line 27) * VxWorks Options: VxWorks Options. (line 6) - * w floating point suffix: Floating Types. (line 6) * W floating point suffix: Floating Types. (line 6) * wakeup function attribute, MSP430: MSP430 Function Attributes. (line 45) * warm function attribute, NDS32: NDS32 Function Attributes. ! (line 52) * warning for comparison of signed and unsigned values: Warning Options. ! (line 1482) * warning for overloaded virtual function: C++ Dialect Options. ! (line 664) * warning for reordering of member initializers: C++ Dialect Options. ! (line 582) ! * warning for unknown pragmas: Warning Options. (line 850) * warning function attribute: Common Function Attributes. (line 197) * warning GCC_COLORS capability: Diagnostic Message Formatting Options. (line 72) * warning messages: Warning Options. (line 6) ! * warnings from system headers: Warning Options. (line 1081) * warnings vs errors: Warnings and Errors. (line 6) - * warn_unused type attribute: C++ Attributes. (line 79) - * warn_unused_result function attribute: Common Function Attributes. - (line 923) * weak function attribute: Common Function Attributes. ! (line 940) * weak variable attribute: Common Variable Attributes. ! (line 247) * weakref function attribute: Common Function Attributes. ! (line 949) * whitespace: Incompatibilities. (line 112) * Windows Options for x86: x86 Windows Options. (line 6) ! * X in constraint: Simple Constraints. (line 122) * X3.159-1989: Standards. (line 13) * x86 named address spaces: Named Address Spaces. (line 168) --- 57146,57185 ---- * vsscanf: Other Builtins. (line 6) * vtable: Vague Linkage. (line 27) * VxWorks Options: VxWorks Options. (line 6) * W floating point suffix: Floating Types. (line 6) + * w floating point suffix: Floating Types. (line 6) * wakeup function attribute, MSP430: MSP430 Function Attributes. (line 45) * warm function attribute, NDS32: NDS32 Function Attributes. ! (line 57) ! * warn_unused type attribute: C++ Attributes. (line 77) ! * warn_unused_result function attribute: Common Function Attributes. ! (line 928) * warning for comparison of signed and unsigned values: Warning Options. ! (line 1501) * warning for overloaded virtual function: C++ Dialect Options. ! (line 670) * warning for reordering of member initializers: C++ Dialect Options. ! (line 586) ! * warning for unknown pragmas: Warning Options. (line 861) * warning function attribute: Common Function Attributes. (line 197) * warning GCC_COLORS capability: Diagnostic Message Formatting Options. (line 72) * warning messages: Warning Options. (line 6) ! * warnings from system headers: Warning Options. (line 1093) * warnings vs errors: Warnings and Errors. (line 6) * weak function attribute: Common Function Attributes. ! (line 945) * weak variable attribute: Common Variable Attributes. ! (line 249) * weakref function attribute: Common Function Attributes. ! (line 954) * whitespace: Incompatibilities. (line 112) * Windows Options for x86: x86 Windows Options. (line 6) ! * X in constraint: Simple Constraints. (line 124) * X3.159-1989: Standards. (line 13) * x86 named address spaces: Named Address Spaces. (line 168) *************** Keyword Index *** 56691,57085 ****  Tag Table: ! Node: Top1969 ! Node: G++ and GCC3794 ! Node: Standards5851 ! Node: Invoking GCC18667 ! Node: Option Summary22868 ! Node: Overall Options69108 ! Node: Invoking G++83577 ! Node: C Dialect Options85100 ! Node: C++ Dialect Options102998 ! Node: Objective-C and Objective-C++ Dialect Options135722 ! Node: Diagnostic Message Formatting Options146966 ! Node: Warning Options151799 ! Node: Debugging Options239497 ! Node: Optimize Options253759 ! Ref: Type-punning314841 ! Node: Instrumentation Options401480 ! Node: Preprocessor Options433659 ! Ref: Wtrigraphs438449 ! Ref: dashMF443199 ! Ref: fdollars-in-identifiers454080 ! Node: Assembler Options464281 ! Node: Link Options464972 ! Ref: Link Options-Footnote-1478550 ! Node: Directory Options478886 ! Node: Code Gen Options485269 ! Node: Developer Options510112 ! Node: Submodel Options551133 ! Node: AArch64 Options552848 ! Ref: aarch64-feature-modifiers560682 ! Node: Adapteva Epiphany Options561560 ! Node: ARC Options567507 ! Node: ARM Options584619 ! Node: AVR Options602903 ! Node: Blackfin Options624317 ! Node: C6X Options632335 ! Node: CRIS Options633878 ! Node: CR16 Options637617 ! Node: Darwin Options638528 ! Node: DEC Alpha Options645968 ! Node: FR30 Options657584 ! Node: FT32 Options658149 ! Node: FRV Options658874 ! Node: GNU/Linux Options665638 ! Node: H8/300 Options667019 ! Node: HPPA Options668471 ! Node: IA-64 Options677661 ! Node: LM32 Options685789 ! Node: M32C Options686312 ! Node: M32R/D Options687585 ! Node: M680x0 Options691130 ! Node: MCore Options705165 ! Node: MeP Options706667 ! Node: MicroBlaze Options710627 ! Node: MIPS Options713429 ! Node: MMIX Options748281 ! Node: MN10300 Options750758 ! Node: Moxie Options753299 ! Node: MSP430 Options753786 ! Node: NDS32 Options758490 ! Node: Nios II Options760384 ! Node: Nvidia PTX Options771317 ! Node: PDP-11 Options771840 ! Node: picoChip Options773537 ! Node: PowerPC Options775675 ! Node: RL78 Options775896 ! Node: RS/6000 and PowerPC Options778991 ! Node: RX Options821875 ! Node: S/390 and zSeries Options830477 ! Node: Score Options840654 ! Node: SH Options841503 ! Node: Solaris 2 Options856644 ! Node: SPARC Options858166 ! Node: SPU Options872287 ! Node: System V Options877226 ! Node: TILE-Gx Options878052 ! Node: TILEPro Options879070 ! Node: V850 Options879574 ! Node: VAX Options886261 ! Node: Visium Options886799 ! Node: VMS Options889107 ! Node: VxWorks Options889923 ! Node: x86 Options891075 ! Node: x86 Windows Options941088 ! Node: Xstormy16 Options943893 ! Node: Xtensa Options944187 ! Node: zSeries Options949336 ! Node: Spec Files949532 ! Node: Environment Variables971355 ! Node: Precompiled Headers979352 ! Node: C Implementation985355 ! Node: Translation implementation987045 ! Node: Environment implementation987636 ! Node: Identifiers implementation988190 ! Node: Characters implementation989276 ! Node: Integers implementation992926 ! Node: Floating point implementation994975 ! Node: Arrays and pointers implementation998038 ! Ref: Arrays and pointers implementation-Footnote-1999498 ! Node: Hints implementation999624 ! Node: Structures unions enumerations and bit-fields implementation1001119 ! Node: Qualifiers implementation1003343 ! Node: Declarators implementation1005123 ! Node: Statements implementation1005464 ! Node: Preprocessing directives implementation1005790 ! Node: Library functions implementation1008111 ! Node: Architecture implementation1008760 ! Node: Locale-specific behavior implementation1010405 ! Node: C++ Implementation1010710 ! Node: Conditionally-supported behavior1011993 ! Node: Exception handling1012610 ! Node: C Extensions1013018 ! Node: Statement Exprs1018238 ! Node: Local Labels1022715 ! Node: Labels as Values1025688 ! Ref: Labels as Values-Footnote-11028215 ! Node: Nested Functions1028400 ! Node: Constructing Calls1032358 ! Node: Typeof1037075 ! Node: Conditionals1041004 ! Node: __int1281041893 ! Node: Long Long1042418 ! Node: Complex1043894 ! Node: Floating Types1046478 ! Node: Half-Precision1048753 ! Node: Decimal Float1050938 ! Node: Hex Floats1052792 ! Node: Fixed-Point1053829 ! Node: Named Address Spaces1057087 ! Ref: AVR Named Address Spaces1057773 ! Node: Zero Length1063897 ! Node: Empty Structures1066937 ! Node: Variable Length1067343 ! Node: Variadic Macros1070061 ! Node: Escaped Newlines1072439 ! Node: Subscripting1073300 ! Node: Pointer Arith1074025 ! Node: Pointers to Arrays1074599 ! Node: Initializers1075344 ! Node: Compound Literals1075845 ! Node: Designated Inits1079191 ! Node: Case Ranges1082929 ! Node: Cast to Union1083610 ! Node: Mixed Declarations1084700 ! Node: Function Attributes1085210 ! Node: Common Function Attributes1088281 ! Node: AArch64 Function Attributes1134402 ! Node: ARC Function Attributes1139550 ! Node: ARM Function Attributes1141242 ! Node: AVR Function Attributes1144903 ! Node: Blackfin Function Attributes1148378 ! Node: CR16 Function Attributes1150876 ! Node: Epiphany Function Attributes1151403 ! Node: H8/300 Function Attributes1154155 ! Node: IA-64 Function Attributes1155351 ! Node: M32C Function Attributes1156393 ! Node: M32R/D Function Attributes1158731 ! Node: m68k Function Attributes1160205 ! Node: MCORE Function Attributes1161149 ! Node: MeP Function Attributes1161960 ! Node: MicroBlaze Function Attributes1163261 ! Node: Microsoft Windows Function Attributes1164768 ! Node: MIPS Function Attributes1169337 ! Node: MSP430 Function Attributes1174900 ! Node: NDS32 Function Attributes1178748 ! Node: Nios II Function Attributes1181172 ! Node: Nvidia PTX Function Attributes1182469 ! Node: PowerPC Function Attributes1183084 ! Node: RL78 Function Attributes1190137 ! Node: RX Function Attributes1191377 ! Node: S/390 Function Attributes1193916 ! Node: SH Function Attributes1195744 ! Node: SPU Function Attributes1199165 ! Node: Symbian OS Function Attributes1199973 ! Node: V850 Function Attributes1200310 ! Node: Visium Function Attributes1200855 ! Node: x86 Function Attributes1201383 ! Node: Xstormy16 Function Attributes1210194 ! Node: Variable Attributes1210701 ! Node: Common Variable Attributes1212085 ! Node: AVR Variable Attributes1223079 ! Node: Blackfin Variable Attributes1225717 ! Node: H8/300 Variable Attributes1226575 ! Node: IA-64 Variable Attributes1227648 ! Node: M32R/D Variable Attributes1228399 ! Node: MeP Variable Attributes1229182 ! Node: Microsoft Windows Variable Attributes1231275 ! Node: MSP430 Variable Attributes1233728 ! Node: PowerPC Variable Attributes1234924 ! Node: RL78 Variable Attributes1235477 ! Node: SPU Variable Attributes1235895 ! Node: V850 Variable Attributes1236260 ! Node: x86 Variable Attributes1236892 ! Node: Xstormy16 Variable Attributes1237948 ! Node: Type Attributes1238518 ! Node: Common Type Attributes1239795 ! Node: ARM Type Attributes1255271 ! Node: MeP Type Attributes1256056 ! Node: PowerPC Type Attributes1256458 ! Node: SPU Type Attributes1257447 ! Node: x86 Type Attributes1257866 ! Node: Label Attributes1258854 ! Node: Enumerator Attributes1260744 ! Node: Attribute Syntax1262016 ! Node: Function Prototypes1273013 ! Node: C++ Comments1274793 ! Node: Dollar Signs1275312 ! Node: Character Escapes1275777 ! Node: Alignment1276061 ! Node: Inline1277433 ! Node: Volatiles1282234 ! Node: Using Assembly Language with C1285133 ! Node: Basic Asm1286370 ! Node: Extended Asm1291369 ! Ref: Volatile1295173 ! Ref: AssemblerTemplate1299258 ! Ref: OutputOperands1303496 ! Ref: FlagOutputOperands1310425 ! Ref: InputOperands1312454 ! Ref: Clobbers1316700 ! Ref: GotoLabels1320016 ! Ref: x86Operandmodifiers1322151 ! Ref: x86floatingpointasmoperands1324322 ! Node: Constraints1327651 ! Node: Simple Constraints1328757 ! Node: Multi-Alternative1336071 ! Node: Modifiers1337746 ! Node: Machine Constraints1340544 ! Node: Asm Labels1400023 ! Node: Explicit Register Variables1401643 ! Ref: Explicit Reg Vars1401857 ! Node: Global Register Variables1402466 ! Ref: Global Reg Vars1402674 ! Node: Local Register Variables1406526 ! Ref: Local Reg Vars1406746 ! Node: Size of an asm1410053 ! Node: Alternate Keywords1411307 ! Node: Incomplete Enums1412806 ! Node: Function Names1413562 ! Node: Return Address1415165 ! Node: Vector Extensions1419106 ! Node: Offsetof1426401 ! Node: __sync Builtins1427234 ! Node: __atomic Builtins1433675 ! Node: Integer Overflow Builtins1447156 ! Node: x86 specific memory model extensions for transactional memory1451341 ! Node: Object Size Checking1452612 ! Node: Pointer Bounds Checker builtins1458118 ! Node: Cilk Plus Builtins1464124 ! Node: Other Builtins1465029 ! Node: Target Builtins1499570 ! Node: AArch64 Built-in Functions1501062 ! Node: Alpha Built-in Functions1501517 ! Node: Altera Nios II Built-in Functions1504565 ! Node: ARC Built-in Functions1508934 ! Node: ARC SIMD Built-in Functions1514146 ! Node: ARM iWMMXt Built-in Functions1523042 ! Node: ARM C Language Extensions (ACLE)1530038 ! Node: ARM Floating Point Status and Control Intrinsics1531315 ! Node: AVR Built-in Functions1531791 ! Node: Blackfin Built-in Functions1534898 ! Node: FR-V Built-in Functions1535517 ! Node: Argument Types1536385 ! Node: Directly-mapped Integer Functions1538139 ! Node: Directly-mapped Media Functions1539223 ! Node: Raw read/write Functions1547429 ! Node: Other Built-in Functions1548337 ! Node: MIPS DSP Built-in Functions1549523 ! Node: MIPS Paired-Single Support1562020 ! Node: MIPS Loongson Built-in Functions1563519 ! Node: Paired-Single Arithmetic1570034 ! Node: Paired-Single Built-in Functions1570982 ! Node: MIPS-3D Built-in Functions1573649 ! Node: Other MIPS Built-in Functions1579027 ! Node: MSP430 Built-in Functions1580032 ! Node: NDS32 Built-in Functions1581433 ! Node: picoChip Built-in Functions1582726 ! Node: PowerPC Built-in Functions1584069 ! Node: PowerPC AltiVec/VSX Built-in Functions1596863 ! Node: PowerPC Hardware Transactional Memory Built-in Functions1743396 ! Node: RX Built-in Functions1751887 ! Node: S/390 System z Built-in Functions1755920 ! Node: SH Built-in Functions1761150 ! Node: SPARC VIS Built-in Functions1762878 ! Node: SPU Built-in Functions1769803 ! Node: TI C6X Built-in Functions1771520 ! Node: TILE-Gx Built-in Functions1772545 ! Node: TILEPro Built-in Functions1773664 ! Node: x86 Built-in Functions1774764 ! Node: x86 transactional memory intrinsics1834731 ! Node: Target Format Checks1837951 ! Node: Solaris Format Checks1838383 ! Node: Darwin Format Checks1838809 ! Node: Pragmas1839627 ! Node: AArch64 Pragmas1840400 ! Node: ARM Pragmas1840857 ! Node: M32C Pragmas1841484 ! Node: MeP Pragmas1842556 ! Node: RS/6000 and PowerPC Pragmas1844624 ! Node: S/390 Pragmas1845364 ! Node: Darwin Pragmas1845930 ! Node: Solaris Pragmas1846983 ! Node: Symbol-Renaming Pragmas1848147 ! Node: Structure-Layout Pragmas1849763 ! Node: Weak Pragmas1852043 ! Node: Diagnostic Pragmas1852778 ! Node: Visibility Pragmas1855887 ! Node: Push/Pop Macro Pragmas1856572 ! Node: Function Specific Option Pragmas1857545 ! Node: Loop-Specific Pragmas1859393 ! Node: Unnamed Fields1860486 ! Node: Thread-Local1862683 ! Node: C99 Thread-Local Edits1864788 ! Node: C++98 Thread-Local Edits1866786 ! Node: Binary constants1870231 ! Node: C++ Extensions1870902 ! Node: C++ Volatiles1872680 ! Node: Restricted Pointers1875028 ! Node: Vague Linkage1876619 ! Node: C++ Interface1880242 ! Ref: C++ Interface-Footnote-11884039 ! Node: Template Instantiation1884177 ! Node: Bound member functions1891660 ! Node: C++ Attributes1893192 ! Node: Function Multiversioning1897636 ! Node: Namespace Association1899453 ! Node: Type Traits1900833 ! Node: C++ Concepts1907315 ! Node: Java Exceptions1908810 ! Node: Deprecated Features1910201 ! Node: Backwards Compatibility1913168 ! Node: Objective-C1914515 ! Node: GNU Objective-C runtime API1915122 ! Node: Modern GNU Objective-C runtime API1916129 ! Node: Traditional GNU Objective-C runtime API1918565 ! Node: Executing code before main1919292 ! Node: What you can and what you cannot do in +load1922036 ! Node: Type encoding1924406 ! Node: Legacy type encoding1929433 ! Node: @encode1930523 ! Node: Method signatures1931068 ! Node: Garbage Collection1933060 ! Node: Constant string objects1935750 ! Node: compatibility_alias1938259 ! Node: Exceptions1938984 ! Node: Synchronization1941694 ! Node: Fast enumeration1942878 ! Node: Using fast enumeration1943190 ! Node: c99-like fast enumeration syntax1944401 ! Node: Fast enumeration details1945104 ! Node: Fast enumeration protocol1947444 ! Node: Messaging with the GNU Objective-C runtime1950596 ! Node: Dynamically registering methods1951968 ! Node: Forwarding hook1953659 ! Node: Compatibility1956699 ! Node: Gcov1963255 ! Node: Gcov Intro1963790 ! Node: Invoking Gcov1966508 ! Node: Gcov and Optimization1980748 ! Node: Gcov Data Files1983750 ! Node: Cross-profiling1985145 ! Node: Gcov-tool1986999 ! Node: Gcov-tool Intro1987422 ! Node: Invoking Gcov-tool1989392 ! Node: Trouble1991971 ! Node: Actual Bugs1993388 ! Node: Interoperation1993835 ! Node: Incompatibilities2000726 ! Node: Fixed Headers2008878 ! Node: Standard Libraries2010536 ! Node: Disappointments2011908 ! Node: C++ Misunderstandings2016267 ! Node: Static Definitions2017078 ! Node: Name lookup2018131 ! Ref: Name lookup-Footnote-12022911 ! Node: Temporaries2023100 ! Node: Copy Assignment2025076 ! Node: Non-bugs2026883 ! Node: Warnings and Errors2037389 ! Node: Bugs2039151 ! Node: Bug Criteria2039618 ! Node: Bug Reporting2041828 ! Node: Service2042049 ! Node: Contributing2042868 ! Node: Funding2043608 ! Node: GNU Project2046098 ! Node: Copying2046744 ! Node: GNU Free Documentation License2084253 ! Node: Contributors2109371 ! Node: Option Index2148177 ! Node: Keyword Index2388424  End Tag Table --- 57206,57603 ----  Tag Table: ! Node: Top2110 ! Node: G++ and GCC4015 ! Node: Standards6084 ! Node: Invoking GCC18896 ! Node: Option Summary23098 ! Node: Overall Options69210 ! Node: Invoking G++83730 ! Node: C Dialect Options85253 ! Node: C++ Dialect Options103162 ! Node: Objective-C and Objective-C++ Dialect Options135921 ! Node: Diagnostic Message Formatting Options147166 ! Node: Warning Options151993 ! Node: Debugging Options239858 ! Node: Optimize Options254120 ! Ref: Type-punning315199 ! Node: Instrumentation Options401734 ! Node: Preprocessor Options433928 ! Ref: Wtrigraphs438717 ! Ref: dashMF443465 ! Ref: fdollars-in-identifiers454329 ! Node: Assembler Options464572 ! Node: Link Options465264 ! Ref: Link Options-Footnote-1478857 ! Node: Directory Options479191 ! Node: Code Gen Options485582 ! Node: Developer Options510446 ! Node: Submodel Options551352 ! Node: AArch64 Options553067 ! Ref: aarch64-feature-modifiers560900 ! Node: Adapteva Epiphany Options561783 ! Node: ARC Options567733 ! Node: ARM Options584822 ! Node: AVR Options603107 ! Node: Blackfin Options624497 ! Node: C6X Options632512 ! Node: CRIS Options634055 ! Node: CR16 Options637799 ! Node: Darwin Options638706 ! Node: DEC Alpha Options646147 ! Node: FR30 Options657735 ! Node: FT32 Options658301 ! Node: FRV Options659027 ! Node: GNU/Linux Options665746 ! Node: H8/300 Options667128 ! Node: HPPA Options668578 ! Node: IA-64 Options677767 ! Node: LM32 Options685893 ! Node: M32C Options686417 ! Node: M32R/D Options687691 ! Node: M680x0 Options691237 ! Node: MCore Options705283 ! Node: MeP Options706786 ! Node: MicroBlaze Options710746 ! Node: MIPS Options713542 ! Node: MMIX Options748454 ! Node: MN10300 Options750936 ! Node: Moxie Options753479 ! Node: MSP430 Options753967 ! Node: NDS32 Options758677 ! Node: Nios II Options760571 ! Node: Nvidia PTX Options771492 ! Node: PDP-11 Options772016 ! Node: picoChip Options773713 ! Node: PowerPC Options775854 ! Node: RL78 Options776075 ! Node: RS/6000 and PowerPC Options779171 ! Node: RX Options821060 ! Node: S/390 and zSeries Options829663 ! Node: Score Options839851 ! Node: SH Options840693 ! Node: Solaris 2 Options855845 ! Node: SPARC Options857373 ! Node: SPU Options871495 ! Node: System V Options876432 ! Node: TILE-Gx Options877258 ! Node: TILEPro Options878276 ! Node: V850 Options878780 ! Node: VAX Options885472 ! Node: Visium Options886010 ! Node: VMS Options888318 ! Node: VxWorks Options889132 ! Node: x86 Options890284 ! Node: x86 Windows Options940253 ! Node: Xstormy16 Options943061 ! Node: Xtensa Options943355 ! Node: zSeries Options948504 ! Node: Spec Files948700 ! Node: Environment Variables970578 ! Node: Precompiled Headers978573 ! Node: C Implementation984581 ! Node: Translation implementation986270 ! Node: Environment implementation986862 ! Node: Identifiers implementation987417 ! Node: Characters implementation988504 ! Node: Integers implementation992155 ! Node: Floating point implementation994205 ! Node: Arrays and pointers implementation997270 ! Ref: Arrays and pointers implementation-Footnote-1998729 ! Node: Hints implementation998853 ! Node: Structures unions enumerations and bit-fields implementation1000350 ! Node: Qualifiers implementation1002575 ! Node: Declarators implementation1004355 ! Node: Statements implementation1004697 ! Node: Preprocessing directives implementation1005024 ! Node: Library functions implementation1007346 ! Node: Architecture implementation1007996 ! Node: Locale-specific behavior implementation1009638 ! Node: C++ Implementation1009943 ! Node: Conditionally-supported behavior1011225 ! Node: Exception handling1011843 ! Node: C Extensions1012252 ! Node: Statement Exprs1017474 ! Node: Local Labels1021950 ! Node: Labels as Values1024923 ! Ref: Labels as Values-Footnote-11027448 ! Node: Nested Functions1027631 ! Node: Constructing Calls1031589 ! Node: Typeof1036307 ! Node: Conditionals1040235 ! Node: __int1281041125 ! Node: Long Long1041649 ! Node: Complex1043125 ! Node: Floating Types1045710 ! Node: Half-Precision1047985 ! Node: Decimal Float1050167 ! Node: Hex Floats1052020 ! Node: Fixed-Point1053056 ! Node: Named Address Spaces1056336 ! Ref: AVR Named Address Spaces1057022 ! Node: Zero Length1063144 ! Node: Empty Structures1066183 ! Node: Variable Length1066589 ! Node: Variadic Macros1069307 ! Node: Escaped Newlines1071685 ! Node: Subscripting1072546 ! Node: Pointer Arith1073272 ! Node: Pointers to Arrays1073846 ! Node: Initializers1074590 ! Node: Compound Literals1075091 ! Node: Designated Inits1078438 ! Node: Case Ranges1082176 ! Node: Cast to Union1082857 ! Node: Mixed Declarations1083948 ! Node: Function Attributes1084458 ! Node: Common Function Attributes1087529 ! Node: AArch64 Function Attributes1133668 ! Node: ARC Function Attributes1138817 ! Node: ARM Function Attributes1140509 ! Node: AVR Function Attributes1144167 ! Node: Blackfin Function Attributes1147638 ! Node: CR16 Function Attributes1150134 ! Node: Epiphany Function Attributes1150661 ! Node: H8/300 Function Attributes1153412 ! Node: IA-64 Function Attributes1154608 ! Node: M32C Function Attributes1155650 ! Node: M32R/D Function Attributes1157985 ! Node: m68k Function Attributes1159458 ! Node: MCORE Function Attributes1160402 ! Node: MeP Function Attributes1161210 ! Node: MicroBlaze Function Attributes1162511 ! Node: Microsoft Windows Function Attributes1164017 ! Node: MIPS Function Attributes1168600 ! Node: MSP430 Function Attributes1174157 ! Node: NDS32 Function Attributes1178002 ! Node: Nios II Function Attributes1180421 ! Node: Nvidia PTX Function Attributes1181715 ! Node: PowerPC Function Attributes1182330 ! Node: RL78 Function Attributes1189337 ! Node: RX Function Attributes1190574 ! Node: S/390 Function Attributes1193110 ! Node: SH Function Attributes1194929 ! Node: SPU Function Attributes1198353 ! Node: Symbian OS Function Attributes1199158 ! Node: V850 Function Attributes1199495 ! Node: Visium Function Attributes1200040 ! Node: x86 Function Attributes1200568 ! Node: Xstormy16 Function Attributes1209323 ! Node: Variable Attributes1209830 ! Node: Common Variable Attributes1211214 ! Node: AVR Variable Attributes1222219 ! Node: Blackfin Variable Attributes1224856 ! Node: H8/300 Variable Attributes1225715 ! Node: IA-64 Variable Attributes1226789 ! Node: M32R/D Variable Attributes1227540 ! Node: MeP Variable Attributes1228323 ! Node: Microsoft Windows Variable Attributes1230426 ! Node: MSP430 Variable Attributes1232885 ! Node: PowerPC Variable Attributes1234081 ! Node: RL78 Variable Attributes1234634 ! Node: SPU Variable Attributes1235052 ! Node: V850 Variable Attributes1235417 ! Node: x86 Variable Attributes1236049 ! Node: Xstormy16 Variable Attributes1237105 ! Node: Type Attributes1237680 ! Node: Common Type Attributes1238956 ! Node: ARM Type Attributes1254440 ! Node: MeP Type Attributes1255224 ! Node: PowerPC Type Attributes1255626 ! Node: SPU Type Attributes1256615 ! Node: x86 Type Attributes1257034 ! Node: Label Attributes1258022 ! Node: Enumerator Attributes1259913 ! Node: Attribute Syntax1261186 ! Node: Function Prototypes1272186 ! Node: C++ Comments1273967 ! Node: Dollar Signs1274486 ! Node: Character Escapes1274951 ! Node: Alignment1275235 ! Node: Inline1276607 ! Node: Volatiles1281408 ! Node: Using Assembly Language with C1284308 ! Node: Basic Asm1285545 ! Node: Extended Asm1290535 ! Ref: Volatile1294332 ! Ref: AssemblerTemplate1298404 ! Ref: OutputOperands1302629 ! Ref: FlagOutputOperands1309541 ! Ref: InputOperands1311556 ! Ref: Clobbers1315791 ! Ref: GotoLabels1319097 ! Ref: x86Operandmodifiers1321230 ! Ref: x86floatingpointasmoperands1323474 ! Node: Constraints1326804 ! Node: Simple Constraints1327910 ! Node: Multi-Alternative1335235 ! Node: Modifiers1336910 ! Node: Machine Constraints1339707 ! Node: Asm Labels1398683 ! Node: Explicit Register Variables1400303 ! Ref: Explicit Reg Vars1400517 ! Node: Global Register Variables1401126 ! Ref: Global Reg Vars1401334 ! Node: Local Register Variables1405176 ! Ref: Local Reg Vars1405396 ! Node: Size of an asm1408706 ! Node: Alternate Keywords1409961 ! Node: Incomplete Enums1411460 ! Node: Function Names1412216 ! Node: Return Address1413819 ! Node: Vector Extensions1417760 ! Node: Offsetof1425045 ! Node: __sync Builtins1425886 ! Node: __atomic Builtins1432331 ! Node: Integer Overflow Builtins1445821 ! Node: x86 specific memory model extensions for transactional memory1450011 ! Node: Object Size Checking1451282 ! Node: Pointer Bounds Checker builtins1456788 ! Node: Cilk Plus Builtins1462794 ! Node: Other Builtins1463711 ! Node: Target Builtins1498276 ! Node: AArch64 Built-in Functions1499768 ! Node: Alpha Built-in Functions1500223 ! Node: Altera Nios II Built-in Functions1503271 ! Node: ARC Built-in Functions1507638 ! Node: ARC SIMD Built-in Functions1512849 ! Node: ARM iWMMXt Built-in Functions1521745 ! Node: ARM C Language Extensions (ACLE)1528741 ! Node: ARM Floating Point Status and Control Intrinsics1530018 ! Node: AVR Built-in Functions1530494 ! Node: Blackfin Built-in Functions1533593 ! Node: FR-V Built-in Functions1534212 ! Node: Argument Types1535078 ! Node: Directly-mapped Integer Functions1536832 ! Node: Directly-mapped Media Functions1537916 ! Node: Raw read/write Functions1544950 ! Node: Other Built-in Functions1545864 ! Node: MIPS DSP Built-in Functions1547050 ! Node: MIPS Paired-Single Support1559548 ! Node: MIPS Loongson Built-in Functions1561047 ! Node: Paired-Single Arithmetic1567567 ! Node: Paired-Single Built-in Functions1568515 ! Node: MIPS-3D Built-in Functions1571182 ! Node: Other MIPS Built-in Functions1576559 ! Node: MSP430 Built-in Functions1577564 ! Node: NDS32 Built-in Functions1578965 ! Node: picoChip Built-in Functions1580258 ! Node: PowerPC Built-in Functions1581602 ! Node: PowerPC AltiVec/VSX Built-in Functions1594393 ! Node: PowerPC Hardware Transactional Memory Built-in Functions1740916 ! Node: RX Built-in Functions1749407 ! Node: S/390 System z Built-in Functions1753440 ! Node: SH Built-in Functions1758675 ! Node: SPARC VIS Built-in Functions1760403 ! Node: SPU Built-in Functions1767329 ! Node: TI C6X Built-in Functions1769045 ! Node: TILE-Gx Built-in Functions1770069 ! Node: TILEPro Built-in Functions1771186 ! Node: x86 Built-in Functions1772284 ! Node: x86 transactional memory intrinsics1832249 ! Node: Target Format Checks1835469 ! Node: Solaris Format Checks1835901 ! Node: Darwin Format Checks1836327 ! Node: Pragmas1837145 ! Node: AArch64 Pragmas1837918 ! Node: ARM Pragmas1838375 ! Node: M32C Pragmas1839002 ! Node: MeP Pragmas1840076 ! Node: RS/6000 and PowerPC Pragmas1842145 ! Node: S/390 Pragmas1842885 ! Node: Darwin Pragmas1843451 ! Node: Solaris Pragmas1844504 ! Node: Symbol-Renaming Pragmas1845665 ! Node: Structure-Layout Pragmas1847278 ! Node: Weak Pragmas1849565 ! Node: Diagnostic Pragmas1850300 ! Node: Visibility Pragmas1853407 ! Node: Push/Pop Macro Pragmas1854092 ! Node: Function Specific Option Pragmas1855064 ! Node: Loop-Specific Pragmas1856909 ! Node: Unnamed Fields1857999 ! Node: Thread-Local1860197 ! Node: C99 Thread-Local Edits1862302 ! Node: C++98 Thread-Local Edits1864314 ! Node: Binary constants1867758 ! Node: C++ Extensions1868429 ! Node: C++ Volatiles1870207 ! Node: Restricted Pointers1872555 ! Node: Vague Linkage1874146 ! Node: C++ Interface1877770 ! Ref: C++ Interface-Footnote-11881563 ! Node: Template Instantiation1881699 ! Node: Bound member functions1889183 ! Node: C++ Attributes1890715 ! Node: Function Multiversioning1895157 ! Node: Namespace Association1896972 ! Node: Type Traits1898352 ! Node: C++ Concepts1904839 ! Node: Java Exceptions1906330 ! Node: Deprecated Features1907721 ! Node: Backwards Compatibility1910686 ! Node: Objective-C1912038 ! Node: GNU Objective-C runtime API1912647 ! Node: Modern GNU Objective-C runtime API1913654 ! Node: Traditional GNU Objective-C runtime API1916091 ! Node: Executing code before main1916819 ! Node: What you can and what you cannot do in +load1919561 ! Node: Type encoding1921933 ! Node: Legacy type encoding1927009 ! Node: @encode1928100 ! Node: Method signatures1928645 ! Node: Garbage Collection1930640 ! Node: Constant string objects1933329 ! Node: compatibility_alias1935837 ! Node: Exceptions1936563 ! Node: Synchronization1939274 ! Node: Fast enumeration1940458 ! Node: Using fast enumeration1940770 ! Node: c99-like fast enumeration syntax1941981 ! Node: Fast enumeration details1942684 ! Node: Fast enumeration protocol1945025 ! Node: Messaging with the GNU Objective-C runtime1948177 ! Node: Dynamically registering methods1949548 ! Node: Forwarding hook1951239 ! Node: Compatibility1954279 ! Node: Gcov1960846 ! Node: Gcov Intro1961381 ! Node: Invoking Gcov1964099 ! Node: Gcov and Optimization1979028 ! Node: Gcov Data Files1982028 ! Node: Cross-profiling1983423 ! Node: Gcov-tool1985274 ! Node: Gcov-tool Intro1985699 ! Node: Invoking Gcov-tool1987660 ! Node: Gcov-dump1990206 ! Node: Gcov-dump Intro1990528 ! Node: Invoking Gcov-dump1990795 ! Node: Trouble1991464 ! Node: Actual Bugs1992881 ! Node: Interoperation1993328 ! Node: Incompatibilities2000220 ! Node: Fixed Headers2008371 ! Node: Standard Libraries2010034 ! Node: Disappointments2011406 ! Node: C++ Misunderstandings2015764 ! Node: Static Definitions2016575 ! Node: Name lookup2017628 ! Ref: Name lookup-Footnote-12022406 ! Node: Temporaries2022593 ! Node: Copy Assignment2024569 ! Node: Non-bugs2026376 ! Node: Warnings and Errors2036883 ! Node: Bugs2038645 ! Node: Bug Criteria2039112 ! Node: Bug Reporting2041322 ! Node: Service2041543 ! Node: Contributing2042362 ! Node: Funding2043102 ! Node: GNU Project2045591 ! Node: Copying2046237 ! Node: GNU Free Documentation License2083765 ! Node: Contributors2108902 ! Node: Option Index2147711 ! Node: Keyword Index2385576  End Tag Table diff -Nrcpad gcc-6.3.0/gcc/doc/gcc.texi gcc-6.4.0/gcc/doc/gcc.texi *** gcc-6.3.0/gcc/doc/gcc.texi Mon Jan 4 13:03:35 2016 --- gcc-6.4.0/gcc/doc/gcc.texi Tue Jul 4 07:15:57 2017 *************** *** 40,46 **** @c %**end of header @copying ! Copyright @copyright{} 1988-2016 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 --- 40,46 ---- @c %**end of header @copying ! Copyright @copyright{} 1988-2017 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 *************** Texts being (a) (see below), and with th *** 67,72 **** --- 67,73 ---- * g++: (gcc). The GNU C++ compiler. * gcov: (gcc) Gcov. @command{gcov}---a test coverage program. * gcov-tool: (gcc) Gcov-tool. @command{gcov-tool}---an offline gcda profile processing program. + * gcov-dump: (gcc) Gcov-dump. @command{gcov-dump}---an offline gcda and gcno profile dump tool. @end direntry This file documents the use of the GNU compilers. @sp 1 *************** Introduction, gccint, GNU Compiler Colle *** 140,145 **** --- 141,147 ---- * Compatibility:: Binary Compatibility * Gcov:: @command{gcov}---a test coverage program. * Gcov-tool:: @command{gcov-tool}---an offline gcda profile processing program. + * Gcov-dump:: @command{gcov-dump}---an offline gcda and gcno profile dump tool. * Trouble:: If you have trouble using GCC. * Bugs:: How, why and where to report bugs. * Service:: How To Get Help with GCC *************** Introduction, gccint, GNU Compiler Colle *** 167,172 **** --- 169,175 ---- @include compat.texi @include gcov.texi @include gcov-tool.texi + @include gcov-dump.texi @include trouble.texi @include bugreport.texi @include service.texi diff -Nrcpad gcc-6.3.0/gcc/doc/gccinstall.info gcc-6.4.0/gcc/doc/gccinstall.info *** gcc-6.3.0/gcc/doc/gccinstall.info Wed Dec 21 09:34:04 2016 --- gcc-6.4.0/gcc/doc/gccinstall.info Tue Jul 4 09:27:46 2017 *************** *** 1,7 **** ! This is gccinstall.info, produced by makeinfo version 6.1 from ! install.texi. ! Copyright (C) 1988-2016 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 --- 1,7 ---- ! This is doc/gccinstall.info, produced by makeinfo version 4.13 from ! /space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/doc/install.texi. ! Copyright (C) 1988-2017 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 *************** is included in the section entitled "GNU *** 17,30 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development. ! INFO-DIR-SECTION Software development ! START-INFO-DIR-ENTRY ! * gccinstall: (gccinstall). Installing the GNU Compiler Collection. ! END-INFO-DIR-ENTRY ! Copyright (C) 1988-2016 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 --- 17,26 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. ! Copyright (C) 1988-2017 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 *************** is included in the section entitled "GNU *** 40,47 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development.  File: gccinstall.info, Node: Top, Up: (dir) --- 36,48 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. ! ! INFO-DIR-SECTION Software development ! START-INFO-DIR-ENTRY ! * gccinstall: (gccinstall). Installing the GNU Compiler Collection. ! END-INFO-DIR-ENTRY  File: gccinstall.info, Node: Top, Up: (dir) *************** File: gccinstall.info, Node: Installing *** 66,78 **** 1 Installing GCC **************** ! The latest version of this document is always available at http://gcc.gnu.org/install/. It refers to the current development sources, instructions for specific released versions are included with the sources. ! This document describes the generic installation procedure for GCC as ! well as detailing some target specific installation instructions. GCC includes several components that previously were separate distributions with their own installation instructions. This document --- 67,79 ---- 1 Installing GCC **************** ! The latest version of this document is always available at http://gcc.gnu.org/install/. It refers to the current development sources, instructions for specific released versions are included with the sources. ! This document describes the generic installation procedure for GCC ! as well as detailing some target specific installation instructions. GCC includes several components that previously were separate distributions with their own installation instructions. This document *************** supersedes all package-specific installa *** 82,90 **** host/target specific installation notes: Specific. We recommend you browse the entire generic installation instructions before you proceed. ! Lists of successful builds for released versions of GCC are available ! at . These lists are updated as new ! information becomes available. The installation procedure itself is broken into five steps. --- 83,91 ---- host/target specific installation notes: Specific. We recommend you browse the entire generic installation instructions before you proceed. ! Lists of successful builds for released versions of GCC are ! available at `http://gcc.gnu.org/buildstat.html'. These lists are ! updated as new information becomes available. The installation procedure itself is broken into five steps. *************** information becomes available. *** 97,108 **** * Testing:: (optional) * Final install:: ! Please note that GCC does not support 'make uninstall' and probably won't do so in the near future as this would open a can of worms. ! Instead, we suggest that you install GCC into a directory of its own and ! simply remove that directory when you do not need that specific version ! of GCC any longer, and, if shared libraries are installed there as well, ! no more binaries exist that use them.  File: gccinstall.info, Node: Prerequisites, Next: Downloading the source, Up: Installing GCC --- 98,109 ---- * Testing:: (optional) * Final install:: ! Please note that GCC does not support `make uninstall' and probably won't do so in the near future as this would open a can of worms. ! Instead, we suggest that you install GCC into a directory of its own ! and simply remove that directory when you do not need that specific ! version of GCC any longer, and, if shared libraries are installed there ! as well, no more binaries exist that use them.  File: gccinstall.info, Node: Prerequisites, Next: Downloading the source, Up: Installing GCC *************** File: gccinstall.info, Node: Prerequisi *** 110,117 **** 2 Prerequisites *************** ! 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 --- 111,118 ---- 2 Prerequisites *************** ! 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++98 compiler *** 124,391 **** C compiler. To build all languages in a cross-compiler or other configuration ! where 3-stage bootstrap is not performed, you need to start with an ! existing GCC binary (version 3.4 or later) because source code for ! language frontends other than C might use GCC extensions. Note that to bootstrap GCC with versions of GCC earlier than 3.4, ! you may need to use '--disable-stage1-checking', though bootstrapping the compiler with such earlier compilers is strongly discouraged. C standard library and headers - In order to build GCC, the C standard library and headers must be present for all target variants for which target libraries will be built (and not only the variant of the host C++ compiler). ! This affects the popular 'x86_64-unknown-linux-gnu' platform (among ! other multilib targets), for which 64-bit ('x86_64') and 32-bit ! ('i386') libc headers are usually packaged separately. If you do a ! build of a native compiler on 'x86_64-unknown-linux-gnu', make sure ! you either have the 32-bit libc developer package properly ! installed (the exact name of the package depends on your distro) or ! you must build GCC as a 64-bit only compiler by configuring with ! the option '--disable-multilib'. Otherwise, you may encounter an ! error such as 'fatal error: gnu/stubs-32.h: No such file' GNAT - In order to build the Ada compiler (GNAT) you must already have GNAT installed because portions of the Ada frontend are written in Ada (with GNAT extensions.) Refer to the Ada installation instructions for more specific information. A "working" POSIX compatible shell, or GNU bash ! ! Necessary when running 'configure' because some '/bin/sh' shells have bugs and may crash when configuring the target libraries. In ! other cases, '/bin/sh' or 'ksh' have disastrous corner-case ! performance problems. This can cause target 'configure' runs to literally take days to complete in some cases. ! So on some platforms '/bin/ksh' is sufficient, on others it isn't. ! See the host/target specific instructions for your platform, or use ! 'bash' to be sure. Then set 'CONFIG_SHELL' in your environment to ! your "good" shell prior to running 'configure'/'make'. ! 'zsh' is not a fully compliant POSIX shell and will not work when configuring GCC. A POSIX or SVR4 awk - Necessary for creating some of the generated source files for GCC. If in doubt, use a recent GNU awk version, as some of the older ones are broken. GNU awk version 3.1.5 is known to work. GNU binutils - Necessary in some circumstances, optional in others. See the host/target specific instructions for your platform for the exact requirements. gzip version 1.2.4 (or later) or bzip2 version 1.0.2 (or later) ! ! Necessary to uncompress GCC 'tar' files when source code is obtained via FTP mirror sites. GNU make version 3.80 (or later) - You must have GNU make installed to build GCC. GNU tar version 1.14 (or later) - Necessary (only on some platforms) to untar the source code. Many ! systems' 'tar' programs will also work, only try GNU 'tar' if you have problems. Perl version 5.6.1 (or later) ! Necessary when targeting Darwin, building 'libstdc++', and not ! using '--disable-symvers'. Necessary when targeting Solaris 2 with ! Sun 'ld' and not using '--disable-symvers'. The bundled 'perl' in ! Solaris 8 and up works. ! ! Necessary when regenerating 'Makefile' dependencies in libiberty. ! Necessary when regenerating 'libiberty/functions.texi'. Necessary when generating manpages from Texinfo manuals. Used by various scripts to generate some files included in SVN (mainly Unicode-related and rarely changing) from source tables. ! 'jar', or InfoZIP ('zip' and 'unzip') ! Necessary to build libgcj, the GCJ runtime. Several support libraries are necessary to build GCC, some are required, others optional. While any sufficiently new version of required tools usually work, library requirements are generally stricter. Newer versions may work in some cases, but it's safer to use ! the exact versions documented. We appreciate bug reports about problems ! with newer versions, though. If your OS vendor provides packages for ! the support libraries then using those packages may be the simplest way ! to install the libraries. GNU Multiple Precision Library (GMP) version 4.3.2 (or later) - Necessary to build GCC. If a GMP source distribution is found in a ! subdirectory of your GCC sources named 'gmp', it will be built ! together with GCC. Alternatively, if GMP is already installed but it is not in your library search path, you will have to configure ! with the '--with-gmp' configure option. See also '--with-gmp-lib' ! and '--with-gmp-include'. MPFR Library version 2.4.2 (or later) - Necessary to build GCC. It can be downloaded from ! . If an MPFR source distribution is found in ! a subdirectory of your GCC sources named 'mpfr', it will be built ! together with GCC. Alternatively, if MPFR is already installed but ! it is not in your default library search path, the '--with-mpfr' ! configure option should be used. See also '--with-mpfr-lib' and ! '--with-mpfr-include'. MPC Library version 0.8.1 (or later) - Necessary to build GCC. It can be downloaded from ! . If an MPC source distribution is ! found in a subdirectory of your GCC sources named 'mpc', it will be ! built together with GCC. Alternatively, if MPC is already installed ! but it is not in your default library search path, the '--with-mpc' ! configure option should be used. See also '--with-mpc-lib' and ! '--with-mpc-include'. isl Library version 0.16, 0.15, or 0.14. - Necessary to build GCC with the Graphite loop optimizations. It ! can be downloaded from . If an isl source distribution is found in a subdirectory of your ! GCC sources named 'isl', it will be built together with GCC. ! Alternatively, the '--with-isl' configure option should be used if isl is not installed in your default library search path. Tools/packages necessary for modifying GCC ========================================== autoconf version 2.64 GNU m4 version 1.4.6 (or later) ! ! Necessary when modifying 'configure.ac', 'aclocal.m4', etc. to ! regenerate 'configure' and 'config.in' files. automake version 1.11.6 ! ! Necessary when modifying a 'Makefile.am' file to regenerate its ! associated 'Makefile.in'. Much of GCC does not use automake, so directly edit the ! 'Makefile.in' file. Specifically this applies to the 'gcc', ! 'intl', 'libcpp', 'libiberty', 'libobjc' directories as well as any ! of their subdirectories. For directories that use automake, GCC requires the latest release ! in the 1.11 series, which is currently 1.11.6. When regenerating a ! directory to a newer version, please update all the directories using an older 1.11 to the latest released version. gettext version 0.14.5 (or later) ! ! Needed to regenerate 'gcc.pot'. gperf version 2.7.2 (or later) ! ! Necessary when modifying 'gperf' input files, e.g. ! 'gcc/cp/cfns.gperf' to regenerate its associated header file, e.g. ! 'gcc/cp/cfns.h'. DejaGnu 1.4.4 Expect Tcl - Necessary to run the GCC testsuite; see the section on testing for details. Tcl 8.6 has a known regression in RE pattern handling that make parts of the testsuite fail. See ! for more information. This bug has been fixed in 8.6.1. autogen version 5.5.4 (or later) and guile version 1.4.1 (or later) ! Necessary to regenerate 'fixinc/fixincl.x' from ! 'fixinc/inclhack.def' and 'fixinc/*.tpl'. ! ! Necessary to run 'make check' for 'fixinc'. ! Necessary to regenerate the top level 'Makefile.in' file from ! 'Makefile.tpl' and 'Makefile.def'. Flex version 2.5.4 (or later) ! ! Necessary when modifying '*.l' files. Necessary to build GCC during development because the generated output files are not included in the SVN repository. They are included in releases. Texinfo version 4.7 (or later) ! ! Necessary for running 'makeinfo' when modifying '*.texi' files to test your changes. ! Necessary for running 'make dvi' or 'make pdf' to create printable documentation in DVI or PDF format. Texinfo version 4.8 or later ! is required for 'make pdf'. Necessary to build GCC documentation during development because the generated output files are not included in the SVN repository. They are included in releases. TeX (any working version) ! ! Necessary for running 'texi2dvi' and 'texi2pdf', which are used ! when running 'make dvi' or 'make pdf' to create DVI or PDF files, respectively. Sphinx version 1.0 (or later) ! ! Necessary to regenerate 'jit/docs/_build/texinfo' from the '.rst' ! files in the directories below 'jit/docs'. SVN (any version) SSH (any version) - Necessary to access the SVN repository. Public releases and weekly snapshots of the development sources are also available via FTP. GNU diffutils version 2.7 (or later) - Useful when submitting patches for the GCC source code. patch version 2.5.4 (or later) ! ! Necessary when applying patches, created with 'diff', to one's own sources. ecj1 gjavah ! ! If you wish to modify '.java' files in libjava, you will need to ! configure with '--enable-java-maintainer-mode', and you will need ! to have executables named 'ecj1' and 'gjavah' in your path. The ! 'ecj1' executable should run the Eclipse Java compiler via the GCC-specific entry point. You can download a suitable jar from ! , or by running the script ! 'contrib/download_ecj'. antlr.jar version 2.7.1 (or later) antlr binary ! ! If you wish to build the 'gjdoc' binary in libjava, you will need ! to have an 'antlr.jar' library available. The library is searched for in system locations but can be specified with ! '--with-antlr-jar=' instead. When configuring with ! '--enable-java-maintainer-mode', you will need to have one of the ! executables named 'cantlr', 'runantlr' or 'antlr' in your path.  File: gccinstall.info, Node: Downloading the source, Next: Configuration, Prev: Prerequisites, Up: Installing GCC --- 125,368 ---- C compiler. To build all languages in a cross-compiler or other configuration ! where 3-stage bootstrap is not performed, you need to start with ! an existing GCC binary (version 3.4 or later) because source code ! for language frontends other than C might use GCC extensions. Note that to bootstrap GCC with versions of GCC earlier than 3.4, ! you may need to use `--disable-stage1-checking', though bootstrapping the compiler with such earlier compilers is strongly discouraged. C standard library and headers In order to build GCC, the C standard library and headers must be present for all target variants for which target libraries will be built (and not only the variant of the host C++ compiler). ! This affects the popular `x86_64-unknown-linux-gnu' platform (among ! other multilib targets), for which 64-bit (`x86_64') and 32-bit ! (`i386') libc headers are usually packaged separately. If you do a ! build of a native compiler on `x86_64-unknown-linux-gnu', make ! sure you either have the 32-bit libc developer package properly ! installed (the exact name of the package depends on your distro) ! or you must build GCC as a 64-bit only compiler by configuring ! with the option `--disable-multilib'. Otherwise, you may ! encounter an error such as `fatal error: gnu/stubs-32.h: No such ! file' GNAT In order to build the Ada compiler (GNAT) you must already have GNAT installed because portions of the Ada frontend are written in Ada (with GNAT extensions.) Refer to the Ada installation instructions for more specific information. A "working" POSIX compatible shell, or GNU bash ! Necessary when running `configure' because some `/bin/sh' shells have bugs and may crash when configuring the target libraries. In ! other cases, `/bin/sh' or `ksh' have disastrous corner-case ! performance problems. This can cause target `configure' runs to literally take days to complete in some cases. ! So on some platforms `/bin/ksh' is sufficient, on others it isn't. ! See the host/target specific instructions for your platform, or ! use `bash' to be sure. Then set `CONFIG_SHELL' in your ! environment to your "good" shell prior to running ! `configure'/`make'. ! `zsh' is not a fully compliant POSIX shell and will not work when configuring GCC. A POSIX or SVR4 awk Necessary for creating some of the generated source files for GCC. If in doubt, use a recent GNU awk version, as some of the older ones are broken. GNU awk version 3.1.5 is known to work. GNU binutils Necessary in some circumstances, optional in others. See the host/target specific instructions for your platform for the exact requirements. gzip version 1.2.4 (or later) or bzip2 version 1.0.2 (or later) ! Necessary to uncompress GCC `tar' files when source code is obtained via FTP mirror sites. GNU make version 3.80 (or later) You must have GNU make installed to build GCC. GNU tar version 1.14 (or later) Necessary (only on some platforms) to untar the source code. Many ! systems' `tar' programs will also work, only try GNU `tar' if you have problems. Perl version 5.6.1 (or later) + Necessary when targeting Darwin, building `libstdc++', and not + using `--disable-symvers'. Necessary when targeting Solaris 2 + with Sun `ld' and not using `--disable-symvers'. The bundled + `perl' in Solaris 8 and up works. ! Necessary when regenerating `Makefile' dependencies in libiberty. ! Necessary when regenerating `libiberty/functions.texi'. Necessary when generating manpages from Texinfo manuals. Used by various scripts to generate some files included in SVN (mainly Unicode-related and rarely changing) from source tables. ! `jar', or InfoZIP (`zip' and `unzip') Necessary to build libgcj, the GCJ runtime. + Several support libraries are necessary to build GCC, some are required, others optional. While any sufficiently new version of required tools usually work, library requirements are generally stricter. Newer versions may work in some cases, but it's safer to use ! the exact versions documented. We appreciate bug reports about ! problems with newer versions, though. If your OS vendor provides ! packages for the support libraries then using those packages may be the ! simplest way to install the libraries. GNU Multiple Precision Library (GMP) version 4.3.2 (or later) Necessary to build GCC. If a GMP source distribution is found in a ! subdirectory of your GCC sources named `gmp', it will be built ! together with GCC. Alternatively, if GMP is already installed but it is not in your library search path, you will have to configure ! with the `--with-gmp' configure option. See also `--with-gmp-lib' ! and `--with-gmp-include'. MPFR Library version 2.4.2 (or later) Necessary to build GCC. It can be downloaded from ! `http://www.mpfr.org/'. If an MPFR source distribution is found ! in a subdirectory of your GCC sources named `mpfr', it will be ! built together with GCC. Alternatively, if MPFR is already ! installed but it is not in your default library search path, the ! `--with-mpfr' configure option should be used. See also ! `--with-mpfr-lib' and `--with-mpfr-include'. MPC Library version 0.8.1 (or later) Necessary to build GCC. It can be downloaded from ! `http://www.multiprecision.org/'. If an MPC source distribution ! is found in a subdirectory of your GCC sources named `mpc', it ! will be built together with GCC. Alternatively, if MPC is already ! installed but it is not in your default library search path, the ! `--with-mpc' configure option should be used. See also ! `--with-mpc-lib' and `--with-mpc-include'. isl Library version 0.16, 0.15, or 0.14. Necessary to build GCC with the Graphite loop optimizations. It ! can be downloaded from `ftp://gcc.gnu.org/pub/gcc/infrastructure/'. If an isl source distribution is found in a subdirectory of your ! GCC sources named `isl', it will be built together with GCC. ! Alternatively, the `--with-isl' configure option should be used if isl is not installed in your default library search path. + Tools/packages necessary for modifying GCC ========================================== autoconf version 2.64 GNU m4 version 1.4.6 (or later) ! Necessary when modifying `configure.ac', `aclocal.m4', etc. to ! regenerate `configure' and `config.in' files. automake version 1.11.6 ! Necessary when modifying a `Makefile.am' file to regenerate its ! associated `Makefile.in'. Much of GCC does not use automake, so directly edit the ! `Makefile.in' file. Specifically this applies to the `gcc', ! `intl', `libcpp', `libiberty', `libobjc' directories as well as ! any of their subdirectories. For directories that use automake, GCC requires the latest release ! in the 1.11 series, which is currently 1.11.6. When regenerating ! a directory to a newer version, please update all the directories using an older 1.11 to the latest released version. gettext version 0.14.5 (or later) ! Needed to regenerate `gcc.pot'. gperf version 2.7.2 (or later) ! Necessary when modifying `gperf' input files, e.g. ! `gcc/cp/cfns.gperf' to regenerate its associated header file, e.g. ! `gcc/cp/cfns.h'. DejaGnu 1.4.4 Expect Tcl Necessary to run the GCC testsuite; see the section on testing for details. Tcl 8.6 has a known regression in RE pattern handling that make parts of the testsuite fail. See ! `http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f' for more information. This bug has been fixed in 8.6.1. autogen version 5.5.4 (or later) and guile version 1.4.1 (or later) + Necessary to regenerate `fixinc/fixincl.x' from + `fixinc/inclhack.def' and `fixinc/*.tpl'. ! Necessary to run `make check' for `fixinc'. ! Necessary to regenerate the top level `Makefile.in' file from ! `Makefile.tpl' and `Makefile.def'. Flex version 2.5.4 (or later) ! Necessary when modifying `*.l' files. Necessary to build GCC during development because the generated output files are not included in the SVN repository. They are included in releases. Texinfo version 4.7 (or later) ! Necessary for running `makeinfo' when modifying `*.texi' files to test your changes. ! Necessary for running `make dvi' or `make pdf' to create printable documentation in DVI or PDF format. Texinfo version 4.8 or later ! is required for `make pdf'. Necessary to build GCC documentation during development because the generated output files are not included in the SVN repository. They are included in releases. TeX (any working version) ! Necessary for running `texi2dvi' and `texi2pdf', which are used ! when running `make dvi' or `make pdf' to create DVI or PDF files, respectively. Sphinx version 1.0 (or later) ! Necessary to regenerate `jit/docs/_build/texinfo' from the `.rst' ! files in the directories below `jit/docs'. SVN (any version) SSH (any version) Necessary to access the SVN repository. Public releases and weekly snapshots of the development sources are also available via FTP. GNU diffutils version 2.7 (or later) Useful when submitting patches for the GCC source code. patch version 2.5.4 (or later) ! Necessary when applying patches, created with `diff', to one's own sources. ecj1 gjavah ! If you wish to modify `.java' files in libjava, you will need to ! configure with `--enable-java-maintainer-mode', and you will need ! to have executables named `ecj1' and `gjavah' in your path. The ! `ecj1' executable should run the Eclipse Java compiler via the GCC-specific entry point. You can download a suitable jar from ! `ftp://sourceware.org/pub/java/', or by running the script ! `contrib/download_ecj'. antlr.jar version 2.7.1 (or later) antlr binary ! If you wish to build the `gjdoc' binary in libjava, you will need ! to have an `antlr.jar' library available. The library is searched for in system locations but can be specified with ! `--with-antlr-jar=' instead. When configuring with ! `--enable-java-maintainer-mode', you will need to have one of the ! executables named `cantlr', `runantlr' or `antlr' in your path. !  File: gccinstall.info, Node: Downloading the source, Next: Configuration, Prev: Prerequisites, Up: Installing GCC *************** File: gccinstall.info, Node: Downloadin *** 393,426 **** 3 Downloading GCC ***************** ! GCC is distributed via SVN and FTP tarballs compressed with 'gzip' or ! 'bzip2'. Please refer to the releases web page for information on how to obtain GCC. The source distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in the case of GCC 3.1 and later) compilers, as well as ! runtime libraries for C++, Objective-C, Fortran, and Java. For previous ! versions these were downloadable as separate components such as the core ! GCC distribution, which included the C language front end and shared ! components, and language-specific distributions including the language ! front end and the language runtime (where appropriate). If you also intend to build binutils (either to upgrade an existing ! installation or for use in place of the corresponding tools of your OS), ! unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components ! of the binutils you intend to build alongside the compiler ('bfd', ! 'binutils', 'gas', 'gprof', 'ld', 'opcodes', ...) to the directory containing the GCC sources. Likewise the GMP, MPFR and MPC libraries can be automatically built ! together with GCC. You may simply run the ! 'contrib/download_prerequisites' script in the GCC source directory to set up everything. Otherwise unpack the GMP, MPFR and/or MPC source distributions in the directory containing the GCC sources and rename ! their directories to 'gmp', 'mpfr' and 'mpc', respectively (or use symbolic links with the same name).  --- 370,403 ---- 3 Downloading GCC ***************** ! GCC is distributed via SVN and FTP tarballs compressed with `gzip' or ! `bzip2'. Please refer to the releases web page for information on how to obtain GCC. The source distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in the case of GCC 3.1 and later) compilers, as well as ! runtime libraries for C++, Objective-C, Fortran, and Java. For ! previous versions these were downloadable as separate components such ! as the core GCC distribution, which included the C language front end ! and shared components, and language-specific distributions including the ! language front end and the language runtime (where appropriate). If you also intend to build binutils (either to upgrade an existing ! installation or for use in place of the corresponding tools of your ! OS), unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components ! of the binutils you intend to build alongside the compiler (`bfd', ! `binutils', `gas', `gprof', `ld', `opcodes', ...) to the directory containing the GCC sources. Likewise the GMP, MPFR and MPC libraries can be automatically built ! together with GCC. You may simply run the ! `contrib/download_prerequisites' script in the GCC source directory to set up everything. Otherwise unpack the GMP, MPFR and/or MPC source distributions in the directory containing the GCC sources and rename ! their directories to `gmp', `mpfr' and `mpc', respectively (or use symbolic links with the same name).  *************** File: gccinstall.info, Node: Configurat *** 429,450 **** 4 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 via SVN, SRCDIR must refer to the top ! 'gcc' directory, the one where the 'MAINTAINERS' file can be found, and ! not its 'gcc' subdirectory, otherwise the build will fail. If either SRCDIR or OBJDIR is located on an automounted NFS file ! system, the shell's built-in 'pwd' command will return temporary ! pathnames. Using these can lead to various sorts of build problems. To ! avoid this issue, set the 'PWDCMD' environment variable to an ! automounter-aware 'pwd' command, e.g., 'pawd' or 'amq -w', during the configuration and build phases. First, we *highly* recommend that GCC be built into a separate --- 406,427 ---- 4 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 via SVN, SRCDIR must refer to the top ! `gcc' directory, the one where the `MAINTAINERS' file can be found, and ! not its `gcc' subdirectory, otherwise the build will fail. If either SRCDIR or OBJDIR is located on an automounted NFS file ! system, the shell's built-in `pwd' command will return temporary ! pathnames. Using these can lead to various sorts of build problems. ! To avoid this issue, set the `PWDCMD' environment variable to an ! automounter-aware `pwd' command, e.g., `pawd' or `amq -w', during the configuration and build phases. First, we *highly* recommend that GCC be built into a separate *************** OBJDIR should still work, but doesn't ge *** 454,469 **** where OBJDIR is a subdirectory of SRCDIR is unsupported. If you have previously built GCC in the same directory for a ! different target machine, do 'make distclean' to delete all files that ! might be invalid. One of the files this deletes is 'Makefile'; if 'make ! distclean' complains that 'Makefile' does not exist or issues a message ! like "don't know how to make distclean" it probably means that the ! directory is already suitably clean. However, with the recommended method of building in a separate OBJDIR, you should simply use a different OBJDIR for each target. ! Second, when configuring a native system, either 'cc' or 'gcc' must ! be in your path or you must set 'CC' in your environment before running configure. Otherwise the configuration scripts may fail. To configure GCC: --- 431,446 ---- where OBJDIR is a subdirectory of SRCDIR is unsupported. If you have previously built GCC in the same directory for a ! different target machine, do `make distclean' to delete all files that ! might be invalid. One of the files this deletes is `Makefile'; if ! `make distclean' complains that `Makefile' does not exist or issues a ! message like "don't know how to make distclean" it probably means that ! the directory is already suitably clean. However, with the recommended method of building in a separate OBJDIR, you should simply use a different OBJDIR for each target. ! Second, when configuring a native system, either `cc' or `gcc' must ! be in your path or you must set `CC' in your environment before running configure. Otherwise the configuration scripts may fail. To configure GCC: *************** Distributor options *** 476,493 **** =================== If you will be distributing binary versions of GCC, with modifications ! to the source code, you should use the options described in this section ! to make clear that your version contains modifications. ! '--with-pkgversion=VERSION' Specify a string that identifies your package. You may wish to include a build number or build date. This version string will be ! included in the output of 'gcc --version'. This suffix does not ! replace the default version string, only the 'GCC' part. ! The default value is 'GCC'. ! '--with-bugurl=URL' Specify the URL that users should visit if they wish to report a bug. You are of course welcome to forward bugs reported to you to the FSF, if you determine that they are not bugs in your --- 453,470 ---- =================== If you will be distributing binary versions of GCC, with modifications ! to the source code, you should use the options described in this ! section to make clear that your version contains modifications. ! `--with-pkgversion=VERSION' Specify a string that identifies your package. You may wish to include a build number or build date. This version string will be ! included in the output of `gcc --version'. This suffix does not ! replace the default version string, only the `GCC' part. ! The default value is `GCC'. ! `--with-bugurl=URL' Specify the URL that users should visit if they wish to report a bug. You are of course welcome to forward bugs reported to you to the FSF, if you determine that they are not bugs in your *************** to make clear that your version contains *** 495,500 **** --- 472,478 ---- The default value refers to the FSF's GCC bug tracker. + Target specification ==================== *************** Target specification *** 503,637 **** do not provide a configure target when configuring a native compiler. ! * TARGET must be specified as '--target=TARGET' when configuring a cross compiler; examples of valid targets would be m68k-elf, sh-elf, etc. ! * Specifying just TARGET instead of '--target=TARGET' implies that the host defaults to TARGET. Options specification ===================== Use OPTIONS to override several configure time options for GCC. A list ! of supported OPTIONS follows; 'configure --help' may list other options, ! but those not listed below may not work and should not normally be used. ! Note that each '--enable' option has a corresponding '--disable' ! option and that each '--with' option has a corresponding '--without' option. ! '--prefix=DIRNAME' Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to ! '/usr/local'. We *highly* recommend against DIRNAME being the same or a subdirectory of OBJDIR or vice versa. If specifying a directory beneath a user's home directory tree, some shells will not expand ! DIRNAME correctly if it contains the '~' metacharacter; use '$HOME' ! instead. ! The following standard 'autoconf' options are supported. Normally you should not need to use these options. ! '--exec-prefix=DIRNAME' Specify the toplevel installation directory for ! architecture-dependent files. The default is 'PREFIX'. ! '--bindir=DIRNAME' Specify the installation directory for the executables called ! by users (such as 'gcc' and 'g++'). The default is ! 'EXEC-PREFIX/bin'. ! '--libdir=DIRNAME' Specify the installation directory for object code libraries and internal data files of GCC. The default is ! 'EXEC-PREFIX/lib'. ! '--libexecdir=DIRNAME' ! Specify the installation directory for internal executables of ! GCC. The default is 'EXEC-PREFIX/libexec'. ! '--with-slibdir=DIRNAME' Specify the installation directory for the shared libgcc ! library. The default is 'LIBDIR'. ! '--datarootdir=DIRNAME' Specify the root of the directory tree for read-only architecture-independent data files referenced by GCC. The ! default is 'PREFIX/share'. ! '--infodir=DIRNAME' Specify the installation directory for documentation in info ! format. The default is 'DATAROOTDIR/info'. ! '--datadir=DIRNAME' Specify the installation directory for some architecture-independent data files referenced by GCC. The ! default is 'DATAROOTDIR'. ! '--docdir=DIRNAME' Specify the installation directory for documentation files ! (other than Info) for GCC. The default is 'DATAROOTDIR/doc'. ! '--htmldir=DIRNAME' Specify the installation directory for HTML documentation ! files. The default is 'DOCDIR'. ! '--pdfdir=DIRNAME' Specify the installation directory for PDF documentation ! files. The default is 'DOCDIR'. ! '--mandir=DIRNAME' Specify the installation directory for manual pages. The ! default is 'DATAROOTDIR/man'. (Note that the manual pages are ! only extracts from the full GCC manuals, which are provided in ! Texinfo format. The manpages are derived by an automatic ! conversion process from parts of the full manual.) ! '--with-gxx-include-dir=DIRNAME' Specify the installation directory for G++ header files. The default depends on other configuration options, and differs between cross and native configurations. ! '--with-specs=SPECS' ! Specify additional command line driver SPECS. This can be useful if you need to turn on a non-standard feature by default without modifying the compiler's source code, for instance ! '--with-specs=%{!fcommon:%{!fno-common:-fno-common}}'. *Note Specifying subprocesses and the switches to pass to them: (gcc)Spec Files, ! '--program-prefix=PREFIX' GCC supports some transformations of the names of its programs when installing them. This option prepends PREFIX to the names of programs to install in BINDIR (see above). For example, specifying ! '--program-prefix=foo-' would result in 'gcc' being installed as ! '/usr/local/bin/foo-gcc'. ! '--program-suffix=SUFFIX' Appends SUFFIX to the names of programs to install in BINDIR (see ! above). For example, specifying '--program-suffix=-3.1' would ! result in 'gcc' being installed as '/usr/local/bin/gcc-3.1'. ! '--program-transform-name=PATTERN' ! Applies the 'sed' script PATTERN to be applied to the names of programs to install in BINDIR (see above). PATTERN has to consist ! of one or more basic 'sed' editing commands, separated by ! semicolons. For example, if you want the 'gcc' program name to be ! transformed to the installed program '/usr/local/bin/myowngcc' and ! the 'g++' program name to be transformed to ! '/usr/local/bin/gspecial++' without changing other program names, you could use the pattern ! '--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'' to achieve this effect. All three options can be combined and used together, resulting in more complex conversion patterns. As a basic rule, PREFIX (and ! SUFFIX) are prepended (appended) before further transformations can ! happen with a special transformation script PATTERN. As currently implemented, this option only takes effect for native builds; cross compiler binaries' names are not transformed even --- 481,617 ---- do not provide a configure target when configuring a native compiler. ! * TARGET must be specified as `--target=TARGET' when configuring a cross compiler; examples of valid targets would be m68k-elf, sh-elf, etc. ! * Specifying just TARGET instead of `--target=TARGET' implies that the host defaults to TARGET. Options specification ===================== Use OPTIONS to override several configure time options for GCC. A list ! of supported OPTIONS follows; `configure --help' may list other ! options, but those not listed below may not work and should not ! normally be used. ! Note that each `--enable' option has a corresponding `--disable' ! option and that each `--with' option has a corresponding `--without' option. ! `--prefix=DIRNAME' Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to ! `/usr/local'. We *highly* recommend against DIRNAME being the same or a subdirectory of OBJDIR or vice versa. If specifying a directory beneath a user's home directory tree, some shells will not expand ! DIRNAME correctly if it contains the `~' metacharacter; use ! `$HOME' instead. ! The following standard `autoconf' options are supported. Normally you should not need to use these options. ! `--exec-prefix=DIRNAME' Specify the toplevel installation directory for ! architecture-dependent files. The default is `PREFIX'. ! `--bindir=DIRNAME' Specify the installation directory for the executables called ! by users (such as `gcc' and `g++'). The default is ! `EXEC-PREFIX/bin'. ! `--libdir=DIRNAME' Specify the installation directory for object code libraries and internal data files of GCC. The default is ! `EXEC-PREFIX/lib'. ! `--libexecdir=DIRNAME' ! Specify the installation directory for internal executables ! of GCC. The default is `EXEC-PREFIX/libexec'. ! `--with-slibdir=DIRNAME' Specify the installation directory for the shared libgcc ! library. The default is `LIBDIR'. ! `--datarootdir=DIRNAME' Specify the root of the directory tree for read-only architecture-independent data files referenced by GCC. The ! default is `PREFIX/share'. ! `--infodir=DIRNAME' Specify the installation directory for documentation in info ! format. The default is `DATAROOTDIR/info'. ! `--datadir=DIRNAME' Specify the installation directory for some architecture-independent data files referenced by GCC. The ! default is `DATAROOTDIR'. ! `--docdir=DIRNAME' Specify the installation directory for documentation files ! (other than Info) for GCC. The default is `DATAROOTDIR/doc'. ! `--htmldir=DIRNAME' Specify the installation directory for HTML documentation ! files. The default is `DOCDIR'. ! `--pdfdir=DIRNAME' Specify the installation directory for PDF documentation ! files. The default is `DOCDIR'. ! `--mandir=DIRNAME' Specify the installation directory for manual pages. The ! default is `DATAROOTDIR/man'. (Note that the manual pages ! are only extracts from the full GCC manuals, which are ! provided in Texinfo format. The manpages are derived by an ! automatic conversion process from parts of the full manual.) ! `--with-gxx-include-dir=DIRNAME' Specify the installation directory for G++ header files. The default depends on other configuration options, and differs between cross and native configurations. ! `--with-specs=SPECS' ! Specify additional command line driver SPECS. This can be useful if you need to turn on a non-standard feature by default without modifying the compiler's source code, for instance ! `--with-specs=%{!fcommon:%{!fno-common:-fno-common}}'. *Note Specifying subprocesses and the switches to pass to them: (gcc)Spec Files, ! ! `--program-prefix=PREFIX' GCC supports some transformations of the names of its programs when installing them. This option prepends PREFIX to the names of programs to install in BINDIR (see above). For example, specifying ! `--program-prefix=foo-' would result in `gcc' being installed as ! `/usr/local/bin/foo-gcc'. ! `--program-suffix=SUFFIX' Appends SUFFIX to the names of programs to install in BINDIR (see ! above). For example, specifying `--program-suffix=-3.1' would ! result in `gcc' being installed as `/usr/local/bin/gcc-3.1'. ! `--program-transform-name=PATTERN' ! Applies the `sed' script PATTERN to be applied to the names of programs to install in BINDIR (see above). PATTERN has to consist ! of one or more basic `sed' editing commands, separated by ! semicolons. For example, if you want the `gcc' program name to be ! transformed to the installed program `/usr/local/bin/myowngcc' and ! the `g++' program name to be transformed to ! `/usr/local/bin/gspecial++' without changing other program names, you could use the pattern ! `--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'' to achieve this effect. All three options can be combined and used together, resulting in more complex conversion patterns. As a basic rule, PREFIX (and ! SUFFIX) are prepended (appended) before further transformations ! can happen with a special transformation script PATTERN. As currently implemented, this option only takes effect for native builds; cross compiler binaries' names are not transformed even *************** option. *** 640,734 **** For native builds, some of the installed programs are also installed with the target alias in front of their name, as in ! 'i686-pc-linux-gnu-gcc'. All of the above transformations happen before the target alias is prepended to the name--so, specifying ! '--program-prefix=foo-' and 'program-suffix=-3.1', the resulting binary would be installed as ! '/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1'. As a last shortcoming, none of the installed Ada programs are transformed yet, which will be fixed in some time. ! '--with-local-prefix=DIRNAME' Specify the installation directory for local include files. The ! default is '/usr/local'. Specify this option if you want the ! compiler to search directory 'DIRNAME/include' for locally ! installed header files _instead_ of '/usr/local/include'. ! You should specify '--with-local-prefix' *only* if your site has a ! different convention (not '/usr/local') for where to put site-specific files. ! The default value for '--with-local-prefix' is '/usr/local' ! regardless of the value of '--prefix'. Specifying '--prefix' has no effect on which directory GCC searches for local header files. This may seem counterintuitive, but actually it is logical. ! The purpose of '--prefix' is to specify where to _install GCC_. The ! local header files in '/usr/local/include'--if you put any in that ! directory--are not part of GCC. They are part of other programs--perhaps many others. (GCC installs its own header files ! in another directory which is based on the '--prefix' value.) Both the local-prefix include directory and the GCC-prefix include ! directory are part of GCC's "system include" directories. Although ! these two directories are not fixed, they need to be searched in ! the proper order for the correct processing of the include_next ! directive. The local-prefix include directory is searched before ! the GCC-prefix include directory. Another characteristic of system ! include directories is that pedantic warnings are turned off for ! headers in these directories. ! Some autoconf macros add '-I DIRECTORY' options to the compiler command line, to ensure that directories containing installed packages' headers are searched. When DIRECTORY is one of GCC's system include directories, GCC will ignore the option so that system directories continue to be processed in the correct order. ! This may result in a search order different from what was specified ! but the directory will still be searched. GCC automatically searches for ordinary libraries using ! 'GCC_EXEC_PREFIX'. Thus, when the same installation prefix is used ! for both GCC and packages, GCC will automatically search for both ! headers and libraries. This provides a configuration that is easy ! to use. GCC behaves in a manner similar to that when it is ! installed as a system compiler in '/usr'. Sites that need to install multiple versions of GCC may not want to use the above simple configuration. It is possible to use the ! '--program-prefix', '--program-suffix' and ! '--program-transform-name' options to install multiple versions into a single directory, but it may be simpler to use different ! prefixes and the '--with-local-prefix' option to specify the ! location of the site-specific files for each version. It will then ! be necessary for users to specify explicitly the location of local ! site libraries (e.g., with 'LIBRARY_PATH'). ! The same value can be used for both '--with-local-prefix' and ! '--prefix' provided it is not '/usr'. This can be used to avoid ! the default search of '/usr/local/include'. ! *Do not* specify '/usr' as the '--with-local-prefix'! The ! directory you use for '--with-local-prefix' *must not* contain any of the system's standard header files. If it did contain them, certain programs would be miscompiled (including GNU Emacs, on certain targets), because this would override and nullify the ! header file corrections made by the 'fixincludes' script. Indications are that people who use this option use it based on ! mistaken ideas of what it is for. People use it as if it specified ! where to install part of GCC. Perhaps they make this assumption ! because installing GCC creates the directory. ! '--with-native-system-header-dir=DIRNAME' Specifies that DIRNAME is the directory that contains native system ! header files, rather than '/usr/include'. This option is most useful if you are creating a compiler that should be isolated from the system as much as possible. It is most commonly used with the ! '--with-sysroot' option and will cause GCC to search DIRNAME inside ! the system root specified by that option. ! '--enable-shared[=PACKAGE[,...]]' Build shared versions of libraries, if shared libraries are supported on the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that --- 620,714 ---- For native builds, some of the installed programs are also installed with the target alias in front of their name, as in ! `i686-pc-linux-gnu-gcc'. All of the above transformations happen before the target alias is prepended to the name--so, specifying ! `--program-prefix=foo-' and `program-suffix=-3.1', the resulting binary would be installed as ! `/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1'. As a last shortcoming, none of the installed Ada programs are transformed yet, which will be fixed in some time. ! `--with-local-prefix=DIRNAME' Specify the installation directory for local include files. The ! default is `/usr/local'. Specify this option if you want the ! compiler to search directory `DIRNAME/include' for locally ! installed header files _instead_ of `/usr/local/include'. ! You should specify `--with-local-prefix' *only* if your site has a ! different convention (not `/usr/local') for where to put site-specific files. ! The default value for `--with-local-prefix' is `/usr/local' ! regardless of the value of `--prefix'. Specifying `--prefix' has no effect on which directory GCC searches for local header files. This may seem counterintuitive, but actually it is logical. ! The purpose of `--prefix' is to specify where to _install GCC_. ! The local header files in `/usr/local/include'--if you put any in ! that directory--are not part of GCC. They are part of other programs--perhaps many others. (GCC installs its own header files ! in another directory which is based on the `--prefix' value.) Both the local-prefix include directory and the GCC-prefix include ! directory are part of GCC's "system include" directories. ! Although these two directories are not fixed, they need to be ! searched in the proper order for the correct processing of the ! include_next directive. The local-prefix include directory is ! searched before the GCC-prefix include directory. Another ! characteristic of system include directories is that pedantic ! warnings are turned off for headers in these directories. ! Some autoconf macros add `-I DIRECTORY' options to the compiler command line, to ensure that directories containing installed packages' headers are searched. When DIRECTORY is one of GCC's system include directories, GCC will ignore the option so that system directories continue to be processed in the correct order. ! This may result in a search order different from what was ! specified but the directory will still be searched. GCC automatically searches for ordinary libraries using ! `GCC_EXEC_PREFIX'. Thus, when the same installation prefix is ! used for both GCC and packages, GCC will automatically search for ! both headers and libraries. This provides a configuration that is ! easy to use. GCC behaves in a manner similar to that when it is ! installed as a system compiler in `/usr'. Sites that need to install multiple versions of GCC may not want to use the above simple configuration. It is possible to use the ! `--program-prefix', `--program-suffix' and ! `--program-transform-name' options to install multiple versions into a single directory, but it may be simpler to use different ! prefixes and the `--with-local-prefix' option to specify the ! location of the site-specific files for each version. It will ! then be necessary for users to specify explicitly the location of ! local site libraries (e.g., with `LIBRARY_PATH'). ! The same value can be used for both `--with-local-prefix' and ! `--prefix' provided it is not `/usr'. This can be used to avoid ! the default search of `/usr/local/include'. ! *Do not* specify `/usr' as the `--with-local-prefix'! The ! directory you use for `--with-local-prefix' *must not* contain any of the system's standard header files. If it did contain them, certain programs would be miscompiled (including GNU Emacs, on certain targets), because this would override and nullify the ! header file corrections made by the `fixincludes' script. Indications are that people who use this option use it based on ! mistaken ideas of what it is for. People use it as if it ! specified where to install part of GCC. Perhaps they make this ! assumption because installing GCC creates the directory. ! `--with-native-system-header-dir=DIRNAME' Specifies that DIRNAME is the directory that contains native system ! header files, rather than `/usr/include'. This option is most useful if you are creating a compiler that should be isolated from the system as much as possible. It is most commonly used with the ! `--with-sysroot' option and will cause GCC to search DIRNAME ! inside the system root specified by that option. ! `--enable-shared[=PACKAGE[,...]]' Build shared versions of libraries, if shared libraries are supported on the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that *************** option. *** 736,754 **** If a list of packages is given as an argument, build shared libraries only for the listed packages. For other packages, only ! static libraries will be built. Package names currently recognized ! in the GCC tree are 'libgcc' (also known as 'gcc'), 'libstdc++' ! (not 'libstdc++-v3'), 'libffi', 'zlib', 'boehm-gc', 'ada', ! 'libada', 'libjava', 'libgo', and 'libobjc'. Note 'libiberty' does ! not support shared libraries at all. ! Use '--disable-shared' to build only static libraries. Note that ! '--disable-shared' does not accept a list of package names as ! argument, only '--enable-shared' does. ! Contrast with '--enable-host-shared', which affects _host_ code. ! '--enable-host-shared' Specify that the _host_ code should be built into position-independent machine code (with -fPIC), allowing it to be used within shared libraries, but yielding a slightly slower --- 716,734 ---- If a list of packages is given as an argument, build shared libraries only for the listed packages. For other packages, only ! static libraries will be built. Package names currently ! recognized in the GCC tree are `libgcc' (also known as `gcc'), ! `libstdc++' (not `libstdc++-v3'), `libffi', `zlib', `boehm-gc', ! `ada', `libada', `libjava', `libgo', and `libobjc'. Note ! `libiberty' does not support shared libraries at all. ! Use `--disable-shared' to build only static libraries. Note that ! `--disable-shared' does not accept a list of package names as ! argument, only `--enable-shared' does. ! Contrast with `--enable-host-shared', which affects _host_ code. ! `--enable-host-shared' Specify that the _host_ code should be built into position-independent machine code (with -fPIC), allowing it to be used within shared libraries, but yielding a slightly slower *************** option. *** 756,931 **** This option is required when building the libgccjit.so library. ! Contrast with '--enable-shared', which affects _target_ libraries. ! '--with-gnu-as' ! Specify that the compiler should assume that the assembler it finds ! is the GNU assembler. However, this does not modify the rules to ! find an assembler and will result in confusion if the assembler ! found is not actually the GNU assembler. (Confusion may also ! result if the compiler finds the GNU assembler but has not been ! configured with '--with-gnu-as'.) If you have more than one ! assembler installed on your system, you may want to use this option ! in connection with '--with-as=PATHNAME' or ! '--with-build-time-tools=PATHNAME'. The following systems are the only ones where it makes a difference whether you use the GNU assembler. On any other system, ! '--with-gnu-as' has no effect. ! * 'hppa1.0-ANY-ANY' ! * 'hppa1.1-ANY-ANY' ! * 'sparc-sun-solaris2.ANY' ! * 'sparc64-ANY-solaris2.ANY' ! '--with-as=PATHNAME' Specify that the compiler should use the assembler pointed to by PATHNAME, rather than the one found by the standard rules to find an assembler, which are: * Unless GCC is being built with a cross compiler, check the ! 'LIBEXEC/gcc/TARGET/VERSION' directory. LIBEXEC defaults to ! 'EXEC-PREFIX/libexec'; EXEC-PREFIX defaults to PREFIX, which ! defaults to '/usr/local' unless overridden by the ! '--prefix=PATHNAME' switch described above. TARGET is the ! target system triple, such as 'sparc-sun-solaris2.7', and VERSION denotes the GCC version, such as 3.0. * If the target system is the same that you are building on, check operating system specific directories (e.g. ! '/usr/ccs/bin' on Sun Solaris 2). ! * Check in the 'PATH' for a tool whose name is prefixed by the target system triple. ! * Check in the 'PATH' for a tool whose name is not prefixed by ! the target system triple, if the host and target system triple ! are the same (in other words, we use a host tool if it can be ! used for the target as well). ! You may want to use '--with-as' if no assembler is installed in the ! directories listed above, or if you have multiple assemblers installed and want to choose one that is not found by the above rules. ! '--with-gnu-ld' ! Same as '--with-gnu-as' but for the linker. ! '--with-ld=PATHNAME' ! Same as '--with-as' but for the linker. ! '--with-stabs' Specify that stabs debugging information should be used instead of ! whatever format the host normally uses. Normally GCC uses the same ! debug format as the host system. On MIPS based systems and on Alphas, you must specify whether you want GCC to create the normal ECOFF debugging format, or to use BSD-style stabs passed through the ECOFF symbol table. The normal ! ECOFF debug format cannot fully handle languages other than C. BSD ! stabs format can handle other languages, but it only works with the ! GNU debugger GDB. Normally, GCC uses the ECOFF debugging format by default; if you ! prefer BSD stabs, specify '--with-stabs' when you configure GCC. No matter which default you choose when you configure GCC, the user ! can use the '-gcoff' and '-gstabs+' options to specify explicitly the debug format for a particular compilation. ! '--with-stabs' is meaningful on the ISC system on the 386, also, if ! '--with-gas' is used. It selects use of stabs debugging information embedded in COFF output. This kind of debugging information supports C++ well; ordinary COFF debugging information does not. ! '--with-stabs' is also meaningful on 386 systems running SVR4. It selects use of stabs debugging information embedded in ELF output. The C++ compiler currently (2.6.0) does not support the DWARF debugging information normally used on 386 SVR4 platforms; stabs provide a workable alternative. This requires gas and gdb, as the normal SVR4 tools can not generate or interpret stabs. ! '--with-tls=DIALECT' Specify the default TLS dialect, for systems were there is a ! choice. For ARM targets, possible values for DIALECT are 'gnu' or ! 'gnu2', which select between the original GNU dialect and the GNU TLS descriptor-based dialect. ! '--enable-multiarch' Specify whether to enable or disable multiarch support. The default is to check for glibc start files in a multiarch location, and enable it if the files are found. The auto detection is enabled for native builds, and for cross builds configured with ! '--with-sysroot', and without '--with-native-system-header-dir'. More documentation about multiarch can be found at ! . ! '--enable-vtable-verify' Specify whether to enable or disable the vtable verification feature. Enabling this feature causes libstdc++ to be built with ! its virtual calls in verifiable mode. This means that, when linked ! with libvtv, every virtual call in libstdc++ will verify the vtable ! pointer through which the call will be made before actually making ! the call. If not linked with libvtv, the verifier will call stub ! functions (in libstdc++ itself) and do nothing. If vtable ! verification is disabled, then libstdc++ is not built with its ! virtual calls in verifiable mode at all. However the libvtv ! library will still be built (see '--disable-libvtv' to turn off ! building libvtv). '--disable-vtable-verify' is the default. ! '--disable-multilib' Specify that multiple target libraries to support different target variants, calling conventions, etc. should not be built. The default is to build a predefined set of them. ! Some targets provide finer-grained control over which multilibs are ! built (e.g., '--disable-softfloat'): ! 'arm-*-*' fpu, 26bit, underscore, interwork, biendian, nofmult. ! 'm68*-*-*' softfloat, m68881, m68000, m68020. ! 'mips*-*-*' single-float, biendian, softfloat. ! 'powerpc*-*-*, rs6000*-*-*' aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, sysv, aix. ! '--with-multilib-list=LIST' ! '--without-multilib-list' Specify what multilibs to build. Currently only implemented for arm*-*-*, sh*-*-* and x86-64-*-linux*. ! 'arm*-*-*' ! LIST is either 'default' or 'aprofile'. Specifying 'default' is equivalent to omitting this option while specifying ! 'aprofile' builds multilibs for each combination of ISA ! ('-marm' or '-mthumb'), architecture ('-march=armv7-a', ! '-march=armv7ve', or '-march=armv8-a'), FPU available (none, ! '-mfpu=vfpv3-d16', '-mfpu=neon', '-mfpu=vfpv4-d16', ! '-mfpu=neon-vfpv4' or '-mfpu=neon-fp-armv8' depending on ! architecture) and floating-point ABI ('-mfloat-abi=softfp' or ! '-mfloat-abi=hard'). ! 'sh*-*-*' ! LIST is a comma separated list of CPU names. These must be of ! the form 'sh*' or 'm*' (in which case they match the compiler ! option for that processor). The list should not contain any ! endian options - these are handled by '--with-endian'. If LIST is empty, then there will be no multilibs for extra processors. The multilib for the secondary endian remains enabled. ! As a special case, if an entry in the list starts with a '!' (exclamation point), then it is added to the list of excluded multilibs. Entries of this sort should be compatible with ! 'MULTILIB_EXCLUDES' (once the leading '!' has been stripped). ! If '--with-multilib-list' is not given, then a default set of ! multilibs is selected based on the value of '--target'. This is usually the complete set of libraries, but some targets imply a more specialized subset. --- 736,922 ---- This option is required when building the libgccjit.so library. ! Contrast with `--enable-shared', which affects _target_ libraries. ! `--with-gnu-as' ! Specify that the compiler should assume that the assembler it ! finds is the GNU assembler. However, this does not modify the ! rules to find an assembler and will result in confusion if the ! assembler found is not actually the GNU assembler. (Confusion may ! also result if the compiler finds the GNU assembler but has not ! been configured with `--with-gnu-as'.) If you have more than one ! assembler installed on your system, you may want to use this ! option in connection with `--with-as=PATHNAME' or ! `--with-build-time-tools=PATHNAME'. The following systems are the only ones where it makes a difference whether you use the GNU assembler. On any other system, ! `--with-gnu-as' has no effect. ! * `hppa1.0-ANY-ANY' ! * `hppa1.1-ANY-ANY' ! ! * `sparc-sun-solaris2.ANY' ! ! * `sparc64-ANY-solaris2.ANY' ! ! `--with-as=PATHNAME' Specify that the compiler should use the assembler pointed to by PATHNAME, rather than the one found by the standard rules to find an assembler, which are: * Unless GCC is being built with a cross compiler, check the ! `LIBEXEC/gcc/TARGET/VERSION' directory. LIBEXEC defaults to ! `EXEC-PREFIX/libexec'; EXEC-PREFIX defaults to PREFIX, which ! defaults to `/usr/local' unless overridden by the ! `--prefix=PATHNAME' switch described above. TARGET is the ! target system triple, such as `sparc-sun-solaris2.7', and VERSION denotes the GCC version, such as 3.0. * If the target system is the same that you are building on, check operating system specific directories (e.g. ! `/usr/ccs/bin' on Sun Solaris 2). ! * Check in the `PATH' for a tool whose name is prefixed by the target system triple. ! * Check in the `PATH' for a tool whose name is not prefixed by ! the target system triple, if the host and target system ! triple are the same (in other words, we use a host tool if it ! can be used for the target as well). ! You may want to use `--with-as' if no assembler is installed in ! the directories listed above, or if you have multiple assemblers installed and want to choose one that is not found by the above rules. ! `--with-gnu-ld' ! Same as `--with-gnu-as' but for the linker. ! `--with-ld=PATHNAME' ! Same as `--with-as' but for the linker. ! `--with-stabs' Specify that stabs debugging information should be used instead of ! whatever format the host normally uses. Normally GCC uses the ! same debug format as the host system. On MIPS based systems and on Alphas, you must specify whether you want GCC to create the normal ECOFF debugging format, or to use BSD-style stabs passed through the ECOFF symbol table. The normal ! ECOFF debug format cannot fully handle languages other than C. ! BSD stabs format can handle other languages, but it only works ! with the GNU debugger GDB. Normally, GCC uses the ECOFF debugging format by default; if you ! prefer BSD stabs, specify `--with-stabs' when you configure GCC. No matter which default you choose when you configure GCC, the user ! can use the `-gcoff' and `-gstabs+' options to specify explicitly the debug format for a particular compilation. ! `--with-stabs' is meaningful on the ISC system on the 386, also, if ! `--with-gas' is used. It selects use of stabs debugging information embedded in COFF output. This kind of debugging information supports C++ well; ordinary COFF debugging information does not. ! `--with-stabs' is also meaningful on 386 systems running SVR4. It selects use of stabs debugging information embedded in ELF output. The C++ compiler currently (2.6.0) does not support the DWARF debugging information normally used on 386 SVR4 platforms; stabs provide a workable alternative. This requires gas and gdb, as the normal SVR4 tools can not generate or interpret stabs. ! `--with-tls=DIALECT' Specify the default TLS dialect, for systems were there is a ! choice. For ARM targets, possible values for DIALECT are `gnu' or ! `gnu2', which select between the original GNU dialect and the GNU TLS descriptor-based dialect. ! `--enable-multiarch' Specify whether to enable or disable multiarch support. The default is to check for glibc start files in a multiarch location, and enable it if the files are found. The auto detection is enabled for native builds, and for cross builds configured with ! `--with-sysroot', and without `--with-native-system-header-dir'. More documentation about multiarch can be found at ! `https://wiki.debian.org/Multiarch'. ! `--enable-sjlj-exceptions' ! Force use of the `setjmp'/`longjmp'-based scheme for exceptions. ! `configure' ordinarily picks the correct value based on the ! platform. Only use this option if you are sure you need a ! different setting. ! ! `--enable-vtable-verify' Specify whether to enable or disable the vtable verification feature. Enabling this feature causes libstdc++ to be built with ! its virtual calls in verifiable mode. This means that, when ! linked with libvtv, every virtual call in libstdc++ will verify ! the vtable pointer through which the call will be made before ! actually making the call. If not linked with libvtv, the verifier ! will call stub functions (in libstdc++ itself) and do nothing. If ! vtable verification is disabled, then libstdc++ is not built with ! its virtual calls in verifiable mode at all. However the libvtv ! library will still be built (see `--disable-libvtv' to turn off ! building libvtv). `--disable-vtable-verify' is the default. ! `--disable-multilib' Specify that multiple target libraries to support different target variants, calling conventions, etc. should not be built. The default is to build a predefined set of them. ! Some targets provide finer-grained control over which multilibs ! are built (e.g., `--disable-softfloat'): ! `arm-*-*' fpu, 26bit, underscore, interwork, biendian, nofmult. ! `m68*-*-*' softfloat, m68881, m68000, m68020. ! `mips*-*-*' single-float, biendian, softfloat. ! `powerpc*-*-*, rs6000*-*-*' aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, sysv, aix. ! ! `--with-multilib-list=LIST' ! `--without-multilib-list' Specify what multilibs to build. Currently only implemented for arm*-*-*, sh*-*-* and x86-64-*-linux*. ! `arm*-*-*' ! LIST is either `default' or `aprofile'. Specifying `default' is equivalent to omitting this option while specifying ! `aprofile' builds multilibs for each combination of ISA ! (`-marm' or `-mthumb'), architecture (`-march=armv7-a', ! `-march=armv7ve', or `-march=armv8-a'), FPU available (none, ! `-mfpu=vfpv3-d16', `-mfpu=neon', `-mfpu=vfpv4-d16', ! `-mfpu=neon-vfpv4' or `-mfpu=neon-fp-armv8' depending on ! architecture) and floating-point ABI (`-mfloat-abi=softfp' or ! `-mfloat-abi=hard'). ! `sh*-*-*' ! LIST is a comma separated list of CPU names. These must be ! of the form `sh*' or `m*' (in which case they match the ! compiler option for that processor). The list should not ! contain any endian options - these are handled by ! `--with-endian'. If LIST is empty, then there will be no multilibs for extra processors. The multilib for the secondary endian remains enabled. ! As a special case, if an entry in the list starts with a `!' (exclamation point), then it is added to the list of excluded multilibs. Entries of this sort should be compatible with ! `MULTILIB_EXCLUDES' (once the leading `!' has been stripped). ! If `--with-multilib-list' is not given, then a default set of ! multilibs is selected based on the value of `--target'. This is usually the complete set of libraries, but some targets imply a more specialized subset. *************** option. *** 938,970 **** --with-cpu=sh4a --with-endian=little,big \ --with-multilib-list=sh4al,!mb/m4al ! 'x86-64-*-linux*' ! LIST is a comma separated list of 'm32', 'm64' and 'mx32' to enable 32-bit, 64-bit and x32 run-time libraries, respectively. If LIST is empty, then there will be no multilibs and only the default run-time library will be enabled. ! If '--with-multilib-list' is not given, then only 32-bit and 64-bit run-time libraries will be enabled. ! '--with-endian=ENDIANS' Specify what endians to use. Currently only implemented for sh*-*-*. ENDIANS may be one of the following: ! 'big' Use big endian exclusively. ! 'little' Use little endian exclusively. ! 'big,little' Use big endian by default. Provide a multilib for little endian. ! 'little,big' Use little endian by default. Provide a multilib for big endian. ! '--enable-threads' Specify that the target supports threads. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. On some systems, this is --- 929,964 ---- --with-cpu=sh4a --with-endian=little,big \ --with-multilib-list=sh4al,!mb/m4al ! `x86-64-*-linux*' ! LIST is a comma separated list of `m32', `m64' and `mx32' to enable 32-bit, 64-bit and x32 run-time libraries, respectively. If LIST is empty, then there will be no multilibs and only the default run-time library will be enabled. ! If `--with-multilib-list' is not given, then only 32-bit and 64-bit run-time libraries will be enabled. ! `--with-endian=ENDIANS' Specify what endians to use. Currently only implemented for sh*-*-*. ENDIANS may be one of the following: ! `big' Use big endian exclusively. ! ! `little' Use little endian exclusively. ! ! `big,little' Use big endian by default. Provide a multilib for little endian. ! ! `little,big' Use little endian by default. Provide a multilib for big endian. ! `--enable-threads' Specify that the target supports threads. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. On some systems, this is *************** option. *** 974,1202 **** model available will be configured for use. Beware that on some systems, GCC has not been taught what threading models are generally available for the system. In this case, ! '--enable-threads' is an alias for '--enable-threads=single'. ! '--disable-threads' Specify that threading support should be disabled for the system. ! This is an alias for '--enable-threads=single'. ! '--enable-threads=LIB' Specify that LIB is the thread support library. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. The possibilities for LIB are: ! 'aix' AIX thread support. ! 'dce' DCE thread support. ! 'lynx' LynxOS thread support. ! 'mipssde' MIPS SDE thread support. ! 'no' ! This is an alias for 'single'. ! 'posix' Generic POSIX/Unix98 thread support. ! 'rtems' RTEMS thread support. ! 'single' Disable thread support, should work for all platforms. ! 'tpf' TPF thread support. ! 'vxworks' VxWorks thread support. ! 'win32' Microsoft Win32 API thread support. ! '--enable-tls' Specify that the target supports TLS (Thread Local Storage). Usually configure can correctly determine if TLS is supported. In cases where it guesses incorrectly, TLS can be explicitly enabled ! or disabled with '--enable-tls' or '--disable-tls'. This can ! happen if the assembler supports TLS but the C library does not, or ! if the assumptions made by the configure test are incorrect. ! '--disable-tls' ! Specify that the target does not support TLS. This is an alias for ! '--enable-tls=no'. ! '--with-cpu=CPU' ! '--with-cpu-32=CPU' ! '--with-cpu-64=CPU' Specify which cpu variant the compiler should generate code for by ! default. CPU will be used as the default value of the '-mcpu=' switch. This option is only supported on some targets, including ! ARC, ARM, i386, M68k, PowerPC, and SPARC. It is mandatory for ARC. ! The '--with-cpu-32' and '--with-cpu-64' options specify separate ! default CPUs for 32-bit and 64-bit modes; these options are only ! supported for i386, x86-64, PowerPC, and SPARC. ! '--with-schedule=CPU' ! '--with-arch=CPU' ! '--with-arch-32=CPU' ! '--with-arch-64=CPU' ! '--with-tune=CPU' ! '--with-tune-32=CPU' ! '--with-tune-64=CPU' ! '--with-abi=ABI' ! '--with-fpu=TYPE' ! '--with-float=TYPE' These configure options provide default values for the ! '-mschedule=', '-march=', '-mtune=', '-mabi=', and '-mfpu=' options ! and for '-mhard-float' or '-msoft-float'. As with '--with-cpu', ! which switches will be accepted and acceptable values of the ! arguments depend on the target. ! '--with-mode=MODE' ! Specify if the compiler should default to '-marm' or '-mthumb'. This option is only supported on ARM targets. ! '--with-stack-offset=NUM' ! This option sets the default for the -mstack-offset=NUM option, and ! will thus generally also control the setting of this option for libraries. This option is only supported on Epiphany targets. ! '--with-fpmath=ISA' ! This options sets '-mfpmath=sse' by default and specifies the default ISA for floating-point arithmetics. You can select either ! 'sse' which enables '-msse2' or 'avx' which enables '-mavx' by default. This option is only supported on i386 and x86-64 targets. ! '--with-fp-32=MODE' ! On MIPS targets, set the default value for the '-mfp' option when ! using the o32 ABI. The possibilities for MODE are: ! '32' ! Use the o32 FP32 ABI extension, as with the '-mfp32' command-line option. ! 'xx' ! Use the o32 FPXX ABI extension, as with the '-mfpxx' command-line option. ! '64' ! Use the o32 FP64 ABI extension, as with the '-mfp64' command-line option. In the absence of this configuration option the default is to use the o32 FP32 ABI extension. ! '--with-odd-spreg-32' ! On MIPS targets, set the '-modd-spreg' option by default when using the o32 ABI. ! '--without-odd-spreg-32' ! On MIPS targets, set the '-mno-odd-spreg' option by default when ! using the o32 ABI. This is normally used in conjunction with ! '--with-fp-32=64' in order to target the o32 FP64A ABI extension. ! '--with-nan=ENCODING' On MIPS targets, set the default encoding convention to use for the special not-a-number (NaN) IEEE 754 floating-point data. The possibilities for ENCODING are: ! 'legacy' ! Use the legacy encoding, as with the '-mnan=legacy' command-line option. ! '2008' ! Use the 754-2008 encoding, as with the '-mnan=2008' command-line option. To use this configuration option you must have an assembler version ! installed that supports the '-mnan=' command-line option too. In the absence of this configuration option the default convention is ! the legacy encoding, as when neither of the '-mnan=2008' and ! '-mnan=legacy' command-line options has been used. ! '--with-divide=TYPE' Specify how the compiler should generate code for checking for division by zero. This option is only supported on the MIPS target. The possibilities for TYPE are: ! 'traps' Division by zero checks use conditional traps (this is the default on systems that support conditional traps). ! 'breaks' Division by zero checks use the break instruction. ! '--with-llsc' ! On MIPS targets, make '-mllsc' the default when no '-mno-llsc' option is passed. This is the default for Linux-based targets, as the kernel will emulate them if the ISA does not provide them. ! '--without-llsc' ! On MIPS targets, make '-mno-llsc' the default when no '-mllsc' option is passed. ! '--with-synci' ! On MIPS targets, make '-msynci' the default when no '-mno-synci' option is passed. ! '--without-synci' ! On MIPS targets, make '-mno-synci' the default when no '-msynci' option is passed. This is the default. ! '--with-mips-plt' On MIPS targets, make use of copy relocations and PLTs. These ! features are extensions to the traditional SVR4-based MIPS ABIs and ! require support from GNU binutils and the runtime C library. ! '--enable-__cxa_atexit' Define if you want to use __cxa_atexit, rather than atexit, to register C++ destructors for local statics and global objects. This is essential for fully standards-compliant handling of destructors, but requires __cxa_atexit in libc. This option is currently only available on systems with GNU libc. When enabled, ! this will cause '-fuse-cxa-atexit' to be passed by default. ! '--enable-gnu-indirect-function' ! Define if you want to enable the 'ifunc' attribute. This option is currently only available on systems with GNU libc on certain targets. ! '--enable-target-optspace' Specify that target libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. ! '--with-cpp-install-dir=DIRNAME' ! Specify that the user visible 'cpp' program should be installed in ! 'PREFIX/DIRNAME/cpp', in addition to BINDIR. ! '--enable-comdat' Enable COMDAT group support. This is primarily used to override the automatically detected value. ! '--enable-initfini-array' ! Force the use of sections '.init_array' and '.fini_array' (instead ! of '.init' and '.fini') for constructors and destructors. Option ! '--disable-initfini-array' has the opposite effect. If neither ! option is specified, the configure script will try to guess whether ! the '.init_array' and '.fini_array' sections are supported and, if ! they are, use them. ! '--enable-link-mutex' When building GCC, use a mutex to avoid linking the compilers for multiple languages at the same time, to avoid thrashing on build ! systems with limited free memory. The default is not to use such a ! mutex. ! '--enable-maintainer-mode' The build rules that regenerate the Autoconf and Automake output ! files as well as the GCC master message catalog 'gcc.pot' are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the catalog, configuring with ! '--enable-maintainer-mode' will enable this. Note that you need a ! recent version of the 'gettext' tools to do so. ! '--disable-bootstrap' For a native build, the default configuration is to perform a ! 3-stage bootstrap of the compiler when 'make' is invoked, testing ! that GCC can compile itself correctly. If you want to disable this ! process, you can configure with '--disable-bootstrap'. ! '--enable-bootstrap' In special cases, you may want to perform a 3-stage build even if the target and host triplets are different. This is possible when the host can run code compiled for the target (e.g. host is i686-linux, target is i486-linux). Starting from GCC 4.2, to do ! this you have to configure explicitly with '--enable-bootstrap'. ! '--enable-generated-files-in-srcdir' Neither the .c and .h files that are generated from Bison and flex nor the info manuals and man pages that are built from the .texi files are present in the SVN development tree. When building GCC --- 968,1210 ---- model available will be configured for use. Beware that on some systems, GCC has not been taught what threading models are generally available for the system. In this case, ! `--enable-threads' is an alias for `--enable-threads=single'. ! `--disable-threads' Specify that threading support should be disabled for the system. ! This is an alias for `--enable-threads=single'. ! `--enable-threads=LIB' Specify that LIB is the thread support library. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. The possibilities for LIB are: ! `aix' AIX thread support. ! ! `dce' DCE thread support. ! ! `lynx' LynxOS thread support. ! ! `mipssde' MIPS SDE thread support. ! ! `no' ! This is an alias for `single'. ! ! `posix' Generic POSIX/Unix98 thread support. ! ! `rtems' RTEMS thread support. ! ! `single' Disable thread support, should work for all platforms. ! ! `tpf' TPF thread support. ! ! `vxworks' VxWorks thread support. ! ! `win32' Microsoft Win32 API thread support. ! `--enable-tls' Specify that the target supports TLS (Thread Local Storage). Usually configure can correctly determine if TLS is supported. In cases where it guesses incorrectly, TLS can be explicitly enabled ! or disabled with `--enable-tls' or `--disable-tls'. This can ! happen if the assembler supports TLS but the C library does not, ! or if the assumptions made by the configure test are incorrect. ! `--disable-tls' ! Specify that the target does not support TLS. This is an alias ! for `--enable-tls=no'. ! `--with-cpu=CPU' ! `--with-cpu-32=CPU' ! `--with-cpu-64=CPU' Specify which cpu variant the compiler should generate code for by ! default. CPU will be used as the default value of the `-mcpu=' switch. This option is only supported on some targets, including ! ARC, ARM, i386, M68k, PowerPC, and SPARC. It is mandatory for ! ARC. The `--with-cpu-32' and `--with-cpu-64' options specify ! separate default CPUs for 32-bit and 64-bit modes; these options ! are only supported for i386, x86-64, PowerPC, and SPARC. ! `--with-schedule=CPU' ! `--with-arch=CPU' ! `--with-arch-32=CPU' ! `--with-arch-64=CPU' ! `--with-tune=CPU' ! `--with-tune-32=CPU' ! `--with-tune-64=CPU' ! `--with-abi=ABI' ! `--with-fpu=TYPE' ! `--with-float=TYPE' These configure options provide default values for the ! `-mschedule=', `-march=', `-mtune=', `-mabi=', and `-mfpu=' ! options and for `-mhard-float' or `-msoft-float'. As with ! `--with-cpu', which switches will be accepted and acceptable values ! of the arguments depend on the target. ! `--with-mode=MODE' ! Specify if the compiler should default to `-marm' or `-mthumb'. This option is only supported on ARM targets. ! `--with-stack-offset=NUM' ! This option sets the default for the -mstack-offset=NUM option, ! and will thus generally also control the setting of this option for libraries. This option is only supported on Epiphany targets. ! `--with-fpmath=ISA' ! This options sets `-mfpmath=sse' by default and specifies the default ISA for floating-point arithmetics. You can select either ! `sse' which enables `-msse2' or `avx' which enables `-mavx' by default. This option is only supported on i386 and x86-64 targets. ! `--with-fp-32=MODE' ! On MIPS targets, set the default value for the `-mfp' option when ! using the o32 ABI. The possibilities for MODE are: ! `32' ! Use the o32 FP32 ABI extension, as with the `-mfp32' command-line option. ! ! `xx' ! Use the o32 FPXX ABI extension, as with the `-mfpxx' command-line option. ! ! `64' ! Use the o32 FP64 ABI extension, as with the `-mfp64' command-line option. In the absence of this configuration option the default is to use the o32 FP32 ABI extension. ! `--with-odd-spreg-32' ! On MIPS targets, set the `-modd-spreg' option by default when using the o32 ABI. ! `--without-odd-spreg-32' ! On MIPS targets, set the `-mno-odd-spreg' option by default when ! using the o32 ABI. This is normally used in conjunction with ! `--with-fp-32=64' in order to target the o32 FP64A ABI extension. ! `--with-nan=ENCODING' On MIPS targets, set the default encoding convention to use for the special not-a-number (NaN) IEEE 754 floating-point data. The possibilities for ENCODING are: ! `legacy' ! Use the legacy encoding, as with the `-mnan=legacy' command-line option. ! ! `2008' ! Use the 754-2008 encoding, as with the `-mnan=2008' command-line option. To use this configuration option you must have an assembler version ! installed that supports the `-mnan=' command-line option too. In the absence of this configuration option the default convention is ! the legacy encoding, as when neither of the `-mnan=2008' and ! `-mnan=legacy' command-line options has been used. ! `--with-divide=TYPE' Specify how the compiler should generate code for checking for division by zero. This option is only supported on the MIPS target. The possibilities for TYPE are: ! `traps' Division by zero checks use conditional traps (this is the default on systems that support conditional traps). ! ! `breaks' Division by zero checks use the break instruction. ! `--with-llsc' ! On MIPS targets, make `-mllsc' the default when no `-mno-llsc' option is passed. This is the default for Linux-based targets, as the kernel will emulate them if the ISA does not provide them. ! `--without-llsc' ! On MIPS targets, make `-mno-llsc' the default when no `-mllsc' option is passed. ! `--with-synci' ! On MIPS targets, make `-msynci' the default when no `-mno-synci' option is passed. ! `--without-synci' ! On MIPS targets, make `-mno-synci' the default when no `-msynci' option is passed. This is the default. ! `--with-mips-plt' On MIPS targets, make use of copy relocations and PLTs. These ! features are extensions to the traditional SVR4-based MIPS ABIs ! and require support from GNU binutils and the runtime C library. ! `--enable-__cxa_atexit' Define if you want to use __cxa_atexit, rather than atexit, to register C++ destructors for local statics and global objects. This is essential for fully standards-compliant handling of destructors, but requires __cxa_atexit in libc. This option is currently only available on systems with GNU libc. When enabled, ! this will cause `-fuse-cxa-atexit' to be passed by default. ! `--enable-gnu-indirect-function' ! Define if you want to enable the `ifunc' attribute. This option is currently only available on systems with GNU libc on certain targets. ! `--enable-target-optspace' Specify that target libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. ! `--with-cpp-install-dir=DIRNAME' ! Specify that the user visible `cpp' program should be installed in ! `PREFIX/DIRNAME/cpp', in addition to BINDIR. ! `--enable-comdat' Enable COMDAT group support. This is primarily used to override the automatically detected value. ! `--enable-initfini-array' ! Force the use of sections `.init_array' and `.fini_array' (instead ! of `.init' and `.fini') for constructors and destructors. Option ! `--disable-initfini-array' has the opposite effect. If neither ! option is specified, the configure script will try to guess ! whether the `.init_array' and `.fini_array' sections are supported ! and, if they are, use them. ! `--enable-link-mutex' When building GCC, use a mutex to avoid linking the compilers for multiple languages at the same time, to avoid thrashing on build ! systems with limited free memory. The default is not to use such ! a mutex. ! `--enable-maintainer-mode' The build rules that regenerate the Autoconf and Automake output ! files as well as the GCC master message catalog `gcc.pot' are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the catalog, configuring with ! `--enable-maintainer-mode' will enable this. Note that you need a ! recent version of the `gettext' tools to do so. ! `--disable-bootstrap' For a native build, the default configuration is to perform a ! 3-stage bootstrap of the compiler when `make' is invoked, testing ! that GCC can compile itself correctly. If you want to disable ! this process, you can configure with `--disable-bootstrap'. ! `--enable-bootstrap' In special cases, you may want to perform a 3-stage build even if the target and host triplets are different. This is possible when the host can run code compiled for the target (e.g. host is i686-linux, target is i486-linux). Starting from GCC 4.2, to do ! this you have to configure explicitly with `--enable-bootstrap'. ! `--enable-generated-files-in-srcdir' Neither the .c and .h files that are generated from Bison and flex nor the info manuals and man pages that are built from the .texi files are present in the SVN development tree. When building GCC *************** option. *** 1204,1386 **** generated files are placed in your build directory, which allows for the source to be in a readonly directory. ! If you configure with '--enable-generated-files-in-srcdir' then those generated files will go into the source directory. This is mainly intended for generating release or prerelease tarballs of the GCC sources, since it is not a requirement that the users of source releases to have flex, Bison, or makeinfo. ! '--enable-version-specific-runtime-libs' Specify that runtime libraries should be installed in the compiler ! specific subdirectory ('LIBDIR/gcc') rather than the usual places. ! In addition, 'libstdc++''s include files will be installed into ! 'LIBDIR' unless you overruled it by using ! '--with-gxx-include-dir=DIRNAME'. Using this option is particularly useful if you intend to use several versions of GCC in ! parallel. This is currently supported by 'libgfortran', 'libjava', ! 'libstdc++', and 'libobjc'. ! '--with-aix-soname='aix', 'svr4' or 'both'' ! Traditional AIX shared library versioning (versioned 'Shared ! Object' files as members of unversioned 'Archive Library' files ! named 'lib.a') causes numerous headaches for package managers. ! However, 'Import Files' as members of 'Archive Library' files allow ! for *filename-based versioning* of shared libraries as seen on ! Linux/SVR4, where this is called the "SONAME". But as they prevent ! static linking, 'Import Files' may be used with 'Runtime Linking' ! only, where the linker does search for 'libNAME.so' before ! 'libNAME.a' library filenames with the '-lNAME' linker flag. For detailed information please refer to the AIX ld Command reference. As long as shared library creation is enabled, upon: ! '--with-aix-soname=aix' ! '--with-aix-soname=both' ! A (traditional AIX) 'Shared Archive Library' file is created: ! * using the 'libNAME.a' filename scheme ! * with the 'Shared Object' file as archive member named ! 'libNAME.so.V' (except for 'libgcc_s', where the 'Shared ! Object' file is named 'shr.o' for backwards compatibility), which - is used for runtime loading from inside the ! 'libNAME.a' file - is used for dynamic loading via ! 'dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER)' - is used for shared linking ! - is used for static linking, so no separate 'Static ! Archive Library' file is needed ! '--with-aix-soname=both' ! '--with-aix-soname=svr4' ! A (second) 'Shared Archive Library' file is created: ! * using the 'libNAME.so.V' filename scheme ! * with the 'Shared Object' file as archive member named ! 'shr.o', which ! - is created with the '-G linker flag' ! - has the 'F_LOADONLY' flag set - is used for runtime loading from inside the ! 'libNAME.so.V' file - is used for dynamic loading via ! 'dlopen("libNAME.so.V(shr.o)", RTLD_MEMBER)' ! * with the 'Import File' as archive member named 'shr.imp', which ! - refers to 'libNAME.so.V(shr.o)' as the "SONAME", to ! be recorded in the 'Loader Section' of subsequent ! binaries ! - indicates whether 'libNAME.so.V(shr.o)' is 32 or 64 bit - lists all the public symbols exported by ! 'lib.so.V(shr.o)', eventually decorated with the ! ''weak' Keyword' - is necessary for shared linking against ! 'lib.so.V(shr.o)' ! A symbolic link using the 'libNAME.so' filename scheme is created: ! * pointing to the 'libNAME.so.V' 'Shared Archive Library' file ! * to permit the 'ld Command' to find 'lib.so.V(shr.imp)' ! via the '-lNAME' argument (requires 'Runtime Linking' to ! be enabled) ! * to permit dynamic loading of 'lib.so.V(shr.o)' without ! the need to specify the version number via ! 'dlopen("libNAME.so(shr.o)", RTLD_MEMBER)' As long as static library creation is enabled, upon: ! '--with-aix-soname=svr4' ! A 'Static Archive Library' is created: ! * using the 'libNAME.a' filename scheme ! * with all the 'Static Object' files as archive members, which - are used for static linking ! While the aix-soname='svr4' option does not create 'Shared Object' ! files as members of unversioned 'Archive Library' files any more, ! package managers still are responsible to transfer 'Shared Object' files found as member of a previously installed unversioned ! 'Archive Library' file into the newly installed 'Archive Library' file with the same filename. ! _WARNING:_ Creating 'Shared Object' files with 'Runtime Linking' ! enabled may bloat the TOC, eventually leading to 'TOC overflow' ! errors, requiring the use of either the '-Wl,-bbigtoc' linker flag ! (seen to break with the 'GDB' debugger) or some of the TOC-related ! compiler flags, *Note RS/6000 and PowerPC Options: (gcc)RS/6000 and ! PowerPC Options. ! '--with-aix-soname' is currently supported by 'libgcc_s' only, so this option is still experimental and not for normal use yet. ! Default is the traditional behavior '--with-aix-soname='aix''. ! '--enable-languages=LANG1,LANG2,...' Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for ! LANGN you can issue the following command in the 'gcc' directory of ! your GCC source tree: grep ^language= */config-lang.in ! Currently, you can use any of the following: 'all', 'ada', 'c', ! 'c++', 'fortran', 'go', 'java', 'jit', 'lto', 'objc', 'obj-c++'. Building the Ada compiler has special requirements, see below. If ! you do not pass this flag, or specify the option 'all', then all ! default languages available in the 'gcc' sub-tree will be configured. Ada, Go, Jit, and Objective-C++ are not default languages. LTO is not a default language, but is built by default ! because '--enable-lto' is enabled by default. The other languages are default languages. ! '--enable-stage1-languages=LANG1,LANG2,...' Specify that a particular subset of compilers and their runtime ! libraries should be built with the system C compiler during stage 1 ! of the bootstrap process, rather than only in later stages with the ! bootstrapped C compiler. The list of valid values is the same as ! for '--enable-languages', and the option 'all' will select all of ! the languages enabled by '--enable-languages'. This option is primarily useful for GCC development; for instance, when a development version of the compiler cannot bootstrap due to ! compiler bugs, or when one is debugging front ends other than the C ! front end. When this option is used, one can then build the target ! libraries for the specified languages with the stage-1 compiler by ! using 'make stage1-bubble all-target', or run the testsuite on the ! stage-1 compiler for the specified languages using 'make ! stage1-start check-gcc'. ! '--disable-libada' Specify that the run-time libraries and tools used by GNAT should not be built. This can be useful for debugging, or for compatibility with previous Ada build procedures, when it was ! required to explicitly do a 'make -C gcc gnatlib_and_tools'. ! '--disable-libsanitizer' Specify that the run-time libraries for the various sanitizers should not be built. ! '--disable-libssp' Specify that the run-time libraries for stack smashing protection should not be built. ! '--disable-libquadmath' Specify that the GCC quad-precision math library should not be built. On some systems, the library is required to be linkable when building the Fortran front end, unless ! '--disable-libquadmath-support' is used. ! '--disable-libquadmath-support' ! Specify that the Fortran front end and 'libgfortran' do not add ! support for 'libquadmath' on systems supporting it. ! '--disable-libgomp' Specify that the GNU Offloading and Multi Processing Runtime Library should not be built. ! '--disable-libvtv' Specify that the run-time libraries used by vtable verification should not be built. ! '--with-dwarf2' Specify that the compiler should use DWARF 2 debugging information as the default. ! '--with-advance-toolchain=AT' On 64-bit PowerPC Linux systems, configure the compiler to use the header files, library files, and the dynamic linker from the Advance Toolchain release AT instead of the default versions that --- 1212,1416 ---- generated files are placed in your build directory, which allows for the source to be in a readonly directory. ! If you configure with `--enable-generated-files-in-srcdir' then those generated files will go into the source directory. This is mainly intended for generating release or prerelease tarballs of the GCC sources, since it is not a requirement that the users of source releases to have flex, Bison, or makeinfo. ! `--enable-version-specific-runtime-libs' Specify that runtime libraries should be installed in the compiler ! specific subdirectory (`LIBDIR/gcc') rather than the usual places. ! In addition, `libstdc++''s include files will be installed into ! `LIBDIR' unless you overruled it by using ! `--with-gxx-include-dir=DIRNAME'. Using this option is particularly useful if you intend to use several versions of GCC in ! parallel. This is currently supported by `libgfortran', ! `libjava', `libstdc++', and `libobjc'. ! `--with-aix-soname=`aix', `svr4' or `both'' ! Traditional AIX shared library versioning (versioned `Shared ! Object' files as members of unversioned `Archive Library' files ! named `lib.a') causes numerous headaches for package managers. ! However, `Import Files' as members of `Archive Library' files ! allow for *filename-based versioning* of shared libraries as seen ! on Linux/SVR4, where this is called the "SONAME". But as they ! prevent static linking, `Import Files' may be used with `Runtime ! Linking' only, where the linker does search for `libNAME.so' ! before `libNAME.a' library filenames with the `-lNAME' linker flag. For detailed information please refer to the AIX ld Command reference. As long as shared library creation is enabled, upon: ! `--with-aix-soname=aix' ! ! `--with-aix-soname=both' ! A (traditional AIX) `Shared Archive Library' file is created: ! * using the `libNAME.a' filename scheme ! ! * with the `Shared Object' file as archive member named ! `libNAME.so.V' (except for `libgcc_s', where the `Shared ! Object' file is named `shr.o' for backwards compatibility), which - is used for runtime loading from inside the ! `libNAME.a' file ! - is used for dynamic loading via ! `dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER)' ! - is used for shared linking ! ! - is used for static linking, so no separate `Static ! Archive Library' file is needed ! ! ! `--with-aix-soname=both' ! ! `--with-aix-soname=svr4' ! A (second) `Shared Archive Library' file is created: ! * using the `libNAME.so.V' filename scheme ! ! * with the `Shared Object' file as archive member named ! `shr.o', which ! - is created with the `-G linker flag' ! ! - has the `F_LOADONLY' flag set ! - is used for runtime loading from inside the ! `libNAME.so.V' file ! - is used for dynamic loading via ! `dlopen("libNAME.so.V(shr.o)", RTLD_MEMBER)' ! ! ! * with the `Import File' as archive member named `shr.imp', which ! - refers to `libNAME.so.V(shr.o)' as the "SONAME", to ! be recorded in the `Loader Section' of ! subsequent binaries ! ! - indicates whether `libNAME.so.V(shr.o)' is 32 or 64 bit + - lists all the public symbols exported by ! `lib.so.V(shr.o)', eventually decorated with the ! ``weak' Keyword' ! - is necessary for shared linking against ! `lib.so.V(shr.o)' ! ! A symbolic link using the `libNAME.so' filename scheme is created: ! * pointing to the `libNAME.so.V' `Shared Archive Library' file ! ! * to permit the `ld Command' to find `lib.so.V(shr.imp)' ! via the `-lNAME' argument (requires `Runtime Linking' ! to be enabled) ! ! * to permit dynamic loading of `lib.so.V(shr.o)' without ! the need to specify the version number via ! `dlopen("libNAME.so(shr.o)", RTLD_MEMBER)' As long as static library creation is enabled, upon: ! `--with-aix-soname=svr4' ! A `Static Archive Library' is created: ! * using the `libNAME.a' filename scheme ! ! * with all the `Static Object' files as archive members, which - are used for static linking ! ! While the aix-soname=`svr4' option does not create `Shared Object' ! files as members of unversioned `Archive Library' files any more, ! package managers still are responsible to transfer `Shared Object' files found as member of a previously installed unversioned ! `Archive Library' file into the newly installed `Archive Library' file with the same filename. ! _WARNING:_ Creating `Shared Object' files with `Runtime Linking' ! enabled may bloat the TOC, eventually leading to `TOC overflow' ! errors, requiring the use of either the `-Wl,-bbigtoc' linker flag ! (seen to break with the `GDB' debugger) or some of the TOC-related ! compiler flags, *Note RS/6000 and PowerPC Options: (gcc)RS/6000 ! and PowerPC Options. ! `--with-aix-soname' is currently supported by `libgcc_s' only, so this option is still experimental and not for normal use yet. ! Default is the traditional behavior `--with-aix-soname=`aix''. ! `--enable-languages=LANG1,LANG2,...' Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for ! LANGN you can issue the following command in the `gcc' directory ! of your GCC source tree: grep ^language= */config-lang.in ! Currently, you can use any of the following: `all', `ada', `c', ! `c++', `fortran', `go', `java', `jit', `lto', `objc', `obj-c++'. Building the Ada compiler has special requirements, see below. If ! you do not pass this flag, or specify the option `all', then all ! default languages available in the `gcc' sub-tree will be configured. Ada, Go, Jit, and Objective-C++ are not default languages. LTO is not a default language, but is built by default ! because `--enable-lto' is enabled by default. The other languages are default languages. ! `--enable-stage1-languages=LANG1,LANG2,...' Specify that a particular subset of compilers and their runtime ! libraries should be built with the system C compiler during stage ! 1 of the bootstrap process, rather than only in later stages with ! the bootstrapped C compiler. The list of valid values is the same ! as for `--enable-languages', and the option `all' will select all ! of the languages enabled by `--enable-languages'. This option is primarily useful for GCC development; for instance, when a development version of the compiler cannot bootstrap due to ! compiler bugs, or when one is debugging front ends other than the ! C front end. When this option is used, one can then build the ! target libraries for the specified languages with the stage-1 ! compiler by using `make stage1-bubble all-target', or run the ! testsuite on the stage-1 compiler for the specified languages ! using `make stage1-start check-gcc'. ! `--disable-libada' Specify that the run-time libraries and tools used by GNAT should not be built. This can be useful for debugging, or for compatibility with previous Ada build procedures, when it was ! required to explicitly do a `make -C gcc gnatlib_and_tools'. ! `--disable-libsanitizer' Specify that the run-time libraries for the various sanitizers should not be built. ! `--disable-libssp' Specify that the run-time libraries for stack smashing protection should not be built. ! `--disable-libquadmath' Specify that the GCC quad-precision math library should not be built. On some systems, the library is required to be linkable when building the Fortran front end, unless ! `--disable-libquadmath-support' is used. ! `--disable-libquadmath-support' ! Specify that the Fortran front end and `libgfortran' do not add ! support for `libquadmath' on systems supporting it. ! `--disable-libgomp' Specify that the GNU Offloading and Multi Processing Runtime Library should not be built. ! `--disable-libvtv' Specify that the run-time libraries used by vtable verification should not be built. ! `--with-dwarf2' Specify that the compiler should use DWARF 2 debugging information as the default. ! `--with-advance-toolchain=AT' On 64-bit PowerPC Linux systems, configure the compiler to use the header files, library files, and the dynamic linker from the Advance Toolchain release AT instead of the default versions that *************** option. *** 1388,1395 **** intended for the developers of GCC, and it is not intended for general use. ! '--enable-targets=all' ! '--enable-targets=TARGET_LIST' Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers. These are compilers that are able to generate either 64-bit or 32-bit code. Typically, the corresponding 32-bit target, e.g. --- 1418,1425 ---- intended for the developers of GCC, and it is not intended for general use. ! `--enable-targets=all' ! `--enable-targets=TARGET_LIST' Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers. These are compilers that are able to generate either 64-bit or 32-bit code. Typically, the corresponding 32-bit target, e.g. *************** option. *** 1402,1700 **** affects sparc-linux, powerpc-linux, x86-linux, mips-linux and s390-linux. ! '--enable-default-pie' ! Turn on '-fPIE' and '-pie' by default. ! '--enable-secureplt' ! This option enables '-msecure-plt' by default for powerpc-linux. *Note RS/6000 and PowerPC Options: (gcc)RS/6000 and PowerPC Options, ! '--enable-default-ssp' ! Turn on '-fstack-protector-strong' by default. ! '--enable-cld' ! This option enables '-mcld' by default for 32-bit x86 targets. *Note i386 and x86-64 Options: (gcc)i386 and x86-64 Options, ! '--enable-win32-registry' ! '--enable-win32-registry=KEY' ! '--disable-win32-registry' ! The '--enable-win32-registry' option enables Microsoft Windows-hosted GCC to look up installations paths in the registry using the following key: ! HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\KEY KEY defaults to GCC version number, and can be overridden by the ! '--enable-win32-registry=KEY' option. Vendors and distributors who ! use custom installers are encouraged to provide a different key, ! perhaps one comprised of vendor name and GCC version number, to ! avoid conflict with existing installations. This feature is enabled by default, and can be disabled by ! '--disable-win32-registry' option. This option has no effect on the other hosts. ! '--nfp' Specify that the machine does not have a floating point unit. This ! option only applies to 'm68k-sun-sunosN'. On any other system, ! '--nfp' has no effect. ! '--enable-werror' ! '--disable-werror' ! '--enable-werror=yes' ! '--enable-werror=no' When you specify this option, it controls whether certain files in ! the compiler are built with '-Werror' in bootstrap stage2 and ! later. If you don't specify it, '-Werror' is turned on for the main development trunk. However it defaults to off for release branches and final releases. The specific files which get ! '-Werror' are controlled by the Makefiles. ! '--enable-checking' ! '--enable-checking=LIST' When you specify this option, the compiler is built to perform ! internal consistency checks of the requested complexity. This does ! not change the generated code, but adds error checking within the ! compiler. This will slow down the compiler and may only work ! properly if you are building the compiler with GCC. This is 'yes' ! by default when building from SVN or snapshots, but 'release' for ! releases. The default for building the stage1 compiler is 'yes'. More control over the checks may be had by specifying LIST. The ! categories of checks available are 'yes' (most common checks ! 'assert,misc,tree,gc,rtlflag,runtime'), 'no' (no checks at all), ! 'all' (all but 'valgrind'), 'release' (cheapest checks ! 'assert,runtime') or 'none' (same as 'no'). Individual checks can ! be enabled with these flags 'assert', 'df', 'fold', 'gc', 'gcac' ! 'misc', 'rtl', 'rtlflag', 'runtime', 'tree', and 'valgrind'. ! The 'valgrind' check requires the external 'valgrind' simulator, ! available from . The 'df', 'rtl', 'gcac' and ! 'valgrind' checks are very expensive. To disable all checking, ! '--disable-checking' or '--enable-checking=none' must be explicitly ! requested. Disabling assertions will make the compiler and runtime ! slightly faster but increase the risk of undetected internal errors ! causing wrong code to be generated. ! '--disable-stage1-checking' ! '--enable-stage1-checking' ! '--enable-stage1-checking=LIST' ! If no '--enable-checking' option is specified the stage1 compiler ! will be built with 'yes' checking enabled, otherwise the stage1 ! checking flags are the same as specified by '--enable-checking'. To build the stage1 compiler with different checking options use ! '--enable-stage1-checking'. The list of checking options is the ! same as for '--enable-checking'. If your system is too slow or too ! small to bootstrap a released compiler with checking for stage1 ! enabled, you can use '--disable-stage1-checking' to disable checking for the stage1 compiler. ! '--enable-coverage' ! '--enable-coverage=LEVEL' With this option, the compiler is built to collect self coverage information, every time it is run. This is for internal development purposes, and only works when the compiler is being built with gcc. The LEVEL argument controls whether the compiler ! is built optimized or not, values are 'opt' and 'noopt'. For ! coverage analysis you want to disable optimization, for performance ! analysis you want to enable optimization. When coverage is ! enabled, the default level is without optimization. ! '--enable-gather-detailed-mem-stats' When this option is specified more detailed information on memory allocation is gathered. This information is printed when using ! '-fmem-report'. ! '--enable-valgrind-annotations' Mark selected memory related operations in the compiler when run under valgrind to suppress false positives. ! '--enable-nls' ! '--disable-nls' ! The '--enable-nls' option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not ! doing a canadian cross build. The '--disable-nls' option disables NLS. ! '--with-included-gettext' ! If NLS is enabled, the '--with-included-gettext' option causes the ! build procedure to prefer its copy of GNU 'gettext'. ! '--with-catgets' ! If NLS is enabled, and if the host lacks 'gettext' but has the ! inferior 'catgets' interface, the GCC build procedure normally ! ignores 'catgets' and instead uses GCC's copy of the GNU 'gettext' ! library. The '--with-catgets' option causes the build procedure to ! use the host's 'catgets' in this situation. ! '--with-libiconv-prefix=DIR' ! Search for libiconv header files in 'DIR/include' and libiconv ! library files in 'DIR/lib'. ! '--enable-obsolete' Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. ! All support for systems which have been obsoleted in one release of ! GCC is removed entirely in the next major release, unless someone ! steps forward to maintain the port. ! '--enable-decimal-float' ! '--enable-decimal-float=yes' ! '--enable-decimal-float=no' ! '--enable-decimal-float=bid' ! '--enable-decimal-float=dpd' ! '--disable-decimal-float' Enable (or disable) support for the C decimal floating point extension that is in the IEEE 754-2008 standard. This is enabled by default only on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also support it, but require the user to specifically enable it. You can optionally control which decimal ! floating point format is used (either 'bid' or 'dpd'). The 'bid' (binary integer decimal) format is default on i386 and x86_64 ! systems, and the 'dpd' (densely packed decimal) format is default on PowerPC systems. ! '--enable-fixed-point' ! '--disable-fixed-point' Enable (or disable) support for C fixed-point arithmetic. This option is enabled by default for some targets (such as MIPS) which have hardware-support for fixed-point operations. On other targets, you may enable this option manually. ! '--with-long-double-128' ! Specify if 'long double' type should be 128-bit by default on selected GNU/Linux architectures. If using ! '--without-long-double-128', 'long double' will be by default ! 64-bit, the same as 'double' type. When neither of these configure ! options are used, the default will be 128-bit 'long double' when ! built against GNU C Library 2.4 and later, 64-bit 'long double' ! otherwise. ! '--enable-fdpic' On SH Linux systems, generate ELF FDPIC code. ! '--with-gmp=PATHNAME' ! '--with-gmp-include=PATHNAME' ! '--with-gmp-lib=PATHNAME' ! '--with-mpfr=PATHNAME' ! '--with-mpfr-include=PATHNAME' ! '--with-mpfr-lib=PATHNAME' ! '--with-mpc=PATHNAME' ! '--with-mpc-include=PATHNAME' ! '--with-mpc-lib=PATHNAME' If you want to build GCC but do not have the GMP library, the MPFR library and/or the MPC library installed in a standard location and do not have their sources present in the GCC source tree then you can explicitly specify the directory where they are installed ! ('--with-gmp=GMPINSTALLDIR', '--with-mpfr=MPFRINSTALLDIR', ! '--with-mpc=MPCINSTALLDIR'). The '--with-gmp=GMPINSTALLDIR' option ! is shorthand for '--with-gmp-lib=GMPINSTALLDIR/lib' and ! '--with-gmp-include=GMPINSTALLDIR/include'. Likewise the ! '--with-mpfr=MPFRINSTALLDIR' option is shorthand for ! '--with-mpfr-lib=MPFRINSTALLDIR/lib' and ! '--with-mpfr-include=MPFRINSTALLDIR/include', also the ! '--with-mpc=MPCINSTALLDIR' option is shorthand for ! '--with-mpc-lib=MPCINSTALLDIR/lib' and ! '--with-mpc-include=MPCINSTALLDIR/include'. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. You might also need to ensure the shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path ! variable ('LD_LIBRARY_PATH' on GNU/Linux and Solaris systems). These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. ! '--with-isl=PATHNAME' ! '--with-isl-include=PATHNAME' ! '--with-isl-lib=PATHNAME' ! If you do not have the isl library installed in a standard location ! and you want to build GCC, you can explicitly specify the directory ! where it is installed ('--with-isl=ISLINSTALLDIR'). The ! '--with-isl=ISLINSTALLDIR' option is shorthand for ! '--with-isl-lib=ISLINSTALLDIR/lib' and ! '--with-isl-include=ISLINSTALLDIR/include'. If this shorthand ! assumption is not correct, you can use the explicit include and lib ! options directly. These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. ! '--with-stage1-ldflags=FLAGS' This option may be used to set linker flags to be used when linking ! stage 1 of GCC. These are also used when linking GCC if configured ! with '--disable-bootstrap'. If '--with-stage1-libs' is not set to ! a value, then the default is '-static-libstdc++ -static-libgcc', if ! supported. ! '--with-stage1-libs=LIBS' This option may be used to set libraries to be used when linking ! stage 1 of GCC. These are also used when linking GCC if configured ! with '--disable-bootstrap'. ! '--with-boot-ldflags=FLAGS' This option may be used to set linker flags to be used when linking ! stage 2 and later when bootstrapping GCC. If -with-boot-libs is not ! is set to a value, then the default is '-static-libstdc++ -static-libgcc'. ! '--with-boot-libs=LIBS' This option may be used to set libraries to be used when linking stage 2 and later when bootstrapping GCC. ! '--with-debug-prefix-map=MAP' ! Convert source directory names using '-fdebug-prefix-map' when ! building runtime libraries. 'MAP' is a space-separated list of ! maps of the form 'OLD=NEW'. ! '--enable-linker-build-id' ! Tells GCC to pass '--build-id' option to the linker for all final ! links (links performed without the '-r' or '--relocatable' option), ! if the linker supports it. If you specify ! '--enable-linker-build-id', but your linker does not support ! '--build-id' option, a warning is issued and the ! '--enable-linker-build-id' option is ignored. The default is off. ! '--with-linker-hash-style=CHOICE' ! Tells GCC to pass '--hash-style=CHOICE' option to the linker for ! all final links. CHOICE can be one of 'sysv', 'gnu', and 'both' ! where 'sysv' is the default. ! '--enable-gnu-unique-object' ! '--disable-gnu-unique-object' Tells GCC to use the gnu_unique_object relocation for C++ template static data members and inline function local statics. Enabled by ! default for a toolchain with an assembler that accepts it and GLIBC ! 2.11 or above, otherwise disabled. ! '--with-diagnostics-color=CHOICE' ! Tells GCC to use CHOICE as the default for '-fdiagnostics-color=' ! option (if not used explicitly on the command line). CHOICE can be ! one of 'never', 'auto', 'always', and 'auto-if-env' where 'auto' is ! the default. 'auto-if-env' means that '-fdiagnostics-color=auto' ! will be the default if 'GCC_COLORS' is present and non-empty in the ! environment, and '-fdiagnostics-color=never' otherwise. ! '--enable-lto' ! '--disable-lto' ! Enable support for link-time optimization (LTO). This is enabled by ! default, and may be disabled using '--disable-lto'. ! '--enable-linker-plugin-configure-flags=FLAGS' ! '--enable-linker-plugin-flags=FLAGS' By default, linker plugins (such as the LTO plugin) are built for the host system architecture. For the case that the linker has a different (but run-time compatible) architecture, these flags can be specified to build plugins that are compatible to the linker. For example, if you are building GCC for a 64-bit x86_64 ! ('x86_64-unknown-linux-gnu') host system, but have a 32-bit x86 ! GNU/Linux ('i686-pc-linux-gnu') linker executable (which is executable on the former system), you can configure GCC as follows for getting compatible linker plugins: --- 1432,1731 ---- affects sparc-linux, powerpc-linux, x86-linux, mips-linux and s390-linux. ! `--enable-default-pie' ! Turn on `-fPIE' and `-pie' by default. ! `--enable-secureplt' ! This option enables `-msecure-plt' by default for powerpc-linux. *Note RS/6000 and PowerPC Options: (gcc)RS/6000 and PowerPC Options, ! `--enable-default-ssp' ! Turn on `-fstack-protector-strong' by default. ! `--enable-cld' ! This option enables `-mcld' by default for 32-bit x86 targets. *Note i386 and x86-64 Options: (gcc)i386 and x86-64 Options, ! `--enable-win32-registry' ! `--enable-win32-registry=KEY' ! `--disable-win32-registry' ! The `--enable-win32-registry' option enables Microsoft Windows-hosted GCC to look up installations paths in the registry using the following key: ! `HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\KEY' KEY defaults to GCC version number, and can be overridden by the ! `--enable-win32-registry=KEY' option. Vendors and distributors ! who use custom installers are encouraged to provide a different ! key, perhaps one comprised of vendor name and GCC version number, ! to avoid conflict with existing installations. This feature is enabled by default, and can be disabled by ! `--disable-win32-registry' option. This option has no effect on the other hosts. ! `--nfp' Specify that the machine does not have a floating point unit. This ! option only applies to `m68k-sun-sunosN'. On any other system, ! `--nfp' has no effect. ! `--enable-werror' ! `--disable-werror' ! `--enable-werror=yes' ! `--enable-werror=no' When you specify this option, it controls whether certain files in ! the compiler are built with `-Werror' in bootstrap stage2 and ! later. If you don't specify it, `-Werror' is turned on for the main development trunk. However it defaults to off for release branches and final releases. The specific files which get ! `-Werror' are controlled by the Makefiles. ! `--enable-checking' ! `--enable-checking=LIST' When you specify this option, the compiler is built to perform ! internal consistency checks of the requested complexity. This ! does not change the generated code, but adds error checking within ! the compiler. This will slow down the compiler and may only work ! properly if you are building the compiler with GCC. This is `yes' ! by default when building from SVN or snapshots, but `release' for ! releases. The default for building the stage1 compiler is `yes'. More control over the checks may be had by specifying LIST. The ! categories of checks available are `yes' (most common checks ! `assert,misc,tree,gc,rtlflag,runtime'), `no' (no checks at all), ! `all' (all but `valgrind'), `release' (cheapest checks ! `assert,runtime') or `none' (same as `no'). Individual checks can ! be enabled with these flags `assert', `df', `fold', `gc', `gcac' ! `misc', `rtl', `rtlflag', `runtime', `tree', and `valgrind'. ! The `valgrind' check requires the external `valgrind' simulator, ! available from `http://valgrind.org/'. The `df', `rtl', `gcac' ! and `valgrind' checks are very expensive. To disable all ! checking, `--disable-checking' or `--enable-checking=none' must be ! explicitly requested. Disabling assertions will make the compiler ! and runtime slightly faster but increase the risk of undetected ! internal errors causing wrong code to be generated. ! `--disable-stage1-checking' ! `--enable-stage1-checking' ! `--enable-stage1-checking=LIST' ! If no `--enable-checking' option is specified the stage1 compiler ! will be built with `yes' checking enabled, otherwise the stage1 ! checking flags are the same as specified by `--enable-checking'. To build the stage1 compiler with different checking options use ! `--enable-stage1-checking'. The list of checking options is the ! same as for `--enable-checking'. If your system is too slow or ! too small to bootstrap a released compiler with checking for ! stage1 enabled, you can use `--disable-stage1-checking' to disable checking for the stage1 compiler. ! `--enable-coverage' ! `--enable-coverage=LEVEL' With this option, the compiler is built to collect self coverage information, every time it is run. This is for internal development purposes, and only works when the compiler is being built with gcc. The LEVEL argument controls whether the compiler ! is built optimized or not, values are `opt' and `noopt'. For ! coverage analysis you want to disable optimization, for ! performance analysis you want to enable optimization. When ! coverage is enabled, the default level is without optimization. ! `--enable-gather-detailed-mem-stats' When this option is specified more detailed information on memory allocation is gathered. This information is printed when using ! `-fmem-report'. ! `--enable-valgrind-annotations' Mark selected memory related operations in the compiler when run under valgrind to suppress false positives. ! `--enable-nls' ! `--disable-nls' ! The `--enable-nls' option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not ! doing a canadian cross build. The `--disable-nls' option disables NLS. ! `--with-included-gettext' ! If NLS is enabled, the `--with-included-gettext' option causes the ! build procedure to prefer its copy of GNU `gettext'. ! `--with-catgets' ! If NLS is enabled, and if the host lacks `gettext' but has the ! inferior `catgets' interface, the GCC build procedure normally ! ignores `catgets' and instead uses GCC's copy of the GNU `gettext' ! library. The `--with-catgets' option causes the build procedure ! to use the host's `catgets' in this situation. ! `--with-libiconv-prefix=DIR' ! Search for libiconv header files in `DIR/include' and libiconv ! library files in `DIR/lib'. ! `--enable-obsolete' Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. ! All support for systems which have been obsoleted in one release ! of GCC is removed entirely in the next major release, unless ! someone steps forward to maintain the port. ! `--enable-decimal-float' ! `--enable-decimal-float=yes' ! `--enable-decimal-float=no' ! `--enable-decimal-float=bid' ! `--enable-decimal-float=dpd' ! `--disable-decimal-float' Enable (or disable) support for the C decimal floating point extension that is in the IEEE 754-2008 standard. This is enabled by default only on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also support it, but require the user to specifically enable it. You can optionally control which decimal ! floating point format is used (either `bid' or `dpd'). The `bid' (binary integer decimal) format is default on i386 and x86_64 ! systems, and the `dpd' (densely packed decimal) format is default on PowerPC systems. ! `--enable-fixed-point' ! `--disable-fixed-point' Enable (or disable) support for C fixed-point arithmetic. This option is enabled by default for some targets (such as MIPS) which have hardware-support for fixed-point operations. On other targets, you may enable this option manually. ! `--with-long-double-128' ! Specify if `long double' type should be 128-bit by default on selected GNU/Linux architectures. If using ! `--without-long-double-128', `long double' will be by default ! 64-bit, the same as `double' type. When neither of these ! configure options are used, the default will be 128-bit `long ! double' when built against GNU C Library 2.4 and later, 64-bit ! `long double' otherwise. ! `--enable-fdpic' On SH Linux systems, generate ELF FDPIC code. ! `--with-gmp=PATHNAME' ! `--with-gmp-include=PATHNAME' ! `--with-gmp-lib=PATHNAME' ! `--with-mpfr=PATHNAME' ! `--with-mpfr-include=PATHNAME' ! `--with-mpfr-lib=PATHNAME' ! `--with-mpc=PATHNAME' ! `--with-mpc-include=PATHNAME' ! `--with-mpc-lib=PATHNAME' If you want to build GCC but do not have the GMP library, the MPFR library and/or the MPC library installed in a standard location and do not have their sources present in the GCC source tree then you can explicitly specify the directory where they are installed ! (`--with-gmp=GMPINSTALLDIR', `--with-mpfr=MPFRINSTALLDIR', ! `--with-mpc=MPCINSTALLDIR'). The `--with-gmp=GMPINSTALLDIR' ! option is shorthand for `--with-gmp-lib=GMPINSTALLDIR/lib' and ! `--with-gmp-include=GMPINSTALLDIR/include'. Likewise the ! `--with-mpfr=MPFRINSTALLDIR' option is shorthand for ! `--with-mpfr-lib=MPFRINSTALLDIR/lib' and ! `--with-mpfr-include=MPFRINSTALLDIR/include', also the ! `--with-mpc=MPCINSTALLDIR' option is shorthand for ! `--with-mpc-lib=MPCINSTALLDIR/lib' and ! `--with-mpc-include=MPCINSTALLDIR/include'. If these shorthand assumptions are not correct, you can use the explicit include and lib options directly. You might also need to ensure the shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path ! variable (`LD_LIBRARY_PATH' on GNU/Linux and Solaris systems). These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. ! `--with-isl=PATHNAME' ! `--with-isl-include=PATHNAME' ! `--with-isl-lib=PATHNAME' ! If you do not have the isl library installed in a standard ! location and you want to build GCC, you can explicitly specify the ! directory where it is installed (`--with-isl=ISLINSTALLDIR'). The ! `--with-isl=ISLINSTALLDIR' option is shorthand for ! `--with-isl-lib=ISLINSTALLDIR/lib' and ! `--with-isl-include=ISLINSTALLDIR/include'. If this shorthand ! assumption is not correct, you can use the explicit include and ! lib options directly. These flags are applicable to the host platform only. When building a cross compiler, they will not be used to configure target libraries. ! `--with-stage1-ldflags=FLAGS' This option may be used to set linker flags to be used when linking ! stage 1 of GCC. These are also used when linking GCC if ! configured with `--disable-bootstrap'. If `--with-stage1-libs' is ! not set to a value, then the default is `-static-libstdc++ ! -static-libgcc', if supported. ! `--with-stage1-libs=LIBS' This option may be used to set libraries to be used when linking ! stage 1 of GCC. These are also used when linking GCC if ! configured with `--disable-bootstrap'. ! `--with-boot-ldflags=FLAGS' This option may be used to set linker flags to be used when linking ! stage 2 and later when bootstrapping GCC. If -with-boot-libs is ! not is set to a value, then the default is `-static-libstdc++ -static-libgcc'. ! `--with-boot-libs=LIBS' This option may be used to set libraries to be used when linking stage 2 and later when bootstrapping GCC. ! `--with-debug-prefix-map=MAP' ! Convert source directory names using `-fdebug-prefix-map' when ! building runtime libraries. `MAP' is a space-separated list of ! maps of the form `OLD=NEW'. ! `--enable-linker-build-id' ! Tells GCC to pass `--build-id' option to the linker for all final ! links (links performed without the `-r' or `--relocatable' ! option), if the linker supports it. If you specify ! `--enable-linker-build-id', but your linker does not support ! `--build-id' option, a warning is issued and the ! `--enable-linker-build-id' option is ignored. The default is off. ! `--with-linker-hash-style=CHOICE' ! Tells GCC to pass `--hash-style=CHOICE' option to the linker for ! all final links. CHOICE can be one of `sysv', `gnu', and `both' ! where `sysv' is the default. ! `--enable-gnu-unique-object' ! `--disable-gnu-unique-object' Tells GCC to use the gnu_unique_object relocation for C++ template static data members and inline function local statics. Enabled by ! default for a toolchain with an assembler that accepts it and ! GLIBC 2.11 or above, otherwise disabled. ! `--with-diagnostics-color=CHOICE' ! Tells GCC to use CHOICE as the default for `-fdiagnostics-color=' ! option (if not used explicitly on the command line). CHOICE can ! be one of `never', `auto', `always', and `auto-if-env' where ! `auto' is the default. `auto-if-env' means that ! `-fdiagnostics-color=auto' will be the default if `GCC_COLORS' is ! present and non-empty in the environment, and ! `-fdiagnostics-color=never' otherwise. ! `--enable-lto' ! `--disable-lto' ! Enable support for link-time optimization (LTO). This is enabled ! by default, and may be disabled using `--disable-lto'. ! `--enable-linker-plugin-configure-flags=FLAGS' ! `--enable-linker-plugin-flags=FLAGS' By default, linker plugins (such as the LTO plugin) are built for the host system architecture. For the case that the linker has a different (but run-time compatible) architecture, these flags can be specified to build plugins that are compatible to the linker. For example, if you are building GCC for a 64-bit x86_64 ! (`x86_64-unknown-linux-gnu') host system, but have a 32-bit x86 ! GNU/Linux (`i686-pc-linux-gnu') linker executable (which is executable on the former system), you can configure GCC as follows for getting compatible linker plugins: *************** option. *** 1703,1724 **** --enable-linker-plugin-configure-flags=--host=i686-pc-linux-gnu \ --enable-linker-plugin-flags='CC=gcc\ -m32\ -Wl,-rpath,[...]/i686-pc-linux-gnu/lib' ! '--with-plugin-ld=PATHNAME' Enable an alternate linker to be used at link-time optimization ! (LTO) link time when '-fuse-linker-plugin' is enabled. This linker ! should have plugin support such as gold starting with version 2.20 ! or GNU ld starting with version 2.21. See '-fuse-linker-plugin' ! for details. ! '--enable-canonical-system-headers' ! '--disable-canonical-system-headers' ! Enable system header path canonicalization for 'libcpp'. This can produce shorter header file paths in diagnostics and dependency ! output files, but these changed header paths may conflict with some ! compilation environments. Enabled by default, and may be disabled ! using '--disable-canonical-system-headers'. ! '--with-glibc-version=MAJOR.MINOR' Tell GCC that when the GNU C Library (glibc) is used on the target it will be version MAJOR.MINOR or later. Normally this can be detected from the C library's header files, but this option may be --- 1734,1755 ---- --enable-linker-plugin-configure-flags=--host=i686-pc-linux-gnu \ --enable-linker-plugin-flags='CC=gcc\ -m32\ -Wl,-rpath,[...]/i686-pc-linux-gnu/lib' ! `--with-plugin-ld=PATHNAME' Enable an alternate linker to be used at link-time optimization ! (LTO) link time when `-fuse-linker-plugin' is enabled. This ! linker should have plugin support such as gold starting with ! version 2.20 or GNU ld starting with version 2.21. See ! `-fuse-linker-plugin' for details. ! `--enable-canonical-system-headers' ! `--disable-canonical-system-headers' ! Enable system header path canonicalization for `libcpp'. This can produce shorter header file paths in diagnostics and dependency ! output files, but these changed header paths may conflict with ! some compilation environments. Enabled by default, and may be ! disabled using `--disable-canonical-system-headers'. ! `--with-glibc-version=MAJOR.MINOR' Tell GCC that when the GNU C Library (glibc) is used on the target it will be version MAJOR.MINOR or later. Normally this can be detected from the C library's header files, but this option may be *************** option. *** 1730,1766 **** glibc. However, such configurations may not work well as not all the relevant configuration in GCC is on a per-multilib basis. ! '--enable-as-accelerator-for=TARGET' ! Build as offload target compiler. Specify offload host triple by TARGET. ! '--enable-offload-targets=TARGET1[=PATH1],...,TARGETN[=PATHN]' Enable offloading to targets TARGET1, ..., TARGETN. Offload compilers are expected to be already installed. Default search ! path for them is 'EXEC-PREFIX', but it can be changed by specifying ! paths PATH1, ..., PATHN. % SRCDIR/configure \ --enable-offload-target=i686-unknown-linux-gnu=/path/to/i686/compiler,x86_64-pc-linux-gnu ! If 'hsa' is specified as one of the targets, the compiler will be built with support for HSA GPU accelerators. Because the same compiler will emit the accelerator code, no path should be specified. ! '--with-hsa-runtime=PATHNAME' ! '--with-hsa-runtime-include=PATHNAME' ! '--with-hsa-runtime-lib=PATHNAME' ! If you configure GCC with HSA offloading but do not have the HSA run-time library installed in a standard location then you can explicitly specify the directory where they are installed. The ! '--with-hsa-runtime=HSAINSTALLDIR' option is a shorthand for ! '--with-hsa-runtime-lib=HSAINSTALLDIR/lib' and ! '--with-hsa-runtime-include=HSAINSTALLDIR/include'. ! ! '--with-hsa-kmt-lib=PATHNAME' If you configure GCC with HSA offloading but do not have the HSA KMT library installed in a standard location then you can explicitly specify the directory where it resides. --- 1761,1795 ---- glibc. However, such configurations may not work well as not all the relevant configuration in GCC is on a per-multilib basis. ! `--enable-as-accelerator-for=TARGET' ! Build as offload target compiler. Specify offload host triple by TARGET. ! `--enable-offload-targets=TARGET1[=PATH1],...,TARGETN[=PATHN]' Enable offloading to targets TARGET1, ..., TARGETN. Offload compilers are expected to be already installed. Default search ! path for them is `EXEC-PREFIX', but it can be changed by ! specifying paths PATH1, ..., PATHN. % SRCDIR/configure \ --enable-offload-target=i686-unknown-linux-gnu=/path/to/i686/compiler,x86_64-pc-linux-gnu ! If `hsa' is specified as one of the targets, the compiler will be built with support for HSA GPU accelerators. Because the same compiler will emit the accelerator code, no path should be specified. ! `--with-hsa-runtime=PATHNAME' ! `--with-hsa-runtime-include=PATHNAME' ! `--with-hsa-runtime-lib=PATHNAME' If you configure GCC with HSA offloading but do not have the HSA run-time library installed in a standard location then you can explicitly specify the directory where they are installed. The ! `--with-hsa-runtime=HSAINSTALLDIR' option is a shorthand for ! `--with-hsa-runtime-lib=HSAINSTALLDIR/lib' and ! `--with-hsa-runtime-include=HSAINSTALLDIR/include'. + `--with-hsa-kmt-lib=PATHNAME' If you configure GCC with HSA offloading but do not have the HSA KMT library installed in a standard location then you can explicitly specify the directory where it resides. *************** Cross-Compiler-Specific Options *** 1770,2144 **** The following options only apply to building cross compilers. ! '--with-sysroot' ! '--with-sysroot=DIR' Tells GCC to consider DIR as the root of a tree that contains (a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be searched for in there. More specifically, this acts as if ! '--sysroot=DIR' was added to the default options of the built compiler. The specified directory is not copied into the install ! tree, unlike the options '--with-headers' and '--with-libs' that ! this option obsoletes. The default value, in case '--with-sysroot' ! is not given an argument, is '${gcc_tooldir}/sys-root'. If the ! specified directory is a subdirectory of '${exec_prefix}', then it ! will be found relative to the GCC binaries if the installation tree ! is moved. This option affects the system root for the compiler used to build target libraries (which runs on the build system) and the compiler ! newly installed with 'make install'; it does not affect the compiler which is used to build GCC itself. ! If you specify the '--with-native-system-header-dir=DIRNAME' option ! then the compiler will search that directory within DIRNAME for ! native system headers rather than the default '/usr/include'. ! '--with-build-sysroot' ! '--with-build-sysroot=DIR' ! Tells GCC to consider DIR as the system root (see '--with-sysroot') ! while building target libraries, instead of the directory specified ! with '--with-sysroot'. This option is only useful when you are ! already using '--with-sysroot'. You can use '--with-build-sysroot' ! when you are configuring with '--prefix' set to a directory that is ! different from the one in which you are installing GCC and your ! target libraries. This option affects the system root for the compiler used to build target libraries (which runs on the build system); it does not affect the compiler which is used to build GCC itself. ! If you specify the '--with-native-system-header-dir=DIRNAME' option ! then the compiler will search that directory within DIRNAME for ! native system headers rather than the default '/usr/include'. ! '--with-headers' ! '--with-headers=DIR' ! Deprecated in favor of '--with-sysroot'. Specifies that target headers are available when building a cross compiler. The DIR argument specifies a directory which has the target include files. ! These include files will be copied into the 'gcc' install directory. _This option with the DIR argument is required_ when ! building a cross compiler, if 'PREFIX/TARGET/sys-include' doesn't ! pre-exist. If 'PREFIX/TARGET/sys-include' does pre-exist, the DIR ! argument may be omitted. 'fixincludes' will be run on these files to make them compatible with GCC. ! '--without-headers' Tells GCC not use any target headers from a libc when building a cross compiler. When crossing to GNU/Linux, you need the headers so GCC can build the exception handling for libgcc. ! '--with-libs' ! '--with-libs="DIR1 DIR2 ... DIRN"' ! Deprecated in favor of '--with-sysroot'. Specifies a list of directories which contain the target runtime libraries. These ! libraries will be copied into the 'gcc' install directory. If the directory list is omitted, this option has no effect. ! '--with-newlib' ! Specifies that 'newlib' is being used as the target C library. ! This causes '__eprintf' to be omitted from 'libgcc.a' on the ! assumption that it will be provided by 'newlib'. ! '--with-avrlibc' ! Specifies that 'AVR-Libc' is being used as the target C library. ! This causes float support functions like '__addsf3' to be omitted ! from 'libgcc.a' on the assumption that it will be provided by ! 'libm.a'. For more technical details, cf. PR54461. This option is only supported for the AVR target. It is not supported for RTEMS configurations, which currently use newlib. The option is supported since version 4.7.2 and is the default in 4.8.0 and newer. ! '--with-nds32-lib=LIBRARY' ! Specifies that LIBRARY setting is used for building 'libgcc.a'. ! Currently, the valid LIBRARY is 'newlib' or 'mculib'. This option is only supported for the NDS32 target. ! '--with-build-time-tools=DIR' ! Specifies where to find the set of target tools (assembler, linker, ! etc.) that will be used while building GCC itself. This option ! can be useful if the directory layouts are different between the ! system you are building GCC on, and the system where you will ! deploy it. ! For example, on an 'ia64-hp-hpux' system, you may have the GNU ! assembler and linker in '/usr/bin', and the native tools in a different path, and build a toolchain that expects to find the ! native tools in '/usr/bin'. ! When you use this option, you should ensure that DIR includes 'ar', ! 'as', 'ld', 'nm', 'ranlib' and 'strip' if necessary, and possibly ! 'objdump'. Otherwise, GCC may use an inconsistent set of tools. ! Overriding 'configure' test results ................................... Sometimes, it might be necessary to override the result of some ! 'configure' test, for example in order to ease porting to a new system ! or work around a bug in a test. The toplevel 'configure' script provides three variables for this: ! 'build_configargs' ! The contents of this variable is passed to all build 'configure' scripts. ! 'host_configargs' ! The contents of this variable is passed to all host 'configure' scripts. ! 'target_configargs' ! The contents of this variable is passed to all target 'configure' scripts. ! In order to avoid shell and 'make' quoting issues for complex ! overrides, you can pass a setting for 'CONFIG_SITE' and set variables in ! the site file. Java-Specific Options --------------------- The following option applies to the build of the Java front end. ! '--disable-libgcj' Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend to use GCJ with some other run-time, or you're going to install it separately, or it just happens not to build on your particular machine. In general, ! if the Java front end is enabled, the GCJ libraries will be enabled ! too, unless they're known to not work on the target platform. If ! GCJ is enabled but 'libgcj' isn't built, you may need to port it; ! in this case, before modifying the top-level 'configure.ac' so that ! 'libgcj' is enabled by default on this platform, you may use ! '--enable-libgcj' to override the default. ! The following options apply to building 'libgcj'. General Options ............... ! '--enable-java-maintainer-mode' ! By default the 'libjava' build will not attempt to compile the ! '.java' source files to '.class'. Instead, it will use the ! '.class' files from the source tree. If you use this option you ! must have executables named 'ecj1' and 'gjavah' in your path for ! use by the build. You must use this option if you intend to modify ! any '.java' files in 'libjava'. ! '--with-java-home=DIRNAME' ! This 'libjava' option overrides the default value of the ! 'java.home' system property. It is also used to set ! 'sun.boot.class.path' to 'DIRNAME/lib/rt.jar'. By default ! 'java.home' is set to 'PREFIX' and 'sun.boot.class.path' to ! 'DATADIR/java/libgcj-VERSION.jar'. ! '--with-ecj-jar=FILENAME' This option can be used to specify the location of an external jar file containing the Eclipse Java compiler. A specially modified ! version of this compiler is used by 'gcj' to parse '.java' source ! files. If this option is given, the 'libjava' build will create ! and install an 'ecj1' executable which uses this jar file at runtime. ! If this option is not given, but an 'ecj.jar' file is found in the ! topmost source tree at configure time, then the 'libgcj' build will ! create and install 'ecj1', and will also install the discovered ! 'ecj.jar' into a suitable place in the install tree. ! If 'ecj1' is not installed, then the user will have to supply one ! on his path in order for 'gcj' to properly parse '.java' source files. A suitable jar is available from ! . ! '--disable-getenv-properties' ! Don't set system properties from 'GCJ_PROPERTIES'. ! '--enable-hash-synchronization' ! Use a global hash table for monitor locks. Ordinarily, 'libgcj''s ! 'configure' script automatically makes the correct choice for this option for your platform. Only use this if you know you need the library to be configured differently. ! '--enable-interpreter' Enable the Java interpreter. The interpreter is automatically enabled by default on all platforms that support it. This option ! is really only useful if you want to disable the interpreter (using ! '--disable-interpreter'). ! '--disable-java-net' Disable java.net. This disables the native part of java.net only, using non-functional stubs for native method implementations. ! '--disable-jvmpi' Disable JVMPI support. ! '--disable-libgcj-bc' Disable BC ABI compilation of certain parts of libgcj. By default, ! some portions of libgcj are compiled with '-findirect-dispatch' and ! '-fno-indirect-classes', allowing them to be overridden at run-time. ! If '--disable-libgcj-bc' is specified, libgcj is built without these options. This allows the compile-time linker to resolve dependencies when statically linking to libgcj. However it makes it impossible to override the affected portions of libgcj at run-time. ! '--enable-reduced-reflection' ! Build most of libgcj with '-freduced-reflection'. This reduces the ! size of libgcj at the expense of not being able to do accurate reflection on the classes it contains. This option is safe if you know that code using libgcj will never use reflection on the standard runtime classes in libgcj (including using serialization, RMI or CORBA). ! '--with-ecos' Enable runtime eCos target support. ! '--without-libffi' ! Don't use 'libffi'. This will disable the interpreter and JNI ! support as well, as these require 'libffi' to work. ! '--enable-libgcj-debug' Enable runtime debugging code. ! '--enable-libgcj-multifile' ! If specified, causes all '.java' source files to be compiled into ! '.class' files in one invocation of 'gcj'. This can speed up build ! time, but is more resource-intensive. If this option is ! unspecified or disabled, 'gcj' is invoked once for each '.java' ! file to compile into a '.class' file. ! ! '--with-libiconv-prefix=DIR' ! Search for libiconv in 'DIR/include' and 'DIR/lib'. ! '--enable-sjlj-exceptions' ! Force use of the 'setjmp'/'longjmp'-based scheme for exceptions. ! 'configure' ordinarily picks the correct value based on the ! platform. Only use this option if you are sure you need a ! different setting. ! '--with-system-zlib' ! Use installed 'zlib' rather than that included with GCC. ! '--with-win32-nlsapi=ansi, unicows or unicode' ! Indicates how MinGW 'libgcj' translates between UNICODE characters and the Win32 API. ! '--enable-java-home' If enabled, this creates a JPackage compatible SDK environment during install. Note that if -enable-java-home is used, -with-arch-directory=ARCH must also be specified. ! '--with-arch-directory=ARCH' ! Specifies the name to use for the 'jre/lib/ARCH' directory in the ! SDK environment created when -enable-java-home is passed. Typical names for this directory include i386, amd64, ia64, etc. ! '--with-os-directory=DIR' ! Specifies the OS directory for the SDK include directory. This is set to auto detect, and is typically 'linux'. ! '--with-origin-name=NAME' ! Specifies the JPackage origin name. This defaults to the 'gcj' in java-1.5.0-gcj. ! '--with-arch-suffix=SUFFIX' ! Specifies the suffix for the sdk directory. Defaults to the empty string. Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'. ! '--with-jvm-root-dir=DIR' Specifies where to install the SDK. Default is $(prefix)/lib/jvm. ! '--with-jvm-jar-dir=DIR' ! Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. ! '--with-python-dir=DIR' ! Specifies where to install the Python modules used for aot-compile. ! DIR should not include the prefix used in installation. For ! example, if the Python modules are to be installed in ! /usr/lib/python2.5/site-packages, then ! -with-python-dir=/lib/python2.5/site-packages should be passed. If this is not specified, then the Python modules are installed in $(prefix)/share/python. ! '--enable-aot-compile-rpm' Adds aot-compile-rpm to the list of installed scripts. ! '--enable-browser-plugin' Build the gcjwebplugin web browser plugin. ! '--enable-static-libjava' ! Build static libraries in libjava. The default is to only build shared libraries. ! 'ansi' ! Use the single-byte 'char' and the Win32 A functions natively, translating to and from UNICODE when using these functions. If unspecified, this is the default. ! 'unicows' ! Use the 'WCHAR' and Win32 W functions natively. Adds ! '-lunicows' to 'libgcj.spec' to link with 'libunicows'. ! 'unicows.dll' needs to be deployed on Microsoft Windows 9X ! machines running built executables. 'libunicows.a', an ! open-source import library around Microsoft's 'unicows.dll', ! is obtained from , which ! also gives details on getting 'unicows.dll' from Microsoft. ! 'unicode' ! Use the 'WCHAR' and Win32 W functions natively. Does _not_ ! add '-lunicows' to 'libgcj.spec'. The built executables will only run on Microsoft Windows NT and above. AWT-Specific Options .................... ! '--with-x' Use the X Window System. ! '--enable-java-awt=PEER(S)' Specifies the AWT peer library or libraries to build alongside ! 'libgcj'. If this option is unspecified or disabled, AWT will be ! non-functional. Current valid values are 'gtk' and 'xlib'. Multiple libraries should be separated by a comma (i.e. ! '--enable-java-awt=gtk,xlib'). ! '--enable-gtk-cairo' Build the cairo Graphics2D implementation on GTK. ! '--enable-java-gc=TYPE' ! Choose garbage collector. Defaults to 'boehm' if unspecified. ! '--disable-gtktest' Do not try to compile and run a test GTK+ program. ! '--disable-glibtest' Do not try to compile and run a test GLIB program. ! '--with-libart-prefix=PFX' Prefix where libart is installed (optional). ! '--with-libart-exec-prefix=PFX' Exec prefix where libart is installed (optional). ! '--disable-libarttest' Do not try to compile and run a test libart program.  File: gccinstall.info, Node: Building, Next: Testing, Prev: Configuration, Up: Installing GCC 5 Building ********** ! Now that GCC is configured, you are ready to build the compiler and runtime libraries. Some commands executed when making the compiler may fail (return a ! nonzero status) and be ignored by 'make'. These failures, which are often due to files that were not found, are expected, and can safely be ignored. --- 1799,2171 ---- The following options only apply to building cross compilers. ! `--with-sysroot' ! `--with-sysroot=DIR' Tells GCC to consider DIR as the root of a tree that contains (a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be searched for in there. More specifically, this acts as if ! `--sysroot=DIR' was added to the default options of the built compiler. The specified directory is not copied into the install ! tree, unlike the options `--with-headers' and `--with-libs' that ! this option obsoletes. The default value, in case ! `--with-sysroot' is not given an argument, is ! `${gcc_tooldir}/sys-root'. If the specified directory is a ! subdirectory of `${exec_prefix}', then it will be found relative to ! the GCC binaries if the installation tree is moved. This option affects the system root for the compiler used to build target libraries (which runs on the build system) and the compiler ! newly installed with `make install'; it does not affect the compiler which is used to build GCC itself. ! If you specify the `--with-native-system-header-dir=DIRNAME' ! option then the compiler will search that directory within DIRNAME ! for native system headers rather than the default `/usr/include'. ! `--with-build-sysroot' ! `--with-build-sysroot=DIR' ! Tells GCC to consider DIR as the system root (see ! `--with-sysroot') while building target libraries, instead of the ! directory specified with `--with-sysroot'. This option is only ! useful when you are already using `--with-sysroot'. You can use ! `--with-build-sysroot' when you are configuring with `--prefix' ! set to a directory that is different from the one in which you are ! installing GCC and your target libraries. This option affects the system root for the compiler used to build target libraries (which runs on the build system); it does not affect the compiler which is used to build GCC itself. ! If you specify the `--with-native-system-header-dir=DIRNAME' ! option then the compiler will search that directory within DIRNAME ! for native system headers rather than the default `/usr/include'. ! `--with-headers' ! `--with-headers=DIR' ! Deprecated in favor of `--with-sysroot'. Specifies that target headers are available when building a cross compiler. The DIR argument specifies a directory which has the target include files. ! These include files will be copied into the `gcc' install directory. _This option with the DIR argument is required_ when ! building a cross compiler, if `PREFIX/TARGET/sys-include' doesn't ! pre-exist. If `PREFIX/TARGET/sys-include' does pre-exist, the DIR ! argument may be omitted. `fixincludes' will be run on these files to make them compatible with GCC. ! `--without-headers' Tells GCC not use any target headers from a libc when building a cross compiler. When crossing to GNU/Linux, you need the headers so GCC can build the exception handling for libgcc. ! `--with-libs' ! `--with-libs="DIR1 DIR2 ... DIRN"' ! Deprecated in favor of `--with-sysroot'. Specifies a list of directories which contain the target runtime libraries. These ! libraries will be copied into the `gcc' install directory. If the directory list is omitted, this option has no effect. ! `--with-newlib' ! Specifies that `newlib' is being used as the target C library. ! This causes `__eprintf' to be omitted from `libgcc.a' on the ! assumption that it will be provided by `newlib'. ! `--with-avrlibc' ! Specifies that `AVR-Libc' is being used as the target C library. ! This causes float support functions like `__addsf3' to be omitted ! from `libgcc.a' on the assumption that it will be provided by ! `libm.a'. For more technical details, cf. PR54461. This option is only supported for the AVR target. It is not supported for RTEMS configurations, which currently use newlib. The option is supported since version 4.7.2 and is the default in 4.8.0 and newer. ! `--with-nds32-lib=LIBRARY' ! Specifies that LIBRARY setting is used for building `libgcc.a'. ! Currently, the valid LIBRARY is `newlib' or `mculib'. This option is only supported for the NDS32 target. ! `--with-build-time-tools=DIR' ! Specifies where to find the set of target tools (assembler, ! linker, etc.) that will be used while building GCC itself. This ! option can be useful if the directory layouts are different ! between the system you are building GCC on, and the system where ! you will deploy it. ! For example, on an `ia64-hp-hpux' system, you may have the GNU ! assembler and linker in `/usr/bin', and the native tools in a different path, and build a toolchain that expects to find the ! native tools in `/usr/bin'. ! When you use this option, you should ensure that DIR includes ! `ar', `as', `ld', `nm', `ranlib' and `strip' if necessary, and ! possibly `objdump'. Otherwise, GCC may use an inconsistent set of ! tools. ! Overriding `configure' test results ................................... Sometimes, it might be necessary to override the result of some ! `configure' test, for example in order to ease porting to a new system ! or work around a bug in a test. The toplevel `configure' script provides three variables for this: ! `build_configargs' ! The contents of this variable is passed to all build `configure' scripts. ! `host_configargs' ! The contents of this variable is passed to all host `configure' scripts. ! `target_configargs' ! The contents of this variable is passed to all target `configure' scripts. ! ! In order to avoid shell and `make' quoting issues for complex ! overrides, you can pass a setting for `CONFIG_SITE' and set variables ! in the site file. Java-Specific Options --------------------- The following option applies to the build of the Java front end. ! `--disable-libgcj' Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend to use GCJ with some other run-time, or you're going to install it separately, or it just happens not to build on your particular machine. In general, ! if the Java front end is enabled, the GCJ libraries will be ! enabled too, unless they're known to not work on the target ! platform. If GCJ is enabled but `libgcj' isn't built, you may ! need to port it; in this case, before modifying the top-level ! `configure.ac' so that `libgcj' is enabled by default on this ! platform, you may use `--enable-libgcj' to override the default. ! ! The following options apply to building `libgcj'. General Options ............... ! `--enable-java-maintainer-mode' ! By default the `libjava' build will not attempt to compile the ! `.java' source files to `.class'. Instead, it will use the ! `.class' files from the source tree. If you use this option you ! must have executables named `ecj1' and `gjavah' in your path for ! use by the build. You must use this option if you intend to ! modify any `.java' files in `libjava'. ! `--with-java-home=DIRNAME' ! This `libjava' option overrides the default value of the ! `java.home' system property. It is also used to set ! `sun.boot.class.path' to `DIRNAME/lib/rt.jar'. By default ! `java.home' is set to `PREFIX' and `sun.boot.class.path' to ! `DATADIR/java/libgcj-VERSION.jar'. ! `--with-ecj-jar=FILENAME' This option can be used to specify the location of an external jar file containing the Eclipse Java compiler. A specially modified ! version of this compiler is used by `gcj' to parse `.java' source ! files. If this option is given, the `libjava' build will create ! and install an `ecj1' executable which uses this jar file at runtime. ! If this option is not given, but an `ecj.jar' file is found in the ! topmost source tree at configure time, then the `libgcj' build ! will create and install `ecj1', and will also install the ! discovered `ecj.jar' into a suitable place in the install tree. ! If `ecj1' is not installed, then the user will have to supply one ! on his path in order for `gcj' to properly parse `.java' source files. A suitable jar is available from ! `ftp://sourceware.org/pub/java/'. ! `--disable-getenv-properties' ! Don't set system properties from `GCJ_PROPERTIES'. ! `--enable-hash-synchronization' ! Use a global hash table for monitor locks. Ordinarily, `libgcj''s ! `configure' script automatically makes the correct choice for this option for your platform. Only use this if you know you need the library to be configured differently. ! `--enable-interpreter' Enable the Java interpreter. The interpreter is automatically enabled by default on all platforms that support it. This option ! is really only useful if you want to disable the interpreter ! (using `--disable-interpreter'). ! `--disable-java-net' Disable java.net. This disables the native part of java.net only, using non-functional stubs for native method implementations. ! `--disable-jvmpi' Disable JVMPI support. ! `--disable-libgcj-bc' Disable BC ABI compilation of certain parts of libgcj. By default, ! some portions of libgcj are compiled with `-findirect-dispatch' ! and `-fno-indirect-classes', allowing them to be overridden at run-time. ! If `--disable-libgcj-bc' is specified, libgcj is built without these options. This allows the compile-time linker to resolve dependencies when statically linking to libgcj. However it makes it impossible to override the affected portions of libgcj at run-time. ! `--enable-reduced-reflection' ! Build most of libgcj with `-freduced-reflection'. This reduces ! the size of libgcj at the expense of not being able to do accurate reflection on the classes it contains. This option is safe if you know that code using libgcj will never use reflection on the standard runtime classes in libgcj (including using serialization, RMI or CORBA). ! `--with-ecos' Enable runtime eCos target support. ! `--without-libffi' ! Don't use `libffi'. This will disable the interpreter and JNI ! support as well, as these require `libffi' to work. ! `--enable-libgcj-debug' Enable runtime debugging code. ! `--enable-libgcj-multifile' ! If specified, causes all `.java' source files to be compiled into ! `.class' files in one invocation of `gcj'. This can speed up ! build time, but is more resource-intensive. If this option is ! unspecified or disabled, `gcj' is invoked once for each `.java' ! file to compile into a `.class' file. ! `--with-libiconv-prefix=DIR' ! Search for libiconv in `DIR/include' and `DIR/lib'. ! `--with-system-zlib' ! Use installed `zlib' rather than that included with GCC. ! `--with-win32-nlsapi=ansi, unicows or unicode' ! Indicates how MinGW `libgcj' translates between UNICODE characters and the Win32 API. ! `--enable-java-home' If enabled, this creates a JPackage compatible SDK environment during install. Note that if -enable-java-home is used, -with-arch-directory=ARCH must also be specified. ! `--with-arch-directory=ARCH' ! Specifies the name to use for the `jre/lib/ARCH' directory in the ! SDK environment created when -enable-java-home is passed. Typical names for this directory include i386, amd64, ia64, etc. ! `--with-os-directory=DIR' ! Specifies the OS directory for the SDK include directory. This is set to auto detect, and is typically 'linux'. ! `--with-origin-name=NAME' ! Specifies the JPackage origin name. This defaults to the 'gcj' in java-1.5.0-gcj. ! `--with-arch-suffix=SUFFIX' ! Specifies the suffix for the sdk directory. Defaults to the empty string. Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'. ! `--with-jvm-root-dir=DIR' Specifies where to install the SDK. Default is $(prefix)/lib/jvm. ! `--with-jvm-jar-dir=DIR' ! Specifies where to install jars. Default is $(prefix)/lib/jvm-exports. ! `--with-python-dir=DIR' ! Specifies where to install the Python modules used for ! aot-compile. DIR should not include the prefix used in ! installation. For example, if the Python modules are to be ! installed in /usr/lib/python2.5/site-packages, then ! -with-python-dir=/lib/python2.5/site-packages should be passed. If this is not specified, then the Python modules are installed in $(prefix)/share/python. ! `--enable-aot-compile-rpm' Adds aot-compile-rpm to the list of installed scripts. ! `--enable-browser-plugin' Build the gcjwebplugin web browser plugin. ! `--enable-static-libjava' ! Build static libraries in libjava. The default is to only build shared libraries. ! `ansi' ! Use the single-byte `char' and the Win32 A functions natively, translating to and from UNICODE when using these functions. If unspecified, this is the default. ! `unicows' ! Use the `WCHAR' and Win32 W functions natively. Adds ! `-lunicows' to `libgcj.spec' to link with `libunicows'. ! `unicows.dll' needs to be deployed on Microsoft Windows 9X ! machines running built executables. `libunicows.a', an ! open-source import library around Microsoft's `unicows.dll', ! is obtained from `http://libunicows.sourceforge.net/', which ! also gives details on getting `unicows.dll' from Microsoft. ! `unicode' ! Use the `WCHAR' and Win32 W functions natively. Does _not_ ! add `-lunicows' to `libgcj.spec'. The built executables will only run on Microsoft Windows NT and above. AWT-Specific Options .................... ! `--with-x' Use the X Window System. ! `--enable-java-awt=PEER(S)' Specifies the AWT peer library or libraries to build alongside ! `libgcj'. If this option is unspecified or disabled, AWT will be ! non-functional. Current valid values are `gtk' and `xlib'. Multiple libraries should be separated by a comma (i.e. ! `--enable-java-awt=gtk,xlib'). ! `--enable-gtk-cairo' Build the cairo Graphics2D implementation on GTK. ! `--enable-java-gc=TYPE' ! Choose garbage collector. Defaults to `boehm' if unspecified. ! `--disable-gtktest' Do not try to compile and run a test GTK+ program. ! `--disable-glibtest' Do not try to compile and run a test GLIB program. ! `--with-libart-prefix=PFX' Prefix where libart is installed (optional). ! `--with-libart-exec-prefix=PFX' Exec prefix where libart is installed (optional). ! `--disable-libarttest' Do not try to compile and run a test libart program. +  File: gccinstall.info, Node: Building, Next: Testing, Prev: Configuration, Up: Installing GCC 5 Building ********** ! Now that GCC is configured, you are ready to build the compiler and runtime libraries. Some commands executed when making the compiler may fail (return a ! nonzero status) and be ignored by `make'. These failures, which are often due to files that were not found, are expected, and can safely be ignored. *************** ignored. *** 2146,2155 **** Unless you are a GCC developer, you can generally ignore these warnings unless they cause compilation to fail. Developers should attempt to fix any warnings encountered, however they can temporarily continue past ! warnings-as-errors by specifying the configure flag '--disable-werror'. On certain old systems, defining certain environment variables such ! as 'CC' can interfere with the functioning of 'make'. If you encounter seemingly strange errors when trying to build the compiler in a directory other than the source directory, it could be --- 2173,2182 ---- Unless you are a GCC developer, you can generally ignore these warnings unless they cause compilation to fail. Developers should attempt to fix any warnings encountered, however they can temporarily continue past ! warnings-as-errors by specifying the configure flag `--disable-werror'. On certain old systems, defining certain environment variables such ! as `CC' can interfere with the functioning of `make'. If you encounter seemingly strange errors when trying to build the compiler in a directory other than the source directory, it could be *************** because you have previously configured t *** 2157,2176 **** directory. Make sure you have done all the necessary preparations. If you build GCC on a BSD system using a directory stored in an old ! System V file system, problems may occur in running 'fixincludes' if the System V file system doesn't support symbolic links. These problems ! result in a failure to fix the declaration of 'size_t' in 'sys/types.h'. ! If you find that 'size_t' is a signed type and that type mismatches ! occur, this could be the cause. The solution is not to use such a directory for building GCC. Similarly, when building from SVN or snapshots, or if you modify ! '*.l' files, you need the Flex lexical analyzer generator installed. If ! you do not modify '*.l' files, releases contain the Flex-generated files ! and you do not need Flex installed to build them. There is still one ! Flex-based lexical analyzer (part of the build machinery, not of GCC ! itself) that is used even if you only build the C front end. When building from SVN or snapshots, or if you modify Texinfo documentation, you need version 4.7 or later of Texinfo installed if you --- 2184,2203 ---- directory. Make sure you have done all the necessary preparations. If you build GCC on a BSD system using a directory stored in an old ! System V file system, problems may occur in running `fixincludes' if the System V file system doesn't support symbolic links. These problems ! result in a failure to fix the declaration of `size_t' in ! `sys/types.h'. If you find that `size_t' is a signed type and that ! type mismatches occur, this could be the cause. The solution is not to use such a directory for building GCC. Similarly, when building from SVN or snapshots, or if you modify ! `*.l' files, you need the Flex lexical analyzer generator installed. ! If you do not modify `*.l' files, releases contain the Flex-generated ! files and you do not need Flex installed to build them. There is still ! one Flex-based lexical analyzer (part of the build machinery, not of ! GCC itself) that is used even if you only build the C front end. When building from SVN or snapshots, or if you modify Texinfo documentation, you need version 4.7 or later of Texinfo installed if you *************** documentation pre-built for the unmodifi *** 2181,2190 **** ============================== For a native build, the default configuration is to perform a 3-stage ! bootstrap of the compiler when 'make' is invoked. This will build the entire GCC system and ensure that it compiles itself correctly. It can ! be disabled with the '--disable-bootstrap' parameter to 'configure', but ! bootstrapping is suggested because the compiler will be tested more completely and could also have better performance. The bootstrapping process will complete the following steps: --- 2208,2217 ---- ============================== For a native build, the default configuration is to perform a 3-stage ! bootstrap of the compiler when `make' is invoked. This will build the entire GCC system and ensure that it compiles itself correctly. It can ! be disabled with the `--disable-bootstrap' parameter to `configure', ! but bootstrapping is suggested because the compiler will be tested more completely and could also have better performance. The bootstrapping process will complete the following steps: *************** completely and could also have better pe *** 2199,2216 **** * Perform a comparison test of the stage2 and stage3 compilers. ! * Build runtime libraries using the stage3 compiler from the previous ! step. ! If you are short on disk space you might consider 'make bootstrap-lean' instead. The sequence of compilation is the same described above, but object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. If you wish to use non-default GCC flags when compiling the stage2 ! and stage3 compilers, set 'BOOT_CFLAGS' on the command line when doing ! 'make'. For example, if you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information as in the following example. This will save roughly 40% of disk space both for the --- 2226,2244 ---- * Perform a comparison test of the stage2 and stage3 compilers. ! * Build runtime libraries using the stage3 compiler from the ! previous step. ! ! If you are short on disk space you might consider `make bootstrap-lean' instead. The sequence of compilation is the same described above, but object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. If you wish to use non-default GCC flags when compiling the stage2 ! and stage3 compilers, set `BOOT_CFLAGS' on the command line when doing ! `make'. For example, if you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information as in the following example. This will save roughly 40% of disk space both for the *************** debugging information.) *** 2219,2345 **** make BOOT_CFLAGS='-O' bootstrap ! You can place non-default optimization flags into 'BOOT_CFLAGS'; they ! are less well tested here than the default of '-g -O2', but should still ! work. In a few cases, you may find that you need to specify special ! flags such as '-msoft-float' here to complete the bootstrap; or, if the ! native compiler miscompiles the stage1 compiler, you may need to work ! around this, by choosing 'BOOT_CFLAGS' to avoid the parts of the stage1 ! compiler that were miscompiled, or by using 'make bootstrap4' to increase the number of stages of bootstrap. ! 'BOOT_CFLAGS' does not apply to bootstrapped target libraries. Since ! these are always compiled with the compiler currently being ! bootstrapped, you can use 'CFLAGS_FOR_TARGET' to modify their compilation flags, as for non-bootstrapped target libraries. Again, if the native compiler miscompiles the stage1 compiler, you may need to work around this by avoiding non-working parts of the stage1 compiler. ! Use 'STAGE1_TFLAGS' to this end. ! If you used the flag '--enable-languages=...' to restrict the ! compilers to be built, only those you've actually enabled will be built. ! This will of course only build those runtime libraries, for which the ! particular compiler has been built. Please note, that re-defining ! 'LANGUAGES' when calling 'make' *does not* work anymore! If the comparison of stage2 and stage3 fails, this normally indicates that the stage2 compiler has compiled GCC incorrectly, and is therefore a potentially serious bug which you should investigate and report. (On a few systems, meaningful comparison of object files is impossible; they ! always appear "different". If you encounter this problem, you will need ! to disable comparison in the 'Makefile'.) If you do not want to bootstrap your compiler, you can configure with ! '--disable-bootstrap'. In particular cases, you may want to bootstrap your compiler even if the target system is not the same as the one you are building on: for example, you could build a ! 'powerpc-unknown-linux-gnu' toolchain on a 'powerpc64-unknown-linux-gnu' ! host. In this case, pass '--enable-bootstrap' to the configure script. ! 'BUILD_CONFIG' can be used to bring in additional customization to the build. It can be set to a whitespace-separated list of names. For ! each such 'NAME', top-level 'config/NAME.mk' will be included by the ! top-level 'Makefile', bringing in any settings it contains. The default ! 'BUILD_CONFIG' can be set using the configure option ! '--with-build-config=NAME...'. Some examples of supported build configurations are: ! 'bootstrap-O1' ! Removes any '-O'-started option from 'BOOT_CFLAGS', and adds '-O1' ! to it. 'BUILD_CONFIG=bootstrap-O1' is equivalent to ! 'BOOT_CFLAGS='-g -O1''. ! 'bootstrap-O3' ! Analogous to 'bootstrap-O1'. ! 'bootstrap-lto' Enables Link-Time Optimization for host tools during bootstrapping. ! 'BUILD_CONFIG=bootstrap-lto' is equivalent to adding '-flto' to ! 'BOOT_CFLAGS'. This option assumes that the host supports the ! linker plugin (e.g. GNU ld version 2.21 or later or GNU gold version 2.21 or later). ! 'bootstrap-lto-noplugin' ! This option is similar to 'bootstrap-lto', but is intended for hosts that do not support the linker plugin. Without the linker plugin static libraries are not compiled with link-time optimizations. Since the GCC middle end and back end are in ! 'libbackend.a' this means that only the front end is actually LTO optimized. ! 'bootstrap-debug' Verifies that the compiler generates the same executable code, ! whether or not it is asked to emit debug information. To this end, ! this option builds stage2 host programs without debug information, ! and uses 'contrib/compare-debug' to compare them with the stripped ! stage3 object files. If 'BOOT_CFLAGS' is overridden so as to not ! enable debug information, stage2 will have it, and stage3 won't. ! This option is enabled by default when GCC bootstrapping is ! enabled, if 'strip' can turn object files compiled with and without ! debug info into identical object files. In addition to better test ! coverage, this option makes default bootstraps faster and leaner. ! 'bootstrap-debug-big' Rather than comparing stripped object files, as in ! 'bootstrap-debug', this option saves internal compiler dumps during ! stage2 and stage3 and compares them as well, which helps catch ! additional potential problems, but at a great cost in terms of disk ! space. It can be specified in addition to 'bootstrap-debug'. ! 'bootstrap-debug-lean' ! This option saves disk space compared with 'bootstrap-debug-big', but at the expense of some recompilation. Instead of saving the dumps of stage2 and stage3 until the final compare, it uses ! '-fcompare-debug' to generate, compare and remove the dumps during stage3, repeating the compilation that already took place in stage2, whose dumps were not saved. ! 'bootstrap-debug-lib' This option tests executable code invariance over debug information ! generation on target libraries, just like 'bootstrap-debug-lean' tests it on host programs. It builds stage3 libraries with ! '-fcompare-debug', and it can be used along with any of the ! 'bootstrap-debug' options above. ! There aren't '-lean' or '-big' counterparts to this option because most libraries are only build in stage3, so bootstrap compares would not get significant coverage. Moreover, the few libraries built in stage2 are used in stage3 host programs, so we wouldn't want to compile stage2 libraries with different options for comparison purposes. ! 'bootstrap-debug-ckovw' Arranges for error messages to be issued if the compiler built on ! any stage is run without the option '-fcompare-debug'. This is ! useful to verify the full '-fcompare-debug' testing coverage. It ! must be used along with 'bootstrap-debug-lean' and ! 'bootstrap-debug-lib'. ! 'bootstrap-time' Arranges for the run time of each program started by the GCC ! driver, built in any stage, to be logged to 'time.log', in the top level of the build tree. 5.2 Building a cross compiler ============================= --- 2247,2377 ---- make BOOT_CFLAGS='-O' bootstrap ! You can place non-default optimization flags into `BOOT_CFLAGS'; they ! are less well tested here than the default of `-g -O2', but should ! still work. In a few cases, you may find that you need to specify ! special flags such as `-msoft-float' here to complete the bootstrap; or, ! if the native compiler miscompiles the stage1 compiler, you may need to ! work around this, by choosing `BOOT_CFLAGS' to avoid the parts of the ! stage1 compiler that were miscompiled, or by using `make bootstrap4' to increase the number of stages of bootstrap. ! `BOOT_CFLAGS' does not apply to bootstrapped target libraries. ! Since these are always compiled with the compiler currently being ! bootstrapped, you can use `CFLAGS_FOR_TARGET' to modify their compilation flags, as for non-bootstrapped target libraries. Again, if the native compiler miscompiles the stage1 compiler, you may need to work around this by avoiding non-working parts of the stage1 compiler. ! Use `STAGE1_TFLAGS' to this end. ! If you used the flag `--enable-languages=...' to restrict the ! compilers to be built, only those you've actually enabled will be ! built. This will of course only build those runtime libraries, for ! which the particular compiler has been built. Please note, that ! re-defining `LANGUAGES' when calling `make' *does not* work anymore! If the comparison of stage2 and stage3 fails, this normally indicates that the stage2 compiler has compiled GCC incorrectly, and is therefore a potentially serious bug which you should investigate and report. (On a few systems, meaningful comparison of object files is impossible; they ! always appear "different". If you encounter this problem, you will ! need to disable comparison in the `Makefile'.) If you do not want to bootstrap your compiler, you can configure with ! `--disable-bootstrap'. In particular cases, you may want to bootstrap your compiler even if the target system is not the same as the one you are building on: for example, you could build a ! `powerpc-unknown-linux-gnu' toolchain on a ! `powerpc64-unknown-linux-gnu' host. In this case, pass ! `--enable-bootstrap' to the configure script. ! `BUILD_CONFIG' can be used to bring in additional customization to the build. It can be set to a whitespace-separated list of names. For ! each such `NAME', top-level `config/`NAME'.mk' will be included by the ! top-level `Makefile', bringing in any settings it contains. The ! default `BUILD_CONFIG' can be set using the configure option ! `--with-build-config=`NAME'...'. Some examples of supported build configurations are: ! `bootstrap-O1' ! Removes any `-O'-started option from `BOOT_CFLAGS', and adds `-O1' ! to it. `BUILD_CONFIG=bootstrap-O1' is equivalent to ! `BOOT_CFLAGS='-g -O1''. ! `bootstrap-O3' ! Analogous to `bootstrap-O1'. ! `bootstrap-lto' Enables Link-Time Optimization for host tools during bootstrapping. ! `BUILD_CONFIG=bootstrap-lto' is equivalent to adding `-flto' to ! `BOOT_CFLAGS'. This option assumes that the host supports the ! linker plugin (e.g. GNU ld version 2.21 or later or GNU gold version 2.21 or later). ! `bootstrap-lto-noplugin' ! This option is similar to `bootstrap-lto', but is intended for hosts that do not support the linker plugin. Without the linker plugin static libraries are not compiled with link-time optimizations. Since the GCC middle end and back end are in ! `libbackend.a' this means that only the front end is actually LTO optimized. ! `bootstrap-debug' Verifies that the compiler generates the same executable code, ! whether or not it is asked to emit debug information. To this ! end, this option builds stage2 host programs without debug ! information, and uses `contrib/compare-debug' to compare them with ! the stripped stage3 object files. If `BOOT_CFLAGS' is overridden ! so as to not enable debug information, stage2 will have it, and ! stage3 won't. This option is enabled by default when GCC ! bootstrapping is enabled, if `strip' can turn object files ! compiled with and without debug info into identical object files. ! In addition to better test coverage, this option makes default ! bootstraps faster and leaner. ! `bootstrap-debug-big' Rather than comparing stripped object files, as in ! `bootstrap-debug', this option saves internal compiler dumps ! during stage2 and stage3 and compares them as well, which helps ! catch additional potential problems, but at a great cost in terms ! of disk space. It can be specified in addition to ! `bootstrap-debug'. ! `bootstrap-debug-lean' ! This option saves disk space compared with `bootstrap-debug-big', but at the expense of some recompilation. Instead of saving the dumps of stage2 and stage3 until the final compare, it uses ! `-fcompare-debug' to generate, compare and remove the dumps during stage3, repeating the compilation that already took place in stage2, whose dumps were not saved. ! `bootstrap-debug-lib' This option tests executable code invariance over debug information ! generation on target libraries, just like `bootstrap-debug-lean' tests it on host programs. It builds stage3 libraries with ! `-fcompare-debug', and it can be used along with any of the ! `bootstrap-debug' options above. ! There aren't `-lean' or `-big' counterparts to this option because most libraries are only build in stage3, so bootstrap compares would not get significant coverage. Moreover, the few libraries built in stage2 are used in stage3 host programs, so we wouldn't want to compile stage2 libraries with different options for comparison purposes. ! `bootstrap-debug-ckovw' Arranges for error messages to be issued if the compiler built on ! any stage is run without the option `-fcompare-debug'. This is ! useful to verify the full `-fcompare-debug' testing coverage. It ! must be used along with `bootstrap-debug-lean' and ! `bootstrap-debug-lib'. ! `bootstrap-time' Arranges for the run time of each program started by the GCC ! driver, built in any stage, to be logged to `time.log', in the top level of the build tree. + 5.2 Building a cross compiler ============================= *************** When building a cross compiler, it is no *** 2347,2366 **** 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC. ! To build a cross compiler, we recommend first building and installing ! a native compiler. You can then use the native GCC compiler to build ! the cross compiler. The installed native compiler needs to be GCC ! version 2.95 or later. If the cross compiler is to be built with support for the Java programming language and the ability to compile .java source files is desired, the installed native compiler used to build the cross compiler ! needs to be the same GCC version as the cross compiler. In addition the ! cross compiler needs to be configured with '--with-ecj-jar=...'. Assuming you have already installed a native copy of GCC and ! configured your cross compiler, issue the command 'make', which performs ! the following steps: * Build host tools necessary to build the compiler. --- 2379,2398 ---- 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC. ! To build a cross compiler, we recommend first building and ! installing a native compiler. You can then use the native GCC compiler ! to build the cross compiler. The installed native compiler needs to be ! GCC version 2.95 or later. If the cross compiler is to be built with support for the Java programming language and the ability to compile .java source files is desired, the installed native compiler used to build the cross compiler ! needs to be the same GCC version as the cross compiler. In addition ! the cross compiler needs to be configured with `--with-ecj-jar=...'. Assuming you have already installed a native copy of GCC and ! configured your cross compiler, issue the command `make', which ! performs the following steps: * Build host tools necessary to build the compiler. *************** the following steps: *** 2377,2396 **** If you are not building GNU binutils in the same source tree as GCC, you will need a cross-assembler and cross-linker installed before ! configuring GCC. Put them in the directory 'PREFIX/TARGET/bin'. Here is a table of the tools you should put in this directory: ! 'as' This should be the cross-assembler. ! 'ld' This should be the cross-linker. ! 'ar' This should be the cross-archiver: a program which can manipulate archive files (linker libraries) in the target machine's format. ! 'ranlib' This should be a program to construct a symbol table in an archive file. --- 2409,2428 ---- If you are not building GNU binutils in the same source tree as GCC, you will need a cross-assembler and cross-linker installed before ! configuring GCC. Put them in the directory `PREFIX/TARGET/bin'. Here is a table of the tools you should put in this directory: ! `as' This should be the cross-assembler. ! `ld' This should be the cross-linker. ! `ar' This should be the cross-archiver: a program which can manipulate archive files (linker libraries) in the target machine's format. ! `ranlib' This should be a program to construct a symbol table in an archive file. *************** and copy or link them to the proper plac *** 2399,2470 **** find them when run later. The easiest way to provide these files is to build the Binutils ! package. Configure it with the same '--host' and '--target' options that you use for configuring GCC, then build and install them. They install their executables automatically into the proper directory. Alas, they do not support all the targets that GCC supports. If you are not building a C library in the same source tree as GCC, you should also provide the target libraries and headers before ! configuring GCC, specifying the directories with '--with-sysroot' or ! '--with-headers' and '--with-libs'. Many targets also require "start ! files" such as 'crt0.o' and 'crtn.o' which are linked into each ! executable. There may be several alternatives for 'crt0.o', for use with profiling or other compilation options. Check your target's ! definition of 'STARTFILE_SPEC' to find out what start files it uses. 5.3 Building in parallel ======================== GNU Make 3.80 and above, which is necessary to build GCC, support ! building in parallel. To activate this, you can use 'make -j 2' instead ! of 'make'. You can also specify a bigger number, and in most cases ! using a value greater than the number of processors in your machine will ! result in fewer and shorter I/O latency hits, thus improving overall ! throughput; this is especially true for slow drives and network ! filesystems. 5.4 Building the Ada compiler ============================= In order to build GNAT, the Ada compiler, you need a working GNAT compiler (GCC version 4.0 or later). This includes GNAT tools such as ! 'gnatmake' and 'gnatlink', since the Ada front end is written in Ada and uses some GNAT-specific extensions. In order to build a cross compiler, it is suggested to install the new compiler as native first, and then use it to build the cross compiler. ! 'configure' does not test whether the GNAT installation works and has ! a sufficiently recent version; if too old a GNAT version is installed, ! the build will fail unless '--enable-languages' is used to disable ! building the Ada front end. ! 'ADA_INCLUDE_PATH' and 'ADA_OBJECT_PATH' environment variables must not be set when building the Ada compiler, the Ada tools, or the Ada ! runtime libraries. You can check that your build environment is clean ! by verifying that 'gnatls -v' lists only one explicit path in each section. 5.5 Building with profile feedback ================================== It is possible to use profile feedback to optimize the compiler itself. ! This should result in a faster compiler binary. Experiments done on x86 ! using gcc 3.3 showed approximately 7 percent speedup on compiling C ! programs. To bootstrap the compiler with profile feedback, use 'make profiledbootstrap'. ! When 'make profiledbootstrap' is run, it will first build a 'stage1' ! compiler. This compiler is used to build a 'stageprofile' compiler instrumented to collect execution counts of instruction and branch probabilities. Then runtime libraries are compiled with profile ! collected. Finally a 'stagefeedback' compiler is built using the information collected. Unlike standard bootstrap, several additional restrictions apply. ! The compiler used to build 'stage1' needs to support a 64-bit integral type. It is recommended to only use GCC for this.  --- 2431,2502 ---- find them when run later. The easiest way to provide these files is to build the Binutils ! package. Configure it with the same `--host' and `--target' options that you use for configuring GCC, then build and install them. They install their executables automatically into the proper directory. Alas, they do not support all the targets that GCC supports. If you are not building a C library in the same source tree as GCC, you should also provide the target libraries and headers before ! configuring GCC, specifying the directories with `--with-sysroot' or ! `--with-headers' and `--with-libs'. Many targets also require "start ! files" such as `crt0.o' and `crtn.o' which are linked into each ! executable. There may be several alternatives for `crt0.o', for use with profiling or other compilation options. Check your target's ! definition of `STARTFILE_SPEC' to find out what start files it uses. 5.3 Building in parallel ======================== GNU Make 3.80 and above, which is necessary to build GCC, support ! building in parallel. To activate this, you can use `make -j 2' ! instead of `make'. You can also specify a bigger number, and in most ! cases using a value greater than the number of processors in your ! machine will result in fewer and shorter I/O latency hits, thus ! improving overall throughput; this is especially true for slow drives ! and network filesystems. 5.4 Building the Ada compiler ============================= In order to build GNAT, the Ada compiler, you need a working GNAT compiler (GCC version 4.0 or later). This includes GNAT tools such as ! `gnatmake' and `gnatlink', since the Ada front end is written in Ada and uses some GNAT-specific extensions. In order to build a cross compiler, it is suggested to install the new compiler as native first, and then use it to build the cross compiler. ! `configure' does not test whether the GNAT installation works and ! has a sufficiently recent version; if too old a GNAT version is ! installed, the build will fail unless `--enable-languages' is used to ! disable building the Ada front end. ! `ADA_INCLUDE_PATH' and `ADA_OBJECT_PATH' environment variables must not be set when building the Ada compiler, the Ada tools, or the Ada ! runtime libraries. You can check that your build environment is clean ! by verifying that `gnatls -v' lists only one explicit path in each section. 5.5 Building with profile feedback ================================== It is possible to use profile feedback to optimize the compiler itself. ! This should result in a faster compiler binary. Experiments done on ! x86 using gcc 3.3 showed approximately 7 percent speedup on compiling C ! programs. To bootstrap the compiler with profile feedback, use `make profiledbootstrap'. ! When `make profiledbootstrap' is run, it will first build a `stage1' ! compiler. This compiler is used to build a `stageprofile' compiler instrumented to collect execution counts of instruction and branch probabilities. Then runtime libraries are compiled with profile ! collected. Finally a `stagefeedback' compiler is built using the information collected. Unlike standard bootstrap, several additional restrictions apply. ! The compiler used to build `stage1' needs to support a 64-bit integral type. It is recommended to only use GCC for this.  *************** File: gccinstall.info, Node: Testing, *** 2473,2486 **** 6 Installing GCC: Testing ************************* ! Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the gcc-testresults mailing list. Some of these archived results are linked from the build status lists at ! , although not everyone who reports a ! successful build runs the testsuites and submits the results. This step ! is optional and may require you to download additional software, but it ! can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC. First, you must have downloaded the testsuites. These are part of --- 2505,2518 ---- 6 Installing GCC: Testing ************************* ! Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the gcc-testresults mailing list. Some of these archived results are linked from the build status lists at ! `http://gcc.gnu.org/buildstat.html', although not everyone who reports ! a successful build runs the testsuites and submits the results. This ! step is optional and may require you to download additional software, ! but it can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC. First, you must have downloaded the testsuites. These are part of *************** any front ends, you must download the te *** 2490,2499 **** Second, you must have the testing tools installed. This includes DejaGnu, Tcl, and Expect; the DejaGnu site has links to these. ! If the directories where 'runtest' and 'expect' were installed are ! not in the 'PATH', you may need to set the following environment ! variables appropriately, as in the following example (which assumes that ! DejaGnu has been installed under '/usr/local'): TCL_LIBRARY = /usr/local/share/tcl8.0 DEJAGNULIBS = /usr/local/share/dejagnu --- 2522,2531 ---- Second, you must have the testing tools installed. This includes DejaGnu, Tcl, and Expect; the DejaGnu site has links to these. ! If the directories where `runtest' and `expect' were installed are ! not in the `PATH', you may need to set the following environment ! variables appropriately, as in the following example (which assumes ! that DejaGnu has been installed under `/usr/local'): TCL_LIBRARY = /usr/local/share/tcl8.0 DEJAGNULIBS = /usr/local/share/dejagnu *************** portability in the DejaGnu code.) *** 2505,2559 **** Finally, you can run the testsuite (which may take a long time): cd OBJDIR; make -k check ! This will test various components of GCC, such as compiler front ends ! and runtime libraries. While running the testsuite, DejaGnu might emit ! some harmless messages resembling 'WARNING: Couldn't find the global ! config file.' or 'WARNING: Couldn't find tool init file' that can be ! ignored. If you are testing a cross-compiler, you may want to run the testsuite on a simulator as described at ! . 6.1 How can you run the testsuite on selected tests? ==================================================== ! In order to run sets of tests selectively, there are targets 'make ! check-gcc' and language specific 'make check-c', 'make check-c++', 'make ! check-fortran', 'make check-java', 'make check-ada', 'make check-objc', ! 'make check-obj-c++', 'make check-lto' in the 'gcc' subdirectory of the ! object directory. You can also just run 'make check' in a subdirectory ! of the object directory. ! A more selective way to just run all 'gcc' execute tests in the testsuite is to use make check-gcc RUNTESTFLAGS="execute.exp OTHER-OPTIONS" ! Likewise, in order to run only the 'g++' "old-deja" tests in the ! testsuite with filenames matching '9805*', you would use make check-g++ RUNTESTFLAGS="old-deja.exp=9805* OTHER-OPTIONS" ! The '*.exp' files are located in the testsuite directories of the GCC ! source, the most important ones being 'compile.exp', 'execute.exp', ! 'dg.exp' and 'old-deja.exp'. To get a list of the possible '*.exp' ! files, pipe the output of 'make check' into a file and look at the ! 'Running ... .exp' lines. 6.2 Passing options and running multiple testsuites =================================================== You can pass multiple options to the testsuite using the ! '--target_board' option of DejaGNU, either passed as part of ! 'RUNTESTFLAGS', or directly to 'runtest' if you prefer to work outside the makefiles. For example, make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants" ! will run the standard 'g++' testsuites ("unix" is the target name for ! a standard native testsuite situation), passing '-O3 -fmerge-constants' ! to the compiler on every test, i.e., slashes separate options. You can run the testsuites multiple times using combinations of options with a syntax similar to the brace expansion of popular shells: --- 2537,2592 ---- Finally, you can run the testsuite (which may take a long time): cd OBJDIR; make -k check ! This will test various components of GCC, such as compiler front ! ends and runtime libraries. While running the testsuite, DejaGnu might ! emit some harmless messages resembling `WARNING: Couldn't find the ! global config file.' or `WARNING: Couldn't find tool init file' that ! can be ignored. If you are testing a cross-compiler, you may want to run the testsuite on a simulator as described at ! `http://gcc.gnu.org/simtest-howto.html'. 6.1 How can you run the testsuite on selected tests? ==================================================== ! In order to run sets of tests selectively, there are targets `make ! check-gcc' and language specific `make check-c', `make check-c++', ! `make check-fortran', `make check-java', `make check-ada', `make ! check-objc', `make check-obj-c++', `make check-lto' in the `gcc' ! subdirectory of the object directory. You can also just run `make ! check' in a subdirectory of the object directory. ! A more selective way to just run all `gcc' execute tests in the testsuite is to use make check-gcc RUNTESTFLAGS="execute.exp OTHER-OPTIONS" ! Likewise, in order to run only the `g++' "old-deja" tests in the ! testsuite with filenames matching `9805*', you would use make check-g++ RUNTESTFLAGS="old-deja.exp=9805* OTHER-OPTIONS" ! The `*.exp' files are located in the testsuite directories of the GCC ! source, the most important ones being `compile.exp', `execute.exp', ! `dg.exp' and `old-deja.exp'. To get a list of the possible `*.exp' ! files, pipe the output of `make check' into a file and look at the ! `Running ... .exp' lines. 6.2 Passing options and running multiple testsuites =================================================== You can pass multiple options to the testsuite using the ! `--target_board' option of DejaGNU, either passed as part of ! `RUNTESTFLAGS', or directly to `runtest' if you prefer to work outside the makefiles. For example, make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants" ! will run the standard `g++' testsuites ("unix" is the target name ! for a standard native testsuite situation), passing `-O3 ! -fmerge-constants' to the compiler on every test, i.e., slashes ! separate options. You can run the testsuites multiple times using combinations of options with a syntax similar to the brace expansion of popular shells: *************** options with a syntax similar to the bra *** 2562,2568 **** (Note the empty option caused by the trailing comma in the final group.) The following will run each testsuite eight times using the ! 'arm-sim' target, as if you had specified all possible combinations yourself: --target_board='arm-sim/-mhard-float/-O1 \ --- 2595,2601 ---- (Note the empty option caused by the trailing comma in the final group.) The following will run each testsuite eight times using the ! `arm-sim' target, as if you had specified all possible combinations yourself: --target_board='arm-sim/-mhard-float/-O1 \ *************** This list: *** 2579,2591 **** ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}" ! will generate four combinations, all involving '-Wextra'. The disadvantage to this method is that the testsuites are run in serial, which is a waste on multiprocessor systems. For users with GNU Make and a shell which performs brace expansion, you can run the testsuites in parallel by having the shell perform the combinations and ! 'make' do the parallel runs. Instead of using '--target_board', use a special makefile target: make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/... --- 2612,2624 ---- ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}" ! will generate four combinations, all involving `-Wextra'. The disadvantage to this method is that the testsuites are run in serial, which is a waste on multiprocessor systems. For users with GNU Make and a shell which performs brace expansion, you can run the testsuites in parallel by having the shell perform the combinations and ! `make' do the parallel runs. Instead of using `--target_board', use a special makefile target: make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/... *************** special makefile target: *** 2596,2631 **** will run three concurrent "make-gcc" testsuites, eventually testing all ten combinations as described above. Note that this is currently ! only supported in the 'gcc' subdirectory. (To see how this works, try ! typing 'echo' before the example given here.) 6.3 Additional testing for Java Class Libraries =============================================== ! The Java runtime tests can be executed via 'make check' in the ! 'TARGET/libjava/testsuite' directory in the build tree. The Mauve Project provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by placing the Mauve tree within the libjava testsuite at ! 'libjava/testsuite/libjava.mauve/mauve', or by specifying the location ! of that tree when invoking 'make', as in 'make MAUVEDIR=~/mauve check'. 6.4 How to interpret test results ================================= ! The result of running the testsuite are various '*.sum' and '*.log' ! files in the testsuite subdirectories. The '*.log' files contain a detailed log of the compiler invocations and the corresponding results, ! the '*.sum' files summarize the results. These summaries contain status ! codes for all tests: * PASS: the test passed as expected * XPASS: the test unexpectedly passed * FAIL: the test unexpectedly failed * XFAIL: the test failed as expected * UNSUPPORTED: the test is not supported on this platform * ERROR: the testsuite detected an error * WARNING: the testsuite detected a possible problem It is normal for some tests to report unexpected failures. At the --- 2629,2670 ---- will run three concurrent "make-gcc" testsuites, eventually testing all ten combinations as described above. Note that this is currently ! only supported in the `gcc' subdirectory. (To see how this works, try ! typing `echo' before the example given here.) 6.3 Additional testing for Java Class Libraries =============================================== ! The Java runtime tests can be executed via `make check' in the ! `TARGET/libjava/testsuite' directory in the build tree. The Mauve Project provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by placing the Mauve tree within the libjava testsuite at ! `libjava/testsuite/libjava.mauve/mauve', or by specifying the location ! of that tree when invoking `make', as in `make MAUVEDIR=~/mauve check'. 6.4 How to interpret test results ================================= ! The result of running the testsuite are various `*.sum' and `*.log' ! files in the testsuite subdirectories. The `*.log' files contain a detailed log of the compiler invocations and the corresponding results, ! the `*.sum' files summarize the results. These summaries contain ! status codes for all tests: * PASS: the test passed as expected + * XPASS: the test unexpectedly passed + * FAIL: the test unexpectedly failed + * XFAIL: the test failed as expected + * UNSUPPORTED: the test is not supported on this platform + * ERROR: the testsuite detected an error + * WARNING: the testsuite detected a possible problem It is normal for some tests to report unexpected failures. At the *************** fixed in future releases. *** 2637,2651 **** =========================== If you want to report the results to the GCC project, use the ! 'contrib/test_summary' shell script. Start it in the OBJDIR with SRCDIR/contrib/test_summary -p your_commentary.txt \ -m gcc-testresults@gcc.gnu.org |sh ! This script uses the 'Mail' program to send the results, so make sure ! it is in your 'PATH'. The file 'your_commentary.txt' is prepended to ! the testsuite summary and should contain any special remarks you have on ! your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. --- 2676,2690 ---- =========================== If you want to report the results to the GCC project, use the ! `contrib/test_summary' shell script. Start it in the OBJDIR with SRCDIR/contrib/test_summary -p your_commentary.txt \ -m gcc-testresults@gcc.gnu.org |sh ! This script uses the `Mail' program to send the results, so make ! sure it is in your `PATH'. The file `your_commentary.txt' is prepended ! to the testsuite summary and should contain any special remarks you ! have on your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. *************** File: gccinstall.info, Node: Final inst *** 2655,2662 **** 7 Installing GCC: Final installation ************************************ ! Now that GCC has been built (and optionally tested), you can install it ! with cd OBJDIR && make install We strongly recommend to install into a target directory where there --- 2694,2701 ---- 7 Installing GCC: Final installation ************************************ ! Now that GCC has been built (and optionally tested), you can install ! it with cd OBJDIR && make install We strongly recommend to install into a target directory where there *************** that depend on this debugging informatio *** 2666,2703 **** instance). That step completes the installation of GCC; user level binaries can ! be found in 'PREFIX/bin' where PREFIX is the value you specified with ! the '--prefix' to configure (or '/usr/local' by default). (If you ! specified '--bindir', that directory will be used instead; otherwise, if ! you specified '--exec-prefix', 'EXEC-PREFIX/bin' will be used.) Headers ! for the C++ and Java libraries are installed in 'PREFIX/include'; ! libraries in 'LIBDIR' (normally 'PREFIX/lib'); internal parts of the ! compiler in 'LIBDIR/gcc' and 'LIBEXECDIR/gcc'; documentation in info ! format in 'INFODIR' (normally 'PREFIX/info'). When installing cross-compilers, GCC's executables are not only ! installed into 'BINDIR', that is, 'EXEC-PREFIX/bin', but additionally ! into 'EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists. Typically, such "tooldirs" hold target-specific binutils, including assembler and linker. ! Installation into a temporary staging area or into a 'chroot' jail can be achieved with the command make DESTDIR=PATH-TO-ROOTDIR install where PATH-TO-ROOTDIR is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the ! directory specified by 'DESTDIR' need not exist yet; it will be created if necessary. ! There is a subtle point with tooldirs and 'DESTDIR': If you relocate ! a cross-compiler installation with e.g. 'DESTDIR=ROOTDIR', then the ! directory 'ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with duplicated GCC executables only if it already exists, it will not be ! created otherwise. This is regarded as a feature, not as a bug, because ! it gives slightly more control to the packagers using the 'DESTDIR' ! feature. You can install stripped programs and libraries with --- 2705,2742 ---- instance). That step completes the installation of GCC; user level binaries can ! be found in `PREFIX/bin' where PREFIX is the value you specified with ! the `--prefix' to configure (or `/usr/local' by default). (If you ! specified `--bindir', that directory will be used instead; otherwise, ! if you specified `--exec-prefix', `EXEC-PREFIX/bin' will be used.) ! Headers for the C++ and Java libraries are installed in ! `PREFIX/include'; libraries in `LIBDIR' (normally `PREFIX/lib'); ! internal parts of the compiler in `LIBDIR/gcc' and `LIBEXECDIR/gcc'; ! documentation in info format in `INFODIR' (normally `PREFIX/info'). When installing cross-compilers, GCC's executables are not only ! installed into `BINDIR', that is, `EXEC-PREFIX/bin', but additionally ! into `EXEC-PREFIX/TARGET-ALIAS/bin', if that directory exists. Typically, such "tooldirs" hold target-specific binutils, including assembler and linker. ! Installation into a temporary staging area or into a `chroot' jail can be achieved with the command make DESTDIR=PATH-TO-ROOTDIR install where PATH-TO-ROOTDIR is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the ! directory specified by `DESTDIR' need not exist yet; it will be created if necessary. ! There is a subtle point with tooldirs and `DESTDIR': If you relocate ! a cross-compiler installation with e.g. `DESTDIR=ROOTDIR', then the ! directory `ROOTDIR/EXEC-PREFIX/TARGET-ALIAS/bin' will be filled with duplicated GCC executables only if it already exists, it will not be ! created otherwise. This is regarded as a feature, not as a bug, ! because it gives slightly more control to the packagers using the ! `DESTDIR' feature. You can install stripped programs and libraries with *************** feature. *** 2705,2769 **** If you are bootstrapping a released version of GCC then please quickly review the build status page for your release, available from ! . If your system is not listed for the version of GCC that you built, send a note to indicating that you successfully built and installed GCC. Include the following information: ! * Output from running 'SRCDIR/config.guess'. Do not send that file itself, just the one-line output from running it. ! * The output of 'gcc -v' for your newly installed 'gcc'. This tells us which version of GCC you built and the options you passed to configure. ! * Whether you enabled all languages or a subset of them. If you used ! a full distribution then this information is part of the configure ! options in the output of 'gcc -v', but if you downloaded the "core" ! compiler plus additional front ends then it isn't apparent which ! ones you built unless you tell us about it. * If the build was for GNU/Linux, also include: ! * The distribution name and version (e.g., Red Hat 7.1 or Debian ! 2.2.3); this information should be available from ! '/etc/issue'. ! * The version of the Linux kernel, available from 'uname ! --version' or 'uname -a'. * The version of glibc you used; for RPM-based systems like Red ! Hat, Mandrake, and SuSE type 'rpm -q glibc' to get the glibc ! version, and on systems like Debian and Progeny use 'dpkg -l libc6'. ! For other systems, you can include similar information if you think ! it is relevant. * Any other information that you think would be useful to people ! building GCC on the same configuration. The new entry in the build ! status list will include a link to the archived copy of your message. ! We'd also like to know if the *note host/target specific installation ! notes: Specific. didn't include your host/target information or if that ! information is incomplete or out of date. Send a note to ! detailing how the information should be changed. If you find a bug, please report it following the bug reporting guidelines. ! If you want to print the GCC manuals, do 'cd OBJDIR; make dvi'. You ! will need to have 'texi2dvi' (version at least 4.7) and TeX installed. ! This creates a number of '.dvi' files in subdirectories of 'OBJDIR'; ! these may be converted for printing with programs such as 'dvips'. ! Alternately, by using 'make pdf' in place of 'make dvi', you can create ! documentation in the form of '.pdf' files; this requires 'texi2pdf', which is included with Texinfo version 4.8 and later. You can also buy printed manuals from the Free Software Foundation, though such manuals may not be for the most recent version of GCC. ! If you would like to generate online HTML documentation, do 'cd OBJDIR; make html' and HTML will be generated for the gcc manuals in ! 'OBJDIR/gcc/HTML'.  File: gccinstall.info, Node: Binaries, Next: Specific, Prev: Installing GCC, Up: Top --- 2744,2809 ---- If you are bootstrapping a released version of GCC then please quickly review the build status page for your release, available from ! `http://gcc.gnu.org/buildstat.html'. If your system is not listed for the version of GCC that you built, send a note to indicating that you successfully built and installed GCC. Include the following information: ! * Output from running `SRCDIR/config.guess'. Do not send that file itself, just the one-line output from running it. ! * The output of `gcc -v' for your newly installed `gcc'. This tells us which version of GCC you built and the options you passed to configure. ! * Whether you enabled all languages or a subset of them. If you ! used a full distribution then this information is part of the ! configure options in the output of `gcc -v', but if you downloaded ! the "core" compiler plus additional front ends then it isn't ! apparent which ones you built unless you tell us about it. * If the build was for GNU/Linux, also include: ! * The distribution name and version (e.g., Red Hat 7.1 or ! Debian 2.2.3); this information should be available from ! `/etc/issue'. ! * The version of the Linux kernel, available from `uname ! --version' or `uname -a'. * The version of glibc you used; for RPM-based systems like Red ! Hat, Mandrake, and SuSE type `rpm -q glibc' to get the glibc ! version, and on systems like Debian and Progeny use `dpkg -l libc6'. ! For other systems, you can include similar information if you ! think it is relevant. * Any other information that you think would be useful to people ! building GCC on the same configuration. The new entry in the ! build status list will include a link to the archived copy of your message. ! We'd also like to know if the *note host/target specific ! installation notes: Specific. didn't include your host/target ! information or if that information is incomplete or out of date. Send ! a note to detailing how the information should be ! changed. If you find a bug, please report it following the bug reporting guidelines. ! If you want to print the GCC manuals, do `cd OBJDIR; make dvi'. You ! will need to have `texi2dvi' (version at least 4.7) and TeX installed. ! This creates a number of `.dvi' files in subdirectories of `OBJDIR'; ! these may be converted for printing with programs such as `dvips'. ! Alternately, by using `make pdf' in place of `make dvi', you can create ! documentation in the form of `.pdf' files; this requires `texi2pdf', which is included with Texinfo version 4.8 and later. You can also buy printed manuals from the Free Software Foundation, though such manuals may not be for the most recent version of GCC. ! If you would like to generate online HTML documentation, do `cd OBJDIR; make html' and HTML will be generated for the gcc manuals in ! `OBJDIR/gcc/HTML'.  File: gccinstall.info, Node: Binaries, Next: Specific, Prev: Installing GCC, Up: Top *************** File: gccinstall.info, Node: Binaries, *** 2771,2780 **** 8 Installing GCC: Binaries ************************** ! We are often asked about pre-compiled versions of GCC. While we cannot ! provide these for all platforms, below you'll find links to binaries for ! various platforms where creating them by yourself is not easy due to ! various reasons. Please note that we did not create these binaries, nor do we support them. If you have any problems installing them, please contact their --- 2811,2820 ---- 8 Installing GCC: Binaries ************************** ! We are often asked about pre-compiled versions of GCC. While we ! cannot provide these for all platforms, below you'll find links to ! binaries for various platforms where creating them by yourself is not ! easy due to various reasons. Please note that we did not create these binaries, nor do we support them. If you have any problems installing them, please contact their *************** makers. *** 2797,2802 **** --- 2837,2843 ---- * Microsoft Windows: * The Cygwin project; + * The MinGW and mingw-w64 projects. * OpenPKG offers binaries for quite a number of platforms. *************** File: gccinstall.info, Node: Specific, *** 2810,2817 **** 9 Host/target specific installation notes for GCC ************************************************* ! Please read this document carefully _before_ installing the GNU Compiler ! Collection on your machine. Note that this list of install notes is _not_ a list of supported hosts or targets. Not all supported hosts and targets are listed here, --- 2851,2858 ---- 9 Host/target specific installation notes for GCC ************************************************* ! Please read this document carefully _before_ installing the GNU ! Compiler Collection on your machine. Note that this list of install notes is _not_ a list of supported hosts or targets. Not all supported hosts and targets are listed here, *************** have to. *** 2821,2850 **** aarch64*-*-* ============ ! Binutils pre 2.24 does not have support for selecting '-mabi' and does not support ILP32. If it is used to build GCC 4.9 or later, GCC will ! not support option '-mabi=ilp32'. To enable a workaround for the Cortex-A53 erratum number 835769 by default (for all CPUs regardless of -mcpu option given) at configure ! time use the '--enable-fix-cortex-a53-835769' option. This will enable the fix by default and can be explicitly disabled during compilation by ! passing the '-mno-fix-cortex-a53-835769' option. Conversely, ! '--disable-fix-cortex-a53-835769' will disable the workaround by default. The workaround is disabled by default if neither of ! '--enable-fix-cortex-a53-835769' or '--disable-fix-cortex-a53-835769' is ! given at configure time. To enable a workaround for the Cortex-A53 erratum number 843419 by default (for all CPUs regardless of -mcpu option given) at configure ! time use the '--enable-fix-cortex-a53-843419' option. This workaround ! is applied at link time. Enabling the workaround will cause GCC to pass ! the relevant option to the linker. It can be explicitly disabled during ! compilation by passing the '-mno-fix-cortex-a53-843419' option. ! Conversely, '--disable-fix-cortex-a53-843419' will disable the ! workaround by default. The workaround is disabled by default if neither ! of '--enable-fix-cortex-a53-843419' or '--disable-fix-cortex-a53-843419' ! is given at configure time. alpha*-*-* ========== --- 2862,2891 ---- aarch64*-*-* ============ ! Binutils pre 2.24 does not have support for selecting `-mabi' and does not support ILP32. If it is used to build GCC 4.9 or later, GCC will ! not support option `-mabi=ilp32'. To enable a workaround for the Cortex-A53 erratum number 835769 by default (for all CPUs regardless of -mcpu option given) at configure ! time use the `--enable-fix-cortex-a53-835769' option. This will enable the fix by default and can be explicitly disabled during compilation by ! passing the `-mno-fix-cortex-a53-835769' option. Conversely, ! `--disable-fix-cortex-a53-835769' will disable the workaround by default. The workaround is disabled by default if neither of ! `--enable-fix-cortex-a53-835769' or `--disable-fix-cortex-a53-835769' ! is given at configure time. To enable a workaround for the Cortex-A53 erratum number 843419 by default (for all CPUs regardless of -mcpu option given) at configure ! time use the `--enable-fix-cortex-a53-843419' option. This workaround ! is applied at link time. Enabling the workaround will cause GCC to ! pass the relevant option to the linker. It can be explicitly disabled ! during compilation by passing the `-mno-fix-cortex-a53-843419' option. ! Conversely, `--disable-fix-cortex-a53-843419' will disable the ! workaround by default. The workaround is disabled by default if ! neither of `--enable-fix-cortex-a53-843419' or ! `--disable-fix-cortex-a53-843419' is given at configure time. alpha*-*-* ========== *************** systems. *** 2868,2892 **** Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC ! 3.2, versions before 'alpha*-dec-osf4' are no longer supported. (These are the versions which identify themselves as DEC OSF/1.) amd64-*-solaris2.1[0-9]* ======================== ! This is a synonym for 'x86_64-*-solaris2.1[0-9]*'. arc-*-elf32 =========== ! Use 'configure --target=arc-elf32 --with-cpu=CPU --enable-languages="c,c++"' to configure GCC, with CPU being one of ! 'arc600', 'arc601', or 'arc700'. arc-linux-uclibc ================ ! Use 'configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"' to configure GCC. arm-*-eabi --- 2909,2933 ---- Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6, support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC ! 3.2, versions before `alpha*-dec-osf4' are no longer supported. (These are the versions which identify themselves as DEC OSF/1.) amd64-*-solaris2.1[0-9]* ======================== ! This is a synonym for `x86_64-*-solaris2.1[0-9]*'. arc-*-elf32 =========== ! Use `configure --target=arc-elf32 --with-cpu=CPU --enable-languages="c,c++"' to configure GCC, with CPU being one of ! `arc600', `arc601', or `arc700'. arc-linux-uclibc ================ ! Use `configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages="c,c++"' to configure GCC. arm-*-eabi *************** arm-*-eabi *** 2894,2903 **** ARM-family processors. Subtargets that use the ELF object format require GNU binutils 2.13 or newer. Such subtargets include: ! 'arm-*-netbsdelf', 'arm-*-*linux-*' and 'arm-*-rtemseabi'. Building the Ada frontend commonly fails (an infinite loop executing ! 'xsinfo') if the host compiler is GNAT 4.8. Host compilers built from the GNAT 4.6, 4.9 or 5 release branches are known to succeed. avr --- 2935,2944 ---- ARM-family processors. Subtargets that use the ELF object format require GNU binutils 2.13 or newer. Such subtargets include: ! `arm-*-netbsdelf', `arm-*-*linux-*' and `arm-*-rtemseabi'. Building the Ada frontend commonly fails (an infinite loop executing ! `xsinfo') if the host compiler is GNAT 4.8. Host compilers built from the GNAT 4.6, 4.9 or 5 release branches are known to succeed. avr *************** ATMEL AVR-family micro controllers. The *** 2907,2918 **** applications. There are no standard Unix configurations. *Note AVR Options: (gcc)AVR Options, for the list of supported MCU types. ! Use 'configure --target=avr --enable-languages="c"' to configure GCC. Further installation notes and other useful information about AVR tools can also be obtained from: * http://www.nongnu.org/avr/ * http://www.amelek.gda.pl/avr/ We _strongly_ recommend using binutils 2.13 or newer. --- 2948,2960 ---- applications. There are no standard Unix configurations. *Note AVR Options: (gcc)AVR Options, for the list of supported MCU types. ! Use `configure --target=avr --enable-languages="c"' to configure GCC. Further installation notes and other useful information about AVR tools can also be obtained from: * http://www.nongnu.org/avr/ + * http://www.amelek.gda.pl/avr/ We _strongly_ recommend using binutils 2.13 or newer. *************** tools can also be obtained from: *** 2925,2948 **** Blackfin ======== ! The Blackfin processor, an Analog Devices DSP. *Note Blackfin Options: (gcc)Blackfin Options, More information, and a version of binutils with support for this ! processor, is available at CR16 ==== ! The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is used in embedded applications. *Note CR16 Options: (gcc)CR16 Options, ! Use 'configure --target=cr16-elf --enable-languages=c,c++' to configure GCC for building a CR16 elf cross-compiler. ! Use 'configure --target=cr16-uclinux --enable-languages=c,c++' to configure GCC for building a CR16 uclinux cross-compiler. CRIS --- 2967,2990 ---- Blackfin ======== ! The Blackfin processor, an Analog Devices DSP. *Note Blackfin Options: (gcc)Blackfin Options, More information, and a version of binutils with support for this ! processor, is available at `http://blackfin.uclinux.org' CR16 ==== ! The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is used in embedded applications. *Note CR16 Options: (gcc)CR16 Options, ! Use `configure --target=cr16-elf --enable-languages=c,c++' to configure GCC for building a CR16 elf cross-compiler. ! Use `configure --target=cr16-uclinux --enable-languages=c,c++' to configure GCC for building a CR16 uclinux cross-compiler. CRIS *************** system-on-a-chip series. These are used *** 2955,2974 **** options. There are a few different CRIS targets: ! 'cris-axis-elf' Mainly for monolithic embedded systems. Includes a multilib for ! the 'v10' core used in 'ETRAX 100 LX'. ! 'cris-axis-linux-gnu' A GNU/Linux port for the CRIS architecture, currently targeting ! 'ETRAX 100 LX' by default. ! For 'cris-axis-elf' you need binutils 2.11 or newer. For ! 'cris-axis-linux-gnu' you need binutils 2.12 or newer. Pre-packaged tools can be obtained from ! . More information about this platform is available at ! . DOS === --- 2997,3017 ---- options. There are a few different CRIS targets: ! `cris-axis-elf' Mainly for monolithic embedded systems. Includes a multilib for ! the `v10' core used in `ETRAX 100 LX'. ! ! `cris-axis-linux-gnu' A GNU/Linux port for the CRIS architecture, currently targeting ! `ETRAX 100 LX' by default. ! For `cris-axis-elf' you need binutils 2.11 or newer. For ! `cris-axis-linux-gnu' you need binutils 2.12 or newer. Pre-packaged tools can be obtained from ! `ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/'. More information about this platform is available at ! `http://developer.axis.com/'. DOS === *************** Support for FreeBSD 1 was discontinued i *** 2995,3024 **** In order to better utilize FreeBSD base system functionality and match the configuration of the system compiler, GCC 4.5 and above as well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is ! present on FreeBSD 7 or later) and the use of '__cxa_atexit' by default ! (on FreeBSD 6 or later). The use of 'dl_iterate_phdr' inside ! 'libgcc_s.so.1' and boehm-gc (on FreeBSD 7 or later) is enabled by GCC 4.5 and above. We support FreeBSD using the ELF file format with DWARF 2 debugging ! for all CPU architectures. You may use '-gstabs' instead of '-g', if you really want the old debugging format. There are no known issues ! with mixing object files and libraries with different debugging formats. ! Otherwise, this release of GCC should now match more of the configuration used in the stock FreeBSD configuration of GCC. In ! particular, '--enable-threads' is now configured by default. However, as a general user, do not attempt to replace the system compiler with ! this release. Known to bootstrap and check with good results on FreeBSD ! 7.2-STABLE. In the past, known to bootstrap and check with good results ! on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and 5-CURRENT. ! The version of binutils installed in '/usr/bin' probably works with this release of GCC. Bootstrapping against the latest GNU binutils ! and/or the version found in '/usr/ports/devel/binutils' has been known to enable additional features and improve overall testsuite results. However, it is currently known that boehm-gc (which itself is required ! for java) may not configure properly on FreeBSD prior to the FreeBSD 7.0 ! release with GNU binutils after 2.16.1. ft32-*-elf ========== --- 3038,3068 ---- In order to better utilize FreeBSD base system functionality and match the configuration of the system compiler, GCC 4.5 and above as well as GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is ! present on FreeBSD 7 or later) and the use of `__cxa_atexit' by default ! (on FreeBSD 6 or later). The use of `dl_iterate_phdr' inside ! `libgcc_s.so.1' and boehm-gc (on FreeBSD 7 or later) is enabled by GCC 4.5 and above. We support FreeBSD using the ELF file format with DWARF 2 debugging ! for all CPU architectures. You may use `-gstabs' instead of `-g', if you really want the old debugging format. There are no known issues ! with mixing object files and libraries with different debugging ! formats. Otherwise, this release of GCC should now match more of the configuration used in the stock FreeBSD configuration of GCC. In ! particular, `--enable-threads' is now configured by default. However, as a general user, do not attempt to replace the system compiler with ! this release. Known to bootstrap and check with good results on ! FreeBSD 7.2-STABLE. In the past, known to bootstrap and check with ! good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5, 4.8, 4.9 and ! 5-CURRENT. ! The version of binutils installed in `/usr/bin' probably works with this release of GCC. Bootstrapping against the latest GNU binutils ! and/or the version found in `/usr/ports/devel/binutils' has been known to enable additional features and improve overall testsuite results. However, it is currently known that boehm-gc (which itself is required ! for java) may not configure properly on FreeBSD prior to the FreeBSD ! 7.0 release with GNU binutils after 2.16.1. ft32-*-elf ========== *************** Support for HP-UX version 9 and older wa *** 3046,3063 **** We require using gas/binutils on all hppa platforms. Version 2.19 or later is recommended. ! It may be helpful to configure GCC with the '--with-gnu-as' and ! '--with-as=...' options to ensure that GCC can find GAS. ! The HP assembler should not be used with GCC. It is rarely tested and ! may not work. It shouldn't be used with any languages other than C due ! to its many limitations. ! Specifically, '-g' does not work (HP-UX uses a peculiar debugging format which GCC does not know about). It also inserts timestamps into ! each object file it creates, causing the 3-stage comparison test to fail ! during a bootstrap. You should be able to continue by saying 'make ! all-host all-target' after getting the failure from 'make'. Various GCC features are not supported. For example, it does not support weak symbols or alias definitions. As a result, explicit --- 3090,3107 ---- We require using gas/binutils on all hppa platforms. Version 2.19 or later is recommended. ! It may be helpful to configure GCC with the `--with-gnu-as' and ! `--with-as=...' options to ensure that GCC can find GAS. ! The HP assembler should not be used with GCC. It is rarely tested ! and may not work. It shouldn't be used with any languages other than C ! due to its many limitations. ! Specifically, `-g' does not work (HP-UX uses a peculiar debugging format which GCC does not know about). It also inserts timestamps into ! each object file it creates, causing the 3-stage comparison test to ! fail during a bootstrap. You should be able to continue by saying ! `make all-host all-target' after getting the failure from `make'. Various GCC features are not supported. For example, it does not support weak symbols or alias definitions. As a result, explicit *************** difficult if not impossible to build man *** 3068,3074 **** PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc architecture specified for the target machine when configuring. PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when the ! target is a 'hppa1*' machine. The PROCESSOR_8000 model is not well suited to older processors. Thus, it is important to completely specify the machine architecture --- 3112,3118 ---- PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc architecture specified for the target machine when configuring. PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when the ! target is a `hppa1*' machine. The PROCESSOR_8000 model is not well suited to older processors. Thus, it is important to completely specify the machine architecture *************** when configuring if you want a model oth *** 3076,3098 **** macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different default scheduling model is desired. ! As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 through ! 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. This ! namespace change might cause problems when bootstrapping with an earlier ! version of GCC or the HP compiler as essentially the same namespace is ! required for an entire build. This problem can be avoided in a number ! of ways. With HP cc, 'UNIX_STD' can be set to '95' or '98'. Another ! way is to add an appropriate set of predefines to 'CC'. The description ! for the 'munix=' option contains a list of the predefines used with each ! standard. ! More specific information to 'hppa*-hp-hpux*' targets follows. hppa*-hp-hpux10 =============== For hpux10.20, we _highly_ recommend you pick up the latest sed patch ! 'PHCO_19798' from HP. The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are used for one-only code and data. This resolves many of the previous --- 3120,3142 ---- macro TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different default scheduling model is desired. ! As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10 ! through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. ! This namespace change might cause problems when bootstrapping with an ! earlier version of GCC or the HP compiler as essentially the same ! namespace is required for an entire build. This problem can be avoided ! in a number of ways. With HP cc, `UNIX_STD' can be set to `95' or ! `98'. Another way is to add an appropriate set of predefines to `CC'. ! The description for the `munix=' option contains a list of the ! predefines used with each standard. ! More specific information to `hppa*-hp-hpux*' targets follows. hppa*-hp-hpux10 =============== For hpux10.20, we _highly_ recommend you pick up the latest sed patch ! `PHCO_19798' from HP. The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are used for one-only code and data. This resolves many of the previous *************** hppa*-hp-hpux11 *** 3106,3118 **** GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot be used to compile GCC 3.0 and up. ! The libffi and libjava libraries haven't been ported to 64-bit ! HP-UX and don't build. Refer to binaries for information about obtaining precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained to build the ! Ada language as it can't be bootstrapped using C. Ada is only available ! for the 32-bit PA-RISC runtime. Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The bundled compiler supports only traditional C; you will need either --- 3150,3162 ---- GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot be used to compile GCC 3.0 and up. ! The libffi and libjava libraries haven't been ported to 64-bit HP-UX ! and don't build. Refer to binaries for information about obtaining precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained to build the ! Ada language as it can't be bootstrapped using C. Ada is only ! available for the 32-bit PA-RISC runtime. Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The bundled compiler supports only traditional C; you will need either *************** compiler, but the process requires sever *** 3123,3129 **** used to build later versions. The fastjar program contains ISO C code and can't be built with the HP bundled compiler. This problem can be avoided by not building the Java language. For example, use the ! '--enable-languages="c,c++,f77,objc"' option in your configure command. There are several possible approaches to building the distribution. Binutils can be built first using the HP tools. Then, the GCC --- 3167,3173 ---- used to build later versions. The fastjar program contains ISO C code and can't be built with the HP bundled compiler. This problem can be avoided by not building the Java language. For example, use the ! `--enable-languages="c,c++,f77,objc"' option in your configure command. There are several possible approaches to building the distribution. Binutils can be built first using the HP tools. Then, the GCC *************** start from a binary distribution. *** 3134,3212 **** On 64-bit capable systems, there are two distinct targets. Different installation prefixes must be used if both are to be installed on the ! same system. The 'hppa[1-2]*-hp-hpux11*' target generates code for the 32-bit PA-RISC runtime architecture and uses the HP linker. The ! 'hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0 architecture. The script config.guess now selects the target type based on the ! compiler detected during configuration. You must define 'PATH' or 'CC' so that configure finds an appropriate compiler for the initial ! bootstrap. When 'CC' is used, the definition should contain the options ! that are needed whenever 'CC' is used. Specifically, options that determine the runtime architecture must be ! in 'CC' to correctly select the target for the build. It is also ! convenient to place many other compiler options in 'CC'. For example, ! 'CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"' can be ! used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit ! K&R/bundled mode. The '+DA2.0W' option will result in the automatic ! selection of the 'hppa64-hp-hpux11*' target. The macro definition table ! of cpp needs to be increased for a successful build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when ! building with the bundled compiler, or when using the '-Ac' option. ! These defines aren't necessary with '-Ae'. ! It is best to explicitly configure the 'hppa64-hp-hpux11*' target ! with the '--with-ld=...' option. This overrides the standard search for ! ld. The two linkers supported on this target require different commands. The default linker is determined during configuration. As a result, it's not possible to switch linkers in the middle of a GCC build. This has been reported to sometimes occur in unified builds of binutils and GCC. A recent linker patch must be installed for the correct operation of ! GCC 3.3 and later. 'PHSS_26559' and 'PHSS_24304' are the oldest linker patches that are known to work. They are for HP-UX 11.00 and 11.11, ! respectively. 'PHSS_24303', the companion to 'PHSS_24304', might be usable but it hasn't been tested. These patches have been superseded. ! Consult the HP patch database to obtain the currently recommended linker ! patch for your system. The patches are necessary for the support of weak symbols on the 32-bit port, and for the running of initializers and finalizers. Weak symbols are implemented using SOM secondary definition symbols. Prior to HP-UX 11, there are bugs in the linker support for secondary symbols. The patches correct a problem of linker core dumps creating shared ! libraries containing secondary symbols, as well as various other linking ! issues involving secondary symbols. GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to run initializers and finalizers on the 64-bit port. The 32-bit port ! uses the linker '+init' and '+fini' options for the same purpose. The ! patches correct various problems with the +init/+fini options, including ! program core dumps. Binutils 2.14 corrects a problem on the 64-bit port ! resulting from HP's non-standard use of the .init and .fini sections for ! array initializers and finalizers. Although the HP and GNU linkers are both supported for the ! 'hppa64-hp-hpux11*' target, it is strongly recommended that the HP linker be used for link editing on this target. At this time, the GNU linker does not support the creation of long branch stubs. As a result, it can't successfully link binaries containing branch offsets larger than 8 megabytes. In addition, there are problems linking shared libraries, linking executables with ! '-static', and with dwarf2 unwind and exception support. It also doesn't provide stubs for internal calls to global functions in shared libraries, so these calls can't be overloaded. The HP dynamic loader does not support GNU symbol versioning, so symbol versioning is not supported. It may be necessary to disable ! symbol versioning with '--disable-symvers' when using GNU ld. POSIX threads are the default. The optional DCE thread library is ! not supported, so '--enable-threads=dce' does not work. *-*-linux-gnu ============= --- 3178,3256 ---- On 64-bit capable systems, there are two distinct targets. Different installation prefixes must be used if both are to be installed on the ! same system. The `hppa[1-2]*-hp-hpux11*' target generates code for the 32-bit PA-RISC runtime architecture and uses the HP linker. The ! `hppa64-hp-hpux11*' target generates 64-bit code for the PA-RISC 2.0 architecture. The script config.guess now selects the target type based on the ! compiler detected during configuration. You must define `PATH' or `CC' so that configure finds an appropriate compiler for the initial ! bootstrap. When `CC' is used, the definition should contain the ! options that are needed whenever `CC' is used. Specifically, options that determine the runtime architecture must be ! in `CC' to correctly select the target for the build. It is also ! convenient to place many other compiler options in `CC'. For example, ! `CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"' can ! be used to bootstrap the GCC 3.3 branch with the HP compiler in 64-bit ! K&R/bundled mode. The `+DA2.0W' option will result in the automatic ! selection of the `hppa64-hp-hpux11*' target. The macro definition ! table of cpp needs to be increased for a successful build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to be defined when ! building with the bundled compiler, or when using the `-Ac' option. ! These defines aren't necessary with `-Ae'. ! It is best to explicitly configure the `hppa64-hp-hpux11*' target ! with the `--with-ld=...' option. This overrides the standard search ! for ld. The two linkers supported on this target require different commands. The default linker is determined during configuration. As a result, it's not possible to switch linkers in the middle of a GCC build. This has been reported to sometimes occur in unified builds of binutils and GCC. A recent linker patch must be installed for the correct operation of ! GCC 3.3 and later. `PHSS_26559' and `PHSS_24304' are the oldest linker patches that are known to work. They are for HP-UX 11.00 and 11.11, ! respectively. `PHSS_24303', the companion to `PHSS_24304', might be usable but it hasn't been tested. These patches have been superseded. ! Consult the HP patch database to obtain the currently recommended ! linker patch for your system. The patches are necessary for the support of weak symbols on the 32-bit port, and for the running of initializers and finalizers. Weak symbols are implemented using SOM secondary definition symbols. Prior to HP-UX 11, there are bugs in the linker support for secondary symbols. The patches correct a problem of linker core dumps creating shared ! libraries containing secondary symbols, as well as various other ! linking issues involving secondary symbols. GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to run initializers and finalizers on the 64-bit port. The 32-bit port ! uses the linker `+init' and `+fini' options for the same purpose. The ! patches correct various problems with the +init/+fini options, ! including program core dumps. Binutils 2.14 corrects a problem on the ! 64-bit port resulting from HP's non-standard use of the .init and .fini ! sections for array initializers and finalizers. Although the HP and GNU linkers are both supported for the ! `hppa64-hp-hpux11*' target, it is strongly recommended that the HP linker be used for link editing on this target. At this time, the GNU linker does not support the creation of long branch stubs. As a result, it can't successfully link binaries containing branch offsets larger than 8 megabytes. In addition, there are problems linking shared libraries, linking executables with ! `-static', and with dwarf2 unwind and exception support. It also doesn't provide stubs for internal calls to global functions in shared libraries, so these calls can't be overloaded. The HP dynamic loader does not support GNU symbol versioning, so symbol versioning is not supported. It may be necessary to disable ! symbol versioning with `--disable-symvers' when using GNU ld. POSIX threads are the default. The optional DCE thread library is ! not supported, so `--enable-threads=dce' does not work. *-*-linux-gnu ============= *************** i?86-*-solaris2.10 *** 3229,3289 **** ================== Use this for Solaris 10 or later on x86 and x86-64 systems. Starting ! with GCC 4.7, there is also a 64-bit 'amd64-*-solaris2.1[0-9]*' or ! 'x86_64-*-solaris2.1[0-9]*' configuration that corresponds to ! 'sparcv9-sun-solaris2*'. It is recommended that you configure GCC to use the GNU assembler. The versions included in Solaris 10, from GNU binutils 2.15 (in ! '/usr/sfw/bin/gas'), and Solaris 11, from GNU binutils 2.19 or newer ! (also available as '/usr/bin/gas' and '/usr/gnu/bin/as'), work fine. ! Please note that the current version, from GNU binutils 2.26, only works ! on Solaris 12 when using the Solaris linker. On Solaris 10 and 11, you ! either have to wait for GNU binutils 2.26.1 or newer, or stay with GNU ! binutils 2.25.1. Recent versions of the Solaris assembler in ! '/usr/ccs/bin/as' work almost as well, though. For linking, the Solaris linker, is preferred. If you want to use the GNU linker instead, note that due to a packaging bug the version in ! Solaris 10, from GNU binutils 2.15 (in '/usr/sfw/bin/gld'), cannot be used, while the version in Solaris 11, from GNU binutils 2.19 or newer ! (also in '/usr/gnu/bin/ld' and '/usr/bin/gld'), works, as does the latest version, from GNU binutils 2.26. ! To use GNU 'as', configure with the options '--with-gnu-as --with-as=/usr/sfw/bin/gas'. It may be necessary to configure with ! '--without-gnu-ld --with-ld=/usr/ccs/bin/ld' to guarantee use of Sun ! 'ld'. ia64-*-linux ============ ! IA-64 processor (also known as IPF, or Itanium Processor Family) running ! GNU/Linux. If you are using the installed system libunwind library with ! '--with-system-libunwind', then you must use libunwind 0.98 or later. None of the following versions of GCC has an ABI that is compatible ! with any of the other versions in this list, with the exception that Red ! Hat 2.96 and Trillian 000171 are compatible with each other: 3.1, 3.0.2, ! 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. This primarily affects ! C++ programs and programs that create shared libraries. GCC 3.1 or ! later is recommended for compiling linux, the kernel. As of version 3.1 ! GCC is believed to be fully ABI compliant, and hence no more major ABI ! changes are expected. ia64-*-hpux* ============ Building GCC on this target requires the GNU Assembler. The bundled HP assembler will not work. To prevent GCC from using the wrong assembler, ! the option '--with-gnu-as' may be necessary. The GCC libunwind library has not been ported to HPUX. This means ! that for GCC versions 3.2.3 and earlier, '--enable-libunwind-exceptions' is required to build GCC. For GCC 3.3 and later, this is the default. ! For gcc 3.4.3 and later, '--enable-libunwind-exceptions' is removed and the system libunwind library will always be used. *-ibm-aix* --- 3273,3333 ---- ================== Use this for Solaris 10 or later on x86 and x86-64 systems. Starting ! with GCC 4.7, there is also a 64-bit `amd64-*-solaris2.1[0-9]*' or ! `x86_64-*-solaris2.1[0-9]*' configuration that corresponds to ! `sparcv9-sun-solaris2*'. It is recommended that you configure GCC to use the GNU assembler. The versions included in Solaris 10, from GNU binutils 2.15 (in ! `/usr/sfw/bin/gas'), and Solaris 11, from GNU binutils 2.19 or newer ! (also available as `/usr/bin/gas' and `/usr/gnu/bin/as'), work fine. ! Please note that the current version, from GNU binutils 2.26, only ! works on Solaris 12 when using the Solaris linker. On Solaris 10 and ! 11, you either have to wait for GNU binutils 2.26.1 or newer, or stay ! with GNU binutils 2.25.1. Recent versions of the Solaris assembler in ! `/usr/ccs/bin/as' work almost as well, though. For linking, the Solaris linker, is preferred. If you want to use the GNU linker instead, note that due to a packaging bug the version in ! Solaris 10, from GNU binutils 2.15 (in `/usr/sfw/bin/gld'), cannot be used, while the version in Solaris 11, from GNU binutils 2.19 or newer ! (also in `/usr/gnu/bin/ld' and `/usr/bin/gld'), works, as does the latest version, from GNU binutils 2.26. ! To use GNU `as', configure with the options `--with-gnu-as --with-as=/usr/sfw/bin/gas'. It may be necessary to configure with ! `--without-gnu-ld --with-ld=/usr/ccs/bin/ld' to guarantee use of Sun ! `ld'. ia64-*-linux ============ ! IA-64 processor (also known as IPF, or Itanium Processor Family) ! running GNU/Linux. If you are using the installed system libunwind library with ! `--with-system-libunwind', then you must use libunwind 0.98 or later. None of the following versions of GCC has an ABI that is compatible ! with any of the other versions in this list, with the exception that ! Red Hat 2.96 and Trillian 000171 are compatible with each other: 3.1, ! 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. This primarily ! affects C++ programs and programs that create shared libraries. GCC ! 3.1 or later is recommended for compiling linux, the kernel. As of ! version 3.1 GCC is believed to be fully ABI compliant, and hence no ! more major ABI changes are expected. ia64-*-hpux* ============ Building GCC on this target requires the GNU Assembler. The bundled HP assembler will not work. To prevent GCC from using the wrong assembler, ! the option `--with-gnu-as' may be necessary. The GCC libunwind library has not been ported to HPUX. This means ! that for GCC versions 3.2.3 and earlier, `--enable-libunwind-exceptions' is required to build GCC. For GCC 3.3 and later, this is the default. ! For gcc 3.4.3 and later, `--enable-libunwind-exceptions' is removed and the system libunwind library will always be used. *-ibm-aix* *************** Support for AIX version 4.2 and older wa *** 3294,3303 **** "out of memory" bootstrap failures may indicate a problem with process resource limits (ulimit). Hard limits are configured in the ! '/etc/security/limits' system configuration file. GCC 4.9 and above require a C++ compiler for bootstrap. IBM VAC++ / ! xlC cannot bootstrap GCC. xlc can bootstrap an older version of GCC and G++ can bootstrap recent releases of GCC. GCC can bootstrap with recent versions of IBM XLC, but bootstrapping --- 3338,3347 ---- "out of memory" bootstrap failures may indicate a problem with process resource limits (ulimit). Hard limits are configured in the ! `/etc/security/limits' system configuration file. GCC 4.9 and above require a C++ compiler for bootstrap. IBM VAC++ / ! xlC cannot bootstrap GCC. xlc can bootstrap an older version of GCC and G++ can bootstrap recent releases of GCC. GCC can bootstrap with recent versions of IBM XLC, but bootstrapping *************** LDR_CNTRL environment variable, e.g., *** 3309,3319 **** % export LDR_CNTRL One can start with a pre-compiled version of GCC to build from ! sources. One may delete GCC's "fixed" header files when starting with a ! version of GCC built for an earlier release of AIX. To speed up the configuration phases of bootstrapping and installing ! GCC, one may use GNU Bash instead of AIX '/bin/sh', e.g., % CONFIG_SHELL=/opt/freeware/bin/bash % export CONFIG_SHELL --- 3353,3363 ---- % export LDR_CNTRL One can start with a pre-compiled version of GCC to build from ! sources. One may delete GCC's "fixed" header files when starting with ! a version of GCC built for an earlier release of AIX. To speed up the configuration phases of bootstrapping and installing ! GCC, one may use GNU Bash instead of AIX `/bin/sh', e.g., % CONFIG_SHELL=/opt/freeware/bin/bash % export CONFIG_SHELL *************** SRCDIR/configure. *** 3324,3343 **** Because GCC on AIX is built as a 32-bit executable by default, (although it can generate 64-bit programs) the GMP and MPFR libraries ! required by gfortran must be 32-bit libraries. Building GMP and MPFR as ! static archive libraries works better than shared libraries. ! Errors involving 'alloca' when building GCC generally are due to an ! incorrect definition of 'CC' in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of the ! build, the native AIX compiler *must* be invoked as 'cc' (not 'xlc'). ! Once 'configure' has been informed of 'xlc', one needs to use 'make ! distclean' to remove the configure cache files and ensure that 'CC' environment variable does not provide a definition that will confuse ! 'configure'. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). ! The native 'as' and 'ld' are recommended for bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is the minimum level that supports bootstrap on AIX 5. The GNU Assembler has not been updated to support AIX 6 or AIX 7. The native AIX tools do --- 3368,3387 ---- Because GCC on AIX is built as a 32-bit executable by default, (although it can generate 64-bit programs) the GMP and MPFR libraries ! required by gfortran must be 32-bit libraries. Building GMP and MPFR ! as static archive libraries works better than shared libraries. ! Errors involving `alloca' when building GCC generally are due to an ! incorrect definition of `CC' in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of the ! build, the native AIX compiler *must* be invoked as `cc' (not `xlc'). ! Once `configure' has been informed of `xlc', one needs to use `make ! distclean' to remove the configure cache files and ensure that `CC' environment variable does not provide a definition that will confuse ! `configure'. If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). ! The native `as' and `ld' are recommended for bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is the minimum level that supports bootstrap on AIX 5. The GNU Assembler has not been updated to support AIX 6 or AIX 7. The native AIX tools do *************** interoperate with GCC. *** 3345,3392 **** AIX 7.1 added partial support for DWARF debugging, but full support requires AIX 7.1 TL03 SP7 that supports additional DWARF sections and ! fixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a version of ! libm.a missing important symbols; a fix for IV77796 will be included in ! SP6. AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX assembler change that sometimes produces corrupt assembly files causing AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause compilation failures with existing GCC installations. An AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR IZ98477 for ! AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, AIX 5.3 ! TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, AIX 6.1 ! TL07 and AIX 7.1 TL01 should include the fix. ! Building 'libstdc++.a' requires a fix for an AIX Assembler bug APAR ! IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix for ! another AIX Assembler bug and a co-dependent AIX Archiver fix referenced ! as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1) ! 'libstdc++' in GCC 3.4 increments the major version number of the ! shared object and GCC installation places the 'libstdc++.a' shared library in a common location which will overwrite the and GCC 3.3 ! version of the shared library. Applications either need to be re-linked ! against the new shared library or the GCC 3.1 and GCC 3.3 versions of ! the 'libstdc++' shared object needs to be available to the AIX runtime ! loader. The GCC 3.1 'libstdc++.so.4', if present, and GCC 3.3 ! 'libstdc++.so.5' shared objects can be installed for runtime dynamic ! loading using the following steps to set the 'F_LOADONLY' flag in the ! shared object for _each_ multilib 'libstdc++.a' installed: ! Extract the shared objects from the currently installed 'libstdc++.a' ! archive: % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5 ! Enable the 'F_LOADONLY' flag so that the shared object will be available for runtime dynamic loading, but not linking: % strip -e libstdc++.so.4 libstdc++.so.5 ! Archive the runtime-only shared object in the GCC 3.4 'libstdc++.a' archive: % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5 ! Eventually, the '--with-aix-soname=svr4' configure option may drop the need for this procedure for libraries that support it. Linking executables and shared libraries may produce warnings of --- 3389,3436 ---- AIX 7.1 added partial support for DWARF debugging, but full support requires AIX 7.1 TL03 SP7 that supports additional DWARF sections and ! fixes a bug in the assembler. AIX 7.1 TL03 SP5 distributed a version ! of libm.a missing important symbols; a fix for IV77796 will be included ! in SP6. AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX assembler change that sometimes produces corrupt assembly files causing AIX linker errors. The bug breaks GCC bootstrap on AIX and can cause compilation failures with existing GCC installations. An AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR IZ98477 for ! AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8, AIX 5.3 ! TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6, AIX ! 6.1 TL07 and AIX 7.1 TL01 should include the fix. ! Building `libstdc++.a' requires a fix for an AIX Assembler bug APAR ! IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a fix ! for another AIX Assembler bug and a co-dependent AIX Archiver fix ! referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1) ! `libstdc++' in GCC 3.4 increments the major version number of the ! shared object and GCC installation places the `libstdc++.a' shared library in a common location which will overwrite the and GCC 3.3 ! version of the shared library. Applications either need to be ! re-linked against the new shared library or the GCC 3.1 and GCC 3.3 ! versions of the `libstdc++' shared object needs to be available to the ! AIX runtime loader. The GCC 3.1 `libstdc++.so.4', if present, and GCC ! 3.3 `libstdc++.so.5' shared objects can be installed for runtime ! dynamic loading using the following steps to set the `F_LOADONLY' flag ! in the shared object for _each_ multilib `libstdc++.a' installed: ! Extract the shared objects from the currently installed ! `libstdc++.a' archive: % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5 ! Enable the `F_LOADONLY' flag so that the shared object will be available for runtime dynamic loading, but not linking: % strip -e libstdc++.so.4 libstdc++.so.5 ! Archive the runtime-only shared object in the GCC 3.4 `libstdc++.a' archive: % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5 ! Eventually, the `--with-aix-soname=svr4' configure option may drop the need for this procedure for libraries that support it. Linking executables and shared libraries may produce warnings of *************** executable. *** 3401,3413 **** to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during linking such as "not a COFF file". The version of the routines shipped ! with AIX 4.3.1 should work for a 32-bit environment. The '-g' option of ! the archive command may be used to create archives of 32-bit objects ! using the original "small format". A correct version of the routines is ! shipped with AIX 4.3.2 and above. Some versions of the AIX binder (linker) can fail with a relocation ! overflow severe error when the '-bbigtoc' option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is available from IBM Customer Support and from its --- 3445,3457 ---- to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during linking such as "not a COFF file". The version of the routines shipped ! with AIX 4.3.1 should work for a 32-bit environment. The `-g' option ! of the archive command may be used to create archives of 32-bit objects ! using the original "small format". A correct version of the routines ! is shipped with AIX 4.3.2 and above. Some versions of the AIX binder (linker) can fail with a relocation ! overflow severe error when the `-bbigtoc' option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is available from IBM Customer Support and from its *************** and from its techsupport.services.ibm.co *** 3426,3440 **** fix is incorporated in AIX 4.3.1 and above. AIX provides National Language Support (NLS). Compilers and ! assemblers use NLS to support locale-specific representations of various ! data formats including floating-point numbers (e.g., '.' vs ',' for ! separating decimal fractions). There have been problems reported where ! GCC does not produce the same floating-point formats that the assembler ! expects. If one encounters this problem, set the 'LANG' environment ! variable to 'C' or 'En_US'. ! A default can be specified with the '-mcpu=CPU_TYPE' switch and using ! the configure option '--with-cpu-CPU_TYPE'. iq2000-*-elf ============ --- 3470,3484 ---- fix is incorporated in AIX 4.3.1 and above. AIX provides National Language Support (NLS). Compilers and ! assemblers use NLS to support locale-specific representations of ! various data formats including floating-point numbers (e.g., `.' vs ! `,' for separating decimal fractions). There have been problems ! reported where GCC does not produce the same floating-point formats ! that the assembler expects. If one encounters this problem, set the ! `LANG' environment variable to `C' or `En_US'. ! A default can be specified with the `-mcpu=CPU_TYPE' switch and ! using the configure option `--with-cpu-CPU_TYPE'. iq2000-*-elf ============ *************** systems. *** 3469,3490 **** m68k-*-* ======== ! By default, 'm68k-*-elf*', 'm68k-*-rtems', 'm68k-*-uclinux' and ! 'm68k-*-linux' build libraries for both M680x0 and ColdFire processors. ! If you only need the M680x0 libraries, you can omit the ColdFire ones by ! passing '--with-arch=m68k' to 'configure'. Alternatively, you can omit ! the M680x0 libraries by passing '--with-arch=cf' to 'configure'. These ! targets default to 5206 or 5475 code as appropriate for the target ! system when configured with '--with-arch=cf' and 68020 code otherwise. ! The 'm68k-*-netbsd' and 'm68k-*-openbsd' targets also support the ! '--with-arch' option. They will generate ColdFire CFV4e code when ! configured with '--with-arch=cf' and 68020 code otherwise. You can override the default processors listed above by configuring ! with '--with-cpu=TARGET'. This TARGET can either be a '-mcpu' argument ! or one of the following values: 'm68000', 'm68010', 'm68020', 'm68030', ! 'm68040', 'm68060', 'm68020-40' and 'm68020-60'. GCC requires at least binutils version 2.17 on these targets. --- 3513,3535 ---- m68k-*-* ======== ! By default, `m68k-*-elf*', `m68k-*-rtems', `m68k-*-uclinux' and ! `m68k-*-linux' build libraries for both M680x0 and ColdFire processors. ! If you only need the M680x0 libraries, you can omit the ColdFire ones ! by passing `--with-arch=m68k' to `configure'. Alternatively, you can ! omit the M680x0 libraries by passing `--with-arch=cf' to `configure'. ! These targets default to 5206 or 5475 code as appropriate for the ! target system when configured with `--with-arch=cf' and 68020 code ! otherwise. ! The `m68k-*-netbsd' and `m68k-*-openbsd' targets also support the ! `--with-arch' option. They will generate ColdFire CFV4e code when ! configured with `--with-arch=cf' and 68020 code otherwise. You can override the default processors listed above by configuring ! with `--with-cpu=TARGET'. This TARGET can either be a `-mcpu' argument ! or one of the following values: `m68000', `m68010', `m68020', `m68030', ! `m68040', `m68060', `m68020-40' and `m68020-60'. GCC requires at least binutils version 2.17 on these targets. *************** m68k-*-uclinux *** 3492,3498 **** ============== GCC 4.3 changed the uClinux configuration so that it uses the ! 'm68k-linux-gnu' ABI rather than the 'm68k-elf' ABI. It also added improved support for C++ and flat shared libraries, both of which were ABI changes. --- 3537,3543 ---- ============== GCC 4.3 changed the uClinux configuration so that it uses the ! `m68k-linux-gnu' ABI rather than the `m68k-elf' ABI. It also added improved support for C++ and flat shared libraries, both of which were ABI changes. *************** optional, and there should not be a warn *** 3522,3557 **** The libstdc++ atomic locking routines for MIPS targets requires MIPS II and later. A patch went in just after the GCC 3.3 release to make ! 'mips*-*-*' use the generic implementation instead. You can also ! configure for 'mipsel-elf' as a workaround. The 'mips*-*-linux*' target ! continues to use the MIPS II routines. More work on this is expected in ! future releases. ! The built-in '__sync_*' functions are available on MIPS II and later ! systems and others that support the 'll', 'sc' and 'sync' instructions. ! This can be overridden by passing '--with-llsc' or '--without-llsc' when ! configuring GCC. Since the Linux kernel emulates these instructions if ! they are missing, the default for 'mips*-*-linux*' targets is ! '--with-llsc'. The '--with-llsc' and '--without-llsc' configure options ! may be overridden at compile time by passing the '-mllsc' or '-mno-llsc' ! options to the compiler. MIPS systems check for division by zero (unless ! '-mno-check-zero-division' is passed to the compiler) by generating ! either a conditional trap or a break instruction. Using trap results in ! smaller code, but is only supported on MIPS II and later. Also, some ! versions of the Linux kernel have a bug that prevents trap from ! generating the proper signal ('SIGFPE'). To enable the use of break, ! use the '--with-divide=breaks' 'configure' option when configuring GCC. The default is to use traps on systems that support them. The assembler from GNU binutils 2.17 and earlier has a bug in the way ! it sorts relocations for REL targets (o32, o64, EABI). This can cause bad code to be generated for simple C++ programs. Also the linker from GNU binutils versions prior to 2.17 has a bug which causes the runtime ! linker stubs in very large programs, like 'libgcj.so', to be incorrectly ! generated. GNU Binutils 2.18 and later (and snapshots made after Nov. ! 9, 2006) should be free from both of these problems. mips-sgi-irix5 ============== --- 3567,3602 ---- The libstdc++ atomic locking routines for MIPS targets requires MIPS II and later. A patch went in just after the GCC 3.3 release to make ! `mips*-*-*' use the generic implementation instead. You can also ! configure for `mipsel-elf' as a workaround. The `mips*-*-linux*' ! target continues to use the MIPS II routines. More work on this is ! expected in future releases. ! The built-in `__sync_*' functions are available on MIPS II and later ! systems and others that support the `ll', `sc' and `sync' instructions. ! This can be overridden by passing `--with-llsc' or `--without-llsc' ! when configuring GCC. Since the Linux kernel emulates these ! instructions if they are missing, the default for `mips*-*-linux*' ! targets is `--with-llsc'. The `--with-llsc' and `--without-llsc' ! configure options may be overridden at compile time by passing the ! `-mllsc' or `-mno-llsc' options to the compiler. MIPS systems check for division by zero (unless ! `-mno-check-zero-division' is passed to the compiler) by generating ! either a conditional trap or a break instruction. Using trap results ! in smaller code, but is only supported on MIPS II and later. Also, ! some versions of the Linux kernel have a bug that prevents trap from ! generating the proper signal (`SIGFPE'). To enable the use of break, ! use the `--with-divide=breaks' `configure' option when configuring GCC. The default is to use traps on systems that support them. The assembler from GNU binutils 2.17 and earlier has a bug in the way ! it sorts relocations for REL targets (o32, o64, EABI). This can cause bad code to be generated for simple C++ programs. Also the linker from GNU binutils versions prior to 2.17 has a bug which causes the runtime ! linker stubs in very large programs, like `libgcj.so', to be ! incorrectly generated. GNU Binutils 2.18 and later (and snapshots made ! after Nov. 9, 2006) should be free from both of these problems. mips-sgi-irix5 ============== *************** Nvidia PTX target. *** 3593,3613 **** Instead of GNU binutils, you will need to install nvptx-tools. Tell GCC where to find it: ! '--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin'. A nvptx port of newlib is available at nvptx-newlib. It can be ! automatically built together with GCC. For this, add a symbolic link to ! nvptx-newlib's 'newlib' directory to the directory containing the GCC ! sources. ! Use the '--disable-sjlj-exceptions' and ! '--enable-newlib-io-long-long' options when configuring. powerpc-*-* =========== ! You can specify a default version for the '-mcpu=CPU_TYPE' switch by ! using the configure option '--with-cpu-CPU_TYPE'. You will need binutils 2.15 or newer for a working GCC. --- 3638,3658 ---- Instead of GNU binutils, you will need to install nvptx-tools. Tell GCC where to find it: ! `--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin'. A nvptx port of newlib is available at nvptx-newlib. It can be ! automatically built together with GCC. For this, add a symbolic link ! to nvptx-newlib's `newlib' directory to the directory containing the ! GCC sources. ! Use the `--disable-sjlj-exceptions' and ! `--enable-newlib-io-long-long' options when configuring. powerpc-*-* =========== ! You can specify a default version for the `-mcpu=CPU_TYPE' switch by ! using the configure option `--with-cpu-CPU_TYPE'. You will need binutils 2.15 or newer for a working GCC. *************** PowerPC running Darwin (Mac OS X kernel) *** 3618,3628 **** Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool ! binaries are available at . This version of GCC requires at least cctools-590.36. The cctools-590.36 package referenced from ! will not work on systems older than 10.3.9 (aka darwin7.9.0). powerpc-*-elf --- 3663,3673 ---- Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool ! binaries are available at `http://opensource.apple.com/'. This version of GCC requires at least cctools-590.36. The cctools-590.36 package referenced from ! `http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html' will not work on systems older than 10.3.9 (aka darwin7.9.0). powerpc-*-elf *************** Embedded PowerPC system in little endian *** 3670,3683 **** rl78-*-elf ========== ! The Renesas RL78 processor. This configuration is intended for embedded ! systems. rx-*-elf ======== The Renesas RX processor. See ! for more information about this processor. s390-*-linux* --- 3715,3728 ---- rl78-*-elf ========== ! The Renesas RL78 processor. This configuration is intended for ! embedded systems. rx-*-elf ======== The Renesas RX processor. See ! `http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&fp=/products/mpumcu/rx_family/rx600_series' for more information about this processor. s390-*-linux* *************** GCC 4.6. *** 3705,3717 **** Sun does not ship a C compiler with Solaris 2 before Solaris 10, though you can download the Sun Studio compilers for free. In Solaris ! 10 and 11, GCC 3.4.3 is available as '/usr/sfw/bin/gcc'. Solaris 11 ! also provides GCC 4.5.2, 4.7.3, and 4.8.2 as '/usr/gcc/4.5/bin/gcc' or similar. Alternatively, you can install a pre-built GCC to bootstrap ! and install GCC. See the binaries page for details. ! The Solaris 2 '/bin/sh' will often fail to configure 'libstdc++-v3', ! 'boehm-gc' or 'libjava'. We therefore recommend using the following initial sequence of commands % CONFIG_SHELL=/bin/ksh --- 3750,3762 ---- Sun does not ship a C compiler with Solaris 2 before Solaris 10, though you can download the Sun Studio compilers for free. In Solaris ! 10 and 11, GCC 3.4.3 is available as `/usr/sfw/bin/gcc'. Solaris 11 ! also provides GCC 4.5.2, 4.7.3, and 4.8.2 as `/usr/gcc/4.5/bin/gcc' or similar. Alternatively, you can install a pre-built GCC to bootstrap ! and install GCC. See the binaries page for details. ! The Solaris 2 `/bin/sh' will often fail to configure `libstdc++-v3', ! `boehm-gc' or `libjava'. We therefore recommend using the following initial sequence of commands % CONFIG_SHELL=/bin/ksh *************** initial sequence of commands *** 3719,3788 **** and proceed as described in the configure instructions. In addition we strongly recommend specifying an absolute path to invoke ! 'SRCDIR/configure'. Solaris 10 comes with a number of optional OS packages. Some of ! these are needed to use GCC fully, namely 'SUNWarc', 'SUNWbtool', ! 'SUNWesu', 'SUNWhea', 'SUNWlibm', 'SUNWsprot', and 'SUNWtoo'. If you did not install all optional packages when installing Solaris 10, you will need to verify that the packages that GCC needs are installed. To ! check whether an optional package is installed, use the 'pkginfo' ! command. To add an optional package, use the 'pkgadd' command. For further details, see the Solaris 10 documentation. Starting with Solaris 11, the package management has changed, so you ! need to check for 'system/header', 'system/linker', and ! 'developer/assembler' packages. Checking for and installing packages is ! done with the 'pkg' command now. ! Trying to use the linker and other tools in '/usr/ucb' to install GCC ! has been observed to cause trouble. For example, the linker may hang ! indefinitely. The fix is to remove '/usr/ucb' from your 'PATH'. The build process works more smoothly with the legacy Sun tools so, ! if you have '/usr/xpg4/bin' in your 'PATH', we recommend that you place ! '/usr/bin' before '/usr/xpg4/bin' for the duration of the build. We recommend the use of the Solaris assembler or the GNU assembler, ! in conjunction with the Solaris linker. The GNU 'as' versions included ! in Solaris 10, from GNU binutils 2.15 (in '/usr/sfw/bin/gas'), and ! Solaris 11, from GNU binutils 2.19 or newer (also in '/usr/bin/gas' and ! '/usr/gnu/bin/as'), are known to work. Current versions of GNU binutils ! (2.26) are known to work as well, with the caveat mentioned in i?86-*-solaris2.10 . Note that your mileage may vary if you use a combination of the GNU tools and the Solaris tools: while the ! combination GNU 'as' + Sun 'ld' should reasonably work, the reverse ! combination Sun 'as' + GNU 'ld' may fail to build or cause memory ! corruption at runtime in some cases for C++ programs. GNU 'ld' usually works as well, although the version included in Solaris 10 cannot be ! used due to several bugs. Again, the current version (2.26) is known to ! work, but generally lacks platform specific features, so better stay ! with Solaris 'ld'. To use the LTO linker plugin ('-fuse-linker-plugin') ! with GNU 'ld', GNU binutils _must_ be configured with ! '--enable-largefile'. ! To enable symbol versioning in 'libstdc++' with the Solaris linker, ! you need to have any version of GNU 'c++filt', which is part of GNU ! binutils. 'libstdc++' symbol versioning will be disabled if no ! appropriate version is found. Solaris 'c++filt' from the Solaris Studio ! compilers does _not_ work. ! GNU 'make' version 3.81 or later is required to build libjava with the Solaris linker. Sun bug 4927647 sometimes causes random spurious testsuite failures related to missing diagnostic output. This bug doesn't affect GCC ! itself, rather it is a kernel bug triggered by the 'expect' program ! which is used only by the GCC testsuite driver. When the bug causes the ! 'expect' program to miss anticipated output, extra testsuite failures ! appear. sparc*-*-* ========== This section contains general configuration information for all ! SPARC-based platforms. In addition to reading this section, please read ! all other sections that match your target. Newer versions of the GNU Multiple Precision Library (GMP), the MPFR library and the MPC library are known to be miscompiled by earlier --- 3764,3833 ---- and proceed as described in the configure instructions. In addition we strongly recommend specifying an absolute path to invoke ! `SRCDIR/configure'. Solaris 10 comes with a number of optional OS packages. Some of ! these are needed to use GCC fully, namely `SUNWarc', `SUNWbtool', ! `SUNWesu', `SUNWhea', `SUNWlibm', `SUNWsprot', and `SUNWtoo'. If you did not install all optional packages when installing Solaris 10, you will need to verify that the packages that GCC needs are installed. To ! check whether an optional package is installed, use the `pkginfo' ! command. To add an optional package, use the `pkgadd' command. For further details, see the Solaris 10 documentation. Starting with Solaris 11, the package management has changed, so you ! need to check for `system/header', `system/linker', and ! `developer/assembler' packages. Checking for and installing packages ! is done with the `pkg' command now. ! Trying to use the linker and other tools in `/usr/ucb' to install ! GCC has been observed to cause trouble. For example, the linker may ! hang indefinitely. The fix is to remove `/usr/ucb' from your `PATH'. The build process works more smoothly with the legacy Sun tools so, ! if you have `/usr/xpg4/bin' in your `PATH', we recommend that you place ! `/usr/bin' before `/usr/xpg4/bin' for the duration of the build. We recommend the use of the Solaris assembler or the GNU assembler, ! in conjunction with the Solaris linker. The GNU `as' versions included ! in Solaris 10, from GNU binutils 2.15 (in `/usr/sfw/bin/gas'), and ! Solaris 11, from GNU binutils 2.19 or newer (also in `/usr/bin/gas' and ! `/usr/gnu/bin/as'), are known to work. Current versions of GNU ! binutils (2.26) are known to work as well, with the caveat mentioned in i?86-*-solaris2.10 . Note that your mileage may vary if you use a combination of the GNU tools and the Solaris tools: while the ! combination GNU `as' + Sun `ld' should reasonably work, the reverse ! combination Sun `as' + GNU `ld' may fail to build or cause memory ! corruption at runtime in some cases for C++ programs. GNU `ld' usually works as well, although the version included in Solaris 10 cannot be ! used due to several bugs. Again, the current version (2.26) is known ! to work, but generally lacks platform specific features, so better stay ! with Solaris `ld'. To use the LTO linker plugin ! (`-fuse-linker-plugin') with GNU `ld', GNU binutils _must_ be ! configured with `--enable-largefile'. ! To enable symbol versioning in `libstdc++' with the Solaris linker, ! you need to have any version of GNU `c++filt', which is part of GNU ! binutils. `libstdc++' symbol versioning will be disabled if no ! appropriate version is found. Solaris `c++filt' from the Solaris ! Studio compilers does _not_ work. ! GNU `make' version 3.81 or later is required to build libjava with the Solaris linker. Sun bug 4927647 sometimes causes random spurious testsuite failures related to missing diagnostic output. This bug doesn't affect GCC ! itself, rather it is a kernel bug triggered by the `expect' program ! which is used only by the GCC testsuite driver. When the bug causes ! the `expect' program to miss anticipated output, extra testsuite ! failures appear. sparc*-*-* ========== This section contains general configuration information for all ! SPARC-based platforms. In addition to reading this section, please ! read all other sections that match your target. Newer versions of the GNU Multiple Precision Library (GMP), the MPFR library and the MPC library are known to be miscompiled by earlier *************** this difference is quite significant for *** 3799,3816 **** information. Starting with Solaris 7, the operating system is capable of executing ! 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this; the ! '-m64' option enables 64-bit code generation. However, if all you want ! is code tuned for the UltraSPARC CPU, you should try the ! '-mtune=ultrasparc' option instead, which produces code that, unlike full 64-bit code, can still run on non-UltraSPARC machines. When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library on a Solaris 7 or later system, the canonical ! target triplet must be specified as the 'build' parameter on the configure line. This target triplet can be obtained by invoking ! './config.guess' in the toplevel source directory of GCC (and not that ! of GMP or MPFR or MPC). For example on a Solaris 9 system: % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx --- 3844,3861 ---- information. Starting with Solaris 7, the operating system is capable of executing ! 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this; ! the `-m64' option enables 64-bit code generation. However, if all you ! want is code tuned for the UltraSPARC CPU, you should try the ! `-mtune=ultrasparc' option instead, which produces code that, unlike full 64-bit code, can still run on non-UltraSPARC machines. When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library on a Solaris 7 or later system, the canonical ! target triplet must be specified as the `build' parameter on the configure line. This target triplet can be obtained by invoking ! `./config.guess' in the toplevel source directory of GCC (and not that ! of GMP or MPFR or MPC). For example on a Solaris 9 system: % ./configure --build=sparc-sun-solaris2.9 --prefix=xxx *************** sparc-sun-solaris2.10 *** 3818,3824 **** ===================== There is a bug in older versions of the Sun assembler which breaks ! thread-local storage (TLS). A typical error message is ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o: symbol : bad symbol type SECT: symbol type must be TLS --- 3863,3869 ---- ===================== There is a bug in older versions of the Sun assembler which breaks ! thread-local storage (TLS). A typical error message is ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o: symbol : bad symbol type SECT: symbol type must be TLS *************** sparc-*-linux* *** 3830,3843 **** GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or newer on this platform. All earlier binutils and glibc releases ! mishandled unaligned relocations on 'sparc-*-*' targets. sparc64-*-solaris2* =================== When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library, the canonical target triplet must be ! specified as the 'build' parameter on the configure line. For example on a Solaris 9 system: % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx --- 3875,3888 ---- GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or newer on this platform. All earlier binutils and glibc releases ! mishandled unaligned relocations on `sparc-*-*' targets. sparc64-*-solaris2* =================== When configuring the GNU Multiple Precision Library (GMP), the MPFR library or the MPC library, the canonical target triplet must be ! specified as the `build' parameter on the configure line. For example on a Solaris 9 system: % ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx *************** on a Solaris 9 system: *** 3845,3857 **** sparcv9-*-solaris2* =================== ! This is a synonym for 'sparc64-*-solaris2*'. c6x-*-* ======= ! The C6X family of processors. This port requires binutils-2.22 or ! newer. tilegx-*-linux* =============== --- 3890,3901 ---- sparcv9-*-solaris2* =================== ! This is a synonym for `sparc64-*-solaris2*'. c6x-*-* ======= ! The C6X family of processors. This port requires binutils-2.22 or newer. tilegx-*-linux* =============== *************** systems. *** 3880,3910 **** *-*-vxworks* ============ ! Support for VxWorks is in flux. At present GCC supports _only_ the very ! recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. We ! welcome patches for other architectures supported by VxWorks 5.5. Support for VxWorks AE would also be welcome; we believe this is merely a matter of writing an appropriate "configlette" (see below). We are not interested in supporting older, a.out or COFF-based, versions of VxWorks in GCC 3. VxWorks comes with an older version of GCC installed in ! '$WIND_BASE/host'; we recommend you do not overwrite it. Choose an installation PREFIX entirely outside $WIND_BASE. Before running ! 'configure', create the directories 'PREFIX' and 'PREFIX/bin'. Link or ! copy the appropriate assembler, linker, etc. into 'PREFIX/bin', and set ! your PATH to include that directory while running both 'configure' and ! 'make'. ! You must give 'configure' the '--with-headers=$WIND_BASE/target/h' ! switch so that it can find the VxWorks system headers. Since VxWorks is ! a cross compilation target only, you must also specify ! '--target=TARGET'. 'configure' will attempt to create the directory ! 'PREFIX/TARGET/sys-include' and copy files into it; make sure the user ! running 'configure' has sufficient privilege to do so. GCC's exception handling runtime requires a special "configlette" ! module, 'contrib/gthr_supp_vxw_5x.c'. Follow the instructions in that file to add the module to your kernel build. (Future versions of VxWorks will incorporate this module.) --- 3924,3954 ---- *-*-vxworks* ============ ! Support for VxWorks is in flux. At present GCC supports _only_ the ! very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. ! We welcome patches for other architectures supported by VxWorks 5.5. Support for VxWorks AE would also be welcome; we believe this is merely a matter of writing an appropriate "configlette" (see below). We are not interested in supporting older, a.out or COFF-based, versions of VxWorks in GCC 3. VxWorks comes with an older version of GCC installed in ! `$WIND_BASE/host'; we recommend you do not overwrite it. Choose an installation PREFIX entirely outside $WIND_BASE. Before running ! `configure', create the directories `PREFIX' and `PREFIX/bin'. Link or ! copy the appropriate assembler, linker, etc. into `PREFIX/bin', and set ! your PATH to include that directory while running both `configure' and ! `make'. ! You must give `configure' the `--with-headers=$WIND_BASE/target/h' ! switch so that it can find the VxWorks system headers. Since VxWorks ! is a cross compilation target only, you must also specify ! `--target=TARGET'. `configure' will attempt to create the directory ! `PREFIX/TARGET/sys-include' and copy files into it; make sure the user ! running `configure' has sufficient privilege to do so. GCC's exception handling runtime requires a special "configlette" ! module, `contrib/gthr_supp_vxw_5x.c'. Follow the instructions in that file to add the module to your kernel build. (Future versions of VxWorks will incorporate this module.) *************** x86_64-*-*, amd64-*-* *** 3914,3957 **** GCC supports the x86-64 architecture implemented by the AMD64 processor (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. On GNU/Linux the default is a bi-arch compiler which is able to generate ! both 64-bit x86-64 and 32-bit x86 code (via the '-m32' switch). x86_64-*-solaris2.1[0-9]* ========================= GCC also supports the x86-64 architecture implemented by the AMD64 ! processor ('amd64-*-*' is an alias for 'x86_64-*-*') on Solaris 10 or ! later. Unlike other systems, without special options a bi-arch compiler ! is built which generates 32-bit code by default, but can generate 64-bit ! x86-64 code with the '-m64' switch. Since GCC 4.7, there is also a ! configuration that defaults to 64-bit code, but can generate 32-bit code ! with '-m32'. To configure and build this way, you have to provide all ! support libraries like 'libgmp' as 64-bit code, configure with ! '--target=x86_64-pc-solaris2.1x' and 'CC=gcc -m64'. xtensa*-*-elf ============= ! This target is intended for embedded Xtensa systems using the 'newlib' C ! library. It uses ELF but does not support shared objects. Designed-defined instructions specified via the Tensilica Instruction Extension (TIE) language are only supported through inline assembly. The Xtensa configuration information must be specified prior to ! building GCC. The 'include/xtensa-config.h' header file contains the ! configuration information. If you created your own Xtensa configuration ! with the Xtensa Processor Generator, the downloaded files include a ! customized copy of this header file, which you can use to replace the ! default header file. xtensa*-*-linux* ================ This target is for Xtensa systems running GNU/Linux. It supports ELF shared objects and the GNU C library (glibc). It also generates ! position-independent code (PIC) regardless of whether the '-fpic' or ! '-fPIC' options are used. In other respects, this target is the same as ! the 'xtensa*-*-elf' target. Microsoft Windows ================= --- 3958,4001 ---- GCC supports the x86-64 architecture implemented by the AMD64 processor (amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. On GNU/Linux the default is a bi-arch compiler which is able to generate ! both 64-bit x86-64 and 32-bit x86 code (via the `-m32' switch). x86_64-*-solaris2.1[0-9]* ========================= GCC also supports the x86-64 architecture implemented by the AMD64 ! processor (`amd64-*-*' is an alias for `x86_64-*-*') on Solaris 10 or ! later. Unlike other systems, without special options a bi-arch ! compiler is built which generates 32-bit code by default, but can ! generate 64-bit x86-64 code with the `-m64' switch. Since GCC 4.7, ! there is also a configuration that defaults to 64-bit code, but can ! generate 32-bit code with `-m32'. To configure and build this way, you ! have to provide all support libraries like `libgmp' as 64-bit code, ! configure with `--target=x86_64-pc-solaris2.1x' and `CC=gcc -m64'. xtensa*-*-elf ============= ! This target is intended for embedded Xtensa systems using the `newlib' ! C library. It uses ELF but does not support shared objects. Designed-defined instructions specified via the Tensilica Instruction Extension (TIE) language are only supported through inline assembly. The Xtensa configuration information must be specified prior to ! building GCC. The `include/xtensa-config.h' header file contains the ! configuration information. If you created your own Xtensa ! configuration with the Xtensa Processor Generator, the downloaded files ! include a customized copy of this header file, which you can use to ! replace the default header file. xtensa*-*-linux* ================ This target is for Xtensa systems running GNU/Linux. It supports ELF shared objects and the GNU C library (glibc). It also generates ! position-independent code (PIC) regardless of whether the `-fpic' or ! `-fPIC' options are used. In other respects, this target is the same ! as the `xtensa*-*-elf' target. Microsoft Windows ================= *************** Windows XP, and Windows Vista, are suppo *** 3973,3993 **** platforms. These targets differ in which Windows subsystem they target and which C libraries are used. ! * Cygwin *-*-cygwin: Cygwin provides a user-space Linux API emulation ! layer in the Win32 subsystem. * Interix *-*-interix: The Interix subsystem provides native support for POSIX. * MinGW *-*-mingw32: MinGW is a native GCC port for the Win32 subsystem that provides a subset of POSIX. ! * MKS i386-pc-mks: NuTCracker from MKS. See ! for more information. Intel 64-bit versions --------------------- GCC contains support for x86-64 using the mingw-w64 runtime library, ! available from . This library should ! be used with the target triple x86_64-pc-mingw32. Presently Windows for Itanium is not supported. --- 4017,4040 ---- platforms. These targets differ in which Windows subsystem they target and which C libraries are used. ! * Cygwin *-*-cygwin: Cygwin provides a user-space Linux API ! emulation layer in the Win32 subsystem. ! * Interix *-*-interix: The Interix subsystem provides native support for POSIX. + * MinGW *-*-mingw32: MinGW is a native GCC port for the Win32 subsystem that provides a subset of POSIX. ! ! * MKS i386-pc-mks: NuTCracker from MKS. See ! `http://www.mkssoftware.com/' for more information. Intel 64-bit versions --------------------- GCC contains support for x86-64 using the mingw-w64 runtime library, ! available from `http://mingw-w64.sourceforge.net/'. This library ! should be used with the target triple x86_64-pc-mingw32. Presently Windows for Itanium is not supported. *************** support the Interix subsystem. See abov *** 4009,4015 **** used. PW32 (i386-pc-pw32) support was never completed, and the project ! seems to be inactive. See for more information. UWIN support has been removed due to a lack of maintenance. --- 4056,4062 ---- used. PW32 (i386-pc-pw32) support was never completed, and the project ! seems to be inactive. See `http://pw32.sourceforge.net/' for more information. UWIN support has been removed due to a lack of maintenance. *************** version 2.20 or above if building your o *** 4032,4038 **** =========== The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), ! and Subsystem for UNIX-based Applications (SUA). Applications compiled with this target run in the Interix subsystem, which is separate from the Win32 subsystem. This target was last known to work in GCC 3.3. --- 4079,4085 ---- =========== The Interix target is used by OpenNT, Interix, Services For UNIX (SFU), ! and Subsystem for UNIX-based Applications (SUA). Applications compiled with this target run in the Interix subsystem, which is separate from the Win32 subsystem. This target was last known to work in GCC 3.3. *************** the Win32 subsystem. This target was la *** 4041,4047 **** GCC will build with and support only MinGW runtime 3.12 and later. Earlier versions of headers are incompatible with the new default ! semantics of 'extern inline' in '-std=c99' and '-std=gnu99' modes. Older systems ============= --- 4088,4094 ---- GCC will build with and support only MinGW runtime 3.12 and later. Earlier versions of headers are incompatible with the new default ! semantics of `extern inline' in `-std=c99' and `-std=gnu99' modes. Older systems ============= *************** and may suffer from bitrot. *** 4053,4059 **** Starting with GCC 3.1, each release has a list of "obsoleted" systems. Support for these systems is still present in that release, ! but 'configure' will fail unless the '--enable-obsolete' option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC. --- 4100,4106 ---- Starting with GCC 3.1, each release has a list of "obsoleted" systems. Support for these systems is still present in that release, ! but `configure' will fail unless the `--enable-obsolete' option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC. *************** bring GCC up on such a system, if still *** 4064,4096 **** require first installing an old version of GCC which did work on that system, and using it to compile a more recent GCC, to avoid bugs in the vendor compiler. Old releases of GCC 1 and GCC 2 are available in the ! 'old-releases' directory on the GCC mirror sites. Header bugs may ! generally be avoided using 'fixincludes', but bugs or deficiencies in libraries and the operating system may still cause problems. Support for older systems as targets for cross-compilation is less problematic than support for them as hosts for GCC; if an enthusiast wishes to make such a target work again (including resurrecting any of ! the targets that never worked with GCC 2, starting from the last version ! before they were removed), patches following the usual requirements ! would be likely to be accepted, since they should not affect the support ! for more modern targets. For some systems, old versions of GNU binutils may also be useful, ! and are available from 'pub/binutils/old-releases' on sourceware.org mirror sites. Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems ! (which may no longer be applicable to current GCC) is to be found in the ! GCC texinfo manual. all ELF targets (SVR4, Solaris 2, etc.) ======================================= C++ support is significantly better on ELF targets if you use the GNU ! linker; duplicate copies of inlines, vtables and template instantiations ! will be discarded automatically.  File: gccinstall.info, Node: Old, Next: GNU Free Documentation License, Prev: Specific, Up: Top --- 4111,4143 ---- require first installing an old version of GCC which did work on that system, and using it to compile a more recent GCC, to avoid bugs in the vendor compiler. Old releases of GCC 1 and GCC 2 are available in the ! `old-releases' directory on the GCC mirror sites. Header bugs may ! generally be avoided using `fixincludes', but bugs or deficiencies in libraries and the operating system may still cause problems. Support for older systems as targets for cross-compilation is less problematic than support for them as hosts for GCC; if an enthusiast wishes to make such a target work again (including resurrecting any of ! the targets that never worked with GCC 2, starting from the last ! version before they were removed), patches following the usual ! requirements would be likely to be accepted, since they should not ! affect the support for more modern targets. For some systems, old versions of GNU binutils may also be useful, ! and are available from `pub/binutils/old-releases' on sourceware.org mirror sites. Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems ! (which may no longer be applicable to current GCC) is to be found in ! the GCC texinfo manual. all ELF targets (SVR4, Solaris 2, etc.) ======================================= C++ support is significantly better on ELF targets if you use the GNU ! linker; duplicate copies of inlines, vtables and template ! instantiations will be discarded automatically.  File: gccinstall.info, Node: Old, Next: GNU Free Documentation License, Prev: Specific, Up: Top *************** File: gccinstall.info, Node: Old, Next *** 4098,4104 **** 10 Old installation documentation ********************************* ! Note most of this information is out of date and superseded by the previous chapters of this manual. It is provided for historical reference only, because of a lack of volunteers to merge it into the main manual. --- 4145,4151 ---- 10 Old installation documentation ********************************* ! Note most of this information is out of date and superseded by the previous chapters of this manual. It is provided for historical reference only, because of a lack of volunteers to merge it into the main manual. *************** main manual. *** 4112,4125 **** 1. If you have chosen a configuration for GCC which requires other GNU tools (such as GAS or the GNU linker) instead of the standard system tools, install the required tools in the build directory ! under the names 'as', 'ld' or whatever is appropriate. Alternatively, you can do subsequent compilation using a value of ! the 'PATH' environment variable such that the necessary GNU tools come before the standard system tools. 2. Specify the host, build and target machine configurations. You do ! this when you run the 'configure' script. The "build" machine is the system which you are using, the "host" machine is the system where you want to run the resulting compiler --- 4159,4172 ---- 1. If you have chosen a configuration for GCC which requires other GNU tools (such as GAS or the GNU linker) instead of the standard system tools, install the required tools in the build directory ! under the names `as', `ld' or whatever is appropriate. Alternatively, you can do subsequent compilation using a value of ! the `PATH' environment variable such that the necessary GNU tools come before the standard system tools. 2. Specify the host, build and target machine configurations. You do ! this when you run the `configure' script. The "build" machine is the system which you are using, the "host" machine is the system where you want to run the resulting compiler *************** main manual. *** 4128,4141 **** If you are building a compiler to produce code for the machine it runs on (a native compiler), you normally do not need to specify ! any operands to 'configure'; it will try to guess the type of machine you are on and use that as the build, host and target machines. So you don't need to specify a configuration when ! building a native compiler unless 'configure' cannot figure out what your configuration is or guesses wrong. In those cases, specify the build machine's "configuration name" ! with the '--host' option; the host and target will default to be the same as the host machine. Here is an example: --- 4175,4188 ---- If you are building a compiler to produce code for the machine it runs on (a native compiler), you normally do not need to specify ! any operands to `configure'; it will try to guess the type of machine you are on and use that as the build, host and target machines. So you don't need to specify a configuration when ! building a native compiler unless `configure' cannot figure out what your configuration is or guesses wrong. In those cases, specify the build machine's "configuration name" ! with the `--host' option; the host and target will default to be the same as the host machine. Here is an example: *************** main manual. *** 4146,4196 **** abbreviated. A canonical configuration name has three parts, separated by ! dashes. It looks like this: 'CPU-COMPANY-SYSTEM'. (The three ! parts may themselves contain dashes; 'configure' can figure out which dashes serve which purpose.) For example, ! 'm68k-sun-sunos4.1' specifies a Sun 3. You can also replace parts of the configuration by nicknames or ! aliases. For example, 'sun3' stands for 'm68k-sun', so ! 'sun3-sunos4.1' is another way to specify a Sun 3. ! You can specify a version number after any of the system types, and ! some of the CPU types. In most cases, the version is irrelevant, ! and will be ignored. So you might as well specify the version if ! you know it. See *note Configurations::, for a list of supported configuration names and notes on many of the configurations. You should check the notes in that section before proceeding any further with the installation of GCC.  File: gccinstall.info, Node: Configurations, Up: Old 10.1 Configurations Supported by GCC ==================================== ! Here are the possible CPU types: 1750a, a29k, alpha, arm, avr, cN, clipper, dsp16xx, elxsi, fr30, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64, ! mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, ! rs6000, sh, sparc, sparclite, sparc64, v850, vax, we32k. Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names. acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent, ! convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ! ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron, plexus, ! sequent, sgi, sony, sun, tti, unicom, wrs. The company name is meaningful only to disambiguate when the rest of ! the information supplied is insufficient. You can omit it, writing just ! 'CPU-SYSTEM', if it is not needed. For example, 'vax-ultrix4.2' is ! equivalent to 'vax-dec-ultrix4.2'. Here is a list of system types: --- 4193,4244 ---- abbreviated. A canonical configuration name has three parts, separated by ! dashes. It looks like this: `CPU-COMPANY-SYSTEM'. (The three ! parts may themselves contain dashes; `configure' can figure out which dashes serve which purpose.) For example, ! `m68k-sun-sunos4.1' specifies a Sun 3. You can also replace parts of the configuration by nicknames or ! aliases. For example, `sun3' stands for `m68k-sun', so ! `sun3-sunos4.1' is another way to specify a Sun 3. ! You can specify a version number after any of the system types, ! and some of the CPU types. In most cases, the version is ! irrelevant, and will be ignored. So you might as well specify the ! version if you know it. See *note Configurations::, for a list of supported configuration names and notes on many of the configurations. You should check the notes in that section before proceeding any further with the installation of GCC. +  File: gccinstall.info, Node: Configurations, Up: Old 10.1 Configurations Supported by GCC ==================================== ! Here are the possible CPU types: 1750a, a29k, alpha, arm, avr, cN, clipper, dsp16xx, elxsi, fr30, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64, ! mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, ! romp, rs6000, sh, sparc, sparclite, sparc64, v850, vax, we32k. Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names. acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent, ! convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, ! hp, ibm, intergraph, isi, mips, motorola, ncr, next, ns, omron, ! plexus, sequent, sgi, sony, sun, tti, unicom, wrs. The company name is meaningful only to disambiguate when the rest of ! the information supplied is insufficient. You can omit it, writing ! just `CPU-SYSTEM', if it is not needed. For example, `vax-ultrix4.2' ! is equivalent to `vax-dec-ultrix4.2'. Here is a list of system types: *************** equivalent to 'vax-dec-ultrix4.2'. *** 4202,4230 **** sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, vxworks, winnt, xenix. ! You can omit the system type; then 'configure' guesses the operating system from the CPU and company. You can add a version number to the system type; this may or may not ! make a difference. For example, you can write 'bsd4.3' or 'bsd4.4' to distinguish versions of BSD. In practice, the version number is most ! needed for 'sysv3' and 'sysv4', which are often treated differently. ! 'linux-gnu' is the canonical name for the GNU/Linux target; however ! GCC will also accept 'linux'. The version of the kernel in use is not ! relevant on these systems. A suffix such as 'libc1' or 'aout' distinguishes major versions of the C library; all of the suffixed versions are obsolete. ! If you specify an impossible combination such as 'i860-dg-vms', then ! you may get an error message from 'configure', or it may ignore part of ! the information and do the best it can with the rest. 'configure' always prints the canonical name for the alternative that it used. GCC does not support all possible alternatives. Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the ! machine name 'sun3', mentioned above, is an alias for 'm68k-sun'. Sometimes we accept a company name as a machine name, when the name is popularly used for a particular machine. Here is a table of the known machine names: --- 4250,4278 ---- sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta, vxworks, winnt, xenix. ! You can omit the system type; then `configure' guesses the operating system from the CPU and company. You can add a version number to the system type; this may or may not ! make a difference. For example, you can write `bsd4.3' or `bsd4.4' to distinguish versions of BSD. In practice, the version number is most ! needed for `sysv3' and `sysv4', which are often treated differently. ! `linux-gnu' is the canonical name for the GNU/Linux target; however ! GCC will also accept `linux'. The version of the kernel in use is not ! relevant on these systems. A suffix such as `libc1' or `aout' distinguishes major versions of the C library; all of the suffixed versions are obsolete. ! If you specify an impossible combination such as `i860-dg-vms', then ! you may get an error message from `configure', or it may ignore part of ! the information and do the best it can with the rest. `configure' always prints the canonical name for the alternative that it used. GCC does not support all possible alternatives. Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the ! machine name `sun3', mentioned above, is an alias for `m68k-sun'. Sometimes we accept a company name as a machine name, when the name is popularly used for a particular machine. Here is a table of the known machine names: *************** machine names: *** 4234,4241 **** encore, fx2800, gmicro, hp7NN, hp8NN, hp9k2NN, hp9k3NN, hp9k7NN, hp9k8NN, iris4d, iris, isi68, m3230, magnum, merlin, miniframe, mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc, ! powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3, sun4, ! symmetry, tower-32, tower. Remember that a machine name specifies both the cpu type and the company name. --- 4282,4289 ---- encore, fx2800, gmicro, hp7NN, hp8NN, hp9k2NN, hp9k3NN, hp9k7NN, hp9k8NN, iris4d, iris, isi68, m3230, magnum, merlin, miniframe, mmax, news-3600, news800, news, next, pbd, pc532, pmax, powerpc, ! powerpcle, ps2, risc-news, rtpc, sun2, sun386i, sun386, sun3, ! sun4, symmetry, tower-32, tower. Remember that a machine name specifies both the cpu type and the company name. *************** GNU Free Documentation License *** 4249,4255 **** Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 4297,4303 ---- Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU Free Documentation License *** 4274,4294 **** free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. We ! recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it can ! be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You accept ! the license if you copy, modify or distribute the work in a way ! requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with --- 4322,4342 ---- free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. ! We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it ! can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You ! accept the license if you copy, modify or distribute the work in a ! way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with *************** GNU Free Documentation License *** 4306,4317 **** regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in the ! notice that says that the Document is released under this License. ! If a section does not fit the above definition of Secondary then it ! is not allowed to be designated as Invariant. The Document may ! contain zero Invariant Sections. If the Document does not identify ! any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice --- 4354,4365 ---- regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in ! the notice that says that the Document is released under this ! License. If a section does not fit the above definition of ! Secondary then it is not allowed to be designated as Invariant. ! The Document may contain zero Invariant Sections. If the Document ! does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice *************** GNU Free Documentation License *** 4322,4348 **** A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images composed ! of pixels) generic paint programs or (for drawings) some widely ! available drawing editor, and that is suitable for input to text ! formatters or for automatic translation to a variety of formats ! suitable for input to text formatters. A copy made in an otherwise ! Transparent file format whose markup, or absence of markup, has ! been arranged to thwart or discourage subsequent modification by ! readers is not Transparent. An image format is not Transparent if ! used for any substantial amount of text. A copy that is not ! "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and standard-conforming ! simple HTML, PostScript or PDF designed for human modification. ! Examples of transparent image formats include PNG, XCF and JPG. ! Opaque formats include proprietary formats that can be read and ! edited only by proprietary word processors, SGML or XML for which ! the DTD and/or processing tools are not generally available, and ! the machine-generated HTML, PostScript or PDF produced by some word ! processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the --- 4370,4396 ---- A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images ! composed of pixels) generic paint programs or (for drawings) some ! widely available drawing editor, and that is suitable for input to ! text formatters or for automatic translation to a variety of ! formats suitable for input to text formatters. A copy made in an ! otherwise Transparent file format whose markup, or absence of ! markup, has been arranged to thwart or discourage subsequent ! modification by readers is not Transparent. An image format is ! not Transparent if used for any substantial amount of text. A ! copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and ! standard-conforming simple HTML, PostScript or PDF designed for ! human modification. Examples of transparent image formats include ! PNG, XCF and JPG. Opaque formats include proprietary formats that ! can be read and edited only by proprietary word processors, SGML or ! XML for which the DTD and/or processing tools are not generally ! available, and the machine-generated HTML, PostScript or PDF ! produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the *************** GNU Free Documentation License *** 4380,4387 **** may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow the ! conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. --- 4428,4435 ---- may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow ! the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. *************** GNU Free Documentation License *** 4395,4405 **** these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the title ! equally prominent and visible. You may add other material on the ! covers in addition. Copying with changes limited to the covers, as ! long as they preserve the title of the Document and satisfy these ! conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit --- 4443,4454 ---- these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the ! title equally prominent and visible. You may add other material ! on the covers in addition. Copying with changes limited to the ! covers, as long as they preserve the title of the Document and ! satisfy these conditions, can be treated as verbatim copying in ! other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit *************** GNU Free Documentation License *** 4407,4445 **** adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a machine-readable ! Transparent copy along with each Opaque copy, or state in or with ! each Opaque copy a computer-network location from which the general ! network-using public has access to download using public-standard ! network protocols a complete Transparent copy of the Document, free ! of added material. If you use the latter option, you must take ! reasonably prudent steps, when you begin distribution of Opaque ! copies in quantity, to ensure that this Transparent copy will ! remain thus accessible at the stated location until at least one ! year after the last time you distribute an Opaque copy (directly or ! through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of copies, ! to give them a chance to provide you with an updated version of the ! Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with the ! Modified Version filling the role of the Document, thus licensing ! distribution and modification of the Modified Version to whoever ! possesses a copy of it. In addition, you must do these things in ! the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of previous ! versions (which should, if there were any, be listed in the ! History section of the Document). You may use the same title ! as a previous version if the original publisher of that ! version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in --- 4456,4495 ---- adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a ! machine-readable Transparent copy along with each Opaque copy, or ! state in or with each Opaque copy a computer-network location from ! which the general network-using public has access to download ! using public-standard network protocols a complete Transparent ! copy of the Document, free of added material. If you use the ! latter option, you must take reasonably prudent steps, when you ! begin distribution of Opaque copies in quantity, to ensure that ! this Transparent copy will remain thus accessible at the stated ! location until at least one year after the last time you ! distribute an Opaque copy (directly or through your agents or ! retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of ! copies, to give them a chance to provide you with an updated ! version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with ! the Modified Version filling the role of the Document, thus ! licensing distribution and modification of the Modified Version to ! whoever possesses a copy of it. In addition, you must do these ! things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of ! previous versions (which should, if there were any, be listed ! in the History section of the Document). You may use the ! same title as a previous version if the original publisher of ! that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in *************** GNU Free Documentation License *** 4469,4498 **** I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on the ! Title Page. If there is no section Entitled "History" in the ! Document, create one stating the title, year, authors, and ! publisher of the Document as given on its Title Page, then add ! an item describing the Modified Version as stated in the ! previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in the ! "History" section. You may omit a network location for a work ! that was published at least four years before the Document ! itself, or if the original publisher of the version it refers ! to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the section ! all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, unaltered ! in their text and in their titles. Section numbers or the ! equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. --- 4519,4549 ---- I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on ! the Title Page. If there is no section Entitled "History" in ! the Document, create one stating the title, year, authors, ! and publisher of the Document as given on its Title Page, ! then add an item describing the Modified Version as stated in ! the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in ! the "History" section. You may omit a network location for a ! work that was published at least four years before the ! Document itself, or if the original publisher of the version ! it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the ! section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, ! unaltered in their text and in their titles. Section numbers ! or the equivalent are not considered part of the section ! titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. *************** GNU Free Documentation License *** 4505,4515 **** If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option designate ! some or all of these sections as invariant. To do this, add their ! titles to the list of Invariant Sections in the Modified Version's ! license notice. These titles must be distinct from any other ! section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various --- 4556,4566 ---- If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option ! designate some or all of these sections as invariant. To do this, ! add their titles to the list of Invariant Sections in the Modified ! Version's license notice. These titles must be distinct from any ! other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various *************** GNU Free Documentation License *** 4518,4532 **** definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end of ! the list of Cover Texts in the Modified Version. Only one passage ! of Front-Cover Text and one of Back-Cover Text may be added by (or ! through arrangements made by) any one entity. If the Document ! already includes a cover text for the same cover, previously added ! by you or by arrangement made by the same entity you are acting on ! behalf of, you may not add another; but you may replace the old ! one, on explicit permission from the previous publisher that added ! the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to --- 4569,4583 ---- definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end ! of the list of Cover Texts in the Modified Version. Only one ! passage of Front-Cover Text and one of Back-Cover Text may be ! added by (or through arrangements made by) any one entity. If the ! Document already includes a cover text for the same cover, ! previously added by you or by arrangement made by the same entity ! you are acting on behalf of, you may not add another; but you may ! replace the old one, on explicit permission from the previous ! publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to *************** GNU Free Documentation License *** 4536,4543 **** You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination all ! of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. --- 4587,4594 ---- You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination ! all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. *************** GNU Free Documentation License *** 4564,4583 **** documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the documents ! in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow this ! License in all other respects regarding verbatim copying of that ! document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of a ! storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this --- 4615,4634 ---- documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the ! documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow ! this License in all other respects regarding verbatim copying of ! that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of ! a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this *************** GNU Free Documentation License *** 4622,4629 **** However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 4673,4680 ---- However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** GNU Free Documentation License *** 4635,4667 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, receipt of a copy of some or all of the ! same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! . Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If the ! Document does not specify a version number of this License, you may ! choose any version ever published (not as a draft) by the Free ! Software Foundation. If the Document specifies that a proxy can ! decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also --- 4686,4718 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, receipt of a copy of some or all of ! the same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! `http://www.gnu.org/copyleft/'. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If ! the Document does not specify a version number of this License, ! you may choose any version ever published (not as a draft) by the ! Free Software Foundation. If the Document specifies that a proxy ! can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also *************** GNU Free Documentation License *** 4691,4696 **** --- 4742,4748 ---- site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. + ADDENDUM: How to use this License for your documents ==================================================== *************** notices just after the title page: *** 4707,4713 **** Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts --- 4759,4765 ---- Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts *************** combination of the three, merge those tw *** 4718,4726 **** situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of free ! software license, such as the GNU General Public License, to permit ! their use in free software.  File: gccinstall.info, Node: Concept Index, Prev: GNU Free Documentation License, Up: Top --- 4770,4778 ---- situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of ! free software license, such as the GNU General Public License, to ! permit their use in free software.  File: gccinstall.info, Node: Concept Index, Prev: GNU Free Documentation License, Up: Top *************** Concept Index *** 4732,4738 **** * Menu: * Binaries: Binaries. (line 6) ! * build_configargs: Configuration. (line 1458) * Configuration: Configuration. (line 6) * configurations supported by GCC: Configurations. (line 6) * Downloading GCC: Downloading the source. --- 4784,4790 ---- * Menu: * Binaries: Binaries. (line 6) ! * build_configargs: Configuration. (line 1511) * Configuration: Configuration. (line 6) * configurations supported by GCC: Configurations. (line 6) * Downloading GCC: Downloading the source. *************** Concept Index *** 4742,4748 **** * FDL, GNU Free Documentation License: GNU Free Documentation License. (line 6) * Host specific installation: Specific. (line 6) ! * host_configargs: Configuration. (line 1462) * Installing GCC: Binaries: Binaries. (line 6) * Installing GCC: Building: Building. (line 6) * Installing GCC: Configuration: Configuration. (line 6) --- 4794,4800 ---- * FDL, GNU Free Documentation License: GNU Free Documentation License. (line 6) * Host specific installation: Specific. (line 6) ! * host_configargs: Configuration. (line 1515) * Installing GCC: Binaries: Binaries. (line 6) * Installing GCC: Building: Building. (line 6) * Installing GCC: Configuration: Configuration. (line 6) *************** Concept Index *** 4752,4863 **** * Specific installation notes: Specific. (line 6) * Target specific installation: Specific. (line 6) * Target specific installation notes: Specific. (line 6) ! * target_configargs: Configuration. (line 1466) * Testing: Testing. (line 6) * Testsuite: Testing. (line 6)  Tag Table: ! Node: Top1696 ! Node: Installing GCC2254 ! Node: Prerequisites3888 ! Node: Downloading the source15018 ! Node: Configuration16692 ! Ref: with-gnu-as32152 ! Ref: with-as33047 ! Ref: with-gnu-ld34460 ! Ref: WithAixSoname52359 ! Ref: AixLdCommand53020 ! Node: Building93396 ! Node: Testing109288 ! Node: Final install117150 ! Node: Binaries122461 ! Node: Specific123515 ! Ref: aarch64-x-x124022 ! Ref: alpha-x-x125454 ! Ref: alpha-dec-osf51125943 ! Ref: amd64-x-solaris210126468 ! Ref: arc-x-elf32126571 ! Ref: arc-linux-uclibc126747 ! Ref: arm-x-eabi126888 ! Ref: avr127305 ! Ref: bfin127944 ! Ref: cr16128185 ! Ref: cris128601 ! Ref: dos129416 ! Ref: epiphany-x-elf129739 ! Ref: x-x-freebsd129844 ! Ref: ft32-x-elf131680 ! Ref: h8300-hms131778 ! Ref: hppa-hp-hpux132130 ! Ref: hppa-hp-hpux10134502 ! Ref: hppa-hp-hpux11134915 ! Ref: x-x-linux-gnu140574 ! Ref: ix86-x-linux140767 ! Ref: ix86-x-solaris210141080 ! Ref: ia64-x-linux142539 ! Ref: ia64-x-hpux143309 ! Ref: x-ibm-aix143864 ! Ref: TransferAixShobj147526 ! Ref: iq2000-x-elf151336 ! Ref: lm32-x-elf151476 ! Ref: lm32-x-uclinux151580 ! Ref: m32c-x-elf151708 ! Ref: m32r-x-elf151810 ! Ref: m68k-x-x151912 ! Ref: m68k-x-uclinux152950 ! Ref: mep-x-elf153195 ! Ref: microblaze-x-elf153305 ! Ref: mips-x-x153424 ! Ref: mips-sgi-irix5155818 ! Ref: mips-sgi-irix6155898 ! Ref: moxie-x-elf156085 ! Ref: msp430-x-elf156132 ! Ref: nds32le-x-elf156235 ! Ref: nds32be-x-elf156307 ! Ref: nvptx-x-none156376 ! Ref: powerpc-x-x156903 ! Ref: powerpc-x-darwin157108 ! Ref: powerpc-x-elf157602 ! Ref: powerpc-x-linux-gnu157687 ! Ref: powerpc-x-netbsd157782 ! Ref: powerpc-x-eabisim157870 ! Ref: powerpc-x-eabi157996 ! Ref: powerpcle-x-elf158072 ! Ref: powerpcle-x-eabisim158164 ! Ref: powerpcle-x-eabi158297 ! Ref: rl78-x-elf158380 ! Ref: rx-x-elf158486 ! Ref: s390-x-linux158685 ! Ref: s390x-x-linux158757 ! Ref: s390x-ibm-tpf158844 ! Ref: x-x-solaris2158975 ! Ref: sparc-x-x162991 ! Ref: sparc-sun-solaris2163493 ! Ref: sparc-sun-solaris210164632 ! Ref: sparc-x-linux165007 ! Ref: sparc64-x-solaris2165232 ! Ref: sparcv9-x-solaris2165565 ! Ref: c6x-x-x165652 ! Ref: tilegx-*-linux165744 ! Ref: tilegxbe-*-linux165886 ! Ref: tilepro-*-linux166029 ! Ref: visium-x-elf166150 ! Ref: x-x-vxworks166258 ! Ref: x86-64-x-x167781 ! Ref: x86-64-x-solaris210168109 ! Ref: xtensa-x-elf168773 ! Ref: xtensa-x-linux169444 ! Ref: windows169785 ! Ref: x-x-cygwin171718 ! Ref: x-x-interix172271 ! Ref: x-x-mingw32172579 ! Ref: older172805 ! Ref: elf174922 ! Node: Old175180 ! Node: Configurations178313 ! Node: GNU Free Documentation License181851 ! Node: Concept Index206979  End Tag Table --- 4804,4915 ---- * Specific installation notes: Specific. (line 6) * Target specific installation: Specific. (line 6) * Target specific installation notes: Specific. (line 6) ! * target_configargs: Configuration. (line 1519) * Testing: Testing. (line 6) * Testsuite: Testing. (line 6)  Tag Table: ! Node: Top1747 ! Node: Installing GCC2305 ! Node: Prerequisites3942 ! Node: Downloading the source15061 ! Node: Configuration16739 ! Ref: with-gnu-as32190 ! Ref: with-as33088 ! Ref: with-gnu-ld34501 ! Ref: WithAixSoname52653 ! Ref: AixLdCommand53314 ! Node: Building93478 ! Node: Testing109387 ! Node: Final install117259 ! Node: Binaries122573 ! Node: Specific123631 ! Ref: aarch64-x-x124141 ! Ref: alpha-x-x125573 ! Ref: alpha-dec-osf51126062 ! Ref: amd64-x-solaris210126587 ! Ref: arc-x-elf32126690 ! Ref: arc-linux-uclibc126866 ! Ref: arm-x-eabi127007 ! Ref: avr127424 ! Ref: bfin128064 ! Ref: cr16128306 ! Ref: cris128721 ! Ref: dos129537 ! Ref: epiphany-x-elf129860 ! Ref: x-x-freebsd129965 ! Ref: ft32-x-elf131802 ! Ref: h8300-hms131900 ! Ref: hppa-hp-hpux132252 ! Ref: hppa-hp-hpux10134623 ! Ref: hppa-hp-hpux11135036 ! Ref: x-x-linux-gnu140695 ! Ref: ix86-x-linux140888 ! Ref: ix86-x-solaris210141201 ! Ref: ia64-x-linux142660 ! Ref: ia64-x-hpux143430 ! Ref: x-ibm-aix143985 ! Ref: TransferAixShobj147647 ! Ref: iq2000-x-elf151458 ! Ref: lm32-x-elf151598 ! Ref: lm32-x-uclinux151702 ! Ref: m32c-x-elf151830 ! Ref: m32r-x-elf151932 ! Ref: m68k-x-x152034 ! Ref: m68k-x-uclinux153072 ! Ref: mep-x-elf153318 ! Ref: microblaze-x-elf153428 ! Ref: mips-x-x153547 ! Ref: mips-sgi-irix5155943 ! Ref: mips-sgi-irix6156023 ! Ref: moxie-x-elf156210 ! Ref: msp430-x-elf156257 ! Ref: nds32le-x-elf156360 ! Ref: nds32be-x-elf156432 ! Ref: nvptx-x-none156501 ! Ref: powerpc-x-x157028 ! Ref: powerpc-x-darwin157233 ! Ref: powerpc-x-elf157727 ! Ref: powerpc-x-linux-gnu157812 ! Ref: powerpc-x-netbsd157907 ! Ref: powerpc-x-eabisim157995 ! Ref: powerpc-x-eabi158121 ! Ref: powerpcle-x-elf158197 ! Ref: powerpcle-x-eabisim158289 ! Ref: powerpcle-x-eabi158422 ! Ref: rl78-x-elf158505 ! Ref: rx-x-elf158611 ! Ref: s390-x-linux158810 ! Ref: s390x-x-linux158882 ! Ref: s390x-ibm-tpf158969 ! Ref: x-x-solaris2159100 ! Ref: sparc-x-x163117 ! Ref: sparc-sun-solaris2163619 ! Ref: sparc-sun-solaris210164759 ! Ref: sparc-x-linux165135 ! Ref: sparc64-x-solaris2165360 ! Ref: sparcv9-x-solaris2165693 ! Ref: c6x-x-x165780 ! Ref: tilegx-*-linux165871 ! Ref: tilegxbe-*-linux166013 ! Ref: tilepro-*-linux166156 ! Ref: visium-x-elf166277 ! Ref: x-x-vxworks166385 ! Ref: x86-64-x-x167907 ! Ref: x86-64-x-solaris210168235 ! Ref: xtensa-x-elf168899 ! Ref: xtensa-x-linux169570 ! Ref: windows169911 ! Ref: x-x-cygwin171848 ! Ref: x-x-interix172401 ! Ref: x-x-mingw32172710 ! Ref: older172936 ! Ref: elf175053 ! Node: Old175311 ! Node: Configurations178448 ! Node: GNU Free Documentation License181989 ! Node: Concept Index207136  End Tag Table diff -Nrcpad gcc-6.3.0/gcc/doc/gccint.info gcc-6.4.0/gcc/doc/gccint.info *** gcc-6.3.0/gcc/doc/gccint.info Wed Dec 21 09:34:03 2016 --- gcc-6.4.0/gcc/doc/gccint.info Tue Jul 4 09:27:46 2017 *************** *** 1,6 **** ! This is gccint.info, produced by makeinfo version 6.1 from gccint.texi. ! Copyright (C) 1988-2016 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 --- 1,7 ---- ! This is doc/gccint.info, produced by makeinfo version 4.13 from ! /space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/doc/gccint.texi. ! Copyright (C) 1988-2017 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 *************** Free Documentation License". *** 16,32 **** (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU software. ! Copies published by the Free Software Foundation raise funds for GNU ! development. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * gccint: (gccint). Internals of the GNU Compiler Collection. END-INFO-DIR-ENTRY - This file documents the internals of the GNU compilers. ! Copyright (C) 1988-2016 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 --- 17,33 ---- (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. ! INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * gccint: (gccint). Internals of the GNU Compiler Collection. END-INFO-DIR-ENTRY This file documents the internals of the GNU compilers. ! Copyright (C) 1988-2017 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 *************** Free Documentation License". *** 42,50 **** (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU software. ! Copies published by the Free Software Foundation raise funds for GNU ! development.  File: gccint.info, Node: Top, Next: Contributing, Up: (DIR) --- 43,52 ---- (b) The FSF's Back-Cover Text is: ! You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. !  File: gccint.info, Node: Top, Next: Contributing, Up: (DIR) *************** Introduction *** 54,62 **** This manual documents the internals of the GNU compilers, including how to port them to new targets and some information about how to write ! front ends for new languages. It corresponds to the compilers (GCC) ! version 6.3.0. The use of the GNU compilers is documented in a separate ! manual. *Note Introduction: (gcc)Top. This manual is mainly a reference manual rather than a tutorial. It discusses how to contribute to GCC (*note Contributing::), the --- 56,64 ---- This manual documents the internals of the GNU compilers, including how to port them to new targets and some information about how to write ! front ends for new languages. It corresponds to the compilers ! (GCC) version 6.4.0. The use of the GNU compilers is documented in a ! separate manual. *Note Introduction: (gcc)Top. This manual is mainly a reference manual rather than a tutorial. It discusses how to contribute to GCC (*note Contributing::), the *************** GCC front ends, and how support for a ta *** 69,75 **** GCC. Additional tutorial information is linked to from ! . * Menu: --- 71,77 ---- GCC. Additional tutorial information is linked to from ! `http://gcc.gnu.org/readings.html'. * Menu: *************** GCC. *** 90,98 **** * Loop Analysis and Representation:: Analysis and representation of loops * Machine Desc:: How to write machine description instruction patterns. * Target Macros:: How to write the machine description C macros and functions. ! * Host Config:: Writing the 'xm-MACHINE.h' file. ! * Fragments:: Writing the 't-TARGET' and 'x-HOST' files. ! * Collect2:: How 'collect2' works; how it finds 'ld'. * Header Dirs:: Understanding the standard header file directories. * Type Information:: GCC's memory management; generating type information. * Plugins:: Extending the compiler with plugins. --- 92,100 ---- * Loop Analysis and Representation:: Analysis and representation of loops * Machine Desc:: How to write machine description instruction patterns. * Target Macros:: How to write the machine description C macros and functions. ! * Host Config:: Writing the `xm-MACHINE.h' file. ! * Fragments:: Writing the `t-TARGET' and `x-HOST' files. ! * Collect2:: How `collect2' works; how it finds `ld'. * Header Dirs:: Understanding the standard header file directories. * Type Information:: GCC's memory management; generating type information. * Plugins:: Extending the compiler with plugins. *************** GCC. *** 111,135 **** * Concept Index:: Index of concepts and symbol names.  ! File: gccint.info, Node: Contributing, Next: Portability, Up: Top 1 Contributing to GCC Development ********************************* If you would like to help pretest GCC releases to assure they work well, current development sources are available by SVN (see ! ). Source and binary snapshots are also ! available for FTP; see . If you would like to work on improvements to GCC, please read the advice at these URLs: ! ! for information on how to make useful contributions and avoid duplication of effort. Suggested projects are listed at ! .  File: gccint.info, Node: Portability, Next: Interface, Prev: Contributing, Up: Top --- 113,137 ---- * Concept Index:: Index of concepts and symbol names.  ! File: gccint.info, Node: Contributing, Next: Portability, Prev: Top, Up: Top 1 Contributing to GCC Development ********************************* If you would like to help pretest GCC releases to assure they work well, current development sources are available by SVN (see ! `http://gcc.gnu.org/svn.html'). Source and binary snapshots are also ! available for FTP; see `http://gcc.gnu.org/snapshots.html'. If you would like to work on improvements to GCC, please read the advice at these URLs: ! `http://gcc.gnu.org/contribute.html' ! `http://gcc.gnu.org/contributewhy.html' for information on how to make useful contributions and avoid duplication of effort. Suggested projects are listed at ! `http://gcc.gnu.org/projects/'.  File: gccint.info, Node: Portability, Next: Interface, Prev: Contributing, Up: Top *************** File: gccint.info, Node: Portability, *** 137,155 **** 2 GCC and Portability ********************* ! GCC itself aims to be portable to any machine where 'int' is at least a 32-bit type. It aims to target machines with a flat (non-segmented) byte addressed data address space (the code address space can be ! separate). Target ABIs may have 8, 16, 32 or 64-bit 'int' type. 'char' can be wider than 8 bits. GCC gets most of the information about the target machine from a machine description which gives an algebraic formula for each of the machine's instructions. This is a very clean way to describe the target. But when the compiler needs information that is difficult to ! express in this fashion, ad-hoc parameters have been defined for machine ! descriptions. The purpose of portability is to reduce the total work ! needed on the compiler; it was not of interest for its own sake. GCC does not contain machine dependent code, but it does contain code that depends on machine parameters such as endianness (whether the most --- 139,158 ---- 2 GCC and Portability ********************* ! GCC itself aims to be portable to any machine where `int' is at least a 32-bit type. It aims to target machines with a flat (non-segmented) byte addressed data address space (the code address space can be ! separate). Target ABIs may have 8, 16, 32 or 64-bit `int' type. `char' can be wider than 8 bits. GCC gets most of the information about the target machine from a machine description which gives an algebraic formula for each of the machine's instructions. This is a very clean way to describe the target. But when the compiler needs information that is difficult to ! express in this fashion, ad-hoc parameters have been defined for ! machine descriptions. The purpose of portability is to reduce the ! total work needed on the compiler; it was not of interest for its own ! sake. GCC does not contain machine dependent code, but it does contain code that depends on machine parameters such as endianness (whether the most *************** word) and the availability of autoincrem *** 158,169 **** RTL-generation pass, it is often necessary to have multiple strategies for generating code for a particular kind of syntax tree, strategies that are usable for different combinations of parameters. Often, not ! all possible cases have been addressed, but only the common ones or only ! the ones that have been encountered. As a result, a new target may ! require additional strategies. You will know if this happens because ! the compiler will call 'abort'. Fortunately, the new strategies can be ! added in a machine-independent fashion, and will affect only the target ! machines that need them.  File: gccint.info, Node: Interface, Next: Libgcc, Prev: Portability, Up: Top --- 161,172 ---- RTL-generation pass, it is often necessary to have multiple strategies for generating code for a particular kind of syntax tree, strategies that are usable for different combinations of parameters. Often, not ! all possible cases have been addressed, but only the common ones or ! only the ones that have been encountered. As a result, a new target ! may require additional strategies. You will know if this happens ! because the compiler will call `abort'. Fortunately, the new ! strategies can be added in a machine-independent fashion, and will ! affect only the target machines that need them.  File: gccint.info, Node: Interface, Next: Libgcc, Prev: Portability, Up: Top *************** returning such types cannot be called fr *** 181,192 **** vice versa. This does not cause trouble often because few Unix library routines return structures or unions. ! GCC code returns structures and unions that are 1, 2, 4 or 8 bytes long ! in the same registers used for 'int' or 'double' return values. (GCC ! typically allocates variables of such types in registers also.) Structures and unions of other sizes are returned by storing them into an address passed by the caller (usually in a register). The target ! hook 'TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address. By contrast, PCC on most target machines returns structures and unions of any size by copying the data into an area of static storage, and then --- 184,195 ---- vice versa. This does not cause trouble often because few Unix library routines return structures or unions. ! GCC code returns structures and unions that are 1, 2, 4 or 8 bytes ! long in the same registers used for `int' or `double' return values. ! (GCC typically allocates variables of such types in registers also.) Structures and unions of other sizes are returned by storing them into an address passed by the caller (usually in a register). The target ! hook `TARGET_STRUCT_VALUE_RTX' tells GCC where to pass this address. By contrast, PCC on most target machines returns structures and unions of any size by copying the data into an area of static storage, and then *************** are passed "by invisible reference". Th *** 217,228 **** stored in memory, and the address of the memory location is passed to the subroutine. ! If you use 'longjmp', beware of automatic variables. ISO C says that ! automatic variables that are not declared 'volatile' have undefined ! values after a 'longjmp'. And this is all GCC promises to do, because ! it is very difficult to restore register variables correctly, and one of ! GCC's features is that it can put variables in registers without your ! asking it to.  File: gccint.info, Node: Libgcc, Next: Languages, Prev: Interface, Up: Top --- 220,231 ---- stored in memory, and the address of the memory location is passed to the subroutine. ! If you use `longjmp', beware of automatic variables. ISO C says that ! automatic variables that are not declared `volatile' have undefined ! values after a `longjmp'. And this is all GCC promises to do, because ! it is very difficult to restore register variables correctly, and one ! of GCC's features is that it can put variables in registers without ! your asking it to.  File: gccint.info, Node: Libgcc, Next: Languages, Prev: Interface, Up: Top *************** File: gccint.info, Node: Libgcc, Next: *** 230,263 **** 4 The GCC low-level runtime library *********************************** ! GCC provides a low-level runtime library, 'libgcc.a' or 'libgcc_s.so.1' on some platforms. GCC generates calls to routines in this library automatically, whenever it needs to perform some operation that is too complicated to emit inline code for. ! Most of the routines in 'libgcc' handle arithmetic operations that the target processor cannot perform directly. This includes integer multiply and divide on some machines, and all floating-point and ! fixed-point operations on other machines. 'libgcc' also includes routines for exception handling, and a handful of miscellaneous operations. Some of these routines can be defined in mostly machine-independent C. ! Others must be hand-written in assembly language for each processor that ! needs them. ! GCC will also generate calls to C library routines, such as 'memcpy' ! and 'memset', in some cases. The set of routines that GCC may possibly ! use is documented in *note (gcc)Other Builtins::. These routines take arguments and return values of a specific machine mode, not a specific C type. *Note Machine Modes::, for an explanation of this concept. For illustrative purposes, in this chapter the ! floating point type 'float' is assumed to correspond to 'SFmode'; ! 'double' to 'DFmode'; and 'long double' to both 'TFmode' and 'XFmode'. ! Similarly, the integer types 'int' and 'unsigned int' correspond to ! 'SImode'; 'long' and 'unsigned long' to 'DImode'; and 'long long' and ! 'unsigned long long' to 'TImode'. * Menu: --- 233,266 ---- 4 The GCC low-level runtime library *********************************** ! GCC provides a low-level runtime library, `libgcc.a' or `libgcc_s.so.1' on some platforms. GCC generates calls to routines in this library automatically, whenever it needs to perform some operation that is too complicated to emit inline code for. ! Most of the routines in `libgcc' handle arithmetic operations that the target processor cannot perform directly. This includes integer multiply and divide on some machines, and all floating-point and ! fixed-point operations on other machines. `libgcc' also includes routines for exception handling, and a handful of miscellaneous operations. Some of these routines can be defined in mostly machine-independent C. ! Others must be hand-written in assembly language for each processor ! that needs them. ! GCC will also generate calls to C library routines, such as `memcpy' ! and `memset', in some cases. The set of routines that GCC may possibly ! use is documented in *note Other Builtins: (gcc)Other Builtins. These routines take arguments and return values of a specific machine mode, not a specific C type. *Note Machine Modes::, for an explanation of this concept. For illustrative purposes, in this chapter the ! floating point type `float' is assumed to correspond to `SFmode'; ! `double' to `DFmode'; and `long double' to both `TFmode' and `XFmode'. ! Similarly, the integer types `int' and `unsigned int' correspond to ! `SImode'; `long' and `unsigned long' to `DImode'; and `long long' and ! `unsigned long long' to `TImode'. * Menu: *************** hardware support for arithmetic operatio *** 320,327 **** -- Runtime Function: unsigned int __udivsi3 (unsigned int A, unsigned int B) ! -- Runtime Function: unsigned long __udivdi3 (unsigned long A, unsigned ! long B) -- Runtime Function: unsigned long long __udivti3 (unsigned long long A, unsigned long long B) These functions return the quotient of the unsigned division of A --- 323,330 ---- -- Runtime Function: unsigned int __udivsi3 (unsigned int A, unsigned int B) ! -- Runtime Function: unsigned long __udivdi3 (unsigned long A, ! unsigned long B) -- Runtime Function: unsigned long long __udivti3 (unsigned long long A, unsigned long long B) These functions return the quotient of the unsigned division of A *************** hardware support for arithmetic operatio *** 337,344 **** -- Runtime Function: unsigned int __umodsi3 (unsigned int A, unsigned int B) ! -- Runtime Function: unsigned long __umoddi3 (unsigned long A, unsigned ! long B) -- Runtime Function: unsigned long long __umodti3 (unsigned long long A, unsigned long long B) These functions return the remainder of the unsigned division of A --- 340,347 ---- -- Runtime Function: unsigned int __umodsi3 (unsigned int A, unsigned int B) ! -- Runtime Function: unsigned long __umoddi3 (unsigned long A, ! unsigned long B) -- Runtime Function: unsigned long long __umodti3 (unsigned long long A, unsigned long long B) These functions return the remainder of the unsigned division of A *************** result using either signed or unsigned c *** 361,377 **** and if A and B are equal they return 1. -- Runtime Function: int __ucmpdi2 (unsigned long A, unsigned long B) ! -- Runtime Function: int __ucmpti2 (unsigned long long A, unsigned long ! long B) ! These functions perform an unsigned comparison of A and B. If A is ! less than B, they return 0; if A is greater than B, they return 2; ! and if A and B are equal they return 1. 4.1.3 Trapping arithmetic functions ----------------------------------- The following functions implement trapping arithmetic. These functions ! call the libc function 'abort' upon signed arithmetic overflow. -- Runtime Function: int __absvsi2 (int A) -- Runtime Function: long __absvdi2 (long A) --- 364,380 ---- and if A and B are equal they return 1. -- Runtime Function: int __ucmpdi2 (unsigned long A, unsigned long B) ! -- Runtime Function: int __ucmpti2 (unsigned long long A, unsigned ! long long B) ! These functions perform an unsigned comparison of A and B. If A ! is less than B, they return 0; if A is greater than B, they return ! 2; and if A and B are equal they return 1. 4.1.3 Trapping arithmetic functions ----------------------------------- The following functions implement trapping arithmetic. These functions ! call the libc function `abort' upon signed arithmetic overflow. -- Runtime Function: int __absvsi2 (int A) -- Runtime Function: long __absvdi2 (long A) *************** call the libc function 'abort' upon sign *** 379,398 **** -- Runtime Function: int __addvsi3 (int A, int B) -- Runtime Function: long __addvdi3 (long A, long B) ! These functions return the sum of A and B; that is 'A + B'. -- Runtime Function: int __mulvsi3 (int A, int B) -- Runtime Function: long __mulvdi3 (long A, long B) ! The functions return the product of A and B; that is 'A * B'. -- Runtime Function: int __negvsi2 (int A) -- Runtime Function: long __negvdi2 (long A) ! These functions return the negation of A; that is '-A'. -- Runtime Function: int __subvsi3 (int A, int B) -- Runtime Function: long __subvdi3 (long A, long B) ! These functions return the difference between B and A; that is 'A - ! B'. 4.1.4 Bit operations -------------------- --- 382,401 ---- -- Runtime Function: int __addvsi3 (int A, int B) -- Runtime Function: long __addvdi3 (long A, long B) ! These functions return the sum of A and B; that is `A + B'. -- Runtime Function: int __mulvsi3 (int A, int B) -- Runtime Function: long __mulvdi3 (long A, long B) ! The functions return the product of A and B; that is `A * B'. -- Runtime Function: int __negvsi2 (int A) -- Runtime Function: long __negvdi2 (long A) ! These functions return the negation of A; that is `-A'. -- Runtime Function: int __subvsi3 (int A, int B) -- Runtime Function: long __subvdi3 (long A, long B) ! These functions return the difference between B and A; that is `A ! - B'. 4.1.4 Bit operations -------------------- *************** File: gccint.info, Node: Soft float lib *** 440,454 **** The software floating point library is used on machines which do not have hardware support for floating point. It is also used whenever ! '-msoft-float' is used to disable generation of floating point instructions. (Not all targets support this switch.) For compatibility with other compilers, the floating point emulation ! routines can be renamed with the 'DECLARE_LIBRARY_RENAMES' macro (*note Library Calls::). In this section, the default names are used. ! Presently the library does not support 'XFmode', which is used for ! 'long double' on some architectures. 4.2.1 Arithmetic functions -------------------------- --- 443,457 ---- The software floating point library is used on machines which do not have hardware support for floating point. It is also used whenever ! `-msoft-float' is used to disable generation of floating point instructions. (Not all targets support this switch.) For compatibility with other compilers, the floating point emulation ! routines can be renamed with the `DECLARE_LIBRARY_RENAMES' macro (*note Library Calls::). In this section, the default names are used. ! Presently the library does not support `XFmode', which is used for ! `long double' on some architectures. 4.2.1 Arithmetic functions -------------------------- *************** Library Calls::). In this section, the *** 549,556 **** -- Runtime Function: unsigned long long __fixunsdfti (double A) -- Runtime Function: unsigned long long __fixunstfti (long double A) -- Runtime Function: unsigned long long __fixunsxfti (long double A) ! These functions convert A to an unsigned long long, rounding toward ! zero. Negative values all become zero. -- Runtime Function: float __floatsisf (int I) -- Runtime Function: double __floatsidf (int I) --- 552,559 ---- -- Runtime Function: unsigned long long __fixunsdfti (double A) -- Runtime Function: unsigned long long __fixunstfti (long double A) -- Runtime Function: unsigned long long __fixunsxfti (long double A) ! These functions convert A to an unsigned long long, rounding ! toward zero. Negative values all become zero. -- Runtime Function: float __floatsisf (int I) -- Runtime Function: double __floatsidf (int I) *************** There are two sets of basic comparison f *** 598,607 **** -- Runtime Function: int __cmpdf2 (double A, double B) -- Runtime Function: int __cmptf2 (long double A, long double B) These functions calculate a <=> b. That is, if A is less than B, ! they return -1; if A is greater than B, they return 1; and if A and ! B are equal they return 0. If either argument is NaN they return ! 1, but you should not rely on this; if NaN is a possibility, use ! one of the higher-level comparison functions. -- Runtime Function: int __unordsf2 (float A, float B) -- Runtime Function: int __unorddf2 (double A, double B) --- 601,610 ---- -- Runtime Function: int __cmpdf2 (double A, double B) -- Runtime Function: int __cmptf2 (long double A, long double B) These functions calculate a <=> b. That is, if A is less than B, ! they return -1; if A is greater than B, they return 1; and if A ! and B are equal they return 0. If either argument is NaN they ! return 1, but you should not rely on this; if NaN is a ! possibility, use one of the higher-level comparison functions. -- Runtime Function: int __unordsf2 (float A, float B) -- Runtime Function: int __unorddf2 (double A, double B) *************** hood, all of these routines are implemen *** 619,634 **** return E; return __cmpXf2 (a, b); ! where E is a constant chosen to give the proper behavior for NaN. Thus, ! the meaning of the return value is different for each set. Do not rely ! on this implementation; only the semantics documented below are ! guaranteed. -- Runtime Function: int __eqsf2 (float A, float B) -- Runtime Function: int __eqdf2 (double A, double B) -- Runtime Function: int __eqtf2 (long double A, long double B) ! These functions return zero if neither argument is NaN, and A and B ! are equal. -- Runtime Function: int __nesf2 (float A, float B) -- Runtime Function: int __nedf2 (double A, double B) --- 622,637 ---- return E; return __cmpXf2 (a, b); ! where E is a constant chosen to give the proper behavior for NaN. ! Thus, the meaning of the return value is different for each set. Do ! not rely on this implementation; only the semantics documented below ! are guaranteed. -- Runtime Function: int __eqsf2 (float A, float B) -- Runtime Function: int __eqdf2 (double A, double B) -- Runtime Function: int __eqtf2 (long double A, long double B) ! These functions return zero if neither argument is NaN, and A and ! B are equal. -- Runtime Function: int __nesf2 (float A, float B) -- Runtime Function: int __nedf2 (double A, double B) *************** guaranteed. *** 669,676 **** -- Runtime Function: long double __powixf2 (long double A, int B) These functions convert raise A to the power B. ! -- Runtime Function: complex float __mulsc3 (float A, float B, float C, ! float D) -- Runtime Function: complex double __muldc3 (double A, double B, double C, double D) -- Runtime Function: complex long double __multc3 (long double A, long --- 672,679 ---- -- Runtime Function: long double __powixf2 (long double A, int B) These functions convert raise A to the power B. ! -- Runtime Function: complex float __mulsc3 (float A, float B, float ! C, float D) -- Runtime Function: complex double __muldc3 (double A, double B, double C, double D) -- Runtime Function: complex long double __multc3 (long double A, long *************** guaranteed. *** 680,687 **** These functions return the product of A + iB and C + iD, following the rules of C99 Annex G. ! -- Runtime Function: complex float __divsc3 (float A, float B, float C, ! float D) -- Runtime Function: complex double __divdc3 (double A, double B, double C, double D) -- Runtime Function: complex long double __divtc3 (long double A, long --- 683,690 ---- These functions return the product of A + iB and C + iD, following the rules of C99 Annex G. ! -- Runtime Function: complex float __divsc3 (float A, float B, float ! C, float D) -- Runtime Function: complex double __divdc3 (double A, double B, double C, double D) -- Runtime Function: complex long double __divtc3 (long double A, long *************** selected at configure time. *** 880,887 **** -- Runtime Function: unsigned long __bid_fixunsdddi (_Decimal64 A) -- Runtime Function: unsigned long __dpd_fixunstddi (_Decimal128 A) -- Runtime Function: unsigned long __bid_fixunstddi (_Decimal128 A) ! These functions convert A to an unsigned long. Negative values all ! become zero. -- Runtime Function: _Decimal32 __dpd_floatsisd (int I) -- Runtime Function: _Decimal32 __bid_floatsisd (int I) --- 883,890 ---- -- Runtime Function: unsigned long __bid_fixunsdddi (_Decimal64 A) -- Runtime Function: unsigned long __dpd_fixunstddi (_Decimal128 A) -- Runtime Function: unsigned long __bid_fixunstddi (_Decimal128 A) ! These functions convert A to an unsigned long. Negative values ! all become zero. -- Runtime Function: _Decimal32 __dpd_floatsisd (int I) -- Runtime Function: _Decimal32 __bid_floatsisd (int I) *************** selected at configure time. *** 907,914 **** -- Runtime Function: _Decimal64 __bid_floatunssidd (unsigned int I) -- Runtime Function: _Decimal128 __dpd_floatunssitd (unsigned int I) -- Runtime Function: _Decimal128 __bid_floatunssitd (unsigned int I) ! These functions convert I, an unsigned integer, to decimal floating ! point. -- Runtime Function: _Decimal32 __dpd_floatunsdisd (unsigned long I) -- Runtime Function: _Decimal32 __bid_floatunsdisd (unsigned long I) --- 910,917 ---- -- Runtime Function: _Decimal64 __bid_floatunssidd (unsigned int I) -- Runtime Function: _Decimal128 __dpd_floatunssitd (unsigned int I) -- Runtime Function: _Decimal128 __bid_floatunssitd (unsigned int I) ! These functions convert I, an unsigned integer, to decimal ! floating point. -- Runtime Function: _Decimal32 __dpd_floatunsdisd (unsigned long I) -- Runtime Function: _Decimal32 __bid_floatunsdisd (unsigned long I) *************** hood, all of these routines are implemen *** 941,950 **** return E; return __bid_cmpXd2 (a, b); ! where E is a constant chosen to give the proper behavior for NaN. Thus, ! the meaning of the return value is different for each set. Do not rely ! on this implementation; only the semantics documented below are ! guaranteed. -- Runtime Function: int __dpd_eqsd2 (_Decimal32 A, _Decimal32 B) -- Runtime Function: int __bid_eqsd2 (_Decimal32 A, _Decimal32 B) --- 944,953 ---- return E; return __bid_cmpXd2 (a, b); ! where E is a constant chosen to give the proper behavior for NaN. ! Thus, the meaning of the return value is different for each set. Do ! not rely on this implementation; only the semantics documented below ! are guaranteed. -- Runtime Function: int __dpd_eqsd2 (_Decimal32 A, _Decimal32 B) -- Runtime Function: int __bid_eqsd2 (_Decimal32 A, _Decimal32 B) *************** guaranteed. *** 952,959 **** -- Runtime Function: int __bid_eqdd2 (_Decimal64 A, _Decimal64 B) -- Runtime Function: int __dpd_eqtd2 (_Decimal128 A, _Decimal128 B) -- Runtime Function: int __bid_eqtd2 (_Decimal128 A, _Decimal128 B) ! These functions return zero if neither argument is NaN, and A and B ! are equal. -- Runtime Function: int __dpd_nesd2 (_Decimal32 A, _Decimal32 B) -- Runtime Function: int __bid_nesd2 (_Decimal32 A, _Decimal32 B) --- 955,962 ---- -- Runtime Function: int __bid_eqdd2 (_Decimal64 A, _Decimal64 B) -- Runtime Function: int __dpd_eqtd2 (_Decimal128 A, _Decimal128 B) -- Runtime Function: int __bid_eqtd2 (_Decimal128 A, _Decimal128 B) ! These functions return zero if neither argument is NaN, and A and ! B are equal. -- Runtime Function: int __dpd_nesd2 (_Decimal32 A, _Decimal32 B) -- Runtime Function: int __bid_nesd2 (_Decimal32 A, _Decimal32 B) *************** File: gccint.info, Node: Fixed-point fr *** 1009,1028 **** The software fixed-point library implements fixed-point fractional arithmetic, and is only activated on selected targets. ! For ease of comprehension 'fract' is an alias for the '_Fract' type, ! 'accum' an alias for '_Accum', and 'sat' an alias for '_Sat'. For illustrative purposes, in this section the fixed-point fractional ! type 'short fract' is assumed to correspond to machine mode 'QQmode'; ! 'unsigned short fract' to 'UQQmode'; 'fract' to 'HQmode'; ! 'unsigned fract' to 'UHQmode'; 'long fract' to 'SQmode'; ! 'unsigned long fract' to 'USQmode'; 'long long fract' to 'DQmode'; and ! 'unsigned long long fract' to 'UDQmode'. Similarly the fixed-point ! accumulator type 'short accum' corresponds to 'HAmode'; ! 'unsigned short accum' to 'UHAmode'; 'accum' to 'SAmode'; ! 'unsigned accum' to 'USAmode'; 'long accum' to 'DAmode'; ! 'unsigned long accum' to 'UDAmode'; 'long long accum' to 'TAmode'; and ! 'unsigned long long accum' to 'UTAmode'. 4.4.1 Arithmetic functions -------------------------- --- 1012,1031 ---- The software fixed-point library implements fixed-point fractional arithmetic, and is only activated on selected targets. ! For ease of comprehension `fract' is an alias for the `_Fract' type, ! `accum' an alias for `_Accum', and `sat' an alias for `_Sat'. For illustrative purposes, in this section the fixed-point fractional ! type `short fract' is assumed to correspond to machine mode `QQmode'; ! `unsigned short fract' to `UQQmode'; `fract' to `HQmode'; ! `unsigned fract' to `UHQmode'; `long fract' to `SQmode'; ! `unsigned long fract' to `USQmode'; `long long fract' to `DQmode'; and ! `unsigned long long fract' to `UDQmode'. Similarly the fixed-point ! accumulator type `short accum' corresponds to `HAmode'; ! `unsigned short accum' to `UHAmode'; `accum' to `SAmode'; ! `unsigned accum' to `USAmode'; `long accum' to `DAmode'; ! `unsigned long accum' to `UDAmode'; `long long accum' to `TAmode'; and ! `unsigned long long accum' to `UTAmode'. 4.4.1 Arithmetic functions -------------------------- *************** accumulator type 'short accum' correspon *** 1037,1044 **** fract A, unsigned short fract B) -- Runtime Function: unsigned fract __adduhq3 (unsigned fract A, unsigned fract B) ! -- Runtime Function: unsigned long fract __addusq3 (unsigned long fract ! A, unsigned long fract B) -- Runtime Function: unsigned long long fract __addudq3 (unsigned long long fract A, unsigned long long fract B) -- Runtime Function: short accum __addha3 (short accum A, short accum --- 1040,1047 ---- fract A, unsigned short fract B) -- Runtime Function: unsigned fract __adduhq3 (unsigned fract A, unsigned fract B) ! -- Runtime Function: unsigned long fract __addusq3 (unsigned long ! fract A, unsigned long fract B) -- Runtime Function: unsigned long long fract __addudq3 (unsigned long long fract A, unsigned long long fract B) -- Runtime Function: short accum __addha3 (short accum A, short accum *************** accumulator type 'short accum' correspon *** 1051,1070 **** accum A, unsigned short accum B) -- Runtime Function: unsigned accum __addusa3 (unsigned accum A, unsigned accum B) ! -- Runtime Function: unsigned long accum __adduda3 (unsigned long accum ! A, unsigned long accum B) -- Runtime Function: unsigned long long accum __adduta3 (unsigned long long accum A, unsigned long long accum B) These functions return the sum of A and B. ! -- Runtime Function: short fract __ssaddqq3 (short fract A, short fract ! B) -- Runtime Function: fract __ssaddhq3 (fract A, fract B) -- Runtime Function: long fract __ssaddsq3 (long fract A, long fract B) -- Runtime Function: long long fract __ssadddq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __ssaddha3 (short accum A, short accum ! B) -- Runtime Function: accum __ssaddsa3 (accum A, accum B) -- Runtime Function: long accum __ssaddda3 (long accum A, long accum B) -- Runtime Function: long long accum __ssaddta3 (long long accum A, --- 1054,1073 ---- accum A, unsigned short accum B) -- Runtime Function: unsigned accum __addusa3 (unsigned accum A, unsigned accum B) ! -- Runtime Function: unsigned long accum __adduda3 (unsigned long ! accum A, unsigned long accum B) -- Runtime Function: unsigned long long accum __adduta3 (unsigned long long accum A, unsigned long long accum B) These functions return the sum of A and B. ! -- Runtime Function: short fract __ssaddqq3 (short fract A, short ! fract B) -- Runtime Function: fract __ssaddhq3 (fract A, fract B) -- Runtime Function: long fract __ssaddsq3 (long fract A, long fract B) -- Runtime Function: long long fract __ssadddq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __ssaddha3 (short accum A, short ! accum B) -- Runtime Function: accum __ssaddsa3 (accum A, accum B) -- Runtime Function: long accum __ssaddda3 (long accum A, long accum B) -- Runtime Function: long long accum __ssaddta3 (long long accum A, *************** accumulator type 'short accum' correspon *** 1099,1106 **** fract A, unsigned short fract B) -- Runtime Function: unsigned fract __subuhq3 (unsigned fract A, unsigned fract B) ! -- Runtime Function: unsigned long fract __subusq3 (unsigned long fract ! A, unsigned long fract B) -- Runtime Function: unsigned long long fract __subudq3 (unsigned long long fract A, unsigned long long fract B) -- Runtime Function: short accum __subha3 (short accum A, short accum --- 1102,1109 ---- fract A, unsigned short fract B) -- Runtime Function: unsigned fract __subuhq3 (unsigned fract A, unsigned fract B) ! -- Runtime Function: unsigned long fract __subusq3 (unsigned long ! fract A, unsigned long fract B) -- Runtime Function: unsigned long long fract __subudq3 (unsigned long long fract A, unsigned long long fract B) -- Runtime Function: short accum __subha3 (short accum A, short accum *************** accumulator type 'short accum' correspon *** 1113,1138 **** accum A, unsigned short accum B) -- Runtime Function: unsigned accum __subusa3 (unsigned accum A, unsigned accum B) ! -- Runtime Function: unsigned long accum __subuda3 (unsigned long accum ! A, unsigned long accum B) -- Runtime Function: unsigned long long accum __subuta3 (unsigned long long accum A, unsigned long long accum B) ! These functions return the difference of A and B; that is, 'A - B'. ! -- Runtime Function: short fract __sssubqq3 (short fract A, short fract ! B) -- Runtime Function: fract __sssubhq3 (fract A, fract B) -- Runtime Function: long fract __sssubsq3 (long fract A, long fract B) -- Runtime Function: long long fract __sssubdq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __sssubha3 (short accum A, short accum ! B) -- Runtime Function: accum __sssubsa3 (accum A, accum B) -- Runtime Function: long accum __sssubda3 (long accum A, long accum B) -- Runtime Function: long long accum __sssubta3 (long long accum A, long long accum B) These functions return the difference of A and B with signed ! saturation; that is, 'A - B'. -- Runtime Function: unsigned short fract __ussubuqq3 (unsigned short fract A, unsigned short fract B) --- 1116,1141 ---- accum A, unsigned short accum B) -- Runtime Function: unsigned accum __subusa3 (unsigned accum A, unsigned accum B) ! -- Runtime Function: unsigned long accum __subuda3 (unsigned long ! accum A, unsigned long accum B) -- Runtime Function: unsigned long long accum __subuta3 (unsigned long long accum A, unsigned long long accum B) ! These functions return the difference of A and B; that is, `A - B'. ! -- Runtime Function: short fract __sssubqq3 (short fract A, short ! fract B) -- Runtime Function: fract __sssubhq3 (fract A, fract B) -- Runtime Function: long fract __sssubsq3 (long fract A, long fract B) -- Runtime Function: long long fract __sssubdq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __sssubha3 (short accum A, short ! accum B) -- Runtime Function: accum __sssubsa3 (accum A, accum B) -- Runtime Function: long accum __sssubda3 (long accum A, long accum B) -- Runtime Function: long long accum __sssubta3 (long long accum A, long long accum B) These functions return the difference of A and B with signed ! saturation; that is, `A - B'. -- Runtime Function: unsigned short fract __ussubuqq3 (unsigned short fract A, unsigned short fract B) *************** accumulator type 'short accum' correspon *** 1151,1157 **** -- Runtime Function: unsigned long long accum __ussubuta3 (unsigned long long accum A, unsigned long long accum B) These functions return the difference of A and B with unsigned ! saturation; that is, 'A - B'. -- Runtime Function: short fract __mulqq3 (short fract A, short fract B) --- 1154,1160 ---- -- Runtime Function: unsigned long long accum __ussubuta3 (unsigned long long accum A, unsigned long long accum B) These functions return the difference of A and B with unsigned ! saturation; that is, `A - B'. -- Runtime Function: short fract __mulqq3 (short fract A, short fract B) *************** accumulator type 'short accum' correspon *** 1163,1170 **** fract A, unsigned short fract B) -- Runtime Function: unsigned fract __muluhq3 (unsigned fract A, unsigned fract B) ! -- Runtime Function: unsigned long fract __mulusq3 (unsigned long fract ! A, unsigned long fract B) -- Runtime Function: unsigned long long fract __muludq3 (unsigned long long fract A, unsigned long long fract B) -- Runtime Function: short accum __mulha3 (short accum A, short accum --- 1166,1173 ---- fract A, unsigned short fract B) -- Runtime Function: unsigned fract __muluhq3 (unsigned fract A, unsigned fract B) ! -- Runtime Function: unsigned long fract __mulusq3 (unsigned long ! fract A, unsigned long fract B) -- Runtime Function: unsigned long long fract __muludq3 (unsigned long long fract A, unsigned long long fract B) -- Runtime Function: short accum __mulha3 (short accum A, short accum *************** accumulator type 'short accum' correspon *** 1177,1196 **** accum A, unsigned short accum B) -- Runtime Function: unsigned accum __mulusa3 (unsigned accum A, unsigned accum B) ! -- Runtime Function: unsigned long accum __muluda3 (unsigned long accum ! A, unsigned long accum B) -- Runtime Function: unsigned long long accum __muluta3 (unsigned long long accum A, unsigned long long accum B) These functions return the product of A and B. ! -- Runtime Function: short fract __ssmulqq3 (short fract A, short fract ! B) -- Runtime Function: fract __ssmulhq3 (fract A, fract B) -- Runtime Function: long fract __ssmulsq3 (long fract A, long fract B) -- Runtime Function: long long fract __ssmuldq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __ssmulha3 (short accum A, short accum ! B) -- Runtime Function: accum __ssmulsa3 (accum A, accum B) -- Runtime Function: long accum __ssmulda3 (long accum A, long accum B) -- Runtime Function: long long accum __ssmulta3 (long long accum A, --- 1180,1199 ---- accum A, unsigned short accum B) -- Runtime Function: unsigned accum __mulusa3 (unsigned accum A, unsigned accum B) ! -- Runtime Function: unsigned long accum __muluda3 (unsigned long ! accum A, unsigned long accum B) -- Runtime Function: unsigned long long accum __muluta3 (unsigned long long accum A, unsigned long long accum B) These functions return the product of A and B. ! -- Runtime Function: short fract __ssmulqq3 (short fract A, short ! fract B) -- Runtime Function: fract __ssmulhq3 (fract A, fract B) -- Runtime Function: long fract __ssmulsq3 (long fract A, long fract B) -- Runtime Function: long long fract __ssmuldq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __ssmulha3 (short accum A, short ! accum B) -- Runtime Function: accum __ssmulsa3 (accum A, accum B) -- Runtime Function: long accum __ssmulda3 (long accum A, long accum B) -- Runtime Function: long long accum __ssmulta3 (long long accum A, *************** accumulator type 'short accum' correspon *** 1229,1236 **** -- Runtime Function: long accum __divda3 (long accum A, long accum B) -- Runtime Function: long long accum __divta3 (long long accum A, long long accum B) ! These functions return the quotient of the signed division of A and ! B. -- Runtime Function: unsigned short fract __udivuqq3 (unsigned short fract A, unsigned short fract B) --- 1232,1239 ---- -- Runtime Function: long accum __divda3 (long accum A, long accum B) -- Runtime Function: long long accum __divta3 (long long accum A, long long accum B) ! These functions return the quotient of the signed division of A ! and B. -- Runtime Function: unsigned short fract __udivuqq3 (unsigned short fract A, unsigned short fract B) *************** accumulator type 'short accum' correspon *** 1238,1270 **** unsigned fract B) -- Runtime Function: unsigned long fract __udivusq3 (unsigned long fract A, unsigned long fract B) ! -- Runtime Function: unsigned long long fract __udivudq3 (unsigned long ! long fract A, unsigned long long fract B) -- Runtime Function: unsigned short accum __udivuha3 (unsigned short accum A, unsigned short accum B) -- Runtime Function: unsigned accum __udivusa3 (unsigned accum A, unsigned accum B) -- Runtime Function: unsigned long accum __udivuda3 (unsigned long accum A, unsigned long accum B) ! -- Runtime Function: unsigned long long accum __udivuta3 (unsigned long ! long accum A, unsigned long long accum B) These functions return the quotient of the unsigned division of A and B. ! -- Runtime Function: short fract __ssdivqq3 (short fract A, short fract ! B) -- Runtime Function: fract __ssdivhq3 (fract A, fract B) -- Runtime Function: long fract __ssdivsq3 (long fract A, long fract B) -- Runtime Function: long long fract __ssdivdq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __ssdivha3 (short accum A, short accum ! B) -- Runtime Function: accum __ssdivsa3 (accum A, accum B) -- Runtime Function: long accum __ssdivda3 (long accum A, long accum B) -- Runtime Function: long long accum __ssdivta3 (long long accum A, long long accum B) ! These functions return the quotient of the signed division of A and ! B with signed saturation. -- Runtime Function: unsigned short fract __usdivuqq3 (unsigned short fract A, unsigned short fract B) --- 1241,1273 ---- unsigned fract B) -- Runtime Function: unsigned long fract __udivusq3 (unsigned long fract A, unsigned long fract B) ! -- Runtime Function: unsigned long long fract __udivudq3 (unsigned ! long long fract A, unsigned long long fract B) -- Runtime Function: unsigned short accum __udivuha3 (unsigned short accum A, unsigned short accum B) -- Runtime Function: unsigned accum __udivusa3 (unsigned accum A, unsigned accum B) -- Runtime Function: unsigned long accum __udivuda3 (unsigned long accum A, unsigned long accum B) ! -- Runtime Function: unsigned long long accum __udivuta3 (unsigned ! long long accum A, unsigned long long accum B) These functions return the quotient of the unsigned division of A and B. ! -- Runtime Function: short fract __ssdivqq3 (short fract A, short ! fract B) -- Runtime Function: fract __ssdivhq3 (fract A, fract B) -- Runtime Function: long fract __ssdivsq3 (long fract A, long fract B) -- Runtime Function: long long fract __ssdivdq3 (long long fract A, long long fract B) ! -- Runtime Function: short accum __ssdivha3 (short accum A, short ! accum B) -- Runtime Function: accum __ssdivsa3 (accum A, accum B) -- Runtime Function: long accum __ssdivda3 (long accum A, long accum B) -- Runtime Function: long long accum __ssdivta3 (long long accum A, long long accum B) ! These functions return the quotient of the signed division of A ! and B with signed saturation. -- Runtime Function: unsigned short fract __usdivuqq3 (unsigned short fract A, unsigned short fract B) *************** accumulator type 'short accum' correspon *** 1292,1299 **** -- Runtime Function: unsigned short fract __neguqq2 (unsigned short fract A) -- Runtime Function: unsigned fract __neguhq2 (unsigned fract A) ! -- Runtime Function: unsigned long fract __negusq2 (unsigned long fract ! A) -- Runtime Function: unsigned long long fract __negudq2 (unsigned long long fract A) -- Runtime Function: short accum __negha2 (short accum A) --- 1295,1302 ---- -- Runtime Function: unsigned short fract __neguqq2 (unsigned short fract A) -- Runtime Function: unsigned fract __neguhq2 (unsigned fract A) ! -- Runtime Function: unsigned long fract __negusq2 (unsigned long ! fract A) -- Runtime Function: unsigned long long fract __negudq2 (unsigned long long fract A) -- Runtime Function: short accum __negha2 (short accum A) *************** accumulator type 'short accum' correspon *** 1303,1310 **** -- Runtime Function: unsigned short accum __neguha2 (unsigned short accum A) -- Runtime Function: unsigned accum __negusa2 (unsigned accum A) ! -- Runtime Function: unsigned long accum __neguda2 (unsigned long accum ! A) -- Runtime Function: unsigned long long accum __neguta2 (unsigned long long accum A) These functions return the negation of A. --- 1306,1313 ---- -- Runtime Function: unsigned short accum __neguha2 (unsigned short accum A) -- Runtime Function: unsigned accum __negusa2 (unsigned accum A) ! -- Runtime Function: unsigned long accum __neguda2 (unsigned long ! accum A) -- Runtime Function: unsigned long long accum __neguta2 (unsigned long long accum A) These functions return the negation of A. *************** accumulator type 'short accum' correspon *** 1346,1353 **** B) -- Runtime Function: unsigned long fract __ashlusq3 (unsigned long fract A, int B) ! -- Runtime Function: unsigned long long fract __ashludq3 (unsigned long ! long fract A, int B) -- Runtime Function: short accum __ashlha3 (short accum A, int B) -- Runtime Function: accum __ashlsa3 (accum A, int B) -- Runtime Function: long accum __ashlda3 (long accum A, int B) --- 1349,1356 ---- B) -- Runtime Function: unsigned long fract __ashlusq3 (unsigned long fract A, int B) ! -- Runtime Function: unsigned long long fract __ashludq3 (unsigned ! long long fract A, int B) -- Runtime Function: short accum __ashlha3 (short accum A, int B) -- Runtime Function: accum __ashlsa3 (accum A, int B) -- Runtime Function: long accum __ashlda3 (long accum A, int B) *************** accumulator type 'short accum' correspon *** 1359,1366 **** B) -- Runtime Function: unsigned long accum __ashluda3 (unsigned long accum A, int B) ! -- Runtime Function: unsigned long long accum __ashluta3 (unsigned long ! long accum A, int B) These functions return the result of shifting A left by B bits. -- Runtime Function: short fract __ashrqq3 (short fract A, int B) --- 1362,1369 ---- B) -- Runtime Function: unsigned long accum __ashluda3 (unsigned long accum A, int B) ! -- Runtime Function: unsigned long long accum __ashluta3 (unsigned ! long long accum A, int B) These functions return the result of shifting A left by B bits. -- Runtime Function: short fract __ashrqq3 (short fract A, int B) *************** accumulator type 'short accum' correspon *** 1382,1397 **** B) -- Runtime Function: unsigned long fract __lshrusq3 (unsigned long fract A, int B) ! -- Runtime Function: unsigned long long fract __lshrudq3 (unsigned long ! long fract A, int B) -- Runtime Function: unsigned short accum __lshruha3 (unsigned short accum A, int B) -- Runtime Function: unsigned accum __lshrusa3 (unsigned accum A, int B) -- Runtime Function: unsigned long accum __lshruda3 (unsigned long accum A, int B) ! -- Runtime Function: unsigned long long accum __lshruta3 (unsigned long ! long accum A, int B) These functions return the result of logically shifting A right by B bits. --- 1385,1400 ---- B) -- Runtime Function: unsigned long fract __lshrusq3 (unsigned long fract A, int B) ! -- Runtime Function: unsigned long long fract __lshrudq3 (unsigned ! long long fract A, int B) -- Runtime Function: unsigned short accum __lshruha3 (unsigned short accum A, int B) -- Runtime Function: unsigned accum __lshrusa3 (unsigned accum A, int B) -- Runtime Function: unsigned long accum __lshruda3 (unsigned long accum A, int B) ! -- Runtime Function: unsigned long long accum __lshruta3 (unsigned ! long long accum A, int B) These functions return the result of logically shifting A right by B bits. *************** accumulator type 'short accum' correspon *** 1404,1430 **** -- Runtime Function: long accum __ssashlda3 (long accum A, int B) -- Runtime Function: long long accum __ssashlta3 (long long accum A, int B) ! These functions return the result of shifting A left by B bits with ! signed saturation. -- Runtime Function: unsigned short fract __usashluqq3 (unsigned short fract A, int B) ! -- Runtime Function: unsigned fract __usashluhq3 (unsigned fract A, int ! B) -- Runtime Function: unsigned long fract __usashlusq3 (unsigned long fract A, int B) -- Runtime Function: unsigned long long fract __usashludq3 (unsigned long long fract A, int B) -- Runtime Function: unsigned short accum __usashluha3 (unsigned short accum A, int B) ! -- Runtime Function: unsigned accum __usashlusa3 (unsigned accum A, int ! B) -- Runtime Function: unsigned long accum __usashluda3 (unsigned long accum A, int B) -- Runtime Function: unsigned long long accum __usashluta3 (unsigned long long accum A, int B) ! These functions return the result of shifting A left by B bits with ! unsigned saturation. 4.4.2 Comparison functions -------------------------- --- 1407,1433 ---- -- Runtime Function: long accum __ssashlda3 (long accum A, int B) -- Runtime Function: long long accum __ssashlta3 (long long accum A, int B) ! These functions return the result of shifting A left by B bits ! with signed saturation. -- Runtime Function: unsigned short fract __usashluqq3 (unsigned short fract A, int B) ! -- Runtime Function: unsigned fract __usashluhq3 (unsigned fract A, ! int B) -- Runtime Function: unsigned long fract __usashlusq3 (unsigned long fract A, int B) -- Runtime Function: unsigned long long fract __usashludq3 (unsigned long long fract A, int B) -- Runtime Function: unsigned short accum __usashluha3 (unsigned short accum A, int B) ! -- Runtime Function: unsigned accum __usashlusa3 (unsigned accum A, ! int B) -- Runtime Function: unsigned long accum __usashluda3 (unsigned long accum A, int B) -- Runtime Function: unsigned long long accum __usashluta3 (unsigned long long accum A, int B) ! These functions return the result of shifting A left by B bits ! with unsigned saturation. 4.4.2 Comparison functions -------------------------- *************** returned result using either signed or u *** 1478,1490 **** -- Runtime Function: unsigned short fract __fractqquqq (short fract A) -- Runtime Function: unsigned fract __fractqquhq (short fract A) -- Runtime Function: unsigned long fract __fractqqusq (short fract A) ! -- Runtime Function: unsigned long long fract __fractqqudq (short fract ! A) -- Runtime Function: unsigned short accum __fractqquha (short fract A) -- Runtime Function: unsigned accum __fractqqusa (short fract A) -- Runtime Function: unsigned long accum __fractqquda (short fract A) ! -- Runtime Function: unsigned long long accum __fractqquta (short fract ! A) -- Runtime Function: signed char __fractqqqi (short fract A) -- Runtime Function: short __fractqqhi (short fract A) -- Runtime Function: int __fractqqsi (short fract A) --- 1481,1493 ---- -- Runtime Function: unsigned short fract __fractqquqq (short fract A) -- Runtime Function: unsigned fract __fractqquhq (short fract A) -- Runtime Function: unsigned long fract __fractqqusq (short fract A) ! -- Runtime Function: unsigned long long fract __fractqqudq (short ! fract A) -- Runtime Function: unsigned short accum __fractqquha (short fract A) -- Runtime Function: unsigned accum __fractqqusa (short fract A) -- Runtime Function: unsigned long accum __fractqquda (short fract A) ! -- Runtime Function: unsigned long long accum __fractqquta (short ! fract A) -- Runtime Function: signed char __fractqqqi (short fract A) -- Runtime Function: short __fractqqhi (short fract A) -- Runtime Function: int __fractqqsi (short fract A) *************** returned result using either signed or u *** 1545,1559 **** -- Runtime Function: accum __fractdqsa (long long fract A) -- Runtime Function: long accum __fractdqda (long long fract A) -- Runtime Function: long long accum __fractdqta (long long fract A) ! -- Runtime Function: unsigned short fract __fractdquqq (long long fract ! A) -- Runtime Function: unsigned fract __fractdquhq (long long fract A) -- Runtime Function: unsigned long fract __fractdqusq (long long fract A) -- Runtime Function: unsigned long long fract __fractdqudq (long long fract A) ! -- Runtime Function: unsigned short accum __fractdquha (long long fract ! A) -- Runtime Function: unsigned accum __fractdqusa (long long fract A) -- Runtime Function: unsigned long accum __fractdquda (long long fract A) --- 1548,1562 ---- -- Runtime Function: accum __fractdqsa (long long fract A) -- Runtime Function: long accum __fractdqda (long long fract A) -- Runtime Function: long long accum __fractdqta (long long fract A) ! -- Runtime Function: unsigned short fract __fractdquqq (long long ! fract A) -- Runtime Function: unsigned fract __fractdquhq (long long fract A) -- Runtime Function: unsigned long fract __fractdqusq (long long fract A) -- Runtime Function: unsigned long long fract __fractdqudq (long long fract A) ! -- Runtime Function: unsigned short accum __fractdquha (long long ! fract A) -- Runtime Function: unsigned accum __fractdqusa (long long fract A) -- Runtime Function: unsigned long accum __fractdquda (long long fract A) *************** returned result using either signed or u *** 1576,1588 **** -- Runtime Function: unsigned short fract __fracthauqq (short accum A) -- Runtime Function: unsigned fract __fracthauhq (short accum A) -- Runtime Function: unsigned long fract __fracthausq (short accum A) ! -- Runtime Function: unsigned long long fract __fracthaudq (short accum ! A) -- Runtime Function: unsigned short accum __fracthauha (short accum A) -- Runtime Function: unsigned accum __fracthausa (short accum A) -- Runtime Function: unsigned long accum __fracthauda (short accum A) ! -- Runtime Function: unsigned long long accum __fracthauta (short accum ! A) -- Runtime Function: signed char __fracthaqi (short accum A) -- Runtime Function: short __fracthahi (short accum A) -- Runtime Function: int __fracthasi (short accum A) --- 1579,1591 ---- -- Runtime Function: unsigned short fract __fracthauqq (short accum A) -- Runtime Function: unsigned fract __fracthauhq (short accum A) -- Runtime Function: unsigned long fract __fracthausq (short accum A) ! -- Runtime Function: unsigned long long fract __fracthaudq (short ! accum A) -- Runtime Function: unsigned short accum __fracthauha (short accum A) -- Runtime Function: unsigned accum __fracthausa (short accum A) -- Runtime Function: unsigned long accum __fracthauda (short accum A) ! -- Runtime Function: unsigned long long accum __fracthauta (short ! accum A) -- Runtime Function: signed char __fracthaqi (short accum A) -- Runtime Function: short __fracthahi (short accum A) -- Runtime Function: int __fracthasi (short accum A) *************** returned result using either signed or u *** 1643,1657 **** -- Runtime Function: short accum __fracttaha2 (long long accum A) -- Runtime Function: accum __fracttasa2 (long long accum A) -- Runtime Function: long accum __fracttada2 (long long accum A) ! -- Runtime Function: unsigned short fract __fracttauqq (long long accum ! A) -- Runtime Function: unsigned fract __fracttauhq (long long accum A) -- Runtime Function: unsigned long fract __fracttausq (long long accum A) -- Runtime Function: unsigned long long fract __fracttaudq (long long accum A) ! -- Runtime Function: unsigned short accum __fracttauha (long long accum ! A) -- Runtime Function: unsigned accum __fracttausa (long long accum A) -- Runtime Function: unsigned long accum __fracttauda (long long accum A) --- 1646,1660 ---- -- Runtime Function: short accum __fracttaha2 (long long accum A) -- Runtime Function: accum __fracttasa2 (long long accum A) -- Runtime Function: long accum __fracttada2 (long long accum A) ! -- Runtime Function: unsigned short fract __fracttauqq (long long ! accum A) -- Runtime Function: unsigned fract __fracttauhq (long long accum A) -- Runtime Function: unsigned long fract __fracttausq (long long accum A) -- Runtime Function: unsigned long long fract __fracttaudq (long long accum A) ! -- Runtime Function: unsigned short accum __fracttauha (long long ! accum A) -- Runtime Function: unsigned accum __fracttausa (long long accum A) -- Runtime Function: unsigned long accum __fracttauda (long long accum A) *************** returned result using either signed or u *** 1667,1689 **** -- Runtime Function: short fract __fractuqqqq (unsigned short fract A) -- Runtime Function: fract __fractuqqhq (unsigned short fract A) -- Runtime Function: long fract __fractuqqsq (unsigned short fract A) ! -- Runtime Function: long long fract __fractuqqdq (unsigned short fract ! A) -- Runtime Function: short accum __fractuqqha (unsigned short fract A) -- Runtime Function: accum __fractuqqsa (unsigned short fract A) -- Runtime Function: long accum __fractuqqda (unsigned short fract A) ! -- Runtime Function: long long accum __fractuqqta (unsigned short fract ! A) ! -- Runtime Function: unsigned fract __fractuqquhq2 (unsigned short fract A) ! -- Runtime Function: unsigned long fract __fractuqqusq2 (unsigned short fract A) -- Runtime Function: unsigned long long fract __fractuqqudq2 (unsigned short fract A) ! -- Runtime Function: unsigned short accum __fractuqquha (unsigned short fract A) - -- Runtime Function: unsigned accum __fractuqqusa (unsigned short fract - A) -- Runtime Function: unsigned long accum __fractuqquda (unsigned short fract A) -- Runtime Function: unsigned long long accum __fractuqquta (unsigned --- 1670,1692 ---- -- Runtime Function: short fract __fractuqqqq (unsigned short fract A) -- Runtime Function: fract __fractuqqhq (unsigned short fract A) -- Runtime Function: long fract __fractuqqsq (unsigned short fract A) ! -- Runtime Function: long long fract __fractuqqdq (unsigned short ! fract A) -- Runtime Function: short accum __fractuqqha (unsigned short fract A) -- Runtime Function: accum __fractuqqsa (unsigned short fract A) -- Runtime Function: long accum __fractuqqda (unsigned short fract A) ! -- Runtime Function: long long accum __fractuqqta (unsigned short fract A) ! -- Runtime Function: unsigned fract __fractuqquhq2 (unsigned short fract A) + -- Runtime Function: unsigned long fract __fractuqqusq2 (unsigned + short fract A) -- Runtime Function: unsigned long long fract __fractuqqudq2 (unsigned short fract A) ! -- Runtime Function: unsigned short accum __fractuqquha (unsigned ! short fract A) ! -- Runtime Function: unsigned accum __fractuqqusa (unsigned short fract A) -- Runtime Function: unsigned long accum __fractuqquda (unsigned short fract A) -- Runtime Function: unsigned long long accum __fractuqquta (unsigned *************** returned result using either signed or u *** 1705,1716 **** -- Runtime Function: long long accum __fractuhqta (unsigned fract A) -- Runtime Function: unsigned short fract __fractuhquqq2 (unsigned fract A) ! -- Runtime Function: unsigned long fract __fractuhqusq2 (unsigned fract ! A) -- Runtime Function: unsigned long long fract __fractuhqudq2 (unsigned fract A) ! -- Runtime Function: unsigned short accum __fractuhquha (unsigned fract ! A) -- Runtime Function: unsigned accum __fractuhqusa (unsigned fract A) -- Runtime Function: unsigned long accum __fractuhquda (unsigned fract A) --- 1708,1719 ---- -- Runtime Function: long long accum __fractuhqta (unsigned fract A) -- Runtime Function: unsigned short fract __fractuhquqq2 (unsigned fract A) ! -- Runtime Function: unsigned long fract __fractuhqusq2 (unsigned ! fract A) -- Runtime Function: unsigned long long fract __fractuhqudq2 (unsigned fract A) ! -- Runtime Function: unsigned short accum __fractuhquha (unsigned ! fract A) -- Runtime Function: unsigned accum __fractuhqusa (unsigned fract A) -- Runtime Function: unsigned long accum __fractuhquda (unsigned fract A) *************** returned result using either signed or u *** 1733,1742 **** -- Runtime Function: long accum __fractusqda (unsigned long fract A) -- Runtime Function: long long accum __fractusqta (unsigned long fract A) ! -- Runtime Function: unsigned short fract __fractusquqq2 (unsigned long fract A) - -- Runtime Function: unsigned fract __fractusquhq2 (unsigned long fract - A) -- Runtime Function: unsigned long long fract __fractusqudq2 (unsigned long fract A) -- Runtime Function: unsigned short accum __fractusquha (unsigned long --- 1736,1745 ---- -- Runtime Function: long accum __fractusqda (unsigned long fract A) -- Runtime Function: long long accum __fractusqta (unsigned long fract A) ! -- Runtime Function: unsigned short fract __fractusquqq2 (unsigned ! long fract A) ! -- Runtime Function: unsigned fract __fractusquhq2 (unsigned long fract A) -- Runtime Function: unsigned long long fract __fractusqudq2 (unsigned long fract A) -- Runtime Function: unsigned short accum __fractusquha (unsigned long *************** returned result using either signed or u *** 1754,1775 **** -- Runtime Function: long long __fractusqti (unsigned long fract A) -- Runtime Function: float __fractusqsf (unsigned long fract A) -- Runtime Function: double __fractusqdf (unsigned long fract A) ! -- Runtime Function: short fract __fractudqqq (unsigned long long fract ! A) -- Runtime Function: fract __fractudqhq (unsigned long long fract A) -- Runtime Function: long fract __fractudqsq (unsigned long long fract A) -- Runtime Function: long long fract __fractudqdq (unsigned long long fract A) ! -- Runtime Function: short accum __fractudqha (unsigned long long fract ! A) -- Runtime Function: accum __fractudqsa (unsigned long long fract A) -- Runtime Function: long accum __fractudqda (unsigned long long fract A) -- Runtime Function: long long accum __fractudqta (unsigned long long fract A) ! -- Runtime Function: unsigned short fract __fractudquqq2 (unsigned long ! long fract A) -- Runtime Function: unsigned fract __fractudquhq2 (unsigned long long fract A) -- Runtime Function: unsigned long fract __fractudqusq2 (unsigned long --- 1757,1778 ---- -- Runtime Function: long long __fractusqti (unsigned long fract A) -- Runtime Function: float __fractusqsf (unsigned long fract A) -- Runtime Function: double __fractusqdf (unsigned long fract A) ! -- Runtime Function: short fract __fractudqqq (unsigned long long ! fract A) -- Runtime Function: fract __fractudqhq (unsigned long long fract A) -- Runtime Function: long fract __fractudqsq (unsigned long long fract A) -- Runtime Function: long long fract __fractudqdq (unsigned long long fract A) ! -- Runtime Function: short accum __fractudqha (unsigned long long ! fract A) -- Runtime Function: accum __fractudqsa (unsigned long long fract A) -- Runtime Function: long accum __fractudqda (unsigned long long fract A) -- Runtime Function: long long accum __fractudqta (unsigned long long fract A) ! -- Runtime Function: unsigned short fract __fractudquqq2 (unsigned ! long long fract A) -- Runtime Function: unsigned fract __fractudquhq2 (unsigned long long fract A) -- Runtime Function: unsigned long fract __fractudqusq2 (unsigned long *************** returned result using either signed or u *** 1782,1789 **** long fract A) -- Runtime Function: unsigned long long accum __fractudquta (unsigned long long fract A) ! -- Runtime Function: signed char __fractudqqi (unsigned long long fract ! A) -- Runtime Function: short __fractudqhi (unsigned long long fract A) -- Runtime Function: int __fractudqsi (unsigned long long fract A) -- Runtime Function: long __fractudqdi (unsigned long long fract A) --- 1785,1792 ---- long fract A) -- Runtime Function: unsigned long long accum __fractudquta (unsigned long long fract A) ! -- Runtime Function: signed char __fractudqqi (unsigned long long ! fract A) -- Runtime Function: short __fractudqhi (unsigned long long fract A) -- Runtime Function: int __fractudqsi (unsigned long long fract A) -- Runtime Function: long __fractudqdi (unsigned long long fract A) *************** returned result using either signed or u *** 1794,1818 **** -- Runtime Function: short fract __fractuhaqq (unsigned short accum A) -- Runtime Function: fract __fractuhahq (unsigned short accum A) -- Runtime Function: long fract __fractuhasq (unsigned short accum A) ! -- Runtime Function: long long fract __fractuhadq (unsigned short accum ! A) -- Runtime Function: short accum __fractuhaha (unsigned short accum A) -- Runtime Function: accum __fractuhasa (unsigned short accum A) -- Runtime Function: long accum __fractuhada (unsigned short accum A) ! -- Runtime Function: long long accum __fractuhata (unsigned short accum ! A) ! -- Runtime Function: unsigned short fract __fractuhauqq (unsigned short accum A) - -- Runtime Function: unsigned fract __fractuhauhq (unsigned short accum - A) -- Runtime Function: unsigned long fract __fractuhausq (unsigned short accum A) -- Runtime Function: unsigned long long fract __fractuhaudq (unsigned short accum A) -- Runtime Function: unsigned accum __fractuhausa2 (unsigned short accum A) ! -- Runtime Function: unsigned long accum __fractuhauda2 (unsigned short ! accum A) -- Runtime Function: unsigned long long accum __fractuhauta2 (unsigned short accum A) -- Runtime Function: signed char __fractuhaqi (unsigned short accum A) --- 1797,1821 ---- -- Runtime Function: short fract __fractuhaqq (unsigned short accum A) -- Runtime Function: fract __fractuhahq (unsigned short accum A) -- Runtime Function: long fract __fractuhasq (unsigned short accum A) ! -- Runtime Function: long long fract __fractuhadq (unsigned short ! accum A) -- Runtime Function: short accum __fractuhaha (unsigned short accum A) -- Runtime Function: accum __fractuhasa (unsigned short accum A) -- Runtime Function: long accum __fractuhada (unsigned short accum A) ! -- Runtime Function: long long accum __fractuhata (unsigned short ! accum A) ! -- Runtime Function: unsigned short fract __fractuhauqq (unsigned ! short accum A) ! -- Runtime Function: unsigned fract __fractuhauhq (unsigned short accum A) -- Runtime Function: unsigned long fract __fractuhausq (unsigned short accum A) -- Runtime Function: unsigned long long fract __fractuhaudq (unsigned short accum A) -- Runtime Function: unsigned accum __fractuhausa2 (unsigned short accum A) ! -- Runtime Function: unsigned long accum __fractuhauda2 (unsigned ! short accum A) -- Runtime Function: unsigned long long accum __fractuhauta2 (unsigned short accum A) -- Runtime Function: signed char __fractuhaqi (unsigned short accum A) *************** returned result using either signed or u *** 1830,1837 **** -- Runtime Function: accum __fractusasa (unsigned accum A) -- Runtime Function: long accum __fractusada (unsigned accum A) -- Runtime Function: long long accum __fractusata (unsigned accum A) ! -- Runtime Function: unsigned short fract __fractusauqq (unsigned accum ! A) -- Runtime Function: unsigned fract __fractusauhq (unsigned accum A) -- Runtime Function: unsigned long fract __fractusausq (unsigned accum A) --- 1833,1840 ---- -- Runtime Function: accum __fractusasa (unsigned accum A) -- Runtime Function: long accum __fractusada (unsigned accum A) -- Runtime Function: long long accum __fractusata (unsigned accum A) ! -- Runtime Function: unsigned short fract __fractusauqq (unsigned ! accum A) -- Runtime Function: unsigned fract __fractusauhq (unsigned accum A) -- Runtime Function: unsigned long fract __fractusausq (unsigned accum A) *************** returned result using either signed or u *** 1839,1846 **** accum A) -- Runtime Function: unsigned short accum __fractusauha2 (unsigned accum A) ! -- Runtime Function: unsigned long accum __fractusauda2 (unsigned accum ! A) -- Runtime Function: unsigned long long accum __fractusauta2 (unsigned accum A) -- Runtime Function: signed char __fractusaqi (unsigned accum A) --- 1842,1849 ---- accum A) -- Runtime Function: unsigned short accum __fractusauha2 (unsigned accum A) ! -- Runtime Function: unsigned long accum __fractusauda2 (unsigned ! accum A) -- Runtime Function: unsigned long long accum __fractusauta2 (unsigned accum A) -- Runtime Function: signed char __fractusaqi (unsigned accum A) *************** returned result using either signed or u *** 1868,1877 **** accum A) -- Runtime Function: unsigned long long fract __fractudaudq (unsigned long accum A) ! -- Runtime Function: unsigned short accum __fractudauha2 (unsigned long accum A) - -- Runtime Function: unsigned accum __fractudausa2 (unsigned long accum - A) -- Runtime Function: unsigned long long accum __fractudauta2 (unsigned long accum A) -- Runtime Function: signed char __fractudaqi (unsigned long accum A) --- 1871,1880 ---- accum A) -- Runtime Function: unsigned long long fract __fractudaudq (unsigned long accum A) ! -- Runtime Function: unsigned short accum __fractudauha2 (unsigned ! long accum A) ! -- Runtime Function: unsigned accum __fractudausa2 (unsigned long accum A) -- Runtime Function: unsigned long long accum __fractudauta2 (unsigned long accum A) -- Runtime Function: signed char __fractudaqi (unsigned long accum A) *************** returned result using either signed or u *** 1881,1895 **** -- Runtime Function: long long __fractudati (unsigned long accum A) -- Runtime Function: float __fractudasf (unsigned long accum A) -- Runtime Function: double __fractudadf (unsigned long accum A) ! -- Runtime Function: short fract __fractutaqq (unsigned long long accum ! A) -- Runtime Function: fract __fractutahq (unsigned long long accum A) -- Runtime Function: long fract __fractutasq (unsigned long long accum A) -- Runtime Function: long long fract __fractutadq (unsigned long long accum A) ! -- Runtime Function: short accum __fractutaha (unsigned long long accum ! A) -- Runtime Function: accum __fractutasa (unsigned long long accum A) -- Runtime Function: long accum __fractutada (unsigned long long accum A) --- 1884,1898 ---- -- Runtime Function: long long __fractudati (unsigned long accum A) -- Runtime Function: float __fractudasf (unsigned long accum A) -- Runtime Function: double __fractudadf (unsigned long accum A) ! -- Runtime Function: short fract __fractutaqq (unsigned long long ! accum A) -- Runtime Function: fract __fractutahq (unsigned long long accum A) -- Runtime Function: long fract __fractutasq (unsigned long long accum A) -- Runtime Function: long long fract __fractutadq (unsigned long long accum A) ! -- Runtime Function: short accum __fractutaha (unsigned long long ! accum A) -- Runtime Function: accum __fractutasa (unsigned long long accum A) -- Runtime Function: long accum __fractutada (unsigned long long accum A) *************** returned result using either signed or u *** 1903,1916 **** long accum A) -- Runtime Function: unsigned long long fract __fractutaudq (unsigned long long accum A) ! -- Runtime Function: unsigned short accum __fractutauha2 (unsigned long ! long accum A) -- Runtime Function: unsigned accum __fractutausa2 (unsigned long long accum A) -- Runtime Function: unsigned long accum __fractutauda2 (unsigned long long accum A) ! -- Runtime Function: signed char __fractutaqi (unsigned long long accum ! A) -- Runtime Function: short __fractutahi (unsigned long long accum A) -- Runtime Function: int __fractutasi (unsigned long long accum A) -- Runtime Function: long __fractutadi (unsigned long long accum A) --- 1906,1919 ---- long accum A) -- Runtime Function: unsigned long long fract __fractutaudq (unsigned long long accum A) ! -- Runtime Function: unsigned short accum __fractutauha2 (unsigned ! long long accum A) -- Runtime Function: unsigned accum __fractutausa2 (unsigned long long accum A) -- Runtime Function: unsigned long accum __fractutauda2 (unsigned long long accum A) ! -- Runtime Function: signed char __fractutaqi (unsigned long long ! accum A) -- Runtime Function: short __fractutahi (unsigned long long accum A) -- Runtime Function: int __fractutasi (unsigned long long accum A) -- Runtime Function: long __fractutadi (unsigned long long accum A) *************** returned result using either signed or u *** 1929,1941 **** -- Runtime Function: unsigned short fract __fractqiuqq (signed char A) -- Runtime Function: unsigned fract __fractqiuhq (signed char A) -- Runtime Function: unsigned long fract __fractqiusq (signed char A) ! -- Runtime Function: unsigned long long fract __fractqiudq (signed char ! A) -- Runtime Function: unsigned short accum __fractqiuha (signed char A) -- Runtime Function: unsigned accum __fractqiusa (signed char A) -- Runtime Function: unsigned long accum __fractqiuda (signed char A) ! -- Runtime Function: unsigned long long accum __fractqiuta (signed char ! A) -- Runtime Function: short fract __fracthiqq (short A) -- Runtime Function: fract __fracthihq (short A) -- Runtime Function: long fract __fracthisq (short A) --- 1932,1944 ---- -- Runtime Function: unsigned short fract __fractqiuqq (signed char A) -- Runtime Function: unsigned fract __fractqiuhq (signed char A) -- Runtime Function: unsigned long fract __fractqiusq (signed char A) ! -- Runtime Function: unsigned long long fract __fractqiudq (signed ! char A) -- Runtime Function: unsigned short accum __fractqiuha (signed char A) -- Runtime Function: unsigned accum __fractqiusa (signed char A) -- Runtime Function: unsigned long accum __fractqiuda (signed char A) ! -- Runtime Function: unsigned long long accum __fractqiuta (signed ! char A) -- Runtime Function: short fract __fracthiqq (short A) -- Runtime Function: fract __fracthihq (short A) -- Runtime Function: long fract __fracthisq (short A) *************** returned result using either signed or u *** 2539,2546 **** -- Runtime Function: unsigned short __fractunsdqhi (long long fract A) -- Runtime Function: unsigned int __fractunsdqsi (long long fract A) -- Runtime Function: unsigned long __fractunsdqdi (long long fract A) ! -- Runtime Function: unsigned long long __fractunsdqti (long long fract ! A) -- Runtime Function: unsigned char __fractunshaqi (short accum A) -- Runtime Function: unsigned short __fractunshahi (short accum A) -- Runtime Function: unsigned int __fractunshasi (short accum A) --- 2542,2549 ---- -- Runtime Function: unsigned short __fractunsdqhi (long long fract A) -- Runtime Function: unsigned int __fractunsdqsi (long long fract A) -- Runtime Function: unsigned long __fractunsdqdi (long long fract A) ! -- Runtime Function: unsigned long long __fractunsdqti (long long ! fract A) -- Runtime Function: unsigned char __fractunshaqi (short accum A) -- Runtime Function: unsigned short __fractunshahi (short accum A) -- Runtime Function: unsigned int __fractunshasi (short accum A) *************** returned result using either signed or u *** 2560,2597 **** -- Runtime Function: unsigned short __fractunstahi (long long accum A) -- Runtime Function: unsigned int __fractunstasi (long long accum A) -- Runtime Function: unsigned long __fractunstadi (long long accum A) ! -- Runtime Function: unsigned long long __fractunstati (long long accum ! A) -- Runtime Function: unsigned char __fractunsuqqqi (unsigned short fract A) -- Runtime Function: unsigned short __fractunsuqqhi (unsigned short fract A) ! -- Runtime Function: unsigned int __fractunsuqqsi (unsigned short fract ! A) ! -- Runtime Function: unsigned long __fractunsuqqdi (unsigned short fract A) ! -- Runtime Function: unsigned long long __fractunsuqqti (unsigned short fract A) -- Runtime Function: unsigned char __fractunsuhqqi (unsigned fract A) -- Runtime Function: unsigned short __fractunsuhqhi (unsigned fract A) -- Runtime Function: unsigned int __fractunsuhqsi (unsigned fract A) -- Runtime Function: unsigned long __fractunsuhqdi (unsigned fract A) ! -- Runtime Function: unsigned long long __fractunsuhqti (unsigned fract ! A) ! -- Runtime Function: unsigned char __fractunsusqqi (unsigned long fract ! A) -- Runtime Function: unsigned short __fractunsusqhi (unsigned long fract A) -- Runtime Function: unsigned int __fractunsusqsi (unsigned long fract A) ! -- Runtime Function: unsigned long __fractunsusqdi (unsigned long fract ! A) -- Runtime Function: unsigned long long __fractunsusqti (unsigned long fract A) -- Runtime Function: unsigned char __fractunsudqqi (unsigned long long fract A) ! -- Runtime Function: unsigned short __fractunsudqhi (unsigned long long ! fract A) -- Runtime Function: unsigned int __fractunsudqsi (unsigned long long fract A) -- Runtime Function: unsigned long __fractunsudqdi (unsigned long long --- 2563,2600 ---- -- Runtime Function: unsigned short __fractunstahi (long long accum A) -- Runtime Function: unsigned int __fractunstasi (long long accum A) -- Runtime Function: unsigned long __fractunstadi (long long accum A) ! -- Runtime Function: unsigned long long __fractunstati (long long ! accum A) -- Runtime Function: unsigned char __fractunsuqqqi (unsigned short fract A) -- Runtime Function: unsigned short __fractunsuqqhi (unsigned short fract A) ! -- Runtime Function: unsigned int __fractunsuqqsi (unsigned short fract A) ! -- Runtime Function: unsigned long __fractunsuqqdi (unsigned short fract A) + -- Runtime Function: unsigned long long __fractunsuqqti (unsigned + short fract A) -- Runtime Function: unsigned char __fractunsuhqqi (unsigned fract A) -- Runtime Function: unsigned short __fractunsuhqhi (unsigned fract A) -- Runtime Function: unsigned int __fractunsuhqsi (unsigned fract A) -- Runtime Function: unsigned long __fractunsuhqdi (unsigned fract A) ! -- Runtime Function: unsigned long long __fractunsuhqti (unsigned ! fract A) ! -- Runtime Function: unsigned char __fractunsusqqi (unsigned long ! fract A) -- Runtime Function: unsigned short __fractunsusqhi (unsigned long fract A) -- Runtime Function: unsigned int __fractunsusqsi (unsigned long fract A) ! -- Runtime Function: unsigned long __fractunsusqdi (unsigned long ! fract A) -- Runtime Function: unsigned long long __fractunsusqti (unsigned long fract A) -- Runtime Function: unsigned char __fractunsudqqi (unsigned long long fract A) ! -- Runtime Function: unsigned short __fractunsudqhi (unsigned long ! long fract A) -- Runtime Function: unsigned int __fractunsudqsi (unsigned long long fract A) -- Runtime Function: unsigned long __fractunsudqdi (unsigned long long *************** returned result using either signed or u *** 2602,2633 **** accum A) -- Runtime Function: unsigned short __fractunsuhahi (unsigned short accum A) ! -- Runtime Function: unsigned int __fractunsuhasi (unsigned short accum ! A) ! -- Runtime Function: unsigned long __fractunsuhadi (unsigned short accum A) ! -- Runtime Function: unsigned long long __fractunsuhati (unsigned short accum A) -- Runtime Function: unsigned char __fractunsusaqi (unsigned accum A) -- Runtime Function: unsigned short __fractunsusahi (unsigned accum A) -- Runtime Function: unsigned int __fractunsusasi (unsigned accum A) -- Runtime Function: unsigned long __fractunsusadi (unsigned accum A) ! -- Runtime Function: unsigned long long __fractunsusati (unsigned accum ! A) ! -- Runtime Function: unsigned char __fractunsudaqi (unsigned long accum ! A) -- Runtime Function: unsigned short __fractunsudahi (unsigned long accum A) -- Runtime Function: unsigned int __fractunsudasi (unsigned long accum A) ! -- Runtime Function: unsigned long __fractunsudadi (unsigned long accum ! A) -- Runtime Function: unsigned long long __fractunsudati (unsigned long accum A) -- Runtime Function: unsigned char __fractunsutaqi (unsigned long long accum A) ! -- Runtime Function: unsigned short __fractunsutahi (unsigned long long ! accum A) -- Runtime Function: unsigned int __fractunsutasi (unsigned long long accum A) -- Runtime Function: unsigned long __fractunsutadi (unsigned long long --- 2605,2636 ---- accum A) -- Runtime Function: unsigned short __fractunsuhahi (unsigned short accum A) ! -- Runtime Function: unsigned int __fractunsuhasi (unsigned short accum A) ! -- Runtime Function: unsigned long __fractunsuhadi (unsigned short accum A) + -- Runtime Function: unsigned long long __fractunsuhati (unsigned + short accum A) -- Runtime Function: unsigned char __fractunsusaqi (unsigned accum A) -- Runtime Function: unsigned short __fractunsusahi (unsigned accum A) -- Runtime Function: unsigned int __fractunsusasi (unsigned accum A) -- Runtime Function: unsigned long __fractunsusadi (unsigned accum A) ! -- Runtime Function: unsigned long long __fractunsusati (unsigned ! accum A) ! -- Runtime Function: unsigned char __fractunsudaqi (unsigned long ! accum A) -- Runtime Function: unsigned short __fractunsudahi (unsigned long accum A) -- Runtime Function: unsigned int __fractunsudasi (unsigned long accum A) ! -- Runtime Function: unsigned long __fractunsudadi (unsigned long ! accum A) -- Runtime Function: unsigned long long __fractunsudati (unsigned long accum A) -- Runtime Function: unsigned char __fractunsutaqi (unsigned long long accum A) ! -- Runtime Function: unsigned short __fractunsutahi (unsigned long ! long accum A) -- Runtime Function: unsigned int __fractunsutasi (unsigned long long accum A) -- Runtime Function: unsigned long __fractunsutadi (unsigned long long *************** returned result using either signed or u *** 2645,2661 **** -- Runtime Function: unsigned short fract __fractunsqiuqq (unsigned char A) -- Runtime Function: unsigned fract __fractunsqiuhq (unsigned char A) ! -- Runtime Function: unsigned long fract __fractunsqiusq (unsigned char ! A) ! -- Runtime Function: unsigned long long fract __fractunsqiudq (unsigned char A) -- Runtime Function: unsigned short accum __fractunsqiuha (unsigned char A) -- Runtime Function: unsigned accum __fractunsqiusa (unsigned char A) ! -- Runtime Function: unsigned long accum __fractunsqiuda (unsigned char ! A) ! -- Runtime Function: unsigned long long accum __fractunsqiuta (unsigned char A) -- Runtime Function: short fract __fractunshiqq (unsigned short A) -- Runtime Function: fract __fractunshihq (unsigned short A) -- Runtime Function: long fract __fractunshisq (unsigned short A) --- 2648,2664 ---- -- Runtime Function: unsigned short fract __fractunsqiuqq (unsigned char A) -- Runtime Function: unsigned fract __fractunsqiuhq (unsigned char A) ! -- Runtime Function: unsigned long fract __fractunsqiusq (unsigned char A) + -- Runtime Function: unsigned long long fract __fractunsqiudq + (unsigned char A) -- Runtime Function: unsigned short accum __fractunsqiuha (unsigned char A) -- Runtime Function: unsigned accum __fractunsqiusa (unsigned char A) ! -- Runtime Function: unsigned long accum __fractunsqiuda (unsigned char A) + -- Runtime Function: unsigned long long accum __fractunsqiuta + (unsigned char A) -- Runtime Function: short fract __fractunshiqq (unsigned short A) -- Runtime Function: fract __fractunshihq (unsigned short A) -- Runtime Function: long fract __fractunshisq (unsigned short A) *************** returned result using either signed or u *** 2669,2683 **** -- Runtime Function: unsigned fract __fractunshiuhq (unsigned short A) -- Runtime Function: unsigned long fract __fractunshiusq (unsigned short A) ! -- Runtime Function: unsigned long long fract __fractunshiudq (unsigned ! short A) -- Runtime Function: unsigned short accum __fractunshiuha (unsigned short A) -- Runtime Function: unsigned accum __fractunshiusa (unsigned short A) -- Runtime Function: unsigned long accum __fractunshiuda (unsigned short A) ! -- Runtime Function: unsigned long long accum __fractunshiuta (unsigned ! short A) -- Runtime Function: short fract __fractunssiqq (unsigned int A) -- Runtime Function: fract __fractunssihq (unsigned int A) -- Runtime Function: long fract __fractunssisq (unsigned int A) --- 2672,2686 ---- -- Runtime Function: unsigned fract __fractunshiuhq (unsigned short A) -- Runtime Function: unsigned long fract __fractunshiusq (unsigned short A) ! -- Runtime Function: unsigned long long fract __fractunshiudq ! (unsigned short A) -- Runtime Function: unsigned short accum __fractunshiuha (unsigned short A) -- Runtime Function: unsigned accum __fractunshiusa (unsigned short A) -- Runtime Function: unsigned long accum __fractunshiuda (unsigned short A) ! -- Runtime Function: unsigned long long accum __fractunshiuta ! (unsigned short A) -- Runtime Function: short fract __fractunssiqq (unsigned int A) -- Runtime Function: fract __fractunssihq (unsigned int A) -- Runtime Function: long fract __fractunssisq (unsigned int A) *************** returned result using either signed or u *** 2686,2705 **** -- Runtime Function: accum __fractunssisa (unsigned int A) -- Runtime Function: long accum __fractunssida (unsigned int A) -- Runtime Function: long long accum __fractunssita (unsigned int A) ! -- Runtime Function: unsigned short fract __fractunssiuqq (unsigned int ! A) -- Runtime Function: unsigned fract __fractunssiuhq (unsigned int A) -- Runtime Function: unsigned long fract __fractunssiusq (unsigned int A) ! -- Runtime Function: unsigned long long fract __fractunssiudq (unsigned int A) - -- Runtime Function: unsigned short accum __fractunssiuha (unsigned int - A) -- Runtime Function: unsigned accum __fractunssiusa (unsigned int A) -- Runtime Function: unsigned long accum __fractunssiuda (unsigned int A) ! -- Runtime Function: unsigned long long accum __fractunssiuta (unsigned ! int A) -- Runtime Function: short fract __fractunsdiqq (unsigned long A) -- Runtime Function: fract __fractunsdihq (unsigned long A) -- Runtime Function: long fract __fractunsdisq (unsigned long A) --- 2689,2708 ---- -- Runtime Function: accum __fractunssisa (unsigned int A) -- Runtime Function: long accum __fractunssida (unsigned int A) -- Runtime Function: long long accum __fractunssita (unsigned int A) ! -- Runtime Function: unsigned short fract __fractunssiuqq (unsigned ! int A) -- Runtime Function: unsigned fract __fractunssiuhq (unsigned int A) -- Runtime Function: unsigned long fract __fractunssiusq (unsigned int A) ! -- Runtime Function: unsigned long long fract __fractunssiudq ! (unsigned int A) ! -- Runtime Function: unsigned short accum __fractunssiuha (unsigned int A) -- Runtime Function: unsigned accum __fractunssiusa (unsigned int A) -- Runtime Function: unsigned long accum __fractunssiuda (unsigned int A) ! -- Runtime Function: unsigned long long accum __fractunssiuta ! (unsigned int A) -- Runtime Function: short fract __fractunsdiqq (unsigned long A) -- Runtime Function: fract __fractunsdihq (unsigned long A) -- Runtime Function: long fract __fractunsdisq (unsigned long A) *************** returned result using either signed or u *** 2711,2753 **** -- Runtime Function: unsigned short fract __fractunsdiuqq (unsigned long A) -- Runtime Function: unsigned fract __fractunsdiuhq (unsigned long A) ! -- Runtime Function: unsigned long fract __fractunsdiusq (unsigned long ! A) ! -- Runtime Function: unsigned long long fract __fractunsdiudq (unsigned long A) -- Runtime Function: unsigned short accum __fractunsdiuha (unsigned long A) -- Runtime Function: unsigned accum __fractunsdiusa (unsigned long A) ! -- Runtime Function: unsigned long accum __fractunsdiuda (unsigned long ! A) ! -- Runtime Function: unsigned long long accum __fractunsdiuta (unsigned long A) -- Runtime Function: short fract __fractunstiqq (unsigned long long A) -- Runtime Function: fract __fractunstihq (unsigned long long A) -- Runtime Function: long fract __fractunstisq (unsigned long long A) ! -- Runtime Function: long long fract __fractunstidq (unsigned long long ! A) -- Runtime Function: short accum __fractunstiha (unsigned long long A) -- Runtime Function: accum __fractunstisa (unsigned long long A) -- Runtime Function: long accum __fractunstida (unsigned long long A) ! -- Runtime Function: long long accum __fractunstita (unsigned long long ! A) -- Runtime Function: unsigned short fract __fractunstiuqq (unsigned long long A) ! -- Runtime Function: unsigned fract __fractunstiuhq (unsigned long long ! A) ! -- Runtime Function: unsigned long fract __fractunstiusq (unsigned long long A) ! -- Runtime Function: unsigned long long fract __fractunstiudq (unsigned long long A) -- Runtime Function: unsigned short accum __fractunstiuha (unsigned long long A) ! -- Runtime Function: unsigned accum __fractunstiusa (unsigned long long ! A) ! -- Runtime Function: unsigned long accum __fractunstiuda (unsigned long long A) ! -- Runtime Function: unsigned long long accum __fractunstiuta (unsigned long long A) These functions convert from fractionals to unsigned non-fractionals; and from unsigned non-fractionals to fractionals, without saturation. --- 2714,2756 ---- -- Runtime Function: unsigned short fract __fractunsdiuqq (unsigned long A) -- Runtime Function: unsigned fract __fractunsdiuhq (unsigned long A) ! -- Runtime Function: unsigned long fract __fractunsdiusq (unsigned long A) + -- Runtime Function: unsigned long long fract __fractunsdiudq + (unsigned long A) -- Runtime Function: unsigned short accum __fractunsdiuha (unsigned long A) -- Runtime Function: unsigned accum __fractunsdiusa (unsigned long A) ! -- Runtime Function: unsigned long accum __fractunsdiuda (unsigned long A) + -- Runtime Function: unsigned long long accum __fractunsdiuta + (unsigned long A) -- Runtime Function: short fract __fractunstiqq (unsigned long long A) -- Runtime Function: fract __fractunstihq (unsigned long long A) -- Runtime Function: long fract __fractunstisq (unsigned long long A) ! -- Runtime Function: long long fract __fractunstidq (unsigned long ! long A) -- Runtime Function: short accum __fractunstiha (unsigned long long A) -- Runtime Function: accum __fractunstisa (unsigned long long A) -- Runtime Function: long accum __fractunstida (unsigned long long A) ! -- Runtime Function: long long accum __fractunstita (unsigned long ! long A) -- Runtime Function: unsigned short fract __fractunstiuqq (unsigned long long A) ! -- Runtime Function: unsigned fract __fractunstiuhq (unsigned long long A) ! -- Runtime Function: unsigned long fract __fractunstiusq (unsigned long long A) + -- Runtime Function: unsigned long long fract __fractunstiudq + (unsigned long long A) -- Runtime Function: unsigned short accum __fractunstiuha (unsigned long long A) ! -- Runtime Function: unsigned accum __fractunstiusa (unsigned long long A) ! -- Runtime Function: unsigned long accum __fractunstiuda (unsigned long long A) + -- Runtime Function: unsigned long long accum __fractunstiuta + (unsigned long long A) These functions convert from fractionals to unsigned non-fractionals; and from unsigned non-fractionals to fractionals, without saturation. *************** File: gccint.info, Node: Miscellaneous *** 2940,2946 **** -- Runtime Function: void * __splitstack_find (void *SEGMENT_ARG, void *SP, size_t LEN, void **NEXT_SEGMENT, void **NEXT_SP, void **INITIAL_SP) ! When using '-fsplit-stack', this call may be used to iterate over the stack segments. It may be called like this: void *next_segment = NULL; void *next_sp = NULL; --- 2943,2949 ---- -- Runtime Function: void * __splitstack_find (void *SEGMENT_ARG, void *SP, size_t LEN, void **NEXT_SEGMENT, void **NEXT_SP, void **INITIAL_SP) ! When using `-fsplit-stack', this call may be used to iterate over the stack segments. It may be called like this: void *next_segment = NULL; void *next_sp = NULL; *************** File: gccint.info, Node: Miscellaneous *** 2961,2975 **** with the SEGMENT_ARG and SP arguments NULL, to pass NEXT_SEGMENT, NEXT_SP, and INITIAL_SP to a different thread, and then to suspend one way or another. A different thread may run the subsequent ! '__splitstack_find' iterations. Of course, this will only work if the first thread is suspended while the second thread is calling ! '__splitstack_find'. If not, the second thread could be looking at ! the stack while it is changing, and anything could happen. -- Variable: __morestack_segments -- Variable: __morestack_current_segment -- Variable: __morestack_initial_sp ! Internal variables used by the '-fsplit-stack' implementation.  File: gccint.info, Node: Languages, Next: Source Tree, Prev: Libgcc, Up: Top --- 2964,2978 ---- with the SEGMENT_ARG and SP arguments NULL, to pass NEXT_SEGMENT, NEXT_SP, and INITIAL_SP to a different thread, and then to suspend one way or another. A different thread may run the subsequent ! `__splitstack_find' iterations. Of course, this will only work if the first thread is suspended while the second thread is calling ! `__splitstack_find'. If not, the second thread could be looking ! at the stack while it is changing, and anything could happen. -- Variable: __morestack_segments -- Variable: __morestack_current_segment -- Variable: __morestack_initial_sp ! Internal variables used by the `-fsplit-stack' implementation.  File: gccint.info, Node: Languages, Next: Source Tree, Prev: Libgcc, Up: Top *************** File: gccint.info, Node: Languages, Ne *** 2978,2984 **** **************************** The interface to front ends for languages in GCC, and in particular the ! 'tree' structure (*note GENERIC::), was initially designed for C, and many aspects of it are still somewhat biased towards C and C-like languages. It is, however, reasonably well suited to other procedural languages, and front ends for many such languages have been written for --- 2981,2987 ---- **************************** The interface to front ends for languages in GCC, and in particular the ! `tree' structure (*note GENERIC::), was initially designed for C, and many aspects of it are still somewhat biased towards C and C-like languages. It is, however, reasonably well suited to other procedural languages, and front ends for many such languages have been written for *************** GCC, has several advantages: *** 2990,3004 **** * GCC front ends benefit from the support for many different target machines already present in GCC. * GCC front ends benefit from all the optimizations in GCC. Some of these, such as alias analysis, may work better when GCC is compiling directly from source code then when it is compiling from generated C code. * Better debugging information is generated when compiling directly from source code than when going via intermediate generated C code. ! Because of the advantages of writing a compiler as a GCC front end, GCC ! front ends have also been created for languages very different from those for which GCC was designed, such as the declarative logic/functional language Mercury. For these reasons, it may also be useful to implement compilers created for specialized purposes (for --- 2993,3009 ---- * GCC front ends benefit from the support for many different target machines already present in GCC. + * GCC front ends benefit from all the optimizations in GCC. Some of these, such as alias analysis, may work better when GCC is compiling directly from source code then when it is compiling from generated C code. + * Better debugging information is generated when compiling directly from source code than when going via intermediate generated C code. ! Because of the advantages of writing a compiler as a GCC front end, ! GCC front ends have also been created for languages very different from those for which GCC was designed, such as the declarative logic/functional language Mercury. For these reasons, it may also be useful to implement compilers created for specialized purposes (for *************** File: gccint.info, Node: Source Tree, *** 3010,3025 **** 6 Source Tree Structure and Build System **************************************** ! This chapter describes the structure of the GCC source tree, and how GCC ! is built. The user documentation for building and installing GCC is in ! a separate manual (), with which it is ! presumed that you are familiar. * Menu: * Configure Terms:: Configuration terminology and history. * Top Level:: The top level source directory. ! * gcc Directory:: The 'gcc' subdirectory.  File: gccint.info, Node: Configure Terms, Next: Top Level, Up: Source Tree --- 3015,3030 ---- 6 Source Tree Structure and Build System **************************************** ! This chapter describes the structure of the GCC source tree, and how ! GCC is built. The user documentation for building and installing GCC ! is in a separate manual (`http://gcc.gnu.org/install/'), with which it ! is presumed that you are familiar. * Menu: * Configure Terms:: Configuration terminology and history. * Top Level:: The top level source directory. ! * gcc Directory:: The `gcc' subdirectory.  File: gccint.info, Node: Configure Terms, Next: Top Level, Up: Source Tree *************** know. *** 3036,3081 **** There are three system names that the build knows about: the machine you are building on ("build"), the machine that you are building for ("host"), and the machine that GCC will produce code for ("target"). ! When you configure GCC, you specify these with '--build=', '--host=', ! and '--target='. Specifying the host without specifying the build should be avoided, as ! 'configure' may (and once did) assume that the host you specify is also the build, which may not be true. ! If build, host, and target are all the same, this is called a "native". ! If build and host are the same but target is different, this is called a ! "cross". If build, host, and target are all different this is called a ! "canadian" (for obscure reasons dealing with Canada's political party ! and the background of the person working on the build at that time). If ! host and target are the same, but build is different, you are using a ! cross-compiler to build a native for a different system. Some people ! call this a "host-x-host", "crossed native", or "cross-built native". ! If build and target are the same, but host is different, you are using a ! cross compiler to build a cross compiler that produces code for the ! machine you're building on. This is rare, so there is no common way of ! describing it. There is a proposal to call this a "crossback". If build and host are the same, the GCC you are building will also be ! used to build the target libraries (like 'libstdc++'). If build and host are different, you must have already built and installed a cross compiler that will be used to build the target libraries (if you ! configured with '--target=foo-bar', this compiler will be called ! 'foo-bar-gcc'). In the case of target libraries, the machine you're building for is the ! machine you specified with '--target'. So, build is the machine you're building on (no change there), host is the machine you're building for (the target libraries are built for the target, so host is the target you specified), and target doesn't apply (because you're not building a compiler, you're building libraries). The configure/make process will ! adjust these variables as needed. It also sets '$with_cross_host' to ! the original '--host' value in case you need it. ! The 'libiberty' support library is built up to three times: once for the host, once for the target (even if they are the same), and once for ! the build if build and host are different. This allows it to be used by ! all programs which are generated in the course of the build process.  File: gccint.info, Node: Top Level, Next: gcc Directory, Prev: Configure Terms, Up: Source Tree --- 3041,3087 ---- There are three system names that the build knows about: the machine you are building on ("build"), the machine that you are building for ("host"), and the machine that GCC will produce code for ("target"). ! When you configure GCC, you specify these with `--build=', `--host=', ! and `--target='. Specifying the host without specifying the build should be avoided, as ! `configure' may (and once did) assume that the host you specify is also the build, which may not be true. ! If build, host, and target are all the same, this is called a ! "native". If build and host are the same but target is different, this ! is called a "cross". If build, host, and target are all different this ! is called a "canadian" (for obscure reasons dealing with Canada's ! political party and the background of the person working on the build ! at that time). If host and target are the same, but build is ! different, you are using a cross-compiler to build a native for a ! different system. Some people call this a "host-x-host", "crossed ! native", or "cross-built native". If build and target are the same, ! but host is different, you are using a cross compiler to build a cross ! compiler that produces code for the machine you're building on. This ! is rare, so there is no common way of describing it. There is a ! proposal to call this a "crossback". If build and host are the same, the GCC you are building will also be ! used to build the target libraries (like `libstdc++'). If build and host are different, you must have already built and installed a cross compiler that will be used to build the target libraries (if you ! configured with `--target=foo-bar', this compiler will be called ! `foo-bar-gcc'). In the case of target libraries, the machine you're building for is the ! machine you specified with `--target'. So, build is the machine you're building on (no change there), host is the machine you're building for (the target libraries are built for the target, so host is the target you specified), and target doesn't apply (because you're not building a compiler, you're building libraries). The configure/make process will ! adjust these variables as needed. It also sets `$with_cross_host' to ! the original `--host' value in case you need it. ! The `libiberty' support library is built up to three times: once for the host, once for the target (even if they are the same), and once for ! the build if build and host are different. This allows it to be used ! by all programs which are generated in the course of the build process.  File: gccint.info, Node: Top Level, Next: gcc Directory, Prev: Configure Terms, Up: Source Tree *************** files and directories that are shared wi *** 3088,3217 **** such as that of GNU Binutils. It also contains several subdirectories that contain parts of GCC and its runtime libraries: ! 'boehm-gc' The Boehm conservative garbage collector, used as part of the Java runtime library. ! 'config' Autoconf macros and Makefile fragments used throughout the tree. ! 'contrib' Contributed scripts that may be found useful in conjunction with ! GCC. One of these, 'contrib/texi2pod.pl', is used to generate man pages from Texinfo manuals as part of the GCC build process. ! 'fixincludes' The support for fixing system headers to work with GCC. See ! 'fixincludes/README' for more information. The headers fixed by ! this mechanism are installed in 'LIBSUBDIR/include-fixed'. Along ! with those headers, 'README-fixinc' is also installed, as ! 'LIBSUBDIR/include-fixed/README'. ! 'gcc' The main sources of GCC itself (except for runtime libraries), including optimizers, support for different target architectures, ! language front ends, and testsuites. *Note The 'gcc' Subdirectory: ! gcc Directory, for details. ! 'gnattools' Support tools for GNAT. ! 'include' ! Headers for the 'libiberty' library. ! 'intl' ! GNU 'libintl', from GNU 'gettext', for systems which do not include ! it in 'libc'. ! 'libada' The Ada runtime library. ! 'libatomic' ! The runtime support library for atomic operations (e.g. for ! '__sync' and '__atomic'). ! 'libcpp' The C preprocessor library. ! 'libdecnumber' The Decimal Float support library. ! 'libffi' ! The 'libffi' library, used as part of the Java runtime library. ! 'libgcc' The GCC runtime library. ! 'libgfortran' The Fortran runtime library. ! 'libgo' The Go runtime library. The bulk of this library is mirrored from the master Go repository (http://code.google.com/p/go/). ! 'libgomp' The GNU Offloading and Multi Processing Runtime Library. ! 'libiberty' ! The 'libiberty' library, used for portability and for some generally useful data structures and algorithms. *Note Introduction: (libiberty)Top, for more information about this library. ! 'libitm' The runtime support library for transactional memory. ! 'libjava' The Java runtime library. ! 'libobjc' The Objective-C and Objective-C++ runtime library. ! 'libquadmath' The runtime support library for quad-precision math operations. ! 'libssp' The Stack protector runtime library. ! 'libstdc++-v3' The C++ runtime library. ! 'lto-plugin' Plugin used by the linker if link-time optimizations are enabled. ! 'maintainer-scripts' ! Scripts used by the 'gccadmin' account on 'gcc.gnu.org'. ! 'zlib' ! The 'zlib' compression library, used by the Java front end, as part ! of the Java runtime library, and for compressing and uncompressing ! GCC's intermediate language in LTO object files. The build system in the top level directory, including how recursion into subdirectories works and how building runtime libraries for multilibs is handled, is documented in a separate manual, included with ! GNU Binutils. *Note GNU configure and build system: (configure)Top, for ! details.  File: gccint.info, Node: gcc Directory, Prev: Top Level, Up: Source Tree ! 6.3 The 'gcc' Subdirectory ========================== ! The 'gcc' directory contains many files that are part of the C sources ! of GCC, other files used as part of the configuration and build process, ! and subdirectories including documentation and a testsuite. The files ! that are sources of GCC are documented in a separate chapter. *Note ! Passes and Files of the Compiler: Passes. * Menu: ! * Subdirectories:: Subdirectories of 'gcc'. * Configuration:: The configuration process, and the files it uses. ! * Build:: The build system in the 'gcc' directory. ! * Makefile:: Targets in 'gcc/Makefile'. ! * Library Files:: Library source files and headers under 'gcc/'. * Headers:: Headers installed by GCC. * Documentation:: Building documentation in GCC. * Front End:: Anatomy of a language front end. --- 3094,3223 ---- such as that of GNU Binutils. It also contains several subdirectories that contain parts of GCC and its runtime libraries: ! `boehm-gc' The Boehm conservative garbage collector, used as part of the Java runtime library. ! `config' Autoconf macros and Makefile fragments used throughout the tree. ! `contrib' Contributed scripts that may be found useful in conjunction with ! GCC. One of these, `contrib/texi2pod.pl', is used to generate man pages from Texinfo manuals as part of the GCC build process. ! `fixincludes' The support for fixing system headers to work with GCC. See ! `fixincludes/README' for more information. The headers fixed by ! this mechanism are installed in `LIBSUBDIR/include-fixed'. Along ! with those headers, `README-fixinc' is also installed, as ! `LIBSUBDIR/include-fixed/README'. ! `gcc' The main sources of GCC itself (except for runtime libraries), including optimizers, support for different target architectures, ! language front ends, and testsuites. *Note The `gcc' ! Subdirectory: gcc Directory, for details. ! `gnattools' Support tools for GNAT. ! `include' ! Headers for the `libiberty' library. ! `intl' ! GNU `libintl', from GNU `gettext', for systems which do not ! include it in `libc'. ! `libada' The Ada runtime library. ! `libatomic' ! The runtime support library for atomic operations (e.g. for ! `__sync' and `__atomic'). ! `libcpp' The C preprocessor library. ! `libdecnumber' The Decimal Float support library. ! `libffi' ! The `libffi' library, used as part of the Java runtime library. ! `libgcc' The GCC runtime library. ! `libgfortran' The Fortran runtime library. ! `libgo' The Go runtime library. The bulk of this library is mirrored from the master Go repository (http://code.google.com/p/go/). ! `libgomp' The GNU Offloading and Multi Processing Runtime Library. ! `libiberty' ! The `libiberty' library, used for portability and for some generally useful data structures and algorithms. *Note Introduction: (libiberty)Top, for more information about this library. ! `libitm' The runtime support library for transactional memory. ! `libjava' The Java runtime library. ! `libobjc' The Objective-C and Objective-C++ runtime library. ! `libquadmath' The runtime support library for quad-precision math operations. ! `libssp' The Stack protector runtime library. ! `libstdc++-v3' The C++ runtime library. ! `lto-plugin' Plugin used by the linker if link-time optimizations are enabled. ! `maintainer-scripts' ! Scripts used by the `gccadmin' account on `gcc.gnu.org'. ! `zlib' ! The `zlib' compression library, used by the Java front end, as ! part of the Java runtime library, and for compressing and ! uncompressing GCC's intermediate language in LTO object files. The build system in the top level directory, including how recursion into subdirectories works and how building runtime libraries for multilibs is handled, is documented in a separate manual, included with ! GNU Binutils. *Note GNU configure and build system: (configure)Top, ! for details.  File: gccint.info, Node: gcc Directory, Prev: Top Level, Up: Source Tree ! 6.3 The `gcc' Subdirectory ========================== ! The `gcc' directory contains many files that are part of the C sources ! of GCC, other files used as part of the configuration and build ! process, and subdirectories including documentation and a testsuite. ! The files that are sources of GCC are documented in a separate chapter. ! *Note Passes and Files of the Compiler: Passes. * Menu: ! * Subdirectories:: Subdirectories of `gcc'. * Configuration:: The configuration process, and the files it uses. ! * Build:: The build system in the `gcc' directory. ! * Makefile:: Targets in `gcc/Makefile'. ! * Library Files:: Library source files and headers under `gcc/'. * Headers:: Headers installed by GCC. * Documentation:: Building documentation in GCC. * Front End:: Anatomy of a language front end. *************** Passes and Files of the Compiler: Passes *** 3220,3340 ****  File: gccint.info, Node: Subdirectories, Next: Configuration, Up: gcc Directory ! 6.3.1 Subdirectories of 'gcc' ----------------------------- ! The 'gcc' directory contains the following subdirectories: ! 'LANGUAGE' Subdirectories for various languages. Directories containing a ! file 'config-lang.in' are language subdirectories. The contents of ! the subdirectories 'c' (for C), 'cp' (for C++), 'objc' (for ! Objective-C), 'objcp' (for Objective-C++), and 'lto' (for LTO) are documented in this manual (*note Passes and Files of the Compiler: Passes.); those for other languages are not. *Note Anatomy of a Language Front End: Front End, for details of the files in these directories. ! 'common' ! Source files shared between the compiler drivers (such as 'gcc') ! and the compilers proper (such as 'cc1'). If an architecture defines target hooks shared between those places, it also has a ! subdirectory in 'common/config'. *Note Target Structure::. ! 'config' Configuration files for supported architectures and operating ! systems. *Note Anatomy of a Target Back End: Back End, for details ! of the files in this directory. ! 'doc' Texinfo documentation for GCC, together with automatically generated man pages and support for converting the installation manual to HTML. *Note Documentation::. ! 'ginclude' System headers installed by GCC, mainly those required by the C standard of freestanding implementations. *Note Headers Installed by GCC: Headers, for details of when these and other headers are installed. ! 'po' Message catalogs with translations of messages produced by GCC into ! various languages, 'LANGUAGE.po'. This directory also contains ! 'gcc.pot', the template for these message catalogues, 'exgettext', ! a wrapper around 'gettext' to extract the messages from the GCC ! sources and create 'gcc.pot', which is run by 'make gcc.pot', and ! 'EXCLUDES', a list of files from which messages should not be extracted. ! 'testsuite' ! The GCC testsuites (except for those for runtime libraries). *Note ! Testsuites::.  File: gccint.info, Node: Configuration, Next: Build, Prev: Subdirectories, Up: gcc Directory ! 6.3.2 Configuration in the 'gcc' Directory ------------------------------------------ ! The 'gcc' directory is configured with an Autoconf-generated script ! 'configure'. The 'configure' script is generated from 'configure.ac' ! and 'aclocal.m4'. From the files 'configure.ac' and 'acconfig.h', ! Autoheader generates the file 'config.in'. The file 'cstamp-h.in' is used as a timestamp. * Menu: ! * Config Fragments:: Scripts used by 'configure'. ! * System Config:: The 'config.build', 'config.host', and ! 'config.gcc' files. ! * Configuration Files:: Files created by running 'configure'.  File: gccint.info, Node: Config Fragments, Next: System Config, Up: Configuration ! 6.3.2.1 Scripts Used by 'configure' ................................... ! 'configure' uses some other scripts to help in its work: ! * The standard GNU 'config.sub' and 'config.guess' files, kept in the ! top level directory, are used. ! * The file 'config.gcc' is used to handle configuration specific to ! the particular target machine. The file 'config.build' is used to ! handle configuration specific to the particular build machine. The ! file 'config.host' is used to handle configuration specific to the ! particular host machine. (In general, these should only be used ! for features that cannot reasonably be tested in Autoconf feature ! tests.) *Note The 'config.build'; 'config.host'; and 'config.gcc' ! Files: System Config, for details of the contents of these files. ! * Each language subdirectory has a file 'LANGUAGE/config-lang.in' ! that is used for front-end-specific configuration. *Note The Front ! End 'config-lang.in' File: Front End Config, for details of this ! file. ! * A helper script 'configure.frag' is used as part of creating the ! output of 'configure'.  File: gccint.info, Node: System Config, Next: Configuration Files, Prev: Config Fragments, Up: Configuration ! 6.3.2.2 The 'config.build'; 'config.host'; and 'config.gcc' Files ................................................................. ! The 'config.build' file contains specific rules for particular systems which GCC is built on. This should be used as rarely as possible, as the behavior of the build system can always be detected by autoconf. ! The 'config.host' file contains specific rules for particular systems which GCC will run on. This is rarely needed. ! The 'config.gcc' file contains specific rules for particular systems which GCC will generate code for. This is usually needed. ! Each file has a list of the shell variables it sets, with descriptions, ! at the top of the file. FIXME: document the contents of these files, and what variables should be set to control build, host and target configuration. --- 3226,3347 ----  File: gccint.info, Node: Subdirectories, Next: Configuration, Up: gcc Directory ! 6.3.1 Subdirectories of `gcc' ----------------------------- ! The `gcc' directory contains the following subdirectories: ! `LANGUAGE' Subdirectories for various languages. Directories containing a ! file `config-lang.in' are language subdirectories. The contents of ! the subdirectories `c' (for C), `cp' (for C++), `objc' (for ! Objective-C), `objcp' (for Objective-C++), and `lto' (for LTO) are documented in this manual (*note Passes and Files of the Compiler: Passes.); those for other languages are not. *Note Anatomy of a Language Front End: Front End, for details of the files in these directories. ! `common' ! Source files shared between the compiler drivers (such as `gcc') ! and the compilers proper (such as `cc1'). If an architecture defines target hooks shared between those places, it also has a ! subdirectory in `common/config'. *Note Target Structure::. ! `config' Configuration files for supported architectures and operating ! systems. *Note Anatomy of a Target Back End: Back End, for ! details of the files in this directory. ! `doc' Texinfo documentation for GCC, together with automatically generated man pages and support for converting the installation manual to HTML. *Note Documentation::. ! `ginclude' System headers installed by GCC, mainly those required by the C standard of freestanding implementations. *Note Headers Installed by GCC: Headers, for details of when these and other headers are installed. ! `po' Message catalogs with translations of messages produced by GCC into ! various languages, `LANGUAGE.po'. This directory also contains ! `gcc.pot', the template for these message catalogues, `exgettext', ! a wrapper around `gettext' to extract the messages from the GCC ! sources and create `gcc.pot', which is run by `make gcc.pot', and ! `EXCLUDES', a list of files from which messages should not be extracted. ! `testsuite' ! The GCC testsuites (except for those for runtime libraries). ! *Note Testsuites::.  File: gccint.info, Node: Configuration, Next: Build, Prev: Subdirectories, Up: gcc Directory ! 6.3.2 Configuration in the `gcc' Directory ------------------------------------------ ! The `gcc' directory is configured with an Autoconf-generated script ! `configure'. The `configure' script is generated from `configure.ac' ! and `aclocal.m4'. From the files `configure.ac' and `acconfig.h', ! Autoheader generates the file `config.in'. The file `cstamp-h.in' is used as a timestamp. * Menu: ! * Config Fragments:: Scripts used by `configure'. ! * System Config:: The `config.build', `config.host', and ! `config.gcc' files. ! * Configuration Files:: Files created by running `configure'.  File: gccint.info, Node: Config Fragments, Next: System Config, Up: Configuration ! 6.3.2.1 Scripts Used by `configure' ................................... ! `configure' uses some other scripts to help in its work: ! * The standard GNU `config.sub' and `config.guess' files, kept in ! the top level directory, are used. ! * The file `config.gcc' is used to handle configuration specific to ! the particular target machine. The file `config.build' is used to ! handle configuration specific to the particular build machine. ! The file `config.host' is used to handle configuration specific to ! the particular host machine. (In general, these should only be ! used for features that cannot reasonably be tested in Autoconf ! feature tests.) *Note The `config.build'; `config.host'; and ! `config.gcc' Files: System Config, for details of the contents of ! these files. ! * Each language subdirectory has a file `LANGUAGE/config-lang.in' ! that is used for front-end-specific configuration. *Note The ! Front End `config-lang.in' File: Front End Config, for details of ! this file. ! * A helper script `configure.frag' is used as part of creating the ! output of `configure'.  File: gccint.info, Node: System Config, Next: Configuration Files, Prev: Config Fragments, Up: Configuration ! 6.3.2.2 The `config.build'; `config.host'; and `config.gcc' Files ................................................................. ! The `config.build' file contains specific rules for particular systems which GCC is built on. This should be used as rarely as possible, as the behavior of the build system can always be detected by autoconf. ! The `config.host' file contains specific rules for particular systems which GCC will run on. This is rarely needed. ! The `config.gcc' file contains specific rules for particular systems which GCC will generate code for. This is usually needed. ! Each file has a list of the shell variables it sets, with ! descriptions, at the top of the file. FIXME: document the contents of these files, and what variables should be set to control build, host and target configuration. *************** be set to control build, host and target *** 3342,3402 ****  File: gccint.info, Node: Configuration Files, Prev: System Config, Up: Configuration ! 6.3.2.3 Files Created by 'configure' .................................... ! Here we spell out what files will be set up by 'configure' in the 'gcc' directory. Some other files are created as temporary files in the configuration process, and are not used in the subsequent build; these are not documented. ! * 'Makefile' is constructed from 'Makefile.in', together with the host and target fragments (*note Makefile Fragments: Fragments.) ! 't-TARGET' and 'x-HOST' from 'config', if any, and language ! Makefile fragments 'LANGUAGE/Make-lang.in'. ! * 'auto-host.h' contains information about the host machine ! determined by 'configure'. If the host machine is different from ! the build machine, then 'auto-build.h' is also created, containing such information about the build machine. ! * 'config.status' is a script that may be run to recreate the current ! configuration. ! * 'configargs.h' is a header containing details of the arguments ! passed to 'configure' to configure GCC, and of the thread model used. ! * 'cstamp-h' is used as a timestamp. ! * If a language 'config-lang.in' file (*note The Front End ! 'config-lang.in' File: Front End Config.) sets 'outputs', then the ! files listed in 'outputs' there are also generated. The following configuration headers are created from the Makefile, ! using 'mkconfig.sh', rather than directly by 'configure'. 'config.h', ! 'bconfig.h' and 'tconfig.h' all contain the 'xm-MACHINE.h' header, if any, appropriate to the host, build and target machines respectively, the configuration headers for the target, and some definitions; for the host and build machines, these include the autoconfigured headers ! generated by 'configure'. The other configuration headers are ! determined by 'config.gcc'. They also contain the typedefs for 'rtx', ! 'rtvec' and 'tree'. ! * 'config.h', for use in programs that run on the host machine. ! * 'bconfig.h', for use in programs that run on the build machine. ! * 'tconfig.h', for use in programs and libraries for the target machine. ! * 'tm_p.h', which includes the header 'MACHINE-protos.h' that ! contains prototypes for functions in the target 'MACHINE.c' file. ! The header 'MACHINE-protos.h' can include prototypes of functions ! that use rtl and tree data structures inside appropriate '#ifdef ! RTX_CODE' and '#ifdef TREE_CODE' conditional code segements. The ! 'MACHINE-protos.h' is included after the 'rtl.h' and/or 'tree.h' ! would have been included. The 'tm_p.h' also includes the header ! 'tm-preds.h' which is generated by 'genpreds' program during the build to define the declarations and inline functions for the predicate functions.  File: gccint.info, Node: Build, Next: Makefile, Prev: Configuration, Up: gcc Directory ! 6.3.3 Build System in the 'gcc' Directory ----------------------------------------- FIXME: describe the build system, including what is built in what --- 3349,3417 ----  File: gccint.info, Node: Configuration Files, Prev: System Config, Up: Configuration ! 6.3.2.3 Files Created by `configure' .................................... ! Here we spell out what files will be set up by `configure' in the `gcc' directory. Some other files are created as temporary files in the configuration process, and are not used in the subsequent build; these are not documented. ! * `Makefile' is constructed from `Makefile.in', together with the host and target fragments (*note Makefile Fragments: Fragments.) ! `t-TARGET' and `x-HOST' from `config', if any, and language ! Makefile fragments `LANGUAGE/Make-lang.in'. ! ! * `auto-host.h' contains information about the host machine ! determined by `configure'. If the host machine is different from ! the build machine, then `auto-build.h' is also created, containing such information about the build machine. ! ! * `config.status' is a script that may be run to recreate the ! current configuration. ! ! * `configargs.h' is a header containing details of the arguments ! passed to `configure' to configure GCC, and of the thread model used. ! ! * `cstamp-h' is used as a timestamp. ! ! * If a language `config-lang.in' file (*note The Front End ! `config-lang.in' File: Front End Config.) sets `outputs', then the ! files listed in `outputs' there are also generated. The following configuration headers are created from the Makefile, ! using `mkconfig.sh', rather than directly by `configure'. `config.h', ! `bconfig.h' and `tconfig.h' all contain the `xm-MACHINE.h' header, if any, appropriate to the host, build and target machines respectively, the configuration headers for the target, and some definitions; for the host and build machines, these include the autoconfigured headers ! generated by `configure'. The other configuration headers are ! determined by `config.gcc'. They also contain the typedefs for `rtx', ! `rtvec' and `tree'. ! * `config.h', for use in programs that run on the host machine. ! ! * `bconfig.h', for use in programs that run on the build machine. ! ! * `tconfig.h', for use in programs and libraries for the target machine. ! ! * `tm_p.h', which includes the header `MACHINE-protos.h' that ! contains prototypes for functions in the target `MACHINE.c' file. ! The header `MACHINE-protos.h' can include prototypes of functions ! that use rtl and tree data structures inside appropriate `#ifdef ! RTX_CODE' and `#ifdef TREE_CODE' conditional code segements. The ! `MACHINE-protos.h' is included after the `rtl.h' and/or `tree.h' ! would have been included. The `tm_p.h' also includes the header ! `tm-preds.h' which is generated by `genpreds' program during the build to define the declarations and inline functions for the predicate functions.  File: gccint.info, Node: Build, Next: Makefile, Prev: Configuration, Up: gcc Directory ! 6.3.3 Build System in the `gcc' Directory ----------------------------------------- FIXME: describe the build system, including what is built in what *************** File: gccint.info, Node: Makefile, Nex *** 3410,3477 **** 6.3.4 Makefile Targets ---------------------- ! These targets are available from the 'gcc' directory: ! 'all' This is the default target. Depending on what your build/host/target configuration is, it coordinates all the things that need to be built. ! 'doc' Produce info-formatted documentation and man pages. Essentially it ! calls 'make man' and 'make info'. ! 'dvi' Produce DVI-formatted documentation. ! 'pdf' Produce PDF-formatted documentation. ! 'html' Produce HTML-formatted documentation. ! 'man' Generate man pages. ! 'info' Generate info-formatted pages. ! 'mostlyclean' Delete the files made while building the compiler. ! 'clean' ! That, and all the other files built by 'make all'. ! 'distclean' ! That, and all the files created by 'configure'. ! 'maintainer-clean' Distclean plus any file that can be generated from other files. Note that additional tools may be required beyond what is normally needed to build GCC. ! 'srcextra' Generates files in the source directory that are not version-controlled but should go into a release tarball. ! 'srcinfo' ! 'srcman' Copies the info-formatted and manpage documentation into the source directory usually for the purpose of generating a release tarball. ! 'install' Installs GCC. ! 'uninstall' Deletes installed files, though this is not supported. ! 'check' ! Run the testsuite. This creates a 'testsuite' subdirectory that ! has various '.sum' and '.log' files containing the results of the ! testing. You can run subsets with, for example, 'make check-gcc'. ! You can specify specific tests by setting 'RUNTESTFLAGS' to be the ! name of the '.exp' file, optionally followed by (for some tests) an ! equals and a file wildcard, like: make check-gcc RUNTESTFLAGS="execute.exp=19980413-*" --- 3425,3492 ---- 6.3.4 Makefile Targets ---------------------- ! These targets are available from the `gcc' directory: ! `all' This is the default target. Depending on what your build/host/target configuration is, it coordinates all the things that need to be built. ! `doc' Produce info-formatted documentation and man pages. Essentially it ! calls `make man' and `make info'. ! `dvi' Produce DVI-formatted documentation. ! `pdf' Produce PDF-formatted documentation. ! `html' Produce HTML-formatted documentation. ! `man' Generate man pages. ! `info' Generate info-formatted pages. ! `mostlyclean' Delete the files made while building the compiler. ! `clean' ! That, and all the other files built by `make all'. ! `distclean' ! That, and all the files created by `configure'. ! `maintainer-clean' Distclean plus any file that can be generated from other files. Note that additional tools may be required beyond what is normally needed to build GCC. ! `srcextra' Generates files in the source directory that are not version-controlled but should go into a release tarball. ! `srcinfo' ! `srcman' Copies the info-formatted and manpage documentation into the source directory usually for the purpose of generating a release tarball. ! `install' Installs GCC. ! `uninstall' Deletes installed files, though this is not supported. ! `check' ! Run the testsuite. This creates a `testsuite' subdirectory that ! has various `.sum' and `.log' files containing the results of the ! testing. You can run subsets with, for example, `make check-gcc'. ! You can specify specific tests by setting `RUNTESTFLAGS' to be the ! name of the `.exp' file, optionally followed by (for some tests) ! an equals and a file wildcard, like: make check-gcc RUNTESTFLAGS="execute.exp=19980413-*" *************** steps of the build, including bootstrapp *** 3484,3574 **** new compiler to build target libraries. When GCC is configured for a native configuration, the default action ! for 'make' is to do a full three-stage bootstrap. This means that GCC is built three times--once with the native compiler, once with the ! native-built compiler it just built, and once with the compiler it built ! the second time. In theory, the last two should produce the same ! results, which 'make compare' can check. Each stage is configured separately and compiled into a separate directory, to minimize problems due to ABI incompatibilities between the native compiler and GCC. ! If you do a change, rebuilding will also start from the first stage and ! "bubble" up the change through the three stages. Each stage is taken ! from its build directory (if it had been built previously), rebuilt, and ! copied to its subdirectory. This will allow you to, for example, ! continue a bootstrap after fixing a bug which causes the stage2 build to ! crash. It does not provide as good coverage of the compiler as ! bootstrapping from scratch, but it ensures that the new code is ! syntactically correct (e.g., that you did not use GCC extensions by ! mistake), and avoids spurious bootstrap comparison failures(1). Other targets available from the top level include: ! 'bootstrap-lean' ! Like 'bootstrap', except that the various stages are removed once they're no longer needed. This saves disk space. ! 'bootstrap2' ! 'bootstrap2-lean' Performs only the first two stages of bootstrap. Unlike a three-stage bootstrap, this does not perform a comparison to test that the compiler is running properly. Note that the disk space required by a "lean" bootstrap is approximately independent of the number of stages. ! 'stageN-bubble (N = 1...4, profile, feedback)' Rebuild all the stages up to N, with the appropriate flags, "bubbling" the changes as described above. ! 'all-stageN (N = 1...4, profile, feedback)' Assuming that stage N has already been built, rebuild it with the appropriate flags. This is rarely needed. ! 'cleanstrap' ! Remove everything ('make clean') and rebuilds ('make bootstrap'). ! 'compare' Compares the results of stages 2 and 3. This ensures that the compiler is running properly, since it should produce the same object files regardless of how it itself was compiled. ! 'profiledbootstrap' Builds a compiler with profiling feedback information. In this ! case, the second and third stages are named 'profile' and ! 'feedback', respectively. For more information, see *note Building ! with profile feedback: (gccinstall)Building. ! 'restrap' ! Restart a bootstrap, so that everything that was not built with the ! system compiler is rebuilt. ! 'stageN-start (N = 1...4, profile, feedback)' For each package that is bootstrapped, rename directories so that, ! for example, 'gcc' points to the stageN GCC, compiled with the stageN-1 GCC(2). ! You will invoke this target if you need to test or debug the stageN ! GCC. If you only need to execute GCC (but you need not run 'make' ! either to rebuild it or to run test suites), you should be able to ! work directly in the 'stageN-gcc' directory. This makes it easier ! to debug multiple stages in parallel. ! 'stage' For each package that is bootstrapped, relocate its build directory ! to indicate its stage. For example, if the 'gcc' directory points ! to the stage2 GCC, after invoking this target it will be renamed to ! 'stage2-gcc'. If you wish to use non-default GCC flags when compiling the stage2 and ! stage3 compilers, set 'BOOT_CFLAGS' on the command line when doing ! 'make'. ! Usually, the first stage only builds the languages that the compiler is ! written in: typically, C and maybe Ada. If you are debugging a miscompilation of a different stage2 front-end (for example, of the Fortran front-end), you may want to have front-ends for other languages ! in the first stage as well. To do so, set 'STAGE1_LANGUAGES' on the ! command line when doing 'make'. For example, in the aforementioned scenario of debugging a Fortran front-end miscompilation caused by the stage1 compiler, you may need a --- 3499,3590 ---- new compiler to build target libraries. When GCC is configured for a native configuration, the default action ! for `make' is to do a full three-stage bootstrap. This means that GCC is built three times--once with the native compiler, once with the ! native-built compiler it just built, and once with the compiler it ! built the second time. In theory, the last two should produce the same ! results, which `make compare' can check. Each stage is configured separately and compiled into a separate directory, to minimize problems due to ABI incompatibilities between the native compiler and GCC. ! If you do a change, rebuilding will also start from the first stage ! and "bubble" up the change through the three stages. Each stage is ! taken from its build directory (if it had been built previously), ! rebuilt, and copied to its subdirectory. This will allow you to, for ! example, continue a bootstrap after fixing a bug which causes the ! stage2 build to crash. It does not provide as good coverage of the ! compiler as bootstrapping from scratch, but it ensures that the new ! code is syntactically correct (e.g., that you did not use GCC extensions ! by mistake), and avoids spurious bootstrap comparison failures(1). Other targets available from the top level include: ! `bootstrap-lean' ! Like `bootstrap', except that the various stages are removed once they're no longer needed. This saves disk space. ! `bootstrap2' ! `bootstrap2-lean' Performs only the first two stages of bootstrap. Unlike a three-stage bootstrap, this does not perform a comparison to test that the compiler is running properly. Note that the disk space required by a "lean" bootstrap is approximately independent of the number of stages. ! `stageN-bubble (N = 1...4, profile, feedback)' Rebuild all the stages up to N, with the appropriate flags, "bubbling" the changes as described above. ! `all-stageN (N = 1...4, profile, feedback)' Assuming that stage N has already been built, rebuild it with the appropriate flags. This is rarely needed. ! `cleanstrap' ! Remove everything (`make clean') and rebuilds (`make bootstrap'). ! `compare' Compares the results of stages 2 and 3. This ensures that the compiler is running properly, since it should produce the same object files regardless of how it itself was compiled. ! `profiledbootstrap' Builds a compiler with profiling feedback information. In this ! case, the second and third stages are named `profile' and ! `feedback', respectively. For more information, see *note ! Building with profile feedback: (gccinstall)Building. ! `restrap' ! Restart a bootstrap, so that everything that was not built with ! the system compiler is rebuilt. ! `stageN-start (N = 1...4, profile, feedback)' For each package that is bootstrapped, rename directories so that, ! for example, `gcc' points to the stageN GCC, compiled with the stageN-1 GCC(2). ! You will invoke this target if you need to test or debug the ! stageN GCC. If you only need to execute GCC (but you need not run ! `make' either to rebuild it or to run test suites), you should be ! able to work directly in the `stageN-gcc' directory. This makes ! it easier to debug multiple stages in parallel. ! `stage' For each package that is bootstrapped, relocate its build directory ! to indicate its stage. For example, if the `gcc' directory points ! to the stage2 GCC, after invoking this target it will be renamed ! to `stage2-gcc'. ! If you wish to use non-default GCC flags when compiling the stage2 and ! stage3 compilers, set `BOOT_CFLAGS' on the command line when doing ! `make'. ! Usually, the first stage only builds the languages that the compiler ! is written in: typically, C and maybe Ada. If you are debugging a miscompilation of a different stage2 front-end (for example, of the Fortran front-end), you may want to have front-ends for other languages ! in the first stage as well. To do so, set `STAGE1_LANGUAGES' on the ! command line when doing `make'. For example, in the aforementioned scenario of debugging a Fortran front-end miscompilation caused by the stage1 compiler, you may need a *************** command like *** 3577,3604 **** make stage2-bubble STAGE1_LANGUAGES=c,fortran Alternatively, you can use per-language targets to build and test ! languages that are not enabled by default in stage1. For example, 'make ! f951' will build a Fortran compiler even in the stage1 build directory. ! ---------- Footnotes ---------- ! (1) Except if the compiler was buggy and miscompiled some of the ! files that were not modified. In this case, it's best to use 'make ! restrap'. ! (2) Customarily, the system compiler is also termed the 'stage0' GCC.  File: gccint.info, Node: Library Files, Next: Headers, Prev: Makefile, Up: gcc Directory ! 6.3.5 Library Source Files and Headers under the 'gcc' Directory ---------------------------------------------------------------- FIXME: list here, with explanation, all the C source files and headers ! under the 'gcc' directory that aren't built into the GCC executable but rather are part of runtime libraries and object files, such as ! 'crtstuff.c' and 'unwind-dw2.c'. *Note Headers Installed by GCC: ! Headers, for more information about the 'ginclude' directory.  File: gccint.info, Node: Headers, Next: Documentation, Prev: Library Files, Up: gcc Directory --- 3593,3620 ---- make stage2-bubble STAGE1_LANGUAGES=c,fortran Alternatively, you can use per-language targets to build and test ! languages that are not enabled by default in stage1. For example, ! `make f951' will build a Fortran compiler even in the stage1 build ! directory. ! ---------- Footnotes ---------- ! (1) Except if the compiler was buggy and miscompiled some of the files ! that were not modified. In this case, it's best to use `make restrap'. ! (2) Customarily, the system compiler is also termed the `stage0' GCC.  File: gccint.info, Node: Library Files, Next: Headers, Prev: Makefile, Up: gcc Directory ! 6.3.5 Library Source Files and Headers under the `gcc' Directory ---------------------------------------------------------------- FIXME: list here, with explanation, all the C source files and headers ! under the `gcc' directory that aren't built into the GCC executable but rather are part of runtime libraries and object files, such as ! `crtstuff.c' and `unwind-dw2.c'. *Note Headers Installed by GCC: ! Headers, for more information about the `ginclude' directory.  File: gccint.info, Node: Headers, Next: Documentation, Prev: Library Files, Up: gcc Directory *************** In general, GCC expects the system C lib *** 3610,3647 **** headers to be used with it. However, GCC will fix those headers if necessary to make them work with GCC, and will install some headers required of freestanding implementations. These headers are installed ! in 'LIBSUBDIR/include'. Headers for non-C runtime libraries are also installed by GCC; these are not documented here. (FIXME: document them somewhere.) ! Several of the headers GCC installs are in the 'ginclude' directory. ! These headers, 'iso646.h', 'stdarg.h', 'stdbool.h', and 'stddef.h', are ! installed in 'LIBSUBDIR/include', unless the target Makefile fragment ! (*note Target Fragment::) overrides this by setting 'USER_H'. In addition to these headers and those generated by fixing system headers to work with GCC, some other headers may also be installed in ! 'LIBSUBDIR/include'. 'config.gcc' may set 'extra_headers'; this ! specifies additional headers under 'config' to be installed on some systems. ! GCC installs its own version of '', from 'ginclude/float.h'. This is done to cope with command-line options that change the representation of floating point numbers. ! GCC also installs its own version of ''; this is generated ! from 'glimits.h', together with 'limitx.h' and 'limity.h' if the system ! also has its own version of ''. (GCC provides its own header because it is required of ISO C freestanding implementations, but needs to include the system header from its own header as well because other standards such as POSIX specify additional values to be defined in ! ''.) The system's '' header is used via ! 'LIBSUBDIR/include/syslimits.h', which is copied from 'gsyslimits.h' if it does not need fixing to work with GCC; if it needs fixing, ! 'syslimits.h' is the fixed copy. ! GCC can also install ''. It will do this when 'config.gcc' ! sets 'use_gcc_tgmath' to 'yes'.  File: gccint.info, Node: Documentation, Next: Front End, Prev: Headers, Up: gcc Directory --- 3626,3663 ---- headers to be used with it. However, GCC will fix those headers if necessary to make them work with GCC, and will install some headers required of freestanding implementations. These headers are installed ! in `LIBSUBDIR/include'. Headers for non-C runtime libraries are also installed by GCC; these are not documented here. (FIXME: document them somewhere.) ! Several of the headers GCC installs are in the `ginclude' directory. ! These headers, `iso646.h', `stdarg.h', `stdbool.h', and `stddef.h', are ! installed in `LIBSUBDIR/include', unless the target Makefile fragment ! (*note Target Fragment::) overrides this by setting `USER_H'. In addition to these headers and those generated by fixing system headers to work with GCC, some other headers may also be installed in ! `LIBSUBDIR/include'. `config.gcc' may set `extra_headers'; this ! specifies additional headers under `config' to be installed on some systems. ! GCC installs its own version of `', from `ginclude/float.h'. This is done to cope with command-line options that change the representation of floating point numbers. ! GCC also installs its own version of `'; this is generated ! from `glimits.h', together with `limitx.h' and `limity.h' if the system ! also has its own version of `'. (GCC provides its own header because it is required of ISO C freestanding implementations, but needs to include the system header from its own header as well because other standards such as POSIX specify additional values to be defined in ! `'.) The system's `' header is used via ! `LIBSUBDIR/include/syslimits.h', which is copied from `gsyslimits.h' if it does not need fixing to work with GCC; if it needs fixing, ! `syslimits.h' is the fixed copy. ! GCC can also install `'. It will do this when `config.gcc' ! sets `use_gcc_tgmath' to `yes'.  File: gccint.info, Node: Documentation, Next: Front End, Prev: Headers, Up: gcc Directory *************** File: gccint.info, Node: Documentation, *** 3651,3661 **** The main GCC documentation is in the form of manuals in Texinfo format. These are installed in Info format; DVI versions may be generated by ! 'make dvi', PDF versions by 'make pdf', and HTML versions by 'make html'. In addition, some man pages are generated from the Texinfo manuals, there are some other text files with miscellaneous documentation, and runtime libraries have their own documentation ! outside the 'gcc' directory. FIXME: document the documentation for runtime libraries somewhere. * Menu: --- 3667,3677 ---- The main GCC documentation is in the form of manuals in Texinfo format. These are installed in Info format; DVI versions may be generated by ! `make dvi', PDF versions by `make pdf', and HTML versions by `make html'. In addition, some man pages are generated from the Texinfo manuals, there are some other text files with miscellaneous documentation, and runtime libraries have their own documentation ! outside the `gcc' directory. FIXME: document the documentation for runtime libraries somewhere. * Menu: *************** File: gccint.info, Node: Texinfo Manual *** 3671,3719 **** ....................... The manuals for GCC as a whole, and the C and C++ front ends, are in ! files 'doc/*.texi'. Other front ends have their own manuals in files ! 'LANGUAGE/*.texi'. Common files 'doc/include/*.texi' are provided which ! may be included in multiple manuals; the following files are in ! 'doc/include': ! 'fdl.texi' The GNU Free Documentation License. ! 'funding.texi' The section "Funding Free Software". ! 'gcc-common.texi' Common definitions for manuals. ! 'gpl_v3.texi' The GNU General Public License. - 'texinfo.tex' - A copy of 'texinfo.tex' known to work with the GCC manuals. ! DVI-formatted manuals are generated by 'make dvi', which uses ! 'texi2dvi' (via the Makefile macro '$(TEXI2DVI)'). PDF-formatted ! manuals are generated by 'make pdf', which uses 'texi2pdf' (via the ! Makefile macro '$(TEXI2PDF)'). HTML formatted manuals are generated by ! 'make html'. Info manuals are generated by 'make info' (which is run as ! part of a bootstrap); this generates the manuals in the source ! directory, using 'makeinfo' via the Makefile macro '$(MAKEINFO)', and they are included in release distributions. Manuals are also provided on the GCC web site, in both HTML and PostScript forms. This is done via the script ! 'maintainer-scripts/update_web_docs_svn'. Each manual to be provided ! online must be listed in the definition of 'MANUALS' in that file; a ! file 'NAME.texi' must only appear once in the source tree, and the output manual must have the same name as the source file. (However, other Texinfo files, included in manuals but not themselves the root files of manuals, may have names that appear more than once in the ! source tree.) The manual file 'NAME.texi' should only include other ! files in its own directory or in 'doc/include'. HTML manuals will be ! generated by 'makeinfo --html', PostScript manuals by 'texi2dvi' and ! 'dvips', and PDF manuals by 'texi2pdf'. All Texinfo files that are parts of manuals must be version-controlled, even if they are generated files, for the generation of online manuals to work. ! The installation manual, 'doc/install.texi', is also provided on the GCC web site. The HTML version is generated by the script ! 'doc/install.texi2html'.  File: gccint.info, Node: Man Page Generation, Next: Miscellaneous Docs, Prev: Texinfo Manuals, Up: Documentation --- 3687,3739 ---- ....................... The manuals for GCC as a whole, and the C and C++ front ends, are in ! files `doc/*.texi'. Other front ends have their own manuals in files ! `LANGUAGE/*.texi'. Common files `doc/include/*.texi' are provided ! which may be included in multiple manuals; the following files are in ! `doc/include': ! `fdl.texi' The GNU Free Documentation License. ! ! `funding.texi' The section "Funding Free Software". ! ! `gcc-common.texi' Common definitions for manuals. ! ! `gpl_v3.texi' The GNU General Public License. ! `texinfo.tex' ! A copy of `texinfo.tex' known to work with the GCC manuals. ! ! DVI-formatted manuals are generated by `make dvi', which uses ! `texi2dvi' (via the Makefile macro `$(TEXI2DVI)'). PDF-formatted ! manuals are generated by `make pdf', which uses `texi2pdf' (via the ! Makefile macro `$(TEXI2PDF)'). HTML formatted manuals are generated by ! `make html'. Info manuals are generated by `make info' (which is run ! as part of a bootstrap); this generates the manuals in the source ! directory, using `makeinfo' via the Makefile macro `$(MAKEINFO)', and they are included in release distributions. Manuals are also provided on the GCC web site, in both HTML and PostScript forms. This is done via the script ! `maintainer-scripts/update_web_docs_svn'. Each manual to be provided ! online must be listed in the definition of `MANUALS' in that file; a ! file `NAME.texi' must only appear once in the source tree, and the output manual must have the same name as the source file. (However, other Texinfo files, included in manuals but not themselves the root files of manuals, may have names that appear more than once in the ! source tree.) The manual file `NAME.texi' should only include other ! files in its own directory or in `doc/include'. HTML manuals will be ! generated by `makeinfo --html', PostScript manuals by `texi2dvi' and ! `dvips', and PDF manuals by `texi2pdf'. All Texinfo files that are parts of manuals must be version-controlled, even if they are generated files, for the generation of online manuals to work. ! The installation manual, `doc/install.texi', is also provided on the GCC web site. The HTML version is generated by the script ! `doc/install.texi2html'.  File: gccint.info, Node: Man Page Generation, Next: Miscellaneous Docs, Prev: Texinfo Manuals, Up: Documentation *************** File: gccint.info, Node: Man Page Gener *** 3722,3759 **** ........................... Because of user demand, in addition to full Texinfo manuals, man pages ! are provided which contain extracts from those manuals. These man pages ! are generated from the Texinfo manuals using 'contrib/texi2pod.pl' and ! 'pod2man'. (The man page for 'g++', 'cp/g++.1', just contains a '.so' ! reference to 'gcc.1', but all the other man pages are generated from ! Texinfo manuals.) Because many systems may not have the necessary tools installed to ! generate the man pages, they are only generated if the 'configure' ! script detects that recent enough tools are installed, and the Makefiles ! allow generating man pages to fail without aborting the build. Man ! pages are also included in release distributions. They are generated in ! the source directory. ! Magic comments in Texinfo files starting '@c man' control what parts of ! a Texinfo file go into a man page. Only a subset of Texinfo is ! supported by 'texi2pod.pl', and it may be necessary to add support for more Texinfo features to this script when generating new man pages. To ! improve the man page output, some special Texinfo macros are provided in ! 'doc/include/gcc-common.texi' which 'texi2pod.pl' understands: ! '@gcctabopt' ! Use in the form '@table @gcctabopt' for tables of options, where ! for printed output the effect of '@code' is better than that of ! '@option' but for man page output a different effect is wanted. ! '@gccoptlist' Use for summary lists of options in manuals. ! '@gol' ! Use at the end of each line inside '@gccoptlist'. This is necessary to avoid problems with differences in how the ! '@gccoptlist' macro is handled by different Texinfo formatters. ! FIXME: describe the 'texi2pod.pl' input language and magic comments in more detail.  --- 3742,3781 ---- ........................... Because of user demand, in addition to full Texinfo manuals, man pages ! are provided which contain extracts from those manuals. These man ! pages are generated from the Texinfo manuals using ! `contrib/texi2pod.pl' and `pod2man'. (The man page for `g++', ! `cp/g++.1', just contains a `.so' reference to `gcc.1', but all the ! other man pages are generated from Texinfo manuals.) Because many systems may not have the necessary tools installed to ! generate the man pages, they are only generated if the `configure' ! script detects that recent enough tools are installed, and the ! Makefiles allow generating man pages to fail without aborting the ! build. Man pages are also included in release distributions. They are ! generated in the source directory. ! Magic comments in Texinfo files starting `@c man' control what parts ! of a Texinfo file go into a man page. Only a subset of Texinfo is ! supported by `texi2pod.pl', and it may be necessary to add support for more Texinfo features to this script when generating new man pages. To ! improve the man page output, some special Texinfo macros are provided ! in `doc/include/gcc-common.texi' which `texi2pod.pl' understands: ! `@gcctabopt' ! Use in the form `@table @gcctabopt' for tables of options, where ! for printed output the effect of `@code' is better than that of ! `@option' but for man page output a different effect is wanted. ! ! `@gccoptlist' Use for summary lists of options in manuals. ! ! `@gol' ! Use at the end of each line inside `@gccoptlist'. This is necessary to avoid problems with differences in how the ! `@gccoptlist' macro is handled by different Texinfo formatters. ! FIXME: describe the `texi2pod.pl' input language and magic comments in more detail.  *************** File: gccint.info, Node: Miscellaneous *** 3763,3799 **** ................................... In addition to the formal documentation that is installed by GCC, there ! are several other text files in the 'gcc' subdirectory with miscellaneous documentation: ! 'ABOUT-GCC-NLS' ! Notes on GCC's Native Language Support. FIXME: this should be part ! of this manual rather than a separate file. ! 'ABOUT-NLS' Notes on the Free Translation Project. ! 'COPYING' ! 'COPYING3' The GNU General Public License, Versions 2 and 3. ! 'COPYING.LIB' ! 'COPYING3.LIB' The GNU Lesser General Public License, Versions 2.1 and 3. ! '*ChangeLog*' ! '*/ChangeLog*' Change log files for various parts of GCC. ! 'LANGUAGES' Details of a few changes to the GCC front-end interface. FIXME: the information in this file should be part of general documentation of the front-end interface in this manual. ! 'ONEWS' Information about new features in old versions of GCC. (For recent versions, the information is on the GCC web site.) ! 'README.Portability' Information about portability issues when writing code in GCC. FIXME: why isn't this part of this manual or of the GCC Coding Conventions? ! FIXME: document such files in subdirectories, at least 'config', 'c', ! 'cp', 'objc', 'testsuite'.  File: gccint.info, Node: Front End, Next: Back End, Prev: Documentation, Up: gcc Directory --- 3785,3828 ---- ................................... In addition to the formal documentation that is installed by GCC, there ! are several other text files in the `gcc' subdirectory with miscellaneous documentation: ! `ABOUT-GCC-NLS' ! Notes on GCC's Native Language Support. FIXME: this should be ! part of this manual rather than a separate file. ! ! `ABOUT-NLS' Notes on the Free Translation Project. ! ! `COPYING' ! `COPYING3' The GNU General Public License, Versions 2 and 3. ! ! `COPYING.LIB' ! `COPYING3.LIB' The GNU Lesser General Public License, Versions 2.1 and 3. ! ! `*ChangeLog*' ! `*/ChangeLog*' Change log files for various parts of GCC. ! ! `LANGUAGES' Details of a few changes to the GCC front-end interface. FIXME: the information in this file should be part of general documentation of the front-end interface in this manual. ! ! `ONEWS' Information about new features in old versions of GCC. (For recent versions, the information is on the GCC web site.) ! ! `README.Portability' Information about portability issues when writing code in GCC. FIXME: why isn't this part of this manual or of the GCC Coding Conventions? ! FIXME: document such files in subdirectories, at least `config', `c', ! `cp', `objc', `testsuite'.  File: gccint.info, Node: Front End, Next: Back End, Prev: Documentation, Up: gcc Directory *************** File: gccint.info, Node: Front End, Ne *** 3803,3839 **** A front end for a language in GCC has the following parts: ! * A directory 'LANGUAGE' under 'gcc' containing source files for that ! front end. *Note The Front End 'LANGUAGE' Directory: Front End ! Directory, for details. * A mention of the language in the list of supported languages in ! 'gcc/doc/install.texi'. * A mention of the name under which the language's runtime library is ! recognized by '--enable-shared=PACKAGE' in the documentation of ! that option in 'gcc/doc/install.texi'. * A mention of any special prerequisites for building the front end ! in the documentation of prerequisites in 'gcc/doc/install.texi'. * Details of contributors to that front end in ! 'gcc/doc/contrib.texi'. If the details are in that front end's own ! manual then there should be a link to that manual's list in ! 'contrib.texi'. * Information about support for that language in ! 'gcc/doc/frontends.texi'. * Information about standards for that language, and the front end's ! support for them, in 'gcc/doc/standards.texi'. This may be a link to such information in the front end's own manual. ! * Details of source file suffixes for that language and '-x LANG' ! options supported, in 'gcc/doc/invoke.texi'. ! * Entries in 'default_compilers' in 'gcc.c' for source file suffixes for that language. ! * Preferably testsuites, which may be under 'gcc/testsuite' or runtime library directories. FIXME: document somewhere how to write testsuite harnesses. ! * Probably a runtime library for the language, outside the 'gcc' directory. FIXME: document this further. * Details of the directories of any runtime libraries in ! 'gcc/doc/sourcebuild.texi'. ! * Check targets in 'Makefile.def' for the top-level 'Makefile' to check just the compiler or the compiler and runtime library for the language. --- 3832,3880 ---- A front end for a language in GCC has the following parts: ! * A directory `LANGUAGE' under `gcc' containing source files for ! that front end. *Note The Front End `LANGUAGE' Directory: Front ! End Directory, for details. ! * A mention of the language in the list of supported languages in ! `gcc/doc/install.texi'. ! * A mention of the name under which the language's runtime library is ! recognized by `--enable-shared=PACKAGE' in the documentation of ! that option in `gcc/doc/install.texi'. ! * A mention of any special prerequisites for building the front end ! in the documentation of prerequisites in `gcc/doc/install.texi'. ! * Details of contributors to that front end in ! `gcc/doc/contrib.texi'. If the details are in that front end's ! own manual then there should be a link to that manual's list in ! `contrib.texi'. ! * Information about support for that language in ! `gcc/doc/frontends.texi'. ! * Information about standards for that language, and the front end's ! support for them, in `gcc/doc/standards.texi'. This may be a link to such information in the front end's own manual. ! ! * Details of source file suffixes for that language and `-x LANG' ! options supported, in `gcc/doc/invoke.texi'. ! ! * Entries in `default_compilers' in `gcc.c' for source file suffixes for that language. ! ! * Preferably testsuites, which may be under `gcc/testsuite' or runtime library directories. FIXME: document somewhere how to write testsuite harnesses. ! ! * Probably a runtime library for the language, outside the `gcc' directory. FIXME: document this further. + * Details of the directories of any runtime libraries in ! `gcc/doc/sourcebuild.texi'. ! ! * Check targets in `Makefile.def' for the top-level `Makefile' to check just the compiler or the compiler and runtime library for the language. *************** A front end for a language in GCC has th *** 3841,4049 **** following are also necessary: * At least one Bugzilla component for bugs in that front end and ! runtime libraries. This category needs to be added to the Bugzilla ! database. * Normally, one or more maintainers of that front end listed in ! 'MAINTAINERS'. ! * Mentions on the GCC web site in 'index.html' and 'frontends.html', ! with any relevant links on 'readings.html'. (Front ends that are ! not an official part of GCC may also be listed on 'frontends.html', ! with relevant links.) ! * A news item on 'index.html', and possibly an announcement on the mailing list. * The front end's manuals should be mentioned in ! 'maintainer-scripts/update_web_docs_svn' (*note Texinfo Manuals::) and the online manuals should be linked to from ! 'onlinedocs/index.html'. * Any old releases or CVS repositories of the front end, before its inclusion in GCC, should be made available on the GCC FTP site ! . ! * The release and snapshot script 'maintainer-scripts/gcc_release' should be updated to generate appropriate tarballs for this front end. * If this front end includes its own version files that include the ! current date, 'maintainer-scripts/update_version' should be updated ! accordingly. * Menu: ! * Front End Directory:: The front end 'LANGUAGE' directory. ! * Front End Config:: The front end 'config-lang.in' file. ! * Front End Makefile:: The front end 'Make-lang.in' file.  File: gccint.info, Node: Front End Directory, Next: Front End Config, Up: Front End ! 6.3.8.1 The Front End 'LANGUAGE' Directory .......................................... ! A front end 'LANGUAGE' directory contains the source files of that front ! end (but not of any runtime libraries, which should be outside the 'gcc' ! directory). This includes documentation, and possibly some subsidiary ! programs built alongside the front end. Certain files are special and ! other parts of the compiler depend on their names: ! 'config-lang.in' This file is required in all language subdirectories. *Note The ! Front End 'config-lang.in' File: Front End Config, for details of its contents ! 'Make-lang.in' This file is required in all language subdirectories. *Note The ! Front End 'Make-lang.in' File: Front End Makefile, for details of its contents. ! 'lang.opt' This file registers the set of switches that the front end accepts ! on the command line, and their '--help' text. *Note Options::. ! 'lang-specs.h' ! This file provides entries for 'default_compilers' in 'gcc.c' which ! override the default of giving an error that a compiler for that ! language is not installed. ! 'LANGUAGE-tree.def' This file, which need not exist, defines any language-specific tree codes.  File: gccint.info, Node: Front End Config, Next: Front End Makefile, Prev: Front End Directory, Up: Front End ! 6.3.8.2 The Front End 'config-lang.in' File ........................................... ! Each language subdirectory contains a 'config-lang.in' file. This file is a shell script that may define some variables describing the language: ! 'language' This definition must be present, and gives the name of the language ! for some purposes such as arguments to '--enable-languages'. ! 'lang_requires' If defined, this variable lists (space-separated) language front ends other than C that this front end requires to be enabled (with ! the names given being their 'language' settings). For example, the Java front end depends on the C++ front end, so sets ! 'lang_requires=c++'. ! 'subdir_requires' If defined, this variable lists (space-separated) front end directories other than C that this front end requires to be present. For example, the Objective-C++ front end uses source files from the C++ and Objective-C front ends, so sets ! 'subdir_requires="cp objc"'. ! 'target_libs' If defined, this variable lists (space-separated) targets in the ! top level 'Makefile' to build the runtime libraries for this ! language, such as 'target-libobjc'. ! 'lang_dirs' If defined, this variable lists (space-separated) top level ! directories (parallel to 'gcc'), apart from the runtime libraries, that should not be configured if this front end is not built. ! 'build_by_default' ! If defined to 'no', this language front end is not built unless ! enabled in a '--enable-languages' argument. Otherwise, front ends are built by default, subject to any special logic in ! 'configure.ac' (as is present to disable the Ada front end if the Ada compiler is not already installed). ! 'boot_language' ! If defined to 'yes', this front end is built in stage1 of the bootstrap. This is only relevant to front ends written in their own languages. ! 'compilers' If defined, a space-separated list of compiler executables that will be run by the driver. The names here will each end with ! '\$(exeext)'. ! 'outputs' If defined, a space-separated list of files that should be ! generated by 'configure' substituting values in them. This ! mechanism can be used to create a file 'LANGUAGE/Makefile' from ! 'LANGUAGE/Makefile.in', but this is deprecated, building everything ! from the single 'gcc/Makefile' is preferred. ! 'gtfiles' If defined, a space-separated list of files that should be scanned ! by 'gengtype.c' to generate the garbage collection tables and routines for this language. This excludes the files that are common to all front ends. *Note Type Information::.  File: gccint.info, Node: Front End Makefile, Prev: Front End Config, Up: Front End ! 6.3.8.3 The Front End 'Make-lang.in' File ......................................... ! Each language subdirectory contains a 'Make-lang.in' file. It contains ! targets 'LANG.HOOK' (where 'LANG' is the setting of 'language' in ! 'config-lang.in') for the following values of 'HOOK', and any other Makefile rules required to build those targets (which may if necessary ! use other Makefiles specified in 'outputs' in 'config-lang.in', although ! this is deprecated). It also adds any testsuite targets that can use ! the standard rule in 'gcc/Makefile.in' to the variable 'lang_checks'. ! 'all.cross' ! 'start.encap' ! 'rest.encap' FIXME: exactly what goes in each of these targets? ! 'tags' ! Build an 'etags' 'TAGS' file in the language subdirectory in the source tree. ! 'info' Build info documentation for the front end, in the build directory. ! This target is only called by 'make bootstrap' if a suitable ! version of 'makeinfo' is available, so does not need to check for this, and should fail if an error occurs. ! 'dvi' Build DVI documentation for the front end, in the build directory. ! This should be done using '$(TEXI2DVI)', with appropriate '-I' arguments pointing to directories of included files. ! 'pdf' Build PDF documentation for the front end, in the build directory. ! This should be done using '$(TEXI2PDF)', with appropriate '-I' arguments pointing to directories of included files. ! 'html' Build HTML documentation for the front end, in the build directory. ! 'man' Build generated man pages for the front end from Texinfo manuals (*note Man Page Generation::), in the build directory. This target is only called if the necessary tools are available, but should ignore errors so as not to stop the build if errors occur; man pages are optional and the tools involved may be installed in a broken way. ! 'install-common' Install everything that is part of the front end, apart from the ! compiler executables listed in 'compilers' in 'config-lang.in'. ! 'install-info' Install info documentation for the front end, if it is present in ! the source directory. This target should have dependencies on info ! files that should be installed. ! 'install-man' Install man pages for the front end. This target should ignore errors. ! 'install-plugin' Install headers needed for plugins. ! 'srcextra' Copies its dependencies into the source directory. This generally ! should be used for generated files such as Bison output files which ! are not version-controlled, but should be included in any release ! tarballs. This target will be executed during a bootstrap if ! '--enable-generated-files-in-srcdir' was specified as a 'configure' ! option. ! 'srcinfo' ! 'srcman' Copies its dependencies into the source directory. These targets will be executed during a bootstrap if ! '--enable-generated-files-in-srcdir' was specified as a 'configure' ! option. ! 'uninstall' Uninstall files installed by installing the compiler. This is currently documented not to be supported, so the hook need not do anything. ! 'mostlyclean' ! 'clean' ! 'distclean' ! 'maintainer-clean' ! The language parts of the standard GNU '*clean' targets. *Note Standard Targets for Users: (standards)Standard Targets, for ! details of the standard targets. For GCC, 'maintainer-clean' should delete all generated files in the source directory that are not version-controlled, but should not delete anything that is. ! 'Make-lang.in' must also define a variable 'LANG_OBJS' to a list of host object files that are used by that language.  --- 3882,4126 ---- following are also necessary: * At least one Bugzilla component for bugs in that front end and ! runtime libraries. This category needs to be added to the ! Bugzilla database. ! * Normally, one or more maintainers of that front end listed in ! `MAINTAINERS'. ! ! * Mentions on the GCC web site in `index.html' and `frontends.html', ! with any relevant links on `readings.html'. (Front ends that are ! not an official part of GCC may also be listed on ! `frontends.html', with relevant links.) ! ! * A news item on `index.html', and possibly an announcement on the mailing list. + * The front end's manuals should be mentioned in ! `maintainer-scripts/update_web_docs_svn' (*note Texinfo Manuals::) and the online manuals should be linked to from ! `onlinedocs/index.html'. ! * Any old releases or CVS repositories of the front end, before its inclusion in GCC, should be made available on the GCC FTP site ! `ftp://gcc.gnu.org/pub/gcc/old-releases/'. ! ! * The release and snapshot script `maintainer-scripts/gcc_release' should be updated to generate appropriate tarballs for this front end. + * If this front end includes its own version files that include the ! current date, `maintainer-scripts/update_version' should be ! updated accordingly. * Menu: ! * Front End Directory:: The front end `LANGUAGE' directory. ! * Front End Config:: The front end `config-lang.in' file. ! * Front End Makefile:: The front end `Make-lang.in' file.  File: gccint.info, Node: Front End Directory, Next: Front End Config, Up: Front End ! 6.3.8.1 The Front End `LANGUAGE' Directory .......................................... ! A front end `LANGUAGE' directory contains the source files of that ! front end (but not of any runtime libraries, which should be outside ! the `gcc' directory). This includes documentation, and possibly some ! subsidiary programs built alongside the front end. Certain files are ! special and other parts of the compiler depend on their names: ! `config-lang.in' This file is required in all language subdirectories. *Note The ! Front End `config-lang.in' File: Front End Config, for details of its contents ! ! `Make-lang.in' This file is required in all language subdirectories. *Note The ! Front End `Make-lang.in' File: Front End Makefile, for details of its contents. ! ! `lang.opt' This file registers the set of switches that the front end accepts ! on the command line, and their `--help' text. *Note Options::. ! ! `lang-specs.h' ! This file provides entries for `default_compilers' in `gcc.c' ! which override the default of giving an error that a compiler for ! that language is not installed. ! ! `LANGUAGE-tree.def' This file, which need not exist, defines any language-specific tree codes.  File: gccint.info, Node: Front End Config, Next: Front End Makefile, Prev: Front End Directory, Up: Front End ! 6.3.8.2 The Front End `config-lang.in' File ........................................... ! Each language subdirectory contains a `config-lang.in' file. This file is a shell script that may define some variables describing the language: ! `language' This definition must be present, and gives the name of the language ! for some purposes such as arguments to `--enable-languages'. ! ! `lang_requires' If defined, this variable lists (space-separated) language front ends other than C that this front end requires to be enabled (with ! the names given being their `language' settings). For example, the Java front end depends on the C++ front end, so sets ! `lang_requires=c++'. ! ! `subdir_requires' If defined, this variable lists (space-separated) front end directories other than C that this front end requires to be present. For example, the Objective-C++ front end uses source files from the C++ and Objective-C front ends, so sets ! `subdir_requires="cp objc"'. ! ! `target_libs' If defined, this variable lists (space-separated) targets in the ! top level `Makefile' to build the runtime libraries for this ! language, such as `target-libobjc'. ! ! `lang_dirs' If defined, this variable lists (space-separated) top level ! directories (parallel to `gcc'), apart from the runtime libraries, that should not be configured if this front end is not built. ! ! `build_by_default' ! If defined to `no', this language front end is not built unless ! enabled in a `--enable-languages' argument. Otherwise, front ends are built by default, subject to any special logic in ! `configure.ac' (as is present to disable the Ada front end if the Ada compiler is not already installed). ! ! `boot_language' ! If defined to `yes', this front end is built in stage1 of the bootstrap. This is only relevant to front ends written in their own languages. ! ! `compilers' If defined, a space-separated list of compiler executables that will be run by the driver. The names here will each end with ! `\$(exeext)'. ! ! `outputs' If defined, a space-separated list of files that should be ! generated by `configure' substituting values in them. This ! mechanism can be used to create a file `LANGUAGE/Makefile' from ! `LANGUAGE/Makefile.in', but this is deprecated, building ! everything from the single `gcc/Makefile' is preferred. ! ! `gtfiles' If defined, a space-separated list of files that should be scanned ! by `gengtype.c' to generate the garbage collection tables and routines for this language. This excludes the files that are common to all front ends. *Note Type Information::. +  File: gccint.info, Node: Front End Makefile, Prev: Front End Config, Up: Front End ! 6.3.8.3 The Front End `Make-lang.in' File ......................................... ! Each language subdirectory contains a `Make-lang.in' file. It contains ! targets `LANG.HOOK' (where `LANG' is the setting of `language' in ! `config-lang.in') for the following values of `HOOK', and any other Makefile rules required to build those targets (which may if necessary ! use other Makefiles specified in `outputs' in `config-lang.in', ! although this is deprecated). It also adds any testsuite targets that ! can use the standard rule in `gcc/Makefile.in' to the variable ! `lang_checks'. ! `all.cross' ! `start.encap' ! `rest.encap' FIXME: exactly what goes in each of these targets? ! ! `tags' ! Build an `etags' `TAGS' file in the language subdirectory in the source tree. ! ! `info' Build info documentation for the front end, in the build directory. ! This target is only called by `make bootstrap' if a suitable ! version of `makeinfo' is available, so does not need to check for this, and should fail if an error occurs. ! ! `dvi' Build DVI documentation for the front end, in the build directory. ! This should be done using `$(TEXI2DVI)', with appropriate `-I' arguments pointing to directories of included files. ! ! `pdf' Build PDF documentation for the front end, in the build directory. ! This should be done using `$(TEXI2PDF)', with appropriate `-I' arguments pointing to directories of included files. ! ! `html' Build HTML documentation for the front end, in the build directory. ! ! `man' Build generated man pages for the front end from Texinfo manuals (*note Man Page Generation::), in the build directory. This target is only called if the necessary tools are available, but should ignore errors so as not to stop the build if errors occur; man pages are optional and the tools involved may be installed in a broken way. ! ! `install-common' Install everything that is part of the front end, apart from the ! compiler executables listed in `compilers' in `config-lang.in'. ! ! `install-info' Install info documentation for the front end, if it is present in ! the source directory. This target should have dependencies on ! info files that should be installed. ! ! `install-man' Install man pages for the front end. This target should ignore errors. ! ! `install-plugin' Install headers needed for plugins. ! ! `srcextra' Copies its dependencies into the source directory. This generally ! should be used for generated files such as Bison output files ! which are not version-controlled, but should be included in any ! release tarballs. This target will be executed during a bootstrap ! if `--enable-generated-files-in-srcdir' was specified as a ! `configure' option. ! ! `srcinfo' ! `srcman' Copies its dependencies into the source directory. These targets will be executed during a bootstrap if ! `--enable-generated-files-in-srcdir' was specified as a ! `configure' option. ! ! `uninstall' Uninstall files installed by installing the compiler. This is currently documented not to be supported, so the hook need not do anything. ! ! `mostlyclean' ! `clean' ! `distclean' ! `maintainer-clean' ! The language parts of the standard GNU `*clean' targets. *Note Standard Targets for Users: (standards)Standard Targets, for ! details of the standard targets. For GCC, `maintainer-clean' should delete all generated files in the source directory that are not version-controlled, but should not delete anything that is. ! `Make-lang.in' must also define a variable `LANG_OBJS' to a list of host object files that are used by that language.  *************** File: gccint.info, Node: Back End, Pre *** 4054,4121 **** A back end for a target architecture in GCC has the following parts: ! * A directory 'MACHINE' under 'gcc/config', containing a machine ! description 'MACHINE.md' file (*note Machine Descriptions: Machine ! Desc.), header files 'MACHINE.h' and 'MACHINE-protos.h' and a ! source file 'MACHINE.c' (*note Target Description Macros and Functions: Target Macros.), possibly a target Makefile fragment ! 't-MACHINE' (*note The Target Makefile Fragment: Target Fragment.), ! and maybe some other files. The names of these files may be ! changed from the defaults given by explicit specifications in ! 'config.gcc'. ! * If necessary, a file 'MACHINE-modes.def' in the 'MACHINE' directory, containing additional machine modes to represent condition codes. *Note Condition Code::, for further details. ! * An optional 'MACHINE.opt' file in the 'MACHINE' directory, containing a list of target-specific options. You can also add ! other option files using the 'extra_options' variable in ! 'config.gcc'. *Note Options::. ! * Entries in 'config.gcc' (*note The 'config.gcc' File: System Config.) for the systems with this target architecture. ! * Documentation in 'gcc/doc/invoke.texi' for any command-line options ! supported by this target (*note Run-time Target Specification: ! Run-time Target.). This means both entries in the summary table of ! options and details of the individual options. ! * Documentation in 'gcc/doc/extend.texi' for any target-specific attributes supported (*note Defining target-specific uses of ! '__attribute__': Target Attributes.), including where the same attribute is already supported on some targets, which are enumerated in the manual. ! * Documentation in 'gcc/doc/extend.texi' for any target-specific pragmas supported. ! * Documentation in 'gcc/doc/extend.texi' of any target-specific built-in functions supported. ! * Documentation in 'gcc/doc/extend.texi' of any target-specific format checking styles supported. ! * Documentation in 'gcc/doc/md.texi' of any target-specific constraint letters (*note Constraints for Particular Machines: Machine Constraints.). ! * A note in 'gcc/doc/contrib.texi' under the person or people who contributed the target support. ! * Entries in 'gcc/doc/install.texi' for all target triplets supported ! with this target architecture, giving details of any special notes ! about installation for this target, or saying that there are no ! special notes if there are none. ! * Possibly other support outside the 'gcc' directory for runtime ! libraries. FIXME: reference docs for this. The 'libstdc++' porting manual needs to be installed as info for this to work, or to be a chapter of this manual. If the back end is added to the official GCC source repository, the following are also necessary: ! * An entry for the target architecture in 'readings.html' on the GCC web site, with any relevant links. * Details of the properties of the back end and target architecture ! in 'backends.html' on the GCC web site. * A news item about the contribution of support for that target ! architecture, in 'index.html' on the GCC web site. * Normally, one or more maintainers of that target listed in ! 'MAINTAINERS'. Some existing architectures may be unmaintained, but it would be unusual to add support for a target that does not have a maintainer when support is added. ! * Target triplets covering all 'config.gcc' stanzas for the target, ! in the list in 'contrib/config-list.mk'.  File: gccint.info, Node: Testsuites, Next: Options, Prev: Source Tree, Up: Top --- 4131,4214 ---- A back end for a target architecture in GCC has the following parts: ! * A directory `MACHINE' under `gcc/config', containing a machine ! description `MACHINE.md' file (*note Machine Descriptions: Machine ! Desc.), header files `MACHINE.h' and `MACHINE-protos.h' and a ! source file `MACHINE.c' (*note Target Description Macros and Functions: Target Macros.), possibly a target Makefile fragment ! `t-MACHINE' (*note The Target Makefile Fragment: Target ! Fragment.), and maybe some other files. The names of these files ! may be changed from the defaults given by explicit specifications ! in `config.gcc'. ! ! * If necessary, a file `MACHINE-modes.def' in the `MACHINE' directory, containing additional machine modes to represent condition codes. *Note Condition Code::, for further details. ! ! * An optional `MACHINE.opt' file in the `MACHINE' directory, containing a list of target-specific options. You can also add ! other option files using the `extra_options' variable in ! `config.gcc'. *Note Options::. ! ! * Entries in `config.gcc' (*note The `config.gcc' File: System Config.) for the systems with this target architecture. ! ! * Documentation in `gcc/doc/invoke.texi' for any command-line ! options supported by this target (*note Run-time Target ! Specification: Run-time Target.). This means both entries in the ! summary table of options and details of the individual options. ! ! * Documentation in `gcc/doc/extend.texi' for any target-specific attributes supported (*note Defining target-specific uses of ! `__attribute__': Target Attributes.), including where the same attribute is already supported on some targets, which are enumerated in the manual. ! ! * Documentation in `gcc/doc/extend.texi' for any target-specific pragmas supported. ! ! * Documentation in `gcc/doc/extend.texi' of any target-specific built-in functions supported. ! ! * Documentation in `gcc/doc/extend.texi' of any target-specific format checking styles supported. ! ! * Documentation in `gcc/doc/md.texi' of any target-specific constraint letters (*note Constraints for Particular Machines: Machine Constraints.). ! ! * A note in `gcc/doc/contrib.texi' under the person or people who contributed the target support. ! ! * Entries in `gcc/doc/install.texi' for all target triplets ! supported with this target architecture, giving details of any ! special notes about installation for this target, or saying that ! there are no special notes if there are none. ! ! * Possibly other support outside the `gcc' directory for runtime ! libraries. FIXME: reference docs for this. The `libstdc++' porting manual needs to be installed as info for this to work, or to be a chapter of this manual. If the back end is added to the official GCC source repository, the following are also necessary: ! * An entry for the target architecture in `readings.html' on the GCC web site, with any relevant links. + * Details of the properties of the back end and target architecture ! in `backends.html' on the GCC web site. ! * A news item about the contribution of support for that target ! architecture, in `index.html' on the GCC web site. ! * Normally, one or more maintainers of that target listed in ! `MAINTAINERS'. Some existing architectures may be unmaintained, but it would be unusual to add support for a target that does not have a maintainer when support is added. ! ! * Target triplets covering all `config.gcc' stanzas for the target, ! in the list in `contrib/config-list.mk'.  File: gccint.info, Node: Testsuites, Next: Options, Prev: Source Tree, Up: Top *************** File: gccint.info, Node: Testsuites, N *** 4123,4132 **** 7 Testsuites ************ ! GCC contains several testsuites to help maintain compiler quality. Most ! of the runtime libraries and language front ends in GCC have testsuites. ! Currently only the C language testsuites are documented here; FIXME: ! document the others. * Menu: --- 4216,4225 ---- 7 Testsuites ************ ! GCC contains several testsuites to help maintain compiler quality. ! Most of the runtime libraries and language front ends in GCC have ! testsuites. Currently only the C language testsuites are documented ! here; FIXME: document the others. * Menu: *************** File: gccint.info, Node: Test Idioms, *** 4147,4188 **** 7.1 Idioms Used in Testsuite Code ================================= ! In general, C testcases have a trailing '-N.c', starting with '-1.c', in ! case other testcases with similar names are added later. If the test is ! a test of some well-defined feature, it should have a name referring to ! that feature such as 'FEATURE-1.c'. If it does not test a well-defined ! feature but just happens to exercise a bug somewhere in the compiler, ! and a bug report has been filed for this bug in the GCC bug database, ! 'prBUG-NUMBER-1.c' is the appropriate form of name. Otherwise (for ! miscellaneous bugs not filed in the GCC bug database), and previously ! more generally, test cases are named after the date on which they were ! added. This allows people to tell at a glance whether a test failure is ! because of a recently found bug that has not yet been fixed, or whether ! it may be a regression, but does not give any other information about ! the bug or where discussion of it may be found. Some other language ! testsuites follow similar conventions. ! In the 'gcc.dg' testsuite, it is often necessary to test that an error is indeed a hard error and not just a warning--for example, where it is a constraint violation in the C standard, which must become an error ! with '-pedantic-errors'. The following idiom, where the first line ! shown is line LINE of the file and the line that generates the error, is ! used for this: /* { dg-bogus "warning" "warning in place of error" } */ /* { dg-error "REGEXP" "MESSAGE" { target *-*-* } LINE } */ It may be necessary to check that an expression is an integer constant ! expression and has a certain value. To check that 'E' has value 'V', an ! idiom similar to the following is used: char x[((E) == (V) ? 1 : -1)]; ! In 'gcc.dg' tests, '__typeof__' is sometimes used to make assertions about the types of expressions. See, for example, ! 'gcc.dg/c99-condexpr-1.c'. The more subtle uses depend on the exact rules for the types of conditional expressions in the C standard; see, ! for example, 'gcc.dg/c99-intconst-1.c'. It is useful to be able to test that optimizations are being made properly. This cannot be done in all cases, but it can be done where --- 4240,4281 ---- 7.1 Idioms Used in Testsuite Code ================================= ! In general, C testcases have a trailing `-N.c', starting with `-1.c', ! in case other testcases with similar names are added later. If the ! test is a test of some well-defined feature, it should have a name ! referring to that feature such as `FEATURE-1.c'. If it does not test a ! well-defined feature but just happens to exercise a bug somewhere in ! the compiler, and a bug report has been filed for this bug in the GCC ! bug database, `prBUG-NUMBER-1.c' is the appropriate form of name. ! Otherwise (for miscellaneous bugs not filed in the GCC bug database), ! and previously more generally, test cases are named after the date on ! which they were added. This allows people to tell at a glance whether ! a test failure is because of a recently found bug that has not yet been ! fixed, or whether it may be a regression, but does not give any other ! information about the bug or where discussion of it may be found. Some ! other language testsuites follow similar conventions. ! In the `gcc.dg' testsuite, it is often necessary to test that an error is indeed a hard error and not just a warning--for example, where it is a constraint violation in the C standard, which must become an error ! with `-pedantic-errors'. The following idiom, where the first line ! shown is line LINE of the file and the line that generates the error, ! is used for this: /* { dg-bogus "warning" "warning in place of error" } */ /* { dg-error "REGEXP" "MESSAGE" { target *-*-* } LINE } */ It may be necessary to check that an expression is an integer constant ! expression and has a certain value. To check that `E' has value `V', ! an idiom similar to the following is used: char x[((E) == (V) ? 1 : -1)]; ! In `gcc.dg' tests, `__typeof__' is sometimes used to make assertions about the types of expressions. See, for example, ! `gcc.dg/c99-condexpr-1.c'. The more subtle uses depend on the exact rules for the types of conditional expressions in the C standard; see, ! for example, `gcc.dg/c99-intconst-1.c'. It is useful to be able to test that optimizations are being made properly. This cannot be done in all cases, but it can be done where *************** the optimization will lead to code being *** 4190,4197 **** where flow analysis or alias analysis should show that certain code cannot be called) or to functions not being called because they have been expanded as built-in functions. Such tests go in ! 'gcc.c-torture/execute'. Where code should be optimized away, a call to ! a nonexistent function such as 'link_failure ()' may be inserted; a definition #ifndef __OPTIMIZE__ --- 4283,4290 ---- where flow analysis or alias analysis should show that certain code cannot be called) or to functions not being called because they have been expanded as built-in functions. Such tests go in ! `gcc.c-torture/execute'. Where code should be optimized away, a call ! to a nonexistent function such as `link_failure ()' may be inserted; a definition #ifndef __OPTIMIZE__ *************** definition *** 4203,4213 **** #endif will also be needed so that linking still succeeds when the test is run ! without optimization. When all calls to a built-in function should have ! been optimized and no calls to the non-built-in version of the function ! should remain, that function may be defined as 'static' to call 'abort ! ()' (although redeclaring a function as static may not work on all ! targets). All testcases must be portable. Target-specific testcases must have appropriate code to avoid causing failures on unsupported systems; --- 4296,4306 ---- #endif will also be needed so that linking still succeeds when the test is run ! without optimization. When all calls to a built-in function should ! have been optimized and no calls to the non-built-in version of the ! function should remain, that function may be defined as `static' to ! call `abort ()' (although redeclaring a function as static may not work ! on all targets). All testcases must be portable. Target-specific testcases must have appropriate code to avoid causing failures on unsupported systems; *************** File: gccint.info, Node: Test Directive *** 4226,4234 **** * Directives:: Syntax and descriptions of test directives. * Selectors:: Selecting targets to which a test applies. * Effective-Target Keywords:: Keywords describing target attributes. ! * Add Options:: Features for 'dg-add-options' ! * Require Support:: Variants of 'dg-require-SUPPORT' ! * Final Actions:: Commands for use in 'dg-final'  File: gccint.info, Node: Directives, Next: Selectors, Up: Test Directives --- 4319,4327 ---- * Directives:: Syntax and descriptions of test directives. * Selectors:: Selecting targets to which a test applies. * Effective-Target Keywords:: Keywords describing target attributes. ! * Add Options:: Features for `dg-add-options' ! * Require Support:: Variants of `dg-require-SUPPORT' ! * Final Actions:: Commands for use in `dg-final'  File: gccint.info, Node: Directives, Next: Selectors, Up: Test Directives *************** File: gccint.info, Node: Directives, N *** 4237,4243 **** ------------------------------------------------ Test directives appear within comments in a test source file and begin ! with 'dg-'. Some of these are defined within DejaGnu and others are local to the GCC testsuite. The order in which test directives appear in a test can be important: --- 4330,4336 ---- ------------------------------------------------ Test directives appear within comments in a test source file and begin ! with `dg-'. Some of these are defined within DejaGnu and others are local to the GCC testsuite. The order in which test directives appear in a test can be important: *************** directives local to GCC sometimes overri *** 4245,4300 **** DejaGnu directives, which know nothing about the GCC directives, so the DejaGnu directives must precede GCC directives. ! Several test directives include selectors (*note Selectors::) which are ! usually preceded by the keyword 'target' or 'xfail'. 7.2.1.1 Specify how to build the test ..................................... ! '{ dg-do DO-WHAT-KEYWORD [{ target/xfail SELECTOR }] }' DO-WHAT-KEYWORD specifies how the test is compiled and whether it is executed. It is one of: ! 'preprocess' ! Compile with '-E' to run only the preprocessor. ! 'compile' ! Compile with '-S' to produce an assembly code file. ! 'assemble' ! Compile with '-c' to produce a relocatable object file. ! 'link' Compile, assemble, and link to produce an executable file. ! 'run' Produce and run an executable file, which is expected to return an exit code of 0. ! The default is 'compile'. That can be overridden for a set of ! tests by redefining 'dg-do-what-default' within the '.exp' file for ! those tests. ! If the directive includes the optional '{ target SELECTOR }' then the test is skipped unless the target system matches the SELECTOR. ! If DO-WHAT-KEYWORD is 'run' and the directive includes the optional ! '{ xfail SELECTOR }' and the selector is met then the test is ! expected to fail. The 'xfail' clause is ignored for other values ! of DO-WHAT-KEYWORD; those tests can use directive 'dg-xfail-if'. 7.2.1.2 Specify additional compiler options ........................................... ! '{ dg-options OPTIONS [{ target SELECTOR }] }' This DejaGnu directive provides a list of compiler options, to be used if the target system matches SELECTOR, that replace the default options used for this set of tests. ! '{ dg-add-options FEATURE ... }' Add any compiler options that are needed to access certain features. This directive does nothing on targets that enable the features by default, or that don't provide them at all. It must ! come after all 'dg-options' directives. For supported values of FEATURE see *note Add Options::. ! '{ dg-additional-options OPTIONS [{ target SELECTOR }] }' This directive provides a list of compiler options, to be used if the target system matches SELECTOR, that are added to the default options used for this set of tests. --- 4338,4398 ---- DejaGnu directives, which know nothing about the GCC directives, so the DejaGnu directives must precede GCC directives. ! Several test directives include selectors (*note Selectors::) which ! are usually preceded by the keyword `target' or `xfail'. 7.2.1.1 Specify how to build the test ..................................... ! `{ dg-do DO-WHAT-KEYWORD [{ target/xfail SELECTOR }] }' DO-WHAT-KEYWORD specifies how the test is compiled and whether it is executed. It is one of: ! `preprocess' ! Compile with `-E' to run only the preprocessor. ! ! `compile' ! Compile with `-S' to produce an assembly code file. ! ! `assemble' ! Compile with `-c' to produce a relocatable object file. ! ! `link' Compile, assemble, and link to produce an executable file. ! ! `run' Produce and run an executable file, which is expected to return an exit code of 0. ! The default is `compile'. That can be overridden for a set of ! tests by redefining `dg-do-what-default' within the `.exp' file ! for those tests. ! If the directive includes the optional `{ target SELECTOR }' then the test is skipped unless the target system matches the SELECTOR. ! If DO-WHAT-KEYWORD is `run' and the directive includes the ! optional `{ xfail SELECTOR }' and the selector is met then the ! test is expected to fail. The `xfail' clause is ignored for other ! values of DO-WHAT-KEYWORD; those tests can use directive ! `dg-xfail-if'. 7.2.1.2 Specify additional compiler options ........................................... ! `{ dg-options OPTIONS [{ target SELECTOR }] }' This DejaGnu directive provides a list of compiler options, to be used if the target system matches SELECTOR, that replace the default options used for this set of tests. ! `{ dg-add-options FEATURE ... }' Add any compiler options that are needed to access certain features. This directive does nothing on targets that enable the features by default, or that don't provide them at all. It must ! come after all `dg-options' directives. For supported values of FEATURE see *note Add Options::. ! `{ dg-additional-options OPTIONS [{ target SELECTOR }] }' This directive provides a list of compiler options, to be used if the target system matches SELECTOR, that are added to the default options used for this set of tests. *************** usually preceded by the keyword 'target' *** 4305,4311 **** The normal timeout limit, in seconds, is found by searching the following in order: ! * the value defined by an earlier 'dg-timeout' directive in the test * variable TOOL_TIMEOUT defined by the set of tests --- 4403,4409 ---- The normal timeout limit, in seconds, is found by searching the following in order: ! * the value defined by an earlier `dg-timeout' directive in the test * variable TOOL_TIMEOUT defined by the set of tests *************** following in order: *** 4313,4330 **** * 300 ! '{ dg-timeout N [{target SELECTOR }] }' ! Set the time limit for the compilation and for the execution of the ! test to the specified number of seconds. ! '{ dg-timeout-factor X [{ target SELECTOR }] }' ! Multiply the normal time limit for compilation and execution of the ! test by the specified floating-point factor. 7.2.1.4 Skip a test for some targets .................................... ! '{ dg-skip-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }' Arguments INCLUDE-OPTS and EXCLUDE-OPTS are lists in which each element is a string of zero or more GCC options. Skip the test if all of the following conditions are met: --- 4411,4428 ---- * 300 ! `{ dg-timeout N [{target SELECTOR }] }' ! Set the time limit for the compilation and for the execution of ! the test to the specified number of seconds. ! `{ dg-timeout-factor X [{ target SELECTOR }] }' ! Multiply the normal time limit for compilation and execution of ! the test by the specified floating-point factor. 7.2.1.4 Skip a test for some targets .................................... ! `{ dg-skip-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }' Arguments INCLUDE-OPTS and EXCLUDE-OPTS are lists in which each element is a string of zero or more GCC options. Skip the test if all of the following conditions are met: *************** following in order: *** 4332,4381 **** * for at least one of the option strings in INCLUDE-OPTS, every option from that string is in the set of options with which ! the test would be compiled; use '"*"' for an INCLUDE-OPTS list that matches any options; that is the default if INCLUDE-OPTS is not specified * for each of the option strings in EXCLUDE-OPTS, at least one option from that string is not in the set of options with ! which the test would be compiled; use '""' for an empty EXCLUDE-OPTS list; that is the default if EXCLUDE-OPTS is not specified ! For example, to skip a test if option '-Os' is present: /* { dg-skip-if "" { *-*-* } { "-Os" } { "" } } */ ! To skip a test if both options '-O2' and '-g' are present: /* { dg-skip-if "" { *-*-* } { "-O2 -g" } { "" } } */ ! To skip a test if either '-O2' or '-O3' is present: /* { dg-skip-if "" { *-*-* } { "-O2" "-O3" } { "" } } */ ! To skip a test unless option '-Os' is present: /* { dg-skip-if "" { *-*-* } { "*" } { "-Os" } } */ ! To skip a test if either '-O2' or '-O3' is used with '-g' but not ! if '-fpic' is also present: /* { dg-skip-if "" { *-*-* } { "-O2 -g" "-O3 -g" } { "-fpic" } } */ ! '{ dg-require-effective-target KEYWORD [{ SELECTOR }] }' Skip the test if the test target, including current multilib flags, is not covered by the effective-target keyword. If the directive ! includes the optional '{ SELECTOR }' then the effective-target test ! is only performed if the target system matches the SELECTOR. This ! directive must appear after any 'dg-do' directive in the test and ! before any 'dg-additional-sources' directive. *Note Effective-Target Keywords::. ! '{ dg-require-SUPPORT args }' Skip the test if the target does not provide the required support. ! These directives must appear after any 'dg-do' directive in the ! test and before any 'dg-additional-sources' directive. They require at least one argument, which can be an empty string if the specific procedure does not examine the argument. *Note Require Support::, for a complete list of these directives. --- 4430,4479 ---- * for at least one of the option strings in INCLUDE-OPTS, every option from that string is in the set of options with which ! the test would be compiled; use `"*"' for an INCLUDE-OPTS list that matches any options; that is the default if INCLUDE-OPTS is not specified * for each of the option strings in EXCLUDE-OPTS, at least one option from that string is not in the set of options with ! which the test would be compiled; use `""' for an empty EXCLUDE-OPTS list; that is the default if EXCLUDE-OPTS is not specified ! For example, to skip a test if option `-Os' is present: /* { dg-skip-if "" { *-*-* } { "-Os" } { "" } } */ ! To skip a test if both options `-O2' and `-g' are present: /* { dg-skip-if "" { *-*-* } { "-O2 -g" } { "" } } */ ! To skip a test if either `-O2' or `-O3' is present: /* { dg-skip-if "" { *-*-* } { "-O2" "-O3" } { "" } } */ ! To skip a test unless option `-Os' is present: /* { dg-skip-if "" { *-*-* } { "*" } { "-Os" } } */ ! To skip a test if either `-O2' or `-O3' is used with `-g' but not ! if `-fpic' is also present: /* { dg-skip-if "" { *-*-* } { "-O2 -g" "-O3 -g" } { "-fpic" } } */ ! `{ dg-require-effective-target KEYWORD [{ SELECTOR }] }' Skip the test if the test target, including current multilib flags, is not covered by the effective-target keyword. If the directive ! includes the optional `{ SELECTOR }' then the effective-target ! test is only performed if the target system matches the SELECTOR. ! This directive must appear after any `dg-do' directive in the test ! and before any `dg-additional-sources' directive. *Note Effective-Target Keywords::. ! `{ dg-require-SUPPORT args }' Skip the test if the target does not provide the required support. ! These directives must appear after any `dg-do' directive in the ! test and before any `dg-additional-sources' directive. They require at least one argument, which can be an empty string if the specific procedure does not examine the argument. *Note Require Support::, for a complete list of these directives. *************** following in order: *** 4383,4471 **** 7.2.1.5 Expect a test to fail for some targets .............................................. ! '{ dg-xfail-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }' Expect the test to fail if the conditions (which are the same as ! for 'dg-skip-if') are met. This does not affect the execute step. ! '{ dg-xfail-run-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }' Expect the execute step of a test to fail if the conditions (which ! are the same as for 'dg-skip-if') are met. 7.2.1.6 Expect the test executable to fail .......................................... ! '{ dg-shouldfail COMMENT [{ SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]]] }' Expect the test executable to return a nonzero exit status if the ! conditions (which are the same as for 'dg-skip-if') are met. 7.2.1.7 Verify compiler messages ................................ ! '{ dg-error REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' ! This DejaGnu directive appears on a source line that is expected to ! get an error message, or else specifies the source line associated ! with the message. If there is no message for that line or if the ! text of that message is not matched by REGEXP then the check fails ! and COMMENT is included in the 'FAIL' message. The check does not ! look for the string 'error' unless it is part of REGEXP. ! '{ dg-warning REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' ! This DejaGnu directive appears on a source line that is expected to ! get a warning message, or else specifies the source line associated ! with the message. If there is no message for that line or if the ! text of that message is not matched by REGEXP then the check fails ! and COMMENT is included in the 'FAIL' message. The check does not ! look for the string 'warning' unless it is part of REGEXP. ! '{ dg-message REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' The line is expected to get a message other than an error or warning. If there is no message for that line or if the text of that message is not matched by REGEXP then the check fails and ! COMMENT is included in the 'FAIL' message. ! '{ dg-bogus REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' ! This DejaGnu directive appears on a source line that should not get ! a message matching REGEXP, or else specifies the source line ! associated with the bogus message. It is usually used with 'xfail' to indicate that the message is a known problem for a particular set of targets. ! '{ dg-excess-errors COMMENT [{ target/xfail SELECTOR }] }' This DejaGnu directive indicates that the test is expected to fail ! due to compiler messages that are not handled by 'dg-error', ! 'dg-warning' or 'dg-bogus'. For this directive 'xfail' has the ! same effect as 'target'. ! '{ dg-prune-output REGEXP }' Prune messages matching REGEXP from the test output. 7.2.1.8 Verify output of the test executable ............................................ ! '{ dg-output REGEXP [{ target/xfail SELECTOR }] }' This DejaGnu directive compares REGEXP to the combined output that ! the test executable writes to 'stdout' and 'stderr'. 7.2.1.9 Specify additional files for a test ........................................... ! '{ dg-additional-files "FILELIST" }' Specify additional files, other than source files, that must be copied to the system where the compiler runs. ! '{ dg-additional-sources "FILELIST" }' Specify additional source files to appear in the compile line following the main test file. 7.2.1.10 Add checks at the end of a test ........................................ ! '{ dg-final { LOCAL-DIRECTIVE } }' This DejaGnu directive is placed within a comment anywhere in the source file and is processed after the test has been compiled and ! run. Multiple 'dg-final' commands are processed in the order in ! which they appear in the source file. *Note Final Actions::, for a ! list of directives that can be used within 'dg-final'.  File: gccint.info, Node: Selectors, Next: Effective-Target Keywords, Prev: Directives, Up: Test Directives --- 4481,4571 ---- 7.2.1.5 Expect a test to fail for some targets .............................................. ! `{ dg-xfail-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }' Expect the test to fail if the conditions (which are the same as ! for `dg-skip-if') are met. This does not affect the execute step. ! `{ dg-xfail-run-if COMMENT { SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]] }' Expect the execute step of a test to fail if the conditions (which ! are the same as for `dg-skip-if') are met. 7.2.1.6 Expect the test executable to fail .......................................... ! `{ dg-shouldfail COMMENT [{ SELECTOR } [{ INCLUDE-OPTS } [{ EXCLUDE-OPTS }]]] }' Expect the test executable to return a nonzero exit status if the ! conditions (which are the same as for `dg-skip-if') are met. 7.2.1.7 Verify compiler messages ................................ ! `{ dg-error REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' ! This DejaGnu directive appears on a source line that is expected ! to get an error message, or else specifies the source line ! associated with the message. If there is no message for that line ! or if the text of that message is not matched by REGEXP then the ! check fails and COMMENT is included in the `FAIL' message. The ! check does not look for the string `error' unless it is part of ! REGEXP. ! `{ dg-warning REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' ! This DejaGnu directive appears on a source line that is expected ! to get a warning message, or else specifies the source line ! associated with the message. If there is no message for that line ! or if the text of that message is not matched by REGEXP then the ! check fails and COMMENT is included in the `FAIL' message. The ! check does not look for the string `warning' unless it is part of ! REGEXP. ! `{ dg-message REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' The line is expected to get a message other than an error or warning. If there is no message for that line or if the text of that message is not matched by REGEXP then the check fails and ! COMMENT is included in the `FAIL' message. ! `{ dg-bogus REGEXP [COMMENT [{ target/xfail SELECTOR } [LINE] }]] }' ! This DejaGnu directive appears on a source line that should not ! get a message matching REGEXP, or else specifies the source line ! associated with the bogus message. It is usually used with `xfail' to indicate that the message is a known problem for a particular set of targets. ! `{ dg-excess-errors COMMENT [{ target/xfail SELECTOR }] }' This DejaGnu directive indicates that the test is expected to fail ! due to compiler messages that are not handled by `dg-error', ! `dg-warning' or `dg-bogus'. For this directive `xfail' has the ! same effect as `target'. ! `{ dg-prune-output REGEXP }' Prune messages matching REGEXP from the test output. 7.2.1.8 Verify output of the test executable ............................................ ! `{ dg-output REGEXP [{ target/xfail SELECTOR }] }' This DejaGnu directive compares REGEXP to the combined output that ! the test executable writes to `stdout' and `stderr'. 7.2.1.9 Specify additional files for a test ........................................... ! `{ dg-additional-files "FILELIST" }' Specify additional files, other than source files, that must be copied to the system where the compiler runs. ! `{ dg-additional-sources "FILELIST" }' Specify additional source files to appear in the compile line following the main test file. 7.2.1.10 Add checks at the end of a test ........................................ ! `{ dg-final { LOCAL-DIRECTIVE } }' This DejaGnu directive is placed within a comment anywhere in the source file and is processed after the test has been compiled and ! run. Multiple `dg-final' commands are processed in the order in ! which they appear in the source file. *Note Final Actions::, for ! a list of directives that can be used within `dg-final'.  File: gccint.info, Node: Selectors, Next: Effective-Target Keywords, Prev: Directives, Up: Test Directives *************** File: gccint.info, Node: Selectors, Ne *** 4473,4497 **** 7.2.2 Selecting targets to which a test applies ----------------------------------------------- ! Several test directives include SELECTORs to limit the targets for which ! a test is run or to declare that a test is expected to fail on particular targets. A selector is: * one or more target triplets, possibly including wildcard ! characters; use '*-*-*' to match any target * a single effective-target keyword (*note Effective-Target Keywords::) * a logical expression Depending on the context, the selector specifies whether a test is skipped and reported as unsupported or is expected to fail. A context ! that allows either 'target' or 'xfail' also allows '{ target SELECTOR1 xfail SELECTOR2 }' to skip the test for targets that don't match SELECTOR1 and the test to fail for targets that match SELECTOR2. A selector expression appears within curly braces and uses a single ! logical operator: one of '!', '&&', or '||'. An operand is another selector expression, an effective-target keyword, a single target triplet, or a list of target triplets within quotes or curly braces. For example: --- 4573,4599 ---- 7.2.2 Selecting targets to which a test applies ----------------------------------------------- ! Several test directives include SELECTORs to limit the targets for ! which a test is run or to declare that a test is expected to fail on particular targets. A selector is: * one or more target triplets, possibly including wildcard ! characters; use `*-*-*' to match any target ! * a single effective-target keyword (*note Effective-Target Keywords::) + * a logical expression Depending on the context, the selector specifies whether a test is skipped and reported as unsupported or is expected to fail. A context ! that allows either `target' or `xfail' also allows `{ target SELECTOR1 xfail SELECTOR2 }' to skip the test for targets that don't match SELECTOR1 and the test to fail for targets that match SELECTOR2. A selector expression appears within curly braces and uses a single ! logical operator: one of `!', `&&', or `||'. An operand is another selector expression, an effective-target keyword, a single target triplet, or a list of target triplets within quotes or curly braces. For example: *************** particular functionality. They are used *** 4511,5516 **** for particular targets, or to specify that particular sets of targets are expected to fail some tests. ! Effective-target keywords are defined in 'lib/target-supports.exp' in the GCC testsuite, with the exception of those that are documented as being local to a particular test directory. ! The 'effective target' takes into account all of the compiler options with which the test will be compiled, including the multilib options. ! By convention, keywords ending in '_nocache' can also include options ! specified for the particular test in an earlier 'dg-options' or ! 'dg-add-options' directive. 7.2.3.1 Data type sizes ....................... ! 'ilp32' ! Target has 32-bit 'int', 'long', and pointers. ! 'lp64' ! Target has 32-bit 'int', 64-bit 'long' and pointers. ! 'llp64' ! Target has 32-bit 'int' and 'long', 64-bit 'long long' and pointers. ! 'double64' ! Target has 64-bit 'double'. ! 'double64plus' ! Target has 'double' that is 64 bits or longer. ! 'longdouble128' ! Target has 128-bit 'long double'. ! 'int32plus' ! Target has 'int' that is at 32 bits or longer. ! 'int16' ! Target has 'int' that is 16 bits or shorter. ! 'long_neq_int' ! Target has 'int' and 'long' with different sizes. ! 'large_double' ! Target supports 'double' that is longer than 'float'. ! 'large_long_double' ! Target supports 'long double' that is longer than 'double'. ! 'ptr32plus' Target has pointers that are 32 bits or longer. ! 'size32plus' Target supports array and structure sizes that are 32 bits or longer. ! '4byte_wchar_t' ! Target has 'wchar_t' that is at least 4 bytes. 7.2.3.2 Fortran-specific attributes ................................... ! 'fortran_integer_16' ! Target supports Fortran 'integer' that is 16 bytes or longer. ! 'fortran_large_int' ! Target supports Fortran 'integer' kinds larger than 'integer(8)'. ! 'fortran_large_real' ! Target supports Fortran 'real' kinds larger than 'real(8)'. 7.2.3.3 Vector-specific attributes .................................. ! 'vect_condition' Target supports vector conditional operations. ! 'vect_double' ! Target supports hardware vectors of 'double'. ! 'vect_float' ! Target supports hardware vectors of 'float'. ! 'vect_int' ! Target supports hardware vectors of 'int'. ! 'vect_long' ! Target supports hardware vectors of 'long'. ! 'vect_long_long' ! Target supports hardware vectors of 'long long'. ! 'vect_aligned_arrays' Target aligns arrays to vector alignment boundary. ! 'vect_hw_misalign' Target supports a vector misalign access. ! 'vect_no_align' Target does not support a vector alignment mechanism. ! 'vect_no_int_min_max' ! Target does not support a vector min and max instruction on 'int'. ! 'vect_no_int_add' ! Target does not support a vector add instruction on 'int'. ! 'vect_no_bitwise' Target does not support vector bitwise instructions. ! 'vect_char_mult' ! Target supports 'vector char' multiplication. ! 'vect_short_mult' ! Target supports 'vector short' multiplication. ! 'vect_int_mult' ! Target supports 'vector int' multiplication. ! 'vect_extract_even_odd' Target supports vector even/odd element extraction. ! 'vect_extract_even_odd_wide' Target supports vector even/odd element extraction of vectors with ! elements 'SImode' or larger. ! 'vect_interleave' Target supports vector interleaving. ! 'vect_strided' Target supports vector interleaving and extract even/odd. ! 'vect_strided_wide' Target supports vector interleaving and extract even/odd for wide element types. ! 'vect_perm' Target supports vector permutation. ! 'vect_shift' Target supports a hardware vector shift operation. ! 'vect_widen_sum_hi_to_si' ! Target supports a vector widening summation of 'short' operands ! into 'int' results, or can promote (unpack) from 'short' to 'int'. ! 'vect_widen_sum_qi_to_hi' ! Target supports a vector widening summation of 'char' operands into ! 'short' results, or can promote (unpack) from 'char' to 'short'. ! 'vect_widen_sum_qi_to_si' ! Target supports a vector widening summation of 'char' operands into ! 'int' results. ! 'vect_widen_mult_qi_to_hi' ! Target supports a vector widening multiplication of 'char' operands ! into 'short' results, or can promote (unpack) from 'char' to ! 'short' and perform non-widening multiplication of 'short'. ! 'vect_widen_mult_hi_to_si' ! Target supports a vector widening multiplication of 'short' ! operands into 'int' results, or can promote (unpack) from 'short' ! to 'int' and perform non-widening multiplication of 'int'. ! 'vect_widen_mult_si_to_di_pattern' ! Target supports a vector widening multiplication of 'int' operands ! into 'long' results. ! 'vect_sdot_qi' ! Target supports a vector dot-product of 'signed char'. ! 'vect_udot_qi' ! Target supports a vector dot-product of 'unsigned char'. ! 'vect_sdot_hi' ! Target supports a vector dot-product of 'signed short'. ! 'vect_udot_hi' ! Target supports a vector dot-product of 'unsigned short'. ! 'vect_pack_trunc' ! Target supports a vector demotion (packing) of 'short' to 'char' ! and from 'int' to 'short' using modulo arithmetic. ! 'vect_unpack' ! Target supports a vector promotion (unpacking) of 'char' to 'short' ! and from 'char' to 'int'. ! 'vect_intfloat_cvt' ! Target supports conversion from 'signed int' to 'float'. ! 'vect_uintfloat_cvt' ! Target supports conversion from 'unsigned int' to 'float'. ! 'vect_floatint_cvt' ! Target supports conversion from 'float' to 'signed int'. ! 'vect_floatuint_cvt' ! Target supports conversion from 'float' to 'unsigned int'. ! 'vect_max_reduc' Target supports max reduction for vectors. 7.2.3.4 Thread Local Storage attributes ....................................... ! 'tls' Target supports thread-local storage. ! 'tls_native' Target supports native (rather than emulated) thread-local storage. ! 'tls_runtime' Test system supports executing TLS executables. 7.2.3.5 Decimal floating point attributes ......................................... ! 'dfp' Targets supports compiling decimal floating point extension to C. ! 'dfp_nocache' Including the options used to compile this particular test, the target supports compiling decimal floating point extension to C. ! 'dfprt' Test system can execute decimal floating point tests. ! 'dfprt_nocache' Including the options used to compile this particular test, the test system can execute decimal floating point tests. ! 'hard_dfp' Target generates decimal floating point instructions with current options. 7.2.3.6 ARM-specific attributes ............................... ! 'arm32' ARM target generates 32-bit code. ! 'arm_eabi' ARM target adheres to the ABI for the ARM Architecture. ! 'arm_fp_ok' ! ARM target defines '__ARM_FP' using '-mfloat-abi=softfp' or equivalent options. Some multilibs may be incompatible with these options. ! 'arm_hf_eabi' ARM target adheres to the VFP and Advanced SIMD Register Arguments variant of the ABI for the ARM Architecture (as selected with ! '-mfloat-abi=hard'). ! 'arm_hard_vfp_ok' ! ARM target supports '-mfpu=vfp -mfloat-abi=hard'. Some multilibs may be incompatible with these options. ! 'arm_iwmmxt_ok' ! ARM target supports '-mcpu=iwmmxt'. Some multilibs may be incompatible with this option. ! 'arm_neon' ARM target supports generating NEON instructions. ! 'arm_tune_string_ops_prefer_neon' Test CPU tune supports inlining string operations with NEON instructions. ! 'arm_neon_hw' Test system supports executing NEON instructions. ! 'arm_neonv2_hw' Test system supports executing NEON v2 instructions. ! 'arm_neon_ok' ! ARM Target supports '-mfpu=neon -mfloat-abi=softfp' or compatible options. Some multilibs may be incompatible with these options. ! 'arm_neonv2_ok' ! ARM Target supports '-mfpu=neon-vfpv4 -mfloat-abi=softfp' or compatible options. Some multilibs may be incompatible with these options. ! 'arm_neon_fp16_ok' ! ARM Target supports '-mfpu=neon-fp16 -mfloat-abi=softfp' or ! compatible options, including '-mfp16-format=ieee' if necessary to ! obtain the '__fp16' type. Some multilibs may be incompatible with these options. ! 'arm_neon_fp16_hw' Test system supports executing Neon half-precision float instructions. (Implies previous.) ! 'arm_thumb1_ok' ! ARM target generates Thumb-1 code for '-mthumb'. ! ! 'arm_thumb2_ok' ! ARM target generates Thumb-2 code for '-mthumb'. ! 'arm_vfp_ok' ! ARM target supports '-mfpu=vfp -mfloat-abi=softfp'. Some multilibs ! may be incompatible with these options. ! 'arm_vfp3_ok' ! ARM target supports '-mfpu=vfp3 -mfloat-abi=softfp'. Some multilibs may be incompatible with these options. ! 'arm_v8_vfp_ok' ! ARM target supports '-mfpu=fp-armv8 -mfloat-abi=softfp'. Some multilibs may be incompatible with these options. ! 'arm_v8_neon_ok' ! ARM target supports '-mfpu=neon-fp-armv8 -mfloat-abi=softfp'. Some multilibs may be incompatible with these options. ! 'arm_v8_1a_neon_ok' ARM target supports options to generate ARMv8.1 Adv.SIMD instructions. Some multilibs may be incompatible with these options. ! 'arm_v8_1a_neon_hw' ARM target supports executing ARMv8.1 Adv.SIMD instructions. Some multilibs may be incompatible with the options needed. Implies arm_v8_1a_neon_ok. ! 'arm_prefer_ldrd_strd' ! ARM target prefers 'LDRD' and 'STRD' instructions over 'LDM' and ! 'STM' instructions. 7.2.3.7 AArch64-specific attributes ................................... ! 'aarch64_asm__ok' ! AArch64 assembler supports the architecture extension 'ext' via the ! '.arch_extension' pseudo-op. ! 'aarch64_tiny' AArch64 target which generates instruction sequences for tiny memory model. ! 'aarch64_small' AArch64 target which generates instruction sequences for small memory model. ! 'aarch64_large' AArch64 target which generates instruction sequences for large memory model. ! 'aarch64_little_endian' AArch64 target which generates instruction sequences for little endian. ! 'aarch64_big_endian' AArch64 target which generates instruction sequences for big endian. ! 'aarch64_small_fpic' Binutils installed on test system supports relocation types required by -fpic for AArch64 small memory model. 7.2.3.8 MIPS-specific attributes ................................ ! 'mips64' MIPS target supports 64-bit instructions. ! 'nomips16' MIPS target does not produce MIPS16 code. ! 'mips16_attribute' MIPS target can generate MIPS16 code. ! 'mips_loongson' MIPS target is a Loongson-2E or -2F target using an ABI that supports the Loongson vector modes. ! 'mips_newabi_large_long_double' ! MIPS target supports 'long double' larger than 'double' when using the new ABI. ! 'mpaired_single' ! MIPS target supports '-mpaired-single'. 7.2.3.9 PowerPC-specific attributes ................................... ! 'dfp_hw' PowerPC target supports executing hardware DFP instructions. ! 'p8vector_hw' PowerPC target supports executing VSX instructions (ISA 2.07). ! 'powerpc64' Test system supports executing 64-bit instructions. ! 'powerpc_altivec' PowerPC target supports AltiVec. ! 'powerpc_altivec_ok' ! PowerPC target supports '-maltivec'. ! 'powerpc_eabi_ok' ! PowerPC target supports '-meabi'. ! 'powerpc_elfv2' ! PowerPC target supports '-mabi=elfv2'. ! 'powerpc_fprs' PowerPC target supports floating-point registers. ! 'powerpc_hard_double' PowerPC target supports hardware double-precision floating-point. ! 'powerpc_htm_ok' ! PowerPC target supports '-mhtm' ! 'powerpc_p8vector_ok' ! PowerPC target supports '-mpower8-vector' ! 'powerpc_ppu_ok' ! PowerPC target supports '-mcpu=cell'. ! 'powerpc_spe' PowerPC target supports PowerPC SPE. ! 'powerpc_spe_nocache' Including the options used to compile this particular test, the PowerPC target supports PowerPC SPE. ! 'powerpc_spu' PowerPC target supports PowerPC SPU. ! 'powerpc_vsx_ok' ! PowerPC target supports '-mvsx'. ! 'powerpc_405_nocache' Including the options used to compile this particular test, the PowerPC target supports PowerPC 405. ! 'ppc_recip_hw' PowerPC target supports executing reciprocal estimate instructions. ! 'spu_auto_overlay' SPU target has toolchain that supports automatic overlay generation. ! 'vmx_hw' PowerPC target supports executing AltiVec instructions. ! 'vsx_hw' PowerPC target supports executing VSX instructions (ISA 2.06). 7.2.3.10 Other hardware attributes .................................. ! 'avx' ! Target supports compiling 'avx' instructions. ! 'avx_runtime' ! Target supports the execution of 'avx' instructions. ! 'cell_hw' Test system can execute AltiVec and Cell PPU instructions. ! 'coldfire_fpu' Target uses a ColdFire FPU. ! 'hard_float' Target supports FPU instructions. ! 'non_strict_align' Target does not require strict alignment. ! 'sqrt_insn' Target has a square root instruction that the compiler can generate. ! 'sse' ! Target supports compiling 'sse' instructions. ! 'sse_runtime' ! Target supports the execution of 'sse' instructions. ! 'sse2' ! Target supports compiling 'sse2' instructions. ! 'sse2_runtime' ! Target supports the execution of 'sse2' instructions. ! 'sync_char_short' ! Target supports atomic operations on 'char' and 'short'. ! 'sync_int_long' ! Target supports atomic operations on 'int' and 'long'. ! 'ultrasparc_hw' Test environment appears to run executables on a simulator that ! accepts only 'EM_SPARC' executables and chokes on 'EM_SPARC32PLUS' ! or 'EM_SPARCV9' executables. ! 'vect_cmdline_needed' Target requires a command line argument to enable a SIMD instruction set. ! 'pie_copyreloc' The x86-64 target linker supports PIE with copy reloc. 7.2.3.11 Environment attributes ............................... ! 'c' The language for the compiler under test is C. ! 'c++' The language for the compiler under test is C++. ! 'c99_runtime' Target provides a full C99 runtime. ! 'correct_iso_cpp_string_wchar_protos' ! Target 'string.h' and 'wchar.h' headers provide C++ required ! overloads for 'strchr' etc. functions. ! 'dummy_wcsftime' ! Target uses a dummy 'wcsftime' function that always returns zero. ! 'fd_truncate' Target can truncate a file from a file descriptor, as used by ! 'libgfortran/io/unix.c:fd_truncate'; i.e. 'ftruncate' or 'chsize'. ! 'freestanding' ! Target is 'freestanding' as defined in section 4 of the C99 standard. Effectively, it is a target which supports no extra headers or libraries other than what is considered essential. ! 'init_priority' Target supports constructors with initialization priority arguments. ! 'inttypes_types' ! Target has the basic signed and unsigned types in 'inttypes.h'. This is for tests that GCC's notions of these types agree with ! those in the header, as some systems have only 'inttypes.h'. ! 'lax_strtofp' Target might have errors of a few ULP in string to floating-point conversion functions and overflow is not always detected correctly by those functions. ! 'mempcpy' ! Target provides 'mempcpy' function. ! 'mmap' ! Target supports 'mmap'. ! 'newlib' Target supports Newlib. ! 'pow10' ! Target provides 'pow10' function. ! 'pthread' ! Target can compile using 'pthread.h' with no errors or warnings. ! 'pthread_h' ! Target has 'pthread.h'. ! 'run_expensive_tests' Expensive testcases (usually those that consume excessive amounts of CPU time) should be run on this target. This can be enabled by ! setting the 'GCC_TEST_RUN_EXPENSIVE' environment variable to a non-empty string. ! 'simulator' ! Test system runs executables on a simulator (i.e. slowly) rather ! than hardware (i.e. fast). ! 'stabs' Target supports the stabs debugging format. ! 'stdint_types' ! Target has the basic signed and unsigned C types in 'stdint.h'. ! This will be obsolete when GCC ensures a working 'stdint.h' for all ! targets. ! 'stpcpy' ! Target provides 'stpcpy' function. ! 'trampolines' Target supports trampolines. ! 'uclibc' Target supports uClibc. ! 'unwrapped' Target does not use a status wrapper. ! 'vxworks_kernel' Target is a VxWorks kernel. ! 'vxworks_rtp' Target is a VxWorks RTP. ! 'wchar' Target supports wide characters. 7.2.3.12 Other attributes ......................... ! 'automatic_stack_alignment' Target supports automatic stack alignment. ! 'cxa_atexit' ! Target uses '__cxa_atexit'. ! 'default_packed' Target has packed layout of structure members by default. ! 'fgraphite' Target supports Graphite optimizations. ! 'fixed_point' Target supports fixed-point extension to C. ! 'fopenacc' ! Target supports OpenACC via '-fopenacc'. ! 'fopenmp' ! Target supports OpenMP via '-fopenmp'. ! 'fpic' ! Target supports '-fpic' and '-fPIC'. ! 'freorder' ! Target supports '-freorder-blocks-and-partition'. ! 'fstack_protector' ! Target supports '-fstack-protector'. ! 'gas' ! Target uses GNU 'as'. ! 'gc_sections' ! Target supports '--gc-sections'. ! 'gld' ! Target uses GNU 'ld'. ! 'keeps_null_pointer_checks' Target keeps null pointer checks, either due to the use of ! '-fno-delete-null-pointer-checks' or hardwired into the target. ! 'lto' Compiler has been configured to support link-time optimization (LTO). ! 'naked_functions' ! Target supports the 'naked' function attribute. ! 'named_sections' Target supports named sections. ! 'natural_alignment_32' Target uses natural alignment (aligned to type size) for types of 32 bits or less. ! 'target_natural_alignment_64' Target uses natural alignment (aligned to type size) for types of 64 bits or less. ! 'nonpic' Target does not generate PIC by default. ! 'pie_enabled' Target generates PIE by default. ! 'pcc_bitfield_type_matters' ! Target defines 'PCC_BITFIELD_TYPE_MATTERS'. ! 'pe_aligned_commons' ! Target supports '-mpe-aligned-commons'. ! 'pie' ! Target supports '-pie', '-fpie' and '-fPIE'. ! 'section_anchors' Target supports section anchors. ! 'short_enums' Target defaults to short enums. ! 'static' ! Target supports '-static'. ! 'static_libgfortran' ! Target supports statically linking 'libgfortran'. ! 'string_merging' Target supports merging string constants at link time. ! 'ucn' Target supports compiling and assembling UCN. ! 'ucn_nocache' Including the options used to compile this particular test, the target supports compiling and assembling UCN. ! 'unaligned_stack' ! Target does not guarantee that its 'STACK_BOUNDARY' is greater than or equal to the required vector alignment. ! 'vector_alignment_reachable' Vector alignment is reachable for types of 32 bits or less. ! 'vector_alignment_reachable_for_64bit' Vector alignment is reachable for types of 64 bits or less. ! 'wchar_t_char16_t_compatible' ! Target supports 'wchar_t' that is compatible with 'char16_t'. ! 'wchar_t_char32_t_compatible' ! Target supports 'wchar_t' that is compatible with 'char32_t'. ! 'comdat_group' Target uses comdat groups. ! 7.2.3.13 Local to tests in 'gcc.target/i386' ............................................ ! '3dnow' ! Target supports compiling '3dnow' instructions. ! 'aes' ! Target supports compiling 'aes' instructions. ! 'fma4' ! Target supports compiling 'fma4' instructions. ! 'ms_hook_prologue' ! Target supports attribute 'ms_hook_prologue'. ! 'pclmul' ! Target supports compiling 'pclmul' instructions. ! 'sse3' ! Target supports compiling 'sse3' instructions. ! 'sse4' ! Target supports compiling 'sse4' instructions. ! 'sse4a' ! Target supports compiling 'sse4a' instructions. ! 'ssse3' ! Target supports compiling 'ssse3' instructions. ! 'vaes' ! Target supports compiling 'vaes' instructions. ! 'vpclmul' ! Target supports compiling 'vpclmul' instructions. ! 'xop' ! Target supports compiling 'xop' instructions. ! 7.2.3.14 Local to tests in 'gcc.target/spu/ea' .............................................. ! 'ealib' ! Target '__ea' library functions are available. ! 7.2.3.15 Local to tests in 'gcc.test-framework' ............................................... ! 'no' Always returns 0. ! 'yes' Always returns 1.  File: gccint.info, Node: Add Options, Next: Require Support, Prev: Effective-Target Keywords, Up: Test Directives ! 7.2.4 Features for 'dg-add-options' ----------------------------------- ! The supported values of FEATURE for directive 'dg-add-options' are: ! 'arm_fp' ! '__ARM_FP' definition. Only ARM targets support this feature, and only then in certain modes; see the *note arm_fp_ok effective target keyword: arm_fp_ok. ! 'arm_neon' NEON support. Only ARM targets support this feature, and only then in certain modes; see the *note arm_neon_ok effective target keyword: arm_neon_ok. ! 'arm_neon_fp16' NEON and half-precision floating point support. Only ARM targets ! support this feature, and only then in certain modes; see the *note ! arm_neon_fp16_ok effective target keyword: arm_neon_fp16_ok. ! 'arm_vfp3' arm vfp3 floating point support; see the *note arm_vfp3_ok effective target keyword: arm_vfp3_ok. ! 'bind_pic_locally' Add the target-specific flags needed to enable functions to bind locally when using pic/PIC passes in the testsuite. ! 'c99_runtime' Add the target-specific flags needed to access the C99 runtime. ! 'ieee' ! Add the target-specific flags needed to enable full IEEE compliance ! mode. ! 'mips16_attribute' ! 'mips16' function attributes. Only MIPS targets support this feature, and only then in certain modes. ! 'tls' Add the target-specific flags needed to use thread-local storage.  File: gccint.info, Node: Require Support, Next: Final Actions, Prev: Add Options, Up: Test Directives ! 7.2.5 Variants of 'dg-require-SUPPORT' -------------------------------------- ! A few of the 'dg-require' directives take arguments. ! 'dg-require-iconv CODESET' ! Skip the test if the target does not support iconv. CODESET is the ! codeset to convert to. ! 'dg-require-profiling PROFOPT' Skip the test if the target does not support profiling with option PROFOPT. ! 'dg-require-visibility VIS' ! Skip the test if the target does not support the 'visibility' ! attribute. If VIS is '""', support for 'visibility("hidden")' is ! checked, for 'visibility("VIS")' otherwise. ! The original 'dg-require' directives were defined before there was support for effective-target keywords. The directives that do not take arguments could be replaced with effective-target keywords. ! 'dg-require-alias ""' ! Skip the test if the target does not support the 'alias' attribute. ! 'dg-require-ascii-locale ""' Skip the test if the host does not support an ASCII locale. ! 'dg-require-compat-dfp ""' ! Skip this test unless both compilers in a 'compat' testsuite support decimal floating point. ! 'dg-require-cxa-atexit ""' ! Skip the test if the target does not support '__cxa_atexit'. This ! is equivalent to 'dg-require-effective-target cxa_atexit'. ! 'dg-require-dll ""' Skip the test if the target does not support DLL attributes. ! 'dg-require-fork ""' ! Skip the test if the target does not support 'fork'. ! 'dg-require-gc-sections ""' Skip the test if the target's linker does not support the ! '--gc-sections' flags. This is equivalent to ! 'dg-require-effective-target gc-sections'. ! 'dg-require-host-local ""' Skip the test if the host is remote, rather than the same as the build system. Some tests are incompatible with DejaGnu's handling ! of remote hosts, which involves copying the source file to the host ! and compiling it with a relative path and "'-o a.out'". ! 'dg-require-mkfifo ""' ! Skip the test if the target does not support 'mkfifo'. ! 'dg-require-named-sections ""' Skip the test is the target does not support named sections. This ! is equivalent to 'dg-require-effective-target named_sections'. ! 'dg-require-weak ""' Skip the test if the target does not support weak symbols. ! 'dg-require-weak-override ""' Skip the test if the target does not support overriding weak symbols.  File: gccint.info, Node: Final Actions, Prev: Require Support, Up: Test Directives ! 7.2.6 Commands for use in 'dg-final' ------------------------------------ The GCC testsuite defines the following directives to be used within ! 'dg-final'. 7.2.6.1 Scan a particular file .............................. ! 'scan-file FILENAME REGEXP [{ target/xfail SELECTOR }]' Passes if REGEXP matches text in FILENAME. ! 'scan-file-not FILENAME REGEXP [{ target/xfail SELECTOR }]' Passes if REGEXP does not match text in FILENAME. ! 'scan-module MODULE REGEXP [{ target/xfail SELECTOR }]' Passes if REGEXP matches in Fortran module MODULE. 7.2.6.2 Scan the assembly output ................................ ! 'scan-assembler REGEX [{ target/xfail SELECTOR }]' Passes if REGEX matches text in the test's assembler output. ! 'scan-assembler-not REGEX [{ target/xfail SELECTOR }]' Passes if REGEX does not match text in the test's assembler output. ! 'scan-assembler-times REGEX NUM [{ target/xfail SELECTOR }]' Passes if REGEX is matched exactly NUM times in the test's assembler output. ! 'scan-assembler-dem REGEX [{ target/xfail SELECTOR }]' Passes if REGEX matches text in the test's demangled assembler output. ! 'scan-assembler-dem-not REGEX [{ target/xfail SELECTOR }]' Passes if REGEX does not match text in the test's demangled assembler output. ! 'scan-hidden SYMBOL [{ target/xfail SELECTOR }]' Passes if SYMBOL is defined as a hidden symbol in the test's assembly output. ! 'scan-not-hidden SYMBOL [{ target/xfail SELECTOR }]' Passes if SYMBOL is not defined as a hidden symbol in the test's assembly output. 7.2.6.3 Scan optimization dump files .................................... ! These commands are available for KIND of 'tree', 'rtl', and 'ipa'. ! 'scan-KIND-dump REGEX SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX matches text in the dump file with suffix SUFFIX. ! 'scan-KIND-dump-not REGEX SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX does not match text in the dump file with suffix SUFFIX. ! 'scan-KIND-dump-times REGEX NUM SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX is found exactly NUM times in the dump file with suffix SUFFIX. ! 'scan-KIND-dump-dem REGEX SUFFIX [{ target/xfail SELECTOR }]' ! Passes if REGEX matches demangled text in the dump file with suffix ! SUFFIX. ! 'scan-KIND-dump-dem-not REGEX SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX does not match demangled text in the dump file with suffix SUFFIX. 7.2.6.4 Verify that an output files exists or not ................................................. ! 'output-exists [{ target/xfail SELECTOR }]' Passes if compiler output file exists. ! 'output-exists-not [{ target/xfail SELECTOR }]' Passes if compiler output file does not exist. 7.2.6.5 Check for LTO tests ........................... ! 'scan-symbol REGEXP [{ target/xfail SELECTOR }]' Passes if the pattern is present in the final executable. ! 7.2.6.6 Checks for 'gcov' tests ............................... ! 'run-gcov SOURCEFILE' ! Check line counts in 'gcov' tests. ! 'run-gcov [branches] [calls] { OPTS SOURCEFILE }' Check branch and/or call counts, in addition to line counts, in ! 'gcov' tests. 7.2.6.7 Clean up generated test files ..................................... Usually the test-framework removes files that were generated during ! testing. If a testcase, for example, uses any dumping mechanism to inspect a passes dump file, the testsuite recognized the dump option passed to the tool and schedules a final cleanup to remove these files. There are, however, following additional cleanup directives that can be used to annotate a testcase "manually". ! 'cleanup-coverage-files' Removes coverage data files generated for this test. ! 'cleanup-modules "LIST-OF-EXTRA-MODULES"' Removes Fortran module files generated for this test, excluding the module names listed in keep-modules. Cleaning up module files is usually done automatically by the testsuite by looking at the --- 4613,5632 ---- for particular targets, or to specify that particular sets of targets are expected to fail some tests. ! Effective-target keywords are defined in `lib/target-supports.exp' in the GCC testsuite, with the exception of those that are documented as being local to a particular test directory. ! The `effective target' takes into account all of the compiler options with which the test will be compiled, including the multilib options. ! By convention, keywords ending in `_nocache' can also include options ! specified for the particular test in an earlier `dg-options' or ! `dg-add-options' directive. 7.2.3.1 Data type sizes ....................... ! `ilp32' ! Target has 32-bit `int', `long', and pointers. ! `lp64' ! Target has 32-bit `int', 64-bit `long' and pointers. ! `llp64' ! Target has 32-bit `int' and `long', 64-bit `long long' and pointers. ! `double64' ! Target has 64-bit `double'. ! `double64plus' ! Target has `double' that is 64 bits or longer. ! `longdouble128' ! Target has 128-bit `long double'. ! `int32plus' ! Target has `int' that is at 32 bits or longer. ! `int16' ! Target has `int' that is 16 bits or shorter. ! `long_neq_int' ! Target has `int' and `long' with different sizes. ! `large_double' ! Target supports `double' that is longer than `float'. ! `large_long_double' ! Target supports `long double' that is longer than `double'. ! `ptr32plus' Target has pointers that are 32 bits or longer. ! `size32plus' Target supports array and structure sizes that are 32 bits or longer. ! `4byte_wchar_t' ! Target has `wchar_t' that is at least 4 bytes. 7.2.3.2 Fortran-specific attributes ................................... ! `fortran_integer_16' ! Target supports Fortran `integer' that is 16 bytes or longer. ! `fortran_large_int' ! Target supports Fortran `integer' kinds larger than `integer(8)'. ! `fortran_large_real' ! Target supports Fortran `real' kinds larger than `real(8)'. 7.2.3.3 Vector-specific attributes .................................. ! `vect_condition' Target supports vector conditional operations. ! `vect_double' ! Target supports hardware vectors of `double'. ! `vect_float' ! Target supports hardware vectors of `float'. ! `vect_int' ! Target supports hardware vectors of `int'. ! `vect_long' ! Target supports hardware vectors of `long'. ! `vect_long_long' ! Target supports hardware vectors of `long long'. ! `vect_aligned_arrays' Target aligns arrays to vector alignment boundary. ! `vect_hw_misalign' Target supports a vector misalign access. ! `vect_no_align' Target does not support a vector alignment mechanism. ! `vect_no_int_min_max' ! Target does not support a vector min and max instruction on `int'. ! `vect_no_int_add' ! Target does not support a vector add instruction on `int'. ! `vect_no_bitwise' Target does not support vector bitwise instructions. ! `vect_char_mult' ! Target supports `vector char' multiplication. ! `vect_short_mult' ! Target supports `vector short' multiplication. ! `vect_int_mult' ! Target supports `vector int' multiplication. ! `vect_extract_even_odd' Target supports vector even/odd element extraction. ! `vect_extract_even_odd_wide' Target supports vector even/odd element extraction of vectors with ! elements `SImode' or larger. ! `vect_interleave' Target supports vector interleaving. ! `vect_strided' Target supports vector interleaving and extract even/odd. ! `vect_strided_wide' Target supports vector interleaving and extract even/odd for wide element types. ! `vect_perm' Target supports vector permutation. ! `vect_shift' Target supports a hardware vector shift operation. ! `vect_widen_sum_hi_to_si' ! Target supports a vector widening summation of `short' operands ! into `int' results, or can promote (unpack) from `short' to `int'. ! `vect_widen_sum_qi_to_hi' ! Target supports a vector widening summation of `char' operands ! into `short' results, or can promote (unpack) from `char' to ! `short'. ! `vect_widen_sum_qi_to_si' ! Target supports a vector widening summation of `char' operands ! into `int' results. ! `vect_widen_mult_qi_to_hi' ! Target supports a vector widening multiplication of `char' operands ! into `short' results, or can promote (unpack) from `char' to ! `short' and perform non-widening multiplication of `short'. ! `vect_widen_mult_hi_to_si' ! Target supports a vector widening multiplication of `short' ! operands into `int' results, or can promote (unpack) from `short' ! to `int' and perform non-widening multiplication of `int'. ! `vect_widen_mult_si_to_di_pattern' ! Target supports a vector widening multiplication of `int' operands ! into `long' results. ! `vect_sdot_qi' ! Target supports a vector dot-product of `signed char'. ! `vect_udot_qi' ! Target supports a vector dot-product of `unsigned char'. ! `vect_sdot_hi' ! Target supports a vector dot-product of `signed short'. ! `vect_udot_hi' ! Target supports a vector dot-product of `unsigned short'. ! `vect_pack_trunc' ! Target supports a vector demotion (packing) of `short' to `char' ! and from `int' to `short' using modulo arithmetic. ! `vect_unpack' ! Target supports a vector promotion (unpacking) of `char' to `short' ! and from `char' to `int'. ! `vect_intfloat_cvt' ! Target supports conversion from `signed int' to `float'. ! `vect_uintfloat_cvt' ! Target supports conversion from `unsigned int' to `float'. ! `vect_floatint_cvt' ! Target supports conversion from `float' to `signed int'. ! `vect_floatuint_cvt' ! Target supports conversion from `float' to `unsigned int'. ! `vect_max_reduc' Target supports max reduction for vectors. 7.2.3.4 Thread Local Storage attributes ....................................... ! `tls' Target supports thread-local storage. ! `tls_native' Target supports native (rather than emulated) thread-local storage. ! `tls_runtime' Test system supports executing TLS executables. 7.2.3.5 Decimal floating point attributes ......................................... ! `dfp' Targets supports compiling decimal floating point extension to C. ! `dfp_nocache' Including the options used to compile this particular test, the target supports compiling decimal floating point extension to C. ! `dfprt' Test system can execute decimal floating point tests. ! `dfprt_nocache' Including the options used to compile this particular test, the test system can execute decimal floating point tests. ! `hard_dfp' Target generates decimal floating point instructions with current options. 7.2.3.6 ARM-specific attributes ............................... ! `arm32' ARM target generates 32-bit code. ! `arm_eabi' ARM target adheres to the ABI for the ARM Architecture. ! `arm_fp_ok' ! ARM target defines `__ARM_FP' using `-mfloat-abi=softfp' or equivalent options. Some multilibs may be incompatible with these options. ! `arm_hf_eabi' ARM target adheres to the VFP and Advanced SIMD Register Arguments variant of the ABI for the ARM Architecture (as selected with ! `-mfloat-abi=hard'). ! `arm_hard_vfp_ok' ! ARM target supports `-mfpu=vfp -mfloat-abi=hard'. Some multilibs may be incompatible with these options. ! `arm_iwmmxt_ok' ! ARM target supports `-mcpu=iwmmxt'. Some multilibs may be incompatible with this option. ! `arm_neon' ARM target supports generating NEON instructions. ! `arm_tune_string_ops_prefer_neon' Test CPU tune supports inlining string operations with NEON instructions. ! `arm_neon_hw' Test system supports executing NEON instructions. ! `arm_neonv2_hw' Test system supports executing NEON v2 instructions. ! `arm_neon_ok' ! ARM Target supports `-mfpu=neon -mfloat-abi=softfp' or compatible options. Some multilibs may be incompatible with these options. ! `arm_neonv2_ok' ! ARM Target supports `-mfpu=neon-vfpv4 -mfloat-abi=softfp' or compatible options. Some multilibs may be incompatible with these options. ! `arm_neon_fp16_ok' ! ARM Target supports `-mfpu=neon-fp16 -mfloat-abi=softfp' or ! compatible options, including `-mfp16-format=ieee' if necessary to ! obtain the `__fp16' type. Some multilibs may be incompatible with these options. ! `arm_neon_fp16_hw' Test system supports executing Neon half-precision float instructions. (Implies previous.) ! `arm_thumb1_ok' ! ARM target generates Thumb-1 code for `-mthumb'. ! `arm_thumb2_ok' ! ARM target generates Thumb-2 code for `-mthumb'. ! `arm_vfp_ok' ! ARM target supports `-mfpu=vfp -mfloat-abi=softfp'. Some multilibs may be incompatible with these options. ! `arm_vfp3_ok' ! ARM target supports `-mfpu=vfp3 -mfloat-abi=softfp'. Some multilibs may be incompatible with these options. ! `arm_v8_vfp_ok' ! ARM target supports `-mfpu=fp-armv8 -mfloat-abi=softfp'. Some multilibs may be incompatible with these options. ! `arm_v8_neon_ok' ! ARM target supports `-mfpu=neon-fp-armv8 -mfloat-abi=softfp'. ! Some multilibs may be incompatible with these options. ! ! `arm_v8_1a_neon_ok' ARM target supports options to generate ARMv8.1 Adv.SIMD instructions. Some multilibs may be incompatible with these options. ! `arm_v8_1a_neon_hw' ARM target supports executing ARMv8.1 Adv.SIMD instructions. Some multilibs may be incompatible with the options needed. Implies arm_v8_1a_neon_ok. ! `arm_prefer_ldrd_strd' ! ARM target prefers `LDRD' and `STRD' instructions over `LDM' and ! `STM' instructions. ! 7.2.3.7 AArch64-specific attributes ................................... ! `aarch64_asm__ok' ! AArch64 assembler supports the architecture extension `ext' via the ! `.arch_extension' pseudo-op. ! ! `aarch64_tiny' AArch64 target which generates instruction sequences for tiny memory model. ! ! `aarch64_small' AArch64 target which generates instruction sequences for small memory model. ! ! `aarch64_large' AArch64 target which generates instruction sequences for large memory model. ! ! `aarch64_little_endian' AArch64 target which generates instruction sequences for little endian. ! ! `aarch64_big_endian' AArch64 target which generates instruction sequences for big endian. ! ! `aarch64_small_fpic' Binutils installed on test system supports relocation types required by -fpic for AArch64 small memory model. + 7.2.3.8 MIPS-specific attributes ................................ ! `mips64' MIPS target supports 64-bit instructions. ! `nomips16' MIPS target does not produce MIPS16 code. ! `mips16_attribute' MIPS target can generate MIPS16 code. ! `mips_loongson' MIPS target is a Loongson-2E or -2F target using an ABI that supports the Loongson vector modes. ! `mips_newabi_large_long_double' ! MIPS target supports `long double' larger than `double' when using the new ABI. ! `mpaired_single' ! MIPS target supports `-mpaired-single'. 7.2.3.9 PowerPC-specific attributes ................................... ! `dfp_hw' PowerPC target supports executing hardware DFP instructions. ! `p8vector_hw' PowerPC target supports executing VSX instructions (ISA 2.07). ! `powerpc64' Test system supports executing 64-bit instructions. ! `powerpc_altivec' PowerPC target supports AltiVec. ! `powerpc_altivec_ok' ! PowerPC target supports `-maltivec'. ! `powerpc_eabi_ok' ! PowerPC target supports `-meabi'. ! `powerpc_elfv2' ! PowerPC target supports `-mabi=elfv2'. ! `powerpc_fprs' PowerPC target supports floating-point registers. ! `powerpc_hard_double' PowerPC target supports hardware double-precision floating-point. ! `powerpc_htm_ok' ! PowerPC target supports `-mhtm' ! `powerpc_p8vector_ok' ! PowerPC target supports `-mpower8-vector' ! `powerpc_ppu_ok' ! PowerPC target supports `-mcpu=cell'. ! `powerpc_spe' PowerPC target supports PowerPC SPE. ! `powerpc_spe_nocache' Including the options used to compile this particular test, the PowerPC target supports PowerPC SPE. ! `powerpc_spu' PowerPC target supports PowerPC SPU. ! `powerpc_vsx_ok' ! PowerPC target supports `-mvsx'. ! `powerpc_405_nocache' Including the options used to compile this particular test, the PowerPC target supports PowerPC 405. ! `ppc_recip_hw' PowerPC target supports executing reciprocal estimate instructions. ! `spu_auto_overlay' SPU target has toolchain that supports automatic overlay generation. ! `vmx_hw' PowerPC target supports executing AltiVec instructions. ! `vsx_hw' PowerPC target supports executing VSX instructions (ISA 2.06). 7.2.3.10 Other hardware attributes .................................. ! `avx' ! Target supports compiling `avx' instructions. ! `avx_runtime' ! Target supports the execution of `avx' instructions. ! `cell_hw' Test system can execute AltiVec and Cell PPU instructions. ! `coldfire_fpu' Target uses a ColdFire FPU. ! `hard_float' Target supports FPU instructions. ! `non_strict_align' Target does not require strict alignment. ! `sqrt_insn' Target has a square root instruction that the compiler can generate. ! `sse' ! Target supports compiling `sse' instructions. ! `sse_runtime' ! Target supports the execution of `sse' instructions. ! `sse2' ! Target supports compiling `sse2' instructions. ! `sse2_runtime' ! Target supports the execution of `sse2' instructions. ! `sync_char_short' ! Target supports atomic operations on `char' and `short'. ! `sync_int_long' ! Target supports atomic operations on `int' and `long'. ! `ultrasparc_hw' Test environment appears to run executables on a simulator that ! accepts only `EM_SPARC' executables and chokes on `EM_SPARC32PLUS' ! or `EM_SPARCV9' executables. ! `vect_cmdline_needed' Target requires a command line argument to enable a SIMD instruction set. ! `pie_copyreloc' The x86-64 target linker supports PIE with copy reloc. 7.2.3.11 Environment attributes ............................... ! `c' The language for the compiler under test is C. ! `c++' The language for the compiler under test is C++. ! `c99_runtime' Target provides a full C99 runtime. ! `correct_iso_cpp_string_wchar_protos' ! Target `string.h' and `wchar.h' headers provide C++ required ! overloads for `strchr' etc. functions. ! `dummy_wcsftime' ! Target uses a dummy `wcsftime' function that always returns zero. ! `fd_truncate' Target can truncate a file from a file descriptor, as used by ! `libgfortran/io/unix.c:fd_truncate'; i.e. `ftruncate' or `chsize'. ! `freestanding' ! Target is `freestanding' as defined in section 4 of the C99 standard. Effectively, it is a target which supports no extra headers or libraries other than what is considered essential. ! `init_priority' Target supports constructors with initialization priority arguments. ! `inttypes_types' ! Target has the basic signed and unsigned types in `inttypes.h'. This is for tests that GCC's notions of these types agree with ! those in the header, as some systems have only `inttypes.h'. ! `lax_strtofp' Target might have errors of a few ULP in string to floating-point conversion functions and overflow is not always detected correctly by those functions. ! `mempcpy' ! Target provides `mempcpy' function. ! `mmap' ! Target supports `mmap'. ! `newlib' Target supports Newlib. ! `pow10' ! Target provides `pow10' function. ! `pthread' ! Target can compile using `pthread.h' with no errors or warnings. ! `pthread_h' ! Target has `pthread.h'. ! `run_expensive_tests' Expensive testcases (usually those that consume excessive amounts of CPU time) should be run on this target. This can be enabled by ! setting the `GCC_TEST_RUN_EXPENSIVE' environment variable to a non-empty string. ! `simulator' ! Test system runs executables on a simulator (i.e. slowly) rather ! than hardware (i.e. fast). ! `stabs' Target supports the stabs debugging format. ! `stdint_types' ! Target has the basic signed and unsigned C types in `stdint.h'. ! This will be obsolete when GCC ensures a working `stdint.h' for ! all targets. ! `stpcpy' ! Target provides `stpcpy' function. ! `trampolines' Target supports trampolines. ! `uclibc' Target supports uClibc. ! `unwrapped' Target does not use a status wrapper. ! `vxworks_kernel' Target is a VxWorks kernel. ! `vxworks_rtp' Target is a VxWorks RTP. ! `wchar' Target supports wide characters. 7.2.3.12 Other attributes ......................... ! `automatic_stack_alignment' Target supports automatic stack alignment. ! `cxa_atexit' ! Target uses `__cxa_atexit'. ! `default_packed' Target has packed layout of structure members by default. ! `fgraphite' Target supports Graphite optimizations. ! `fixed_point' Target supports fixed-point extension to C. ! `fopenacc' ! Target supports OpenACC via `-fopenacc'. ! `fopenmp' ! Target supports OpenMP via `-fopenmp'. ! `fpic' ! Target supports `-fpic' and `-fPIC'. ! `freorder' ! Target supports `-freorder-blocks-and-partition'. ! `fstack_protector' ! Target supports `-fstack-protector'. ! `gas' ! Target uses GNU `as'. ! `gc_sections' ! Target supports `--gc-sections'. ! `gld' ! Target uses GNU `ld'. ! `keeps_null_pointer_checks' Target keeps null pointer checks, either due to the use of ! `-fno-delete-null-pointer-checks' or hardwired into the target. ! `lto' Compiler has been configured to support link-time optimization (LTO). ! `naked_functions' ! Target supports the `naked' function attribute. ! `named_sections' Target supports named sections. ! `natural_alignment_32' Target uses natural alignment (aligned to type size) for types of 32 bits or less. ! `target_natural_alignment_64' Target uses natural alignment (aligned to type size) for types of 64 bits or less. ! `nonpic' Target does not generate PIC by default. ! `pie_enabled' Target generates PIE by default. ! `pcc_bitfield_type_matters' ! Target defines `PCC_BITFIELD_TYPE_MATTERS'. ! `pe_aligned_commons' ! Target supports `-mpe-aligned-commons'. ! `pie' ! Target supports `-pie', `-fpie' and `-fPIE'. ! `rdynamic' ! Target supports `-rdynamic'. ! ! `section_anchors' Target supports section anchors. ! `short_enums' Target defaults to short enums. ! `static' ! Target supports `-static'. ! `static_libgfortran' ! Target supports statically linking `libgfortran'. ! `string_merging' Target supports merging string constants at link time. ! `ucn' Target supports compiling and assembling UCN. ! `ucn_nocache' Including the options used to compile this particular test, the target supports compiling and assembling UCN. ! `unaligned_stack' ! Target does not guarantee that its `STACK_BOUNDARY' is greater than or equal to the required vector alignment. ! `vector_alignment_reachable' Vector alignment is reachable for types of 32 bits or less. ! `vector_alignment_reachable_for_64bit' Vector alignment is reachable for types of 64 bits or less. ! `wchar_t_char16_t_compatible' ! Target supports `wchar_t' that is compatible with `char16_t'. ! `wchar_t_char32_t_compatible' ! Target supports `wchar_t' that is compatible with `char32_t'. ! `comdat_group' Target uses comdat groups. ! 7.2.3.13 Local to tests in `gcc.target/i386' ............................................ ! `3dnow' ! Target supports compiling `3dnow' instructions. ! `aes' ! Target supports compiling `aes' instructions. ! `fma4' ! Target supports compiling `fma4' instructions. ! `ms_hook_prologue' ! Target supports attribute `ms_hook_prologue'. ! `pclmul' ! Target supports compiling `pclmul' instructions. ! `sse3' ! Target supports compiling `sse3' instructions. ! `sse4' ! Target supports compiling `sse4' instructions. ! `sse4a' ! Target supports compiling `sse4a' instructions. ! `ssse3' ! Target supports compiling `ssse3' instructions. ! `vaes' ! Target supports compiling `vaes' instructions. ! `vpclmul' ! Target supports compiling `vpclmul' instructions. ! `xop' ! Target supports compiling `xop' instructions. ! 7.2.3.14 Local to tests in `gcc.target/spu/ea' .............................................. ! `ealib' ! Target `__ea' library functions are available. ! 7.2.3.15 Local to tests in `gcc.test-framework' ............................................... ! `no' Always returns 0. ! `yes' Always returns 1.  File: gccint.info, Node: Add Options, Next: Require Support, Prev: Effective-Target Keywords, Up: Test Directives ! 7.2.4 Features for `dg-add-options' ----------------------------------- ! The supported values of FEATURE for directive `dg-add-options' are: ! `arm_fp' ! `__ARM_FP' definition. Only ARM targets support this feature, and only then in certain modes; see the *note arm_fp_ok effective target keyword: arm_fp_ok. ! `arm_neon' NEON support. Only ARM targets support this feature, and only then in certain modes; see the *note arm_neon_ok effective target keyword: arm_neon_ok. ! `arm_neon_fp16' NEON and half-precision floating point support. Only ARM targets ! support this feature, and only then in certain modes; see the ! *note arm_neon_fp16_ok effective target keyword: arm_neon_fp16_ok. ! `arm_vfp3' arm vfp3 floating point support; see the *note arm_vfp3_ok effective target keyword: arm_vfp3_ok. ! `bind_pic_locally' Add the target-specific flags needed to enable functions to bind locally when using pic/PIC passes in the testsuite. ! `c99_runtime' Add the target-specific flags needed to access the C99 runtime. ! `ieee' ! Add the target-specific flags needed to enable full IEEE ! compliance mode. ! `mips16_attribute' ! `mips16' function attributes. Only MIPS targets support this feature, and only then in certain modes. ! `tls' Add the target-specific flags needed to use thread-local storage.  File: gccint.info, Node: Require Support, Next: Final Actions, Prev: Add Options, Up: Test Directives ! 7.2.5 Variants of `dg-require-SUPPORT' -------------------------------------- ! A few of the `dg-require' directives take arguments. ! `dg-require-iconv CODESET' ! Skip the test if the target does not support iconv. CODESET is ! the codeset to convert to. ! `dg-require-profiling PROFOPT' Skip the test if the target does not support profiling with option PROFOPT. ! `dg-require-visibility VIS' ! Skip the test if the target does not support the `visibility' ! attribute. If VIS is `""', support for `visibility("hidden")' is ! checked, for `visibility("VIS")' otherwise. ! The original `dg-require' directives were defined before there was support for effective-target keywords. The directives that do not take arguments could be replaced with effective-target keywords. ! `dg-require-alias ""' ! Skip the test if the target does not support the `alias' attribute. ! `dg-require-ascii-locale ""' Skip the test if the host does not support an ASCII locale. ! `dg-require-compat-dfp ""' ! Skip this test unless both compilers in a `compat' testsuite support decimal floating point. ! `dg-require-cxa-atexit ""' ! Skip the test if the target does not support `__cxa_atexit'. This ! is equivalent to `dg-require-effective-target cxa_atexit'. ! `dg-require-dll ""' Skip the test if the target does not support DLL attributes. ! `dg-require-fork ""' ! Skip the test if the target does not support `fork'. ! `dg-require-gc-sections ""' Skip the test if the target's linker does not support the ! `--gc-sections' flags. This is equivalent to ! `dg-require-effective-target gc-sections'. ! `dg-require-host-local ""' Skip the test if the host is remote, rather than the same as the build system. Some tests are incompatible with DejaGnu's handling ! of remote hosts, which involves copying the source file to the ! host and compiling it with a relative path and "`-o a.out'". ! `dg-require-mkfifo ""' ! Skip the test if the target does not support `mkfifo'. ! `dg-require-named-sections ""' Skip the test is the target does not support named sections. This ! is equivalent to `dg-require-effective-target named_sections'. ! `dg-require-weak ""' Skip the test if the target does not support weak symbols. ! `dg-require-weak-override ""' Skip the test if the target does not support overriding weak symbols.  File: gccint.info, Node: Final Actions, Prev: Require Support, Up: Test Directives ! 7.2.6 Commands for use in `dg-final' ------------------------------------ The GCC testsuite defines the following directives to be used within ! `dg-final'. 7.2.6.1 Scan a particular file .............................. ! `scan-file FILENAME REGEXP [{ target/xfail SELECTOR }]' Passes if REGEXP matches text in FILENAME. ! ! `scan-file-not FILENAME REGEXP [{ target/xfail SELECTOR }]' Passes if REGEXP does not match text in FILENAME. ! ! `scan-module MODULE REGEXP [{ target/xfail SELECTOR }]' Passes if REGEXP matches in Fortran module MODULE. 7.2.6.2 Scan the assembly output ................................ ! `scan-assembler REGEX [{ target/xfail SELECTOR }]' Passes if REGEX matches text in the test's assembler output. ! `scan-assembler-not REGEX [{ target/xfail SELECTOR }]' Passes if REGEX does not match text in the test's assembler output. ! `scan-assembler-times REGEX NUM [{ target/xfail SELECTOR }]' Passes if REGEX is matched exactly NUM times in the test's assembler output. ! `scan-assembler-dem REGEX [{ target/xfail SELECTOR }]' Passes if REGEX matches text in the test's demangled assembler output. ! `scan-assembler-dem-not REGEX [{ target/xfail SELECTOR }]' Passes if REGEX does not match text in the test's demangled assembler output. ! `scan-hidden SYMBOL [{ target/xfail SELECTOR }]' Passes if SYMBOL is defined as a hidden symbol in the test's assembly output. ! `scan-not-hidden SYMBOL [{ target/xfail SELECTOR }]' Passes if SYMBOL is not defined as a hidden symbol in the test's assembly output. 7.2.6.3 Scan optimization dump files .................................... ! These commands are available for KIND of `tree', `rtl', and `ipa'. ! `scan-KIND-dump REGEX SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX matches text in the dump file with suffix SUFFIX. ! `scan-KIND-dump-not REGEX SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX does not match text in the dump file with suffix SUFFIX. ! `scan-KIND-dump-times REGEX NUM SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX is found exactly NUM times in the dump file with suffix SUFFIX. ! `scan-KIND-dump-dem REGEX SUFFIX [{ target/xfail SELECTOR }]' ! Passes if REGEX matches demangled text in the dump file with ! suffix SUFFIX. ! `scan-KIND-dump-dem-not REGEX SUFFIX [{ target/xfail SELECTOR }]' Passes if REGEX does not match demangled text in the dump file with suffix SUFFIX. 7.2.6.4 Verify that an output files exists or not ................................................. ! `output-exists [{ target/xfail SELECTOR }]' Passes if compiler output file exists. ! `output-exists-not [{ target/xfail SELECTOR }]' Passes if compiler output file does not exist. 7.2.6.5 Check for LTO tests ........................... ! `scan-symbol REGEXP [{ target/xfail SELECTOR }]' Passes if the pattern is present in the final executable. ! 7.2.6.6 Checks for `gcov' tests ............................... ! `run-gcov SOURCEFILE' ! Check line counts in `gcov' tests. ! `run-gcov [branches] [calls] { OPTS SOURCEFILE }' Check branch and/or call counts, in addition to line counts, in ! `gcov' tests. 7.2.6.7 Clean up generated test files ..................................... Usually the test-framework removes files that were generated during ! testing. If a testcase, for example, uses any dumping mechanism to inspect a passes dump file, the testsuite recognized the dump option passed to the tool and schedules a final cleanup to remove these files. There are, however, following additional cleanup directives that can be used to annotate a testcase "manually". ! `cleanup-coverage-files' Removes coverage data files generated for this test. ! `cleanup-modules "LIST-OF-EXTRA-MODULES"' Removes Fortran module files generated for this test, excluding the module names listed in keep-modules. Cleaning up module files is usually done automatically by the testsuite by looking at the *************** used to annotate a testcase "manually". *** 5527,5533 **** ! { dg-final { cleanup-modules "mod1 mod2" } } ! redundant ! { dg-final { keep-modules "mod3 mod4" } } ! 'keep-modules "LIST-OF-MODULES-NOT-TO-DELETE"' Whitespace separated list of module names that should not be deleted by cleanup-modules. If the list of modules is empty, all modules defined in this file are kept. --- 5643,5649 ---- ! { dg-final { cleanup-modules "mod1 mod2" } } ! redundant ! { dg-final { keep-modules "mod3 mod4" } } ! `keep-modules "LIST-OF-MODULES-NOT-TO-DELETE"' Whitespace separated list of module names that should not be deleted by cleanup-modules. If the list of modules is empty, all modules defined in this file are kept. *************** used to annotate a testcase "manually". *** 5540,5559 **** ! { dg-final { keep-modules "keep1 keep2" } } ! just keep these two ! { dg-final { keep-modules "" } } ! keep all ! 'dg-keep-saved-temps "LIST-OF-SUFFIXES-NOT-TO-DELETE"' Whitespace separated list of suffixes that should not be deleted ! automatically in a testcase that uses '-save-temps'. // { dg-options "-save-temps -fpch-preprocess -I." } int main() { return 0; } // { dg-keep-saved-temps ".s" } ! just keep assembler file // { dg-keep-saved-temps ".s" ".i" } ! ... and .i // { dg-keep-saved-temps ".ii" ".o" } ! or just .ii and .o ! 'cleanup-profile-file' Removes profiling files generated for this test. ! 'cleanup-repo-files' ! Removes files generated for this test for '-frepo'.  File: gccint.info, Node: Ada Tests, Next: C Tests, Prev: Test Directives, Up: Testsuites --- 5656,5676 ---- ! { dg-final { keep-modules "keep1 keep2" } } ! just keep these two ! { dg-final { keep-modules "" } } ! keep all ! `dg-keep-saved-temps "LIST-OF-SUFFIXES-NOT-TO-DELETE"' Whitespace separated list of suffixes that should not be deleted ! automatically in a testcase that uses `-save-temps'. // { dg-options "-save-temps -fpch-preprocess -I." } int main() { return 0; } // { dg-keep-saved-temps ".s" } ! just keep assembler file // { dg-keep-saved-temps ".s" ".i" } ! ... and .i // { dg-keep-saved-temps ".ii" ".o" } ! or just .ii and .o ! `cleanup-profile-file' Removes profiling files generated for this test. ! `cleanup-repo-files' ! Removes files generated for this test for `-frepo'. !  File: gccint.info, Node: Ada Tests, Next: C Tests, Prev: Test Directives, Up: Testsuites *************** File: gccint.info, Node: Ada Tests, Ne *** 5562,5593 **** =========================== The Ada testsuite includes executable tests from the ACATS testsuite, ! publicly available at . ! These tests are integrated in the GCC testsuite in the 'ada/acats' ! directory, and enabled automatically when running 'make check', assuming the Ada language has been enabled when configuring GCC. ! You can also run the Ada testsuite independently, using 'make check-ada', or run a subset of the tests by specifying which chapter to run, e.g.: $ make check-ada CHAPTERS="c3 c9" ! The tests are organized by directory, each directory corresponding to a ! chapter of the Ada Reference Manual. So for example, 'c9' corresponds to chapter 9, which deals with tasking features of the language. ! There is also an extra chapter called 'gcc' containing a template for creating new executable tests, although this is deprecated in favor of ! the 'gnat.dg' testsuite. ! The tests are run using two 'sh' scripts: 'run_acats' and 'run_all.sh'. ! To run the tests using a simulator or a cross target, see the small ! customization section at the top of 'run_all.sh'. These tests are run using the build tree: they can be run without doing ! a 'make install'.  File: gccint.info, Node: C Tests, Next: libgcj Tests, Prev: Ada Tests, Up: Testsuites --- 5679,5710 ---- =========================== The Ada testsuite includes executable tests from the ACATS testsuite, ! publicly available at `http://www.ada-auth.org/acats.html'. ! These tests are integrated in the GCC testsuite in the `ada/acats' ! directory, and enabled automatically when running `make check', assuming the Ada language has been enabled when configuring GCC. ! You can also run the Ada testsuite independently, using `make check-ada', or run a subset of the tests by specifying which chapter to run, e.g.: $ make check-ada CHAPTERS="c3 c9" ! The tests are organized by directory, each directory corresponding to ! a chapter of the Ada Reference Manual. So for example, `c9' corresponds to chapter 9, which deals with tasking features of the language. ! There is also an extra chapter called `gcc' containing a template for creating new executable tests, although this is deprecated in favor of ! the `gnat.dg' testsuite. ! The tests are run using two `sh' scripts: `run_acats' and ! `run_all.sh'. To run the tests using a simulator or a cross target, ! see the small customization section at the top of `run_all.sh'. These tests are run using the build tree: they can be run without doing ! a `make install'.  File: gccint.info, Node: C Tests, Next: libgcj Tests, Prev: Ada Tests, Up: Testsuites *************** File: gccint.info, Node: C Tests, Next *** 5595,5695 **** 7.4 C Language Testsuites ========================= ! GCC contains the following C language testsuites, in the 'gcc/testsuite' ! directory: ! 'gcc.dg' ! This contains tests of particular features of the C compiler, using ! the more modern 'dg' harness. Correctness tests for various compiler features should go here if possible. Magic comments determine whether the file is preprocessed, ! compiled, linked or run. In these tests, error and warning message ! texts are compared against expected texts or regular expressions ! given in comments. These tests are run with the options '-ansi ! -pedantic' unless other options are given in the test. Except as ! noted below they are not run with multiple optimization options. ! 'gcc.dg/compat' This subdirectory contains tests for binary compatibility using ! 'lib/compat.exp', which in turn uses the language-independent support (*note Support for testing binary compatibility: compat Testing.). ! 'gcc.dg/cpp' This subdirectory contains tests of the preprocessor. ! 'gcc.dg/debug' This subdirectory contains tests for debug formats. Tests in this subdirectory are run for each debug format that the compiler supports. ! 'gcc.dg/format' ! This subdirectory contains tests of the '-Wformat' format checking. ! Tests in this directory are run with and without '-DWIDE'. ! 'gcc.dg/noncompile' This subdirectory contains tests of code that should not compile and does not need any special compilation options. They are run with multiple optimization options, since sometimes invalid code crashes the compiler with optimization. ! 'gcc.dg/special' FIXME: describe this. ! 'gcc.c-torture' This contains particular code fragments which have historically broken easily. These tests are run with multiple optimization options, so tests for features which only break at some ! optimization levels belong here. This also contains tests to check ! that certain optimizations occur. It might be worthwhile to ! separate the correctness tests cleanly from the code quality tests, ! but it hasn't been done yet. ! 'gcc.c-torture/compat' FIXME: describe this. This directory should probably not be used for new tests. ! 'gcc.c-torture/compile' This testsuite contains test cases that should compile, but do not need to link or run. These test cases are compiled with several different combinations of optimization options. All warnings are disabled for these test cases, so this directory is not suitable if you wish to test for the presence or absence of compiler warnings. While special options can be set, and tests disabled on specific ! platforms, by the use of '.x' files, mostly these test cases should ! not contain platform dependencies. FIXME: discuss how defines such ! as 'NO_LABEL_VALUES' and 'STACK_SIZE' are used. ! 'gcc.c-torture/execute' This testsuite contains test cases that should compile, link and ! run; otherwise the same comments as for 'gcc.c-torture/compile' apply. ! 'gcc.c-torture/execute/ieee' This contains tests which are specific to IEEE floating point. ! 'gcc.c-torture/unsorted' FIXME: describe this. This directory should probably not be used for new tests. ! 'gcc.misc-tests' This directory contains C tests that require special handling. Some of these tests have individual expect files, and others share special-purpose expect files: ! 'bprob*.c' ! Test '-fbranch-probabilities' using ! 'gcc.misc-tests/bprob.exp', which in turn uses the generic, language-independent framework (*note Support for testing profile-directed optimizations: profopt Testing.). ! 'gcov*.c' ! Test 'gcov' output using 'gcov.exp', which in turn uses the language-independent support (*note Support for testing gcov: gcov Testing.). ! 'i386-pf-*.c' Test i386-specific support for data prefetch using ! 'i386-prefetch.exp'. ! 'gcc.test-framework' ! 'dg-*.c' Test the testsuite itself using ! 'gcc.test-framework/test-framework.exp'. ! FIXME: merge in 'testsuite/README.gcc' and discuss the format of test cases and magic comments more.  --- 5712,5827 ---- 7.4 C Language Testsuites ========================= ! GCC contains the following C language testsuites, in the ! `gcc/testsuite' directory: ! `gcc.dg' ! This contains tests of particular features of the C compiler, ! using the more modern `dg' harness. Correctness tests for various compiler features should go here if possible. Magic comments determine whether the file is preprocessed, ! compiled, linked or run. In these tests, error and warning ! message texts are compared against expected texts or regular ! expressions given in comments. These tests are run with the ! options `-ansi -pedantic' unless other options are given in the ! test. Except as noted below they are not run with multiple ! optimization options. ! ! `gcc.dg/compat' This subdirectory contains tests for binary compatibility using ! `lib/compat.exp', which in turn uses the language-independent support (*note Support for testing binary compatibility: compat Testing.). ! ! `gcc.dg/cpp' This subdirectory contains tests of the preprocessor. ! ! `gcc.dg/debug' This subdirectory contains tests for debug formats. Tests in this subdirectory are run for each debug format that the compiler supports. ! ! `gcc.dg/format' ! This subdirectory contains tests of the `-Wformat' format ! checking. Tests in this directory are run with and without ! `-DWIDE'. ! ! `gcc.dg/noncompile' This subdirectory contains tests of code that should not compile and does not need any special compilation options. They are run with multiple optimization options, since sometimes invalid code crashes the compiler with optimization. ! ! `gcc.dg/special' FIXME: describe this. ! `gcc.c-torture' This contains particular code fragments which have historically broken easily. These tests are run with multiple optimization options, so tests for features which only break at some ! optimization levels belong here. This also contains tests to ! check that certain optimizations occur. It might be worthwhile to ! separate the correctness tests cleanly from the code quality ! tests, but it hasn't been done yet. ! `gcc.c-torture/compat' FIXME: describe this. This directory should probably not be used for new tests. ! ! `gcc.c-torture/compile' This testsuite contains test cases that should compile, but do not need to link or run. These test cases are compiled with several different combinations of optimization options. All warnings are disabled for these test cases, so this directory is not suitable if you wish to test for the presence or absence of compiler warnings. While special options can be set, and tests disabled on specific ! platforms, by the use of `.x' files, mostly these test cases ! should not contain platform dependencies. FIXME: discuss how ! defines such as `NO_LABEL_VALUES' and `STACK_SIZE' are used. ! ! `gcc.c-torture/execute' This testsuite contains test cases that should compile, link and ! run; otherwise the same comments as for `gcc.c-torture/compile' apply. ! ! `gcc.c-torture/execute/ieee' This contains tests which are specific to IEEE floating point. ! ! `gcc.c-torture/unsorted' FIXME: describe this. This directory should probably not be used for new tests. ! ! `gcc.misc-tests' This directory contains C tests that require special handling. Some of these tests have individual expect files, and others share special-purpose expect files: ! ``bprob*.c'' ! Test `-fbranch-probabilities' using ! `gcc.misc-tests/bprob.exp', which in turn uses the generic, language-independent framework (*note Support for testing profile-directed optimizations: profopt Testing.). ! ``gcov*.c'' ! Test `gcov' output using `gcov.exp', which in turn uses the language-independent support (*note Support for testing gcov: gcov Testing.). ! ``i386-pf-*.c'' Test i386-specific support for data prefetch using ! `i386-prefetch.exp'. ! `gcc.test-framework' ! ! ``dg-*.c'' Test the testsuite itself using ! `gcc.test-framework/test-framework.exp'. ! ! FIXME: merge in `testsuite/README.gcc' and discuss the format of test cases and magic comments more.  *************** File: gccint.info, Node: libgcj Tests, *** 5698,5717 **** 7.5 The Java library testsuites. ================================ ! Runtime tests are executed via 'make check' in the ! 'TARGET/libjava/testsuite' directory in the build tree. Additional runtime tests can be checked into this testsuite. Regression testing of the core packages in libgcj is also covered by the Mauve testsuite. The Mauve Project develops tests for the Java Class Libraries. These tests are run as part of libgcj testing by placing the Mauve tree within the libjava testsuite sources at ! 'libjava/testsuite/libjava.mauve/mauve', or by specifying the location ! of that tree when invoking 'make', as in 'make MAUVEDIR=~/mauve check'. ! To detect regressions, a mechanism in 'mauve.exp' compares the failures ! for a test run against the list of expected failures in ! 'libjava/testsuite/libjava.mauve/xfails' from the source hierarchy. Update this file when adding new failing tests to Mauve, or when fixing bugs in libgcj that had caused Mauve test failures. --- 5830,5849 ---- 7.5 The Java library testsuites. ================================ ! Runtime tests are executed via `make check' in the ! `TARGET/libjava/testsuite' directory in the build tree. Additional runtime tests can be checked into this testsuite. Regression testing of the core packages in libgcj is also covered by the Mauve testsuite. The Mauve Project develops tests for the Java Class Libraries. These tests are run as part of libgcj testing by placing the Mauve tree within the libjava testsuite sources at ! `libjava/testsuite/libjava.mauve/mauve', or by specifying the location ! of that tree when invoking `make', as in `make MAUVEDIR=~/mauve check'. ! To detect regressions, a mechanism in `mauve.exp' compares the ! failures for a test run against the list of expected failures in ! `libjava/testsuite/libjava.mauve/xfails' from the source hierarchy. Update this file when adding new failing tests to Mauve, or when fixing bugs in libgcj that had caused Mauve test failures. *************** Tests for link-time optimizations usuall *** 5727,5804 **** that are compiled separately, perhaps with different sets of options. There are several special-purpose test directives used for these tests. ! '{ dg-lto-do DO-WHAT-KEYWORD }' DO-WHAT-KEYWORD specifies how the test is compiled and whether it is executed. It is one of: ! 'assemble' ! Compile with '-c' to produce a relocatable object file. ! 'link' Compile, assemble, and link to produce an executable file. ! 'run' Produce and run an executable file, which is expected to return an exit code of 0. ! The default is 'assemble'. That can be overridden for a set of ! tests by redefining 'dg-do-what-default' within the '.exp' file for ! those tests. ! Unlike 'dg-do', 'dg-lto-do' does not support an optional 'target' ! or 'xfail' list. Use 'dg-skip-if', 'dg-xfail-if', or ! 'dg-xfail-run-if'. ! '{ dg-lto-options { { OPTIONS } [{ OPTIONS }] } [{ target SELECTOR }]}' This directive provides a list of one or more sets of compiler options to override LTO_OPTIONS. Each test will be compiled and run with each of these sets of options. ! '{ dg-extra-ld-options OPTIONS [{ target SELECTOR }]}' This directive adds OPTIONS to the linker options used. ! '{ dg-suppress-ld-options OPTIONS [{ target SELECTOR }]}' This directive removes OPTIONS from the set of linker options used.  File: gccint.info, Node: gcov Testing, Next: profopt Testing, Prev: LTO Testing, Up: Testsuites ! 7.7 Support for testing 'gcov' ============================== ! Language-independent support for testing 'gcov', and for checking that branch profiling produces expected values, is provided by the expect ! file 'lib/gcov.exp'. 'gcov' tests also rely on procedures in ! 'lib/gcc-dg.exp' to compile and run the test program. A typical 'gcov' test contains the following DejaGnu commands within comments: { dg-options "-fprofile-arcs -ftest-coverage" } { dg-do run { target native } } { dg-final { run-gcov sourcefile } } ! Checks of 'gcov' output can include line counts, branch percentages, and call return percentages. All of these checks are requested via ! commands that appear in comments in the test's source file. Commands to ! check line counts are processed by default. Commands to check branch ! percentages and call return percentages are processed if the 'run-gcov' ! command has arguments 'branches' or 'calls', respectively. For example, ! the following specifies checking both, as well as passing '-b' to ! 'gcov': { dg-final { run-gcov branches calls { -b sourcefile } } } A line count command appears within a comment on the source line that ! is expected to get the specified count and has the form 'count(CNT)'. A ! test should only check line counts for lines that will get the same count for any architecture. ! Commands to check branch percentages ('branch') and call return ! percentages ('returns') are very similar to each other. A beginning command appears on or before the first of a range of lines that will report the percentage, and the ending command follows that range of lines. The beginning command can include a list of percentages, all of which are expected to be found within the range. A range is terminated ! by the next command of the same kind. A command 'branch(end)' or ! 'returns(end)' marks the end of a range without starting a new one. For ! example: if (i > 10 && j > i && j < 20) /* branch(27 50 75) */ /* branch(end) */ --- 5859,5938 ---- that are compiled separately, perhaps with different sets of options. There are several special-purpose test directives used for these tests. ! `{ dg-lto-do DO-WHAT-KEYWORD }' DO-WHAT-KEYWORD specifies how the test is compiled and whether it is executed. It is one of: ! `assemble' ! Compile with `-c' to produce a relocatable object file. ! ! `link' Compile, assemble, and link to produce an executable file. ! ! `run' Produce and run an executable file, which is expected to return an exit code of 0. ! The default is `assemble'. That can be overridden for a set of ! tests by redefining `dg-do-what-default' within the `.exp' file ! for those tests. ! Unlike `dg-do', `dg-lto-do' does not support an optional `target' ! or `xfail' list. Use `dg-skip-if', `dg-xfail-if', or ! `dg-xfail-run-if'. ! `{ dg-lto-options { { OPTIONS } [{ OPTIONS }] } [{ target SELECTOR }]}' This directive provides a list of one or more sets of compiler options to override LTO_OPTIONS. Each test will be compiled and run with each of these sets of options. ! `{ dg-extra-ld-options OPTIONS [{ target SELECTOR }]}' This directive adds OPTIONS to the linker options used. ! `{ dg-suppress-ld-options OPTIONS [{ target SELECTOR }]}' This directive removes OPTIONS from the set of linker options used.  File: gccint.info, Node: gcov Testing, Next: profopt Testing, Prev: LTO Testing, Up: Testsuites ! 7.7 Support for testing `gcov' ============================== ! Language-independent support for testing `gcov', and for checking that branch profiling produces expected values, is provided by the expect ! file `lib/gcov.exp'. `gcov' tests also rely on procedures in ! `lib/gcc-dg.exp' to compile and run the test program. A typical `gcov' test contains the following DejaGnu commands within comments: { dg-options "-fprofile-arcs -ftest-coverage" } { dg-do run { target native } } { dg-final { run-gcov sourcefile } } ! Checks of `gcov' output can include line counts, branch percentages, and call return percentages. All of these checks are requested via ! commands that appear in comments in the test's source file. Commands ! to check line counts are processed by default. Commands to check ! branch percentages and call return percentages are processed if the ! `run-gcov' command has arguments `branches' or `calls', respectively. ! For example, the following specifies checking both, as well as passing ! `-b' to `gcov': { dg-final { run-gcov branches calls { -b sourcefile } } } A line count command appears within a comment on the source line that ! is expected to get the specified count and has the form `count(CNT)'. ! A test should only check line counts for lines that will get the same count for any architecture. ! Commands to check branch percentages (`branch') and call return ! percentages (`returns') are very similar to each other. A beginning command appears on or before the first of a range of lines that will report the percentage, and the ending command follows that range of lines. The beginning command can include a list of percentages, all of which are expected to be found within the range. A range is terminated ! by the next command of the same kind. A command `branch(end)' or ! `returns(end)' marks the end of a range without starting a new one. ! For example: if (i > 10 && j > i && j < 20) /* branch(27 50 75) */ /* branch(end) */ *************** calls reported to return. For a branch *** 5809,5818 **** the expected percentage or 100 minus that value, since the direction of a branch can differ depending on the target or the optimization level. ! Not all branches and calls need to be checked. A test should not check ! for branches that might be optimized away or replaced with predicated ! instructions. Don't check for calls inserted by the compiler or ones ! that might be inlined or optimized away. A single test can check for combinations of line counts, branch percentages, and call return percentages. The command to check a line --- 5943,5952 ---- the expected percentage or 100 minus that value, since the direction of a branch can differ depending on the target or the optimization level. ! Not all branches and calls need to be checked. A test should not ! check for branches that might be optimized away or replaced with ! predicated instructions. Don't check for calls inserted by the ! compiler or ones that might be inlined or optimized away. A single test can check for combinations of line counts, branch percentages, and call return percentages. The command to check a line *************** File: gccint.info, Node: profopt Testin *** 5826,5869 **** 7.8 Support for testing profile-directed optimizations ====================================================== ! The file 'profopt.exp' provides language-independent support for checking correct execution of a test built with profile-directed optimization. This testing requires that a test program be built and ! executed twice. The first time it is compiled to generate profile data, ! and the second time it is compiled to use the data that was generated ! during the first execution. The second execution is to verify that the ! test produces the expected results. To check that the optimization actually generated better code, a test can be built and run a third time with normal optimizations to verify that the performance is better with the profile-directed optimizations. ! 'profopt.exp' has the beginnings of this kind of support. ! 'profopt.exp' provides generic support for profile-directed optimizations. Each set of tests that uses it provides information about a specific optimization: ! 'tool' ! tool being tested, e.g., 'gcc' ! 'profile_option' options used to generate profile data ! 'feedback_option' options used to optimize using that profile data ! 'prof_ext' suffix of profile data files ! 'PROFOPT_OPTIONS' list of options with which to run each test, similar to the lists for torture tests ! '{ dg-final-generate { LOCAL-DIRECTIVE } }' ! This directive is similar to 'dg-final', but the LOCAL-DIRECTIVE is ! run after the generation of profile data. ! '{ dg-final-use { LOCAL-DIRECTIVE } }' The LOCAL-DIRECTIVE is run after the profile data have been used.  --- 5960,6003 ---- 7.8 Support for testing profile-directed optimizations ====================================================== ! The file `profopt.exp' provides language-independent support for checking correct execution of a test built with profile-directed optimization. This testing requires that a test program be built and ! executed twice. The first time it is compiled to generate profile ! data, and the second time it is compiled to use the data that was ! generated during the first execution. The second execution is to ! verify that the test produces the expected results. To check that the optimization actually generated better code, a test can be built and run a third time with normal optimizations to verify that the performance is better with the profile-directed optimizations. ! `profopt.exp' has the beginnings of this kind of support. ! `profopt.exp' provides generic support for profile-directed optimizations. Each set of tests that uses it provides information about a specific optimization: ! `tool' ! tool being tested, e.g., `gcc' ! `profile_option' options used to generate profile data ! `feedback_option' options used to optimize using that profile data ! `prof_ext' suffix of profile data files ! `PROFOPT_OPTIONS' list of options with which to run each test, similar to the lists for torture tests ! `{ dg-final-generate { LOCAL-DIRECTIVE } }' ! This directive is similar to `dg-final', but the LOCAL-DIRECTIVE ! is run after the generation of profile data. ! `{ dg-final-use { LOCAL-DIRECTIVE } }' The LOCAL-DIRECTIVE is run after the profile data have been used.  *************** File: gccint.info, Node: compat Testing *** 5872,5896 **** 7.9 Support for testing binary compatibility ============================================ ! The file 'compat.exp' provides language-independent support for binary compatibility testing. It supports testing interoperability of two compilers that follow the same ABI, or of multiple sets of compiler options that should not affect binary compatibility. It is intended to be used for testsuites that complement ABI testsuites. A test supported by this framework has three parts, each in a separate ! source file: a main program and two pieces that interact with each other ! to split up the functionality being tested. ! 'TESTNAME_main.SUFFIX' Contains the main program, which calls a function in file ! 'TESTNAME_x.SUFFIX'. ! 'TESTNAME_x.SUFFIX' ! Contains at least one call to a function in 'TESTNAME_y.SUFFIX'. ! 'TESTNAME_y.SUFFIX' ! Shares data with, or gets arguments from, 'TESTNAME_x.SUFFIX'. Within each test, the main program and one functional piece are compiled by the GCC under test. The other piece can be compiled by an --- 6006,6030 ---- 7.9 Support for testing binary compatibility ============================================ ! The file `compat.exp' provides language-independent support for binary compatibility testing. It supports testing interoperability of two compilers that follow the same ABI, or of multiple sets of compiler options that should not affect binary compatibility. It is intended to be used for testsuites that complement ABI testsuites. A test supported by this framework has three parts, each in a separate ! source file: a main program and two pieces that interact with each ! other to split up the functionality being tested. ! `TESTNAME_main.SUFFIX' Contains the main program, which calls a function in file ! `TESTNAME_x.SUFFIX'. ! `TESTNAME_x.SUFFIX' ! Contains at least one call to a function in `TESTNAME_y.SUFFIX'. ! `TESTNAME_y.SUFFIX' ! Shares data with, or gets arguments from, `TESTNAME_x.SUFFIX'. Within each test, the main program and one functional piece are compiled by the GCC under test. The other piece can be compiled by an *************** pair specifies options used with the GCC *** 5901,5933 **** element of the pair specifies options used with the alternate compiler. Each test is compiled with each pair of options. ! 'compat.exp' defines default pairs of compiler options. These can be ! overridden by defining the environment variable 'COMPAT_OPTIONS' as: COMPAT_OPTIONS="[list [list {TST1} {ALT1}] ...[list {TSTN} {ALTN}]]" where TSTI and ALTI are lists of options, with TSTI used by the compiler under test and ALTI used by the alternate compiler. For ! example, with '[list [list {-g -O0} {-O3}] [list {-fpic} {-fPIC -O2}]]', ! the test is first built with '-g -O0' by the compiler under test and ! with '-O3' by the alternate compiler. The test is built a second time ! using '-fpic' by the compiler under test and '-fPIC -O2' by the alternate compiler. An alternate compiler is specified by defining an environment variable to be the full pathname of an installed compiler; for C define ! 'ALT_CC_UNDER_TEST', and for C++ define 'ALT_CXX_UNDER_TEST'. These ! will be written to the 'site.exp' file used by DejaGnu. The default is to build each test with the compiler under test using the first of each ! pair of compiler options from 'COMPAT_OPTIONS'. When ! 'ALT_CC_UNDER_TEST' or 'ALT_CXX_UNDER_TEST' is 'same', each test is ! built using the compiler under test but with combinations of the options ! from 'COMPAT_OPTIONS'. To run only the C++ compatibility suite using the compiler under test and another version of GCC using specific compiler options, do the ! following from 'OBJDIR/gcc': rm site.exp make -k \ --- 6035,6067 ---- element of the pair specifies options used with the alternate compiler. Each test is compiled with each pair of options. ! `compat.exp' defines default pairs of compiler options. These can be ! overridden by defining the environment variable `COMPAT_OPTIONS' as: COMPAT_OPTIONS="[list [list {TST1} {ALT1}] ...[list {TSTN} {ALTN}]]" where TSTI and ALTI are lists of options, with TSTI used by the compiler under test and ALTI used by the alternate compiler. For ! example, with `[list [list {-g -O0} {-O3}] [list {-fpic} {-fPIC -O2}]]', ! the test is first built with `-g -O0' by the compiler under test and ! with `-O3' by the alternate compiler. The test is built a second time ! using `-fpic' by the compiler under test and `-fPIC -O2' by the alternate compiler. An alternate compiler is specified by defining an environment variable to be the full pathname of an installed compiler; for C define ! `ALT_CC_UNDER_TEST', and for C++ define `ALT_CXX_UNDER_TEST'. These ! will be written to the `site.exp' file used by DejaGnu. The default is to build each test with the compiler under test using the first of each ! pair of compiler options from `COMPAT_OPTIONS'. When ! `ALT_CC_UNDER_TEST' or `ALT_CXX_UNDER_TEST' is `same', each test is ! built using the compiler under test but with combinations of the ! options from `COMPAT_OPTIONS'. To run only the C++ compatibility suite using the compiler under test and another version of GCC using specific compiler options, do the ! following from `OBJDIR/gcc': rm site.exp make -k \ *************** compiler under test but is present in th *** 5946,5962 **** The binary compatibility tests support a small number of test framework commands that appear within comments in a test file. ! 'dg-require-*' ! These commands can be used in 'TESTNAME_main.SUFFIX' to skip the test if specific support is not available on the target. ! 'dg-options' The specified options are used for compiling this particular source ! file, appended to the options from 'COMPAT_OPTIONS'. When this ! command appears in 'TESTNAME_main.SUFFIX' the options are also used ! to link the test program. ! 'dg-xfail-if' This command can be used in a secondary source file to specify that compilation is expected to fail for particular options on particular targets. --- 6080,6096 ---- The binary compatibility tests support a small number of test framework commands that appear within comments in a test file. ! `dg-require-*' ! These commands can be used in `TESTNAME_main.SUFFIX' to skip the test if specific support is not available on the target. ! `dg-options' The specified options are used for compiling this particular source ! file, appended to the options from `COMPAT_OPTIONS'. When this ! command appears in `TESTNAME_main.SUFFIX' the options are also ! used to link the test program. ! `dg-xfail-if' This command can be used in a secondary source file to specify that compilation is expected to fail for particular options on particular targets. *************** File: gccint.info, Node: Torture Tests, *** 5969,6004 **** Throughout the compiler testsuite there are several directories whose tests are run multiple times, each with a different set of options. ! These are known as torture tests. 'lib/torture-options.exp' defines procedures to set up these lists: ! 'torture-init' Initialize use of torture lists. ! 'set-torture-options' Set lists of torture options to use for tests with and without loops. Optionally combine a set of torture options with a set of other options, as is done with Objective-C runtime options. ! 'torture-finish' Finalize use of torture lists. ! The '.exp' file for a set of tests that use torture options must include calls to these three procedures if: ! * It calls 'gcc-dg-runtest' and overrides DG_TORTURE_OPTIONS. ! * It calls ${TOOL}'-torture' or ${TOOL}'-torture-execute', where TOOL ! is 'c', 'fortran', or 'objc'. ! * It calls 'dg-pch'. ! It is not necessary for a '.exp' file that calls 'gcc-dg-runtest' to call the torture procedures if the tests should use the list in ! DG_TORTURE_OPTIONS defined in 'gcc-dg.exp'. Most uses of torture options can override the default lists by defining TORTURE_OPTIONS or add to the default list by defining ! ADDITIONAL_TORTURE_OPTIONS. Define these in a '.dejagnurc' file or add ! them to the 'site.exp' file; for example set ADDITIONAL_TORTURE_OPTIONS [list \ { -O2 -ftree-loop-linear } \ --- 6103,6140 ---- Throughout the compiler testsuite there are several directories whose tests are run multiple times, each with a different set of options. ! These are known as torture tests. `lib/torture-options.exp' defines procedures to set up these lists: ! `torture-init' Initialize use of torture lists. ! ! `set-torture-options' Set lists of torture options to use for tests with and without loops. Optionally combine a set of torture options with a set of other options, as is done with Objective-C runtime options. ! ! `torture-finish' Finalize use of torture lists. ! The `.exp' file for a set of tests that use torture options must include calls to these three procedures if: ! * It calls `gcc-dg-runtest' and overrides DG_TORTURE_OPTIONS. ! * It calls ${TOOL}`-torture' or ${TOOL}`-torture-execute', where ! TOOL is `c', `fortran', or `objc'. ! * It calls `dg-pch'. ! It is not necessary for a `.exp' file that calls `gcc-dg-runtest' to call the torture procedures if the tests should use the list in ! DG_TORTURE_OPTIONS defined in `gcc-dg.exp'. Most uses of torture options can override the default lists by defining TORTURE_OPTIONS or add to the default list by defining ! ADDITIONAL_TORTURE_OPTIONS. Define these in a `.dejagnurc' file or add ! them to the `site.exp' file; for example set ADDITIONAL_TORTURE_OPTIONS [list \ { -O2 -ftree-loop-linear } \ *************** File: gccint.info, Node: Options, Next *** 6010,6018 **** 8 Option specification files **************************** ! Most GCC command-line options are described by special option definition ! files, the names of which conventionally end in '.opt'. This chapter ! describes the format of these files. * Menu: --- 6146,6154 ---- 8 Option specification files **************************** ! Most GCC command-line options are described by special option ! definition files, the names of which conventionally end in `.opt'. ! This chapter describes the format of these files. * Menu: *************** semicolon. *** 6034,6159 **** The files can contain the following types of record: * A language definition record. These records have two fields: the ! string 'Language' and the name of the language. Once a language has been declared in this way, it can be used as an option property. *Note Option properties::. ! * A target specific save record to save additional information. ! These records have two fields: the string 'TargetSave', and a ! declaration type to go in the 'cl_target_option' structure. * A variable record to define a variable used to store option ! information. These records have two fields: the string 'Variable', ! and a declaration of the type and name of the variable, optionally ! with an initializer (but without any trailing ';'). These records ! may be used for variables used for many options where declaring the ! initializer in a single option definition record, or duplicating it ! in many records, would be inappropriate, or for variables set in ! option handlers rather than referenced by 'Var' properties. * A variable record to define a variable used to store option information. These records have two fields: the string ! 'TargetVariable', and a declaration of the type and name of the variable, optionally with an initializer (but without any trailing ! ';'). 'TargetVariable' is a combination of 'Variable' and ! 'TargetSave' records in that the variable is defined in the ! 'gcc_options' structure, but these variables are also stored in the ! 'cl_target_option' structure. The variables are saved in the target save code and restored in the target restore code. * A variable record to record any additional files that the ! 'options.h' file should include. This is useful to provide enumeration or structure definitions needed for target variables. ! These records have two fields: the string 'HeaderInclude' and the name of the include file. * A variable record to record any additional files that the ! 'options.c' or 'options-save.c' file should include. This is useful to provide inline functions needed for target variables ! and/or '#ifdef' sequences to properly set up the initialization. ! These records have two fields: the string 'SourceInclude' and the name of the include file. * An enumeration record to define a set of strings that may be used as arguments to an option or options. These records have three ! fields: the string 'Enum', a space-separated list of properties and ! help text used to describe the set of strings in '--help' output. ! Properties use the same format as option properties; the following ! are valid: ! 'Name(NAME)' This property is required; NAME must be a name (suitable for use in C identifiers) used to identify the set of strings in ! 'Enum' option properties. ! 'Type(TYPE)' This property is required; TYPE is the C type for variables ! set by options using this enumeration together with 'Var'. ! 'UnknownError(MESSAGE)' The message MESSAGE will be used as an error message if the ! argument is invalid; for enumerations without 'UnknownError', a generic error message is used. MESSAGE should contain a ! single '%qs' format, which will be used to format the invalid argument. * An enumeration value record to define one of the strings in a set ! given in an 'Enum' record. These records have two fields: the ! string 'EnumValue' and a space-separated list of properties. Properties use the same format as option properties; the following are valid: ! 'Enum(NAME)' ! This property is required; NAME says which 'Enum' record this ! 'EnumValue' record corresponds to. ! 'String(STRING)' This property is required; STRING is the string option argument being described by this record. ! 'Value(VALUE)' This property is required; it says what value (representable ! as 'int') should be used for the given string. ! 'Canonical' This property is optional. If present, it says the present string is the canonical one among all those with the given value. Other strings yielding that value will be mapped to this one so specs do not need to handle them. ! 'DriverOnly' This property is optional. If present, the present string will only be accepted by the driver. This is used for cases ! such as '-march=native' that are processed by the driver so ! that 'gcc -v' shows how the options chosen depended on the system on which the compiler was run. * An option definition record. These records have the following fields: 1. the name of the option, with the leading "-" removed 2. a space-separated list of option properties (*note Option properties::) ! 3. the help text to use for '--help' (omitted if the second field ! contains the 'Undocumented' property). By default, all options beginning with "f", "W" or "m" are implicitly assumed to take a "no-" form. This form should not be listed separately. If an option beginning with one of these letters does not have a "no-" form, you can use the ! 'RejectNegative' property to reject it. The help text is automatically line-wrapped before being displayed. Normally the name of the option is printed on the left-hand side of the output and the help text is printed on the right. However, if ! the help text contains a tab character, the text to the left of the ! tab is used instead of the option's name and the text to the right ! of the tab forms the help text. This allows you to elaborate on ! what type of argument the option takes. * A target mask record. These records have one field of the form ! 'Mask(X)'. The options-processing script will automatically ! allocate a bit in 'target_flags' (*note Run-time Target::) for each ! mask name X and set the macro 'MASK_X' to the appropriate bitmask. ! It will also declare a 'TARGET_X' macro that has the value 1 when ! bit 'MASK_X' is set and 0 otherwise. They are primarily intended to declare target masks that are not associated with user options, either because these masks represent --- 6170,6298 ---- The files can contain the following types of record: * A language definition record. These records have two fields: the ! string `Language' and the name of the language. Once a language has been declared in this way, it can be used as an option property. *Note Option properties::. ! * A target specific save record to save additional information. These ! records have two fields: the string `TargetSave', and a ! declaration type to go in the `cl_target_option' structure. * A variable record to define a variable used to store option ! information. These records have two fields: the string ! `Variable', and a declaration of the type and name of the ! variable, optionally with an initializer (but without any trailing ! `;'). These records may be used for variables used for many ! options where declaring the initializer in a single option ! definition record, or duplicating it in many records, would be ! inappropriate, or for variables set in option handlers rather than ! referenced by `Var' properties. * A variable record to define a variable used to store option information. These records have two fields: the string ! `TargetVariable', and a declaration of the type and name of the variable, optionally with an initializer (but without any trailing ! `;'). `TargetVariable' is a combination of `Variable' and ! `TargetSave' records in that the variable is defined in the ! `gcc_options' structure, but these variables are also stored in ! the `cl_target_option' structure. The variables are saved in the target save code and restored in the target restore code. * A variable record to record any additional files that the ! `options.h' file should include. This is useful to provide enumeration or structure definitions needed for target variables. ! These records have two fields: the string `HeaderInclude' and the name of the include file. * A variable record to record any additional files that the ! `options.c' or `options-save.c' file should include. This is useful to provide inline functions needed for target variables ! and/or `#ifdef' sequences to properly set up the initialization. ! These records have two fields: the string `SourceInclude' and the name of the include file. * An enumeration record to define a set of strings that may be used as arguments to an option or options. These records have three ! fields: the string `Enum', a space-separated list of properties ! and help text used to describe the set of strings in `--help' ! output. Properties use the same format as option properties; the ! following are valid: ! `Name(NAME)' This property is required; NAME must be a name (suitable for use in C identifiers) used to identify the set of strings in ! `Enum' option properties. ! `Type(TYPE)' This property is required; TYPE is the C type for variables ! set by options using this enumeration together with `Var'. ! `UnknownError(MESSAGE)' The message MESSAGE will be used as an error message if the ! argument is invalid; for enumerations without `UnknownError', a generic error message is used. MESSAGE should contain a ! single `%qs' format, which will be used to format the invalid argument. * An enumeration value record to define one of the strings in a set ! given in an `Enum' record. These records have two fields: the ! string `EnumValue' and a space-separated list of properties. Properties use the same format as option properties; the following are valid: ! `Enum(NAME)' ! This property is required; NAME says which `Enum' record this ! `EnumValue' record corresponds to. ! `String(STRING)' This property is required; STRING is the string option argument being described by this record. ! `Value(VALUE)' This property is required; it says what value (representable ! as `int') should be used for the given string. ! `Canonical' This property is optional. If present, it says the present string is the canonical one among all those with the given value. Other strings yielding that value will be mapped to this one so specs do not need to handle them. ! `DriverOnly' This property is optional. If present, the present string will only be accepted by the driver. This is used for cases ! such as `-march=native' that are processed by the driver so ! that `gcc -v' shows how the options chosen depended on the system on which the compiler was run. * An option definition record. These records have the following fields: 1. the name of the option, with the leading "-" removed + 2. a space-separated list of option properties (*note Option properties::) ! ! 3. the help text to use for `--help' (omitted if the second field ! contains the `Undocumented' property). By default, all options beginning with "f", "W" or "m" are implicitly assumed to take a "no-" form. This form should not be listed separately. If an option beginning with one of these letters does not have a "no-" form, you can use the ! `RejectNegative' property to reject it. The help text is automatically line-wrapped before being displayed. Normally the name of the option is printed on the left-hand side of the output and the help text is printed on the right. However, if ! the help text contains a tab character, the text to the left of ! the tab is used instead of the option's name and the text to the ! right of the tab forms the help text. This allows you to ! elaborate on what type of argument the option takes. * A target mask record. These records have one field of the form ! `Mask(X)'. The options-processing script will automatically ! allocate a bit in `target_flags' (*note Run-time Target::) for ! each mask name X and set the macro `MASK_X' to the appropriate ! bitmask. It will also declare a `TARGET_X' macro that has the ! value 1 when bit `MASK_X' is set and 0 otherwise. They are primarily intended to declare target masks that are not associated with user options, either because these masks represent *************** File: gccint.info, Node: Option propert *** 6168,6474 **** The second field of an option record can specify any of the following properties. When an option takes an argument, it is enclosed in ! parentheses following the option property name. The parser that handles ! option files is quite simplistic, and will be tricked by any nested ! parentheses within the argument text itself; in this case, the entire ! option argument can be wrapped in curly braces within the parentheses to ! demarcate it, e.g.: Condition({defined (USE_CYGWIN_LIBSTDCXX_WRAPPERS)}) ! 'Common' The option is available for all languages and targets. ! 'Target' The option is available for all languages but is target-specific. ! 'Driver' The option is handled by the compiler driver using code not shared ! with the compilers proper ('cc1' etc.). ! 'LANGUAGE' The option is available when compiling for the given language. It is possible to specify several different languages for the same option. Each LANGUAGE must have been declared by an earlier ! 'Language' record. *Note Option file format::. ! 'RejectDriver' ! The option is only handled by the compilers proper ('cc1' etc.) and ! should not be accepted by the driver. ! 'RejectNegative' The option does not have a "no-" form. All options beginning with "f", "W" or "m" are assumed to have a "no-" form unless this property is used. ! 'Negative(OTHERNAME)' The option will turn off another option OTHERNAME, which is the option name with the leading "-" removed. This chain action will ! propagate through the 'Negative' property of the option to be turned off. As a consequence, if you have a group of mutually-exclusive ! options, their 'Negative' properties should form a circular chain. ! For example, if options '-A', '-B' and '-C' are mutually exclusive, ! their respective 'Negative' properties should be 'Negative(B)', ! 'Negative(C)' and 'Negative(A)'. ! 'Joined' ! 'Separate' ! The option takes a mandatory argument. 'Joined' indicates that the ! option and argument can be included in the same 'argv' entry (as ! with '-mflush-func=NAME', for example). 'Separate' indicates that ! the option and argument can be separate 'argv' entries (as with ! '-o'). An option is allowed to have both of these properties. ! 'JoinedOrMissing' The option takes an optional argument. If the argument is given, ! it will be part of the same 'argv' entry as the option itself. ! This property cannot be used alongside 'Joined' or 'Separate'. ! 'MissingArgError(MESSAGE)' ! For an option marked 'Joined' or 'Separate', the message MESSAGE will be used as an error message if the mandatory argument is ! missing; for options without 'MissingArgError', a generic error ! message is used. MESSAGE should contain a single '%qs' format, which will be used to format the name of the option passed. ! 'Args(N)' ! For an option marked 'Separate', indicate that it takes N arguments. The default is 1. ! 'UInteger' The option's argument is a non-negative integer. The option parser will check and convert the argument before passing it to the ! relevant option handler. 'UInteger' should also be used on options ! like '-falign-loops' where both '-falign-loops' and ! '-falign-loops'=N are supported to make sure the saved options are given a full integer. ! 'ToLower' The option's argument should be converted to lowercase as part of putting it in canonical form, and before comparing with the strings ! indicated by any 'Enum' property. ! 'NoDriverArg' ! For an option marked 'Separate', the option only takes an argument in the compiler proper, not in the driver. This is for compatibility with existing options that are used both directly and ! via '-Wp,'; new options should not have this property. ! 'Var(VAR)' ! The state of this option should be stored in variable VAR (actually ! a macro for 'global_options.x_VAR'). The way that the state is ! stored depends on the type of option: ! * If the option uses the 'Mask' or 'InverseMask' properties, VAR ! is the integer variable that contains the mask. * If the option is a normal on/off switch, VAR is an integer variable that is nonzero when the option is enabled. The options parser will set the variable to 1 when the positive form of the option is used and 0 when the "no-" form is used. ! * If the option takes an argument and has the 'UInteger' property, VAR is an integer variable that stores the value of the argument. ! * If the option takes an argument and has the 'Enum' property, ! VAR is a variable (type given in the 'Type' property of the ! 'Enum' record whose 'Name' property has the same argument as ! the 'Enum' property of this option) that stores the value of the argument. ! * If the option has the 'Defer' property, VAR is a pointer to a ! 'VEC(cl_deferred_option,heap)' that stores the option for ! later processing. (VAR is declared with type 'void *' and ! needs to be cast to 'VEC(cl_deferred_option,heap)' before use.) * Otherwise, if the option takes an argument, VAR is a pointer to the argument string. The pointer will be null if the argument is optional and wasn't given. ! The option-processing script will usually zero-initialize VAR. You ! can modify this behavior using 'Init'. ! 'Var(VAR, SET)' The option controls an integer variable VAR and is active when VAR equals SET. The option parser will set VAR to SET when the ! positive form of the option is used and '!SET' when the "no-" form is used. VAR is declared in the same way as for the single-argument form described above. ! 'Init(VALUE)' ! The variable specified by the 'Var' property should be statically initialized to VALUE. If more than one option using the same ! variable specifies 'Init', all must specify the same initializer. ! 'Mask(NAME)' ! The option is associated with a bit in the 'target_flags' variable (*note Run-time Target::) and is active when that bit is set. You ! may also specify 'Var' to select a variable other than ! 'target_flags'. The options-processing script will automatically allocate a unique ! bit for the option. If the option is attached to 'target_flags', ! the script will set the macro 'MASK_NAME' to the appropriate ! bitmask. It will also declare a 'TARGET_NAME' macro that has the value 1 when the option is active and 0 otherwise. If you use ! 'Var' to attach the option to a different variable, the bitmask ! macro with be called 'OPTION_MASK_NAME'. ! 'InverseMask(OTHERNAME)' ! 'InverseMask(OTHERNAME, THISNAME)' The option is the inverse of another option that has the ! 'Mask(OTHERNAME)' property. If THISNAME is given, the ! options-processing script will declare a 'TARGET_THISNAME' macro that is 1 when the option is active and 0 otherwise. ! 'Enum(NAME)' The option's argument is a string from the set of strings ! associated with the corresponding 'Enum' record. The string is checked and converted to the integer specified in the corresponding ! 'EnumValue' record before being passed to option handlers. ! 'Defer' ! The option should be stored in a vector, specified with 'Var', for later processing. ! 'Alias(OPT)' ! 'Alias(OPT, ARG)' ! 'Alias(OPT, POSARG, NEGARG)' ! The option is an alias for '-OPT' (or the negative form of that ! option, depending on 'NegativeAlias'). In the first form, any ! argument passed to the alias is considered to be passed to '-OPT', ! and '-OPT' is considered to be negated if the alias is used in negated form. In the second form, the alias may not be negated or have an argument, and POSARG is considered to be passed as an ! argument to '-OPT'. In the third form, the alias may not have an argument, if the alias is used in the positive form then POSARG is ! considered to be passed to '-OPT', and if the alias is used in the ! negative form then NEGARG is considered to be passed to '-OPT'. ! Aliases should not specify 'Var' or 'Mask' or 'UInteger'. Aliases should normally specify the same languages as the target of the alias; the flags on the target will be used to determine any ! diagnostic for use of an option for the wrong language, while those ! on the alias will be used to identify what command-line text is the ! option and what text is any argument to that option. ! When an 'Alias' definition is used for an option, driver specs do ! not need to handle it and no 'OPT_' enumeration value is defined for it; only the canonical form of the option will be seen in those places. ! 'NegativeAlias' ! For an option marked with 'Alias(OPT)', the option is considered to ! be an alias for the positive form of '-OPT' if negated and for the ! negative form of '-OPT' if not negated. 'NegativeAlias' may not be ! used with the forms of 'Alias' taking more than one argument. ! 'Ignore' This option is ignored apart from printing any warning specified ! using 'Warn'. The option will not be seen by specs and no 'OPT_' enumeration value is defined for it. ! 'SeparateAlias' ! For an option marked with 'Joined', 'Separate' and 'Alias', the option only acts as an alias when passed a separate argument; with ! a joined argument it acts as a normal option, with an 'OPT_' ! enumeration value. This is for compatibility with the Java '-d' option and should not be used for new options. ! 'Warn(MESSAGE)' If this option is used, output the warning MESSAGE. MESSAGE is a ! format string, either taking a single operand with a '%qs' format which is the option name, or not taking any operands, which is ! passed to the 'warning' function. If an alias is marked 'Warn', ! the target of the alias must not also be marked 'Warn'. ! 'Report' ! The state of the option should be printed by '-fverbose-asm'. ! 'Warning' ! This is a warning option and should be shown as such in '--help' output. This flag does not currently affect anything other than ! '--help'. ! 'Optimization' This is an optimization option. It should be shown as such in ! '--help' output, and any associated variable named using 'Var' ! should be saved and restored when the optimization level is changed ! with 'optimize' attributes. ! 'Undocumented' The option is deliberately missing documentation and should not be ! included in the '--help' output. ! 'Condition(COND)' The option should only be accepted if preprocessor condition COND is true. Note that any C declarations associated with the option ! will be present even if COND is false; COND simply controls whether ! the option is accepted and whether it is printed in the '--help' ! output. ! 'Save' ! Build the 'cl_target_option' structure to hold a copy of the ! option, add the functions 'cl_target_option_save' and ! 'cl_target_option_restore' to save and restore the options. ! 'SetByCombined' The option may also be set by a combined option such as ! '-ffast-math'. This causes the 'gcc_options' struct to have a ! field 'frontend_set_NAME', where 'NAME' is the name of the field ! holding the value of this option (without the leading 'x_'). This gives the front end a way to indicate that the value has been set explicitly and should not be changed by the combined option. For ! example, some front ends use this to prevent '-ffast-math' and ! '-fno-fast-math' from changing the value of '-fmath-errno' for ! languages that do not use 'errno'. ! 'EnabledBy(OPT)' ! 'EnabledBy(OPT || OPT2)' ! 'EnabledBy(OPT && OPT2)' ! If not explicitly set, the option is set to the value of '-OPT'; ! multiple options can be given, separated by '||'. The third form ! using '&&' specifies that the option is only set if both OPT and ! OPT2 are set. The options OPT and OPT2 must have the 'Common' ! property; otherwise, use 'LangEnabledBy'. ! 'LangEnabledBy(LANGUAGE, OPT)' ! 'LangEnabledBy(LANGUAGE, OPT, POSARG, NEGARG)' When compiling for the given language, the option is set to the ! value of '-OPT', if not explicitly set. OPT can be also a list of ! '||' separated options. In the second form, if OPT is used in the ! positive form then POSARG is considered to be passed to the option, ! and if OPT is used in the negative form then NEGARG is considered ! to be passed to the option. It is possible to specify several ! different languages. Each LANGUAGE must have been declared by an ! earlier 'Language' record. *Note Option file format::. ! 'NoDWARFRecord' The option is omitted from the producer string written by ! '-grecord-gcc-switches'. ! 'PchIgnore' ! Even if this is a target option, this option will not be recorded / ! compared to determine if a precompiled header file matches. ! 'CPP(VAR)' The state of this option should be kept in sync with the preprocessor option VAR. If this property is set, then properties ! 'Var' and 'Init' must be set as well. ! 'CppReason(CPP_W_ENUM)' ! This warning option corresponds to 'cpplib.h' warning reason code CPP_W_ENUM. This should only be used for warning options of the C-family front-ends.  File: gccint.info, Node: Passes, Next: GENERIC, Prev: Options, Up: Top --- 6307,6616 ---- The second field of an option record can specify any of the following properties. When an option takes an argument, it is enclosed in ! parentheses following the option property name. The parser that ! handles option files is quite simplistic, and will be tricked by any ! nested parentheses within the argument text itself; in this case, the ! entire option argument can be wrapped in curly braces within the ! parentheses to demarcate it, e.g.: Condition({defined (USE_CYGWIN_LIBSTDCXX_WRAPPERS)}) ! `Common' The option is available for all languages and targets. ! `Target' The option is available for all languages but is target-specific. ! `Driver' The option is handled by the compiler driver using code not shared ! with the compilers proper (`cc1' etc.). ! `LANGUAGE' The option is available when compiling for the given language. It is possible to specify several different languages for the same option. Each LANGUAGE must have been declared by an earlier ! `Language' record. *Note Option file format::. ! `RejectDriver' ! The option is only handled by the compilers proper (`cc1' etc.) ! and should not be accepted by the driver. ! `RejectNegative' The option does not have a "no-" form. All options beginning with "f", "W" or "m" are assumed to have a "no-" form unless this property is used. ! `Negative(OTHERNAME)' The option will turn off another option OTHERNAME, which is the option name with the leading "-" removed. This chain action will ! propagate through the `Negative' property of the option to be turned off. As a consequence, if you have a group of mutually-exclusive ! options, their `Negative' properties should form a circular chain. ! For example, if options `-A', `-B' and `-C' are mutually ! exclusive, their respective `Negative' properties should be ! `Negative(B)', `Negative(C)' and `Negative(A)'. ! `Joined' ! `Separate' ! The option takes a mandatory argument. `Joined' indicates that ! the option and argument can be included in the same `argv' entry ! (as with `-mflush-func=NAME', for example). `Separate' indicates ! that the option and argument can be separate `argv' entries (as ! with `-o'). An option is allowed to have both of these properties. ! `JoinedOrMissing' The option takes an optional argument. If the argument is given, ! it will be part of the same `argv' entry as the option itself. ! This property cannot be used alongside `Joined' or `Separate'. ! `MissingArgError(MESSAGE)' ! For an option marked `Joined' or `Separate', the message MESSAGE will be used as an error message if the mandatory argument is ! missing; for options without `MissingArgError', a generic error ! message is used. MESSAGE should contain a single `%qs' format, which will be used to format the name of the option passed. ! `Args(N)' ! For an option marked `Separate', indicate that it takes N arguments. The default is 1. ! `UInteger' The option's argument is a non-negative integer. The option parser will check and convert the argument before passing it to the ! relevant option handler. `UInteger' should also be used on ! options like `-falign-loops' where both `-falign-loops' and ! `-falign-loops'=N are supported to make sure the saved options are given a full integer. ! `ToLower' The option's argument should be converted to lowercase as part of putting it in canonical form, and before comparing with the strings ! indicated by any `Enum' property. ! `NoDriverArg' ! For an option marked `Separate', the option only takes an argument in the compiler proper, not in the driver. This is for compatibility with existing options that are used both directly and ! via `-Wp,'; new options should not have this property. ! `Var(VAR)' ! The state of this option should be stored in variable VAR ! (actually a macro for `global_options.x_VAR'). The way that the ! state is stored depends on the type of option: ! * If the option uses the `Mask' or `InverseMask' properties, ! VAR is the integer variable that contains the mask. * If the option is a normal on/off switch, VAR is an integer variable that is nonzero when the option is enabled. The options parser will set the variable to 1 when the positive form of the option is used and 0 when the "no-" form is used. ! * If the option takes an argument and has the `UInteger' property, VAR is an integer variable that stores the value of the argument. ! * If the option takes an argument and has the `Enum' property, ! VAR is a variable (type given in the `Type' property of the ! `Enum' record whose `Name' property has the same argument as ! the `Enum' property of this option) that stores the value of the argument. ! * If the option has the `Defer' property, VAR is a pointer to a ! `VEC(cl_deferred_option,heap)' that stores the option for ! later processing. (VAR is declared with type `void *' and ! needs to be cast to `VEC(cl_deferred_option,heap)' before use.) * Otherwise, if the option takes an argument, VAR is a pointer to the argument string. The pointer will be null if the argument is optional and wasn't given. ! The option-processing script will usually zero-initialize VAR. ! You can modify this behavior using `Init'. ! `Var(VAR, SET)' The option controls an integer variable VAR and is active when VAR equals SET. The option parser will set VAR to SET when the ! positive form of the option is used and `!SET' when the "no-" form is used. VAR is declared in the same way as for the single-argument form described above. ! `Init(VALUE)' ! The variable specified by the `Var' property should be statically initialized to VALUE. If more than one option using the same ! variable specifies `Init', all must specify the same initializer. ! `Mask(NAME)' ! The option is associated with a bit in the `target_flags' variable (*note Run-time Target::) and is active when that bit is set. You ! may also specify `Var' to select a variable other than ! `target_flags'. The options-processing script will automatically allocate a unique ! bit for the option. If the option is attached to `target_flags', ! the script will set the macro `MASK_NAME' to the appropriate ! bitmask. It will also declare a `TARGET_NAME' macro that has the value 1 when the option is active and 0 otherwise. If you use ! `Var' to attach the option to a different variable, the bitmask ! macro with be called `OPTION_MASK_NAME'. ! `InverseMask(OTHERNAME)' ! `InverseMask(OTHERNAME, THISNAME)' The option is the inverse of another option that has the ! `Mask(OTHERNAME)' property. If THISNAME is given, the ! options-processing script will declare a `TARGET_THISNAME' macro that is 1 when the option is active and 0 otherwise. ! `Enum(NAME)' The option's argument is a string from the set of strings ! associated with the corresponding `Enum' record. The string is checked and converted to the integer specified in the corresponding ! `EnumValue' record before being passed to option handlers. ! `Defer' ! The option should be stored in a vector, specified with `Var', for later processing. ! `Alias(OPT)' ! `Alias(OPT, ARG)' ! `Alias(OPT, POSARG, NEGARG)' ! The option is an alias for `-OPT' (or the negative form of that ! option, depending on `NegativeAlias'). In the first form, any ! argument passed to the alias is considered to be passed to `-OPT', ! and `-OPT' is considered to be negated if the alias is used in negated form. In the second form, the alias may not be negated or have an argument, and POSARG is considered to be passed as an ! argument to `-OPT'. In the third form, the alias may not have an argument, if the alias is used in the positive form then POSARG is ! considered to be passed to `-OPT', and if the alias is used in the ! negative form then NEGARG is considered to be passed to `-OPT'. ! Aliases should not specify `Var' or `Mask' or `UInteger'. Aliases should normally specify the same languages as the target of the alias; the flags on the target will be used to determine any ! diagnostic for use of an option for the wrong language, while ! those on the alias will be used to identify what command-line text ! is the option and what text is any argument to that option. ! When an `Alias' definition is used for an option, driver specs do ! not need to handle it and no `OPT_' enumeration value is defined for it; only the canonical form of the option will be seen in those places. ! `NegativeAlias' ! For an option marked with `Alias(OPT)', the option is considered ! to be an alias for the positive form of `-OPT' if negated and for ! the negative form of `-OPT' if not negated. `NegativeAlias' may ! not be used with the forms of `Alias' taking more than one ! argument. ! `Ignore' This option is ignored apart from printing any warning specified ! using `Warn'. The option will not be seen by specs and no `OPT_' enumeration value is defined for it. ! `SeparateAlias' ! For an option marked with `Joined', `Separate' and `Alias', the option only acts as an alias when passed a separate argument; with ! a joined argument it acts as a normal option, with an `OPT_' ! enumeration value. This is for compatibility with the Java `-d' option and should not be used for new options. ! `Warn(MESSAGE)' If this option is used, output the warning MESSAGE. MESSAGE is a ! format string, either taking a single operand with a `%qs' format which is the option name, or not taking any operands, which is ! passed to the `warning' function. If an alias is marked `Warn', ! the target of the alias must not also be marked `Warn'. ! `Report' ! The state of the option should be printed by `-fverbose-asm'. ! `Warning' ! This is a warning option and should be shown as such in `--help' output. This flag does not currently affect anything other than ! `--help'. ! `Optimization' This is an optimization option. It should be shown as such in ! `--help' output, and any associated variable named using `Var' ! should be saved and restored when the optimization level is ! changed with `optimize' attributes. ! `Undocumented' The option is deliberately missing documentation and should not be ! included in the `--help' output. ! `Condition(COND)' The option should only be accepted if preprocessor condition COND is true. Note that any C declarations associated with the option ! will be present even if COND is false; COND simply controls ! whether the option is accepted and whether it is printed in the ! `--help' output. ! `Save' ! Build the `cl_target_option' structure to hold a copy of the ! option, add the functions `cl_target_option_save' and ! `cl_target_option_restore' to save and restore the options. ! `SetByCombined' The option may also be set by a combined option such as ! `-ffast-math'. This causes the `gcc_options' struct to have a ! field `frontend_set_NAME', where `NAME' is the name of the field ! holding the value of this option (without the leading `x_'). This gives the front end a way to indicate that the value has been set explicitly and should not be changed by the combined option. For ! example, some front ends use this to prevent `-ffast-math' and ! `-fno-fast-math' from changing the value of `-fmath-errno' for ! languages that do not use `errno'. ! `EnabledBy(OPT)' ! `EnabledBy(OPT || OPT2)' ! `EnabledBy(OPT && OPT2)' ! If not explicitly set, the option is set to the value of `-OPT'; ! multiple options can be given, separated by `||'. The third form ! using `&&' specifies that the option is only set if both OPT and ! OPT2 are set. The options OPT and OPT2 must have the `Common' ! property; otherwise, use `LangEnabledBy'. ! `LangEnabledBy(LANGUAGE, OPT)' ! `LangEnabledBy(LANGUAGE, OPT, POSARG, NEGARG)' When compiling for the given language, the option is set to the ! value of `-OPT', if not explicitly set. OPT can be also a list of ! `||' separated options. In the second form, if OPT is used in the ! positive form then POSARG is considered to be passed to the ! option, and if OPT is used in the negative form then NEGARG is ! considered to be passed to the option. It is possible to specify ! several different languages. Each LANGUAGE must have been ! declared by an earlier `Language' record. *Note Option file ! format::. ! `NoDWARFRecord' The option is omitted from the producer string written by ! `-grecord-gcc-switches'. ! `PchIgnore' ! Even if this is a target option, this option will not be recorded ! / compared to determine if a precompiled header file matches. ! `CPP(VAR)' The state of this option should be kept in sync with the preprocessor option VAR. If this property is set, then properties ! `Var' and `Init' must be set as well. ! `CppReason(CPP_W_ENUM)' ! This warning option corresponds to `cpplib.h' warning reason code CPP_W_ENUM. This should only be used for warning options of the C-family front-ends. +  File: gccint.info, Node: Passes, Next: GENERIC, Prev: Options, Up: Top *************** File: gccint.info, Node: Parsing pass, *** 6497,6534 **** ================ The language front end is invoked only once, via ! 'lang_hooks.parse_file', to parse the entire input. The language front ! end may use any intermediate language representation deemed appropriate. ! The C front end uses GENERIC trees (*note GENERIC::), plus a double ! handful of language specific tree codes defined in 'c-common.def'. The ! Fortran front end uses a completely different private representation. At some point the front end must translate the representation used in the front end to a representation understood by the language-independent ! portions of the compiler. Current practice takes one of two forms. The ! C front end manually invokes the gimplifier (*note GIMPLE::) on each ! function, and uses the gimplifier callbacks to convert the language-specific tree nodes directly to GIMPLE before passing the function off to be compiled. The Fortran front end converts from a ! private representation to GENERIC, which is later lowered to GIMPLE when ! the function is compiled. Which route to choose probably depends on how ! well GENERIC (plus extensions) can be made to match up with the source ! language and necessary parsing data structures. BUG: Gimplification must occur before nested function lowering, and nested function lowering must be done by the front end before passing the data off to cgraph. ! TODO: Cgraph should control nested function lowering. It would only be ! invoked when it is certain that the outer-most function is used. TODO: Cgraph needs a gimplify_function callback. It should be invoked when (1) it is certain that the function is used, (2) warning flags specified by the user require some amount of compilation in order to ! honor, (3) the language indicates that semantic analysis is not complete ! until gimplification occurs. Hum... this sounds overly complicated. ! Perhaps we should just have the front end gimplify always; in most cases ! it's only one function call. The front end needs to pass all function definitions and top level declarations off to the middle-end so that they can be compiled and --- 6639,6677 ---- ================ The language front end is invoked only once, via ! `lang_hooks.parse_file', to parse the entire input. The language front ! end may use any intermediate language representation deemed ! appropriate. The C front end uses GENERIC trees (*note GENERIC::), plus ! a double handful of language specific tree codes defined in ! `c-common.def'. The Fortran front end uses a completely different ! private representation. At some point the front end must translate the representation used in the front end to a representation understood by the language-independent ! portions of the compiler. Current practice takes one of two forms. ! The C front end manually invokes the gimplifier (*note GIMPLE::) on ! each function, and uses the gimplifier callbacks to convert the language-specific tree nodes directly to GIMPLE before passing the function off to be compiled. The Fortran front end converts from a ! private representation to GENERIC, which is later lowered to GIMPLE ! when the function is compiled. Which route to choose probably depends ! on how well GENERIC (plus extensions) can be made to match up with the ! source language and necessary parsing data structures. BUG: Gimplification must occur before nested function lowering, and nested function lowering must be done by the front end before passing the data off to cgraph. ! TODO: Cgraph should control nested function lowering. It would only ! be invoked when it is certain that the outer-most function is used. TODO: Cgraph needs a gimplify_function callback. It should be invoked when (1) it is certain that the function is used, (2) warning flags specified by the user require some amount of compilation in order to ! honor, (3) the language indicates that semantic analysis is not ! complete until gimplification occurs. Hum... this sounds overly ! complicated. Perhaps we should just have the front end gimplify ! always; in most cases it's only one function call. The front end needs to pass all function definitions and top level declarations off to the middle-end so that they can be compiled and *************** all be passed as well. *** 6543,6558 **** In any case, the front end needs each complete top-level function or data declaration, and each data definition should be passed to ! 'rest_of_decl_compilation'. Each complete type definition should be ! passed to 'rest_of_type_compilation'. Each function definition should ! be passed to 'cgraph_finalize_function'. TODO: I know rest_of_compilation currently has all sorts of RTL generation semantics. I plan to move all code generation bits (both ! Tree and RTL) to compile_function. Should we hide cgraph from the front ! ends and move back to rest_of_compilation as the official interface? ! Possibly we should rename all three interfaces such that the names match ! in some meaningful way and that is more descriptive than "rest_of". The middle-end will, at its option, emit the function and data definitions immediately or queue them for later processing. --- 6686,6702 ---- In any case, the front end needs each complete top-level function or data declaration, and each data definition should be passed to ! `rest_of_decl_compilation'. Each complete type definition should be ! passed to `rest_of_type_compilation'. Each function definition should ! be passed to `cgraph_finalize_function'. TODO: I know rest_of_compilation currently has all sorts of RTL generation semantics. I plan to move all code generation bits (both ! Tree and RTL) to compile_function. Should we hide cgraph from the ! front ends and move back to rest_of_compilation as the official ! interface? Possibly we should rename all three interfaces such that ! the names match in some meaningful way and that is more descriptive ! than "rest_of". The middle-end will, at its option, emit the function and data definitions immediately or queue them for later processing. *************** File: gccint.info, Node: Cilk Plus Tran *** 6563,6621 **** 9.2 Cilk Plus Transformation ============================ ! If Cilk Plus generation (flag '-fcilkplus') is enabled, all the Cilk Plus code is transformed into equivalent C and C++ functions. Majority of this transformation occurs toward the end of the parsing and right before the gimplification pass. These are the major components to the Cilk Plus language extension: * Array Notations: During parsing phase, all the array notation ! specific information is stored in 'ARRAY_NOTATION_REF' tree using ! the function 'c_parser_array_notation'. During the end of parsing, ! we check the entire function to see if there are any array notation ! specific code (using the function 'contains_array_notation_expr'). ! If this function returns true, then we expand them using either ! 'expand_array_notation_exprs' or 'build_array_notation_expr'. For ! the cases where array notations are inside conditions, they are ! transformed using the function 'fix_conditional_array_notations'. ! The C language-specific routines are located in ! 'c/c-array-notation.c' and the equivalent C++ routines are in the ! file 'cp/cp-array-notation.c'. Common routines such as functions ! to initialize built-in functions are stored in ! 'array-notation-common.c'. * Cilk keywords: ! * '_Cilk_spawn': The '_Cilk_spawn' keyword is parsed and the function it contains is marked as a spawning function. The spawning function is called the spawner. At the end of the ! parsing phase, appropriate built-in functions are added to the ! spawner that are defined in the Cilk runtime. The appropriate ! locations of these functions, and the internal structures are ! detailed in 'cilk_init_builtins' in the file 'cilk-common.c'. ! The pointers to Cilk functions and fields of internal ! structures are described in 'cilk.h'. The built-in functions ! are described in 'cilk-builtins.def'. During gimplification, a new "spawn-helper" function is ! created. The spawned function is replaced with a spawn helper ! function in the spawner. The spawned function-call is moved ! into the spawn helper. The main function that does these ! transformations is 'gimplify_cilk_spawn' in 'c-family/cilk.c'. ! In the spawn-helper, the gimplification function ! 'gimplify_call_expr', inserts a function call ! '__cilkrts_detach'. This function is expanded by ! 'builtin_expand_cilk_detach' located in 'c-family/cilk.c'. ! * '_Cilk_sync': '_Cilk_sync' is parsed like a keyword. During ! gimplification, the function 'gimplify_cilk_sync' in ! 'c-family/cilk.c', will replace this keyword with a set of functions that are stored in the Cilk runtime. One of the internal functions inserted during gimplification, ! '__cilkrts_pop_frame' must be expanded by the compiler and is ! done by 'builtin_expand_cilk_pop_frame' in 'cilk-common.c'. Documentation about Cilk Plus and language specification is provided ! under the "Learn" section in . It is worth mentioning that the current implementation follows ABI 1.1.  --- 6707,6766 ---- 9.2 Cilk Plus Transformation ============================ ! If Cilk Plus generation (flag `-fcilkplus') is enabled, all the Cilk Plus code is transformed into equivalent C and C++ functions. Majority of this transformation occurs toward the end of the parsing and right before the gimplification pass. These are the major components to the Cilk Plus language extension: * Array Notations: During parsing phase, all the array notation ! specific information is stored in `ARRAY_NOTATION_REF' tree using ! the function `c_parser_array_notation'. During the end of ! parsing, we check the entire function to see if there are any ! array notation specific code (using the function ! `contains_array_notation_expr'). If this function returns true, ! then we expand them using either `expand_array_notation_exprs' or ! `build_array_notation_expr'. For the cases where array notations ! are inside conditions, they are transformed using the function ! `fix_conditional_array_notations'. The C language-specific ! routines are located in `c/c-array-notation.c' and the equivalent ! C++ routines are in the file `cp/cp-array-notation.c'. Common ! routines such as functions to initialize built-in functions are ! stored in `array-notation-common.c'. * Cilk keywords: ! * `_Cilk_spawn': The `_Cilk_spawn' keyword is parsed and the function it contains is marked as a spawning function. The spawning function is called the spawner. At the end of the ! parsing phase, appropriate built-in functions are added to ! the spawner that are defined in the Cilk runtime. The ! appropriate locations of these functions, and the internal ! structures are detailed in `cilk_init_builtins' in the file ! `cilk-common.c'. The pointers to Cilk functions and fields ! of internal structures are described in `cilk.h'. The ! built-in functions are described in `cilk-builtins.def'. During gimplification, a new "spawn-helper" function is ! created. The spawned function is replaced with a spawn ! helper function in the spawner. The spawned function-call is ! moved into the spawn helper. The main function that does ! these transformations is `gimplify_cilk_spawn' in ! `c-family/cilk.c'. In the spawn-helper, the gimplification ! function `gimplify_call_expr', inserts a function call ! `__cilkrts_detach'. This function is expanded by ! `builtin_expand_cilk_detach' located in `c-family/cilk.c'. ! * `_Cilk_sync': `_Cilk_sync' is parsed like a keyword. During ! gimplification, the function `gimplify_cilk_sync' in ! `c-family/cilk.c', will replace this keyword with a set of functions that are stored in the Cilk runtime. One of the internal functions inserted during gimplification, ! `__cilkrts_pop_frame' must be expanded by the compiler and is ! done by `builtin_expand_cilk_pop_frame' in `cilk-common.c'. ! Documentation about Cilk Plus and language specification is provided ! under the "Learn" section in `https://www.cilkplus.org'. It is worth mentioning that the current implementation follows ABI 1.1.  *************** intermediate language used by the front *** 6636,6658 **** Usually it is easier to generate GENERIC trees plus extensions and let the language-independent gimplifier do most of the work. ! The main entry point to this pass is 'gimplify_function_tree' located ! in 'gimplify.c'. From here we process the entire function gimplifying each statement in turn. The main workhorse for this pass is ! 'gimplify_expr'. Approximately everything passes through here at least ! once, and it is from here that we invoke the 'lang_hooks.gimplify_expr' callback. The callback should examine the expression in question and return ! 'GS_UNHANDLED' if the expression is not a language specific construct that requires attention. Otherwise it should alter the expression in some way to such that forward progress is made toward producing valid GIMPLE. If the callback is certain that the transformation is complete ! and the expression is valid GIMPLE, it should return 'GS_ALL_DONE'. ! Otherwise it should return 'GS_OK', which will cause the expression to be processed again. If the callback encounters an error during the transformation (because the front end is relying on the gimplification ! process to finish semantic checks), it should return 'GS_ERROR'.  File: gccint.info, Node: Pass manager, Next: Tree SSA passes, Prev: Gimplification pass, Up: Passes --- 6781,6803 ---- Usually it is easier to generate GENERIC trees plus extensions and let the language-independent gimplifier do most of the work. ! The main entry point to this pass is `gimplify_function_tree' located ! in `gimplify.c'. From here we process the entire function gimplifying each statement in turn. The main workhorse for this pass is ! `gimplify_expr'. Approximately everything passes through here at least ! once, and it is from here that we invoke the `lang_hooks.gimplify_expr' callback. The callback should examine the expression in question and return ! `GS_UNHANDLED' if the expression is not a language specific construct that requires attention. Otherwise it should alter the expression in some way to such that forward progress is made toward producing valid GIMPLE. If the callback is certain that the transformation is complete ! and the expression is valid GIMPLE, it should return `GS_ALL_DONE'. ! Otherwise it should return `GS_OK', which will cause the expression to be processed again. If the callback encounters an error during the transformation (because the front end is relying on the gimplification ! process to finish semantic checks), it should return `GS_ERROR'.  File: gccint.info, Node: Pass manager, Next: Tree SSA passes, Prev: Gimplification pass, Up: Passes *************** File: gccint.info, Node: Pass manager, *** 6660,6679 **** 9.4 Pass manager ================ ! The pass manager is located in 'passes.c', 'tree-optimize.c' and ! 'tree-pass.h'. It processes passes as described in 'passes.def'. Its job is to run all of the individual passes in the correct order, and take care of standard bookkeeping that applies to every pass. The theory of operation is that each pass defines a structure that ! represents everything we need to know about that pass--when it should be ! run, how it should be run, what intermediate language form or ! on-the-side data structures it needs. We register the pass to be run in ! some particular order, and the pass manager arranges for everything to ! happen in the correct order. The actuality doesn't completely live up to the theory at present. ! Command-line switches and 'timevar_id_t' enumerations must still be defined elsewhere. The pass manager validates constraints but does not attempt to (re-)generate data structures or lower intermediate language form based on the requirements of the next pass. Nevertheless, what is --- 6805,6824 ---- 9.4 Pass manager ================ ! The pass manager is located in `passes.c', `tree-optimize.c' and ! `tree-pass.h'. It processes passes as described in `passes.def'. Its job is to run all of the individual passes in the correct order, and take care of standard bookkeeping that applies to every pass. The theory of operation is that each pass defines a structure that ! represents everything we need to know about that pass--when it should ! be run, how it should be run, what intermediate language form or ! on-the-side data structures it needs. We register the pass to be run ! in some particular order, and the pass manager arranges for everything ! to happen in the correct order. The actuality doesn't completely live up to the theory at present. ! Command-line switches and `timevar_id_t' enumerations must still be defined elsewhere. The pass manager validates constraints but does not attempt to (re-)generate data structures or lower intermediate language form based on the requirements of the next pass. Nevertheless, what is *************** present is useful, and a far sight bette *** 6683,6691 **** file (for GCC debugging purposes). Passes with a name starting with a star do not dump anything. Sometimes passes are supposed to share a dump file / option name. To still give these unique names, you can use ! a prefix that is delimited by a space from the part that is used for the ! dump file / option name. E.g. When the pass name is "ud dce", the name ! used for dump file/options is "dce". TODO: describe the global variables set up by the pass manager, and a brief description of how a new pass should use it. I need to look at --- 6828,6836 ---- file (for GCC debugging purposes). Passes with a name starting with a star do not dump anything. Sometimes passes are supposed to share a dump file / option name. To still give these unique names, you can use ! a prefix that is delimited by a space from the part that is used for ! the dump file / option name. E.g. When the pass name is "ud dce", the ! name used for dump file/options is "dce". TODO: describe the global variables set up by the pass manager, and a brief description of how a new pass should use it. I need to look at *************** run after gimplification and what source *** 6704,6866 **** This pass is an extremely simple sweep across the gimple code in which we identify obviously dead code and remove it. Here we do ! things like simplify 'if' statements with constant conditions, remove exception handling constructs surrounding code that obviously cannot throw, remove lexical bindings that contain no variables, and other assorted simplistic cleanups. The idea is to get rid of the obvious stuff quickly rather than wait until later when it's more work to get rid of it. This pass is located in ! 'tree-cfg.c' and described by 'pass_remove_useless_stmts'. * OpenMP lowering ! If OpenMP generation ('-fopenmp') is enabled, this pass lowers OpenMP constructs into GIMPLE. Lowering of OpenMP constructs involves creating replacement expressions for local variables that have been mapped using data sharing clauses, exposing the control flow of most synchronization directives and adding region markers to facilitate the creation of ! the control flow graph. The pass is located in 'omp-low.c' and is ! described by 'pass_lower_omp'. * OpenMP expansion ! If OpenMP generation ('-fopenmp') is enabled, this pass expands parallel regions into their own functions to be invoked by the ! thread library. The pass is located in 'omp-low.c' and is ! described by 'pass_expand_omp'. * Lower control flow ! This pass flattens 'if' statements ('COND_EXPR') and moves lexical ! bindings ('BIND_EXPR') out of line. After this pass, all 'if' ! statements will have exactly two 'goto' statements in its 'then' ! and 'else' arms. Lexical binding information for each statement ! will be found in 'TREE_BLOCK' rather than being inferred from its ! position under a 'BIND_EXPR'. This pass is found in 'gimple-low.c' ! and is described by 'pass_lower_cf'. * Lower exception handling control flow This pass decomposes high-level exception handling constructs ! ('TRY_FINALLY_EXPR' and 'TRY_CATCH_EXPR') into a form that explicitly represents the control flow involved. After this pass, ! 'lookup_stmt_eh_region' will return a non-negative number for any statement that may have EH control flow semantics; examine ! 'tree_can_throw_internal' or 'tree_can_throw_external' for exact semantics. Exact control flow may be extracted from ! 'foreach_reachable_handler'. The EH region nesting tree is defined ! in 'except.h' and built in 'except.c'. The lowering pass itself is ! in 'tree-eh.c' and is described by 'pass_lower_eh'. * Build the control flow graph This pass decomposes a function into basic blocks and creates all ! of the edges that connect them. It is located in 'tree-cfg.c' and ! is described by 'pass_build_cfg'. * Find all referenced variables This pass walks the entire function and collects an array of all ! variables referenced in the function, 'referenced_vars'. The index ! at which a variable is found in the array is used as a UID for the ! variable within this function. This data is needed by the SSA ! rewriting routines. The pass is located in 'tree-dfa.c' and is ! described by 'pass_referenced_vars'. * Enter static single assignment form This pass rewrites the function such that it is in SSA form. After ! this pass, all 'is_gimple_reg' variables will be referenced by ! 'SSA_NAME', and all occurrences of other variables will be ! annotated with 'VDEFS' and 'VUSES'; PHI nodes will have been inserted as necessary for each basic block. This pass is located ! in 'tree-ssa.c' and is described by 'pass_build_ssa'. * Warn for uninitialized variables ! This pass scans the function for uses of 'SSA_NAME's that are fed by default definition. For non-parameter variables, such uses are uninitialized. The pass is run twice, before and after optimization (if turned on). In the first pass we only warn for uses that are positively uninitialized; in the second pass we warn for uses that are possibly uninitialized. The pass is located in ! 'tree-ssa.c' and is defined by 'pass_early_warn_uninitialized' and ! 'pass_late_warn_uninitialized'. * Dead code elimination This pass scans the function for statements without side effects whose result is unused. It does not do memory life analysis, so ! any value that is stored in memory is considered used. The pass is ! run multiple times throughout the optimization process. It is ! located in 'tree-ssa-dce.c' and is described by 'pass_dce'. * Dominator optimizations This pass performs trivial dominator-based copy and constant propagation, expression simplification, and jump threading. It is run multiple times throughout the optimization process. It is ! located in 'tree-ssa-dom.c' and is described by 'pass_dominator'. * Forward propagation of single-use variables This pass attempts to remove redundant computation by substituting variables that are used once into the expression that uses them and seeing if the result can be simplified. It is located in ! 'tree-ssa-forwprop.c' and is described by 'pass_forwprop'. * Copy Renaming This pass attempts to change the name of compiler temporaries involved in copy operations such that SSA->normal can coalesce the ! copy away. When compiler temporaries are copies of user variables, ! it also renames the compiler temporary to the user variable ! resulting in better use of user symbols. It is located in ! 'tree-ssa-copyrename.c' and is described by 'pass_copyrename'. * PHI node optimizations This pass recognizes forms of PHI inputs that can be represented as conditional expressions and rewrites them into straight line code. ! It is located in 'tree-ssa-phiopt.c' and is described by ! 'pass_phiopt'. * May-alias optimization This pass performs a flow sensitive SSA-based points-to analysis. The resulting may-alias, must-alias, and escape analysis ! information is used to promote variables from in-memory addressable ! objects to non-aliased variables that can be renamed into SSA form. ! We also update the 'VDEF'/'VUSE' memory tags for non-renameable ! aggregates so that we get fewer false kills. The pass is located ! in 'tree-ssa-alias.c' and is described by 'pass_may_alias'. Interprocedural points-to information is located in ! 'tree-ssa-structalias.c' and described by 'pass_ipa_pta'. * Profiling This pass instruments the function in order to collect runtime ! block and value profiling data. Such data may be fed back into the ! compiler on a subsequent run so as to allow optimization based on ! expected execution frequencies. The pass is located in ! 'tree-profile.c' and is described by 'pass_ipa_tree_profile'. * Static profile estimation This pass implements series of heuristics to guess propababilities of branches. The resulting predictions are turned into edge profile by propagating branches across the control flow graphs. ! The pass is located in 'tree-profile.c' and is described by ! 'pass_profile'. * Lower complex arithmetic This pass rewrites complex arithmetic operations into their component scalar arithmetic operations. The pass is located in ! 'tree-complex.c' and is described by 'pass_lower_complex'. * Scalar replacement of aggregates --- 6849,7012 ---- This pass is an extremely simple sweep across the gimple code in which we identify obviously dead code and remove it. Here we do ! things like simplify `if' statements with constant conditions, remove exception handling constructs surrounding code that obviously cannot throw, remove lexical bindings that contain no variables, and other assorted simplistic cleanups. The idea is to get rid of the obvious stuff quickly rather than wait until later when it's more work to get rid of it. This pass is located in ! `tree-cfg.c' and described by `pass_remove_useless_stmts'. * OpenMP lowering ! If OpenMP generation (`-fopenmp') is enabled, this pass lowers OpenMP constructs into GIMPLE. Lowering of OpenMP constructs involves creating replacement expressions for local variables that have been mapped using data sharing clauses, exposing the control flow of most synchronization directives and adding region markers to facilitate the creation of ! the control flow graph. The pass is located in `omp-low.c' and is ! described by `pass_lower_omp'. * OpenMP expansion ! If OpenMP generation (`-fopenmp') is enabled, this pass expands parallel regions into their own functions to be invoked by the ! thread library. The pass is located in `omp-low.c' and is ! described by `pass_expand_omp'. * Lower control flow ! This pass flattens `if' statements (`COND_EXPR') and moves lexical ! bindings (`BIND_EXPR') out of line. After this pass, all `if' ! statements will have exactly two `goto' statements in its `then' ! and `else' arms. Lexical binding information for each statement ! will be found in `TREE_BLOCK' rather than being inferred from its ! position under a `BIND_EXPR'. This pass is found in ! `gimple-low.c' and is described by `pass_lower_cf'. * Lower exception handling control flow This pass decomposes high-level exception handling constructs ! (`TRY_FINALLY_EXPR' and `TRY_CATCH_EXPR') into a form that explicitly represents the control flow involved. After this pass, ! `lookup_stmt_eh_region' will return a non-negative number for any statement that may have EH control flow semantics; examine ! `tree_can_throw_internal' or `tree_can_throw_external' for exact semantics. Exact control flow may be extracted from ! `foreach_reachable_handler'. The EH region nesting tree is defined ! in `except.h' and built in `except.c'. The lowering pass itself ! is in `tree-eh.c' and is described by `pass_lower_eh'. * Build the control flow graph This pass decomposes a function into basic blocks and creates all ! of the edges that connect them. It is located in `tree-cfg.c' and ! is described by `pass_build_cfg'. * Find all referenced variables This pass walks the entire function and collects an array of all ! variables referenced in the function, `referenced_vars'. The ! index at which a variable is found in the array is used as a UID ! for the variable within this function. This data is needed by the ! SSA rewriting routines. The pass is located in `tree-dfa.c' and ! is described by `pass_referenced_vars'. * Enter static single assignment form This pass rewrites the function such that it is in SSA form. After ! this pass, all `is_gimple_reg' variables will be referenced by ! `SSA_NAME', and all occurrences of other variables will be ! annotated with `VDEFS' and `VUSES'; PHI nodes will have been inserted as necessary for each basic block. This pass is located ! in `tree-ssa.c' and is described by `pass_build_ssa'. * Warn for uninitialized variables ! This pass scans the function for uses of `SSA_NAME's that are fed by default definition. For non-parameter variables, such uses are uninitialized. The pass is run twice, before and after optimization (if turned on). In the first pass we only warn for uses that are positively uninitialized; in the second pass we warn for uses that are possibly uninitialized. The pass is located in ! `tree-ssa.c' and is defined by `pass_early_warn_uninitialized' and ! `pass_late_warn_uninitialized'. * Dead code elimination This pass scans the function for statements without side effects whose result is unused. It does not do memory life analysis, so ! any value that is stored in memory is considered used. The pass ! is run multiple times throughout the optimization process. It is ! located in `tree-ssa-dce.c' and is described by `pass_dce'. * Dominator optimizations This pass performs trivial dominator-based copy and constant propagation, expression simplification, and jump threading. It is run multiple times throughout the optimization process. It is ! located in `tree-ssa-dom.c' and is described by `pass_dominator'. * Forward propagation of single-use variables This pass attempts to remove redundant computation by substituting variables that are used once into the expression that uses them and seeing if the result can be simplified. It is located in ! `tree-ssa-forwprop.c' and is described by `pass_forwprop'. * Copy Renaming This pass attempts to change the name of compiler temporaries involved in copy operations such that SSA->normal can coalesce the ! copy away. When compiler temporaries are copies of user ! variables, it also renames the compiler temporary to the user ! variable resulting in better use of user symbols. It is located ! in `tree-ssa-copyrename.c' and is described by `pass_copyrename'. * PHI node optimizations This pass recognizes forms of PHI inputs that can be represented as conditional expressions and rewrites them into straight line code. ! It is located in `tree-ssa-phiopt.c' and is described by ! `pass_phiopt'. * May-alias optimization This pass performs a flow sensitive SSA-based points-to analysis. The resulting may-alias, must-alias, and escape analysis ! information is used to promote variables from in-memory ! addressable objects to non-aliased variables that can be renamed ! into SSA form. We also update the `VDEF'/`VUSE' memory tags for ! non-renameable aggregates so that we get fewer false kills. The ! pass is located in `tree-ssa-alias.c' and is described by ! `pass_may_alias'. Interprocedural points-to information is located in ! `tree-ssa-structalias.c' and described by `pass_ipa_pta'. * Profiling This pass instruments the function in order to collect runtime ! block and value profiling data. Such data may be fed back into ! the compiler on a subsequent run so as to allow optimization based ! on expected execution frequencies. The pass is located in ! `tree-profile.c' and is described by `pass_ipa_tree_profile'. * Static profile estimation This pass implements series of heuristics to guess propababilities of branches. The resulting predictions are turned into edge profile by propagating branches across the control flow graphs. ! The pass is located in `tree-profile.c' and is described by ! `pass_profile'. * Lower complex arithmetic This pass rewrites complex arithmetic operations into their component scalar arithmetic operations. The pass is located in ! `tree-complex.c' and is described by `pass_lower_complex'. * Scalar replacement of aggregates *************** run after gimplification and what source *** 6868,6976 **** into a set of scalar variables. The resulting scalar variables are rewritten into SSA form, which allows subsequent optimization passes to do a significantly better job with them. The pass is ! located in 'tree-sra.c' and is described by 'pass_sra'. * Dead store elimination This pass eliminates stores to memory that are subsequently overwritten by another store, without any intervening loads. The ! pass is located in 'tree-ssa-dse.c' and is described by 'pass_dse'. * Tail recursion elimination This pass transforms tail recursion into a loop. It is located in ! 'tree-tailcall.c' and is described by 'pass_tail_recursion'. * Forward store motion ! This pass sinks stores and assignments down the flowgraph closer to ! their use point. The pass is located in 'tree-ssa-sink.c' and is ! described by 'pass_sink_code'. * Partial redundancy elimination This pass eliminates partially redundant computations, as well as ! performing load motion. The pass is located in 'tree-ssa-pre.c' ! and is described by 'pass_pre'. Just before partial redundancy elimination, if ! '-funsafe-math-optimizations' is on, GCC tries to convert divisions ! to multiplications by the reciprocal. The pass is located in ! 'tree-ssa-math-opts.c' and is described by 'pass_cse_reciprocal'. * Full redundancy elimination This is a simpler form of PRE that only eliminates redundancies ! that occur on all paths. It is located in 'tree-ssa-pre.c' and ! described by 'pass_fre'. * Loop optimization ! The main driver of the pass is placed in 'tree-ssa-loop.c' and ! described by 'pass_loop'. The optimizations performed by this pass are: Loop invariant motion. This pass moves only invariants that would be hard to handle on RTL level (function calls, operations that ! expand to nontrivial sequences of insns). With '-funswitch-loops' it also moves operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion. The pass ! is implemented in 'tree-ssa-loop-im.c'. Canonical induction variable creation. This pass creates a simple counter for number of iterations of the loop and replaces the exit ! condition of the loop using it, in case when a complicated analysis ! is necessary to determine the number of iterations. Later ! optimizations then may determine the number easily. The pass is ! implemented in 'tree-ssa-loop-ivcanon.c'. Induction variable optimizations. This pass performs standard induction variable optimizations, including strength reduction, ! induction variable merging and induction variable elimination. The ! pass is implemented in 'tree-ssa-loop-ivopts.c'. Loop unswitching. This pass moves the conditional jumps that are invariant out of the loops. To achieve this, a duplicate of the loop is created for each possible outcome of conditional jump(s). ! The pass is implemented in 'tree-ssa-loop-unswitch.c'. The optimizations also use various utility functions contained in ! 'tree-ssa-loop-manip.c', 'cfgloop.c', 'cfgloopanal.c' and ! 'cfgloopmanip.c'. Vectorization. This pass transforms loops to operate on vector types instead of scalar types. Data parallelism across loop iterations is exploited to group data elements from consecutive iterations into a vector and operate on them in parallel. Depending on available target support the loop is conceptually ! unrolled by a factor 'VF' (vectorization factor), which is the ! number of elements operated upon in parallel in each iteration, and ! the 'VF' copies of each scalar operation are fused to form a vector ! operation. Additional loop transformations such as peeling and ! versioning may take place to align the number of iterations, and to ! align the memory accesses in the loop. The pass is implemented in ! 'tree-vectorizer.c' (the main driver), 'tree-vect-loop.c' and ! 'tree-vect-loop-manip.c' (loop specific parts and general loop ! utilities), 'tree-vect-slp' (loop-aware SLP functionality), ! 'tree-vect-stmts.c' and 'tree-vect-data-refs.c'. Analysis of data ! references is in 'tree-data-ref.c'. SLP Vectorization. This pass performs vectorization of ! straight-line code. The pass is implemented in 'tree-vectorizer.c' ! (the main driver), 'tree-vect-slp.c', 'tree-vect-stmts.c' and ! 'tree-vect-data-refs.c'. Autoparallelization. This pass splits the loop iteration space to run into several threads. The pass is implemented in ! 'tree-parloops.c'. Graphite is a loop transformation framework based on the polyhedral model. Graphite stands for Gimple Represented as Polyhedra. The internals of this infrastructure are documented in ! . The passes working on this ! representation are implemented in the various 'graphite-*' files. * Tree level if-conversion for vectorizer --- 7014,7123 ---- into a set of scalar variables. The resulting scalar variables are rewritten into SSA form, which allows subsequent optimization passes to do a significantly better job with them. The pass is ! located in `tree-sra.c' and is described by `pass_sra'. * Dead store elimination This pass eliminates stores to memory that are subsequently overwritten by another store, without any intervening loads. The ! pass is located in `tree-ssa-dse.c' and is described by `pass_dse'. * Tail recursion elimination This pass transforms tail recursion into a loop. It is located in ! `tree-tailcall.c' and is described by `pass_tail_recursion'. * Forward store motion ! This pass sinks stores and assignments down the flowgraph closer ! to their use point. The pass is located in `tree-ssa-sink.c' and ! is described by `pass_sink_code'. * Partial redundancy elimination This pass eliminates partially redundant computations, as well as ! performing load motion. The pass is located in `tree-ssa-pre.c' ! and is described by `pass_pre'. Just before partial redundancy elimination, if ! `-funsafe-math-optimizations' is on, GCC tries to convert ! divisions to multiplications by the reciprocal. The pass is ! located in `tree-ssa-math-opts.c' and is described by ! `pass_cse_reciprocal'. * Full redundancy elimination This is a simpler form of PRE that only eliminates redundancies ! that occur on all paths. It is located in `tree-ssa-pre.c' and ! described by `pass_fre'. * Loop optimization ! The main driver of the pass is placed in `tree-ssa-loop.c' and ! described by `pass_loop'. The optimizations performed by this pass are: Loop invariant motion. This pass moves only invariants that would be hard to handle on RTL level (function calls, operations that ! expand to nontrivial sequences of insns). With `-funswitch-loops' it also moves operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion. The pass ! is implemented in `tree-ssa-loop-im.c'. Canonical induction variable creation. This pass creates a simple counter for number of iterations of the loop and replaces the exit ! condition of the loop using it, in case when a complicated ! analysis is necessary to determine the number of iterations. ! Later optimizations then may determine the number easily. The ! pass is implemented in `tree-ssa-loop-ivcanon.c'. Induction variable optimizations. This pass performs standard induction variable optimizations, including strength reduction, ! induction variable merging and induction variable elimination. ! The pass is implemented in `tree-ssa-loop-ivopts.c'. Loop unswitching. This pass moves the conditional jumps that are invariant out of the loops. To achieve this, a duplicate of the loop is created for each possible outcome of conditional jump(s). ! The pass is implemented in `tree-ssa-loop-unswitch.c'. The optimizations also use various utility functions contained in ! `tree-ssa-loop-manip.c', `cfgloop.c', `cfgloopanal.c' and ! `cfgloopmanip.c'. Vectorization. This pass transforms loops to operate on vector types instead of scalar types. Data parallelism across loop iterations is exploited to group data elements from consecutive iterations into a vector and operate on them in parallel. Depending on available target support the loop is conceptually ! unrolled by a factor `VF' (vectorization factor), which is the ! number of elements operated upon in parallel in each iteration, ! and the `VF' copies of each scalar operation are fused to form a ! vector operation. Additional loop transformations such as peeling ! and versioning may take place to align the number of iterations, ! and to align the memory accesses in the loop. The pass is ! implemented in `tree-vectorizer.c' (the main driver), ! `tree-vect-loop.c' and `tree-vect-loop-manip.c' (loop specific ! parts and general loop utilities), `tree-vect-slp' (loop-aware SLP ! functionality), `tree-vect-stmts.c' and `tree-vect-data-refs.c'. ! Analysis of data references is in `tree-data-ref.c'. SLP Vectorization. This pass performs vectorization of ! straight-line code. The pass is implemented in `tree-vectorizer.c' ! (the main driver), `tree-vect-slp.c', `tree-vect-stmts.c' and ! `tree-vect-data-refs.c'. Autoparallelization. This pass splits the loop iteration space to run into several threads. The pass is implemented in ! `tree-parloops.c'. Graphite is a loop transformation framework based on the polyhedral model. Graphite stands for Gimple Represented as Polyhedra. The internals of this infrastructure are documented in ! `http://gcc.gnu.org/wiki/Graphite'. The passes working on this ! representation are implemented in the various `graphite-*' files. * Tree level if-conversion for vectorizer *************** run after gimplification and what source *** 6979,7007 **** basic blocks in one big block. The idea is to present loop in such form so that vectorizer can have one to one mapping between statements and available vector operations. This pass is located ! in 'tree-if-conv.c' and is described by 'pass_if_conversion'. * Conditional constant propagation This pass relaxes a lattice of values in order to identify those that must be constant even in the presence of conditional branches. ! The pass is located in 'tree-ssa-ccp.c' and is described by ! 'pass_ccp'. A related pass that works on memory loads and stores, and not just ! register values, is located in 'tree-ssa-ccp.c' and described by ! 'pass_store_ccp'. * Conditional copy propagation This is similar to constant propagation but the lattice of values is the "copy-of" relation. It eliminates redundant copies from the ! code. The pass is located in 'tree-ssa-copy.c' and described by ! 'pass_copy_prop'. A related pass that works on memory copies, and not just register ! copies, is located in 'tree-ssa-copy.c' and described by ! 'pass_store_copy_prop'. * Value range propagation --- 7126,7154 ---- basic blocks in one big block. The idea is to present loop in such form so that vectorizer can have one to one mapping between statements and available vector operations. This pass is located ! in `tree-if-conv.c' and is described by `pass_if_conversion'. * Conditional constant propagation This pass relaxes a lattice of values in order to identify those that must be constant even in the presence of conditional branches. ! The pass is located in `tree-ssa-ccp.c' and is described by ! `pass_ccp'. A related pass that works on memory loads and stores, and not just ! register values, is located in `tree-ssa-ccp.c' and described by ! `pass_store_ccp'. * Conditional copy propagation This is similar to constant propagation but the lattice of values is the "copy-of" relation. It eliminates redundant copies from the ! code. The pass is located in `tree-ssa-copy.c' and described by ! `pass_copy_prop'. A related pass that works on memory copies, and not just register ! copies, is located in `tree-ssa-copy.c' and described by ! `pass_store_copy_prop'. * Value range propagation *************** run after gimplification and what source *** 7012,7038 **** Range Propagation, J. R. C. Patterson, PLDI '95). In contrast to Patterson's algorithm, this implementation does not propagate branch probabilities nor it uses more than a single range per SSA ! name. This means that the current implementation cannot be used for branch prediction (though adapting it would not be difficult). ! The pass is located in 'tree-vrp.c' and is described by 'pass_vrp'. * Folding built-in functions This pass simplifies built-in functions, as applicable, with ! constant arguments or with inferable string lengths. It is located ! in 'tree-ssa-ccp.c' and is described by 'pass_fold_builtins'. * Split critical edges This pass identifies critical edges and inserts empty basic blocks such that the edge is no longer critical. The pass is located in ! 'tree-cfg.c' and is described by 'pass_split_crit_edges'. * Control dependence dead code elimination This pass is a stronger form of dead code elimination that can ! eliminate unnecessary control flow statements. It is located in ! 'tree-ssa-dce.c' and is described by 'pass_cd_dce'. * Tail call elimination --- 7159,7186 ---- Range Propagation, J. R. C. Patterson, PLDI '95). In contrast to Patterson's algorithm, this implementation does not propagate branch probabilities nor it uses more than a single range per SSA ! name. This means that the current implementation cannot be used for branch prediction (though adapting it would not be difficult). ! The pass is located in `tree-vrp.c' and is described by `pass_vrp'. * Folding built-in functions This pass simplifies built-in functions, as applicable, with ! constant arguments or with inferable string lengths. It is ! located in `tree-ssa-ccp.c' and is described by ! `pass_fold_builtins'. * Split critical edges This pass identifies critical edges and inserts empty basic blocks such that the edge is no longer critical. The pass is located in ! `tree-cfg.c' and is described by `pass_split_crit_edges'. * Control dependence dead code elimination This pass is a stronger form of dead code elimination that can ! eliminate unnecessary control flow statements. It is located in ! `tree-ssa-dce.c' and is described by `pass_cd_dce'. * Tail call elimination *************** run after gimplification and what source *** 7040,7049 **** jumps. No code transformation is actually applied here, but the data and control flow problem is solved. The code transformation requires target support, and so is delayed until RTL. In the ! meantime 'CALL_EXPR_TAILCALL' is set indicating the possibility. ! The pass is located in 'tree-tailcall.c' and is described by ! 'pass_tail_calls'. The RTL transformation is handled by ! 'fixup_tail_calls' in 'calls.c'. * Warn for function return without value --- 7188,7197 ---- jumps. No code transformation is actually applied here, but the data and control flow problem is solved. The code transformation requires target support, and so is delayed until RTL. In the ! meantime `CALL_EXPR_TAILCALL' is set indicating the possibility. ! The pass is located in `tree-tailcall.c' and is described by ! `pass_tail_calls'. The RTL transformation is handled by ! `fixup_tail_calls' in `calls.c'. * Warn for function return without value *************** run after gimplification and what source *** 7051,7103 **** not specify a value and issues a warning. Such a statement may have been injected by falling off the end of the function. This pass is run last so that we have as much time as possible to prove ! that the statement is not reachable. It is located in 'tree-cfg.c' ! and is described by 'pass_warn_function_return'. * Leave static single assignment form This pass rewrites the function such that it is in normal form. At the same time, we eliminate as many single-use temporaries as possible, so the intermediate language is no longer GIMPLE, but ! GENERIC. The pass is located in 'tree-outof-ssa.c' and is ! described by 'pass_del_ssa'. * Merge PHI nodes that feed into one another This is part of the CFG cleanup passes. It attempts to join PHI ! nodes from a forwarder CFG block into another block with PHI nodes. ! The pass is located in 'tree-cfgcleanup.c' and is described by ! 'pass_merge_phi'. * Return value optimization If a function always returns the same local variable, and that local variable is an aggregate type, then the variable is replaced with the return value for the function (i.e., the function's ! DECL_RESULT). This is equivalent to the C++ named return value optimization applied to GIMPLE. The pass is located in ! 'tree-nrv.c' and is described by 'pass_nrv'. * Return slot optimization ! If a function returns a memory object and is called as 'var = foo()', this pass tries to change the call so that the address of ! 'var' is sent to the caller to avoid an extra memory copy. This ! pass is located in 'tree-nrv.c' and is described by ! 'pass_return_slot'. ! * Optimize calls to '__builtin_object_size' This is a propagation pass similar to CCP that tries to remove ! calls to '__builtin_object_size' when the size of the object can be computed at compile-time. This pass is located in ! 'tree-object-size.c' and is described by 'pass_object_sizes'. * Loop invariant motion This pass removes expensive loop-invariant computations out of ! loops. The pass is located in 'tree-ssa-loop.c' and described by ! 'pass_lim'. * Loop nest optimizations --- 7199,7251 ---- not specify a value and issues a warning. Such a statement may have been injected by falling off the end of the function. This pass is run last so that we have as much time as possible to prove ! that the statement is not reachable. It is located in ! `tree-cfg.c' and is described by `pass_warn_function_return'. * Leave static single assignment form This pass rewrites the function such that it is in normal form. At the same time, we eliminate as many single-use temporaries as possible, so the intermediate language is no longer GIMPLE, but ! GENERIC. The pass is located in `tree-outof-ssa.c' and is ! described by `pass_del_ssa'. * Merge PHI nodes that feed into one another This is part of the CFG cleanup passes. It attempts to join PHI ! nodes from a forwarder CFG block into another block with PHI ! nodes. The pass is located in `tree-cfgcleanup.c' and is ! described by `pass_merge_phi'. * Return value optimization If a function always returns the same local variable, and that local variable is an aggregate type, then the variable is replaced with the return value for the function (i.e., the function's ! DECL_RESULT). This is equivalent to the C++ named return value optimization applied to GIMPLE. The pass is located in ! `tree-nrv.c' and is described by `pass_nrv'. * Return slot optimization ! If a function returns a memory object and is called as `var = foo()', this pass tries to change the call so that the address of ! `var' is sent to the caller to avoid an extra memory copy. This ! pass is located in `tree-nrv.c' and is described by ! `pass_return_slot'. ! * Optimize calls to `__builtin_object_size' This is a propagation pass similar to CCP that tries to remove ! calls to `__builtin_object_size' when the size of the object can be computed at compile-time. This pass is located in ! `tree-object-size.c' and is described by `pass_object_sizes'. * Loop invariant motion This pass removes expensive loop-invariant computations out of ! loops. The pass is located in `tree-ssa-loop.c' and described by ! `pass_lim'. * Loop nest optimizations *************** run after gimplification and what source *** 7106,7160 **** they are all geared to the optimization of data locality in array traversals and the removal of dependencies that hamper optimizations such as loop parallelization and vectorization. The ! pass is located in 'tree-loop-linear.c' and described by ! 'pass_linear_transform'. * Removal of empty loops This pass removes loops with no code in them. The pass is located ! in 'tree-ssa-loop-ivcanon.c' and described by 'pass_empty_loop'. * Unrolling of small loops This pass completely unrolls loops with few iterations. The pass ! is located in 'tree-ssa-loop-ivcanon.c' and described by ! 'pass_complete_unroll'. * Predictive commoning This pass makes the code reuse the computations from the previous ! iterations of the loops, especially loads and stores to memory. It ! does so by storing the values of these computations to a bank of ! temporary variables that are rotated at the end of loop. To avoid ! the need for this rotation, the loop is then unrolled and the ! copies of the loop body are rewritten to use the appropriate version of the temporary variable. This pass is located in ! 'tree-predcom.c' and described by 'pass_predcom'. * Array prefetching This pass issues prefetch instructions for array references inside ! loops. The pass is located in 'tree-ssa-loop-prefetch.c' and ! described by 'pass_loop_prefetch'. * Reassociation This pass rewrites arithmetic expressions to enable optimizations that operate on them, like redundancy elimination and ! vectorization. The pass is located in 'tree-ssa-reassoc.c' and ! described by 'pass_reassoc'. ! * Optimization of 'stdarg' functions This pass tries to avoid the saving of register arguments into the ! stack on entry to 'stdarg' functions. If the function doesn't use ! any 'va_start' macros, no registers need to be saved. If ! 'va_start' macros are used, the 'va_list' variables don't escape the function, it is only necessary to save registers that will be ! used in 'va_arg' macros. For instance, if 'va_arg' is only used ! with integral types in the function, floating point registers don't ! need to be saved. This pass is located in 'tree-stdarg.c' and ! described by 'pass_stdarg'.  File: gccint.info, Node: RTL passes, Next: Optimization info, Prev: Tree SSA passes, Up: Passes --- 7254,7309 ---- they are all geared to the optimization of data locality in array traversals and the removal of dependencies that hamper optimizations such as loop parallelization and vectorization. The ! pass is located in `tree-loop-linear.c' and described by ! `pass_linear_transform'. * Removal of empty loops This pass removes loops with no code in them. The pass is located ! in `tree-ssa-loop-ivcanon.c' and described by `pass_empty_loop'. * Unrolling of small loops This pass completely unrolls loops with few iterations. The pass ! is located in `tree-ssa-loop-ivcanon.c' and described by ! `pass_complete_unroll'. * Predictive commoning This pass makes the code reuse the computations from the previous ! iterations of the loops, especially loads and stores to memory. ! It does so by storing the values of these computations to a bank ! of temporary variables that are rotated at the end of loop. To ! avoid the need for this rotation, the loop is then unrolled and ! the copies of the loop body are rewritten to use the appropriate version of the temporary variable. This pass is located in ! `tree-predcom.c' and described by `pass_predcom'. * Array prefetching This pass issues prefetch instructions for array references inside ! loops. The pass is located in `tree-ssa-loop-prefetch.c' and ! described by `pass_loop_prefetch'. * Reassociation This pass rewrites arithmetic expressions to enable optimizations that operate on them, like redundancy elimination and ! vectorization. The pass is located in `tree-ssa-reassoc.c' and ! described by `pass_reassoc'. ! * Optimization of `stdarg' functions This pass tries to avoid the saving of register arguments into the ! stack on entry to `stdarg' functions. If the function doesn't use ! any `va_start' macros, no registers need to be saved. If ! `va_start' macros are used, the `va_list' variables don't escape the function, it is only necessary to save registers that will be ! used in `va_arg' macros. For instance, if `va_arg' is only used ! with integral types in the function, floating point registers ! don't need to be saved. This pass is located in `tree-stdarg.c' ! and described by `pass_stdarg'. !  File: gccint.info, Node: RTL passes, Next: Optimization info, Prev: Tree SSA passes, Up: Passes *************** passes that are run after the Tree optim *** 7167,7200 **** * RTL generation ! The source files for RTL generation include 'stmt.c', 'calls.c', ! 'expr.c', 'explow.c', 'expmed.c', 'function.c', 'optabs.c' and ! 'emit-rtl.c'. Also, the file 'insn-emit.c', generated from the ! machine description by the program 'genemit', is used in this pass. ! The header file 'expr.h' is used for communication within this ! pass. ! The header files 'insn-flags.h' and 'insn-codes.h', generated from ! the machine description by the programs 'genflags' and 'gencodes', ! tell this pass which standard names are available for use and which ! patterns correspond to them. * Generation of exception landing pads This pass generates the glue that handles communication between the exception handling library routines and the exception handlers ! within the function. Entry points in the function that are invoked ! by the exception handling library are called "landing pads". The ! code for this pass is located in 'except.c'. * Control flow graph cleanup ! This pass removes unreachable code, simplifies jumps to next, jumps ! to jump, jumps across jumps, etc. The pass is run multiple times. ! For historical reasons, it is occasionally referred to as the "jump ! optimization pass". The bulk of the code for this pass is in ! 'cfgcleanup.c', and there are support routines in 'cfgrtl.c' and ! 'jump.c'. * Forward propagation of single-def values --- 7316,7349 ---- * RTL generation ! The source files for RTL generation include `stmt.c', `calls.c', ! `expr.c', `explow.c', `expmed.c', `function.c', `optabs.c' and ! `emit-rtl.c'. Also, the file `insn-emit.c', generated from the ! machine description by the program `genemit', is used in this ! pass. The header file `expr.h' is used for communication within ! this pass. ! The header files `insn-flags.h' and `insn-codes.h', generated from ! the machine description by the programs `genflags' and `gencodes', ! tell this pass which standard names are available for use and ! which patterns correspond to them. * Generation of exception landing pads This pass generates the glue that handles communication between the exception handling library routines and the exception handlers ! within the function. Entry points in the function that are ! invoked by the exception handling library are called "landing ! pads". The code for this pass is located in `except.c'. * Control flow graph cleanup ! This pass removes unreachable code, simplifies jumps to next, ! jumps to jump, jumps across jumps, etc. The pass is run multiple ! times. For historical reasons, it is occasionally referred to as ! the "jump optimization pass". The bulk of the code for this pass ! is in `cfgcleanup.c', and there are support routines in `cfgrtl.c' ! and `jump.c'. * Forward propagation of single-def values *************** passes that are run after the Tree optim *** 7203,7251 **** result can be simplified. It performs copy propagation and addressing mode selection. The pass is run twice, with values being propagated into loops only on the second run. The code is ! located in 'fwprop.c'. * Common subexpression elimination This pass removes redundant computation within basic blocks, and optimizes addressing modes based on cost. The pass is run twice. ! The code for this pass is located in 'cse.c'. * Global common subexpression elimination ! This pass performs two different types of GCSE depending on whether ! you are optimizing for size or not (LCM based GCSE tends to ! increase code size for a gain in speed, while Morel-Renvoise based ! GCSE does not). When optimizing for size, GCSE is done using ! Morel-Renvoise Partial Redundancy Elimination, with the exception ! that it does not try to move invariants out of loops--that is left ! to the loop optimization pass. If MR PRE GCSE is done, code ! hoisting (aka unification) is also done, as well as load motion. ! If you are optimizing for speed, LCM (lazy code motion) based GCSE ! is done. LCM is based on the work of Knoop, Ruthing, and Steffen. ! LCM based GCSE also does loop invariant code motion. We also ! perform load and store motion when optimizing for speed. ! Regardless of which type of GCSE is used, the GCSE pass also ! performs global constant and copy propagation. The source file for ! this pass is 'gcse.c', and the LCM routines are in 'lcm.c'. * Loop optimization This pass performs several loop related optimizations. The source ! files 'cfgloopanal.c' and 'cfgloopmanip.c' contain generic loop ! analysis and manipulation code. Initialization and finalization of ! loop structures is handled by 'loop-init.c'. A loop invariant ! motion pass is implemented in 'loop-invariant.c'. Basic block ! level optimizations--unrolling, and peeling loops-- are implemented ! in 'loop-unroll.c'. Replacing of the exit condition of loops by ! special machine-dependent instructions is handled by ! 'loop-doloop.c'. * Jump bypassing This pass is an aggressive form of GCSE that transforms the control flow graph of a function by propagating constants into conditional ! branch instructions. The source file for this pass is 'gcse.c'. * If conversion --- 7352,7401 ---- result can be simplified. It performs copy propagation and addressing mode selection. The pass is run twice, with values being propagated into loops only on the second run. The code is ! located in `fwprop.c'. * Common subexpression elimination This pass removes redundant computation within basic blocks, and optimizes addressing modes based on cost. The pass is run twice. ! The code for this pass is located in `cse.c'. * Global common subexpression elimination ! This pass performs two different types of GCSE depending on ! whether you are optimizing for size or not (LCM based GCSE tends ! to increase code size for a gain in speed, while Morel-Renvoise ! based GCSE does not). When optimizing for size, GCSE is done ! using Morel-Renvoise Partial Redundancy Elimination, with the ! exception that it does not try to move invariants out of ! loops--that is left to the loop optimization pass. If MR PRE ! GCSE is done, code hoisting (aka unification) is also done, as ! well as load motion. If you are optimizing for speed, LCM (lazy ! code motion) based GCSE is done. LCM is based on the work of ! Knoop, Ruthing, and Steffen. LCM based GCSE also does loop ! invariant code motion. We also perform load and store motion when ! optimizing for speed. Regardless of which type of GCSE is used, ! the GCSE pass also performs global constant and copy propagation. ! The source file for this pass is `gcse.c', and the LCM routines ! are in `lcm.c'. * Loop optimization This pass performs several loop related optimizations. The source ! files `cfgloopanal.c' and `cfgloopmanip.c' contain generic loop ! analysis and manipulation code. Initialization and finalization ! of loop structures is handled by `loop-init.c'. A loop invariant ! motion pass is implemented in `loop-invariant.c'. Basic block ! level optimizations--unrolling, and peeling loops-- are ! implemented in `loop-unroll.c'. Replacing of the exit condition ! of loops by special machine-dependent instructions is handled by ! `loop-doloop.c'. * Jump bypassing This pass is an aggressive form of GCSE that transforms the control flow graph of a function by propagating constants into conditional ! branch instructions. The source file for this pass is `gcse.c'. * If conversion *************** passes that are run after the Tree optim *** 7254,7302 **** instructions, and conditional move instructions. In the very last invocation after reload/LRA, it will generate predicated instructions when supported by the target. The code is located in ! 'ifcvt.c'. * Web construction This pass splits independent uses of each pseudo-register. This can improve effect of the other transformation, such as CSE or ! register allocation. The code for this pass is located in 'web.c'. * Instruction combination This pass attempts to combine groups of two or three instructions that are related by data flow into single instructions. It combines the RTL expressions for the instructions by substitution, ! simplifies the result using algebra, and then attempts to match the ! result against the machine description. The code is located in ! 'combine.c'. * Mode switching optimization This pass looks for instructions that require the processor to be in a specific "mode" and minimizes the number of mode changes ! required to satisfy all users. What these modes are, and what they ! apply to are completely target-specific. The code for this pass is ! located in 'mode-switching.c'. * Modulo scheduling This pass looks at innermost loops and reorders their instructions by overlapping different iterations. Modulo scheduling is performed immediately before instruction scheduling. The code for ! this pass is located in 'modulo-sched.c'. * Instruction scheduling ! This pass looks for instructions whose output will not be available ! by the time that it is used in subsequent instructions. Memory ! loads and floating point instructions often have this behavior on ! RISC machines. It re-orders instructions within a basic block to ! try to separate the definition and use of items that otherwise ! would cause pipeline stalls. This pass is performed twice, before ! and after register allocation. The code for this pass is located ! in 'haifa-sched.c', 'sched-deps.c', 'sched-ebb.c', 'sched-rgn.c' ! and 'sched-vis.c'. * Register allocation --- 7404,7452 ---- instructions, and conditional move instructions. In the very last invocation after reload/LRA, it will generate predicated instructions when supported by the target. The code is located in ! `ifcvt.c'. * Web construction This pass splits independent uses of each pseudo-register. This can improve effect of the other transformation, such as CSE or ! register allocation. The code for this pass is located in `web.c'. * Instruction combination This pass attempts to combine groups of two or three instructions that are related by data flow into single instructions. It combines the RTL expressions for the instructions by substitution, ! simplifies the result using algebra, and then attempts to match ! the result against the machine description. The code is located ! in `combine.c'. * Mode switching optimization This pass looks for instructions that require the processor to be in a specific "mode" and minimizes the number of mode changes ! required to satisfy all users. What these modes are, and what ! they apply to are completely target-specific. The code for this ! pass is located in `mode-switching.c'. * Modulo scheduling This pass looks at innermost loops and reorders their instructions by overlapping different iterations. Modulo scheduling is performed immediately before instruction scheduling. The code for ! this pass is located in `modulo-sched.c'. * Instruction scheduling ! This pass looks for instructions whose output will not be ! available by the time that it is used in subsequent instructions. ! Memory loads and floating point instructions often have this ! behavior on RISC machines. It re-orders instructions within a ! basic block to try to separate the definition and use of items ! that otherwise would cause pipeline stalls. This pass is ! performed twice, before and after register allocation. The code ! for this pass is located in `haifa-sched.c', `sched-deps.c', ! `sched-ebb.c', `sched-rgn.c' and `sched-vis.c'. * Register allocation *************** passes that are run after the Tree optim *** 7320,7330 **** regions using register pressure but the user can force it to use one region or regions corresponding to all loops. ! Source files of the allocator are 'ira.c', 'ira-build.c', ! 'ira-costs.c', 'ira-conflicts.c', 'ira-color.c', 'ira-emit.c', ! 'ira-lives', plus header files 'ira.h' and 'ira-int.h' used ! for the communication between the allocator and the rest of ! the compiler and between the IRA files. * Reloading. This pass renumbers pseudo registers with the hardware registers numbers they were allocated. Pseudo --- 7470,7480 ---- regions using register pressure but the user can force it to use one region or regions corresponding to all loops. ! Source files of the allocator are `ira.c', `ira-build.c', ! `ira-costs.c', `ira-conflicts.c', `ira-color.c', ! `ira-emit.c', `ira-lives', plus header files `ira.h' and ! `ira-int.h' used for the communication between the allocator ! and the rest of the compiler and between the IRA files. * Reloading. This pass renumbers pseudo registers with the hardware registers numbers they were allocated. Pseudo *************** passes that are run after the Tree optim *** 7332,7359 **** stack slots. Then it finds instructions that are invalid because a value has failed to end up in a register, or has ended up in a register of the wrong kind. It fixes up these ! instructions by reloading the problematical values temporarily ! into registers. Additional instructions are generated to do ! the copying. The reload pass also optionally eliminates the frame pointer and inserts instructions to save and restore call-clobbered registers around calls. ! Source files are 'reload.c' and 'reload1.c', plus the header ! 'reload.h' used for communication between them. * This pass is a modern replacement of the reload pass. Source ! files are 'lra.c', 'lra-assign.c', 'lra-coalesce.c', ! 'lra-constraints.c', 'lra-eliminations.c', 'lra-lives.c', ! 'lra-remat.c', 'lra-spills.c', the header 'lra-int.h' used for ! communication between them, and the header 'lra.h' used for ! communication between LRA and the rest of compiler. Unlike the reload pass, intermediate LRA decisions are ! reflected in RTL as much as possible. This reduces the number ! of target-dependent macros and hooks, leaving instruction ! constraints as the primary source of control. LRA is run on targets for which TARGET_LRA_P returns true. --- 7482,7509 ---- stack slots. Then it finds instructions that are invalid because a value has failed to end up in a register, or has ended up in a register of the wrong kind. It fixes up these ! instructions by reloading the problematical values ! temporarily into registers. Additional instructions are ! generated to do the copying. The reload pass also optionally eliminates the frame pointer and inserts instructions to save and restore call-clobbered registers around calls. ! Source files are `reload.c' and `reload1.c', plus the header ! `reload.h' used for communication between them. * This pass is a modern replacement of the reload pass. Source ! files are `lra.c', `lra-assign.c', `lra-coalesce.c', ! `lra-constraints.c', `lra-eliminations.c', `lra-lives.c', ! `lra-remat.c', `lra-spills.c', the header `lra-int.h' used ! for communication between them, and the header `lra.h' used ! for communication between LRA and the rest of compiler. Unlike the reload pass, intermediate LRA decisions are ! reflected in RTL as much as possible. This reduces the ! number of target-dependent macros and hooks, leaving ! instruction constraints as the primary source of control. LRA is run on targets for which TARGET_LRA_P returns true. *************** passes that are run after the Tree optim *** 7363,7370 **** information is not available, various types of static analysis are performed to make the predictions normally coming from the profile feedback (IE execution frequency, branch probability, etc). It is ! implemented in the file 'bb-reorder.c', and the various prediction ! routines are in 'predict.c'. * Variable tracking --- 7513,7520 ---- information is not available, various types of static analysis are performed to make the predictions normally coming from the profile feedback (IE execution frequency, branch probability, etc). It is ! implemented in the file `bb-reorder.c', and the various prediction ! routines are in `predict.c'. * Variable tracking *************** passes that are run after the Tree optim *** 7372,7418 **** in code and generates notes describing the variable locations to RTL code. The location lists are then generated according to these notes to debug information if the debugging information format ! supports location lists. The code is located in 'var-tracking.c'. * Delayed branch scheduling This optional pass attempts to find instructions that can go into the delay slots of other instructions, usually jumps and calls. ! The code for this pass is located in 'reorg.c'. * Branch shortening On many RISC machines, branch instructions have a limited range. Thus, longer sequences of instructions must be used for long ! branches. In this pass, the compiler figures out what how far each ! instruction will be from each other instruction, and therefore ! whether the usual instructions, or the longer sequences, must be ! used for each branch. The code for this pass is located in ! 'final.c'. * Register-to-stack conversion Conversion from usage of some hard registers to usage of a register stack may be done at this point. Currently, this is supported only for the floating-point registers of the Intel 80387 coprocessor. ! The code for this pass is located in 'reg-stack.c'. * Final This pass outputs the assembler code for the function. The source ! files are 'final.c' plus 'insn-output.c'; the latter is generated ! automatically from the machine description by the tool 'genoutput'. ! The header file 'conditions.h' is used for communication between these files. * Debugging information output This is run after final because it must output the stack slot offsets for pseudo registers that did not get hard registers. ! Source files are 'dbxout.c' for DBX symbol table format, 'sdbout.c' ! for SDB symbol table format, 'dwarfout.c' for DWARF symbol table ! format, files 'dwarf2out.c' and 'dwarf2asm.c' for DWARF2 symbol ! table format, and 'vmsdbgout.c' for VMS debug symbol table format.  File: gccint.info, Node: Optimization info, Prev: RTL passes, Up: Passes --- 7522,7570 ---- in code and generates notes describing the variable locations to RTL code. The location lists are then generated according to these notes to debug information if the debugging information format ! supports location lists. The code is located in `var-tracking.c'. * Delayed branch scheduling This optional pass attempts to find instructions that can go into the delay slots of other instructions, usually jumps and calls. ! The code for this pass is located in `reorg.c'. * Branch shortening On many RISC machines, branch instructions have a limited range. Thus, longer sequences of instructions must be used for long ! branches. In this pass, the compiler figures out what how far ! each instruction will be from each other instruction, and ! therefore whether the usual instructions, or the longer sequences, ! must be used for each branch. The code for this pass is located ! in `final.c'. * Register-to-stack conversion Conversion from usage of some hard registers to usage of a register stack may be done at this point. Currently, this is supported only for the floating-point registers of the Intel 80387 coprocessor. ! The code for this pass is located in `reg-stack.c'. * Final This pass outputs the assembler code for the function. The source ! files are `final.c' plus `insn-output.c'; the latter is generated ! automatically from the machine description by the tool `genoutput'. ! The header file `conditions.h' is used for communication between these files. * Debugging information output This is run after final because it must output the stack slot offsets for pseudo registers that did not get hard registers. ! Source files are `dbxout.c' for DBX symbol table format, ! `sdbout.c' for SDB symbol table format, `dwarfout.c' for DWARF ! symbol table format, files `dwarf2out.c' and `dwarf2asm.c' for ! DWARF2 symbol table format, and `vmsdbgout.c' for VMS debug symbol ! table format. !  File: gccint.info, Node: Optimization info, Prev: RTL passes, Up: Passes *************** File: gccint.info, Node: Optimization i *** 7421,7427 **** ===================== This section is describes dump infrastructure which is common to both ! pass dumps as well as optimization dumps. The goal for this infrastructure is to provide both gcc developers and users detailed information about various compiler transformations and optimizations. --- 7573,7579 ---- ===================== This section is describes dump infrastructure which is common to both ! pass dumps as well as optimization dumps. The goal for this infrastructure is to provide both gcc developers and users detailed information about various compiler transformations and optimizations. *************** File: gccint.info, Node: Dump setup, N *** 7440,7463 **** 9.7.1 Dump setup ---------------- ! A dump_manager class is defined in 'dumpfile.h'. Various passes ! register dumping pass-specific information via 'dump_register' in ! 'passes.c'. During the registration, an optimization pass can select ! its optimization group (*note Optimization groups::). After that optimization information corresponding to the entire group (presumably ! from multiple passes) can be output via command-line switches. Note that if a pass does not fit into any of the pre-defined groups, it can ! select 'OPTGROUP_NONE'. Note that in general, a pass need not know its dump output file name, ! whether certain flags are enabled, etc. However, for legacy reasons, ! passes could also call 'dump_begin' which returns a stream in case the ! particular pass has optimization dumps enabled. A pass could call ! 'dump_end' when the dump has ended. These methods should go away once all the passes are converted to use the new dump infrastructure. ! The recommended way to setup the dump output is via 'dump_start' and ! 'dump_end'.  File: gccint.info, Node: Optimization groups, Next: Dump files and streams, Prev: Dump setup, Up: Optimization info --- 7592,7615 ---- 9.7.1 Dump setup ---------------- ! A dump_manager class is defined in `dumpfile.h'. Various passes ! register dumping pass-specific information via `dump_register' in ! `passes.c'. During the registration, an optimization pass can select ! its optimization group (*note Optimization groups::). After that optimization information corresponding to the entire group (presumably ! from multiple passes) can be output via command-line switches. Note that if a pass does not fit into any of the pre-defined groups, it can ! select `OPTGROUP_NONE'. Note that in general, a pass need not know its dump output file name, ! whether certain flags are enabled, etc. However, for legacy reasons, ! passes could also call `dump_begin' which returns a stream in case the ! particular pass has optimization dumps enabled. A pass could call ! `dump_end' when the dump has ended. These methods should go away once all the passes are converted to use the new dump infrastructure. ! The recommended way to setup the dump output is via `dump_start' and ! `dump_end'.  File: gccint.info, Node: Optimization groups, Next: Dump files and streams, Prev: Dump setup, Up: Optimization info *************** File: gccint.info, Node: Optimization g *** 7465,7494 **** 9.7.2 Optimization groups ------------------------- ! The optimization passes are grouped into several categories. Currently ! defined categories in 'dumpfile.h' are ! 'OPTGROUP_IPA' ! IPA optimization passes. Enabled by '-ipa' ! 'OPTGROUP_LOOP' ! Loop optimization passes. Enabled by '-loop'. ! 'OPTGROUP_INLINE' ! Inlining passes. Enabled by '-inline'. ! 'OPTGROUP_VEC' ! Vectorization passes. Enabled by '-vec'. ! 'OPTGROUP_OTHER' All other optimization passes which do not fall into one of the above. ! 'OPTGROUP_ALL' ! All optimization passes. Enabled by '-all'. By using groups a user could selectively enable optimization ! information only for a group of passes. By default, the optimization information for all the passes is dumped.  --- 7617,7647 ---- 9.7.2 Optimization groups ------------------------- ! The optimization passes are grouped into several categories. Currently ! defined categories in `dumpfile.h' are ! `OPTGROUP_IPA' ! IPA optimization passes. Enabled by `-ipa' ! `OPTGROUP_LOOP' ! Loop optimization passes. Enabled by `-loop'. ! `OPTGROUP_INLINE' ! Inlining passes. Enabled by `-inline'. ! `OPTGROUP_VEC' ! Vectorization passes. Enabled by `-vec'. ! `OPTGROUP_OTHER' All other optimization passes which do not fall into one of the above. ! `OPTGROUP_ALL' ! All optimization passes. Enabled by `-all'. ! By using groups a user could selectively enable optimization ! information only for a group of passes. By default, the optimization information for all the passes is dumped.  *************** File: gccint.info, Node: Dump files and *** 7498,7522 **** ---------------------------- There are two separate output streams available for outputting ! optimization information from passes. Note that both these streams ! accept 'stderr' and 'stdout' as valid streams and thus it is possible to ! dump output to standard output or error. This is specially handy for outputting all available information in a single file by redirecting ! 'stderr'. ! 'pstream' ! This stream is for pass-specific dump output. For example, ! '-fdump-tree-vect=foo.v' dumps tree vectorization pass output into ! the given file name 'foo.v'. If the file name is not provided, the ! default file name is based on the source file and pass number. ! Note that one could also use special file names 'stdout' and ! 'stderr' for dumping to standard output and standard error ! respectively. ! 'alt_stream' This steam is used for printing optimization specific output in ! response to the '-fopt-info'. Again a file name can be given. If ! the file name is not given, it defaults to 'stderr'.  File: gccint.info, Node: Dump output verbosity, Next: Dump types, Prev: Dump files and streams, Up: Optimization info --- 7651,7674 ---- ---------------------------- There are two separate output streams available for outputting ! optimization information from passes. Note that both these streams ! accept `stderr' and `stdout' as valid streams and thus it is possible ! to dump output to standard output or error. This is specially handy for outputting all available information in a single file by redirecting ! `stderr'. ! ``pstream'' ! This stream is for pass-specific dump output. For example, ! `-fdump-tree-vect=foo.v' dumps tree vectorization pass output into ! the given file name `foo.v'. If the file name is not provided, the ! default file name is based on the source file and pass number. Note ! that one could also use special file names `stdout' and `stderr' ! for dumping to standard output and standard error respectively. ! ``alt_stream'' This steam is used for printing optimization specific output in ! response to the `-fopt-info'. Again a file name can be given. If ! the file name is not given, it defaults to `stderr'.  File: gccint.info, Node: Dump output verbosity, Next: Dump types, Prev: Dump files and streams, Up: Optimization info *************** File: gccint.info, Node: Dump output ve *** 7526,7552 **** The dump verbosity has the following options ! 'optimized' ! Print information when an optimization is successfully applied. It ! is up to a pass to decide which information is relevant. For example, the vectorizer passes print the source location of loops which got successfully vectorized. ! 'missed' ! Print information about missed optimizations. Individual passes ! control which information to include in the output. For example, gcc -O2 -ftree-vectorize -fopt-info-vec-missed will print information about missed optimization opportunities from vectorization passes on stderr. ! 'note' Print verbose information about optimizations, such as certain transformations, more detailed messages about decisions etc. ! 'all' ! Print detailed optimization information. This includes OPTIMIZED, MISSED, and NOTE.  --- 7678,7704 ---- The dump verbosity has the following options ! `optimized' ! Print information when an optimization is successfully applied. It ! is up to a pass to decide which information is relevant. For example, the vectorizer passes print the source location of loops which got successfully vectorized. ! `missed' ! Print information about missed optimizations. Individual passes ! control which information to include in the output. For example, gcc -O2 -ftree-vectorize -fopt-info-vec-missed will print information about missed optimization opportunities from vectorization passes on stderr. ! `note' Print verbose information about optimizations, such as certain transformations, more detailed messages about decisions etc. ! `all' ! Print detailed optimization information. This includes OPTIMIZED, MISSED, and NOTE.  *************** File: gccint.info, Node: Dump types, N *** 7555,7594 **** 9.7.5 Dump types ---------------- ! 'dump_printf' ! ! This is a generic method for doing formatted output. It takes an ! additional argument 'dump_kind' which signifies the type of dump. ! This method outputs information only when the dumps are enabled for ! this particular 'dump_kind'. Note that the caller doesn't need to ! know if the particular dump is enabled or not, or even the file ! name. The caller only needs to decide which dump output ! information is relevant, and under what conditions. This ! determines the associated flags. ! Consider the following example from 'loop-unroll.c' where an informative message about a loop (along with its location) is printed when any of the following flags is enabled - - optimization messages - RTL dumps - detailed dumps int report_flags = MSG_OPTIMIZED_LOCATIONS | TDF_RTL | TDF_DETAILS; dump_printf_loc (report_flags, locus, "loop turned into non-loop; it never loops.\n"); ! 'dump_basic_block' Output basic block. ! 'dump_generic_expr' Output generic expression. ! 'dump_gimple_stmt' Output gimple statement. Note that the above methods also have variants prefixed with ! '_loc', such as 'dump_printf_loc', which are similar except they also output the source location information.  File: gccint.info, Node: Dump examples, Prev: Dump types, Up: Optimization info --- 7707,7750 ---- 9.7.5 Dump types ---------------- ! `dump_printf' ! This is a generic method for doing formatted output. It takes an ! additional argument `dump_kind' which signifies the type of dump. ! This method outputs information only when the dumps are enabled ! for this particular `dump_kind'. Note that the caller doesn't need ! to know if the particular dump is enabled or not, or even the file ! name. The caller only needs to decide which dump output ! information is relevant, and under what conditions. This determines ! the associated flags. ! Consider the following example from `loop-unroll.c' where an informative message about a loop (along with its location) is printed when any of the following flags is enabled - optimization messages + - RTL dumps + - detailed dumps + int report_flags = MSG_OPTIMIZED_LOCATIONS | TDF_RTL | TDF_DETAILS; dump_printf_loc (report_flags, locus, "loop turned into non-loop; it never loops.\n"); ! `dump_basic_block' Output basic block. ! ! `dump_generic_expr' Output generic expression. ! ! `dump_gimple_stmt' Output gimple statement. Note that the above methods also have variants prefixed with ! `_loc', such as `dump_printf_loc', which are similar except they also output the source location information. +  File: gccint.info, Node: Dump examples, Prev: Dump types, Up: Optimization info *************** File: gccint.info, Node: Dump examples, *** 7598,7631 **** gcc -O3 -fopt-info-missed=missed.all outputs missed optimization report from all the passes into ! 'missed.all'. As another example, gcc -O3 -fopt-info-inline-optimized-missed=inline.txt ! will output information about missed optimizations as well as optimized ! locations from all the inlining passes into 'inline.txt'. If the FILENAME is provided, then the dumps from all the applicable ! optimizations are concatenated into the 'filename'. Otherwise the dump ! is output onto 'stderr'. If OPTIONS is omitted, it defaults to ! 'all-all', which means dump all available optimization info from all the ! passes. In the following example, all optimization info is output on to ! 'stderr'. gcc -O3 -fopt-info ! Note that '-fopt-info-vec-missed' behaves the same as ! '-fopt-info-missed-vec'. As another example, consider gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt ! Here the two output file names 'vec.miss' and 'loop.opt' are in ! conflict since only one output file is allowed. In this case, only the ! first option takes effect and the subsequent options are ignored. Thus ! only the 'vec.miss' is produced which containts dumps from the vectorizer about missed opportunities.  --- 7754,7787 ---- gcc -O3 -fopt-info-missed=missed.all outputs missed optimization report from all the passes into ! `missed.all'. As another example, gcc -O3 -fopt-info-inline-optimized-missed=inline.txt ! will output information about missed optimizations as well as ! optimized locations from all the inlining passes into `inline.txt'. If the FILENAME is provided, then the dumps from all the applicable ! optimizations are concatenated into the `filename'. Otherwise the dump ! is output onto `stderr'. If OPTIONS is omitted, it defaults to ! `all-all', which means dump all available optimization info from all ! the passes. In the following example, all optimization info is output ! on to `stderr'. gcc -O3 -fopt-info ! Note that `-fopt-info-vec-missed' behaves the same as ! `-fopt-info-missed-vec'. As another example, consider gcc -fopt-info-vec-missed=vec.miss -fopt-info-loop-optimized=loop.opt ! Here the two output file names `vec.miss' and `loop.opt' are in ! conflict since only one output file is allowed. In this case, only the ! first option takes effect and the subsequent options are ignored. Thus ! only the `vec.miss' is produced which containts dumps from the vectorizer about missed opportunities.  *************** The purpose of GENERIC is simply to prov *** 7638,7663 **** of representing an entire function in trees. To this end, it was necessary to add a few new tree codes to the back end, but almost everything was already there. If you can express it with the codes in ! 'gcc/tree.def', it's GENERIC. Early on, there was a great deal of debate about how to think about statements in a tree IL. In GENERIC, a statement is defined as any expression whose value, if any, is ignored. A statement will always ! have 'TREE_SIDE_EFFECTS' set (or it will be discarded), but a ! non-statement expression may also have side effects. A 'CALL_EXPR', for ! instance. It would be possible for some local optimizations to work on the GENERIC form of a function; indeed, the adapted tree inliner works fine ! on GENERIC, but the current compiler performs inlining after lowering to ! GIMPLE (a restricted form described in the next section). Indeed, currently the frontends perform this lowering before handing off to ! 'tree_rest_of_compilation', but this seems inelegant. * Menu: * Deficiencies:: Topics net yet covered in this document. ! * Tree overview:: All about 'tree's. * Types:: Fundamental and aggregate types. * Declarations:: Type declarations and variables. * Attributes:: Declaration and type attributes. --- 7794,7819 ---- of representing an entire function in trees. To this end, it was necessary to add a few new tree codes to the back end, but almost everything was already there. If you can express it with the codes in ! `gcc/tree.def', it's GENERIC. Early on, there was a great deal of debate about how to think about statements in a tree IL. In GENERIC, a statement is defined as any expression whose value, if any, is ignored. A statement will always ! have `TREE_SIDE_EFFECTS' set (or it will be discarded), but a ! non-statement expression may also have side effects. A `CALL_EXPR', ! for instance. It would be possible for some local optimizations to work on the GENERIC form of a function; indeed, the adapted tree inliner works fine ! on GENERIC, but the current compiler performs inlining after lowering ! to GIMPLE (a restricted form described in the next section). Indeed, currently the frontends perform this lowering before handing off to ! `tree_rest_of_compilation', but this seems inelegant. * Menu: * Deficiencies:: Topics net yet covered in this document. ! * Tree overview:: All about `tree's. * Types:: Fundamental and aggregate types. * Declarations:: Type declarations and variables. * Attributes:: Declaration and type attributes. *************** File: gccint.info, Node: Tree overview, *** 7684,7721 **** ============= The central data structure used by the internal representation is the ! 'tree'. These nodes, while all of the C type 'tree', are of many ! varieties. A 'tree' is a pointer type, but the object to which it points may be of a variety of types. From this point forward, we will ! refer to trees in ordinary type, rather than in 'this font', except when ! talking about the actual C type 'tree'. You can tell what kind of node a particular tree is by using the ! 'TREE_CODE' macro. Many, many macros take trees as input and return trees as output. However, most macros require a certain kind of tree ! node as input. In other words, there is a type-system for trees, but it ! is not reflected in the C type-system. ! For safety, it is useful to configure GCC with '--enable-checking'. Although this results in a significant performance penalty (since all tree types are checked at run-time), and is therefore inappropriate in a release version, it is extremely helpful during the development process. Many macros behave as predicates. Many, although not all, of these ! predicates end in '_P'. Do not rely on the result type of these macros being of any particular type. You may, however, rely on the fact that ! the type can be compared to '0', so that statements like if (TEST_P (t) && !TEST_P (y)) x = 1; ! and int i = (TEST_P (t) != 0); ! are legal. Macros that return 'int' values now may be changed to return ! 'tree' values, or other pointers in the future. Even those that ! continue to return 'int' may return multiple nonzero codes where previously they returned only zero and one. Therefore, you should not write code like if (TEST_P (t) == 1) ! as this code is not guaranteed to work correctly in the future. You should not take the address of values returned by the macros or functions described here. In particular, no guarantee is given that the --- 7840,7877 ---- ============= The central data structure used by the internal representation is the ! `tree'. These nodes, while all of the C type `tree', are of many ! varieties. A `tree' is a pointer type, but the object to which it points may be of a variety of types. From this point forward, we will ! refer to trees in ordinary type, rather than in `this font', except ! when talking about the actual C type `tree'. You can tell what kind of node a particular tree is by using the ! `TREE_CODE' macro. Many, many macros take trees as input and return trees as output. However, most macros require a certain kind of tree ! node as input. In other words, there is a type-system for trees, but ! it is not reflected in the C type-system. ! For safety, it is useful to configure GCC with `--enable-checking'. Although this results in a significant performance penalty (since all tree types are checked at run-time), and is therefore inappropriate in a release version, it is extremely helpful during the development process. Many macros behave as predicates. Many, although not all, of these ! predicates end in `_P'. Do not rely on the result type of these macros being of any particular type. You may, however, rely on the fact that ! the type can be compared to `0', so that statements like if (TEST_P (t) && !TEST_P (y)) x = 1; ! and int i = (TEST_P (t) != 0); ! are legal. Macros that return `int' values now may be changed to ! return `tree' values, or other pointers in the future. Even those that ! continue to return `int' may return multiple nonzero codes where previously they returned only zero and one. Therefore, you should not write code like if (TEST_P (t) == 1) ! as this code is not guaranteed to work correctly in the future. You should not take the address of values returned by the macros or functions described here. In particular, no guarantee is given that the *************** made up entirely of uppercase letters ma *** 7728,7752 **** than once. You may assume that a macro or function whose name is made up entirely of lowercase letters will evaluate its arguments only once. ! The 'error_mark_node' is a special tree. Its tree code is ! 'ERROR_MARK', but since there is only ever one node with that code, the ! usual practice is to compare the tree against 'error_mark_node'. (This test is just a test for pointer equality.) If an error has occurred ! during front-end processing the flag 'errorcount' will be set. If the ! front end has encountered code it cannot handle, it will issue a message ! to the user and set 'sorrycount'. When these flags are set, any macro ! or function which normally returns a tree of a particular kind may ! instead return the 'error_mark_node'. Thus, if you intend to do any ! processing of erroneous code, you must be prepared to deal with the ! 'error_mark_node'. Occasionally, a particular tree slot (like an operand to an expression, ! or a particular field in a declaration) will be referred to as "reserved ! for the back end". These slots are used to store RTL when the tree is ! converted to RTL for use by the GCC back end. However, if that process ! is not taking place (e.g., if the front end is being hooked up to an ! intelligent editor), then those slots may be used by the back end ! presently in use. If you encounter situations that do not match this documentation, such as tree nodes of types not mentioned here, or macros documented to --- 7884,7908 ---- than once. You may assume that a macro or function whose name is made up entirely of lowercase letters will evaluate its arguments only once. ! The `error_mark_node' is a special tree. Its tree code is ! `ERROR_MARK', but since there is only ever one node with that code, the ! usual practice is to compare the tree against `error_mark_node'. (This test is just a test for pointer equality.) If an error has occurred ! during front-end processing the flag `errorcount' will be set. If the ! front end has encountered code it cannot handle, it will issue a ! message to the user and set `sorrycount'. When these flags are set, ! any macro or function which normally returns a tree of a particular ! kind may instead return the `error_mark_node'. Thus, if you intend to ! do any processing of erroneous code, you must be prepared to deal with ! the `error_mark_node'. Occasionally, a particular tree slot (like an operand to an expression, ! or a particular field in a declaration) will be referred to as ! "reserved for the back end". These slots are used to store RTL when ! the tree is converted to RTL for use by the GCC back end. However, if ! that process is not taking place (e.g., if the front end is being hooked ! up to an intelligent editor), then those slots may be used by the back ! end presently in use. If you encounter situations that do not match this documentation, such as tree nodes of types not mentioned here, or macros documented to *************** File: gccint.info, Node: Macros and Fun *** 7766,7834 **** 10.2.1 Trees ------------ ! All GENERIC trees have two fields in common. First, 'TREE_CHAIN' is a pointer that can be used as a singly-linked list to other trees. The ! other is 'TREE_TYPE'. Many trees store the type of an expression or declaration in this field. These are some other functions for handling trees: ! 'tree_size' Return the number of bytes a tree takes. ! 'build0' ! 'build1' ! 'build2' ! 'build3' ! 'build4' ! 'build5' ! 'build6' ! These functions build a tree and supply values to put in each ! parameter. The basic signature is 'code, type, [operands]'. ! 'code' is the 'TREE_CODE', and 'type' is a tree representing the ! 'TREE_TYPE'. These are followed by the operands, each of which is also a tree.  File: gccint.info, Node: Identifiers, Next: Containers, Prev: Macros and Functions, Up: Tree overview 10.2.2 Identifiers ------------------ ! An 'IDENTIFIER_NODE' represents a slightly more general concept than the ! standard C or C++ concept of identifier. In particular, an ! 'IDENTIFIER_NODE' may contain a '$', or other extraordinary characters. ! There are never two distinct 'IDENTIFIER_NODE's representing the same identifier. Therefore, you may use pointer equality to compare ! 'IDENTIFIER_NODE's, rather than using a routine like 'strcmp'. Use ! 'get_identifier' to obtain the unique 'IDENTIFIER_NODE' for a supplied string. You can use the following macros to access identifiers: ! 'IDENTIFIER_POINTER' ! The string represented by the identifier, represented as a 'char*'. ! This string is always 'NUL'-terminated, and contains no embedded ! 'NUL' characters. ! 'IDENTIFIER_LENGTH' ! The length of the string returned by 'IDENTIFIER_POINTER', not ! including the trailing 'NUL'. This value of 'IDENTIFIER_LENGTH ! (x)' is always the same as 'strlen (IDENTIFIER_POINTER (x))'. ! 'IDENTIFIER_OPNAME_P' This predicate holds if the identifier represents the name of an overloaded operator. In this case, you should not depend on the ! contents of either the 'IDENTIFIER_POINTER' or the ! 'IDENTIFIER_LENGTH'. ! 'IDENTIFIER_TYPENAME_P' This predicate holds if the identifier represents the name of a ! user-defined conversion operator. In this case, the 'TREE_TYPE' of ! the 'IDENTIFIER_NODE' holds the type to which the conversion operator converts.  File: gccint.info, Node: Containers, Prev: Identifiers, Up: Tree overview --- 7922,7991 ---- 10.2.1 Trees ------------ ! All GENERIC trees have two fields in common. First, `TREE_CHAIN' is a pointer that can be used as a singly-linked list to other trees. The ! other is `TREE_TYPE'. Many trees store the type of an expression or declaration in this field. These are some other functions for handling trees: ! `tree_size' Return the number of bytes a tree takes. ! `build0' ! `build1' ! `build2' ! `build3' ! `build4' ! `build5' ! `build6' These functions build a tree and supply values to put in each ! parameter. The basic signature is `code, type, [operands]'. ! `code' is the `TREE_CODE', and `type' is a tree representing the ! `TREE_TYPE'. These are followed by the operands, each of which is also a tree. +  File: gccint.info, Node: Identifiers, Next: Containers, Prev: Macros and Functions, Up: Tree overview 10.2.2 Identifiers ------------------ ! An `IDENTIFIER_NODE' represents a slightly more general concept than ! the standard C or C++ concept of identifier. In particular, an ! `IDENTIFIER_NODE' may contain a `$', or other extraordinary characters. ! There are never two distinct `IDENTIFIER_NODE's representing the same identifier. Therefore, you may use pointer equality to compare ! `IDENTIFIER_NODE's, rather than using a routine like `strcmp'. Use ! `get_identifier' to obtain the unique `IDENTIFIER_NODE' for a supplied string. You can use the following macros to access identifiers: ! `IDENTIFIER_POINTER' ! The string represented by the identifier, represented as a ! `char*'. This string is always `NUL'-terminated, and contains no ! embedded `NUL' characters. ! `IDENTIFIER_LENGTH' ! The length of the string returned by `IDENTIFIER_POINTER', not ! including the trailing `NUL'. This value of `IDENTIFIER_LENGTH ! (x)' is always the same as `strlen (IDENTIFIER_POINTER (x))'. ! `IDENTIFIER_OPNAME_P' This predicate holds if the identifier represents the name of an overloaded operator. In this case, you should not depend on the ! contents of either the `IDENTIFIER_POINTER' or the ! `IDENTIFIER_LENGTH'. ! `IDENTIFIER_TYPENAME_P' This predicate holds if the identifier represents the name of a ! user-defined conversion operator. In this case, the `TREE_TYPE' of ! the `IDENTIFIER_NODE' holds the type to which the conversion operator converts. +  File: gccint.info, Node: Containers, Prev: Identifiers, Up: Tree overview *************** File: gccint.info, Node: Containers, P *** 7836,7857 **** ----------------- Two common container data structures can be represented directly with ! tree nodes. A 'TREE_LIST' is a singly linked list containing two trees ! per node. These are the 'TREE_PURPOSE' and 'TREE_VALUE' of each node. ! (Often, the 'TREE_PURPOSE' contains some kind of tag, or additional ! information, while the 'TREE_VALUE' contains the majority of the ! payload. In other cases, the 'TREE_PURPOSE' is simply 'NULL_TREE', ! while in still others both the 'TREE_PURPOSE' and 'TREE_VALUE' are of ! equal stature.) Given one 'TREE_LIST' node, the next node is found by ! following the 'TREE_CHAIN'. If the 'TREE_CHAIN' is 'NULL_TREE', then you have reached the end of the list. ! A 'TREE_VEC' is a simple vector. The 'TREE_VEC_LENGTH' is an integer (not a tree) giving the number of nodes in the vector. The nodes ! themselves are accessed using the 'TREE_VEC_ELT' macro, which takes two ! arguments. The first is the 'TREE_VEC' in question; the second is an ! integer indicating which element in the vector is desired. The elements ! are indexed from zero.  File: gccint.info, Node: Types, Next: Declarations, Prev: Tree overview, Up: GENERIC --- 7993,8014 ---- ----------------- Two common container data structures can be represented directly with ! tree nodes. A `TREE_LIST' is a singly linked list containing two trees ! per node. These are the `TREE_PURPOSE' and `TREE_VALUE' of each node. ! (Often, the `TREE_PURPOSE' contains some kind of tag, or additional ! information, while the `TREE_VALUE' contains the majority of the ! payload. In other cases, the `TREE_PURPOSE' is simply `NULL_TREE', ! while in still others both the `TREE_PURPOSE' and `TREE_VALUE' are of ! equal stature.) Given one `TREE_LIST' node, the next node is found by ! following the `TREE_CHAIN'. If the `TREE_CHAIN' is `NULL_TREE', then you have reached the end of the list. ! A `TREE_VEC' is a simple vector. The `TREE_VEC_LENGTH' is an integer (not a tree) giving the number of nodes in the vector. The nodes ! themselves are accessed using the `TREE_VEC_ELT' macro, which takes two ! arguments. The first is the `TREE_VEC' in question; the second is an ! integer indicating which element in the vector is desired. The ! elements are indexed from zero.  File: gccint.info, Node: Types, Next: Declarations, Prev: Tree overview, Up: GENERIC *************** that there is exactly one tree node corr *** 7864,8108 **** are often multiple nodes corresponding to the same type. For the most part, different kinds of types have different tree codes. ! (For example, pointer types use a 'POINTER_TYPE' code while arrays use ! an 'ARRAY_TYPE' code.) However, pointers to member functions use the ! 'RECORD_TYPE' code. Therefore, when writing a 'switch' statement that depends on the code associated with a particular type, you should take ! care to handle pointers to member functions under the 'RECORD_TYPE' case ! label. The following functions and macros deal with cv-qualification of types: ! 'TYPE_MAIN_VARIANT' This macro returns the unqualified version of a type. It may be applied to an unqualified type, but it is not always the identity function in that case. A few other macros and functions are usable with all types: ! 'TYPE_SIZE' The number of bits required to represent the type, represented as ! an 'INTEGER_CST'. For an incomplete type, 'TYPE_SIZE' will be ! 'NULL_TREE'. ! 'TYPE_ALIGN' ! The alignment of the type, in bits, represented as an 'int'. ! 'TYPE_NAME' ! This macro returns a declaration (in the form of a 'TYPE_DECL') for ! the type. (Note this macro does _not_ return an 'IDENTIFIER_NODE', ! as you might expect, given its name!) You can look at the ! 'DECL_NAME' of the 'TYPE_DECL' to obtain the actual name of the ! type. The 'TYPE_NAME' will be 'NULL_TREE' for a type that is not a ! built-in type, the result of a typedef, or a named class type. ! 'TYPE_CANONICAL' This macro returns the "canonical" type for the given type node. Canonical types are used to improve performance in the C++ and Objective-C++ front ends by allowing efficient comparison between ! two type nodes in 'same_type_p': if the 'TYPE_CANONICAL' values of the types are equal, the types are equivalent; otherwise, the types ! are not equivalent. The notion of equivalence for canonical types is the same as the notion of type equivalence in the language ! itself. For instance, ! When 'TYPE_CANONICAL' is 'NULL_TREE', there is no canonical type ! for the given type node. In this case, comparison between this type and any other type requires the compiler to perform a deep, "structural" comparison to see if the two type nodes have the same form and properties. The canonical type for a node is always the most fundamental type ! in the equivalence class of types. For instance, 'int' is its own ! canonical type. A typedef 'I' of 'int' will have 'int' as its ! canonical type. Similarly, 'I*' and a typedef 'IP' (defined to ! 'I*') will has 'int*' as their canonical type. When building a new ! type node, be sure to set 'TYPE_CANONICAL' to the appropriate ! canonical type. If the new type is a compound type (built from other types), and any of those other types require structural ! equality, use 'SET_TYPE_STRUCTURAL_EQUALITY' to ensure that the new ! type also requires structural equality. Finally, if for some ! reason you cannot guarantee that 'TYPE_CANONICAL' will point to the ! canonical type, use 'SET_TYPE_STRUCTURAL_EQUALITY' to make sure ! that the new type-and any type constructed based on it-requires ! structural equality. If you suspect that the canonical type system ! is miscomparing types, pass '--param verify-canonical-types=1' to ! the compiler or configure with '--enable-checking' to force the ! compiler to verify its canonical-type comparisons against the ! structural comparisons; the compiler will then print any warnings ! if the canonical types miscompare. ! 'TYPE_STRUCTURAL_EQUALITY_P' This predicate holds when the node requires structural equality ! checks, e.g., when 'TYPE_CANONICAL' is 'NULL_TREE'. ! 'SET_TYPE_STRUCTURAL_EQUALITY' This macro states that the type node it is given requires ! structural equality checks, e.g., it sets 'TYPE_CANONICAL' to ! 'NULL_TREE'. ! 'same_type_p' This predicate takes two types as input, and holds if they are the ! same type. For example, if one type is a 'typedef' for the other, ! or both are 'typedef's for the same type. This predicate also holds if the two trees given as input are simply copies of one another; i.e., there is no difference between them at the source level, but, for whatever reason, a duplicate has been made in the ! representation. You should never use '==' (pointer equality) to ! compare types; always use 'same_type_p' instead. Detailed below are the various kinds of types, and the macros that can be used to access them. Although other kinds of types are used elsewhere in G++, the types described here are the only ones that you will encounter while examining the intermediate representation. ! 'VOID_TYPE' ! Used to represent the 'void' type. ! 'INTEGER_TYPE' ! Used to represent the various integral types, including 'char', ! 'short', 'int', 'long', and 'long long'. This code is not used for ! enumeration types, nor for the 'bool' type. The 'TYPE_PRECISION' ! is the number of bits used in the representation, represented as an ! 'unsigned int'. (Note that in the general case this is not the ! same value as 'TYPE_SIZE'; suppose that there were a 24-bit integer ! type, but that alignment requirements for the ABI required 32-bit ! alignment. Then, 'TYPE_SIZE' would be an 'INTEGER_CST' for 32, ! while 'TYPE_PRECISION' would be 24.) The integer type is unsigned ! if 'TYPE_UNSIGNED' holds; otherwise, it is signed. ! The 'TYPE_MIN_VALUE' is an 'INTEGER_CST' for the smallest integer that may be represented by this type. Similarly, the ! 'TYPE_MAX_VALUE' is an 'INTEGER_CST' for the largest integer that may be represented by this type. ! 'REAL_TYPE' ! Used to represent the 'float', 'double', and 'long double' types. ! The number of bits in the floating-point representation is given by ! 'TYPE_PRECISION', as in the 'INTEGER_TYPE' case. ! 'FIXED_POINT_TYPE' ! Used to represent the 'short _Fract', '_Fract', 'long _Fract', ! 'long long _Fract', 'short _Accum', '_Accum', 'long _Accum', and ! 'long long _Accum' types. The number of bits in the fixed-point ! representation is given by 'TYPE_PRECISION', as in the ! 'INTEGER_TYPE' case. There may be padding bits, fractional bits and integral bits. The number of fractional bits is given by ! 'TYPE_FBIT', and the number of integral bits is given by ! 'TYPE_IBIT'. The fixed-point type is unsigned if 'TYPE_UNSIGNED' ! holds; otherwise, it is signed. The fixed-point type is saturating ! if 'TYPE_SATURATING' holds; otherwise, it is not saturating. ! 'COMPLEX_TYPE' ! Used to represent GCC built-in '__complex__' data types. The ! 'TREE_TYPE' is the type of the real and imaginary parts. ! 'ENUMERAL_TYPE' ! Used to represent an enumeration type. The 'TYPE_PRECISION' gives ! (as an 'int'), the number of bits used to represent the type. If ! there are no negative enumeration constants, 'TYPE_UNSIGNED' will hold. The minimum and maximum enumeration constants may be ! obtained with 'TYPE_MIN_VALUE' and 'TYPE_MAX_VALUE', respectively; ! each of these macros returns an 'INTEGER_CST'. The actual enumeration constants themselves may be obtained by ! looking at the 'TYPE_VALUES'. This macro will return a ! 'TREE_LIST', containing the constants. The 'TREE_PURPOSE' of each ! node will be an 'IDENTIFIER_NODE' giving the name of the constant; ! the 'TREE_VALUE' will be an 'INTEGER_CST' giving the value assigned ! to that constant. These constants will appear in the order in ! which they were declared. The 'TREE_TYPE' of each of these ! constants will be the type of enumeration type itself. ! 'BOOLEAN_TYPE' ! Used to represent the 'bool' type. ! 'POINTER_TYPE' Used to represent pointer types, and pointer to data member types. ! The 'TREE_TYPE' gives the type to which this type points. ! 'REFERENCE_TYPE' ! Used to represent reference types. The 'TREE_TYPE' gives the type to which this type refers. ! 'FUNCTION_TYPE' Used to represent the type of non-member functions and of static ! member functions. The 'TREE_TYPE' gives the return type of the ! function. The 'TYPE_ARG_TYPES' are a 'TREE_LIST' of the argument ! types. The 'TREE_VALUE' of each node in this list is the type of ! the corresponding argument; the 'TREE_PURPOSE' is an expression for ! the default argument value, if any. If the last node in the list ! is 'void_list_node' (a 'TREE_LIST' node whose 'TREE_VALUE' is the ! 'void_type_node'), then functions of this type do not take variable ! arguments. Otherwise, they do take a variable number of arguments. ! Note that in C (but not in C++) a function declared like 'void f()' is an unprototyped function taking a variable number of arguments; ! the 'TYPE_ARG_TYPES' of such a function will be 'NULL'. ! 'METHOD_TYPE' Used to represent the type of a non-static member function. Like a ! 'FUNCTION_TYPE', the return type is given by the 'TREE_TYPE'. The ! type of '*this', i.e., the class of which functions of this type ! are a member, is given by the 'TYPE_METHOD_BASETYPE'. The ! 'TYPE_ARG_TYPES' is the parameter list, as for a 'FUNCTION_TYPE', ! and includes the 'this' argument. ! 'ARRAY_TYPE' ! Used to represent array types. The 'TREE_TYPE' gives the type of the elements in the array. If the array-bound is present in the ! type, the 'TYPE_DOMAIN' is an 'INTEGER_TYPE' whose 'TYPE_MIN_VALUE' ! and 'TYPE_MAX_VALUE' will be the lower and upper bounds of the ! array, respectively. The 'TYPE_MIN_VALUE' will always be an ! 'INTEGER_CST' for zero, while the 'TYPE_MAX_VALUE' will be one less ! than the number of elements in the array, i.e., the highest value ! which may be used to index an element in the array. ! 'RECORD_TYPE' ! Used to represent 'struct' and 'class' types, as well as pointers to member functions and similar constructs in other languages. ! 'TYPE_FIELDS' contains the items contained in this type, each of ! which can be a 'FIELD_DECL', 'VAR_DECL', 'CONST_DECL', or ! 'TYPE_DECL'. You may not make any assumptions about the ordering of the fields in the type or whether one or more of them overlap. ! 'UNION_TYPE' ! Used to represent 'union' types. Similar to 'RECORD_TYPE' except ! that all 'FIELD_DECL' nodes in 'TYPE_FIELD' start at bit position zero. ! 'QUAL_UNION_TYPE' Used to represent part of a variant record in Ada. Similar to ! 'UNION_TYPE' except that each 'FIELD_DECL' has a 'DECL_QUALIFIER' field, which contains a boolean expression that indicates whether the field is present in the object. The type will only have one ! field, so each field's 'DECL_QUALIFIER' is only evaluated if none ! of the expressions in the previous fields in 'TYPE_FIELDS' are nonzero. Normally these expressions will reference a field in the ! outer object using a 'PLACEHOLDER_EXPR'. ! 'LANG_TYPE' This node is used to represent a language-specific type. The front end must handle it. ! 'OFFSET_TYPE' This node is used to represent a pointer-to-data member. For a ! data member 'X::m' the 'TYPE_OFFSET_BASETYPE' is 'X' and the ! 'TREE_TYPE' is the type of 'm'. There are variables whose values represent some of the basic types. These include: ! 'void_type_node' ! A node for 'void'. ! 'integer_type_node' ! A node for 'int'. ! 'unsigned_type_node.' ! A node for 'unsigned int'. ! 'char_type_node.' ! A node for 'char'. ! It may sometimes be useful to compare one of these variables with a type ! in hand, using 'same_type_p'.  File: gccint.info, Node: Declarations, Next: Attributes, Prev: Types, Up: GENERIC --- 8021,8272 ---- are often multiple nodes corresponding to the same type. For the most part, different kinds of types have different tree codes. ! (For example, pointer types use a `POINTER_TYPE' code while arrays use ! an `ARRAY_TYPE' code.) However, pointers to member functions use the ! `RECORD_TYPE' code. Therefore, when writing a `switch' statement that depends on the code associated with a particular type, you should take ! care to handle pointers to member functions under the `RECORD_TYPE' ! case label. The following functions and macros deal with cv-qualification of types: ! `TYPE_MAIN_VARIANT' This macro returns the unqualified version of a type. It may be applied to an unqualified type, but it is not always the identity function in that case. A few other macros and functions are usable with all types: ! `TYPE_SIZE' The number of bits required to represent the type, represented as ! an `INTEGER_CST'. For an incomplete type, `TYPE_SIZE' will be ! `NULL_TREE'. ! `TYPE_ALIGN' ! The alignment of the type, in bits, represented as an `int'. ! `TYPE_NAME' ! This macro returns a declaration (in the form of a `TYPE_DECL') for ! the type. (Note this macro does _not_ return an ! `IDENTIFIER_NODE', as you might expect, given its name!) You can ! look at the `DECL_NAME' of the `TYPE_DECL' to obtain the actual ! name of the type. The `TYPE_NAME' will be `NULL_TREE' for a type ! that is not a built-in type, the result of a typedef, or a named ! class type. ! `TYPE_CANONICAL' This macro returns the "canonical" type for the given type node. Canonical types are used to improve performance in the C++ and Objective-C++ front ends by allowing efficient comparison between ! two type nodes in `same_type_p': if the `TYPE_CANONICAL' values of the types are equal, the types are equivalent; otherwise, the types ! are not equivalent. The notion of equivalence for canonical types is the same as the notion of type equivalence in the language ! itself. For instance, ! When `TYPE_CANONICAL' is `NULL_TREE', there is no canonical type ! for the given type node. In this case, comparison between this type and any other type requires the compiler to perform a deep, "structural" comparison to see if the two type nodes have the same form and properties. The canonical type for a node is always the most fundamental type ! in the equivalence class of types. For instance, `int' is its own ! canonical type. A typedef `I' of `int' will have `int' as its ! canonical type. Similarly, `I*' and a typedef `IP' (defined to ! `I*') will has `int*' as their canonical type. When building a new ! type node, be sure to set `TYPE_CANONICAL' to the appropriate ! canonical type. If the new type is a compound type (built from other types), and any of those other types require structural ! equality, use `SET_TYPE_STRUCTURAL_EQUALITY' to ensure that the ! new type also requires structural equality. Finally, if for some ! reason you cannot guarantee that `TYPE_CANONICAL' will point to ! the canonical type, use `SET_TYPE_STRUCTURAL_EQUALITY' to make ! sure that the new type-and any type constructed based on ! it-requires structural equality. If you suspect that the canonical ! type system is miscomparing types, pass `--param ! verify-canonical-types=1' to the compiler or configure with ! `--enable-checking' to force the compiler to verify its ! canonical-type comparisons against the structural comparisons; the ! compiler will then print any warnings if the canonical types ! miscompare. ! `TYPE_STRUCTURAL_EQUALITY_P' This predicate holds when the node requires structural equality ! checks, e.g., when `TYPE_CANONICAL' is `NULL_TREE'. ! `SET_TYPE_STRUCTURAL_EQUALITY' This macro states that the type node it is given requires ! structural equality checks, e.g., it sets `TYPE_CANONICAL' to ! `NULL_TREE'. ! `same_type_p' This predicate takes two types as input, and holds if they are the ! same type. For example, if one type is a `typedef' for the other, ! or both are `typedef's for the same type. This predicate also holds if the two trees given as input are simply copies of one another; i.e., there is no difference between them at the source level, but, for whatever reason, a duplicate has been made in the ! representation. You should never use `==' (pointer equality) to ! compare types; always use `same_type_p' instead. Detailed below are the various kinds of types, and the macros that can be used to access them. Although other kinds of types are used elsewhere in G++, the types described here are the only ones that you will encounter while examining the intermediate representation. ! `VOID_TYPE' ! Used to represent the `void' type. ! `INTEGER_TYPE' ! Used to represent the various integral types, including `char', ! `short', `int', `long', and `long long'. This code is not used ! for enumeration types, nor for the `bool' type. The ! `TYPE_PRECISION' is the number of bits used in the representation, ! represented as an `unsigned int'. (Note that in the general case ! this is not the same value as `TYPE_SIZE'; suppose that there were ! a 24-bit integer type, but that alignment requirements for the ABI ! required 32-bit alignment. Then, `TYPE_SIZE' would be an ! `INTEGER_CST' for 32, while `TYPE_PRECISION' would be 24.) The ! integer type is unsigned if `TYPE_UNSIGNED' holds; otherwise, it ! is signed. ! The `TYPE_MIN_VALUE' is an `INTEGER_CST' for the smallest integer that may be represented by this type. Similarly, the ! `TYPE_MAX_VALUE' is an `INTEGER_CST' for the largest integer that may be represented by this type. ! `REAL_TYPE' ! Used to represent the `float', `double', and `long double' types. ! The number of bits in the floating-point representation is given ! by `TYPE_PRECISION', as in the `INTEGER_TYPE' case. ! `FIXED_POINT_TYPE' ! Used to represent the `short _Fract', `_Fract', `long _Fract', ! `long long _Fract', `short _Accum', `_Accum', `long _Accum', and ! `long long _Accum' types. The number of bits in the fixed-point ! representation is given by `TYPE_PRECISION', as in the ! `INTEGER_TYPE' case. There may be padding bits, fractional bits and integral bits. The number of fractional bits is given by ! `TYPE_FBIT', and the number of integral bits is given by ! `TYPE_IBIT'. The fixed-point type is unsigned if `TYPE_UNSIGNED' ! holds; otherwise, it is signed. The fixed-point type is ! saturating if `TYPE_SATURATING' holds; otherwise, it is not ! saturating. ! `COMPLEX_TYPE' ! Used to represent GCC built-in `__complex__' data types. The ! `TREE_TYPE' is the type of the real and imaginary parts. ! `ENUMERAL_TYPE' ! Used to represent an enumeration type. The `TYPE_PRECISION' gives ! (as an `int'), the number of bits used to represent the type. If ! there are no negative enumeration constants, `TYPE_UNSIGNED' will hold. The minimum and maximum enumeration constants may be ! obtained with `TYPE_MIN_VALUE' and `TYPE_MAX_VALUE', respectively; ! each of these macros returns an `INTEGER_CST'. The actual enumeration constants themselves may be obtained by ! looking at the `TYPE_VALUES'. This macro will return a ! `TREE_LIST', containing the constants. The `TREE_PURPOSE' of each ! node will be an `IDENTIFIER_NODE' giving the name of the constant; ! the `TREE_VALUE' will be an `INTEGER_CST' giving the value ! assigned to that constant. These constants will appear in the ! order in which they were declared. The `TREE_TYPE' of each of ! these constants will be the type of enumeration type itself. ! `BOOLEAN_TYPE' ! Used to represent the `bool' type. ! `POINTER_TYPE' Used to represent pointer types, and pointer to data member types. ! The `TREE_TYPE' gives the type to which this type points. ! `REFERENCE_TYPE' ! Used to represent reference types. The `TREE_TYPE' gives the type to which this type refers. ! `FUNCTION_TYPE' Used to represent the type of non-member functions and of static ! member functions. The `TREE_TYPE' gives the return type of the ! function. The `TYPE_ARG_TYPES' are a `TREE_LIST' of the argument ! types. The `TREE_VALUE' of each node in this list is the type of ! the corresponding argument; the `TREE_PURPOSE' is an expression ! for the default argument value, if any. If the last node in the ! list is `void_list_node' (a `TREE_LIST' node whose `TREE_VALUE' is ! the `void_type_node'), then functions of this type do not take ! variable arguments. Otherwise, they do take a variable number of ! arguments. ! Note that in C (but not in C++) a function declared like `void f()' is an unprototyped function taking a variable number of arguments; ! the `TYPE_ARG_TYPES' of such a function will be `NULL'. ! `METHOD_TYPE' Used to represent the type of a non-static member function. Like a ! `FUNCTION_TYPE', the return type is given by the `TREE_TYPE'. The ! type of `*this', i.e., the class of which functions of this type ! are a member, is given by the `TYPE_METHOD_BASETYPE'. The ! `TYPE_ARG_TYPES' is the parameter list, as for a `FUNCTION_TYPE', ! and includes the `this' argument. ! `ARRAY_TYPE' ! Used to represent array types. The `TREE_TYPE' gives the type of the elements in the array. If the array-bound is present in the ! type, the `TYPE_DOMAIN' is an `INTEGER_TYPE' whose ! `TYPE_MIN_VALUE' and `TYPE_MAX_VALUE' will be the lower and upper ! bounds of the array, respectively. The `TYPE_MIN_VALUE' will ! always be an `INTEGER_CST' for zero, while the `TYPE_MAX_VALUE' ! will be one less than the number of elements in the array, i.e., ! the highest value which may be used to index an element in the ! array. ! `RECORD_TYPE' ! Used to represent `struct' and `class' types, as well as pointers to member functions and similar constructs in other languages. ! `TYPE_FIELDS' contains the items contained in this type, each of ! which can be a `FIELD_DECL', `VAR_DECL', `CONST_DECL', or ! `TYPE_DECL'. You may not make any assumptions about the ordering of the fields in the type or whether one or more of them overlap. ! `UNION_TYPE' ! Used to represent `union' types. Similar to `RECORD_TYPE' except ! that all `FIELD_DECL' nodes in `TYPE_FIELD' start at bit position zero. ! `QUAL_UNION_TYPE' Used to represent part of a variant record in Ada. Similar to ! `UNION_TYPE' except that each `FIELD_DECL' has a `DECL_QUALIFIER' field, which contains a boolean expression that indicates whether the field is present in the object. The type will only have one ! field, so each field's `DECL_QUALIFIER' is only evaluated if none ! of the expressions in the previous fields in `TYPE_FIELDS' are nonzero. Normally these expressions will reference a field in the ! outer object using a `PLACEHOLDER_EXPR'. ! `LANG_TYPE' This node is used to represent a language-specific type. The front end must handle it. ! `OFFSET_TYPE' This node is used to represent a pointer-to-data member. For a ! data member `X::m' the `TYPE_OFFSET_BASETYPE' is `X' and the ! `TREE_TYPE' is the type of `m'. ! There are variables whose values represent some of the basic types. These include: ! `void_type_node' ! A node for `void'. ! `integer_type_node' ! A node for `int'. ! `unsigned_type_node.' ! A node for `unsigned int'. ! `char_type_node.' ! A node for `char'. ! It may sometimes be useful to compare one of these variables with a ! type in hand, using `same_type_p'.  File: gccint.info, Node: Declarations, Next: Attributes, Prev: Types, Up: GENERIC *************** File: gccint.info, Node: Declarations, *** 8112,8118 **** This section covers the various kinds of declarations that appear in the internal representation, except for declarations of functions ! (represented by 'FUNCTION_DECL' nodes), which are described in *note Functions::. * Menu: --- 8276,8282 ---- This section covers the various kinds of declarations that appear in the internal representation, except for declarations of functions ! (represented by `FUNCTION_DECL' nodes), which are described in *note Functions::. * Menu: *************** File: gccint.info, Node: Working with d *** 8128,8250 **** -------------------------------- Some macros can be used with any kind of declaration. These include: ! 'DECL_NAME' ! This macro returns an 'IDENTIFIER_NODE' giving the name of the entity. ! 'TREE_TYPE' This macro returns the type of the entity declared. ! 'EXPR_FILENAME' This macro returns the name of the file in which the entity was ! declared, as a 'char*'. For an entity declared implicitly by the ! compiler (like '__builtin_memcpy'), this will be the string ! '""'. ! 'EXPR_LINENO' This macro returns the line number at which the entity was ! declared, as an 'int'. ! 'DECL_ARTIFICIAL' ! This predicate holds if the declaration was implicitly generated by ! the compiler. For example, this predicate will hold of an ! implicitly declared member function, or of the 'TYPE_DECL' implicitly generated for a class type. Recall that in C++ code like: struct S {}; is roughly equivalent to C code like: struct S {}; typedef struct S S; ! The implicitly generated 'typedef' declaration is represented by a ! 'TYPE_DECL' for which 'DECL_ARTIFICIAL' holds. The various kinds of declarations include: ! 'LABEL_DECL' These nodes are used to represent labels in function bodies. For more information, see *note Functions::. These nodes only appear in block scopes. ! 'CONST_DECL' ! These nodes are used to represent enumeration constants. The value ! of the constant is given by 'DECL_INITIAL' which will be an ! 'INTEGER_CST' with the same type as the 'TREE_TYPE' of the ! 'CONST_DECL', i.e., an 'ENUMERAL_TYPE'. ! 'RESULT_DECL' These nodes represent the value returned by a function. When a ! value is assigned to a 'RESULT_DECL', that indicates that the value ! should be returned, via bitwise copy, by the function. You can use ! 'DECL_SIZE' and 'DECL_ALIGN' on a 'RESULT_DECL', just as with a ! 'VAR_DECL'. ! 'TYPE_DECL' ! These nodes represent 'typedef' declarations. The 'TREE_TYPE' is ! the type declared to have the name given by 'DECL_NAME'. In some cases, there is no associated name. ! 'VAR_DECL' These nodes represent variables with namespace or block scope, as ! well as static data members. The 'DECL_SIZE' and 'DECL_ALIGN' are ! analogous to 'TYPE_SIZE' and 'TYPE_ALIGN'. For a declaration, you ! should always use the 'DECL_SIZE' and 'DECL_ALIGN' rather than the ! 'TYPE_SIZE' and 'TYPE_ALIGN' given by the 'TREE_TYPE', since ! special attributes may have been applied to the variable to give it ! a particular size and alignment. You may use the predicates ! 'DECL_THIS_STATIC' or 'DECL_THIS_EXTERN' to test whether the ! storage class specifiers 'static' or 'extern' were used to declare a variable. If this variable is initialized (but does not require a ! constructor), the 'DECL_INITIAL' will be an expression for the initializer. The initializer should be evaluated, and a bitwise ! copy into the variable performed. If the 'DECL_INITIAL' is the ! 'error_mark_node', there is an initializer, but it is given by an explicit statement later in the code; no bitwise copy is required. GCC provides an extension that allows either automatic variables, or global variables, to be placed in particular registers. This ! extension is being used for a particular 'VAR_DECL' if ! 'DECL_REGISTER' holds for the 'VAR_DECL', and if ! 'DECL_ASSEMBLER_NAME' is not equal to 'DECL_NAME'. In that case, ! 'DECL_ASSEMBLER_NAME' is the name of the register into which the variable will be placed. ! 'PARM_DECL' Used to represent a parameter to a function. Treat these nodes ! similarly to 'VAR_DECL' nodes. These nodes only appear in the ! 'DECL_ARGUMENTS' for a 'FUNCTION_DECL'. ! The 'DECL_ARG_TYPE' for a 'PARM_DECL' is the type that will actually be used when a value is passed to this function. It may ! be a wider type than the 'TREE_TYPE' of the parameter; for example, ! the ordinary type might be 'short' while the 'DECL_ARG_TYPE' is ! 'int'. ! 'DEBUG_EXPR_DECL' Used to represent an anonymous debug-information temporary created to hold an expression as it is optimized away, so that its value can be referenced in debug bind statements. ! 'FIELD_DECL' ! These nodes represent non-static data members. The 'DECL_SIZE' and ! 'DECL_ALIGN' behave as for 'VAR_DECL' nodes. The position of the field within the parent record is specified by a combination of ! three attributes. 'DECL_FIELD_OFFSET' is the position, counting in ! bytes, of the 'DECL_OFFSET_ALIGN'-bit sized word containing the bit ! of the field closest to the beginning of the structure. ! 'DECL_FIELD_BIT_OFFSET' is the bit offset of the first bit of the field within this word; this may be nonzero even for fields that ! are not bit-fields, since 'DECL_OFFSET_ALIGN' may be greater than the natural alignment of the field's type. ! If 'DECL_C_BIT_FIELD' holds, this field is a bit-field. In a ! bit-field, 'DECL_BIT_FIELD_TYPE' also contains the type that was ! originally specified for it, while DECL_TYPE may be a modified type ! with lesser precision, according to the size of the bit field. ! 'NAMESPACE_DECL' Namespaces provide a name hierarchy for other declarations. They ! appear in the 'DECL_CONTEXT' of other '_DECL' nodes.  File: gccint.info, Node: Internal structure, Prev: Working with declarations, Up: Declarations --- 8292,8416 ---- -------------------------------- Some macros can be used with any kind of declaration. These include: ! `DECL_NAME' ! This macro returns an `IDENTIFIER_NODE' giving the name of the entity. ! `TREE_TYPE' This macro returns the type of the entity declared. ! `EXPR_FILENAME' This macro returns the name of the file in which the entity was ! declared, as a `char*'. For an entity declared implicitly by the ! compiler (like `__builtin_memcpy'), this will be the string ! `""'. ! `EXPR_LINENO' This macro returns the line number at which the entity was ! declared, as an `int'. ! `DECL_ARTIFICIAL' ! This predicate holds if the declaration was implicitly generated ! by the compiler. For example, this predicate will hold of an ! implicitly declared member function, or of the `TYPE_DECL' implicitly generated for a class type. Recall that in C++ code like: struct S {}; is roughly equivalent to C code like: struct S {}; typedef struct S S; ! The implicitly generated `typedef' declaration is represented by a ! `TYPE_DECL' for which `DECL_ARTIFICIAL' holds. ! The various kinds of declarations include: ! `LABEL_DECL' These nodes are used to represent labels in function bodies. For more information, see *note Functions::. These nodes only appear in block scopes. ! `CONST_DECL' ! These nodes are used to represent enumeration constants. The ! value of the constant is given by `DECL_INITIAL' which will be an ! `INTEGER_CST' with the same type as the `TREE_TYPE' of the ! `CONST_DECL', i.e., an `ENUMERAL_TYPE'. ! `RESULT_DECL' These nodes represent the value returned by a function. When a ! value is assigned to a `RESULT_DECL', that indicates that the ! value should be returned, via bitwise copy, by the function. You ! can use `DECL_SIZE' and `DECL_ALIGN' on a `RESULT_DECL', just as ! with a `VAR_DECL'. ! `TYPE_DECL' ! These nodes represent `typedef' declarations. The `TREE_TYPE' is ! the type declared to have the name given by `DECL_NAME'. In some cases, there is no associated name. ! `VAR_DECL' These nodes represent variables with namespace or block scope, as ! well as static data members. The `DECL_SIZE' and `DECL_ALIGN' are ! analogous to `TYPE_SIZE' and `TYPE_ALIGN'. For a declaration, you ! should always use the `DECL_SIZE' and `DECL_ALIGN' rather than the ! `TYPE_SIZE' and `TYPE_ALIGN' given by the `TREE_TYPE', since ! special attributes may have been applied to the variable to give ! it a particular size and alignment. You may use the predicates ! `DECL_THIS_STATIC' or `DECL_THIS_EXTERN' to test whether the ! storage class specifiers `static' or `extern' were used to declare a variable. If this variable is initialized (but does not require a ! constructor), the `DECL_INITIAL' will be an expression for the initializer. The initializer should be evaluated, and a bitwise ! copy into the variable performed. If the `DECL_INITIAL' is the ! `error_mark_node', there is an initializer, but it is given by an explicit statement later in the code; no bitwise copy is required. GCC provides an extension that allows either automatic variables, or global variables, to be placed in particular registers. This ! extension is being used for a particular `VAR_DECL' if ! `DECL_REGISTER' holds for the `VAR_DECL', and if ! `DECL_ASSEMBLER_NAME' is not equal to `DECL_NAME'. In that case, ! `DECL_ASSEMBLER_NAME' is the name of the register into which the variable will be placed. ! `PARM_DECL' Used to represent a parameter to a function. Treat these nodes ! similarly to `VAR_DECL' nodes. These nodes only appear in the ! `DECL_ARGUMENTS' for a `FUNCTION_DECL'. ! The `DECL_ARG_TYPE' for a `PARM_DECL' is the type that will actually be used when a value is passed to this function. It may ! be a wider type than the `TREE_TYPE' of the parameter; for ! example, the ordinary type might be `short' while the ! `DECL_ARG_TYPE' is `int'. ! `DEBUG_EXPR_DECL' Used to represent an anonymous debug-information temporary created to hold an expression as it is optimized away, so that its value can be referenced in debug bind statements. ! `FIELD_DECL' ! These nodes represent non-static data members. The `DECL_SIZE' and ! `DECL_ALIGN' behave as for `VAR_DECL' nodes. The position of the field within the parent record is specified by a combination of ! three attributes. `DECL_FIELD_OFFSET' is the position, counting ! in bytes, of the `DECL_OFFSET_ALIGN'-bit sized word containing the ! bit of the field closest to the beginning of the structure. ! `DECL_FIELD_BIT_OFFSET' is the bit offset of the first bit of the field within this word; this may be nonzero even for fields that ! are not bit-fields, since `DECL_OFFSET_ALIGN' may be greater than the natural alignment of the field's type. ! If `DECL_C_BIT_FIELD' holds, this field is a bit-field. In a ! bit-field, `DECL_BIT_FIELD_TYPE' also contains the type that was ! originally specified for it, while DECL_TYPE may be a modified ! type with lesser precision, according to the size of the bit field. ! `NAMESPACE_DECL' Namespaces provide a name hierarchy for other declarations. They ! appear in the `DECL_CONTEXT' of other `_DECL' nodes. !  File: gccint.info, Node: Internal structure, Prev: Working with declarations, Up: Declarations *************** File: gccint.info, Node: Internal struc *** 8252,8258 **** 10.4.2 Internal structure ------------------------- ! 'DECL' nodes are represented internally as a hierarchy of structures. * Menu: --- 8418,8424 ---- 10.4.2 Internal structure ------------------------- ! `DECL' nodes are represented internally as a hierarchy of structures. * Menu: *************** File: gccint.info, Node: Current struct *** 8267,8323 **** 10.4.2.1 Current structure hierarchy .................................... ! 'struct tree_decl_minimal' This is the minimal structure to inherit from in order for common ! 'DECL' macros to work. The fields it contains are a unique ID, source location, context, and name. ! 'struct tree_decl_common' ! This structure inherits from 'struct tree_decl_minimal'. It ! contains fields that most 'DECL' nodes need, such as a field to store alignment, machine mode, size, and attributes. ! 'struct tree_field_decl' ! This structure inherits from 'struct tree_decl_common'. It is used ! to represent 'FIELD_DECL'. ! 'struct tree_label_decl' ! This structure inherits from 'struct tree_decl_common'. It is used ! to represent 'LABEL_DECL'. ! 'struct tree_translation_unit_decl' ! This structure inherits from 'struct tree_decl_common'. It is used ! to represent 'TRANSLATION_UNIT_DECL'. ! 'struct tree_decl_with_rtl' ! This structure inherits from 'struct tree_decl_common'. It contains a field to store the low-level RTL associated with a ! 'DECL' node. ! 'struct tree_result_decl' ! This structure inherits from 'struct tree_decl_with_rtl'. It is ! used to represent 'RESULT_DECL'. ! 'struct tree_const_decl' ! This structure inherits from 'struct tree_decl_with_rtl'. It is ! used to represent 'CONST_DECL'. ! 'struct tree_parm_decl' ! This structure inherits from 'struct tree_decl_with_rtl'. It is ! used to represent 'PARM_DECL'. ! 'struct tree_decl_with_vis' ! This structure inherits from 'struct tree_decl_with_rtl'. It contains fields necessary to store visibility information, as well as a section name and assembler name. ! 'struct tree_var_decl' ! This structure inherits from 'struct tree_decl_with_vis'. It is ! used to represent 'VAR_DECL'. - 'struct tree_function_decl' - This structure inherits from 'struct tree_decl_with_vis'. It is - used to represent 'FUNCTION_DECL'.  File: gccint.info, Node: Adding new DECL node types, Prev: Current structure hierarchy, Up: Internal structure --- 8433,8490 ---- 10.4.2.1 Current structure hierarchy .................................... ! `struct tree_decl_minimal' This is the minimal structure to inherit from in order for common ! `DECL' macros to work. The fields it contains are a unique ID, source location, context, and name. ! `struct tree_decl_common' ! This structure inherits from `struct tree_decl_minimal'. It ! contains fields that most `DECL' nodes need, such as a field to store alignment, machine mode, size, and attributes. ! `struct tree_field_decl' ! This structure inherits from `struct tree_decl_common'. It is ! used to represent `FIELD_DECL'. ! `struct tree_label_decl' ! This structure inherits from `struct tree_decl_common'. It is ! used to represent `LABEL_DECL'. ! `struct tree_translation_unit_decl' ! This structure inherits from `struct tree_decl_common'. It is ! used to represent `TRANSLATION_UNIT_DECL'. ! `struct tree_decl_with_rtl' ! This structure inherits from `struct tree_decl_common'. It contains a field to store the low-level RTL associated with a ! `DECL' node. ! `struct tree_result_decl' ! This structure inherits from `struct tree_decl_with_rtl'. It is ! used to represent `RESULT_DECL'. ! `struct tree_const_decl' ! This structure inherits from `struct tree_decl_with_rtl'. It is ! used to represent `CONST_DECL'. ! `struct tree_parm_decl' ! This structure inherits from `struct tree_decl_with_rtl'. It is ! used to represent `PARM_DECL'. ! `struct tree_decl_with_vis' ! This structure inherits from `struct tree_decl_with_rtl'. It contains fields necessary to store visibility information, as well as a section name and assembler name. ! `struct tree_var_decl' ! This structure inherits from `struct tree_decl_with_vis'. It is ! used to represent `VAR_DECL'. ! ! `struct tree_function_decl' ! This structure inherits from `struct tree_decl_with_vis'. It is ! used to represent `FUNCTION_DECL'.  File: gccint.info, Node: Adding new DECL node types, Prev: Current structure hierarchy, Up: Internal structure *************** File: gccint.info, Node: Adding new DEC *** 8325,8401 **** 10.4.2.2 Adding new DECL node types ................................... ! Adding a new 'DECL' tree consists of the following steps ! Add a new tree code for the 'DECL' node ! For language specific 'DECL' nodes, there is a '.def' file in each ! frontend directory where the tree code should be added. For 'DECL' ! nodes that are part of the middle-end, the code should be added to ! 'tree.def'. ! Create a new structure type for the 'DECL' node ! These structures should inherit from one of the existing structures ! in the language hierarchy by using that structure as the first ! member. struct tree_foo_decl { struct tree_decl_with_vis common; } ! Would create a structure name 'tree_foo_decl' that inherits from ! 'struct tree_decl_with_vis'. ! For language specific 'DECL' nodes, this new structure type should ! go in the appropriate '.h' file. For 'DECL' nodes that are part of ! the middle-end, the structure type should go in 'tree.h'. Add a member to the tree structure enumerator for the node ! For garbage collection and dynamic checking purposes, each 'DECL' node structure type is required to have a unique enumerator value ! specified with it. For language specific 'DECL' nodes, this new ! enumerator value should go in the appropriate '.def' file. For ! 'DECL' nodes that are part of the middle-end, the enumerator values ! are specified in 'treestruct.def'. ! Update 'union tree_node' In order to make your new structure type usable, it must be added ! to 'union tree_node'. For language specific 'DECL' nodes, a new ! entry should be added to the appropriate '.h' file of the form struct tree_foo_decl GTY ((tag ("TS_VAR_DECL"))) foo_decl; ! For 'DECL' nodes that are part of the middle-end, the additional ! member goes directly into 'union tree_node' in 'tree.h'. Update dynamic checking info In order to be able to check whether accessing a named portion of ! 'union tree_node' is legal, and whether a certain 'DECL' node ! contains one of the enumerated 'DECL' node structures in the hierarchy, a simple lookup table is used. This lookup table needs to be kept up to date with the tree structure hierarchy, or else checking and containment macros will fail inappropriately. ! For language specific 'DECL' nodes, their is an 'init_ts' function ! in an appropriate '.c' file, which initializes the lookup table. ! Code setting up the table for new 'DECL' nodes should be added ! there. For each 'DECL' tree code and enumerator value representing ! a member of the inheritance hierarchy, the table should contain 1 ! if that tree code inherits (directly or indirectly) from that ! member. Thus, a 'FOO_DECL' node derived from 'struct ! decl_with_rtl', and enumerator value 'TS_FOO_DECL', would be set up ! as follows tree_contains_struct[FOO_DECL][TS_FOO_DECL] = 1; tree_contains_struct[FOO_DECL][TS_DECL_WRTL] = 1; tree_contains_struct[FOO_DECL][TS_DECL_COMMON] = 1; tree_contains_struct[FOO_DECL][TS_DECL_MINIMAL] = 1; ! For 'DECL' nodes that are part of the middle-end, the setup code ! goes into 'tree.c'. Add macros to access any new fields and flags - Each added field or flag should have a macro that is used to access it, that performs appropriate checking to ensure only the right ! type of 'DECL' nodes access the field. These macros generally take the following form #define FOO_DECL_FIELDNAME(NODE) FOO_DECL_CHECK(NODE)->foo_decl.fieldname --- 8492,8567 ---- 10.4.2.2 Adding new DECL node types ................................... ! Adding a new `DECL' tree consists of the following steps ! Add a new tree code for the `DECL' node ! For language specific `DECL' nodes, there is a `.def' file in each ! frontend directory where the tree code should be added. For ! `DECL' nodes that are part of the middle-end, the code should be ! added to `tree.def'. ! Create a new structure type for the `DECL' node ! These structures should inherit from one of the existing ! structures in the language hierarchy by using that structure as ! the first member. struct tree_foo_decl { struct tree_decl_with_vis common; } ! Would create a structure name `tree_foo_decl' that inherits from ! `struct tree_decl_with_vis'. ! For language specific `DECL' nodes, this new structure type should ! go in the appropriate `.h' file. For `DECL' nodes that are part ! of the middle-end, the structure type should go in `tree.h'. Add a member to the tree structure enumerator for the node ! For garbage collection and dynamic checking purposes, each `DECL' node structure type is required to have a unique enumerator value ! specified with it. For language specific `DECL' nodes, this new ! enumerator value should go in the appropriate `.def' file. For ! `DECL' nodes that are part of the middle-end, the enumerator ! values are specified in `treestruct.def'. ! Update `union tree_node' In order to make your new structure type usable, it must be added ! to `union tree_node'. For language specific `DECL' nodes, a new ! entry should be added to the appropriate `.h' file of the form struct tree_foo_decl GTY ((tag ("TS_VAR_DECL"))) foo_decl; ! For `DECL' nodes that are part of the middle-end, the additional ! member goes directly into `union tree_node' in `tree.h'. Update dynamic checking info In order to be able to check whether accessing a named portion of ! `union tree_node' is legal, and whether a certain `DECL' node ! contains one of the enumerated `DECL' node structures in the hierarchy, a simple lookup table is used. This lookup table needs to be kept up to date with the tree structure hierarchy, or else checking and containment macros will fail inappropriately. ! For language specific `DECL' nodes, their is an `init_ts' function ! in an appropriate `.c' file, which initializes the lookup table. ! Code setting up the table for new `DECL' nodes should be added ! there. For each `DECL' tree code and enumerator value ! representing a member of the inheritance hierarchy, the table ! should contain 1 if that tree code inherits (directly or ! indirectly) from that member. Thus, a `FOO_DECL' node derived ! from `struct decl_with_rtl', and enumerator value `TS_FOO_DECL', ! would be set up as follows tree_contains_struct[FOO_DECL][TS_FOO_DECL] = 1; tree_contains_struct[FOO_DECL][TS_DECL_WRTL] = 1; tree_contains_struct[FOO_DECL][TS_DECL_COMMON] = 1; tree_contains_struct[FOO_DECL][TS_DECL_MINIMAL] = 1; ! For `DECL' nodes that are part of the middle-end, the setup code ! goes into `tree.c'. Add macros to access any new fields and flags Each added field or flag should have a macro that is used to access it, that performs appropriate checking to ensure only the right ! type of `DECL' nodes access the field. These macros generally take the following form #define FOO_DECL_FIELDNAME(NODE) FOO_DECL_CHECK(NODE)->foo_decl.fieldname *************** Add macros to access any new fields and *** 8405,8413 **** #define BASE_STRUCT_FIELDNAME(NODE) \ (BASE_STRUCT_CHECK(NODE)->base_struct.fieldname ! Reading them from the generated 'all-tree.def' file (which in turn ! includes all the 'tree.def' files), 'gencheck.c' is used during ! GCC's build to generate the '*_CHECK' macros for all tree codes.  File: gccint.info, Node: Attributes, Next: Expression trees, Prev: Declarations, Up: GENERIC --- 8571,8580 ---- #define BASE_STRUCT_FIELDNAME(NODE) \ (BASE_STRUCT_CHECK(NODE)->base_struct.fieldname ! Reading them from the generated `all-tree.def' file (which in turn ! includes all the `tree.def' files), `gencheck.c' is used during ! GCC's build to generate the `*_CHECK' macros for all tree codes. !  File: gccint.info, Node: Attributes, Next: Expression trees, Prev: Declarations, Up: GENERIC *************** File: gccint.info, Node: Attributes, N *** 8415,8429 **** 10.5 Attributes in trees ======================== ! Attributes, as specified using the '__attribute__' keyword, are ! represented internally as a 'TREE_LIST'. The 'TREE_PURPOSE' is the name ! of the attribute, as an 'IDENTIFIER_NODE'. The 'TREE_VALUE' is a ! 'TREE_LIST' of the arguments of the attribute, if any, or 'NULL_TREE' if ! there are no arguments; the arguments are stored as the 'TREE_VALUE' of ! successive entries in the list, and may be identifiers or expressions. ! The 'TREE_CHAIN' of the attribute is the next attribute in a list of ! attributes applying to the same declaration or type, or 'NULL_TREE' if ! there are no further attributes in the list. Attributes may be attached to declarations and to types; these attributes may be accessed with the following macros. All attributes --- 8582,8596 ---- 10.5 Attributes in trees ======================== ! Attributes, as specified using the `__attribute__' keyword, are ! represented internally as a `TREE_LIST'. The `TREE_PURPOSE' is the ! name of the attribute, as an `IDENTIFIER_NODE'. The `TREE_VALUE' is a ! `TREE_LIST' of the arguments of the attribute, if any, or `NULL_TREE' ! if there are no arguments; the arguments are stored as the `TREE_VALUE' ! of successive entries in the list, and may be identifiers or ! expressions. The `TREE_CHAIN' of the attribute is the next attribute ! in a list of attributes applying to the same declaration or type, or ! `NULL_TREE' if there are no further attributes in the list. Attributes may be attached to declarations and to types; these attributes may be accessed with the following macros. All attributes *************** mind. In particular, the expression "tr *** 8448,8465 **** acyclic graph. (For example there may be many references to the integer constant zero throughout the source program; many of these will be represented by the same expression node.) You should not rely on ! certain kinds of node being shared, nor should you rely on certain kinds ! of nodes being unshared. The following macros can be used with all expression nodes: ! 'TREE_TYPE' Returns the type of the expression. This value may not be precisely the same type that would be given the expression in the original program. In what follows, some nodes that one might expect to always have type ! 'bool' are documented to have either integral or boolean type. At some point in the future, the C front end may also make use of this same intermediate representation, and at this point these nodes will certainly have integral type. The previous sentence is not meant to --- 8615,8632 ---- acyclic graph. (For example there may be many references to the integer constant zero throughout the source program; many of these will be represented by the same expression node.) You should not rely on ! certain kinds of node being shared, nor should you rely on certain ! kinds of nodes being unshared. The following macros can be used with all expression nodes: ! `TREE_TYPE' Returns the type of the expression. This value may not be precisely the same type that would be given the expression in the original program. In what follows, some nodes that one might expect to always have type ! `bool' are documented to have either integral or boolean type. At some point in the future, the C front end may also make use of this same intermediate representation, and at this point these nodes will certainly have integral type. The previous sentence is not meant to *************** integral type. *** 8468,8478 **** Below, we list the various kinds of expression nodes. Except where noted otherwise, the operands to an expression are accessed using the ! 'TREE_OPERAND' macro. For example, to access the first operand to a ! binary plus expression 'expr', use: TREE_OPERAND (expr, 0) - As this example indicates, the operands are zero-indexed. * Menu: --- 8635,8644 ---- Below, we list the various kinds of expression nodes. Except where noted otherwise, the operands to an expression are accessed using the ! `TREE_OPERAND' macro. For example, to access the first operand to a ! binary plus expression `expr', use: TREE_OPERAND (expr, 0) As this example indicates, the operands are zero-indexed. * Menu: *************** The table below begins with constants, m *** 8492,8566 **** then proceeds to binary expressions, and concludes with various other kinds of expressions: ! 'INTEGER_CST' These nodes represent integer constants. Note that the type of ! these constants is obtained with 'TREE_TYPE'; they are not always ! of type 'int'. In particular, 'char' constants are represented ! with 'INTEGER_CST' nodes. The value of the integer constant 'e' is ! represented in an array of HOST_WIDE_INT. There are enough elements ! in the array to represent the value without taking extra elements ! for redundant 0s or -1. The number of elements used to represent ! 'e' is available via 'TREE_INT_CST_NUNITS'. Element 'i' can be ! extracted by using 'TREE_INT_CST_ELT (e, i)'. 'TREE_INT_CST_LOW' ! is a shorthand for 'TREE_INT_CST_ELT (e, 0)'. ! ! The functions 'tree_fits_shwi_p' and 'tree_fits_uhwi_p' can be used ! to tell if the value is small enough to fit in a signed ! HOST_WIDE_INT or an unsigned HOST_WIDE_INT respectively. The value ! can then be extracted using 'tree_to_shwi' and 'tree_to_uhwi'. ! 'REAL_CST' FIXME: Talk about how to obtain representations of this constant, do comparisons, and so forth. ! 'FIXED_CST' ! These nodes represent fixed-point constants. The type of these ! constants is obtained with 'TREE_TYPE'. 'TREE_FIXED_CST_PTR' ! points to a 'struct fixed_value'; 'TREE_FIXED_CST' returns the ! structure itself. 'struct fixed_value' contains 'data' with the ! size of two 'HOST_BITS_PER_WIDE_INT' and 'mode' as the associated ! fixed-point machine mode for 'data'. ! 'COMPLEX_CST' ! These nodes are used to represent complex number constants, that is ! a '__complex__' whose parts are constant nodes. The ! 'TREE_REALPART' and 'TREE_IMAGPART' return the real and the imaginary parts respectively. ! 'VECTOR_CST' These nodes are used to represent vector constants, whose parts are ! constant nodes. Each individual constant node is either an integer ! or a double constant node. The first operand is a 'TREE_LIST' of ! the constant nodes and is accessed through 'TREE_VECTOR_CST_ELTS'. ! 'STRING_CST' ! These nodes represent string-constants. The 'TREE_STRING_LENGTH' ! returns the length of the string, as an 'int'. The ! 'TREE_STRING_POINTER' is a 'char*' containing the string itself. ! The string may not be 'NUL'-terminated, and it may contain embedded ! 'NUL' characters. Therefore, the 'TREE_STRING_LENGTH' includes the ! trailing 'NUL' if it is present. ! For wide string constants, the 'TREE_STRING_LENGTH' is the number ! of bytes in the string, and the 'TREE_STRING_POINTER' points to an array of the bytes of the string, as represented on the target system (that is, as integers in the target endianness). Wide and ! non-wide string constants are distinguished only by the 'TREE_TYPE' ! of the 'STRING_CST'. FIXME: The formats of string constants are not well-defined when the target system bytes are not the same width as host system bytes.  File: gccint.info, Node: Storage References, Next: Unary and Binary Expressions, Prev: Constant expressions, Up: Expression trees 10.6.2 References to storage ---------------------------- ! 'ARRAY_REF' These nodes represent array accesses. The first operand is the array; the second is the index. To calculate the address of the memory accessed, you must scale the index by the size of the type --- 8658,8733 ---- then proceeds to binary expressions, and concludes with various other kinds of expressions: ! `INTEGER_CST' These nodes represent integer constants. Note that the type of ! these constants is obtained with `TREE_TYPE'; they are not always ! of type `int'. In particular, `char' constants are represented ! with `INTEGER_CST' nodes. The value of the integer constant `e' is ! represented in an array of HOST_WIDE_INT. There are enough ! elements in the array to represent the value without taking extra ! elements for redundant 0s or -1. The number of elements used to ! represent `e' is available via `TREE_INT_CST_NUNITS'. Element `i' ! can be extracted by using `TREE_INT_CST_ELT (e, i)'. ! `TREE_INT_CST_LOW' is a shorthand for `TREE_INT_CST_ELT (e, 0)'. ! The functions `tree_fits_shwi_p' and `tree_fits_uhwi_p' can be ! used to tell if the value is small enough to fit in a signed ! HOST_WIDE_INT or an unsigned HOST_WIDE_INT respectively. The ! value can then be extracted using `tree_to_shwi' and ! `tree_to_uhwi'. + `REAL_CST' FIXME: Talk about how to obtain representations of this constant, do comparisons, and so forth. ! `FIXED_CST' These nodes represent fixed-point constants. The type of these ! constants is obtained with `TREE_TYPE'. `TREE_FIXED_CST_PTR' ! points to a `struct fixed_value'; `TREE_FIXED_CST' returns the ! structure itself. `struct fixed_value' contains `data' with the ! size of two `HOST_BITS_PER_WIDE_INT' and `mode' as the associated ! fixed-point machine mode for `data'. ! `COMPLEX_CST' ! These nodes are used to represent complex number constants, that ! is a `__complex__' whose parts are constant nodes. The ! `TREE_REALPART' and `TREE_IMAGPART' return the real and the imaginary parts respectively. ! `VECTOR_CST' These nodes are used to represent vector constants, whose parts are ! constant nodes. Each individual constant node is either an ! integer or a double constant node. The first operand is a ! `TREE_LIST' of the constant nodes and is accessed through ! `TREE_VECTOR_CST_ELTS'. ! `STRING_CST' ! These nodes represent string-constants. The `TREE_STRING_LENGTH' ! returns the length of the string, as an `int'. The ! `TREE_STRING_POINTER' is a `char*' containing the string itself. ! The string may not be `NUL'-terminated, and it may contain ! embedded `NUL' characters. Therefore, the `TREE_STRING_LENGTH' ! includes the trailing `NUL' if it is present. ! For wide string constants, the `TREE_STRING_LENGTH' is the number ! of bytes in the string, and the `TREE_STRING_POINTER' points to an array of the bytes of the string, as represented on the target system (that is, as integers in the target endianness). Wide and ! non-wide string constants are distinguished only by the `TREE_TYPE' ! of the `STRING_CST'. FIXME: The formats of string constants are not well-defined when the target system bytes are not the same width as host system bytes. +  File: gccint.info, Node: Storage References, Next: Unary and Binary Expressions, Prev: Constant expressions, Up: Expression trees 10.6.2 References to storage ---------------------------- ! `ARRAY_REF' These nodes represent array accesses. The first operand is the array; the second is the index. To calculate the address of the memory accessed, you must scale the index by the size of the type *************** File: gccint.info, Node: Storage Refere *** 8568,8631 **** type of a component of the array. The third and fourth operands are used after gimplification to represent the lower bound and component size but should not be used directly; call ! 'array_ref_low_bound' and 'array_ref_element_size' instead. ! 'ARRAY_RANGE_REF' These nodes represent access to a range (or "slice") of an array. ! The operands are the same as that for 'ARRAY_REF' and have the same meanings. The type of these expressions must be an array whose ! component type is the same as that of the first operand. The range ! of that array type determines the amount of data these expressions ! access. ! 'TARGET_MEM_REF' These nodes represent memory accesses whose address directly map to an addressing mode of the target architecture. The first argument ! is 'TMR_SYMBOL' and must be a 'VAR_DECL' of an object with a fixed ! address. The second argument is 'TMR_BASE' and the third one is ! 'TMR_INDEX'. The fourth argument is 'TMR_STEP' and must be an ! 'INTEGER_CST'. The fifth argument is 'TMR_OFFSET' and must be an ! 'INTEGER_CST'. Any of the arguments may be NULL if the appropriate ! component does not appear in the address. Address of the ! 'TARGET_MEM_REF' is determined in the following way. &TMR_SYMBOL + TMR_BASE + TMR_INDEX * TMR_STEP + TMR_OFFSET The sixth argument is the reference to the original memory access, ! which is preserved for the purposes of the RTL alias analysis. The ! seventh argument is a tag representing the results of tree level ! alias analysis. ! 'ADDR_EXPR' These nodes are used to represent the address of an object. (These expressions will always have pointer or reference type.) The operand may be another expression, or it may be a declaration. As an extension, GCC allows users to take the address of a label. ! In this case, the operand of the 'ADDR_EXPR' will be a ! 'LABEL_DECL'. The type of such an expression is 'void*'. If the object addressed is not an lvalue, a temporary is created, and the address of the temporary is used. ! 'INDIRECT_REF' These nodes are used to represent the object pointed to by a pointer. The operand is the pointer being dereferenced; it will always have pointer or reference type. ! 'MEM_REF' These nodes are used to represent the object pointed to by a pointer offset by a constant. The first operand is the pointer being dereferenced; it will always have pointer or reference type. The second operand is a pointer constant. Its type is specifying the type to be used for type-based alias analysis. ! 'COMPONENT_REF' These nodes represent non-static data member accesses. The first operand is the object (rather than a pointer to it); the second ! operand is the 'FIELD_DECL' for the data member. The third operand ! represents the byte offset of the field, but should not be used ! directly; call 'component_ref_field_offset' instead.  File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: Storage References, Up: Expression trees --- 8735,8799 ---- type of a component of the array. The third and fourth operands are used after gimplification to represent the lower bound and component size but should not be used directly; call ! `array_ref_low_bound' and `array_ref_element_size' instead. ! `ARRAY_RANGE_REF' These nodes represent access to a range (or "slice") of an array. ! The operands are the same as that for `ARRAY_REF' and have the same meanings. The type of these expressions must be an array whose ! component type is the same as that of the first operand. The ! range of that array type determines the amount of data these ! expressions access. ! `TARGET_MEM_REF' These nodes represent memory accesses whose address directly map to an addressing mode of the target architecture. The first argument ! is `TMR_SYMBOL' and must be a `VAR_DECL' of an object with a fixed ! address. The second argument is `TMR_BASE' and the third one is ! `TMR_INDEX'. The fourth argument is `TMR_STEP' and must be an ! `INTEGER_CST'. The fifth argument is `TMR_OFFSET' and must be an ! `INTEGER_CST'. Any of the arguments may be NULL if the ! appropriate component does not appear in the address. Address of ! the `TARGET_MEM_REF' is determined in the following way. &TMR_SYMBOL + TMR_BASE + TMR_INDEX * TMR_STEP + TMR_OFFSET The sixth argument is the reference to the original memory access, ! which is preserved for the purposes of the RTL alias analysis. ! The seventh argument is a tag representing the results of tree ! level alias analysis. ! `ADDR_EXPR' These nodes are used to represent the address of an object. (These expressions will always have pointer or reference type.) The operand may be another expression, or it may be a declaration. As an extension, GCC allows users to take the address of a label. ! In this case, the operand of the `ADDR_EXPR' will be a ! `LABEL_DECL'. The type of such an expression is `void*'. If the object addressed is not an lvalue, a temporary is created, and the address of the temporary is used. ! `INDIRECT_REF' These nodes are used to represent the object pointed to by a pointer. The operand is the pointer being dereferenced; it will always have pointer or reference type. ! `MEM_REF' These nodes are used to represent the object pointed to by a pointer offset by a constant. The first operand is the pointer being dereferenced; it will always have pointer or reference type. The second operand is a pointer constant. Its type is specifying the type to be used for type-based alias analysis. ! `COMPONENT_REF' These nodes represent non-static data member accesses. The first operand is the object (rather than a pointer to it); the second ! operand is the `FIELD_DECL' for the data member. The third ! operand represents the byte offset of the field, but should not be ! used directly; call `component_ref_field_offset' instead. !  File: gccint.info, Node: Unary and Binary Expressions, Next: Vectors, Prev: Storage References, Up: Expression trees *************** File: gccint.info, Node: Unary and Bina *** 8633,8792 **** 10.6.3 Unary and Binary Expressions ----------------------------------- ! 'NEGATE_EXPR' These nodes represent unary negation of the single operand, for both integer and floating-point types. The type of negation can be determined by looking at the type of the expression. The behavior of this operation on signed arithmetic overflow is ! controlled by the 'flag_wrapv' and 'flag_trapv' variables. ! 'ABS_EXPR' These nodes represent the absolute value of the single operand, for both integer and floating-point types. This is typically used to ! implement the 'abs', 'labs' and 'llabs' builtins for integer types, ! and the 'fabs', 'fabsf' and 'fabsl' builtins for floating point ! types. The type of abs operation can be determined by looking at ! the type of the expression. This node is not used for complex types. To represent the modulus ! or complex abs of a complex value, use the 'BUILT_IN_CABS', ! 'BUILT_IN_CABSF' or 'BUILT_IN_CABSL' builtins, as used to implement ! the C99 'cabs', 'cabsf' and 'cabsl' built-in functions. ! 'BIT_NOT_EXPR' These nodes represent bitwise complement, and will always have integral type. The only operand is the value to be complemented. ! 'TRUTH_NOT_EXPR' These nodes represent logical negation, and will always have integral (or boolean) type. The operand is the value being ! negated. The type of the operand and that of the result are always ! of 'BOOLEAN_TYPE' or 'INTEGER_TYPE'. ! 'PREDECREMENT_EXPR' ! 'PREINCREMENT_EXPR' ! 'POSTDECREMENT_EXPR' ! 'POSTINCREMENT_EXPR' These nodes represent increment and decrement expressions. The value of the single operand is computed, and the operand ! incremented or decremented. In the case of 'PREDECREMENT_EXPR' and ! 'PREINCREMENT_EXPR', the value of the expression is the value resulting after the increment or decrement; in the case of ! 'POSTDECREMENT_EXPR' and 'POSTINCREMENT_EXPR' is the value before the increment or decrement occurs. The type of the operand, like that of the result, will be either integral, boolean, or floating-point. ! 'FIX_TRUNC_EXPR' These nodes represent conversion of a floating-point value to an integer. The single operand will have a floating-point type, while the complete expression will have an integral (or boolean) type. The operand is rounded towards zero. ! 'FLOAT_EXPR' These nodes represent conversion of an integral (or boolean) value to a floating-point value. The single operand will have integral type, while the complete expression will have a floating-point type. FIXME: How is the operand supposed to be rounded? Is this ! dependent on '-mieee'? ! 'COMPLEX_EXPR' These nodes are used to represent complex numbers constructed from two expressions of the same (integer or real) type. The first operand is the real part and the second operand is the imaginary part. ! 'CONJ_EXPR' These nodes represent the conjugate of their operand. ! 'REALPART_EXPR' ! 'IMAGPART_EXPR' These nodes represent respectively the real and the imaginary parts of complex numbers (their sole argument). ! 'NON_LVALUE_EXPR' These nodes indicate that their one and only operand is not an lvalue. A back end can treat these identically to the single operand. ! 'NOP_EXPR' These nodes are used to represent conversions that do not require ! any code-generation. For example, conversion of a 'char*' to an ! 'int*' does not require any code be generated; such a conversion is ! represented by a 'NOP_EXPR'. The single operand is the expression to be converted. The conversion from a pointer to a reference is ! also represented with a 'NOP_EXPR'. ! 'CONVERT_EXPR' ! These nodes are similar to 'NOP_EXPR's, but are used in those situations where code may need to be generated. For example, if an ! 'int*' is converted to an 'int' code may need to be generated on some platforms. These nodes are never used for C++-specific ! conversions, like conversions between pointers to different classes ! in an inheritance hierarchy. Any adjustments that need to be made ! in such cases are always indicated explicitly. Similarly, a ! user-defined conversion is never represented by a 'CONVERT_EXPR'; ! instead, the function calls are made explicit. ! 'FIXED_CONVERT_EXPR' These nodes are used to represent conversions that involve fixed-point values. For example, from a fixed-point value to another fixed-point value, from an integer to a fixed-point value, ! from a fixed-point value to an integer, from a floating-point value ! to a fixed-point value, or from a fixed-point value to a floating-point value. ! 'LSHIFT_EXPR' ! 'RSHIFT_EXPR' These nodes represent left and right shifts, respectively. The first operand is the value to shift; it will always be of integral type. The second operand is an expression for the number of bits by which to shift. Right shift should be treated as arithmetic, ! i.e., the high-order bits should be zero-filled when the expression ! has unsigned type and filled with the sign bit when the expression ! has signed type. Note that the result is undefined if the second ! operand is larger than or equal to the first operand's type size. ! Unlike most nodes, these can have a vector as first operand and a ! scalar as second operand. ! 'BIT_IOR_EXPR' ! 'BIT_XOR_EXPR' ! 'BIT_AND_EXPR' These nodes represent bitwise inclusive or, bitwise exclusive or, and bitwise and, respectively. Both operands will always have integral type. ! 'TRUTH_ANDIF_EXPR' ! 'TRUTH_ORIF_EXPR' These nodes represent logical "and" and logical "or", respectively. These operators are not strict; i.e., the second operand is evaluated only if the value of the expression is not determined by ! evaluation of the first operand. The type of the operands and that ! of the result are always of 'BOOLEAN_TYPE' or 'INTEGER_TYPE'. ! 'TRUTH_AND_EXPR' ! 'TRUTH_OR_EXPR' ! 'TRUTH_XOR_EXPR' These nodes represent logical and, logical or, and logical exclusive or. They are strict; both arguments are always evaluated. There are no corresponding operators in C or C++, but the front end will sometimes generate these expressions anyhow, if it can tell that strictness does not matter. The type of the ! operands and that of the result are always of 'BOOLEAN_TYPE' or ! 'INTEGER_TYPE'. ! 'POINTER_PLUS_EXPR' This node represents pointer arithmetic. The first operand is always a pointer/reference type. The second operand is always an unsigned integer type compatible with sizetype. This is the only binary arithmetic operand that can operate on pointer types. ! 'PLUS_EXPR' ! 'MINUS_EXPR' ! 'MULT_EXPR' These nodes represent various binary arithmetic operations. Respectively, these operations are addition, subtraction (of the second operand from the first) and multiplication. Their operands --- 8801,8960 ---- 10.6.3 Unary and Binary Expressions ----------------------------------- ! `NEGATE_EXPR' These nodes represent unary negation of the single operand, for both integer and floating-point types. The type of negation can be determined by looking at the type of the expression. The behavior of this operation on signed arithmetic overflow is ! controlled by the `flag_wrapv' and `flag_trapv' variables. ! `ABS_EXPR' These nodes represent the absolute value of the single operand, for both integer and floating-point types. This is typically used to ! implement the `abs', `labs' and `llabs' builtins for integer ! types, and the `fabs', `fabsf' and `fabsl' builtins for floating ! point types. The type of abs operation can be determined by ! looking at the type of the expression. This node is not used for complex types. To represent the modulus ! or complex abs of a complex value, use the `BUILT_IN_CABS', ! `BUILT_IN_CABSF' or `BUILT_IN_CABSL' builtins, as used to ! implement the C99 `cabs', `cabsf' and `cabsl' built-in functions. ! `BIT_NOT_EXPR' These nodes represent bitwise complement, and will always have integral type. The only operand is the value to be complemented. ! `TRUTH_NOT_EXPR' These nodes represent logical negation, and will always have integral (or boolean) type. The operand is the value being ! negated. The type of the operand and that of the result are ! always of `BOOLEAN_TYPE' or `INTEGER_TYPE'. ! `PREDECREMENT_EXPR' ! `PREINCREMENT_EXPR' ! `POSTDECREMENT_EXPR' ! `POSTINCREMENT_EXPR' These nodes represent increment and decrement expressions. The value of the single operand is computed, and the operand ! incremented or decremented. In the case of `PREDECREMENT_EXPR' and ! `PREINCREMENT_EXPR', the value of the expression is the value resulting after the increment or decrement; in the case of ! `POSTDECREMENT_EXPR' and `POSTINCREMENT_EXPR' is the value before the increment or decrement occurs. The type of the operand, like that of the result, will be either integral, boolean, or floating-point. ! `FIX_TRUNC_EXPR' These nodes represent conversion of a floating-point value to an integer. The single operand will have a floating-point type, while the complete expression will have an integral (or boolean) type. The operand is rounded towards zero. ! `FLOAT_EXPR' These nodes represent conversion of an integral (or boolean) value to a floating-point value. The single operand will have integral type, while the complete expression will have a floating-point type. FIXME: How is the operand supposed to be rounded? Is this ! dependent on `-mieee'? ! `COMPLEX_EXPR' These nodes are used to represent complex numbers constructed from two expressions of the same (integer or real) type. The first operand is the real part and the second operand is the imaginary part. ! `CONJ_EXPR' These nodes represent the conjugate of their operand. ! `REALPART_EXPR' ! `IMAGPART_EXPR' These nodes represent respectively the real and the imaginary parts of complex numbers (their sole argument). ! `NON_LVALUE_EXPR' These nodes indicate that their one and only operand is not an lvalue. A back end can treat these identically to the single operand. ! `NOP_EXPR' These nodes are used to represent conversions that do not require ! any code-generation. For example, conversion of a `char*' to an ! `int*' does not require any code be generated; such a conversion is ! represented by a `NOP_EXPR'. The single operand is the expression to be converted. The conversion from a pointer to a reference is ! also represented with a `NOP_EXPR'. ! `CONVERT_EXPR' ! These nodes are similar to `NOP_EXPR's, but are used in those situations where code may need to be generated. For example, if an ! `int*' is converted to an `int' code may need to be generated on some platforms. These nodes are never used for C++-specific ! conversions, like conversions between pointers to different ! classes in an inheritance hierarchy. Any adjustments that need to ! be made in such cases are always indicated explicitly. Similarly, ! a user-defined conversion is never represented by a ! `CONVERT_EXPR'; instead, the function calls are made explicit. ! `FIXED_CONVERT_EXPR' These nodes are used to represent conversions that involve fixed-point values. For example, from a fixed-point value to another fixed-point value, from an integer to a fixed-point value, ! from a fixed-point value to an integer, from a floating-point ! value to a fixed-point value, or from a fixed-point value to a floating-point value. ! `LSHIFT_EXPR' ! `RSHIFT_EXPR' These nodes represent left and right shifts, respectively. The first operand is the value to shift; it will always be of integral type. The second operand is an expression for the number of bits by which to shift. Right shift should be treated as arithmetic, ! i.e., the high-order bits should be zero-filled when the ! expression has unsigned type and filled with the sign bit when the ! expression has signed type. Note that the result is undefined if ! the second operand is larger than or equal to the first operand's ! type size. Unlike most nodes, these can have a vector as first ! operand and a scalar as second operand. ! `BIT_IOR_EXPR' ! `BIT_XOR_EXPR' ! `BIT_AND_EXPR' These nodes represent bitwise inclusive or, bitwise exclusive or, and bitwise and, respectively. Both operands will always have integral type. ! `TRUTH_ANDIF_EXPR' ! `TRUTH_ORIF_EXPR' These nodes represent logical "and" and logical "or", respectively. These operators are not strict; i.e., the second operand is evaluated only if the value of the expression is not determined by ! evaluation of the first operand. The type of the operands and ! that of the result are always of `BOOLEAN_TYPE' or `INTEGER_TYPE'. ! `TRUTH_AND_EXPR' ! `TRUTH_OR_EXPR' ! `TRUTH_XOR_EXPR' These nodes represent logical and, logical or, and logical exclusive or. They are strict; both arguments are always evaluated. There are no corresponding operators in C or C++, but the front end will sometimes generate these expressions anyhow, if it can tell that strictness does not matter. The type of the ! operands and that of the result are always of `BOOLEAN_TYPE' or ! `INTEGER_TYPE'. ! `POINTER_PLUS_EXPR' This node represents pointer arithmetic. The first operand is always a pointer/reference type. The second operand is always an unsigned integer type compatible with sizetype. This is the only binary arithmetic operand that can operate on pointer types. ! `PLUS_EXPR' ! `MINUS_EXPR' ! `MULT_EXPR' These nodes represent various binary arithmetic operations. Respectively, these operations are addition, subtraction (of the second operand from the first) and multiplication. Their operands *************** File: gccint.info, Node: Unary and Bina *** 8795,8868 **** integral type. The behavior of these operations on signed arithmetic overflow is ! controlled by the 'flag_wrapv' and 'flag_trapv' variables. ! 'MULT_HIGHPART_EXPR' This node represents the "high-part" of a widening multiplication. For an integral type with B bits of precision, the result is the most significant B bits of the full 2B product. ! 'RDIV_EXPR' This node represents a floating point division operation. ! 'TRUNC_DIV_EXPR' ! 'FLOOR_DIV_EXPR' ! 'CEIL_DIV_EXPR' ! 'ROUND_DIV_EXPR' These nodes represent integer division operations that return an ! integer result. 'TRUNC_DIV_EXPR' rounds towards zero, ! 'FLOOR_DIV_EXPR' rounds towards negative infinity, 'CEIL_DIV_EXPR' ! rounds towards positive infinity and 'ROUND_DIV_EXPR' rounds to the ! closest integer. Integer division in C and C++ is truncating, i.e. ! 'TRUNC_DIV_EXPR'. The behavior of these operations on signed arithmetic overflow, when dividing the minimum signed integer by minus one, is ! controlled by the 'flag_wrapv' and 'flag_trapv' variables. ! 'TRUNC_MOD_EXPR' ! 'FLOOR_MOD_EXPR' ! 'CEIL_MOD_EXPR' ! 'ROUND_MOD_EXPR' These nodes represent the integer remainder or modulus operation. ! The integer modulus of two operands 'a' and 'b' is defined as 'a - (a/b)*b' where the division calculated using the corresponding ! division operator. Hence for 'TRUNC_MOD_EXPR' this definition assumes division using truncation towards zero, i.e. ! 'TRUNC_DIV_EXPR'. Integer remainder in C and C++ uses truncating ! division, i.e. 'TRUNC_MOD_EXPR'. ! 'EXACT_DIV_EXPR' ! The 'EXACT_DIV_EXPR' code is used to represent integer divisions where the numerator is known to be an exact multiple of the denominator. This allows the backend to choose between the faster ! of 'TRUNC_DIV_EXPR', 'CEIL_DIV_EXPR' and 'FLOOR_DIV_EXPR' for the current target. ! 'LT_EXPR' ! 'LE_EXPR' ! 'GT_EXPR' ! 'GE_EXPR' ! 'EQ_EXPR' ! 'NE_EXPR' These nodes represent the less than, less than or equal to, greater than, greater than or equal to, equal, and not equal comparison operators. The first and second operands will either be both of integral type, both of floating type or both of vector type. The result type of these expressions will always be of integral, boolean or signed integral vector type. These operations return ! the result type's zero value for false, the result type's one value ! for true, and a vector whose elements are zero (false) or minus one ! (true) for vectors. For floating point comparisons, if we honor IEEE NaNs and either ! operand is NaN, then 'NE_EXPR' always returns true and the remaining operators always return false. On some targets, comparisons against an IEEE NaN, other than equality and inequality, may generate a floating point exception. ! 'ORDERED_EXPR' ! 'UNORDERED_EXPR' These nodes represent non-trapping ordered and unordered comparison operators. These operations take two floating point operands and determine whether they are ordered or unordered relative to each --- 8963,9036 ---- integral type. The behavior of these operations on signed arithmetic overflow is ! controlled by the `flag_wrapv' and `flag_trapv' variables. ! `MULT_HIGHPART_EXPR' This node represents the "high-part" of a widening multiplication. For an integral type with B bits of precision, the result is the most significant B bits of the full 2B product. ! `RDIV_EXPR' This node represents a floating point division operation. ! `TRUNC_DIV_EXPR' ! `FLOOR_DIV_EXPR' ! `CEIL_DIV_EXPR' ! `ROUND_DIV_EXPR' These nodes represent integer division operations that return an ! integer result. `TRUNC_DIV_EXPR' rounds towards zero, ! `FLOOR_DIV_EXPR' rounds towards negative infinity, `CEIL_DIV_EXPR' ! rounds towards positive infinity and `ROUND_DIV_EXPR' rounds to ! the closest integer. Integer division in C and C++ is truncating, ! i.e. `TRUNC_DIV_EXPR'. The behavior of these operations on signed arithmetic overflow, when dividing the minimum signed integer by minus one, is ! controlled by the `flag_wrapv' and `flag_trapv' variables. ! `TRUNC_MOD_EXPR' ! `FLOOR_MOD_EXPR' ! `CEIL_MOD_EXPR' ! `ROUND_MOD_EXPR' These nodes represent the integer remainder or modulus operation. ! The integer modulus of two operands `a' and `b' is defined as `a - (a/b)*b' where the division calculated using the corresponding ! division operator. Hence for `TRUNC_MOD_EXPR' this definition assumes division using truncation towards zero, i.e. ! `TRUNC_DIV_EXPR'. Integer remainder in C and C++ uses truncating ! division, i.e. `TRUNC_MOD_EXPR'. ! `EXACT_DIV_EXPR' ! The `EXACT_DIV_EXPR' code is used to represent integer divisions where the numerator is known to be an exact multiple of the denominator. This allows the backend to choose between the faster ! of `TRUNC_DIV_EXPR', `CEIL_DIV_EXPR' and `FLOOR_DIV_EXPR' for the current target. ! `LT_EXPR' ! `LE_EXPR' ! `GT_EXPR' ! `GE_EXPR' ! `EQ_EXPR' ! `NE_EXPR' These nodes represent the less than, less than or equal to, greater than, greater than or equal to, equal, and not equal comparison operators. The first and second operands will either be both of integral type, both of floating type or both of vector type. The result type of these expressions will always be of integral, boolean or signed integral vector type. These operations return ! the result type's zero value for false, the result type's one ! value for true, and a vector whose elements are zero (false) or ! minus one (true) for vectors. For floating point comparisons, if we honor IEEE NaNs and either ! operand is NaN, then `NE_EXPR' always returns true and the remaining operators always return false. On some targets, comparisons against an IEEE NaN, other than equality and inequality, may generate a floating point exception. ! `ORDERED_EXPR' ! `UNORDERED_EXPR' These nodes represent non-trapping ordered and unordered comparison operators. These operations take two floating point operands and determine whether they are ordered or unordered relative to each *************** File: gccint.info, Node: Unary and Bina *** 8873,8922 **** type's zero value for false, and the result type's one value for true. ! 'UNLT_EXPR' ! 'UNLE_EXPR' ! 'UNGT_EXPR' ! 'UNGE_EXPR' ! 'UNEQ_EXPR' ! 'LTGT_EXPR' These nodes represent the unordered comparison operators. These operations take two floating point operands and determine whether the operands are unordered or are less than, less than or equal to, greater than, greater than or equal to, or equal respectively. For ! example, 'UNLT_EXPR' returns true if either operand is an IEEE NaN or the first operand is less than the second. With the possible ! exception of 'LTGT_EXPR', all of these operations are guaranteed not to generate a floating point exception. The result type of these expressions will always be of integral or boolean type. ! These operations return the result type's zero value for false, and ! the result type's one value for true. ! 'MODIFY_EXPR' These nodes represent assignment. The left-hand side is the first operand; the right-hand side is the second operand. The left-hand ! side will be a 'VAR_DECL', 'INDIRECT_REF', 'COMPONENT_REF', or other lvalue. ! These nodes are used to represent not only assignment with '=' but ! also compound assignments (like '+='), by reduction to '=' ! assignment. In other words, the representation for 'i += 3' looks ! just like that for 'i = i + 3'. ! 'INIT_EXPR' ! These nodes are just like 'MODIFY_EXPR', but are used only when a variable is initialized, rather than assigned to subsequently. ! This means that we can assume that the target of the initialization ! is not used in computing its own value; any reference to the lhs in ! computing the rhs is undefined. ! 'COMPOUND_EXPR' These nodes represent comma-expressions. The first operand is an expression whose value is computed and thrown away prior to the evaluation of the second operand. The value of the entire expression is the value of the second operand. ! 'COND_EXPR' ! These nodes represent '?:' expressions. The first operand is of boolean or integral type. If it evaluates to a nonzero value, the second operand should be evaluated, and returned as the value of the expression. Otherwise, the third operand is evaluated, and --- 9041,9090 ---- type's zero value for false, and the result type's one value for true. ! `UNLT_EXPR' ! `UNLE_EXPR' ! `UNGT_EXPR' ! `UNGE_EXPR' ! `UNEQ_EXPR' ! `LTGT_EXPR' These nodes represent the unordered comparison operators. These operations take two floating point operands and determine whether the operands are unordered or are less than, less than or equal to, greater than, greater than or equal to, or equal respectively. For ! example, `UNLT_EXPR' returns true if either operand is an IEEE NaN or the first operand is less than the second. With the possible ! exception of `LTGT_EXPR', all of these operations are guaranteed not to generate a floating point exception. The result type of these expressions will always be of integral or boolean type. ! These operations return the result type's zero value for false, ! and the result type's one value for true. ! `MODIFY_EXPR' These nodes represent assignment. The left-hand side is the first operand; the right-hand side is the second operand. The left-hand ! side will be a `VAR_DECL', `INDIRECT_REF', `COMPONENT_REF', or other lvalue. ! These nodes are used to represent not only assignment with `=' but ! also compound assignments (like `+='), by reduction to `=' ! assignment. In other words, the representation for `i += 3' looks ! just like that for `i = i + 3'. ! `INIT_EXPR' ! These nodes are just like `MODIFY_EXPR', but are used only when a variable is initialized, rather than assigned to subsequently. ! This means that we can assume that the target of the ! initialization is not used in computing its own value; any ! reference to the lhs in computing the rhs is undefined. ! `COMPOUND_EXPR' These nodes represent comma-expressions. The first operand is an expression whose value is computed and thrown away prior to the evaluation of the second operand. The value of the entire expression is the value of the second operand. ! `COND_EXPR' ! These nodes represent `?:' expressions. The first operand is of boolean or integral type. If it evaluates to a nonzero value, the second operand should be evaluated, and returned as the value of the expression. Otherwise, the third operand is evaluated, and *************** File: gccint.info, Node: Unary and Bina *** 8926,8957 **** expression, unless it unconditionally throws an exception or calls a noreturn function, in which case it should have void type. The same constraints apply to the third operand. This allows array ! bounds checks to be represented conveniently as '(i >= 0 && i < 10) ! ? i : abort()'. As a GNU extension, the C language front-ends allow the second ! operand of the '?:' operator may be omitted in the source. For ! example, 'x ? : 3' is equivalent to 'x ? x : 3', assuming that 'x' ! is an expression without side-effects. In the tree representation, ! however, the second operand is always present, possibly protected ! by 'SAVE_EXPR' if the first argument does cause side-effects. ! 'CALL_EXPR' These nodes are used to represent calls to functions, including ! non-static member functions. 'CALL_EXPR's are implemented as expression nodes with a variable number of operands. Rather than ! using 'TREE_OPERAND' to extract them, it is preferable to use the ! specialized accessor macros and functions that operate specifically ! on 'CALL_EXPR' nodes. ! 'CALL_EXPR_FN' returns a pointer to the function to call; it is ! always an expression whose type is a 'POINTER_TYPE'. The number of arguments to the call is returned by ! 'call_expr_nargs', while the arguments themselves can be accessed ! with the 'CALL_EXPR_ARG' macro. The arguments are zero-indexed and ! numbered left-to-right. You can iterate over the arguments using ! 'FOR_EACH_CALL_EXPR_ARG', as in: tree call, arg; call_expr_arg_iterator iter; --- 9094,9126 ---- expression, unless it unconditionally throws an exception or calls a noreturn function, in which case it should have void type. The same constraints apply to the third operand. This allows array ! bounds checks to be represented conveniently as `(i >= 0 && i < ! 10) ? i : abort()'. As a GNU extension, the C language front-ends allow the second ! operand of the `?:' operator may be omitted in the source. For ! example, `x ? : 3' is equivalent to `x ? x : 3', assuming that `x' ! is an expression without side-effects. In the tree ! representation, however, the second operand is always present, ! possibly protected by `SAVE_EXPR' if the first argument does cause ! side-effects. ! `CALL_EXPR' These nodes are used to represent calls to functions, including ! non-static member functions. `CALL_EXPR's are implemented as expression nodes with a variable number of operands. Rather than ! using `TREE_OPERAND' to extract them, it is preferable to use the ! specialized accessor macros and functions that operate ! specifically on `CALL_EXPR' nodes. ! `CALL_EXPR_FN' returns a pointer to the function to call; it is ! always an expression whose type is a `POINTER_TYPE'. The number of arguments to the call is returned by ! `call_expr_nargs', while the arguments themselves can be accessed ! with the `CALL_EXPR_ARG' macro. The arguments are zero-indexed ! and numbered left-to-right. You can iterate over the arguments ! using `FOR_EACH_CALL_EXPR_ARG', as in: tree call, arg; call_expr_arg_iterator iter; *************** File: gccint.info, Node: Unary and Bina *** 8960,9063 **** ...; For non-static member functions, there will be an operand ! corresponding to the 'this' pointer. There will always be expressions corresponding to all of the arguments, even if the function is declared with default arguments and some arguments are not explicitly provided at the call sites. ! 'CALL_EXPR's also have a 'CALL_EXPR_STATIC_CHAIN' operand that is used to implement nested functions. This operand is otherwise null. ! 'CLEANUP_POINT_EXPR' These nodes represent full-expressions. The single operand is an expression to evaluate. Any destructor calls engendered by the creation of temporaries during the evaluation of that expression should be performed immediately after the expression is evaluated. ! 'CONSTRUCTOR' These nodes represent the brace-enclosed initializers for a ! structure or an array. They contain a sequence of component values ! made out of a vector of constructor_elt, which is a ('INDEX', ! 'VALUE') pair. ! If the 'TREE_TYPE' of the 'CONSTRUCTOR' is a 'RECORD_TYPE', ! 'UNION_TYPE' or 'QUAL_UNION_TYPE' then the 'INDEX' of each node in ! the sequence will be a 'FIELD_DECL' and the 'VALUE' will be the expression used to initialize that field. ! If the 'TREE_TYPE' of the 'CONSTRUCTOR' is an 'ARRAY_TYPE', then ! the 'INDEX' of each node in the sequence will be an 'INTEGER_CST' ! or a 'RANGE_EXPR' of two 'INTEGER_CST's. A single 'INTEGER_CST' indicates which element of the array is being assigned to. A ! 'RANGE_EXPR' indicates an inclusive range of elements to ! initialize. In both cases the 'VALUE' is the corresponding initializer. It is re-evaluated for each element of a ! 'RANGE_EXPR'. If the 'INDEX' is 'NULL_TREE', then the initializer is for the next available array element. In the front end, you should not depend on the fields appearing in any particular order. However, in the middle end, fields must ! appear in declaration order. You should not assume that all fields ! will be represented. Unrepresented fields will be cleared (zeroed), unless the CONSTRUCTOR_NO_CLEARING flag is set, in which case their value becomes undefined. ! 'COMPOUND_LITERAL_EXPR' These nodes represent ISO C99 compound literals. The ! 'COMPOUND_LITERAL_EXPR_DECL_EXPR' is a 'DECL_EXPR' containing an ! anonymous 'VAR_DECL' for the unnamed object represented by the ! compound literal; the 'DECL_INITIAL' of that 'VAR_DECL' is a ! 'CONSTRUCTOR' representing the brace-enclosed list of initializers ! in the compound literal. That anonymous 'VAR_DECL' can also be ! accessed directly by the 'COMPOUND_LITERAL_EXPR_DECL' macro. ! ! 'SAVE_EXPR' ! A 'SAVE_EXPR' represents an expression (possibly involving side-effects) that is used more than once. The side-effects should occur only the first time the expression is evaluated. Subsequent uses should just reuse the computed value. The first operand to ! the 'SAVE_EXPR' is the expression to evaluate. The side-effects ! should be executed where the 'SAVE_EXPR' is first encountered in a depth-first preorder traversal of the expression tree. ! 'TARGET_EXPR' ! A 'TARGET_EXPR' represents a temporary object. The first operand ! is a 'VAR_DECL' for the temporary variable. The second operand is the initializer for the temporary. The initializer is evaluated and, if non-void, copied (bitwise) into the temporary. If the initializer is void, that means that it will perform the initialization itself. ! Often, a 'TARGET_EXPR' occurs on the right-hand side of an assignment, or as the second operand to a comma-expression which is ! itself the right-hand side of an assignment, etc. In this case, we ! say that the 'TARGET_EXPR' is "normal"; otherwise, we say it is ! "orphaned". For a normal 'TARGET_EXPR' the temporary variable should be treated as an alias for the left-hand side of the assignment, rather than as a new temporary variable. ! The third operand to the 'TARGET_EXPR', if present, is a cleanup-expression (i.e., destructor call) for the temporary. If this expression is orphaned, then this expression must be executed when the statement containing this expression is complete. These cleanups must always be executed in the order opposite to that in which they were encountered. Note that if a temporary is created on one branch of a conditional operator (i.e., in the second or ! third operand to a 'COND_EXPR'), the cleanup must be run only if that branch is actually executed. ! 'VA_ARG_EXPR' This node is used to implement support for the C/C++ variable ! argument-list mechanism. It represents expressions like 'va_arg ! (ap, type)'. Its 'TREE_TYPE' yields the tree representation for ! 'type' and its sole argument yields the representation for 'ap'. ! 'ANNOTATE_EXPR' ! This node is used to attach markers to an expression. The first ! operand is the annotated expression, the second is an 'INTEGER_CST' ! with a value from 'enum annot_expr_kind'.  File: gccint.info, Node: Vectors, Prev: Unary and Binary Expressions, Up: Expression trees --- 9129,9231 ---- ...; For non-static member functions, there will be an operand ! corresponding to the `this' pointer. There will always be expressions corresponding to all of the arguments, even if the function is declared with default arguments and some arguments are not explicitly provided at the call sites. ! `CALL_EXPR's also have a `CALL_EXPR_STATIC_CHAIN' operand that is used to implement nested functions. This operand is otherwise null. ! `CLEANUP_POINT_EXPR' These nodes represent full-expressions. The single operand is an expression to evaluate. Any destructor calls engendered by the creation of temporaries during the evaluation of that expression should be performed immediately after the expression is evaluated. ! `CONSTRUCTOR' These nodes represent the brace-enclosed initializers for a ! structure or an array. They contain a sequence of component ! values made out of a vector of constructor_elt, which is a ! (`INDEX', `VALUE') pair. ! If the `TREE_TYPE' of the `CONSTRUCTOR' is a `RECORD_TYPE', ! `UNION_TYPE' or `QUAL_UNION_TYPE' then the `INDEX' of each node in ! the sequence will be a `FIELD_DECL' and the `VALUE' will be the expression used to initialize that field. ! If the `TREE_TYPE' of the `CONSTRUCTOR' is an `ARRAY_TYPE', then ! the `INDEX' of each node in the sequence will be an `INTEGER_CST' ! or a `RANGE_EXPR' of two `INTEGER_CST's. A single `INTEGER_CST' indicates which element of the array is being assigned to. A ! `RANGE_EXPR' indicates an inclusive range of elements to ! initialize. In both cases the `VALUE' is the corresponding initializer. It is re-evaluated for each element of a ! `RANGE_EXPR'. If the `INDEX' is `NULL_TREE', then the initializer is for the next available array element. In the front end, you should not depend on the fields appearing in any particular order. However, in the middle end, fields must ! appear in declaration order. You should not assume that all ! fields will be represented. Unrepresented fields will be cleared (zeroed), unless the CONSTRUCTOR_NO_CLEARING flag is set, in which case their value becomes undefined. ! `COMPOUND_LITERAL_EXPR' These nodes represent ISO C99 compound literals. The ! `COMPOUND_LITERAL_EXPR_DECL_EXPR' is a `DECL_EXPR' containing an ! anonymous `VAR_DECL' for the unnamed object represented by the ! compound literal; the `DECL_INITIAL' of that `VAR_DECL' is a ! `CONSTRUCTOR' representing the brace-enclosed list of initializers ! in the compound literal. That anonymous `VAR_DECL' can also be ! accessed directly by the `COMPOUND_LITERAL_EXPR_DECL' macro. ! `SAVE_EXPR' ! A `SAVE_EXPR' represents an expression (possibly involving side-effects) that is used more than once. The side-effects should occur only the first time the expression is evaluated. Subsequent uses should just reuse the computed value. The first operand to ! the `SAVE_EXPR' is the expression to evaluate. The side-effects ! should be executed where the `SAVE_EXPR' is first encountered in a depth-first preorder traversal of the expression tree. ! `TARGET_EXPR' ! A `TARGET_EXPR' represents a temporary object. The first operand ! is a `VAR_DECL' for the temporary variable. The second operand is the initializer for the temporary. The initializer is evaluated and, if non-void, copied (bitwise) into the temporary. If the initializer is void, that means that it will perform the initialization itself. ! Often, a `TARGET_EXPR' occurs on the right-hand side of an assignment, or as the second operand to a comma-expression which is ! itself the right-hand side of an assignment, etc. In this case, ! we say that the `TARGET_EXPR' is "normal"; otherwise, we say it is ! "orphaned". For a normal `TARGET_EXPR' the temporary variable should be treated as an alias for the left-hand side of the assignment, rather than as a new temporary variable. ! The third operand to the `TARGET_EXPR', if present, is a cleanup-expression (i.e., destructor call) for the temporary. If this expression is orphaned, then this expression must be executed when the statement containing this expression is complete. These cleanups must always be executed in the order opposite to that in which they were encountered. Note that if a temporary is created on one branch of a conditional operator (i.e., in the second or ! third operand to a `COND_EXPR'), the cleanup must be run only if that branch is actually executed. ! `VA_ARG_EXPR' This node is used to implement support for the C/C++ variable ! argument-list mechanism. It represents expressions like `va_arg ! (ap, type)'. Its `TREE_TYPE' yields the tree representation for ! `type' and its sole argument yields the representation for `ap'. ! `ANNOTATE_EXPR' ! This node is used to attach markers to an expression. The first ! operand is the annotated expression, the second is an ! `INTEGER_CST' with a value from `enum annot_expr_kind'.  File: gccint.info, Node: Vectors, Prev: Unary and Binary Expressions, Up: Expression trees *************** File: gccint.info, Node: Vectors, Prev *** 9065,9072 **** 10.6.4 Vectors -------------- ! 'VEC_LSHIFT_EXPR' ! 'VEC_RSHIFT_EXPR' These nodes represent whole vector left and right shifts, respectively. The first operand is the vector to shift; it will always be of vector type. The second operand is an expression for --- 9233,9240 ---- 10.6.4 Vectors -------------- ! `VEC_LSHIFT_EXPR' ! `VEC_RSHIFT_EXPR' These nodes represent whole vector left and right shifts, respectively. The first operand is the vector to shift; it will always be of vector type. The second operand is an expression for *************** File: gccint.info, Node: Vectors, Prev *** 9074,9126 **** undefined if the second operand is larger than or equal to the first operand's type size. ! 'VEC_WIDEN_MULT_HI_EXPR' ! 'VEC_WIDEN_MULT_LO_EXPR' These nodes represent widening vector multiplication of the high and low parts of the two input vectors, respectively. Their ! operands are vectors that contain the same number of elements ('N') ! of the same integral type. The result is a vector that contains ! half as many elements, of an integral type whose size is twice as ! wide. In the case of 'VEC_WIDEN_MULT_HI_EXPR' the high 'N/2' ! elements of the two vector are multiplied to produce the vector of ! 'N/2' products. In the case of 'VEC_WIDEN_MULT_LO_EXPR' the low ! 'N/2' elements of the two vector are multiplied to produce the ! vector of 'N/2' products. ! 'VEC_UNPACK_HI_EXPR' ! 'VEC_UNPACK_LO_EXPR' These nodes represent unpacking of the high and low parts of the input vector, respectively. The single operand is a vector that ! contains 'N' elements of the same integral or floating point type. The result is a vector that contains half as many elements, of an integral or floating point type whose size is twice as wide. In ! the case of 'VEC_UNPACK_HI_EXPR' the high 'N/2' elements of the vector are extracted and widened (promoted). In the case of ! 'VEC_UNPACK_LO_EXPR' the low 'N/2' elements of the vector are extracted and widened (promoted). ! 'VEC_UNPACK_FLOAT_HI_EXPR' ! 'VEC_UNPACK_FLOAT_LO_EXPR' These nodes represent unpacking of the high and low parts of the input vector, where the values are converted from fixed point to ! floating point. The single operand is a vector that contains 'N' elements of the same integral type. The result is a vector that contains half as many elements of a floating point type whose size ! is twice as wide. In the case of 'VEC_UNPACK_HI_EXPR' the high ! 'N/2' elements of the vector are extracted, converted and widened. ! In the case of 'VEC_UNPACK_LO_EXPR' the low 'N/2' elements of the vector are extracted, converted and widened. ! 'VEC_PACK_TRUNC_EXPR' ! This node represents packing of truncated elements of the two input ! vectors into the output vector. Input operands are vectors that ! contain the same number of elements of the same integral or ! floating point type. The result is a vector that contains twice as ! many elements of an integral or floating point type whose size is ! half as wide. The elements of the two vectors are demoted and merged (concatenated) to form the output vector. ! 'VEC_PACK_SAT_EXPR' This node represents packing of elements of the two input vectors into the output vector using saturation. Input operands are vectors that contain the same number of elements of the same --- 9242,9294 ---- undefined if the second operand is larger than or equal to the first operand's type size. ! `VEC_WIDEN_MULT_HI_EXPR' ! `VEC_WIDEN_MULT_LO_EXPR' These nodes represent widening vector multiplication of the high and low parts of the two input vectors, respectively. Their ! operands are vectors that contain the same number of elements ! (`N') of the same integral type. The result is a vector that ! contains half as many elements, of an integral type whose size is ! twice as wide. In the case of `VEC_WIDEN_MULT_HI_EXPR' the high ! `N/2' elements of the two vector are multiplied to produce the ! vector of `N/2' products. In the case of `VEC_WIDEN_MULT_LO_EXPR' ! the low `N/2' elements of the two vector are multiplied to produce ! the vector of `N/2' products. ! `VEC_UNPACK_HI_EXPR' ! `VEC_UNPACK_LO_EXPR' These nodes represent unpacking of the high and low parts of the input vector, respectively. The single operand is a vector that ! contains `N' elements of the same integral or floating point type. The result is a vector that contains half as many elements, of an integral or floating point type whose size is twice as wide. In ! the case of `VEC_UNPACK_HI_EXPR' the high `N/2' elements of the vector are extracted and widened (promoted). In the case of ! `VEC_UNPACK_LO_EXPR' the low `N/2' elements of the vector are extracted and widened (promoted). ! `VEC_UNPACK_FLOAT_HI_EXPR' ! `VEC_UNPACK_FLOAT_LO_EXPR' These nodes represent unpacking of the high and low parts of the input vector, where the values are converted from fixed point to ! floating point. The single operand is a vector that contains `N' elements of the same integral type. The result is a vector that contains half as many elements of a floating point type whose size ! is twice as wide. In the case of `VEC_UNPACK_HI_EXPR' the high ! `N/2' elements of the vector are extracted, converted and widened. ! In the case of `VEC_UNPACK_LO_EXPR' the low `N/2' elements of the vector are extracted, converted and widened. ! `VEC_PACK_TRUNC_EXPR' ! This node represents packing of truncated elements of the two ! input vectors into the output vector. Input operands are vectors ! that contain the same number of elements of the same integral or ! floating point type. The result is a vector that contains twice ! as many elements of an integral or floating point type whose size ! is half as wide. The elements of the two vectors are demoted and merged (concatenated) to form the output vector. ! `VEC_PACK_SAT_EXPR' This node represents packing of elements of the two input vectors into the output vector using saturation. Input operands are vectors that contain the same number of elements of the same *************** File: gccint.info, Node: Vectors, Prev *** 9129,9135 **** elements of the two vectors are demoted and merged (concatenated) to form the output vector. ! 'VEC_PACK_FIX_TRUNC_EXPR' This node represents packing of elements of the two input vectors into the output vector, where the values are converted from floating point to fixed point. Input operands are vectors that --- 9297,9303 ---- elements of the two vectors are demoted and merged (concatenated) to form the output vector. ! `VEC_PACK_FIX_TRUNC_EXPR' This node represents packing of elements of the two input vectors into the output vector, where the values are converted from floating point to fixed point. Input operands are vectors that *************** File: gccint.info, Node: Vectors, Prev *** 9138,9164 **** integral type whose size is half as wide. The elements of the two vectors are merged (concatenated) to form the output vector. ! 'VEC_COND_EXPR' ! These nodes represent '?:' expressions. The three operands must be vectors of the same size and number of elements. The second and third operands must have the same type as the entire expression. ! The first operand is of signed integral vector type. If an element ! of the first operand evaluates to a zero value, the corresponding ! element of the result is taken from the third operand. If it ! evaluates to a minus one value, it is taken from the second ! operand. It should never evaluate to any other value currently, ! but optimizations should not rely on that property. In contrast ! with a 'COND_EXPR', all operands are always evaluated. ! 'SAD_EXPR' This node represents the Sum of Absolute Differences operation. The three operands must be vectors of integral types. The first ! and second operand must have the same type. The size of the vector ! element of the third operand must be at lease twice of the size of ! the vector element of the first and second one. The SAD is ! calculated between the first and second operands, added to the third operand, and returned.  File: gccint.info, Node: Statements, Next: Functions, Prev: Expression trees, Up: GENERIC --- 9306,9333 ---- integral type whose size is half as wide. The elements of the two vectors are merged (concatenated) to form the output vector. ! `VEC_COND_EXPR' ! These nodes represent `?:' expressions. The three operands must be vectors of the same size and number of elements. The second and third operands must have the same type as the entire expression. ! The first operand is of signed integral vector type. If an ! element of the first operand evaluates to a zero value, the ! corresponding element of the result is taken from the third ! operand. If it evaluates to a minus one value, it is taken from ! the second operand. It should never evaluate to any other value ! currently, but optimizations should not rely on that property. In ! contrast with a `COND_EXPR', all operands are always evaluated. ! `SAD_EXPR' This node represents the Sum of Absolute Differences operation. The three operands must be vectors of integral types. The first ! and second operand must have the same type. The size of the ! vector element of the third operand must be at lease twice of the ! size of the vector element of the first and second one. The SAD ! is calculated between the first and second operands, added to the third operand, and returned. +  File: gccint.info, Node: Statements, Next: Functions, Prev: Expression trees, Up: GENERIC *************** File: gccint.info, Node: Statements, N *** 9166,9173 **** =============== Most statements in GIMPLE are assignment statements, represented by ! 'GIMPLE_ASSIGN'. No other C expressions can appear at statement level; ! a reference to a volatile object is converted into a 'GIMPLE_ASSIGN'. There are also several varieties of complex statements. --- 9335,9342 ---- =============== Most statements in GIMPLE are assignment statements, represented by ! `GIMPLE_ASSIGN'. No other C expressions can appear at statement level; ! a reference to a volatile object is converted into a `GIMPLE_ASSIGN'. There are also several varieties of complex statements. *************** File: gccint.info, Node: Basic Statemen *** 9188,9288 **** 10.7.1 Basic Statements ----------------------- ! 'ASM_EXPR' ! Used to represent an inline assembly statement. For an inline assembly statement like: asm ("mov x, y"); ! The 'ASM_STRING' macro will return a 'STRING_CST' node for '"mov x, ! y"'. If the original statement made use of the extended-assembly ! syntax, then 'ASM_OUTPUTS', 'ASM_INPUTS', and 'ASM_CLOBBERS' will ! be the outputs, inputs, and clobbers for the statement, represented ! as 'STRING_CST' nodes. The extended-assembly syntax looks like: asm ("fsinx %1,%0" : "=f" (result) : "f" (angle)); ! The first string is the 'ASM_STRING', containing the instruction template. The next two strings are the output and inputs, respectively; this statement has no clobbers. As this example ! indicates, "plain" assembly statements are merely a special case of ! extended assembly statements; they have no cv-qualifiers, outputs, ! inputs, or clobbers. All of the strings will be 'NUL'-terminated, ! and will contain no embedded 'NUL'-characters. ! If the assembly statement is declared 'volatile', or if the statement was not an extended assembly statement, and is therefore ! implicitly volatile, then the predicate 'ASM_VOLATILE_P' will hold ! of the 'ASM_EXPR'. ! ! 'DECL_EXPR' ! Used to represent a local declaration. The 'DECL_EXPR_DECL' macro ! can be used to obtain the entity declared. This declaration may be ! a 'LABEL_DECL', indicating that the label declared is a local ! label. (As an extension, GCC allows the declaration of labels with ! scope.) In C, this declaration may be a 'FUNCTION_DECL', indicating the use of the GCC nested function extension. For more information, *note Functions::. ! 'LABEL_EXPR' ! ! Used to represent a label. The 'LABEL_DECL' declared by this ! statement can be obtained with the 'LABEL_EXPR_LABEL' macro. The ! 'IDENTIFIER_NODE' giving the name of the label can be obtained from ! the 'LABEL_DECL' with 'DECL_NAME'. ! ! 'GOTO_EXPR' ! Used to represent a 'goto' statement. The 'GOTO_DESTINATION' will ! usually be a 'LABEL_DECL'. However, if the "computed goto" ! extension has been used, the 'GOTO_DESTINATION' will be an arbitrary expression indicating the destination. This expression will always have pointer type. ! 'RETURN_EXPR' ! ! Used to represent a 'return' statement. Operand 0 represents the ! value to return. It should either be the 'RESULT_DECL' for the ! containing function, or a 'MODIFY_EXPR' or 'INIT_EXPR' setting the ! function's 'RESULT_DECL'. It will be 'NULL_TREE' if the statement was just return; ! 'LOOP_EXPR' ! These nodes represent "infinite" loops. The 'LOOP_EXPR_BODY' represents the body of the loop. It should be executed forever, ! unless an 'EXIT_EXPR' is encountered. ! 'EXIT_EXPR' These nodes represent conditional exits from the nearest enclosing ! 'LOOP_EXPR'. The single operand is the condition; if it is ! nonzero, then the loop should be exited. An 'EXIT_EXPR' will only ! appear within a 'LOOP_EXPR'. ! ! 'SWITCH_STMT' ! Used to represent a 'switch' statement. The 'SWITCH_STMT_COND' is the expression on which the switch is occurring. See the ! documentation for an 'IF_STMT' for more information on the ! representation used for the condition. The 'SWITCH_STMT_BODY' is ! the body of the switch statement. The 'SWITCH_STMT_TYPE' is the original type of switch expression as given in the source, before any compiler conversions. ! 'CASE_LABEL_EXPR' ! ! Use to represent a 'case' label, range of 'case' labels, or a ! 'default' label. If 'CASE_LOW' is 'NULL_TREE', then this is a ! 'default' label. Otherwise, if 'CASE_HIGH' is 'NULL_TREE', then ! this is an ordinary 'case' label. In this case, 'CASE_LOW' is an ! expression giving the value of the label. Both 'CASE_LOW' and ! 'CASE_HIGH' are 'INTEGER_CST' nodes. These values will have the same type as the condition expression in the switch statement. ! Otherwise, if both 'CASE_LOW' and 'CASE_HIGH' are defined, the statement is a range of case labels. Such statements originate with the extension that allows users to write things of the form: case 2 ... 5: ! The first value will be 'CASE_LOW', while the second will be ! 'CASE_HIGH'.  File: gccint.info, Node: Blocks, Next: Statement Sequences, Prev: Basic Statements, Up: Statements --- 9357,9452 ---- 10.7.1 Basic Statements ----------------------- ! `ASM_EXPR' Used to represent an inline assembly statement. For an inline assembly statement like: asm ("mov x, y"); ! The `ASM_STRING' macro will return a `STRING_CST' node for `"mov ! x, y"'. If the original statement made use of the ! extended-assembly syntax, then `ASM_OUTPUTS', `ASM_INPUTS', and ! `ASM_CLOBBERS' will be the outputs, inputs, and clobbers for the ! statement, represented as `STRING_CST' nodes. The ! extended-assembly syntax looks like: asm ("fsinx %1,%0" : "=f" (result) : "f" (angle)); ! The first string is the `ASM_STRING', containing the instruction template. The next two strings are the output and inputs, respectively; this statement has no clobbers. As this example ! indicates, "plain" assembly statements are merely a special case ! of extended assembly statements; they have no cv-qualifiers, ! outputs, inputs, or clobbers. All of the strings will be ! `NUL'-terminated, and will contain no embedded `NUL'-characters. ! If the assembly statement is declared `volatile', or if the statement was not an extended assembly statement, and is therefore ! implicitly volatile, then the predicate `ASM_VOLATILE_P' will hold ! of the `ASM_EXPR'. ! `DECL_EXPR' ! Used to represent a local declaration. The `DECL_EXPR_DECL' macro ! can be used to obtain the entity declared. This declaration may ! be a `LABEL_DECL', indicating that the label declared is a local ! label. (As an extension, GCC allows the declaration of labels ! with scope.) In C, this declaration may be a `FUNCTION_DECL', indicating the use of the GCC nested function extension. For more information, *note Functions::. ! `LABEL_EXPR' ! Used to represent a label. The `LABEL_DECL' declared by this ! statement can be obtained with the `LABEL_EXPR_LABEL' macro. The ! `IDENTIFIER_NODE' giving the name of the label can be obtained from ! the `LABEL_DECL' with `DECL_NAME'. ! `GOTO_EXPR' ! Used to represent a `goto' statement. The `GOTO_DESTINATION' will ! usually be a `LABEL_DECL'. However, if the "computed goto" ! extension has been used, the `GOTO_DESTINATION' will be an arbitrary expression indicating the destination. This expression will always have pointer type. ! `RETURN_EXPR' ! Used to represent a `return' statement. Operand 0 represents the ! value to return. It should either be the `RESULT_DECL' for the ! containing function, or a `MODIFY_EXPR' or `INIT_EXPR' setting the ! function's `RESULT_DECL'. It will be `NULL_TREE' if the statement was just return; ! `LOOP_EXPR' ! These nodes represent "infinite" loops. The `LOOP_EXPR_BODY' represents the body of the loop. It should be executed forever, ! unless an `EXIT_EXPR' is encountered. ! `EXIT_EXPR' These nodes represent conditional exits from the nearest enclosing ! `LOOP_EXPR'. The single operand is the condition; if it is ! nonzero, then the loop should be exited. An `EXIT_EXPR' will only ! appear within a `LOOP_EXPR'. ! `SWITCH_STMT' ! Used to represent a `switch' statement. The `SWITCH_STMT_COND' is the expression on which the switch is occurring. See the ! documentation for an `IF_STMT' for more information on the ! representation used for the condition. The `SWITCH_STMT_BODY' is ! the body of the switch statement. The `SWITCH_STMT_TYPE' is the original type of switch expression as given in the source, before any compiler conversions. ! `CASE_LABEL_EXPR' ! Use to represent a `case' label, range of `case' labels, or a ! `default' label. If `CASE_LOW' is `NULL_TREE', then this is a ! `default' label. Otherwise, if `CASE_HIGH' is `NULL_TREE', then ! this is an ordinary `case' label. In this case, `CASE_LOW' is an ! expression giving the value of the label. Both `CASE_LOW' and ! `CASE_HIGH' are `INTEGER_CST' nodes. These values will have the same type as the condition expression in the switch statement. ! Otherwise, if both `CASE_LOW' and `CASE_HIGH' are defined, the statement is a range of case labels. Such statements originate with the extension that allows users to write things of the form: case 2 ... 5: ! The first value will be `CASE_LOW', while the second will be ! `CASE_HIGH'. !  File: gccint.info, Node: Blocks, Next: Statement Sequences, Prev: Basic Statements, Up: Statements *************** File: gccint.info, Node: Blocks, Next: *** 9291,9322 **** ------------- Block scopes and the variables they declare in GENERIC are expressed ! using the 'BIND_EXPR' code, which in previous versions of GCC was primarily used for the C statement-expression extension. ! Variables in a block are collected into 'BIND_EXPR_VARS' in declaration ! order through their 'TREE_CHAIN' field. Any runtime initialization is ! moved out of 'DECL_INITIAL' and into a statement in the controlled ! block. When gimplifying from C or C++, this initialization replaces the ! 'DECL_STMT'. These variables will never require cleanups. The scope of ! these variables is just the body Variable-length arrays (VLAs) complicate this process, as their size often refers to variables initialized earlier in the block and their initialization involves an explicit stack allocation. To handle this, we add an indirection and replace them with a pointer to stack space ! allocated by means of 'alloca'. In most cases, we also arrange for this ! space to be reclaimed when the enclosing 'BIND_EXPR' is exited, the ! exception to this being when there is an explicit call to 'alloca' in ! the source code, in which case the stack is left depressed on exit of ! the 'BIND_EXPR'. ! A C++ program will usually contain more 'BIND_EXPR's than there are syntactic blocks in the source code, since several C++ constructs have implicit scopes associated with them. On the other hand, although the C++ front end uses pseudo-scopes to handle cleanups for objects with destructors, these don't translate into the GIMPLE form; multiple ! declarations at the same level use the same 'BIND_EXPR'.  File: gccint.info, Node: Statement Sequences, Next: Empty Statements, Prev: Blocks, Up: Statements --- 9455,9486 ---- ------------- Block scopes and the variables they declare in GENERIC are expressed ! using the `BIND_EXPR' code, which in previous versions of GCC was primarily used for the C statement-expression extension. ! Variables in a block are collected into `BIND_EXPR_VARS' in ! declaration order through their `TREE_CHAIN' field. Any runtime ! initialization is moved out of `DECL_INITIAL' and into a statement in ! the controlled block. When gimplifying from C or C++, this ! initialization replaces the `DECL_STMT'. These variables will never ! require cleanups. The scope of these variables is just the body Variable-length arrays (VLAs) complicate this process, as their size often refers to variables initialized earlier in the block and their initialization involves an explicit stack allocation. To handle this, we add an indirection and replace them with a pointer to stack space ! allocated by means of `alloca'. In most cases, we also arrange for ! this space to be reclaimed when the enclosing `BIND_EXPR' is exited, ! the exception to this being when there is an explicit call to `alloca' ! in the source code, in which case the stack is left depressed on exit ! of the `BIND_EXPR'. ! A C++ program will usually contain more `BIND_EXPR's than there are syntactic blocks in the source code, since several C++ constructs have implicit scopes associated with them. On the other hand, although the C++ front end uses pseudo-scopes to handle cleanups for objects with destructors, these don't translate into the GIMPLE form; multiple ! declarations at the same level use the same `BIND_EXPR'.  File: gccint.info, Node: Statement Sequences, Next: Empty Statements, Prev: Blocks, Up: Statements *************** File: gccint.info, Node: Statement Sequ *** 9325,9332 **** -------------------------- Multiple statements at the same nesting level are collected into a ! 'STATEMENT_LIST'. Statement lists are modified and traversed using the ! interface in 'tree-iterator.h'.  File: gccint.info, Node: Empty Statements, Next: Jumps, Prev: Statement Sequences, Up: Statements --- 9489,9496 ---- -------------------------- Multiple statements at the same nesting level are collected into a ! `STATEMENT_LIST'. Statement lists are modified and traversed using the ! interface in `tree-iterator.h'.  File: gccint.info, Node: Empty Statements, Next: Jumps, Prev: Statement Sequences, Up: Statements *************** File: gccint.info, Node: Empty Statemen *** 9334,9347 **** 10.7.4 Empty Statements ----------------------- ! Whenever possible, statements with no effect are discarded. But if they ! are nested within another construct which cannot be discarded for some ! reason, they are instead replaced with an empty statement, generated by ! 'build_empty_stmt'. Initially, all empty statements were shared, after ! the pattern of the Java front end, but this caused a lot of trouble in ! practice. ! An empty statement is represented as '(void)0'.  File: gccint.info, Node: Jumps, Next: Cleanups, Prev: Empty Statements, Up: Statements --- 9498,9511 ---- 10.7.4 Empty Statements ----------------------- ! Whenever possible, statements with no effect are discarded. But if ! they are nested within another construct which cannot be discarded for ! some reason, they are instead replaced with an empty statement, ! generated by `build_empty_stmt'. Initially, all empty statements were ! shared, after the pattern of the Java front end, but this caused a lot ! of trouble in practice. ! An empty statement is represented as `(void)0'.  File: gccint.info, Node: Jumps, Next: Cleanups, Prev: Empty Statements, Up: Statements *************** File: gccint.info, Node: Jumps, Next: *** 9349,9365 **** 10.7.5 Jumps ------------ ! Other jumps are expressed by either 'GOTO_EXPR' or 'RETURN_EXPR'. ! The operand of a 'GOTO_EXPR' must be either a label or a variable containing the address to jump to. ! The operand of a 'RETURN_EXPR' is either 'NULL_TREE', 'RESULT_DECL', or ! a 'MODIFY_EXPR' which sets the return value. It would be nice to move ! the 'MODIFY_EXPR' into a separate statement, but the special return ! semantics in 'expand_return' make that difficult. It may still happen ! in the future, perhaps by moving most of that logic into ! 'expand_assignment'.  File: gccint.info, Node: Cleanups, Next: OpenMP, Prev: Jumps, Up: Statements --- 9513,9529 ---- 10.7.5 Jumps ------------ ! Other jumps are expressed by either `GOTO_EXPR' or `RETURN_EXPR'. ! The operand of a `GOTO_EXPR' must be either a label or a variable containing the address to jump to. ! The operand of a `RETURN_EXPR' is either `NULL_TREE', `RESULT_DECL', ! or a `MODIFY_EXPR' which sets the return value. It would be nice to ! move the `MODIFY_EXPR' into a separate statement, but the special ! return semantics in `expand_return' make that difficult. It may still ! happen in the future, perhaps by moving most of that logic into ! `expand_assignment'.  File: gccint.info, Node: Cleanups, Next: OpenMP, Prev: Jumps, Up: Statements *************** File: gccint.info, Node: Cleanups, Nex *** 9368,9374 **** --------------- Destructors for local C++ objects and similar dynamic cleanups are ! represented in GIMPLE by a 'TRY_FINALLY_EXPR'. 'TRY_FINALLY_EXPR' has two operands, both of which are a sequence of statements to execute. The first sequence is executed. When it completes the second sequence is executed. --- 9532,9538 ---- --------------- Destructors for local C++ objects and similar dynamic cleanups are ! represented in GIMPLE by a `TRY_FINALLY_EXPR'. `TRY_FINALLY_EXPR' has two operands, both of which are a sequence of statements to execute. The first sequence is executed. When it completes the second sequence is executed. *************** is executed. *** 9377,9407 **** 1. Execute the last statement in the sequence and fall off the end. ! 2. Execute a goto statement ('GOTO_EXPR') to an ordinary label outside ! the sequence. ! 3. Execute a return statement ('RETURN_EXPR'). 4. Throw an exception. This is currently not explicitly represented in GIMPLE. The second sequence is not executed if the first sequence completes by ! calling 'setjmp' or 'exit' or any other function that does not return. ! The second sequence is also not executed if the first sequence completes ! via a non-local goto or a computed goto (in general the compiler does ! not know whether such a goto statement exits the first sequence or not, ! so we assume that it doesn't). After the second sequence is executed, if it completes normally by falling off the end, execution continues wherever the first sequence would have continued, by falling off the end, or doing a goto, etc. ! 'TRY_FINALLY_EXPR' complicates the flow graph, since the cleanup needs to appear on every edge out of the controlled block; this reduces the freedom to move code across these edges. Therefore, the EH lowering pass which runs before most of the optimization passes eliminates these expressions by explicitly adding the cleanup to each edge. Rethrowing ! the exception is represented using 'RESX_EXPR'.  File: gccint.info, Node: OpenMP, Next: OpenACC, Prev: Cleanups, Up: Statements --- 9541,9572 ---- 1. Execute the last statement in the sequence and fall off the end. ! 2. Execute a goto statement (`GOTO_EXPR') to an ordinary label ! outside the sequence. ! 3. Execute a return statement (`RETURN_EXPR'). 4. Throw an exception. This is currently not explicitly represented in GIMPLE. + The second sequence is not executed if the first sequence completes by ! calling `setjmp' or `exit' or any other function that does not return. ! The second sequence is also not executed if the first sequence ! completes via a non-local goto or a computed goto (in general the ! compiler does not know whether such a goto statement exits the first ! sequence or not, so we assume that it doesn't). After the second sequence is executed, if it completes normally by falling off the end, execution continues wherever the first sequence would have continued, by falling off the end, or doing a goto, etc. ! `TRY_FINALLY_EXPR' complicates the flow graph, since the cleanup needs to appear on every edge out of the controlled block; this reduces the freedom to move code across these edges. Therefore, the EH lowering pass which runs before most of the optimization passes eliminates these expressions by explicitly adding the cleanup to each edge. Rethrowing ! the exception is represented using `RESX_EXPR'.  File: gccint.info, Node: OpenMP, Next: OpenACC, Prev: Cleanups, Up: Statements *************** File: gccint.info, Node: OpenMP, Next: *** 9409,9540 **** 10.7.7 OpenMP ------------- ! All the statements starting with 'OMP_' represent directives and clauses ! used by the OpenMP API . ! ! 'OMP_PARALLEL' ! Represents '#pragma omp parallel [clause1 ... clauseN]'. It has four operands: ! Operand 'OMP_PARALLEL_BODY' is valid while in GENERIC and High GIMPLE forms. It contains the body of code to be executed by all ! the threads. During GIMPLE lowering, this operand becomes 'NULL' ! and the body is emitted linearly after 'OMP_PARALLEL'. ! Operand 'OMP_PARALLEL_CLAUSES' is the list of clauses associated with the directive. ! Operand 'OMP_PARALLEL_FN' is created by 'pass_lower_omp', it ! contains the 'FUNCTION_DECL' for the function that will contain the ! body of the parallel region. ! Operand 'OMP_PARALLEL_DATA_ARG' is also created by ! 'pass_lower_omp'. If there are shared variables to be communicated ! to the children threads, this operand will contain the 'VAR_DECL' that contains all the shared values and variables. ! 'OMP_FOR' ! ! Represents '#pragma omp for [clause1 ... clauseN]'. It has six operands: ! Operand 'OMP_FOR_BODY' contains the loop body. ! Operand 'OMP_FOR_CLAUSES' is the list of clauses associated with the directive. ! Operand 'OMP_FOR_INIT' is the loop initialization code of the form ! 'VAR = N1'. ! Operand 'OMP_FOR_COND' is the loop conditional expression of the ! form 'VAR {<,>,<=,>=} N2'. ! Operand 'OMP_FOR_INCR' is the loop index increment of the form 'VAR ! {+=,-=} INCR'. ! Operand 'OMP_FOR_PRE_BODY' contains side-effect code from operands ! 'OMP_FOR_INIT', 'OMP_FOR_COND' and 'OMP_FOR_INC'. These ! side-effects are part of the 'OMP_FOR' block but must be evaluated before the start of loop body. ! The loop index variable 'VAR' must be a signed integer variable, ! which is implicitly private to each thread. Bounds 'N1' and 'N2' ! and the increment expression 'INCR' are required to be loop invariant integer expressions that are evaluated without any ! synchronization. The evaluation order, frequency of evaluation and side-effects are unspecified by the standard. ! 'OMP_SECTIONS' ! ! Represents '#pragma omp sections [clause1 ... clauseN]'. ! Operand 'OMP_SECTIONS_BODY' contains the sections body, which in ! turn contains a set of 'OMP_SECTION' nodes for each of the ! concurrent sections delimited by '#pragma omp section'. ! Operand 'OMP_SECTIONS_CLAUSES' is the list of clauses associated with the directive. ! 'OMP_SECTION' ! ! Section delimiter for 'OMP_SECTIONS'. ! ! 'OMP_SINGLE' ! Represents '#pragma omp single'. ! Operand 'OMP_SINGLE_BODY' contains the body of code to be executed by a single thread. ! Operand 'OMP_SINGLE_CLAUSES' is the list of clauses associated with ! the directive. ! ! 'OMP_MASTER' ! Represents '#pragma omp master'. ! Operand 'OMP_MASTER_BODY' contains the body of code to be executed by the master thread. ! 'OMP_ORDERED' ! ! Represents '#pragma omp ordered'. ! ! Operand 'OMP_ORDERED_BODY' contains the body of code to be executed ! in the sequential order dictated by the loop index variable. ! 'OMP_CRITICAL' ! Represents '#pragma omp critical [name]'. ! Operand 'OMP_CRITICAL_BODY' is the critical section. ! Operand 'OMP_CRITICAL_NAME' is an optional identifier to label the critical section. ! 'OMP_RETURN' ! This does not represent any OpenMP directive, it is an artificial ! marker to indicate the end of the body of an OpenMP. It is used by ! the flow graph ('tree-cfg.c') and OpenMP region building code ! ('omp-low.c'). ! ! 'OMP_CONTINUE' ! Similarly, this instruction does not represent an OpenMP directive, ! it is used by 'OMP_FOR' (and similar codes) as well as ! 'OMP_SECTIONS' to mark the place where the code needs to loop to the next iteration, or the next section, respectively. ! In some cases, 'OMP_CONTINUE' is placed right before 'OMP_RETURN'. But if there are cleanups that need to occur right after the ! looping body, it will be emitted between 'OMP_CONTINUE' and ! 'OMP_RETURN'. ! ! 'OMP_ATOMIC' ! Represents '#pragma omp atomic'. Operand 0 is the address at which the atomic operation is to be performed. --- 9574,9695 ---- 10.7.7 OpenMP ------------- ! All the statements starting with `OMP_' represent directives and ! clauses used by the OpenMP API `http://www.openmp.org/'. ! `OMP_PARALLEL' ! Represents `#pragma omp parallel [clause1 ... clauseN]'. It has four operands: ! Operand `OMP_PARALLEL_BODY' is valid while in GENERIC and High GIMPLE forms. It contains the body of code to be executed by all ! the threads. During GIMPLE lowering, this operand becomes `NULL' ! and the body is emitted linearly after `OMP_PARALLEL'. ! Operand `OMP_PARALLEL_CLAUSES' is the list of clauses associated with the directive. ! Operand `OMP_PARALLEL_FN' is created by `pass_lower_omp', it ! contains the `FUNCTION_DECL' for the function that will contain ! the body of the parallel region. ! Operand `OMP_PARALLEL_DATA_ARG' is also created by ! `pass_lower_omp'. If there are shared variables to be communicated ! to the children threads, this operand will contain the `VAR_DECL' that contains all the shared values and variables. ! `OMP_FOR' ! Represents `#pragma omp for [clause1 ... clauseN]'. It has six operands: ! Operand `OMP_FOR_BODY' contains the loop body. ! Operand `OMP_FOR_CLAUSES' is the list of clauses associated with the directive. ! Operand `OMP_FOR_INIT' is the loop initialization code of the form ! `VAR = N1'. ! Operand `OMP_FOR_COND' is the loop conditional expression of the ! form `VAR {<,>,<=,>=} N2'. ! Operand `OMP_FOR_INCR' is the loop index increment of the form ! `VAR {+=,-=} INCR'. ! Operand `OMP_FOR_PRE_BODY' contains side-effect code from operands ! `OMP_FOR_INIT', `OMP_FOR_COND' and `OMP_FOR_INC'. These ! side-effects are part of the `OMP_FOR' block but must be evaluated before the start of loop body. ! The loop index variable `VAR' must be a signed integer variable, ! which is implicitly private to each thread. Bounds `N1' and `N2' ! and the increment expression `INCR' are required to be loop invariant integer expressions that are evaluated without any ! synchronization. The evaluation order, frequency of evaluation and side-effects are unspecified by the standard. ! `OMP_SECTIONS' ! Represents `#pragma omp sections [clause1 ... clauseN]'. ! Operand `OMP_SECTIONS_BODY' contains the sections body, which in ! turn contains a set of `OMP_SECTION' nodes for each of the ! concurrent sections delimited by `#pragma omp section'. ! Operand `OMP_SECTIONS_CLAUSES' is the list of clauses associated with the directive. ! `OMP_SECTION' ! Section delimiter for `OMP_SECTIONS'. ! `OMP_SINGLE' ! Represents `#pragma omp single'. ! Operand `OMP_SINGLE_BODY' contains the body of code to be executed by a single thread. ! Operand `OMP_SINGLE_CLAUSES' is the list of clauses associated ! with the directive. ! `OMP_MASTER' ! Represents `#pragma omp master'. ! Operand `OMP_MASTER_BODY' contains the body of code to be executed by the master thread. ! `OMP_ORDERED' ! Represents `#pragma omp ordered'. ! Operand `OMP_ORDERED_BODY' contains the body of code to be ! executed in the sequential order dictated by the loop index ! variable. ! `OMP_CRITICAL' ! Represents `#pragma omp critical [name]'. ! Operand `OMP_CRITICAL_BODY' is the critical section. ! Operand `OMP_CRITICAL_NAME' is an optional identifier to label the critical section. ! `OMP_RETURN' This does not represent any OpenMP directive, it is an artificial ! marker to indicate the end of the body of an OpenMP. It is used by ! the flow graph (`tree-cfg.c') and OpenMP region building code ! (`omp-low.c'). ! `OMP_CONTINUE' ! Similarly, this instruction does not represent an OpenMP ! directive, it is used by `OMP_FOR' (and similar codes) as well as ! `OMP_SECTIONS' to mark the place where the code needs to loop to the next iteration, or the next section, respectively. ! In some cases, `OMP_CONTINUE' is placed right before `OMP_RETURN'. But if there are cleanups that need to occur right after the ! looping body, it will be emitted between `OMP_CONTINUE' and ! `OMP_RETURN'. ! `OMP_ATOMIC' ! Represents `#pragma omp atomic'. Operand 0 is the address at which the atomic operation is to be performed. *************** used by the OpenMP API . ! ! 'OACC_CACHE' ! ! Represents '#pragma acc cache (var ...)'. ! ! 'OACC_DATA' ! ! Represents '#pragma acc data [clause1 ... clauseN]'. ! ! 'OACC_DECLARE' ! ! Represents '#pragma acc declare [clause1 ... clauseN]'. ! ! 'OACC_ENTER_DATA' ! ! Represents '#pragma acc enter data [clause1 ... clauseN]'. ! ! 'OACC_EXIT_DATA' ! Represents '#pragma acc exit data [clause1 ... clauseN]'. ! 'OACC_HOST_DATA' ! Represents '#pragma acc host_data [clause1 ... clauseN]'. ! 'OACC_KERNELS' ! Represents '#pragma acc kernels [clause1 ... clauseN]'. ! 'OACC_LOOP' ! Represents '#pragma acc loop [clause1 ... clauseN]'. ! See the description of the 'OMP_FOR' code. ! 'OACC_PARALLEL' ! Represents '#pragma acc parallel [clause1 ... clauseN]'. ! 'OACC_UPDATE' - Represents '#pragma acc update [clause1 ... clauseN]'.  File: gccint.info, Node: Functions, Next: Language-dependent trees, Prev: Statements, Up: GENERIC --- 9727,9767 ---- 10.7.8 OpenACC -------------- ! All the statements starting with `OACC_' represent directives and ! clauses used by the OpenACC API `http://www.openacc.org/'. ! `OACC_CACHE' ! Represents `#pragma acc cache (var ...)'. ! `OACC_DATA' ! Represents `#pragma acc data [clause1 ... clauseN]'. ! `OACC_DECLARE' ! Represents `#pragma acc declare [clause1 ... clauseN]'. ! `OACC_ENTER_DATA' ! Represents `#pragma acc enter data [clause1 ... clauseN]'. ! `OACC_EXIT_DATA' ! Represents `#pragma acc exit data [clause1 ... clauseN]'. ! `OACC_HOST_DATA' ! Represents `#pragma acc host_data [clause1 ... clauseN]'. ! `OACC_KERNELS' ! Represents `#pragma acc kernels [clause1 ... clauseN]'. ! `OACC_LOOP' ! Represents `#pragma acc loop [clause1 ... clauseN]'. ! See the description of the `OMP_FOR' code. ! `OACC_PARALLEL' ! Represents `#pragma acc parallel [clause1 ... clauseN]'. ! `OACC_UPDATE' ! Represents `#pragma acc update [clause1 ... clauseN]'.  File: gccint.info, Node: Functions, Next: Language-dependent trees, Prev: Statements, Up: GENERIC *************** File: gccint.info, Node: Functions, Ne *** 9623,9629 **** 10.8 Functions ============== ! A function is represented by a 'FUNCTION_DECL' node. It stores the basic pieces of the function such as body, parameters, and return type as well as information on the surrounding context, visibility, and linkage. --- 9769,9775 ---- 10.8 Functions ============== ! A function is represented by a `FUNCTION_DECL' node. It stores the basic pieces of the function such as body, parameters, and return type as well as information on the surrounding context, visibility, and linkage. *************** File: gccint.info, Node: Function Basic *** 9641,9700 **** A function has four core parts: the name, the parameters, the result, and the body. The following macros and functions access these parts of ! a 'FUNCTION_DECL' as well as other basic features: ! 'DECL_NAME' This macro returns the unqualified name of the function, as an ! 'IDENTIFIER_NODE'. For an instantiation of a function template, ! the 'DECL_NAME' is the unqualified name of the template, not ! something like 'f'. The value of 'DECL_NAME' is undefined when used on a constructor, destructor, overloaded operator, or type-conversion operator, or any function that is implicitly generated by the compiler. See below for macros that can be used to distinguish these cases. ! 'DECL_ASSEMBLER_NAME' This macro returns the mangled name of the function, also an ! 'IDENTIFIER_NODE'. This name does not contain leading underscores on systems that prefix all identifiers with underscores. The mangled name is computed in the same way on all platforms; if special processing is required to deal with the object file format ! used on a particular platform, it is the responsibility of the back ! end to perform those modifications. (Of course, the back end ! should not modify 'DECL_ASSEMBLER_NAME' itself.) ! Using 'DECL_ASSEMBLER_NAME' will cause additional memory to be allocated (for the mangled name of the entity) so it should be used only when emitting assembly code. It should not be used within the optimizers to determine whether or not two declarations are the ! same, even though some of the existing optimizers do use it in that ! way. These uses will be removed over time. ! 'DECL_ARGUMENTS' ! This macro returns the 'PARM_DECL' for the first argument to the ! function. Subsequent 'PARM_DECL' nodes can be obtained by ! following the 'TREE_CHAIN' links. ! 'DECL_RESULT' ! This macro returns the 'RESULT_DECL' for the function. ! 'DECL_SAVED_TREE' This macro returns the complete body of the function. ! 'TREE_TYPE' ! This macro returns the 'FUNCTION_TYPE' or 'METHOD_TYPE' for the function. ! 'DECL_INITIAL' A function that has a definition in the current translation unit ! will have a non-'NULL' 'DECL_INITIAL'. However, back ends should ! not make use of the particular value given by 'DECL_INITIAL'. ! It should contain a tree of 'BLOCK' nodes that mirrors the scopes that variables are bound in the function. Each block contains a list of decls declared in a basic block, a pointer to a chain of blocks at the next lower scope level, then a pointer to the next ! block at the same level and a backpointer to the parent 'BLOCK' or ! 'FUNCTION_DECL'. So given a function as follows: void foo() { --- 9787,9846 ---- A function has four core parts: the name, the parameters, the result, and the body. The following macros and functions access these parts of ! a `FUNCTION_DECL' as well as other basic features: ! `DECL_NAME' This macro returns the unqualified name of the function, as an ! `IDENTIFIER_NODE'. For an instantiation of a function template, ! the `DECL_NAME' is the unqualified name of the template, not ! something like `f'. The value of `DECL_NAME' is undefined when used on a constructor, destructor, overloaded operator, or type-conversion operator, or any function that is implicitly generated by the compiler. See below for macros that can be used to distinguish these cases. ! `DECL_ASSEMBLER_NAME' This macro returns the mangled name of the function, also an ! `IDENTIFIER_NODE'. This name does not contain leading underscores on systems that prefix all identifiers with underscores. The mangled name is computed in the same way on all platforms; if special processing is required to deal with the object file format ! used on a particular platform, it is the responsibility of the ! back end to perform those modifications. (Of course, the back end ! should not modify `DECL_ASSEMBLER_NAME' itself.) ! Using `DECL_ASSEMBLER_NAME' will cause additional memory to be allocated (for the mangled name of the entity) so it should be used only when emitting assembly code. It should not be used within the optimizers to determine whether or not two declarations are the ! same, even though some of the existing optimizers do use it in ! that way. These uses will be removed over time. ! `DECL_ARGUMENTS' ! This macro returns the `PARM_DECL' for the first argument to the ! function. Subsequent `PARM_DECL' nodes can be obtained by ! following the `TREE_CHAIN' links. ! `DECL_RESULT' ! This macro returns the `RESULT_DECL' for the function. ! `DECL_SAVED_TREE' This macro returns the complete body of the function. ! `TREE_TYPE' ! This macro returns the `FUNCTION_TYPE' or `METHOD_TYPE' for the function. ! `DECL_INITIAL' A function that has a definition in the current translation unit ! will have a non-`NULL' `DECL_INITIAL'. However, back ends should ! not make use of the particular value given by `DECL_INITIAL'. ! It should contain a tree of `BLOCK' nodes that mirrors the scopes that variables are bound in the function. Each block contains a list of decls declared in a basic block, a pointer to a chain of blocks at the next lower scope level, then a pointer to the next ! block at the same level and a backpointer to the parent `BLOCK' or ! `FUNCTION_DECL'. So given a function as follows: void foo() { *************** a 'FUNCTION_DECL' as well as other basic *** 9724,9777 **** BLOCK_SUPERCONTEXT(block_c) = foo; DECL_INITIAL(foo) = block_a;  File: gccint.info, Node: Function Properties, Prev: Function Basics, Up: Functions 10.8.2 Function Properties -------------------------- ! To determine the scope of a function, you can use the 'DECL_CONTEXT' ! macro. This macro will return the class (either a 'RECORD_TYPE' or a ! 'UNION_TYPE') or namespace (a 'NAMESPACE_DECL') of which the function is ! a member. For a virtual function, this macro returns the class in which ! the function was actually defined, not the base class in which the ! virtual declaration occurred. ! In C, the 'DECL_CONTEXT' for a function maybe another function. This representation indicates that the GNU nested function extension is in use. For details on the semantics of nested functions, see the GCC Manual. The nested function can refer to local variables in its containing function. Such references are not explicitly marked in the ! tree structure; back ends must look at the 'DECL_CONTEXT' for the ! referenced 'VAR_DECL'. If the 'DECL_CONTEXT' for the referenced ! 'VAR_DECL' is not the same as the function currently being processed, ! and neither 'DECL_EXTERNAL' nor 'TREE_STATIC' hold, then the reference is to a local variable in a containing function, and the back end must take appropriate action. ! 'DECL_EXTERNAL' This predicate holds if the function is undefined. ! 'TREE_PUBLIC' This predicate holds if the function has external linkage. ! 'TREE_STATIC' This predicate holds if the function has been defined. ! 'TREE_THIS_VOLATILE' This predicate holds if the function does not return normally. ! 'TREE_READONLY' This predicate holds if the function can only read its arguments. ! 'DECL_PURE_P' This predicate holds if the function can only read its arguments, but may also read global memory. ! 'DECL_VIRTUAL_P' This predicate holds if the function is virtual. ! 'DECL_ARTIFICIAL' This macro holds if the function was implicitly generated by the compiler, rather than explicitly declared. In addition to implicitly generated class member functions, this macro holds for --- 9870,9924 ---- BLOCK_SUPERCONTEXT(block_c) = foo; DECL_INITIAL(foo) = block_a; +  File: gccint.info, Node: Function Properties, Prev: Function Basics, Up: Functions 10.8.2 Function Properties -------------------------- ! To determine the scope of a function, you can use the `DECL_CONTEXT' ! macro. This macro will return the class (either a `RECORD_TYPE' or a ! `UNION_TYPE') or namespace (a `NAMESPACE_DECL') of which the function ! is a member. For a virtual function, this macro returns the class in ! which the function was actually defined, not the base class in which ! the virtual declaration occurred. ! In C, the `DECL_CONTEXT' for a function maybe another function. This representation indicates that the GNU nested function extension is in use. For details on the semantics of nested functions, see the GCC Manual. The nested function can refer to local variables in its containing function. Such references are not explicitly marked in the ! tree structure; back ends must look at the `DECL_CONTEXT' for the ! referenced `VAR_DECL'. If the `DECL_CONTEXT' for the referenced ! `VAR_DECL' is not the same as the function currently being processed, ! and neither `DECL_EXTERNAL' nor `TREE_STATIC' hold, then the reference is to a local variable in a containing function, and the back end must take appropriate action. ! `DECL_EXTERNAL' This predicate holds if the function is undefined. ! `TREE_PUBLIC' This predicate holds if the function has external linkage. ! `TREE_STATIC' This predicate holds if the function has been defined. ! `TREE_THIS_VOLATILE' This predicate holds if the function does not return normally. ! `TREE_READONLY' This predicate holds if the function can only read its arguments. ! `DECL_PURE_P' This predicate holds if the function can only read its arguments, but may also read global memory. ! `DECL_VIRTUAL_P' This predicate holds if the function is virtual. ! `DECL_ARTIFICIAL' This macro holds if the function was implicitly generated by the compiler, rather than explicitly declared. In addition to implicitly generated class member functions, this macro holds for *************** take appropriate action. *** 9779,9795 **** and destruction, to compute run-time type information, and so forth. ! 'DECL_FUNCTION_SPECIFIC_TARGET' This macro returns a tree node that holds the target options that ! are to be used to compile this particular function or 'NULL_TREE' ! if the function is to be compiled with the target options specified ! on the command line. ! 'DECL_FUNCTION_SPECIFIC_OPTIMIZATION' This macro returns a tree node that holds the optimization options that are to be used to compile this particular function or ! 'NULL_TREE' if the function is to be compiled with the optimization ! options specified on the command line.  File: gccint.info, Node: Language-dependent trees, Next: C and C++ Trees, Prev: Functions, Up: GENERIC --- 9926,9943 ---- and destruction, to compute run-time type information, and so forth. ! `DECL_FUNCTION_SPECIFIC_TARGET' This macro returns a tree node that holds the target options that ! are to be used to compile this particular function or `NULL_TREE' ! if the function is to be compiled with the target options ! specified on the command line. ! `DECL_FUNCTION_SPECIFIC_OPTIMIZATION' This macro returns a tree node that holds the optimization options that are to be used to compile this particular function or ! `NULL_TREE' if the function is to be compiled with the ! optimization options specified on the command line. !  File: gccint.info, Node: Language-dependent trees, Next: C and C++ Trees, Prev: Functions, Up: GENERIC *************** File: gccint.info, Node: Language-depen *** 9798,9814 **** ============================= Front ends may wish to keep some state associated with various GENERIC ! trees while parsing. To support this, trees provide a set of flags that ! may be used by the front end. They are accessed using ! 'TREE_LANG_FLAG_n' where 'n' is currently 0 through 6. ! If necessary, a front end can use some language-dependent tree codes in ! its GENERIC representation, so long as it provides a hook for converting ! them to GIMPLE and doesn't expect them to work with any (hypothetical) ! optimizers that run before the conversion to GIMPLE. The intermediate ! representation used while parsing C and C++ looks very little like ! GENERIC, but the C and C++ gimplifier hooks are perfectly happy to take ! it as input and spit out GIMPLE.  File: gccint.info, Node: C and C++ Trees, Next: Java Trees, Prev: Language-dependent trees, Up: GENERIC --- 9946,9962 ---- ============================= Front ends may wish to keep some state associated with various GENERIC ! trees while parsing. To support this, trees provide a set of flags ! that may be used by the front end. They are accessed using ! `TREE_LANG_FLAG_n' where `n' is currently 0 through 6. ! If necessary, a front end can use some language-dependent tree codes ! in its GENERIC representation, so long as it provides a hook for ! converting them to GIMPLE and doesn't expect them to work with any ! (hypothetical) optimizers that run before the conversion to GIMPLE. The ! intermediate representation used while parsing C and C++ looks very ! little like GENERIC, but the C and C++ gimplifier hooks are perfectly ! happy to take it as input and spit out GIMPLE.  File: gccint.info, Node: C and C++ Trees, Next: Java Trees, Prev: Language-dependent trees, Up: GENERIC *************** submit your patches for inclusion in GCC *** 9864,9870 **** * Classes:: Classes. * Functions for C++:: Overloading and accessors for C++. * Statements for C++:: Statements specific to C and C++. ! * C++ Expressions:: From 'typeid' to 'throw'.  File: gccint.info, Node: Types for C++, Next: Namespaces, Up: C and C++ Trees --- 10012,10018 ---- * Classes:: Classes. * Functions for C++:: Overloading and accessors for C++. * Statements for C++:: Statements specific to C and C++. ! * C++ Expressions:: From `typeid' to `throw'.  File: gccint.info, Node: Types for C++, Next: Namespaces, Up: C and C++ Trees *************** representation. The macros described he *** 9878,9991 **** qualification of the underlying element type when applied to an array type. (If the element type is itself an array, then the recursion continues until a non-array type is found, and the qualification of this ! type is examined.) So, for example, 'CP_TYPE_CONST_P' will hold of the ! type 'const int ()[7]', denoting an array of seven 'int's. The following functions and macros deal with cv-qualification of types: ! 'cp_type_quals' This function returns the set of type qualifiers applied to this ! type. This value is 'TYPE_UNQUALIFIED' if no qualifiers have been ! applied. The 'TYPE_QUAL_CONST' bit is set if the type is ! 'const'-qualified. The 'TYPE_QUAL_VOLATILE' bit is set if the type ! is 'volatile'-qualified. The 'TYPE_QUAL_RESTRICT' bit is set if ! the type is 'restrict'-qualified. ! 'CP_TYPE_CONST_P' ! This macro holds if the type is 'const'-qualified. ! 'CP_TYPE_VOLATILE_P' ! This macro holds if the type is 'volatile'-qualified. ! 'CP_TYPE_RESTRICT_P' ! This macro holds if the type is 'restrict'-qualified. - 'CP_TYPE_CONST_NON_VOLATILE_P' - This predicate holds for a type that is 'const'-qualified, but - _not_ 'volatile'-qualified; other cv-qualifiers are ignored as - well: only the 'const'-ness is tested. A few other macros and functions are usable with all types: ! 'TYPE_SIZE' The number of bits required to represent the type, represented as ! an 'INTEGER_CST'. For an incomplete type, 'TYPE_SIZE' will be ! 'NULL_TREE'. ! 'TYPE_ALIGN' ! The alignment of the type, in bits, represented as an 'int'. ! 'TYPE_NAME' ! This macro returns a declaration (in the form of a 'TYPE_DECL') for ! the type. (Note this macro does _not_ return an 'IDENTIFIER_NODE', ! as you might expect, given its name!) You can look at the ! 'DECL_NAME' of the 'TYPE_DECL' to obtain the actual name of the ! type. The 'TYPE_NAME' will be 'NULL_TREE' for a type that is not a ! built-in type, the result of a typedef, or a named class type. ! 'CP_INTEGRAL_TYPE' This predicate holds if the type is an integral type. Notice that in C++, enumerations are _not_ integral types. ! 'ARITHMETIC_TYPE_P' This predicate holds if the type is an integral type (in the C++ sense) or a floating point type. ! 'CLASS_TYPE_P' This predicate holds for a class-type. ! 'TYPE_BUILT_IN' This predicate holds for a built-in type. ! 'TYPE_PTRDATAMEM_P' This predicate holds if the type is a pointer to data member. ! 'TYPE_PTR_P' ! This predicate holds if the type is a pointer type, and the pointee ! is not a data member. ! 'TYPE_PTRFN_P' This predicate holds for a pointer to function type. ! 'TYPE_PTROB_P' This predicate holds for a pointer to object type. Note however ! that it does not hold for the generic pointer to object type 'void ! *'. You may use 'TYPE_PTROBV_P' to test for a pointer to object ! type as well as 'void *'. The table below describes types specific to C and C++ as well as language-dependent info about GENERIC types. ! 'POINTER_TYPE' Used to represent pointer types, and pointer to data member types. ! If 'TREE_TYPE' is a pointer to data member type, then ! 'TYPE_PTRDATAMEM_P' will hold. For a pointer to data member type ! of the form 'T X::*', 'TYPE_PTRMEM_CLASS_TYPE' will be the type ! 'X', while 'TYPE_PTRMEM_POINTED_TO_TYPE' will be the type 'T'. ! 'RECORD_TYPE' ! Used to represent 'struct' and 'class' types in C and C++. If ! 'TYPE_PTRMEMFUNC_P' holds, then this type is a pointer-to-member ! type. In that case, the 'TYPE_PTRMEMFUNC_FN_TYPE' is a ! 'POINTER_TYPE' pointing to a 'METHOD_TYPE'. The 'METHOD_TYPE' is the type of a function pointed to by the pointer-to-member ! function. If 'TYPE_PTRMEMFUNC_P' does not hold, this type is a class type. For more information, *note Classes::. ! 'UNKNOWN_TYPE' This node is used to represent a type the knowledge of which is insufficient for a sound processing. ! 'TYPENAME_TYPE' ! Used to represent a construct of the form 'typename T::A'. The ! 'TYPE_CONTEXT' is 'T'; the 'TYPE_NAME' is an 'IDENTIFIER_NODE' for ! 'A'. If the type is specified via a template-id, then ! 'TYPENAME_TYPE_FULLNAME' yields a 'TEMPLATE_ID_EXPR'. The ! 'TREE_TYPE' is non-'NULL' if the node is implicitly generated in support for the implicit typename extension; in which case the ! 'TREE_TYPE' is a type node for the base-class. - 'TYPEOF_TYPE' - Used to represent the '__typeof__' extension. The 'TYPE_FIELDS' is - the expression the type of which is being represented.  File: gccint.info, Node: Namespaces, Next: Classes, Prev: Types for C++, Up: C and C++ Trees --- 10026,10143 ---- qualification of the underlying element type when applied to an array type. (If the element type is itself an array, then the recursion continues until a non-array type is found, and the qualification of this ! type is examined.) So, for example, `CP_TYPE_CONST_P' will hold of the ! type `const int ()[7]', denoting an array of seven `int's. The following functions and macros deal with cv-qualification of types: ! `cp_type_quals' This function returns the set of type qualifiers applied to this ! type. This value is `TYPE_UNQUALIFIED' if no qualifiers have been ! applied. The `TYPE_QUAL_CONST' bit is set if the type is ! `const'-qualified. The `TYPE_QUAL_VOLATILE' bit is set if the ! type is `volatile'-qualified. The `TYPE_QUAL_RESTRICT' bit is set ! if the type is `restrict'-qualified. ! `CP_TYPE_CONST_P' ! This macro holds if the type is `const'-qualified. ! `CP_TYPE_VOLATILE_P' ! This macro holds if the type is `volatile'-qualified. ! `CP_TYPE_RESTRICT_P' ! This macro holds if the type is `restrict'-qualified. ! ! `CP_TYPE_CONST_NON_VOLATILE_P' ! This predicate holds for a type that is `const'-qualified, but ! _not_ `volatile'-qualified; other cv-qualifiers are ignored as ! well: only the `const'-ness is tested. A few other macros and functions are usable with all types: ! `TYPE_SIZE' The number of bits required to represent the type, represented as ! an `INTEGER_CST'. For an incomplete type, `TYPE_SIZE' will be ! `NULL_TREE'. ! `TYPE_ALIGN' ! The alignment of the type, in bits, represented as an `int'. ! `TYPE_NAME' ! This macro returns a declaration (in the form of a `TYPE_DECL') for ! the type. (Note this macro does _not_ return an ! `IDENTIFIER_NODE', as you might expect, given its name!) You can ! look at the `DECL_NAME' of the `TYPE_DECL' to obtain the actual ! name of the type. The `TYPE_NAME' will be `NULL_TREE' for a type ! that is not a built-in type, the result of a typedef, or a named ! class type. ! `CP_INTEGRAL_TYPE' This predicate holds if the type is an integral type. Notice that in C++, enumerations are _not_ integral types. ! `ARITHMETIC_TYPE_P' This predicate holds if the type is an integral type (in the C++ sense) or a floating point type. ! `CLASS_TYPE_P' This predicate holds for a class-type. ! `TYPE_BUILT_IN' This predicate holds for a built-in type. ! `TYPE_PTRDATAMEM_P' This predicate holds if the type is a pointer to data member. ! `TYPE_PTR_P' ! This predicate holds if the type is a pointer type, and the ! pointee is not a data member. ! `TYPE_PTRFN_P' This predicate holds for a pointer to function type. ! `TYPE_PTROB_P' This predicate holds for a pointer to object type. Note however ! that it does not hold for the generic pointer to object type `void ! *'. You may use `TYPE_PTROBV_P' to test for a pointer to object ! type as well as `void *'. ! The table below describes types specific to C and C++ as well as language-dependent info about GENERIC types. ! `POINTER_TYPE' Used to represent pointer types, and pointer to data member types. ! If `TREE_TYPE' is a pointer to data member type, then ! `TYPE_PTRDATAMEM_P' will hold. For a pointer to data member type ! of the form `T X::*', `TYPE_PTRMEM_CLASS_TYPE' will be the type ! `X', while `TYPE_PTRMEM_POINTED_TO_TYPE' will be the type `T'. ! `RECORD_TYPE' ! Used to represent `struct' and `class' types in C and C++. If ! `TYPE_PTRMEMFUNC_P' holds, then this type is a pointer-to-member ! type. In that case, the `TYPE_PTRMEMFUNC_FN_TYPE' is a ! `POINTER_TYPE' pointing to a `METHOD_TYPE'. The `METHOD_TYPE' is the type of a function pointed to by the pointer-to-member ! function. If `TYPE_PTRMEMFUNC_P' does not hold, this type is a class type. For more information, *note Classes::. ! `UNKNOWN_TYPE' This node is used to represent a type the knowledge of which is insufficient for a sound processing. ! `TYPENAME_TYPE' ! Used to represent a construct of the form `typename T::A'. The ! `TYPE_CONTEXT' is `T'; the `TYPE_NAME' is an `IDENTIFIER_NODE' for ! `A'. If the type is specified via a template-id, then ! `TYPENAME_TYPE_FULLNAME' yields a `TEMPLATE_ID_EXPR'. The ! `TREE_TYPE' is non-`NULL' if the node is implicitly generated in support for the implicit typename extension; in which case the ! `TREE_TYPE' is a type node for the base-class. ! ! `TYPEOF_TYPE' ! Used to represent the `__typeof__' extension. The `TYPE_FIELDS' ! is the expression the type of which is being represented.  File: gccint.info, Node: Namespaces, Next: Classes, Prev: Types for C++, Up: C and C++ Trees *************** File: gccint.info, Node: Namespaces, N *** 9994,10000 **** ------------------ The root of the entire intermediate representation is the variable ! 'global_namespace'. This is the namespace specified with '::' in C++ source code. All other namespaces, types, variables, functions, and so forth can be found starting with this namespace. --- 10146,10152 ---- ------------------ The root of the entire intermediate representation is the variable ! `global_namespace'. This is the namespace specified with `::' in C++ source code. All other namespaces, types, variables, functions, and so forth can be found starting with this namespace. *************** the representation, the global namespace *** 10003,10062 **** namespace. Thus, in what follows, we describe namespaces generally, rather than the global namespace in particular. ! A namespace is represented by a 'NAMESPACE_DECL' node. ! The following macros and functions can be used on a 'NAMESPACE_DECL': ! 'DECL_NAME' ! This macro is used to obtain the 'IDENTIFIER_NODE' corresponding to the unqualified name of the name of the namespace (*note ! Identifiers::). The name of the global namespace is '::', even ! though in C++ the global namespace is unnamed. However, you should ! use comparison with 'global_namespace', rather than 'DECL_NAME' to ! determine whether or not a namespace is the global one. An unnamed ! namespace will have a 'DECL_NAME' equal to ! 'anonymous_namespace_name'. Within a single translation unit, all unnamed namespaces will have the same name. ! 'DECL_CONTEXT' ! This macro returns the enclosing namespace. The 'DECL_CONTEXT' for ! the 'global_namespace' is 'NULL_TREE'. ! 'DECL_NAMESPACE_ALIAS' If this declaration is for a namespace alias, then ! 'DECL_NAMESPACE_ALIAS' is the namespace for which this one is an alias. ! Do not attempt to use 'cp_namespace_decls' for a namespace which is ! an alias. Instead, follow 'DECL_NAMESPACE_ALIAS' links until you reach an ordinary, non-alias, namespace, and call ! 'cp_namespace_decls' there. ! 'DECL_NAMESPACE_STD_P' ! This predicate holds if the namespace is the special '::std' namespace. ! 'cp_namespace_decls' This function will return the declarations contained in the ! namespace, including types, overloaded functions, other namespaces, ! and so forth. If there are no declarations, this function will ! return 'NULL_TREE'. The declarations are connected through their ! 'TREE_CHAIN' fields. Although most entries on this list will be declarations, ! 'TREE_LIST' nodes may also appear. In this case, the 'TREE_VALUE' ! will be an 'OVERLOAD'. The value of the 'TREE_PURPOSE' is ! unspecified; back ends should ignore this value. As with the other ! kinds of declarations returned by 'cp_namespace_decls', the ! 'TREE_CHAIN' will point to the next declaration in this list. ! For more information on the kinds of declarations that can occur on ! this list, *Note Declarations::. Some declarations will not appear ! on this list. In particular, no 'FIELD_DECL', 'LABEL_DECL', or ! 'PARM_DECL' nodes will appear here. This function cannot be used with namespaces that have ! 'DECL_NAMESPACE_ALIAS' set.  File: gccint.info, Node: Classes, Next: Functions for C++, Prev: Namespaces, Up: C and C++ Trees --- 10155,10215 ---- namespace. Thus, in what follows, we describe namespaces generally, rather than the global namespace in particular. ! A namespace is represented by a `NAMESPACE_DECL' node. ! The following macros and functions can be used on a `NAMESPACE_DECL': ! `DECL_NAME' ! This macro is used to obtain the `IDENTIFIER_NODE' corresponding to the unqualified name of the name of the namespace (*note ! Identifiers::). The name of the global namespace is `::', even ! though in C++ the global namespace is unnamed. However, you ! should use comparison with `global_namespace', rather than ! `DECL_NAME' to determine whether or not a namespace is the global ! one. An unnamed namespace will have a `DECL_NAME' equal to ! `anonymous_namespace_name'. Within a single translation unit, all unnamed namespaces will have the same name. ! `DECL_CONTEXT' ! This macro returns the enclosing namespace. The `DECL_CONTEXT' for ! the `global_namespace' is `NULL_TREE'. ! `DECL_NAMESPACE_ALIAS' If this declaration is for a namespace alias, then ! `DECL_NAMESPACE_ALIAS' is the namespace for which this one is an alias. ! Do not attempt to use `cp_namespace_decls' for a namespace which is ! an alias. Instead, follow `DECL_NAMESPACE_ALIAS' links until you reach an ordinary, non-alias, namespace, and call ! `cp_namespace_decls' there. ! `DECL_NAMESPACE_STD_P' ! This predicate holds if the namespace is the special `::std' namespace. ! `cp_namespace_decls' This function will return the declarations contained in the ! namespace, including types, overloaded functions, other ! namespaces, and so forth. If there are no declarations, this ! function will return `NULL_TREE'. The declarations are connected ! through their `TREE_CHAIN' fields. Although most entries on this list will be declarations, ! `TREE_LIST' nodes may also appear. In this case, the `TREE_VALUE' ! will be an `OVERLOAD'. The value of the `TREE_PURPOSE' is ! unspecified; back ends should ignore this value. As with the ! other kinds of declarations returned by `cp_namespace_decls', the ! `TREE_CHAIN' will point to the next declaration in this list. ! For more information on the kinds of declarations that can occur ! on this list, *Note Declarations::. Some declarations will not ! appear on this list. In particular, no `FIELD_DECL', ! `LABEL_DECL', or `PARM_DECL' nodes will appear here. This function cannot be used with namespaces that have ! `DECL_NAMESPACE_ALIAS' set. !  File: gccint.info, Node: Classes, Next: Functions for C++, Prev: Namespaces, Up: C and C++ Trees *************** File: gccint.info, Node: Classes, Next *** 10067,10302 **** Besides namespaces, the other high-level scoping construct in C++ is the class. (Throughout this manual the term "class" is used to mean the types referred to in the ANSI/ISO C++ Standard as classes; these include ! types defined with the 'class', 'struct', and 'union' keywords.) ! A class type is represented by either a 'RECORD_TYPE' or a ! 'UNION_TYPE'. A class declared with the 'union' tag is represented by a ! 'UNION_TYPE', while classes declared with either the 'struct' or the ! 'class' tag are represented by 'RECORD_TYPE's. You can use the ! 'CLASSTYPE_DECLARED_CLASS' macro to discern whether or not a particular ! type is a 'class' as opposed to a 'struct'. This macro will be true ! only for classes declared with the 'class' tag. ! Almost all non-function members are available on the 'TYPE_FIELDS' list. Given one member, the next can be found by following the ! 'TREE_CHAIN'. You should not depend in any way on the order in which ! fields appear on this list. All nodes on this list will be 'DECL' ! nodes. A 'FIELD_DECL' is used to represent a non-static data member, a ! 'VAR_DECL' is used to represent a static data member, and a 'TYPE_DECL' ! is used to represent a type. Note that the 'CONST_DECL' for an enumeration constant will appear on this list, if the enumeration type ! was declared in the class. (Of course, the 'TYPE_DECL' for the enumeration type will appear here as well.) There are no entries for ! base classes on this list. In particular, there is no 'FIELD_DECL' for the "base-class portion" of an object. ! The 'TYPE_VFIELD' is a compiler-generated field used to point to ! virtual function tables. It may or may not appear on the 'TYPE_FIELDS' ! list. However, back ends should handle the 'TYPE_VFIELD' just like all ! the entries on the 'TYPE_FIELDS' list. ! The function members are available on the 'TYPE_METHODS' list. Again, ! subsequent members are found by following the 'TREE_CHAIN' field. If a function is overloaded, each of the overloaded functions appears; no ! 'OVERLOAD' nodes appear on the 'TYPE_METHODS' list. Implicitly declared ! functions (including default constructors, copy constructors, assignment ! operators, and destructors) will appear on this list as well. Every class has an associated "binfo", which can be obtained with ! 'TYPE_BINFO'. Binfos are used to represent base-classes. The binfo ! given by 'TYPE_BINFO' is the degenerate case, whereby every class is considered to be its own base-class. The base binfos for a particular binfo are held in a vector, whose length is obtained with ! 'BINFO_N_BASE_BINFOS'. The base binfos themselves are obtained with ! 'BINFO_BASE_BINFO' and 'BINFO_BASE_ITERATE'. To add a new binfo, use ! 'BINFO_BASE_APPEND'. The vector of base binfos can be obtained with ! 'BINFO_BASE_BINFOS', but normally you do not need to use that. The ! class type associated with a binfo is given by 'BINFO_TYPE'. It is not ! always the case that 'BINFO_TYPE (TYPE_BINFO (x))', because of typedefs ! and qualified types. Neither is it the case that 'TYPE_BINFO ! (BINFO_TYPE (y))' is the same binfo as 'y'. The reason is that if 'y' ! is a binfo representing a base-class 'B' of a derived class 'D', then ! 'BINFO_TYPE (y)' will be 'B', and 'TYPE_BINFO (BINFO_TYPE (y))' will be ! 'B' as its own base-class, rather than as a base-class of 'D'. ! The access to a base type can be found with 'BINFO_BASE_ACCESS'. This ! will produce 'access_public_node', 'access_private_node' or ! 'access_protected_node'. If bases are always public, ! 'BINFO_BASE_ACCESSES' may be 'NULL'. ! 'BINFO_VIRTUAL_P' is used to specify whether the binfo is inherited ! virtually or not. The other flags, 'BINFO_FLAG_0' to 'BINFO_FLAG_6', can be used for language specific use. The following macros can be used on a tree node representing a class-type. ! 'LOCAL_CLASS_P' This predicate holds if the class is local class _i.e._ declared inside a function body. ! 'TYPE_POLYMORPHIC_P' This predicate holds if the class has at least one virtual function (declared or inherited). ! 'TYPE_HAS_DEFAULT_CONSTRUCTOR' This predicate holds whenever its argument represents a class-type with default constructor. ! 'CLASSTYPE_HAS_MUTABLE' ! 'TYPE_HAS_MUTABLE_P' These predicates hold for a class-type having a mutable data member. ! 'CLASSTYPE_NON_POD_P' This predicate holds only for class-types that are not PODs. ! 'TYPE_HAS_NEW_OPERATOR' ! This predicate holds for a class-type that defines 'operator new'. ! 'TYPE_HAS_ARRAY_NEW_OPERATOR' ! This predicate holds for a class-type for which 'operator new[]' is ! defined. ! 'TYPE_OVERLOADS_CALL_EXPR' This predicate holds for class-type for which the function call ! 'operator()' is overloaded. ! 'TYPE_OVERLOADS_ARRAY_REF' ! This predicate holds for a class-type that overloads 'operator[]' ! 'TYPE_OVERLOADS_ARROW' ! This predicate holds for a class-type for which 'operator->' is overloaded.  File: gccint.info, Node: Functions for C++, Next: Statements for C++, Prev: Classes, Up: C and C++ Trees 10.10.4 Functions for C++ ------------------------- ! A function is represented by a 'FUNCTION_DECL' node. A set of ! overloaded functions is sometimes represented by an 'OVERLOAD' node. ! An 'OVERLOAD' node is not a declaration, so none of the 'DECL_' macros ! should be used on an 'OVERLOAD'. An 'OVERLOAD' node is similar to a ! 'TREE_LIST'. Use 'OVL_CURRENT' to get the function associated with an ! 'OVERLOAD' node; use 'OVL_NEXT' to get the next 'OVERLOAD' node in the ! list of overloaded functions. The macros 'OVL_CURRENT' and 'OVL_NEXT' ! are actually polymorphic; you can use them to work with 'FUNCTION_DECL' ! nodes as well as with overloads. In the case of a 'FUNCTION_DECL', ! 'OVL_CURRENT' will always return the function itself, and 'OVL_NEXT' ! will always be 'NULL_TREE'. ! To determine the scope of a function, you can use the 'DECL_CONTEXT' ! macro. This macro will return the class (either a 'RECORD_TYPE' or a ! 'UNION_TYPE') or namespace (a 'NAMESPACE_DECL') of which the function is ! a member. For a virtual function, this macro returns the class in which ! the function was actually defined, not the base class in which the ! virtual declaration occurred. If a friend function is defined in a class scope, the ! 'DECL_FRIEND_CONTEXT' macro can be used to determine the class in which it was defined. For example, in class C { friend void f() {} }; ! the 'DECL_CONTEXT' for 'f' will be the 'global_namespace', but the ! 'DECL_FRIEND_CONTEXT' will be the 'RECORD_TYPE' for 'C'. ! The following macros and functions can be used on a 'FUNCTION_DECL': ! 'DECL_MAIN_P' This predicate holds for a function that is the program entry point ! '::code'. ! 'DECL_LOCAL_FUNCTION_P' This predicate holds if the function was declared at block scope, even though it has a global scope. ! 'DECL_ANTICIPATED' This predicate holds if the function is a built-in function but its prototype is not yet explicitly declared. ! 'DECL_EXTERN_C_FUNCTION_P' ! This predicate holds if the function is declared as an ''extern "C"'' function. ! 'DECL_LINKONCE_P' ! This macro holds if multiple copies of this function may be emitted ! in various translation units. It is the responsibility of the ! linker to merge the various copies. Template instantiations are ! the most common example of functions for which 'DECL_LINKONCE_P' ! holds; G++ instantiates needed templates in all translation units ! which require them, and then relies on the linker to remove ! duplicate instantiations. FIXME: This macro is not yet implemented. ! 'DECL_FUNCTION_MEMBER_P' This macro holds if the function is a member of a class, rather than a member of a namespace. ! 'DECL_STATIC_FUNCTION_P' This predicate holds if the function a static member function. ! 'DECL_NONSTATIC_MEMBER_FUNCTION_P' This macro holds for a non-static member function. ! 'DECL_CONST_MEMFUNC_P' ! This predicate holds for a 'const'-member function. ! 'DECL_VOLATILE_MEMFUNC_P' ! This predicate holds for a 'volatile'-member function. ! 'DECL_CONSTRUCTOR_P' This macro holds if the function is a constructor. ! 'DECL_NONCONVERTING_P' This predicate holds if the constructor is a non-converting constructor. ! 'DECL_COMPLETE_CONSTRUCTOR_P' This predicate holds for a function which is a constructor for an object of a complete type. ! 'DECL_BASE_CONSTRUCTOR_P' This predicate holds for a function which is a constructor for a base class sub-object. ! 'DECL_COPY_CONSTRUCTOR_P' This predicate holds for a function which is a copy-constructor. ! 'DECL_DESTRUCTOR_P' This macro holds if the function is a destructor. ! 'DECL_COMPLETE_DESTRUCTOR_P' This predicate holds if the function is the destructor for an object a complete type. ! 'DECL_OVERLOADED_OPERATOR_P' This macro holds if the function is an overloaded operator. ! 'DECL_CONV_FN_P' This macro holds if the function is a type-conversion operator. ! 'DECL_GLOBAL_CTOR_P' This predicate holds if the function is a file-scope initialization function. ! 'DECL_GLOBAL_DTOR_P' This predicate holds if the function is a file-scope finalization function. ! 'DECL_THUNK_P' This predicate holds if the function is a thunk. ! These functions represent stub code that adjusts the 'this' pointer and then jumps to another function. When the jumped-to function returns, control is transferred directly to the caller, without ! returning to the thunk. The first parameter to the thunk is always ! the 'this' pointer; the thunk should add 'THUNK_DELTA' to this ! value. (The 'THUNK_DELTA' is an 'int', not an 'INTEGER_CST'.) ! Then, if 'THUNK_VCALL_OFFSET' (an 'INTEGER_CST') is nonzero the ! adjusted 'this' pointer must be adjusted again. The complete calculation is given by the following pseudo-code: this += THUNK_DELTA --- 10220,10456 ---- Besides namespaces, the other high-level scoping construct in C++ is the class. (Throughout this manual the term "class" is used to mean the types referred to in the ANSI/ISO C++ Standard as classes; these include ! types defined with the `class', `struct', and `union' keywords.) ! A class type is represented by either a `RECORD_TYPE' or a ! `UNION_TYPE'. A class declared with the `union' tag is represented by ! a `UNION_TYPE', while classes declared with either the `struct' or the ! `class' tag are represented by `RECORD_TYPE's. You can use the ! `CLASSTYPE_DECLARED_CLASS' macro to discern whether or not a particular ! type is a `class' as opposed to a `struct'. This macro will be true ! only for classes declared with the `class' tag. ! Almost all non-function members are available on the `TYPE_FIELDS' list. Given one member, the next can be found by following the ! `TREE_CHAIN'. You should not depend in any way on the order in which ! fields appear on this list. All nodes on this list will be `DECL' ! nodes. A `FIELD_DECL' is used to represent a non-static data member, a ! `VAR_DECL' is used to represent a static data member, and a `TYPE_DECL' ! is used to represent a type. Note that the `CONST_DECL' for an enumeration constant will appear on this list, if the enumeration type ! was declared in the class. (Of course, the `TYPE_DECL' for the enumeration type will appear here as well.) There are no entries for ! base classes on this list. In particular, there is no `FIELD_DECL' for the "base-class portion" of an object. ! The `TYPE_VFIELD' is a compiler-generated field used to point to ! virtual function tables. It may or may not appear on the `TYPE_FIELDS' ! list. However, back ends should handle the `TYPE_VFIELD' just like all ! the entries on the `TYPE_FIELDS' list. ! The function members are available on the `TYPE_METHODS' list. Again, ! subsequent members are found by following the `TREE_CHAIN' field. If a function is overloaded, each of the overloaded functions appears; no ! `OVERLOAD' nodes appear on the `TYPE_METHODS' list. Implicitly ! declared functions (including default constructors, copy constructors, ! assignment operators, and destructors) will appear on this list as well. Every class has an associated "binfo", which can be obtained with ! `TYPE_BINFO'. Binfos are used to represent base-classes. The binfo ! given by `TYPE_BINFO' is the degenerate case, whereby every class is considered to be its own base-class. The base binfos for a particular binfo are held in a vector, whose length is obtained with ! `BINFO_N_BASE_BINFOS'. The base binfos themselves are obtained with ! `BINFO_BASE_BINFO' and `BINFO_BASE_ITERATE'. To add a new binfo, use ! `BINFO_BASE_APPEND'. The vector of base binfos can be obtained with ! `BINFO_BASE_BINFOS', but normally you do not need to use that. The ! class type associated with a binfo is given by `BINFO_TYPE'. It is not ! always the case that `BINFO_TYPE (TYPE_BINFO (x))', because of typedefs ! and qualified types. Neither is it the case that `TYPE_BINFO ! (BINFO_TYPE (y))' is the same binfo as `y'. The reason is that if `y' ! is a binfo representing a base-class `B' of a derived class `D', then ! `BINFO_TYPE (y)' will be `B', and `TYPE_BINFO (BINFO_TYPE (y))' will be ! `B' as its own base-class, rather than as a base-class of `D'. ! The access to a base type can be found with `BINFO_BASE_ACCESS'. This ! will produce `access_public_node', `access_private_node' or ! `access_protected_node'. If bases are always public, ! `BINFO_BASE_ACCESSES' may be `NULL'. ! `BINFO_VIRTUAL_P' is used to specify whether the binfo is inherited ! virtually or not. The other flags, `BINFO_FLAG_0' to `BINFO_FLAG_6', can be used for language specific use. The following macros can be used on a tree node representing a class-type. ! `LOCAL_CLASS_P' This predicate holds if the class is local class _i.e._ declared inside a function body. ! `TYPE_POLYMORPHIC_P' This predicate holds if the class has at least one virtual function (declared or inherited). ! `TYPE_HAS_DEFAULT_CONSTRUCTOR' This predicate holds whenever its argument represents a class-type with default constructor. ! `CLASSTYPE_HAS_MUTABLE' ! `TYPE_HAS_MUTABLE_P' These predicates hold for a class-type having a mutable data member. ! `CLASSTYPE_NON_POD_P' This predicate holds only for class-types that are not PODs. ! `TYPE_HAS_NEW_OPERATOR' ! This predicate holds for a class-type that defines `operator new'. ! `TYPE_HAS_ARRAY_NEW_OPERATOR' ! This predicate holds for a class-type for which `operator new[]' ! is defined. ! `TYPE_OVERLOADS_CALL_EXPR' This predicate holds for class-type for which the function call ! `operator()' is overloaded. ! `TYPE_OVERLOADS_ARRAY_REF' ! This predicate holds for a class-type that overloads `operator[]' ! `TYPE_OVERLOADS_ARROW' ! This predicate holds for a class-type for which `operator->' is overloaded. +  File: gccint.info, Node: Functions for C++, Next: Statements for C++, Prev: Classes, Up: C and C++ Trees 10.10.4 Functions for C++ ------------------------- ! A function is represented by a `FUNCTION_DECL' node. A set of ! overloaded functions is sometimes represented by an `OVERLOAD' node. ! An `OVERLOAD' node is not a declaration, so none of the `DECL_' macros ! should be used on an `OVERLOAD'. An `OVERLOAD' node is similar to a ! `TREE_LIST'. Use `OVL_CURRENT' to get the function associated with an ! `OVERLOAD' node; use `OVL_NEXT' to get the next `OVERLOAD' node in the ! list of overloaded functions. The macros `OVL_CURRENT' and `OVL_NEXT' ! are actually polymorphic; you can use them to work with `FUNCTION_DECL' ! nodes as well as with overloads. In the case of a `FUNCTION_DECL', ! `OVL_CURRENT' will always return the function itself, and `OVL_NEXT' ! will always be `NULL_TREE'. ! To determine the scope of a function, you can use the `DECL_CONTEXT' ! macro. This macro will return the class (either a `RECORD_TYPE' or a ! `UNION_TYPE') or namespace (a `NAMESPACE_DECL') of which the function ! is a member. For a virtual function, this macro returns the class in ! which the function was actually defined, not the base class in which ! the virtual declaration occurred. If a friend function is defined in a class scope, the ! `DECL_FRIEND_CONTEXT' macro can be used to determine the class in which it was defined. For example, in class C { friend void f() {} }; ! the `DECL_CONTEXT' for `f' will be the `global_namespace', but the ! `DECL_FRIEND_CONTEXT' will be the `RECORD_TYPE' for `C'. ! The following macros and functions can be used on a `FUNCTION_DECL': ! `DECL_MAIN_P' This predicate holds for a function that is the program entry point ! `::code'. ! `DECL_LOCAL_FUNCTION_P' This predicate holds if the function was declared at block scope, even though it has a global scope. ! `DECL_ANTICIPATED' This predicate holds if the function is a built-in function but its prototype is not yet explicitly declared. ! `DECL_EXTERN_C_FUNCTION_P' ! This predicate holds if the function is declared as an ``extern "C"'' function. ! `DECL_LINKONCE_P' ! This macro holds if multiple copies of this function may be ! emitted in various translation units. It is the responsibility of ! the linker to merge the various copies. Template instantiations ! are the most common example of functions for which ! `DECL_LINKONCE_P' holds; G++ instantiates needed templates in all ! translation units which require them, and then relies on the ! linker to remove duplicate instantiations. FIXME: This macro is not yet implemented. ! `DECL_FUNCTION_MEMBER_P' This macro holds if the function is a member of a class, rather than a member of a namespace. ! `DECL_STATIC_FUNCTION_P' This predicate holds if the function a static member function. ! `DECL_NONSTATIC_MEMBER_FUNCTION_P' This macro holds for a non-static member function. ! `DECL_CONST_MEMFUNC_P' ! This predicate holds for a `const'-member function. ! `DECL_VOLATILE_MEMFUNC_P' ! This predicate holds for a `volatile'-member function. ! `DECL_CONSTRUCTOR_P' This macro holds if the function is a constructor. ! `DECL_NONCONVERTING_P' This predicate holds if the constructor is a non-converting constructor. ! `DECL_COMPLETE_CONSTRUCTOR_P' This predicate holds for a function which is a constructor for an object of a complete type. ! `DECL_BASE_CONSTRUCTOR_P' This predicate holds for a function which is a constructor for a base class sub-object. ! `DECL_COPY_CONSTRUCTOR_P' This predicate holds for a function which is a copy-constructor. ! `DECL_DESTRUCTOR_P' This macro holds if the function is a destructor. ! `DECL_COMPLETE_DESTRUCTOR_P' This predicate holds if the function is the destructor for an object a complete type. ! `DECL_OVERLOADED_OPERATOR_P' This macro holds if the function is an overloaded operator. ! `DECL_CONV_FN_P' This macro holds if the function is a type-conversion operator. ! `DECL_GLOBAL_CTOR_P' This predicate holds if the function is a file-scope initialization function. ! `DECL_GLOBAL_DTOR_P' This predicate holds if the function is a file-scope finalization function. ! `DECL_THUNK_P' This predicate holds if the function is a thunk. ! These functions represent stub code that adjusts the `this' pointer and then jumps to another function. When the jumped-to function returns, control is transferred directly to the caller, without ! returning to the thunk. The first parameter to the thunk is ! always the `this' pointer; the thunk should add `THUNK_DELTA' to ! this value. (The `THUNK_DELTA' is an `int', not an `INTEGER_CST'.) ! Then, if `THUNK_VCALL_OFFSET' (an `INTEGER_CST') is nonzero the ! adjusted `this' pointer must be adjusted again. The complete calculation is given by the following pseudo-code: this += THUNK_DELTA *************** the 'DECL_CONTEXT' for 'f' will be the ' *** 10304,10336 **** this += (*((ptrdiff_t **) this))[THUNK_VCALL_OFFSET] Finally, the thunk should jump to the location given by ! 'DECL_INITIAL'; this will always be an expression for the address of a function. ! 'DECL_NON_THUNK_FUNCTION_P' This predicate holds if the function is _not_ a thunk function. ! 'GLOBAL_INIT_PRIORITY' ! If either 'DECL_GLOBAL_CTOR_P' or 'DECL_GLOBAL_DTOR_P' holds, then this gives the initialization priority for the function. The linker will arrange that all functions for which ! 'DECL_GLOBAL_CTOR_P' holds are run in increasing order of priority ! before 'main' is called. When the program exits, all functions for ! which 'DECL_GLOBAL_DTOR_P' holds are run in the reverse order. ! 'TYPE_RAISES_EXCEPTIONS' This macro returns the list of exceptions that a (member-)function ! can raise. The returned list, if non 'NULL', is comprised of nodes ! whose 'TREE_VALUE' represents a type. ! 'TYPE_NOTHROW_P' This predicate holds when the exception-specification of its ! arguments is of the form ''()''. ! 'DECL_ARRAY_DELETE_OPERATOR_P' ! This predicate holds if the function an overloaded 'operator delete[]'.  File: gccint.info, Node: Statements for C++, Next: C++ Expressions, Prev: Functions for C++, Up: C and C++ Trees --- 10458,10491 ---- this += (*((ptrdiff_t **) this))[THUNK_VCALL_OFFSET] Finally, the thunk should jump to the location given by ! `DECL_INITIAL'; this will always be an expression for the address of a function. ! `DECL_NON_THUNK_FUNCTION_P' This predicate holds if the function is _not_ a thunk function. ! `GLOBAL_INIT_PRIORITY' ! If either `DECL_GLOBAL_CTOR_P' or `DECL_GLOBAL_DTOR_P' holds, then this gives the initialization priority for the function. The linker will arrange that all functions for which ! `DECL_GLOBAL_CTOR_P' holds are run in increasing order of priority ! before `main' is called. When the program exits, all functions for ! which `DECL_GLOBAL_DTOR_P' holds are run in the reverse order. ! `TYPE_RAISES_EXCEPTIONS' This macro returns the list of exceptions that a (member-)function ! can raise. The returned list, if non `NULL', is comprised of nodes ! whose `TREE_VALUE' represents a type. ! `TYPE_NOTHROW_P' This predicate holds when the exception-specification of its ! arguments is of the form ``()''. ! `DECL_ARRAY_DELETE_OPERATOR_P' ! This predicate holds if the function an overloaded `operator delete[]'. +  File: gccint.info, Node: Statements for C++, Next: C++ Expressions, Prev: Functions for C++, Up: C and C++ Trees *************** File: gccint.info, Node: Statements for *** 10338,10347 **** -------------------------- A function that has a definition in the current translation unit will ! have a non-'NULL' 'DECL_INITIAL'. However, back ends should not make ! use of the particular value given by 'DECL_INITIAL'. ! The 'DECL_SAVED_TREE' macro will give the complete body of the function. 10.10.5.1 Statements --- 10493,10502 ---- -------------------------- A function that has a definition in the current translation unit will ! have a non-`NULL' `DECL_INITIAL'. However, back ends should not make ! use of the particular value given by `DECL_INITIAL'. ! The `DECL_SAVED_TREE' macro will give the complete body of the function. 10.10.5.1 Statements *************** here, together with a list of the variou *** 10353,10366 **** obtain information about them. There are a few macros that can be used with all statements: ! 'STMT_IS_FULL_EXPR_P' In C++, statements normally constitute "full expressions"; temporaries created during a statement are destroyed when the statement is complete. However, G++ sometimes represents expressions by statements; these statements will not have ! 'STMT_IS_FULL_EXPR_P' set. Temporaries created during such statements should be destroyed when the innermost enclosing ! statement with 'STMT_IS_FULL_EXPR_P' set is exited. Here is the list of the various statement nodes, and the macros used to access them. This documentation describes the use of these nodes in --- 10508,10522 ---- obtain information about them. There are a few macros that can be used with all statements: ! `STMT_IS_FULL_EXPR_P' In C++, statements normally constitute "full expressions"; temporaries created during a statement are destroyed when the statement is complete. However, G++ sometimes represents expressions by statements; these statements will not have ! `STMT_IS_FULL_EXPR_P' set. Temporaries created during such statements should be destroyed when the innermost enclosing ! statement with `STMT_IS_FULL_EXPR_P' set is exited. ! Here is the list of the various statement nodes, and the macros used to access them. This documentation describes the use of these nodes in *************** non-template functions (including instan *** 10368,10379 **** In template functions, the same nodes are used, but sometimes in slightly different ways. ! Many of the statements have substatements. For example, a 'while' loop ! will have a body, which is itself a statement. If the substatement is ! 'NULL_TREE', it is considered equivalent to a statement consisting of a ! single ';', i.e., an expression statement in which the expression has ! been omitted. A substatement may in fact be a list of statements, ! connected via their 'TREE_CHAIN's. So, you should always process the statement tree by looping over substatements, like this: void process_stmt (stmt) tree stmt; --- 10524,10535 ---- In template functions, the same nodes are used, but sometimes in slightly different ways. ! Many of the statements have substatements. For example, a `while' ! loop will have a body, which is itself a statement. If the substatement ! is `NULL_TREE', it is considered equivalent to a statement consisting ! of a single `;', i.e., an expression statement in which the expression ! has been omitted. A substatement may in fact be a list of statements, ! connected via their `TREE_CHAIN's. So, you should always process the statement tree by looping over substatements, like this: void process_stmt (stmt) tree stmt; *************** statement tree by looping over substatem *** 10393,10500 **** stmt = TREE_CHAIN (stmt); } } ! In other words, while the 'then' clause of an 'if' statement in C++ can ! be only one statement (although that one statement may be a compound ! statement), the intermediate representation will sometimes use several ! statements chained together. ! ! 'BREAK_STMT' ! Used to represent a 'break' statement. There are no additional fields. ! 'CILK_SPAWN_STMT' ! Used to represent a spawning function in the Cilk Plus language extension. This tree has one field that holds the name of the ! spawning function. '_Cilk_spawn' can be written in C in the following way: ! _Cilk_spawn (); ! ! Detailed description for usage and functionality of '_Cilk_spawn' ! can be found at http://www.cilkplus.org ! 'CILK_SYNC_STMT' This statement is part of the Cilk Plus language extension. It indicates that the current function cannot continue in parallel with its spawned children. There are no additional fields. ! '_Cilk_sync' can be written in C in the following way: ! ! _Cilk_sync; ! 'CLEANUP_STMT' Used to represent an action that should take place upon exit from the enclosing scope. Typically, these actions are calls to destructors for local objects, but back ends cannot rely on this fact. If these nodes are in fact representing such destructors, ! 'CLEANUP_DECL' will be the 'VAR_DECL' destroyed. Otherwise, ! 'CLEANUP_DECL' will be 'NULL_TREE'. In any case, the ! 'CLEANUP_EXPR' is the expression to execute. The cleanups executed ! on exit from a scope should be run in the reverse order of the ! order in which the associated 'CLEANUP_STMT's were encountered. ! ! 'CONTINUE_STMT' ! Used to represent a 'continue' statement. There are no additional fields. ! 'CTOR_STMT' ! ! Used to mark the beginning (if 'CTOR_BEGIN_P' holds) or end (if ! 'CTOR_END_P' holds of the main body of a constructor. See also ! 'SUBOBJECT' for more information on how to use these nodes. ! ! 'DO_STMT' ! Used to represent a 'do' loop. The body of the loop is given by ! 'DO_BODY' while the termination condition for the loop is given by ! 'DO_COND'. The condition for a 'do'-statement is always an expression. ! 'EMPTY_CLASS_EXPR' ! Used to represent a temporary object of a class with no data whose address is never taken. (All such objects are interchangeable.) ! The 'TREE_TYPE' represents the type of the object. ! ! 'EXPR_STMT' ! Used to represent an expression statement. Use 'EXPR_STMT_EXPR' to obtain the expression. ! 'FOR_STMT' ! ! Used to represent a 'for' statement. The 'FOR_INIT_STMT' is the ! initialization statement for the loop. The 'FOR_COND' is the ! termination condition. The 'FOR_EXPR' is the expression executed ! right before the 'FOR_COND' on each loop iteration; often, this expression increments a counter. The body of the loop is given by ! 'FOR_BODY'. Note that 'FOR_INIT_STMT' and 'FOR_BODY' return ! statements, while 'FOR_COND' and 'FOR_EXPR' return expressions. ! ! 'HANDLER' ! Used to represent a C++ 'catch' block. The 'HANDLER_TYPE' is the type of exception that will be caught by this handler; it is equal ! (by pointer equality) to 'NULL' if this handler is for all types. ! 'HANDLER_PARMS' is the 'DECL_STMT' for the catch parameter, and ! 'HANDLER_BODY' is the code for the block itself. ! ! 'IF_STMT' ! Used to represent an 'if' statement. The 'IF_COND' is the expression. ! If the condition is a 'TREE_LIST', then the 'TREE_PURPOSE' is a ! statement (usually a 'DECL_STMT'). Each time the condition is evaluated, the statement should be executed. Then, the ! 'TREE_VALUE' should be used as the conditional expression itself. This representation is used to handle C++ code like this: ! C++ distinguishes between this and 'COND_EXPR' for handling templates. if (int i = 7) ... --- 10549,10645 ---- stmt = TREE_CHAIN (stmt); } } ! In other words, while the `then' clause of an `if' statement in C++ ! can be only one statement (although that one statement may be a ! compound statement), the intermediate representation will sometimes use ! several statements chained together. ! `BREAK_STMT' ! Used to represent a `break' statement. There are no additional fields. ! `CILK_SPAWN_STMT' Used to represent a spawning function in the Cilk Plus language extension. This tree has one field that holds the name of the ! spawning function. `_Cilk_spawn' can be written in C in the following way: ! `_Cilk_spawn' (); ! Detailed description for usage and functionality of `_Cilk_spawn' ! can be found at `https://www.cilkplus.org'. + `CILK_SYNC_STMT' This statement is part of the Cilk Plus language extension. It indicates that the current function cannot continue in parallel with its spawned children. There are no additional fields. ! `_Cilk_sync' can be written in C in the following way: ! `_Cilk_sync'; + `CLEANUP_STMT' Used to represent an action that should take place upon exit from the enclosing scope. Typically, these actions are calls to destructors for local objects, but back ends cannot rely on this fact. If these nodes are in fact representing such destructors, ! `CLEANUP_DECL' will be the `VAR_DECL' destroyed. Otherwise, ! `CLEANUP_DECL' will be `NULL_TREE'. In any case, the ! `CLEANUP_EXPR' is the expression to execute. The cleanups ! executed on exit from a scope should be run in the reverse order ! of the order in which the associated `CLEANUP_STMT's were ! encountered. ! `CONTINUE_STMT' ! Used to represent a `continue' statement. There are no additional fields. ! `CTOR_STMT' ! Used to mark the beginning (if `CTOR_BEGIN_P' holds) or end (if ! `CTOR_END_P' holds of the main body of a constructor. See also ! `SUBOBJECT' for more information on how to use these nodes. ! `DO_STMT' ! Used to represent a `do' loop. The body of the loop is given by ! `DO_BODY' while the termination condition for the loop is given by ! `DO_COND'. The condition for a `do'-statement is always an expression. ! `EMPTY_CLASS_EXPR' Used to represent a temporary object of a class with no data whose address is never taken. (All such objects are interchangeable.) ! The `TREE_TYPE' represents the type of the object. ! `EXPR_STMT' ! Used to represent an expression statement. Use `EXPR_STMT_EXPR' to obtain the expression. ! `FOR_STMT' ! Used to represent a `for' statement. The `FOR_INIT_STMT' is the ! initialization statement for the loop. The `FOR_COND' is the ! termination condition. The `FOR_EXPR' is the expression executed ! right before the `FOR_COND' on each loop iteration; often, this expression increments a counter. The body of the loop is given by ! `FOR_BODY'. Note that `FOR_INIT_STMT' and `FOR_BODY' return ! statements, while `FOR_COND' and `FOR_EXPR' return expressions. ! `HANDLER' ! Used to represent a C++ `catch' block. The `HANDLER_TYPE' is the type of exception that will be caught by this handler; it is equal ! (by pointer equality) to `NULL' if this handler is for all types. ! `HANDLER_PARMS' is the `DECL_STMT' for the catch parameter, and ! `HANDLER_BODY' is the code for the block itself. ! `IF_STMT' ! Used to represent an `if' statement. The `IF_COND' is the expression. ! If the condition is a `TREE_LIST', then the `TREE_PURPOSE' is a ! statement (usually a `DECL_STMT'). Each time the condition is evaluated, the statement should be executed. Then, the ! `TREE_VALUE' should be used as the conditional expression itself. This representation is used to handle C++ code like this: ! C++ distinguishes between this and `COND_EXPR' for handling templates. if (int i = 7) ... *************** statements chained together. *** 10502,10559 **** where there is a new local variable (or variables) declared within the condition. ! The 'THEN_CLAUSE' represents the statement given by the 'then' ! condition, while the 'ELSE_CLAUSE' represents the statement given ! by the 'else' condition. ! ! 'SUBOBJECT' In a constructor, these nodes are used to mark the point at which a ! subobject of 'this' is fully constructed. If, after this point, an ! exception is thrown before a 'CTOR_STMT' with 'CTOR_END_P' set is ! encountered, the 'SUBOBJECT_CLEANUP' must be executed. The cleanups must be executed in the reverse order in which they appear. ! 'SWITCH_STMT' ! ! Used to represent a 'switch' statement. The 'SWITCH_STMT_COND' is the expression on which the switch is occurring. See the ! documentation for an 'IF_STMT' for more information on the ! representation used for the condition. The 'SWITCH_STMT_BODY' is ! the body of the switch statement. The 'SWITCH_STMT_TYPE' is the original type of switch expression as given in the source, before any compiler conversions. ! 'TRY_BLOCK' ! Used to represent a 'try' block. The body of the try block is ! given by 'TRY_STMTS'. Each of the catch blocks is a 'HANDLER' ! node. The first handler is given by 'TRY_HANDLERS'. Subsequent ! handlers are obtained by following the 'TREE_CHAIN' link from one handler to the next. The body of the handler is given by ! 'HANDLER_BODY'. ! If 'CLEANUP_P' holds of the 'TRY_BLOCK', then the 'TRY_HANDLERS' ! will not be a 'HANDLER' node. Instead, it will be an expression ! that should be executed if an exception is thrown in the try block. ! It must rethrow the exception after executing that code. And, if ! an exception is thrown while the expression is executing, ! 'terminate' must be called. ! 'USING_STMT' ! Used to represent a 'using' directive. The namespace is given by ! 'USING_STMT_NAMESPACE', which will be a NAMESPACE_DECL. This node is needed inside template functions, to implement using directives during instantiation. ! 'WHILE_STMT' ! ! Used to represent a 'while' loop. The 'WHILE_COND' is the termination condition for the loop. See the documentation for an ! 'IF_STMT' for more information on the representation used for the condition. ! The 'WHILE_BODY' is the body of the loop.  File: gccint.info, Node: C++ Expressions, Prev: Statements for C++, Up: C and C++ Trees --- 10647,10702 ---- where there is a new local variable (or variables) declared within the condition. ! The `THEN_CLAUSE' represents the statement given by the `then' ! condition, while the `ELSE_CLAUSE' represents the statement given ! by the `else' condition. + `SUBOBJECT' In a constructor, these nodes are used to mark the point at which a ! subobject of `this' is fully constructed. If, after this point, an ! exception is thrown before a `CTOR_STMT' with `CTOR_END_P' set is ! encountered, the `SUBOBJECT_CLEANUP' must be executed. The cleanups must be executed in the reverse order in which they appear. ! `SWITCH_STMT' ! Used to represent a `switch' statement. The `SWITCH_STMT_COND' is the expression on which the switch is occurring. See the ! documentation for an `IF_STMT' for more information on the ! representation used for the condition. The `SWITCH_STMT_BODY' is ! the body of the switch statement. The `SWITCH_STMT_TYPE' is the original type of switch expression as given in the source, before any compiler conversions. ! `TRY_BLOCK' ! Used to represent a `try' block. The body of the try block is ! given by `TRY_STMTS'. Each of the catch blocks is a `HANDLER' ! node. The first handler is given by `TRY_HANDLERS'. Subsequent ! handlers are obtained by following the `TREE_CHAIN' link from one handler to the next. The body of the handler is given by ! `HANDLER_BODY'. ! If `CLEANUP_P' holds of the `TRY_BLOCK', then the `TRY_HANDLERS' ! will not be a `HANDLER' node. Instead, it will be an expression ! that should be executed if an exception is thrown in the try ! block. It must rethrow the exception after executing that code. ! And, if an exception is thrown while the expression is executing, ! `terminate' must be called. ! `USING_STMT' ! Used to represent a `using' directive. The namespace is given by ! `USING_STMT_NAMESPACE', which will be a NAMESPACE_DECL. This node is needed inside template functions, to implement using directives during instantiation. ! `WHILE_STMT' ! Used to represent a `while' loop. The `WHILE_COND' is the termination condition for the loop. See the documentation for an ! `IF_STMT' for more information on the representation used for the condition. ! The `WHILE_BODY' is the body of the loop. !  File: gccint.info, Node: C++ Expressions, Prev: Statements for C++, Up: C and C++ Trees *************** File: gccint.info, Node: C++ Expression *** 10563,10608 **** This section describes expressions specific to the C and C++ front ends. ! 'TYPEID_EXPR' ! ! Used to represent a 'typeid' expression. ! ! 'NEW_EXPR' ! 'VEC_NEW_EXPR' ! ! Used to represent a call to 'new' and 'new[]' respectively. ! ! 'DELETE_EXPR' ! 'VEC_DELETE_EXPR' ! Used to represent a call to 'delete' and 'delete[]' respectively. ! 'MEMBER_REF' Represents a reference to a member of a class. ! 'THROW_EXPR' ! ! Represents an instance of 'throw' in the program. Operand 0, which ! is the expression to throw, may be 'NULL_TREE'. ! 'AGGR_INIT_EXPR' ! An 'AGGR_INIT_EXPR' represents the initialization as the return value of a function call, or as the result of a constructor. An ! 'AGGR_INIT_EXPR' will only appear as a full-expression, or as the ! second operand of a 'TARGET_EXPR'. 'AGGR_INIT_EXPR's have a ! representation similar to that of 'CALL_EXPR's. You can use the ! 'AGGR_INIT_EXPR_FN' and 'AGGR_INIT_EXPR_ARG' macros to access the function to call and the arguments to pass. ! If 'AGGR_INIT_VIA_CTOR_P' holds of the 'AGGR_INIT_EXPR', then the initialization is via a constructor call. The address of the ! 'AGGR_INIT_EXPR_SLOT' operand, which is always a 'VAR_DECL', is taken, and this value replaces the first argument in the argument list. In either case, the expression is void.  File: gccint.info, Node: Java Trees, Prev: C and C++ Trees, Up: GENERIC --- 10706,10747 ---- This section describes expressions specific to the C and C++ front ends. ! `TYPEID_EXPR' ! Used to represent a `typeid' expression. ! `NEW_EXPR' ! `VEC_NEW_EXPR' ! Used to represent a call to `new' and `new[]' respectively. ! `DELETE_EXPR' ! `VEC_DELETE_EXPR' ! Used to represent a call to `delete' and `delete[]' respectively. + `MEMBER_REF' Represents a reference to a member of a class. ! `THROW_EXPR' ! Represents an instance of `throw' in the program. Operand 0, ! which is the expression to throw, may be `NULL_TREE'. ! `AGGR_INIT_EXPR' ! An `AGGR_INIT_EXPR' represents the initialization as the return value of a function call, or as the result of a constructor. An ! `AGGR_INIT_EXPR' will only appear as a full-expression, or as the ! second operand of a `TARGET_EXPR'. `AGGR_INIT_EXPR's have a ! representation similar to that of `CALL_EXPR's. You can use the ! `AGGR_INIT_EXPR_FN' and `AGGR_INIT_EXPR_ARG' macros to access the function to call and the arguments to pass. ! If `AGGR_INIT_VIA_CTOR_P' holds of the `AGGR_INIT_EXPR', then the initialization is via a constructor call. The address of the ! `AGGR_INIT_EXPR_SLOT' operand, which is always a `VAR_DECL', is taken, and this value replaces the first argument in the argument list. In either case, the expression is void. +  File: gccint.info, Node: Java Trees, Prev: C and C++ Trees, Up: GENERIC *************** File: gccint.info, Node: GIMPLE, Next: *** 10616,10677 **** ********* GIMPLE is a three-address representation derived from GENERIC by ! breaking down GENERIC expressions into tuples of no more than 3 operands ! (with some exceptions like function calls). GIMPLE was heavily ! influenced by the SIMPLE IL used by the McCAT compiler project at McGill ! University, though we have made some different choices. For one thing, ! SIMPLE doesn't support 'goto'. Temporaries are introduced to hold intermediate values needed to ! compute complex expressions. Additionally, all the control structures used in GENERIC are lowered into conditional jumps, lexical scopes are removed and exception regions are converted into an on the side exception region tree. The compiler pass which converts GENERIC into GIMPLE is referred to as ! the 'gimplifier'. The gimplifier works recursively, generating GIMPLE tuples out of the original GENERIC expressions. One of the early implementation strategies used for the GIMPLE representation was to use the same internal data structures used by ! front ends to represent parse trees. This simplified implementation because we could leverage existing functionality and interfaces. However, GIMPLE is a much more restrictive representation than abstract syntax trees (AST), therefore it does not require the full structural complexity provided by the main tree data structure. The GENERIC representation of a function is stored in the ! 'DECL_SAVED_TREE' field of the associated 'FUNCTION_DECL' tree node. It ! is converted to GIMPLE by a call to 'gimplify_function_tree'. If a front end wants to include language-specific tree codes in the tree representation which it provides to the back end, it must provide a ! definition of 'LANG_HOOKS_GIMPLIFY_EXPR' which knows how to convert the ! front end trees to GIMPLE. Usually such a hook will involve much of the ! same code for expanding front end trees to RTL. This function can return fully lowered GIMPLE, or it can return GENERIC trees and let the main gimplifier lower them the rest of the way; this is often simpler. GIMPLE that is not fully lowered is known as "High GIMPLE" and consists ! of the IL before the pass 'pass_lower_cf'. High GIMPLE contains some ! container statements like lexical scopes (represented by 'GIMPLE_BIND') ! and nested expressions (e.g., 'GIMPLE_TRY'), while "Low GIMPLE" exposes ! all of the implicit jumps for control and exception expressions directly ! in the IL and EH region trees. The C and C++ front ends currently convert directly from front end trees to GIMPLE, and hand that off to the back end rather than first converting to GENERIC. Their gimplifier hooks know about all the ! '_STMT' nodes and how to convert them to GENERIC forms. There was some work done on a genericization pass which would run first, but the ! existence of 'STMT_EXPR' meant that in order to convert all of the C statements into GENERIC equivalents would involve walking the entire tree anyway, so it was simpler to lower all the way. This might change in the future if someone writes an optimization pass which would work better with higher-level trees, but currently the optimizers all expect GIMPLE. ! You can request to dump a C-like representation of the GIMPLE form with ! the flag '-fdump-tree-gimple'. * Menu: --- 10755,10816 ---- ********* GIMPLE is a three-address representation derived from GENERIC by ! breaking down GENERIC expressions into tuples of no more than 3 ! operands (with some exceptions like function calls). GIMPLE was ! heavily influenced by the SIMPLE IL used by the McCAT compiler project ! at McGill University, though we have made some different choices. For ! one thing, SIMPLE doesn't support `goto'. Temporaries are introduced to hold intermediate values needed to ! compute complex expressions. Additionally, all the control structures used in GENERIC are lowered into conditional jumps, lexical scopes are removed and exception regions are converted into an on the side exception region tree. The compiler pass which converts GENERIC into GIMPLE is referred to as ! the `gimplifier'. The gimplifier works recursively, generating GIMPLE tuples out of the original GENERIC expressions. One of the early implementation strategies used for the GIMPLE representation was to use the same internal data structures used by ! front ends to represent parse trees. This simplified implementation because we could leverage existing functionality and interfaces. However, GIMPLE is a much more restrictive representation than abstract syntax trees (AST), therefore it does not require the full structural complexity provided by the main tree data structure. The GENERIC representation of a function is stored in the ! `DECL_SAVED_TREE' field of the associated `FUNCTION_DECL' tree node. ! It is converted to GIMPLE by a call to `gimplify_function_tree'. If a front end wants to include language-specific tree codes in the tree representation which it provides to the back end, it must provide a ! definition of `LANG_HOOKS_GIMPLIFY_EXPR' which knows how to convert the ! front end trees to GIMPLE. Usually such a hook will involve much of ! the same code for expanding front end trees to RTL. This function can return fully lowered GIMPLE, or it can return GENERIC trees and let the main gimplifier lower them the rest of the way; this is often simpler. GIMPLE that is not fully lowered is known as "High GIMPLE" and consists ! of the IL before the pass `pass_lower_cf'. High GIMPLE contains some ! container statements like lexical scopes (represented by `GIMPLE_BIND') ! and nested expressions (e.g., `GIMPLE_TRY'), while "Low GIMPLE" exposes ! all of the implicit jumps for control and exception expressions ! directly in the IL and EH region trees. The C and C++ front ends currently convert directly from front end trees to GIMPLE, and hand that off to the back end rather than first converting to GENERIC. Their gimplifier hooks know about all the ! `_STMT' nodes and how to convert them to GENERIC forms. There was some work done on a genericization pass which would run first, but the ! existence of `STMT_EXPR' meant that in order to convert all of the C statements into GENERIC equivalents would involve walking the entire tree anyway, so it was simpler to lower all the way. This might change in the future if someone writes an optimization pass which would work better with higher-level trees, but currently the optimizers all expect GIMPLE. ! You can request to dump a C-like representation of the GIMPLE form ! with the flag `-fdump-tree-gimple'. * Menu: *************** File: gccint.info, Node: Tuple represen *** 10694,10862 **** 11.1 Tuple representation ========================= ! GIMPLE instructions are tuples of variable size divided in two groups: a ! header describing the instruction and its locations, and a variable ! length body with all the operands. Tuples are organized into a hierarchy with 3 main classes of tuples. ! 11.1.1 'gimple' (gsbase) ------------------------ This is the root of the hierarchy, it holds basic information needed by ! most GIMPLE statements. There are some fields that may not be relevant to every GIMPLE statement, but those were moved into the base structure to take advantage of holes left by other fields (thus making the structure more compact). The structure takes 4 words (32 bytes) on 64 bit hosts: Field Size (bits) ! 'code' 8 ! 'subcode' 16 ! 'no_warning' 1 ! 'visited' 1 ! 'nontemporal_move' 1 ! 'plf' 2 ! 'modified' 1 ! 'has_volatile_ops' 1 ! 'references_memory_p' 1 ! 'uid' 32 ! 'location' 32 ! 'num_ops' 32 ! 'bb' 64 ! 'block' 63 Total size 32 bytes ! * 'code' Main identifier for a GIMPLE instruction. ! * 'subcode' Used to distinguish different variants of the same basic ! instruction or provide flags applicable to a given code. The ! 'subcode' flags field has different uses depending on the code of the instruction, but mostly it distinguishes instructions of the ! same family. The most prominent use of this field is in assignments, where subcode indicates the operation done on the RHS ! of the assignment. For example, a = b + c is encoded as ! 'GIMPLE_ASSIGN '. ! * 'no_warning' Bitflag to indicate whether a warning has already been ! issued on this statement. ! * 'visited' General purpose "visited" marker. Set and cleared by each pass when needed. ! * 'nontemporal_move' Bitflag used in assignments that represent non-temporal moves. Although this bitflag is only used in assignments, it was moved into the base to take advantage of the bit holes left by the previous fields. ! * 'plf' Pass Local Flags. This 2-bit mask can be used as general ! purpose markers by any pass. Passes are responsible for clearing and setting these two flags accordingly. ! * 'modified' Bitflag to indicate whether the statement has been modified. Used mainly by the operand scanner to determine when to re-scan a statement for operands. ! * 'has_volatile_ops' Bitflag to indicate whether this statement contains operands that have been marked volatile. ! * 'references_memory_p' Bitflag to indicate whether this statement contains memory references (i.e., its operands are either global variables, or pointer dereferences or anything that must reside in memory). ! * 'uid' This is an unsigned integer used by passes that want to ! assign IDs to every statement. These IDs must be assigned and used by each pass. ! * 'location' This is a 'location_t' identifier to specify source code ! location for this statement. It is inherited from the front end. ! * 'num_ops' Number of operands that this statement has. This specifies the size of the operand vector embedded in the tuple. Only used in some tuples, but it is declared in the base tuple to take advantage of the 32-bit hole left by the previous fields. ! * 'bb' Basic block holding the instruction. ! * 'block' Lexical block holding this statement. Also used for debug information generation. ! 11.1.2 'gimple_statement_with_ops' ---------------------------------- ! This tuple is actually split in two: 'gimple_statement_with_ops_base' ! and 'gimple_statement_with_ops'. This is needed to accommodate the way ! the operand vector is allocated. The operand vector is defined to be an ! array of 1 element. So, to allocate a dynamic number of operands, the ! memory allocator ('gimple_alloc') simply allocates enough memory to hold ! the structure itself plus 'N - 1' operands which run "off the end" of ! the structure. For example, to allocate space for a tuple with 3 ! operands, 'gimple_alloc' reserves 'sizeof (struct gimple_statement_with_ops) + 2 * sizeof (tree)' bytes. On the other hand, several fields in this tuple need to be shared with ! the 'gimple_statement_with_memory_ops' tuple. So, these common fields ! are placed in 'gimple_statement_with_ops_base' which is then inherited from the other two tuples. ! 'gsbase' 256 ! 'def_ops' 64 ! 'use_ops' 64 ! 'op' 'num_ops' * 64 ! Total 48 + 8 * 'num_ops' bytes ! size ! * 'gsbase' Inherited from 'struct gimple'. ! * 'def_ops' Array of pointers into the operand array indicating all the slots that contain a variable written-to by the statement. ! This array is also used for immediate use chaining. Note that it would be possible to not rely on this array, but the changes required to implement this are pretty invasive. ! * 'use_ops' Similar to 'def_ops' but for variables read by the statement. ! * 'op' Array of trees with 'num_ops' slots. ! 11.1.3 'gimple_statement_with_memory_ops' ----------------------------------------- ! This tuple is essentially identical to 'gimple_statement_with_ops', except that it contains 4 additional fields to hold vectors related ! memory stores and loads. Similar to the previous case, the structure is ! split in two to accommodate for the operand vector ! ('gimple_statement_with_memory_ops_base' and ! 'gimple_statement_with_memory_ops'). Field Size (bits) ! 'gsbase' 256 ! 'def_ops' 64 ! 'use_ops' 64 ! 'vdef_ops' 64 ! 'vuse_ops' 64 ! 'stores' 64 ! 'loads' 64 ! 'op' 'num_ops' * 64 ! Total size 80 + 8 * 'num_ops' bytes ! * 'vdef_ops' Similar to 'def_ops' but for 'VDEF' operators. There is ! one entry per memory symbol written by this statement. This is used to maintain the memory SSA use-def and def-def chains. ! * 'vuse_ops' Similar to 'use_ops' but for 'VUSE' operators. There is ! one entry per memory symbol loaded by this statement. This is used to maintain the memory SSA use-def chains. ! * 'stores' Bitset with all the UIDs for the symbols written-to by the ! statement. This is different than 'vdef_ops' in that all the ! affected symbols are mentioned in this set. If memory partitioning ! is enabled, the 'vdef_ops' vector will refer to memory partitions. ! Furthermore, no SSA information is stored in this set. ! * 'loads' Similar to 'stores', but for memory loads. (Note that ! there is some amount of redundancy here, it should be possible to ! reduce memory utilization further by removing these sets). All the other tuples are defined in terms of these three basic ones. Each tuple will add some fields. --- 10833,11000 ---- 11.1 Tuple representation ========================= ! GIMPLE instructions are tuples of variable size divided in two groups: ! a header describing the instruction and its locations, and a variable ! length body with all the operands. Tuples are organized into a hierarchy with 3 main classes of tuples. ! 11.1.1 `gimple' (gsbase) ------------------------ This is the root of the hierarchy, it holds basic information needed by ! most GIMPLE statements. There are some fields that may not be relevant to every GIMPLE statement, but those were moved into the base structure to take advantage of holes left by other fields (thus making the structure more compact). The structure takes 4 words (32 bytes) on 64 bit hosts: Field Size (bits) ! `code' 8 ! `subcode' 16 ! `no_warning' 1 ! `visited' 1 ! `nontemporal_move' 1 ! `plf' 2 ! `modified' 1 ! `has_volatile_ops' 1 ! `references_memory_p' 1 ! `uid' 32 ! `location' 32 ! `num_ops' 32 ! `bb' 64 ! `block' 63 Total size 32 bytes ! * `code' Main identifier for a GIMPLE instruction. ! * `subcode' Used to distinguish different variants of the same basic ! instruction or provide flags applicable to a given code. The ! `subcode' flags field has different uses depending on the code of the instruction, but mostly it distinguishes instructions of the ! same family. The most prominent use of this field is in assignments, where subcode indicates the operation done on the RHS ! of the assignment. For example, a = b + c is encoded as ! `GIMPLE_ASSIGN '. ! * `no_warning' Bitflag to indicate whether a warning has already ! been issued on this statement. ! * `visited' General purpose "visited" marker. Set and cleared by each pass when needed. ! * `nontemporal_move' Bitflag used in assignments that represent non-temporal moves. Although this bitflag is only used in assignments, it was moved into the base to take advantage of the bit holes left by the previous fields. ! * `plf' Pass Local Flags. This 2-bit mask can be used as general ! purpose markers by any pass. Passes are responsible for clearing and setting these two flags accordingly. ! * `modified' Bitflag to indicate whether the statement has been modified. Used mainly by the operand scanner to determine when to re-scan a statement for operands. ! * `has_volatile_ops' Bitflag to indicate whether this statement contains operands that have been marked volatile. ! * `references_memory_p' Bitflag to indicate whether this statement contains memory references (i.e., its operands are either global variables, or pointer dereferences or anything that must reside in memory). ! * `uid' This is an unsigned integer used by passes that want to ! assign IDs to every statement. These IDs must be assigned and used by each pass. ! * `location' This is a `location_t' identifier to specify source code ! location for this statement. It is inherited from the front end. ! * `num_ops' Number of operands that this statement has. This specifies the size of the operand vector embedded in the tuple. Only used in some tuples, but it is declared in the base tuple to take advantage of the 32-bit hole left by the previous fields. ! * `bb' Basic block holding the instruction. ! * `block' Lexical block holding this statement. Also used for debug information generation. ! 11.1.2 `gimple_statement_with_ops' ---------------------------------- ! This tuple is actually split in two: `gimple_statement_with_ops_base' ! and `gimple_statement_with_ops'. This is needed to accommodate the way ! the operand vector is allocated. The operand vector is defined to be an ! array of 1 element. So, to allocate a dynamic number of operands, the ! memory allocator (`gimple_alloc') simply allocates enough memory to ! hold the structure itself plus `N - 1' operands which run "off the end" ! of the structure. For example, to allocate space for a tuple with 3 ! operands, `gimple_alloc' reserves `sizeof (struct gimple_statement_with_ops) + 2 * sizeof (tree)' bytes. On the other hand, several fields in this tuple need to be shared with ! the `gimple_statement_with_memory_ops' tuple. So, these common fields ! are placed in `gimple_statement_with_ops_base' which is then inherited from the other two tuples. ! `gsbase' 256 ! `def_ops' 64 ! `use_ops' 64 ! `op' `num_ops' * 64 ! Total size 48 + 8 * `num_ops' bytes ! * `gsbase' Inherited from `struct gimple'. ! * `def_ops' Array of pointers into the operand array indicating all the slots that contain a variable written-to by the statement. ! This array is also used for immediate use chaining. Note that it would be possible to not rely on this array, but the changes required to implement this are pretty invasive. ! * `use_ops' Similar to `def_ops' but for variables read by the statement. ! * `op' Array of trees with `num_ops' slots. ! 11.1.3 `gimple_statement_with_memory_ops' ----------------------------------------- ! This tuple is essentially identical to `gimple_statement_with_ops', except that it contains 4 additional fields to hold vectors related ! memory stores and loads. Similar to the previous case, the structure ! is split in two to accommodate for the operand vector ! (`gimple_statement_with_memory_ops_base' and ! `gimple_statement_with_memory_ops'). Field Size (bits) ! `gsbase' 256 ! `def_ops' 64 ! `use_ops' 64 ! `vdef_ops' 64 ! `vuse_ops' 64 ! `stores' 64 ! `loads' 64 ! `op' `num_ops' * 64 ! Total size 80 + 8 * `num_ops' bytes ! * `vdef_ops' Similar to `def_ops' but for `VDEF' operators. There is ! one entry per memory symbol written by this statement. This is used to maintain the memory SSA use-def and def-def chains. ! * `vuse_ops' Similar to `use_ops' but for `VUSE' operators. There is ! one entry per memory symbol loaded by this statement. This is used to maintain the memory SSA use-def chains. ! * `stores' Bitset with all the UIDs for the symbols written-to by the ! statement. This is different than `vdef_ops' in that all the ! affected symbols are mentioned in this set. If memory ! partitioning is enabled, the `vdef_ops' vector will refer to memory ! partitions. Furthermore, no SSA information is stored in this set. ! * `loads' Similar to `stores', but for memory loads. (Note that there ! is some amount of redundancy here, it should be possible to reduce ! memory utilization further by removing these sets). All the other tuples are defined in terms of these three basic ones. Each tuple will add some fields. *************** File: gccint.info, Node: Class hierarch *** 10868,10875 **** ========================================= The following diagram shows the C++ inheritance hierarchy of statement ! kinds, along with their relationships to 'GSS_' values (layouts) and ! 'GIMPLE_' values (codes): gimple | layout: GSS_BASE --- 11006,11013 ---- ========================================= The following diagram shows the C++ inheritance hierarchy of statement ! kinds, along with their relationships to `GSS_' values (layouts) and ! `GIMPLE_' values (codes): gimple | layout: GSS_BASE *************** File: gccint.info, Node: GIMPLE instruc *** 11013,11047 **** The following table briefly describes the GIMPLE instruction set. Instruction High GIMPLE Low GIMPLE ! 'GIMPLE_ASM' x x ! 'GIMPLE_ASSIGN' x x ! 'GIMPLE_BIND' x ! 'GIMPLE_CALL' x x ! 'GIMPLE_CATCH' x ! 'GIMPLE_COND' x x ! 'GIMPLE_DEBUG' x x ! 'GIMPLE_EH_FILTER' x ! 'GIMPLE_GOTO' x x ! 'GIMPLE_LABEL' x x ! 'GIMPLE_NOP' x x ! 'GIMPLE_OMP_ATOMIC_LOAD' x x ! 'GIMPLE_OMP_ATOMIC_STORE' x x ! 'GIMPLE_OMP_CONTINUE' x x ! 'GIMPLE_OMP_CRITICAL' x x ! 'GIMPLE_OMP_FOR' x x ! 'GIMPLE_OMP_MASTER' x x ! 'GIMPLE_OMP_ORDERED' x x ! 'GIMPLE_OMP_PARALLEL' x x ! 'GIMPLE_OMP_RETURN' x x ! 'GIMPLE_OMP_SECTION' x x ! 'GIMPLE_OMP_SECTIONS' x x ! 'GIMPLE_OMP_SECTIONS_SWITCH' x x ! 'GIMPLE_OMP_SINGLE' x x ! 'GIMPLE_PHI' x ! 'GIMPLE_RESX' x ! 'GIMPLE_RETURN' x x ! 'GIMPLE_SWITCH' x x ! 'GIMPLE_TRY' x  File: gccint.info, Node: GIMPLE Exception Handling, Next: Temporaries, Prev: GIMPLE instruction set, Up: GIMPLE --- 11151,11185 ---- The following table briefly describes the GIMPLE instruction set. Instruction High GIMPLE Low GIMPLE ! `GIMPLE_ASM' x x ! `GIMPLE_ASSIGN' x x ! `GIMPLE_BIND' x ! `GIMPLE_CALL' x x ! `GIMPLE_CATCH' x ! `GIMPLE_COND' x x ! `GIMPLE_DEBUG' x x ! `GIMPLE_EH_FILTER' x ! `GIMPLE_GOTO' x x ! `GIMPLE_LABEL' x x ! `GIMPLE_NOP' x x ! `GIMPLE_OMP_ATOMIC_LOAD' x x ! `GIMPLE_OMP_ATOMIC_STORE' x x ! `GIMPLE_OMP_CONTINUE' x x ! `GIMPLE_OMP_CRITICAL' x x ! `GIMPLE_OMP_FOR' x x ! `GIMPLE_OMP_MASTER' x x ! `GIMPLE_OMP_ORDERED' x x ! `GIMPLE_OMP_PARALLEL' x x ! `GIMPLE_OMP_RETURN' x x ! `GIMPLE_OMP_SECTION' x x ! `GIMPLE_OMP_SECTIONS' x x ! `GIMPLE_OMP_SECTIONS_SWITCH' x x ! `GIMPLE_OMP_SINGLE' x x ! `GIMPLE_PHI' x ! `GIMPLE_RESX' x ! `GIMPLE_RETURN' x x ! `GIMPLE_SWITCH' x x ! `GIMPLE_TRY' x  File: gccint.info, Node: GIMPLE Exception Handling, Next: Temporaries, Prev: GIMPLE instruction set, Up: GIMPLE *************** File: gccint.info, Node: GIMPLE Excepti *** 11050,11087 **** ======================= Other exception handling constructs are represented using ! 'GIMPLE_TRY_CATCH'. 'GIMPLE_TRY_CATCH' has two operands. The first operand is a sequence of statements to execute. If executing these statements does not throw an exception, then the second operand is ignored. Otherwise, if an exception is thrown, then the second operand ! of the 'GIMPLE_TRY_CATCH' is checked. The second operand may have the following forms: 1. A sequence of statements to execute. When an exception occurs, these statements are executed, and then the exception is rethrown. ! 2. A sequence of 'GIMPLE_CATCH' statements. Each 'GIMPLE_CATCH' has a ! list of applicable exception types and handler code. If the thrown ! exception matches one of the caught types, the associated handler ! code is executed. If the handler code falls off the bottom, ! execution continues after the original 'GIMPLE_TRY_CATCH'. ! 3. A 'GIMPLE_EH_FILTER' statement. This has a list of permitted ! exception types, and code to handle a match failure. If the thrown ! exception does not match one of the allowed types, the associated ! match failure code is executed. If the thrown exception does ! match, it continues unwinding the stack looking for the next handler. Currently throwing an exception is not directly represented in GIMPLE, since it is implemented by calling a function. At some point in the future we will want to add some way to express that the call will throw an exception of a known type. Just before running the optimizers, the compiler lowers the high-level ! EH constructs above into a set of 'goto's, magic labels, and EH regions. ! Continuing to unwind at the end of a cleanup is represented with a ! 'GIMPLE_RESX'.  File: gccint.info, Node: Temporaries, Next: Operands, Prev: GIMPLE Exception Handling, Up: GIMPLE --- 11188,11226 ---- ======================= Other exception handling constructs are represented using ! `GIMPLE_TRY_CATCH'. `GIMPLE_TRY_CATCH' has two operands. The first operand is a sequence of statements to execute. If executing these statements does not throw an exception, then the second operand is ignored. Otherwise, if an exception is thrown, then the second operand ! of the `GIMPLE_TRY_CATCH' is checked. The second operand may have the following forms: 1. A sequence of statements to execute. When an exception occurs, these statements are executed, and then the exception is rethrown. ! 2. A sequence of `GIMPLE_CATCH' statements. Each `GIMPLE_CATCH' has ! a list of applicable exception types and handler code. If the ! thrown exception matches one of the caught types, the associated ! handler code is executed. If the handler code falls off the ! bottom, execution continues after the original `GIMPLE_TRY_CATCH'. ! 3. A `GIMPLE_EH_FILTER' statement. This has a list of permitted ! exception types, and code to handle a match failure. If the ! thrown exception does not match one of the allowed types, the ! associated match failure code is executed. If the thrown exception ! does match, it continues unwinding the stack looking for the next handler. + Currently throwing an exception is not directly represented in GIMPLE, since it is implemented by calling a function. At some point in the future we will want to add some way to express that the call will throw an exception of a known type. Just before running the optimizers, the compiler lowers the high-level ! EH constructs above into a set of `goto's, magic labels, and EH ! regions. Continuing to unwind at the end of a cleanup is represented ! with a `GIMPLE_RESX'.  File: gccint.info, Node: Temporaries, Next: Operands, Prev: GIMPLE Exception Handling, Up: GIMPLE *************** File: gccint.info, Node: Temporaries, *** 11090,11108 **** ================ When gimplification encounters a subexpression that is too complex, it ! creates a new temporary variable to hold the value of the subexpression, ! and adds a new statement to initialize it before the current statement. ! These special temporaries are known as 'expression temporaries', and are ! allocated using 'get_formal_tmp_var'. The compiler tries to always ! evaluate identical expressions into the same temporary, to simplify ! elimination of redundant calculations. ! We can only use expression temporaries when we know that it will not be ! reevaluated before its value is used, and that it will not be otherwise ! modified(1). Other temporaries can be allocated using ! 'get_initialized_tmp_var' or 'create_tmp_var'. ! Currently, an expression like 'a = b + 5' is not reduced any further. We tried converting it to something like T1 = b + 5; a = T1; --- 11229,11247 ---- ================ When gimplification encounters a subexpression that is too complex, it ! creates a new temporary variable to hold the value of the ! subexpression, and adds a new statement to initialize it before the ! current statement. These special temporaries are known as `expression ! temporaries', and are allocated using `get_formal_tmp_var'. The ! compiler tries to always evaluate identical expressions into the same ! temporary, to simplify elimination of redundant calculations. ! We can only use expression temporaries when we know that it will not ! be reevaluated before its value is used, and that it will not be ! otherwise modified(1). Other temporaries can be allocated using ! `get_initialized_tmp_var' or `create_tmp_var'. ! Currently, an expression like `a = b + 5' is not reduced any further. We tried converting it to something like T1 = b + 5; a = T1; *************** value is explicitly loaded into a tempor *** 11112,11120 **** the value of an expression to a memory variable goes through a temporary. ! ---------- Footnotes ---------- ! (1) These restrictions are derived from those in Morgan 4.8.  File: gccint.info, Node: Operands, Next: Manipulating GIMPLE statements, Prev: Temporaries, Up: GIMPLE --- 11251,11259 ---- the value of an expression to a memory variable goes through a temporary. ! ---------- Footnotes ---------- ! (1) These restrictions are derived from those in Morgan 4.8.  File: gccint.info, Node: Operands, Next: Manipulating GIMPLE statements, Prev: Temporaries, Up: GIMPLE *************** File: gccint.info, Node: Operands, Nex *** 11124,11140 **** In general, expressions in GIMPLE consist of an operation and the appropriate number of simple operands; these operands must either be a ! GIMPLE rvalue ('is_gimple_val'), i.e. a constant or a register variable. ! More complex operands are factored out into temporaries, so that a = b + c + d becomes T1 = b + c; a = T1 + d; ! The same rule holds for arguments to a 'GIMPLE_CALL'. The target of an assignment is usually a variable, but can also be a ! 'MEM_REF' or a compound lvalue as described below. * Menu: --- 11263,11280 ---- In general, expressions in GIMPLE consist of an operation and the appropriate number of simple operands; these operands must either be a ! GIMPLE rvalue (`is_gimple_val'), i.e. a constant or a register ! variable. More complex operands are factored out into temporaries, so ! that a = b + c + d becomes T1 = b + c; a = T1 + d; ! The same rule holds for arguments to a `GIMPLE_CALL'. The target of an assignment is usually a variable, but can also be a ! `MEM_REF' or a compound lvalue as described below. * Menu: *************** File: gccint.info, Node: Compound Lvalu *** 11159,11165 **** ----------------------- Currently compound lvalues involving array and structure field ! references are not broken down; an expression like 'a.b[2] = 42' is not reduced any further (though complex array subscripts are). This restriction is a workaround for limitations in later optimizers; if we were to convert this to --- 11299,11305 ---- ----------------------- Currently compound lvalues involving array and structure field ! references are not broken down; an expression like `a.b[2] = 42' is not reduced any further (though complex array subscripts are). This restriction is a workaround for limitations in later optimizers; if we were to convert this to *************** were to convert this to *** 11167,11175 **** T1 = &a.b; T1[2] = 42; ! alias analysis would not remember that the reference to 'T1[2]' came by ! way of 'a.b', so it would think that the assignment could alias another ! member of 'a'; this broke 'struct-alias-1.c'. Future optimizer improvements may make this limitation unnecessary.  --- 11307,11315 ---- T1 = &a.b; T1[2] = 42; ! alias analysis would not remember that the reference to `T1[2]' came ! by way of `a.b', so it would think that the assignment could alias ! another member of `a'; this broke `struct-alias-1.c'. Future optimizer improvements may make this limitation unnecessary.  *************** File: gccint.info, Node: Conditional Ex *** 11178,11185 **** 11.6.3 Conditional Expressions ------------------------------ ! A C '?:' expression is converted into an 'if' statement with each branch ! assigning to the same temporary. So, a = b ? c : d; becomes --- 11318,11325 ---- 11.6.3 Conditional Expressions ------------------------------ ! A C `?:' expression is converted into an `if' statement with each ! branch assigning to the same temporary. So, a = b ? c : d; becomes *************** assigning to the same temporary. So, *** 11189,11200 **** T1 = d; a = T1; ! The GIMPLE level if-conversion pass re-introduces '?:' expression, if ! appropriate. It is used to vectorize loops with conditions using vector conditional operations. ! Note that in GIMPLE, 'if' statements are represented using ! 'GIMPLE_COND', as described below.  File: gccint.info, Node: Logical Operators, Prev: Conditional Expressions, Up: Operands --- 11329,11340 ---- T1 = d; a = T1; ! The GIMPLE level if-conversion pass re-introduces `?:' expression, if ! appropriate. It is used to vectorize loops with conditions using vector conditional operations. ! Note that in GIMPLE, `if' statements are represented using ! `GIMPLE_COND', as described below.  File: gccint.info, Node: Logical Operators, Prev: Conditional Expressions, Up: Operands *************** File: gccint.info, Node: Logical Operat *** 11202,11254 **** 11.6.4 Logical Operators ------------------------ ! Except when they appear in the condition operand of a 'GIMPLE_COND', ! logical 'and' and 'or' operators are simplified as follows: 'a = b && c' ! becomes T1 = (bool)b; if (T1 == true) T1 = (bool)c; a = T1; ! Note that 'T1' in this example cannot be an expression temporary, because it has two different assignments. 11.6.5 Manipulating operands ---------------------------- ! All gimple operands are of type 'tree'. But only certain types of trees ! are allowed to be used as operand tuples. Basic validation is ! controlled by the function 'get_gimple_rhs_class', which given a tree ! code, returns an 'enum' with the following values of type 'enum gimple_rhs_class' ! * 'GIMPLE_INVALID_RHS' The tree cannot be used as a GIMPLE operand. ! * 'GIMPLE_TERNARY_RHS' The tree is a valid GIMPLE ternary operation. ! * 'GIMPLE_BINARY_RHS' The tree is a valid GIMPLE binary operation. ! * 'GIMPLE_UNARY_RHS' The tree is a valid GIMPLE unary operation. ! * 'GIMPLE_SINGLE_RHS' The tree is a single object, that cannot be ! split into simpler operands (for instance, 'SSA_NAME', 'VAR_DECL', ! 'COMPONENT_REF', etc). ! This operand class also acts as an escape hatch for tree nodes that ! may be flattened out into the operand vector, but would need more ! than two slots on the RHS. For instance, a 'COND_EXPR' expression ! of the form '(a op b) ? x : y' could be flattened out on the ! operand vector using 4 slots, but it would also require additional ! processing to distinguish 'c = a op b' from 'c = a op b ? x : y'. ! Something similar occurs with 'ASSERT_EXPR'. In time, these ! special case tree expressions should be flattened into the operand ! vector. ! For tree nodes in the categories 'GIMPLE_TERNARY_RHS', ! 'GIMPLE_BINARY_RHS' and 'GIMPLE_UNARY_RHS', they cannot be stored inside ! tuples directly. They first need to be flattened and separated into ! individual components. For instance, given the GENERIC expression a = b + c --- 11342,11394 ---- 11.6.4 Logical Operators ------------------------ ! Except when they appear in the condition operand of a `GIMPLE_COND', ! logical `and' and `or' operators are simplified as follows: `a = b && ! c' becomes T1 = (bool)b; if (T1 == true) T1 = (bool)c; a = T1; ! Note that `T1' in this example cannot be an expression temporary, because it has two different assignments. 11.6.5 Manipulating operands ---------------------------- ! All gimple operands are of type `tree'. But only certain types of ! trees are allowed to be used as operand tuples. Basic validation is ! controlled by the function `get_gimple_rhs_class', which given a tree ! code, returns an `enum' with the following values of type `enum gimple_rhs_class' ! * `GIMPLE_INVALID_RHS' The tree cannot be used as a GIMPLE operand. ! * `GIMPLE_TERNARY_RHS' The tree is a valid GIMPLE ternary operation. ! * `GIMPLE_BINARY_RHS' The tree is a valid GIMPLE binary operation. ! * `GIMPLE_UNARY_RHS' The tree is a valid GIMPLE unary operation. ! * `GIMPLE_SINGLE_RHS' The tree is a single object, that cannot be ! split into simpler operands (for instance, `SSA_NAME', `VAR_DECL', ! `COMPONENT_REF', etc). ! This operand class also acts as an escape hatch for tree nodes ! that may be flattened out into the operand vector, but would need ! more than two slots on the RHS. For instance, a `COND_EXPR' ! expression of the form `(a op b) ? x : y' could be flattened out ! on the operand vector using 4 slots, but it would also require ! additional processing to distinguish `c = a op b' from `c = a op b ! ? x : y'. Something similar occurs with `ASSERT_EXPR'. In time, ! these special case tree expressions should be flattened into the ! operand vector. ! For tree nodes in the categories `GIMPLE_TERNARY_RHS', ! `GIMPLE_BINARY_RHS' and `GIMPLE_UNARY_RHS', they cannot be stored ! inside tuples directly. They first need to be flattened and separated ! into individual components. For instance, given the GENERIC expression a = b + c *************** individual components. For instance, gi *** 11256,11297 **** MODIFY_EXPR , PLUS_EXPR , VAR_DECL >> ! In this case, the GIMPLE form for this statement is logically identical ! to its GENERIC form but in GIMPLE, the 'PLUS_EXPR' on the RHS of the ! assignment is not represented as a tree, instead the two operands are ! taken out of the 'PLUS_EXPR' sub-tree and flattened into the GIMPLE ! tuple as follows: GIMPLE_ASSIGN , VAR_DECL , VAR_DECL > 11.6.6 Operand vector allocation -------------------------------- ! The operand vector is stored at the bottom of the three tuple structures ! that accept operands. This means, that depending on the code of a given ! statement, its operand vector will be at different offsets from the base ! of the structure. To access tuple operands use the following accessors -- GIMPLE function: unsigned gimple_num_ops (gimple g) Returns the number of operands in statement G. -- GIMPLE function: tree gimple_op (gimple g, unsigned i) ! Returns operand 'I' from statement 'G'. -- GIMPLE function: tree * gimple_ops (gimple g) ! Returns a pointer into the operand vector for statement 'G'. This ! is computed using an internal table called 'gimple_ops_offset_'[]. ! This table is indexed by the gimple code of 'G'. ! When the compiler is built, this table is filled-in using the sizes ! of the structures used by each statement code defined in gimple.def. Since the operand vector is at the bottom of the ! structure, for a gimple code 'C' the offset is computed as sizeof ! (struct-of 'C') - sizeof (tree). This mechanism adds one memory indirection to every access when ! using 'gimple_op'(), if this becomes a bottleneck, a pass can ! choose to memoize the result from 'gimple_ops'() and use that to access the operands. 11.6.7 Operand validation --- 11396,11438 ---- MODIFY_EXPR , PLUS_EXPR , VAR_DECL >> ! In this case, the GIMPLE form for this statement is logically ! identical to its GENERIC form but in GIMPLE, the `PLUS_EXPR' on the RHS ! of the assignment is not represented as a tree, instead the two ! operands are taken out of the `PLUS_EXPR' sub-tree and flattened into ! the GIMPLE tuple as follows: GIMPLE_ASSIGN , VAR_DECL , VAR_DECL > 11.6.6 Operand vector allocation -------------------------------- ! The operand vector is stored at the bottom of the three tuple ! structures that accept operands. This means, that depending on the code ! of a given statement, its operand vector will be at different offsets ! from the base of the structure. To access tuple operands use the ! following accessors -- GIMPLE function: unsigned gimple_num_ops (gimple g) Returns the number of operands in statement G. -- GIMPLE function: tree gimple_op (gimple g, unsigned i) ! Returns operand `I' from statement `G'. -- GIMPLE function: tree * gimple_ops (gimple g) ! Returns a pointer into the operand vector for statement `G'. This ! is computed using an internal table called `gimple_ops_offset_'[]. ! This table is indexed by the gimple code of `G'. ! When the compiler is built, this table is filled-in using the ! sizes of the structures used by each statement code defined in gimple.def. Since the operand vector is at the bottom of the ! structure, for a gimple code `C' the offset is computed as sizeof ! (struct-of `C') - sizeof (tree). This mechanism adds one memory indirection to every access when ! using `gimple_op'(), if this becomes a bottleneck, a pass can ! choose to memoize the result from `gimple_ops'() and use that to access the operands. 11.6.7 Operand validation *************** of the structure. To access tuple opera *** 11299,11365 **** When adding a new operand to a gimple statement, the operand will be validated according to what each tuple accepts in its operand vector. ! These predicates are called by the 'gimple_NAME_set_...()'. Each tuple will use one of the following predicates (Note, this list is not exhaustive): -- GIMPLE function: bool is_gimple_val (tree t) Returns true if t is a "GIMPLE value", which are all the non-addressable stack variables (variables for which ! 'is_gimple_reg' returns true) and constants (expressions for which ! 'is_gimple_min_invariant' returns true). -- GIMPLE function: bool is_gimple_addressable (tree t) ! Returns true if t is a symbol or memory reference whose address can ! be taken. -- GIMPLE function: bool is_gimple_asm_val (tree t) ! Similar to 'is_gimple_val' but it also accepts hard registers. -- GIMPLE function: bool is_gimple_call_addr (tree t) Return true if t is a valid expression to use as the function ! called by a 'GIMPLE_CALL'. -- GIMPLE function: bool is_gimple_mem_ref_addr (tree t) ! Return true if t is a valid expression to use as first operand of a ! 'MEM_REF' expression. -- GIMPLE function: bool is_gimple_constant (tree t) Return true if t is a valid gimple constant. -- GIMPLE function: bool is_gimple_min_invariant (tree t) Return true if t is a valid minimal invariant. This is different ! from constants, in that the specific value of t may not be known at ! compile time, but it is known that it doesn't change (e.g., the address of a function local variable). -- GIMPLE function: bool is_gimple_ip_invariant (tree t) Return true if t is an interprocedural invariant. This means that ! t is a valid invariant in all functions (e.g. it can be an address of a global variable but not of a local one). -- GIMPLE function: bool is_gimple_ip_invariant_address (tree t) ! Return true if t is an 'ADDR_EXPR' that does not change once the program is running (and which is valid in all functions). 11.6.8 Statement validation --------------------------- -- GIMPLE function: bool is_gimple_assign (gimple g) ! Return true if the code of g is 'GIMPLE_ASSIGN'. -- GIMPLE function: bool is_gimple_call (gimple g) ! Return true if the code of g is 'GIMPLE_CALL'. -- GIMPLE function: bool is_gimple_debug (gimple g) ! Return true if the code of g is 'GIMPLE_DEBUG'. -- GIMPLE function: bool gimple_assign_cast_p (const_gimple g) ! Return true if g is a 'GIMPLE_ASSIGN' that performs a type cast operation. -- GIMPLE function: bool gimple_debug_bind_p (gimple g) ! Return true if g is a 'GIMPLE_DEBUG' that binds the value of an expression to a variable. -- GIMPLE function: bool is_gimple_omp (gimple g) --- 11440,11506 ---- When adding a new operand to a gimple statement, the operand will be validated according to what each tuple accepts in its operand vector. ! These predicates are called by the `gimple_NAME_set_...()'. Each tuple will use one of the following predicates (Note, this list is not exhaustive): -- GIMPLE function: bool is_gimple_val (tree t) Returns true if t is a "GIMPLE value", which are all the non-addressable stack variables (variables for which ! `is_gimple_reg' returns true) and constants (expressions for which ! `is_gimple_min_invariant' returns true). -- GIMPLE function: bool is_gimple_addressable (tree t) ! Returns true if t is a symbol or memory reference whose address ! can be taken. -- GIMPLE function: bool is_gimple_asm_val (tree t) ! Similar to `is_gimple_val' but it also accepts hard registers. -- GIMPLE function: bool is_gimple_call_addr (tree t) Return true if t is a valid expression to use as the function ! called by a `GIMPLE_CALL'. -- GIMPLE function: bool is_gimple_mem_ref_addr (tree t) ! Return true if t is a valid expression to use as first operand of ! a `MEM_REF' expression. -- GIMPLE function: bool is_gimple_constant (tree t) Return true if t is a valid gimple constant. -- GIMPLE function: bool is_gimple_min_invariant (tree t) Return true if t is a valid minimal invariant. This is different ! from constants, in that the specific value of t may not be known ! at compile time, but it is known that it doesn't change (e.g., the address of a function local variable). -- GIMPLE function: bool is_gimple_ip_invariant (tree t) Return true if t is an interprocedural invariant. This means that ! t is a valid invariant in all functions (e.g. it can be an address of a global variable but not of a local one). -- GIMPLE function: bool is_gimple_ip_invariant_address (tree t) ! Return true if t is an `ADDR_EXPR' that does not change once the program is running (and which is valid in all functions). 11.6.8 Statement validation --------------------------- -- GIMPLE function: bool is_gimple_assign (gimple g) ! Return true if the code of g is `GIMPLE_ASSIGN'. -- GIMPLE function: bool is_gimple_call (gimple g) ! Return true if the code of g is `GIMPLE_CALL'. -- GIMPLE function: bool is_gimple_debug (gimple g) ! Return true if the code of g is `GIMPLE_DEBUG'. -- GIMPLE function: bool gimple_assign_cast_p (const_gimple g) ! Return true if g is a `GIMPLE_ASSIGN' that performs a type cast operation. -- GIMPLE function: bool gimple_debug_bind_p (gimple g) ! Return true if g is a `GIMPLE_DEBUG' that binds the value of an expression to a variable. -- GIMPLE function: bool is_gimple_omp (gimple g) *************** File: gccint.info, Node: Manipulating G *** 11371,11378 **** 11.7 Manipulating GIMPLE statements =================================== ! This section documents all the functions available to handle each of the ! GIMPLE instructions. 11.7.1 Common accessors ----------------------- --- 11512,11519 ---- 11.7 Manipulating GIMPLE statements =================================== ! This section documents all the functions available to handle each of ! the GIMPLE instructions. 11.7.1 Common accessors ----------------------- *************** GIMPLE instructions. *** 11380,11518 **** The following are common accessors for gimple statements. -- GIMPLE function: enum gimple_code gimple_code (gimple g) ! Return the code for statement 'G'. -- GIMPLE function: basic_block gimple_bb (gimple g) ! Return the basic block to which statement 'G' belongs to. -- GIMPLE function: tree gimple_block (gimple g) ! Return the lexical scope block holding statement 'G'. -- GIMPLE function: tree gimple_expr_type (gimple stmt) ! Return the type of the main expression computed by 'STMT'. Return ! 'void_type_node' if 'STMT' computes nothing. This will only return ! something meaningful for 'GIMPLE_ASSIGN', 'GIMPLE_COND' and ! 'GIMPLE_CALL'. For all other tuple codes, it will return ! 'void_type_node'. -- GIMPLE function: enum tree_code gimple_expr_code (gimple stmt) ! Return the tree code for the expression computed by 'STMT'. This ! is only meaningful for 'GIMPLE_CALL', 'GIMPLE_ASSIGN' and ! 'GIMPLE_COND'. If 'STMT' is 'GIMPLE_CALL', it will return ! 'CALL_EXPR'. For 'GIMPLE_COND', it returns the code of the ! comparison predicate. For 'GIMPLE_ASSIGN' it returns the code of ! the operation performed by the 'RHS' of the assignment. -- GIMPLE function: void gimple_set_block (gimple g, tree block) ! Set the lexical scope block of 'G' to 'BLOCK'. -- GIMPLE function: location_t gimple_locus (gimple g) ! Return locus information for statement 'G'. -- GIMPLE function: void gimple_set_locus (gimple g, location_t locus) ! Set locus information for statement 'G'. -- GIMPLE function: bool gimple_locus_empty_p (gimple g) ! Return true if 'G' does not have locus information. -- GIMPLE function: bool gimple_no_warning_p (gimple stmt) ! Return true if no warnings should be emitted for statement 'STMT'. -- GIMPLE function: void gimple_set_visited (gimple stmt, bool visited_p) ! Set the visited status on statement 'STMT' to 'VISITED_P'. -- GIMPLE function: bool gimple_visited_p (gimple stmt) ! Return the visited status on statement 'STMT'. -- GIMPLE function: void gimple_set_plf (gimple stmt, enum plf_mask plf, bool val_p) ! Set pass local flag 'PLF' on statement 'STMT' to 'VAL_P'. ! -- GIMPLE function: unsigned int gimple_plf (gimple stmt, enum plf_mask ! plf) ! Return the value of pass local flag 'PLF' on statement 'STMT'. -- GIMPLE function: bool gimple_has_ops (gimple g) ! Return true if statement 'G' has register or memory operands. -- GIMPLE function: bool gimple_has_mem_ops (gimple g) ! Return true if statement 'G' has memory operands. -- GIMPLE function: unsigned gimple_num_ops (gimple g) ! Return the number of operands for statement 'G'. -- GIMPLE function: tree * gimple_ops (gimple g) ! Return the array of operands for statement 'G'. -- GIMPLE function: tree gimple_op (gimple g, unsigned i) ! Return operand 'I' for statement 'G'. -- GIMPLE function: tree * gimple_op_ptr (gimple g, unsigned i) ! Return a pointer to operand 'I' for statement 'G'. -- GIMPLE function: void gimple_set_op (gimple g, unsigned i, tree op) ! Set operand 'I' of statement 'G' to 'OP'. -- GIMPLE function: bitmap gimple_addresses_taken (gimple stmt) Return the set of symbols that have had their address taken by ! 'STMT'. -- GIMPLE function: struct def_optype_d * gimple_def_ops (gimple g) ! Return the set of 'DEF' operands for statement 'G'. -- GIMPLE function: void gimple_set_def_ops (gimple g, struct def_optype_d *def) ! Set 'DEF' to be the set of 'DEF' operands for statement 'G'. -- GIMPLE function: struct use_optype_d * gimple_use_ops (gimple g) ! Return the set of 'USE' operands for statement 'G'. -- GIMPLE function: void gimple_set_use_ops (gimple g, struct use_optype_d *use) ! Set 'USE' to be the set of 'USE' operands for statement 'G'. -- GIMPLE function: struct voptype_d * gimple_vuse_ops (gimple g) ! Return the set of 'VUSE' operands for statement 'G'. -- GIMPLE function: void gimple_set_vuse_ops (gimple g, struct voptype_d *ops) ! Set 'OPS' to be the set of 'VUSE' operands for statement 'G'. -- GIMPLE function: struct voptype_d * gimple_vdef_ops (gimple g) ! Return the set of 'VDEF' operands for statement 'G'. -- GIMPLE function: void gimple_set_vdef_ops (gimple g, struct voptype_d *ops) ! Set 'OPS' to be the set of 'VDEF' operands for statement 'G'. -- GIMPLE function: bitmap gimple_loaded_syms (gimple g) ! Return the set of symbols loaded by statement 'G'. Each element of ! the set is the 'DECL_UID' of the corresponding symbol. -- GIMPLE function: bitmap gimple_stored_syms (gimple g) ! Return the set of symbols stored by statement 'G'. Each element of ! the set is the 'DECL_UID' of the corresponding symbol. -- GIMPLE function: bool gimple_modified_p (gimple g) ! Return true if statement 'G' has operands and the modified field has been set. -- GIMPLE function: bool gimple_has_volatile_ops (gimple stmt) ! Return true if statement 'STMT' contains volatile operands. ! -- GIMPLE function: void gimple_set_has_volatile_ops (gimple stmt, bool ! volatilep) ! Return true if statement 'STMT' contains volatile operands. -- GIMPLE function: void update_stmt (gimple s) ! Mark statement 'S' as modified, and update it. -- GIMPLE function: void update_stmt_if_modified (gimple s) ! Update statement 'S' if it has been marked modified. -- GIMPLE function: gimple gimple_copy (gimple stmt) ! Return a deep copy of statement 'STMT'.  File: gccint.info, Node: Tuple specific accessors, Next: GIMPLE sequences, Prev: Manipulating GIMPLE statements, Up: GIMPLE --- 11521,11659 ---- The following are common accessors for gimple statements. -- GIMPLE function: enum gimple_code gimple_code (gimple g) ! Return the code for statement `G'. -- GIMPLE function: basic_block gimple_bb (gimple g) ! Return the basic block to which statement `G' belongs to. -- GIMPLE function: tree gimple_block (gimple g) ! Return the lexical scope block holding statement `G'. -- GIMPLE function: tree gimple_expr_type (gimple stmt) ! Return the type of the main expression computed by `STMT'. Return ! `void_type_node' if `STMT' computes nothing. This will only return ! something meaningful for `GIMPLE_ASSIGN', `GIMPLE_COND' and ! `GIMPLE_CALL'. For all other tuple codes, it will return ! `void_type_node'. -- GIMPLE function: enum tree_code gimple_expr_code (gimple stmt) ! Return the tree code for the expression computed by `STMT'. This ! is only meaningful for `GIMPLE_CALL', `GIMPLE_ASSIGN' and ! `GIMPLE_COND'. If `STMT' is `GIMPLE_CALL', it will return ! `CALL_EXPR'. For `GIMPLE_COND', it returns the code of the ! comparison predicate. For `GIMPLE_ASSIGN' it returns the code of ! the operation performed by the `RHS' of the assignment. -- GIMPLE function: void gimple_set_block (gimple g, tree block) ! Set the lexical scope block of `G' to `BLOCK'. -- GIMPLE function: location_t gimple_locus (gimple g) ! Return locus information for statement `G'. -- GIMPLE function: void gimple_set_locus (gimple g, location_t locus) ! Set locus information for statement `G'. -- GIMPLE function: bool gimple_locus_empty_p (gimple g) ! Return true if `G' does not have locus information. -- GIMPLE function: bool gimple_no_warning_p (gimple stmt) ! Return true if no warnings should be emitted for statement `STMT'. -- GIMPLE function: void gimple_set_visited (gimple stmt, bool visited_p) ! Set the visited status on statement `STMT' to `VISITED_P'. -- GIMPLE function: bool gimple_visited_p (gimple stmt) ! Return the visited status on statement `STMT'. -- GIMPLE function: void gimple_set_plf (gimple stmt, enum plf_mask plf, bool val_p) ! Set pass local flag `PLF' on statement `STMT' to `VAL_P'. ! -- GIMPLE function: unsigned int gimple_plf (gimple stmt, enum ! plf_mask plf) ! Return the value of pass local flag `PLF' on statement `STMT'. -- GIMPLE function: bool gimple_has_ops (gimple g) ! Return true if statement `G' has register or memory operands. -- GIMPLE function: bool gimple_has_mem_ops (gimple g) ! Return true if statement `G' has memory operands. -- GIMPLE function: unsigned gimple_num_ops (gimple g) ! Return the number of operands for statement `G'. -- GIMPLE function: tree * gimple_ops (gimple g) ! Return the array of operands for statement `G'. -- GIMPLE function: tree gimple_op (gimple g, unsigned i) ! Return operand `I' for statement `G'. -- GIMPLE function: tree * gimple_op_ptr (gimple g, unsigned i) ! Return a pointer to operand `I' for statement `G'. -- GIMPLE function: void gimple_set_op (gimple g, unsigned i, tree op) ! Set operand `I' of statement `G' to `OP'. -- GIMPLE function: bitmap gimple_addresses_taken (gimple stmt) Return the set of symbols that have had their address taken by ! `STMT'. -- GIMPLE function: struct def_optype_d * gimple_def_ops (gimple g) ! Return the set of `DEF' operands for statement `G'. -- GIMPLE function: void gimple_set_def_ops (gimple g, struct def_optype_d *def) ! Set `DEF' to be the set of `DEF' operands for statement `G'. -- GIMPLE function: struct use_optype_d * gimple_use_ops (gimple g) ! Return the set of `USE' operands for statement `G'. -- GIMPLE function: void gimple_set_use_ops (gimple g, struct use_optype_d *use) ! Set `USE' to be the set of `USE' operands for statement `G'. -- GIMPLE function: struct voptype_d * gimple_vuse_ops (gimple g) ! Return the set of `VUSE' operands for statement `G'. -- GIMPLE function: void gimple_set_vuse_ops (gimple g, struct voptype_d *ops) ! Set `OPS' to be the set of `VUSE' operands for statement `G'. -- GIMPLE function: struct voptype_d * gimple_vdef_ops (gimple g) ! Return the set of `VDEF' operands for statement `G'. -- GIMPLE function: void gimple_set_vdef_ops (gimple g, struct voptype_d *ops) ! Set `OPS' to be the set of `VDEF' operands for statement `G'. -- GIMPLE function: bitmap gimple_loaded_syms (gimple g) ! Return the set of symbols loaded by statement `G'. Each element of ! the set is the `DECL_UID' of the corresponding symbol. -- GIMPLE function: bitmap gimple_stored_syms (gimple g) ! Return the set of symbols stored by statement `G'. Each element of ! the set is the `DECL_UID' of the corresponding symbol. -- GIMPLE function: bool gimple_modified_p (gimple g) ! Return true if statement `G' has operands and the modified field has been set. -- GIMPLE function: bool gimple_has_volatile_ops (gimple stmt) ! Return true if statement `STMT' contains volatile operands. ! -- GIMPLE function: void gimple_set_has_volatile_ops (gimple stmt, ! bool volatilep) ! Return true if statement `STMT' contains volatile operands. -- GIMPLE function: void update_stmt (gimple s) ! Mark statement `S' as modified, and update it. -- GIMPLE function: void update_stmt_if_modified (gimple s) ! Update statement `S' if it has been marked modified. -- GIMPLE function: gimple gimple_copy (gimple stmt) ! Return a deep copy of statement `STMT'.  File: gccint.info, Node: Tuple specific accessors, Next: GIMPLE sequences, Prev: Manipulating GIMPLE statements, Up: GIMPLE *************** File: gccint.info, Node: Tuple specific *** 11522,12068 **** * Menu: ! * GIMPLE_ASM:: ! * GIMPLE_ASSIGN:: ! * GIMPLE_BIND:: ! * GIMPLE_CALL:: ! * GIMPLE_CATCH:: ! * GIMPLE_COND:: ! * GIMPLE_DEBUG:: ! * GIMPLE_EH_FILTER:: ! * GIMPLE_LABEL:: ! * GIMPLE_GOTO:: ! * GIMPLE_NOP:: ! * GIMPLE_OMP_ATOMIC_LOAD:: ! * GIMPLE_OMP_ATOMIC_STORE:: ! * GIMPLE_OMP_CONTINUE:: ! * GIMPLE_OMP_CRITICAL:: ! * GIMPLE_OMP_FOR:: ! * GIMPLE_OMP_MASTER:: ! * GIMPLE_OMP_ORDERED:: ! * GIMPLE_OMP_PARALLEL:: ! * GIMPLE_OMP_RETURN:: ! * GIMPLE_OMP_SECTION:: ! * GIMPLE_OMP_SECTIONS:: ! * GIMPLE_OMP_SINGLE:: ! * GIMPLE_PHI:: ! * GIMPLE_RESX:: ! * GIMPLE_RETURN:: ! * GIMPLE_SWITCH:: ! * GIMPLE_TRY:: ! * GIMPLE_WITH_CLEANUP_EXPR::  ! File: gccint.info, Node: GIMPLE_ASM, Next: GIMPLE_ASSIGN, Up: Tuple specific accessors ! 11.8.1 'GIMPLE_ASM' ------------------- -- GIMPLE function: gasm *gimple_build_asm_vec ( const char *string, ! vec *inputs, vec *outputs, vec *clobbers, vec *labels) ! Build a 'GIMPLE_ASM' statement. This statement is used for ! building in-line assembly constructs. 'STRING' is the assembly ! code. 'INPUTS', 'OUTPUTS', 'CLOBBERS' and 'LABELS' are the inputs, ! outputs, clobbered registers and labels. -- GIMPLE function: unsigned gimple_asm_ninputs (const gasm *g) ! Return the number of input operands for 'GIMPLE_ASM' 'G'. -- GIMPLE function: unsigned gimple_asm_noutputs (const gasm *g) ! Return the number of output operands for 'GIMPLE_ASM' 'G'. -- GIMPLE function: unsigned gimple_asm_nclobbers (const gasm *g) ! Return the number of clobber operands for 'GIMPLE_ASM' 'G'. -- GIMPLE function: tree gimple_asm_input_op (const gasm *g, unsigned index) ! Return input operand 'INDEX' of 'GIMPLE_ASM' 'G'. -- GIMPLE function: void gimple_asm_set_input_op (gasm *g, unsigned index, tree in_op) ! Set 'IN_OP' to be input operand 'INDEX' in 'GIMPLE_ASM' 'G'. -- GIMPLE function: tree gimple_asm_output_op (const gasm *g, unsigned index) ! Return output operand 'INDEX' of 'GIMPLE_ASM' 'G'. -- GIMPLE function: void gimple_asm_set_output_op (gasm *g, unsigned index, tree out_op) ! Set 'OUT_OP' to be output operand 'INDEX' in 'GIMPLE_ASM' 'G'. ! -- GIMPLE function: tree gimple_asm_clobber_op (const gasm *g, unsigned ! index) ! Return clobber operand 'INDEX' of 'GIMPLE_ASM' 'G'. -- GIMPLE function: void gimple_asm_set_clobber_op (gasm *g, unsigned index, tree clobber_op) ! Set 'CLOBBER_OP' to be clobber operand 'INDEX' in 'GIMPLE_ASM' 'G'. -- GIMPLE function: const char * gimple_asm_string (const gasm *g) Return the string representing the assembly instruction in ! 'GIMPLE_ASM' 'G'. -- GIMPLE function: bool gimple_asm_volatile_p (const gasm *g) ! Return true if 'G' is an asm statement marked volatile. -- GIMPLE function: void gimple_asm_set_volatile (gasm *g, bool volatile_p) ! Mark asm statement 'G' as volatile or non-volatile based on ! 'VOLATILE_P'.  ! File: gccint.info, Node: GIMPLE_ASSIGN, Next: GIMPLE_BIND, Prev: GIMPLE_ASM, Up: Tuple specific accessors ! 11.8.2 'GIMPLE_ASSIGN' ---------------------- -- GIMPLE function: gassign *gimple_build_assign (tree lhs, tree rhs) ! Build a 'GIMPLE_ASSIGN' statement. The left-hand side is an lvalue ! passed in lhs. The right-hand side can be either a unary or binary ! tree expression. The expression tree rhs will be flattened and its ! operands assigned to the corresponding operand slots in the new ! statement. This function is useful when you already have a tree ! expression that you want to convert into a tuple. However, try to ! avoid building expression trees for the sole purpose of calling ! this function. If you already have the operands in separate trees, ! it is better to use 'gimple_build_assign' with 'enum tree_code' ! argument and separate arguments for each operand. -- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum tree_code subcode, tree op1, tree op2, tree op3) ! This function is similar to two operand 'gimple_build_assign', but ! is used to build a 'GIMPLE_ASSIGN' statement when the operands of the right-hand side of the assignment are already split into different operands. The left-hand side is an lvalue passed in lhs. Subcode is the ! 'tree_code' for the right-hand side of the assignment. Op1, op2 and op3 are the operands. -- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum tree_code subcode, tree op1, tree op2) ! Like the above 5 operand 'gimple_build_assign', but with the last ! argument 'NULL' - this overload should not be used for ! 'GIMPLE_TERNARY_RHS' assignments. -- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum tree_code subcode, tree op1) ! Like the above 4 operand 'gimple_build_assign', but with the last ! argument 'NULL' - this overload should be used only for ! 'GIMPLE_UNARY_RHS' and 'GIMPLE_SINGLE_RHS' assignments. -- GIMPLE function: gimple gimplify_assign (tree dst, tree src, gimple_seq *seq_p) ! Build a new 'GIMPLE_ASSIGN' tuple and append it to the end of ! '*SEQ_P'. ! 'DST'/'SRC' are the destination and source respectively. You can pass ! ungimplified trees in 'DST' or 'SRC', in which case they will be converted to a gimple operand if necessary. ! This function returns the newly created 'GIMPLE_ASSIGN' tuple. -- GIMPLE function: enum tree_code gimple_assign_rhs_code (gimple g) ! Return the code of the expression computed on the 'RHS' of ! assignment statement 'G'. -- GIMPLE function: enum gimple_rhs_class gimple_assign_rhs_class (gimple g) ! Return the gimple rhs class of the code for the expression computed ! on the rhs of assignment statement 'G'. This will never return ! 'GIMPLE_INVALID_RHS'. -- GIMPLE function: tree gimple_assign_lhs (gimple g) ! Return the 'LHS' of assignment statement 'G'. -- GIMPLE function: tree * gimple_assign_lhs_ptr (gimple g) ! Return a pointer to the 'LHS' of assignment statement 'G'. -- GIMPLE function: tree gimple_assign_rhs1 (gimple g) ! Return the first operand on the 'RHS' of assignment statement 'G'. -- GIMPLE function: tree * gimple_assign_rhs1_ptr (gimple g) ! Return the address of the first operand on the 'RHS' of assignment ! statement 'G'. -- GIMPLE function: tree gimple_assign_rhs2 (gimple g) ! Return the second operand on the 'RHS' of assignment statement 'G'. -- GIMPLE function: tree * gimple_assign_rhs2_ptr (gimple g) ! Return the address of the second operand on the 'RHS' of assignment ! statement 'G'. -- GIMPLE function: tree gimple_assign_rhs3 (gimple g) ! Return the third operand on the 'RHS' of assignment statement 'G'. -- GIMPLE function: tree * gimple_assign_rhs3_ptr (gimple g) ! Return the address of the third operand on the 'RHS' of assignment ! statement 'G'. -- GIMPLE function: void gimple_assign_set_lhs (gimple g, tree lhs) ! Set 'LHS' to be the 'LHS' operand of assignment statement 'G'. -- GIMPLE function: void gimple_assign_set_rhs1 (gimple g, tree rhs) ! Set 'RHS' to be the first operand on the 'RHS' of assignment ! statement 'G'. -- GIMPLE function: void gimple_assign_set_rhs2 (gimple g, tree rhs) ! Set 'RHS' to be the second operand on the 'RHS' of assignment ! statement 'G'. -- GIMPLE function: void gimple_assign_set_rhs3 (gimple g, tree rhs) ! Set 'RHS' to be the third operand on the 'RHS' of assignment ! statement 'G'. -- GIMPLE function: bool gimple_assign_cast_p (const_gimple s) ! Return true if 'S' is a type-cast assignment.  ! File: gccint.info, Node: GIMPLE_BIND, Next: GIMPLE_CALL, Prev: GIMPLE_ASSIGN, Up: Tuple specific accessors ! 11.8.3 'GIMPLE_BIND' -------------------- -- GIMPLE function: gbind *gimple_build_bind (tree vars, gimple_seq body) ! Build a 'GIMPLE_BIND' statement with a list of variables in 'VARS' ! and a body of statements in sequence 'BODY'. -- GIMPLE function: tree gimple_bind_vars (const gbind *g) ! Return the variables declared in the 'GIMPLE_BIND' statement 'G'. -- GIMPLE function: void gimple_bind_set_vars (gbind *g, tree vars) ! Set 'VARS' to be the set of variables declared in the 'GIMPLE_BIND' ! statement 'G'. -- GIMPLE function: void gimple_bind_append_vars (gbind *g, tree vars) ! Append 'VARS' to the set of variables declared in the 'GIMPLE_BIND' ! statement 'G'. -- GIMPLE function: gimple_seq gimple_bind_body (gbind *g) ! Return the GIMPLE sequence contained in the 'GIMPLE_BIND' statement ! 'G'. -- GIMPLE function: void gimple_bind_set_body (gbind *g, gimple_seq seq) ! Set 'SEQ' to be sequence contained in the 'GIMPLE_BIND' statement ! 'G'. -- GIMPLE function: void gimple_bind_add_stmt (gbind *gs, gimple stmt) ! Append a statement to the end of a 'GIMPLE_BIND''s body. -- GIMPLE function: void gimple_bind_add_seq (gbind *gs, gimple_seq seq) ! Append a sequence of statements to the end of a 'GIMPLE_BIND''s body. -- GIMPLE function: tree gimple_bind_block (const gbind *g) ! Return the 'TREE_BLOCK' node associated with 'GIMPLE_BIND' ! statement 'G'. This is analogous to the 'BIND_EXPR_BLOCK' field in trees. -- GIMPLE function: void gimple_bind_set_block (gbind *g, tree block) ! Set 'BLOCK' to be the 'TREE_BLOCK' node associated with ! 'GIMPLE_BIND' statement 'G'.  ! File: gccint.info, Node: GIMPLE_CALL, Next: GIMPLE_CATCH, Prev: GIMPLE_BIND, Up: Tuple specific accessors ! 11.8.4 'GIMPLE_CALL' -------------------- -- GIMPLE function: gcall *gimple_build_call (tree fn, unsigned nargs, ...) ! Build a 'GIMPLE_CALL' statement to function 'FN'. The argument ! 'FN' must be either a 'FUNCTION_DECL' or a gimple call address as ! determined by 'is_gimple_call_addr'. 'NARGS' are the number of ! arguments. The rest of the arguments follow the argument 'NARGS', and must be trees that are valid as rvalues in gimple (i.e., each ! operand is validated with 'is_gimple_operand'). -- GIMPLE function: gcall *gimple_build_call_from_tree (tree call_expr) ! Build a 'GIMPLE_CALL' from a 'CALL_EXPR' node. The arguments and the function are taken from the expression directly. This routine ! assumes that 'call_expr' is already in GIMPLE form. That is, its operands are GIMPLE values and the function call needs no further ! simplification. All the call flags in 'call_expr' are copied over ! to the new 'GIMPLE_CALL'. ! -- GIMPLE function: gcall *gimple_build_call_vec (tree fn, 'vec' args) ! Identical to 'gimple_build_call' but the arguments are stored in a ! 'vec'. -- GIMPLE function: tree gimple_call_lhs (gimple g) ! Return the 'LHS' of call statement 'G'. -- GIMPLE function: tree * gimple_call_lhs_ptr (gimple g) ! Return a pointer to the 'LHS' of call statement 'G'. -- GIMPLE function: void gimple_call_set_lhs (gimple g, tree lhs) ! Set 'LHS' to be the 'LHS' operand of call statement 'G'. -- GIMPLE function: tree gimple_call_fn (gimple g) Return the tree node representing the function called by call ! statement 'G'. -- GIMPLE function: void gimple_call_set_fn (gcall *g, tree fn) ! Set 'FN' to be the function called by call statement 'G'. This has to be a gimple value specifying the address of the called function. -- GIMPLE function: tree gimple_call_fndecl (gimple g) ! If a given 'GIMPLE_CALL''s callee is a 'FUNCTION_DECL', return it. ! Otherwise return 'NULL'. This function is analogous to ! 'get_callee_fndecl' in 'GENERIC'. -- GIMPLE function: tree gimple_call_set_fndecl (gimple g, tree fndecl) ! Set the called function to 'FNDECL'. -- GIMPLE function: tree gimple_call_return_type (const gcall *g) ! Return the type returned by call statement 'G'. -- GIMPLE function: tree gimple_call_chain (gimple g) ! Return the static chain for call statement 'G'. -- GIMPLE function: void gimple_call_set_chain (gcall *g, tree chain) ! Set 'CHAIN' to be the static chain for call statement 'G'. -- GIMPLE function: unsigned gimple_call_num_args (gimple g) ! Return the number of arguments used by call statement 'G'. -- GIMPLE function: tree gimple_call_arg (gimple g, unsigned index) ! Return the argument at position 'INDEX' for call statement 'G'. The first argument is 0. -- GIMPLE function: tree * gimple_call_arg_ptr (gimple g, unsigned index) ! Return a pointer to the argument at position 'INDEX' for call ! statement 'G'. ! -- GIMPLE function: void gimple_call_set_arg (gimple g, unsigned index, ! tree arg) ! Set 'ARG' to be the argument at position 'INDEX' for call statement ! 'G'. -- GIMPLE function: void gimple_call_set_tail (gcall *s) ! Mark call statement 'S' as being a tail call (i.e., a call just ! before the exit of a function). These calls are candidate for tail call optimization. -- GIMPLE function: bool gimple_call_tail_p (gcall *s) ! Return true if 'GIMPLE_CALL' 'S' is marked as a tail call. -- GIMPLE function: bool gimple_call_noreturn_p (gimple s) ! Return true if 'S' is a noreturn call. -- GIMPLE function: gimple gimple_call_copy_skip_args (gcall *stmt, bitmap args_to_skip) ! Build a 'GIMPLE_CALL' identical to 'STMT' but skipping the ! arguments in the positions marked by the set 'ARGS_TO_SKIP'.  ! File: gccint.info, Node: GIMPLE_CATCH, Next: GIMPLE_COND, Prev: GIMPLE_CALL, Up: Tuple specific accessors ! 11.8.5 'GIMPLE_CATCH' --------------------- -- GIMPLE function: gcatch *gimple_build_catch (tree types, gimple_seq handler) ! Build a 'GIMPLE_CATCH' statement. 'TYPES' are the tree types this ! catch handles. 'HANDLER' is a sequence of statements with the code for the handler. -- GIMPLE function: tree gimple_catch_types (const gcatch *g) ! Return the types handled by 'GIMPLE_CATCH' statement 'G'. -- GIMPLE function: tree * gimple_catch_types_ptr (gcatch *g) ! Return a pointer to the types handled by 'GIMPLE_CATCH' statement ! 'G'. -- GIMPLE function: gimple_seq gimple_catch_handler (gcatch *g) Return the GIMPLE sequence representing the body of the handler of ! 'GIMPLE_CATCH' statement 'G'. -- GIMPLE function: void gimple_catch_set_types (gcatch *g, tree t) ! Set 'T' to be the set of types handled by 'GIMPLE_CATCH' 'G'. -- GIMPLE function: void gimple_catch_set_handler (gcatch *g, gimple_seq handler) ! Set 'HANDLER' to be the body of 'GIMPLE_CATCH' 'G'.  ! File: gccint.info, Node: GIMPLE_COND, Next: GIMPLE_DEBUG, Prev: GIMPLE_CATCH, Up: Tuple specific accessors ! 11.8.6 'GIMPLE_COND' -------------------- -- GIMPLE function: gcond *gimple_build_cond ( enum tree_code pred_code, tree lhs, tree rhs, tree t_label, tree f_label) ! Build a 'GIMPLE_COND' statement. 'A' 'GIMPLE_COND' statement ! compares 'LHS' and 'RHS' and if the condition in 'PRED_CODE' is ! true, jump to the label in 't_label', otherwise jump to the label ! in 'f_label'. 'PRED_CODE' are relational operator tree codes like ! 'EQ_EXPR', 'LT_EXPR', 'LE_EXPR', 'NE_EXPR', etc. ! -- GIMPLE function: gcond *gimple_build_cond_from_tree (tree cond, tree ! t_label, tree f_label) ! Build a 'GIMPLE_COND' statement from the conditional expression ! tree 'COND'. 'T_LABEL' and 'F_LABEL' are as in ! 'gimple_build_cond'. -- GIMPLE function: enum tree_code gimple_cond_code (gimple g) Return the code of the predicate computed by conditional statement ! 'G'. ! -- GIMPLE function: void gimple_cond_set_code (gcond *g, enum tree_code ! code) ! Set 'CODE' to be the predicate code for the conditional statement ! 'G'. -- GIMPLE function: tree gimple_cond_lhs (gimple g) ! Return the 'LHS' of the predicate computed by conditional statement ! 'G'. -- GIMPLE function: void gimple_cond_set_lhs (gcond *g, tree lhs) ! Set 'LHS' to be the 'LHS' operand of the predicate computed by ! conditional statement 'G'. -- GIMPLE function: tree gimple_cond_rhs (gimple g) ! Return the 'RHS' operand of the predicate computed by conditional ! 'G'. -- GIMPLE function: void gimple_cond_set_rhs (gcond *g, tree rhs) ! Set 'RHS' to be the 'RHS' operand of the predicate computed by ! conditional statement 'G'. -- GIMPLE function: tree gimple_cond_true_label (const gcond *g) ! Return the label used by conditional statement 'G' when its predicate evaluates to true. -- GIMPLE function: void gimple_cond_set_true_label (gcond *g, tree label) ! Set 'LABEL' to be the label used by conditional statement 'G' when its predicate evaluates to true. -- GIMPLE function: void gimple_cond_set_false_label (gcond *g, tree label) ! Set 'LABEL' to be the label used by conditional statement 'G' when its predicate evaluates to false. -- GIMPLE function: tree gimple_cond_false_label (const gcond *g) ! Return the label used by conditional statement 'G' when its predicate evaluates to false. -- GIMPLE function: void gimple_cond_make_false (gcond *g) ! Set the conditional 'COND_STMT' to be of the form 'if (1 == 0)'. -- GIMPLE function: void gimple_cond_make_true (gcond *g) ! Set the conditional 'COND_STMT' to be of the form 'if (1 == 1)'.  ! File: gccint.info, Node: GIMPLE_DEBUG, Next: GIMPLE_EH_FILTER, Prev: GIMPLE_COND, Up: Tuple specific accessors ! 11.8.7 'GIMPLE_DEBUG' --------------------- -- GIMPLE function: gdebug *gimple_build_debug_bind (tree var, tree value, gimple stmt) ! Build a 'GIMPLE_DEBUG' statement with 'GIMPLE_DEBUG_BIND' of ! 'subcode'. The effect of this statement is to tell debug information generation machinery that the value of user variable ! 'var' is given by 'value' at that point, and to remain with that ! value until 'var' runs out of scope, a dynamically-subsequent debug ! bind statement overrides the binding, or conflicting values reach a ! control flow merge point. Even if components of the 'value' ! expression change afterwards, the variable is supposed to retain ! the same value, though not necessarily the same location. ! It is expected that 'var' be most often a tree for automatic user ! variables ('VAR_DECL' or 'PARM_DECL') that satisfy the requirements ! for gimple registers, but it may also be a tree for a scalarized ! component of a user variable ('ARRAY_REF', 'COMPONENT_REF'), or a ! debug temporary ('DEBUG_EXPR_DECL'). ! As for 'value', it can be an arbitrary tree expression, but it is recommended that it be in a suitable form for a gimple assignment ! 'RHS'. It is not expected that user variables that could appear as ! 'var' ever appear in 'value', because in the latter we'd have their ! 'SSA_NAME's instead, but even if they were not in SSA form, user ! variables appearing in 'value' are to be regarded as part of the ! executable code space, whereas those in 'var' are to be regarded as ! part of the source code space. There is no way to refer to the ! value bound to a user variable within a 'value' expression. ! If 'value' is 'GIMPLE_DEBUG_BIND_NOVALUE', debug information ! generation machinery is informed that the variable 'var' is unbound, i.e., that its value is indeterminate, which sometimes means it is really unavailable, and other times that the compiler could not keep track of it. ! Block and location information for the newly-created stmt are taken ! from 'stmt', if given. -- GIMPLE function: tree gimple_debug_bind_get_var (gimple stmt) ! Return the user variable VAR that is bound at 'stmt'. -- GIMPLE function: tree gimple_debug_bind_get_value (gimple stmt) Return the value expression that is bound to a user variable at ! 'stmt'. -- GIMPLE function: tree * gimple_debug_bind_get_value_ptr (gimple stmt) Return a pointer to the value expression that is bound to a user ! variable at 'stmt'. -- GIMPLE function: void gimple_debug_bind_set_var (gimple stmt, tree var) ! Modify the user variable bound at 'stmt' to VAR. ! -- GIMPLE function: void gimple_debug_bind_set_value (gimple stmt, tree ! var) ! Modify the value bound to the user variable bound at 'stmt' to VALUE. -- GIMPLE function: void gimple_debug_bind_reset_value (gimple stmt) ! Modify the value bound to the user variable bound at 'stmt' so that ! the variable becomes unbound. -- GIMPLE function: bool gimple_debug_bind_has_value_p (gimple stmt) ! Return 'TRUE' if 'stmt' binds a user variable to a value, and ! 'FALSE' if it unbinds the variable.  ! File: gccint.info, Node: GIMPLE_EH_FILTER, Next: GIMPLE_LABEL, Prev: GIMPLE_DEBUG, Up: Tuple specific accessors ! 11.8.8 'GIMPLE_EH_FILTER' ------------------------- -- GIMPLE function: geh_filter *gimple_build_eh_filter (tree types, gimple_seq failure) ! Build a 'GIMPLE_EH_FILTER' statement. 'TYPES' are the filter's ! types. 'FAILURE' is a sequence with the filter's failure action. -- GIMPLE function: tree gimple_eh_filter_types (gimple g) ! Return the types handled by 'GIMPLE_EH_FILTER' statement 'G'. -- GIMPLE function: tree * gimple_eh_filter_types_ptr (gimple g) ! Return a pointer to the types handled by 'GIMPLE_EH_FILTER' ! statement 'G'. -- GIMPLE function: gimple_seq gimple_eh_filter_failure (gimple g) ! Return the sequence of statement to execute when 'GIMPLE_EH_FILTER' statement fails. -- GIMPLE function: void gimple_eh_filter_set_types (geh_filter *g, tree types) ! Set 'TYPES' to be the set of types handled by 'GIMPLE_EH_FILTER' ! 'G'. -- GIMPLE function: void gimple_eh_filter_set_failure (geh_filter *g, gimple_seq failure) ! Set 'FAILURE' to be the sequence of statements to execute on ! failure for 'GIMPLE_EH_FILTER' 'G'. -- GIMPLE function: tree gimple_eh_must_not_throw_fndecl ( geh_mnt *eh_mnt_stmt) --- 11663,12210 ---- * Menu: ! * `GIMPLE_ASM':: ! * `GIMPLE_ASSIGN':: ! * `GIMPLE_BIND':: ! * `GIMPLE_CALL':: ! * `GIMPLE_CATCH':: ! * `GIMPLE_COND':: ! * `GIMPLE_DEBUG':: ! * `GIMPLE_EH_FILTER':: ! * `GIMPLE_LABEL':: ! * `GIMPLE_GOTO':: ! * `GIMPLE_NOP':: ! * `GIMPLE_OMP_ATOMIC_LOAD':: ! * `GIMPLE_OMP_ATOMIC_STORE':: ! * `GIMPLE_OMP_CONTINUE':: ! * `GIMPLE_OMP_CRITICAL':: ! * `GIMPLE_OMP_FOR':: ! * `GIMPLE_OMP_MASTER':: ! * `GIMPLE_OMP_ORDERED':: ! * `GIMPLE_OMP_PARALLEL':: ! * `GIMPLE_OMP_RETURN':: ! * `GIMPLE_OMP_SECTION':: ! * `GIMPLE_OMP_SECTIONS':: ! * `GIMPLE_OMP_SINGLE':: ! * `GIMPLE_PHI':: ! * `GIMPLE_RESX':: ! * `GIMPLE_RETURN':: ! * `GIMPLE_SWITCH':: ! * `GIMPLE_TRY':: ! * `GIMPLE_WITH_CLEANUP_EXPR'::  ! File: gccint.info, Node: `GIMPLE_ASM', Next: `GIMPLE_ASSIGN', Up: Tuple specific accessors ! 11.8.1 `GIMPLE_ASM' ------------------- -- GIMPLE function: gasm *gimple_build_asm_vec ( const char *string, ! vec *inputs, vec *outputs, ! vec *clobbers, vec *labels) ! Build a `GIMPLE_ASM' statement. This statement is used for ! building in-line assembly constructs. `STRING' is the assembly ! code. `INPUTS', `OUTPUTS', `CLOBBERS' and `LABELS' are the ! inputs, outputs, clobbered registers and labels. -- GIMPLE function: unsigned gimple_asm_ninputs (const gasm *g) ! Return the number of input operands for `GIMPLE_ASM' `G'. -- GIMPLE function: unsigned gimple_asm_noutputs (const gasm *g) ! Return the number of output operands for `GIMPLE_ASM' `G'. -- GIMPLE function: unsigned gimple_asm_nclobbers (const gasm *g) ! Return the number of clobber operands for `GIMPLE_ASM' `G'. -- GIMPLE function: tree gimple_asm_input_op (const gasm *g, unsigned index) ! Return input operand `INDEX' of `GIMPLE_ASM' `G'. -- GIMPLE function: void gimple_asm_set_input_op (gasm *g, unsigned index, tree in_op) ! Set `IN_OP' to be input operand `INDEX' in `GIMPLE_ASM' `G'. -- GIMPLE function: tree gimple_asm_output_op (const gasm *g, unsigned index) ! Return output operand `INDEX' of `GIMPLE_ASM' `G'. -- GIMPLE function: void gimple_asm_set_output_op (gasm *g, unsigned index, tree out_op) ! Set `OUT_OP' to be output operand `INDEX' in `GIMPLE_ASM' `G'. ! -- GIMPLE function: tree gimple_asm_clobber_op (const gasm *g, ! unsigned index) ! Return clobber operand `INDEX' of `GIMPLE_ASM' `G'. -- GIMPLE function: void gimple_asm_set_clobber_op (gasm *g, unsigned index, tree clobber_op) ! Set `CLOBBER_OP' to be clobber operand `INDEX' in `GIMPLE_ASM' `G'. -- GIMPLE function: const char * gimple_asm_string (const gasm *g) Return the string representing the assembly instruction in ! `GIMPLE_ASM' `G'. -- GIMPLE function: bool gimple_asm_volatile_p (const gasm *g) ! Return true if `G' is an asm statement marked volatile. -- GIMPLE function: void gimple_asm_set_volatile (gasm *g, bool volatile_p) ! Mark asm statement `G' as volatile or non-volatile based on ! `VOLATILE_P'.  ! File: gccint.info, Node: `GIMPLE_ASSIGN', Next: `GIMPLE_BIND', Prev: `GIMPLE_ASM', Up: Tuple specific accessors ! 11.8.2 `GIMPLE_ASSIGN' ---------------------- -- GIMPLE function: gassign *gimple_build_assign (tree lhs, tree rhs) ! Build a `GIMPLE_ASSIGN' statement. The left-hand side is an lvalue ! passed in lhs. The right-hand side can be either a unary or ! binary tree expression. The expression tree rhs will be flattened ! and its operands assigned to the corresponding operand slots in ! the new statement. This function is useful when you already have ! a tree expression that you want to convert into a tuple. However, ! try to avoid building expression trees for the sole purpose of ! calling this function. If you already have the operands in ! separate trees, it is better to use `gimple_build_assign' with ! `enum tree_code' argument and separate arguments for each operand. -- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum tree_code subcode, tree op1, tree op2, tree op3) ! This function is similar to two operand `gimple_build_assign', but ! is used to build a `GIMPLE_ASSIGN' statement when the operands of the right-hand side of the assignment are already split into different operands. The left-hand side is an lvalue passed in lhs. Subcode is the ! `tree_code' for the right-hand side of the assignment. Op1, op2 and op3 are the operands. -- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum tree_code subcode, tree op1, tree op2) ! Like the above 5 operand `gimple_build_assign', but with the last ! argument `NULL' - this overload should not be used for ! `GIMPLE_TERNARY_RHS' assignments. -- GIMPLE function: gassign *gimple_build_assign (tree lhs, enum tree_code subcode, tree op1) ! Like the above 4 operand `gimple_build_assign', but with the last ! argument `NULL' - this overload should be used only for ! `GIMPLE_UNARY_RHS' and `GIMPLE_SINGLE_RHS' assignments. -- GIMPLE function: gimple gimplify_assign (tree dst, tree src, gimple_seq *seq_p) ! Build a new `GIMPLE_ASSIGN' tuple and append it to the end of ! `*SEQ_P'. ! `DST'/`SRC' are the destination and source respectively. You can pass ! ungimplified trees in `DST' or `SRC', in which case they will be converted to a gimple operand if necessary. ! This function returns the newly created `GIMPLE_ASSIGN' tuple. -- GIMPLE function: enum tree_code gimple_assign_rhs_code (gimple g) ! Return the code of the expression computed on the `RHS' of ! assignment statement `G'. -- GIMPLE function: enum gimple_rhs_class gimple_assign_rhs_class (gimple g) ! Return the gimple rhs class of the code for the expression ! computed on the rhs of assignment statement `G'. This will never ! return `GIMPLE_INVALID_RHS'. -- GIMPLE function: tree gimple_assign_lhs (gimple g) ! Return the `LHS' of assignment statement `G'. -- GIMPLE function: tree * gimple_assign_lhs_ptr (gimple g) ! Return a pointer to the `LHS' of assignment statement `G'. -- GIMPLE function: tree gimple_assign_rhs1 (gimple g) ! Return the first operand on the `RHS' of assignment statement `G'. -- GIMPLE function: tree * gimple_assign_rhs1_ptr (gimple g) ! Return the address of the first operand on the `RHS' of assignment ! statement `G'. -- GIMPLE function: tree gimple_assign_rhs2 (gimple g) ! Return the second operand on the `RHS' of assignment statement `G'. -- GIMPLE function: tree * gimple_assign_rhs2_ptr (gimple g) ! Return the address of the second operand on the `RHS' of assignment ! statement `G'. -- GIMPLE function: tree gimple_assign_rhs3 (gimple g) ! Return the third operand on the `RHS' of assignment statement `G'. -- GIMPLE function: tree * gimple_assign_rhs3_ptr (gimple g) ! Return the address of the third operand on the `RHS' of assignment ! statement `G'. -- GIMPLE function: void gimple_assign_set_lhs (gimple g, tree lhs) ! Set `LHS' to be the `LHS' operand of assignment statement `G'. -- GIMPLE function: void gimple_assign_set_rhs1 (gimple g, tree rhs) ! Set `RHS' to be the first operand on the `RHS' of assignment ! statement `G'. -- GIMPLE function: void gimple_assign_set_rhs2 (gimple g, tree rhs) ! Set `RHS' to be the second operand on the `RHS' of assignment ! statement `G'. -- GIMPLE function: void gimple_assign_set_rhs3 (gimple g, tree rhs) ! Set `RHS' to be the third operand on the `RHS' of assignment ! statement `G'. -- GIMPLE function: bool gimple_assign_cast_p (const_gimple s) ! Return true if `S' is a type-cast assignment.  ! File: gccint.info, Node: `GIMPLE_BIND', Next: `GIMPLE_CALL', Prev: `GIMPLE_ASSIGN', Up: Tuple specific accessors ! 11.8.3 `GIMPLE_BIND' -------------------- -- GIMPLE function: gbind *gimple_build_bind (tree vars, gimple_seq body) ! Build a `GIMPLE_BIND' statement with a list of variables in `VARS' ! and a body of statements in sequence `BODY'. -- GIMPLE function: tree gimple_bind_vars (const gbind *g) ! Return the variables declared in the `GIMPLE_BIND' statement `G'. -- GIMPLE function: void gimple_bind_set_vars (gbind *g, tree vars) ! Set `VARS' to be the set of variables declared in the `GIMPLE_BIND' ! statement `G'. -- GIMPLE function: void gimple_bind_append_vars (gbind *g, tree vars) ! Append `VARS' to the set of variables declared in the `GIMPLE_BIND' ! statement `G'. -- GIMPLE function: gimple_seq gimple_bind_body (gbind *g) ! Return the GIMPLE sequence contained in the `GIMPLE_BIND' statement ! `G'. -- GIMPLE function: void gimple_bind_set_body (gbind *g, gimple_seq seq) ! Set `SEQ' to be sequence contained in the `GIMPLE_BIND' statement ! `G'. -- GIMPLE function: void gimple_bind_add_stmt (gbind *gs, gimple stmt) ! Append a statement to the end of a `GIMPLE_BIND''s body. -- GIMPLE function: void gimple_bind_add_seq (gbind *gs, gimple_seq seq) ! Append a sequence of statements to the end of a `GIMPLE_BIND''s body. -- GIMPLE function: tree gimple_bind_block (const gbind *g) ! Return the `TREE_BLOCK' node associated with `GIMPLE_BIND' ! statement `G'. This is analogous to the `BIND_EXPR_BLOCK' field in trees. -- GIMPLE function: void gimple_bind_set_block (gbind *g, tree block) ! Set `BLOCK' to be the `TREE_BLOCK' node associated with ! `GIMPLE_BIND' statement `G'.  ! File: gccint.info, Node: `GIMPLE_CALL', Next: `GIMPLE_CATCH', Prev: `GIMPLE_BIND', Up: Tuple specific accessors ! 11.8.4 `GIMPLE_CALL' -------------------- -- GIMPLE function: gcall *gimple_build_call (tree fn, unsigned nargs, ...) ! Build a `GIMPLE_CALL' statement to function `FN'. The argument ! `FN' must be either a `FUNCTION_DECL' or a gimple call address as ! determined by `is_gimple_call_addr'. `NARGS' are the number of ! arguments. The rest of the arguments follow the argument `NARGS', and must be trees that are valid as rvalues in gimple (i.e., each ! operand is validated with `is_gimple_operand'). -- GIMPLE function: gcall *gimple_build_call_from_tree (tree call_expr) ! Build a `GIMPLE_CALL' from a `CALL_EXPR' node. The arguments and the function are taken from the expression directly. This routine ! assumes that `call_expr' is already in GIMPLE form. That is, its operands are GIMPLE values and the function call needs no further ! simplification. All the call flags in `call_expr' are copied over ! to the new `GIMPLE_CALL'. ! -- GIMPLE function: gcall *gimple_build_call_vec (tree fn, `vec' args) ! Identical to `gimple_build_call' but the arguments are stored in a ! `vec'. -- GIMPLE function: tree gimple_call_lhs (gimple g) ! Return the `LHS' of call statement `G'. -- GIMPLE function: tree * gimple_call_lhs_ptr (gimple g) ! Return a pointer to the `LHS' of call statement `G'. -- GIMPLE function: void gimple_call_set_lhs (gimple g, tree lhs) ! Set `LHS' to be the `LHS' operand of call statement `G'. -- GIMPLE function: tree gimple_call_fn (gimple g) Return the tree node representing the function called by call ! statement `G'. -- GIMPLE function: void gimple_call_set_fn (gcall *g, tree fn) ! Set `FN' to be the function called by call statement `G'. This has to be a gimple value specifying the address of the called function. -- GIMPLE function: tree gimple_call_fndecl (gimple g) ! If a given `GIMPLE_CALL''s callee is a `FUNCTION_DECL', return it. ! Otherwise return `NULL'. This function is analogous to ! `get_callee_fndecl' in `GENERIC'. -- GIMPLE function: tree gimple_call_set_fndecl (gimple g, tree fndecl) ! Set the called function to `FNDECL'. -- GIMPLE function: tree gimple_call_return_type (const gcall *g) ! Return the type returned by call statement `G'. -- GIMPLE function: tree gimple_call_chain (gimple g) ! Return the static chain for call statement `G'. -- GIMPLE function: void gimple_call_set_chain (gcall *g, tree chain) ! Set `CHAIN' to be the static chain for call statement `G'. -- GIMPLE function: unsigned gimple_call_num_args (gimple g) ! Return the number of arguments used by call statement `G'. -- GIMPLE function: tree gimple_call_arg (gimple g, unsigned index) ! Return the argument at position `INDEX' for call statement `G'. The first argument is 0. -- GIMPLE function: tree * gimple_call_arg_ptr (gimple g, unsigned index) ! Return a pointer to the argument at position `INDEX' for call ! statement `G'. ! -- GIMPLE function: void gimple_call_set_arg (gimple g, unsigned ! index, tree arg) ! Set `ARG' to be the argument at position `INDEX' for call statement ! `G'. -- GIMPLE function: void gimple_call_set_tail (gcall *s) ! Mark call statement `S' as being a tail call (i.e., a call just ! before the exit of a function). These calls are candidate for tail call optimization. -- GIMPLE function: bool gimple_call_tail_p (gcall *s) ! Return true if `GIMPLE_CALL' `S' is marked as a tail call. -- GIMPLE function: bool gimple_call_noreturn_p (gimple s) ! Return true if `S' is a noreturn call. -- GIMPLE function: gimple gimple_call_copy_skip_args (gcall *stmt, bitmap args_to_skip) ! Build a `GIMPLE_CALL' identical to `STMT' but skipping the ! arguments in the positions marked by the set `ARGS_TO_SKIP'.  ! File: gccint.info, Node: `GIMPLE_CATCH', Next: `GIMPLE_COND', Prev: `GIMPLE_CALL', Up: Tuple specific accessors ! 11.8.5 `GIMPLE_CATCH' --------------------- -- GIMPLE function: gcatch *gimple_build_catch (tree types, gimple_seq handler) ! Build a `GIMPLE_CATCH' statement. `TYPES' are the tree types this ! catch handles. `HANDLER' is a sequence of statements with the code for the handler. -- GIMPLE function: tree gimple_catch_types (const gcatch *g) ! Return the types handled by `GIMPLE_CATCH' statement `G'. -- GIMPLE function: tree * gimple_catch_types_ptr (gcatch *g) ! Return a pointer to the types handled by `GIMPLE_CATCH' statement ! `G'. -- GIMPLE function: gimple_seq gimple_catch_handler (gcatch *g) Return the GIMPLE sequence representing the body of the handler of ! `GIMPLE_CATCH' statement `G'. -- GIMPLE function: void gimple_catch_set_types (gcatch *g, tree t) ! Set `T' to be the set of types handled by `GIMPLE_CATCH' `G'. -- GIMPLE function: void gimple_catch_set_handler (gcatch *g, gimple_seq handler) ! Set `HANDLER' to be the body of `GIMPLE_CATCH' `G'.  ! File: gccint.info, Node: `GIMPLE_COND', Next: `GIMPLE_DEBUG', Prev: `GIMPLE_CATCH', Up: Tuple specific accessors ! 11.8.6 `GIMPLE_COND' -------------------- -- GIMPLE function: gcond *gimple_build_cond ( enum tree_code pred_code, tree lhs, tree rhs, tree t_label, tree f_label) ! Build a `GIMPLE_COND' statement. `A' `GIMPLE_COND' statement ! compares `LHS' and `RHS' and if the condition in `PRED_CODE' is ! true, jump to the label in `t_label', otherwise jump to the label ! in `f_label'. `PRED_CODE' are relational operator tree codes like ! `EQ_EXPR', `LT_EXPR', `LE_EXPR', `NE_EXPR', etc. ! -- GIMPLE function: gcond *gimple_build_cond_from_tree (tree cond, ! tree t_label, tree f_label) ! Build a `GIMPLE_COND' statement from the conditional expression ! tree `COND'. `T_LABEL' and `F_LABEL' are as in ! `gimple_build_cond'. -- GIMPLE function: enum tree_code gimple_cond_code (gimple g) Return the code of the predicate computed by conditional statement ! `G'. ! -- GIMPLE function: void gimple_cond_set_code (gcond *g, enum ! tree_code code) ! Set `CODE' to be the predicate code for the conditional statement ! `G'. -- GIMPLE function: tree gimple_cond_lhs (gimple g) ! Return the `LHS' of the predicate computed by conditional statement ! `G'. -- GIMPLE function: void gimple_cond_set_lhs (gcond *g, tree lhs) ! Set `LHS' to be the `LHS' operand of the predicate computed by ! conditional statement `G'. -- GIMPLE function: tree gimple_cond_rhs (gimple g) ! Return the `RHS' operand of the predicate computed by conditional ! `G'. -- GIMPLE function: void gimple_cond_set_rhs (gcond *g, tree rhs) ! Set `RHS' to be the `RHS' operand of the predicate computed by ! conditional statement `G'. -- GIMPLE function: tree gimple_cond_true_label (const gcond *g) ! Return the label used by conditional statement `G' when its predicate evaluates to true. -- GIMPLE function: void gimple_cond_set_true_label (gcond *g, tree label) ! Set `LABEL' to be the label used by conditional statement `G' when its predicate evaluates to true. -- GIMPLE function: void gimple_cond_set_false_label (gcond *g, tree label) ! Set `LABEL' to be the label used by conditional statement `G' when its predicate evaluates to false. -- GIMPLE function: tree gimple_cond_false_label (const gcond *g) ! Return the label used by conditional statement `G' when its predicate evaluates to false. -- GIMPLE function: void gimple_cond_make_false (gcond *g) ! Set the conditional `COND_STMT' to be of the form 'if (1 == 0)'. -- GIMPLE function: void gimple_cond_make_true (gcond *g) ! Set the conditional `COND_STMT' to be of the form 'if (1 == 1)'.  ! File: gccint.info, Node: `GIMPLE_DEBUG', Next: `GIMPLE_EH_FILTER', Prev: `GIMPLE_COND', Up: Tuple specific accessors ! 11.8.7 `GIMPLE_DEBUG' --------------------- -- GIMPLE function: gdebug *gimple_build_debug_bind (tree var, tree value, gimple stmt) ! Build a `GIMPLE_DEBUG' statement with `GIMPLE_DEBUG_BIND' of ! `subcode'. The effect of this statement is to tell debug information generation machinery that the value of user variable ! `var' is given by `value' at that point, and to remain with that ! value until `var' runs out of scope, a dynamically-subsequent ! debug bind statement overrides the binding, or conflicting values ! reach a control flow merge point. Even if components of the ! `value' expression change afterwards, the variable is supposed to ! retain the same value, though not necessarily the same location. ! It is expected that `var' be most often a tree for automatic user ! variables (`VAR_DECL' or `PARM_DECL') that satisfy the ! requirements for gimple registers, but it may also be a tree for a ! scalarized component of a user variable (`ARRAY_REF', ! `COMPONENT_REF'), or a debug temporary (`DEBUG_EXPR_DECL'). ! As for `value', it can be an arbitrary tree expression, but it is recommended that it be in a suitable form for a gimple assignment ! `RHS'. It is not expected that user variables that could appear ! as `var' ever appear in `value', because in the latter we'd have ! their `SSA_NAME's instead, but even if they were not in SSA form, ! user variables appearing in `value' are to be regarded as part of ! the executable code space, whereas those in `var' are to be ! regarded as part of the source code space. There is no way to ! refer to the value bound to a user variable within a `value' ! expression. ! If `value' is `GIMPLE_DEBUG_BIND_NOVALUE', debug information ! generation machinery is informed that the variable `var' is unbound, i.e., that its value is indeterminate, which sometimes means it is really unavailable, and other times that the compiler could not keep track of it. ! Block and location information for the newly-created stmt are ! taken from `stmt', if given. -- GIMPLE function: tree gimple_debug_bind_get_var (gimple stmt) ! Return the user variable VAR that is bound at `stmt'. -- GIMPLE function: tree gimple_debug_bind_get_value (gimple stmt) Return the value expression that is bound to a user variable at ! `stmt'. -- GIMPLE function: tree * gimple_debug_bind_get_value_ptr (gimple stmt) Return a pointer to the value expression that is bound to a user ! variable at `stmt'. -- GIMPLE function: void gimple_debug_bind_set_var (gimple stmt, tree var) ! Modify the user variable bound at `stmt' to VAR. ! -- GIMPLE function: void gimple_debug_bind_set_value (gimple stmt, ! tree var) ! Modify the value bound to the user variable bound at `stmt' to VALUE. -- GIMPLE function: void gimple_debug_bind_reset_value (gimple stmt) ! Modify the value bound to the user variable bound at `stmt' so ! that the variable becomes unbound. -- GIMPLE function: bool gimple_debug_bind_has_value_p (gimple stmt) ! Return `TRUE' if `stmt' binds a user variable to a value, and ! `FALSE' if it unbinds the variable.  ! File: gccint.info, Node: `GIMPLE_EH_FILTER', Next: `GIMPLE_LABEL', Prev: `GIMPLE_DEBUG', Up: Tuple specific accessors ! 11.8.8 `GIMPLE_EH_FILTER' ------------------------- -- GIMPLE function: geh_filter *gimple_build_eh_filter (tree types, gimple_seq failure) ! Build a `GIMPLE_EH_FILTER' statement. `TYPES' are the filter's ! types. `FAILURE' is a sequence with the filter's failure action. -- GIMPLE function: tree gimple_eh_filter_types (gimple g) ! Return the types handled by `GIMPLE_EH_FILTER' statement `G'. -- GIMPLE function: tree * gimple_eh_filter_types_ptr (gimple g) ! Return a pointer to the types handled by `GIMPLE_EH_FILTER' ! statement `G'. -- GIMPLE function: gimple_seq gimple_eh_filter_failure (gimple g) ! Return the sequence of statement to execute when `GIMPLE_EH_FILTER' statement fails. -- GIMPLE function: void gimple_eh_filter_set_types (geh_filter *g, tree types) ! Set `TYPES' to be the set of types handled by `GIMPLE_EH_FILTER' ! `G'. -- GIMPLE function: void gimple_eh_filter_set_failure (geh_filter *g, gimple_seq failure) ! Set `FAILURE' to be the sequence of statements to execute on ! failure for `GIMPLE_EH_FILTER' `G'. -- GIMPLE function: tree gimple_eh_must_not_throw_fndecl ( geh_mnt *eh_mnt_stmt) *************** File: gccint.info, Node: GIMPLE_EH_FILT *** 12073,12158 **** Set the function decl to be called by GS to DECL.  ! File: gccint.info, Node: GIMPLE_LABEL, Next: GIMPLE_GOTO, Prev: GIMPLE_EH_FILTER, Up: Tuple specific accessors ! 11.8.9 'GIMPLE_LABEL' --------------------- -- GIMPLE function: glabel *gimple_build_label (tree label) ! Build a 'GIMPLE_LABEL' statement with corresponding to the tree ! label, 'LABEL'. -- GIMPLE function: tree gimple_label_label (const glabel *g) ! Return the 'LABEL_DECL' node used by 'GIMPLE_LABEL' statement 'G'. -- GIMPLE function: void gimple_label_set_label (glabel *g, tree label) ! Set 'LABEL' to be the 'LABEL_DECL' node used by 'GIMPLE_LABEL' ! statement 'G'.  ! File: gccint.info, Node: GIMPLE_GOTO, Next: GIMPLE_NOP, Prev: GIMPLE_LABEL, Up: Tuple specific accessors ! 11.8.10 'GIMPLE_GOTO' --------------------- -- GIMPLE function: ggoto *gimple_build_goto (tree dest) ! Build a 'GIMPLE_GOTO' statement to label 'DEST'. -- GIMPLE function: tree gimple_goto_dest (gimple g) ! Return the destination of the unconditional jump 'G'. -- GIMPLE function: void gimple_goto_set_dest (ggoto *g, tree dest) ! Set 'DEST' to be the destination of the unconditional jump 'G'.  ! File: gccint.info, Node: GIMPLE_NOP, Next: GIMPLE_OMP_ATOMIC_LOAD, Prev: GIMPLE_GOTO, Up: Tuple specific accessors ! 11.8.11 'GIMPLE_NOP' -------------------- -- GIMPLE function: gimple gimple_build_nop (void) ! Build a 'GIMPLE_NOP' statement. -- GIMPLE function: bool gimple_nop_p (gimple g) ! Returns 'TRUE' if statement 'G' is a 'GIMPLE_NOP'.  ! File: gccint.info, Node: GIMPLE_OMP_ATOMIC_LOAD, Next: GIMPLE_OMP_ATOMIC_STORE, Prev: GIMPLE_NOP, Up: Tuple specific accessors ! 11.8.12 'GIMPLE_OMP_ATOMIC_LOAD' -------------------------------- -- GIMPLE function: gomp_atomic_load *gimple_build_omp_atomic_load ( tree lhs, tree rhs) ! Build a 'GIMPLE_OMP_ATOMIC_LOAD' statement. 'LHS' is the left-hand ! side of the assignment. 'RHS' is the right-hand side of the assignment. -- GIMPLE function: void gimple_omp_atomic_load_set_lhs ( gomp_atomic_load *g, tree lhs) ! Set the 'LHS' of an atomic load. -- GIMPLE function: tree gimple_omp_atomic_load_lhs ( const gomp_atomic_load *g) ! Get the 'LHS' of an atomic load. -- GIMPLE function: void gimple_omp_atomic_load_set_rhs ( gomp_atomic_load *g, tree rhs) ! Set the 'RHS' of an atomic set. -- GIMPLE function: tree gimple_omp_atomic_load_rhs ( const gomp_atomic_load *g) ! Get the 'RHS' of an atomic set.  ! File: gccint.info, Node: GIMPLE_OMP_ATOMIC_STORE, Next: GIMPLE_OMP_CONTINUE, Prev: GIMPLE_OMP_ATOMIC_LOAD, Up: Tuple specific accessors ! 11.8.13 'GIMPLE_OMP_ATOMIC_STORE' --------------------------------- -- GIMPLE function: gomp_atomic_store *gimple_build_omp_atomic_store ( tree val) ! Build a 'GIMPLE_OMP_ATOMIC_STORE' statement. 'VAL' is the value to be stored. -- GIMPLE function: void gimple_omp_atomic_store_set_val ( --- 12215,12300 ---- Set the function decl to be called by GS to DECL.  ! File: gccint.info, Node: `GIMPLE_LABEL', Next: `GIMPLE_GOTO', Prev: `GIMPLE_EH_FILTER', Up: Tuple specific accessors ! 11.8.9 `GIMPLE_LABEL' --------------------- -- GIMPLE function: glabel *gimple_build_label (tree label) ! Build a `GIMPLE_LABEL' statement with corresponding to the tree ! label, `LABEL'. -- GIMPLE function: tree gimple_label_label (const glabel *g) ! Return the `LABEL_DECL' node used by `GIMPLE_LABEL' statement `G'. -- GIMPLE function: void gimple_label_set_label (glabel *g, tree label) ! Set `LABEL' to be the `LABEL_DECL' node used by `GIMPLE_LABEL' ! statement `G'.  ! File: gccint.info, Node: `GIMPLE_GOTO', Next: `GIMPLE_NOP', Prev: `GIMPLE_LABEL', Up: Tuple specific accessors ! 11.8.10 `GIMPLE_GOTO' --------------------- -- GIMPLE function: ggoto *gimple_build_goto (tree dest) ! Build a `GIMPLE_GOTO' statement to label `DEST'. -- GIMPLE function: tree gimple_goto_dest (gimple g) ! Return the destination of the unconditional jump `G'. -- GIMPLE function: void gimple_goto_set_dest (ggoto *g, tree dest) ! Set `DEST' to be the destination of the unconditional jump `G'.  ! File: gccint.info, Node: `GIMPLE_NOP', Next: `GIMPLE_OMP_ATOMIC_LOAD', Prev: `GIMPLE_GOTO', Up: Tuple specific accessors ! 11.8.11 `GIMPLE_NOP' -------------------- -- GIMPLE function: gimple gimple_build_nop (void) ! Build a `GIMPLE_NOP' statement. -- GIMPLE function: bool gimple_nop_p (gimple g) ! Returns `TRUE' if statement `G' is a `GIMPLE_NOP'.  ! File: gccint.info, Node: `GIMPLE_OMP_ATOMIC_LOAD', Next: `GIMPLE_OMP_ATOMIC_STORE', Prev: `GIMPLE_NOP', Up: Tuple specific accessors ! 11.8.12 `GIMPLE_OMP_ATOMIC_LOAD' -------------------------------- -- GIMPLE function: gomp_atomic_load *gimple_build_omp_atomic_load ( tree lhs, tree rhs) ! Build a `GIMPLE_OMP_ATOMIC_LOAD' statement. `LHS' is the left-hand ! side of the assignment. `RHS' is the right-hand side of the assignment. -- GIMPLE function: void gimple_omp_atomic_load_set_lhs ( gomp_atomic_load *g, tree lhs) ! Set the `LHS' of an atomic load. -- GIMPLE function: tree gimple_omp_atomic_load_lhs ( const gomp_atomic_load *g) ! Get the `LHS' of an atomic load. -- GIMPLE function: void gimple_omp_atomic_load_set_rhs ( gomp_atomic_load *g, tree rhs) ! Set the `RHS' of an atomic set. -- GIMPLE function: tree gimple_omp_atomic_load_rhs ( const gomp_atomic_load *g) ! Get the `RHS' of an atomic set.  ! File: gccint.info, Node: `GIMPLE_OMP_ATOMIC_STORE', Next: `GIMPLE_OMP_CONTINUE', Prev: `GIMPLE_OMP_ATOMIC_LOAD', Up: Tuple specific accessors ! 11.8.13 `GIMPLE_OMP_ATOMIC_STORE' --------------------------------- -- GIMPLE function: gomp_atomic_store *gimple_build_omp_atomic_store ( tree val) ! Build a `GIMPLE_OMP_ATOMIC_STORE' statement. `VAL' is the value to be stored. -- GIMPLE function: void gimple_omp_atomic_store_set_val ( *************** File: gccint.info, Node: GIMPLE_OMP_ATO *** 12164,12184 **** Return the value being stored in an atomic store.  ! File: gccint.info, Node: GIMPLE_OMP_CONTINUE, Next: GIMPLE_OMP_CRITICAL, Prev: GIMPLE_OMP_ATOMIC_STORE, Up: Tuple specific accessors ! 11.8.14 'GIMPLE_OMP_CONTINUE' ----------------------------- -- GIMPLE function: gomp_continue *gimple_build_omp_continue ( tree control_def, tree control_use) ! Build a 'GIMPLE_OMP_CONTINUE' statement. 'CONTROL_DEF' is the ! definition of the control variable. 'CONTROL_USE' is the use of the control variable. -- GIMPLE function: tree gimple_omp_continue_control_def ( const gomp_continue *s) Return the definition of the control variable on a ! 'GIMPLE_OMP_CONTINUE' in 'S'. -- GIMPLE function: tree gimple_omp_continue_control_def_ptr ( gomp_continue *s) --- 12306,12326 ---- Return the value being stored in an atomic store.  ! File: gccint.info, Node: `GIMPLE_OMP_CONTINUE', Next: `GIMPLE_OMP_CRITICAL', Prev: `GIMPLE_OMP_ATOMIC_STORE', Up: Tuple specific accessors ! 11.8.14 `GIMPLE_OMP_CONTINUE' ----------------------------- -- GIMPLE function: gomp_continue *gimple_build_omp_continue ( tree control_def, tree control_use) ! Build a `GIMPLE_OMP_CONTINUE' statement. `CONTROL_DEF' is the ! definition of the control variable. `CONTROL_USE' is the use of the control variable. -- GIMPLE function: tree gimple_omp_continue_control_def ( const gomp_continue *s) Return the definition of the control variable on a ! `GIMPLE_OMP_CONTINUE' in `S'. -- GIMPLE function: tree gimple_omp_continue_control_def_ptr ( gomp_continue *s) *************** File: gccint.info, Node: GIMPLE_OMP_CON *** 12186,12198 **** -- GIMPLE function: tree gimple_omp_continue_set_control_def ( gomp_continue *s) ! Set the control variable definition for a 'GIMPLE_OMP_CONTINUE' ! statement in 'S'. -- GIMPLE function: tree gimple_omp_continue_control_use ( const gomp_continue *s) ! Return the use of the control variable on a 'GIMPLE_OMP_CONTINUE' ! in 'S'. -- GIMPLE function: tree gimple_omp_continue_control_use_ptr ( gomp_continue *s) --- 12328,12340 ---- -- GIMPLE function: tree gimple_omp_continue_set_control_def ( gomp_continue *s) ! Set the control variable definition for a `GIMPLE_OMP_CONTINUE' ! statement in `S'. -- GIMPLE function: tree gimple_omp_continue_control_use ( const gomp_continue *s) ! Return the use of the control variable on a `GIMPLE_OMP_CONTINUE' ! in `S'. -- GIMPLE function: tree gimple_omp_continue_control_use_ptr ( gomp_continue *s) *************** File: gccint.info, Node: GIMPLE_OMP_CON *** 12200,12612 **** -- GIMPLE function: tree gimple_omp_continue_set_control_use ( gomp_continue *s) ! Set the control variable use for a 'GIMPLE_OMP_CONTINUE' statement ! in 'S'.  ! File: gccint.info, Node: GIMPLE_OMP_CRITICAL, Next: GIMPLE_OMP_FOR, Prev: GIMPLE_OMP_CONTINUE, Up: Tuple specific accessors ! 11.8.15 'GIMPLE_OMP_CRITICAL' ----------------------------- -- GIMPLE function: gomp_critical *gimple_build_omp_critical ( gimple_seq body, tree name) ! Build a 'GIMPLE_OMP_CRITICAL' statement. 'BODY' is the sequence of ! statements for which only one thread can execute. 'NAME' is an optional identifier for this critical block. ! -- GIMPLE function: tree gimple_omp_critical_name ( const gomp_critical ! *g) ! Return the name associated with 'OMP_CRITICAL' statement 'G'. ! -- GIMPLE function: tree * gimple_omp_critical_name_ptr ( gomp_critical ! *g) ! Return a pointer to the name associated with 'OMP' critical ! statement 'G'. -- GIMPLE function: void gimple_omp_critical_set_name ( gomp_critical *g, tree name) ! Set 'NAME' to be the name associated with 'OMP' critical statement ! 'G'.  ! File: gccint.info, Node: GIMPLE_OMP_FOR, Next: GIMPLE_OMP_MASTER, Prev: GIMPLE_OMP_CRITICAL, Up: Tuple specific accessors ! 11.8.16 'GIMPLE_OMP_FOR' ------------------------ -- GIMPLE function: gomp_for *gimple_build_omp_for (gimple_seq body, ! tree clauses, tree index, tree initial, tree final, tree incr, ! gimple_seq pre_body, enum tree_code omp_for_cond) ! Build a 'GIMPLE_OMP_FOR' statement. 'BODY' is sequence of ! statements inside the for loop. 'CLAUSES', are any of the loop ! construct's clauses. 'PRE_BODY' is the sequence of statements that ! are loop invariant. 'INDEX' is the index variable. 'INITIAL' is ! the initial value of 'INDEX'. 'FINAL' is final value of 'INDEX'. ! OMP_FOR_COND is the predicate used to compare 'INDEX' and 'FINAL'. ! 'INCR' is the increment expression. -- GIMPLE function: tree gimple_omp_for_clauses (gimple g) ! Return the clauses associated with 'OMP_FOR' 'G'. -- GIMPLE function: tree * gimple_omp_for_clauses_ptr (gimple g) ! Return a pointer to the 'OMP_FOR' 'G'. -- GIMPLE function: void gimple_omp_for_set_clauses (gimple g, tree clauses) ! Set 'CLAUSES' to be the list of clauses associated with 'OMP_FOR' ! 'G'. -- GIMPLE function: tree gimple_omp_for_index (gimple g) ! Return the index variable for 'OMP_FOR' 'G'. -- GIMPLE function: tree * gimple_omp_for_index_ptr (gimple g) ! Return a pointer to the index variable for 'OMP_FOR' 'G'. -- GIMPLE function: void gimple_omp_for_set_index (gimple g, tree index) ! Set 'INDEX' to be the index variable for 'OMP_FOR' 'G'. -- GIMPLE function: tree gimple_omp_for_initial (gimple g) ! Return the initial value for 'OMP_FOR' 'G'. -- GIMPLE function: tree * gimple_omp_for_initial_ptr (gimple g) ! Return a pointer to the initial value for 'OMP_FOR' 'G'. -- GIMPLE function: void gimple_omp_for_set_initial (gimple g, tree initial) ! Set 'INITIAL' to be the initial value for 'OMP_FOR' 'G'. -- GIMPLE function: tree gimple_omp_for_final (gimple g) ! Return the final value for 'OMP_FOR' 'G'. -- GIMPLE function: tree * gimple_omp_for_final_ptr (gimple g) ! turn a pointer to the final value for 'OMP_FOR' 'G'. -- GIMPLE function: void gimple_omp_for_set_final (gimple g, tree final) ! Set 'FINAL' to be the final value for 'OMP_FOR' 'G'. -- GIMPLE function: tree gimple_omp_for_incr (gimple g) ! Return the increment value for 'OMP_FOR' 'G'. -- GIMPLE function: tree * gimple_omp_for_incr_ptr (gimple g) ! Return a pointer to the increment value for 'OMP_FOR' 'G'. -- GIMPLE function: void gimple_omp_for_set_incr (gimple g, tree incr) ! Set 'INCR' to be the increment value for 'OMP_FOR' 'G'. -- GIMPLE function: gimple_seq gimple_omp_for_pre_body (gimple g) ! Return the sequence of statements to execute before the 'OMP_FOR' ! statement 'G' starts. -- GIMPLE function: void gimple_omp_for_set_pre_body (gimple g, gimple_seq pre_body) ! Set 'PRE_BODY' to be the sequence of statements to execute before ! the 'OMP_FOR' statement 'G' starts. -- GIMPLE function: void gimple_omp_for_set_cond (gimple g, enum tree_code cond) ! Set 'COND' to be the condition code for 'OMP_FOR' 'G'. -- GIMPLE function: enum tree_code gimple_omp_for_cond (gimple g) ! Return the condition code associated with 'OMP_FOR' 'G'.  ! File: gccint.info, Node: GIMPLE_OMP_MASTER, Next: GIMPLE_OMP_ORDERED, Prev: GIMPLE_OMP_FOR, Up: Tuple specific accessors ! 11.8.17 'GIMPLE_OMP_MASTER' --------------------------- -- GIMPLE function: gimple gimple_build_omp_master (gimple_seq body) ! Build a 'GIMPLE_OMP_MASTER' statement. 'BODY' is the sequence of statements to be executed by just the master.  ! File: gccint.info, Node: GIMPLE_OMP_ORDERED, Next: GIMPLE_OMP_PARALLEL, Prev: GIMPLE_OMP_MASTER, Up: Tuple specific accessors ! 11.8.18 'GIMPLE_OMP_ORDERED' ---------------------------- -- GIMPLE function: gimple gimple_build_omp_ordered (gimple_seq body) ! Build a 'GIMPLE_OMP_ORDERED' statement. ! 'BODY' is the sequence of statements inside a loop that will executed in sequence.  ! File: gccint.info, Node: GIMPLE_OMP_PARALLEL, Next: GIMPLE_OMP_RETURN, Prev: GIMPLE_OMP_ORDERED, Up: Tuple specific accessors ! 11.8.19 'GIMPLE_OMP_PARALLEL' ----------------------------- ! -- GIMPLE function: gomp_parallel *gimple_build_omp_parallel ! (gimple_seq body, tree clauses, tree child_fn, tree data_arg) ! Build a 'GIMPLE_OMP_PARALLEL' statement. ! 'BODY' is sequence of statements which are executed in parallel. ! 'CLAUSES', are the 'OMP' parallel construct's clauses. 'CHILD_FN' is ! the function created for the parallel threads to execute. 'DATA_ARG' are the shared data argument(s). -- GIMPLE function: bool gimple_omp_parallel_combined_p (gimple g) ! Return true if 'OMP' parallel statement 'G' has the ! 'GF_OMP_PARALLEL_COMBINED' flag set. -- GIMPLE function: void gimple_omp_parallel_set_combined_p (gimple g) ! Set the 'GF_OMP_PARALLEL_COMBINED' field in 'OMP' parallel ! statement 'G'. -- GIMPLE function: gimple_seq gimple_omp_body (gimple g) ! Return the body for the 'OMP' statement 'G'. -- GIMPLE function: void gimple_omp_set_body (gimple g, gimple_seq body) ! Set 'BODY' to be the body for the 'OMP' statement 'G'. -- GIMPLE function: tree gimple_omp_parallel_clauses (gimple g) ! Return the clauses associated with 'OMP_PARALLEL' 'G'. -- GIMPLE function: tree * gimple_omp_parallel_clauses_ptr ( gomp_parallel *g) ! Return a pointer to the clauses associated with 'OMP_PARALLEL' 'G'. -- GIMPLE function: void gimple_omp_parallel_set_clauses ( gomp_parallel *g, tree clauses) ! Set 'CLAUSES' to be the list of clauses associated with ! 'OMP_PARALLEL' 'G'. -- GIMPLE function: tree gimple_omp_parallel_child_fn ( const gomp_parallel *g) ! Return the child function used to hold the body of 'OMP_PARALLEL' ! 'G'. -- GIMPLE function: tree * gimple_omp_parallel_child_fn_ptr ( gomp_parallel *g) Return a pointer to the child function used to hold the body of ! 'OMP_PARALLEL' 'G'. -- GIMPLE function: void gimple_omp_parallel_set_child_fn ( gomp_parallel *g, tree child_fn) ! Set 'CHILD_FN' to be the child function for 'OMP_PARALLEL' 'G'. -- GIMPLE function: tree gimple_omp_parallel_data_arg ( const gomp_parallel *g) Return the artificial argument used to send variables and values ! from the parent to the children threads in 'OMP_PARALLEL' 'G'. -- GIMPLE function: tree * gimple_omp_parallel_data_arg_ptr ( gomp_parallel *g) ! Return a pointer to the data argument for 'OMP_PARALLEL' 'G'. -- GIMPLE function: void gimple_omp_parallel_set_data_arg ( gomp_parallel *g, tree data_arg) ! Set 'DATA_ARG' to be the data argument for 'OMP_PARALLEL' 'G'.  ! File: gccint.info, Node: GIMPLE_OMP_RETURN, Next: GIMPLE_OMP_SECTION, Prev: GIMPLE_OMP_PARALLEL, Up: Tuple specific accessors ! 11.8.20 'GIMPLE_OMP_RETURN' --------------------------- -- GIMPLE function: gimple gimple_build_omp_return (bool wait_p) ! Build a 'GIMPLE_OMP_RETURN' statement. 'WAIT_P' is true if this is a non-waiting return. -- GIMPLE function: void gimple_omp_return_set_nowait (gimple s) ! Set the nowait flag on 'GIMPLE_OMP_RETURN' statement 'S'. -- GIMPLE function: bool gimple_omp_return_nowait_p (gimple g) ! Return true if 'OMP' return statement 'G' has the ! 'GF_OMP_RETURN_NOWAIT' flag set.  ! File: gccint.info, Node: GIMPLE_OMP_SECTION, Next: GIMPLE_OMP_SECTIONS, Prev: GIMPLE_OMP_RETURN, Up: Tuple specific accessors ! 11.8.21 'GIMPLE_OMP_SECTION' ---------------------------- -- GIMPLE function: gimple gimple_build_omp_section (gimple_seq body) ! Build a 'GIMPLE_OMP_SECTION' statement for a sections statement. ! 'BODY' is the sequence of statements in the section. -- GIMPLE function: bool gimple_omp_section_last_p (gimple g) ! Return true if 'OMP' section statement 'G' has the ! 'GF_OMP_SECTION_LAST' flag set. -- GIMPLE function: void gimple_omp_section_set_last (gimple g) ! Set the 'GF_OMP_SECTION_LAST' flag on 'G'.  ! File: gccint.info, Node: GIMPLE_OMP_SECTIONS, Next: GIMPLE_OMP_SINGLE, Prev: GIMPLE_OMP_SECTION, Up: Tuple specific accessors ! 11.8.22 'GIMPLE_OMP_SECTIONS' ----------------------------- -- GIMPLE function: gomp_sections *gimple_build_omp_sections ( gimple_seq body, tree clauses) ! Build a 'GIMPLE_OMP_SECTIONS' statement. 'BODY' is a sequence of ! section statements. 'CLAUSES' are any of the 'OMP' sections ! construct's clauses: private, firstprivate, lastprivate, reduction, ! and nowait. -- GIMPLE function: gimple gimple_build_omp_sections_switch (void) ! Build a 'GIMPLE_OMP_SECTIONS_SWITCH' statement. -- GIMPLE function: tree gimple_omp_sections_control (gimple g) Return the control variable associated with the ! 'GIMPLE_OMP_SECTIONS' in 'G'. -- GIMPLE function: tree * gimple_omp_sections_control_ptr (gimple g) Return a pointer to the clauses associated with the ! 'GIMPLE_OMP_SECTIONS' in 'G'. -- GIMPLE function: void gimple_omp_sections_set_control (gimple g, tree control) ! Set 'CONTROL' to be the set of clauses associated with the ! 'GIMPLE_OMP_SECTIONS' in 'G'. -- GIMPLE function: tree gimple_omp_sections_clauses (gimple g) ! Return the clauses associated with 'OMP_SECTIONS' 'G'. -- GIMPLE function: tree * gimple_omp_sections_clauses_ptr (gimple g) ! Return a pointer to the clauses associated with 'OMP_SECTIONS' 'G'. -- GIMPLE function: void gimple_omp_sections_set_clauses (gimple g, tree clauses) ! Set 'CLAUSES' to be the set of clauses associated with ! 'OMP_SECTIONS' 'G'.  ! File: gccint.info, Node: GIMPLE_OMP_SINGLE, Next: GIMPLE_PHI, Prev: GIMPLE_OMP_SECTIONS, Up: Tuple specific accessors ! 11.8.23 'GIMPLE_OMP_SINGLE' --------------------------- -- GIMPLE function: gomp_single *gimple_build_omp_single ( gimple_seq body, tree clauses) ! Build a 'GIMPLE_OMP_SINGLE' statement. 'BODY' is the sequence of ! statements that will be executed once. 'CLAUSES' are any of the ! 'OMP' single construct's clauses: private, firstprivate, copyprivate, nowait. -- GIMPLE function: tree gimple_omp_single_clauses (gimple g) ! Return the clauses associated with 'OMP_SINGLE' 'G'. -- GIMPLE function: tree * gimple_omp_single_clauses_ptr (gimple g) ! Return a pointer to the clauses associated with 'OMP_SINGLE' 'G'. -- GIMPLE function: void gimple_omp_single_set_clauses ( gomp_single *g, tree clauses) ! Set 'CLAUSES' to be the clauses associated with 'OMP_SINGLE' 'G'.  ! File: gccint.info, Node: GIMPLE_PHI, Next: GIMPLE_RESX, Prev: GIMPLE_OMP_SINGLE, Up: Tuple specific accessors ! 11.8.24 'GIMPLE_PHI' -------------------- -- GIMPLE function: unsigned gimple_phi_capacity (gimple g) ! Return the maximum number of arguments supported by 'GIMPLE_PHI' ! 'G'. -- GIMPLE function: unsigned gimple_phi_num_args (gimple g) ! Return the number of arguments in 'GIMPLE_PHI' 'G'. This must always be exactly the number of incoming edges for the basic block ! holding 'G'. -- GIMPLE function: tree gimple_phi_result (gimple g) ! Return the 'SSA' name created by 'GIMPLE_PHI' 'G'. -- GIMPLE function: tree * gimple_phi_result_ptr (gimple g) ! Return a pointer to the 'SSA' name created by 'GIMPLE_PHI' 'G'. -- GIMPLE function: void gimple_phi_set_result (gphi *g, tree result) ! Set 'RESULT' to be the 'SSA' name created by 'GIMPLE_PHI' 'G'. -- GIMPLE function: struct phi_arg_d * gimple_phi_arg (gimple g, index) ! Return the 'PHI' argument corresponding to incoming edge 'INDEX' ! for 'GIMPLE_PHI' 'G'. -- GIMPLE function: void gimple_phi_set_arg (gphi *g, index, struct phi_arg_d * phiarg) ! Set 'PHIARG' to be the argument corresponding to incoming edge ! 'INDEX' for 'GIMPLE_PHI' 'G'.  ! File: gccint.info, Node: GIMPLE_RESX, Next: GIMPLE_RETURN, Prev: GIMPLE_PHI, Up: Tuple specific accessors ! 11.8.25 'GIMPLE_RESX' --------------------- -- GIMPLE function: gresx *gimple_build_resx (int region) ! Build a 'GIMPLE_RESX' statement which is a statement. This statement is a placeholder for _Unwind_Resume before we know if a ! function call or a branch is needed. 'REGION' is the exception region from which control is flowing. -- GIMPLE function: int gimple_resx_region (const gresx *g) ! Return the region number for 'GIMPLE_RESX' 'G'. -- GIMPLE function: void gimple_resx_set_region (gresx *g, int region) ! Set 'REGION' to be the region number for 'GIMPLE_RESX' 'G'.  ! File: gccint.info, Node: GIMPLE_RETURN, Next: GIMPLE_SWITCH, Prev: GIMPLE_RESX, Up: Tuple specific accessors ! 11.8.26 'GIMPLE_RETURN' ----------------------- -- GIMPLE function: greturn *gimple_build_return (tree retval) ! Build a 'GIMPLE_RETURN' statement whose return value is retval. -- GIMPLE function: tree gimple_return_retval (const greturn *g) ! Return the return value for 'GIMPLE_RETURN' 'G'. -- GIMPLE function: void gimple_return_set_retval (greturn *g, tree retval) ! Set 'RETVAL' to be the return value for 'GIMPLE_RETURN' 'G'.  ! File: gccint.info, Node: GIMPLE_SWITCH, Next: GIMPLE_TRY, Prev: GIMPLE_RETURN, Up: Tuple specific accessors ! 11.8.27 'GIMPLE_SWITCH' ----------------------- -- GIMPLE function: gswitch *gimple_build_switch (tree index, tree ! default_label, 'vec' *args) ! Build a 'GIMPLE_SWITCH' statement. 'INDEX' is the index variable ! to switch on, and 'DEFAULT_LABEL' represents the default label. ! 'ARGS' is a vector of 'CASE_LABEL_EXPR' trees that contain the non-default case labels. Each label is a tree of code ! 'CASE_LABEL_EXPR'. -- GIMPLE function: unsigned gimple_switch_num_labels ( const gswitch *g) Return the number of labels associated with the switch statement ! 'G'. -- GIMPLE function: void gimple_switch_set_num_labels (gswitch *g, unsigned nlabels) ! Set 'NLABELS' to be the number of labels for the switch statement ! 'G'. -- GIMPLE function: tree gimple_switch_index (const gswitch *g) ! Return the index variable used by the switch statement 'G'. -- GIMPLE function: void gimple_switch_set_index (gswitch *g, tree index) ! Set 'INDEX' to be the index variable for switch statement 'G'. -- GIMPLE function: tree gimple_switch_label (const gswitch *g, unsigned index) ! Return the label numbered 'INDEX'. The default label is 0, ! followed by any labels in a switch statement. -- GIMPLE function: void gimple_switch_set_label (gswitch *g, unsigned index, tree label) ! Set the label number 'INDEX' to 'LABEL'. 0 is always the default label. -- GIMPLE function: tree gimple_switch_default_label ( const gswitch --- 12342,12754 ---- -- GIMPLE function: tree gimple_omp_continue_set_control_use ( gomp_continue *s) ! Set the control variable use for a `GIMPLE_OMP_CONTINUE' statement ! in `S'.  ! File: gccint.info, Node: `GIMPLE_OMP_CRITICAL', Next: `GIMPLE_OMP_FOR', Prev: `GIMPLE_OMP_CONTINUE', Up: Tuple specific accessors ! 11.8.15 `GIMPLE_OMP_CRITICAL' ----------------------------- -- GIMPLE function: gomp_critical *gimple_build_omp_critical ( gimple_seq body, tree name) ! Build a `GIMPLE_OMP_CRITICAL' statement. `BODY' is the sequence of ! statements for which only one thread can execute. `NAME' is an optional identifier for this critical block. ! -- GIMPLE function: tree gimple_omp_critical_name ( const ! gomp_critical *g) ! Return the name associated with `OMP_CRITICAL' statement `G'. ! -- GIMPLE function: tree * gimple_omp_critical_name_ptr ( ! gomp_critical *g) ! Return a pointer to the name associated with `OMP' critical ! statement `G'. -- GIMPLE function: void gimple_omp_critical_set_name ( gomp_critical *g, tree name) ! Set `NAME' to be the name associated with `OMP' critical statement ! `G'.  ! File: gccint.info, Node: `GIMPLE_OMP_FOR', Next: `GIMPLE_OMP_MASTER', Prev: `GIMPLE_OMP_CRITICAL', Up: Tuple specific accessors ! 11.8.16 `GIMPLE_OMP_FOR' ------------------------ -- GIMPLE function: gomp_for *gimple_build_omp_for (gimple_seq body, ! tree clauses, tree index, tree initial, tree final, tree ! incr, gimple_seq pre_body, enum tree_code omp_for_cond) ! Build a `GIMPLE_OMP_FOR' statement. `BODY' is sequence of ! statements inside the for loop. `CLAUSES', are any of the loop ! construct's clauses. `PRE_BODY' is the sequence of statements ! that are loop invariant. `INDEX' is the index variable. ! `INITIAL' is the initial value of `INDEX'. `FINAL' is final value ! of `INDEX'. OMP_FOR_COND is the predicate used to compare `INDEX' ! and `FINAL'. `INCR' is the increment expression. -- GIMPLE function: tree gimple_omp_for_clauses (gimple g) ! Return the clauses associated with `OMP_FOR' `G'. -- GIMPLE function: tree * gimple_omp_for_clauses_ptr (gimple g) ! Return a pointer to the `OMP_FOR' `G'. -- GIMPLE function: void gimple_omp_for_set_clauses (gimple g, tree clauses) ! Set `CLAUSES' to be the list of clauses associated with `OMP_FOR' ! `G'. -- GIMPLE function: tree gimple_omp_for_index (gimple g) ! Return the index variable for `OMP_FOR' `G'. -- GIMPLE function: tree * gimple_omp_for_index_ptr (gimple g) ! Return a pointer to the index variable for `OMP_FOR' `G'. -- GIMPLE function: void gimple_omp_for_set_index (gimple g, tree index) ! Set `INDEX' to be the index variable for `OMP_FOR' `G'. -- GIMPLE function: tree gimple_omp_for_initial (gimple g) ! Return the initial value for `OMP_FOR' `G'. -- GIMPLE function: tree * gimple_omp_for_initial_ptr (gimple g) ! Return a pointer to the initial value for `OMP_FOR' `G'. -- GIMPLE function: void gimple_omp_for_set_initial (gimple g, tree initial) ! Set `INITIAL' to be the initial value for `OMP_FOR' `G'. -- GIMPLE function: tree gimple_omp_for_final (gimple g) ! Return the final value for `OMP_FOR' `G'. -- GIMPLE function: tree * gimple_omp_for_final_ptr (gimple g) ! turn a pointer to the final value for `OMP_FOR' `G'. -- GIMPLE function: void gimple_omp_for_set_final (gimple g, tree final) ! Set `FINAL' to be the final value for `OMP_FOR' `G'. -- GIMPLE function: tree gimple_omp_for_incr (gimple g) ! Return the increment value for `OMP_FOR' `G'. -- GIMPLE function: tree * gimple_omp_for_incr_ptr (gimple g) ! Return a pointer to the increment value for `OMP_FOR' `G'. -- GIMPLE function: void gimple_omp_for_set_incr (gimple g, tree incr) ! Set `INCR' to be the increment value for `OMP_FOR' `G'. -- GIMPLE function: gimple_seq gimple_omp_for_pre_body (gimple g) ! Return the sequence of statements to execute before the `OMP_FOR' ! statement `G' starts. -- GIMPLE function: void gimple_omp_for_set_pre_body (gimple g, gimple_seq pre_body) ! Set `PRE_BODY' to be the sequence of statements to execute before ! the `OMP_FOR' statement `G' starts. -- GIMPLE function: void gimple_omp_for_set_cond (gimple g, enum tree_code cond) ! Set `COND' to be the condition code for `OMP_FOR' `G'. -- GIMPLE function: enum tree_code gimple_omp_for_cond (gimple g) ! Return the condition code associated with `OMP_FOR' `G'.  ! File: gccint.info, Node: `GIMPLE_OMP_MASTER', Next: `GIMPLE_OMP_ORDERED', Prev: `GIMPLE_OMP_FOR', Up: Tuple specific accessors ! 11.8.17 `GIMPLE_OMP_MASTER' --------------------------- -- GIMPLE function: gimple gimple_build_omp_master (gimple_seq body) ! Build a `GIMPLE_OMP_MASTER' statement. `BODY' is the sequence of statements to be executed by just the master.  ! File: gccint.info, Node: `GIMPLE_OMP_ORDERED', Next: `GIMPLE_OMP_PARALLEL', Prev: `GIMPLE_OMP_MASTER', Up: Tuple specific accessors ! 11.8.18 `GIMPLE_OMP_ORDERED' ---------------------------- -- GIMPLE function: gimple gimple_build_omp_ordered (gimple_seq body) ! Build a `GIMPLE_OMP_ORDERED' statement. ! `BODY' is the sequence of statements inside a loop that will executed in sequence.  ! File: gccint.info, Node: `GIMPLE_OMP_PARALLEL', Next: `GIMPLE_OMP_RETURN', Prev: `GIMPLE_OMP_ORDERED', Up: Tuple specific accessors ! 11.8.19 `GIMPLE_OMP_PARALLEL' ----------------------------- ! -- GIMPLE function: gomp_parallel *gimple_build_omp_parallel ( ! gimple_seq body, tree clauses, tree child_fn, tree data_arg) ! Build a `GIMPLE_OMP_PARALLEL' statement. ! `BODY' is sequence of statements which are executed in parallel. ! `CLAUSES', are the `OMP' parallel construct's clauses. `CHILD_FN' is ! the function created for the parallel threads to execute. `DATA_ARG' are the shared data argument(s). -- GIMPLE function: bool gimple_omp_parallel_combined_p (gimple g) ! Return true if `OMP' parallel statement `G' has the ! `GF_OMP_PARALLEL_COMBINED' flag set. -- GIMPLE function: void gimple_omp_parallel_set_combined_p (gimple g) ! Set the `GF_OMP_PARALLEL_COMBINED' field in `OMP' parallel ! statement `G'. -- GIMPLE function: gimple_seq gimple_omp_body (gimple g) ! Return the body for the `OMP' statement `G'. -- GIMPLE function: void gimple_omp_set_body (gimple g, gimple_seq body) ! Set `BODY' to be the body for the `OMP' statement `G'. -- GIMPLE function: tree gimple_omp_parallel_clauses (gimple g) ! Return the clauses associated with `OMP_PARALLEL' `G'. -- GIMPLE function: tree * gimple_omp_parallel_clauses_ptr ( gomp_parallel *g) ! Return a pointer to the clauses associated with `OMP_PARALLEL' `G'. -- GIMPLE function: void gimple_omp_parallel_set_clauses ( gomp_parallel *g, tree clauses) ! Set `CLAUSES' to be the list of clauses associated with ! `OMP_PARALLEL' `G'. -- GIMPLE function: tree gimple_omp_parallel_child_fn ( const gomp_parallel *g) ! Return the child function used to hold the body of `OMP_PARALLEL' ! `G'. -- GIMPLE function: tree * gimple_omp_parallel_child_fn_ptr ( gomp_parallel *g) Return a pointer to the child function used to hold the body of ! `OMP_PARALLEL' `G'. -- GIMPLE function: void gimple_omp_parallel_set_child_fn ( gomp_parallel *g, tree child_fn) ! Set `CHILD_FN' to be the child function for `OMP_PARALLEL' `G'. -- GIMPLE function: tree gimple_omp_parallel_data_arg ( const gomp_parallel *g) Return the artificial argument used to send variables and values ! from the parent to the children threads in `OMP_PARALLEL' `G'. -- GIMPLE function: tree * gimple_omp_parallel_data_arg_ptr ( gomp_parallel *g) ! Return a pointer to the data argument for `OMP_PARALLEL' `G'. -- GIMPLE function: void gimple_omp_parallel_set_data_arg ( gomp_parallel *g, tree data_arg) ! Set `DATA_ARG' to be the data argument for `OMP_PARALLEL' `G'.  ! File: gccint.info, Node: `GIMPLE_OMP_RETURN', Next: `GIMPLE_OMP_SECTION', Prev: `GIMPLE_OMP_PARALLEL', Up: Tuple specific accessors ! 11.8.20 `GIMPLE_OMP_RETURN' --------------------------- -- GIMPLE function: gimple gimple_build_omp_return (bool wait_p) ! Build a `GIMPLE_OMP_RETURN' statement. `WAIT_P' is true if this is a non-waiting return. -- GIMPLE function: void gimple_omp_return_set_nowait (gimple s) ! Set the nowait flag on `GIMPLE_OMP_RETURN' statement `S'. -- GIMPLE function: bool gimple_omp_return_nowait_p (gimple g) ! Return true if `OMP' return statement `G' has the ! `GF_OMP_RETURN_NOWAIT' flag set.  ! File: gccint.info, Node: `GIMPLE_OMP_SECTION', Next: `GIMPLE_OMP_SECTIONS', Prev: `GIMPLE_OMP_RETURN', Up: Tuple specific accessors ! 11.8.21 `GIMPLE_OMP_SECTION' ---------------------------- -- GIMPLE function: gimple gimple_build_omp_section (gimple_seq body) ! Build a `GIMPLE_OMP_SECTION' statement for a sections statement. ! `BODY' is the sequence of statements in the section. -- GIMPLE function: bool gimple_omp_section_last_p (gimple g) ! Return true if `OMP' section statement `G' has the ! `GF_OMP_SECTION_LAST' flag set. -- GIMPLE function: void gimple_omp_section_set_last (gimple g) ! Set the `GF_OMP_SECTION_LAST' flag on `G'.  ! File: gccint.info, Node: `GIMPLE_OMP_SECTIONS', Next: `GIMPLE_OMP_SINGLE', Prev: `GIMPLE_OMP_SECTION', Up: Tuple specific accessors ! 11.8.22 `GIMPLE_OMP_SECTIONS' ----------------------------- -- GIMPLE function: gomp_sections *gimple_build_omp_sections ( gimple_seq body, tree clauses) ! Build a `GIMPLE_OMP_SECTIONS' statement. `BODY' is a sequence of ! section statements. `CLAUSES' are any of the `OMP' sections ! construct's clauses: private, firstprivate, lastprivate, ! reduction, and nowait. -- GIMPLE function: gimple gimple_build_omp_sections_switch (void) ! Build a `GIMPLE_OMP_SECTIONS_SWITCH' statement. -- GIMPLE function: tree gimple_omp_sections_control (gimple g) Return the control variable associated with the ! `GIMPLE_OMP_SECTIONS' in `G'. -- GIMPLE function: tree * gimple_omp_sections_control_ptr (gimple g) Return a pointer to the clauses associated with the ! `GIMPLE_OMP_SECTIONS' in `G'. -- GIMPLE function: void gimple_omp_sections_set_control (gimple g, tree control) ! Set `CONTROL' to be the set of clauses associated with the ! `GIMPLE_OMP_SECTIONS' in `G'. -- GIMPLE function: tree gimple_omp_sections_clauses (gimple g) ! Return the clauses associated with `OMP_SECTIONS' `G'. -- GIMPLE function: tree * gimple_omp_sections_clauses_ptr (gimple g) ! Return a pointer to the clauses associated with `OMP_SECTIONS' `G'. -- GIMPLE function: void gimple_omp_sections_set_clauses (gimple g, tree clauses) ! Set `CLAUSES' to be the set of clauses associated with ! `OMP_SECTIONS' `G'.  ! File: gccint.info, Node: `GIMPLE_OMP_SINGLE', Next: `GIMPLE_PHI', Prev: `GIMPLE_OMP_SECTIONS', Up: Tuple specific accessors ! 11.8.23 `GIMPLE_OMP_SINGLE' --------------------------- -- GIMPLE function: gomp_single *gimple_build_omp_single ( gimple_seq body, tree clauses) ! Build a `GIMPLE_OMP_SINGLE' statement. `BODY' is the sequence of ! statements that will be executed once. `CLAUSES' are any of the ! `OMP' single construct's clauses: private, firstprivate, copyprivate, nowait. -- GIMPLE function: tree gimple_omp_single_clauses (gimple g) ! Return the clauses associated with `OMP_SINGLE' `G'. -- GIMPLE function: tree * gimple_omp_single_clauses_ptr (gimple g) ! Return a pointer to the clauses associated with `OMP_SINGLE' `G'. -- GIMPLE function: void gimple_omp_single_set_clauses ( gomp_single *g, tree clauses) ! Set `CLAUSES' to be the clauses associated with `OMP_SINGLE' `G'.  ! File: gccint.info, Node: `GIMPLE_PHI', Next: `GIMPLE_RESX', Prev: `GIMPLE_OMP_SINGLE', Up: Tuple specific accessors ! 11.8.24 `GIMPLE_PHI' -------------------- -- GIMPLE function: unsigned gimple_phi_capacity (gimple g) ! Return the maximum number of arguments supported by `GIMPLE_PHI' ! `G'. -- GIMPLE function: unsigned gimple_phi_num_args (gimple g) ! Return the number of arguments in `GIMPLE_PHI' `G'. This must always be exactly the number of incoming edges for the basic block ! holding `G'. -- GIMPLE function: tree gimple_phi_result (gimple g) ! Return the `SSA' name created by `GIMPLE_PHI' `G'. -- GIMPLE function: tree * gimple_phi_result_ptr (gimple g) ! Return a pointer to the `SSA' name created by `GIMPLE_PHI' `G'. -- GIMPLE function: void gimple_phi_set_result (gphi *g, tree result) ! Set `RESULT' to be the `SSA' name created by `GIMPLE_PHI' `G'. -- GIMPLE function: struct phi_arg_d * gimple_phi_arg (gimple g, index) ! Return the `PHI' argument corresponding to incoming edge `INDEX' ! for `GIMPLE_PHI' `G'. -- GIMPLE function: void gimple_phi_set_arg (gphi *g, index, struct phi_arg_d * phiarg) ! Set `PHIARG' to be the argument corresponding to incoming edge ! `INDEX' for `GIMPLE_PHI' `G'.  ! File: gccint.info, Node: `GIMPLE_RESX', Next: `GIMPLE_RETURN', Prev: `GIMPLE_PHI', Up: Tuple specific accessors ! 11.8.25 `GIMPLE_RESX' --------------------- -- GIMPLE function: gresx *gimple_build_resx (int region) ! Build a `GIMPLE_RESX' statement which is a statement. This statement is a placeholder for _Unwind_Resume before we know if a ! function call or a branch is needed. `REGION' is the exception region from which control is flowing. -- GIMPLE function: int gimple_resx_region (const gresx *g) ! Return the region number for `GIMPLE_RESX' `G'. -- GIMPLE function: void gimple_resx_set_region (gresx *g, int region) ! Set `REGION' to be the region number for `GIMPLE_RESX' `G'.  ! File: gccint.info, Node: `GIMPLE_RETURN', Next: `GIMPLE_SWITCH', Prev: `GIMPLE_RESX', Up: Tuple specific accessors ! 11.8.26 `GIMPLE_RETURN' ----------------------- -- GIMPLE function: greturn *gimple_build_return (tree retval) ! Build a `GIMPLE_RETURN' statement whose return value is retval. -- GIMPLE function: tree gimple_return_retval (const greturn *g) ! Return the return value for `GIMPLE_RETURN' `G'. -- GIMPLE function: void gimple_return_set_retval (greturn *g, tree retval) ! Set `RETVAL' to be the return value for `GIMPLE_RETURN' `G'.  ! File: gccint.info, Node: `GIMPLE_SWITCH', Next: `GIMPLE_TRY', Prev: `GIMPLE_RETURN', Up: Tuple specific accessors ! 11.8.27 `GIMPLE_SWITCH' ----------------------- -- GIMPLE function: gswitch *gimple_build_switch (tree index, tree ! default_label, `vec' *args) ! Build a `GIMPLE_SWITCH' statement. `INDEX' is the index variable ! to switch on, and `DEFAULT_LABEL' represents the default label. ! `ARGS' is a vector of `CASE_LABEL_EXPR' trees that contain the non-default case labels. Each label is a tree of code ! `CASE_LABEL_EXPR'. -- GIMPLE function: unsigned gimple_switch_num_labels ( const gswitch *g) Return the number of labels associated with the switch statement ! `G'. -- GIMPLE function: void gimple_switch_set_num_labels (gswitch *g, unsigned nlabels) ! Set `NLABELS' to be the number of labels for the switch statement ! `G'. -- GIMPLE function: tree gimple_switch_index (const gswitch *g) ! Return the index variable used by the switch statement `G'. -- GIMPLE function: void gimple_switch_set_index (gswitch *g, tree index) ! Set `INDEX' to be the index variable for switch statement `G'. -- GIMPLE function: tree gimple_switch_label (const gswitch *g, unsigned index) ! Return the label numbered `INDEX'. The default label is 0, followed ! by any labels in a switch statement. -- GIMPLE function: void gimple_switch_set_label (gswitch *g, unsigned index, tree label) ! Set the label number `INDEX' to `LABEL'. 0 is always the default label. -- GIMPLE function: tree gimple_switch_default_label ( const gswitch *************** File: gccint.info, Node: GIMPLE_SWITCH, *** 12618,12688 **** Set the default label for a switch statement.  ! File: gccint.info, Node: GIMPLE_TRY, Next: GIMPLE_WITH_CLEANUP_EXPR, Prev: GIMPLE_SWITCH, Up: Tuple specific accessors ! 11.8.28 'GIMPLE_TRY' -------------------- ! -- GIMPLE function: gtry *gimple_build_try (gimple_seq eval, gimple_seq ! cleanup, unsigned int kind) ! Build a 'GIMPLE_TRY' statement. 'EVAL' is a sequence with the ! expression to evaluate. 'CLEANUP' is a sequence of statements to ! run at clean-up time. 'KIND' is the enumeration value ! 'GIMPLE_TRY_CATCH' if this statement denotes a try/catch construct ! or 'GIMPLE_TRY_FINALLY' if this statement denotes a try/finally construct. -- GIMPLE function: enum gimple_try_flags gimple_try_kind (gimple g) ! Return the kind of try block represented by 'GIMPLE_TRY' 'G'. This ! is either 'GIMPLE_TRY_CATCH' or 'GIMPLE_TRY_FINALLY'. -- GIMPLE function: bool gimple_try_catch_is_cleanup (gimple g) ! Return the 'GIMPLE_TRY_CATCH_IS_CLEANUP' flag. -- GIMPLE function: gimple_seq gimple_try_eval (gimple g) ! Return the sequence of statements used as the body for 'GIMPLE_TRY' ! 'G'. -- GIMPLE function: gimple_seq gimple_try_cleanup (gimple g) Return the sequence of statements used as the cleanup body for ! 'GIMPLE_TRY' 'G'. -- GIMPLE function: void gimple_try_set_catch_is_cleanup (gimple g, bool catch_is_cleanup) ! Set the 'GIMPLE_TRY_CATCH_IS_CLEANUP' flag. -- GIMPLE function: void gimple_try_set_eval (gtry *g, gimple_seq eval) ! Set 'EVAL' to be the sequence of statements to use as the body for ! 'GIMPLE_TRY' 'G'. -- GIMPLE function: void gimple_try_set_cleanup (gtry *g, gimple_seq cleanup) ! Set 'CLEANUP' to be the sequence of statements to use as the ! cleanup body for 'GIMPLE_TRY' 'G'.  ! File: gccint.info, Node: GIMPLE_WITH_CLEANUP_EXPR, Prev: GIMPLE_TRY, Up: Tuple specific accessors ! 11.8.29 'GIMPLE_WITH_CLEANUP_EXPR' ---------------------------------- -- GIMPLE function: gimple gimple_build_wce (gimple_seq cleanup) ! Build a 'GIMPLE_WITH_CLEANUP_EXPR' statement. 'CLEANUP' is the clean-up expression. -- GIMPLE function: gimple_seq gimple_wce_cleanup (gimple g) ! Return the cleanup sequence for cleanup statement 'G'. -- GIMPLE function: void gimple_wce_set_cleanup (gimple g, gimple_seq cleanup) ! Set 'CLEANUP' to be the cleanup sequence for 'G'. -- GIMPLE function: bool gimple_wce_cleanup_eh_only (gimple g) ! Return the 'CLEANUP_EH_ONLY' flag for a 'WCE' tuple. ! -- GIMPLE function: void gimple_wce_set_cleanup_eh_only (gimple g, bool ! eh_only_p) ! Set the 'CLEANUP_EH_ONLY' flag for a 'WCE' tuple.  File: gccint.info, Node: GIMPLE sequences, Next: Sequence iterators, Prev: Tuple specific accessors, Up: GIMPLE --- 12760,12830 ---- Set the default label for a switch statement.  ! File: gccint.info, Node: `GIMPLE_TRY', Next: `GIMPLE_WITH_CLEANUP_EXPR', Prev: `GIMPLE_SWITCH', Up: Tuple specific accessors ! 11.8.28 `GIMPLE_TRY' -------------------- ! -- GIMPLE function: gtry *gimple_build_try (gimple_seq eval, ! gimple_seq cleanup, unsigned int kind) ! Build a `GIMPLE_TRY' statement. `EVAL' is a sequence with the ! expression to evaluate. `CLEANUP' is a sequence of statements to ! run at clean-up time. `KIND' is the enumeration value ! `GIMPLE_TRY_CATCH' if this statement denotes a try/catch construct ! or `GIMPLE_TRY_FINALLY' if this statement denotes a try/finally construct. -- GIMPLE function: enum gimple_try_flags gimple_try_kind (gimple g) ! Return the kind of try block represented by `GIMPLE_TRY' `G'. This ! is either `GIMPLE_TRY_CATCH' or `GIMPLE_TRY_FINALLY'. -- GIMPLE function: bool gimple_try_catch_is_cleanup (gimple g) ! Return the `GIMPLE_TRY_CATCH_IS_CLEANUP' flag. -- GIMPLE function: gimple_seq gimple_try_eval (gimple g) ! Return the sequence of statements used as the body for `GIMPLE_TRY' ! `G'. -- GIMPLE function: gimple_seq gimple_try_cleanup (gimple g) Return the sequence of statements used as the cleanup body for ! `GIMPLE_TRY' `G'. -- GIMPLE function: void gimple_try_set_catch_is_cleanup (gimple g, bool catch_is_cleanup) ! Set the `GIMPLE_TRY_CATCH_IS_CLEANUP' flag. -- GIMPLE function: void gimple_try_set_eval (gtry *g, gimple_seq eval) ! Set `EVAL' to be the sequence of statements to use as the body for ! `GIMPLE_TRY' `G'. -- GIMPLE function: void gimple_try_set_cleanup (gtry *g, gimple_seq cleanup) ! Set `CLEANUP' to be the sequence of statements to use as the ! cleanup body for `GIMPLE_TRY' `G'.  ! File: gccint.info, Node: `GIMPLE_WITH_CLEANUP_EXPR', Prev: `GIMPLE_TRY', Up: Tuple specific accessors ! 11.8.29 `GIMPLE_WITH_CLEANUP_EXPR' ---------------------------------- -- GIMPLE function: gimple gimple_build_wce (gimple_seq cleanup) ! Build a `GIMPLE_WITH_CLEANUP_EXPR' statement. `CLEANUP' is the clean-up expression. -- GIMPLE function: gimple_seq gimple_wce_cleanup (gimple g) ! Return the cleanup sequence for cleanup statement `G'. -- GIMPLE function: void gimple_wce_set_cleanup (gimple g, gimple_seq cleanup) ! Set `CLEANUP' to be the cleanup sequence for `G'. -- GIMPLE function: bool gimple_wce_cleanup_eh_only (gimple g) ! Return the `CLEANUP_EH_ONLY' flag for a `WCE' tuple. ! -- GIMPLE function: void gimple_wce_set_cleanup_eh_only (gimple g, ! bool eh_only_p) ! Set the `CLEANUP_EH_ONLY' flag for a `WCE' tuple.  File: gccint.info, Node: GIMPLE sequences, Next: Sequence iterators, Prev: Tuple specific accessors, Up: GIMPLE *************** File: gccint.info, Node: GIMPLE sequenc *** 12690,12707 **** 11.9 GIMPLE sequences ===================== ! GIMPLE sequences are the tuple equivalent of 'STATEMENT_LIST''s used in ! 'GENERIC'. They are used to chain statements together, and when used in ! conjunction with sequence iterators, provide a framework for iterating ! through statements. ! GIMPLE sequences are of type struct 'gimple_sequence', but are more commonly passed by reference to functions dealing with sequences. The ! type for a sequence pointer is 'gimple_seq' which is the same as struct ! 'gimple_sequence' *. When declaring a local sequence, you can define a ! local variable of type struct 'gimple_sequence'. When declaring a sequence allocated on the garbage collected heap, use the function ! 'gimple_seq_alloc' documented below. There are convenience functions for iterating through sequences in the section entitled Sequence Iterators. --- 12832,12849 ---- 11.9 GIMPLE sequences ===================== ! GIMPLE sequences are the tuple equivalent of `STATEMENT_LIST''s used in ! `GENERIC'. They are used to chain statements together, and when used ! in conjunction with sequence iterators, provide a framework for ! iterating through statements. ! GIMPLE sequences are of type struct `gimple_sequence', but are more commonly passed by reference to functions dealing with sequences. The ! type for a sequence pointer is `gimple_seq' which is the same as struct ! `gimple_sequence' *. When declaring a local sequence, you can define a ! local variable of type struct `gimple_sequence'. When declaring a sequence allocated on the garbage collected heap, use the function ! `gimple_seq_alloc' documented below. There are convenience functions for iterating through sequences in the section entitled Sequence Iterators. *************** section entitled Sequence Iterators. *** 12710,12749 **** -- GIMPLE function: void gimple_seq_add_stmt (gimple_seq *seq, gimple g) ! Link a gimple statement to the end of the sequence *'SEQ' if 'G' is ! not 'NULL'. If *'SEQ' is 'NULL', allocate a sequence before linking. -- GIMPLE function: void gimple_seq_add_seq (gimple_seq *dest, gimple_seq src) ! Append sequence 'SRC' to the end of sequence *'DEST' if 'SRC' is ! not 'NULL'. If *'DEST' is 'NULL', allocate a new sequence before appending. -- GIMPLE function: gimple_seq gimple_seq_deep_copy (gimple_seq src) ! Perform a deep copy of sequence 'SRC' and return the result. -- GIMPLE function: gimple_seq gimple_seq_reverse (gimple_seq seq) ! Reverse the order of the statements in the sequence 'SEQ'. Return ! 'SEQ'. -- GIMPLE function: gimple gimple_seq_first (gimple_seq s) ! Return the first statement in sequence 'S'. -- GIMPLE function: gimple gimple_seq_last (gimple_seq s) ! Return the last statement in sequence 'S'. -- GIMPLE function: void gimple_seq_set_last (gimple_seq s, gimple last) ! Set the last statement in sequence 'S' to the statement in 'LAST'. -- GIMPLE function: void gimple_seq_set_first (gimple_seq s, gimple first) ! Set the first statement in sequence 'S' to the statement in ! 'FIRST'. -- GIMPLE function: void gimple_seq_init (gimple_seq s) ! Initialize sequence 'S' to an empty sequence. -- GIMPLE function: gimple_seq gimple_seq_alloc (void) Allocate a new sequence in the garbage collected store and return --- 12852,12891 ---- -- GIMPLE function: void gimple_seq_add_stmt (gimple_seq *seq, gimple g) ! Link a gimple statement to the end of the sequence *`SEQ' if `G' is ! not `NULL'. If *`SEQ' is `NULL', allocate a sequence before linking. -- GIMPLE function: void gimple_seq_add_seq (gimple_seq *dest, gimple_seq src) ! Append sequence `SRC' to the end of sequence *`DEST' if `SRC' is ! not `NULL'. If *`DEST' is `NULL', allocate a new sequence before appending. -- GIMPLE function: gimple_seq gimple_seq_deep_copy (gimple_seq src) ! Perform a deep copy of sequence `SRC' and return the result. -- GIMPLE function: gimple_seq gimple_seq_reverse (gimple_seq seq) ! Reverse the order of the statements in the sequence `SEQ'. Return ! `SEQ'. -- GIMPLE function: gimple gimple_seq_first (gimple_seq s) ! Return the first statement in sequence `S'. -- GIMPLE function: gimple gimple_seq_last (gimple_seq s) ! Return the last statement in sequence `S'. -- GIMPLE function: void gimple_seq_set_last (gimple_seq s, gimple last) ! Set the last statement in sequence `S' to the statement in `LAST'. -- GIMPLE function: void gimple_seq_set_first (gimple_seq s, gimple first) ! Set the first statement in sequence `S' to the statement in ! `FIRST'. -- GIMPLE function: void gimple_seq_init (gimple_seq s) ! Initialize sequence `S' to an empty sequence. -- GIMPLE function: gimple_seq gimple_seq_alloc (void) Allocate a new sequence in the garbage collected store and return *************** section entitled Sequence Iterators. *** 12751,12769 **** -- GIMPLE function: void gimple_seq_copy (gimple_seq dest, gimple_seq src) ! Copy the sequence 'SRC' into the sequence 'DEST'. -- GIMPLE function: bool gimple_seq_empty_p (gimple_seq s) ! Return true if the sequence 'S' is empty. -- GIMPLE function: gimple_seq bb_seq (basic_block bb) ! Returns the sequence of statements in 'BB'. -- GIMPLE function: void set_bb_seq (basic_block bb, gimple_seq seq) ! Sets the sequence of statements in 'BB' to 'SEQ'. -- GIMPLE function: bool gimple_seq_singleton_p (gimple_seq seq) ! Determine whether 'SEQ' contains exactly one statement.  File: gccint.info, Node: Sequence iterators, Next: Adding a new GIMPLE statement code, Prev: GIMPLE sequences, Up: GIMPLE --- 12893,12911 ---- -- GIMPLE function: void gimple_seq_copy (gimple_seq dest, gimple_seq src) ! Copy the sequence `SRC' into the sequence `DEST'. -- GIMPLE function: bool gimple_seq_empty_p (gimple_seq s) ! Return true if the sequence `S' is empty. -- GIMPLE function: gimple_seq bb_seq (basic_block bb) ! Returns the sequence of statements in `BB'. -- GIMPLE function: void set_bb_seq (basic_block bb, gimple_seq seq) ! Sets the sequence of statements in `BB' to `SEQ'. -- GIMPLE function: bool gimple_seq_singleton_p (gimple_seq seq) ! Determine whether `SEQ' contains exactly one statement.  File: gccint.info, Node: Sequence iterators, Next: Adding a new GIMPLE statement code, Prev: GIMPLE sequences, Up: GIMPLE *************** File: gccint.info, Node: Sequence itera *** 12772,12786 **** ======================== Sequence iterators are convenience constructs for iterating through ! statements in a sequence. Given a sequence 'SEQ', here is a typical use ! of gimple sequence iterators: gimple_stmt_iterator gsi; for (gsi = gsi_start (seq); !gsi_end_p (gsi); gsi_next (&gsi)) { gimple g = gsi_stmt (gsi); ! /* Do something with gimple statement G. */ } Backward iterations are possible: --- 12914,12928 ---- ======================== Sequence iterators are convenience constructs for iterating through ! statements in a sequence. Given a sequence `SEQ', here is a typical ! use of gimple sequence iterators: gimple_stmt_iterator gsi; for (gsi = gsi_start (seq); !gsi_end_p (gsi); gsi_next (&gsi)) { gimple g = gsi_stmt (gsi); ! /* Do something with gimple statement `G'. */ } Backward iterations are possible: *************** of gimple sequence iterators: *** 12788,12834 **** for (gsi = gsi_last (seq); !gsi_end_p (gsi); gsi_prev (&gsi)) Forward and backward iterations on basic blocks are possible with ! 'gsi_start_bb' and 'gsi_last_bb'. In the documentation below we sometimes refer to enum ! 'gsi_iterator_update'. The valid options for this enumeration are: ! * 'GSI_NEW_STMT' Only valid when a single statement is added. Move the iterator to it. ! * 'GSI_SAME_STMT' Leave the iterator at the same statement. ! * 'GSI_CONTINUE_LINKING' Move iterator to whatever position is suitable for linking other statements in the same direction. Below is a list of the functions used to manipulate and use statement iterators. -- GIMPLE function: gimple_stmt_iterator gsi_start (gimple_seq seq) ! Return a new iterator pointing to the sequence 'SEQ''s first ! statement. If 'SEQ' is empty, the iterator's basic block is ! 'NULL'. Use 'gsi_start_bb' instead when the iterator needs to always have the correct basic block set. -- GIMPLE function: gimple_stmt_iterator gsi_start_bb (basic_block bb) Return a new iterator pointing to the first statement in basic ! block 'BB'. -- GIMPLE function: gimple_stmt_iterator gsi_last (gimple_seq seq) Return a new iterator initially pointing to the last statement of ! sequence 'SEQ'. If 'SEQ' is empty, the iterator's basic block is ! 'NULL'. Use 'gsi_last_bb' instead when the iterator needs to always have the correct basic block set. -- GIMPLE function: gimple_stmt_iterator gsi_last_bb (basic_block bb) ! Return a new iterator pointing to the last statement in basic block ! 'BB'. -- GIMPLE function: bool gsi_end_p (gimple_stmt_iterator i) ! Return 'TRUE' if at the end of 'I'. -- GIMPLE function: bool gsi_one_before_end_p (gimple_stmt_iterator i) ! Return 'TRUE' if we're one statement before the end of 'I'. -- GIMPLE function: void gsi_next (gimple_stmt_iterator *i) Advance the iterator to the next gimple statement. --- 12930,12976 ---- for (gsi = gsi_last (seq); !gsi_end_p (gsi); gsi_prev (&gsi)) Forward and backward iterations on basic blocks are possible with ! `gsi_start_bb' and `gsi_last_bb'. In the documentation below we sometimes refer to enum ! `gsi_iterator_update'. The valid options for this enumeration are: ! * `GSI_NEW_STMT' Only valid when a single statement is added. Move the iterator to it. ! * `GSI_SAME_STMT' Leave the iterator at the same statement. ! * `GSI_CONTINUE_LINKING' Move iterator to whatever position is suitable for linking other statements in the same direction. Below is a list of the functions used to manipulate and use statement iterators. -- GIMPLE function: gimple_stmt_iterator gsi_start (gimple_seq seq) ! Return a new iterator pointing to the sequence `SEQ''s first ! statement. If `SEQ' is empty, the iterator's basic block is ! `NULL'. Use `gsi_start_bb' instead when the iterator needs to always have the correct basic block set. -- GIMPLE function: gimple_stmt_iterator gsi_start_bb (basic_block bb) Return a new iterator pointing to the first statement in basic ! block `BB'. -- GIMPLE function: gimple_stmt_iterator gsi_last (gimple_seq seq) Return a new iterator initially pointing to the last statement of ! sequence `SEQ'. If `SEQ' is empty, the iterator's basic block is ! `NULL'. Use `gsi_last_bb' instead when the iterator needs to always have the correct basic block set. -- GIMPLE function: gimple_stmt_iterator gsi_last_bb (basic_block bb) ! Return a new iterator pointing to the last statement in basic ! block `BB'. -- GIMPLE function: bool gsi_end_p (gimple_stmt_iterator i) ! Return `TRUE' if at the end of `I'. -- GIMPLE function: bool gsi_one_before_end_p (gimple_stmt_iterator i) ! Return `TRUE' if we're one statement before the end of `I'. -- GIMPLE function: void gsi_next (gimple_stmt_iterator *i) Advance the iterator to the next gimple statement. *************** iterators. *** 12842,12848 **** -- GIMPLE function: gimple_stmt_iterator gsi_after_labels (basic_block bb) Return a block statement iterator that points to the first ! non-label statement in block 'BB'. -- GIMPLE function: gimple * gsi_stmt_ptr (gimple_stmt_iterator *i) Return a pointer to the current stmt. --- 12984,12990 ---- -- GIMPLE function: gimple_stmt_iterator gsi_after_labels (basic_block bb) Return a block statement iterator that points to the first ! non-label statement in block `BB'. -- GIMPLE function: gimple * gsi_stmt_ptr (gimple_stmt_iterator *i) Return a pointer to the current stmt. *************** iterators. *** 12855,12962 **** -- GIMPLE function: void gsi_remove (gimple_stmt_iterator *i, bool remove_eh_info) ! Remove the current stmt from the sequence. The iterator is updated ! to point to the next statement. When 'REMOVE_EH_INFO' is true we ! remove the statement pointed to by iterator 'I' from the 'EH' ! tables. Otherwise we do not modify the 'EH' tables. Generally, ! 'REMOVE_EH_INFO' should be true when the statement is going to be ! removed from the 'IL' and not reinserted elsewhere. -- GIMPLE function: void gsi_link_seq_before (gimple_stmt_iterator *i, gimple_seq seq, enum gsi_iterator_update mode) ! Links the sequence of statements 'SEQ' before the statement pointed ! by iterator 'I'. 'MODE' indicates what to do with the iterator ! after insertion (see 'enum gsi_iterator_update' above). -- GIMPLE function: void gsi_link_before (gimple_stmt_iterator *i, gimple g, enum gsi_iterator_update mode) ! Links statement 'G' before the statement pointed-to by iterator ! 'I'. Updates iterator 'I' according to 'MODE'. -- GIMPLE function: void gsi_link_seq_after (gimple_stmt_iterator *i, gimple_seq seq, enum gsi_iterator_update mode) ! Links sequence 'SEQ' after the statement pointed-to by iterator ! 'I'. 'MODE' is as in 'gsi_insert_after'. -- GIMPLE function: void gsi_link_after (gimple_stmt_iterator *i, gimple g, enum gsi_iterator_update mode) ! Links statement 'G' after the statement pointed-to by iterator 'I'. ! 'MODE' is as in 'gsi_insert_after'. -- GIMPLE function: gimple_seq gsi_split_seq_after (gimple_stmt_iterator i) ! Move all statements in the sequence after 'I' to a new sequence. Return this new sequence. -- GIMPLE function: gimple_seq gsi_split_seq_before (gimple_stmt_iterator *i) ! Move all statements in the sequence before 'I' to a new sequence. Return this new sequence. -- GIMPLE function: void gsi_replace (gimple_stmt_iterator *i, gimple stmt, bool update_eh_info) ! Replace the statement pointed-to by 'I' to 'STMT'. If ! 'UPDATE_EH_INFO' is true, the exception handling information of the ! original statement is moved to the new statement. -- GIMPLE function: void gsi_insert_before (gimple_stmt_iterator *i, gimple stmt, enum gsi_iterator_update mode) ! Insert statement 'STMT' before the statement pointed-to by iterator ! 'I', update 'STMT''s basic block and scan it for new operands. ! 'MODE' specifies how to update iterator 'I' after insertion (see ! enum 'gsi_iterator_update'). -- GIMPLE function: void gsi_insert_seq_before (gimple_stmt_iterator *i, gimple_seq seq, enum gsi_iterator_update mode) ! Like 'gsi_insert_before', but for all the statements in 'SEQ'. -- GIMPLE function: void gsi_insert_after (gimple_stmt_iterator *i, gimple stmt, enum gsi_iterator_update mode) ! Insert statement 'STMT' after the statement pointed-to by iterator ! 'I', update 'STMT''s basic block and scan it for new operands. ! 'MODE' specifies how to update iterator 'I' after insertion (see ! enum 'gsi_iterator_update'). ! -- GIMPLE function: void gsi_insert_seq_after (gimple_stmt_iterator *i, ! gimple_seq seq, enum gsi_iterator_update mode) ! Like 'gsi_insert_after', but for all the statements in 'SEQ'. -- GIMPLE function: gimple_stmt_iterator gsi_for_stmt (gimple stmt) ! Finds iterator for 'STMT'. -- GIMPLE function: void gsi_move_after (gimple_stmt_iterator *from, gimple_stmt_iterator *to) ! Move the statement at 'FROM' so it comes right after the statement ! at 'TO'. -- GIMPLE function: void gsi_move_before (gimple_stmt_iterator *from, gimple_stmt_iterator *to) ! Move the statement at 'FROM' so it comes right before the statement ! at 'TO'. -- GIMPLE function: void gsi_move_to_bb_end (gimple_stmt_iterator *from, basic_block bb) ! Move the statement at 'FROM' to the end of basic block 'BB'. -- GIMPLE function: void gsi_insert_on_edge (edge e, gimple stmt) ! Add 'STMT' to the pending list of edge 'E'. No actual insertion is ! made until a call to 'gsi_commit_edge_inserts'() is made. -- GIMPLE function: void gsi_insert_seq_on_edge (edge e, gimple_seq seq) ! Add the sequence of statements in 'SEQ' to the pending list of edge ! 'E'. No actual insertion is made until a call to ! 'gsi_commit_edge_inserts'() is made. -- GIMPLE function: basic_block gsi_insert_on_edge_immediate (edge e, gimple stmt) ! Similar to 'gsi_insert_on_edge'+'gsi_commit_edge_inserts'. If a new block has to be created, it is returned. -- GIMPLE function: void gsi_commit_one_edge_insert (edge e, basic_block *new_bb) ! Commit insertions pending at edge 'E'. If a new block is created, ! set 'NEW_BB' to this block, otherwise set it to 'NULL'. -- GIMPLE function: void gsi_commit_edge_inserts (void) This routine will commit all pending edge insertions, creating any --- 12997,13104 ---- -- GIMPLE function: void gsi_remove (gimple_stmt_iterator *i, bool remove_eh_info) ! Remove the current stmt from the sequence. The iterator is ! updated to point to the next statement. When `REMOVE_EH_INFO' is ! true we remove the statement pointed to by iterator `I' from the ! `EH' tables. Otherwise we do not modify the `EH' tables. ! Generally, `REMOVE_EH_INFO' should be true when the statement is ! going to be removed from the `IL' and not reinserted elsewhere. -- GIMPLE function: void gsi_link_seq_before (gimple_stmt_iterator *i, gimple_seq seq, enum gsi_iterator_update mode) ! Links the sequence of statements `SEQ' before the statement pointed ! by iterator `I'. `MODE' indicates what to do with the iterator ! after insertion (see `enum gsi_iterator_update' above). -- GIMPLE function: void gsi_link_before (gimple_stmt_iterator *i, gimple g, enum gsi_iterator_update mode) ! Links statement `G' before the statement pointed-to by iterator ! `I'. Updates iterator `I' according to `MODE'. -- GIMPLE function: void gsi_link_seq_after (gimple_stmt_iterator *i, gimple_seq seq, enum gsi_iterator_update mode) ! Links sequence `SEQ' after the statement pointed-to by iterator ! `I'. `MODE' is as in `gsi_insert_after'. -- GIMPLE function: void gsi_link_after (gimple_stmt_iterator *i, gimple g, enum gsi_iterator_update mode) ! Links statement `G' after the statement pointed-to by iterator `I'. ! `MODE' is as in `gsi_insert_after'. -- GIMPLE function: gimple_seq gsi_split_seq_after (gimple_stmt_iterator i) ! Move all statements in the sequence after `I' to a new sequence. Return this new sequence. -- GIMPLE function: gimple_seq gsi_split_seq_before (gimple_stmt_iterator *i) ! Move all statements in the sequence before `I' to a new sequence. Return this new sequence. -- GIMPLE function: void gsi_replace (gimple_stmt_iterator *i, gimple stmt, bool update_eh_info) ! Replace the statement pointed-to by `I' to `STMT'. If ! `UPDATE_EH_INFO' is true, the exception handling information of ! the original statement is moved to the new statement. -- GIMPLE function: void gsi_insert_before (gimple_stmt_iterator *i, gimple stmt, enum gsi_iterator_update mode) ! Insert statement `STMT' before the statement pointed-to by iterator ! `I', update `STMT''s basic block and scan it for new operands. ! `MODE' specifies how to update iterator `I' after insertion (see ! enum `gsi_iterator_update'). -- GIMPLE function: void gsi_insert_seq_before (gimple_stmt_iterator *i, gimple_seq seq, enum gsi_iterator_update mode) ! Like `gsi_insert_before', but for all the statements in `SEQ'. -- GIMPLE function: void gsi_insert_after (gimple_stmt_iterator *i, gimple stmt, enum gsi_iterator_update mode) ! Insert statement `STMT' after the statement pointed-to by iterator ! `I', update `STMT''s basic block and scan it for new operands. ! `MODE' specifies how to update iterator `I' after insertion (see ! enum `gsi_iterator_update'). ! -- GIMPLE function: void gsi_insert_seq_after (gimple_stmt_iterator ! *i, gimple_seq seq, enum gsi_iterator_update mode) ! Like `gsi_insert_after', but for all the statements in `SEQ'. -- GIMPLE function: gimple_stmt_iterator gsi_for_stmt (gimple stmt) ! Finds iterator for `STMT'. -- GIMPLE function: void gsi_move_after (gimple_stmt_iterator *from, gimple_stmt_iterator *to) ! Move the statement at `FROM' so it comes right after the statement ! at `TO'. -- GIMPLE function: void gsi_move_before (gimple_stmt_iterator *from, gimple_stmt_iterator *to) ! Move the statement at `FROM' so it comes right before the statement ! at `TO'. -- GIMPLE function: void gsi_move_to_bb_end (gimple_stmt_iterator *from, basic_block bb) ! Move the statement at `FROM' to the end of basic block `BB'. -- GIMPLE function: void gsi_insert_on_edge (edge e, gimple stmt) ! Add `STMT' to the pending list of edge `E'. No actual insertion is ! made until a call to `gsi_commit_edge_inserts'() is made. -- GIMPLE function: void gsi_insert_seq_on_edge (edge e, gimple_seq seq) ! Add the sequence of statements in `SEQ' to the pending list of edge ! `E'. No actual insertion is made until a call to ! `gsi_commit_edge_inserts'() is made. -- GIMPLE function: basic_block gsi_insert_on_edge_immediate (edge e, gimple stmt) ! Similar to `gsi_insert_on_edge'+`gsi_commit_edge_inserts'. If a new block has to be created, it is returned. -- GIMPLE function: void gsi_commit_one_edge_insert (edge e, basic_block *new_bb) ! Commit insertions pending at edge `E'. If a new block is created, ! set `NEW_BB' to this block, otherwise set it to `NULL'. -- GIMPLE function: void gsi_commit_edge_inserts (void) This routine will commit all pending edge insertions, creating any *************** File: gccint.info, Node: Adding a new G *** 12969,12995 **** ======================================== The first step in adding a new GIMPLE statement code, is modifying the ! file 'gimple.def', which contains all the GIMPLE codes. Then you must ! add a corresponding gimple subclass located in 'gimple.h'. This in ! turn, will require you to add a corresponding 'GTY' tag in ! 'gsstruct.def', and code to handle this tag in 'gss_for_code' which is ! located in 'gimple.c'. In order for the garbage collector to know the size of the structure ! you created in 'gimple.h', you need to add a case to handle your new ! GIMPLE statement in 'gimple_size' which is located in 'gimple.c'. You will probably want to create a function to build the new gimple ! statement in 'gimple.c'. The function should be called ! 'gimple_build_NEW-TUPLE-NAME', and should return the new tuple as a pointer to the appropriate gimple subclass. ! If your new statement requires accessors for any members or operands it ! may have, put simple inline accessors in 'gimple.h' and any non-trivial ! accessors in 'gimple.c' with a corresponding prototype in 'gimple.h'. You should add the new statement subclass to the class hierarchy ! diagram in 'gimple.texi'.  File: gccint.info, Node: Statement and operand traversals, Prev: Adding a new GIMPLE statement code, Up: GIMPLE --- 13111,13138 ---- ======================================== The first step in adding a new GIMPLE statement code, is modifying the ! file `gimple.def', which contains all the GIMPLE codes. Then you must ! add a corresponding gimple subclass located in `gimple.h'. This in ! turn, will require you to add a corresponding `GTY' tag in ! `gsstruct.def', and code to handle this tag in `gss_for_code' which is ! located in `gimple.c'. In order for the garbage collector to know the size of the structure ! you created in `gimple.h', you need to add a case to handle your new ! GIMPLE statement in `gimple_size' which is located in `gimple.c'. You will probably want to create a function to build the new gimple ! statement in `gimple.c'. The function should be called ! `gimple_build_NEW-TUPLE-NAME', and should return the new tuple as a pointer to the appropriate gimple subclass. ! If your new statement requires accessors for any members or operands ! it may have, put simple inline accessors in `gimple.h' and any ! non-trivial accessors in `gimple.c' with a corresponding prototype in ! `gimple.h'. You should add the new statement subclass to the class hierarchy ! diagram in `gimple.texi'.  File: gccint.info, Node: Statement and operand traversals, Prev: Adding a new GIMPLE statement code, Up: GIMPLE *************** File: gccint.info, Node: Statement and *** 12998,13051 **** ====================================== There are two functions available for walking statements and sequences: ! 'walk_gimple_stmt' and 'walk_gimple_seq', accordingly, and a third ! function for walking the operands in a statement: 'walk_gimple_op'. -- GIMPLE function: tree walk_gimple_stmt (gimple_stmt_iterator *gsi, walk_stmt_fn callback_stmt, walk_tree_fn callback_op, struct walk_stmt_info *wi) ! This function is used to walk the current statement in 'GSI', ! optionally using traversal state stored in 'WI'. If 'WI' is ! 'NULL', no state is kept during the traversal. ! The callback 'CALLBACK_STMT' is called. If 'CALLBACK_STMT' returns true, it means that the callback function has handled all the operands of the statement and it is not necessary to walk its operands. ! If 'CALLBACK_STMT' is 'NULL' or it returns false, 'CALLBACK_OP' is ! called on each operand of the statement via 'walk_gimple_op'. If ! 'walk_gimple_op' returns non-'NULL' for any operand, the remaining operands are not scanned. The return value is that returned by the last call to ! 'walk_gimple_op', or 'NULL_TREE' if no 'CALLBACK_OP' is specified. -- GIMPLE function: tree walk_gimple_op (gimple stmt, walk_tree_fn callback_op, struct walk_stmt_info *wi) ! Use this function to walk the operands of statement 'STMT'. Every ! operand is walked via 'walk_tree' with optional state information ! in 'WI'. ! 'CALLBACK_OP' is called on each operand of 'STMT' via 'walk_tree'. ! Additional parameters to 'walk_tree' must be stored in 'WI'. For ! each operand 'OP', 'walk_tree' is called as: ! walk_tree (&OP, CALLBACK_OP, WI, PSET) ! If 'CALLBACK_OP' returns non-'NULL' for an operand, the remaining ! operands are not scanned. The return value is that returned by the ! last call to 'walk_tree', or 'NULL_TREE' if no 'CALLBACK_OP' is specified. -- GIMPLE function: tree walk_gimple_seq (gimple_seq seq, walk_stmt_fn ! callback_stmt, walk_tree_fn callback_op, struct walk_stmt_info ! *wi) ! This function walks all the statements in the sequence 'SEQ' ! calling 'walk_gimple_stmt' on each one. 'WI' is as in ! 'walk_gimple_stmt'. If 'walk_gimple_stmt' returns non-'NULL', the walk is stopped and the value returned. Otherwise, all the ! statements are walked and 'NULL_TREE' returned.  File: gccint.info, Node: Tree SSA, Next: RTL, Prev: GIMPLE, Up: Top --- 13141,13194 ---- ====================================== There are two functions available for walking statements and sequences: ! `walk_gimple_stmt' and `walk_gimple_seq', accordingly, and a third ! function for walking the operands in a statement: `walk_gimple_op'. -- GIMPLE function: tree walk_gimple_stmt (gimple_stmt_iterator *gsi, walk_stmt_fn callback_stmt, walk_tree_fn callback_op, struct walk_stmt_info *wi) ! This function is used to walk the current statement in `GSI', ! optionally using traversal state stored in `WI'. If `WI' is ! `NULL', no state is kept during the traversal. ! The callback `CALLBACK_STMT' is called. If `CALLBACK_STMT' returns true, it means that the callback function has handled all the operands of the statement and it is not necessary to walk its operands. ! If `CALLBACK_STMT' is `NULL' or it returns false, `CALLBACK_OP' is ! called on each operand of the statement via `walk_gimple_op'. If ! `walk_gimple_op' returns non-`NULL' for any operand, the remaining operands are not scanned. The return value is that returned by the last call to ! `walk_gimple_op', or `NULL_TREE' if no `CALLBACK_OP' is specified. -- GIMPLE function: tree walk_gimple_op (gimple stmt, walk_tree_fn callback_op, struct walk_stmt_info *wi) ! Use this function to walk the operands of statement `STMT'. Every ! operand is walked via `walk_tree' with optional state information ! in `WI'. ! `CALLBACK_OP' is called on each operand of `STMT' via `walk_tree'. ! Additional parameters to `walk_tree' must be stored in `WI'. For ! each operand `OP', `walk_tree' is called as: ! walk_tree (&`OP', `CALLBACK_OP', `WI', `PSET') ! If `CALLBACK_OP' returns non-`NULL' for an operand, the remaining ! operands are not scanned. The return value is that returned by ! the last call to `walk_tree', or `NULL_TREE' if no `CALLBACK_OP' is specified. -- GIMPLE function: tree walk_gimple_seq (gimple_seq seq, walk_stmt_fn ! callback_stmt, walk_tree_fn callback_op, struct ! walk_stmt_info *wi) ! This function walks all the statements in the sequence `SEQ' ! calling `walk_gimple_stmt' on each one. `WI' is as in ! `walk_gimple_stmt'. If `walk_gimple_stmt' returns non-`NULL', the walk is stopped and the value returned. Otherwise, all the ! statements are walked and `NULL_TREE' returned.  File: gccint.info, Node: Tree SSA, Next: RTL, Prev: GIMPLE, Up: Top *************** File: gccint.info, Node: Tree SSA, Nex *** 13056,13080 **** GCC uses three main intermediate languages to represent the program during compilation: GENERIC, GIMPLE and RTL. GENERIC is a language-independent representation generated by each front end. It is ! used to serve as an interface between the parser and optimizer. GENERIC ! is a common representation that is able to represent programs written in ! all the languages supported by GCC. GIMPLE and RTL are used to optimize the program. GIMPLE is used for target and language independent optimizations (e.g., inlining, constant propagation, tail call elimination, redundancy elimination, etc). Much like GENERIC, GIMPLE is a language independent, tree based representation. However, it differs from GENERIC in that the GIMPLE ! grammar is more restrictive: expressions contain no more than 3 operands ! (except function calls), it has no control flow structures and ! expressions with side-effects are only allowed on the right hand side of ! assignments. See the chapter describing GENERIC and GIMPLE for more details. This chapter describes the data structures and functions used in the ! GIMPLE optimizers (also known as "tree optimizers" or "middle end"). In ! particular, it focuses on all the macros, data structures, functions and ! programming constructs needed to implement optimization passes for GIMPLE. * Menu: --- 13199,13223 ---- GCC uses three main intermediate languages to represent the program during compilation: GENERIC, GIMPLE and RTL. GENERIC is a language-independent representation generated by each front end. It is ! used to serve as an interface between the parser and optimizer. ! GENERIC is a common representation that is able to represent programs ! written in all the languages supported by GCC. GIMPLE and RTL are used to optimize the program. GIMPLE is used for target and language independent optimizations (e.g., inlining, constant propagation, tail call elimination, redundancy elimination, etc). Much like GENERIC, GIMPLE is a language independent, tree based representation. However, it differs from GENERIC in that the GIMPLE ! grammar is more restrictive: expressions contain no more than 3 ! operands (except function calls), it has no control flow structures and ! expressions with side-effects are only allowed on the right hand side ! of assignments. See the chapter describing GENERIC and GIMPLE for more details. This chapter describes the data structures and functions used in the ! GIMPLE optimizers (also known as "tree optimizers" or "middle end"). ! In particular, it focuses on all the macros, data structures, functions ! and programming constructs needed to implement optimization passes for GIMPLE. * Menu: *************** File: gccint.info, Node: Annotations, *** 13094,13100 **** The optimizers need to associate attributes with variables during the optimization process. For instance, we need to know whether a variable has aliases. All these attributes are stored in data structures called ! annotations which are then linked to the field 'ann' in 'struct tree_common'.  --- 13237,13243 ---- The optimizers need to associate attributes with variables during the optimization process. For instance, we need to know whether a variable has aliases. All these attributes are stored in data structures called ! annotations which are then linked to the field `ann' in `struct tree_common'.  *************** their operands are going to be located a *** 13109,13150 **** statement's tree. To facilitate access to the statement's operands, they are organized into lists associated inside each statement's annotation. Each element in an operand list is a pointer to a ! 'VAR_DECL', 'PARM_DECL' or 'SSA_NAME' tree node. This provides a very convenient way of examining and replacing operands. Data flow analysis and optimization is done on all tree nodes ! representing variables. Any node for which 'SSA_VAR_P' returns nonzero is considered when scanning statement operands. However, not all ! 'SSA_VAR_P' variables are processed in the same way. For the purposes of optimization, we need to distinguish between references to local ! scalar variables and references to globals, statics, structures, arrays, ! aliased variables, etc. The reason is simple, the compiler can gather ! complete data flow information for a local scalar. On the other hand, a ! global variable may be modified by a function call, it may not be ! possible to keep track of all the elements of an array or the fields of ! a structure, etc. The operand scanner gathers two kinds of operands: "real" and ! "virtual". An operand for which 'is_gimple_reg' returns true is ! considered real, otherwise it is a virtual operand. We also distinguish ! between uses and definitions. An operand is used if its value is loaded ! by the statement (e.g., the operand at the RHS of an assignment). If ! the statement assigns a new value to the operand, the operand is ! considered a definition (e.g., the operand at the LHS of an assignment). Virtual and real operands also have very different data flow ! properties. Real operands are unambiguous references to the full object ! that they represent. For instance, given { int a, b; a = b } ! Since 'a' and 'b' are non-aliased locals, the statement 'a = b' will ! have one real definition and one real use because variable 'a' is ! completely modified with the contents of variable 'b'. Real definition ! are also known as "killing definitions". Similarly, the use of 'b' reads all its bits. In contrast, virtual operands are used with variables that can have a --- 13252,13294 ---- statement's tree. To facilitate access to the statement's operands, they are organized into lists associated inside each statement's annotation. Each element in an operand list is a pointer to a ! `VAR_DECL', `PARM_DECL' or `SSA_NAME' tree node. This provides a very convenient way of examining and replacing operands. Data flow analysis and optimization is done on all tree nodes ! representing variables. Any node for which `SSA_VAR_P' returns nonzero is considered when scanning statement operands. However, not all ! `SSA_VAR_P' variables are processed in the same way. For the purposes of optimization, we need to distinguish between references to local ! scalar variables and references to globals, statics, structures, ! arrays, aliased variables, etc. The reason is simple, the compiler can ! gather complete data flow information for a local scalar. On the other ! hand, a global variable may be modified by a function call, it may not ! be possible to keep track of all the elements of an array or the fields ! of a structure, etc. The operand scanner gathers two kinds of operands: "real" and ! "virtual". An operand for which `is_gimple_reg' returns true is ! considered real, otherwise it is a virtual operand. We also ! distinguish between uses and definitions. An operand is used if its ! value is loaded by the statement (e.g., the operand at the RHS of an ! assignment). If the statement assigns a new value to the operand, the ! operand is considered a definition (e.g., the operand at the LHS of an ! assignment). Virtual and real operands also have very different data flow ! properties. Real operands are unambiguous references to the full ! object that they represent. For instance, given { int a, b; a = b } ! Since `a' and `b' are non-aliased locals, the statement `a = b' will ! have one real definition and one real use because variable `a' is ! completely modified with the contents of variable `b'. Real definition ! are also known as "killing definitions". Similarly, the use of `b' reads all its bits. In contrast, virtual operands are used with variables that can have a *************** definitions. For globals, structures, a *** 13154,13163 **** a statement whether a variable of these types has a killing definition. If the variable does, then the statement is marked as having a "must definition" of that variable. However, if a statement is only defining ! a part of the variable (i.e. a field in a structure), or if we know that ! a statement might define the variable but we cannot say for sure, then ! we mark that statement as having a "may definition". For instance, ! given { int a, b, *p; --- 13298,13307 ---- a statement whether a variable of these types has a killing definition. If the variable does, then the statement is marked as having a "must definition" of that variable. However, if a statement is only defining ! a part of the variable (i.e. a field in a structure), or if we know ! that a statement might define the variable but we cannot say for sure, ! then we mark that statement as having a "may definition". For ! instance, given { int a, b, *p; *************** given *** 13170,13182 **** return *p; } ! The assignment '*p = 5' may be a definition of 'a' or 'b'. If we ! cannot determine statically where 'p' is pointing to at the time of the ! store operation, we create virtual definitions to mark that statement as ! a potential definition site for 'a' and 'b'. Memory loads are similarly ! marked with virtual use operands. Virtual operands are shown in tree ! dumps right before the statement that contains them. To request a tree ! dump with virtual operands, use the '-vops' option to '-fdump-tree': { int a, b, *p; --- 13314,13327 ---- return *p; } ! The assignment `*p = 5' may be a definition of `a' or `b'. If we ! cannot determine statically where `p' is pointing to at the time of the ! store operation, we create virtual definitions to mark that statement ! as a potential definition site for `a' and `b'. Memory loads are ! similarly marked with virtual use operands. Virtual operands are shown ! in tree dumps right before the statement that contains them. To ! request a tree dump with virtual operands, use the `-vops' option to ! `-fdump-tree': { int a, b, *p; *************** dump with virtual operands, use the '-vo *** 13194,13247 **** return *p; } ! Notice that 'VDEF' operands have two copies of the referenced variable. ! This indicates that this is not a killing definition of that variable. ! In this case we refer to it as a "may definition" or "aliased store". ! The presence of the second copy of the variable in the 'VDEF' operand ! will become important when the function is converted into SSA form. ! This will be used to link all the non-killing definitions to prevent ! optimizations from making incorrect assumptions about them. ! Operands are updated as soon as the statement is finished via a call to ! 'update_stmt'. If statement elements are changed via 'SET_USE' or ! 'SET_DEF', then no further action is required (i.e., those macros take care of updating the statement). If changes are made by manipulating ! the statement's tree directly, then a call must be made to 'update_stmt' ! when complete. Calling one of the 'bsi_insert' routines or ! 'bsi_replace' performs an implicit call to 'update_stmt'. 12.2.1 Operand Iterators And Access Routines -------------------------------------------- ! Operands are collected by 'tree-ssa-operands.c'. They are stored inside ! each statement's annotation and can be accessed through either the ! operand iterators or an access routine. The following access routines are available for examining operands: ! 1. 'SINGLE_SSA_{USE,DEF,TREE}_OPERAND': These accessors will return NULL unless there is exactly one operand matching the specified ! flags. If there is exactly one operand, the operand is returned as ! either a 'tree', 'def_operand_p', or 'use_operand_p'. tree t = SINGLE_SSA_TREE_OPERAND (stmt, flags); use_operand_p u = SINGLE_SSA_USE_OPERAND (stmt, SSA_ALL_VIRTUAL_USES); def_operand_p d = SINGLE_SSA_DEF_OPERAND (stmt, SSA_OP_ALL_DEFS); ! 2. 'ZERO_SSA_OPERANDS': This macro returns true if there are no operands matching the specified flags. if (ZERO_SSA_OPERANDS (stmt, SSA_OP_ALL_VIRTUALS)) return; ! 3. 'NUM_SSA_OPERANDS': This macro Returns the number of operands matching 'flags'. This actually executes a loop to perform the count, so only use this if it is really needed. int count = NUM_SSA_OPERANDS (stmt, flags) If you wish to iterate over some or all operands, use the ! 'FOR_EACH_SSA_{USE,DEF,TREE}_OPERAND' iterator. For example, to print all the operands for a statement: void --- 13339,13393 ---- return *p; } ! Notice that `VDEF' operands have two copies of the referenced ! variable. This indicates that this is not a killing definition of that ! variable. In this case we refer to it as a "may definition" or ! "aliased store". The presence of the second copy of the variable in ! the `VDEF' operand will become important when the function is converted ! into SSA form. This will be used to link all the non-killing ! definitions to prevent optimizations from making incorrect assumptions ! about them. ! Operands are updated as soon as the statement is finished via a call ! to `update_stmt'. If statement elements are changed via `SET_USE' or ! `SET_DEF', then no further action is required (i.e., those macros take care of updating the statement). If changes are made by manipulating ! the statement's tree directly, then a call must be made to ! `update_stmt' when complete. Calling one of the `bsi_insert' routines ! or `bsi_replace' performs an implicit call to `update_stmt'. 12.2.1 Operand Iterators And Access Routines -------------------------------------------- ! Operands are collected by `tree-ssa-operands.c'. They are stored ! inside each statement's annotation and can be accessed through either ! the operand iterators or an access routine. The following access routines are available for examining operands: ! 1. `SINGLE_SSA_{USE,DEF,TREE}_OPERAND': These accessors will return NULL unless there is exactly one operand matching the specified ! flags. If there is exactly one operand, the operand is returned ! as either a `tree', `def_operand_p', or `use_operand_p'. tree t = SINGLE_SSA_TREE_OPERAND (stmt, flags); use_operand_p u = SINGLE_SSA_USE_OPERAND (stmt, SSA_ALL_VIRTUAL_USES); def_operand_p d = SINGLE_SSA_DEF_OPERAND (stmt, SSA_OP_ALL_DEFS); ! 2. `ZERO_SSA_OPERANDS': This macro returns true if there are no operands matching the specified flags. if (ZERO_SSA_OPERANDS (stmt, SSA_OP_ALL_VIRTUALS)) return; ! 3. `NUM_SSA_OPERANDS': This macro Returns the number of operands matching 'flags'. This actually executes a loop to perform the count, so only use this if it is really needed. int count = NUM_SSA_OPERANDS (stmt, flags) If you wish to iterate over some or all operands, use the ! `FOR_EACH_SSA_{USE,DEF,TREE}_OPERAND' iterator. For example, to print all the operands for a statement: void *************** all the operands for a statement: *** 13256,13263 **** How to choose the appropriate iterator: ! 1. Determine whether you are need to see the operand pointers, or just ! the trees, and choose the appropriate macro: Need Macro: ---- ------- --- 13402,13409 ---- How to choose the appropriate iterator: ! 1. Determine whether you are need to see the operand pointers, or ! just the trees, and choose the appropriate macro: Need Macro: ---- ------- *************** all the operands for a statement: *** 13271,13277 **** 3. Determine which operands you wish to use, and specify the flags of those you are interested in. They are documented in ! 'tree-ssa-operands.h': #define SSA_OP_USE 0x01 /* Real USE operands. */ #define SSA_OP_DEF 0x02 /* Real DEF operands. */ --- 13417,13423 ---- 3. Determine which operands you wish to use, and specify the flags of those you are interested in. They are documented in ! `tree-ssa-operands.h': #define SSA_OP_USE 0x01 /* Real USE operands. */ #define SSA_OP_DEF 0x02 /* Real DEF operands. */ *************** all the operands for a statement: *** 13286,13293 **** #define SSA_OP_ALL_DEFS (SSA_OP_VIRTUAL_DEFS | SSA_OP_DEF) #define SSA_OP_ALL_OPERANDS (SSA_OP_ALL_USES | SSA_OP_ALL_DEFS) ! So if you want to look at the use pointers for all the 'USE' and 'VUSE' ! operands, you would do something like: use_operand_p use_p; ssa_op_iter iter; --- 13432,13439 ---- #define SSA_OP_ALL_DEFS (SSA_OP_VIRTUAL_DEFS | SSA_OP_DEF) #define SSA_OP_ALL_OPERANDS (SSA_OP_ALL_USES | SSA_OP_ALL_DEFS) ! So if you want to look at the use pointers for all the `USE' and ! `VUSE' operands, you would do something like: use_operand_p use_p; ssa_op_iter iter; *************** operands, you would do something like: *** 13297,13306 **** process_use_ptr (use_p); } ! The 'TREE' macro is basically the same as the 'USE' and 'DEF' macros, ! only with the use or def dereferenced via 'USE_FROM_PTR (use_p)' and ! 'DEF_FROM_PTR (def_p)'. Since we aren't using operand pointers, use and ! defs flags can be mixed. tree var; ssa_op_iter iter; --- 13443,13452 ---- process_use_ptr (use_p); } ! The `TREE' macro is basically the same as the `USE' and `DEF' macros, ! only with the use or def dereferenced via `USE_FROM_PTR (use_p)' and ! `DEF_FROM_PTR (def_p)'. Since we aren't using operand pointers, use ! and defs flags can be mixed. tree var; ssa_op_iter iter; *************** defs flags can be mixed. *** 13310,13326 **** print_generic_expr (stderr, var, TDF_SLIM); } ! 'VDEF's are broken into two flags, one for the 'DEF' portion ! ('SSA_OP_VDEF') and one for the USE portion ('SSA_OP_VUSE'). There are many examples in the code, in addition to the documentation ! in 'tree-ssa-operands.h' and 'ssa-iterators.h'. There are also a couple of variants on the stmt iterators regarding PHI nodes. ! 'FOR_EACH_PHI_ARG' Works exactly like 'FOR_EACH_SSA_USE_OPERAND', ! except it works over 'PHI' arguments instead of statement operands. /* Look at every virtual PHI use. */ FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_VIRTUAL_USES) --- 13456,13472 ---- print_generic_expr (stderr, var, TDF_SLIM); } ! `VDEF's are broken into two flags, one for the `DEF' portion ! (`SSA_OP_VDEF') and one for the USE portion (`SSA_OP_VUSE'). There are many examples in the code, in addition to the documentation ! in `tree-ssa-operands.h' and `ssa-iterators.h'. There are also a couple of variants on the stmt iterators regarding PHI nodes. ! `FOR_EACH_PHI_ARG' Works exactly like `FOR_EACH_SSA_USE_OPERAND', ! except it works over `PHI' arguments instead of statement operands. /* Look at every virtual PHI use. */ FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_VIRTUAL_USES) *************** except it works over 'PHI' arguments ins *** 13336,13346 **** FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_ALL_USES) my_code; ! 'FOR_EACH_PHI_OR_STMT_{USE,DEF}' works exactly like ! 'FOR_EACH_SSA_{USE,DEF}_OPERAND', except it will function on either a ! statement or a 'PHI' node. These should be used when it is appropriate ! but they are not quite as efficient as the individual 'FOR_EACH_PHI' and ! 'FOR_EACH_SSA' routines. FOR_EACH_PHI_OR_STMT_USE (use_operand_p, stmt, iter, flags) { --- 13482,13492 ---- FOR_EACH_PHI_ARG (use_p, phi_stmt, iter, SSA_OP_ALL_USES) my_code; ! `FOR_EACH_PHI_OR_STMT_{USE,DEF}' works exactly like ! `FOR_EACH_SSA_{USE,DEF}_OPERAND', except it will function on either a ! statement or a `PHI' node. These should be used when it is appropriate ! but they are not quite as efficient as the individual `FOR_EACH_PHI' ! and `FOR_EACH_SSA' routines. FOR_EACH_PHI_OR_STMT_USE (use_operand_p, stmt, iter, flags) { *************** but they are not quite as efficient as t *** 13356,13363 **** --------------------- Immediate use information is now always available. Using the immediate ! use iterators, you may examine every use of any 'SSA_NAME'. For ! instance, to change each use of 'ssa_var' to 'ssa_var2' and call fold_stmt on each stmt after that is done: use_operand_p imm_use_p; --- 13502,13509 ---- --------------------- Immediate use information is now always available. Using the immediate ! use iterators, you may examine every use of any `SSA_NAME'. For ! instance, to change each use of `ssa_var' to `ssa_var2' and call fold_stmt on each stmt after that is done: use_operand_p imm_use_p; *************** fold_stmt on each stmt after that is don *** 13372,13392 **** fold_stmt (stmt); } ! There are 2 iterators which can be used. 'FOR_EACH_IMM_USE_FAST' is used when the immediate uses are not changed, i.e., you are looking at the uses, but not setting them. If they do get changed, then care must be taken that things are not ! changed under the iterators, so use the 'FOR_EACH_IMM_USE_STMT' and ! 'FOR_EACH_IMM_USE_ON_STMT' iterators. They attempt to preserve the sanity of the use list by moving all the uses for a statement into a controlled position, and then iterating over those uses. Then the optimization can manipulate the stmt when all the uses have been processed. This is a little slower than the FAST version since it adds a placeholder element and must sort through the list a bit for each ! statement. This placeholder element must be also be removed if the loop ! is terminated early. The macro 'BREAK_FROM_IMM_USE_SAFE' is provided to ! do this : FOR_EACH_IMM_USE_STMT (stmt, iterator, ssa_var) { --- 13518,13538 ---- fold_stmt (stmt); } ! There are 2 iterators which can be used. `FOR_EACH_IMM_USE_FAST' is used when the immediate uses are not changed, i.e., you are looking at the uses, but not setting them. If they do get changed, then care must be taken that things are not ! changed under the iterators, so use the `FOR_EACH_IMM_USE_STMT' and ! `FOR_EACH_IMM_USE_ON_STMT' iterators. They attempt to preserve the sanity of the use list by moving all the uses for a statement into a controlled position, and then iterating over those uses. Then the optimization can manipulate the stmt when all the uses have been processed. This is a little slower than the FAST version since it adds a placeholder element and must sort through the list a bit for each ! statement. This placeholder element must be also be removed if the ! loop is terminated early. The macro `BREAK_FROM_IMM_USE_SAFE' is ! provided to do this : FOR_EACH_IMM_USE_STMT (stmt, iterator, ssa_var) { *************** do this : *** 13398,13428 **** fold_stmt (stmt); } ! There are checks in 'verify_ssa' which verify that the immediate use list is up to date, as well as checking that an optimization didn't break from the loop without using this macro. It is safe to simply ! 'break'; from a 'FOR_EACH_IMM_USE_FAST' traverse. Some useful functions and macros: ! 1. 'has_zero_uses (ssa_var)' : Returns true if there are no uses of ! 'ssa_var'. ! 2. 'has_single_use (ssa_var)' : Returns true if there is only a single ! use of 'ssa_var'. ! 3. 'single_imm_use (ssa_var, use_operand_p *ptr, tree *stmt)' : ! Returns true if there is only a single use of 'ssa_var', and also returns the use pointer and statement it occurs in, in the second and third parameters. ! 4. 'num_imm_uses (ssa_var)' : Returns the number of immediate uses of ! 'ssa_var'. It is better not to use this if possible since it ! simply utilizes a loop to count the uses. ! 5. 'PHI_ARG_INDEX_FROM_USE (use_p)' : Given a use within a 'PHI' node, ! return the index number for the use. An assert is triggered if the ! use isn't located in a 'PHI' node. ! 6. 'USE_STMT (use_p)' : Return the statement a use occurs in. Note that uses are not put into an immediate use list until their ! statement is actually inserted into the instruction stream via a 'bsi_*' ! routine. It is also still possible to utilize lazy updating of statements, but this should be used only when absolutely required. Both alias analysis --- 13544,13579 ---- fold_stmt (stmt); } ! There are checks in `verify_ssa' which verify that the immediate use list is up to date, as well as checking that an optimization didn't break from the loop without using this macro. It is safe to simply ! 'break'; from a `FOR_EACH_IMM_USE_FAST' traverse. Some useful functions and macros: ! 1. `has_zero_uses (ssa_var)' : Returns true if there are no uses of ! `ssa_var'. ! ! 2. `has_single_use (ssa_var)' : Returns true if there is only a ! single use of `ssa_var'. ! ! 3. `single_imm_use (ssa_var, use_operand_p *ptr, tree *stmt)' : ! Returns true if there is only a single use of `ssa_var', and also returns the use pointer and statement it occurs in, in the second and third parameters. ! ! 4. `num_imm_uses (ssa_var)' : Returns the number of immediate uses of ! `ssa_var'. It is better not to use this if possible since it simply ! utilizes a loop to count the uses. ! ! 5. `PHI_ARG_INDEX_FROM_USE (use_p)' : Given a use within a `PHI' ! node, return the index number for the use. An assert is triggered ! if the use isn't located in a `PHI' node. ! ! 6. `USE_STMT (use_p)' : Return the statement a use occurs in. Note that uses are not put into an immediate use list until their ! statement is actually inserted into the instruction stream via a ! `bsi_*' routine. It is also still possible to utilize lazy updating of statements, but this should be used only when absolutely required. Both alias analysis *************** and the dominator optimizations currentl *** 13430,13440 **** When lazy updating is being used, the immediate use information is out of date and cannot be used reliably. Lazy updating is achieved by ! simply marking statements modified via calls to 'gimple_set_modified' ! instead of 'update_stmt'. When lazy updating is no longer required, all ! the modified statements must have 'update_stmt' called in order to bring ! them up to date. This must be done before the optimization is finished, ! or 'verify_ssa' will trigger an abort. This is done with a simple loop over the instruction stream: block_stmt_iterator bsi; --- 13581,13591 ---- When lazy updating is being used, the immediate use information is out of date and cannot be used reliably. Lazy updating is achieved by ! simply marking statements modified via calls to `gimple_set_modified' ! instead of `update_stmt'. When lazy updating is no longer required, ! all the modified statements must have `update_stmt' called in order to ! bring them up to date. This must be done before the optimization is ! finished, or `verify_ssa' will trigger an abort. This is done with a simple loop over the instruction stream: block_stmt_iterator bsi; *************** File: gccint.info, Node: SSA, Next: Al *** 13453,13462 **** Most of the tree optimizers rely on the data flow information provided by the Static Single Assignment (SSA) form. We implement the SSA form ! as described in 'R. Cytron, J. Ferrante, B. Rosen, M. Wegman, and K. ! Zadeck. Efficiently Computing Static Single Assignment Form and the ! Control Dependence Graph. ACM Transactions on Programming Languages and ! Systems, 13(4):451-490, October 1991'. The SSA form is based on the premise that program variables are assigned in exactly one location in the program. Multiple assignments --- 13604,13613 ---- Most of the tree optimizers rely on the data flow information provided by the Static Single Assignment (SSA) form. We implement the SSA form ! as described in `R. Cytron, J. Ferrante, B. Rosen, M. Wegman, and K. ! Zadeck. Efficiently Computing Static Single Assignment Form and the ! Control Dependence Graph. ACM Transactions on Programming Languages ! and Systems, 13(4):451-490, October 1991'. The SSA form is based on the premise that program variables are assigned in exactly one location in the program. Multiple assignments *************** representation so that every time a vari *** 13467,13480 **** new version of the variable is created. Different versions of the same variable are distinguished by subscripting the variable name with its version number. Variables used in the right-hand side of expressions ! are renamed so that their version number matches that of the most recent ! assignment. ! We represent variable versions using 'SSA_NAME' nodes. The renaming ! process in 'tree-ssa.c' wraps every real and virtual operand with an ! 'SSA_NAME' node which contains the version number and the statement that ! created the 'SSA_NAME'. Only definitions and virtual definitions may ! create new 'SSA_NAME' nodes. Sometimes, flow of control makes it impossible to determine the most recent version of a variable. In these cases, the compiler inserts an --- 13618,13631 ---- new version of the variable is created. Different versions of the same variable are distinguished by subscripting the variable name with its version number. Variables used in the right-hand side of expressions ! are renamed so that their version number matches that of the most ! recent assignment. ! We represent variable versions using `SSA_NAME' nodes. The renaming ! process in `tree-ssa.c' wraps every real and virtual operand with an ! `SSA_NAME' node which contains the version number and the statement ! that created the `SSA_NAME'. Only definitions and virtual definitions ! may create new `SSA_NAME' nodes. Sometimes, flow of control makes it impossible to determine the most recent version of a variable. In these cases, the compiler inserts an *************** variable to create a new name for it. F *** 13493,13511 **** return a_4; Since it is not possible to determine which of the three branches will ! be taken at runtime, we don't know which of 'a_1', 'a_2' or 'a_3' to use ! at the return statement. So, the SSA renamer creates a new version ! 'a_4' which is assigned the result of "merging" 'a_1', 'a_2' and 'a_3'. Hence, PHI nodes mean "one of these operands. I don't know which". The following functions can be used to examine PHI nodes -- Function: gimple_phi_result (PHI) ! Returns the 'SSA_NAME' created by PHI node PHI (i.e., PHI's LHS). -- Function: gimple_phi_num_args (PHI) ! Returns the number of arguments in PHI. This number is exactly the ! number of incoming edges to the basic block holding PHI. -- Function: gimple_phi_arg (PHI, I) Returns Ith argument of PHI. --- 13644,13662 ---- return a_4; Since it is not possible to determine which of the three branches will ! be taken at runtime, we don't know which of `a_1', `a_2' or `a_3' to ! use at the return statement. So, the SSA renamer creates a new version ! `a_4' which is assigned the result of "merging" `a_1', `a_2' and `a_3'. Hence, PHI nodes mean "one of these operands. I don't know which". The following functions can be used to examine PHI nodes -- Function: gimple_phi_result (PHI) ! Returns the `SSA_NAME' created by PHI node PHI (i.e., PHI's LHS). -- Function: gimple_phi_num_args (PHI) ! Returns the number of arguments in PHI. This number is exactly ! the number of incoming edges to the basic block holding PHI. -- Function: gimple_phi_arg (PHI, I) Returns Ith argument of PHI. *************** Hence, PHI nodes mean "one of these oper *** 13514,13520 **** Returns the incoming edge for the Ith argument of PHI. -- Function: gimple_phi_arg_def (PHI, I) ! Returns the 'SSA_NAME' for the Ith argument of PHI. 12.3.1 Preserving the SSA form ------------------------------ --- 13665,13671 ---- Returns the incoming edge for the Ith argument of PHI. -- Function: gimple_phi_arg_def (PHI, I) ! Returns the `SSA_NAME' for the Ith argument of PHI. 12.3.1 Preserving the SSA form ------------------------------ *************** SSA form. *** 13531,13538 **** variables, keeping the SSA form up to date depends on whether you are updating register or virtual names. In both cases, the general idea behind incremental SSA updates is similar: when new SSA names are ! created, they typically are meant to replace other existing names in the ! program. For instance, given the following code: --- 13682,13689 ---- variables, keeping the SSA form up to date depends on whether you are updating register or virtual names. In both cases, the general idea behind incremental SSA updates is similar: when new SSA names are ! created, they typically are meant to replace other existing names in ! the program. For instance, given the following code: *************** program. *** 13548,13554 **** 10 goto L0; 11 endif ! Suppose that we insert new names 'x_10' and 'x_11' (lines '4' and '8'). 1 L0: 2 x_1 = PHI (0, x_5) --- 13699,13705 ---- 10 goto L0; 11 endif ! Suppose that we insert new names `x_10' and `x_11' (lines `4' and `8'). 1 L0: 2 x_1 = PHI (0, x_5) *************** program. *** 13564,13650 **** 12 goto L0; 13 endif ! We want to replace all the uses of 'x_1' with the new definitions of ! 'x_10' and 'x_11'. Note that the only uses that should be replaced are ! those at lines '5', '9' and '11'. Also, the use of 'x_7' at line '9' ! should _not_ be replaced (this is why we cannot just mark symbol 'x' for renaming). ! Additionally, we may need to insert a PHI node at line '11' because ! that is a merge point for 'x_10' and 'x_11'. So the use of 'x_1' at ! line '11' will be replaced with the new PHI node. The insertion of PHI nodes is optional. They are not strictly necessary to preserve the SSA form, and depending on what the caller inserted, they may not even be useful for the optimizers. Updating the SSA form is a two step process. First, the pass has to identify which names need to be updated and/or which symbols need to be ! renamed into SSA form for the first time. When new names are introduced ! to replace existing names in the program, the mapping between the old ! and the new names are registered by calling 'register_new_name_mapping' ! (note that if your pass creates new code by duplicating basic blocks, ! the call to 'tree_duplicate_bb' will set up the necessary mappings ! automatically). After the replacement mappings have been registered and new symbols ! marked for renaming, a call to 'update_ssa' makes the registered ! changes. This can be done with an explicit call or by creating 'TODO' ! flags in the 'tree_opt_pass' structure for your pass. There are several ! 'TODO' flags that control the behavior of 'update_ssa': ! * 'TODO_update_ssa'. Update the SSA form inserting PHI nodes for newly exposed symbols and virtual names marked for updating. When ! updating real names, only insert PHI nodes for a real name 'O_j' in ! blocks reached by all the new and old definitions for 'O_j'. If ! the iterated dominance frontier for 'O_j' is not pruned, we may end ! up inserting PHI nodes in blocks that have one or more edges with ! no incoming definition for 'O_j'. This would lead to uninitialized ! warnings for 'O_j''s symbol. ! * 'TODO_update_ssa_no_phi'. Update the SSA form without inserting any new PHI nodes at all. This is used by passes that have either inserted all the PHI nodes themselves or passes that need only to patch use-def and def-def chains for virtuals (e.g., DCE). ! * 'TODO_update_ssa_full_phi'. Insert PHI nodes everywhere they are needed. No pruning of the IDF is done. This is used by passes ! that need the PHI nodes for 'O_j' even if it means that some ! arguments will come from the default definition of 'O_j''s symbol ! (e.g., 'pass_linear_transform'). WARNING: If you need to use this flag, chances are that your pass may be doing something wrong. Inserting PHI nodes for an old name where not all edges carry a new replacement may lead to silent codegen errors or spurious uninitialized warnings. ! * 'TODO_update_ssa_only_virtuals'. Passes that update the SSA form on their own may want to delegate the updating of virtual names to ! the generic updater. Since FUD chains are easier to maintain, this ! simplifies the work they need to do. NOTE: If this flag is used, ! any OLD->NEW mappings for real names are explicitly destroyed and ! only the symbols marked for renaming are processed. ! 12.3.2 Examining 'SSA_NAME' nodes --------------------------------- ! The following macros can be used to examine 'SSA_NAME' nodes -- Macro: SSA_NAME_DEF_STMT (VAR) ! Returns the statement S that creates the 'SSA_NAME' VAR. If S is ! an empty statement (i.e., 'IS_EMPTY_STMT (S)' returns 'true'), it means that the first reference to this variable is a USE or a VUSE. -- Macro: SSA_NAME_VERSION (VAR) ! Returns the version number of the 'SSA_NAME' object VAR. 12.3.3 Walking the dominator tree --------------------------------- -- Tree SSA function: void walk_dominator_tree (WALK_DATA, BB) - This function walks the dominator tree for the current CFG calling a set of callback functions defined in STRUCT DOM_WALK_DATA in ! 'domwalk.h'. The call back functions you need to define give you hooks to execute custom code at various points during traversal: 1. Once to initialize any local data needed while processing BB --- 13715,13800 ---- 12 goto L0; 13 endif ! We want to replace all the uses of `x_1' with the new definitions of ! `x_10' and `x_11'. Note that the only uses that should be replaced are ! those at lines `5', `9' and `11'. Also, the use of `x_7' at line `9' ! should _not_ be replaced (this is why we cannot just mark symbol `x' for renaming). ! Additionally, we may need to insert a PHI node at line `11' because ! that is a merge point for `x_10' and `x_11'. So the use of `x_1' at ! line `11' will be replaced with the new PHI node. The insertion of PHI nodes is optional. They are not strictly necessary to preserve the SSA form, and depending on what the caller inserted, they may not even be useful for the optimizers. Updating the SSA form is a two step process. First, the pass has to identify which names need to be updated and/or which symbols need to be ! renamed into SSA form for the first time. When new names are ! introduced to replace existing names in the program, the mapping ! between the old and the new names are registered by calling ! `register_new_name_mapping' (note that if your pass creates new code by ! duplicating basic blocks, the call to `tree_duplicate_bb' will set up ! the necessary mappings automatically). After the replacement mappings have been registered and new symbols ! marked for renaming, a call to `update_ssa' makes the registered ! changes. This can be done with an explicit call or by creating `TODO' ! flags in the `tree_opt_pass' structure for your pass. There are ! several `TODO' flags that control the behavior of `update_ssa': ! * `TODO_update_ssa'. Update the SSA form inserting PHI nodes for newly exposed symbols and virtual names marked for updating. When ! updating real names, only insert PHI nodes for a real name `O_j' ! in blocks reached by all the new and old definitions for `O_j'. ! If the iterated dominance frontier for `O_j' is not pruned, we may ! end up inserting PHI nodes in blocks that have one or more edges ! with no incoming definition for `O_j'. This would lead to ! uninitialized warnings for `O_j''s symbol. ! * `TODO_update_ssa_no_phi'. Update the SSA form without inserting any new PHI nodes at all. This is used by passes that have either inserted all the PHI nodes themselves or passes that need only to patch use-def and def-def chains for virtuals (e.g., DCE). ! * `TODO_update_ssa_full_phi'. Insert PHI nodes everywhere they are needed. No pruning of the IDF is done. This is used by passes ! that need the PHI nodes for `O_j' even if it means that some ! arguments will come from the default definition of `O_j''s symbol ! (e.g., `pass_linear_transform'). WARNING: If you need to use this flag, chances are that your pass may be doing something wrong. Inserting PHI nodes for an old name where not all edges carry a new replacement may lead to silent codegen errors or spurious uninitialized warnings. ! * `TODO_update_ssa_only_virtuals'. Passes that update the SSA form on their own may want to delegate the updating of virtual names to ! the generic updater. Since FUD chains are easier to maintain, ! this simplifies the work they need to do. NOTE: If this flag is ! used, any OLD->NEW mappings for real names are explicitly ! destroyed and only the symbols marked for renaming are processed. ! 12.3.2 Examining `SSA_NAME' nodes --------------------------------- ! The following macros can be used to examine `SSA_NAME' nodes -- Macro: SSA_NAME_DEF_STMT (VAR) ! Returns the statement S that creates the `SSA_NAME' VAR. If S is ! an empty statement (i.e., `IS_EMPTY_STMT (S)' returns `true'), it means that the first reference to this variable is a USE or a VUSE. -- Macro: SSA_NAME_VERSION (VAR) ! Returns the version number of the `SSA_NAME' object VAR. 12.3.3 Walking the dominator tree --------------------------------- -- Tree SSA function: void walk_dominator_tree (WALK_DATA, BB) This function walks the dominator tree for the current CFG calling a set of callback functions defined in STRUCT DOM_WALK_DATA in ! `domwalk.h'. The call back functions you need to define give you hooks to execute custom code at various points during traversal: 1. Once to initialize any local data needed while processing BB *************** disambiguate explicit and implicit memor *** 13683,13691 **** 1. Memory SSA form. ! All statements that may use memory have exactly one accompanied use ! of a virtual SSA name that represents the state of memory at the ! given point in the IL. All statements that may define memory have exactly one accompanied definition of a virtual SSA name using the previous state of memory --- 13833,13841 ---- 1. Memory SSA form. ! All statements that may use memory have exactly one accompanied ! use of a virtual SSA name that represents the state of memory at ! the given point in the IL. All statements that may define memory have exactly one accompanied definition of a virtual SSA name using the previous state of memory *************** disambiguate explicit and implicit memor *** 13701,13709 **** return i; } ! The virtual SSA names in this case are '.MEM_2(D)' and '.MEM_3'. ! The store to the global variable 'i' defines '.MEM_3' invalidating ! '.MEM_2(D)'. The load from 'i' uses that new state '.MEM_3'. The virtual SSA web serves as constraints to SSA optimizers preventing illegitimate code-motion and optimization. It also --- 13851,13859 ---- return i; } ! The virtual SSA names in this case are `.MEM_2(D)' and `.MEM_3'. ! The store to the global variable `i' defines `.MEM_3' invalidating ! `.MEM_2(D)'. The load from `i' uses that new state `.MEM_3'. The virtual SSA web serves as constraints to SSA optimizers preventing illegitimate code-motion and optimization. It also *************** disambiguate explicit and implicit memor *** 13719,13746 **** what it may possibly point to. This points-to solution for a given SSA name pointer is stored in ! the 'pt_solution' sub-structure of the 'SSA_NAME_PTR_INFO' record. The following accessor functions are available: ! * 'pt_solution_includes' ! * 'pt_solutions_intersect' Points-to analysis also computes the solution for two special set ! of pointers, 'ESCAPED' and 'CALLUSED'. Those represent all memory that has escaped the scope of analysis or that is used by pure or nested const calls. 3. Type-based alias analysis Type-based alias analysis is frontend dependent though generic ! support is provided by the middle-end in 'alias.c'. TBAA code is used by both tree optimizers and RTL optimizers. Every language that wishes to perform language-specific alias ! analysis should define a function that computes, given a 'tree' ! node, an alias set for the node. Nodes in different alias sets are ! not allowed to alias. For an example, see the C front-end function ! 'c_get_alias_set'. 4. Tree alias-oracle --- 13869,13897 ---- what it may possibly point to. This points-to solution for a given SSA name pointer is stored in ! the `pt_solution' sub-structure of the `SSA_NAME_PTR_INFO' record. The following accessor functions are available: ! * `pt_solution_includes' ! ! * `pt_solutions_intersect' Points-to analysis also computes the solution for two special set ! of pointers, `ESCAPED' and `CALLUSED'. Those represent all memory that has escaped the scope of analysis or that is used by pure or nested const calls. 3. Type-based alias analysis Type-based alias analysis is frontend dependent though generic ! support is provided by the middle-end in `alias.c'. TBAA code is used by both tree optimizers and RTL optimizers. Every language that wishes to perform language-specific alias ! analysis should define a function that computes, given a `tree' ! node, an alias set for the node. Nodes in different alias sets ! are not allowed to alias. For an example, see the C front-end ! function `c_get_alias_set'. 4. Tree alias-oracle *************** disambiguate explicit and implicit memor *** 13748,13767 **** references and memory references against statements. The following queries are available: ! * 'refs_may_alias_p' ! * 'ref_maybe_used_by_stmt_p' ! * 'stmt_may_clobber_ref_p' In addition to those two kind of statement walkers are available walking statements related to a reference ref. ! 'walk_non_aliased_vuses' walks over dominating memory defining statements and calls back if the statement does not clobber ref ! providing the non-aliased VUSE. The walk stops at the first ! clobbering statement or if asked to. 'walk_aliased_vdefs' walks over dominating memory defining statements and calls back on each ! statement clobbering ref providing its aliasing VDEF. The walk stops if asked to.  File: gccint.info, Node: Memory model, Prev: Alias analysis, Up: Tree SSA --- 13899,13921 ---- references and memory references against statements. The following queries are available: ! * `refs_may_alias_p' ! ! * `ref_maybe_used_by_stmt_p' ! ! * `stmt_may_clobber_ref_p' In addition to those two kind of statement walkers are available walking statements related to a reference ref. ! `walk_non_aliased_vuses' walks over dominating memory defining statements and calls back if the statement does not clobber ref ! providing the non-aliased VUSE. The walk stops at the first ! clobbering statement or if asked to. `walk_aliased_vdefs' walks over dominating memory defining statements and calls back on each ! statement clobbering ref providing its aliasing VDEF. The walk stops if asked to. +  File: gccint.info, Node: Memory model, Prev: Alias analysis, Up: Tree SSA *************** effective type to objects with a declare *** 13782,13788 **** an lvalue having a type that is not a character type, then the type of the lvalue becomes the effective type of the object for that access and for subsequent accesses that do not modify the stored value. ! If a value is copied into an object using memcpy or memmove, or is copied as an array of character type, then the effective type of the modified object for that access and for subsequent accesses that do not modify the value is undetermined. For all other accesses to an --- 13936,13942 ---- an lvalue having a type that is not a character type, then the type of the lvalue becomes the effective type of the object for that access and for subsequent accesses that do not modify the stored value. ! If a value is copied into an object using `memcpy' or `memmove', or is copied as an array of character type, then the effective type of the modified object for that access and for subsequent accesses that do not modify the value is undetermined. For all other accesses to an *************** instructions to be output are described, *** 13801,13808 **** algebraic form that describes what the instruction does. RTL is inspired by Lisp lists. It has both an internal form, made up ! of structures that point at other structures, and a textual form that is ! used in the machine description and in printed debugging dumps. The textual form uses nested parentheses to indicate the pointers in the internal form. --- 13955,13962 ---- algebraic form that describes what the instruction does. RTL is inspired by Lisp lists. It has both an internal form, made up ! of structures that point at other structures, and a textual form that ! is used in the machine description and in printed debugging dumps. The textual form uses nested parentheses to indicate the pointers in the internal form. *************** internal form. *** 13824,13830 **** * RTL Declarations:: Declaring volatility, constancy, etc. * Side Effects:: Expressions for storing in registers, etc. * Incdec:: Embedded side-effects for autoincrement addressing. ! * Assembler:: Representing 'asm' with operands. * Debug Information:: Expressions representing debugging information. * Insns:: Expression types for entire insns. * Calls:: RTL representation of function call insns. --- 13978,13984 ---- * RTL Declarations:: Declaring volatility, constancy, etc. * Side Effects:: Expressions for storing in registers, etc. * Incdec:: Embedded side-effects for autoincrement addressing. ! * Assembler:: Representing `asm' with operands. * Debug Information:: Expressions representing debugging information. * Insns:: Expression types for entire insns. * Calls:: RTL representation of function call insns. *************** File: gccint.info, Node: RTL Objects, *** 13840,13859 **** RTL uses five kinds of objects: expressions, integers, wide integers, strings and vectors. Expressions are the most important ones. An RTL expression ("RTX", for short) is a C structure, but it is usually ! referred to with a pointer; a type that is given the typedef name 'rtx'. ! An integer is simply an 'int'; their written form uses decimal digits. ! A wide integer is an integral object whose type is 'HOST_WIDE_INT'; their written form uses decimal digits. A string is a sequence of characters. In core it is represented as a ! 'char *' in usual C fashion, and it is written in C syntax as well. ! However, strings in RTL may never be null. If you write an empty string ! in a machine description, it is represented in core as a null pointer ! rather than as a pointer to a null character. In certain contexts, ! these null pointers instead of strings are valid. Within RTL code, ! strings are most commonly found inside 'symbol_ref' expressions, but ! they appear in other contexts in the RTL expressions that make up machine descriptions. In a machine description, strings are normally written with double --- 13994,14013 ---- RTL uses five kinds of objects: expressions, integers, wide integers, strings and vectors. Expressions are the most important ones. An RTL expression ("RTX", for short) is a C structure, but it is usually ! referred to with a pointer; a type that is given the typedef name `rtx'. ! An integer is simply an `int'; their written form uses decimal digits. ! A wide integer is an integral object whose type is `HOST_WIDE_INT'; their written form uses decimal digits. A string is a sequence of characters. In core it is represented as a ! `char *' in usual C fashion, and it is written in C syntax as well. ! However, strings in RTL may never be null. If you write an empty ! string in a machine description, it is represented in core as a null ! pointer rather than as a pointer to a null character. In certain ! contexts, these null pointers instead of strings are valid. Within RTL ! code, strings are most commonly found inside `symbol_ref' expressions, ! but they appear in other contexts in the RTL expressions that make up machine descriptions. In a machine description, strings are normally written with double *************** need not escape each quote character wit *** 13873,13911 **** A vector contains an arbitrary number of pointers to expressions. The number of elements in the vector is explicitly present in the vector. ! The written form of a vector consists of square brackets ('[...]') surrounding the elements, in sequence and with whitespace separating them. Vectors of length zero are not created; null pointers are used instead. Expressions are classified by "expression codes" (also called RTX ! codes). The expression code is a name defined in 'rtl.def', which is also (in uppercase) a C enumeration constant. The possible expression codes and their meanings are machine-independent. The code of an RTX ! can be extracted with the macro 'GET_CODE (X)' and altered with ! 'PUT_CODE (X, NEWCODE)'. The expression code determines how many operands the expression contains, and what kinds of objects they are. In RTL, unlike Lisp, you cannot tell by looking at an operand what kind of object it is. ! Instead, you must know from its context--from the expression code of the ! containing expression. For example, in an expression of code 'subreg', ! the first operand is to be regarded as an expression and the second ! operand as an integer. In an expression of code 'plus', there are two ! operands, both of which are to be regarded as expressions. In a ! 'symbol_ref' expression, there is one operand, which is to be regarded ! as a string. Expressions are written as parentheses containing the name of the expression type, its flags and machine mode if any, and then the operands of the expression (separated by spaces). ! Expression code names in the 'md' file are written in lowercase, but when they appear in C code they are written in uppercase. In this ! manual, they are shown as follows: 'const_int'. In a few contexts a null pointer is valid where an expression is ! normally wanted. The written form of this is '(nil)'.  File: gccint.info, Node: RTL Classes, Next: Accessors, Prev: RTL Objects, Up: RTL --- 14027,14065 ---- A vector contains an arbitrary number of pointers to expressions. The number of elements in the vector is explicitly present in the vector. ! The written form of a vector consists of square brackets (`[...]') surrounding the elements, in sequence and with whitespace separating them. Vectors of length zero are not created; null pointers are used instead. Expressions are classified by "expression codes" (also called RTX ! codes). The expression code is a name defined in `rtl.def', which is also (in uppercase) a C enumeration constant. The possible expression codes and their meanings are machine-independent. The code of an RTX ! can be extracted with the macro `GET_CODE (X)' and altered with ! `PUT_CODE (X, NEWCODE)'. The expression code determines how many operands the expression contains, and what kinds of objects they are. In RTL, unlike Lisp, you cannot tell by looking at an operand what kind of object it is. ! Instead, you must know from its context--from the expression code of ! the containing expression. For example, in an expression of code ! `subreg', the first operand is to be regarded as an expression and the ! second operand as an integer. In an expression of code `plus', there ! are two operands, both of which are to be regarded as expressions. In ! a `symbol_ref' expression, there is one operand, which is to be ! regarded as a string. Expressions are written as parentheses containing the name of the expression type, its flags and machine mode if any, and then the operands of the expression (separated by spaces). ! Expression code names in the `md' file are written in lowercase, but when they appear in C code they are written in uppercase. In this ! manual, they are shown as follows: `const_int'. In a few contexts a null pointer is valid where an expression is ! normally wanted. The written form of this is `(nil)'.  File: gccint.info, Node: RTL Classes, Next: Accessors, Prev: RTL Objects, Up: RTL *************** File: gccint.info, Node: RTL Classes, *** 13914,14069 **** ============================ The various expression codes are divided into several "classes", which ! are represented by single characters. You can determine the class of an ! RTX code with the macro 'GET_RTX_CLASS (CODE)'. Currently, 'rtl.def' ! defines these classes: ! 'RTX_OBJ' An RTX code that represents an actual object, such as a register ! ('REG') or a memory location ('MEM', 'SYMBOL_REF'). 'LO_SUM') is ! also included; instead, 'SUBREG' and 'STRICT_LOW_PART' are not in ! this class, but in class 'x'. ! 'RTX_CONST_OBJ' ! An RTX code that represents a constant object. 'HIGH' is also included in this class. ! 'RTX_COMPARE' ! An RTX code for a non-symmetric comparison, such as 'GEU' or 'LT'. ! 'RTX_COMM_COMPARE' ! An RTX code for a symmetric (commutative) comparison, such as 'EQ' ! or 'ORDERED'. ! 'RTX_UNARY' ! An RTX code for a unary arithmetic operation, such as 'NEG', 'NOT', ! or 'ABS'. This category also includes value extension (sign or ! zero) and conversions between integer and floating point. ! 'RTX_COMM_ARITH' ! An RTX code for a commutative binary operation, such as 'PLUS' or ! 'AND'. 'NE' and 'EQ' are comparisons, so they have class '<'. ! 'RTX_BIN_ARITH' An RTX code for a non-commutative binary operation, such as ! 'MINUS', 'DIV', or 'ASHIFTRT'. ! 'RTX_BITFIELD_OPS' An RTX code for a bit-field operation. Currently only ! 'ZERO_EXTRACT' and 'SIGN_EXTRACT'. These have three inputs and are ! lvalues (so they can be used for insertion as well). *Note Bit-Fields::. ! 'RTX_TERNARY' An RTX code for other three input operations. Currently only ! 'IF_THEN_ELSE', 'VEC_MERGE', 'SIGN_EXTRACT', 'ZERO_EXTRACT', and ! 'FMA'. ! 'RTX_INSN' ! An RTX code for an entire instruction: 'INSN', 'JUMP_INSN', and ! 'CALL_INSN'. *Note Insns::. ! 'RTX_MATCH' An RTX code for something that matches in insns, such as ! 'MATCH_DUP'. These only occur in machine descriptions. ! 'RTX_AUTOINC' An RTX code for an auto-increment addressing mode, such as ! 'POST_INC'. 'XEXP (X, 0)' gives the auto-modified register. ! 'RTX_EXTRA' All other RTX codes. This category includes the remaining codes ! used only in machine descriptions ('DEFINE_*', etc.). It also ! includes all the codes describing side effects ('SET', 'USE', ! 'CLOBBER', etc.) and the non-insns that may appear on an insn ! chain, such as 'NOTE', 'BARRIER', and 'CODE_LABEL'. 'SUBREG' is also part of this class. ! For each expression code, 'rtl.def' specifies the number of contained objects and their kinds using a sequence of characters called the ! "format" of the expression code. For example, the format of 'subreg' is ! 'ei'. These are the most commonly used format characters: ! 'e' An expression (actually a pointer to an expression). ! 'i' An integer. ! 'w' A wide integer. ! 's' A string. ! 'E' A vector of expressions. A few other format characters are used occasionally: ! 'u' ! 'u' is equivalent to 'e' except that it is printed differently in debugging dumps. It is used for pointers to insns. ! 'n' ! 'n' is equivalent to 'i' except that it is printed differently in debugging dumps. It is used for the line number or code number of ! a 'note' insn. ! 'S' ! 'S' indicates a string which is optional. In the RTL objects in ! core, 'S' is equivalent to 's', but when the object is read, from ! an 'md' file, the string value of this operand may be omitted. An omitted string is taken to be the null string. ! 'V' ! 'V' indicates a vector which is optional. In the RTL objects in ! core, 'V' is equivalent to 'E', but when the object is read from an ! 'md' file, the vector value of this operand may be omitted. An omitted vector is effectively the same as a vector of no elements. ! 'B' ! 'B' indicates a pointer to basic block structure. ! '0' ! '0' means a slot whose contents do not fit any normal category. ! '0' slots are not printed at all in dumps, and are often used in special ways by small parts of the compiler. There are macros to get the number of operands and the format of an expression code: ! 'GET_RTX_LENGTH (CODE)' Number of operands of an RTX of code CODE. ! 'GET_RTX_FORMAT (CODE)' The format of an RTX of code CODE, as a C string. Some classes of RTX codes always have the same format. For example, it ! is safe to assume that all comparison operations have format 'ee'. ! '1' ! All codes of this class have format 'e'. ! '<' ! 'c' ! '2' ! All codes of these classes have format 'ee'. ! 'b' ! '3' ! All codes of these classes have format 'eee'. ! 'i' ! All codes of this class have formats that begin with 'iuueiee'. *Note Insns::. Note that not all RTL objects linked onto an insn ! chain are of class 'i'. ! 'o' ! 'm' ! 'x' You can make no assumptions about the format of these codes.  --- 14068,14223 ---- ============================ The various expression codes are divided into several "classes", which ! are represented by single characters. You can determine the class of ! an RTX code with the macro `GET_RTX_CLASS (CODE)'. Currently, ! `rtl.def' defines these classes: ! `RTX_OBJ' An RTX code that represents an actual object, such as a register ! (`REG') or a memory location (`MEM', `SYMBOL_REF'). `LO_SUM') is ! also included; instead, `SUBREG' and `STRICT_LOW_PART' are not in ! this class, but in class `x'. ! `RTX_CONST_OBJ' ! An RTX code that represents a constant object. `HIGH' is also included in this class. ! `RTX_COMPARE' ! An RTX code for a non-symmetric comparison, such as `GEU' or `LT'. ! `RTX_COMM_COMPARE' ! An RTX code for a symmetric (commutative) comparison, such as `EQ' ! or `ORDERED'. ! `RTX_UNARY' ! An RTX code for a unary arithmetic operation, such as `NEG', ! `NOT', or `ABS'. This category also includes value extension ! (sign or zero) and conversions between integer and floating point. ! `RTX_COMM_ARITH' ! An RTX code for a commutative binary operation, such as `PLUS' or ! `AND'. `NE' and `EQ' are comparisons, so they have class `<'. ! `RTX_BIN_ARITH' An RTX code for a non-commutative binary operation, such as ! `MINUS', `DIV', or `ASHIFTRT'. ! `RTX_BITFIELD_OPS' An RTX code for a bit-field operation. Currently only ! `ZERO_EXTRACT' and `SIGN_EXTRACT'. These have three inputs and ! are lvalues (so they can be used for insertion as well). *Note Bit-Fields::. ! `RTX_TERNARY' An RTX code for other three input operations. Currently only ! `IF_THEN_ELSE', `VEC_MERGE', `SIGN_EXTRACT', `ZERO_EXTRACT', and ! `FMA'. ! `RTX_INSN' ! An RTX code for an entire instruction: `INSN', `JUMP_INSN', and ! `CALL_INSN'. *Note Insns::. ! `RTX_MATCH' An RTX code for something that matches in insns, such as ! `MATCH_DUP'. These only occur in machine descriptions. ! `RTX_AUTOINC' An RTX code for an auto-increment addressing mode, such as ! `POST_INC'. `XEXP (X, 0)' gives the auto-modified register. ! `RTX_EXTRA' All other RTX codes. This category includes the remaining codes ! used only in machine descriptions (`DEFINE_*', etc.). It also ! includes all the codes describing side effects (`SET', `USE', ! `CLOBBER', etc.) and the non-insns that may appear on an insn ! chain, such as `NOTE', `BARRIER', and `CODE_LABEL'. `SUBREG' is also part of this class. ! For each expression code, `rtl.def' specifies the number of contained objects and their kinds using a sequence of characters called the ! "format" of the expression code. For example, the format of `subreg' ! is `ei'. These are the most commonly used format characters: ! `e' An expression (actually a pointer to an expression). ! `i' An integer. ! `w' A wide integer. ! `s' A string. ! `E' A vector of expressions. A few other format characters are used occasionally: ! `u' ! `u' is equivalent to `e' except that it is printed differently in debugging dumps. It is used for pointers to insns. ! `n' ! `n' is equivalent to `i' except that it is printed differently in debugging dumps. It is used for the line number or code number of ! a `note' insn. ! `S' ! `S' indicates a string which is optional. In the RTL objects in ! core, `S' is equivalent to `s', but when the object is read, from ! an `md' file, the string value of this operand may be omitted. An omitted string is taken to be the null string. ! `V' ! `V' indicates a vector which is optional. In the RTL objects in ! core, `V' is equivalent to `E', but when the object is read from ! an `md' file, the vector value of this operand may be omitted. An omitted vector is effectively the same as a vector of no elements. ! `B' ! `B' indicates a pointer to basic block structure. ! `0' ! `0' means a slot whose contents do not fit any normal category. ! `0' slots are not printed at all in dumps, and are often used in special ways by small parts of the compiler. There are macros to get the number of operands and the format of an expression code: ! `GET_RTX_LENGTH (CODE)' Number of operands of an RTX of code CODE. ! `GET_RTX_FORMAT (CODE)' The format of an RTX of code CODE, as a C string. Some classes of RTX codes always have the same format. For example, it ! is safe to assume that all comparison operations have format `ee'. ! `1' ! All codes of this class have format `e'. ! `<' ! `c' ! `2' ! All codes of these classes have format `ee'. ! `b' ! `3' ! All codes of these classes have format `eee'. ! `i' ! All codes of this class have formats that begin with `iuueiee'. *Note Insns::. Note that not all RTL objects linked onto an insn ! chain are of class `i'. ! `o' ! `m' ! `x' You can make no assumptions about the format of these codes.  *************** File: gccint.info, Node: Accessors, Ne *** 14072,14079 **** 13.3 Access to Operands ======================= ! Operands of expressions are accessed using the macros 'XEXP', 'XINT', ! 'XWINT' and 'XSTR'. Each of these macros takes two arguments: an expression-pointer (RTX) and an operand number (counting from zero). Thus, --- 14226,14233 ---- 13.3 Access to Operands ======================= ! Operands of expressions are accessed using the macros `XEXP', `XINT', ! `XWINT' and `XSTR'. Each of these macros takes two arguments: an expression-pointer (RTX) and an operand number (counting from zero). Thus, *************** accesses operand 2 of expression X, as a *** 14083,14089 **** XINT (X, 2) ! accesses the same operand as an integer. 'XSTR', used in the same fashion, would access it as a string. Any operand can be accessed as an integer, as an expression or as a --- 14237,14243 ---- XINT (X, 2) ! accesses the same operand as an integer. `XSTR', used in the same fashion, would access it as a string. Any operand can be accessed as an integer, as an expression or as a *************** value actually stored in the operand. Y *** 14092,14125 **** expression code of the containing expression. That is also how you would know how many operands there are. ! For example, if X is a 'subreg' expression, you know that it has two ! operands which can be correctly accessed as 'XEXP (X, 0)' and 'XINT (X, ! 1)'. If you did 'XINT (X, 0)', you would get the address of the expression operand but cast as an integer; that might occasionally be ! useful, but it would be cleaner to write '(int) XEXP (X, 0)'. 'XEXP (X, ! 1)' would also compile without error, and would return the second, integer operand cast as an expression pointer, which would probably ! result in a crash when accessed. Nothing stops you from writing 'XEXP (X, 28)' either, but this will access memory past the end of the expression with unpredictable results. Access to operands which are vectors is more complicated. You can use ! the macro 'XVEC' to get the vector-pointer itself, or the macros ! 'XVECEXP' and 'XVECLEN' to access the elements and length of a vector. ! 'XVEC (EXP, IDX)' Access the vector-pointer which is operand number IDX in EXP. ! 'XVECLEN (EXP, IDX)' Access the length (number of elements) in the vector which is in ! operand number IDX in EXP. This value is an 'int'. ! 'XVECEXP (EXP, IDX, ELTNUM)' Access element number ELTNUM in the vector which is in operand number IDX in EXP. This value is an RTX. It is up to you to make sure that ELTNUM is not negative and is ! less than 'XVECLEN (EXP, IDX)'. All the macros defined in this section expand into lvalues and therefore can be used to assign the operands, lengths and vector --- 14246,14279 ---- expression code of the containing expression. That is also how you would know how many operands there are. ! For example, if X is a `subreg' expression, you know that it has two ! operands which can be correctly accessed as `XEXP (X, 0)' and `XINT (X, ! 1)'. If you did `XINT (X, 0)', you would get the address of the expression operand but cast as an integer; that might occasionally be ! useful, but it would be cleaner to write `(int) XEXP (X, 0)'. `XEXP ! (X, 1)' would also compile without error, and would return the second, integer operand cast as an expression pointer, which would probably ! result in a crash when accessed. Nothing stops you from writing `XEXP (X, 28)' either, but this will access memory past the end of the expression with unpredictable results. Access to operands which are vectors is more complicated. You can use ! the macro `XVEC' to get the vector-pointer itself, or the macros ! `XVECEXP' and `XVECLEN' to access the elements and length of a vector. ! `XVEC (EXP, IDX)' Access the vector-pointer which is operand number IDX in EXP. ! `XVECLEN (EXP, IDX)' Access the length (number of elements) in the vector which is in ! operand number IDX in EXP. This value is an `int'. ! `XVECEXP (EXP, IDX, ELTNUM)' Access element number ELTNUM in the vector which is in operand number IDX in EXP. This value is an RTX. It is up to you to make sure that ELTNUM is not negative and is ! less than `XVECLEN (EXP, IDX)'. All the macros defined in this section expand into lvalues and therefore can be used to assign the operands, lengths and vector *************** File: gccint.info, Node: Special Access *** 14133,14270 **** Some RTL nodes have special annotations associated with them. ! 'MEM' ! 'MEM_ALIAS_SET (X)' If 0, X is not in any alias set, and may alias anything. ! Otherwise, X can only alias 'MEM's in a conflicting alias set. ! This value is set in a language-dependent manner in the ! front-end, and should not be altered in the back-end. In some ! front-ends, these numbers may correspond in some way to types, ! or other language-level entities, but they need not, and the ! back-end makes no such assumptions. These set numbers are ! tested with 'alias_sets_conflict_p'. ! 'MEM_EXPR (X)' If this register is known to hold the value of some user-level declaration, this is that tree node. It may also be a ! 'COMPONENT_REF', in which case this is some field reference, ! and 'TREE_OPERAND (X, 0)' contains the declaration, or another ! 'COMPONENT_REF', or null if there is no compile-time object ! associated with the reference. ! 'MEM_OFFSET_KNOWN_P (X)' ! True if the offset of the memory reference from 'MEM_EXPR' is ! known. 'MEM_OFFSET (X)' provides the offset if so. ! 'MEM_OFFSET (X)' ! The offset from the start of 'MEM_EXPR'. The value is only ! valid if 'MEM_OFFSET_KNOWN_P (X)' is true. ! 'MEM_SIZE_KNOWN_P (X)' ! True if the size of the memory reference is known. 'MEM_SIZE (X)' provides its size if so. ! 'MEM_SIZE (X)' The size in bytes of the memory reference. This is mostly ! relevant for 'BLKmode' references as otherwise the size is implied by the mode. The value is only valid if ! 'MEM_SIZE_KNOWN_P (X)' is true. ! 'MEM_ALIGN (X)' The known alignment in bits of the memory reference. ! 'MEM_ADDR_SPACE (X)' ! The address space of the memory reference. This will commonly ! be zero for the generic address space. ! 'REG' ! 'ORIGINAL_REGNO (X)' ! This field holds the number the register "originally" had; for ! a pseudo register turned into a hard reg this will hold the ! old pseudo register number. ! 'REG_EXPR (X)' If this register is known to hold the value of some user-level declaration, this is that tree node. ! 'REG_OFFSET (X)' If this register is known to hold the value of some user-level declaration, this is the offset into that logical storage. ! 'SYMBOL_REF' ! 'SYMBOL_REF_DECL (X)' ! If the 'symbol_ref' X was created for a 'VAR_DECL' or a ! 'FUNCTION_DECL', that tree is recorded here. If this value is null, then X was created by back end code generation routines, and there is no associated front end symbol table entry. ! 'SYMBOL_REF_DECL' may also point to a tree of class ''c'', that is, some sort of constant. In this case, the ! 'symbol_ref' is an entry in the per-file constant pool; again, ! there is no associated front end symbol table entry. ! 'SYMBOL_REF_CONSTANT (X)' ! If 'CONSTANT_POOL_ADDRESS_P (X)' is true, this is the constant pool entry for X. It is null otherwise. ! 'SYMBOL_REF_DATA (X)' ! A field of opaque type used to store 'SYMBOL_REF_DECL' or ! 'SYMBOL_REF_CONSTANT'. ! 'SYMBOL_REF_FLAGS (X)' ! In a 'symbol_ref', this is used to communicate various predicates about the symbol. Some of these are common enough to be computed by common code, some are specific to the target. The common bits are: ! 'SYMBOL_FLAG_FUNCTION' Set if the symbol refers to a function. ! 'SYMBOL_FLAG_LOCAL' Set if the symbol is local to this "module". See ! 'TARGET_BINDS_LOCAL_P'. ! 'SYMBOL_FLAG_EXTERNAL' Set if this symbol is not defined in this translation unit. Note that this is not the inverse of ! 'SYMBOL_FLAG_LOCAL'. ! 'SYMBOL_FLAG_SMALL' Set if the symbol is located in the small data section. ! See 'TARGET_IN_SMALL_DATA_P'. ! 'SYMBOL_REF_TLS_MODEL (X)' This is a multi-bit field accessor that returns the ! 'tls_model' to be used for a thread-local storage symbol. ! It returns zero for non-thread-local symbols. ! 'SYMBOL_FLAG_HAS_BLOCK_INFO' ! Set if the symbol has 'SYMBOL_REF_BLOCK' and ! 'SYMBOL_REF_BLOCK_OFFSET' fields. ! 'SYMBOL_FLAG_ANCHOR' Set if the symbol is used as a section anchor. "Section ! anchors" are symbols that have a known position within an ! 'object_block' and that can be used to access nearby members of that block. They are used to implement ! '-fsection-anchors'. ! If this flag is set, then 'SYMBOL_FLAG_HAS_BLOCK_INFO' will be too. ! Bits beginning with 'SYMBOL_FLAG_MACH_DEP' are available for the target's use. ! 'SYMBOL_REF_BLOCK (X)' ! If 'SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the 'object_block' ! structure to which the symbol belongs, or 'NULL' if it has not been ! assigned a block. ! 'SYMBOL_REF_BLOCK_OFFSET (X)' ! If 'SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the offset of X from ! the first object in 'SYMBOL_REF_BLOCK (X)'. The value is negative ! if X has not yet been assigned to a block, or it has not been given ! an offset within that block.  File: gccint.info, Node: Flags, Next: Machine Modes, Prev: Special Accessors, Up: RTL --- 14287,14427 ---- Some RTL nodes have special annotations associated with them. ! `MEM' ! ! `MEM_ALIAS_SET (X)' If 0, X is not in any alias set, and may alias anything. ! Otherwise, X can only alias `MEM's in a conflicting alias ! set. This value is set in a language-dependent manner in the ! front-end, and should not be altered in the back-end. In ! some front-ends, these numbers may correspond in some way to ! types, or other language-level entities, but they need not, ! and the back-end makes no such assumptions. These set ! numbers are tested with `alias_sets_conflict_p'. ! `MEM_EXPR (X)' If this register is known to hold the value of some user-level declaration, this is that tree node. It may also be a ! `COMPONENT_REF', in which case this is some field reference, ! and `TREE_OPERAND (X, 0)' contains the declaration, or ! another `COMPONENT_REF', or null if there is no compile-time ! object associated with the reference. ! `MEM_OFFSET_KNOWN_P (X)' ! True if the offset of the memory reference from `MEM_EXPR' is ! known. `MEM_OFFSET (X)' provides the offset if so. ! `MEM_OFFSET (X)' ! The offset from the start of `MEM_EXPR'. The value is only ! valid if `MEM_OFFSET_KNOWN_P (X)' is true. ! `MEM_SIZE_KNOWN_P (X)' ! True if the size of the memory reference is known. `MEM_SIZE (X)' provides its size if so. ! `MEM_SIZE (X)' The size in bytes of the memory reference. This is mostly ! relevant for `BLKmode' references as otherwise the size is implied by the mode. The value is only valid if ! `MEM_SIZE_KNOWN_P (X)' is true. ! `MEM_ALIGN (X)' The known alignment in bits of the memory reference. ! `MEM_ADDR_SPACE (X)' ! The address space of the memory reference. This will ! commonly be zero for the generic address space. ! `REG' ! `ORIGINAL_REGNO (X)' ! This field holds the number the register "originally" had; ! for a pseudo register turned into a hard reg this will hold ! the old pseudo register number. ! ! `REG_EXPR (X)' If this register is known to hold the value of some user-level declaration, this is that tree node. ! `REG_OFFSET (X)' If this register is known to hold the value of some user-level declaration, this is the offset into that logical storage. ! `SYMBOL_REF' ! ! `SYMBOL_REF_DECL (X)' ! If the `symbol_ref' X was created for a `VAR_DECL' or a ! `FUNCTION_DECL', that tree is recorded here. If this value is null, then X was created by back end code generation routines, and there is no associated front end symbol table entry. ! `SYMBOL_REF_DECL' may also point to a tree of class `'c'', that is, some sort of constant. In this case, the ! `symbol_ref' is an entry in the per-file constant pool; ! again, there is no associated front end symbol table entry. ! `SYMBOL_REF_CONSTANT (X)' ! If `CONSTANT_POOL_ADDRESS_P (X)' is true, this is the constant pool entry for X. It is null otherwise. ! `SYMBOL_REF_DATA (X)' ! A field of opaque type used to store `SYMBOL_REF_DECL' or ! `SYMBOL_REF_CONSTANT'. ! `SYMBOL_REF_FLAGS (X)' ! In a `symbol_ref', this is used to communicate various predicates about the symbol. Some of these are common enough to be computed by common code, some are specific to the target. The common bits are: ! `SYMBOL_FLAG_FUNCTION' Set if the symbol refers to a function. ! `SYMBOL_FLAG_LOCAL' Set if the symbol is local to this "module". See ! `TARGET_BINDS_LOCAL_P'. ! `SYMBOL_FLAG_EXTERNAL' Set if this symbol is not defined in this translation unit. Note that this is not the inverse of ! `SYMBOL_FLAG_LOCAL'. ! `SYMBOL_FLAG_SMALL' Set if the symbol is located in the small data section. ! See `TARGET_IN_SMALL_DATA_P'. ! `SYMBOL_REF_TLS_MODEL (X)' This is a multi-bit field accessor that returns the ! `tls_model' to be used for a thread-local storage ! symbol. It returns zero for non-thread-local symbols. ! `SYMBOL_FLAG_HAS_BLOCK_INFO' ! Set if the symbol has `SYMBOL_REF_BLOCK' and ! `SYMBOL_REF_BLOCK_OFFSET' fields. ! `SYMBOL_FLAG_ANCHOR' Set if the symbol is used as a section anchor. "Section ! anchors" are symbols that have a known position within ! an `object_block' and that can be used to access nearby members of that block. They are used to implement ! `-fsection-anchors'. ! If this flag is set, then `SYMBOL_FLAG_HAS_BLOCK_INFO' will be too. ! Bits beginning with `SYMBOL_FLAG_MACH_DEP' are available for the target's use. ! `SYMBOL_REF_BLOCK (X)' ! If `SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the `object_block' ! structure to which the symbol belongs, or `NULL' if it has not ! been assigned a block. ! `SYMBOL_REF_BLOCK_OFFSET (X)' ! If `SYMBOL_REF_HAS_BLOCK_INFO_P (X)', this is the offset of X from ! the first object in `SYMBOL_REF_BLOCK (X)'. The value is negative ! if X has not yet been assigned to a block, or it has not been ! given an offset within that block.  File: gccint.info, Node: Flags, Next: Machine Modes, Prev: Special Accessors, Up: RTL *************** File: gccint.info, Node: Flags, Next: *** 14272,14385 **** 13.5 Flags in an RTL Expression =============================== ! RTL expressions contain several flags (one-bit bit-fields) that are used ! in certain types of expression. Most often they are accessed with the ! following macros, which expand into lvalues. ! 'CONSTANT_POOL_ADDRESS_P (X)' ! Nonzero in a 'symbol_ref' if it refers to part of the current function's constant pool. For most targets these addresses are in ! a '.rodata' section entirely separate from the function, but for some targets the addresses are close to the beginning of the function. In either case GCC assumes these addresses can be addressed directly, perhaps with the help of base registers. ! Stored in the 'unchanging' field and printed as '/u'. ! 'RTL_CONST_CALL_P (X)' ! In a 'call_insn' indicates that the insn represents a call to a ! const function. Stored in the 'unchanging' field and printed as ! '/u'. ! 'RTL_PURE_CALL_P (X)' ! In a 'call_insn' indicates that the insn represents a call to a ! pure function. Stored in the 'return_val' field and printed as ! '/i'. ! 'RTL_CONST_OR_PURE_CALL_P (X)' ! In a 'call_insn', true if 'RTL_CONST_CALL_P' or 'RTL_PURE_CALL_P' is true. ! 'RTL_LOOPING_CONST_OR_PURE_CALL_P (X)' ! In a 'call_insn' indicates that the insn represents a possibly infinite looping call to a const or pure function. Stored in the ! 'call' field and printed as '/c'. Only true if one of ! 'RTL_CONST_CALL_P' or 'RTL_PURE_CALL_P' is true. ! 'INSN_ANNULLED_BRANCH_P (X)' ! In a 'jump_insn', 'call_insn', or 'insn' indicates that the branch ! is an annulling one. See the discussion under 'sequence' below. ! Stored in the 'unchanging' field and printed as '/u'. ! 'INSN_DELETED_P (X)' ! In an 'insn', 'call_insn', 'jump_insn', 'code_label', ! 'jump_table_data', 'barrier', or 'note', nonzero if the insn has ! been deleted. Stored in the 'volatil' field and printed as '/v'. ! 'INSN_FROM_TARGET_P (X)' ! In an 'insn' or 'jump_insn' or 'call_insn' in a delay slot of a branch, indicates that the insn is from the target of the branch. ! If the branch insn has 'INSN_ANNULLED_BRANCH_P' set, this insn will ! only be executed if the branch is taken. For annulled branches ! with 'INSN_FROM_TARGET_P' clear, the insn will be executed only if ! the branch is not taken. When 'INSN_ANNULLED_BRANCH_P' is not set, ! this insn will always be executed. Stored in the 'in_struct' field ! and printed as '/s'. ! 'LABEL_PRESERVE_P (X)' ! In a 'code_label' or 'note', indicates that the label is referenced ! by code or data not visible to the RTL of a given function. Labels ! referenced by a non-local goto will have this bit set. Stored in ! the 'in_struct' field and printed as '/s'. ! 'LABEL_REF_NONLOCAL_P (X)' ! In 'label_ref' and 'reg_label' expressions, nonzero if this is a ! reference to a non-local label. Stored in the 'volatil' field and ! printed as '/v'. ! 'MEM_KEEP_ALIAS_SET_P (X)' ! In 'mem' expressions, 1 if we should keep the alias set for this mem unchanged when we access a component. Set to 1, for example, when we are already in a non-addressable component of an aggregate. ! Stored in the 'jump' field and printed as '/j'. ! 'MEM_VOLATILE_P (X)' ! In 'mem', 'asm_operands', and 'asm_input' expressions, nonzero for ! volatile memory references. Stored in the 'volatil' field and ! printed as '/v'. ! 'MEM_NOTRAP_P (X)' ! In 'mem', nonzero for memory references that will not trap. Stored ! in the 'call' field and printed as '/c'. ! 'MEM_POINTER (X)' ! Nonzero in a 'mem' if the memory reference holds a pointer. Stored ! in the 'frame_related' field and printed as '/f'. ! 'REG_FUNCTION_VALUE_P (X)' ! Nonzero in a 'reg' if it is the place in which this function's value is going to be returned. (This happens only in a hard ! register.) Stored in the 'return_val' field and printed as '/i'. ! 'REG_POINTER (X)' ! Nonzero in a 'reg' if the register holds a pointer. Stored in the ! 'frame_related' field and printed as '/f'. ! 'REG_USERVAR_P (X)' ! In a 'reg', nonzero if it corresponds to a variable present in the user's source code. Zero for temporaries generated internally by ! the compiler. Stored in the 'volatil' field and printed as '/v'. The same hard register may be used also for collecting the values ! of functions called by this one, but 'REG_FUNCTION_VALUE_P' is zero in this kind of use. ! 'RTX_FRAME_RELATED_P (X)' ! Nonzero in an 'insn', 'call_insn', 'jump_insn', 'barrier', or 'set' ! which is part of a function prologue and sets the stack pointer, ! sets the frame pointer, or saves a register. This flag should also ! be set on an instruction that sets up a temporary register to use ! in place of the frame pointer. Stored in the 'frame_related' field ! and printed as '/f'. In particular, on RISC targets where there are limits on the sizes of immediate constants, it is sometimes impossible to reach the --- 14429,14542 ---- 13.5 Flags in an RTL Expression =============================== ! RTL expressions contain several flags (one-bit bit-fields) that are ! used in certain types of expression. Most often they are accessed with ! the following macros, which expand into lvalues. ! `CONSTANT_POOL_ADDRESS_P (X)' ! Nonzero in a `symbol_ref' if it refers to part of the current function's constant pool. For most targets these addresses are in ! a `.rodata' section entirely separate from the function, but for some targets the addresses are close to the beginning of the function. In either case GCC assumes these addresses can be addressed directly, perhaps with the help of base registers. ! Stored in the `unchanging' field and printed as `/u'. ! `RTL_CONST_CALL_P (X)' ! In a `call_insn' indicates that the insn represents a call to a ! const function. Stored in the `unchanging' field and printed as ! `/u'. ! `RTL_PURE_CALL_P (X)' ! In a `call_insn' indicates that the insn represents a call to a ! pure function. Stored in the `return_val' field and printed as ! `/i'. ! `RTL_CONST_OR_PURE_CALL_P (X)' ! In a `call_insn', true if `RTL_CONST_CALL_P' or `RTL_PURE_CALL_P' is true. ! `RTL_LOOPING_CONST_OR_PURE_CALL_P (X)' ! In a `call_insn' indicates that the insn represents a possibly infinite looping call to a const or pure function. Stored in the ! `call' field and printed as `/c'. Only true if one of ! `RTL_CONST_CALL_P' or `RTL_PURE_CALL_P' is true. ! `INSN_ANNULLED_BRANCH_P (X)' ! In a `jump_insn', `call_insn', or `insn' indicates that the branch ! is an annulling one. See the discussion under `sequence' below. ! Stored in the `unchanging' field and printed as `/u'. ! `INSN_DELETED_P (X)' ! In an `insn', `call_insn', `jump_insn', `code_label', ! `jump_table_data', `barrier', or `note', nonzero if the insn has ! been deleted. Stored in the `volatil' field and printed as `/v'. ! `INSN_FROM_TARGET_P (X)' ! In an `insn' or `jump_insn' or `call_insn' in a delay slot of a branch, indicates that the insn is from the target of the branch. ! If the branch insn has `INSN_ANNULLED_BRANCH_P' set, this insn ! will only be executed if the branch is taken. For annulled ! branches with `INSN_FROM_TARGET_P' clear, the insn will be ! executed only if the branch is not taken. When ! `INSN_ANNULLED_BRANCH_P' is not set, this insn will always be ! executed. Stored in the `in_struct' field and printed as `/s'. ! `LABEL_PRESERVE_P (X)' ! In a `code_label' or `note', indicates that the label is ! referenced by code or data not visible to the RTL of a given ! function. Labels referenced by a non-local goto will have this ! bit set. Stored in the `in_struct' field and printed as `/s'. ! `LABEL_REF_NONLOCAL_P (X)' ! In `label_ref' and `reg_label' expressions, nonzero if this is a ! reference to a non-local label. Stored in the `volatil' field and ! printed as `/v'. ! `MEM_KEEP_ALIAS_SET_P (X)' ! In `mem' expressions, 1 if we should keep the alias set for this mem unchanged when we access a component. Set to 1, for example, when we are already in a non-addressable component of an aggregate. ! Stored in the `jump' field and printed as `/j'. ! `MEM_VOLATILE_P (X)' ! In `mem', `asm_operands', and `asm_input' expressions, nonzero for ! volatile memory references. Stored in the `volatil' field and ! printed as `/v'. ! `MEM_NOTRAP_P (X)' ! In `mem', nonzero for memory references that will not trap. ! Stored in the `call' field and printed as `/c'. ! `MEM_POINTER (X)' ! Nonzero in a `mem' if the memory reference holds a pointer. ! Stored in the `frame_related' field and printed as `/f'. ! `REG_FUNCTION_VALUE_P (X)' ! Nonzero in a `reg' if it is the place in which this function's value is going to be returned. (This happens only in a hard ! register.) Stored in the `return_val' field and printed as `/i'. ! `REG_POINTER (X)' ! Nonzero in a `reg' if the register holds a pointer. Stored in the ! `frame_related' field and printed as `/f'. ! `REG_USERVAR_P (X)' ! In a `reg', nonzero if it corresponds to a variable present in the user's source code. Zero for temporaries generated internally by ! the compiler. Stored in the `volatil' field and printed as `/v'. The same hard register may be used also for collecting the values ! of functions called by this one, but `REG_FUNCTION_VALUE_P' is zero in this kind of use. ! `RTX_FRAME_RELATED_P (X)' ! Nonzero in an `insn', `call_insn', `jump_insn', `barrier', or ! `set' which is part of a function prologue and sets the stack ! pointer, sets the frame pointer, or saves a register. This flag ! should also be set on an instruction that sets up a temporary ! register to use in place of the frame pointer. Stored in the ! `frame_related' field and printed as `/f'. In particular, on RISC targets where there are limits on the sizes of immediate constants, it is sometimes impossible to reach the *************** following macros, which expand into lval *** 14388,14407 **** save area, and the Canonical Frame Address, i.e., DWARF2's logical frame pointer, register must (temporarily) be changed to be this temporary register. So, the instruction that sets this temporary ! register must be marked as 'RTX_FRAME_RELATED_P'. If the marked instruction is overly complex (defined in terms of ! what 'dwarf2out_frame_debug_expr' can handle), you will also have ! to create a 'REG_FRAME_RELATED_EXPR' note and attach it to the instruction. This note should contain a simple expression of the computation performed by this instruction, i.e., one that ! 'dwarf2out_frame_debug_expr' can handle. This flag is required for exception handling support on targets with RTL prologues. ! 'MEM_READONLY_P (X)' ! Nonzero in a 'mem', if the memory is statically allocated and read-only. Read-only in this context means never modified during the lifetime --- 14545,14564 ---- save area, and the Canonical Frame Address, i.e., DWARF2's logical frame pointer, register must (temporarily) be changed to be this temporary register. So, the instruction that sets this temporary ! register must be marked as `RTX_FRAME_RELATED_P'. If the marked instruction is overly complex (defined in terms of ! what `dwarf2out_frame_debug_expr' can handle), you will also have ! to create a `REG_FRAME_RELATED_EXPR' note and attach it to the instruction. This note should contain a simple expression of the computation performed by this instruction, i.e., one that ! `dwarf2out_frame_debug_expr' can handle. This flag is required for exception handling support on targets with RTL prologues. ! `MEM_READONLY_P (X)' ! Nonzero in a `mem', if the memory is statically allocated and read-only. Read-only in this context means never modified during the lifetime *************** following macros, which expand into lval *** 14412,14619 **** from the runtime loader to the application, this memory will never be subsequently modified. ! Stored in the 'unchanging' field and printed as '/u'. ! 'SCHED_GROUP_P (X)' ! During instruction scheduling, in an 'insn', 'call_insn', ! 'jump_insn' or 'jump_table_data', indicates that the previous insn must be scheduled together with this insn. This is used to ensure that certain groups of instructions will not be split up by the ! instruction scheduling pass, for example, 'use' insns before a ! 'call_insn' may not be separated from the 'call_insn'. Stored in ! the 'in_struct' field and printed as '/s'. ! 'SET_IS_RETURN_P (X)' ! For a 'set', nonzero if it is for a return. Stored in the 'jump' ! field and printed as '/j'. ! 'SIBLING_CALL_P (X)' ! For a 'call_insn', nonzero if the insn is a sibling call. Stored ! in the 'jump' field and printed as '/j'. ! 'STRING_POOL_ADDRESS_P (X)' ! For a 'symbol_ref' expression, nonzero if it addresses this ! function's string constant pool. Stored in the 'frame_related' ! field and printed as '/f'. ! 'SUBREG_PROMOTED_UNSIGNED_P (X)' ! Returns a value greater then zero for a 'subreg' that has ! 'SUBREG_PROMOTED_VAR_P' nonzero if the object being referenced is ! kept zero-extended, zero if it is kept sign-extended, and less then ! zero if it is extended some other way via the 'ptr_extend' ! instruction. Stored in the 'unchanging' field and 'volatil' field, ! printed as '/u' and '/v'. This macro may only be used to get the ! value it may not be used to change the value. Use ! 'SUBREG_PROMOTED_UNSIGNED_SET' to change the value. ! 'SUBREG_PROMOTED_UNSIGNED_SET (X)' ! Set the 'unchanging' and 'volatil' fields in a 'subreg' to reflect ! zero, sign, or other extension. If 'volatil' is zero, then ! 'unchanging' as nonzero means zero extension and as zero means sign ! extension. If 'volatil' is nonzero then some other type of ! extension was done via the 'ptr_extend' instruction. ! 'SUBREG_PROMOTED_VAR_P (X)' ! Nonzero in a 'subreg' if it was made when accessing an object that ! was promoted to a wider mode in accord with the 'PROMOTED_MODE' machine description macro (*note Storage Layout::). In this case, ! the mode of the 'subreg' is the declared mode of the object and the ! mode of 'SUBREG_REG' is the mode of the register that holds the ! object. Promoted variables are always either sign- or ! zero-extended to the wider mode on every assignment. Stored in the ! 'in_struct' field and printed as '/s'. ! 'SYMBOL_REF_USED (X)' ! In a 'symbol_ref', indicates that X has been used. This is ! normally only used to ensure that X is only declared external once. ! Stored in the 'used' field. ! 'SYMBOL_REF_WEAK (X)' ! In a 'symbol_ref', indicates that X has been declared weak. Stored ! in the 'return_val' field and printed as '/i'. ! 'SYMBOL_REF_FLAG (X)' ! In a 'symbol_ref', this is used as a flag for machine-specific ! purposes. Stored in the 'volatil' field and printed as '/v'. ! Most uses of 'SYMBOL_REF_FLAG' are historic and may be subsumed by ! 'SYMBOL_REF_FLAGS'. Certainly use of 'SYMBOL_REF_FLAGS' is mandatory if the target requires more than one bit of storage. ! 'PREFETCH_SCHEDULE_BARRIER_P (X)' ! In a 'prefetch', indicates that the prefetch is a scheduling barrier. No other INSNs will be moved over it. Stored in the ! 'volatil' field and printed as '/v'. These are the fields to which the above macros refer: ! 'call' ! In a 'mem', 1 means that the memory reference will not trap. ! In a 'call', 1 means that this pure or const call may possibly infinite loop. ! In an RTL dump, this flag is represented as '/c'. ! 'frame_related' ! In an 'insn' or 'set' expression, 1 means that it is part of a function prologue and sets the stack pointer, sets the frame pointer, saves a register, or sets up a temporary register to use in place of the frame pointer. ! In 'reg' expressions, 1 means that the register holds a pointer. ! In 'mem' expressions, 1 means that the memory reference holds a pointer. ! In 'symbol_ref' expressions, 1 means that the reference addresses this function's string constant pool. ! In an RTL dump, this flag is represented as '/f'. ! 'in_struct' ! In 'reg' expressions, it is 1 if the register has its entire life contained within the test expression of some loop. ! In 'subreg' expressions, 1 means that the 'subreg' is accessing an object that has had its mode promoted from a wider mode. ! In 'label_ref' expressions, 1 means that the referenced label is outside the innermost loop containing the insn in which the ! 'label_ref' was found. ! In 'code_label' expressions, it is 1 if the label may never be ! deleted. This is used for labels which are the target of non-local ! gotos. Such a label that would have been deleted is replaced with ! a 'note' of type 'NOTE_INSN_DELETED_LABEL'. ! In an 'insn' during dead-code elimination, 1 means that the insn is dead code. ! In an 'insn' or 'jump_insn' during reorg for an insn in the delay slot of a branch, 1 means that this insn is from the target of the branch. ! In an 'insn' during instruction scheduling, 1 means that this insn must be scheduled as part of a group together with the previous insn. ! In an RTL dump, this flag is represented as '/s'. ! 'return_val' ! In 'reg' expressions, 1 means the register contains the value to be ! returned by the current function. On machines that pass parameters ! in registers, the same register number may be used for parameters ! as well, but this flag is not set on such uses. ! In 'symbol_ref' expressions, 1 means the referenced symbol is weak. ! In 'call' expressions, 1 means the call is pure. ! In an RTL dump, this flag is represented as '/i'. ! 'jump' ! In a 'mem' expression, 1 means we should keep the alias set for this mem unchanged when we access a component. ! In a 'set', 1 means it is for a return. ! In a 'call_insn', 1 means it is a sibling call. ! In an RTL dump, this flag is represented as '/j'. ! 'unchanging' ! In 'reg' and 'mem' expressions, 1 means that the value of the expression never changes. ! In 'subreg' expressions, it is 1 if the 'subreg' references an unsigned object whose mode has been promoted to a wider mode. ! In an 'insn' or 'jump_insn' in the delay slot of a branch instruction, 1 means an annulling branch should be used. ! In a 'symbol_ref' expression, 1 means that this symbol addresses something in the per-function constant pool. ! In a 'call_insn' 1 means that this instruction is a call to a const function. ! In an RTL dump, this flag is represented as '/u'. ! 'used' This flag is used directly (without an access macro) at the end of RTL generation for a function, to count the number of times an expression appears in insns. Expressions that appear more than ! once are copied, according to the rules for shared structure (*note ! Sharing::). ! For a 'reg', it is used directly (without an access macro) by the leaf register renumbering code to ensure that each register is only renumbered once. ! In a 'symbol_ref', it indicates that an external declaration for the symbol has already been written. ! 'volatil' ! In a 'mem', 'asm_operands', or 'asm_input' expression, it is 1 if the memory reference is volatile. Volatile memory references may not be deleted, reordered or combined. ! In a 'symbol_ref' expression, it is used for machine-specific purposes. ! In a 'reg' expression, it is 1 if the value is a user-level variable. 0 indicates an internal compiler temporary. ! In an 'insn', 1 means the insn has been deleted. ! In 'label_ref' and 'reg_label' expressions, 1 means a reference to a non-local label. ! In 'prefetch' expressions, 1 means that the containing insn is a scheduling barrier. ! In an RTL dump, this flag is represented as '/v'.  File: gccint.info, Node: Machine Modes, Next: Constants, Prev: Flags, Up: RTL --- 14569,14776 ---- from the runtime loader to the application, this memory will never be subsequently modified. ! Stored in the `unchanging' field and printed as `/u'. ! `SCHED_GROUP_P (X)' ! During instruction scheduling, in an `insn', `call_insn', ! `jump_insn' or `jump_table_data', indicates that the previous insn must be scheduled together with this insn. This is used to ensure that certain groups of instructions will not be split up by the ! instruction scheduling pass, for example, `use' insns before a ! `call_insn' may not be separated from the `call_insn'. Stored in ! the `in_struct' field and printed as `/s'. ! `SET_IS_RETURN_P (X)' ! For a `set', nonzero if it is for a return. Stored in the `jump' ! field and printed as `/j'. ! `SIBLING_CALL_P (X)' ! For a `call_insn', nonzero if the insn is a sibling call. Stored ! in the `jump' field and printed as `/j'. ! `STRING_POOL_ADDRESS_P (X)' ! For a `symbol_ref' expression, nonzero if it addresses this ! function's string constant pool. Stored in the `frame_related' ! field and printed as `/f'. ! `SUBREG_PROMOTED_UNSIGNED_P (X)' ! Returns a value greater then zero for a `subreg' that has ! `SUBREG_PROMOTED_VAR_P' nonzero if the object being referenced is ! kept zero-extended, zero if it is kept sign-extended, and less ! then zero if it is extended some other way via the `ptr_extend' ! instruction. Stored in the `unchanging' field and `volatil' ! field, printed as `/u' and `/v'. This macro may only be used to ! get the value it may not be used to change the value. Use ! `SUBREG_PROMOTED_UNSIGNED_SET' to change the value. ! `SUBREG_PROMOTED_UNSIGNED_SET (X)' ! Set the `unchanging' and `volatil' fields in a `subreg' to reflect ! zero, sign, or other extension. If `volatil' is zero, then ! `unchanging' as nonzero means zero extension and as zero means ! sign extension. If `volatil' is nonzero then some other type of ! extension was done via the `ptr_extend' instruction. ! `SUBREG_PROMOTED_VAR_P (X)' ! Nonzero in a `subreg' if it was made when accessing an object that ! was promoted to a wider mode in accord with the `PROMOTED_MODE' machine description macro (*note Storage Layout::). In this case, ! the mode of the `subreg' is the declared mode of the object and ! the mode of `SUBREG_REG' is the mode of the register that holds ! the object. Promoted variables are always either sign- or ! zero-extended to the wider mode on every assignment. Stored in ! the `in_struct' field and printed as `/s'. ! `SYMBOL_REF_USED (X)' ! In a `symbol_ref', indicates that X has been used. This is ! normally only used to ensure that X is only declared external ! once. Stored in the `used' field. ! `SYMBOL_REF_WEAK (X)' ! In a `symbol_ref', indicates that X has been declared weak. ! Stored in the `return_val' field and printed as `/i'. ! `SYMBOL_REF_FLAG (X)' ! In a `symbol_ref', this is used as a flag for machine-specific ! purposes. Stored in the `volatil' field and printed as `/v'. ! Most uses of `SYMBOL_REF_FLAG' are historic and may be subsumed by ! `SYMBOL_REF_FLAGS'. Certainly use of `SYMBOL_REF_FLAGS' is mandatory if the target requires more than one bit of storage. ! `PREFETCH_SCHEDULE_BARRIER_P (X)' ! In a `prefetch', indicates that the prefetch is a scheduling barrier. No other INSNs will be moved over it. Stored in the ! `volatil' field and printed as `/v'. These are the fields to which the above macros refer: ! `call' ! In a `mem', 1 means that the memory reference will not trap. ! In a `call', 1 means that this pure or const call may possibly infinite loop. ! In an RTL dump, this flag is represented as `/c'. ! `frame_related' ! In an `insn' or `set' expression, 1 means that it is part of a function prologue and sets the stack pointer, sets the frame pointer, saves a register, or sets up a temporary register to use in place of the frame pointer. ! In `reg' expressions, 1 means that the register holds a pointer. ! In `mem' expressions, 1 means that the memory reference holds a pointer. ! In `symbol_ref' expressions, 1 means that the reference addresses this function's string constant pool. ! In an RTL dump, this flag is represented as `/f'. ! `in_struct' ! In `reg' expressions, it is 1 if the register has its entire life contained within the test expression of some loop. ! In `subreg' expressions, 1 means that the `subreg' is accessing an object that has had its mode promoted from a wider mode. ! In `label_ref' expressions, 1 means that the referenced label is outside the innermost loop containing the insn in which the ! `label_ref' was found. ! In `code_label' expressions, it is 1 if the label may never be ! deleted. This is used for labels which are the target of ! non-local gotos. Such a label that would have been deleted is ! replaced with a `note' of type `NOTE_INSN_DELETED_LABEL'. ! In an `insn' during dead-code elimination, 1 means that the insn is dead code. ! In an `insn' or `jump_insn' during reorg for an insn in the delay slot of a branch, 1 means that this insn is from the target of the branch. ! In an `insn' during instruction scheduling, 1 means that this insn must be scheduled as part of a group together with the previous insn. ! In an RTL dump, this flag is represented as `/s'. ! `return_val' ! In `reg' expressions, 1 means the register contains the value to ! be returned by the current function. On machines that pass ! parameters in registers, the same register number may be used for ! parameters as well, but this flag is not set on such uses. ! In `symbol_ref' expressions, 1 means the referenced symbol is weak. ! In `call' expressions, 1 means the call is pure. ! In an RTL dump, this flag is represented as `/i'. ! `jump' ! In a `mem' expression, 1 means we should keep the alias set for this mem unchanged when we access a component. ! In a `set', 1 means it is for a return. ! In a `call_insn', 1 means it is a sibling call. ! In an RTL dump, this flag is represented as `/j'. ! `unchanging' ! In `reg' and `mem' expressions, 1 means that the value of the expression never changes. ! In `subreg' expressions, it is 1 if the `subreg' references an unsigned object whose mode has been promoted to a wider mode. ! In an `insn' or `jump_insn' in the delay slot of a branch instruction, 1 means an annulling branch should be used. ! In a `symbol_ref' expression, 1 means that this symbol addresses something in the per-function constant pool. ! In a `call_insn' 1 means that this instruction is a call to a const function. ! In an RTL dump, this flag is represented as `/u'. ! `used' This flag is used directly (without an access macro) at the end of RTL generation for a function, to count the number of times an expression appears in insns. Expressions that appear more than ! once are copied, according to the rules for shared structure ! (*note Sharing::). ! For a `reg', it is used directly (without an access macro) by the leaf register renumbering code to ensure that each register is only renumbered once. ! In a `symbol_ref', it indicates that an external declaration for the symbol has already been written. ! `volatil' ! In a `mem', `asm_operands', or `asm_input' expression, it is 1 if the memory reference is volatile. Volatile memory references may not be deleted, reordered or combined. ! In a `symbol_ref' expression, it is used for machine-specific purposes. ! In a `reg' expression, it is 1 if the value is a user-level variable. 0 indicates an internal compiler temporary. ! In an `insn', 1 means the insn has been deleted. ! In `label_ref' and `reg_label' expressions, 1 means a reference to a non-local label. ! In `prefetch' expressions, 1 means that the containing insn is a scheduling barrier. ! In an RTL dump, this flag is represented as `/v'.  File: gccint.info, Node: Machine Modes, Next: Constants, Prev: Flags, Up: RTL *************** File: gccint.info, Node: Machine Modes, *** 14623,14991 **** A machine mode describes a size of data object and the representation used for it. In the C code, machine modes are represented by an ! enumeration type, 'machine_mode', defined in 'machmode.def'. Each RTL expression has room for a machine mode and so do certain kinds of tree expressions (declarations and types, to be precise). In debugging dumps and machine descriptions, the machine mode of an RTL expression is written after the expression code with a colon to separate ! them. The letters 'mode' which appear at the end of each machine mode ! name are omitted. For example, '(reg:SI 38)' is a 'reg' expression with ! machine mode 'SImode'. If the mode is 'VOIDmode', it is not written at ! all. Here is a table of machine modes. The term "byte" below refers to an ! object of 'BITS_PER_UNIT' bits (*note Storage Layout::). ! 'BImode' "Bit" mode represents a single bit, for predicate registers. ! 'QImode' "Quarter-Integer" mode represents a single byte treated as an integer. ! 'HImode' "Half-Integer" mode represents a two-byte integer. ! 'PSImode' "Partial Single Integer" mode represents an integer which occupies four bytes but which doesn't really use all four. On some machines, this is the right mode to use for pointers. ! 'SImode' "Single Integer" mode represents a four-byte integer. ! 'PDImode' "Partial Double Integer" mode represents an integer which occupies eight bytes but which doesn't really use all eight. On some machines, this is the right mode to use for certain pointers. ! 'DImode' "Double Integer" mode represents an eight-byte integer. ! 'TImode' ! "Tetra Integer" (?) mode represents a sixteen-byte integer. ! 'OImode' ! "Octa Integer" (?) mode represents a thirty-two-byte integer. ! 'XImode' ! "Hexadeca Integer" (?) mode represents a sixty-four-byte integer. ! 'QFmode' "Quarter-Floating" mode represents a quarter-precision (single byte) floating point number. ! 'HFmode' "Half-Floating" mode represents a half-precision (two byte) floating point number. ! 'TQFmode' ! "Three-Quarter-Floating" (?) mode represents a three-quarter-precision (three byte) floating point number. ! 'SFmode' "Single Floating" mode represents a four byte floating point number. In the common case, of a processor with IEEE arithmetic and 8-bit bytes, this is a single-precision IEEE floating point number; it can also be used for double-precision (on processors with 16-bit bytes) and single-precision VAX and IBM types. ! 'DFmode' "Double Floating" mode represents an eight byte floating point number. In the common case, of a processor with IEEE arithmetic and 8-bit bytes, this is a double-precision IEEE floating point number. ! 'XFmode' "Extended Floating" mode represents an IEEE extended floating point number. This mode only has 80 meaningful bits (ten bytes). Some processors require such numbers to be padded to twelve bytes, others to sixteen; this mode is used for either. ! 'SDmode' "Single Decimal Floating" mode represents a four byte decimal floating point number (as distinct from conventional binary floating point). ! 'DDmode' "Double Decimal Floating" mode represents an eight byte decimal floating point number. ! 'TDmode' "Tetra Decimal Floating" mode represents a sixteen byte decimal floating point number all 128 of whose bits are meaningful. ! 'TFmode' "Tetra Floating" mode represents a sixteen byte floating point number all 128 of whose bits are meaningful. One common use is the IEEE quad-precision format. ! 'QQmode' "Quarter-Fractional" mode represents a single byte treated as a signed fractional number. The default format is "s.7". ! 'HQmode' "Half-Fractional" mode represents a two-byte signed fractional number. The default format is "s.15". ! 'SQmode' "Single Fractional" mode represents a four-byte signed fractional number. The default format is "s.31". ! 'DQmode' ! "Double Fractional" mode represents an eight-byte signed fractional ! number. The default format is "s.63". ! 'TQmode' ! "Tetra Fractional" mode represents a sixteen-byte signed fractional ! number. The default format is "s.127". ! 'UQQmode' ! "Unsigned Quarter-Fractional" mode represents a single byte treated ! as an unsigned fractional number. The default format is ".8". ! 'UHQmode' "Unsigned Half-Fractional" mode represents a two-byte unsigned fractional number. The default format is ".16". ! 'USQmode' "Unsigned Single Fractional" mode represents a four-byte unsigned fractional number. The default format is ".32". ! 'UDQmode' "Unsigned Double Fractional" mode represents an eight-byte unsigned fractional number. The default format is ".64". ! 'UTQmode' "Unsigned Tetra Fractional" mode represents a sixteen-byte unsigned fractional number. The default format is ".128". ! 'HAmode' "Half-Accumulator" mode represents a two-byte signed accumulator. The default format is "s8.7". ! 'SAmode' "Single Accumulator" mode represents a four-byte signed accumulator. The default format is "s16.15". ! 'DAmode' "Double Accumulator" mode represents an eight-byte signed accumulator. The default format is "s32.31". ! 'TAmode' "Tetra Accumulator" mode represents a sixteen-byte signed accumulator. The default format is "s64.63". ! 'UHAmode' "Unsigned Half-Accumulator" mode represents a two-byte unsigned accumulator. The default format is "8.8". ! 'USAmode' "Unsigned Single Accumulator" mode represents a four-byte unsigned accumulator. The default format is "16.16". ! 'UDAmode' "Unsigned Double Accumulator" mode represents an eight-byte unsigned accumulator. The default format is "32.32". ! 'UTAmode' "Unsigned Tetra Accumulator" mode represents a sixteen-byte unsigned accumulator. The default format is "64.64". ! 'CCmode' "Condition Code" mode represents the value of a condition code, which is a machine-specific set of bits used to represent the ! result of a comparison operation. Other machine-specific modes may ! also be used for the condition code. These modes are not used on ! machines that use 'cc0' (*note Condition Code::). ! 'BLKmode' "Block" mode represents values that are aggregates to which none of the other modes apply. In RTL, only memory references can have this mode, and only if they appear in string-move or vector instructions. On machines which have no such instructions, ! 'BLKmode' will not appear in RTL. ! 'VOIDmode' Void mode means the absence of a mode or an unspecified mode. For ! example, RTL expressions of code 'const_int' have mode 'VOIDmode' because they can be taken to have whatever mode the context ! requires. In debugging dumps of RTL, 'VOIDmode' is expressed by the absence of any mode. ! 'QCmode, HCmode, SCmode, DCmode, XCmode, TCmode' These modes stand for a complex number represented as a pair of ! floating point values. The floating point values are in 'QFmode', ! 'HFmode', 'SFmode', 'DFmode', 'XFmode', and 'TFmode', respectively. ! 'CQImode, CHImode, CSImode, CDImode, CTImode, COImode' These modes stand for a complex number represented as a pair of ! integer values. The integer values are in 'QImode', 'HImode', ! 'SImode', 'DImode', 'TImode', and 'OImode', respectively. ! 'BND32mode BND64mode' These modes stand for bounds for pointer of 32 and 64 bit size respectively. Mode size is double pointer mode size. ! The machine description defines 'Pmode' as a C macro which expands into ! the machine mode used for addresses. Normally this is the mode whose ! size is 'BITS_PER_WORD', 'SImode' on 32-bit machines. ! The only modes which a machine description must support are 'QImode', ! and the modes corresponding to 'BITS_PER_WORD', 'FLOAT_TYPE_SIZE' and ! 'DOUBLE_TYPE_SIZE'. The compiler will attempt to use 'DImode' for 8-byte structures and unions, but this can be prevented by overriding ! the definition of 'MAX_FIXED_MODE_SIZE'. Alternatively, you can have ! the compiler use 'TImode' for 16-byte structures and unions. Likewise, ! you can arrange for the C type 'short int' to avoid using 'HImode'. Very few explicit references to machine modes remain in the compiler and these few references will soon be removed. Instead, the machine modes are divided into mode classes. These are represented by the ! enumeration type 'enum mode_class' defined in 'machmode.h'. The possible mode classes are: ! 'MODE_INT' ! Integer modes. By default these are 'BImode', 'QImode', 'HImode', ! 'SImode', 'DImode', 'TImode', and 'OImode'. ! 'MODE_PARTIAL_INT' ! The "partial integer" modes, 'PQImode', 'PHImode', 'PSImode' and ! 'PDImode'. ! 'MODE_FLOAT' ! Floating point modes. By default these are 'QFmode', 'HFmode', ! 'TQFmode', 'SFmode', 'DFmode', 'XFmode' and 'TFmode'. ! 'MODE_DECIMAL_FLOAT' ! Decimal floating point modes. By default these are 'SDmode', ! 'DDmode' and 'TDmode'. ! 'MODE_FRACT' ! Signed fractional modes. By default these are 'QQmode', 'HQmode', ! 'SQmode', 'DQmode' and 'TQmode'. ! 'MODE_UFRACT' ! Unsigned fractional modes. By default these are 'UQQmode', ! 'UHQmode', 'USQmode', 'UDQmode' and 'UTQmode'. ! 'MODE_ACCUM' ! Signed accumulator modes. By default these are 'HAmode', 'SAmode', ! 'DAmode' and 'TAmode'. ! 'MODE_UACCUM' ! Unsigned accumulator modes. By default these are 'UHAmode', ! 'USAmode', 'UDAmode' and 'UTAmode'. ! 'MODE_COMPLEX_INT' Complex integer modes. (These are not currently implemented). ! 'MODE_COMPLEX_FLOAT' ! Complex floating point modes. By default these are 'QCmode', ! 'HCmode', 'SCmode', 'DCmode', 'XCmode', and 'TCmode'. ! 'MODE_FUNCTION' Algol or Pascal function variables including a static chain. (These are not currently implemented). ! 'MODE_CC' ! Modes representing condition code values. These are 'CCmode' plus ! any 'CC_MODE' modes listed in the 'MACHINE-modes.def'. *Note Jump Patterns::, also see *note Condition Code::. ! 'MODE_POINTER_BOUNDS' Pointer bounds modes. Used to represent values of pointer bounds type. Operations in these modes may be executed as NOPs depending on hardware features and environment setup. ! 'MODE_RANDOM' This is a catchall mode class for modes which don't fit into the ! above classes. Currently 'VOIDmode' and 'BLKmode' are in ! 'MODE_RANDOM'. Here are some C macros that relate to machine modes: ! 'GET_MODE (X)' Returns the machine mode of the RTX X. ! 'PUT_MODE (X, NEWMODE)' Alters the machine mode of the RTX X to be NEWMODE. ! 'NUM_MACHINE_MODES' Stands for the number of machine modes available on the target machine. This is one greater than the largest numeric value of any machine mode. ! 'GET_MODE_NAME (M)' Returns the name of mode M as a string. ! 'GET_MODE_CLASS (M)' Returns the mode class of mode M. ! 'GET_MODE_WIDER_MODE (M)' Returns the next wider natural mode. For example, the expression ! 'GET_MODE_WIDER_MODE (QImode)' returns 'HImode'. ! 'GET_MODE_SIZE (M)' Returns the size in bytes of a datum of mode M. ! 'GET_MODE_BITSIZE (M)' Returns the size in bits of a datum of mode M. ! 'GET_MODE_IBIT (M)' Returns the number of integral bits of a datum of fixed-point mode M. ! 'GET_MODE_FBIT (M)' Returns the number of fractional bits of a datum of fixed-point mode M. ! 'GET_MODE_MASK (M)' Returns a bitmask containing 1 for all bits in a word that fit ! within mode M. This macro can only be used for modes whose bitsize ! is less than or equal to 'HOST_BITS_PER_INT'. ! 'GET_MODE_ALIGNMENT (M)' Return the required alignment, in bits, for an object of mode M. ! 'GET_MODE_UNIT_SIZE (M)' Returns the size in bytes of the subunits of a datum of mode M. ! This is the same as 'GET_MODE_SIZE' except in the case of complex modes. For them, the unit size is the size of the real or imaginary part. ! 'GET_MODE_NUNITS (M)' Returns the number of units contained in a mode, i.e., ! 'GET_MODE_SIZE' divided by 'GET_MODE_UNIT_SIZE'. ! 'GET_CLASS_NARROWEST_MODE (C)' Returns the narrowest mode in mode class C. ! The following 3 variables are defined on every target. They can be used to allocate buffers that are guaranteed to be large enough to hold ! any value that can be represented on the target. The first two can be overridden by defining them in the target's mode.def file, however, the value must be a constant that can determined very early in the ! compilation process. The third symbol cannot be overridden. ! 'BITS_PER_UNIT' The number of bits in an addressable storage unit (byte). If you do not define this, the default is 8. ! 'MAX_BITSIZE_MODE_ANY_INT' The maximum bitsize of any mode that is used in integer math. This should be overridden by the target if it uses large integers as ! containers for larger vectors but otherwise never uses the contents ! to compute integer values. ! 'MAX_BITSIZE_MODE_ANY_MODE' The bitsize of the largest mode on the target. ! The global variables 'byte_mode' and 'word_mode' contain modes whose ! classes are 'MODE_INT' and whose bitsizes are either 'BITS_PER_UNIT' or ! 'BITS_PER_WORD', respectively. On 32-bit machines, these are 'QImode' ! and 'SImode', respectively.  File: gccint.info, Node: Constants, Next: Regs and Memory, Prev: Machine Modes, Up: RTL --- 14780,15149 ---- A machine mode describes a size of data object and the representation used for it. In the C code, machine modes are represented by an ! enumeration type, `machine_mode', defined in `machmode.def'. Each RTL expression has room for a machine mode and so do certain kinds of tree expressions (declarations and types, to be precise). In debugging dumps and machine descriptions, the machine mode of an RTL expression is written after the expression code with a colon to separate ! them. The letters `mode' which appear at the end of each machine mode ! name are omitted. For example, `(reg:SI 38)' is a `reg' expression ! with machine mode `SImode'. If the mode is `VOIDmode', it is not ! written at all. Here is a table of machine modes. The term "byte" below refers to an ! object of `BITS_PER_UNIT' bits (*note Storage Layout::). ! `BImode' "Bit" mode represents a single bit, for predicate registers. ! `QImode' "Quarter-Integer" mode represents a single byte treated as an integer. ! `HImode' "Half-Integer" mode represents a two-byte integer. ! `PSImode' "Partial Single Integer" mode represents an integer which occupies four bytes but which doesn't really use all four. On some machines, this is the right mode to use for pointers. ! `SImode' "Single Integer" mode represents a four-byte integer. ! `PDImode' "Partial Double Integer" mode represents an integer which occupies eight bytes but which doesn't really use all eight. On some machines, this is the right mode to use for certain pointers. ! `DImode' "Double Integer" mode represents an eight-byte integer. ! `TImode' ! "Tetra Integer" (?) mode represents a sixteen-byte integer. ! `OImode' ! "Octa Integer" (?) mode represents a thirty-two-byte integer. ! `XImode' ! "Hexadeca Integer" (?) mode represents a sixty-four-byte integer. ! `QFmode' "Quarter-Floating" mode represents a quarter-precision (single byte) floating point number. ! `HFmode' "Half-Floating" mode represents a half-precision (two byte) floating point number. ! `TQFmode' ! "Three-Quarter-Floating" (?) mode represents a three-quarter-precision (three byte) floating point number. ! `SFmode' "Single Floating" mode represents a four byte floating point number. In the common case, of a processor with IEEE arithmetic and 8-bit bytes, this is a single-precision IEEE floating point number; it can also be used for double-precision (on processors with 16-bit bytes) and single-precision VAX and IBM types. ! `DFmode' "Double Floating" mode represents an eight byte floating point number. In the common case, of a processor with IEEE arithmetic and 8-bit bytes, this is a double-precision IEEE floating point number. ! `XFmode' "Extended Floating" mode represents an IEEE extended floating point number. This mode only has 80 meaningful bits (ten bytes). Some processors require such numbers to be padded to twelve bytes, others to sixteen; this mode is used for either. ! `SDmode' "Single Decimal Floating" mode represents a four byte decimal floating point number (as distinct from conventional binary floating point). ! `DDmode' "Double Decimal Floating" mode represents an eight byte decimal floating point number. ! `TDmode' "Tetra Decimal Floating" mode represents a sixteen byte decimal floating point number all 128 of whose bits are meaningful. ! `TFmode' "Tetra Floating" mode represents a sixteen byte floating point number all 128 of whose bits are meaningful. One common use is the IEEE quad-precision format. ! `QQmode' "Quarter-Fractional" mode represents a single byte treated as a signed fractional number. The default format is "s.7". ! `HQmode' "Half-Fractional" mode represents a two-byte signed fractional number. The default format is "s.15". ! `SQmode' "Single Fractional" mode represents a four-byte signed fractional number. The default format is "s.31". ! `DQmode' ! "Double Fractional" mode represents an eight-byte signed ! fractional number. The default format is "s.63". ! `TQmode' ! "Tetra Fractional" mode represents a sixteen-byte signed ! fractional number. The default format is "s.127". ! `UQQmode' ! "Unsigned Quarter-Fractional" mode represents a single byte ! treated as an unsigned fractional number. The default format is ! ".8". ! `UHQmode' "Unsigned Half-Fractional" mode represents a two-byte unsigned fractional number. The default format is ".16". ! `USQmode' "Unsigned Single Fractional" mode represents a four-byte unsigned fractional number. The default format is ".32". ! `UDQmode' "Unsigned Double Fractional" mode represents an eight-byte unsigned fractional number. The default format is ".64". ! `UTQmode' "Unsigned Tetra Fractional" mode represents a sixteen-byte unsigned fractional number. The default format is ".128". ! `HAmode' "Half-Accumulator" mode represents a two-byte signed accumulator. The default format is "s8.7". ! `SAmode' "Single Accumulator" mode represents a four-byte signed accumulator. The default format is "s16.15". ! `DAmode' "Double Accumulator" mode represents an eight-byte signed accumulator. The default format is "s32.31". ! `TAmode' "Tetra Accumulator" mode represents a sixteen-byte signed accumulator. The default format is "s64.63". ! `UHAmode' "Unsigned Half-Accumulator" mode represents a two-byte unsigned accumulator. The default format is "8.8". ! `USAmode' "Unsigned Single Accumulator" mode represents a four-byte unsigned accumulator. The default format is "16.16". ! `UDAmode' "Unsigned Double Accumulator" mode represents an eight-byte unsigned accumulator. The default format is "32.32". ! `UTAmode' "Unsigned Tetra Accumulator" mode represents a sixteen-byte unsigned accumulator. The default format is "64.64". ! `CCmode' "Condition Code" mode represents the value of a condition code, which is a machine-specific set of bits used to represent the ! result of a comparison operation. Other machine-specific modes ! may also be used for the condition code. These modes are not used ! on machines that use `cc0' (*note Condition Code::). ! `BLKmode' "Block" mode represents values that are aggregates to which none of the other modes apply. In RTL, only memory references can have this mode, and only if they appear in string-move or vector instructions. On machines which have no such instructions, ! `BLKmode' will not appear in RTL. ! `VOIDmode' Void mode means the absence of a mode or an unspecified mode. For ! example, RTL expressions of code `const_int' have mode `VOIDmode' because they can be taken to have whatever mode the context ! requires. In debugging dumps of RTL, `VOIDmode' is expressed by the absence of any mode. ! `QCmode, HCmode, SCmode, DCmode, XCmode, TCmode' These modes stand for a complex number represented as a pair of ! floating point values. The floating point values are in `QFmode', ! `HFmode', `SFmode', `DFmode', `XFmode', and `TFmode', respectively. ! `CQImode, CHImode, CSImode, CDImode, CTImode, COImode' These modes stand for a complex number represented as a pair of ! integer values. The integer values are in `QImode', `HImode', ! `SImode', `DImode', `TImode', and `OImode', respectively. ! `BND32mode BND64mode' These modes stand for bounds for pointer of 32 and 64 bit size respectively. Mode size is double pointer mode size. ! The machine description defines `Pmode' as a C macro which expands ! into the machine mode used for addresses. Normally this is the mode ! whose size is `BITS_PER_WORD', `SImode' on 32-bit machines. ! The only modes which a machine description must support are `QImode', ! and the modes corresponding to `BITS_PER_WORD', `FLOAT_TYPE_SIZE' and ! `DOUBLE_TYPE_SIZE'. The compiler will attempt to use `DImode' for 8-byte structures and unions, but this can be prevented by overriding ! the definition of `MAX_FIXED_MODE_SIZE'. Alternatively, you can have ! the compiler use `TImode' for 16-byte structures and unions. Likewise, ! you can arrange for the C type `short int' to avoid using `HImode'. Very few explicit references to machine modes remain in the compiler and these few references will soon be removed. Instead, the machine modes are divided into mode classes. These are represented by the ! enumeration type `enum mode_class' defined in `machmode.h'. The possible mode classes are: ! `MODE_INT' ! Integer modes. By default these are `BImode', `QImode', `HImode', ! `SImode', `DImode', `TImode', and `OImode'. ! `MODE_PARTIAL_INT' ! The "partial integer" modes, `PQImode', `PHImode', `PSImode' and ! `PDImode'. ! `MODE_FLOAT' ! Floating point modes. By default these are `QFmode', `HFmode', ! `TQFmode', `SFmode', `DFmode', `XFmode' and `TFmode'. ! `MODE_DECIMAL_FLOAT' ! Decimal floating point modes. By default these are `SDmode', ! `DDmode' and `TDmode'. ! `MODE_FRACT' ! Signed fractional modes. By default these are `QQmode', `HQmode', ! `SQmode', `DQmode' and `TQmode'. ! `MODE_UFRACT' ! Unsigned fractional modes. By default these are `UQQmode', ! `UHQmode', `USQmode', `UDQmode' and `UTQmode'. ! `MODE_ACCUM' ! Signed accumulator modes. By default these are `HAmode', ! `SAmode', `DAmode' and `TAmode'. ! `MODE_UACCUM' ! Unsigned accumulator modes. By default these are `UHAmode', ! `USAmode', `UDAmode' and `UTAmode'. ! `MODE_COMPLEX_INT' Complex integer modes. (These are not currently implemented). ! `MODE_COMPLEX_FLOAT' ! Complex floating point modes. By default these are `QCmode', ! `HCmode', `SCmode', `DCmode', `XCmode', and `TCmode'. ! `MODE_FUNCTION' Algol or Pascal function variables including a static chain. (These are not currently implemented). ! `MODE_CC' ! Modes representing condition code values. These are `CCmode' plus ! any `CC_MODE' modes listed in the `MACHINE-modes.def'. *Note Jump Patterns::, also see *note Condition Code::. ! `MODE_POINTER_BOUNDS' Pointer bounds modes. Used to represent values of pointer bounds type. Operations in these modes may be executed as NOPs depending on hardware features and environment setup. ! `MODE_RANDOM' This is a catchall mode class for modes which don't fit into the ! above classes. Currently `VOIDmode' and `BLKmode' are in ! `MODE_RANDOM'. Here are some C macros that relate to machine modes: ! `GET_MODE (X)' Returns the machine mode of the RTX X. ! `PUT_MODE (X, NEWMODE)' Alters the machine mode of the RTX X to be NEWMODE. ! `NUM_MACHINE_MODES' Stands for the number of machine modes available on the target machine. This is one greater than the largest numeric value of any machine mode. ! `GET_MODE_NAME (M)' Returns the name of mode M as a string. ! `GET_MODE_CLASS (M)' Returns the mode class of mode M. ! `GET_MODE_WIDER_MODE (M)' Returns the next wider natural mode. For example, the expression ! `GET_MODE_WIDER_MODE (QImode)' returns `HImode'. ! `GET_MODE_SIZE (M)' Returns the size in bytes of a datum of mode M. ! `GET_MODE_BITSIZE (M)' Returns the size in bits of a datum of mode M. ! `GET_MODE_IBIT (M)' Returns the number of integral bits of a datum of fixed-point mode M. ! `GET_MODE_FBIT (M)' Returns the number of fractional bits of a datum of fixed-point mode M. ! `GET_MODE_MASK (M)' Returns a bitmask containing 1 for all bits in a word that fit ! within mode M. This macro can only be used for modes whose ! bitsize is less than or equal to `HOST_BITS_PER_INT'. ! `GET_MODE_ALIGNMENT (M)' Return the required alignment, in bits, for an object of mode M. ! `GET_MODE_UNIT_SIZE (M)' Returns the size in bytes of the subunits of a datum of mode M. ! This is the same as `GET_MODE_SIZE' except in the case of complex modes. For them, the unit size is the size of the real or imaginary part. ! `GET_MODE_NUNITS (M)' Returns the number of units contained in a mode, i.e., ! `GET_MODE_SIZE' divided by `GET_MODE_UNIT_SIZE'. ! `GET_CLASS_NARROWEST_MODE (C)' Returns the narrowest mode in mode class C. ! The following 3 variables are defined on every target. They can be used to allocate buffers that are guaranteed to be large enough to hold ! any value that can be represented on the target. The first two can be overridden by defining them in the target's mode.def file, however, the value must be a constant that can determined very early in the ! compilation process. The third symbol cannot be overridden. ! `BITS_PER_UNIT' The number of bits in an addressable storage unit (byte). If you do not define this, the default is 8. ! `MAX_BITSIZE_MODE_ANY_INT' The maximum bitsize of any mode that is used in integer math. This should be overridden by the target if it uses large integers as ! containers for larger vectors but otherwise never uses the ! contents to compute integer values. ! `MAX_BITSIZE_MODE_ANY_MODE' The bitsize of the largest mode on the target. ! The global variables `byte_mode' and `word_mode' contain modes whose ! classes are `MODE_INT' and whose bitsizes are either `BITS_PER_UNIT' or ! `BITS_PER_WORD', respectively. On 32-bit machines, these are `QImode' ! and `SImode', respectively.  File: gccint.info, Node: Constants, Next: Regs and Memory, Prev: Machine Modes, Up: RTL *************** File: gccint.info, Node: Constants, Ne *** 14995,15159 **** The simplest RTL expressions are those that represent constant values. ! '(const_int I)' This type of expression represents the integer value I. I is ! customarily accessed with the macro 'INTVAL' as in 'INTVAL (EXP)', ! which is equivalent to 'XWINT (EXP, 0)'. Constants generated for modes with fewer bits than in ! 'HOST_WIDE_INT' must be sign extended to full width (e.g., with ! 'gen_int_mode'). For constants for modes with more bits than in ! 'HOST_WIDE_INT' the implied high order bits of that constant are copies of the top bit. Note however that values are neither inherently signed nor inherently unsigned; where necessary, signedness is determined by the rtl operation instead. There is only one expression object for the integer value zero; it ! is the value of the variable 'const0_rtx'. Likewise, the only ! expression for integer value one is found in 'const1_rtx', the only ! expression for integer value two is found in 'const2_rtx', and the only expression for integer value negative one is found in ! 'constm1_rtx'. Any attempt to create an expression of code ! 'const_int' and value zero, one, two or negative one will return ! 'const0_rtx', 'const1_rtx', 'const2_rtx' or 'constm1_rtx' as appropriate. Similarly, there is only one object for the integer whose value is ! 'STORE_FLAG_VALUE'. It is found in 'const_true_rtx'. If ! 'STORE_FLAG_VALUE' is one, 'const_true_rtx' and 'const1_rtx' will ! point to the same object. If 'STORE_FLAG_VALUE' is -1, ! 'const_true_rtx' and 'constm1_rtx' will point to the same object. ! '(const_double:M I0 I1 ...)' This represents either a floating-point constant of mode M or (on ! older ports that do not define 'TARGET_SUPPORTS_WIDE_INT') an ! integer constant too large to fit into 'HOST_BITS_PER_WIDE_INT' bits but small enough to fit within twice that number of bits. In ! the latter case, M will be 'VOIDmode'. For integral values constants for modes with more bits than twice the number in ! 'HOST_WIDE_INT' the implied high order bits of that constant are ! copies of the top bit of 'CONST_DOUBLE_HIGH'. Note however that integral values are neither inherently signed nor inherently unsigned; where necessary, signedness is determined by the rtl operation instead. ! On more modern ports, 'CONST_DOUBLE' only represents floating point ! values. New ports define 'TARGET_SUPPORTS_WIDE_INT' to make this ! designation. ! If M is 'VOIDmode', the bits of the value are stored in I0 and I1. ! I0 is customarily accessed with the macro 'CONST_DOUBLE_LOW' and I1 ! with 'CONST_DOUBLE_HIGH'. If the constant is floating point (regardless of its precision), then the number of integers used to store the value depends on the ! size of 'REAL_VALUE_TYPE' (*note Floating Point::). The integers represent a floating point number, but not precisely in the target ! machine's or host machine's floating point format. To convert them ! to the precise bit pattern used by the target machine, use the ! macro 'REAL_VALUE_TO_TARGET_DOUBLE' and friends (*note Data Output::). ! '(const_wide_int:M NUNITS ELT0 ...)' ! This contains an array of 'HOST_WIDE_INT's that is large enough to hold any constant that can be represented on the target. This form of rtl is only used on targets that define ! 'TARGET_SUPPORTS_WIDE_INT' to be nonzero and then 'CONST_DOUBLE's are only used to hold floating-point values. If the target leaves ! 'TARGET_SUPPORTS_WIDE_INT' defined as 0, 'CONST_WIDE_INT's are not ! used and 'CONST_DOUBLE's are as they were before. The values are stored in a compressed format. The higher-order 0s or -1s are not represented if they are just the logical sign extension of the number that is represented. ! 'CONST_WIDE_INT_VEC (CODE)' ! Returns the entire array of 'HOST_WIDE_INT's that are used to store ! the value. This macro should be rarely used. ! 'CONST_WIDE_INT_NUNITS (CODE)' ! The number of 'HOST_WIDE_INT's used to represent the number. Note ! that this generally is smaller than the number of 'HOST_WIDE_INT's implied by the mode size. ! 'CONST_WIDE_INT_NUNITS (CODE,I)' ! Returns the 'i'th element of the array. Element 0 is contains the ! low order bits of the constant. ! '(const_fixed:M ...)' ! Represents a fixed-point constant of mode M. The operand is a data ! structure of type 'struct fixed_value' and is accessed with the ! macro 'CONST_FIXED_VALUE'. The high part of data is accessed with ! 'CONST_FIXED_VALUE_HIGH'; the low part is accessed with ! 'CONST_FIXED_VALUE_LOW'. ! '(const_vector:M [X0 X1 ...])' Represents a vector constant. The square brackets stand for the vector containing the constant elements. X0, X1 and so on are the ! 'const_int', 'const_double' or 'const_fixed' elements. ! The number of units in a 'const_vector' is obtained with the macro ! 'CONST_VECTOR_NUNITS' as in 'CONST_VECTOR_NUNITS (V)'. Individual elements in a vector constant are accessed with the ! macro 'CONST_VECTOR_ELT' as in 'CONST_VECTOR_ELT (V, N)' where V is ! the vector constant and N is the element desired. ! '(const_string STR)' Represents a constant string with value STR. Currently this is used only for insn attributes (*note Insn Attributes::) since constant strings in C are placed in memory. ! '(symbol_ref:MODE SYMBOL)' Represents the value of an assembler label for data. SYMBOL is a string that describes the name of the assembler label. If it ! starts with a '*', the label is the rest of SYMBOL not including ! the '*'. Otherwise, the label is SYMBOL, usually prefixed with ! '_'. ! The 'symbol_ref' contains a mode, which is usually 'Pmode'. Usually that is the only mode for which a symbol is directly valid. ! '(label_ref:MODE LABEL)' Represents the value of an assembler label for code. It contains ! one operand, an expression, which must be a 'code_label' or a ! 'note' of type 'NOTE_INSN_DELETED_LABEL' that appears in the instruction sequence to identify the place where the label should go. The reason for using a distinct expression type for code label references is so that jump optimization can distinguish them. ! The 'label_ref' contains a mode, which is usually 'Pmode'. Usually ! that is the only mode for which a label is directly valid. ! '(const:M EXP)' Represents a constant that is the result of an assembly-time arithmetic computation. The operand, EXP, is an expression that ! contains only constants ('const_int', 'symbol_ref' and 'label_ref' ! expressions) combined with 'plus' and 'minus'. However, not all combinations are valid, since the assembler cannot do arbitrary arithmetic on relocatable symbols. ! M should be 'Pmode'. ! '(high:M EXP)' ! Represents the high-order bits of EXP, usually a 'symbol_ref'. The ! number of bits is machine-dependent and is normally the number of ! bits specified in an instruction that initializes the high order ! bits of a register. It is used with 'lo_sum' to represent the ! typical two-instruction sequence used in RISC machines to reference ! a global memory location. ! M should be 'Pmode'. ! The macro 'CONST0_RTX (MODE)' refers to an expression with value 0 in ! mode MODE. If mode MODE is of mode class 'MODE_INT', it returns ! 'const0_rtx'. If mode MODE is of mode class 'MODE_FLOAT', it returns a ! 'CONST_DOUBLE' expression in mode MODE. Otherwise, it returns a ! 'CONST_VECTOR' expression in mode MODE. Similarly, the macro ! 'CONST1_RTX (MODE)' refers to an expression with value 1 in mode MODE ! and similarly for 'CONST2_RTX'. The 'CONST1_RTX' and 'CONST2_RTX' macros are undefined for vector modes.  --- 15153,15317 ---- The simplest RTL expressions are those that represent constant values. ! `(const_int I)' This type of expression represents the integer value I. I is ! customarily accessed with the macro `INTVAL' as in `INTVAL (EXP)', ! which is equivalent to `XWINT (EXP, 0)'. Constants generated for modes with fewer bits than in ! `HOST_WIDE_INT' must be sign extended to full width (e.g., with ! `gen_int_mode'). For constants for modes with more bits than in ! `HOST_WIDE_INT' the implied high order bits of that constant are copies of the top bit. Note however that values are neither inherently signed nor inherently unsigned; where necessary, signedness is determined by the rtl operation instead. There is only one expression object for the integer value zero; it ! is the value of the variable `const0_rtx'. Likewise, the only ! expression for integer value one is found in `const1_rtx', the only ! expression for integer value two is found in `const2_rtx', and the only expression for integer value negative one is found in ! `constm1_rtx'. Any attempt to create an expression of code ! `const_int' and value zero, one, two or negative one will return ! `const0_rtx', `const1_rtx', `const2_rtx' or `constm1_rtx' as appropriate. Similarly, there is only one object for the integer whose value is ! `STORE_FLAG_VALUE'. It is found in `const_true_rtx'. If ! `STORE_FLAG_VALUE' is one, `const_true_rtx' and `const1_rtx' will ! point to the same object. If `STORE_FLAG_VALUE' is -1, ! `const_true_rtx' and `constm1_rtx' will point to the same object. ! `(const_double:M I0 I1 ...)' This represents either a floating-point constant of mode M or (on ! older ports that do not define `TARGET_SUPPORTS_WIDE_INT') an ! integer constant too large to fit into `HOST_BITS_PER_WIDE_INT' bits but small enough to fit within twice that number of bits. In ! the latter case, M will be `VOIDmode'. For integral values constants for modes with more bits than twice the number in ! `HOST_WIDE_INT' the implied high order bits of that constant are ! copies of the top bit of `CONST_DOUBLE_HIGH'. Note however that integral values are neither inherently signed nor inherently unsigned; where necessary, signedness is determined by the rtl operation instead. ! On more modern ports, `CONST_DOUBLE' only represents floating ! point values. New ports define `TARGET_SUPPORTS_WIDE_INT' to make ! this designation. ! If M is `VOIDmode', the bits of the value are stored in I0 and I1. ! I0 is customarily accessed with the macro `CONST_DOUBLE_LOW' and ! I1 with `CONST_DOUBLE_HIGH'. If the constant is floating point (regardless of its precision), then the number of integers used to store the value depends on the ! size of `REAL_VALUE_TYPE' (*note Floating Point::). The integers represent a floating point number, but not precisely in the target ! machine's or host machine's floating point format. To convert ! them to the precise bit pattern used by the target machine, use ! the macro `REAL_VALUE_TO_TARGET_DOUBLE' and friends (*note Data Output::). ! `(const_wide_int:M NUNITS ELT0 ...)' ! This contains an array of `HOST_WIDE_INT's that is large enough to hold any constant that can be represented on the target. This form of rtl is only used on targets that define ! `TARGET_SUPPORTS_WIDE_INT' to be nonzero and then `CONST_DOUBLE's are only used to hold floating-point values. If the target leaves ! `TARGET_SUPPORTS_WIDE_INT' defined as 0, `CONST_WIDE_INT's are not ! used and `CONST_DOUBLE's are as they were before. The values are stored in a compressed format. The higher-order 0s or -1s are not represented if they are just the logical sign extension of the number that is represented. ! `CONST_WIDE_INT_VEC (CODE)' ! Returns the entire array of `HOST_WIDE_INT's that are used to ! store the value. This macro should be rarely used. ! `CONST_WIDE_INT_NUNITS (CODE)' ! The number of `HOST_WIDE_INT's used to represent the number. Note ! that this generally is smaller than the number of `HOST_WIDE_INT's implied by the mode size. ! `CONST_WIDE_INT_NUNITS (CODE,I)' ! Returns the `i'th element of the array. Element 0 is contains ! the low order bits of the constant. ! `(const_fixed:M ...)' ! Represents a fixed-point constant of mode M. The operand is a ! data structure of type `struct fixed_value' and is accessed with ! the macro `CONST_FIXED_VALUE'. The high part of data is accessed ! with `CONST_FIXED_VALUE_HIGH'; the low part is accessed with ! `CONST_FIXED_VALUE_LOW'. ! `(const_vector:M [X0 X1 ...])' Represents a vector constant. The square brackets stand for the vector containing the constant elements. X0, X1 and so on are the ! `const_int', `const_double' or `const_fixed' elements. ! The number of units in a `const_vector' is obtained with the macro ! `CONST_VECTOR_NUNITS' as in `CONST_VECTOR_NUNITS (V)'. Individual elements in a vector constant are accessed with the ! macro `CONST_VECTOR_ELT' as in `CONST_VECTOR_ELT (V, N)' where V ! is the vector constant and N is the element desired. ! `(const_string STR)' Represents a constant string with value STR. Currently this is used only for insn attributes (*note Insn Attributes::) since constant strings in C are placed in memory. ! `(symbol_ref:MODE SYMBOL)' Represents the value of an assembler label for data. SYMBOL is a string that describes the name of the assembler label. If it ! starts with a `*', the label is the rest of SYMBOL not including ! the `*'. Otherwise, the label is SYMBOL, usually prefixed with ! `_'. ! The `symbol_ref' contains a mode, which is usually `Pmode'. Usually that is the only mode for which a symbol is directly valid. ! `(label_ref:MODE LABEL)' Represents the value of an assembler label for code. It contains ! one operand, an expression, which must be a `code_label' or a ! `note' of type `NOTE_INSN_DELETED_LABEL' that appears in the instruction sequence to identify the place where the label should go. The reason for using a distinct expression type for code label references is so that jump optimization can distinguish them. ! The `label_ref' contains a mode, which is usually `Pmode'. ! Usually that is the only mode for which a label is directly valid. ! `(const:M EXP)' Represents a constant that is the result of an assembly-time arithmetic computation. The operand, EXP, is an expression that ! contains only constants (`const_int', `symbol_ref' and `label_ref' ! expressions) combined with `plus' and `minus'. However, not all combinations are valid, since the assembler cannot do arbitrary arithmetic on relocatable symbols. ! M should be `Pmode'. ! `(high:M EXP)' ! Represents the high-order bits of EXP, usually a `symbol_ref'. ! The number of bits is machine-dependent and is normally the number ! of bits specified in an instruction that initializes the high ! order bits of a register. It is used with `lo_sum' to represent ! the typical two-instruction sequence used in RISC machines to ! reference a global memory location. ! M should be `Pmode'. ! The macro `CONST0_RTX (MODE)' refers to an expression with value 0 in ! mode MODE. If mode MODE is of mode class `MODE_INT', it returns ! `const0_rtx'. If mode MODE is of mode class `MODE_FLOAT', it returns a ! `CONST_DOUBLE' expression in mode MODE. Otherwise, it returns a ! `CONST_VECTOR' expression in mode MODE. Similarly, the macro ! `CONST1_RTX (MODE)' refers to an expression with value 1 in mode MODE ! and similarly for `CONST2_RTX'. The `CONST1_RTX' and `CONST2_RTX' macros are undefined for vector modes.  *************** File: gccint.info, Node: Regs and Memor *** 15165,15173 **** Here are the RTL expression types for describing access to machine registers and to main memory. ! '(reg:M N)' For small values of the integer N (those that are less than ! 'FIRST_PSEUDO_REGISTER'), this stands for a reference to machine register number N: a "hard register". For larger values of N, it stands for a temporary value or "pseudo register". The compiler's strategy is to generate code assuming an unlimited number of such --- 15323,15331 ---- Here are the RTL expression types for describing access to machine registers and to main memory. ! `(reg:M N)' For small values of the integer N (those that are less than ! `FIRST_PSEUDO_REGISTER'), this stands for a reference to machine register number N: a "hard register". For larger values of N, it stands for a temporary value or "pseudo register". The compiler's strategy is to generate code assuming an unlimited number of such *************** registers and to main memory. *** 15184,15190 **** Even for a register that the machine can access in only one mode, the mode must always be specified. ! The symbol 'FIRST_PSEUDO_REGISTER' is defined by the machine description, since the number of hard registers on the machine is an invariant characteristic of the machine. Note, however, that not all of the machine registers must be general registers. All --- 15342,15348 ---- Even for a register that the machine can access in only one mode, the mode must always be specified. ! The symbol `FIRST_PSEUDO_REGISTER' is defined by the machine description, since the number of hard registers on the machine is an invariant characteristic of the machine. Note, however, that not all of the machine registers must be general registers. All *************** registers and to main memory. *** 15195,15336 **** A hard register may be accessed in various modes throughout one function, but each pseudo register is given a natural mode and is accessed only in that mode. When it is necessary to describe an ! access to a pseudo register using a nonnatural mode, a 'subreg' expression is used. ! A 'reg' expression with a machine mode that specifies more than one ! word of data may actually stand for several consecutive registers. ! If in addition the register number specifies a hardware register, ! then it actually represents several consecutive hardware registers ! starting with the specified one. Each pseudo register number used in a function's RTL code is ! represented by a unique 'reg' expression. Some pseudo register numbers, those within the range of ! 'FIRST_VIRTUAL_REGISTER' to 'LAST_VIRTUAL_REGISTER' only appear during the RTL generation phase and are eliminated before the optimization phases. These represent locations in the stack frame ! that cannot be determined until RTL generation for the function has ! been completed. The following virtual register numbers are defined: ! 'VIRTUAL_INCOMING_ARGS_REGNUM' ! This points to the first word of the incoming arguments passed ! on the stack. Normally these arguments are placed there by ! the caller, but the callee may have pushed some arguments that ! were previously passed in registers. When RTL generation is complete, this virtual register is replaced by the sum of the register given by ! 'ARG_POINTER_REGNUM' and the value of 'FIRST_PARM_OFFSET'. ! 'VIRTUAL_STACK_VARS_REGNUM' ! If 'FRAME_GROWS_DOWNWARD' is defined to a nonzero value, this points to immediately above the first variable on the stack. Otherwise, it points to the first variable on the stack. ! 'VIRTUAL_STACK_VARS_REGNUM' is replaced with the sum of the ! register given by 'FRAME_POINTER_REGNUM' and the value ! 'STARTING_FRAME_OFFSET'. ! 'VIRTUAL_STACK_DYNAMIC_REGNUM' ! This points to the location of dynamically allocated memory on ! the stack immediately after the stack pointer has been adjusted by the amount of memory desired. This virtual register is replaced by the sum of the register ! given by 'STACK_POINTER_REGNUM' and the value ! 'STACK_DYNAMIC_OFFSET'. ! 'VIRTUAL_OUTGOING_ARGS_REGNUM' This points to the location in the stack at which outgoing arguments should be written when the stack is pre-pushed (arguments pushed using push insns should always use ! 'STACK_POINTER_REGNUM'). This virtual register is replaced by the sum of the register ! given by 'STACK_POINTER_REGNUM' and the value ! 'STACK_POINTER_OFFSET'. ! ! '(subreg:M1 REG:M2 BYTENUM)' ! 'subreg' expressions are used to refer to a register in a machine mode other than its natural one, or to refer to one register of a ! multi-part 'reg' that actually refers to several registers. Each pseudo register has a natural mode. If it is necessary to ! operate on it in a different mode, the register must be enclosed in ! a 'subreg'. There are currently three supported types for the first operand of ! a 'subreg': ! * pseudo registers This is the most common case. Most 'subreg's ! have pseudo 'reg's as their first operand. ! * mem 'subreg's of 'mem' were common in earlier versions of GCC and are still supported. During the reload pass these are ! replaced by plain 'mem's. On machines that do not do ! instruction scheduling, use of 'subreg's of 'mem' are still ! used, but this is no longer recommended. Such 'subreg's are ! considered to be 'register_operand's rather than ! 'memory_operand's before and during reload. Because of this, the scheduling passes cannot properly schedule instructions ! with 'subreg's of 'mem', so for machines that do scheduling, ! 'subreg's of 'mem' should never be used. To support this, the ! combine and recog passes have explicit code to inhibit the ! creation of 'subreg's of 'mem' when 'INSN_SCHEDULING' is defined. ! The use of 'subreg's of 'mem' after the reload pass is an area that is not well understood and should be avoided. There is ! still some code in the compiler to support this, but this code ! has possibly rotted. This use of 'subreg's is discouraged and ! will most likely not be supported in the future. * hard registers It is seldom necessary to wrap hard registers ! in 'subreg's; such registers would normally reduce to a single ! 'reg' rtx. This use of 'subreg's is discouraged and may not ! be supported in the future. - 'subreg's of 'subreg's are not supported. Using - 'simplify_gen_subreg' is the recommended way to avoid this problem. ! 'subreg's come in two distinct flavors, each having its own usage and rules: ! Paradoxical subregs ! When M1 is strictly wider than M2, the 'subreg' expression is called "paradoxical". The canonical test for this class of ! 'subreg' is: GET_MODE_SIZE (M1) > GET_MODE_SIZE (M2) ! Paradoxical 'subreg's can be used as both lvalues and rvalues. When used as an lvalue, the low-order bits of the source value ! are stored in REG and the high-order bits are discarded. When ! used as an rvalue, the low-order bits of the 'subreg' are taken from REG while the high-order bits may or may not be defined. The high-order bits of rvalues are in the following circumstances: ! * 'subreg's of 'mem' When M2 is smaller than a word, the ! macro 'LOAD_EXTEND_OP', can control how the high-order bits are defined. ! * 'subreg' of 'reg's The upper bits are defined when ! 'SUBREG_PROMOTED_VAR_P' is true. ! 'SUBREG_PROMOTED_UNSIGNED_P' describes what the upper bits hold. Such subregs usually represent local variables, register variables and parameter pseudo variables that have been promoted to a wider mode. ! BYTENUM is always zero for a paradoxical 'subreg', even on big-endian targets. ! For example, the paradoxical 'subreg': (set (subreg:SI (reg:HI X) 0) Y) --- 15353,15496 ---- A hard register may be accessed in various modes throughout one function, but each pseudo register is given a natural mode and is accessed only in that mode. When it is necessary to describe an ! access to a pseudo register using a nonnatural mode, a `subreg' expression is used. ! A `reg' expression with a machine mode that specifies more than ! one word of data may actually stand for several consecutive ! registers. If in addition the register number specifies a ! hardware register, then it actually represents several consecutive ! hardware registers starting with the specified one. Each pseudo register number used in a function's RTL code is ! represented by a unique `reg' expression. Some pseudo register numbers, those within the range of ! `FIRST_VIRTUAL_REGISTER' to `LAST_VIRTUAL_REGISTER' only appear during the RTL generation phase and are eliminated before the optimization phases. These represent locations in the stack frame ! that cannot be determined until RTL generation for the function ! has been completed. The following virtual register numbers are defined: ! `VIRTUAL_INCOMING_ARGS_REGNUM' ! This points to the first word of the incoming arguments ! passed on the stack. Normally these arguments are placed ! there by the caller, but the callee may have pushed some ! arguments that were previously passed in registers. When RTL generation is complete, this virtual register is replaced by the sum of the register given by ! `ARG_POINTER_REGNUM' and the value of `FIRST_PARM_OFFSET'. ! `VIRTUAL_STACK_VARS_REGNUM' ! If `FRAME_GROWS_DOWNWARD' is defined to a nonzero value, this points to immediately above the first variable on the stack. Otherwise, it points to the first variable on the stack. ! `VIRTUAL_STACK_VARS_REGNUM' is replaced with the sum of the ! register given by `FRAME_POINTER_REGNUM' and the value ! `STARTING_FRAME_OFFSET'. ! `VIRTUAL_STACK_DYNAMIC_REGNUM' ! This points to the location of dynamically allocated memory ! on the stack immediately after the stack pointer has been adjusted by the amount of memory desired. This virtual register is replaced by the sum of the register ! given by `STACK_POINTER_REGNUM' and the value ! `STACK_DYNAMIC_OFFSET'. ! `VIRTUAL_OUTGOING_ARGS_REGNUM' This points to the location in the stack at which outgoing arguments should be written when the stack is pre-pushed (arguments pushed using push insns should always use ! `STACK_POINTER_REGNUM'). This virtual register is replaced by the sum of the register ! given by `STACK_POINTER_REGNUM' and the value ! `STACK_POINTER_OFFSET'. ! `(subreg:M1 REG:M2 BYTENUM)' ! `subreg' expressions are used to refer to a register in a machine mode other than its natural one, or to refer to one register of a ! multi-part `reg' that actually refers to several registers. Each pseudo register has a natural mode. If it is necessary to ! operate on it in a different mode, the register must be enclosed ! in a `subreg'. There are currently three supported types for the first operand of ! a `subreg': ! * pseudo registers This is the most common case. Most ! `subreg's have pseudo `reg's as their first operand. ! * mem `subreg's of `mem' were common in earlier versions of GCC and are still supported. During the reload pass these are ! replaced by plain `mem's. On machines that do not do ! instruction scheduling, use of `subreg's of `mem' are still ! used, but this is no longer recommended. Such `subreg's are ! considered to be `register_operand's rather than ! `memory_operand's before and during reload. Because of this, the scheduling passes cannot properly schedule instructions ! with `subreg's of `mem', so for machines that do scheduling, ! `subreg's of `mem' should never be used. To support this, ! the combine and recog passes have explicit code to inhibit ! the creation of `subreg's of `mem' when `INSN_SCHEDULING' is defined. ! The use of `subreg's of `mem' after the reload pass is an area that is not well understood and should be avoided. There is ! still some code in the compiler to support this, but this ! code has possibly rotted. This use of `subreg's is ! discouraged and will most likely not be supported in the ! future. * hard registers It is seldom necessary to wrap hard registers ! in `subreg's; such registers would normally reduce to a ! single `reg' rtx. This use of `subreg's is discouraged and ! may not be supported in the future. ! `subreg's of `subreg's are not supported. Using ! `simplify_gen_subreg' is the recommended way to avoid this problem. ! ! `subreg's come in two distinct flavors, each having its own usage and rules: ! Paradoxical subregs ! When M1 is strictly wider than M2, the `subreg' expression is called "paradoxical". The canonical test for this class of ! `subreg' is: GET_MODE_SIZE (M1) > GET_MODE_SIZE (M2) ! Paradoxical `subreg's can be used as both lvalues and rvalues. When used as an lvalue, the low-order bits of the source value ! are stored in REG and the high-order bits are discarded. ! When used as an rvalue, the low-order bits of the `subreg' are taken from REG while the high-order bits may or may not be defined. The high-order bits of rvalues are in the following circumstances: ! * `subreg's of `mem' When M2 is smaller than a word, the ! macro `LOAD_EXTEND_OP', can control how the high-order bits are defined. ! * `subreg' of `reg's The upper bits are defined when ! `SUBREG_PROMOTED_VAR_P' is true. ! `SUBREG_PROMOTED_UNSIGNED_P' describes what the upper bits hold. Such subregs usually represent local variables, register variables and parameter pseudo variables that have been promoted to a wider mode. ! ! BYTENUM is always zero for a paradoxical `subreg', even on big-endian targets. ! For example, the paradoxical `subreg': (set (subreg:SI (reg:HI X) 0) Y) *************** registers and to main memory. *** 15340,15465 **** (set Z (subreg:SI (reg:HI X) 0)) would set the lower two bytes of Z to Y and set the upper two ! bytes to an unknown value assuming 'SUBREG_PROMOTED_VAR_P' is false. ! Normal subregs ! When M1 is at least as narrow as M2 the 'subreg' expression is ! called "normal". ! Normal 'subreg's restrict consideration to certain bits of REG. There are two cases. If M1 is smaller than a word, the ! 'subreg' refers to the least-significant part (or "lowpart") of one word of REG. If M1 is word-sized or greater, the ! 'subreg' refers to one or more complete words. ! When used as an lvalue, 'subreg' is a word-based accessor. ! Storing to a 'subreg' modifies all the words of REG that ! overlap the 'subreg', but it leaves the other words of REG alone. ! When storing to a normal 'subreg' that is smaller than a word, the other bits of the referenced word are usually left in an undefined state. This laxity makes it easier to generate efficient code for such instructions. To represent an instruction that preserves all the bits outside of those in ! the 'subreg', use 'strict_low_part' or 'zero_extract' around ! the 'subreg'. BYTENUM must identify the offset of the first byte of the ! 'subreg' from the start of REG, assuming that REG is laid out in memory order. The memory order of bytes is defined by two ! target macros, 'WORDS_BIG_ENDIAN' and 'BYTES_BIG_ENDIAN': ! * 'WORDS_BIG_ENDIAN', if set to 1, says that byte number zero is part of the most significant word; otherwise, it is part of the least significant word. ! * 'BYTES_BIG_ENDIAN', if set to 1, says that byte number zero is the most significant byte within a word; otherwise, it is the least significant byte within a word. ! On a few targets, 'FLOAT_WORDS_BIG_ENDIAN' disagrees with ! 'WORDS_BIG_ENDIAN'. However, most parts of the compiler treat floating point values as if they had the same endianness as ! integer values. This works because they handle them solely as ! a collection of integer values, with no particular numerical ! value. Only real.c and the runtime libraries care about ! 'FLOAT_WORDS_BIG_ENDIAN'. Thus, (subreg:HI (reg:SI X) 2) ! on a 'BYTES_BIG_ENDIAN', 'UNITS_PER_WORD == 4' target is the same as (subreg:HI (reg:SI X) 0) ! on a little-endian, 'UNITS_PER_WORD == 4' target. Both ! 'subreg's access the lower two bytes of register X. ! A 'MODE_PARTIAL_INT' mode behaves as if it were as wide as the ! corresponding 'MODE_INT' mode, except that it has an unknown number ! of undefined bits. For example: (subreg:PSI (reg:SI 0) 0) ! accesses the whole of '(reg:SI 0)', but the exact relationship ! between the 'PSImode' value and the 'SImode' value is not defined. ! If we assume 'UNITS_PER_WORD <= 4', then the following two ! 'subreg's: (subreg:PSI (reg:DI 0) 0) (subreg:PSI (reg:DI 0) 4) ! represent independent 4-byte accesses to the two halves of '(reg:DI ! 0)'. Both 'subreg's have an unknown number of undefined bits. ! If 'UNITS_PER_WORD <= 2' then these two 'subreg's: (subreg:HI (reg:PSI 0) 0) (subreg:HI (reg:PSI 0) 2) represent independent 2-byte accesses that together span the whole ! of '(reg:PSI 0)'. Storing to the first 'subreg' does not affect ! the value of the second, and vice versa. '(reg:PSI 0)' has an unknown number of undefined bits, so the assignment: (set (subreg:HI (reg:PSI 0) 0) (reg:HI 4)) ! does not guarantee that '(subreg:HI (reg:PSI 0) 0)' has the value ! '(reg:HI 4)'. The rules above apply to both pseudo REGs and hard REGs. If the ! semantics are not correct for particular combinations of M1, M2 and ! hard REG, the target-specific code must ensure that those combinations are never used. For example: CANNOT_CHANGE_MODE_CLASS (M2, M1, CLASS) must be true for every class CLASS that includes REG. ! The first operand of a 'subreg' expression is customarily accessed ! with the 'SUBREG_REG' macro and the second operand is customarily ! accessed with the 'SUBREG_BYTE' macro. It has been several years since a platform in which ! 'BYTES_BIG_ENDIAN' not equal to 'WORDS_BIG_ENDIAN' has been tested. ! Anyone wishing to support such a platform in the future may be ! confronted with code rot. ! '(scratch:M)' This represents a scratch register that will be required for the execution of a single instruction and not used subsequently. It is ! converted into a 'reg' by either the local register allocator or the reload pass. ! 'scratch' is usually present inside a 'clobber' operation (*note Side Effects::). ! '(cc0)' This refers to the machine's condition code register. It has no operands and may not have a machine mode. There are two ways to use it: --- 15500,15627 ---- (set Z (subreg:SI (reg:HI X) 0)) would set the lower two bytes of Z to Y and set the upper two ! bytes to an unknown value assuming `SUBREG_PROMOTED_VAR_P' is false. ! Normal subregs ! When M1 is at least as narrow as M2 the `subreg' expression ! is called "normal". ! Normal `subreg's restrict consideration to certain bits of REG. There are two cases. If M1 is smaller than a word, the ! `subreg' refers to the least-significant part (or "lowpart") of one word of REG. If M1 is word-sized or greater, the ! `subreg' refers to one or more complete words. ! When used as an lvalue, `subreg' is a word-based accessor. ! Storing to a `subreg' modifies all the words of REG that ! overlap the `subreg', but it leaves the other words of REG alone. ! When storing to a normal `subreg' that is smaller than a word, the other bits of the referenced word are usually left in an undefined state. This laxity makes it easier to generate efficient code for such instructions. To represent an instruction that preserves all the bits outside of those in ! the `subreg', use `strict_low_part' or `zero_extract' around ! the `subreg'. BYTENUM must identify the offset of the first byte of the ! `subreg' from the start of REG, assuming that REG is laid out in memory order. The memory order of bytes is defined by two ! target macros, `WORDS_BIG_ENDIAN' and `BYTES_BIG_ENDIAN': ! * `WORDS_BIG_ENDIAN', if set to 1, says that byte number zero is part of the most significant word; otherwise, it is part of the least significant word. ! * `BYTES_BIG_ENDIAN', if set to 1, says that byte number zero is the most significant byte within a word; otherwise, it is the least significant byte within a word. ! On a few targets, `FLOAT_WORDS_BIG_ENDIAN' disagrees with ! `WORDS_BIG_ENDIAN'. However, most parts of the compiler treat floating point values as if they had the same endianness as ! integer values. This works because they handle them solely ! as a collection of integer values, with no particular ! numerical value. Only real.c and the runtime libraries care ! about `FLOAT_WORDS_BIG_ENDIAN'. Thus, (subreg:HI (reg:SI X) 2) ! on a `BYTES_BIG_ENDIAN', `UNITS_PER_WORD == 4' target is the same as (subreg:HI (reg:SI X) 0) ! on a little-endian, `UNITS_PER_WORD == 4' target. Both ! `subreg's access the lower two bytes of register X. ! ! A `MODE_PARTIAL_INT' mode behaves as if it were as wide as the ! corresponding `MODE_INT' mode, except that it has an unknown ! number of undefined bits. For example: (subreg:PSI (reg:SI 0) 0) ! accesses the whole of `(reg:SI 0)', but the exact relationship ! between the `PSImode' value and the `SImode' value is not defined. ! If we assume `UNITS_PER_WORD <= 4', then the following two ! `subreg's: (subreg:PSI (reg:DI 0) 0) (subreg:PSI (reg:DI 0) 4) ! represent independent 4-byte accesses to the two halves of ! `(reg:DI 0)'. Both `subreg's have an unknown number of undefined ! bits. ! If `UNITS_PER_WORD <= 2' then these two `subreg's: (subreg:HI (reg:PSI 0) 0) (subreg:HI (reg:PSI 0) 2) represent independent 2-byte accesses that together span the whole ! of `(reg:PSI 0)'. Storing to the first `subreg' does not affect ! the value of the second, and vice versa. `(reg:PSI 0)' has an unknown number of undefined bits, so the assignment: (set (subreg:HI (reg:PSI 0) 0) (reg:HI 4)) ! does not guarantee that `(subreg:HI (reg:PSI 0) 0)' has the value ! `(reg:HI 4)'. The rules above apply to both pseudo REGs and hard REGs. If the ! semantics are not correct for particular combinations of M1, M2 ! and hard REG, the target-specific code must ensure that those combinations are never used. For example: CANNOT_CHANGE_MODE_CLASS (M2, M1, CLASS) must be true for every class CLASS that includes REG. ! The first operand of a `subreg' expression is customarily accessed ! with the `SUBREG_REG' macro and the second operand is customarily ! accessed with the `SUBREG_BYTE' macro. It has been several years since a platform in which ! `BYTES_BIG_ENDIAN' not equal to `WORDS_BIG_ENDIAN' has been ! tested. Anyone wishing to support such a platform in the future ! may be confronted with code rot. ! `(scratch:M)' This represents a scratch register that will be required for the execution of a single instruction and not used subsequently. It is ! converted into a `reg' by either the local register allocator or the reload pass. ! `scratch' is usually present inside a `clobber' operation (*note Side Effects::). ! `(cc0)' This refers to the machine's condition code register. It has no operands and may not have a machine mode. There are two ways to use it: *************** registers and to main memory. *** 15468,15506 **** best on most machines, where each comparison sets the entire series of flags. ! With this technique, '(cc0)' may be validly used in only two contexts: as the destination of an assignment (in test and compare instructions) and in comparison operators comparing ! against zero ('const_int' with value zero; that is to say, ! 'const0_rtx'). * To stand for a single flag that is the result of a single ! condition. This is useful on machines that have only a single ! flag bit, and in which comparison instructions must specify ! the condition to test. ! With this technique, '(cc0)' may be validly used in only two contexts: as the destination of an assignment (in test and compare instructions) where the source is a comparison ! operator, and as the first operand of 'if_then_else' (in a conditional branch). ! There is only one expression object of code 'cc0'; it is the value ! of the variable 'cc0_rtx'. Any attempt to create an expression of ! code 'cc0' will return 'cc0_rtx'. Instructions can set the condition code implicitly. On many machines, nearly all instructions set the condition code based on the value that they compute or store. It is not necessary to record these actions explicitly in the RTL because the machine description includes a prescription for recognizing the ! instructions that do so (by means of the macro 'NOTICE_UPDATE_CC'). ! *Note Condition Code::. Only instructions whose sole purpose is to ! set the condition code, and instructions that use the condition ! code, need mention '(cc0)'. On some machines, the condition code register is given a register ! number and a 'reg' is used instead of '(cc0)'. This is usually the preferable approach if only a small subset of instructions modify the condition code. Other machines store condition codes in general registers; in such cases a pseudo register should be used. --- 15630,15668 ---- best on most machines, where each comparison sets the entire series of flags. ! With this technique, `(cc0)' may be validly used in only two contexts: as the destination of an assignment (in test and compare instructions) and in comparison operators comparing ! against zero (`const_int' with value zero; that is to say, ! `const0_rtx'). * To stand for a single flag that is the result of a single ! condition. This is useful on machines that have only a ! single flag bit, and in which comparison instructions must ! specify the condition to test. ! With this technique, `(cc0)' may be validly used in only two contexts: as the destination of an assignment (in test and compare instructions) where the source is a comparison ! operator, and as the first operand of `if_then_else' (in a conditional branch). ! There is only one expression object of code `cc0'; it is the value ! of the variable `cc0_rtx'. Any attempt to create an expression of ! code `cc0' will return `cc0_rtx'. Instructions can set the condition code implicitly. On many machines, nearly all instructions set the condition code based on the value that they compute or store. It is not necessary to record these actions explicitly in the RTL because the machine description includes a prescription for recognizing the ! instructions that do so (by means of the macro ! `NOTICE_UPDATE_CC'). *Note Condition Code::. Only instructions ! whose sole purpose is to set the condition code, and instructions ! that use the condition code, need mention `(cc0)'. On some machines, the condition code register is given a register ! number and a `reg' is used instead of `(cc0)'. This is usually the preferable approach if only a small subset of instructions modify the condition code. Other machines store condition codes in general registers; in such cases a pseudo register should be used. *************** registers and to main memory. *** 15510,15551 **** the condition code. This is best handled by normally generating the instruction that does not set the condition code, and making a pattern that both performs the arithmetic and sets the condition ! code register (which would not be '(cc0)' in this case). For ! examples, search for 'addcc' and 'andcc' in 'sparc.md'. ! '(pc)' This represents the machine's program counter. It has no operands ! and may not have a machine mode. '(pc)' may be validly used only in certain specific contexts in jump instructions. ! There is only one expression object of code 'pc'; it is the value ! of the variable 'pc_rtx'. Any attempt to create an expression of ! code 'pc' will return 'pc_rtx'. All instructions that do not jump alter the program counter ! implicitly by incrementing it, but there is no need to mention this ! in the RTL. ! '(mem:M ADDR ALIAS)' This RTX represents a reference to main memory at an address represented by the expression ADDR. M specifies how large a unit of memory is accessed. ALIAS specifies an alias set for the reference. In general two items are in different alias sets if they cannot reference the same memory address. ! The construct '(mem:BLK (scratch))' is considered to alias all other memories. Thus it may be used as a memory barrier in epilogue stack deallocation patterns. ! '(concatM RTX RTX)' This RTX represents the concatenation of two other RTXs. This is ! used for complex values. It should only appear in the RTL attached ! to declarations and during RTL generation. It should not appear in ! the ordinary insn chain. ! '(concatnM [RTX ...])' This RTX represents the concatenation of all the RTX to make a ! single value. Like 'concat', this should only appear in declarations, and not in the insn chain.  --- 15672,15713 ---- the condition code. This is best handled by normally generating the instruction that does not set the condition code, and making a pattern that both performs the arithmetic and sets the condition ! code register (which would not be `(cc0)' in this case). For ! examples, search for `addcc' and `andcc' in `sparc.md'. ! `(pc)' This represents the machine's program counter. It has no operands ! and may not have a machine mode. `(pc)' may be validly used only in certain specific contexts in jump instructions. ! There is only one expression object of code `pc'; it is the value ! of the variable `pc_rtx'. Any attempt to create an expression of ! code `pc' will return `pc_rtx'. All instructions that do not jump alter the program counter ! implicitly by incrementing it, but there is no need to mention ! this in the RTL. ! `(mem:M ADDR ALIAS)' This RTX represents a reference to main memory at an address represented by the expression ADDR. M specifies how large a unit of memory is accessed. ALIAS specifies an alias set for the reference. In general two items are in different alias sets if they cannot reference the same memory address. ! The construct `(mem:BLK (scratch))' is considered to alias all other memories. Thus it may be used as a memory barrier in epilogue stack deallocation patterns. ! `(concatM RTX RTX)' This RTX represents the concatenation of two other RTXs. This is ! used for complex values. It should only appear in the RTL ! attached to declarations and during RTL generation. It should not ! appear in the ordinary insn chain. ! `(concatnM [RTX ...])' This RTX represents the concatenation of all the RTX to make a ! single value. Like `concat', this should only appear in declarations, and not in the insn chain.  *************** File: gccint.info, Node: Arithmetic, N *** 15555,15653 **** =================================== Unless otherwise specified, all the operands of arithmetic expressions ! must be valid for mode M. An operand is valid for mode M if it has mode ! M, or if it is a 'const_int' or 'const_double' and M is a mode of class ! 'MODE_INT'. For commutative binary operations, constants should be placed in the second operand. ! '(plus:M X Y)' ! '(ss_plus:M X Y)' ! '(us_plus:M X Y)' ! These three expressions all represent the sum of the values represented by X and Y carried out in machine mode M. They differ ! in their behavior on overflow of integer modes. 'plus' wraps round ! modulo the width of M; 'ss_plus' saturates at the maximum signed ! value representable in M; 'us_plus' saturates at the maximum ! unsigned value. ! ! '(lo_sum:M X Y)' This expression represents the sum of X and the low-order bits of ! Y. It is used with 'high' (*note Constants::) to represent the ! typical two-instruction sequence used in RISC machines to reference ! a global memory location. The number of low order bits is machine-dependent but is normally ! the number of bits in a 'Pmode' item minus the number of bits set ! by 'high'. ! ! M should be 'Pmode'. ! '(minus:M X Y)' ! '(ss_minus:M X Y)' ! '(us_minus:M X Y)' These three expressions represent the result of subtracting Y from X, carried out in mode M. Behavior on overflow is the same as for ! the three variants of 'plus' (see above). ! '(compare:M X Y)' Represents the result of subtracting Y from X for purposes of comparison. The result is computed without overflow, as if with infinite precision. Of course, machines can't really subtract with infinite precision. ! However, they can pretend to do so when only the sign of the result ! will be used, which is the case when the result is stored in the ! condition code. And that is the _only_ way this kind of expression ! may validly be used: as a value to be stored in the condition ! codes, either '(cc0)' or a register. *Note Comparisons::. The mode M is not related to the modes of X and Y, but instead is ! the mode of the condition code value. If '(cc0)' is used, it is ! 'VOIDmode'. Otherwise it is some mode in class 'MODE_CC', often ! 'CCmode'. *Note Condition Code::. If M is 'VOIDmode' or 'CCmode', ! the operation returns sufficient information (in an unspecified ! format) so that any comparison operator can be applied to the ! result of the 'COMPARE' operation. For other modes in class ! 'MODE_CC', the operation only returns a subset of this information. ! Normally, X and Y must have the same mode. Otherwise, 'compare' is ! valid only if the mode of X is in class 'MODE_INT' and Y is a ! 'const_int' or 'const_double' with mode 'VOIDmode'. The mode of X determines what mode the comparison is to be done in; thus it must ! not be 'VOIDmode'. If one of the operands is a constant, it should be placed in the second operand and the comparison code adjusted as appropriate. ! A 'compare' specifying two 'VOIDmode' constants is not valid since there is no way to know in what mode the comparison is to be performed; the comparison must either be folded during the compilation or the first operand must be loaded into a register while its mode is still known. ! '(neg:M X)' ! '(ss_neg:M X)' ! '(us_neg:M X)' These two expressions represent the negation (subtraction from zero) of the value represented by X, carried out in mode M. They differ in the behavior on overflow of integer modes. In the case ! of 'neg', the negation of the operand may be a number not representable in mode M, in which case it is truncated to M. ! 'ss_neg' and 'us_neg' ensure that an out-of-bounds result saturates ! to the maximum or minimum signed or unsigned value. ! '(mult:M X Y)' ! '(ss_mult:M X Y)' ! '(us_mult:M X Y)' Represents the signed product of the values represented by X and Y ! carried out in machine mode M. 'ss_mult' and 'us_mult' ensure that ! an out-of-bounds result saturates to the maximum or minimum signed ! or unsigned value. Some machines support a multiplication that generates a product wider than the operands. Write the pattern for this as --- 15717,15814 ---- =================================== Unless otherwise specified, all the operands of arithmetic expressions ! must be valid for mode M. An operand is valid for mode M if it has ! mode M, or if it is a `const_int' or `const_double' and M is a mode of ! class `MODE_INT'. For commutative binary operations, constants should be placed in the second operand. ! `(plus:M X Y)' ! `(ss_plus:M X Y)' ! `(us_plus:M X Y)' These three expressions all represent the sum of the values represented by X and Y carried out in machine mode M. They differ ! in their behavior on overflow of integer modes. `plus' wraps ! round modulo the width of M; `ss_plus' saturates at the maximum ! signed value representable in M; `us_plus' saturates at the ! maximum unsigned value. + `(lo_sum:M X Y)' This expression represents the sum of X and the low-order bits of ! Y. It is used with `high' (*note Constants::) to represent the ! typical two-instruction sequence used in RISC machines to ! reference a global memory location. The number of low order bits is machine-dependent but is normally ! the number of bits in a `Pmode' item minus the number of bits set ! by `high'. ! M should be `Pmode'. + `(minus:M X Y)' + `(ss_minus:M X Y)' + `(us_minus:M X Y)' These three expressions represent the result of subtracting Y from X, carried out in mode M. Behavior on overflow is the same as for ! the three variants of `plus' (see above). ! `(compare:M X Y)' Represents the result of subtracting Y from X for purposes of comparison. The result is computed without overflow, as if with infinite precision. Of course, machines can't really subtract with infinite precision. ! However, they can pretend to do so when only the sign of the ! result will be used, which is the case when the result is stored ! in the condition code. And that is the _only_ way this kind of ! expression may validly be used: as a value to be stored in the ! condition codes, either `(cc0)' or a register. *Note ! Comparisons::. The mode M is not related to the modes of X and Y, but instead is ! the mode of the condition code value. If `(cc0)' is used, it is ! `VOIDmode'. Otherwise it is some mode in class `MODE_CC', often ! `CCmode'. *Note Condition Code::. If M is `VOIDmode' or ! `CCmode', the operation returns sufficient information (in an ! unspecified format) so that any comparison operator can be applied ! to the result of the `COMPARE' operation. For other modes in ! class `MODE_CC', the operation only returns a subset of this ! information. ! Normally, X and Y must have the same mode. Otherwise, `compare' ! is valid only if the mode of X is in class `MODE_INT' and Y is a ! `const_int' or `const_double' with mode `VOIDmode'. The mode of X determines what mode the comparison is to be done in; thus it must ! not be `VOIDmode'. If one of the operands is a constant, it should be placed in the second operand and the comparison code adjusted as appropriate. ! A `compare' specifying two `VOIDmode' constants is not valid since there is no way to know in what mode the comparison is to be performed; the comparison must either be folded during the compilation or the first operand must be loaded into a register while its mode is still known. ! `(neg:M X)' ! `(ss_neg:M X)' ! `(us_neg:M X)' These two expressions represent the negation (subtraction from zero) of the value represented by X, carried out in mode M. They differ in the behavior on overflow of integer modes. In the case ! of `neg', the negation of the operand may be a number not representable in mode M, in which case it is truncated to M. ! `ss_neg' and `us_neg' ensure that an out-of-bounds result ! saturates to the maximum or minimum signed or unsigned value. ! `(mult:M X Y)' ! `(ss_mult:M X Y)' ! `(us_mult:M X Y)' Represents the signed product of the values represented by X and Y ! carried out in machine mode M. `ss_mult' and `us_mult' ensure ! that an out-of-bounds result saturates to the maximum or minimum ! signed or unsigned value. Some machines support a multiplication that generates a product wider than the operands. Write the pattern for this as *************** second operand. *** 15658,15803 **** same. For unsigned widening multiplication, use the same idiom, but with ! 'zero_extend' instead of 'sign_extend'. ! '(fma:M X Y Z)' ! Represents the 'fma', 'fmaf', and 'fmal' builtin functions, which ! compute 'X * Y + Z' without doing an intermediate rounding step. ! '(div:M X Y)' ! '(ss_div:M X Y)' Represents the quotient in signed division of X by Y, carried out in machine mode M. If M is a floating point mode, it represents ! the exact quotient; otherwise, the integerized quotient. 'ss_div' ensures that an out-of-bounds result saturates to the maximum or minimum signed value. Some machines have division instructions in which the operands and quotient widths are not all the same; you should represent such ! instructions using 'truncate' and 'sign_extend' as in, (truncate:M1 (div:M2 X (sign_extend:M2 Y))) ! '(udiv:M X Y)' ! '(us_div:M X Y)' ! Like 'div' but represents unsigned division. 'us_div' ensures that ! an out-of-bounds result saturates to the maximum or minimum unsigned value. ! '(mod:M X Y)' ! '(umod:M X Y)' ! Like 'div' and 'udiv' but represent the remainder instead of the quotient. ! '(smin:M X Y)' ! '(smax:M X Y)' ! Represents the smaller (for 'smin') or larger (for 'smax') of X and ! Y, interpreted as signed values in mode M. When used with floating ! point, if both operands are zeros, or if either operand is 'NaN', ! then it is unspecified which of the two operands is returned as the ! result. ! '(umin:M X Y)' ! '(umax:M X Y)' ! Like 'smin' and 'smax', but the values are interpreted as unsigned integers. ! '(not:M X)' Represents the bitwise complement of the value represented by X, carried out in mode M, which must be a fixed-point machine mode. ! '(and:M X Y)' Represents the bitwise logical-and of the values represented by X and Y, carried out in machine mode M, which must be a fixed-point machine mode. ! '(ior:M X Y)' Represents the bitwise inclusive-or of the values represented by X and Y, carried out in machine mode M, which must be a fixed-point mode. ! '(xor:M X Y)' Represents the bitwise exclusive-or of the values represented by X and Y, carried out in machine mode M, which must be a fixed-point mode. ! '(ashift:M X C)' ! '(ss_ashift:M X C)' ! '(us_ashift:M X C)' These three expressions represent the result of arithmetically shifting X left by C places. They differ in their behavior on ! overflow of integer modes. An 'ashift' operation is a plain shift with no special behavior in case of a change in the sign bit; ! 'ss_ashift' and 'us_ashift' saturates to the minimum or maximum ! representable value if any of the bits shifted out differs from the ! final sign bit. ! X have mode M, a fixed-point machine mode. C be a fixed-point mode ! or be a constant with mode 'VOIDmode'; which mode is determined by ! the mode called for in the machine description entry for the ! left-shift instruction. For example, on the VAX, the mode of C is ! 'QImode' regardless of M. ! '(lshiftrt:M X C)' ! '(ashiftrt:M X C)' ! Like 'ashift' but for right shift. Unlike the case for left shift, these two operations are distinct. ! '(rotate:M X C)' ! '(rotatert:M X C)' Similar but represent left and right rotate. If C is a constant, ! use 'rotate'. ! '(abs:M X)' ! '(ss_abs:M X)' ! Represents the absolute value of X, computed in mode M. 'ss_abs' ensures that an out-of-bounds result saturates to the maximum signed value. ! '(sqrt:M X)' Represents the square root of X, computed in mode M. Most often M will be a floating point mode. ! '(ffs:M X)' Represents one plus the index of the least significant 1-bit in X, represented as an integer of mode M. (The value is zero if X is ! zero.) The mode of X must be M or 'VOIDmode'. ! '(clrsb:M X)' Represents the number of redundant leading sign bits in X, represented as an integer of mode M, starting at the most significant bit position. This is one less than the number of ! leading sign bits (either 0 or 1), with no special cases. The mode ! of X must be M or 'VOIDmode'. ! '(clz:M X)' Represents the number of leading 0-bits in X, represented as an integer of mode M, starting at the most significant bit position. If X is zero, the value is determined by ! 'CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Note that this is one of the few expressions that is not invariant under widening. The ! mode of X must be M or 'VOIDmode'. ! '(ctz:M X)' Represents the number of trailing 0-bits in X, represented as an integer of mode M, starting at the least significant bit position. If X is zero, the value is determined by ! 'CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Except for this case, ! 'ctz(x)' is equivalent to 'ffs(X) - 1'. The mode of X must be M or ! 'VOIDmode'. ! '(popcount:M X)' Represents the number of 1-bits in X, represented as an integer of ! mode M. The mode of X must be M or 'VOIDmode'. ! '(parity:M X)' Represents the number of 1-bits modulo 2 in X, represented as an ! integer of mode M. The mode of X must be M or 'VOIDmode'. ! '(bswap:M X)' Represents the value X with the order of bytes reversed, carried out in mode M, which must be a fixed-point machine mode. The mode ! of X must be M or 'VOIDmode'.  File: gccint.info, Node: Comparisons, Next: Bit-Fields, Prev: Arithmetic, Up: RTL --- 15819,15965 ---- same. For unsigned widening multiplication, use the same idiom, but with ! `zero_extend' instead of `sign_extend'. ! `(fma:M X Y Z)' ! Represents the `fma', `fmaf', and `fmal' builtin functions, which ! compute `X * Y + Z' without doing an intermediate rounding step. ! `(div:M X Y)' ! `(ss_div:M X Y)' Represents the quotient in signed division of X by Y, carried out in machine mode M. If M is a floating point mode, it represents ! the exact quotient; otherwise, the integerized quotient. `ss_div' ensures that an out-of-bounds result saturates to the maximum or minimum signed value. Some machines have division instructions in which the operands and quotient widths are not all the same; you should represent such ! instructions using `truncate' and `sign_extend' as in, (truncate:M1 (div:M2 X (sign_extend:M2 Y))) ! `(udiv:M X Y)' ! `(us_div:M X Y)' ! Like `div' but represents unsigned division. `us_div' ensures ! that an out-of-bounds result saturates to the maximum or minimum unsigned value. ! `(mod:M X Y)' ! `(umod:M X Y)' ! Like `div' and `udiv' but represent the remainder instead of the quotient. ! `(smin:M X Y)' ! `(smax:M X Y)' ! Represents the smaller (for `smin') or larger (for `smax') of X ! and Y, interpreted as signed values in mode M. When used with ! floating point, if both operands are zeros, or if either operand ! is `NaN', then it is unspecified which of the two operands is ! returned as the result. ! `(umin:M X Y)' ! `(umax:M X Y)' ! Like `smin' and `smax', but the values are interpreted as unsigned integers. ! `(not:M X)' Represents the bitwise complement of the value represented by X, carried out in mode M, which must be a fixed-point machine mode. ! `(and:M X Y)' Represents the bitwise logical-and of the values represented by X and Y, carried out in machine mode M, which must be a fixed-point machine mode. ! `(ior:M X Y)' Represents the bitwise inclusive-or of the values represented by X and Y, carried out in machine mode M, which must be a fixed-point mode. ! `(xor:M X Y)' Represents the bitwise exclusive-or of the values represented by X and Y, carried out in machine mode M, which must be a fixed-point mode. ! `(ashift:M X C)' ! `(ss_ashift:M X C)' ! `(us_ashift:M X C)' These three expressions represent the result of arithmetically shifting X left by C places. They differ in their behavior on ! overflow of integer modes. An `ashift' operation is a plain shift with no special behavior in case of a change in the sign bit; ! `ss_ashift' and `us_ashift' saturates to the minimum or maximum ! representable value if any of the bits shifted out differs from ! the final sign bit. ! X have mode M, a fixed-point machine mode. C be a fixed-point ! mode or be a constant with mode `VOIDmode'; which mode is ! determined by the mode called for in the machine description entry ! for the left-shift instruction. For example, on the VAX, the mode ! of C is `QImode' regardless of M. ! `(lshiftrt:M X C)' ! `(ashiftrt:M X C)' ! Like `ashift' but for right shift. Unlike the case for left shift, these two operations are distinct. ! `(rotate:M X C)' ! `(rotatert:M X C)' Similar but represent left and right rotate. If C is a constant, ! use `rotate'. ! `(abs:M X)' ! ! `(ss_abs:M X)' ! Represents the absolute value of X, computed in mode M. `ss_abs' ensures that an out-of-bounds result saturates to the maximum signed value. ! `(sqrt:M X)' Represents the square root of X, computed in mode M. Most often M will be a floating point mode. ! `(ffs:M X)' Represents one plus the index of the least significant 1-bit in X, represented as an integer of mode M. (The value is zero if X is ! zero.) The mode of X must be M or `VOIDmode'. ! `(clrsb:M X)' Represents the number of redundant leading sign bits in X, represented as an integer of mode M, starting at the most significant bit position. This is one less than the number of ! leading sign bits (either 0 or 1), with no special cases. The ! mode of X must be M or `VOIDmode'. ! `(clz:M X)' Represents the number of leading 0-bits in X, represented as an integer of mode M, starting at the most significant bit position. If X is zero, the value is determined by ! `CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Note that this is one of the few expressions that is not invariant under widening. The ! mode of X must be M or `VOIDmode'. ! `(ctz:M X)' Represents the number of trailing 0-bits in X, represented as an integer of mode M, starting at the least significant bit position. If X is zero, the value is determined by ! `CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::). Except for this case, ! `ctz(x)' is equivalent to `ffs(X) - 1'. The mode of X must be M ! or `VOIDmode'. ! `(popcount:M X)' Represents the number of 1-bits in X, represented as an integer of ! mode M. The mode of X must be M or `VOIDmode'. ! `(parity:M X)' Represents the number of 1-bits modulo 2 in X, represented as an ! integer of mode M. The mode of X must be M or `VOIDmode'. ! `(bswap:M X)' Represents the value X with the order of bytes reversed, carried out in mode M, which must be a fixed-point machine mode. The mode ! of X must be M or `VOIDmode'.  File: gccint.info, Node: Comparisons, Next: Bit-Fields, Prev: Arithmetic, Up: RTL *************** File: gccint.info, Node: Comparisons, *** 15807,15831 **** Comparison operators test a relation on two operands and are considered to represent a machine-dependent nonzero value described by, but not ! necessarily equal to, 'STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or zero if it does not, for comparison operators whose results ! have a 'MODE_INT' mode, 'FLOAT_STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or zero if it does not, for comparison operators that return floating-point values, and a vector of either ! 'VECTOR_STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or of zeros if it does not, for comparison operators that return vector results. The mode of the comparison operation is independent of the mode of the data being compared. If the comparison operation is being ! tested (e.g., the first operand of an 'if_then_else'), the mode must be ! 'VOIDmode'. There are two ways that comparison operations may be used. The ! comparison operators may be used to compare the condition codes '(cc0)' ! against zero, as in '(eq (cc0) (const_int 0))'. Such a construct actually refers to the result of the preceding instruction in which the condition codes were set. The instruction setting the condition code must be adjacent to the instruction using the condition code; only ! 'note' insns may separate them. Alternatively, a comparison operation may directly compare two data objects. The mode of the comparison is determined by the operands; they --- 15969,15993 ---- Comparison operators test a relation on two operands and are considered to represent a machine-dependent nonzero value described by, but not ! necessarily equal to, `STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or zero if it does not, for comparison operators whose results ! have a `MODE_INT' mode, `FLOAT_STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or zero if it does not, for comparison operators that return floating-point values, and a vector of either ! `VECTOR_STORE_FLAG_VALUE' (*note Misc::) if the relation holds, or of zeros if it does not, for comparison operators that return vector results. The mode of the comparison operation is independent of the mode of the data being compared. If the comparison operation is being ! tested (e.g., the first operand of an `if_then_else'), the mode must be ! `VOIDmode'. There are two ways that comparison operations may be used. The ! comparison operators may be used to compare the condition codes `(cc0)' ! against zero, as in `(eq (cc0) (const_int 0))'. Such a construct actually refers to the result of the preceding instruction in which the condition codes were set. The instruction setting the condition code must be adjacent to the instruction using the condition code; only ! `note' insns may separate them. Alternatively, a comparison operation may directly compare two data objects. The mode of the comparison is determined by the operands; they *************** operands constant would be invalid as th *** 15834,15899 **** deduced from it, but such a comparison should never exist in RTL due to constant folding. ! In the example above, if '(cc0)' were last set to '(compare X Y)', the ! comparison operation is identical to '(eq X Y)'. Usually only one style of comparisons is supported on a particular machine, but the combine ! pass will try to merge the operations to produce the 'eq' shown in case it exists in the context of the particular insn involved. Inequality comparisons come in two flavors, signed and unsigned. Thus, ! there are distinct expression codes 'gt' and 'gtu' for signed and unsigned greater-than. These can produce different results for the same pair of integer values: for example, 1 is signed greater-than -1 but not unsigned greater-than, because -1 when regarded as unsigned is actually ! '0xffffffff' which is greater than 1. The signed comparisons are also used for floating point values. ! Floating point comparisons are distinguished by the machine modes of the ! operands. ! '(eq:M X Y)' ! 'STORE_FLAG_VALUE' if the values represented by X and Y are equal, otherwise 0. ! '(ne:M X Y)' ! 'STORE_FLAG_VALUE' if the values represented by X and Y are not equal, otherwise 0. ! '(gt:M X Y)' ! 'STORE_FLAG_VALUE' if the X is greater than Y. If they are fixed-point, the comparison is done in a signed sense. ! '(gtu:M X Y)' ! Like 'gt' but does unsigned comparison, on fixed-point numbers only. ! '(lt:M X Y)' ! '(ltu:M X Y)' ! Like 'gt' and 'gtu' but test for "less than". ! '(ge:M X Y)' ! '(geu:M X Y)' ! Like 'gt' and 'gtu' but test for "greater than or equal". ! '(le:M X Y)' ! '(leu:M X Y)' ! Like 'gt' and 'gtu' but test for "less than or equal". ! '(if_then_else COND THEN ELSE)' This is not a comparison operation but is listed here because it is always used in conjunction with a comparison operation. To be precise, COND is a comparison expression. This expression represents a choice, according to COND, between the value represented by THEN and the one represented by ELSE. ! On most machines, 'if_then_else' expressions are valid only to express conditional jumps. ! '(cond [TEST1 VALUE1 TEST2 VALUE2 ...] DEFAULT)' ! Similar to 'if_then_else', but more general. Each of TEST1, TEST2, ! ... is performed in turn. The result of this expression is the ! VALUE corresponding to the first nonzero test, or DEFAULT if none ! of the tests are nonzero expressions. This is currently not valid for instruction patterns and is supported only for insn attributes. *Note Insn Attributes::. --- 15996,16061 ---- deduced from it, but such a comparison should never exist in RTL due to constant folding. ! In the example above, if `(cc0)' were last set to `(compare X Y)', the ! comparison operation is identical to `(eq X Y)'. Usually only one style of comparisons is supported on a particular machine, but the combine ! pass will try to merge the operations to produce the `eq' shown in case it exists in the context of the particular insn involved. Inequality comparisons come in two flavors, signed and unsigned. Thus, ! there are distinct expression codes `gt' and `gtu' for signed and unsigned greater-than. These can produce different results for the same pair of integer values: for example, 1 is signed greater-than -1 but not unsigned greater-than, because -1 when regarded as unsigned is actually ! `0xffffffff' which is greater than 1. The signed comparisons are also used for floating point values. ! Floating point comparisons are distinguished by the machine modes of ! the operands. ! `(eq:M X Y)' ! `STORE_FLAG_VALUE' if the values represented by X and Y are equal, otherwise 0. ! `(ne:M X Y)' ! `STORE_FLAG_VALUE' if the values represented by X and Y are not equal, otherwise 0. ! `(gt:M X Y)' ! `STORE_FLAG_VALUE' if the X is greater than Y. If they are fixed-point, the comparison is done in a signed sense. ! `(gtu:M X Y)' ! Like `gt' but does unsigned comparison, on fixed-point numbers only. ! `(lt:M X Y)' ! `(ltu:M X Y)' ! Like `gt' and `gtu' but test for "less than". ! `(ge:M X Y)' ! `(geu:M X Y)' ! Like `gt' and `gtu' but test for "greater than or equal". ! `(le:M X Y)' ! `(leu:M X Y)' ! Like `gt' and `gtu' but test for "less than or equal". ! `(if_then_else COND THEN ELSE)' This is not a comparison operation but is listed here because it is always used in conjunction with a comparison operation. To be precise, COND is a comparison expression. This expression represents a choice, according to COND, between the value represented by THEN and the one represented by ELSE. ! On most machines, `if_then_else' expressions are valid only to express conditional jumps. ! `(cond [TEST1 VALUE1 TEST2 VALUE2 ...] DEFAULT)' ! Similar to `if_then_else', but more general. Each of TEST1, ! TEST2, ... is performed in turn. The result of this expression is ! the VALUE corresponding to the first nonzero test, or DEFAULT if ! none of the tests are nonzero expressions. This is currently not valid for instruction patterns and is supported only for insn attributes. *Note Insn Attributes::. *************** File: gccint.info, Node: Bit-Fields, N *** 15906,15939 **** Special expression codes exist to represent bit-field instructions. ! '(sign_extract:M LOC SIZE POS)' This represents a reference to a sign-extended bit-field contained or starting in LOC (a memory or register reference). The bit-field is SIZE bits wide and starts at bit POS. The compilation option ! 'BITS_BIG_ENDIAN' says which end of the memory unit POS counts from. If LOC is in memory, its mode must be a single-byte integer mode. If LOC is in a register, the mode to use is specified by the ! operand of the 'insv' or 'extv' pattern (*note Standard Names::) and is usually a full-word integer mode, which is the default if none is specified. The mode of POS is machine-specific and is also specified in the ! 'insv' or 'extv' pattern. ! The mode M is the same as the mode that would be used for LOC if it ! were a register. ! A 'sign_extract' can not appear as an lvalue, or part thereof, in RTL. ! '(zero_extract:M LOC SIZE POS)' ! Like 'sign_extract' but refers to an unsigned or zero-extended bit-field. The same sequence of bits are extracted, but they are filled to an entire word with zeros instead of by sign-extension. ! Unlike 'sign_extract', this type of expressions can be lvalues in RTL; they may appear on the left side of an assignment, indicating insertion of a value into the specified bit-field. --- 16068,16101 ---- Special expression codes exist to represent bit-field instructions. ! `(sign_extract:M LOC SIZE POS)' This represents a reference to a sign-extended bit-field contained or starting in LOC (a memory or register reference). The bit-field is SIZE bits wide and starts at bit POS. The compilation option ! `BITS_BIG_ENDIAN' says which end of the memory unit POS counts from. If LOC is in memory, its mode must be a single-byte integer mode. If LOC is in a register, the mode to use is specified by the ! operand of the `insv' or `extv' pattern (*note Standard Names::) and is usually a full-word integer mode, which is the default if none is specified. The mode of POS is machine-specific and is also specified in the ! `insv' or `extv' pattern. ! The mode M is the same as the mode that would be used for LOC if ! it were a register. ! A `sign_extract' can not appear as an lvalue, or part thereof, in RTL. ! `(zero_extract:M LOC SIZE POS)' ! Like `sign_extract' but refers to an unsigned or zero-extended bit-field. The same sequence of bits are extracted, but they are filled to an entire word with zeros instead of by sign-extension. ! Unlike `sign_extract', this type of expressions can be lvalues in RTL; they may appear on the left side of an assignment, indicating insertion of a value into the specified bit-field. *************** interpreted as operating on each part of *** 15948,15981 **** Additionally, there are a few new expressions to describe specific vector operations. ! '(vec_merge:M VEC1 VEC2 ITEMS)' This describes a merge operation between two vectors. The result is a vector of mode M; its elements are selected from either VEC1 or VEC2. Which elements are selected is described by ITEMS, which ! is a bit mask represented by a 'const_int'; a zero bit indicates the corresponding element in the result vector is taken from VEC2 while a set bit indicates it is taken from VEC1. ! '(vec_select:M VEC1 SELECTION)' This describes an operation that selects parts of a vector. VEC1 ! is the source vector, and SELECTION is a 'parallel' that contains a ! 'const_int' for each of the subparts of the result vector, giving the number of the source subpart that should be stored into it. The result mode M is either the submode for a single element of ! VEC1 (if only one subpart is selected), or another vector mode with ! that element submode (if multiple subparts are selected). ! '(vec_concat:M X1 X2)' ! Describes a vector concat operation. The result is a concatenation ! of the vectors or scalars X1 and X2; its length is the sum of the ! lengths of the two inputs. ! '(vec_duplicate:M X)' This operation converts a scalar into a vector or a small vector into a larger one by duplicating the input values. The output ! vector mode must have the same submodes as the input vector mode or ! the scalar modes, and the number of output parts must be an integer ! multiple of the number of input parts.  File: gccint.info, Node: Conversions, Next: RTL Declarations, Prev: Vector Operations, Up: RTL --- 16110,16144 ---- Additionally, there are a few new expressions to describe specific vector operations. ! `(vec_merge:M VEC1 VEC2 ITEMS)' This describes a merge operation between two vectors. The result is a vector of mode M; its elements are selected from either VEC1 or VEC2. Which elements are selected is described by ITEMS, which ! is a bit mask represented by a `const_int'; a zero bit indicates the corresponding element in the result vector is taken from VEC2 while a set bit indicates it is taken from VEC1. ! `(vec_select:M VEC1 SELECTION)' This describes an operation that selects parts of a vector. VEC1 ! is the source vector, and SELECTION is a `parallel' that contains a ! `const_int' for each of the subparts of the result vector, giving the number of the source subpart that should be stored into it. The result mode M is either the submode for a single element of ! VEC1 (if only one subpart is selected), or another vector mode ! with that element submode (if multiple subparts are selected). ! `(vec_concat:M X1 X2)' ! Describes a vector concat operation. The result is a ! concatenation of the vectors or scalars X1 and X2; its length is ! the sum of the lengths of the two inputs. ! `(vec_duplicate:M X)' This operation converts a scalar into a vector or a small vector into a larger one by duplicating the input values. The output ! vector mode must have the same submodes as the input vector mode ! or the scalar modes, and the number of output parts must be an ! integer multiple of the number of input parts. !  File: gccint.info, Node: Conversions, Next: RTL Declarations, Prev: Vector Operations, Up: RTL *************** File: gccint.info, Node: Conversions, *** 15984,15993 **** ================= All conversions between machine modes must be represented by explicit ! conversion operations. For example, an expression which is the sum of a ! byte and a full word cannot be written as '(plus:SI (reg:QI 34) (reg:SI ! 80))' because the 'plus' operation requires two operands of the same ! machine mode. Therefore, the byte-sized operand is enclosed in a conversion operation, as in (plus:SI (sign_extend:SI (reg:QI 34)) (reg:SI 80)) --- 16147,16156 ---- ================= All conversions between machine modes must be represented by explicit ! conversion operations. For example, an expression which is the sum of ! a byte and a full word cannot be written as `(plus:SI (reg:QI 34) ! (reg:SI 80))' because the `plus' operation requires two operands of the ! same machine mode. Therefore, the byte-sized operand is enclosed in a conversion operation, as in (plus:SI (sign_extend:SI (reg:QI 34)) (reg:SI 80)) *************** conversion operation, as in *** 15996,16065 **** be more than one way of converting from a given starting mode to the desired final mode. The conversion operation code says how to do it. ! For all conversion operations, X must not be 'VOIDmode' because the mode in which to do the conversion would not be known. The conversion must either be done at compile-time or X must be placed into a register. ! '(sign_extend:M X)' ! Represents the result of sign-extending the value X to machine mode ! M. M must be a fixed-point mode and X a fixed-point value of a ! mode narrower than M. ! '(zero_extend:M X)' ! Represents the result of zero-extending the value X to machine mode ! M. M must be a fixed-point mode and X a fixed-point value of a ! mode narrower than M. ! '(float_extend:M X)' Represents the result of extending the value X to machine mode M. M must be a floating point mode and X a floating point value of a mode narrower than M. ! '(truncate:M X)' Represents the result of truncating the value X to machine mode M. M must be a fixed-point mode and X a fixed-point value of a mode wider than M. ! '(ss_truncate:M X)' Represents the result of truncating the value X to machine mode M, using signed saturation in the case of overflow. Both M and the mode of X must be fixed-point modes. ! '(us_truncate:M X)' Represents the result of truncating the value X to machine mode M, using unsigned saturation in the case of overflow. Both M and the mode of X must be fixed-point modes. ! '(float_truncate:M X)' Represents the result of truncating the value X to machine mode M. M must be a floating point mode and X a floating point value of a mode wider than M. ! '(float:M X)' Represents the result of converting fixed point value X, regarded as signed, to floating point mode M. ! '(unsigned_float:M X)' Represents the result of converting fixed point value X, regarded as unsigned, to floating point mode M. ! '(fix:M X)' When M is a floating-point mode, represents the result of ! converting floating point value X (valid for mode M) to an integer, ! still represented in floating point mode M, by rounding towards ! zero. When M is a fixed-point mode, represents the result of converting ! floating point value X to mode M, regarded as signed. How rounding ! is done is not specified, so this operation may be used validly in ! compiling C code only for integer-valued operands. ! '(unsigned_fix:M X)' ! Represents the result of converting floating point value X to fixed ! point mode M, regarded as unsigned. How rounding is done is not ! specified. ! '(fract_convert:M X)' Represents the result of converting fixed-point value X to fixed-point mode M, signed integer value X to fixed-point mode M, floating-point value X to fixed-point mode M, fixed-point value X --- 16159,16228 ---- be more than one way of converting from a given starting mode to the desired final mode. The conversion operation code says how to do it. ! For all conversion operations, X must not be `VOIDmode' because the mode in which to do the conversion would not be known. The conversion must either be done at compile-time or X must be placed into a register. ! `(sign_extend:M X)' ! Represents the result of sign-extending the value X to machine ! mode M. M must be a fixed-point mode and X a fixed-point value of ! a mode narrower than M. ! `(zero_extend:M X)' ! Represents the result of zero-extending the value X to machine ! mode M. M must be a fixed-point mode and X a fixed-point value of ! a mode narrower than M. ! `(float_extend:M X)' Represents the result of extending the value X to machine mode M. M must be a floating point mode and X a floating point value of a mode narrower than M. ! `(truncate:M X)' Represents the result of truncating the value X to machine mode M. M must be a fixed-point mode and X a fixed-point value of a mode wider than M. ! `(ss_truncate:M X)' Represents the result of truncating the value X to machine mode M, using signed saturation in the case of overflow. Both M and the mode of X must be fixed-point modes. ! `(us_truncate:M X)' Represents the result of truncating the value X to machine mode M, using unsigned saturation in the case of overflow. Both M and the mode of X must be fixed-point modes. ! `(float_truncate:M X)' Represents the result of truncating the value X to machine mode M. M must be a floating point mode and X a floating point value of a mode wider than M. ! `(float:M X)' Represents the result of converting fixed point value X, regarded as signed, to floating point mode M. ! `(unsigned_float:M X)' Represents the result of converting fixed point value X, regarded as unsigned, to floating point mode M. ! `(fix:M X)' When M is a floating-point mode, represents the result of ! converting floating point value X (valid for mode M) to an ! integer, still represented in floating point mode M, by rounding ! towards zero. When M is a fixed-point mode, represents the result of converting ! floating point value X to mode M, regarded as signed. How ! rounding is done is not specified, so this operation may be used ! validly in compiling C code only for integer-valued operands. ! `(unsigned_fix:M X)' ! Represents the result of converting floating point value X to ! fixed point mode M, regarded as unsigned. How rounding is done is ! not specified. ! `(fract_convert:M X)' Represents the result of converting fixed-point value X to fixed-point mode M, signed integer value X to fixed-point mode M, floating-point value X to fixed-point mode M, fixed-point value X *************** must either be done at compile-time or X *** 16067,16086 **** floating-point mode M. When overflows or underflows happen, the results are undefined. ! '(sat_fract:M X)' Represents the result of converting fixed-point value X to fixed-point mode M, signed integer value X to fixed-point mode M, ! or floating-point value X to fixed-point mode M. When overflows or ! underflows happen, the results are saturated to the maximum or the ! minimum. ! '(unsigned_fract_convert:M X)' Represents the result of converting fixed-point value X to integer mode M regarded as unsigned, or unsigned integer value X to fixed-point mode M. When overflows or underflows happen, the results are undefined. ! '(unsigned_sat_fract:M X)' Represents the result of converting unsigned integer value X to fixed-point mode M. When overflows or underflows happen, the results are saturated to the maximum or the minimum. --- 16230,16249 ---- floating-point mode M. When overflows or underflows happen, the results are undefined. ! `(sat_fract:M X)' Represents the result of converting fixed-point value X to fixed-point mode M, signed integer value X to fixed-point mode M, ! or floating-point value X to fixed-point mode M. When overflows ! or underflows happen, the results are saturated to the maximum or ! the minimum. ! `(unsigned_fract_convert:M X)' Represents the result of converting fixed-point value X to integer mode M regarded as unsigned, or unsigned integer value X to fixed-point mode M. When overflows or underflows happen, the results are undefined. ! `(unsigned_sat_fract:M X)' Represents the result of converting unsigned integer value X to fixed-point mode M. When overflows or underflows happen, the results are saturated to the maximum or the minimum. *************** File: gccint.info, Node: RTL Declaratio *** 16094,16106 **** Declaration expression codes do not represent arithmetic operations but rather state assertions about their operands. ! '(strict_low_part (subreg:M (reg:N R) 0))' This expression code is used in only one context: as the ! destination operand of a 'set' expression. In addition, the ! operand of this expression must be a non-paradoxical 'subreg' expression. ! The presence of 'strict_low_part' says that the part of the register which is meaningful in mode N, but is not part of mode M, is not to be altered. Normally, an assignment to such a subreg is allowed to have undefined effects on the rest of the register when --- 16257,16269 ---- Declaration expression codes do not represent arithmetic operations but rather state assertions about their operands. ! `(strict_low_part (subreg:M (reg:N R) 0))' This expression code is used in only one context: as the ! destination operand of a `set' expression. In addition, the ! operand of this expression must be a non-paradoxical `subreg' expression. ! The presence of `strict_low_part' says that the part of the register which is meaningful in mode N, but is not part of mode M, is not to be altered. Normally, an assignment to such a subreg is allowed to have undefined effects on the rest of the register when *************** codes are used to represent side effects *** 16121,16245 **** the codes described above, which represent values, appear only as the operands of these. ! '(set LVAL X)' Represents the action of storing the value of X into the place represented by LVAL. LVAL must be an expression representing a ! place that can be stored in: 'reg' (or 'subreg', 'strict_low_part' ! or 'zero_extract'), 'mem', 'pc', 'parallel', or 'cc0'. ! If LVAL is a 'reg', 'subreg' or 'mem', it has a machine mode; then X must be valid for that mode. ! If LVAL is a 'reg' whose machine mode is less than the full width of the register, then it means that the part of the register specified by the machine mode is given the specified value and the rest of the register receives an undefined value. Likewise, if ! LVAL is a 'subreg' whose machine mode is narrower than the mode of the register, the rest of the register can be changed in an undefined way. ! If LVAL is a 'strict_low_part' of a subreg, then the part of the ! register specified by the machine mode of the 'subreg' is given the ! value X and the rest of the register is not changed. ! If LVAL is a 'zero_extract', then the referenced part of the bit-field (a memory or register reference) specified by the ! 'zero_extract' is given the value X and the rest of the bit-field ! is not changed. Note that 'sign_extract' can not appear in LVAL. ! If LVAL is '(cc0)', it has no machine mode, and X may be either a ! 'compare' expression or a value that may have any mode. The latter ! case represents a "test" instruction. The expression '(set (cc0) ! (reg:M N))' is equivalent to '(set (cc0) (compare (reg:M N) (const_int 0)))'. Use the former expression to save space during the compilation. ! If LVAL is a 'parallel', it is used to represent the case of a function returning a structure in multiple registers. Each element ! of the 'parallel' is an 'expr_list' whose first operand is a 'reg' ! and whose second operand is a 'const_int' representing the offset (in bytes) into the structure at which the data in that register corresponds. The first element may be null to indicate that the structure is also passed partly in memory. ! If LVAL is '(pc)', we have a jump instruction, and the ! possibilities for X are very limited. It may be a 'label_ref' ! expression (unconditional jump). It may be an 'if_then_else' (conditional jump), in which case either the second or the third ! operand must be '(pc)' (for the case which does not jump) and the ! other of the two must be a 'label_ref' (for the case which does ! jump). X may also be a 'mem' or '(plus:SI (pc) Y)', where Y may be ! a 'reg' or a 'mem'; these unusual patterns are used to represent ! jumps through branch tables. ! If LVAL is neither '(cc0)' nor '(pc)', the mode of LVAL must not be ! 'VOIDmode' and the mode of X must be valid for the mode of LVAL. ! LVAL is customarily accessed with the 'SET_DEST' macro and X with ! the 'SET_SRC' macro. ! '(return)' As the sole expression in a pattern, represents a return from the current function, on machines where this can be done with one instruction, such as VAXen. On machines where a multi-instruction "epilogue" must be executed in order to return from the function, returning is done by jumping to a label which precedes the ! epilogue, and the 'return' expression code is never used. ! Inside an 'if_then_else' expression, represents the value to be ! placed in 'pc' to return to the caller. ! Note that an insn pattern of '(return)' is logically equivalent to ! '(set (pc) (return))', but the latter form is never used. ! '(simple_return)' ! Like '(return)', but truly represents only a function return, while ! '(return)' may represent an insn that also performs other functions ! of the function epilogue. Like '(return)', this may also occur in conditional jumps. ! '(call FUNCTION NARGS)' ! Represents a function call. FUNCTION is a 'mem' expression whose address is the address of the function to be called. NARGS is an expression which can be used for two purposes: on some machines it represents the number of bytes of stack argument; on others, it represents the number of argument registers. Each machine has a standard machine mode which FUNCTION must have. ! The machine description defines macro 'FUNCTION_MODE' to expand into the requisite mode name. The purpose of this mode is to specify what kind of addressing is allowed, on machines where the allowed kinds of addressing depend on the machine mode being addressed. ! '(clobber X)' Represents the storing or possible storing of an unpredictable, ! undescribed value into X, which must be a 'reg', 'scratch', ! 'parallel' or 'mem' expression. One place this is used is in string instructions that store standard values into particular hard registers. It may not be ! worth the trouble to describe the values that are stored, but it is ! essential to inform the compiler that the registers will be altered, lest it attempt to keep data in them across the string instruction. ! If X is '(mem:BLK (const_int 0))' or '(mem:BLK (scratch))', it means that all memory locations must be presumed clobbered. If X ! is a 'parallel', it has the same meaning as a 'parallel' in a 'set' ! expression. ! Note that the machine description classifies certain hard registers ! as "call-clobbered". All function call instructions are assumed by ! default to clobber these registers, so there is no need to use ! 'clobber' expressions to indicate this fact. Also, each function ! call is assumed to have the potential to alter any memory location, ! unless the function is declared 'const'. ! If the last group of expressions in a 'parallel' are each a ! 'clobber' expression whose arguments are 'reg' or 'match_scratch' (*note RTL Template::) expressions, the combiner phase can add the ! appropriate 'clobber' expressions to an insn it has constructed when doing so will cause a pattern to be matched. This feature can be used, for example, on a machine that whose --- 16284,16408 ---- the codes described above, which represent values, appear only as the operands of these. ! `(set LVAL X)' Represents the action of storing the value of X into the place represented by LVAL. LVAL must be an expression representing a ! place that can be stored in: `reg' (or `subreg', `strict_low_part' ! or `zero_extract'), `mem', `pc', `parallel', or `cc0'. ! If LVAL is a `reg', `subreg' or `mem', it has a machine mode; then X must be valid for that mode. ! If LVAL is a `reg' whose machine mode is less than the full width of the register, then it means that the part of the register specified by the machine mode is given the specified value and the rest of the register receives an undefined value. Likewise, if ! LVAL is a `subreg' whose machine mode is narrower than the mode of the register, the rest of the register can be changed in an undefined way. ! If LVAL is a `strict_low_part' of a subreg, then the part of the ! register specified by the machine mode of the `subreg' is given ! the value X and the rest of the register is not changed. ! If LVAL is a `zero_extract', then the referenced part of the bit-field (a memory or register reference) specified by the ! `zero_extract' is given the value X and the rest of the bit-field ! is not changed. Note that `sign_extract' can not appear in LVAL. ! If LVAL is `(cc0)', it has no machine mode, and X may be either a ! `compare' expression or a value that may have any mode. The ! latter case represents a "test" instruction. The expression `(set ! (cc0) (reg:M N))' is equivalent to `(set (cc0) (compare (reg:M N) (const_int 0)))'. Use the former expression to save space during the compilation. ! If LVAL is a `parallel', it is used to represent the case of a function returning a structure in multiple registers. Each element ! of the `parallel' is an `expr_list' whose first operand is a `reg' ! and whose second operand is a `const_int' representing the offset (in bytes) into the structure at which the data in that register corresponds. The first element may be null to indicate that the structure is also passed partly in memory. ! If LVAL is `(pc)', we have a jump instruction, and the ! possibilities for X are very limited. It may be a `label_ref' ! expression (unconditional jump). It may be an `if_then_else' (conditional jump), in which case either the second or the third ! operand must be `(pc)' (for the case which does not jump) and the ! other of the two must be a `label_ref' (for the case which does ! jump). X may also be a `mem' or `(plus:SI (pc) Y)', where Y may ! be a `reg' or a `mem'; these unusual patterns are used to ! represent jumps through branch tables. ! If LVAL is neither `(cc0)' nor `(pc)', the mode of LVAL must not ! be `VOIDmode' and the mode of X must be valid for the mode of LVAL. ! LVAL is customarily accessed with the `SET_DEST' macro and X with ! the `SET_SRC' macro. ! `(return)' As the sole expression in a pattern, represents a return from the current function, on machines where this can be done with one instruction, such as VAXen. On machines where a multi-instruction "epilogue" must be executed in order to return from the function, returning is done by jumping to a label which precedes the ! epilogue, and the `return' expression code is never used. ! Inside an `if_then_else' expression, represents the value to be ! placed in `pc' to return to the caller. ! Note that an insn pattern of `(return)' is logically equivalent to ! `(set (pc) (return))', but the latter form is never used. ! `(simple_return)' ! Like `(return)', but truly represents only a function return, while ! `(return)' may represent an insn that also performs other functions ! of the function epilogue. Like `(return)', this may also occur in conditional jumps. ! `(call FUNCTION NARGS)' ! Represents a function call. FUNCTION is a `mem' expression whose address is the address of the function to be called. NARGS is an expression which can be used for two purposes: on some machines it represents the number of bytes of stack argument; on others, it represents the number of argument registers. Each machine has a standard machine mode which FUNCTION must have. ! The machine description defines macro `FUNCTION_MODE' to expand into the requisite mode name. The purpose of this mode is to specify what kind of addressing is allowed, on machines where the allowed kinds of addressing depend on the machine mode being addressed. ! `(clobber X)' Represents the storing or possible storing of an unpredictable, ! undescribed value into X, which must be a `reg', `scratch', ! `parallel' or `mem' expression. One place this is used is in string instructions that store standard values into particular hard registers. It may not be ! worth the trouble to describe the values that are stored, but it ! is essential to inform the compiler that the registers will be altered, lest it attempt to keep data in them across the string instruction. ! If X is `(mem:BLK (const_int 0))' or `(mem:BLK (scratch))', it means that all memory locations must be presumed clobbered. If X ! is a `parallel', it has the same meaning as a `parallel' in a ! `set' expression. ! Note that the machine description classifies certain hard ! registers as "call-clobbered". All function call instructions are ! assumed by default to clobber these registers, so there is no need ! to use `clobber' expressions to indicate this fact. Also, each ! function call is assumed to have the potential to alter any memory ! location, unless the function is declared `const'. ! If the last group of expressions in a `parallel' are each a ! `clobber' expression whose arguments are `reg' or `match_scratch' (*note RTL Template::) expressions, the combiner phase can add the ! appropriate `clobber' expressions to an insn it has constructed when doing so will cause a pattern to be matched. This feature can be used, for example, on a machine that whose *************** operands of these. *** 16248,16290 **** register. Similarly, a combined instruction might require a temporary register while the constituent instructions might not. ! When a 'clobber' expression for a register appears inside a ! 'parallel' with other side effects, the register allocator guarantees that the register is unoccupied both before and after that insn if it is a hard register clobber. For pseudo-register clobber, the register allocator and the reload pass do not assign the same hard register to the clobber and the input operands if ! there is an insn alternative containing the '&' constraint (*note Modifiers::) for the clobber and the hard register is in register classes of the clobber in the alternative. You can clobber either ! a specific hard register, a pseudo register, or a 'scratch' expression; in the latter two cases, GCC will allocate a hard register that is available there for use as a temporary. For instructions that require a temporary register, you should use ! 'scratch' instead of a pseudo-register because this will allow the ! combiner phase to add the 'clobber' when required. You do this by ! coding ('clobber' ('match_scratch' ...)). If you do clobber a ! pseudo register, use one which appears nowhere else--generate a new ! one each time. Otherwise, you may confuse CSE. There is one other known use for clobbering a pseudo register in a ! 'parallel': when one of the input operands of the insn is also clobbered by the insn. In this case, using the same pseudo register in the clobber and elsewhere in the insn produces the expected results. ! '(use X)' Represents the use of the value of X. It indicates that the value ! in X at this point in the program is needed, even though it may not ! be apparent why this is so. Therefore, the compiler will not attempt to delete previous instructions whose only effect is to ! store a value in X. X must be a 'reg' expression. ! In some situations, it may be tempting to add a 'use' of a register ! in a 'parallel' to describe a situation where the value of a ! special register will modify the behavior of the instruction. A ! hypothetical example might be a pattern for an addition that can either wrap around or use saturating addition depending on the value of a special control register: --- 16411,16453 ---- register. Similarly, a combined instruction might require a temporary register while the constituent instructions might not. ! When a `clobber' expression for a register appears inside a ! `parallel' with other side effects, the register allocator guarantees that the register is unoccupied both before and after that insn if it is a hard register clobber. For pseudo-register clobber, the register allocator and the reload pass do not assign the same hard register to the clobber and the input operands if ! there is an insn alternative containing the `&' constraint (*note Modifiers::) for the clobber and the hard register is in register classes of the clobber in the alternative. You can clobber either ! a specific hard register, a pseudo register, or a `scratch' expression; in the latter two cases, GCC will allocate a hard register that is available there for use as a temporary. For instructions that require a temporary register, you should use ! `scratch' instead of a pseudo-register because this will allow the ! combiner phase to add the `clobber' when required. You do this by ! coding (`clobber' (`match_scratch' ...)). If you do clobber a ! pseudo register, use one which appears nowhere else--generate a ! new one each time. Otherwise, you may confuse CSE. There is one other known use for clobbering a pseudo register in a ! `parallel': when one of the input operands of the insn is also clobbered by the insn. In this case, using the same pseudo register in the clobber and elsewhere in the insn produces the expected results. ! `(use X)' Represents the use of the value of X. It indicates that the value ! in X at this point in the program is needed, even though it may ! not be apparent why this is so. Therefore, the compiler will not attempt to delete previous instructions whose only effect is to ! store a value in X. X must be a `reg' expression. ! In some situations, it may be tempting to add a `use' of a ! register in a `parallel' to describe a situation where the value ! of a special register will modify the behavior of the instruction. ! A hypothetical example might be a pattern for an addition that can either wrap around or use saturating addition depending on the value of a special control register: *************** operands of these. *** 16292,16327 **** (reg:SI 4)] 0)) (use (reg:SI 1))]) - This will not work, several of the optimizers only look at expressions locally; it is very likely that if you have multiple ! insns with identical inputs to the 'unspec', they will be optimized ! away even if register 1 changes in between. ! This means that 'use' can _only_ be used to describe that the ! register is live. You should think twice before adding 'use' ! statements, more often you will want to use 'unspec' instead. The ! 'use' RTX is most commonly useful to describe that a fixed register ! is implicitly used in an insn. It is also safe to use in patterns ! where the compiler knows for other reasons that the result of the ! whole pattern is variable, such as 'movmemM' or 'call' patterns. ! During the reload phase, an insn that has a 'use' as pattern can ! carry a reg_equal note. These 'use' insns will be deleted before the reload phase exits. ! During the delayed branch scheduling phase, X may be an insn. This ! indicates that X previously was located at this place in the code ! and its data dependencies need to be taken into account. These ! 'use' insns will be deleted before the delayed branch scheduling ! phase exits. ! '(parallel [X0 X1 ...])' Represents several side effects performed in parallel. The square ! brackets stand for a vector; the operand of 'parallel' is a vector of expressions. X0, X1 and so on are individual side effect ! expressions--expressions of code 'set', 'call', 'return', ! 'simple_return', 'clobber' or 'use'. "In parallel" means that first all the values used in the individual side-effects are computed, and second all the actual --- 16455,16490 ---- (reg:SI 4)] 0)) (use (reg:SI 1))]) This will not work, several of the optimizers only look at expressions locally; it is very likely that if you have multiple ! insns with identical inputs to the `unspec', they will be ! optimized away even if register 1 changes in between. ! This means that `use' can _only_ be used to describe that the ! register is live. You should think twice before adding `use' ! statements, more often you will want to use `unspec' instead. The ! `use' RTX is most commonly useful to describe that a fixed ! register is implicitly used in an insn. It is also safe to use in ! patterns where the compiler knows for other reasons that the result ! of the whole pattern is variable, such as `movmemM' or `call' ! patterns. ! During the reload phase, an insn that has a `use' as pattern can ! carry a reg_equal note. These `use' insns will be deleted before the reload phase exits. ! During the delayed branch scheduling phase, X may be an insn. ! This indicates that X previously was located at this place in the ! code and its data dependencies need to be taken into account. ! These `use' insns will be deleted before the delayed branch ! scheduling phase exits. ! `(parallel [X0 X1 ...])' Represents several side effects performed in parallel. The square ! brackets stand for a vector; the operand of `parallel' is a vector of expressions. X0, X1 and so on are individual side effect ! expressions--expressions of code `set', `call', `return', ! `simple_return', `clobber' or `use'. "In parallel" means that first all the values used in the individual side-effects are computed, and second all the actual *************** operands of these. *** 16332,16344 **** says unambiguously that the values of hard register 1 and the memory location addressed by it are interchanged. In both places ! where '(reg:SI 1)' appears as a memory address it refers to the value in register 1 _before_ the execution of the insn. ! It follows that it is _incorrect_ to use 'parallel' and expect the ! result of one 'set' to be available for the next one. For example, ! people sometimes attempt to represent a jump-if-zero instruction ! this way: (parallel [(set (cc0) (reg:SI 34)) (set (pc) (if_then_else --- 16495,16507 ---- says unambiguously that the values of hard register 1 and the memory location addressed by it are interchanged. In both places ! where `(reg:SI 1)' appears as a memory address it refers to the value in register 1 _before_ the execution of the insn. ! It follows that it is _incorrect_ to use `parallel' and expect the ! result of one `set' to be available for the next one. For ! example, people sometimes attempt to represent a jump-if-zero ! instruction this way: (parallel [(set (cc0) (reg:SI 34)) (set (pc) (if_then_else *************** operands of these. *** 16351,16428 **** on the new value that is set by this instruction. Peephole optimization, which takes place together with final ! assembly code output, can produce insns whose patterns consist of a ! 'parallel' whose elements are the operands needed to output the ! resulting assembler code--often 'reg', 'mem' or constant expressions. This would not be well-formed RTL at any other stage in compilation, but it is OK then because no further optimization remains to be done. However, the definition of the macro ! 'NOTICE_UPDATE_CC', if any, must deal with such insns if you define ! any peephole optimizations. ! '(cond_exec [COND EXPR])' Represents a conditionally executed expression. The EXPR is ! executed only if the COND is nonzero. The COND expression must not ! have side-effects, but the EXPR may very well have side-effects. ! '(sequence [INSNS ...])' ! Represents a sequence of insns. If a 'sequence' appears in the chain of insns, then each of the INSNS that appears in the sequence ! must be suitable for appearing in the chain of insns, i.e. must ! satisfy the 'INSN_P' predicate. ! After delay-slot scheduling is completed, an insn and all the insns ! that reside in its delay slots are grouped together into a ! 'sequence'. The insn requiring the delay slot is the first insn in ! the vector; subsequent insns are to be placed in the delay slot. ! 'INSN_ANNULLED_BRANCH_P' is set on an insn in a delay slot to indicate that a branch insn should be used that will conditionally annul the effect of the insns in the delay slots. In such a case, ! 'INSN_FROM_TARGET_P' indicates that the insn is from the target of the branch and should be executed only if the branch is taken; otherwise the insn should be executed only if the branch is not taken. *Note Delay Slots::. ! Some back ends also use 'sequence' objects for purposes other than delay-slot groups. This is not supported in the common parts of the compiler, which treat such sequences as delay-slot groups. DWARF2 Call Frame Address (CFA) adjustments are sometimes also ! expressed using 'sequence' objects as the value of a ! 'RTX_FRAME_RELATED_P' note. This only happens if the CFA adjustments cannot be easily derived from the pattern of the instruction to which the note is attached. In such cases, the value of the note is used instead of best-guesing the semantics of the instruction. The back end can attach notes containing a ! 'sequence' of 'set' patterns that express the effect of the parent instruction. These expression codes appear in place of a side effect, as the body of an insn, though strictly speaking they do not always describe side effects as such: ! '(asm_input S)' Represents literal assembler code as described by the string S. ! '(unspec [OPERANDS ...] INDEX)' ! '(unspec_volatile [OPERANDS ...] INDEX)' ! Represents a machine-specific operation on OPERANDS. INDEX selects ! between multiple machine-specific operations. 'unspec_volatile' is ! used for volatile operations and operations that may trap; 'unspec' ! is used for other operations. ! These codes may appear inside a 'pattern' of an insn, inside a ! 'parallel', or inside an expression. ! '(addr_vec:M [LR0 LR1 ...])' Represents a table of jump addresses. The vector elements LR0, ! etc., are 'label_ref' expressions. The mode M specifies how much ! space is given to each address; normally M would be 'Pmode'. ! '(addr_diff_vec:M BASE [LR0 LR1 ...] MIN MAX FLAGS)' Represents a table of jump addresses expressed as offsets from ! BASE. The vector elements LR0, etc., are 'label_ref' expressions and so is BASE. The mode M specifies how much space is given to each address-difference. MIN and MAX are set up by branch shortening and hold a label with a minimum and a maximum address, --- 16514,16592 ---- on the new value that is set by this instruction. Peephole optimization, which takes place together with final ! assembly code output, can produce insns whose patterns consist of ! a `parallel' whose elements are the operands needed to output the ! resulting assembler code--often `reg', `mem' or constant expressions. This would not be well-formed RTL at any other stage in compilation, but it is OK then because no further optimization remains to be done. However, the definition of the macro ! `NOTICE_UPDATE_CC', if any, must deal with such insns if you ! define any peephole optimizations. ! `(cond_exec [COND EXPR])' Represents a conditionally executed expression. The EXPR is ! executed only if the COND is nonzero. The COND expression must ! not have side-effects, but the EXPR may very well have ! side-effects. ! `(sequence [INSNS ...])' ! Represents a sequence of insns. If a `sequence' appears in the chain of insns, then each of the INSNS that appears in the sequence ! must be suitable for appearing in the chain of insns, i.e. must ! satisfy the `INSN_P' predicate. ! After delay-slot scheduling is completed, an insn and all the ! insns that reside in its delay slots are grouped together into a ! `sequence'. The insn requiring the delay slot is the first insn ! in the vector; subsequent insns are to be placed in the delay slot. ! `INSN_ANNULLED_BRANCH_P' is set on an insn in a delay slot to indicate that a branch insn should be used that will conditionally annul the effect of the insns in the delay slots. In such a case, ! `INSN_FROM_TARGET_P' indicates that the insn is from the target of the branch and should be executed only if the branch is taken; otherwise the insn should be executed only if the branch is not taken. *Note Delay Slots::. ! Some back ends also use `sequence' objects for purposes other than delay-slot groups. This is not supported in the common parts of the compiler, which treat such sequences as delay-slot groups. DWARF2 Call Frame Address (CFA) adjustments are sometimes also ! expressed using `sequence' objects as the value of a ! `RTX_FRAME_RELATED_P' note. This only happens if the CFA adjustments cannot be easily derived from the pattern of the instruction to which the note is attached. In such cases, the value of the note is used instead of best-guesing the semantics of the instruction. The back end can attach notes containing a ! `sequence' of `set' patterns that express the effect of the parent instruction. These expression codes appear in place of a side effect, as the body of an insn, though strictly speaking they do not always describe side effects as such: ! `(asm_input S)' Represents literal assembler code as described by the string S. ! `(unspec [OPERANDS ...] INDEX)' ! `(unspec_volatile [OPERANDS ...] INDEX)' ! Represents a machine-specific operation on OPERANDS. INDEX ! selects between multiple machine-specific operations. ! `unspec_volatile' is used for volatile operations and operations ! that may trap; `unspec' is used for other operations. ! These codes may appear inside a `pattern' of an insn, inside a ! `parallel', or inside an expression. ! `(addr_vec:M [LR0 LR1 ...])' Represents a table of jump addresses. The vector elements LR0, ! etc., are `label_ref' expressions. The mode M specifies how much ! space is given to each address; normally M would be `Pmode'. ! `(addr_diff_vec:M BASE [LR0 LR1 ...] MIN MAX FLAGS)' Represents a table of jump addresses expressed as offsets from ! BASE. The vector elements LR0, etc., are `label_ref' expressions and so is BASE. The mode M specifies how much space is given to each address-difference. MIN and MAX are set up by branch shortening and hold a label with a minimum and a maximum address, *************** effects as such: *** 16430,16442 **** and MAX to the containing insn and of MIN and MAX to BASE. See rtl.def for details. ! '(prefetch:M ADDR RW LOCALITY)' Represents prefetch of memory at address ADDR. Operand RW is 1 if the prefetch is for data to be written, 0 otherwise; targets that do not support write prefetches should treat this as a normal prefetch. Operand LOCALITY specifies the amount of temporal ! locality; 0 if there is none or 1, 2, or 3 for increasing levels of ! temporal locality; targets that do not support locality hints should ignore this. This insn is used to minimize cache-miss latency by moving data --- 16594,16606 ---- and MAX to the containing insn and of MIN and MAX to BASE. See rtl.def for details. ! `(prefetch:M ADDR RW LOCALITY)' Represents prefetch of memory at address ADDR. Operand RW is 1 if the prefetch is for data to be written, 0 otherwise; targets that do not support write prefetches should treat this as a normal prefetch. Operand LOCALITY specifies the amount of temporal ! locality; 0 if there is none or 1, 2, or 3 for increasing levels ! of temporal locality; targets that do not support locality hints should ignore this. This insn is used to minimize cache-miss latency by moving data *************** File: gccint.info, Node: Incdec, Next: *** 16451,16490 **** Six special side-effect expression codes appear as memory addresses. ! '(pre_dec:M X)' Represents the side effect of decrementing X by a standard amount and represents also the value that X has after being decremented. ! X must be a 'reg' or 'mem', but most machines allow only a 'reg'. ! M must be the machine mode for pointers on the machine in use. The ! amount X is decremented by is the length in bytes of the machine ! mode of the containing memory reference of which this expression ! serves as the address. Here is an example of its use: (mem:DF (pre_dec:SI (reg:SI 39))) This says to decrement pseudo register 39 by the length of a ! 'DFmode' value and use the result to address a 'DFmode' value. ! '(pre_inc:M X)' Similar, but specifies incrementing X instead of decrementing it. ! '(post_dec:M X)' ! Represents the same side effect as 'pre_dec' but a different value. ! The value represented here is the value X has before being decremented. ! '(post_inc:M X)' Similar, but specifies incrementing X instead of decrementing it. ! '(post_modify:M X Y)' ! Represents the side effect of setting X to Y and represents X ! before X is modified. X must be a 'reg' or 'mem', but most ! machines allow only a 'reg'. M must be the machine mode for pointers on the machine in use. ! The expression Y must be one of three forms: '(plus:M X Z)', ! '(minus:M X Z)', or '(plus:M X I)', where Z is an index register and I is a constant. Here is an example of its use: --- 16615,16653 ---- Six special side-effect expression codes appear as memory addresses. ! `(pre_dec:M X)' Represents the side effect of decrementing X by a standard amount and represents also the value that X has after being decremented. ! X must be a `reg' or `mem', but most machines allow only a `reg'. ! M must be the machine mode for pointers on the machine in use. ! The amount X is decremented by is the length in bytes of the ! machine mode of the containing memory reference of which this ! expression serves as the address. Here is an example of its use: (mem:DF (pre_dec:SI (reg:SI 39))) This says to decrement pseudo register 39 by the length of a ! `DFmode' value and use the result to address a `DFmode' value. ! `(pre_inc:M X)' Similar, but specifies incrementing X instead of decrementing it. ! `(post_dec:M X)' ! Represents the same side effect as `pre_dec' but a different ! value. The value represented here is the value X has before being decremented. ! `(post_inc:M X)' Similar, but specifies incrementing X instead of decrementing it. ! `(post_modify:M X Y)' Represents the side effect of setting X to Y and represents X ! before X is modified. X must be a `reg' or `mem', but most ! machines allow only a `reg'. M must be the machine mode for pointers on the machine in use. ! The expression Y must be one of three forms: `(plus:M X Z)', ! `(minus:M X Z)', or `(plus:M X I)', where Z is an index register and I is a constant. Here is an example of its use: *************** Six special side-effect expression codes *** 16495,16509 **** This says to modify pseudo register 42 by adding the contents of pseudo register 48 to it, after the use of what ever 42 points to. ! '(pre_modify:M X EXPR)' Similar except side effects happen before the use. These embedded side effect expressions must be used with care. ! Instruction patterns may not use them. Until the 'flow' pass of the compiler, they may occur only to represent pushes onto the stack. The ! 'flow' pass finds cases where registers are incremented or decremented ! in one instruction and used as an address shortly before or after; these ! cases are then transformed to use pre- or post-increment or -decrement. If a register used as the operand of these expressions is used in another address in an insn, the original value of the register is used. --- 16658,16673 ---- This says to modify pseudo register 42 by adding the contents of pseudo register 48 to it, after the use of what ever 42 points to. ! `(pre_modify:M X EXPR)' Similar except side effects happen before the use. These embedded side effect expressions must be used with care. ! Instruction patterns may not use them. Until the `flow' pass of the compiler, they may occur only to represent pushes onto the stack. The ! `flow' pass finds cases where registers are incremented or decremented ! in one instruction and used as an address shortly before or after; ! these cases are then transformed to use pre- or post-increment or ! -decrement. If a register used as the operand of these expressions is used in another address in an insn, the original value of the register is used. *************** insns behave differently on different ma *** 16513,16524 **** as ambiguous and disallowed. An instruction that can be represented with an embedded side effect ! could also be represented using 'parallel' containing an additional ! 'set' to describe how the address register is altered. This is not done ! because machines that allow these operations at all typically allow them ! wherever a memory address is called for. Describing them as additional ! parallel stores would require doubling the number of entries in the ! machine description.  File: gccint.info, Node: Assembler, Next: Debug Information, Prev: Incdec, Up: RTL --- 16677,16688 ---- as ambiguous and disallowed. An instruction that can be represented with an embedded side effect ! could also be represented using `parallel' containing an additional ! `set' to describe how the address register is altered. This is not ! done because machines that allow these operations at all typically ! allow them wherever a memory address is called for. Describing them as ! additional parallel stores would require doubling the number of entries ! in the machine description.  File: gccint.info, Node: Assembler, Next: Debug Information, Prev: Incdec, Up: RTL *************** File: gccint.info, Node: Assembler, Ne *** 16526,16540 **** 13.17 Assembler Instructions as Expressions =========================================== ! The RTX code 'asm_operands' represents a value produced by a ! user-specified assembler instruction. It is used to represent an 'asm' ! statement with arguments. An 'asm' statement with a single output operand, like this: asm ("foo %1,%2,%0" : "=a" (outputvar) : "g" (x + y), "di" (*z)); ! is represented using a single 'asm_operands' RTX which represents the ! value that is stored in 'outputvar': (set RTX-FOR-OUTPUTVAR (asm_operands "foo %1,%2,%0" "a" 0 --- 16690,16704 ---- 13.17 Assembler Instructions as Expressions =========================================== ! The RTX code `asm_operands' represents a value produced by a ! user-specified assembler instruction. It is used to represent an `asm' ! statement with arguments. An `asm' statement with a single output operand, like this: asm ("foo %1,%2,%0" : "=a" (outputvar) : "g" (x + y), "di" (*z)); ! is represented using a single `asm_operands' RTX which represents the ! value that is stored in `outputvar': (set RTX-FOR-OUTPUTVAR (asm_operands "foo %1,%2,%0" "a" 0 *************** value that is stored in 'outputvar': *** 16542,16556 **** [(asm_input:M1 "g") (asm_input:M2 "di")])) ! Here the operands of the 'asm_operands' RTX are the assembler template string, the output-operand's constraint, the index-number of the output operand among the output operands specified, a vector of input operand ! RTX's, and a vector of input-operand modes and constraints. The mode M1 ! is the mode of the sum 'x+y'; M2 is that of '*z'. ! When an 'asm' statement has multiple output values, its insn has ! several such 'set' RTX's inside of a 'parallel'. Each 'set' contains an ! 'asm_operands'; all of these share the same assembler template and vectors, but each contains the constraint for the respective output operand. They are also distinguished by the output-operand index number, which is 0, 1, ... for successive output operands. --- 16706,16720 ---- [(asm_input:M1 "g") (asm_input:M2 "di")])) ! Here the operands of the `asm_operands' RTX are the assembler template string, the output-operand's constraint, the index-number of the output operand among the output operands specified, a vector of input operand ! RTX's, and a vector of input-operand modes and constraints. The mode ! M1 is the mode of the sum `x+y'; M2 is that of `*z'. ! When an `asm' statement has multiple output values, its insn has ! several such `set' RTX's inside of a `parallel'. Each `set' contains ! an `asm_operands'; all of these share the same assembler template and vectors, but each contains the constraint for the respective output operand. They are also distinguished by the output-operand index number, which is 0, 1, ... for successive output operands. *************** File: gccint.info, Node: Debug Informat *** 16561,16587 **** 13.18 Variable Location Debug Information in RTL ================================================ ! Variable tracking relies on 'MEM_EXPR' and 'REG_EXPR' annotations to determine what user variables memory and register references refer to. Variable tracking at assignments uses these notes only when they refer to variables that live at fixed locations (e.g., addressable variables, ! global non-automatic variables). For variables whose location may vary, ! it relies on the following types of notes. ! '(var_location:MODE VAR EXP STAT)' ! Binds variable 'var', a tree, to value EXP, an RTL expression. It ! appears only in 'NOTE_INSN_VAR_LOCATION' and 'DEBUG_INSN's, with ! slightly different meanings. MODE, if present, represents the mode ! of EXP, which is useful if it is a modeless expression. STAT is ! only meaningful in notes, indicating whether the variable is known ! to be initialized or uninitialized. ! '(debug_expr:MODE DECL)' ! Stands for the value bound to the 'DEBUG_EXPR_DECL' DECL, that ! points back to it, within value expressions in 'VAR_LOCATION' nodes.  File: gccint.info, Node: Insns, Next: Calls, Prev: Debug Information, Up: RTL --- 16725,16752 ---- 13.18 Variable Location Debug Information in RTL ================================================ ! Variable tracking relies on `MEM_EXPR' and `REG_EXPR' annotations to determine what user variables memory and register references refer to. Variable tracking at assignments uses these notes only when they refer to variables that live at fixed locations (e.g., addressable variables, ! global non-automatic variables). For variables whose location may ! vary, it relies on the following types of notes. ! `(var_location:MODE VAR EXP STAT)' ! Binds variable `var', a tree, to value EXP, an RTL expression. It ! appears only in `NOTE_INSN_VAR_LOCATION' and `DEBUG_INSN's, with ! slightly different meanings. MODE, if present, represents the ! mode of EXP, which is useful if it is a modeless expression. STAT ! is only meaningful in notes, indicating whether the variable is ! known to be initialized or uninitialized. ! `(debug_expr:MODE DECL)' ! Stands for the value bound to the `DEBUG_EXPR_DECL' DECL, that ! points back to it, within value expressions in `VAR_LOCATION' nodes. +  File: gccint.info, Node: Insns, Next: Calls, Prev: Debug Information, Up: RTL *************** File: gccint.info, Node: Insns, Next: *** 16591,16597 **** The RTL representation of the code for a function is a doubly-linked chain of objects called "insns". Insns are expressions with special codes that are used for no other purpose. Some insns are actual ! instructions; others represent dispatch tables for 'switch' statements; others represent labels to jump to or various sorts of declarative information. --- 16756,16762 ---- The RTL representation of the code for a function is a doubly-linked chain of objects called "insns". Insns are expressions with special codes that are used for no other purpose. Some insns are actual ! instructions; others represent dispatch tables for `switch' statements; others represent labels to jump to or various sorts of declarative information. *************** id-number that distinguishes it from all *** 16600,16624 **** function (after delayed branch scheduling, copies of an insn with the same id-number may be present in multiple places in a function, but these copies will always be identical and will only appear inside a ! 'sequence'), and chain pointers to the preceding and following insns. These three fields occupy the same position in every insn, independent ! of the expression code of the insn. They could be accessed with 'XEXP' ! and 'XINT', but instead three special macros are always used: ! 'INSN_UID (I)' Accesses the unique id of insn I. ! 'PREV_INSN (I)' Accesses the chain pointer to the insn preceding I. If I is the first insn, this is a null pointer. ! 'NEXT_INSN (I)' Accesses the chain pointer to the insn following I. If I is the last insn, this is a null pointer. ! The first insn in the chain is obtained by calling 'get_insns'; the ! last insn is the result of calling 'get_last_insn'. Within the chain ! delimited by these insns, the 'NEXT_INSN' and 'PREV_INSN' pointers must always correspond: if INSN is not the first insn, NEXT_INSN (PREV_INSN (INSN)) == INSN --- 16765,16789 ---- function (after delayed branch scheduling, copies of an insn with the same id-number may be present in multiple places in a function, but these copies will always be identical and will only appear inside a ! `sequence'), and chain pointers to the preceding and following insns. These three fields occupy the same position in every insn, independent ! of the expression code of the insn. They could be accessed with `XEXP' ! and `XINT', but instead three special macros are always used: ! `INSN_UID (I)' Accesses the unique id of insn I. ! `PREV_INSN (I)' Accesses the chain pointer to the insn preceding I. If I is the first insn, this is a null pointer. ! `NEXT_INSN (I)' Accesses the chain pointer to the insn following I. If I is the last insn, this is a null pointer. ! The first insn in the chain is obtained by calling `get_insns'; the ! last insn is the result of calling `get_last_insn'. Within the chain ! delimited by these insns, the `NEXT_INSN' and `PREV_INSN' pointers must always correspond: if INSN is not the first insn, NEXT_INSN (PREV_INSN (INSN)) == INSN *************** is always true and if INSN is not the la *** 16630,16919 **** is always true. After delay slot scheduling, some of the insns in the chain might be ! 'sequence' expressions, which contain a vector of insns. The value of ! 'NEXT_INSN' in all but the last of these insns is the next insn in the ! vector; the value of 'NEXT_INSN' of the last insn in the vector is the ! same as the value of 'NEXT_INSN' for the 'sequence' in which it is ! contained. Similar rules apply for 'PREV_INSN'. This means that the above invariants are not necessarily true for insns ! inside 'sequence' expressions. Specifically, if INSN is the first insn ! in a 'sequence', 'NEXT_INSN (PREV_INSN (INSN))' is the insn containing ! the 'sequence' expression, as is the value of 'PREV_INSN (NEXT_INSN ! (INSN))' if INSN is the last insn in the 'sequence' expression. You can ! use these expressions to find the containing 'sequence' expression. Every insn has one of the following expression codes: ! 'insn' ! The expression code 'insn' is used for instructions that do not ! jump and do not do function calls. 'sequence' expressions are ! always contained in insns with code 'insn' even if one of those insns should jump or do function calls. ! Insns with code 'insn' have four additional fields beyond the three mandatory ones listed above. These four are described in a table below. ! 'jump_insn' ! The expression code 'jump_insn' is used for instructions that may ! jump (or, more generally, may contain 'label_ref' expressions to ! which 'pc' can be set in that instruction). If there is an instruction to return from the current function, it is recorded as ! a 'jump_insn'. ! 'jump_insn' insns have the same extra fields as 'insn' insns, accessed in the same way and in addition contain a field ! 'JUMP_LABEL' which is defined once jump optimization has completed. For simple conditional and unconditional jumps, this field contains ! the 'code_label' to which this insn will (possibly conditionally) ! branch. In a more complex jump, 'JUMP_LABEL' records one of the labels that the insn refers to; other jump target labels are ! recorded as 'REG_LABEL_TARGET' notes. The exception is 'addr_vec' ! and 'addr_diff_vec', where 'JUMP_LABEL' is 'NULL_RTX' and the only way to find the labels is to scan the entire body of the insn. ! Return insns count as jumps, but their 'JUMP_LABEL' is 'RETURN' or ! 'SIMPLE_RETURN'. ! 'call_insn' ! The expression code 'call_insn' is used for instructions that may do function calls. It is important to distinguish these instructions because they imply that certain registers and memory locations may be altered unpredictably. ! 'call_insn' insns have the same extra fields as 'insn' insns, accessed in the same way and in addition contain a field ! 'CALL_INSN_FUNCTION_USAGE', which contains a list (chain of ! 'expr_list' expressions) containing 'use', 'clobber' and sometimes ! 'set' expressions that denote hard registers and 'mem's used or clobbered by the called function. ! A 'mem' generally points to a stack slot in which arguments passed to the libcall by reference (*note TARGET_PASS_BY_REFERENCE: Register Arguments.) are stored. If the argument is caller-copied (*note TARGET_CALLEE_COPIES: Register Arguments.), the stack slot ! will be mentioned in 'clobber' and 'use' entries; if it's ! callee-copied, only a 'use' will appear, and the 'mem' may point to ! addresses that are not stack slots. ! Registers occurring inside a 'clobber' in this list augment ! registers specified in 'CALL_USED_REGISTERS' (*note Register Basics::). ! If the list contains a 'set' involving two registers, it indicates ! that the function returns one of its arguments. Such a 'set' may look like a no-op if the same register holds the argument and the return value. ! 'code_label' ! A 'code_label' insn represents a label that a jump insn can jump to. It contains two special fields of data in addition to the ! three standard ones. 'CODE_LABEL_NUMBER' is used to hold the "label number", a number that identifies this label uniquely among all the labels in the compilation (not just in the current function). Ultimately, the label is represented in the assembler ! output as an assembler label, usually of the form 'LN' where N is the label number. ! When a 'code_label' appears in an RTL expression, it normally ! appears within a 'label_ref' which represents the address of the label, as a number. ! Besides as a 'code_label', a label can also be represented as a ! 'note' of type 'NOTE_INSN_DELETED_LABEL'. ! The field 'LABEL_NUSES' is only defined once the jump optimization phase is completed. It contains the number of times this label is referenced in the current function. ! The field 'LABEL_KIND' differentiates four different types of ! labels: 'LABEL_NORMAL', 'LABEL_STATIC_ENTRY', 'LABEL_GLOBAL_ENTRY', ! and 'LABEL_WEAK_ENTRY'. The only labels that do not have type ! 'LABEL_NORMAL' are "alternate entry points" to the current ! function. These may be static (visible only in the containing ! translation unit), global (exposed to all translation units), or ! weak (global, but can be overridden by another symbol with the same ! name). Much of the compiler treats all four kinds of label identically. Some of it needs to know whether or not a label is an alternate ! entry point; for this purpose, the macro 'LABEL_ALT_ENTRY_P' is ! provided. It is equivalent to testing whether 'LABEL_KIND (label) == LABEL_NORMAL'. The only place that cares about the distinction between static, global, and weak alternate entry points, besides the front-end code that creates them, is the function ! 'output_alternate_entry_point', in 'final.c'. ! To set the kind of a label, use the 'SET_LABEL_KIND' macro. ! 'jump_table_data' ! A 'jump_table_data' insn is a placeholder for the jump-table data ! of a 'casesi' or 'tablejump' insn. They are placed after a ! 'tablejump_p' insn. A 'jump_table_data' insn is not part o a basic ! blockm but it is associated with the basic block that ends with the ! 'tablejump_p' insn. The 'PATTERN' of a 'jump_table_data' is always ! either an 'addr_vec' or an 'addr_diff_vec', and a 'jump_table_data' ! insn is always preceded by a 'code_label'. The 'tablejump_p' insn ! refers to that 'code_label' via its 'JUMP_LABEL'. ! 'barrier' Barriers are placed in the instruction stream when control cannot flow past them. They are placed after unconditional jump ! instructions to indicate that the jumps are unconditional and after ! calls to 'volatile' functions, which do not return (e.g., 'exit'). ! They contain no information beyond the three standard fields. ! 'note' ! 'note' insns are used to represent additional debugging and declarative information. They contain two nonstandard fields, an ! integer which is accessed with the macro 'NOTE_LINE_NUMBER' and a ! string accessed with 'NOTE_SOURCE_FILE'. ! If 'NOTE_LINE_NUMBER' is positive, the note represents the position ! of a source line and 'NOTE_SOURCE_FILE' is the source file name ! that the line came from. These notes control generation of line ! number data in the assembler output. ! Otherwise, 'NOTE_LINE_NUMBER' is not really a line number but a ! code with one of the following values (and 'NOTE_SOURCE_FILE' must contain a null pointer): ! 'NOTE_INSN_DELETED' Such a note is completely ignorable. Some passes of the compiler delete insns by altering them into notes of this kind. ! 'NOTE_INSN_DELETED_LABEL' ! This marks what used to be a 'code_label', but was not used ! for other purposes than taking its address and was transformed ! to mark that no code jumps to it. ! 'NOTE_INSN_BLOCK_BEG' ! 'NOTE_INSN_BLOCK_END' These types of notes indicate the position of the beginning ! and end of a level of scoping of variable names. They control ! the output of debugging information. ! 'NOTE_INSN_EH_REGION_BEG' ! 'NOTE_INSN_EH_REGION_END' These types of notes indicate the position of the beginning and end of a level of scoping for exception handling. ! 'NOTE_EH_HANDLER' identifies which region is associated with these notes. ! 'NOTE_INSN_FUNCTION_BEG' Appears at the start of the function body, after the function prologue. ! 'NOTE_INSN_VAR_LOCATION' This note is used to generate variable location debugging information. It indicates that the user variable in its ! 'VAR_LOCATION' operand is at the location given in the RTL expression, or holds a value that can be computed by evaluating the RTL expression from that static point in the program up to the next such note for the same user variable. These codes are printed symbolically when they appear in debugging dumps. ! 'debug_insn' ! The expression code 'debug_insn' is used for pseudo-instructions that hold debugging information for variable tracking at ! assignments (see '-fvar-tracking-assignments' option). They are ! the RTL representation of 'GIMPLE_DEBUG' statements (*note ! GIMPLE_DEBUG::), with a 'VAR_LOCATION' operand that binds a user ! variable tree to an RTL representation of the 'value' in the ! corresponding statement. A 'DEBUG_EXPR' in it stands for the value ! bound to the corresponding 'DEBUG_EXPR_DECL'. Throughout optimization passes, binding information is kept in pseudo-instruction form, so that, unlike notes, it gets the same treatment and adjustments that regular instructions would. It is the variable tracking pass that turns these pseudo-instructions ! into var location notes, analyzing control flow, value equivalences ! and changes to registers and memory referenced in value ! expressions, propagating the values of debug temporaries and determining expressions that can be used to compute the value of each user variable at as many points (ranges, actually) in the program as possible. ! Unlike 'NOTE_INSN_VAR_LOCATION', the value expression in an ! 'INSN_VAR_LOCATION' denotes a value at that specific point in the program, rather than an expression that can be evaluated at any ! later point before an overriding 'VAR_LOCATION' is encountered. ! E.g., if a user variable is bound to a 'REG' and then a subsequent ! insn modifies the 'REG', the note location would keep mapping the user variable to the register across the insn, whereas the insn location would keep the variable bound to the value, so that the variable tracking pass would emit another location note for the variable at the point in which the register is modified. ! The machine mode of an insn is normally 'VOIDmode', but some phases use ! the mode for various purposes. The common subexpression elimination pass sets the mode of an insn to ! 'QImode' when it is the first insn in a block that has already been processed. The second Haifa scheduling pass, for targets that can multiple issue, ! sets the mode of an insn to 'TImode' when it is believed that the ! instruction begins an issue group. That is, when the instruction cannot ! issue simultaneously with the previous. This may be relied on by later ! passes, in particular machine-dependent reorg. ! Here is a table of the extra fields of 'insn', 'jump_insn' and ! 'call_insn' insns: ! 'PATTERN (I)' An expression for the side effect performed by this insn. This ! must be one of the following codes: 'set', 'call', 'use', ! 'clobber', 'return', 'simple_return', 'asm_input', 'asm_output', ! 'addr_vec', 'addr_diff_vec', 'trap_if', 'unspec', ! 'unspec_volatile', 'parallel', 'cond_exec', or 'sequence'. If it ! is a 'parallel', each element of the 'parallel' must be one these ! codes, except that 'parallel' expressions cannot be nested and ! 'addr_vec' and 'addr_diff_vec' are not permitted inside a ! 'parallel' expression. ! 'INSN_CODE (I)' An integer that says which pattern in the machine description matches this insn, or -1 if the matching has not yet been attempted. Such matching is never attempted and this field remains -1 on an ! insn whose pattern consists of a single 'use', 'clobber', ! 'asm_input', 'addr_vec' or 'addr_diff_vec' expression. ! Matching is also never attempted on insns that result from an 'asm' ! statement. These contain at least one 'asm_operands' expression. ! The function 'asm_noperands' returns a non-negative value for such insns. ! In the debugging output, this field is printed as a number followed ! by a symbolic representation that locates the pattern in the 'md' ! file as some small positive or negative offset from a named ! pattern. ! 'LOG_LINKS (I)' ! A list (chain of 'insn_list' expressions) giving information about dependencies between instructions within a basic block. Neither a jump nor a label may come between the related insns. These are only used by the schedulers and by combine. This is a deprecated data structure. Def-use and use-def chains are now preferred. ! 'REG_NOTES (I)' ! A list (chain of 'expr_list', 'insn_list' and 'int_list' expressions) giving miscellaneous information about the insn. It is often information pertaining to the registers used in this insn. ! The 'LOG_LINKS' field of an insn is a chain of 'insn_list' expressions. ! Each of these has two operands: the first is an insn, and the second is ! another 'insn_list' expression (the next one in the chain). The last ! 'insn_list' in the chain has a null pointer as second operand. The ! significant thing about the chain is which insns appear in it (as first ! operands of 'insn_list' expressions). Their order is not significant. This list is originally set up by the flow analysis pass; it is a null pointer until then. Flow only adds links for those data dependencies --- 16795,17089 ---- is always true. After delay slot scheduling, some of the insns in the chain might be ! `sequence' expressions, which contain a vector of insns. The value of ! `NEXT_INSN' in all but the last of these insns is the next insn in the ! vector; the value of `NEXT_INSN' of the last insn in the vector is the ! same as the value of `NEXT_INSN' for the `sequence' in which it is ! contained. Similar rules apply for `PREV_INSN'. This means that the above invariants are not necessarily true for insns ! inside `sequence' expressions. Specifically, if INSN is the first insn ! in a `sequence', `NEXT_INSN (PREV_INSN (INSN))' is the insn containing ! the `sequence' expression, as is the value of `PREV_INSN (NEXT_INSN ! (INSN))' if INSN is the last insn in the `sequence' expression. You ! can use these expressions to find the containing `sequence' expression. Every insn has one of the following expression codes: ! `insn' ! The expression code `insn' is used for instructions that do not ! jump and do not do function calls. `sequence' expressions are ! always contained in insns with code `insn' even if one of those insns should jump or do function calls. ! Insns with code `insn' have four additional fields beyond the three mandatory ones listed above. These four are described in a table below. ! `jump_insn' ! The expression code `jump_insn' is used for instructions that may ! jump (or, more generally, may contain `label_ref' expressions to ! which `pc' can be set in that instruction). If there is an instruction to return from the current function, it is recorded as ! a `jump_insn'. ! `jump_insn' insns have the same extra fields as `insn' insns, accessed in the same way and in addition contain a field ! `JUMP_LABEL' which is defined once jump optimization has completed. For simple conditional and unconditional jumps, this field contains ! the `code_label' to which this insn will (possibly conditionally) ! branch. In a more complex jump, `JUMP_LABEL' records one of the labels that the insn refers to; other jump target labels are ! recorded as `REG_LABEL_TARGET' notes. The exception is `addr_vec' ! and `addr_diff_vec', where `JUMP_LABEL' is `NULL_RTX' and the only way to find the labels is to scan the entire body of the insn. ! Return insns count as jumps, but their `JUMP_LABEL' is `RETURN' or ! `SIMPLE_RETURN'. ! `call_insn' ! The expression code `call_insn' is used for instructions that may do function calls. It is important to distinguish these instructions because they imply that certain registers and memory locations may be altered unpredictably. ! `call_insn' insns have the same extra fields as `insn' insns, accessed in the same way and in addition contain a field ! `CALL_INSN_FUNCTION_USAGE', which contains a list (chain of ! `expr_list' expressions) containing `use', `clobber' and sometimes ! `set' expressions that denote hard registers and `mem's used or clobbered by the called function. ! A `mem' generally points to a stack slot in which arguments passed to the libcall by reference (*note TARGET_PASS_BY_REFERENCE: Register Arguments.) are stored. If the argument is caller-copied (*note TARGET_CALLEE_COPIES: Register Arguments.), the stack slot ! will be mentioned in `clobber' and `use' entries; if it's ! callee-copied, only a `use' will appear, and the `mem' may point ! to addresses that are not stack slots. ! Registers occurring inside a `clobber' in this list augment ! registers specified in `CALL_USED_REGISTERS' (*note Register Basics::). ! If the list contains a `set' involving two registers, it indicates ! that the function returns one of its arguments. Such a `set' may look like a no-op if the same register holds the argument and the return value. ! `code_label' ! A `code_label' insn represents a label that a jump insn can jump to. It contains two special fields of data in addition to the ! three standard ones. `CODE_LABEL_NUMBER' is used to hold the "label number", a number that identifies this label uniquely among all the labels in the compilation (not just in the current function). Ultimately, the label is represented in the assembler ! output as an assembler label, usually of the form `LN' where N is the label number. ! When a `code_label' appears in an RTL expression, it normally ! appears within a `label_ref' which represents the address of the label, as a number. ! Besides as a `code_label', a label can also be represented as a ! `note' of type `NOTE_INSN_DELETED_LABEL'. ! The field `LABEL_NUSES' is only defined once the jump optimization phase is completed. It contains the number of times this label is referenced in the current function. ! The field `LABEL_KIND' differentiates four different types of ! labels: `LABEL_NORMAL', `LABEL_STATIC_ENTRY', ! `LABEL_GLOBAL_ENTRY', and `LABEL_WEAK_ENTRY'. The only labels ! that do not have type `LABEL_NORMAL' are "alternate entry points" ! to the current function. These may be static (visible only in the ! containing translation unit), global (exposed to all translation ! units), or weak (global, but can be overridden by another symbol ! with the same name). Much of the compiler treats all four kinds of label identically. Some of it needs to know whether or not a label is an alternate ! entry point; for this purpose, the macro `LABEL_ALT_ENTRY_P' is ! provided. It is equivalent to testing whether `LABEL_KIND (label) == LABEL_NORMAL'. The only place that cares about the distinction between static, global, and weak alternate entry points, besides the front-end code that creates them, is the function ! `output_alternate_entry_point', in `final.c'. ! To set the kind of a label, use the `SET_LABEL_KIND' macro. ! `jump_table_data' ! A `jump_table_data' insn is a placeholder for the jump-table data ! of a `casesi' or `tablejump' insn. They are placed after a ! `tablejump_p' insn. A `jump_table_data' insn is not part o a ! basic blockm but it is associated with the basic block that ends ! with the `tablejump_p' insn. The `PATTERN' of a `jump_table_data' ! is always either an `addr_vec' or an `addr_diff_vec', and a ! `jump_table_data' insn is always preceded by a `code_label'. The ! `tablejump_p' insn refers to that `code_label' via its ! `JUMP_LABEL'. ! `barrier' Barriers are placed in the instruction stream when control cannot flow past them. They are placed after unconditional jump ! instructions to indicate that the jumps are unconditional and ! after calls to `volatile' functions, which do not return (e.g., ! `exit'). They contain no information beyond the three standard ! fields. ! `note' ! `note' insns are used to represent additional debugging and declarative information. They contain two nonstandard fields, an ! integer which is accessed with the macro `NOTE_LINE_NUMBER' and a ! string accessed with `NOTE_SOURCE_FILE'. ! If `NOTE_LINE_NUMBER' is positive, the note represents the ! position of a source line and `NOTE_SOURCE_FILE' is the source ! file name that the line came from. These notes control generation ! of line number data in the assembler output. ! Otherwise, `NOTE_LINE_NUMBER' is not really a line number but a ! code with one of the following values (and `NOTE_SOURCE_FILE' must contain a null pointer): ! `NOTE_INSN_DELETED' Such a note is completely ignorable. Some passes of the compiler delete insns by altering them into notes of this kind. ! `NOTE_INSN_DELETED_LABEL' ! This marks what used to be a `code_label', but was not used ! for other purposes than taking its address and was ! transformed to mark that no code jumps to it. ! `NOTE_INSN_BLOCK_BEG' ! `NOTE_INSN_BLOCK_END' These types of notes indicate the position of the beginning ! and end of a level of scoping of variable names. They ! control the output of debugging information. ! `NOTE_INSN_EH_REGION_BEG' ! `NOTE_INSN_EH_REGION_END' These types of notes indicate the position of the beginning and end of a level of scoping for exception handling. ! `NOTE_EH_HANDLER' identifies which region is associated with these notes. ! `NOTE_INSN_FUNCTION_BEG' Appears at the start of the function body, after the function prologue. ! `NOTE_INSN_VAR_LOCATION' This note is used to generate variable location debugging information. It indicates that the user variable in its ! `VAR_LOCATION' operand is at the location given in the RTL expression, or holds a value that can be computed by evaluating the RTL expression from that static point in the program up to the next such note for the same user variable. + These codes are printed symbolically when they appear in debugging dumps. ! `debug_insn' ! The expression code `debug_insn' is used for pseudo-instructions that hold debugging information for variable tracking at ! assignments (see `-fvar-tracking-assignments' option). They are ! the RTL representation of `GIMPLE_DEBUG' statements (*note ! `GIMPLE_DEBUG'::), with a `VAR_LOCATION' operand that binds a user ! variable tree to an RTL representation of the `value' in the ! corresponding statement. A `DEBUG_EXPR' in it stands for the ! value bound to the corresponding `DEBUG_EXPR_DECL'. Throughout optimization passes, binding information is kept in pseudo-instruction form, so that, unlike notes, it gets the same treatment and adjustments that regular instructions would. It is the variable tracking pass that turns these pseudo-instructions ! into var location notes, analyzing control flow, value ! equivalences and changes to registers and memory referenced in ! value expressions, propagating the values of debug temporaries and determining expressions that can be used to compute the value of each user variable at as many points (ranges, actually) in the program as possible. ! Unlike `NOTE_INSN_VAR_LOCATION', the value expression in an ! `INSN_VAR_LOCATION' denotes a value at that specific point in the program, rather than an expression that can be evaluated at any ! later point before an overriding `VAR_LOCATION' is encountered. ! E.g., if a user variable is bound to a `REG' and then a subsequent ! insn modifies the `REG', the note location would keep mapping the user variable to the register across the insn, whereas the insn location would keep the variable bound to the value, so that the variable tracking pass would emit another location note for the variable at the point in which the register is modified. ! ! The machine mode of an insn is normally `VOIDmode', but some phases ! use the mode for various purposes. The common subexpression elimination pass sets the mode of an insn to ! `QImode' when it is the first insn in a block that has already been processed. The second Haifa scheduling pass, for targets that can multiple issue, ! sets the mode of an insn to `TImode' when it is believed that the ! instruction begins an issue group. That is, when the instruction ! cannot issue simultaneously with the previous. This may be relied on ! by later passes, in particular machine-dependent reorg. ! Here is a table of the extra fields of `insn', `jump_insn' and ! `call_insn' insns: ! `PATTERN (I)' An expression for the side effect performed by this insn. This ! must be one of the following codes: `set', `call', `use', ! `clobber', `return', `simple_return', `asm_input', `asm_output', ! `addr_vec', `addr_diff_vec', `trap_if', `unspec', ! `unspec_volatile', `parallel', `cond_exec', or `sequence'. If it ! is a `parallel', each element of the `parallel' must be one these ! codes, except that `parallel' expressions cannot be nested and ! `addr_vec' and `addr_diff_vec' are not permitted inside a ! `parallel' expression. ! `INSN_CODE (I)' An integer that says which pattern in the machine description matches this insn, or -1 if the matching has not yet been attempted. Such matching is never attempted and this field remains -1 on an ! insn whose pattern consists of a single `use', `clobber', ! `asm_input', `addr_vec' or `addr_diff_vec' expression. ! Matching is also never attempted on insns that result from an `asm' ! statement. These contain at least one `asm_operands' expression. ! The function `asm_noperands' returns a non-negative value for such insns. ! In the debugging output, this field is printed as a number ! followed by a symbolic representation that locates the pattern in ! the `md' file as some small positive or negative offset from a ! named pattern. ! `LOG_LINKS (I)' ! A list (chain of `insn_list' expressions) giving information about dependencies between instructions within a basic block. Neither a jump nor a label may come between the related insns. These are only used by the schedulers and by combine. This is a deprecated data structure. Def-use and use-def chains are now preferred. ! `REG_NOTES (I)' ! A list (chain of `expr_list', `insn_list' and `int_list' expressions) giving miscellaneous information about the insn. It is often information pertaining to the registers used in this insn. ! The `LOG_LINKS' field of an insn is a chain of `insn_list' ! expressions. Each of these has two operands: the first is an insn, and ! the second is another `insn_list' expression (the next one in the ! chain). The last `insn_list' in the chain has a null pointer as second ! operand. The significant thing about the chain is which insns appear ! in it (as first operands of `insn_list' expressions). Their order is ! not significant. This list is originally set up by the flow analysis pass; it is a null pointer until then. Flow only adds links for those data dependencies *************** which can be used for instruction combin *** 16921,16945 **** analysis pass adds a link to insns which store into registers values that are used for the first time in this insn. ! The 'REG_NOTES' field of an insn is a chain similar to the 'LOG_LINKS' ! field but it includes 'expr_list' and 'int_list' expressions in addition ! to 'insn_list' expressions. There are several kinds of register notes, ! which are distinguished by the machine mode, which in a register note is ! really understood as being an 'enum reg_note'. The first operand OP of ! the note is data whose meaning depends on the kind of note. ! The macro 'REG_NOTE_KIND (X)' returns the kind of register note. Its ! counterpart, the macro 'PUT_REG_NOTE_KIND (X, NEWKIND)' sets the register note type of X to be NEWKIND. Register notes are of three classes: They may say something about an input to an insn, they may say something about an output of an insn, or they may create a linkage between two insns. There are also a set of ! values that are only used in 'LOG_LINKS'. These register notes annotate inputs to an insn: ! 'REG_DEAD' The value in OP dies in this insn; that is to say, altering the value immediately after this insn would not affect the future behavior of the program. --- 17091,17116 ---- analysis pass adds a link to insns which store into registers values that are used for the first time in this insn. ! The `REG_NOTES' field of an insn is a chain similar to the `LOG_LINKS' ! field but it includes `expr_list' and `int_list' expressions in ! addition to `insn_list' expressions. There are several kinds of ! register notes, which are distinguished by the machine mode, which in a ! register note is really understood as being an `enum reg_note'. The ! first operand OP of the note is data whose meaning depends on the kind ! of note. ! The macro `REG_NOTE_KIND (X)' returns the kind of register note. Its ! counterpart, the macro `PUT_REG_NOTE_KIND (X, NEWKIND)' sets the register note type of X to be NEWKIND. Register notes are of three classes: They may say something about an input to an insn, they may say something about an output of an insn, or they may create a linkage between two insns. There are also a set of ! values that are only used in `LOG_LINKS'. These register notes annotate inputs to an insn: ! `REG_DEAD' The value in OP dies in this insn; that is to say, altering the value immediately after this insn would not affect the future behavior of the program. *************** values that are only used in 'LOG_LINKS' *** 16948,17019 **** this insn since OP is not necessarily modified by this insn. Rather, no subsequent instruction uses the contents of OP. ! 'REG_UNUSED' The register OP being set by this insn will not be used in a ! subsequent insn. This differs from a 'REG_DEAD' note, which indicates that the value in an input will not be used subsequently. These two notes are independent; both may be present for the same register. ! 'REG_INC' ! The register OP is incremented (or decremented; at this level there ! is no distinction) by an embedded side effect inside this insn. ! This means it appears in a 'post_inc', 'pre_inc', 'post_dec' or ! 'pre_dec' expression. ! 'REG_NONNEG' ! The register OP is known to have a nonnegative value when this insn ! is reached. This is used so that decrement and branch until zero ! instructions, such as the m68k dbra, can be matched. ! The 'REG_NONNEG' note is added to insns only if the machine ! description has a 'decrement_and_branch_until_zero' pattern. ! 'REG_LABEL_OPERAND' ! This insn uses OP, a 'code_label' or a 'note' of type ! 'NOTE_INSN_DELETED_LABEL', but is not a 'jump_insn', or it is a ! 'jump_insn' that refers to the operand as an ordinary operand. The ! label may still eventually be a jump target, but if so in an indirect jump in a subsequent insn. The presence of this note allows jump optimization to be aware that OP is, in fact, being used, and flow optimization to build an accurate flow graph. ! 'REG_LABEL_TARGET' ! This insn is a 'jump_insn' but not an 'addr_vec' or ! 'addr_diff_vec'. It uses OP, a 'code_label' as a direct or indirect jump target. Its purpose is similar to that of ! 'REG_LABEL_OPERAND'. This note is only present if the insn has multiple targets; the last label in the insn (in the highest ! numbered insn-field) goes into the 'JUMP_LABEL' field and does not ! have a 'REG_LABEL_TARGET' note. *Note JUMP_LABEL: Insns. ! 'REG_CROSSING_JUMP' This insn is a branching instruction (either an unconditional jump or an indirect jump) which crosses between hot and cold sections, which could potentially be very far apart in the executable. The presence of this note indicates to other optimizations that this branching instruction should not be "collapsed" into a simpler ! branching construct. It is used when the optimization to partition ! basic blocks into hot and cold sections is turned on. ! 'REG_SETJMP' ! Appears attached to each 'CALL_INSN' to 'setjmp' or a related function. The following notes describe attributes of outputs of an insn: ! 'REG_EQUIV' ! 'REG_EQUAL' This note is only valid on an insn that sets only one register and indicates that that register will be equal to OP at run time; the scope of this equivalence differs between the two types of notes. The value which the insn explicitly copies into the register may look different from OP, but they will be equal at run time. If the ! output of the single 'set' is a 'strict_low_part' or 'zero_extract' ! expression, the note refers to the register that is contained in ! its first operand. ! For 'REG_EQUIV', the register is equivalent to OP throughout the entire function, and could validly be replaced in all its occurrences by OP. ("Validly" here refers to the data flow of the program; simple replacement may make some insns invalid.) For --- 17119,17190 ---- this insn since OP is not necessarily modified by this insn. Rather, no subsequent instruction uses the contents of OP. ! `REG_UNUSED' The register OP being set by this insn will not be used in a ! subsequent insn. This differs from a `REG_DEAD' note, which indicates that the value in an input will not be used subsequently. These two notes are independent; both may be present for the same register. ! `REG_INC' ! The register OP is incremented (or decremented; at this level ! there is no distinction) by an embedded side effect inside this ! insn. This means it appears in a `post_inc', `pre_inc', ! `post_dec' or `pre_dec' expression. ! `REG_NONNEG' ! The register OP is known to have a nonnegative value when this ! insn is reached. This is used so that decrement and branch until ! zero instructions, such as the m68k dbra, can be matched. ! The `REG_NONNEG' note is added to insns only if the machine ! description has a `decrement_and_branch_until_zero' pattern. ! `REG_LABEL_OPERAND' ! This insn uses OP, a `code_label' or a `note' of type ! `NOTE_INSN_DELETED_LABEL', but is not a `jump_insn', or it is a ! `jump_insn' that refers to the operand as an ordinary operand. ! The label may still eventually be a jump target, but if so in an indirect jump in a subsequent insn. The presence of this note allows jump optimization to be aware that OP is, in fact, being used, and flow optimization to build an accurate flow graph. ! `REG_LABEL_TARGET' ! This insn is a `jump_insn' but not an `addr_vec' or ! `addr_diff_vec'. It uses OP, a `code_label' as a direct or indirect jump target. Its purpose is similar to that of ! `REG_LABEL_OPERAND'. This note is only present if the insn has multiple targets; the last label in the insn (in the highest ! numbered insn-field) goes into the `JUMP_LABEL' field and does not ! have a `REG_LABEL_TARGET' note. *Note JUMP_LABEL: Insns. ! `REG_CROSSING_JUMP' This insn is a branching instruction (either an unconditional jump or an indirect jump) which crosses between hot and cold sections, which could potentially be very far apart in the executable. The presence of this note indicates to other optimizations that this branching instruction should not be "collapsed" into a simpler ! branching construct. It is used when the optimization to ! partition basic blocks into hot and cold sections is turned on. ! `REG_SETJMP' ! Appears attached to each `CALL_INSN' to `setjmp' or a related function. The following notes describe attributes of outputs of an insn: ! `REG_EQUIV' ! `REG_EQUAL' This note is only valid on an insn that sets only one register and indicates that that register will be equal to OP at run time; the scope of this equivalence differs between the two types of notes. The value which the insn explicitly copies into the register may look different from OP, but they will be equal at run time. If the ! output of the single `set' is a `strict_low_part' or ! `zero_extract' expression, the note refers to the register that is ! contained in its first operand. ! For `REG_EQUIV', the register is equivalent to OP throughout the entire function, and could validly be replaced in all its occurrences by OP. ("Validly" here refers to the data flow of the program; simple replacement may make some insns invalid.) For *************** values that are only used in 'LOG_LINKS' *** 17023,17044 **** When a parameter is copied into a pseudo-register at entry to a function, a note of this kind records that the register is equivalent to the stack slot where the parameter was passed. ! Although in this case the register may be set by other insns, it is ! still valid to replace the register by the stack slot throughout ! the function. ! A 'REG_EQUIV' note is also used on an instruction which copies a register parameter into a pseudo-register at entry to a function, if there is a stack slot where that parameter could be stored. Although other insns may set the pseudo-register, it is valid for the compiler to replace the pseudo-register by stack slot throughout the function, provided the compiler ensures that the ! stack slot is properly initialized by making the replacement in the ! initial copy instruction as well. This is used on machines for ! which the calling convention allocates stack space for register ! parameters. See 'REG_PARM_STACK_SPACE' in *note Stack Arguments::. ! In the case of 'REG_EQUAL', the register that is set by this insn will be equal to OP at run time at the end of this insn but not necessarily elsewhere in the function. In this case, OP is typically an arithmetic expression. For example, when a sequence --- 17194,17216 ---- When a parameter is copied into a pseudo-register at entry to a function, a note of this kind records that the register is equivalent to the stack slot where the parameter was passed. ! Although in this case the register may be set by other insns, it ! is still valid to replace the register by the stack slot ! throughout the function. ! A `REG_EQUIV' note is also used on an instruction which copies a register parameter into a pseudo-register at entry to a function, if there is a stack slot where that parameter could be stored. Although other insns may set the pseudo-register, it is valid for the compiler to replace the pseudo-register by stack slot throughout the function, provided the compiler ensures that the ! stack slot is properly initialized by making the replacement in ! the initial copy instruction as well. This is used on machines ! for which the calling convention allocates stack space for ! register parameters. See `REG_PARM_STACK_SPACE' in *note Stack ! Arguments::. ! In the case of `REG_EQUAL', the register that is set by this insn will be equal to OP at run time at the end of this insn but not necessarily elsewhere in the function. In this case, OP is typically an arithmetic expression. For example, when a sequence *************** values that are only used in 'LOG_LINKS' *** 17047,17132 **** or copies the final value. These two notes are used in different ways by the compiler passes. ! 'REG_EQUAL' is used by passes prior to register allocation (such as common subexpression elimination and loop optimization) to tell ! them how to think of that value. 'REG_EQUIV' notes are used by register allocation to indicate that there is an available ! substitute expression (either a constant or a 'mem' expression for ! the location of a parameter on the stack) that may be used in place ! of a register if insufficient registers are available. Except for stack homes for parameters, which are indicated by a ! 'REG_EQUIV' note and are not useful to the early optimization passes and pseudo registers that are equivalent to a memory location throughout their entire life, which is not detected until later in the compilation, all equivalences are initially indicated ! by an attached 'REG_EQUAL' note. In the early stages of register ! allocation, a 'REG_EQUAL' note is changed into a 'REG_EQUIV' note if OP is a constant and the insn represents the only set of its destination register. Thus, compiler passes prior to register allocation need only check ! for 'REG_EQUAL' notes and passes subsequent to register allocation ! need only check for 'REG_EQUIV' notes. These notes describe linkages between insns. They occur in pairs: one insn has one of a pair of notes that points to a second insn, which has the inverse note pointing back to the first insn. ! 'REG_CC_SETTER' ! 'REG_CC_USER' ! On machines that use 'cc0', the insns which set and use 'cc0' set ! and use 'cc0' are adjacent. However, when branch delay slot filling is done, this may no longer be true. In this case a ! 'REG_CC_USER' note will be placed on the insn setting 'cc0' to ! point to the insn using 'cc0' and a 'REG_CC_SETTER' note will be ! placed on the insn using 'cc0' to point to the insn setting 'cc0'. ! These values are only used in the 'LOG_LINKS' field, and indicate the type of dependency that each link represents. Links which indicate a data dependence (a read after write dependence) do not use any code, ! they simply have mode 'VOIDmode', and are printed without any descriptive text. ! 'REG_DEP_TRUE' This indicates a true dependence (a read after write dependence). ! 'REG_DEP_OUTPUT' This indicates an output dependence (a write after write dependence). ! 'REG_DEP_ANTI' This indicates an anti dependence (a write after read dependence). These notes describe information gathered from gcov profile data. They ! are stored in the 'REG_NOTES' field of an insn. ! 'REG_BR_PROB' This is used to specify the ratio of branches to non-branches of a branch insn according to the profile data. The note is represented ! as an 'int_list' expression whose integer value is between 0 and ! REG_BR_PROB_BASE. Larger values indicate a higher probability that the branch will be taken. ! 'REG_BR_PRED' These notes are found in JUMP insns after delayed branch scheduling has taken place. They indicate both the direction and the likelihood of the JUMP. The format is a bitmask of ATTR_FLAG_* values. ! 'REG_FRAME_RELATED_EXPR' This is used on an RTX_FRAME_RELATED_P insn wherein the attached expression is used in place of the actual insn pattern. This is done in cases where the pattern is either complex or misleading. ! For convenience, the machine mode in an 'insn_list' or 'expr_list' is printed using these symbolic codes in debugging dumps. ! The only difference between the expression codes 'insn_list' and ! 'expr_list' is that the first operand of an 'insn_list' is assumed to be ! an insn and is printed in debugging dumps as the insn's unique id; the ! first operand of an 'expr_list' is printed in the ordinary way as an ! expression.  File: gccint.info, Node: Calls, Next: Sharing, Prev: Insns, Up: RTL --- 17219,17305 ---- or copies the final value. These two notes are used in different ways by the compiler passes. ! `REG_EQUAL' is used by passes prior to register allocation (such as common subexpression elimination and loop optimization) to tell ! them how to think of that value. `REG_EQUIV' notes are used by register allocation to indicate that there is an available ! substitute expression (either a constant or a `mem' expression for ! the location of a parameter on the stack) that may be used in ! place of a register if insufficient registers are available. Except for stack homes for parameters, which are indicated by a ! `REG_EQUIV' note and are not useful to the early optimization passes and pseudo registers that are equivalent to a memory location throughout their entire life, which is not detected until later in the compilation, all equivalences are initially indicated ! by an attached `REG_EQUAL' note. In the early stages of register ! allocation, a `REG_EQUAL' note is changed into a `REG_EQUIV' note if OP is a constant and the insn represents the only set of its destination register. Thus, compiler passes prior to register allocation need only check ! for `REG_EQUAL' notes and passes subsequent to register allocation ! need only check for `REG_EQUIV' notes. These notes describe linkages between insns. They occur in pairs: one insn has one of a pair of notes that points to a second insn, which has the inverse note pointing back to the first insn. ! `REG_CC_SETTER' ! `REG_CC_USER' ! On machines that use `cc0', the insns which set and use `cc0' set ! and use `cc0' are adjacent. However, when branch delay slot filling is done, this may no longer be true. In this case a ! `REG_CC_USER' note will be placed on the insn setting `cc0' to ! point to the insn using `cc0' and a `REG_CC_SETTER' note will be ! placed on the insn using `cc0' to point to the insn setting `cc0'. ! These values are only used in the `LOG_LINKS' field, and indicate the type of dependency that each link represents. Links which indicate a data dependence (a read after write dependence) do not use any code, ! they simply have mode `VOIDmode', and are printed without any descriptive text. ! `REG_DEP_TRUE' This indicates a true dependence (a read after write dependence). ! `REG_DEP_OUTPUT' This indicates an output dependence (a write after write dependence). ! `REG_DEP_ANTI' This indicates an anti dependence (a write after read dependence). + These notes describe information gathered from gcov profile data. They ! are stored in the `REG_NOTES' field of an insn. ! `REG_BR_PROB' This is used to specify the ratio of branches to non-branches of a branch insn according to the profile data. The note is represented ! as an `int_list' expression whose integer value is between 0 and ! REG_BR_PROB_BASE. Larger values indicate a higher probability that the branch will be taken. ! `REG_BR_PRED' These notes are found in JUMP insns after delayed branch scheduling has taken place. They indicate both the direction and the likelihood of the JUMP. The format is a bitmask of ATTR_FLAG_* values. ! `REG_FRAME_RELATED_EXPR' This is used on an RTX_FRAME_RELATED_P insn wherein the attached expression is used in place of the actual insn pattern. This is done in cases where the pattern is either complex or misleading. ! For convenience, the machine mode in an `insn_list' or `expr_list' is printed using these symbolic codes in debugging dumps. ! The only difference between the expression codes `insn_list' and ! `expr_list' is that the first operand of an `insn_list' is assumed to ! be an insn and is printed in debugging dumps as the insn's unique id; ! the first operand of an `expr_list' is printed in the ordinary way as ! an expression.  File: gccint.info, Node: Calls, Next: Sharing, Prev: Insns, Up: RTL *************** File: gccint.info, Node: Calls, Next: *** 17134,17157 **** 13.20 RTL Representation of Function-Call Insns =============================================== ! Insns that call subroutines have the RTL expression code 'call_insn'. These insns must satisfy special rules, and their bodies must use a ! special RTL expression code, 'call'. ! A 'call' expression has two operands, as follows: (call (mem:FM ADDR) NBYTES) Here NBYTES is an operand that represents the number of bytes of argument data being passed to the subroutine, FM is a machine mode ! (which must equal as the definition of the 'FUNCTION_MODE' macro in the machine description) and ADDR represents the address of the subroutine. ! For a subroutine that returns no value, the 'call' expression as shown above is the entire body of the insn, except that the insn might also ! contain 'use' or 'clobber' expressions. ! For a subroutine that returns a value whose mode is not 'BLKmode', the value is returned in a hard register. If this register's number is R, then the body of the call insn looks like this: --- 17307,17330 ---- 13.20 RTL Representation of Function-Call Insns =============================================== ! Insns that call subroutines have the RTL expression code `call_insn'. These insns must satisfy special rules, and their bodies must use a ! special RTL expression code, `call'. ! A `call' expression has two operands, as follows: (call (mem:FM ADDR) NBYTES) Here NBYTES is an operand that represents the number of bytes of argument data being passed to the subroutine, FM is a machine mode ! (which must equal as the definition of the `FUNCTION_MODE' macro in the machine description) and ADDR represents the address of the subroutine. ! For a subroutine that returns no value, the `call' expression as shown above is the entire body of the insn, except that the insn might also ! contain `use' or `clobber' expressions. ! For a subroutine that returns a value whose mode is not `BLKmode', the value is returned in a hard register. If this register's number is R, then the body of the call insn looks like this: *************** then the body of the call insn looks lik *** 17161,17190 **** This RTL expression makes it clear (to the optimizer passes) that the appropriate register receives a useful value in this insn. ! When a subroutine returns a 'BLKmode' value, it is handled by passing to the subroutine the address of a place to store the value. So the call insn itself does not "return" any value, and it has the same RTL form as a call that returns nothing. On some machines, the call instruction itself clobbers some register, ! for example to contain the return address. 'call_insn' insns on these ! machines should have a body which is a 'parallel' that contains both the ! 'call' expression and 'clobber' expressions that indicate which registers are destroyed. Similarly, if the call instruction requires some register other than the stack pointer that is not explicitly ! mentioned in its RTL, a 'use' subexpression should mention that register. Functions that are called are assumed to modify all registers listed in ! the configuration macro 'CALL_USED_REGISTERS' (*note Register Basics::) ! and, with the exception of 'const' functions and library calls, to modify all of memory. ! Insns containing just 'use' expressions directly precede the ! 'call_insn' insn to indicate which registers contain inputs to the function. Similarly, if registers other than those in ! 'CALL_USED_REGISTERS' are clobbered by the called function, insns ! containing a single 'clobber' follow immediately after the call to indicate which registers.  --- 17334,17363 ---- This RTL expression makes it clear (to the optimizer passes) that the appropriate register receives a useful value in this insn. ! When a subroutine returns a `BLKmode' value, it is handled by passing to the subroutine the address of a place to store the value. So the call insn itself does not "return" any value, and it has the same RTL form as a call that returns nothing. On some machines, the call instruction itself clobbers some register, ! for example to contain the return address. `call_insn' insns on these ! machines should have a body which is a `parallel' that contains both ! the `call' expression and `clobber' expressions that indicate which registers are destroyed. Similarly, if the call instruction requires some register other than the stack pointer that is not explicitly ! mentioned in its RTL, a `use' subexpression should mention that register. Functions that are called are assumed to modify all registers listed in ! the configuration macro `CALL_USED_REGISTERS' (*note Register Basics::) ! and, with the exception of `const' functions and library calls, to modify all of memory. ! Insns containing just `use' expressions directly precede the ! `call_insn' insn to indicate which registers contain inputs to the function. Similarly, if registers other than those in ! `CALL_USED_REGISTERS' are clobbered by the called function, insns ! containing a single `clobber' follow immediately after the call to indicate which registers.  *************** File: gccint.info, Node: Sharing, Next *** 17194,17242 **** =================================== The compiler assumes that certain kinds of RTL expressions are unique; ! there do not exist two distinct objects representing the same value. In ! other cases, it makes an opposite assumption: that no RTL expression object of a certain kind appears in more than one place in the containing structure. These assumptions refer to a single function; except for the RTL ! objects that describe global variables and external functions, and a few ! standard objects such as small integer constants, no RTL objects are ! common to two functions. ! * Each pseudo-register has only a single 'reg' object to represent it, and therefore only a single machine mode. ! * For any symbolic label, there is only one 'symbol_ref' object referring to it. ! * All 'const_int' expressions with equal values are shared. ! * There is only one 'pc' expression. ! * There is only one 'cc0' expression. ! * There is only one 'const_double' expression with value 0 for each floating point mode. Likewise for values 1 and 2. ! * There is only one 'const_vector' expression with value 0 for each vector mode, be it an integer or a double constant vector. ! * No 'label_ref' or 'scratch' appears in more than one place in the RTL structure; in other words, it is safe to do a tree-walk of all ! the insns in the function and assume that each time a 'label_ref' ! or 'scratch' is seen it is distinct from all others that are seen. ! * Only one 'mem' object is normally created for each static variable or stack slot, so these objects are frequently shared in all the places they appear. However, separate but equal objects for these variables are occasionally made. ! * When a single 'asm' statement has multiple output operands, a ! distinct 'asm_operands' expression is made for each output operand. However, these all share the vector which contains the sequence of input operands. This sharing is used later on to test whether two ! 'asm_operands' expressions come from the same statement, so all optimizations must carefully preserve the sharing if they copy the vector at all. --- 17367,17415 ---- =================================== The compiler assumes that certain kinds of RTL expressions are unique; ! there do not exist two distinct objects representing the same value. ! In other cases, it makes an opposite assumption: that no RTL expression object of a certain kind appears in more than one place in the containing structure. These assumptions refer to a single function; except for the RTL ! objects that describe global variables and external functions, and a ! few standard objects such as small integer constants, no RTL objects ! are common to two functions. ! * Each pseudo-register has only a single `reg' object to represent it, and therefore only a single machine mode. ! * For any symbolic label, there is only one `symbol_ref' object referring to it. ! * All `const_int' expressions with equal values are shared. ! * There is only one `pc' expression. ! * There is only one `cc0' expression. ! * There is only one `const_double' expression with value 0 for each floating point mode. Likewise for values 1 and 2. ! * There is only one `const_vector' expression with value 0 for each vector mode, be it an integer or a double constant vector. ! * No `label_ref' or `scratch' appears in more than one place in the RTL structure; in other words, it is safe to do a tree-walk of all ! the insns in the function and assume that each time a `label_ref' ! or `scratch' is seen it is distinct from all others that are seen. ! * Only one `mem' object is normally created for each static variable or stack slot, so these objects are frequently shared in all the places they appear. However, separate but equal objects for these variables are occasionally made. ! * When a single `asm' statement has multiple output operands, a ! distinct `asm_operands' expression is made for each output operand. However, these all share the vector which contains the sequence of input operands. This sharing is used later on to test whether two ! `asm_operands' expressions come from the same statement, so all optimizations must carefully preserve the sharing if they copy the vector at all. *************** common to two functions. *** 17247,17260 **** * During initial RTL generation, shared structure is freely introduced. After all the RTL for a function has been generated, ! all shared structure is copied by 'unshare_all_rtl' in ! 'emit-rtl.c', after which the above rules are guaranteed to be followed. * During the combiner pass, shared structure within an insn can exist temporarily. However, the shared structure is copied before the combiner is finished with the insn. This is done by calling ! 'copy_rtx_if_shared', which is a subroutine of 'unshare_all_rtl'.  File: gccint.info, Node: Reading RTL, Prev: Sharing, Up: RTL --- 17420,17433 ---- * During initial RTL generation, shared structure is freely introduced. After all the RTL for a function has been generated, ! all shared structure is copied by `unshare_all_rtl' in ! `emit-rtl.c', after which the above rules are guaranteed to be followed. * During the combiner pass, shared structure within an insn can exist temporarily. However, the shared structure is copied before the combiner is finished with the insn. This is done by calling ! `copy_rtx_if_shared', which is a subroutine of `unshare_all_rtl'.  File: gccint.info, Node: Reading RTL, Prev: Sharing, Up: RTL *************** File: gccint.info, Node: Reading RTL, *** 17262,17272 **** 13.22 Reading RTL ================= ! To read an RTL object from a file, call 'read_rtx'. It takes one argument, a stdio stream, and returns a single RTL object. This routine ! is defined in 'read-rtl.c'. It is not available in the compiler itself, ! only the various programs that generate the compiler back end from the ! machine description. People frequently have the idea of using RTL stored as text in a file as an interface between a language front end and the bulk of GCC. This --- 17435,17445 ---- 13.22 Reading RTL ================= ! To read an RTL object from a file, call `read_rtx'. It takes one argument, a stdio stream, and returns a single RTL object. This routine ! is defined in `read-rtl.c'. It is not available in the compiler ! itself, only the various programs that generate the compiler back end ! from the machine description. People frequently have the idea of using RTL stored as text in a file as an interface between a language front end and the bulk of GCC. This *************** idea is not feasible. *** 17276,17284 **** program is very dependent on the particular target machine. And the RTL does not contain all the information about the program. ! The proper way to interface GCC to a new language front end is with the ! "tree" data structure, described in the files 'tree.h' and 'tree.def'. ! The documentation for this structure (*note GENERIC::) is incomplete.  File: gccint.info, Node: Control Flow, Next: Loop Analysis and Representation, Prev: RTL, Up: Top --- 17449,17458 ---- program is very dependent on the particular target machine. And the RTL does not contain all the information about the program. ! The proper way to interface GCC to a new language front end is with ! the "tree" data structure, described in the files `tree.h' and ! `tree.def'. The documentation for this structure (*note GENERIC::) is ! incomplete.  File: gccint.info, Node: Control Flow, Next: Loop Analysis and Representation, Prev: RTL, Up: Top *************** File: gccint.info, Node: Control Flow, *** 17287,17307 **** ********************* A control flow graph (CFG) is a data structure built on top of the ! intermediate code representation (the RTL or 'GIMPLE' instruction stream) abstracting the control flow behavior of a function that is being compiled. The CFG is a directed graph where the vertices represent basic blocks and edges represent possible transfer of control flow from one basic block to another. The data structures used to ! represent the control flow graph are defined in 'basic-block.h'. ! In GCC, the representation of control flow is maintained throughout the ! compilation process, from constructing the CFG early in 'pass_build_cfg' ! to 'pass_free_cfg' (see 'passes.def'). The CFG takes various different ! modes and may undergo extensive manipulations, but the graph is always ! valid between its construction and its release. This way, transfer of ! information such as data flow, a measured profile, or the loop tree, can ! be propagated through the passes pipeline, and even from 'GIMPLE' to ! 'RTL'. Often the CFG may be better viewed as integral part of instruction chain, than structure built on the top of it. Updating the compiler's --- 17461,17481 ---- ********************* A control flow graph (CFG) is a data structure built on top of the ! intermediate code representation (the RTL or `GIMPLE' instruction stream) abstracting the control flow behavior of a function that is being compiled. The CFG is a directed graph where the vertices represent basic blocks and edges represent possible transfer of control flow from one basic block to another. The data structures used to ! represent the control flow graph are defined in `basic-block.h'. ! In GCC, the representation of control flow is maintained throughout ! the compilation process, from constructing the CFG early in ! `pass_build_cfg' to `pass_free_cfg' (see `passes.def'). The CFG takes ! various different modes and may undergo extensive manipulations, but ! the graph is always valid between its construction and its release. ! This way, transfer of information such as data flow, a measured ! profile, or the loop tree, can be propagated through the passes ! pipeline, and even from `GIMPLE' to `RTL'. Often the CFG may be better viewed as integral part of instruction chain, than structure built on the top of it. Updating the compiler's *************** File: gccint.info, Node: Basic Blocks, *** 17323,17372 **** ================= A basic block is a straight-line sequence of code with only one entry ! point and only one exit. In GCC, basic blocks are represented using the ! 'basic_block' data type. Special basic blocks represent possible entry and exit points of a ! function. These blocks are called 'ENTRY_BLOCK_PTR' and ! 'EXIT_BLOCK_PTR'. These blocks do not contain any code. ! The 'BASIC_BLOCK' array contains all basic blocks in an unspecified ! order. Each 'basic_block' structure has a field that holds a unique ! integer identifier 'index' that is the index of the block in the ! 'BASIC_BLOCK' array. The total number of basic blocks in the function ! is 'n_basic_blocks'. Both the basic block indices and the total number of basic blocks may vary during the compilation process, as passes ! reorder, create, duplicate, and destroy basic blocks. The index for any ! block should never be greater than 'last_basic_block'. The indices 0 ! and 1 are special codes reserved for 'ENTRY_BLOCK' and 'EXIT_BLOCK', the ! indices of 'ENTRY_BLOCK_PTR' and 'EXIT_BLOCK_PTR'. ! Two pointer members of the 'basic_block' structure are the pointers ! 'next_bb' and 'prev_bb'. These are used to keep doubly linked chain of basic blocks in the same order as the underlying instruction stream. The chain of basic blocks is updated transparently by the provided API ! for manipulating the CFG. The macro 'FOR_EACH_BB' can be used to visit ! all the basic blocks in lexicographical order, except 'ENTRY_BLOCK' and ! 'EXIT_BLOCK'. The macro 'FOR_ALL_BB' also visits all basic blocks in ! lexicographical order, including 'ENTRY_BLOCK' and 'EXIT_BLOCK'. ! The functions 'post_order_compute' and 'inverted_post_order_compute' ! can be used to compute topological orders of the CFG. The orders are ! stored as vectors of basic block indices. The 'BASIC_BLOCK' array can be used to iterate each basic block by index. Dominator traversals are ! also possible using 'walk_dominator_tree'. Given two basic blocks A and ! B, block A dominates block B if A is _always_ executed before B. ! Each 'basic_block' also contains pointers to the first instruction (the ! "head") and the last instruction (the "tail") or "end" of the instruction stream contained in a basic block. In fact, since the ! 'basic_block' data type is used to represent blocks in both major ! intermediate representations of GCC ('GIMPLE' and RTL), there are pointers to the head and end of a basic block for both representations, ! stored in intermediate representation specific data in the 'il' field of ! 'struct basic_block_def'. ! For RTL, these pointers are 'BB_HEAD' and 'BB_END'. In the RTL representation of a function, the instruction stream contains not only the "real" instructions, but also "notes" or "insn --- 17497,17546 ---- ================= A basic block is a straight-line sequence of code with only one entry ! point and only one exit. In GCC, basic blocks are represented using ! the `basic_block' data type. Special basic blocks represent possible entry and exit points of a ! function. These blocks are called `ENTRY_BLOCK_PTR' and ! `EXIT_BLOCK_PTR'. These blocks do not contain any code. ! The `BASIC_BLOCK' array contains all basic blocks in an unspecified ! order. Each `basic_block' structure has a field that holds a unique ! integer identifier `index' that is the index of the block in the ! `BASIC_BLOCK' array. The total number of basic blocks in the function ! is `n_basic_blocks'. Both the basic block indices and the total number of basic blocks may vary during the compilation process, as passes ! reorder, create, duplicate, and destroy basic blocks. The index for ! any block should never be greater than `last_basic_block'. The indices ! 0 and 1 are special codes reserved for `ENTRY_BLOCK' and `EXIT_BLOCK', ! the indices of `ENTRY_BLOCK_PTR' and `EXIT_BLOCK_PTR'. ! Two pointer members of the `basic_block' structure are the pointers ! `next_bb' and `prev_bb'. These are used to keep doubly linked chain of basic blocks in the same order as the underlying instruction stream. The chain of basic blocks is updated transparently by the provided API ! for manipulating the CFG. The macro `FOR_EACH_BB' can be used to visit ! all the basic blocks in lexicographical order, except `ENTRY_BLOCK' and ! `EXIT_BLOCK'. The macro `FOR_ALL_BB' also visits all basic blocks in ! lexicographical order, including `ENTRY_BLOCK' and `EXIT_BLOCK'. ! The functions `post_order_compute' and `inverted_post_order_compute' ! can be used to compute topological orders of the CFG. The orders are ! stored as vectors of basic block indices. The `BASIC_BLOCK' array can be used to iterate each basic block by index. Dominator traversals are ! also possible using `walk_dominator_tree'. Given two basic blocks A ! and B, block A dominates block B if A is _always_ executed before B. ! Each `basic_block' also contains pointers to the first instruction ! (the "head") and the last instruction (the "tail") or "end" of the instruction stream contained in a basic block. In fact, since the ! `basic_block' data type is used to represent blocks in both major ! intermediate representations of GCC (`GIMPLE' and RTL), there are pointers to the head and end of a basic block for both representations, ! stored in intermediate representation specific data in the `il' field ! of `struct basic_block_def'. ! For RTL, these pointers are `BB_HEAD' and `BB_END'. In the RTL representation of a function, the instruction stream contains not only the "real" instructions, but also "notes" or "insn *************** notes" (to distinguish them from "reg no *** 17374,17409 **** or duplicates the basic blocks needs to take care of updating of these notes. Many of these notes expect that the instruction stream consists of linear regions, so updating can sometimes be tedious. All types of ! insn notes are defined in 'insn-notes.def'. In the RTL function representation, the instructions contained in a ! basic block always follow a 'NOTE_INSN_BASIC_BLOCK', but zero or more ! 'CODE_LABEL' nodes can precede the block note. A basic block ends with a control flow instruction or with the last instruction before the next ! 'CODE_LABEL' or 'NOTE_INSN_BASIC_BLOCK'. By definition, a 'CODE_LABEL' cannot appear in the middle of the instruction stream of a basic block. In addition to notes, the jump table vectors are also represented as "pseudo-instructions" inside the insn stream. These vectors never appear in the basic block and should always be placed just after the ! table jump instructions referencing them. After removing the table-jump ! it is often difficult to eliminate the code computing the address and ! referencing the vector, so cleaning up these vectors is postponed until ! after liveness analysis. Thus the jump table vectors may appear in the ! insn stream unreferenced and without any purpose. Before any edge is ! made "fall-thru", the existence of such construct in the way needs to be ! checked by calling 'can_fallthru' function. ! For the 'GIMPLE' representation, the PHI nodes and statements contained ! in a basic block are in a 'gimple_seq' pointed to by the basic block ! intermediate language specific pointers. Abstract containers and ! iterators are used to access the PHI nodes and statements in a basic ! blocks. These iterators are called "GIMPLE statement iterators" (GSIs). ! Grep for '^gsi' in the various 'gimple-*' and 'tree-*' files. There is ! a 'gimple_stmt_iterator' type for iterating over all kinds of statement, ! and a 'gphi_iterator' subclass for iterating over PHI nodes. The ! following snippet will pretty-print all PHI nodes the statements of the ! current function in the GIMPLE representation. basic_block bb; --- 17548,17584 ---- or duplicates the basic blocks needs to take care of updating of these notes. Many of these notes expect that the instruction stream consists of linear regions, so updating can sometimes be tedious. All types of ! insn notes are defined in `insn-notes.def'. In the RTL function representation, the instructions contained in a ! basic block always follow a `NOTE_INSN_BASIC_BLOCK', but zero or more ! `CODE_LABEL' nodes can precede the block note. A basic block ends with a control flow instruction or with the last instruction before the next ! `CODE_LABEL' or `NOTE_INSN_BASIC_BLOCK'. By definition, a `CODE_LABEL' cannot appear in the middle of the instruction stream of a basic block. In addition to notes, the jump table vectors are also represented as "pseudo-instructions" inside the insn stream. These vectors never appear in the basic block and should always be placed just after the ! table jump instructions referencing them. After removing the ! table-jump it is often difficult to eliminate the code computing the ! address and referencing the vector, so cleaning up these vectors is ! postponed until after liveness analysis. Thus the jump table vectors ! may appear in the insn stream unreferenced and without any purpose. ! Before any edge is made "fall-thru", the existence of such construct in ! the way needs to be checked by calling `can_fallthru' function. ! For the `GIMPLE' representation, the PHI nodes and statements ! contained in a basic block are in a `gimple_seq' pointed to by the ! basic block intermediate language specific pointers. Abstract ! containers and iterators are used to access the PHI nodes and ! statements in a basic blocks. These iterators are called "GIMPLE ! statement iterators" (GSIs). Grep for `^gsi' in the various `gimple-*' ! and `tree-*' files. There is a `gimple_stmt_iterator' type for ! iterating over all kinds of statement, and a `gphi_iterator' subclass ! for iterating over PHI nodes. The following snippet will pretty-print ! all PHI nodes the statements of the current function in the GIMPLE ! representation. basic_block bb; *************** File: gccint.info, Node: Edges, Next: *** 17433,17484 **** Edges represent possible control flow transfers from the end of some basic block A to the head of another basic block B. We say that A is a predecessor of B, and B is a successor of A. Edges are represented in ! GCC with the 'edge' data type. Each 'edge' acts as a link between two ! basic blocks: The 'src' member of an edge points to the predecessor ! basic block of the 'dest' basic block. The members 'preds' and 'succs' ! of the 'basic_block' data type point to type-safe vectors of edges to the predecessors and successors of the block. When walking the edges in an edge vector, "edge iterators" should be ! used. Edge iterators are constructed using the 'edge_iterator' data structure and several methods are available to operate on them: ! 'ei_start' ! This function initializes an 'edge_iterator' that points to the first edge in a vector of edges. ! 'ei_last' ! This function initializes an 'edge_iterator' that points to the last edge in a vector of edges. ! 'ei_end_p' ! This predicate is 'true' if an 'edge_iterator' represents the last edge in an edge vector. ! 'ei_one_before_end_p' ! This predicate is 'true' if an 'edge_iterator' represents the second last edge in an edge vector. ! 'ei_next' ! This function takes a pointer to an 'edge_iterator' and makes it point to the next edge in the sequence. ! 'ei_prev' ! This function takes a pointer to an 'edge_iterator' and makes it point to the previous edge in the sequence. ! 'ei_edge' ! This function returns the 'edge' currently pointed to by an ! 'edge_iterator'. ! 'ei_safe_safe' ! This function returns the 'edge' currently pointed to by an ! 'edge_iterator', but returns 'NULL' if the iterator is pointing at the end of the sequence. This function has been provided for ! existing code makes the assumption that a 'NULL' edge indicates the ! end of the sequence. ! The convenience macro 'FOR_EACH_EDGE' can be used to visit all of the edges in a sequence of predecessor or successor edges. It must not be used when an element might be removed during the traversal, otherwise elements will be missed. Here is an example of how to use the macro: --- 17608,17660 ---- Edges represent possible control flow transfers from the end of some basic block A to the head of another basic block B. We say that A is a predecessor of B, and B is a successor of A. Edges are represented in ! GCC with the `edge' data type. Each `edge' acts as a link between two ! basic blocks: The `src' member of an edge points to the predecessor ! basic block of the `dest' basic block. The members `preds' and `succs' ! of the `basic_block' data type point to type-safe vectors of edges to the predecessors and successors of the block. When walking the edges in an edge vector, "edge iterators" should be ! used. Edge iterators are constructed using the `edge_iterator' data structure and several methods are available to operate on them: ! `ei_start' ! This function initializes an `edge_iterator' that points to the first edge in a vector of edges. ! `ei_last' ! This function initializes an `edge_iterator' that points to the last edge in a vector of edges. ! `ei_end_p' ! This predicate is `true' if an `edge_iterator' represents the last edge in an edge vector. ! `ei_one_before_end_p' ! This predicate is `true' if an `edge_iterator' represents the second last edge in an edge vector. ! `ei_next' ! This function takes a pointer to an `edge_iterator' and makes it point to the next edge in the sequence. ! `ei_prev' ! This function takes a pointer to an `edge_iterator' and makes it point to the previous edge in the sequence. ! `ei_edge' ! This function returns the `edge' currently pointed to by an ! `edge_iterator'. ! `ei_safe_safe' ! This function returns the `edge' currently pointed to by an ! `edge_iterator', but returns `NULL' if the iterator is pointing at the end of the sequence. This function has been provided for ! existing code makes the assumption that a `NULL' edge indicates ! the end of the sequence. ! ! The convenience macro `FOR_EACH_EDGE' can be used to visit all of the edges in a sequence of predecessor or successor edges. It must not be used when an element might be removed during the traversal, otherwise elements will be missed. Here is an example of how to use the macro: *************** elements will be missed. Here is an exa *** 17494,17505 **** There are various reasons why control flow may transfer from one block to another. One possibility is that some instruction, for example a ! 'CODE_LABEL', in a linearized instruction stream just always starts a new basic block. In this case a "fall-thru" edge links the basic block ! to the first following basic block. But there are several other reasons ! why edges may be created. The 'flags' field of the 'edge' data type is ! used to store information about the type of edge we are dealing with. ! Each edge is of one of the following types: _jump_ No type flags are set for edges corresponding to jump instructions. --- 17670,17681 ---- There are various reasons why control flow may transfer from one block to another. One possibility is that some instruction, for example a ! `CODE_LABEL', in a linearized instruction stream just always starts a new basic block. In this case a "fall-thru" edge links the basic block ! to the first following basic block. But there are several other ! reasons why edges may be created. The `flags' field of the `edge' data ! type is used to store information about the type of edge we are dealing ! with. Each edge is of one of the following types: _jump_ No type flags are set for edges corresponding to jump instructions. *************** _jump_ *** 17511,17522 **** _fall-thru_ Fall-thru edges are present in case where the basic block may continue execution to the following one without branching. These ! edges have the 'EDGE_FALLTHRU' flag set. Unlike other types of edges, these edges must come into the basic block immediately following in the instruction stream. The function ! 'force_nonfallthru' is available to insert an unconditional jump in ! the case that redirection is needed. Note that this may require ! creation of a new basic block. _exception handling_ Exception handling edges represent possible control transfers from --- 17687,17698 ---- _fall-thru_ Fall-thru edges are present in case where the basic block may continue execution to the following one without branching. These ! edges have the `EDGE_FALLTHRU' flag set. Unlike other types of edges, these edges must come into the basic block immediately following in the instruction stream. The function ! `force_nonfallthru' is available to insert an unconditional jump ! in the case that redirection is needed. Note that this may ! require creation of a new basic block. _exception handling_ Exception handling edges represent possible control transfers from *************** _exception handling_ *** 17525,17558 **** Java and Ada, exceptions like division by zero or segmentation fault are defined and thus each instruction possibly throwing this kind of exception needs to be handled as control flow instruction. ! Exception edges have the 'EDGE_ABNORMAL' and 'EDGE_EH' flags set. When updating the instruction stream it is easy to change possibly trapping instruction to non-trapping, by simply removing the exception edge. The opposite conversion is difficult, but should not happen anyway. The edges can be eliminated via ! 'purge_dead_edges' call. In the RTL representation, the destination of an exception edge is ! specified by 'REG_EH_REGION' note attached to the insn. In case of ! a trapping call the 'EDGE_ABNORMAL_CALL' flag is set too. In the ! 'GIMPLE' representation, this extra flag is not set. ! In the RTL representation, the predicate 'may_trap_p' may be used to check whether instruction still may trap or not. For the tree ! representation, the 'tree_could_trap_p' predicate is available, but ! this predicate only checks for possible memory traps, as in dereferencing an invalid pointer location. _sibling calls_ Sibling calls or tail calls terminate the function in a non-standard way and thus an edge to the exit must be present. ! 'EDGE_SIBCALL' and 'EDGE_ABNORMAL' are set in such case. These edges only exist in the RTL representation. _computed jumps_ Computed jumps contain edges to all labels in the function ! referenced from the code. All those edges have 'EDGE_ABNORMAL' flag set. The edges used to represent computed jumps often cause compile time performance problems, since functions consisting of many taken labels and many computed jumps may have _very_ dense --- 17701,17734 ---- Java and Ada, exceptions like division by zero or segmentation fault are defined and thus each instruction possibly throwing this kind of exception needs to be handled as control flow instruction. ! Exception edges have the `EDGE_ABNORMAL' and `EDGE_EH' flags set. When updating the instruction stream it is easy to change possibly trapping instruction to non-trapping, by simply removing the exception edge. The opposite conversion is difficult, but should not happen anyway. The edges can be eliminated via ! `purge_dead_edges' call. In the RTL representation, the destination of an exception edge is ! specified by `REG_EH_REGION' note attached to the insn. In case ! of a trapping call the `EDGE_ABNORMAL_CALL' flag is set too. In ! the `GIMPLE' representation, this extra flag is not set. ! In the RTL representation, the predicate `may_trap_p' may be used to check whether instruction still may trap or not. For the tree ! representation, the `tree_could_trap_p' predicate is available, ! but this predicate only checks for possible memory traps, as in dereferencing an invalid pointer location. _sibling calls_ Sibling calls or tail calls terminate the function in a non-standard way and thus an edge to the exit must be present. ! `EDGE_SIBCALL' and `EDGE_ABNORMAL' are set in such case. These edges only exist in the RTL representation. _computed jumps_ Computed jumps contain edges to all labels in the function ! referenced from the code. All those edges have `EDGE_ABNORMAL' flag set. The edges used to represent computed jumps often cause compile time performance problems, since functions consisting of many taken labels and many computed jumps may have _very_ dense *************** _computed jumps_ *** 17589,17616 **** has a runtime cost in there resulting code: An extra jump. Therefore, the computed jumps are un-factored in the later passes of the compiler (in the pass called ! 'pass_duplicate_computed_gotos'). Be aware of that when you work on passes in that area. There have been numerous examples already where the compile time for code with unfactored computed jumps caused some serious headaches. _nonlocal goto handlers_ ! GCC allows nested functions to return into caller using a 'goto' to ! a label passed to as an argument to the callee. The labels passed ! to nested functions contain special code to cleanup after function ! call. Such sections of code are referred to as "nonlocal goto ! receivers". If a function contains such nonlocal goto receivers, ! an edge from the call to the label is created with the ! 'EDGE_ABNORMAL' and 'EDGE_ABNORMAL_CALL' flags set. _function entry points_ By definition, execution of function starts at basic block 0, so ! there is always an edge from the 'ENTRY_BLOCK_PTR' to basic block ! 0. There is no 'GIMPLE' representation for alternate entry points at this moment. In RTL, alternate entry points are specified by ! 'CODE_LABEL' with 'LABEL_ALTERNATE_NAME' defined. This feature is ! currently used for multiple entry point prologues and is limited to ! post-reload passes only. This can be used by back-ends to emit alternate prologues for functions called from different contexts. In future full support for multiple entry functions defined by Fortran 90 needs to be implemented. --- 17765,17792 ---- has a runtime cost in there resulting code: An extra jump. Therefore, the computed jumps are un-factored in the later passes of the compiler (in the pass called ! `pass_duplicate_computed_gotos'). Be aware of that when you work on passes in that area. There have been numerous examples already where the compile time for code with unfactored computed jumps caused some serious headaches. _nonlocal goto handlers_ ! GCC allows nested functions to return into caller using a `goto' ! to a label passed to as an argument to the callee. The labels ! passed to nested functions contain special code to cleanup after ! function call. Such sections of code are referred to as "nonlocal ! goto receivers". If a function contains such nonlocal goto ! receivers, an edge from the call to the label is created with the ! `EDGE_ABNORMAL' and `EDGE_ABNORMAL_CALL' flags set. _function entry points_ By definition, execution of function starts at basic block 0, so ! there is always an edge from the `ENTRY_BLOCK_PTR' to basic block ! 0. There is no `GIMPLE' representation for alternate entry points at this moment. In RTL, alternate entry points are specified by ! `CODE_LABEL' with `LABEL_ALTERNATE_NAME' defined. This feature is ! currently used for multiple entry point prologues and is limited ! to post-reload passes only. This can be used by back-ends to emit alternate prologues for functions called from different contexts. In future full support for multiple entry functions defined by Fortran 90 needs to be implemented. *************** _function entry points_ *** 17618,17627 **** _function exits_ In the pre-reload representation a function terminates after the last instruction in the insn chain and no explicit return ! instructions are used. This corresponds to the fall-thru edge into ! exit block. After reload, optimal RTL epilogues are used that use ! explicit (conditional) return instructions that are represented by ! edges with no flags set.  File: gccint.info, Node: Profile information, Next: Maintaining the CFG, Prev: Edges, Up: Control Flow --- 17794,17804 ---- _function exits_ In the pre-reload representation a function terminates after the last instruction in the insn chain and no explicit return ! instructions are used. This corresponds to the fall-thru edge ! into exit block. After reload, optimal RTL epilogues are used ! that use explicit (conditional) return instructions that are ! represented by edges with no flags set. !  File: gccint.info, Node: Profile information, Next: Maintaining the CFG, Prev: Edges, Up: Control Flow *************** instrumentation, executing it on a train *** 17642,17673 **** executions of basic blocks and edges back to the compiler while re-compiling the program to produce the final executable. This method provides very accurate information about where a program spends most of ! its time on the train run. Whether it matches the average run of course ! depends on the choice of train data set, but several studies have shown ! that the behavior of a program usually changes just marginally over ! different data sets. When profile feedback is not available, the compiler may be asked to attempt to predict the behavior of each branch in the program using a ! set of heuristics (see 'predict.def' for details) and compute estimated frequencies of each basic block by propagating the probabilities over the graph. ! Each 'basic_block' contains two integer fields to represent profile ! information: 'frequency' and 'count'. The 'frequency' is an estimation how often is basic block executed within a function. It is represented ! as an integer scaled in the range from 0 to 'BB_FREQ_BASE'. The most frequently executed basic block in function is initially set to ! 'BB_FREQ_BASE' and the rest of frequencies are scaled accordingly. During optimization, the frequency of the most frequent basic block can both decrease (for instance by loop unrolling) or grow (for instance by cross-jumping optimization), so scaling sometimes has to be performed multiple times. ! The 'count' contains hard-counted numbers of execution measured during training runs and is nonzero only when profile feedback is available. This value is represented as the host's widest integer (typically a 64 ! bit integer) of the special type 'gcov_type'. Most optimization passes can use only the frequency information of a basic block, but a few passes may want to know hard execution counts. --- 17819,17850 ---- executions of basic blocks and edges back to the compiler while re-compiling the program to produce the final executable. This method provides very accurate information about where a program spends most of ! its time on the train run. Whether it matches the average run of ! course depends on the choice of train data set, but several studies ! have shown that the behavior of a program usually changes just ! marginally over different data sets. When profile feedback is not available, the compiler may be asked to attempt to predict the behavior of each branch in the program using a ! set of heuristics (see `predict.def' for details) and compute estimated frequencies of each basic block by propagating the probabilities over the graph. ! Each `basic_block' contains two integer fields to represent profile ! information: `frequency' and `count'. The `frequency' is an estimation how often is basic block executed within a function. It is represented ! as an integer scaled in the range from 0 to `BB_FREQ_BASE'. The most frequently executed basic block in function is initially set to ! `BB_FREQ_BASE' and the rest of frequencies are scaled accordingly. During optimization, the frequency of the most frequent basic block can both decrease (for instance by loop unrolling) or grow (for instance by cross-jumping optimization), so scaling sometimes has to be performed multiple times. ! The `count' contains hard-counted numbers of execution measured during training runs and is nonzero only when profile feedback is available. This value is represented as the host's widest integer (typically a 64 ! bit integer) of the special type `gcov_type'. Most optimization passes can use only the frequency information of a basic block, but a few passes may want to know hard execution counts. *************** during updating of the profile informati *** 17676,17691 **** accumulate into quite large errors. Each edge also contains a branch probability field: an integer in the ! range from 0 to 'REG_BR_PROB_BASE'. It represents probability of ! passing control from the end of the 'src' basic block to the 'dest' basic block, i.e. the probability that control will flow along this ! edge. The 'EDGE_FREQUENCY' macro is available to compute how frequently ! a given edge is taken. There is a 'count' field for each edge as well, ! representing same information as for a basic block. The basic block frequencies are not represented in the instruction stream, but in the RTL representation the edge frequencies are ! represented for conditional jumps (via the 'REG_BR_PROB' macro) since they are used when instructions are output to the assembly file and the flow graph is no longer maintained. --- 17853,17868 ---- accumulate into quite large errors. Each edge also contains a branch probability field: an integer in the ! range from 0 to `REG_BR_PROB_BASE'. It represents probability of ! passing control from the end of the `src' basic block to the `dest' basic block, i.e. the probability that control will flow along this ! edge. The `EDGE_FREQUENCY' macro is available to compute how ! frequently a given edge is taken. There is a `count' field for each ! edge as well, representing same information as for a basic block. The basic block frequencies are not represented in the instruction stream, but in the RTL representation the edge frequencies are ! represented for conditional jumps (via the `REG_BR_PROB' macro) since they are used when instructions are output to the assembly file and the flow graph is no longer maintained. *************** basic blocks. *** 17697,17715 **** Updating profile information is a delicate task that can unfortunately not be easily integrated with the CFG manipulation API. Many of the functions and hooks to modify the CFG, such as ! 'redirect_edge_and_branch', do not have enough information to easily update the profile, so updating it is in the majority of cases left up to the caller. It is difficult to uncover bugs in the profile updating ! code, because they manifest themselves only by producing worse code, and ! checking profile consistency is not possible because of numeric error ! accumulation. Hence special attention needs to be given to this issue ! in each pass that modifies the CFG. ! It is important to point out that 'REG_BR_PROB_BASE' and 'BB_FREQ_BASE' ! are both set low enough to be possible to compute second power of any ! frequency or probability in the flow graph, it is not possible to even ! square the 'count' field, as modern CPUs are fast enough to execute ! $2^32$ operations quickly.  File: gccint.info, Node: Maintaining the CFG, Next: Liveness information, Prev: Profile information, Up: Control Flow --- 17874,17892 ---- Updating profile information is a delicate task that can unfortunately not be easily integrated with the CFG manipulation API. Many of the functions and hooks to modify the CFG, such as ! `redirect_edge_and_branch', do not have enough information to easily update the profile, so updating it is in the majority of cases left up to the caller. It is difficult to uncover bugs in the profile updating ! code, because they manifest themselves only by producing worse code, ! and checking profile consistency is not possible because of numeric ! error accumulation. Hence special attention needs to be given to this ! issue in each pass that modifies the CFG. ! It is important to point out that `REG_BR_PROB_BASE' and ! `BB_FREQ_BASE' are both set low enough to be possible to compute second ! power of any frequency or probability in the flow graph, it is not ! possible to even square the `count' field, as modern CPUs are fast ! enough to execute $2^32$ operations quickly.  File: gccint.info, Node: Maintaining the CFG, Next: Liveness information, Prev: Profile information, Up: Control Flow *************** File: gccint.info, Node: Maintaining th *** 17717,17834 **** 14.4 Maintaining the CFG ======================== ! An important task of each compiler pass is to keep both the control flow ! graph and all profile information up-to-date. Reconstruction of the ! control flow graph after each pass is not an option, since it may be very expensive and lost profile information cannot be reconstructed at all. GCC has two major intermediate representations, and both use the ! 'basic_block' and 'edge' data types to represent control flow. Both representations share as much of the CFG maintenance code as possible. For each representation, a set of "hooks" is defined so that each representation can provide its own implementation of CFG manipulation ! routines when necessary. These hooks are defined in 'cfghooks.h'. ! There are hooks for almost all common CFG manipulations, including block ! splitting and merging, edge redirection and creating and deleting basic ! blocks. These hooks should provide everything you need to maintain and ! manipulate the CFG in both the RTL and 'GIMPLE' representation. At the moment, the basic block boundaries are maintained transparently when modifying instructions, so there rarely is a need to move them manually (such as in case someone wants to output instruction outside basic block explicitly). ! In the RTL representation, each instruction has a 'BLOCK_FOR_INSN' value that represents pointer to the basic block that contains the ! instruction. In the 'GIMPLE' representation, the function 'gimple_bb' returns a pointer to the basic block containing the queried statement. ! When changes need to be applied to a function in its 'GIMPLE' representation, "GIMPLE statement iterators" should be used. These iterators provide an integrated abstraction of the flow graph and the ! instruction stream. Block statement iterators are constructed using the ! 'gimple_stmt_iterator' data structure and several modifiers are available, including the following: ! 'gsi_start' ! This function initializes a 'gimple_stmt_iterator' that points to the first non-empty statement in a basic block. ! 'gsi_last' ! This function initializes a 'gimple_stmt_iterator' that points to the last statement in a basic block. ! 'gsi_end_p' ! This predicate is 'true' if a 'gimple_stmt_iterator' represents the ! end of a basic block. ! 'gsi_next' ! This function takes a 'gimple_stmt_iterator' and makes it point to its successor. ! 'gsi_prev' ! This function takes a 'gimple_stmt_iterator' and makes it point to its predecessor. ! 'gsi_insert_after' ! This function inserts a statement after the 'gimple_stmt_iterator' passed in. The final parameter determines whether the statement iterator is updated to point to the newly inserted statement, or left pointing to the original statement. ! 'gsi_insert_before' ! This function inserts a statement before the 'gimple_stmt_iterator' passed in. The final parameter determines whether the statement iterator is updated to point to the newly inserted statement, or ! left pointing to the original statement. ! 'gsi_remove' ! This function removes the 'gimple_stmt_iterator' passed in and rechains the remaining statements in a basic block, if any. ! In the RTL representation, the macros 'BB_HEAD' and 'BB_END' may be ! used to get the head and end 'rtx' of a basic block. No abstract iterators are defined for traversing the insn chain, but you can just ! use 'NEXT_INSN' and 'PREV_INSN' instead. *Note Insns::. Usually a code manipulating pass simplifies the instruction stream and the flow of control, possibly eliminating some edges. This may for ! example happen when a conditional jump is replaced with an unconditional ! jump, but also when simplifying possibly trapping instruction to ! non-trapping while compiling Java. Updating of edges is not transparent ! and each optimization pass is required to do so manually. However only ! few cases occur in practice. The pass may call 'purge_dead_edges' on a ! given basic block to remove superfluous edges, if any. ! Another common scenario is redirection of branch instructions, but this ! is best modeled as redirection of edges in the control flow graph and ! thus use of 'redirect_edge_and_branch' is preferred over more low level ! functions, such as 'redirect_jump' that operate on RTL chain only. The ! CFG hooks defined in 'cfghooks.h' should provide the complete API ! required for manipulating and maintaining the CFG. It is also possible that a pass has to insert control flow instruction into the middle of a basic block, thus creating an entry point in the middle of the basic block, which is impossible by definition: The block ! must be split to make sure it only has one entry point, i.e. the head of ! the basic block. The CFG hook 'split_block' may be used when an ! instruction in the middle of a basic block has to become the target of a ! jump or branch instruction. For a global optimizer, a common operation is to split edges in the flow graph and insert instructions on them. In the RTL representation, ! this can be easily done using the 'insert_insn_on_edge' function that emits an instruction "on the edge", caching it for a later ! 'commit_edge_insertions' call that will take care of moving the inserted ! instructions off the edge into the instruction stream contained in a ! basic block. This includes the creation of new basic blocks where ! needed. In the 'GIMPLE' representation, the equivalent functions are ! 'gsi_insert_on_edge' which inserts a block statement iterator on an ! edge, and 'gsi_commit_edge_inserts' which flushes the instruction to ! actual instruction stream. ! While debugging the optimization pass, the 'verify_flow_info' function may be useful to find bugs in the control flow graph updating code.  --- 17894,18013 ---- 14.4 Maintaining the CFG ======================== ! An important task of each compiler pass is to keep both the control ! flow graph and all profile information up-to-date. Reconstruction of ! the control flow graph after each pass is not an option, since it may be very expensive and lost profile information cannot be reconstructed at all. GCC has two major intermediate representations, and both use the ! `basic_block' and `edge' data types to represent control flow. Both representations share as much of the CFG maintenance code as possible. For each representation, a set of "hooks" is defined so that each representation can provide its own implementation of CFG manipulation ! routines when necessary. These hooks are defined in `cfghooks.h'. ! There are hooks for almost all common CFG manipulations, including ! block splitting and merging, edge redirection and creating and deleting ! basic blocks. These hooks should provide everything you need to ! maintain and manipulate the CFG in both the RTL and `GIMPLE' ! representation. At the moment, the basic block boundaries are maintained transparently when modifying instructions, so there rarely is a need to move them manually (such as in case someone wants to output instruction outside basic block explicitly). ! In the RTL representation, each instruction has a `BLOCK_FOR_INSN' value that represents pointer to the basic block that contains the ! instruction. In the `GIMPLE' representation, the function `gimple_bb' returns a pointer to the basic block containing the queried statement. ! When changes need to be applied to a function in its `GIMPLE' representation, "GIMPLE statement iterators" should be used. These iterators provide an integrated abstraction of the flow graph and the ! instruction stream. Block statement iterators are constructed using ! the `gimple_stmt_iterator' data structure and several modifiers are available, including the following: ! `gsi_start' ! This function initializes a `gimple_stmt_iterator' that points to the first non-empty statement in a basic block. ! `gsi_last' ! This function initializes a `gimple_stmt_iterator' that points to the last statement in a basic block. ! `gsi_end_p' ! This predicate is `true' if a `gimple_stmt_iterator' represents ! the end of a basic block. ! `gsi_next' ! This function takes a `gimple_stmt_iterator' and makes it point to its successor. ! `gsi_prev' ! This function takes a `gimple_stmt_iterator' and makes it point to its predecessor. ! `gsi_insert_after' ! This function inserts a statement after the `gimple_stmt_iterator' passed in. The final parameter determines whether the statement iterator is updated to point to the newly inserted statement, or left pointing to the original statement. ! `gsi_insert_before' ! This function inserts a statement before the `gimple_stmt_iterator' passed in. The final parameter determines whether the statement iterator is updated to point to the newly inserted statement, or ! left pointing to the original statement. ! `gsi_remove' ! This function removes the `gimple_stmt_iterator' passed in and rechains the remaining statements in a basic block, if any. ! In the RTL representation, the macros `BB_HEAD' and `BB_END' may be ! used to get the head and end `rtx' of a basic block. No abstract iterators are defined for traversing the insn chain, but you can just ! use `NEXT_INSN' and `PREV_INSN' instead. *Note Insns::. Usually a code manipulating pass simplifies the instruction stream and the flow of control, possibly eliminating some edges. This may for ! example happen when a conditional jump is replaced with an ! unconditional jump, but also when simplifying possibly trapping ! instruction to non-trapping while compiling Java. Updating of edges is ! not transparent and each optimization pass is required to do so ! manually. However only few cases occur in practice. The pass may call ! `purge_dead_edges' on a given basic block to remove superfluous edges, ! if any. ! Another common scenario is redirection of branch instructions, but ! this is best modeled as redirection of edges in the control flow graph ! and thus use of `redirect_edge_and_branch' is preferred over more low ! level functions, such as `redirect_jump' that operate on RTL chain ! only. The CFG hooks defined in `cfghooks.h' should provide the ! complete API required for manipulating and maintaining the CFG. It is also possible that a pass has to insert control flow instruction into the middle of a basic block, thus creating an entry point in the middle of the basic block, which is impossible by definition: The block ! must be split to make sure it only has one entry point, i.e. the head ! of the basic block. The CFG hook `split_block' may be used when an ! instruction in the middle of a basic block has to become the target of ! a jump or branch instruction. For a global optimizer, a common operation is to split edges in the flow graph and insert instructions on them. In the RTL representation, ! this can be easily done using the `insert_insn_on_edge' function that emits an instruction "on the edge", caching it for a later ! `commit_edge_insertions' call that will take care of moving the ! inserted instructions off the edge into the instruction stream ! contained in a basic block. This includes the creation of new basic ! blocks where needed. In the `GIMPLE' representation, the equivalent ! functions are `gsi_insert_on_edge' which inserts a block statement ! iterator on an edge, and `gsi_commit_edge_inserts' which flushes the ! instruction to actual instruction stream. ! While debugging the optimization pass, the `verify_flow_info' function may be useful to find bugs in the control flow graph updating code.  *************** File: gccint.info, Node: Liveness infor *** 17838,17873 **** ========================= Liveness information is useful to determine whether some register is ! "live" at given point of program, i.e. that it contains a value that may ! be used at a later point in the program. This information is used, for ! instance, during register allocation, as the pseudo registers only need ! to be assigned to a unique hard register or to a stack slot if they are ! live. The hard registers and stack slots may be freely reused for other ! values when a register is dead. Liveness information is available in the back end starting with ! 'pass_df_initialize' and ending with 'pass_df_finish'. Three flavors of ! live analysis are available: With 'LR', it is possible to determine at ! any point 'P' in the function if the register may be used on some path ! from 'P' to the end of the function. With 'UR', it is possible to ! determine if there is a path from the beginning of the function to 'P' ! that defines the variable. 'LIVE' is the intersection of the 'LR' and ! 'UR' and a variable is live at 'P' if there is both an assignment that reaches it from the beginning of the function and a use that can be ! reached on some path from 'P' to the end of the function. ! In general 'LIVE' is the most useful of the three. The macros ! 'DF_[LR,UR,LIVE]_[IN,OUT]' can be used to access this information. The macros take a basic block number and return a bitmap that is indexed by the register number. This information is only guaranteed to be up to ! date after calls are made to 'df_analyze'. See the file 'df-core.c' for ! details on using the dataflow. The liveness information is stored partly in the RTL instruction stream and partly in the flow graph. Local information is stored in the ! instruction stream: Each instruction may contain 'REG_DEAD' notes representing that the value of a given register is no longer needed, or ! 'REG_UNUSED' notes representing that the value computed by the instruction is never used. The second is useful for instructions computing multiple values at once. --- 18017,18052 ---- ========================= Liveness information is useful to determine whether some register is ! "live" at given point of program, i.e. that it contains a value that ! may be used at a later point in the program. This information is used, ! for instance, during register allocation, as the pseudo registers only ! need to be assigned to a unique hard register or to a stack slot if ! they are live. The hard registers and stack slots may be freely reused ! for other values when a register is dead. Liveness information is available in the back end starting with ! `pass_df_initialize' and ending with `pass_df_finish'. Three flavors ! of live analysis are available: With `LR', it is possible to determine ! at any point `P' in the function if the register may be used on some ! path from `P' to the end of the function. With `UR', it is possible to ! determine if there is a path from the beginning of the function to `P' ! that defines the variable. `LIVE' is the intersection of the `LR' and ! `UR' and a variable is live at `P' if there is both an assignment that reaches it from the beginning of the function and a use that can be ! reached on some path from `P' to the end of the function. ! In general `LIVE' is the most useful of the three. The macros ! `DF_[LR,UR,LIVE]_[IN,OUT]' can be used to access this information. The macros take a basic block number and return a bitmap that is indexed by the register number. This information is only guaranteed to be up to ! date after calls are made to `df_analyze'. See the file `df-core.c' ! for details on using the dataflow. The liveness information is stored partly in the RTL instruction stream and partly in the flow graph. Local information is stored in the ! instruction stream: Each instruction may contain `REG_DEAD' notes representing that the value of a given register is no longer needed, or ! `REG_UNUSED' notes representing that the value computed by the instruction is never used. The second is useful for instructions computing multiple values at once. *************** File: gccint.info, Node: Loop represent *** 17902,17910 **** This chapter describes the representation of loops in GCC, and functions that can be used to build, modify and analyze this representation. Most ! of the interfaces and data structures are declared in 'cfgloop.h'. Loop ! structures are analyzed and this information disposed or updated at the ! discretion of individual passes. Still most of the generic CFG manipulation routines are aware of loop structures and try to keep them up-to-date. By this means an increasing part of the compilation pipeline is setup to maintain loop structure across passes to allow --- 18081,18089 ---- This chapter describes the representation of loops in GCC, and functions that can be used to build, modify and analyze this representation. Most ! of the interfaces and data structures are declared in `cfgloop.h'. ! Loop structures are analyzed and this information disposed or updated ! at the discretion of individual passes. Still most of the generic CFG manipulation routines are aware of loop structures and try to keep them up-to-date. By this means an increasing part of the compilation pipeline is setup to maintain loop structure across passes to allow *************** correspond to sub-loops or to control fl *** 17924,17930 **** that the analysis sometimes changes the CFG, and if you run it in the middle of an optimization pass, you must be able to deal with the new blocks. You may avoid CFG changes by passing ! 'LOOPS_MAY_HAVE_MULTIPLE_LATCHES' flag to the loop discovery, note however that most other loop manipulation functions will not work correctly for loops with multiple latch edges (the functions that only query membership of blocks to loops and subloop relationships, or --- 18103,18109 ---- that the analysis sometimes changes the CFG, and if you run it in the middle of an optimization pass, you must be able to deal with the new blocks. You may avoid CFG changes by passing ! `LOOPS_MAY_HAVE_MULTIPLE_LATCHES' flag to the loop discovery, note however that most other loop manipulation functions will not work correctly for loops with multiple latch edges (the functions that only query membership of blocks to loops and subloop relationships, or *************** enumerate and test loop exits, can be ex *** 17934,17990 **** and reachable from its latch against the direction of edges in CFG. The loops are organized in a containment hierarchy (tree) such that all the loops immediately contained inside loop L are the children of L in the ! tree. This tree is represented by the 'struct loops' structure. The root of this tree is a fake loop that contains all blocks in the ! function. Each of the loops is represented in a 'struct loop' ! structure. Each loop is assigned an index ('num' field of the 'struct loop' structure), and the pointer to the loop is stored in the ! corresponding field of the 'larray' vector in the loops structure. The ! indices do not have to be continuous, there may be empty ('NULL') ! entries in the 'larray' created by deleting loops. Also, there is no guarantee on the relative order of a loop and its subloops in the numbering. The index of a loop never changes. ! The entries of the 'larray' field should not be accessed directly. The ! function 'get_loop' returns the loop description for a loop with the ! given index. 'number_of_loops' function returns number of loops in the ! function. To traverse all loops, use 'FOR_EACH_LOOP' macro. The ! 'flags' argument of the macro is used to determine the direction of traversal and the set of loops visited. Each loop is guaranteed to be visited exactly once, regardless of the changes to the loop tree, and the loops may be removed during the traversal. The newly created loops are never traversed, if they need to be visited, this must be done ! separately after their creation. The 'FOR_EACH_LOOP' macro allocates ! temporary variables. If the 'FOR_EACH_LOOP' loop were ended using break ! or goto, they would not be released; 'FOR_EACH_LOOP_BREAK' macro must be ! used instead. Each basic block contains the reference to the innermost loop it ! belongs to ('loop_father'). For this reason, it is only possible to ! have one 'struct loops' structure initialized at the same time for each ! CFG. The global variable 'current_loops' contains the 'struct loops' structure. Many of the loop manipulation functions assume that dominance information is up-to-date. ! The loops are analyzed through 'loop_optimizer_init' function. The argument of this function is a set of flags represented in an integer bitmask. These flags specify what other properties of the loop structures should be calculated/enforced and preserved later: ! * 'LOOPS_MAY_HAVE_MULTIPLE_LATCHES': If this flag is set, no changes ! to CFG will be performed in the loop analysis, in particular, loops ! with multiple latch edges will not be disambiguated. If a loop has ! multiple latches, its latch block is set to NULL. Most of the loop ! manipulation functions will not work for loops in this shape. No ! other flags that require CFG changes can be passed to loop_optimizer_init. ! * 'LOOPS_HAVE_PREHEADERS': Forwarder blocks are created in such a way ! that each loop has only one entry edge, and additionally, the source block of this entry edge has only one successor. This creates a natural place where the code can be moved out of the loop, and ensures that the entry edge of the loop leads from its immediate super-loop. ! * 'LOOPS_HAVE_SIMPLE_LATCHES': Forwarder blocks are created to force the latch block of each loop to have only one successor. This ensures that the latch of the loop does not belong to any of its sub-loops, and makes manipulation with the loops significantly --- 18113,18171 ---- and reachable from its latch against the direction of edges in CFG. The loops are organized in a containment hierarchy (tree) such that all the loops immediately contained inside loop L are the children of L in the ! tree. This tree is represented by the `struct loops' structure. The root of this tree is a fake loop that contains all blocks in the ! function. Each of the loops is represented in a `struct loop' ! structure. Each loop is assigned an index (`num' field of the `struct loop' structure), and the pointer to the loop is stored in the ! corresponding field of the `larray' vector in the loops structure. The ! indices do not have to be continuous, there may be empty (`NULL') ! entries in the `larray' created by deleting loops. Also, there is no guarantee on the relative order of a loop and its subloops in the numbering. The index of a loop never changes. ! The entries of the `larray' field should not be accessed directly. ! The function `get_loop' returns the loop description for a loop with ! the given index. `number_of_loops' function returns number of loops in ! the function. To traverse all loops, use `FOR_EACH_LOOP' macro. The ! `flags' argument of the macro is used to determine the direction of traversal and the set of loops visited. Each loop is guaranteed to be visited exactly once, regardless of the changes to the loop tree, and the loops may be removed during the traversal. The newly created loops are never traversed, if they need to be visited, this must be done ! separately after their creation. The `FOR_EACH_LOOP' macro allocates ! temporary variables. If the `FOR_EACH_LOOP' loop were ended using ! break or goto, they would not be released; `FOR_EACH_LOOP_BREAK' macro ! must be used instead. Each basic block contains the reference to the innermost loop it ! belongs to (`loop_father'). For this reason, it is only possible to ! have one `struct loops' structure initialized at the same time for each ! CFG. The global variable `current_loops' contains the `struct loops' structure. Many of the loop manipulation functions assume that dominance information is up-to-date. ! The loops are analyzed through `loop_optimizer_init' function. The argument of this function is a set of flags represented in an integer bitmask. These flags specify what other properties of the loop structures should be calculated/enforced and preserved later: ! * `LOOPS_MAY_HAVE_MULTIPLE_LATCHES': If this flag is set, no changes ! to CFG will be performed in the loop analysis, in particular, ! loops with multiple latch edges will not be disambiguated. If a ! loop has multiple latches, its latch block is set to NULL. Most of ! the loop manipulation functions will not work for loops in this ! shape. No other flags that require CFG changes can be passed to loop_optimizer_init. ! ! * `LOOPS_HAVE_PREHEADERS': Forwarder blocks are created in such a ! way that each loop has only one entry edge, and additionally, the source block of this entry edge has only one successor. This creates a natural place where the code can be moved out of the loop, and ensures that the entry edge of the loop leads from its immediate super-loop. ! ! * `LOOPS_HAVE_SIMPLE_LATCHES': Forwarder blocks are created to force the latch block of each loop to have only one successor. This ensures that the latch of the loop does not belong to any of its sub-loops, and makes manipulation with the loops significantly *************** structures should be calculated/enforced *** 17992,18029 **** loops are in this shape. Note that with this flag, the "normal" loop without any control flow inside and with one exit consists of two basic blocks. ! * 'LOOPS_HAVE_MARKED_IRREDUCIBLE_REGIONS': Basic blocks and edges in the strongly connected components that are not natural loops (have ! more than one entry block) are marked with 'BB_IRREDUCIBLE_LOOP' ! and 'EDGE_IRREDUCIBLE_LOOP' flags. The flag is not set for blocks and edges that belong to natural loops that are in such an irreducible region (but it is set for the entry and exit edges of such a loop, if they lead to/from this region). ! * 'LOOPS_HAVE_RECORDED_EXITS': The lists of exits are recorded and updated for each loop. This makes some functions (e.g., ! 'get_loop_exit_edges') more efficient. Some functions (e.g., ! 'single_exit') can be used only if the lists of exits are recorded. These properties may also be computed/enforced later, using functions ! 'create_preheaders', 'force_single_succ_latches', ! 'mark_irreducible_loops' and 'record_loop_exits'. The properties can be ! queried using 'loops_state_satisfies_p'. The memory occupied by the loops structures should be freed with ! 'loop_optimizer_finalize' function. When loop structures are setup to be preserved across passes this function reduces the information to be ! kept up-to-date to a minimum (only 'LOOPS_MAY_HAVE_MULTIPLE_LATCHES' set). The CFG manipulation functions in general do not update loop structures. Specialized versions that additionally do so are provided ! for the most common tasks. On GIMPLE, 'cleanup_tree_cfg_loop' function can be used to cleanup CFG while updating the loops structures if ! 'current_loops' is set. ! At the moment loop structure is preserved from the start of GIMPLE loop ! optimizations until the end of RTL loop optimizations. During this time ! a loop can be tracked by its 'struct loop' and number.  File: gccint.info, Node: Loop querying, Next: Loop manipulation, Prev: Loop representation, Up: Loop Analysis and Representation --- 18173,18212 ---- loops are in this shape. Note that with this flag, the "normal" loop without any control flow inside and with one exit consists of two basic blocks. ! ! * `LOOPS_HAVE_MARKED_IRREDUCIBLE_REGIONS': Basic blocks and edges in the strongly connected components that are not natural loops (have ! more than one entry block) are marked with `BB_IRREDUCIBLE_LOOP' ! and `EDGE_IRREDUCIBLE_LOOP' flags. The flag is not set for blocks and edges that belong to natural loops that are in such an irreducible region (but it is set for the entry and exit edges of such a loop, if they lead to/from this region). ! ! * `LOOPS_HAVE_RECORDED_EXITS': The lists of exits are recorded and updated for each loop. This makes some functions (e.g., ! `get_loop_exit_edges') more efficient. Some functions (e.g., ! `single_exit') can be used only if the lists of exits are recorded. These properties may also be computed/enforced later, using functions ! `create_preheaders', `force_single_succ_latches', ! `mark_irreducible_loops' and `record_loop_exits'. The properties can ! be queried using `loops_state_satisfies_p'. The memory occupied by the loops structures should be freed with ! `loop_optimizer_finalize' function. When loop structures are setup to be preserved across passes this function reduces the information to be ! kept up-to-date to a minimum (only `LOOPS_MAY_HAVE_MULTIPLE_LATCHES' set). The CFG manipulation functions in general do not update loop structures. Specialized versions that additionally do so are provided ! for the most common tasks. On GIMPLE, `cleanup_tree_cfg_loop' function can be used to cleanup CFG while updating the loops structures if ! `current_loops' is set. ! At the moment loop structure is preserved from the start of GIMPLE ! loop optimizations until the end of RTL loop optimizations. During ! this time a loop can be tracked by its `struct loop' and number.  File: gccint.info, Node: Loop querying, Next: Loop manipulation, Prev: Loop representation, Up: Loop Analysis and Representation *************** File: gccint.info, Node: Loop querying, *** 18032,18046 **** ================== The functions to query the information about loops are declared in ! 'cfgloop.h'. Some of the information can be taken directly from the ! structures. 'loop_father' field of each basic block contains the innermost loop to that the block belongs. The most useful fields of loop structure (that are kept up-to-date at all times) are: ! * 'header', 'latch': Header and latch basic blocks of the loop. ! * 'num_nodes': Number of basic blocks in the loop (including the basic blocks of the sub-loops). ! * 'outer', 'inner', 'next': The super-loop, the first sub-loop, and the sibling of the loop in the loops tree. There are other fields in the loop structures, many of them used only --- 18215,18231 ---- ================== The functions to query the information about loops are declared in ! `cfgloop.h'. Some of the information can be taken directly from the ! structures. `loop_father' field of each basic block contains the innermost loop to that the block belongs. The most useful fields of loop structure (that are kept up-to-date at all times) are: ! * `header', `latch': Header and latch basic blocks of the loop. ! ! * `num_nodes': Number of basic blocks in the loop (including the basic blocks of the sub-loops). ! ! * `outer', `inner', `next': The super-loop, the first sub-loop, and the sibling of the loop in the loops tree. There are other fields in the loop structures, many of them used only *************** they should not be accessed directly. *** 18049,18082 **** The most important functions to query loop structures are: ! * 'loop_depth': The depth of the loop in the loops tree, i.e., the number of super-loops of the loop. ! * 'flow_loops_dump': Dumps the information about loops to a file. ! * 'verify_loop_structure': Checks consistency of the loop structures. ! * 'loop_latch_edge': Returns the latch edge of a loop. ! * 'loop_preheader_edge': If loops have preheaders, returns the preheader edge of a loop. ! * 'flow_loop_nested_p': Tests whether loop is a sub-loop of another loop. ! * 'flow_bb_inside_loop_p': Tests whether a basic block belongs to a loop (including its sub-loops). ! * 'find_common_loop': Finds the common super-loop of two loops. ! * 'superloop_at_depth': Returns the super-loop of a loop with the given depth. ! * 'tree_num_loop_insns', 'num_loop_insns': Estimates the number of insns in the loop, on GIMPLE and on RTL. ! * 'loop_exit_edge_p': Tests whether edge is an exit from a loop. ! * 'mark_loop_exit_edges': Marks all exit edges of all loops with ! 'EDGE_LOOP_EXIT' flag. ! * 'get_loop_body', 'get_loop_body_in_dom_order', ! 'get_loop_body_in_bfs_order': Enumerates the basic blocks in the loop in depth-first search order in reversed CFG, ordered by dominance relation, and breath-first search order, respectively. ! * 'single_exit': Returns the single exit edge of the loop, or 'NULL' ! if the loop has more than one exit. You can only use this function ! if LOOPS_HAVE_MARKED_SINGLE_EXITS property is used. ! * 'get_loop_exit_edges': Enumerates the exit edges of a loop. ! * 'just_once_each_iteration_p': Returns true if the basic block is executed exactly once during each iteration of a loop (that is, it does not belong to a sub-loop, and it dominates the latch of the loop). --- 18234,18282 ---- The most important functions to query loop structures are: ! * `loop_depth': The depth of the loop in the loops tree, i.e., the number of super-loops of the loop. ! ! * `flow_loops_dump': Dumps the information about loops to a file. ! ! * `verify_loop_structure': Checks consistency of the loop structures. ! ! * `loop_latch_edge': Returns the latch edge of a loop. ! ! * `loop_preheader_edge': If loops have preheaders, returns the preheader edge of a loop. ! ! * `flow_loop_nested_p': Tests whether loop is a sub-loop of another loop. ! ! * `flow_bb_inside_loop_p': Tests whether a basic block belongs to a loop (including its sub-loops). ! ! * `find_common_loop': Finds the common super-loop of two loops. ! ! * `superloop_at_depth': Returns the super-loop of a loop with the given depth. ! ! * `tree_num_loop_insns', `num_loop_insns': Estimates the number of insns in the loop, on GIMPLE and on RTL. ! ! * `loop_exit_edge_p': Tests whether edge is an exit from a loop. ! ! * `mark_loop_exit_edges': Marks all exit edges of all loops with ! `EDGE_LOOP_EXIT' flag. ! ! * `get_loop_body', `get_loop_body_in_dom_order', ! `get_loop_body_in_bfs_order': Enumerates the basic blocks in the loop in depth-first search order in reversed CFG, ordered by dominance relation, and breath-first search order, respectively. ! ! * `single_exit': Returns the single exit edge of the loop, or `NULL' ! if the loop has more than one exit. You can only use this ! function if LOOPS_HAVE_MARKED_SINGLE_EXITS property is used. ! ! * `get_loop_exit_edges': Enumerates the exit edges of a loop. ! ! * `just_once_each_iteration_p': Returns true if the basic block is executed exactly once during each iteration of a loop (that is, it does not belong to a sub-loop, and it dominates the latch of the loop). *************** File: gccint.info, Node: Loop manipulat *** 18089,18105 **** The loops tree can be manipulated using the following functions: ! * 'flow_loop_tree_node_add': Adds a node to the tree. ! * 'flow_loop_tree_node_remove': Removes a node from the tree. ! * 'add_bb_to_loop': Adds a basic block to a loop. ! * 'remove_bb_from_loops': Removes a basic block from loops. Most low-level CFG functions update loops automatically. The following functions handle some more complicated cases of CFG manipulations: ! * 'remove_path': Removes an edge and all blocks it dominates. ! * 'split_loop_exit_edge': Splits exit edge of the loop, ensuring that ! PHI node arguments remain in the loop (this ensures that loop-closed SSA form is preserved). Only useful on GIMPLE. Finally, there are some higher-level loop transformations implemented. --- 18289,18309 ---- The loops tree can be manipulated using the following functions: ! * `flow_loop_tree_node_add': Adds a node to the tree. ! ! * `flow_loop_tree_node_remove': Removes a node from the tree. ! ! * `add_bb_to_loop': Adds a basic block to a loop. ! ! * `remove_bb_from_loops': Removes a basic block from loops. Most low-level CFG functions update loops automatically. The following functions handle some more complicated cases of CFG manipulations: ! * `remove_path': Removes an edge and all blocks it dominates. ! ! * `split_loop_exit_edge': Splits exit edge of the loop, ensuring ! that PHI node arguments remain in the loop (this ensures that loop-closed SSA form is preserved). Only useful on GIMPLE. Finally, there are some higher-level loop transformations implemented. *************** While some of them are written so that t *** 18107,18129 **** loops, they are mostly untested in that case, and at the moment, they are only reliable for the innermost loops: ! * 'create_iv': Creates a new induction variable. Only works on ! GIMPLE. 'standard_iv_increment_position' can be used to find a suitable place for the iv increment. ! * 'duplicate_loop_to_header_edge', ! 'tree_duplicate_loop_to_header_edge': These functions (on RTL and on GIMPLE) duplicate the body of the loop prescribed number of times on one of the edges entering loop header, thus performing ! either loop unrolling or loop peeling. 'can_duplicate_loop_p' ! ('can_unroll_loop_p' on GIMPLE) must be true for the duplicated loop. ! * 'loop_version', 'tree_ssa_loop_version': These function create a copy of a loop, and a branch before them that selects one of them depending on the prescribed condition. This is useful for optimizations that need to verify some assumptions in runtime (one of the copies of the loop is usually left unchanged, while the other one is transformed in some way). ! * 'tree_unroll_loop': Unrolls the loop, including peeling the extra iterations to make the number of iterations divisible by unroll factor, updating the exit condition, and removing the exits that now cannot be taken. Works only on GIMPLE. --- 18311,18336 ---- loops, they are mostly untested in that case, and at the moment, they are only reliable for the innermost loops: ! * `create_iv': Creates a new induction variable. Only works on ! GIMPLE. `standard_iv_increment_position' can be used to find a suitable place for the iv increment. ! ! * `duplicate_loop_to_header_edge', ! `tree_duplicate_loop_to_header_edge': These functions (on RTL and on GIMPLE) duplicate the body of the loop prescribed number of times on one of the edges entering loop header, thus performing ! either loop unrolling or loop peeling. `can_duplicate_loop_p' ! (`can_unroll_loop_p' on GIMPLE) must be true for the duplicated loop. ! ! * `loop_version', `tree_ssa_loop_version': These function create a copy of a loop, and a branch before them that selects one of them depending on the prescribed condition. This is useful for optimizations that need to verify some assumptions in runtime (one of the copies of the loop is usually left unchanged, while the other one is transformed in some way). ! ! * `tree_unroll_loop': Unrolls the loop, including peeling the extra iterations to make the number of iterations divisible by unroll factor, updating the exit condition, and removing the exits that now cannot be taken. Works only on GIMPLE. *************** File: gccint.info, Node: LCSSA, Next: *** 18135,18141 **** ========================= Throughout the loop optimizations on tree level, one extra condition is ! enforced on the SSA form: No SSA name is used outside of the loop in that it is defined. The SSA form satisfying this condition is called "loop-closed SSA form" - LCSSA. To enforce LCSSA, PHI nodes must be created at the exits of the loops for the SSA names that are used --- 18342,18348 ---- ========================= Throughout the loop optimizations on tree level, one extra condition is ! enforced on the SSA form: No SSA name is used outside of the loop in that it is defined. The SSA form satisfying this condition is called "loop-closed SSA form" - LCSSA. To enforce LCSSA, PHI nodes must be created at the exits of the loops for the SSA names that are used *************** held in LCSSA, in order to save memory. *** 18148,18172 **** are interested in the values that are defined in the loop and used outside of it, i.e., exactly those for that we create new PHI nodes. * In induction variable analysis, it is not necessary to specify the loop in that the analysis should be performed - the scalar evolution analysis always returns the results with respect to the loop in that the SSA name is defined. * It makes updating of SSA form during loop transformations simpler. ! Without LCSSA, operations like loop unrolling may force creation of ! PHI nodes arbitrarily far from the loop, while in LCSSA, the SSA ! form can be updated locally. However, since we only keep real operands in LCSSA, we cannot use this advantage (we could have local updating of real operands, but it is not much more efficient ! than to use generic SSA form updating for it as well; the amount of ! changes to SSA is the same). However, it also means LCSSA must be updated. This is usually straightforward, unless you create a new value in loop and use it outside, or unless you manipulate loop exit edges (functions are provided to make these manipulations simple). ! 'rewrite_into_loop_closed_ssa' is used to rewrite SSA form to LCSSA, and ! 'verify_loop_closed_ssa' to check that the invariant of LCSSA is preserved.  --- 18355,18381 ---- are interested in the values that are defined in the loop and used outside of it, i.e., exactly those for that we create new PHI nodes. + * In induction variable analysis, it is not necessary to specify the loop in that the analysis should be performed - the scalar evolution analysis always returns the results with respect to the loop in that the SSA name is defined. + * It makes updating of SSA form during loop transformations simpler. ! Without LCSSA, operations like loop unrolling may force creation ! of PHI nodes arbitrarily far from the loop, while in LCSSA, the ! SSA form can be updated locally. However, since we only keep real operands in LCSSA, we cannot use this advantage (we could have local updating of real operands, but it is not much more efficient ! than to use generic SSA form updating for it as well; the amount ! of changes to SSA is the same). However, it also means LCSSA must be updated. This is usually straightforward, unless you create a new value in loop and use it outside, or unless you manipulate loop exit edges (functions are provided to make these manipulations simple). ! `rewrite_into_loop_closed_ssa' is used to rewrite SSA form to LCSSA, ! and `verify_loop_closed_ssa' to check that the invariant of LCSSA is preserved.  *************** variable analysis on GIMPLE. They enabl *** 18180,18216 **** complicated behavior in a simple and consistent way (we only use it to express values of polynomial induction variables, but it is possible to extend it). The interfaces to SCEV analysis are declared in ! 'tree-scalar-evolution.h'. To use scalar evolutions analysis, ! 'scev_initialize' must be used. To stop using SCEV, 'scev_finalize' should be used. SCEV analysis caches results in order to save time and memory. This cache however is made invalid by most of the loop ! transformations, including removal of code. If such a transformation is ! performed, 'scev_reset' must be called to clean the caches. Given an SSA name, its behavior in loops can be analyzed using the ! 'analyze_scalar_evolution' function. The returned SCEV however does not ! have to be fully analyzed and it may contain references to other SSA ! names defined in the loop. To resolve these (potentially recursive) ! references, 'instantiate_parameters' or 'resolve_mixers' functions must ! be used. 'instantiate_parameters' is useful when you use the results of ! SCEV only for some analysis, and when you work with whole nest of loops ! at once. It will try replacing all SSA names by their SCEV in all ! loops, including the super-loops of the current loop, thus providing a ! complete information about the behavior of the variable in the loop ! nest. 'resolve_mixers' is useful if you work with only one loop at a ! time, and if you possibly need to create code based on the value of the ! induction variable. It will only resolve the SSA names defined in the ! current loop, leaving the SSA names defined outside unchanged, even if ! their evolution in the outer loops is known. The SCEV is a normal tree expression, except for the fact that it may ! contain several special tree nodes. One of them is 'SCEV_NOT_KNOWN', used for SSA names whose value cannot be expressed. The other one is ! 'POLYNOMIAL_CHREC'. Polynomial chrec has three arguments - base, step and loop (both base and step may contain further polynomial chrecs). Type of the expression and of base and step must be the same. A ! variable has evolution 'POLYNOMIAL_CHREC(base, step, loop)' if it is (in ! the specified loop) equivalent to 'x_1' in the following example while (...) { --- 18389,18425 ---- complicated behavior in a simple and consistent way (we only use it to express values of polynomial induction variables, but it is possible to extend it). The interfaces to SCEV analysis are declared in ! `tree-scalar-evolution.h'. To use scalar evolutions analysis, ! `scev_initialize' must be used. To stop using SCEV, `scev_finalize' should be used. SCEV analysis caches results in order to save time and memory. This cache however is made invalid by most of the loop ! transformations, including removal of code. If such a transformation ! is performed, `scev_reset' must be called to clean the caches. Given an SSA name, its behavior in loops can be analyzed using the ! `analyze_scalar_evolution' function. The returned SCEV however does ! not have to be fully analyzed and it may contain references to other ! SSA names defined in the loop. To resolve these (potentially ! recursive) references, `instantiate_parameters' or `resolve_mixers' ! functions must be used. `instantiate_parameters' is useful when you ! use the results of SCEV only for some analysis, and when you work with ! whole nest of loops at once. It will try replacing all SSA names by ! their SCEV in all loops, including the super-loops of the current loop, ! thus providing a complete information about the behavior of the ! variable in the loop nest. `resolve_mixers' is useful if you work with ! only one loop at a time, and if you possibly need to create code based ! on the value of the induction variable. It will only resolve the SSA ! names defined in the current loop, leaving the SSA names defined ! outside unchanged, even if their evolution in the outer loops is known. The SCEV is a normal tree expression, except for the fact that it may ! contain several special tree nodes. One of them is `SCEV_NOT_KNOWN', used for SSA names whose value cannot be expressed. The other one is ! `POLYNOMIAL_CHREC'. Polynomial chrec has three arguments - base, step and loop (both base and step may contain further polynomial chrecs). Type of the expression and of base and step must be the same. A ! variable has evolution `POLYNOMIAL_CHREC(base, step, loop)' if it is ! (in the specified loop) equivalent to `x_1' in the following example while (...) { *************** the specified loop) equivalent to 'x_1' *** 18219,18225 **** } Note that this includes the language restrictions on the operations. ! For example, if we compile C code and 'x' has signed type, then the overflow in addition would cause undefined behavior, and we may assume that this does not happen. Hence, the value with this SCEV cannot overflow (which restricts the number of iterations of such a loop). --- 18428,18434 ---- } Note that this includes the language restrictions on the operations. ! For example, if we compile C code and `x' has signed type, then the overflow in addition would cause undefined behavior, and we may assume that this does not happen. Hence, the value with this SCEV cannot overflow (which restricts the number of iterations of such a loop). *************** overflow (which restricts the number of *** 18227,18233 **** In many cases, one wants to restrict the attention just to affine induction variables. In this case, the extra expressive power of SCEV is not useful, and may complicate the optimizations. In this case, ! 'simple_iv' function may be used to analyze a value - the result is a loop-invariant base and step.  --- 18436,18442 ---- In many cases, one wants to restrict the attention just to affine induction variables. In this case, the extra expressive power of SCEV is not useful, and may complicate the optimizations. In this case, ! `simple_iv' function may be used to analyze a value - the result is a loop-invariant base and step.  *************** File: gccint.info, Node: loop-iv, Next *** 18238,18275 **** The induction variable on RTL is simple and only allows analysis of affine induction variables, and only in one loop at once. The interface ! is declared in 'cfgloop.h'. Before analyzing induction variables in a ! loop L, 'iv_analysis_loop_init' function must be called on L. After the ! analysis (possibly calling 'iv_analysis_loop_init' for several loops) is ! finished, 'iv_analysis_done' should be called. The following functions ! can be used to access the results of the analysis: ! * 'iv_analyze': Analyzes a single register used in the given insn. If no use of the register in this insn is found, the following insns are scanned, so that this function can be called on the insn returned by get_condition. - * 'iv_analyze_result': Analyzes result of the assignment in the given - insn. - * 'iv_analyze_expr': Analyzes a more complicated expression. All its - operands are analyzed by 'iv_analyze', and hence they must be used - in the specified insn or one of the following insns. ! The description of the induction variable is provided in 'struct rtx_iv'. In order to handle subregs, the representation is a bit ! complicated; if the value of the 'extend' field is not 'UNKNOWN', the value of the induction variable in the i-th iteration is delta + mult * extend_{extend_mode} (subreg_{mode} (base + i * step)), ! with the following exception: if 'first_special' is true, then the ! value in the first iteration (when 'i' is zero) is 'delta + mult * ! base'. However, if 'extend' is equal to 'UNKNOWN', then 'first_special' ! must be false, 'delta' 0, 'mult' 1 and the value in the i-th iteration ! is subreg_{mode} (base + i * step) ! The function 'get_iv_value' can be used to perform these calculations.  File: gccint.info, Node: Number of iterations, Next: Dependency analysis, Prev: loop-iv, Up: Loop Analysis and Representation --- 18447,18486 ---- The induction variable on RTL is simple and only allows analysis of affine induction variables, and only in one loop at once. The interface ! is declared in `cfgloop.h'. Before analyzing induction variables in a ! loop L, `iv_analysis_loop_init' function must be called on L. After ! the analysis (possibly calling `iv_analysis_loop_init' for several ! loops) is finished, `iv_analysis_done' should be called. The following ! functions can be used to access the results of the analysis: ! * `iv_analyze': Analyzes a single register used in the given insn. If no use of the register in this insn is found, the following insns are scanned, so that this function can be called on the insn returned by get_condition. ! * `iv_analyze_result': Analyzes result of the assignment in the ! given insn. ! ! * `iv_analyze_expr': Analyzes a more complicated expression. All ! its operands are analyzed by `iv_analyze', and hence they must be ! used in the specified insn or one of the following insns. ! ! The description of the induction variable is provided in `struct rtx_iv'. In order to handle subregs, the representation is a bit ! complicated; if the value of the `extend' field is not `UNKNOWN', the value of the induction variable in the i-th iteration is delta + mult * extend_{extend_mode} (subreg_{mode} (base + i * step)), ! with the following exception: if `first_special' is true, then the ! value in the first iteration (when `i' is zero) is `delta + mult * ! base'. However, if `extend' is equal to `UNKNOWN', then ! `first_special' must be false, `delta' 0, `mult' 1 and the value in the ! i-th iteration is subreg_{mode} (base + i * step) ! The function `get_iv_value' can be used to perform these calculations.  File: gccint.info, Node: Number of iterations, Next: Dependency analysis, Prev: loop-iv, Up: Loop Analysis and Representation *************** program; if it fails, the conditions are *** 18288,18326 **** result. The following information and conditions are provided by the analysis: ! * 'assumptions': If this condition is false, the rest of the information is invalid. ! * 'noloop_assumptions' on RTL, 'may_be_zero' on GIMPLE: If this condition is true, the loop exits in the first iteration. ! * 'infinite': If this condition is true, the loop is infinite. This condition is only available on RTL. On GIMPLE, conditions for ! finiteness of the loop are included in 'assumptions'. ! * 'niter_expr' on RTL, 'niter' on GIMPLE: The expression that gives number of iterations. The number of iterations is defined as the number of executions of the loop latch. Both on GIMPLE and on RTL, it necessary for the induction variable analysis framework to be initialized (SCEV on GIMPLE, loop-iv on RTL). ! On GIMPLE, the results are stored to 'struct tree_niter_desc' structure. ! Number of iterations before the loop is exited through a given exit can ! be determined using 'number_of_iterations_exit' function. On RTL, the ! results are returned in 'struct niter_desc' structure. The ! corresponding function is named 'check_simple_exit'. There are also ! functions that pass through all the exits of a loop and try to find one ! with easy to determine number of iterations - 'find_loop_niter' on ! GIMPLE and 'find_simple_exit' on RTL. Finally, there are functions that ! provide the same information, but additionally cache it, so that ! repeated calls to number of iterations are not so costly - ! 'number_of_latch_executions' on GIMPLE and 'get_simple_loop_desc' on ! RTL. Note that some of these functions may behave slightly differently than others - some of them return only the expression for the number of iterations, and fail if there are some assumptions. The function ! 'number_of_latch_executions' works only for single-exit loops. The ! function 'number_of_cond_exit_executions' can be used to determine number of executions of the exit condition of a single-exit loop (i.e., ! the 'number_of_latch_executions' increased by one).  File: gccint.info, Node: Dependency analysis, Prev: Number of iterations, Up: Loop Analysis and Representation --- 18499,18540 ---- result. The following information and conditions are provided by the analysis: ! * `assumptions': If this condition is false, the rest of the information is invalid. ! ! * `noloop_assumptions' on RTL, `may_be_zero' on GIMPLE: If this condition is true, the loop exits in the first iteration. ! ! * `infinite': If this condition is true, the loop is infinite. This condition is only available on RTL. On GIMPLE, conditions for ! finiteness of the loop are included in `assumptions'. ! ! * `niter_expr' on RTL, `niter' on GIMPLE: The expression that gives number of iterations. The number of iterations is defined as the number of executions of the loop latch. Both on GIMPLE and on RTL, it necessary for the induction variable analysis framework to be initialized (SCEV on GIMPLE, loop-iv on RTL). ! On GIMPLE, the results are stored to `struct tree_niter_desc' ! structure. Number of iterations before the loop is exited through a ! given exit can be determined using `number_of_iterations_exit' ! function. On RTL, the results are returned in `struct niter_desc' ! structure. The corresponding function is named `check_simple_exit'. ! There are also functions that pass through all the exits of a loop and ! try to find one with easy to determine number of iterations - ! `find_loop_niter' on GIMPLE and `find_simple_exit' on RTL. Finally, ! there are functions that provide the same information, but additionally ! cache it, so that repeated calls to number of iterations are not so ! costly - `number_of_latch_executions' on GIMPLE and ! `get_simple_loop_desc' on RTL. Note that some of these functions may behave slightly differently than others - some of them return only the expression for the number of iterations, and fail if there are some assumptions. The function ! `number_of_latch_executions' works only for single-exit loops. The ! function `number_of_cond_exit_executions' can be used to determine number of executions of the exit condition of a single-exit loop (i.e., ! the `number_of_latch_executions' increased by one).  File: gccint.info, Node: Dependency analysis, Prev: Number of iterations, Up: Loop Analysis and Representation *************** File: gccint.info, Node: Dependency ana *** 18329,18349 **** ============================= The code for the data dependence analysis can be found in ! 'tree-data-ref.c' and its interface and data structures are described in ! 'tree-data-ref.h'. The function that computes the data dependences for ! all the array and pointer references for a given loop is ! 'compute_data_dependences_for_loop'. This function is currently used by ! the linear loop transform and the vectorization passes. Before calling ! this function, one has to allocate two vectors: a first vector will ! contain the set of data references that are contained in the analyzed ! loop body, and the second vector will contain the dependence relations ! between the data references. Thus if the vector of data references is ! of size 'n', the vector containing the dependence relations will contain ! 'n*n' elements. However if the analyzed loop contains side effects, ! such as calls that potentially can interfere with the data references in ! the current analyzed loop, the analysis stops while scanning the loop ! body for data references, and inserts a single 'chrec_dont_know' in the ! dependence relation array. The data references are discovered in a particular order during the scanning of the loop body: the loop body is analyzed in execution order, --- 18543,18563 ---- ============================= The code for the data dependence analysis can be found in ! `tree-data-ref.c' and its interface and data structures are described ! in `tree-data-ref.h'. The function that computes the data dependences ! for all the array and pointer references for a given loop is ! `compute_data_dependences_for_loop'. This function is currently used ! by the linear loop transform and the vectorization passes. Before ! calling this function, one has to allocate two vectors: a first vector ! will contain the set of data references that are contained in the ! analyzed loop body, and the second vector will contain the dependence ! relations between the data references. Thus if the vector of data ! references is of size `n', the vector containing the dependence ! relations will contain `n*n' elements. However if the analyzed loop ! contains side effects, such as calls that potentially can interfere ! with the data references in the current analyzed loop, the analysis ! stops while scanning the loop body for data references, and inserts a ! single `chrec_dont_know' in the dependence relation array. The data references are discovered in a particular order during the scanning of the loop body: the loop body is analyzed in execution order, *************** and mapping this order to the elements o *** 18355,18390 **** queries to the loop body representation. Three types of data references are currently handled: ARRAY_REF, ! INDIRECT_REF and COMPONENT_REF. The data structure for the data ! reference is 'data_reference', where 'data_reference_p' is a name of a ! pointer to the data reference structure. The structure contains the following elements: ! * 'base_object_info': Provides information about the base object of ! the data reference and its access functions. These access ! functions represent the evolution of the data reference in the loop ! relative to its base, in keeping with the classical meaning of the ! data reference access function for the support of arrays. For ! example, for a reference 'a.b[i][j]', the base object is 'a.b' and ! the access functions, one for each array subscript, are: '{i_init, ! + i_step}_1, {j_init, +, j_step}_2'. ! * 'first_location_in_loop': Provides information about the first location accessed by the data reference in the loop and about the access function used to represent evolution relative to this ! location. This data is used to support pointers, and is not used ! for arrays (for which we have base objects). Pointer accesses are represented as a one-dimensional access that starts from the first ! location accessed in the loop. For example: for1 i for2 j *((int *)p + i + j) = a[i][j]; ! The access function of the pointer access is '{0, + 4B}_for2' ! relative to 'p + i'. The access functions of the array are ! '{i_init, + i_step}_for1' and '{j_init, +, j_step}_for2' relative ! to 'a'. Usually, the object the pointer refers to is either unknown, or we can't prove that the access is confined to the boundaries of a --- 18569,18604 ---- queries to the loop body representation. Three types of data references are currently handled: ARRAY_REF, ! INDIRECT_REF and COMPONENT_REF. The data structure for the data ! reference is `data_reference', where `data_reference_p' is a name of a ! pointer to the data reference structure. The structure contains the following elements: ! * `base_object_info': Provides information about the base object of ! the data reference and its access functions. These access functions ! represent the evolution of the data reference in the loop relative ! to its base, in keeping with the classical meaning of the data ! reference access function for the support of arrays. For example, ! for a reference `a.b[i][j]', the base object is `a.b' and the ! access functions, one for each array subscript, are: `{i_init, + ! i_step}_1, {j_init, +, j_step}_2'. ! * `first_location_in_loop': Provides information about the first location accessed by the data reference in the loop and about the access function used to represent evolution relative to this ! location. This data is used to support pointers, and is not used ! for arrays (for which we have base objects). Pointer accesses are represented as a one-dimensional access that starts from the first ! location accessed in the loop. For example: for1 i for2 j *((int *)p + i + j) = a[i][j]; ! The access function of the pointer access is `{0, + 4B}_for2' ! relative to `p + i'. The access functions of the array are ! `{i_init, + i_step}_for1' and `{j_init, +, j_step}_for2' relative ! to `a'. Usually, the object the pointer refers to is either unknown, or we can't prove that the access is confined to the boundaries of a *************** following elements: *** 18395,18444 **** references. The current strategy for data dependence tests is as follows: If ! both 'a' and 'b' are represented as arrays, compare 'a.base_object' ! and 'b.base_object'; if they are equal, apply dependence tests (use ! access functions based on base_objects). Else if both 'a' and 'b' ! are represented as pointers, compare 'a.first_location' and ! 'b.first_location'; if they are equal, apply dependence tests (use ! access functions based on first location). However, if 'a' and 'b' ! are represented differently, only try to prove that the bases are ! definitely different. * Aliasing information. * Alignment information. The structure describing the relation between two data references is ! 'data_dependence_relation' and the shorter name for a pointer to such a ! structure is 'ddr_p'. This structure contains: * a pointer to each data reference, ! * a tree node 'are_dependent' that is set to 'chrec_known' if the analysis has proved that there is no dependence between these two ! data references, 'chrec_dont_know' if the analysis was not able to determine any useful result and potentially there could exist a ! dependence between these data references, and 'are_dependent' is ! set to 'NULL_TREE' if there exist a dependence relation between the data references, and the description of this dependence relation is ! given in the 'subscripts', 'dir_vects', and 'dist_vects' arrays, * a boolean that determines whether the dependence relation can be represented by a classical distance vector, ! * an array 'subscripts' that contains a description of each subscript ! of the data references. Given two array accesses a subscript is ! the tuple composed of the access functions for a given dimension. ! For example, given 'A[f1][f2][f3]' and 'B[g1][g2][g3]', there are ! three subscripts: '(f1, g1), (f2, g2), (f3, g3)'. ! * two arrays 'dir_vects' and 'dist_vects' that contain classical ! representations of the data dependences under the form of direction ! and distance dependence vectors, ! * an array of loops 'loop_nest' that contains the loops to which the distance and direction vectors refer to. Several functions for pretty printing the information extracted by the ! data dependence analysis are available: 'dump_ddrs' prints with a maximum verbosity the details of a data dependence relations array, ! 'dump_dist_dir_vectors' prints only the classical distance and direction ! vectors for a data dependence relations array, and ! 'dump_data_references' prints the details of the data references contained in a data reference array.  --- 18609,18665 ---- references. The current strategy for data dependence tests is as follows: If ! both `a' and `b' are represented as arrays, compare ! `a.base_object' and `b.base_object'; if they are equal, apply ! dependence tests (use access functions based on base_objects). ! Else if both `a' and `b' are represented as pointers, compare ! `a.first_location' and `b.first_location'; if they are equal, ! apply dependence tests (use access functions based on first ! location). However, if `a' and `b' are represented differently, ! only try to prove that the bases are definitely different. * Aliasing information. + * Alignment information. The structure describing the relation between two data references is ! `data_dependence_relation' and the shorter name for a pointer to such a ! structure is `ddr_p'. This structure contains: * a pointer to each data reference, ! ! * a tree node `are_dependent' that is set to `chrec_known' if the analysis has proved that there is no dependence between these two ! data references, `chrec_dont_know' if the analysis was not able to determine any useful result and potentially there could exist a ! dependence between these data references, and `are_dependent' is ! set to `NULL_TREE' if there exist a dependence relation between the data references, and the description of this dependence relation is ! given in the `subscripts', `dir_vects', and `dist_vects' arrays, ! * a boolean that determines whether the dependence relation can be represented by a classical distance vector, ! ! * an array `subscripts' that contains a description of each ! subscript of the data references. Given two array accesses a ! subscript is the tuple composed of the access functions for a given ! dimension. For example, given `A[f1][f2][f3]' and ! `B[g1][g2][g3]', there are three subscripts: `(f1, g1), (f2, g2), ! (f3, g3)'. ! ! * two arrays `dir_vects' and `dist_vects' that contain classical ! representations of the data dependences under the form of ! direction and distance dependence vectors, ! ! * an array of loops `loop_nest' that contains the loops to which the distance and direction vectors refer to. Several functions for pretty printing the information extracted by the ! data dependence analysis are available: `dump_ddrs' prints with a maximum verbosity the details of a data dependence relations array, ! `dump_dist_dir_vectors' prints only the classical distance and ! direction vectors for a data dependence relations array, and ! `dump_data_references' prints the details of the data references contained in a data reference array.  *************** File: gccint.info, Node: Machine Desc, *** 18448,18456 **** *********************** A machine description has two parts: a file of instruction patterns ! ('.md' file) and a C header file of macro definitions. ! The '.md' file for a target machine contains a pattern for each instruction that the target machine supports (or at least each instruction that is worth telling the compiler about). It may also contain comments. A semicolon causes the rest of the line to be a --- 18669,18677 ---- *********************** A machine description has two parts: a file of instruction patterns ! (`.md' file) and a C header file of macro definitions. ! The `.md' file for a target machine contains a pattern for each instruction that the target machine supports (or at least each instruction that is worth telling the compiler about). It may also contain comments. A semicolon causes the rest of the line to be a *************** comment, unless the semicolon is inside *** 18462,18468 **** * Overview:: How the machine description is used. * Patterns:: How to write instruction patterns. ! * Example:: An explained example of a 'define_insn' pattern. * RTL Template:: The RTL template defines what insns match a pattern. * Output Template:: The output template says how to make assembler code from such an insn. --- 18683,18689 ---- * Overview:: How the machine description is used. * Patterns:: How to write instruction patterns. ! * Example:: An explained example of a `define_insn' pattern. * RTL Template:: The RTL template defines what insns match a pattern. * Output Template:: The output template says how to make assembler code from such an insn. *************** comment, unless the semicolon is inside *** 18483,18491 **** * Including Patterns:: Including Patterns in Machine Descriptions. * Peephole Definitions::Defining machine-specific peephole optimizations. * Insn Attributes:: Specifying the value of attributes for generated insns. ! * Conditional Execution::Generating 'define_insn' patterns for predication. ! * Define Subst:: Generating 'define_insn' and 'define_expand' patterns from other patterns. * Constant Definitions::Defining symbolic constants that can be used in the md file. --- 18704,18712 ---- * Including Patterns:: Including Patterns in Machine Descriptions. * Peephole Definitions::Defining machine-specific peephole optimizations. * Insn Attributes:: Specifying the value of attributes for generated insns. ! * Conditional Execution::Generating `define_insn' patterns for predication. ! * Define Subst:: Generating `define_insn' and `define_expand' patterns from other patterns. * Constant Definitions::Defining symbolic constants that can be used in the md file. *************** There are three main conversions that ha *** 18507,18537 **** 3. The insn list is matched against the RTL templates to produce assembler code. For the generate pass, only the names of the insns matter, from either ! a named 'define_insn' or a 'define_expand'. The compiler will choose the pattern with the right name and apply the operands according to the ! documentation later in this chapter, without regard for the RTL template ! or operand constraints. Note that the names the compiler looks for are ! hard-coded in the compiler--it will ignore unnamed patterns and patterns ! with names it doesn't know about, but if you don't provide a named ! pattern it needs, it will abort. ! If a 'define_insn' is used, the template given is inserted into the ! insn list. If a 'define_expand' is used, one of three things happens, based on the condition logic. The condition logic may manually create ! new insns for the insn list, say via 'emit_insn()', and invoke 'DONE'. ! For certain named patterns, it may invoke 'FAIL' to tell the compiler to ! use an alternate way of performing that task. If it invokes neither ! 'DONE' nor 'FAIL', the template given in the pattern is inserted, as if ! the 'define_expand' were a 'define_insn'. Once the insn list is generated, various optimization passes convert, replace, and rearrange the insns in the insn list. This is where the ! 'define_split' and 'define_peephole' patterns get used, for example. Finally, the insn list's RTL is matched up with the RTL templates in ! the 'define_insn' patterns, and those patterns are used to emit the ! final assembly code. For this purpose, each named 'define_insn' acts like it's unnamed, since the names are ignored.  --- 18728,18759 ---- 3. The insn list is matched against the RTL templates to produce assembler code. + For the generate pass, only the names of the insns matter, from either ! a named `define_insn' or a `define_expand'. The compiler will choose the pattern with the right name and apply the operands according to the ! documentation later in this chapter, without regard for the RTL ! template or operand constraints. Note that the names the compiler looks ! for are hard-coded in the compiler--it will ignore unnamed patterns and ! patterns with names it doesn't know about, but if you don't provide a ! named pattern it needs, it will abort. ! If a `define_insn' is used, the template given is inserted into the ! insn list. If a `define_expand' is used, one of three things happens, based on the condition logic. The condition logic may manually create ! new insns for the insn list, say via `emit_insn()', and invoke `DONE'. ! For certain named patterns, it may invoke `FAIL' to tell the compiler ! to use an alternate way of performing that task. If it invokes neither ! `DONE' nor `FAIL', the template given in the pattern is inserted, as if ! the `define_expand' were a `define_insn'. Once the insn list is generated, various optimization passes convert, replace, and rearrange the insns in the insn list. This is where the ! `define_split' and `define_peephole' patterns get used, for example. Finally, the insn list's RTL is matched up with the RTL templates in ! the `define_insn' patterns, and those patterns are used to emit the ! final assembly code. For this purpose, each named `define_insn' acts like it's unnamed, since the names are ignored.  *************** File: gccint.info, Node: Patterns, Nex *** 18540,18598 **** 16.2 Everything about Instruction Patterns ========================================== ! A 'define_insn' expression is used to define instruction patterns to ! which insns may be matched. A 'define_insn' expression contains an incomplete RTL expression, with pieces to be filled in later, operand constraints that restrict how the pieces can be filled in, and an output template or C code to generate the assembler output. ! A 'define_insn' is an RTL expression containing four or five operands: 1. An optional name. The presence of a name indicate that this instruction pattern can perform a certain standard job for the ! RTL-generation pass of the compiler. This pass knows certain names ! and will use the instruction patterns with those names, if the ! names are defined in the machine description. ! The absence of a name is indicated by writing an empty string where ! the name should go. Nameless instruction patterns are never used ! for generating RTL code, but they may permit several simpler insns ! to be combined later on. Names that are not thus known and used in RTL-generation have no effect; they are equivalent to no name at all. For the purpose of debugging the compiler, you may also specify a ! name beginning with the '*' character. Such a name is used only for identifying the instruction in RTL dumps; it is equivalent to having a nameless pattern for all other purposes. Names beginning ! with the '*' character are not required to be unique. 2. The "RTL template": This is a vector of incomplete RTL expressions which describe the semantics of the instruction (*note RTL Template::). It is incomplete because it may contain ! 'match_operand', 'match_operator', and 'match_dup' expressions that ! stand for operands of the instruction. ! If the vector has multiple elements, the RTL template is treated as ! a 'parallel' expression. 3. The condition: This is a string which contains a C expression. When the compiler attempts to match RTL against a pattern, the ! condition is evaluated. If the condition evaluates to 'true', the ! match is permitted. The condition may be an empty string, which is ! treated as always 'true'. For a named pattern, the condition may not depend on the data in the insn being matched, but only the target-machine-type flags. The compiler needs to test these conditions during initialization ! in order to learn exactly which named instructions are available in ! a particular run. For nameless patterns, the condition is applied only when matching an individual insn, and only after the insn has matched the pattern's recognition template. The insn's operands may be found ! in the vector 'operands'. For an insn where the condition has once matched, it cannot later be used to control register allocation by excluding certain --- 18762,18820 ---- 16.2 Everything about Instruction Patterns ========================================== ! A `define_insn' expression is used to define instruction patterns to ! which insns may be matched. A `define_insn' expression contains an incomplete RTL expression, with pieces to be filled in later, operand constraints that restrict how the pieces can be filled in, and an output template or C code to generate the assembler output. ! A `define_insn' is an RTL expression containing four or five operands: 1. An optional name. The presence of a name indicate that this instruction pattern can perform a certain standard job for the ! RTL-generation pass of the compiler. This pass knows certain ! names and will use the instruction patterns with those names, if ! the names are defined in the machine description. ! The absence of a name is indicated by writing an empty string ! where the name should go. Nameless instruction patterns are never ! used for generating RTL code, but they may permit several simpler ! insns to be combined later on. Names that are not thus known and used in RTL-generation have no effect; they are equivalent to no name at all. For the purpose of debugging the compiler, you may also specify a ! name beginning with the `*' character. Such a name is used only for identifying the instruction in RTL dumps; it is equivalent to having a nameless pattern for all other purposes. Names beginning ! with the `*' character are not required to be unique. 2. The "RTL template": This is a vector of incomplete RTL expressions which describe the semantics of the instruction (*note RTL Template::). It is incomplete because it may contain ! `match_operand', `match_operator', and `match_dup' expressions ! that stand for operands of the instruction. ! If the vector has multiple elements, the RTL template is treated ! as a `parallel' expression. 3. The condition: This is a string which contains a C expression. When the compiler attempts to match RTL against a pattern, the ! condition is evaluated. If the condition evaluates to `true', the ! match is permitted. The condition may be an empty string, which ! is treated as always `true'. For a named pattern, the condition may not depend on the data in the insn being matched, but only the target-machine-type flags. The compiler needs to test these conditions during initialization ! in order to learn exactly which named instructions are available ! in a particular run. For nameless patterns, the condition is applied only when matching an individual insn, and only after the insn has matched the pattern's recognition template. The insn's operands may be found ! in the vector `operands'. For an insn where the condition has once matched, it cannot later be used to control register allocation by excluding certain *************** template or C code to generate the assem *** 18611,18617 ****  File: gccint.info, Node: Example, Next: RTL Template, Prev: Patterns, Up: Machine Desc ! 16.3 Example of 'define_insn' ============================= Here is an example of an instruction pattern, taken from the machine --- 18833,18839 ----  File: gccint.info, Node: Example, Next: RTL Template, Prev: Patterns, Up: Machine Desc ! 16.3 Example of `define_insn' ============================= Here is an example of an instruction pattern, taken from the machine *************** This can also be written using braced st *** 18643,18649 **** This describes an instruction which sets the condition codes based on the value of a general operand. It has no condition, so any insn with an RTL description of the form shown may be matched to this pattern. ! The name 'tstsi' means "test a 'SImode' value" and tells the RTL generation pass that, when it is necessary to test such a value, an insn to do so can be constructed using this pattern. --- 18865,18871 ---- This describes an instruction which sets the condition codes based on the value of a general operand. It has no condition, so any insn with an RTL description of the form shown may be matched to this pattern. ! The name `tstsi' means "test a `SImode' value" and tells the RTL generation pass that, when it is necessary to test such a value, an insn to do so can be constructed using this pattern. *************** to do so can be constructed using this p *** 18651,18657 **** output template to return based on the kind of operand and the specific type of CPU for which code is being generated. ! '"rm"' is an operand constraint. Its meaning is explained below.  File: gccint.info, Node: RTL Template, Next: Output Template, Prev: Example, Up: Machine Desc --- 18873,18879 ---- output template to return based on the kind of operand and the specific type of CPU for which code is being generated. ! `"rm"' is an operand constraint. Its meaning is explained below.  File: gccint.info, Node: RTL Template, Next: Output Template, Prev: Example, Up: Machine Desc *************** the operands in the insn being matched. *** 18669,18766 **** controlled by special expression types that direct matching and substitution of the operands. ! '(match_operand:M N PREDICATE CONSTRAINT)' This expression is a placeholder for operand number N of the insn. When constructing an insn, operand number N will be substituted at this point. When matching an insn, whatever appears at this ! position in the insn will be taken as operand number N; but it must ! satisfy PREDICATE or this instruction pattern will not match at ! all. Operand numbers must be chosen consecutively counting from zero in ! each instruction pattern. There may be only one 'match_operand' expression in the pattern for each operand number. Usually ! operands are numbered in the order of appearance in 'match_operand' ! expressions. In the case of a 'define_expand', any operand numbers ! used only in 'match_dup' expressions have higher values than all other operand numbers. PREDICATE is a string that is the name of a function that accepts two arguments, an expression and a machine mode. *Note Predicates::. During matching, the function will be called with the putative operand as the expression and M as the mode argument ! (if M is not specified, 'VOIDmode' will be used, which normally causes PREDICATE to accept any mode). If it returns zero, this instruction pattern fails to match. PREDICATE may be an empty string; then it means no test is to be done on the operand, so anything which occurs in this position is valid. ! Most of the time, PREDICATE will reject modes other than M--but not ! always. For example, the predicate 'address_operand' uses M as the ! mode of memory ref that the address should be valid for. Many ! predicates accept 'const_int' nodes even though their mode is ! 'VOIDmode'. CONSTRAINT controls reloading and the choice of the best register class to use for a value, as explained later (*note Constraints::). If the constraint would be an empty string, it can be omitted. People are often unclear on the difference between the constraint ! and the predicate. The predicate helps decide whether a given insn ! matches the pattern. The constraint plays no role in this decision; instead, it controls various decisions in the case of an insn which does match. ! '(match_scratch:M N CONSTRAINT)' This expression is also a placeholder for operand number N and ! indicates that operand must be a 'scratch' or 'reg' expression. When matching patterns, this is equivalent to (match_operand:M N "scratch_operand" CONSTRAINT) ! but, when generating RTL, it produces a ('scratch':M) expression. ! If the last few expressions in a 'parallel' are 'clobber' expressions whose operands are either a hard register or ! 'match_scratch', the combiner can add or delete them when necessary. *Note Side Effects::. ! '(match_dup N)' This expression is also a placeholder for operand number N. It is used when the operand needs to appear more than once in the insn. ! In construction, 'match_dup' acts just like 'match_operand': the operand is substituted into the insn being constructed. But in ! matching, 'match_dup' behaves differently. It assumes that operand ! number N has already been determined by a 'match_operand' appearing ! earlier in the recognition template, and it matches only an ! identical-looking expression. ! Note that 'match_dup' should not be used to tell the compiler that a particular register is being used for two operands (example: ! 'add' that adds one register to another; the second register is both an input operand and the output operand). Use a matching ! constraint (*note Simple Constraints::) for those. 'match_dup' is for the cases where one operand is used in two places in the template, such as an instruction that computes both a quotient and a remainder, where the opcode takes two input operands but the RTL ! template has to refer to each of those twice; once for the quotient ! pattern and once for the remainder pattern. ! '(match_operator:M N PREDICATE [OPERANDS...])' This pattern is a kind of placeholder for a variable RTL expression code. When constructing an insn, it stands for an RTL expression whose ! expression code is taken from that of operand N, and whose operands ! are constructed from the patterns OPERANDS. When matching an expression, it matches an expression if the function PREDICATE returns nonzero on that expression _and_ the patterns OPERANDS match the operands of the expression. ! Suppose that the function 'commutative_operator' is defined as follows, to match any expression whose operator is one of the commutative arithmetic operators of RTL and whose mode is MODE: --- 18891,18988 ---- controlled by special expression types that direct matching and substitution of the operands. ! `(match_operand:M N PREDICATE CONSTRAINT)' This expression is a placeholder for operand number N of the insn. When constructing an insn, operand number N will be substituted at this point. When matching an insn, whatever appears at this ! position in the insn will be taken as operand number N; but it ! must satisfy PREDICATE or this instruction pattern will not match ! at all. Operand numbers must be chosen consecutively counting from zero in ! each instruction pattern. There may be only one `match_operand' expression in the pattern for each operand number. Usually ! operands are numbered in the order of appearance in `match_operand' ! expressions. In the case of a `define_expand', any operand numbers ! used only in `match_dup' expressions have higher values than all other operand numbers. PREDICATE is a string that is the name of a function that accepts two arguments, an expression and a machine mode. *Note Predicates::. During matching, the function will be called with the putative operand as the expression and M as the mode argument ! (if M is not specified, `VOIDmode' will be used, which normally causes PREDICATE to accept any mode). If it returns zero, this instruction pattern fails to match. PREDICATE may be an empty string; then it means no test is to be done on the operand, so anything which occurs in this position is valid. ! Most of the time, PREDICATE will reject modes other than M--but ! not always. For example, the predicate `address_operand' uses M ! as the mode of memory ref that the address should be valid for. ! Many predicates accept `const_int' nodes even though their mode is ! `VOIDmode'. CONSTRAINT controls reloading and the choice of the best register class to use for a value, as explained later (*note Constraints::). If the constraint would be an empty string, it can be omitted. People are often unclear on the difference between the constraint ! and the predicate. The predicate helps decide whether a given ! insn matches the pattern. The constraint plays no role in this decision; instead, it controls various decisions in the case of an insn which does match. ! `(match_scratch:M N CONSTRAINT)' This expression is also a placeholder for operand number N and ! indicates that operand must be a `scratch' or `reg' expression. When matching patterns, this is equivalent to (match_operand:M N "scratch_operand" CONSTRAINT) ! but, when generating RTL, it produces a (`scratch':M) expression. ! If the last few expressions in a `parallel' are `clobber' expressions whose operands are either a hard register or ! `match_scratch', the combiner can add or delete them when necessary. *Note Side Effects::. ! `(match_dup N)' This expression is also a placeholder for operand number N. It is used when the operand needs to appear more than once in the insn. ! In construction, `match_dup' acts just like `match_operand': the operand is substituted into the insn being constructed. But in ! matching, `match_dup' behaves differently. It assumes that operand ! number N has already been determined by a `match_operand' ! appearing earlier in the recognition template, and it matches only ! an identical-looking expression. ! Note that `match_dup' should not be used to tell the compiler that a particular register is being used for two operands (example: ! `add' that adds one register to another; the second register is both an input operand and the output operand). Use a matching ! constraint (*note Simple Constraints::) for those. `match_dup' is for the cases where one operand is used in two places in the template, such as an instruction that computes both a quotient and a remainder, where the opcode takes two input operands but the RTL ! template has to refer to each of those twice; once for the ! quotient pattern and once for the remainder pattern. ! `(match_operator:M N PREDICATE [OPERANDS...])' This pattern is a kind of placeholder for a variable RTL expression code. When constructing an insn, it stands for an RTL expression whose ! expression code is taken from that of operand N, and whose ! operands are constructed from the patterns OPERANDS. When matching an expression, it matches an expression if the function PREDICATE returns nonzero on that expression _and_ the patterns OPERANDS match the operands of the expression. ! Suppose that the function `commutative_operator' is defined as follows, to match any expression whose operator is one of the commutative arithmetic operators of RTL and whose mode is MODE: *************** substitution of the operands. *** 18783,18848 **** [(match_operand:SI 1 "general_operand" "g") (match_operand:SI 2 "general_operand" "g")]) ! Here the vector '[OPERANDS...]' contains two patterns because the expressions to be matched all contain two operands. When this pattern does match, the two operands of the commutative operator are recorded as operands 1 and 2 of the insn. (This is ! done by the two instances of 'match_operand'.) Operand 3 of the ! insn will be the entire commutative expression: use 'GET_CODE (operands[3])' to see which commutative operator was used. ! The machine mode M of 'match_operator' works like that of ! 'match_operand': it is passed as the second argument to the predicate function, and that function is solely responsible for deciding whether the expression to be matched "has" that mode. When constructing an insn, argument 3 of the gen-function will ! specify the operation (i.e. the expression code) for the expression ! to be made. It should be an RTL expression, whose expression code ! is copied into a new expression whose operands are arguments 1 and ! 2 of the gen-function. The subexpressions of argument 3 are not ! used; only its expression code matters. ! When 'match_operator' is used in a pattern for matching an insn, it ! usually best if the operand number of the 'match_operator' is higher than that of the actual operands of the insn. This improves register allocation because the register allocator often looks at operands 1 and 2 of insns to see if it can do register tying. ! There is no way to specify constraints in 'match_operator'. The ! operand of the insn which corresponds to the 'match_operator' never ! has any constraints because it is never reloaded as a whole. ! However, if parts of its OPERANDS are matched by 'match_operand' patterns, those parts may have constraints of their own. ! '(match_op_dup:M N[OPERANDS...])' ! Like 'match_dup', except that it applies to operators instead of operands. When constructing an insn, operand number N will be ! substituted at this point. But in matching, 'match_op_dup' behaves differently. It assumes that operand number N has already been ! determined by a 'match_operator' appearing earlier in the recognition template, and it matches only an identical-looking expression. ! '(match_parallel N PREDICATE [SUBPAT...])' This pattern is a placeholder for an insn that consists of a ! 'parallel' expression with a variable number of elements. This expression should only appear at the top level of an insn pattern. When constructing an insn, operand number N will be substituted at this point. When matching an insn, it matches if the body of the ! insn is a 'parallel' expression with at least as many elements as ! the vector of SUBPAT expressions in the 'match_parallel', if each ! SUBPAT matches the corresponding element of the 'parallel', _and_ ! the function PREDICATE returns nonzero on the 'parallel' that is ! the body of the insn. It is the responsibility of the predicate to ! validate elements of the 'parallel' beyond those listed in the ! 'match_parallel'. ! A typical use of 'match_parallel' is to match load and store multiple expressions, which can contain a variable number of ! elements in a 'parallel'. For example, (define_insn "" [(match_parallel 0 "load_multiple_operation" --- 19005,19070 ---- [(match_operand:SI 1 "general_operand" "g") (match_operand:SI 2 "general_operand" "g")]) ! Here the vector `[OPERANDS...]' contains two patterns because the expressions to be matched all contain two operands. When this pattern does match, the two operands of the commutative operator are recorded as operands 1 and 2 of the insn. (This is ! done by the two instances of `match_operand'.) Operand 3 of the ! insn will be the entire commutative expression: use `GET_CODE (operands[3])' to see which commutative operator was used. ! The machine mode M of `match_operator' works like that of ! `match_operand': it is passed as the second argument to the predicate function, and that function is solely responsible for deciding whether the expression to be matched "has" that mode. When constructing an insn, argument 3 of the gen-function will ! specify the operation (i.e. the expression code) for the ! expression to be made. It should be an RTL expression, whose ! expression code is copied into a new expression whose operands are ! arguments 1 and 2 of the gen-function. The subexpressions of ! argument 3 are not used; only its expression code matters. ! When `match_operator' is used in a pattern for matching an insn, ! it usually best if the operand number of the `match_operator' is higher than that of the actual operands of the insn. This improves register allocation because the register allocator often looks at operands 1 and 2 of insns to see if it can do register tying. ! There is no way to specify constraints in `match_operator'. The ! operand of the insn which corresponds to the `match_operator' ! never has any constraints because it is never reloaded as a whole. ! However, if parts of its OPERANDS are matched by `match_operand' patterns, those parts may have constraints of their own. ! `(match_op_dup:M N[OPERANDS...])' ! Like `match_dup', except that it applies to operators instead of operands. When constructing an insn, operand number N will be ! substituted at this point. But in matching, `match_op_dup' behaves differently. It assumes that operand number N has already been ! determined by a `match_operator' appearing earlier in the recognition template, and it matches only an identical-looking expression. ! `(match_parallel N PREDICATE [SUBPAT...])' This pattern is a placeholder for an insn that consists of a ! `parallel' expression with a variable number of elements. This expression should only appear at the top level of an insn pattern. When constructing an insn, operand number N will be substituted at this point. When matching an insn, it matches if the body of the ! insn is a `parallel' expression with at least as many elements as ! the vector of SUBPAT expressions in the `match_parallel', if each ! SUBPAT matches the corresponding element of the `parallel', _and_ ! the function PREDICATE returns nonzero on the `parallel' that is ! the body of the insn. It is the responsibility of the predicate ! to validate elements of the `parallel' beyond those listed in the ! `match_parallel'. ! A typical use of `match_parallel' is to match load and store multiple expressions, which can contain a variable number of ! elements in a `parallel'. For example, (define_insn "" [(match_parallel 0 "load_multiple_operation" *************** substitution of the operands. *** 18853,18861 **** "" "loadm 0,0,%1,%2") ! This example comes from 'a29k.md'. The function ! 'load_multiple_operation' is defined in 'a29k.c' and checks that ! subsequent elements in the 'parallel' are the same as the 'set' in the pattern, except that they are referencing subsequent registers and memory locations. --- 19075,19083 ---- "" "loadm 0,0,%1,%2") ! This example comes from `a29k.md'. The function ! `load_multiple_operation' is defined in `a29k.c' and checks that ! subsequent elements in the `parallel' are the same as the `set' in the pattern, except that they are referencing subsequent registers and memory locations. *************** substitution of the operands. *** 18872,18880 **** (mem:SI (plus:SI (reg:SI 100) (const_int 8))))]) ! '(match_par_dup N [SUBPAT...])' ! Like 'match_op_dup', but for 'match_parallel' instead of ! 'match_operator'.  File: gccint.info, Node: Output Template, Next: Output Statement, Prev: RTL Template, Up: Machine Desc --- 19094,19103 ---- (mem:SI (plus:SI (reg:SI 100) (const_int 8))))]) ! `(match_par_dup N [SUBPAT...])' ! Like `match_op_dup', but for `match_parallel' instead of ! `match_operator'. !  File: gccint.info, Node: Output Template, Next: Output Statement, Prev: RTL Template, Up: Machine Desc *************** File: gccint.info, Node: Output Templat *** 18884,18958 **** The "output template" is a string which specifies how to output the assembler code for an instruction pattern. Most of the template is a ! fixed string which is output literally. The character '%' is used to specify where to substitute an operand; it can also be used to identify places where different variants of the assembler require different syntax. ! In the simplest case, a '%' followed by a digit N says to output operand N at that point in the string. ! '%' followed by a letter and a digit says to output an operand in an alternate fashion. Four letters have standard, built-in meanings ! described below. The machine description macro 'PRINT_OPERAND' can define additional letters with nonstandard meanings. ! '%cDIGIT' can be used to substitute an operand that is a constant value ! without the syntax that normally indicates an immediate operand. ! '%nDIGIT' is like '%cDIGIT' except that the value of the constant is negated before printing. ! '%aDIGIT' can be used to substitute an operand as if it were a memory reference, with the actual operand treated as the address. This may be useful when outputting a "load address" instruction, because often the assembler syntax for such an instruction requires you to write the operand as if it were a memory reference. ! '%lDIGIT' is used to substitute a 'label_ref' into a jump instruction. ! '%=' outputs a number which is unique to each instruction in the entire ! compilation. This is useful for making local labels to be referred to ! more than once in a single template that generates multiple assembler ! instructions. ! '%' followed by a punctuation character specifies a substitution that ! does not use an operand. Only one case is standard: '%%' outputs a '%' into the assembler code. Other nonstandard cases can be defined in the ! 'PRINT_OPERAND' macro. You must also define which punctuation ! characters are valid with the 'PRINT_OPERAND_PUNCT_VALID_P' macro. The template may generate multiple assembler instructions. Write the ! text for the instructions, with '\;' between them. When the RTL contains two operands which are required by constraint to match each other, the output template must refer only to the ! lower-numbered operand. Matching operands are not always identical, and ! the rest of the compiler arranges to put the proper RTL expression for ! printing into the lower-numbered operand. ! One use of nonstandard letters or punctuation following '%' is to distinguish between different assembler languages for the same machine; for example, Motorola syntax versus MIT syntax for the 68000. Motorola ! syntax requires periods in most opcode names, while MIT syntax does not. ! For example, the opcode 'movel' in MIT syntax is 'move.l' in Motorola ! syntax. The same file of patterns is used for both kinds of output ! syntax, but the character sequence '%.' is used in each place where ! Motorola syntax wants a period. The 'PRINT_OPERAND' macro for Motorola ! syntax defines the sequence to output a period; the macro for MIT syntax ! defines it to do nothing. ! As a special case, a template consisting of the single character '#' instructs the compiler to first split the insn, and then output the resulting instructions separately. This helps eliminate redundancy in ! the output templates. If you have a 'define_insn' that needs to emit ! multiple assembler instructions, and there is a matching 'define_split' ! already defined, then you can simply use '#' as the output template instead of writing an output template that emits the multiple assembler instructions. ! If the macro 'ASSEMBLER_DIALECT' is defined, you can use construct of ! the form '{option0|option1|option2}' in the templates. These describe multiple variants of assembler language syntax. *Note Instruction Output::. --- 19107,19181 ---- The "output template" is a string which specifies how to output the assembler code for an instruction pattern. Most of the template is a ! fixed string which is output literally. The character `%' is used to specify where to substitute an operand; it can also be used to identify places where different variants of the assembler require different syntax. ! In the simplest case, a `%' followed by a digit N says to output operand N at that point in the string. ! `%' followed by a letter and a digit says to output an operand in an alternate fashion. Four letters have standard, built-in meanings ! described below. The machine description macro `PRINT_OPERAND' can define additional letters with nonstandard meanings. ! `%cDIGIT' can be used to substitute an operand that is a constant ! value without the syntax that normally indicates an immediate operand. ! `%nDIGIT' is like `%cDIGIT' except that the value of the constant is negated before printing. ! `%aDIGIT' can be used to substitute an operand as if it were a memory reference, with the actual operand treated as the address. This may be useful when outputting a "load address" instruction, because often the assembler syntax for such an instruction requires you to write the operand as if it were a memory reference. ! `%lDIGIT' is used to substitute a `label_ref' into a jump instruction. ! `%=' outputs a number which is unique to each instruction in the ! entire compilation. This is useful for making local labels to be ! referred to more than once in a single template that generates multiple ! assembler instructions. ! `%' followed by a punctuation character specifies a substitution that ! does not use an operand. Only one case is standard: `%%' outputs a `%' into the assembler code. Other nonstandard cases can be defined in the ! `PRINT_OPERAND' macro. You must also define which punctuation ! characters are valid with the `PRINT_OPERAND_PUNCT_VALID_P' macro. The template may generate multiple assembler instructions. Write the ! text for the instructions, with `\;' between them. When the RTL contains two operands which are required by constraint to match each other, the output template must refer only to the ! lower-numbered operand. Matching operands are not always identical, ! and the rest of the compiler arranges to put the proper RTL expression ! for printing into the lower-numbered operand. ! One use of nonstandard letters or punctuation following `%' is to distinguish between different assembler languages for the same machine; for example, Motorola syntax versus MIT syntax for the 68000. Motorola ! syntax requires periods in most opcode names, while MIT syntax does ! not. For example, the opcode `movel' in MIT syntax is `move.l' in ! Motorola syntax. The same file of patterns is used for both kinds of ! output syntax, but the character sequence `%.' is used in each place ! where Motorola syntax wants a period. The `PRINT_OPERAND' macro for ! Motorola syntax defines the sequence to output a period; the macro for ! MIT syntax defines it to do nothing. ! As a special case, a template consisting of the single character `#' instructs the compiler to first split the insn, and then output the resulting instructions separately. This helps eliminate redundancy in ! the output templates. If you have a `define_insn' that needs to emit ! multiple assembler instructions, and there is a matching `define_split' ! already defined, then you can simply use `#' as the output template instead of writing an output template that emits the multiple assembler instructions. ! If the macro `ASSEMBLER_DIALECT' is defined, you can use construct of ! the form `{option0|option1|option2}' in the templates. These describe multiple variants of assembler language syntax. *Note Instruction Output::. *************** single instruction pattern. For example *** 18968,18980 **** kinds of operands; or some unfortunate combinations of operands may require extra machine instructions. ! If the output control string starts with a '@', then it is actually a series of templates, each on a separate line. (Blank lines and leading ! spaces and tabs are ignored.) The templates correspond to the pattern's ! constraint alternatives (*note Multi-Alternative::). For example, if a ! target machine has a two-address add instruction 'addr' to add into a ! register and another 'addm' to add a register to memory, you might write ! this pattern: (define_insn "addsi3" [(set (match_operand:SI 0 "general_operand" "=r,m") --- 19191,19203 ---- kinds of operands; or some unfortunate combinations of operands may require extra machine instructions. ! If the output control string starts with a `@', then it is actually a series of templates, each on a separate line. (Blank lines and leading ! spaces and tabs are ignored.) The templates correspond to the ! pattern's constraint alternatives (*note Multi-Alternative::). For ! example, if a target machine has a two-address add instruction `addr' ! to add into a register and another `addm' to add a register to memory, ! you might write this pattern: (define_insn "addsi3" [(set (match_operand:SI 0 "general_operand" "=r,m") *************** this pattern: *** 18985,19029 **** addr %2,%0 addm %2,%0") ! If the output control string starts with a '*', then it is not an output template but rather a piece of C program that should compute a ! template. It should execute a 'return' statement to return the template-string you want. Most such templates use C string literals, which require doublequote characters to delimit them. To include these ! doublequote characters in the string, prefix each one with '\'. If the output control string is written as a brace block instead of a double-quoted string, it is automatically assumed to be C code. In that case, it is not necessary to put in a leading asterisk, or to escape the doublequotes surrounding C string literals. ! The operands may be found in the array 'operands', whose C data type is ! 'rtx []'. It is very common to select different ways of generating assembler code based on whether an immediate operand is within a certain range. Be ! careful when doing this, because the result of 'INTVAL' is an integer on ! the host machine. If the host machine has more bits in an 'int' than ! the target machine has in the mode in which the constant will be used, ! then some of the bits you get from 'INTVAL' will be superfluous. For ! proper results, you must carefully disregard the values of those bits. It is possible to output an assembler instruction and then go on to ! output or compute more of them, using the subroutine 'output_asm_insn'. ! This receives two arguments: a template-string and a vector of operands. ! The vector may be 'operands', or it may be another array of 'rtx' that ! you declare locally and initialize yourself. When an insn pattern has multiple alternatives in its constraints, ! often the appearance of the assembler code is determined mostly by which ! alternative was matched. When this is so, the C code can test the ! variable 'which_alternative', which is the ordinal number of the alternative that was actually satisfied (0 for the first, 1 for the second alternative, etc.). ! For example, suppose there are two opcodes for storing zero, 'clrreg' ! for registers and 'clrmem' for memory locations. Here is how a pattern ! could use 'which_alternative' to choose between them: (define_insn "" [(set (match_operand:SI 0 "general_operand" "=r,m") --- 19208,19253 ---- addr %2,%0 addm %2,%0") ! If the output control string starts with a `*', then it is not an output template but rather a piece of C program that should compute a ! template. It should execute a `return' statement to return the template-string you want. Most such templates use C string literals, which require doublequote characters to delimit them. To include these ! doublequote characters in the string, prefix each one with `\'. If the output control string is written as a brace block instead of a double-quoted string, it is automatically assumed to be C code. In that case, it is not necessary to put in a leading asterisk, or to escape the doublequotes surrounding C string literals. ! The operands may be found in the array `operands', whose C data type ! is `rtx []'. It is very common to select different ways of generating assembler code based on whether an immediate operand is within a certain range. Be ! careful when doing this, because the result of `INTVAL' is an integer ! on the host machine. If the host machine has more bits in an `int' ! than the target machine has in the mode in which the constant will be ! used, then some of the bits you get from `INTVAL' will be superfluous. ! For proper results, you must carefully disregard the values of those ! bits. It is possible to output an assembler instruction and then go on to ! output or compute more of them, using the subroutine `output_asm_insn'. ! This receives two arguments: a template-string and a vector of ! operands. The vector may be `operands', or it may be another array of ! `rtx' that you declare locally and initialize yourself. When an insn pattern has multiple alternatives in its constraints, ! often the appearance of the assembler code is determined mostly by ! which alternative was matched. When this is so, the C code can test ! the variable `which_alternative', which is the ordinal number of the alternative that was actually satisfied (0 for the first, 1 for the second alternative, etc.). ! For example, suppose there are two opcodes for storing zero, `clrreg' ! for registers and `clrmem' for memory locations. Here is how a pattern ! could use `which_alternative' to choose between them: (define_insn "" [(set (match_operand:SI 0 "general_operand" "=r,m") *************** could use 'which_alternative' to choose *** 19036,19042 **** The example above, where the assembler code to generate was _solely_ determined by the alternative, could also have been specified as ! follows, having the output control string start with a '@': (define_insn "" [(set (match_operand:SI 0 "general_operand" "=r,m") --- 19260,19266 ---- The example above, where the assembler code to generate was _solely_ determined by the alternative, could also have been specified as ! follows, having the output control string start with a `@': (define_insn "" [(set (match_operand:SI 0 "general_operand" "=r,m") *************** follows, having the output control strin *** 19047,19053 **** clrmem %0") If you just need a little bit of C code in one (or a few) alternatives, ! you can use '*' inside of a '@' multi-alternative template: (define_insn "" [(set (match_operand:SI 0 "general_operand" "=r,<,m") --- 19271,19277 ---- clrmem %0") If you just need a little bit of C code in one (or a few) alternatives, ! you can use `*' inside of a `@' multi-alternative template: (define_insn "" [(set (match_operand:SI 0 "general_operand" "=r,<,m") *************** File: gccint.info, Node: Predicates, N *** 19064,19081 **** 16.7 Predicates =============== ! A predicate determines whether a 'match_operand' or 'match_operator' expression matches, and therefore whether the surrounding instruction ! pattern will be used for that combination of operands. GCC has a number ! of machine-independent predicates, and you can define machine-specific ! predicates as needed. By convention, predicates used with ! 'match_operand' have names that end in '_operand', and those used with ! 'match_operator' have names that end in '_operator'. ! All predicates are Boolean functions (in the mathematical sense) of two ! arguments: the RTL expression that is being considered at that position ! in the instruction pattern, and the machine mode that the ! 'match_operand' or 'match_operator' specifies. In this section, the first argument is called OP and the second argument MODE. Predicates can be called from C as ordinary two-argument functions; this can be useful in output templates or other machine-specific code. --- 19288,19305 ---- 16.7 Predicates =============== ! A predicate determines whether a `match_operand' or `match_operator' expression matches, and therefore whether the surrounding instruction ! pattern will be used for that combination of operands. GCC has a ! number of machine-independent predicates, and you can define ! machine-specific predicates as needed. By convention, predicates used ! with `match_operand' have names that end in `_operand', and those used ! with `match_operator' have names that end in `_operator'. ! All predicates are Boolean functions (in the mathematical sense) of ! two arguments: the RTL expression that is being considered at that ! position in the instruction pattern, and the machine mode that the ! `match_operand' or `match_operator' specifies. In this section, the first argument is called OP and the second argument MODE. Predicates can be called from C as ordinary two-argument functions; this can be useful in output templates or other machine-specific code. *************** useful in output templates or other mach *** 19084,19113 **** to the hardware, as long as the constraints give reload the ability to fix them up (*note Constraints::). However, GCC will usually generate better code if the predicates specify the requirements of the machine ! instructions as closely as possible. Reload cannot fix up operands that ! must be constants ("immediate operands"); you must use a predicate that ! allows only constants, or else enforce the requirement in the extra ! condition. Most predicates handle their MODE argument in a uniform manner. If ! MODE is 'VOIDmode' (unspecified), then OP can have any mode. If MODE is ! anything else, then OP must have the same mode, unless OP is a ! 'CONST_INT' or integer 'CONST_DOUBLE'. These RTL expressions always ! have 'VOIDmode', so it would be counterproductive to check that their ! mode matches. Instead, predicates that accept 'CONST_INT' and/or ! integer 'CONST_DOUBLE' check that the value stored in the constant will fit in the requested mode. ! Predicates with this behavior are called "normal". 'genrecog' can optimize the instruction recognizer based on knowledge of how normal predicates treat modes. It can also diagnose certain kinds of common errors in the use of normal predicates; for instance, it is almost always an error to use a normal predicate without specifying a mode. Predicates that do something different with their MODE argument are ! called "special". The generic predicates 'address_operand' and ! 'pmode_register_operand' are special predicates. 'genrecog' does not do ! any optimizations or diagnosis when special predicates are used. * Menu: --- 19308,19337 ---- to the hardware, as long as the constraints give reload the ability to fix them up (*note Constraints::). However, GCC will usually generate better code if the predicates specify the requirements of the machine ! instructions as closely as possible. Reload cannot fix up operands ! that must be constants ("immediate operands"); you must use a predicate ! that allows only constants, or else enforce the requirement in the ! extra condition. Most predicates handle their MODE argument in a uniform manner. If ! MODE is `VOIDmode' (unspecified), then OP can have any mode. If MODE ! is anything else, then OP must have the same mode, unless OP is a ! `CONST_INT' or integer `CONST_DOUBLE'. These RTL expressions always ! have `VOIDmode', so it would be counterproductive to check that their ! mode matches. Instead, predicates that accept `CONST_INT' and/or ! integer `CONST_DOUBLE' check that the value stored in the constant will fit in the requested mode. ! Predicates with this behavior are called "normal". `genrecog' can optimize the instruction recognizer based on knowledge of how normal predicates treat modes. It can also diagnose certain kinds of common errors in the use of normal predicates; for instance, it is almost always an error to use a normal predicate without specifying a mode. Predicates that do something different with their MODE argument are ! called "special". The generic predicates `address_operand' and ! `pmode_register_operand' are special predicates. `genrecog' does not ! do any optimizations or diagnosis when special predicates are used. * Menu: *************** File: gccint.info, Node: Machine-Indepe *** 19122,19128 **** ------------------------------------- These are the generic predicates available to all back ends. They are ! defined in 'recog.c'. The first category of predicates allow only constant, or "immediate", operands. -- Function: immediate_operand --- 19346,19352 ---- ------------------------------------- These are the generic predicates available to all back ends. They are ! defined in `recog.c'. The first category of predicates allow only constant, or "immediate", operands. -- Function: immediate_operand *************** constant, or "immediate", operands. *** 19131,19157 **** must be constant. -- Function: const_int_operand ! This predicate allows any 'CONST_INT' expression that fits in MODE. ! It is an appropriate choice for an immediate operand that does not ! allow a symbol or label. -- Function: const_double_operand ! This predicate accepts any 'CONST_DOUBLE' expression that has ! exactly MODE. If MODE is 'VOIDmode', it will also accept ! 'CONST_INT'. It is intended for immediate floating point constants. The second category of predicates allow only some kind of machine register. -- Function: register_operand ! This predicate allows any 'REG' or 'SUBREG' expression that is valid for MODE. It is often suitable for arithmetic instruction operands on a RISC machine. -- Function: pmode_register_operand ! This is a slight variant on 'register_operand' which works around a ! limitation in the machine-description reader. (match_operand N "pmode_register_operand" CONSTRAINT) --- 19355,19381 ---- must be constant. -- Function: const_int_operand ! This predicate allows any `CONST_INT' expression that fits in ! MODE. It is an appropriate choice for an immediate operand that ! does not allow a symbol or label. -- Function: const_double_operand ! This predicate accepts any `CONST_DOUBLE' expression that has ! exactly MODE. If MODE is `VOIDmode', it will also accept ! `CONST_INT'. It is intended for immediate floating point constants. The second category of predicates allow only some kind of machine register. -- Function: register_operand ! This predicate allows any `REG' or `SUBREG' expression that is valid for MODE. It is often suitable for arithmetic instruction operands on a RISC machine. -- Function: pmode_register_operand ! This is a slight variant on `register_operand' which works around ! a limitation in the machine-description reader. (match_operand N "pmode_register_operand" CONSTRAINT) *************** register. *** 19159,19173 **** (match_operand:P N "register_operand" CONSTRAINT) ! would mean, if the machine-description reader accepted ':P' mode ! suffixes. Unfortunately, it cannot, because 'Pmode' is an alias for some other mode, and might vary with machine-specific options. *Note Misc::. -- Function: scratch_operand ! This predicate allows hard registers and 'SCRATCH' expressions, but ! not pseudo-registers. It is used internally by 'match_scratch'; it ! should not be used directly. The third category of predicates allow only some kind of memory reference. --- 19383,19397 ---- (match_operand:P N "register_operand" CONSTRAINT) ! would mean, if the machine-description reader accepted `:P' mode ! suffixes. Unfortunately, it cannot, because `Pmode' is an alias for some other mode, and might vary with machine-specific options. *Note Misc::. -- Function: scratch_operand ! This predicate allows hard registers and `SCRATCH' expressions, ! but not pseudo-registers. It is used internally by ! `match_scratch'; it should not be used directly. The third category of predicates allow only some kind of memory reference. *************** reference. *** 19175,19212 **** -- Function: memory_operand This predicate allows any valid reference to a quantity of mode MODE in memory, as determined by the weak form of ! 'GO_IF_LEGITIMATE_ADDRESS' (*note Addressing Modes::). -- Function: address_operand This predicate is a little unusual; it allows any operand that is a valid expression for the _address_ of a quantity of mode MODE, ! again determined by the weak form of 'GO_IF_LEGITIMATE_ADDRESS'. ! To first order, if '(mem:MODE (EXP))' is acceptable to ! 'memory_operand', then EXP is acceptable to 'address_operand'. Note that EXP does not necessarily have the mode MODE. -- Function: indirect_operand ! This is a stricter form of 'memory_operand' which allows only ! memory references with a 'general_operand' as the address expression. New uses of this predicate are discouraged, because ! 'general_operand' is very permissive, so it's hard to tell what an ! 'indirect_operand' does or does not allow. If a target has different requirements for memory operands for different instructions, it is better to define target-specific predicates which enforce the hardware's requirements explicitly. -- Function: push_operand This predicate allows a memory reference suitable for pushing a ! value onto the stack. This will be a 'MEM' which refers to ! 'stack_pointer_rtx', with a side-effect in its address expression ! (*note Incdec::); which one is determined by the 'STACK_PUSH_CODE' macro (*note Frame Layout::). -- Function: pop_operand This predicate allows a memory reference suitable for popping a ! value off the stack. Again, this will be a 'MEM' referring to ! 'stack_pointer_rtx', with a side-effect in its address expression. ! However, this time 'STACK_POP_CODE' is expected. The fourth category of predicates allow some combination of the above operands. --- 19399,19436 ---- -- Function: memory_operand This predicate allows any valid reference to a quantity of mode MODE in memory, as determined by the weak form of ! `GO_IF_LEGITIMATE_ADDRESS' (*note Addressing Modes::). -- Function: address_operand This predicate is a little unusual; it allows any operand that is a valid expression for the _address_ of a quantity of mode MODE, ! again determined by the weak form of `GO_IF_LEGITIMATE_ADDRESS'. ! To first order, if `(mem:MODE (EXP))' is acceptable to ! `memory_operand', then EXP is acceptable to `address_operand'. Note that EXP does not necessarily have the mode MODE. -- Function: indirect_operand ! This is a stricter form of `memory_operand' which allows only ! memory references with a `general_operand' as the address expression. New uses of this predicate are discouraged, because ! `general_operand' is very permissive, so it's hard to tell what an ! `indirect_operand' does or does not allow. If a target has different requirements for memory operands for different instructions, it is better to define target-specific predicates which enforce the hardware's requirements explicitly. -- Function: push_operand This predicate allows a memory reference suitable for pushing a ! value onto the stack. This will be a `MEM' which refers to ! `stack_pointer_rtx', with a side-effect in its address expression ! (*note Incdec::); which one is determined by the `STACK_PUSH_CODE' macro (*note Frame Layout::). -- Function: pop_operand This predicate allows a memory reference suitable for popping a ! value off the stack. Again, this will be a `MEM' referring to ! `stack_pointer_rtx', with a side-effect in its address expression. ! However, this time `STACK_POP_CODE' is expected. The fourth category of predicates allow some combination of the above operands. *************** Finally, there are two generic operator *** 19227,19240 **** -- Function: comparison_operator This predicate matches any expression which performs an arithmetic ! comparison in MODE; that is, 'COMPARISON_P' is true for the expression code. -- Function: ordered_comparison_operator This predicate matches any expression which performs an arithmetic comparison in MODE and whose expression code is valid for integer ! modes; that is, the expression code will be one of 'eq', 'ne', ! 'lt', 'ltu', 'le', 'leu', 'gt', 'gtu', 'ge', 'geu'.  File: gccint.info, Node: Defining Predicates, Prev: Machine-Independent Predicates, Up: Predicates --- 19451,19464 ---- -- Function: comparison_operator This predicate matches any expression which performs an arithmetic ! comparison in MODE; that is, `COMPARISON_P' is true for the expression code. -- Function: ordered_comparison_operator This predicate matches any expression which performs an arithmetic comparison in MODE and whose expression code is valid for integer ! modes; that is, the expression code will be one of `eq', `ne', ! `lt', `ltu', `le', `leu', `gt', `gtu', `ge', `geu'.  File: gccint.info, Node: Defining Predicates, Prev: Machine-Independent Predicates, Up: Predicates *************** File: gccint.info, Node: Defining Predi *** 19244,19275 **** Many machines have requirements for their operands that cannot be expressed precisely using the generic predicates. You can define ! additional predicates using 'define_predicate' and ! 'define_special_predicate' expressions. These expressions have three operands: * The name of the predicate, as it will be referred to in ! 'match_operand' or 'match_operator' expressions. * An RTL expression which evaluates to true if the predicate allows the operand OP, false if it does not. This expression can only use the following RTL codes: ! 'MATCH_OPERAND' ! When written inside a predicate expression, a 'MATCH_OPERAND' expression evaluates to true if the predicate it names would ! allow OP. The operand number and constraint are ignored. Due ! to limitations in 'genrecog', you can only refer to generic ! predicates and predicates that have already been defined. ! 'MATCH_CODE' This expression evaluates to true if OP or a specified subexpression of OP has one of a given list of RTX codes. The first operand of this expression is a string constant containing a comma-separated list of RTX code names (in lower ! case). These are the codes for which the 'MATCH_CODE' will be ! true. The second operand is a string constant which indicates what subexpression of OP to examine. If it is absent or the empty --- 19468,19500 ---- Many machines have requirements for their operands that cannot be expressed precisely using the generic predicates. You can define ! additional predicates using `define_predicate' and ! `define_special_predicate' expressions. These expressions have three operands: * The name of the predicate, as it will be referred to in ! `match_operand' or `match_operator' expressions. * An RTL expression which evaluates to true if the predicate allows the operand OP, false if it does not. This expression can only use the following RTL codes: ! `MATCH_OPERAND' ! When written inside a predicate expression, a `MATCH_OPERAND' expression evaluates to true if the predicate it names would ! allow OP. The operand number and constraint are ignored. ! Due to limitations in `genrecog', you can only refer to ! generic predicates and predicates that have already been ! defined. ! `MATCH_CODE' This expression evaluates to true if OP or a specified subexpression of OP has one of a given list of RTX codes. The first operand of this expression is a string constant containing a comma-separated list of RTX code names (in lower ! case). These are the codes for which the `MATCH_CODE' will ! be true. The second operand is a string constant which indicates what subexpression of OP to examine. If it is absent or the empty *************** operands: *** 19278,19330 **** character indicates a subexpression to extract from the current expression; for the first character this is OP, for the second and subsequent characters it is the result of the ! previous character. A digit N extracts 'XEXP (E, N)'; a ! letter L extracts 'XVECEXP (E, 0, N)' where N is the ! alphabetic ordinal of L (0 for 'a', 1 for 'b', and so on). ! The 'MATCH_CODE' then examines the RTX code of the subexpression extracted by the complete string. It is not ! possible to extract components of an 'rtvec' that is not at position 0 within its RTX object. ! 'MATCH_TEST' This expression has one operand, a string constant containing a C expression. The predicate's arguments, OP and MODE, are available with those names in the C expression. The ! 'MATCH_TEST' evaluates to true if the C expression evaluates ! to a nonzero value. 'MATCH_TEST' expressions must not have side effects. ! 'AND' ! 'IOR' ! 'NOT' ! 'IF_THEN_ELSE' ! The basic 'MATCH_' expressions can be combined using these logical operators, which have the semantics of the C operators ! '&&', '||', '!', and '? :' respectively. As in Common Lisp, ! you may give an 'AND' or 'IOR' expression an arbitrary number of arguments; this has exactly the same effect as writing a ! chain of two-argument 'AND' or 'IOR' expressions. ! * An optional block of C code, which should execute 'return true' if ! the predicate is found to match and 'return false' if it does not. ! It must not have any side effects. The predicate arguments, OP and ! MODE, are available with those names. If a code block is present in a predicate definition, then the RTL expression must evaluate to true _and_ the code block must execute ! 'return true' for the predicate to allow the operand. The RTL ! expression is evaluated first; do not re-check anything in the code ! block that was checked in the RTL expression. ! The program 'genrecog' scans 'define_predicate' and ! 'define_special_predicate' expressions to determine which RTX codes are possibly allowed. You should always make this explicit in the RTL ! predicate expression, using 'MATCH_OPERAND' and 'MATCH_CODE'. Here is an example of a simple predicate definition, from the IA64 machine description: ! ;; True if OP is a 'SYMBOL_REF' which refers to the sdata section. (define_predicate "small_addr_symbolic_operand" (and (match_code "symbol_ref") (match_test "SYMBOL_REF_SMALL_ADDR_P (op)"))) --- 19503,19555 ---- character indicates a subexpression to extract from the current expression; for the first character this is OP, for the second and subsequent characters it is the result of the ! previous character. A digit N extracts `XEXP (E, N)'; a ! letter L extracts `XVECEXP (E, 0, N)' where N is the ! alphabetic ordinal of L (0 for `a', 1 for 'b', and so on). ! The `MATCH_CODE' then examines the RTX code of the subexpression extracted by the complete string. It is not ! possible to extract components of an `rtvec' that is not at position 0 within its RTX object. ! `MATCH_TEST' This expression has one operand, a string constant containing a C expression. The predicate's arguments, OP and MODE, are available with those names in the C expression. The ! `MATCH_TEST' evaluates to true if the C expression evaluates ! to a nonzero value. `MATCH_TEST' expressions must not have side effects. ! `AND' ! `IOR' ! `NOT' ! `IF_THEN_ELSE' ! The basic `MATCH_' expressions can be combined using these logical operators, which have the semantics of the C operators ! `&&', `||', `!', and `? :' respectively. As in Common Lisp, ! you may give an `AND' or `IOR' expression an arbitrary number of arguments; this has exactly the same effect as writing a ! chain of two-argument `AND' or `IOR' expressions. ! * An optional block of C code, which should execute `return true' if ! the predicate is found to match and `return false' if it does not. ! It must not have any side effects. The predicate arguments, OP ! and MODE, are available with those names. If a code block is present in a predicate definition, then the RTL expression must evaluate to true _and_ the code block must execute ! `return true' for the predicate to allow the operand. The RTL ! expression is evaluated first; do not re-check anything in the ! code block that was checked in the RTL expression. ! The program `genrecog' scans `define_predicate' and ! `define_special_predicate' expressions to determine which RTX codes are possibly allowed. You should always make this explicit in the RTL ! predicate expression, using `MATCH_OPERAND' and `MATCH_CODE'. Here is an example of a simple predicate definition, from the IA64 machine description: ! ;; True if OP is a `SYMBOL_REF' which refers to the sdata section. (define_predicate "small_addr_symbolic_operand" (and (match_code "symbol_ref") (match_test "SYMBOL_REF_SMALL_ADDR_P (op)"))) *************** And here is another, showing the use of *** 19343,19367 **** return (regno >= FIRST_PSEUDO_REGISTER || GENERAL_REGNO_P (regno)); }) ! Predicates written with 'define_predicate' automatically include a test ! that MODE is 'VOIDmode', or OP has the same mode as MODE, or OP is a ! 'CONST_INT' or 'CONST_DOUBLE'. They do _not_ check specifically for ! integer 'CONST_DOUBLE', nor do they test that the value of either kind ! of constant fits in the requested mode. This is because target-specific ! predicates that take constants usually have to do more stringent value ! checks anyway. If you need the exact same treatment of 'CONST_INT' or ! 'CONST_DOUBLE' that the generic predicates provide, use a ! 'MATCH_OPERAND' subexpression to call 'const_int_operand', ! 'const_double_operand', or 'immediate_operand'. ! Predicates written with 'define_special_predicate' do not get any automatic mode checks, and are treated as having special mode handling ! by 'genrecog'. ! The program 'genpreds' is responsible for generating code to test predicates. It also writes a header file containing function declarations for all machine-specific predicates. It is not necessary ! to declare these predicates in 'CPU-protos.h'.  File: gccint.info, Node: Constraints, Next: Standard Names, Prev: Predicates, Up: Machine Desc --- 19568,19592 ---- return (regno >= FIRST_PSEUDO_REGISTER || GENERAL_REGNO_P (regno)); }) ! Predicates written with `define_predicate' automatically include a ! test that MODE is `VOIDmode', or OP has the same mode as MODE, or OP is ! a `CONST_INT' or `CONST_DOUBLE'. They do _not_ check specifically for ! integer `CONST_DOUBLE', nor do they test that the value of either kind ! of constant fits in the requested mode. This is because ! target-specific predicates that take constants usually have to do more ! stringent value checks anyway. If you need the exact same treatment of ! `CONST_INT' or `CONST_DOUBLE' that the generic predicates provide, use ! a `MATCH_OPERAND' subexpression to call `const_int_operand', ! `const_double_operand', or `immediate_operand'. ! Predicates written with `define_special_predicate' do not get any automatic mode checks, and are treated as having special mode handling ! by `genrecog'. ! The program `genpreds' is responsible for generating code to test predicates. It also writes a header file containing function declarations for all machine-specific predicates. It is not necessary ! to declare these predicates in `CPU-protos.h'.  File: gccint.info, Node: Constraints, Next: Standard Names, Prev: Predicates, Up: Machine Desc *************** File: gccint.info, Node: Constraints, *** 19369,19375 **** 16.8 Operand Constraints ======================== ! Each 'match_operand' in an instruction pattern can specify constraints for the operands allowed. The constraints allow you to fine-tune matching within the set of operands allowed by the predicate. --- 19594,19600 ---- 16.8 Operand Constraints ======================== ! Each `match_operand' in an instruction pattern can specify constraints for the operands allowed. The constraints allow you to fine-tune matching within the set of operands allowed by the predicate. *************** kinds of register; whether the operand c *** 19378,19384 **** which kinds of address; whether the operand may be an immediate constant, and which possible values it may have. Constraints can also require two operands to match. Side-effects aren't allowed in operands ! of inline 'asm', unless '<' or '>' constraints are used, because there is no guarantee that the side-effects will happen exactly once in an instruction that can update the addressing register. --- 19603,19609 ---- which kinds of address; whether the operand may be an immediate constant, and which possible values it may have. Constraints can also require two operands to match. Side-effects aren't allowed in operands ! of inline `asm', unless `<' or `>' constraints are used, because there is no guarantee that the side-effects will happen exactly once in an instruction that can update the addressing register. *************** whitespace *** 19410,19422 **** description even if they have different number of constraints and modifiers. ! 'm' A memory operand is allowed, with any kind of address that the machine supports in general. Note that the letter used for the ! general memory constraint can be re-defined by a back end using the ! 'TARGET_MEM_CONSTRAINT' macro. ! 'o' A memory operand is allowed, but only if the address is "offsettable". This means that adding a small integer (actually, the width in bytes of the operand, as determined by its machine --- 19635,19647 ---- description even if they have different number of constraints and modifiers. ! `m' A memory operand is allowed, with any kind of address that the machine supports in general. Note that the letter used for the ! general memory constraint can be re-defined by a back end using ! the `TARGET_MEM_CONSTRAINT' macro. ! `o' A memory operand is allowed, but only if the address is "offsettable". This means that adding a small integer (actually, the width in bytes of the operand, as determined by its machine *************** whitespace *** 19432,19537 **** on the other addressing modes that the machine supports. Note that in an output operand which can be matched by another ! operand, the constraint letter 'o' is valid only when accompanied ! by both '<' (if the target machine has predecrement addressing) and ! '>' (if the target machine has preincrement addressing). ! 'V' ! A memory operand that is not offsettable. In other words, anything ! that would fit the 'm' constraint but not the 'o' constraint. ! '<' ! A memory operand with autodecrement addressing (either predecrement ! or postdecrement) is allowed. In inline 'asm' this constraint is ! only allowed if the operand is used exactly once in an instruction ! that can handle the side-effects. Not using an operand with '<' in ! constraint string in the inline 'asm' pattern at all or using it in ! multiple instructions isn't valid, because the side-effects ! wouldn't be performed or would be performed more than once. ! Furthermore, on some targets the operand with '<' in constraint ! string must be accompanied by special instruction suffixes like ! '%U0' instruction suffix on PowerPC or '%P0' on IA-64. ! '>' ! A memory operand with autoincrement addressing (either preincrement ! or postincrement) is allowed. In inline 'asm' the same ! restrictions as for '<' apply. ! 'r' A register operand is allowed provided that it is in a general register. ! 'i' An immediate integer operand (one with constant value) is allowed. This includes symbolic constants whose values will be known only at assembly time or later. ! 'n' An immediate integer operand with a known numeric value is allowed. Many systems cannot support assembly-time constants for operands less than a word wide. Constraints for these operands should use ! 'n' rather than 'i'. ! 'I', 'J', 'K', ... 'P' ! Other letters in the range 'I' through 'P' may be defined in a machine-dependent fashion to permit immediate integer operands with explicit integer values in specified ranges. For example, on the ! 68000, 'I' is defined to stand for the range of values 1 to 8. This is the range permitted as a shift count in the shift instructions. ! 'E' ! An immediate floating operand (expression code 'const_double') is allowed, but only if the target floating point format is the same as that of the host machine (on which the compiler is running). ! 'F' ! An immediate floating operand (expression code 'const_double' or ! 'const_vector') is allowed. ! 'G', 'H' ! 'G' and 'H' may be defined in a machine-dependent fashion to permit ! immediate floating operands in particular ranges of values. ! 's' ! An immediate integer operand whose value is not an explicit integer ! is allowed. This might appear strange; if an insn allows a constant operand ! with a value not known at compile time, it certainly must allow any ! known value. So why use 's' instead of 'i'? Sometimes it allows ! better code to be generated. For example, on the 68000 in a fullword instruction it is possible to use an immediate operand; but if the immediate value is between -128 and 127, better code results from loading the value into a ! register and using the register. This is because the load into the ! register can be done with a 'moveq' instruction. We arrange for ! this to happen by defining the letter 'K' to mean "any integer ! outside the range -128 to 127", and then specifying 'Ks' in the operand constraints. ! 'g' Any register, memory or immediate integer operand is allowed, except for registers that are not general registers. ! 'X' Any operand whatsoever is allowed, even if it does not satisfy ! 'general_operand'. This is normally used in the constraint of a ! 'match_scratch' when certain alternatives will not actually require ! a scratch register. ! '0', '1', '2', ... '9' An operand that matches the specified operand number is allowed. If a digit is used together with letters within the same alternative, the digit should come last. This number is allowed to be more than a single digit. If multiple digits are encountered consecutively, they are interpreted as a ! single decimal integer. There is scant chance for ambiguity, since ! to-date it has never been desirable that '10' be interpreted as ! matching either operand 1 _or_ operand 0. Should this be desired, ! one can use multiple alternatives instead. This is called a "matching constraint" and what it really means is that the assembler has only a single operand that fills two roles --- 19657,19764 ---- on the other addressing modes that the machine supports. Note that in an output operand which can be matched by another ! operand, the constraint letter `o' is valid only when accompanied ! by both `<' (if the target machine has predecrement addressing) ! and `>' (if the target machine has preincrement addressing). ! `V' ! A memory operand that is not offsettable. In other words, ! anything that would fit the `m' constraint but not the `o' ! constraint. ! `<' ! A memory operand with autodecrement addressing (either ! predecrement or postdecrement) is allowed. In inline `asm' this ! constraint is only allowed if the operand is used exactly once in ! an instruction that can handle the side-effects. Not using an ! operand with `<' in constraint string in the inline `asm' pattern ! at all or using it in multiple instructions isn't valid, because ! the side-effects wouldn't be performed or would be performed more ! than once. Furthermore, on some targets the operand with `<' in ! constraint string must be accompanied by special instruction ! suffixes like `%U0' instruction suffix on PowerPC or `%P0' on ! IA-64. ! `>' ! A memory operand with autoincrement addressing (either ! preincrement or postincrement) is allowed. In inline `asm' the ! same restrictions as for `<' apply. ! `r' A register operand is allowed provided that it is in a general register. ! `i' An immediate integer operand (one with constant value) is allowed. This includes symbolic constants whose values will be known only at assembly time or later. ! `n' An immediate integer operand with a known numeric value is allowed. Many systems cannot support assembly-time constants for operands less than a word wide. Constraints for these operands should use ! `n' rather than `i'. ! `I', `J', `K', ... `P' ! Other letters in the range `I' through `P' may be defined in a machine-dependent fashion to permit immediate integer operands with explicit integer values in specified ranges. For example, on the ! 68000, `I' is defined to stand for the range of values 1 to 8. This is the range permitted as a shift count in the shift instructions. ! `E' ! An immediate floating operand (expression code `const_double') is allowed, but only if the target floating point format is the same as that of the host machine (on which the compiler is running). ! `F' ! An immediate floating operand (expression code `const_double' or ! `const_vector') is allowed. ! `G', `H' ! `G' and `H' may be defined in a machine-dependent fashion to ! permit immediate floating operands in particular ranges of values. ! `s' ! An immediate integer operand whose value is not an explicit ! integer is allowed. This might appear strange; if an insn allows a constant operand ! with a value not known at compile time, it certainly must allow ! any known value. So why use `s' instead of `i'? Sometimes it ! allows better code to be generated. For example, on the 68000 in a fullword instruction it is possible to use an immediate operand; but if the immediate value is between -128 and 127, better code results from loading the value into a ! register and using the register. This is because the load into ! the register can be done with a `moveq' instruction. We arrange ! for this to happen by defining the letter `K' to mean "any integer ! outside the range -128 to 127", and then specifying `Ks' in the operand constraints. ! `g' Any register, memory or immediate integer operand is allowed, except for registers that are not general registers. ! `X' Any operand whatsoever is allowed, even if it does not satisfy ! `general_operand'. This is normally used in the constraint of a ! `match_scratch' when certain alternatives will not actually ! require a scratch register. ! `0', `1', `2', ... `9' An operand that matches the specified operand number is allowed. If a digit is used together with letters within the same alternative, the digit should come last. This number is allowed to be more than a single digit. If multiple digits are encountered consecutively, they are interpreted as a ! single decimal integer. There is scant chance for ambiguity, ! since to-date it has never been desirable that `10' be interpreted ! as matching either operand 1 _or_ operand 0. Should this be ! desired, one can use multiple alternatives instead. This is called a "matching constraint" and what it really means is that the assembler has only a single operand that fills two roles *************** whitespace *** 19550,19573 **** For operands to match in a particular case usually means that they are identical-looking RTL expressions. But in a few special cases ! specific kinds of dissimilarity are allowed. For example, '*x' as ! an input operand will match '*x++' as an output operand. For ! proper results in such cases, the output template should always use ! the output-operand's number when printing the operand. ! 'p' An operand that is a valid memory address is allowed. This is for "load address" and "push address" instructions. ! 'p' in the constraint must be accompanied by 'address_operand' as ! the predicate in the 'match_operand'. This predicate interprets ! the mode specified in the 'match_operand' as the mode of the memory reference for which the address would be valid. OTHER-LETTERS Other letters can be defined in machine-dependent fashion to stand for particular classes of registers or other arbitrary operand ! types. 'd', 'a' and 'f' are defined on the 68000/68020 to stand for data, address and floating point registers. In order to have valid assembler code, each operand must satisfy its --- 19777,19800 ---- For operands to match in a particular case usually means that they are identical-looking RTL expressions. But in a few special cases ! specific kinds of dissimilarity are allowed. For example, `*x' as ! an input operand will match `*x++' as an output operand. For ! proper results in such cases, the output template should always ! use the output-operand's number when printing the operand. ! `p' An operand that is a valid memory address is allowed. This is for "load address" and "push address" instructions. ! `p' in the constraint must be accompanied by `address_operand' as ! the predicate in the `match_operand'. This predicate interprets ! the mode specified in the `match_operand' as the mode of the memory reference for which the address would be valid. OTHER-LETTERS Other letters can be defined in machine-dependent fashion to stand for particular classes of registers or other arbitrary operand ! types. `d', `a' and `f' are defined on the 68000/68020 to stand for data, address and floating point registers. In order to have valid assembler code, each operand must satisfy its *************** the first pattern would not apply at all *** 19606,19614 **** contain two identical subexpressions in the right place. The pattern would say, "That does not look like an add instruction; try other patterns". The second pattern would say, "Yes, that's an add ! instruction, but there is something wrong with it". It would direct the ! reload pass of the compiler to generate additional insns to make the ! constraint true. The results might look like this: (insn N2 PREV N (set (reg:SI 3) (reg:SI 6)) --- 19833,19841 ---- contain two identical subexpressions in the right place. The pattern would say, "That does not look like an add instruction; try other patterns". The second pattern would say, "Yes, that's an add ! instruction, but there is something wrong with it". It would direct ! the reload pass of the compiler to generate additional insns to make ! the constraint true. The results might look like this: (insn N2 PREV N (set (reg:SI 3) (reg:SI 6)) *************** reloading any possible operand so that i *** 19635,19680 **** registers is safe provided its predicate rejects registers. An operand whose predicate accepts only constant values is safe ! provided its constraints include the letter 'i'. If any possible ! constant value is accepted, then nothing less than 'i' will do; if the predicate is more selective, then the constraints may also be more selective. * Any operand expression can be reloaded by copying it into a register. So if an operand's constraints allow some kind of ! register, it is certain to be safe. It need not permit all classes ! of registers; the compiler knows how to copy a register into ! another register of the proper class in order to make an instruction valid. * A nonoffsettable memory reference can be reloaded by copying the ! address into a register. So if the constraint uses the letter 'o', ! all memory references are taken care of. * A constant operand can be reloaded by allocating space in memory to hold it as preinitialized data. Then the memory reference can be used in place of the constant. So if the constraint uses the ! letters 'o' or 'm', constant operands are not a problem. * If the constraint permits a constant and a pseudo register used in ! an insn was not allocated to a hard register and is equivalent to a ! constant, the register will be replaced with the constant. If the ! predicate does not permit a constant and the insn is re-recognized ! for some reason, the compiler will crash. Thus the predicate must ! always recognize any objects allowed by the constraint. If the operand's predicate can recognize registers, but the constraint ! does not permit them, it can make the compiler crash. When this operand ! happens to be a register, the reload pass will be stymied, because it ! does not know how to copy a register temporarily into memory. If the predicate accepts a unary operator, the constraint applies to the operand. For example, the MIPS processor at ISA level 3 supports an ! instruction which adds two registers in 'SImode' to produce a 'DImode' result, but only if the registers are correctly sign extended. This ! predicate for the input operands accepts a 'sign_extend' of an 'SImode' ! register. Write the constraint to indicate the type of register that is ! required for the operand of the 'sign_extend'.  File: gccint.info, Node: Multi-Alternative, Next: Class Preferences, Prev: Simple Constraints, Up: Constraints --- 19862,19908 ---- registers is safe provided its predicate rejects registers. An operand whose predicate accepts only constant values is safe ! provided its constraints include the letter `i'. If any possible ! constant value is accepted, then nothing less than `i' will do; if the predicate is more selective, then the constraints may also be more selective. * Any operand expression can be reloaded by copying it into a register. So if an operand's constraints allow some kind of ! register, it is certain to be safe. It need not permit all ! classes of registers; the compiler knows how to copy a register ! into another register of the proper class in order to make an instruction valid. * A nonoffsettable memory reference can be reloaded by copying the ! address into a register. So if the constraint uses the letter ! `o', all memory references are taken care of. * A constant operand can be reloaded by allocating space in memory to hold it as preinitialized data. Then the memory reference can be used in place of the constant. So if the constraint uses the ! letters `o' or `m', constant operands are not a problem. * If the constraint permits a constant and a pseudo register used in ! an insn was not allocated to a hard register and is equivalent to ! a constant, the register will be replaced with the constant. If ! the predicate does not permit a constant and the insn is ! re-recognized for some reason, the compiler will crash. Thus the ! predicate must always recognize any objects allowed by the ! constraint. If the operand's predicate can recognize registers, but the constraint ! does not permit them, it can make the compiler crash. When this ! operand happens to be a register, the reload pass will be stymied, ! because it does not know how to copy a register temporarily into memory. If the predicate accepts a unary operator, the constraint applies to the operand. For example, the MIPS processor at ISA level 3 supports an ! instruction which adds two registers in `SImode' to produce a `DImode' result, but only if the registers are correctly sign extended. This ! predicate for the input operands accepts a `sign_extend' of an `SImode' ! register. Write the constraint to indicate the type of register that ! is required for the operand of the `sign_extend'.  File: gccint.info, Node: Multi-Alternative, Next: Class Preferences, Prev: Simple Constraints, Up: Constraints *************** on the 68000: *** 19703,19748 **** (match_operand:SI 2 "general_operand" "dKs,dmKs")))] ...) ! The first alternative has 'm' (memory) for operand 0, '0' for operand 1 ! (meaning it must match operand 0), and 'dKs' for operand 2. The second ! alternative has 'd' (data register) for operand 0, '0' for operand 1, ! and 'dmKs' for operand 2. The '=' and '%' in the constraints apply to ! all the alternatives; their meaning is explained in the next section ! (*note Class Preferences::). If all the operands fit any one alternative, the instruction is valid. Otherwise, for each alternative, the compiler counts how many ! instructions must be added to copy the operands so that that alternative ! applies. The alternative requiring the least copying is chosen. If two ! alternatives need the same amount of copying, the one that comes first ! is chosen. These choices can be altered with the '?' and '!' ! characters: ! '?' ! Disparage slightly the alternative that the '?' appears in, as a choice when no alternative applies exactly. The compiler regards ! this alternative as one unit more costly for each '?' that appears in it. ! '!' ! Disparage severely the alternative that the '!' appears in. This alternative can still be used if it fits without reloading, but if reloading is needed, some other alternative will be used. ! '^' ! This constraint is analogous to '?' but it disparages slightly the ! alternative only if the operand with the '^' needs a reload. ! '$' ! This constraint is analogous to '!' but it disparages severely the ! alternative only if the operand with the '$' needs a reload. When an insn pattern has multiple alternatives in its constraints, often the appearance of the assembler code is determined mostly by which alternative was matched. When this is so, the C code for writing the ! assembler code can use the variable 'which_alternative', which is the ! ordinal number of the alternative that was actually satisfied (0 for the ! first, 1 for the second alternative, etc.). *Note Output Statement::.  File: gccint.info, Node: Class Preferences, Next: Modifiers, Prev: Multi-Alternative, Up: Constraints --- 19931,19977 ---- (match_operand:SI 2 "general_operand" "dKs,dmKs")))] ...) ! The first alternative has `m' (memory) for operand 0, `0' for operand ! 1 (meaning it must match operand 0), and `dKs' for operand 2. The ! second alternative has `d' (data register) for operand 0, `0' for ! operand 1, and `dmKs' for operand 2. The `=' and `%' in the ! constraints apply to all the alternatives; their meaning is explained ! in the next section (*note Class Preferences::). If all the operands fit any one alternative, the instruction is valid. Otherwise, for each alternative, the compiler counts how many ! instructions must be added to copy the operands so that that ! alternative applies. The alternative requiring the least copying is ! chosen. If two alternatives need the same amount of copying, the one ! that comes first is chosen. These choices can be altered with the `?' ! and `!' characters: ! `?' ! Disparage slightly the alternative that the `?' appears in, as a choice when no alternative applies exactly. The compiler regards ! this alternative as one unit more costly for each `?' that appears in it. ! `!' ! Disparage severely the alternative that the `!' appears in. This alternative can still be used if it fits without reloading, but if reloading is needed, some other alternative will be used. ! `^' ! This constraint is analogous to `?' but it disparages slightly the ! alternative only if the operand with the `^' needs a reload. ! `$' ! This constraint is analogous to `!' but it disparages severely the ! alternative only if the operand with the `$' needs a reload. When an insn pattern has multiple alternatives in its constraints, often the appearance of the assembler code is determined mostly by which alternative was matched. When this is so, the C code for writing the ! assembler code can use the variable `which_alternative', which is the ! ordinal number of the alternative that was actually satisfied (0 for ! the first, 1 for the second alternative, etc.). *Note Output ! Statement::.  File: gccint.info, Node: Class Preferences, Next: Modifiers, Prev: Multi-Alternative, Up: Constraints *************** The operand constraints have another fun *** 19754,19762 **** to decide which kind of hardware register a pseudo register is best allocated to. The compiler examines the constraints that apply to the insns that use the pseudo register, looking for the machine-dependent ! letters such as 'd' and 'a' that specify classes of registers. The pseudo register is put in whichever class gets the most "votes". The ! constraint letters 'g' and 'r' also vote: they vote in favor of a general register. The machine description says which registers are considered general. --- 19983,19991 ---- to decide which kind of hardware register a pseudo register is best allocated to. The compiler examines the constraints that apply to the insns that use the pseudo register, looking for the machine-dependent ! letters such as `d' and `a' that specify classes of registers. The pseudo register is put in whichever class gets the most "votes". The ! constraint letters `g' and `r' also vote: they vote in favor of a general register. The machine description says which registers are considered general. *************** File: gccint.info, Node: Modifiers, Ne *** 19771,19827 **** Here are constraint modifier characters. ! '=' Means that this operand is written to by this instruction: the previous value is discarded and replaced by new data. ! '+' Means that this operand is both read and written by the instruction. When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are read by the instruction and ! which are written by it. '=' identifies an operand which is only ! written; '+' identifies an operand that is both read and written; all other operands are assumed to only be read. ! If you specify '=' or '+' in a constraint, you put it in the first character of the constraint string. ! '&' Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is written before the instruction is ! finished using the input operands. Therefore, this operand may not ! lie in a register that is read by the instruction or as part of any ! memory address. ! '&' applies only to the alternative in which it is written. In constraints with multiple alternatives, sometimes one alternative ! requires '&' while others do not. See, for example, the 'movdf' insn of the 68000. A operand which is read by the instruction can be tied to an earlyclobber operand if its only use as an input occurs before the early result is written. Adding alternatives of this form often allows GCC to produce better code when only some of the read ! operands can be affected by the earlyclobber. See, for example, ! the 'mulsi3' insn of the ARM. Furthermore, if the "earlyclobber" operand is also a read/write operand, then that operand is written only after it's used. ! '&' does not obviate the need to write '=' or '+'. As "earlyclobber" operands are always written, a read-only "earlyclobber" operand is ill-formed and will be rejected by the compiler. ! '%' Declares the instruction to be commutative for this operand and the following operand. This means that the compiler may interchange the two operands if that is the cheapest way to make all operands ! fit the constraints. '%' applies to all alternatives and must appear as the first character in the constraint. Only read-only ! operands can use '%'. This is often used in patterns for addition instructions that really have only two operands: the result must go in one of the --- 20000,20056 ---- Here are constraint modifier characters. ! `=' Means that this operand is written to by this instruction: the previous value is discarded and replaced by new data. ! `+' Means that this operand is both read and written by the instruction. When the compiler fixes up the operands to satisfy the constraints, it needs to know which operands are read by the instruction and ! which are written by it. `=' identifies an operand which is only ! written; `+' identifies an operand that is both read and written; all other operands are assumed to only be read. ! If you specify `=' or `+' in a constraint, you put it in the first character of the constraint string. ! `&' Means (in a particular alternative) that this operand is an "earlyclobber" operand, which is written before the instruction is ! finished using the input operands. Therefore, this operand may ! not lie in a register that is read by the instruction or as part ! of any memory address. ! `&' applies only to the alternative in which it is written. In constraints with multiple alternatives, sometimes one alternative ! requires `&' while others do not. See, for example, the `movdf' insn of the 68000. A operand which is read by the instruction can be tied to an earlyclobber operand if its only use as an input occurs before the early result is written. Adding alternatives of this form often allows GCC to produce better code when only some of the read ! operands can be affected by the earlyclobber. See, for example, ! the `mulsi3' insn of the ARM. Furthermore, if the "earlyclobber" operand is also a read/write operand, then that operand is written only after it's used. ! `&' does not obviate the need to write `=' or `+'. As "earlyclobber" operands are always written, a read-only "earlyclobber" operand is ill-formed and will be rejected by the compiler. ! `%' Declares the instruction to be commutative for this operand and the following operand. This means that the compiler may interchange the two operands if that is the cheapest way to make all operands ! fit the constraints. `%' applies to all alternatives and must appear as the first character in the constraint. Only read-only ! operands can use `%'. This is often used in patterns for addition instructions that really have only two operands: the result must go in one of the *************** Here are constraint modifier characters. *** 19835,19866 **** ...) GCC can only handle one commutative pair in an asm; if you use more, the compiler may fail. Note that you need not use the ! modifier if the two alternatives are strictly identical; this would ! only waste time in the reload pass. The modifier is not operational after register allocation, so the result of ! 'define_peephole2' and 'define_split's performed after reload ! cannot rely on '%' to make the intended insn match. ! '#' Says that all following characters, up to the next comma, are to be ignored as a constraint. They are significant only for choosing register preferences. ! '*' Says that the following character should be ignored when choosing ! register preferences. '*' has no effect on the meaning of the constraint as a constraint, and no effect on reloading. For LRA ! '*' additionally disparages slightly the alternative if the following character matches the operand. Here is an example: the 68000 has an instruction to sign-extend a halfword in a data register, and can also sign-extend a value by ! copying it into an address register. While either kind of register ! is acceptable, the constraints on an address-register destination ! are less strict, so it is best if register allocation makes an ! address register its goal. Therefore, '*' is used so that the 'd' ! constraint letter (for data register) is ignored when computing ! register preferences. (define_insn "extendhisi2" [(set (match_operand:SI 0 "general_operand" "=*d,a") --- 20064,20095 ---- ...) GCC can only handle one commutative pair in an asm; if you use more, the compiler may fail. Note that you need not use the ! modifier if the two alternatives are strictly identical; this ! would only waste time in the reload pass. The modifier is not operational after register allocation, so the result of ! `define_peephole2' and `define_split's performed after reload ! cannot rely on `%' to make the intended insn match. ! `#' Says that all following characters, up to the next comma, are to be ignored as a constraint. They are significant only for choosing register preferences. ! `*' Says that the following character should be ignored when choosing ! register preferences. `*' has no effect on the meaning of the constraint as a constraint, and no effect on reloading. For LRA ! `*' additionally disparages slightly the alternative if the following character matches the operand. Here is an example: the 68000 has an instruction to sign-extend a halfword in a data register, and can also sign-extend a value by ! copying it into an address register. While either kind of ! register is acceptable, the constraints on an address-register ! destination are less strict, so it is best if register allocation ! makes an address register its goal. Therefore, `*' is used so ! that the `d' constraint letter (for data register) is ignored when ! computing register preferences. (define_insn "extendhisi2" [(set (match_operand:SI 0 "general_operand" "=*d,a") *************** File: gccint.info, Node: Machine Constr *** 19875,21258 **** ------------------------------------------ Whenever possible, you should use the general-purpose constraint letters ! in 'asm' arguments, since they will convey meaning more readily to ! people reading your code. Failing that, use the constraint letters that ! usually have very similar meanings across architectures. The most ! commonly used constraints are 'm' and 'r' (for memory and general-purpose registers respectively; *note Simple Constraints::), and ! 'I', usually the letter indicating the most common immediate-constant format. Each architecture defines additional constraints. These constraints are used by the compiler itself for instruction generation, as well as ! for 'asm' statements; therefore, some of the constraints are not ! particularly useful for 'asm'. Here is a summary of some of the machine-dependent constraints available on some particular machines; it ! includes both constraints that are useful for 'asm' and constraints that ! aren't. The compiler source file mentioned in the table heading for ! each architecture is the definitive reference for the meanings of that ! architecture's constraints. ! _AArch64 family--'config/aarch64/constraints.md'_ ! 'k' ! The stack pointer register ('SP') ! 'w' Floating point or SIMD vector register ! 'I' Integer constant that is valid as an immediate operand in an ! 'ADD' instruction ! 'J' Integer constant that is valid as an immediate operand in a ! 'SUB' instruction (once negated) ! 'K' Integer constant that can be used with a 32-bit logical instruction ! 'L' Integer constant that can be used with a 64-bit logical instruction ! 'M' Integer constant that is valid as an immediate operand in a ! 32-bit 'MOV' pseudo instruction. The 'MOV' may be assembled to one of several different machine instructions depending on the value ! 'N' Integer constant that is valid as an immediate operand in a ! 64-bit 'MOV' pseudo instruction ! 'S' An absolute symbolic address or a label reference ! 'Y' Floating point constant zero ! 'Z' Integer constant zero ! 'Ush' ! The high part (bits 12 and upwards) of the pc-relative address ! of a symbol within 4GB of the instruction ! 'Q' A memory address which uses a single base register with no offset ! 'Ump' ! A memory address suitable for a load/store pair instruction in ! SI, DI, SF and DF modes ! _ARC --'config/arc/constraints.md'_ ! 'q' ! Registers usable in ARCompact 16-bit instructions: 'r0'-'r3', ! 'r12'-'r15'. This constraint can only match when the '-mq' option is in effect. ! 'e' ! Registers usable as base-regs of memory addresses in ARCompact ! 16-bit memory instructions: 'r0'-'r3', 'r12'-'r15', 'sp'. ! This constraint can only match when the '-mq' option is in ! effect. ! 'D' ! ARC FPX (dpfp) 64-bit registers. 'D0', 'D1'. ! 'I' A signed 12-bit integer constant. ! 'Cal' ! constant for arithmetic/logical operations. This might be any ! constant that can be put into a long immediate by the assmbler ! or linker without involving a PIC relocation. ! 'K' A 3-bit unsigned integer constant. ! 'L' A 6-bit unsigned integer constant. ! 'CnL' One's complement of a 6-bit unsigned integer constant. ! 'CmL' Two's complement of a 6-bit unsigned integer constant. ! 'M' A 5-bit unsigned integer constant. ! 'O' A 7-bit unsigned integer constant. ! 'P' A 8-bit unsigned integer constant. ! 'H' Any const_double value. ! _ARM family--'config/arm/constraints.md'_ ! 'h' ! In Thumb state, the core registers 'r8'-'r15'. ! 'k' The stack pointer register. ! 'l' ! In Thumb State the core registers 'r0'-'r7'. In ARM state ! this is an alias for the 'r' constraint. ! 't' ! VFP floating-point registers 's0'-'s31'. Used for 32 bit values. ! 'w' ! VFP floating-point registers 'd0'-'d31' and the appropriate ! subset 'd0'-'d15' based on command line options. Used for 64 bit values only. Not valid for Thumb1. ! 'y' The iWMMX co-processor registers. ! 'z' The iWMMX GR registers. ! 'G' The floating-point constant 0.0 ! 'I' Integer that is valid as an immediate operand in a data ! processing instruction. That is, an integer in the range 0 to ! 255 rotated by a multiple of 2 ! 'J' Integer in the range -4095 to 4095 ! 'K' ! Integer that satisfies constraint 'I' when inverted (ones complement) ! 'L' ! Integer that satisfies constraint 'I' when negated (twos complement) ! 'M' Integer in the range 0 to 32 ! 'Q' A memory reference where the exact address is in a single ! register (''m'' is preferable for 'asm' statements) ! 'R' An item in the constant pool ! 'S' A symbol in the text segment of the current file ! 'Uv' A memory reference suitable for VFP load/store insns (reg+constant offset) ! 'Uy' A memory reference suitable for iWMMXt load/store instructions. ! 'Uq' A memory reference suitable for the ARMv4 ldrsb instruction. ! _AVR family--'config/avr/constraints.md'_ ! 'l' Registers from r0 to r15 ! 'a' Registers from r16 to r23 ! 'd' Registers from r16 to r31 ! 'w' Registers from r24 to r31. These registers can be used in ! 'adiw' command ! 'e' Pointer register (r26-r31) ! 'b' Base pointer register (r28-r31) ! 'q' Stack pointer register (SPH:SPL) ! 't' Temporary register r0 ! 'x' Register pair X (r27:r26) ! 'y' Register pair Y (r29:r28) ! 'z' Register pair Z (r31:r30) ! 'I' Constant greater than -1, less than 64 ! 'J' Constant greater than -64, less than 1 ! 'K' Constant integer 2 ! 'L' Constant integer 0 ! 'M' Constant that fits in 8 bits ! 'N' Constant integer -1 ! 'O' Constant integer 8, 16, or 24 ! 'P' Constant integer 1 ! 'G' A floating point constant 0.0 ! 'Q' A memory address based on Y or Z pointer with displacement. ! _Blackfin family--'config/bfin/constraints.md'_ ! 'a' P register ! 'd' D register ! 'z' A call clobbered P register. ! 'qN' A single register. If N is in the range 0 to 7, the ! corresponding D register. If it is 'A', then the register P0. ! 'D' Even-numbered D register ! 'W' Odd-numbered D register ! 'e' Accumulator register. ! 'A' Even-numbered accumulator register. ! 'B' Odd-numbered accumulator register. ! 'b' I register ! 'v' B register ! 'f' M register ! 'c' ! Registers used for circular buffering, i.e. I, B, or L registers. ! 'C' The CC register. ! 't' LT0 or LT1. ! 'k' LC0 or LC1. ! 'u' LB0 or LB1. ! 'x' Any D, P, B, M, I or L register. ! 'y' Additional registers typically used only in prologues and epilogues: RETS, RETN, RETI, RETX, RETE, ASTAT, SEQSTAT and USP. ! 'w' Any register except accumulators or CC. ! 'Ksh' Signed 16 bit integer (in the range -32768 to 32767) ! 'Kuh' Unsigned 16 bit integer (in the range 0 to 65535) ! 'Ks7' Signed 7 bit integer (in the range -64 to 63) ! 'Ku7' Unsigned 7 bit integer (in the range 0 to 127) ! 'Ku5' Unsigned 5 bit integer (in the range 0 to 31) ! 'Ks4' Signed 4 bit integer (in the range -8 to 7) ! 'Ks3' Signed 3 bit integer (in the range -3 to 4) ! 'Ku3' Unsigned 3 bit integer (in the range 0 to 7) ! 'PN' Constant N, where N is a single-digit constant in the range 0 to 4. ! 'PA' An integer equal to one of the MACFLAG_XXX constants that is suitable for use with either accumulator. ! 'PB' An integer equal to one of the MACFLAG_XXX constants that is suitable for use only with accumulator A1. ! 'M1' Constant 255. ! 'M2' Constant 65535. ! 'J' An integer constant with exactly a single bit set. ! 'L' An integer constant with all bits set except exactly one. ! 'H' ! 'Q' Any SYMBOL_REF. ! _CR16 Architecture--'config/cr16/cr16.h'_ ! 'b' Registers from r0 to r14 (registers without stack pointer) ! 't' Register from r0 to r11 (all 16-bit registers) ! 'p' Register from r12 to r15 (all 32-bit registers) ! 'I' Signed constant that fits in 4 bits ! 'J' Signed constant that fits in 5 bits ! 'K' Signed constant that fits in 6 bits ! 'L' Unsigned constant that fits in 4 bits ! 'M' Signed constant that fits in 32 bits ! 'N' Check for 64 bits wide constants for add/sub instructions ! 'G' Floating point constant that is legal for store immediate ! _Epiphany--'config/epiphany/constraints.md'_ ! 'U16' An unsigned 16-bit constant. ! 'K' An unsigned 5-bit constant. ! 'L' A signed 11-bit constant. ! 'Cm1' ! A signed 11-bit constant added to -1. Can only match when the ! '-m1reg-REG' option is active. ! 'Cl1' Left-shift of -1, i.e., a bit mask with a block of leading ones, the rest being a block of trailing zeroes. Can only ! match when the '-m1reg-REG' option is active. ! 'Cr1' Right-shift of -1, i.e., a bit mask with a trailing block of ones, the rest being zeroes. Or to put it another way, one less than a power of two. Can only match when the ! '-m1reg-REG' option is active. ! 'Cal' ! Constant for arithmetic/logical operations. This is like 'i', ! except that for position independent code, no symbols / expressions needing relocations are allowed. ! 'Csy' Symbolic constant for call/jump instruction. ! 'Rcs' The register class usable in short insns. This is a register class constraint, and can thus drive register allocation. ! This constraint won't match unless '-mprefer-short-insn-regs' is in effect. ! 'Rsc' The the register class of registers that can be used to hold a sibcall call address. I.e., a caller-saved register. ! 'Rct' Core control register class. ! 'Rgs' The register group usable in short insns. This constraint does not use a register class, so that it only passively matches suitable registers, and doesn't drive register allocation. ! 'Car' Constant suitable for the addsi3_r pattern. This is a valid offset For byte, halfword, or word addressing. ! 'Rra' ! Matches the return address if it can be replaced with the link ! register. ! 'Rcc' Matches the integer condition code register. ! 'Sra' Matches the return address if it is in a stack slot. ! 'Cfm' Matches control register values to switch fp mode, which are ! encapsulated in 'UNSPEC_FP_MODE'. ! _FRV--'config/frv/frv.h'_ ! 'a' ! Register in the class 'ACC_REGS' ('acc0' to 'acc7'). ! 'b' ! Register in the class 'EVEN_ACC_REGS' ('acc0' to 'acc7'). ! 'c' ! Register in the class 'CC_REGS' ('fcc0' to 'fcc3' and 'icc0' ! to 'icc3'). ! 'd' ! Register in the class 'GPR_REGS' ('gr0' to 'gr63'). ! 'e' ! Register in the class 'EVEN_REGS' ('gr0' to 'gr63'). Odd ! registers are excluded not in the class but through the use of ! a machine mode larger than 4 bytes. ! 'f' ! Register in the class 'FPR_REGS' ('fr0' to 'fr63'). ! 'h' ! Register in the class 'FEVEN_REGS' ('fr0' to 'fr63'). Odd ! registers are excluded not in the class but through the use of ! a machine mode larger than 4 bytes. ! 'l' ! Register in the class 'LR_REG' (the 'lr' register). ! 'q' ! Register in the class 'QUAD_REGS' ('gr2' to 'gr63'). Register ! numbers not divisible by 4 are excluded not in the class but ! through the use of a machine mode larger than 8 bytes. ! 't' ! Register in the class 'ICC_REGS' ('icc0' to 'icc3'). ! 'u' ! Register in the class 'FCC_REGS' ('fcc0' to 'fcc3'). ! 'v' ! Register in the class 'ICR_REGS' ('cc4' to 'cc7'). ! 'w' ! Register in the class 'FCR_REGS' ('cc0' to 'cc3'). ! 'x' ! Register in the class 'QUAD_FPR_REGS' ('fr0' to 'fr63'). Register numbers not divisible by 4 are excluded not in the class but through the use of a machine mode larger than 8 bytes. ! 'z' ! Register in the class 'SPR_REGS' ('lcr' and 'lr'). ! 'A' ! Register in the class 'QUAD_ACC_REGS' ('acc0' to 'acc7'). ! 'B' ! Register in the class 'ACCG_REGS' ('accg0' to 'accg7'). ! 'C' ! Register in the class 'CR_REGS' ('cc0' to 'cc7'). ! 'G' Floating point constant zero ! 'I' 6-bit signed integer constant ! 'J' 10-bit signed integer constant ! 'L' 16-bit signed integer constant ! 'M' 16-bit unsigned integer constant ! 'N' 12-bit signed integer constant that is negative--i.e. in the range of -2048 to -1 ! 'O' Constant zero ! 'P' ! 12-bit signed integer constant that is greater than zero--i.e. ! in the range of 1 to 2047. ! _FT32--'config/ft32/constraints.md'_ ! 'A' An absolute address ! 'B' An offset address ! 'W' A register indirect memory operand ! 'e' An offset address. ! 'f' An offset address. ! 'O' The constant zero or one ! 'I' A 16-bit signed constant (-32768 ... 32767) ! 'w' A bitfield mask suitable for bext or bins ! 'x' An inverted bitfield mask suitable for bext or bins ! 'L' A 16-bit unsigned constant, multiple of 4 (0 ... 65532) ! 'S' A 20-bit signed constant (-524288 ... 524287) ! 'b' A constant for a bitfield width (1 ... 16) ! 'KA' A 10-bit signed constant (-512 ... 511) ! _Hewlett-Packard PA-RISC--'config/pa/pa.h'_ ! 'a' General register 1 ! 'f' Floating point register ! 'q' Shift amount register ! 'x' Floating point register (deprecated) ! 'y' Upper floating point register (32-bit), floating point register (64-bit) ! 'Z' Any register ! 'I' Signed 11-bit integer constant ! 'J' Signed 14-bit integer constant ! 'K' ! Integer constant that can be deposited with a 'zdepi' instruction ! 'L' Signed 5-bit integer constant ! 'M' Integer constant 0 ! 'N' ! Integer constant that can be loaded with a 'ldil' instruction ! 'O' Integer constant whose value plus one is a power of 2 ! 'P' ! Integer constant that can be used for 'and' operations in ! 'depi' and 'extru' instructions ! 'S' Integer constant 31 ! 'U' Integer constant 63 ! 'G' Floating-point constant 0.0 ! 'A' ! A 'lo_sum' data-linkage-table memory operand ! 'Q' A memory operand that can be used as the destination operand of an integer store instruction ! 'R' A scaled or unscaled indexed memory operand ! 'T' A memory operand for floating-point loads and stores ! 'W' A register indirect memory operand ! _Intel IA-64--'config/ia64/ia64.h'_ ! 'a' ! General register 'r0' to 'r3' for 'addl' instruction ! 'b' Branch register ! 'c' ! Predicate register ('c' as in "conditional") ! 'd' Application register residing in M-unit ! 'e' Application register residing in I-unit ! 'f' Floating-point register ! 'm' ! Memory operand. If used together with '<' or '>', the operand ! can have postincrement and postdecrement which require ! printing with '%Pn' on IA-64. ! 'G' Floating-point constant 0.0 or 1.0 ! 'I' 14-bit signed integer constant ! 'J' 22-bit signed integer constant ! 'K' 8-bit signed integer constant for logical instructions ! 'L' 8-bit adjusted signed integer constant for compare pseudo-ops ! 'M' 6-bit unsigned integer constant for shift counts ! 'N' 9-bit signed integer constant for load and store postincrements ! 'O' The constant zero ! 'P' ! 0 or -1 for 'dep' instruction ! 'Q' Non-volatile memory for floating-point loads and stores ! 'R' ! Integer constant in the range 1 to 4 for 'shladd' instruction ! 'S' Memory operand except postincrement and postdecrement. This ! is now roughly the same as 'm' when not used together with '<' ! or '>'. ! _M32C--'config/m32c/m32c.c'_ ! 'Rsp' ! 'Rfb' ! 'Rsb' ! '$sp', '$fb', '$sb'. ! 'Rcr' Any control register, when they're 16 bits wide (nothing if control registers are 24 bits wide) ! 'Rcl' Any control register, when they're 24 bits wide. ! 'R0w' ! 'R1w' ! 'R2w' ! 'R3w' $r0, $r1, $r2, $r3. ! 'R02' $r0 or $r2, or $r2r0 for 32 bit values. ! 'R13' $r1 or $r3, or $r3r1 for 32 bit values. ! 'Rdi' A register that can hold a 64 bit value. ! 'Rhl' $r0 or $r1 (registers with addressable high/low bytes) ! 'R23' $r2 or $r3 ! 'Raa' Address registers ! 'Raw' Address registers when they're 16 bits wide. ! 'Ral' Address registers when they're 24 bits wide. ! 'Rqi' Registers that can hold QI values. ! 'Rad' Registers that can be used with displacements ($a0, $a1, $sb). ! 'Rsi' Registers that can hold 32 bit values. ! 'Rhi' Registers that can hold 16 bit values. ! 'Rhc' Registers chat can hold 16 bit values, including all control registers. ! 'Rra' $r0 through R1, plus $a0 and $a1. ! 'Rfl' The flags register. ! 'Rmm' The memory-based pseudo-registers $mem0 through $mem15. ! 'Rpi' Registers that can hold pointers (16 bit registers for r8c, m16c; 24 bit registers for m32cm, m32c). ! 'Rpa' Matches multiple registers in a PARALLEL to form a larger register. Used to match function return values. ! 'Is3' -8 ... 7 ! 'IS1' -128 ... 127 ! 'IS2' -32768 ... 32767 ! 'IU2' 0 ... 65535 ! 'In4' -8 ... -1 or 1 ... 8 ! 'In5' -16 ... -1 or 1 ... 16 ! 'In6' -32 ... -1 or 1 ... 32 ! 'IM2' -65536 ... -1 ! 'Ilb' An 8 bit value with exactly one bit set. ! 'Ilw' A 16 bit value with exactly one bit set. ! 'Sd' The common src/dest memory addressing modes. ! 'Sa' Memory addressed using $a0 or $a1. ! 'Si' Memory addressed with immediate addresses. ! 'Ss' Memory addressed using the stack pointer ($sp). ! 'Sf' Memory addressed using the frame base register ($fb). ! 'Ss' Memory addressed using the small base register ($sb). ! 'S1' $r1h ! _MeP--'config/mep/constraints.md'_ ! 'a' The $sp register. ! 'b' The $tp register. ! 'c' Any control register. ! 'd' Either the $hi or the $lo register. ! 'em' Coprocessor registers that can be directly loaded ($c0-$c15). ! 'ex' Coprocessor registers that can be moved to each other. ! 'er' Coprocessor registers that can be moved to core registers. ! 'h' The $hi register. ! 'j' The $rpc register. ! 'l' The $lo register. ! 't' Registers which can be used in $tp-relative addressing. ! 'v' The $gp register. ! 'x' The coprocessor registers. ! 'y' The coprocessor control registers. ! 'z' The $0 register. ! 'A' User-defined register set A. ! 'B' User-defined register set B. ! 'C' User-defined register set C. ! 'D' User-defined register set D. ! 'I' Offsets for $gp-rel addressing. ! 'J' Constants that can be used directly with boolean insns. ! 'K' Constants that can be moved directly to registers. ! 'L' Small constants that can be added to registers. ! 'M' Long shift counts. ! 'N' Small constants that can be compared to registers. ! 'O' Constants that can be loaded into the top half of registers. ! 'S' Signed 8-bit immediates. ! 'T' Symbols encoded for $tp-rel or $gp-rel addressing. ! 'U' Non-constant addresses for loading/saving coprocessor registers. ! 'W' The top half of a symbol's value. ! 'Y' A register indirect address without offset. ! 'Z' Symbolic references to the control bus. - _MicroBlaze--'config/microblaze/constraints.md'_ - 'd' - A general register ('r0' to 'r31'). ! 'z' ! A status register ('rmsr', '$fcc1' to '$fcc7'). ! _MIPS--'config/mips/constraints.md'_ ! 'd' ! An address register. This is equivalent to 'r' unless generating MIPS16 code. ! 'f' A floating-point register (if available). ! 'h' ! Formerly the 'hi' register. This constraint is no longer supported. ! 'l' ! The 'lo' register. Use this register to store values that are no bigger than a word. ! 'x' ! The concatenated 'hi' and 'lo' registers. Use this register to store doubleword values. ! 'c' A register suitable for use in an indirect jump. This will ! always be '$25' for '-mabicalls'. ! 'v' ! Register '$3'. Do not use this constraint in new code; it is retained only for compatibility with glibc. ! 'y' ! Equivalent to 'r'; retained for backwards compatibility. ! 'z' A floating-point condition code register. ! 'I' A signed 16-bit constant (for arithmetic instructions). ! 'J' Integer zero. ! 'K' An unsigned 16-bit constant (for logic instructions). ! 'L' A signed 32-bit constant in which the lower 16 bits are zero. ! Such constants can be loaded using 'lui'. ! 'M' ! A constant that cannot be loaded using 'lui', 'addiu' or ! 'ori'. ! 'N' A constant in the range -65535 to -1 (inclusive). ! 'O' A signed 15-bit constant. ! 'P' A constant in the range 1 to 65535 (inclusive). ! 'G' Floating-point zero. ! 'R' An address that can be used in a non-macro load or store. ! 'ZC' A memory operand whose address is formed by a base register and offset that is suitable for use in instructions with the ! same addressing mode as 'll' and 'sc'. ! 'ZD' ! An address suitable for a 'prefetch' instruction, or for any ! other instruction with the same addressing mode as 'prefetch'. ! _Motorola 680x0--'config/m68k/constraints.md'_ ! 'a' Address register ! 'd' Data register ! 'f' 68881 floating-point register, if available ! 'I' Integer in the range 1 to 8 ! 'J' 16-bit signed number ! 'K' Signed number whose magnitude is greater than 0x80 ! 'L' Integer in the range -8 to -1 ! 'M' Signed number whose magnitude is greater than 0x100 ! 'N' Range 24 to 31, rotatert:SI 8 to 1 expressed as rotate ! 'O' 16 (for rotate using swap) ! 'P' Range 8 to 15, rotatert:HI 8 to 1 expressed as rotate ! 'R' Numbers that mov3q can handle ! 'G' Floating point constant that is not a 68881 constant ! 'S' Operands that satisfy 'm' when -mpcrel is in effect ! 'T' Operands that satisfy 's' when -mpcrel is not in effect ! 'Q' Address register indirect addressing mode ! 'U' Register offset addressing ! 'W' const_call_operand ! 'Cs' symbol_ref or const ! 'Ci' const_int ! 'C0' const_int 0 ! 'Cj' Range of signed numbers that don't fit in 16 bits ! 'Cmvq' Integers valid for mvq ! 'Capsw' Integers valid for a moveq followed by a swap ! 'Cmvz' Integers valid for mvz ! 'Cmvs' Integers valid for mvs ! 'Ap' push_operand ! 'Ac' Non-register operands allowed in clr ! _Moxie--'config/moxie/constraints.md'_ ! 'A' An absolute address ! 'B' An offset address ! 'W' A register indirect memory operand ! 'I' A constant in the range of 0 to 255. ! 'N' A constant in the range of 0 to -255. - _MSP430-'config/msp430/constraints.md'_ ! 'R12' Register R12. ! 'R13' Register R13. ! 'K' Integer constant 1. ! 'L' Integer constant -1^20..1^19. ! 'M' Integer constant 1-4. ! 'Ya' Memory references which do not require an extended MOVX instruction. ! 'Yl' Memory reference, labels only. ! 'Ys' Memory reference, stack only. ! _NDS32--'config/nds32/constraints.md'_ ! 'w' LOW register class $r0 to $r7 constraint for V3/V3M ISA. ! 'l' LOW register class $r0 to $r7. ! 'd' MIDDLE register class $r0 to $r11, $r16 to $r19. ! 'h' HIGH register class $r12 to $r14, $r20 to $r31. ! 't' Temporary assist register $ta (i.e. $r15). ! 'k' Stack register $sp. ! 'Iu03' Unsigned immediate 3-bit value. ! 'In03' Negative immediate 3-bit value in the range of -7-0. ! 'Iu04' Unsigned immediate 4-bit value. ! 'Is05' Signed immediate 5-bit value. ! 'Iu05' Unsigned immediate 5-bit value. ! 'In05' Negative immediate 5-bit value in the range of -31-0. ! 'Ip05' Unsigned immediate 5-bit value for movpi45 instruction with range 16-47. ! 'Iu06' Unsigned immediate 6-bit value constraint for addri36.sp instruction. ! 'Iu08' Unsigned immediate 8-bit value. ! 'Iu09' Unsigned immediate 9-bit value. ! 'Is10' Signed immediate 10-bit value. ! 'Is11' Signed immediate 11-bit value. ! 'Is15' Signed immediate 15-bit value. ! 'Iu15' Unsigned immediate 15-bit value. ! 'Ic15' ! A constant which is not in the range of imm15u but ok for bclr ! instruction. ! 'Ie15' ! A constant which is not in the range of imm15u but ok for bset ! instruction. ! 'It15' ! A constant which is not in the range of imm15u but ok for btgl ! instruction. ! 'Ii15' A constant whose compliment value is in the range of imm15u and ok for bitci instruction. ! 'Is16' Signed immediate 16-bit value. ! 'Is17' Signed immediate 17-bit value. ! 'Is19' Signed immediate 19-bit value. ! 'Is20' Signed immediate 20-bit value. ! 'Ihig' The immediate value that can be simply set high 20-bit. ! 'Izeb' The immediate value 0xff. ! 'Izeh' The immediate value 0xffff. ! 'Ixls' The immediate value 0x01. ! 'Ix11' The immediate value 0x7ff. ! 'Ibms' The immediate value with power of 2. ! 'Ifex' The immediate value with power of 2 minus 1. ! 'U33' Memory constraint for 333 format. ! 'U45' Memory constraint for 45 format. ! 'U37' Memory constraint for 37 format. ! _Nios II family--'config/nios2/constraints.md'_ ! 'I' Integer that is valid as an immediate operand in an ! instruction taking a signed 16-bit number. Range -32768 to 32767. ! 'J' Integer that is valid as an immediate operand in an ! instruction taking an unsigned 16-bit number. Range 0 to 65535. ! 'K' Integer that is valid as an immediate operand in an instruction taking only the upper 16-bits of a 32-bit number. Range 32-bit numbers with the lower 16-bits being 0. ! 'L' Integer that is valid as an immediate operand for a shift ! instruction. Range 0 to 31. ! 'M' Integer that is valid as an immediate operand for only the ! value 0. Can be used in conjunction with the format modifier ! 'z' to use 'r0' instead of '0' in the assembly output. ! 'N' Integer that is valid as an immediate operand for a custom ! instruction opcode. Range 0 to 255. ! 'P' An immediate operand for R2 andchi/andci instructions. ! 'S' Matches immediates which are addresses in the small data ! section and therefore can be added to 'gp' as a 16-bit immediate to re-create their 32-bit value. ! 'U' Matches constants suitable as an operand for the rdprs and cache instructions. ! 'v' A memory operand suitable for Nios II R2 load/store exclusive instructions. ! 'w' A memory operand suitable for load/store IO and cache instructions. ! 'T' ! A 'const' wrapped 'UNSPEC' expression, representing a supported PIC or TLS relocation. - _PDP-11--'config/pdp11/constraints.md'_ - 'a' - Floating point registers AC0 through AC3. These can be loaded - from/to memory with a single instruction. ! 'd' Odd numbered general registers (R1, R3, R5). These are used for 16-bit multiply operations. ! 'f' Any of the floating point registers (AC0 through AC5). ! 'G' Floating point constant 0. ! 'I' An integer constant that fits in 16 bits. ! 'J' An integer constant whose low order 16 bits are zero. ! 'K' An integer constant that does not meet the constraints for ! codes 'I' or 'J'. ! 'L' The integer constant 1. ! 'M' The integer constant -1. ! 'N' The integer constant 0. ! 'O' Integer constants -4 through -1 and 1 through 4; shifts by ! these amounts are handled as multiple single-bit shifts rather ! than a single variable-length shift. ! 'Q' A memory reference which requires an additional word (address or offset) after the opcode. ! 'R' A memory reference that is encoded within the opcode. ! _PowerPC and IBM RS6000--'config/rs6000/constraints.md'_ ! 'b' Address base register ! 'd' Floating point register (containing 64-bit value) ! 'f' Floating point register (containing 32-bit value) ! 'v' Altivec vector register ! 'wa' Any VSX register if the -mvsx option was used or NO_REGS. ! When using any of the register constraints ('wa', 'wd', 'wf', ! 'wg', 'wh', 'wi', 'wj', 'wk', 'wl', 'wm', 'wo', 'wp', 'wq', ! 'ws', 'wt', 'wu', 'wv', 'ww', or 'wy') that take VSX ! registers, you must use '%x' in the template so that the correct register is used. Otherwise the register number output in the assembly file will be incorrect if an Altivec register is an operand of a VSX instruction that expects VSX --- 20104,21553 ---- ------------------------------------------ Whenever possible, you should use the general-purpose constraint letters ! in `asm' arguments, since they will convey meaning more readily to ! people reading your code. Failing that, use the constraint letters ! that usually have very similar meanings across architectures. The most ! commonly used constraints are `m' and `r' (for memory and general-purpose registers respectively; *note Simple Constraints::), and ! `I', usually the letter indicating the most common immediate-constant format. Each architecture defines additional constraints. These constraints are used by the compiler itself for instruction generation, as well as ! for `asm' statements; therefore, some of the constraints are not ! particularly useful for `asm'. Here is a summary of some of the machine-dependent constraints available on some particular machines; it ! includes both constraints that are useful for `asm' and constraints ! that aren't. The compiler source file mentioned in the table heading ! for each architecture is the definitive reference for the meanings of ! that architecture's constraints. ! _AArch64 family--`config/aarch64/constraints.md'_ ! `k' ! The stack pointer register (`SP') ! ! `w' Floating point or SIMD vector register ! `I' Integer constant that is valid as an immediate operand in an ! `ADD' instruction ! `J' Integer constant that is valid as an immediate operand in a ! `SUB' instruction (once negated) ! `K' Integer constant that can be used with a 32-bit logical instruction ! `L' Integer constant that can be used with a 64-bit logical instruction ! `M' Integer constant that is valid as an immediate operand in a ! 32-bit `MOV' pseudo instruction. The `MOV' may be assembled to one of several different machine instructions depending on the value ! `N' Integer constant that is valid as an immediate operand in a ! 64-bit `MOV' pseudo instruction ! `S' An absolute symbolic address or a label reference ! `Y' Floating point constant zero ! `Z' Integer constant zero ! `Ush' ! The high part (bits 12 and upwards) of the pc-relative ! address of a symbol within 4GB of the instruction ! `Q' A memory address which uses a single base register with no offset ! `Ump' ! A memory address suitable for a load/store pair instruction ! in SI, DI, SF and DF modes ! ! _ARC --`config/arc/constraints.md'_ ! ! `q' ! Registers usable in ARCompact 16-bit instructions: `r0'-`r3', ! `r12'-`r15'. This constraint can only match when the `-mq' option is in effect. ! `e' ! Registers usable as base-regs of memory addresses in ! ARCompact 16-bit memory instructions: `r0'-`r3', `r12'-`r15', ! `sp'. This constraint can only match when the `-mq' option ! is in effect. ! `D' ! ARC FPX (dpfp) 64-bit registers. `D0', `D1'. ! ! `I' A signed 12-bit integer constant. ! `Cal' ! constant for arithmetic/logical operations. This might be ! any constant that can be put into a long immediate by the ! assmbler or linker without involving a PIC relocation. ! `K' A 3-bit unsigned integer constant. ! `L' A 6-bit unsigned integer constant. ! `CnL' One's complement of a 6-bit unsigned integer constant. ! `CmL' Two's complement of a 6-bit unsigned integer constant. ! `M' A 5-bit unsigned integer constant. ! `O' A 7-bit unsigned integer constant. ! `P' A 8-bit unsigned integer constant. ! `H' Any const_double value. ! _ARM family--`config/arm/constraints.md'_ ! `h' ! In Thumb state, the core registers `r8'-`r15'. ! `k' The stack pointer register. ! `l' ! In Thumb State the core registers `r0'-`r7'. In ARM state ! this is an alias for the `r' constraint. ! `t' ! VFP floating-point registers `s0'-`s31'. Used for 32 bit values. ! `w' ! VFP floating-point registers `d0'-`d31' and the appropriate ! subset `d0'-`d15' based on command line options. Used for 64 bit values only. Not valid for Thumb1. ! `y' The iWMMX co-processor registers. ! `z' The iWMMX GR registers. ! `G' The floating-point constant 0.0 ! `I' Integer that is valid as an immediate operand in a data ! processing instruction. That is, an integer in the range 0 ! to 255 rotated by a multiple of 2 ! `J' Integer in the range -4095 to 4095 ! `K' ! Integer that satisfies constraint `I' when inverted (ones complement) ! `L' ! Integer that satisfies constraint `I' when negated (twos complement) ! `M' Integer in the range 0 to 32 ! `Q' A memory reference where the exact address is in a single ! register (``m'' is preferable for `asm' statements) ! `R' An item in the constant pool ! `S' A symbol in the text segment of the current file ! `Uv' A memory reference suitable for VFP load/store insns (reg+constant offset) ! `Uy' A memory reference suitable for iWMMXt load/store instructions. ! `Uq' A memory reference suitable for the ARMv4 ldrsb instruction. ! _AVR family--`config/avr/constraints.md'_ ! ! `l' Registers from r0 to r15 ! `a' Registers from r16 to r23 ! `d' Registers from r16 to r31 ! `w' Registers from r24 to r31. These registers can be used in ! `adiw' command ! `e' Pointer register (r26-r31) ! `b' Base pointer register (r28-r31) ! `q' Stack pointer register (SPH:SPL) ! `t' Temporary register r0 ! `x' Register pair X (r27:r26) ! `y' Register pair Y (r29:r28) ! `z' Register pair Z (r31:r30) ! `I' Constant greater than -1, less than 64 ! `J' Constant greater than -64, less than 1 ! `K' Constant integer 2 ! `L' Constant integer 0 ! `M' Constant that fits in 8 bits ! `N' Constant integer -1 ! `O' Constant integer 8, 16, or 24 ! `P' Constant integer 1 ! `G' A floating point constant 0.0 ! `Q' A memory address based on Y or Z pointer with displacement. ! _Blackfin family--`config/bfin/constraints.md'_ ! ! `a' P register ! `d' D register ! `z' A call clobbered P register. ! `qN' A single register. If N is in the range 0 to 7, the ! corresponding D register. If it is `A', then the register P0. ! `D' Even-numbered D register ! `W' Odd-numbered D register ! `e' Accumulator register. ! `A' Even-numbered accumulator register. ! `B' Odd-numbered accumulator register. ! `b' I register ! `v' B register ! `f' M register ! `c' ! Registers used for circular buffering, i.e. I, B, or L registers. ! `C' The CC register. ! `t' LT0 or LT1. ! `k' LC0 or LC1. ! `u' LB0 or LB1. ! `x' Any D, P, B, M, I or L register. ! `y' Additional registers typically used only in prologues and epilogues: RETS, RETN, RETI, RETX, RETE, ASTAT, SEQSTAT and USP. ! `w' Any register except accumulators or CC. ! `Ksh' Signed 16 bit integer (in the range -32768 to 32767) ! `Kuh' Unsigned 16 bit integer (in the range 0 to 65535) ! `Ks7' Signed 7 bit integer (in the range -64 to 63) ! `Ku7' Unsigned 7 bit integer (in the range 0 to 127) ! `Ku5' Unsigned 5 bit integer (in the range 0 to 31) ! `Ks4' Signed 4 bit integer (in the range -8 to 7) ! `Ks3' Signed 3 bit integer (in the range -3 to 4) ! `Ku3' Unsigned 3 bit integer (in the range 0 to 7) ! `PN' Constant N, where N is a single-digit constant in the range 0 to 4. ! `PA' An integer equal to one of the MACFLAG_XXX constants that is suitable for use with either accumulator. ! `PB' An integer equal to one of the MACFLAG_XXX constants that is suitable for use only with accumulator A1. ! `M1' Constant 255. ! `M2' Constant 65535. ! `J' An integer constant with exactly a single bit set. ! `L' An integer constant with all bits set except exactly one. ! `H' ! `Q' Any SYMBOL_REF. ! _CR16 Architecture--`config/cr16/cr16.h'_ ! `b' Registers from r0 to r14 (registers without stack pointer) ! `t' Register from r0 to r11 (all 16-bit registers) ! `p' Register from r12 to r15 (all 32-bit registers) ! `I' Signed constant that fits in 4 bits ! `J' Signed constant that fits in 5 bits ! `K' Signed constant that fits in 6 bits ! `L' Unsigned constant that fits in 4 bits ! `M' Signed constant that fits in 32 bits ! `N' Check for 64 bits wide constants for add/sub instructions ! `G' Floating point constant that is legal for store immediate ! _Epiphany--`config/epiphany/constraints.md'_ ! ! `U16' An unsigned 16-bit constant. ! `K' An unsigned 5-bit constant. ! `L' A signed 11-bit constant. ! `Cm1' ! A signed 11-bit constant added to -1. Can only match when ! the `-m1reg-REG' option is active. ! `Cl1' Left-shift of -1, i.e., a bit mask with a block of leading ones, the rest being a block of trailing zeroes. Can only ! match when the `-m1reg-REG' option is active. ! `Cr1' Right-shift of -1, i.e., a bit mask with a trailing block of ones, the rest being zeroes. Or to put it another way, one less than a power of two. Can only match when the ! `-m1reg-REG' option is active. ! `Cal' ! Constant for arithmetic/logical operations. This is like ! `i', except that for position independent code, no symbols / expressions needing relocations are allowed. ! `Csy' Symbolic constant for call/jump instruction. ! `Rcs' The register class usable in short insns. This is a register class constraint, and can thus drive register allocation. ! This constraint won't match unless `-mprefer-short-insn-regs' is in effect. ! `Rsc' The the register class of registers that can be used to hold a sibcall call address. I.e., a caller-saved register. ! `Rct' Core control register class. ! `Rgs' The register group usable in short insns. This constraint does not use a register class, so that it only passively matches suitable registers, and doesn't drive register allocation. ! `Car' Constant suitable for the addsi3_r pattern. This is a valid offset For byte, halfword, or word addressing. ! `Rra' ! Matches the return address if it can be replaced with the ! link register. ! `Rcc' Matches the integer condition code register. ! `Sra' Matches the return address if it is in a stack slot. ! `Cfm' Matches control register values to switch fp mode, which are ! encapsulated in `UNSPEC_FP_MODE'. ! _FRV--`config/frv/frv.h'_ ! `a' ! Register in the class `ACC_REGS' (`acc0' to `acc7'). ! `b' ! Register in the class `EVEN_ACC_REGS' (`acc0' to `acc7'). ! `c' ! Register in the class `CC_REGS' (`fcc0' to `fcc3' and `icc0' ! to `icc3'). ! `d' ! Register in the class `GPR_REGS' (`gr0' to `gr63'). ! `e' ! Register in the class `EVEN_REGS' (`gr0' to `gr63'). Odd ! registers are excluded not in the class but through the use ! of a machine mode larger than 4 bytes. ! `f' ! Register in the class `FPR_REGS' (`fr0' to `fr63'). ! `h' ! Register in the class `FEVEN_REGS' (`fr0' to `fr63'). Odd ! registers are excluded not in the class but through the use ! of a machine mode larger than 4 bytes. ! `l' ! Register in the class `LR_REG' (the `lr' register). ! `q' ! Register in the class `QUAD_REGS' (`gr2' to `gr63'). ! Register numbers not divisible by 4 are excluded not in the ! class but through the use of a machine mode larger than 8 ! bytes. ! `t' ! Register in the class `ICC_REGS' (`icc0' to `icc3'). ! `u' ! Register in the class `FCC_REGS' (`fcc0' to `fcc3'). ! `v' ! Register in the class `ICR_REGS' (`cc4' to `cc7'). ! `w' ! Register in the class `FCR_REGS' (`cc0' to `cc3'). ! ! `x' ! Register in the class `QUAD_FPR_REGS' (`fr0' to `fr63'). Register numbers not divisible by 4 are excluded not in the class but through the use of a machine mode larger than 8 bytes. ! `z' ! Register in the class `SPR_REGS' (`lcr' and `lr'). ! `A' ! Register in the class `QUAD_ACC_REGS' (`acc0' to `acc7'). ! `B' ! Register in the class `ACCG_REGS' (`accg0' to `accg7'). ! `C' ! Register in the class `CR_REGS' (`cc0' to `cc7'). ! `G' Floating point constant zero ! `I' 6-bit signed integer constant ! `J' 10-bit signed integer constant ! `L' 16-bit signed integer constant ! `M' 16-bit unsigned integer constant ! `N' 12-bit signed integer constant that is negative--i.e. in the range of -2048 to -1 ! `O' Constant zero ! `P' ! 12-bit signed integer constant that is greater than ! zero--i.e. in the range of 1 to 2047. ! ! _FT32--`config/ft32/constraints.md'_ ! ! `A' An absolute address ! `B' An offset address ! `W' A register indirect memory operand ! `e' An offset address. ! `f' An offset address. ! `O' The constant zero or one ! `I' A 16-bit signed constant (-32768 ... 32767) ! `w' A bitfield mask suitable for bext or bins ! `x' An inverted bitfield mask suitable for bext or bins ! `L' A 16-bit unsigned constant, multiple of 4 (0 ... 65532) ! `S' A 20-bit signed constant (-524288 ... 524287) ! `b' A constant for a bitfield width (1 ... 16) ! `KA' A 10-bit signed constant (-512 ... 511) ! ! _Hewlett-Packard PA-RISC--`config/pa/pa.h'_ ! ! `a' General register 1 ! `f' Floating point register ! `q' Shift amount register ! `x' Floating point register (deprecated) ! `y' Upper floating point register (32-bit), floating point register (64-bit) ! `Z' Any register ! `I' Signed 11-bit integer constant ! `J' Signed 14-bit integer constant ! `K' ! Integer constant that can be deposited with a `zdepi' instruction ! `L' Signed 5-bit integer constant ! `M' Integer constant 0 ! `N' ! Integer constant that can be loaded with a `ldil' instruction ! `O' Integer constant whose value plus one is a power of 2 ! `P' ! Integer constant that can be used for `and' operations in ! `depi' and `extru' instructions ! `S' Integer constant 31 ! `U' Integer constant 63 ! `G' Floating-point constant 0.0 ! `A' ! A `lo_sum' data-linkage-table memory operand ! `Q' A memory operand that can be used as the destination operand of an integer store instruction ! `R' A scaled or unscaled indexed memory operand ! `T' A memory operand for floating-point loads and stores ! `W' A register indirect memory operand ! _Intel IA-64--`config/ia64/ia64.h'_ ! `a' ! General register `r0' to `r3' for `addl' instruction ! ! `b' Branch register ! `c' ! Predicate register (`c' as in "conditional") ! `d' Application register residing in M-unit ! `e' Application register residing in I-unit ! `f' Floating-point register ! `m' ! Memory operand. If used together with `<' or `>', the ! operand can have postincrement and postdecrement which ! require printing with `%Pn' on IA-64. ! `G' Floating-point constant 0.0 or 1.0 ! `I' 14-bit signed integer constant ! `J' 22-bit signed integer constant ! `K' 8-bit signed integer constant for logical instructions ! `L' 8-bit adjusted signed integer constant for compare pseudo-ops ! `M' 6-bit unsigned integer constant for shift counts ! `N' 9-bit signed integer constant for load and store postincrements ! `O' The constant zero ! `P' ! 0 or -1 for `dep' instruction ! `Q' Non-volatile memory for floating-point loads and stores ! `R' ! Integer constant in the range 1 to 4 for `shladd' instruction ! `S' Memory operand except postincrement and postdecrement. This ! is now roughly the same as `m' when not used together with `<' ! or `>'. ! _M32C--`config/m32c/m32c.c'_ ! `Rsp' ! `Rfb' ! `Rsb' ! `$sp', `$fb', `$sb'. ! ! `Rcr' Any control register, when they're 16 bits wide (nothing if control registers are 24 bits wide) ! `Rcl' Any control register, when they're 24 bits wide. ! `R0w' ! `R1w' ! `R2w' ! `R3w' $r0, $r1, $r2, $r3. ! `R02' $r0 or $r2, or $r2r0 for 32 bit values. ! `R13' $r1 or $r3, or $r3r1 for 32 bit values. ! `Rdi' A register that can hold a 64 bit value. ! `Rhl' $r0 or $r1 (registers with addressable high/low bytes) ! `R23' $r2 or $r3 ! `Raa' Address registers ! `Raw' Address registers when they're 16 bits wide. ! `Ral' Address registers when they're 24 bits wide. ! `Rqi' Registers that can hold QI values. ! `Rad' Registers that can be used with displacements ($a0, $a1, $sb). ! `Rsi' Registers that can hold 32 bit values. ! `Rhi' Registers that can hold 16 bit values. ! `Rhc' Registers chat can hold 16 bit values, including all control registers. ! `Rra' $r0 through R1, plus $a0 and $a1. ! `Rfl' The flags register. ! `Rmm' The memory-based pseudo-registers $mem0 through $mem15. ! `Rpi' Registers that can hold pointers (16 bit registers for r8c, m16c; 24 bit registers for m32cm, m32c). ! `Rpa' Matches multiple registers in a PARALLEL to form a larger register. Used to match function return values. ! `Is3' -8 ... 7 ! `IS1' -128 ... 127 ! `IS2' -32768 ... 32767 ! `IU2' 0 ... 65535 ! `In4' -8 ... -1 or 1 ... 8 ! `In5' -16 ... -1 or 1 ... 16 ! `In6' -32 ... -1 or 1 ... 32 ! `IM2' -65536 ... -1 ! `Ilb' An 8 bit value with exactly one bit set. ! `Ilw' A 16 bit value with exactly one bit set. ! `Sd' The common src/dest memory addressing modes. ! `Sa' Memory addressed using $a0 or $a1. ! `Si' Memory addressed with immediate addresses. ! `Ss' Memory addressed using the stack pointer ($sp). ! `Sf' Memory addressed using the frame base register ($fb). ! `Ss' Memory addressed using the small base register ($sb). ! `S1' $r1h ! _MeP--`config/mep/constraints.md'_ ! `a' The $sp register. ! `b' The $tp register. ! `c' Any control register. ! `d' Either the $hi or the $lo register. ! `em' Coprocessor registers that can be directly loaded ($c0-$c15). ! `ex' Coprocessor registers that can be moved to each other. ! `er' Coprocessor registers that can be moved to core registers. ! `h' The $hi register. ! `j' The $rpc register. ! `l' The $lo register. ! `t' Registers which can be used in $tp-relative addressing. ! `v' The $gp register. ! `x' The coprocessor registers. ! `y' The coprocessor control registers. ! `z' The $0 register. ! `A' User-defined register set A. ! `B' User-defined register set B. ! `C' User-defined register set C. ! `D' User-defined register set D. ! `I' Offsets for $gp-rel addressing. ! `J' Constants that can be used directly with boolean insns. ! `K' Constants that can be moved directly to registers. ! `L' Small constants that can be added to registers. ! `M' Long shift counts. ! `N' Small constants that can be compared to registers. ! `O' Constants that can be loaded into the top half of registers. ! `S' Signed 8-bit immediates. ! `T' Symbols encoded for $tp-rel or $gp-rel addressing. ! `U' Non-constant addresses for loading/saving coprocessor registers. ! `W' The top half of a symbol's value. ! `Y' A register indirect address without offset. ! `Z' Symbolic references to the control bus. ! _MicroBlaze--`config/microblaze/constraints.md'_ ! `d' ! A general register (`r0' to `r31'). ! ! `z' ! A status register (`rmsr', `$fcc1' to `$fcc7'). ! ! ! _MIPS--`config/mips/constraints.md'_ ! ! `d' ! An address register. This is equivalent to `r' unless generating MIPS16 code. ! `f' A floating-point register (if available). ! `h' ! Formerly the `hi' register. This constraint is no longer supported. ! `l' ! The `lo' register. Use this register to store values that are no bigger than a word. ! `x' ! The concatenated `hi' and `lo' registers. Use this register to store doubleword values. ! `c' A register suitable for use in an indirect jump. This will ! always be `$25' for `-mabicalls'. ! `v' ! Register `$3'. Do not use this constraint in new code; it is retained only for compatibility with glibc. ! `y' ! Equivalent to `r'; retained for backwards compatibility. ! `z' A floating-point condition code register. ! `I' A signed 16-bit constant (for arithmetic instructions). ! `J' Integer zero. ! `K' An unsigned 16-bit constant (for logic instructions). ! `L' A signed 32-bit constant in which the lower 16 bits are zero. ! Such constants can be loaded using `lui'. ! `M' ! A constant that cannot be loaded using `lui', `addiu' or ! `ori'. ! `N' A constant in the range -65535 to -1 (inclusive). ! `O' A signed 15-bit constant. ! `P' A constant in the range 1 to 65535 (inclusive). ! `G' Floating-point zero. ! `R' An address that can be used in a non-macro load or store. ! `ZC' A memory operand whose address is formed by a base register and offset that is suitable for use in instructions with the ! same addressing mode as `ll' and `sc'. ! `ZD' ! An address suitable for a `prefetch' instruction, or for any ! other instruction with the same addressing mode as `prefetch'. ! _Motorola 680x0--`config/m68k/constraints.md'_ ! ! `a' Address register ! `d' Data register ! `f' 68881 floating-point register, if available ! `I' Integer in the range 1 to 8 ! `J' 16-bit signed number ! `K' Signed number whose magnitude is greater than 0x80 ! `L' Integer in the range -8 to -1 ! `M' Signed number whose magnitude is greater than 0x100 ! `N' Range 24 to 31, rotatert:SI 8 to 1 expressed as rotate ! `O' 16 (for rotate using swap) ! `P' Range 8 to 15, rotatert:HI 8 to 1 expressed as rotate ! `R' Numbers that mov3q can handle ! `G' Floating point constant that is not a 68881 constant ! `S' Operands that satisfy 'm' when -mpcrel is in effect ! `T' Operands that satisfy 's' when -mpcrel is not in effect ! `Q' Address register indirect addressing mode ! `U' Register offset addressing ! `W' const_call_operand ! `Cs' symbol_ref or const ! `Ci' const_int ! `C0' const_int 0 ! `Cj' Range of signed numbers that don't fit in 16 bits ! `Cmvq' Integers valid for mvq ! `Capsw' Integers valid for a moveq followed by a swap ! `Cmvz' Integers valid for mvz ! `Cmvs' Integers valid for mvs ! `Ap' push_operand ! `Ac' Non-register operands allowed in clr ! ! _Moxie--`config/moxie/constraints.md'_ ! ! `A' An absolute address ! `B' An offset address ! `W' A register indirect memory operand ! `I' A constant in the range of 0 to 255. ! `N' A constant in the range of 0 to -255. ! _MSP430-`config/msp430/constraints.md'_ ! ! `R12' Register R12. ! `R13' Register R13. ! `K' Integer constant 1. ! `L' Integer constant -1^20..1^19. ! `M' Integer constant 1-4. ! `Ya' Memory references which do not require an extended MOVX instruction. ! `Yl' Memory reference, labels only. ! `Ys' Memory reference, stack only. ! ! _NDS32--`config/nds32/constraints.md'_ ! ! `w' LOW register class $r0 to $r7 constraint for V3/V3M ISA. ! ! `l' LOW register class $r0 to $r7. ! ! `d' MIDDLE register class $r0 to $r11, $r16 to $r19. ! ! `h' HIGH register class $r12 to $r14, $r20 to $r31. ! ! `t' Temporary assist register $ta (i.e. $r15). ! ! `k' Stack register $sp. ! ! `Iu03' Unsigned immediate 3-bit value. ! ! `In03' Negative immediate 3-bit value in the range of -7-0. ! ! `Iu04' Unsigned immediate 4-bit value. ! ! `Is05' Signed immediate 5-bit value. ! ! `Iu05' Unsigned immediate 5-bit value. ! ! `In05' Negative immediate 5-bit value in the range of -31-0. ! ! `Ip05' Unsigned immediate 5-bit value for movpi45 instruction with range 16-47. ! ! `Iu06' Unsigned immediate 6-bit value constraint for addri36.sp instruction. ! ! `Iu08' Unsigned immediate 8-bit value. ! ! `Iu09' Unsigned immediate 9-bit value. ! ! `Is10' Signed immediate 10-bit value. ! ! `Is11' Signed immediate 11-bit value. ! ! `Is15' Signed immediate 15-bit value. ! ! `Iu15' Unsigned immediate 15-bit value. ! ! `Ic15' ! A constant which is not in the range of imm15u but ok for ! bclr instruction. ! ! `Ie15' ! A constant which is not in the range of imm15u but ok for ! bset instruction. ! ! `It15' ! A constant which is not in the range of imm15u but ok for ! btgl instruction. ! ! `Ii15' A constant whose compliment value is in the range of imm15u and ok for bitci instruction. ! ! `Is16' Signed immediate 16-bit value. ! ! `Is17' Signed immediate 17-bit value. ! ! `Is19' Signed immediate 19-bit value. ! ! `Is20' Signed immediate 20-bit value. ! ! `Ihig' The immediate value that can be simply set high 20-bit. ! ! `Izeb' The immediate value 0xff. ! ! `Izeh' The immediate value 0xffff. ! ! `Ixls' The immediate value 0x01. ! ! `Ix11' The immediate value 0x7ff. ! ! `Ibms' The immediate value with power of 2. ! ! `Ifex' The immediate value with power of 2 minus 1. ! ! `U33' Memory constraint for 333 format. ! ! `U45' Memory constraint for 45 format. ! ! `U37' Memory constraint for 37 format. ! _Nios II family--`config/nios2/constraints.md'_ ! `I' Integer that is valid as an immediate operand in an ! instruction taking a signed 16-bit number. Range -32768 to 32767. ! `J' Integer that is valid as an immediate operand in an ! instruction taking an unsigned 16-bit number. Range 0 to 65535. ! `K' Integer that is valid as an immediate operand in an instruction taking only the upper 16-bits of a 32-bit number. Range 32-bit numbers with the lower 16-bits being 0. ! `L' Integer that is valid as an immediate operand for a shift ! instruction. Range 0 to 31. ! `M' Integer that is valid as an immediate operand for only the ! value 0. Can be used in conjunction with the format modifier ! `z' to use `r0' instead of `0' in the assembly output. ! `N' Integer that is valid as an immediate operand for a custom ! instruction opcode. Range 0 to 255. ! `P' An immediate operand for R2 andchi/andci instructions. ! `S' Matches immediates which are addresses in the small data ! section and therefore can be added to `gp' as a 16-bit immediate to re-create their 32-bit value. ! `U' Matches constants suitable as an operand for the rdprs and cache instructions. ! `v' A memory operand suitable for Nios II R2 load/store exclusive instructions. ! `w' A memory operand suitable for load/store IO and cache instructions. ! `T' ! A `const' wrapped `UNSPEC' expression, representing a supported PIC or TLS relocation. ! _PDP-11--`config/pdp11/constraints.md'_ ! ! `a' ! Floating point registers AC0 through AC3. These can be ! loaded from/to memory with a single instruction. ! ! `d' Odd numbered general registers (R1, R3, R5). These are used for 16-bit multiply operations. ! `f' Any of the floating point registers (AC0 through AC5). ! `G' Floating point constant 0. ! `I' An integer constant that fits in 16 bits. ! `J' An integer constant whose low order 16 bits are zero. ! `K' An integer constant that does not meet the constraints for ! codes `I' or `J'. ! `L' The integer constant 1. ! `M' The integer constant -1. ! `N' The integer constant 0. ! `O' Integer constants -4 through -1 and 1 through 4; shifts by ! these amounts are handled as multiple single-bit shifts ! rather than a single variable-length shift. ! `Q' A memory reference which requires an additional word (address or offset) after the opcode. ! `R' A memory reference that is encoded within the opcode. ! ! _PowerPC and IBM RS6000--`config/rs6000/constraints.md'_ ! ! `b' Address base register ! `d' Floating point register (containing 64-bit value) ! `f' Floating point register (containing 32-bit value) ! `v' Altivec vector register ! `wa' Any VSX register if the -mvsx option was used or NO_REGS. ! When using any of the register constraints (`wa', `wd', `wf', ! `wg', `wh', `wi', `wj', `wk', `wl', `wm', `wo', `wp', `wq', ! `ws', `wt', `wu', `wv', `ww', or `wy') that take VSX ! registers, you must use `%x' in the template so that the correct register is used. Otherwise the register number output in the assembly file will be incorrect if an Altivec register is an operand of a VSX instruction that expects VSX *************** _PowerPC and IBM RS6000--'config/rs6000/ *** 21267,21462 **** is not correct. If an instruction only takes Altivec registers, you do not ! want to use '%x'. asm ("xsaddqp %0,%1,%2" : "=v" (v1) : "v" (v2), "v" (v3)); ! is correct because the 'xsaddqp' instruction only takes Altivec registers, while: asm ("xsaddqp %x0,%x1,%x2" : "=v" (v1) : "v" (v2), "v" (v3)); is incorrect. ! 'wb' ! Altivec register if '-mpower9-dform' is used or NO_REGS. ! 'wd' VSX vector register to hold vector double data or NO_REGS. ! 'we' ! VSX register if the '-mpower9-vector' and '-m64' options were used or NO_REGS. ! 'wf' VSX vector register to hold vector float data or NO_REGS. ! 'wg' ! If '-mmfpgpr' was used, a floating point register or NO_REGS. ! 'wh' Floating point register if direct moves are available, or NO_REGS. ! 'wi' FP or VSX register to hold 64-bit integers for VSX insns or NO_REGS. ! 'wj' ! FP or VSX register to hold 64-bit integers for direct moves or ! NO_REGS. ! 'wk' FP or VSX register to hold 64-bit doubles for direct moves or NO_REGS. ! 'wl' Floating point register if the LFIWAX instruction is enabled or NO_REGS. ! 'wm' VSX register if direct move instructions are enabled, or NO_REGS. ! 'wn' No register (NO_REGS). ! 'wo' VSX register to use for ISA 3.0 vector instructions, or NO_REGS. ! 'wp' ! VSX register to use for IEEE 128-bit floating point TFmode, or ! NO_REGS. ! 'wq' VSX register to use for IEEE 128-bit floating point, or NO_REGS. ! 'wr' ! General purpose register if 64-bit instructions are enabled or ! NO_REGS. ! 'ws' VSX vector register to hold scalar double values or NO_REGS. ! 'wt' VSX vector register to hold 128 bit integer or NO_REGS. ! 'wu' ! Altivec register to use for float/32-bit int loads/stores or NO_REGS. ! 'wv' ! Altivec register to use for double loads/stores or NO_REGS. ! 'ww' ! FP or VSX register to perform float operations under '-mvsx' or NO_REGS. ! 'wx' Floating point register if the STFIWX instruction is enabled or NO_REGS. ! 'wy' FP or VSX register to perform ISA 2.07 float ops or NO_REGS. ! 'wz' Floating point register if the LFIWZX instruction is enabled or NO_REGS. ! 'wD' Int constant that is the element number of the 64-bit scalar in a vector. ! 'wE' Vector constant that can be loaded with the XXSPLTIB instruction. ! 'wF' Memory operand suitable for power9 fusion load/stores. ! 'wG' Memory operand suitable for TOC fusion memory references. ! 'wL' Int constant that is the element number that the MFVSRLD instruction. targets. ! 'wM' Match vector constant with all 1's if the XXLORC instruction is available. ! 'wO' A memory operand suitable for the ISA 3.0 vector d-form instructions. ! 'wQ' ! A memory address that will work with the 'lq' and 'stq' instructions. ! 'wS' Vector constant that can be loaded with XXSPLTIB & sign extension. ! 'h' ! 'MQ', 'CTR', or 'LINK' register ! 'c' ! 'CTR' register ! 'l' ! 'LINK' register ! 'x' ! 'CR' register (condition register) number 0 ! 'y' ! 'CR' register (condition register) ! 'z' ! 'XER[CA]' carry bit (part of the XER register) ! 'I' Signed 16-bit constant ! 'J' ! Unsigned 16-bit constant shifted left 16 bits (use 'L' instead ! for 'SImode' constants) ! 'K' Unsigned 16-bit constant ! 'L' Signed 16-bit constant shifted left 16 bits ! 'M' Constant larger than 31 ! 'N' Exact power of 2 ! 'O' Zero ! 'P' Constant whose negation is a signed 16-bit constant ! 'G' Floating point constant that can be loaded into a register with one instruction per word ! 'H' Integer/Floating point constant that can be loaded into a register using three instructions ! 'm' ! Memory operand. Normally, 'm' does not allow addresses that ! update the base register. If '<' or '>' constraint is also used, they are allowed and therefore on PowerPC targets in ! that case it is only safe to use 'm<>' in an 'asm' statement ! if that 'asm' statement accesses the operand exactly once. ! The 'asm' statement must also use '%U' as a placeholder for the "update" flag in the corresponding load or store instruction. For example: --- 21562,21761 ---- is not correct. If an instruction only takes Altivec registers, you do not ! want to use `%x'. asm ("xsaddqp %0,%1,%2" : "=v" (v1) : "v" (v2), "v" (v3)); ! is correct because the `xsaddqp' instruction only takes Altivec registers, while: asm ("xsaddqp %x0,%x1,%x2" : "=v" (v1) : "v" (v2), "v" (v3)); is incorrect. ! `wb' ! Altivec register if `-mcpu=power9' is used or NO_REGS. ! `wd' VSX vector register to hold vector double data or NO_REGS. ! `we' ! VSX register if the `-mcpu=power9' and `-m64' options were used or NO_REGS. ! `wf' VSX vector register to hold vector float data or NO_REGS. ! `wg' ! If `-mmfpgpr' was used, a floating point register or NO_REGS. ! `wh' Floating point register if direct moves are available, or NO_REGS. ! `wi' FP or VSX register to hold 64-bit integers for VSX insns or NO_REGS. ! `wj' ! FP or VSX register to hold 64-bit integers for direct moves ! or NO_REGS. ! `wk' FP or VSX register to hold 64-bit doubles for direct moves or NO_REGS. ! `wl' Floating point register if the LFIWAX instruction is enabled or NO_REGS. ! `wm' VSX register if direct move instructions are enabled, or NO_REGS. ! `wn' No register (NO_REGS). ! `wo' VSX register to use for ISA 3.0 vector instructions, or NO_REGS. ! `wp' ! VSX register to use for IEEE 128-bit floating point TFmode, ! or NO_REGS. ! `wq' VSX register to use for IEEE 128-bit floating point, or NO_REGS. ! `wr' ! General purpose register if 64-bit instructions are enabled ! or NO_REGS. ! `ws' VSX vector register to hold scalar double values or NO_REGS. ! `wt' VSX vector register to hold 128 bit integer or NO_REGS. ! `wu' ! Altivec register to use for float/32-bit int loads/stores or NO_REGS. ! `wv' ! Altivec register to use for double loads/stores or NO_REGS. ! `ww' ! FP or VSX register to perform float operations under `-mvsx' or NO_REGS. ! `wx' Floating point register if the STFIWX instruction is enabled or NO_REGS. ! `wy' FP or VSX register to perform ISA 2.07 float ops or NO_REGS. ! `wz' Floating point register if the LFIWZX instruction is enabled or NO_REGS. ! `wA' ! Address base register if 64-bit instructions are enabled or ! NO_REGS. ! ! `wD' Int constant that is the element number of the 64-bit scalar in a vector. ! `wE' Vector constant that can be loaded with the XXSPLTIB instruction. ! `wF' Memory operand suitable for power9 fusion load/stores. ! `wG' Memory operand suitable for TOC fusion memory references. ! `wL' Int constant that is the element number that the MFVSRLD instruction. targets. ! `wM' Match vector constant with all 1's if the XXLORC instruction is available. ! `wO' A memory operand suitable for the ISA 3.0 vector d-form instructions. ! `wQ' ! A memory address that will work with the `lq' and `stq' instructions. ! `wS' Vector constant that can be loaded with XXSPLTIB & sign extension. ! `h' ! `MQ', `CTR', or `LINK' register ! `c' ! `CTR' register ! `l' ! `LINK' register ! `x' ! `CR' register (condition register) number 0 ! `y' ! `CR' register (condition register) ! `z' ! `XER[CA]' carry bit (part of the XER register) ! `I' Signed 16-bit constant ! `J' ! Unsigned 16-bit constant shifted left 16 bits (use `L' ! instead for `SImode' constants) ! `K' Unsigned 16-bit constant ! `L' Signed 16-bit constant shifted left 16 bits ! `M' Constant larger than 31 ! `N' Exact power of 2 ! `O' Zero ! `P' Constant whose negation is a signed 16-bit constant ! `G' Floating point constant that can be loaded into a register with one instruction per word ! `H' Integer/Floating point constant that can be loaded into a register using three instructions ! `m' ! Memory operand. Normally, `m' does not allow addresses that ! update the base register. If `<' or `>' constraint is also used, they are allowed and therefore on PowerPC targets in ! that case it is only safe to use `m<>' in an `asm' statement ! if that `asm' statement accesses the operand exactly once. ! The `asm' statement must also use `%U' as a placeholder for the "update" flag in the corresponding load or store instruction. For example: *************** _PowerPC and IBM RS6000--'config/rs6000/ *** 21468,22182 **** is not. ! 'es' ! A "stable" memory operand; that is, one which does not include ! any automodification of the base register. This used to be ! useful when 'm' allowed automodification of the base register, ! but as those are now only allowed when '<' or '>' is used, ! 'es' is basically the same as 'm' without '<' and '>'. ! 'Q' Memory operand that is an offset from a register (it is ! usually better to use 'm' or 'es' in 'asm' statements) ! 'Z' Memory operand that is an indexed or indirect from a register ! (it is usually better to use 'm' or 'es' in 'asm' statements) ! 'R' AIX TOC entry ! 'a' ! Address operand that is an indexed or indirect from a register ! ('p' is preferable for 'asm' statements) ! 'U' System V Release 4 small data area reference ! 'W' Vector constant that does not require memory ! 'j' Vector constant that is all zeros. - _RL78--'config/rl78/constraints.md'_ ! 'Int3' An integer constant in the range 1 ... 7. ! 'Int8' An integer constant in the range 0 ... 255. ! 'J' An integer constant in the range -255 ... 0 ! 'K' The integer constant 1. ! 'L' The integer constant -1. ! 'M' The integer constant 0. ! 'N' The integer constant 2. ! 'O' The integer constant -2. ! 'P' An integer constant in the range 1 ... 15. ! 'Qbi' The built-in compare types-eq, ne, gtu, ltu, geu, and leu. ! 'Qsc' The synthetic compare types-gt, lt, ge, and le. ! 'Wab' A memory reference with an absolute address. ! 'Wbc' ! A memory reference using 'BC' as a base register, with an optional offset. ! 'Wca' ! A memory reference using 'AX', 'BC', 'DE', or 'HL' for the address, for calls. ! 'Wcv' A memory reference using any 16-bit register pair for the address, for calls. ! 'Wd2' ! A memory reference using 'DE' as a base register, with an optional offset. ! 'Wde' ! A memory reference using 'DE' as a base register, without any offset. ! 'Wfr' Any memory reference to an address in the far address space. ! 'Wh1' ! A memory reference using 'HL' as a base register, with an optional one-byte offset. ! 'Whb' ! A memory reference using 'HL' as a base register, with 'B' or ! 'C' as the index register. ! 'Whl' ! A memory reference using 'HL' as a base register, without any offset. ! 'Ws1' ! A memory reference using 'SP' as a base register, with an optional one-byte offset. ! 'Y' Any memory reference to an address in the near address space. ! 'A' ! The 'AX' register. ! 'B' ! The 'BC' register. ! 'D' ! The 'DE' register. ! 'R' ! 'A' through 'L' registers. ! 'S' ! The 'SP' register. ! 'T' ! The 'HL' register. ! 'Z08W' ! The 16-bit 'R8' register. ! 'Z10W' ! The 16-bit 'R10' register. ! 'Zint' ! The registers reserved for interrupts ('R24' to 'R31'). ! 'a' ! The 'A' register. ! 'b' ! The 'B' register. ! 'c' ! The 'C' register. ! 'd' ! The 'D' register. ! 'e' ! The 'E' register. ! 'h' ! The 'H' register. ! 'l' ! The 'L' register. ! 'v' The virtual registers. - 'w' - The 'PSW' register. - 'x' - The 'X' register. ! _RX--'config/rx/constraints.md'_ ! 'Q' ! An address which does not involve register indirect addressing ! or pre/post increment/decrement addressing. ! 'Symbol' A symbol reference. ! 'Int08' A constant in the range -256 to 255, inclusive. ! 'Sint08' A constant in the range -128 to 127, inclusive. ! 'Sint16' A constant in the range -32768 to 32767, inclusive. ! 'Sint24' A constant in the range -8388608 to 8388607, inclusive. ! 'Uint04' A constant in the range 0 to 15, inclusive. ! _S/390 and zSeries--'config/s390/s390.h'_ ! 'a' Address register (general purpose register except r0) ! 'c' Condition code register ! 'd' Data register (arbitrary general purpose register) ! 'f' Floating-point register ! 'I' Unsigned 8-bit constant (0-255) ! 'J' Unsigned 12-bit constant (0-4095) ! 'K' Signed 16-bit constant (-32768-32767) ! 'L' Value appropriate as displacement. ! '(0..4095)' for short displacement ! '(-524288..524287)' for long displacement ! 'M' Constant integer with a value of 0x7fffffff. ! 'N' Multiple letter constraint followed by 4 parameter letters. ! '0..9:' number of the part counting from most to least significant ! 'H,Q:' mode of the part ! 'D,S,H:' mode of the containing operand ! '0,F:' value of the other parts (F--all bits set) ! The constraint matches if the specified part of a constant has ! a value different from its other parts. ! 'Q' Memory reference without index register and with short displacement. ! 'R' Memory reference with index register and short displacement. ! 'S' Memory reference without index register but with long displacement. ! 'T' Memory reference with index register and long displacement. ! 'U' Pointer with short displacement. ! 'W' Pointer with long displacement. ! 'Y' Shift count operand. - _SPARC--'config/sparc/sparc.h'_ - 'f' - Floating-point register on the SPARC-V8 architecture and lower - floating-point register on the SPARC-V9 architecture. ! 'e' ! Floating-point register. It is equivalent to 'f' on the SPARC-V8 architecture and contains both lower and upper floating-point registers on the SPARC-V9 architecture. ! 'c' Floating-point condition code register. ! 'd' Lower floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! 'b' Floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! 'h' 64-bit global or out register for the SPARC-V8+ architecture. ! 'C' The constant all-ones, for floating-point. ! 'A' Signed 5-bit constant ! 'D' A vector constant ! 'I' Signed 13-bit constant ! 'J' Zero ! 'K' 32-bit constant with the low 12 bits clear (a constant that ! can be loaded with the 'sethi' instruction) ! 'L' ! A constant in the range supported by 'movcc' instructions (11-bit signed immediate) ! 'M' ! A constant in the range supported by 'movrcc' instructions (10-bit signed immediate) ! 'N' ! Same as 'K', except that it verifies that bits that are not in ! the lower 32-bit range are all zero. Must be used instead of ! 'K' for modes wider than 'SImode' ! 'O' The constant 4096 ! 'G' Floating-point zero ! 'H' Signed 13-bit constant, sign-extended to 32 or 64 bits ! 'P' The constant -1 ! 'Q' Floating-point constant whose integral representation can be moved into an integer register using a single sethi instruction ! 'R' Floating-point constant whose integral representation can be moved into an integer register using a single mov instruction ! 'S' Floating-point constant whose integral representation can be ! moved into an integer register using a high/lo_sum instruction ! sequence ! 'T' Memory address aligned to an 8-byte boundary ! 'U' Even register ! 'W' ! Memory address for 'e' constraint registers ! 'w' Memory address with only a base register ! 'Y' Vector zero ! _SPU--'config/spu/spu.h'_ ! 'a' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 64 bit value. ! 'c' An immediate for and/xor/or instructions. const_int is treated as a 64 bit value. ! 'd' ! An immediate for the 'iohl' instruction. const_int is treated ! as a 64 bit value. ! 'f' ! An immediate which can be loaded with 'fsmbi'. ! 'A' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 32 bit value. ! 'B' An immediate for most arithmetic instructions. const_int is treated as a 32 bit value. ! 'C' An immediate for and/xor/or instructions. const_int is treated as a 32 bit value. ! 'D' ! An immediate for the 'iohl' instruction. const_int is treated ! as a 32 bit value. ! 'I' A constant in the range [-64, 63] for shift/rotate instructions. ! 'J' An unsigned 7-bit constant for conversion/nop/channel instructions. ! 'K' A signed 10-bit constant for most arithmetic instructions. ! 'M' ! A signed 16 bit immediate for 'stop'. ! 'N' ! An unsigned 16-bit constant for 'iohl' and 'fsmbi'. ! 'O' An unsigned 7-bit constant whose 3 least significant bits are 0. ! 'P' An unsigned 3-bit constant for 16-byte rotates and shifts ! 'R' Call operand, reg, for indirect calls ! 'S' Call operand, symbol, for relative calls. ! 'T' Call operand, const_int, for absolute calls. ! 'U' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is sign extended to 128 bit. ! 'W' An immediate for shift and rotate instructions. const_int is treated as a 32 bit value. ! 'Y' An immediate for and/xor/or instructions. const_int is sign extended as a 128 bit. ! 'Z' ! An immediate for the 'iohl' instruction. const_int is sign extended to 128 bit. ! _TI C6X family--'config/c6x/constraints.md'_ ! 'a' Register file A (A0-A31). ! 'b' Register file B (B0-B31). ! 'A' Predicate registers in register file A (A0-A2 on C64X and higher, A1 and A2 otherwise). ! 'B' Predicate registers in register file B (B0-B2). ! 'C' A call-used register in register file B (B0-B9, B16-B31). ! 'Da' Register file A, excluding predicate registers (A3-A31, plus A0 if not C64X or higher). ! 'Db' Register file B, excluding predicate registers (B3-B31). ! 'Iu4' Integer constant in the range 0 ... 15. ! 'Iu5' Integer constant in the range 0 ... 31. ! 'In5' Integer constant in the range -31 ... 0. ! 'Is5' Integer constant in the range -16 ... 15. ! 'I5x' Integer constant that can be the operand of an ADDA or a SUBA insn. ! 'IuB' Integer constant in the range 0 ... 65535. ! 'IsB' Integer constant in the range -32768 ... 32767. ! 'IsC' ! Integer constant in the range -2^{20} ... 2^{20} - 1. ! 'Jc' Integer constant that is a valid mask for the clr instruction. ! 'Js' Integer constant that is a valid mask for the set instruction. ! 'Q' Memory location with A base register. ! 'R' Memory location with B base register. ! 'S0' On C64x+ targets, a GP-relative small data reference. ! 'S1' ! Any kind of 'SYMBOL_REF', for use in a call address. ! 'Si' Any kind of immediate operand, unless it matches the S0 constraint. ! 'T' Memory location with B base register, but not using a long offset. ! 'W' A memory operand with an address that can't be used in an unaligned access. ! 'Z' Register B14 (aka DP). ! _TILE-Gx--'config/tilegx/constraints.md'_ ! 'R00' ! 'R01' ! 'R02' ! 'R03' ! 'R04' ! 'R05' ! 'R06' ! 'R07' ! 'R08' ! 'R09' ! 'R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! 'I' Signed 8-bit integer constant. ! 'J' Signed 16-bit integer constant. ! 'K' Unsigned 16-bit integer constant. ! 'L' ! Integer constant that fits in one signed byte when incremented ! by one (-129 ... 126). ! 'm' ! Memory operand. If used together with '<' or '>', the operand ! can have postincrement which requires printing with '%In' and ! '%in' on TILE-Gx. For example: asm ("st_add %I0,%1,%i0" : "=m<>" (*mem) : "r" (val)); ! 'M' A bit mask suitable for the BFINS instruction. ! 'N' Integer constant that is a byte tiled out eight times. ! 'O' The integer zero constant. ! 'P' Integer constant that is a sign-extended byte tiled out as four shorts. ! 'Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! 'S' Integer constant that has all 1 bits consecutive and starting at bit 0. ! 'T' A 16-bit fragment of a got, tls, or pc-relative reference. ! 'U' ! Memory operand except postincrement. This is roughly the same ! as 'm' when not used together with '<' or '>'. ! 'W' An 8-element vector constant with identical elements. ! 'Y' A 4-element vector constant with identical elements. ! 'Z0' The integer constant 0xffffffff. ! 'Z1' The integer constant 0xffffffff00000000. ! _TILEPro--'config/tilepro/constraints.md'_ ! 'R00' ! 'R01' ! 'R02' ! 'R03' ! 'R04' ! 'R05' ! 'R06' ! 'R07' ! 'R08' ! 'R09' ! 'R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! 'I' Signed 8-bit integer constant. ! 'J' Signed 16-bit integer constant. ! 'K' Nonzero integer constant with low 16 bits zero. ! 'L' ! Integer constant that fits in one signed byte when incremented ! by one (-129 ... 126). ! 'm' ! Memory operand. If used together with '<' or '>', the operand ! can have postincrement which requires printing with '%In' and ! '%in' on TILEPro. For example: asm ("swadd %I0,%1,%i0" : "=m<>" (mem) : "r" (val)); ! 'M' A bit mask suitable for the MM instruction. ! 'N' Integer constant that is a byte tiled out four times. ! 'O' The integer zero constant. ! 'P' ! Integer constant that is a sign-extended byte tiled out as two ! shorts. ! 'Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! 'T' A symbolic operand, or a 16-bit fragment of a got, tls, or pc-relative reference. ! 'U' ! Memory operand except postincrement. This is roughly the same ! as 'm' when not used together with '<' or '>'. ! 'W' A 4-element vector constant with identical elements. ! 'Y' A 2-element vector constant with identical elements. - _Visium--'config/visium/constraints.md'_ - 'b' - EAM register 'mdb' ! 'c' ! EAM register 'mdc' ! 'f' Floating point register ! 'k' Register for sibcall optimization ! 'l' ! General register, but not 'r29', 'r30' and 'r31' ! 't' ! Register 'r1' ! 'u' ! Register 'r2' ! 'v' ! Register 'r3' ! 'G' Floating-point constant 0.0 ! 'J' ! Integer constant in the range 0 .. 65535 (16-bit immediate) ! 'K' ! Integer constant in the range 1 .. 31 (5-bit immediate) ! 'L' ! Integer constant in the range -65535 .. -1 (16-bit negative immediate) ! 'M' Integer constant -1 ! 'O' Integer constant 0 ! 'P' Integer constant 32 ! _x86 family--'config/i386/constraints.md'_ ! 'R' Legacy register--the eight integer registers available on all ! i386 processors ('a', 'b', 'c', 'd', 'si', 'di', 'bp', 'sp'). ! 'q' ! Any register accessible as 'Rl'. In 32-bit mode, 'a', 'b', ! 'c', and 'd'; in 64-bit mode, any integer register. ! 'Q' ! Any register accessible as 'Rh': 'a', 'b', 'c', and 'd'. ! 'l' Any register that can be used as the index in a base+index memory access: that is, any general register except the stack pointer. ! 'a' ! The 'a' register. ! 'b' ! The 'b' register. ! 'c' ! The 'c' register. ! 'd' ! The 'd' register. ! 'S' ! The 'si' register. ! 'D' ! The 'di' register. ! 'A' ! The 'a' and 'd' registers. This class is used for ! instructions that return double word results in the 'ax:dx' ! register pair. Single word values will be allocated either in ! 'ax' or 'dx'. For example on i386 the following implements ! 'rdtsc': unsigned long long rdtsc (void) { --- 21767,22545 ---- is not. ! `es' ! A "stable" memory operand; that is, one which does not ! include any automodification of the base register. This used ! to be useful when `m' allowed automodification of the base ! register, but as those are now only allowed when `<' or `>' ! is used, `es' is basically the same as `m' without `<' and ! `>'. ! `Q' Memory operand that is an offset from a register (it is ! usually better to use `m' or `es' in `asm' statements) ! `Z' Memory operand that is an indexed or indirect from a register ! (it is usually better to use `m' or `es' in `asm' statements) ! `R' AIX TOC entry ! `a' ! Address operand that is an indexed or indirect from a ! register (`p' is preferable for `asm' statements) ! `U' System V Release 4 small data area reference ! `W' Vector constant that does not require memory ! `j' Vector constant that is all zeros. ! _RL78--`config/rl78/constraints.md'_ ! ! `Int3' An integer constant in the range 1 ... 7. ! ! `Int8' An integer constant in the range 0 ... 255. ! ! `J' An integer constant in the range -255 ... 0 ! ! `K' The integer constant 1. ! ! `L' The integer constant -1. ! ! `M' The integer constant 0. ! ! `N' The integer constant 2. ! ! `O' The integer constant -2. ! ! `P' An integer constant in the range 1 ... 15. ! ! `Qbi' The built-in compare types-eq, ne, gtu, ltu, geu, and leu. ! ! `Qsc' The synthetic compare types-gt, lt, ge, and le. ! ! `Wab' A memory reference with an absolute address. ! ! `Wbc' ! A memory reference using `BC' as a base register, with an optional offset. ! ! `Wca' ! A memory reference using `AX', `BC', `DE', or `HL' for the address, for calls. ! ! `Wcv' A memory reference using any 16-bit register pair for the address, for calls. ! ! `Wd2' ! A memory reference using `DE' as a base register, with an optional offset. ! ! `Wde' ! A memory reference using `DE' as a base register, without any offset. ! ! `Wfr' Any memory reference to an address in the far address space. ! ! `Wh1' ! A memory reference using `HL' as a base register, with an optional one-byte offset. ! ! `Whb' ! A memory reference using `HL' as a base register, with `B' or ! `C' as the index register. ! ! `Whl' ! A memory reference using `HL' as a base register, without any offset. ! ! `Ws1' ! A memory reference using `SP' as a base register, with an optional one-byte offset. ! ! `Y' Any memory reference to an address in the near address space. ! ! `A' ! The `AX' register. ! ! `B' ! The `BC' register. ! ! `D' ! The `DE' register. ! ! `R' ! `A' through `L' registers. ! ! `S' ! The `SP' register. ! ! `T' ! The `HL' register. ! ! `Z08W' ! The 16-bit `R8' register. ! ! `Z10W' ! The 16-bit `R10' register. ! ! `Zint' ! The registers reserved for interrupts (`R24' to `R31'). ! ! `a' ! The `A' register. ! ! `b' ! The `B' register. ! ! `c' ! The `C' register. ! ! `d' ! The `D' register. ! ! `e' ! The `E' register. ! ! `h' ! The `H' register. ! ! `l' ! The `L' register. ! ! `v' The virtual registers. ! `w' ! The `PSW' register. ! `x' ! The `X' register. ! ! ! _RX--`config/rx/constraints.md'_ ! ! `Q' ! An address which does not involve register indirect ! addressing or pre/post increment/decrement addressing. ! ! `Symbol' A symbol reference. ! `Int08' A constant in the range -256 to 255, inclusive. ! `Sint08' A constant in the range -128 to 127, inclusive. ! `Sint16' A constant in the range -32768 to 32767, inclusive. ! `Sint24' A constant in the range -8388608 to 8388607, inclusive. ! `Uint04' A constant in the range 0 to 15, inclusive. ! ! _S/390 and zSeries--`config/s390/s390.h'_ ! ! `a' Address register (general purpose register except r0) ! `c' Condition code register ! `d' Data register (arbitrary general purpose register) ! `f' Floating-point register ! `I' Unsigned 8-bit constant (0-255) ! `J' Unsigned 12-bit constant (0-4095) ! `K' Signed 16-bit constant (-32768-32767) ! `L' Value appropriate as displacement. ! `(0..4095)' for short displacement ! ! `(-524288..524287)' for long displacement ! `M' Constant integer with a value of 0x7fffffff. ! `N' Multiple letter constraint followed by 4 parameter letters. ! `0..9:' number of the part counting from most to least significant ! ! `H,Q:' mode of the part ! ! `D,S,H:' mode of the containing operand ! ! `0,F:' value of the other parts (F--all bits set) ! The constraint matches if the specified part of a constant ! has a value different from its other parts. ! `Q' Memory reference without index register and with short displacement. ! `R' Memory reference with index register and short displacement. ! `S' Memory reference without index register but with long displacement. ! `T' Memory reference with index register and long displacement. ! `U' Pointer with short displacement. ! `W' Pointer with long displacement. ! `Y' Shift count operand. ! _SPARC--`config/sparc/sparc.h'_ ! ! `f' ! Floating-point register on the SPARC-V8 architecture and ! lower floating-point register on the SPARC-V9 architecture. ! ! `e' ! Floating-point register. It is equivalent to `f' on the SPARC-V8 architecture and contains both lower and upper floating-point registers on the SPARC-V9 architecture. ! `c' Floating-point condition code register. ! `d' Lower floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! `b' Floating-point register. It is only valid on the SPARC-V9 architecture when the Visual Instruction Set is available. ! `h' 64-bit global or out register for the SPARC-V8+ architecture. ! `C' The constant all-ones, for floating-point. ! `A' Signed 5-bit constant ! `D' A vector constant ! `I' Signed 13-bit constant ! `J' Zero ! `K' 32-bit constant with the low 12 bits clear (a constant that ! can be loaded with the `sethi' instruction) ! `L' ! A constant in the range supported by `movcc' instructions (11-bit signed immediate) ! `M' ! A constant in the range supported by `movrcc' instructions (10-bit signed immediate) ! `N' ! Same as `K', except that it verifies that bits that are not ! in the lower 32-bit range are all zero. Must be used instead ! of `K' for modes wider than `SImode' ! `O' The constant 4096 ! `G' Floating-point zero ! `H' Signed 13-bit constant, sign-extended to 32 or 64 bits ! `P' The constant -1 ! `Q' Floating-point constant whose integral representation can be moved into an integer register using a single sethi instruction ! `R' Floating-point constant whose integral representation can be moved into an integer register using a single mov instruction ! `S' Floating-point constant whose integral representation can be ! moved into an integer register using a high/lo_sum ! instruction sequence ! `T' Memory address aligned to an 8-byte boundary ! `U' Even register ! `W' ! Memory address for `e' constraint registers ! `w' Memory address with only a base register ! `Y' Vector zero ! ! _SPU--`config/spu/spu.h'_ ! ! `a' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 64 bit value. ! `c' An immediate for and/xor/or instructions. const_int is treated as a 64 bit value. ! `d' ! An immediate for the `iohl' instruction. const_int is ! treated as a 64 bit value. ! `f' ! An immediate which can be loaded with `fsmbi'. ! `A' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is treated as a 32 bit value. ! `B' An immediate for most arithmetic instructions. const_int is treated as a 32 bit value. ! `C' An immediate for and/xor/or instructions. const_int is treated as a 32 bit value. ! `D' ! An immediate for the `iohl' instruction. const_int is ! treated as a 32 bit value. ! `I' A constant in the range [-64, 63] for shift/rotate instructions. ! `J' An unsigned 7-bit constant for conversion/nop/channel instructions. ! `K' A signed 10-bit constant for most arithmetic instructions. ! `M' ! A signed 16 bit immediate for `stop'. ! `N' ! An unsigned 16-bit constant for `iohl' and `fsmbi'. ! `O' An unsigned 7-bit constant whose 3 least significant bits are 0. ! `P' An unsigned 3-bit constant for 16-byte rotates and shifts ! `R' Call operand, reg, for indirect calls ! `S' Call operand, symbol, for relative calls. ! `T' Call operand, const_int, for absolute calls. ! `U' An immediate which can be loaded with the il/ila/ilh/ilhu instructions. const_int is sign extended to 128 bit. ! `W' An immediate for shift and rotate instructions. const_int is treated as a 32 bit value. ! `Y' An immediate for and/xor/or instructions. const_int is sign extended as a 128 bit. ! `Z' ! An immediate for the `iohl' instruction. const_int is sign extended to 128 bit. ! ! _TI C6X family--`config/c6x/constraints.md'_ ! ! `a' Register file A (A0-A31). ! `b' Register file B (B0-B31). ! `A' Predicate registers in register file A (A0-A2 on C64X and higher, A1 and A2 otherwise). ! `B' Predicate registers in register file B (B0-B2). ! `C' A call-used register in register file B (B0-B9, B16-B31). ! `Da' Register file A, excluding predicate registers (A3-A31, plus A0 if not C64X or higher). ! `Db' Register file B, excluding predicate registers (B3-B31). ! `Iu4' Integer constant in the range 0 ... 15. ! `Iu5' Integer constant in the range 0 ... 31. ! `In5' Integer constant in the range -31 ... 0. ! `Is5' Integer constant in the range -16 ... 15. ! `I5x' Integer constant that can be the operand of an ADDA or a SUBA insn. ! `IuB' Integer constant in the range 0 ... 65535. ! `IsB' Integer constant in the range -32768 ... 32767. ! `IsC' ! Integer constant in the range -2^20 ... 2^20 - 1. ! `Jc' Integer constant that is a valid mask for the clr instruction. ! `Js' Integer constant that is a valid mask for the set instruction. ! `Q' Memory location with A base register. ! `R' Memory location with B base register. ! `S0' On C64x+ targets, a GP-relative small data reference. ! `S1' ! Any kind of `SYMBOL_REF', for use in a call address. ! `Si' Any kind of immediate operand, unless it matches the S0 constraint. ! `T' Memory location with B base register, but not using a long offset. ! `W' A memory operand with an address that can't be used in an unaligned access. ! `Z' Register B14 (aka DP). ! ! _TILE-Gx--`config/tilegx/constraints.md'_ ! ! `R00' ! `R01' ! `R02' ! `R03' ! `R04' ! `R05' ! `R06' ! `R07' ! `R08' ! `R09' ! `R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! `I' Signed 8-bit integer constant. ! `J' Signed 16-bit integer constant. ! `K' Unsigned 16-bit integer constant. ! `L' ! Integer constant that fits in one signed byte when ! incremented by one (-129 ... 126). ! `m' ! Memory operand. If used together with `<' or `>', the ! operand can have postincrement which requires printing with ! `%In' and `%in' on TILE-Gx. For example: asm ("st_add %I0,%1,%i0" : "=m<>" (*mem) : "r" (val)); ! `M' A bit mask suitable for the BFINS instruction. ! `N' Integer constant that is a byte tiled out eight times. ! `O' The integer zero constant. ! `P' Integer constant that is a sign-extended byte tiled out as four shorts. ! `Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! `S' Integer constant that has all 1 bits consecutive and starting at bit 0. ! `T' A 16-bit fragment of a got, tls, or pc-relative reference. ! `U' ! Memory operand except postincrement. This is roughly the ! same as `m' when not used together with `<' or `>'. ! `W' An 8-element vector constant with identical elements. ! `Y' A 4-element vector constant with identical elements. ! `Z0' The integer constant 0xffffffff. ! `Z1' The integer constant 0xffffffff00000000. ! ! _TILEPro--`config/tilepro/constraints.md'_ ! ! `R00' ! `R01' ! `R02' ! `R03' ! `R04' ! `R05' ! `R06' ! `R07' ! `R08' ! `R09' ! `R10' Each of these represents a register constraint for an individual register, from r0 to r10. ! `I' Signed 8-bit integer constant. ! `J' Signed 16-bit integer constant. ! `K' Nonzero integer constant with low 16 bits zero. ! `L' ! Integer constant that fits in one signed byte when ! incremented by one (-129 ... 126). ! `m' ! Memory operand. If used together with `<' or `>', the ! operand can have postincrement which requires printing with ! `%In' and `%in' on TILEPro. For example: asm ("swadd %I0,%1,%i0" : "=m<>" (mem) : "r" (val)); ! `M' A bit mask suitable for the MM instruction. ! `N' Integer constant that is a byte tiled out four times. ! `O' The integer zero constant. ! `P' ! Integer constant that is a sign-extended byte tiled out as ! two shorts. ! `Q' Integer constant that fits in one signed byte when incremented (-129 ... 126), but excluding -1. ! `T' A symbolic operand, or a 16-bit fragment of a got, tls, or pc-relative reference. ! `U' ! Memory operand except postincrement. This is roughly the ! same as `m' when not used together with `<' or `>'. ! `W' A 4-element vector constant with identical elements. ! `Y' A 2-element vector constant with identical elements. ! _Visium--`config/visium/constraints.md'_ ! `b' ! EAM register `mdb' ! ! `c' ! EAM register `mdc' ! ! `f' Floating point register ! `k' Register for sibcall optimization ! `l' ! General register, but not `r29', `r30' and `r31' ! `t' ! Register `r1' ! `u' ! Register `r2' ! `v' ! Register `r3' ! `G' Floating-point constant 0.0 ! `J' ! Integer constant in the range 0 .. 65535 (16-bit immediate) ! `K' ! Integer constant in the range 1 .. 31 (5-bit immediate) ! `L' ! Integer constant in the range -65535 .. -1 (16-bit negative immediate) ! `M' Integer constant -1 ! `O' Integer constant 0 ! `P' Integer constant 32 ! _x86 family--`config/i386/constraints.md'_ ! ! `R' Legacy register--the eight integer registers available on all ! i386 processors (`a', `b', `c', `d', `si', `di', `bp', `sp'). ! `q' ! Any register accessible as `Rl'. In 32-bit mode, `a', `b', ! `c', and `d'; in 64-bit mode, any integer register. ! `Q' ! Any register accessible as `Rh': `a', `b', `c', and `d'. ! `l' Any register that can be used as the index in a base+index memory access: that is, any general register except the stack pointer. ! `a' ! The `a' register. ! `b' ! The `b' register. ! `c' ! The `c' register. ! `d' ! The `d' register. ! `S' ! The `si' register. ! `D' ! The `di' register. ! `A' ! The `a' and `d' registers. This class is used for ! instructions that return double word results in the `ax:dx' ! register pair. Single word values will be allocated either ! in `ax' or `dx'. For example on i386 the following ! implements `rdtsc': unsigned long long rdtsc (void) { *************** _x86 family--'config/i386/constraints.md *** 22186,22192 **** } This is not correct on x86-64 as it would allocate tick in ! either 'ax' or 'dx'. You have to use the following variant instead: unsigned long long rdtsc (void) --- 22549,22555 ---- } This is not correct on x86-64 as it would allocate tick in ! either `ax' or `dx'. You have to use the following variant instead: unsigned long long rdtsc (void) *************** _x86 family--'config/i386/constraints.md *** 22196,22407 **** return ((unsigned long long)tickh << 32)|tickl; } ! 'f' Any 80387 floating-point (stack) register. ! 't' ! Top of 80387 floating-point stack ('%st(0)'). ! 'u' ! Second from top of 80387 floating-point stack ('%st(1)'). ! 'y' Any MMX register. ! 'x' Any SSE register. ! 'Yz' ! First SSE register ('%xmm0'). ! 'Y2' Any SSE register, when SSE2 is enabled. ! 'Yi' Any SSE register, when SSE2 and inter-unit moves are enabled. ! 'Ym' Any MMX register, when inter-unit moves are enabled. ! 'I' Integer constant in the range 0 ... 31, for 32-bit shifts. ! 'J' Integer constant in the range 0 ... 63, for 64-bit shifts. ! 'K' Signed 8-bit integer constant. ! 'L' ! '0xFF' or '0xFFFF', for andsi as a zero-extending move. ! 'M' ! 0, 1, 2, or 3 (shifts for the 'lea' instruction). ! 'N' ! Unsigned 8-bit integer constant (for 'in' and 'out' instructions). ! 'O' Integer constant in the range 0 ... 127, for 128-bit shifts. ! 'G' Standard 80387 floating point constant. ! 'C' SSE constant zero operand. ! 'e' 32-bit signed integer constant, or a symbolic reference known to fit that range (for immediate operands in sign-extending x86-64 instructions). ! 'Z' 32-bit unsigned integer constant, or a symbolic reference known to fit that range (for immediate operands in zero-extending x86-64 instructions). ! _Xstormy16--'config/stormy16/stormy16.h'_ ! 'a' Register r0. ! 'b' Register r1. ! 'c' Register r2. ! 'd' Register r8. ! 'e' Registers r0 through r7. ! 't' Registers r0 and r1. ! 'y' The carry register. ! 'z' Registers r8 and r9. ! 'I' A constant between 0 and 3 inclusive. ! 'J' A constant that has exactly one bit set. ! 'K' A constant that has exactly one bit clear. ! 'L' A constant between 0 and 255 inclusive. ! 'M' A constant between -255 and 0 inclusive. ! 'N' A constant between -3 and 0 inclusive. ! 'O' A constant between 1 and 4 inclusive. ! 'P' A constant between -4 and -1 inclusive. ! 'Q' A memory reference that is a stack push. ! 'R' A memory reference that is a stack pop. ! 'S' A memory reference that refers to a constant address of known value. ! 'T' The register indicated by Rx (not implemented yet). ! 'U' A constant that is not between 2 and 15 inclusive. ! 'Z' The constant 0. ! _Xtensa--'config/xtensa/constraints.md'_ ! 'a' General-purpose 32-bit register ! 'b' One-bit boolean register ! 'A' MAC16 40-bit accumulator register ! 'I' Signed 12-bit integer constant, for use in MOVI instructions ! 'J' Signed 8-bit integer constant, for use in ADDI instructions ! 'K' Integer constant valid for BccI instructions ! 'L' Unsigned constant valid for BccUI instructions  File: gccint.info, Node: Disable Insn Alternatives, Next: Define Constraints, Prev: Machine Constraints, Up: Constraints ! 16.8.6 Disable insn alternatives using the 'enabled' attribute -------------------------------------------------------------- There are three insn attributes that may be used to selectively disable instruction alternatives: ! 'enabled' Says whether an alternative is available on the current subtarget. ! 'preferred_for_size' Says whether an enabled alternative should be used in code that is optimized for size. ! 'preferred_for_speed' Says whether an enabled alternative should be used in code that is optimized for speed. ! All these attributes should use '(const_int 1)' to allow an alternative ! or '(const_int 0)' to disallow it. The attributes must be a static ! property of the subtarget; they cannot for example depend on the current ! operands, on the current optimization level, on the location of the insn ! within the body of a loop, on whether register allocation has finished, ! or on the current compiler pass. ! The 'enabled' attribute is a correctness property. It tells GCC to act as though the disabled alternatives were never defined in the first place. This is useful when adding new instructions to an existing pattern in cases where the new instructions are only available for ! certain cpu architecture levels (typically mapped to the '-march=' command-line option). ! In contrast, the 'preferred_for_size' and 'preferred_for_speed' attributes are strong optimization hints rather than correctness ! properties. 'preferred_for_size' tells GCC which alternatives to consider when adding or modifying an instruction that GCC wants to ! optimize for size. 'preferred_for_speed' does the same thing for speed. ! Note that things like code motion can lead to cases where code optimized ! for size uses alternatives that are not preferred for size, and ! similarly for speed. ! Although 'define_insn's can in principle specify the 'enabled' attribute directly, it is often clearer to have subsiduary attributes ! for each architectural feature of interest. The 'define_insn's can then ! use these subsiduary attributes to say which alternatives require which ! features. The example below does this for 'cpu_facility'. ! E.g. the following two patterns could easily be merged using the ! 'enabled' attribute: (define_insn "*movdi_old" --- 22559,22776 ---- return ((unsigned long long)tickh << 32)|tickl; } ! `f' Any 80387 floating-point (stack) register. ! `t' ! Top of 80387 floating-point stack (`%st(0)'). ! `u' ! Second from top of 80387 floating-point stack (`%st(1)'). ! `y' Any MMX register. ! `x' Any SSE register. ! `Yz' ! First SSE register (`%xmm0'). ! `Y2' Any SSE register, when SSE2 is enabled. ! `Yi' Any SSE register, when SSE2 and inter-unit moves are enabled. ! `Ym' Any MMX register, when inter-unit moves are enabled. ! `I' Integer constant in the range 0 ... 31, for 32-bit shifts. ! `J' Integer constant in the range 0 ... 63, for 64-bit shifts. ! `K' Signed 8-bit integer constant. ! `L' ! `0xFF' or `0xFFFF', for andsi as a zero-extending move. ! `M' ! 0, 1, 2, or 3 (shifts for the `lea' instruction). ! `N' ! Unsigned 8-bit integer constant (for `in' and `out' instructions). ! `O' Integer constant in the range 0 ... 127, for 128-bit shifts. ! `G' Standard 80387 floating point constant. ! `C' SSE constant zero operand. ! `e' 32-bit signed integer constant, or a symbolic reference known to fit that range (for immediate operands in sign-extending x86-64 instructions). ! `Z' 32-bit unsigned integer constant, or a symbolic reference known to fit that range (for immediate operands in zero-extending x86-64 instructions). ! ! _Xstormy16--`config/stormy16/stormy16.h'_ ! ! `a' Register r0. ! `b' Register r1. ! `c' Register r2. ! `d' Register r8. ! `e' Registers r0 through r7. ! `t' Registers r0 and r1. ! `y' The carry register. ! `z' Registers r8 and r9. ! `I' A constant between 0 and 3 inclusive. ! `J' A constant that has exactly one bit set. ! `K' A constant that has exactly one bit clear. ! `L' A constant between 0 and 255 inclusive. ! `M' A constant between -255 and 0 inclusive. ! `N' A constant between -3 and 0 inclusive. ! `O' A constant between 1 and 4 inclusive. ! `P' A constant between -4 and -1 inclusive. ! `Q' A memory reference that is a stack push. ! `R' A memory reference that is a stack pop. ! `S' A memory reference that refers to a constant address of known value. ! `T' The register indicated by Rx (not implemented yet). ! `U' A constant that is not between 2 and 15 inclusive. ! `Z' The constant 0. ! ! _Xtensa--`config/xtensa/constraints.md'_ ! ! `a' General-purpose 32-bit register ! `b' One-bit boolean register ! `A' MAC16 40-bit accumulator register ! `I' Signed 12-bit integer constant, for use in MOVI instructions ! `J' Signed 8-bit integer constant, for use in ADDI instructions ! `K' Integer constant valid for BccI instructions ! `L' Unsigned constant valid for BccUI instructions + +  File: gccint.info, Node: Disable Insn Alternatives, Next: Define Constraints, Prev: Machine Constraints, Up: Constraints ! 16.8.6 Disable insn alternatives using the `enabled' attribute -------------------------------------------------------------- There are three insn attributes that may be used to selectively disable instruction alternatives: ! `enabled' Says whether an alternative is available on the current subtarget. ! `preferred_for_size' Says whether an enabled alternative should be used in code that is optimized for size. ! `preferred_for_speed' Says whether an enabled alternative should be used in code that is optimized for speed. ! All these attributes should use `(const_int 1)' to allow an alternative ! or `(const_int 0)' to disallow it. The attributes must be a static ! property of the subtarget; they cannot for example depend on the ! current operands, on the current optimization level, on the location of ! the insn within the body of a loop, on whether register allocation has ! finished, or on the current compiler pass. ! The `enabled' attribute is a correctness property. It tells GCC to act as though the disabled alternatives were never defined in the first place. This is useful when adding new instructions to an existing pattern in cases where the new instructions are only available for ! certain cpu architecture levels (typically mapped to the `-march=' command-line option). ! In contrast, the `preferred_for_size' and `preferred_for_speed' attributes are strong optimization hints rather than correctness ! properties. `preferred_for_size' tells GCC which alternatives to consider when adding or modifying an instruction that GCC wants to ! optimize for size. `preferred_for_speed' does the same thing for ! speed. Note that things like code motion can lead to cases where code ! optimized for size uses alternatives that are not preferred for size, ! and similarly for speed. ! Although `define_insn's can in principle specify the `enabled' attribute directly, it is often clearer to have subsiduary attributes ! for each architectural feature of interest. The `define_insn's can ! then use these subsiduary attributes to say which alternatives require ! which features. The example below does this for `cpu_facility'. ! E.g. the following two patterns could easily be merged using the ! `enabled' attribute: (define_insn "*movdi_old" *************** features. The example below does this f *** 22419,22425 **** ldgr %0,%1 lgdr %0,%1") - to: --- 22788,22793 ---- *************** features. The example below does this f *** 22433,22440 **** lgdr %0,%1" [(set_attr "cpu_facility" "*,new,new")]) ! ! with the 'enabled' attribute defined like this: (define_attr "cpu_facility" "standard,new" (const_string "standard")) --- 22801,22807 ---- lgdr %0,%1" [(set_attr "cpu_facility" "*,new,new")]) ! with the `enabled' attribute defined like this: (define_attr "cpu_facility" "standard,new" (const_string "standard")) *************** features. The example below does this f *** 22446,22452 **** (const_int 1)] (const_int 0))) -  File: gccint.info, Node: Define Constraints, Next: C Constraint Interface, Prev: Disable Insn Alternatives, Up: Constraints --- 22813,22818 ---- *************** File: gccint.info, Node: Define Constra *** 22454,22473 **** -------------------------------------------- Machine-specific constraints fall into two categories: register and ! non-register constraints. Within the latter category, constraints which ! allow subsets of all possible memory or address operands should be ! specially marked, to give 'reload' more information. Machine-specific constraints can be given names of arbitrary length, but they must be entirely composed of letters, digits, underscores ! ('_'), and angle brackets ('< >'). Like C identifiers, they must begin with a letter or underscore. In order to avoid ambiguity in operand constraint strings, no ! constraint can have a name that begins with any other constraint's name. ! For example, if 'x' is defined as a constraint name, 'xy' may not be, ! and vice versa. As a consequence of this rule, no constraint may begin ! with one of the generic constraint letters: 'E F V X g i m n o p r s'. Register constraints correspond directly to register classes. *Note Register Classes::. There is thus not much flexibility in their --- 22820,22840 ---- -------------------------------------------- Machine-specific constraints fall into two categories: register and ! non-register constraints. Within the latter category, constraints ! which allow subsets of all possible memory or address operands should ! be specially marked, to give `reload' more information. Machine-specific constraints can be given names of arbitrary length, but they must be entirely composed of letters, digits, underscores ! (`_'), and angle brackets (`< >'). Like C identifiers, they must begin with a letter or underscore. In order to avoid ambiguity in operand constraint strings, no ! constraint can have a name that begins with any other constraint's ! name. For example, if `x' is defined as a constraint name, `xy' may ! not be, and vice versa. As a consequence of this rule, no constraint ! may begin with one of the generic constraint letters: `E F V X g i m n ! o p r s'. Register constraints correspond directly to register classes. *Note Register Classes::. There is thus not much flexibility in their *************** definitions. *** 22475,22489 **** -- MD Expression: define_register_constraint name regclass docstring All three arguments are string constants. NAME is the name of the ! constraint, as it will appear in 'match_operand' expressions. If NAME is a multi-letter constraint its length shall be the same for all constraints starting with the same letter. REGCLASS can be ! either the name of the corresponding register class (*note Register ! Classes::), or a C expression which evaluates to the appropriate ! register class. If it is an expression, it must have no side ! effects, and it cannot look at the operand. The usual use of ! expressions is to map some register constraints to 'NO_REGS' when ! the register class is not available on a given subarchitecture. DOCSTRING is a sentence documenting the meaning of the constraint. Docstrings are explained further below. --- 22842,22857 ---- -- MD Expression: define_register_constraint name regclass docstring All three arguments are string constants. NAME is the name of the ! constraint, as it will appear in `match_operand' expressions. If NAME is a multi-letter constraint its length shall be the same for all constraints starting with the same letter. REGCLASS can be ! either the name of the corresponding register class (*note ! Register Classes::), or a C expression which evaluates to the ! appropriate register class. If it is an expression, it must have ! no side effects, and it cannot look at the operand. The usual use ! of expressions is to map some register constraints to `NO_REGS' ! when the register class is not available on a given ! subarchitecture. DOCSTRING is a sentence documenting the meaning of the constraint. Docstrings are explained further below. *************** constraint matches. *** 22494,22607 **** -- MD Expression: define_constraint name docstring exp The NAME and DOCSTRING arguments are the same as for ! 'define_register_constraint', but note that the docstring comes immediately after the name for these expressions. EXP is an RTL expression, obeying the same rules as the RTL expressions in predicate definitions. *Note Defining Predicates::, for details. If it evaluates true, the constraint matches; if it evaluates ! false, it doesn't. Constraint expressions should indicate which RTL codes they might match, just like predicate expressions. ! 'match_test' C expressions have access to the following variables: ! OP The RTL object defining the operand. ! MODE The machine mode of OP. ! IVAL ! 'INTVAL (OP)', if OP is a 'const_int'. ! HVAL ! 'CONST_DOUBLE_HIGH (OP)', if OP is an integer 'const_double'. ! LVAL ! 'CONST_DOUBLE_LOW (OP)', if OP is an integer 'const_double'. ! RVAL ! 'CONST_DOUBLE_REAL_VALUE (OP)', if OP is a floating-point ! 'const_double'. The *VAL variables should only be used once another piece of the expression has verified that OP is the appropriate kind of RTL object. Most non-register constraints should be defined with ! 'define_constraint'. The remaining two definition expressions are only ! appropriate for constraints that should be handled specially by 'reload' ! if they fail to match. -- MD Expression: define_memory_constraint name docstring exp Use this expression for constraints that match a subset of all ! memory operands: that is, 'reload' can make them match by ! converting the operand to the form '(mem (reg X))', where X is a base register (from the register class specified by ! 'BASE_REG_CLASS', *note Register Classes::). For example, on the S/390, some instructions do not accept ! arbitrary memory references, but only those that do not make use of ! an index register. The constraint letter 'Q' is defined to ! represent a memory address of this type. If 'Q' is defined with ! 'define_memory_constraint', a 'Q' constraint can handle any memory ! operand, because 'reload' knows it can simply copy the memory ! address into a base register if required. This is analogous to the ! way an 'o' constraint can handle any memory operand. The syntax and semantics are otherwise identical to ! 'define_constraint'. -- MD Expression: define_special_memory_constraint name docstring exp Use this expression for constraints that match a subset of all ! memory operands: that is, 'reload' can not make them match by reloading the address as it is described for ! 'define_memory_constraint' or such address reload is undesirable with the performance point of view. ! For example, 'define_special_memory_constraint' can be useful if specifically aligned memory is necessary or desirable for some insn operand. The syntax and semantics are otherwise identical to ! 'define_constraint'. -- MD Expression: define_address_constraint name docstring exp Use this expression for constraints that match a subset of all ! address operands: that is, 'reload' can make the constraint match ! by converting the operand to the form '(reg X)', again with X a base register. ! Constraints defined with 'define_address_constraint' can only be ! used with the 'address_operand' predicate, or machine-specific predicates that work the same way. They are treated analogously to ! the generic 'p' constraint. The syntax and semantics are otherwise identical to ! 'define_constraint'. ! For historical reasons, names beginning with the letters 'G H' are ! reserved for constraints that match only 'const_double's, and names ! beginning with the letters 'I J K L M N O P' are reserved for ! constraints that match only 'const_int's. This may change in the future. For the time being, constraints with these names must be ! written in a stylized form, so that 'genpreds' can tell you did it correctly: (define_constraint "[GHIJKLMNOP]..." "DOC..." ! (and (match_code "const_int") ; 'const_double' for G/H ! CONDITION...)) ; usually a 'match_test' It is fine to use names beginning with other letters for constraints ! that match 'const_double's or 'const_int's. Each docstring in a constraint definition should be one or more complete sentences, marked up in Texinfo format. _They are currently ! unused._ In the future they will be copied into the GCC manual, in *note Machine Constraints::, replacing the hand-maintained tables currently found in that section. Also, in the future the compiler may ! use this to give more helpful diagnostics when poor choice of 'asm' constraints causes a reload failure. ! If you put the pseudo-Texinfo directive '@internal' at the beginning of ! a docstring, then (in the future) it will appear only in the internals ! manual's version of the machine-specific constraint tables. Use this ! for constraints that should not appear in 'asm' statements.  File: gccint.info, Node: C Constraint Interface, Prev: Define Constraints, Up: Constraints --- 22862,22980 ---- -- MD Expression: define_constraint name docstring exp The NAME and DOCSTRING arguments are the same as for ! `define_register_constraint', but note that the docstring comes immediately after the name for these expressions. EXP is an RTL expression, obeying the same rules as the RTL expressions in predicate definitions. *Note Defining Predicates::, for details. If it evaluates true, the constraint matches; if it evaluates ! false, it doesn't. Constraint expressions should indicate which RTL codes they might match, just like predicate expressions. ! `match_test' C expressions have access to the following variables: ! OP The RTL object defining the operand. ! ! MODE The machine mode of OP. ! ! IVAL ! `INTVAL (OP)', if OP is a `const_int'. ! ! HVAL ! `CONST_DOUBLE_HIGH (OP)', if OP is an integer `const_double'. ! ! LVAL ! `CONST_DOUBLE_LOW (OP)', if OP is an integer `const_double'. ! ! RVAL ! `CONST_DOUBLE_REAL_VALUE (OP)', if OP is a floating-point ! `const_double'. The *VAL variables should only be used once another piece of the expression has verified that OP is the appropriate kind of RTL object. Most non-register constraints should be defined with ! `define_constraint'. The remaining two definition expressions are only ! appropriate for constraints that should be handled specially by ! `reload' if they fail to match. -- MD Expression: define_memory_constraint name docstring exp Use this expression for constraints that match a subset of all ! memory operands: that is, `reload' can make them match by ! converting the operand to the form `(mem (reg X))', where X is a base register (from the register class specified by ! `BASE_REG_CLASS', *note Register Classes::). For example, on the S/390, some instructions do not accept ! arbitrary memory references, but only those that do not make use ! of an index register. The constraint letter `Q' is defined to ! represent a memory address of this type. If `Q' is defined with ! `define_memory_constraint', a `Q' constraint can handle any memory ! operand, because `reload' knows it can simply copy the memory ! address into a base register if required. This is analogous to ! the way an `o' constraint can handle any memory operand. The syntax and semantics are otherwise identical to ! `define_constraint'. -- MD Expression: define_special_memory_constraint name docstring exp Use this expression for constraints that match a subset of all ! memory operands: that is, `reload' can not make them match by reloading the address as it is described for ! `define_memory_constraint' or such address reload is undesirable with the performance point of view. ! For example, `define_special_memory_constraint' can be useful if specifically aligned memory is necessary or desirable for some insn operand. The syntax and semantics are otherwise identical to ! `define_constraint'. -- MD Expression: define_address_constraint name docstring exp Use this expression for constraints that match a subset of all ! address operands: that is, `reload' can make the constraint match ! by converting the operand to the form `(reg X)', again with X a base register. ! Constraints defined with `define_address_constraint' can only be ! used with the `address_operand' predicate, or machine-specific predicates that work the same way. They are treated analogously to ! the generic `p' constraint. The syntax and semantics are otherwise identical to ! `define_constraint'. ! For historical reasons, names beginning with the letters `G H' are ! reserved for constraints that match only `const_double's, and names ! beginning with the letters `I J K L M N O P' are reserved for ! constraints that match only `const_int's. This may change in the future. For the time being, constraints with these names must be ! written in a stylized form, so that `genpreds' can tell you did it correctly: (define_constraint "[GHIJKLMNOP]..." "DOC..." ! (and (match_code "const_int") ; `const_double' for G/H ! CONDITION...)) ; usually a `match_test' It is fine to use names beginning with other letters for constraints ! that match `const_double's or `const_int's. Each docstring in a constraint definition should be one or more complete sentences, marked up in Texinfo format. _They are currently ! unused._ In the future they will be copied into the GCC manual, in *note Machine Constraints::, replacing the hand-maintained tables currently found in that section. Also, in the future the compiler may ! use this to give more helpful diagnostics when poor choice of `asm' constraints causes a reload failure. ! If you put the pseudo-Texinfo directive `@internal' at the beginning ! of a docstring, then (in the future) it will appear only in the ! internals manual's version of the machine-specific constraint tables. ! Use this for constraints that should not appear in `asm' statements.  File: gccint.info, Node: C Constraint Interface, Prev: Define Constraints, Up: Constraints *************** File: gccint.info, Node: C Constraint I *** 22610,22668 **** --------------------------------- It is occasionally useful to test a constraint from C code rather than ! implicitly via the constraint string in a 'match_operand'. The ! generated file 'tm_p.h' declares a few interfaces for working with constraints. At present these are defined for all constraints except ! 'g' (which is equivalent to 'general_operand'). Some valid constraint names are not valid C identifiers, so there is a mangling scheme for referring to them from C. Constraint names that do not contain angle brackets or underscores are left unchanged. ! Underscores are doubled, each '<' is replaced with '_l', and each '>' ! with '_g'. Here are some examples: ! *Original* *Mangled* ! x x ! P42x P42x ! P4_x P4__x ! P4>x P4_gx ! P4>> P4_g_g ! P4_g> P4__g_g Throughout this section, the variable C is either a constraint in the ! abstract sense, or a constant from 'enum constraint_num'; the variable M ! is a mangled constraint name (usually as part of a larger identifier). -- Enum: constraint_num ! For each constraint except 'g', there is a corresponding ! enumeration constant: 'CONSTRAINT_' plus the mangled name of the ! constraint. Functions that take an 'enum constraint_num' as an argument expect one of these constants. -- Function: inline bool satisfies_constraint_M (rtx EXP) ! For each non-register constraint M except 'g', there is one of ! these functions; it returns 'true' if EXP satisfies the constraint. ! These functions are only visible if 'rtl.h' was included before ! 'tm_p.h'. -- Function: bool constraint_satisfied_p (rtx EXP, enum constraint_num C) ! Like the 'satisfies_constraint_M' functions, but the constraint to test is given as an argument, C. If C specifies a register ! constraint, this function will always return 'false'. -- Function: enum reg_class reg_class_for_constraint (enum constraint_num C) Returns the register class associated with C. If C is not a register constraint, or those registers are not available for the ! currently selected subtarget, returns 'NO_REGS'. ! Here is an example use of 'satisfies_constraint_M'. In peephole ! optimizations (*note Peephole Definitions::), operand constraint strings ! are ignored, so if there are relevant constraints, they must be tested ! in the C condition. In the example, the optimization is applied if ! operand 2 does _not_ satisfy the 'K' constraint. (This is a simplified ! version of a peephole definition from the i386 machine description.) (define_peephole2 [(match_scratch:SI 3 "r") --- 22983,23042 ---- --------------------------------- It is occasionally useful to test a constraint from C code rather than ! implicitly via the constraint string in a `match_operand'. The ! generated file `tm_p.h' declares a few interfaces for working with constraints. At present these are defined for all constraints except ! `g' (which is equivalent to `general_operand'). Some valid constraint names are not valid C identifiers, so there is a mangling scheme for referring to them from C. Constraint names that do not contain angle brackets or underscores are left unchanged. ! Underscores are doubled, each `<' is replaced with `_l', and each `>' ! with `_g'. Here are some examples: ! *Original* *Mangled* ! `x' `x' ! `P42x' `P42x' ! `P4_x' `P4__x' ! `P4>x' `P4_gx' ! `P4>>' `P4_g_g' ! `P4_g>' `P4__g_g' Throughout this section, the variable C is either a constraint in the ! abstract sense, or a constant from `enum constraint_num'; the variable ! M is a mangled constraint name (usually as part of a larger identifier). -- Enum: constraint_num ! For each constraint except `g', there is a corresponding ! enumeration constant: `CONSTRAINT_' plus the mangled name of the ! constraint. Functions that take an `enum constraint_num' as an argument expect one of these constants. -- Function: inline bool satisfies_constraint_M (rtx EXP) ! For each non-register constraint M except `g', there is one of ! these functions; it returns `true' if EXP satisfies the ! constraint. These functions are only visible if `rtl.h' was ! included before `tm_p.h'. -- Function: bool constraint_satisfied_p (rtx EXP, enum constraint_num C) ! Like the `satisfies_constraint_M' functions, but the constraint to test is given as an argument, C. If C specifies a register ! constraint, this function will always return `false'. -- Function: enum reg_class reg_class_for_constraint (enum constraint_num C) Returns the register class associated with C. If C is not a register constraint, or those registers are not available for the ! currently selected subtarget, returns `NO_REGS'. ! Here is an example use of `satisfies_constraint_M'. In peephole ! optimizations (*note Peephole Definitions::), operand constraint ! strings are ignored, so if there are relevant constraints, they must be ! tested in the C condition. In the example, the optimization is applied ! if operand 2 does _not_ satisfy the `K' constraint. (This is a ! simplified version of a peephole definition from the i386 machine ! description.) (define_peephole2 [(match_scratch:SI 3 "r") *************** generation pass of the compiler. Giving *** 22688,22723 **** instruction pattern tells the RTL generation pass that it can use the pattern to accomplish a certain task. ! 'movM' Here M stands for a two-letter machine mode name, in lowercase. This instruction pattern moves data with that machine mode from ! operand 1 to operand 0. For example, 'movsi' moves full-word data. ! If operand 0 is a 'subreg' with mode M of a register whose own mode ! is wider than M, the effect of this instruction is to store the ! specified value in the part of the register that corresponds to ! mode M. Bits outside of M, but which are within the same target ! word as the 'subreg' are undefined. Bits which are outside the ! target word are left unchanged. This class of patterns is special in several ways. First of all, each of these names up to and including full word size _must_ be defined, because there is no other way to copy a datum from one place to another. If there are patterns accepting operands in ! larger modes, 'movM' must be defined for integer modes of those sizes. Second, these patterns are not used solely in the RTL generation pass. Even the reload pass can generate move insns to copy values ! from stack slots into temporary registers. When it does so, one of ! the operands is a hard register and the other is an operand that ! can need to be reloaded into a register. Therefore, when given such a pair of operands, the pattern must generate RTL which needs no reloading and needs no temporary registers--no registers other than the operands. For example, if ! you support the pattern with a 'define_expand', then in such a case ! the 'define_expand' mustn't call 'force_reg' or any other such function which might generate new pseudo registers. This requirement exists even for subword modes on a RISC machine --- 23062,23097 ---- instruction pattern tells the RTL generation pass that it can use the pattern to accomplish a certain task. ! `movM' Here M stands for a two-letter machine mode name, in lowercase. This instruction pattern moves data with that machine mode from ! operand 1 to operand 0. For example, `movsi' moves full-word data. ! If operand 0 is a `subreg' with mode M of a register whose own ! mode is wider than M, the effect of this instruction is to store ! the specified value in the part of the register that corresponds ! to mode M. Bits outside of M, but which are within the same ! target word as the `subreg' are undefined. Bits which are outside ! the target word are left unchanged. This class of patterns is special in several ways. First of all, each of these names up to and including full word size _must_ be defined, because there is no other way to copy a datum from one place to another. If there are patterns accepting operands in ! larger modes, `movM' must be defined for integer modes of those sizes. Second, these patterns are not used solely in the RTL generation pass. Even the reload pass can generate move insns to copy values ! from stack slots into temporary registers. When it does so, one ! of the operands is a hard register and the other is an operand ! that can need to be reloaded into a register. Therefore, when given such a pair of operands, the pattern must generate RTL which needs no reloading and needs no temporary registers--no registers other than the operands. For example, if ! you support the pattern with a `define_expand', then in such a ! case the `define_expand' mustn't call `force_reg' or any other such function which might generate new pseudo registers. This requirement exists even for subword modes on a RISC machine *************** pattern to accomplish a certain task. *** 22730,22740 **** be done with the address except to use it as it stands. If it is copied, it will not be replaced with a valid address. No attempt should be made to make such an address into a valid address and no ! routine (such as 'change_address') that will do so may be called. ! Note that 'general_operand' will fail when applied to such an address. ! The global variable 'reload_in_progress' (which must be explicitly declared if required) can be used to determine whether such special handling is required. --- 23104,23114 ---- be done with the address except to use it as it stands. If it is copied, it will not be replaced with a valid address. No attempt should be made to make such an address into a valid address and no ! routine (such as `change_address') that will do so may be called. ! Note that `general_operand' will fail when applied to such an address. ! The global variable `reload_in_progress' (which must be explicitly declared if required) can be used to determine whether such special handling is required. *************** pattern to accomplish a certain task. *** 22745,22819 **** reloads. If a scratch register is required to move an object to or from ! memory, it can be allocated using 'gen_reg_rtx' prior to life analysis. If there are cases which need scratch registers during or after reload, you must provide an appropriate secondary_reload target hook. ! The macro 'can_create_pseudo_p' can be used to determine if it is unsafe to create new pseudo registers. If this variable is ! nonzero, then it is unsafe to call 'gen_reg_rtx' to allocate a new pseudo. ! The constraints on a 'movM' must permit moving any hard register to ! any other hard register provided that 'HARD_REGNO_MODE_OK' permits ! mode M in both registers and 'TARGET_REGISTER_MOVE_COST' applied to ! their classes returns a value of 2. ! It is obligatory to support floating point 'movM' instructions into ! and out of any registers that can hold fixed point values, because ! unions and structures (which have modes 'SImode' or 'DImode') can ! be in those registers and they may have floating point members. ! There may also be a need to support fixed point 'movM' instructions ! in and out of floating point registers. Unfortunately, I have ! forgotten why this was so, and I don't know whether it is still ! true. If 'HARD_REGNO_MODE_OK' rejects fixed point values in ! floating point registers, then the constraints of the fixed point ! 'movM' instructions must be designed to avoid ever trying to reload ! into a floating point register. ! 'reload_inM' ! 'reload_outM' These named patterns have been obsoleted by the target hook ! 'secondary_reload'. ! Like 'movM', but used when a scratch register is required to move between operand 0 and operand 1. Operand 2 describes the scratch ! register. See the discussion of the 'SECONDARY_RELOAD_CLASS' macro ! in *note Register Classes::. ! There are special restrictions on the form of the 'match_operand's used in these patterns. First, only the predicate for the reload ! operand is examined, i.e., 'reload_in' examines operand 1, but not the predicates for operand 0 or 2. Second, there may be only one alternative in the constraints. Third, only a single register class letter may be used for the constraint; subsequent constraint letters are ignored. As a special exception, an empty constraint ! string matches the 'ALL_REGS' register class. This may relieve ! ports of the burden of defining an 'ALL_REGS' constraint letter just for these patterns. ! 'movstrictM' ! Like 'movM' except that if operand 0 is a 'subreg' with mode M of a ! register whose natural mode is wider, the 'movstrictM' instruction ! is guaranteed not to alter any of the register except the part ! which belongs to mode M. ! 'movmisalignM' This variant of a move pattern is designed to load or store a value from a memory address that is not naturally aligned for its mode. For a store, the memory will be in operand 0; for a load, the memory will be in operand 1. The other operand is guaranteed not ! to be a memory, so that it's easy to tell whether this is a load or ! store. This pattern is used by the autovectorizer, and when expanding a ! 'MISALIGNED_INDIRECT_REF' expression. ! 'load_multiple' Load several consecutive memory locations into consecutive registers. Operand 0 is the first of the consecutive registers, operand 1 is the first memory location, and operand 2 is a --- 23119,23194 ---- reloads. If a scratch register is required to move an object to or from ! memory, it can be allocated using `gen_reg_rtx' prior to life analysis. If there are cases which need scratch registers during or after reload, you must provide an appropriate secondary_reload target hook. ! The macro `can_create_pseudo_p' can be used to determine if it is unsafe to create new pseudo registers. If this variable is ! nonzero, then it is unsafe to call `gen_reg_rtx' to allocate a new pseudo. ! The constraints on a `movM' must permit moving any hard register ! to any other hard register provided that `HARD_REGNO_MODE_OK' ! permits mode M in both registers and `TARGET_REGISTER_MOVE_COST' ! applied to their classes returns a value of 2. ! It is obligatory to support floating point `movM' instructions ! into and out of any registers that can hold fixed point values, ! because unions and structures (which have modes `SImode' or ! `DImode') can be in those registers and they may have floating ! point members. ! There may also be a need to support fixed point `movM' ! instructions in and out of floating point registers. ! Unfortunately, I have forgotten why this was so, and I don't know ! whether it is still true. If `HARD_REGNO_MODE_OK' rejects fixed ! point values in floating point registers, then the constraints of ! the fixed point `movM' instructions must be designed to avoid ever ! trying to reload into a floating point register. ! `reload_inM' ! `reload_outM' These named patterns have been obsoleted by the target hook ! `secondary_reload'. ! Like `movM', but used when a scratch register is required to move between operand 0 and operand 1. Operand 2 describes the scratch ! register. See the discussion of the `SECONDARY_RELOAD_CLASS' ! macro in *note Register Classes::. ! There are special restrictions on the form of the `match_operand's used in these patterns. First, only the predicate for the reload ! operand is examined, i.e., `reload_in' examines operand 1, but not the predicates for operand 0 or 2. Second, there may be only one alternative in the constraints. Third, only a single register class letter may be used for the constraint; subsequent constraint letters are ignored. As a special exception, an empty constraint ! string matches the `ALL_REGS' register class. This may relieve ! ports of the burden of defining an `ALL_REGS' constraint letter just for these patterns. ! `movstrictM' ! Like `movM' except that if operand 0 is a `subreg' with mode M of ! a register whose natural mode is wider, the `movstrictM' ! instruction is guaranteed not to alter any of the register except ! the part which belongs to mode M. ! `movmisalignM' This variant of a move pattern is designed to load or store a value from a memory address that is not naturally aligned for its mode. For a store, the memory will be in operand 0; for a load, the memory will be in operand 1. The other operand is guaranteed not ! to be a memory, so that it's easy to tell whether this is a load ! or store. This pattern is used by the autovectorizer, and when expanding a ! `MISALIGNED_INDIRECT_REF' expression. ! `load_multiple' Load several consecutive memory locations into consecutive registers. Operand 0 is the first of the consecutive registers, operand 1 is the first memory location, and operand 2 is a *************** pattern to accomplish a certain task. *** 22827,22848 **** On some machines, there are restrictions as to which consecutive registers can be stored into memory, such as particular starting or ending register numbers or only a range of valid counts. For those ! machines, use a 'define_expand' (*note Expander Definitions::) and make the pattern fail if the restrictions are not met. ! Write the generated insn as a 'parallel' with elements being a ! 'set' of one register from the appropriate memory location (you may ! also need 'use' or 'clobber' elements). Use a 'match_parallel' ! (*note RTL Template::) to recognize the insn. See 'rs6000.md' for examples of the use of this insn pattern. ! 'store_multiple' ! Similar to 'load_multiple', but store several consecutive registers into consecutive memory locations. Operand 0 is the first of the consecutive memory locations, operand 1 is the first register, and operand 2 is a constant: the number of consecutive registers. ! 'vec_load_lanesMN' Perform an interleaved load of several vectors from memory operand 1 into register operand 0. Both operands have mode M. The register operand is viewed as holding consecutive vectors of mode --- 23202,23223 ---- On some machines, there are restrictions as to which consecutive registers can be stored into memory, such as particular starting or ending register numbers or only a range of valid counts. For those ! machines, use a `define_expand' (*note Expander Definitions::) and make the pattern fail if the restrictions are not met. ! Write the generated insn as a `parallel' with elements being a ! `set' of one register from the appropriate memory location (you may ! also need `use' or `clobber' elements). Use a `match_parallel' ! (*note RTL Template::) to recognize the insn. See `rs6000.md' for examples of the use of this insn pattern. ! `store_multiple' ! Similar to `load_multiple', but store several consecutive registers into consecutive memory locations. Operand 0 is the first of the consecutive memory locations, operand 1 is the first register, and operand 2 is a constant: the number of consecutive registers. ! `vec_load_lanesMN' Perform an interleaved load of several vectors from memory operand 1 into register operand 0. Both operands have mode M. The register operand is viewed as holding consecutive vectors of mode *************** pattern to accomplish a certain task. *** 22854,22862 **** for (i = 0; i < c; i++) operand0[i][j] = operand1[j * c + i]; ! For example, 'vec_load_lanestiv4hi' loads 8 16-bit values from ! memory into a register of mode 'TI'. The register contains two ! consecutive vectors of mode 'V4HI'. This pattern can only be used if: TARGET_ARRAY_MODE_SUPPORTED_P (N, C) --- 23229,23237 ---- for (i = 0; i < c; i++) operand0[i][j] = operand1[j * c + i]; ! For example, `vec_load_lanestiv4hi' loads 8 16-bit values from ! memory into a register of mode `TI'. The register contains two ! consecutive vectors of mode `V4HI'. This pattern can only be used if: TARGET_ARRAY_MODE_SUPPORTED_P (N, C) *************** pattern to accomplish a certain task. *** 22864,22873 **** instruction for some mode N, it also supports unaligned loads for vectors of mode N. ! This pattern is not allowed to 'FAIL'. ! 'vec_store_lanesMN' ! Equivalent to 'vec_load_lanesMN', with the memory and register operands reversed. That is, the instruction is equivalent to: int c = GET_MODE_SIZE (M) / GET_MODE_SIZE (N); --- 23239,23248 ---- instruction for some mode N, it also supports unaligned loads for vectors of mode N. ! This pattern is not allowed to `FAIL'. ! `vec_store_lanesMN' ! Equivalent to `vec_load_lanesMN', with the memory and register operands reversed. That is, the instruction is equivalent to: int c = GET_MODE_SIZE (M) / GET_MODE_SIZE (N); *************** pattern to accomplish a certain task. *** 22877,23156 **** for a memory operand 0 and register operand 1. ! This pattern is not allowed to 'FAIL'. ! 'vec_setM' Set given field in the vector value. Operand 0 is the vector to modify, operand 1 is new value of field and operand 2 specify the field index. ! 'vec_extractM' Extract given field from the vector value. Operand 1 is the vector, operand 2 specify field index and operand 0 place to store value into. ! 'vec_initM' Initialize the vector to given values. Operand 0 is the vector to initialize and operand 1 is parallel containing values for individual fields. ! 'vec_cmpMN' ! Output a vector comparison. Operand 0 of mode N is the destination ! for predicate in operand 1 which is a signed vector comparison with ! operands of mode M in operands 2 and 3. Predicate is computed by ! element-wise evaluation of the vector comparison with a truth value ! of all-ones and a false value of all-zeros. ! 'vec_cmpuMN' ! Similar to 'vec_cmpMN' but perform unsigned vector comparison. ! 'vcondMN' Output a conditional vector move. Operand 0 is the destination to ! receive a combination of operand 1 and operand 2, which are of mode ! M, dependent on the outcome of the predicate in operand 3 which is ! a signed vector comparison with operands of mode N in operands 4 ! and 5. The modes M and N should have the same size. Operand 0 ! will be set to the value OP1 & MSK | OP2 & ~MSK where MSK is ! computed by element-wise evaluation of the vector comparison with a ! truth value of all-ones and a false value of all-zeros. ! 'vconduMN' ! Similar to 'vcondMN' but performs unsigned vector comparison. ! 'vcond_mask_MN' ! Similar to 'vcondMN' but operand 3 holds a pre-computed result of vector comparison. ! 'maskloadMN' Perform a masked load of vector from memory operand 1 of mode M into register operand 0. Mask is provided in register operand 2 of mode N. ! This pattern is not allowed to 'FAIL'. ! 'maskstoreMN' Perform a masked store of vector from register operand 1 of mode M into memory operand 0. Mask is provided in register operand 2 of mode N. ! This pattern is not allowed to 'FAIL'. ! 'vec_permM' Output a (variable) vector permutation. Operand 0 is the ! destination to receive elements from operand 1 and operand 2, which ! are of mode M. Operand 3 is the "selector". It is an integral ! mode vector of the same width and number of elements as mode M. The input elements are numbered from 0 in operand 1 through 2*N-1 ! in operand 2. The elements of the selector must be computed modulo ! 2*N. Note that if 'rtx_equal_p(operand1, operand2)', this can be ! implemented with just operand 1 and selector elements modulo N. In order to make things easy for a number of targets, if there is ! no 'vec_perm' pattern for mode M, but there is for mode Q where Q ! is a vector of 'QImode' of the same width as M, the middle-end will ! lower the mode M 'VEC_PERM_EXPR' to mode Q. ! 'vec_perm_constM' ! Like 'vec_perm' except that the permutation is a compile-time ! constant. That is, operand 3, the "selector", is a 'CONST_VECTOR'. Some targets cannot perform a permutation with a variable selector, but can efficiently perform a constant permutation. Further, the ! target hook 'vec_perm_ok' is queried to determine if the specific ! constant permutation is available efficiently; the named pattern is ! never expanded without 'vec_perm_ok' returning true. ! There is no need for a target to supply both 'vec_permM' and ! 'vec_perm_constM' if the former can trivially implement the operation with, say, the vector constant loaded into a register. ! 'pushM1' Output a push instruction. Operand 0 is value to push. Used only ! when 'PUSH_ROUNDING' is defined. For historical reason, this ! pattern may be missing and in such case an 'mov' expander is used ! instead, with a 'MEM' expression forming the push operation. The ! 'mov' expander method is deprecated. ! 'addM3' Add operand 2 and operand 1, storing the result in operand 0. All operands must have mode M. This can be used even on two-address machines, by means of constraints requiring operands 1 and 0 to be the same location. ! 'ssaddM3', 'usaddM3' ! 'subM3', 'sssubM3', 'ussubM3' ! 'mulM3', 'ssmulM3', 'usmulM3' ! 'divM3', 'ssdivM3' ! 'udivM3', 'usdivM3' ! 'modM3', 'umodM3' ! 'uminM3', 'umaxM3' ! 'andM3', 'iorM3', 'xorM3' Similar, for other arithmetic operations. ! 'addvM4' ! Like 'addM3' but takes a 'code_label' as operand 3 and emits code to jump to it if signed overflow occurs during the addition. This pattern is used to implement the built-in functions performing signed integer addition with overflow checking. ! 'subvM4', 'mulvM4' Similar, for other signed arithmetic operations. ! 'uaddvM4' ! Like 'addvM4' but for unsigned addition. That is to say, the ! operation is the same as signed addition but the jump is taken only ! on unsigned overflow. ! 'usubvM4', 'umulvM4' Similar, for other unsigned arithmetic operations. ! 'addptrM3' ! Like 'addM3' but is guaranteed to only be used for address calculations. The expanded code is not allowed to clobber the ! condition code. It only needs to be defined if 'addM3' sets the condition code. If adds used for address calculations and normal ! adds are not compatible it is required to expand a distinct pattern ! (e.g. using an unspec). The pattern is used by LRA to emit ! address calculations. 'addM3' is used if 'addptrM3' is not defined. ! 'fmaM4' Multiply operand 2 and operand 1, then add operand 3, storing the result in operand 0 without doing an intermediate rounding step. All operands must have mode M. This pattern is used to implement ! the 'fma', 'fmaf', and 'fmal' builtin functions from the ISO C99 standard. ! 'fmsM4' ! Like 'fmaM4', except operand 3 subtracted from the product instead of added to the product. This is represented in the rtl as (fma:M OP1 OP2 (neg:M OP3)) ! 'fnmaM4' ! Like 'fmaM4' except that the intermediate product is negated before ! being added to operand 3. This is represented in the rtl as (fma:M (neg:M OP1) OP2 OP3) ! 'fnmsM4' ! Like 'fmsM4' except that the intermediate product is negated before ! subtracting operand 3. This is represented in the rtl as (fma:M (neg:M OP1) OP2 (neg:M OP3)) ! 'sminM3', 'smaxM3' Signed minimum and maximum operations. When used with floating ! point, if both operands are zeros, or if either operand is 'NaN', ! then it is unspecified which of the two operands is returned as the ! result. ! 'fminM3', 'fmaxM3' IEEE-conformant minimum and maximum operations. If one operand is ! a quiet 'NaN', then the other operand is returned. If both ! operands are quiet 'NaN', then a quiet 'NaN' is returned. In the ! case when gcc supports signalling 'NaN' (-fsignaling-nans) an ! invalid floating point exception is raised and a quiet 'NaN' is returned. All operands have mode M, which is a scalar or vector ! floating-point mode. These patterns are not allowed to 'FAIL'. ! 'reduc_smin_scal_M', 'reduc_smax_scal_M' ! Find the signed minimum/maximum of the elements of a vector. The vector is operand 1, and operand 0 is the scalar result, with mode equal to the mode of the elements of the input vector. ! 'reduc_umin_scal_M', 'reduc_umax_scal_M' ! Find the unsigned minimum/maximum of the elements of a vector. The vector is operand 1, and operand 0 is the scalar result, with mode equal to the mode of the elements of the input vector. ! 'reduc_plus_scal_M' ! Compute the sum of the elements of a vector. The vector is operand 1, and operand 0 is the scalar result, with mode equal to the mode of the elements of the input vector. ! 'sdot_prodM' ! 'udot_prodM' Compute the sum of the products of two signed/unsigned elements. ! Operand 1 and operand 2 are of the same mode. Their product, which ! is of a wider mode, is computed and added to operand 3. Operand 3 ! is of a mode equal or wider than the mode of the product. The ! result is placed in operand 0, which is of the same mode as operand ! 3. ! 'ssadM' ! 'usadM' Compute the sum of absolute differences of two signed/unsigned ! elements. Operand 1 and operand 2 are of the same mode. Their absolute difference, which is of a wider mode, is computed and ! added to operand 3. Operand 3 is of a mode equal or wider than the ! mode of the absolute difference. The result is placed in operand 0, which is of the same mode as operand 3. ! 'widen_ssumM3' ! 'widen_usumM3' ! Operands 0 and 2 are of the same mode, which is wider than the mode ! of operand 1. Add operand 1 to operand 2 and place the widened ! result in operand 0. (This is used express accumulation of elements into an accumulator of a wider mode.) ! 'vec_shr_M' ! Whole vector right shift in bits, i.e. towards element 0. Operand 1 is a vector to be shifted. Operand 2 is an integer shift amount in bits. Operand 0 is where the resulting shifted vector is stored. The output and input vectors should have the same modes. ! 'vec_pack_trunc_M' ! Narrow (demote) and merge the elements of two vectors. Operands 1 and 2 are vectors of the same mode having N integral or floating point elements of size S. Operand 0 is the resulting vector in which 2*N elements of size N/2 are concatenated after narrowing them down using truncation. ! 'vec_pack_ssat_M', 'vec_pack_usat_M' Narrow (demote) and merge the elements of two vectors. Operands 1 and 2 are vectors of the same mode having N integral elements of ! size S. Operand 0 is the resulting vector in which the elements of ! the two input vectors are concatenated after narrowing them down ! using signed/unsigned saturating arithmetic. ! 'vec_pack_sfix_trunc_M', 'vec_pack_ufix_trunc_M' Narrow, convert to signed/unsigned integral type and merge the elements of two vectors. Operands 1 and 2 are vectors of the same mode having N floating point elements of size S. Operand 0 is the resulting vector in which 2*N elements of size N/2 are concatenated. ! 'vec_unpacks_hi_M', 'vec_unpacks_lo_M' Extract and widen (promote) the high/low part of a vector of signed integral or floating point elements. The input vector (operand 1) ! has N elements of size S. Widen (promote) the high/low elements of ! the vector using signed or floating point extension and place the ! resulting N/2 values of size 2*S in the output vector (operand 0). ! 'vec_unpacku_hi_M', 'vec_unpacku_lo_M' Extract and widen (promote) the high/low part of a vector of unsigned integral elements. The input vector (operand 1) has N ! elements of size S. Widen (promote) the high/low elements of the vector using zero extension and place the resulting N/2 values of size 2*S in the output vector (operand 0). ! 'vec_unpacks_float_hi_M', 'vec_unpacks_float_lo_M' ! 'vec_unpacku_float_hi_M', 'vec_unpacku_float_lo_M' ! Extract, convert to floating point type and widen the high/low part ! of a vector of signed/unsigned integral elements. The input vector ! (operand 1) has N elements of size S. Convert the high/low elements of the vector using floating point conversion and place the resulting N/2 values of size 2*S in the output vector (operand 0). ! 'vec_widen_umult_hi_M', 'vec_widen_umult_lo_M' ! 'vec_widen_smult_hi_M', 'vec_widen_smult_lo_M' ! 'vec_widen_umult_even_M', 'vec_widen_umult_odd_M' ! 'vec_widen_smult_even_M', 'vec_widen_smult_odd_M' Signed/Unsigned widening multiplication. The two inputs (operands 1 and 2) are vectors with N signed/unsigned elements of size S. Multiply the high/low or even/odd elements of the two vectors, and --- 23252,23536 ---- for a memory operand 0 and register operand 1. ! This pattern is not allowed to `FAIL'. ! `vec_setM' Set given field in the vector value. Operand 0 is the vector to modify, operand 1 is new value of field and operand 2 specify the field index. ! `vec_extractM' Extract given field from the vector value. Operand 1 is the vector, operand 2 specify field index and operand 0 place to store value into. ! `vec_initM' Initialize the vector to given values. Operand 0 is the vector to initialize and operand 1 is parallel containing values for individual fields. ! `vec_cmpMN' ! Output a vector comparison. Operand 0 of mode N is the ! destination for predicate in operand 1 which is a signed vector ! comparison with operands of mode M in operands 2 and 3. Predicate ! is computed by element-wise evaluation of the vector comparison ! with a truth value of all-ones and a false value of all-zeros. ! `vec_cmpuMN' ! Similar to `vec_cmpMN' but perform unsigned vector comparison. ! `vcondMN' Output a conditional vector move. Operand 0 is the destination to ! receive a combination of operand 1 and operand 2, which are of ! mode M, dependent on the outcome of the predicate in operand 3 ! which is a signed vector comparison with operands of mode N in ! operands 4 and 5. The modes M and N should have the same size. ! Operand 0 will be set to the value OP1 & MSK | OP2 & ~MSK where ! MSK is computed by element-wise evaluation of the vector ! comparison with a truth value of all-ones and a false value of ! all-zeros. ! `vconduMN' ! Similar to `vcondMN' but performs unsigned vector comparison. ! `vcond_mask_MN' ! Similar to `vcondMN' but operand 3 holds a pre-computed result of vector comparison. ! `maskloadMN' Perform a masked load of vector from memory operand 1 of mode M into register operand 0. Mask is provided in register operand 2 of mode N. ! This pattern is not allowed to `FAIL'. ! `maskstoreMN' Perform a masked store of vector from register operand 1 of mode M into memory operand 0. Mask is provided in register operand 2 of mode N. ! This pattern is not allowed to `FAIL'. ! `vec_permM' Output a (variable) vector permutation. Operand 0 is the ! destination to receive elements from operand 1 and operand 2, ! which are of mode M. Operand 3 is the "selector". It is an ! integral mode vector of the same width and number of elements as ! mode M. The input elements are numbered from 0 in operand 1 through 2*N-1 ! in operand 2. The elements of the selector must be computed ! modulo 2*N. Note that if `rtx_equal_p(operand1, operand2)', this ! can be implemented with just operand 1 and selector elements ! modulo N. In order to make things easy for a number of targets, if there is ! no `vec_perm' pattern for mode M, but there is for mode Q where Q ! is a vector of `QImode' of the same width as M, the middle-end ! will lower the mode M `VEC_PERM_EXPR' to mode Q. ! `vec_perm_constM' ! Like `vec_perm' except that the permutation is a compile-time ! constant. That is, operand 3, the "selector", is a `CONST_VECTOR'. Some targets cannot perform a permutation with a variable selector, but can efficiently perform a constant permutation. Further, the ! target hook `vec_perm_ok' is queried to determine if the specific ! constant permutation is available efficiently; the named pattern ! is never expanded without `vec_perm_ok' returning true. ! There is no need for a target to supply both `vec_permM' and ! `vec_perm_constM' if the former can trivially implement the operation with, say, the vector constant loaded into a register. ! `pushM1' Output a push instruction. Operand 0 is value to push. Used only ! when `PUSH_ROUNDING' is defined. For historical reason, this ! pattern may be missing and in such case an `mov' expander is used ! instead, with a `MEM' expression forming the push operation. The ! `mov' expander method is deprecated. ! `addM3' Add operand 2 and operand 1, storing the result in operand 0. All operands must have mode M. This can be used even on two-address machines, by means of constraints requiring operands 1 and 0 to be the same location. ! `ssaddM3', `usaddM3' ! `subM3', `sssubM3', `ussubM3' ! `mulM3', `ssmulM3', `usmulM3' ! `divM3', `ssdivM3' ! `udivM3', `usdivM3' ! `modM3', `umodM3' ! `uminM3', `umaxM3' ! `andM3', `iorM3', `xorM3' Similar, for other arithmetic operations. ! `addvM4' ! Like `addM3' but takes a `code_label' as operand 3 and emits code to jump to it if signed overflow occurs during the addition. This pattern is used to implement the built-in functions performing signed integer addition with overflow checking. ! `subvM4', `mulvM4' Similar, for other signed arithmetic operations. ! `uaddvM4' ! Like `addvM4' but for unsigned addition. That is to say, the ! operation is the same as signed addition but the jump is taken ! only on unsigned overflow. ! `usubvM4', `umulvM4' Similar, for other unsigned arithmetic operations. ! `addptrM3' ! Like `addM3' but is guaranteed to only be used for address calculations. The expanded code is not allowed to clobber the ! condition code. It only needs to be defined if `addM3' sets the condition code. If adds used for address calculations and normal ! adds are not compatible it is required to expand a distinct ! pattern (e.g. using an unspec). The pattern is used by LRA to emit ! address calculations. `addM3' is used if `addptrM3' is not defined. ! `fmaM4' Multiply operand 2 and operand 1, then add operand 3, storing the result in operand 0 without doing an intermediate rounding step. All operands must have mode M. This pattern is used to implement ! the `fma', `fmaf', and `fmal' builtin functions from the ISO C99 standard. ! `fmsM4' ! Like `fmaM4', except operand 3 subtracted from the product instead of added to the product. This is represented in the rtl as (fma:M OP1 OP2 (neg:M OP3)) ! `fnmaM4' ! Like `fmaM4' except that the intermediate product is negated ! before being added to operand 3. This is represented in the rtl as (fma:M (neg:M OP1) OP2 OP3) ! `fnmsM4' ! Like `fmsM4' except that the intermediate product is negated ! before subtracting operand 3. This is represented in the rtl as (fma:M (neg:M OP1) OP2 (neg:M OP3)) ! `sminM3', `smaxM3' Signed minimum and maximum operations. When used with floating ! point, if both operands are zeros, or if either operand is `NaN', ! then it is unspecified which of the two operands is returned as ! the result. ! `fminM3', `fmaxM3' IEEE-conformant minimum and maximum operations. If one operand is ! a quiet `NaN', then the other operand is returned. If both ! operands are quiet `NaN', then a quiet `NaN' is returned. In the ! case when gcc supports signalling `NaN' (-fsignaling-nans) an ! invalid floating point exception is raised and a quiet `NaN' is returned. All operands have mode M, which is a scalar or vector ! floating-point mode. These patterns are not allowed to `FAIL'. ! `reduc_smin_scal_M', `reduc_smax_scal_M' ! Find the signed minimum/maximum of the elements of a vector. The vector is operand 1, and operand 0 is the scalar result, with mode equal to the mode of the elements of the input vector. ! `reduc_umin_scal_M', `reduc_umax_scal_M' ! Find the unsigned minimum/maximum of the elements of a vector. The vector is operand 1, and operand 0 is the scalar result, with mode equal to the mode of the elements of the input vector. ! `reduc_plus_scal_M' ! Compute the sum of the elements of a vector. The vector is operand 1, and operand 0 is the scalar result, with mode equal to the mode of the elements of the input vector. ! `sdot_prodM' ! `udot_prodM' Compute the sum of the products of two signed/unsigned elements. ! Operand 1 and operand 2 are of the same mode. Their product, which ! is of a wider mode, is computed and added to operand 3. Operand 3 ! is of a mode equal or wider than the mode of the product. The ! result is placed in operand 0, which is of the same mode as ! operand 3. ! `ssadM' ! ! `usadM' Compute the sum of absolute differences of two signed/unsigned ! elements. Operand 1 and operand 2 are of the same mode. Their absolute difference, which is of a wider mode, is computed and ! added to operand 3. Operand 3 is of a mode equal or wider than the ! mode of the absolute difference. The result is placed in operand 0, which is of the same mode as operand 3. ! `widen_ssumM3' ! `widen_usumM3' ! Operands 0 and 2 are of the same mode, which is wider than the ! mode of operand 1. Add operand 1 to operand 2 and place the ! widened result in operand 0. (This is used express accumulation of elements into an accumulator of a wider mode.) ! `vec_shr_M' ! Whole vector right shift in bits, i.e. towards element 0. Operand 1 is a vector to be shifted. Operand 2 is an integer shift amount in bits. Operand 0 is where the resulting shifted vector is stored. The output and input vectors should have the same modes. ! `vec_pack_trunc_M' ! Narrow (demote) and merge the elements of two vectors. Operands 1 and 2 are vectors of the same mode having N integral or floating point elements of size S. Operand 0 is the resulting vector in which 2*N elements of size N/2 are concatenated after narrowing them down using truncation. ! `vec_pack_ssat_M', `vec_pack_usat_M' Narrow (demote) and merge the elements of two vectors. Operands 1 and 2 are vectors of the same mode having N integral elements of ! size S. Operand 0 is the resulting vector in which the elements ! of the two input vectors are concatenated after narrowing them ! down using signed/unsigned saturating arithmetic. ! `vec_pack_sfix_trunc_M', `vec_pack_ufix_trunc_M' Narrow, convert to signed/unsigned integral type and merge the elements of two vectors. Operands 1 and 2 are vectors of the same mode having N floating point elements of size S. Operand 0 is the resulting vector in which 2*N elements of size N/2 are concatenated. ! `vec_unpacks_hi_M', `vec_unpacks_lo_M' Extract and widen (promote) the high/low part of a vector of signed integral or floating point elements. The input vector (operand 1) ! has N elements of size S. Widen (promote) the high/low elements ! of the vector using signed or floating point extension and place ! the resulting N/2 values of size 2*S in the output vector (operand ! 0). ! `vec_unpacku_hi_M', `vec_unpacku_lo_M' Extract and widen (promote) the high/low part of a vector of unsigned integral elements. The input vector (operand 1) has N ! elements of size S. Widen (promote) the high/low elements of the vector using zero extension and place the resulting N/2 values of size 2*S in the output vector (operand 0). ! `vec_unpacks_float_hi_M', `vec_unpacks_float_lo_M' ! `vec_unpacku_float_hi_M', `vec_unpacku_float_lo_M' ! Extract, convert to floating point type and widen the high/low ! part of a vector of signed/unsigned integral elements. The input ! vector (operand 1) has N elements of size S. Convert the high/low elements of the vector using floating point conversion and place the resulting N/2 values of size 2*S in the output vector (operand 0). ! `vec_widen_umult_hi_M', `vec_widen_umult_lo_M' ! `vec_widen_smult_hi_M', `vec_widen_smult_lo_M' ! `vec_widen_umult_even_M', `vec_widen_umult_odd_M' ! `vec_widen_smult_even_M', `vec_widen_smult_odd_M' Signed/Unsigned widening multiplication. The two inputs (operands 1 and 2) are vectors with N signed/unsigned elements of size S. Multiply the high/low or even/odd elements of the two vectors, and *************** pattern to accomplish a certain task. *** 23158,23718 **** A target shouldn't implement even/odd pattern pair if it is less efficient than lo/hi one. ! 'vec_widen_ushiftl_hi_M', 'vec_widen_ushiftl_lo_M' ! 'vec_widen_sshiftl_hi_M', 'vec_widen_sshiftl_lo_M' Signed/Unsigned widening shift left. The first input (operand 1) is a vector with N signed/unsigned elements of size S. Operand 2 is a constant. Shift the high/low elements of operand 1, and put the N/2 results of size 2*S in the output vector (operand 0). ! 'mulhisi3' ! Multiply operands 1 and 2, which have mode 'HImode', and store a ! 'SImode' product in operand 0. ! 'mulqihi3', 'mulsidi3' Similar widening-multiplication instructions of other widths. ! 'umulqihi3', 'umulhisi3', 'umulsidi3' Similar widening-multiplication instructions that do unsigned multiplication. ! 'usmulqihi3', 'usmulhisi3', 'usmulsidi3' Similar widening-multiplication instructions that interpret the ! first operand as unsigned and the second operand as signed, then do ! a signed multiplication. ! 'smulM3_highpart' Perform a signed multiplication of operands 1 and 2, which have mode M, and store the most significant half of the product in operand 0. The least significant half of the product is discarded. ! 'umulM3_highpart' Similar, but the multiplication is unsigned. ! 'maddMN4' Multiply operands 1 and 2, sign-extend them to mode N, add operand ! 3, and store the result in operand 0. Operands 1 and 2 have mode M ! and operands 0 and 3 have mode N. Both modes must be integer or fixed-point modes and N must be twice the size of M. ! In other words, 'maddMN4' is like 'mulMN3' except that it also adds ! operand 3. ! These instructions are not allowed to 'FAIL'. ! 'umaddMN4' ! Like 'maddMN4', but zero-extend the multiplication operands instead ! of sign-extending them. ! 'ssmaddMN4' ! Like 'maddMN4', but all involved operations must be signed-saturating. ! 'usmaddMN4' ! Like 'umaddMN4', but all involved operations must be unsigned-saturating. ! 'msubMN4' Multiply operands 1 and 2, sign-extend them to mode N, subtract the ! result from operand 3, and store the result in operand 0. Operands ! 1 and 2 have mode M and operands 0 and 3 have mode N. Both modes ! must be integer or fixed-point modes and N must be twice the size ! of M. ! In other words, 'msubMN4' is like 'mulMN3' except that it also subtracts the result from operand 3. ! These instructions are not allowed to 'FAIL'. ! 'umsubMN4' ! Like 'msubMN4', but zero-extend the multiplication operands instead ! of sign-extending them. ! 'ssmsubMN4' ! Like 'msubMN4', but all involved operations must be signed-saturating. ! 'usmsubMN4' ! Like 'umsubMN4', but all involved operations must be unsigned-saturating. ! 'divmodM4' Signed division that produces both a quotient and a remainder. Operand 1 is divided by operand 2 to produce a quotient stored in operand 0 and a remainder stored in operand 3. For machines with an instruction that produces both a quotient and ! a remainder, provide a pattern for 'divmodM4' but do not provide ! patterns for 'divM3' and 'modM3'. This allows optimization in the relatively common case when both the quotient and remainder are computed. If an instruction that just produces a quotient or just a remainder exists and is more efficient than the instruction that produces ! both, write the output routine of 'divmodM4' to call ! 'find_reg_note' and look for a 'REG_UNUSED' note on the quotient or ! remainder and generate the appropriate instruction. ! 'udivmodM4' Similar, but does unsigned division. ! 'ashlM3', 'ssashlM3', 'usashlM3' Arithmetic-shift operand 1 left by a number of bits specified by operand 2, and store the result in operand 0. Here M is the mode of operand 0 and operand 1; operand 2's mode is specified by the instruction pattern, and the compiler will convert the operand to that mode before generating the instruction. The shift or rotate expander or instruction pattern should explicitly specify the mode ! of the operand 2, it should never be 'VOIDmode'. The meaning of out-of-range shift counts can optionally be specified by ! 'TARGET_SHIFT_TRUNCATION_MASK'. *Note TARGET_SHIFT_TRUNCATION_MASK::. Operand 2 is always a scalar type. ! 'ashrM3', 'lshrM3', 'rotlM3', 'rotrM3' ! Other shift and rotate instructions, analogous to the 'ashlM3' instructions. Operand 2 is always a scalar type. ! 'vashlM3', 'vashrM3', 'vlshrM3', 'vrotlM3', 'vrotrM3' Vector shift and rotate instructions that take vectors as operand 2 instead of a scalar type. ! 'bswapM2' Reverse the order of bytes of operand 1 and store the result in operand 0. ! 'negM2', 'ssnegM2', 'usnegM2' Negate operand 1 and store the result in operand 0. ! 'negvM3' ! Like 'negM2' but takes a 'code_label' as operand 2 and emits code to jump to it if signed overflow occurs during the negation. ! 'absM2' Store the absolute value of operand 1 into operand 0. ! 'sqrtM2' Store the square root of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'rsqrtM2' Store the reciprocal of the square root of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. On most architectures this pattern is only approximate, so either ! its C condition or the 'TARGET_OPTAB_SUPPORTED_P' hook should check ! for the appropriate math flags. (Using the C condition is more ! direct, but using 'TARGET_OPTAB_SUPPORTED_P' can be useful if a ! target-specific built-in also uses the 'rsqrtM2' pattern.) ! This pattern is not allowed to 'FAIL'. ! 'fmodM3' ! Store the remainder of dividing operand 1 by operand 2 into operand ! 0, rounded towards zero to an integer. All operands have mode M, ! which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'remainderM3' ! Store the remainder of dividing operand 1 by operand 2 into operand ! 0, rounded to the nearest integer. All operands have mode M, which ! is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'scalbM3' ! Raise 'FLT_RADIX' to the power of operand 2, multiply it by operand ! 1, and store the result in operand 0. All operands have mode M, ! which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'ldexpM3' Raise 2 to the power of operand 2, multiply it by operand 1, and ! store the result in operand 0. Operands 0 and 1 have mode M, which ! is a scalar or vector floating-point mode. Operand 2's mode has ! the same number of elements as M and each element is wide enough to ! store an 'int'. The integers are signed. ! This pattern is not allowed to 'FAIL'. ! 'cosM2' Store the cosine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'sinM2' Store the sine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'sincosM3' Store the cosine of operand 2 into operand 0 and the sine of operand 2 into operand 1. All operands have mode M, which is a scalar or vector floating-point mode. Targets that can calculate the sine and cosine simultaneously can implement this pattern as opposed to implementing individual ! 'sinM2' and 'cosM2' patterns. The 'sin' and 'cos' built-in ! functions will then be expanded to the 'sincosM3' pattern, with one ! of the output values left unused. ! 'tanM2' Store the tangent of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'asinM2' Store the arc sine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'acosM2' Store the arc cosine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'atanM2' Store the arc tangent of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'expM2' Raise e (the base of natural logarithms) to the power of operand 1 and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'expm1M2' Raise e (the base of natural logarithms) to the power of operand 1, subtract 1, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. For inputs close to zero, the pattern is expected to be more ! accurate than a separate 'expM2' and 'subM3' would be. ! This pattern is not allowed to 'FAIL'. ! 'exp10M2' Raise 10 to the power of operand 1 and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'exp2M2' Raise 2 to the power of operand 1 and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'logM2' Store the natural logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'log1pM2' Add 1 to operand 1, compute the natural logarithm, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. For inputs close to zero, the pattern is expected to be more ! accurate than a separate 'addM3' and 'logM2' would be. ! This pattern is not allowed to 'FAIL'. ! 'log10M2' Store the base-10 logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'log2M2' Store the base-2 logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'logbM2' ! Store the base-'FLT_RADIX' logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'significandM2' Store the significand of floating-point operand 1 in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'powM3' Store the value of operand 1 raised to the exponent operand 2 into operand 0. All operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'atan2M3' Store the arc tangent (inverse tangent) of operand 1 divided by operand 2 into operand 0, using the signs of both arguments to determine the quadrant of the result. All operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'floorM2' Store the largest integral value not greater than operand 1 in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'btruncM2' Round operand 1 to an integer, towards zero, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'roundM2' Round operand 1 to the nearest integer, rounding away from zero in the event of a tie, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'ceilM2' Store the smallest integral value not less than operand 1 in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'nearbyintM2' Round operand 1 to an integer, using the current rounding mode, and store the result in operand 0. Do not raise an inexact condition ! when the result is different from the argument. Both operands have ! mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'rintM2' Round operand 1 to an integer, using the current rounding mode, and ! store the result in operand 0. Raise an inexact condition when the ! result is different from the argument. Both operands have mode M, ! which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'lrintMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number according to the current rounding mode and store in operand 0 (which has mode N). ! 'lroundMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number rounding to nearest and away from zero and store in operand 0 (which has mode N). ! 'lfloorMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number rounding down and store in operand 0 (which has mode N). ! 'lceilMN2' Convert operand 1 (valid for floating point mode M) to fixed point ! mode N as a signed number rounding up and store in operand 0 (which ! has mode N). ! 'copysignM3' Store a value with the magnitude of operand 1 and the sign of operand 2 into operand 0. All operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to 'FAIL'. ! 'ffsM2' Store into operand 0 one plus the index of the least significant 1-bit of operand 1. If operand 1 is zero, store zero. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar integer ! mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as 'int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to 'FAIL'. ! 'clrsbM2' ! Count leading redundant sign bits. Store into operand 0 the number ! of redundant sign bits in operand 1, starting at the most significant bit position. A redundant sign bit is defined as any ! sign bit after the first. As such, this count will be one less than the count of leading sign bits. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar integer ! mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as 'int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to 'FAIL'. ! 'clzM2' Store into operand 0 the number of leading 0-bits in operand 1, starting at the most significant bit position. If operand 1 is 0, ! the 'CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if the ! result is undefined or has a useful value. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar integer ! mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as 'int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to 'FAIL'. ! 'ctzM2' Store into operand 0 the number of trailing 0-bits in operand 1, ! starting at the least significant bit position. If operand 1 is 0, ! the 'CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if the ! result is undefined or has a useful value. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar integer ! mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as 'int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to 'FAIL'. ! 'popcountM2' Store into operand 0 the number of 1-bits in operand 1. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar integer ! mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as 'int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to 'FAIL'. ! 'parityM2' Store into operand 0 the parity of operand 1, i.e. the number of 1-bits in operand 1 modulo 2. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar integer ! mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as 'int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to 'FAIL'. ! 'one_cmplM2' Store the bitwise-complement of operand 1 into operand 0. ! 'movmemM' Block move instruction. The destination and source blocks of ! memory are the first two operands, and both are 'mem:BLK's with an ! address in mode 'Pmode'. The number of bytes to move is the third operand, in mode M. ! Usually, you specify 'Pmode' for M. However, if you can generate better code knowing the range of valid lengths is smaller than those representable in a full Pmode pointer, you should provide a pattern with a mode corresponding to the range of values you can ! handle efficiently (e.g., 'QImode' for values in the range 0-127; ! note we avoid numbers that appear negative) and also a pattern with ! 'Pmode'. The fourth operand is the known shared alignment of the source and ! destination, in the form of a 'const_int' rtx. Thus, if the compiler knows that both source and destination are word-aligned, it may provide the value 4 for this operand. Optional operands 5 and 6 specify expected alignment and size of block respectively. The expected alignment differs from alignment in operand 4 in a way that the blocks are not required to be ! aligned according to it in all cases. This expected alignment is also in bytes, just like operand 4. Expected size, when unknown, ! is set to '(const_int -1)'. ! Descriptions of multiple 'movmemM' patterns can only be beneficial if the patterns for smaller modes have fewer restrictions on their first, second and fourth operands. Note that the mode M in ! 'movmemM' does not impose any restriction on the mode of individually moved data units in the block. These patterns need not give special consideration to the possibility that the source and destination strings might overlap. ! 'movstr' ! String copy instruction, with 'stpcpy' semantics. Operand 0 is an ! output operand in mode 'Pmode'. The addresses of the destination ! and source strings are operands 1 and 2, and both are 'mem:BLK's ! with addresses in mode 'Pmode'. The execution of the expansion of this pattern should store in operand 0 the address in which the ! 'NUL' terminator was stored in the destination string. This patern has also several optional operands that are same as in ! 'setmem'. ! 'setmemM' Block set instruction. The destination string is the first ! operand, given as a 'mem:BLK' whose address is in mode 'Pmode'. The number of bytes to set is the second operand, in mode M. The ! value to initialize the memory with is the third operand. Targets that only support the clearing of memory should reject any value ! that is not the constant 0. See 'movmemM' for a discussion of the choice of mode. The fourth operand is the known alignment of the destination, in ! the form of a 'const_int' rtx. Thus, if the compiler knows that the destination is word-aligned, it may provide the value 4 for this operand. Optional operands 5 and 6 specify expected alignment and size of block respectively. The expected alignment differs from alignment in operand 4 in a way that the blocks are not required to be ! aligned according to it in all cases. This expected alignment is also in bytes, just like operand 4. Expected size, when unknown, ! is set to '(const_int -1)'. Operand 7 is the minimal size of the block and operand 8 is the maximal size of the block (NULL if it ! can not be represented as CONST_INT). Operand 9 is the probable ! maximal size (i.e. we can not rely on it for correctness, but it can be used for choosing proper code sequence for a given size). ! The use for multiple 'setmemM' is as for 'movmemM'. ! 'cmpstrnM' String compare instruction, with five operands. Operand 0 is the output; it has mode M. The remaining four operands are like the ! operands of 'movmemM'. The two memory blocks specified are compared byte by byte in lexicographic order starting at the beginning of each string. The instruction is not allowed to prefetch more than one byte at a time since either string may end --- 23538,24098 ---- A target shouldn't implement even/odd pattern pair if it is less efficient than lo/hi one. ! `vec_widen_ushiftl_hi_M', `vec_widen_ushiftl_lo_M' ! `vec_widen_sshiftl_hi_M', `vec_widen_sshiftl_lo_M' Signed/Unsigned widening shift left. The first input (operand 1) is a vector with N signed/unsigned elements of size S. Operand 2 is a constant. Shift the high/low elements of operand 1, and put the N/2 results of size 2*S in the output vector (operand 0). ! `mulhisi3' ! Multiply operands 1 and 2, which have mode `HImode', and store a ! `SImode' product in operand 0. ! `mulqihi3', `mulsidi3' Similar widening-multiplication instructions of other widths. ! `umulqihi3', `umulhisi3', `umulsidi3' Similar widening-multiplication instructions that do unsigned multiplication. ! `usmulqihi3', `usmulhisi3', `usmulsidi3' Similar widening-multiplication instructions that interpret the ! first operand as unsigned and the second operand as signed, then ! do a signed multiplication. ! `smulM3_highpart' Perform a signed multiplication of operands 1 and 2, which have mode M, and store the most significant half of the product in operand 0. The least significant half of the product is discarded. ! `umulM3_highpart' Similar, but the multiplication is unsigned. ! `maddMN4' Multiply operands 1 and 2, sign-extend them to mode N, add operand ! 3, and store the result in operand 0. Operands 1 and 2 have mode ! M and operands 0 and 3 have mode N. Both modes must be integer or fixed-point modes and N must be twice the size of M. ! In other words, `maddMN4' is like `mulMN3' except that it also ! adds operand 3. ! These instructions are not allowed to `FAIL'. ! `umaddMN4' ! Like `maddMN4', but zero-extend the multiplication operands ! instead of sign-extending them. ! `ssmaddMN4' ! Like `maddMN4', but all involved operations must be signed-saturating. ! `usmaddMN4' ! Like `umaddMN4', but all involved operations must be unsigned-saturating. ! `msubMN4' Multiply operands 1 and 2, sign-extend them to mode N, subtract the ! result from operand 3, and store the result in operand 0. ! Operands 1 and 2 have mode M and operands 0 and 3 have mode N. ! Both modes must be integer or fixed-point modes and N must be twice ! the size of M. ! In other words, `msubMN4' is like `mulMN3' except that it also subtracts the result from operand 3. ! These instructions are not allowed to `FAIL'. ! `umsubMN4' ! Like `msubMN4', but zero-extend the multiplication operands ! instead of sign-extending them. ! `ssmsubMN4' ! Like `msubMN4', but all involved operations must be signed-saturating. ! `usmsubMN4' ! Like `umsubMN4', but all involved operations must be unsigned-saturating. ! `divmodM4' Signed division that produces both a quotient and a remainder. Operand 1 is divided by operand 2 to produce a quotient stored in operand 0 and a remainder stored in operand 3. For machines with an instruction that produces both a quotient and ! a remainder, provide a pattern for `divmodM4' but do not provide ! patterns for `divM3' and `modM3'. This allows optimization in the relatively common case when both the quotient and remainder are computed. If an instruction that just produces a quotient or just a remainder exists and is more efficient than the instruction that produces ! both, write the output routine of `divmodM4' to call ! `find_reg_note' and look for a `REG_UNUSED' note on the quotient ! or remainder and generate the appropriate instruction. ! `udivmodM4' Similar, but does unsigned division. ! `ashlM3', `ssashlM3', `usashlM3' Arithmetic-shift operand 1 left by a number of bits specified by operand 2, and store the result in operand 0. Here M is the mode of operand 0 and operand 1; operand 2's mode is specified by the instruction pattern, and the compiler will convert the operand to that mode before generating the instruction. The shift or rotate expander or instruction pattern should explicitly specify the mode ! of the operand 2, it should never be `VOIDmode'. The meaning of out-of-range shift counts can optionally be specified by ! `TARGET_SHIFT_TRUNCATION_MASK'. *Note TARGET_SHIFT_TRUNCATION_MASK::. Operand 2 is always a scalar type. ! `ashrM3', `lshrM3', `rotlM3', `rotrM3' ! Other shift and rotate instructions, analogous to the `ashlM3' instructions. Operand 2 is always a scalar type. ! `vashlM3', `vashrM3', `vlshrM3', `vrotlM3', `vrotrM3' Vector shift and rotate instructions that take vectors as operand 2 instead of a scalar type. ! `bswapM2' Reverse the order of bytes of operand 1 and store the result in operand 0. ! `negM2', `ssnegM2', `usnegM2' Negate operand 1 and store the result in operand 0. ! `negvM3' ! Like `negM2' but takes a `code_label' as operand 2 and emits code to jump to it if signed overflow occurs during the negation. ! `absM2' Store the absolute value of operand 1 into operand 0. ! `sqrtM2' Store the square root of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `rsqrtM2' Store the reciprocal of the square root of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. On most architectures this pattern is only approximate, so either ! its C condition or the `TARGET_OPTAB_SUPPORTED_P' hook should ! check for the appropriate math flags. (Using the C condition is ! more direct, but using `TARGET_OPTAB_SUPPORTED_P' can be useful if ! a target-specific built-in also uses the `rsqrtM2' pattern.) ! This pattern is not allowed to `FAIL'. ! `fmodM3' ! Store the remainder of dividing operand 1 by operand 2 into ! operand 0, rounded towards zero to an integer. All operands have ! mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `remainderM3' ! Store the remainder of dividing operand 1 by operand 2 into ! operand 0, rounded to the nearest integer. All operands have mode ! M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `scalbM3' ! Raise `FLT_RADIX' to the power of operand 2, multiply it by ! operand 1, and store the result in operand 0. All operands have ! mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `ldexpM3' Raise 2 to the power of operand 2, multiply it by operand 1, and ! store the result in operand 0. Operands 0 and 1 have mode M, ! which is a scalar or vector floating-point mode. Operand 2's mode ! has the same number of elements as M and each element is wide ! enough to store an `int'. The integers are signed. ! This pattern is not allowed to `FAIL'. ! `cosM2' Store the cosine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `sinM2' Store the sine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `sincosM3' Store the cosine of operand 2 into operand 0 and the sine of operand 2 into operand 1. All operands have mode M, which is a scalar or vector floating-point mode. Targets that can calculate the sine and cosine simultaneously can implement this pattern as opposed to implementing individual ! `sinM2' and `cosM2' patterns. The `sin' and `cos' built-in ! functions will then be expanded to the `sincosM3' pattern, with ! one of the output values left unused. ! `tanM2' Store the tangent of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `asinM2' Store the arc sine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `acosM2' Store the arc cosine of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `atanM2' Store the arc tangent of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `expM2' Raise e (the base of natural logarithms) to the power of operand 1 and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `expm1M2' Raise e (the base of natural logarithms) to the power of operand 1, subtract 1, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. For inputs close to zero, the pattern is expected to be more ! accurate than a separate `expM2' and `subM3' would be. ! This pattern is not allowed to `FAIL'. ! `exp10M2' Raise 10 to the power of operand 1 and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `exp2M2' Raise 2 to the power of operand 1 and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `logM2' Store the natural logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `log1pM2' Add 1 to operand 1, compute the natural logarithm, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. For inputs close to zero, the pattern is expected to be more ! accurate than a separate `addM3' and `logM2' would be. ! This pattern is not allowed to `FAIL'. ! `log10M2' Store the base-10 logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `log2M2' Store the base-2 logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `logbM2' ! Store the base-`FLT_RADIX' logarithm of operand 1 into operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `significandM2' Store the significand of floating-point operand 1 in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `powM3' Store the value of operand 1 raised to the exponent operand 2 into operand 0. All operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `atan2M3' Store the arc tangent (inverse tangent) of operand 1 divided by operand 2 into operand 0, using the signs of both arguments to determine the quadrant of the result. All operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `floorM2' Store the largest integral value not greater than operand 1 in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `btruncM2' Round operand 1 to an integer, towards zero, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `roundM2' Round operand 1 to the nearest integer, rounding away from zero in the event of a tie, and store the result in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `ceilM2' Store the smallest integral value not less than operand 1 in operand 0. Both operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `nearbyintM2' Round operand 1 to an integer, using the current rounding mode, and store the result in operand 0. Do not raise an inexact condition ! when the result is different from the argument. Both operands ! have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `rintM2' Round operand 1 to an integer, using the current rounding mode, and ! store the result in operand 0. Raise an inexact condition when ! the result is different from the argument. Both operands have mode ! M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `lrintMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number according to the current rounding mode and store in operand 0 (which has mode N). ! `lroundMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number rounding to nearest and away from zero and store in operand 0 (which has mode N). ! `lfloorMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number rounding down and store in operand 0 (which has mode N). ! `lceilMN2' Convert operand 1 (valid for floating point mode M) to fixed point ! mode N as a signed number rounding up and store in operand 0 ! (which has mode N). ! `copysignM3' Store a value with the magnitude of operand 1 and the sign of operand 2 into operand 0. All operands have mode M, which is a scalar or vector floating-point mode. ! This pattern is not allowed to `FAIL'. ! `ffsM2' Store into operand 0 one plus the index of the least significant 1-bit of operand 1. If operand 1 is zero, store zero. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar ! integer mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as `int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to `FAIL'. ! `clrsbM2' ! Count leading redundant sign bits. Store into operand 0 the ! number of redundant sign bits in operand 1, starting at the most significant bit position. A redundant sign bit is defined as any ! sign bit after the first. As such, this count will be one less than the count of leading sign bits. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar ! integer mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as `int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to `FAIL'. ! `clzM2' Store into operand 0 the number of leading 0-bits in operand 1, starting at the most significant bit position. If operand 1 is 0, ! the `CLZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if ! the result is undefined or has a useful value. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar ! integer mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as `int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to `FAIL'. ! `ctzM2' Store into operand 0 the number of trailing 0-bits in operand 1, ! starting at the least significant bit position. If operand 1 is ! 0, the `CTZ_DEFINED_VALUE_AT_ZERO' (*note Misc::) macro defines if ! the result is undefined or has a useful value. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar ! integer mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as `int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to `FAIL'. ! `popcountM2' Store into operand 0 the number of 1-bits in operand 1. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar ! integer mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as `int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to `FAIL'. ! `parityM2' Store into operand 0 the parity of operand 1, i.e. the number of 1-bits in operand 1 modulo 2. M is either a scalar or vector integer mode. When it is a scalar, ! operand 1 has mode M but operand 0 can have whatever scalar ! integer mode is suitable for the target. The compiler will insert conversion instructions as necessary (typically to convert the ! result to the same width as `int'). When M is a vector, both operands must have mode M. ! This pattern is not allowed to `FAIL'. ! `one_cmplM2' Store the bitwise-complement of operand 1 into operand 0. ! `movmemM' Block move instruction. The destination and source blocks of ! memory are the first two operands, and both are `mem:BLK's with an ! address in mode `Pmode'. The number of bytes to move is the third operand, in mode M. ! Usually, you specify `Pmode' for M. However, if you can generate better code knowing the range of valid lengths is smaller than those representable in a full Pmode pointer, you should provide a pattern with a mode corresponding to the range of values you can ! handle efficiently (e.g., `QImode' for values in the range 0-127; ! note we avoid numbers that appear negative) and also a pattern ! with `Pmode'. The fourth operand is the known shared alignment of the source and ! destination, in the form of a `const_int' rtx. Thus, if the compiler knows that both source and destination are word-aligned, it may provide the value 4 for this operand. Optional operands 5 and 6 specify expected alignment and size of block respectively. The expected alignment differs from alignment in operand 4 in a way that the blocks are not required to be ! aligned according to it in all cases. This expected alignment is also in bytes, just like operand 4. Expected size, when unknown, ! is set to `(const_int -1)'. ! Descriptions of multiple `movmemM' patterns can only be beneficial if the patterns for smaller modes have fewer restrictions on their first, second and fourth operands. Note that the mode M in ! `movmemM' does not impose any restriction on the mode of individually moved data units in the block. These patterns need not give special consideration to the possibility that the source and destination strings might overlap. ! `movstr' ! String copy instruction, with `stpcpy' semantics. Operand 0 is an ! output operand in mode `Pmode'. The addresses of the destination ! and source strings are operands 1 and 2, and both are `mem:BLK's ! with addresses in mode `Pmode'. The execution of the expansion of this pattern should store in operand 0 the address in which the ! `NUL' terminator was stored in the destination string. This patern has also several optional operands that are same as in ! `setmem'. ! `setmemM' Block set instruction. The destination string is the first ! operand, given as a `mem:BLK' whose address is in mode `Pmode'. The number of bytes to set is the second operand, in mode M. The ! value to initialize the memory with is the third operand. Targets that only support the clearing of memory should reject any value ! that is not the constant 0. See `movmemM' for a discussion of the choice of mode. The fourth operand is the known alignment of the destination, in ! the form of a `const_int' rtx. Thus, if the compiler knows that the destination is word-aligned, it may provide the value 4 for this operand. Optional operands 5 and 6 specify expected alignment and size of block respectively. The expected alignment differs from alignment in operand 4 in a way that the blocks are not required to be ! aligned according to it in all cases. This expected alignment is also in bytes, just like operand 4. Expected size, when unknown, ! is set to `(const_int -1)'. Operand 7 is the minimal size of the block and operand 8 is the maximal size of the block (NULL if it ! can not be represented as CONST_INT). Operand 9 is the probable ! maximal size (i.e. we can not rely on it for correctness, but it can be used for choosing proper code sequence for a given size). ! The use for multiple `setmemM' is as for `movmemM'. ! `cmpstrnM' String compare instruction, with five operands. Operand 0 is the output; it has mode M. The remaining four operands are like the ! operands of `movmemM'. The two memory blocks specified are compared byte by byte in lexicographic order starting at the beginning of each string. The instruction is not allowed to prefetch more than one byte at a time since either string may end *************** pattern to accomplish a certain task. *** 23722,23904 **** effect of the instruction is to store a value in operand 0 whose sign indicates the result of the comparison. ! 'cmpstrM' String compare instruction, without known maximum length. Operand 0 is the output; it has mode M. The second and third operand are ! the blocks of memory to be compared; both are 'mem:BLK' with an ! address in mode 'Pmode'. The fourth operand is the known shared alignment of the source and ! destination, in the form of a 'const_int' rtx. Thus, if the compiler knows that both source and destination are word-aligned, it may provide the value 4 for this operand. The two memory blocks specified are compared byte by byte in lexicographic order starting at the beginning of each string. The ! instruction is not allowed to prefetch more than one byte at a time ! since either string may end in the first byte and reading past that ! may access an invalid page or segment and cause a fault. The ! comparison will terminate when the fetched bytes are different or ! if they are equal to zero. The effect of the instruction is to store a value in operand 0 whose sign indicates the result of the comparison. ! 'cmpmemM' Block compare instruction, with five operands like the operands of ! 'cmpstrM'. The two memory blocks specified are compared byte by byte in lexicographic order starting at the beginning of each ! block. Unlike 'cmpstrM' the instruction can prefetch any bytes in ! the two memory blocks. Also unlike 'cmpstrM' the comparison will not stop if both bytes are zero. The effect of the instruction is to store a value in operand 0 whose sign indicates the result of the comparison. ! 'strlenM' Compute the length of a string, with three operands. Operand 0 is ! the result (of mode M), operand 1 is a 'mem' referring to the first ! character of the string, operand 2 is the character to search for ! (normally zero), and operand 3 is a constant describing the known ! alignment of the beginning of the string. ! 'floatMN2' Convert signed integer operand 1 (valid for fixed point mode M) to floating point mode N and store in operand 0 (which has mode N). ! 'floatunsMN2' Convert unsigned integer operand 1 (valid for fixed point mode M) to floating point mode N and store in operand 0 (which has mode N). ! 'fixMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number and store in operand 0 (which has mode N). This instruction's result is defined only when the value of operand 1 is an integer. If the machine description defines this pattern, it also needs to ! define the 'ftrunc' pattern. ! 'fixunsMN2' Convert operand 1 (valid for floating point mode M) to fixed point ! mode N as an unsigned number and store in operand 0 (which has mode ! N). This instruction's result is defined only when the value of ! operand 1 is an integer. ! 'ftruncM2' Convert operand 1 (valid for floating point mode M) to an integer value, still represented in floating point mode M, and store it in operand 0 (valid for floating point mode M). ! 'fix_truncMN2' ! Like 'fixMN2' but works for any floating point value of mode M by converting the value to an integer. ! 'fixuns_truncMN2' ! Like 'fixunsMN2' but works for any floating point value of mode M by converting the value to an integer. ! 'truncMN2' Truncate operand 1 (valid for mode M) to mode N and store in operand 0 (which has mode N). Both modes must be fixed point or both floating point. ! 'extendMN2' Sign-extend operand 1 (valid for mode M) to mode N and store in operand 0 (which has mode N). Both modes must be fixed point or both floating point. ! 'zero_extendMN2' Zero-extend operand 1 (valid for mode M) to mode N and store in operand 0 (which has mode N). Both modes must be fixed point. ! 'fractMN2' ! Convert operand 1 of mode M to mode N and store in operand 0 (which ! has mode N). Mode M and mode N could be fixed-point to fixed-point, signed integer to fixed-point, fixed-point to signed integer, floating-point to fixed-point, or fixed-point to floating-point. When overflows or underflows happen, the results are undefined. ! 'satfractMN2' ! Convert operand 1 of mode M to mode N and store in operand 0 (which ! has mode N). Mode M and mode N could be fixed-point to fixed-point, signed integer to fixed-point, or floating-point to fixed-point. When overflows or underflows happen, the instruction saturates the results to the maximum or the minimum. ! 'fractunsMN2' ! Convert operand 1 of mode M to mode N and store in operand 0 (which ! has mode N). Mode M and mode N could be unsigned integer to ! fixed-point, or fixed-point to unsigned integer. When overflows or ! underflows happen, the results are undefined. ! 'satfractunsMN2' Convert unsigned integer operand 1 of mode M to fixed-point mode N and store in operand 0 (which has mode N). When overflows or underflows happen, the instruction saturates the results to the maximum or the minimum. ! 'extvM' Extract a bit-field from register operand 1, sign-extend it, and store it in operand 0. Operand 2 specifies the width of the field in bits and operand 3 the starting bit, which counts from the most ! significant bit if 'BITS_BIG_ENDIAN' is true and from the least significant bit otherwise. Operands 0 and 1 both have mode M. Operands 2 and 3 have a target-specific mode. ! 'extvmisalignM' Extract a bit-field from memory operand 1, sign extend it, and store it in operand 0. Operand 2 specifies the width in bits and operand 3 the starting bit. The starting bit is always somewhere ! in the first byte of operand 1; it counts from the most significant ! bit if 'BITS_BIG_ENDIAN' is true and from the least significant bit ! otherwise. ! Operand 0 has mode M while operand 1 has 'BLK' mode. Operands 2 and 3 have a target-specific mode. The instruction must not read beyond the last byte of the bit-field. ! 'extzvM' ! Like 'extvM' except that the bit-field value is zero-extended. ! 'extzvmisalignM' ! Like 'extvmisalignM' except that the bit-field value is zero-extended. ! 'insvM' Insert operand 3 into a bit-field of register operand 0. Operand 1 ! specifies the width of the field in bits and operand 2 the starting ! bit, which counts from the most significant bit if ! 'BITS_BIG_ENDIAN' is true and from the least significant bit otherwise. Operands 0 and 3 both have mode M. Operands 1 and 2 have a target-specific mode. ! 'insvmisalignM' Insert operand 3 into a bit-field of memory operand 0. Operand 1 ! specifies the width of the field in bits and operand 2 the starting ! bit. The starting bit is always somewhere in the first byte of ! operand 0; it counts from the most significant bit if ! 'BITS_BIG_ENDIAN' is true and from the least significant bit otherwise. ! Operand 3 has mode M while operand 0 has 'BLK' mode. Operands 1 and 2 have a target-specific mode. The instruction must not read or write beyond the last byte of the bit-field. ! 'extv' Extract a bit-field from operand 1 (a register or memory operand), where operand 2 specifies the width in bits and operand 3 the starting bit, and store it in operand 0. Operand 0 must have mode ! 'word_mode'. Operand 1 may have mode 'byte_mode' or 'word_mode'; ! often 'word_mode' is allowed only for registers. Operands 2 and 3 ! must be valid for 'word_mode'. The RTL generation pass generates this instruction only with constants for operands 2 and 3 and the constant is never zero for --- 24102,24284 ---- effect of the instruction is to store a value in operand 0 whose sign indicates the result of the comparison. ! `cmpstrM' String compare instruction, without known maximum length. Operand 0 is the output; it has mode M. The second and third operand are ! the blocks of memory to be compared; both are `mem:BLK' with an ! address in mode `Pmode'. The fourth operand is the known shared alignment of the source and ! destination, in the form of a `const_int' rtx. Thus, if the compiler knows that both source and destination are word-aligned, it may provide the value 4 for this operand. The two memory blocks specified are compared byte by byte in lexicographic order starting at the beginning of each string. The ! instruction is not allowed to prefetch more than one byte at a ! time since either string may end in the first byte and reading ! past that may access an invalid page or segment and cause a fault. ! The comparison will terminate when the fetched bytes are different ! or if they are equal to zero. The effect of the instruction is to store a value in operand 0 whose sign indicates the result of the comparison. ! `cmpmemM' Block compare instruction, with five operands like the operands of ! `cmpstrM'. The two memory blocks specified are compared byte by byte in lexicographic order starting at the beginning of each ! block. Unlike `cmpstrM' the instruction can prefetch any bytes in ! the two memory blocks. Also unlike `cmpstrM' the comparison will not stop if both bytes are zero. The effect of the instruction is to store a value in operand 0 whose sign indicates the result of the comparison. ! `strlenM' Compute the length of a string, with three operands. Operand 0 is ! the result (of mode M), operand 1 is a `mem' referring to the ! first character of the string, operand 2 is the character to ! search for (normally zero), and operand 3 is a constant describing ! the known alignment of the beginning of the string. ! `floatMN2' Convert signed integer operand 1 (valid for fixed point mode M) to floating point mode N and store in operand 0 (which has mode N). ! `floatunsMN2' Convert unsigned integer operand 1 (valid for fixed point mode M) to floating point mode N and store in operand 0 (which has mode N). ! `fixMN2' Convert operand 1 (valid for floating point mode M) to fixed point mode N as a signed number and store in operand 0 (which has mode N). This instruction's result is defined only when the value of operand 1 is an integer. If the machine description defines this pattern, it also needs to ! define the `ftrunc' pattern. ! `fixunsMN2' Convert operand 1 (valid for floating point mode M) to fixed point ! mode N as an unsigned number and store in operand 0 (which has ! mode N). This instruction's result is defined only when the value ! of operand 1 is an integer. ! `ftruncM2' Convert operand 1 (valid for floating point mode M) to an integer value, still represented in floating point mode M, and store it in operand 0 (valid for floating point mode M). ! `fix_truncMN2' ! Like `fixMN2' but works for any floating point value of mode M by converting the value to an integer. ! `fixuns_truncMN2' ! Like `fixunsMN2' but works for any floating point value of mode M by converting the value to an integer. ! `truncMN2' Truncate operand 1 (valid for mode M) to mode N and store in operand 0 (which has mode N). Both modes must be fixed point or both floating point. ! `extendMN2' Sign-extend operand 1 (valid for mode M) to mode N and store in operand 0 (which has mode N). Both modes must be fixed point or both floating point. ! `zero_extendMN2' Zero-extend operand 1 (valid for mode M) to mode N and store in operand 0 (which has mode N). Both modes must be fixed point. ! `fractMN2' ! Convert operand 1 of mode M to mode N and store in operand 0 ! (which has mode N). Mode M and mode N could be fixed-point to fixed-point, signed integer to fixed-point, fixed-point to signed integer, floating-point to fixed-point, or fixed-point to floating-point. When overflows or underflows happen, the results are undefined. ! `satfractMN2' ! Convert operand 1 of mode M to mode N and store in operand 0 ! (which has mode N). Mode M and mode N could be fixed-point to fixed-point, signed integer to fixed-point, or floating-point to fixed-point. When overflows or underflows happen, the instruction saturates the results to the maximum or the minimum. ! `fractunsMN2' ! Convert operand 1 of mode M to mode N and store in operand 0 ! (which has mode N). Mode M and mode N could be unsigned integer ! to fixed-point, or fixed-point to unsigned integer. When ! overflows or underflows happen, the results are undefined. ! `satfractunsMN2' Convert unsigned integer operand 1 of mode M to fixed-point mode N and store in operand 0 (which has mode N). When overflows or underflows happen, the instruction saturates the results to the maximum or the minimum. ! `extvM' Extract a bit-field from register operand 1, sign-extend it, and store it in operand 0. Operand 2 specifies the width of the field in bits and operand 3 the starting bit, which counts from the most ! significant bit if `BITS_BIG_ENDIAN' is true and from the least significant bit otherwise. Operands 0 and 1 both have mode M. Operands 2 and 3 have a target-specific mode. ! `extvmisalignM' Extract a bit-field from memory operand 1, sign extend it, and store it in operand 0. Operand 2 specifies the width in bits and operand 3 the starting bit. The starting bit is always somewhere ! in the first byte of operand 1; it counts from the most ! significant bit if `BITS_BIG_ENDIAN' is true and from the least ! significant bit otherwise. ! Operand 0 has mode M while operand 1 has `BLK' mode. Operands 2 and 3 have a target-specific mode. The instruction must not read beyond the last byte of the bit-field. ! `extzvM' ! Like `extvM' except that the bit-field value is zero-extended. ! `extzvmisalignM' ! Like `extvmisalignM' except that the bit-field value is zero-extended. ! `insvM' Insert operand 3 into a bit-field of register operand 0. Operand 1 ! specifies the width of the field in bits and operand 2 the ! starting bit, which counts from the most significant bit if ! `BITS_BIG_ENDIAN' is true and from the least significant bit otherwise. Operands 0 and 3 both have mode M. Operands 1 and 2 have a target-specific mode. ! `insvmisalignM' Insert operand 3 into a bit-field of memory operand 0. Operand 1 ! specifies the width of the field in bits and operand 2 the ! starting bit. The starting bit is always somewhere in the first ! byte of operand 0; it counts from the most significant bit if ! `BITS_BIG_ENDIAN' is true and from the least significant bit otherwise. ! Operand 3 has mode M while operand 0 has `BLK' mode. Operands 1 and 2 have a target-specific mode. The instruction must not read or write beyond the last byte of the bit-field. ! `extv' Extract a bit-field from operand 1 (a register or memory operand), where operand 2 specifies the width in bits and operand 3 the starting bit, and store it in operand 0. Operand 0 must have mode ! `word_mode'. Operand 1 may have mode `byte_mode' or `word_mode'; ! often `word_mode' is allowed only for registers. Operands 2 and 3 ! must be valid for `word_mode'. The RTL generation pass generates this instruction only with constants for operands 2 and 3 and the constant is never zero for *************** pattern to accomplish a certain task. *** 23907,24023 **** The bit-field value is sign-extended to a full word integer before it is stored in operand 0. ! This pattern is deprecated; please use 'extvM' and 'extvmisalignM' instead. ! 'extzv' ! Like 'extv' except that the bit-field value is zero-extended. ! This pattern is deprecated; please use 'extzvM' and ! 'extzvmisalignM' instead. ! 'insv' ! Store operand 3 (which must be valid for 'word_mode') into a ! bit-field in operand 0, where operand 1 specifies the width in bits ! and operand 2 the starting bit. Operand 0 may have mode ! 'byte_mode' or 'word_mode'; often 'word_mode' is allowed only for ! registers. Operands 1 and 2 must be valid for 'word_mode'. The RTL generation pass generates this instruction only with constants for operands 1 and 2 and the constant is never zero for operand 1. ! This pattern is deprecated; please use 'insvM' and 'insvmisalignM' instead. ! 'movMODEcc' Conditionally move operand 2 or operand 3 into operand 0 according ! to the comparison in operand 1. If the comparison is true, operand ! 2 is moved into operand 0, otherwise operand 3 is moved. ! The mode of the operands being compared need not be the same as the ! operands being moved. Some machines, sparc64 for example, have ! instructions that conditionally move an integer value based on the ! floating point condition codes and vice versa. If the machine does not have conditional move instructions, do not define these patterns. ! 'addMODEcc' ! Similar to 'movMODEcc' but for conditional addition. Conditionally ! move operand 2 or (operands 2 + operand 3) into operand 0 according ! to the comparison in operand 1. If the comparison is false, ! operand 2 is moved into operand 0, otherwise (operand 2 + operand ! 3) is moved. ! 'negMODEcc' ! Similar to 'movMODEcc' but for conditional negation. Conditionally move the negation of operand 2 or the unchanged operand 3 into operand 0 according to the comparison in operand 1. If the ! comparison is true, the negation of operand 2 is moved into operand ! 0, otherwise operand 3 is moved. ! 'notMODEcc' ! Similar to 'negMODEcc' but for conditional complement. Conditionally move the bitwise complement of operand 2 or the unchanged operand 3 into operand 0 according to the comparison in operand 1. If the comparison is true, the complement of operand 2 is moved into operand 0, otherwise operand 3 is moved. ! 'cstoreMODE4' Store zero or nonzero in operand 0 according to whether a ! comparison is true. Operand 1 is a comparison operator. Operand 2 ! and operand 3 are the first and second operand of the comparison, ! respectively. You specify the mode that operand 0 must have when ! you write the 'match_operand' expression. The compiler ! automatically sees which mode you have used and supplies an operand ! of that mode. The value stored for a true condition must have 1 as its low bit, or else must be negative. Otherwise the instruction is not suitable and you should omit it from the machine description. You describe to the compiler exactly which value is stored by defining ! the macro 'STORE_FLAG_VALUE' (*note Misc::). If a description cannot be found that can be used for all the possible comparison ! operators, you should pick one and use a 'define_expand' to map all ! results onto the one you chose. ! These operations may 'FAIL', but should do so only in relatively ! uncommon cases; if they would 'FAIL' for common cases involving integer comparisons, it is best to restrict the predicates to not allow these operands. Likewise if a given comparison operator will ! always fail, independent of the operands (for floating-point modes, ! the 'ordered_comparison_operator' predicate is often useful in this ! case). If this pattern is omitted, the compiler will generate a conditional branch--for example, it may copy a constant one to the ! target and branching around an assignment of zero to the target--or ! a libcall. If the predicate for operand 1 only rejects some ! operators, it will also try reordering the operands and/or ! inverting the result value (e.g. by an exclusive OR). These possibilities could be cheaper or equivalent to the instructions ! used for the 'cstoreMODE4' pattern followed by those required to ! convert a positive result from 'STORE_FLAG_VALUE' to 1; in this case, you can and should make operand 1's predicate reject some ! operators in the 'cstoreMODE4' pattern, or remove the pattern altogether from the machine description. ! 'cbranchMODE4' Conditional branch instruction combined with a compare instruction. Operand 0 is a comparison operator. Operand 1 and operand 2 are the first and second operands of the comparison, respectively. ! Operand 3 is the 'code_label' to jump to. ! 'jump' A jump inside a function; an unconditional branch. Operand 0 is ! the 'code_label' to jump to. This pattern name is mandatory on all machines. ! 'call' Subroutine call instruction returning no value. Operand 0 is the function to call; operand 1 is the number of bytes of arguments ! pushed as a 'const_int'; operand 2 is the number of registers used as operands. On most machines, operand 2 is not actually stored into the RTL --- 24287,24403 ---- The bit-field value is sign-extended to a full word integer before it is stored in operand 0. ! This pattern is deprecated; please use `extvM' and `extvmisalignM' instead. ! `extzv' ! Like `extv' except that the bit-field value is zero-extended. ! This pattern is deprecated; please use `extzvM' and ! `extzvmisalignM' instead. ! `insv' ! Store operand 3 (which must be valid for `word_mode') into a ! bit-field in operand 0, where operand 1 specifies the width in ! bits and operand 2 the starting bit. Operand 0 may have mode ! `byte_mode' or `word_mode'; often `word_mode' is allowed only for ! registers. Operands 1 and 2 must be valid for `word_mode'. The RTL generation pass generates this instruction only with constants for operands 1 and 2 and the constant is never zero for operand 1. ! This pattern is deprecated; please use `insvM' and `insvmisalignM' instead. ! `movMODEcc' Conditionally move operand 2 or operand 3 into operand 0 according ! to the comparison in operand 1. If the comparison is true, ! operand 2 is moved into operand 0, otherwise operand 3 is moved. ! The mode of the operands being compared need not be the same as ! the operands being moved. Some machines, sparc64 for example, ! have instructions that conditionally move an integer value based ! on the floating point condition codes and vice versa. If the machine does not have conditional move instructions, do not define these patterns. ! `addMODEcc' ! Similar to `movMODEcc' but for conditional addition. Conditionally ! move operand 2 or (operands 2 + operand 3) into operand 0 ! according to the comparison in operand 1. If the comparison is ! false, operand 2 is moved into operand 0, otherwise (operand 2 + ! operand 3) is moved. ! `negMODEcc' ! Similar to `movMODEcc' but for conditional negation. Conditionally move the negation of operand 2 or the unchanged operand 3 into operand 0 according to the comparison in operand 1. If the ! comparison is true, the negation of operand 2 is moved into ! operand 0, otherwise operand 3 is moved. ! `notMODEcc' ! Similar to `negMODEcc' but for conditional complement. Conditionally move the bitwise complement of operand 2 or the unchanged operand 3 into operand 0 according to the comparison in operand 1. If the comparison is true, the complement of operand 2 is moved into operand 0, otherwise operand 3 is moved. ! `cstoreMODE4' Store zero or nonzero in operand 0 according to whether a ! comparison is true. Operand 1 is a comparison operator. Operand ! 2 and operand 3 are the first and second operand of the ! comparison, respectively. You specify the mode that operand 0 ! must have when you write the `match_operand' expression. The ! compiler automatically sees which mode you have used and supplies ! an operand of that mode. The value stored for a true condition must have 1 as its low bit, or else must be negative. Otherwise the instruction is not suitable and you should omit it from the machine description. You describe to the compiler exactly which value is stored by defining ! the macro `STORE_FLAG_VALUE' (*note Misc::). If a description cannot be found that can be used for all the possible comparison ! operators, you should pick one and use a `define_expand' to map ! all results onto the one you chose. ! These operations may `FAIL', but should do so only in relatively ! uncommon cases; if they would `FAIL' for common cases involving integer comparisons, it is best to restrict the predicates to not allow these operands. Likewise if a given comparison operator will ! always fail, independent of the operands (for floating-point ! modes, the `ordered_comparison_operator' predicate is often useful ! in this case). If this pattern is omitted, the compiler will generate a conditional branch--for example, it may copy a constant one to the ! target and branching around an assignment of zero to the ! target--or a libcall. If the predicate for operand 1 only rejects ! some operators, it will also try reordering the operands and/or ! inverting the result value (e.g. by an exclusive OR). These possibilities could be cheaper or equivalent to the instructions ! used for the `cstoreMODE4' pattern followed by those required to ! convert a positive result from `STORE_FLAG_VALUE' to 1; in this case, you can and should make operand 1's predicate reject some ! operators in the `cstoreMODE4' pattern, or remove the pattern altogether from the machine description. ! `cbranchMODE4' Conditional branch instruction combined with a compare instruction. Operand 0 is a comparison operator. Operand 1 and operand 2 are the first and second operands of the comparison, respectively. ! Operand 3 is the `code_label' to jump to. ! `jump' A jump inside a function; an unconditional branch. Operand 0 is ! the `code_label' to jump to. This pattern name is mandatory on all machines. ! `call' Subroutine call instruction returning no value. Operand 0 is the function to call; operand 1 is the number of bytes of arguments ! pushed as a `const_int'; operand 2 is the number of registers used as operands. On most machines, operand 2 is not actually stored into the RTL *************** pattern to accomplish a certain task. *** 24025,24102 **** need to put this information into the assembler code; they can put it in the RTL instead of operand 1. ! Operand 0 should be a 'mem' RTX whose address is the address of the ! function. Note, however, that this address can be a 'symbol_ref' expression even if it would not be a legitimate memory address on the target machine. If it is also not a valid argument for a call instruction, the pattern for this operation should be a ! 'define_expand' (*note Expander Definitions::) that places the address into a register and uses that register in the call instruction. ! 'call_value' Subroutine call instruction returning a value. Operand 0 is the hard register in which the value is returned. There are three more ! operands, the same as the three operands of the 'call' instruction (but with numbers increased by one). ! Subroutines that return 'BLKmode' objects use the 'call' insn. ! 'call_pop', 'call_value_pop' ! Similar to 'call' and 'call_value', except used if defined and if ! 'RETURN_POPS_ARGS' is nonzero. They should emit a 'parallel' that ! contains both the function call and a 'set' to indicate the adjustment made to the frame pointer. ! For machines where 'RETURN_POPS_ARGS' can be nonzero, the use of these patterns increases the number of functions for which the frame pointer can be eliminated, if desired. ! 'untyped_call' ! Subroutine call instruction returning a value of any type. Operand ! 0 is the function to call; operand 1 is a memory location where the ! result of calling the function is to be stored; operand 2 is a ! 'parallel' expression where each element is a 'set' expression that ! indicates the saving of a function return value into the result ! block. This instruction pattern should be defined to support ! '__builtin_apply' on machines where special instructions are needed to call a subroutine with arbitrary arguments or to save the value returned. This instruction pattern is required on machines that have multiple registers that can hold a return value (i.e. ! 'FUNCTION_VALUE_REGNO_P' is true for more than one register). ! 'return' Subroutine return instruction. This instruction pattern name should be defined only if a single instruction can do all the work of returning from a function. ! Like the 'movM' patterns, this pattern is also used after the RTL generation phase. In this case it is to support machines where ! multiple instructions are usually needed to return from a function, ! but some class of functions only requires one instruction to ! implement a return. Normally, the applicable functions are those ! which do not need to save any registers or allocate stack space. It is valid for this pattern to expand to an instruction using ! 'simple_return' if no epilogue is required. ! 'simple_return' Subroutine return instruction. This instruction pattern name should be defined only if a single instruction can do all the work of returning from a function on a path where no epilogue is ! required. This pattern is very similar to the 'return' instruction ! pattern, but it is emitted only by the shrink-wrapping optimization ! on paths where the function prologue has not been executed, and a ! function return should occur without any of the effects of the ! epilogue. Additional uses may be introduced on paths where both ! the prologue and the epilogue have executed. For such machines, the condition specified in this pattern should ! only be true when 'reload_completed' is nonzero and the function's epilogue would only be a single instruction. For machines with ! register windows, the routine 'leaf_function_p' may be used to determine if a register window push is required. Machines that have conditional return instructions should define --- 24405,24483 ---- need to put this information into the assembler code; they can put it in the RTL instead of operand 1. ! Operand 0 should be a `mem' RTX whose address is the address of the ! function. Note, however, that this address can be a `symbol_ref' expression even if it would not be a legitimate memory address on the target machine. If it is also not a valid argument for a call instruction, the pattern for this operation should be a ! `define_expand' (*note Expander Definitions::) that places the address into a register and uses that register in the call instruction. ! `call_value' Subroutine call instruction returning a value. Operand 0 is the hard register in which the value is returned. There are three more ! operands, the same as the three operands of the `call' instruction (but with numbers increased by one). ! Subroutines that return `BLKmode' objects use the `call' insn. ! `call_pop', `call_value_pop' ! Similar to `call' and `call_value', except used if defined and if ! `RETURN_POPS_ARGS' is nonzero. They should emit a `parallel' that ! contains both the function call and a `set' to indicate the adjustment made to the frame pointer. ! For machines where `RETURN_POPS_ARGS' can be nonzero, the use of these patterns increases the number of functions for which the frame pointer can be eliminated, if desired. ! `untyped_call' ! Subroutine call instruction returning a value of any type. ! Operand 0 is the function to call; operand 1 is a memory location ! where the result of calling the function is to be stored; operand ! 2 is a `parallel' expression where each element is a `set' ! expression that indicates the saving of a function return value ! into the result block. This instruction pattern should be defined to support ! `__builtin_apply' on machines where special instructions are needed to call a subroutine with arbitrary arguments or to save the value returned. This instruction pattern is required on machines that have multiple registers that can hold a return value (i.e. ! `FUNCTION_VALUE_REGNO_P' is true for more than one register). ! `return' Subroutine return instruction. This instruction pattern name should be defined only if a single instruction can do all the work of returning from a function. ! Like the `movM' patterns, this pattern is also used after the RTL generation phase. In this case it is to support machines where ! multiple instructions are usually needed to return from a ! function, but some class of functions only requires one ! instruction to implement a return. Normally, the applicable ! functions are those which do not need to save any registers or ! allocate stack space. It is valid for this pattern to expand to an instruction using ! `simple_return' if no epilogue is required. ! `simple_return' Subroutine return instruction. This instruction pattern name should be defined only if a single instruction can do all the work of returning from a function on a path where no epilogue is ! required. This pattern is very similar to the `return' ! instruction pattern, but it is emitted only by the shrink-wrapping ! optimization on paths where the function prologue has not been ! executed, and a function return should occur without any of the ! effects of the epilogue. Additional uses may be introduced on ! paths where both the prologue and the epilogue have executed. For such machines, the condition specified in this pattern should ! only be true when `reload_completed' is nonzero and the function's epilogue would only be a single instruction. For machines with ! register windows, the routine `leaf_function_p' may be used to determine if a register window push is required. Machines that have conditional return instructions should define *************** pattern to accomplish a certain task. *** 24113,24145 **** "...") where CONDITION would normally be the same condition specified on ! the named 'return' pattern. ! 'untyped_return' Untyped subroutine return instruction. This instruction pattern ! should be defined to support '__builtin_return' on machines where special instructions are needed to return a value of any type. Operand 0 is a memory location where the result of calling a ! function with '__builtin_apply' is stored; operand 1 is a ! 'parallel' expression where each element is a 'set' expression that ! indicates the restoring of a function return value from the result ! block. ! 'nop' No-op instruction. This instruction pattern name should always be ! defined to output a no-op in assembler code. '(const_int 0)' will do as an RTL pattern. ! 'indirect_jump' An instruction to jump to an address which is operand zero. This pattern name is mandatory on all machines. ! 'casesi' Instruction to jump through a dispatch table, including bounds checking. This instruction takes five operands: ! 1. The index to dispatch on, which has mode 'SImode'. 2. The lower bound for indices in the table, an integer constant. --- 24494,24526 ---- "...") where CONDITION would normally be the same condition specified on ! the named `return' pattern. ! `untyped_return' Untyped subroutine return instruction. This instruction pattern ! should be defined to support `__builtin_return' on machines where special instructions are needed to return a value of any type. Operand 0 is a memory location where the result of calling a ! function with `__builtin_apply' is stored; operand 1 is a ! `parallel' expression where each element is a `set' expression ! that indicates the restoring of a function return value from the ! result block. ! `nop' No-op instruction. This instruction pattern name should always be ! defined to output a no-op in assembler code. `(const_int 0)' will do as an RTL pattern. ! `indirect_jump' An instruction to jump to an address which is operand zero. This pattern name is mandatory on all machines. ! `casesi' Instruction to jump through a dispatch table, including bounds checking. This instruction takes five operands: ! 1. The index to dispatch on, which has mode `SImode'. 2. The lower bound for indices in the table, an integer constant. *************** pattern to accomplish a certain task. *** 24151,24215 **** 5. A label to jump to if the index has a value outside the bounds. ! The table is an 'addr_vec' or 'addr_diff_vec' inside of a ! 'jump_table_data'. The number of elements in the table is one plus ! the difference between the upper bound and the lower bound. ! 'tablejump' Instruction to jump to a variable address. This is a low-level capability which can be used to implement a dispatch table when ! there is no 'casesi' pattern. This pattern requires two operands: the address or offset, and a label which should immediately precede the jump table. If the ! macro 'CASE_VECTOR_PC_RELATIVE' evaluates to a nonzero value then ! the first operand is an offset which counts from the address of the ! table; otherwise, it is an absolute address to jump to. In either ! case, the first operand has mode 'Pmode'. ! The 'tablejump' insn is always the last insn before the jump table ! it uses. Its assembler code normally has no need to use the second ! operand, but you should incorporate it in the RTL pattern so that ! the jump optimizer will not delete the table as unreachable code. ! 'decrement_and_branch_until_zero' ! Conditional branch instruction that decrements a register and jumps ! if the register is nonzero. Operand 0 is the register to decrement ! and test; operand 1 is the label to jump to if the register is ! nonzero. *Note Looping Patterns::. This optional instruction pattern is only used by the combiner, typically for loops reversed by the loop optimizer when strength reduction is enabled. ! 'doloop_end' ! Conditional branch instruction that decrements a register and jumps ! if the register is nonzero. Operand 0 is the register to decrement ! and test; operand 1 is the label to jump to if the register is ! nonzero. *Note Looping Patterns::. This optional instruction pattern should be defined for machines with low-overhead looping instructions as the loop optimizer will try to modify suitable loops to utilize it. The target hook ! 'TARGET_CAN_USE_DOLOOP_P' controls the conditions under which low-overhead loops can be used. ! 'doloop_begin' ! Companion instruction to 'doloop_end' required for machines that need to perform some initialization, such as loading a special ! counter register. Operand 1 is the associated 'doloop_end' pattern ! and operand 0 is the register that it decrements. If initialization insns do not always need to be emitted, use a ! 'define_expand' (*note Expander Definitions::) and make it fail. ! 'canonicalize_funcptr_for_compare' Canonicalize the function pointer in operand 1 and store the result into operand 0. ! Operand 0 is always a 'reg' and has mode 'Pmode'; operand 1 may be ! a 'reg', 'mem', 'symbol_ref', 'const_int', etc and also has mode ! 'Pmode'. Canonicalization of a function pointer usually involves computing the address of the function which would be called if the function --- 24532,24597 ---- 5. A label to jump to if the index has a value outside the bounds. ! The table is an `addr_vec' or `addr_diff_vec' inside of a ! `jump_table_data'. The number of elements in the table is one ! plus the difference between the upper bound and the lower bound. ! `tablejump' Instruction to jump to a variable address. This is a low-level capability which can be used to implement a dispatch table when ! there is no `casesi' pattern. This pattern requires two operands: the address or offset, and a label which should immediately precede the jump table. If the ! macro `CASE_VECTOR_PC_RELATIVE' evaluates to a nonzero value then ! the first operand is an offset which counts from the address of ! the table; otherwise, it is an absolute address to jump to. In ! either case, the first operand has mode `Pmode'. ! The `tablejump' insn is always the last insn before the jump table ! it uses. Its assembler code normally has no need to use the ! second operand, but you should incorporate it in the RTL pattern so ! that the jump optimizer will not delete the table as unreachable ! code. ! `decrement_and_branch_until_zero' ! Conditional branch instruction that decrements a register and ! jumps if the register is nonzero. Operand 0 is the register to ! decrement and test; operand 1 is the label to jump to if the ! register is nonzero. *Note Looping Patterns::. This optional instruction pattern is only used by the combiner, typically for loops reversed by the loop optimizer when strength reduction is enabled. ! `doloop_end' ! Conditional branch instruction that decrements a register and ! jumps if the register is nonzero. Operand 0 is the register to ! decrement and test; operand 1 is the label to jump to if the ! register is nonzero. *Note Looping Patterns::. This optional instruction pattern should be defined for machines with low-overhead looping instructions as the loop optimizer will try to modify suitable loops to utilize it. The target hook ! `TARGET_CAN_USE_DOLOOP_P' controls the conditions under which low-overhead loops can be used. ! `doloop_begin' ! Companion instruction to `doloop_end' required for machines that need to perform some initialization, such as loading a special ! counter register. Operand 1 is the associated `doloop_end' ! pattern and operand 0 is the register that it decrements. If initialization insns do not always need to be emitted, use a ! `define_expand' (*note Expander Definitions::) and make it fail. ! `canonicalize_funcptr_for_compare' Canonicalize the function pointer in operand 1 and store the result into operand 0. ! Operand 0 is always a `reg' and has mode `Pmode'; operand 1 may be ! a `reg', `mem', `symbol_ref', `const_int', etc and also has mode ! `Pmode'. Canonicalization of a function pointer usually involves computing the address of the function which would be called if the function *************** pattern to accomplish a certain task. *** 24219,24255 **** can have different values but still call the same function when used in an indirect call. ! 'save_stack_block' ! 'save_stack_function' ! 'save_stack_nonlocal' ! 'restore_stack_block' ! 'restore_stack_function' ! 'restore_stack_nonlocal' Most machines save and restore the stack pointer by copying it to ! or from an object of mode 'Pmode'. Do not define these patterns on such machines. Some machines require special handling for stack pointer saves and restores. On those machines, define the patterns corresponding to ! the non-standard cases by using a 'define_expand' (*note Expander Definitions::) that produces the required insns. The three types of saves and restores are: ! 1. 'save_stack_block' saves the stack pointer at the start of a block that allocates a variable-sized object, and ! 'restore_stack_block' restores the stack pointer when the block is exited. ! 2. 'save_stack_function' and 'restore_stack_function' do a ! similar job for the outermost block of a function and are used ! when the function allocates variable-sized objects or calls ! 'alloca'. Only the epilogue uses the restored stack pointer, ! allowing a simpler save or restore sequence on some machines. ! 3. 'save_stack_nonlocal' is used in functions that contain labels branched to by nested functions. It saves the stack pointer in such a way that the inner function can use ! 'restore_stack_nonlocal' to restore the stack pointer. The compiler generates code to restore the frame and argument pointer registers, but some machines require saving and restoring additional data such as register window information --- 24601,24638 ---- can have different values but still call the same function when used in an indirect call. ! `save_stack_block' ! `save_stack_function' ! `save_stack_nonlocal' ! `restore_stack_block' ! `restore_stack_function' ! `restore_stack_nonlocal' Most machines save and restore the stack pointer by copying it to ! or from an object of mode `Pmode'. Do not define these patterns on such machines. Some machines require special handling for stack pointer saves and restores. On those machines, define the patterns corresponding to ! the non-standard cases by using a `define_expand' (*note Expander Definitions::) that produces the required insns. The three types of saves and restores are: ! 1. `save_stack_block' saves the stack pointer at the start of a block that allocates a variable-sized object, and ! `restore_stack_block' restores the stack pointer when the block is exited. ! 2. `save_stack_function' and `restore_stack_function' do a ! similar job for the outermost block of a function and are ! used when the function allocates variable-sized objects or ! calls `alloca'. Only the epilogue uses the restored stack ! pointer, allowing a simpler save or restore sequence on some ! machines. ! 3. `save_stack_nonlocal' is used in functions that contain labels branched to by nested functions. It saves the stack pointer in such a way that the inner function can use ! `restore_stack_nonlocal' to restore the stack pointer. The compiler generates code to restore the frame and argument pointer registers, but some machines require saving and restoring additional data such as register window information *************** pattern to accomplish a certain task. *** 24257,24285 **** and restore any such required data. When saving the stack pointer, operand 0 is the save area and ! operand 1 is the stack pointer. The mode used to allocate the save ! area defaults to 'Pmode' but you can override that choice by ! defining the 'STACK_SAVEAREA_MODE' macro (*note Storage Layout::). ! You must specify an integral mode, or 'VOIDmode' if no save area is ! needed for a particular type of save (either because no save is needed or because a machine-specific save area can be used). Operand 0 is the stack pointer and operand 1 is the save area for ! restore operations. If 'save_stack_block' is defined, operand 0 ! must not be 'VOIDmode' since these saves can be arbitrarily nested. ! A save area is a 'mem' that is at a constant offset from ! 'virtual_stack_vars_rtx' when the stack pointer is saved for use by ! nonlocal gotos and a 'reg' in the other two cases. ! 'allocate_stack' ! Subtract (or add if 'STACK_GROWS_DOWNWARD' is undefined) operand 1 from the stack pointer to create space for dynamically allocated data. Store the resultant pointer to this space into operand 0. If you are allocating space from the main stack, do this by emitting a ! move insn to copy 'virtual_stack_dynamic_rtx' to operand 0. If you ! are allocating the space elsewhere, generate code to copy the location of the space to operand 0. In the latter case, you must ensure this space gets freed when the corresponding space on the main stack is free. --- 24640,24668 ---- and restore any such required data. When saving the stack pointer, operand 0 is the save area and ! operand 1 is the stack pointer. The mode used to allocate the ! save area defaults to `Pmode' but you can override that choice by ! defining the `STACK_SAVEAREA_MODE' macro (*note Storage Layout::). ! You must specify an integral mode, or `VOIDmode' if no save area ! is needed for a particular type of save (either because no save is needed or because a machine-specific save area can be used). Operand 0 is the stack pointer and operand 1 is the save area for ! restore operations. If `save_stack_block' is defined, operand 0 ! must not be `VOIDmode' since these saves can be arbitrarily nested. ! A save area is a `mem' that is at a constant offset from ! `virtual_stack_vars_rtx' when the stack pointer is saved for use by ! nonlocal gotos and a `reg' in the other two cases. ! `allocate_stack' ! Subtract (or add if `STACK_GROWS_DOWNWARD' is undefined) operand 1 from the stack pointer to create space for dynamically allocated data. Store the resultant pointer to this space into operand 0. If you are allocating space from the main stack, do this by emitting a ! move insn to copy `virtual_stack_dynamic_rtx' to operand 0. If ! you are allocating the space elsewhere, generate code to copy the location of the space to operand 0. In the latter case, you must ensure this space gets freed when the corresponding space on the main stack is free. *************** pattern to accomplish a certain task. *** 24289,24295 **** probes or maintaining the back chain. Define this pattern to emit those operations in addition to updating the stack pointer. ! 'check_stack' If stack checking (*note Stack Checking::) cannot be done on your system by probing the stack, define this pattern to perform the needed check and signal an error if the stack has overflowed. The --- 24672,24678 ---- probes or maintaining the back chain. Define this pattern to emit those operations in addition to updating the stack pointer. ! `check_stack' If stack checking (*note Stack Checking::) cannot be done on your system by probing the stack, define this pattern to perform the needed check and signal an error if the stack has overflowed. The *************** pattern to accomplish a certain task. *** 24298,24311 **** platforms where this pattern is needed, you would obtain the stack limit from a global or thread-specific variable or register. ! 'probe_stack_address' If stack checking (*note Stack Checking::) can be done on your ! system by probing the stack but without the need to actually access ! it, define this pattern and signal an error if the stack has ! overflowed. The single operand is the memory address in the stack ! that needs to be probed. ! 'probe_stack' If stack checking (*note Stack Checking::) can be done on your system by probing the stack but doing it with a "store zero" instruction is not valid or optimal, define this pattern to do the --- 24681,24694 ---- platforms where this pattern is needed, you would obtain the stack limit from a global or thread-specific variable or register. ! `probe_stack_address' If stack checking (*note Stack Checking::) can be done on your ! system by probing the stack but without the need to actually ! access it, define this pattern and signal an error if the stack ! has overflowed. The single operand is the memory address in the ! stack that needs to be probed. ! `probe_stack' If stack checking (*note Stack Checking::) can be done on your system by probing the stack but doing it with a "store zero" instruction is not valid or optimal, define this pattern to do the *************** pattern to accomplish a certain task. *** 24313,24319 **** overflowed. The single operand is the memory reference in the stack that needs to be probed. ! 'nonlocal_goto' Emit code to generate a non-local goto, e.g., a jump from one function to a label in an outer function. This pattern has four arguments, each representing a value to be used in the jump. The --- 24696,24702 ---- overflowed. The single operand is the memory reference in the stack that needs to be probed. ! `nonlocal_goto' Emit code to generate a non-local goto, e.g., a jump from one function to a label in an outer function. This pattern has four arguments, each representing a value to be used in the jump. The *************** pattern to accomplish a certain task. *** 24326,24365 **** On most machines you need not define this pattern, since GCC will already generate the correct code, which is to load the frame pointer and static chain, restore the stack (using the ! 'restore_stack_nonlocal' pattern, if defined), and jump indirectly to the dispatcher. You need only define this pattern if this code will not work on your machine. ! 'nonlocal_goto_receiver' This pattern, if defined, contains code needed at the target of a nonlocal goto after the code already generated by GCC. You will ! not normally need to define this pattern. A typical reason why you ! might need this pattern is if some value, such as a pointer to a ! global table, must be restored when the frame pointer is restored. ! Note that a nonlocal goto only occurs within a unit-of-translation, ! so a global table pointer that is shared by all functions of a ! given module need not be restored. There are no arguments. ! 'exception_receiver' This pattern, if defined, contains code needed at the site of an ! exception handler that isn't needed at the site of a nonlocal goto. ! You will not normally need to define this pattern. A typical ! reason why you might need this pattern is if some value, such as a ! pointer to a global table, must be restored after control flow is ! branched to the handler of an exception. There are no arguments. ! 'builtin_setjmp_setup' This pattern, if defined, contains additional code needed to ! initialize the 'jmp_buf'. You will not normally need to define this pattern. A typical reason why you might need this pattern is if some value, such as a pointer to a global table, must be restored. Though it is preferred that the pointer value be recalculated if possible (given the address of a label for ! instance). The single argument is a pointer to the 'jmp_buf'. Note that the buffer is five words long and that the first three are normally used by the generic mechanism. ! 'builtin_setjmp_receiver' This pattern, if defined, contains code needed at the site of a built-in setjmp that isn't needed at the site of a nonlocal goto. You will not normally need to define this pattern. A typical --- 24709,24750 ---- On most machines you need not define this pattern, since GCC will already generate the correct code, which is to load the frame pointer and static chain, restore the stack (using the ! `restore_stack_nonlocal' pattern, if defined), and jump indirectly to the dispatcher. You need only define this pattern if this code will not work on your machine. ! `nonlocal_goto_receiver' This pattern, if defined, contains code needed at the target of a nonlocal goto after the code already generated by GCC. You will ! not normally need to define this pattern. A typical reason why ! you might need this pattern is if some value, such as a pointer to ! a global table, must be restored when the frame pointer is ! restored. Note that a nonlocal goto only occurs within a ! unit-of-translation, so a global table pointer that is shared by ! all functions of a given module need not be restored. There are ! no arguments. ! `exception_receiver' This pattern, if defined, contains code needed at the site of an ! exception handler that isn't needed at the site of a nonlocal ! goto. You will not normally need to define this pattern. A ! typical reason why you might need this pattern is if some value, ! such as a pointer to a global table, must be restored after ! control flow is branched to the handler of an exception. There ! are no arguments. ! `builtin_setjmp_setup' This pattern, if defined, contains additional code needed to ! initialize the `jmp_buf'. You will not normally need to define this pattern. A typical reason why you might need this pattern is if some value, such as a pointer to a global table, must be restored. Though it is preferred that the pointer value be recalculated if possible (given the address of a label for ! instance). The single argument is a pointer to the `jmp_buf'. Note that the buffer is five words long and that the first three are normally used by the generic mechanism. ! `builtin_setjmp_receiver' This pattern, if defined, contains code needed at the site of a built-in setjmp that isn't needed at the site of a nonlocal goto. You will not normally need to define this pattern. A typical *************** pattern to accomplish a certain task. *** 24369,24452 **** control; this pattern may be emitted at a small offset from that label. ! 'builtin_longjmp' This pattern, if defined, performs the entire action of the longjmp. You will not normally need to define this pattern unless ! you also define 'builtin_setjmp_setup'. The single argument is a ! pointer to the 'jmp_buf'. ! 'eh_return' ! This pattern, if defined, affects the way '__builtin_eh_return', and thence the call frame exception handling library routines, are built. It is intended to handle non-trivial actions needed along the abnormal return path. The address of the exception handler to which the function should ! return is passed as operand to this pattern. It will normally need ! to copied by the pattern to some special register or memory location. If the pattern needs to determine the location of the target call frame in order to do so, it may use ! 'EH_RETURN_STACKADJ_RTX', if defined; it will have already been assigned. If this pattern is not defined, the default action will be to ! simply copy the return address to 'EH_RETURN_HANDLER_RTX'. Either that macro or this pattern needs to be defined if call frame exception handling is to be used. ! 'prologue' This pattern, if defined, emits RTL for entry to a function. The function entry is responsible for setting up the stack frame, initializing the frame pointer register, saving callee saved registers, etc. Using a prologue pattern is generally preferred over defining ! 'TARGET_ASM_FUNCTION_PROLOGUE' to emit assembly code for the prologue. ! The 'prologue' pattern is particularly useful for targets which perform instruction scheduling. ! 'window_save' ! This pattern, if defined, emits RTL for a register window save. It ! should be defined if the target machine has register windows but ! the window events are decoupled from calls to subroutines. The ! canonical example is the SPARC architecture. ! 'epilogue' ! This pattern emits RTL for exit from a function. The function exit ! is responsible for deallocating the stack frame, restoring callee ! saved registers and emitting the return instruction. Using an epilogue pattern is generally preferred over defining ! 'TARGET_ASM_FUNCTION_EPILOGUE' to emit assembly code for the epilogue. ! The 'epilogue' pattern is particularly useful for targets which perform instruction scheduling or which have delay slots for their return instruction. ! 'sibcall_epilogue' This pattern, if defined, emits RTL for exit from a function without the final branch back to the calling function. This pattern will be emitted before any sibling call (aka tail call) sites. ! The 'sibcall_epilogue' pattern must not clobber any arguments used for parameter passing or any stack slots for arguments passed to the current function. ! 'trap' This pattern, if defined, signals an error, typically by causing some kind of signal to be raised. Among other places, it is used ! by the Java front end to signal 'invalid array index' exceptions. ! 'ctrapMM4' Conditional trap instruction. Operand 0 is a piece of RTL which performs a comparison, and operands 1 and 2 are the arms of the comparison. Operand 3 is the trap code, an integer. ! A typical 'ctrap' pattern looks like (define_insn "ctrapsi4" [(trap_if (match_operator 0 "trap_operator" --- 24754,24837 ---- control; this pattern may be emitted at a small offset from that label. ! `builtin_longjmp' This pattern, if defined, performs the entire action of the longjmp. You will not normally need to define this pattern unless ! you also define `builtin_setjmp_setup'. The single argument is a ! pointer to the `jmp_buf'. ! `eh_return' ! This pattern, if defined, affects the way `__builtin_eh_return', and thence the call frame exception handling library routines, are built. It is intended to handle non-trivial actions needed along the abnormal return path. The address of the exception handler to which the function should ! return is passed as operand to this pattern. It will normally ! need to copied by the pattern to some special register or memory location. If the pattern needs to determine the location of the target call frame in order to do so, it may use ! `EH_RETURN_STACKADJ_RTX', if defined; it will have already been assigned. If this pattern is not defined, the default action will be to ! simply copy the return address to `EH_RETURN_HANDLER_RTX'. Either that macro or this pattern needs to be defined if call frame exception handling is to be used. ! `prologue' This pattern, if defined, emits RTL for entry to a function. The function entry is responsible for setting up the stack frame, initializing the frame pointer register, saving callee saved registers, etc. Using a prologue pattern is generally preferred over defining ! `TARGET_ASM_FUNCTION_PROLOGUE' to emit assembly code for the prologue. ! The `prologue' pattern is particularly useful for targets which perform instruction scheduling. ! `window_save' ! This pattern, if defined, emits RTL for a register window save. ! It should be defined if the target machine has register windows ! but the window events are decoupled from calls to subroutines. ! The canonical example is the SPARC architecture. ! `epilogue' ! This pattern emits RTL for exit from a function. The function ! exit is responsible for deallocating the stack frame, restoring ! callee saved registers and emitting the return instruction. Using an epilogue pattern is generally preferred over defining ! `TARGET_ASM_FUNCTION_EPILOGUE' to emit assembly code for the epilogue. ! The `epilogue' pattern is particularly useful for targets which perform instruction scheduling or which have delay slots for their return instruction. ! `sibcall_epilogue' This pattern, if defined, emits RTL for exit from a function without the final branch back to the calling function. This pattern will be emitted before any sibling call (aka tail call) sites. ! The `sibcall_epilogue' pattern must not clobber any arguments used for parameter passing or any stack slots for arguments passed to the current function. ! `trap' This pattern, if defined, signals an error, typically by causing some kind of signal to be raised. Among other places, it is used ! by the Java front end to signal `invalid array index' exceptions. ! `ctrapMM4' Conditional trap instruction. Operand 0 is a piece of RTL which performs a comparison, and operands 1 and 2 are the arms of the comparison. Operand 3 is the trap code, an integer. ! A typical `ctrap' pattern looks like (define_insn "ctrapsi4" [(trap_if (match_operator 0 "trap_operator" *************** pattern to accomplish a certain task. *** 24456,24491 **** "" "...") ! 'prefetch' This pattern, if defined, emits code for a non-faulting data prefetch instruction. Operand 0 is the address of the memory to prefetch. Operand 1 is a constant 1 if the prefetch is preparing for a write to the memory address, or a constant 0 otherwise. Operand 2 is the expected degree of temporal locality of the data and is a value between 0 and 3, inclusive; 0 means that the data ! has no temporal locality, so it need not be left in the cache after ! the access; 3 means that the data has a high degree of temporal ! locality and should be left in all levels of cache possible; 1 and ! 2 mean, respectively, a low or moderate degree of temporal ! locality. Targets that do not support write prefetches or locality hints can ignore the values of operands 1 and 2. ! 'blockage' This pattern defines a pseudo insn that prevents the instruction scheduler and other passes from moving instructions and using register equivalences across the boundary defined by the blockage insn. This needs to be an UNSPEC_VOLATILE pattern or a volatile ASM. ! 'memory_barrier' If the target memory model is not fully synchronous, then this pattern should be defined to an instruction that orders both loads and stores before the instruction with respect to loads and stores after the instruction. This pattern has no operands. ! 'sync_compare_and_swapMODE' This pattern, if defined, emits code for an atomic compare-and-swap operation. Operand 1 is the memory on which the atomic operation is performed. Operand 2 is the "old" value to be compared against --- 24841,24876 ---- "" "...") ! `prefetch' This pattern, if defined, emits code for a non-faulting data prefetch instruction. Operand 0 is the address of the memory to prefetch. Operand 1 is a constant 1 if the prefetch is preparing for a write to the memory address, or a constant 0 otherwise. Operand 2 is the expected degree of temporal locality of the data and is a value between 0 and 3, inclusive; 0 means that the data ! has no temporal locality, so it need not be left in the cache ! after the access; 3 means that the data has a high degree of ! temporal locality and should be left in all levels of cache ! possible; 1 and 2 mean, respectively, a low or moderate degree of ! temporal locality. Targets that do not support write prefetches or locality hints can ignore the values of operands 1 and 2. ! `blockage' This pattern defines a pseudo insn that prevents the instruction scheduler and other passes from moving instructions and using register equivalences across the boundary defined by the blockage insn. This needs to be an UNSPEC_VOLATILE pattern or a volatile ASM. ! `memory_barrier' If the target memory model is not fully synchronous, then this pattern should be defined to an instruction that orders both loads and stores before the instruction with respect to loads and stores after the instruction. This pattern has no operands. ! `sync_compare_and_swapMODE' This pattern, if defined, emits code for an atomic compare-and-swap operation. Operand 1 is the memory on which the atomic operation is performed. Operand 2 is the "old" value to be compared against *************** pattern to accomplish a certain task. *** 24506,24533 **** For targets where the success or failure of the compare-and-swap operation is available via the status flags, it is possible to avoid a separate compare operation and issue the subsequent branch ! or store-flag operation immediately after the compare-and-swap. To ! this end, GCC will look for a 'MODE_CC' set in the output of ! 'sync_compare_and_swapMODE'; if the machine description includes ! such a set, the target should also define special 'cbranchcc4' ! and/or 'cstorecc4' instructions. GCC will then be able to take the ! destination of the 'MODE_CC' set and pass it to the 'cbranchcc4' or ! 'cstorecc4' pattern as the first operand of the comparison (the ! second will be '(const_int 0)'). For targets where the operating system may provide support for this ! operation via library calls, the 'sync_compare_and_swap_optab' may be initialized to a function with the same interface as the ! '__sync_val_compare_and_swap_N' built-in. If the entire set of __SYNC builtins are supported via library calls, the target can ! initialize all of the optabs at once with 'init_sync_libfuncs'. ! For the purposes of C++11 'std::atomic::is_lock_free', it is assumed that these library calls do _not_ use any kind of interruptable locking. ! 'sync_addMODE', 'sync_subMODE' ! 'sync_iorMODE', 'sync_andMODE' ! 'sync_xorMODE', 'sync_nandMODE' These patterns emit code for an atomic operation on memory. Operand 0 is the memory on which the atomic operation is performed. Operand 1 is the second operand to the binary operator. --- 24891,24918 ---- For targets where the success or failure of the compare-and-swap operation is available via the status flags, it is possible to avoid a separate compare operation and issue the subsequent branch ! or store-flag operation immediately after the compare-and-swap. ! To this end, GCC will look for a `MODE_CC' set in the output of ! `sync_compare_and_swapMODE'; if the machine description includes ! such a set, the target should also define special `cbranchcc4' ! and/or `cstorecc4' instructions. GCC will then be able to take ! the destination of the `MODE_CC' set and pass it to the ! `cbranchcc4' or `cstorecc4' pattern as the first operand of the ! comparison (the second will be `(const_int 0)'). For targets where the operating system may provide support for this ! operation via library calls, the `sync_compare_and_swap_optab' may be initialized to a function with the same interface as the ! `__sync_val_compare_and_swap_N' built-in. If the entire set of __SYNC builtins are supported via library calls, the target can ! initialize all of the optabs at once with `init_sync_libfuncs'. ! For the purposes of C++11 `std::atomic::is_lock_free', it is assumed that these library calls do _not_ use any kind of interruptable locking. ! `sync_addMODE', `sync_subMODE' ! `sync_iorMODE', `sync_andMODE' ! `sync_xorMODE', `sync_nandMODE' These patterns emit code for an atomic operation on memory. Operand 0 is the memory on which the atomic operation is performed. Operand 1 is the second operand to the binary operator. *************** pattern to accomplish a certain task. *** 24540,24548 **** If these patterns are not defined, the operation will be constructed from a compare-and-swap operation, if defined. ! 'sync_old_addMODE', 'sync_old_subMODE' ! 'sync_old_iorMODE', 'sync_old_andMODE' ! 'sync_old_xorMODE', 'sync_old_nandMODE' These patterns emit code for an atomic operation on memory, and return the value that the memory contained before the operation. Operand 0 is the result value, operand 1 is the memory on which the --- 24925,24933 ---- If these patterns are not defined, the operation will be constructed from a compare-and-swap operation, if defined. ! `sync_old_addMODE', `sync_old_subMODE' ! `sync_old_iorMODE', `sync_old_andMODE' ! `sync_old_xorMODE', `sync_old_nandMODE' These patterns emit code for an atomic operation on memory, and return the value that the memory contained before the operation. Operand 0 is the result value, operand 1 is the memory on which the *************** pattern to accomplish a certain task. *** 24557,24574 **** If these patterns are not defined, the operation will be constructed from a compare-and-swap operation, if defined. ! 'sync_new_addMODE', 'sync_new_subMODE' ! 'sync_new_iorMODE', 'sync_new_andMODE' ! 'sync_new_xorMODE', 'sync_new_nandMODE' ! These patterns are like their 'sync_old_OP' counterparts, except ! that they return the value that exists in the memory location after ! the operation, rather than before the operation. ! 'sync_lock_test_and_setMODE' This pattern takes two forms, based on the capabilities of the target. In either case, operand 0 is the result of the operand, ! operand 1 is the memory on which the atomic operation is performed, ! and operand 2 is the value to set in the lock. In the ideal case, this operation is an atomic exchange operation, in which the previous value in memory operand is copied into the --- 24942,24959 ---- If these patterns are not defined, the operation will be constructed from a compare-and-swap operation, if defined. ! `sync_new_addMODE', `sync_new_subMODE' ! `sync_new_iorMODE', `sync_new_andMODE' ! `sync_new_xorMODE', `sync_new_nandMODE' ! These patterns are like their `sync_old_OP' counterparts, except ! that they return the value that exists in the memory location ! after the operation, rather than before the operation. ! `sync_lock_test_and_setMODE' This pattern takes two forms, based on the capabilities of the target. In either case, operand 0 is the result of the operand, ! operand 1 is the memory on which the atomic operation is ! performed, and operand 2 is the value to set in the lock. In the ideal case, this operation is an atomic exchange operation, in which the previous value in memory operand is copied into the *************** pattern to accomplish a certain task. *** 24576,24586 **** operand. For less capable targets, any value operand that is not the ! constant 1 should be rejected with 'FAIL'. In this case the target ! may use an atomic test-and-set bit operation. The result operand ! should contain 1 if the bit was previously set and 0 if the bit was ! previously clear. The true contents of the memory operand are ! implementation defined. This pattern must issue any memory barrier instructions such that the pattern as a whole acts as an acquire barrier, that is all --- 24961,24971 ---- operand. For less capable targets, any value operand that is not the ! constant 1 should be rejected with `FAIL'. In this case the ! target may use an atomic test-and-set bit operation. The result ! operand should contain 1 if the bit was previously set and 0 if ! the bit was previously clear. The true contents of the memory ! operand are implementation defined. This pattern must issue any memory barrier instructions such that the pattern as a whole acts as an acquire barrier, that is all *************** pattern to accomplish a certain task. *** 24590,24630 **** If this pattern is not defined, the operation will be constructed from a compare-and-swap operation, if defined. ! 'sync_lock_releaseMODE' This pattern, if defined, releases a lock set by ! 'sync_lock_test_and_setMODE'. Operand 0 is the memory that contains the lock; operand 1 is the value to store in the lock. If the target doesn't implement full semantics for ! 'sync_lock_test_and_setMODE', any value operand which is not the ! constant 0 should be rejected with 'FAIL', and the true contents of ! the memory operand are implementation defined. This pattern must issue any memory barrier instructions such that the pattern as a whole acts as a release barrier, that is the lock is released only after all previous memory operations have completed. ! If this pattern is not defined, then a 'memory_barrier' pattern will be emitted, followed by a store of the value to the memory operand. ! 'atomic_compare_and_swapMODE' This pattern, if defined, emits code for an atomic compare-and-swap operation with memory model semantics. Operand 2 is the memory on which the atomic operation is performed. Operand 0 is an output operand which is set to true or false based on whether the operation succeeded. Operand 1 is an output operand which is set to the contents of the memory before the operation was attempted. ! Operand 3 is the value that is expected to be in memory. Operand 4 ! is the value to put in memory if the expected value is found there. ! Operand 5 is set to 1 if this compare and swap is to be treated as ! a weak operation. Operand 6 is the memory model to be used if the ! operation is a success. Operand 7 is the memory model to be used ! if the operation fails. ! If memory referred to in operand 2 contains the value in operand 3, ! then operand 4 is stored in memory pointed to by operand 2 and fencing based on the memory model in operand 6 is issued. If memory referred to in operand 2 does not contain the value in --- 24975,25015 ---- If this pattern is not defined, the operation will be constructed from a compare-and-swap operation, if defined. ! `sync_lock_releaseMODE' This pattern, if defined, releases a lock set by ! `sync_lock_test_and_setMODE'. Operand 0 is the memory that contains the lock; operand 1 is the value to store in the lock. If the target doesn't implement full semantics for ! `sync_lock_test_and_setMODE', any value operand which is not the ! constant 0 should be rejected with `FAIL', and the true contents ! of the memory operand are implementation defined. This pattern must issue any memory barrier instructions such that the pattern as a whole acts as a release barrier, that is the lock is released only after all previous memory operations have completed. ! If this pattern is not defined, then a `memory_barrier' pattern will be emitted, followed by a store of the value to the memory operand. ! `atomic_compare_and_swapMODE' This pattern, if defined, emits code for an atomic compare-and-swap operation with memory model semantics. Operand 2 is the memory on which the atomic operation is performed. Operand 0 is an output operand which is set to true or false based on whether the operation succeeded. Operand 1 is an output operand which is set to the contents of the memory before the operation was attempted. ! Operand 3 is the value that is expected to be in memory. Operand ! 4 is the value to put in memory if the expected value is found ! there. Operand 5 is set to 1 if this compare and swap is to be ! treated as a weak operation. Operand 6 is the memory model to be ! used if the operation is a success. Operand 7 is the memory model ! to be used if the operation fails. ! If memory referred to in operand 2 contains the value in operand ! 3, then operand 4 is stored in memory pointed to by operand 2 and fencing based on the memory model in operand 6 is issued. If memory referred to in operand 2 does not contain the value in *************** pattern to accomplish a certain task. *** 24636,24744 **** operand 5 can be ignored. Note a strong implementation must be provided. ! If this pattern is not provided, the '__atomic_compare_exchange' ! built-in functions will utilize the legacy 'sync_compare_and_swap' ! pattern with an '__ATOMIC_SEQ_CST' memory model. ! 'atomic_loadMODE' This pattern implements an atomic load operation with memory model semantics. Operand 1 is the memory address being loaded from. ! Operand 0 is the result of the load. Operand 2 is the memory model ! to be used for the load operation. ! If not present, the '__atomic_load' built-in function will either resort to a normal load with memory barriers, or a compare-and-swap operation if a normal load would not be atomic. ! 'atomic_storeMODE' This pattern implements an atomic store operation with memory model semantics. Operand 0 is the memory address being stored to. Operand 1 is the value to be written. Operand 2 is the memory model to be used for the operation. ! If not present, the '__atomic_store' built-in function will attempt ! to perform a normal store and surround it with any required memory ! fences. If the store would not be atomic, then an ! '__atomic_exchange' is attempted with the result being ignored. ! 'atomic_exchangeMODE' This pattern implements an atomic exchange operation with memory ! model semantics. Operand 1 is the memory location the operation is ! performed on. Operand 0 is an output operand which is set to the ! original value contained in the memory pointed to by operand 1. ! Operand 2 is the value to be stored. Operand 3 is the memory model ! to be used. If this pattern is not present, the built-in function ! '__atomic_exchange' will attempt to preform the operation with a compare and swap loop. ! 'atomic_addMODE', 'atomic_subMODE' ! 'atomic_orMODE', 'atomic_andMODE' ! 'atomic_xorMODE', 'atomic_nandMODE' These patterns emit code for an atomic operation on memory with ! memory model semantics. Operand 0 is the memory on which the atomic operation is performed. Operand 1 is the second operand to the binary operator. Operand 2 is the memory model to be used by the operation. If these patterns are not defined, attempts will be made to use ! legacy 'sync' patterns, or equivalent patterns which return a result. If none of these are available a compare-and-swap loop will be used. ! 'atomic_fetch_addMODE', 'atomic_fetch_subMODE' ! 'atomic_fetch_orMODE', 'atomic_fetch_andMODE' ! 'atomic_fetch_xorMODE', 'atomic_fetch_nandMODE' These patterns emit code for an atomic operation on memory with ! memory model semantics, and return the original value. Operand 0 is an output operand which contains the value of the memory location before the operation was performed. Operand 1 is the memory on which the atomic operation is performed. Operand 2 is ! the second operand to the binary operator. Operand 3 is the memory ! model to be used by the operation. If these patterns are not defined, attempts will be made to use ! legacy 'sync' patterns. If none of these are available a compare-and-swap loop will be used. ! 'atomic_add_fetchMODE', 'atomic_sub_fetchMODE' ! 'atomic_or_fetchMODE', 'atomic_and_fetchMODE' ! 'atomic_xor_fetchMODE', 'atomic_nand_fetchMODE' These patterns emit code for an atomic operation on memory with ! memory model semantics and return the result after the operation is ! performed. Operand 0 is an output operand which contains the value ! after the operation. Operand 1 is the memory on which the atomic ! operation is performed. Operand 2 is the second operand to the ! binary operator. Operand 3 is the memory model to be used by the ! operation. If these patterns are not defined, attempts will be made to use ! legacy 'sync' patterns, or equivalent patterns which return the result before the operation followed by the arithmetic operation required to produce the result. If none of these are available a compare-and-swap loop will be used. ! 'atomic_test_and_set' ! This pattern emits code for '__builtin_atomic_test_and_set'. Operand 0 is an output operand which is set to true if the previous previous contents of the byte was "set", and false otherwise. ! Operand 1 is the 'QImode' memory to be modified. Operand 2 is the memory model to be used. The specific value that defines "set" is implementation defined, and is normally based on what is performed by the native atomic test and set instruction. ! 'mem_thread_fenceMODE' This pattern emits code required to implement a thread fence with memory model semantics. Operand 0 is the memory model to be used. If this pattern is not specified, all memory models except ! '__ATOMIC_RELAXED' will result in issuing a 'sync_synchronize' barrier pattern. ! 'mem_signal_fenceMODE' This pattern emits code required to implement a signal fence with memory model semantics. Operand 0 is the memory model to be used. --- 25021,25129 ---- operand 5 can be ignored. Note a strong implementation must be provided. ! If this pattern is not provided, the `__atomic_compare_exchange' ! built-in functions will utilize the legacy `sync_compare_and_swap' ! pattern with an `__ATOMIC_SEQ_CST' memory model. ! `atomic_loadMODE' This pattern implements an atomic load operation with memory model semantics. Operand 1 is the memory address being loaded from. ! Operand 0 is the result of the load. Operand 2 is the memory ! model to be used for the load operation. ! If not present, the `__atomic_load' built-in function will either resort to a normal load with memory barriers, or a compare-and-swap operation if a normal load would not be atomic. ! `atomic_storeMODE' This pattern implements an atomic store operation with memory model semantics. Operand 0 is the memory address being stored to. Operand 1 is the value to be written. Operand 2 is the memory model to be used for the operation. ! If not present, the `__atomic_store' built-in function will ! attempt to perform a normal store and surround it with any ! required memory fences. If the store would not be atomic, then an ! `__atomic_exchange' is attempted with the result being ignored. ! `atomic_exchangeMODE' This pattern implements an atomic exchange operation with memory ! model semantics. Operand 1 is the memory location the operation ! is performed on. Operand 0 is an output operand which is set to ! the original value contained in the memory pointed to by operand ! 1. Operand 2 is the value to be stored. Operand 3 is the memory ! model to be used. If this pattern is not present, the built-in function ! `__atomic_exchange' will attempt to preform the operation with a compare and swap loop. ! `atomic_addMODE', `atomic_subMODE' ! `atomic_orMODE', `atomic_andMODE' ! `atomic_xorMODE', `atomic_nandMODE' These patterns emit code for an atomic operation on memory with ! memory model semantics. Operand 0 is the memory on which the atomic operation is performed. Operand 1 is the second operand to the binary operator. Operand 2 is the memory model to be used by the operation. If these patterns are not defined, attempts will be made to use ! legacy `sync' patterns, or equivalent patterns which return a result. If none of these are available a compare-and-swap loop will be used. ! `atomic_fetch_addMODE', `atomic_fetch_subMODE' ! `atomic_fetch_orMODE', `atomic_fetch_andMODE' ! `atomic_fetch_xorMODE', `atomic_fetch_nandMODE' These patterns emit code for an atomic operation on memory with ! memory model semantics, and return the original value. Operand 0 is an output operand which contains the value of the memory location before the operation was performed. Operand 1 is the memory on which the atomic operation is performed. Operand 2 is ! the second operand to the binary operator. Operand 3 is the ! memory model to be used by the operation. If these patterns are not defined, attempts will be made to use ! legacy `sync' patterns. If none of these are available a compare-and-swap loop will be used. ! `atomic_add_fetchMODE', `atomic_sub_fetchMODE' ! `atomic_or_fetchMODE', `atomic_and_fetchMODE' ! `atomic_xor_fetchMODE', `atomic_nand_fetchMODE' These patterns emit code for an atomic operation on memory with ! memory model semantics and return the result after the operation ! is performed. Operand 0 is an output operand which contains the ! value after the operation. Operand 1 is the memory on which the ! atomic operation is performed. Operand 2 is the second operand to ! the binary operator. Operand 3 is the memory model to be used by ! the operation. If these patterns are not defined, attempts will be made to use ! legacy `sync' patterns, or equivalent patterns which return the result before the operation followed by the arithmetic operation required to produce the result. If none of these are available a compare-and-swap loop will be used. ! `atomic_test_and_set' ! This pattern emits code for `__builtin_atomic_test_and_set'. Operand 0 is an output operand which is set to true if the previous previous contents of the byte was "set", and false otherwise. ! Operand 1 is the `QImode' memory to be modified. Operand 2 is the memory model to be used. The specific value that defines "set" is implementation defined, and is normally based on what is performed by the native atomic test and set instruction. ! `mem_thread_fenceMODE' This pattern emits code required to implement a thread fence with memory model semantics. Operand 0 is the memory model to be used. If this pattern is not specified, all memory models except ! `__ATOMIC_RELAXED' will result in issuing a `sync_synchronize' barrier pattern. ! `mem_signal_fenceMODE' This pattern emits code required to implement a signal fence with memory model semantics. Operand 0 is the memory model to be used. *************** pattern to accomplish a certain task. *** 24747,24767 **** barrier instructions. If this pattern is not specified, all memory models except ! '__ATOMIC_RELAXED' will result in issuing a 'sync_synchronize' barrier pattern. ! 'get_thread_pointerMODE' ! 'set_thread_pointerMODE' These patterns emit code that reads/sets the TLS thread pointer. Currently, these are only needed if the target needs to support the ! '__builtin_thread_pointer' and '__builtin_set_thread_pointer' builtins. The get/set patterns have a single output/input operand ! respectively, with MODE intended to be 'Pmode'. ! 'stack_protect_set' ! This pattern, if defined, moves a 'ptr_mode' value from the memory in operand 1 to the memory in operand 0 without leaving the value in a register afterward. This is to avoid leaking the value some place that an attacker might use to rewrite the stack guard slot --- 25132,25152 ---- barrier instructions. If this pattern is not specified, all memory models except ! `__ATOMIC_RELAXED' will result in issuing a `sync_synchronize' barrier pattern. ! `get_thread_pointerMODE' ! `set_thread_pointerMODE' These patterns emit code that reads/sets the TLS thread pointer. Currently, these are only needed if the target needs to support the ! `__builtin_thread_pointer' and `__builtin_set_thread_pointer' builtins. The get/set patterns have a single output/input operand ! respectively, with MODE intended to be `Pmode'. ! `stack_protect_set' ! This pattern, if defined, moves a `ptr_mode' value from the memory in operand 1 to the memory in operand 0 without leaving the value in a register afterward. This is to avoid leaking the value some place that an attacker might use to rewrite the stack guard slot *************** pattern to accomplish a certain task. *** 24770,24777 **** If this pattern is not defined, then a plain move pattern is generated. ! 'stack_protect_test' ! This pattern, if defined, compares a 'ptr_mode' value from the memory in operand 1 with the memory in operand 0 without leaving the value in a register afterward and branches to operand 2 if the values were equal. --- 25155,25162 ---- If this pattern is not defined, then a plain move pattern is generated. ! `stack_protect_test' ! This pattern, if defined, compares a `ptr_mode' value from the memory in operand 1 with the memory in operand 0 without leaving the value in a register afterward and branches to operand 2 if the values were equal. *************** pattern to accomplish a certain task. *** 24779,24791 **** If this pattern is not defined, then a plain compare pattern and conditional branch pattern is used. ! 'clear_cache' This pattern, if defined, flushes the instruction cache for a region of memory. The region is bounded to by the Pmode pointers in operand 0 inclusive and operand 1 exclusive. If this pattern is not defined, a call to the library function ! '__clear_cache' is used.  File: gccint.info, Node: Pattern Ordering, Next: Dependent Patterns, Prev: Standard Names, Up: Machine Desc --- 25164,25177 ---- If this pattern is not defined, then a plain compare pattern and conditional branch pattern is used. ! `clear_cache' This pattern, if defined, flushes the instruction cache for a region of memory. The region is bounded to by the Pmode pointers in operand 0 inclusive and operand 1 exclusive. If this pattern is not defined, a call to the library function ! `__clear_cache' is used. !  File: gccint.info, Node: Pattern Ordering, Next: Dependent Patterns, Prev: Standard Names, Up: Machine Desc *************** Therefore, more specific patterns (patte *** 24799,24814 **** things) and faster instructions (those that will produce better code when they do match) should usually go first in the description. ! In some cases the effect of ordering the patterns can be used to hide a ! pattern when it is not valid. For example, the 68000 has an instruction ! for converting a fullword to floating point and another for converting a ! byte to floating point. An instruction converting an integer to ! floating point could match either one. We put the pattern to convert ! the fullword first to make sure that one will be used rather than the ! other. (Otherwise a large integer might be generated as a single-byte ! immediate quantity, which would not work.) Instead of using this ! pattern ordering it would be possible to make the pattern for ! convert-a-byte smart enough to deal properly with any constant value.  File: gccint.info, Node: Dependent Patterns, Next: Jump Patterns, Prev: Pattern Ordering, Up: Machine Desc --- 25185,25201 ---- things) and faster instructions (those that will produce better code when they do match) should usually go first in the description. ! In some cases the effect of ordering the patterns can be used to hide ! a pattern when it is not valid. For example, the 68000 has an ! instruction for converting a fullword to floating point and another for ! converting a byte to floating point. An instruction converting an ! integer to floating point could match either one. We put the pattern ! to convert the fullword first to make sure that one will be used rather ! than the other. (Otherwise a large integer might be generated as a ! single-byte immediate quantity, which would not work.) Instead of ! using this pattern ordering it would be possible to make the pattern ! for convert-a-byte smart enough to deal properly with any constant ! value.  File: gccint.info, Node: Dependent Patterns, Next: Jump Patterns, Prev: Pattern Ordering, Up: Machine Desc *************** Constant integers do not specify a machi *** 24831,24842 **** extend a constant value could match either pattern. The pattern it actually will match is the one that appears first in the file. For correct results, this must be the one for the widest possible mode ! ('HImode', here). If the pattern matches the 'QImode' instruction, the results will be incorrect if the constant value does not actually fit that mode. ! Such instructions to extend constants are rarely generated because they ! are optimized away, but they do occasionally happen in nonoptimized compilations. If a constraint in a pattern allows a constant, the reload pass may --- 25218,25229 ---- extend a constant value could match either pattern. The pattern it actually will match is the one that appears first in the file. For correct results, this must be the one for the widest possible mode ! (`HImode', here). If the pattern matches the `QImode' instruction, the results will be incorrect if the constant value does not actually fit that mode. ! Such instructions to extend constants are rarely generated because ! they are optimized away, but they do occasionally happen in nonoptimized compilations. If a constraint in a pattern allows a constant, the reload pass may *************** File: gccint.info, Node: Jump Patterns, *** 24855,24882 **** GCC does not assume anything about how the machine realizes jumps. The machine description should define a single pattern, usually a ! 'define_expand', which expands to all the required insns. Usually, this would be a comparison insn to set the condition code and a separate branch insn testing the condition code and branching or not ! according to its value. For many machines, however, separating compares ! and branches is limiting, which is why the more flexible approach with ! one 'define_expand' is used in GCC. The machine description becomes ! clearer for architectures that have compare-and-branch instructions but ! no condition code. It also works better when different sets of ! comparison operators are supported by different kinds of conditional ! branches (e.g. integer vs. floating-point), or by conditional branches ! with respect to conditional stores. Two separate insns are always used if the machine description represents a condition code register using the legacy RTL expression ! '(cc0)', and on most machines that use a separate condition code ! register (*note Condition Code::). For machines that use '(cc0)', in fact, the set and use of the condition code must be separate and ! adjacent(1), thus allowing flags in 'cc_status' to be used (*note Condition Code::) and so that the comparison and branch insns could be ! located from each other by using the functions 'prev_cc0_setter' and ! 'next_cc0_user'. Even in this case having a single entry point for conditional branches is advantageous, because it handles equally well the case where a single --- 25242,25270 ---- GCC does not assume anything about how the machine realizes jumps. The machine description should define a single pattern, usually a ! `define_expand', which expands to all the required insns. Usually, this would be a comparison insn to set the condition code and a separate branch insn testing the condition code and branching or not ! according to its value. For many machines, however, separating ! compares and branches is limiting, which is why the more flexible ! approach with one `define_expand' is used in GCC. The machine ! description becomes clearer for architectures that have ! compare-and-branch instructions but no condition code. It also works ! better when different sets of comparison operators are supported by ! different kinds of conditional branches (e.g. integer vs. ! floating-point), or by conditional branches with respect to conditional ! stores. Two separate insns are always used if the machine description represents a condition code register using the legacy RTL expression ! `(cc0)', and on most machines that use a separate condition code ! register (*note Condition Code::). For machines that use `(cc0)', in fact, the set and use of the condition code must be separate and ! adjacent(1), thus allowing flags in `cc_status' to be used (*note Condition Code::) and so that the comparison and branch insns could be ! located from each other by using the functions `prev_cc0_setter' and ! `next_cc0_user'. Even in this case having a single entry point for conditional branches is advantageous, because it handles equally well the case where a single *************** distinct signed and unsigned flavors) as *** 24886,24894 **** case where there are distinct signed and unsigned compare instructions and only one set of conditional branch instructions as in the PowerPC. ! ---------- Footnotes ---------- ! (1) 'note' insns can separate them, though.  File: gccint.info, Node: Looping Patterns, Next: Insn Canonicalizations, Prev: Jump Patterns, Up: Machine Desc --- 25274,25282 ---- case where there are distinct signed and unsigned compare instructions and only one set of conditional branch instructions as in the PowerPC. ! ---------- Footnotes ---------- ! (1) `note' insns can separate them, though.  File: gccint.info, Node: Looping Patterns, Next: Insn Canonicalizations, Prev: Jump Patterns, Up: Machine Desc *************** File: gccint.info, Node: Looping Patter *** 24897,24903 **** =========================================== Some machines have special jump instructions that can be utilized to ! make loops more efficient. A common example is the 68000 'dbra' instruction which performs a decrement of a register and a branch if the result was greater than zero. Other machines, in particular digital signal processors (DSPs), have special block repeat instructions to --- 25285,25291 ---- =========================================== Some machines have special jump instructions that can be utilized to ! make loops more efficient. A common example is the 68000 `dbra' instruction which performs a decrement of a register and a branch if the result was greater than zero. Other machines, in particular digital signal processors (DSPs), have special block repeat instructions to *************** provide low-overhead loop support. For *** 24905,24924 **** DSPs have a block repeat instruction that loads special registers to mark the top and end of a loop and to count the number of loop iterations. This avoids the need for fetching and executing a ! 'dbra'-like instruction and avoids pipeline stalls associated with the jump. GCC has three special named patterns to support low overhead looping. ! They are 'decrement_and_branch_until_zero', 'doloop_begin', and ! 'doloop_end'. The first pattern, 'decrement_and_branch_until_zero', is not emitted during RTL generation but may be emitted during the ! instruction combination phase. This requires the assistance of the loop ! optimizer, using information collected during strength reduction, to ! reverse a loop to count down to zero. Some targets also require the ! loop optimizer to add a 'REG_NONNEG' note to indicate that the iteration ! count is always positive. This is needed if the target performs a ! signed loop termination test. For example, the 68000 uses a pattern ! similar to the following for its 'dbra' instruction: (define_insn "decrement_and_branch_until_zero" [(set (pc) --- 25293,25312 ---- DSPs have a block repeat instruction that loads special registers to mark the top and end of a loop and to count the number of loop iterations. This avoids the need for fetching and executing a ! `dbra'-like instruction and avoids pipeline stalls associated with the jump. GCC has three special named patterns to support low overhead looping. ! They are `decrement_and_branch_until_zero', `doloop_begin', and ! `doloop_end'. The first pattern, `decrement_and_branch_until_zero', is not emitted during RTL generation but may be emitted during the ! instruction combination phase. This requires the assistance of the ! loop optimizer, using information collected during strength reduction, ! to reverse a loop to count down to zero. Some targets also require the ! loop optimizer to add a `REG_NONNEG' note to indicate that the ! iteration count is always positive. This is needed if the target ! performs a signed loop termination test. For example, the 68000 uses a ! pattern similar to the following for its `dbra' instruction: (define_insn "decrement_and_branch_until_zero" [(set (pc) *************** similar to the following for its 'dbra' *** 24935,24941 **** "...") Note that since the insn is both a jump insn and has an output, it must ! deal with its own reloads, hence the 'm' constraints. Also note that since this insn is generated by the instruction combination phase combining two sequential insns together into an implicit parallel insn, the iteration counter needs to be biased by the same amount as the --- 25323,25329 ---- "...") Note that since the insn is both a jump insn and has an output, it must ! deal with its own reloads, hence the `m' constraints. Also note that since this insn is generated by the instruction combination phase combining two sequential insns together into an implicit parallel insn, the iteration counter needs to be biased by the same amount as the *************** pattern will not be matched by the combi *** 24955,24989 **** "find_reg_note (insn, REG_NONNEG, 0)" "...") ! The other two special looping patterns, 'doloop_begin' and ! 'doloop_end', are emitted by the loop optimizer for certain well-behaved ! loops with a finite number of loop iterations using information ! collected during strength reduction. ! The 'doloop_end' pattern describes the actual looping instruction (or ! the implicit looping operation) and the 'doloop_begin' pattern is an optional companion pattern that can be used for initialization needed for some low-overhead looping instructions. Note that some machines require the actual looping instruction to be emitted at the top of the loop (e.g., the TMS320C3x/C4x DSPs). Emitting the true RTL for a looping instruction at the top of the loop can cause ! problems with flow analysis. So instead, a dummy 'doloop' insn is emitted at the end of the loop. The machine dependent reorg pass checks ! for the presence of this 'doloop' insn and then searches back to the top ! of the loop, where it inserts the true looping insn (provided there are ! no instructions in the loop which would cause problems). Any additional ! labels can be emitted at this point. In addition, if the desired ! special iteration counter register was not allocated, this machine ! dependent reorg pass could emit a traditional compare and jump instruction pair. ! The essential difference between the 'decrement_and_branch_until_zero' ! and the 'doloop_end' patterns is that the loop optimizer allocates an ! additional pseudo register for the latter as an iteration counter. This ! pseudo register cannot be used within the loop (i.e., general induction ! variables cannot be derived from it), however, in many cases the loop ! induction variable may become redundant and removed by the flow pass.  File: gccint.info, Node: Insn Canonicalizations, Next: Expander Definitions, Prev: Looping Patterns, Up: Machine Desc --- 25343,25378 ---- "find_reg_note (insn, REG_NONNEG, 0)" "...") ! The other two special looping patterns, `doloop_begin' and ! `doloop_end', are emitted by the loop optimizer for certain ! well-behaved loops with a finite number of loop iterations using ! information collected during strength reduction. ! The `doloop_end' pattern describes the actual looping instruction (or ! the implicit looping operation) and the `doloop_begin' pattern is an optional companion pattern that can be used for initialization needed for some low-overhead looping instructions. Note that some machines require the actual looping instruction to be emitted at the top of the loop (e.g., the TMS320C3x/C4x DSPs). Emitting the true RTL for a looping instruction at the top of the loop can cause ! problems with flow analysis. So instead, a dummy `doloop' insn is emitted at the end of the loop. The machine dependent reorg pass checks ! for the presence of this `doloop' insn and then searches back to the ! top of the loop, where it inserts the true looping insn (provided there ! are no instructions in the loop which would cause problems). Any ! additional labels can be emitted at this point. In addition, if the ! desired special iteration counter register was not allocated, this ! machine dependent reorg pass could emit a traditional compare and jump instruction pair. ! The essential difference between the `decrement_and_branch_until_zero' ! and the `doloop_end' patterns is that the loop optimizer allocates an ! additional pseudo register for the latter as an iteration counter. ! This pseudo register cannot be used within the loop (i.e., general ! induction variables cannot be derived from it), however, in many cases ! the loop induction variable may become redundant and removed by the ! flow pass.  File: gccint.info, Node: Insn Canonicalizations, Next: Expander Definitions, Prev: Looping Patterns, Up: Machine Desc *************** number of insn patterns required. *** 25001,25044 **** In addition to algebraic simplifications, following canonicalizations are performed: ! * For commutative and comparison operators, a constant is always made ! the second operand. If a machine only supports a constant as the ! second operand, only patterns that match a constant in the second ! operand need be supplied. * For associative operators, a sequence of operators will always chain to the left; for instance, only the left operand of an ! integer 'plus' can itself be a 'plus'. 'and', 'ior', 'xor', ! 'plus', 'mult', 'smin', 'smax', 'umin', and 'umax' are associative when applied to integers, and sometimes to floating-point. ! * For these operators, if only one operand is a 'neg', 'not', 'mult', ! 'plus', or 'minus' expression, it will be the first operand. ! * In combinations of 'neg', 'mult', 'plus', and 'minus', the 'neg' operations (if any) will be moved inside the operations as far as ! possible. For instance, '(neg (mult A B))' is canonicalized as ! '(mult (neg A) B)', but '(plus (mult (neg B) C) A)' is ! canonicalized as '(minus A (mult B C))'. ! * For the 'compare' operator, a constant is always the second operand ! if the first argument is a condition code register or '(cc0)'. ! * An operand of 'neg', 'not', 'mult', 'plus', or 'minus' is made the first operand under the same conditions as above. ! * '(ltu (plus A B) B)' is converted to '(ltu (plus A B) A)'. ! Likewise with 'geu' instead of 'ltu'. ! * '(minus X (const_int N))' is converted to '(plus X (const_int -N))'. ! * Within address computations (i.e., inside 'mem'), a left shift is converted into the appropriate multiplication by a power of two. * De Morgan's Law is used to move bitwise negation inside a bitwise logical-and or logical-or operation. If this results in only one ! operand being a 'not' expression, it will be the first one. A machine that has an instruction that performs a bitwise logical-and of one operand with the bitwise negation of the other --- 25390,25434 ---- In addition to algebraic simplifications, following canonicalizations are performed: ! * For commutative and comparison operators, a constant is always ! made the second operand. If a machine only supports a constant as ! the second operand, only patterns that match a constant in the ! second operand need be supplied. * For associative operators, a sequence of operators will always chain to the left; for instance, only the left operand of an ! integer `plus' can itself be a `plus'. `and', `ior', `xor', ! `plus', `mult', `smin', `smax', `umin', and `umax' are associative when applied to integers, and sometimes to floating-point. ! * For these operators, if only one operand is a `neg', `not', ! `mult', `plus', or `minus' expression, it will be the first ! operand. ! * In combinations of `neg', `mult', `plus', and `minus', the `neg' operations (if any) will be moved inside the operations as far as ! possible. For instance, `(neg (mult A B))' is canonicalized as ! `(mult (neg A) B)', but `(plus (mult (neg B) C) A)' is ! canonicalized as `(minus A (mult B C))'. ! * For the `compare' operator, a constant is always the second operand ! if the first argument is a condition code register or `(cc0)'. ! * An operand of `neg', `not', `mult', `plus', or `minus' is made the first operand under the same conditions as above. ! * `(ltu (plus A B) B)' is converted to `(ltu (plus A B) A)'. ! Likewise with `geu' instead of `ltu'. ! * `(minus X (const_int N))' is converted to `(plus X (const_int -N))'. ! * Within address computations (i.e., inside `mem'), a left shift is converted into the appropriate multiplication by a power of two. * De Morgan's Law is used to move bitwise negation inside a bitwise logical-and or logical-or operation. If this results in only one ! operand being a `not' expression, it will be the first one. A machine that has an instruction that performs a bitwise logical-and of one operand with the bitwise negation of the other *************** are performed: *** 25064,25070 **** logically equivalent RTL expressions. * The only possible RTL expressions involving both bitwise ! exclusive-or and bitwise negation are '(xor:M X Y)' and '(not:M (xor:M X Y))'. * The sum of three items, one of which is a constant, will only --- 25454,25460 ---- logically equivalent RTL expressions. * The only possible RTL expressions involving both bitwise ! exclusive-or and bitwise negation are `(xor:M X Y)' and `(not:M (xor:M X Y))'. * The sum of three items, one of which is a constant, will only *************** are performed: *** 25072,25095 **** (plus:M (plus:M X Y) CONSTANT) ! * Equality comparisons of a group of bits (usually a single bit) with ! zero will be written using 'zero_extract' rather than the ! equivalent 'and' or 'sign_extract' operations. ! * '(sign_extend:M1 (mult:M2 (sign_extend:M2 X) (sign_extend:M2 Y)))' ! is converted to '(mult:M1 (sign_extend:M1 X) (sign_extend:M1 Y))', ! and likewise for 'zero_extend'. - * '(sign_extend:M1 (mult:M2 (ashiftrt:M2 X S) (sign_extend:M2 Y)))' - is converted to '(mult:M1 (sign_extend:M1 (ashiftrt:M2 X S)) - (sign_extend:M1 Y))', and likewise for patterns using 'zero_extend' - and 'lshiftrt'. If the second operand of 'mult' is also a shift, - then that is extended also. This transformation is only applied - when it can be proven that the original operation had sufficient - precision to prevent overflow. Further canonicalization rules are defined in the function ! 'commutative_operand_precedence' in 'gcc/rtlanal.c'.  File: gccint.info, Node: Expander Definitions, Next: Insn Splitting, Prev: Insn Canonicalizations, Up: Machine Desc --- 25462,25486 ---- (plus:M (plus:M X Y) CONSTANT) ! * Equality comparisons of a group of bits (usually a single bit) ! with zero will be written using `zero_extract' rather than the ! equivalent `and' or `sign_extract' operations. ! * `(sign_extend:M1 (mult:M2 (sign_extend:M2 X) (sign_extend:M2 Y)))' ! is converted to `(mult:M1 (sign_extend:M1 X) (sign_extend:M1 Y))', ! and likewise for `zero_extend'. ! ! * `(sign_extend:M1 (mult:M2 (ashiftrt:M2 X S) (sign_extend:M2 Y)))' ! is converted to `(mult:M1 (sign_extend:M1 (ashiftrt:M2 X S)) ! (sign_extend:M1 Y))', and likewise for patterns using ! `zero_extend' and `lshiftrt'. If the second operand of `mult' is ! also a shift, then that is extended also. This transformation is ! only applied when it can be proven that the original operation had ! sufficient precision to prevent overflow. Further canonicalization rules are defined in the function ! `commutative_operand_precedence' in `gcc/rtlanal.c'.  File: gccint.info, Node: Expander Definitions, Next: Insn Splitting, Prev: Insn Canonicalizations, Up: Machine Desc *************** File: gccint.info, Node: Expander Defin *** 25100,25129 **** On some target machines, some standard pattern names for RTL generation cannot be handled with single insn, but a sequence of RTL insns can represent them. For these target machines, you can write a ! 'define_expand' to specify how to generate the sequence of RTL. ! A 'define_expand' is an RTL expression that looks almost like a ! 'define_insn'; but, unlike the latter, a 'define_expand' is used only for RTL generation and it can produce more than one RTL insn. ! A 'define_expand' RTX has four operands: ! * The name. Each 'define_expand' must have a name, since the only use for it is to refer to it by name. * The RTL template. This is a vector of RTL expressions representing ! a sequence of separate instructions. Unlike 'define_insn', there ! is no implicit surrounding 'PARALLEL'. ! * The condition, a string containing a C expression. This expression ! is used to express how the availability of this pattern depends on ! subclasses of target machine, selected by command-line options when ! GCC is run. This is just like the condition of a 'define_insn' ! that has a standard name. Therefore, the condition (if present) ! may not depend on the data in the insn being matched, but only the ! target-machine-type flags. The compiler needs to test these ! conditions during initialization in order to learn exactly which ! named instructions are available in a particular run. * The preparation statements, a string containing zero or more C statements which are to be executed before RTL code is generated --- 25491,25520 ---- On some target machines, some standard pattern names for RTL generation cannot be handled with single insn, but a sequence of RTL insns can represent them. For these target machines, you can write a ! `define_expand' to specify how to generate the sequence of RTL. ! A `define_expand' is an RTL expression that looks almost like a ! `define_insn'; but, unlike the latter, a `define_expand' is used only for RTL generation and it can produce more than one RTL insn. ! A `define_expand' RTX has four operands: ! * The name. Each `define_expand' must have a name, since the only use for it is to refer to it by name. * The RTL template. This is a vector of RTL expressions representing ! a sequence of separate instructions. Unlike `define_insn', there ! is no implicit surrounding `PARALLEL'. ! * The condition, a string containing a C expression. This ! expression is used to express how the availability of this pattern ! depends on subclasses of target machine, selected by command-line ! options when GCC is run. This is just like the condition of a ! `define_insn' that has a standard name. Therefore, the condition ! (if present) may not depend on the data in the insn being matched, ! but only the target-machine-type flags. The compiler needs to ! test these conditions during initialization in order to learn ! exactly which named instructions are available in a particular run. * The preparation statements, a string containing zero or more C statements which are to be executed before RTL code is generated *************** for RTL generation and it can produce mo *** 25131,25144 **** Usually these statements prepare temporary registers for use as internal operands in the RTL template, but they can also generate ! RTL insns directly by calling routines such as 'emit_insn', etc. Any such insns precede the ones that come from the RTL template. ! * Optionally, a vector containing the values of attributes. *Note Insn Attributes::. ! Every RTL insn emitted by a 'define_expand' must match some ! 'define_insn' in the machine description. Otherwise, the compiler will crash when trying to generate code for the insn or trying to optimize it. --- 25522,25535 ---- Usually these statements prepare temporary registers for use as internal operands in the RTL template, but they can also generate ! RTL insns directly by calling routines such as `emit_insn', etc. Any such insns precede the ones that come from the RTL template. ! * Optionally, a vector containing the values of attributes. *Note Insn Attributes::. ! Every RTL insn emitted by a `define_expand' must match some ! `define_insn' in the machine description. Otherwise, the compiler will crash when trying to generate code for the insn or trying to optimize it. *************** also describes the operands that need to *** 25147,25197 **** is used. In particular, it gives a predicate for each operand. A true operand, which needs to be specified in order to generate RTL ! from the pattern, should be described with a 'match_operand' in its first occurrence in the RTL template. This enters information on the operand's predicate into the tables that record such things. GCC uses the information to preload the operand into a register if that is required for valid RTL code. If the operand is referred to more than ! once, subsequent references should use 'match_dup'. The RTL template may also refer to internal "operands" which are temporary registers or labels used only within the sequence made by the ! 'define_expand'. Internal operands are substituted into the RTL ! template with 'match_dup', never with 'match_operand'. The values of the internal operands are not passed in as arguments by the compiler ! when it requests use of this pattern. Instead, they are computed within ! the pattern, in the preparation statements. These statements compute ! the values and store them into the appropriate elements of 'operands' so ! that 'match_dup' can find them. There are two special macros defined for use in the preparation ! statements: 'DONE' and 'FAIL'. Use them with a following semicolon, as a statement. ! 'DONE' ! Use the 'DONE' macro to end RTL generation for the pattern. The only RTL insns resulting from the pattern on this occasion will be ! those already emitted by explicit calls to 'emit_insn' within the preparation statements; the RTL template will not be generated. ! 'FAIL' Make the pattern fail on this occasion. When a pattern fails, it means that the pattern was not truly available. The calling routines in the compiler will try other strategies for code generation using other patterns. Failure is currently supported only for binary (addition, ! multiplication, shifting, etc.) and bit-field ('extv', 'extzv', ! and 'insv') operations. ! If the preparation falls through (invokes neither 'DONE' nor 'FAIL'), ! then the 'define_expand' acts like a 'define_insn' in that the RTL template is used to generate the insn. The RTL template is not used for matching, only for generating the ! initial insn list. If the preparation statement always invokes 'DONE' ! or 'FAIL', the RTL template may be reduced to a simple list of operands, ! such as this example: (define_expand "addsi3" [(match_operand:SI 0 "register_operand" "") --- 25538,25588 ---- is used. In particular, it gives a predicate for each operand. A true operand, which needs to be specified in order to generate RTL ! from the pattern, should be described with a `match_operand' in its first occurrence in the RTL template. This enters information on the operand's predicate into the tables that record such things. GCC uses the information to preload the operand into a register if that is required for valid RTL code. If the operand is referred to more than ! once, subsequent references should use `match_dup'. The RTL template may also refer to internal "operands" which are temporary registers or labels used only within the sequence made by the ! `define_expand'. Internal operands are substituted into the RTL ! template with `match_dup', never with `match_operand'. The values of the internal operands are not passed in as arguments by the compiler ! when it requests use of this pattern. Instead, they are computed ! within the pattern, in the preparation statements. These statements ! compute the values and store them into the appropriate elements of ! `operands' so that `match_dup' can find them. There are two special macros defined for use in the preparation ! statements: `DONE' and `FAIL'. Use them with a following semicolon, as a statement. ! `DONE' ! Use the `DONE' macro to end RTL generation for the pattern. The only RTL insns resulting from the pattern on this occasion will be ! those already emitted by explicit calls to `emit_insn' within the preparation statements; the RTL template will not be generated. ! `FAIL' Make the pattern fail on this occasion. When a pattern fails, it means that the pattern was not truly available. The calling routines in the compiler will try other strategies for code generation using other patterns. Failure is currently supported only for binary (addition, ! multiplication, shifting, etc.) and bit-field (`extv', `extzv', ! and `insv') operations. ! If the preparation falls through (invokes neither `DONE' nor `FAIL'), ! then the `define_expand' acts like a `define_insn' in that the RTL template is used to generate the insn. The RTL template is not used for matching, only for generating the ! initial insn list. If the preparation statement always invokes `DONE' ! or `FAIL', the RTL template may be reduced to a simple list of ! operands, such as this example: (define_expand "addsi3" [(match_operand:SI 0 "register_operand" "") *************** such as this example: *** 25220,25235 **** FAIL; }") ! This example uses 'define_expand' so that it can generate an RTL insn for shifting when the shift-count is in the supported range of 0 to 3 but fail in other cases where machine insns aren't available. When it fails, the compiler tries another strategy using different patterns (such as, a library call). If the compiler were able to handle nontrivial condition-strings in ! patterns with names, then it would be possible to use a 'define_insn' in ! that case. Here is another case (zero-extension on the 68000) which ! makes more use of the power of 'define_expand': (define_expand "zero_extendhisi2" [(set (match_operand:SI 0 "general_operand" "") --- 25611,25626 ---- FAIL; }") ! This example uses `define_expand' so that it can generate an RTL insn for shifting when the shift-count is in the supported range of 0 to 3 but fail in other cases where machine insns aren't available. When it fails, the compiler tries another strategy using different patterns (such as, a library call). If the compiler were able to handle nontrivial condition-strings in ! patterns with names, then it would be possible to use a `define_insn' ! in that case. Here is another case (zero-extension on the 68000) which ! makes more use of the power of `define_expand': (define_expand "zero_extendhisi2" [(set (match_operand:SI 0 "general_operand" "") *************** Here two RTL insns are generated, one to *** 25246,25261 **** and the other to copy the input operand into its low half. This sequence is incorrect if the input operand refers to [the old value of] the output operand, so the preparation statement makes sure this isn't ! so. The function 'make_safe_from' copies the 'operands[1]' into a ! temporary register if it refers to 'operands[0]'. It does this by emitting another RTL insn. Finally, a third example shows the use of an internal operand. ! Zero-extension on the SPUR chip is done by 'and'-ing the result against ! a halfword mask. But this mask cannot be represented by a 'const_int' because the constant value is too large to be legitimate on this ! machine. So it must be copied into a register with 'force_reg' and then ! the register used in the 'and'. (define_expand "zero_extendhisi2" [(set (match_operand:SI 0 "register_operand" "") --- 25637,25652 ---- and the other to copy the input operand into its low half. This sequence is incorrect if the input operand refers to [the old value of] the output operand, so the preparation statement makes sure this isn't ! so. The function `make_safe_from' copies the `operands[1]' into a ! temporary register if it refers to `operands[0]'. It does this by emitting another RTL insn. Finally, a third example shows the use of an internal operand. ! Zero-extension on the SPUR chip is done by `and'-ing the result against ! a halfword mask. But this mask cannot be represented by a `const_int' because the constant value is too large to be legitimate on this ! machine. So it must be copied into a register with `force_reg' and ! then the register used in the `and'. (define_expand "zero_extendhisi2" [(set (match_operand:SI 0 "register_operand" "") *************** the register used in the 'and'. *** 25267,25276 **** "operands[2] = force_reg (SImode, GEN_INT (65535)); ") ! _Note:_ If the 'define_expand' is used to serve a standard binary or unary arithmetic operation or a bit-field operation, then the last insn ! it generates must not be a 'code_label', 'barrier' or 'note'. It must ! be an 'insn', 'jump_insn' or 'call_insn'. If you don't need a real insn at the end, emit an insn to copy the result of the operation into itself. Such an insn will generate no code, but it can avoid problems in the compiler. --- 25658,25667 ---- "operands[2] = force_reg (SImode, GEN_INT (65535)); ") ! _Note:_ If the `define_expand' is used to serve a standard binary or unary arithmetic operation or a bit-field operation, then the last insn ! it generates must not be a `code_label', `barrier' or `note'. It must ! be an `insn', `jump_insn' or `call_insn'. If you don't need a real insn at the end, emit an insn to copy the result of the operation into itself. Such an insn will generate no code, but it can avoid problems in the compiler. *************** File: gccint.info, Node: Insn Splitting *** 25281,25292 **** 16.16 Defining How to Split Instructions ======================================== ! There are two cases where you should specify how to split a pattern into ! multiple insns. On machines that have instructions requiring delay ! slots (*note Delay Slots::) or that have instructions whose output is ! not available for multiple cycles (*note Processor pipeline ! description::), the compiler phases that optimize these cases need to be ! able to move insns into one-instruction delay slots. However, some insns may generate more than one machine instruction. These insns cannot be placed into a delay slot. --- 25672,25683 ---- 16.16 Defining How to Split Instructions ======================================== ! There are two cases where you should specify how to split a pattern ! into multiple insns. On machines that have instructions requiring ! delay slots (*note Delay Slots::) or that have instructions whose ! output is not available for multiple cycles (*note Processor pipeline ! description::), the compiler phases that optimize these cases need to ! be able to move insns into one-instruction delay slots. However, some insns may generate more than one machine instruction. These insns cannot be placed into a delay slot. *************** scheduling. *** 25300,25314 **** The insn combiner phase also splits putative insns. If three insns are merged into one insn with a complex expression that cannot be matched by ! some 'define_insn' pattern, the combiner phase attempts to split the complex pattern into two insns that are recognized. Usually it can break the complex pattern into two patterns by splitting out some subexpression. However, in some other cases, such as performing an addition of a large constant in two insns on a RISC machine, the way to split the addition into two insns is machine-dependent. ! The 'define_split' definition tells the compiler how to split a complex ! insn into several simpler insns. It looks like this: (define_split [INSN-PATTERN] --- 25691,25705 ---- The insn combiner phase also splits putative insns. If three insns are merged into one insn with a complex expression that cannot be matched by ! some `define_insn' pattern, the combiner phase attempts to split the complex pattern into two insns that are recognized. Usually it can break the complex pattern into two patterns by splitting out some subexpression. However, in some other cases, such as performing an addition of a large constant in two insns on a RISC machine, the way to split the addition into two insns is machine-dependent. ! The `define_split' definition tells the compiler how to split a ! complex insn into several simpler insns. It looks like this: (define_split [INSN-PATTERN] *************** insn into several simpler insns. It loo *** 25319,25349 **** "PREPARATION-STATEMENTS") INSN-PATTERN is a pattern that needs to be split and CONDITION is the ! final condition to be tested, as in a 'define_insn'. When an insn matching INSN-PATTERN and satisfying CONDITION is found, it is replaced in the insn list with the insns given by NEW-INSN-PATTERN-1, NEW-INSN-PATTERN-2, etc. The PREPARATION-STATEMENTS are similar to those statements that are ! specified for 'define_expand' (*note Expander Definitions::) and are executed before the new RTL is generated to prepare for the generated code or emit some insns whose pattern is not fixed. Unlike those in ! 'define_expand', however, these statements must not generate any new pseudo-registers. Once reload has completed, they also must not allocate any space in the stack frame. Patterns are matched against INSN-PATTERN in two different circumstances. If an insn needs to be split for delay slot scheduling or insn scheduling, the insn is already known to be valid, which means ! that it must have been matched by some 'define_insn' and, if ! 'reload_completed' is nonzero, is known to satisfy the constraints of ! that 'define_insn'. In that case, the new insn patterns must also be ! insns that are matched by some 'define_insn' and, if 'reload_completed' is nonzero, must also satisfy the constraints of those definitions. ! As an example of this usage of 'define_split', consider the following ! example from 'a29k.md', which splits a 'sign_extend' from 'HImode' to ! 'SImode' into a pair of shift insns: (define_split [(set (match_operand:SI 0 "gen_reg_operand" "") --- 25710,25740 ---- "PREPARATION-STATEMENTS") INSN-PATTERN is a pattern that needs to be split and CONDITION is the ! final condition to be tested, as in a `define_insn'. When an insn matching INSN-PATTERN and satisfying CONDITION is found, it is replaced in the insn list with the insns given by NEW-INSN-PATTERN-1, NEW-INSN-PATTERN-2, etc. The PREPARATION-STATEMENTS are similar to those statements that are ! specified for `define_expand' (*note Expander Definitions::) and are executed before the new RTL is generated to prepare for the generated code or emit some insns whose pattern is not fixed. Unlike those in ! `define_expand', however, these statements must not generate any new pseudo-registers. Once reload has completed, they also must not allocate any space in the stack frame. Patterns are matched against INSN-PATTERN in two different circumstances. If an insn needs to be split for delay slot scheduling or insn scheduling, the insn is already known to be valid, which means ! that it must have been matched by some `define_insn' and, if ! `reload_completed' is nonzero, is known to satisfy the constraints of ! that `define_insn'. In that case, the new insn patterns must also be ! insns that are matched by some `define_insn' and, if `reload_completed' is nonzero, must also satisfy the constraints of those definitions. ! As an example of this usage of `define_split', consider the following ! example from `a29k.md', which splits a `sign_extend' from `HImode' to ! `SImode' into a pair of shift insns: (define_split [(set (match_operand:SI 0 "gen_reg_operand" "") *************** example from 'a29k.md', which splits a ' *** 25359,25376 **** { operands[1] = gen_lowpart (SImode, operands[1]); }") When the combiner phase tries to split an insn pattern, it is always ! the case that the pattern is _not_ matched by any 'define_insn'. The ! combiner pass first tries to split a single 'set' expression and then ! the same 'set' expression inside a 'parallel', but followed by a ! 'clobber' of a pseudo-reg to use as a scratch register. In these cases, ! the combiner expects exactly two new insn patterns to be generated. It ! will verify that these patterns match some 'define_insn' definitions, so ! you need not do this test in the 'define_split' (of course, there is no ! point in writing a 'define_split' that will never produce insns that ! match). ! Here is an example of this use of 'define_split', taken from ! 'rs6000.md': (define_split [(set (match_operand:SI 0 "gen_reg_operand" "") --- 25750,25767 ---- { operands[1] = gen_lowpart (SImode, operands[1]); }") When the combiner phase tries to split an insn pattern, it is always ! the case that the pattern is _not_ matched by any `define_insn'. The ! combiner pass first tries to split a single `set' expression and then ! the same `set' expression inside a `parallel', but followed by a ! `clobber' of a pseudo-reg to use as a scratch register. In these ! cases, the combiner expects exactly two new insn patterns to be ! generated. It will verify that these patterns match some `define_insn' ! definitions, so you need not do this test in the `define_split' (of ! course, there is no point in writing a `define_split' that will never ! produce insns that match). ! Here is an example of this use of `define_split', taken from ! `rs6000.md': (define_split [(set (match_operand:SI 0 "gen_reg_operand" "") *************** match). *** 25391,25400 **** operands[4] = GEN_INT (low); }") ! Here the predicate 'non_add_cint_operand' matches any 'const_int' that ! is _not_ a valid operand of a single add insn. The add with the smaller ! displacement is written so that it can be substituted into the address ! of a subsequent operation. An example that uses a scratch register, from the same file, generates an equality comparison of a register and a large constant: --- 25782,25791 ---- operands[4] = GEN_INT (low); }") ! Here the predicate `non_add_cint_operand' matches any `const_int' that ! is _not_ a valid operand of a single add insn. The add with the ! smaller displacement is written so that it can be substituted into the ! address of a subsequent operation. An example that uses a scratch register, from the same file, generates an equality comparison of a register and a large constant: *************** an equality comparison of a register and *** 25423,25431 **** operands[5] = GEN_INT (sextc); }") ! To avoid confusion, don't write a single 'define_split' that accepts ! some insns that match some 'define_insn' as well as some insns that ! don't. Instead, write two separate 'define_split' definitions, one for the insns that are valid and one for the insns that are not valid. The splitter is allowed to split jump instructions into sequence of --- 25814,25822 ---- operands[5] = GEN_INT (sextc); }") ! To avoid confusion, don't write a single `define_split' that accepts ! some insns that match some `define_insn' as well as some insns that ! don't. Instead, write two separate `define_split' definitions, one for the insns that are valid and one for the insns that are not valid. The splitter is allowed to split jump instructions into sequence of *************** instruction is always valid, as compiler *** 25438,25453 **** new jump. When new sequence contains multiple jump instructions or new labels, more assistance is needed. Splitter is required to create only unconditional jumps, or simple conditional jump instructions. ! Additionally it must attach a 'REG_BR_PROB' note to each conditional ! jump. A global variable 'split_branch_probability' holds the probability of the original branch in case it was a simple conditional jump, -1 otherwise. To simplify recomputing of edge frequencies, the ! new sequence is required to have only forward jumps to the newly created ! labels. ! For the common case where the pattern of a define_split exactly matches ! the pattern of a define_insn, use 'define_insn_and_split'. It looks ! like this: (define_insn_and_split [INSN-PATTERN] --- 25829,25844 ---- new jump. When new sequence contains multiple jump instructions or new labels, more assistance is needed. Splitter is required to create only unconditional jumps, or simple conditional jump instructions. ! Additionally it must attach a `REG_BR_PROB' note to each conditional ! jump. A global variable `split_branch_probability' holds the probability of the original branch in case it was a simple conditional jump, -1 otherwise. To simplify recomputing of edge frequencies, the ! new sequence is required to have only forward jumps to the newly ! created labels. ! For the common case where the pattern of a define_split exactly ! matches the pattern of a define_insn, use `define_insn_and_split'. It ! looks like this: (define_insn_and_split [INSN-PATTERN] *************** like this: *** 25460,25471 **** "PREPARATION-STATEMENTS" [INSN-ATTRIBUTES]) - INSN-PATTERN, CONDITION, OUTPUT-TEMPLATE, and INSN-ATTRIBUTES are used ! as in 'define_insn'. The NEW-INSN-PATTERN vector and the ! PREPARATION-STATEMENTS are used as in a 'define_split'. The ! SPLIT-CONDITION is also used as in 'define_split', with the additional ! behavior that if the condition starts with '&&', the condition used for the split will be the constructed as a logical "and" of the split condition with the insn condition. For example, from i386.md: --- 25851,25861 ---- "PREPARATION-STATEMENTS" [INSN-ATTRIBUTES]) INSN-PATTERN, CONDITION, OUTPUT-TEMPLATE, and INSN-ATTRIBUTES are used ! as in `define_insn'. The NEW-INSN-PATTERN vector and the ! PREPARATION-STATEMENTS are used as in a `define_split'. The ! SPLIT-CONDITION is also used as in `define_split', with the additional ! behavior that if the condition starts with `&&', the condition used for the split will be the constructed as a logical "and" of the split condition with the insn condition. For example, from i386.md: *************** condition with the insn condition. For *** 25482,25495 **** "" [(set_attr "type" "alu1")]) - In this case, the actual split condition will be ! 'TARGET_ZERO_EXTEND_WITH_AND && !optimize_size && reload_completed'. ! The 'define_insn_and_split' construction provides exactly the same ! functionality as two separate 'define_insn' and 'define_split' patterns. ! It exists for compactness, and as a maintenance tool to prevent having ! to ensure the two patterns' templates match.  File: gccint.info, Node: Including Patterns, Next: Peephole Definitions, Prev: Insn Splitting, Up: Machine Desc --- 25872,25884 ---- "" [(set_attr "type" "alu1")]) In this case, the actual split condition will be ! `TARGET_ZERO_EXTEND_WITH_AND && !optimize_size && reload_completed'. ! The `define_insn_and_split' construction provides exactly the same ! functionality as two separate `define_insn' and `define_split' ! patterns. It exists for compactness, and as a maintenance tool to ! prevent having to ensure the two patterns' templates match.  File: gccint.info, Node: Including Patterns, Next: Peephole Definitions, Prev: Insn Splitting, Up: Machine Desc *************** File: gccint.info, Node: Including Patt *** 25497,25504 **** 16.17 Including Patterns in Machine Descriptions. ================================================= ! The 'include' pattern tells the compiler tools where to look for ! patterns that are in files other than in the file '.md'. This is used only at build time and there is no preprocessing allowed. It looks like: --- 25886,25893 ---- 16.17 Including Patterns in Machine Descriptions. ================================================= ! The `include' pattern tells the compiler tools where to look for ! patterns that are in files other than in the file `.md'. This is used only at build time and there is no preprocessing allowed. It looks like: *************** only at build time and there is no prepr *** 25512,25521 **** (include "filestuff") - Where PATHNAME is a string that specifies the location of the file, ! specifies the include file to be in 'gcc/config/target/filestuff'. The ! directory 'gcc/config/target' is regarded as the default directory. Machine descriptions may be split up into smaller more manageable subsections and placed into subdirectories. --- 25901,25909 ---- (include "filestuff") Where PATHNAME is a string that specifies the location of the file, ! specifies the include file to be in `gcc/config/target/filestuff'. The ! directory `gcc/config/target' is regarded as the default directory. Machine descriptions may be split up into smaller more manageable subsections and placed into subdirectories. *************** subsections and placed into subdirectori *** 25525,25555 **** (include "BOGUS/filestuff") - the include file is specified to be in ! 'gcc/config/TARGET/BOGUS/filestuff'. Specifying an absolute path for the include file such as; (include "/u2/BOGUS/filestuff") - is permitted but is not encouraged. 16.17.1 RTL Generation Tool Options for Directory Search -------------------------------------------------------- ! The '-IDIR' option specifies directories to search for machine descriptions. For example: genrecog -I/p1/abc/proc1 -I/p2/abcd/pro2 target.md - Add the directory DIR to the head of the list of directories to be searched for header files. This can be used to override a system machine definition file, substituting your own version, since these directories are searched before the default machine description file ! directories. If you use more than one '-I' option, the directories are scanned in left-to-right order; the standard default directory come after. --- 25913,25940 ---- (include "BOGUS/filestuff") the include file is specified to be in ! `gcc/config/TARGET/BOGUS/filestuff'. Specifying an absolute path for the include file such as; (include "/u2/BOGUS/filestuff") is permitted but is not encouraged. 16.17.1 RTL Generation Tool Options for Directory Search -------------------------------------------------------- ! The `-IDIR' option specifies directories to search for machine descriptions. For example: genrecog -I/p1/abc/proc1 -I/p2/abcd/pro2 target.md Add the directory DIR to the head of the list of directories to be searched for header files. This can be used to override a system machine definition file, substituting your own version, since these directories are searched before the default machine description file ! directories. If you use more than one `-I' option, the directories are scanned in left-to-right order; the standard default directory come after. *************** File: gccint.info, Node: Peephole Defin *** 25559,25565 **** 16.18 Machine-Specific Peephole Optimizers ========================================== ! In addition to instruction patterns the 'md' file may contain definitions of machine-specific peephole optimizations. The combiner does not notice certain peephole optimizations when the --- 25944,25950 ---- 16.18 Machine-Specific Peephole Optimizers ========================================== ! In addition to instruction patterns the `md' file may contain definitions of machine-specific peephole optimizations. The combiner does not notice certain peephole optimizations when the *************** computed in the first one. A machine-sp *** 25570,25580 **** detect such opportunities. There are two forms of peephole definitions that may be used. The ! original 'define_peephole' is run at assembly output time to match insns ! and substitute assembly text. Use of 'define_peephole' is deprecated. ! A newer 'define_peephole2' matches insns and substitutes new insns. ! The 'peephole2' pass is run after register allocation but before scheduling, which may result in much better code for targets that do scheduling. --- 25955,25966 ---- detect such opportunities. There are two forms of peephole definitions that may be used. The ! original `define_peephole' is run at assembly output time to match ! insns and substitute assembly text. Use of `define_peephole' is ! deprecated. ! A newer `define_peephole2' matches insns and substitutes new insns. ! The `peephole2' pass is run after register allocation but before scheduling, which may result in much better code for targets that do scheduling. *************** A definition looks like this: *** 25601,25607 **** The last string operand may be omitted if you are not using any machine-specific information in this machine description. If present, ! it must obey the same rules as in a 'define_insn'. In this skeleton, INSN-PATTERN-1 and so on are patterns to match consecutive insns. The optimization applies to a sequence of insns when --- 25987,25993 ---- The last string operand may be omitted if you are not using any machine-specific information in this machine description. If present, ! it must obey the same rules as in a `define_insn'. In this skeleton, INSN-PATTERN-1 and so on are patterns to match consecutive insns. The optimization applies to a sequence of insns when *************** INSN-PATTERN-1 matches the first one, IN *** 25609,25631 **** and so on. Each of the insns matched by a peephole must also match a ! 'define_insn'. Peepholes are checked only at the last stage just before ! code generation, and only optionally. Therefore, any insn which would ! match a peephole but no 'define_insn' will cause a crash in code generation in an unoptimized compilation, or at various optimization stages. ! The operands of the insns are matched with 'match_operands', ! 'match_operator', and 'match_dup', as usual. What is not usual is that the operand numbers apply to all the insn patterns in the definition. So, you can check for identical operands in two insns by using ! 'match_operand' in one insn and 'match_dup' in the other. ! The operand constraints used in 'match_operand' patterns do not have ! any direct effect on the applicability of the peephole, but they will be ! validated afterward, so make sure your constraints are general enough to ! apply whenever the peephole matches. If the peephole matches but the ! constraints are not satisfied, the compiler will crash. It is safe to omit constraints in all the operands of the peephole; or you can write constraints which serve as a double-check on the criteria --- 25995,26017 ---- and so on. Each of the insns matched by a peephole must also match a ! `define_insn'. Peepholes are checked only at the last stage just ! before code generation, and only optionally. Therefore, any insn which ! would match a peephole but no `define_insn' will cause a crash in code generation in an unoptimized compilation, or at various optimization stages. ! The operands of the insns are matched with `match_operands', ! `match_operator', and `match_dup', as usual. What is not usual is that the operand numbers apply to all the insn patterns in the definition. So, you can check for identical operands in two insns by using ! `match_operand' in one insn and `match_dup' in the other. ! The operand constraints used in `match_operand' patterns do not have ! any direct effect on the applicability of the peephole, but they will ! be validated afterward, so make sure your constraints are general enough ! to apply whenever the peephole matches. If the peephole matches but ! the constraints are not satisfied, the compiler will crash. It is safe to omit constraints in all the operands of the peephole; or you can write constraints which serve as a double-check on the criteria *************** allocation is complete. Therefore, the *** 25643,25664 **** which operands have ended up in which kinds of registers, just by looking at the operands. ! The way to refer to the operands in CONDITION is to write 'operands[I]' ! for operand number I (as matched by '(match_operand I ...)'). Use the ! variable 'insn' to refer to the last of the insns being matched; use ! 'prev_active_insn' to find the preceding insns. When optimizing computations with intermediate results, you can use CONDITION to match only when the intermediate results are not used ! elsewhere. Use the C expression 'dead_or_set_p (INSN, OP)', where INSN is the insn in which you expect the value to be used for the last time ! (from the value of 'insn', together with use of 'prev_nonnote_insn'), ! and OP is the intermediate value (from 'operands[I]'). Applying the optimization means replacing the sequence of insns with one new insn. The TEMPLATE controls ultimate output of assembler code for this combined insn. It works exactly like the template of a ! 'define_insn'. Operand numbers in this template are the same ones used in matching the original sequence of insns. The result of a defined peephole optimizer does not need to match any --- 26029,26050 ---- which operands have ended up in which kinds of registers, just by looking at the operands. ! The way to refer to the operands in CONDITION is to write ! `operands[I]' for operand number I (as matched by `(match_operand I ! ...)'). Use the variable `insn' to refer to the last of the insns ! being matched; use `prev_active_insn' to find the preceding insns. When optimizing computations with intermediate results, you can use CONDITION to match only when the intermediate results are not used ! elsewhere. Use the C expression `dead_or_set_p (INSN, OP)', where INSN is the insn in which you expect the value to be used for the last time ! (from the value of `insn', together with use of `prev_nonnote_insn'), ! and OP is the intermediate value (from `operands[I]'). Applying the optimization means replacing the sequence of insns with one new insn. The TEMPLATE controls ultimate output of assembler code for this combined insn. It works exactly like the template of a ! `define_insn'. Operand numbers in this template are the same ones used in matching the original sequence of insns. The result of a defined peephole optimizer does not need to match any *************** into *** 25706,25718 **** fmoved sp@+,fp0 INSN-PATTERN-1 and so on look _almost_ like the second operand of ! 'define_insn'. There is one important difference: the second operand of ! 'define_insn' consists of one or more RTX's enclosed in square brackets. ! Usually, there is only one: then the same action can be written as an ! element of a 'define_peephole'. But when there are multiple actions in ! a 'define_insn', they are implicitly enclosed in a 'parallel'. Then you ! must explicitly write the 'parallel', and the square brackets within it, ! in the 'define_peephole'. Thus, if an insn pattern looks like this, (define_insn "divmodsi4" [(set (match_operand:SI 0 "general_operand" "=d") --- 26092,26105 ---- fmoved sp@+,fp0 INSN-PATTERN-1 and so on look _almost_ like the second operand of ! `define_insn'. There is one important difference: the second operand ! of `define_insn' consists of one or more RTX's enclosed in square ! brackets. Usually, there is only one: then the same action can be ! written as an element of a `define_peephole'. But when there are ! multiple actions in a `define_insn', they are implicitly enclosed in a ! `parallel'. Then you must explicitly write the `parallel', and the ! square brackets within it, in the `define_peephole'. Thus, if an insn ! pattern looks like this, (define_insn "divmodsi4" [(set (match_operand:SI 0 "general_operand" "=d") *************** File: gccint.info, Node: define_peephol *** 25742,25748 **** 16.18.2 RTL to RTL Peephole Optimizers -------------------------------------- ! The 'define_peephole2' definition tells the compiler how to substitute one sequence of instructions for another sequence, what additional scratch registers may be needed and what their lifetimes must be. --- 26129,26135 ---- 16.18.2 RTL to RTL Peephole Optimizers -------------------------------------- ! The `define_peephole2' definition tells the compiler how to substitute one sequence of instructions for another sequence, what additional scratch registers may be needed and what their lifetimes must be. *************** scratch registers may be needed and what *** 25756,25762 **** ...] "PREPARATION-STATEMENTS") ! The definition is almost identical to 'define_split' (*note Insn Splitting::) except that the pattern to match is not a single instruction, but a sequence of instructions. --- 26143,26149 ---- ...] "PREPARATION-STATEMENTS") ! The definition is almost identical to `define_split' (*note Insn Splitting::) except that the pattern to match is not a single instruction, but a sequence of instructions. *************** instruction, but a sequence of instructi *** 25764,25773 **** output template. If appropriate registers are not free, the pattern will simply not match. ! Scratch registers are requested with a 'match_scratch' pattern at the top level of the input pattern. The allocated register (initially) will be dead at the point requested within the original sequence. If the ! scratch is used at more than a single point, a 'match_dup' pattern at the top level of the input pattern marks the last position in the input sequence at which the register must be available. --- 26151,26160 ---- output template. If appropriate registers are not free, the pattern will simply not match. ! Scratch registers are requested with a `match_scratch' pattern at the top level of the input pattern. The allocated register (initially) will be dead at the point requested within the original sequence. If the ! scratch is used at more than a single point, a `match_dup' pattern at the top level of the input pattern marks the last position in the input sequence at which the register must be available. *************** sequence at which the register must be a *** 25789,25795 **** This pattern tries to split a load from its use in the hopes that we'll be able to schedule around the memory load latency. It allocates a ! single 'SImode' register of class 'GENERAL_REGS' ('"r"') that needs to be live only at the point just before the arithmetic. A real example requiring extended scratch lifetimes is harder to come --- 26176,26182 ---- This pattern tries to split a load from its use in the hopes that we'll be able to schedule around the memory load latency. It allocates a ! single `SImode' register of class `GENERAL_REGS' (`"r"') that needs to be live only at the point just before the arithmetic. A real example requiring extended scratch lifetimes is harder to come *************** by, so here's a silly made-up example: *** 25808,25816 **** (set (match_dup 3) (match_dup 4))] "") ! If we had not added the '(match_dup 4)' in the middle of the input sequence, it might have been the case that the register we chose at the ! beginning of the sequence is killed by the first or second 'set'.  File: gccint.info, Node: Insn Attributes, Next: Conditional Execution, Prev: Peephole Definitions, Up: Machine Desc --- 26195,26203 ---- (set (match_dup 3) (match_dup 4))] "") ! If we had not added the `(match_dup 4)' in the middle of the input sequence, it might have been the case that the register we chose at the ! beginning of the sequence is killed by the first or second `set'.  File: gccint.info, Node: Insn Attributes, Next: Conditional Execution, Prev: Peephole Definitions, Up: Machine Desc *************** File: gccint.info, Node: Insn Attribute *** 25819,25829 **** ============================ In addition to describing the instruction supported by the target ! machine, the 'md' file also defines a group of "attributes" and a set of values for each. Every generated insn is assigned a value for each ! attribute. One possible attribute would be the effect that the insn has ! on the machine's condition code. This attribute can then be used by ! 'NOTICE_UPDATE_CC' to track the condition codes. * Menu: --- 26206,26216 ---- ============================ In addition to describing the instruction supported by the target ! machine, the `md' file also defines a group of "attributes" and a set of values for each. Every generated insn is assigned a value for each ! attribute. One possible attribute would be the effect that the insn ! has on the machine's condition code. This attribute can then be used ! by `NOTICE_UPDATE_CC' to track the condition codes. * Menu: *************** File: gccint.info, Node: Defining Attri *** 25843,25934 **** 16.19.1 Defining Attributes and their Values -------------------------------------------- ! The 'define_attr' expression is used to define each attribute required by the target machine. It looks like: (define_attr NAME LIST-OF-VALUES DEFAULT) NAME is a string specifying the name of the attribute being defined. Some attributes are used in a special way by the rest of the compiler. ! The 'enabled' attribute can be used to conditionally enable or disable ! insn alternatives (*note Disable Insn Alternatives::). The 'predicable' ! attribute, together with a suitable 'define_cond_exec' (*note Conditional Execution::), can be used to automatically generate ! conditional variants of instruction patterns. The 'mnemonic' attribute can be used to check for the instruction mnemonic (*note Mnemonic ! Attribute::). The compiler internally uses the names 'ce_enabled' and ! 'nonce_enabled', so they should not be used elsewhere as alternative names. ! LIST-OF-VALUES is either a string that specifies a comma-separated list ! of values that can be assigned to the attribute, or a null string to ! indicate that the attribute takes numeric values. DEFAULT is an attribute expression that gives the value of this attribute for insns that match patterns whose definition does not ! include an explicit value for this attribute. *Note Attr Example::, for ! more information on the handling of defaults. *Note Constant Attributes::, for information on attributes that do not depend on any particular insn. For each defined attribute, a number of definitions are written to the ! 'insn-attr.h' file. For cases where an explicit set of values is specified for an attribute, the following are defined: ! * A '#define' is written for the symbol 'HAVE_ATTR_NAME'. ! * An enumerated class is defined for 'attr_NAME' with elements of the ! form 'UPPER-NAME_UPPER-VALUE' where the attribute name and value ! are first converted to uppercase. ! * A function 'get_attr_NAME' is defined that is passed an insn and returns the attribute value for that insn. ! For example, if the following is present in the 'md' file: (define_attr "type" "branch,fp,load,store,arith" ...) ! the following lines will be written to the file 'insn-attr.h'. #define HAVE_ATTR_type 1 enum attr_type {TYPE_BRANCH, TYPE_FP, TYPE_LOAD, TYPE_STORE, TYPE_ARITH}; extern enum attr_type get_attr_type (); ! If the attribute takes numeric values, no 'enum' type will be defined ! and the function to obtain the attribute's value will return 'int'. There are attributes which are tied to a specific meaning. These attributes are not free to use for other purposes: ! 'length' ! The 'length' attribute is used to calculate the length of emitted code chunks. This is especially important when verifying branch ! distances. *Note Insn Lengths::. ! 'enabled' ! The 'enabled' attribute can be defined to prevent certain alternatives of an insn definition from being used during code ! generation. *Note Disable Insn Alternatives::. ! 'mnemonic' ! The 'mnemonic' attribute can be defined to implement instruction ! specific checks in e.g. the pipeline description. *Note Mnemonic Attribute::. For each of these special attributes, the corresponding ! 'HAVE_ATTR_NAME' '#define' is also written when the attribute is not ! defined; in that case, it is defined as '0'. Another way of defining an attribute is to use: (define_enum_attr "ATTR" "ENUM" DEFAULT) ! This works in just the same way as 'define_attr', except that the list of values is taken from a separate enumeration called ENUM (*note ! define_enum::). This form allows you to use the same list of values for ! several attributes without having to repeat the list each time. For ! example: (define_enum "processor" [ model_a --- 26230,26321 ---- 16.19.1 Defining Attributes and their Values -------------------------------------------- ! The `define_attr' expression is used to define each attribute required by the target machine. It looks like: (define_attr NAME LIST-OF-VALUES DEFAULT) NAME is a string specifying the name of the attribute being defined. Some attributes are used in a special way by the rest of the compiler. ! The `enabled' attribute can be used to conditionally enable or disable ! insn alternatives (*note Disable Insn Alternatives::). The `predicable' ! attribute, together with a suitable `define_cond_exec' (*note Conditional Execution::), can be used to automatically generate ! conditional variants of instruction patterns. The `mnemonic' attribute can be used to check for the instruction mnemonic (*note Mnemonic ! Attribute::). The compiler internally uses the names `ce_enabled' and ! `nonce_enabled', so they should not be used elsewhere as alternative names. ! LIST-OF-VALUES is either a string that specifies a comma-separated ! list of values that can be assigned to the attribute, or a null string ! to indicate that the attribute takes numeric values. DEFAULT is an attribute expression that gives the value of this attribute for insns that match patterns whose definition does not ! include an explicit value for this attribute. *Note Attr Example::, ! for more information on the handling of defaults. *Note Constant Attributes::, for information on attributes that do not depend on any particular insn. For each defined attribute, a number of definitions are written to the ! `insn-attr.h' file. For cases where an explicit set of values is specified for an attribute, the following are defined: ! * A `#define' is written for the symbol `HAVE_ATTR_NAME'. ! * An enumerated class is defined for `attr_NAME' with elements of ! the form `UPPER-NAME_UPPER-VALUE' where the attribute name and ! value are first converted to uppercase. ! * A function `get_attr_NAME' is defined that is passed an insn and returns the attribute value for that insn. ! For example, if the following is present in the `md' file: (define_attr "type" "branch,fp,load,store,arith" ...) ! the following lines will be written to the file `insn-attr.h'. #define HAVE_ATTR_type 1 enum attr_type {TYPE_BRANCH, TYPE_FP, TYPE_LOAD, TYPE_STORE, TYPE_ARITH}; extern enum attr_type get_attr_type (); ! If the attribute takes numeric values, no `enum' type will be defined ! and the function to obtain the attribute's value will return `int'. There are attributes which are tied to a specific meaning. These attributes are not free to use for other purposes: ! `length' ! The `length' attribute is used to calculate the length of emitted code chunks. This is especially important when verifying branch ! distances. *Note Insn Lengths::. ! `enabled' ! The `enabled' attribute can be defined to prevent certain alternatives of an insn definition from being used during code ! generation. *Note Disable Insn Alternatives::. ! `mnemonic' ! The `mnemonic' attribute can be defined to implement instruction ! specific checks in e.g. the pipeline description. *Note Mnemonic Attribute::. For each of these special attributes, the corresponding ! `HAVE_ATTR_NAME' `#define' is also written when the attribute is not ! defined; in that case, it is defined as `0'. Another way of defining an attribute is to use: (define_enum_attr "ATTR" "ENUM" DEFAULT) ! This works in just the same way as `define_attr', except that the list of values is taken from a separate enumeration called ENUM (*note ! define_enum::). This form allows you to use the same list of values ! for several attributes without having to repeat the list each time. ! For example: (define_enum "processor" [ model_a *************** example: *** 25947,25955 **** (define_attr "tune" "model_a,model_b,..." (const (symbol_ref "target_tune"))) ! but without duplicating the processor list. The second example defines ! two separate C enums ('attr_arch' and 'attr_tune') whereas the first ! defines a single C enum ('processor').  File: gccint.info, Node: Expressions, Next: Tagging Insns, Prev: Defining Attributes, Up: Insn Attributes --- 26334,26342 ---- (define_attr "tune" "model_a,model_b,..." (const (symbol_ref "target_tune"))) ! but without duplicating the processor list. The second example ! defines two separate C enums (`attr_arch' and `attr_tune') whereas the ! first defines a single C enum (`processor').  File: gccint.info, Node: Expressions, Next: Tagging Insns, Prev: Defining Attributes, Up: Insn Attributes *************** RTL expressions used to define attribute *** 25961,26068 **** plus a few specific to attribute definitions, to be discussed below. Attribute value expressions must have one of the following forms: ! '(const_int I)' The integer I specifies the value of a numeric attribute. I must be non-negative. The value of a numeric attribute can be specified either with a ! 'const_int', or as an integer represented as a string in ! 'const_string', 'eq_attr' (see below), 'attr', 'symbol_ref', simple ! arithmetic expressions, and 'set_attr' overrides on specific ! instructions (*note Tagging Insns::). ! '(const_string VALUE)' ! The string VALUE specifies a constant attribute value. If VALUE is ! specified as '"*"', it means that the default value of the attribute is to be used for the insn containing this expression. ! '"*"' obviously cannot be used in the DEFAULT expression of a ! 'define_attr'. If the attribute whose value is being specified is numeric, VALUE must be a string containing a non-negative integer (normally ! 'const_int' would be used in this case). Otherwise, it must contain one of the valid values for the attribute. ! '(if_then_else TEST TRUE-VALUE FALSE-VALUE)' TEST specifies an attribute test, whose format is defined below. The value of this expression is TRUE-VALUE if TEST is true, otherwise it is FALSE-VALUE. ! '(cond [TEST1 VALUE1 ...] DEFAULT)' The first operand of this expression is a vector containing an even number of expressions and consisting of pairs of TEST and VALUE ! expressions. The value of the 'cond' expression is that of the VALUE corresponding to the first true TEST expression. If none of ! the TEST expressions are true, the value of the 'cond' expression is that of the DEFAULT expression. TEST expressions can have one of the following forms: ! '(const_int I)' This test is true if I is nonzero and false otherwise. ! '(not TEST)' ! '(ior TEST1 TEST2)' ! '(and TEST1 TEST2)' These tests are true if the indicated logical function is true. ! '(match_operand:M N PRED CONSTRAINTS)' ! This test is true if operand N of the insn whose attribute value is ! being determined has mode M (this part of the test is ignored if M ! is 'VOIDmode') and the function specified by the string PRED ! returns a nonzero value when passed operand N and mode M (this part ! of the test is ignored if PRED is the null string). The CONSTRAINTS operand is ignored and should be the null string. ! '(match_test C-EXPR)' The test is true if C expression C-EXPR is true. In non-constant attributes, C-EXPR has access to the following variables: ! INSN The rtl instruction under test. ! WHICH_ALTERNATIVE ! The 'define_insn' alternative that INSN matches. *Note Output ! Statement::. ! OPERANDS An array of INSN's rtl operands. ! C-EXPR behaves like the condition in a C 'if' statement, so there ! is no need to explicitly convert the expression into a boolean 0 or ! 1 value. For example, the following two tests are equivalent: (match_test "x & 2") (match_test "(x & 2) != 0") ! '(le ARITH1 ARITH2)' ! '(leu ARITH1 ARITH2)' ! '(lt ARITH1 ARITH2)' ! '(ltu ARITH1 ARITH2)' ! '(gt ARITH1 ARITH2)' ! '(gtu ARITH1 ARITH2)' ! '(ge ARITH1 ARITH2)' ! '(geu ARITH1 ARITH2)' ! '(ne ARITH1 ARITH2)' ! '(eq ARITH1 ARITH2)' These tests are true if the indicated comparison of the two arithmetic expressions is true. Arithmetic expressions are formed ! with 'plus', 'minus', 'mult', 'div', 'mod', 'abs', 'neg', 'and', ! 'ior', 'xor', 'not', 'ashift', 'lshiftrt', and 'ashiftrt' expressions. ! 'const_int' and 'symbol_ref' are always valid terms (*note Insn ! Lengths::,for additional forms). 'symbol_ref' is a string denoting ! a C expression that yields an 'int' when evaluated by the ! 'get_attr_...' routine. It should normally be a global variable. ! '(eq_attr NAME VALUE)' NAME is a string specifying the name of an attribute. VALUE is a string that is either a valid value for attribute NAME, ! a comma-separated list of values, or '!' followed by a value or ! list. If VALUE does not begin with a '!', this test is true if the ! value of the NAME attribute of the current insn is in the list ! specified by VALUE. If VALUE begins with a '!', this test is true if the attribute's value is _not_ in the specified list. For example, --- 26348,26457 ---- plus a few specific to attribute definitions, to be discussed below. Attribute value expressions must have one of the following forms: ! `(const_int I)' The integer I specifies the value of a numeric attribute. I must be non-negative. The value of a numeric attribute can be specified either with a ! `const_int', or as an integer represented as a string in ! `const_string', `eq_attr' (see below), `attr', `symbol_ref', ! simple arithmetic expressions, and `set_attr' overrides on ! specific instructions (*note Tagging Insns::). ! `(const_string VALUE)' ! The string VALUE specifies a constant attribute value. If VALUE ! is specified as `"*"', it means that the default value of the attribute is to be used for the insn containing this expression. ! `"*"' obviously cannot be used in the DEFAULT expression of a ! `define_attr'. If the attribute whose value is being specified is numeric, VALUE must be a string containing a non-negative integer (normally ! `const_int' would be used in this case). Otherwise, it must contain one of the valid values for the attribute. ! `(if_then_else TEST TRUE-VALUE FALSE-VALUE)' TEST specifies an attribute test, whose format is defined below. The value of this expression is TRUE-VALUE if TEST is true, otherwise it is FALSE-VALUE. ! `(cond [TEST1 VALUE1 ...] DEFAULT)' The first operand of this expression is a vector containing an even number of expressions and consisting of pairs of TEST and VALUE ! expressions. The value of the `cond' expression is that of the VALUE corresponding to the first true TEST expression. If none of ! the TEST expressions are true, the value of the `cond' expression is that of the DEFAULT expression. TEST expressions can have one of the following forms: ! `(const_int I)' This test is true if I is nonzero and false otherwise. ! `(not TEST)' ! `(ior TEST1 TEST2)' ! `(and TEST1 TEST2)' These tests are true if the indicated logical function is true. ! `(match_operand:M N PRED CONSTRAINTS)' ! This test is true if operand N of the insn whose attribute value ! is being determined has mode M (this part of the test is ignored ! if M is `VOIDmode') and the function specified by the string PRED ! returns a nonzero value when passed operand N and mode M (this ! part of the test is ignored if PRED is the null string). The CONSTRAINTS operand is ignored and should be the null string. ! `(match_test C-EXPR)' The test is true if C expression C-EXPR is true. In non-constant attributes, C-EXPR has access to the following variables: ! INSN The rtl instruction under test. ! ! WHICH_ALTERNATIVE ! The `define_insn' alternative that INSN matches. *Note ! Output Statement::. ! ! OPERANDS An array of INSN's rtl operands. ! C-EXPR behaves like the condition in a C `if' statement, so there ! is no need to explicitly convert the expression into a boolean 0 ! or 1 value. For example, the following two tests are equivalent: (match_test "x & 2") (match_test "(x & 2) != 0") ! `(le ARITH1 ARITH2)' ! `(leu ARITH1 ARITH2)' ! `(lt ARITH1 ARITH2)' ! `(ltu ARITH1 ARITH2)' ! `(gt ARITH1 ARITH2)' ! `(gtu ARITH1 ARITH2)' ! `(ge ARITH1 ARITH2)' ! `(geu ARITH1 ARITH2)' ! `(ne ARITH1 ARITH2)' ! `(eq ARITH1 ARITH2)' These tests are true if the indicated comparison of the two arithmetic expressions is true. Arithmetic expressions are formed ! with `plus', `minus', `mult', `div', `mod', `abs', `neg', `and', ! `ior', `xor', `not', `ashift', `lshiftrt', and `ashiftrt' expressions. ! `const_int' and `symbol_ref' are always valid terms (*note Insn ! Lengths::,for additional forms). `symbol_ref' is a string ! denoting a C expression that yields an `int' when evaluated by the ! `get_attr_...' routine. It should normally be a global variable. ! `(eq_attr NAME VALUE)' NAME is a string specifying the name of an attribute. VALUE is a string that is either a valid value for attribute NAME, ! a comma-separated list of values, or `!' followed by a value or ! list. If VALUE does not begin with a `!', this test is true if ! the value of the NAME attribute of the current insn is in the list ! specified by VALUE. If VALUE begins with a `!', this test is true if the attribute's value is _not_ in the specified list. For example, *************** Attribute value expressions must have on *** 26073,26080 **** (ior (eq_attr "type" "load") (eq_attr "type" "store")) ! If NAME specifies an attribute of 'alternative', it refers to the ! value of the compiler variable 'which_alternative' (*note Output Statement::) and the values must be small integers. For example, (eq_attr "alternative" "2,3") --- 26462,26469 ---- (ior (eq_attr "type" "load") (eq_attr "type" "store")) ! If NAME specifies an attribute of `alternative', it refers to the ! value of the compiler variable `which_alternative' (*note Output Statement::) and the values must be small integers. For example, (eq_attr "alternative" "2,3") *************** Attribute value expressions must have on *** 26084,26105 **** (ior (eq (symbol_ref "which_alternative") (const_int 2)) (eq (symbol_ref "which_alternative") (const_int 3))) ! Note that, for most attributes, an 'eq_attr' test is simplified in cases where the value of the attribute being tested is known for all insns matching a particular pattern. This is by far the most common case. ! '(attr_flag NAME)' ! The value of an 'attr_flag' expression is true if the flag ! specified by NAME is true for the 'insn' currently being scheduled. NAME is a string specifying one of a fixed set of flags to test. ! Test the flags 'forward' and 'backward' to determine the direction of a conditional branch. ! This example describes a conditional branch delay slot which can be ! nullified for forward branches that are taken (annul-true) or for ! backward branches which are not taken (annul-false). (define_delay (eq_attr "type" "cbranch") [(eq_attr "in_branch_delay" "true") --- 26473,26494 ---- (ior (eq (symbol_ref "which_alternative") (const_int 2)) (eq (symbol_ref "which_alternative") (const_int 3))) ! Note that, for most attributes, an `eq_attr' test is simplified in cases where the value of the attribute being tested is known for all insns matching a particular pattern. This is by far the most common case. ! `(attr_flag NAME)' ! The value of an `attr_flag' expression is true if the flag ! specified by NAME is true for the `insn' currently being scheduled. NAME is a string specifying one of a fixed set of flags to test. ! Test the flags `forward' and `backward' to determine the direction of a conditional branch. ! This example describes a conditional branch delay slot which can ! be nullified for forward branches that are taken (annul-true) or ! for backward branches which are not taken (annul-false). (define_delay (eq_attr "type" "cbranch") [(eq_attr "in_branch_delay" "true") *************** Attribute value expressions must have on *** 26108,26122 **** (and (eq_attr "in_branch_delay" "true") (attr_flag "backward"))]) ! The 'forward' and 'backward' flags are false if the current 'insn' being scheduled is not a conditional branch. ! 'attr_flag' is only used during delay slot scheduling and has no meaning to other passes of the compiler. ! '(attr NAME)' The value of another attribute is returned. This is most useful ! for numeric attributes, as 'eq_attr' and 'attr_flag' produce more efficient code for non-numeric attributes.  --- 26497,26511 ---- (and (eq_attr "in_branch_delay" "true") (attr_flag "backward"))]) ! The `forward' and `backward' flags are false if the current `insn' being scheduled is not a conditional branch. ! `attr_flag' is only used during delay slot scheduling and has no meaning to other passes of the compiler. ! `(attr NAME)' The value of another attribute is returned. This is most useful ! for numeric attributes, as `eq_attr' and `attr_flag' produce more efficient code for non-numeric attributes.  *************** File: gccint.info, Node: Tagging Insns, *** 26126,26181 **** ------------------------------------------- The value assigned to an attribute of an insn is primarily determined by ! which pattern is matched by that insn (or which 'define_peephole' ! generated it). Every 'define_insn' and 'define_peephole' can have an optional last argument to specify the values of attributes for matching ! insns. The value of any attribute not specified in a particular insn is ! set to the default value for that attribute, as specified in its ! 'define_attr'. Extensive use of default values for attributes permits the specification of the values for only one or two attributes in the definition of most insn patterns, as seen in the example in the next section. ! The optional last argument of 'define_insn' and 'define_peephole' is a vector of expressions, each of which defines the value for a single ! attribute. The most general way of assigning an attribute's value is to ! use a 'set' expression whose first operand is an 'attr' expression giving the name of the attribute being set. The second operand of the ! 'set' is an attribute expression (*note Expressions::) giving the value of the attribute. ! When the attribute value depends on the 'alternative' attribute (i.e., which is the applicable alternative in the constraint of the insn), the ! 'set_attr_alternative' expression can be used. It allows the specification of a vector of attribute expressions, one for each alternative. When the generality of arbitrary attribute expressions is not required, ! the simpler 'set_attr' expression can be used, which allows specifying a ! string giving either a single attribute value or a list of attribute values, one for each alternative. The form of each of the above specifications is shown below. In each case, NAME is a string specifying the attribute to be set. ! '(set_attr NAME VALUE-STRING)' VALUE-STRING is either a string giving the desired attribute value, or a string containing a comma-separated list giving the values for succeeding alternatives. The number of elements must match the number of alternatives in the constraint of the insn pattern. ! Note that it may be useful to specify '*' for some alternative, in which case the attribute will assume its default value for insns matching that alternative. ! '(set_attr_alternative NAME [VALUE1 VALUE2 ...])' Depending on the alternative of the insn, the value will be one of ! the specified values. This is a shorthand for using a 'cond' with ! tests on the 'alternative' attribute. ! '(set (attr NAME) VALUE)' ! The first operand of this 'set' must be the special RTL expression ! 'attr', whose sole operand is a string giving the name of the attribute being set. VALUE is the value of the attribute. The following shows three different ways of representing the same --- 26515,26570 ---- ------------------------------------------- The value assigned to an attribute of an insn is primarily determined by ! which pattern is matched by that insn (or which `define_peephole' ! generated it). Every `define_insn' and `define_peephole' can have an optional last argument to specify the values of attributes for matching ! insns. The value of any attribute not specified in a particular insn ! is set to the default value for that attribute, as specified in its ! `define_attr'. Extensive use of default values for attributes permits the specification of the values for only one or two attributes in the definition of most insn patterns, as seen in the example in the next section. ! The optional last argument of `define_insn' and `define_peephole' is a vector of expressions, each of which defines the value for a single ! attribute. The most general way of assigning an attribute's value is ! to use a `set' expression whose first operand is an `attr' expression giving the name of the attribute being set. The second operand of the ! `set' is an attribute expression (*note Expressions::) giving the value of the attribute. ! When the attribute value depends on the `alternative' attribute (i.e., which is the applicable alternative in the constraint of the insn), the ! `set_attr_alternative' expression can be used. It allows the specification of a vector of attribute expressions, one for each alternative. When the generality of arbitrary attribute expressions is not required, ! the simpler `set_attr' expression can be used, which allows specifying ! a string giving either a single attribute value or a list of attribute values, one for each alternative. The form of each of the above specifications is shown below. In each case, NAME is a string specifying the attribute to be set. ! `(set_attr NAME VALUE-STRING)' VALUE-STRING is either a string giving the desired attribute value, or a string containing a comma-separated list giving the values for succeeding alternatives. The number of elements must match the number of alternatives in the constraint of the insn pattern. ! Note that it may be useful to specify `*' for some alternative, in which case the attribute will assume its default value for insns matching that alternative. ! `(set_attr_alternative NAME [VALUE1 VALUE2 ...])' Depending on the alternative of the insn, the value will be one of ! the specified values. This is a shorthand for using a `cond' with ! tests on the `alternative' attribute. ! `(set (attr NAME) VALUE)' ! The first operand of this `set' must be the special RTL expression ! `attr', whose sole operand is a string giving the name of the attribute being set. VALUE is the value of the attribute. The following shows three different ways of representing the same *************** attribute value specification: *** 26192,26216 **** (eq_attr "alternative" "2") (const_string "store")] (const_string "arith"))) ! The 'define_asm_attributes' expression provides a mechanism to specify ! the attributes assigned to insns produced from an 'asm' statement. It has the form: (define_asm_attributes [ATTR-SETS]) ! where ATTR-SETS is specified the same as for both the 'define_insn' and ! the 'define_peephole' expressions. These values will typically be the "worst case" attribute values. For example, they might indicate that the condition code will be clobbered. ! A specification for a 'length' attribute is handled specially. The way ! to compute the length of an 'asm' insn is to multiply the length ! specified in the expression 'define_asm_attributes' by the number of ! machine instructions specified in the 'asm' statement, determined by counting the number of semicolons and newlines in the string. ! Therefore, the value of the 'length' attribute specified in a ! 'define_asm_attributes' should be the maximum possible length of a single machine instruction.  --- 26581,26605 ---- (eq_attr "alternative" "2") (const_string "store")] (const_string "arith"))) ! The `define_asm_attributes' expression provides a mechanism to specify ! the attributes assigned to insns produced from an `asm' statement. It has the form: (define_asm_attributes [ATTR-SETS]) ! where ATTR-SETS is specified the same as for both the `define_insn' and ! the `define_peephole' expressions. These values will typically be the "worst case" attribute values. For example, they might indicate that the condition code will be clobbered. ! A specification for a `length' attribute is handled specially. The ! way to compute the length of an `asm' insn is to multiply the length ! specified in the expression `define_asm_attributes' by the number of ! machine instructions specified in the `asm' statement, determined by counting the number of semicolons and newlines in the string. ! Therefore, the value of the `length' attribute specified in a ! `define_asm_attributes' should be the maximum possible length of a single machine instruction.  *************** File: gccint.info, Node: Attr Example, *** 26221,26227 **** The judicious use of defaulting is important in the efficient use of insn attributes. Typically, insns are divided into "types" and an ! attribute, customarily called 'type', is used to represent this value. This attribute is normally used only to define the default value for other attributes. An example will clarify this usage. --- 26610,26616 ---- The judicious use of defaulting is important in the efficient use of insn attributes. Typically, insns are divided into "types" and an ! attribute, customarily called `type', is used to represent this value. This attribute is normally used only to define the default value for other attributes. An example will clarify this usage. *************** operations, floating point operations, a *** 26232,26243 **** Here we will concern ourselves with determining the effect of an insn on the condition code and will limit ourselves to the following possible ! effects: The condition code can be set unpredictably (clobbered), not be ! changed, be set to agree with the results of the operation, or only changed if the item previously set into the condition code has been modified. ! Here is part of a sample 'md' file for such a machine: (define_attr "type" "load,store,arith,fp,branch" (const_string "arith")) --- 26621,26632 ---- Here we will concern ourselves with determining the effect of an insn on the condition code and will limit ourselves to the following possible ! effects: The condition code can be set unpredictably (clobbered), not ! be changed, be set to agree with the results of the operation, or only changed if the item previously set into the condition code has been modified. ! Here is part of a sample `md' file for such a machine: (define_attr "type" "load,store,arith,fp,branch" (const_string "arith")) *************** File: gccint.info, Node: Insn Lengths, *** 26275,26325 **** For many machines, multiple types of branch instructions are provided, each for different length branch displacements. In most cases, the ! assembler will choose the correct instruction to use. However, when the ! assembler cannot do so, GCC can when a special attribute, the 'length' ! attribute, is defined. This attribute must be defined to have numeric ! values by specifying a null string in its 'define_attr'. ! In the case of the 'length' attribute, two additional forms of arithmetic terms are allowed in test expressions: ! '(match_dup N)' This refers to the address of operand N of the current insn, which ! must be a 'label_ref'. ! '(pc)' For non-branch instructions and backward branch instructions, this refers to the address of the current insn. But for forward branch instructions, this refers to the address of the next insn, because the length of the current insn is to be computed. For normal insns, the length will be determined by value of the ! 'length' attribute. In the case of 'addr_vec' and 'addr_diff_vec' insn patterns, the length is computed as the number of vectors multiplied by the size of each vector. Lengths are measured in addressable storage units (bytes). ! Note that it is possible to call functions via the 'symbol_ref' mechanism to compute the length of an insn. However, if you use this mechanism you must provide dummy clauses to express the maximum length ! without using the function call. You can an example of this in the 'pa' ! machine description for the 'call_symref' pattern. The following macros can be used to refine the length computation: ! 'ADJUST_INSN_LENGTH (INSN, LENGTH)' If defined, modifies the length assigned to instruction INSN as a function of the context in which it is used. LENGTH is an lvalue that contains the initially computed length of the insn and should be updated with the correct length of the insn. This macro will normally not be required. A case in which it is ! required is the ROMP. On this machine, the size of an 'addr_vec' insn must be increased by two to compensate for the fact that alignment may be required. ! The routine that returns 'get_attr_length' (the value of the 'length' attribute) can be used by the output routine to determine the form of the branch instruction to be written, as the example below illustrates. --- 26664,26714 ---- For many machines, multiple types of branch instructions are provided, each for different length branch displacements. In most cases, the ! assembler will choose the correct instruction to use. However, when ! the assembler cannot do so, GCC can when a special attribute, the ! `length' attribute, is defined. This attribute must be defined to have ! numeric values by specifying a null string in its `define_attr'. ! In the case of the `length' attribute, two additional forms of arithmetic terms are allowed in test expressions: ! `(match_dup N)' This refers to the address of operand N of the current insn, which ! must be a `label_ref'. ! `(pc)' For non-branch instructions and backward branch instructions, this refers to the address of the current insn. But for forward branch instructions, this refers to the address of the next insn, because the length of the current insn is to be computed. For normal insns, the length will be determined by value of the ! `length' attribute. In the case of `addr_vec' and `addr_diff_vec' insn patterns, the length is computed as the number of vectors multiplied by the size of each vector. Lengths are measured in addressable storage units (bytes). ! Note that it is possible to call functions via the `symbol_ref' mechanism to compute the length of an insn. However, if you use this mechanism you must provide dummy clauses to express the maximum length ! without using the function call. You can an example of this in the ! `pa' machine description for the `call_symref' pattern. The following macros can be used to refine the length computation: ! `ADJUST_INSN_LENGTH (INSN, LENGTH)' If defined, modifies the length assigned to instruction INSN as a function of the context in which it is used. LENGTH is an lvalue that contains the initially computed length of the insn and should be updated with the correct length of the insn. This macro will normally not be required. A case in which it is ! required is the ROMP. On this machine, the size of an `addr_vec' insn must be increased by two to compensate for the fact that alignment may be required. ! The routine that returns `get_attr_length' (the value of the `length' attribute) can be used by the output routine to determine the form of the branch instruction to be written, as the example below illustrates. *************** the branch instruction to be written, as *** 26327,26334 **** consider the IBM 360. If we adopt the convention that a register will be set to the starting address of a function, we can jump to labels within 4k of the start using a four-byte instruction. Otherwise, we ! need a six-byte sequence to load the address from memory and then branch ! to it. On such a machine, a pattern for a branch instruction might be specified as follows: --- 26716,26723 ---- consider the IBM 360. If we adopt the convention that a register will be set to the starting address of a function, we can jump to labels within 4k of the start using a four-byte instruction. Otherwise, we ! need a six-byte sequence to load the address from memory and then ! branch to it. On such a machine, a pattern for a branch instruction might be specified as follows: *************** File: gccint.info, Node: Constant Attri *** 26352,26359 **** 16.19.6 Constant Attributes --------------------------- ! A special form of 'define_attr', where the expression for the default ! value is a 'const' expression, indicates an attribute that is constant for a given run of the compiler. Constant attributes may be used to specify which variety of processor is used. For example, --- 26741,26748 ---- 16.19.6 Constant Attributes --------------------------- ! A special form of `define_attr', where the expression for the default ! value is a `const' expression, indicates an attribute that is constant for a given run of the compiler. Constant attributes may be used to specify which variety of processor is used. For example, *************** specify which variety of processor is us *** 26371,26379 **** The routine generated for constant attributes has no parameters as it does not depend on any particular insn. RTL expressions used to define ! the value of a constant attribute may use the 'symbol_ref' form, but may ! not use either the 'match_operand' form or 'eq_attr' forms involving ! insn attributes.  File: gccint.info, Node: Mnemonic Attribute, Next: Delay Slots, Prev: Constant Attributes, Up: Insn Attributes --- 26760,26768 ---- The routine generated for constant attributes has no parameters as it does not depend on any particular insn. RTL expressions used to define ! the value of a constant attribute may use the `symbol_ref' form, but ! may not use either the `match_operand' form or `eq_attr' forms ! involving insn attributes.  File: gccint.info, Node: Mnemonic Attribute, Next: Delay Slots, Prev: Constant Attributes, Up: Insn Attributes *************** File: gccint.info, Node: Mnemonic Attri *** 26381,26408 **** 16.19.7 Mnemonic Attribute -------------------------- ! The 'mnemonic' attribute is a string type attribute holding the ! instruction mnemonic for an insn alternative. The attribute values will ! automatically be generated by the machine description parser if there is ! an attribute definition in the md file: (define_attr "mnemonic" "unknown" (const_string "unknown")) The default value can be freely chosen as long as it does not collide ! with any of the instruction mnemonics. This value will be used whenever ! the machine description parser is not able to determine the mnemonic ! string. This might be the case for output templates containing more ! than a single instruction as in '"mvcle\t%0,%1,0\;jo\t.-4"'. ! The 'mnemonic' attribute set is not generated automatically if the instruction string is generated via C code. ! An existing 'mnemonic' attribute set in an insn definition will not be overriden by the md file parser. That way it is possible to manually set the instruction mnemonics for the cases where the md file parser fails to determine it automatically. ! The 'mnemonic' attribute is useful for dealing with instruction specific properties in the pipeline description without defining additional insn attributes. --- 26770,26798 ---- 16.19.7 Mnemonic Attribute -------------------------- ! The `mnemonic' attribute is a string type attribute holding the ! instruction mnemonic for an insn alternative. The attribute values ! will automatically be generated by the machine description parser if ! there is an attribute definition in the md file: (define_attr "mnemonic" "unknown" (const_string "unknown")) The default value can be freely chosen as long as it does not collide ! with any of the instruction mnemonics. This value will be used ! whenever the machine description parser is not able to determine the ! mnemonic string. This might be the case for output templates ! containing more than a single instruction as in ! `"mvcle\t%0,%1,0\;jo\t.-4"'. ! The `mnemonic' attribute set is not generated automatically if the instruction string is generated via C code. ! An existing `mnemonic' attribute set in an insn definition will not be overriden by the md file parser. That way it is possible to manually set the instruction mnemonics for the cases where the md file parser fails to determine it automatically. ! The `mnemonic' attribute is useful for dealing with instruction specific properties in the pipeline description without defining additional insn attributes. *************** File: gccint.info, Node: Delay Slots, *** 26420,26434 **** The insn attribute mechanism can be used to specify the requirements for delay slots, if any, on a target machine. An instruction is said to require a "delay slot" if some instructions that are physically after ! the instruction are executed as if they were located before it. Classic ! examples are branch and call instructions, which often execute the ! following instruction before the branch or call is performed. On some machines, conditional branch instructions can optionally ! "annul" instructions in the delay slot. This means that the instruction ! will not be executed for certain branch outcomes. Both instructions ! that annul if the branch is true and instructions that annul if the ! branch is false are supported. Delay slot scheduling differs from instruction scheduling in that determining whether an instruction needs a delay slot is dependent only --- 26810,26824 ---- The insn attribute mechanism can be used to specify the requirements for delay slots, if any, on a target machine. An instruction is said to require a "delay slot" if some instructions that are physically after ! the instruction are executed as if they were located before it. ! Classic examples are branch and call instructions, which often execute ! the following instruction before the branch or call is performed. On some machines, conditional branch instructions can optionally ! "annul" instructions in the delay slot. This means that the ! instruction will not be executed for certain branch outcomes. Both ! instructions that annul if the branch is true and instructions that ! annul if the branch is false are supported. Delay slot scheduling differs from instruction scheduling in that determining whether an instruction needs a delay slot is dependent only *************** instructions. See the next section for *** 26437,26473 **** instruction scheduling. The requirement of an insn needing one or more delay slots is indicated ! via the 'define_delay' expression. It has the following form: (define_delay TEST [DELAY-1 ANNUL-TRUE-1 ANNUL-FALSE-1 DELAY-2 ANNUL-TRUE-2 ANNUL-FALSE-2 ...]) ! TEST is an attribute test that indicates whether this 'define_delay' ! applies to a particular insn. If so, the number of required delay slots ! is determined by the length of the vector specified as the second argument. An insn placed in delay slot N must satisfy attribute test DELAY-N. ANNUL-TRUE-N is an attribute test that specifies which insns may be annulled if the branch is true. Similarly, ANNUL-FALSE-N ! specifies which insns in the delay slot may be annulled if the branch is ! false. If annulling is not supported for that delay slot, '(nil)' should be coded. For example, in the common case where branch and call insns require a single delay slot, which may contain any insn other than a branch or ! call, the following would be placed in the 'md' file: (define_delay (eq_attr "type" "branch,call") [(eq_attr "type" "!branch,call") (nil) (nil)]) ! Multiple 'define_delay' expressions may be specified. In this case, each such expression specifies different delay slot requirements and ! there must be no insn for which tests in two 'define_delay' expressions are both true. For example, if we have a machine that requires one delay slot for ! branches but two for calls, no delay slot can contain a branch or call insn, and any valid insn in the delay slot for the branch can be annulled if the branch is true, we might represent this as follows: --- 26827,26863 ---- instruction scheduling. The requirement of an insn needing one or more delay slots is indicated ! via the `define_delay' expression. It has the following form: (define_delay TEST [DELAY-1 ANNUL-TRUE-1 ANNUL-FALSE-1 DELAY-2 ANNUL-TRUE-2 ANNUL-FALSE-2 ...]) ! TEST is an attribute test that indicates whether this `define_delay' ! applies to a particular insn. If so, the number of required delay ! slots is determined by the length of the vector specified as the second argument. An insn placed in delay slot N must satisfy attribute test DELAY-N. ANNUL-TRUE-N is an attribute test that specifies which insns may be annulled if the branch is true. Similarly, ANNUL-FALSE-N ! specifies which insns in the delay slot may be annulled if the branch ! is false. If annulling is not supported for that delay slot, `(nil)' should be coded. For example, in the common case where branch and call insns require a single delay slot, which may contain any insn other than a branch or ! call, the following would be placed in the `md' file: (define_delay (eq_attr "type" "branch,call") [(eq_attr "type" "!branch,call") (nil) (nil)]) ! Multiple `define_delay' expressions may be specified. In this case, each such expression specifies different delay slot requirements and ! there must be no insn for which tests in two `define_delay' expressions are both true. For example, if we have a machine that requires one delay slot for ! branches but two for calls, no delay slot can contain a branch or call insn, and any valid insn in the delay slot for the branch can be annulled if the branch is true, we might represent this as follows: *************** superscalar RISC, and VLIW processors) h *** 26491,26499 **** which several instructions can be executed simultaneously. An instruction starts execution if its issue conditions are satisfied. If not, the instruction is stalled until its conditions are satisfied. ! Such "interlock (pipeline) delay" causes interruption of the fetching of ! successor instructions (or demands nop instructions, e.g. for some MIPS ! processors). There are two major kinds of interlock delays in modern processors. The first one is a data dependence delay determining "instruction --- 26881,26889 ---- which several instructions can be executed simultaneously. An instruction starts execution if its issue conditions are satisfied. If not, the instruction is stalled until its conditions are satisfied. ! Such "interlock (pipeline) delay" causes interruption of the fetching ! of successor instructions (or demands nop instructions, e.g. for some ! MIPS processors). There are two major kinds of interlock delays in modern processors. The first one is a data dependence delay determining "instruction *************** automatically generated from the process *** 26526,26533 **** pipeline hazard recognizer generated from the machine description is based on a deterministic finite state automaton (DFA): the instruction issue is possible if there is a transition from one automaton state to ! another one. This algorithm is very fast, and furthermore, its speed is ! not dependent on processor complexity(1). The rest of this section describes the directives that constitute an automaton-based processor pipeline description. The order of these --- 26916,26923 ---- pipeline hazard recognizer generated from the machine description is based on a deterministic finite state automaton (DFA): the instruction issue is possible if there is a transition from one automaton state to ! another one. This algorithm is very fast, and furthermore, its speed ! is not dependent on processor complexity(1). The rest of this section describes the directives that constitute an automaton-based processor pipeline description. The order of these *************** constructions within the machine descrip *** 26537,26552 **** generated and used for the pipeline hazards recognition. Sometimes the generated finite state automaton used by the pipeline hazard recognizer is large. If we use more than one automaton and bind functional units ! to the automata, the total size of the automata is usually less than the ! size of the single automaton. If there is no one such construction, ! only one finite state automaton is generated. (define_automaton AUTOMATA-NAMES) ! AUTOMATA-NAMES is a string giving names of the automata. The names are ! separated by commas. All the automata should have unique names. The ! automaton name is used in the constructions 'define_cpu_unit' and ! 'define_query_cpu_unit'. Each processor functional unit used in the description of instruction reservations should be described by the following construction. --- 26927,26942 ---- generated and used for the pipeline hazards recognition. Sometimes the generated finite state automaton used by the pipeline hazard recognizer is large. If we use more than one automaton and bind functional units ! to the automata, the total size of the automata is usually less than ! the size of the single automaton. If there is no one such ! construction, only one finite state automaton is generated. (define_automaton AUTOMATA-NAMES) ! AUTOMATA-NAMES is a string giving names of the automata. The names ! are separated by commas. All the automata should have unique names. ! The automaton name is used in the constructions `define_cpu_unit' and ! `define_query_cpu_unit'. Each processor functional unit used in the description of instruction reservations should be described by the following construction. *************** reservations should be described by the *** 26554,26581 **** (define_cpu_unit UNIT-NAMES [AUTOMATON-NAME]) UNIT-NAMES is a string giving the names of the functional units ! separated by commas. Don't use name 'nothing', it is reserved for other ! goals. AUTOMATON-NAME is a string giving the name of the automaton with which the unit is bound. The automaton should be described in construction ! 'define_automaton'. You should give "automaton-name", if there is a defined automaton. The assignment of units to automata are constrained by the uses of the ! units in insn reservations. The most important constraint is: if a unit ! reservation is present on a particular cycle of an alternative for an ! insn reservation, then some unit from the same automaton must be present ! on the same cycle for the other alternatives of the insn reservation. ! The rest of the constraints are mentioned in the description of the ! subsequent constructions. The following construction describes CPU functional units analogously ! to 'define_cpu_unit'. The reservation of such units can be queried for ! an automaton state. The instruction scheduler never queries reservation ! of functional units for given automaton state. So as a rule, you don't ! need this construction. This construction could be used for future code ! generation goals (e.g. to generate VLIW insn templates). (define_query_cpu_unit UNIT-NAMES [AUTOMATON-NAME]) --- 26944,26972 ---- (define_cpu_unit UNIT-NAMES [AUTOMATON-NAME]) UNIT-NAMES is a string giving the names of the functional units ! separated by commas. Don't use name `nothing', it is reserved for ! other goals. AUTOMATON-NAME is a string giving the name of the automaton with which the unit is bound. The automaton should be described in construction ! `define_automaton'. You should give "automaton-name", if there is a defined automaton. The assignment of units to automata are constrained by the uses of the ! units in insn reservations. The most important constraint is: if a ! unit reservation is present on a particular cycle of an alternative for ! an insn reservation, then some unit from the same automaton must be ! present on the same cycle for the other alternatives of the insn ! reservation. The rest of the constraints are mentioned in the ! description of the subsequent constructions. The following construction describes CPU functional units analogously ! to `define_cpu_unit'. The reservation of such units can be queried for ! an automaton state. The instruction scheduler never queries ! reservation of functional units for given automaton state. So as a ! rule, you don't need this construction. This construction could be ! used for future code generation goals (e.g. to generate VLIW insn ! templates). (define_query_cpu_unit UNIT-NAMES [AUTOMATON-NAME]) *************** There is an important difference between *** 26596,26622 **** automaton based pipeline description. The latency time is used for all dependencies when we use the old description. In the automaton based pipeline description, the given latency time is only used for true ! dependencies. The cost of anti-dependencies is always zero and the cost ! of output dependencies is the difference between latency times of the ! producing and consuming insns (if the difference is negative, the cost ! is considered to be zero). You can always change the default costs for ! any description by using the target hook 'TARGET_SCHED_ADJUST_COST' ! (*note Scheduling::). INSN-NAME is a string giving the internal name of the insn. The ! internal names are used in constructions 'define_bypass' and in the automaton description file generated for debugging. The internal name ! has nothing in common with the names in 'define_insn'. It is a good practice to use insn classes described in the processor manual. CONDITION defines what RTL insns are described by this construction. You should remember that you will be in trouble if CONDITION for two or ! more different 'define_insn_reservation' constructions is TRUE for an insn. In this case what reservation will be used for the insn is not defined. Such cases are not checked during generation of the pipeline hazards recognizer because in general recognizing that two conditions may have the same value is quite difficult (especially if the conditions ! contain 'symbol_ref'). It is also not checked during the pipeline hazard recognizer work because it would slow down the recognizer considerably. --- 26987,27013 ---- automaton based pipeline description. The latency time is used for all dependencies when we use the old description. In the automaton based pipeline description, the given latency time is only used for true ! dependencies. The cost of anti-dependencies is always zero and the ! cost of output dependencies is the difference between latency times of ! the producing and consuming insns (if the difference is negative, the ! cost is considered to be zero). You can always change the default ! costs for any description by using the target hook ! `TARGET_SCHED_ADJUST_COST' (*note Scheduling::). INSN-NAME is a string giving the internal name of the insn. The ! internal names are used in constructions `define_bypass' and in the automaton description file generated for debugging. The internal name ! has nothing in common with the names in `define_insn'. It is a good practice to use insn classes described in the processor manual. CONDITION defines what RTL insns are described by this construction. You should remember that you will be in trouble if CONDITION for two or ! more different `define_insn_reservation' constructions is TRUE for an insn. In this case what reservation will be used for the insn is not defined. Such cases are not checked during generation of the pipeline hazards recognizer because in general recognizing that two conditions may have the same value is quite difficult (especially if the conditions ! contain `symbol_ref'). It is also not checked during the pipeline hazard recognizer work because it would slow down the recognizer considerably. *************** expression according to the following sy *** 26642,26669 **** | "nothing" | "(" regexp ")" ! * ',' is used for describing the start of the next cycle in the reservation. ! * '|' is used for describing a reservation described by the first regular expression *or* a reservation described by the second regular expression *or* etc. ! * '+' is used for describing a reservation described by the first regular expression *and* a reservation described by the second regular expression *and* etc. ! * '*' is used for convenience and simply means a sequence in which the regular expression are repeated NUMBER times with cycle ! advancing (see ','). ! * 'cpu_function_unit_name' denotes reservation of the named functional unit. ! * 'reservation_name' -- see description of construction ! 'define_reservation'. ! * 'nothing' denotes no unit reservations. Sometimes unit reservations for different insns contain common parts. In such case, you can simplify the pipeline description by describing --- 27033,27060 ---- | "nothing" | "(" regexp ")" ! * `,' is used for describing the start of the next cycle in the reservation. ! * `|' is used for describing a reservation described by the first regular expression *or* a reservation described by the second regular expression *or* etc. ! * `+' is used for describing a reservation described by the first regular expression *and* a reservation described by the second regular expression *and* etc. ! * `*' is used for convenience and simply means a sequence in which the regular expression are repeated NUMBER times with cycle ! advancing (see `,'). ! * `cpu_function_unit_name' denotes reservation of the named functional unit. ! * `reservation_name' -- see description of construction ! `define_reservation'. ! * `nothing' denotes no unit reservations. Sometimes unit reservations for different insns contain common parts. In such case, you can simplify the pipeline description by describing *************** the common part by the following constru *** 26673,26680 **** RESERVATION-NAME is a string giving name of REGEXP. Functional unit names and reservation names are in the same name space. So the ! reservation names should be different from the functional unit names and ! can not be the reserved name 'nothing'. The following construction is used to describe exceptions in the latency time for given instruction pair. This is so called bypasses. --- 27064,27071 ---- RESERVATION-NAME is a string giving name of REGEXP. Functional unit names and reservation names are in the same name space. So the ! reservation names should be different from the functional unit names ! and can not be the reserved name `nothing'. The following construction is used to describe exceptions in the latency time for given instruction pair. This is so called bypasses. *************** latency time for given instruction pair. *** 26683,26707 **** [GUARD]) NUMBER defines when the result generated by the instructions given in ! string OUT_INSN_NAMES will be ready for the instructions given in string ! IN_INSN_NAMES. Each of these strings is a comma-separated list of ! filename-style globs and they refer to the names of ! 'define_insn_reservation's. For example: (define_bypass 1 "cpu1_load_*, cpu1_store_*" "cpu1_load_*") ! defines a bypass between instructions that start with 'cpu1_load_' or ! 'cpu1_store_' and those that start with 'cpu1_load_'. GUARD is an optional string giving the name of a C function which defines an additional guard for the bypass. The function will get the two insns as parameters. If the function returns zero the bypass will be ignored for this case. The additional guard is necessary to recognize complicated bypasses, e.g. when the consumer is only an ! address of insn 'store' (not a stored value). If there are more one bypass with the same output and input insns, the chosen bypass is the first bypass with a guard in description whose ! guard function returns nonzero. If there is no such bypass, then bypass ! without the guard function is chosen. The following five constructions are usually used to describe VLIW processors, or more precisely, to describe a placement of small --- 27074,27098 ---- [GUARD]) NUMBER defines when the result generated by the instructions given in ! string OUT_INSN_NAMES will be ready for the instructions given in ! string IN_INSN_NAMES. Each of these strings is a comma-separated list ! of filename-style globs and they refer to the names of ! `define_insn_reservation's. For example: (define_bypass 1 "cpu1_load_*, cpu1_store_*" "cpu1_load_*") ! defines a bypass between instructions that start with `cpu1_load_' or ! `cpu1_store_' and those that start with `cpu1_load_'. GUARD is an optional string giving the name of a C function which defines an additional guard for the bypass. The function will get the two insns as parameters. If the function returns zero the bypass will be ignored for this case. The additional guard is necessary to recognize complicated bypasses, e.g. when the consumer is only an ! address of insn `store' (not a stored value). If there are more one bypass with the same output and input insns, the chosen bypass is the first bypass with a guard in description whose ! guard function returns nonzero. If there is no such bypass, then ! bypass without the guard function is chosen. The following five constructions are usually used to describe VLIW processors, or more precisely, to describe a placement of small *************** commas. *** 26721,26727 **** comma. Currently pattern is one unit or units separated by white-spaces. ! The first construction ('exclusion_set') means that each functional unit in the first string can not be reserved simultaneously with a unit whose name is in the second string and vice versa. For example, the construction is useful for describing processors (e.g. some SPARC --- 27112,27118 ---- comma. Currently pattern is one unit or units separated by white-spaces. ! The first construction (`exclusion_set') means that each functional unit in the first string can not be reserved simultaneously with a unit whose name is in the second string and vice versa. For example, the construction is useful for describing processors (e.g. some SPARC *************** processors) with a fully pipelined float *** 26729,26788 **** can execute simultaneously only single floating point insns or only double floating point insns. ! The second construction ('presence_set') means that each functional unit in the first string can not be reserved unless at least one of ! pattern of units whose names are in the second string is reserved. This ! is an asymmetric relation. For example, it is useful for description ! that VLIW 'slot1' is reserved after 'slot0' reservation. We could ! describe it by the following construction (presence_set "slot1" "slot0") ! Or 'slot1' is reserved only after 'slot0' and unit 'b0' reservation. In this case we could write (presence_set "slot1" "slot0 b0") ! The third construction ('final_presence_set') is analogous to ! 'presence_set'. The difference between them is when checking is done. When an instruction is issued in given automaton state reflecting all current and planned unit reservations, the automaton state is changed. The first state is a source state, the second one is a result state. ! Checking for 'presence_set' is done on the source state reservation, ! checking for 'final_presence_set' is done on the result reservation. This construction is useful to describe a reservation which is actually two subsequent reservations. For example, if we use (presence_set "slot1" "slot0") ! the following insn will be never issued (because 'slot1' requires ! 'slot0' which is absent in the source state). (define_reservation "insn_and_nop" "slot0 + slot1") ! but it can be issued if we use analogous 'final_presence_set'. ! The forth construction ('absence_set') means that each functional unit in the first string can be reserved only if each pattern of units whose names are in the second string is not reserved. This is an asymmetric ! relation (actually 'exclusion_set' is analogous to this one but it is ! symmetric). For example it might be useful in a VLIW description to say ! that 'slot0' cannot be reserved after either 'slot1' or 'slot2' have ! been reserved. This can be described as: (absence_set "slot0" "slot1, slot2") ! Or 'slot2' can not be reserved if 'slot0' and unit 'b0' are reserved or ! 'slot1' and unit 'b1' are reserved. In this case we could write (absence_set "slot2" "slot0 b0, slot1 b1") All functional units mentioned in a set should belong to the same automaton. ! The last construction ('final_absence_set') is analogous to ! 'absence_set' but checking is done on the result (state) reservation. ! See comments for 'final_presence_set'. You can control the generator of the pipeline hazard recognizer with the following construction. --- 27120,27179 ---- can execute simultaneously only single floating point insns or only double floating point insns. ! The second construction (`presence_set') means that each functional unit in the first string can not be reserved unless at least one of ! pattern of units whose names are in the second string is reserved. ! This is an asymmetric relation. For example, it is useful for ! description that VLIW `slot1' is reserved after `slot0' reservation. ! We could describe it by the following construction (presence_set "slot1" "slot0") ! Or `slot1' is reserved only after `slot0' and unit `b0' reservation. In this case we could write (presence_set "slot1" "slot0 b0") ! The third construction (`final_presence_set') is analogous to ! `presence_set'. The difference between them is when checking is done. When an instruction is issued in given automaton state reflecting all current and planned unit reservations, the automaton state is changed. The first state is a source state, the second one is a result state. ! Checking for `presence_set' is done on the source state reservation, ! checking for `final_presence_set' is done on the result reservation. This construction is useful to describe a reservation which is actually two subsequent reservations. For example, if we use (presence_set "slot1" "slot0") ! the following insn will be never issued (because `slot1' requires ! `slot0' which is absent in the source state). (define_reservation "insn_and_nop" "slot0 + slot1") ! but it can be issued if we use analogous `final_presence_set'. ! The forth construction (`absence_set') means that each functional unit in the first string can be reserved only if each pattern of units whose names are in the second string is not reserved. This is an asymmetric ! relation (actually `exclusion_set' is analogous to this one but it is ! symmetric). For example it might be useful in a VLIW description to ! say that `slot0' cannot be reserved after either `slot1' or `slot2' ! have been reserved. This can be described as: (absence_set "slot0" "slot1, slot2") ! Or `slot2' can not be reserved if `slot0' and unit `b0' are reserved ! or `slot1' and unit `b1' are reserved. In this case we could write (absence_set "slot2" "slot0 b0, slot1 b1") All functional units mentioned in a set should belong to the same automaton. ! The last construction (`final_absence_set') is analogous to ! `absence_set' but checking is done on the result (state) reservation. ! See comments for `final_presence_set'. You can control the generator of the pipeline hazard recognizer with the following construction. *************** Currently there are the following option *** 26799,26836 **** * "time" means printing time statistics about the generation of automata. ! * "stats" means printing statistics about the generated automata such ! as the number of DFA states, NDFA states and arcs. * "v" means a generation of the file describing the result automata. ! The file has suffix '.dfa' and can be used for the description verification and debugging. ! * "w" means a generation of warning instead of error for non-critical ! errors. ! * "no-comb-vect" prevents the automaton generator from generating two ! data structures and comparing them for space efficiency. Using a ! comb vector to represent transitions may be better, but it can be very expensive to construct. This option is useful if the build process spends an unacceptably long time in genautomata. * "ndfa" makes nondeterministic finite state automata. This affects ! the treatment of operator '|' in the regular expressions. The usual treatment of the operator is to try the first alternative and, if the reservation is not possible, the second alternative. The nondeterministic treatment means trying all alternatives, some of them may be rejected by reservations in the subsequent insns. * "collapse-ndfa" modifies the behavior of the generator when ! producing an automaton. An additional state transition to collapse ! a nondeterministic NDFA state to a deterministic DFA state is ! generated. It can be triggered by passing 'const0_rtx' to state_transition. In such an automaton, cycle advance transitions are available only for these collapsed states. This option is ! useful for ports that want to use the 'ndfa' option, but also want ! to use 'define_query_cpu_unit' to assign units to insns issued in a ! cycle. * "progress" means output of a progress bar showing how many states were generated so far for automaton being processed. This is --- 27190,27227 ---- * "time" means printing time statistics about the generation of automata. ! * "stats" means printing statistics about the generated automata ! such as the number of DFA states, NDFA states and arcs. * "v" means a generation of the file describing the result automata. ! The file has suffix `.dfa' and can be used for the description verification and debugging. ! * "w" means a generation of warning instead of error for ! non-critical errors. ! * "no-comb-vect" prevents the automaton generator from generating ! two data structures and comparing them for space efficiency. Using ! a comb vector to represent transitions may be better, but it can be very expensive to construct. This option is useful if the build process spends an unacceptably long time in genautomata. * "ndfa" makes nondeterministic finite state automata. This affects ! the treatment of operator `|' in the regular expressions. The usual treatment of the operator is to try the first alternative and, if the reservation is not possible, the second alternative. The nondeterministic treatment means trying all alternatives, some of them may be rejected by reservations in the subsequent insns. * "collapse-ndfa" modifies the behavior of the generator when ! producing an automaton. An additional state transition to ! collapse a nondeterministic NDFA state to a deterministic DFA ! state is generated. It can be triggered by passing `const0_rtx' to state_transition. In such an automaton, cycle advance transitions are available only for these collapsed states. This option is ! useful for ports that want to use the `ndfa' option, but also want ! to use `define_query_cpu_unit' to assign units to insns issued in ! a cycle. * "progress" means output of a progress bar showing how many states were generated so far for automaton being processed. This is *************** Currently there are the following option *** 26840,26847 **** the huge automaton. As an example, consider a superscalar RISC machine which can issue ! three insns (two integer insns and one floating point insn) on the cycle ! but can finish only two insns. To describe this, we define the following functional units. (define_cpu_unit "i0_pipeline, i1_pipeline, f_pipeline") --- 27231,27238 ---- the huge automaton. As an example, consider a superscalar RISC machine which can issue ! three insns (two integer insns and one floating point insn) on the ! cycle but can finish only two insns. To describe this, we define the following functional units. (define_cpu_unit "i0_pipeline, i1_pipeline, f_pipeline") *************** following functional units. *** 26849,26864 **** All simple integer insns can be executed in any integer pipeline and their result is ready in two cycles. The simple integer insns are ! issued into the first pipeline unless it is reserved, otherwise they are ! issued into the second pipeline. Integer division and multiplication ! insns can be executed only in the second integer pipeline and their ! results are ready correspondingly in 8 and 4 cycles. The integer ! division is not pipelined, i.e. the subsequent integer division insn can ! not be issued until the current division insn finished. Floating point ! insns are fully pipelined and their results are ready in 3 cycles. ! Where the result of a floating point insn is used by an integer insn, an ! additional delay of one cycle is incurred. To describe all of this we ! could specify (define_cpu_unit "div") --- 27240,27255 ---- All simple integer insns can be executed in any integer pipeline and their result is ready in two cycles. The simple integer insns are ! issued into the first pipeline unless it is reserved, otherwise they ! are issued into the second pipeline. Integer division and ! multiplication insns can be executed only in the second integer ! pipeline and their results are ready correspondingly in 8 and 4 cycles. ! The integer division is not pipelined, i.e. the subsequent integer ! division insn can not be issued until the current division insn ! finished. Floating point insns are fully pipelined and their results ! are ready in 3 cycles. Where the result of a floating point insn is ! used by an integer insn, an additional delay of one cycle is incurred. ! To describe all of this we could specify (define_cpu_unit "div") *************** could specify *** 26880,26898 **** (define_reservation "finish" "port0|port1") ! and use it in all 'define_insn_reservation' as in the following construction (define_insn_reservation "simple" 2 (eq_attr "type" "int") "(i0_pipeline | i1_pipeline), finish") ! ---------- Footnotes ---------- ! (1) However, the size of the automaton depends on processor complexity. To limit this effect, machine descriptions can split orthogonal parts of the machine description among several automata: but ! then, since each of these must be stepped independently, this does cause ! a small decrease in the algorithm's performance.  File: gccint.info, Node: Conditional Execution, Next: Define Subst, Prev: Insn Attributes, Up: Machine Desc --- 27271,27289 ---- (define_reservation "finish" "port0|port1") ! and use it in all `define_insn_reservation' as in the following construction (define_insn_reservation "simple" 2 (eq_attr "type" "int") "(i0_pipeline | i1_pipeline), finish") ! ---------- Footnotes ---------- ! (1) However, the size of the automaton depends on processor complexity. To limit this effect, machine descriptions can split orthogonal parts of the machine description among several automata: but ! then, since each of these must be stepped independently, this does ! cause a small decrease in the algorithm's performance.  File: gccint.info, Node: Conditional Execution, Next: Define Subst, Prev: Insn Attributes, Up: Machine Desc *************** A number of architectures provide for so *** 26904,26911 **** execution, or predication. The hallmark of this feature is the ability to nullify most of the instructions in the instruction set. When the instruction set is large and not entirely symmetric, it can be quite ! tedious to describe these forms directly in the '.md' file. An ! alternative is the 'define_cond_exec' template. (define_cond_exec [PREDICATE-PATTERN] --- 27295,27302 ---- execution, or predication. The hallmark of this feature is the ability to nullify most of the instructions in the instruction set. When the instruction set is large and not entirely symmetric, it can be quite ! tedious to describe these forms directly in the `.md' file. An ! alternative is the `define_cond_exec' template. (define_cond_exec [PREDICATE-PATTERN] *************** alternative is the 'define_cond_exec' te *** 26913,26954 **** "OUTPUT-TEMPLATE" "OPTIONAL-INSN-ATTRIBUES") ! PREDICATE-PATTERN is the condition that must be true for the insn to be ! executed at runtime and should match a relational operator. One can use ! 'match_operator' to match several relational operators at once. Any ! 'match_operand' operands must have no more than one alternative. ! CONDITION is a C expression that must be true for the generated pattern ! to match. ! OUTPUT-TEMPLATE is a string similar to the 'define_insn' output ! template (*note Output Template::), except that the '*' and '@' special cases do not apply. This is only useful if the assembly text for the predicate is a simple prefix to the main insn. In order to handle the ! general case, there is a global variable 'current_insn_predicate' that ! will contain the entire predicate if the current insn is predicated, and ! will otherwise be 'NULL'. OPTIONAL-INSN-ATTRIBUTES is an optional vector of attributes that gets ! appended to the insn attributes of the produced cond_exec rtx. It can be used to add some distinguishing attribute to cond_exec rtxs produced ! that way. An example usage would be to use this attribute in ! conjunction with attributes on the main pattern to disable particular ! alternatives under certain conditions. ! When 'define_cond_exec' is used, an implicit reference to the ! 'predicable' instruction attribute is made. *Note Insn Attributes::. This attribute must be a boolean (i.e. have exactly two elements in its ! LIST-OF-VALUES), with the possible values being 'no' and 'yes'. The default and all uses in the insns must be a simple constant, not a complex expressions. It may, however, depend on the alternative, by using a comma-separated list of values. If that is the case, the port ! should also define an 'enabled' attribute (*note Disable Insn ! Alternatives::), which should also allow only 'no' and 'yes' as its values. ! For each 'define_insn' for which the 'predicable' attribute is true, a ! new 'define_insn' pattern will be generated that matches a predicated version of the instruction. For example, (define_insn "addsi" --- 27304,27345 ---- "OUTPUT-TEMPLATE" "OPTIONAL-INSN-ATTRIBUES") ! PREDICATE-PATTERN is the condition that must be true for the insn to ! be executed at runtime and should match a relational operator. One can ! use `match_operator' to match several relational operators at once. ! Any `match_operand' operands must have no more than one alternative. ! CONDITION is a C expression that must be true for the generated ! pattern to match. ! OUTPUT-TEMPLATE is a string similar to the `define_insn' output ! template (*note Output Template::), except that the `*' and `@' special cases do not apply. This is only useful if the assembly text for the predicate is a simple prefix to the main insn. In order to handle the ! general case, there is a global variable `current_insn_predicate' that ! will contain the entire predicate if the current insn is predicated, ! and will otherwise be `NULL'. OPTIONAL-INSN-ATTRIBUTES is an optional vector of attributes that gets ! appended to the insn attributes of the produced cond_exec rtx. It can be used to add some distinguishing attribute to cond_exec rtxs produced ! that way. An example usage would be to use this attribute in conjunction ! with attributes on the main pattern to disable particular alternatives ! under certain conditions. ! When `define_cond_exec' is used, an implicit reference to the ! `predicable' instruction attribute is made. *Note Insn Attributes::. This attribute must be a boolean (i.e. have exactly two elements in its ! LIST-OF-VALUES), with the possible values being `no' and `yes'. The default and all uses in the insns must be a simple constant, not a complex expressions. It may, however, depend on the alternative, by using a comma-separated list of values. If that is the case, the port ! should also define an `enabled' attribute (*note Disable Insn ! Alternatives::), which should also allow only `no' and `yes' as its values. ! For each `define_insn' for which the `predicable' attribute is true, a ! new `define_insn' pattern will be generated that matches a predicated version of the instruction. For example, (define_insn "addsi" *************** File: gccint.info, Node: Define Subst, *** 26983,26993 **** For some hardware architectures there are common cases when the RTL templates for the instructions can be derived from the other RTL ! templates using simple transformations. E.g., 'i386.md' contains an RTL ! template for the ordinary 'sub' instruction-- '*subsi_1', and for the ! 'sub' instruction with subsequent zero-extension--'*subsi_1_zext'. Such ! cases can be easily implemented by a single meta-template capable of ! generating a modified case based on the initial one: (define_subst "NAME" [INPUT-TEMPLATE] --- 27374,27384 ---- For some hardware architectures there are common cases when the RTL templates for the instructions can be derived from the other RTL ! templates using simple transformations. E.g., `i386.md' contains an ! RTL template for the ordinary `sub' instruction-- `*subsi_1', and for ! the `sub' instruction with subsequent zero-extension--`*subsi_1_zext'. ! Such cases can be easily implemented by a single meta-template capable ! of generating a modified case based on the initial one: (define_subst "NAME" [INPUT-TEMPLATE] *************** output-template. *** 27003,27040 **** OUTPUT-TEMPLATE is a pattern that will be used in the resulting template. ! 'define_subst' mechanism is tightly coupled with the notion of the ! subst attribute (*note Subst Iterators::). The use of 'define_subst' is ! triggered by a reference to a subst attribute in the transforming RTL ! template. This reference initiates duplication of the source RTL template and substitution of the attributes with their values. The source RTL template is left unchanged, while the copy is transformed by ! 'define_subst'. This transformation can fail in the case when the source RTL template is not matched against the input-template of the ! 'define_subst'. In such case the copy is deleted. ! 'define_subst' can be used only in 'define_insn' and 'define_expand', ! it cannot be used in other expressions (e.g. in ! 'define_insn_and_split'). * Menu: ! * Define Subst Example:: Example of 'define_subst' work. * Define Subst Pattern Matching:: Process of template comparison. * Define Subst Output Template:: Generation of output template.  File: gccint.info, Node: Define Subst Example, Next: Define Subst Pattern Matching, Up: Define Subst ! 16.21.1 'define_subst' Example ------------------------------ ! To illustrate how 'define_subst' works, let us examine a simple template ! transformation. Suppose there are two kinds of instructions: one that touches flags and the other that does not. The instructions of the second type could be ! generated with the following 'define_subst': (define_subst "add_clobber_subst" [(set (match_operand:SI 0 "" "") --- 27394,27431 ---- OUTPUT-TEMPLATE is a pattern that will be used in the resulting template. ! `define_subst' mechanism is tightly coupled with the notion of the ! subst attribute (*note Subst Iterators::). The use of `define_subst' ! is triggered by a reference to a subst attribute in the transforming ! RTL template. This reference initiates duplication of the source RTL template and substitution of the attributes with their values. The source RTL template is left unchanged, while the copy is transformed by ! `define_subst'. This transformation can fail in the case when the source RTL template is not matched against the input-template of the ! `define_subst'. In such case the copy is deleted. ! `define_subst' can be used only in `define_insn' and `define_expand', ! it cannot be used in other expressions (e.g. in ! `define_insn_and_split'). * Menu: ! * Define Subst Example:: Example of `define_subst' work. * Define Subst Pattern Matching:: Process of template comparison. * Define Subst Output Template:: Generation of output template.  File: gccint.info, Node: Define Subst Example, Next: Define Subst Pattern Matching, Up: Define Subst ! 16.21.1 `define_subst' Example ------------------------------ ! To illustrate how `define_subst' works, let us examine a simple ! template transformation. Suppose there are two kinds of instructions: one that touches flags and the other that does not. The instructions of the second type could be ! generated with the following `define_subst': (define_subst "add_clobber_subst" [(set (match_operand:SI 0 "" "") *************** generated with the following 'define_sub *** 27044,27054 **** (match_dup 1)) (clobber (reg:CC FLAGS_REG))] ! This 'define_subst' can be applied to any RTL pattern containing 'set' of mode SI and generates a copy with clobber when it is applied. ! Assume there is an RTL template for a 'max' instruction to be used in ! 'define_subst' mentioned above: (define_insn "maxsi" [(set (match_operand:SI 0 "register_operand" "=r") --- 27435,27445 ---- (match_dup 1)) (clobber (reg:CC FLAGS_REG))] ! This `define_subst' can be applied to any RTL pattern containing `set' of mode SI and generates a copy with clobber when it is applied. ! Assume there is an RTL template for a `max' instruction to be used in ! `define_subst' mentioned above: (define_insn "maxsi" [(set (match_operand:SI 0 "register_operand" "=r") *************** of mode SI and generates a copy with clo *** 27059,27078 **** "max\t{%2, %1, %0|%0, %1, %2}" [...]) ! To mark the RTL template for 'define_subst' application, subst-attributes are used. They should be declared in advance: (define_subst_attr "add_clobber_name" "add_clobber_subst" "_noclobber" "_clobber") ! Here 'add_clobber_name' is the attribute name, 'add_clobber_subst' is ! the name of the corresponding 'define_subst', the third argument ! ('_noclobber') is the attribute value that would be substituted into the ! unchanged version of the source RTL template, and the last argument ! ('_clobber') is the value that would be substituted into the second, transformed, version of the RTL template. Once the subst-attribute has been defined, it should be used in RTL ! templates which need to be processed by the 'define_subst'. So, the original RTL template should be changed: (define_insn "maxsi" --- 27450,27469 ---- "max\t{%2, %1, %0|%0, %1, %2}" [...]) ! To mark the RTL template for `define_subst' application, subst-attributes are used. They should be declared in advance: (define_subst_attr "add_clobber_name" "add_clobber_subst" "_noclobber" "_clobber") ! Here `add_clobber_name' is the attribute name, `add_clobber_subst' is ! the name of the corresponding `define_subst', the third argument ! (`_noclobber') is the attribute value that would be substituted into ! the unchanged version of the source RTL template, and the last argument ! (`_clobber') is the value that would be substituted into the second, transformed, version of the RTL template. Once the subst-attribute has been defined, it should be used in RTL ! templates which need to be processed by the `define_subst'. So, the original RTL template should be changed: (define_insn "maxsi" *************** original RTL template should be changed: *** 27084,27090 **** "max\t{%2, %1, %0|%0, %1, %2}" [...]) ! The result of the 'define_subst' usage would look like the following: (define_insn "maxsi_noclobber" [(set (match_operand:SI 0 "register_operand" "=r") --- 27475,27481 ---- "max\t{%2, %1, %0|%0, %1, %2}" [...]) ! The result of the `define_subst' usage would look like the following: (define_insn "maxsi_noclobber" [(set (match_operand:SI 0 "register_operand" "=r") *************** original RTL template should be changed: *** 27107,27172 ****  File: gccint.info, Node: Define Subst Pattern Matching, Next: Define Subst Output Template, Prev: Define Subst Example, Up: Define Subst ! 16.21.2 Pattern Matching in 'define_subst' ------------------------------------------ ! All expressions, allowed in 'define_insn' or 'define_expand', are ! allowed in the input-template of 'define_subst', except 'match_par_dup', ! 'match_scratch', 'match_parallel'. The meanings of expressions in the ! input-template were changed: ! 'match_operand' matches any expression (possibly, a subtree in ! RTL-template), if modes of the 'match_operand' and this expression are ! the same, or mode of the 'match_operand' is 'VOIDmode', or this ! expression is 'match_dup', 'match_op_dup'. If the expression is ! 'match_operand' too, and predicate of 'match_operand' from the input pattern is not empty, then the predicates are compared. That can be used for more accurate filtering of accepted RTL-templates. ! 'match_operator' matches common operators (like 'plus', 'minus'), ! 'unspec', 'unspec_volatile' operators and 'match_operator's from the ! original pattern if the modes match and 'match_operator' from the input pattern has the same number of operands as the operator from the original pattern.  File: gccint.info, Node: Define Subst Output Template, Prev: Define Subst Pattern Matching, Up: Define Subst ! 16.21.3 Generation of output template in 'define_subst' ------------------------------------------------------- ! If all necessary checks for 'define_subst' application pass, a new RTL-pattern, based on the output-template, is created to replace the old template. Like in input-patterns, meanings of some RTL expressions are ! changed when they are used in output-patterns of a 'define_subst'. ! Thus, 'match_dup' is used for copying the whole expression from the ! original pattern, which matched corresponding 'match_operand' from the input pattern. ! 'match_dup N' is used in the output template to be replaced with the ! expression from the original pattern, which matched 'match_operand N' ! from the input pattern. As a consequence, 'match_dup' cannot be used to ! point to 'match_operand's from the output pattern, it should always ! refer to a 'match_operand' from the input pattern. In the output template one can refer to the expressions from the original pattern and create new ones. For instance, some operands could ! be added by means of standard 'match_operand'. ! After replacing 'match_dup' with some RTL-subtree from the original ! pattern, it could happen that several 'match_operand's in the output ! pattern have the same indexes. It is unknown, how many and what indexes ! would be used in the expression which would replace 'match_dup', so such ! conflicts in indexes are inevitable. To overcome this issue, ! 'match_operands' and 'match_operators', which were introduced into the ! output pattern, are renumerated when all 'match_dup's are replaced. ! Number of alternatives in 'match_operand's introduced into the output ! template 'M' could differ from the number of alternatives in the ! original pattern 'N', so in the resultant pattern there would be 'N*M' alternatives. Thus, constraints from the original pattern would be ! duplicated 'N' times, constraints from the output pattern would be ! duplicated 'M' times, producing all possible combinations.  File: gccint.info, Node: Constant Definitions, Next: Iterators, Prev: Define Subst, Up: Machine Desc --- 27498,27564 ----  File: gccint.info, Node: Define Subst Pattern Matching, Next: Define Subst Output Template, Prev: Define Subst Example, Up: Define Subst ! 16.21.2 Pattern Matching in `define_subst' ------------------------------------------ ! All expressions, allowed in `define_insn' or `define_expand', are ! allowed in the input-template of `define_subst', except ! `match_par_dup', `match_scratch', `match_parallel'. The meanings of ! expressions in the input-template were changed: ! `match_operand' matches any expression (possibly, a subtree in ! RTL-template), if modes of the `match_operand' and this expression are ! the same, or mode of the `match_operand' is `VOIDmode', or this ! expression is `match_dup', `match_op_dup'. If the expression is ! `match_operand' too, and predicate of `match_operand' from the input pattern is not empty, then the predicates are compared. That can be used for more accurate filtering of accepted RTL-templates. ! `match_operator' matches common operators (like `plus', `minus'), ! `unspec', `unspec_volatile' operators and `match_operator's from the ! original pattern if the modes match and `match_operator' from the input pattern has the same number of operands as the operator from the original pattern.  File: gccint.info, Node: Define Subst Output Template, Prev: Define Subst Pattern Matching, Up: Define Subst ! 16.21.3 Generation of output template in `define_subst' ------------------------------------------------------- ! If all necessary checks for `define_subst' application pass, a new RTL-pattern, based on the output-template, is created to replace the old template. Like in input-patterns, meanings of some RTL expressions are ! changed when they are used in output-patterns of a `define_subst'. ! Thus, `match_dup' is used for copying the whole expression from the ! original pattern, which matched corresponding `match_operand' from the input pattern. ! `match_dup N' is used in the output template to be replaced with the ! expression from the original pattern, which matched `match_operand N' ! from the input pattern. As a consequence, `match_dup' cannot be used ! to point to `match_operand's from the output pattern, it should always ! refer to a `match_operand' from the input pattern. In the output template one can refer to the expressions from the original pattern and create new ones. For instance, some operands could ! be added by means of standard `match_operand'. ! After replacing `match_dup' with some RTL-subtree from the original ! pattern, it could happen that several `match_operand's in the output ! pattern have the same indexes. It is unknown, how many and what ! indexes would be used in the expression which would replace ! `match_dup', so such conflicts in indexes are inevitable. To overcome ! this issue, `match_operands' and `match_operators', which were ! introduced into the output pattern, are renumerated when all ! `match_dup's are replaced. ! Number of alternatives in `match_operand's introduced into the output ! template `M' could differ from the number of alternatives in the ! original pattern `N', so in the resultant pattern there would be `N*M' alternatives. Thus, constraints from the original pattern would be ! duplicated `N' times, constraints from the output pattern would be ! duplicated `M' times, producing all possible combinations.  File: gccint.info, Node: Constant Definitions, Next: Iterators, Prev: Define Subst, Up: Machine Desc *************** File: gccint.info, Node: Constant Defin *** 27177,27187 **** Using literal constants inside instruction patterns reduces legibility and can be a maintenance problem. ! To overcome this problem, you may use the 'define_constants' expression. It contains a vector of name-value pairs. From that point on, wherever any of the names appears in the MD file, it is as if the corresponding value had been written instead. You may use ! 'define_constants' multiple times; each appearance adds more constants to the table. It is an error to redefine a constant with a different value. --- 27569,27579 ---- Using literal constants inside instruction patterns reduces legibility and can be a maintenance problem. ! To overcome this problem, you may use the `define_constants' expression. It contains a vector of name-value pairs. From that point on, wherever any of the names appears in the MD file, it is as if the corresponding value had been written instead. You may use ! `define_constants' multiple times; each appearance adds more constants to the table. It is an error to redefine a constant with a different value. *************** value. *** 27218,27224 **** in the insn-codes.h header file as #defines. You can also use the machine description file to define enumerations. ! Like the constants defined by 'define_constant', these enumerations are visible to both the machine description file and the main C code. The syntax is as follows: --- 27610,27616 ---- in the insn-codes.h header file as #defines. You can also use the machine description file to define enumerations. ! Like the constants defined by `define_constant', these enumerations are visible to both the machine description file and the main C code. The syntax is as follows: *************** visible to both the machine description *** 27231,27237 **** ]) This definition causes the equivalent of the following C code to appear ! in 'insn-constants.h': enum NAME { VALUE0 = 0, --- 27623,27629 ---- ]) This definition causes the equivalent of the following C code to appear ! in `insn-constants.h': enum NAME { VALUE0 = 0, *************** in 'insn-constants.h': *** 27241,27257 **** }; #define NUM_CNAME_VALUES (N + 1) ! where CNAME is the capitalized form of NAME. It also makes each VALUEI ! available in the machine description file, just as if it had been ! declared with: (define_constants [(VALUEI I)]) ! Each VALUEI is usually an upper-case identifier and usually begins with ! CNAME. ! You can split the enumeration definition into as many statements as you ! like. The above example is directly equivalent to: (define_c_enum "NAME" [VALUE0]) (define_c_enum "NAME" [VALUE1]) --- 27633,27649 ---- }; #define NUM_CNAME_VALUES (N + 1) ! where CNAME is the capitalized form of NAME. It also makes each ! VALUEI available in the machine description file, just as if it had ! been declared with: (define_constants [(VALUEI I)]) ! Each VALUEI is usually an upper-case identifier and usually begins ! with CNAME. ! You can split the enumeration definition into as many statements as ! you like. The above example is directly equivalent to: (define_c_enum "NAME" [VALUE0]) (define_c_enum "NAME" [VALUE1]) *************** like. The above example is directly equ *** 27259,27292 **** (define_c_enum "NAME" [VALUEN]) Splitting the enumeration helps to improve the modularity of each ! individual '.md' file. For example, if a port defines its ! synchronization instructions in a separate 'sync.md' file, it is convenient to define all synchronization-specific enumeration values in ! 'sync.md' rather than in the main '.md' file. Some enumeration names have special significance to GCC: ! 'unspecv' ! If an enumeration called 'unspecv' is defined, GCC will use it when ! printing out 'unspec_volatile' expressions. For example: (define_c_enum "unspecv" [ UNSPECV_BLOCKAGE ]) ! causes GCC to print '(unspec_volatile ... 0)' as: (unspec_volatile ... UNSPECV_BLOCKAGE) ! 'unspec' ! If an enumeration called 'unspec' is defined, GCC will use it when ! printing out 'unspec' expressions. GCC will also use it when ! printing out 'unspec_volatile' expressions unless an 'unspecv' enumeration is also defined. You can therefore decide whether to keep separate enumerations for volatile and non-volatile expressions or whether to use the same enumeration for both. ! Another way of defining an enumeration is to use 'define_enum': (define_enum "NAME" [ VALUE0 --- 27651,27684 ---- (define_c_enum "NAME" [VALUEN]) Splitting the enumeration helps to improve the modularity of each ! individual `.md' file. For example, if a port defines its ! synchronization instructions in a separate `sync.md' file, it is convenient to define all synchronization-specific enumeration values in ! `sync.md' rather than in the main `.md' file. Some enumeration names have special significance to GCC: ! `unspecv' ! If an enumeration called `unspecv' is defined, GCC will use it ! when printing out `unspec_volatile' expressions. For example: (define_c_enum "unspecv" [ UNSPECV_BLOCKAGE ]) ! causes GCC to print `(unspec_volatile ... 0)' as: (unspec_volatile ... UNSPECV_BLOCKAGE) ! `unspec' ! If an enumeration called `unspec' is defined, GCC will use it when ! printing out `unspec' expressions. GCC will also use it when ! printing out `unspec_volatile' expressions unless an `unspecv' enumeration is also defined. You can therefore decide whether to keep separate enumerations for volatile and non-volatile expressions or whether to use the same enumeration for both. ! Another way of defining an enumeration is to use `define_enum': (define_enum "NAME" [ VALUE0 *************** convenient to define all synchronization *** 27305,27311 **** ]) where CVALUEI is the capitalized form of VALUEI. However, unlike ! 'define_c_enum', the enumerations defined by 'define_enum' can be used in attribute specifications (*note define_enum_attr::).  --- 27697,27703 ---- ]) where CVALUEI is the capitalized form of VALUEI. However, unlike ! `define_c_enum', the enumerations defined by `define_enum' can be used in attribute specifications (*note define_enum_attr::).  *************** Ports often need to define similar patte *** 27335,27350 **** modes. For example: * If a processor has hardware support for both single and double ! floating-point arithmetic, the 'SFmode' patterns tend to be very ! similar to the 'DFmode' ones. ! * If a port uses 'SImode' pointers in one configuration and 'DImode' ! pointers in another, it will usually have very similar 'SImode' and ! 'DImode' patterns for manipulating pointers. ! Mode iterators allow several patterns to be instantiated from one '.md' ! file template. They can be used with any type of rtx-based construct, ! such as a 'define_insn', 'define_split', or 'define_peephole2'. * Menu: --- 27727,27743 ---- modes. For example: * If a processor has hardware support for both single and double ! floating-point arithmetic, the `SFmode' patterns tend to be very ! similar to the `DFmode' ones. ! * If a port uses `SImode' pointers in one configuration and `DImode' ! pointers in another, it will usually have very similar `SImode' ! and `DImode' patterns for manipulating pointers. ! Mode iterators allow several patterns to be instantiated from one ! `.md' file template. They can be used with any type of rtx-based ! construct, such as a `define_insn', `define_split', or ! `define_peephole2'. * Menu: *************** The syntax for defining a mode iterator *** 27362,27390 **** (define_mode_iterator NAME [(MODE1 "COND1") ... (MODEN "CONDN")]) ! This allows subsequent '.md' file constructs to use the mode suffix ! ':NAME'. Every construct that does so will be expanded N times, once ! with every use of ':NAME' replaced by ':MODE1', once with every use ! replaced by ':MODE2', and so on. In the expansion for a particular MODEI, every C condition will also require that CONDI be true. For example: (define_mode_iterator P [(SI "Pmode == SImode") (DI "Pmode == DImode")]) ! defines a new mode suffix ':P'. Every construct that uses ':P' will be ! expanded twice, once with every ':P' replaced by ':SI' and once with ! every ':P' replaced by ':DI'. The ':SI' version will only apply if ! 'Pmode == SImode' and the ':DI' version will only apply if 'Pmode == DImode'. ! As with other '.md' conditions, an empty string is treated as "always ! true". '(MODE "")' can also be abbreviated to 'MODE'. For example: (define_mode_iterator GPR [SI (DI "TARGET_64BIT")]) ! means that the ':DI' expansion only applies if 'TARGET_64BIT' but that ! the ':SI' expansion has no such constraint. Iterators are applied in the order they are defined. This can be significant if two iterators are used in a construct that requires --- 27755,27783 ---- (define_mode_iterator NAME [(MODE1 "COND1") ... (MODEN "CONDN")]) ! This allows subsequent `.md' file constructs to use the mode suffix ! `:NAME'. Every construct that does so will be expanded N times, once ! with every use of `:NAME' replaced by `:MODE1', once with every use ! replaced by `:MODE2', and so on. In the expansion for a particular MODEI, every C condition will also require that CONDI be true. For example: (define_mode_iterator P [(SI "Pmode == SImode") (DI "Pmode == DImode")]) ! defines a new mode suffix `:P'. Every construct that uses `:P' will ! be expanded twice, once with every `:P' replaced by `:SI' and once with ! every `:P' replaced by `:DI'. The `:SI' version will only apply if ! `Pmode == SImode' and the `:DI' version will only apply if `Pmode == DImode'. ! As with other `.md' conditions, an empty string is treated as "always ! true". `(MODE "")' can also be abbreviated to `MODE'. For example: (define_mode_iterator GPR [SI (DI "TARGET_64BIT")]) ! means that the `:DI' expansion only applies if `TARGET_64BIT' but that ! the `:SI' expansion has no such constraint. Iterators are applied in the order they are defined. This can be significant if two iterators are used in a construct that requires *************** File: gccint.info, Node: Substitutions, *** 27396,27420 **** 16.23.1.2 Substitution in Mode Iterators ........................................ ! If an '.md' file construct uses mode iterators, each version of the construct will often need slightly different strings or modes. For example: ! * When a 'define_expand' defines several 'addM3' patterns (*note Standard Names::), each expander will need to use the appropriate mode name for M. ! * When a 'define_insn' defines several instruction patterns, each instruction will often use a different assembler mnemonic. ! * When a 'define_insn' requires operands with different modes, using an iterator for one of the operand modes usually requires a specific mode for the other operand(s). GCC supports such variations through a system of "mode attributes". ! There are two standard attributes: 'mode', which is the name of the mode ! in lower case, and 'MODE', which is the same thing in upper case. You ! can define other attributes using: (define_mode_attr NAME [(MODE1 "VALUE1") ... (MODEN "VALUEN")]) --- 27789,27813 ---- 16.23.1.2 Substitution in Mode Iterators ........................................ ! If an `.md' file construct uses mode iterators, each version of the construct will often need slightly different strings or modes. For example: ! * When a `define_expand' defines several `addM3' patterns (*note Standard Names::), each expander will need to use the appropriate mode name for M. ! * When a `define_insn' defines several instruction patterns, each instruction will often use a different assembler mnemonic. ! * When a `define_insn' requires operands with different modes, using an iterator for one of the operand modes usually requires a specific mode for the other operand(s). GCC supports such variations through a system of "mode attributes". ! There are two standard attributes: `mode', which is the name of the ! mode in lower case, and `MODE', which is the same thing in upper case. ! You can define other attributes using: (define_mode_attr NAME [(MODE1 "VALUE1") ... (MODEN "VALUEN")]) *************** can define other attributes using: *** 27422,27440 **** associated with MODEI. When GCC replaces some :ITERATOR with :MODE, it will scan each string ! and mode in the pattern for sequences of the form '', ! where ATTR is the name of a mode attribute. If the attribute is defined ! for MODE, the whole '<...>' sequence will be replaced by the appropriate ! attribute value. ! For example, suppose an '.md' file has: (define_mode_iterator P [(SI "Pmode == SImode") (DI "Pmode == DImode")]) (define_mode_attr load [(SI "lw") (DI "ld")]) ! If one of the patterns that uses ':P' contains the string ! '"\t%0,%1"', the 'SI' version of that pattern will use ! '"lw\t%0,%1"' and the 'DI' version will use '"ld\t%0,%1"'. Here is an example of using an attribute for a mode: --- 27815,27833 ---- associated with MODEI. When GCC replaces some :ITERATOR with :MODE, it will scan each string ! and mode in the pattern for sequences of the form `', ! where ATTR is the name of a mode attribute. If the attribute is ! defined for MODE, the whole `<...>' sequence will be replaced by the ! appropriate attribute value. ! For example, suppose an `.md' file has: (define_mode_iterator P [(SI "Pmode == SImode") (DI "Pmode == DImode")]) (define_mode_attr load [(SI "lw") (DI "ld")]) ! If one of the patterns that uses `:P' contains the string ! `"\t%0,%1"', the `SI' version of that pattern will use ! `"lw\t%0,%1"' and the `DI' version will use `"ld\t%0,%1"'. Here is an example of using an attribute for a mode: *************** attribute value. *** 27443,27449 **** (define_insn ... (sign_extend:LONG (match_operand: ...)) ...) ! The 'ITERATOR:' prefix may be omitted, in which case the substitution will be attempted for every iterator expansion.  --- 27836,27842 ---- (define_insn ... (sign_extend:LONG (match_operand: ...)) ...) ! The `ITERATOR:' prefix may be omitted, in which case the substitution will be attempted for every iterator expansion.  *************** and attributes (among others): *** 27458,27464 **** (define_mode_iterator GPR [SI (DI "TARGET_64BIT")]) (define_mode_attr d [(SI "") (DI "d")]) ! and uses the following template to define both 'subsi3' and 'subdi3': (define_insn "sub3" [(set (match_operand:GPR 0 "register_operand" "=d") --- 27851,27857 ---- (define_mode_iterator GPR [SI (DI "TARGET_64BIT")]) (define_mode_attr d [(SI "") (DI "d")]) ! and uses the following template to define both `subsi3' and `subdi3': (define_insn "sub3" [(set (match_operand:GPR 0 "register_operand" "=d") *************** times, once with all uses of NAME replac *** 27511,27518 **** replaced by CODE2, and so on. *Note Defining Mode Iterators::. It is possible to define attributes for codes as well as for modes. ! There are two standard code attributes: 'code', the name of the code in ! lower case, and 'CODE', the name of the code in upper case. Other attributes are defined using: (define_code_attr NAME [(CODE1 "VALUE1") ... (CODEN "VALUEN")]) --- 27904,27911 ---- replaced by CODE2, and so on. *Note Defining Mode Iterators::. It is possible to define attributes for codes as well as for modes. ! There are two standard code attributes: `code', the name of the code in ! lower case, and `CODE', the name of the code in upper case. Other attributes are defined using: (define_code_attr NAME [(CODE1 "VALUE1") ... (CODEN "VALUEN")]) *************** Iterators::. *** 27576,27590 **** (define_int_iterator NAME [(INT1 "COND1") ... (INTN "CONDN")]) ! defines a pseudo integer constant NAME that can be instantiated as INTI ! if condition CONDI is true. Each INT must have the same rtx format. ! *Note RTL Classes::. Int iterators can appear in only those rtx fields ! that have 'i' as the specifier. This means that each INT has to be a ! constant defined using define_constant or define_c_enum. As with mode and code iterators, each pattern that uses NAME will be ! expanded N times, once with all uses of NAME replaced by INT1, once with ! all uses replaced by INT2, and so on. *Note Defining Mode Iterators::. It is possible to define attributes for ints as well as for codes and modes. Attributes are defined using: --- 27969,27984 ---- (define_int_iterator NAME [(INT1 "COND1") ... (INTN "CONDN")]) ! defines a pseudo integer constant NAME that can be instantiated as ! INTI if condition CONDI is true. Each INT must have the same rtx ! format. *Note RTL Classes::. Int iterators can appear in only those ! rtx fields that have 'i' as the specifier. This means that each INT has ! to be a constant defined using define_constant or define_c_enum. As with mode and code iterators, each pattern that uses NAME will be ! expanded N times, once with all uses of NAME replaced by INT1, once ! with all uses replaced by INT2, and so on. *Note Defining Mode ! Iterators::. It is possible to define attributes for ints as well as for codes and modes. Attributes are defined using: *************** modes. Attributes are defined using: *** 27607,27613 **** [(set_attr "type" "neon_vqneg_vqabs")] ) - This is equivalent to: (define_insn "neon_vqabs" --- 28001,28006 ---- *************** modes. Attributes are defined using: *** 27630,27636 **** [(set_attr "type" "neon_vqneg_vqabs")] ) -  File: gccint.info, Node: Subst Iterators, Prev: Int Iterators, Up: Iterators --- 28023,28028 ---- *************** used in RTL-pattern. *** 27646,27659 **** Subst iterators transform templates in the following way: the templates are duplicated, the subst-attributes in these templates are replaced with the corresponding values, and a new attribute is implicitly added ! to the given 'define_insn'/'define_expand'. The name of the added ! attribute matches the name of 'define_subst'. Such attributes are ! declared implicitly, and it is not allowed to have a 'define_attr' named ! as a 'define_subst'. ! Each subst iterator is linked to a 'define_subst'. It is declared implicitly by the first appearance of the corresponding ! 'define_subst_attr', and it is not allowed to define it explicitly. Declarations of subst-attributes have the following syntax: --- 28038,28051 ---- Subst iterators transform templates in the following way: the templates are duplicated, the subst-attributes in these templates are replaced with the corresponding values, and a new attribute is implicitly added ! to the given `define_insn'/`define_expand'. The name of the added ! attribute matches the name of `define_subst'. Such attributes are ! declared implicitly, and it is not allowed to have a `define_attr' ! named as a `define_subst'. ! Each subst iterator is linked to a `define_subst'. It is declared implicitly by the first appearance of the corresponding ! `define_subst_attr', and it is not allowed to define it explicitly. Declarations of subst-attributes have the following syntax: *************** implicitly by the first appearance of th *** 27662,27671 **** "NO-SUBST-VALUE" "SUBST-APPLIED-VALUE") ! NAME is a string with which the given subst-attribute could be referred ! to. ! SUBST-NAME shows which 'define_subst' should be applied to an RTL-template if the given subst-attribute is present in the RTL-template. --- 28054,28063 ---- "NO-SUBST-VALUE" "SUBST-APPLIED-VALUE") ! NAME is a string with which the given subst-attribute could be ! referred to. ! SUBST-NAME shows which `define_subst' should be applied to an RTL-template if the given subst-attribute is present in the RTL-template. *************** File: gccint.info, Node: Target Macros, *** 27681,27704 **** 17 Target Description Macros and Functions ****************************************** ! In addition to the file 'MACHINE.md', a machine description includes a C ! header file conventionally given the name 'MACHINE.h' and a C source ! file named 'MACHINE.c'. The header file defines numerous macros that convey the information about the target machine that does not fit into ! the scheme of the '.md' file. The file 'tm.h' should be a link to ! 'MACHINE.h'. The header file 'config.h' includes 'tm.h' and most ! compiler source files include 'config.h'. The source file defines a ! variable 'targetm', which is a structure containing pointers to ! functions and data relating to the target machine. 'MACHINE.c' should also contain their definitions, if they are not defined elsewhere in ! GCC, and other functions called through the macros defined in the '.h' file. * Menu: ! * Target Structure:: The 'targetm' variable. * Driver:: Controlling how the driver runs the compilation passes. ! * Run-time Target:: Defining '-m' options like '-m68000' and '-m68020'. * Per-Function Data:: Defining data structures for per-function information. * Storage Layout:: Defining sizes and alignments of data. * Type Layout:: Defining sizes and properties of basic user data types. --- 28073,28096 ---- 17 Target Description Macros and Functions ****************************************** ! In addition to the file `MACHINE.md', a machine description includes a ! C header file conventionally given the name `MACHINE.h' and a C source ! file named `MACHINE.c'. The header file defines numerous macros that convey the information about the target machine that does not fit into ! the scheme of the `.md' file. The file `tm.h' should be a link to ! `MACHINE.h'. The header file `config.h' includes `tm.h' and most ! compiler source files include `config.h'. The source file defines a ! variable `targetm', which is a structure containing pointers to ! functions and data relating to the target machine. `MACHINE.c' should also contain their definitions, if they are not defined elsewhere in ! GCC, and other functions called through the macros defined in the `.h' file. * Menu: ! * Target Structure:: The `targetm' variable. * Driver:: Controlling how the driver runs the compilation passes. ! * Run-time Target:: Defining `-m' options like `-m68000' and `-m68020'. * Per-Function Data:: Defining data structures for per-function information. * Storage Layout:: Defining sizes and alignments of data. * Type Layout:: Defining sizes and properties of basic user data types. *************** file. *** 27709,27715 **** * Trampolines:: Code set up at run time to enter a nested function. * Library Calls:: Controlling how library routines are implicitly called. * Addressing Modes:: Defining addressing modes valid for memory operands. ! * Anchored Addresses:: Defining how '-fsection-anchors' should work. * Condition Code:: Defining how insns update the condition code. * Costs:: Defining relative costs of different operations. * Scheduling:: Adjusting the behavior of the instruction scheduler. --- 28101,28107 ---- * Trampolines:: Code set up at run time to enter a nested function. * Library Calls:: Controlling how library routines are implicitly called. * Addressing Modes:: Defining addressing modes valid for memory operands. ! * Anchored Addresses:: Defining how `-fsection-anchors' should work. * Condition Code:: Defining how insns update the condition code. * Costs:: Defining relative costs of different operations. * Scheduling:: Adjusting the behavior of the instruction scheduler. *************** file. *** 27719,27725 **** * Debugging Info:: Defining the format of debugging output. * Floating Point:: Handling floating point for cross-compilers. * Mode Switching:: Insertion of mode-switching instructions. ! * Target Attributes:: Defining target-specific uses of '__attribute__'. * Emulated TLS:: Emulated TLS support. * MIPS Coprocessors:: MIPS coprocessor support and how to customize it. * PCH Target:: Validity checking for precompiled headers. --- 28111,28117 ---- * Debugging Info:: Defining the format of debugging output. * Floating Point:: Handling floating point for cross-compilers. * Mode Switching:: Insertion of mode-switching instructions. ! * Target Attributes:: Defining target-specific uses of `__attribute__'. * Emulated TLS:: Emulated TLS support. * MIPS Coprocessors:: MIPS coprocessor support and how to customize it. * PCH Target:: Validity checking for precompiled headers. *************** file. *** 27730,27747 ****  File: gccint.info, Node: Target Structure, Next: Driver, Up: Target Macros ! 17.1 The Global 'targetm' Variable ================================== -- Variable: struct gcc_target targetm ! The target '.c' file must define the global 'targetm' variable which contains pointers to functions and data relating to the ! target machine. The variable is declared in 'target.h'; ! 'target-def.h' defines the macro 'TARGET_INITIALIZER' which is used ! to initialize the variable, and macros for the default initializers ! for elements of the structure. The '.c' file should override those ! macros for which the default definition is inappropriate. For ! example: #include "target.h" #include "target-def.h" --- 28122,28139 ----  File: gccint.info, Node: Target Structure, Next: Driver, Up: Target Macros ! 17.1 The Global `targetm' Variable ================================== -- Variable: struct gcc_target targetm ! The target `.c' file must define the global `targetm' variable which contains pointers to functions and data relating to the ! target machine. The variable is declared in `target.h'; ! `target-def.h' defines the macro `TARGET_INITIALIZER' which is ! used to initialize the variable, and macros for the default ! initializers for elements of the structure. The `.c' file should ! override those macros for which the default definition is ! inappropriate. For example: #include "target.h" #include "target-def.h" *************** File: gccint.info, Node: Target Structu *** 27752,27782 **** struct gcc_target targetm = TARGET_INITIALIZER; ! Where a macro should be defined in the '.c' file in this manner to form ! part of the 'targetm' structure, it is documented below as a "Target Hook" with a prototype. Many macros will change in future from being ! defined in the '.h' file to being part of the 'targetm' structure. ! Similarly, there is a 'targetcm' variable for hooks that are specific to front ends for C-family languages, documented as "C Target Hook". ! This is declared in 'c-family/c-target.h', the initializer ! 'TARGETCM_INITIALIZER' in 'c-family/c-target-def.h'. If targets ! initialize 'targetcm' themselves, they should set ! 'target_has_targetcm=yes' in 'config.gcc'; otherwise a default definition is used. ! Similarly, there is a 'targetm_common' variable for hooks that are shared between the compiler driver and the compilers proper, documented ! as "Common Target Hook". This is declared in 'common/common-target.h', ! the initializer 'TARGETM_COMMON_INITIALIZER' in ! 'common/common-target-def.h'. If targets initialize 'targetm_common' ! themselves, they should set 'target_has_targetm_common=yes' in ! 'config.gcc'; otherwise a default definition is used.  File: gccint.info, Node: Driver, Next: Run-time Target, Prev: Target Structure, Up: Target Macros ! 17.2 Controlling the Compilation Driver, 'gcc' ============================================== You can control the compilation driver. --- 28144,28174 ---- struct gcc_target targetm = TARGET_INITIALIZER; ! Where a macro should be defined in the `.c' file in this manner to form ! part of the `targetm' structure, it is documented below as a "Target Hook" with a prototype. Many macros will change in future from being ! defined in the `.h' file to being part of the `targetm' structure. ! Similarly, there is a `targetcm' variable for hooks that are specific to front ends for C-family languages, documented as "C Target Hook". ! This is declared in `c-family/c-target.h', the initializer ! `TARGETCM_INITIALIZER' in `c-family/c-target-def.h'. If targets ! initialize `targetcm' themselves, they should set ! `target_has_targetcm=yes' in `config.gcc'; otherwise a default definition is used. ! Similarly, there is a `targetm_common' variable for hooks that are shared between the compiler driver and the compilers proper, documented ! as "Common Target Hook". This is declared in `common/common-target.h', ! the initializer `TARGETM_COMMON_INITIALIZER' in ! `common/common-target-def.h'. If targets initialize `targetm_common' ! themselves, they should set `target_has_targetm_common=yes' in ! `config.gcc'; otherwise a default definition is used.  File: gccint.info, Node: Driver, Next: Run-time Target, Prev: Target Structure, Up: Target Macros ! 17.2 Controlling the Compilation Driver, `gcc' ============================================== You can control the compilation driver. *************** You can control the compilation driver. *** 27786,27796 **** initializer for an array of strings, with no surrounding braces. The driver applies these specs to its own command line between ! loading default 'specs' files (but not command-line specified ones) ! and choosing the multilib directory or running any subcommands. It ! applies them in the order given, so each spec can depend on the ! options added by earlier ones. It is also possible to remove ! options using '%' in such a case, the header provided may not conform to C99, depending on the type in question. The defaults for all of these macros are null pointers. --- 29642,29660 ---- -- Macro: UINT_FAST64_TYPE -- Macro: INTPTR_TYPE -- Macro: UINTPTR_TYPE ! C expressions for the standard types `sig_atomic_t', `int8_t', ! `int16_t', `int32_t', `int64_t', `uint8_t', `uint16_t', ! `uint32_t', `uint64_t', `int_least8_t', `int_least16_t', ! `int_least32_t', `int_least64_t', `uint_least8_t', ! `uint_least16_t', `uint_least32_t', `uint_least64_t', ! `int_fast8_t', `int_fast16_t', `int_fast32_t', `int_fast64_t', ! `uint_fast8_t', `uint_fast16_t', `uint_fast32_t', `uint_fast64_t', ! `intptr_t', and `uintptr_t'. See `SIZE_TYPE' above for more ! information. If any of these macros evaluates to a null pointer, the corresponding type is not supported; if GCC is configured to ! provide `' in such a case, the header provided may not conform to C99, depending on the type in question. The defaults for all of these macros are null pointers. *************** languages, rather than to fundamental as *** 29278,29299 **** vtable_index is odd, we can distinguish which variant of the union is in use. But, on some platforms function pointers can be odd, and so this doesn't work. In that case, we use the low-order bit ! of the 'delta' field, and shift the remainder of the 'delta' field to the left. GCC will automatically make the right selection about where to ! store this bit using the 'FUNCTION_BOUNDARY' setting for your platform. However, some platforms such as ARM/Thumb have ! 'FUNCTION_BOUNDARY' set such that functions always start at even addresses, but the lowest bit of pointers to functions indicate whether the function at that address is in ARM or Thumb mode. If ! this is the case of your architecture, you should define this macro ! to 'ptrmemfunc_vbit_in_delta'. In general, you should not have to define this macro. On architectures in which function addresses are always even, ! according to 'FUNCTION_BOUNDARY', GCC will automatically define ! this macro to 'ptrmemfunc_vbit_in_pfn'. -- Macro: TARGET_VTABLE_USES_DESCRIPTORS Normally, the C++ compiler uses function pointers in vtables. This --- 29677,29698 ---- vtable_index is odd, we can distinguish which variant of the union is in use. But, on some platforms function pointers can be odd, and so this doesn't work. In that case, we use the low-order bit ! of the `delta' field, and shift the remainder of the `delta' field to the left. GCC will automatically make the right selection about where to ! store this bit using the `FUNCTION_BOUNDARY' setting for your platform. However, some platforms such as ARM/Thumb have ! `FUNCTION_BOUNDARY' set such that functions always start at even addresses, but the lowest bit of pointers to functions indicate whether the function at that address is in ARM or Thumb mode. If ! this is the case of your architecture, you should define this ! macro to `ptrmemfunc_vbit_in_delta'. In general, you should not have to define this macro. On architectures in which function addresses are always even, ! according to `FUNCTION_BOUNDARY', GCC will automatically define ! this macro to `ptrmemfunc_vbit_in_pfn'. -- Macro: TARGET_VTABLE_USES_DESCRIPTORS Normally, the C++ compiler uses function pointers in vtables. This *************** languages, rather than to fundamental as *** 29310,29321 **** By default, the vtable entries are void pointers, the so the alignment is the same as pointer alignment. The value of this macro specifies the alignment of the vtable entry in bits. It ! should be defined only when special alignment is necessary. */ -- Macro: TARGET_VTABLE_DATA_ENTRY_DISTANCE There are a few non-descriptor entries in the vtable at offsets below zero. If these entries must be padded (say, to preserve the ! alignment specified by 'TARGET_VTABLE_ENTRY_ALIGN'), set this to the number of words in each data entry.  --- 29709,29720 ---- By default, the vtable entries are void pointers, the so the alignment is the same as pointer alignment. The value of this macro specifies the alignment of the vtable entry in bits. It ! should be defined only when special alignment is necessary. */ -- Macro: TARGET_VTABLE_DATA_ENTRY_DISTANCE There are a few non-descriptor entries in the vtable at offsets below zero. If these entries must be padded (say, to preserve the ! alignment specified by `TARGET_VTABLE_ENTRY_ALIGN'), set this to the number of words in each data entry.  *************** Registers have various characteristics. *** 29352,29360 **** -- Macro: FIRST_PSEUDO_REGISTER Number of hardware registers known to the compiler. They receive ! numbers 0 through 'FIRST_PSEUDO_REGISTER-1'; thus, the first pseudo ! register's number really is assigned the number ! 'FIRST_PSEUDO_REGISTER'. -- Macro: FIXED_REGISTERS An initializer that says which registers are used for fixed --- 29751,29759 ---- -- Macro: FIRST_PSEUDO_REGISTER Number of hardware registers known to the compiler. They receive ! numbers 0 through `FIRST_PSEUDO_REGISTER-1'; thus, the first ! pseudo register's number really is assigned the number ! `FIRST_PSEUDO_REGISTER'. -- Macro: FIXED_REGISTERS An initializer that says which registers are used for fixed *************** Registers have various characteristics. *** 29373,29398 **** The table initialized from this macro, and the table initialized by the following one, may be overridden at run time either automatically, by the actions of the macro ! 'CONDITIONAL_REGISTER_USAGE', or by the user with the command ! options '-ffixed-REG', '-fcall-used-REG' and '-fcall-saved-REG'. -- Macro: CALL_USED_REGISTERS ! Like 'FIXED_REGISTERS' but has 1 for each register that is clobbered (in general) by function calls as well as for fixed registers. This macro therefore identifies the registers that are not available for general allocation of values that must live across function calls. ! If a register has 0 in 'CALL_USED_REGISTERS', the compiler automatically saves it on function entry and restores it on function exit, if the register is used within the function. -- Macro: CALL_REALLY_USED_REGISTERS ! Like 'CALL_USED_REGISTERS' except this macro doesn't require that ! the entire set of 'FIXED_REGISTERS' be included. ! ('CALL_USED_REGISTERS' must be a superset of 'FIXED_REGISTERS'). This macro is optional. If not specified, it defaults to the value ! of 'CALL_USED_REGISTERS'. -- Macro: HARD_REGNO_CALL_PART_CLOBBERED (REGNO, MODE) A C expression that is nonzero if it is not permissible to store a --- 29772,29797 ---- The table initialized from this macro, and the table initialized by the following one, may be overridden at run time either automatically, by the actions of the macro ! `CONDITIONAL_REGISTER_USAGE', or by the user with the command ! options `-ffixed-REG', `-fcall-used-REG' and `-fcall-saved-REG'. -- Macro: CALL_USED_REGISTERS ! Like `FIXED_REGISTERS' but has 1 for each register that is clobbered (in general) by function calls as well as for fixed registers. This macro therefore identifies the registers that are not available for general allocation of values that must live across function calls. ! If a register has 0 in `CALL_USED_REGISTERS', the compiler automatically saves it on function entry and restores it on function exit, if the register is used within the function. -- Macro: CALL_REALLY_USED_REGISTERS ! Like `CALL_USED_REGISTERS' except this macro doesn't require that ! the entire set of `FIXED_REGISTERS' be included. ! (`CALL_USED_REGISTERS' must be a superset of `FIXED_REGISTERS'). This macro is optional. If not specified, it defaults to the value ! of `CALL_USED_REGISTERS'. -- Macro: HARD_REGNO_CALL_PART_CLOBBERED (REGNO, MODE) A C expression that is nonzero if it is not permissible to store a *************** Registers have various characteristics. *** 29402,29451 **** do not preserve the entire contents of a register across a call. -- Target Hook: void TARGET_CONDITIONAL_REGISTER_USAGE (void) ! This hook may conditionally modify five variables 'fixed_regs', ! 'call_used_regs', 'global_regs', 'reg_names', and ! 'reg_class_contents', to take into account any dependence of these register sets on target flags. The first three of these are of ! type 'char []' (interpreted as Boolean vectors). 'global_regs' is ! a 'const char *[]', and 'reg_class_contents' is a 'HARD_REG_SET'. ! Before the macro is called, 'fixed_regs', 'call_used_regs', ! 'reg_class_contents', and 'reg_names' have been initialized from ! 'FIXED_REGISTERS', 'CALL_USED_REGISTERS', 'REG_CLASS_CONTENTS', and ! 'REGISTER_NAMES', respectively. 'global_regs' has been cleared, ! and any '-ffixed-REG', '-fcall-used-REG' and '-fcall-saved-REG' ! command options have been applied. If the usage of an entire class of registers depends on the target flags, you may indicate this to GCC by using this macro to modify ! 'fixed_regs' and 'call_used_regs' to 1 for each of the registers in ! the classes which should not be used by GCC. Also make ! 'define_register_constraint's return 'NO_REGS' for constraints that ! shouldn't be used. ! (However, if this class is not included in 'GENERAL_REGS' and all of the insn patterns whose constraints permit this class are controlled by target switches, then GCC will automatically avoid using these registers when the target switches are opposed to them.) -- Macro: INCOMING_REGNO (OUT) ! Define this macro if the target machine has register windows. This ! C expression returns the register number as seen by the called ! function corresponding to the register number OUT as seen by the ! calling function. Return OUT if register number OUT is not an ! outbound register. -- Macro: OUTGOING_REGNO (IN) ! Define this macro if the target machine has register windows. This ! C expression returns the register number as seen by the calling ! function corresponding to the register number IN as seen by the ! called function. Return IN if register number IN is not an inbound ! register. -- Macro: LOCAL_REGNO (REGNO) ! Define this macro if the target machine has register windows. This ! C expression returns true if the register is call-saved but is in ! the register window. Unlike most call-saved registers, such registers need not be explicitly restored on function exit or during non-local gotos. --- 29801,29850 ---- do not preserve the entire contents of a register across a call. -- Target Hook: void TARGET_CONDITIONAL_REGISTER_USAGE (void) ! This hook may conditionally modify five variables `fixed_regs', ! `call_used_regs', `global_regs', `reg_names', and ! `reg_class_contents', to take into account any dependence of these register sets on target flags. The first three of these are of ! type `char []' (interpreted as Boolean vectors). `global_regs' is ! a `const char *[]', and `reg_class_contents' is a `HARD_REG_SET'. ! Before the macro is called, `fixed_regs', `call_used_regs', ! `reg_class_contents', and `reg_names' have been initialized from ! `FIXED_REGISTERS', `CALL_USED_REGISTERS', `REG_CLASS_CONTENTS', ! and `REGISTER_NAMES', respectively. `global_regs' has been ! cleared, and any `-ffixed-REG', `-fcall-used-REG' and ! `-fcall-saved-REG' command options have been applied. If the usage of an entire class of registers depends on the target flags, you may indicate this to GCC by using this macro to modify ! `fixed_regs' and `call_used_regs' to 1 for each of the registers ! in the classes which should not be used by GCC. Also make ! `define_register_constraint's return `NO_REGS' for constraints ! that shouldn't be used. ! (However, if this class is not included in `GENERAL_REGS' and all of the insn patterns whose constraints permit this class are controlled by target switches, then GCC will automatically avoid using these registers when the target switches are opposed to them.) -- Macro: INCOMING_REGNO (OUT) ! Define this macro if the target machine has register windows. ! This C expression returns the register number as seen by the ! called function corresponding to the register number OUT as seen ! by the calling function. Return OUT if register number OUT is not ! an outbound register. -- Macro: OUTGOING_REGNO (IN) ! Define this macro if the target machine has register windows. ! This C expression returns the register number as seen by the ! calling function corresponding to the register number IN as seen ! by the called function. Return IN if register number IN is not an ! inbound register. -- Macro: LOCAL_REGNO (REGNO) ! Define this macro if the target machine has register windows. ! This C expression returns true if the register is call-saved but ! is in the register window. Unlike most call-saved registers, such registers need not be explicitly restored on function exit or during non-local gotos. *************** Registers are allocated in order. *** 29472,29478 **** One use of this macro is on machines where the highest numbered registers must always be saved and the save-multiple-registers instruction supports only sequences of consecutive registers. On ! such machines, define 'REG_ALLOC_ORDER' to be an initializer that lists the highest numbered allocable register first. -- Macro: ADJUST_REG_ALLOC_ORDER --- 29871,29877 ---- One use of this macro is on machines where the highest numbered registers must always be saved and the save-multiple-registers instruction supports only sequences of consecutive registers. On ! such machines, define `REG_ALLOC_ORDER' to be an initializer that lists the highest numbered allocable register first. -- Macro: ADJUST_REG_ALLOC_ORDER *************** Registers are allocated in order. *** 29480,29501 **** allocate hard registers for pseudo-registers local to a basic block. ! Store the desired register order in the array 'reg_alloc_order'. Element 0 should be the register to allocate first; element 1, the next register; and so on. The macro body should not assume anything about the contents of ! 'reg_alloc_order' before execution of the macro. On most machines, it is not necessary to define this macro. -- Macro: HONOR_REG_ALLOC_ORDER Normally, IRA tries to estimate the costs for saving a register in ! the prologue and restoring it in the epilogue. This discourages it ! from using call-saved registers. If a machine wants to ensure that ! IRA allocates registers in the order given by REG_ALLOC_ORDER even ! if some call-saved registers appear earlier than call-used ones, ! then define this macro as a C expression to nonzero. Default is 0. -- Macro: IRA_HARD_REGNO_ADD_COST_MULTIPLIER (REGNO) In some case register allocation order is not enough for the --- 29879,29901 ---- allocate hard registers for pseudo-registers local to a basic block. ! Store the desired register order in the array `reg_alloc_order'. Element 0 should be the register to allocate first; element 1, the next register; and so on. The macro body should not assume anything about the contents of ! `reg_alloc_order' before execution of the macro. On most machines, it is not necessary to define this macro. -- Macro: HONOR_REG_ALLOC_ORDER Normally, IRA tries to estimate the costs for saving a register in ! the prologue and restoring it in the epilogue. This discourages ! it from using call-saved registers. If a machine wants to ensure ! that IRA allocates registers in the order given by REG_ALLOC_ORDER ! even if some call-saved registers appear earlier than call-used ! ones, then define this macro as a C expression to nonzero. Default ! is 0. -- Macro: IRA_HARD_REGNO_ADD_COST_MULTIPLIER (REGNO) In some case register allocation order is not enough for the *************** Registers are allocated in order. *** 29504,29510 **** based on REGNO. The cost of using REGNO for a pseudo will be increased by approximately the pseudo's usage frequency times the value returned by this macro. Not defining this macro is ! equivalent to having it always return '0.0'. On most machines, it is not necessary to define this macro. --- 29904,29910 ---- based on REGNO. The cost of using REGNO for a pseudo will be increased by approximately the pseudo's usage frequency times the value returned by this macro. Not defining this macro is ! equivalent to having it always return `0.0'. On most machines, it is not necessary to define this macro. *************** consecutive registers are needed for a g *** 29521,29529 **** -- Macro: HARD_REGNO_NREGS (REGNO, MODE) A C expression for the number of consecutive hard registers, starting at register number REGNO, required to hold a value of mode ! MODE. This macro must never return zero, even if a register cannot ! hold the requested mode - indicate that with HARD_REGNO_MODE_OK ! and/or CANNOT_CHANGE_MODE_CLASS instead. On a machine where all registers are exactly one word, a suitable definition of this macro is --- 29921,29929 ---- -- Macro: HARD_REGNO_NREGS (REGNO, MODE) A C expression for the number of consecutive hard registers, starting at register number REGNO, required to hold a value of mode ! MODE. This macro must never return zero, even if a register ! cannot hold the requested mode - indicate that with ! HARD_REGNO_MODE_OK and/or CANNOT_CHANGE_MODE_CLASS instead. On a machine where all registers are exactly one word, a suitable definition of this macro is *************** consecutive registers are needed for a g *** 29538,29561 **** in registers starting at register number REGNO (as determined by multiplying GCC's notion of the size of the register when containing this mode by the number of registers returned by ! 'HARD_REGNO_NREGS'). By default this is zero. For example, if a floating-point value is stored in three 32-bit registers but takes up 128 bits in memory, then this would be nonzero. This macros only needs to be defined if there are cases where ! 'subreg_get_info' would otherwise wrongly determine that a 'subreg' ! can be represented by an offset to the register number, when in ! fact such a 'subreg' would contain some of the padding not stored ! in registers and so not be representable. -- Macro: HARD_REGNO_NREGS_WITH_PADDING (REGNO, MODE) For values of REGNO and MODE for which ! 'HARD_REGNO_NREGS_HAS_PADDING' returns nonzero, a C expression returning the greater number of registers required to hold the ! value including any padding. In the example above, the value would ! be four. -- Macro: REGMODE_NATURAL_SIZE (MODE) Define this macro if the natural size of registers that hold values --- 29938,29961 ---- in registers starting at register number REGNO (as determined by multiplying GCC's notion of the size of the register when containing this mode by the number of registers returned by ! `HARD_REGNO_NREGS'). By default this is zero. For example, if a floating-point value is stored in three 32-bit registers but takes up 128 bits in memory, then this would be nonzero. This macros only needs to be defined if there are cases where ! `subreg_get_info' would otherwise wrongly determine that a ! `subreg' can be represented by an offset to the register number, ! when in fact such a `subreg' would contain some of the padding not ! stored in registers and so not be representable. -- Macro: HARD_REGNO_NREGS_WITH_PADDING (REGNO, MODE) For values of REGNO and MODE for which ! `HARD_REGNO_NREGS_HAS_PADDING' returns nonzero, a C expression returning the greater number of registers required to hold the ! value including any padding. In the example above, the value ! would be four. -- Macro: REGMODE_NATURAL_SIZE (MODE) Define this macro if the natural size of registers that hold values *************** consecutive registers are needed for a g *** 29582,29629 **** reject odd register numbers for such modes. The minimum requirement for a mode to be OK in a register is that ! the 'movMODE' instruction pattern support moves between the register and other hard register in the same class and that moving a value into the register and back out not alter it. ! Since the same instruction used to move 'word_mode' will work for all narrower integer modes, it is not necessary on any machine for ! 'HARD_REGNO_MODE_OK' to distinguish between these modes, provided ! you define patterns 'movhi', etc., to take advantage of this. This ! is useful because of the interaction between 'HARD_REGNO_MODE_OK' ! and 'MODES_TIEABLE_P'; it is very desirable for all integer modes to be tieable. Many machines have special registers for floating point arithmetic. Often people assume that floating point machine modes are allowed ! only in floating point registers. This is not true. Any registers ! that can hold integers can safely _hold_ a floating point machine ! mode, whether or not floating arithmetic can be done on it in those ! registers. Integer move instructions can be used to move the ! values. On some machines, though, the converse is true: fixed-point machine modes may not go in floating registers. This is true if the floating registers normalize any value stored in them, because storing a non-floating value there would garble it. In this case, ! 'HARD_REGNO_MODE_OK' should reject fixed-point machine modes in floating registers. But if the floating registers do not automatically normalize, if you can store any bit pattern in one ! and retrieve it unchanged without a trap, then any machine mode may ! go in a floating register, so you can define this macro to say so. The primary significance of special floating registers is rather that they are the registers acceptable in floating point arithmetic instructions. However, this is of no concern to ! 'HARD_REGNO_MODE_OK'. You handle it by writing the proper constraints for those instructions. On some machines, the floating registers are especially slow to ! access, so that it is better to store a value in a stack frame than ! in such a register if floating point arithmetic is not being done. ! As long as the floating registers are not in class 'GENERAL_REGS', ! they will not be used unless some pattern's constraint asks for ! one. -- Macro: HARD_REGNO_RENAME_OK (FROM, TO) A C expression that is nonzero if it is OK to rename a hard --- 29982,30030 ---- reject odd register numbers for such modes. The minimum requirement for a mode to be OK in a register is that ! the `movMODE' instruction pattern support moves between the register and other hard register in the same class and that moving a value into the register and back out not alter it. ! Since the same instruction used to move `word_mode' will work for all narrower integer modes, it is not necessary on any machine for ! `HARD_REGNO_MODE_OK' to distinguish between these modes, provided ! you define patterns `movhi', etc., to take advantage of this. This ! is useful because of the interaction between `HARD_REGNO_MODE_OK' ! and `MODES_TIEABLE_P'; it is very desirable for all integer modes to be tieable. Many machines have special registers for floating point arithmetic. Often people assume that floating point machine modes are allowed ! only in floating point registers. This is not true. Any ! registers that can hold integers can safely _hold_ a floating ! point machine mode, whether or not floating arithmetic can be done ! on it in those registers. Integer move instructions can be used ! to move the values. On some machines, though, the converse is true: fixed-point machine modes may not go in floating registers. This is true if the floating registers normalize any value stored in them, because storing a non-floating value there would garble it. In this case, ! `HARD_REGNO_MODE_OK' should reject fixed-point machine modes in floating registers. But if the floating registers do not automatically normalize, if you can store any bit pattern in one ! and retrieve it unchanged without a trap, then any machine mode ! may go in a floating register, so you can define this macro to say ! so. The primary significance of special floating registers is rather that they are the registers acceptable in floating point arithmetic instructions. However, this is of no concern to ! `HARD_REGNO_MODE_OK'. You handle it by writing the proper constraints for those instructions. On some machines, the floating registers are especially slow to ! access, so that it is better to store a value in a stack frame ! than in such a register if floating point arithmetic is not being ! done. As long as the floating registers are not in class ! `GENERAL_REGS', they will not be used unless some pattern's ! constraint asks for one. -- Macro: HARD_REGNO_RENAME_OK (FROM, TO) A C expression that is nonzero if it is OK to rename a hard *************** consecutive registers are needed for a g *** 29639,29667 **** A C expression that is nonzero if a value of mode MODE1 is accessible in mode MODE2 without copying. ! If 'HARD_REGNO_MODE_OK (R, MODE1)' and 'HARD_REGNO_MODE_OK (R, ! MODE2)' are always the same for any R, then 'MODES_TIEABLE_P (MODE1, MODE2)' should be nonzero. If they differ for any R, you ! should define this macro to return zero unless some other mechanism ! ensures the accessibility of the value in a narrower mode. You should define this macro to return nonzero in as many cases as possible since doing so will allow GCC to perform better register allocation. -- Target Hook: bool TARGET_HARD_REGNO_SCRATCH_OK (unsigned int REGNO) ! This target hook should return 'true' if it is OK to use a hard register REGNO as scratch reg in peephole2. One common use of this macro is to prevent using of a register that is not saved by a prologue in an interrupt handler. ! The default version of this hook always returns 'true'. -- Macro: AVOID_CCMODE_COPIES Define this macro if the compiler should avoid copies to/from ! 'CCmode' registers. You should only define this macro if support ! for copying to/from 'CCmode' is incomplete.  File: gccint.info, Node: Leaf Functions, Next: Stack Registers, Prev: Values in Registers, Up: Registers --- 30040,30069 ---- A C expression that is nonzero if a value of mode MODE1 is accessible in mode MODE2 without copying. ! If `HARD_REGNO_MODE_OK (R, MODE1)' and `HARD_REGNO_MODE_OK (R, ! MODE2)' are always the same for any R, then `MODES_TIEABLE_P (MODE1, MODE2)' should be nonzero. If they differ for any R, you ! should define this macro to return zero unless some other ! mechanism ensures the accessibility of the value in a narrower ! mode. You should define this macro to return nonzero in as many cases as possible since doing so will allow GCC to perform better register allocation. -- Target Hook: bool TARGET_HARD_REGNO_SCRATCH_OK (unsigned int REGNO) ! This target hook should return `true' if it is OK to use a hard register REGNO as scratch reg in peephole2. One common use of this macro is to prevent using of a register that is not saved by a prologue in an interrupt handler. ! The default version of this hook always returns `true'. -- Macro: AVOID_CCMODE_COPIES Define this macro if the compiler should avoid copies to/from ! `CCmode' registers. You should only define this macro if support ! for copying to/from `CCmode' is incomplete.  File: gccint.info, Node: Leaf Functions, Next: Stack Registers, Prev: Values in Registers, Up: Registers *************** File: gccint.info, Node: Leaf Functions *** 29670,29685 **** ------------------------------ On some machines, a leaf function (i.e., one which makes no calls) can ! run more efficiently if it does not make its own register window. Often ! this means it is required to receive its arguments in the registers ! where they are passed by the caller, instead of the registers where they ! would normally arrive. The special treatment for leaf functions generally applies only when other conditions are met; for example, often they may use only those registers for its own variables and temporaries. We use the term "leaf ! function" to mean a function that is suitable for this special handling, ! so that functions with no calls are not necessarily "leaf functions". GCC assigns register numbers before it knows whether the function is suitable for leaf function treatment. So it needs to renumber the --- 30072,30088 ---- ------------------------------ On some machines, a leaf function (i.e., one which makes no calls) can ! run more efficiently if it does not make its own register window. ! Often this means it is required to receive its arguments in the ! registers where they are passed by the caller, instead of the registers ! where they would normally arrive. The special treatment for leaf functions generally applies only when other conditions are met; for example, often they may use only those registers for its own variables and temporaries. We use the term "leaf ! function" to mean a function that is suitable for this special ! handling, so that functions with no calls are not necessarily "leaf ! functions". GCC assigns register numbers before it knows whether the function is suitable for leaf function treatment. So it needs to renumber the *************** accomplish this. *** 29691,29698 **** contains 1 for a register that is allowable in a candidate for leaf function treatment. ! If leaf function treatment involves renumbering the registers, then ! the registers marked here should be the ones before renumbering--those that GCC would ordinarily allocate. The registers which will actually be used in the assembler code, after renumbering, should not be marked with 1 in this vector. --- 30094,30101 ---- contains 1 for a register that is allowable in a candidate for leaf function treatment. ! If leaf function treatment involves renumbering the registers, ! then the registers marked here should be the ones before renumbering--those that GCC would ordinarily allocate. The registers which will actually be used in the assembler code, after renumbering, should not be marked with 1 in this vector. *************** accomplish this. *** 29713,29728 **** optimize the treatment of leaf functions, and registers need to be renumbered to do this. ! 'TARGET_ASM_FUNCTION_PROLOGUE' and 'TARGET_ASM_FUNCTION_EPILOGUE' must usually treat leaf functions specially. They can test the C variable ! 'current_function_is_leaf' which is nonzero for leaf functions. ! 'current_function_is_leaf' is set prior to local register allocation and ! is valid for the remaining compiler passes. They can also test the C ! variable 'current_function_uses_only_leaf_regs' which is nonzero for leaf functions which only use leaf registers. ! 'current_function_uses_only_leaf_regs' is valid after all passes that modify the instructions have been run and is only useful if ! 'LEAF_REGISTERS' is defined.  File: gccint.info, Node: Stack Registers, Prev: Leaf Functions, Up: Registers --- 30116,30131 ---- optimize the treatment of leaf functions, and registers need to be renumbered to do this. ! `TARGET_ASM_FUNCTION_PROLOGUE' and `TARGET_ASM_FUNCTION_EPILOGUE' must usually treat leaf functions specially. They can test the C variable ! `current_function_is_leaf' which is nonzero for leaf functions. ! `current_function_is_leaf' is set prior to local register allocation ! and is valid for the remaining compiler passes. They can also test the ! C variable `current_function_uses_only_leaf_regs' which is nonzero for leaf functions which only use leaf registers. ! `current_function_uses_only_leaf_regs' is valid after all passes that modify the instructions have been run and is only useful if ! `LEAF_REGISTERS' is defined.  File: gccint.info, Node: Stack Registers, Prev: Leaf Functions, Up: Registers *************** stack. *** 29739,29747 **** they must be consecutively numbered. Furthermore, the existing support for stack-like registers is specific to the 80387 floating point coprocessor. If you have a new architecture that uses stack-like ! registers, you will need to do substantial work on 'reg-stack.c' and ! write your machine description to cooperate with it, as well as defining ! these macros. -- Macro: STACK_REGS Define this if the machine has any stack-like registers. --- 30142,30150 ---- they must be consecutively numbered. Furthermore, the existing support for stack-like registers is specific to the 80387 floating point coprocessor. If you have a new architecture that uses stack-like ! registers, you will need to do substantial work on `reg-stack.c' and ! write your machine description to cooperate with it, as well as ! defining these macros. -- Macro: STACK_REGS Define this if the machine has any stack-like registers. *************** these macros. *** 29755,29762 **** of the stack. -- Macro: LAST_STACK_REG ! The number of the last stack-like register. This one is the bottom ! of the stack.  File: gccint.info, Node: Register Classes, Next: Stack and Calling, Prev: Registers, Up: Target Macros --- 30158,30165 ---- of the stack. -- Macro: LAST_STACK_REG ! The number of the last stack-like register. This one is the ! bottom of the stack.  File: gccint.info, Node: Register Classes, Next: Stack and Calling, Prev: Registers, Up: Target Macros *************** register classes that are allowed as ope *** 29776,29810 **** patterns. In general, each register will belong to several classes. In fact, one ! class must be named 'ALL_REGS' and contain all the registers. Another ! class must be named 'NO_REGS' and contain no registers. Often the union ! of two classes will be another class; however, this is not required. ! One of the classes must be named 'GENERAL_REGS'. There is nothing ! terribly special about the name, but the operand constraint letters 'r' ! and 'g' specify this class. If 'GENERAL_REGS' is the same as ! 'ALL_REGS', just define it as a macro which expands to 'ALL_REGS'. ! Order the classes so that if class X is contained in class Y then X has ! a lower class number than Y. ! The way classes other than 'GENERAL_REGS' are specified in operand constraints is through machine-dependent operand constraint letters. You can define such letters to correspond to various classes, then use them in operand constraints. You must define the narrowest register classes for allocatable ! registers, so that each class either has no subclasses, or that for some ! mode, the move cost between registers within the class is cheaper than ! moving a register in the class to or from memory (*note Costs::). You should define a class for the union of two classes whenever some instruction allows both classes. For example, if an instruction allows ! either a floating point (coprocessor) register or a general register for ! a certain operand, you should define a class 'FLOAT_OR_GENERAL_REGS' ! which includes both of them. Otherwise you will get suboptimal code, or ! even internal compiler errors when reload cannot find a register in the ! class computed via 'reg_class_subunion'. You must also specify certain redundant information about the register classes: for each class, which classes contain it and which ones are --- 30179,30214 ---- patterns. In general, each register will belong to several classes. In fact, one ! class must be named `ALL_REGS' and contain all the registers. Another ! class must be named `NO_REGS' and contain no registers. Often the ! union of two classes will be another class; however, this is not ! required. ! One of the classes must be named `GENERAL_REGS'. There is nothing ! terribly special about the name, but the operand constraint letters `r' ! and `g' specify this class. If `GENERAL_REGS' is the same as ! `ALL_REGS', just define it as a macro which expands to `ALL_REGS'. ! Order the classes so that if class X is contained in class Y then X ! has a lower class number than Y. ! The way classes other than `GENERAL_REGS' are specified in operand constraints is through machine-dependent operand constraint letters. You can define such letters to correspond to various classes, then use them in operand constraints. You must define the narrowest register classes for allocatable ! registers, so that each class either has no subclasses, or that for ! some mode, the move cost between registers within the class is cheaper ! than moving a register in the class to or from memory (*note Costs::). You should define a class for the union of two classes whenever some instruction allows both classes. For example, if an instruction allows ! either a floating point (coprocessor) register or a general register ! for a certain operand, you should define a class `FLOAT_OR_GENERAL_REGS' ! which includes both of them. Otherwise you will get suboptimal code, ! or even internal compiler errors when reload cannot find a register in ! the class computed via `reg_class_subunion'. You must also specify certain redundant information about the register classes: for each class, which classes contain it and which ones are *************** in their union. *** 29815,29843 **** certain class, all the registers used must belong to that class. Therefore, register classes cannot be used to enforce a requirement for a register pair to start with an even-numbered register. The way to ! specify this requirement is with 'HARD_REGNO_MODE_OK'. Register classes used for input-operands of bitwise-and or shift instructions have a special requirement: each such class must have, for each fixed-point machine mode, a subclass whose registers can transfer that mode to or from memory. For example, on some machines, the ! operations for single-byte values ('QImode') are limited to certain registers. When this is so, each register class that is used in a bitwise-and or shift instruction must have a subclass consisting of registers from which single-byte values can be loaded or stored. This ! is so that 'PREFERRED_RELOAD_CLASS' can always have a possible value to return. -- Data type: enum reg_class ! An enumerated type that must be defined with all the register class ! names as enumerated values. 'NO_REGS' must be first. 'ALL_REGS' ! must be the last register class, followed by one more enumerated ! value, 'LIM_REG_CLASSES', which is not a register class but rather ! tells how many classes there are. ! Each register class has a number, which is the value of casting the ! class name to type 'int'. The number serves as an index in many of ! the tables described below. -- Macro: N_REG_CLASSES The number of distinct register classes, defined as follows: --- 30219,30247 ---- certain class, all the registers used must belong to that class. Therefore, register classes cannot be used to enforce a requirement for a register pair to start with an even-numbered register. The way to ! specify this requirement is with `HARD_REGNO_MODE_OK'. Register classes used for input-operands of bitwise-and or shift instructions have a special requirement: each such class must have, for each fixed-point machine mode, a subclass whose registers can transfer that mode to or from memory. For example, on some machines, the ! operations for single-byte values (`QImode') are limited to certain registers. When this is so, each register class that is used in a bitwise-and or shift instruction must have a subclass consisting of registers from which single-byte values can be loaded or stored. This ! is so that `PREFERRED_RELOAD_CLASS' can always have a possible value to return. -- Data type: enum reg_class ! An enumerated type that must be defined with all the register ! class names as enumerated values. `NO_REGS' must be first. ! `ALL_REGS' must be the last register class, followed by one more ! enumerated value, `LIM_REG_CLASSES', which is not a register class ! but rather tells how many classes there are. ! Each register class has a number, which is the value of casting ! the class name to type `int'. The number serves as an index in ! many of the tables described below. -- Macro: N_REG_CLASSES The number of distinct register classes, defined as follows: *************** return. *** 29853,29867 **** An initializer containing the contents of the register classes, as integers which are bit masks. The Nth integer specifies the contents of class N. The way the integer MASK is interpreted is ! that register R is in the class if 'MASK & (1 << R)' is 1. When the machine has more than 32 registers, an integer does not suffice. Then the integers are replaced by sub-initializers, ! braced groupings containing several integers. Each sub-initializer ! must be suitable as an initializer for the type 'HARD_REG_SET' ! which is defined in 'hard-reg-set.h'. In this situation, the first ! integer in each sub-initializer corresponds to registers 0 through ! 31, the second integer to registers 32 through 63, and so on. -- Macro: REGNO_REG_CLASS (REGNO) A C expression whose value is a register class containing hard --- 30257,30272 ---- An initializer containing the contents of the register classes, as integers which are bit masks. The Nth integer specifies the contents of class N. The way the integer MASK is interpreted is ! that register R is in the class if `MASK & (1 << R)' is 1. When the machine has more than 32 registers, an integer does not suffice. Then the integers are replaced by sub-initializers, ! braced groupings containing several integers. Each ! sub-initializer must be suitable as an initializer for the type ! `HARD_REG_SET' which is defined in `hard-reg-set.h'. In this ! situation, the first integer in each sub-initializer corresponds to ! registers 0 through 31, the second integer to registers 32 through ! 63, and so on. -- Macro: REGNO_REG_CLASS (REGNO) A C expression whose value is a register class containing hard *************** return. *** 29875,29884 **** address which is the register value plus a displacement. -- Macro: MODE_BASE_REG_CLASS (MODE) ! This is a variation of the 'BASE_REG_CLASS' macro which allows the selection of a base register in a mode dependent manner. If MODE is VOIDmode then it should return the same value as ! 'BASE_REG_CLASS'. -- Macro: MODE_BASE_REG_REG_CLASS (MODE) A C expression whose value is the register class to which a valid --- 30280,30289 ---- address which is the register value plus a displacement. -- Macro: MODE_BASE_REG_CLASS (MODE) ! This is a variation of the `BASE_REG_CLASS' macro which allows the selection of a base register in a mode dependent manner. If MODE is VOIDmode then it should return the same value as ! `BASE_REG_CLASS'. -- Macro: MODE_BASE_REG_REG_CLASS (MODE) A C expression whose value is the register class to which a valid *************** return. *** 29893,29902 **** base register for a memory reference in mode MODE to address space ADDRESS_SPACE must belong. OUTER_CODE and INDEX_CODE define the context in which the base register occurs. OUTER_CODE is the code ! of the immediately enclosing expression ('MEM' for the top level of ! an address, 'ADDRESS' for something that occurs in an ! 'address_operand'). INDEX_CODE is the code of the corresponding ! index expression if OUTER_CODE is 'PLUS'; 'SCRATCH' otherwise. -- Macro: INDEX_REG_CLASS A macro whose definition is the name of the class to which a valid --- 30298,30307 ---- base register for a memory reference in mode MODE to address space ADDRESS_SPACE must belong. OUTER_CODE and INDEX_CODE define the context in which the base register occurs. OUTER_CODE is the code ! of the immediately enclosing expression (`MEM' for the top level ! of an address, `ADDRESS' for something that occurs in an ! `address_operand'). INDEX_CODE is the code of the corresponding ! index expression if OUTER_CODE is `PLUS'; `SCRATCH' otherwise. -- Macro: INDEX_REG_CLASS A macro whose definition is the name of the class to which a valid *************** return. *** 29909,29922 **** for use as a base register in operand addresses. -- Macro: REGNO_MODE_OK_FOR_BASE_P (NUM, MODE) ! A C expression that is just like 'REGNO_OK_FOR_BASE_P', except that that expression may examine the mode of the memory reference in MODE. You should define this macro if the mode of the memory reference affects whether a register may be used as a base register. If you define this macro, the compiler will use it ! instead of 'REGNO_OK_FOR_BASE_P'. The mode may be 'VOIDmode' for ! addresses that appear outside a 'MEM', i.e., as an ! 'address_operand'. -- Macro: REGNO_MODE_OK_FOR_REG_BASE_P (NUM, MODE) A C expression which is nonzero if register number NUM is suitable --- 30314,30327 ---- for use as a base register in operand addresses. -- Macro: REGNO_MODE_OK_FOR_BASE_P (NUM, MODE) ! A C expression that is just like `REGNO_OK_FOR_BASE_P', except that that expression may examine the mode of the memory reference in MODE. You should define this macro if the mode of the memory reference affects whether a register may be used as a base register. If you define this macro, the compiler will use it ! instead of `REGNO_OK_FOR_BASE_P'. The mode may be `VOIDmode' for ! addresses that appear outside a `MEM', i.e., as an ! `address_operand'. -- Macro: REGNO_MODE_OK_FOR_REG_BASE_P (NUM, MODE) A C expression which is nonzero if register number NUM is suitable *************** return. *** 29928,29948 **** uses. Use of this macro is deprecated; please use the more general ! 'REGNO_MODE_CODE_OK_FOR_BASE_P'. -- Macro: REGNO_MODE_CODE_OK_FOR_BASE_P (NUM, MODE, ADDRESS_SPACE, OUTER_CODE, INDEX_CODE) A C expression which is nonzero if register number NUM is suitable for use as a base register in operand addresses, accessing memory in mode MODE in address space ADDRESS_SPACE. This is similar to ! 'REGNO_MODE_OK_FOR_BASE_P', except that that expression may examine ! the context in which the register appears in the memory reference. ! OUTER_CODE is the code of the immediately enclosing expression ! ('MEM' if at the top level of the address, 'ADDRESS' for something ! that occurs in an 'address_operand'). INDEX_CODE is the code of ! the corresponding index expression if OUTER_CODE is 'PLUS'; ! 'SCRATCH' otherwise. The mode may be 'VOIDmode' for addresses that ! appear outside a 'MEM', i.e., as an 'address_operand'. -- Macro: REGNO_OK_FOR_INDEX_P (NUM) A C expression which is nonzero if register number NUM is suitable --- 30333,30354 ---- uses. Use of this macro is deprecated; please use the more general ! `REGNO_MODE_CODE_OK_FOR_BASE_P'. -- Macro: REGNO_MODE_CODE_OK_FOR_BASE_P (NUM, MODE, ADDRESS_SPACE, OUTER_CODE, INDEX_CODE) A C expression which is nonzero if register number NUM is suitable for use as a base register in operand addresses, accessing memory in mode MODE in address space ADDRESS_SPACE. This is similar to ! `REGNO_MODE_OK_FOR_BASE_P', except that that expression may ! examine the context in which the register appears in the memory ! reference. OUTER_CODE is the code of the immediately enclosing ! expression (`MEM' if at the top level of the address, `ADDRESS' ! for something that occurs in an `address_operand'). INDEX_CODE is ! the code of the corresponding index expression if OUTER_CODE is ! `PLUS'; `SCRATCH' otherwise. The mode may be `VOIDmode' for ! addresses that appear outside a `MEM', i.e., as an ! `address_operand'. -- Macro: REGNO_OK_FOR_INDEX_P (NUM) A C expression which is nonzero if register number NUM is suitable *************** return. *** 29964,30008 **** A target hook that places additional preference on the register class to use when it is necessary to rename a register in class RCLASS to another class, or perhaps NO_REGS, if no preferred ! register class is found or hook 'preferred_rename_class' is not ! implemented. Sometimes returning a more restrictive class makes better code. For example, on ARM, thumb-2 instructions using ! 'LO_REGS' may be smaller than instructions using 'GENERIC_REGS'. ! By returning 'LO_REGS' from 'preferred_rename_class', code size can ! be reduced. -- Target Hook: reg_class_t TARGET_PREFERRED_RELOAD_CLASS (rtx X, reg_class_t RCLASS) A target hook that places additional restrictions on the register class to use when it is necessary to copy value X into a register ! in class RCLASS. The value is a register class; perhaps RCLASS, or ! perhaps another, smaller class. ! The default version of this hook always returns value of 'rclass' argument. Sometimes returning a more restrictive class makes better code. ! For example, on the 68000, when X is an integer constant that is in ! range for a 'moveq' instruction, the value of this macro is always ! 'DATA_REGS' as long as RCLASS includes the data registers. ! Requiring a data register guarantees that a 'moveq' will be used. ! One case where 'TARGET_PREFERRED_RELOAD_CLASS' must not return ! RCLASS is if X is a legitimate constant which cannot be loaded into ! some register class. By returning 'NO_REGS' you can force X into a ! memory location. For example, rs6000 can load immediate values ! into general-purpose registers, but does not have an instruction ! for loading an immediate value into a floating-point register, so ! 'TARGET_PREFERRED_RELOAD_CLASS' returns 'NO_REGS' when X is a ! floating-point constant. If the constant can't be loaded into any ! kind of register, code generation will be better if ! 'TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate ! instead of using 'TARGET_PREFERRED_RELOAD_CLASS'. ! If an insn has pseudos in it after register allocation, reload will ! go through the alternatives and call repeatedly ! 'TARGET_PREFERRED_RELOAD_CLASS' to find the best one. Returning ! 'NO_REGS', in this case, makes reload add a '!' in front of the constraint: the x86 back-end uses this feature to discourage usage of 387 registers when math is done in the SSE registers (and vice versa). --- 30370,30414 ---- A target hook that places additional preference on the register class to use when it is necessary to rename a register in class RCLASS to another class, or perhaps NO_REGS, if no preferred ! register class is found or hook `preferred_rename_class' is not ! implemented. Sometimes returning a more restrictive class makes better code. For example, on ARM, thumb-2 instructions using ! `LO_REGS' may be smaller than instructions using `GENERIC_REGS'. ! By returning `LO_REGS' from `preferred_rename_class', code size ! can be reduced. -- Target Hook: reg_class_t TARGET_PREFERRED_RELOAD_CLASS (rtx X, reg_class_t RCLASS) A target hook that places additional restrictions on the register class to use when it is necessary to copy value X into a register ! in class RCLASS. The value is a register class; perhaps RCLASS, ! or perhaps another, smaller class. ! The default version of this hook always returns value of `rclass' argument. Sometimes returning a more restrictive class makes better code. ! For example, on the 68000, when X is an integer constant that is ! in range for a `moveq' instruction, the value of this macro is ! always `DATA_REGS' as long as RCLASS includes the data registers. ! Requiring a data register guarantees that a `moveq' will be used. ! One case where `TARGET_PREFERRED_RELOAD_CLASS' must not return ! RCLASS is if X is a legitimate constant which cannot be loaded ! into some register class. By returning `NO_REGS' you can force X ! into a memory location. For example, rs6000 can load immediate ! values into general-purpose registers, but does not have an ! instruction for loading an immediate value into a floating-point ! register, so `TARGET_PREFERRED_RELOAD_CLASS' returns `NO_REGS' when ! X is a floating-point constant. If the constant can't be loaded ! into any kind of register, code generation will be better if ! `TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate ! instead of using `TARGET_PREFERRED_RELOAD_CLASS'. ! If an insn has pseudos in it after register allocation, reload ! will go through the alternatives and call repeatedly ! `TARGET_PREFERRED_RELOAD_CLASS' to find the best one. Returning ! `NO_REGS', in this case, makes reload add a `!' in front of the constraint: the x86 back-end uses this feature to discourage usage of 387 registers when math is done in the SSE registers (and vice versa). *************** return. *** 30017,30058 **** #define PREFERRED_RELOAD_CLASS(X,CLASS) CLASS Sometimes returning a more restrictive class makes better code. ! For example, on the 68000, when X is an integer constant that is in ! range for a 'moveq' instruction, the value of this macro is always ! 'DATA_REGS' as long as CLASS includes the data registers. ! Requiring a data register guarantees that a 'moveq' will be used. ! One case where 'PREFERRED_RELOAD_CLASS' must not return CLASS is if ! X is a legitimate constant which cannot be loaded into some ! register class. By returning 'NO_REGS' you can force X into a memory location. For example, rs6000 can load immediate values into general-purpose registers, but does not have an instruction for loading an immediate value into a floating-point register, so ! 'PREFERRED_RELOAD_CLASS' returns 'NO_REGS' when X is a floating-point constant. If the constant can't be loaded into any kind of register, code generation will be better if ! 'TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate ! instead of using 'TARGET_PREFERRED_RELOAD_CLASS'. ! If an insn has pseudos in it after register allocation, reload will ! go through the alternatives and call repeatedly ! 'PREFERRED_RELOAD_CLASS' to find the best one. Returning ! 'NO_REGS', in this case, makes reload add a '!' in front of the constraint: the x86 back-end uses this feature to discourage usage of 387 registers when math is done in the SSE registers (and vice versa). -- Target Hook: reg_class_t TARGET_PREFERRED_OUTPUT_RELOAD_CLASS (rtx X, reg_class_t RCLASS) ! Like 'TARGET_PREFERRED_RELOAD_CLASS', but for output reloads instead of input reloads. ! The default version of this hook always returns value of 'rclass' argument. ! You can also use 'TARGET_PREFERRED_OUTPUT_RELOAD_CLASS' to discourage reload from using some alternatives, like ! 'TARGET_PREFERRED_RELOAD_CLASS'. -- Macro: LIMIT_RELOAD_CLASS (MODE, CLASS) A C expression that places additional restrictions on the register --- 30423,30464 ---- #define PREFERRED_RELOAD_CLASS(X,CLASS) CLASS Sometimes returning a more restrictive class makes better code. ! For example, on the 68000, when X is an integer constant that is ! in range for a `moveq' instruction, the value of this macro is ! always `DATA_REGS' as long as CLASS includes the data registers. ! Requiring a data register guarantees that a `moveq' will be used. ! One case where `PREFERRED_RELOAD_CLASS' must not return CLASS is ! if X is a legitimate constant which cannot be loaded into some ! register class. By returning `NO_REGS' you can force X into a memory location. For example, rs6000 can load immediate values into general-purpose registers, but does not have an instruction for loading an immediate value into a floating-point register, so ! `PREFERRED_RELOAD_CLASS' returns `NO_REGS' when X is a floating-point constant. If the constant can't be loaded into any kind of register, code generation will be better if ! `TARGET_LEGITIMATE_CONSTANT_P' makes the constant illegitimate ! instead of using `TARGET_PREFERRED_RELOAD_CLASS'. ! If an insn has pseudos in it after register allocation, reload ! will go through the alternatives and call repeatedly ! `PREFERRED_RELOAD_CLASS' to find the best one. Returning ! `NO_REGS', in this case, makes reload add a `!' in front of the constraint: the x86 back-end uses this feature to discourage usage of 387 registers when math is done in the SSE registers (and vice versa). -- Target Hook: reg_class_t TARGET_PREFERRED_OUTPUT_RELOAD_CLASS (rtx X, reg_class_t RCLASS) ! Like `TARGET_PREFERRED_RELOAD_CLASS', but for output reloads instead of input reloads. ! The default version of this hook always returns value of `rclass' argument. ! You can also use `TARGET_PREFERRED_OUTPUT_RELOAD_CLASS' to discourage reload from using some alternatives, like ! `TARGET_PREFERRED_RELOAD_CLASS'. -- Macro: LIMIT_RELOAD_CLASS (MODE, CLASS) A C expression that places additional restrictions on the register *************** return. *** 30060,30066 **** mode MODE in a reload register for which class CLASS would ordinarily be used. ! Unlike 'PREFERRED_RELOAD_CLASS', this macro should be used when there are certain modes that simply can't go in certain reload classes. --- 30466,30472 ---- mode MODE in a reload register for which class CLASS would ordinarily be used. ! Unlike `PREFERRED_RELOAD_CLASS', this macro should be used when there are certain modes that simply can't go in certain reload classes. *************** return. *** 30073,30091 **** -- Target Hook: reg_class_t TARGET_SECONDARY_RELOAD (bool IN_P, rtx X, reg_class_t RELOAD_CLASS, machine_mode RELOAD_MODE, secondary_reload_info *SRI) ! Many machines have some registers that cannot be copied directly to ! or from memory or even from other types of registers. An example ! is the 'MQ' register, which on most machines, can only be copied to ! or from general registers, but not memory. Below, we shall be ! using the term 'intermediate register' when a move operation cannot ! be performed directly, but has to be done by copying the source ! into the intermediate register first, and then copying the ! intermediate register to the destination. An intermediate register ! always has the same mode as source and destination. Since it holds ! the actual value being copied, reload might apply optimizations to ! re-use an intermediate register and eliding the copy from the ! source when it can determine that the intermediate register still ! holds the required value. Another kind of secondary reload is required on some machines which allow copying all registers to and from memory, but require a --- 30479,30497 ---- -- Target Hook: reg_class_t TARGET_SECONDARY_RELOAD (bool IN_P, rtx X, reg_class_t RELOAD_CLASS, machine_mode RELOAD_MODE, secondary_reload_info *SRI) ! Many machines have some registers that cannot be copied directly ! to or from memory or even from other types of registers. An ! example is the `MQ' register, which on most machines, can only be ! copied to or from general registers, but not memory. Below, we ! shall be using the term 'intermediate register' when a move ! operation cannot be performed directly, but has to be done by ! copying the source into the intermediate register first, and then ! copying the intermediate register to the destination. An ! intermediate register always has the same mode as source and ! destination. Since it holds the actual value being copied, reload ! might apply optimizations to re-use an intermediate register and ! eliding the copy from the source when it can determine that the ! intermediate register still holds the required value. Another kind of secondary reload is required on some machines which allow copying all registers to and from memory, but require a *************** return. *** 30108,30187 **** needs to be copied to rtx X in RELOAD_MODE. If copying a register of RELOAD_CLASS from/to X requires an ! intermediate register, the hook 'secondary_reload' should return the register class required for this intermediate register. If no ! intermediate register is required, it should return NO_REGS. If more than one intermediate register is required, describe the one that is closest in the copy chain to the reload register. If scratch registers are needed, you also have to describe how to perform the copy from/to the reload register to/from this closest ! intermediate register. Or if no intermediate register is required, ! but still a scratch register is needed, describe the copy from/to ! the reload register to/from the reload operand X. ! You do this by setting 'sri->icode' to the instruction code of a pattern in the md file which performs the move. Operands 0 and 1 ! are the output and input of this copy, respectively. Operands from ! operand 2 onward are for scratch operands. These scratch operands ! must have a mode, and a single-register-class output constraint. ! When an intermediate register is used, the 'secondary_reload' hook will be called again to determine how to copy the intermediate register to/from the reload operand X, so your hook must also have code to handle the register class of the intermediate operand. ! X might be a pseudo-register or a 'subreg' of a pseudo-register, which could either be in a hard register or in memory. Use ! 'true_regnum' to find out; it will return -1 if the pseudo is in memory and the hard register number if it is in a register. ! Scratch operands in memory (constraint '"=m"' / '"=&m"') are currently not supported. For the time being, you will have to ! continue to use 'SECONDARY_MEMORY_NEEDED' for that purpose. ! 'copy_cost' also uses this target hook to find out how values are copied. If you want it to include some extra cost for the need to ! allocate (a) scratch register(s), set 'sri->extra_cost' to the additional cost. Or if two dependent moves are supposed to have a lower cost than the sum of the individual moves due to expected fortuitous scheduling and/or special forwarding logic, you can set ! 'sri->extra_cost' to a negative amount. -- Macro: SECONDARY_RELOAD_CLASS (CLASS, MODE, X) -- Macro: SECONDARY_INPUT_RELOAD_CLASS (CLASS, MODE, X) -- Macro: SECONDARY_OUTPUT_RELOAD_CLASS (CLASS, MODE, X) These macros are obsolete, new ports should use the target hook ! 'TARGET_SECONDARY_RELOAD' instead. These are obsolete macros, replaced by the ! 'TARGET_SECONDARY_RELOAD' target hook. Older ports still define these macros to indicate to the reload phase that it may need to allocate at least one register for a reload in addition to the register to contain the data. Specifically, if copying X to a register CLASS in MODE requires an intermediate register, you were ! supposed to define 'SECONDARY_INPUT_RELOAD_CLASS' to return the largest register class all of whose registers can be used as intermediate registers or scratch registers. If copying a register CLASS in MODE to X requires an intermediate ! or scratch register, 'SECONDARY_OUTPUT_RELOAD_CLASS' was supposed to be defined be defined to return the largest register class required. If the requirements for input and output reloads were ! the same, the macro 'SECONDARY_RELOAD_CLASS' should have been used instead of defining both macros identically. ! The values returned by these macros are often 'GENERAL_REGS'. ! Return 'NO_REGS' if no spare register is needed; i.e., if X can be directly copied to or from a register of CLASS in MODE without ! requiring a scratch register. Do not define this macro if it would ! always return 'NO_REGS'. If a scratch register is required (either with or without an intermediate register), you were supposed to define patterns for ! 'reload_inM' or 'reload_outM', as required (*note Standard Names::. ! These patterns, which were normally implemented with a ! 'define_expand', should be similar to the 'movM' patterns, except that operand 2 is the scratch register. These patterns need constraints for the reload register and scratch --- 30514,30594 ---- needs to be copied to rtx X in RELOAD_MODE. If copying a register of RELOAD_CLASS from/to X requires an ! intermediate register, the hook `secondary_reload' should return the register class required for this intermediate register. If no ! intermediate register is required, it should return NO_REGS. If more than one intermediate register is required, describe the one that is closest in the copy chain to the reload register. If scratch registers are needed, you also have to describe how to perform the copy from/to the reload register to/from this closest ! intermediate register. Or if no intermediate register is ! required, but still a scratch register is needed, describe the ! copy from/to the reload register to/from the reload operand X. ! You do this by setting `sri->icode' to the instruction code of a pattern in the md file which performs the move. Operands 0 and 1 ! are the output and input of this copy, respectively. Operands ! from operand 2 onward are for scratch operands. These scratch ! operands must have a mode, and a single-register-class output ! constraint. ! When an intermediate register is used, the `secondary_reload' hook will be called again to determine how to copy the intermediate register to/from the reload operand X, so your hook must also have code to handle the register class of the intermediate operand. ! X might be a pseudo-register or a `subreg' of a pseudo-register, which could either be in a hard register or in memory. Use ! `true_regnum' to find out; it will return -1 if the pseudo is in memory and the hard register number if it is in a register. ! Scratch operands in memory (constraint `"=m"' / `"=&m"') are currently not supported. For the time being, you will have to ! continue to use `SECONDARY_MEMORY_NEEDED' for that purpose. ! `copy_cost' also uses this target hook to find out how values are copied. If you want it to include some extra cost for the need to ! allocate (a) scratch register(s), set `sri->extra_cost' to the additional cost. Or if two dependent moves are supposed to have a lower cost than the sum of the individual moves due to expected fortuitous scheduling and/or special forwarding logic, you can set ! `sri->extra_cost' to a negative amount. -- Macro: SECONDARY_RELOAD_CLASS (CLASS, MODE, X) -- Macro: SECONDARY_INPUT_RELOAD_CLASS (CLASS, MODE, X) -- Macro: SECONDARY_OUTPUT_RELOAD_CLASS (CLASS, MODE, X) These macros are obsolete, new ports should use the target hook ! `TARGET_SECONDARY_RELOAD' instead. These are obsolete macros, replaced by the ! `TARGET_SECONDARY_RELOAD' target hook. Older ports still define these macros to indicate to the reload phase that it may need to allocate at least one register for a reload in addition to the register to contain the data. Specifically, if copying X to a register CLASS in MODE requires an intermediate register, you were ! supposed to define `SECONDARY_INPUT_RELOAD_CLASS' to return the largest register class all of whose registers can be used as intermediate registers or scratch registers. If copying a register CLASS in MODE to X requires an intermediate ! or scratch register, `SECONDARY_OUTPUT_RELOAD_CLASS' was supposed to be defined be defined to return the largest register class required. If the requirements for input and output reloads were ! the same, the macro `SECONDARY_RELOAD_CLASS' should have been used instead of defining both macros identically. ! The values returned by these macros are often `GENERAL_REGS'. ! Return `NO_REGS' if no spare register is needed; i.e., if X can be directly copied to or from a register of CLASS in MODE without ! requiring a scratch register. Do not define this macro if it ! would always return `NO_REGS'. If a scratch register is required (either with or without an intermediate register), you were supposed to define patterns for ! `reload_inM' or `reload_outM', as required (*note Standard ! Names::. These patterns, which were normally implemented with a ! `define_expand', should be similar to the `movM' patterns, except that operand 2 is the scratch register. These patterns need constraints for the reload register and scratch *************** return. *** 30189,30207 **** reload register (whose class is CLASS) can meet the constraint given in the pattern, the value returned by these macros is used for the class of the scratch register. Otherwise, two additional ! reload registers are required. Their classes are obtained from the ! constraints in the insn pattern. ! X might be a pseudo-register or a 'subreg' of a pseudo-register, which could either be in a hard register or in memory. Use ! 'true_regnum' to find out; it will return -1 if the pseudo is in memory and the hard register number if it is in a register. These macros should not be used in the case where a particular class of registers can only be copied to memory and not to another class of registers. In that case, secondary reload registers are not needed and would not be helpful. Instead, a stack location ! must be used to perform the copy and the 'movM' pattern should use memory as an intermediate storage. This case often occurs between floating-point and general registers. --- 30596,30614 ---- reload register (whose class is CLASS) can meet the constraint given in the pattern, the value returned by these macros is used for the class of the scratch register. Otherwise, two additional ! reload registers are required. Their classes are obtained from ! the constraints in the insn pattern. ! X might be a pseudo-register or a `subreg' of a pseudo-register, which could either be in a hard register or in memory. Use ! `true_regnum' to find out; it will return -1 if the pseudo is in memory and the hard register number if it is in a register. These macros should not be used in the case where a particular class of registers can only be copied to memory and not to another class of registers. In that case, secondary reload registers are not needed and would not be helpful. Instead, a stack location ! must be used to perform the copy and the `movM' pattern should use memory as an intermediate storage. This case often occurs between floating-point and general registers. *************** return. *** 30216,30235 **** Do not define this macro if its value would always be zero. -- Macro: SECONDARY_MEMORY_NEEDED_RTX (MODE) ! Normally when 'SECONDARY_MEMORY_NEEDED' is defined, the compiler allocates a stack slot for a memory location needed for register copies. If this macro is defined, the compiler instead uses the memory location defined by this macro. Do not define this macro if you do not define ! 'SECONDARY_MEMORY_NEEDED'. -- Macro: SECONDARY_MEMORY_NEEDED_MODE (MODE) ! When the compiler needs a secondary memory location to copy between ! two registers of mode MODE, it normally allocates sufficient memory ! to hold a quantity of 'BITS_PER_WORD' bits and performs the store ! and load operations in a mode that many bits wide and whose class ! is the same as that of MODE. This is right thing to do on most machines because it ensures that all bits of the register are copied and prevents accesses to the --- 30623,30642 ---- Do not define this macro if its value would always be zero. -- Macro: SECONDARY_MEMORY_NEEDED_RTX (MODE) ! Normally when `SECONDARY_MEMORY_NEEDED' is defined, the compiler allocates a stack slot for a memory location needed for register copies. If this macro is defined, the compiler instead uses the memory location defined by this macro. Do not define this macro if you do not define ! `SECONDARY_MEMORY_NEEDED'. -- Macro: SECONDARY_MEMORY_NEEDED_MODE (MODE) ! When the compiler needs a secondary memory location to copy ! between two registers of mode MODE, it normally allocates ! sufficient memory to hold a quantity of `BITS_PER_WORD' bits and ! performs the store and load operations in a mode that many bits ! wide and whose class is the same as that of MODE. This is right thing to do on most machines because it ensures that all bits of the register are copied and prevents accesses to the *************** return. *** 30239,30259 **** However, this default behavior is not correct on some machines, such as the DEC Alpha, that store short integers in floating-point registers differently than in integer registers. On those ! machines, the default widening will not work correctly and you must ! define this macro to suppress that widening in some cases. See the ! file 'alpha.h' for details. Do not define this macro if you do not define ! 'SECONDARY_MEMORY_NEEDED' or if widening MODE to a mode that is ! 'BITS_PER_WORD' bits wide is correct for your machine. -- Target Hook: bool TARGET_CLASS_LIKELY_SPILLED_P (reg_class_t RCLASS) ! A target hook which returns 'true' if pseudos that have been assigned to registers of class RCLASS would likely be spilled because registers of RCLASS are needed for spill registers. ! The default version of this target hook returns 'true' if RCLASS ! has exactly one register and 'false' otherwise. On most machines, this default should be used. For generally register-starved machines, such as i386, or machines with right register constraints, such as SH, this hook can be used to avoid excessive --- 30646,30666 ---- However, this default behavior is not correct on some machines, such as the DEC Alpha, that store short integers in floating-point registers differently than in integer registers. On those ! machines, the default widening will not work correctly and you ! must define this macro to suppress that widening in some cases. ! See the file `alpha.h' for details. Do not define this macro if you do not define ! `SECONDARY_MEMORY_NEEDED' or if widening MODE to a mode that is ! `BITS_PER_WORD' bits wide is correct for your machine. -- Target Hook: bool TARGET_CLASS_LIKELY_SPILLED_P (reg_class_t RCLASS) ! A target hook which returns `true' if pseudos that have been assigned to registers of class RCLASS would likely be spilled because registers of RCLASS are needed for spill registers. ! The default version of this target hook returns `true' if RCLASS ! has exactly one register and `false' otherwise. On most machines, this default should be used. For generally register-starved machines, such as i386, or machines with right register constraints, such as SH, this hook can be used to avoid excessive *************** return. *** 30268,30292 **** A target hook returns the maximum number of consecutive registers of class RCLASS needed to hold a value of mode MODE. ! This is closely related to the macro 'HARD_REGNO_NREGS'. In fact, ! the value returned by 'TARGET_CLASS_MAX_NREGS (RCLASS, MODE)' ! target hook should be the maximum value of 'HARD_REGNO_NREGS (REGNO, MODE)' for all REGNO values in the class RCLASS. This target hook helps control the handling of multiple-word values in the reload pass. ! The default version of this target hook returns the size of MODE in ! words. -- Macro: CLASS_MAX_NREGS (CLASS, MODE) A C expression for the maximum number of consecutive registers of class CLASS needed to hold a value of mode MODE. ! This is closely related to the macro 'HARD_REGNO_NREGS'. In fact, ! the value of the macro 'CLASS_MAX_NREGS (CLASS, MODE)' should be ! the maximum value of 'HARD_REGNO_NREGS (REGNO, MODE)' for all REGNO ! values in the class CLASS. This macro helps control the handling of multiple-word values in the reload pass. --- 30675,30699 ---- A target hook returns the maximum number of consecutive registers of class RCLASS needed to hold a value of mode MODE. ! This is closely related to the macro `HARD_REGNO_NREGS'. In fact, ! the value returned by `TARGET_CLASS_MAX_NREGS (RCLASS, MODE)' ! target hook should be the maximum value of `HARD_REGNO_NREGS (REGNO, MODE)' for all REGNO values in the class RCLASS. This target hook helps control the handling of multiple-word values in the reload pass. ! The default version of this target hook returns the size of MODE ! in words. -- Macro: CLASS_MAX_NREGS (CLASS, MODE) A C expression for the maximum number of consecutive registers of class CLASS needed to hold a value of mode MODE. ! This is closely related to the macro `HARD_REGNO_NREGS'. In fact, ! the value of the macro `CLASS_MAX_NREGS (CLASS, MODE)' should be ! the maximum value of `HARD_REGNO_NREGS (REGNO, MODE)' for all ! REGNO values in the class CLASS. This macro helps control the handling of multiple-word values in the reload pass. *************** return. *** 30299,30389 **** floating-point registers on Alpha extends them to 64 bits. Therefore loading a 64-bit object and then storing it as a 32-bit object does not store the low-order 32 bits, as would be the case ! for a normal register. Therefore, 'alpha.h' defines ! 'CANNOT_CHANGE_MODE_CLASS' as below: #define CANNOT_CHANGE_MODE_CLASS(FROM, TO, CLASS) \ (GET_MODE_SIZE (FROM) != GET_MODE_SIZE (TO) \ ? reg_classes_intersect_p (FLOAT_REGS, (CLASS)) : 0) Even if storing from a register in mode TO would be valid, if both ! FROM and 'raw_reg_mode' for CLASS are wider than 'word_mode', then we must prevent TO narrowing the mode. This happens when the middle-end assumes that it can load or store pieces of an N-word pseudo, and that the pseudo will eventually be allocated to N ! 'word_mode' hard registers. Failure to prevent this kind of mode ! change will result in the entire 'raw_reg_mode' being modified instead of the partial value that the middle-end intended. -- Target Hook: reg_class_t TARGET_IRA_CHANGE_PSEUDO_ALLOCNO_CLASS (int, REG_CLASS_T, REG_CLASS_T) A target hook which can change allocno class for given pseudo from ! allocno and best class calculated by IRA. The default version of this target hook always returns given class. -- Target Hook: bool TARGET_LRA_P (void) A target hook which returns true if we use LRA instead of reload ! pass. The default version of this target hook returns always ! false, but new ports should use LRA. -- Target Hook: int TARGET_REGISTER_PRIORITY (int) A target hook which returns the register priority number to which ! the register HARD_REGNO belongs to. The bigger the number, the more preferable the hard register usage (when all other conditions ! are the same). This hook can be used to prefer some hard register ! over others in LRA. For example, some x86-64 register usage needs ! additional prefix which makes instructions longer. The hook can ! return lower priority number for such registers make them less ! favorable and as result making the generated code smaller. The ! default version of this target hook returns always zero. -- Target Hook: bool TARGET_REGISTER_USAGE_LEVELING_P (void) A target hook which returns true if we need register usage leveling. That means if a few hard registers are equally good for ! the assignment, we choose the least used hard register. The ! register usage leveling may be profitable for some targets. Don't ! use the usage leveling for targets with conditional execution or ! targets with big register files as it hurts if-conversion and ! cross-jumping optimizations. The default version of this target ! hook returns always false. -- Target Hook: bool TARGET_DIFFERENT_ADDR_DISPLACEMENT_P (void) A target hook which returns true if an address with the same ! structure can have different maximal legitimate displacement. For ! example, the displacement can depend on memory mode or on operand ! combinations in the insn. The default version of this target hook ! returns always false. -- Target Hook: bool TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P (rtx SUBST) ! A target hook which returns 'true' if SUBST can't substitute safely ! pseudos with equivalent memory values during register allocation. ! The default version of this target hook returns 'false'. On most ! machines, this default should be used. For generally machines with ! non orthogonal register usage for addressing, such as SH, this hook ! can be used to avoid excessive spilling. ! -- Target Hook: bool TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT (rtx *DISP, ! rtx *OFFSET, machine_mode MODE) ! A target hook which returns 'true' if *DISP is legitimezed to valid ! address displacement with subtracting *OFFSET at memory mode MODE. ! The default version of this target hook returns 'false'. This hook ! will benefit machines with limited base plus displacement addressing. -- Target Hook: reg_class_t TARGET_SPILL_CLASS (reg_class_t, MACHINE_MODE) This hook defines a class of registers which could be used for ! spilling pseudos of the given mode and class, or 'NO_REGS' if only ! memory should be used. Not defining this hook is equivalent to ! returning 'NO_REGS' for all inputs. -- Target Hook: machine_mode TARGET_CSTORE_MODE (enum insn_code ICODE) ! This hook defines the machine mode to use for the boolean result of ! conditional store patterns. The ICODE argument is the instruction ! code for the cstore being performed. Not definiting this hook is ! the same as accepting the mode encoded into operand 0 of the cstore ! expander patterns.  File: gccint.info, Node: Stack and Calling, Next: Varargs, Prev: Register Classes, Up: Target Macros --- 30706,30799 ---- floating-point registers on Alpha extends them to 64 bits. Therefore loading a 64-bit object and then storing it as a 32-bit object does not store the low-order 32 bits, as would be the case ! for a normal register. Therefore, `alpha.h' defines ! `CANNOT_CHANGE_MODE_CLASS' as below: #define CANNOT_CHANGE_MODE_CLASS(FROM, TO, CLASS) \ (GET_MODE_SIZE (FROM) != GET_MODE_SIZE (TO) \ ? reg_classes_intersect_p (FLOAT_REGS, (CLASS)) : 0) Even if storing from a register in mode TO would be valid, if both ! FROM and `raw_reg_mode' for CLASS are wider than `word_mode', then we must prevent TO narrowing the mode. This happens when the middle-end assumes that it can load or store pieces of an N-word pseudo, and that the pseudo will eventually be allocated to N ! `word_mode' hard registers. Failure to prevent this kind of mode ! change will result in the entire `raw_reg_mode' being modified instead of the partial value that the middle-end intended. + -- Target Hook: reg_class_t TARGET_IRA_CHANGE_PSEUDO_ALLOCNO_CLASS (int, REG_CLASS_T, REG_CLASS_T) A target hook which can change allocno class for given pseudo from ! allocno and best class calculated by IRA. The default version of this target hook always returns given class. -- Target Hook: bool TARGET_LRA_P (void) A target hook which returns true if we use LRA instead of reload ! pass. The default version of this target hook returns always ! false, but new ports should use LRA. -- Target Hook: int TARGET_REGISTER_PRIORITY (int) A target hook which returns the register priority number to which ! the register HARD_REGNO belongs to. The bigger the number, the more preferable the hard register usage (when all other conditions ! are the same). This hook can be used to prefer some hard ! register over others in LRA. For example, some x86-64 register ! usage needs additional prefix which makes instructions longer. ! The hook can return lower priority number for such registers make ! them less favorable and as result making the generated code ! smaller. The default version of this target hook returns always ! zero. -- Target Hook: bool TARGET_REGISTER_USAGE_LEVELING_P (void) A target hook which returns true if we need register usage leveling. That means if a few hard registers are equally good for ! the assignment, we choose the least used hard register. The ! register usage leveling may be profitable for some targets. ! Don't use the usage leveling for targets with conditional ! execution or targets with big register files as it hurts ! if-conversion and cross-jumping optimizations. The default ! version of this target hook returns always false. -- Target Hook: bool TARGET_DIFFERENT_ADDR_DISPLACEMENT_P (void) A target hook which returns true if an address with the same ! structure can have different maximal legitimate displacement. ! For example, the displacement can depend on memory mode or on ! operand combinations in the insn. The default version of this ! target hook returns always false. -- Target Hook: bool TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P (rtx SUBST) ! A target hook which returns `true' if SUBST can't substitute ! safely pseudos with equivalent memory values during register ! allocation. The default version of this target hook returns ! `false'. On most machines, this default should be used. For ! generally machines with non orthogonal register usage for ! addressing, such as SH, this hook can be used to avoid excessive ! spilling. ! -- Target Hook: bool TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT (rtx ! *DISP, rtx *OFFSET, machine_mode MODE) ! A target hook which returns `true' if *DISP is legitimezed to ! valid address displacement with subtracting *OFFSET at memory mode ! MODE. The default version of this target hook returns `false'. ! This hook will benefit machines with limited base plus displacement addressing. -- Target Hook: reg_class_t TARGET_SPILL_CLASS (reg_class_t, MACHINE_MODE) This hook defines a class of registers which could be used for ! spilling pseudos of the given mode and class, or `NO_REGS' if ! only memory should be used. Not defining this hook is equivalent ! to returning `NO_REGS' for all inputs. -- Target Hook: machine_mode TARGET_CSTORE_MODE (enum insn_code ICODE) ! This hook defines the machine mode to use for the boolean result ! of conditional store patterns. The ICODE argument is the ! instruction code for the cstore being performed. Not definiting ! this hook is the same as accepting the mode encoded into operand ! 0 of the cstore expander patterns.  File: gccint.info, Node: Stack and Calling, Next: Varargs, Prev: Register Classes, Up: Target Macros *************** File: gccint.info, Node: Frame Layout, *** 30420,30441 **** Here is the basic stack layout. -- Macro: STACK_GROWS_DOWNWARD ! Define this macro to be true if pushing a word onto the stack moves ! the stack pointer to a smaller address, and false otherwise. -- Macro: STACK_PUSH_CODE This macro defines the operation used when something is pushed on ! the stack. In RTL, a push operation will be '(set (mem (STACK_PUSH_CODE (reg sp))) ...)' ! The choices are 'PRE_DEC', 'POST_DEC', 'PRE_INC', and 'POST_INC'. Which of these is correct depends on the stack direction and on whether the stack pointer points to the last item on the stack or whether it points to the space for the next item on the stack. ! The default is 'PRE_DEC' when 'STACK_GROWS_DOWNWARD' is true, which ! is almost always right, and 'PRE_INC' otherwise, which is often ! wrong. -- Macro: FRAME_GROWS_DOWNWARD Define this macro to nonzero value if the addresses of local --- 30830,30851 ---- Here is the basic stack layout. -- Macro: STACK_GROWS_DOWNWARD ! Define this macro to be true if pushing a word onto the stack ! moves the stack pointer to a smaller address, and false otherwise. -- Macro: STACK_PUSH_CODE This macro defines the operation used when something is pushed on ! the stack. In RTL, a push operation will be `(set (mem (STACK_PUSH_CODE (reg sp))) ...)' ! The choices are `PRE_DEC', `POST_DEC', `PRE_INC', and `POST_INC'. Which of these is correct depends on the stack direction and on whether the stack pointer points to the last item on the stack or whether it points to the space for the next item on the stack. ! The default is `PRE_DEC' when `STACK_GROWS_DOWNWARD' is true, ! which is almost always right, and `PRE_INC' otherwise, which is ! often wrong. -- Macro: FRAME_GROWS_DOWNWARD Define this macro to nonzero value if the addresses of local *************** Here is the basic stack layout. *** 30449,30475 **** Offset from the frame pointer to the first local variable slot to be allocated. ! If 'FRAME_GROWS_DOWNWARD', find the next slot's offset by ! subtracting the first slot's length from 'STARTING_FRAME_OFFSET'. Otherwise, it is found by adding the length of the first slot to ! the value 'STARTING_FRAME_OFFSET'. -- Macro: STACK_ALIGNMENT_NEEDED Define to zero to disable final alignment of the stack during reload. The nonzero default for this macro is suitable for most ports. ! On ports where 'STARTING_FRAME_OFFSET' is nonzero or where there is ! a register save block following the local block that doesn't ! require alignment to 'STACK_BOUNDARY', it may be beneficial to disable stack alignment and do it in the backend. -- Macro: STACK_POINTER_OFFSET Offset from the stack pointer register to the first location at ! which outgoing arguments are placed. If not specified, the default ! value of zero is used. This is the proper value for most machines. ! If 'ARGS_GROW_DOWNWARD', this is the offset to the location above the first location at which outgoing arguments are placed. -- Macro: FIRST_PARM_OFFSET (FUNDECL) --- 30859,30886 ---- Offset from the frame pointer to the first local variable slot to be allocated. ! If `FRAME_GROWS_DOWNWARD', find the next slot's offset by ! subtracting the first slot's length from `STARTING_FRAME_OFFSET'. Otherwise, it is found by adding the length of the first slot to ! the value `STARTING_FRAME_OFFSET'. -- Macro: STACK_ALIGNMENT_NEEDED Define to zero to disable final alignment of the stack during reload. The nonzero default for this macro is suitable for most ports. ! On ports where `STARTING_FRAME_OFFSET' is nonzero or where there ! is a register save block following the local block that doesn't ! require alignment to `STACK_BOUNDARY', it may be beneficial to disable stack alignment and do it in the backend. -- Macro: STACK_POINTER_OFFSET Offset from the stack pointer register to the first location at ! which outgoing arguments are placed. If not specified, the ! default value of zero is used. This is the proper value for most ! machines. ! If `ARGS_GROW_DOWNWARD', this is the offset to the location above the first location at which outgoing arguments are placed. -- Macro: FIRST_PARM_OFFSET (FUNDECL) *************** Here is the basic stack layout. *** 30477,30501 **** address. On some machines it may depend on the data type of the function. ! If 'ARGS_GROW_DOWNWARD', this is the offset to the location above the first argument's address. -- Macro: STACK_DYNAMIC_OFFSET (FUNDECL) Offset from the stack pointer register to an item dynamically ! allocated on the stack, e.g., by 'alloca'. ! The default value for this macro is 'STACK_POINTER_OFFSET' plus the length of the outgoing arguments. The default is correct for most ! machines. See 'function.c' for details. -- Macro: INITIAL_FRAME_ADDRESS_RTX A C expression whose value is RTL representing the address of the ! initial stack frame. This address is passed to 'RETURN_ADDR_RTX' ! and 'DYNAMIC_CHAIN_ADDRESS'. If you don't define this macro, a reasonable default value will be used. Define this macro in order to make frame pointer elimination work in the presence of ! '__builtin_frame_address (count)' and '__builtin_return_address ! (count)' for 'count' not equal to zero. -- Macro: DYNAMIC_CHAIN_ADDRESS (FRAMEADDR) A C expression whose value is RTL representing the address in a --- 30888,30912 ---- address. On some machines it may depend on the data type of the function. ! If `ARGS_GROW_DOWNWARD', this is the offset to the location above the first argument's address. -- Macro: STACK_DYNAMIC_OFFSET (FUNDECL) Offset from the stack pointer register to an item dynamically ! allocated on the stack, e.g., by `alloca'. ! The default value for this macro is `STACK_POINTER_OFFSET' plus the length of the outgoing arguments. The default is correct for most ! machines. See `function.c' for details. -- Macro: INITIAL_FRAME_ADDRESS_RTX A C expression whose value is RTL representing the address of the ! initial stack frame. This address is passed to `RETURN_ADDR_RTX' ! and `DYNAMIC_CHAIN_ADDRESS'. If you don't define this macro, a reasonable default value will be used. Define this macro in order to make frame pointer elimination work in the presence of ! `__builtin_frame_address (count)' and `__builtin_return_address ! (count)' for `count' not equal to zero. -- Macro: DYNAMIC_CHAIN_ADDRESS (FRAMEADDR) A C expression whose value is RTL representing the address in a *************** Here is the basic stack layout. *** 30508,30525 **** of the stack word that points to the previous frame. -- Macro: SETUP_FRAME_ADDRESSES ! A C expression that produces the machine-specific code to setup the ! stack so that arbitrary frames can be accessed. For example, on ! the SPARC, we must flush all of the register windows to the stack ! before we can access arbitrary stack frames. You will seldom need ! to define this macro. The default is to do nothing. -- Target Hook: rtx TARGET_BUILTIN_SETJMP_FRAME_VALUE (void) This target hook should return an rtx that is used to store the ! address of the current frame into the built in 'setjmp' buffer. ! The default value, 'virtual_stack_vars_rtx', is correct for most machines. One reason you may need to define this target hook is if ! 'hard_frame_pointer_rtx' is the appropriate value on your machine. -- Macro: FRAME_ADDR_RTX (FRAMEADDR) A C expression whose value is RTL representing the value of the --- 30919,30936 ---- of the stack word that points to the previous frame. -- Macro: SETUP_FRAME_ADDRESSES ! A C expression that produces the machine-specific code to setup ! the stack so that arbitrary frames can be accessed. For example, ! on the SPARC, we must flush all of the register windows to the ! stack before we can access arbitrary stack frames. You will ! seldom need to define this macro. The default is to do nothing. -- Target Hook: rtx TARGET_BUILTIN_SETJMP_FRAME_VALUE (void) This target hook should return an rtx that is used to store the ! address of the current frame into the built in `setjmp' buffer. ! The default value, `virtual_stack_vars_rtx', is correct for most machines. One reason you may need to define this target hook is if ! `hard_frame_pointer_rtx' is the appropriate value on your machine. -- Macro: FRAME_ADDR_RTX (FRAMEADDR) A C expression whose value is RTL representing the value of the *************** Here is the basic stack layout. *** 30531,30543 **** -- Macro: RETURN_ADDR_RTX (COUNT, FRAMEADDR) A C expression whose value is RTL representing the value of the ! return address for the frame COUNT steps up from the current frame, ! after the prologue. FRAMEADDR is the frame pointer of the COUNT ! frame, or the frame pointer of the COUNT - 1 frame if ! 'RETURN_ADDR_IN_PREVIOUS_FRAME' is nonzero. The value of the expression must always be the correct address when ! COUNT is zero, but may be 'NULL_RTX' if there is no way to determine the return address of other frames. -- Macro: RETURN_ADDR_IN_PREVIOUS_FRAME --- 30942,30954 ---- -- Macro: RETURN_ADDR_RTX (COUNT, FRAMEADDR) A C expression whose value is RTL representing the value of the ! return address for the frame COUNT steps up from the current ! frame, after the prologue. FRAMEADDR is the frame pointer of the ! COUNT frame, or the frame pointer of the COUNT - 1 frame if ! `RETURN_ADDR_IN_PREVIOUS_FRAME' is nonzero. The value of the expression must always be the correct address when ! COUNT is zero, but may be `NULL_RTX' if there is no way to determine the return address of other frames. -- Macro: RETURN_ADDR_IN_PREVIOUS_FRAME *************** Here is the basic stack layout. *** 30549,30571 **** -- Macro: INCOMING_RETURN_ADDR_RTX A C expression whose value is RTL representing the location of the incoming return address at the beginning of any function, before ! the prologue. This RTL is either a 'REG', indicating that the ! return value is saved in 'REG', or a 'MEM' representing a location in the stack. You only need to define this macro if you want to support call frame debugging information like that provided by DWARF 2. ! If this RTL is a 'REG', you should also define ! 'DWARF_FRAME_RETURN_COLUMN' to 'DWARF_FRAME_REGNUM (REGNO)'. -- Macro: DWARF_ALT_FRAME_RETURN_COLUMN A C expression whose value is an integer giving a DWARF 2 column number that may be used as an alternative return column. The column must not correspond to any gcc hard register (that is, it ! must not be in the range of 'DWARF_FRAME_REGNUM'). ! This macro can be useful if 'DWARF_FRAME_RETURN_COLUMN' is set to a general register, but an alternative column needs to be used for signal frames. Some targets have also used different frame return columns over time. --- 30960,30982 ---- -- Macro: INCOMING_RETURN_ADDR_RTX A C expression whose value is RTL representing the location of the incoming return address at the beginning of any function, before ! the prologue. This RTL is either a `REG', indicating that the ! return value is saved in `REG', or a `MEM' representing a location in the stack. You only need to define this macro if you want to support call frame debugging information like that provided by DWARF 2. ! If this RTL is a `REG', you should also define ! `DWARF_FRAME_RETURN_COLUMN' to `DWARF_FRAME_REGNUM (REGNO)'. -- Macro: DWARF_ALT_FRAME_RETURN_COLUMN A C expression whose value is an integer giving a DWARF 2 column number that may be used as an alternative return column. The column must not correspond to any gcc hard register (that is, it ! must not be in the range of `DWARF_FRAME_REGNUM'). ! This macro can be useful if `DWARF_FRAME_RETURN_COLUMN' is set to a general register, but an alternative column needs to be used for signal frames. Some targets have also used different frame return columns over time. *************** Here is the basic stack layout. *** 30575,30582 **** number that is considered to always have the value zero. This should only be defined if the target has an architected zero register, and someone decided it was a good idea to use that ! register number to terminate the stack backtrace. New ports should ! avoid this. -- Target Hook: void TARGET_DWARF_HANDLE_FRAME_UNSPEC (const char *LABEL, rtx PATTERN, int INDEX) --- 30986,30993 ---- number that is considered to always have the value zero. This should only be defined if the target has an architected zero register, and someone decided it was a good idea to use that ! register number to terminate the stack backtrace. New ports ! should avoid this. -- Target Hook: void TARGET_DWARF_HANDLE_FRAME_UNSPEC (const char *LABEL, rtx PATTERN, int INDEX) *************** Here is the basic stack layout. *** 30588,30594 **** (set (reg) (unspec_volatile [...] UNSPECV_INDEX)). to let the backend emit the call frame instructions. LABEL is the CFI label attached to the insn, PATTERN is the pattern of the insn ! and INDEX is 'UNSPEC_INDEX' or 'UNSPECV_INDEX'. -- Macro: INCOMING_FRAME_SP_OFFSET A C expression whose value is an integer giving the offset, in --- 30999,31005 ---- (set (reg) (unspec_volatile [...] UNSPECV_INDEX)). to let the backend emit the call frame instructions. LABEL is the CFI label attached to the insn, PATTERN is the pattern of the insn ! and INDEX is `UNSPEC_INDEX' or `UNSPECV_INDEX'. -- Macro: INCOMING_FRAME_SP_OFFSET A C expression whose value is an integer giving the offset, in *************** Here is the basic stack layout. *** 30605,30644 **** A C expression whose value is an integer giving the offset, in bytes, from the argument pointer to the canonical frame address (cfa). The final value should coincide with that calculated by ! 'INCOMING_FRAME_SP_OFFSET'. Which is unfortunately not usable during virtual register instantiation. ! The default value for this macro is 'FIRST_PARM_OFFSET (fundecl) + crtl->args.pretend_args_size', which is correct for most machines; in general, the arguments are found immediately before the stack frame. Note that this is not the case on some targets that save ! registers into the caller's frame, such as SPARC and rs6000, and so ! such targets need to define this macro. ! You only need to define this macro if the default is incorrect, and ! you want to support call frame debugging information like that provided by DWARF 2. -- Macro: FRAME_POINTER_CFA_OFFSET (FUNDECL) If defined, a C expression whose value is an integer giving the offset in bytes from the frame pointer to the canonical frame address (cfa). The final value should coincide with that ! calculated by 'INCOMING_FRAME_SP_OFFSET'. Normally the CFA is calculated as an offset from the argument ! pointer, via 'ARG_POINTER_CFA_OFFSET', but if the argument pointer is variable due to the ABI, this may not be possible. If this macro is defined, it implies that the virtual register instantiation should be based on the frame pointer instead of the ! argument pointer. Only one of 'FRAME_POINTER_CFA_OFFSET' and ! 'ARG_POINTER_CFA_OFFSET' should be defined. -- Macro: CFA_FRAME_BASE_OFFSET (FUNDECL) If defined, a C expression whose value is an integer giving the ! offset in bytes from the canonical frame address (cfa) to the frame ! base used in DWARF 2 debug information. The default is zero. A ! different value may reduce the size of debug information on some ! ports.  File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Frame Layout, Up: Stack and Calling --- 31016,31055 ---- A C expression whose value is an integer giving the offset, in bytes, from the argument pointer to the canonical frame address (cfa). The final value should coincide with that calculated by ! `INCOMING_FRAME_SP_OFFSET'. Which is unfortunately not usable during virtual register instantiation. ! The default value for this macro is `FIRST_PARM_OFFSET (fundecl) + crtl->args.pretend_args_size', which is correct for most machines; in general, the arguments are found immediately before the stack frame. Note that this is not the case on some targets that save ! registers into the caller's frame, such as SPARC and rs6000, and ! so such targets need to define this macro. ! You only need to define this macro if the default is incorrect, ! and you want to support call frame debugging information like that provided by DWARF 2. -- Macro: FRAME_POINTER_CFA_OFFSET (FUNDECL) If defined, a C expression whose value is an integer giving the offset in bytes from the frame pointer to the canonical frame address (cfa). The final value should coincide with that ! calculated by `INCOMING_FRAME_SP_OFFSET'. Normally the CFA is calculated as an offset from the argument ! pointer, via `ARG_POINTER_CFA_OFFSET', but if the argument pointer is variable due to the ABI, this may not be possible. If this macro is defined, it implies that the virtual register instantiation should be based on the frame pointer instead of the ! argument pointer. Only one of `FRAME_POINTER_CFA_OFFSET' and ! `ARG_POINTER_CFA_OFFSET' should be defined. -- Macro: CFA_FRAME_BASE_OFFSET (FUNDECL) If defined, a C expression whose value is an integer giving the ! offset in bytes from the canonical frame address (cfa) to the ! frame base used in DWARF 2 debug information. The default is ! zero. A different value may reduce the size of debug information ! on some ports.  File: gccint.info, Node: Exception Handling, Next: Stack Checking, Prev: Frame Layout, Up: Stack and Calling *************** File: gccint.info, Node: Exception Hand *** 30647,30654 **** --------------------------------- -- Macro: EH_RETURN_DATA_REGNO (N) ! A C expression whose value is the Nth register number used for data ! by exception handlers, or 'INVALID_REGNUM' if fewer than N registers are usable. The exception handling library routines communicate with the --- 31058,31065 ---- --------------------------------- -- Macro: EH_RETURN_DATA_REGNO (N) ! A C expression whose value is the Nth register number used for ! data by exception handlers, or `INVALID_REGNUM' if fewer than N registers are usable. The exception handling library routines communicate with the *************** File: gccint.info, Node: Exception Hand *** 30688,30709 **** normal return address is stored. For targets that return by popping an address off the stack, this might be a memory address just below the _target_ call frame rather than inside the current ! call frame. If defined, 'EH_RETURN_STACKADJ_RTX' will have already been assigned, so it may be used to calculate the location of the target call frame. Some targets have more complex requirements than storing to an address calculable during initial code generation. In that case ! the 'eh_return' instruction pattern should be used instead. If you want to support call frame exception handling, you must ! define either this macro or the 'eh_return' instruction pattern. -- Macro: RETURN_ADDR_OFFSET If defined, an integer-valued C expression for which rtl will be generated to add it to the exception handler address before it is ! searched in the exception handling tables, and to subtract it again ! from the address before using it to return to the exception handler. -- Macro: ASM_PREFERRED_EH_DATA_FORMAT (CODE, GLOBAL) --- 31099,31120 ---- normal return address is stored. For targets that return by popping an address off the stack, this might be a memory address just below the _target_ call frame rather than inside the current ! call frame. If defined, `EH_RETURN_STACKADJ_RTX' will have already been assigned, so it may be used to calculate the location of the target call frame. Some targets have more complex requirements than storing to an address calculable during initial code generation. In that case ! the `eh_return' instruction pattern should be used instead. If you want to support call frame exception handling, you must ! define either this macro or the `eh_return' instruction pattern. -- Macro: RETURN_ADDR_OFFSET If defined, an integer-valued C expression for which rtl will be generated to add it to the exception handler address before it is ! searched in the exception handling tables, and to subtract it ! again from the address before using it to return to the exception handler. -- Macro: ASM_PREFERRED_EH_DATA_FORMAT (CODE, GLOBAL) *************** File: gccint.info, Node: Exception Hand *** 30715,30721 **** CODE is 0 for data, 1 for code labels, 2 for function pointers. GLOBAL is true if the symbol may be affected by dynamic relocations. The macro should return a combination of the ! 'DW_EH_PE_*' defines as found in 'dwarf2.h'. If this macro is not defined, pointers will not be encoded but represented directly. --- 31126,31132 ---- CODE is 0 for data, 1 for code labels, 2 for function pointers. GLOBAL is true if the symbol may be affected by dynamic relocations. The macro should return a combination of the ! `DW_EH_PE_*' defines as found in `dwarf2.h'. If this macro is not defined, pointers will not be encoded but represented directly. *************** File: gccint.info, Node: Exception Hand *** 30724,30736 **** ADDR, DONE) This macro allows the target to emit whatever special magic is required to represent the encoding chosen by ! 'ASM_PREFERRED_EH_DATA_FORMAT'. Generic code takes care of pc-relative and indirect encodings; this must be defined if the target uses text-relative or data-relative encodings. This is a C statement that branches to DONE if the format was handled. ENCODING is the format chosen, SIZE is the number of ! bytes that the format occupies, ADDR is the 'SYMBOL_REF' to be emitted. -- Macro: MD_FALLBACK_FRAME_STATE_FOR (CONTEXT, FS) --- 31135,31147 ---- ADDR, DONE) This macro allows the target to emit whatever special magic is required to represent the encoding chosen by ! `ASM_PREFERRED_EH_DATA_FORMAT'. Generic code takes care of pc-relative and indirect encodings; this must be defined if the target uses text-relative or data-relative encodings. This is a C statement that branches to DONE if the format was handled. ENCODING is the format chosen, SIZE is the number of ! bytes that the format occupies, ADDR is the `SYMBOL_REF' to be emitted. -- Macro: MD_FALLBACK_FRAME_STATE_FOR (CONTEXT, FS) *************** File: gccint.info, Node: Exception Hand *** 30739,30772 **** unwind data available. The most common reason to implement this macro is to unwind through signal frames. ! This macro is called from 'uw_frame_state_for' in 'unwind-dw2.c', ! 'unwind-dw2-xtensa.c' and 'unwind-ia64.c'. CONTEXT is an ! '_Unwind_Context'; FS is an '_Unwind_FrameState'. Examine ! 'context->ra' for the address of the code being executed and ! 'context->cfa' for the stack pointer value. If the frame can be decoded, the register save addresses should be updated in FS and ! the macro should evaluate to '_URC_NO_REASON'. If the frame cannot ! be decoded, the macro should evaluate to '_URC_END_OF_STACK'. For proper signal handling in Java this macro is accompanied by ! 'MAKE_THROW_FRAME', defined in 'libjava/include/*-signal.h' headers. -- Macro: MD_HANDLE_UNWABI (CONTEXT, FS) This macro allows the target to add operating system specific code ! to the call-frame unwinder to handle the IA-64 '.unwabi' unwinding directive, usually used for signal or interrupt frames. ! This macro is called from 'uw_update_context' in libgcc's ! 'unwind-ia64.c'. CONTEXT is an '_Unwind_Context'; FS is an ! '_Unwind_FrameState'. Examine 'fs->unwabi' for the abi and context ! in the '.unwabi' directive. If the '.unwabi' directive can be ! handled, the register save addresses should be updated in FS. -- Macro: TARGET_USES_WEAK_UNWIND_INFO A C expression that evaluates to true if the target requires unwind ! info to be given comdat linkage. Define it to be '1' if comdat ! linkage is necessary. The default is '0'.  File: gccint.info, Node: Stack Checking, Next: Frame Registers, Prev: Exception Handling, Up: Stack and Calling --- 31150,31185 ---- unwind data available. The most common reason to implement this macro is to unwind through signal frames. ! This macro is called from `uw_frame_state_for' in `unwind-dw2.c', ! `unwind-dw2-xtensa.c' and `unwind-ia64.c'. CONTEXT is an ! `_Unwind_Context'; FS is an `_Unwind_FrameState'. Examine ! `context->ra' for the address of the code being executed and ! `context->cfa' for the stack pointer value. If the frame can be decoded, the register save addresses should be updated in FS and ! the macro should evaluate to `_URC_NO_REASON'. If the frame ! cannot be decoded, the macro should evaluate to ! `_URC_END_OF_STACK'. For proper signal handling in Java this macro is accompanied by ! `MAKE_THROW_FRAME', defined in `libjava/include/*-signal.h' headers. -- Macro: MD_HANDLE_UNWABI (CONTEXT, FS) This macro allows the target to add operating system specific code ! to the call-frame unwinder to handle the IA-64 `.unwabi' unwinding directive, usually used for signal or interrupt frames. ! This macro is called from `uw_update_context' in libgcc's ! `unwind-ia64.c'. CONTEXT is an `_Unwind_Context'; FS is an ! `_Unwind_FrameState'. Examine `fs->unwabi' for the abi and ! context in the `.unwabi' directive. If the `.unwabi' directive ! can be handled, the register save addresses should be updated in ! FS. -- Macro: TARGET_USES_WEAK_UNWIND_INFO A C expression that evaluates to true if the target requires unwind ! info to be given comdat linkage. Define it to be `1' if comdat ! linkage is necessary. The default is `0'.  File: gccint.info, Node: Stack Checking, Next: Frame Registers, Prev: Exception Handling, Up: Stack and Calling *************** File: gccint.info, Node: Stack Checking *** 30775,30794 **** -------------------------------------------- GCC will check that stack references are within the boundaries of the ! stack, if the option '-fstack-check' is specified, in one of three ways: ! 1. If the value of the 'STACK_CHECK_BUILTIN' macro is nonzero, GCC will assume that you have arranged for full stack checking to be done at appropriate places in the configuration files. GCC will not do other special processing. ! 2. If 'STACK_CHECK_BUILTIN' is zero and the value of the ! 'STACK_CHECK_STATIC_BUILTIN' macro is nonzero, GCC will assume that ! you have arranged for static stack checking (checking of the static ! stack frame of functions) to be done at appropriate places in the ! configuration files. GCC will only emit code to do dynamic stack ! checking (checking on dynamic stack allocations) using the third ! approach below. 3. If neither of the above are true, GCC will generate code to periodically "probe" the stack pointer using the values of the --- 31188,31207 ---- -------------------------------------------- GCC will check that stack references are within the boundaries of the ! stack, if the option `-fstack-check' is specified, in one of three ways: ! 1. If the value of the `STACK_CHECK_BUILTIN' macro is nonzero, GCC will assume that you have arranged for full stack checking to be done at appropriate places in the configuration files. GCC will not do other special processing. ! 2. If `STACK_CHECK_BUILTIN' is zero and the value of the ! `STACK_CHECK_STATIC_BUILTIN' macro is nonzero, GCC will assume ! that you have arranged for static stack checking (checking of the ! static stack frame of functions) to be done at appropriate places ! in the configuration files. GCC will only emit code to do dynamic ! stack checking (checking on dynamic stack allocations) using the ! third approach below. 3. If neither of the above are true, GCC will generate code to periodically "probe" the stack pointer using the values of the *************** stack, if the option '-fstack-check' is *** 30796,30810 **** If neither STACK_CHECK_BUILTIN nor STACK_CHECK_STATIC_BUILTIN is defined, GCC will change its allocation strategy for large objects if ! the option '-fstack-check' is specified: they will always be allocated ! dynamically if their size exceeds 'STACK_CHECK_MAX_VAR_SIZE' bytes. -- Macro: STACK_CHECK_BUILTIN A nonzero value if stack checking is done by the configuration files in a machine-dependent manner. You should define this macro if stack checking is required by the ABI of your machine or if you ! would like to do stack checking in some more efficient way than the ! generic approach. The default value of this macro is zero. -- Macro: STACK_CHECK_STATIC_BUILTIN A nonzero value if static stack checking is done by the --- 31209,31223 ---- If neither STACK_CHECK_BUILTIN nor STACK_CHECK_STATIC_BUILTIN is defined, GCC will change its allocation strategy for large objects if ! the option `-fstack-check' is specified: they will always be allocated ! dynamically if their size exceeds `STACK_CHECK_MAX_VAR_SIZE' bytes. -- Macro: STACK_CHECK_BUILTIN A nonzero value if stack checking is done by the configuration files in a machine-dependent manner. You should define this macro if stack checking is required by the ABI of your machine or if you ! would like to do stack checking in some more efficient way than ! the generic approach. The default value of this macro is zero. -- Macro: STACK_CHECK_STATIC_BUILTIN A nonzero value if static stack checking is done by the *************** dynamically if their size exceeds 'STACK *** 30814,30839 **** value of this macro is zero. -- Macro: STACK_CHECK_PROBE_INTERVAL_EXP ! An integer specifying the interval at which GCC must generate stack ! probe instructions, defined as 2 raised to this integer. You will ! normally define this macro so that the interval be no larger than ! the size of the "guard pages" at the end of a stack area. The ! default value of 12 (4096-byte interval) is suitable for most ! systems. -- Macro: STACK_CHECK_MOVING_SP An integer which is nonzero if GCC should move the stack pointer page by page when doing probes. This can be necessary on systems where the stack pointer contains the bottom address of the memory area accessible to the executing thread at any point in time. In ! this situation an alternate signal stack is required in order to be ! able to recover from a stack overflow. The default value of this ! macro is zero. -- Macro: STACK_CHECK_PROTECT The number of bytes of stack needed to recover from a stack overflow, for languages where such a recovery is supported. The ! default value of 4KB/8KB with the 'setjmp'/'longjmp'-based exception handling mechanism and 8KB/12KB with other exception handling mechanisms should be adequate for most architectures and operating systems. --- 31227,31252 ---- value of this macro is zero. -- Macro: STACK_CHECK_PROBE_INTERVAL_EXP ! An integer specifying the interval at which GCC must generate ! stack probe instructions, defined as 2 raised to this integer. ! You will normally define this macro so that the interval be no ! larger than the size of the "guard pages" at the end of a stack ! area. The default value of 12 (4096-byte interval) is suitable ! for most systems. -- Macro: STACK_CHECK_MOVING_SP An integer which is nonzero if GCC should move the stack pointer page by page when doing probes. This can be necessary on systems where the stack pointer contains the bottom address of the memory area accessible to the executing thread at any point in time. In ! this situation an alternate signal stack is required in order to ! be able to recover from a stack overflow. The default value of ! this macro is zero. -- Macro: STACK_CHECK_PROTECT The number of bytes of stack needed to recover from a stack overflow, for languages where such a recovery is supported. The ! default value of 4KB/8KB with the `setjmp'/`longjmp'-based exception handling mechanism and 8KB/12KB with other exception handling mechanisms should be adequate for most architectures and operating systems. *************** in the opposite case. *** 30845,30855 **** -- Macro: STACK_CHECK_MAX_FRAME_SIZE The maximum size of a stack frame, in bytes. GCC will generate probe instructions in non-leaf functions to ensure at least this ! many bytes of stack are available. If a stack frame is larger than ! this size, stack checking will not be reliable and GCC will issue a ! warning. The default is chosen so that GCC only generates one ! instruction on most systems. You should normally not change the ! default value of this macro. -- Macro: STACK_CHECK_FIXED_FRAME_SIZE GCC uses this value to generate the above warning message. It --- 31258,31268 ---- -- Macro: STACK_CHECK_MAX_FRAME_SIZE The maximum size of a stack frame, in bytes. GCC will generate probe instructions in non-leaf functions to ensure at least this ! many bytes of stack are available. If a stack frame is larger ! than this size, stack checking will not be reliable and GCC will ! issue a warning. The default is chosen so that GCC only generates ! one instruction on most systems. You should normally not change ! the default value of this macro. -- Macro: STACK_CHECK_FIXED_FRAME_SIZE GCC uses this value to generate the above warning message. It *************** in the opposite case. *** 30861,30867 **** -- Macro: STACK_CHECK_MAX_VAR_SIZE The maximum size, in bytes, of an object that GCC will place in the fixed area of the stack frame when the user specifies ! '-fstack-check'. GCC computed the default from the values of the above macros and you will normally not need to override that default. --- 31274,31280 ---- -- Macro: STACK_CHECK_MAX_VAR_SIZE The maximum size, in bytes, of an object that GCC will place in the fixed area of the stack frame when the user specifies ! `-fstack-check'. GCC computed the default from the values of the above macros and you will normally not need to override that default. *************** This discusses registers that address th *** 30875,30931 **** -- Macro: STACK_POINTER_REGNUM The register number of the stack pointer register, which must also ! be a fixed register according to 'FIXED_REGISTERS'. On most machines, the hardware determines which register this is. -- Macro: FRAME_POINTER_REGNUM The register number of the frame pointer register, which is used to access automatic variables in the stack frame. On some machines, ! the hardware determines which register this is. On other machines, ! you can choose any register you wish for this purpose. -- Macro: HARD_FRAME_POINTER_REGNUM On some machines the offset between the frame pointer and starting offset of the automatic variables is not known until after register allocation has been done (for example, because the saved registers are between these two locations). On those machines, define ! 'FRAME_POINTER_REGNUM' the number of a special, fixed register to be used internally until the offset is known, and define ! 'HARD_FRAME_POINTER_REGNUM' to be the actual hard register number used for the frame pointer. You should define this macro only in the very rare circumstances when it is not possible to calculate the offset between the frame ! pointer and the automatic variables until after register allocation ! has been completed. When this macro is defined, you must also ! indicate in your definition of 'ELIMINABLE_REGS' how to eliminate ! 'FRAME_POINTER_REGNUM' into either 'HARD_FRAME_POINTER_REGNUM' or ! 'STACK_POINTER_REGNUM'. Do not define this macro if it would be the same as ! 'FRAME_POINTER_REGNUM'. -- Macro: ARG_POINTER_REGNUM The register number of the arg pointer register, which is used to ! access the function's argument list. On some machines, this is the ! same as the frame pointer register. On some machines, the hardware ! determines which register this is. On other machines, you can ! choose any register you wish for this purpose. If this is not the ! same register as the frame pointer register, then you must mark it ! as a fixed register according to 'FIXED_REGISTERS', or arrange to ! be able to eliminate it (*note Elimination::). -- Macro: HARD_FRAME_POINTER_IS_FRAME_POINTER Define this to a preprocessor constant that is nonzero if ! 'hard_frame_pointer_rtx' and 'frame_pointer_rtx' should be the ! same. The default definition is '(HARD_FRAME_POINTER_REGNUM == FRAME_POINTER_REGNUM)'; you only need to define this macro if that definition is not suitable for use in preprocessor conditionals. -- Macro: HARD_FRAME_POINTER_IS_ARG_POINTER Define this to a preprocessor constant that is nonzero if ! 'hard_frame_pointer_rtx' and 'arg_pointer_rtx' should be the same. ! The default definition is '(HARD_FRAME_POINTER_REGNUM == ARG_POINTER_REGNUM)'; you only need to define this macro if that definition is not suitable for use in preprocessor conditionals. --- 31288,31344 ---- -- Macro: STACK_POINTER_REGNUM The register number of the stack pointer register, which must also ! be a fixed register according to `FIXED_REGISTERS'. On most machines, the hardware determines which register this is. -- Macro: FRAME_POINTER_REGNUM The register number of the frame pointer register, which is used to access automatic variables in the stack frame. On some machines, ! the hardware determines which register this is. On other ! machines, you can choose any register you wish for this purpose. -- Macro: HARD_FRAME_POINTER_REGNUM On some machines the offset between the frame pointer and starting offset of the automatic variables is not known until after register allocation has been done (for example, because the saved registers are between these two locations). On those machines, define ! `FRAME_POINTER_REGNUM' the number of a special, fixed register to be used internally until the offset is known, and define ! `HARD_FRAME_POINTER_REGNUM' to be the actual hard register number used for the frame pointer. You should define this macro only in the very rare circumstances when it is not possible to calculate the offset between the frame ! pointer and the automatic variables until after register ! allocation has been completed. When this macro is defined, you ! must also indicate in your definition of `ELIMINABLE_REGS' how to ! eliminate `FRAME_POINTER_REGNUM' into either ! `HARD_FRAME_POINTER_REGNUM' or `STACK_POINTER_REGNUM'. Do not define this macro if it would be the same as ! `FRAME_POINTER_REGNUM'. -- Macro: ARG_POINTER_REGNUM The register number of the arg pointer register, which is used to ! access the function's argument list. On some machines, this is ! the same as the frame pointer register. On some machines, the ! hardware determines which register this is. On other machines, ! you can choose any register you wish for this purpose. If this is ! not the same register as the frame pointer register, then you must ! mark it as a fixed register according to `FIXED_REGISTERS', or ! arrange to be able to eliminate it (*note Elimination::). -- Macro: HARD_FRAME_POINTER_IS_FRAME_POINTER Define this to a preprocessor constant that is nonzero if ! `hard_frame_pointer_rtx' and `frame_pointer_rtx' should be the ! same. The default definition is `(HARD_FRAME_POINTER_REGNUM == FRAME_POINTER_REGNUM)'; you only need to define this macro if that definition is not suitable for use in preprocessor conditionals. -- Macro: HARD_FRAME_POINTER_IS_ARG_POINTER Define this to a preprocessor constant that is nonzero if ! `hard_frame_pointer_rtx' and `arg_pointer_rtx' should be the same. ! The default definition is `(HARD_FRAME_POINTER_REGNUM == ARG_POINTER_REGNUM)'; you only need to define this macro if that definition is not suitable for use in preprocessor conditionals. *************** This discusses registers that address th *** 30933,30942 **** The register number of the return address pointer register, which is used to access the current function's return address from the stack. On some machines, the return address is not at a fixed ! offset from the frame pointer or stack pointer or argument pointer. ! This register can be defined to point to the return address on the ! stack, and then be converted by 'ELIMINABLE_REGS' into either the ! frame pointer or stack pointer. Do not define this macro unless there is no other way to get the return address from the stack. --- 31346,31355 ---- The register number of the return address pointer register, which is used to access the current function's return address from the stack. On some machines, the return address is not at a fixed ! offset from the frame pointer or stack pointer or argument ! pointer. This register can be defined to point to the return ! address on the stack, and then be converted by `ELIMINABLE_REGS' ! into either the frame pointer or stack pointer. Do not define this macro unless there is no other way to get the return address from the stack. *************** This discusses registers that address th *** 30944,30977 **** -- Macro: STATIC_CHAIN_REGNUM -- Macro: STATIC_CHAIN_INCOMING_REGNUM Register numbers used for passing a function's static chain ! pointer. If register windows are used, the register number as seen ! by the called function is 'STATIC_CHAIN_INCOMING_REGNUM', while the ! register number as seen by the calling function is ! 'STATIC_CHAIN_REGNUM'. If these registers are the same, ! 'STATIC_CHAIN_INCOMING_REGNUM' need not be defined. The static chain register need not be a fixed register. If the static chain is passed in memory, these macros should not be ! defined; instead, the 'TARGET_STATIC_CHAIN' hook should be used. -- Target Hook: rtx TARGET_STATIC_CHAIN (const_tree FNDECL_OR_TYPE, bool INCOMING_P) ! This hook replaces the use of 'STATIC_CHAIN_REGNUM' et al for targets that may use different static chain locations for different nested functions. This may be required if the target has function attributes that affect the calling conventions of the function and those calling conventions use different static chain locations. ! The default version of this hook uses 'STATIC_CHAIN_REGNUM' et al. If the static chain is passed in memory, this hook should be used ! to provide rtx giving 'mem' expressions that denote where they are ! stored. Often the 'mem' expression as seen by the caller will be ! at an offset from the stack pointer and the 'mem' expression as ! seen by the callee will be at an offset from the frame pointer. ! The variables 'stack_pointer_rtx', 'frame_pointer_rtx', and ! 'arg_pointer_rtx' will have been initialized and should be used to refer to those items. -- Macro: DWARF_FRAME_REGISTERS --- 31357,31390 ---- -- Macro: STATIC_CHAIN_REGNUM -- Macro: STATIC_CHAIN_INCOMING_REGNUM Register numbers used for passing a function's static chain ! pointer. If register windows are used, the register number as ! seen by the called function is `STATIC_CHAIN_INCOMING_REGNUM', ! while the register number as seen by the calling function is ! `STATIC_CHAIN_REGNUM'. If these registers are the same, ! `STATIC_CHAIN_INCOMING_REGNUM' need not be defined. The static chain register need not be a fixed register. If the static chain is passed in memory, these macros should not be ! defined; instead, the `TARGET_STATIC_CHAIN' hook should be used. -- Target Hook: rtx TARGET_STATIC_CHAIN (const_tree FNDECL_OR_TYPE, bool INCOMING_P) ! This hook replaces the use of `STATIC_CHAIN_REGNUM' et al for targets that may use different static chain locations for different nested functions. This may be required if the target has function attributes that affect the calling conventions of the function and those calling conventions use different static chain locations. ! The default version of this hook uses `STATIC_CHAIN_REGNUM' et al. If the static chain is passed in memory, this hook should be used ! to provide rtx giving `mem' expressions that denote where they are ! stored. Often the `mem' expression as seen by the caller will be ! at an offset from the stack pointer and the `mem' expression as ! seen by the callee will be at an offset from the frame pointer. The ! variables `stack_pointer_rtx', `frame_pointer_rtx', and ! `arg_pointer_rtx' will have been initialized and should be used to refer to those items. -- Macro: DWARF_FRAME_REGISTERS *************** This discusses registers that address th *** 30989,31006 **** call-saved. If this macro is not defined, it defaults to ! 'FIRST_PSEUDO_REGISTER'. -- Macro: PRE_GCC3_DWARF_FRAME_REGISTERS ! ! This macro is similar to 'DWARF_FRAME_REGISTERS', but is provided for backward compatibility in pre GCC 3.0 compiled code. If this macro is not defined, it defaults to ! 'DWARF_FRAME_REGISTERS'. -- Macro: DWARF_REG_TO_UNWIND_COLUMN (REGNO) - Define this macro if the target's representation for dwarf registers is different than the internal representation for unwind column. Given a dwarf register, this macro should return the --- 31402,31417 ---- call-saved. If this macro is not defined, it defaults to ! `FIRST_PSEUDO_REGISTER'. -- Macro: PRE_GCC3_DWARF_FRAME_REGISTERS ! This macro is similar to `DWARF_FRAME_REGISTERS', but is provided for backward compatibility in pre GCC 3.0 compiled code. If this macro is not defined, it defaults to ! `DWARF_FRAME_REGISTERS'. -- Macro: DWARF_REG_TO_UNWIND_COLUMN (REGNO) Define this macro if the target's representation for dwarf registers is different than the internal representation for unwind column. Given a dwarf register, this macro should return the *************** This discusses registers that address th *** 31009,31041 **** See the PowerPC's SPE target for an example. -- Macro: DWARF_FRAME_REGNUM (REGNO) - Define this macro if the target's representation for dwarf registers used in .eh_frame or .debug_frame is different from that used in other debug info sections. Given a GCC hard register number, this macro should return the .eh_frame register number. ! The default is 'DBX_REGISTER_NUMBER (REGNO)'. - -- Macro: DWARF2_FRAME_REG_OUT (REGNO, FOR_EH) Define this macro to map register numbers held in the call frame ! info that GCC has collected using 'DWARF_FRAME_REGNUM' to those ! that should be output in .debug_frame ('FOR_EH' is zero) and ! .eh_frame ('FOR_EH' is nonzero). The default is to return 'REGNO'. - -- Macro: REG_VALUE_IN_UNWIND_CONTEXT Define this macro if the target stores register values as ! '_Unwind_Word' type in unwind context. It should be defined if ! target register size is larger than the size of 'void *'. The ! default is to store register values as 'void *' type. - -- Macro: ASSUME_EXTENDED_UNWIND_CONTEXT Define this macro to be 1 if the target always uses extended unwind context with version, args_size and by_value fields. If it is undefined, it will be defined to 1 when ! 'REG_VALUE_IN_UNWIND_CONTEXT' is defined and 0 otherwise.  File: gccint.info, Node: Elimination, Next: Stack Arguments, Prev: Frame Registers, Up: Stack and Calling --- 31420,31452 ---- See the PowerPC's SPE target for an example. -- Macro: DWARF_FRAME_REGNUM (REGNO) Define this macro if the target's representation for dwarf registers used in .eh_frame or .debug_frame is different from that used in other debug info sections. Given a GCC hard register number, this macro should return the .eh_frame register number. ! The default is `DBX_REGISTER_NUMBER (REGNO)'. + -- Macro: DWARF2_FRAME_REG_OUT (REGNO, FOR_EH) Define this macro to map register numbers held in the call frame ! info that GCC has collected using `DWARF_FRAME_REGNUM' to those ! that should be output in .debug_frame (`FOR_EH' is zero) and ! .eh_frame (`FOR_EH' is nonzero). The default is to return `REGNO'. + -- Macro: REG_VALUE_IN_UNWIND_CONTEXT Define this macro if the target stores register values as ! `_Unwind_Word' type in unwind context. It should be defined if ! target register size is larger than the size of `void *'. The ! default is to store register values as `void *' type. + -- Macro: ASSUME_EXTENDED_UNWIND_CONTEXT Define this macro to be 1 if the target always uses extended unwind context with version, args_size and by_value fields. If it is undefined, it will be defined to 1 when ! `REG_VALUE_IN_UNWIND_CONTEXT' is defined and 0 otherwise. !  File: gccint.info, Node: Elimination, Next: Stack Arguments, Prev: Frame Registers, Up: Stack and Calling *************** File: gccint.info, Node: Elimination, *** 31046,31086 **** This is about eliminating the frame pointer and arg pointer. -- Target Hook: bool TARGET_FRAME_POINTER_REQUIRED (void) ! This target hook should return 'true' if a function must have and use a frame pointer. This target hook is called in the reload ! pass. If its return value is 'true' the function will have a frame ! pointer. This target hook can in principle examine the current function and decide according to the facts, but on most machines the constant ! 'false' or the constant 'true' suffices. Use 'false' when the machine allows code to be generated with no frame pointer, and ! doing so saves some time or space. Use 'true' when there is no possible advantage to avoiding a frame pointer. In certain cases, the compiler does not know how to produce valid code without a frame pointer. The compiler recognizes those cases and automatically gives the function a frame pointer regardless of ! what 'TARGET_FRAME_POINTER_REQUIRED' returns. You don't need to worry about them. In a function that does not require a frame pointer, the frame pointer register can be allocated for ordinary usage, unless you ! mark it as a fixed register. See 'FIXED_REGISTERS' for more information. ! Default return value is 'false'. -- Macro: INITIAL_FRAME_POINTER_OFFSET (DEPTH-VAR) A C statement to store in the variable DEPTH-VAR the difference between the frame pointer and the stack pointer values immediately after the function prologue. The value would be computed from ! information such as the result of 'get_frame_size ()' and the ! tables of registers 'regs_ever_live' and 'call_used_regs'. ! If 'ELIMINABLE_REGS' is defined, this macro will be not be used and need not be defined. Otherwise, it must be defined even if ! 'TARGET_FRAME_POINTER_REQUIRED' always returns true; in that case, you may set DEPTH-VAR to anything. -- Macro: ELIMINABLE_REGS --- 31457,31497 ---- This is about eliminating the frame pointer and arg pointer. -- Target Hook: bool TARGET_FRAME_POINTER_REQUIRED (void) ! This target hook should return `true' if a function must have and use a frame pointer. This target hook is called in the reload ! pass. If its return value is `true' the function will have a ! frame pointer. This target hook can in principle examine the current function and decide according to the facts, but on most machines the constant ! `false' or the constant `true' suffices. Use `false' when the machine allows code to be generated with no frame pointer, and ! doing so saves some time or space. Use `true' when there is no possible advantage to avoiding a frame pointer. In certain cases, the compiler does not know how to produce valid code without a frame pointer. The compiler recognizes those cases and automatically gives the function a frame pointer regardless of ! what `TARGET_FRAME_POINTER_REQUIRED' returns. You don't need to worry about them. In a function that does not require a frame pointer, the frame pointer register can be allocated for ordinary usage, unless you ! mark it as a fixed register. See `FIXED_REGISTERS' for more information. ! Default return value is `false'. -- Macro: INITIAL_FRAME_POINTER_OFFSET (DEPTH-VAR) A C statement to store in the variable DEPTH-VAR the difference between the frame pointer and the stack pointer values immediately after the function prologue. The value would be computed from ! information such as the result of `get_frame_size ()' and the ! tables of registers `regs_ever_live' and `call_used_regs'. ! If `ELIMINABLE_REGS' is defined, this macro will be not be used and need not be defined. Otherwise, it must be defined even if ! `TARGET_FRAME_POINTER_REQUIRED' always returns true; in that case, you may set DEPTH-VAR to anything. -- Macro: ELIMINABLE_REGS *************** This is about eliminating the frame poin *** 31094,31105 **** initializations, each of which specifies an original and replacement register. ! On some machines, the position of the argument pointer is not known ! until the compilation is completed. In such a case, a separate ! hard register must be used for the argument pointer. This register ! can be eliminated by replacing it with either the frame pointer or ! the argument pointer, depending on whether or not the frame pointer ! has been eliminated. In this case, you might specify: #define ELIMINABLE_REGS \ --- 31505,31516 ---- initializations, each of which specifies an original and replacement register. ! On some machines, the position of the argument pointer is not ! known until the compilation is completed. In such a case, a ! separate hard register must be used for the argument pointer. ! This register can be eliminated by replacing it with either the ! frame pointer or the argument pointer, depending on whether or not ! the frame pointer has been eliminated. In this case, you might specify: #define ELIMINABLE_REGS \ *************** This is about eliminating the frame poin *** 31112,31130 **** -- Target Hook: bool TARGET_CAN_ELIMINATE (const int FROM_REG, const int TO_REG) ! This target hook should returns 'true' if the compiler is allowed to try to replace register number FROM_REG with register number ! TO_REG. This target hook need only be defined if 'ELIMINABLE_REGS' ! is defined, and will usually be 'true', since most of the cases preventing register elimination are things that the compiler already knows about. ! Default return value is 'true'. -- Macro: INITIAL_ELIMINATION_OFFSET (FROM-REG, TO-REG, OFFSET-VAR) ! This macro is similar to 'INITIAL_FRAME_POINTER_OFFSET'. It specifies the initial difference between the specified pair of ! registers. This macro must be defined if 'ELIMINABLE_REGS' is defined.  --- 31523,31541 ---- -- Target Hook: bool TARGET_CAN_ELIMINATE (const int FROM_REG, const int TO_REG) ! This target hook should returns `true' if the compiler is allowed to try to replace register number FROM_REG with register number ! TO_REG. This target hook need only be defined if `ELIMINABLE_REGS' ! is defined, and will usually be `true', since most of the cases preventing register elimination are things that the compiler already knows about. ! Default return value is `true'. -- Macro: INITIAL_ELIMINATION_OFFSET (FROM-REG, TO-REG, OFFSET-VAR) ! This macro is similar to `INITIAL_FRAME_POINTER_OFFSET'. It specifies the initial difference between the specified pair of ! registers. This macro must be defined if `ELIMINABLE_REGS' is defined.  *************** stack. See the following section for ot *** 31138,31146 **** certain arguments in registers. -- Target Hook: bool TARGET_PROMOTE_PROTOTYPES (const_tree FNTYPE) ! This target hook returns 'true' if an argument declared in a ! prototype as an integral type smaller than 'int' should actually be ! passed as an 'int'. In addition to avoiding errors in certain cases of mismatch, it also makes for better code on certain machines. The default is to not promote prototypes. --- 31549,31557 ---- certain arguments in registers. -- Target Hook: bool TARGET_PROMOTE_PROTOTYPES (const_tree FNTYPE) ! This target hook returns `true' if an argument declared in a ! prototype as an integral type smaller than `int' should actually be ! passed as an `int'. In addition to avoiding errors in certain cases of mismatch, it also makes for better code on certain machines. The default is to not promote prototypes. *************** certain arguments in registers. *** 31149,31161 **** outgoing arguments. If the target machine does not have a push instruction, set it to zero. That directs GCC to use an alternate strategy: to allocate the entire argument block and then store the ! arguments into it. When 'PUSH_ARGS' is nonzero, 'PUSH_ROUNDING' must be defined too. -- Macro: PUSH_ARGS_REVERSED A C expression. If nonzero, function arguments will be evaluated from last to first, rather than from first to last. If this macro ! is not defined, it defaults to 'PUSH_ARGS' on targets where the stack and args grow in opposite directions, and 0 otherwise. -- Macro: PUSH_ROUNDING (NPUSHED) --- 31560,31572 ---- outgoing arguments. If the target machine does not have a push instruction, set it to zero. That directs GCC to use an alternate strategy: to allocate the entire argument block and then store the ! arguments into it. When `PUSH_ARGS' is nonzero, `PUSH_ROUNDING' must be defined too. -- Macro: PUSH_ARGS_REVERSED A C expression. If nonzero, function arguments will be evaluated from last to first, rather than from first to last. If this macro ! is not defined, it defaults to `PUSH_ARGS' on targets where the stack and args grow in opposite directions, and 0 otherwise. -- Macro: PUSH_ROUNDING (NPUSHED) *************** certain arguments in registers. *** 31178,31188 **** -- Macro: ACCUMULATE_OUTGOING_ARGS A C expression. If nonzero, the maximum amount of space required for outgoing arguments will be computed and placed into ! 'crtl->outgoing_args_size'. No space will be pushed onto the stack ! for each call; instead, the function prologue should increase the ! stack frame size by this amount. ! Setting both 'PUSH_ARGS' and 'ACCUMULATE_OUTGOING_ARGS' is not proper. -- Macro: REG_PARM_STACK_SPACE (FNDECL) --- 31589,31599 ---- -- Macro: ACCUMULATE_OUTGOING_ARGS A C expression. If nonzero, the maximum amount of space required for outgoing arguments will be computed and placed into ! `crtl->outgoing_args_size'. No space will be pushed onto the ! stack for each call; instead, the function prologue should ! increase the stack frame size by this amount. ! Setting both `PUSH_ARGS' and `ACCUMULATE_OUTGOING_ARGS' is not proper. -- Macro: REG_PARM_STACK_SPACE (FNDECL) *************** certain arguments in registers. *** 31190,31229 **** been allocated for arguments even when their values are passed in registers. ! The value of this macro is the size, in bytes, of the area reserved ! for arguments passed in registers for the function represented by ! FNDECL, which can be zero if GCC is calling a library function. ! The argument FNDECL can be the FUNCTION_DECL, or the type itself of ! the function. This space can be allocated by the caller, or be a part of the ! machine-dependent stack frame: 'OUTGOING_REG_PARM_STACK_SPACE' says which. -- Macro: INCOMING_REG_PARM_STACK_SPACE (FNDECL) ! Like 'REG_PARM_STACK_SPACE', but for incoming register arguments. Define this macro if space guaranteed when compiling a function ! body is different to space required when making a call, a situation ! that can arise with K&R style function definitions. -- Macro: OUTGOING_REG_PARM_STACK_SPACE (FNTYPE) Define this to a nonzero value if it is the responsibility of the caller to allocate the area reserved for arguments passed in ! registers when calling a function of FNTYPE. FNTYPE may be NULL if ! the function called is a library function. ! If 'ACCUMULATE_OUTGOING_ARGS' is defined, this macro controls whether the space for these arguments counts in the value of ! 'crtl->outgoing_args_size'. -- Macro: STACK_PARMS_IN_REG_PARM_AREA ! Define this macro if 'REG_PARM_STACK_SPACE' is defined, but the stack parameters don't skip the area specified by it. ! Normally, when a parameter is not passed in registers, it is placed ! on the stack beyond the 'REG_PARM_STACK_SPACE' area. Defining this ! macro suppresses this behavior and causes the parameter to be ! passed on the stack in its natural location. -- Target Hook: int TARGET_RETURN_POPS_ARGS (tree FUNDECL, tree FUNTYPE, int SIZE) --- 31601,31640 ---- been allocated for arguments even when their values are passed in registers. ! The value of this macro is the size, in bytes, of the area ! reserved for arguments passed in registers for the function ! represented by FNDECL, which can be zero if GCC is calling a ! library function. The argument FNDECL can be the FUNCTION_DECL, ! or the type itself of the function. This space can be allocated by the caller, or be a part of the ! machine-dependent stack frame: `OUTGOING_REG_PARM_STACK_SPACE' says which. -- Macro: INCOMING_REG_PARM_STACK_SPACE (FNDECL) ! Like `REG_PARM_STACK_SPACE', but for incoming register arguments. Define this macro if space guaranteed when compiling a function ! body is different to space required when making a call, a ! situation that can arise with K&R style function definitions. -- Macro: OUTGOING_REG_PARM_STACK_SPACE (FNTYPE) Define this to a nonzero value if it is the responsibility of the caller to allocate the area reserved for arguments passed in ! registers when calling a function of FNTYPE. FNTYPE may be NULL ! if the function called is a library function. ! If `ACCUMULATE_OUTGOING_ARGS' is defined, this macro controls whether the space for these arguments counts in the value of ! `crtl->outgoing_args_size'. -- Macro: STACK_PARMS_IN_REG_PARM_AREA ! Define this macro if `REG_PARM_STACK_SPACE' is defined, but the stack parameters don't skip the area specified by it. ! Normally, when a parameter is not passed in registers, it is ! placed on the stack beyond the `REG_PARM_STACK_SPACE' area. ! Defining this macro suppresses this behavior and causes the ! parameter to be passed on the stack in its natural location. -- Target Hook: int TARGET_RETURN_POPS_ARGS (tree FUNDECL, tree FUNTYPE, int SIZE) *************** certain arguments in registers. *** 31234,31274 **** FUNDECL is a C variable whose value is a tree node that describes the function in question. Normally it is a node of type ! 'FUNCTION_DECL' that describes the declaration of the function. ! From this you can obtain the 'DECL_ATTRIBUTES' of the function. FUNTYPE is a C variable whose value is a tree node that describes the function in question. Normally it is a node of type ! 'FUNCTION_TYPE' that describes the data type of the function. From ! this it is possible to obtain the data types of the value and arguments (if known). ! When a call to a library function is being considered, FUNDECL will ! contain an identifier node for the library function. Thus, if you ! need to distinguish among various library functions, you can do so ! by their names. Note that "library function" in this context means ! a function used to perform arithmetic, whose name is known ! specially in the compiler and was not mentioned in the C code being ! compiled. ! SIZE is the number of bytes of arguments passed on the stack. If a ! variable number of bytes is passed, it is zero, and argument popping will always be the responsibility of the calling function. On the VAX, all functions always pop their arguments, so the definition of this macro is SIZE. On the 68000, using the standard calling convention, no functions pop their arguments, so the value of the macro is always 0 in this case. But an alternative calling ! convention is available in which functions that take a fixed number ! of arguments pop them but other functions (such as 'printf') pop ! nothing (the caller pops all). When this convention is in use, ! FUNTYPE is examined to determine whether a function takes a fixed ! number of arguments. -- Macro: CALL_POPS_ARGS (CUM) A C expression that should indicate the number of bytes a call sequence pops off the stack. It is added to the value of ! 'RETURN_POPS_ARGS' when compiling a function call. CUM is the variable in which all arguments to the called function have been accumulated. --- 31645,31685 ---- FUNDECL is a C variable whose value is a tree node that describes the function in question. Normally it is a node of type ! `FUNCTION_DECL' that describes the declaration of the function. ! From this you can obtain the `DECL_ATTRIBUTES' of the function. FUNTYPE is a C variable whose value is a tree node that describes the function in question. Normally it is a node of type ! `FUNCTION_TYPE' that describes the data type of the function. ! From this it is possible to obtain the data types of the value and arguments (if known). ! When a call to a library function is being considered, FUNDECL ! will contain an identifier node for the library function. Thus, if ! you need to distinguish among various library functions, you can ! do so by their names. Note that "library function" in this ! context means a function used to perform arithmetic, whose name is ! known specially in the compiler and was not mentioned in the C ! code being compiled. ! SIZE is the number of bytes of arguments passed on the stack. If ! a variable number of bytes is passed, it is zero, and argument popping will always be the responsibility of the calling function. On the VAX, all functions always pop their arguments, so the definition of this macro is SIZE. On the 68000, using the standard calling convention, no functions pop their arguments, so the value of the macro is always 0 in this case. But an alternative calling ! convention is available in which functions that take a fixed ! number of arguments pop them but other functions (such as ! `printf') pop nothing (the caller pops all). When this convention ! is in use, FUNTYPE is examined to determine whether a function ! takes a fixed number of arguments. -- Macro: CALL_POPS_ARGS (CUM) A C expression that should indicate the number of bytes a call sequence pops off the stack. It is added to the value of ! `RETURN_POPS_ARGS' when compiling a function call. CUM is the variable in which all arguments to the called function have been accumulated. *************** certain arguments in registers. *** 31277,31283 **** used that pops certain registers off the stack, depending on the arguments that have been passed to the function. Since this is a property of the call site, not of the called function, ! 'RETURN_POPS_ARGS' is not appropriate.  File: gccint.info, Node: Register Arguments, Next: Scalar Return, Prev: Stack Arguments, Up: Stack and Calling --- 31688,31694 ---- used that pops certain registers off the stack, depending on the arguments that have been passed to the function. Since this is a property of the call site, not of the called function, ! `RETURN_POPS_ARGS' is not appropriate.  File: gccint.info, Node: Register Arguments, Next: Scalar Return, Prev: Stack Arguments, Up: Stack and Calling *************** the stack. *** 31297,31370 **** The arguments are CA, which summarizes all the previous arguments; MODE, the machine mode of the argument; TYPE, the data type of the argument as a tree node or 0 if that is not known (which happens ! for C support library functions); and NAMED, which is 'true' for an ! ordinary argument and 'false' for nameless arguments that ! correspond to '...' in the called function's prototype. TYPE can be an incomplete type if a syntax error has previously occurred. ! The return value is usually either a 'reg' RTX for the hard register in which to pass the argument, or zero to pass the argument on the stack. ! The return value can be a 'const_int' which means argument is passed in a target specific slot with specified number. Target hooks should be used to store or load argument in such case. See ! 'TARGET_STORE_BOUNDS_FOR_ARG' and 'TARGET_LOAD_BOUNDS_FOR_ARG' for more information. ! The value of the expression can also be a 'parallel' RTX. This is ! used when an argument is passed in multiple locations. The mode of ! the 'parallel' should be the mode of the entire argument. The ! 'parallel' holds any number of 'expr_list' pairs; each one describes where part of the argument is passed. In each ! 'expr_list' the first operand must be a 'reg' RTX for the hard register in which to pass this part of the argument, and the mode of the register RTX indicates how large this part of the argument ! is. The second operand of the 'expr_list' is a 'const_int' which gives the offset in bytes into the entire argument of where this ! part starts. As a special exception the first 'expr_list' in the ! 'parallel' RTX may have a first operand of zero. This indicates that the entire argument is also stored on the stack. ! The last time this hook is called, it is called with 'MODE == ! VOIDmode', and its result is passed to the 'call' or 'call_value' pattern as operands 2 and 3 respectively. ! The usual way to make the ISO library 'stdarg.h' work on a machine where some arguments are usually passed in registers, is to cause ! nameless arguments to be passed on the stack instead. This is done ! by making 'TARGET_FUNCTION_ARG' return 0 whenever NAMED is 'false'. ! You may use the hook 'targetm.calls.must_pass_in_stack' in the ! definition of this macro to determine if this argument is of a type ! that must be passed in the stack. If 'REG_PARM_STACK_SPACE' is not ! defined and 'TARGET_FUNCTION_ARG' returns nonzero for such an ! argument, the compiler will abort. If 'REG_PARM_STACK_SPACE' is ! defined, the argument will be computed in the stack and then loaded ! into a register. -- Target Hook: bool TARGET_MUST_PASS_IN_STACK (machine_mode MODE, const_tree TYPE) ! This target hook should return 'true' if we should not pass TYPE ! solely in registers. The file 'expr.h' defines a definition that ! is usually appropriate, refer to 'expr.h' for additional documentation. ! -- Target Hook: rtx TARGET_FUNCTION_INCOMING_ARG (cumulative_args_t CA, ! machine_mode MODE, const_tree TYPE, bool NAMED) Define this hook if the target machine has "register windows", so that the register in which a function sees an arguments is not necessarily the same as the one in which the caller passed the argument. ! For such machines, 'TARGET_FUNCTION_ARG' computes the register in which the caller passes the value, and ! 'TARGET_FUNCTION_INCOMING_ARG' should be defined in a similar fashion to tell the function being called where the arguments will arrive. ! If 'TARGET_FUNCTION_INCOMING_ARG' is not defined, ! 'TARGET_FUNCTION_ARG' serves both purposes. -- Target Hook: bool TARGET_USE_PSEUDO_PIC_REG (void) This hook should return 1 in case pseudo register should be created --- 31708,31782 ---- The arguments are CA, which summarizes all the previous arguments; MODE, the machine mode of the argument; TYPE, the data type of the argument as a tree node or 0 if that is not known (which happens ! for C support library functions); and NAMED, which is `true' for ! an ordinary argument and `false' for nameless arguments that ! correspond to `...' in the called function's prototype. TYPE can be an incomplete type if a syntax error has previously occurred. ! The return value is usually either a `reg' RTX for the hard register in which to pass the argument, or zero to pass the argument on the stack. ! The return value can be a `const_int' which means argument is passed in a target specific slot with specified number. Target hooks should be used to store or load argument in such case. See ! `TARGET_STORE_BOUNDS_FOR_ARG' and `TARGET_LOAD_BOUNDS_FOR_ARG' for more information. ! The value of the expression can also be a `parallel' RTX. This is ! used when an argument is passed in multiple locations. The mode ! of the `parallel' should be the mode of the entire argument. The ! `parallel' holds any number of `expr_list' pairs; each one describes where part of the argument is passed. In each ! `expr_list' the first operand must be a `reg' RTX for the hard register in which to pass this part of the argument, and the mode of the register RTX indicates how large this part of the argument ! is. The second operand of the `expr_list' is a `const_int' which gives the offset in bytes into the entire argument of where this ! part starts. As a special exception the first `expr_list' in the ! `parallel' RTX may have a first operand of zero. This indicates that the entire argument is also stored on the stack. ! The last time this hook is called, it is called with `MODE == ! VOIDmode', and its result is passed to the `call' or `call_value' pattern as operands 2 and 3 respectively. ! The usual way to make the ISO library `stdarg.h' work on a machine where some arguments are usually passed in registers, is to cause ! nameless arguments to be passed on the stack instead. This is ! done by making `TARGET_FUNCTION_ARG' return 0 whenever NAMED is ! `false'. ! You may use the hook `targetm.calls.must_pass_in_stack' in the ! definition of this macro to determine if this argument is of a ! type that must be passed in the stack. If `REG_PARM_STACK_SPACE' ! is not defined and `TARGET_FUNCTION_ARG' returns nonzero for such ! an argument, the compiler will abort. If `REG_PARM_STACK_SPACE' is ! defined, the argument will be computed in the stack and then ! loaded into a register. -- Target Hook: bool TARGET_MUST_PASS_IN_STACK (machine_mode MODE, const_tree TYPE) ! This target hook should return `true' if we should not pass TYPE ! solely in registers. The file `expr.h' defines a definition that ! is usually appropriate, refer to `expr.h' for additional documentation. ! -- Target Hook: rtx TARGET_FUNCTION_INCOMING_ARG (cumulative_args_t ! CA, machine_mode MODE, const_tree TYPE, bool NAMED) Define this hook if the target machine has "register windows", so that the register in which a function sees an arguments is not necessarily the same as the one in which the caller passed the argument. ! For such machines, `TARGET_FUNCTION_ARG' computes the register in which the caller passes the value, and ! `TARGET_FUNCTION_INCOMING_ARG' should be defined in a similar fashion to tell the function being called where the arguments will arrive. ! If `TARGET_FUNCTION_INCOMING_ARG' is not defined, ! `TARGET_FUNCTION_ARG' serves both purposes. -- Target Hook: bool TARGET_USE_PSEUDO_PIC_REG (void) This hook should return 1 in case pseudo register should be created *************** the stack. *** 31384,31410 **** On some machines, certain arguments must be passed partially in registers and partially in memory. On these machines, typically the first few words of arguments are passed in registers, and the ! rest on the stack. If a multi-word argument (a 'double' or a structure) crosses that boundary, its first few words must be passed in registers and the rest must be pushed. This macro tells the compiler when this occurs, and how many bytes should go in registers. ! 'TARGET_FUNCTION_ARG' for these arguments should return the first register to be used by the caller for this argument; likewise ! 'TARGET_FUNCTION_INCOMING_ARG', for the called function. -- Target Hook: bool TARGET_PASS_BY_REFERENCE (cumulative_args_t CUM, machine_mode MODE, const_tree TYPE, bool NAMED) ! This target hook should return 'true' if an argument at the position indicated by CUM should be passed by reference. This predicate is queried after target independent reasons for being ! passed by reference, such as 'TREE_ADDRESSABLE (type)'. ! If the hook returns true, a copy of that argument is made in memory ! and a pointer to the argument is passed instead of the argument ! itself. The pointer is passed in whatever way is appropriate for ! passing a pointer to that type. -- Target Hook: bool TARGET_CALLEE_COPIES (cumulative_args_t CUM, machine_mode MODE, const_tree TYPE, bool NAMED) --- 31796,31822 ---- On some machines, certain arguments must be passed partially in registers and partially in memory. On these machines, typically the first few words of arguments are passed in registers, and the ! rest on the stack. If a multi-word argument (a `double' or a structure) crosses that boundary, its first few words must be passed in registers and the rest must be pushed. This macro tells the compiler when this occurs, and how many bytes should go in registers. ! `TARGET_FUNCTION_ARG' for these arguments should return the first register to be used by the caller for this argument; likewise ! `TARGET_FUNCTION_INCOMING_ARG', for the called function. -- Target Hook: bool TARGET_PASS_BY_REFERENCE (cumulative_args_t CUM, machine_mode MODE, const_tree TYPE, bool NAMED) ! This target hook should return `true' if an argument at the position indicated by CUM should be passed by reference. This predicate is queried after target independent reasons for being ! passed by reference, such as `TREE_ADDRESSABLE (type)'. ! If the hook returns true, a copy of that argument is made in ! memory and a pointer to the argument is passed instead of the ! argument itself. The pointer is passed in whatever way is ! appropriate for passing a pointer to that type. -- Target Hook: bool TARGET_CALLEE_COPIES (cumulative_args_t CUM, machine_mode MODE, const_tree TYPE, bool NAMED) *************** the stack. *** 31421,31524 **** -- Macro: CUMULATIVE_ARGS A C type for declaring a variable that is used as the first ! argument of 'TARGET_FUNCTION_ARG' and other related values. For ! some target machines, the type 'int' suffices and can hold the number of bytes of argument so far. ! There is no need to record in 'CUMULATIVE_ARGS' anything about the arguments that have been passed on the stack. The compiler has other variables to keep track of that. For target machines on which all arguments are passed on the stack, there is no need to ! store anything in 'CUMULATIVE_ARGS'; however, the data structure ! must exist and should not be empty, so use 'int'. -- Macro: OVERRIDE_ABI_FORMAT (FNDECL) If defined, this macro is called before generating any code for a function, but after the CFUN descriptor for the function has been ! created. The back end may use this macro to update CFUN to reflect ! an ABI other than that which would normally be used by default. If ! the compiler is generating code for a compiler-generated function, ! FNDECL may be 'NULL'. -- Macro: INIT_CUMULATIVE_ARGS (CUM, FNTYPE, LIBNAME, FNDECL, N_NAMED_ARGS) A C statement (sans semicolon) for initializing the variable CUM for the state at the beginning of the argument list. The variable ! has type 'CUMULATIVE_ARGS'. The value of FNTYPE is the tree node ! for the data type of the function which will receive the args, or 0 ! if the args are to a compiler support library function. For direct ! calls that are not libcalls, FNDECL contain the declaration node of ! the function. FNDECL is also set when 'INIT_CUMULATIVE_ARGS' is ! used to find arguments for the function being compiled. ! N_NAMED_ARGS is set to the number of named arguments, including a ! structure return address if it is passed as a parameter, when ! making a call. When processing incoming arguments, N_NAMED_ARGS is ! set to -1. When processing a call to a compiler support library function, ! LIBNAME identifies which one. It is a 'symbol_ref' rtx which contains the name of the function, as a string. LIBNAME is 0 when an ordinary C function call is being processed. Thus, each time this macro is called, either LIBNAME or FNTYPE is nonzero, but never both of them at once. -- Macro: INIT_CUMULATIVE_LIBCALL_ARGS (CUM, MODE, LIBNAME) ! Like 'INIT_CUMULATIVE_ARGS' but only used for outgoing libcalls, it ! gets a 'MODE' argument instead of FNTYPE, that would be 'NULL'. INDIRECT would always be zero, too. If this macro is not defined, ! 'INIT_CUMULATIVE_ARGS (cum, NULL_RTX, libname, 0)' is used instead. -- Macro: INIT_CUMULATIVE_INCOMING_ARGS (CUM, FNTYPE, LIBNAME) ! Like 'INIT_CUMULATIVE_ARGS' but overrides it for the purposes of finding the arguments for the function being compiled. If this ! macro is undefined, 'INIT_CUMULATIVE_ARGS' is used instead. The value passed for LIBNAME is always 0, since library routines with special calling conventions are never compiled with GCC. The ! argument LIBNAME exists for symmetry with 'INIT_CUMULATIVE_ARGS'. ! -- Target Hook: void TARGET_FUNCTION_ARG_ADVANCE (cumulative_args_t CA, ! machine_mode MODE, const_tree TYPE, bool NAMED) This hook updates the summarizer variable pointed to by CA to advance past an argument in the argument list. The values MODE, TYPE and NAMED describe that argument. Once this is done, the variable CUM is suitable for analyzing the _following_ argument ! with 'TARGET_FUNCTION_ARG', etc. This hook need not do anything if the argument in question was ! passed on the stack. The compiler knows how to track the amount of ! stack space used for arguments without any special help. -- Macro: FUNCTION_ARG_OFFSET (MODE, TYPE) If defined, a C expression that is the number of bytes to add to the offset of the argument passed in memory. This is needed for ! the SPU, which passes 'char' and 'short' arguments in the preferred slot that is in the middle of the quad word instead of starting at the top. -- Macro: FUNCTION_ARG_PADDING (MODE, TYPE) If defined, a C expression which determines whether, and in which direction, to pad out an argument with extra space. The value ! should be of type 'enum direction': either 'upward' to pad above ! the argument, 'downward' to pad below, or 'none' to inhibit padding. The _amount_ of padding is not controlled by this macro, but by the ! target hook 'TARGET_FUNCTION_ARG_ROUND_BOUNDARY'. It is always just enough to reach the next multiple of that boundary. This macro has a default definition which is right for most ! systems. For little-endian machines, the default is to pad upward. ! For big-endian machines, the default is to pad downward for an ! argument of constant size shorter than an 'int', and upward otherwise. -- Macro: PAD_VARARGS_DOWN If defined, a C expression which determines whether the default implementation of va_arg will attempt to pad down before reading the next argument, if that argument is smaller than its aligned ! space as controlled by 'PARM_BOUNDARY'. If this macro is not ! defined, all such arguments are padded down if 'BYTES_BIG_ENDIAN' is true. -- Macro: BLOCK_REG_PADDING (MODE, TYPE, FIRST) --- 31833,31936 ---- -- Macro: CUMULATIVE_ARGS A C type for declaring a variable that is used as the first ! argument of `TARGET_FUNCTION_ARG' and other related values. For ! some target machines, the type `int' suffices and can hold the number of bytes of argument so far. ! There is no need to record in `CUMULATIVE_ARGS' anything about the arguments that have been passed on the stack. The compiler has other variables to keep track of that. For target machines on which all arguments are passed on the stack, there is no need to ! store anything in `CUMULATIVE_ARGS'; however, the data structure ! must exist and should not be empty, so use `int'. -- Macro: OVERRIDE_ABI_FORMAT (FNDECL) If defined, this macro is called before generating any code for a function, but after the CFUN descriptor for the function has been ! created. The back end may use this macro to update CFUN to ! reflect an ABI other than that which would normally be used by ! default. If the compiler is generating code for a ! compiler-generated function, FNDECL may be `NULL'. -- Macro: INIT_CUMULATIVE_ARGS (CUM, FNTYPE, LIBNAME, FNDECL, N_NAMED_ARGS) A C statement (sans semicolon) for initializing the variable CUM for the state at the beginning of the argument list. The variable ! has type `CUMULATIVE_ARGS'. The value of FNTYPE is the tree node ! for the data type of the function which will receive the args, or ! 0 if the args are to a compiler support library function. For ! direct calls that are not libcalls, FNDECL contain the declaration ! node of the function. FNDECL is also set when ! `INIT_CUMULATIVE_ARGS' is used to find arguments for the function ! being compiled. N_NAMED_ARGS is set to the number of named ! arguments, including a structure return address if it is passed as ! a parameter, when making a call. When processing incoming ! arguments, N_NAMED_ARGS is set to -1. When processing a call to a compiler support library function, ! LIBNAME identifies which one. It is a `symbol_ref' rtx which contains the name of the function, as a string. LIBNAME is 0 when an ordinary C function call is being processed. Thus, each time this macro is called, either LIBNAME or FNTYPE is nonzero, but never both of them at once. -- Macro: INIT_CUMULATIVE_LIBCALL_ARGS (CUM, MODE, LIBNAME) ! Like `INIT_CUMULATIVE_ARGS' but only used for outgoing libcalls, ! it gets a `MODE' argument instead of FNTYPE, that would be `NULL'. INDIRECT would always be zero, too. If this macro is not defined, ! `INIT_CUMULATIVE_ARGS (cum, NULL_RTX, libname, 0)' is used instead. -- Macro: INIT_CUMULATIVE_INCOMING_ARGS (CUM, FNTYPE, LIBNAME) ! Like `INIT_CUMULATIVE_ARGS' but overrides it for the purposes of finding the arguments for the function being compiled. If this ! macro is undefined, `INIT_CUMULATIVE_ARGS' is used instead. The value passed for LIBNAME is always 0, since library routines with special calling conventions are never compiled with GCC. The ! argument LIBNAME exists for symmetry with `INIT_CUMULATIVE_ARGS'. ! -- Target Hook: void TARGET_FUNCTION_ARG_ADVANCE (cumulative_args_t ! CA, machine_mode MODE, const_tree TYPE, bool NAMED) This hook updates the summarizer variable pointed to by CA to advance past an argument in the argument list. The values MODE, TYPE and NAMED describe that argument. Once this is done, the variable CUM is suitable for analyzing the _following_ argument ! with `TARGET_FUNCTION_ARG', etc. This hook need not do anything if the argument in question was ! passed on the stack. The compiler knows how to track the amount ! of stack space used for arguments without any special help. -- Macro: FUNCTION_ARG_OFFSET (MODE, TYPE) If defined, a C expression that is the number of bytes to add to the offset of the argument passed in memory. This is needed for ! the SPU, which passes `char' and `short' arguments in the preferred slot that is in the middle of the quad word instead of starting at the top. -- Macro: FUNCTION_ARG_PADDING (MODE, TYPE) If defined, a C expression which determines whether, and in which direction, to pad out an argument with extra space. The value ! should be of type `enum direction': either `upward' to pad above ! the argument, `downward' to pad below, or `none' to inhibit padding. The _amount_ of padding is not controlled by this macro, but by the ! target hook `TARGET_FUNCTION_ARG_ROUND_BOUNDARY'. It is always just enough to reach the next multiple of that boundary. This macro has a default definition which is right for most ! systems. For little-endian machines, the default is to pad ! upward. For big-endian machines, the default is to pad downward ! for an argument of constant size shorter than an `int', and upward otherwise. -- Macro: PAD_VARARGS_DOWN If defined, a C expression which determines whether the default implementation of va_arg will attempt to pad down before reading the next argument, if that argument is smaller than its aligned ! space as controlled by `PARM_BOUNDARY'. If this macro is not ! defined, all such arguments are padded down if `BYTES_BIG_ENDIAN' is true. -- Macro: BLOCK_REG_PADDING (MODE, TYPE, FIRST) *************** the stack. *** 31526,31548 **** registers and memory. FIRST is nonzero if this is the only element. Defining this macro allows better control of register function parameters on big-endian machines, without using ! 'PARALLEL' rtl. In particular, 'MUST_PASS_IN_STACK' need not test padding and mode of types in registers, as there is no longer a ! "wrong" part of a register; For example, a three byte aggregate may ! be passed in the high part of a register if so required. ! -- Target Hook: unsigned int TARGET_FUNCTION_ARG_BOUNDARY (machine_mode ! MODE, const_tree TYPE) This hook returns the alignment boundary, in bits, of an argument with the specified mode and type. The default hook returns ! 'PARM_BOUNDARY' for all arguments. -- Target Hook: unsigned int TARGET_FUNCTION_ARG_ROUND_BOUNDARY (machine_mode MODE, const_tree TYPE) ! Normally, the size of an argument is rounded up to 'PARM_BOUNDARY', ! which is the default value for this hook. You can define this hook ! to return a different value if an argument size must be rounded to ! a larger value. -- Macro: FUNCTION_ARG_REGNO_P (REGNO) A C expression that is nonzero if REGNO is the number of a hard --- 31938,31960 ---- registers and memory. FIRST is nonzero if this is the only element. Defining this macro allows better control of register function parameters on big-endian machines, without using ! `PARALLEL' rtl. In particular, `MUST_PASS_IN_STACK' need not test padding and mode of types in registers, as there is no longer a ! "wrong" part of a register; For example, a three byte aggregate ! may be passed in the high part of a register if so required. ! -- Target Hook: unsigned int TARGET_FUNCTION_ARG_BOUNDARY ! (machine_mode MODE, const_tree TYPE) This hook returns the alignment boundary, in bits, of an argument with the specified mode and type. The default hook returns ! `PARM_BOUNDARY' for all arguments. -- Target Hook: unsigned int TARGET_FUNCTION_ARG_ROUND_BOUNDARY (machine_mode MODE, const_tree TYPE) ! Normally, the size of an argument is rounded up to `PARM_BOUNDARY', ! which is the default value for this hook. You can define this ! hook to return a different value if an argument size must be ! rounded to a larger value. -- Macro: FUNCTION_ARG_REGNO_P (REGNO) A C expression that is nonzero if REGNO is the number of a hard *************** the stack. *** 31557,31579 **** as two scalar parameters. By default, GCC will attempt to pack complex arguments into the target's word size. Some ABIs require complex arguments to be split and treated as their individual ! components. For example, on AIX64, complex floats should be passed ! in a pair of floating point registers, even though a complex float ! would fit in one 64-bit floating point register. ! The default value of this hook is 'NULL', which is treated as always false. -- Target Hook: tree TARGET_BUILD_BUILTIN_VA_LIST (void) ! This hook returns a type node for 'va_list' for the target. The ! default version of the hook returns 'void*'. ! -- Target Hook: int TARGET_ENUM_VA_LIST_P (int IDX, const char **PNAME, ! tree *PTREE) ! This target hook is used in function 'c_common_nodes_and_builtins' to iterate through the target specific builtin types for va_list. ! The variable IDX is used as iterator. PNAME has to be a pointer to ! a 'const char *' and PTREE a pointer to a 'tree' typed variable. The arguments PNAME and PTREE are used to store the result of this macro and are set to the name of the va_list builtin type and its internal type. If the return value of this macro is zero, then --- 31969,31991 ---- as two scalar parameters. By default, GCC will attempt to pack complex arguments into the target's word size. Some ABIs require complex arguments to be split and treated as their individual ! components. For example, on AIX64, complex floats should be ! passed in a pair of floating point registers, even though a ! complex float would fit in one 64-bit floating point register. ! The default value of this hook is `NULL', which is treated as always false. -- Target Hook: tree TARGET_BUILD_BUILTIN_VA_LIST (void) ! This hook returns a type node for `va_list' for the target. The ! default version of the hook returns `void*'. ! -- Target Hook: int TARGET_ENUM_VA_LIST_P (int IDX, const char ! **PNAME, tree *PTREE) ! This target hook is used in function `c_common_nodes_and_builtins' to iterate through the target specific builtin types for va_list. ! The variable IDX is used as iterator. PNAME has to be a pointer to ! a `const char *' and PTREE a pointer to a `tree' typed variable. The arguments PNAME and PTREE are used to store the result of this macro and are set to the name of the va_list builtin type and its internal type. If the return value of this macro is zero, then *************** the stack. *** 31583,31623 **** -- Target Hook: tree TARGET_FN_ABI_VA_LIST (tree FNDECL) This hook returns the va_list type of the calling convention specified by FNDECL. The default version of this hook returns ! 'va_list_type_node'. -- Target Hook: tree TARGET_CANONICAL_VA_LIST_TYPE (tree TYPE) This hook returns the va_list type of the calling convention ! specified by the type of TYPE. If TYPE is not a valid va_list ! type, it returns 'NULL_TREE'. -- Target Hook: tree TARGET_GIMPLIFY_VA_ARG_EXPR (tree VALIST, tree TYPE, gimple_seq *PRE_P, gimple_seq *POST_P) ! This hook performs target-specific gimplification of 'VA_ARG_EXPR'. ! The first two parameters correspond to the arguments to 'va_arg'; ! the latter two are as in 'gimplify.c:gimplify_expr'. -- Target Hook: bool TARGET_VALID_POINTER_MODE (machine_mode MODE) Define this to return nonzero if the port can handle pointers with machine mode MODE. The default version of this hook returns true ! for both 'ptr_mode' and 'Pmode'. -- Target Hook: bool TARGET_REF_MAY_ALIAS_ERRNO (struct ao_ref *REF) ! Define this to return nonzero if the memory reference REF may alias ! with the system C library errno location. The default version of ! this hook assumes the system C library errno location is either a ! declaration of type int or accessed by dereferencing a pointer to ! int. -- Target Hook: bool TARGET_SCALAR_MODE_SUPPORTED_P (machine_mode MODE) Define this to return nonzero if the port is prepared to handle insns involving scalar mode MODE. For a scalar mode to be ! considered supported, all the basic arithmetic and comparisons must ! work. ! The default version of this hook returns true for any mode required ! to handle the basic C types (as defined by the port). Included ! here are the double-word arithmetic supported by the code in ! 'optabs.c'. -- Target Hook: bool TARGET_VECTOR_MODE_SUPPORTED_P (machine_mode MODE) Define this to return nonzero if the port is prepared to handle --- 31995,32036 ---- -- Target Hook: tree TARGET_FN_ABI_VA_LIST (tree FNDECL) This hook returns the va_list type of the calling convention specified by FNDECL. The default version of this hook returns ! `va_list_type_node'. -- Target Hook: tree TARGET_CANONICAL_VA_LIST_TYPE (tree TYPE) This hook returns the va_list type of the calling convention ! specified by the type of TYPE. If TYPE is not a valid va_list ! type, it returns `NULL_TREE'. -- Target Hook: tree TARGET_GIMPLIFY_VA_ARG_EXPR (tree VALIST, tree TYPE, gimple_seq *PRE_P, gimple_seq *POST_P) ! This hook performs target-specific gimplification of ! `VA_ARG_EXPR'. The first two parameters correspond to the ! arguments to `va_arg'; the latter two are as in ! `gimplify.c:gimplify_expr'. -- Target Hook: bool TARGET_VALID_POINTER_MODE (machine_mode MODE) Define this to return nonzero if the port can handle pointers with machine mode MODE. The default version of this hook returns true ! for both `ptr_mode' and `Pmode'. -- Target Hook: bool TARGET_REF_MAY_ALIAS_ERRNO (struct ao_ref *REF) ! Define this to return nonzero if the memory reference REF may ! alias with the system C library errno location. The default ! version of this hook assumes the system C library errno location ! is either a declaration of type int or accessed by dereferencing ! a pointer to int. -- Target Hook: bool TARGET_SCALAR_MODE_SUPPORTED_P (machine_mode MODE) Define this to return nonzero if the port is prepared to handle insns involving scalar mode MODE. For a scalar mode to be ! considered supported, all the basic arithmetic and comparisons ! must work. ! The default version of this hook returns true for any mode ! required to handle the basic C types (as defined by the port). ! Included here are the double-word arithmetic supported by the code ! in `optabs.c'. -- Target Hook: bool TARGET_VECTOR_MODE_SUPPORTED_P (machine_mode MODE) Define this to return nonzero if the port is prepared to handle *************** the stack. *** 31628,31634 **** unsigned HOST_WIDE_INT NELEMS) Return true if GCC should try to use a scalar mode to store an array of NELEMS elements, given that each element has mode MODE. ! Returning true here overrides the usual 'MAX_FIXED_MODE' limit and allows GCC to use any defined integer mode. One use of this hook is to support vector load and store operations --- 32041,32047 ---- unsigned HOST_WIDE_INT NELEMS) Return true if GCC should try to use a scalar mode to store an array of NELEMS elements, given that each element has mode MODE. ! Returning true here overrides the usual `MAX_FIXED_MODE' limit and allows GCC to use any defined integer mode. One use of this hook is to support vector load and store operations *************** the stack. *** 31644,31667 **** int8x8_t val[3]; } int8x8x3_t; ! If this hook allows 'val' to have a scalar mode, then 'int8x8x3_t' ! can have the same mode. GCC can then store 'int8x8x3_t's in registers rather than forcing them onto the stack. -- Target Hook: bool TARGET_LIBGCC_FLOATING_MODE_SUPPORTED_P (machine_mode MODE) Define this to return nonzero if libgcc provides support for the floating-point mode MODE, which is known to pass ! 'TARGET_SCALAR_MODE_SUPPORTED_P'. The default version of this hook ! returns true for all of 'SFmode', 'DFmode', 'XFmode' and 'TFmode', ! if such modes exist. -- Target Hook: bool TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P (machine_mode MODE) Define this to return nonzero for machine modes for which the port has small register classes. If this target hook returns nonzero ! for a given MODE, the compiler will try to minimize the lifetime of ! registers in MODE. The hook may be called with 'VOIDmode' as argument. In this case, the hook is expected to return nonzero if it returns nonzero for any mode. --- 32057,32080 ---- int8x8_t val[3]; } int8x8x3_t; ! If this hook allows `val' to have a scalar mode, then `int8x8x3_t' ! can have the same mode. GCC can then store `int8x8x3_t's in registers rather than forcing them onto the stack. -- Target Hook: bool TARGET_LIBGCC_FLOATING_MODE_SUPPORTED_P (machine_mode MODE) Define this to return nonzero if libgcc provides support for the floating-point mode MODE, which is known to pass ! `TARGET_SCALAR_MODE_SUPPORTED_P'. The default version of this ! hook returns true for all of `SFmode', `DFmode', `XFmode' and ! `TFmode', if such modes exist. -- Target Hook: bool TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P (machine_mode MODE) Define this to return nonzero for machine modes for which the port has small register classes. If this target hook returns nonzero ! for a given MODE, the compiler will try to minimize the lifetime ! of registers in MODE. The hook may be called with `VOIDmode' as argument. In this case, the hook is expected to return nonzero if it returns nonzero for any mode. *************** the stack. *** 31675,31694 **** in an instruction, but the machine modes of the registers set or used in the instruction are already known. And for some machines, register classes are small for, say, integer registers but not for ! floating point registers. For example, the AMD x86-64 architecture ! requires specific registers for the legacy x86 integer ! instructions, but there are many SSE registers for floating point ! operations. On such targets, a good strategy may be to return ! nonzero from this hook for 'INTEGRAL_MODE_P' machine modes but zero ! for the SSE register classes. ! The default version of this hook returns false for any mode. It is ! always safe to redefine this hook to return with a nonzero value. ! But if you unnecessarily define it, you will reduce the amount of ! optimizations that can be performed in some cases. If you do not ! define this hook to return a nonzero value when it is required, the ! compiler will run out of spill registers and print a fatal error ! message.  File: gccint.info, Node: Scalar Return, Next: Aggregate Return, Prev: Register Arguments, Up: Stack and Calling --- 32088,32107 ---- in an instruction, but the machine modes of the registers set or used in the instruction are already known. And for some machines, register classes are small for, say, integer registers but not for ! floating point registers. For example, the AMD x86-64 ! architecture requires specific registers for the legacy x86 ! integer instructions, but there are many SSE registers for ! floating point operations. On such targets, a good strategy may ! be to return nonzero from this hook for `INTEGRAL_MODE_P' machine ! modes but zero for the SSE register classes. ! The default version of this hook returns false for any mode. It ! is always safe to redefine this hook to return with a nonzero ! value. But if you unnecessarily define it, you will reduce the ! amount of optimizations that can be performed in some cases. If ! you do not define this hook to return a nonzero value when it is ! required, the compiler will run out of spill registers and print a ! fatal error message.  File: gccint.info, Node: Scalar Return, Next: Aggregate Return, Prev: Register Arguments, Up: Stack and Calling *************** values--values that can fit in registers *** 31701,31749 **** -- Target Hook: rtx TARGET_FUNCTION_VALUE (const_tree RET_TYPE, const_tree FN_DECL_OR_TYPE, bool OUTGOING) - Define this to return an RTX representing the place where a function returns or receives a value of data type RET_TYPE, a tree node representing a data type. FN_DECL_OR_TYPE is a tree node ! representing 'FUNCTION_DECL' or 'FUNCTION_TYPE' of a function being ! called. If OUTGOING is false, the hook should compute the register ! in which the caller will see the return value. Otherwise, the hook ! should return an RTX representing the place where a function ! returns a value. ! On many machines, only 'TYPE_MODE (RET_TYPE)' is relevant. (Actually, on most machines, scalar values are returned in the same place regardless of mode.) The value of the expression is usually ! a 'reg' RTX for the hard register where the return value is stored. ! The value can also be a 'parallel' RTX, if the return value is in ! multiple places. See 'TARGET_FUNCTION_ARG' for an explanation of ! the 'parallel' form. Note that the callee will populate every ! location specified in the 'parallel', but if the first element of ! the 'parallel' contains the whole return value, callers will use that element as the canonical location and ignore the others. The ! m68k port uses this type of 'parallel' to return pointers in both ! '%a0' (the canonical location) and '%d0'. ! If 'TARGET_PROMOTE_FUNCTION_RETURN' returns true, you must apply ! the same promotion rules specified in 'PROMOTE_MODE' if VALTYPE is a scalar type. If the precise function being called is known, FUNC is a tree node ! ('FUNCTION_DECL') for it; otherwise, FUNC is a null pointer. This ! makes it possible to use a different value-returning convention for ! specific functions when all their calls are known. Some target machines have "register windows" so that the register ! in which a function returns its value is not the same as the one in ! which the caller sees the value. For such machines, you should return different RTX depending on OUTGOING. ! 'TARGET_FUNCTION_VALUE' is not used for return values with aggregate data types, because these are returned in another way. ! See 'TARGET_STRUCT_VALUE_RTX' and related macros, below. -- Macro: FUNCTION_VALUE (VALTYPE, FUNC) ! This macro has been deprecated. Use 'TARGET_FUNCTION_VALUE' for a new target instead. -- Macro: LIBCALL_VALUE (MODE) --- 32114,32161 ---- -- Target Hook: rtx TARGET_FUNCTION_VALUE (const_tree RET_TYPE, const_tree FN_DECL_OR_TYPE, bool OUTGOING) Define this to return an RTX representing the place where a function returns or receives a value of data type RET_TYPE, a tree node representing a data type. FN_DECL_OR_TYPE is a tree node ! representing `FUNCTION_DECL' or `FUNCTION_TYPE' of a function ! being called. If OUTGOING is false, the hook should compute the ! register in which the caller will see the return value. ! Otherwise, the hook should return an RTX representing the place ! where a function returns a value. ! On many machines, only `TYPE_MODE (RET_TYPE)' is relevant. (Actually, on most machines, scalar values are returned in the same place regardless of mode.) The value of the expression is usually ! a `reg' RTX for the hard register where the return value is stored. ! The value can also be a `parallel' RTX, if the return value is in ! multiple places. See `TARGET_FUNCTION_ARG' for an explanation of ! the `parallel' form. Note that the callee will populate every ! location specified in the `parallel', but if the first element of ! the `parallel' contains the whole return value, callers will use that element as the canonical location and ignore the others. The ! m68k port uses this type of `parallel' to return pointers in both ! `%a0' (the canonical location) and `%d0'. ! If `TARGET_PROMOTE_FUNCTION_RETURN' returns true, you must apply ! the same promotion rules specified in `PROMOTE_MODE' if VALTYPE is a scalar type. If the precise function being called is known, FUNC is a tree node ! (`FUNCTION_DECL') for it; otherwise, FUNC is a null pointer. This ! makes it possible to use a different value-returning convention ! for specific functions when all their calls are known. Some target machines have "register windows" so that the register ! in which a function returns its value is not the same as the one ! in which the caller sees the value. For such machines, you should return different RTX depending on OUTGOING. ! `TARGET_FUNCTION_VALUE' is not used for return values with aggregate data types, because these are returned in another way. ! See `TARGET_STRUCT_VALUE_RTX' and related macros, below. -- Macro: FUNCTION_VALUE (VALTYPE, FUNC) ! This macro has been deprecated. Use `TARGET_FUNCTION_VALUE' for a new target instead. -- Macro: LIBCALL_VALUE (MODE) *************** values--values that can fit in registers *** 31773,31779 **** register in which the values of called function may come back. A register whose use for returning values is limited to serving as ! the second of a pair (for a value of type 'double', say) need not be recognized by this macro. So for most machines, this definition suffices: --- 32185,32191 ---- register in which the values of called function may come back. A register whose use for returning values is limited to serving as ! the second of a pair (for a value of type `double', say) need not be recognized by this macro. So for most machines, this definition suffices: *************** values--values that can fit in registers *** 31784,31798 **** macro should recognize only the caller's register numbers. This macro has been deprecated. Use ! 'TARGET_FUNCTION_VALUE_REGNO_P' for a new target instead. -- Target Hook: bool TARGET_FUNCTION_VALUE_REGNO_P (const unsigned int REGNO) ! A target hook that return 'true' if REGNO is the number of a hard register in which the values of called function may come back. A register whose use for returning values is limited to serving as ! the second of a pair (for a value of type 'double', say) need not be recognized by this target hook. If the machine has register windows, so that the caller and the --- 32196,32210 ---- macro should recognize only the caller's register numbers. This macro has been deprecated. Use ! `TARGET_FUNCTION_VALUE_REGNO_P' for a new target instead. -- Target Hook: bool TARGET_FUNCTION_VALUE_REGNO_P (const unsigned int REGNO) ! A target hook that return `true' if REGNO is the number of a hard register in which the values of called function may come back. A register whose use for returning values is limited to serving as ! the second of a pair (for a value of type `double', say) need not be recognized by this target hook. If the machine has register windows, so that the caller and the *************** values--values that can fit in registers *** 31803,31830 **** used. -- Macro: APPLY_RESULT_SIZE ! Define this macro if 'untyped_call' and 'untyped_return' need more ! space than is implied by 'FUNCTION_VALUE_REGNO_P' for saving and restoring an arbitrary return value. -- Target Hook: bool TARGET_OMIT_STRUCT_RETURN_REG Normally, when a function returns a structure by memory, the address is passed as an invisible pointer argument, but the ! compiler also arranges to return the address from the function like ! it would a normal pointer return value. Define this to true if ! that behavior is undesirable on your target. -- Target Hook: bool TARGET_RETURN_IN_MSB (const_tree TYPE) ! This hook should return true if values of type TYPE are returned at ! the most significant end of a register (in other words, if they are ! padded at the least significant end). You can assume that TYPE is ! returned in a register; the caller is required to check this. ! Note that the register provided by 'TARGET_FUNCTION_VALUE' must be able to hold the complete return value. For example, if a 1-, 2- or 3-byte structure is returned at the most significant end of a ! 4-byte register, 'TARGET_FUNCTION_VALUE' should provide an 'SImode' ! rtx.  File: gccint.info, Node: Aggregate Return, Next: Caller Saves, Prev: Scalar Return, Up: Stack and Calling --- 32215,32242 ---- used. -- Macro: APPLY_RESULT_SIZE ! Define this macro if `untyped_call' and `untyped_return' need more ! space than is implied by `FUNCTION_VALUE_REGNO_P' for saving and restoring an arbitrary return value. -- Target Hook: bool TARGET_OMIT_STRUCT_RETURN_REG Normally, when a function returns a structure by memory, the address is passed as an invisible pointer argument, but the ! compiler also arranges to return the address from the function ! like it would a normal pointer return value. Define this to true ! if that behavior is undesirable on your target. -- Target Hook: bool TARGET_RETURN_IN_MSB (const_tree TYPE) ! This hook should return true if values of type TYPE are returned ! at the most significant end of a register (in other words, if they ! are padded at the least significant end). You can assume that TYPE ! is returned in a register; the caller is required to check this. ! Note that the register provided by `TARGET_FUNCTION_VALUE' must be able to hold the complete return value. For example, if a 1-, 2- or 3-byte structure is returned at the most significant end of a ! 4-byte register, `TARGET_FUNCTION_VALUE' should provide an ! `SImode' rtx.  File: gccint.info, Node: Aggregate Return, Next: Caller Saves, Prev: Scalar Return, Up: Stack and Calling *************** File: gccint.info, Node: Aggregate Retu *** 31832,31841 **** 17.9.9 How Large Values Are Returned ------------------------------------ ! When a function value's mode is 'BLKmode' (and in some other cases), the ! value is not returned according to 'TARGET_FUNCTION_VALUE' (*note Scalar ! Return::). Instead, the caller passes the address of a block of memory ! in which the value should be stored. This address is called the "structure value address". This section describes how to control returning structure values in --- 32244,32253 ---- 17.9.9 How Large Values Are Returned ------------------------------------ ! When a function value's mode is `BLKmode' (and in some other cases), ! the value is not returned according to `TARGET_FUNCTION_VALUE' (*note ! Scalar Return::). Instead, the caller passes the address of a block of ! memory in which the value should be stored. This address is called the "structure value address". This section describes how to control returning structure values in *************** memory. *** 31846,31894 **** This target hook should return a nonzero value to say to return the function value in memory, just as large structures are always returned. Here TYPE will be the data type of the value, and FNTYPE ! will be the type of the function doing the returning, or 'NULL' for libcalls. ! Note that values of mode 'BLKmode' must be explicitly handled by ! this function. Also, the option '-fpcc-struct-return' takes effect ! regardless of this macro. On most systems, it is possible to leave ! the hook undefined; this causes a default definition to be used, ! whose value is the constant 1 for 'BLKmode' values, and 0 otherwise. Do not use this hook to indicate that structures and unions should always be returned in memory. You should instead use ! 'DEFAULT_PCC_STRUCT_RETURN' to indicate this. -- Macro: DEFAULT_PCC_STRUCT_RETURN Define this macro to be 1 if all structure and union return values must be in memory. Since this results in slower code, this should ! be defined only if needed for compatibility with other compilers or ! with an ABI. If you define this macro to be 0, then the conventions used for structure and union return values are decided ! by the 'TARGET_RETURN_IN_MEMORY' target hook. If not defined, this defaults to the value 1. -- Target Hook: rtx TARGET_STRUCT_VALUE_RTX (tree FNDECL, int INCOMING) This target hook should return the location of the structure value ! address (normally a 'mem' or 'reg'), or 0 if the address is passed ! as an "invisible" first argument. Note that FNDECL may be 'NULL', for libcalls. You do not need to define this target hook if the address is always passed as an "invisible" first argument. On some architectures the place where the structure value address is found by the called function is not the same place that the ! caller put it. This can be due to register windows, or it could be ! because the function prologue moves it to a different place. ! INCOMING is '1' or '2' when the location is needed in the context ! of the called function, and '0' in the context of the caller. ! If INCOMING is nonzero and the address is to be found on the stack, ! return a 'mem' which refers to the frame pointer. If INCOMING is ! '2', the result is being used to fetch the structure value address ! at the beginning of a function. If you need to emit adjusting ! code, you should do it at this point. -- Macro: PCC_STATIC_STRUCT_RETURN Define this macro if the usual system convention on the target --- 32258,32306 ---- This target hook should return a nonzero value to say to return the function value in memory, just as large structures are always returned. Here TYPE will be the data type of the value, and FNTYPE ! will be the type of the function doing the returning, or `NULL' for libcalls. ! Note that values of mode `BLKmode' must be explicitly handled by ! this function. Also, the option `-fpcc-struct-return' takes ! effect regardless of this macro. On most systems, it is possible ! to leave the hook undefined; this causes a default definition to ! be used, whose value is the constant 1 for `BLKmode' values, and 0 otherwise. Do not use this hook to indicate that structures and unions should always be returned in memory. You should instead use ! `DEFAULT_PCC_STRUCT_RETURN' to indicate this. -- Macro: DEFAULT_PCC_STRUCT_RETURN Define this macro to be 1 if all structure and union return values must be in memory. Since this results in slower code, this should ! be defined only if needed for compatibility with other compilers ! or with an ABI. If you define this macro to be 0, then the conventions used for structure and union return values are decided ! by the `TARGET_RETURN_IN_MEMORY' target hook. If not defined, this defaults to the value 1. -- Target Hook: rtx TARGET_STRUCT_VALUE_RTX (tree FNDECL, int INCOMING) This target hook should return the location of the structure value ! address (normally a `mem' or `reg'), or 0 if the address is passed ! as an "invisible" first argument. Note that FNDECL may be `NULL', for libcalls. You do not need to define this target hook if the address is always passed as an "invisible" first argument. On some architectures the place where the structure value address is found by the called function is not the same place that the ! caller put it. This can be due to register windows, or it could ! be because the function prologue moves it to a different place. ! INCOMING is `1' or `2' when the location is needed in the context ! of the called function, and `0' in the context of the caller. ! If INCOMING is nonzero and the address is to be found on the ! stack, return a `mem' which refers to the frame pointer. If ! INCOMING is `2', the result is being used to fetch the structure ! value address at the beginning of a function. If you need to emit ! adjusting code, you should do it at this point. -- Macro: PCC_STATIC_STRUCT_RETURN Define this macro if the usual system convention on the target *************** memory. *** 31896,31916 **** function to return the address of a static variable containing the value. ! Do not define this if the usual system convention is for the caller ! to pass an address to the subroutine. ! This macro has effect in '-fpcc-struct-return' mode, but it does ! nothing when you use '-freg-struct-return' mode. -- Target Hook: machine_mode TARGET_GET_RAW_RESULT_MODE (int REGNO) This target hook returns the mode to be used when accessing raw ! return registers in '__builtin_return'. Define this macro if the value in REG_RAW_MODE is not correct. -- Target Hook: machine_mode TARGET_GET_RAW_ARG_MODE (int REGNO) This target hook returns the mode to be used when accessing raw ! argument registers in '__builtin_apply_args'. Define this macro if ! the value in REG_RAW_MODE is not correct.  File: gccint.info, Node: Caller Saves, Next: Function Entry, Prev: Aggregate Return, Up: Stack and Calling --- 32308,32328 ---- function to return the address of a static variable containing the value. ! Do not define this if the usual system convention is for the ! caller to pass an address to the subroutine. ! This macro has effect in `-fpcc-struct-return' mode, but it does ! nothing when you use `-freg-struct-return' mode. -- Target Hook: machine_mode TARGET_GET_RAW_RESULT_MODE (int REGNO) This target hook returns the mode to be used when accessing raw ! return registers in `__builtin_return'. Define this macro if the value in REG_RAW_MODE is not correct. -- Target Hook: machine_mode TARGET_GET_RAW_ARG_MODE (int REGNO) This target hook returns the mode to be used when accessing raw ! argument registers in `__builtin_apply_args'. Define this macro ! if the value in REG_RAW_MODE is not correct.  File: gccint.info, Node: Caller Saves, Next: Function Entry, Prev: Aggregate Return, Up: Stack and Calling *************** must live across calls. *** 31925,31933 **** -- Macro: HARD_REGNO_CALLER_SAVE_MODE (REGNO, NREGS) A C expression specifying which mode is required for saving NREGS of a pseudo-register in call-clobbered hard register REGNO. If ! REGNO is unsuitable for caller save, 'VOIDmode' should be returned. ! For most machines this macro need not be defined since GCC will ! select the smallest suitable mode.  File: gccint.info, Node: Function Entry, Next: Profiling, Prev: Caller Saves, Up: Stack and Calling --- 32337,32345 ---- -- Macro: HARD_REGNO_CALLER_SAVE_MODE (REGNO, NREGS) A C expression specifying which mode is required for saving NREGS of a pseudo-register in call-clobbered hard register REGNO. If ! REGNO is unsuitable for caller save, `VOIDmode' should be ! returned. For most machines this macro need not be defined since ! GCC will select the smallest suitable mode.  File: gccint.info, Node: Function Entry, Next: Profiling, Prev: Caller Saves, Up: Stack and Calling *************** This section describes the macros that o *** 31940,31980 **** -- Target Hook: void TARGET_ASM_FUNCTION_PROLOGUE (FILE *FILE, HOST_WIDE_INT SIZE) ! If defined, a function that outputs the assembler code for entry to ! a function. The prologue is responsible for setting up the stack ! frame, initializing the frame pointer register, saving registers ! that must be saved, and allocating SIZE additional bytes of storage ! for the local variables. SIZE is an integer. FILE is a stdio ! stream to which the assembler code should be output. The label for the beginning of the function need not be output by this macro. That has already been done when the macro is run. To determine which registers to save, the macro can refer to the ! array 'regs_ever_live': element R is nonzero if hard register R is used anywhere within the function. This implies the function prologue should save register R, provided it is not one of the ! call-used registers. ('TARGET_ASM_FUNCTION_EPILOGUE' must likewise ! use 'regs_ever_live'.) On machines that have "register windows", the function entry code does not save on the stack the registers that are in the windows, even if they are supposed to be preserved by function calls; ! instead it takes appropriate steps to "push" the register stack, if ! any non-call-used registers are used in the function. On machines where functions may or may not have frame-pointers, the function entry code must vary accordingly; it must set up the frame pointer if one is wanted, and not otherwise. To determine whether a frame pointer is in wanted, the macro can refer to the variable ! 'frame_pointer_needed'. The variable's value will be 1 at run time ! in a function that needs a frame pointer. *Note Elimination::. The function entry code is responsible for allocating any stack space required for the function. This stack space consists of the regions listed below. In most cases, these regions are allocated ! in the order listed, with the last listed region closest to the top ! of the stack (the lowest address if 'STACK_GROWS_DOWNWARD' is defined, and the highest address if it is not defined). You can use a different order for a machine if doing so is more convenient or required for compatibility reasons. Except in cases where --- 32352,32393 ---- -- Target Hook: void TARGET_ASM_FUNCTION_PROLOGUE (FILE *FILE, HOST_WIDE_INT SIZE) ! If defined, a function that outputs the assembler code for entry ! to a function. The prologue is responsible for setting up the ! stack frame, initializing the frame pointer register, saving ! registers that must be saved, and allocating SIZE additional bytes ! of storage for the local variables. SIZE is an integer. FILE is ! a stdio stream to which the assembler code should be output. The label for the beginning of the function need not be output by this macro. That has already been done when the macro is run. To determine which registers to save, the macro can refer to the ! array `regs_ever_live': element R is nonzero if hard register R is used anywhere within the function. This implies the function prologue should save register R, provided it is not one of the ! call-used registers. (`TARGET_ASM_FUNCTION_EPILOGUE' must ! likewise use `regs_ever_live'.) On machines that have "register windows", the function entry code does not save on the stack the registers that are in the windows, even if they are supposed to be preserved by function calls; ! instead it takes appropriate steps to "push" the register stack, ! if any non-call-used registers are used in the function. On machines where functions may or may not have frame-pointers, the function entry code must vary accordingly; it must set up the frame pointer if one is wanted, and not otherwise. To determine whether a frame pointer is in wanted, the macro can refer to the variable ! `frame_pointer_needed'. The variable's value will be 1 at run ! time in a function that needs a frame pointer. *Note ! Elimination::. The function entry code is responsible for allocating any stack space required for the function. This stack space consists of the regions listed below. In most cases, these regions are allocated ! in the order listed, with the last listed region closest to the ! top of the stack (the lowest address if `STACK_GROWS_DOWNWARD' is defined, and the highest address if it is not defined). You can use a different order for a machine if doing so is more convenient or required for compatibility reasons. Except in cases where *************** This section describes the macros that o *** 31998,32053 **** HOST_WIDE_INT SIZE) If defined, a function that outputs the assembler code for exit from a function. The epilogue is responsible for restoring the ! saved registers and stack pointer to their values when the function ! was called, and returning control to the caller. This macro takes ! the same arguments as the macro 'TARGET_ASM_FUNCTION_PROLOGUE', and ! the registers to restore are determined from 'regs_ever_live' and ! 'CALL_USED_REGISTERS' in the same way. On some machines, there is a single instruction that does all the work of returning from the function. On these machines, give that ! instruction the name 'return' and do not define the macro ! 'TARGET_ASM_FUNCTION_EPILOGUE' at all. ! Do not define a pattern named 'return' if you want the ! 'TARGET_ASM_FUNCTION_EPILOGUE' to be used. If you want the target switches to control whether return instructions or epilogues are ! used, define a 'return' pattern with a validity condition that ! tests the target switches appropriately. If the 'return' pattern's ! validity condition is false, epilogues will be used. On machines where functions may or may not have frame-pointers, the function exit code must vary accordingly. Sometimes the code for these two cases is completely different. To determine whether a frame pointer is wanted, the macro can refer to the variable ! 'frame_pointer_needed'. The variable's value will be 1 when compiling a function that needs a frame pointer. ! Normally, 'TARGET_ASM_FUNCTION_PROLOGUE' and ! 'TARGET_ASM_FUNCTION_EPILOGUE' must treat leaf functions specially. ! The C variable 'current_function_is_leaf' is nonzero for such a function. *Note Leaf Functions::. On some machines, some functions pop their arguments on exit while others leave that for the caller to do. For example, the 68020 ! when given '-mrtd' pops arguments in functions that take a fixed number of arguments. ! Your definition of the macro 'RETURN_POPS_ARGS' decides which ! functions pop their own arguments. 'TARGET_ASM_FUNCTION_EPILOGUE' needs to know what was decided. The number of bytes of the current function's arguments that this function should pop is available in ! 'crtl->args.pops_args'. *Note Scalar Return::. ! * A region of 'crtl->args.pretend_args_size' bytes of uninitialized space just underneath the first argument arriving on the stack. ! (This may not be at the very start of the allocated stack region if ! the calling sequence has pushed anything else since pushing the stack arguments. But usually, on such machines, nothing else has been pushed yet, because the function prologue itself does all the ! pushing.) This region is used on machines where an argument may be ! passed partly in registers and partly in memory, and, in some cases ! to support the features in ''. * An area of memory used to save certain registers used by the function. The size of this area, which may also include space for --- 32411,32467 ---- HOST_WIDE_INT SIZE) If defined, a function that outputs the assembler code for exit from a function. The epilogue is responsible for restoring the ! saved registers and stack pointer to their values when the ! function was called, and returning control to the caller. This ! macro takes the same arguments as the macro ! `TARGET_ASM_FUNCTION_PROLOGUE', and the registers to restore are ! determined from `regs_ever_live' and `CALL_USED_REGISTERS' in the ! same way. On some machines, there is a single instruction that does all the work of returning from the function. On these machines, give that ! instruction the name `return' and do not define the macro ! `TARGET_ASM_FUNCTION_EPILOGUE' at all. ! Do not define a pattern named `return' if you want the ! `TARGET_ASM_FUNCTION_EPILOGUE' to be used. If you want the target switches to control whether return instructions or epilogues are ! used, define a `return' pattern with a validity condition that ! tests the target switches appropriately. If the `return' ! pattern's validity condition is false, epilogues will be used. On machines where functions may or may not have frame-pointers, the function exit code must vary accordingly. Sometimes the code for these two cases is completely different. To determine whether a frame pointer is wanted, the macro can refer to the variable ! `frame_pointer_needed'. The variable's value will be 1 when compiling a function that needs a frame pointer. ! Normally, `TARGET_ASM_FUNCTION_PROLOGUE' and ! `TARGET_ASM_FUNCTION_EPILOGUE' must treat leaf functions specially. ! The C variable `current_function_is_leaf' is nonzero for such a function. *Note Leaf Functions::. On some machines, some functions pop their arguments on exit while others leave that for the caller to do. For example, the 68020 ! when given `-mrtd' pops arguments in functions that take a fixed number of arguments. ! Your definition of the macro `RETURN_POPS_ARGS' decides which ! functions pop their own arguments. `TARGET_ASM_FUNCTION_EPILOGUE' needs to know what was decided. The number of bytes of the current function's arguments that this function should pop is available in ! `crtl->args.pops_args'. *Note Scalar Return::. ! * A region of `crtl->args.pretend_args_size' bytes of uninitialized space just underneath the first argument arriving on the stack. ! (This may not be at the very start of the allocated stack region ! if the calling sequence has pushed anything else since pushing the stack arguments. But usually, on such machines, nothing else has been pushed yet, because the function prologue itself does all the ! pushing.) This region is used on machines where an argument may ! be passed partly in registers and partly in memory, and, in some ! cases to support the features in `'. * An area of memory used to save certain registers used by the function. The size of this area, which may also include space for *************** This section describes the macros that o *** 32062,32069 **** occur in the opposite order, with the save area closer to the top of the stack. ! * Optionally, when 'ACCUMULATE_OUTGOING_ARGS' is defined, a region of ! 'crtl->outgoing_args_size' bytes to be used for outgoing argument lists of the function. *Note Stack Arguments::. -- Macro: EXIT_IGNORE_STACK --- 32476,32483 ---- occur in the opposite order, with the save area closer to the top of the stack. ! * Optionally, when `ACCUMULATE_OUTGOING_ARGS' is defined, a region of ! `crtl->outgoing_args_size' bytes to be used for outgoing argument lists of the function. *Note Stack Arguments::. -- Macro: EXIT_IGNORE_STACK *************** This section describes the macros that o *** 32075,32097 **** Note that this macro's value is relevant only for functions for which frame pointers are maintained. It is never safe to delete a ! final stack adjustment in a function that has no frame pointer, and ! the compiler knows this regardless of 'EXIT_IGNORE_STACK'. -- Macro: EPILOGUE_USES (REGNO) Define this macro as a C expression that is nonzero for registers ! that are used by the epilogue or the 'return' pattern. The stack and frame pointer registers are already assumed to be used as needed. -- Macro: EH_USES (REGNO) Define this macro as a C expression that is nonzero for registers ! that are used by the exception handling mechanism, and so should be ! considered live on entry to an exception edge. -- Target Hook: void TARGET_ASM_OUTPUT_MI_THUNK (FILE *FILE, tree ! THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT VCALL_OFFSET, ! tree FUNCTION) A function that outputs the assembler code for a thunk function, used to implement C++ virtual function calls with multiple inheritance. The thunk acts as a wrapper around a virtual --- 32489,32511 ---- Note that this macro's value is relevant only for functions for which frame pointers are maintained. It is never safe to delete a ! final stack adjustment in a function that has no frame pointer, ! and the compiler knows this regardless of `EXIT_IGNORE_STACK'. -- Macro: EPILOGUE_USES (REGNO) Define this macro as a C expression that is nonzero for registers ! that are used by the epilogue or the `return' pattern. The stack and frame pointer registers are already assumed to be used as needed. -- Macro: EH_USES (REGNO) Define this macro as a C expression that is nonzero for registers ! that are used by the exception handling mechanism, and so should ! be considered live on entry to an exception edge. -- Target Hook: void TARGET_ASM_OUTPUT_MI_THUNK (FILE *FILE, tree ! THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT ! VCALL_OFFSET, tree FUNCTION) A function that outputs the assembler code for a thunk function, used to implement C++ virtual function calls with multiple inheritance. The thunk acts as a wrapper around a virtual *************** This section describes the macros that o *** 32100,32144 **** First, emit code to add the integer DELTA to the location that contains the incoming first argument. Assume that this argument ! contains a pointer, and is the one used to pass the 'this' pointer in C++. This is the incoming argument _before_ the function ! prologue, e.g. '%o0' on a sparc. The addition must preserve the values of all other incoming arguments. Then, if VCALL_OFFSET is nonzero, an additional adjustment should ! be made after adding 'delta'. In particular, if P is the adjusted pointer, the following adjustment should be made: p += (*((ptrdiff_t **)p))[vcall_offset/sizeof(ptrdiff_t)] After the additions, emit code to jump to FUNCTION, which is a ! 'FUNCTION_DECL'. This is a direct pure jump, not a call, and does not touch the return address. Hence returning from FUNCTION will ! return to whoever called the current 'thunk'. ! The effect must be as if FUNCTION had been called directly with the ! adjusted first argument. This macro is responsible for emitting ! all of the code for a thunk function; ! 'TARGET_ASM_FUNCTION_PROLOGUE' and 'TARGET_ASM_FUNCTION_EPILOGUE' are not invoked. The THUNK_FNDECL is redundant. (DELTA and FUNCTION have already been extracted from it.) It might possibly be useful on some targets, but probably not. ! If you do not define this macro, the target-independent code in the ! C++ front end will generate a less efficient heavyweight thunk that ! calls FUNCTION instead of jumping to it. The generic approach does ! not support varargs. -- Target Hook: bool TARGET_ASM_CAN_OUTPUT_MI_THUNK (const_tree ! THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT VCALL_OFFSET, ! const_tree FUNCTION) ! A function that returns true if TARGET_ASM_OUTPUT_MI_THUNK would be ! able to output the assembler code for the thunk function specified ! by the arguments it is passed, and false otherwise. In the latter ! case, the generic approach will be used by the C++ front end, with ! the limitations previously exposed.  File: gccint.info, Node: Profiling, Next: Tail Calls, Prev: Function Entry, Up: Stack and Calling --- 32514,32558 ---- First, emit code to add the integer DELTA to the location that contains the incoming first argument. Assume that this argument ! contains a pointer, and is the one used to pass the `this' pointer in C++. This is the incoming argument _before_ the function ! prologue, e.g. `%o0' on a sparc. The addition must preserve the values of all other incoming arguments. Then, if VCALL_OFFSET is nonzero, an additional adjustment should ! be made after adding `delta'. In particular, if P is the adjusted pointer, the following adjustment should be made: p += (*((ptrdiff_t **)p))[vcall_offset/sizeof(ptrdiff_t)] After the additions, emit code to jump to FUNCTION, which is a ! `FUNCTION_DECL'. This is a direct pure jump, not a call, and does not touch the return address. Hence returning from FUNCTION will ! return to whoever called the current `thunk'. ! The effect must be as if FUNCTION had been called directly with ! the adjusted first argument. This macro is responsible for ! emitting all of the code for a thunk function; ! `TARGET_ASM_FUNCTION_PROLOGUE' and `TARGET_ASM_FUNCTION_EPILOGUE' are not invoked. The THUNK_FNDECL is redundant. (DELTA and FUNCTION have already been extracted from it.) It might possibly be useful on some targets, but probably not. ! If you do not define this macro, the target-independent code in ! the C++ front end will generate a less efficient heavyweight thunk ! that calls FUNCTION instead of jumping to it. The generic ! approach does not support varargs. -- Target Hook: bool TARGET_ASM_CAN_OUTPUT_MI_THUNK (const_tree ! THUNK_FNDECL, HOST_WIDE_INT DELTA, HOST_WIDE_INT ! VCALL_OFFSET, const_tree FUNCTION) ! A function that returns true if TARGET_ASM_OUTPUT_MI_THUNK would ! be able to output the assembler code for the thunk function ! specified by the arguments it is passed, and false otherwise. In ! the latter case, the generic approach will be used by the C++ ! front end, with the limitations previously exposed.  File: gccint.info, Node: Profiling, Next: Tail Calls, Prev: Function Entry, Up: Stack and Calling *************** These macros will help you generate code *** 32150,32178 **** -- Macro: FUNCTION_PROFILER (FILE, LABELNO) A C statement or compound statement to output to FILE some ! assembler code to call the profiling subroutine 'mcount'. ! The details of how 'mcount' expects to be called are determined by your operating system environment, not by GCC. To figure them out, compile a small program for profiling using the system's installed C compiler and look at the assembler code that results. ! Older implementations of 'mcount' expect the address of a counter variable to be loaded into some register. The name of this ! variable is 'LP' followed by the number LABELNO, so you would ! generate the name using 'LP%d' in a 'fprintf'. -- Macro: PROFILE_HOOK A C statement or compound statement to output to FILE some assembly ! code to call the profiling subroutine 'mcount' even the target does not support profiling. -- Macro: NO_PROFILE_COUNTERS Define this macro to be an expression with a nonzero value if the ! 'mcount' subroutine on your system does not need a counter variable allocated for each function. This is true for almost all modern implementations. If you define this macro, you must not use the ! LABELNO argument to 'FUNCTION_PROFILER'. -- Macro: PROFILE_BEFORE_PROLOGUE Define this macro if the code for function profiling should come --- 32564,32592 ---- -- Macro: FUNCTION_PROFILER (FILE, LABELNO) A C statement or compound statement to output to FILE some ! assembler code to call the profiling subroutine `mcount'. ! The details of how `mcount' expects to be called are determined by your operating system environment, not by GCC. To figure them out, compile a small program for profiling using the system's installed C compiler and look at the assembler code that results. ! Older implementations of `mcount' expect the address of a counter variable to be loaded into some register. The name of this ! variable is `LP' followed by the number LABELNO, so you would ! generate the name using `LP%d' in a `fprintf'. -- Macro: PROFILE_HOOK A C statement or compound statement to output to FILE some assembly ! code to call the profiling subroutine `mcount' even the target does not support profiling. -- Macro: NO_PROFILE_COUNTERS Define this macro to be an expression with a nonzero value if the ! `mcount' subroutine on your system does not need a counter variable allocated for each function. This is true for almost all modern implementations. If you define this macro, you must not use the ! LABELNO argument to `FUNCTION_PROFILER'. -- Macro: PROFILE_BEFORE_PROLOGUE Define this macro if the code for function profiling should come *************** These macros will help you generate code *** 32180,32190 **** after. -- Target Hook: bool TARGET_KEEP_LEAF_WHEN_PROFILED (void) ! This target hook returns true if the target wants the leaf flag for ! the current function to stay true even if it calls mcount. This ! might make sense for targets using the leaf flag only to determine ! whether a stack frame needs to be generated or not and for which ! the call to mcount is generated before the function prologue.  File: gccint.info, Node: Tail Calls, Next: Stack Smashing Protection, Prev: Profiling, Up: Stack and Calling --- 32594,32605 ---- after. -- Target Hook: bool TARGET_KEEP_LEAF_WHEN_PROFILED (void) ! This target hook returns true if the target wants the leaf flag ! for the current function to stay true even if it calls mcount. ! This might make sense for targets using the leaf flag only to ! determine whether a stack frame needs to be generated or not and ! for which the call to mcount is generated before the function ! prologue.  File: gccint.info, Node: Tail Calls, Next: Stack Smashing Protection, Prev: Profiling, Up: Stack and Calling *************** File: gccint.info, Node: Tail Calls, N *** 32195,32219 **** -- Target Hook: bool TARGET_FUNCTION_OK_FOR_SIBCALL (tree DECL, tree EXP) True if it is OK to do sibling call optimization for the specified ! call expression EXP. DECL will be the called function, or 'NULL' if this is an indirect call. It is not uncommon for limitations of calling conventions to prevent tail calls to functions outside the current unit of translation, or during PIC compilation. The hook is used to ! enforce these restrictions, as the 'sibcall' md pattern can not ! fail, or fall over to a "normal" call. The criteria for successful ! sibling call optimization may vary greatly between different ! architectures. -- Target Hook: void TARGET_EXTRA_LIVE_ON_ENTRY (bitmap REGS) Add any hard registers to REGS that are live on entry to the function. This hook only needs to be defined to provide registers that cannot be found by examination of FUNCTION_ARG_REGNO_P, the callee saved registers, STATIC_CHAIN_INCOMING_REGNUM, ! STATIC_CHAIN_REGNUM, TARGET_STRUCT_VALUE_RTX, FRAME_POINTER_REGNUM, ! EH_USES, FRAME_POINTER_REGNUM, ARG_POINTER_REGNUM, and the ! PIC_OFFSET_TABLE_REGNUM. -- Target Hook: void TARGET_SET_UP_BY_PROLOGUE (struct hard_reg_set_container *) --- 32610,32634 ---- -- Target Hook: bool TARGET_FUNCTION_OK_FOR_SIBCALL (tree DECL, tree EXP) True if it is OK to do sibling call optimization for the specified ! call expression EXP. DECL will be the called function, or `NULL' if this is an indirect call. It is not uncommon for limitations of calling conventions to prevent tail calls to functions outside the current unit of translation, or during PIC compilation. The hook is used to ! enforce these restrictions, as the `sibcall' md pattern can not ! fail, or fall over to a "normal" call. The criteria for ! successful sibling call optimization may vary greatly between ! different architectures. -- Target Hook: void TARGET_EXTRA_LIVE_ON_ENTRY (bitmap REGS) Add any hard registers to REGS that are live on entry to the function. This hook only needs to be defined to provide registers that cannot be found by examination of FUNCTION_ARG_REGNO_P, the callee saved registers, STATIC_CHAIN_INCOMING_REGNUM, ! STATIC_CHAIN_REGNUM, TARGET_STRUCT_VALUE_RTX, ! FRAME_POINTER_REGNUM, EH_USES, FRAME_POINTER_REGNUM, ! ARG_POINTER_REGNUM, and the PIC_OFFSET_TABLE_REGNUM. -- Target Hook: void TARGET_SET_UP_BY_PROLOGUE (struct hard_reg_set_container *) *************** File: gccint.info, Node: Stack Smashing *** 32234,32256 **** --------------------------------- -- Target Hook: tree TARGET_STACK_PROTECT_GUARD (void) ! This hook returns a 'DECL' node for the external variable to use for the stack protection guard. This variable is initialized by the runtime to some random value and is used to initialize the guard value that is placed at the top of the local stack frame. ! The type of this variable must be 'ptr_type_node'. The default version of this hook creates a variable called ! '__stack_chk_guard', which is normally defined in 'libgcc2.c'. -- Target Hook: tree TARGET_STACK_PROTECT_FAIL (void) ! This hook returns a 'CALL_EXPR' that alerts the runtime that the stack protect guard variable has been modified. This expression ! should involve a call to a 'noreturn' function. The default version of this hook invokes a function called ! '__stack_chk_fail', taking no arguments. This function is normally ! defined in 'libgcc2.c'. -- Common Target Hook: bool TARGET_SUPPORTS_SPLIT_STACK (bool REPORT, struct gcc_options *OPTS) --- 32649,32671 ---- --------------------------------- -- Target Hook: tree TARGET_STACK_PROTECT_GUARD (void) ! This hook returns a `DECL' node for the external variable to use for the stack protection guard. This variable is initialized by the runtime to some random value and is used to initialize the guard value that is placed at the top of the local stack frame. ! The type of this variable must be `ptr_type_node'. The default version of this hook creates a variable called ! `__stack_chk_guard', which is normally defined in `libgcc2.c'. -- Target Hook: tree TARGET_STACK_PROTECT_FAIL (void) ! This hook returns a `CALL_EXPR' that alerts the runtime that the stack protect guard variable has been modified. This expression ! should involve a call to a `noreturn' function. The default version of this hook invokes a function called ! `__stack_chk_fail', taking no arguments. This function is ! normally defined in `libgcc2.c'. -- Common Target Hook: bool TARGET_SUPPORTS_SPLIT_STACK (bool REPORT, struct gcc_options *OPTS) *************** File: gccint.info, Node: Miscellaneous *** 32271,32280 **** Set to true if each call that binds to a local definition explicitly clobbers or sets all non-fixed registers modified by performing the call. That is, by the call pattern itself, or by ! code that might be inserted by the linker (e.g. stubs, veneers, branch islands), but not including those modifiable by the callee. The affected registers may be mentioned explicitly in the call ! pattern, or included as clobbers in CALL_INSN_FUNCTION_USAGE. The default version of this hook is set to false. The purpose of this hook is to enable the fipa-ra optimization. --- 32686,32695 ---- Set to true if each call that binds to a local definition explicitly clobbers or sets all non-fixed registers modified by performing the call. That is, by the call pattern itself, or by ! code that might be inserted by the linker (e.g. stubs, veneers, branch islands), but not including those modifiable by the callee. The affected registers may be mentioned explicitly in the call ! pattern, or included as clobbers in CALL_INSN_FUNCTION_USAGE. The default version of this hook is set to false. The purpose of this hook is to enable the fipa-ra optimization. *************** File: gccint.info, Node: Varargs, Next *** 32284,32444 **** 17.10 Implementing the Varargs Macros ===================================== ! GCC comes with an implementation of '' and '' that ! work without change on machines that pass arguments on the stack. Other ! machines require their own implementations of varargs, and the two ! machine independent header files must have conditionals to include it. ! ISO '' differs from traditional '' mainly in the ! calling convention for 'va_start'. The traditional implementation takes ! just one argument, which is the variable in which to store the argument ! pointer. The ISO implementation of 'va_start' takes an additional ! second argument. The user is supposed to write the last named argument ! of the function here. ! However, 'va_start' should not use this argument. The way to find the end of the named arguments is with the built-in functions described below. -- Macro: __builtin_saveregs () ! Use this built-in function to save the argument registers in memory ! so that the varargs mechanism can access them. Both ISO and ! traditional versions of 'va_start' must use '__builtin_saveregs', ! unless you use 'TARGET_SETUP_INCOMING_VARARGS' (see below) instead. ! On some machines, '__builtin_saveregs' is open-coded under the ! control of the target hook 'TARGET_EXPAND_BUILTIN_SAVEREGS'. On other machines, it calls a routine written in assembler language, ! found in 'libgcc2.c'. ! Code generated for the call to '__builtin_saveregs' appears at the beginning of the function, as opposed to where the call to ! '__builtin_saveregs' is written, regardless of what the code is. This is because the registers must be saved before the function starts to use them for its own purposes. -- Macro: __builtin_next_arg (LASTARG) This builtin returns the address of the first anonymous stack ! argument, as type 'void *'. If 'ARGS_GROW_DOWNWARD', it returns the address of the location above the first anonymous stack ! argument. Use it in 'va_start' to initialize the pointer for ! fetching arguments from the stack. Also use it in 'va_start' to verify that the second parameter LASTARG is the last named argument of the current function. -- Macro: __builtin_classify_type (OBJECT) Since each machine has its own conventions for which data types are ! passed in which kind of register, your implementation of 'va_arg' has to embody these conventions. The easiest way to categorize the ! specified data type is to use '__builtin_classify_type' together ! with 'sizeof' and '__alignof__'. ! '__builtin_classify_type' ignores the value of OBJECT, considering only its data type. It returns an integer describing what kind of type that is--integer, floating, pointer, structure, and so on. ! The file 'typeclass.h' defines an enumeration that you can use to ! interpret the values of '__builtin_classify_type'. These machine description macros help implement varargs: -- Target Hook: rtx TARGET_EXPAND_BUILTIN_SAVEREGS (void) ! If defined, this hook produces the machine-specific code for a call ! to '__builtin_saveregs'. This code will be moved to the very beginning of the function, before any parameter access are made. The return value of this function should be an RTX that contains ! the value to use as the return of '__builtin_saveregs'. -- Target Hook: void TARGET_SETUP_INCOMING_VARARGS (cumulative_args_t ARGS_SO_FAR, machine_mode MODE, tree TYPE, int *PRETEND_ARGS_SIZE, int SECOND_TIME) This target hook offers an alternative to using ! '__builtin_saveregs' and defining the hook ! 'TARGET_EXPAND_BUILTIN_SAVEREGS'. Use it to store the anonymous register arguments into the stack so that all the arguments appear ! to have been passed consecutively on the stack. Once this is done, ! you can use the standard implementation of varargs that works for ! machines that pass all their arguments on the stack. ! The argument ARGS_SO_FAR points to the 'CUMULATIVE_ARGS' data ! structure, containing the values that are obtained after processing ! the named arguments. The arguments MODE and TYPE describe the last ! named argument--its machine mode and its data type as a tree node. The target hook should do two things: first, push onto the stack all the argument registers _not_ used for the named arguments, and second, store the size of the data thus pushed into the ! 'int'-valued variable pointed to by PRETEND_ARGS_SIZE. The value that you store here will serve as additional offset for setting up the stack frame. Because you must generate code to push the anonymous arguments at compile time without knowing their data types, ! 'TARGET_SETUP_INCOMING_VARARGS' is only useful on machines that have just a single category of argument register and use it uniformly for all data types. ! If the argument SECOND_TIME is nonzero, it means that the arguments ! of the function are being analyzed for the second time. This ! happens for an inline function, which is not actually compiled ! until the end of the source file. The hook ! 'TARGET_SETUP_INCOMING_VARARGS' should not generate any instructions in this case. -- Target Hook: bool TARGET_STRICT_ARGUMENT_NAMING (cumulative_args_t CA) ! Define this hook to return 'true' if the location where a function argument is passed depends on whether or not it is a named argument. ! This hook controls how the NAMED argument to 'TARGET_FUNCTION_ARG' is set for varargs and stdarg functions. If this hook returns ! 'true', the NAMED argument is always true for named arguments, and ! false for unnamed arguments. If it returns 'false', but ! 'TARGET_PRETEND_OUTGOING_VARARGS_NAMED' returns 'true', then all arguments are treated as named. Otherwise, all named arguments except the last are treated as named. ! You need not define this hook if it always returns 'false'. -- Target Hook: void TARGET_CALL_ARGS (rtx, TREE) While generating RTL for a function call, this target hook is invoked once for each argument passed to the function, either a ! register returned by 'TARGET_FUNCTION_ARG' or a memory location. It is called just before the point where argument registers are stored. The type of the function to be called is also passed as ! the second argument; it is 'NULL_TREE' for libcalls. The ! 'TARGET_END_CALL_ARGS' hook is invoked just after the code to copy ! the return reg has been emitted. This functionality can be used to ! perform special setup of call argument registers if a target needs ! it. For functions without arguments, the hook is called once with ! 'pc_rtx' passed instead of an argument register. Most ports do not ! need to implement anything for this hook. -- Target Hook: void TARGET_END_CALL_ARGS (void) This target hook is invoked while generating RTL for a function call, just after the point where the return reg is copied into a ! pseudo. It signals that all the call argument and return registers ! for the just emitted call are now no longer in use. Most ports do ! not need to implement anything for this hook. -- Target Hook: bool TARGET_PRETEND_OUTGOING_VARARGS_NAMED (cumulative_args_t CA) If you need to conditionally change ABIs so that one works with ! 'TARGET_SETUP_INCOMING_VARARGS', but the other works like neither ! 'TARGET_SETUP_INCOMING_VARARGS' nor 'TARGET_STRICT_ARGUMENT_NAMING' ! was defined, then define this hook to return 'true' if ! 'TARGET_SETUP_INCOMING_VARARGS' is used, 'false' otherwise. ! Otherwise, you should not define this hook. -- Target Hook: rtx TARGET_LOAD_BOUNDS_FOR_ARG (rtx SLOT, rtx ARG, rtx SLOT_NO) ! This hook is used by expand pass to emit insn to load bounds of ARG ! passed in SLOT. Expand pass uses this hook in case bounds of ARG ! are not passed in register. If SLOT is a memory, then bounds are ! loaded as for regular pointer loaded from memory. If SLOT is not a ! memory then SLOT_NO is an integer constant holding number of the ! target dependent special slot which should be used to obtain bounds. Hook returns RTX holding loaded bounds. -- Target Hook: void TARGET_STORE_BOUNDS_FOR_ARG (rtx ARG, rtx SLOT, --- 32699,32862 ---- 17.10 Implementing the Varargs Macros ===================================== ! GCC comes with an implementation of `' and `' that ! work without change on machines that pass arguments on the stack. ! Other machines require their own implementations of varargs, and the ! two machine independent header files must have conditionals to include ! it. ! ISO `' differs from traditional `' mainly in the ! calling convention for `va_start'. The traditional implementation ! takes just one argument, which is the variable in which to store the ! argument pointer. The ISO implementation of `va_start' takes an ! additional second argument. The user is supposed to write the last ! named argument of the function here. ! However, `va_start' should not use this argument. The way to find the end of the named arguments is with the built-in functions described below. -- Macro: __builtin_saveregs () ! Use this built-in function to save the argument registers in ! memory so that the varargs mechanism can access them. Both ISO ! and traditional versions of `va_start' must use ! `__builtin_saveregs', unless you use ! `TARGET_SETUP_INCOMING_VARARGS' (see below) instead. ! On some machines, `__builtin_saveregs' is open-coded under the ! control of the target hook `TARGET_EXPAND_BUILTIN_SAVEREGS'. On other machines, it calls a routine written in assembler language, ! found in `libgcc2.c'. ! Code generated for the call to `__builtin_saveregs' appears at the beginning of the function, as opposed to where the call to ! `__builtin_saveregs' is written, regardless of what the code is. This is because the registers must be saved before the function starts to use them for its own purposes. -- Macro: __builtin_next_arg (LASTARG) This builtin returns the address of the first anonymous stack ! argument, as type `void *'. If `ARGS_GROW_DOWNWARD', it returns the address of the location above the first anonymous stack ! argument. Use it in `va_start' to initialize the pointer for ! fetching arguments from the stack. Also use it in `va_start' to verify that the second parameter LASTARG is the last named argument of the current function. -- Macro: __builtin_classify_type (OBJECT) Since each machine has its own conventions for which data types are ! passed in which kind of register, your implementation of `va_arg' has to embody these conventions. The easiest way to categorize the ! specified data type is to use `__builtin_classify_type' together ! with `sizeof' and `__alignof__'. ! `__builtin_classify_type' ignores the value of OBJECT, considering only its data type. It returns an integer describing what kind of type that is--integer, floating, pointer, structure, and so on. ! The file `typeclass.h' defines an enumeration that you can use to ! interpret the values of `__builtin_classify_type'. These machine description macros help implement varargs: -- Target Hook: rtx TARGET_EXPAND_BUILTIN_SAVEREGS (void) ! If defined, this hook produces the machine-specific code for a ! call to `__builtin_saveregs'. This code will be moved to the very beginning of the function, before any parameter access are made. The return value of this function should be an RTX that contains ! the value to use as the return of `__builtin_saveregs'. -- Target Hook: void TARGET_SETUP_INCOMING_VARARGS (cumulative_args_t ARGS_SO_FAR, machine_mode MODE, tree TYPE, int *PRETEND_ARGS_SIZE, int SECOND_TIME) This target hook offers an alternative to using ! `__builtin_saveregs' and defining the hook ! `TARGET_EXPAND_BUILTIN_SAVEREGS'. Use it to store the anonymous register arguments into the stack so that all the arguments appear ! to have been passed consecutively on the stack. Once this is ! done, you can use the standard implementation of varargs that ! works for machines that pass all their arguments on the stack. ! The argument ARGS_SO_FAR points to the `CUMULATIVE_ARGS' data ! structure, containing the values that are obtained after ! processing the named arguments. The arguments MODE and TYPE ! describe the last named argument--its machine mode and its data ! type as a tree node. The target hook should do two things: first, push onto the stack all the argument registers _not_ used for the named arguments, and second, store the size of the data thus pushed into the ! `int'-valued variable pointed to by PRETEND_ARGS_SIZE. The value that you store here will serve as additional offset for setting up the stack frame. Because you must generate code to push the anonymous arguments at compile time without knowing their data types, ! `TARGET_SETUP_INCOMING_VARARGS' is only useful on machines that have just a single category of argument register and use it uniformly for all data types. ! If the argument SECOND_TIME is nonzero, it means that the ! arguments of the function are being analyzed for the second time. ! This happens for an inline function, which is not actually ! compiled until the end of the source file. The hook ! `TARGET_SETUP_INCOMING_VARARGS' should not generate any instructions in this case. -- Target Hook: bool TARGET_STRICT_ARGUMENT_NAMING (cumulative_args_t CA) ! Define this hook to return `true' if the location where a function argument is passed depends on whether or not it is a named argument. ! This hook controls how the NAMED argument to `TARGET_FUNCTION_ARG' is set for varargs and stdarg functions. If this hook returns ! `true', the NAMED argument is always true for named arguments, and ! false for unnamed arguments. If it returns `false', but ! `TARGET_PRETEND_OUTGOING_VARARGS_NAMED' returns `true', then all arguments are treated as named. Otherwise, all named arguments except the last are treated as named. ! You need not define this hook if it always returns `false'. -- Target Hook: void TARGET_CALL_ARGS (rtx, TREE) While generating RTL for a function call, this target hook is invoked once for each argument passed to the function, either a ! register returned by `TARGET_FUNCTION_ARG' or a memory location. It is called just before the point where argument registers are stored. The type of the function to be called is also passed as ! the second argument; it is `NULL_TREE' for libcalls. The ! `TARGET_END_CALL_ARGS' hook is invoked just after the code to copy ! the return reg has been emitted. This functionality can be used ! to perform special setup of call argument registers if a target ! needs it. For functions without arguments, the hook is called ! once with `pc_rtx' passed instead of an argument register. Most ! ports do not need to implement anything for this hook. -- Target Hook: void TARGET_END_CALL_ARGS (void) This target hook is invoked while generating RTL for a function call, just after the point where the return reg is copied into a ! pseudo. It signals that all the call argument and return ! registers for the just emitted call are now no longer in use. ! Most ports do not need to implement anything for this hook. -- Target Hook: bool TARGET_PRETEND_OUTGOING_VARARGS_NAMED (cumulative_args_t CA) If you need to conditionally change ABIs so that one works with ! `TARGET_SETUP_INCOMING_VARARGS', but the other works like neither ! `TARGET_SETUP_INCOMING_VARARGS' nor ! `TARGET_STRICT_ARGUMENT_NAMING' was defined, then define this hook ! to return `true' if `TARGET_SETUP_INCOMING_VARARGS' is used, ! `false' otherwise. Otherwise, you should not define this hook. -- Target Hook: rtx TARGET_LOAD_BOUNDS_FOR_ARG (rtx SLOT, rtx ARG, rtx SLOT_NO) ! This hook is used by expand pass to emit insn to load bounds of ! ARG passed in SLOT. Expand pass uses this hook in case bounds of ! ARG are not passed in register. If SLOT is a memory, then bounds ! are loaded as for regular pointer loaded from memory. If SLOT is ! not a memory then SLOT_NO is an integer constant holding number of ! the target dependent special slot which should be used to obtain bounds. Hook returns RTX holding loaded bounds. -- Target Hook: void TARGET_STORE_BOUNDS_FOR_ARG (rtx ARG, rtx SLOT, *************** below. *** 32446,32459 **** This hook is used by expand pass to emit insns to store BOUNDS of ARG passed in SLOT. Expand pass uses this hook in case BOUNDS of ARG are not passed in register. If SLOT is a memory, then BOUNDS ! are stored as for regular pointer stored in memory. If SLOT is not ! a memory then SLOT_NO is an integer constant holding number of the ! target dependent special slot which should be used to store BOUNDS. -- Target Hook: rtx TARGET_LOAD_RETURNED_BOUNDS (rtx SLOT) This hook is used by expand pass to emit insn to load bounds ! returned by function call in SLOT. Hook returns RTX holding loaded ! bounds. -- Target Hook: void TARGET_STORE_RETURNED_BOUNDS (rtx SLOT, rtx BOUNDS) --- 32864,32878 ---- This hook is used by expand pass to emit insns to store BOUNDS of ARG passed in SLOT. Expand pass uses this hook in case BOUNDS of ARG are not passed in register. If SLOT is a memory, then BOUNDS ! are stored as for regular pointer stored in memory. If SLOT is ! not a memory then SLOT_NO is an integer constant holding number of ! the target dependent special slot which should be used to store ! BOUNDS. -- Target Hook: rtx TARGET_LOAD_RETURNED_BOUNDS (rtx SLOT) This hook is used by expand pass to emit insn to load bounds ! returned by function call in SLOT. Hook returns RTX holding ! loaded bounds. -- Target Hook: void TARGET_STORE_RETURNED_BOUNDS (rtx SLOT, rtx BOUNDS) *************** below. *** 32464,32477 **** RET_TYPE, const_tree FN_DECL_OR_TYPE, bool OUTGOING) Define this to return an RTX representing the place where a function returns bounds for returned pointers. Arguments meaning ! is similar to 'TARGET_FUNCTION_VALUE'. -- Target Hook: void TARGET_SETUP_INCOMING_VARARG_BOUNDS (cumulative_args_t ARGS_SO_FAR, enum machine_mode MODE, tree TYPE, int *PRETEND_ARGS_SIZE, int SECOND_TIME) ! Use it to store bounds for anonymous register arguments stored into ! the stack. Arguments meaning is similar to ! 'TARGET_SETUP_INCOMING_VARARGS'.  File: gccint.info, Node: Trampolines, Next: Library Calls, Prev: Varargs, Up: Target Macros --- 32883,32896 ---- RET_TYPE, const_tree FN_DECL_OR_TYPE, bool OUTGOING) Define this to return an RTX representing the place where a function returns bounds for returned pointers. Arguments meaning ! is similar to `TARGET_FUNCTION_VALUE'. -- Target Hook: void TARGET_SETUP_INCOMING_VARARG_BOUNDS (cumulative_args_t ARGS_SO_FAR, enum machine_mode MODE, tree TYPE, int *PRETEND_ARGS_SIZE, int SECOND_TIME) ! Use it to store bounds for anonymous register arguments stored ! into the stack. Arguments meaning is similar to ! `TARGET_SETUP_INCOMING_VARARGS'.  File: gccint.info, Node: Trampolines, Next: Library Calls, Prev: Varargs, Up: Target Macros *************** File: gccint.info, Node: Trampolines, *** 32479,32488 **** 17.11 Trampolines for Nested Functions ====================================== ! A "trampoline" is a small piece of code that is created at run time when ! the address of a nested function is taken. It normally resides on the ! stack, in the stack frame of the containing function. These macros tell ! GCC how to generate code to allocate and initialize a trampoline. The instructions in the trampoline must do two things: load a constant address into the static chain register, and jump to the real address of --- 32898,32907 ---- 17.11 Trampolines for Nested Functions ====================================== ! A "trampoline" is a small piece of code that is created at run time ! when the address of a nested function is taken. It normally resides on ! the stack, in the stack frame of the containing function. These macros ! tell GCC how to generate code to allocate and initialize a trampoline. The instructions in the trampoline must do two things: load a constant address into the static chain register, and jump to the real address of *************** may be necessary to take out pieces of t *** 32502,32510 **** separately. -- Target Hook: void TARGET_ASM_TRAMPOLINE_TEMPLATE (FILE *F) ! This hook is called by 'assemble_trampoline_template' to output, on ! the stream F, assembler code for a block of data that contains the ! constant parts of a trampoline. This code should not include a label--the label is taken care of automatically. If you do not define this hook, it means no template is needed for --- 32921,32929 ---- separately. -- Target Hook: void TARGET_ASM_TRAMPOLINE_TEMPLATE (FILE *F) ! This hook is called by `assemble_trampoline_template' to output, ! on the stream F, assembler code for a block of data that contains ! the constant parts of a trampoline. This code should not include a label--the label is taken care of automatically. If you do not define this hook, it means no template is needed for *************** separately. *** 32515,32521 **** -- Macro: TRAMPOLINE_SECTION Return the section into which the trampoline template is to be placed (*note Sections::). The default value is ! 'readonly_data_section'. -- Macro: TRAMPOLINE_SIZE A C expression for the size in bytes of the trampoline, as an --- 32934,32940 ---- -- Macro: TRAMPOLINE_SECTION Return the section into which the trampoline template is to be placed (*note Sections::). The default value is ! `readonly_data_section'. -- Macro: TRAMPOLINE_SIZE A C expression for the size in bytes of the trampoline, as an *************** separately. *** 32524,32546 **** -- Macro: TRAMPOLINE_ALIGNMENT Alignment required for trampolines, in bits. ! If you don't define this macro, the value of 'FUNCTION_ALIGNMENT' is used for aligning trampolines. -- Target Hook: void TARGET_TRAMPOLINE_INIT (rtx M_TRAMP, tree FNDECL, rtx STATIC_CHAIN) This hook is called to initialize a trampoline. M_TRAMP is an RTX for the memory block for the trampoline; FNDECL is the ! 'FUNCTION_DECL' for the nested function; STATIC_CHAIN is an RTX for ! the static chain value that should be passed to the function when ! it is called. ! If the target defines 'TARGET_ASM_TRAMPOLINE_TEMPLATE', then the first thing this hook should do is emit a block move into M_TRAMP ! from the memory block returned by 'assemble_trampoline_template'. Note that the block move need only cover the constant parts of the trampoline. If the target isolates the variable parts of the ! trampoline to the end, not all 'TRAMPOLINE_SIZE' bytes need be copied. If the target requires any other actions, such as flushing caches --- 32943,32965 ---- -- Macro: TRAMPOLINE_ALIGNMENT Alignment required for trampolines, in bits. ! If you don't define this macro, the value of `FUNCTION_ALIGNMENT' is used for aligning trampolines. -- Target Hook: void TARGET_TRAMPOLINE_INIT (rtx M_TRAMP, tree FNDECL, rtx STATIC_CHAIN) This hook is called to initialize a trampoline. M_TRAMP is an RTX for the memory block for the trampoline; FNDECL is the ! `FUNCTION_DECL' for the nested function; STATIC_CHAIN is an RTX ! for the static chain value that should be passed to the function ! when it is called. ! If the target defines `TARGET_ASM_TRAMPOLINE_TEMPLATE', then the first thing this hook should do is emit a block move into M_TRAMP ! from the memory block returned by `assemble_trampoline_template'. Note that the block move need only cover the constant parts of the trampoline. If the target isolates the variable parts of the ! trampoline to the end, not all `TRAMPOLINE_SIZE' bytes need be copied. If the target requires any other actions, such as flushing caches *************** separately. *** 32550,32566 **** -- Target Hook: rtx TARGET_TRAMPOLINE_ADJUST_ADDRESS (rtx ADDR) This hook should perform any machine-specific adjustment in the address of the trampoline. Its argument contains the address of ! the memory block that was passed to 'TARGET_TRAMPOLINE_INIT'. In ! case the address to be used for a function call should be different ! from the address at which the template was stored, the different ! address should be returned; otherwise ADDR should be returned ! unchanged. If this hook is not defined, ADDR will be used for ! function calls. Implementing trampolines is difficult on many machines because they have separate instruction and data caches. Writing into a stack ! location fails to clear the memory in the instruction cache, so when the ! program jumps to that location, it executes the old contents. Here are two possible solutions. One is to clear the relevant parts of the instruction cache whenever a trampoline is set up. The other is to --- 32969,32985 ---- -- Target Hook: rtx TARGET_TRAMPOLINE_ADJUST_ADDRESS (rtx ADDR) This hook should perform any machine-specific adjustment in the address of the trampoline. Its argument contains the address of ! the memory block that was passed to `TARGET_TRAMPOLINE_INIT'. In ! case the address to be used for a function call should be ! different from the address at which the template was stored, the ! different address should be returned; otherwise ADDR should be ! returned unchanged. If this hook is not defined, ADDR will be ! used for function calls. Implementing trampolines is difficult on many machines because they have separate instruction and data caches. Writing into a stack ! location fails to clear the memory in the instruction cache, so when ! the program jumps to that location, it executes the old contents. Here are two possible solutions. One is to clear the relevant parts of the instruction cache whenever a trampoline is set up. The other is to *************** the following macro. *** 32574,32600 **** -- Macro: CLEAR_INSN_CACHE (BEG, END) If defined, expands to a C expression clearing the _instruction cache_ in the specified interval. The definition of this macro ! would typically be a series of 'asm' statements. Both BEG and END are both pointer expressions. To use a standard subroutine, define the following macro. In addition, you must make sure that the instructions in a trampoline fill an entire cache line with identical instructions, or else ensure that the beginning of the trampoline code is always aligned at the same point in ! its cache line. Look in 'm68k.h' as a guide. -- Macro: TRANSFER_FROM_TRAMPOLINE Define this macro if trampolines need a special subroutine to do ! their work. The macro should expand to a series of 'asm' statements which will be compiled with GCC. They go in a library ! function named '__transfer_from_trampoline'. If you need to avoid executing the ordinary prologue code of a compiled C function when you jump to the subroutine, you can do so by placing a special label of your own in the assembler code. Use ! one 'asm' statement to generate an assembler label, and another to ! make the label global. Then trampolines can use that label to jump ! directly to your special assembler code.  File: gccint.info, Node: Library Calls, Next: Addressing Modes, Prev: Trampolines, Up: Target Macros --- 32993,33019 ---- -- Macro: CLEAR_INSN_CACHE (BEG, END) If defined, expands to a C expression clearing the _instruction cache_ in the specified interval. The definition of this macro ! would typically be a series of `asm' statements. Both BEG and END are both pointer expressions. To use a standard subroutine, define the following macro. In addition, you must make sure that the instructions in a trampoline fill an entire cache line with identical instructions, or else ensure that the beginning of the trampoline code is always aligned at the same point in ! its cache line. Look in `m68k.h' as a guide. -- Macro: TRANSFER_FROM_TRAMPOLINE Define this macro if trampolines need a special subroutine to do ! their work. The macro should expand to a series of `asm' statements which will be compiled with GCC. They go in a library ! function named `__transfer_from_trampoline'. If you need to avoid executing the ordinary prologue code of a compiled C function when you jump to the subroutine, you can do so by placing a special label of your own in the assembler code. Use ! one `asm' statement to generate an assembler label, and another to ! make the label global. Then trampolines can use that label to ! jump directly to your special assembler code.  File: gccint.info, Node: Library Calls, Next: Addressing Modes, Prev: Trampolines, Up: Target Macros *************** Here is an explanation of implicit calls *** 32606,32635 **** -- Macro: DECLARE_LIBRARY_RENAMES This macro, if defined, should expand to a piece of C code that ! will get expanded when compiling functions for libgcc.a. It can be ! used to provide alternate names for GCC's internal library functions if there are ABI-mandated names that the compiler should provide. -- Target Hook: void TARGET_INIT_LIBFUNCS (void) This hook should declare additional library routines or rename ! existing ones, using the functions 'set_optab_libfunc' and ! 'init_one_libfunc' defined in 'optabs.c'. 'init_optabs' calls this ! macro after initializing all the normal library routines. ! The default is to do nothing. Most ports don't need to define this ! hook. -- Target Hook: bool TARGET_LIBFUNC_GNU_PREFIX If false (the default), internal library routines start with two ! underscores. If set to true, these routines start with '__gnu_' ! instead. E.g., '__muldi3' changes to '__gnu_muldi3'. This ! currently only affects functions defined in 'libgcc2.c'. If this ! is set to true, the 'tm.h' file must also '#define LIBGCC2_GNU_PREFIX'. -- Macro: FLOAT_LIB_COMPARE_RETURNS_BOOL (MODE, COMPARISON) ! This macro should return 'true' if the library routine that implements the floating point comparison operator COMPARISON in mode MODE will return a boolean, and FALSE if it will return a tristate. --- 33025,33054 ---- -- Macro: DECLARE_LIBRARY_RENAMES This macro, if defined, should expand to a piece of C code that ! will get expanded when compiling functions for libgcc.a. It can ! be used to provide alternate names for GCC's internal library functions if there are ABI-mandated names that the compiler should provide. -- Target Hook: void TARGET_INIT_LIBFUNCS (void) This hook should declare additional library routines or rename ! existing ones, using the functions `set_optab_libfunc' and ! `init_one_libfunc' defined in `optabs.c'. `init_optabs' calls ! this macro after initializing all the normal library routines. ! The default is to do nothing. Most ports don't need to define ! this hook. -- Target Hook: bool TARGET_LIBFUNC_GNU_PREFIX If false (the default), internal library routines start with two ! underscores. If set to true, these routines start with `__gnu_' ! instead. E.g., `__muldi3' changes to `__gnu_muldi3'. This ! currently only affects functions defined in `libgcc2.c'. If this ! is set to true, the `tm.h' file must also `#define LIBGCC2_GNU_PREFIX'. -- Macro: FLOAT_LIB_COMPARE_RETURNS_BOOL (MODE, COMPARISON) ! This macro should return `true' if the library routine that implements the floating point comparison operator COMPARISON in mode MODE will return a boolean, and FALSE if it will return a tristate. *************** Here is an explanation of implicit calls *** 32639,32651 **** ports don't need to define this macro. -- Macro: TARGET_LIB_INT_CMP_BIASED ! This macro should evaluate to 'true' if the integer comparison ! functions (like '__cmpdi2') return 0 to indicate that the first operand is smaller than the second, 1 to indicate that they are ! equal, and 2 to indicate that the first operand is greater than the ! second. If this macro evaluates to 'false' the comparison functions return -1, 0, and 1 instead of 0, 1, and 2. If the ! target uses the routines in 'libgcc.a', you do not need to define this macro. -- Macro: TARGET_HAS_NO_HW_DIVIDE --- 33058,33070 ---- ports don't need to define this macro. -- Macro: TARGET_LIB_INT_CMP_BIASED ! This macro should evaluate to `true' if the integer comparison ! functions (like `__cmpdi2') return 0 to indicate that the first operand is smaller than the second, 1 to indicate that they are ! equal, and 2 to indicate that the first operand is greater than ! the second. If this macro evaluates to `false' the comparison functions return -1, 0, and 1 instead of 0, 1, and 2. If the ! target uses the routines in `libgcc.a', you do not need to define this macro. -- Macro: TARGET_HAS_NO_HW_DIVIDE *************** Here is an explanation of implicit calls *** 32656,32676 **** algorithm which make use of a 64-bit by 32-bit divide primitive. -- Macro: TARGET_EDOM ! The value of 'EDOM' on the target machine, as a C integer constant expression. If you don't define this macro, GCC does not attempt ! to deposit the value of 'EDOM' into 'errno' directly. Look in ! '/usr/include/errno.h' to find the value of 'EDOM' on your system. ! If you do not define 'TARGET_EDOM', then compiled code reports ! domain errors by calling the library function and letting it report ! the error. If mathematical functions on your system use 'matherr' ! when there is an error, then you should leave 'TARGET_EDOM' ! undefined so that 'matherr' is used normally. -- Macro: GEN_ERRNO_RTX Define this macro as a C expression to create an rtl expression ! that refers to the global "variable" 'errno'. (On certain systems, ! 'errno' may not actually be a variable.) If you don't define this macro, a reasonable default is used. -- Target Hook: bool TARGET_LIBC_HAS_FUNCTION (enum function_class --- 33075,33095 ---- algorithm which make use of a 64-bit by 32-bit divide primitive. -- Macro: TARGET_EDOM ! The value of `EDOM' on the target machine, as a C integer constant expression. If you don't define this macro, GCC does not attempt ! to deposit the value of `EDOM' into `errno' directly. Look in ! `/usr/include/errno.h' to find the value of `EDOM' on your system. ! If you do not define `TARGET_EDOM', then compiled code reports ! domain errors by calling the library function and letting it ! report the error. If mathematical functions on your system use ! `matherr' when there is an error, then you should leave ! `TARGET_EDOM' undefined so that `matherr' is used normally. -- Macro: GEN_ERRNO_RTX Define this macro as a C expression to create an rtl expression ! that refers to the global "variable" `errno'. (On certain systems, ! `errno' may not actually be a variable.) If you don't define this macro, a reasonable default is used. -- Target Hook: bool TARGET_LIBC_HAS_FUNCTION (enum function_class *************** Here is an explanation of implicit calls *** 32682,32690 **** Set this macro to 1 to use the "NeXT" Objective-C message sending conventions by default. This calling convention involves passing the object, the selector and the method arguments all at once to ! the method-lookup library function. This is the usual setting when ! targeting Darwin/Mac OS X systems, which have the NeXT runtime ! installed. If the macro is set to 0, the "GNU" Objective-C message sending convention will be used by default. This convention passes just --- 33101,33109 ---- Set this macro to 1 to use the "NeXT" Objective-C message sending conventions by default. This calling convention involves passing the object, the selector and the method arguments all at once to ! the method-lookup library function. This is the usual setting ! when targeting Darwin/Mac OS X systems, which have the NeXT ! runtime installed. If the macro is set to 0, the "GNU" Objective-C message sending convention will be used by default. This convention passes just *************** This is about addressing modes. *** 32725,32746 **** -- Macro: CONSTANT_ADDRESS_P (X) A C expression that is 1 if the RTX X is a constant which is a valid address. On most machines the default definition of ! '(CONSTANT_P (X) && GET_CODE (X) != CONST_DOUBLE)' is acceptable, but a few machines are more restrictive as to which constant addresses are supported. -- Macro: CONSTANT_P (X) ! 'CONSTANT_P', which is defined by target-independent code, accepts integer-values expressions whose values are not explicitly known, ! such as 'symbol_ref', 'label_ref', and 'high' expressions and ! 'const' arithmetic expressions, in addition to 'const_int' and ! 'const_double' expressions. -- Macro: MAX_REGS_PER_ADDRESS A number, the maximum number of registers that can appear in a ! valid memory address. Note that it is up to you to specify a value ! equal to the maximum number that 'TARGET_LEGITIMATE_ADDRESS_P' ! would ever accept. -- Target Hook: bool TARGET_LEGITIMATE_ADDRESS_P (machine_mode MODE, rtx X, bool STRICT) --- 33144,33165 ---- -- Macro: CONSTANT_ADDRESS_P (X) A C expression that is 1 if the RTX X is a constant which is a valid address. On most machines the default definition of ! `(CONSTANT_P (X) && GET_CODE (X) != CONST_DOUBLE)' is acceptable, but a few machines are more restrictive as to which constant addresses are supported. -- Macro: CONSTANT_P (X) ! `CONSTANT_P', which is defined by target-independent code, accepts integer-values expressions whose values are not explicitly known, ! such as `symbol_ref', `label_ref', and `high' expressions and ! `const' arithmetic expressions, in addition to `const_int' and ! `const_double' expressions. -- Macro: MAX_REGS_PER_ADDRESS A number, the maximum number of registers that can appear in a ! valid memory address. Note that it is up to you to specify a ! value equal to the maximum number that ! `TARGET_LEGITIMATE_ADDRESS_P' would ever accept. -- Target Hook: bool TARGET_LEGITIMATE_ADDRESS_P (machine_mode MODE, rtx X, bool STRICT) *************** This is about addressing modes. *** 32754,32800 **** The strict variant is used in the reload pass. It must be defined so that any pseudo-register that has not been allocated a hard register is considered a memory reference. This is because in ! contexts where some kind of register is required, a pseudo-register ! with no hard register must be rejected. For non-hard registers, ! the strict variant should look up the 'reg_renumber' array; it ! should then proceed using the hard register number in the array, or ! treat the pseudo as a memory reference if the array holds '-1'. ! The non-strict variant is used in other passes. It must be defined ! to accept all pseudo-registers in every context where some kind of ! register is required. ! Normally, constant addresses which are the sum of a 'symbol_ref' ! and an integer are stored inside a 'const' RTX to mark them as constant. Therefore, there is no need to recognize such sums specifically as legitimate addresses. Normally you would simply ! recognize any 'const' as legitimate. ! Usually 'PRINT_OPERAND_ADDRESS' is not prepared to handle constant ! sums that are not marked with 'const'. It assumes that a naked ! 'plus' indicates indexing. If so, then you _must_ reject such ! naked constant sums as illegitimate addresses, so that none of them ! will be given to 'PRINT_OPERAND_ADDRESS'. On some machines, whether a symbolic address is legitimate depends on the section that the address refers to. On these machines, ! define the target hook 'TARGET_ENCODE_SECTION_INFO' to store the ! information into the 'symbol_ref', and then check for it here. ! When you see a 'const', you will have to look inside it to find the ! 'symbol_ref' in order to determine the section. *Note Assembler Format::. Some ports are still using a deprecated legacy substitute for this ! hook, the 'GO_IF_LEGITIMATE_ADDRESS' macro. This macro has this syntax: #define GO_IF_LEGITIMATE_ADDRESS (MODE, X, LABEL) ! and should 'goto LABEL' if the address X is a valid address on the target machine for a memory operand of mode MODE. Compiler source files that want to use the strict variant of this ! macro define the macro 'REG_OK_STRICT'. You should use an '#ifdef REG_OK_STRICT' conditional to define the strict variant in that case and the non-strict variant otherwise. --- 33173,33220 ---- The strict variant is used in the reload pass. It must be defined so that any pseudo-register that has not been allocated a hard register is considered a memory reference. This is because in ! contexts where some kind of register is required, a ! pseudo-register with no hard register must be rejected. For ! non-hard registers, the strict variant should look up the ! `reg_renumber' array; it should then proceed using the hard ! register number in the array, or treat the pseudo as a memory ! reference if the array holds `-1'. ! The non-strict variant is used in other passes. It must be ! defined to accept all pseudo-registers in every context where some ! kind of register is required. ! Normally, constant addresses which are the sum of a `symbol_ref' ! and an integer are stored inside a `const' RTX to mark them as constant. Therefore, there is no need to recognize such sums specifically as legitimate addresses. Normally you would simply ! recognize any `const' as legitimate. ! Usually `PRINT_OPERAND_ADDRESS' is not prepared to handle constant ! sums that are not marked with `const'. It assumes that a naked ! `plus' indicates indexing. If so, then you _must_ reject such ! naked constant sums as illegitimate addresses, so that none of ! them will be given to `PRINT_OPERAND_ADDRESS'. On some machines, whether a symbolic address is legitimate depends on the section that the address refers to. On these machines, ! define the target hook `TARGET_ENCODE_SECTION_INFO' to store the ! information into the `symbol_ref', and then check for it here. ! When you see a `const', you will have to look inside it to find the ! `symbol_ref' in order to determine the section. *Note Assembler Format::. Some ports are still using a deprecated legacy substitute for this ! hook, the `GO_IF_LEGITIMATE_ADDRESS' macro. This macro has this syntax: #define GO_IF_LEGITIMATE_ADDRESS (MODE, X, LABEL) ! and should `goto LABEL' if the address X is a valid address on the target machine for a memory operand of mode MODE. Compiler source files that want to use the strict variant of this ! macro define the macro `REG_OK_STRICT'. You should use an `#ifdef REG_OK_STRICT' conditional to define the strict variant in that case and the non-strict variant otherwise. *************** This is about addressing modes. *** 32802,32821 **** files that are recompiled when changes are made. -- Macro: TARGET_MEM_CONSTRAINT ! A single character to be used instead of the default ''m'' character for general memory addresses. This defines the constraint letter which matches the memory addresses accepted by ! 'TARGET_LEGITIMATE_ADDRESS_P'. Define this macro if you want to support new address formats in your back end without changing the ! semantics of the ''m'' constraint. This is necessary in order to preserve functionality of inline assembly constructs using the ! ''m'' constraint. -- Macro: FIND_BASE_TERM (X) A C expression to determine the base term of address X, or to ! provide a simplified version of X from which 'alias.c' can easily find the base term. This macro is used in only two places: ! 'find_base_value' and 'find_base_term' in 'alias.c'. It is always safe for this macro to not be defined. It exists so that alias analysis can understand machine-dependent addresses. --- 33222,33241 ---- files that are recompiled when changes are made. -- Macro: TARGET_MEM_CONSTRAINT ! A single character to be used instead of the default `'m'' character for general memory addresses. This defines the constraint letter which matches the memory addresses accepted by ! `TARGET_LEGITIMATE_ADDRESS_P'. Define this macro if you want to support new address formats in your back end without changing the ! semantics of the `'m'' constraint. This is necessary in order to preserve functionality of inline assembly constructs using the ! `'m'' constraint. -- Macro: FIND_BASE_TERM (X) A C expression to determine the base term of address X, or to ! provide a simplified version of X from which `alias.c' can easily find the base term. This macro is used in only two places: ! `find_base_value' and `find_base_term' in `alias.c'. It is always safe for this macro to not be defined. It exists so that alias analysis can understand machine-dependent addresses. *************** This is about addressing modes. *** 32828,32901 **** This hook is given an invalid memory address X for an operand of mode MODE and should try to return a valid memory address. ! X will always be the result of a call to 'break_out_memory_refs', and OLDX will be the operand that was given to that function to produce X. ! The code of the hook should not alter the substructure of X. If it ! transforms X into a more legitimate form, it should return the new ! X. It is not necessary for this hook to come up with a legitimate ! address, with the exception of native TLS addresses (*note Emulated ! TLS::). The compiler has standard ways of doing so in all cases. ! In fact, if the target supports only emulated TLS, it is safe to ! omit this hook or make it return X if it cannot find a valid way to ! legitimize the address. But often a machine-dependent strategy can ! generate better code. -- Macro: LEGITIMIZE_RELOAD_ADDRESS (X, MODE, OPNUM, TYPE, IND_LEVELS, WIN) A C compound statement that attempts to replace X, which is an address that needs reloading, with a valid memory address for an ! operand of mode MODE. WIN will be a C statement label elsewhere in ! the code. It is not necessary to define this macro, but it might ! be useful for performance reasons. For example, on the i386, it is sometimes possible to use a single reload register instead of two by reloading a sum of two pseudo registers into a register. On the other hand, for number of RISC processors offsets are limited so that often an intermediate ! address needs to be generated in order to address a stack slot. By ! defining 'LEGITIMIZE_RELOAD_ADDRESS' appropriately, the intermediate addresses generated for adjacent some stack slots can be made identical, and thus be shared. ! _Note_: This macro should be used with caution. It is necessary to ! know something of how reload works in order to effectively use ! this, and it is quite easy to produce macros that build in too much ! knowledge of reload internals. _Note_: This macro must be able to reload an address created by a previous invocation of this macro. If it fails to handle such addresses then the compiler may generate incorrect code or abort. ! The macro definition should use 'push_reload' to indicate parts that need reloading; OPNUM, TYPE and IND_LEVELS are usually ! suitable to be passed unaltered to 'push_reload'. The code generated by this macro must not alter the substructure of X. If it transforms X into a more legitimate form, it should assign X (which will always be a C variable) a new value. This also applies to parts that you change indirectly by calling ! 'push_reload'. ! The macro definition may use 'strict_memory_address_p' to test if the address has become legitimate. If you want to change only a part of X, one standard way of doing ! this is to use 'copy_rtx'. Note, however, that it unshares only a single level of rtl. Thus, if the part to be changed is not at the top level, you'll need to replace first the top level. It is not ! necessary for this macro to come up with a legitimate address; but ! often a machine-dependent strategy can generate better code. -- Target Hook: bool TARGET_MODE_DEPENDENT_ADDRESS_P (const_rtx ADDR, addr_space_t ADDRSPACE) ! This hook returns 'true' if memory address ADDR in address space ! ADDRSPACE can have different meanings depending on the machine mode ! of the memory reference it is used for or if the address is valid ! for some modes but not others. Autoincrement and autodecrement addresses typically have mode-dependent effects because the amount of the increment or --- 33248,33321 ---- This hook is given an invalid memory address X for an operand of mode MODE and should try to return a valid memory address. ! X will always be the result of a call to `break_out_memory_refs', and OLDX will be the operand that was given to that function to produce X. ! The code of the hook should not alter the substructure of X. If ! it transforms X into a more legitimate form, it should return the ! new X. It is not necessary for this hook to come up with a legitimate ! address, with the exception of native TLS addresses (*note ! Emulated TLS::). The compiler has standard ways of doing so in ! all cases. In fact, if the target supports only emulated TLS, it ! is safe to omit this hook or make it return X if it cannot find a ! valid way to legitimize the address. But often a machine-dependent ! strategy can generate better code. -- Macro: LEGITIMIZE_RELOAD_ADDRESS (X, MODE, OPNUM, TYPE, IND_LEVELS, WIN) A C compound statement that attempts to replace X, which is an address that needs reloading, with a valid memory address for an ! operand of mode MODE. WIN will be a C statement label elsewhere ! in the code. It is not necessary to define this macro, but it ! might be useful for performance reasons. For example, on the i386, it is sometimes possible to use a single reload register instead of two by reloading a sum of two pseudo registers into a register. On the other hand, for number of RISC processors offsets are limited so that often an intermediate ! address needs to be generated in order to address a stack slot. ! By defining `LEGITIMIZE_RELOAD_ADDRESS' appropriately, the intermediate addresses generated for adjacent some stack slots can be made identical, and thus be shared. ! _Note_: This macro should be used with caution. It is necessary ! to know something of how reload works in order to effectively use ! this, and it is quite easy to produce macros that build in too ! much knowledge of reload internals. _Note_: This macro must be able to reload an address created by a previous invocation of this macro. If it fails to handle such addresses then the compiler may generate incorrect code or abort. ! The macro definition should use `push_reload' to indicate parts that need reloading; OPNUM, TYPE and IND_LEVELS are usually ! suitable to be passed unaltered to `push_reload'. The code generated by this macro must not alter the substructure of X. If it transforms X into a more legitimate form, it should assign X (which will always be a C variable) a new value. This also applies to parts that you change indirectly by calling ! `push_reload'. ! The macro definition may use `strict_memory_address_p' to test if the address has become legitimate. If you want to change only a part of X, one standard way of doing ! this is to use `copy_rtx'. Note, however, that it unshares only a single level of rtl. Thus, if the part to be changed is not at the top level, you'll need to replace first the top level. It is not ! necessary for this macro to come up with a legitimate address; ! but often a machine-dependent strategy can generate better code. -- Target Hook: bool TARGET_MODE_DEPENDENT_ADDRESS_P (const_rtx ADDR, addr_space_t ADDRSPACE) ! This hook returns `true' if memory address ADDR in address space ! ADDRSPACE can have different meanings depending on the machine ! mode of the memory reference it is used for or if the address is ! valid for some modes but not others. Autoincrement and autodecrement addresses typically have mode-dependent effects because the amount of the increment or *************** This is about addressing modes. *** 32905,32928 **** You may assume that ADDR is a valid address for the machine. ! The default version of this hook returns 'false'. -- Target Hook: bool TARGET_LEGITIMATE_CONSTANT_P (machine_mode MODE, rtx X) This hook returns true if X is a legitimate constant for a MODE-mode immediate operand on the target machine. You can assume ! that X satisfies 'CONSTANT_P', so you need not check this. The default definition returns true. -- Target Hook: rtx TARGET_DELEGITIMIZE_ADDRESS (rtx X) This hook is used to undo the possibly obfuscating effects of the ! 'LEGITIMIZE_ADDRESS' and 'LEGITIMIZE_RELOAD_ADDRESS' target macros. ! Some backend implementations of these macros wrap symbol references ! inside an 'UNSPEC' rtx to represent PIC or similar addressing ! modes. This target hook allows GCC's optimizers to understand the ! semantics of these opaque 'UNSPEC's by converting them back into ! their original form. -- Target Hook: bool TARGET_CONST_NOT_OK_FOR_DEBUG_P (rtx X) This hook should return true if X should not be emitted into debug --- 33325,33348 ---- You may assume that ADDR is a valid address for the machine. ! The default version of this hook returns `false'. -- Target Hook: bool TARGET_LEGITIMATE_CONSTANT_P (machine_mode MODE, rtx X) This hook returns true if X is a legitimate constant for a MODE-mode immediate operand on the target machine. You can assume ! that X satisfies `CONSTANT_P', so you need not check this. The default definition returns true. -- Target Hook: rtx TARGET_DELEGITIMIZE_ADDRESS (rtx X) This hook is used to undo the possibly obfuscating effects of the ! `LEGITIMIZE_ADDRESS' and `LEGITIMIZE_RELOAD_ADDRESS' target ! macros. Some backend implementations of these macros wrap symbol ! references inside an `UNSPEC' rtx to represent PIC or similar ! addressing modes. This target hook allows GCC's optimizers to ! understand the semantics of these opaque `UNSPEC's by converting ! them back into their original form. -- Target Hook: bool TARGET_CONST_NOT_OK_FOR_DEBUG_P (rtx X) This hook should return true if X should not be emitted into debug *************** This is about addressing modes. *** 32945,32964 **** -- Target Hook: bool TARGET_USE_BLOCKS_FOR_CONSTANT_P (machine_mode MODE, const_rtx X) This hook should return true if pool entries for constant X can be ! placed in an 'object_block' structure. MODE is the mode of X. The default version returns false for all constants. -- Target Hook: bool TARGET_USE_BLOCKS_FOR_DECL_P (const_tree DECL) This hook should return true if pool entries for DECL should be ! placed in an 'object_block' structure. The default version returns true for all decls. -- Target Hook: tree TARGET_BUILTIN_RECIPROCAL (tree FNDECL) This hook should return the DECL of a function that implements the reciprocal of the machine-specific builtin function FNDECL, or ! 'NULL_TREE' if such a function is not available. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD (void) This hook should return the DECL of a function F that given an --- 33365,33384 ---- -- Target Hook: bool TARGET_USE_BLOCKS_FOR_CONSTANT_P (machine_mode MODE, const_rtx X) This hook should return true if pool entries for constant X can be ! placed in an `object_block' structure. MODE is the mode of X. The default version returns false for all constants. -- Target Hook: bool TARGET_USE_BLOCKS_FOR_DECL_P (const_tree DECL) This hook should return true if pool entries for DECL should be ! placed in an `object_block' structure. The default version returns true for all decls. -- Target Hook: tree TARGET_BUILTIN_RECIPROCAL (tree FNDECL) This hook should return the DECL of a function that implements the reciprocal of the machine-specific builtin function FNDECL, or ! `NULL_TREE' if such a function is not available. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD (void) This hook should return the DECL of a function F that given an *************** This is about addressing modes. *** 32968,32989 **** The autovectorizer, when vectorizing a load operation from an address ADDR that may be unaligned, will generate two vector loads ! from the two aligned addresses around ADDR. It then generates a ! 'REALIGN_LOAD' operation to extract the relevant data from the two ! loaded vectors. The first two arguments to 'REALIGN_LOAD', V1 and V2, are the two vectors, each of size VS, and the third argument, ! OFF, defines how the data will be extracted from these two vectors: ! if OFF is 0, then the returned vector is V2; otherwise, the ! returned vector is composed from the last VS-OFF elements of V1 ! concatenated to the first OFF elements of V2. ! If this hook is defined, the autovectorizer will generate a call to ! F (using the DECL tree that this hook returns) and will use the ! return value of F as the argument OFF to 'REALIGN_LOAD'. Therefore, the mask M returned by F should comply with the ! semantics expected by 'REALIGN_LOAD' described above. If this hook ! is not defined, then ADDR will be used as the argument OFF to ! 'REALIGN_LOAD', in which case the low log2(VS) - 1 bits of ADDR will be considered. -- Target Hook: int TARGET_VECTORIZE_BUILTIN_VECTORIZATION_COST (enum --- 33388,33409 ---- The autovectorizer, when vectorizing a load operation from an address ADDR that may be unaligned, will generate two vector loads ! from the two aligned addresses around ADDR. It then generates a ! `REALIGN_LOAD' operation to extract the relevant data from the two ! loaded vectors. The first two arguments to `REALIGN_LOAD', V1 and V2, are the two vectors, each of size VS, and the third argument, ! OFF, defines how the data will be extracted from these two ! vectors: if OFF is 0, then the returned vector is V2; otherwise, ! the returned vector is composed from the last VS-OFF elements of ! V1 concatenated to the first OFF elements of V2. ! If this hook is defined, the autovectorizer will generate a call ! to F (using the DECL tree that this hook returns) and will use the ! return value of F as the argument OFF to `REALIGN_LOAD'. Therefore, the mask M returned by F should comply with the ! semantics expected by `REALIGN_LOAD' described above. If this ! hook is not defined, then ADDR will be used as the argument OFF to ! `REALIGN_LOAD', in which case the low log2(VS) - 1 bits of ADDR will be considered. -- Target Hook: int TARGET_VECTORIZE_BUILTIN_VECTORIZATION_COST (enum *************** This is about addressing modes. *** 32995,33030 **** -- Target Hook: bool TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE (const_tree TYPE, bool IS_PACKED) Return true if vector alignment is reachable (by peeling N ! iterations) for the given type. -- Target Hook: bool TARGET_VECTORIZE_VEC_PERM_CONST_OK (machine_mode, const unsigned char *SEL) ! Return true if a vector created for 'vec_perm_const' is valid. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_CONVERSION (unsigned CODE, tree DEST_TYPE, tree SRC_TYPE) This hook should return the DECL of a function that implements conversion of the input vector of type SRC_TYPE to type DEST_TYPE. ! The value of CODE is one of the enumerators in 'enum tree_code' and specifies how the conversion is to be applied (truncation, rounding, etc.). If this hook is defined, the autovectorizer will use the ! 'TARGET_VECTORIZE_BUILTIN_CONVERSION' target hook when vectorizing ! conversion. Otherwise, it will return 'NULL_TREE'. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION (unsigned CODE, tree VEC_TYPE_OUT, tree VEC_TYPE_IN) This hook should return the decl of a function that implements the ! vectorized variant of the function with the 'combined_fn' code CODE ! or 'NULL_TREE' if such a function is not available. The return ! type of the vectorized function shall be of vector type VEC_TYPE_OUT and the argument types should be VEC_TYPE_IN. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_MD_VECTORIZED_FUNCTION (tree FNDECL, tree VEC_TYPE_OUT, tree VEC_TYPE_IN) This hook should return the decl of a function that implements the ! vectorized variant of target built-in function 'fndecl'. The return type of the vectorized function shall be of vector type VEC_TYPE_OUT and the argument types should be VEC_TYPE_IN. --- 33415,33451 ---- -- Target Hook: bool TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE (const_tree TYPE, bool IS_PACKED) Return true if vector alignment is reachable (by peeling N ! iterations) for the given scalar type TYPE. IS_PACKED is false if ! the scalar access using TYPE is known to be naturally aligned. -- Target Hook: bool TARGET_VECTORIZE_VEC_PERM_CONST_OK (machine_mode, const unsigned char *SEL) ! Return true if a vector created for `vec_perm_const' is valid. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_CONVERSION (unsigned CODE, tree DEST_TYPE, tree SRC_TYPE) This hook should return the DECL of a function that implements conversion of the input vector of type SRC_TYPE to type DEST_TYPE. ! The value of CODE is one of the enumerators in `enum tree_code' and specifies how the conversion is to be applied (truncation, rounding, etc.). If this hook is defined, the autovectorizer will use the ! `TARGET_VECTORIZE_BUILTIN_CONVERSION' target hook when vectorizing ! conversion. Otherwise, it will return `NULL_TREE'. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION (unsigned CODE, tree VEC_TYPE_OUT, tree VEC_TYPE_IN) This hook should return the decl of a function that implements the ! vectorized variant of the function with the `combined_fn' code ! CODE or `NULL_TREE' if such a function is not available. The ! return type of the vectorized function shall be of vector type VEC_TYPE_OUT and the argument types should be VEC_TYPE_IN. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_MD_VECTORIZED_FUNCTION (tree FNDECL, tree VEC_TYPE_OUT, tree VEC_TYPE_IN) This hook should return the decl of a function that implements the ! vectorized variant of target built-in function `fndecl'. The return type of the vectorized function shall be of vector type VEC_TYPE_OUT and the argument types should be VEC_TYPE_IN. *************** This is about addressing modes. *** 33041,33055 **** -- Target Hook: machine_mode TARGET_VECTORIZE_PREFERRED_SIMD_MODE (machine_mode MODE) This hook should return the preferred mode for vectorizing scalar ! mode MODE. The default is equal to 'word_mode', because the vectorizer can do some transformations even in absence of specialized SIMD hardware. -- Target Hook: unsigned int ! TARGET_VECTORIZE_AUTOVECTORIZE_VECTOR_SIZES (void) This hook should return a mask of sizes that should be iterated over after trying to autovectorize using the vector size derived ! from the mode returned by 'TARGET_VECTORIZE_PREFERRED_SIMD_MODE'. The default is zero which means to not iterate over other vector sizes. --- 33462,33476 ---- -- Target Hook: machine_mode TARGET_VECTORIZE_PREFERRED_SIMD_MODE (machine_mode MODE) This hook should return the preferred mode for vectorizing scalar ! mode MODE. The default is equal to `word_mode', because the vectorizer can do some transformations even in absence of specialized SIMD hardware. -- Target Hook: unsigned int ! TARGET_VECTORIZE_AUTOVECTORIZE_VECTOR_SIZES (void) This hook should return a mask of sizes that should be iterated over after trying to autovectorize using the vector size derived ! from the mode returned by `TARGET_VECTORIZE_PREFERRED_SIMD_MODE'. The default is zero which means to not iterate over other vector sizes. *************** This is about addressing modes. *** 33064,33109 **** This hook should initialize target-specific data structures in preparation for modeling the costs of vectorizing a loop or basic block. The default allocates three unsigned integers for ! accumulating costs for the prologue, body, and epilogue of the loop ! or basic block. If LOOP_INFO is non-NULL, it identifies the loop ! being vectorized; otherwise a single block is being vectorized. -- Target Hook: unsigned TARGET_VECTORIZE_ADD_STMT_COST (void *DATA, ! int COUNT, enum vect_cost_for_stmt KIND, struct _stmt_vec_info ! *STMT_INFO, int MISALIGN, enum vect_cost_model_location WHERE) This hook should update the target-specific DATA in response to adding COUNT copies of the given KIND of statement to a loop or basic block. The default adds the builtin vectorizer cost for the ! copies of the statement to the accumulator specified by WHERE, (the ! prologue, body, or epilogue) and returns the amount added. The ! return value should be viewed as a tentative cost that may later be ! revised. ! -- Target Hook: void TARGET_VECTORIZE_FINISH_COST (void *DATA, unsigned ! *PROLOGUE_COST, unsigned *BODY_COST, unsigned *EPILOGUE_COST) ! This hook should complete calculations of the cost of vectorizing a ! loop or basic block based on DATA, and return the prologue, body, ! and epilogue costs as unsigned integers. The default returns the ! value of the three accumulators. -- Target Hook: void TARGET_VECTORIZE_DESTROY_COST_DATA (void *DATA) This hook should release DATA and any related data structures ! allocated by TARGET_VECTORIZE_INIT_COST. The default releases the accumulator. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_GATHER (const_tree MEM_VECTYPE, const_tree INDEX_TYPE, int SCALE) Target builtin that implements vector gather operation. ! MEM_VECTYPE is the vector type of the load and INDEX_TYPE is scalar ! type of the index, scaled by SCALE. The default is 'NULL_TREE' ! which means to not vectorize gather loads. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_SCATTER (const_tree VECTYPE, const_tree INDEX_TYPE, int SCALE) Target builtin that implements vector scatter operation. VECTYPE is the vector type of the store and INDEX_TYPE is scalar type of ! the index, scaled by SCALE. The default is 'NULL_TREE' which means ! to not vectorize scatter stores. -- Target Hook: int TARGET_SIMD_CLONE_COMPUTE_VECSIZE_AND_SIMDLEN (struct cgraph_node *, struct cgraph_simd_clone *, TREE, INT) --- 33485,33533 ---- This hook should initialize target-specific data structures in preparation for modeling the costs of vectorizing a loop or basic block. The default allocates three unsigned integers for ! accumulating costs for the prologue, body, and epilogue of the ! loop or basic block. If LOOP_INFO is non-NULL, it identifies the ! loop being vectorized; otherwise a single block is being ! vectorized. -- Target Hook: unsigned TARGET_VECTORIZE_ADD_STMT_COST (void *DATA, ! int COUNT, enum vect_cost_for_stmt KIND, struct ! _stmt_vec_info *STMT_INFO, int MISALIGN, enum ! vect_cost_model_location WHERE) This hook should update the target-specific DATA in response to adding COUNT copies of the given KIND of statement to a loop or basic block. The default adds the builtin vectorizer cost for the ! copies of the statement to the accumulator specified by WHERE, ! (the prologue, body, or epilogue) and returns the amount added. ! The return value should be viewed as a tentative cost that may ! later be revised. ! -- Target Hook: void TARGET_VECTORIZE_FINISH_COST (void *DATA, ! unsigned *PROLOGUE_COST, unsigned *BODY_COST, unsigned ! *EPILOGUE_COST) ! This hook should complete calculations of the cost of vectorizing ! a loop or basic block based on DATA, and return the prologue, ! body, and epilogue costs as unsigned integers. The default ! returns the value of the three accumulators. -- Target Hook: void TARGET_VECTORIZE_DESTROY_COST_DATA (void *DATA) This hook should release DATA and any related data structures ! allocated by TARGET_VECTORIZE_INIT_COST. The default releases the accumulator. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_GATHER (const_tree MEM_VECTYPE, const_tree INDEX_TYPE, int SCALE) Target builtin that implements vector gather operation. ! MEM_VECTYPE is the vector type of the load and INDEX_TYPE is ! scalar type of the index, scaled by SCALE. The default is ! `NULL_TREE' which means to not vectorize gather loads. -- Target Hook: tree TARGET_VECTORIZE_BUILTIN_SCATTER (const_tree VECTYPE, const_tree INDEX_TYPE, int SCALE) Target builtin that implements vector scatter operation. VECTYPE is the vector type of the store and INDEX_TYPE is scalar type of ! the index, scaled by SCALE. The default is `NULL_TREE' which ! means to not vectorize scatter stores. -- Target Hook: int TARGET_SIMD_CLONE_COMPUTE_VECSIZE_AND_SIMDLEN (struct cgraph_node *, struct cgraph_simd_clone *, TREE, INT) *************** This is about addressing modes. *** 33114,33120 **** variants that should be emitted. -- Target Hook: void TARGET_SIMD_CLONE_ADJUST (struct cgraph_node *) ! This hook should add implicit 'attribute(target("..."))' attribute to SIMD clone NODE if needed. -- Target Hook: int TARGET_SIMD_CLONE_USABLE (struct cgraph_node *) --- 33538,33544 ---- variants that should be emitted. -- Target Hook: void TARGET_SIMD_CLONE_ADJUST (struct cgraph_node *) ! This hook should add implicit `attribute(target("..."))' attribute to SIMD clone NODE if needed. -- Target Hook: int TARGET_SIMD_CLONE_USABLE (struct cgraph_node *) *************** This is about addressing modes. *** 33128,33140 **** This hook should check the launch dimensions provided for an OpenACC compute region, or routine. Defaulted values are represented as -1 and non-constant values as 0. The FN_LEVEL is ! negative for the function corresponding to the compute region. For ! a routine is is the outermost level at which partitioned execution ! may be spawned. The hook should verify non-default values. If ! DECL is NULL, global defaults are being validated and unspecified ! defaults should be filled in. Diagnostics should be issued as ! appropriate. Return true, if changes have been made. You must ! override this hook to provide dimensions larger than 1. -- Target Hook: int TARGET_GOACC_DIM_LIMIT (int AXIS) This hook should return the maximum size of a particular dimension, --- 33552,33564 ---- This hook should check the launch dimensions provided for an OpenACC compute region, or routine. Defaulted values are represented as -1 and non-constant values as 0. The FN_LEVEL is ! negative for the function corresponding to the compute region. ! For a routine is is the outermost level at which partitioned ! execution may be spawned. The hook should verify non-default ! values. If DECL is NULL, global defaults are being validated and ! unspecified defaults should be filled in. Diagnostics should be ! issued as appropriate. Return true, if changes have been made. ! You must override this hook to provide dimensions larger than 1. -- Target Hook: int TARGET_GOACC_DIM_LIMIT (int AXIS) This hook should return the maximum size of a particular dimension, *************** example, if we have: *** 33171,33178 **** static int a, b, c; int foo (void) { return a + b + c; } ! the code for 'foo' will usually calculate three separate symbolic ! addresses: those of 'a', 'b' and 'c'. On some targets, it would be better to calculate just one symbolic address and access the three variables relative to it. The equivalent pseudocode would be something like: --- 33595,33602 ---- static int a, b, c; int foo (void) { return a + b + c; } ! the code for `foo' will usually calculate three separate symbolic ! addresses: those of `a', `b' and `c'. On some targets, it would be better to calculate just one symbolic address and access the three variables relative to it. The equivalent pseudocode would be something like: *************** like: *** 33183,33195 **** return xr[&a - &x] + xr[&b - &x] + xr[&c - &x]; } ! (which isn't valid C). We refer to shared addresses like 'x' as ! "section anchors". Their use is controlled by '-fsection-anchors'. The hooks below describe the target properties that GCC needs to know ! in order to make effective use of section anchors. It won't use section ! anchors at all unless either 'TARGET_MIN_ANCHOR_OFFSET' or ! 'TARGET_MAX_ANCHOR_OFFSET' is set to a nonzero value. -- Target Hook: HOST_WIDE_INT TARGET_MIN_ANCHOR_OFFSET The minimum offset that should be applied to a section anchor. On --- 33607,33619 ---- return xr[&a - &x] + xr[&b - &x] + xr[&c - &x]; } ! (which isn't valid C). We refer to shared addresses like `x' as ! "section anchors". Their use is controlled by `-fsection-anchors'. The hooks below describe the target properties that GCC needs to know ! in order to make effective use of section anchors. It won't use ! section anchors at all unless either `TARGET_MIN_ANCHOR_OFFSET' or ! `TARGET_MAX_ANCHOR_OFFSET' is set to a nonzero value. -- Target Hook: HOST_WIDE_INT TARGET_MIN_ANCHOR_OFFSET The minimum offset that should be applied to a section anchor. On *************** anchors at all unless either 'TARGET_MIN *** 33198,33224 **** every mode. The default value is 0. -- Target Hook: HOST_WIDE_INT TARGET_MAX_ANCHOR_OFFSET ! Like 'TARGET_MIN_ANCHOR_OFFSET', but the maximum (inclusive) offset ! that should be applied to section anchors. The default value is 0. -- Target Hook: void TARGET_ASM_OUTPUT_ANCHOR (rtx X) Write the assembly code to define section anchor X, which is a ! 'SYMBOL_REF' for which 'SYMBOL_REF_ANCHOR_P (X)' is true. The hook ! is called with the assembly output position set to the beginning of ! 'SYMBOL_REF_BLOCK (X)'. ! If 'ASM_OUTPUT_DEF' is available, the hook's default definition ! uses it to define the symbol as '. + SYMBOL_REF_BLOCK_OFFSET (X)'. ! If 'ASM_OUTPUT_DEF' is not available, the hook's default definition ! is 'NULL', which disables the use of section anchors altogether. -- Target Hook: bool TARGET_USE_ANCHORS_FOR_SYMBOL_P (const_rtx X) Return true if GCC should attempt to use anchors to access ! 'SYMBOL_REF' X. You can assume 'SYMBOL_REF_HAS_BLOCK_INFO_P (X)' ! and '!SYMBOL_REF_ANCHOR_P (X)'. ! The default version is correct for most targets, but you might need ! to intercept this hook to handle things like target-specific attributes or target-specific sections.  --- 33622,33649 ---- every mode. The default value is 0. -- Target Hook: HOST_WIDE_INT TARGET_MAX_ANCHOR_OFFSET ! Like `TARGET_MIN_ANCHOR_OFFSET', but the maximum (inclusive) ! offset that should be applied to section anchors. The default ! value is 0. -- Target Hook: void TARGET_ASM_OUTPUT_ANCHOR (rtx X) Write the assembly code to define section anchor X, which is a ! `SYMBOL_REF' for which `SYMBOL_REF_ANCHOR_P (X)' is true. The ! hook is called with the assembly output position set to the ! beginning of `SYMBOL_REF_BLOCK (X)'. ! If `ASM_OUTPUT_DEF' is available, the hook's default definition ! uses it to define the symbol as `. + SYMBOL_REF_BLOCK_OFFSET (X)'. ! If `ASM_OUTPUT_DEF' is not available, the hook's default definition ! is `NULL', which disables the use of section anchors altogether. -- Target Hook: bool TARGET_USE_ANCHORS_FOR_SYMBOL_P (const_rtx X) Return true if GCC should attempt to use anchors to access ! `SYMBOL_REF' X. You can assume `SYMBOL_REF_HAS_BLOCK_INFO_P (X)' ! and `!SYMBOL_REF_ANCHOR_P (X)'. ! The default version is correct for most targets, but you might ! need to intercept this hook to handle things like target-specific attributes or target-specific sections.  *************** File: gccint.info, Node: Condition Code *** 33230,33247 **** The macros in this section can be split in two families, according to the two ways of representing condition codes in GCC. ! The first representation is the so called '(cc0)' representation (*note ! Jump Patterns::), where all instructions can have an implicit clobber of ! the condition codes. The second is the condition code register ! representation, which provides better schedulability for architectures ! that do have a condition code register, but on which most instructions ! do not affect it. The latter category includes most RISC machines. The implicit clobbering poses a strong restriction on the placement of the definition and use of the condition code. In the past the definition and use were always adjacent. However, recent changes to support trapping arithmatic may result in the definition and user being ! in different blocks. Thus, there may be a 'NOTE_INSN_BASIC_BLOCK' between them. Additionally, the definition may be the source of exception handling edges. --- 33655,33673 ---- The macros in this section can be split in two families, according to the two ways of representing condition codes in GCC. ! The first representation is the so called `(cc0)' representation ! (*note Jump Patterns::), where all instructions can have an implicit ! clobber of the condition codes. The second is the condition code ! register representation, which provides better schedulability for ! architectures that do have a condition code register, but on which most ! instructions do not affect it. The latter category includes most RISC ! machines. The implicit clobbering poses a strong restriction on the placement of the definition and use of the condition code. In the past the definition and use were always adjacent. However, recent changes to support trapping arithmatic may result in the definition and user being ! in different blocks. Thus, there may be a `NOTE_INSN_BASIC_BLOCK' between them. Additionally, the definition may be the source of exception handling edges. *************** represent the condition code for new por *** 33257,33266 **** condition code register in the machine, use a hard register. If the condition code or comparison result can be placed in any general register, or if there are multiple condition registers, use a pseudo ! register. Registers used to store the condition code value will usually ! have a mode that is in class 'MODE_CC'. ! Alternatively, you can use 'BImode' if the comparison operator is specified already in the compare instruction. In this case, you are not interested in most macros in this section. --- 33683,33692 ---- condition code register in the machine, use a hard register. If the condition code or comparison result can be placed in any general register, or if there are multiple condition registers, use a pseudo ! register. Registers used to store the condition code value will ! usually have a mode that is in class `MODE_CC'. ! Alternatively, you can use `BImode' if the comparison operator is specified already in the compare instruction. In this case, you are not interested in most macros in this section. *************** interested in most macros in this sectio *** 33272,33281 ****  File: gccint.info, Node: CC0 Condition Codes, Next: MODE_CC Condition Codes, Up: Condition Code ! 17.15.1 Representation of condition codes using '(cc0)' ------------------------------------------------------- ! The file 'conditions.h' defines a variable 'cc_status' to describe how the condition code was computed (in case the interpretation of the condition code depends on the instruction that it was set by). This variable contains the RTL expressions on which the condition code is --- 33698,33707 ----  File: gccint.info, Node: CC0 Condition Codes, Next: MODE_CC Condition Codes, Up: Condition Code ! 17.15.1 Representation of condition codes using `(cc0)' ------------------------------------------------------- ! The file `conditions.h' defines a variable `cc_status' to describe how the condition code was computed (in case the interpretation of the condition code depends on the instruction that it was set by). This variable contains the RTL expressions on which the condition code is *************** currently based, and several standard fl *** 33283,33338 **** Sometimes additional machine-specific flags must be defined in the machine description header file. It can also add additional ! machine-specific information by defining 'CC_STATUS_MDEP'. -- Macro: CC_STATUS_MDEP ! C code for a data type which is used for declaring the 'mdep' ! component of 'cc_status'. It defaults to 'int'. ! This macro is not used on machines that do not use 'cc0'. -- Macro: CC_STATUS_MDEP_INIT ! A C expression to initialize the 'mdep' field to "empty". The default definition does nothing, since most machines don't use the field anyway. If you want to use the field, you should probably define this macro to initialize it. ! This macro is not used on machines that do not use 'cc0'. -- Macro: NOTICE_UPDATE_CC (EXP, INSN) ! A C compound statement to set the components of 'cc_status' appropriately for an insn INSN whose body is EXP. It is this macro's responsibility to recognize insns that set the condition code as a byproduct of other activity as well as those that ! explicitly set '(cc0)'. ! This macro is not used on machines that do not use 'cc0'. If there are insns that do not set the condition code but do alter other machine registers, this macro must check to see whether they invalidate the expressions that the condition code is recorded as reflecting. For example, on the 68000, insns that store in address registers do not set the condition code, which means that usually ! 'NOTICE_UPDATE_CC' can leave 'cc_status' unaltered for such insns. But suppose that the previous insn set the condition code based on ! location 'a4@(102)' and the current insn stores a new value in ! 'a4'. Although the condition code is not changed by this, it will ! no longer be true that it reflects the contents of 'a4@(102)'. ! Therefore, 'NOTICE_UPDATE_CC' must alter 'cc_status' in this case to say that nothing is known about the condition code value. ! The definition of 'NOTICE_UPDATE_CC' must be prepared to deal with the results of peephole optimization: insns whose patterns are ! 'parallel' RTXs containing various 'reg', 'mem' or constants which are just the operands. The RTL structure of these insns is not sufficient to indicate what the insns actually do. What ! 'NOTICE_UPDATE_CC' should do when it sees one is just to run ! 'CC_STATUS_INIT'. ! A possible definition of 'NOTICE_UPDATE_CC' is to call a function that looks at an attribute (*note Insn Attributes::) named, for ! example, 'cc'. This avoids having detailed information about ! patterns in two places, the 'md' file and in 'NOTICE_UPDATE_CC'.  File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes, Up: Condition Code --- 33709,33764 ---- Sometimes additional machine-specific flags must be defined in the machine description header file. It can also add additional ! machine-specific information by defining `CC_STATUS_MDEP'. -- Macro: CC_STATUS_MDEP ! C code for a data type which is used for declaring the `mdep' ! component of `cc_status'. It defaults to `int'. ! This macro is not used on machines that do not use `cc0'. -- Macro: CC_STATUS_MDEP_INIT ! A C expression to initialize the `mdep' field to "empty". The default definition does nothing, since most machines don't use the field anyway. If you want to use the field, you should probably define this macro to initialize it. ! This macro is not used on machines that do not use `cc0'. -- Macro: NOTICE_UPDATE_CC (EXP, INSN) ! A C compound statement to set the components of `cc_status' appropriately for an insn INSN whose body is EXP. It is this macro's responsibility to recognize insns that set the condition code as a byproduct of other activity as well as those that ! explicitly set `(cc0)'. ! This macro is not used on machines that do not use `cc0'. If there are insns that do not set the condition code but do alter other machine registers, this macro must check to see whether they invalidate the expressions that the condition code is recorded as reflecting. For example, on the 68000, insns that store in address registers do not set the condition code, which means that usually ! `NOTICE_UPDATE_CC' can leave `cc_status' unaltered for such insns. But suppose that the previous insn set the condition code based on ! location `a4@(102)' and the current insn stores a new value in ! `a4'. Although the condition code is not changed by this, it will ! no longer be true that it reflects the contents of `a4@(102)'. ! Therefore, `NOTICE_UPDATE_CC' must alter `cc_status' in this case to say that nothing is known about the condition code value. ! The definition of `NOTICE_UPDATE_CC' must be prepared to deal with the results of peephole optimization: insns whose patterns are ! `parallel' RTXs containing various `reg', `mem' or constants which are just the operands. The RTL structure of these insns is not sufficient to indicate what the insns actually do. What ! `NOTICE_UPDATE_CC' should do when it sees one is just to run ! `CC_STATUS_INIT'. ! A possible definition of `NOTICE_UPDATE_CC' is to call a function that looks at an attribute (*note Insn Attributes::) named, for ! example, `cc'. This avoids having detailed information about ! patterns in two places, the `md' file and in `NOTICE_UPDATE_CC'.  File: gccint.info, Node: MODE_CC Condition Codes, Prev: CC0 Condition Codes, Up: Condition Code *************** File: gccint.info, Node: MODE_CC Condit *** 33342,33364 **** -- Macro: SELECT_CC_MODE (OP, X, Y) On many machines, the condition code may be produced by other ! instructions than compares, for example the branch can use directly ! the condition code set by a subtract instruction. However, on some ! machines when the condition code is set this way some bits (such as ! the overflow bit) are not set in the same way as a test ! instruction, so that a different branch instruction must be used ! for some conditional branches. When this happens, use the machine ! mode of the condition code register to record different formats of ! the condition code register. Modes can also be used to record ! which compare instruction (e.g. a signed or an unsigned comparison) produced the condition codes. ! If other modes than 'CCmode' are required, add them to ! 'MACHINE-modes.def' and define 'SELECT_CC_MODE' to choose a mode given an operand of a compare. This is needed because the modes have to be chosen not only during RTL generation but also, for example, by instruction combination. The result of ! 'SELECT_CC_MODE' should be consistent with the mode used in the patterns; for example to support the case of the add on the SPARC discussed above, we have the pattern --- 33768,33790 ---- -- Macro: SELECT_CC_MODE (OP, X, Y) On many machines, the condition code may be produced by other ! instructions than compares, for example the branch can use ! directly the condition code set by a subtract instruction. ! However, on some machines when the condition code is set this way ! some bits (such as the overflow bit) are not set in the same way ! as a test instruction, so that a different branch instruction must ! be used for some conditional branches. When this happens, use the ! machine mode of the condition code register to record different ! formats of the condition code register. Modes can also be used to ! record which compare instruction (e.g. a signed or an unsigned comparison) produced the condition codes. ! If other modes than `CCmode' are required, add them to ! `MACHINE-modes.def' and define `SELECT_CC_MODE' to choose a mode given an operand of a compare. This is needed because the modes have to be chosen not only during RTL generation but also, for example, by instruction combination. The result of ! `SELECT_CC_MODE' should be consistent with the mode used in the patterns; for example to support the case of the add on the SPARC discussed above, we have the pattern *************** File: gccint.info, Node: MODE_CC Condit *** 33371,33378 **** "" "...") ! together with a 'SELECT_CC_MODE' that returns 'CC_NOOVmode' for ! comparisons whose argument is a 'plus': #define SELECT_CC_MODE(OP,X,Y) \ (GET_MODE_CLASS (GET_MODE (X)) == MODE_FLOAT \ --- 33797,33804 ---- "" "...") ! together with a `SELECT_CC_MODE' that returns `CC_NOOVmode' for ! comparisons whose argument is a `plus': #define SELECT_CC_MODE(OP,X,Y) \ (GET_MODE_CLASS (GET_MODE (X)) == MODE_FLOAT \ *************** File: gccint.info, Node: MODE_CC Condit *** 33383,33427 **** ? CC_NOOVmode : CCmode)) Another reason to use modes is to retain information on which ! operands were used by the comparison; see 'REVERSIBLE_CC_MODE' later in this section. You should define this macro if and only if you define extra CC ! modes in 'MACHINE-modes.def'. -- Target Hook: void TARGET_CANONICALIZE_COMPARISON (int *CODE, rtx *OP0, rtx *OP1, bool OP0_PRESERVE_VALUE) On some machines not all possible comparisons are defined, but you can convert an invalid comparison into a valid one. For example, ! the Alpha does not have a 'GT' comparison, but you can use an 'LT' comparison instead and swap the order of the operands. On such machines, implement this hook to do any required conversions. CODE is the initial comparison code and OP0 and OP1 are the left and right operands of the comparison, respectively. ! If OP0_PRESERVE_VALUE is 'true' the implementation is not allowed to change the value of OP0 since the value might be used in RTXs ! which aren't comparisons. E.g. the implementation is not allowed to swap operands in that case. GCC will not assume that the comparison resulting from this macro is valid but will see if the resulting insn matches a pattern in ! the 'md' file. You need not to implement this hook if it would never change the comparison code or operands. -- Macro: REVERSIBLE_CC_MODE (MODE) A C expression whose value is one if it is always safe to reverse a ! comparison whose mode is MODE. If 'SELECT_CC_MODE' can ever return ! MODE for a floating-point inequality comparison, then ! 'REVERSIBLE_CC_MODE (MODE)' must be zero. You need not define this macro if it would always returns zero or if the floating-point format is anything other than ! 'IEEE_FLOAT_FORMAT'. For example, here is the definition used on the SPARC, where floating-point inequality comparisons are given ! either 'CCFPEmode' or 'CCFPmode': #define REVERSIBLE_CC_MODE(MODE) \ ((MODE) != CCFPEmode && (MODE) != CCFPmode) --- 33809,33853 ---- ? CC_NOOVmode : CCmode)) Another reason to use modes is to retain information on which ! operands were used by the comparison; see `REVERSIBLE_CC_MODE' later in this section. You should define this macro if and only if you define extra CC ! modes in `MACHINE-modes.def'. -- Target Hook: void TARGET_CANONICALIZE_COMPARISON (int *CODE, rtx *OP0, rtx *OP1, bool OP0_PRESERVE_VALUE) On some machines not all possible comparisons are defined, but you can convert an invalid comparison into a valid one. For example, ! the Alpha does not have a `GT' comparison, but you can use an `LT' comparison instead and swap the order of the operands. On such machines, implement this hook to do any required conversions. CODE is the initial comparison code and OP0 and OP1 are the left and right operands of the comparison, respectively. ! If OP0_PRESERVE_VALUE is `true' the implementation is not allowed to change the value of OP0 since the value might be used in RTXs ! which aren't comparisons. E.g. the implementation is not allowed to swap operands in that case. GCC will not assume that the comparison resulting from this macro is valid but will see if the resulting insn matches a pattern in ! the `md' file. You need not to implement this hook if it would never change the comparison code or operands. -- Macro: REVERSIBLE_CC_MODE (MODE) A C expression whose value is one if it is always safe to reverse a ! comparison whose mode is MODE. If `SELECT_CC_MODE' can ever ! return MODE for a floating-point inequality comparison, then ! `REVERSIBLE_CC_MODE (MODE)' must be zero. You need not define this macro if it would always returns zero or if the floating-point format is anything other than ! `IEEE_FLOAT_FORMAT'. For example, here is the definition used on the SPARC, where floating-point inequality comparisons are given ! either `CCFPEmode' or `CCFPmode': #define REVERSIBLE_CC_MODE(MODE) \ ((MODE) != CCFPEmode && (MODE) != CCFPmode) *************** File: gccint.info, Node: MODE_CC Condit *** 33429,33439 **** -- Macro: REVERSE_CONDITION (CODE, MODE) A C expression whose value is reversed condition code of the CODE for comparison done in CC_MODE MODE. The macro is used only in ! case 'REVERSIBLE_CC_MODE (MODE)' is nonzero. Define this macro in case machine has some non-standard way how to reverse certain conditionals. For instance in case all floating point conditions ! are non-trapping, compiler may freely convert unordered compares to ! ordered ones. Then definition may look like: #define REVERSE_CONDITION(CODE, MODE) \ ((MODE) != CCFPmode ? reverse_condition (CODE) \ --- 33855,33865 ---- -- Macro: REVERSE_CONDITION (CODE, MODE) A C expression whose value is reversed condition code of the CODE for comparison done in CC_MODE MODE. The macro is used only in ! case `REVERSIBLE_CC_MODE (MODE)' is nonzero. Define this macro in case machine has some non-standard way how to reverse certain conditionals. For instance in case all floating point conditions ! are non-trapping, compiler may freely convert unordered compares ! to ordered ones. Then definition may look like: #define REVERSE_CONDITION(CODE, MODE) \ ((MODE) != CCFPmode ? reverse_condition (CODE) \ *************** File: gccint.info, Node: MODE_CC Condit *** 33441,33476 **** -- Target Hook: bool TARGET_FIXED_CONDITION_CODE_REGS (unsigned int *P1, unsigned int *P2) ! On targets which do not use '(cc0)', and which use a hard register rather than a pseudo-register to hold condition codes, the regular CSE passes are often not able to identify cases in which the hard ! register is set to a common value. Use this hook to enable a small ! pass which optimizes such cases. This hook should return true to ! enable this pass, and it should set the integers to which its ! arguments point to the hard register numbers used for condition ! codes. When there is only one such register, as is true on most ! systems, the integer pointed to by P2 should be set to ! 'INVALID_REGNUM'. The default version of this hook returns false. -- Target Hook: machine_mode TARGET_CC_MODES_COMPATIBLE (machine_mode M1, machine_mode M2) On targets which use multiple condition code modes in class ! 'MODE_CC', it is sometimes the case that a comparison can be validly done in more than one mode. On such a system, define this target hook to take two mode arguments and to return a mode in which both comparisons may be validly done. If there is no such ! mode, return 'VOIDmode'. The default version of this hook checks whether the modes are the same. If they are, it returns that mode. If they are different, ! it returns 'VOIDmode'. -- Target Hook: unsigned int TARGET_FLAGS_REGNUM If the target has a dedicated flags register, and it needs to use ! the post-reload comparison elimination pass, then this value should ! be set appropriately.  File: gccint.info, Node: Costs, Next: Scheduling, Prev: Condition Code, Up: Target Macros --- 33867,33902 ---- -- Target Hook: bool TARGET_FIXED_CONDITION_CODE_REGS (unsigned int *P1, unsigned int *P2) ! On targets which do not use `(cc0)', and which use a hard register rather than a pseudo-register to hold condition codes, the regular CSE passes are often not able to identify cases in which the hard ! register is set to a common value. Use this hook to enable a ! small pass which optimizes such cases. This hook should return ! true to enable this pass, and it should set the integers to which ! its arguments point to the hard register numbers used for ! condition codes. When there is only one such register, as is true ! on most systems, the integer pointed to by P2 should be set to ! `INVALID_REGNUM'. The default version of this hook returns false. -- Target Hook: machine_mode TARGET_CC_MODES_COMPATIBLE (machine_mode M1, machine_mode M2) On targets which use multiple condition code modes in class ! `MODE_CC', it is sometimes the case that a comparison can be validly done in more than one mode. On such a system, define this target hook to take two mode arguments and to return a mode in which both comparisons may be validly done. If there is no such ! mode, return `VOIDmode'. The default version of this hook checks whether the modes are the same. If they are, it returns that mode. If they are different, ! it returns `VOIDmode'. -- Target Hook: unsigned int TARGET_FLAGS_REGNUM If the target has a dedicated flags register, and it needs to use ! the post-reload comparison elimination pass, then this value ! should be set appropriately.  File: gccint.info, Node: Costs, Next: Scheduling, Prev: Condition Code, Up: Target Macros *************** on the target machine. *** 33484,33490 **** -- Macro: REGISTER_MOVE_COST (MODE, FROM, TO) A C expression for the cost of moving data of mode MODE from a register in class FROM to one in class TO. The classes are ! expressed using the enumeration values such as 'GENERAL_REGS'. A value of 2 is the default; other values are interpreted relative to that. --- 33910,33916 ---- -- Macro: REGISTER_MOVE_COST (MODE, FROM, TO) A C expression for the cost of moving data of mode MODE from a register in class FROM to one in class TO. The classes are ! expressed using the enumeration values such as `GENERAL_REGS'. A value of 2 is the default; other values are interpreted relative to that. *************** on the target machine. *** 33492,33513 **** same as TO; on some machines it is expensive to move between registers if they are not general registers. ! If reload sees an insn consisting of a single 'set' between two ! hard registers, and if 'REGISTER_MOVE_COST' applied to their classes returns a value of 2, reload does not check to ensure that the constraints of the insn are met. Setting a cost of other than 2 will allow reload to verify that the constraints are met. You ! should do this if the 'movM' pattern's constraints do not allow such copying. These macros are obsolete, new ports should use the target hook ! 'TARGET_REGISTER_MOVE_COST' instead. -- Target Hook: int TARGET_REGISTER_MOVE_COST (machine_mode MODE, reg_class_t FROM, reg_class_t TO) This target hook should return the cost of moving data of mode MODE from a register in class FROM to one in class TO. The classes are ! expressed using the enumeration values such as 'GENERAL_REGS'. A value of 2 is the default; other values are interpreted relative to that. --- 33918,33939 ---- same as TO; on some machines it is expensive to move between registers if they are not general registers. ! If reload sees an insn consisting of a single `set' between two ! hard registers, and if `REGISTER_MOVE_COST' applied to their classes returns a value of 2, reload does not check to ensure that the constraints of the insn are met. Setting a cost of other than 2 will allow reload to verify that the constraints are met. You ! should do this if the `movM' pattern's constraints do not allow such copying. These macros are obsolete, new ports should use the target hook ! `TARGET_REGISTER_MOVE_COST' instead. -- Target Hook: int TARGET_REGISTER_MOVE_COST (machine_mode MODE, reg_class_t FROM, reg_class_t TO) This target hook should return the cost of moving data of mode MODE from a register in class FROM to one in class TO. The classes are ! expressed using the enumeration values such as `GENERAL_REGS'. A value of 2 is the default; other values are interpreted relative to that. *************** on the target machine. *** 33515,33526 **** same as TO; on some machines it is expensive to move between registers if they are not general registers. ! If reload sees an insn consisting of a single 'set' between two ! hard registers, and if 'TARGET_REGISTER_MOVE_COST' applied to their classes returns a value of 2, reload does not check to ensure that the constraints of the insn are met. Setting a cost of other than 2 will allow reload to verify that the constraints are met. You ! should do this if the 'movM' pattern's constraints do not allow such copying. The default version of this function returns 2. --- 33941,33952 ---- same as TO; on some machines it is expensive to move between registers if they are not general registers. ! If reload sees an insn consisting of a single `set' between two ! hard registers, and if `TARGET_REGISTER_MOVE_COST' applied to their classes returns a value of 2, reload does not check to ensure that the constraints of the insn are met. Setting a cost of other than 2 will allow reload to verify that the constraints are met. You ! should do this if the `movM' pattern's constraints do not allow such copying. The default version of this function returns 2. *************** on the target machine. *** 33528,33535 **** -- Macro: MEMORY_MOVE_COST (MODE, CLASS, IN) A C expression for the cost of moving data of mode MODE between a register of class CLASS and memory; IN is zero if the value is to ! be written to memory, nonzero if it is to be read in. This cost is ! relative to those in 'REGISTER_MOVE_COST'. If moving between registers and memory is more expensive than between two registers, you should define this macro to express the relative cost. --- 33954,33961 ---- -- Macro: MEMORY_MOVE_COST (MODE, CLASS, IN) A C expression for the cost of moving data of mode MODE between a register of class CLASS and memory; IN is zero if the value is to ! be written to memory, nonzero if it is to be read in. This cost ! is relative to those in `REGISTER_MOVE_COST'. If moving between registers and memory is more expensive than between two registers, you should define this macro to express the relative cost. *************** on the target machine. *** 33540,33565 **** mechanism is more complex than copying via an intermediate, define this macro to reflect the actual cost of the move. ! GCC defines the function 'memory_move_secondary_cost' if secondary reloads are needed. It computes the costs due to copying via a secondary register. If your machine copies from memory using a secondary register in the conventional way but the default base value of 4 is not correct for your machine, define this macro to ! add some other value to the result of that function. The arguments ! to that function are the same as to this macro. These macros are obsolete, new ports should use the target hook ! 'TARGET_MEMORY_MOVE_COST' instead. -- Target Hook: int TARGET_MEMORY_MOVE_COST (machine_mode MODE, reg_class_t RCLASS, bool IN) This target hook should return the cost of moving data of mode MODE ! between a register of class RCLASS and memory; IN is 'false' if the ! value is to be written to memory, 'true' if it is to be read in. ! This cost is relative to those in 'TARGET_REGISTER_MOVE_COST'. If ! moving between registers and memory is more expensive than between ! two registers, you should add this target hook to express the ! relative cost. If you do not add this target hook, GCC uses a default cost of 4 plus the cost of copying via a secondary reload register, if one is --- 33966,33991 ---- mechanism is more complex than copying via an intermediate, define this macro to reflect the actual cost of the move. ! GCC defines the function `memory_move_secondary_cost' if secondary reloads are needed. It computes the costs due to copying via a secondary register. If your machine copies from memory using a secondary register in the conventional way but the default base value of 4 is not correct for your machine, define this macro to ! add some other value to the result of that function. The ! arguments to that function are the same as to this macro. These macros are obsolete, new ports should use the target hook ! `TARGET_MEMORY_MOVE_COST' instead. -- Target Hook: int TARGET_MEMORY_MOVE_COST (machine_mode MODE, reg_class_t RCLASS, bool IN) This target hook should return the cost of moving data of mode MODE ! between a register of class RCLASS and memory; IN is `false' if ! the value is to be written to memory, `true' if it is to be read ! in. This cost is relative to those in `TARGET_REGISTER_MOVE_COST'. ! If moving between registers and memory is more expensive than ! between two registers, you should add this target hook to express ! the relative cost. If you do not add this target hook, GCC uses a default cost of 4 plus the cost of copying via a secondary reload register, if one is *************** on the target machine. *** 33568,33589 **** mechanism is more complex than copying via an intermediate, use this target hook to reflect the actual cost of the move. ! GCC defines the function 'memory_move_secondary_cost' if secondary reloads are needed. It computes the costs due to copying via a secondary register. If your machine copies from memory using a secondary register in the conventional way but the default base ! value of 4 is not correct for your machine, use this target hook to ! add some other value to the result of that function. The arguments ! to that function are the same as to this target hook. -- Macro: BRANCH_COST (SPEED_P, PREDICTABLE_P) A C expression for the cost of a branch instruction. A value of 1 is the default; other values are interpreted relative to that. Parameter SPEED_P is true when the branch in question should be ! optimized for speed. When it is false, 'BRANCH_COST' should return ! a value optimal for code size rather than performance. ! PREDICTABLE_P is true for well-predicted branches. On many ! architectures the 'BRANCH_COST' can be reduced then. Here are additional macros which do not specify precise relative costs, but only that certain actions are more expensive than GCC would --- 33994,34015 ---- mechanism is more complex than copying via an intermediate, use this target hook to reflect the actual cost of the move. ! GCC defines the function `memory_move_secondary_cost' if secondary reloads are needed. It computes the costs due to copying via a secondary register. If your machine copies from memory using a secondary register in the conventional way but the default base ! value of 4 is not correct for your machine, use this target hook ! to add some other value to the result of that function. The ! arguments to that function are the same as to this target hook. -- Macro: BRANCH_COST (SPEED_P, PREDICTABLE_P) A C expression for the cost of a branch instruction. A value of 1 is the default; other values are interpreted relative to that. Parameter SPEED_P is true when the branch in question should be ! optimized for speed. When it is false, `BRANCH_COST' should ! return a value optimal for code size rather than performance. ! PREDICTABLE_P is true for well-predicted branches. On many ! architectures the `BRANCH_COST' can be reduced then. Here are additional macros which do not specify precise relative costs, but only that certain actions are more expensive than GCC would *************** ordinarily expect. *** 33591,33597 **** -- Macro: SLOW_BYTE_ACCESS Define this macro as a C expression which is nonzero if accessing ! less than a word of memory (i.e. a 'char' or a 'short') is no faster than accessing a word of memory, i.e., if such access require more than one instruction or if there is no difference in cost between byte and (aligned) word loads. --- 34017,34023 ---- -- Macro: SLOW_BYTE_ACCESS Define this macro as a C expression which is nonzero if accessing ! less than a word of memory (i.e. a `char' or a `short') is no faster than accessing a word of memory, i.e., if such access require more than one instruction or if there is no difference in cost between byte and (aligned) word loads. *************** ordinarily expect. *** 33605,33624 **** structure, but to different bytes. -- Macro: SLOW_UNALIGNED_ACCESS (MODE, ALIGNMENT) ! Define this macro to be the value 1 if memory accesses described by ! the MODE and ALIGNMENT parameters have a cost many times greater than aligned accesses, for example if they are emulated in a trap handler. When this macro is nonzero, the compiler will act as if ! 'STRICT_ALIGNMENT' were nonzero when generating code for block moves. This can cause significantly more instructions to be produced. Therefore, do not set this macro nonzero if unaligned accesses only add a cycle or two to the time for a memory access. If the value of this macro is always zero, it need not be defined. If this macro is defined, it should produce a nonzero value when ! 'STRICT_ALIGNMENT' is nonzero. -- Macro: MOVE_RATIO (SPEED) The threshold of number of scalar memory-to-memory move insns, --- 34031,34050 ---- structure, but to different bytes. -- Macro: SLOW_UNALIGNED_ACCESS (MODE, ALIGNMENT) ! Define this macro to be the value 1 if memory accesses described ! by the MODE and ALIGNMENT parameters have a cost many times greater than aligned accesses, for example if they are emulated in a trap handler. When this macro is nonzero, the compiler will act as if ! `STRICT_ALIGNMENT' were nonzero when generating code for block moves. This can cause significantly more instructions to be produced. Therefore, do not set this macro nonzero if unaligned accesses only add a cycle or two to the time for a memory access. If the value of this macro is always zero, it need not be defined. If this macro is defined, it should produce a nonzero value when ! `STRICT_ALIGNMENT' is nonzero. -- Macro: MOVE_RATIO (SPEED) The threshold of number of scalar memory-to-memory move insns, *************** ordinarily expect. *** 33628,33634 **** increased code size. Note that on machines where the corresponding move insn is a ! 'define_expand' that emits a sequence of insns, this macro counts the number of such sequences. The parameter SPEED is true if the code is currently being --- 34054,34060 ---- increased code size. Note that on machines where the corresponding move insn is a ! `define_expand' that emits a sequence of insns, this macro counts the number of such sequences. The parameter SPEED is true if the code is currently being *************** ordinarily expect. *** 33641,33659 **** by_pieces_operation OP, bool SPEED_P) GCC will attempt several strategies when asked to copy between two areas of memory, or to set, clear or store to memory, for example ! when copying a 'struct'. The 'by_pieces' infrastructure implements such memory operations as a sequence of load, store or move insns. ! Alternate strategies are to expand the 'movmem' or 'setmem' optabs, ! to emit a library call, or to emit unit-by-unit, loop-based ! operations. ! This target hook should return true if, for a memory operation with ! a given SIZE and ALIGNMENT, using the 'by_pieces' infrastructure is ! expected to result in better code generation. Both SIZE and ! ALIGNMENT are measured in terms of storage units. ! The parameter OP is one of: 'CLEAR_BY_PIECES', 'MOVE_BY_PIECES', ! 'SET_BY_PIECES', 'STORE_BY_PIECES'. These describe the type of memory operation under consideration. The parameter SPEED_P is true if the code is currently being --- 34067,34085 ---- by_pieces_operation OP, bool SPEED_P) GCC will attempt several strategies when asked to copy between two areas of memory, or to set, clear or store to memory, for example ! when copying a `struct'. The `by_pieces' infrastructure implements such memory operations as a sequence of load, store or move insns. ! Alternate strategies are to expand the `movmem' or `setmem' ! optabs, to emit a library call, or to emit unit-by-unit, ! loop-based operations. ! This target hook should return true if, for a memory operation ! with a given SIZE and ALIGNMENT, using the `by_pieces' ! infrastructure is expected to result in better code generation. ! Both SIZE and ALIGNMENT are measured in terms of storage units. ! The parameter OP is one of: `CLEAR_BY_PIECES', `MOVE_BY_PIECES', ! `SET_BY_PIECES', `STORE_BY_PIECES'. These describe the type of memory operation under consideration. The parameter SPEED_P is true if the code is currently being *************** ordinarily expect. *** 33661,33680 **** Returning true for higher values of SIZE can improve code generation for speed if the target does not provide an ! implementation of the 'movmem' or 'setmem' standard names, if the ! 'movmem' or 'setmem' implementation would be more expensive than a sequence of insns, or if the overhead of a library call would dominate that of the body of the memory operation. ! Returning true for higher values of 'size' may also cause an increase in code size, for example where the number of insns emitted to perform a move would be greater than that of a library call. -- Macro: MOVE_MAX_PIECES ! A C expression used by 'move_by_pieces' to determine the largest unit a load or store used to copy memory is. Defaults to ! 'MOVE_MAX'. -- Macro: CLEAR_RATIO (SPEED) The threshold of number of scalar move insns, _below_ which a --- 34087,34106 ---- Returning true for higher values of SIZE can improve code generation for speed if the target does not provide an ! implementation of the `movmem' or `setmem' standard names, if the ! `movmem' or `setmem' implementation would be more expensive than a sequence of insns, or if the overhead of a library call would dominate that of the body of the memory operation. ! Returning true for higher values of `size' may also cause an increase in code size, for example where the number of insns emitted to perform a move would be greater than that of a library call. -- Macro: MOVE_MAX_PIECES ! A C expression used by `move_by_pieces' to determine the largest unit a load or store used to copy memory is. Defaults to ! `MOVE_MAX'. -- Macro: CLEAR_RATIO (SPEED) The threshold of number of scalar move insns, _below_ which a *************** ordinarily expect. *** 33698,33744 **** The parameter SPEED is true if the code is currently being optimized for speed rather than size. ! If you don't define this, it defaults to the value of 'MOVE_RATIO'. -- Macro: USE_LOAD_POST_INCREMENT (MODE) A C expression used to determine whether a load postincrement is a good thing to use for a given mode. Defaults to the value of ! 'HAVE_POST_INCREMENT'. -- Macro: USE_LOAD_POST_DECREMENT (MODE) A C expression used to determine whether a load postdecrement is a good thing to use for a given mode. Defaults to the value of ! 'HAVE_POST_DECREMENT'. -- Macro: USE_LOAD_PRE_INCREMENT (MODE) A C expression used to determine whether a load preincrement is a good thing to use for a given mode. Defaults to the value of ! 'HAVE_PRE_INCREMENT'. -- Macro: USE_LOAD_PRE_DECREMENT (MODE) A C expression used to determine whether a load predecrement is a good thing to use for a given mode. Defaults to the value of ! 'HAVE_PRE_DECREMENT'. -- Macro: USE_STORE_POST_INCREMENT (MODE) ! A C expression used to determine whether a store postincrement is a ! good thing to use for a given mode. Defaults to the value of ! 'HAVE_POST_INCREMENT'. -- Macro: USE_STORE_POST_DECREMENT (MODE) ! A C expression used to determine whether a store postdecrement is a ! good thing to use for a given mode. Defaults to the value of ! 'HAVE_POST_DECREMENT'. -- Macro: USE_STORE_PRE_INCREMENT (MODE) This macro is used to determine whether a store preincrement is a good thing to use for a given mode. Defaults to the value of ! 'HAVE_PRE_INCREMENT'. -- Macro: USE_STORE_PRE_DECREMENT (MODE) This macro is used to determine whether a store predecrement is a good thing to use for a given mode. Defaults to the value of ! 'HAVE_PRE_DECREMENT'. -- Macro: NO_FUNCTION_CSE Define this macro to be true if it is as good or better to call a --- 34124,34170 ---- The parameter SPEED is true if the code is currently being optimized for speed rather than size. ! If you don't define this, it defaults to the value of `MOVE_RATIO'. -- Macro: USE_LOAD_POST_INCREMENT (MODE) A C expression used to determine whether a load postincrement is a good thing to use for a given mode. Defaults to the value of ! `HAVE_POST_INCREMENT'. -- Macro: USE_LOAD_POST_DECREMENT (MODE) A C expression used to determine whether a load postdecrement is a good thing to use for a given mode. Defaults to the value of ! `HAVE_POST_DECREMENT'. -- Macro: USE_LOAD_PRE_INCREMENT (MODE) A C expression used to determine whether a load preincrement is a good thing to use for a given mode. Defaults to the value of ! `HAVE_PRE_INCREMENT'. -- Macro: USE_LOAD_PRE_DECREMENT (MODE) A C expression used to determine whether a load predecrement is a good thing to use for a given mode. Defaults to the value of ! `HAVE_PRE_DECREMENT'. -- Macro: USE_STORE_POST_INCREMENT (MODE) ! A C expression used to determine whether a store postincrement is ! a good thing to use for a given mode. Defaults to the value of ! `HAVE_POST_INCREMENT'. -- Macro: USE_STORE_POST_DECREMENT (MODE) ! A C expression used to determine whether a store postdecrement is ! a good thing to use for a given mode. Defaults to the value of ! `HAVE_POST_DECREMENT'. -- Macro: USE_STORE_PRE_INCREMENT (MODE) This macro is used to determine whether a store preincrement is a good thing to use for a given mode. Defaults to the value of ! `HAVE_PRE_INCREMENT'. -- Macro: USE_STORE_PRE_DECREMENT (MODE) This macro is used to determine whether a store predecrement is a good thing to use for a given mode. Defaults to the value of ! `HAVE_PRE_DECREMENT'. -- Macro: NO_FUNCTION_CSE Define this macro to be true if it is as good or better to call a *************** ordinarily expect. *** 33747,33766 **** -- Macro: LOGICAL_OP_NON_SHORT_CIRCUIT Define this macro if a non-short-circuit operation produced by ! 'fold_range_test ()' is optimal. This macro defaults to true if ! 'BRANCH_COST' is greater than or equal to the value 2. -- Target Hook: bool TARGET_OPTAB_SUPPORTED_P (int OP, machine_mode MODE1, machine_mode MODE2, optimization_type OPT_TYPE) Return true if the optimizers should use optab OP with modes MODE1 and MODE2 for optimization type OPT_TYPE. The optab is known to ! have an associated '.md' instruction whose C condition is true. MODE2 is only meaningful for conversion optabs; for direct optabs it is a copy of MODE1. ! For example, when called with OP equal to 'rint_optab' and MODE1 ! equal to 'DFmode', the hook should say whether the optimizers ! should use optab 'rintdf2'. The default hook returns true for all inputs. --- 34173,34192 ---- -- Macro: LOGICAL_OP_NON_SHORT_CIRCUIT Define this macro if a non-short-circuit operation produced by ! `fold_range_test ()' is optimal. This macro defaults to true if ! `BRANCH_COST' is greater than or equal to the value 2. -- Target Hook: bool TARGET_OPTAB_SUPPORTED_P (int OP, machine_mode MODE1, machine_mode MODE2, optimization_type OPT_TYPE) Return true if the optimizers should use optab OP with modes MODE1 and MODE2 for optimization type OPT_TYPE. The optab is known to ! have an associated `.md' instruction whose C condition is true. MODE2 is only meaningful for conversion optabs; for direct optabs it is a copy of MODE1. ! For example, when called with OP equal to `rint_optab' and MODE1 ! equal to `DFmode', the hook should say whether the optimizers ! should use optab `rintdf2'. The default hook returns true for all inputs. *************** ordinarily expect. *** 33771,33810 **** The cost may depend on the precise form of the expression, which is available for examination in X, and the fact that X appears as operand OPNO of an expression with rtx code OUTER_CODE. That is, ! the hook can assume that there is some rtx Y such that 'GET_CODE ! (Y) == OUTER_CODE' and such that either (a) 'XEXP (Y, OPNO) == X' ! or (b) 'XVEC (Y, OPNO)' contains X. ! MODE is X's machine mode, or for cases like 'const_int' that do not ! have a mode, the mode in which X is used. ! In implementing this hook, you can use the construct 'COSTS_N_INSNS ! (N)' to specify a cost equal to N fast instructions. ! On entry to the hook, '*TOTAL' contains a default estimate for the cost of the expression. The hook should modify this value as ! necessary. Traditionally, the default costs are 'COSTS_N_INSNS ! (5)' for multiplications, 'COSTS_N_INSNS (7)' for division and ! modulus operations, and 'COSTS_N_INSNS (1)' for all other operations. ! When optimizing for code size, i.e. when 'speed' is false, this ! target hook should be used to estimate the relative size cost of an ! expression, again relative to 'COSTS_N_INSNS'. The hook returns true when all subexpressions of X have been ! processed, and false when 'rtx_cost' should recurse. -- Target Hook: int TARGET_ADDRESS_COST (rtx ADDRESS, machine_mode MODE, addr_space_t AS, bool SPEED) This hook computes the cost of an addressing mode that contains ADDRESS. If not defined, the cost is computed from the ADDRESS ! expression and the 'TARGET_RTX_COST' hook. ! For most CISC machines, the default cost is a good approximation of ! the true cost of the addressing mode. However, on RISC machines, ! all instructions normally have the same length and execution time. ! Hence all addresses will have equal costs. In cases where more than one form of an address is known, the form with the lowest cost will be used. If multiple forms have the --- 34197,34236 ---- The cost may depend on the precise form of the expression, which is available for examination in X, and the fact that X appears as operand OPNO of an expression with rtx code OUTER_CODE. That is, ! the hook can assume that there is some rtx Y such that `GET_CODE ! (Y) == OUTER_CODE' and such that either (a) `XEXP (Y, OPNO) == X' ! or (b) `XVEC (Y, OPNO)' contains X. ! MODE is X's machine mode, or for cases like `const_int' that do ! not have a mode, the mode in which X is used. ! In implementing this hook, you can use the construct ! `COSTS_N_INSNS (N)' to specify a cost equal to N fast instructions. ! On entry to the hook, `*TOTAL' contains a default estimate for the cost of the expression. The hook should modify this value as ! necessary. Traditionally, the default costs are `COSTS_N_INSNS ! (5)' for multiplications, `COSTS_N_INSNS (7)' for division and ! modulus operations, and `COSTS_N_INSNS (1)' for all other operations. ! When optimizing for code size, i.e. when `speed' is false, this ! target hook should be used to estimate the relative size cost of ! an expression, again relative to `COSTS_N_INSNS'. The hook returns true when all subexpressions of X have been ! processed, and false when `rtx_cost' should recurse. -- Target Hook: int TARGET_ADDRESS_COST (rtx ADDRESS, machine_mode MODE, addr_space_t AS, bool SPEED) This hook computes the cost of an addressing mode that contains ADDRESS. If not defined, the cost is computed from the ADDRESS ! expression and the `TARGET_RTX_COST' hook. ! For most CISC machines, the default cost is a good approximation ! of the true cost of the addressing mode. However, on RISC ! machines, all instructions normally have the same length and ! execution time. Hence all addresses will have equal costs. In cases where more than one form of an address is known, the form with the lowest cost will be used. If multiple forms have the *************** ordinarily expect. *** 33816,33835 **** register and memory references will be indirect through that register. On machines where the cost of the addressing mode containing the sum is no higher than that of a simple indirect ! reference, this will produce an additional instruction and possibly ! require an additional register. Proper specification of this macro ! eliminates this overhead for such machines. This hook is never called with an invalid address. On machines where an address involving more than one register is as cheap as an address computation involving only one register, ! defining 'TARGET_ADDRESS_COST' to reflect this can cause two registers to be live over a region of code where only one would ! have been if 'TARGET_ADDRESS_COST' were not defined in that manner. ! This effect should be considered in the definition of this macro. ! Equivalent costs should probably only be given to addresses with ! different numbers of registers on machines with lots of registers. -- Target Hook: bool TARGET_NO_SPECULATION_IN_DELAY_SLOTS_P (void) This predicate controls the use of the eager delay slot filler to --- 34242,34262 ---- register and memory references will be indirect through that register. On machines where the cost of the addressing mode containing the sum is no higher than that of a simple indirect ! reference, this will produce an additional instruction and ! possibly require an additional register. Proper specification of ! this macro eliminates this overhead for such machines. This hook is never called with an invalid address. On machines where an address involving more than one register is as cheap as an address computation involving only one register, ! defining `TARGET_ADDRESS_COST' to reflect this can cause two registers to be live over a region of code where only one would ! have been if `TARGET_ADDRESS_COST' were not defined in that ! manner. This effect should be considered in the definition of ! this macro. Equivalent costs should probably only be given to ! addresses with different numbers of registers on machines with ! lots of registers. -- Target Hook: bool TARGET_NO_SPECULATION_IN_DELAY_SLOTS_P (void) This predicate controls the use of the eager delay slot filler to *************** ordinarily expect. *** 33837,33845 **** slots. Targets such as certain MIPS architectures possess both branches with and without delay slots. As the eager delay slot filler can decrease performance, disabling it is beneficial when ! ordinary branches are available. Use of delay slot branches filled ! using the basic filler is often still desirable as the delay slot ! can hide a pipeline bubble.  File: gccint.info, Node: Scheduling, Next: Sections, Prev: Costs, Up: Target Macros --- 34264,34272 ---- slots. Targets such as certain MIPS architectures possess both branches with and without delay slots. As the eager delay slot filler can decrease performance, disabling it is beneficial when ! ordinary branches are available. Use of delay slot branches ! filled using the basic filler is often still desirable as the ! delay slot can hide a pipeline bubble.  File: gccint.info, Node: Scheduling, Next: Sections, Prev: Costs, Up: Target Macros *************** them: try the first ones in this list fi *** 33858,33883 **** Although the insn scheduler can define itself the possibility of issue an insn on the same cycle, the value can serve as an additional constraint to issue insns on the same simulated ! processor cycle (see hooks 'TARGET_SCHED_REORDER' and ! 'TARGET_SCHED_REORDER2'). This value must be constant over the entire compilation. If you need it to vary depending on what the ! instructions are, you must use 'TARGET_SCHED_VARIABLE_ISSUE'. -- Target Hook: int TARGET_SCHED_VARIABLE_ISSUE (FILE *FILE, int VERBOSE, rtx_insn *INSN, int MORE) This hook is executed by the scheduler after it has scheduled an insn from the ready list. It should return the number of insns which can still be issued in the current cycle. The default is ! 'MORE - 1' for insns other than 'CLOBBER' and 'USE', which normally ! are not counted against the issue rate. You should define this ! hook if some insns take more machine resources than others, so that ! fewer insns can follow them in the same cycle. FILE is either a ! null pointer, or a stdio stream to write any debug output to. ! VERBOSE is the verbose level provided by '-fsched-verbose-N'. INSN ! is the instruction that was scheduled. ! -- Target Hook: int TARGET_SCHED_ADJUST_COST (rtx_insn *INSN, rtx LINK, ! rtx_insn *DEP_INSN, int COST) This function corrects the value of COST based on the relationship between INSN and DEP_INSN through the dependence LINK. It should return the new value. The default is to make no adjustment to --- 34285,34310 ---- Although the insn scheduler can define itself the possibility of issue an insn on the same cycle, the value can serve as an additional constraint to issue insns on the same simulated ! processor cycle (see hooks `TARGET_SCHED_REORDER' and ! `TARGET_SCHED_REORDER2'). This value must be constant over the entire compilation. If you need it to vary depending on what the ! instructions are, you must use `TARGET_SCHED_VARIABLE_ISSUE'. -- Target Hook: int TARGET_SCHED_VARIABLE_ISSUE (FILE *FILE, int VERBOSE, rtx_insn *INSN, int MORE) This hook is executed by the scheduler after it has scheduled an insn from the ready list. It should return the number of insns which can still be issued in the current cycle. The default is ! `MORE - 1' for insns other than `CLOBBER' and `USE', which ! normally are not counted against the issue rate. You should ! define this hook if some insns take more machine resources than ! others, so that fewer insns can follow them in the same cycle. ! FILE is either a null pointer, or a stdio stream to write any ! debug output to. VERBOSE is the verbose level provided by ! `-fsched-verbose-N'. INSN is the instruction that was scheduled. ! -- Target Hook: int TARGET_SCHED_ADJUST_COST (rtx_insn *INSN, rtx ! LINK, rtx_insn *DEP_INSN, int COST) This function corrects the value of COST based on the relationship between INSN and DEP_INSN through the dependence LINK. It should return the new value. The default is to make no adjustment to *************** them: try the first ones in this list fi *** 33893,33931 **** -- Target Hook: int TARGET_SCHED_ADJUST_PRIORITY (rtx_insn *INSN, int PRIORITY) ! This hook adjusts the integer scheduling priority PRIORITY of INSN. ! It should return the new priority. Increase the priority to execute INSN earlier, reduce the priority to execute INSN later. ! Do not define this hook if you do not need to adjust the scheduling ! priorities of insns. -- Target Hook: int TARGET_SCHED_REORDER (FILE *FILE, int VERBOSE, rtx_insn **READY, int *N_READYP, int CLOCK) This hook is executed by the scheduler after it has scheduled the ready list, to allow the machine description to reorder it (for ! example to combine two small instructions together on 'VLIW' machines). FILE is either a null pointer, or a stdio stream to write any debug output to. VERBOSE is the verbose level provided ! by '-fsched-verbose-N'. READY is a pointer to the ready list of ! instructions that are ready to be scheduled. N_READYP is a pointer ! to the number of elements in the ready list. The scheduler reads ! the ready list in reverse order, starting with READY[*N_READYP - 1] ! and going to READY[0]. CLOCK is the timer tick of the scheduler. ! You may modify the ready list and the number of ready insns. The ! return value is the number of insns that can issue this cycle; ! normally this is just 'issue_rate'. See also ! 'TARGET_SCHED_REORDER2'. -- Target Hook: int TARGET_SCHED_REORDER2 (FILE *FILE, int VERBOSE, rtx_insn **READY, int *N_READYP, int CLOCK) ! Like 'TARGET_SCHED_REORDER', but called at a different time. That ! function is called whenever the scheduler starts a new cycle. This ! one is called once per iteration over a cycle, immediately after ! 'TARGET_SCHED_VARIABLE_ISSUE'; it can reorder the ready list and ! return the number of insns to be scheduled in the same cycle. Defining this hook can be useful if there are frequent situations ! where scheduling one insn causes other insns to become ready in the ! same cycle. These other insns can then be taken into account properly. -- Target Hook: bool TARGET_SCHED_MACRO_FUSION_P (void) --- 34320,34358 ---- -- Target Hook: int TARGET_SCHED_ADJUST_PRIORITY (rtx_insn *INSN, int PRIORITY) ! This hook adjusts the integer scheduling priority PRIORITY of ! INSN. It should return the new priority. Increase the priority to execute INSN earlier, reduce the priority to execute INSN later. ! Do not define this hook if you do not need to adjust the ! scheduling priorities of insns. -- Target Hook: int TARGET_SCHED_REORDER (FILE *FILE, int VERBOSE, rtx_insn **READY, int *N_READYP, int CLOCK) This hook is executed by the scheduler after it has scheduled the ready list, to allow the machine description to reorder it (for ! example to combine two small instructions together on `VLIW' machines). FILE is either a null pointer, or a stdio stream to write any debug output to. VERBOSE is the verbose level provided ! by `-fsched-verbose-N'. READY is a pointer to the ready list of ! instructions that are ready to be scheduled. N_READYP is a ! pointer to the number of elements in the ready list. The scheduler ! reads the ready list in reverse order, starting with ! READY[*N_READYP - 1] and going to READY[0]. CLOCK is the timer ! tick of the scheduler. You may modify the ready list and the ! number of ready insns. The return value is the number of insns ! that can issue this cycle; normally this is just `issue_rate'. ! See also `TARGET_SCHED_REORDER2'. -- Target Hook: int TARGET_SCHED_REORDER2 (FILE *FILE, int VERBOSE, rtx_insn **READY, int *N_READYP, int CLOCK) ! Like `TARGET_SCHED_REORDER', but called at a different time. That ! function is called whenever the scheduler starts a new cycle. ! This one is called once per iteration over a cycle, immediately ! after `TARGET_SCHED_VARIABLE_ISSUE'; it can reorder the ready list ! and return the number of insns to be scheduled in the same cycle. Defining this hook can be useful if there are frequent situations ! where scheduling one insn causes other insns to become ready in ! the same cycle. These other insns can then be taken into account properly. -- Target Hook: bool TARGET_SCHED_MACRO_FUSION_P (void) *************** them: try the first ones in this list fi *** 33935,33946 **** -- Target Hook: bool TARGET_SCHED_MACRO_FUSION_PAIR_P (rtx_insn *PREV, rtx_insn *CURR) This hook is used to check whether two insns should be macro fused ! for a target microarchitecture. If this hook returns true for the ! given insn pair (PREV and CURR), the scheduler will put them into a ! sched group, and they will not be scheduled apart. The two insns ! will be either two SET insns or a compare and a conditional jump ! and this hook should validate any dependencies needed to fuse the ! two insns together. -- Target Hook: void TARGET_SCHED_DEPENDENCIES_EVALUATION_HOOK (rtx_insn *HEAD, rtx_insn *TAIL) --- 34362,34373 ---- -- Target Hook: bool TARGET_SCHED_MACRO_FUSION_PAIR_P (rtx_insn *PREV, rtx_insn *CURR) This hook is used to check whether two insns should be macro fused ! for a target microarchitecture. If this hook returns true for the ! given insn pair (PREV and CURR), the scheduler will put them into ! a sched group, and they will not be scheduled apart. The two ! insns will be either two SET insns or a compare and a conditional ! jump and this hook should validate any dependencies needed to fuse ! the two insns together. -- Target Hook: void TARGET_SCHED_DEPENDENCIES_EVALUATION_HOOK (rtx_insn *HEAD, rtx_insn *TAIL) *************** them: try the first ones in this list fi *** 33957,33989 **** This hook is executed by the scheduler at the beginning of each block of instructions that are to be scheduled. FILE is either a null pointer, or a stdio stream to write any debug output to. ! VERBOSE is the verbose level provided by '-fsched-verbose-N'. MAX_READY is the maximum number of insns in the current scheduling region that can be live at the same time. This can be used to allocate scratch space if it is needed, e.g. by ! 'TARGET_SCHED_REORDER'. -- Target Hook: void TARGET_SCHED_FINISH (FILE *FILE, int VERBOSE) This hook is executed by the scheduler at the end of each block of instructions that are to be scheduled. It can be used to perform ! cleanup of any actions done by the other scheduling hooks. FILE is ! either a null pointer, or a stdio stream to write any debug output ! to. VERBOSE is the verbose level provided by '-fsched-verbose-N'. ! -- Target Hook: void TARGET_SCHED_INIT_GLOBAL (FILE *FILE, int VERBOSE, ! int OLD_MAX_UID) This hook is executed by the scheduler after function level initializations. FILE is either a null pointer, or a stdio stream to write any debug output to. VERBOSE is the verbose level ! provided by '-fsched-verbose-N'. OLD_MAX_UID is the maximum insn uid when scheduling begins. -- Target Hook: void TARGET_SCHED_FINISH_GLOBAL (FILE *FILE, int VERBOSE) This is the cleanup hook corresponding to ! 'TARGET_SCHED_INIT_GLOBAL'. FILE is either a null pointer, or a stdio stream to write any debug output to. VERBOSE is the verbose ! level provided by '-fsched-verbose-N'. -- Target Hook: rtx TARGET_SCHED_DFA_PRE_CYCLE_INSN (void) The hook returns an RTL insn. The automaton state used in the --- 34384,34417 ---- This hook is executed by the scheduler at the beginning of each block of instructions that are to be scheduled. FILE is either a null pointer, or a stdio stream to write any debug output to. ! VERBOSE is the verbose level provided by `-fsched-verbose-N'. MAX_READY is the maximum number of insns in the current scheduling region that can be live at the same time. This can be used to allocate scratch space if it is needed, e.g. by ! `TARGET_SCHED_REORDER'. -- Target Hook: void TARGET_SCHED_FINISH (FILE *FILE, int VERBOSE) This hook is executed by the scheduler at the end of each block of instructions that are to be scheduled. It can be used to perform ! cleanup of any actions done by the other scheduling hooks. FILE ! is either a null pointer, or a stdio stream to write any debug ! output to. VERBOSE is the verbose level provided by ! `-fsched-verbose-N'. ! -- Target Hook: void TARGET_SCHED_INIT_GLOBAL (FILE *FILE, int ! VERBOSE, int OLD_MAX_UID) This hook is executed by the scheduler after function level initializations. FILE is either a null pointer, or a stdio stream to write any debug output to. VERBOSE is the verbose level ! provided by `-fsched-verbose-N'. OLD_MAX_UID is the maximum insn uid when scheduling begins. -- Target Hook: void TARGET_SCHED_FINISH_GLOBAL (FILE *FILE, int VERBOSE) This is the cleanup hook corresponding to ! `TARGET_SCHED_INIT_GLOBAL'. FILE is either a null pointer, or a stdio stream to write any debug output to. VERBOSE is the verbose ! level provided by `-fsched-verbose-N'. -- Target Hook: rtx TARGET_SCHED_DFA_PRE_CYCLE_INSN (void) The hook returns an RTL insn. The automaton state used in the *************** them: try the first ones in this list fi *** 33991,34022 **** when the new simulated processor cycle starts. Usage of the hook may simplify the automaton pipeline description for some VLIW processors. If the hook is defined, it is used only for the ! automaton based pipeline description. The default is not to change ! the state when the new simulated processor cycle starts. -- Target Hook: void TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN (void) The hook can be used to initialize data used by the previous hook. -- Target Hook: rtx_insn * TARGET_SCHED_DFA_POST_CYCLE_INSN (void) ! The hook is analogous to 'TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used to changed the state as if the insn were scheduled when the new simulated processor cycle finishes. -- Target Hook: void TARGET_SCHED_INIT_DFA_POST_CYCLE_INSN (void) ! The hook is analogous to 'TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN' but used to initialize data used by the previous hook. -- Target Hook: void TARGET_SCHED_DFA_PRE_ADVANCE_CYCLE (void) ! The hook to notify target that the current simulated cycle is about ! to finish. The hook is analogous to ! 'TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used to change the state in more complicated situations - e.g., when advancing state on a single insn is not enough. -- Target Hook: void TARGET_SCHED_DFA_POST_ADVANCE_CYCLE (void) The hook to notify target that new simulated cycle has just started. The hook is analogous to ! 'TARGET_SCHED_DFA_POST_CYCLE_INSN' but used to change the state in more complicated situations - e.g., when advancing state on a single insn is not enough. --- 34419,34450 ---- when the new simulated processor cycle starts. Usage of the hook may simplify the automaton pipeline description for some VLIW processors. If the hook is defined, it is used only for the ! automaton based pipeline description. The default is not to ! change the state when the new simulated processor cycle starts. -- Target Hook: void TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN (void) The hook can be used to initialize data used by the previous hook. -- Target Hook: rtx_insn * TARGET_SCHED_DFA_POST_CYCLE_INSN (void) ! The hook is analogous to `TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used to changed the state as if the insn were scheduled when the new simulated processor cycle finishes. -- Target Hook: void TARGET_SCHED_INIT_DFA_POST_CYCLE_INSN (void) ! The hook is analogous to `TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN' but used to initialize data used by the previous hook. -- Target Hook: void TARGET_SCHED_DFA_PRE_ADVANCE_CYCLE (void) ! The hook to notify target that the current simulated cycle is ! about to finish. The hook is analogous to ! `TARGET_SCHED_DFA_PRE_CYCLE_INSN' but used to change the state in more complicated situations - e.g., when advancing state on a single insn is not enough. -- Target Hook: void TARGET_SCHED_DFA_POST_ADVANCE_CYCLE (void) The hook to notify target that new simulated cycle has just started. The hook is analogous to ! `TARGET_SCHED_DFA_POST_CYCLE_INSN' but used to change the state in more complicated situations - e.g., when advancing state on a single insn is not enough. *************** them: try the first ones in this list fi *** 34025,34037 **** This hook controls better choosing an insn from the ready insn queue for the DFA-based insn scheduler. Usually the scheduler chooses the first insn from the queue. If the hook returns a ! positive value, an additional scheduler code tries all permutations ! of 'TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD ()' subsequent ! ready insns to choose an insn whose issue will result in maximal ! number of issued insns on the same cycle. For the VLIW processor, ! the code could actually solve the problem of packing simple insns ! into the VLIW insn. Of course, if the rules of VLIW packing are ! described in the automaton. This code also could be used for superscalar RISC processors. Let us consider a superscalar RISC processor with 3 pipelines. Some --- 34453,34465 ---- This hook controls better choosing an insn from the ready insn queue for the DFA-based insn scheduler. Usually the scheduler chooses the first insn from the queue. If the hook returns a ! positive value, an additional scheduler code tries all ! permutations of `TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD ! ()' subsequent ready insns to choose an insn whose issue will ! result in maximal number of issued insns on the same cycle. For ! the VLIW processor, the code could actually solve the problem of ! packing simple insns into the VLIW insn. Of course, if the rules ! of VLIW packing are described in the automaton. This code also could be used for superscalar RISC processors. Let us consider a superscalar RISC processor with 3 pipelines. Some *************** them: try the first ones in this list fi *** 34049,34063 **** The default is no multipass scheduling. -- Target Hook: int ! TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD_GUARD ! (rtx_insn *INSN, int READY_INDEX) ! This hook controls what insns from the ready insn queue will be considered for the multipass insn scheduling. If the hook returns zero for INSN, the insn will be considered in multipass scheduling. Positive return values will remove INSN from consideration on the ! current round of multipass scheduling. Negative return values will ! remove INSN from consideration for given number of cycles. Backends should be careful about returning non-zero for highest priority instruction at position 0 in the ready list. READY_INDEX is passed to allow backends make correct judgements. --- 34477,34490 ---- The default is no multipass scheduling. -- Target Hook: int ! TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD_GUARD (rtx_insn *INSN, ! int READY_INDEX) This hook controls what insns from the ready insn queue will be considered for the multipass insn scheduling. If the hook returns zero for INSN, the insn will be considered in multipass scheduling. Positive return values will remove INSN from consideration on the ! current round of multipass scheduling. Negative return values ! will remove INSN from consideration for given number of cycles. Backends should be careful about returning non-zero for highest priority instruction at position 0 in the ready list. READY_INDEX is passed to allow backends make correct judgements. *************** them: try the first ones in this list fi *** 34073,34088 **** -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_ISSUE (void *DATA, signed char *READY_TRY, int N_READY, rtx_insn *INSN, const void *PREV_DATA) ! This hook is called when multipass scheduling evaluates instruction ! INSN. -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BACKTRACK (const void *DATA, signed char *READY_TRY, int N_READY) ! This is called when multipass scheduling backtracks from evaluation ! of an instruction. ! -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END (const void ! *DATA) This hook notifies the target about the result of the concluded current round of multipass scheduling. --- 34500,34515 ---- -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_ISSUE (void *DATA, signed char *READY_TRY, int N_READY, rtx_insn *INSN, const void *PREV_DATA) ! This hook is called when multipass scheduling evaluates ! instruction INSN. -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BACKTRACK (const void *DATA, signed char *READY_TRY, int N_READY) ! This is called when multipass scheduling backtracks from ! evaluation of an instruction. ! -- Target Hook: void TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END (const ! void *DATA) This hook notifies the target about the result of the concluded current round of multipass scheduling. *************** them: try the first ones in this list fi *** 34110,34134 **** -- Target Hook: bool TARGET_SCHED_IS_COSTLY_DEPENDENCE (struct _dep *_DEP, int COST, int DISTANCE) ! This hook is used to define which dependences are considered costly ! by the target, so costly that it is not advisable to schedule the ! insns that are involved in the dependence too close to one another. ! The parameters to this hook are as follows: The first parameter ! _DEP is the dependence being evaluated. The second parameter COST ! is the cost of the dependence as estimated by the scheduler, and ! the third parameter DISTANCE is the distance in cycles between the ! two insns. The hook returns 'true' if considering the distance ! between the two insns the dependence between them is considered ! costly by the target, and 'false' otherwise. Defining this hook can be useful in multiple-issue out-of-order ! machines, where (a) it's practically hopeless to predict the actual ! data/resource delays, however: (b) there's a better chance to ! predict the actual grouping that will be formed, and (c) correctly ! emulating the grouping can be very important. In such targets one ! may want to allow issuing dependent insns closer to one ! another--i.e., closer than the dependence distance; however, not in ! cases of "costly dependences", which this hooks allows to define. -- Target Hook: void TARGET_SCHED_H_I_D_EXTENDED (void) This hook is called by the insn scheduler after emitting a new --- 34537,34563 ---- -- Target Hook: bool TARGET_SCHED_IS_COSTLY_DEPENDENCE (struct _dep *_DEP, int COST, int DISTANCE) ! This hook is used to define which dependences are considered ! costly by the target, so costly that it is not advisable to ! schedule the insns that are involved in the dependence too close ! to one another. The parameters to this hook are as follows: The ! first parameter _DEP is the dependence being evaluated. The ! second parameter COST is the cost of the dependence as estimated ! by the scheduler, and the third parameter DISTANCE is the distance ! in cycles between the two insns. The hook returns `true' if ! considering the distance between the two insns the dependence ! between them is considered costly by the target, and `false' ! otherwise. Defining this hook can be useful in multiple-issue out-of-order ! machines, where (a) it's practically hopeless to predict the ! actual data/resource delays, however: (b) there's a better chance ! to predict the actual grouping that will be formed, and (c) ! correctly emulating the grouping can be very important. In such ! targets one may want to allow issuing dependent insns closer to ! one another--i.e., closer than the dependence distance; however, ! not in cases of "costly dependences", which this hooks allows to ! define. -- Target Hook: void TARGET_SCHED_H_I_D_EXTENDED (void) This hook is called by the insn scheduler after emitting a new *************** them: try the first ones in this list fi *** 34143,34158 **** CLEAN_P) Initialize store pointed to by TC to hold target scheduling context. It CLEAN_P is true then initialize TC as if scheduler is ! at the beginning of the block. Otherwise, copy the current context ! into TC. -- Target Hook: void TARGET_SCHED_SET_SCHED_CONTEXT (void *TC) Copy target scheduling context pointed to by TC to the current context. -- Target Hook: void TARGET_SCHED_CLEAR_SCHED_CONTEXT (void *TC) ! Deallocate internal data in target scheduling context pointed to by ! TC. -- Target Hook: void TARGET_SCHED_FREE_SCHED_CONTEXT (void *TC) Deallocate a store for target scheduling context pointed to by TC. --- 34572,34587 ---- CLEAN_P) Initialize store pointed to by TC to hold target scheduling context. It CLEAN_P is true then initialize TC as if scheduler is ! at the beginning of the block. Otherwise, copy the current ! context into TC. -- Target Hook: void TARGET_SCHED_SET_SCHED_CONTEXT (void *TC) Copy target scheduling context pointed to by TC to the current context. -- Target Hook: void TARGET_SCHED_CLEAR_SCHED_CONTEXT (void *TC) ! Deallocate internal data in target scheduling context pointed to ! by TC. -- Target Hook: void TARGET_SCHED_FREE_SCHED_CONTEXT (void *TC) Deallocate a store for target scheduling context pointed to by TC. *************** them: try the first ones in this list fi *** 34165,34186 **** has a speculative version and, in case of successful check, to generate that speculative pattern. The hook should return 1, if the instruction has a speculative form, or -1, if it doesn't. ! REQUEST describes the type of requested speculation. If the return ! value equals 1 then NEW_PAT is assigned the generated speculative ! pattern. -- Target Hook: bool TARGET_SCHED_NEEDS_BLOCK_P (unsigned int DEP_STATUS) This hook is called by the insn scheduler during generation of ! recovery code for INSN. It should return 'true', if the corresponding check instruction should branch to recovery code, or ! 'false' otherwise. -- Target Hook: rtx TARGET_SCHED_GEN_SPEC_CHECK (rtx_insn *INSN, rtx_insn *LABEL, unsigned int DS) ! This hook is called by the insn scheduler to generate a pattern for ! recovery check instruction. If MUTATE_P is zero, then INSN is a ! speculative instruction for which the check should be generated. LABEL is either a label of a basic block, where recovery code should be emitted, or a null pointer, when requested check doesn't branch to recovery code (a simple check). If MUTATE_P is nonzero, --- 34594,34615 ---- has a speculative version and, in case of successful check, to generate that speculative pattern. The hook should return 1, if the instruction has a speculative form, or -1, if it doesn't. ! REQUEST describes the type of requested speculation. If the ! return value equals 1 then NEW_PAT is assigned the generated ! speculative pattern. -- Target Hook: bool TARGET_SCHED_NEEDS_BLOCK_P (unsigned int DEP_STATUS) This hook is called by the insn scheduler during generation of ! recovery code for INSN. It should return `true', if the corresponding check instruction should branch to recovery code, or ! `false' otherwise. -- Target Hook: rtx TARGET_SCHED_GEN_SPEC_CHECK (rtx_insn *INSN, rtx_insn *LABEL, unsigned int DS) ! This hook is called by the insn scheduler to generate a pattern ! for recovery check instruction. If MUTATE_P is zero, then INSN is ! a speculative instruction for which the check should be generated. LABEL is either a label of a basic block, where recovery code should be emitted, or a null pointer, when requested check doesn't branch to recovery code (a simple check). If MUTATE_P is nonzero, *************** them: try the first ones in this list fi *** 34188,34195 **** denoted by INSN should be generated. In this case LABEL can't be null. ! -- Target Hook: void TARGET_SCHED_SET_SCHED_FLAGS (struct spec_info_def ! *SPEC_INFO) This hook is used by the insn scheduler to find out what features should be enabled/used. The structure *SPEC_INFO should be filled in by the target. The structure describes speculation types that --- 34617,34624 ---- denoted by INSN should be generated. In this case LABEL can't be null. ! -- Target Hook: void TARGET_SCHED_SET_SCHED_FLAGS (struct ! spec_info_def *SPEC_INFO) This hook is used by the insn scheduler to find out what features should be enabled/used. The structure *SPEC_INFO should be filled in by the target. The structure describes speculation types that *************** them: try the first ones in this list fi *** 34199,34208 **** This hook is called by the swing modulo scheduler to calculate a resource-based lower bound which is based on the resources available in the machine and the resources required by each ! instruction. The target backend can use G to calculate such bound. ! A very simple lower bound will be used in case this hook is not ! implemented: the total number of instructions divided by the issue ! rate. -- Target Hook: bool TARGET_SCHED_DISPATCH (rtx_insn *INSN, int X) This hook is called by Haifa Scheduler. It returns true if --- 34628,34637 ---- This hook is called by the swing modulo scheduler to calculate a resource-based lower bound which is based on the resources available in the machine and the resources required by each ! instruction. The target backend can use G to calculate such ! bound. A very simple lower bound will be used in case this hook ! is not implemented: the total number of instructions divided by ! the issue rate. -- Target Hook: bool TARGET_SCHED_DISPATCH (rtx_insn *INSN, int X) This hook is called by Haifa Scheduler. It returns true if *************** them: try the first ones in this list fi *** 34214,34233 **** specified in its second parameter. -- Target Hook: bool TARGET_SCHED_EXPOSED_PIPELINE ! True if the processor has an exposed pipeline, which means that not ! just the order of instructions is important for correctness when ! scheduling, but also the latencies of operations. ! -- Target Hook: int TARGET_SCHED_REASSOCIATION_WIDTH (unsigned int OPC, ! machine_mode MODE) This hook is called by tree reassociator to determine a level of parallelism required in output calculations chain. -- Target Hook: void TARGET_SCHED_FUSION_PRIORITY (rtx_insn *INSN, int MAX_PRI, int *FUSION_PRI, int *PRI) This hook is called by scheduling fusion pass. It calculates ! fusion priorities for each instruction passed in by parameter. The ! priorities are returned via pointer parameters. INSN is the instruction whose priorities need to be calculated. MAX_PRI is the maximum priority can be returned in any cases. --- 34643,34662 ---- specified in its second parameter. -- Target Hook: bool TARGET_SCHED_EXPOSED_PIPELINE ! True if the processor has an exposed pipeline, which means that ! not just the order of instructions is important for correctness ! when scheduling, but also the latencies of operations. ! -- Target Hook: int TARGET_SCHED_REASSOCIATION_WIDTH (unsigned int ! OPC, machine_mode MODE) This hook is called by tree reassociator to determine a level of parallelism required in output calculations chain. -- Target Hook: void TARGET_SCHED_FUSION_PRIORITY (rtx_insn *INSN, int MAX_PRI, int *FUSION_PRI, int *PRI) This hook is called by scheduling fusion pass. It calculates ! fusion priorities for each instruction passed in by parameter. ! The priorities are returned via pointer parameters. INSN is the instruction whose priorities need to be calculated. MAX_PRI is the maximum priority can be returned in any cases. *************** them: try the first ones in this list fi *** 34236,34250 **** parameter through which INSN's priority should be calculated and returned. ! Same FUSION_PRI should be returned for instructions which should be ! scheduled together. Different PRI should be returned for instructions with same FUSION_PRI. FUSION_PRI is the major sort ! key, PRI is the minor sort key. All instructions will be scheduled ! according to the two priorities. All priorities calculated should ! be between 0 (exclusive) and MAX_PRI (inclusive). To avoid false ! dependencies, FUSION_PRI of instructions which need to be scheduled ! together should be smaller than FUSION_PRI of irrelevant ! instructions. Given below example: --- 34665,34679 ---- parameter through which INSN's priority should be calculated and returned. ! Same FUSION_PRI should be returned for instructions which should ! be scheduled together. Different PRI should be returned for instructions with same FUSION_PRI. FUSION_PRI is the major sort ! key, PRI is the minor sort key. All instructions will be ! scheduled according to the two priorities. All priorities ! calculated should be between 0 (exclusive) and MAX_PRI ! (inclusive). To avoid false dependencies, FUSION_PRI of ! instructions which need to be scheduled together should be smaller ! than FUSION_PRI of irrelevant instructions. Given below example: *************** section", which holds initialized writab *** 34308,34341 **** which holds uninitialized data. Some systems have other kinds of sections. ! 'varasm.c' provides several well-known sections, such as ! 'text_section', 'data_section' and 'bss_section'. The normal way of ! controlling a 'FOO_section' variable is to define the associated ! 'FOO_SECTION_ASM_OP' macro, as described below. The macros are only ! read once, when 'varasm.c' initializes itself, so their values must be run-time constants. They may however depend on command-line flags. ! _Note:_ Some run-time files, such 'crtstuff.c', also make use of the ! 'FOO_SECTION_ASM_OP' macros, and expect them to be string literals. Some assemblers require a different string to be written every time a section is selected. If your assembler falls into this category, you ! should define the 'TARGET_ASM_INIT_SECTIONS' hook and use ! 'get_unnamed_section' to set up the sections. ! You must always create a 'text_section', either by defining ! 'TEXT_SECTION_ASM_OP' or by initializing 'text_section' in ! 'TARGET_ASM_INIT_SECTIONS'. The same is true of 'data_section' and ! 'DATA_SECTION_ASM_OP'. If you do not create a distinct ! 'readonly_data_section', the default is to reuse 'text_section'. ! All the other 'varasm.c' sections are optional, and are null if the target does not provide them. -- Macro: TEXT_SECTION_ASM_OP A C expression whose value is a string, including spacing, ! containing the assembler operation that should precede instructions ! and read-only data. Normally '"\t.text"' is right. -- Macro: HOT_TEXT_SECTION_NAME If defined, a C string constant for the name of the section --- 34737,34770 ---- which holds uninitialized data. Some systems have other kinds of sections. ! `varasm.c' provides several well-known sections, such as ! `text_section', `data_section' and `bss_section'. The normal way of ! controlling a `FOO_section' variable is to define the associated ! `FOO_SECTION_ASM_OP' macro, as described below. The macros are only ! read once, when `varasm.c' initializes itself, so their values must be run-time constants. They may however depend on command-line flags. ! _Note:_ Some run-time files, such `crtstuff.c', also make use of the ! `FOO_SECTION_ASM_OP' macros, and expect them to be string literals. Some assemblers require a different string to be written every time a section is selected. If your assembler falls into this category, you ! should define the `TARGET_ASM_INIT_SECTIONS' hook and use ! `get_unnamed_section' to set up the sections. ! You must always create a `text_section', either by defining ! `TEXT_SECTION_ASM_OP' or by initializing `text_section' in ! `TARGET_ASM_INIT_SECTIONS'. The same is true of `data_section' and ! `DATA_SECTION_ASM_OP'. If you do not create a distinct ! `readonly_data_section', the default is to reuse `text_section'. ! All the other `varasm.c' sections are optional, and are null if the target does not provide them. -- Macro: TEXT_SECTION_ASM_OP A C expression whose value is a string, including spacing, ! containing the assembler operation that should precede ! instructions and read-only data. Normally `"\t.text"' is right. -- Macro: HOT_TEXT_SECTION_NAME If defined, a C string constant for the name of the section *************** target does not provide them. *** 34350,34356 **** -- Macro: DATA_SECTION_ASM_OP A C expression whose value is a string, including spacing, containing the assembler operation to identify the following data ! as writable initialized data. Normally '"\t.data"' is right. -- Macro: SDATA_SECTION_ASM_OP If defined, a C expression whose value is a string, including --- 34779,34785 ---- -- Macro: DATA_SECTION_ASM_OP A C expression whose value is a string, including spacing, containing the assembler operation to identify the following data ! as writable initialized data. Normally `"\t.data"' is right. -- Macro: SDATA_SECTION_ASM_OP If defined, a C expression whose value is a string, including *************** target does not provide them. *** 34366,34374 **** If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the following data as uninitialized global data. If not defined, and ! 'ASM_OUTPUT_ALIGNED_BSS' not defined, uninitialized global data ! will be output in the data section if '-fno-common' is passed, ! otherwise 'ASM_OUTPUT_COMMON' will be used. -- Macro: SBSS_SECTION_ASM_OP If defined, a C expression whose value is a string, including --- 34795,34803 ---- If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the following data as uninitialized global data. If not defined, and ! `ASM_OUTPUT_ALIGNED_BSS' not defined, uninitialized global data ! will be output in the data section if `-fno-common' is passed, ! otherwise `ASM_OUTPUT_COMMON' will be used. -- Macro: SBSS_SECTION_ASM_OP If defined, a C expression whose value is a string, including *************** target does not provide them. *** 34378,34396 **** -- Macro: TLS_COMMON_ASM_OP If defined, a C expression whose value is a string containing the assembler operation to identify the following data as thread-local ! common data. The default is '".tls_common"'. -- Macro: TLS_SECTION_ASM_FLAG If defined, a C expression whose value is a character constant containing the flag used to mark a section as a TLS section. The ! default is ''T''. -- Macro: INIT_SECTION_ASM_OP If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the following data as initialization code. If not defined, GCC will assume such a section does not exist. This section has no ! corresponding 'init_section' variable; it is used entirely in runtime code. -- Macro: FINI_SECTION_ASM_OP --- 34807,34825 ---- -- Macro: TLS_COMMON_ASM_OP If defined, a C expression whose value is a string containing the assembler operation to identify the following data as thread-local ! common data. The default is `".tls_common"'. -- Macro: TLS_SECTION_ASM_FLAG If defined, a C expression whose value is a character constant containing the flag used to mark a section as a TLS section. The ! default is `'T''. -- Macro: INIT_SECTION_ASM_OP If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the following data as initialization code. If not defined, GCC will assume such a section does not exist. This section has no ! corresponding `init_section' variable; it is used entirely in runtime code. -- Macro: FINI_SECTION_ASM_OP *************** target does not provide them. *** 34398,34453 **** spacing, containing the assembler operation to identify the following data as finalization code. If not defined, GCC will assume such a section does not exist. This section has no ! corresponding 'fini_section' variable; it is used entirely in runtime code. -- Macro: INIT_ARRAY_SECTION_ASM_OP If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the ! following data as part of the '.init_array' (or equivalent) section. If not defined, GCC will assume such a section does not ! exist. Do not define both this macro and 'INIT_SECTION_ASM_OP'. -- Macro: FINI_ARRAY_SECTION_ASM_OP If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the ! following data as part of the '.fini_array' (or equivalent) section. If not defined, GCC will assume such a section does not ! exist. Do not define both this macro and 'FINI_SECTION_ASM_OP'. -- Macro: CRT_CALL_STATIC_FUNCTION (SECTION_OP, FUNCTION) If defined, an ASM statement that switches to a different section via SECTION_OP, calls FUNCTION, and switches back to the text ! section. This is used in 'crtstuff.c' if 'INIT_SECTION_ASM_OP' or ! 'FINI_SECTION_ASM_OP' to calls to initialization and finalization functions from the init and fini sections. By default, this macro ! uses a simple function call. Some ports need hand-crafted assembly ! code to avoid dependencies on registers initialized in the function ! prologue or to ensure that constant pools don't end up too far way ! in the text section. -- Macro: TARGET_LIBGCC_SDATA_SECTION If defined, a string which names the section into which small variables defined in crtstuff and libgcc should go. This is useful when the target has options for optimizing access to small data, ! and you want the crtstuff and libgcc routines to be conservative in ! what they expect of your application yet liberal in what your ! application expects. For example, for targets with a '.sdata' ! section (like MIPS), you could compile crtstuff with '-G 0' so that ! it doesn't require small data support from your application, but ! use this macro to put small data into '.sdata' so that your application can access these variables whether it uses small data or not. -- Macro: FORCE_CODE_SECTION_ALIGN If defined, an ASM statement that aligns a code section to some arbitrary boundary. This is used to force all fragments of the ! '.init' and '.fini' sections to have to same alignment and thus prevent the linker from having to add any padding. -- Macro: JUMP_TABLES_IN_TEXT_SECTION Define this macro to be an expression with a nonzero value if jump ! tables (for 'tablejump' insns) should be output in the text section, along with the assembler instructions. Otherwise, the readonly data section is used. --- 34827,34882 ---- spacing, containing the assembler operation to identify the following data as finalization code. If not defined, GCC will assume such a section does not exist. This section has no ! corresponding `fini_section' variable; it is used entirely in runtime code. -- Macro: INIT_ARRAY_SECTION_ASM_OP If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the ! following data as part of the `.init_array' (or equivalent) section. If not defined, GCC will assume such a section does not ! exist. Do not define both this macro and `INIT_SECTION_ASM_OP'. -- Macro: FINI_ARRAY_SECTION_ASM_OP If defined, a C expression whose value is a string, including spacing, containing the assembler operation to identify the ! following data as part of the `.fini_array' (or equivalent) section. If not defined, GCC will assume such a section does not ! exist. Do not define both this macro and `FINI_SECTION_ASM_OP'. -- Macro: CRT_CALL_STATIC_FUNCTION (SECTION_OP, FUNCTION) If defined, an ASM statement that switches to a different section via SECTION_OP, calls FUNCTION, and switches back to the text ! section. This is used in `crtstuff.c' if `INIT_SECTION_ASM_OP' or ! `FINI_SECTION_ASM_OP' to calls to initialization and finalization functions from the init and fini sections. By default, this macro ! uses a simple function call. Some ports need hand-crafted ! assembly code to avoid dependencies on registers initialized in ! the function prologue or to ensure that constant pools don't end ! up too far way in the text section. -- Macro: TARGET_LIBGCC_SDATA_SECTION If defined, a string which names the section into which small variables defined in crtstuff and libgcc should go. This is useful when the target has options for optimizing access to small data, ! and you want the crtstuff and libgcc routines to be conservative ! in what they expect of your application yet liberal in what your ! application expects. For example, for targets with a `.sdata' ! section (like MIPS), you could compile crtstuff with `-G 0' so ! that it doesn't require small data support from your application, ! but use this macro to put small data into `.sdata' so that your application can access these variables whether it uses small data or not. -- Macro: FORCE_CODE_SECTION_ALIGN If defined, an ASM statement that aligns a code section to some arbitrary boundary. This is used to force all fragments of the ! `.init' and `.fini' sections to have to same alignment and thus prevent the linker from having to add any padding. -- Macro: JUMP_TABLES_IN_TEXT_SECTION Define this macro to be an expression with a nonzero value if jump ! tables (for `tablejump' insns) should be output in the text section, along with the assembler instructions. Otherwise, the readonly data section is used. *************** target does not provide them. *** 34456,34463 **** -- Target Hook: void TARGET_ASM_INIT_SECTIONS (void) Define this hook if you need to do something special to set up the ! 'varasm.c' sections, or if your target has some special sections of ! its own that you need to create. GCC calls this hook after processing the command line, but before writing any assembly code, and before calling any of the --- 34885,34892 ---- -- Target Hook: void TARGET_ASM_INIT_SECTIONS (void) Define this hook if you need to do something special to set up the ! `varasm.c' sections, or if your target has some special sections ! of its own that you need to create. GCC calls this hook after processing the command line, but before writing any assembly code, and before calling any of the *************** target does not provide them. *** 34469,34550 **** should be placed in a read-write section; bit 0 should be set if local relocations should be placed in a read-write section. ! The default version of this function returns 3 when '-fpic' is in effect, and 0 otherwise. The hook is typically redefined when the target cannot support (some kinds of) dynamic relocations in read-only sections even in executables. -- Target Hook: section * TARGET_ASM_SELECT_SECTION (tree EXP, int RELOC, unsigned HOST_WIDE_INT ALIGN) ! Return the section into which EXP should be placed. You can assume ! that EXP is either a 'VAR_DECL' node or a constant of some sort. ! RELOC indicates whether the initial value of EXP requires link-time ! relocations. Bit 0 is set when variable contains local relocations ! only, while bit 1 is set for global relocations. ALIGN is the ! constant alignment in bits. The default version of this function takes care of putting ! read-only variables in 'readonly_data_section'. See also USE_SELECT_SECTION_FOR_FUNCTIONS. -- Macro: USE_SELECT_SECTION_FOR_FUNCTIONS Define this macro if you wish TARGET_ASM_SELECT_SECTION to be ! called for 'FUNCTION_DECL's as well as for variables and constants. ! In the case of a 'FUNCTION_DECL', RELOC will be zero if the ! function has been determined to be likely to be called, and nonzero ! if it is unlikely to be called. -- Target Hook: void TARGET_ASM_UNIQUE_SECTION (tree DECL, int RELOC) ! Build up a unique section name, expressed as a 'STRING_CST' node, ! and assign it to 'DECL_SECTION_NAME (DECL)'. As with ! 'TARGET_ASM_SELECT_SECTION', RELOC indicates whether the initial value of EXP requires link-time relocations. The default version of this function appends the symbol name to the ELF section name that would normally be used for the symbol. For ! example, the function 'foo' would be placed in '.text.foo'. Whatever the actual target object format, this is often good enough. -- Target Hook: section * TARGET_ASM_FUNCTION_RODATA_SECTION (tree DECL) ! Return the readonly data section associated with 'DECL_SECTION_NAME ! (DECL)'. The default version of this function selects ! '.gnu.linkonce.r.name' if the function's section is ! '.gnu.linkonce.t.name', '.rodata.name' if function is in ! '.text.name', and the normal readonly-data section otherwise. -- Target Hook: const char * TARGET_ASM_MERGEABLE_RODATA_PREFIX ! Usually, the compiler uses the prefix '".rodata"' to construct section names for mergeable constant data. Define this macro to override the string if a different section name should be used. -- Target Hook: section * TARGET_ASM_TM_CLONE_TABLE_SECTION (void) Return the section that should be used for transactional memory ! clone tables. -- Target Hook: section * TARGET_ASM_SELECT_RTX_SECTION (machine_mode MODE, rtx X, unsigned HOST_WIDE_INT ALIGN) ! Return the section into which a constant X, of mode MODE, should be ! placed. You can assume that X is some kind of constant in RTL. ! The argument MODE is redundant except in the case of a 'const_int' rtx. ALIGN is the constant alignment in bits. The default version of this function takes care of putting symbolic ! constants in 'flag_pic' mode in 'data_section' and everything else ! in 'readonly_data_section'. ! -- Target Hook: tree TARGET_MANGLE_DECL_ASSEMBLER_NAME (tree DECL, tree ! ID) Define this hook if you need to postprocess the assembler name ! generated by target-independent code. The ID provided to this hook ! will be the computed name (e.g., the macro 'DECL_NAME' of the DECL ! in C, or the mangled name of the DECL in C++). The return value of ! the hook is an 'IDENTIFIER_NODE' for the appropriate mangled name ! on your target system. The default implementation of this hook ! just returns the ID provided. -- Target Hook: void TARGET_ENCODE_SECTION_INFO (tree DECL, rtx RTL, int NEW_DECL_P) --- 34898,34979 ---- should be placed in a read-write section; bit 0 should be set if local relocations should be placed in a read-write section. ! The default version of this function returns 3 when `-fpic' is in effect, and 0 otherwise. The hook is typically redefined when the target cannot support (some kinds of) dynamic relocations in read-only sections even in executables. -- Target Hook: section * TARGET_ASM_SELECT_SECTION (tree EXP, int RELOC, unsigned HOST_WIDE_INT ALIGN) ! Return the section into which EXP should be placed. You can ! assume that EXP is either a `VAR_DECL' node or a constant of some ! sort. RELOC indicates whether the initial value of EXP requires ! link-time relocations. Bit 0 is set when variable contains local ! relocations only, while bit 1 is set for global relocations. ! ALIGN is the constant alignment in bits. The default version of this function takes care of putting ! read-only variables in `readonly_data_section'. See also USE_SELECT_SECTION_FOR_FUNCTIONS. -- Macro: USE_SELECT_SECTION_FOR_FUNCTIONS Define this macro if you wish TARGET_ASM_SELECT_SECTION to be ! called for `FUNCTION_DECL's as well as for variables and constants. ! In the case of a `FUNCTION_DECL', RELOC will be zero if the ! function has been determined to be likely to be called, and ! nonzero if it is unlikely to be called. -- Target Hook: void TARGET_ASM_UNIQUE_SECTION (tree DECL, int RELOC) ! Build up a unique section name, expressed as a `STRING_CST' node, ! and assign it to `DECL_SECTION_NAME (DECL)'. As with ! `TARGET_ASM_SELECT_SECTION', RELOC indicates whether the initial value of EXP requires link-time relocations. The default version of this function appends the symbol name to the ELF section name that would normally be used for the symbol. For ! example, the function `foo' would be placed in `.text.foo'. Whatever the actual target object format, this is often good enough. -- Target Hook: section * TARGET_ASM_FUNCTION_RODATA_SECTION (tree DECL) ! Return the readonly data section associated with ! `DECL_SECTION_NAME (DECL)'. The default version of this function ! selects `.gnu.linkonce.r.name' if the function's section is ! `.gnu.linkonce.t.name', `.rodata.name' if function is in ! `.text.name', and the normal readonly-data section otherwise. -- Target Hook: const char * TARGET_ASM_MERGEABLE_RODATA_PREFIX ! Usually, the compiler uses the prefix `".rodata"' to construct section names for mergeable constant data. Define this macro to override the string if a different section name should be used. -- Target Hook: section * TARGET_ASM_TM_CLONE_TABLE_SECTION (void) Return the section that should be used for transactional memory ! clone tables. -- Target Hook: section * TARGET_ASM_SELECT_RTX_SECTION (machine_mode MODE, rtx X, unsigned HOST_WIDE_INT ALIGN) ! Return the section into which a constant X, of mode MODE, should ! be placed. You can assume that X is some kind of constant in RTL. ! The argument MODE is redundant except in the case of a `const_int' rtx. ALIGN is the constant alignment in bits. The default version of this function takes care of putting symbolic ! constants in `flag_pic' mode in `data_section' and everything else ! in `readonly_data_section'. ! -- Target Hook: tree TARGET_MANGLE_DECL_ASSEMBLER_NAME (tree DECL, ! tree ID) Define this hook if you need to postprocess the assembler name ! generated by target-independent code. The ID provided to this ! hook will be the computed name (e.g., the macro `DECL_NAME' of the ! DECL in C, or the mangled name of the DECL in C++). The return ! value of the hook is an `IDENTIFIER_NODE' for the appropriate ! mangled name on your target system. The default implementation of ! this hook just returns the ID provided. -- Target Hook: void TARGET_ENCODE_SECTION_INFO (tree DECL, rtx RTL, int NEW_DECL_P) *************** target does not provide them. *** 34555,34616 **** The hook is executed immediately after rtl has been created for DECL, which may be a variable or function declaration or an entry in the constant pool. In either case, RTL is the rtl in question. ! Do _not_ use 'DECL_RTL (DECL)' in this hook; that field may not have been initialized yet. In the case of a constant, it is safe to assume that the rtl is a ! 'mem' whose address is a 'symbol_ref'. Most decls will also have this form, but that is not guaranteed. Global register variables, ! for instance, will have a 'reg' for their rtl. (Normally the right ! thing to do with such unusual rtl is leave it alone.) ! The NEW_DECL_P argument will be true if this is the first time that ! 'TARGET_ENCODE_SECTION_INFO' has been invoked on this decl. It ! will be false for subsequent invocations, which will happen for duplicate declarations. Whether or not anything must be done for the duplicate declaration depends on whether the hook examines ! 'DECL_ATTRIBUTES'. NEW_DECL_P is always true when the hook is called for a constant. The usual thing for this hook to do is to record flags in the ! 'symbol_ref', using 'SYMBOL_REF_FLAG' or 'SYMBOL_REF_FLAGS'. Historically, the name string was modified if it was necessary to encode more than one bit of information, but this practice is now ! discouraged; use 'SYMBOL_REF_FLAGS'. ! The default definition of this hook, 'default_encode_section_info' ! in 'varasm.c', sets a number of commonly-useful bits in ! 'SYMBOL_REF_FLAGS'. Check whether the default does what you need before overriding it. -- Target Hook: const char * TARGET_STRIP_NAME_ENCODING (const char *NAME) ! Decode NAME and return the real name part, sans the characters that ! 'TARGET_ENCODE_SECTION_INFO' may have added. -- Target Hook: bool TARGET_IN_SMALL_DATA_P (const_tree EXP) Returns true if EXP should be placed into a "small data" section. The default version of this hook always returns false. -- Target Hook: bool TARGET_HAVE_SRODATA_SECTION ! Contains the value true if the target places read-only "small data" ! into a separate section. The default value is false. -- Target Hook: bool TARGET_PROFILE_BEFORE_PROLOGUE (void) It returns true if target wants profile code emitted before prologue. The default version of this hook use the target macro ! 'PROFILE_BEFORE_PROLOGUE'. -- Target Hook: bool TARGET_BINDS_LOCAL_P (const_tree EXP) ! Returns true if EXP names an object for which name resolution rules ! must resolve to the current "module" (dynamic shared library or ! executable image). The default version of this hook implements the name resolution ! rules for ELF, which has a looser model of global name binding than ! other currently supported object file formats. -- Target Hook: bool TARGET_HAVE_TLS Contains the value true if the target supports thread-local --- 34984,35045 ---- The hook is executed immediately after rtl has been created for DECL, which may be a variable or function declaration or an entry in the constant pool. In either case, RTL is the rtl in question. ! Do _not_ use `DECL_RTL (DECL)' in this hook; that field may not have been initialized yet. In the case of a constant, it is safe to assume that the rtl is a ! `mem' whose address is a `symbol_ref'. Most decls will also have this form, but that is not guaranteed. Global register variables, ! for instance, will have a `reg' for their rtl. (Normally the ! right thing to do with such unusual rtl is leave it alone.) ! The NEW_DECL_P argument will be true if this is the first time ! that `TARGET_ENCODE_SECTION_INFO' has been invoked on this decl. ! It will be false for subsequent invocations, which will happen for duplicate declarations. Whether or not anything must be done for the duplicate declaration depends on whether the hook examines ! `DECL_ATTRIBUTES'. NEW_DECL_P is always true when the hook is called for a constant. The usual thing for this hook to do is to record flags in the ! `symbol_ref', using `SYMBOL_REF_FLAG' or `SYMBOL_REF_FLAGS'. Historically, the name string was modified if it was necessary to encode more than one bit of information, but this practice is now ! discouraged; use `SYMBOL_REF_FLAGS'. ! The default definition of this hook, `default_encode_section_info' ! in `varasm.c', sets a number of commonly-useful bits in ! `SYMBOL_REF_FLAGS'. Check whether the default does what you need before overriding it. -- Target Hook: const char * TARGET_STRIP_NAME_ENCODING (const char *NAME) ! Decode NAME and return the real name part, sans the characters ! that `TARGET_ENCODE_SECTION_INFO' may have added. -- Target Hook: bool TARGET_IN_SMALL_DATA_P (const_tree EXP) Returns true if EXP should be placed into a "small data" section. The default version of this hook always returns false. -- Target Hook: bool TARGET_HAVE_SRODATA_SECTION ! Contains the value true if the target places read-only "small ! data" into a separate section. The default value is false. -- Target Hook: bool TARGET_PROFILE_BEFORE_PROLOGUE (void) It returns true if target wants profile code emitted before prologue. The default version of this hook use the target macro ! `PROFILE_BEFORE_PROLOGUE'. -- Target Hook: bool TARGET_BINDS_LOCAL_P (const_tree EXP) ! Returns true if EXP names an object for which name resolution ! rules must resolve to the current "module" (dynamic shared library ! or executable image). The default version of this hook implements the name resolution ! rules for ELF, which has a looser model of global name binding ! than other currently supported object file formats. -- Target Hook: bool TARGET_HAVE_TLS Contains the value true if the target supports thread-local *************** File: gccint.info, Node: PIC, Next: As *** 34625,34633 **** This section describes macros that help implement generation of position independent code. Simply defining these macros is not enough to generate valid PIC; you must also add support to the hook ! 'TARGET_LEGITIMATE_ADDRESS_P' and to the macro 'PRINT_OPERAND_ADDRESS', ! as well as 'LEGITIMIZE_ADDRESS'. You must modify the definition of ! 'movsi' to do something appropriate when the source operand contains a symbolic address. You may also need to alter the handling of switch statements so that they use relative addresses. --- 35054,35062 ---- This section describes macros that help implement generation of position independent code. Simply defining these macros is not enough to generate valid PIC; you must also add support to the hook ! `TARGET_LEGITIMATE_ADDRESS_P' and to the macro `PRINT_OPERAND_ADDRESS', ! as well as `LEGITIMIZE_ADDRESS'. You must modify the definition of ! `movsi' to do something appropriate when the source operand contains a symbolic address. You may also need to alter the handling of switch statements so that they use relative addresses. *************** statements so that they use relative add *** 34639,34659 **** once, as with the stack pointer and frame pointer registers. If this macro is not defined, it is up to the machine-dependent files to allocate such a register (if necessary). Note that this ! register must be fixed when in use (e.g. when 'flag_pic' is true). -- Macro: PIC_OFFSET_TABLE_REG_CALL_CLOBBERED A C expression that is nonzero if the register defined by ! 'PIC_OFFSET_TABLE_REGNUM' is clobbered by calls. If not defined, the default is zero. Do not define this macro if ! 'PIC_OFFSET_TABLE_REGNUM' is not defined. -- Macro: LEGITIMATE_PIC_OPERAND_P (X) A C expression that is nonzero if X is a legitimate immediate operand on the target machine when generating position independent ! code. You can assume that X satisfies 'CONSTANT_P', so you need not check this. You can also assume FLAG_PIC is true, so you need not check it either. You need not define this macro if all ! constants (including 'SYMBOL_REF') can be immediate operands when generating position independent code.  --- 35068,35088 ---- once, as with the stack pointer and frame pointer registers. If this macro is not defined, it is up to the machine-dependent files to allocate such a register (if necessary). Note that this ! register must be fixed when in use (e.g. when `flag_pic' is true). -- Macro: PIC_OFFSET_TABLE_REG_CALL_CLOBBERED A C expression that is nonzero if the register defined by ! `PIC_OFFSET_TABLE_REGNUM' is clobbered by calls. If not defined, the default is zero. Do not define this macro if ! `PIC_OFFSET_TABLE_REGNUM' is not defined. -- Macro: LEGITIMATE_PIC_OPERAND_P (X) A C expression that is nonzero if X is a legitimate immediate operand on the target machine when generating position independent ! code. You can assume that X satisfies `CONSTANT_P', so you need not check this. You can also assume FLAG_PIC is true, so you need not check it either. You need not define this macro if all ! constants (including `SYMBOL_REF') can be immediate operands when generating position independent code.  *************** File: gccint.info, Node: File Framework *** 34691,34746 **** This describes the overall framework of an assembly file. -- Target Hook: void TARGET_ASM_FILE_START (void) ! Output to 'asm_out_file' any text which the assembler expects to find at the beginning of a file. The default behavior is controlled by two flags, documented below. Unless your target's ! assembler is quite unusual, if you override the default, you should ! call 'default_file_start' at some point in your target hook. This ! lets other target files rely on these variables. -- Target Hook: bool TARGET_ASM_FILE_START_APP_OFF ! If this flag is true, the text of the macro 'ASM_APP_OFF' will be printed as the very first line in the assembly file, unless ! '-fverbose-asm' is in effect. (If that macro has been defined to the empty string, this variable has no effect.) With the normal ! definition of 'ASM_APP_OFF', the effect is to notify the GNU assembler that it need not bother stripping comments or extra whitespace from its input. This allows it to work a bit faster. The default is false. You should not set it to true unless you ! have verified that your port does not generate any extra whitespace ! or comments that will cause GAS to issue errors in NO_APP mode. -- Target Hook: bool TARGET_ASM_FILE_START_FILE_DIRECTIVE ! If this flag is true, 'output_file_directive' will be called for ! the primary source file, immediately after printing 'ASM_APP_OFF' (if that is enabled). Most ELF assemblers expect this to be done. The default is false. -- Target Hook: void TARGET_ASM_FILE_END (void) ! Output to 'asm_out_file' any text which the assembler expects to find at the end of a file. The default is to output nothing. -- Function: void file_end_indicate_exec_stack () ! Some systems use a common convention, the '.note.GNU-stack' special ! section, to indicate whether or not an object file relies on the ! stack being executable. If your system uses this convention, you ! should define 'TARGET_ASM_FILE_END' to this function. If you need ! to do other things in that hook, have your hook function call this ! function. -- Target Hook: void TARGET_ASM_LTO_START (void) ! Output to 'asm_out_file' any text which the assembler expects to find at the start of an LTO section. The default is to output nothing. -- Target Hook: void TARGET_ASM_LTO_END (void) ! Output to 'asm_out_file' any text which the assembler expects to find at the end of an LTO section. The default is to output nothing. -- Target Hook: void TARGET_ASM_CODE_END (void) ! Output to 'asm_out_file' any text which is needed before emitting unwind info and debug info at the end of a file. Some targets emit here PIC setup thunks that cannot be emitted at the end of file, because they couldn't have unwind info then. The default is to --- 35120,35176 ---- This describes the overall framework of an assembly file. -- Target Hook: void TARGET_ASM_FILE_START (void) ! Output to `asm_out_file' any text which the assembler expects to find at the beginning of a file. The default behavior is controlled by two flags, documented below. Unless your target's ! assembler is quite unusual, if you override the default, you ! should call `default_file_start' at some point in your target ! hook. This lets other target files rely on these variables. -- Target Hook: bool TARGET_ASM_FILE_START_APP_OFF ! If this flag is true, the text of the macro `ASM_APP_OFF' will be printed as the very first line in the assembly file, unless ! `-fverbose-asm' is in effect. (If that macro has been defined to the empty string, this variable has no effect.) With the normal ! definition of `ASM_APP_OFF', the effect is to notify the GNU assembler that it need not bother stripping comments or extra whitespace from its input. This allows it to work a bit faster. The default is false. You should not set it to true unless you ! have verified that your port does not generate any extra ! whitespace or comments that will cause GAS to issue errors in ! NO_APP mode. -- Target Hook: bool TARGET_ASM_FILE_START_FILE_DIRECTIVE ! If this flag is true, `output_file_directive' will be called for ! the primary source file, immediately after printing `ASM_APP_OFF' (if that is enabled). Most ELF assemblers expect this to be done. The default is false. -- Target Hook: void TARGET_ASM_FILE_END (void) ! Output to `asm_out_file' any text which the assembler expects to find at the end of a file. The default is to output nothing. -- Function: void file_end_indicate_exec_stack () ! Some systems use a common convention, the `.note.GNU-stack' ! special section, to indicate whether or not an object file relies ! on the stack being executable. If your system uses this ! convention, you should define `TARGET_ASM_FILE_END' to this ! function. If you need to do other things in that hook, have your ! hook function call this function. -- Target Hook: void TARGET_ASM_LTO_START (void) ! Output to `asm_out_file' any text which the assembler expects to find at the start of an LTO section. The default is to output nothing. -- Target Hook: void TARGET_ASM_LTO_END (void) ! Output to `asm_out_file' any text which the assembler expects to find at the end of an LTO section. The default is to output nothing. -- Target Hook: void TARGET_ASM_CODE_END (void) ! Output to `asm_out_file' any text which is needed before emitting unwind info and debug info at the end of a file. Some targets emit here PIC setup thunks that cannot be emitted at the end of file, because they couldn't have unwind info then. The default is to *************** This describes the overall framework of *** 34748,34767 **** -- Macro: ASM_COMMENT_START A C string constant describing how to begin a comment in the target ! assembler language. The compiler assumes that the comment will end ! at the end of the line. -- Macro: ASM_APP_ON ! A C string constant for text to be output before each 'asm' ! statement or group of consecutive ones. Normally this is '"#APP"', ! which is a comment that has no effect on most assemblers but tells ! the GNU assembler that it must check the lines that follow for all ! valid assembler constructs. -- Macro: ASM_APP_OFF ! A C string constant for text to be output after each 'asm' statement or group of consecutive ones. Normally this is ! '"#NO_APP"', which tells the GNU assembler to resume making the time-saving assumptions that are valid for ordinary compiler output. --- 35178,35197 ---- -- Macro: ASM_COMMENT_START A C string constant describing how to begin a comment in the target ! assembler language. The compiler assumes that the comment will ! end at the end of the line. -- Macro: ASM_APP_ON ! A C string constant for text to be output before each `asm' ! statement or group of consecutive ones. Normally this is ! `"#APP"', which is a comment that has no effect on most assemblers ! but tells the GNU assembler that it must check the lines that ! follow for all valid assembler constructs. -- Macro: ASM_APP_OFF ! A C string constant for text to be output after each `asm' statement or group of consecutive ones. Normally this is ! `"#NO_APP"', which tells the GNU assembler to resume making the time-saving assumptions that are valid for ordinary compiler output. *************** This describes the overall framework of *** 34779,34815 **** indicates that filename NAME is the current source file to the stdio stream FILE. ! This target hook need not be defined if the standard form of output ! for the file format in use is appropriate. -- Target Hook: void TARGET_ASM_OUTPUT_IDENT (const char *NAME) ! Output a string based on NAME, suitable for the '#ident' directive, ! or the equivalent directive or pragma in non-C-family languages. ! If this hook is not defined, nothing is output for the '#ident' ! directive. -- Macro: OUTPUT_QUOTED_STRING (STREAM, STRING) A C statement to output the string STRING to the stdio stream ! STREAM. If you do not call the function 'output_quoted_string' in ! your config files, GCC will only call it to output filenames to the ! assembler source. So you can use it to canonicalize the format of ! the filename using this macro. -- Target Hook: void TARGET_ASM_NAMED_SECTION (const char *NAME, unsigned int FLAGS, tree DECL) Output assembly directives to switch to section NAME. The section should have attributes as specified by FLAGS, which is a bit mask ! of the 'SECTION_*' flags defined in 'output.h'. If DECL is ! non-NULL, it is the 'VAR_DECL' or 'FUNCTION_DECL' with which this section is associated. -- Target Hook: section * TARGET_ASM_FUNCTION_SECTION (tree DECL, enum node_frequency FREQ, bool STARTUP, bool EXIT) ! Return preferred text (sub)section for function DECL. Main purpose ! of this function is to separate cold, normal and hot functions. ! STARTUP is true when function is known to be used only at startup ! (from static constructors or it is 'main()'). EXIT is true when ! function is known to be used only at exit (from static destructors). Return NULL if function should go to default text section. --- 35209,35245 ---- indicates that filename NAME is the current source file to the stdio stream FILE. ! This target hook need not be defined if the standard form of ! output for the file format in use is appropriate. -- Target Hook: void TARGET_ASM_OUTPUT_IDENT (const char *NAME) ! Output a string based on NAME, suitable for the `#ident' ! directive, or the equivalent directive or pragma in non-C-family ! languages. If this hook is not defined, nothing is output for the ! `#ident' directive. -- Macro: OUTPUT_QUOTED_STRING (STREAM, STRING) A C statement to output the string STRING to the stdio stream ! STREAM. If you do not call the function `output_quoted_string' in ! your config files, GCC will only call it to output filenames to ! the assembler source. So you can use it to canonicalize the format ! of the filename using this macro. -- Target Hook: void TARGET_ASM_NAMED_SECTION (const char *NAME, unsigned int FLAGS, tree DECL) Output assembly directives to switch to section NAME. The section should have attributes as specified by FLAGS, which is a bit mask ! of the `SECTION_*' flags defined in `output.h'. If DECL is ! non-NULL, it is the `VAR_DECL' or `FUNCTION_DECL' with which this section is associated. -- Target Hook: section * TARGET_ASM_FUNCTION_SECTION (tree DECL, enum node_frequency FREQ, bool STARTUP, bool EXIT) ! Return preferred text (sub)section for function DECL. Main ! purpose of this function is to separate cold, normal and hot ! functions. STARTUP is true when function is known to be used only ! at startup (from static constructors or it is `main()'). EXIT is ! true when function is known to be used only at exit (from static destructors). Return NULL if function should go to default text section. *************** This describes the overall framework of *** 34817,34848 **** *FILE, tree DECL, bool NEW_IS_COLD) Used by the target to emit any assembler directives or additional labels needed when a function is partitioned between different ! sections. Output should be written to FILE. The function decl is ! available as DECL and the new section is 'cold' if NEW_IS_COLD is ! 'true'. -- Common Target Hook: bool TARGET_HAVE_NAMED_SECTIONS This flag is true if the target supports ! 'TARGET_ASM_NAMED_SECTION'. It must not be modified by command-line option processing. -- Target Hook: bool TARGET_HAVE_SWITCHABLE_BSS_SECTIONS This flag is true if we can create zeroed data by switching to a ! BSS section and then using 'ASM_OUTPUT_SKIP' to allocate the space. This is true on most ELF targets. -- Target Hook: unsigned int TARGET_SECTION_TYPE_FLAGS (tree DECL, const char *NAME, int RELOC) Choose a set of section attributes for use by ! 'TARGET_ASM_NAMED_SECTION' based on a variable or function decl, a section name, and whether or not the declaration's initializer may contain runtime relocations. DECL may be null, in which case read-write data should be assumed. The default version of this function handles choosing code vs data, ! read-only vs read-write data, and 'flag_pic'. You should only need ! to override this if your target has special flags that might be set ! via '__attribute__'. -- Target Hook: int TARGET_ASM_RECORD_GCC_SWITCHES (print_switch_type TYPE, const char *TEXT) --- 35247,35278 ---- *FILE, tree DECL, bool NEW_IS_COLD) Used by the target to emit any assembler directives or additional labels needed when a function is partitioned between different ! sections. Output should be written to FILE. The function decl ! is available as DECL and the new section is `cold' if NEW_IS_COLD ! is `true'. -- Common Target Hook: bool TARGET_HAVE_NAMED_SECTIONS This flag is true if the target supports ! `TARGET_ASM_NAMED_SECTION'. It must not be modified by command-line option processing. -- Target Hook: bool TARGET_HAVE_SWITCHABLE_BSS_SECTIONS This flag is true if we can create zeroed data by switching to a ! BSS section and then using `ASM_OUTPUT_SKIP' to allocate the space. This is true on most ELF targets. -- Target Hook: unsigned int TARGET_SECTION_TYPE_FLAGS (tree DECL, const char *NAME, int RELOC) Choose a set of section attributes for use by ! `TARGET_ASM_NAMED_SECTION' based on a variable or function decl, a section name, and whether or not the declaration's initializer may contain runtime relocations. DECL may be null, in which case read-write data should be assumed. The default version of this function handles choosing code vs data, ! read-only vs read-write data, and `flag_pic'. You should only ! need to override this if your target has special flags that might ! be set via `__attribute__'. -- Target Hook: int TARGET_ASM_RECORD_GCC_SWITCHES (print_switch_type TYPE, const char *TEXT) *************** This describes the overall framework of *** 34851,34882 **** are enabled. The TYPE argument specifies what is being recorded. It can take the following values: ! 'SWITCH_TYPE_PASSED' TEXT is a command line switch that has been set by the user. ! 'SWITCH_TYPE_ENABLED' TEXT is an option which has been enabled. This might be as a direct result of a command line switch, or because it is enabled by default or because it has been enabled as a side effect of a different command line switch. For example, the ! '-O2' switch enables various different individual optimization ! passes. ! 'SWITCH_TYPE_DESCRIPTIVE' TEXT is either NULL or some descriptive text which should be ignored. If TEXT is NULL then it is being used to warn the target hook that either recording is starting or ending. The first time TYPE is SWITCH_TYPE_DESCRIPTIVE and TEXT is NULL, ! the warning is for start up and the second time the warning is ! for wind down. This feature is to allow the target hook to ! make any necessary preparations before it starts to record switches and to perform any necessary tidying up after it has finished recording switches. ! 'SWITCH_TYPE_LINE_START' This option can be ignored by this target hook. ! 'SWITCH_TYPE_LINE_END' This option can be ignored by this target hook. The hook's return value must be zero. Other return values may be --- 35281,35312 ---- are enabled. The TYPE argument specifies what is being recorded. It can take the following values: ! `SWITCH_TYPE_PASSED' TEXT is a command line switch that has been set by the user. ! `SWITCH_TYPE_ENABLED' TEXT is an option which has been enabled. This might be as a direct result of a command line switch, or because it is enabled by default or because it has been enabled as a side effect of a different command line switch. For example, the ! `-O2' switch enables various different individual ! optimization passes. ! `SWITCH_TYPE_DESCRIPTIVE' TEXT is either NULL or some descriptive text which should be ignored. If TEXT is NULL then it is being used to warn the target hook that either recording is starting or ending. The first time TYPE is SWITCH_TYPE_DESCRIPTIVE and TEXT is NULL, ! the warning is for start up and the second time the warning ! is for wind down. This feature is to allow the target hook ! to make any necessary preparations before it starts to record switches and to perform any necessary tidying up after it has finished recording switches. ! `SWITCH_TYPE_LINE_START' This option can be ignored by this target hook. ! `SWITCH_TYPE_LINE_END' This option can be ignored by this target hook. The hook's return value must be zero. Other return values may be *************** This describes the overall framework of *** 34887,34897 **** it records the switches as ASCII text inside a new, string mergeable section in the assembler output file. The name of the new section is provided by the ! 'TARGET_ASM_RECORD_GCC_SWITCHES_SECTION' target hook. -- Target Hook: const char * TARGET_ASM_RECORD_GCC_SWITCHES_SECTION This is the name of the section that will be created by the example ! ELF implementation of the 'TARGET_ASM_RECORD_GCC_SWITCHES' target hook.  --- 35317,35327 ---- it records the switches as ASCII text inside a new, string mergeable section in the assembler output file. The name of the new section is provided by the ! `TARGET_ASM_RECORD_GCC_SWITCHES_SECTION' target hook. -- Target Hook: const char * TARGET_ASM_RECORD_GCC_SWITCHES_SECTION This is the name of the section that will be created by the example ! ELF implementation of the `TARGET_ASM_RECORD_GCC_SWITCHES' target hook.  *************** File: gccint.info, Node: Data Output, *** 34910,34919 **** -- Target Hook: const char * TARGET_ASM_UNALIGNED_DI_OP -- Target Hook: const char * TARGET_ASM_UNALIGNED_TI_OP These hooks specify assembly directives for creating certain kinds ! of integer object. The 'TARGET_ASM_BYTE_OP' directive creates a ! byte-sized object, the 'TARGET_ASM_ALIGNED_HI_OP' one creates an aligned two-byte object, and so on. Any of the hooks may be ! 'NULL', indicating that no suitable directive is available. The compiler will print these strings at the start of a new line, followed immediately by the object's initial value. In most cases, --- 35340,35349 ---- -- Target Hook: const char * TARGET_ASM_UNALIGNED_DI_OP -- Target Hook: const char * TARGET_ASM_UNALIGNED_TI_OP These hooks specify assembly directives for creating certain kinds ! of integer object. The `TARGET_ASM_BYTE_OP' directive creates a ! byte-sized object, the `TARGET_ASM_ALIGNED_HI_OP' one creates an aligned two-byte object, and so on. Any of the hooks may be ! `NULL', indicating that no suitable directive is available. The compiler will print these strings at the start of a new line, followed immediately by the object's initial value. In most cases, *************** File: gccint.info, Node: Data Output, *** 34921,34936 **** -- Target Hook: bool TARGET_ASM_INTEGER (rtx X, unsigned int SIZE, int ALIGNED_P) ! The 'assemble_integer' function uses this hook to output an integer ! object. X is the object's value, SIZE is its size in bytes and ! ALIGNED_P indicates whether it is aligned. The function should ! return 'true' if it was able to output the object. If it returns ! false, 'assemble_integer' will try to split the object into smaller ! parts. The default implementation of this hook will use the ! 'TARGET_ASM_BYTE_OP' family of strings, returning 'false' when the ! relevant string is 'NULL'. -- Target Hook: void TARGET_ASM_DECL_END (void) Define this hook if the target assembler requires a special marker --- 35351,35366 ---- -- Target Hook: bool TARGET_ASM_INTEGER (rtx X, unsigned int SIZE, int ALIGNED_P) ! The `assemble_integer' function uses this hook to output an ! integer object. X is the object's value, SIZE is its size in ! bytes and ALIGNED_P indicates whether it is aligned. The function ! should return `true' if it was able to output the object. If it ! returns false, `assemble_integer' will try to split the object ! into smaller parts. The default implementation of this hook will use the ! `TARGET_ASM_BYTE_OP' family of strings, returning `false' when the ! relevant string is `NULL'. -- Target Hook: void TARGET_ASM_DECL_END (void) Define this hook if the target assembler requires a special marker *************** File: gccint.info, Node: Data Output, *** 34938,34972 **** -- Target Hook: bool TARGET_ASM_OUTPUT_ADDR_CONST_EXTRA (FILE *FILE, rtx X) ! A target hook to recognize RTX patterns that 'output_addr_const' can't deal with, and output assembly code to FILE corresponding to the pattern X. This may be used to allow machine-dependent ! 'UNSPEC's to appear within constants. If target hook fails to recognize a pattern, it must return ! 'false', so that a standard error message is printed. If it prints ! an error message itself, by calling, for example, ! 'output_operand_lossage', it may just return 'true'. -- Macro: ASM_OUTPUT_ASCII (STREAM, PTR, LEN) A C statement to output to the stdio stream STREAM an assembler instruction to assemble a string constant containing the LEN bytes ! at PTR. PTR will be a C expression of type 'char *' and LEN a C ! expression of type 'int'. ! If the assembler has a '.ascii' pseudo-op as found in the Berkeley ! Unix assembler, do not define the macro 'ASM_OUTPUT_ASCII'. -- Macro: ASM_OUTPUT_FDESC (STREAM, DECL, N) A C statement to output word N of a function descriptor for DECL. ! This must be defined if 'TARGET_VTABLE_USES_DESCRIPTORS' is defined, and is otherwise unused. -- Macro: CONSTANT_POOL_BEFORE_FUNCTION You may define this macro as a C expression. You should define the expression to have a nonzero value if GCC should output the ! constant pool for a function before the code for the function, or a ! zero value if GCC should output the constant pool after the function. If you do not define this macro, the usual case, GCC will output the constant pool before the function. --- 35368,35402 ---- -- Target Hook: bool TARGET_ASM_OUTPUT_ADDR_CONST_EXTRA (FILE *FILE, rtx X) ! A target hook to recognize RTX patterns that `output_addr_const' can't deal with, and output assembly code to FILE corresponding to the pattern X. This may be used to allow machine-dependent ! `UNSPEC's to appear within constants. If target hook fails to recognize a pattern, it must return ! `false', so that a standard error message is printed. If it ! prints an error message itself, by calling, for example, ! `output_operand_lossage', it may just return `true'. -- Macro: ASM_OUTPUT_ASCII (STREAM, PTR, LEN) A C statement to output to the stdio stream STREAM an assembler instruction to assemble a string constant containing the LEN bytes ! at PTR. PTR will be a C expression of type `char *' and LEN a C ! expression of type `int'. ! If the assembler has a `.ascii' pseudo-op as found in the Berkeley ! Unix assembler, do not define the macro `ASM_OUTPUT_ASCII'. -- Macro: ASM_OUTPUT_FDESC (STREAM, DECL, N) A C statement to output word N of a function descriptor for DECL. ! This must be defined if `TARGET_VTABLE_USES_DESCRIPTORS' is defined, and is otherwise unused. -- Macro: CONSTANT_POOL_BEFORE_FUNCTION You may define this macro as a C expression. You should define the expression to have a nonzero value if GCC should output the ! constant pool for a function before the code for the function, or ! a zero value if GCC should output the constant pool after the function. If you do not define this macro, the usual case, GCC will output the constant pool before the function. *************** File: gccint.info, Node: Data Output, *** 34981,34995 **** If no constant-pool prefix is required, the usual case, this macro need not be defined. ! -- Macro: ASM_OUTPUT_SPECIAL_POOL_ENTRY (FILE, X, MODE, ALIGN, LABELNO, ! JUMPTO) A C statement (with or without semicolon) to output a constant in ! the constant pool, if it needs special treatment. (This macro need ! not do anything for RTL expressions that can be output normally.) The argument FILE is the standard I/O stream to output the assembler code on. X is the RTL expression for the constant to ! output, and MODE is the machine mode (in case X is a 'const_int'). ALIGN is the required alignment for the value X; you should output an assembler directive to force this much alignment. --- 35411,35426 ---- If no constant-pool prefix is required, the usual case, this macro need not be defined. ! -- Macro: ASM_OUTPUT_SPECIAL_POOL_ENTRY (FILE, X, MODE, ALIGN, ! LABELNO, JUMPTO) A C statement (with or without semicolon) to output a constant in ! the constant pool, if it needs special treatment. (This macro ! need not do anything for RTL expressions that can be output ! normally.) The argument FILE is the standard I/O stream to output the assembler code on. X is the RTL expression for the constant to ! output, and MODE is the machine mode (in case X is a `const_int'). ALIGN is the required alignment for the value X; you should output an assembler directive to force this much alignment. *************** File: gccint.info, Node: Data Output, *** 34998,35007 **** responsible for outputting the label definition at the proper place. Here is how to do this: ! (*targetm.asm_out.internal_label) (FILE, "LC", LABELNO); When you output a pool entry specially, you should end with a ! 'goto' to the label JUMPTO. This will prevent the same pool entry from being output a second time in the usual manner. You need not define this macro if it would do nothing. --- 35429,35438 ---- responsible for outputting the label definition at the proper place. Here is how to do this: ! `(*targetm.asm_out.internal_label)' (FILE, "LC", LABELNO); When you output a pool entry specially, you should end with a ! `goto' to the label JUMPTO. This will prevent the same pool entry from being output a second time in the usual manner. You need not define this macro if it would do nothing. *************** File: gccint.info, Node: Data Output, *** 35024,35040 **** line separator uses multiple characters. If you do not define this macro, the default is that only the ! character ';' is treated as a logical line separator. -- Target Hook: const char * TARGET_ASM_OPEN_PAREN -- Target Hook: const char * TARGET_ASM_CLOSE_PAREN ! These target hooks are C string constants, describing the syntax in ! the assembler for grouping arithmetic expressions. If not overridden, they default to normal parentheses, which is correct for most assemblers. ! These macros are provided by 'real.h' for writing the definitions of ! 'ASM_OUTPUT_DOUBLE' and the like: -- Macro: REAL_VALUE_TO_TARGET_SINGLE (X, L) -- Macro: REAL_VALUE_TO_TARGET_DOUBLE (X, L) --- 35455,35471 ---- line separator uses multiple characters. If you do not define this macro, the default is that only the ! character `;' is treated as a logical line separator. -- Target Hook: const char * TARGET_ASM_OPEN_PAREN -- Target Hook: const char * TARGET_ASM_CLOSE_PAREN ! These target hooks are C string constants, describing the syntax ! in the assembler for grouping arithmetic expressions. If not overridden, they default to normal parentheses, which is correct for most assemblers. ! These macros are provided by `real.h' for writing the definitions of ! `ASM_OUTPUT_DOUBLE' and the like: -- Macro: REAL_VALUE_TO_TARGET_SINGLE (X, L) -- Macro: REAL_VALUE_TO_TARGET_DOUBLE (X, L) *************** File: gccint.info, Node: Data Output, *** 35042,35060 **** -- Macro: REAL_VALUE_TO_TARGET_DECIMAL32 (X, L) -- Macro: REAL_VALUE_TO_TARGET_DECIMAL64 (X, L) -- Macro: REAL_VALUE_TO_TARGET_DECIMAL128 (X, L) ! These translate X, of type 'REAL_VALUE_TYPE', to the target's floating point representation, and store its bit pattern in the ! variable L. For 'REAL_VALUE_TO_TARGET_SINGLE' and ! 'REAL_VALUE_TO_TARGET_DECIMAL32', this variable should be a simple ! 'long int'. For the others, it should be an array of 'long int'. The number of elements in this array is determined by the size of the desired target floating point data type: 32 bits of it go in ! each 'long int' array element. Each array element holds 32 bits of ! the result, even if 'long int' is wider than 32 bits on the host ! machine. The array element values are designed so that you can print them ! out using 'fprintf' in the order they should appear in the target machine's memory.  --- 35473,35491 ---- -- Macro: REAL_VALUE_TO_TARGET_DECIMAL32 (X, L) -- Macro: REAL_VALUE_TO_TARGET_DECIMAL64 (X, L) -- Macro: REAL_VALUE_TO_TARGET_DECIMAL128 (X, L) ! These translate X, of type `REAL_VALUE_TYPE', to the target's floating point representation, and store its bit pattern in the ! variable L. For `REAL_VALUE_TO_TARGET_SINGLE' and ! `REAL_VALUE_TO_TARGET_DECIMAL32', this variable should be a simple ! `long int'. For the others, it should be an array of `long int'. The number of elements in this array is determined by the size of the desired target floating point data type: 32 bits of it go in ! each `long int' array element. Each array element holds 32 bits ! of the result, even if `long int' is wider than 32 bits on the ! host machine. The array element values are designed so that you can print them ! out using `fprintf' in the order they should appear in the target machine's memory.  *************** Each of the macros in this section is us *** 35067,35077 **** outputting a single uninitialized variable. -- Macro: ASM_OUTPUT_COMMON (STREAM, NAME, SIZE, ROUNDED) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! the assembler definition of a common-label named NAME whose size is ! SIZE bytes. The variable ROUNDED is the size rounded up to ! whatever alignment the caller wants. It is possible that SIZE may ! be zero, for instance if a struct with no other member than a zero-length array is defined. In this case, the backend must output a symbol definition that allocates at least one byte, both so that the address of the resulting object does not compare equal --- 35498,35508 ---- outputting a single uninitialized variable. -- Macro: ASM_OUTPUT_COMMON (STREAM, NAME, SIZE, ROUNDED) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM the assembler definition of a common-label named NAME whose ! size is SIZE bytes. The variable ROUNDED is the size rounded up ! to whatever alignment the caller wants. It is possible that SIZE ! may be zero, for instance if a struct with no other member than a zero-length array is defined. In this case, the backend must output a symbol definition that allocates at least one byte, both so that the address of the resulting object does not compare equal *************** outputting a single uninitialized variab *** 35079,35159 **** the concept of a zero-sized common symbol, as that is how they represent an ordinary undefined external. ! Use the expression 'assemble_name (STREAM, NAME)' to output the ! name itself; before and after that, output the additional assembler ! syntax for defining the name, and a newline. This macro controls how the assembler definitions of uninitialized common global variables are output. -- Macro: ASM_OUTPUT_ALIGNED_COMMON (STREAM, NAME, SIZE, ALIGNMENT) ! Like 'ASM_OUTPUT_COMMON' except takes the required alignment as a separate, explicit argument. If you define this macro, it is used ! in place of 'ASM_OUTPUT_COMMON', and gives you more flexibility in handling the required alignment of the variable. The alignment is specified as the number of bits. -- Macro: ASM_OUTPUT_ALIGNED_DECL_COMMON (STREAM, DECL, NAME, SIZE, ALIGNMENT) ! Like 'ASM_OUTPUT_ALIGNED_COMMON' except that DECL of the variable ! to be output, if there is one, or 'NULL_TREE' if there is no corresponding variable. If you define this macro, GCC will use it ! in place of both 'ASM_OUTPUT_COMMON' and ! 'ASM_OUTPUT_ALIGNED_COMMON'. Define this macro when you need to see the variable's decl in order to chose what to output. -- Macro: ASM_OUTPUT_ALIGNED_BSS (STREAM, DECL, NAME, SIZE, ALIGNMENT) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! the assembler definition of uninitialized global DECL named NAME ! whose size is SIZE bytes. The variable ALIGNMENT is the alignment ! specified as the number of bits. ! Try to use function 'asm_output_aligned_bss' defined in file ! 'varasm.c' when defining this macro. If unable, use the expression ! 'assemble_name (STREAM, NAME)' to output the name itself; before and after that, output the additional assembler syntax for defining the name, and a newline. There are two ways of handling global BSS. One is to define this ! macro. The other is to have 'TARGET_ASM_SELECT_SECTION' return a switchable BSS section (*note TARGET_HAVE_SWITCHABLE_BSS_SECTIONS::). You do not need to do both. ! Some languages do not have 'common' data, and require a non-common form of global BSS in order to handle uninitialized globals efficiently. C++ is one example of this. However, if the target does not support global BSS, the front end may choose to make globals common in order to save space in the object file. -- Macro: ASM_OUTPUT_LOCAL (STREAM, NAME, SIZE, ROUNDED) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! the assembler definition of a local-common-label named NAME whose ! size is SIZE bytes. The variable ROUNDED is the size rounded up to ! whatever alignment the caller wants. ! Use the expression 'assemble_name (STREAM, NAME)' to output the ! name itself; before and after that, output the additional assembler ! syntax for defining the name, and a newline. This macro controls how the assembler definitions of uninitialized static variables are output. -- Macro: ASM_OUTPUT_ALIGNED_LOCAL (STREAM, NAME, SIZE, ALIGNMENT) ! Like 'ASM_OUTPUT_LOCAL' except takes the required alignment as a separate, explicit argument. If you define this macro, it is used ! in place of 'ASM_OUTPUT_LOCAL', and gives you more flexibility in handling the required alignment of the variable. The alignment is specified as the number of bits. -- Macro: ASM_OUTPUT_ALIGNED_DECL_LOCAL (STREAM, DECL, NAME, SIZE, ALIGNMENT) ! Like 'ASM_OUTPUT_ALIGNED_DECL' except that DECL of the variable to ! be output, if there is one, or 'NULL_TREE' if there is no corresponding variable. If you define this macro, GCC will use it ! in place of both 'ASM_OUTPUT_DECL' and 'ASM_OUTPUT_ALIGNED_DECL'. ! Define this macro when you need to see the variable's decl in order ! to chose what to output.  File: gccint.info, Node: Label Output, Next: Initialization, Prev: Uninitialized Data, Up: Assembler Format --- 35510,35590 ---- the concept of a zero-sized common symbol, as that is how they represent an ordinary undefined external. ! Use the expression `assemble_name (STREAM, NAME)' to output the ! name itself; before and after that, output the additional ! assembler syntax for defining the name, and a newline. This macro controls how the assembler definitions of uninitialized common global variables are output. -- Macro: ASM_OUTPUT_ALIGNED_COMMON (STREAM, NAME, SIZE, ALIGNMENT) ! Like `ASM_OUTPUT_COMMON' except takes the required alignment as a separate, explicit argument. If you define this macro, it is used ! in place of `ASM_OUTPUT_COMMON', and gives you more flexibility in handling the required alignment of the variable. The alignment is specified as the number of bits. -- Macro: ASM_OUTPUT_ALIGNED_DECL_COMMON (STREAM, DECL, NAME, SIZE, ALIGNMENT) ! Like `ASM_OUTPUT_ALIGNED_COMMON' except that DECL of the variable ! to be output, if there is one, or `NULL_TREE' if there is no corresponding variable. If you define this macro, GCC will use it ! in place of both `ASM_OUTPUT_COMMON' and ! `ASM_OUTPUT_ALIGNED_COMMON'. Define this macro when you need to see the variable's decl in order to chose what to output. -- Macro: ASM_OUTPUT_ALIGNED_BSS (STREAM, DECL, NAME, SIZE, ALIGNMENT) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM the assembler definition of uninitialized global DECL named ! NAME whose size is SIZE bytes. The variable ALIGNMENT is the ! alignment specified as the number of bits. ! Try to use function `asm_output_aligned_bss' defined in file ! `varasm.c' when defining this macro. If unable, use the expression ! `assemble_name (STREAM, NAME)' to output the name itself; before and after that, output the additional assembler syntax for defining the name, and a newline. There are two ways of handling global BSS. One is to define this ! macro. The other is to have `TARGET_ASM_SELECT_SECTION' return a switchable BSS section (*note TARGET_HAVE_SWITCHABLE_BSS_SECTIONS::). You do not need to do both. ! Some languages do not have `common' data, and require a non-common form of global BSS in order to handle uninitialized globals efficiently. C++ is one example of this. However, if the target does not support global BSS, the front end may choose to make globals common in order to save space in the object file. -- Macro: ASM_OUTPUT_LOCAL (STREAM, NAME, SIZE, ROUNDED) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM the assembler definition of a local-common-label named NAME ! whose size is SIZE bytes. The variable ROUNDED is the size ! rounded up to whatever alignment the caller wants. ! Use the expression `assemble_name (STREAM, NAME)' to output the ! name itself; before and after that, output the additional ! assembler syntax for defining the name, and a newline. This macro controls how the assembler definitions of uninitialized static variables are output. -- Macro: ASM_OUTPUT_ALIGNED_LOCAL (STREAM, NAME, SIZE, ALIGNMENT) ! Like `ASM_OUTPUT_LOCAL' except takes the required alignment as a separate, explicit argument. If you define this macro, it is used ! in place of `ASM_OUTPUT_LOCAL', and gives you more flexibility in handling the required alignment of the variable. The alignment is specified as the number of bits. -- Macro: ASM_OUTPUT_ALIGNED_DECL_LOCAL (STREAM, DECL, NAME, SIZE, ALIGNMENT) ! Like `ASM_OUTPUT_ALIGNED_DECL' except that DECL of the variable to ! be output, if there is one, or `NULL_TREE' if there is no corresponding variable. If you define this macro, GCC will use it ! in place of both `ASM_OUTPUT_DECL' and `ASM_OUTPUT_ALIGNED_DECL'. ! Define this macro when you need to see the variable's decl in ! order to chose what to output.  File: gccint.info, Node: Label Output, Next: Initialization, Prev: Uninitialized Data, Up: Assembler Format *************** File: gccint.info, Node: Label Output, *** 35164,35446 **** This is about outputting labels. -- Macro: ASM_OUTPUT_LABEL (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! the assembler definition of a label named NAME. Use the expression ! 'assemble_name (STREAM, NAME)' to output the name itself; before ! and after that, output the additional assembler syntax for defining ! the name, and a newline. A default definition of this macro is ! provided which is correct for most systems. ! ! -- Macro: ASM_OUTPUT_FUNCTION_LABEL (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! the assembler definition of a label named NAME of a function. Use ! the expression 'assemble_name (STREAM, NAME)' to output the name itself; before and after that, output the additional assembler syntax for defining the name, and a newline. A default definition of this macro is provided which is correct for most systems. If this macro is not defined, then the function name is defined in ! the usual manner as a label (by means of 'ASM_OUTPUT_LABEL'). -- Macro: ASM_OUTPUT_INTERNAL_LABEL (STREAM, NAME) ! Identical to 'ASM_OUTPUT_LABEL', except that NAME is known to refer ! to a compiler-generated label. The default definition uses ! 'assemble_name_raw', which is like 'assemble_name' except that it is more efficient. -- Macro: SIZE_ASM_OP A C string containing the appropriate assembler directive to specify the size of a symbol, without any arguments. On systems ! that use ELF, the default (in 'config/elfos.h') is '"\t.size\t"'; on other systems, the default is not to define this macro. Define this macro only if it is correct to use the default ! definitions of 'ASM_OUTPUT_SIZE_DIRECTIVE' and ! 'ASM_OUTPUT_MEASURED_SIZE' for your system. If you need your own custom definitions of those macros, or if you do not need explicit symbol sizes at all, do not define this macro. -- Macro: ASM_OUTPUT_SIZE_DIRECTIVE (STREAM, NAME, SIZE) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! a directive telling the assembler that the size of the symbol NAME ! is SIZE. SIZE is a 'HOST_WIDE_INT'. If you define 'SIZE_ASM_OP', ! a default definition of this macro is provided. -- Macro: ASM_OUTPUT_MEASURED_SIZE (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! a directive telling the assembler to calculate the size of the ! symbol NAME by subtracting its address from the current address. ! If you define 'SIZE_ASM_OP', a default definition of this macro is provided. The default assumes that the assembler recognizes a ! special '.' symbol as referring to the current address, and can calculate the difference between this and another symbol. If your ! assembler does not recognize '.' or cannot do calculations with it, ! you will need to redefine 'ASM_OUTPUT_MEASURED_SIZE' to use some ! other technique. -- Macro: NO_DOLLAR_IN_LABEL Define this macro if the assembler does not accept the character ! '$' in label names. By default constructors and destructors in G++ ! have '$' in the identifiers. If this macro is defined, '.' is used ! instead. -- Macro: NO_DOT_IN_LABEL Define this macro if the assembler does not accept the character ! '.' in label names. By default constructors and destructors in G++ ! have names that use '.'. If this macro is defined, these names are ! rewritten to avoid '.'. -- Macro: TYPE_ASM_OP A C string containing the appropriate assembler directive to specify the type of a symbol, without any arguments. On systems ! that use ELF, the default (in 'config/elfos.h') is '"\t.type\t"'; on other systems, the default is not to define this macro. Define this macro only if it is correct to use the default ! definition of 'ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you need your own custom definition of this macro, or if you do not need explicit symbol types at all, do not define this macro. -- Macro: TYPE_OPERAND_FMT ! A C string which specifies (using 'printf' syntax) the format of ! the second operand to 'TYPE_ASM_OP'. On systems that use ELF, the ! default (in 'config/elfos.h') is '"@%s"'; on other systems, the default is not to define this macro. Define this macro only if it is correct to use the default ! definition of 'ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you need your own custom definition of this macro, or if you do not need explicit symbol types at all, do not define this macro. -- Macro: ASM_OUTPUT_TYPE_DIRECTIVE (STREAM, TYPE) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! a directive telling the assembler that the type of the symbol NAME ! is TYPE. TYPE is a C string; currently, that string is always ! either '"function"' or '"object"', but you should not count on ! this. ! If you define 'TYPE_ASM_OP' and 'TYPE_OPERAND_FMT', a default definition of this macro is provided. -- Macro: ASM_DECLARE_FUNCTION_NAME (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! any text necessary for declaring the name NAME of a function which ! is being defined. This macro is responsible for outputting the ! label definition (perhaps using 'ASM_OUTPUT_FUNCTION_LABEL'). The ! argument DECL is the 'FUNCTION_DECL' tree node representing the ! function. If this macro is not defined, then the function name is defined in the usual manner as a label (by means of ! 'ASM_OUTPUT_FUNCTION_LABEL'). ! You may wish to use 'ASM_OUTPUT_TYPE_DIRECTIVE' in the definition of this macro. -- Macro: ASM_DECLARE_FUNCTION_SIZE (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! any text necessary for declaring the size of a function which is ! being defined. The argument NAME is the name of the function. The ! argument DECL is the 'FUNCTION_DECL' tree node representing the ! function. If this macro is not defined, then the function size is not defined. ! You may wish to use 'ASM_OUTPUT_MEASURED_SIZE' in the definition of ! this macro. -- Macro: ASM_DECLARE_COLD_FUNCTION_NAME (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! any text necessary for declaring the name NAME of a cold function ! partition which is being defined. This macro is responsible for ! outputting the label definition (perhaps using ! 'ASM_OUTPUT_FUNCTION_LABEL'). The argument DECL is the ! 'FUNCTION_DECL' tree node representing the function. If this macro is not defined, then the cold partition name is defined in the usual manner as a label (by means of ! 'ASM_OUTPUT_LABEL'). ! You may wish to use 'ASM_OUTPUT_TYPE_DIRECTIVE' in the definition of this macro. -- Macro: ASM_DECLARE_COLD_FUNCTION_SIZE (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! any text necessary for declaring the size of a cold function ! partition which is being defined. The argument NAME is the name of ! the cold partition of the function. The argument DECL is the ! 'FUNCTION_DECL' tree node representing the function. If this macro is not defined, then the partition size is not defined. ! You may wish to use 'ASM_OUTPUT_MEASURED_SIZE' in the definition of ! this macro. -- Macro: ASM_DECLARE_OBJECT_NAME (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! any text necessary for declaring the name NAME of an initialized ! variable which is being defined. This macro must output the label ! definition (perhaps using 'ASM_OUTPUT_LABEL'). The argument DECL ! is the 'VAR_DECL' tree node representing the variable. If this macro is not defined, then the variable name is defined in ! the usual manner as a label (by means of 'ASM_OUTPUT_LABEL'). ! You may wish to use 'ASM_OUTPUT_TYPE_DIRECTIVE' and/or ! 'ASM_OUTPUT_SIZE_DIRECTIVE' in the definition of this macro. -- Target Hook: void TARGET_ASM_DECLARE_CONSTANT_NAME (FILE *FILE, const char *NAME, const_tree EXPR, HOST_WIDE_INT SIZE) A target hook to output to the stdio stream FILE any text necessary for declaring the name NAME of a constant which is being defined. ! This target hook is responsible for outputting the label definition ! (perhaps using 'assemble_label'). The argument EXP is the value of ! the constant, and SIZE is the size of the constant in bytes. The ! NAME will be an internal label. The default version of this target hook, define the NAME in the ! usual manner as a label (by means of 'assemble_label'). ! You may wish to use 'ASM_OUTPUT_TYPE_DIRECTIVE' in this target hook. -- Macro: ASM_DECLARE_REGISTER_GLOBAL (STREAM, DECL, REGNO, NAME) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! any text necessary for claiming a register REGNO for a global ! variable DECL with name NAME. If you don't define this macro, that is equivalent to defining it to do nothing. -- Macro: ASM_FINISH_DECLARE_OBJECT (STREAM, DECL, TOPLEVEL, ATEND) A C statement (sans semicolon) to finish up declaring a variable ! name once the compiler has processed its initializer fully and thus ! has had a chance to determine the size of an array when controlled ! by an initializer. This is used on systems where it's necessary to ! declare something about the size of the object. If you don't define this macro, that is equivalent to defining it to do nothing. ! You may wish to use 'ASM_OUTPUT_SIZE_DIRECTIVE' and/or ! 'ASM_OUTPUT_MEASURED_SIZE' in the definition of this macro. -- Target Hook: void TARGET_ASM_GLOBALIZE_LABEL (FILE *STREAM, const char *NAME) ! This target hook is a function to output to the stdio stream STREAM ! some commands that will make the label NAME global; that is, ! available for reference from other files. The default implementation relies on a proper definition of ! 'GLOBAL_ASM_OP'. ! -- Target Hook: void TARGET_ASM_GLOBALIZE_DECL_NAME (FILE *STREAM, tree ! DECL) ! This target hook is a function to output to the stdio stream STREAM ! some commands that will make the name associated with DECL global; ! that is, available for reference from other files. The default implementation uses the TARGET_ASM_GLOBALIZE_LABEL target hook. -- Target Hook: void TARGET_ASM_ASSEMBLE_UNDEFINED_DECL (FILE *STREAM, const char *NAME, const_tree DECL) ! This target hook is a function to output to the stdio stream STREAM ! some commands that will declare the name associated with DECL which ! is not defined in the current translation unit. Most assemblers do ! not require anything to be output in this case. -- Macro: ASM_WEAKEN_LABEL (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! some commands that will make the label NAME weak; that is, available for reference from other files but only used if no other ! definition is available. Use the expression 'assemble_name (STREAM, NAME)' to output the name itself; before and after that, output the additional assembler syntax for making that name weak, and a newline. ! If you don't define this macro or 'ASM_WEAKEN_DECL', GCC will not ! support weak symbols and you should not define the 'SUPPORTS_WEAK' macro. -- Macro: ASM_WEAKEN_DECL (STREAM, DECL, NAME, VALUE) ! Combines (and replaces) the function of 'ASM_WEAKEN_LABEL' and ! 'ASM_OUTPUT_WEAK_ALIAS', allowing access to the associated function ! or variable decl. If VALUE is not 'NULL', this C statement should output to the stdio stream STREAM assembler code which defines (equates) the weak symbol NAME to have the value VALUE. If VALUE ! is 'NULL', it should output commands to make NAME weak. -- Macro: ASM_OUTPUT_WEAKREF (STREAM, DECL, NAME, VALUE) ! Outputs a directive that enables NAME to be used to refer to symbol ! VALUE with weak-symbol semantics. 'decl' is the declaration of ! 'name'. -- Macro: SUPPORTS_WEAK A preprocessor constant expression which evaluates to true if the target supports weak symbols. ! If you don't define this macro, 'defaults.h' provides a default ! definition. If either 'ASM_WEAKEN_LABEL' or 'ASM_WEAKEN_DECL' is ! defined, the default definition is '1'; otherwise, it is '0'. -- Macro: TARGET_SUPPORTS_WEAK A C expression which evaluates to true if the target supports weak symbols. ! If you don't define this macro, 'defaults.h' provides a default ! definition. The default definition is '(SUPPORTS_WEAK)'. Define this macro if you want to control weak symbol support with a ! compiler flag such as '-melf'. -- Macro: MAKE_DECL_ONE_ONLY (DECL) A C statement (sans semicolon) to mark DECL to be emitted as a public symbol such that extra copies in multiple translation units will be discarded by the linker. Define this macro if your object ! file format provides support for this concept, such as the 'COMDAT' section flags in the Microsoft Windows PE/COFF format, and this support requires changes to DECL, such as putting it in a separate section. --- 35595,35880 ---- This is about outputting labels. -- Macro: ASM_OUTPUT_LABEL (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM the assembler definition of a label named NAME. Use the ! expression `assemble_name (STREAM, NAME)' to output the name itself; before and after that, output the additional assembler syntax for defining the name, and a newline. A default definition of this macro is provided which is correct for most systems. + -- Macro: ASM_OUTPUT_FUNCTION_LABEL (STREAM, NAME, DECL) + A C statement (sans semicolon) to output to the stdio stream + STREAM the assembler definition of a label named NAME of a + function. Use the expression `assemble_name (STREAM, NAME)' to + output the name itself; before and after that, output the + additional assembler syntax for defining the name, and a newline. + A default definition of this macro is provided which is correct + for most systems. + If this macro is not defined, then the function name is defined in ! the usual manner as a label (by means of `ASM_OUTPUT_LABEL'). -- Macro: ASM_OUTPUT_INTERNAL_LABEL (STREAM, NAME) ! Identical to `ASM_OUTPUT_LABEL', except that NAME is known to ! refer to a compiler-generated label. The default definition uses ! `assemble_name_raw', which is like `assemble_name' except that it is more efficient. -- Macro: SIZE_ASM_OP A C string containing the appropriate assembler directive to specify the size of a symbol, without any arguments. On systems ! that use ELF, the default (in `config/elfos.h') is `"\t.size\t"'; on other systems, the default is not to define this macro. Define this macro only if it is correct to use the default ! definitions of `ASM_OUTPUT_SIZE_DIRECTIVE' and ! `ASM_OUTPUT_MEASURED_SIZE' for your system. If you need your own custom definitions of those macros, or if you do not need explicit symbol sizes at all, do not define this macro. -- Macro: ASM_OUTPUT_SIZE_DIRECTIVE (STREAM, NAME, SIZE) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM a directive telling the assembler that the size of the ! symbol NAME is SIZE. SIZE is a `HOST_WIDE_INT'. If you define ! `SIZE_ASM_OP', a default definition of this macro is provided. -- Macro: ASM_OUTPUT_MEASURED_SIZE (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM a directive telling the assembler to calculate the size of ! the symbol NAME by subtracting its address from the current ! address. ! If you define `SIZE_ASM_OP', a default definition of this macro is provided. The default assumes that the assembler recognizes a ! special `.' symbol as referring to the current address, and can calculate the difference between this and another symbol. If your ! assembler does not recognize `.' or cannot do calculations with ! it, you will need to redefine `ASM_OUTPUT_MEASURED_SIZE' to use ! some other technique. -- Macro: NO_DOLLAR_IN_LABEL Define this macro if the assembler does not accept the character ! `$' in label names. By default constructors and destructors in ! G++ have `$' in the identifiers. If this macro is defined, `.' is ! used instead. -- Macro: NO_DOT_IN_LABEL Define this macro if the assembler does not accept the character ! `.' in label names. By default constructors and destructors in G++ ! have names that use `.'. If this macro is defined, these names ! are rewritten to avoid `.'. -- Macro: TYPE_ASM_OP A C string containing the appropriate assembler directive to specify the type of a symbol, without any arguments. On systems ! that use ELF, the default (in `config/elfos.h') is `"\t.type\t"'; on other systems, the default is not to define this macro. Define this macro only if it is correct to use the default ! definition of `ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you need your own custom definition of this macro, or if you do not need explicit symbol types at all, do not define this macro. -- Macro: TYPE_OPERAND_FMT ! A C string which specifies (using `printf' syntax) the format of ! the second operand to `TYPE_ASM_OP'. On systems that use ELF, the ! default (in `config/elfos.h') is `"@%s"'; on other systems, the default is not to define this macro. Define this macro only if it is correct to use the default ! definition of `ASM_OUTPUT_TYPE_DIRECTIVE' for your system. If you need your own custom definition of this macro, or if you do not need explicit symbol types at all, do not define this macro. -- Macro: ASM_OUTPUT_TYPE_DIRECTIVE (STREAM, TYPE) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM a directive telling the assembler that the type of the ! symbol NAME is TYPE. TYPE is a C string; currently, that string ! is always either `"function"' or `"object"', but you should not ! count on this. ! If you define `TYPE_ASM_OP' and `TYPE_OPERAND_FMT', a default definition of this macro is provided. -- Macro: ASM_DECLARE_FUNCTION_NAME (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM any text necessary for declaring the name NAME of a ! function which is being defined. This macro is responsible for ! outputting the label definition (perhaps using ! `ASM_OUTPUT_FUNCTION_LABEL'). The argument DECL is the ! `FUNCTION_DECL' tree node representing the function. If this macro is not defined, then the function name is defined in the usual manner as a label (by means of ! `ASM_OUTPUT_FUNCTION_LABEL'). ! You may wish to use `ASM_OUTPUT_TYPE_DIRECTIVE' in the definition of this macro. -- Macro: ASM_DECLARE_FUNCTION_SIZE (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM any text necessary for declaring the size of a function ! which is being defined. The argument NAME is the name of the ! function. The argument DECL is the `FUNCTION_DECL' tree node ! representing the function. If this macro is not defined, then the function size is not defined. ! You may wish to use `ASM_OUTPUT_MEASURED_SIZE' in the definition ! of this macro. -- Macro: ASM_DECLARE_COLD_FUNCTION_NAME (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM any text necessary for declaring the name NAME of a cold ! function partition which is being defined. This macro is ! responsible for outputting the label definition (perhaps using ! `ASM_OUTPUT_FUNCTION_LABEL'). The argument DECL is the ! `FUNCTION_DECL' tree node representing the function. If this macro is not defined, then the cold partition name is defined in the usual manner as a label (by means of ! `ASM_OUTPUT_LABEL'). ! You may wish to use `ASM_OUTPUT_TYPE_DIRECTIVE' in the definition of this macro. -- Macro: ASM_DECLARE_COLD_FUNCTION_SIZE (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM any text necessary for declaring the size of a cold function ! partition which is being defined. The argument NAME is the name ! of the cold partition of the function. The argument DECL is the ! `FUNCTION_DECL' tree node representing the function. If this macro is not defined, then the partition size is not defined. ! You may wish to use `ASM_OUTPUT_MEASURED_SIZE' in the definition ! of this macro. -- Macro: ASM_DECLARE_OBJECT_NAME (STREAM, NAME, DECL) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM any text necessary for declaring the name NAME of an ! initialized variable which is being defined. This macro must ! output the label definition (perhaps using `ASM_OUTPUT_LABEL'). ! The argument DECL is the `VAR_DECL' tree node representing the ! variable. If this macro is not defined, then the variable name is defined in ! the usual manner as a label (by means of `ASM_OUTPUT_LABEL'). ! You may wish to use `ASM_OUTPUT_TYPE_DIRECTIVE' and/or ! `ASM_OUTPUT_SIZE_DIRECTIVE' in the definition of this macro. -- Target Hook: void TARGET_ASM_DECLARE_CONSTANT_NAME (FILE *FILE, const char *NAME, const_tree EXPR, HOST_WIDE_INT SIZE) A target hook to output to the stdio stream FILE any text necessary for declaring the name NAME of a constant which is being defined. ! This target hook is responsible for outputting the label ! definition (perhaps using `assemble_label'). The argument EXP is ! the value of the constant, and SIZE is the size of the constant in ! bytes. The NAME will be an internal label. The default version of this target hook, define the NAME in the ! usual manner as a label (by means of `assemble_label'). ! You may wish to use `ASM_OUTPUT_TYPE_DIRECTIVE' in this target hook. -- Macro: ASM_DECLARE_REGISTER_GLOBAL (STREAM, DECL, REGNO, NAME) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM any text necessary for claiming a register REGNO for a ! global variable DECL with name NAME. If you don't define this macro, that is equivalent to defining it to do nothing. -- Macro: ASM_FINISH_DECLARE_OBJECT (STREAM, DECL, TOPLEVEL, ATEND) A C statement (sans semicolon) to finish up declaring a variable ! name once the compiler has processed its initializer fully and ! thus has had a chance to determine the size of an array when ! controlled by an initializer. This is used on systems where it's ! necessary to declare something about the size of the object. If you don't define this macro, that is equivalent to defining it to do nothing. ! You may wish to use `ASM_OUTPUT_SIZE_DIRECTIVE' and/or ! `ASM_OUTPUT_MEASURED_SIZE' in the definition of this macro. -- Target Hook: void TARGET_ASM_GLOBALIZE_LABEL (FILE *STREAM, const char *NAME) ! This target hook is a function to output to the stdio stream ! STREAM some commands that will make the label NAME global; that ! is, available for reference from other files. The default implementation relies on a proper definition of ! `GLOBAL_ASM_OP'. ! -- Target Hook: void TARGET_ASM_GLOBALIZE_DECL_NAME (FILE *STREAM, ! tree DECL) ! This target hook is a function to output to the stdio stream ! STREAM some commands that will make the name associated with DECL ! global; that is, available for reference from other files. The default implementation uses the TARGET_ASM_GLOBALIZE_LABEL target hook. -- Target Hook: void TARGET_ASM_ASSEMBLE_UNDEFINED_DECL (FILE *STREAM, const char *NAME, const_tree DECL) ! This target hook is a function to output to the stdio stream ! STREAM some commands that will declare the name associated with ! DECL which is not defined in the current translation unit. Most ! assemblers do not require anything to be output in this case. -- Macro: ASM_WEAKEN_LABEL (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM some commands that will make the label NAME weak; that is, available for reference from other files but only used if no other ! definition is available. Use the expression `assemble_name (STREAM, NAME)' to output the name itself; before and after that, output the additional assembler syntax for making that name weak, and a newline. ! If you don't define this macro or `ASM_WEAKEN_DECL', GCC will not ! support weak symbols and you should not define the `SUPPORTS_WEAK' macro. -- Macro: ASM_WEAKEN_DECL (STREAM, DECL, NAME, VALUE) ! Combines (and replaces) the function of `ASM_WEAKEN_LABEL' and ! `ASM_OUTPUT_WEAK_ALIAS', allowing access to the associated function ! or variable decl. If VALUE is not `NULL', this C statement should output to the stdio stream STREAM assembler code which defines (equates) the weak symbol NAME to have the value VALUE. If VALUE ! is `NULL', it should output commands to make NAME weak. -- Macro: ASM_OUTPUT_WEAKREF (STREAM, DECL, NAME, VALUE) ! Outputs a directive that enables NAME to be used to refer to ! symbol VALUE with weak-symbol semantics. `decl' is the ! declaration of `name'. -- Macro: SUPPORTS_WEAK A preprocessor constant expression which evaluates to true if the target supports weak symbols. ! If you don't define this macro, `defaults.h' provides a default ! definition. If either `ASM_WEAKEN_LABEL' or `ASM_WEAKEN_DECL' is ! defined, the default definition is `1'; otherwise, it is `0'. -- Macro: TARGET_SUPPORTS_WEAK A C expression which evaluates to true if the target supports weak symbols. ! If you don't define this macro, `defaults.h' provides a default ! definition. The default definition is `(SUPPORTS_WEAK)'. Define this macro if you want to control weak symbol support with a ! compiler flag such as `-melf'. -- Macro: MAKE_DECL_ONE_ONLY (DECL) A C statement (sans semicolon) to mark DECL to be emitted as a public symbol such that extra copies in multiple translation units will be discarded by the linker. Define this macro if your object ! file format provides support for this concept, such as the `COMDAT' section flags in the Microsoft Windows PE/COFF format, and this support requires changes to DECL, such as putting it in a separate section. *************** This is about outputting labels. *** 35449,35459 **** A C expression which evaluates to true if the target supports one-only semantics. ! If you don't define this macro, 'varasm.c' provides a default ! definition. If 'MAKE_DECL_ONE_ONLY' is defined, the default ! definition is '1'; otherwise, it is '0'. Define this macro if you want to control one-only symbol support with a compiler flag, or if ! setting the 'DECL_ONE_ONLY' flag is enough to mark a declaration to be emitted as one-only. -- Target Hook: void TARGET_ASM_ASSEMBLE_VISIBILITY (tree DECL, int --- 35883,35893 ---- A C expression which evaluates to true if the target supports one-only semantics. ! If you don't define this macro, `varasm.c' provides a default ! definition. If `MAKE_DECL_ONE_ONLY' is defined, the default ! definition is `1'; otherwise, it is `0'. Define this macro if you want to control one-only symbol support with a compiler flag, or if ! setting the `DECL_ONE_ONLY' flag is enough to mark a declaration to be emitted as one-only. -- Target Hook: void TARGET_ASM_ASSEMBLE_VISIBILITY (tree DECL, int *************** This is about outputting labels. *** 35465,35502 **** -- Macro: TARGET_WEAK_NOT_IN_ARCHIVE_TOC A C expression that evaluates to true if the target's linker ! expects that weak symbols do not appear in a static archive's table ! of contents. The default is '0'. Leaving weak symbols out of an archive's table of contents means that, if a symbol will only have a definition in one translation unit and will have undefined references from other translation units, that symbol should not be weak. Defining this macro to be nonzero will thus have the effect that certain symbols that would ! normally be weak (explicit template instantiations, and vtables for ! polymorphic classes with noninline key methods) will instead be ! nonweak. The C++ ABI requires this macro to be zero. Define this macro for targets where full C++ ABI compliance is impossible and where ! linker restrictions require weak symbols to be left out of a static ! archive's table of contents. -- Macro: ASM_OUTPUT_EXTERNAL (STREAM, DECL, NAME) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! any text necessary for declaring the name of an external symbol ! named NAME which is referenced in this compilation but not defined. ! The value of DECL is the tree node for the declaration. This macro need not be defined if it does not need to output ! anything. The GNU assembler and most Unix assemblers don't require ! anything. -- Target Hook: void TARGET_ASM_EXTERNAL_LIBCALL (rtx SYMREF) This target hook is a function to output to ASM_OUT_FILE an assembler pseudo-op to declare a library function name external. The name of the library function is given by SYMREF, which is a ! 'symbol_ref'. -- Target Hook: void TARGET_ASM_MARK_DECL_PRESERVED (const char *SYMBOL) --- 35899,35936 ---- -- Macro: TARGET_WEAK_NOT_IN_ARCHIVE_TOC A C expression that evaluates to true if the target's linker ! expects that weak symbols do not appear in a static archive's ! table of contents. The default is `0'. Leaving weak symbols out of an archive's table of contents means that, if a symbol will only have a definition in one translation unit and will have undefined references from other translation units, that symbol should not be weak. Defining this macro to be nonzero will thus have the effect that certain symbols that would ! normally be weak (explicit template instantiations, and vtables ! for polymorphic classes with noninline key methods) will instead ! be nonweak. The C++ ABI requires this macro to be zero. Define this macro for targets where full C++ ABI compliance is impossible and where ! linker restrictions require weak symbols to be left out of a ! static archive's table of contents. -- Macro: ASM_OUTPUT_EXTERNAL (STREAM, DECL, NAME) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM any text necessary for declaring the name of an external ! symbol named NAME which is referenced in this compilation but not ! defined. The value of DECL is the tree node for the declaration. This macro need not be defined if it does not need to output ! anything. The GNU assembler and most Unix assemblers don't ! require anything. -- Target Hook: void TARGET_ASM_EXTERNAL_LIBCALL (rtx SYMREF) This target hook is a function to output to ASM_OUT_FILE an assembler pseudo-op to declare a library function name external. The name of the library function is given by SYMREF, which is a ! `symbol_ref'. -- Target Hook: void TARGET_ASM_MARK_DECL_PRESERVED (const char *SYMBOL) *************** This is about outputting labels. *** 35505,35539 **** uses the .no_dead_code_strip directive. -- Macro: ASM_OUTPUT_LABELREF (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream STREAM ! a reference in assembler syntax to a label named NAME. This should ! add '_' to the front of the name, if that is customary on your ! operating system, as it is in most Berkeley Unix systems. This ! macro is used in 'assemble_name'. -- Target Hook: tree TARGET_MANGLE_ASSEMBLER_NAME (const char *NAME) ! Given a symbol NAME, perform same mangling as 'varasm.c''s ! 'assemble_name', but in memory rather than to a file stream, ! returning result as an 'IDENTIFIER_NODE'. Required for correct LTO ! symtabs. The default implementation calls the ! 'TARGET_STRIP_NAME_ENCODING' hook and then prepends the ! 'USER_LABEL_PREFIX', if any. -- Macro: ASM_OUTPUT_SYMBOL_REF (STREAM, SYM) A C statement (sans semicolon) to output a reference to ! 'SYMBOL_REF' SYM. If not defined, 'assemble_name' will be used to output the name of the symbol. This macro may be used to modify the way a symbol is referenced depending on information encoded by ! 'TARGET_ENCODE_SECTION_INFO'. -- Macro: ASM_OUTPUT_LABEL_REF (STREAM, BUF) A C statement (sans semicolon) to output a reference to BUF, the ! result of 'ASM_GENERATE_INTERNAL_LABEL'. If not defined, ! 'assemble_name' will be used to output the name of the symbol. ! This macro is not used by 'output_asm_label', or the '%l' specifier ! that calls it; the intention is that this macro should be set when ! it is necessary to output a label differently when its address is ! being taken. -- Target Hook: void TARGET_ASM_INTERNAL_LABEL (FILE *STREAM, const char *PREFIX, unsigned long LABELNO) --- 35939,35973 ---- uses the .no_dead_code_strip directive. -- Macro: ASM_OUTPUT_LABELREF (STREAM, NAME) ! A C statement (sans semicolon) to output to the stdio stream ! STREAM a reference in assembler syntax to a label named NAME. ! This should add `_' to the front of the name, if that is customary ! on your operating system, as it is in most Berkeley Unix systems. ! This macro is used in `assemble_name'. -- Target Hook: tree TARGET_MANGLE_ASSEMBLER_NAME (const char *NAME) ! Given a symbol NAME, perform same mangling as `varasm.c''s ! `assemble_name', but in memory rather than to a file stream, ! returning result as an `IDENTIFIER_NODE'. Required for correct ! LTO symtabs. The default implementation calls the ! `TARGET_STRIP_NAME_ENCODING' hook and then prepends the ! `USER_LABEL_PREFIX', if any. -- Macro: ASM_OUTPUT_SYMBOL_REF (STREAM, SYM) A C statement (sans semicolon) to output a reference to ! `SYMBOL_REF' SYM. If not defined, `assemble_name' will be used to output the name of the symbol. This macro may be used to modify the way a symbol is referenced depending on information encoded by ! `TARGET_ENCODE_SECTION_INFO'. -- Macro: ASM_OUTPUT_LABEL_REF (STREAM, BUF) A C statement (sans semicolon) to output a reference to BUF, the ! result of `ASM_GENERATE_INTERNAL_LABEL'. If not defined, ! `assemble_name' will be used to output the name of the symbol. ! This macro is not used by `output_asm_label', or the `%l' ! specifier that calls it; the intention is that this macro should ! be set when it is necessary to output a label differently when its ! address is being taken. -- Target Hook: void TARGET_ASM_INTERNAL_LABEL (FILE *STREAM, const char *PREFIX, unsigned long LABELNO) *************** This is about outputting labels. *** 35544,35593 **** labels used for user-level functions and variables. Otherwise, certain programs will have name conflicts with internal labels. ! It is desirable to exclude internal labels from the symbol table of ! the object file. Most assemblers have a naming convention for ! labels that should be excluded; on many systems, the letter 'L' at the beginning of a label has this effect. You should find out what convention your system uses, and follow it. The default version of this function utilizes ! 'ASM_GENERATE_INTERNAL_LABEL'. -- Macro: ASM_OUTPUT_DEBUG_LABEL (STREAM, PREFIX, NUM) A C statement to output to the stdio stream STREAM a debug info ! label whose name is made from the string PREFIX and the number NUM. ! This is useful for VLIW targets, where debug info labels may need ! to be treated differently than branch target labels. On some systems, branch target labels must be at the beginning of instruction bundles, but debug info labels can occur in the middle of instruction bundles. If this macro is not defined, then ! '(*targetm.asm_out.internal_label)' will be used. -- Macro: ASM_GENERATE_INTERNAL_LABEL (STRING, PREFIX, NUM) ! A C statement to store into the string STRING a label whose name is ! made from the string PREFIX and the number NUM. ! This string, when output subsequently by 'assemble_name', should ! produce the output that '(*targetm.asm_out.internal_label)' would produce with the same PREFIX and NUM. ! If the string begins with '*', then 'assemble_name' will output the ! rest of the string unchanged. It is often convenient for ! 'ASM_GENERATE_INTERNAL_LABEL' to use '*' in this way. If the ! string doesn't start with '*', then 'ASM_OUTPUT_LABELREF' gets to output the string, and may change it. (Of course, ! 'ASM_OUTPUT_LABELREF' is also part of your machine description, so you should know what it does on your machine.) -- Macro: ASM_FORMAT_PRIVATE_NAME (OUTVAR, NAME, NUMBER) A C expression to assign to OUTVAR (which is a variable of type ! 'char *') a newly allocated string made from the string NAME and the number NUMBER, with some suitable punctuation added. Use ! 'alloca' to get space for the string. ! The string will be used as an argument to 'ASM_OUTPUT_LABELREF' to produce an assembler label for an internal static variable whose name is NAME. Therefore, the string must be such as to result in valid assembler code. The argument NUMBER is different each time --- 35978,36027 ---- labels used for user-level functions and variables. Otherwise, certain programs will have name conflicts with internal labels. ! It is desirable to exclude internal labels from the symbol table ! of the object file. Most assemblers have a naming convention for ! labels that should be excluded; on many systems, the letter `L' at the beginning of a label has this effect. You should find out what convention your system uses, and follow it. The default version of this function utilizes ! `ASM_GENERATE_INTERNAL_LABEL'. -- Macro: ASM_OUTPUT_DEBUG_LABEL (STREAM, PREFIX, NUM) A C statement to output to the stdio stream STREAM a debug info ! label whose name is made from the string PREFIX and the number ! NUM. This is useful for VLIW targets, where debug info labels may ! need to be treated differently than branch target labels. On some systems, branch target labels must be at the beginning of instruction bundles, but debug info labels can occur in the middle of instruction bundles. If this macro is not defined, then ! `(*targetm.asm_out.internal_label)' will be used. -- Macro: ASM_GENERATE_INTERNAL_LABEL (STRING, PREFIX, NUM) ! A C statement to store into the string STRING a label whose name ! is made from the string PREFIX and the number NUM. ! This string, when output subsequently by `assemble_name', should ! produce the output that `(*targetm.asm_out.internal_label)' would produce with the same PREFIX and NUM. ! If the string begins with `*', then `assemble_name' will output ! the rest of the string unchanged. It is often convenient for ! `ASM_GENERATE_INTERNAL_LABEL' to use `*' in this way. If the ! string doesn't start with `*', then `ASM_OUTPUT_LABELREF' gets to output the string, and may change it. (Of course, ! `ASM_OUTPUT_LABELREF' is also part of your machine description, so you should know what it does on your machine.) -- Macro: ASM_FORMAT_PRIVATE_NAME (OUTVAR, NAME, NUMBER) A C expression to assign to OUTVAR (which is a variable of type ! `char *') a newly allocated string made from the string NAME and the number NUMBER, with some suitable punctuation added. Use ! `alloca' to get space for the string. ! The string will be used as an argument to `ASM_OUTPUT_LABELREF' to produce an assembler label for an internal static variable whose name is NAME. Therefore, the string must be such as to result in valid assembler code. The argument NUMBER is different each time *************** This is about outputting labels. *** 35596,35603 **** Ideally this string should not be a valid C identifier, to prevent any conflict with the user's own symbols. Most assemblers allow ! periods or percent signs in assembler symbols; putting at least one ! of these between the name and the number will suffice. If this macro is not defined, a default definition will be provided which is correct for most systems. --- 36030,36037 ---- Ideally this string should not be a valid C identifier, to prevent any conflict with the user's own symbols. Most assemblers allow ! periods or percent signs in assembler symbols; putting at least ! one of these between the name and the number will suffice. If this macro is not defined, a default definition will be provided which is correct for most systems. *************** This is about outputting labels. *** 35606,35612 **** A C statement to output to the stdio stream STREAM assembler code which defines (equates) the symbol NAME to have the value VALUE. ! If 'SET_ASM_OP' is defined, a default definition is provided which is correct for most systems. -- Macro: ASM_OUTPUT_DEF_FROM_DECLS (STREAM, DECL_OF_NAME, --- 36040,36046 ---- A C statement to output to the stdio stream STREAM assembler code which defines (equates) the symbol NAME to have the value VALUE. ! If `SET_ASM_OP' is defined, a default definition is provided which is correct for most systems. -- Macro: ASM_OUTPUT_DEF_FROM_DECLS (STREAM, DECL_OF_NAME, *************** This is about outputting labels. *** 35614,35623 **** A C statement to output to the stdio stream STREAM assembler code which defines (equates) the symbol whose tree node is DECL_OF_NAME to have the value of the tree node DECL_OF_VALUE. This macro will ! be used in preference to 'ASM_OUTPUT_DEF' if it is defined and if the tree nodes are available. ! If 'SET_ASM_OP' is defined, a default definition is provided which is correct for most systems. -- Macro: TARGET_DEFERRED_OUTPUT_DEFS (DECL_OF_NAME, DECL_OF_VALUE) --- 36048,36057 ---- A C statement to output to the stdio stream STREAM assembler code which defines (equates) the symbol whose tree node is DECL_OF_NAME to have the value of the tree node DECL_OF_VALUE. This macro will ! be used in preference to `ASM_OUTPUT_DEF' if it is defined and if the tree nodes are available. ! If `SET_ASM_OP' is defined, a default definition is provided which is correct for most systems. -- Macro: TARGET_DEFERRED_OUTPUT_DEFS (DECL_OF_NAME, DECL_OF_VALUE) *************** This is about outputting labels. *** 35626,35641 **** have the value of the tree node DECL_OF_VALUE should be emitted near the end of the current compilation unit. The default is to not defer output of defines. This macro affects defines output by ! 'ASM_OUTPUT_DEF' and 'ASM_OUTPUT_DEF_FROM_DECLS'. -- Macro: ASM_OUTPUT_WEAK_ALIAS (STREAM, NAME, VALUE) A C statement to output to the stdio stream STREAM assembler code which defines (equates) the weak symbol NAME to have the value ! VALUE. If VALUE is 'NULL', it defines NAME as an undefined weak symbol. Define this macro if the target only supports weak aliases; define ! 'ASM_OUTPUT_DEF' instead if possible. -- Macro: OBJC_GEN_METHOD_LABEL (BUF, IS_INST, CLASS_NAME, CAT_NAME, SEL_NAME) --- 36060,36075 ---- have the value of the tree node DECL_OF_VALUE should be emitted near the end of the current compilation unit. The default is to not defer output of defines. This macro affects defines output by ! `ASM_OUTPUT_DEF' and `ASM_OUTPUT_DEF_FROM_DECLS'. -- Macro: ASM_OUTPUT_WEAK_ALIAS (STREAM, NAME, VALUE) A C statement to output to the stdio stream STREAM assembler code which defines (equates) the weak symbol NAME to have the value ! VALUE. If VALUE is `NULL', it defines NAME as an undefined weak symbol. Define this macro if the target only supports weak aliases; define ! `ASM_OUTPUT_DEF' instead if possible. -- Macro: OBJC_GEN_METHOD_LABEL (BUF, IS_INST, CLASS_NAME, CAT_NAME, SEL_NAME) *************** This is about outputting labels. *** 35643,35667 **** Objective-C methods. The default name is a unique method number followed by the name of ! the class (e.g. '_1_Foo'). For methods in categories, the name of the category is also included in the assembler name (e.g. ! '_1_Foo_Bar'). These names are safe on most systems, but make debugging difficult ! since the method's selector is not present in the name. Therefore, ! particular systems define other ways of computing names. ! BUF is an expression of type 'char *' which gives you a buffer in which to store the name; its length is as long as CLASS_NAME, CAT_NAME and SEL_NAME put together, plus 50 characters extra. The argument IS_INST specifies whether the method is an instance method or a class method; CLASS_NAME is the name of the class; ! CAT_NAME is the name of the category (or 'NULL' if the method is not in a category); and SEL_NAME is the name of the selector. ! On systems where the assembler can handle quoted names, you can use ! this macro to provide more human-readable names.  File: gccint.info, Node: Initialization, Next: Macros for Initialization, Prev: Label Output, Up: Assembler Format --- 36077,36101 ---- Objective-C methods. The default name is a unique method number followed by the name of ! the class (e.g. `_1_Foo'). For methods in categories, the name of the category is also included in the assembler name (e.g. ! `_1_Foo_Bar'). These names are safe on most systems, but make debugging difficult ! since the method's selector is not present in the name. ! Therefore, particular systems define other ways of computing names. ! BUF is an expression of type `char *' which gives you a buffer in which to store the name; its length is as long as CLASS_NAME, CAT_NAME and SEL_NAME put together, plus 50 characters extra. The argument IS_INST specifies whether the method is an instance method or a class method; CLASS_NAME is the name of the class; ! CAT_NAME is the name of the category (or `NULL' if the method is not in a category); and SEL_NAME is the name of the selector. ! On systems where the assembler can handle quoted names, you can ! use this macro to provide more human-readable names.  File: gccint.info, Node: Initialization, Next: Macros for Initialization, Prev: Label Output, Up: Assembler Format *************** File: gccint.info, Node: Initialization *** 35672,35678 **** The compiled code for certain languages includes "constructors" (also called "initialization routines")--functions to initialize data in the program when the program is started. These functions need to be called ! before the program is "started"--that is to say, before 'main' is called. Compiling some languages generates "destructors" (also called --- 36106,36112 ---- The compiled code for certain languages includes "constructors" (also called "initialization routines")--functions to initialize data in the program when the program is started. These functions need to be called ! before the program is "started"--that is to say, before `main' is called. Compiling some languages generates "destructors" (also called *************** initialization and termination functions *** 35689,35696 **** Much of the structure is common to all four variations. The linker must build two lists of these functions--a list of ! initialization functions, called '__CTOR_LIST__', and a list of ! termination functions, called '__DTOR_LIST__'. Each list always begins with an ignored function pointer (which may hold 0, -1, or a count of the function pointers after it, depending on --- 36123,36130 ---- Much of the structure is common to all four variations. The linker must build two lists of these functions--a list of ! initialization functions, called `__CTOR_LIST__', and a list of ! termination functions, called `__DTOR_LIST__'. Each list always begins with an ignored function pointer (which may hold 0, -1, or a count of the function pointers after it, depending on *************** pointers to constructors (or destructors *** 35699,35779 **** pointer containing zero. Depending on the operating system and its executable file format, ! either 'crtstuff.c' or 'libgcc2.c' traverses these lists at startup time ! and exit time. Constructors are called in reverse order of the list; ! destructors in forward order. The best way to handle static constructors works only for object file formats which provide arbitrarily-named sections. A section is set aside for a list of constructors, and another for a list of destructors. ! Traditionally these are called '.ctors' and '.dtors'. Each object file that defines an initialization function also puts a word in the constructor section to point to that function. The linker accumulates ! all these words into one contiguous '.ctors' section. Termination functions are handled similarly. ! This method will be chosen as the default by 'target-def.h' if ! 'TARGET_ASM_NAMED_SECTION' is defined. A target that does not support arbitrary sections, but does support special designated constructor and ! destructor sections may define 'CTORS_SECTION_ASM_OP' and ! 'DTORS_SECTION_ASM_OP' to achieve the same effect. When arbitrary sections are available, there are two variants, ! depending upon how the code in 'crtstuff.c' is called. On systems that ! support a ".init" section which is executed at program startup, parts of ! 'crtstuff.c' are compiled into that section. The program is linked by ! the 'gcc' driver like this: ld -o OUTPUT_FILE crti.o crtbegin.o ... -lgcc crtend.o crtn.o ! The prologue of a function ('__init') appears in the '.init' section of ! 'crti.o'; the epilogue appears in 'crtn.o'. Likewise for the function ! '__fini' in the ".fini" section. Normally these files are provided by ! the operating system or by the GNU C library, but are provided by GCC ! for a few targets. ! The objects 'crtbegin.o' and 'crtend.o' are (for most targets) compiled ! from 'crtstuff.c'. They contain, among other things, code fragments ! within the '.init' and '.fini' sections that branch to routines in the ! '.text' section. The linker will pull all parts of a section together, ! which results in a complete '__init' function that invokes the routines ! we need at startup. ! To use this variant, you must define the 'INIT_SECTION_ASM_OP' macro properly. If no init section is available, when GCC compiles any function called ! 'main' (or more accurately, any function designated as a program entry ! point by the language front end calling 'expand_main_function'), it ! inserts a procedure call to '__main' as the first executable code after ! the function prologue. The '__main' function is defined in 'libgcc2.c' and runs the global constructors. In file formats that don't support arbitrary sections, there are again ! two variants. In the simplest variant, the GNU linker (GNU 'ld') and an ! 'a.out' format must be used. In this case, 'TARGET_ASM_CONSTRUCTOR' is ! defined to produce a '.stabs' entry of type 'N_SETT', referencing the ! name '__CTOR_LIST__', and with the address of the void function containing the initialization code as its value. The GNU linker ! recognizes this as a request to add the value to a "set"; the values are ! accumulated, and are eventually placed in the executable as a vector in ! the format described above, with a leading (ignored) count and a ! trailing zero element. 'TARGET_ASM_DESTRUCTOR' is handled similarly. ! Since no init section is available, the absence of 'INIT_SECTION_ASM_OP' ! causes the compilation of 'main' to call '__main' as above, starting the ! initialization process. The last variant uses neither arbitrary sections nor the GNU linker. This is preferable when you want to do dynamic linking and when using ! file formats which the GNU linker does not support, such as 'ECOFF'. In ! this case, 'TARGET_HAVE_CTORS_DTORS' is false, initialization and termination functions are recognized simply by their names. This ! requires an extra program in the linkage step, called 'collect2'. This program pretends to be the linker, for use with GCC; it does its job by running the ordinary linker, but also arranges to include the vectors of initialization and termination functions. These functions are called ! via '__main' as described above. In order to use this method, ! 'use_collect2' must be defined in the target in 'config.gcc'. The following section describes the specific macros that control and customize the handling of initialization and termination functions. --- 36133,36213 ---- pointer containing zero. Depending on the operating system and its executable file format, ! either `crtstuff.c' or `libgcc2.c' traverses these lists at startup ! time and exit time. Constructors are called in reverse order of the ! list; destructors in forward order. The best way to handle static constructors works only for object file formats which provide arbitrarily-named sections. A section is set aside for a list of constructors, and another for a list of destructors. ! Traditionally these are called `.ctors' and `.dtors'. Each object file that defines an initialization function also puts a word in the constructor section to point to that function. The linker accumulates ! all these words into one contiguous `.ctors' section. Termination functions are handled similarly. ! This method will be chosen as the default by `target-def.h' if ! `TARGET_ASM_NAMED_SECTION' is defined. A target that does not support arbitrary sections, but does support special designated constructor and ! destructor sections may define `CTORS_SECTION_ASM_OP' and ! `DTORS_SECTION_ASM_OP' to achieve the same effect. When arbitrary sections are available, there are two variants, ! depending upon how the code in `crtstuff.c' is called. On systems that ! support a ".init" section which is executed at program startup, parts ! of `crtstuff.c' are compiled into that section. The program is linked ! by the `gcc' driver like this: ld -o OUTPUT_FILE crti.o crtbegin.o ... -lgcc crtend.o crtn.o ! The prologue of a function (`__init') appears in the `.init' section ! of `crti.o'; the epilogue appears in `crtn.o'. Likewise for the ! function `__fini' in the ".fini" section. Normally these files are ! provided by the operating system or by the GNU C library, but are ! provided by GCC for a few targets. ! The objects `crtbegin.o' and `crtend.o' are (for most targets) ! compiled from `crtstuff.c'. They contain, among other things, code ! fragments within the `.init' and `.fini' sections that branch to ! routines in the `.text' section. The linker will pull all parts of a ! section together, which results in a complete `__init' function that ! invokes the routines we need at startup. ! To use this variant, you must define the `INIT_SECTION_ASM_OP' macro properly. If no init section is available, when GCC compiles any function called ! `main' (or more accurately, any function designated as a program entry ! point by the language front end calling `expand_main_function'), it ! inserts a procedure call to `__main' as the first executable code after ! the function prologue. The `__main' function is defined in `libgcc2.c' and runs the global constructors. In file formats that don't support arbitrary sections, there are again ! two variants. In the simplest variant, the GNU linker (GNU `ld') and ! an `a.out' format must be used. In this case, `TARGET_ASM_CONSTRUCTOR' ! is defined to produce a `.stabs' entry of type `N_SETT', referencing ! the name `__CTOR_LIST__', and with the address of the void function containing the initialization code as its value. The GNU linker ! recognizes this as a request to add the value to a "set"; the values ! are accumulated, and are eventually placed in the executable as a ! vector in the format described above, with a leading (ignored) count ! and a trailing zero element. `TARGET_ASM_DESTRUCTOR' is handled ! similarly. Since no init section is available, the absence of ! `INIT_SECTION_ASM_OP' causes the compilation of `main' to call `__main' ! as above, starting the initialization process. The last variant uses neither arbitrary sections nor the GNU linker. This is preferable when you want to do dynamic linking and when using ! file formats which the GNU linker does not support, such as `ECOFF'. In ! this case, `TARGET_HAVE_CTORS_DTORS' is false, initialization and termination functions are recognized simply by their names. This ! requires an extra program in the linkage step, called `collect2'. This program pretends to be the linker, for use with GCC; it does its job by running the ordinary linker, but also arranges to include the vectors of initialization and termination functions. These functions are called ! via `__main' as described above. In order to use this method, ! `use_collect2' must be defined in the target in `config.gcc'. The following section describes the specific macros that control and customize the handling of initialization and termination functions. *************** and termination functions: *** 35793,35806 **** initialization code. If not defined, GCC will assume such a section does not exist. When you are using special sections for initialization and termination functions, this macro also controls ! how 'crtstuff.c' and 'libgcc2.c' arrange to run the initialization functions. -- Macro: HAS_INIT_SECTION ! If defined, 'main' will not call '__main' as described above. This ! macro should be defined for systems that control start-up code on a ! symbol-by-symbol basis, such as OSF/1, and should not be defined ! explicitly for systems that support 'INIT_SECTION_ASM_OP'. -- Macro: LD_INIT_SWITCH If defined, a C string constant for a switch that tells the linker --- 36227,36240 ---- initialization code. If not defined, GCC will assume such a section does not exist. When you are using special sections for initialization and termination functions, this macro also controls ! how `crtstuff.c' and `libgcc2.c' arrange to run the initialization functions. -- Macro: HAS_INIT_SECTION ! If defined, `main' will not call `__main' as described above. ! This macro should be defined for systems that control start-up code ! on a symbol-by-symbol basis, such as OSF/1, and should not be ! defined explicitly for systems that support `INIT_SECTION_ASM_OP'. -- Macro: LD_INIT_SWITCH If defined, a C string constant for a switch that tells the linker *************** and termination functions: *** 35815,35898 **** automatically called when a shared library is loaded. The function should call FUNC, which takes no arguments. If not defined, and the object format requires an explicit initialization function, ! then a function called '_GLOBAL__DI' will be generated. This function and the following one are used by collect2 when ! linking a shared library that needs constructors or destructors, or ! has DWARF2 exception tables embedded in the code. -- Macro: COLLECT_SHARED_FINI_FUNC (STREAM, FUNC) If defined, a C statement that will write a function that can be automatically called when a shared library is unloaded. The function should call FUNC, which takes no arguments. If not defined, and the object format requires an explicit finalization ! function, then a function called '_GLOBAL__DD' will be generated. -- Macro: INVOKE__main ! If defined, 'main' will call '__main' despite the presence of ! 'INIT_SECTION_ASM_OP'. This macro should be defined for systems where the init section is not actually run automatically, but is still useful for collecting the lists of constructors and destructors. -- Macro: SUPPORTS_INIT_PRIORITY ! If nonzero, the C++ 'init_priority' attribute is supported and the compiler should emit instructions to control the order of initialization of objects. If zero, the compiler will issue an ! error message upon encountering an 'init_priority' attribute. -- Target Hook: bool TARGET_HAVE_CTORS_DTORS This value is true if the target supports some "native" method of collecting constructors and destructors to be run at startup and ! exit. It is false if we must use 'collect2'. -- Target Hook: void TARGET_ASM_CONSTRUCTOR (rtx SYMBOL, int PRIORITY) If defined, a function that outputs assembler code to arrange to call the function referenced by SYMBOL at initialization time. ! Assume that SYMBOL is a 'SYMBOL_REF' for a function taking no arguments and with no return value. If the target supports initialization priorities, PRIORITY is a value between 0 and ! 'MAX_INIT_PRIORITY'; otherwise it must be 'DEFAULT_INIT_PRIORITY'. If this macro is not defined by the target, a suitable default will be chosen if (1) the target supports arbitrary section names, (2) ! the target defines 'CTORS_SECTION_ASM_OP', or (3) 'USE_COLLECT2' is ! not defined. -- Target Hook: void TARGET_ASM_DESTRUCTOR (rtx SYMBOL, int PRIORITY) ! This is like 'TARGET_ASM_CONSTRUCTOR' but used for termination functions rather than initialization functions. ! If 'TARGET_HAVE_CTORS_DTORS' is true, the initialization routine generated for the generated object file will have static linkage. ! If your system uses 'collect2' as the means of processing constructors, ! then that program normally uses 'nm' to scan an object file for ! constructor functions to be called. On certain kinds of systems, you can define this macro to make ! 'collect2' work faster (and, in some cases, make it work at all): -- Macro: OBJECT_FORMAT_COFF Define this macro if the system uses COFF (Common Object File ! Format) object files, so that 'collect2' can assume this format and ! scan object files directly for dynamic constructor/destructor functions. ! This macro is effective only in a native compiler; 'collect2' as ! part of a cross compiler always uses 'nm' for the target machine. -- Macro: REAL_NM_FILE_NAME Define this macro as a C string constant containing the file name ! to use to execute 'nm'. The default is to search the path normally ! for 'nm'. -- Macro: NM_FLAGS ! 'collect2' calls 'nm' to scan object files for static constructors ! and destructors and LTO info. By default, '-n' is passed. Define ! 'NM_FLAGS' to a C string constant if other options are needed to ! get the same output format as GNU 'nm -n' produces. If your system supports shared libraries and has a program to list the dynamic dependencies of a given library or executable, you can define --- 36249,36332 ---- automatically called when a shared library is loaded. The function should call FUNC, which takes no arguments. If not defined, and the object format requires an explicit initialization function, ! then a function called `_GLOBAL__DI' will be generated. This function and the following one are used by collect2 when ! linking a shared library that needs constructors or destructors, ! or has DWARF2 exception tables embedded in the code. -- Macro: COLLECT_SHARED_FINI_FUNC (STREAM, FUNC) If defined, a C statement that will write a function that can be automatically called when a shared library is unloaded. The function should call FUNC, which takes no arguments. If not defined, and the object format requires an explicit finalization ! function, then a function called `_GLOBAL__DD' will be generated. -- Macro: INVOKE__main ! If defined, `main' will call `__main' despite the presence of ! `INIT_SECTION_ASM_OP'. This macro should be defined for systems where the init section is not actually run automatically, but is still useful for collecting the lists of constructors and destructors. -- Macro: SUPPORTS_INIT_PRIORITY ! If nonzero, the C++ `init_priority' attribute is supported and the compiler should emit instructions to control the order of initialization of objects. If zero, the compiler will issue an ! error message upon encountering an `init_priority' attribute. -- Target Hook: bool TARGET_HAVE_CTORS_DTORS This value is true if the target supports some "native" method of collecting constructors and destructors to be run at startup and ! exit. It is false if we must use `collect2'. -- Target Hook: void TARGET_ASM_CONSTRUCTOR (rtx SYMBOL, int PRIORITY) If defined, a function that outputs assembler code to arrange to call the function referenced by SYMBOL at initialization time. ! Assume that SYMBOL is a `SYMBOL_REF' for a function taking no arguments and with no return value. If the target supports initialization priorities, PRIORITY is a value between 0 and ! `MAX_INIT_PRIORITY'; otherwise it must be `DEFAULT_INIT_PRIORITY'. If this macro is not defined by the target, a suitable default will be chosen if (1) the target supports arbitrary section names, (2) ! the target defines `CTORS_SECTION_ASM_OP', or (3) `USE_COLLECT2' ! is not defined. -- Target Hook: void TARGET_ASM_DESTRUCTOR (rtx SYMBOL, int PRIORITY) ! This is like `TARGET_ASM_CONSTRUCTOR' but used for termination functions rather than initialization functions. ! If `TARGET_HAVE_CTORS_DTORS' is true, the initialization routine generated for the generated object file will have static linkage. ! If your system uses `collect2' as the means of processing ! constructors, then that program normally uses `nm' to scan an object ! file for constructor functions to be called. On certain kinds of systems, you can define this macro to make ! `collect2' work faster (and, in some cases, make it work at all): -- Macro: OBJECT_FORMAT_COFF Define this macro if the system uses COFF (Common Object File ! Format) object files, so that `collect2' can assume this format ! and scan object files directly for dynamic constructor/destructor functions. ! This macro is effective only in a native compiler; `collect2' as ! part of a cross compiler always uses `nm' for the target machine. -- Macro: REAL_NM_FILE_NAME Define this macro as a C string constant containing the file name ! to use to execute `nm'. The default is to search the path ! normally for `nm'. -- Macro: NM_FLAGS ! `collect2' calls `nm' to scan object files for static constructors ! and destructors and LTO info. By default, `-n' is passed. Define ! `NM_FLAGS' to a C string constant if other options are needed to ! get the same output format as GNU `nm -n' produces. If your system supports shared libraries and has a program to list the dynamic dependencies of a given library or executable, you can define *************** these macros to enable support for runni *** 35900,35922 **** termination functions in shared libraries: -- Macro: LDD_SUFFIX ! Define this macro to a C string constant containing the name of the ! program which lists dynamic dependencies, like 'ldd' under SunOS 4. -- Macro: PARSE_LDD_OUTPUT (PTR) Define this macro to be C code that extracts filenames from the ! output of the program denoted by 'LDD_SUFFIX'. PTR is a variable ! of type 'char *' that points to the beginning of a line of output ! from 'LDD_SUFFIX'. If the line lists a dynamic dependency, the code must advance PTR to the beginning of the filename on that ! line. Otherwise, it must set PTR to 'NULL'. -- Macro: SHLIB_SUFFIX Define this macro to a C string constant containing the default ! shared library extension of the target (e.g., '".so"'). 'collect2' strips version information after this suffix when generating global constructor and destructor names. This define is only needed on ! targets that use 'collect2' to process constructors and destructors.  --- 36334,36357 ---- termination functions in shared libraries: -- Macro: LDD_SUFFIX ! Define this macro to a C string constant containing the name of ! the program which lists dynamic dependencies, like `ldd' under ! SunOS 4. -- Macro: PARSE_LDD_OUTPUT (PTR) Define this macro to be C code that extracts filenames from the ! output of the program denoted by `LDD_SUFFIX'. PTR is a variable ! of type `char *' that points to the beginning of a line of output ! from `LDD_SUFFIX'. If the line lists a dynamic dependency, the code must advance PTR to the beginning of the filename on that ! line. Otherwise, it must set PTR to `NULL'. -- Macro: SHLIB_SUFFIX Define this macro to a C string constant containing the default ! shared library extension of the target (e.g., `".so"'). `collect2' strips version information after this suffix when generating global constructor and destructor names. This define is only needed on ! targets that use `collect2' to process constructors and destructors.  *************** This describes assembler instruction out *** 35934,35955 **** language. -- Macro: ADDITIONAL_REGISTER_NAMES ! If defined, a C initializer for an array of structures containing a ! name and a register number. This macro defines additional names ! for hard registers, thus allowing the 'asm' option in declarations to refer to registers using alternate names. -- Macro: OVERLAPPING_REGISTER_NAMES If defined, a C initializer for an array of structures containing a name, a register number and a count of the number of consecutive machine registers the name overlaps. This macro defines additional ! names for hard registers, thus allowing the 'asm' option in declarations to refer to registers using alternate names. Unlike ! 'ADDITIONAL_REGISTER_NAMES', this macro should be used when the register name implies multiple underlying registers. This macro should be used when it is important that a clobber in an ! 'asm' statement clobbers all the underlying values implied by the register name. For example, on ARM, clobbering the double-precision VFP register "d0" implies clobbering both single-precision registers "s0" and "s1". --- 36369,36390 ---- language. -- Macro: ADDITIONAL_REGISTER_NAMES ! If defined, a C initializer for an array of structures containing ! a name and a register number. This macro defines additional names ! for hard registers, thus allowing the `asm' option in declarations to refer to registers using alternate names. -- Macro: OVERLAPPING_REGISTER_NAMES If defined, a C initializer for an array of structures containing a name, a register number and a count of the number of consecutive machine registers the name overlaps. This macro defines additional ! names for hard registers, thus allowing the `asm' option in declarations to refer to registers using alternate names. Unlike ! `ADDITIONAL_REGISTER_NAMES', this macro should be used when the register name implies multiple underlying registers. This macro should be used when it is important that a clobber in an ! `asm' statement clobbers all the underlying values implied by the register name. For example, on ARM, clobbering the double-precision VFP register "d0" implies clobbering both single-precision registers "s0" and "s1". *************** This describes assembler instruction out *** 35960,35980 **** The definition is a C statement or statements which output an assembler instruction opcode to the stdio stream STREAM. The ! macro-operand PTR is a variable of type 'char *' which points to ! the opcode name in its "internal" form--the form that is written in ! the machine description. The definition should output the opcode ! name to STREAM, performing any translation you desire, and increment the variable PTR to point at the end of the opcode so that it will not be output twice. In fact, your macro definition may process less than the entire opcode name, or more than the opcode name; but if you want to ! process text that includes '%'-sequences to substitute operands, you must take care of the substitution yourself. Just be sure to increment PTR over whatever text should not be output normally. If you need to look at the operand values, they can be found as the ! elements of 'recog_data.operand'. If the macro definition does nothing, the instruction is output in the usual way. --- 36395,36415 ---- The definition is a C statement or statements which output an assembler instruction opcode to the stdio stream STREAM. The ! macro-operand PTR is a variable of type `char *' which points to ! the opcode name in its "internal" form--the form that is written ! in the machine description. The definition should output the ! opcode name to STREAM, performing any translation you desire, and increment the variable PTR to point at the end of the opcode so that it will not be output twice. In fact, your macro definition may process less than the entire opcode name, or more than the opcode name; but if you want to ! process text that includes `%'-sequences to substitute operands, you must take care of the substitution yourself. Just be sure to increment PTR over whatever text should not be output normally. If you need to look at the operand values, they can be found as the ! elements of `recog_data.operand'. If the macro definition does nothing, the instruction is output in the usual way. *************** This describes assembler instruction out *** 35985,36003 **** they will be output differently. Here the argument OPVEC is the vector containing the operands ! extracted from INSN, and NOPERANDS is the number of elements of the ! vector which contain meaningful data for this insn. The contents ! of this vector are what will be used to convert the insn template ! into assembler code, so you can change the assembler output by ! changing the contents of the vector. This macro is useful when various assembler syntaxes share a single file of instruction patterns; by defining this macro differently, you can cause a large class of instructions to be output differently (such as with rearranged operands). Naturally, variations in assembler syntax affecting individual insn patterns ! ought to be handled by writing conditional output routines in those ! patterns. If this macro is not defined, it is equivalent to a null statement. --- 36420,36438 ---- they will be output differently. Here the argument OPVEC is the vector containing the operands ! extracted from INSN, and NOPERANDS is the number of elements of ! the vector which contain meaningful data for this insn. The ! contents of this vector are what will be used to convert the insn ! template into assembler code, so you can change the assembler ! output by changing the contents of the vector. This macro is useful when various assembler syntaxes share a single file of instruction patterns; by defining this macro differently, you can cause a large class of instructions to be output differently (such as with rearranged operands). Naturally, variations in assembler syntax affecting individual insn patterns ! ought to be handled by writing conditional output routines in ! those patterns. If this macro is not defined, it is equivalent to a null statement. *************** This describes assembler instruction out *** 36008,36018 **** the assembler if necessary. Here the argument OPVEC is the vector containing the operands ! extracted from INSN, and NOPERANDS is the number of elements of the ! vector which contain meaningful data for this insn. The contents ! of this vector are what was used to convert the insn template into ! assembler code, so you can change the assembler mode by checking ! the contents of the vector. -- Macro: PRINT_OPERAND (STREAM, X, CODE) A C compound statement to output to stdio stream STREAM the --- 36443,36453 ---- the assembler if necessary. Here the argument OPVEC is the vector containing the operands ! extracted from INSN, and NOPERANDS is the number of elements of ! the vector which contain meaningful data for this insn. The ! contents of this vector are what was used to convert the insn ! template into assembler code, so you can change the assembler mode ! by checking the contents of the vector. -- Macro: PRINT_OPERAND (STREAM, X, CODE) A C compound statement to output to stdio stream STREAM the *************** This describes assembler instruction out *** 36022,36044 **** CODE is a value that can be used to specify one of several ways of printing the operand. It is used when identical operands must be printed differently depending on the context. CODE comes from the ! '%' specification that was used to request printing of the operand. ! If the specification was just '%DIGIT' then CODE is 0; if the ! specification was '%LTR DIGIT' then CODE is the ASCII code for LTR. If X is a register, this macro should print the register's name. ! The names can be found in an array 'reg_names' whose type is 'char ! *[]'. 'reg_names' is initialized from 'REGISTER_NAMES'. ! When the machine description has a specification '%PUNCT' (a '%' followed by a punctuation character), this macro is called with a null pointer for X and the punctuation character for CODE. -- Macro: PRINT_OPERAND_PUNCT_VALID_P (CODE) A C expression which evaluates to true if CODE is a valid ! punctuation character for use in the 'PRINT_OPERAND' macro. If ! 'PRINT_OPERAND_PUNCT_VALID_P' is not defined, it means that no ! punctuation characters (except for the standard one, '%') are used in this way. -- Macro: PRINT_OPERAND_ADDRESS (STREAM, X) --- 36457,36480 ---- CODE is a value that can be used to specify one of several ways of printing the operand. It is used when identical operands must be printed differently depending on the context. CODE comes from the ! `%' specification that was used to request printing of the ! operand. If the specification was just `%DIGIT' then CODE is 0; ! if the specification was `%LTR DIGIT' then CODE is the ASCII code ! for LTR. If X is a register, this macro should print the register's name. ! The names can be found in an array `reg_names' whose type is `char ! *[]'. `reg_names' is initialized from `REGISTER_NAMES'. ! When the machine description has a specification `%PUNCT' (a `%' followed by a punctuation character), this macro is called with a null pointer for X and the punctuation character for CODE. -- Macro: PRINT_OPERAND_PUNCT_VALID_P (CODE) A C expression which evaluates to true if CODE is a valid ! punctuation character for use in the `PRINT_OPERAND' macro. If ! `PRINT_OPERAND_PUNCT_VALID_P' is not defined, it means that no ! punctuation characters (except for the standard one, `%') are used in this way. -- Macro: PRINT_OPERAND_ADDRESS (STREAM, X) *************** This describes assembler instruction out *** 36048,36060 **** On some machines, the syntax for a symbolic address depends on the section that the address refers to. On these machines, define the ! hook 'TARGET_ENCODE_SECTION_INFO' to store the information into the ! 'symbol_ref', and then check for it here. *Note Assembler Format::. -- Macro: DBR_OUTPUT_SEQEND (FILE) A C statement, to be executed after all slot-filler instructions ! have been output. If necessary, call 'dbr_sequence_length' to determine the number of slots filled in a sequence (zero if not currently outputting a sequence), to decide how many no-ops to output, or whatever. --- 36484,36496 ---- On some machines, the syntax for a symbolic address depends on the section that the address refers to. On these machines, define the ! hook `TARGET_ENCODE_SECTION_INFO' to store the information into the ! `symbol_ref', and then check for it here. *Note Assembler Format::. -- Macro: DBR_OUTPUT_SEQEND (FILE) A C statement, to be executed after all slot-filler instructions ! have been output. If necessary, call `dbr_sequence_length' to determine the number of slots filled in a sequence (zero if not currently outputting a sequence), to decide how many no-ops to output, or whatever. *************** This describes assembler instruction out *** 36065,36088 **** Note that output routines for instructions with delay slots must be prepared to deal with not being output as part of a sequence (i.e. when ! the scheduling pass is not run, or when no slot fillers could be found.) ! The variable 'final_sequence' is null when not processing a sequence, ! otherwise it contains the 'sequence' rtx being output. -- Macro: REGISTER_PREFIX -- Macro: LOCAL_LABEL_PREFIX -- Macro: USER_LABEL_PREFIX -- Macro: IMMEDIATE_PREFIX ! If defined, C string expressions to be used for the '%R', '%L', ! '%U', and '%I' options of 'asm_fprintf' (see 'final.c'). These are ! useful when a single 'md' file must support multiple assembler ! formats. In that case, the various 'tm.h' files can define these macros differently. -- Macro: ASM_FPRINTF_EXTENSIONS (FILE, ARGPTR, FORMAT) ! If defined this macro should expand to a series of 'case' ! statements which will be parsed inside the 'switch' statement of ! the 'asm_fprintf' function. This allows targets to define extra printf formats which may useful when generating their assembler statements. Note that uppercase letters are reserved for future generic extensions to asm_fprintf, and so are not available to --- 36501,36524 ---- Note that output routines for instructions with delay slots must be prepared to deal with not being output as part of a sequence (i.e. when ! the scheduling pass is not run, or when no slot fillers could be ! found.) The variable `final_sequence' is null when not processing a ! sequence, otherwise it contains the `sequence' rtx being output. -- Macro: REGISTER_PREFIX -- Macro: LOCAL_LABEL_PREFIX -- Macro: USER_LABEL_PREFIX -- Macro: IMMEDIATE_PREFIX ! If defined, C string expressions to be used for the `%R', `%L', ! `%U', and `%I' options of `asm_fprintf' (see `final.c'). These ! are useful when a single `md' file must support multiple assembler ! formats. In that case, the various `tm.h' files can define these macros differently. -- Macro: ASM_FPRINTF_EXTENSIONS (FILE, ARGPTR, FORMAT) ! If defined this macro should expand to a series of `case' ! statements which will be parsed inside the `switch' statement of ! the `asm_fprintf' function. This allows targets to define extra printf formats which may useful when generating their assembler statements. Note that uppercase letters are reserved for future generic extensions to asm_fprintf, and so are not available to *************** otherwise it contains the 'sequence' rtx *** 36098,36122 **** use, with zero as the first variant. If this macro is defined, you may use constructs of the form ! '{option0|option1|option2...}' ! in the output templates of patterns (*note Output Template::) or in ! the first argument of 'asm_fprintf'. This construct outputs ! 'option0', 'option1', 'option2', etc., if the value of ! 'ASSEMBLER_DIALECT' is zero, one, two, etc. Any special characters within these strings retain their usual meaning. If there are fewer alternatives within the braces than the value of ! 'ASSEMBLER_DIALECT', the construct outputs nothing. If it's needed ! to print curly braces or '|' character in assembler output ! directly, '%{', '%}' and '%|' can be used. ! If you do not define this macro, the characters '{', '|' and '}' do ! not have any special meaning when used in templates or operands to ! 'asm_fprintf'. ! Define the macros 'REGISTER_PREFIX', 'LOCAL_LABEL_PREFIX', ! 'USER_LABEL_PREFIX' and 'IMMEDIATE_PREFIX' if you can express the variations in assembler language syntax with that mechanism. ! Define 'ASSEMBLER_DIALECT' and use the '{option0|option1}' syntax if the syntax variant are larger and involve such things as different opcodes or operand order. --- 36534,36558 ---- use, with zero as the first variant. If this macro is defined, you may use constructs of the form ! `{option0|option1|option2...}' ! in the output templates of patterns (*note Output Template::) or ! in the first argument of `asm_fprintf'. This construct outputs ! `option0', `option1', `option2', etc., if the value of ! `ASSEMBLER_DIALECT' is zero, one, two, etc. Any special characters within these strings retain their usual meaning. If there are fewer alternatives within the braces than the value of ! `ASSEMBLER_DIALECT', the construct outputs nothing. If it's needed ! to print curly braces or `|' character in assembler output ! directly, `%{', `%}' and `%|' can be used. ! If you do not define this macro, the characters `{', `|' and `}' ! do not have any special meaning when used in templates or operands ! to `asm_fprintf'. ! Define the macros `REGISTER_PREFIX', `LOCAL_LABEL_PREFIX', ! `USER_LABEL_PREFIX' and `IMMEDIATE_PREFIX' if you can express the variations in assembler language syntax with that mechanism. ! Define `ASSEMBLER_DIALECT' and use the `{option0|option1}' syntax if the syntax variant are larger and involve such things as different opcodes or operand order. *************** otherwise it contains the 'sequence' rtx *** 36127,36134 **** -- Macro: ASM_OUTPUT_REG_POP (STREAM, REGNO) A C expression to output to STREAM some assembler code which will ! pop hard register number REGNO off of the stack. The code need not ! be optimal, since this macro is used only when profiling.  File: gccint.info, Node: Dispatch Tables, Next: Exception Region Output, Prev: Instruction Output, Up: Assembler Format --- 36563,36570 ---- -- Macro: ASM_OUTPUT_REG_POP (STREAM, REGNO) A C expression to output to STREAM some assembler code which will ! pop hard register number REGNO off of the stack. The code need ! not be optimal, since this macro is used only when profiling.  File: gccint.info, Node: Dispatch Tables, Next: Exception Region Output, Prev: Instruction Output, Up: Assembler Format *************** This concerns dispatch tables. *** 36143,36149 **** pseudo-instruction to generate a difference between two labels. VALUE and REL are the numbers of two internal labels. The definitions of these labels are output using ! '(*targetm.asm_out.internal_label)', and they must be printed in the same way here. For example, fprintf (STREAM, "\t.word L%d-L%d\n", --- 36579,36585 ---- pseudo-instruction to generate a difference between two labels. VALUE and REL are the numbers of two internal labels. The definitions of these labels are output using ! `(*targetm.asm_out.internal_label)', and they must be printed in the same way here. For example, fprintf (STREAM, "\t.word L%d-L%d\n", *************** This concerns dispatch tables. *** 36152,36158 **** You must provide this macro on machines where the addresses in a dispatch table are relative to the table's own address. If defined, GCC will also use this macro on all machines when ! producing PIC. BODY is the body of the 'ADDR_DIFF_VEC'; it is provided so that the mode and flags can be read. -- Macro: ASM_OUTPUT_ADDR_VEC_ELT (STREAM, VALUE) --- 36588,36594 ---- You must provide this macro on machines where the addresses in a dispatch table are relative to the table's own address. If defined, GCC will also use this macro on all machines when ! producing PIC. BODY is the body of the `ADDR_DIFF_VEC'; it is provided so that the mode and flags can be read. -- Macro: ASM_OUTPUT_ADDR_VEC_ELT (STREAM, VALUE) *************** This concerns dispatch tables. *** 36163,36192 **** stream STREAM an assembler pseudo-instruction to generate a reference to a label. VALUE is the number of an internal label whose definition is output using ! '(*targetm.asm_out.internal_label)'. For example, fprintf (STREAM, "\t.word L%d\n", VALUE) -- Macro: ASM_OUTPUT_CASE_LABEL (STREAM, PREFIX, NUM, TABLE) Define this if the label before a jump-table needs to be output specially. The first three arguments are the same as for ! '(*targetm.asm_out.internal_label)'; the fourth argument is the ! jump-table which follows (a 'jump_table_data' containing an ! 'addr_vec' or 'addr_diff_vec'). ! This feature is used on system V to output a 'swbeg' statement for the table. If this macro is not defined, these labels are output with ! '(*targetm.asm_out.internal_label)'. -- Macro: ASM_OUTPUT_CASE_END (STREAM, NUM, TABLE) Define this if something special must be output at the end of a jump-table. The definition should be a C statement to be executed after the assembler code for the table is written. It should write ! the appropriate code to stdio stream STREAM. The argument TABLE is ! the jump-table insn, and NUM is the label-number of the preceding ! label. If this macro is not defined, nothing special is output at the end of the jump-table. --- 36599,36628 ---- stream STREAM an assembler pseudo-instruction to generate a reference to a label. VALUE is the number of an internal label whose definition is output using ! `(*targetm.asm_out.internal_label)'. For example, fprintf (STREAM, "\t.word L%d\n", VALUE) -- Macro: ASM_OUTPUT_CASE_LABEL (STREAM, PREFIX, NUM, TABLE) Define this if the label before a jump-table needs to be output specially. The first three arguments are the same as for ! `(*targetm.asm_out.internal_label)'; the fourth argument is the ! jump-table which follows (a `jump_table_data' containing an ! `addr_vec' or `addr_diff_vec'). ! This feature is used on system V to output a `swbeg' statement for the table. If this macro is not defined, these labels are output with ! `(*targetm.asm_out.internal_label)'. -- Macro: ASM_OUTPUT_CASE_END (STREAM, NUM, TABLE) Define this if something special must be output at the end of a jump-table. The definition should be a C statement to be executed after the assembler code for the table is written. It should write ! the appropriate code to stdio stream STREAM. The argument TABLE ! is the jump-table insn, and NUM is the label-number of the ! preceding label. If this macro is not defined, nothing special is output at the end of the jump-table. *************** This concerns dispatch tables. *** 36198,36205 **** should write the appropriate label, for the FDE associated with the function declaration DECL, to the stdio stream STREAM. The third argument, FOR_EH, is a boolean: true if this is for an exception ! table. The fourth argument, EMPTY, is a boolean: true if this is a ! placeholder label for an omitted FDE. The default is that FDEs are not given nonlocal labels. --- 36634,36641 ---- should write the appropriate label, for the FDE associated with the function declaration DECL, to the stdio stream STREAM. The third argument, FOR_EH, is a boolean: true if this is for an exception ! table. The fourth argument, EMPTY, is a boolean: true if this is ! a placeholder label for an omitted FDE. The default is that FDEs are not given nonlocal labels. *************** This concerns dispatch tables. *** 36212,36232 **** -- Target Hook: void TARGET_ASM_EMIT_EXCEPT_PERSONALITY (rtx PERSONALITY) ! If the target implements 'TARGET_ASM_UNWIND_EMIT', this hook may be ! used to emit a directive to install a personality hook into the ! unwind info. This hook should not be used if dwarf2 unwind info is ! used. -- Target Hook: void TARGET_ASM_UNWIND_EMIT (FILE *STREAM, rtx_insn *INSN) This target hook emits assembly directives required to unwind the given instruction. This is only used when ! 'TARGET_EXCEPT_UNWIND_INFO' returns 'UI_TARGET'. -- Target Hook: bool TARGET_ASM_UNWIND_EMIT_BEFORE_INSN ! True if the 'TARGET_ASM_UNWIND_EMIT' hook should be called before ! the assembly for INSN has been emitted, false if the hook should be ! called afterward.  File: gccint.info, Node: Exception Region Output, Next: Alignment Output, Prev: Dispatch Tables, Up: Assembler Format --- 36648,36668 ---- -- Target Hook: void TARGET_ASM_EMIT_EXCEPT_PERSONALITY (rtx PERSONALITY) ! If the target implements `TARGET_ASM_UNWIND_EMIT', this hook may ! be used to emit a directive to install a personality hook into the ! unwind info. This hook should not be used if dwarf2 unwind info ! is used. -- Target Hook: void TARGET_ASM_UNWIND_EMIT (FILE *STREAM, rtx_insn *INSN) This target hook emits assembly directives required to unwind the given instruction. This is only used when ! `TARGET_EXCEPT_UNWIND_INFO' returns `UI_TARGET'. -- Target Hook: bool TARGET_ASM_UNWIND_EMIT_BEFORE_INSN ! True if the `TARGET_ASM_UNWIND_EMIT' hook should be called before ! the assembly for INSN has been emitted, false if the hook should ! be called afterward.  File: gccint.info, Node: Exception Region Output, Next: Alignment Output, Prev: Dispatch Tables, Up: Assembler Format *************** region. *** 36241,36248 **** If defined, a C string constant for the name of the section containing exception handling frame unwind information. If not defined, GCC will provide a default definition if the target ! supports named sections. 'crtstuff.c' uses this macro to switch to ! the appropriate section. You should define this symbol if your target supports DWARF 2 frame unwind information and the default definition does not work. --- 36677,36684 ---- If defined, a C string constant for the name of the section containing exception handling frame unwind information. If not defined, GCC will provide a default definition if the target ! supports named sections. `crtstuff.c' uses this macro to switch ! to the appropriate section. You should define this symbol if your target supports DWARF 2 frame unwind information and the default definition does not work. *************** region. *** 36253,36259 **** labels and generate code to register the frames. This might be necessary, for instance, if the system linker will ! not place the eh_frames in-between the sentinals from 'crtstuff.c', or if the system linker does garbage collection and sections cannot be marked as not to be collected. --- 36689,36695 ---- labels and generate code to register the frames. This might be necessary, for instance, if the system linker will ! not place the eh_frames in-between the sentinals from `crtstuff.c', or if the system linker does garbage collection and sections cannot be marked as not to be collected. *************** region. *** 36264,36328 **** read-only and read-write sections into a single read-write section. -- Macro: MASK_RETURN_ADDR ! An rtx used to mask the return address found via 'RETURN_ADDR_RTX', ! so that it does not contain any extraneous set bits in it. -- Macro: DWARF2_UNWIND_INFO Define this macro to 0 if your target supports DWARF 2 frame unwind information, but it does not yet work with exception handling. Otherwise, if your target supports this information (if it defines ! 'INCOMING_RETURN_ADDR_RTX' and 'OBJECT_FORMAT_ELF'), GCC will provide a default definition of 1. -- Common Target Hook: enum unwind_info_type TARGET_EXCEPT_UNWIND_INFO (struct gcc_options *OPTS) This hook defines the mechanism that will be used for exception handling by the target. If the target has ABI specified unwind ! tables, the hook should return 'UI_TARGET'. If the target is to ! use the 'setjmp'/'longjmp'-based exception handling scheme, the ! hook should return 'UI_SJLJ'. If the target supports DWARF 2 frame ! unwind information, the hook should return 'UI_DWARF2'. A target may, if exceptions are disabled, choose to return ! 'UI_NONE'. This may end up simplifying other parts of target-specific code. The default implementation of this hook ! never returns 'UI_NONE'. Note that the value returned by this hook should be constant. It should not depend on anything except the command-line switches ! described by OPTS. In particular, the setting 'UI_SJLJ' must be fixed at compiler start-up as C pre-processor macros and builtin functions related to exception handling are set up depending on this setting. The default implementation of the hook first honors the ! '--enable-sjlj-exceptions' configure option, then ! 'DWARF2_UNWIND_INFO', and finally defaults to 'UI_SJLJ'. If ! 'DWARF2_UNWIND_INFO' depends on command-line options, the target must define this hook so that OPTS is used correctly. -- Common Target Hook: bool TARGET_UNWIND_TABLES_DEFAULT ! This variable should be set to 'true' if the target ABI requires ! unwinding tables even when exceptions are not used. It must not be ! modified by command-line option processing. -- Macro: DONT_USE_BUILTIN_SETJMP ! Define this macro to 1 if the 'setjmp'/'longjmp'-based scheme ! should use the 'setjmp'/'longjmp' functions from the C library ! instead of the '__builtin_setjmp'/'__builtin_longjmp' machinery. -- Macro: JMP_BUF_SIZE ! This macro has no effect unless 'DONT_USE_BUILTIN_SETJMP' is also ! defined. Define this macro if the default size of 'jmp_buf' buffer ! for the 'setjmp'/'longjmp'-based exception handling mechanism is not large enough, or if it is much too large. The default size is ! 'FIRST_PSEUDO_REGISTER * sizeof(void *)'. -- Macro: DWARF_CIE_DATA_ALIGNMENT This macro need only be defined if the target might save registers in the function prologue at an offset to the stack pointer that is ! not aligned to 'UNITS_PER_WORD'. The definition should be the ! negative minimum alignment if 'STACK_GROWS_DOWNWARD' is true, and the positive minimum alignment otherwise. *Note SDB and DWARF::. Only applicable if the target supports DWARF 2 frame unwind information. --- 36700,36765 ---- read-only and read-write sections into a single read-write section. -- Macro: MASK_RETURN_ADDR ! An rtx used to mask the return address found via ! `RETURN_ADDR_RTX', so that it does not contain any extraneous set ! bits in it. -- Macro: DWARF2_UNWIND_INFO Define this macro to 0 if your target supports DWARF 2 frame unwind information, but it does not yet work with exception handling. Otherwise, if your target supports this information (if it defines ! `INCOMING_RETURN_ADDR_RTX' and `OBJECT_FORMAT_ELF'), GCC will provide a default definition of 1. -- Common Target Hook: enum unwind_info_type TARGET_EXCEPT_UNWIND_INFO (struct gcc_options *OPTS) This hook defines the mechanism that will be used for exception handling by the target. If the target has ABI specified unwind ! tables, the hook should return `UI_TARGET'. If the target is to ! use the `setjmp'/`longjmp'-based exception handling scheme, the ! hook should return `UI_SJLJ'. If the target supports DWARF 2 ! frame unwind information, the hook should return `UI_DWARF2'. A target may, if exceptions are disabled, choose to return ! `UI_NONE'. This may end up simplifying other parts of target-specific code. The default implementation of this hook ! never returns `UI_NONE'. Note that the value returned by this hook should be constant. It should not depend on anything except the command-line switches ! described by OPTS. In particular, the setting `UI_SJLJ' must be fixed at compiler start-up as C pre-processor macros and builtin functions related to exception handling are set up depending on this setting. The default implementation of the hook first honors the ! `--enable-sjlj-exceptions' configure option, then ! `DWARF2_UNWIND_INFO', and finally defaults to `UI_SJLJ'. If ! `DWARF2_UNWIND_INFO' depends on command-line options, the target must define this hook so that OPTS is used correctly. -- Common Target Hook: bool TARGET_UNWIND_TABLES_DEFAULT ! This variable should be set to `true' if the target ABI requires ! unwinding tables even when exceptions are not used. It must not ! be modified by command-line option processing. -- Macro: DONT_USE_BUILTIN_SETJMP ! Define this macro to 1 if the `setjmp'/`longjmp'-based scheme ! should use the `setjmp'/`longjmp' functions from the C library ! instead of the `__builtin_setjmp'/`__builtin_longjmp' machinery. -- Macro: JMP_BUF_SIZE ! This macro has no effect unless `DONT_USE_BUILTIN_SETJMP' is also ! defined. Define this macro if the default size of `jmp_buf' buffer ! for the `setjmp'/`longjmp'-based exception handling mechanism is not large enough, or if it is much too large. The default size is ! `FIRST_PSEUDO_REGISTER * sizeof(void *)'. -- Macro: DWARF_CIE_DATA_ALIGNMENT This macro need only be defined if the target might save registers in the function prologue at an offset to the stack pointer that is ! not aligned to `UNITS_PER_WORD'. The definition should be the ! negative minimum alignment if `STACK_GROWS_DOWNWARD' is true, and the positive minimum alignment otherwise. *Note SDB and DWARF::. Only applicable if the target supports DWARF 2 frame unwind information. *************** region. *** 36330,36336 **** -- Target Hook: bool TARGET_TERMINATE_DW2_EH_FRAME_INFO Contains the value true if the target should add a zero word onto the end of a Dwarf-2 frame info section when used for exception ! handling. Default value is false if 'EH_FRAME_SECTION_NAME' is defined, and true otherwise. -- Target Hook: rtx TARGET_DWARF_REGISTER_SPAN (rtx REG) --- 36767,36773 ---- -- Target Hook: bool TARGET_TERMINATE_DW2_EH_FRAME_INFO Contains the value true if the target should add a zero word onto the end of a Dwarf-2 frame info section when used for exception ! handling. Default value is false if `EH_FRAME_SECTION_NAME' is defined, and true otherwise. -- Target Hook: rtx TARGET_DWARF_REGISTER_SPAN (rtx REG) *************** region. *** 36339,36346 **** if the register and its mode are represented in Dwarf in non-contiguous locations, or if the register should be represented in more than one register in Dwarf. Otherwise, this hook should ! return 'NULL_RTX'. If not defined, the default is to return ! 'NULL_RTX'. -- Target Hook: machine_mode TARGET_DWARF_FRAME_REG_MODE (int REGNO) Given a register, this hook should return the mode which the --- 36776,36783 ---- if the register and its mode are represented in Dwarf in non-contiguous locations, or if the register should be represented in more than one register in Dwarf. Otherwise, this hook should ! return `NULL_RTX'. If not defined, the default is to return ! `NULL_RTX'. -- Target Hook: machine_mode TARGET_DWARF_FRAME_REG_MODE (int REGNO) Given a register, this hook should return the mode which the *************** region. *** 36352,36372 **** If some registers are represented in Dwarf-2 unwind information in multiple pieces, define this hook to fill in information about the sizes of those pieces in the table used by the unwinder at runtime. ! It will be called by 'expand_builtin_init_dwarf_reg_sizes' after filling in a single size corresponding to each hard register; ADDRESS is the address of the table. -- Target Hook: bool TARGET_ASM_TTYPE (rtx SYM) This hook is used to output a reference from a frame unwinding table to the type_info object identified by SYM. It should return ! 'true' if the reference was output. Returning 'false' will cause the reference to be output using the normal Dwarf2 routines. -- Target Hook: bool TARGET_ARM_EABI_UNWINDER ! This flag should be set to 'true' on targets that use an ARM EABI ! based unwinding library, and 'false' on other targets. This effects the format of unwinding tables, and how the unwinder in ! entered after running a cleanup. The default is 'false'.  File: gccint.info, Node: Alignment Output, Prev: Exception Region Output, Up: Assembler Format --- 36789,36809 ---- If some registers are represented in Dwarf-2 unwind information in multiple pieces, define this hook to fill in information about the sizes of those pieces in the table used by the unwinder at runtime. ! It will be called by `expand_builtin_init_dwarf_reg_sizes' after filling in a single size corresponding to each hard register; ADDRESS is the address of the table. -- Target Hook: bool TARGET_ASM_TTYPE (rtx SYM) This hook is used to output a reference from a frame unwinding table to the type_info object identified by SYM. It should return ! `true' if the reference was output. Returning `false' will cause the reference to be output using the normal Dwarf2 routines. -- Target Hook: bool TARGET_ARM_EABI_UNWINDER ! This flag should be set to `true' on targets that use an ARM EABI ! based unwinding library, and `false' on other targets. This effects the format of unwinding tables, and how the unwinder in ! entered after running a cleanup. The default is `false'.  File: gccint.info, Node: Alignment Output, Prev: Exception Region Output, Up: Assembler Format *************** This describes commands for alignment. *** 36386,36402 **** Unless it's necessary to inspect the LABEL parameter, it is better to set the variable ALIGN_JUMPS in the target's ! 'TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the ! user's selection in ALIGN_JUMPS in a 'JUMP_ALIGN' implementation. -- Target Hook: int TARGET_ASM_JUMP_ALIGN_MAX_SKIP (rtx_insn *LABEL) The maximum number of bytes to skip before LABEL when applying ! 'JUMP_ALIGN'. This works only if 'ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: LABEL_ALIGN_AFTER_BARRIER (LABEL) The alignment (log base 2) to put in front of LABEL, which follows ! a 'BARRIER'. This macro need not be defined if you don't want any special alignment to be done at such a time. Most machine descriptions do --- 36823,36839 ---- Unless it's necessary to inspect the LABEL parameter, it is better to set the variable ALIGN_JUMPS in the target's ! `TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the ! user's selection in ALIGN_JUMPS in a `JUMP_ALIGN' implementation. -- Target Hook: int TARGET_ASM_JUMP_ALIGN_MAX_SKIP (rtx_insn *LABEL) The maximum number of bytes to skip before LABEL when applying ! `JUMP_ALIGN'. This works only if `ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: LABEL_ALIGN_AFTER_BARRIER (LABEL) The alignment (log base 2) to put in front of LABEL, which follows ! a `BARRIER'. This macro need not be defined if you don't want any special alignment to be done at such a time. Most machine descriptions do *************** This describes commands for alignment. *** 36405,36412 **** -- Target Hook: int TARGET_ASM_LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP (rtx_insn *LABEL) The maximum number of bytes to skip before LABEL when applying ! 'LABEL_ALIGN_AFTER_BARRIER'. This works only if ! 'ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: LOOP_ALIGN (LABEL) The alignment (log base 2) to put in front of LABEL that heads a --- 36842,36849 ---- -- Target Hook: int TARGET_ASM_LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP (rtx_insn *LABEL) The maximum number of bytes to skip before LABEL when applying ! `LABEL_ALIGN_AFTER_BARRIER'. This works only if ! `ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: LOOP_ALIGN (LABEL) The alignment (log base 2) to put in front of LABEL that heads a *************** This describes commands for alignment. *** 36417,36465 **** not currently define the macro. Unless it's necessary to inspect the LABEL parameter, it is better ! to set the variable 'align_loops' in the target's ! 'TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the ! user's selection in 'align_loops' in a 'LOOP_ALIGN' implementation. -- Target Hook: int TARGET_ASM_LOOP_ALIGN_MAX_SKIP (rtx_insn *LABEL) ! The maximum number of bytes to skip when applying 'LOOP_ALIGN' to ! LABEL. This works only if 'ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: LABEL_ALIGN (LABEL) The alignment (log base 2) to put in front of LABEL. If ! 'LABEL_ALIGN_AFTER_BARRIER' / 'LOOP_ALIGN' specify a different alignment, the maximum of the specified values is used. Unless it's necessary to inspect the LABEL parameter, it is better ! to set the variable 'align_labels' in the target's ! 'TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the ! user's selection in 'align_labels' in a 'LABEL_ALIGN' implementation. -- Target Hook: int TARGET_ASM_LABEL_ALIGN_MAX_SKIP (rtx_insn *LABEL) ! The maximum number of bytes to skip when applying 'LABEL_ALIGN' to ! LABEL. This works only if 'ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: ASM_OUTPUT_SKIP (STREAM, NBYTES) A C statement to output to the stdio stream STREAM an assembler ! instruction to advance the location counter by NBYTES bytes. Those ! bytes should be zero when loaded. NBYTES will be a C expression of ! type 'unsigned HOST_WIDE_INT'. -- Macro: ASM_NO_SKIP_IN_TEXT ! Define this macro if 'ASM_OUTPUT_SKIP' should not be used in the text section because it fails to put zeros in the bytes that are ! skipped. This is true on many Unix systems, where the pseudo-op to ! skip bytes produces no-op instructions rather than zeros when used ! in the text section. -- Macro: ASM_OUTPUT_ALIGN (STREAM, POWER) A C statement to output to the stdio stream STREAM an assembler command to advance the location counter to a multiple of 2 to the ! POWER bytes. POWER will be a C expression of type 'int'. -- Macro: ASM_OUTPUT_ALIGN_WITH_NOP (STREAM, POWER) ! Like 'ASM_OUTPUT_ALIGN', except that the "nop" instruction is used for padding, if necessary. -- Macro: ASM_OUTPUT_MAX_SKIP_ALIGN (STREAM, POWER, MAX_SKIP) --- 36854,36902 ---- not currently define the macro. Unless it's necessary to inspect the LABEL parameter, it is better ! to set the variable `align_loops' in the target's ! `TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the ! user's selection in `align_loops' in a `LOOP_ALIGN' implementation. -- Target Hook: int TARGET_ASM_LOOP_ALIGN_MAX_SKIP (rtx_insn *LABEL) ! The maximum number of bytes to skip when applying `LOOP_ALIGN' to ! LABEL. This works only if `ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: LABEL_ALIGN (LABEL) The alignment (log base 2) to put in front of LABEL. If ! `LABEL_ALIGN_AFTER_BARRIER' / `LOOP_ALIGN' specify a different alignment, the maximum of the specified values is used. Unless it's necessary to inspect the LABEL parameter, it is better ! to set the variable `align_labels' in the target's ! `TARGET_OPTION_OVERRIDE'. Otherwise, you should try to honor the ! user's selection in `align_labels' in a `LABEL_ALIGN' implementation. -- Target Hook: int TARGET_ASM_LABEL_ALIGN_MAX_SKIP (rtx_insn *LABEL) ! The maximum number of bytes to skip when applying `LABEL_ALIGN' to ! LABEL. This works only if `ASM_OUTPUT_MAX_SKIP_ALIGN' is defined. -- Macro: ASM_OUTPUT_SKIP (STREAM, NBYTES) A C statement to output to the stdio stream STREAM an assembler ! instruction to advance the location counter by NBYTES bytes. ! Those bytes should be zero when loaded. NBYTES will be a C ! expression of type `unsigned HOST_WIDE_INT'. -- Macro: ASM_NO_SKIP_IN_TEXT ! Define this macro if `ASM_OUTPUT_SKIP' should not be used in the text section because it fails to put zeros in the bytes that are ! skipped. This is true on many Unix systems, where the pseudo-op ! to skip bytes produces no-op instructions rather than zeros when ! used in the text section. -- Macro: ASM_OUTPUT_ALIGN (STREAM, POWER) A C statement to output to the stdio stream STREAM an assembler command to advance the location counter to a multiple of 2 to the ! POWER bytes. POWER will be a C expression of type `int'. -- Macro: ASM_OUTPUT_ALIGN_WITH_NOP (STREAM, POWER) ! Like `ASM_OUTPUT_ALIGN', except that the "nop" instruction is used for padding, if necessary. -- Macro: ASM_OUTPUT_MAX_SKIP_ALIGN (STREAM, POWER, MAX_SKIP) *************** This describes commands for alignment. *** 36467,36473 **** command to advance the location counter to a multiple of 2 to the POWER bytes, but only if MAX_SKIP or fewer bytes are needed to satisfy the alignment request. POWER and MAX_SKIP will be a C ! expression of type 'int'.  File: gccint.info, Node: Debugging Info, Next: Floating Point, Prev: Assembler Format, Up: Target Macros --- 36904,36910 ---- command to advance the location counter to a multiple of 2 to the POWER bytes, but only if MAX_SKIP or fewer bytes are needed to satisfy the alignment request. POWER and MAX_SKIP will be a C ! expression of type `int'.  File: gccint.info, Node: Debugging Info, Next: Floating Point, Prev: Assembler Format, Up: Target Macros *************** These macros affect all debugging format *** 36496,36515 **** -- Macro: DBX_REGISTER_NUMBER (REGNO) A C expression that returns the DBX register number for the ! compiler register number REGNO. In the default macro provided, the ! value of this expression will be REGNO itself. But sometimes there ! are some registers that the compiler knows about and DBX does not, ! or vice versa. In such cases, some register may need to have one ! number in the compiler and another for DBX. If two registers have consecutive numbers inside GCC, and they can be used as a pair to hold a multiword value, then they _must_ have ! consecutive numbers after renumbering with 'DBX_REGISTER_NUMBER'. Otherwise, debuggers will be unable to access such a pair, because ! they expect register pairs to be consecutive in their own numbering ! scheme. ! If you find yourself defining 'DBX_REGISTER_NUMBER' in way that does not preserve register pairs, then what you must do instead is redefine the actual register numbering scheme. --- 36933,36952 ---- -- Macro: DBX_REGISTER_NUMBER (REGNO) A C expression that returns the DBX register number for the ! compiler register number REGNO. In the default macro provided, ! the value of this expression will be REGNO itself. But sometimes ! there are some registers that the compiler knows about and DBX ! does not, or vice versa. In such cases, some register may need to ! have one number in the compiler and another for DBX. If two registers have consecutive numbers inside GCC, and they can be used as a pair to hold a multiword value, then they _must_ have ! consecutive numbers after renumbering with `DBX_REGISTER_NUMBER'. Otherwise, debuggers will be unable to access such a pair, because ! they expect register pairs to be consecutive in their own ! numbering scheme. ! If you find yourself defining `DBX_REGISTER_NUMBER' in way that does not preserve register pairs, then what you must do instead is redefine the actual register numbering scheme. *************** These macros affect all debugging format *** 36520,36526 **** and gives the offset from the frame-pointer. This is required for targets that produce debugging output for DBX or COFF-style debugging output for SDB and allow the frame-pointer to be ! eliminated when the '-g' options is used. -- Macro: DEBUGGER_ARG_OFFSET (OFFSET, X) A C expression that returns the integer offset value for an --- 36957,36963 ---- and gives the offset from the frame-pointer. This is required for targets that produce debugging output for DBX or COFF-style debugging output for SDB and allow the frame-pointer to be ! eliminated when the `-g' options is used. -- Macro: DEBUGGER_ARG_OFFSET (OFFSET, X) A C expression that returns the integer offset value for an *************** These macros affect all debugging format *** 36529,36549 **** -- Macro: PREFERRED_DEBUGGING_TYPE A C expression that returns the type of debugging output GCC should ! produce when the user specifies just '-g'. Define this if you have ! arranged for GCC to support more than one format of debugging ! output. Currently, the allowable values are 'DBX_DEBUG', ! 'SDB_DEBUG', 'DWARF_DEBUG', 'DWARF2_DEBUG', 'XCOFF_DEBUG', ! 'VMS_DEBUG', and 'VMS_AND_DWARF2_DEBUG'. ! When the user specifies '-ggdb', GCC normally also uses the value of this macro to select the debugging output format, but with two ! exceptions. If 'DWARF2_DEBUGGING_INFO' is defined, GCC uses the ! value 'DWARF2_DEBUG'. Otherwise, if 'DBX_DEBUGGING_INFO' is ! defined, GCC uses 'DBX_DEBUG'. The value of this macro only affects the default debugging output; the user can always get a specific type of output by using ! '-gstabs', '-gcoff', '-gdwarf-2', '-gxcoff', or '-gvms'.  File: gccint.info, Node: DBX Options, Next: DBX Hooks, Prev: All Debuggers, Up: Debugging Info --- 36966,36986 ---- -- Macro: PREFERRED_DEBUGGING_TYPE A C expression that returns the type of debugging output GCC should ! produce when the user specifies just `-g'. Define this if you ! have arranged for GCC to support more than one format of debugging ! output. Currently, the allowable values are `DBX_DEBUG', ! `SDB_DEBUG', `DWARF_DEBUG', `DWARF2_DEBUG', `XCOFF_DEBUG', ! `VMS_DEBUG', and `VMS_AND_DWARF2_DEBUG'. ! When the user specifies `-ggdb', GCC normally also uses the value of this macro to select the debugging output format, but with two ! exceptions. If `DWARF2_DEBUGGING_INFO' is defined, GCC uses the ! value `DWARF2_DEBUG'. Otherwise, if `DBX_DEBUGGING_INFO' is ! defined, GCC uses `DBX_DEBUG'. The value of this macro only affects the default debugging output; the user can always get a specific type of output by using ! `-gstabs', `-gcoff', `-gdwarf-2', `-gxcoff', or `-gvms'.  File: gccint.info, Node: DBX Options, Next: DBX Hooks, Prev: All Debuggers, Up: Debugging Info *************** File: gccint.info, Node: DBX Options, *** 36554,36565 **** These are specific options for DBX output. -- Macro: DBX_DEBUGGING_INFO ! Define this macro if GCC should produce debugging output for DBX in ! response to the '-g' option. -- Macro: XCOFF_DEBUGGING_INFO Define this macro if GCC should produce XCOFF format debugging ! output in response to the '-g' option. This is a variant of DBX format. -- Macro: DEFAULT_GDB_EXTENSIONS --- 36991,37002 ---- These are specific options for DBX output. -- Macro: DBX_DEBUGGING_INFO ! Define this macro if GCC should produce debugging output for DBX ! in response to the `-g' option. -- Macro: XCOFF_DEBUGGING_INFO Define this macro if GCC should produce XCOFF format debugging ! output in response to the `-g' option. This is a variant of DBX format. -- Macro: DEFAULT_GDB_EXTENSIONS *************** These are specific options for DBX outpu *** 36570,36606 **** information if there is any occasion to. -- Macro: DEBUG_SYMS_TEXT ! Define this macro if all '.stabs' commands should be output while in the text section. -- Macro: ASM_STABS_OP ! A C string constant, including spacing, naming the assembler pseudo ! op to use instead of '"\t.stabs\t"' to define an ordinary debugging ! symbol. If you don't define this macro, '"\t.stabs\t"' is used. ! This macro applies only to DBX debugging information format. -- Macro: ASM_STABD_OP ! A C string constant, including spacing, naming the assembler pseudo ! op to use instead of '"\t.stabd\t"' to define a debugging symbol ! whose value is the current location. If you don't define this ! macro, '"\t.stabd\t"' is used. This macro applies only to DBX ! debugging information format. -- Macro: ASM_STABN_OP ! A C string constant, including spacing, naming the assembler pseudo ! op to use instead of '"\t.stabn\t"' to define a debugging symbol ! with no name. If you don't define this macro, '"\t.stabn\t"' is ! used. This macro applies only to DBX debugging information format. -- Macro: DBX_NO_XREFS Define this macro if DBX on your system does not support the ! construct 'xsTAGNAME'. On some systems, this construct is used to describe a forward reference to a structure named TAGNAME. On other systems, this construct is not supported at all. -- Macro: DBX_CONTIN_LENGTH A symbol name in DBX-format debugging information is normally ! continued (split into two separate '.stabs' directives) when it exceeds a certain length (by default, 80 characters). On some operating systems, DBX requires this splitting; on others, splitting must not be done. You can inhibit splitting by defining --- 37007,37045 ---- information if there is any occasion to. -- Macro: DEBUG_SYMS_TEXT ! Define this macro if all `.stabs' commands should be output while in the text section. -- Macro: ASM_STABS_OP ! A C string constant, including spacing, naming the assembler ! pseudo op to use instead of `"\t.stabs\t"' to define an ordinary ! debugging symbol. If you don't define this macro, `"\t.stabs\t"' ! is used. This macro applies only to DBX debugging information ! format. -- Macro: ASM_STABD_OP ! A C string constant, including spacing, naming the assembler ! pseudo op to use instead of `"\t.stabd\t"' to define a debugging ! symbol whose value is the current location. If you don't define ! this macro, `"\t.stabd\t"' is used. This macro applies only to ! DBX debugging information format. -- Macro: ASM_STABN_OP ! A C string constant, including spacing, naming the assembler ! pseudo op to use instead of `"\t.stabn\t"' to define a debugging ! symbol with no name. If you don't define this macro, ! `"\t.stabn\t"' is used. This macro applies only to DBX debugging ! information format. -- Macro: DBX_NO_XREFS Define this macro if DBX on your system does not support the ! construct `xsTAGNAME'. On some systems, this construct is used to describe a forward reference to a structure named TAGNAME. On other systems, this construct is not supported at all. -- Macro: DBX_CONTIN_LENGTH A symbol name in DBX-format debugging information is normally ! continued (split into two separate `.stabs' directives) when it exceeds a certain length (by default, 80 characters). On some operating systems, DBX requires this splitting; on others, splitting must not be done. You can inhibit splitting by defining *************** These are specific options for DBX outpu *** 36609,36669 **** length you desire. -- Macro: DBX_CONTIN_CHAR ! Normally continuation is indicated by adding a '\' character to the ! end of a '.stabs' string when a continuation follows. To use a ! different character instead, define this macro as a character constant for the character you want to use. Do not define this macro if backslash is correct for your system. -- Macro: DBX_STATIC_STAB_DATA_SECTION Define this macro if it is necessary to go to the data section ! before outputting the '.stabs' pseudo-op for a non-global static variable. -- Macro: DBX_TYPE_DECL_STABS_CODE ! The value to use in the "code" field of the '.stabs' directive for ! a typedef. The default is 'N_LSYM'. -- Macro: DBX_STATIC_CONST_VAR_CODE ! The value to use in the "code" field of the '.stabs' directive for a static variable located in the text section. DBX format does not ! provide any "right" way to do this. The default is 'N_FUN'. -- Macro: DBX_REGPARM_STABS_CODE ! The value to use in the "code" field of the '.stabs' directive for a parameter passed in registers. DBX format does not provide any ! "right" way to do this. The default is 'N_RSYM'. -- Macro: DBX_REGPARM_STABS_LETTER The letter to use in DBX symbol data to identify a symbol as a parameter passed in registers. DBX format does not customarily ! provide any way to do this. The default is ''P''. -- Macro: DBX_FUNCTION_FIRST Define this macro if the DBX information for a function and its arguments should precede the assembler code for the function. ! Normally, in DBX format, the debugging information entirely follows ! the assembler code. -- Macro: DBX_BLOCKS_FUNCTION_RELATIVE Define this macro, with value 1, if the value of a symbol ! describing the scope of a block ('N_LBRAC' or 'N_RBRAC') should be relative to the start of the enclosing function. Normally, GCC uses an absolute address. -- Macro: DBX_LINES_FUNCTION_RELATIVE Define this macro, with value 1, if the value of a symbol ! indicating the current line number ('N_SLINE') should be relative to the start of the enclosing function. Normally, GCC uses an absolute address. -- Macro: DBX_USE_BINCL ! Define this macro if GCC should generate 'N_BINCL' and 'N_EINCL' stabs for included header files, as on Sun systems. This macro ! also directs GCC to output a type number as a pair of a file number ! and a type number within the file. Normally, GCC does not generate ! 'N_BINCL' or 'N_EINCL' stabs, and it outputs a single number for a ! type number.  File: gccint.info, Node: DBX Hooks, Next: File Names and DBX, Prev: DBX Options, Up: Debugging Info --- 37048,37108 ---- length you desire. -- Macro: DBX_CONTIN_CHAR ! Normally continuation is indicated by adding a `\' character to ! the end of a `.stabs' string when a continuation follows. To use ! a different character instead, define this macro as a character constant for the character you want to use. Do not define this macro if backslash is correct for your system. -- Macro: DBX_STATIC_STAB_DATA_SECTION Define this macro if it is necessary to go to the data section ! before outputting the `.stabs' pseudo-op for a non-global static variable. -- Macro: DBX_TYPE_DECL_STABS_CODE ! The value to use in the "code" field of the `.stabs' directive for ! a typedef. The default is `N_LSYM'. -- Macro: DBX_STATIC_CONST_VAR_CODE ! The value to use in the "code" field of the `.stabs' directive for a static variable located in the text section. DBX format does not ! provide any "right" way to do this. The default is `N_FUN'. -- Macro: DBX_REGPARM_STABS_CODE ! The value to use in the "code" field of the `.stabs' directive for a parameter passed in registers. DBX format does not provide any ! "right" way to do this. The default is `N_RSYM'. -- Macro: DBX_REGPARM_STABS_LETTER The letter to use in DBX symbol data to identify a symbol as a parameter passed in registers. DBX format does not customarily ! provide any way to do this. The default is `'P''. -- Macro: DBX_FUNCTION_FIRST Define this macro if the DBX information for a function and its arguments should precede the assembler code for the function. ! Normally, in DBX format, the debugging information entirely ! follows the assembler code. -- Macro: DBX_BLOCKS_FUNCTION_RELATIVE Define this macro, with value 1, if the value of a symbol ! describing the scope of a block (`N_LBRAC' or `N_RBRAC') should be relative to the start of the enclosing function. Normally, GCC uses an absolute address. -- Macro: DBX_LINES_FUNCTION_RELATIVE Define this macro, with value 1, if the value of a symbol ! indicating the current line number (`N_SLINE') should be relative to the start of the enclosing function. Normally, GCC uses an absolute address. -- Macro: DBX_USE_BINCL ! Define this macro if GCC should generate `N_BINCL' and `N_EINCL' stabs for included header files, as on Sun systems. This macro ! also directs GCC to output a type number as a pair of a file ! number and a type number within the file. Normally, GCC does not ! generate `N_BINCL' or `N_EINCL' stabs, and it outputs a single ! number for a type number.  File: gccint.info, Node: DBX Hooks, Next: File Names and DBX, Prev: DBX Options, Up: Debugging Info *************** These are hooks for DBX format. *** 36677,36697 **** A C statement to output DBX debugging information before code for line number LINE of the current source file to the stdio stream STREAM. COUNTER is the number of time the macro was invoked, ! including the current invocation; it is intended to generate unique ! labels in the assembly output. This macro should not be defined if the default output is correct, or if it can be made correct by defining ! 'DBX_LINES_FUNCTION_RELATIVE'. -- Macro: NO_DBX_FUNCTION_END Some stabs encapsulation formats (in particular ECOFF), cannot ! handle the '.stabs "",N_FUN,,0,0,Lscope-function-1' gdb dbx extension construct. On those machines, define this macro to turn this feature off without disturbing the rest of the gdb extensions. -- Macro: NO_DBX_BNSYM_ENSYM ! Some assemblers cannot handle the '.stabd BNSYM/ENSYM,0,0' gdb dbx extension construct. On those machines, define this macro to turn this feature off without disturbing the rest of the gdb extensions. --- 37116,37136 ---- A C statement to output DBX debugging information before code for line number LINE of the current source file to the stdio stream STREAM. COUNTER is the number of time the macro was invoked, ! including the current invocation; it is intended to generate ! unique labels in the assembly output. This macro should not be defined if the default output is correct, or if it can be made correct by defining ! `DBX_LINES_FUNCTION_RELATIVE'. -- Macro: NO_DBX_FUNCTION_END Some stabs encapsulation formats (in particular ECOFF), cannot ! handle the `.stabs "",N_FUN,,0,0,Lscope-function-1' gdb dbx extension construct. On those machines, define this macro to turn this feature off without disturbing the rest of the gdb extensions. -- Macro: NO_DBX_BNSYM_ENSYM ! Some assemblers cannot handle the `.stabd BNSYM/ENSYM,0,0' gdb dbx extension construct. On those machines, define this macro to turn this feature off without disturbing the rest of the gdb extensions. *************** This describes file names in DBX format. *** 36713,36721 **** DBX debugging information is appropriate. It may be necessary to refer to a label equal to the beginning of ! the text section. You can use 'assemble_name (stream, ! ltext_label_name)' to do so. If you do this, you must also set the ! variable USED_LTEXT_LABEL_NAME to 'true'. -- Macro: NO_DBX_MAIN_SOURCE_DIRECTORY Define this macro, with value 1, if GCC should not emit an --- 37152,37160 ---- DBX debugging information is appropriate. It may be necessary to refer to a label equal to the beginning of ! the text section. You can use `assemble_name (stream, ! ltext_label_name)' to do so. If you do this, you must also set ! the variable USED_LTEXT_LABEL_NAME to `true'. -- Macro: NO_DBX_MAIN_SOURCE_DIRECTORY Define this macro, with value 1, if GCC should not emit an *************** This describes file names in DBX format. *** 36725,36745 **** -- Macro: NO_DBX_GCC_MARKER Define this macro, with value 1, if GCC should not emit an indication that this object file was compiled by GCC. The default ! is to emit an 'N_OPT' stab at the beginning of every source file, ! with 'gcc2_compiled.' for the string and value 0. -- Macro: DBX_OUTPUT_MAIN_SOURCE_FILE_END (STREAM, NAME) A C statement to output DBX debugging information at the end of ! compilation of the main source file NAME. Output should be written ! to the stdio stream STREAM. If you don't define this macro, nothing special is output at the end of compilation, which is correct for most machines. -- Macro: DBX_OUTPUT_NULL_N_SO_AT_MAIN_SOURCE_FILE_END Define this macro _instead of_ defining ! 'DBX_OUTPUT_MAIN_SOURCE_FILE_END', if what needs to be output at ! the end of compilation is an 'N_SO' stab with an empty string, whose value is the highest absolute text address in the file.  --- 37164,37184 ---- -- Macro: NO_DBX_GCC_MARKER Define this macro, with value 1, if GCC should not emit an indication that this object file was compiled by GCC. The default ! is to emit an `N_OPT' stab at the beginning of every source file, ! with `gcc2_compiled.' for the string and value 0. -- Macro: DBX_OUTPUT_MAIN_SOURCE_FILE_END (STREAM, NAME) A C statement to output DBX debugging information at the end of ! compilation of the main source file NAME. Output should be ! written to the stdio stream STREAM. If you don't define this macro, nothing special is output at the end of compilation, which is correct for most machines. -- Macro: DBX_OUTPUT_NULL_N_SO_AT_MAIN_SOURCE_FILE_END Define this macro _instead of_ defining ! `DBX_OUTPUT_MAIN_SOURCE_FILE_END', if what needs to be output at ! the end of compilation is an `N_SO' stab with an empty string, whose value is the highest absolute text address in the file.  *************** Here are macros for SDB and DWARF output *** 36752,36793 **** -- Macro: SDB_DEBUGGING_INFO Define this macro to 1 if GCC should produce COFF-style debugging ! output for SDB in response to the '-g' option. -- Macro: DWARF2_DEBUGGING_INFO Define this macro if GCC should produce dwarf version 2 format ! debugging output in response to the '-g' option. -- Target Hook: int TARGET_DWARF_CALLING_CONVENTION (const_tree FUNCTION) Define this to enable the dwarf attribute ! 'DW_AT_calling_convention' to be emitted for each function. ! Instead of an integer return the enum value for the 'DW_CC_' tag. To support optional call frame debugging information, you must also ! define 'INCOMING_RETURN_ADDR_RTX' and either set ! 'RTX_FRAME_RELATED_P' on the prologue insns if you use RTL for the ! prologue, or call 'dwarf2out_def_cfa' and 'dwarf2out_reg_save' as ! appropriate from 'TARGET_ASM_FUNCTION_PROLOGUE' if you don't. -- Macro: DWARF2_FRAME_INFO Define this macro to a nonzero value if GCC should always output ! Dwarf 2 frame information. If 'TARGET_EXCEPT_UNWIND_INFO' (*note ! Exception Region Output::) returns 'UI_DWARF2', and exceptions are ! enabled, GCC will output this information not matter how you define ! 'DWARF2_FRAME_INFO'. -- Target Hook: enum unwind_info_type TARGET_DEBUG_UNWIND_INFO (void) This hook defines the mechanism that will be used for describing frame unwind information to the debugger. Normally the hook will ! return 'UI_DWARF2' if DWARF 2 debug information is enabled, and ! return 'UI_NONE' otherwise. ! A target may return 'UI_DWARF2' even when DWARF 2 debug information is disabled in order to always output DWARF 2 frame information. ! A target may return 'UI_TARGET' if it has ABI specified unwind tables. This will suppress generation of the normal debug frame unwind information. --- 37191,37232 ---- -- Macro: SDB_DEBUGGING_INFO Define this macro to 1 if GCC should produce COFF-style debugging ! output for SDB in response to the `-g' option. -- Macro: DWARF2_DEBUGGING_INFO Define this macro if GCC should produce dwarf version 2 format ! debugging output in response to the `-g' option. -- Target Hook: int TARGET_DWARF_CALLING_CONVENTION (const_tree FUNCTION) Define this to enable the dwarf attribute ! `DW_AT_calling_convention' to be emitted for each function. ! Instead of an integer return the enum value for the `DW_CC_' tag. To support optional call frame debugging information, you must also ! define `INCOMING_RETURN_ADDR_RTX' and either set ! `RTX_FRAME_RELATED_P' on the prologue insns if you use RTL for the ! prologue, or call `dwarf2out_def_cfa' and `dwarf2out_reg_save' as ! appropriate from `TARGET_ASM_FUNCTION_PROLOGUE' if you don't. -- Macro: DWARF2_FRAME_INFO Define this macro to a nonzero value if GCC should always output ! Dwarf 2 frame information. If `TARGET_EXCEPT_UNWIND_INFO' (*note ! Exception Region Output::) returns `UI_DWARF2', and exceptions are ! enabled, GCC will output this information not matter how you ! define `DWARF2_FRAME_INFO'. -- Target Hook: enum unwind_info_type TARGET_DEBUG_UNWIND_INFO (void) This hook defines the mechanism that will be used for describing frame unwind information to the debugger. Normally the hook will ! return `UI_DWARF2' if DWARF 2 debug information is enabled, and ! return `UI_NONE' otherwise. ! A target may return `UI_DWARF2' even when DWARF 2 debug information is disabled in order to always output DWARF 2 frame information. ! A target may return `UI_TARGET' if it has ABI specified unwind tables. This will suppress generation of the normal debug frame unwind information. *************** Here are macros for SDB and DWARF output *** 36798,36811 **** works. -- Target Hook: bool TARGET_WANT_DEBUG_PUB_SECTIONS ! True if the '.debug_pubtypes' and '.debug_pubnames' sections should ! be emitted. These sections are not used on most platforms, and in ! particular GDB does not use them. -- Target Hook: bool TARGET_FORCE_AT_COMP_DIR ! True if the 'DW_AT_comp_dir' attribute should be emitted for each ! compilation unit. This attribute is required for the darwin linker ! to emit debug information. -- Target Hook: bool TARGET_DELAY_SCHED2 True if sched2 is not to be run at its normal place. This usually --- 37237,37250 ---- works. -- Target Hook: bool TARGET_WANT_DEBUG_PUB_SECTIONS ! True if the `.debug_pubtypes' and `.debug_pubnames' sections ! should be emitted. These sections are not used on most platforms, ! and in particular GDB does not use them. -- Target Hook: bool TARGET_FORCE_AT_COMP_DIR ! True if the `DW_AT_comp_dir' attribute should be emitted for each ! compilation unit. This attribute is required for the darwin ! linker to emit debug information. -- Target Hook: bool TARGET_DELAY_SCHED2 True if sched2 is not to be run at its normal place. This usually *************** Here are macros for SDB and DWARF output *** 36836,36843 **** -- Macro: ASM_OUTPUT_DWARF_PCREL (STREAM, SIZE, LABEL) A C statement to issue assembly directives that create a ! self-relative reference to the given LABEL, using an integer of the ! given SIZE. -- Macro: ASM_OUTPUT_DWARF_DATAREL (STREAM, SIZE, LABEL) A C statement to issue assembly directives that create a reference --- 37275,37282 ---- -- Macro: ASM_OUTPUT_DWARF_PCREL (STREAM, SIZE, LABEL) A C statement to issue assembly directives that create a ! self-relative reference to the given LABEL, using an integer of ! the given SIZE. -- Macro: ASM_OUTPUT_DWARF_DATAREL (STREAM, SIZE, LABEL) A C statement to issue assembly directives that create a reference *************** Here are macros for SDB and DWARF output *** 36858,36872 **** -- Macro: PUT_SDB_... Define these macros to override the assembler syntax for the ! special SDB assembler directives. See 'sdbout.c' for a list of these macros and their arguments. If the standard syntax is used, you need not define them yourself. -- Macro: SDB_DELIM Some assemblers do not support a semicolon as a delimiter, even between SDB assembler directives. In that case, define this macro ! to be the delimiter to use (usually '\n'). It is not necessary to ! define a new set of 'PUT_SDB_OP' macros if this is the only change required. -- Macro: SDB_ALLOW_UNKNOWN_REFERENCES --- 37297,37311 ---- -- Macro: PUT_SDB_... Define these macros to override the assembler syntax for the ! special SDB assembler directives. See `sdbout.c' for a list of these macros and their arguments. If the standard syntax is used, you need not define them yourself. -- Macro: SDB_DELIM Some assemblers do not support a semicolon as a delimiter, even between SDB assembler directives. In that case, define this macro ! to be the delimiter to use (usually `\n'). It is not necessary to ! define a new set of `PUT_SDB_OP' macros if this is the only change required. -- Macro: SDB_ALLOW_UNKNOWN_REFERENCES *************** Here are macros for SDB and DWARF output *** 36882,36888 **** -- Macro: SDB_OUTPUT_SOURCE_LINE (STREAM, LINE) A C statement to output SDB debugging information before code for line number LINE of the current source file to the stdio stream ! STREAM. The default is to emit an '.ln' directive.  File: gccint.info, Node: VMS Debug, Prev: SDB and DWARF, Up: Debugging Info --- 37321,37327 ---- -- Macro: SDB_OUTPUT_SOURCE_LINE (STREAM, LINE) A C statement to output SDB debugging information before code for line number LINE of the current source file to the stdio stream ! STREAM. The default is to emit an `.ln' directive.  File: gccint.info, Node: VMS Debug, Prev: SDB and DWARF, Up: Debugging Info *************** File: gccint.info, Node: VMS Debug, Pr *** 36893,36904 **** Here are macros for VMS debug format. -- Macro: VMS_DEBUGGING_INFO ! Define this macro if GCC should produce debugging output for VMS in ! response to the '-g' option. The default behavior for VMS is to ! generate minimal debug info for a traceback in the absence of '-g' ! unless explicitly overridden with '-g0'. This behavior is ! controlled by 'TARGET_OPTION_OPTIMIZATION' and ! 'TARGET_OPTION_OVERRIDE'.  File: gccint.info, Node: Floating Point, Next: Mode Switching, Prev: Debugging Info, Up: Target Macros --- 37332,37343 ---- Here are macros for VMS debug format. -- Macro: VMS_DEBUGGING_INFO ! Define this macro if GCC should produce debugging output for VMS ! in response to the `-g' option. The default behavior for VMS is ! to generate minimal debug info for a traceback in the absence of ! `-g' unless explicitly overridden with `-g0'. This behavior is ! controlled by `TARGET_OPTION_OPTIMIZATION' and ! `TARGET_OPTION_OVERRIDE'.  File: gccint.info, Node: Floating Point, Next: Mode Switching, Prev: Debugging Info, Up: Target Macros *************** the target's arithmetic. To ensure cons *** 36920,36934 **** emulation to work with floating point values, even when the host and target floating point formats are identical. ! The following macros are provided by 'real.h' for the compiler to use. All parts of the compiler which generate or optimize floating-point calculations must use these macros. They may evaluate their operands more than once, so operands must not have side effects. -- Macro: REAL_VALUE_TYPE The C data type to be used to hold a floating point value in the ! target machine's format. Typically this is a 'struct' containing ! an array of 'HOST_WIDE_INT', but all code should treat it as an opaque quantity. -- Macro: HOST_WIDE_INT REAL_VALUE_FIX (REAL_VALUE_TYPE X) --- 37359,37373 ---- emulation to work with floating point values, even when the host and target floating point formats are identical. ! The following macros are provided by `real.h' for the compiler to use. All parts of the compiler which generate or optimize floating-point calculations must use these macros. They may evaluate their operands more than once, so operands must not have side effects. -- Macro: REAL_VALUE_TYPE The C data type to be used to hold a floating point value in the ! target machine's format. Typically this is a `struct' containing ! an array of `HOST_WIDE_INT', but all code should treat it as an opaque quantity. -- Macro: HOST_WIDE_INT REAL_VALUE_FIX (REAL_VALUE_TYPE X) *************** File: gccint.info, Node: Mode Switching *** 36970,37022 **** The following macros control mode switching optimizations: -- Macro: OPTIMIZE_MODE_SWITCHING (ENTITY) ! Define this macro if the port needs extra instructions inserted for ! mode switching in an optimizing compilation. For an example, the SH4 can perform both single and double precision floating point operations, but to perform a single precision operation, the FPSCR PR bit has to be cleared, while for ! a double precision operation, this bit has to be set. Changing the ! PR bit requires a general purpose register as a scratch register, ! hence these FPSCR sets have to be inserted before reload, i.e. you ! can't put this into instruction emitting or ! 'TARGET_MACHINE_DEPENDENT_REORG'. You can have multiple entities that are mode-switched, and select at run time which entities actually need it. ! 'OPTIMIZE_MODE_SWITCHING' should return nonzero for any ENTITY that ! needs mode-switching. If you define this macro, you also have to ! define 'NUM_MODES_FOR_MODE_SWITCHING', 'TARGET_MODE_NEEDED', ! 'TARGET_MODE_PRIORITY' and 'TARGET_MODE_EMIT'. ! 'TARGET_MODE_AFTER', 'TARGET_MODE_ENTRY', and 'TARGET_MODE_EXIT' ! are optional. -- Macro: NUM_MODES_FOR_MODE_SWITCHING ! If you define 'OPTIMIZE_MODE_SWITCHING', you have to define this as initializer for an array of integers. Each initializer element N refers to an entity that needs mode switching, and specifies the number of different modes that might need to be set for this entity. The position of the initializer in the ! initializer--starting counting at zero--determines the integer that ! is used to refer to the mode-switched entity in question. In macros that take mode arguments / yield a mode result, modes are represented as numbers 0 ... N - 1. N is used to specify that no mode switch is needed / supplied. -- Target Hook: void TARGET_MODE_EMIT (int ENTITY, int MODE, int PREV_MODE, HARD_REG_SET REGS_LIVE) ! Generate one or more insns to set ENTITY to MODE. HARD_REG_LIVE is the set of hard registers live at the point where the insn(s) are ! to be inserted. PREV_MOXDE indicates the mode to switch from. ! Sets of a lower numbered entity will be emitted before sets of a ! higher numbered entity to a mode of the same or lower priority. -- Target Hook: int TARGET_MODE_NEEDED (int ENTITY, rtx_insn *INSN) ENTITY is an integer specifying a mode-switched entity. If ! 'OPTIMIZE_MODE_SWITCHING' is defined, you must define this macro to ! return an integer value not larger than the corresponding element ! in 'NUM_MODES_FOR_MODE_SWITCHING', to denote the mode that ENTITY ! must be switched into prior to the execution of INSN. -- Target Hook: int TARGET_MODE_AFTER (int ENTITY, int MODE, rtx_insn *INSN) --- 37409,37461 ---- The following macros control mode switching optimizations: -- Macro: OPTIMIZE_MODE_SWITCHING (ENTITY) ! Define this macro if the port needs extra instructions inserted ! for mode switching in an optimizing compilation. For an example, the SH4 can perform both single and double precision floating point operations, but to perform a single precision operation, the FPSCR PR bit has to be cleared, while for ! a double precision operation, this bit has to be set. Changing ! the PR bit requires a general purpose register as a scratch ! register, hence these FPSCR sets have to be inserted before ! reload, i.e. you can't put this into instruction emitting or ! `TARGET_MACHINE_DEPENDENT_REORG'. You can have multiple entities that are mode-switched, and select at run time which entities actually need it. ! `OPTIMIZE_MODE_SWITCHING' should return nonzero for any ENTITY ! that needs mode-switching. If you define this macro, you also ! have to define `NUM_MODES_FOR_MODE_SWITCHING', ! `TARGET_MODE_NEEDED', `TARGET_MODE_PRIORITY' and ! `TARGET_MODE_EMIT'. `TARGET_MODE_AFTER', `TARGET_MODE_ENTRY', and ! `TARGET_MODE_EXIT' are optional. -- Macro: NUM_MODES_FOR_MODE_SWITCHING ! If you define `OPTIMIZE_MODE_SWITCHING', you have to define this as initializer for an array of integers. Each initializer element N refers to an entity that needs mode switching, and specifies the number of different modes that might need to be set for this entity. The position of the initializer in the ! initializer--starting counting at zero--determines the integer ! that is used to refer to the mode-switched entity in question. In macros that take mode arguments / yield a mode result, modes are represented as numbers 0 ... N - 1. N is used to specify that no mode switch is needed / supplied. -- Target Hook: void TARGET_MODE_EMIT (int ENTITY, int MODE, int PREV_MODE, HARD_REG_SET REGS_LIVE) ! Generate one or more insns to set ENTITY to MODE. HARD_REG_LIVE is the set of hard registers live at the point where the insn(s) are ! to be inserted. PREV_MOXDE indicates the mode to switch from. Sets ! of a lower numbered entity will be emitted before sets of a higher ! numbered entity to a mode of the same or lower priority. -- Target Hook: int TARGET_MODE_NEEDED (int ENTITY, rtx_insn *INSN) ENTITY is an integer specifying a mode-switched entity. If ! `OPTIMIZE_MODE_SWITCHING' is defined, you must define this macro ! to return an integer value not larger than the corresponding ! element in `NUM_MODES_FOR_MODE_SWITCHING', to denote the mode that ! ENTITY must be switched into prior to the execution of INSN. -- Target Hook: int TARGET_MODE_AFTER (int ENTITY, int MODE, rtx_insn *INSN) *************** The following macros control mode switch *** 37027,37067 **** -- Target Hook: int TARGET_MODE_ENTRY (int ENTITY) If this macro is defined, it is evaluated for every ENTITY that ! needs mode switching. It should evaluate to an integer, which is a ! mode that ENTITY is assumed to be switched to at function entry. ! If 'TARGET_MODE_ENTRY' is defined then 'TARGET_MODE_EXIT' must be defined. -- Target Hook: int TARGET_MODE_EXIT (int ENTITY) If this macro is defined, it is evaluated for every ENTITY that ! needs mode switching. It should evaluate to an integer, which is a ! mode that ENTITY is assumed to be switched to at function exit. If ! 'TARGET_MODE_EXIT' is defined then 'TARGET_MODE_ENTRY' must be defined. -- Target Hook: int TARGET_MODE_PRIORITY (int ENTITY, int N) This macro specifies the order in which modes for ENTITY are ! processed. 0 is the highest priority, ! 'NUM_MODES_FOR_MODE_SWITCHING[ENTITY] - 1' the lowest. The value of the macro should be an integer designating a mode for ENTITY. ! For any fixed ENTITY, 'mode_priority' (ENTITY, N) shall be a ! bijection in 0 ... 'num_modes_for_mode_switching[ENTITY] - 1'.  File: gccint.info, Node: Target Attributes, Next: Emulated TLS, Prev: Mode Switching, Up: Target Macros ! 17.24 Defining target-specific uses of '__attribute__' ====================================================== Target-specific attributes may be defined for functions, data and types. These are described using the following target hooks; they also need to ! be documented in 'extend.texi'. -- Target Hook: const struct attribute_spec * TARGET_ATTRIBUTE_TABLE ! If defined, this target hook points to an array of 'struct ! attribute_spec' (defined in 'tree-core.h') specifying the machine ! specific attributes for this target and some of the restrictions on ! the entities to which these attributes are applied and the arguments they take. -- Target Hook: bool TARGET_ATTRIBUTE_TAKES_IDENTIFIER_P (const_tree --- 37466,37506 ---- -- Target Hook: int TARGET_MODE_ENTRY (int ENTITY) If this macro is defined, it is evaluated for every ENTITY that ! needs mode switching. It should evaluate to an integer, which is ! a mode that ENTITY is assumed to be switched to at function entry. ! If `TARGET_MODE_ENTRY' is defined then `TARGET_MODE_EXIT' must be defined. -- Target Hook: int TARGET_MODE_EXIT (int ENTITY) If this macro is defined, it is evaluated for every ENTITY that ! needs mode switching. It should evaluate to an integer, which is ! a mode that ENTITY is assumed to be switched to at function exit. ! If `TARGET_MODE_EXIT' is defined then `TARGET_MODE_ENTRY' must be defined. -- Target Hook: int TARGET_MODE_PRIORITY (int ENTITY, int N) This macro specifies the order in which modes for ENTITY are ! processed. 0 is the highest priority, ! `NUM_MODES_FOR_MODE_SWITCHING[ENTITY] - 1' the lowest. The value of the macro should be an integer designating a mode for ENTITY. ! For any fixed ENTITY, `mode_priority' (ENTITY, N) shall be a ! bijection in 0 ... `num_modes_for_mode_switching[ENTITY] - 1'.  File: gccint.info, Node: Target Attributes, Next: Emulated TLS, Prev: Mode Switching, Up: Target Macros ! 17.24 Defining target-specific uses of `__attribute__' ====================================================== Target-specific attributes may be defined for functions, data and types. These are described using the following target hooks; they also need to ! be documented in `extend.texi'. -- Target Hook: const struct attribute_spec * TARGET_ATTRIBUTE_TABLE ! If defined, this target hook points to an array of `struct ! attribute_spec' (defined in `tree-core.h') specifying the machine ! specific attributes for this target and some of the restrictions ! on the entities to which these attributes are applied and the arguments they take. -- Target Hook: bool TARGET_ATTRIBUTE_TAKES_IDENTIFIER_P (const_tree *************** be documented in 'extend.texi'. *** 37075,37084 **** -- Target Hook: int TARGET_COMP_TYPE_ATTRIBUTES (const_tree TYPE1, const_tree TYPE2) If defined, this target hook is a function which returns zero if ! the attributes on TYPE1 and TYPE2 are incompatible, one if they are ! compatible, and two if they are nearly compatible (which causes a ! warning to be generated). If this is not defined, machine-specific ! attributes are supposed always to be compatible. -- Target Hook: void TARGET_SET_DEFAULT_TYPE_ATTRIBUTES (tree TYPE) If defined, this target hook is a function which assigns default --- 37514,37523 ---- -- Target Hook: int TARGET_COMP_TYPE_ATTRIBUTES (const_tree TYPE1, const_tree TYPE2) If defined, this target hook is a function which returns zero if ! the attributes on TYPE1 and TYPE2 are incompatible, one if they ! are compatible, and two if they are nearly compatible (which ! causes a warning to be generated). If this is not defined, ! machine-specific attributes are supposed always to be compatible. -- Target Hook: void TARGET_SET_DEFAULT_TYPE_ATTRIBUTES (tree TYPE) If defined, this target hook is a function which assigns default *************** be documented in 'extend.texi'. *** 37088,37219 **** TYPE2) Define this target hook if the merging of type attributes needs special handling. If defined, the result is a list of the combined ! 'TYPE_ATTRIBUTES' of TYPE1 and TYPE2. It is assumed that ! 'comptypes' has already been called and returned 1. This function ! may call 'merge_attributes' to handle machine-independent merging. -- Target Hook: tree TARGET_MERGE_DECL_ATTRIBUTES (tree OLDDECL, tree NEWDECL) Define this target hook if the merging of decl attributes needs special handling. If defined, the result is a list of the combined ! 'DECL_ATTRIBUTES' of OLDDECL and NEWDECL. NEWDECL is a duplicate declaration of OLDDECL. Examples of when this is needed are when one attribute overrides another, or when an attribute is nullified by a subsequent definition. This function may call ! 'merge_attributes' to handle machine-independent merging. ! If the only target-specific handling you require is 'dllimport' for ! Microsoft Windows targets, you should define the macro ! 'TARGET_DLLIMPORT_DECL_ATTRIBUTES' to '1'. The compiler will then ! define a function called 'merge_dllimport_decl_attributes' which can then be defined as the expansion of ! 'TARGET_MERGE_DECL_ATTRIBUTES'. You can also add ! 'handle_dll_attribute' in the attribute table for your port to ! perform initial processing of the 'dllimport' and 'dllexport' ! attributes. This is done in 'i386/cygwin.h' and 'i386/i386.c', for ! example. -- Target Hook: bool TARGET_VALID_DLLIMPORT_ATTRIBUTE_P (const_tree DECL) ! DECL is a variable or function with '__attribute__((dllimport))' specified. Use this hook if the target needs to add extra ! validation checks to 'handle_dll_attribute'. -- Macro: TARGET_DECLSPEC Define this macro to a nonzero value if you want to treat ! '__declspec(X)' as equivalent to '__attribute((X))'. By default, this behavior is enabled only for targets that define ! 'TARGET_DLLIMPORT_DECL_ATTRIBUTES'. The current implementation of ! '__declspec' is via a built-in macro, but you should not rely on this implementation detail. -- Target Hook: void TARGET_INSERT_ATTRIBUTES (tree NODE, tree *ATTR_PTR) ! Define this target hook if you want to be able to add attributes to ! a decl when it is being created. This is normally useful for back ! ends which wish to implement a pragma by using the attributes which ! correspond to the pragma's effect. The NODE argument is the decl ! which is being created. The ATTR_PTR argument is a pointer to the ! attribute list for this decl. The list itself should not be ! modified, since it may be shared with other decls, but attributes ! may be chained on the head of the list and '*ATTR_PTR' modified to ! point to the new attributes, or a copy of the list may be made if ! further changes are needed. -- Target Hook: bool TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P (const_tree FNDECL) ! This target hook returns 'true' if it is OK to inline FNDECL into the current function, despite its having target-specific ! attributes, 'false' otherwise. By default, if a function has a target specific attribute attached to it, it will not be inlined. ! -- Target Hook: bool TARGET_OPTION_VALID_ATTRIBUTE_P (tree FNDECL, tree ! NAME, tree ARGS, int FLAGS) ! This hook is called to parse 'attribute(target("..."))', which allows setting target-specific options on individual functions. These function-specific options may differ from the options ! specified on the command line. The hook should return 'true' if the options are valid. ! The hook should set the 'DECL_FUNCTION_SPECIFIC_TARGET' field in the function declaration to hold a pointer to a target-specific ! 'struct cl_target_option' structure. -- Target Hook: void TARGET_OPTION_SAVE (struct cl_target_option *PTR, struct gcc_options *OPTS) This hook is called to save any additional target-specific ! information in the 'struct cl_target_option' structure for ! function-specific options from the 'struct gcc_options' structure. *Note Option file format::. -- Target Hook: void TARGET_OPTION_RESTORE (struct gcc_options *OPTS, struct cl_target_option *PTR) This hook is called to restore any additional target-specific ! information in the 'struct cl_target_option' structure for ! function-specific options to the 'struct gcc_options' structure. -- Target Hook: void TARGET_OPTION_POST_STREAM_IN (struct cl_target_option *PTR) This hook is called to update target-specific information in the ! 'struct cl_target_option' structure after it is streamed in from LTO bytecode. -- Target Hook: void TARGET_OPTION_PRINT (FILE *FILE, int INDENT, struct cl_target_option *PTR) This hook is called to print any additional target-specific ! information in the 'struct cl_target_option' structure for function-specific options. -- Target Hook: bool TARGET_OPTION_PRAGMA_PARSE (tree ARGS, tree POP_TARGET) ! This target hook parses the options for '#pragma GCC target', which sets the target-specific options for functions that occur later in ! the input stream. The options accepted should be the same as those ! handled by the 'TARGET_OPTION_VALID_ATTRIBUTE_P' hook. -- Target Hook: void TARGET_OPTION_OVERRIDE (void) ! Sometimes certain combinations of command options do not make sense ! on a particular target machine. You can override the hook ! 'TARGET_OPTION_OVERRIDE' to take account of this. This hooks is called once just after all the command options have been parsed. Don't use this hook to turn on various extra optimizations for ! '-O'. That is what 'TARGET_OPTION_OPTIMIZATION' is for. If you need to do something whenever the optimization level is changed via the optimize attribute or pragma, see ! 'TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE' -- Target Hook: bool TARGET_OPTION_FUNCTION_VERSIONS (tree DECL1, tree DECL2) ! This target hook returns 'true' if DECL1 and DECL2 are versions of the same function. DECL1 and DECL2 are function versions if and only if they have the same function signature and different target specific attributes, that is, they are compiled for different target machines. -- Target Hook: bool TARGET_CAN_INLINE_P (tree CALLER, tree CALLEE) ! This target hook returns 'false' if the CALLER function cannot inline CALLEE, based on target specific information. By default, inlining is not allowed if the callee function has function specific target options and the caller does not use the same --- 37527,37658 ---- TYPE2) Define this target hook if the merging of type attributes needs special handling. If defined, the result is a list of the combined ! `TYPE_ATTRIBUTES' of TYPE1 and TYPE2. It is assumed that ! `comptypes' has already been called and returned 1. This function ! may call `merge_attributes' to handle machine-independent merging. -- Target Hook: tree TARGET_MERGE_DECL_ATTRIBUTES (tree OLDDECL, tree NEWDECL) Define this target hook if the merging of decl attributes needs special handling. If defined, the result is a list of the combined ! `DECL_ATTRIBUTES' of OLDDECL and NEWDECL. NEWDECL is a duplicate declaration of OLDDECL. Examples of when this is needed are when one attribute overrides another, or when an attribute is nullified by a subsequent definition. This function may call ! `merge_attributes' to handle machine-independent merging. ! If the only target-specific handling you require is `dllimport' ! for Microsoft Windows targets, you should define the macro ! `TARGET_DLLIMPORT_DECL_ATTRIBUTES' to `1'. The compiler will then ! define a function called `merge_dllimport_decl_attributes' which can then be defined as the expansion of ! `TARGET_MERGE_DECL_ATTRIBUTES'. You can also add ! `handle_dll_attribute' in the attribute table for your port to ! perform initial processing of the `dllimport' and `dllexport' ! attributes. This is done in `i386/cygwin.h' and `i386/i386.c', ! for example. -- Target Hook: bool TARGET_VALID_DLLIMPORT_ATTRIBUTE_P (const_tree DECL) ! DECL is a variable or function with `__attribute__((dllimport))' specified. Use this hook if the target needs to add extra ! validation checks to `handle_dll_attribute'. -- Macro: TARGET_DECLSPEC Define this macro to a nonzero value if you want to treat ! `__declspec(X)' as equivalent to `__attribute((X))'. By default, this behavior is enabled only for targets that define ! `TARGET_DLLIMPORT_DECL_ATTRIBUTES'. The current implementation of ! `__declspec' is via a built-in macro, but you should not rely on this implementation detail. -- Target Hook: void TARGET_INSERT_ATTRIBUTES (tree NODE, tree *ATTR_PTR) ! Define this target hook if you want to be able to add attributes ! to a decl when it is being created. This is normally useful for ! back ends which wish to implement a pragma by using the attributes ! which correspond to the pragma's effect. The NODE argument is the ! decl which is being created. The ATTR_PTR argument is a pointer ! to the attribute list for this decl. The list itself should not ! be modified, since it may be shared with other decls, but ! attributes may be chained on the head of the list and `*ATTR_PTR' ! modified to point to the new attributes, or a copy of the list may ! be made if further changes are needed. -- Target Hook: bool TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P (const_tree FNDECL) ! This target hook returns `true' if it is OK to inline FNDECL into the current function, despite its having target-specific ! attributes, `false' otherwise. By default, if a function has a target specific attribute attached to it, it will not be inlined. ! -- Target Hook: bool TARGET_OPTION_VALID_ATTRIBUTE_P (tree FNDECL, ! tree NAME, tree ARGS, int FLAGS) ! This hook is called to parse `attribute(target("..."))', which allows setting target-specific options on individual functions. These function-specific options may differ from the options ! specified on the command line. The hook should return `true' if the options are valid. ! The hook should set the `DECL_FUNCTION_SPECIFIC_TARGET' field in the function declaration to hold a pointer to a target-specific ! `struct cl_target_option' structure. -- Target Hook: void TARGET_OPTION_SAVE (struct cl_target_option *PTR, struct gcc_options *OPTS) This hook is called to save any additional target-specific ! information in the `struct cl_target_option' structure for ! function-specific options from the `struct gcc_options' structure. *Note Option file format::. -- Target Hook: void TARGET_OPTION_RESTORE (struct gcc_options *OPTS, struct cl_target_option *PTR) This hook is called to restore any additional target-specific ! information in the `struct cl_target_option' structure for ! function-specific options to the `struct gcc_options' structure. -- Target Hook: void TARGET_OPTION_POST_STREAM_IN (struct cl_target_option *PTR) This hook is called to update target-specific information in the ! `struct cl_target_option' structure after it is streamed in from LTO bytecode. -- Target Hook: void TARGET_OPTION_PRINT (FILE *FILE, int INDENT, struct cl_target_option *PTR) This hook is called to print any additional target-specific ! information in the `struct cl_target_option' structure for function-specific options. -- Target Hook: bool TARGET_OPTION_PRAGMA_PARSE (tree ARGS, tree POP_TARGET) ! This target hook parses the options for `#pragma GCC target', which sets the target-specific options for functions that occur later in ! the input stream. The options accepted should be the same as ! those handled by the `TARGET_OPTION_VALID_ATTRIBUTE_P' hook. -- Target Hook: void TARGET_OPTION_OVERRIDE (void) ! Sometimes certain combinations of command options do not make ! sense on a particular target machine. You can override the hook ! `TARGET_OPTION_OVERRIDE' to take account of this. This hooks is called once just after all the command options have been parsed. Don't use this hook to turn on various extra optimizations for ! `-O'. That is what `TARGET_OPTION_OPTIMIZATION' is for. If you need to do something whenever the optimization level is changed via the optimize attribute or pragma, see ! `TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE' -- Target Hook: bool TARGET_OPTION_FUNCTION_VERSIONS (tree DECL1, tree DECL2) ! This target hook returns `true' if DECL1 and DECL2 are versions of the same function. DECL1 and DECL2 are function versions if and only if they have the same function signature and different target specific attributes, that is, they are compiled for different target machines. -- Target Hook: bool TARGET_CAN_INLINE_P (tree CALLER, tree CALLEE) ! This target hook returns `false' if the CALLER function cannot inline CALLEE, based on target specific information. By default, inlining is not allowed if the callee function has function specific target options and the caller does not use the same *************** be documented in 'extend.texi'. *** 37221,37227 **** -- Target Hook: void TARGET_RELAYOUT_FUNCTION (tree FNDECL) This target hook fixes function FNDECL after attributes are ! processed. Default does nothing. On ARM, the default function's alignment is updated with the attribute target.  --- 37660,37666 ---- -- Target Hook: void TARGET_RELAYOUT_FUNCTION (tree FNDECL) This target hook fixes function FNDECL after attributes are ! processed. Default does nothing. On ARM, the default function's alignment is updated with the attribute target.  *************** layer. *** 37239,37246 **** The emulation layer works by creating a control object for every TLS object. To access the TLS object, a lookup function is provided which, ! when given the address of the control object, will return the address of ! the current thread's instance of the TLS object. -- Target Hook: const char * TARGET_EMUTLS_GET_ADDRESS Contains the name of the helper function that uses a TLS control --- 37678,37685 ---- The emulation layer works by creating a control object for every TLS object. To access the TLS object, a lookup function is provided which, ! when given the address of the control object, will return the address ! of the current thread's instance of the TLS object. -- Target Hook: const char * TARGET_EMUTLS_GET_ADDRESS Contains the name of the helper function that uses a TLS control *************** the current thread's instance of the TLS *** 37250,37289 **** -- Target Hook: const char * TARGET_EMUTLS_REGISTER_COMMON Contains the name of the helper function that should be used at program startup to register TLS objects that are implicitly ! initialized to zero. If this is 'NULL', all TLS objects will have explicit initializers. The default causes libgcc's emulated TLS registration function to be used. -- Target Hook: const char * TARGET_EMUTLS_VAR_SECTION Contains the name of the section in which TLS control variables ! should be placed. The default of 'NULL' allows these to be placed in any section. -- Target Hook: const char * TARGET_EMUTLS_TMPL_SECTION Contains the name of the section in which TLS initializers should ! be placed. The default of 'NULL' allows these to be placed in any section. -- Target Hook: const char * TARGET_EMUTLS_VAR_PREFIX Contains the prefix to be prepended to TLS control variable names. ! The default of 'NULL' uses a target-specific prefix. -- Target Hook: const char * TARGET_EMUTLS_TMPL_PREFIX Contains the prefix to be prepended to TLS initializer objects. ! The default of 'NULL' uses a target-specific prefix. -- Target Hook: tree TARGET_EMUTLS_VAR_FIELDS (tree TYPE, tree *NAME) Specifies a function that generates the FIELD_DECLs for a TLS control object type. TYPE is the RECORD_TYPE the fields are for and NAME should be filled with the structure tag, if the default of ! '__emutls_object' is unsuitable. The default creates a type suitable for libgcc's emulated TLS function. -- Target Hook: tree TARGET_EMUTLS_VAR_INIT (tree VAR, tree DECL, tree TMPL_ADDR) Specifies a function that generates the CONSTRUCTOR to initialize a ! TLS control object. VAR is the TLS control object, DECL is the TLS ! object and TMPL_ADDR is the address of the initializer. The default initializes libgcc's emulated TLS control object. -- Target Hook: bool TARGET_EMUTLS_VAR_ALIGN_FIXED --- 37689,37728 ---- -- Target Hook: const char * TARGET_EMUTLS_REGISTER_COMMON Contains the name of the helper function that should be used at program startup to register TLS objects that are implicitly ! initialized to zero. If this is `NULL', all TLS objects will have explicit initializers. The default causes libgcc's emulated TLS registration function to be used. -- Target Hook: const char * TARGET_EMUTLS_VAR_SECTION Contains the name of the section in which TLS control variables ! should be placed. The default of `NULL' allows these to be placed in any section. -- Target Hook: const char * TARGET_EMUTLS_TMPL_SECTION Contains the name of the section in which TLS initializers should ! be placed. The default of `NULL' allows these to be placed in any section. -- Target Hook: const char * TARGET_EMUTLS_VAR_PREFIX Contains the prefix to be prepended to TLS control variable names. ! The default of `NULL' uses a target-specific prefix. -- Target Hook: const char * TARGET_EMUTLS_TMPL_PREFIX Contains the prefix to be prepended to TLS initializer objects. ! The default of `NULL' uses a target-specific prefix. -- Target Hook: tree TARGET_EMUTLS_VAR_FIELDS (tree TYPE, tree *NAME) Specifies a function that generates the FIELD_DECLs for a TLS control object type. TYPE is the RECORD_TYPE the fields are for and NAME should be filled with the structure tag, if the default of ! `__emutls_object' is unsuitable. The default creates a type suitable for libgcc's emulated TLS function. -- Target Hook: tree TARGET_EMUTLS_VAR_INIT (tree VAR, tree DECL, tree TMPL_ADDR) Specifies a function that generates the CONSTRUCTOR to initialize a ! TLS control object. VAR is the TLS control object, DECL is the ! TLS object and TMPL_ADDR is the address of the initializer. The default initializes libgcc's emulated TLS control object. -- Target Hook: bool TARGET_EMUTLS_VAR_ALIGN_FIXED *************** the current thread's instance of the TLS *** 37292,37298 **** optimize single objects. The default is false. -- Target Hook: bool TARGET_EMUTLS_DEBUG_FORM_TLS_ADDRESS ! Specifies whether a DWARF 'DW_OP_form_tls_address' location descriptor may be used to describe emulated TLS control objects.  --- 37731,37737 ---- optimize single objects. The default is false. -- Target Hook: bool TARGET_EMUTLS_DEBUG_FORM_TLS_ADDRESS ! Specifies whether a DWARF `DW_OP_form_tls_address' location descriptor may be used to describe emulated TLS control objects.  *************** and memory using asm-ized variables. Fo *** 37313,37319 **** ("c0r1" is the default name of register 1 in coprocessor 0; alternate names may be added as described below, or the default names may be ! overridden entirely in 'SUBTARGET_CONDITIONAL_REGISTER_USAGE'.) Coprocessor registers are assumed to be epilogue-used; sets to them will be preserved even if it does not appear that the register is used --- 37752,37758 ---- ("c0r1" is the default name of register 1 in coprocessor 0; alternate names may be added as described below, or the default names may be ! overridden entirely in `SUBTARGET_CONDITIONAL_REGISTER_USAGE'.) Coprocessor registers are assumed to be epilogue-used; sets to them will be preserved even if it does not appear that the register is used *************** File: gccint.info, Node: PCH Target, N *** 37331,37361 **** -- Target Hook: void * TARGET_GET_PCH_VALIDITY (size_t *SZ) This hook returns a pointer to the data needed by ! 'TARGET_PCH_VALID_P' and sets '*SZ' to the size of the data in bytes. -- Target Hook: const char * TARGET_PCH_VALID_P (const void *DATA, size_t SZ) This hook checks whether the options used to create a PCH file are ! compatible with the current settings. It returns 'NULL' if so and a suitable error message if not. Error messages will be presented ! to the user and must be localized using '_(MSG)'. ! DATA is the data that was returned by 'TARGET_GET_PCH_VALIDITY' when the PCH file was created and SZ is the size of that data in bytes. It's safe to assume that the data was created by the same version of the compiler, so no format checking is needed. ! The default definition of 'default_pch_valid_p' should be suitable for most targets. -- Target Hook: const char * TARGET_CHECK_PCH_TARGET_FLAGS (int PCH_FLAGS) If this hook is nonnull, the default implementation of ! 'TARGET_PCH_VALID_P' will use it to check for compatible values of ! 'target_flags'. PCH_FLAGS specifies the value that 'target_flags' ! had when the PCH file was created. The return value is the same as ! for 'TARGET_PCH_VALID_P'. -- Target Hook: void TARGET_PREPARE_PCH_SAVE (void) Called before writing out a PCH file. If the target has some --- 37770,37800 ---- -- Target Hook: void * TARGET_GET_PCH_VALIDITY (size_t *SZ) This hook returns a pointer to the data needed by ! `TARGET_PCH_VALID_P' and sets `*SZ' to the size of the data in bytes. -- Target Hook: const char * TARGET_PCH_VALID_P (const void *DATA, size_t SZ) This hook checks whether the options used to create a PCH file are ! compatible with the current settings. It returns `NULL' if so and a suitable error message if not. Error messages will be presented ! to the user and must be localized using `_(MSG)'. ! DATA is the data that was returned by `TARGET_GET_PCH_VALIDITY' when the PCH file was created and SZ is the size of that data in bytes. It's safe to assume that the data was created by the same version of the compiler, so no format checking is needed. ! The default definition of `default_pch_valid_p' should be suitable for most targets. -- Target Hook: const char * TARGET_CHECK_PCH_TARGET_FLAGS (int PCH_FLAGS) If this hook is nonnull, the default implementation of ! `TARGET_PCH_VALID_P' will use it to check for compatible values of ! `target_flags'. PCH_FLAGS specifies the value that `target_flags' ! had when the PCH file was created. The return value is the same ! as for `TARGET_PCH_VALID_P'. -- Target Hook: void TARGET_PREPARE_PCH_SAVE (void) Called before writing out a PCH file. If the target has some *************** File: gccint.info, Node: C++ ABI, Next *** 37376,37395 **** -- Target Hook: bool TARGET_CXX_GUARD_MASK_BIT (void) This hook determines how guard variables are used. It should ! return 'false' (the default) if the first byte should be used. A ! return value of 'true' indicates that only the least significant bit should be used. -- Target Hook: tree TARGET_CXX_GET_COOKIE_SIZE (tree TYPE) This hook returns the size of the cookie to use when allocating an array whose elements have the indicated TYPE. Assumes that it is ! already known that a cookie is needed. The default is 'max(sizeof (size_t), alignof(type))', as defined in section 2.7 of the IA64/Generic C++ ABI. -- Target Hook: bool TARGET_CXX_COOKIE_HAS_SIZE (void) ! This hook should return 'true' if the element size should be stored ! in array cookies. The default is to return 'false'. -- Target Hook: int TARGET_CXX_IMPORT_EXPORT_CLASS (tree TYPE, int IMPORT_EXPORT) --- 37815,37834 ---- -- Target Hook: bool TARGET_CXX_GUARD_MASK_BIT (void) This hook determines how guard variables are used. It should ! return `false' (the default) if the first byte should be used. A ! return value of `true' indicates that only the least significant bit should be used. -- Target Hook: tree TARGET_CXX_GET_COOKIE_SIZE (tree TYPE) This hook returns the size of the cookie to use when allocating an array whose elements have the indicated TYPE. Assumes that it is ! already known that a cookie is needed. The default is `max(sizeof (size_t), alignof(type))', as defined in section 2.7 of the IA64/Generic C++ ABI. -- Target Hook: bool TARGET_CXX_COOKIE_HAS_SIZE (void) ! This hook should return `true' if the element size should be ! stored in array cookies. The default is to return `false'. -- Target Hook: int TARGET_CXX_IMPORT_EXPORT_CLASS (tree TYPE, int IMPORT_EXPORT) *************** File: gccint.info, Node: C++ ABI, Next *** 37401,37409 **** the backend's targeted operating system. -- Target Hook: bool TARGET_CXX_CDTOR_RETURNS_THIS (void) ! This hook should return 'true' if constructors and destructors ! return the address of the object created/destroyed. The default is ! to return 'false'. -- Target Hook: bool TARGET_CXX_KEY_METHOD_MAY_BE_INLINE (void) This hook returns true if the key method for a class (i.e., the --- 37840,37848 ---- the backend's targeted operating system. -- Target Hook: bool TARGET_CXX_CDTOR_RETURNS_THIS (void) ! This hook should return `true' if constructors and destructors ! return the address of the object created/destroyed. The default ! is to return `false'. -- Target Hook: bool TARGET_CXX_KEY_METHOD_MAY_BE_INLINE (void) This hook returns true if the key method for a class (i.e., the *************** File: gccint.info, Node: C++ ABI, Next *** 37413,37419 **** function so long as the function is not declared inline in the class definition. Under some variants of the ABI, an inline function can never be the key method. The default is to return ! 'true'. -- Target Hook: void TARGET_CXX_DETERMINE_CLASS_DATA_VISIBILITY (tree DECL) --- 37852,37858 ---- function so long as the function is not declared inline in the class definition. Under some variants of the ABI, an inline function can never be the key method. The default is to return ! `true'. -- Target Hook: void TARGET_CXX_DETERMINE_CLASS_DATA_VISIBILITY (tree DECL) *************** File: gccint.info, Node: C++ ABI, Next *** 37422,37428 **** external linkage in this translation unit. No ELF visibility has been explicitly specified. If the target needs to specify a visibility other than that of the containing class, use this hook ! to set 'DECL_VISIBILITY' and 'DECL_VISIBILITY_SPECIFIED'. -- Target Hook: bool TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT (void) This hook returns true (the default) if virtual tables and other --- 37861,37867 ---- external linkage in this translation unit. No ELF visibility has been explicitly specified. If the target needs to specify a visibility other than that of the containing class, use this hook ! to set `DECL_VISIBILITY' and `DECL_VISIBILITY_SPECIFIED'. -- Target Hook: bool TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT (void) This hook returns true (the default) if virtual tables and other *************** File: gccint.info, Node: C++ ABI, Next *** 37437,37462 **** be COMDAT, false if it should not be COMDAT. -- Target Hook: bool TARGET_CXX_USE_AEABI_ATEXIT (void) ! This hook returns true if '__aeabi_atexit' (as defined by the ARM EABI) should be used to register static destructors when ! '-fuse-cxa-atexit' is in effect. The default is to return false to ! use '__cxa_atexit'. -- Target Hook: bool TARGET_CXX_USE_ATEXIT_FOR_CXA_ATEXIT (void) ! This hook returns true if the target 'atexit' function can be used ! in the same manner as '__cxa_atexit' to register C++ static ! destructors. This requires that 'atexit'-registered functions in shared libraries are run in the correct order when the libraries ! are unloaded. The default is to return false. -- Target Hook: void TARGET_CXX_ADJUST_CLASS_AT_DEFINITION (tree TYPE) ! TYPE is a C++ class (i.e., RECORD_TYPE or UNION_TYPE) that has just ! been defined. Use this hook to make adjustments to the class (eg, ! tweak visibility or perform any other required target modifications). -- Target Hook: tree TARGET_CXX_DECL_MANGLING_CONTEXT (const_tree DECL) ! Return target-specific mangling context of DECL or 'NULL_TREE'.  File: gccint.info, Node: Named Address Spaces, Next: Misc, Prev: C++ ABI, Up: Target Macros --- 37876,37901 ---- be COMDAT, false if it should not be COMDAT. -- Target Hook: bool TARGET_CXX_USE_AEABI_ATEXIT (void) ! This hook returns true if `__aeabi_atexit' (as defined by the ARM EABI) should be used to register static destructors when ! `-fuse-cxa-atexit' is in effect. The default is to return false ! to use `__cxa_atexit'. -- Target Hook: bool TARGET_CXX_USE_ATEXIT_FOR_CXA_ATEXIT (void) ! This hook returns true if the target `atexit' function can be used ! in the same manner as `__cxa_atexit' to register C++ static ! destructors. This requires that `atexit'-registered functions in shared libraries are run in the correct order when the libraries ! are unloaded. The default is to return false. -- Target Hook: void TARGET_CXX_ADJUST_CLASS_AT_DEFINITION (tree TYPE) ! TYPE is a C++ class (i.e., RECORD_TYPE or UNION_TYPE) that has ! just been defined. Use this hook to make adjustments to the class ! (eg, tweak visibility or perform any other required target modifications). -- Target Hook: tree TARGET_CXX_DECL_MANGLING_CONTEXT (const_tree DECL) ! Return target-specific mangling context of DECL or `NULL_TREE'.  File: gccint.info, Node: Named Address Spaces, Next: Misc, Prev: C++ ABI, Up: Target Macros *************** File: gccint.info, Node: Named Address *** 37465,37486 **** ============================================= The draft technical report of the ISO/IEC JTC1 S22 WG14 N1275 standards ! committee, 'Programming Languages - C - Extensions to support embedded processors', specifies a syntax for embedded processors to specify alternate address spaces. You can configure a GCC port to support section 5.1 of the draft report to add support for address spaces other than the default address space. These address spaces are new keywords ! that are similar to the 'volatile' and 'const' type attributes. Pointers to named address spaces can have a different size than pointers to the generic address space. ! For example, the SPU port uses the '__ea' address space to refer to memory in the host processor, rather than memory local to the SPU ! processor. Access to memory in the '__ea' address space involves issuing DMA operations to move data between the host processor and the ! local processor memory address space. Pointers in the '__ea' address ! space are either 32 bits or 64 bits based on the '-mea32' or '-mea64' switches (native SPU pointers are always 32 bits). Internally, address spaces are represented as a small integer in the --- 37904,37925 ---- ============================================= The draft technical report of the ISO/IEC JTC1 S22 WG14 N1275 standards ! committee, `Programming Languages - C - Extensions to support embedded processors', specifies a syntax for embedded processors to specify alternate address spaces. You can configure a GCC port to support section 5.1 of the draft report to add support for address spaces other than the default address space. These address spaces are new keywords ! that are similar to the `volatile' and `const' type attributes. Pointers to named address spaces can have a different size than pointers to the generic address space. ! For example, the SPU port uses the `__ea' address space to refer to memory in the host processor, rather than memory local to the SPU ! processor. Access to memory in the `__ea' address space involves issuing DMA operations to move data between the host processor and the ! local processor memory address space. Pointers in the `__ea' address ! space are either 32 bits or 64 bits based on the `-mea32' or `-mea64' switches (native SPU pointers are always 32 bits). Internally, address spaces are represented as a small integer in the *************** range 0 to 15 with address space 0 being *** 37488,37495 **** address space. To register a named address space qualifier keyword with the C front ! end, the target may call the 'c_register_addr_space' routine. For ! example, the SPU port uses the following to declare '__ea' as the keyword for named address space #1: #define ADDR_SPACE_EA 1 c_register_addr_space ("__ea", ADDR_SPACE_EA); --- 37927,37934 ---- address space. To register a named address space qualifier keyword with the C front ! end, the target may call the `c_register_addr_space' routine. For ! example, the SPU port uses the following to declare `__ea' as the keyword for named address space #1: #define ADDR_SPACE_EA 1 c_register_addr_space ("__ea", ADDR_SPACE_EA); *************** keyword for named address space #1: *** 37498,37535 **** (addr_space_t ADDRESS_SPACE) Define this to return the machine mode to use for pointers to ADDRESS_SPACE if the target supports named address spaces. The ! default version of this hook returns 'ptr_mode'. -- Target Hook: machine_mode TARGET_ADDR_SPACE_ADDRESS_MODE (addr_space_t ADDRESS_SPACE) Define this to return the machine mode to use for addresses in ADDRESS_SPACE if the target supports named address spaces. The ! default version of this hook returns 'Pmode'. ! -- Target Hook: bool TARGET_ADDR_SPACE_VALID_POINTER_MODE (machine_mode ! MODE, addr_space_t AS) Define this to return nonzero if the port can handle pointers with machine mode MODE to address space AS. This target hook is the ! same as the 'TARGET_VALID_POINTER_MODE' target hook, except that it ! includes explicit named address space support. The default version ! of this hook returns true for the modes returned by either the ! 'TARGET_ADDR_SPACE_POINTER_MODE' or ! 'TARGET_ADDR_SPACE_ADDRESS_MODE' target hooks for the given address ! space. -- Target Hook: bool TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P (machine_mode MODE, rtx EXP, bool STRICT, addr_space_t AS) Define this to return true if EXP is a valid address for mode MODE in the named address space AS. The STRICT parameter says whether strict addressing is in effect after reload has finished. This ! target hook is the same as the 'TARGET_LEGITIMATE_ADDRESS_P' target ! hook, except that it includes explicit named address space support. -- Target Hook: rtx TARGET_ADDR_SPACE_LEGITIMIZE_ADDRESS (rtx X, rtx OLDX, machine_mode MODE, addr_space_t AS) Define this to modify an invalid address X to be a valid address with mode MODE in the named address space AS. This target hook is ! the same as the 'TARGET_LEGITIMIZE_ADDRESS' target hook, except that it includes explicit named address space support. -- Target Hook: bool TARGET_ADDR_SPACE_SUBSET_P (addr_space_t SUBSET, --- 37937,37975 ---- (addr_space_t ADDRESS_SPACE) Define this to return the machine mode to use for pointers to ADDRESS_SPACE if the target supports named address spaces. The ! default version of this hook returns `ptr_mode'. -- Target Hook: machine_mode TARGET_ADDR_SPACE_ADDRESS_MODE (addr_space_t ADDRESS_SPACE) Define this to return the machine mode to use for addresses in ADDRESS_SPACE if the target supports named address spaces. The ! default version of this hook returns `Pmode'. ! -- Target Hook: bool TARGET_ADDR_SPACE_VALID_POINTER_MODE ! (machine_mode MODE, addr_space_t AS) Define this to return nonzero if the port can handle pointers with machine mode MODE to address space AS. This target hook is the ! same as the `TARGET_VALID_POINTER_MODE' target hook, except that ! it includes explicit named address space support. The default ! version of this hook returns true for the modes returned by either ! the `TARGET_ADDR_SPACE_POINTER_MODE' or ! `TARGET_ADDR_SPACE_ADDRESS_MODE' target hooks for the given ! address space. -- Target Hook: bool TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P (machine_mode MODE, rtx EXP, bool STRICT, addr_space_t AS) Define this to return true if EXP is a valid address for mode MODE in the named address space AS. The STRICT parameter says whether strict addressing is in effect after reload has finished. This ! target hook is the same as the `TARGET_LEGITIMATE_ADDRESS_P' ! target hook, except that it includes explicit named address space ! support. -- Target Hook: rtx TARGET_ADDR_SPACE_LEGITIMIZE_ADDRESS (rtx X, rtx OLDX, machine_mode MODE, addr_space_t AS) Define this to modify an invalid address X to be a valid address with mode MODE in the named address space AS. This target hook is ! the same as the `TARGET_LEGITIMIZE_ADDRESS' target hook, except that it includes explicit named address space support. -- Target Hook: bool TARGET_ADDR_SPACE_SUBSET_P (addr_space_t SUBSET, *************** keyword for named address space #1: *** 37541,37548 **** arithmetic operations. Pointers to a superset address space can be converted to pointers to a subset address space via explicit casts. ! -- Target Hook: bool TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID (addr_space_t ! AS) Define this to modify the default handling of address 0 for the address space. Return true if 0 should be considered a valid address. --- 37981,37988 ---- arithmetic operations. Pointers to a superset address space can be converted to pointers to a subset address space via explicit casts. ! -- Target Hook: bool TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID ! (addr_space_t AS) Define this to modify the default handling of address 0 for the address space. Return true if 0 should be considered a valid address. *************** keyword for named address space #1: *** 37554,37565 **** a new pointer expression with type TO_TYPE that points to a different named address space. When this hook it called, it is guaranteed that one of the two address spaces is a subset of the ! other, as determined by the 'TARGET_ADDR_SPACE_SUBSET_P' target hook. -- Target Hook: int TARGET_ADDR_SPACE_DEBUG (addr_space_t AS) Define this to define how the address space is encoded in dwarf. ! The result is the value to be used with 'DW_AT_address_class'.  File: gccint.info, Node: Misc, Prev: Named Address Spaces, Up: Target Macros --- 37994,38005 ---- a new pointer expression with type TO_TYPE that points to a different named address space. When this hook it called, it is guaranteed that one of the two address spaces is a subset of the ! other, as determined by the `TARGET_ADDR_SPACE_SUBSET_P' target hook. -- Target Hook: int TARGET_ADDR_SPACE_DEBUG (addr_space_t AS) Define this to define how the address space is encoded in dwarf. ! The result is the value to be used with `DW_AT_address_class'.  File: gccint.info, Node: Misc, Prev: Named Address Spaces, Up: Target Macros *************** Here are several miscellaneous parameter *** 37573,37580 **** Define this boolean macro to indicate whether or not your architecture has conditional branches that can span all of memory. It is used in conjunction with an optimization that partitions hot ! and cold basic blocks into separate sections of the executable. If ! this macro is set to false, gcc will convert any conditional branches that attempt to cross between sections into unconditional branches or indirect jumps. --- 38013,38020 ---- Define this boolean macro to indicate whether or not your architecture has conditional branches that can span all of memory. It is used in conjunction with an optimization that partitions hot ! and cold basic blocks into separate sections of the executable. ! If this macro is set to false, gcc will convert any conditional branches that attempt to cross between sections into unconditional branches or indirect jumps. *************** Here are several miscellaneous parameter *** 37592,37602 **** elements of a jump-table should have. -- Macro: CASE_VECTOR_SHORTEN_MODE (MIN_OFFSET, MAX_OFFSET, BODY) ! Optional: return the preferred mode for an 'addr_diff_vec' when the ! minimum and maximum offset are known. If you define this, it enables extra code in branch shortening to deal with ! 'addr_diff_vec'. To make this work, you also have to define ! 'INSN_ALIGN' and make the alignment for 'addr_diff_vec' explicit. The BODY argument is provided so that the offset_unsigned and scale flags can be updated. --- 38032,38042 ---- elements of a jump-table should have. -- Macro: CASE_VECTOR_SHORTEN_MODE (MIN_OFFSET, MAX_OFFSET, BODY) ! Optional: return the preferred mode for an `addr_diff_vec' when ! the minimum and maximum offset are known. If you define this, it enables extra code in branch shortening to deal with ! `addr_diff_vec'. To make this work, you also have to define ! `INSN_ALIGN' and make the alignment for `addr_diff_vec' explicit. The BODY argument is provided so that the offset_unsigned and scale flags can be updated. *************** Here are several miscellaneous parameter *** 37604,37617 **** Define this macro to be a C expression to indicate when jump-tables should contain relative addresses. You need not define this macro if jump-tables never contain relative addresses, or jump-tables ! should contain relative addresses only when '-fPIC' or '-fPIC' is in effect. -- Target Hook: unsigned int TARGET_CASE_VALUES_THRESHOLD (void) This function return the smallest number of different values for which it is best to use a jump-table instead of a tree of conditional branches. The default is four for machines with a ! 'casesi' instruction and five otherwise. This is best for most machines. -- Macro: WORD_REGISTER_OPERATIONS --- 38044,38057 ---- Define this macro to be a C expression to indicate when jump-tables should contain relative addresses. You need not define this macro if jump-tables never contain relative addresses, or jump-tables ! should contain relative addresses only when `-fPIC' or `-fPIC' is in effect. -- Target Hook: unsigned int TARGET_CASE_VALUES_THRESHOLD (void) This function return the smallest number of different values for which it is best to use a jump-table instead of a tree of conditional branches. The default is four for machines with a ! `casesi' instruction and five otherwise. This is best for most machines. -- Macro: WORD_REGISTER_OPERATIONS *************** Here are several miscellaneous parameter *** 37622,37651 **** -- Macro: LOAD_EXTEND_OP (MEM_MODE) Define this macro to be a C expression indicating when insns that ! read memory in MEM_MODE, an integral mode narrower than a word, set ! the bits outside of MEM_MODE to be either the sign-extension or the ! zero-extension of the data read. Return 'SIGN_EXTEND' for values ! of MEM_MODE for which the insn sign-extends, 'ZERO_EXTEND' for ! which it zero-extends, and 'UNKNOWN' for other modes. This macro is not called with MEM_MODE non-integral or with a width ! greater than or equal to 'BITS_PER_WORD', so you may return any value in this case. Do not define this macro if it would always ! return 'UNKNOWN'. On machines where this macro is defined, you ! will normally define it as the constant 'SIGN_EXTEND' or ! 'ZERO_EXTEND'. ! You may return a non-'UNKNOWN' value even if for some hard registers the sign extension is not performed, if for the ! 'REGNO_REG_CLASS' of these hard registers ! 'CANNOT_CHANGE_MODE_CLASS' returns nonzero when the FROM mode is MEM_MODE and the TO mode is any integral mode larger than this but ! not larger than 'word_mode'. ! You must return 'UNKNOWN' if for some hard registers that allow ! this mode, 'CANNOT_CHANGE_MODE_CLASS' says that they cannot change ! to 'word_mode', but that they can change to another integral mode ! that is larger then MEM_MODE but still smaller than 'word_mode'. -- Macro: SHORT_IMMEDIATES_SIGN_EXTEND Define this macro to 1 if loading short immediate values into --- 38062,38091 ---- -- Macro: LOAD_EXTEND_OP (MEM_MODE) Define this macro to be a C expression indicating when insns that ! read memory in MEM_MODE, an integral mode narrower than a word, ! set the bits outside of MEM_MODE to be either the sign-extension ! or the zero-extension of the data read. Return `SIGN_EXTEND' for ! values of MEM_MODE for which the insn sign-extends, `ZERO_EXTEND' ! for which it zero-extends, and `UNKNOWN' for other modes. This macro is not called with MEM_MODE non-integral or with a width ! greater than or equal to `BITS_PER_WORD', so you may return any value in this case. Do not define this macro if it would always ! return `UNKNOWN'. On machines where this macro is defined, you ! will normally define it as the constant `SIGN_EXTEND' or ! `ZERO_EXTEND'. ! You may return a non-`UNKNOWN' value even if for some hard registers the sign extension is not performed, if for the ! `REGNO_REG_CLASS' of these hard registers ! `CANNOT_CHANGE_MODE_CLASS' returns nonzero when the FROM mode is MEM_MODE and the TO mode is any integral mode larger than this but ! not larger than `word_mode'. ! You must return `UNKNOWN' if for some hard registers that allow ! this mode, `CANNOT_CHANGE_MODE_CLASS' says that they cannot change ! to `word_mode', but that they can change to another integral mode ! that is larger then MEM_MODE but still smaller than `word_mode'. -- Macro: SHORT_IMMEDIATES_SIGN_EXTEND Define this macro to 1 if loading short immediate values into *************** Here are several miscellaneous parameter *** 37653,37660 **** -- Target Hook: unsigned int TARGET_MIN_DIVISIONS_FOR_RECIP_MUL (machine_mode MODE) ! When '-ffast-math' is in effect, GCC tries to optimize divisions by ! the same divisor, by turning them into multiplications by the reciprocal. This target hook specifies the minimum number of divisions that should be there for GCC to perform the optimization for a variable of mode MODE. The default implementation returns 3 --- 38093,38100 ---- -- Target Hook: unsigned int TARGET_MIN_DIVISIONS_FOR_RECIP_MUL (machine_mode MODE) ! When `-ffast-math' is in effect, GCC tries to optimize divisions ! by the same divisor, by turning them into multiplications by the reciprocal. This target hook specifies the minimum number of divisions that should be there for GCC to perform the optimization for a variable of mode MODE. The default implementation returns 3 *************** Here are several miscellaneous parameter *** 37669,37690 **** -- Macro: MAX_MOVE_MAX The maximum number of bytes that a single instruction can move quickly between memory and registers or between two memory ! locations. If this is undefined, the default is 'MOVE_MAX'. Otherwise, it is the constant value that is the largest value that ! 'MOVE_MAX' can have at run-time. -- Macro: SHIFT_COUNT_TRUNCATED A C expression that is nonzero if on this machine the number of bits actually used for the count of a shift operation is equal to ! the number of bits needed to represent the size of the object being ! shifted. When this macro is nonzero, the compiler will assume that ! it is safe to omit a sign-extend, zero-extend, and certain bitwise ! 'and' instructions that truncates the count of a shift operation. ! On machines that have instructions that act on bit-fields at ! variable positions, which may include 'bit test' instructions, a ! nonzero 'SHIFT_COUNT_TRUNCATED' also enables deletion of ! truncations of the values that serve as arguments to bit-field ! instructions. If both types of instructions truncate the count (for shifts) and position (for bit-field operations), or if no variable-position --- 38109,38130 ---- -- Macro: MAX_MOVE_MAX The maximum number of bytes that a single instruction can move quickly between memory and registers or between two memory ! locations. If this is undefined, the default is `MOVE_MAX'. Otherwise, it is the constant value that is the largest value that ! `MOVE_MAX' can have at run-time. -- Macro: SHIFT_COUNT_TRUNCATED A C expression that is nonzero if on this machine the number of bits actually used for the count of a shift operation is equal to ! the number of bits needed to represent the size of the object ! being shifted. When this macro is nonzero, the compiler will ! assume that it is safe to omit a sign-extend, zero-extend, and ! certain bitwise `and' instructions that truncates the count of a ! shift operation. On machines that have instructions that act on ! bit-fields at variable positions, which may include `bit test' ! instructions, a nonzero `SHIFT_COUNT_TRUNCATED' also enables ! deletion of truncations of the values that serve as arguments to ! bit-field instructions. If both types of instructions truncate the count (for shifts) and position (for bit-field operations), or if no variable-position *************** Here are several miscellaneous parameter *** 37692,37703 **** However, on some machines, such as the 80386 and the 680x0, truncation only applies to shift operations and not the (real or ! pretended) bit-field operations. Define 'SHIFT_COUNT_TRUNCATED' to ! be zero on such machines. Instead, add patterns to the 'md' file ! that include the implied truncation of the shift instructions. ! You need not define this macro if it would always have the value of ! zero. -- Target Hook: unsigned HOST_WIDE_INT TARGET_SHIFT_TRUNCATION_MASK (machine_mode MODE) --- 38132,38143 ---- However, on some machines, such as the 80386 and the 680x0, truncation only applies to shift operations and not the (real or ! pretended) bit-field operations. Define `SHIFT_COUNT_TRUNCATED' ! to be zero on such machines. Instead, add patterns to the `md' ! file that include the implied truncation of the shift instructions. ! You need not define this macro if it would always have the value ! of zero. -- Target Hook: unsigned HOST_WIDE_INT TARGET_SHIFT_TRUNCATION_MASK (machine_mode MODE) *************** Here are several miscellaneous parameter *** 37712,37725 **** should return 0. A return value of 0 indicates that no particular behavior is guaranteed. ! Note that, unlike 'SHIFT_COUNT_TRUNCATED', this function does _not_ ! apply to general shift rtxes; it applies only to instructions that ! are generated by the named shift patterns. The default implementation of this function returns ! 'GET_MODE_BITSIZE (MODE) - 1' if 'SHIFT_COUNT_TRUNCATED' and 0 otherwise. This definition is always safe, but if ! 'SHIFT_COUNT_TRUNCATED' is false, and some shift patterns nevertheless truncate the shift count, you may get better code by overriding it. --- 38152,38165 ---- should return 0. A return value of 0 indicates that no particular behavior is guaranteed. ! Note that, unlike `SHIFT_COUNT_TRUNCATED', this function does ! _not_ apply to general shift rtxes; it applies only to instructions ! that are generated by the named shift patterns. The default implementation of this function returns ! `GET_MODE_BITSIZE (MODE) - 1' if `SHIFT_COUNT_TRUNCATED' and 0 otherwise. This definition is always safe, but if ! `SHIFT_COUNT_TRUNCATED' is false, and some shift patterns nevertheless truncate the shift count, you may get better code by overriding it. *************** Here are several miscellaneous parameter *** 37731,37773 **** On many machines, this expression can be 1. ! When 'TRULY_NOOP_TRUNCATION' returns 1 for a pair of sizes for ! modes for which 'MODES_TIEABLE_P' is 0, suboptimal code can result. ! If this is the case, making 'TRULY_NOOP_TRUNCATION' return 0 in such cases may improve things. -- Target Hook: int TARGET_MODE_REP_EXTENDED (machine_mode MODE, machine_mode REP_MODE) The representation of an integral mode can be such that the values ! are always extended to a wider integral mode. Return 'SIGN_EXTEND' ! if values of MODE are represented in sign-extended form to ! REP_MODE. Return 'UNKNOWN' otherwise. (Currently, none of the ! targets use zero-extended representation this way so unlike ! 'LOAD_EXTEND_OP', 'TARGET_MODE_REP_EXTENDED' is expected to return ! either 'SIGN_EXTEND' or 'UNKNOWN'. Also no target extends MODE to REP_MODE so that REP_MODE is not the next widest integral mode and currently we take advantage of this fact.) ! Similarly to 'LOAD_EXTEND_OP' you may return a non-'UNKNOWN' value ! even if the extension is not performed on certain hard registers as ! long as for the 'REGNO_REG_CLASS' of these hard registers ! 'CANNOT_CHANGE_MODE_CLASS' returns nonzero. ! Note that 'TARGET_MODE_REP_EXTENDED' and 'LOAD_EXTEND_OP' describe ! two related properties. If you define 'TARGET_MODE_REP_EXTENDED ! (mode, word_mode)' you probably also want to define 'LOAD_EXTEND_OP ! (mode)' to return the same type of extension. ! In order to enforce the representation of 'mode', ! 'TRULY_NOOP_TRUNCATION' should return false when truncating to ! 'mode'. -- Macro: STORE_FLAG_VALUE A C expression describing the value returned by a comparison operator with an integral mode and stored by a store-flag ! instruction ('cstoreMODE4') when the condition is true. This ! description must apply to _all_ the 'cstoreMODE4' patterns and all ! the comparison operators whose results have a 'MODE_INT' mode. A value of 1 or -1 means that the instruction implementing the comparison operator returns exactly 1 or -1 when the comparison is --- 38171,38213 ---- On many machines, this expression can be 1. ! When `TRULY_NOOP_TRUNCATION' returns 1 for a pair of sizes for ! modes for which `MODES_TIEABLE_P' is 0, suboptimal code can result. ! If this is the case, making `TRULY_NOOP_TRUNCATION' return 0 in such cases may improve things. -- Target Hook: int TARGET_MODE_REP_EXTENDED (machine_mode MODE, machine_mode REP_MODE) The representation of an integral mode can be such that the values ! are always extended to a wider integral mode. Return ! `SIGN_EXTEND' if values of MODE are represented in sign-extended ! form to REP_MODE. Return `UNKNOWN' otherwise. (Currently, none ! of the targets use zero-extended representation this way so unlike ! `LOAD_EXTEND_OP', `TARGET_MODE_REP_EXTENDED' is expected to return ! either `SIGN_EXTEND' or `UNKNOWN'. Also no target extends MODE to REP_MODE so that REP_MODE is not the next widest integral mode and currently we take advantage of this fact.) ! Similarly to `LOAD_EXTEND_OP' you may return a non-`UNKNOWN' value ! even if the extension is not performed on certain hard registers ! as long as for the `REGNO_REG_CLASS' of these hard registers ! `CANNOT_CHANGE_MODE_CLASS' returns nonzero. ! Note that `TARGET_MODE_REP_EXTENDED' and `LOAD_EXTEND_OP' describe ! two related properties. If you define `TARGET_MODE_REP_EXTENDED ! (mode, word_mode)' you probably also want to define ! `LOAD_EXTEND_OP (mode)' to return the same type of extension. ! In order to enforce the representation of `mode', ! `TRULY_NOOP_TRUNCATION' should return false when truncating to ! `mode'. -- Macro: STORE_FLAG_VALUE A C expression describing the value returned by a comparison operator with an integral mode and stored by a store-flag ! instruction (`cstoreMODE4') when the condition is true. This ! description must apply to _all_ the `cstoreMODE4' patterns and all ! the comparison operators whose results have a `MODE_INT' mode. A value of 1 or -1 means that the instruction implementing the comparison operator returns exactly 1 or -1 when the comparison is *************** Here are several miscellaneous parameter *** 37775,37791 **** indicates which bits of the result are guaranteed to be 1 when the comparison is true. This value is interpreted in the mode of the comparison operation, which is given by the mode of the first ! operand in the 'cstoreMODE4' pattern. Either the low bit or the ! sign bit of 'STORE_FLAG_VALUE' be on. Presently, only those bits are used by the compiler. ! If 'STORE_FLAG_VALUE' is neither 1 or -1, the compiler will generate code that depends only on the specified bits. It can also replace comparison operators with equivalent operations if they cause the required bits to be set, even if the remaining bits are undefined. For example, on a machine whose comparison operators ! return an 'SImode' value and where 'STORE_FLAG_VALUE' is defined as ! '0x80000000', saying that just the sign bit is relevant, the expression (ne:SI (and:SI X (const_int POWER-OF-2)) (const_int 0)) --- 38215,38231 ---- indicates which bits of the result are guaranteed to be 1 when the comparison is true. This value is interpreted in the mode of the comparison operation, which is given by the mode of the first ! operand in the `cstoreMODE4' pattern. Either the low bit or the ! sign bit of `STORE_FLAG_VALUE' be on. Presently, only those bits are used by the compiler. ! If `STORE_FLAG_VALUE' is neither 1 or -1, the compiler will generate code that depends only on the specified bits. It can also replace comparison operators with equivalent operations if they cause the required bits to be set, even if the remaining bits are undefined. For example, on a machine whose comparison operators ! return an `SImode' value and where `STORE_FLAG_VALUE' is defined as ! `0x80000000', saying that just the sign bit is relevant, the expression (ne:SI (and:SI X (const_int POWER-OF-2)) (const_int 0)) *************** Here are several miscellaneous parameter *** 37794,37817 **** (ashift:SI X (const_int N)) ! where N is the appropriate shift count to move the bit being tested ! into the sign bit. There is no way to describe a machine that always sets the ! low-order bit for a true value, but does not guarantee the value of ! any other bits, but we do not know of any machine that has such an ! instruction. If you are trying to port GCC to such a machine, include an instruction to perform a logical-and of the result with 1 in the pattern for the comparison operators and let us know at . Often, a machine will have multiple instructions that obtain a value from a comparison (or the condition codes). Here are rules ! to guide the choice of value for 'STORE_FLAG_VALUE', and hence the instructions to be used: * Use the shortest sequence that yields a valid definition for ! 'STORE_FLAG_VALUE'. It is more efficient for the compiler to "normalize" the value (convert it to, e.g., 1 or 0) than for the comparison operators to do so because there may be opportunities to combine the normalization with other --- 38234,38257 ---- (ashift:SI X (const_int N)) ! where N is the appropriate shift count to move the bit being ! tested into the sign bit. There is no way to describe a machine that always sets the ! low-order bit for a true value, but does not guarantee the value ! of any other bits, but we do not know of any machine that has such ! an instruction. If you are trying to port GCC to such a machine, include an instruction to perform a logical-and of the result with 1 in the pattern for the comparison operators and let us know at . Often, a machine will have multiple instructions that obtain a value from a comparison (or the condition codes). Here are rules ! to guide the choice of value for `STORE_FLAG_VALUE', and hence the instructions to be used: * Use the shortest sequence that yields a valid definition for ! `STORE_FLAG_VALUE'. It is more efficient for the compiler to "normalize" the value (convert it to, e.g., 1 or 0) than for the comparison operators to do so because there may be opportunities to combine the normalization with other *************** Here are several miscellaneous parameter *** 37821,37891 **** being slightly preferred on machines with expensive jumps and 1 preferred on other machines. ! * As a second choice, choose a value of '0x80000001' if instructions exist that set both the sign and low-order bits but do not define the others. ! * Otherwise, use a value of '0x80000000'. Many machines can produce both the value chosen for ! 'STORE_FLAG_VALUE' and its negation in the same number of instructions. On those machines, you should also define a pattern for those cases, e.g., one matching (set A (neg:M (ne:M B C))) ! Some machines can also perform 'and' or 'plus' operations on condition code values with less instructions than the corresponding ! 'cstoreMODE4' insn followed by 'and' or 'plus'. On those machines, ! define the appropriate patterns. Use the names 'incscc' and ! 'decscc', respectively, for the patterns which perform 'plus' or ! 'minus' operations on condition code values. See 'rs6000.md' for ! some examples. The GNU Superoptimizer can be used to find such ! instruction sequences on other machines. If this macro is not defined, the default value, 1, is used. You ! need not define 'STORE_FLAG_VALUE' if the machine has no store-flag instructions, or if the value generated by these instructions is 1. -- Macro: FLOAT_STORE_FLAG_VALUE (MODE) ! A C expression that gives a nonzero 'REAL_VALUE_TYPE' value that is returned when comparison operators with floating-point results are true. Define this macro on machines that have comparison ! operations that return floating-point values. If there are no such ! operations, do not define this macro. -- Macro: VECTOR_STORE_FLAG_VALUE (MODE) A C expression that gives a rtx representing the nonzero true element for vector comparisons. The returned rtx should be valid ! for the inner mode of MODE which is guaranteed to be a vector mode. ! Define this macro on machines that have vector comparison operations that return a vector result. If there are no such operations, do not define this macro. Typically, this macro is ! defined as 'const1_rtx' or 'constm1_rtx'. This macro may return ! 'NULL_RTX' to prevent the compiler optimizing such vector comparison operations for the given mode. -- Macro: CLZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE) -- Macro: CTZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE) A C expression that indicates whether the architecture defines a ! value for 'clz' or 'ctz' with a zero operand. A result of '0' ! indicates the value is undefined. If the value is defined for only ! the RTL expression, the macro should evaluate to '1'; if the value ! applies also to the corresponding optab entry (which is normally ! the case if it expands directly into the corresponding RTL), then ! the macro should evaluate to '2'. In the cases where the value is ! defined, VALUE should be set to this value. ! If this macro is not defined, the value of 'clz' or 'ctz' at zero is assumed to be undefined. ! This macro must be defined if the target's expansion for 'ffs' relies on a particular value to get correct results. Otherwise it is not necessary, though it may be used to optimize some corner ! cases, and to provide a default expansion for the 'ffs' optab. ! Note that regardless of this macro the "definedness" of 'clz' and ! 'ctz' at zero do _not_ extend to the builtin functions visible to the user. Thus one may be free to adjust the value at will to match the target expansion of these operations without fear of breaking the API. --- 38261,38331 ---- being slightly preferred on machines with expensive jumps and 1 preferred on other machines. ! * As a second choice, choose a value of `0x80000001' if instructions exist that set both the sign and low-order bits but do not define the others. ! * Otherwise, use a value of `0x80000000'. Many machines can produce both the value chosen for ! `STORE_FLAG_VALUE' and its negation in the same number of instructions. On those machines, you should also define a pattern for those cases, e.g., one matching (set A (neg:M (ne:M B C))) ! Some machines can also perform `and' or `plus' operations on condition code values with less instructions than the corresponding ! `cstoreMODE4' insn followed by `and' or `plus'. On those ! machines, define the appropriate patterns. Use the names `incscc' ! and `decscc', respectively, for the patterns which perform `plus' ! or `minus' operations on condition code values. See `rs6000.md' ! for some examples. The GNU Superoptimizer can be used to find ! such instruction sequences on other machines. If this macro is not defined, the default value, 1, is used. You ! need not define `STORE_FLAG_VALUE' if the machine has no store-flag instructions, or if the value generated by these instructions is 1. -- Macro: FLOAT_STORE_FLAG_VALUE (MODE) ! A C expression that gives a nonzero `REAL_VALUE_TYPE' value that is returned when comparison operators with floating-point results are true. Define this macro on machines that have comparison ! operations that return floating-point values. If there are no ! such operations, do not define this macro. -- Macro: VECTOR_STORE_FLAG_VALUE (MODE) A C expression that gives a rtx representing the nonzero true element for vector comparisons. The returned rtx should be valid ! for the inner mode of MODE which is guaranteed to be a vector ! mode. Define this macro on machines that have vector comparison operations that return a vector result. If there are no such operations, do not define this macro. Typically, this macro is ! defined as `const1_rtx' or `constm1_rtx'. This macro may return ! `NULL_RTX' to prevent the compiler optimizing such vector comparison operations for the given mode. -- Macro: CLZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE) -- Macro: CTZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE) A C expression that indicates whether the architecture defines a ! value for `clz' or `ctz' with a zero operand. A result of `0' ! indicates the value is undefined. If the value is defined for ! only the RTL expression, the macro should evaluate to `1'; if the ! value applies also to the corresponding optab entry (which is ! normally the case if it expands directly into the corresponding ! RTL), then the macro should evaluate to `2'. In the cases where ! the value is defined, VALUE should be set to this value. ! If this macro is not defined, the value of `clz' or `ctz' at zero is assumed to be undefined. ! This macro must be defined if the target's expansion for `ffs' relies on a particular value to get correct results. Otherwise it is not necessary, though it may be used to optimize some corner ! cases, and to provide a default expansion for the `ffs' optab. ! Note that regardless of this macro the "definedness" of `clz' and ! `ctz' at zero do _not_ extend to the builtin functions visible to the user. Thus one may be free to adjust the value at will to match the target expansion of these operations without fear of breaking the API. *************** Here are several miscellaneous parameter *** 37893,38031 **** -- Macro: Pmode An alias for the machine mode for pointers. On most machines, define this to be the integer mode corresponding to the width of a ! hardware pointer; 'SImode' on 32-bit machine or 'DImode' on 64-bit machines. On some machines you must define this to be one of the ! partial integer modes, such as 'PSImode'. ! The width of 'Pmode' must be at least as large as the value of ! 'POINTER_SIZE'. If it is not equal, you must define the macro ! 'POINTERS_EXTEND_UNSIGNED' to specify how pointers are extended to ! 'Pmode'. -- Macro: FUNCTION_MODE An alias for the machine mode used for memory references to ! functions being called, in 'call' RTL expressions. On most CISC machines, where an instruction can begin at any byte address, this ! should be 'QImode'. On most RISC machines, where all instructions have fixed size and alignment, this should be a mode with the same size and alignment as the machine instruction words - typically ! 'SImode' or 'HImode'. -- Macro: STDC_0_IN_SYSTEM_HEADERS ! In normal operation, the preprocessor expands '__STDC__' to the constant 1, to signify that GCC conforms to ISO Standard C. On some hosts, like Solaris, the system compiler uses a different ! convention, where '__STDC__' is normally 0, but is 1 if the user specifies strict conformance to the C Standard. ! Defining 'STDC_0_IN_SYSTEM_HEADERS' makes GNU CPP follows the host ! convention when processing system header files, but when processing ! user files '__STDC__' will always expand to 1. -- C Target Hook: const char * TARGET_C_PREINCLUDE (void) ! Define this hook to return the name of a header file to be included ! at the start of all compilations, as if it had been included with ! '#include '. If this hook returns 'NULL', or is not defined, ! or the header is not found, or if the user specifies ! '-ffreestanding' or '-nostdinc', no header is included. ! This hook can be used together with a header provided by the system ! C library to implement ISO C requirements for certain macros to be ! predefined that describe properties of the whole implementation ! rather than just the compiler. -- C Target Hook: bool TARGET_CXX_IMPLICIT_EXTERN_C (const char*) Define this hook to add target-specific C++ implicit extern C ! functions. If this function returns true for the name of a file-scope function, that function implicitly gets extern "C" ! linkage rather than whatever language linkage the declaration would ! normally have. An example of such function is WinMain on Win32 ! targets. -- Macro: NO_IMPLICIT_EXTERN_C ! Define this macro if the system header files support C++ as well as ! C. This macro inhibits the usual method of using system header files in C++, which is to pretend that the file's contents are ! enclosed in 'extern "C" {...}'. -- Macro: REGISTER_TARGET_PRAGMAS () Define this macro if you want to implement any target-specific pragmas. If defined, it is a C expression which makes a series of ! calls to 'c_register_pragma' or 'c_register_pragma_with_expansion' for each pragma. The macro may also do any setup required for the pragmas. ! The primary reason to define this macro is to provide compatibility ! with other compilers for the same target. In general, we ! discourage definition of target-specific pragmas for GCC. If the pragma can be implemented by attributes then you should ! consider defining the target hook 'TARGET_INSERT_ATTRIBUTES' as well. Preprocessor macros that appear on pragma lines are not expanded. ! All '#pragma' directives that do not match any registered pragma are silently ignored, unless the user specifies ! '-Wunknown-pragmas'. -- Function: void c_register_pragma (const char *SPACE, const char *NAME, void (*CALLBACK) (struct cpp_reader *)) -- Function: void c_register_pragma_with_expansion (const char *SPACE, const char *NAME, void (*CALLBACK) (struct cpp_reader *)) ! ! Each call to 'c_register_pragma' or ! 'c_register_pragma_with_expansion' establishes one pragma. The CALLBACK routine will be called when the preprocessor encounters a pragma of the form #pragma [SPACE] NAME ... ! SPACE is the case-sensitive namespace of the pragma, or 'NULL' to put the pragma in the global namespace. The callback routine receives PFILE as its first argument, which can be passed on to ! cpplib's functions if necessary. You can lex tokens after the NAME ! by calling 'pragma_lex'. Tokens that are not read by the callback ! will be silently ignored. The end of the line is indicated by a ! token of type 'CPP_EOF'. Macro expansion occurs on the arguments ! of pragmas registered with 'c_register_pragma_with_expansion' but ! not on the arguments of pragmas registered with ! 'c_register_pragma'. ! Note that the use of 'pragma_lex' is specific to the C and C++ compilers. It will not work in the Java or Fortran compilers, or ! any other language compilers for that matter. Thus if 'pragma_lex' ! is going to be called from target-specific code, it must only be ! done so when building the C and C++ compilers. This can be done by ! defining the variables 'c_target_objs' and 'cxx_target_objs' in the ! target entry in the 'config.gcc' file. These variables should name ! the target-specific, language-specific object file which contains ! the code that uses 'pragma_lex'. Note it will also be necessary to ! add a rule to the makefile fragment pointed to by 'tmake_file' that ! shows how to build this object file. -- Macro: HANDLE_PRAGMA_PACK_WITH_EXPANSION Define this macro if macros should be expanded in the arguments of ! '#pragma pack'. -- Macro: TARGET_DEFAULT_PACK_STRUCT If your target requires a structure packing default other than 0 (meaning the machine default), define this macro to the necessary ! value (in bytes). This must be a value that would also be valid to ! use with '#pragma pack()' (that is, a small power of two). -- Macro: DOLLARS_IN_IDENTIFIERS ! Define this macro to control use of the character '$' in identifier ! names for the C family of languages. 0 means '$' is not allowed by ! default; 1 means it is allowed. 1 is the default; there is no need ! to define this macro in that case. -- Macro: INSN_SETS_ARE_DELAYED (INSN) Define this macro as a C expression that is nonzero if it is safe for the delay slot scheduler to place instructions in the delay slot of INSN, even if they appear to use a resource set or ! clobbered in INSN. INSN is always a 'jump_insn' or an 'insn'; GCC ! knows that every 'call_insn' has this behavior. On machines where ! some 'insn' or 'jump_insn' is really a function call and hence has this behavior, you should define this macro. You need not define this macro if it would always return zero. --- 38333,38472 ---- -- Macro: Pmode An alias for the machine mode for pointers. On most machines, define this to be the integer mode corresponding to the width of a ! hardware pointer; `SImode' on 32-bit machine or `DImode' on 64-bit machines. On some machines you must define this to be one of the ! partial integer modes, such as `PSImode'. ! The width of `Pmode' must be at least as large as the value of ! `POINTER_SIZE'. If it is not equal, you must define the macro ! `POINTERS_EXTEND_UNSIGNED' to specify how pointers are extended to ! `Pmode'. -- Macro: FUNCTION_MODE An alias for the machine mode used for memory references to ! functions being called, in `call' RTL expressions. On most CISC machines, where an instruction can begin at any byte address, this ! should be `QImode'. On most RISC machines, where all instructions have fixed size and alignment, this should be a mode with the same size and alignment as the machine instruction words - typically ! `SImode' or `HImode'. -- Macro: STDC_0_IN_SYSTEM_HEADERS ! In normal operation, the preprocessor expands `__STDC__' to the constant 1, to signify that GCC conforms to ISO Standard C. On some hosts, like Solaris, the system compiler uses a different ! convention, where `__STDC__' is normally 0, but is 1 if the user specifies strict conformance to the C Standard. ! Defining `STDC_0_IN_SYSTEM_HEADERS' makes GNU CPP follows the host ! convention when processing system header files, but when ! processing user files `__STDC__' will always expand to 1. -- C Target Hook: const char * TARGET_C_PREINCLUDE (void) ! Define this hook to return the name of a header file to be ! included at the start of all compilations, as if it had been ! included with `#include '. If this hook returns `NULL', or ! is not defined, or the header is not found, or if the user ! specifies `-ffreestanding' or `-nostdinc', no header is included. ! This hook can be used together with a header provided by the ! system C library to implement ISO C requirements for certain ! macros to be predefined that describe properties of the whole ! implementation rather than just the compiler. -- C Target Hook: bool TARGET_CXX_IMPLICIT_EXTERN_C (const char*) Define this hook to add target-specific C++ implicit extern C ! functions. If this function returns true for the name of a file-scope function, that function implicitly gets extern "C" ! linkage rather than whatever language linkage the declaration ! would normally have. An example of such function is WinMain on ! Win32 targets. -- Macro: NO_IMPLICIT_EXTERN_C ! Define this macro if the system header files support C++ as well ! as C. This macro inhibits the usual method of using system header files in C++, which is to pretend that the file's contents are ! enclosed in `extern "C" {...}'. -- Macro: REGISTER_TARGET_PRAGMAS () Define this macro if you want to implement any target-specific pragmas. If defined, it is a C expression which makes a series of ! calls to `c_register_pragma' or `c_register_pragma_with_expansion' for each pragma. The macro may also do any setup required for the pragmas. ! The primary reason to define this macro is to provide ! compatibility with other compilers for the same target. In ! general, we discourage definition of target-specific pragmas for ! GCC. If the pragma can be implemented by attributes then you should ! consider defining the target hook `TARGET_INSERT_ATTRIBUTES' as well. Preprocessor macros that appear on pragma lines are not expanded. ! All `#pragma' directives that do not match any registered pragma are silently ignored, unless the user specifies ! `-Wunknown-pragmas'. -- Function: void c_register_pragma (const char *SPACE, const char *NAME, void (*CALLBACK) (struct cpp_reader *)) -- Function: void c_register_pragma_with_expansion (const char *SPACE, const char *NAME, void (*CALLBACK) (struct cpp_reader *)) ! Each call to `c_register_pragma' or ! `c_register_pragma_with_expansion' establishes one pragma. The CALLBACK routine will be called when the preprocessor encounters a pragma of the form #pragma [SPACE] NAME ... ! SPACE is the case-sensitive namespace of the pragma, or `NULL' to put the pragma in the global namespace. The callback routine receives PFILE as its first argument, which can be passed on to ! cpplib's functions if necessary. You can lex tokens after the ! NAME by calling `pragma_lex'. Tokens that are not read by the ! callback will be silently ignored. The end of the line is ! indicated by a token of type `CPP_EOF'. Macro expansion occurs on ! the arguments of pragmas registered with ! `c_register_pragma_with_expansion' but not on the arguments of ! pragmas registered with `c_register_pragma'. ! Note that the use of `pragma_lex' is specific to the C and C++ compilers. It will not work in the Java or Fortran compilers, or ! any other language compilers for that matter. Thus if ! `pragma_lex' is going to be called from target-specific code, it ! must only be done so when building the C and C++ compilers. This ! can be done by defining the variables `c_target_objs' and ! `cxx_target_objs' in the target entry in the `config.gcc' file. ! These variables should name the target-specific, language-specific ! object file which contains the code that uses `pragma_lex'. Note ! it will also be necessary to add a rule to the makefile fragment ! pointed to by `tmake_file' that shows how to build this object ! file. -- Macro: HANDLE_PRAGMA_PACK_WITH_EXPANSION Define this macro if macros should be expanded in the arguments of ! `#pragma pack'. -- Macro: TARGET_DEFAULT_PACK_STRUCT If your target requires a structure packing default other than 0 (meaning the machine default), define this macro to the necessary ! value (in bytes). This must be a value that would also be valid ! to use with `#pragma pack()' (that is, a small power of two). -- Macro: DOLLARS_IN_IDENTIFIERS ! Define this macro to control use of the character `$' in ! identifier names for the C family of languages. 0 means `$' is ! not allowed by default; 1 means it is allowed. 1 is the default; ! there is no need to define this macro in that case. -- Macro: INSN_SETS_ARE_DELAYED (INSN) Define this macro as a C expression that is nonzero if it is safe for the delay slot scheduler to place instructions in the delay slot of INSN, even if they appear to use a resource set or ! clobbered in INSN. INSN is always a `jump_insn' or an `insn'; GCC ! knows that every `call_insn' has this behavior. On machines where ! some `insn' or `jump_insn' is really a function call and hence has this behavior, you should define this macro. You need not define this macro if it would always return zero. *************** Here are several miscellaneous parameter *** 38034,38052 **** Define this macro as a C expression that is nonzero if it is safe for the delay slot scheduler to place instructions in the delay slot of INSN, even if they appear to set or clobber a resource ! referenced in INSN. INSN is always a 'jump_insn' or an 'insn'. On ! machines where some 'insn' or 'jump_insn' is really a function call ! and its operands are registers whose use is actually in the ! subroutine it calls, you should define this macro. Doing so allows ! the delay slot scheduler to move instructions which copy arguments ! into the argument registers into the delay slot of INSN. You need not define this macro if it would always return zero. -- Macro: MULTIPLE_SYMBOL_SPACES Define this macro as a C expression that is nonzero if, in some ! cases, global symbols from one translation unit may not be bound to ! undefined symbols in another translation unit without user intervention. For instance, under Microsoft Windows symbols must be explicitly imported from shared libraries (DLLs). --- 38475,38493 ---- Define this macro as a C expression that is nonzero if it is safe for the delay slot scheduler to place instructions in the delay slot of INSN, even if they appear to set or clobber a resource ! referenced in INSN. INSN is always a `jump_insn' or an `insn'. ! On machines where some `insn' or `jump_insn' is really a function ! call and its operands are registers whose use is actually in the ! subroutine it calls, you should define this macro. Doing so ! allows the delay slot scheduler to move instructions which copy ! arguments into the argument registers into the delay slot of INSN. You need not define this macro if it would always return zero. -- Macro: MULTIPLE_SYMBOL_SPACES Define this macro as a C expression that is nonzero if, in some ! cases, global symbols from one translation unit may not be bound ! to undefined symbols in another translation unit without user intervention. For instance, under Microsoft Windows symbols must be explicitly imported from shared libraries (DLLs). *************** Here are several miscellaneous parameter *** 38057,38138 **** CLOBBERS, HARD_REG_SET& CLOBBERED_REGS) This target hook may add "clobbers" to CLOBBERS and CLOBBERED_REGS for any hard regs the port wishes to automatically clobber for an ! asm. The OUTPUTS and INPUTS may be inspected to avoid clobbering a ! register that is already used by the asm. ! It may modify the OUTPUTS, INPUTS, and CONSTRAINTS as necessary for ! other pre-processing. In this case the return value is a sequence ! of insns to emit after the asm. -- Macro: MATH_LIBRARY ! Define this macro as a C string constant for the linker argument to ! link in the system math library, minus the initial '"-l"', or '""' ! if the target does not have a separate math library. ! You need only define this macro if the default of '"m"' is wrong. -- Macro: LIBRARY_PATH_ENV Define this macro as a C string constant for the environment variable that specifies where the linker should look for libraries. ! You need only define this macro if the default of '"LIBRARY_PATH"' is wrong. -- Macro: TARGET_POSIX_IO Define this macro if the target supports the following POSIX file ! functions, access, mkdir and file locking with fcntl / F_SETLKW. ! Defining 'TARGET_POSIX_IO' will enable the test coverage code to use file locking when exiting a program, which avoids race ! conditions if the program has forked. It will also create directories at run-time for cross-profiling. -- Macro: MAX_CONDITIONAL_EXECUTE - A C expression for the maximum number of instructions to execute via conditional execution instructions instead of a branch. A ! value of 'BRANCH_COST'+1 is the default if the machine does not use ! cc0, and 1 if it does use cc0. -- Macro: IFCVT_MODIFY_TESTS (CE_INFO, TRUE_EXPR, FALSE_EXPR) ! Used if the target needs to perform machine-dependent modifications ! on the conditionals used for turning basic blocks into ! conditionally executed code. CE_INFO points to a data structure, ! 'struct ce_if_block', which contains information about the ! currently processed blocks. TRUE_EXPR and FALSE_EXPR are the tests ! that are used for converting the then-block and the else-block, ! respectively. Set either TRUE_EXPR or FALSE_EXPR to a null pointer ! if the tests cannot be converted. -- Macro: IFCVT_MODIFY_MULTIPLE_TESTS (CE_INFO, BB, TRUE_EXPR, FALSE_EXPR) ! Like 'IFCVT_MODIFY_TESTS', but used when converting more ! complicated if-statements into conditions combined by 'and' and ! 'or' operations. BB contains the basic block that contains the test that is currently being processed and about to be turned into a condition. -- Macro: IFCVT_MODIFY_INSN (CE_INFO, PATTERN, INSN) A C expression to modify the PATTERN of an INSN that is to be converted to conditional execution format. CE_INFO points to a ! data structure, 'struct ce_if_block', which contains information about the currently processed blocks. -- Macro: IFCVT_MODIFY_FINAL (CE_INFO) ! A C expression to perform any final machine dependent modifications ! in converting code to conditional execution. The involved basic ! blocks can be found in the 'struct ce_if_block' structure that is ! pointed to by CE_INFO. -- Macro: IFCVT_MODIFY_CANCEL (CE_INFO) A C expression to cancel any machine dependent modifications in converting code to conditional execution. The involved basic ! blocks can be found in the 'struct ce_if_block' structure that is pointed to by CE_INFO. -- Macro: IFCVT_MACHDEP_INIT (CE_INFO) A C expression to initialize any machine specific data for ! if-conversion of the if-block in the 'struct ce_if_block' structure ! that is pointed to by CE_INFO. -- Target Hook: void TARGET_MACHINE_DEPENDENT_REORG (void) If non-null, this hook performs a target-specific pass over the --- 38498,38578 ---- CLOBBERS, HARD_REG_SET& CLOBBERED_REGS) This target hook may add "clobbers" to CLOBBERS and CLOBBERED_REGS for any hard regs the port wishes to automatically clobber for an ! asm. The OUTPUTS and INPUTS may be inspected to avoid clobbering ! a register that is already used by the asm. ! It may modify the OUTPUTS, INPUTS, and CONSTRAINTS as necessary ! for other pre-processing. In this case the return value is a ! sequence of insns to emit after the asm. -- Macro: MATH_LIBRARY ! Define this macro as a C string constant for the linker argument ! to link in the system math library, minus the initial `"-l"', or ! `""' if the target does not have a separate math library. ! You need only define this macro if the default of `"m"' is wrong. -- Macro: LIBRARY_PATH_ENV Define this macro as a C string constant for the environment variable that specifies where the linker should look for libraries. ! You need only define this macro if the default of `"LIBRARY_PATH"' is wrong. -- Macro: TARGET_POSIX_IO Define this macro if the target supports the following POSIX file ! functions, access, mkdir and file locking with fcntl / F_SETLKW. ! Defining `TARGET_POSIX_IO' will enable the test coverage code to use file locking when exiting a program, which avoids race ! conditions if the program has forked. It will also create directories at run-time for cross-profiling. -- Macro: MAX_CONDITIONAL_EXECUTE A C expression for the maximum number of instructions to execute via conditional execution instructions instead of a branch. A ! value of `BRANCH_COST'+1 is the default if the machine does not ! use cc0, and 1 if it does use cc0. -- Macro: IFCVT_MODIFY_TESTS (CE_INFO, TRUE_EXPR, FALSE_EXPR) ! Used if the target needs to perform machine-dependent ! modifications on the conditionals used for turning basic blocks ! into conditionally executed code. CE_INFO points to a data ! structure, `struct ce_if_block', which contains information about ! the currently processed blocks. TRUE_EXPR and FALSE_EXPR are the ! tests that are used for converting the then-block and the ! else-block, respectively. Set either TRUE_EXPR or FALSE_EXPR to a ! null pointer if the tests cannot be converted. -- Macro: IFCVT_MODIFY_MULTIPLE_TESTS (CE_INFO, BB, TRUE_EXPR, FALSE_EXPR) ! Like `IFCVT_MODIFY_TESTS', but used when converting more ! complicated if-statements into conditions combined by `and' and ! `or' operations. BB contains the basic block that contains the test that is currently being processed and about to be turned into a condition. -- Macro: IFCVT_MODIFY_INSN (CE_INFO, PATTERN, INSN) A C expression to modify the PATTERN of an INSN that is to be converted to conditional execution format. CE_INFO points to a ! data structure, `struct ce_if_block', which contains information about the currently processed blocks. -- Macro: IFCVT_MODIFY_FINAL (CE_INFO) ! A C expression to perform any final machine dependent ! modifications in converting code to conditional execution. The ! involved basic blocks can be found in the `struct ce_if_block' ! structure that is pointed to by CE_INFO. -- Macro: IFCVT_MODIFY_CANCEL (CE_INFO) A C expression to cancel any machine dependent modifications in converting code to conditional execution. The involved basic ! blocks can be found in the `struct ce_if_block' structure that is pointed to by CE_INFO. -- Macro: IFCVT_MACHDEP_INIT (CE_INFO) A C expression to initialize any machine specific data for ! if-conversion of the if-block in the `struct ce_if_block' ! structure that is pointed to by CE_INFO. -- Target Hook: void TARGET_MACHINE_DEPENDENT_REORG (void) If non-null, this hook performs a target-specific pass over the *************** Here are several miscellaneous parameter *** 38154,38169 **** functions that need to be defined. It should be a function that performs the necessary setup. ! Machine specific built-in functions can be useful to expand special ! machine instructions that would otherwise not normally be generated ! because they have no equivalent in the source language (for ! example, SIMD vector instructions or prefetch instructions). To create a built-in function, call the function ! 'lang_hooks.builtin_function' which is defined by the language front end. You can use any type nodes set up by ! 'build_common_tree_nodes'; only language front ends that use those ! two functions will call 'TARGET_INIT_BUILTINS'. -- Target Hook: tree TARGET_BUILTIN_DECL (unsigned CODE, bool INITIALIZE_P) --- 38594,38609 ---- functions that need to be defined. It should be a function that performs the necessary setup. ! Machine specific built-in functions can be useful to expand ! special machine instructions that would otherwise not normally be ! generated because they have no equivalent in the source language ! (for example, SIMD vector instructions or prefetch instructions). To create a built-in function, call the function ! `lang_hooks.builtin_function' which is defined by the language front end. You can use any type nodes set up by ! `build_common_tree_nodes'; only language front ends that use those ! two functions will call `TARGET_INIT_BUILTINS'. -- Target Hook: tree TARGET_BUILTIN_DECL (unsigned CODE, bool INITIALIZE_P) *************** Here are several miscellaneous parameter *** 38172,38185 **** returns the builtin function declaration for the builtin function code CODE. If there is no such builtin and it cannot be initialized at this time if INITIALIZE_P is true the function ! should return 'NULL_TREE'. If CODE is out of range the function ! should return 'error_mark_node'. -- Target Hook: rtx TARGET_EXPAND_BUILTIN (tree EXP, rtx TARGET, rtx SUBTARGET, machine_mode MODE, int IGNORE) - Expand a call to a machine specific built-in function that was set ! up by 'TARGET_INIT_BUILTINS'. EXP is the expression for the function call; the result should go to TARGET if that is convenient, and have mode MODE if that is convenient. SUBTARGET may be used as the target for computing one of EXP's operands. --- 38612,38624 ---- returns the builtin function declaration for the builtin function code CODE. If there is no such builtin and it cannot be initialized at this time if INITIALIZE_P is true the function ! should return `NULL_TREE'. If CODE is out of range the function ! should return `error_mark_node'. -- Target Hook: rtx TARGET_EXPAND_BUILTIN (tree EXP, rtx TARGET, rtx SUBTARGET, machine_mode MODE, int IGNORE) Expand a call to a machine specific built-in function that was set ! up by `TARGET_INIT_BUILTINS'. EXP is the expression for the function call; the result should go to TARGET if that is convenient, and have mode MODE if that is convenient. SUBTARGET may be used as the target for computing one of EXP's operands. *************** Here are several miscellaneous parameter *** 38192,38318 **** return fndecl of function implementing generic builtin whose code is passed in FCODE. Currently following built-in functions are obtained using this hook: -- Built-in Function: __bounds_type __chkp_bndmk (const void *LB, size_t SIZE) ! Function code - BUILT_IN_CHKP_BNDMK. This built-in function is ! used by Pointer Bounds Checker to create bound values. LB holds low bound of the resulting bounds. SIZE holds size of created bounds. -- Built-in Function: void __chkp_bndstx (const void *PTR, __bounds_type B, const void **LOC) ! Function code - 'BUILT_IN_CHKP_BNDSTX'. This built-in function is used by Pointer Bounds Checker to store bounds B for pointer PTR when PTR is stored by address LOC. -- Built-in Function: __bounds_type __chkp_bndldx (const void **LOC, const void *PTR) ! Function code - 'BUILT_IN_CHKP_BNDLDX'. This built-in function is used by Pointer Bounds Checker to get bounds of pointer PTR loaded by address LOC. -- Built-in Function: void __chkp_bndcl (const void *PTR, __bounds_type B) ! Function code - 'BUILT_IN_CHKP_BNDCL'. This built-in function ! is used by Pointer Bounds Checker to perform check for pointer ! PTR against lower bound of bounds B. -- Built-in Function: void __chkp_bndcu (const void *PTR, __bounds_type B) ! Function code - 'BUILT_IN_CHKP_BNDCU'. This built-in function ! is used by Pointer Bounds Checker to perform check for pointer ! PTR against upper bound of bounds B. -- Built-in Function: __bounds_type __chkp_bndret (void *PTR) ! Function code - 'BUILT_IN_CHKP_BNDRET'. This built-in function is used by Pointer Bounds Checker to obtain bounds returned by a call statement. PTR passed to built-in is ! 'SSA_NAME' returned by the call. -- Built-in Function: __bounds_type __chkp_intersect (__bounds_type B1, __bounds_type B2) ! Function code - 'BUILT_IN_CHKP_INTERSECT'. This built-in function returns intersection of bounds B1 and B2. -- Built-in Function: __bounds_type __chkp_narrow (const void *PTR, __bounds_type B, size_t S) ! Function code - 'BUILT_IN_CHKP_NARROW'. This built-in function returns intersection of bounds B and [PTR, PTR + S - ! '1']. -- Built-in Function: size_t __chkp_sizeof (const void *PTR) ! Function code - 'BUILT_IN_CHKP_SIZEOF'. This built-in ! function returns size of object referenced by PTR. PTR is ! always 'ADDR_EXPR' of 'VAR_DECL'. This built-in is used by Pointer Bounds Checker when bounds of object cannot be ! computed statically (e.g. object has incomplete type). -- Built-in Function: const void *__chkp_extract_lower (__bounds_type B) ! Function code - 'BUILT_IN_CHKP_EXTRACT_LOWER'. This built-in function returns lower bound of bounds B. -- Built-in Function: const void *__chkp_extract_upper (__bounds_type B) ! Function code - 'BUILT_IN_CHKP_EXTRACT_UPPER'. This built-in function returns upper bound of bounds B. -- Target Hook: tree TARGET_CHKP_BOUND_TYPE (void) Return type to be used for bounds -- Target Hook: enum machine_mode TARGET_CHKP_BOUND_MODE (void) Return mode to be used for bounds. -- Target Hook: tree TARGET_CHKP_MAKE_BOUNDS_CONSTANT (HOST_WIDE_INT LB, HOST_WIDE_INT UB) Return constant used to statically initialize constant bounds with specified lower bound LB and upper bounds UB. -- Target Hook: int TARGET_CHKP_INITIALIZE_BOUNDS (tree VAR, tree LB, tree UB, tree *STMTS) Generate a list of statements STMTS to initialize pointer bounds ! variable VAR with bounds LB and UB. Return the number of generated ! statements. -- Target Hook: tree TARGET_RESOLVE_OVERLOADED_BUILTIN (unsigned int LOC, tree FNDECL, void *ARGLIST) Select a replacement for a machine specific built-in function that ! was set up by 'TARGET_INIT_BUILTINS'. This is done _before_ regular type checking, and so allows the target to implement a crude form of function overloading. FNDECL is the declaration of the built-in function. ARGLIST is the list of arguments passed to the built-in function. The result is a complete expression that ! implements the operation, usually another 'CALL_EXPR'. ARGLIST ! really has type 'VEC(tree,gc)*' ! -- Target Hook: tree TARGET_FOLD_BUILTIN (tree FNDECL, int N_ARGS, tree ! *ARGP, bool IGNORE) ! Fold a call to a machine specific built-in function that was set up ! by 'TARGET_INIT_BUILTINS'. FNDECL is the declaration of the ! built-in function. N_ARGS is the number of arguments passed to the ! function; the arguments themselves are pointed to by ARGP. The ! result is another tree, valid for both GIMPLE and GENERIC, containing a simplified expression for the call's result. If IGNORE is true the value will be ignored. -- Target Hook: bool TARGET_GIMPLE_FOLD_BUILTIN (gimple_stmt_iterator *GSI) Fold a call to a machine specific built-in function that was set up ! by 'TARGET_INIT_BUILTINS'. GSI points to the gimple statement holding the function call. Returns true if any change was made to the GIMPLE stream. -- Target Hook: int TARGET_COMPARE_VERSION_PRIORITY (tree DECL1, tree DECL2) ! This hook is used to compare the target attributes in two functions ! to determine which function's features get higher priority. This ! is used during function multi-versioning to figure out the order in ! which two versions must be dispatched. A function version with a ! higher priority is checked for dispatching earlier. DECL1 and ! DECL2 are the two function decls that will be compared. -- Target Hook: tree TARGET_GET_FUNCTION_VERSIONS_DISPATCHER (void *DECL) This hook is used to get the dispatcher function for a set of ! function versions. The dispatcher function is called to invoke the ! right function version at run-time. DECL is one version from a set ! of semantically identical versions. -- Target Hook: tree TARGET_GENERATE_VERSION_DISPATCHER_BODY (void *ARG) --- 38631,38763 ---- return fndecl of function implementing generic builtin whose code is passed in FCODE. Currently following built-in functions are obtained using this hook: + -- Built-in Function: __bounds_type __chkp_bndmk (const void *LB, size_t SIZE) ! Function code - BUILT_IN_CHKP_BNDMK. This built-in function ! is used by Pointer Bounds Checker to create bound values. LB holds low bound of the resulting bounds. SIZE holds size of created bounds. -- Built-in Function: void __chkp_bndstx (const void *PTR, __bounds_type B, const void **LOC) ! Function code - `BUILT_IN_CHKP_BNDSTX'. This built-in function is used by Pointer Bounds Checker to store bounds B for pointer PTR when PTR is stored by address LOC. -- Built-in Function: __bounds_type __chkp_bndldx (const void **LOC, const void *PTR) ! Function code - `BUILT_IN_CHKP_BNDLDX'. This built-in function is used by Pointer Bounds Checker to get bounds of pointer PTR loaded by address LOC. -- Built-in Function: void __chkp_bndcl (const void *PTR, __bounds_type B) ! Function code - `BUILT_IN_CHKP_BNDCL'. This built-in ! function is used by Pointer Bounds Checker to perform check ! for pointer PTR against lower bound of bounds B. -- Built-in Function: void __chkp_bndcu (const void *PTR, __bounds_type B) ! Function code - `BUILT_IN_CHKP_BNDCU'. This built-in ! function is used by Pointer Bounds Checker to perform check ! for pointer PTR against upper bound of bounds B. -- Built-in Function: __bounds_type __chkp_bndret (void *PTR) ! Function code - `BUILT_IN_CHKP_BNDRET'. This built-in function is used by Pointer Bounds Checker to obtain bounds returned by a call statement. PTR passed to built-in is ! `SSA_NAME' returned by the call. -- Built-in Function: __bounds_type __chkp_intersect (__bounds_type B1, __bounds_type B2) ! Function code - `BUILT_IN_CHKP_INTERSECT'. This built-in function returns intersection of bounds B1 and B2. -- Built-in Function: __bounds_type __chkp_narrow (const void *PTR, __bounds_type B, size_t S) ! Function code - `BUILT_IN_CHKP_NARROW'. This built-in function returns intersection of bounds B and [PTR, PTR + S - ! `1']. -- Built-in Function: size_t __chkp_sizeof (const void *PTR) ! Function code - `BUILT_IN_CHKP_SIZEOF'. This built-in ! function returns size of object referenced by PTR. PTR is ! always `ADDR_EXPR' of `VAR_DECL'. This built-in is used by Pointer Bounds Checker when bounds of object cannot be ! computed statically (e.g. object has incomplete type). -- Built-in Function: const void *__chkp_extract_lower (__bounds_type B) ! Function code - `BUILT_IN_CHKP_EXTRACT_LOWER'. This built-in function returns lower bound of bounds B. -- Built-in Function: const void *__chkp_extract_upper (__bounds_type B) ! Function code - `BUILT_IN_CHKP_EXTRACT_UPPER'. This built-in function returns upper bound of bounds B. + -- Target Hook: tree TARGET_CHKP_BOUND_TYPE (void) Return type to be used for bounds + -- Target Hook: enum machine_mode TARGET_CHKP_BOUND_MODE (void) Return mode to be used for bounds. + -- Target Hook: tree TARGET_CHKP_MAKE_BOUNDS_CONSTANT (HOST_WIDE_INT LB, HOST_WIDE_INT UB) Return constant used to statically initialize constant bounds with specified lower bound LB and upper bounds UB. + -- Target Hook: int TARGET_CHKP_INITIALIZE_BOUNDS (tree VAR, tree LB, tree UB, tree *STMTS) Generate a list of statements STMTS to initialize pointer bounds ! variable VAR with bounds LB and UB. Return the number of ! generated statements. -- Target Hook: tree TARGET_RESOLVE_OVERLOADED_BUILTIN (unsigned int LOC, tree FNDECL, void *ARGLIST) Select a replacement for a machine specific built-in function that ! was set up by `TARGET_INIT_BUILTINS'. This is done _before_ regular type checking, and so allows the target to implement a crude form of function overloading. FNDECL is the declaration of the built-in function. ARGLIST is the list of arguments passed to the built-in function. The result is a complete expression that ! implements the operation, usually another `CALL_EXPR'. ARGLIST ! really has type `VEC(tree,gc)*' ! -- Target Hook: tree TARGET_FOLD_BUILTIN (tree FNDECL, int N_ARGS, ! tree *ARGP, bool IGNORE) ! Fold a call to a machine specific built-in function that was set ! up by `TARGET_INIT_BUILTINS'. FNDECL is the declaration of the ! built-in function. N_ARGS is the number of arguments passed to ! the function; the arguments themselves are pointed to by ARGP. ! The result is another tree, valid for both GIMPLE and GENERIC, containing a simplified expression for the call's result. If IGNORE is true the value will be ignored. -- Target Hook: bool TARGET_GIMPLE_FOLD_BUILTIN (gimple_stmt_iterator *GSI) Fold a call to a machine specific built-in function that was set up ! by `TARGET_INIT_BUILTINS'. GSI points to the gimple statement holding the function call. Returns true if any change was made to the GIMPLE stream. -- Target Hook: int TARGET_COMPARE_VERSION_PRIORITY (tree DECL1, tree DECL2) ! This hook is used to compare the target attributes in two ! functions to determine which function's features get higher ! priority. This is used during function multi-versioning to figure ! out the order in which two versions must be dispatched. A ! function version with a higher priority is checked for dispatching ! earlier. DECL1 and DECL2 are the two function decls that will be ! compared. -- Target Hook: tree TARGET_GET_FUNCTION_VERSIONS_DISPATCHER (void *DECL) This hook is used to get the dispatcher function for a set of ! function versions. The dispatcher function is called to invoke ! the right function version at run-time. DECL is one version from a ! set of semantically identical versions. -- Target Hook: tree TARGET_GENERATE_VERSION_DISPATCHER_BODY (void *ARG) *************** Here are several miscellaneous parameter *** 38325,38351 **** &ITERATIONS, const widest_int &ITERATIONS_MAX, unsigned int LOOP_DEPTH, bool ENTERED_AT_TOP) Return true if it is possible to use low-overhead loops ! ('doloop_end' and 'doloop_begin') for a particular loop. ! ITERATIONS gives the exact number of iterations, or 0 if not known. ! ITERATIONS_MAX gives the maximum number of iterations, or 0 if not ! known. LOOP_DEPTH is the nesting depth of the loop, with 1 for ! innermost loops, 2 for loops that contain innermost loops, and so ! on. ENTERED_AT_TOP is true if the loop is only entered from the ! top. ! This hook is only used if 'doloop_end' is available. The default implementation returns true. You can use ! 'can_use_doloop_if_innermost' if the loop must be the innermost, and if there are no other restrictions. -- Target Hook: const char * TARGET_INVALID_WITHIN_DOLOOP (const rtx_insn *INSN) - Take an instruction in INSN and return NULL if it is valid within a low-overhead loop, otherwise return a string explaining why doloop could not be applied. ! Many targets use special registers for low-overhead looping. For any instruction that clobbers these this function should return a string indicating the reason why the doloop could not be applied. By default, the RTL loop optimizer does not use a present doloop --- 38770,38795 ---- &ITERATIONS, const widest_int &ITERATIONS_MAX, unsigned int LOOP_DEPTH, bool ENTERED_AT_TOP) Return true if it is possible to use low-overhead loops ! (`doloop_end' and `doloop_begin') for a particular loop. ! ITERATIONS gives the exact number of iterations, or 0 if not ! known. ITERATIONS_MAX gives the maximum number of iterations, or ! 0 if not known. LOOP_DEPTH is the nesting depth of the loop, with ! 1 for innermost loops, 2 for loops that contain innermost loops, ! and so on. ENTERED_AT_TOP is true if the loop is only entered ! from the top. ! This hook is only used if `doloop_end' is available. The default implementation returns true. You can use ! `can_use_doloop_if_innermost' if the loop must be the innermost, and if there are no other restrictions. -- Target Hook: const char * TARGET_INVALID_WITHIN_DOLOOP (const rtx_insn *INSN) Take an instruction in INSN and return NULL if it is valid within a low-overhead loop, otherwise return a string explaining why doloop could not be applied. ! Many targets use special registers for low-overhead looping. For any instruction that clobbers these this function should return a string indicating the reason why the doloop could not be applied. By default, the RTL loop optimizer does not use a present doloop *************** Here are several miscellaneous parameter *** 38353,38438 **** instructions. -- Target Hook: bool TARGET_LEGITIMATE_COMBINED_INSN (rtx_insn *INSN) ! Take an instruction in INSN and return 'false' if the instruction is not appropriate as a combination of two or more instructions. The default is to accept all instructions. -- Target Hook: bool TARGET_CAN_FOLLOW_JUMP (const rtx_insn *FOLLOWER, const rtx_insn *FOLLOWEE) ! FOLLOWER and FOLLOWEE are JUMP_INSN instructions; return true if ! FOLLOWER may be modified to follow FOLLOWEE; false, if it can't. For example, on some targets, certain kinds of branches can't be ! made to follow through a hot/cold partitioning. -- Target Hook: bool TARGET_COMMUTATIVE_P (const_rtx X, int OUTER_CODE) ! This target hook returns 'true' if X is considered to be commutative. Usually, this is just COMMUTATIVE_P (X), but the HP PA doesn't consider PLUS to be commutative inside a MEM. OUTER_CODE is the rtx code of the enclosing rtl, if known, otherwise it is UNKNOWN. -- Target Hook: rtx TARGET_ALLOCATE_INITIAL_VALUE (rtx HARD_REG) - When the initial value of a hard register has been copied in a pseudo register, it is often not necessary to actually allocate ! another register to this pseudo register, because the original hard ! register or a stack slot it has been saved into can be used. ! 'TARGET_ALLOCATE_INITIAL_VALUE' is called at the start of register allocation once for each hard register that had its initial value ! copied by using 'get_func_hard_reg_initial_val' or ! 'get_hard_reg_initial_val'. Possible values are 'NULL_RTX', if you ! don't want to do any special allocation, a 'REG' rtx--that would ! typically be the hard register itself, if it is known not to be ! clobbered--or a 'MEM'. If you are returning a 'MEM', this is only ! a hint for the allocator; it might decide to use another register ! anyways. You may use 'current_function_is_leaf' or 'REG_N_SETS' in ! the hook to determine if the hard register in question will not be ! clobbered. The default value of this hook is 'NULL', which ! disables any special allocation. -- Target Hook: int TARGET_UNSPEC_MAY_TRAP_P (const_rtx X, unsigned FLAGS) ! This target hook returns nonzero if X, an 'unspec' or ! 'unspec_volatile' operation, might cause a trap. Targets can use ! this hook to enhance precision of analysis for 'unspec' and ! 'unspec_volatile' operations. You may call 'may_trap_p_1' to analyze inner elements of X in which case FLAGS should be passed along. -- Target Hook: void TARGET_SET_CURRENT_FUNCTION (tree DECL) The compiler invokes this hook whenever it changes its current ! function context ('cfun'). You can define this function if the back end needs to perform any initialization or reset actions on a per-function basis. For example, it may be used to implement function attributes that affect register usage or code generation patterns. The argument DECL is the declaration for the new ! function context, and may be null to indicate that the compiler has ! left a function context and is returning to processing at the top ! level. The default hook function does nothing. ! GCC sets 'cfun' to a dummy function context during initialization ! of some parts of the back end. The hook function is not invoked in ! this situation; you need not worry about the hook being invoked recursively, or when the back end is in a partially-initialized ! state. 'cfun' might be 'NULL' to indicate processing at top level, outside of any function scope. -- Macro: TARGET_OBJECT_SUFFIX Define this macro to be a C string representing the suffix for object files on your target machine. If you do not define this ! macro, GCC will use '.o' as the suffix for object files. -- Macro: TARGET_EXECUTABLE_SUFFIX Define this macro to be a C string representing the suffix to be ! automatically added to executable files on your target machine. If ! you do not define this macro, GCC will use the null string as the ! suffix for executable files. -- Macro: COLLECT_EXPORT_LIST ! If defined, 'collect2' will scan the individual object files specified on its command line and create an export list for the linker. Define this macro for systems like AIX, where the linker ! discards object files that are not referenced from 'main' and uses export lists. -- Macro: MODIFY_JNI_METHOD_CALL (MDECL) --- 38797,38881 ---- instructions. -- Target Hook: bool TARGET_LEGITIMATE_COMBINED_INSN (rtx_insn *INSN) ! Take an instruction in INSN and return `false' if the instruction is not appropriate as a combination of two or more instructions. The default is to accept all instructions. -- Target Hook: bool TARGET_CAN_FOLLOW_JUMP (const rtx_insn *FOLLOWER, const rtx_insn *FOLLOWEE) ! FOLLOWER and FOLLOWEE are JUMP_INSN instructions; return true if ! FOLLOWER may be modified to follow FOLLOWEE; false, if it can't. For example, on some targets, certain kinds of branches can't be ! made to follow through a hot/cold partitioning. -- Target Hook: bool TARGET_COMMUTATIVE_P (const_rtx X, int OUTER_CODE) ! This target hook returns `true' if X is considered to be commutative. Usually, this is just COMMUTATIVE_P (X), but the HP PA doesn't consider PLUS to be commutative inside a MEM. OUTER_CODE is the rtx code of the enclosing rtl, if known, otherwise it is UNKNOWN. -- Target Hook: rtx TARGET_ALLOCATE_INITIAL_VALUE (rtx HARD_REG) When the initial value of a hard register has been copied in a pseudo register, it is often not necessary to actually allocate ! another register to this pseudo register, because the original ! hard register or a stack slot it has been saved into can be used. ! `TARGET_ALLOCATE_INITIAL_VALUE' is called at the start of register allocation once for each hard register that had its initial value ! copied by using `get_func_hard_reg_initial_val' or ! `get_hard_reg_initial_val'. Possible values are `NULL_RTX', if ! you don't want to do any special allocation, a `REG' rtx--that ! would typically be the hard register itself, if it is known not to ! be clobbered--or a `MEM'. If you are returning a `MEM', this is ! only a hint for the allocator; it might decide to use another ! register anyways. You may use `current_function_is_leaf' or ! `REG_N_SETS' in the hook to determine if the hard register in ! question will not be clobbered. The default value of this hook is ! `NULL', which disables any special allocation. -- Target Hook: int TARGET_UNSPEC_MAY_TRAP_P (const_rtx X, unsigned FLAGS) ! This target hook returns nonzero if X, an `unspec' or ! `unspec_volatile' operation, might cause a trap. Targets can use ! this hook to enhance precision of analysis for `unspec' and ! `unspec_volatile' operations. You may call `may_trap_p_1' to analyze inner elements of X in which case FLAGS should be passed along. -- Target Hook: void TARGET_SET_CURRENT_FUNCTION (tree DECL) The compiler invokes this hook whenever it changes its current ! function context (`cfun'). You can define this function if the back end needs to perform any initialization or reset actions on a per-function basis. For example, it may be used to implement function attributes that affect register usage or code generation patterns. The argument DECL is the declaration for the new ! function context, and may be null to indicate that the compiler ! has left a function context and is returning to processing at the ! top level. The default hook function does nothing. ! GCC sets `cfun' to a dummy function context during initialization ! of some parts of the back end. The hook function is not invoked ! in this situation; you need not worry about the hook being invoked recursively, or when the back end is in a partially-initialized ! state. `cfun' might be `NULL' to indicate processing at top level, outside of any function scope. -- Macro: TARGET_OBJECT_SUFFIX Define this macro to be a C string representing the suffix for object files on your target machine. If you do not define this ! macro, GCC will use `.o' as the suffix for object files. -- Macro: TARGET_EXECUTABLE_SUFFIX Define this macro to be a C string representing the suffix to be ! automatically added to executable files on your target machine. ! If you do not define this macro, GCC will use the null string as ! the suffix for executable files. -- Macro: COLLECT_EXPORT_LIST ! If defined, `collect2' will scan the individual object files specified on its command line and create an export list for the linker. Define this macro for systems like AIX, where the linker ! discards object files that are not referenced from `main' and uses export lists. -- Macro: MODIFY_JNI_METHOD_CALL (MDECL) *************** Here are several miscellaneous parameter *** 38440,38446 **** method call MDECL, if Java Native Interface (JNI) methods must be invoked differently from other methods on your target. For example, on 32-bit Microsoft Windows, JNI methods must be invoked ! using the 'stdcall' calling convention and this macro is then defined as this expression: build_type_attribute_variant (MDECL, --- 38883,38889 ---- method call MDECL, if Java Native Interface (JNI) methods must be invoked differently from other methods on your target. For example, on 32-bit Microsoft Windows, JNI methods must be invoked ! using the `stdcall' calling convention and this macro is then defined as this expression: build_type_attribute_variant (MDECL, *************** Here are several miscellaneous parameter *** 38449,38459 **** NULL)) -- Target Hook: bool TARGET_CANNOT_MODIFY_JUMPS_P (void) ! This target hook returns 'true' past the point in which new jump ! instructions could be created. On machines that require a register ! for every jump such as the SHmedia ISA of SH5, this point would ! typically be reload, so this target hook should be defined to a ! function such as: static bool cannot_modify_jumps_past_reload_p () --- 38892,38902 ---- NULL)) -- Target Hook: bool TARGET_CANNOT_MODIFY_JUMPS_P (void) ! This target hook returns `true' past the point in which new jump ! instructions could be created. On machines that require a ! register for every jump such as the SHmedia ISA of SH5, this point ! would typically be reload, so this target hook should be defined ! to a function such as: static bool cannot_modify_jumps_past_reload_p () *************** Here are several miscellaneous parameter *** 38464,38485 **** -- Target Hook: reg_class_t TARGET_BRANCH_TARGET_REGISTER_CLASS (void) This target hook returns a register class for which branch target register optimizations should be applied. All registers in this ! class should be usable interchangeably. After reload, registers in ! this class will be re-allocated and loads will be hoisted out of ! loops and be subjected to inter-block scheduling. -- Target Hook: bool TARGET_BRANCH_TARGET_REGISTER_CALLEE_SAVED (bool AFTER_PROLOGUE_EPILOGUE_GEN) Branch target register optimization will by default exclude ! callee-saved registers that are not already live during the current ! function; if this target hook returns true, they will be included. ! The target code must than make sure that all target registers in ! the class returned by 'TARGET_BRANCH_TARGET_REGISTER_CLASS' that ! might need saving are saved. AFTER_PROLOGUE_EPILOGUE_GEN indicates ! if prologues and epilogues have already been generated. Note, even ! if you only return true when AFTER_PROLOGUE_EPILOGUE_GEN is false, ! you still are likely to have to make special provisions in ! 'INITIAL_ELIMINATION_OFFSET' to reserve space for caller-saved target registers. -- Target Hook: bool TARGET_HAVE_CONDITIONAL_EXECUTION (void) --- 38907,38929 ---- -- Target Hook: reg_class_t TARGET_BRANCH_TARGET_REGISTER_CLASS (void) This target hook returns a register class for which branch target register optimizations should be applied. All registers in this ! class should be usable interchangeably. After reload, registers ! in this class will be re-allocated and loads will be hoisted out ! of loops and be subjected to inter-block scheduling. -- Target Hook: bool TARGET_BRANCH_TARGET_REGISTER_CALLEE_SAVED (bool AFTER_PROLOGUE_EPILOGUE_GEN) Branch target register optimization will by default exclude ! callee-saved registers that are not already live during the ! current function; if this target hook returns true, they will be ! included. The target code must than make sure that all target ! registers in the class returned by ! `TARGET_BRANCH_TARGET_REGISTER_CLASS' that might need saving are ! saved. AFTER_PROLOGUE_EPILOGUE_GEN indicates if prologues and ! epilogues have already been generated. Note, even if you only ! return true when AFTER_PROLOGUE_EPILOGUE_GEN is false, you still ! are likely to have to make special provisions in ! `INITIAL_ELIMINATION_OFFSET' to reserve space for caller-saved target registers. -- Target Hook: bool TARGET_HAVE_CONDITIONAL_EXECUTION (void) *************** Here are several miscellaneous parameter *** 38488,38526 **** several different modes and they have different conditional execution capability, such as ARM. ! -- Target Hook: rtx TARGET_GEN_CCMP_FIRST (rtx *PREP_SEQ, rtx *GEN_SEQ, ! int CODE, tree OP0, tree OP1) This function prepares to emit a comparison insn for the first ! compare in a sequence of conditional comparisions. It returns an ! appropriate comparison with 'CC' for passing to 'gen_ccmp_next' or ! 'cbranch_optab'. The insns to prepare the compare are saved in ! PREP_SEQ and the compare insns are saved in GEN_SEQ. They will be ! emitted when all the compares in the the conditional comparision ! are generated without error. CODE is the 'rtx_code' of the compare ! for OP0 and OP1. -- Target Hook: rtx TARGET_GEN_CCMP_NEXT (rtx *PREP_SEQ, rtx *GEN_SEQ, rtx PREV, int CMP_CODE, tree OP0, tree OP1, int BIT_CODE) This function prepares to emit a conditional comparison within a ! sequence of conditional comparisons. It returns an appropriate ! comparison with 'CC' for passing to 'gen_ccmp_next' or ! 'cbranch_optab'. The insns to prepare the compare are saved in ! PREP_SEQ and the compare insns are saved in GEN_SEQ. They will be ! emitted when all the compares in the conditional comparision are ! generated without error. The PREV expression is the result of a ! prior call to 'gen_ccmp_first' or 'gen_ccmp_next'. It may return ! 'NULL' if the combination of PREV and this comparison is not ! supported, otherwise the result must be appropriate for passing to ! 'gen_ccmp_next' or 'cbranch_optab'. CODE is the 'rtx_code' of the ! compare for OP0 and OP1. BIT_CODE is 'AND' or 'IOR', which is the ! op on the compares. -- Target Hook: unsigned TARGET_LOOP_UNROLL_ADJUST (unsigned NUNROLL, struct loop *LOOP) This target hook returns a new value for the number of times LOOP ! should be unrolled. The parameter NUNROLL is the number of times ! the loop is to be unrolled. The parameter LOOP is a pointer to the ! loop, which is going to be checked for unrolling. This target hook is required only when the target has special constraints like maximum number of memory accesses. --- 38932,38970 ---- several different modes and they have different conditional execution capability, such as ARM. ! -- Target Hook: rtx TARGET_GEN_CCMP_FIRST (rtx *PREP_SEQ, rtx ! *GEN_SEQ, int CODE, tree OP0, tree OP1) This function prepares to emit a comparison insn for the first ! compare in a sequence of conditional comparisions. It returns an ! appropriate comparison with `CC' for passing to `gen_ccmp_next' ! or `cbranch_optab'. The insns to prepare the compare are saved ! in PREP_SEQ and the compare insns are saved in GEN_SEQ. They ! will be emitted when all the compares in the the conditional ! comparision are generated without error. CODE is the `rtx_code' ! of the compare for OP0 and OP1. -- Target Hook: rtx TARGET_GEN_CCMP_NEXT (rtx *PREP_SEQ, rtx *GEN_SEQ, rtx PREV, int CMP_CODE, tree OP0, tree OP1, int BIT_CODE) This function prepares to emit a conditional comparison within a ! sequence of conditional comparisons. It returns an appropriate ! comparison with `CC' for passing to `gen_ccmp_next' or ! `cbranch_optab'. The insns to prepare the compare are saved in ! PREP_SEQ and the compare insns are saved in GEN_SEQ. They will ! be emitted when all the compares in the conditional comparision ! are generated without error. The PREV expression is the result ! of a prior call to `gen_ccmp_first' or `gen_ccmp_next'. It may ! return `NULL' if the combination of PREV and this comparison is ! not supported, otherwise the result must be appropriate for ! passing to `gen_ccmp_next' or `cbranch_optab'. CODE is the ! `rtx_code' of the compare for OP0 and OP1. BIT_CODE is `AND' or ! `IOR', which is the op on the compares. -- Target Hook: unsigned TARGET_LOOP_UNROLL_ADJUST (unsigned NUNROLL, struct loop *LOOP) This target hook returns a new value for the number of times LOOP ! should be unrolled. The parameter NUNROLL is the number of times ! the loop is to be unrolled. The parameter LOOP is a pointer to the ! loop, which is going to be checked for unrolling. This target hook is required only when the target has special constraints like maximum number of memory accesses. *************** Here are several miscellaneous parameter *** 38531,38590 **** exponentiation by an integer constant inline. When this value is defined, exponentiation requiring more than this number of multiplications is implemented by calling the system library's ! 'pow', 'powf' or 'powl' routines. The default value places no upper bound on the multiplication count. -- Macro: void TARGET_EXTRA_INCLUDES (const char *SYSROOT, const char *IPREFIX, int STDINC) This target hook should register any extra include files for the ! target. The parameter STDINC indicates if normal include files are ! present. The parameter SYSROOT is the system root directory. The ! parameter IPREFIX is the prefix for the gcc directory. -- Macro: void TARGET_EXTRA_PRE_INCLUDES (const char *SYSROOT, const char *IPREFIX, int STDINC) This target hook should register any extra include files for the ! target before any standard headers. The parameter STDINC indicates ! if normal include files are present. The parameter SYSROOT is the ! system root directory. The parameter IPREFIX is the prefix for the ! gcc directory. -- Macro: void TARGET_OPTF (char *PATH) This target hook should register special include paths for the target. The parameter PATH is the include to register. On Darwin systems, this is used for Framework includes, which have semantics ! that are different from '-I'. -- Macro: bool TARGET_USE_LOCAL_THUNK_ALIAS_P (tree FNDECL) ! This target macro returns 'true' if it is safe to use a local alias ! for a virtual function FNDECL when constructing thunks, 'false' ! otherwise. By default, the macro returns 'true' for all functions, ! if a target supports aliases (i.e. defines 'ASM_OUTPUT_DEF'), ! 'false' otherwise, -- Macro: TARGET_FORMAT_TYPES If defined, this macro is the name of a global variable containing ! target-specific format checking information for the '-Wformat' option. The default is to have no target-specific format checks. -- Macro: TARGET_N_FORMAT_TYPES If defined, this macro is the number of entries in ! 'TARGET_FORMAT_TYPES'. -- Macro: TARGET_OVERRIDES_FORMAT_ATTRIBUTES If defined, this macro is the name of a global variable containing ! target-specific format overrides for the '-Wformat' option. The ! default is to have no target-specific format overrides. If ! defined, 'TARGET_FORMAT_TYPES' must be defined, too. -- Macro: TARGET_OVERRIDES_FORMAT_ATTRIBUTES_COUNT If defined, this macro specifies the number of entries in ! 'TARGET_OVERRIDES_FORMAT_ATTRIBUTES'. -- Macro: TARGET_OVERRIDES_FORMAT_INIT If defined, this macro specifies the optional initialization ! routine for target specific customizations of the system printf and ! scanf formatter settings. -- Target Hook: const char * TARGET_INVALID_ARG_FOR_UNPROTOTYPED_FN (const_tree TYPELIST, const_tree FUNCDECL, const_tree VAL) --- 38975,39034 ---- exponentiation by an integer constant inline. When this value is defined, exponentiation requiring more than this number of multiplications is implemented by calling the system library's ! `pow', `powf' or `powl' routines. The default value places no upper bound on the multiplication count. -- Macro: void TARGET_EXTRA_INCLUDES (const char *SYSROOT, const char *IPREFIX, int STDINC) This target hook should register any extra include files for the ! target. The parameter STDINC indicates if normal include files ! are present. The parameter SYSROOT is the system root directory. ! The parameter IPREFIX is the prefix for the gcc directory. -- Macro: void TARGET_EXTRA_PRE_INCLUDES (const char *SYSROOT, const char *IPREFIX, int STDINC) This target hook should register any extra include files for the ! target before any standard headers. The parameter STDINC ! indicates if normal include files are present. The parameter ! SYSROOT is the system root directory. The parameter IPREFIX is ! the prefix for the gcc directory. -- Macro: void TARGET_OPTF (char *PATH) This target hook should register special include paths for the target. The parameter PATH is the include to register. On Darwin systems, this is used for Framework includes, which have semantics ! that are different from `-I'. -- Macro: bool TARGET_USE_LOCAL_THUNK_ALIAS_P (tree FNDECL) ! This target macro returns `true' if it is safe to use a local alias ! for a virtual function FNDECL when constructing thunks, `false' ! otherwise. By default, the macro returns `true' for all ! functions, if a target supports aliases (i.e. defines ! `ASM_OUTPUT_DEF'), `false' otherwise, -- Macro: TARGET_FORMAT_TYPES If defined, this macro is the name of a global variable containing ! target-specific format checking information for the `-Wformat' option. The default is to have no target-specific format checks. -- Macro: TARGET_N_FORMAT_TYPES If defined, this macro is the number of entries in ! `TARGET_FORMAT_TYPES'. -- Macro: TARGET_OVERRIDES_FORMAT_ATTRIBUTES If defined, this macro is the name of a global variable containing ! target-specific format overrides for the `-Wformat' option. The ! default is to have no target-specific format overrides. If defined, ! `TARGET_FORMAT_TYPES' must be defined, too. -- Macro: TARGET_OVERRIDES_FORMAT_ATTRIBUTES_COUNT If defined, this macro specifies the number of entries in ! `TARGET_OVERRIDES_FORMAT_ATTRIBUTES'. -- Macro: TARGET_OVERRIDES_FORMAT_INIT If defined, this macro specifies the optional initialization ! routine for target specific customizations of the system printf ! and scanf formatter settings. -- Target Hook: const char * TARGET_INVALID_ARG_FOR_UNPROTOTYPED_FN (const_tree TYPELIST, const_tree FUNCDECL, const_tree VAL) *************** Here are several miscellaneous parameter *** 38595,38661 **** -- Target Hook: const char * TARGET_INVALID_CONVERSION (const_tree FROMTYPE, const_tree TOTYPE) If defined, this macro returns the diagnostic message when it is ! invalid to convert from FROMTYPE to TOTYPE, or 'NULL' if validity should be determined by the front end. -- Target Hook: const char * TARGET_INVALID_UNARY_OP (int OP, const_tree TYPE) If defined, this macro returns the diagnostic message when it is invalid to apply operation OP (where unary plus is denoted by ! 'CONVERT_EXPR') to an operand of type TYPE, or 'NULL' if validity should be determined by the front end. -- Target Hook: const char * TARGET_INVALID_BINARY_OP (int OP, const_tree TYPE1, const_tree TYPE2) If defined, this macro returns the diagnostic message when it is ! invalid to apply operation OP to operands of types TYPE1 and TYPE2, ! or 'NULL' if validity should be determined by the front end. -- Target Hook: const char * TARGET_INVALID_PARAMETER_TYPE (const_tree TYPE) If defined, this macro returns the diagnostic message when it is ! invalid for functions to include parameters of type TYPE, or 'NULL' ! if validity should be determined by the front end. This is currently used only by the C and C++ front ends. -- Target Hook: const char * TARGET_INVALID_RETURN_TYPE (const_tree TYPE) If defined, this macro returns the diagnostic message when it is ! invalid for functions to have return type TYPE, or 'NULL' if validity should be determined by the front end. This is currently used only by the C and C++ front ends. -- Target Hook: tree TARGET_PROMOTED_TYPE (const_tree TYPE) If defined, this target hook returns the type to which values of TYPE should be promoted when they appear in expressions, analogous ! to the integer promotions, or 'NULL_TREE' to use the front end's normal promotion rules. This hook is useful when there are target-specific types with special promotion rules. This is currently used only by the C and C++ front ends. -- Target Hook: tree TARGET_CONVERT_TO_TYPE (tree TYPE, tree EXPR) If defined, this hook returns the result of converting EXPR to ! TYPE. It should return the converted expression, or 'NULL_TREE' to ! apply the front end's normal conversion rules. This hook is useful ! when there are target-specific types with special conversion rules. ! This is currently used only by the C and C++ front ends. -- Macro: TARGET_USE_JCR_SECTION This macro determines whether to use the JCR section to register ! Java classes. By default, TARGET_USE_JCR_SECTION is defined to 1 ! if both SUPPORTS_WEAK and TARGET_HAVE_NAMED_SECTIONS are true, else ! 0. -- Macro: OBJC_JBLEN This macro determines the size of the objective C jump buffer for ! the NeXT runtime. By default, OBJC_JBLEN is defined to an innocuous value. -- Macro: LIBGCC2_UNWIND_ATTRIBUTE Define this macro if any target-specific attributes need to be ! attached to the functions in 'libgcc' that provide low-level support for call stack unwinding. It is used in declarations in ! 'unwind-generic.h' and the associated definitions of those functions. -- Target Hook: void TARGET_UPDATE_STACK_BOUNDARY (void) --- 39039,39106 ---- -- Target Hook: const char * TARGET_INVALID_CONVERSION (const_tree FROMTYPE, const_tree TOTYPE) If defined, this macro returns the diagnostic message when it is ! invalid to convert from FROMTYPE to TOTYPE, or `NULL' if validity should be determined by the front end. -- Target Hook: const char * TARGET_INVALID_UNARY_OP (int OP, const_tree TYPE) If defined, this macro returns the diagnostic message when it is invalid to apply operation OP (where unary plus is denoted by ! `CONVERT_EXPR') to an operand of type TYPE, or `NULL' if validity should be determined by the front end. -- Target Hook: const char * TARGET_INVALID_BINARY_OP (int OP, const_tree TYPE1, const_tree TYPE2) If defined, this macro returns the diagnostic message when it is ! invalid to apply operation OP to operands of types TYPE1 and ! TYPE2, or `NULL' if validity should be determined by the front end. -- Target Hook: const char * TARGET_INVALID_PARAMETER_TYPE (const_tree TYPE) If defined, this macro returns the diagnostic message when it is ! invalid for functions to include parameters of type TYPE, or ! `NULL' if validity should be determined by the front end. This is currently used only by the C and C++ front ends. -- Target Hook: const char * TARGET_INVALID_RETURN_TYPE (const_tree TYPE) If defined, this macro returns the diagnostic message when it is ! invalid for functions to have return type TYPE, or `NULL' if validity should be determined by the front end. This is currently used only by the C and C++ front ends. -- Target Hook: tree TARGET_PROMOTED_TYPE (const_tree TYPE) If defined, this target hook returns the type to which values of TYPE should be promoted when they appear in expressions, analogous ! to the integer promotions, or `NULL_TREE' to use the front end's normal promotion rules. This hook is useful when there are target-specific types with special promotion rules. This is currently used only by the C and C++ front ends. -- Target Hook: tree TARGET_CONVERT_TO_TYPE (tree TYPE, tree EXPR) If defined, this hook returns the result of converting EXPR to ! TYPE. It should return the converted expression, or `NULL_TREE' ! to apply the front end's normal conversion rules. This hook is ! useful when there are target-specific types with special ! conversion rules. This is currently used only by the C and C++ ! front ends. -- Macro: TARGET_USE_JCR_SECTION This macro determines whether to use the JCR section to register ! Java classes. By default, TARGET_USE_JCR_SECTION is defined to 1 ! if both SUPPORTS_WEAK and TARGET_HAVE_NAMED_SECTIONS are true, ! else 0. -- Macro: OBJC_JBLEN This macro determines the size of the objective C jump buffer for ! the NeXT runtime. By default, OBJC_JBLEN is defined to an innocuous value. -- Macro: LIBGCC2_UNWIND_ATTRIBUTE Define this macro if any target-specific attributes need to be ! attached to the functions in `libgcc' that provide low-level support for call stack unwinding. It is used in declarations in ! `unwind-generic.h' and the associated definitions of those functions. -- Target Hook: void TARGET_UPDATE_STACK_BOUNDARY (void) *************** Here are several miscellaneous parameter *** 38663,38679 **** necessary. -- Target Hook: rtx TARGET_GET_DRAP_RTX (void) ! This hook should return an rtx for Dynamic Realign Argument Pointer ! (DRAP) if a different argument pointer register is needed to access ! the function's argument list due to stack realignment. Return ! 'NULL' if no DRAP is needed. -- Target Hook: bool TARGET_ALLOCATE_STACK_SLOTS_FOR_ARGS (void) When optimization is disabled, this hook indicates whether or not arguments should be allocated to stack slots. Normally, GCC allocates stacks slots for arguments when not optimizing in order to make debugging easier. However, when a function is declared ! with '__attribute__((naked))', there is no stack frame, and the compiler cannot safely move arguments from the registers in which they are passed to the stack. Therefore, this hook should return true in general, but false for naked functions. The default --- 39108,39124 ---- necessary. -- Target Hook: rtx TARGET_GET_DRAP_RTX (void) ! This hook should return an rtx for Dynamic Realign Argument ! Pointer (DRAP) if a different argument pointer register is needed ! to access the function's argument list due to stack realignment. ! Return `NULL' if no DRAP is needed. -- Target Hook: bool TARGET_ALLOCATE_STACK_SLOTS_FOR_ARGS (void) When optimization is disabled, this hook indicates whether or not arguments should be allocated to stack slots. Normally, GCC allocates stacks slots for arguments when not optimizing in order to make debugging easier. However, when a function is declared ! with `__attribute__((naked))', there is no stack frame, and the compiler cannot safely move arguments from the registers in which they are passed to the stack. Therefore, this hook should return true in general, but false for naked functions. The default *************** Here are several miscellaneous parameter *** 38684,38700 **** synthesize a constant. If there is another constant already in a register that is close enough in value then it is preferable that the new constant is computed from this register using immediate ! addition or subtraction. We accomplish this through CSE. Besides ! the value of the constant we also add a lower and an upper constant ! anchor to the available expressions. These are then queried when ! encountering new constants. The anchors are computed by rounding ! the constant up and down to a multiple of the value of ! 'TARGET_CONST_ANCHOR'. 'TARGET_CONST_ANCHOR' should be the maximum ! positive value accepted by immediate-add plus one. We currently ! assume that the value of 'TARGET_CONST_ANCHOR' is a power of 2. ! For example, on MIPS, where add-immediate takes a 16-bit signed ! value, 'TARGET_CONST_ANCHOR' is set to '0x8000'. The default value ! is zero, which disables this optimization. -- Target Hook: unsigned HOST_WIDE_INT TARGET_ASAN_SHADOW_OFFSET (void) Return the offset bitwise ored into shifted address to get --- 39129,39145 ---- synthesize a constant. If there is another constant already in a register that is close enough in value then it is preferable that the new constant is computed from this register using immediate ! addition or subtraction. We accomplish this through CSE. Besides ! the value of the constant we also add a lower and an upper ! constant anchor to the available expressions. These are then ! queried when encountering new constants. The anchors are computed ! by rounding the constant up and down to a multiple of the value of ! `TARGET_CONST_ANCHOR'. `TARGET_CONST_ANCHOR' should be the ! maximum positive value accepted by immediate-add plus one. We ! currently assume that the value of `TARGET_CONST_ANCHOR' is a ! power of 2. For example, on MIPS, where add-immediate takes a ! 16-bit signed value, `TARGET_CONST_ANCHOR' is set to `0x8000'. ! The default value is zero, which disables this optimization. -- Target Hook: unsigned HOST_WIDE_INT TARGET_ASAN_SHADOW_OFFSET (void) Return the offset bitwise ored into shifted address to get *************** Here are several miscellaneous parameter *** 38703,38798 **** -- Target Hook: unsigned HOST_WIDE_INT TARGET_MEMMODEL_CHECK (unsigned HOST_WIDE_INT VAL) ! Validate target specific memory model mask bits. When NULL no target specific memory model bits are allowed. -- Target Hook: unsigned char TARGET_ATOMIC_TEST_AND_SET_TRUEVAL This value should be set if the result written by ! 'atomic_test_and_set' is not exactly 1, i.e. the 'bool' 'true'. -- Target Hook: bool TARGET_HAS_IFUNC_P (void) ! It returns true if the target supports GNU indirect functions. The ! support includes the assembler, linker and dynamic linker. The ! default value of this hook is based on target's libc. ! -- Target Hook: unsigned int TARGET_ATOMIC_ALIGN_FOR_MODE (machine_mode ! MODE) If defined, this function returns an appropriate alignment in bits for an atomic object of machine_mode MODE. If 0 is returned then the default alignment for the specified mode is used. ! -- Target Hook: void TARGET_ATOMIC_ASSIGN_EXPAND_FENV (tree *HOLD, tree ! *CLEAR, tree *UPDATE) ISO C11 requires atomic compound assignments that may raise floating-point exceptions to raise exceptions corresponding to the arithmetic operation whose result was successfully stored in a compare-and-exchange sequence. This requires code equivalent to ! calls to 'feholdexcept', 'feclearexcept' and 'feupdateenv' to be generated at appropriate points in the compare-and-exchange ! sequence. This hook should set '*HOLD' to an expression equivalent ! to the call to 'feholdexcept', '*CLEAR' to an expression equivalent ! to the call to 'feclearexcept' and '*UPDATE' to an expression ! equivalent to the call to 'feupdateenv'. The three expressions are ! 'NULL_TREE' on entry to the hook and may be left as 'NULL_TREE' if ! no code is required in a particular place. The default ! implementation leaves all three expressions as 'NULL_TREE'. The ! '__atomic_feraiseexcept' function from 'libatomic' may be of use as ! part of the code generated in '*UPDATE'. -- Target Hook: void TARGET_RECORD_OFFLOAD_SYMBOL (tree) Used when offloaded functions are seen in the compilation unit and ! no named sections are available. It is called once for each symbol ! that must be recorded in the offload function and variable table. -- Target Hook: char * TARGET_OFFLOAD_OPTIONS (void) Used when writing out the list of options into an LTO file. It should translate any relevant target-specific options (such as the ! ABI in use) into one of the '-foffload' options that exist as a common interface to express such options. It should return a string containing these options, separated by spaces, which the caller will free. - -- Macro: TARGET_SUPPORTS_WIDE_INT ! On older ports, large integers are stored in 'CONST_DOUBLE' rtl ! objects. Newer ports define 'TARGET_SUPPORTS_WIDE_INT' to be nonzero to indicate that large integers are stored in ! 'CONST_WIDE_INT' rtl objects. The 'CONST_WIDE_INT' allows very ! large integer constants to be represented. 'CONST_DOUBLE' is ! limited to twice the size of the host's 'HOST_WIDE_INT' representation. Converting a port mostly requires looking for the places where ! 'CONST_DOUBLE's are used with 'VOIDmode' and replacing that code ! with code that accesses 'CONST_WIDE_INT's. '"grep -i const_double"' at the port level gets you to 95% of the changes ! that need to be made. There are a few places that require a deeper ! look. ! * There is no equivalent to 'hval' and 'lval' for ! 'CONST_WIDE_INT's. This would be difficult to express in the md language since there are a variable number of elements. ! Most ports only check that 'hval' is either 0 or -1 to see if the value is small. As mentioned above, this will no longer ! be necessary since small constants are always 'CONST_INT'. Of ! course there are still a few exceptions, the alpha's constraint used by the zap instruction certainly requires careful examination by C code. However, all the current code does is pass the hval and lval to C code, so evolving the c ! code to look at the 'CONST_WIDE_INT' is not really a large change. * Because there is no standard template that ports use to ! materialize constants, there is likely to be some futzing that ! is unique to each port in this code. * The rtx costs may have to be adjusted to properly account for ! larger constants that are represented as 'CONST_WIDE_INT'. All and all it does not take long to convert ports that the maintainer is familiar with.  File: gccint.info, Node: Host Config, Next: Fragments, Prev: Target Macros, Up: Top --- 39148,39246 ---- -- Target Hook: unsigned HOST_WIDE_INT TARGET_MEMMODEL_CHECK (unsigned HOST_WIDE_INT VAL) ! Validate target specific memory model mask bits. When NULL no target specific memory model bits are allowed. -- Target Hook: unsigned char TARGET_ATOMIC_TEST_AND_SET_TRUEVAL This value should be set if the result written by ! `atomic_test_and_set' is not exactly 1, i.e. the `bool' `true'. -- Target Hook: bool TARGET_HAS_IFUNC_P (void) ! It returns true if the target supports GNU indirect functions. ! The support includes the assembler, linker and dynamic linker. ! The default value of this hook is based on target's libc. ! -- Target Hook: unsigned int TARGET_ATOMIC_ALIGN_FOR_MODE ! (machine_mode MODE) If defined, this function returns an appropriate alignment in bits for an atomic object of machine_mode MODE. If 0 is returned then the default alignment for the specified mode is used. ! -- Target Hook: void TARGET_ATOMIC_ASSIGN_EXPAND_FENV (tree *HOLD, ! tree *CLEAR, tree *UPDATE) ISO C11 requires atomic compound assignments that may raise floating-point exceptions to raise exceptions corresponding to the arithmetic operation whose result was successfully stored in a compare-and-exchange sequence. This requires code equivalent to ! calls to `feholdexcept', `feclearexcept' and `feupdateenv' to be generated at appropriate points in the compare-and-exchange ! sequence. This hook should set `*HOLD' to an expression ! equivalent to the call to `feholdexcept', `*CLEAR' to an ! expression equivalent to the call to `feclearexcept' and `*UPDATE' ! to an expression equivalent to the call to `feupdateenv'. The ! three expressions are `NULL_TREE' on entry to the hook and may be ! left as `NULL_TREE' if no code is required in a particular place. ! The default implementation leaves all three expressions as ! `NULL_TREE'. The `__atomic_feraiseexcept' function from ! `libatomic' may be of use as part of the code generated in ! `*UPDATE'. -- Target Hook: void TARGET_RECORD_OFFLOAD_SYMBOL (tree) Used when offloaded functions are seen in the compilation unit and ! no named sections are available. It is called once for each ! symbol that must be recorded in the offload function and variable ! table. -- Target Hook: char * TARGET_OFFLOAD_OPTIONS (void) Used when writing out the list of options into an LTO file. It should translate any relevant target-specific options (such as the ! ABI in use) into one of the `-foffload' options that exist as a common interface to express such options. It should return a string containing these options, separated by spaces, which the caller will free. ! -- Macro: TARGET_SUPPORTS_WIDE_INT ! On older ports, large integers are stored in `CONST_DOUBLE' rtl ! objects. Newer ports define `TARGET_SUPPORTS_WIDE_INT' to be nonzero to indicate that large integers are stored in ! `CONST_WIDE_INT' rtl objects. The `CONST_WIDE_INT' allows very ! large integer constants to be represented. `CONST_DOUBLE' is ! limited to twice the size of the host's `HOST_WIDE_INT' representation. Converting a port mostly requires looking for the places where ! `CONST_DOUBLE's are used with `VOIDmode' and replacing that code ! with code that accesses `CONST_WIDE_INT's. `"grep -i const_double"' at the port level gets you to 95% of the changes ! that need to be made. There are a few places that require a ! deeper look. ! * There is no equivalent to `hval' and `lval' for ! `CONST_WIDE_INT's. This would be difficult to express in the md language since there are a variable number of elements. ! Most ports only check that `hval' is either 0 or -1 to see if the value is small. As mentioned above, this will no longer ! be necessary since small constants are always `CONST_INT'. ! Of course there are still a few exceptions, the alpha's constraint used by the zap instruction certainly requires careful examination by C code. However, all the current code does is pass the hval and lval to C code, so evolving the c ! code to look at the `CONST_WIDE_INT' is not really a large change. * Because there is no standard template that ports use to ! materialize constants, there is likely to be some futzing ! that is unique to each port in this code. * The rtx costs may have to be adjusted to properly account for ! larger constants that are represented as `CONST_WIDE_INT'. All and all it does not take long to convert ports that the maintainer is familiar with. +  File: gccint.info, Node: Host Config, Next: Fragments, Prev: Target Macros, Up: Top *************** File: gccint.info, Node: Host Config, *** 38800,38822 **** ********************* Most details about the machine and system on which the compiler is ! actually running are detected by the 'configure' script. Some things ! are impossible for 'configure' to detect; these are described in two ! ways, either by macros defined in a file named 'xm-MACHINE.h' or by hook ! functions in the file specified by the OUT_HOST_HOOK_OBJ variable in ! 'config.gcc'. (The intention is that very few hosts will need a header ! file but nearly every fully supported host will need to override some ! hooks.) If you need to define only a few macros, and they have simple ! definitions, consider using the 'xm_defines' variable in your ! 'config.gcc' entry instead of creating a host configuration header. *Note System Config::. * Menu: * Host Common:: Things every host probably needs implemented. ! * Filesystem:: Your host can't have the letter 'a' in filenames? * Host Misc:: Rare configuration options for hosts.  --- 39248,39270 ---- ********************* Most details about the machine and system on which the compiler is ! actually running are detected by the `configure' script. Some things ! are impossible for `configure' to detect; these are described in two ! ways, either by macros defined in a file named `xm-MACHINE.h' or by ! hook functions in the file specified by the OUT_HOST_HOOK_OBJ variable ! in `config.gcc'. (The intention is that very few hosts will need a ! header file but nearly every fully supported host will need to override ! some hooks.) If you need to define only a few macros, and they have simple ! definitions, consider using the `xm_defines' variable in your ! `config.gcc' entry instead of creating a host configuration header. *Note System Config::. * Menu: * Host Common:: Things every host probably needs implemented. ! * Filesystem:: Your host can't have the letter `a' in filenames? * Host Misc:: Rare configuration options for hosts.  *************** File: gccint.info, Node: Host Common, *** 38828,38834 **** Some things are just not portable, even between similar operating systems, and are too difficult for autoconf to detect. They get implemented using hook functions in the file specified by the ! HOST_HOOK_OBJ variable in 'config.gcc'. -- Host Hook: void HOST_HOOKS_EXTRA_SIGNALS (void) This host hook is used to set up handling for extra signals. The --- 39276,39282 ---- Some things are just not portable, even between similar operating systems, and are too difficult for autoconf to detect. They get implemented using hook functions in the file specified by the ! HOST_HOOK_OBJ variable in `config.gcc'. -- Host Hook: void HOST_HOOKS_EXTRA_SIGNALS (void) This host hook is used to set up handling for extra signals. The *************** HOST_HOOK_OBJ variable in 'config.gcc'. *** 38838,38856 **** FD) This host hook returns the address of some space that is likely to be free in some subsequent invocation of the compiler. We intend ! to load the PCH data at this address such that the data need not be ! relocated. The area should be able to hold SIZE bytes. If the ! host uses 'mmap', FD is an open file descriptor that can be used for probing. ! -- Host Hook: int HOST_HOOKS_GT_PCH_USE_ADDRESS (void * ADDRESS, size_t ! SIZE, int FD, size_t OFFSET) ! This host hook is called when a PCH file is about to be loaded. We ! want to load SIZE bytes from FD at OFFSET into memory at ADDRESS. ! The given address will be the result of a previous invocation of ! 'HOST_HOOKS_GT_PCH_GET_ADDRESS'. Return -1 if we couldn't allocate ! SIZE bytes at ADDRESS. Return 0 if the memory is allocated but the ! data is not loaded. Return 1 if the hook has performed everything. If the implementation uses reserved address space, free any reserved space beyond SIZE, regardless of the return value. If no --- 39286,39305 ---- FD) This host hook returns the address of some space that is likely to be free in some subsequent invocation of the compiler. We intend ! to load the PCH data at this address such that the data need not ! be relocated. The area should be able to hold SIZE bytes. If the ! host uses `mmap', FD is an open file descriptor that can be used for probing. ! -- Host Hook: int HOST_HOOKS_GT_PCH_USE_ADDRESS (void * ADDRESS, ! size_t SIZE, int FD, size_t OFFSET) ! This host hook is called when a PCH file is about to be loaded. ! We want to load SIZE bytes from FD at OFFSET into memory at ! ADDRESS. The given address will be the result of a previous ! invocation of `HOST_HOOKS_GT_PCH_GET_ADDRESS'. Return -1 if we ! couldn't allocate SIZE bytes at ADDRESS. Return 0 if the memory ! is allocated but the data is not loaded. Return 1 if the hook has ! performed everything. If the implementation uses reserved address space, free any reserved space beyond SIZE, regardless of the return value. If no *************** File: gccint.info, Node: Filesystem, N *** 38876,38933 **** GCC needs to know a number of things about the semantics of the host machine's filesystem. Filesystems with Unix and MS-DOS semantics are ! automatically detected. For other systems, you can define the following ! macros in 'xm-MACHINE.h'. ! 'HAVE_DOS_BASED_FILE_SYSTEM' ! This macro is automatically defined by 'system.h' if the host file system obeys the semantics defined by MS-DOS instead of Unix. DOS file systems are case insensitive, file specifications may begin ! with a drive letter, and both forward slash and backslash ('/' and ! '\') are directory separators. ! 'DIR_SEPARATOR' ! 'DIR_SEPARATOR_2' If defined, these macros expand to character constants specifying separators for directory names within a file specification. ! 'system.h' will automatically give them appropriate values on Unix and MS-DOS file systems. If your file system is neither of these, ! define one or both appropriately in 'xm-MACHINE.h'. However, operating systems like VMS, where constructing a pathname is more complicated than just stringing together directory names separated by a special character, should not define either of these macros. ! 'PATH_SEPARATOR' If defined, this macro should expand to a character constant specifying the separator for elements of search paths. The default ! value is a colon (':'). DOS-based systems usually, but not always, ! use semicolon (';'). ! 'VMS' Define this macro if the host system is VMS. ! 'HOST_OBJECT_SUFFIX' Define this macro to be a C string representing the suffix for object files on your host machine. If you do not define this ! macro, GCC will use '.o' as the suffix for object files. ! 'HOST_EXECUTABLE_SUFFIX' Define this macro to be a C string representing the suffix for executable files on your host machine. If you do not define this macro, GCC will use the null string as the suffix for executable files. ! 'HOST_BIT_BUCKET' A pathname defined by the host operating system, which can be ! opened as a file and written to, but all the information written is ! discarded. This is commonly known as a "bit bucket" or "null ! device". If you do not define this macro, GCC will use '/dev/null' ! as the bit bucket. If the host does not support a bit bucket, ! define this macro to an invalid filename. ! 'UPDATE_PATH_HOST_CANONICALIZE (PATH)' If defined, a C statement (sans semicolon) that performs host-dependent canonicalization when a path used in a compilation driver or preprocessor is canonicalized. PATH is a malloc-ed path --- 39325,39382 ---- GCC needs to know a number of things about the semantics of the host machine's filesystem. Filesystems with Unix and MS-DOS semantics are ! automatically detected. For other systems, you can define the ! following macros in `xm-MACHINE.h'. ! `HAVE_DOS_BASED_FILE_SYSTEM' ! This macro is automatically defined by `system.h' if the host file system obeys the semantics defined by MS-DOS instead of Unix. DOS file systems are case insensitive, file specifications may begin ! with a drive letter, and both forward slash and backslash (`/' and ! `\') are directory separators. ! `DIR_SEPARATOR' ! `DIR_SEPARATOR_2' If defined, these macros expand to character constants specifying separators for directory names within a file specification. ! `system.h' will automatically give them appropriate values on Unix and MS-DOS file systems. If your file system is neither of these, ! define one or both appropriately in `xm-MACHINE.h'. However, operating systems like VMS, where constructing a pathname is more complicated than just stringing together directory names separated by a special character, should not define either of these macros. ! `PATH_SEPARATOR' If defined, this macro should expand to a character constant specifying the separator for elements of search paths. The default ! value is a colon (`:'). DOS-based systems usually, but not ! always, use semicolon (`;'). ! `VMS' Define this macro if the host system is VMS. ! `HOST_OBJECT_SUFFIX' Define this macro to be a C string representing the suffix for object files on your host machine. If you do not define this ! macro, GCC will use `.o' as the suffix for object files. ! `HOST_EXECUTABLE_SUFFIX' Define this macro to be a C string representing the suffix for executable files on your host machine. If you do not define this macro, GCC will use the null string as the suffix for executable files. ! `HOST_BIT_BUCKET' A pathname defined by the host operating system, which can be ! opened as a file and written to, but all the information written ! is discarded. This is commonly known as a "bit bucket" or "null ! device". If you do not define this macro, GCC will use ! `/dev/null' as the bit bucket. If the host does not support a bit ! bucket, define this macro to an invalid filename. ! `UPDATE_PATH_HOST_CANONICALIZE (PATH)' If defined, a C statement (sans semicolon) that performs host-dependent canonicalization when a path used in a compilation driver or preprocessor is canonicalized. PATH is a malloc-ed path *************** macros in 'xm-MACHINE.h'. *** 38935,38953 **** into a different buffer, the old path should be freed and the new buffer should have been allocated with malloc. ! 'DUMPFILE_FORMAT' Define this macro to be a C string representing the format to use for constructing the index part of debugging dump file names. The ! resultant string must fit in fifteen bytes. The full filename will ! be the concatenation of: the prefix of the assembler file name, the ! string resulting from applying this format to an index number, and ! a string unique to each dump file kind, e.g. 'rtl'. ! If you do not define this macro, GCC will use '.%02d.'. You should define this macro if using the default will create an invalid file name. ! 'DELETE_IF_ORDINARY' Define this macro to be a C statement (sans semicolon) that performs host-dependent removal of ordinary temp files in the compilation driver. --- 39384,39402 ---- into a different buffer, the old path should be freed and the new buffer should have been allocated with malloc. ! `DUMPFILE_FORMAT' Define this macro to be a C string representing the format to use for constructing the index part of debugging dump file names. The ! resultant string must fit in fifteen bytes. The full filename ! will be the concatenation of: the prefix of the assembler file ! name, the string resulting from applying this format to an index ! number, and a string unique to each dump file kind, e.g. `rtl'. ! If you do not define this macro, GCC will use `.%02d.'. You should define this macro if using the default will create an invalid file name. ! `DELETE_IF_ORDINARY' Define this macro to be a C statement (sans semicolon) that performs host-dependent removal of ordinary temp files in the compilation driver. *************** macros in 'xm-MACHINE.h'. *** 38957,38965 **** reliably remove the temp file as, for example, on VMS which allows multiple versions of a file. ! 'HOST_LACKS_INODE_NUMBERS' ! Define this macro if the host filesystem does not report meaningful ! inode numbers in struct stat.  File: gccint.info, Node: Host Misc, Prev: Filesystem, Up: Host Config --- 39406,39414 ---- reliably remove the temp file as, for example, on VMS which allows multiple versions of a file. ! `HOST_LACKS_INODE_NUMBERS' ! Define this macro if the host filesystem does not report ! meaningful inode numbers in struct stat.  File: gccint.info, Node: Host Misc, Prev: Filesystem, Up: Host Config *************** File: gccint.info, Node: Host Misc, Pr *** 38967,39023 **** 18.3 Host Misc ============== ! 'FATAL_EXIT_CODE' A C expression for the status code to be returned when the compiler exits after serious errors. The default is the system-provided ! macro 'EXIT_FAILURE', or '1' if the system doesn't define that macro. Define this macro only if these defaults are incorrect. ! 'SUCCESS_EXIT_CODE' A C expression for the status code to be returned when the compiler exits without serious errors. (Warnings are not serious errors.) ! The default is the system-provided macro 'EXIT_SUCCESS', or '0' if the system doesn't define that macro. Define this macro only if these defaults are incorrect. ! 'USE_C_ALLOCA' Define this macro if GCC should use the C implementation of ! 'alloca' provided by 'libiberty.a'. This only affects how some parts of the compiler itself allocate memory. It does not change code generation. ! When GCC is built with a compiler other than itself, the C 'alloca' is always used. This is because most other implementations have serious bugs. You should define this macro only on a system where ! no stack-based 'alloca' can possibly work. For instance, if a system has a small limit on the size of the stack, GCC's builtin ! 'alloca' will not work reliably. ! 'COLLECT2_HOST_INITIALIZATION' If defined, a C statement (sans semicolon) that performs ! host-dependent initialization when 'collect2' is being initialized. ! 'GCC_DRIVER_HOST_INITIALIZATION' If defined, a C statement (sans semicolon) that performs host-dependent initialization when a compilation driver is being initialized. ! 'HOST_LONG_LONG_FORMAT' ! If defined, the string used to indicate an argument of type 'long ! long' to functions like 'printf'. The default value is '"ll"'. ! 'HOST_LONG_FORMAT' ! If defined, the string used to indicate an argument of type 'long' ! to functions like 'printf'. The default value is '"l"'. ! 'HOST_PTR_PRINTF' ! If defined, the string used to indicate an argument of type 'void ! *' to functions like 'printf'. The default value is '"%p"'. ! In addition, if 'configure' generates an incorrect definition of any of ! the macros in 'auto-host.h', you can override that definition in a host ! configuration header. If you need to do this, first see if it is ! possible to fix 'configure'.  File: gccint.info, Node: Fragments, Next: Collect2, Prev: Host Config, Up: Top --- 39416,39472 ---- 18.3 Host Misc ============== ! `FATAL_EXIT_CODE' A C expression for the status code to be returned when the compiler exits after serious errors. The default is the system-provided ! macro `EXIT_FAILURE', or `1' if the system doesn't define that macro. Define this macro only if these defaults are incorrect. ! `SUCCESS_EXIT_CODE' A C expression for the status code to be returned when the compiler exits without serious errors. (Warnings are not serious errors.) ! The default is the system-provided macro `EXIT_SUCCESS', or `0' if the system doesn't define that macro. Define this macro only if these defaults are incorrect. ! `USE_C_ALLOCA' Define this macro if GCC should use the C implementation of ! `alloca' provided by `libiberty.a'. This only affects how some parts of the compiler itself allocate memory. It does not change code generation. ! When GCC is built with a compiler other than itself, the C `alloca' is always used. This is because most other implementations have serious bugs. You should define this macro only on a system where ! no stack-based `alloca' can possibly work. For instance, if a system has a small limit on the size of the stack, GCC's builtin ! `alloca' will not work reliably. ! `COLLECT2_HOST_INITIALIZATION' If defined, a C statement (sans semicolon) that performs ! host-dependent initialization when `collect2' is being initialized. ! `GCC_DRIVER_HOST_INITIALIZATION' If defined, a C statement (sans semicolon) that performs host-dependent initialization when a compilation driver is being initialized. ! `HOST_LONG_LONG_FORMAT' ! If defined, the string used to indicate an argument of type `long ! long' to functions like `printf'. The default value is `"ll"'. ! `HOST_LONG_FORMAT' ! If defined, the string used to indicate an argument of type `long' ! to functions like `printf'. The default value is `"l"'. ! `HOST_PTR_PRINTF' ! If defined, the string used to indicate an argument of type `void ! *' to functions like `printf'. The default value is `"%p"'. ! In addition, if `configure' generates an incorrect definition of any ! of the macros in `auto-host.h', you can override that definition in a ! host configuration header. If you need to do this, first see if it is ! possible to fix `configure'.  File: gccint.info, Node: Fragments, Next: Collect2, Prev: Host Config, Up: Top *************** File: gccint.info, Node: Fragments, Ne *** 39025,39052 **** 19 Makefile Fragments ********************* ! When you configure GCC using the 'configure' script, it will construct ! the file 'Makefile' from the template file 'Makefile.in'. When it does ! this, it can incorporate makefile fragments from the 'config' directory. ! These are used to set Makefile parameters that are not amenable to being ! calculated by autoconf. The list of fragments to incorporate is set by ! 'config.gcc' (and occasionally 'config.build' and 'config.host'); *Note ! System Config::. ! Fragments are named either 't-TARGET' or 'x-HOST', depending on whether ! they are relevant to configuring GCC to produce code for a particular ! target, or to configuring GCC to run on a particular host. Here TARGET ! and HOST are mnemonics which usually have some relationship to the ! canonical system name, but no formal connection. If these files do not exist, it means nothing needs to be added for a ! given target or host. Most targets need a few 't-TARGET' fragments, but ! needing 'x-HOST' fragments is rare. * Menu: ! * Target Fragment:: Writing 't-TARGET' files. ! * Host Fragment:: Writing 'x-HOST' files.  File: gccint.info, Node: Target Fragment, Next: Host Fragment, Up: Fragments --- 39474,39501 ---- 19 Makefile Fragments ********************* ! When you configure GCC using the `configure' script, it will construct ! the file `Makefile' from the template file `Makefile.in'. When it does ! this, it can incorporate makefile fragments from the `config' ! directory. These are used to set Makefile parameters that are not ! amenable to being calculated by autoconf. The list of fragments to ! incorporate is set by `config.gcc' (and occasionally `config.build' and ! `config.host'); *Note System Config::. ! Fragments are named either `t-TARGET' or `x-HOST', depending on ! whether they are relevant to configuring GCC to produce code for a ! particular target, or to configuring GCC to run on a particular host. ! Here TARGET and HOST are mnemonics which usually have some relationship ! to the canonical system name, but no formal connection. If these files do not exist, it means nothing needs to be added for a ! given target or host. Most targets need a few `t-TARGET' fragments, ! but needing `x-HOST' fragments is rare. * Menu: ! * Target Fragment:: Writing `t-TARGET' files. ! * Host Fragment:: Writing `x-HOST' files.  File: gccint.info, Node: Target Fragment, Next: Host Fragment, Up: Fragments *************** File: gccint.info, Node: Target Fragmen *** 39056,39224 **** Target makefile fragments can set these Makefile variables. ! 'LIBGCC2_CFLAGS' ! Compiler flags to use when compiling 'libgcc2.c'. ! 'LIB2FUNCS_EXTRA' A list of source file names to be compiled or assembled and ! inserted into 'libgcc.a'. ! 'CRTSTUFF_T_CFLAGS' ! Special flags used when compiling 'crtstuff.c'. *Note Initialization::. ! 'CRTSTUFF_T_CFLAGS_S' ! Special flags used when compiling 'crtstuff.c' for shared linking. ! Used if you use 'crtbeginS.o' and 'crtendS.o' in 'EXTRA-PARTS'. *Note Initialization::. ! 'MULTILIB_OPTIONS' For some targets, invoking GCC in different ways produces objects that can not be linked together. For example, for some targets GCC produces both big and little endian code. For these targets, you ! must arrange for multiple versions of 'libgcc.a' to be compiled, one for each set of incompatible options. When GCC invokes the ! linker, it arranges to link in the right version of 'libgcc.a', based on the command line options used. ! The 'MULTILIB_OPTIONS' macro lists the set of options for which ! special versions of 'libgcc.a' must be built. Write options that are mutually incompatible side by side, separated by a slash. Write options that may be used together separated by a space. The build procedure will build all combinations of compatible options. ! For example, if you set 'MULTILIB_OPTIONS' to 'm68000/m68020 ! msoft-float', 'Makefile' will build special versions of 'libgcc.a' ! using the following sets of options: '-m68000', '-m68020', ! '-msoft-float', '-m68000 -msoft-float', and '-m68020 -msoft-float'. ! 'MULTILIB_DIRNAMES' ! If 'MULTILIB_OPTIONS' is used, this variable specifies the directory names that should be used to hold the various libraries. ! Write one element in 'MULTILIB_DIRNAMES' for each element in ! 'MULTILIB_OPTIONS'. If 'MULTILIB_DIRNAMES' is not used, the ! default value will be 'MULTILIB_OPTIONS', with all slashes treated as spaces. ! 'MULTILIB_DIRNAMES' describes the multilib directories using GCC conventions and is applied to directories that are part of the GCC installation. When multilib-enabled, the compiler will add a subdirectory of the form PREFIX/MULTILIB before each directory in the search path for libraries and crt files. ! For example, if 'MULTILIB_OPTIONS' is set to 'm68000/m68020 ! msoft-float', then the default value of 'MULTILIB_DIRNAMES' is ! 'm68000 m68020 msoft-float'. You may specify a different value if you desire a different set of directory names. ! 'MULTILIB_MATCHES' ! Sometimes the same option may be written in two different ways. If ! an option is listed in 'MULTILIB_OPTIONS', GCC needs to know about ! any synonyms. In that case, set 'MULTILIB_MATCHES' to a list of ! items of the form 'option=option' to describe all relevant ! synonyms. For example, 'm68000=mc68000 m68020=mc68020'. ! 'MULTILIB_EXCEPTIONS' ! Sometimes when there are multiple sets of 'MULTILIB_OPTIONS' being specified, there are combinations that should not be built. In ! that case, set 'MULTILIB_EXCEPTIONS' to be all of the switch exceptions in shell case syntax that should not be built. For example the ARM processor cannot execute both hardware floating point instructions and the reduced size THUMB instructions at the same time, so there is no need to build libraries with both of ! these options enabled. Therefore 'MULTILIB_EXCEPTIONS' is set to: *mthumb/*mhard-float* ! 'MULTILIB_REQUIRED' Sometimes when there are only a few combinations are required, it ! would be a big effort to come up with a 'MULTILIB_EXCEPTIONS' list to cover all undesired ones. In such a case, just listing all the ! required combinations in 'MULTILIB_REQUIRED' would be more straightforward. ! The way to specify the entries in 'MULTILIB_REQUIRED' is same with ! the way used for 'MULTILIB_EXCEPTIONS', only this time what are required will be specified. Suppose there are multiple sets of ! 'MULTILIB_OPTIONS' and only two combinations are required, one for ARMv7-M and one for ARMv7-R with hard floating-point ABI and FPU, ! the 'MULTILIB_REQUIRED' can be set to: ! MULTILIB_REQUIRED = mthumb/march=armv7-m ! MULTILIB_REQUIRED += march=armv7-r/mfloat-abi=hard/mfpu=vfpv3-d16 ! The 'MULTILIB_REQUIRED' can be used together with ! 'MULTILIB_EXCEPTIONS'. The option combinations generated from ! 'MULTILIB_OPTIONS' will be filtered by 'MULTILIB_EXCEPTIONS' and ! then by 'MULTILIB_REQUIRED'. ! 'MULTILIB_REUSE' Sometimes it is desirable to reuse one existing multilib for different sets of options. Such kind of reuse can minimize the number of multilib variants. And for some targets it is better to reuse an existing multilib than to fall back to default multilib when there is no corresponding multilib. This can be done by ! adding reuse rules to 'MULTILIB_REUSE'. A reuse rule is comprised of two parts connected by equality sign. The left part is option set used to build multilib and the right part is option set that will reuse this multilib. The order of options in the left part matters and should be same with those ! specified in 'MULTILIB_REQUIRED' or aligned with order in ! 'MULTILIB_OPTIONS'. There is no such limitation for options in right part as we don't build multilib from them. But the equality sign in both parts should be replaced with period. ! The 'MULTILIB_REUSE' is different from 'MULTILIB_MATCHES' in that it sets up relations between two option sets rather than two options. Here is an example to demo how we reuse libraries built in Thumb mode for applications built in ARM mode: ! MULTILIB_REUSE = mthumb/march.armv7-r=marm/march.armv7-r ! Before the advent of 'MULTILIB_REUSE', GCC select multilib by ! comparing command line options with options used to build multilib. ! The 'MULTILIB_REUSE' is complementary to that way. Only when the ! original comparison matches nothing it will work to see if it is OK ! to reuse some existing multilib. ! 'MULTILIB_EXTRA_OPTS' Sometimes it is desirable that when building multiple versions of ! 'libgcc.a' certain options should always be passed on to the ! compiler. In that case, set 'MULTILIB_EXTRA_OPTS' to be the list of options to be used for all builds. If you set this, you should ! probably set 'CRTSTUFF_T_CFLAGS' to a dash followed by it. ! 'MULTILIB_OSDIRNAMES' ! If 'MULTILIB_OPTIONS' is used, this variable specifies a list of subdirectory names, that are used to modify the search path ! depending on the chosen multilib. Unlike 'MULTILIB_DIRNAMES', ! 'MULTILIB_OSDIRNAMES' describes the multilib directories using operating systems conventions, and is applied to the directories ! such as 'lib' or those in the 'LIBRARY_PATH' environment variable. ! The format is either the same as of 'MULTILIB_DIRNAMES', or a set ! of mappings. When it is the same as 'MULTILIB_DIRNAMES', it describes the multilib directories using operating system conventions, rather than GCC conventions. When it is a set of mappings of the form GCCDIR=OSDIR, the left side gives the GCC convention and the right gives the equivalent OS defined location. ! If the OSDIR part begins with a '!', GCC will not search in the non-multilib directory and use exclusively the multilib directory. Otherwise, the compiler will examine the search path for libraries and crt files twice; the first time it will add MULTILIB to each directory in the search path, the second it will not. For configurations that support both multilib and multiarch, ! 'MULTILIB_OSDIRNAMES' also encodes the multiarch name, thus ! subsuming 'MULTIARCH_DIRNAME'. The multiarch name is appended to each directory name, separated by a colon (e.g. ! '../lib32:i386-linux-gnu'). Each multiarch subdirectory will be searched before the corresponding OS multilib directory, for example ! '/lib/i386-linux-gnu' before '/lib/../lib32'. The multiarch name will also be used to modify the system header search path, as ! explained for 'MULTIARCH_DIRNAME'. ! 'MULTIARCH_DIRNAME' This variable specifies the multiarch name for configurations that are multiarch-enabled but not multilibbed configurations. --- 39505,39673 ---- Target makefile fragments can set these Makefile variables. ! `LIBGCC2_CFLAGS' ! Compiler flags to use when compiling `libgcc2.c'. ! `LIB2FUNCS_EXTRA' A list of source file names to be compiled or assembled and ! inserted into `libgcc.a'. ! `CRTSTUFF_T_CFLAGS' ! Special flags used when compiling `crtstuff.c'. *Note Initialization::. ! `CRTSTUFF_T_CFLAGS_S' ! Special flags used when compiling `crtstuff.c' for shared linking. ! Used if you use `crtbeginS.o' and `crtendS.o' in `EXTRA-PARTS'. *Note Initialization::. ! `MULTILIB_OPTIONS' For some targets, invoking GCC in different ways produces objects that can not be linked together. For example, for some targets GCC produces both big and little endian code. For these targets, you ! must arrange for multiple versions of `libgcc.a' to be compiled, one for each set of incompatible options. When GCC invokes the ! linker, it arranges to link in the right version of `libgcc.a', based on the command line options used. ! The `MULTILIB_OPTIONS' macro lists the set of options for which ! special versions of `libgcc.a' must be built. Write options that are mutually incompatible side by side, separated by a slash. Write options that may be used together separated by a space. The build procedure will build all combinations of compatible options. ! For example, if you set `MULTILIB_OPTIONS' to `m68000/m68020 ! msoft-float', `Makefile' will build special versions of `libgcc.a' ! using the following sets of options: `-m68000', `-m68020', ! `-msoft-float', `-m68000 -msoft-float', and `-m68020 -msoft-float'. ! `MULTILIB_DIRNAMES' ! If `MULTILIB_OPTIONS' is used, this variable specifies the directory names that should be used to hold the various libraries. ! Write one element in `MULTILIB_DIRNAMES' for each element in ! `MULTILIB_OPTIONS'. If `MULTILIB_DIRNAMES' is not used, the ! default value will be `MULTILIB_OPTIONS', with all slashes treated as spaces. ! `MULTILIB_DIRNAMES' describes the multilib directories using GCC conventions and is applied to directories that are part of the GCC installation. When multilib-enabled, the compiler will add a subdirectory of the form PREFIX/MULTILIB before each directory in the search path for libraries and crt files. ! For example, if `MULTILIB_OPTIONS' is set to `m68000/m68020 ! msoft-float', then the default value of `MULTILIB_DIRNAMES' is ! `m68000 m68020 msoft-float'. You may specify a different value if you desire a different set of directory names. ! `MULTILIB_MATCHES' ! Sometimes the same option may be written in two different ways. ! If an option is listed in `MULTILIB_OPTIONS', GCC needs to know ! about any synonyms. In that case, set `MULTILIB_MATCHES' to a ! list of items of the form `option=option' to describe all relevant ! synonyms. For example, `m68000=mc68000 m68020=mc68020'. ! `MULTILIB_EXCEPTIONS' ! Sometimes when there are multiple sets of `MULTILIB_OPTIONS' being specified, there are combinations that should not be built. In ! that case, set `MULTILIB_EXCEPTIONS' to be all of the switch exceptions in shell case syntax that should not be built. For example the ARM processor cannot execute both hardware floating point instructions and the reduced size THUMB instructions at the same time, so there is no need to build libraries with both of ! these options enabled. Therefore `MULTILIB_EXCEPTIONS' is set to: *mthumb/*mhard-float* ! `MULTILIB_REQUIRED' Sometimes when there are only a few combinations are required, it ! would be a big effort to come up with a `MULTILIB_EXCEPTIONS' list to cover all undesired ones. In such a case, just listing all the ! required combinations in `MULTILIB_REQUIRED' would be more straightforward. ! The way to specify the entries in `MULTILIB_REQUIRED' is same with ! the way used for `MULTILIB_EXCEPTIONS', only this time what are required will be specified. Suppose there are multiple sets of ! `MULTILIB_OPTIONS' and only two combinations are required, one for ARMv7-M and one for ARMv7-R with hard floating-point ABI and FPU, ! the `MULTILIB_REQUIRED' can be set to: ! `MULTILIB_REQUIRED' = mthumb/march=armv7-m ! `MULTILIB_REQUIRED' += march=armv7-r/mfloat-abi=hard/mfpu=vfpv3-d16 ! The `MULTILIB_REQUIRED' can be used together with ! `MULTILIB_EXCEPTIONS'. The option combinations generated from ! `MULTILIB_OPTIONS' will be filtered by `MULTILIB_EXCEPTIONS' and ! then by `MULTILIB_REQUIRED'. ! `MULTILIB_REUSE' Sometimes it is desirable to reuse one existing multilib for different sets of options. Such kind of reuse can minimize the number of multilib variants. And for some targets it is better to reuse an existing multilib than to fall back to default multilib when there is no corresponding multilib. This can be done by ! adding reuse rules to `MULTILIB_REUSE'. A reuse rule is comprised of two parts connected by equality sign. The left part is option set used to build multilib and the right part is option set that will reuse this multilib. The order of options in the left part matters and should be same with those ! specified in `MULTILIB_REQUIRED' or aligned with order in ! `MULTILIB_OPTIONS'. There is no such limitation for options in right part as we don't build multilib from them. But the equality sign in both parts should be replaced with period. ! The `MULTILIB_REUSE' is different from `MULTILIB_MATCHES' in that it sets up relations between two option sets rather than two options. Here is an example to demo how we reuse libraries built in Thumb mode for applications built in ARM mode: ! `MULTILIB_REUSE' = mthumb/march.armv7-r=marm/march.armv7-r ! Before the advent of `MULTILIB_REUSE', GCC select multilib by ! comparing command line options with options used to build ! multilib. The `MULTILIB_REUSE' is complementary to that way. ! Only when the original comparison matches nothing it will work to ! see if it is OK to reuse some existing multilib. ! `MULTILIB_EXTRA_OPTS' Sometimes it is desirable that when building multiple versions of ! `libgcc.a' certain options should always be passed on to the ! compiler. In that case, set `MULTILIB_EXTRA_OPTS' to be the list of options to be used for all builds. If you set this, you should ! probably set `CRTSTUFF_T_CFLAGS' to a dash followed by it. ! `MULTILIB_OSDIRNAMES' ! If `MULTILIB_OPTIONS' is used, this variable specifies a list of subdirectory names, that are used to modify the search path ! depending on the chosen multilib. Unlike `MULTILIB_DIRNAMES', ! `MULTILIB_OSDIRNAMES' describes the multilib directories using operating systems conventions, and is applied to the directories ! such as `lib' or those in the `LIBRARY_PATH' environment variable. ! The format is either the same as of `MULTILIB_DIRNAMES', or a set ! of mappings. When it is the same as `MULTILIB_DIRNAMES', it describes the multilib directories using operating system conventions, rather than GCC conventions. When it is a set of mappings of the form GCCDIR=OSDIR, the left side gives the GCC convention and the right gives the equivalent OS defined location. ! If the OSDIR part begins with a `!', GCC will not search in the non-multilib directory and use exclusively the multilib directory. Otherwise, the compiler will examine the search path for libraries and crt files twice; the first time it will add MULTILIB to each directory in the search path, the second it will not. For configurations that support both multilib and multiarch, ! `MULTILIB_OSDIRNAMES' also encodes the multiarch name, thus ! subsuming `MULTIARCH_DIRNAME'. The multiarch name is appended to each directory name, separated by a colon (e.g. ! `../lib32:i386-linux-gnu'). Each multiarch subdirectory will be searched before the corresponding OS multilib directory, for example ! `/lib/i386-linux-gnu' before `/lib/../lib32'. The multiarch name will also be used to modify the system header search path, as ! explained for `MULTIARCH_DIRNAME'. ! `MULTIARCH_DIRNAME' This variable specifies the multiarch name for configurations that are multiarch-enabled but not multilibbed configurations. *************** Target makefile fragments can set these *** 39227,39260 **** locations. The compiler will add a multiarch subdirectory of the form PREFIX/MULTIARCH before each directory in the library and crt search path. It will also add two directories ! 'LOCAL_INCLUDE_DIR'/MULTIARCH and ! 'NATIVE_SYSTEM_HEADER_DIR'/MULTIARCH) to the system header search ! path, respectively before 'LOCAL_INCLUDE_DIR' and ! 'NATIVE_SYSTEM_HEADER_DIR'. ! 'MULTIARCH_DIRNAME' is not used for configurations that support both multilib and multiarch. In that case, multiarch names are ! encoded in 'MULTILIB_OSDIRNAMES' instead. More documentation about multiarch can be found at ! . ! 'SPECS' ! Unfortunately, setting 'MULTILIB_EXTRA_OPTS' is not enough, since it does not affect the build of target libraries, at least not the build of the default multilib. One possible work-around is to use ! 'DRIVER_SELF_SPECS' to bring options from the 'specs' file as if ! they had been passed in the compiler driver command line. However, ! you don't want to be adding these options after the toolchain is ! installed, so you can instead tweak the 'specs' file that will be ! used during the toolchain build, while you still install the ! original, built-in 'specs'. The trick is to set 'SPECS' to some ! other filename (say 'specs.install'), that will then be created out ! of the built-in specs, and introduce a 'Makefile' rule to generate ! the 'specs' file that's going to be used at build time out of your ! 'specs.install'. ! 'T_CFLAGS' These are extra flags to pass to the C compiler. They are used both when building GCC, and when compiling things with the just-built GCC. This variable is deprecated and should not be --- 39676,39709 ---- locations. The compiler will add a multiarch subdirectory of the form PREFIX/MULTIARCH before each directory in the library and crt search path. It will also add two directories ! `LOCAL_INCLUDE_DIR'/MULTIARCH and ! `NATIVE_SYSTEM_HEADER_DIR'/MULTIARCH) to the system header search ! path, respectively before `LOCAL_INCLUDE_DIR' and ! `NATIVE_SYSTEM_HEADER_DIR'. ! `MULTIARCH_DIRNAME' is not used for configurations that support both multilib and multiarch. In that case, multiarch names are ! encoded in `MULTILIB_OSDIRNAMES' instead. More documentation about multiarch can be found at ! `https://wiki.debian.org/Multiarch'. ! `SPECS' ! Unfortunately, setting `MULTILIB_EXTRA_OPTS' is not enough, since it does not affect the build of target libraries, at least not the build of the default multilib. One possible work-around is to use ! `DRIVER_SELF_SPECS' to bring options from the `specs' file as if ! they had been passed in the compiler driver command line. ! However, you don't want to be adding these options after the ! toolchain is installed, so you can instead tweak the `specs' file ! that will be used during the toolchain build, while you still ! install the original, built-in `specs'. The trick is to set ! `SPECS' to some other filename (say `specs.install'), that will ! then be created out of the built-in specs, and introduce a ! `Makefile' rule to generate the `specs' file that's going to be ! used at build time out of your `specs.install'. ! `T_CFLAGS' These are extra flags to pass to the C compiler. They are used both when building GCC, and when compiling things with the just-built GCC. This variable is deprecated and should not be *************** File: gccint.info, Node: Host Fragment, *** 39266,39344 **** 19.2 Host Makefile Fragments ============================ ! The use of 'x-HOST' fragments is discouraged. You should only use it for makefile dependencies.  File: gccint.info, Node: Collect2, Next: Header Dirs, Prev: Fragments, Up: Top ! 20 'collect2' ************* ! GCC uses a utility called 'collect2' on nearly all systems to arrange to ! call various initialization functions at start time. ! The program 'collect2' works by linking the program once and looking through the linker output file for symbols with particular names indicating they are constructor functions. If it finds any, it creates ! a new temporary '.c' file containing a table of them, compiles it, and links the program a second time including that file. The actual calls to the constructors are carried out by a subroutine ! called '__main', which is called (automatically) at the beginning of the ! body of 'main' (provided 'main' was compiled with GNU CC). Calling ! '__main' is necessary, even when compiling C code, to allow linking C ! and C++ object code together. (If you use '-nostdlib', you get an ! unresolved reference to '__main', since it's defined in the standard GCC ! library. Include '-lgcc' at the end of your compiler command line to ! resolve this reference.) ! The program 'collect2' is installed as 'ld' in the directory where the ! passes of the compiler are installed. When 'collect2' needs to find the ! _real_ 'ld', it tries the following file names: * a hard coded linker file name, if GCC was configured with the ! '--with-ld' option. ! * 'real-ld' in the directories listed in the compiler's search directories. ! * 'real-ld' in the directories listed in the environment variable ! 'PATH'. ! * The file specified in the 'REAL_LD_FILE_NAME' configuration macro, if specified. ! * 'ld' in the compiler's search directories, except that 'collect2' will not execute itself recursively. ! * 'ld' in 'PATH'. "The compiler's search directories" means all the directories where ! 'gcc' searches for passes of the compiler. This includes directories ! that you specify with '-B'. Cross-compilers search a little differently: ! * 'real-ld' in the compiler's search directories. ! * 'TARGET-real-ld' in 'PATH'. ! * The file specified in the 'REAL_LD_FILE_NAME' configuration macro, if specified. ! * 'ld' in the compiler's search directories. ! * 'TARGET-ld' in 'PATH'. ! 'collect2' explicitly avoids running 'ld' using the file name under ! which 'collect2' itself was invoked. In fact, it remembers up a list of ! such names--in case one copy of 'collect2' finds another copy (or ! version) of 'collect2' installed as 'ld' in a second place in the search ! path. ! 'collect2' searches for the utilities 'nm' and 'strip' using the same ! algorithm as above for 'ld'.  File: gccint.info, Node: Header Dirs, Next: Type Information, Prev: Collect2, Up: Top --- 39715,39793 ---- 19.2 Host Makefile Fragments ============================ ! The use of `x-HOST' fragments is discouraged. You should only use it for makefile dependencies.  File: gccint.info, Node: Collect2, Next: Header Dirs, Prev: Fragments, Up: Top ! 20 `collect2' ************* ! GCC uses a utility called `collect2' on nearly all systems to arrange ! to call various initialization functions at start time. ! The program `collect2' works by linking the program once and looking through the linker output file for symbols with particular names indicating they are constructor functions. If it finds any, it creates ! a new temporary `.c' file containing a table of them, compiles it, and links the program a second time including that file. The actual calls to the constructors are carried out by a subroutine ! called `__main', which is called (automatically) at the beginning of ! the body of `main' (provided `main' was compiled with GNU CC). Calling ! `__main' is necessary, even when compiling C code, to allow linking C ! and C++ object code together. (If you use `-nostdlib', you get an ! unresolved reference to `__main', since it's defined in the standard ! GCC library. Include `-lgcc' at the end of your compiler command line ! to resolve this reference.) ! The program `collect2' is installed as `ld' in the directory where the ! passes of the compiler are installed. When `collect2' needs to find ! the _real_ `ld', it tries the following file names: * a hard coded linker file name, if GCC was configured with the ! `--with-ld' option. ! * `real-ld' in the directories listed in the compiler's search directories. ! * `real-ld' in the directories listed in the environment variable ! `PATH'. ! * The file specified in the `REAL_LD_FILE_NAME' configuration macro, if specified. ! * `ld' in the compiler's search directories, except that `collect2' will not execute itself recursively. ! * `ld' in `PATH'. "The compiler's search directories" means all the directories where ! `gcc' searches for passes of the compiler. This includes directories ! that you specify with `-B'. Cross-compilers search a little differently: ! * `real-ld' in the compiler's search directories. ! * `TARGET-real-ld' in `PATH'. ! * The file specified in the `REAL_LD_FILE_NAME' configuration macro, if specified. ! * `ld' in the compiler's search directories. ! * `TARGET-ld' in `PATH'. ! `collect2' explicitly avoids running `ld' using the file name under ! which `collect2' itself was invoked. In fact, it remembers up a list ! of such names--in case one copy of `collect2' finds another copy (or ! version) of `collect2' installed as `ld' in a second place in the ! search path. ! `collect2' searches for the utilities `nm' and `strip' using the same ! algorithm as above for `ld'.  File: gccint.info, Node: Header Dirs, Next: Type Information, Prev: Collect2, Up: Top *************** File: gccint.info, Node: Header Dirs, *** 39346,39374 **** 21 Standard Header File Directories *********************************** ! 'GCC_INCLUDE_DIR' means the same thing for native and cross. It is where GCC stores its private include files, and also where GCC stores ! the fixed include files. A cross compiled GCC runs 'fixincludes' on the ! header files in '$(tooldir)/include'. (If the cross compilation header ! files need to be fixed, they must be installed before GCC is built. If ! the cross compilation header files are already suitable for GCC, nothing ! special need be done). ! 'GPLUSPLUS_INCLUDE_DIR' means the same thing for native and cross. It ! is where 'g++' looks first for header files. The C++ library installs only target independent header files in that directory. ! 'LOCAL_INCLUDE_DIR' is used only by native compilers. GCC doesn't ! install anything there. It is normally '/usr/local/include'. This is where local additions to a packaged system should place header files. ! 'CROSS_INCLUDE_DIR' is used only by cross compilers. GCC doesn't install anything there. ! 'TOOL_INCLUDE_DIR' is used for both native and cross compilers. It is the place for other packages to install header files that GCC will use. ! For a cross-compiler, this is the equivalent of '/usr/include'. When ! you build a cross-compiler, 'fixincludes' processes any header files in this directory.  --- 39795,39823 ---- 21 Standard Header File Directories *********************************** ! `GCC_INCLUDE_DIR' means the same thing for native and cross. It is where GCC stores its private include files, and also where GCC stores ! the fixed include files. A cross compiled GCC runs `fixincludes' on ! the header files in `$(tooldir)/include'. (If the cross compilation ! header files need to be fixed, they must be installed before GCC is ! built. If the cross compilation header files are already suitable for ! GCC, nothing special need be done). ! `GPLUSPLUS_INCLUDE_DIR' means the same thing for native and cross. It ! is where `g++' looks first for header files. The C++ library installs only target independent header files in that directory. ! `LOCAL_INCLUDE_DIR' is used only by native compilers. GCC doesn't ! install anything there. It is normally `/usr/local/include'. This is where local additions to a packaged system should place header files. ! `CROSS_INCLUDE_DIR' is used only by cross compilers. GCC doesn't install anything there. ! `TOOL_INCLUDE_DIR' is used for both native and cross compilers. It is the place for other packages to install header files that GCC will use. ! For a cross-compiler, this is the equivalent of `/usr/include'. When ! you build a cross-compiler, `fixincludes' processes any header files in this directory.  *************** implement precompiled headers. *** 39384,39407 **** A full C++ parser would be too complicated for this task, so a limited subset of C++ is interpreted and special markers are used to determine ! what parts of the source to look at. All 'struct', 'union' and ! 'template' structure declarations that define data structures that are allocated under control of the garbage collector must be marked. All global variables that hold pointers to garbage-collected memory must ! also be marked. Finally, all global variables that need to be saved and ! restored by a precompiled header must be marked. (The precompiled header mechanism can only save static variables if they're scalar. ! Complex data structures must be allocated in garbage-collected memory to ! be saved in a precompiled header.) The full format of a marker is GTY (([OPTION] [(PARAM)], [OPTION] [(PARAM)] ...)) ! but in most cases no options are needed. The outer double parentheses ! are still necessary, though: 'GTY(())'. Markers can appear: * In a structure definition, before the open brace; ! * In a global variable declaration, after the keyword 'static' or ! 'extern'; and * In a structure field definition, before the name of the field. Here are some examples of marking simple data structures and globals. --- 39833,39858 ---- A full C++ parser would be too complicated for this task, so a limited subset of C++ is interpreted and special markers are used to determine ! what parts of the source to look at. All `struct', `union' and ! `template' structure declarations that define data structures that are allocated under control of the garbage collector must be marked. All global variables that hold pointers to garbage-collected memory must ! also be marked. Finally, all global variables that need to be saved ! and restored by a precompiled header must be marked. (The precompiled header mechanism can only save static variables if they're scalar. ! Complex data structures must be allocated in garbage-collected memory ! to be saved in a precompiled header.) The full format of a marker is GTY (([OPTION] [(PARAM)], [OPTION] [(PARAM)] ...)) ! but in most cases no options are needed. The outer double parentheses ! are still necessary, though: `GTY(())'. Markers can appear: * In a structure definition, before the open brace; ! ! * In a global variable declaration, after the keyword `static' or ! `extern'; and ! * In a structure field definition, before the name of the field. Here are some examples of marking simple data structures and globals. *************** are still necessary, though: 'GTY(())'. *** 39419,39447 **** static GTY(()) struct TAG *LIST; /* points to GC memory */ static GTY(()) int COUNTER; /* save counter in a PCH */ ! The parser understands simple typedefs such as 'typedef struct TAG ! *NAME;' and 'typedef int NAME;'. These don't need to be marked. ! Since 'gengtype''s understanding of C++ is limited, there are several constructs and declarations that are not supported inside classes/structures marked for automatic GC code generation. The ! following C++ constructs produce a 'gengtype' error on structures/classes marked for automatic GC code generation: * Type definitions inside classes/structures are not supported. * Enumerations inside classes/structures are not supported. ! If you have a class or structure using any of the above constructs, you ! need to mark that class as 'GTY ((user))' and provide your own marking ! routines (see section *note User GC:: for details). It is always valid to include function definitions inside classes. ! Those are always ignored by 'gengtype', as it only cares about data members. * Menu: ! * GTY Options:: What goes inside a 'GTY(())'. * Inheritance and GTY:: Adding GTY to a class hierarchy. * User GC:: Adding user-provided GC marking routines. * GGC Roots:: Making global variables GGC roots. --- 39870,39899 ---- static GTY(()) struct TAG *LIST; /* points to GC memory */ static GTY(()) int COUNTER; /* save counter in a PCH */ ! The parser understands simple typedefs such as `typedef struct TAG ! *NAME;' and `typedef int NAME;'. These don't need to be marked. ! Since `gengtype''s understanding of C++ is limited, there are several constructs and declarations that are not supported inside classes/structures marked for automatic GC code generation. The ! following C++ constructs produce a `gengtype' error on structures/classes marked for automatic GC code generation: * Type definitions inside classes/structures are not supported. + * Enumerations inside classes/structures are not supported. ! If you have a class or structure using any of the above constructs, ! you need to mark that class as `GTY ((user))' and provide your own ! marking routines (see section *note User GC:: for details). It is always valid to include function definitions inside classes. ! Those are always ignored by `gengtype', as it only cares about data members. * Menu: ! * GTY Options:: What goes inside a `GTY(())'. * Inheritance and GTY:: Adding GTY to a class hierarchy. * User GC:: Adding user-provided GC marking routines. * GGC Roots:: Making global variables GGC roots. *************** members. *** 39452,39480 ****  File: gccint.info, Node: GTY Options, Next: Inheritance and GTY, Up: Type Information ! 22.1 The Inside of a 'GTY(())' ============================== ! Sometimes the C code is not enough to fully describe the type structure. ! Extra information can be provided with 'GTY' options and additional ! markers. Some options take a parameter, which may be either a string or ! a type name, depending on the parameter. If an option takes no ! parameter, it is acceptable either to omit the parameter entirely, or to ! provide an empty string as a parameter. For example, 'GTY ((skip))' and ! 'GTY ((skip ("")))' are equivalent. When the parameter is a string, often it is a fragment of C code. Four special escapes may be used in these strings, to refer to pieces of the data structure being marked: ! '%h' The current structure. ! '%1' The structure that immediately contains the current structure. ! '%0' The outermost structure that contains the current structure. ! '%a' ! A partial expression of the form '[i1][i2]...' that indexes the array item currently being marked. For instance, suppose that you have a structure of the form --- 39904,39935 ----  File: gccint.info, Node: GTY Options, Next: Inheritance and GTY, Up: Type Information ! 22.1 The Inside of a `GTY(())' ============================== ! Sometimes the C code is not enough to fully describe the type ! structure. Extra information can be provided with `GTY' options and ! additional markers. Some options take a parameter, which may be either ! a string or a type name, depending on the parameter. If an option ! takes no parameter, it is acceptable either to omit the parameter ! entirely, or to provide an empty string as a parameter. For example, ! `GTY ((skip))' and `GTY ((skip ("")))' are equivalent. When the parameter is a string, often it is a fragment of C code. Four special escapes may be used in these strings, to refer to pieces of the data structure being marked: ! `%h' The current structure. ! ! `%1' The structure that immediately contains the current structure. ! ! `%0' The outermost structure that contains the current structure. ! ! `%a' ! A partial expression of the form `[i1][i2]...' that indexes the array item currently being marked. For instance, suppose that you have a structure of the form *************** data structure being marked: *** 39484,39492 **** struct B { struct A foo[12]; }; ! and 'b' is a variable of type 'struct B'. When marking 'b.foo[11]', ! '%h' would expand to 'b.foo[11]', '%0' and '%1' would both expand to ! 'b', and '%a' would expand to '[11]'. As in ordinary C, adjacent strings will be concatenated; this is helpful when you have a complicated expression. --- 39939,39947 ---- struct B { struct A foo[12]; }; ! and `b' is a variable of type `struct B'. When marking `b.foo[11]', ! `%h' would expand to `b.foo[11]', `%0' and `%1' would both expand to ! `b', and `%a' would expand to `[11]'. As in ordinary C, adjacent strings will be concatenated; this is helpful when you have a complicated expression. *************** helpful when you have a complicated expr *** 39496,39503 **** The available options are: ! 'length ("EXPRESSION")' ! There are two places the type machinery will need to be explicitly told the length of an array of non-atomic objects. The first case is when a structure ends in a variable-length array, like this: --- 39951,39957 ---- The available options are: ! `length ("EXPRESSION")' There are two places the type machinery will need to be explicitly told the length of an array of non-atomic objects. The first case is when a structure ends in a variable-length array, like this: *************** helpful when you have a complicated expr *** 39506,39557 **** rtx GTY ((length ("%h.num_elem"))) elem[1]; }; ! In this case, the 'length' option is used to override the specified ! array length (which should usually be '1'). The parameter of the option is a fragment of C code that calculates the length. The second case is when a structure or a global variable contains a pointer to an array, like this: struct gimple_omp_for_iter * GTY((length ("%h.collapse"))) iter; ! In this case, 'iter' has been allocated by writing something like x->iter = ggc_alloc_cleared_vec_gimple_omp_for_iter (collapse); ! and the 'collapse' provides the length of the field. ! ! This second use of 'length' also works on global variables, like: ! static GTY((length("reg_known_value_size"))) rtx *reg_known_value; ! Note that the 'length' option is only meant for use with arrays of ! non-atomic objects, that is, objects that contain pointers pointing ! to other GTY-managed objects. For other GC-allocated arrays and ! strings you should use 'atomic'. ! 'skip' ! If 'skip' is applied to a field, the type machinery will ignore it. This is somewhat dangerous; the only safe use is in a union when one field really isn't ever used. Use this to mark types that need to be marked by user gc routines, ! but are not refered to in a template argument. So if you have some ! user gc type T1 and a non user gc type T2 you can give T2 the for_user option so that the marking functions for T1 can call non mangled functions to mark T2. ! 'desc ("EXPRESSION")' ! 'tag ("CONSTANT")' ! 'default' ! ! The type machinery needs to be told which field of a 'union' is currently active. This is done by giving each field a constant ! 'tag' value, and then specifying a discriminator using 'desc'. The ! value of the expression given by 'desc' is compared against each ! 'tag' value, each of which should be different. If no 'tag' is ! matched, the field marked with 'default' is used if there is one, ! otherwise no field in the union will be marked. ! In the 'desc' option, the "current structure" is the union that it ! discriminates. Use '%1' to mean the structure containing it. ! There are no escapes available to the 'tag' option, since it is a constant. For example, --- 39960,40008 ---- rtx GTY ((length ("%h.num_elem"))) elem[1]; }; ! In this case, the `length' option is used to override the specified ! array length (which should usually be `1'). The parameter of the option is a fragment of C code that calculates the length. The second case is when a structure or a global variable contains a pointer to an array, like this: struct gimple_omp_for_iter * GTY((length ("%h.collapse"))) iter; ! In this case, `iter' has been allocated by writing something like x->iter = ggc_alloc_cleared_vec_gimple_omp_for_iter (collapse); ! and the `collapse' provides the length of the field. ! This second use of `length' also works on global variables, like: static GTY((length("reg_known_value_size"))) rtx *reg_known_value; ! Note that the `length' option is only meant for use with arrays of ! non-atomic objects, that is, objects that contain pointers ! pointing to other GTY-managed objects. For other GC-allocated ! arrays and strings you should use `atomic'. ! `skip' ! If `skip' is applied to a field, the type machinery will ignore it. This is somewhat dangerous; the only safe use is in a union when one field really isn't ever used. Use this to mark types that need to be marked by user gc routines, ! but are not refered to in a template argument. So if you have ! some user gc type T1 and a non user gc type T2 you can give T2 the for_user option so that the marking functions for T1 can call non mangled functions to mark T2. ! `desc ("EXPRESSION")' ! `tag ("CONSTANT")' ! `default' ! The type machinery needs to be told which field of a `union' is currently active. This is done by giving each field a constant ! `tag' value, and then specifying a discriminator using `desc'. ! The value of the expression given by `desc' is compared against ! each `tag' value, each of which should be different. If no `tag' ! is matched, the field marked with `default' is used if there is ! one, otherwise no field in the union will be marked. ! In the `desc' option, the "current structure" is the union that it ! discriminates. Use `%1' to mean the structure containing it. ! There are no escapes available to the `tag' option, since it is a constant. For example, *************** helpful when you have a complicated expr *** 39566,39603 **** }; In this example, the value of BINDING_HAS_LEVEL_P when applied to a ! 'struct tree_binding *' is presumed to be 0 or 1. If 1, the type ! mechanism will treat the field 'level' as being present and if 0, ! will treat the field 'scope' as being present. ! The 'desc' and 'tag' options can also be used for inheritance to denote which subclass an instance is. See *note Inheritance and GTY:: for more information. ! 'cache' ! ! When the 'cache' option is applied to a global variable gt_clear_cache is called on that variable between the mark and ! sweep phases of garbage collection. The gt_clear_cache function is ! free to mark blocks as used, or to clear pointers in the variable. ! ! 'deletable' ! 'deletable', when applied to a global variable, indicates that when garbage collection runs, there's no need to mark anything pointed ! to by this variable, it can just be set to 'NULL' instead. This is ! used to keep a list of free structures around for re-use. ! ! 'maybe_undef' ! When applied to a field, 'maybe_undef' indicates that it's OK if the structure that this fields points to is never defined, so long ! as this field is always 'NULL'. This is used to avoid requiring backends to define certain optional structures. It doesn't work with language frontends. ! 'nested_ptr (TYPE, "TO EXPRESSION", "FROM EXPRESSION")' ! The type machinery expects all pointers to point to the start of an object. Sometimes for abstraction purposes it's convenient to have a pointer which points inside an object. So long as it's possible --- 40017,40051 ---- }; In this example, the value of BINDING_HAS_LEVEL_P when applied to a ! `struct tree_binding *' is presumed to be 0 or 1. If 1, the type ! mechanism will treat the field `level' as being present and if 0, ! will treat the field `scope' as being present. ! The `desc' and `tag' options can also be used for inheritance to denote which subclass an instance is. See *note Inheritance and GTY:: for more information. ! `cache' ! When the `cache' option is applied to a global variable gt_clear_cache is called on that variable between the mark and ! sweep phases of garbage collection. The gt_clear_cache function ! is free to mark blocks as used, or to clear pointers in the ! variable. ! `deletable' ! `deletable', when applied to a global variable, indicates that when garbage collection runs, there's no need to mark anything pointed ! to by this variable, it can just be set to `NULL' instead. This ! is used to keep a list of free structures around for re-use. ! `maybe_undef' ! When applied to a field, `maybe_undef' indicates that it's OK if the structure that this fields points to is never defined, so long ! as this field is always `NULL'. This is used to avoid requiring backends to define certain optional structures. It doesn't work with language frontends. ! `nested_ptr (TYPE, "TO EXPRESSION", "FROM EXPRESSION")' The type machinery expects all pointers to point to the start of an object. Sometimes for abstraction purposes it's convenient to have a pointer which points inside an object. So long as it's possible *************** helpful when you have a complicated expr *** 39605,39701 **** pointers can still be used. TYPE is the type of the original object, the TO EXPRESSION returns the pointer given the original object, and the FROM EXPRESSION returns the original object given ! the pointer. The pointer will be available using the '%h' escape. ! ! 'chain_next ("EXPRESSION")' ! 'chain_prev ("EXPRESSION")' ! 'chain_circular ("EXPRESSION")' It's helpful for the type machinery to know if objects are often chained together in long lists; this lets it generate code that uses less stack space by iterating along the list instead of ! recursing down it. 'chain_next' is an expression for the next item ! in the list, 'chain_prev' is an expression for the previous item. ! For singly linked lists, use only 'chain_next'; for doubly linked ! lists, use both. The machinery requires that taking the next item ! of the previous item gives the original item. 'chain_circular' is ! similar to 'chain_next', but can be used for circular single linked ! lists. ! ! 'reorder ("FUNCTION NAME")' Some data structures depend on the relative ordering of pointers. If the precompiled header machinery needs to change that ordering, ! it will call the function referenced by the 'reorder' option, ! before changing the pointers in the object that's pointed to by the ! field the option applies to. The function must take four arguments, with the signature ! 'void *, void *, gt_pointer_operator, void *'. The first parameter ! is a pointer to the structure that contains the object being ! updated, or the object itself if there is no containing structure. ! The second parameter is a cookie that should be ignored. The third ! parameter is a routine that, given a pointer, will update it to its ! correct new value. The fourth parameter is a cookie that must be ! passed to the second parameter. PCH cannot handle data structures that depend on the absolute ! values of pointers. 'reorder' functions can be expensive. When ! possible, it is better to depend on properties of the data, like an ! ID number or the hash of a string instead. ! ! 'atomic' ! The 'atomic' option can only be used with pointers. It informs the ! GC machinery that the memory that the pointer points to does not ! contain any pointers, and hence it should be treated by the GC and ! PCH machinery as an "atomic" block of memory that does not need to ! be examined when scanning memory for pointers. In particular, the ! machinery will not scan that memory for pointers to mark them as ! reachable (when marking pointers for GC) or to relocate them (when ! writing a PCH file). ! The 'atomic' option differs from the 'skip' option. 'atomic' keeps ! the memory under Garbage Collection, but makes the GC ignore the ! contents of the memory. 'skip' is more drastic in that it causes ! the pointer and the memory to be completely ignored by the Garbage ! Collector. So, memory marked as 'atomic' is automatically freed ! when no longer reachable, while memory marked as 'skip' is not. ! The 'atomic' option must be used with great care, because all sorts ! of problem can occur if used incorrectly, that is, if the memory ! the pointer points to does actually contain a pointer. Here is an example of how to use it: struct GTY(()) my_struct { int number_of_elements; unsigned int * GTY ((atomic)) elements; }; ! In this case, 'elements' is a pointer under GC, and the memory it points to needs to be allocated using the Garbage Collector, and will be freed automatically by the Garbage Collector when it is no ! longer referenced. But the memory that the pointer points to is an ! array of 'unsigned int' elements, and the GC must not try to scan ! it to find pointers to mark or relocate, which is why it is marked ! with the 'atomic' option. Note that, currently, global variables can not be marked with ! 'atomic'; only fields of a struct can. This is a known limitation. ! It would be useful to be able to mark global pointers with 'atomic' ! to make the PCH machinery aware of them so that they are saved and ! restored correctly to PCH files. ! ! 'special ("NAME")' ! The 'special' option is used to mark types that have to be dealt with by special case machinery. The parameter is the name of the ! special case. See 'gengtype.c' for further details. Avoid adding new special cases unless there is no other alternative. ! 'user' ! ! The 'user' option indicates that the code to mark structure fields ! is completely handled by user-provided routines. See section *note ! User GC:: for details on what functions need to be provided.  File: gccint.info, Node: Inheritance and GTY, Next: User GC, Prev: GTY Options, Up: Type Information --- 40053,40145 ---- pointers can still be used. TYPE is the type of the original object, the TO EXPRESSION returns the pointer given the original object, and the FROM EXPRESSION returns the original object given ! the pointer. The pointer will be available using the `%h' escape. + `chain_next ("EXPRESSION")' + `chain_prev ("EXPRESSION")' + `chain_circular ("EXPRESSION")' It's helpful for the type machinery to know if objects are often chained together in long lists; this lets it generate code that uses less stack space by iterating along the list instead of ! recursing down it. `chain_next' is an expression for the next ! item in the list, `chain_prev' is an expression for the previous ! item. For singly linked lists, use only `chain_next'; for doubly ! linked lists, use both. The machinery requires that taking the ! next item of the previous item gives the original item. ! `chain_circular' is similar to `chain_next', but can be used for ! circular single linked lists. + `reorder ("FUNCTION NAME")' Some data structures depend on the relative ordering of pointers. If the precompiled header machinery needs to change that ordering, ! it will call the function referenced by the `reorder' option, ! before changing the pointers in the object that's pointed to by ! the field the option applies to. The function must take four arguments, with the signature ! `void *, void *, gt_pointer_operator, void *'. The first ! parameter is a pointer to the structure that contains the object ! being updated, or the object itself if there is no containing ! structure. The second parameter is a cookie that should be ! ignored. The third parameter is a routine that, given a pointer, ! will update it to its correct new value. The fourth parameter is ! a cookie that must be passed to the second parameter. PCH cannot handle data structures that depend on the absolute ! values of pointers. `reorder' functions can be expensive. When ! possible, it is better to depend on properties of the data, like ! an ID number or the hash of a string instead. ! `atomic' ! The `atomic' option can only be used with pointers. It informs ! the GC machinery that the memory that the pointer points to does ! not contain any pointers, and hence it should be treated by the GC ! and PCH machinery as an "atomic" block of memory that does not ! need to be examined when scanning memory for pointers. In ! particular, the machinery will not scan that memory for pointers ! to mark them as reachable (when marking pointers for GC) or to ! relocate them (when writing a PCH file). ! The `atomic' option differs from the `skip' option. `atomic' ! keeps the memory under Garbage Collection, but makes the GC ignore ! the contents of the memory. `skip' is more drastic in that it ! causes the pointer and the memory to be completely ignored by the ! Garbage Collector. So, memory marked as `atomic' is automatically ! freed when no longer reachable, while memory marked as `skip' is ! not. ! The `atomic' option must be used with great care, because all ! sorts of problem can occur if used incorrectly, that is, if the ! memory the pointer points to does actually contain a pointer. Here is an example of how to use it: struct GTY(()) my_struct { int number_of_elements; unsigned int * GTY ((atomic)) elements; }; ! In this case, `elements' is a pointer under GC, and the memory it points to needs to be allocated using the Garbage Collector, and will be freed automatically by the Garbage Collector when it is no ! longer referenced. But the memory that the pointer points to is ! an array of `unsigned int' elements, and the GC must not try to ! scan it to find pointers to mark or relocate, which is why it is ! marked with the `atomic' option. Note that, currently, global variables can not be marked with ! `atomic'; only fields of a struct can. This is a known ! limitation. It would be useful to be able to mark global pointers ! with `atomic' to make the PCH machinery aware of them so that they ! are saved and restored correctly to PCH files. ! `special ("NAME")' ! The `special' option is used to mark types that have to be dealt with by special case machinery. The parameter is the name of the ! special case. See `gengtype.c' for further details. Avoid adding new special cases unless there is no other alternative. ! `user' ! The `user' option indicates that the code to mark structure fields ! is completely handled by user-provided routines. See section ! *note User GC:: for details on what functions need to be provided.  File: gccint.info, Node: Inheritance and GTY, Next: User GC, Prev: GTY Options, Up: Type Information *************** this to have gengtype autogenerate marki *** 39709,39715 **** --- 40153,40161 ---- * There must be a concrete base class, with a discriminator expression that can be used to identify which subclass an instance is. + * Only single inheritance is used. + * None of the classes within the hierarchy are templates. If your class hierarchy does not fit in this pattern, you must use *************** this to have gengtype autogenerate marki *** 39719,39725 **** "desc" option. Each concrete subclass must use the "tag" option to identify which value of the discriminator it corresponds to. ! Every class in the hierarchy must have a 'GTY(())' marker, as gengtype will only attempt to parse classes that have such a marker (1). class GTY((desc("%h.kind"), tag("0"))) example_base --- 40165,40171 ---- "desc" option. Each concrete subclass must use the "tag" option to identify which value of the discriminator it corresponds to. ! Every class in the hierarchy must have a `GTY(())' marker, as gengtype will only attempt to parse classes that have such a marker (1). class GTY((desc("%h.kind"), tag("0"))) example_base *************** will only attempt to parse classes that *** 39741,39754 **** tree c; }; ! The generated marking routines for the above will contain a "switch" on ! "kind", visiting all appropriate fields. For example, if kind is 2, it ! will cast to "some_other_subclass" and visit fields a, b, and c. ! ---------- Footnotes ---------- ! (1) Classes lacking such a marker will not be identified as being ! part of the hierarchy, and so the marking routines will not handle them, leading to a assertion failure within the marking routines due to an unknown tag value (assuming that assertions are enabled). --- 40187,40200 ---- tree c; }; ! The generated marking routines for the above will contain a "switch" ! on "kind", visiting all appropriate fields. For example, if kind is 2, ! it will cast to "some_other_subclass" and visit fields a, b, and c. ! ---------- Footnotes ---------- ! (1) Classes lacking such a marker will not be identified as being part ! of the hierarchy, and so the marking routines will not handle them, leading to a assertion failure within the marking routines due to an unknown tag value (assuming that assertions are enabled). *************** File: gccint.info, Node: User GC, Next *** 39758,39770 **** 22.3 Support for user-provided GC marking routines ================================================== ! The garbage collector supports types for which no automatic marking code ! is generated. For these types, the user is required to provide three ! functions: one to act as a marker for garbage collection, and two functions to act as marker and pointer walker for pre-compiled headers. ! Given a structure 'struct GTY((user)) my_struct', the following ! functions should be defined to mark 'my_struct': void gt_ggc_mx (my_struct *p) { --- 40204,40216 ---- 22.3 Support for user-provided GC marking routines ================================================== ! The garbage collector supports types for which no automatic marking ! code is generated. For these types, the user is required to provide ! three functions: one to act as a marker for garbage collection, and two functions to act as marker and pointer walker for pre-compiled headers. ! Given a structure `struct GTY((user)) my_struct', the following ! functions should be defined to mark `my_struct': void gt_ggc_mx (my_struct *p) { *************** functions should be defined to mark 'my_ *** 39784,39811 **** op (&(tp->fld), cookie); } ! In general, each marker 'M' should call 'M' for every pointer field in the structure. Fields that are not allocated in GC or are not pointers must be ignored. ! For embedded lists (e.g., structures with a 'next' or 'prev' pointer), the marker must follow the chain and mark every element in it. ! Note that the rules for the pointer walker 'gt_pch_nx (my_struct *, ! gt_pointer_operator, void *)' are slightly different. In this case, the ! operation 'op' must be applied to the _address_ of every pointer field. 22.3.1 User-provided marking routines for template types -------------------------------------------------------- ! When a template type 'TP' is marked with 'GTY', all instances of that ! type are considered user-provided types. This means that the individual ! instances of 'TP' do not need to be marked with 'GTY'. The user needs ! to provide template functions to mark all the fields of the type. ! The following code snippets represent all the functions that need to be ! provided. Note that type 'TP' may reference to more than one type. In ! these snippets, there is only one type 'T', but there could be more. template void gt_ggc_mx (TP *tp) --- 40230,40259 ---- op (&(tp->fld), cookie); } ! In general, each marker `M' should call `M' for every pointer field in the structure. Fields that are not allocated in GC or are not pointers must be ignored. ! For embedded lists (e.g., structures with a `next' or `prev' pointer), the marker must follow the chain and mark every element in it. ! Note that the rules for the pointer walker `gt_pch_nx (my_struct *, ! gt_pointer_operator, void *)' are slightly different. In this case, ! the operation `op' must be applied to the _address_ of every pointer ! field. 22.3.1 User-provided marking routines for template types -------------------------------------------------------- ! When a template type `TP' is marked with `GTY', all instances of that ! type are considered user-provided types. This means that the ! individual instances of `TP' do not need to be marked with `GTY'. The ! user needs to provide template functions to mark all the fields of the ! type. ! The following code snippets represent all the functions that need to ! be provided. Note that type `TP' may reference to more than one type. ! In these snippets, there is only one type `T', but there could be more. template void gt_ggc_mx (TP *tp) *************** these snippets, there is only one type ' *** 39843,39860 **** gt_pch_nx (&(tp->fld), op, cookie); } ! Support for user-defined types is currently limited. The following restrictions apply: ! 1. Type 'TP' and all the argument types 'T' must be marked with 'GTY'. ! 2. Type 'TP' can only have type names in its argument list. ! 3. The pointer walker functions are different for 'TP' and 'TP'. In the case of 'TP', references to 'T' must be handled by ! calling 'gt_pch_nx' (which will, in turn, walk all the pointers ! inside fields of 'T'). In the case of 'TP', references to 'T ! *' must be handled by calling the 'op' function on the address of the pointer (see the code snippets above).  --- 40291,40308 ---- gt_pch_nx (&(tp->fld), op, cookie); } ! Support for user-defined types is currently limited. The following restrictions apply: ! 1. Type `TP' and all the argument types `T' must be marked with `GTY'. ! 2. Type `TP' can only have type names in its argument list. ! 3. The pointer walker functions are different for `TP' and `TP'. In the case of `TP', references to `T' must be handled by ! calling `gt_pch_nx' (which will, in turn, walk all the pointers ! inside fields of `T'). In the case of `TP', references to `T ! *' must be handled by calling the `op' function on the address of the pointer (see the code snippets above).  *************** In addition to keeping track of types, t *** 39867,39879 **** the global variables ("roots") that the garbage collector starts at. Roots must be declared using one of the following syntaxes: ! * 'extern GTY(([OPTIONS])) TYPE NAME;' ! * 'static GTY(([OPTIONS])) TYPE NAME;' ! The syntax ! * 'GTY(([OPTIONS])) TYPE NAME;' ! is _not_ accepted. There should be an 'extern' declaration of such a variable in a header somewhere--mark that, not the definition. Or, if ! the variable is only used in one file, make it 'static'.  File: gccint.info, Node: Files, Next: Invoking the garbage collector, Prev: GGC Roots, Up: Type Information --- 40315,40328 ---- the global variables ("roots") that the garbage collector starts at. Roots must be declared using one of the following syntaxes: ! * `extern GTY(([OPTIONS])) TYPE NAME;' ! ! * `static GTY(([OPTIONS])) TYPE NAME;' ! The syntax ! * `GTY(([OPTIONS])) TYPE NAME;' ! is _not_ accepted. There should be an `extern' declaration of such a variable in a header somewhere--mark that, not the definition. Or, if ! the variable is only used in one file, make it `static'.  File: gccint.info, Node: Files, Next: Invoking the garbage collector, Prev: GGC Roots, Up: Type Information *************** File: gccint.info, Node: Files, Next: *** 39881,39935 **** 22.5 Source Files Containing Type Information ============================================= ! Whenever you add 'GTY' markers to a source file that previously had ! none, or create a new source file containing 'GTY' markers, there are three things you need to do: 1. You need to add the file to the list of source files the type machinery scans. There are four cases: a. For a back-end file, this is usually done automatically; if ! not, you should add it to 'target_gtfiles' in the appropriate ! port's entries in 'config.gcc'. b. For files shared by all front ends, add the filename to the ! 'GTFILES' variable in 'Makefile.in'. c. For files that are part of one front end, add the filename to ! the 'gtfiles' variable defined in the appropriate ! 'config-lang.in'. Headers should appear before non-headers in ! this list. d. For files that are part of some but not all front ends, add ! the filename to the 'gtfiles' variable of _all_ the front ends that use it. 2. If the file was a header file, you'll need to check that it's included in the right place to be visible to the generated files. ! For a back-end header file, this should be done automatically. For ! a front-end header file, it needs to be included by the same file ! that includes 'gtype-LANG.h'. For other header files, it needs to ! be included in 'gtype-desc.c', which is a generated file, so add it ! to 'ifiles' in 'open_base_file' in 'gengtype.c'. For source files that aren't header files, the machinery will generate a header file that should be included in the source file ! you just changed. The file will be called 'gt-PATH.h' where PATH ! is the pathname relative to the 'gcc' directory with slashes replaced by -, so for example the header file to be included in ! 'cp/parser.c' is called 'gt-cp-parser.c'. The generated header file should be included after everything else in the source file. Don't forget to mention this file as a dependency in the ! 'Makefile'! For language frontends, there is another file that needs to be included ! somewhere. It will be called 'gtype-LANG.h', where LANG is the name of the subdirectory the language is contained in. ! Plugins can add additional root tables. Run the 'gengtype' utility in ! plugin mode as 'gengtype -P pluginout.h SOURCE-DIR FILE-LIST PLUGIN*.C' ! with your plugin files PLUGIN*.C using 'GTY' to generate the PLUGINOUT.H ! file. The GCC build tree is needed to be present in that mode.  File: gccint.info, Node: Invoking the garbage collector, Next: Troubleshooting, Prev: Files, Up: Type Information --- 40330,40386 ---- 22.5 Source Files Containing Type Information ============================================= ! Whenever you add `GTY' markers to a source file that previously had ! none, or create a new source file containing `GTY' markers, there are three things you need to do: 1. You need to add the file to the list of source files the type machinery scans. There are four cases: a. For a back-end file, this is usually done automatically; if ! not, you should add it to `target_gtfiles' in the appropriate ! port's entries in `config.gcc'. b. For files shared by all front ends, add the filename to the ! `GTFILES' variable in `Makefile.in'. c. For files that are part of one front end, add the filename to ! the `gtfiles' variable defined in the appropriate ! `config-lang.in'. Headers should appear before non-headers ! in this list. d. For files that are part of some but not all front ends, add ! the filename to the `gtfiles' variable of _all_ the front ends that use it. 2. If the file was a header file, you'll need to check that it's included in the right place to be visible to the generated files. ! For a back-end header file, this should be done automatically. ! For a front-end header file, it needs to be included by the same ! file that includes `gtype-LANG.h'. For other header files, it ! needs to be included in `gtype-desc.c', which is a generated file, ! so add it to `ifiles' in `open_base_file' in `gengtype.c'. For source files that aren't header files, the machinery will generate a header file that should be included in the source file ! you just changed. The file will be called `gt-PATH.h' where PATH ! is the pathname relative to the `gcc' directory with slashes replaced by -, so for example the header file to be included in ! `cp/parser.c' is called `gt-cp-parser.c'. The generated header file should be included after everything else in the source file. Don't forget to mention this file as a dependency in the ! `Makefile'! ! For language frontends, there is another file that needs to be included ! somewhere. It will be called `gtype-LANG.h', where LANG is the name of the subdirectory the language is contained in. ! Plugins can add additional root tables. Run the `gengtype' utility in ! plugin mode as `gengtype -P pluginout.h SOURCE-DIR FILE-LIST PLUGIN*.C' ! with your plugin files PLUGIN*.C using `GTY' to generate the ! PLUGINOUT.H file. The GCC build tree is needed to be present in that ! mode.  File: gccint.info, Node: Invoking the garbage collector, Next: Troubleshooting, Prev: Files, Up: Type Information *************** File: gccint.info, Node: Invoking the g *** 39937,39958 **** 22.6 How to invoke the garbage collector ======================================== ! The GCC garbage collector GGC is only invoked explicitly. In contrast with many other garbage collectors, it is not implicitly invoked by ! allocation routines when a lot of memory has been consumed. So the only ! way to have GGC reclaim storage is to call the 'ggc_collect' function ! explicitly. This call is an expensive operation, as it may have to scan ! the entire heap. Beware that local variables (on the GCC call stack) ! are not followed by such an invocation (as many other garbage collectors ! do): you should reference all your data from static or external 'GTY'-ed ! variables, and it is advised to call 'ggc_collect' with a shallow call ! stack. The GGC is an exact mark and sweep garbage collector (so it does ! not scan the call stack for pointers). In practice GCC passes don't ! often call 'ggc_collect' themselves, because it is called by the pass ! manager between passes. ! At the time of the 'ggc_collect' call all pointers in the GC-marked ! structures must be valid or 'NULL'. In practice this means that there should not be uninitialized pointer fields in the structures even if your code never reads or writes those fields at a particular instance. One way to ensure this is to use cleared versions of allocators unless --- 40388,40409 ---- 22.6 How to invoke the garbage collector ======================================== ! The GCC garbage collector GGC is only invoked explicitly. In contrast with many other garbage collectors, it is not implicitly invoked by ! allocation routines when a lot of memory has been consumed. So the only ! way to have GGC reclaim storage is to call the `ggc_collect' function ! explicitly. This call is an expensive operation, as it may have to ! scan the entire heap. Beware that local variables (on the GCC call ! stack) are not followed by such an invocation (as many other garbage ! collectors do): you should reference all your data from static or ! external `GTY'-ed variables, and it is advised to call `ggc_collect' ! with a shallow call stack. The GGC is an exact mark and sweep garbage ! collector (so it does not scan the call stack for pointers). In ! practice GCC passes don't often call `ggc_collect' themselves, because ! it is called by the pass manager between passes. ! At the time of the `ggc_collect' call all pointers in the GC-marked ! structures must be valid or `NULL'. In practice this means that there should not be uninitialized pointer fields in the structures even if your code never reads or writes those fields at a particular instance. One way to ensure this is to use cleared versions of allocators unless *************** With the current garbage collector imple *** 39968,39985 **** show up as GCC compilation errors. Some of the most commonly encountered issues are described below. ! * Gengtype does not produce allocators for a 'GTY'-marked type. Gengtype checks if there is at least one possible path from GC roots to at least one instance of each type before outputting ! allocators. If there is no such path, the 'GTY' markers will be ignored and no allocators will be output. Solve this by making sure that there exists at least one such path. If creating it is unfeasible or raises a "code smell", consider if you really must use GC for allocating such type. ! * Link-time errors about undefined 'gt_ggc_r_foo_bar' and ! similarly-named symbols. Check if your 'foo_bar' source file has ! '#include "gt-foo_bar.h"' as its very last line.  File: gccint.info, Node: Plugins, Next: LTO, Prev: Type Information, Up: Top --- 40419,40437 ---- show up as GCC compilation errors. Some of the most commonly encountered issues are described below. ! * Gengtype does not produce allocators for a `GTY'-marked type. Gengtype checks if there is at least one possible path from GC roots to at least one instance of each type before outputting ! allocators. If there is no such path, the `GTY' markers will be ignored and no allocators will be output. Solve this by making sure that there exists at least one such path. If creating it is unfeasible or raises a "code smell", consider if you really must use GC for allocating such type. ! * Link-time errors about undefined `gt_ggc_r_foo_bar' and ! similarly-named symbols. Check if your `foo_bar' source file has ! `#include "gt-foo_bar.h"' as its very last line. !  File: gccint.info, Node: Plugins, Next: LTO, Prev: Type Information, Up: Top *************** File: gccint.info, Node: Plugins loadin *** 40015,40037 **** 23.1 Loading Plugins ==================== ! Plugins are supported on platforms that support '-ldl -rdynamic'. They ! are loaded by the compiler using 'dlopen' and invoked at pre-determined locations in the compilation process. Plugins are loaded with ! '-fplugin=/path/to/NAME.so' '-fplugin-arg-NAME-KEY1[=VALUE1]' ! The plugin arguments are parsed by GCC and passed to respective plugins ! as key-value pairs. Multiple plugins can be invoked by specifying ! multiple '-fplugin' arguments. A plugin can be simply given by its short name (no dots or slashes). ! When simply passing '-fplugin=NAME', the plugin is loaded from the ! 'plugin' directory, so '-fplugin=NAME' is the same as '-fplugin=`gcc ! -print-file-name=plugin`/NAME.so', using backquote shell syntax to query ! the 'plugin' directory.  File: gccint.info, Node: Plugin API, Next: Plugins pass, Prev: Plugins loading, Up: Plugins --- 40467,40489 ---- 23.1 Loading Plugins ==================== ! Plugins are supported on platforms that support `-ldl -rdynamic'. They ! are loaded by the compiler using `dlopen' and invoked at pre-determined locations in the compilation process. Plugins are loaded with ! `-fplugin=/path/to/NAME.so' `-fplugin-arg-NAME-KEY1[=VALUE1]' ! The plugin arguments are parsed by GCC and passed to respective ! plugins as key-value pairs. Multiple plugins can be invoked by ! specifying multiple `-fplugin' arguments. A plugin can be simply given by its short name (no dots or slashes). ! When simply passing `-fplugin=NAME', the plugin is loaded from the ! `plugin' directory, so `-fplugin=NAME' is the same as `-fplugin=`gcc ! -print-file-name=plugin`/NAME.so', using backquote shell syntax to ! query the `plugin' directory.  File: gccint.info, Node: Plugin API, Next: Plugins pass, Prev: Plugins loading, Up: Plugins *************** File: gccint.info, Node: Plugin API, N *** 40040,40055 **** =============== Plugins are activated by the compiler at specific events as defined in ! 'gcc-plugin.h'. For each event of interest, the plugin should call ! 'register_callback' specifying the name of the event and address of the callback function that will handle that event. ! The header 'gcc-plugin.h' must be the first gcc header to be included. 23.2.1 Plugin license check --------------------------- ! Every plugin should define the global symbol 'plugin_is_GPL_compatible' to assert that it has been licensed under a GPL-compatible license. If this symbol does not exist, the compiler will emit a fatal error and exit with the error message: --- 40492,40507 ---- =============== Plugins are activated by the compiler at specific events as defined in ! `gcc-plugin.h'. For each event of interest, the plugin should call ! `register_callback' specifying the name of the event and address of the callback function that will handle that event. ! The header `gcc-plugin.h' must be the first gcc header to be included. 23.2.1 Plugin license check --------------------------- ! Every plugin should define the global symbol `plugin_is_GPL_compatible' to assert that it has been licensed under a GPL-compatible license. If this symbol does not exist, the compiler will emit a fatal error and exit with the error message: *************** exit with the error message: *** 40059,40086 **** compilation terminated The declared type of the symbol should be int, to match a forward ! declaration in 'gcc-plugin.h' that suppresses C++ mangling. It does not ! need to be in any allocated section, though. The compiler merely ! asserts that the symbol exists in the global scope. Something like this ! is enough: int plugin_is_GPL_compatible; 23.2.2 Plugin initialization ---------------------------- ! Every plugin should export a function called 'plugin_init' that is ! called right after the plugin is loaded. This function is responsible for registering all the callbacks required by the plugin and do any other required initialization. ! This function is called from 'compile_file' right before invoking the ! parser. The arguments to 'plugin_init' are: ! * 'plugin_info': Plugin invocation information. ! * 'version': GCC version. ! The 'plugin_info' struct is defined as follows: struct plugin_name_args { --- 40511,40539 ---- compilation terminated The declared type of the symbol should be int, to match a forward ! declaration in `gcc-plugin.h' that suppresses C++ mangling. It does ! not need to be in any allocated section, though. The compiler merely ! asserts that the symbol exists in the global scope. Something like ! this is enough: int plugin_is_GPL_compatible; 23.2.2 Plugin initialization ---------------------------- ! Every plugin should export a function called `plugin_init' that is ! called right after the plugin is loaded. This function is responsible for registering all the callbacks required by the plugin and do any other required initialization. ! This function is called from `compile_file' right before invoking the ! parser. The arguments to `plugin_init' are: ! * `plugin_info': Plugin invocation information. ! * `version': GCC version. ! ! The `plugin_info' struct is defined as follows: struct plugin_name_args { *************** parser. The arguments to 'plugin_init' *** 40095,40101 **** const char *help; /* Help string provided by plugin. */ } ! If initialization fails, 'plugin_init' must return a non-zero value. Otherwise, it should return 0. The version of the GCC compiler loading the plugin is described by the --- 40548,40554 ---- const char *help; /* Help string provided by plugin. */ } ! If initialization fails, `plugin_init' must return a non-zero value. Otherwise, it should return 0. The version of the GCC compiler loading the plugin is described by the *************** following structure: *** 40110,40121 **** const char *configuration_arguments; }; ! The function 'plugin_default_version_check' takes two pointers to such ! structure and compare them field by field. It can be used by the ! plugin's 'plugin_init' function. The version of GCC used to compile the plugin can be found in the ! symbol 'gcc_version' defined in the header 'plugin-version.h'. The recommended version check to perform looks like #include "plugin-version.h" --- 40563,40574 ---- const char *configuration_arguments; }; ! The function `plugin_default_version_check' takes two pointers to such ! structure and compare them field by field. It can be used by the ! plugin's `plugin_init' function. The version of GCC used to compile the plugin can be found in the ! symbol `gcc_version' defined in the header `plugin-version.h'. The recommended version check to perform looks like #include "plugin-version.h" *************** Callback functions have the following pr *** 40194,40224 **** In addition, plugins can also look up the enumerator of a named event, and / or generate new events dynamically, by calling the function ! 'get_named_event_id'. ! To register a callback, the plugin calls 'register_callback' with the arguments: ! * 'char *name': Plugin name. ! * 'int event': The event code. ! * 'plugin_callback_func callback': The function that handles 'event'. ! * 'void *user_data': Pointer to plugin-specific data. For the PLUGIN_PASS_MANAGER_SETUP, PLUGIN_INFO, and ! PLUGIN_REGISTER_GGC_ROOTS pseudo-events the 'callback' should be null, ! and the 'user_data' is specific. ! When the PLUGIN_PRAGMAS event is triggered (with a null pointer as data ! from GCC), plugins may register their own pragmas. Notice that pragmas ! are not available from 'lto1', so plugins used with '-flto' option to ! GCC during link-time optimization cannot use pragmas and do not even see ! functions like 'c_register_pragma' or 'pragma_lex'. ! The PLUGIN_INCLUDE_FILE event, with a 'const char*' file path as GCC ! data, is triggered for processing of '#include' or '#line' directives. The PLUGIN_FINISH event is the last time that plugins can call GCC ! functions, notably emit diagnostics with 'warning', 'error' etc.  File: gccint.info, Node: Plugins pass, Next: Plugins GC, Prev: Plugin API, Up: Plugins --- 40647,40680 ---- In addition, plugins can also look up the enumerator of a named event, and / or generate new events dynamically, by calling the function ! `get_named_event_id'. ! To register a callback, the plugin calls `register_callback' with the arguments: ! * `char *name': Plugin name. ! ! * `int event': The event code. ! ! * `plugin_callback_func callback': The function that handles `event'. ! ! * `void *user_data': Pointer to plugin-specific data. For the PLUGIN_PASS_MANAGER_SETUP, PLUGIN_INFO, and ! PLUGIN_REGISTER_GGC_ROOTS pseudo-events the `callback' should be null, ! and the `user_data' is specific. ! When the PLUGIN_PRAGMAS event is triggered (with a null pointer as ! data from GCC), plugins may register their own pragmas. Notice that ! pragmas are not available from `lto1', so plugins used with `-flto' ! option to GCC during link-time optimization cannot use pragmas and do ! not even see functions like `c_register_pragma' or `pragma_lex'. ! The PLUGIN_INCLUDE_FILE event, with a `const char*' file path as GCC ! data, is triggered for processing of `#include' or `#line' directives. The PLUGIN_FINISH event is the last time that plugins can call GCC ! functions, notably emit diagnostics with `warning', `error' etc.  File: gccint.info, Node: Plugins pass, Next: Plugins GC, Prev: Plugin API, Up: Plugins *************** File: gccint.info, Node: Plugins pass, *** 40226,40239 **** 23.3 Interacting with the pass manager ====================================== ! There needs to be a way to add/reorder/remove passes dynamically. This is useful for both analysis plugins (plugging in after a certain pass such as CFG or an IPA pass) and optimization plugins. Basic support for inserting new passes or replacing existing passes is ! provided. A plugin registers a new pass with GCC by calling ! 'register_callback' with the 'PLUGIN_PASS_MANAGER_SETUP' event and a ! pointer to a 'struct register_pass_info' object defined as follows enum pass_positioning_ops { --- 40682,40695 ---- 23.3 Interacting with the pass manager ====================================== ! There needs to be a way to add/reorder/remove passes dynamically. This is useful for both analysis plugins (plugging in after a certain pass such as CFG or an IPA pass) and optimization plugins. Basic support for inserting new passes or replacing existing passes is ! provided. A plugin registers a new pass with GCC by calling ! `register_callback' with the `PLUGIN_PASS_MANAGER_SETUP' event and a ! pointer to a `struct register_pass_info' object defined as follows enum pass_positioning_ops { *************** File: gccint.info, Node: Plugins GC, N *** 40280,40311 **** =============================================== Some plugins may want to be informed when GGC (the GCC Garbage ! Collector) is running. They can register callbacks for the ! 'PLUGIN_GGC_START' and 'PLUGIN_GGC_END' events (for which the callback ! is called with a null 'gcc_data') to be notified of the start or end of the GCC garbage collection. ! Some plugins may need to have GGC mark additional data. This can be ! done by registering a callback (called with a null 'gcc_data') for the ! 'PLUGIN_GGC_MARKING' event. Such callbacks can call the 'ggc_set_mark' ! routine, preferably through the 'ggc_mark' macro (and conversely, these routines should usually not be used in plugins outside of the ! 'PLUGIN_GGC_MARKING' event). Plugins that wish to hold weak references to gc data may also use this event to drop weak references when the ! object is about to be collected. The 'ggc_marked_p' function can be ! used to tell if an object is marked, or is about to be collected. The ! 'gt_clear_cache' overloads which some types define may also be of use in managing weak references. ! Some plugins may need to add extra GGC root tables, e.g. to handle ! their own 'GTY'-ed data. This can be done with the ! 'PLUGIN_REGISTER_GGC_ROOTS' pseudo-event with a null callback and the ! extra root table (of type 'struct ggc_root_tab*') as 'user_data'. ! Running the 'gengtype -p SOURCE-DIR FILE-LIST PLUGIN*.C ...' utility generates these extra root tables. You should understand the details of memory management inside GCC ! before using 'PLUGIN_GGC_MARKING' or 'PLUGIN_REGISTER_GGC_ROOTS'.  File: gccint.info, Node: Plugins description, Next: Plugins attr, Prev: Plugins GC, Up: Plugins --- 40736,40767 ---- =============================================== Some plugins may want to be informed when GGC (the GCC Garbage ! Collector) is running. They can register callbacks for the ! `PLUGIN_GGC_START' and `PLUGIN_GGC_END' events (for which the callback ! is called with a null `gcc_data') to be notified of the start or end of the GCC garbage collection. ! Some plugins may need to have GGC mark additional data. This can be ! done by registering a callback (called with a null `gcc_data') for the ! `PLUGIN_GGC_MARKING' event. Such callbacks can call the `ggc_set_mark' ! routine, preferably through the `ggc_mark' macro (and conversely, these routines should usually not be used in plugins outside of the ! `PLUGIN_GGC_MARKING' event). Plugins that wish to hold weak references to gc data may also use this event to drop weak references when the ! object is about to be collected. The `ggc_marked_p' function can be ! used to tell if an object is marked, or is about to be collected. The ! `gt_clear_cache' overloads which some types define may also be of use in managing weak references. ! Some plugins may need to add extra GGC root tables, e.g. to handle ! their own `GTY'-ed data. This can be done with the ! `PLUGIN_REGISTER_GGC_ROOTS' pseudo-event with a null callback and the ! extra root table (of type `struct ggc_root_tab*') as `user_data'. ! Running the `gengtype -p SOURCE-DIR FILE-LIST PLUGIN*.C ...' utility generates these extra root tables. You should understand the details of memory management inside GCC ! before using `PLUGIN_GGC_MARKING' or `PLUGIN_REGISTER_GGC_ROOTS'.  File: gccint.info, Node: Plugins description, Next: Plugins attr, Prev: Plugins GC, Up: Plugins *************** File: gccint.info, Node: Plugins descri *** 40313,40319 **** 23.5 Giving information about a plugin ====================================== ! A plugin should give some information to the user about itself. This uses the following structure: struct plugin_info --- 40769,40775 ---- 23.5 Giving information about a plugin ====================================== ! A plugin should give some information to the user about itself. This uses the following structure: struct plugin_info *************** uses the following structure: *** 40322,40329 **** const char *help; }; ! Such a structure is passed as the 'user_data' by the plugin's init ! routine using 'register_callback' with the 'PLUGIN_INFO' pseudo-event and a null callback.  --- 40778,40785 ---- const char *help; }; ! Such a structure is passed as the `user_data' by the plugin's init ! routine using `register_callback' with the `PLUGIN_INFO' pseudo-event and a null callback.  *************** File: gccint.info, Node: Plugins attr, *** 40335,40342 **** For analysis (or other) purposes it is useful to be able to add custom attributes or pragmas. ! The 'PLUGIN_ATTRIBUTES' callback is called during attribute ! registration. Use the 'register_attribute' function to register custom attributes. /* Attribute handler callback */ --- 40791,40798 ---- For analysis (or other) purposes it is useful to be able to add custom attributes or pragmas. ! The `PLUGIN_ATTRIBUTES' callback is called during attribute ! registration. Use the `register_attribute' function to register custom attributes. /* Attribute handler callback */ *************** attributes. *** 40361,40373 **** register_attribute (&user_attr); } ! ! The PLUGIN_PRAGMAS callback is called once during pragmas registration. ! Use the 'c_register_pragma', 'c_register_pragma_with_data', ! 'c_register_pragma_with_expansion', ! 'c_register_pragma_with_expansion_and_data' functions to register custom ! pragmas and their handlers (which often want to call 'pragma_lex') from ! 'c-family/c-pragma.h'. /* Plugin callback called during pragmas registration. Registered with register_callback (plugin_name, PLUGIN_PRAGMAS, --- 40817,40828 ---- register_attribute (&user_attr); } ! The PLUGIN_PRAGMAS callback is called once during pragmas ! registration. Use the `c_register_pragma', ! `c_register_pragma_with_data', `c_register_pragma_with_expansion', ! `c_register_pragma_with_expansion_and_data' functions to register ! custom pragmas and their handlers (which often want to call ! `pragma_lex') from `c-family/c-pragma.h'. /* Plugin callback called during pragmas registration. Registered with register_callback (plugin_name, PLUGIN_PRAGMAS, *************** pragmas and their handlers (which often *** 40380,40391 **** c_register_pragma ("GCCPLUGIN", "sayhello", handle_pragma_sayhello); } ! It is suggested to pass '"GCCPLUGIN"' (or a short name identifying your ! plugin) as the "space" argument of your pragma. ! Pragmas registered with 'c_register_pragma_with_expansion' or ! 'c_register_pragma_with_expansion_and_data' support preprocessor ! expansions. For example: #define NUMBER 10 #pragma GCCPLUGIN foothreshold (NUMBER) --- 40835,40846 ---- c_register_pragma ("GCCPLUGIN", "sayhello", handle_pragma_sayhello); } ! It is suggested to pass `"GCCPLUGIN"' (or a short name identifying ! your plugin) as the "space" argument of your pragma. ! Pragmas registered with `c_register_pragma_with_expansion' or ! `c_register_pragma_with_expansion_and_data' support preprocessor ! expansions. For example: #define NUMBER 10 #pragma GCCPLUGIN foothreshold (NUMBER) *************** File: gccint.info, Node: Plugins record *** 40397,40410 **** =============================================== The event PLUGIN_PASS_EXECUTION passes the pointer to the executed pass ! (the same as current_pass) as 'gcc_data' to the callback. You can also inspect cfun to find out about which function this pass is executed for. Note that this event will only be invoked if the gate check (if applicable, modified by PLUGIN_OVERRIDE_GATE) succeeds. You can use ! other hooks, like 'PLUGIN_ALL_PASSES_START', 'PLUGIN_ALL_PASSES_END', ! 'PLUGIN_ALL_IPA_PASSES_START', 'PLUGIN_ALL_IPA_PASSES_END', ! 'PLUGIN_EARLY_GIMPLE_PASSES_START', and/or ! 'PLUGIN_EARLY_GIMPLE_PASSES_END' to manipulate global state in your plugin(s) in order to get context for the pass execution.  --- 40852,40865 ---- =============================================== The event PLUGIN_PASS_EXECUTION passes the pointer to the executed pass ! (the same as current_pass) as `gcc_data' to the callback. You can also inspect cfun to find out about which function this pass is executed for. Note that this event will only be invoked if the gate check (if applicable, modified by PLUGIN_OVERRIDE_GATE) succeeds. You can use ! other hooks, like `PLUGIN_ALL_PASSES_START', `PLUGIN_ALL_PASSES_END', ! `PLUGIN_ALL_IPA_PASSES_START', `PLUGIN_ALL_IPA_PASSES_END', ! `PLUGIN_EARLY_GIMPLE_PASSES_START', and/or ! `PLUGIN_EARLY_GIMPLE_PASSES_END' to manipulate global state in your plugin(s) in order to get context for the pass execution.  *************** File: gccint.info, Node: Plugins gate, *** 40415,40422 **** After the original gate function for a pass is called, its result - the gate status - is stored as an integer. Then the event ! 'PLUGIN_OVERRIDE_GATE' is invoked, with a pointer to the gate status in ! the 'gcc_data' parameter to the callback function. A nonzero value of the gate status means that the pass is to be executed. You can both read and write the gate status via the passed pointer. --- 40870,40877 ---- After the original gate function for a pass is called, its result - the gate status - is stored as an integer. Then the event ! `PLUGIN_OVERRIDE_GATE' is invoked, with a pointer to the gate status in ! the `gcc_data' parameter to the callback function. A nonzero value of the gate status means that the pass is to be executed. You can both read and write the gate status via the passed pointer. *************** File: gccint.info, Node: Plugins tracki *** 40429,40437 **** When your plugin is loaded, you can inspect the various pass lists to determine what passes are available. However, other plugins might add new passes. Also, future changes to GCC might cause generic passes to ! be added after plugin loading. When a pass is first added to one of the ! pass lists, the event 'PLUGIN_NEW_PASS' is invoked, with the callback ! parameter 'gcc_data' pointing to the new pass.  File: gccint.info, Node: Plugins building, Prev: Plugins tracking, Up: Plugins --- 40884,40892 ---- When your plugin is loaded, you can inspect the various pass lists to determine what passes are available. However, other plugins might add new passes. Also, future changes to GCC might cause generic passes to ! be added after plugin loading. When a pass is first added to one of ! the pass lists, the event `PLUGIN_NEW_PASS' is invoked, with the ! callback parameter `gcc_data' pointing to the new pass.  File: gccint.info, Node: Plugins building, Prev: Plugins tracking, Up: Plugins *************** File: gccint.info, Node: Plugins buildi *** 40440,40461 **** ========================== If plugins are enabled, GCC installs the headers needed to build a ! plugin (somewhere in the installation tree, e.g. under '/usr/local'). ! In particular a 'plugin/include' directory is installed, containing all the header files needed to build plugins. ! On most systems, you can query this 'plugin' directory by invoking 'gcc ! -print-file-name=plugin' (replace if needed 'gcc' with the appropriate ! program path). ! Inside plugins, this 'plugin' directory name can be queried by calling ! 'default_plugin_dir_name ()'. Plugins may know, when they are compiled, the GCC version for which ! 'plugin-version.h' is provided. The constant macros ! 'GCCPLUGIN_VERSION_MAJOR', 'GCCPLUGIN_VERSION_MINOR', ! 'GCCPLUGIN_VERSION_PATCHLEVEL', 'GCCPLUGIN_VERSION' are integer numbers, ! so a plugin could ensure it is built for GCC 4.7 with #if GCCPLUGIN_VERSION != 4007 #error this GCC plugin is for GCC 4.7 #endif --- 40895,40916 ---- ========================== If plugins are enabled, GCC installs the headers needed to build a ! plugin (somewhere in the installation tree, e.g. under `/usr/local'). ! In particular a `plugin/include' directory is installed, containing all the header files needed to build plugins. ! On most systems, you can query this `plugin' directory by invoking ! `gcc -print-file-name=plugin' (replace if needed `gcc' with the ! appropriate program path). ! Inside plugins, this `plugin' directory name can be queried by calling ! `default_plugin_dir_name ()'. Plugins may know, when they are compiled, the GCC version for which ! `plugin-version.h' is provided. The constant macros ! `GCCPLUGIN_VERSION_MAJOR', `GCCPLUGIN_VERSION_MINOR', ! `GCCPLUGIN_VERSION_PATCHLEVEL', `GCCPLUGIN_VERSION' are integer ! numbers, so a plugin could ensure it is built for GCC 4.7 with #if GCCPLUGIN_VERSION != 4007 #error this GCC plugin is for GCC 4.7 #endif *************** so a plugin could ensure it is built for *** 40471,40484 **** plugin.so: $(PLUGIN_SOURCE_FILES) $(HOST_GCC) -shared $(CXXFLAGS) $^ -o $@ ! A single source file plugin may be built with 'g++ -I`gcc -print-file-name=plugin`/include -fPIC -shared -fno-rtti -O2 plugin.c -o ! plugin.so', using backquote shell syntax to query the 'plugin' directory. ! When a plugin needs to use 'gengtype', be sure that both 'gengtype' and ! 'gtype.state' have the same version as the GCC for which the plugin is ! built.  File: gccint.info, Node: LTO, Next: Match and Simplify, Prev: Plugins, Up: Top --- 40926,40939 ---- plugin.so: $(PLUGIN_SOURCE_FILES) $(HOST_GCC) -shared $(CXXFLAGS) $^ -o $@ ! A single source file plugin may be built with `g++ -I`gcc -print-file-name=plugin`/include -fPIC -shared -fno-rtti -O2 plugin.c -o ! plugin.so', using backquote shell syntax to query the `plugin' directory. ! When a plugin needs to use `gengtype', be sure that both `gengtype' ! and `gtype.state' have the same version as the GCC for which the plugin ! is built.  File: gccint.info, Node: LTO, Next: Match and Simplify, Prev: Plugins, Up: Top *************** File: gccint.info, Node: LTO, Next: Ma *** 40488,40497 **** 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 inter-procedural optimizations ! to encompass the whole program (or, rather, everything that is visible ! at link time). * Menu: --- 40943,40952 ---- 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 inter-procedural ! optimizations to encompass the whole program (or, rather, everything ! that is visible at link time). * Menu: *************** at link time). *** 40500,40506 **** * IPA:: Using summary information in IPA passes. * WHOPR:: Whole program assumptions, linker plugin and symbol visibilities. ! * Internal flags:: Internal flags controlling 'lto1'.  File: gccint.info, Node: LTO Overview, Next: LTO object file layout, Up: LTO --- 40955,40961 ---- * IPA:: Using summary information in IPA passes. * WHOPR:: Whole program assumptions, linker plugin and symbol visibilities. ! * Internal flags:: Internal flags controlling `lto1'.  File: gccint.info, Node: LTO Overview, Next: LTO object file layout, Up: LTO *************** File: gccint.info, Node: LTO Overview, *** 40509,40515 **** ==================== Link time optimization is implemented as a GCC front end for a bytecode ! representation of GIMPLE that is emitted in special sections of '.o' files. Currently, LTO support is enabled in most ELF-based systems, as well as darwin, cygwin and mingw systems. --- 40964,40970 ---- ==================== Link time optimization is implemented as a GCC front end for a bytecode ! representation of GIMPLE that is emitted in special sections of `.o' files. Currently, LTO support is enabled in most ELF-based systems, as well as darwin, cygwin and mingw systems. *************** build systems, as one can, for instance, *** 40520,40536 **** Additionally, one might be able to ship one set of fat objects which could be used both for development and the production of optimized builds. A, perhaps surprising, side effect of this feature is that any ! mistake in the toolchain that leads to LTO information not being used ! (e.g. an older 'libtool' calling 'ld' directly). This is both an ! advantage, as the system is more robust, and a disadvantage, as the user ! is not informed that the optimization has been disabled. The current implementation only produces "fat" objects, effectively doubling compilation time and increasing file sizes up to 5x the ! original size. This hides the problem that some tools, such as 'ar' and ! 'nm', need to understand symbol tables of LTO sections. These tools ! were extended to use the plugin infrastructure, and with these problems ! solved, GCC will also support "slim" objects consisting of the intermediate code alone. At the highest level, LTO splits the compiler in two. The first half --- 40975,40991 ---- Additionally, one might be able to ship one set of fat objects which could be used both for development and the production of optimized builds. A, perhaps surprising, side effect of this feature is that any ! mistake in the toolchain leads to LTO information not being used (e.g. ! an older `libtool' calling `ld' directly). This is both an advantage, ! as the system is more robust, and a disadvantage, as the user is not ! informed that the optimization has been disabled. The current implementation only produces "fat" objects, effectively doubling compilation time and increasing file sizes up to 5x the ! original size. This hides the problem that some tools, such as `ar' ! and `nm', need to understand symbol tables of LTO sections. These ! tools were extended to use the plugin infrastructure, and with these ! problems solved, GCC will also support "slim" objects consisting of the intermediate code alone. At the highest level, LTO splits the compiler in two. The first half *************** data structures needed to optimize and g *** 40539,40586 **** declarations, types, the callgraph and the GIMPLE representation of function bodies. ! When '-flto' is given during compilation of a source file, the pass ! manager executes all the passes in 'all_lto_gen_passes'. Currently, this phase is composed of two IPA passes: ! * 'pass_ipa_lto_gimple_out' This pass executes the function ! 'lto_output' in 'lto-streamer-out.c', which traverses the call graph encoding every reachable declaration, type and function. This generates a memory representation of all the file sections described below. ! * 'pass_ipa_lto_finish_out' This pass executes the function ! 'produce_asm_for_decls' in 'lto-streamer-out.c', which takes the memory image built in the previous pass and encodes it in the corresponding ELF file sections. ! The second half of LTO support is the "reader". This is implemented as ! the GCC front end 'lto1' in 'lto/lto.c'. When 'collect2' detects a link ! set of '.o'/'.a' files with LTO information and the '-flto' is enabled, ! it invokes 'lto1' which reads the set of files and aggregates them into ! a single translation unit for optimization. The main entry point for ! the reader is 'lto/lto.c':'lto_main'. 24.1.1 LTO modes of operation ----------------------------- One of the main goals of the GCC link-time infrastructure was to allow ! effective compilation of large programs. For this reason GCC implements ! two link-time compilation modes. ! 1. _LTO mode_, in which the whole program is read into the compiler at ! link-time and optimized in a similar way as if it were a single source-level compilation unit. 2. _WHOPR or partitioned mode_, designed to utilize multiple CPUs and/or a distributed compilation environment to quickly link large applications. WHOPR stands for WHOle Program optimizeR (not to be ! confused with the semantics of '-fwhole-program'). It partitions ! the aggregated callgraph from many different '.o' files and distributes the compilation of the sub-graphs to different CPUs. Note that distributed compilation is not implemented yet, but since ! the parallelism is facilitated via generating a 'Makefile', it would be easy to implement. WHOPR splits LTO into three main stages: --- 40994,41041 ---- declarations, types, the callgraph and the GIMPLE representation of function bodies. ! When `-flto' is given during compilation of a source file, the pass ! manager executes all the passes in `all_lto_gen_passes'. Currently, this phase is composed of two IPA passes: ! * `pass_ipa_lto_gimple_out' This pass executes the function ! `lto_output' in `lto-streamer-out.c', which traverses the call graph encoding every reachable declaration, type and function. This generates a memory representation of all the file sections described below. ! * `pass_ipa_lto_finish_out' This pass executes the function ! `produce_asm_for_decls' in `lto-streamer-out.c', which takes the memory image built in the previous pass and encodes it in the corresponding ELF file sections. ! The second half of LTO support is the "reader". This is implemented ! as the GCC front end `lto1' in `lto/lto.c'. When `collect2' detects a ! link set of `.o'/`.a' files with LTO information and the `-flto' is ! enabled, it invokes `lto1' which reads the set of files and aggregates ! them into a single translation unit for optimization. The main entry ! point for the reader is `lto/lto.c':`lto_main'. 24.1.1 LTO modes of operation ----------------------------- One of the main goals of the GCC link-time infrastructure was to allow ! effective compilation of large programs. For this reason GCC ! implements two link-time compilation modes. ! 1. _LTO mode_, in which the whole program is read into the compiler ! at link-time and optimized in a similar way as if it were a single source-level compilation unit. 2. _WHOPR or partitioned mode_, designed to utilize multiple CPUs and/or a distributed compilation environment to quickly link large applications. WHOPR stands for WHOle Program optimizeR (not to be ! confused with the semantics of `-fwhole-program'). It partitions ! the aggregated callgraph from many different `.o' files and distributes the compilation of the sub-graphs to different CPUs. Note that distributed compilation is not implemented yet, but since ! the parallelism is facilitated via generating a `Makefile', it would be easy to implement. WHOPR splits LTO into three main stages: *************** two link-time compilation modes. *** 40594,40602 **** global call-graph is generated, and a global analysis procedure makes transformation decisions. The global call-graph is partitioned to facilitate parallel optimization during phase 3. ! The results of the WPA stage are stored into new object files which ! contain the partitions of program expressed in the intermediate ! language and the optimization decisions. 3. Local transformations (LTRANS) This stage executes in parallel. All the decisions made during phase 2 are implemented locally in --- 41049,41057 ---- global call-graph is generated, and a global analysis procedure makes transformation decisions. The global call-graph is partitioned to facilitate parallel optimization during phase 3. ! The results of the WPA stage are stored into new object files ! which contain the partitions of program expressed in the ! intermediate language and the optimization decisions. 3. Local transformations (LTRANS) This stage executes in parallel. All the decisions made during phase 2 are implemented locally in *************** two link-time compilation modes. *** 40605,40621 **** during the phase 2 may be performed on the local call-graph partitions. ! WHOPR can be seen as an extension of the usual LTO mode of compilation. ! In LTO, WPA and LTRANS are executed within a single execution of the ! compiler, after the whole program has been read into memory. When compiling in WHOPR mode, the callgraph is partitioned during the ! WPA stage. The whole program is split into a given number of partitions ! of roughly the same size. The compiler tries to minimize the number of ! references which cross partition boundaries. The main advantage of ! WHOPR is to allow the parallel execution of LTRANS stages, which are the ! most time-consuming part of the compilation process. Additionally, it ! avoids the need to load the whole program into memory.  File: gccint.info, Node: LTO object file layout, Next: IPA, Prev: LTO Overview, Up: LTO --- 41060,41077 ---- during the phase 2 may be performed on the local call-graph partitions. ! WHOPR can be seen as an extension of the usual LTO mode of ! compilation. In LTO, WPA and LTRANS are executed within a single ! execution of the compiler, after the whole program has been read into ! memory. When compiling in WHOPR mode, the callgraph is partitioned during the ! WPA stage. The whole program is split into a given number of ! partitions of roughly the same size. The compiler tries to minimize ! the number of references which cross partition boundaries. The main ! advantage of WHOPR is to allow the parallel execution of LTRANS stages, ! which are the most time-consuming part of the compilation process. ! Additionally, it avoids the need to load the whole program into memory.  File: gccint.info, Node: LTO object file layout, Next: IPA, Prev: LTO Overview, Up: LTO *************** File: gccint.info, Node: LTO object fil *** 40625,40637 **** LTO information is stored in several ELF sections inside object files. Data structures and enum codes for sections are defined in ! 'lto-streamer.h'. ! These sections are emitted from 'lto-streamer-out.c' and mapped in all ! at once from 'lto/lto.c':'lto_file_read'. The individual functions dealing with the reading/writing of each section are described below. ! * Command line options ('.gnu.lto_.opts') This section contains the command line options used to generate the object files. This is used at link time to determine the --- 41081,41093 ---- LTO information is stored in several ELF sections inside object files. Data structures and enum codes for sections are defined in ! `lto-streamer.h'. ! These sections are emitted from `lto-streamer-out.c' and mapped in all ! at once from `lto/lto.c':`lto_file_read'. The individual functions dealing with the reading/writing of each section are described below. ! * Command line options (`.gnu.lto_.opts') This section contains the command line options used to generate the object files. This is used at link time to determine the *************** dealing with the reading/writing of each *** 40644,40655 **** the options saved on all the files in a link-time set are applied globally. No attempt is made at validating the combination of flags (other than the usual validation done by option processing). ! This is implemented in 'lto/lto.c':'lto_read_all_file_options'. ! * Symbol table ('.gnu.lto_.symtab') This table replaces the ELF symbol table for functions and ! variables represented in the LTO IL. Symbols used and exported by the optimized assembly code of "fat" objects might not match the ones used and exported by the intermediate code. This table is necessary because the intermediate code is less optimized and thus --- 41100,41111 ---- the options saved on all the files in a link-time set are applied globally. No attempt is made at validating the combination of flags (other than the usual validation done by option processing). ! This is implemented in `lto/lto.c':`lto_read_all_file_options'. ! * Symbol table (`.gnu.lto_.symtab') This table replaces the ELF symbol table for functions and ! variables represented in the LTO IL. Symbols used and exported by the optimized assembly code of "fat" objects might not match the ones used and exported by the intermediate code. This table is necessary because the intermediate code is less optimized and thus *************** dealing with the reading/writing of each *** 40663,40726 **** symbol table was used. The symbol table is emitted in ! 'lto-streamer-out.c':'produce_symtab'. ! * Global declarations and types ('.gnu.lto_.decls') This section contains an intermediate language dump of all declarations and types required to represent the callgraph, static variables and top-level debug info. The contents of this section are emitted in ! 'lto-streamer-out.c':'produce_asm_for_decls'. Types and symbols are emitted in a topological order that preserves the sharing of pointers when the file is read back in ! ('lto.c':'read_cgraph_and_symbols'). ! * The callgraph ('.gnu.lto_.cgraph') This section contains the basic data structure used by the GCC inter-procedural optimization infrastructure. This section stores an annotated multi-graph which represents the functions and call ! sites as well as the variables, aliases and top-level 'asm' statements. ! This section is emitted in 'lto-streamer-out.c':'output_cgraph' and ! read in 'lto-cgraph.c':'input_cgraph'. ! * IPA references ('.gnu.lto_.refs') This section contains references between function and static ! variables. It is emitted by 'lto-cgraph.c':'output_refs' and read ! by 'lto-cgraph.c':'input_refs'. ! * Function bodies ('.gnu.lto_.function_body.') This section contains function bodies in the intermediate language representation. Every function body is in a separate section to allow copying of the section independently to different object files or reading the function on demand. ! Functions are emitted in 'lto-streamer-out.c':'output_function' and ! read in 'lto-streamer-in.c':'input_function'. ! * Static variable initializers ('.gnu.lto_.vars') This section contains all the symbols in the global variable pool. ! It is emitted by 'lto-cgraph.c':'output_varpool' and read in ! 'lto-cgraph.c':'input_cgraph'. * Summaries and optimization summaries used by IPA passes ! ('.gnu.lto_.', where '' is one of 'jmpfuncs', 'pureconst' ! or 'reference') These sections are used by IPA passes that need to emit summary ! information during LTO generation to be read and aggregated at link ! time. Each pass is responsible for implementing two pass manager ! hooks: one for writing the summary and another for reading it in. ! The format of these sections is entirely up to each individual ! pass. The only requirement is that the writer and reader hooks ! agree on the format.  File: gccint.info, Node: IPA, Next: WHOPR, Prev: LTO object file layout, Up: LTO --- 41119,41182 ---- symbol table was used. The symbol table is emitted in ! `lto-streamer-out.c':`produce_symtab'. ! * Global declarations and types (`.gnu.lto_.decls') This section contains an intermediate language dump of all declarations and types required to represent the callgraph, static variables and top-level debug info. The contents of this section are emitted in ! `lto-streamer-out.c':`produce_asm_for_decls'. Types and symbols are emitted in a topological order that preserves the sharing of pointers when the file is read back in ! (`lto.c':`read_cgraph_and_symbols'). ! * The callgraph (`.gnu.lto_.cgraph') This section contains the basic data structure used by the GCC inter-procedural optimization infrastructure. This section stores an annotated multi-graph which represents the functions and call ! sites as well as the variables, aliases and top-level `asm' statements. ! This section is emitted in `lto-streamer-out.c':`output_cgraph' ! and read in `lto-cgraph.c':`input_cgraph'. ! * IPA references (`.gnu.lto_.refs') This section contains references between function and static ! variables. It is emitted by `lto-cgraph.c':`output_refs' and read ! by `lto-cgraph.c':`input_refs'. ! * Function bodies (`.gnu.lto_.function_body.') This section contains function bodies in the intermediate language representation. Every function body is in a separate section to allow copying of the section independently to different object files or reading the function on demand. ! Functions are emitted in `lto-streamer-out.c':`output_function' ! and read in `lto-streamer-in.c':`input_function'. ! * Static variable initializers (`.gnu.lto_.vars') This section contains all the symbols in the global variable pool. ! It is emitted by `lto-cgraph.c':`output_varpool' and read in ! `lto-cgraph.c':`input_cgraph'. * Summaries and optimization summaries used by IPA passes ! (`.gnu.lto_.', where `' is one of `jmpfuncs', ! `pureconst' or `reference') These sections are used by IPA passes that need to emit summary ! information during LTO generation to be read and aggregated at ! link time. Each pass is responsible for implementing two pass ! manager hooks: one for writing the summary and another for reading ! it in. The format of these sections is entirely up to each ! individual pass. The only requirement is that the writer and ! reader hooks agree on the format.  File: gccint.info, Node: IPA, Next: WHOPR, Prev: LTO object file layout, Up: LTO *************** optimization pass is split into several *** 40739,40784 **** different times during WHOPR compilation: * LGEN time ! 1. _Generate summary_ ('generate_summary' in 'struct ! ipa_opt_pass_d'). This stage analyzes every function body and ! variable initializer is examined and stores relevant information into a pass-specific data structure. ! 2. _Write summary_ ('write_summary' in 'struct ipa_opt_pass_d'). This stage writes all the pass-specific information generated ! by 'generate_summary'. Summaries go into their own ! 'LTO_section_*' sections that have to be declared in ! 'lto-streamer.h':'enum lto_section_type'. A new section is ! created by calling 'create_output_block' and data can be ! written using the 'lto_output_*' routines. * WPA time ! 1. _Read summary_ ('read_summary' in 'struct ipa_opt_pass_d'). This stage reads all the pass-specific information in exactly ! the same order that it was written by 'write_summary'. ! 2. _Execute_ ('execute' in 'struct opt_pass'). This performs inter-procedural propagation. This must be done without actual access to the individual function bodies or variable ! initializers. Typically, this results in a transitive closure ! operation over the summary information of all the nodes in the ! callgraph. ! 3. _Write optimization summary_ ('write_optimization_summary' in ! 'struct ipa_opt_pass_d'). This writes the result of the inter-procedural propagation into the object file. This can use the same data structures and helper routines used in ! 'write_summary'. * LTRANS time ! 1. _Read optimization summary_ ('read_optimization_summary' in ! 'struct ipa_opt_pass_d'). The counterpart to ! 'write_optimization_summary'. This reads the interprocedural optimization decisions in exactly the same format emitted by ! 'write_optimization_summary'. ! 2. _Transform_ ('function_transform' and 'variable_transform' in ! 'struct ipa_opt_pass_d'). The actual function bodies and variable initializers are updated based on the information passed down from the _Execute_ stage. --- 41195,41240 ---- different times during WHOPR compilation: * LGEN time ! 1. _Generate summary_ (`generate_summary' in `struct ! ipa_opt_pass_d'). This stage analyzes every function body ! and variable initializer is examined and stores relevant information into a pass-specific data structure. ! 2. _Write summary_ (`write_summary' in `struct ipa_opt_pass_d'). This stage writes all the pass-specific information generated ! by `generate_summary'. Summaries go into their own ! `LTO_section_*' sections that have to be declared in ! `lto-streamer.h':`enum lto_section_type'. A new section is ! created by calling `create_output_block' and data can be ! written using the `lto_output_*' routines. * WPA time ! 1. _Read summary_ (`read_summary' in `struct ipa_opt_pass_d'). This stage reads all the pass-specific information in exactly ! the same order that it was written by `write_summary'. ! 2. _Execute_ (`execute' in `struct opt_pass'). This performs inter-procedural propagation. This must be done without actual access to the individual function bodies or variable ! initializers. Typically, this results in a transitive ! closure operation over the summary information of all the ! nodes in the callgraph. ! 3. _Write optimization summary_ (`write_optimization_summary' in ! `struct ipa_opt_pass_d'). This writes the result of the inter-procedural propagation into the object file. This can use the same data structures and helper routines used in ! `write_summary'. * LTRANS time ! 1. _Read optimization summary_ (`read_optimization_summary' in ! `struct ipa_opt_pass_d'). The counterpart to ! `write_optimization_summary'. This reads the interprocedural optimization decisions in exactly the same format emitted by ! `write_optimization_summary'. ! 2. _Transform_ (`function_transform' and `variable_transform' in ! `struct ipa_opt_pass_d'). The actual function bodies and variable initializers are updated based on the information passed down from the _Execute_ stage. *************** LTO, WHOPR and classic non-LTO compilati *** 40798,40804 **** To simplify development, the GCC pass manager differentiates between normal inter-procedural passes and small inter-procedural passes. A ! _small inter-procedural pass_ ('SIMPLE_IPA_PASS') is a pass that does everything at once and thus it can not be executed during WPA in WHOPR mode. It defines only the _Execute_ stage and during this stage it accesses and modifies the function bodies. Such passes are useful for --- 41254,41260 ---- To simplify development, the GCC pass manager differentiates between normal inter-procedural passes and small inter-procedural passes. A ! _small inter-procedural pass_ (`SIMPLE_IPA_PASS') is a pass that does everything at once and thus it can not be executed during WPA in WHOPR mode. It defines only the _Execute_ stage and during this stage it accesses and modifies the function bodies. Such passes are useful for *************** development of a new inter-procedural pa *** 40810,40822 **** 24.3.1 Virtual clones --------------------- ! One of the main challenges of introducing the WHOPR compilation mode was ! addressing the interactions between optimization passes. In LTO compilation mode, the passes are executed in a sequence, each of which ! consists of analysis (or _Generate summary_), propagation (or _Execute_) ! and _Transform_ stages. Once the work of one pass is finished, the next ! pass sees the updated program representation and can execute. This ! makes the individual passes dependent on each other. In WHOPR mode all passes first execute their _Generate summary_ stage. Then summary writing marks the end of the LGEN stage. At WPA time, the --- 41266,41278 ---- 24.3.1 Virtual clones --------------------- ! One of the main challenges of introducing the WHOPR compilation mode ! was addressing the interactions between optimization passes. In LTO compilation mode, the passes are executed in a sequence, each of which ! consists of analysis (or _Generate summary_), propagation (or ! _Execute_) and _Transform_ stages. Once the work of one pass is ! finished, the next pass sees the updated program representation and can ! execute. This makes the individual passes dependent on each other. In WHOPR mode all passes first execute their _Generate summary_ stage. Then summary writing marks the end of the LGEN stage. At WPA time, the *************** summaries are read back into memory and *** 40824,40861 **** stage. Optimization summaries are streamed and sent to LTRANS, where all the passes execute the _Transform_ stage. ! Most optimization passes split naturally into analysis, propagation and ! transformation stages. But some do not. The main problem arises when ! one pass performs changes and the following pass gets confused by seeing ! different callgraphs between the _Transform_ stage and the _Generate ! summary_ or _Execute_ stage. This means that the passes are required to ! communicate their decisions with each other. To facilitate this communication, the GCC callgraph infrastructure implements _virtual clones_, a method of representing the changes ! performed by the optimization passes in the callgraph without needing to ! update function bodies. ! A _virtual clone_ in the callgraph is a function that has no associated ! body, just a description of how to create its body based on a different ! function (which itself may be a virtual clone). The description of function modifications includes adjustments to the function's signature (which allows, for example, removing or adding ! function arguments), substitutions to perform on the function body, and, ! for inlined functions, a pointer to the function that it will be inlined ! into. It is also possible to redirect any edge of the callgraph from a function to its virtual clone. This implies updating of the call site to adjust for the new function signature. ! Most of the transformations performed by inter-procedural optimizations ! can be represented via virtual clones. For instance, a constant ! propagation pass can produce a virtual clone of the function which ! replaces one of its arguments by a constant. The inliner can represent ! its decisions by producing a clone of a function whose body will be ! later integrated into a given function. Using _virtual clones_, the program can be easily updated during the _Execute_ stage, solving most of pass interactions problems that would --- 41280,41317 ---- stage. Optimization summaries are streamed and sent to LTRANS, where all the passes execute the _Transform_ stage. ! Most optimization passes split naturally into analysis, propagation ! and transformation stages. But some do not. The main problem arises ! when one pass performs changes and the following pass gets confused by ! seeing different callgraphs between the _Transform_ stage and the ! _Generate summary_ or _Execute_ stage. This means that the passes are ! required to communicate their decisions with each other. To facilitate this communication, the GCC callgraph infrastructure implements _virtual clones_, a method of representing the changes ! performed by the optimization passes in the callgraph without needing ! to update function bodies. ! A _virtual clone_ in the callgraph is a function that has no ! associated body, just a description of how to create its body based on ! a different function (which itself may be a virtual clone). The description of function modifications includes adjustments to the function's signature (which allows, for example, removing or adding ! function arguments), substitutions to perform on the function body, ! and, for inlined functions, a pointer to the function that it will be ! inlined into. It is also possible to redirect any edge of the callgraph from a function to its virtual clone. This implies updating of the call site to adjust for the new function signature. ! Most of the transformations performed by inter-procedural ! optimizations can be represented via virtual clones. For instance, a ! constant propagation pass can produce a virtual clone of the function ! which replaces one of its arguments by a constant. The inliner can ! represent its decisions by producing a clone of a function whose body ! will be later integrated into a given function. Using _virtual clones_, the program can be easily updated during the _Execute_ stage, solving most of pass interactions problems that would *************** otherwise occur during _Transform_. *** 40863,40875 **** Virtual clones are later materialized in the LTRANS stage and turned into real functions. Passes executed after the virtual clone were ! introduced also perform their _Transform_ stage on new functions, so for ! a pass there is no significant difference between operating on a real ! function or a virtual clone introduced before its _Execute_ stage. ! Optimization passes then work on virtual clones introduced before their ! _Execute_ stage as if they were real functions. The only difference is ! that clones are not visible during the _Generate Summary_ stage. To keep function summaries updated, the callgraph interface allows an optimizer to register a callback that is called every time a new clone --- 41319,41332 ---- Virtual clones are later materialized in the LTRANS stage and turned into real functions. Passes executed after the virtual clone were ! introduced also perform their _Transform_ stage on new functions, so ! for a pass there is no significant difference between operating on a ! real function or a virtual clone introduced before its _Execute_ stage. ! Optimization passes then work on virtual clones introduced before ! their _Execute_ stage as if they were real functions. The only ! difference is that clones are not visible during the _Generate Summary_ ! stage. To keep function summaries updated, the callgraph interface allows an optimizer to register a callback that is called every time a new clone *************** summaries updated for the _Transform_ st *** 40884,40902 **** --------------------- GCC represents IPA references in the callgraph. For a function or ! variable 'A', the _IPA reference_ is a list of all locations where the ! address of 'A' is taken and, when 'A' is a variable, a list of all ! direct stores and reads to/from 'A'. References represent an oriented multi-graph on the union of nodes of the callgraph and the varpool. See ! 'ipa-reference.c':'ipa_reference_write_optimization_summary' and ! 'ipa-reference.c':'ipa_reference_read_optimization_summary' for details. 24.3.3 Jump functions --------------------- ! Suppose that an optimization pass sees a function 'A' and it knows the values of (some of) its arguments. The _jump function_ describes the ! value of a parameter of a given function call in function 'A' based on this knowledge. Jump functions are used by several optimizations, such as the --- 41341,41359 ---- --------------------- GCC represents IPA references in the callgraph. For a function or ! variable `A', the _IPA reference_ is a list of all locations where the ! address of `A' is taken and, when `A' is a variable, a list of all ! direct stores and reads to/from `A'. References represent an oriented multi-graph on the union of nodes of the callgraph and the varpool. See ! `ipa-reference.c':`ipa_reference_write_optimization_summary' and ! `ipa-reference.c':`ipa_reference_read_optimization_summary' for details. 24.3.3 Jump functions --------------------- ! Suppose that an optimization pass sees a function `A' and it knows the values of (some of) its arguments. The _jump function_ describes the ! value of a parameter of a given function call in function `A' based on this knowledge. Jump functions are used by several optimizations, such as the *************** File: gccint.info, Node: WHOPR, Next: *** 40911,40965 **** ===================================================================== Link-time optimization gives relatively minor benefits when used alone. ! The problem is that propagation of inter-procedural information does not ! work well across functions and variables that are called or referenced ! by other compilation units (such as from a dynamically linked library). ! We say that such functions and variables are _externally visible_. To make the situation even more difficult, many applications organize themselves as a set of shared libraries, and the default ELF visibility rules allow one to overwrite any externally visible symbol with a different symbol at runtime. This basically disables any optimizations ! across such functions and variables, because the compiler cannot be sure ! that the function body it is seeing is the same function body that will ! be used at runtime. Any function or variable not declared 'static' in ! the sources degrades the quality of inter-procedural optimization. To avoid this problem the compiler must assume that it sees the whole ! program when doing link-time optimization. Strictly speaking, the whole ! program is rarely visible even at link-time. Standard system libraries ! are usually linked dynamically or not provided with the link-time ! information. In GCC, the whole program option ('-fwhole-program') ! asserts that every function and variable defined in the current ! compilation unit is static, except for function 'main' (note: at link ! time, the current unit is the union of all objects compiled with LTO). ! Since some functions and variables need to be referenced externally, for ! example by another DSO or from an assembler file, GCC also provides the ! function and variable attribute 'externally_visible' which can be used ! to disable the effect of '-fwhole-program' on a specific symbol. The whole program mode assumptions are slightly more complex in C++, where inline functions in headers are put into _COMDAT_ sections. COMDAT function and variables can be defined by multiple object files ! and their bodies are unified at link-time and dynamic link-time. COMDAT ! functions are changed to local only when their address is not taken and ! thus un-sharing them with a library is not harmful. COMDAT variables ! always remain externally visible, however for readonly variables it is ! assumed that their initializers cannot be overwritten by a different ! value. ! GCC provides the function and variable attribute 'visibility' that can be used to specify the visibility of externally visible symbols (or ! alternatively an '-fdefault-visibility' command line option). ELF ! defines the 'default', 'protected', 'hidden' and 'internal' visibilities. ! The most commonly used is visibility is 'hidden'. It specifies that the symbol cannot be referenced from outside of the current shared ! library. Unfortunately, this information cannot be used directly by the ! link-time optimization in the compiler since the whole shared library ! also might contain non-LTO objects and those are not visible to the ! compiler. GCC solves this problem using linker plugins. A _linker plugin_ is an interface to the linker that allows an external program to claim the --- 41368,41425 ---- ===================================================================== Link-time optimization gives relatively minor benefits when used alone. ! The problem is that propagation of inter-procedural information does ! not work well across functions and variables that are called or ! referenced by other compilation units (such as from a dynamically ! linked library). We say that such functions and variables are ! _externally visible_. To make the situation even more difficult, many applications organize themselves as a set of shared libraries, and the default ELF visibility rules allow one to overwrite any externally visible symbol with a different symbol at runtime. This basically disables any optimizations ! across such functions and variables, because the compiler cannot be ! sure that the function body it is seeing is the same function body that ! will be used at runtime. Any function or variable not declared ! `static' in the sources degrades the quality of inter-procedural ! optimization. To avoid this problem the compiler must assume that it sees the whole ! program when doing link-time optimization. Strictly speaking, the ! whole program is rarely visible even at link-time. Standard system ! libraries are usually linked dynamically or not provided with the ! link-time information. In GCC, the whole program option ! (`-fwhole-program') asserts that every function and variable defined in ! the current compilation unit is static, except for function `main' ! (note: at link time, the current unit is the union of all objects ! compiled with LTO). Since some functions and variables need to be ! referenced externally, for example by another DSO or from an assembler ! file, GCC also provides the function and variable attribute ! `externally_visible' which can be used to disable the effect of ! `-fwhole-program' on a specific symbol. The whole program mode assumptions are slightly more complex in C++, where inline functions in headers are put into _COMDAT_ sections. COMDAT function and variables can be defined by multiple object files ! and their bodies are unified at link-time and dynamic link-time. ! COMDAT functions are changed to local only when their address is not ! taken and thus un-sharing them with a library is not harmful. COMDAT ! variables always remain externally visible, however for readonly ! variables it is assumed that their initializers cannot be overwritten ! by a different value. ! GCC provides the function and variable attribute `visibility' that can be used to specify the visibility of externally visible symbols (or ! alternatively an `-fdefault-visibility' command line option). ELF ! defines the `default', `protected', `hidden' and `internal' visibilities. ! The most commonly used is visibility is `hidden'. It specifies that the symbol cannot be referenced from outside of the current shared ! library. Unfortunately, this information cannot be used directly by ! the link-time optimization in the compiler since the whole shared ! library also might contain non-LTO objects and those are not visible to ! the compiler. GCC solves this problem using linker plugins. A _linker plugin_ is an interface to the linker that allows an external program to claim the *************** ownership of a given object file. The l *** 40967,41003 **** procedure by querying the plugin about the symbol table of the claimed objects and once the linking decisions are complete, the plugin is allowed to provide the final object file before the actual linking is ! made. The linker plugin obtains the symbol resolution information which ! specifies which symbols provided by the claimed objects are bound from ! the rest of a binary being linked. ! GCC is designed to be independent of the rest of the toolchain and aims ! to support linkers without plugin support. For this reason it does not ! use the linker plugin by default. Instead, the object files are ! examined by 'collect2' before being passed to the linker and objects ! found to have LTO sections are passed to 'lto1' first. This mode does ! not work for library archives. The decision on what object files from ! the archive are needed depends on the actual linking and thus GCC would ! have to implement the linker itself. The resolution information is ! missing too and thus GCC needs to make an educated guess based on ! '-fwhole-program'. Without the linker plugin GCC also assumes that ! symbols are declared 'hidden' and not referred by non-LTO code by default.  File: gccint.info, Node: Internal flags, Prev: WHOPR, Up: LTO ! 24.5 Internal flags controlling 'lto1' ====================================== ! The following flags are passed into 'lto1' and are not meant to be used directly from the command line. * -fwpa This option runs the serial part of the link-time optimizer performing the inter-procedural propagation (WPA mode). The compiler reads in summary information from all inputs and performs ! an analysis based on summary information only. It generates object ! files for subsequent runs of the link-time optimizer where individual object files are optimized using both summary information from the WPA mode and the actual function bodies. It then drives the LTRANS phase. --- 41427,41463 ---- procedure by querying the plugin about the symbol table of the claimed objects and once the linking decisions are complete, the plugin is allowed to provide the final object file before the actual linking is ! made. The linker plugin obtains the symbol resolution information ! which specifies which symbols provided by the claimed objects are bound ! from the rest of a binary being linked. ! GCC is designed to be independent of the rest of the toolchain and ! aims to support linkers without plugin support. For this reason it ! does not use the linker plugin by default. Instead, the object files ! are examined by `collect2' before being passed to the linker and ! objects found to have LTO sections are passed to `lto1' first. This ! mode does not work for library archives. The decision on what object ! files from the archive are needed depends on the actual linking and ! thus GCC would have to implement the linker itself. The resolution ! information is missing too and thus GCC needs to make an educated guess ! based on `-fwhole-program'. Without the linker plugin GCC also assumes ! that symbols are declared `hidden' and not referred by non-LTO code by default.  File: gccint.info, Node: Internal flags, Prev: WHOPR, Up: LTO ! 24.5 Internal flags controlling `lto1' ====================================== ! The following flags are passed into `lto1' and are not meant to be used directly from the command line. * -fwpa This option runs the serial part of the link-time optimizer performing the inter-procedural propagation (WPA mode). The compiler reads in summary information from all inputs and performs ! an analysis based on summary information only. It generates ! object files for subsequent runs of the link-time optimizer where individual object files are optimized using both summary information from the WPA mode and the actual function bodies. It then drives the LTRANS phase. *************** directly from the command line. *** 41007,41019 **** previous run of the LTO in WPA mode. In the LTRANS mode, LTO optimizes an object and produces the final assembly. ! * -fltrans-output-list=FILE This option specifies a file to which the ! names of LTRANS output files are written. This option is only ! meaningful in conjunction with '-fwpa'. ! * -fresolution=FILE This option specifies the linker resolution file. ! This option is only meaningful in conjunction with '-fwpa' and as ! option to pass through to the LTO linker plugin.  File: gccint.info, Node: Match and Simplify, Next: Funding, Prev: LTO, Up: Top --- 41467,41479 ---- previous run of the LTO in WPA mode. In the LTRANS mode, LTO optimizes an object and produces the final assembly. ! * -fltrans-output-list=FILE This option specifies a file to which ! the names of LTRANS output files are written. This option is only ! meaningful in conjunction with `-fwpa'. ! * -fresolution=FILE This option specifies the linker resolution ! file. This option is only meaningful in conjunction with `-fwpa' ! and as option to pass through to the LTO linker plugin.  File: gccint.info, Node: Match and Simplify, Next: Funding, Prev: LTO, Up: Top *************** File: gccint.info, Node: Match and Simp *** 41021,41031 **** 25 Match and Simplify ********************* ! The GIMPLE and GENERIC pattern matching project match-and-simplify tries ! to address several issues. 1. unify expression simplifications currently spread and duplicated ! over separate files like fold-const.c, gimple-fold.c and builtins.c 2. allow for a cheap way to implement building and simplifying non-trivial GIMPLE expressions, avoiding the need to go through building and simplifying GENERIC via fold_buildN and then --- 41481,41493 ---- 25 Match and Simplify ********************* ! The GIMPLE and GENERIC pattern matching project match-and-simplify ! tries to address several issues. 1. unify expression simplifications currently spread and duplicated ! over separate files like fold-const.c, gimple-fold.c and ! builtins.c ! 2. allow for a cheap way to implement building and simplifying non-trivial GIMPLE expressions, avoiding the need to go through building and simplifying GENERIC via fold_buildN and then *************** File: gccint.info, Node: GIMPLE API, N *** 41054,41080 **** tree, gimple_seq *, tree (*)(tree)) -- GIMPLE function: tree gimple_simplify (enum tree_code, tree, tree, tree, tree, gimple_seq *, tree (*)(tree)) ! -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree, ! tree, gimple_seq *, tree (*)(tree)) ! -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree, tree, tree, gimple_seq *, tree (*)(tree)) ! -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree, tree, tree, tree, gimple_seq *, tree (*)(tree)) The main GIMPLE API entry to the expression simplifications mimicing that of the GENERIC fold_{unary,binary,ternary} functions. thus providing n-ary overloads for operation or function. The additional arguments are a gimple_seq where built statements are ! inserted on (if 'NULL' then simplifications requiring new statements are ! not performed) and a valueization hook that can be used to tie simplifications to a SSA lattice. ! In addition to those APIs 'fold_stmt' is overloaded with a valueization ! hook: -- bool: fold_stmt (gimple_stmt_iterator *, tree (*)(tree)); ! Ontop of these a 'fold_buildN'-like API for GIMPLE is introduced: -- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum tree_code, tree, tree, tree (*valueize) (tree) = NULL); --- 41516,41542 ---- tree, gimple_seq *, tree (*)(tree)) -- GIMPLE function: tree gimple_simplify (enum tree_code, tree, tree, tree, tree, gimple_seq *, tree (*)(tree)) ! -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree, tree, gimple_seq *, tree (*)(tree)) ! -- GIMPLE function: tree gimple_simplify (enum built_in_function, tree, tree, tree, gimple_seq *, tree (*)(tree)) + -- GIMPLE function: tree gimple_simplify (enum built_in_function, + tree, tree, tree, tree, gimple_seq *, tree (*)(tree)) The main GIMPLE API entry to the expression simplifications mimicing that of the GENERIC fold_{unary,binary,ternary} functions. thus providing n-ary overloads for operation or function. The additional arguments are a gimple_seq where built statements are ! inserted on (if `NULL' then simplifications requiring new statements ! are not performed) and a valueization hook that can be used to tie simplifications to a SSA lattice. ! In addition to those APIs `fold_stmt' is overloaded with a ! valueization hook: -- bool: fold_stmt (gimple_stmt_iterator *, tree (*)(tree)); ! Ontop of these a `fold_buildN'-like API for GIMPLE is introduced: -- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum tree_code, tree, tree, tree (*valueize) (tree) = NULL); *************** hook: *** 41087,41102 **** built_in_function, tree, tree, tree (*valueize) (tree) = NULL); -- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum ! built_in_function, tree, tree, tree, tree (*valueize) (tree) = ! NULL); -- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum built_in_function, tree, tree, tree, tree, tree (*valueize) (tree) = NULL); -- GIMPLE function: tree gimple_convert (gimple_seq *, location_t, tree, tree); ! which is supposed to replace 'force_gimple_operand (fold_buildN (...), ! ...)' and calls to 'fold_convert'. Overloads without the 'location_t' argument exist. Built statements are inserted on the provided sequence and simplification is performed using the optional valueization hook. --- 41549,41564 ---- built_in_function, tree, tree, tree (*valueize) (tree) = NULL); -- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum ! built_in_function, tree, tree, tree, tree (*valueize) (tree) ! = NULL); -- GIMPLE function: tree gimple_build (gimple_seq *, location_t, enum built_in_function, tree, tree, tree, tree, tree (*valueize) (tree) = NULL); -- GIMPLE function: tree gimple_convert (gimple_seq *, location_t, tree, tree); ! which is supposed to replace `force_gimple_operand (fold_buildN (...), ! ...)' and calls to `fold_convert'. Overloads without the `location_t' argument exist. Built statements are inserted on the provided sequence and simplification is performed using the optional valueization hook. *************** an example from the match.pd file: *** 41115,41164 **** @0) This example contains all required parts of an expression ! simplification. A simplification is wrapped inside a '(simplify ...)' ! expression. That contains at least two operands - an expression that is ! matched with the GIMPLE or GENERIC IL and a replacement expression that ! is returned if the match was successful. ! Expressions have an operator ID, 'bit_and' in this case. Expressions ! can be lower-case tree codes with '_expr' stripped off or builtin ! function code names in all-caps, like 'BUILT_IN_SQRT'. ! '@n' denotes a so-called capture. It captures the operand and lets you ! refer to it in other places of the match-and-simplify. In the above ! example it is refered to in the replacement expression. Captures are ! '@' followed by a number or an identifier. (simplify (bit_xor @0 @0) { build_zero_cst (type); }) ! In this example '@0' is mentioned twice which constrains the matched expression to have two equal operands. This example also introduces operands written in C code. These can be used in the expression ! replacements and are supposed to evaluate to a tree node which has to be ! a valid GIMPLE operand (so you cannot generate expressions in C code). (simplify (trunc_mod integer_zerop@0 @1) (if (!integer_zerop (@1)) @0)) ! Here '@0' captures the first operand of the trunc_mod expression which ! is also predicated with 'integer_zerop'. Expression operands may be either expressions, predicates or captures. Captures can be unconstrained or capture expresions or predicates. This example introduces an optional operand of simplify, the ! if-expression. This condition is evaluated after the expression matched ! in the IL and is required to evaluate to true to enable the replacement ! expression in the second operand position. The expression operand of ! the 'if' is a standard C expression which may contain references to ! captures. The 'if' has an optional third operand which may contain the ! replacement expression that is enabled when the condition evaluates to ! false. ! A 'if' expression can be used to specify a common condition for multiple simplify patterns, avoiding the need to repeat that multiple times: --- 41577,41627 ---- @0) This example contains all required parts of an expression ! simplification. A simplification is wrapped inside a `(simplify ...)' ! expression. That contains at least two operands - an expression that ! is matched with the GIMPLE or GENERIC IL and a replacement expression ! that is returned if the match was successful. ! Expressions have an operator ID, `bit_and' in this case. Expressions ! can be lower-case tree codes with `_expr' stripped off or builtin ! function code names in all-caps, like `BUILT_IN_SQRT'. ! `@n' denotes a so-called capture. It captures the operand and lets ! you refer to it in other places of the match-and-simplify. In the ! above example it is refered to in the replacement expression. Captures ! are `@' followed by a number or an identifier. (simplify (bit_xor @0 @0) { build_zero_cst (type); }) ! In this example `@0' is mentioned twice which constrains the matched expression to have two equal operands. This example also introduces operands written in C code. These can be used in the expression ! replacements and are supposed to evaluate to a tree node which has to ! be a valid GIMPLE operand (so you cannot generate expressions in C ! code). (simplify (trunc_mod integer_zerop@0 @1) (if (!integer_zerop (@1)) @0)) ! Here `@0' captures the first operand of the trunc_mod expression which ! is also predicated with `integer_zerop'. Expression operands may be either expressions, predicates or captures. Captures can be unconstrained or capture expresions or predicates. This example introduces an optional operand of simplify, the ! if-expression. This condition is evaluated after the expression ! matched in the IL and is required to evaluate to true to enable the ! replacement expression in the second operand position. The expression ! operand of the `if' is a standard C expression which may contain ! references to captures. The `if' has an optional third operand which ! may contain the replacement expression that is enabled when the ! condition evaluates to false. ! A `if' expression can be used to specify a common condition for multiple simplify patterns, avoiding the need to repeat that multiple times: *************** times: *** 41171,41183 **** (minus (minus @0 @1) @0) (negate @1))) ! Note that 'if's in outer position do not have the optional else clause but instead have multiple then clauses. Ifs can be nested. ! There exists a 'switch' expression which can be used to chain ! conditions avoiding nesting 'if's too much: (simplify (simple_comparison @0 REAL_CST@1) --- 41634,41646 ---- (minus (minus @0 @1) @0) (negate @1))) ! Note that `if's in outer position do not have the optional else clause but instead have multiple then clauses. Ifs can be nested. ! There exists a `switch' expression which can be used to chain ! conditions avoiding nesting `if's too much: (simplify (simple_comparison @0 REAL_CST@1) *************** conditions avoiding nesting 'if's too mu *** 41203,41210 **** && ! HONOR_SNANS (@1)) { constant_boolean_node (cmp == NE_EXPR, type); })))) ! which has the second 'if' in the else operand of the first. The ! 'switch' expression takes 'if' expressions as operands (which may not have else clauses) and as a last operand a replacement expression which should be enabled by default if no other condition evaluated to true. --- 41666,41673 ---- && ! HONOR_SNANS (@1)) { constant_boolean_node (cmp == NE_EXPR, type); })))) ! which has the second `if' in the else operand of the first. The ! `switch' expression takes `if' expressions as operands (which may not have else clauses) and as a last operand a replacement expression which should be enabled by default if no other condition evaluated to true. *************** should be enabled by default if no other *** 41227,41245 **** }) #endif ! In the above example, '@2' captures the result of the expression '(addr ! @0)'. For outermost expression only its type can be captured, and the ! keyword 'type' is reserved for this purpose. The above example also ! gives a way to conditionalize patterns to only apply to 'GIMPLE' or ! 'GENERIC' by means of using the pre-defined preprocessor macros 'GIMPLE' ! and 'GENERIC' and using preprocessor directives. (simplify (bit_and:c integral_op_p@0 (bit_ior:c (bit_not @0) @1)) (bit_and @1 @0)) Here we introduce flags on match expressions. The flag used above, ! 'c', denotes that the expression should be also matched commutated. Thus the above match expression is really the following four match expressions: --- 41690,41708 ---- }) #endif ! In the above example, `@2' captures the result of the expression ! `(addr @0)'. For outermost expression only its type can be captured, ! and the keyword `type' is reserved for this purpose. The above example ! also gives a way to conditionalize patterns to only apply to `GIMPLE' ! or `GENERIC' by means of using the pre-defined preprocessor macros ! `GIMPLE' and `GENERIC' and using preprocessor directives. (simplify (bit_and:c integral_op_p@0 (bit_ior:c (bit_not @0) @1)) (bit_and @1 @0)) Here we introduce flags on match expressions. The flag used above, ! `c', denotes that the expression should be also matched commutated. Thus the above match expression is really the following four match expressions: *************** expressions: *** 41252,41266 **** before matching, so for example constant operands always come second in commutative expressions. ! The second supported flag is 's' which tells the code generator to fail ! the pattern if the expression marked with 's' does have more than one ! use. For example in (simplify (pointer_plus (pointer_plus:s @0 @1) @3) (pointer_plus @0 (plus @1 @3))) ! this avoids the association if '(pointer_plus @0 @1)' is used outside of the matched expression and thus it would stay live and not trivially removed by dead code elimination. --- 41715,41729 ---- before matching, so for example constant operands always come second in commutative expressions. ! The second supported flag is `s' which tells the code generator to ! fail the pattern if the expression marked with `s' does have more than ! one use. For example in (simplify (pointer_plus (pointer_plus:s @0 @1) @3) (pointer_plus @0 (plus @1 @3))) ! this avoids the association if `(pointer_plus @0 @1)' is used outside of the matched expression and thus it would stay live and not trivially removed by dead code elimination. *************** removed by dead code elimination. *** 41271,41278 **** (op @0 integer_zerop) @0)) ! A 'for' expression can be used to repeat a pattern for each operator ! specified, substituting 'op'. 'for' can be nested and a 'for' can have multiple operators to iterate. (for opa (plus minus) --- 41734,41741 ---- (op @0 integer_zerop) @0)) ! A `for' expression can be used to repeat a pattern for each operator ! specified, substituting `op'. `for' can be nested and a `for' can have multiple operators to iterate. (for opa (plus minus) *************** multiple operators to iterate. *** 41280,41303 **** (for opc (plus minus) (simplify... ! In this example the pattern will be repeated four times with 'opa, opb, ! opc' being 'plus, minus, plus', 'plus, minus, minus', 'minus, plus, ! plus', 'minus, plus, minus'. ! To avoid repeating operator lists in 'for' you can name them via (define_operator_list pmm plus minus mult) ! and use them in 'for' operator lists where they get expanded. (for opa (pmm trunc_div) (simplify... ! So this example iterates over 'plus', 'minus', 'mult' and 'trunc_div'. Using operator lists can also remove the need to explicitely write a ! 'for'. All operator list uses that appear in a 'simplify' or 'match' ! pattern in operator positions will implicitely be added to a new 'for'. For example (define_operator_list SQRT BUILT_IN_SQRTF BUILT_IN_SQRT BUILT_IN_SQRTL) --- 41743,41766 ---- (for opc (plus minus) (simplify... ! In this example the pattern will be repeated four times with `opa, ! opb, opc' being `plus, minus, plus', `plus, minus, minus', `minus, ! plus, plus', `minus, plus, minus'. ! To avoid repeating operator lists in `for' you can name them via (define_operator_list pmm plus minus mult) ! and use them in `for' operator lists where they get expanded. (for opa (pmm trunc_div) (simplify... ! So this example iterates over `plus', `minus', `mult' and `trunc_div'. Using operator lists can also remove the need to explicitely write a ! `for'. All operator list uses that appear in a `simplify' or `match' ! pattern in operator positions will implicitely be added to a new `for'. For example (define_operator_list SQRT BUILT_IN_SQRTF BUILT_IN_SQRT BUILT_IN_SQRTL) *************** For example *** 41314,41325 **** (SQRT (POW @0 @1)) (POW (abs @0) (mult @1 { built_real (TREE_TYPE (@1), dconsthalf); })))) ! 'for's and operator lists can include the special identifier 'null' that matches nothing and can never be generated. This can be used to ! pad an operator list so that it has a standard form, even if there isn't ! a suitable operator for every form. ! Another building block are 'with' expressions in the result expression which nest the generated code in a new C block followed by its argument: (simplify --- 41777,41788 ---- (SQRT (POW @0 @1)) (POW (abs @0) (mult @1 { built_real (TREE_TYPE (@1), dconsthalf); })))) ! `for's and operator lists can include the special identifier `null' that matches nothing and can never be generated. This can be used to ! pad an operator list so that it has a standard form, even if there ! isn't a suitable operator for every form. ! Another building block are `with' expressions in the result expression which nest the generated code in a new C block followed by its argument: (simplify *************** which nest the generated code in a new C *** 41327,41363 **** (with { tree utype = unsigned_type_for (type); } (convert (mult (convert:utype @0) (convert:utype @1))))) ! This allows code nested in the 'with' to refer to the declared variables. In the above case we use the feature to specify the type of ! a generated expression with the ':type' syntax where 'type' needs to be ! an identifier that refers to the desired type. Usually the types of the ! generated result expressions are determined from the context, but sometimes like in the above case it is required that you specify them explicitely. As intermediate conversions are often optional there is a way to avoid the need to repeat patterns both with and without such conversions. ! Namely you can mark a conversion as being optional with a '?': (simplify (eq (convert@0 @1) (convert? @2)) (eq @1 (convert @2))) ! which will match both '(eq (convert @1) (convert @2))' and '(eq (convert @1) @2)'. The optional converts are supposed to be all either ! present or not, thus '(eq (convert? @1) (convert? @2))' will result in two patterns only. If you want to match all four combinations you have ! access to two additional conditional converts as in '(eq (convert1? @1) (convert2? @2))'. Predicates available from the GCC middle-end need to be made available ! explicitely via 'define_predicates': (define_predicates integer_onep integer_zerop integer_all_onesp) You can also define predicates using the pattern matching language and ! the 'match' form: (match negate_expr_p INTEGER_CST --- 41790,41826 ---- (with { tree utype = unsigned_type_for (type); } (convert (mult (convert:utype @0) (convert:utype @1))))) ! This allows code nested in the `with' to refer to the declared variables. In the above case we use the feature to specify the type of ! a generated expression with the `:type' syntax where `type' needs to be ! an identifier that refers to the desired type. Usually the types of ! the generated result expressions are determined from the context, but sometimes like in the above case it is required that you specify them explicitely. As intermediate conversions are often optional there is a way to avoid the need to repeat patterns both with and without such conversions. ! Namely you can mark a conversion as being optional with a `?': (simplify (eq (convert@0 @1) (convert? @2)) (eq @1 (convert @2))) ! which will match both `(eq (convert @1) (convert @2))' and `(eq (convert @1) @2)'. The optional converts are supposed to be all either ! present or not, thus `(eq (convert? @1) (convert? @2))' will result in two patterns only. If you want to match all four combinations you have ! access to two additional conditional converts as in `(eq (convert1? @1) (convert2? @2))'. Predicates available from the GCC middle-end need to be made available ! explicitely via `define_predicates': (define_predicates integer_onep integer_zerop integer_all_onesp) You can also define predicates using the pattern matching language and ! the `match' form: (match negate_expr_p INTEGER_CST *************** the 'match' form: *** 41366,41376 **** (match negate_expr_p (negate @0)) ! This shows that for 'match' expressions there is 't' available which captures the outermost expression (something not possible in the ! 'simplify' context). As you can see 'match' has an identifier as first operand which is how you refer to the predicate in patterns. Multiple ! 'match' for the same identifier add additional cases where the predicate matches. Predicates can also match an expression in which case you need to --- 41829,41839 ---- (match negate_expr_p (negate @0)) ! This shows that for `match' expressions there is `t' available which captures the outermost expression (something not possible in the ! `simplify' context). As you can see `match' has an identifier as first operand which is how you refer to the predicate in patterns. Multiple ! `match' for the same identifier add additional cases where the predicate matches. Predicates can also match an expression in which case you need to *************** to free software developers--the Free So *** 41408,41415 **** The way to convince distributors to do this is to demand it and expect it from them. So when you compare distributors, judge them partly by ! how much they give to free software development. Show distributors they ! must compete to be the one who gives the most. To make this approach work, you must insist on numbers that you can compare, such as, "We will donate ten dollars to the Frobnitz project --- 41871,41878 ---- The way to convince distributors to do this is to demand it and expect it from them. So when you compare distributors, judge them partly by ! how much they give to free software development. Show distributors ! they must compete to be the one who gives the most. To make this approach work, you must insist on numbers that you can compare, such as, "We will donate ten dollars to the Frobnitz project *************** for comparison. *** 41419,41426 **** Even a precise fraction "of the profits from this disk" is not very meaningful, since creative accounting and unrelated business decisions ! can greatly alter what fraction of the sales price counts as profit. If ! the price you pay is $50, ten percent of the profit is probably less than a dollar; it might be a few cents, or nothing at all. Some redistributors do development work themselves. This is useful --- 41882,41889 ---- Even a precise fraction "of the profits from this disk" is not very meaningful, since creative accounting and unrelated business decisions ! can greatly alter what fraction of the sales price counts as profit. ! If the price you pay is $50, ten percent of the profit is probably less than a dollar; it might be a few cents, or nothing at all. Some redistributors do development work themselves. This is useful *************** difference than others. For example, ma *** 41430,41437 **** a program contributes very little; maintaining the standard version of a program for the whole community contributes much. Easy new ports contribute little, since someone else would surely do them; difficult ! ports such as adding a new CPU to the GNU Compiler Collection contribute ! more; major new features or packages contribute the most. By establishing the idea that supporting further development is "the proper thing to do" when distributing free software for a fee, we can --- 41893,41900 ---- a program contributes very little; maintaining the standard version of a program for the whole community contributes much. Easy new ports contribute little, since someone else would surely do them; difficult ! ports such as adding a new CPU to the GNU Compiler Collection ! contribute more; major new features or packages contribute the most. By establishing the idea that supporting further development is "the proper thing to do" when distributing free software for a fee, we can *************** now widely used; though these systems ar *** 41455,41462 **** they are more accurately called GNU/Linux systems. For more information, see: ! !  File: gccint.info, Node: Copying, Next: GNU Free Documentation License, Prev: GNU Project, Up: Top --- 41918,41925 ---- they are more accurately called GNU/Linux systems. For more information, see: ! `http://www.gnu.org/' ! `http://www.gnu.org/gnu/linux-and-gnu.html'  File: gccint.info, Node: Copying, Next: GNU Free Documentation License, Prev: GNU Project, Up: Top *************** GNU General Public License *** 41466,41472 **** Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 41929,41935 ---- Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU General Public License for most of o *** 41486,41512 **** any other work released this way by its authors. You can apply it to your programs, too. ! When we speak of free software, we are referring to freedom, not price. ! Our General Public Licenses are designed to make sure that you have the ! freedom to distribute copies of free software (and charge for them if ! you wish), that you receive source code or can get it if you want it, ! that you can change the software or use pieces of it in new free ! programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you have ! certain responsibilities if you distribute copies of the software, or if ! you modify it: responsibilities to respect the freedom of others. ! For example, if you distribute copies of such a program, whether gratis ! or for a fee, you must pass on to the recipients the same freedoms that ! you received. You must make sure that they, too, receive or can get the ! source code. And you must show them these terms so they know their ! rights. ! Developers that use the GNU GPL protect your rights with two steps: (1) ! assert copyright on the software, and (2) offer you this License giving ! you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and --- 41949,41975 ---- any other work released this way by its authors. You can apply it to your programs, too. ! When we speak of free software, we are referring to freedom, not ! price. Our General Public Licenses are designed to make sure that you ! have the freedom to distribute copies of free software (and charge for ! them if you wish), that you receive source code or can get it if you ! want it, that you can change the software or use pieces of it in new ! free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you ! have certain responsibilities if you distribute copies of the software, ! or if you modify it: responsibilities to respect the freedom of others. ! For example, if you distribute copies of such a program, whether ! gratis or for a fee, you must pass on to the recipients the same ! freedoms that you received. You must make sure that they, too, receive ! or can get the source code. And you must show them these terms so they ! know their rights. ! Developers that use the GNU GPL protect your rights with two steps: ! (1) assert copyright on the software, and (2) offer you this License ! giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and *************** changed, so that their problems will not *** 41515,41529 **** authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the manufacturer ! can do so. This is fundamentally incompatible with the aim of ! protecting users' freedom to change the software. The systematic ! pattern of such abuse occurs in the area of products for individuals to ! use, which is precisely where it is most unacceptable. Therefore, we ! have designed this version of the GPL to prohibit the practice for those ! products. If such problems arise substantially in other domains, we ! stand ready to extend this provision to those domains in future versions ! of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of --- 41978,41993 ---- authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the ! manufacturer can do so. This is fundamentally incompatible with the ! aim of protecting users' freedom to change the software. The ! systematic pattern of such abuse occurs in the area of products for ! individuals to use, which is precisely where it is most unacceptable. ! Therefore, we have designed this version of the GPL to prohibit the ! practice for those products. If such problems arise substantially in ! other domains, we stand ready to extend this provision to those domains ! in future versions of the GPL, as needed to protect the freedom of ! users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of *************** TERMS AND CONDITIONS *** 41560,41567 **** To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it on ! a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. --- 42024,42031 ---- To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it ! on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. *************** TERMS AND CONDITIONS *** 41575,41582 **** to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may convey ! the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. --- 42039,42046 ---- to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may ! convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. *************** TERMS AND CONDITIONS *** 41584,41591 **** 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any non-source ! form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in --- 42048,42055 ---- 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any ! non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in *************** TERMS AND CONDITIONS *** 41596,41605 **** The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work with ! that Major Component, or to implement a Standard Interface for ! which an implementation is available to the public in source code ! form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code --- 42060,42069 ---- The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work ! with that Major Component, or to implement a Standard Interface ! for which an implementation is available to the public in source ! code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code *************** TERMS AND CONDITIONS *** 41607,41621 **** The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including scripts ! to control those activities. However, it does not include the ! work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files associated ! with source files for the work, and the source code for shared ! libraries and dynamically linked subprograms that the work is ! specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. --- 42071,42085 ---- The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including ! scripts to control those activities. However, it does not include ! the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files ! associated with source files for the work, and the source code for ! shared libraries and dynamically linked subprograms that the work ! is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. *************** TERMS AND CONDITIONS *** 41632,41653 **** copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, given ! its content, constitutes a covered work. This License acknowledges ! your rights of fair use or other equivalent, as provided by ! copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for you, ! or provide you with facilities for running those works, provided ! that you comply with the terms of this License in conveying all ! material for which you do not control copyright. Those thus making ! or running the covered works for you must do so exclusively on your ! behalf, under your direction and control, on terms that prohibit ! them from making any copies of your copyrighted material outside ! their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section --- 42096,42117 ---- copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, ! given its content, constitutes a covered work. This License ! acknowledges your rights of fair use or other equivalent, as ! provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for ! you, or provide you with facilities for running those works, ! provided that you comply with the terms of this License in ! conveying all material for which you do not control copyright. ! Those thus making or running the covered works for you must do so ! exclusively on your behalf, under your direction and control, on ! terms that prohibit them from making any copies of your ! copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section *************** TERMS AND CONDITIONS *** 41664,41671 **** When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention to ! limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. --- 42128,42135 ---- When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention ! to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. *************** TERMS AND CONDITIONS *** 41735,41742 **** b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for as ! long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a --- 42199,42206 ---- b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for ! as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a *************** TERMS AND CONDITIONS *** 41746,41776 **** to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of the ! written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access to ! the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated by ! you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to the ! object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long as ! needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. --- 42210,42241 ---- to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of ! the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access ! to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated ! by you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to ! the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long ! as needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. + A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. *************** TERMS AND CONDITIONS *** 41778,41785 **** A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product is ! a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the --- 42243,42250 ---- A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product ! is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the *************** TERMS AND CONDITIONS *** 41810,41820 **** The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or installed ! by the recipient, or for the User Product in which it has been ! modified or installed. Access to a network may be denied when the ! modification itself materially and adversely affects the operation ! of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information --- 42275,42285 ---- The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or ! installed by the recipient, or for the User Product in which it ! has been modified or installed. Access to a network may be denied ! when the modification itself materially and adversely affects the ! operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information *************** TERMS AND CONDITIONS *** 41844,41851 **** Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License with ! terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or --- 42309,42316 ---- Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License ! with terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or *************** TERMS AND CONDITIONS *** 41855,41862 **** Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be marked ! in reasonable ways as different from the original version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or --- 42320,42328 ---- Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be ! marked in reasonable ways as different from the original ! version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or *************** TERMS AND CONDITIONS *** 41875,41884 **** you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or conveying ! under this License, you may add to a covered work material governed ! by the terms of that license document, provided that the further ! restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the --- 42341,42351 ---- you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or ! conveying under this License, you may add to a covered work ! material governed by the terms of that license document, provided ! that the further restriction does not survive such relicensing or ! conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the *************** TERMS AND CONDITIONS *** 41894,41906 **** You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under the ! third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 42361,42373 ---- You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under ! the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** TERMS AND CONDITIONS *** 41912,41921 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, you do not qualify to receive new licenses ! for the same material under section 10. 9. Acceptance Not Required for Having Copies. --- 42379,42388 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, you do not qualify to receive new ! licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. *************** TERMS AND CONDITIONS *** 41929,41935 **** by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and --- 42396,42402 ---- by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and *************** TERMS AND CONDITIONS *** 41943,41963 **** covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to possession ! of the Corresponding Source of the work from the predecessor in ! interest, if the predecessor has it or can get it with reasonable ! efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for exercise ! of rights granted under this License, and you may not initiate ! litigation (including a cross-claim or counterclaim in a lawsuit) ! alleging that any patent claim is infringed by making, using, ! selling, offering for sale, or importing the Program or any portion ! of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. --- 42410,42430 ---- covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to ! possession of the Corresponding Source of the work from the ! predecessor in interest, if the predecessor has it or can get it ! with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for ! exercise of rights granted under this License, and you may not ! initiate litigation (including a cross-claim or counterclaim in a ! lawsuit) alleging that any patent claim is infringed by making, ! using, selling, offering for sale, or importing the Program or any ! portion of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. *************** TERMS AND CONDITIONS *** 41977,41991 **** Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its contributor ! version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To "grant" ! such a patent license to a party means to make such an agreement or ! commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available --- 42444,42458 ---- Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its ! contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To ! "grant" such a patent license to a party means to make such an ! agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available *************** TERMS AND CONDITIONS *** 42015,42049 **** conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under which ! you make payment to the third party based on the extent of your ! activity of conveying the work, and under which the third party ! grants, to any of the parties who would receive the covered work ! from you, a discriminatory patent license (a) in connection with ! copies of the covered work conveyed by you (or copies made from ! those copies), or (b) primarily for and in connection with specific ! products or compilations that contain the covered work, unless you ! entered into that arrangement, or that patent license was granted, ! prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, agreement ! or otherwise) that contradict the conditions of this License, they ! do not excuse you from the conditions of this License. If you ! cannot convey a covered work so as to satisfy simultaneously your ! obligations under this License and any other pertinent obligations, ! then as a consequence you may not convey it at all. For example, ! if you agree to terms that obligate you to collect a royalty for ! further conveying from those to whom you convey the Program, the ! only way you could satisfy both those terms and this License would ! be to refrain entirely from conveying the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed --- 42482,42517 ---- conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under ! which you make payment to the third party based on the extent of ! your activity of conveying the work, and under which the third ! party grants, to any of the parties who would receive the covered ! work from you, a discriminatory patent license (a) in connection ! with copies of the covered work conveyed by you (or copies made ! from those copies), or (b) primarily for and in connection with ! specific products or compilations that contain the covered work, ! unless you entered into that arrangement, or that patent license ! was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, ! agreement or otherwise) that contradict the conditions of this ! License, they do not excuse you from the conditions of this ! License. If you cannot convey a covered work so as to satisfy ! simultaneously your obligations under this License and any other ! pertinent obligations, then as a consequence you may not convey it ! at all. For example, if you agree to terms that obligate you to ! collect a royalty for further conveying from those to whom you ! convey the Program, the only way you could satisfy both those ! terms and this License would be to refrain entirely from conveying ! the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed *************** TERMS AND CONDITIONS *** 42054,42074 **** General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. Such ! new versions will be similar in spirit to the present version, but ! may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the Free ! Software Foundation. If the Program does not specify a version ! number of the GNU General Public License, you may choose any ! version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that --- 42522,42543 ---- General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. ! Such new versions will be similar in spirit to the present ! version, but may differ in detail to address new problems or ! concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the ! Free Software Foundation. If the Program does not specify a ! version number of the GNU General Public License, you may choose ! any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that *************** TERMS AND CONDITIONS *** 42080,42103 **** author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR ! DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD --- 42549,42572 ---- author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU ! FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD *************** TERMS AND CONDITIONS *** 42105,42111 **** PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, --- 42574,42580 ---- PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, *************** TERMS AND CONDITIONS *** 42114,42119 **** --- 42583,42589 ---- connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. + END OF TERMS AND CONDITIONS =========================== *************** possible use to the public, the best way *** 42125,42133 **** free software which everyone can redistribute and change under these terms. ! To do so, attach the following notices to the program. It is safest to ! attach them to the start of each source file to most effectively state ! the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES. --- 42595,42603 ---- free software which everyone can redistribute and change under these terms. ! To do so, attach the following notices to the program. It is safest ! to attach them to the start of each source file to most effectively ! state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES. *************** the exclusion of warranty; and each file *** 42144,42163 **** General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. ! If the program does terminal interaction, make it output a short notice ! like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type 'show c' for details. ! The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". --- 42614,42633 ---- General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see `http://www.gnu.org/licenses/'. Also add information on how to contact you by electronic and paper mail. ! If the program does terminal interaction, make it output a short ! notice like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type `show c' for details. ! The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". *************** use an "about box". *** 42165,42178 **** You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read .  File: gccint.info, Node: GNU Free Documentation License, Next: Contributors, Prev: Copying, Up: Top --- 42635,42648 ---- You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see `http://www.gnu.org/licenses/'. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.  File: gccint.info, Node: GNU Free Documentation License, Next: Contributors, Prev: Copying, Up: Top *************** GNU Free Documentation License *** 42183,42189 **** Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 42653,42659 ---- Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU Free Documentation License *** 42208,42228 **** free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. We ! recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it can ! be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You accept ! the license if you copy, modify or distribute the work in a way ! requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with --- 42678,42698 ---- free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. ! We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it ! can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You ! accept the license if you copy, modify or distribute the work in a ! way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with *************** GNU Free Documentation License *** 42240,42251 **** regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in the ! notice that says that the Document is released under this License. ! If a section does not fit the above definition of Secondary then it ! is not allowed to be designated as Invariant. The Document may ! contain zero Invariant Sections. If the Document does not identify ! any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice --- 42710,42721 ---- regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in ! the notice that says that the Document is released under this ! License. If a section does not fit the above definition of ! Secondary then it is not allowed to be designated as Invariant. ! The Document may contain zero Invariant Sections. If the Document ! does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice *************** GNU Free Documentation License *** 42256,42282 **** A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images composed ! of pixels) generic paint programs or (for drawings) some widely ! available drawing editor, and that is suitable for input to text ! formatters or for automatic translation to a variety of formats ! suitable for input to text formatters. A copy made in an otherwise ! Transparent file format whose markup, or absence of markup, has ! been arranged to thwart or discourage subsequent modification by ! readers is not Transparent. An image format is not Transparent if ! used for any substantial amount of text. A copy that is not ! "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and standard-conforming ! simple HTML, PostScript or PDF designed for human modification. ! Examples of transparent image formats include PNG, XCF and JPG. ! Opaque formats include proprietary formats that can be read and ! edited only by proprietary word processors, SGML or XML for which ! the DTD and/or processing tools are not generally available, and ! the machine-generated HTML, PostScript or PDF produced by some word ! processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the --- 42726,42752 ---- A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images ! composed of pixels) generic paint programs or (for drawings) some ! widely available drawing editor, and that is suitable for input to ! text formatters or for automatic translation to a variety of ! formats suitable for input to text formatters. A copy made in an ! otherwise Transparent file format whose markup, or absence of ! markup, has been arranged to thwart or discourage subsequent ! modification by readers is not Transparent. An image format is ! not Transparent if used for any substantial amount of text. A ! copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and ! standard-conforming simple HTML, PostScript or PDF designed for ! human modification. Examples of transparent image formats include ! PNG, XCF and JPG. Opaque formats include proprietary formats that ! can be read and edited only by proprietary word processors, SGML or ! XML for which the DTD and/or processing tools are not generally ! available, and the machine-generated HTML, PostScript or PDF ! produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the *************** GNU Free Documentation License *** 42314,42321 **** may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow the ! conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. --- 42784,42791 ---- may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow ! the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. *************** GNU Free Documentation License *** 42329,42339 **** these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the title ! equally prominent and visible. You may add other material on the ! covers in addition. Copying with changes limited to the covers, as ! long as they preserve the title of the Document and satisfy these ! conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit --- 42799,42810 ---- these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the ! title equally prominent and visible. You may add other material ! on the covers in addition. Copying with changes limited to the ! covers, as long as they preserve the title of the Document and ! satisfy these conditions, can be treated as verbatim copying in ! other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit *************** GNU Free Documentation License *** 42341,42379 **** adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a machine-readable ! Transparent copy along with each Opaque copy, or state in or with ! each Opaque copy a computer-network location from which the general ! network-using public has access to download using public-standard ! network protocols a complete Transparent copy of the Document, free ! of added material. If you use the latter option, you must take ! reasonably prudent steps, when you begin distribution of Opaque ! copies in quantity, to ensure that this Transparent copy will ! remain thus accessible at the stated location until at least one ! year after the last time you distribute an Opaque copy (directly or ! through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of copies, ! to give them a chance to provide you with an updated version of the ! Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with the ! Modified Version filling the role of the Document, thus licensing ! distribution and modification of the Modified Version to whoever ! possesses a copy of it. In addition, you must do these things in ! the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of previous ! versions (which should, if there were any, be listed in the ! History section of the Document). You may use the same title ! as a previous version if the original publisher of that ! version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in --- 42812,42851 ---- adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a ! machine-readable Transparent copy along with each Opaque copy, or ! state in or with each Opaque copy a computer-network location from ! which the general network-using public has access to download ! using public-standard network protocols a complete Transparent ! copy of the Document, free of added material. If you use the ! latter option, you must take reasonably prudent steps, when you ! begin distribution of Opaque copies in quantity, to ensure that ! this Transparent copy will remain thus accessible at the stated ! location until at least one year after the last time you ! distribute an Opaque copy (directly or through your agents or ! retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of ! copies, to give them a chance to provide you with an updated ! version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with ! the Modified Version filling the role of the Document, thus ! licensing distribution and modification of the Modified Version to ! whoever possesses a copy of it. In addition, you must do these ! things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of ! previous versions (which should, if there were any, be listed ! in the History section of the Document). You may use the ! same title as a previous version if the original publisher of ! that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in *************** GNU Free Documentation License *** 42403,42432 **** I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on the ! Title Page. If there is no section Entitled "History" in the ! Document, create one stating the title, year, authors, and ! publisher of the Document as given on its Title Page, then add ! an item describing the Modified Version as stated in the ! previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in the ! "History" section. You may omit a network location for a work ! that was published at least four years before the Document ! itself, or if the original publisher of the version it refers ! to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the section ! all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, unaltered ! in their text and in their titles. Section numbers or the ! equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. --- 42875,42905 ---- I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on ! the Title Page. If there is no section Entitled "History" in ! the Document, create one stating the title, year, authors, ! and publisher of the Document as given on its Title Page, ! then add an item describing the Modified Version as stated in ! the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in ! the "History" section. You may omit a network location for a ! work that was published at least four years before the ! Document itself, or if the original publisher of the version ! it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the ! section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, ! unaltered in their text and in their titles. Section numbers ! or the equivalent are not considered part of the section ! titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. *************** GNU Free Documentation License *** 42439,42449 **** If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option designate ! some or all of these sections as invariant. To do this, add their ! titles to the list of Invariant Sections in the Modified Version's ! license notice. These titles must be distinct from any other ! section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various --- 42912,42922 ---- If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option ! designate some or all of these sections as invariant. To do this, ! add their titles to the list of Invariant Sections in the Modified ! Version's license notice. These titles must be distinct from any ! other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various *************** GNU Free Documentation License *** 42452,42466 **** definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end of ! the list of Cover Texts in the Modified Version. Only one passage ! of Front-Cover Text and one of Back-Cover Text may be added by (or ! through arrangements made by) any one entity. If the Document ! already includes a cover text for the same cover, previously added ! by you or by arrangement made by the same entity you are acting on ! behalf of, you may not add another; but you may replace the old ! one, on explicit permission from the previous publisher that added ! the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to --- 42925,42939 ---- definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end ! of the list of Cover Texts in the Modified Version. Only one ! passage of Front-Cover Text and one of Back-Cover Text may be ! added by (or through arrangements made by) any one entity. If the ! Document already includes a cover text for the same cover, ! previously added by you or by arrangement made by the same entity ! you are acting on behalf of, you may not add another; but you may ! replace the old one, on explicit permission from the previous ! publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to *************** GNU Free Documentation License *** 42470,42477 **** You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination all ! of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. --- 42943,42950 ---- You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination ! all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. *************** GNU Free Documentation License *** 42498,42517 **** documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the documents ! in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow this ! License in all other respects regarding verbatim copying of that ! document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of a ! storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this --- 42971,42990 ---- documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the ! documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow ! this License in all other respects regarding verbatim copying of ! that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of ! a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this *************** GNU Free Documentation License *** 42556,42563 **** However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 43029,43036 ---- However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** GNU Free Documentation License *** 42569,42601 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, receipt of a copy of some or all of the ! same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! . Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If the ! Document does not specify a version number of this License, you may ! choose any version ever published (not as a draft) by the Free ! Software Foundation. If the Document specifies that a proxy can ! decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also --- 43042,43074 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, receipt of a copy of some or all of ! the same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! `http://www.gnu.org/copyleft/'. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If ! the Document does not specify a version number of this License, ! you may choose any version ever published (not as a draft) by the ! Free Software Foundation. If the Document specifies that a proxy ! can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also *************** GNU Free Documentation License *** 42625,42630 **** --- 43098,43104 ---- site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. + ADDENDUM: How to use this License for your documents ==================================================== *************** notices just after the title page: *** 42641,42647 **** Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, ! replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts --- 43115,43121 ---- Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, ! replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts *************** combination of the three, merge those tw *** 42652,42660 **** situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of free ! software license, such as the GNU General Public License, to permit ! their use in free software.  File: gccint.info, Node: Contributors, Next: Option Index, Prev: GNU Free Documentation License, Up: Top --- 43126,43134 ---- situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of ! free software license, such as the GNU General Public License, to ! permit their use in free software.  File: gccint.info, Node: Contributors, Next: Option Index, Prev: GNU Free Documentation License, Up: Top *************** File: gccint.info, Node: Contributors, *** 42662,42670 **** Contributors to GCC ******************* ! The GCC project would like to thank its many contributors. Without them ! the project would not have been nearly as successful as it has been. ! Any omissions in this list are accidental. Feel free to contact or if you have been left out or some of your contributions are not listed. Please keep this list in alphabetical order. --- 43136,43144 ---- Contributors to GCC ******************* ! The GCC project would like to thank its many contributors. Without ! them the project would not have been nearly as successful as it has ! been. Any omissions in this list are accidental. Feel free to contact or if you have been left out or some of your contributions are not listed. Please keep this list in alphabetical order. *************** alphabetical order. *** 42799,42805 **** * The GNU Classpath project for all of their merged runtime code. * Nick Clifton for arm, mcore, fr30, v850, m32r, msp430 rx work, ! '--help', and other random hacking. * Michael Cook for libstdc++ cleanup patches to reduce warnings. --- 43273,43279 ---- * The GNU Classpath project for all of their merged runtime code. * Nick Clifton for arm, mcore, fr30, v850, m32r, msp430 rx work, ! `--help', and other random hacking. * Michael Cook for libstdc++ cleanup patches to reduce warnings. *************** alphabetical order. *** 42819,42826 **** * Paul Dale for his work to add uClinux platform support to the m68k backend. ! * Dario Dariol contributed the four varieties of sample programs that ! print a copy of their source. * Russell Davidson for fstream and stringstream fixes in libstdc++. --- 43293,43300 ---- * Paul Dale for his work to add uClinux platform support to the m68k backend. ! * Dario Dariol contributed the four varieties of sample programs ! that print a copy of their source. * Russell Davidson for fstream and stringstream fixes in libstdc++. *************** alphabetical order. *** 42835,42853 **** * Gabriel Dos Reis for contributions to G++, contributions and maintenance of GCC diagnostics infrastructure, libstdc++-v3, ! including 'valarray<>', 'complex<>', maintaining the numerics ! library (including that pesky '' :-) and keeping up-to-date ! anything to do with numbers. * Ulrich Drepper for his work on glibc, testing of GCC using glibc, ! ISO C99 support, CFG dumping support, etc., plus support of the C++ ! runtime libraries including for all kinds of C interface issues, ! contributing and maintaining 'complex<>', sanity checking and ! disbursement, configuration architecture, libio maintenance, and ! early math work. * Franc,ois Dumont for his work on libstdc++-v3, especially ! maintaining and improving 'debug-mode' and associative and unordered containers. * Zdenek Dvorak for a new loop unroller and various fixes. --- 43309,43327 ---- * Gabriel Dos Reis for contributions to G++, contributions and maintenance of GCC diagnostics infrastructure, libstdc++-v3, ! including `valarray<>', `complex<>', maintaining the numerics ! library (including that pesky `' :-) and keeping ! up-to-date anything to do with numbers. * Ulrich Drepper for his work on glibc, testing of GCC using glibc, ! ISO C99 support, CFG dumping support, etc., plus support of the ! C++ runtime libraries including for all kinds of C interface ! issues, contributing and maintaining `complex<>', sanity checking ! and disbursement, configuration architecture, libio maintenance, ! and early math work. * Franc,ois Dumont for his work on libstdc++-v3, especially ! maintaining and improving `debug-mode' and associative and unordered containers. * Zdenek Dvorak for a new loop unroller and various fixes. *************** alphabetical order. *** 42899,42908 **** * Peter Gerwinski for various bug fixes and the Pascal front end. * Kaveh R. Ghazi for his direction via the steering committee, ! amazing work to make '-W -Wall -W* -Werror' useful, and testing GCC ! on a plethora of platforms. Kaveh extends his gratitude to the ! CAIP Center at Rutgers University for providing him with computing ! resources to work on Free Software from the late 1980s to 2010. * John Gilmore for a donation to the FSF earmarked improving GNU Java. --- 43373,43383 ---- * Peter Gerwinski for various bug fixes and the Pascal front end. * Kaveh R. Ghazi for his direction via the steering committee, ! amazing work to make `-W -Wall -W* -Werror' useful, and testing ! GCC on a plethora of platforms. Kaveh extends his gratitude to ! the CAIP Center at Rutgers University for providing him with ! computing resources to work on Free Software from the late 1980s ! to 2010. * John Gilmore for a donation to the FSF earmarked improving GNU Java. *************** alphabetical order. *** 42914,42934 **** support, improved leaf function register allocation, and his direction via the steering committee. ! * Jonny Grant for improvements to 'collect2's' '--help' documentation. ! * Anthony Green for his '-Os' contributions, the moxie port, and Java ! front end work. ! * Stu Grossman for gdb hacking, allowing GCJ developers to debug Java ! code. * Michael K. Gschwind contributed the port to the PDP-11. * Richard Biener for his ongoing middle-end contributions and bug fixes and for release management. ! * Ron Guilmette implemented the 'protoize' and 'unprotoize' tools, the support for DWARF 1 symbolic debugging information, and much of the support for System V Release 4. He has also worked heavily on the Intel 386 and 860 support. --- 43389,43409 ---- support, improved leaf function register allocation, and his direction via the steering committee. ! * Jonny Grant for improvements to `collect2's' `--help' documentation. ! * Anthony Green for his `-Os' contributions, the moxie port, and ! Java front end work. ! * Stu Grossman for gdb hacking, allowing GCJ developers to debug ! Java code. * Michael K. Gschwind contributed the port to the PDP-11. * Richard Biener for his ongoing middle-end contributions and bug fixes and for release management. ! * Ron Guilmette implemented the `protoize' and `unprotoize' tools, the support for DWARF 1 symbolic debugging information, and much of the support for System V Release 4. He has also worked heavily on the Intel 386 and 860 support. *************** alphabetical order. *** 42947,42954 **** series 300. * Michael Hayes for various thankless work he's done trying to get ! the c30/c40 ports functional. Lots of loop and unroll improvements ! and fixes. * Dara Hazeghi for wading through myriads of target-specific bug reports. --- 43422,43429 ---- series 300. * Michael Hayes for various thankless work he's done trying to get ! the c30/c40 ports functional. Lots of loop and unroll ! improvements and fixes. * Dara Hazeghi for wading through myriads of target-specific bug reports. *************** alphabetical order. *** 42982,42989 **** * Falk Hueffner for working on C and optimization bug reports. ! * Bernardo Innocenti for his m68k work, including merging of ColdFire ! improvements and uClinux support. * Christian Iseli for various bug fixes. --- 43457,43464 ---- * Falk Hueffner for working on C and optimization bug reports. ! * Bernardo Innocenti for his m68k work, including merging of ! ColdFire improvements and uClinux support. * Christian Iseli for various bug fixes. *************** alphabetical order. *** 43036,43048 **** * Richard Kenner of the New York University Ultracomputer Research Laboratory wrote the machine descriptions for the AMD 29000, the DEC Alpha, the IBM RT PC, and the IBM RS/6000 as well as the ! support for instruction attributes. He also made changes to better ! support RISC processors including changes to common subexpression ! elimination, strength reduction, function calling sequence ! handling, and condition code support, in addition to generalizing ! the code for frame pointer elimination and delay slot scheduling. ! Richard Kenner was also the head maintainer of GCC for several ! years. * Mumit Khan for various contributions to the Cygwin and Mingw32 ports and maintaining binary releases for Microsoft Windows hosts, --- 43511,43523 ---- * Richard Kenner of the New York University Ultracomputer Research Laboratory wrote the machine descriptions for the AMD 29000, the DEC Alpha, the IBM RT PC, and the IBM RS/6000 as well as the ! support for instruction attributes. He also made changes to ! better support RISC processors including changes to common ! subexpression elimination, strength reduction, function calling ! sequence handling, and condition code support, in addition to ! generalizing the code for frame pointer elimination and delay slot ! scheduling. Richard Kenner was also the head maintainer of GCC ! for several years. * Mumit Khan for various contributions to the Cygwin and Mingw32 ports and maintaining binary releases for Microsoft Windows hosts, *************** alphabetical order. *** 43068,43078 **** * Asher Langton and Mike Kumbera for contributing Cray pointer support to GNU Fortran, and for other GNU Fortran improvements. ! * Jeff Law for his direction via the steering committee, coordinating ! the entire egcs project and GCC 2.95, rolling out snapshots and ! releases, handling merges from GCC2, reviewing tons of patches that ! might have fallen through the cracks else, and random but extensive ! hacking. * Walter Lee for work on the TILE-Gx and TILEPro ports. --- 43543,43553 ---- * Asher Langton and Mike Kumbera for contributing Cray pointer support to GNU Fortran, and for other GNU Fortran improvements. ! * Jeff Law for his direction via the steering committee, ! coordinating the entire egcs project and GCC 2.95, rolling out ! snapshots and releases, handling merges from GCC2, reviewing tons ! of patches that might have fallen through the cracks else, and ! random but extensive hacking. * Walter Lee for work on the TILE-Gx and TILEPro ports. *************** alphabetical order. *** 43101,43107 **** * Weiwen Liu for testing and various bug fixes. ! * Manuel Lo'pez-Iba'n~ez for improving '-Wconversion' and many other diagnostics fixes and improvements. * Dave Love for his ongoing work with the Fortran front end and --- 43576,43582 ---- * Weiwen Liu for testing and various bug fixes. ! * Manuel Lo'pez-Iba'n~ez for improving `-Wconversion' and many other diagnostics fixes and improvements. * Dave Love for his ongoing work with the Fortran front end and *************** alphabetical order. *** 43118,43130 **** * Greg McGary for random fixes and (someday) bounded pointers. * Andrew MacLeod for his ongoing work in building a real EH system, ! various code generation improvements, work on the global optimizer, ! etc. * Vladimir Makarov for hacking some ugly i960 problems, PowerPC ! hacking improvements to compile-time performance, overall knowledge ! and direction in the area of instruction scheduling, and design and ! implementation of the automaton based instruction scheduler. * Bob Manson for his behind the scenes work on dejagnu. --- 43593,43606 ---- * Greg McGary for random fixes and (someday) bounded pointers. * Andrew MacLeod for his ongoing work in building a real EH system, ! various code generation improvements, work on the global ! optimizer, etc. * Vladimir Makarov for hacking some ugly i960 problems, PowerPC ! hacking improvements to compile-time performance, overall ! knowledge and direction in the area of instruction scheduling, and ! design and implementation of the automaton based instruction ! scheduler. * Bob Manson for his behind the scenes work on dejagnu. *************** alphabetical order. *** 43163,43169 **** * Mark Mitchell for his direction via the steering committee, mountains of C++ work, load/store hoisting out of loops, alias ! analysis improvements, ISO C 'restrict' support, and serving as release manager from 2000 to 2011. * Alan Modra for various GNU/Linux bits and testing. --- 43639,43645 ---- * Mark Mitchell for his direction via the steering committee, mountains of C++ work, load/store hoisting out of loops, alias ! analysis improvements, ISO C `restrict' support, and serving as release manager from 2000 to 2011. * Alan Modra for various GNU/Linux bits and testing. *************** alphabetical order. *** 43173,43181 **** * Jason Molenda for major help in the care and feeding of all the services on the gcc.gnu.org (formerly egcs.cygnus.com) ! machine--mail, web services, ftp services, etc etc. Doing all this ! work on scrap paper and the backs of envelopes would have been... ! difficult. * Catherine Moore for fixing various ugly problems we have sent her way, including the haifa bug which was killing the Alpha & PowerPC --- 43649,43657 ---- * Jason Molenda for major help in the care and feeding of all the services on the gcc.gnu.org (formerly egcs.cygnus.com) ! machine--mail, web services, ftp services, etc etc. Doing all ! this work on scrap paper and the backs of envelopes would have ! been... difficult. * Catherine Moore for fixing various ugly problems we have sent her way, including the haifa bug which was killing the Alpha & PowerPC *************** alphabetical order. *** 43187,43194 **** initial IA-64 port. * Stephen Moshier contributed the floating point emulator that ! assists in cross-compilation and permits support for floating point ! numbers wider than 64 bits and for ISO C99 support. * Bill Moyer for his behind the scenes work on various issues. --- 43663,43670 ---- initial IA-64 port. * Stephen Moshier contributed the floating point emulator that ! assists in cross-compilation and permits support for floating ! point numbers wider than 64 bits and for ISO C99 support. * Bill Moyer for his behind the scenes work on various issues. *************** alphabetical order. *** 43211,43219 **** * NeXT, Inc. donated the front end that supports the Objective-C language. ! * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to the ! search engine setup, various documentation fixes and other small ! fixes. * Geoff Noer for his work on getting cygwin native builds working. --- 43687,43695 ---- * NeXT, Inc. donated the front end that supports the Objective-C language. ! * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to ! the search engine setup, various documentation fixes and other ! small fixes. * Geoff Noer for his work on getting cygwin native builds working. *************** alphabetical order. *** 43221,43228 **** tracking web pages, GIMPLE tuples, and assorted fixes. * David O'Brien for the FreeBSD/alpha, FreeBSD/AMD x86-64, ! FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and related ! infrastructure improvements. * Alexandre Oliva for various build infrastructure improvements, scripts and amazing testing work, including keeping libtool issues --- 43697,43704 ---- tracking web pages, GIMPLE tuples, and assorted fixes. * David O'Brien for the FreeBSD/alpha, FreeBSD/AMD x86-64, ! FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and ! related infrastructure improvements. * Alexandre Oliva for various build infrastructure improvements, scripts and amazing testing work, including keeping libtool issues *************** alphabetical order. *** 43234,43241 **** * Rainer Orth for random MIPS work, including improvements to GCC's o32 ABI support, improvements to dejagnu's MIPS support, Java ! configuration clean-ups and porting work, and maintaining the IRIX, ! Solaris 2, and Tru64 UNIX ports. * Hartmut Penner for work on the s390 port. --- 43710,43717 ---- * Rainer Orth for random MIPS work, including improvements to GCC's o32 ABI support, improvements to dejagnu's MIPS support, Java ! configuration clean-ups and porting work, and maintaining the ! IRIX, Solaris 2, and Tru64 UNIX ports. * Hartmut Penner for work on the s390 port. *************** alphabetical order. *** 43285,43291 **** * David Ronis inspired and encouraged Craig to rewrite the G77 documentation in texinfo format by contributing a first pass at a ! translation of the old 'g77-0.5.16/f/DOC' file. * Ken Rose for fixes to GCC's delay slot filling code. --- 43761,43767 ---- * David Ronis inspired and encouraged Craig to rewrite the G77 documentation in texinfo format by contributing a first pass at a ! translation of the old `g77-0.5.16/f/DOC' file. * Ken Rose for fixes to GCC's delay slot filling code. *************** alphabetical order. *** 43317,43324 **** * Tobias Schlu"ter for work on GNU Fortran. * Bernd Schmidt for various code generation improvements and major ! work in the reload pass, serving as release manager for GCC 2.95.3, ! and work on the Blackfin and C6X ports. * Peter Schmid for constant testing of libstdc++--especially application testing, going above and beyond what was requested for --- 43793,43800 ---- * Tobias Schlu"ter for work on GNU Fortran. * Bernd Schmidt for various code generation improvements and major ! work in the reload pass, serving as release manager for GCC ! 2.95.3, and work on the Blackfin and C6X ports. * Peter Schmid for constant testing of libstdc++--especially application testing, going above and beyond what was requested for *************** alphabetical order. *** 43333,43339 **** * Dodji Seketeli for numerous C++ bug fixes and debug info improvements. ! * Tim Shen for major work on ''. * Joel Sherrill for his direction via the steering committee, RTEMS contributions and RTEMS testing. --- 43809,43815 ---- * Dodji Seketeli for numerous C++ bug fixes and debug info improvements. ! * Tim Shen for major work on `'. * Joel Sherrill for his direction via the steering committee, RTEMS contributions and RTEMS testing. *************** alphabetical order. *** 43348,43355 **** from the LWG (thereby keeping GCC in line with updates from the ISO). ! * Franz Sirl for his ongoing work with making the PPC port stable for ! GNU/Linux. * Andrey Slepuhin for assorted AIX hacking. --- 43824,43831 ---- from the LWG (thereby keeping GCC in line with updates from the ISO). ! * Franz Sirl for his ongoing work with making the PPC port stable ! for GNU/Linux. * Andrey Slepuhin for assorted AIX hacking. *************** alphabetical order. *** 43364,43375 **** * Randy Smith finished the Sun FPA support. * Ed Smith-Rowland for his continuous work on libstdc++-v3, special ! functions, '', and various improvements to C++11 features. * Scott Snyder for queue, iterator, istream, and string fixes and libstdc++ testsuite entries. Also for providing the patch to G77 ! to add rudimentary support for 'INTEGER*1', 'INTEGER*2', and ! 'LOGICAL*1'. * Zdenek Sojka for running automated regression testing of GCC and reporting numerous bugs. --- 43840,43851 ---- * Randy Smith finished the Sun FPA support. * Ed Smith-Rowland for his continuous work on libstdc++-v3, special ! functions, `', and various improvements to C++11 features. * Scott Snyder for queue, iterator, istream, and string fixes and libstdc++ testsuite entries. Also for providing the patch to G77 ! to add rudimentary support for `INTEGER*1', `INTEGER*2', and ! `LOGICAL*1'. * Zdenek Sojka for running automated regression testing of GCC and reporting numerous bugs. *************** alphabetical order. *** 43393,43400 **** * John Stracke for his Java HTTP protocol fixes. ! * Mike Stump for his Elxsi port, G++ contributions over the years and ! more recently his vxworks contributions * Jeff Sturm for Java porting help, bug fixes, and encouragement. --- 43869,43876 ---- * John Stracke for his Java HTTP protocol fixes. ! * Mike Stump for his Elxsi port, G++ contributions over the years ! and more recently his vxworks contributions * Jeff Sturm for Java porting help, bug fixes, and encouragement. *************** alphabetical order. *** 43448,43455 **** * Jonathan Wakely for contributing libstdc++ Doxygen notes and XHTML guidance. ! * Dean Wakerley for converting the install documentation from HTML to ! texinfo in time for GCC 3.0. * Krister Walfridsson for random bug fixes. --- 43924,43931 ---- * Jonathan Wakely for contributing libstdc++ Doxygen notes and XHTML guidance. ! * Dean Wakerley for converting the install documentation from HTML ! to texinfo in time for GCC 3.0. * Krister Walfridsson for random bug fixes. *************** alphabetical order. *** 43457,43464 **** * Stephen M. Webb for time and effort on making libstdc++ shadow files work with the tricky Solaris 8+ headers, and for pushing the ! build-time header tree. Also, for starting and driving the ! '' effort. * John Wehle for various improvements for the x86 code generator, related infrastructure improvements to help x86 code generation, --- 43933,43940 ---- * Stephen M. Webb for time and effort on making libstdc++ shadow files work with the tricky Solaris 8+ headers, and for pushing the ! build-time header tree. Also, for starting and driving the ! `' effort. * John Wehle for various improvements for the x86 code generator, related infrastructure improvements to help x86 code generation, *************** alphabetical order. *** 43480,43487 **** * Bob Wilson from Tensilica, Inc. for the Xtensa port. * Jim Wilson for his direction via the steering committee, tackling ! hard problems in various places that nobody else wanted to work on, ! strength reduction and other loop optimizations. * Paul Woegerer and Tal Agmon for the CRX port. --- 43956,43963 ---- * Bob Wilson from Tensilica, Inc. for the Xtensa port. * Jim Wilson for his direction via the steering committee, tackling ! hard problems in various places that nobody else wanted to work ! on, strength reduction and other loop optimizations. * Paul Woegerer and Tal Agmon for the CRX port. *************** alphabetical order. *** 43504,43509 **** --- 43980,43986 ---- * Gilles Zunino for help porting Java to Irix. + The following people are recognized for their contributions to GNAT, the Ada front end of GCC: * Bernard Banner *************** the Ada front end of GCC: *** 43600,43701 **** * Samuel Tardieu The following people are recognized for their contributions of new features, bug reports, testing and integration of classpath/libgcj for GCC version 4.1: ! * Lillian Angel for 'JTree' implementation and lots Free Swing additions and bug fixes. ! * Wolfgang Baer for 'GapContent' bug fixes. ! * Anthony Balkissoon for 'JList', Free Swing 1.5 updates and mouse ! event fixes, lots of Free Swing work including 'JTable' editing. * Stuart Ballard for RMI constant fixes. ! * Goffredo Baroncelli for 'HTTPURLConnection' fixes. ! * Gary Benson for 'MessageFormat' fixes. ! * Daniel Bonniot for 'Serialization' fixes. ! * Chris Burdess for lots of gnu.xml and http protocol fixes, 'StAX' ! and 'DOM xml:id' support. ! * Ka-Hing Cheung for 'TreePath' and 'TreeSelection' fixes. * Archie Cobbs for build fixes, VM interface updates, ! 'URLClassLoader' updates. * Kelley Cook for build fixes. ! * Martin Cordova for Suggestions for better 'SocketTimeoutException'. ! * David Daney for 'BitSet' bug fixes, 'HttpURLConnection' rewrite and ! improvements. * Thomas Fitzsimmons for lots of upgrades to the gtk+ AWT and Cairo ! 2D support. Lots of imageio framework additions, lots of AWT and Free Swing bug fixes. ! * Jeroen Frijters for 'ClassLoader' and nio cleanups, serialization ! fixes, better 'Proxy' support, bug fixes and IKVM integration. ! * Santiago Gala for 'AccessControlContext' fixes. ! * Nicolas Geoffray for 'VMClassLoader' and 'AccessController' improvements. ! * David Gilbert for 'basic' and 'metal' icon and plaf support and lots of documenting, Lots of Free Swing and metal theme additions. ! 'MetalIconFactory' implementation. ! * Anthony Green for 'MIDI' framework, 'ALSA' and 'DSSI' providers. ! * Andrew Haley for 'Serialization' and 'URLClassLoader' fixes, gcj build speedups. ! * Kim Ho for 'JFileChooser' implementation. ! * Andrew John Hughes for 'Locale' and net fixes, URI RFC2986 updates, ! 'Serialization' fixes, 'Properties' XML support and generic branch ! work, VMIntegration guide update. ! * Bastiaan Huisman for 'TimeZone' bug fixing. * Andreas Jaeger for mprec updates. ! * Paul Jenner for better '-Werror' support. ! * Ito Kazumitsu for 'NetworkInterface' implementation and updates. ! * Roman Kennke for 'BoxLayout', 'GrayFilter' and 'SplitPane', plus ! bug fixes all over. Lots of Free Swing work including styled text. ! * Simon Kitching for 'String' cleanups and optimization suggestions. ! * Michael Koch for configuration fixes, 'Locale' updates, bug and build fixes. * Guilhem Lavaux for configuration, thread and channel fixes and ! Kaffe integration. JCL native 'Pointer' updates. Logger bug ! fixes. * David Lichteblau for JCL support library global/local reference cleanups. * Aaron Luchko for JDWP updates and documentation fixes. ! * Ziga Mahkovec for 'Graphics2D' upgraded to Cairo 0.5 and new regex features. ! * Sven de Marothy for BMP imageio support, CSS and 'TextLayout' ! fixes. 'GtkImage' rewrite, 2D, awt, free swing and date/time fixes and implementing the Qt4 peers. ! * Casey Marshall for crypto algorithm fixes, 'FileChannel' lock, ! 'SystemLogger' and 'FileHandler' rotate implementations, NIO ! 'FileChannel.map' support, security and policy updates. * Bryce McKinlay for RMI work. --- 44077,44178 ---- * Samuel Tardieu + The following people are recognized for their contributions of new features, bug reports, testing and integration of classpath/libgcj for GCC version 4.1: ! * Lillian Angel for `JTree' implementation and lots Free Swing additions and bug fixes. ! * Wolfgang Baer for `GapContent' bug fixes. ! * Anthony Balkissoon for `JList', Free Swing 1.5 updates and mouse ! event fixes, lots of Free Swing work including `JTable' editing. * Stuart Ballard for RMI constant fixes. ! * Goffredo Baroncelli for `HTTPURLConnection' fixes. ! * Gary Benson for `MessageFormat' fixes. ! * Daniel Bonniot for `Serialization' fixes. ! * Chris Burdess for lots of gnu.xml and http protocol fixes, `StAX' ! and `DOM xml:id' support. ! * Ka-Hing Cheung for `TreePath' and `TreeSelection' fixes. * Archie Cobbs for build fixes, VM interface updates, ! `URLClassLoader' updates. * Kelley Cook for build fixes. ! * Martin Cordova for Suggestions for better `SocketTimeoutException'. ! * David Daney for `BitSet' bug fixes, `HttpURLConnection' rewrite ! and improvements. * Thomas Fitzsimmons for lots of upgrades to the gtk+ AWT and Cairo ! 2D support. Lots of imageio framework additions, lots of AWT and Free Swing bug fixes. ! * Jeroen Frijters for `ClassLoader' and nio cleanups, serialization ! fixes, better `Proxy' support, bug fixes and IKVM integration. ! * Santiago Gala for `AccessControlContext' fixes. ! * Nicolas Geoffray for `VMClassLoader' and `AccessController' improvements. ! * David Gilbert for `basic' and `metal' icon and plaf support and lots of documenting, Lots of Free Swing and metal theme additions. ! `MetalIconFactory' implementation. ! * Anthony Green for `MIDI' framework, `ALSA' and `DSSI' providers. ! * Andrew Haley for `Serialization' and `URLClassLoader' fixes, gcj build speedups. ! * Kim Ho for `JFileChooser' implementation. ! * Andrew John Hughes for `Locale' and net fixes, URI RFC2986 ! updates, `Serialization' fixes, `Properties' XML support and ! generic branch work, VMIntegration guide update. ! * Bastiaan Huisman for `TimeZone' bug fixing. * Andreas Jaeger for mprec updates. ! * Paul Jenner for better `-Werror' support. ! * Ito Kazumitsu for `NetworkInterface' implementation and updates. ! * Roman Kennke for `BoxLayout', `GrayFilter' and `SplitPane', plus ! bug fixes all over. Lots of Free Swing work including styled text. ! * Simon Kitching for `String' cleanups and optimization suggestions. ! * Michael Koch for configuration fixes, `Locale' updates, bug and build fixes. * Guilhem Lavaux for configuration, thread and channel fixes and ! Kaffe integration. JCL native `Pointer' updates. Logger bug fixes. * David Lichteblau for JCL support library global/local reference cleanups. * Aaron Luchko for JDWP updates and documentation fixes. ! * Ziga Mahkovec for `Graphics2D' upgraded to Cairo 0.5 and new regex features. ! * Sven de Marothy for BMP imageio support, CSS and `TextLayout' ! fixes. `GtkImage' rewrite, 2D, awt, free swing and date/time fixes and implementing the Qt4 peers. ! * Casey Marshall for crypto algorithm fixes, `FileChannel' lock, ! `SystemLogger' and `FileHandler' rotate implementations, NIO ! `FileChannel.map' support, security and policy updates. * Bryce McKinlay for RMI work. *************** GCC version 4.1: *** 43706,43750 **** * Rainer Orth for build fixes. ! * Andrew Overholt for 'File' locking fixes. ! * Ingo Proetel for 'Image', 'Logger' and 'URLClassLoader' updates. ! * Olga Rodimina for 'MenuSelectionManager' implementation. ! * Jan Roehrich for 'BasicTreeUI' and 'JTree' fixes. * Julian Scheid for documentation updates and gjdoc support. * Christian Schlichtherle for zip fixes and cleanups. * Robert Schuster for documentation updates and beans fixes, ! 'TreeNode' enumerations and 'ActionCommand' and various fixes, XML and URL, AWT and Free Swing bug fixes. * Keith Seitz for lots of JDWP work. * Christian Thalinger for 64-bit cleanups, Configuration and VM ! interface fixes and 'CACAO' integration, 'fdlibm' updates. ! * Gael Thomas for 'VMClassLoader' boot packages support suggestions. ! * Andreas Tobler for Darwin and Solaris testing and fixing, 'Qt4' ! support for Darwin/OS X, 'Graphics2D' support, 'gtk+' updates. ! * Dalibor Topic for better 'DEBUG' support, build cleanups and Kaffe ! integration. 'Qt4' build infrastructure, 'SHA1PRNG' and ! 'GdkPixbugDecoder' updates. * Tom Tromey for Eclipse integration, generics work, lots of bug fixes and gcj integration including coordinating The Big Merge. * Mark Wielaard for bug fixes, packaging and release management, ! 'Clipboard' implementation, system call interrupts and network ! timeouts and 'GdkPixpufDecoder' fixes. ! In addition to the above, all of which also contributed time and energy ! in testing GCC, we would like to thank the following for their contributions to testing: * Michael Abd-El-Malek --- 44183,44228 ---- * Rainer Orth for build fixes. ! * Andrew Overholt for `File' locking fixes. ! * Ingo Proetel for `Image', `Logger' and `URLClassLoader' updates. ! * Olga Rodimina for `MenuSelectionManager' implementation. ! * Jan Roehrich for `BasicTreeUI' and `JTree' fixes. * Julian Scheid for documentation updates and gjdoc support. * Christian Schlichtherle for zip fixes and cleanups. * Robert Schuster for documentation updates and beans fixes, ! `TreeNode' enumerations and `ActionCommand' and various fixes, XML and URL, AWT and Free Swing bug fixes. * Keith Seitz for lots of JDWP work. * Christian Thalinger for 64-bit cleanups, Configuration and VM ! interface fixes and `CACAO' integration, `fdlibm' updates. ! * Gael Thomas for `VMClassLoader' boot packages support suggestions. ! * Andreas Tobler for Darwin and Solaris testing and fixing, `Qt4' ! support for Darwin/OS X, `Graphics2D' support, `gtk+' updates. ! * Dalibor Topic for better `DEBUG' support, build cleanups and Kaffe ! integration. `Qt4' build infrastructure, `SHA1PRNG' and ! `GdkPixbugDecoder' updates. * Tom Tromey for Eclipse integration, generics work, lots of bug fixes and gcj integration including coordinating The Big Merge. * Mark Wielaard for bug fixes, packaging and release management, ! `Clipboard' implementation, system call interrupts and network ! timeouts and `GdkPixpufDecoder' fixes. ! ! In addition to the above, all of which also contributed time and ! energy in testing GCC, we would like to thank the following for their contributions to testing: * Michael Abd-El-Malek *************** File: gccint.info, Node: Option Index, *** 43913,43921 **** Option Index ************ ! GCC's command line options are indexed here without any initial '-' or ! '--'. Where an option has both positive and negative forms (such as ! '-fOPTION' and '-fno-OPTION'), relevant entries in the manual are indexed under the most appropriate form; it may sometimes be useful to look up both forms. --- 44391,44399 ---- Option Index ************ ! GCC's command line options are indexed here without any initial `-' or ! `--'. Where an option has both positive and negative forms (such as ! `-fOPTION' and `-fno-OPTION'), relevant entries in the manual are indexed under the most appropriate form; it may sometimes be useful to look up both forms. *************** Concept Index *** 43947,43993 **** * % in GTY option: GTY Options. (line 18) * % in template: Output Template. (line 6) * & in constraint: Modifiers. (line 25) ! * (gimple_stmt_iterator: GIMPLE API. (line 30) * (nil): RTL Objects. (line 73) * * in constraint: Modifiers. (line 83) * * in template: Output Statement. (line 29) ! * *gimple_build_asm_vec: GIMPLE_ASM. (line 6) ! * *gimple_build_assign: GIMPLE_ASSIGN. (line 6) ! * *gimple_build_assign <1>: GIMPLE_ASSIGN. (line 18) ! * *gimple_build_assign <2>: GIMPLE_ASSIGN. (line 29) ! * *gimple_build_assign <3>: GIMPLE_ASSIGN. (line 35) ! * *gimple_build_bind: GIMPLE_BIND. (line 6) ! * *gimple_build_call: GIMPLE_CALL. (line 6) ! * *gimple_build_call_from_tree: GIMPLE_CALL. (line 15) ! * *gimple_build_call_vec: GIMPLE_CALL. (line 23) ! * *gimple_build_catch: GIMPLE_CATCH. (line 6) ! * *gimple_build_cond: GIMPLE_COND. (line 6) ! * *gimple_build_cond_from_tree: GIMPLE_COND. (line 14) ! * *gimple_build_debug_bind: GIMPLE_DEBUG. (line 6) ! * *gimple_build_eh_filter: GIMPLE_EH_FILTER. (line 6) ! * *gimple_build_goto: GIMPLE_GOTO. (line 6) ! * *gimple_build_label: GIMPLE_LABEL. (line 6) * *gimple_build_omp_atomic_load: GIMPLE_OMP_ATOMIC_LOAD. ! (line 6) * *gimple_build_omp_atomic_store: GIMPLE_OMP_ATOMIC_STORE. ! (line 6) * *gimple_build_omp_continue: GIMPLE_OMP_CONTINUE. ! (line 6) * *gimple_build_omp_critical: GIMPLE_OMP_CRITICAL. ! (line 6) ! * *gimple_build_omp_for: GIMPLE_OMP_FOR. (line 6) * *gimple_build_omp_parallel: GIMPLE_OMP_PARALLEL. ! (line 6) * *gimple_build_omp_sections: GIMPLE_OMP_SECTIONS. ! (line 6) ! * *gimple_build_omp_single: GIMPLE_OMP_SINGLE. (line 6) ! * *gimple_build_resx: GIMPLE_RESX. (line 6) ! * *gimple_build_return: GIMPLE_RETURN. (line 6) ! * *gimple_build_switch: GIMPLE_SWITCH. (line 6) ! * *gimple_build_try: GIMPLE_TRY. (line 6) * + in constraint: Modifiers. (line 12) - * -fsection-anchors: Special Accessors. (line 117) * -fsection-anchors <1>: Anchored Addresses. (line 6) * /c in RTL dump: Flags. (line 221) * /f in RTL dump: Flags. (line 229) * /i in RTL dump: Flags. (line 274) --- 44425,44468 ---- * % in GTY option: GTY Options. (line 18) * % in template: Output Template. (line 6) * & in constraint: Modifiers. (line 25) ! * (: GIMPLE API. (line 31) * (nil): RTL Objects. (line 73) * * in constraint: Modifiers. (line 83) * * in template: Output Statement. (line 29) ! * *gimple_build_asm_vec: GIMPLE_ASM. (line 9) ! * *gimple_build_assign: GIMPLE_ASSIGN. (line 7) ! * *gimple_build_bind: GIMPLE_BIND. (line 8) ! * *gimple_build_call: GIMPLE_CALL. (line 8) ! * *gimple_build_call_from_tree: GIMPLE_CALL. (line 16) ! * *gimple_build_call_vec: GIMPLE_CALL. (line 25) ! * *gimple_build_catch: GIMPLE_CATCH. (line 8) ! * *gimple_build_cond: GIMPLE_COND. (line 8) ! * *gimple_build_cond_from_tree: GIMPLE_COND. (line 16) ! * *gimple_build_debug_bind: GIMPLE_DEBUG. (line 8) ! * *gimple_build_eh_filter: GIMPLE_EH_FILTER. (line 8) ! * *gimple_build_goto: GIMPLE_GOTO. (line 7) ! * *gimple_build_label: GIMPLE_LABEL. (line 7) * *gimple_build_omp_atomic_load: GIMPLE_OMP_ATOMIC_LOAD. ! (line 8) * *gimple_build_omp_atomic_store: GIMPLE_OMP_ATOMIC_STORE. ! (line 8) * *gimple_build_omp_continue: GIMPLE_OMP_CONTINUE. ! (line 8) * *gimple_build_omp_critical: GIMPLE_OMP_CRITICAL. ! (line 8) ! * *gimple_build_omp_for: GIMPLE_OMP_FOR. (line 9) * *gimple_build_omp_parallel: GIMPLE_OMP_PARALLEL. ! (line 8) * *gimple_build_omp_sections: GIMPLE_OMP_SECTIONS. ! (line 8) ! * *gimple_build_omp_single: GIMPLE_OMP_SINGLE. (line 8) ! * *gimple_build_resx: GIMPLE_RESX. (line 7) ! * *gimple_build_return: GIMPLE_RETURN. (line 7) ! * *gimple_build_switch: GIMPLE_SWITCH. (line 8) ! * *gimple_build_try: GIMPLE_TRY. (line 8) * + in constraint: Modifiers. (line 12) * -fsection-anchors <1>: Anchored Addresses. (line 6) + * -fsection-anchors: Special Accessors. (line 120) * /c in RTL dump: Flags. (line 221) * /f in RTL dump: Flags. (line 229) * /i in RTL dump: Flags. (line 274) *************** Concept Index *** 43995,47535 **** * /s in RTL dump: Flags. (line 245) * /u in RTL dump: Flags. (line 296) * /v in RTL dump: Flags. (line 328) ! * 0 in constraint: Simple Constraints. (line 128) ! * < in constraint: Simple Constraints. (line 47) * = in constraint: Modifiers. (line 8) ! * > in constraint: Simple Constraints. (line 59) * ? in constraint: Multi-Alternative. (line 42) * \: Output Template. (line 46) * ^ in constraint: Multi-Alternative. (line 53) * __absvdi2: Integer library routines. ! (line 106) * __absvsi2: Integer library routines. ! (line 105) * __addda3: Fixed-point fractional library routines. ! (line 52) * __adddf3: Soft float library routines. ! (line 22) * __adddq3: Fixed-point fractional library routines. ! (line 39) * __addha3: Fixed-point fractional library routines. ! (line 49) * __addhq3: Fixed-point fractional library routines. ! (line 37) * __addqq3: Fixed-point fractional library routines. ! (line 35) * __addsa3: Fixed-point fractional library routines. ! (line 51) * __addsf3: Soft float library routines. ! (line 21) * __addsq3: Fixed-point fractional library routines. ! (line 38) * __addta3: Fixed-point fractional library routines. ! (line 53) * __addtf3: Soft float library routines. ! (line 23) * __adduda3: Fixed-point fractional library routines. ! (line 59) * __addudq3: Fixed-point fractional library routines. ! (line 47) * __adduha3: Fixed-point fractional library routines. ! (line 55) * __adduhq3: Fixed-point fractional library routines. ! (line 43) * __adduqq3: Fixed-point fractional library routines. ! (line 41) * __addusa3: Fixed-point fractional library routines. ! (line 57) * __addusq3: Fixed-point fractional library routines. ! (line 45) * __adduta3: Fixed-point fractional library routines. ! (line 61) * __addvdi3: Integer library routines. ! (line 110) * __addvsi3: Integer library routines. ! (line 109) * __addxf3: Soft float library routines. ! (line 25) * __ashlda3: Fixed-point fractional library routines. ! (line 358) * __ashldi3: Integer library routines. ! (line 13) * __ashldq3: Fixed-point fractional library routines. ! (line 346) * __ashlha3: Fixed-point fractional library routines. ! (line 356) * __ashlhq3: Fixed-point fractional library routines. ! (line 344) * __ashlqq3: Fixed-point fractional library routines. ! (line 343) * __ashlsa3: Fixed-point fractional library routines. ! (line 357) * __ashlsi3: Integer library routines. ! (line 12) * __ashlsq3: Fixed-point fractional library routines. ! (line 345) * __ashlta3: Fixed-point fractional library routines. ! (line 359) * __ashlti3: Integer library routines. ! (line 14) * __ashluda3: Fixed-point fractional library routines. ! (line 365) * __ashludq3: Fixed-point fractional library routines. ! (line 354) * __ashluha3: Fixed-point fractional library routines. ! (line 361) * __ashluhq3: Fixed-point fractional library routines. ! (line 350) * __ashluqq3: Fixed-point fractional library routines. ! (line 348) * __ashlusa3: Fixed-point fractional library routines. ! (line 363) * __ashlusq3: Fixed-point fractional library routines. ! (line 352) * __ashluta3: Fixed-point fractional library routines. ! (line 367) * __ashrda3: Fixed-point fractional library routines. ! (line 378) * __ashrdi3: Integer library routines. ! (line 18) * __ashrdq3: Fixed-point fractional library routines. ! (line 374) * __ashrha3: Fixed-point fractional library routines. ! (line 376) * __ashrhq3: Fixed-point fractional library routines. ! (line 372) * __ashrqq3: Fixed-point fractional library routines. ! (line 371) * __ashrsa3: Fixed-point fractional library routines. ! (line 377) * __ashrsi3: Integer library routines. ! (line 17) * __ashrsq3: Fixed-point fractional library routines. ! (line 373) * __ashrta3: Fixed-point fractional library routines. ! (line 379) * __ashrti3: Integer library routines. ! (line 19) * __bid_adddd3: Decimal float library routines. ! (line 23) * __bid_addsd3: Decimal float library routines. ! (line 19) * __bid_addtd3: Decimal float library routines. ! (line 27) * __bid_divdd3: Decimal float library routines. ! (line 66) * __bid_divsd3: Decimal float library routines. ! (line 62) * __bid_divtd3: Decimal float library routines. ! (line 70) * __bid_eqdd2: Decimal float library routines. ! (line 258) * __bid_eqsd2: Decimal float library routines. ! (line 256) * __bid_eqtd2: Decimal float library routines. ! (line 260) * __bid_extendddtd2: Decimal float library routines. ! (line 91) * __bid_extendddtf: Decimal float library routines. ! (line 139) * __bid_extendddxf: Decimal float library routines. ! (line 133) * __bid_extenddfdd: Decimal float library routines. ! (line 146) * __bid_extenddftd: Decimal float library routines. ! (line 106) * __bid_extendsddd2: Decimal float library routines. ! (line 87) * __bid_extendsddf: Decimal float library routines. ! (line 127) * __bid_extendsdtd2: Decimal float library routines. ! (line 89) * __bid_extendsdtf: Decimal float library routines. ! (line 137) * __bid_extendsdxf: Decimal float library routines. ! (line 131) * __bid_extendsfdd: Decimal float library routines. ! (line 102) * __bid_extendsfsd: Decimal float library routines. ! (line 144) * __bid_extendsftd: Decimal float library routines. ! (line 104) * __bid_extendtftd: Decimal float library routines. ! (line 148) * __bid_extendxftd: Decimal float library routines. ! (line 108) * __bid_fixdddi: Decimal float library routines. ! (line 169) * __bid_fixddsi: Decimal float library routines. ! (line 161) * __bid_fixsddi: Decimal float library routines. ! (line 167) * __bid_fixsdsi: Decimal float library routines. ! (line 159) * __bid_fixtddi: Decimal float library routines. ! (line 171) * __bid_fixtdsi: Decimal float library routines. ! (line 163) * __bid_fixunsdddi: Decimal float library routines. ! (line 186) * __bid_fixunsddsi: Decimal float library routines. ! (line 177) * __bid_fixunssddi: Decimal float library routines. ! (line 184) * __bid_fixunssdsi: Decimal float library routines. ! (line 175) * __bid_fixunstddi: Decimal float library routines. ! (line 188) * __bid_fixunstdsi: Decimal float library routines. ! (line 179) * __bid_floatdidd: Decimal float library routines. ! (line 204) * __bid_floatdisd: Decimal float library routines. ! (line 202) * __bid_floatditd: Decimal float library routines. ! (line 206) * __bid_floatsidd: Decimal float library routines. ! (line 195) * __bid_floatsisd: Decimal float library routines. ! (line 193) * __bid_floatsitd: Decimal float library routines. ! (line 197) * __bid_floatunsdidd: Decimal float library routines. ! (line 222) * __bid_floatunsdisd: Decimal float library routines. ! (line 220) * __bid_floatunsditd: Decimal float library routines. ! (line 224) * __bid_floatunssidd: Decimal float library routines. ! (line 213) * __bid_floatunssisd: Decimal float library routines. ! (line 211) * __bid_floatunssitd: Decimal float library routines. ! (line 215) * __bid_gedd2: Decimal float library routines. ! (line 276) * __bid_gesd2: Decimal float library routines. ! (line 274) * __bid_getd2: Decimal float library routines. ! (line 278) * __bid_gtdd2: Decimal float library routines. ! (line 303) * __bid_gtsd2: Decimal float library routines. ! (line 301) * __bid_gttd2: Decimal float library routines. ! (line 305) * __bid_ledd2: Decimal float library routines. ! (line 294) * __bid_lesd2: Decimal float library routines. ! (line 292) * __bid_letd2: Decimal float library routines. ! (line 296) * __bid_ltdd2: Decimal float library routines. ! (line 285) * __bid_ltsd2: Decimal float library routines. ! (line 283) * __bid_lttd2: Decimal float library routines. ! (line 287) * __bid_muldd3: Decimal float library routines. ! (line 52) * __bid_mulsd3: Decimal float library routines. ! (line 48) * __bid_multd3: Decimal float library routines. ! (line 56) * __bid_nedd2: Decimal float library routines. ! (line 267) * __bid_negdd2: Decimal float library routines. ! (line 77) * __bid_negsd2: Decimal float library routines. ! (line 75) * __bid_negtd2: Decimal float library routines. ! (line 79) * __bid_nesd2: Decimal float library routines. ! (line 265) * __bid_netd2: Decimal float library routines. ! (line 269) * __bid_subdd3: Decimal float library routines. ! (line 37) * __bid_subsd3: Decimal float library routines. ! (line 33) * __bid_subtd3: Decimal float library routines. ! (line 41) * __bid_truncdddf: Decimal float library routines. ! (line 152) * __bid_truncddsd2: Decimal float library routines. ! (line 93) * __bid_truncddsf: Decimal float library routines. ! (line 123) * __bid_truncdfsd: Decimal float library routines. ! (line 110) * __bid_truncsdsf: Decimal float library routines. ! (line 150) * __bid_trunctddd2: Decimal float library routines. ! (line 97) * __bid_trunctddf: Decimal float library routines. ! (line 129) * __bid_trunctdsd2: Decimal float library routines. ! (line 95) * __bid_trunctdsf: Decimal float library routines. ! (line 125) * __bid_trunctdtf: Decimal float library routines. ! (line 154) * __bid_trunctdxf: Decimal float library routines. ! (line 135) * __bid_trunctfdd: Decimal float library routines. ! (line 118) * __bid_trunctfsd: Decimal float library routines. ! (line 114) * __bid_truncxfdd: Decimal float library routines. ! (line 116) * __bid_truncxfsd: Decimal float library routines. ! (line 112) * __bid_unorddd2: Decimal float library routines. ! (line 234) * __bid_unordsd2: Decimal float library routines. ! (line 232) * __bid_unordtd2: Decimal float library routines. ! (line 236) * __bswapdi2: Integer library routines. ! (line 161) * __bswapsi2: Integer library routines. ! (line 160) ! * __builtin_classify_type: Varargs. (line 48) ! * __builtin_next_arg: Varargs. (line 39) ! * __builtin_saveregs: Varargs. (line 22) ! * __chkp_bndcl: Misc. (line 650) ! * __chkp_bndcu: Misc. (line 656) ! * __chkp_bndldx: Misc. (line 644) ! * __chkp_bndmk: Misc. (line 631) ! * __chkp_bndret: Misc. (line 662) ! * __chkp_bndstx: Misc. (line 638) ! * __chkp_intersect: Misc. (line 668) ! * __chkp_narrow: Misc. (line 673) ! * __chkp_sizeof: Misc. (line 679) * __clear_cache: Miscellaneous routines. ! (line 9) * __clzdi2: Integer library routines. ! (line 130) * __clzsi2: Integer library routines. ! (line 129) * __clzti2: Integer library routines. ! (line 131) * __cmpda2: Fixed-point fractional library routines. ! (line 458) * __cmpdf2: Soft float library routines. ! (line 163) * __cmpdi2: Integer library routines. ! (line 86) * __cmpdq2: Fixed-point fractional library routines. ! (line 447) * __cmpha2: Fixed-point fractional library routines. ! (line 456) * __cmphq2: Fixed-point fractional library routines. ! (line 445) * __cmpqq2: Fixed-point fractional library routines. ! (line 444) * __cmpsa2: Fixed-point fractional library routines. ! (line 457) * __cmpsf2: Soft float library routines. ! (line 162) * __cmpsq2: Fixed-point fractional library routines. ! (line 446) * __cmpta2: Fixed-point fractional library routines. ! (line 459) * __cmptf2: Soft float library routines. ! (line 164) * __cmpti2: Integer library routines. ! (line 87) * __cmpuda2: Fixed-point fractional library routines. ! (line 464) * __cmpudq2: Fixed-point fractional library routines. ! (line 454) * __cmpuha2: Fixed-point fractional library routines. ! (line 461) * __cmpuhq2: Fixed-point fractional library routines. ! (line 451) * __cmpuqq2: Fixed-point fractional library routines. ! (line 449) * __cmpusa2: Fixed-point fractional library routines. ! (line 463) * __cmpusq2: Fixed-point fractional library routines. ! (line 452) * __cmputa2: Fixed-point fractional library routines. ! (line 466) * __CTOR_LIST__: Initialization. (line 25) * __ctzdi2: Integer library routines. ! (line 137) * __ctzsi2: Integer library routines. ! (line 136) * __ctzti2: Integer library routines. ! (line 138) * __divda3: Fixed-point fractional library routines. ! (line 234) * __divdc3: Soft float library routines. ! (line 250) * __divdf3: Soft float library routines. ! (line 47) * __divdi3: Integer library routines. ! (line 24) * __divdq3: Fixed-point fractional library routines. ! (line 229) * __divha3: Fixed-point fractional library routines. ! (line 231) * __divhq3: Fixed-point fractional library routines. ! (line 227) * __divqq3: Fixed-point fractional library routines. ! (line 225) * __divsa3: Fixed-point fractional library routines. ! (line 233) * __divsc3: Soft float library routines. ! (line 248) * __divsf3: Soft float library routines. ! (line 46) * __divsi3: Integer library routines. ! (line 23) * __divsq3: Fixed-point fractional library routines. ! (line 228) * __divta3: Fixed-point fractional library routines. ! (line 235) * __divtc3: Soft float library routines. ! (line 252) * __divtf3: Soft float library routines. ! (line 48) * __divti3: Integer library routines. ! (line 25) * __divxc3: Soft float library routines. ! (line 254) * __divxf3: Soft float library routines. ! (line 50) * __dpd_adddd3: Decimal float library routines. ! (line 21) * __dpd_addsd3: Decimal float library routines. ! (line 17) * __dpd_addtd3: Decimal float library routines. ! (line 25) * __dpd_divdd3: Decimal float library routines. ! (line 64) * __dpd_divsd3: Decimal float library routines. ! (line 60) * __dpd_divtd3: Decimal float library routines. ! (line 68) * __dpd_eqdd2: Decimal float library routines. ! (line 257) * __dpd_eqsd2: Decimal float library routines. ! (line 255) * __dpd_eqtd2: Decimal float library routines. ! (line 259) * __dpd_extendddtd2: Decimal float library routines. ! (line 90) * __dpd_extendddtf: Decimal float library routines. ! (line 138) * __dpd_extendddxf: Decimal float library routines. ! (line 132) * __dpd_extenddfdd: Decimal float library routines. ! (line 145) * __dpd_extenddftd: Decimal float library routines. ! (line 105) * __dpd_extendsddd2: Decimal float library routines. ! (line 86) * __dpd_extendsddf: Decimal float library routines. ! (line 126) * __dpd_extendsdtd2: Decimal float library routines. ! (line 88) * __dpd_extendsdtf: Decimal float library routines. ! (line 136) * __dpd_extendsdxf: Decimal float library routines. ! (line 130) * __dpd_extendsfdd: Decimal float library routines. ! (line 101) * __dpd_extendsfsd: Decimal float library routines. ! (line 143) * __dpd_extendsftd: Decimal float library routines. ! (line 103) * __dpd_extendtftd: Decimal float library routines. ! (line 147) * __dpd_extendxftd: Decimal float library routines. ! (line 107) * __dpd_fixdddi: Decimal float library routines. ! (line 168) * __dpd_fixddsi: Decimal float library routines. ! (line 160) * __dpd_fixsddi: Decimal float library routines. ! (line 166) * __dpd_fixsdsi: Decimal float library routines. ! (line 158) * __dpd_fixtddi: Decimal float library routines. ! (line 170) * __dpd_fixtdsi: Decimal float library routines. ! (line 162) * __dpd_fixunsdddi: Decimal float library routines. ! (line 185) * __dpd_fixunsddsi: Decimal float library routines. ! (line 176) * __dpd_fixunssddi: Decimal float library routines. ! (line 183) * __dpd_fixunssdsi: Decimal float library routines. ! (line 174) * __dpd_fixunstddi: Decimal float library routines. ! (line 187) * __dpd_fixunstdsi: Decimal float library routines. ! (line 178) * __dpd_floatdidd: Decimal float library routines. ! (line 203) * __dpd_floatdisd: Decimal float library routines. ! (line 201) * __dpd_floatditd: Decimal float library routines. ! (line 205) * __dpd_floatsidd: Decimal float library routines. ! (line 194) * __dpd_floatsisd: Decimal float library routines. ! (line 192) * __dpd_floatsitd: Decimal float library routines. ! (line 196) * __dpd_floatunsdidd: Decimal float library routines. ! (line 221) * __dpd_floatunsdisd: Decimal float library routines. ! (line 219) * __dpd_floatunsditd: Decimal float library routines. ! (line 223) * __dpd_floatunssidd: Decimal float library routines. ! (line 212) * __dpd_floatunssisd: Decimal float library routines. ! (line 210) * __dpd_floatunssitd: Decimal float library routines. ! (line 214) * __dpd_gedd2: Decimal float library routines. ! (line 275) * __dpd_gesd2: Decimal float library routines. ! (line 273) * __dpd_getd2: Decimal float library routines. ! (line 277) * __dpd_gtdd2: Decimal float library routines. ! (line 302) * __dpd_gtsd2: Decimal float library routines. ! (line 300) * __dpd_gttd2: Decimal float library routines. ! (line 304) * __dpd_ledd2: Decimal float library routines. ! (line 293) * __dpd_lesd2: Decimal float library routines. ! (line 291) * __dpd_letd2: Decimal float library routines. ! (line 295) * __dpd_ltdd2: Decimal float library routines. ! (line 284) * __dpd_ltsd2: Decimal float library routines. ! (line 282) * __dpd_lttd2: Decimal float library routines. ! (line 286) * __dpd_muldd3: Decimal float library routines. ! (line 50) * __dpd_mulsd3: Decimal float library routines. ! (line 46) * __dpd_multd3: Decimal float library routines. ! (line 54) * __dpd_nedd2: Decimal float library routines. ! (line 266) * __dpd_negdd2: Decimal float library routines. ! (line 76) * __dpd_negsd2: Decimal float library routines. ! (line 74) * __dpd_negtd2: Decimal float library routines. ! (line 78) * __dpd_nesd2: Decimal float library routines. ! (line 264) * __dpd_netd2: Decimal float library routines. ! (line 268) * __dpd_subdd3: Decimal float library routines. ! (line 35) * __dpd_subsd3: Decimal float library routines. ! (line 31) * __dpd_subtd3: Decimal float library routines. ! (line 39) * __dpd_truncdddf: Decimal float library routines. ! (line 151) * __dpd_truncddsd2: Decimal float library routines. ! (line 92) * __dpd_truncddsf: Decimal float library routines. ! (line 122) * __dpd_truncdfsd: Decimal float library routines. ! (line 109) * __dpd_truncsdsf: Decimal float library routines. ! (line 149) * __dpd_trunctddd2: Decimal float library routines. ! (line 96) * __dpd_trunctddf: Decimal float library routines. ! (line 128) * __dpd_trunctdsd2: Decimal float library routines. ! (line 94) * __dpd_trunctdsf: Decimal float library routines. ! (line 124) * __dpd_trunctdtf: Decimal float library routines. ! (line 153) * __dpd_trunctdxf: Decimal float library routines. ! (line 134) * __dpd_trunctfdd: Decimal float library routines. ! (line 117) * __dpd_trunctfsd: Decimal float library routines. ! (line 113) * __dpd_truncxfdd: Decimal float library routines. ! (line 115) * __dpd_truncxfsd: Decimal float library routines. ! (line 111) * __dpd_unorddd2: Decimal float library routines. ! (line 233) * __dpd_unordsd2: Decimal float library routines. ! (line 231) * __dpd_unordtd2: Decimal float library routines. ! (line 235) * __DTOR_LIST__: Initialization. (line 25) * __eqdf2: Soft float library routines. ! (line 193) * __eqsf2: Soft float library routines. ! (line 192) * __eqtf2: Soft float library routines. ! (line 194) * __extenddftf2: Soft float library routines. - (line 67) - * __extenddfxf2: Soft float library routines. (line 68) * __extendsfdf2: Soft float library routines. - (line 64) - * __extendsftf2: Soft float library routines. (line 65) ! * __extendsfxf2: Soft float library routines. (line 66) * __ffsdi2: Integer library routines. - (line 143) - * __ffsti2: Integer library routines. (line 144) * __fixdfdi: Soft float library routines. ! (line 87) * __fixdfsi: Soft float library routines. ! (line 80) * __fixdfti: Soft float library routines. ! (line 93) * __fixsfdi: Soft float library routines. ! (line 86) * __fixsfsi: Soft float library routines. ! (line 79) * __fixsfti: Soft float library routines. ! (line 92) * __fixtfdi: Soft float library routines. ! (line 88) * __fixtfsi: Soft float library routines. ! (line 81) * __fixtfti: Soft float library routines. ! (line 94) * __fixunsdfdi: Soft float library routines. ! (line 107) * __fixunsdfsi: Soft float library routines. ! (line 100) * __fixunsdfti: Soft float library routines. ! (line 114) * __fixunssfdi: Soft float library routines. ! (line 106) * __fixunssfsi: Soft float library routines. ! (line 99) * __fixunssfti: Soft float library routines. ! (line 113) * __fixunstfdi: Soft float library routines. ! (line 108) * __fixunstfsi: Soft float library routines. ! (line 101) * __fixunstfti: Soft float library routines. ! (line 115) * __fixunsxfdi: Soft float library routines. ! (line 109) * __fixunsxfsi: Soft float library routines. ! (line 102) * __fixunsxfti: Soft float library routines. ! (line 116) * __fixxfdi: Soft float library routines. ! (line 89) * __fixxfsi: Soft float library routines. ! (line 82) * __fixxfti: Soft float library routines. ! (line 95) * __floatdidf: Soft float library routines. ! (line 127) * __floatdisf: Soft float library routines. ! (line 126) * __floatditf: Soft float library routines. - (line 128) - * __floatdixf: Soft float library routines. (line 129) * __floatsidf: Soft float library routines. ! (line 121) * __floatsisf: Soft float library routines. ! (line 120) * __floatsitf: Soft float library routines. - (line 122) - * __floatsixf: Soft float library routines. (line 123) * __floattidf: Soft float library routines. ! (line 133) * __floattisf: Soft float library routines. ! (line 132) * __floattitf: Soft float library routines. - (line 134) - * __floattixf: Soft float library routines. (line 135) * __floatundidf: Soft float library routines. ! (line 145) * __floatundisf: Soft float library routines. ! (line 144) * __floatunditf: Soft float library routines. - (line 146) - * __floatundixf: Soft float library routines. (line 147) * __floatunsidf: Soft float library routines. ! (line 139) * __floatunsisf: Soft float library routines. ! (line 138) * __floatunsitf: Soft float library routines. - (line 140) - * __floatunsixf: Soft float library routines. (line 141) * __floatuntidf: Soft float library routines. ! (line 151) * __floatuntisf: Soft float library routines. ! (line 150) * __floatuntitf: Soft float library routines. - (line 152) - * __floatuntixf: Soft float library routines. (line 153) * __fractdadf: Fixed-point fractional library routines. ! (line 643) * __fractdadi: Fixed-point fractional library routines. ! (line 640) * __fractdadq: Fixed-point fractional library routines. ! (line 623) * __fractdaha2: Fixed-point fractional library routines. ! (line 624) * __fractdahi: Fixed-point fractional library routines. ! (line 638) * __fractdahq: Fixed-point fractional library routines. ! (line 621) * __fractdaqi: Fixed-point fractional library routines. ! (line 637) * __fractdaqq: Fixed-point fractional library routines. ! (line 620) * __fractdasa2: Fixed-point fractional library routines. ! (line 625) * __fractdasf: Fixed-point fractional library routines. ! (line 642) * __fractdasi: Fixed-point fractional library routines. ! (line 639) * __fractdasq: Fixed-point fractional library routines. ! (line 622) * __fractdata2: Fixed-point fractional library routines. ! (line 626) * __fractdati: Fixed-point fractional library routines. - (line 641) - * __fractdauda: Fixed-point fractional library routines. (line 634) * __fractdaudq: Fixed-point fractional library routines. ! (line 630) * __fractdauha: Fixed-point fractional library routines. ! (line 632) * __fractdauhq: Fixed-point fractional library routines. ! (line 628) * __fractdauqq: Fixed-point fractional library routines. ! (line 627) * __fractdausa: Fixed-point fractional library routines. ! (line 633) * __fractdausq: Fixed-point fractional library routines. ! (line 629) * __fractdauta: Fixed-point fractional library routines. ! (line 635) * __fractdfda: Fixed-point fractional library routines. ! (line 1032) * __fractdfdq: Fixed-point fractional library routines. ! (line 1029) * __fractdfha: Fixed-point fractional library routines. ! (line 1030) * __fractdfhq: Fixed-point fractional library routines. ! (line 1027) * __fractdfqq: Fixed-point fractional library routines. ! (line 1026) * __fractdfsa: Fixed-point fractional library routines. ! (line 1031) * __fractdfsq: Fixed-point fractional library routines. ! (line 1028) * __fractdfta: Fixed-point fractional library routines. ! (line 1033) * __fractdfuda: Fixed-point fractional library routines. ! (line 1040) * __fractdfudq: Fixed-point fractional library routines. ! (line 1037) * __fractdfuha: Fixed-point fractional library routines. ! (line 1038) * __fractdfuhq: Fixed-point fractional library routines. ! (line 1035) * __fractdfuqq: Fixed-point fractional library routines. ! (line 1034) * __fractdfusa: Fixed-point fractional library routines. ! (line 1039) * __fractdfusq: Fixed-point fractional library routines. ! (line 1036) * __fractdfuta: Fixed-point fractional library routines. ! (line 1041) * __fractdida: Fixed-point fractional library routines. ! (line 982) * __fractdidq: Fixed-point fractional library routines. ! (line 979) * __fractdiha: Fixed-point fractional library routines. ! (line 980) * __fractdihq: Fixed-point fractional library routines. ! (line 977) * __fractdiqq: Fixed-point fractional library routines. ! (line 976) * __fractdisa: Fixed-point fractional library routines. ! (line 981) * __fractdisq: Fixed-point fractional library routines. ! (line 978) * __fractdita: Fixed-point fractional library routines. ! (line 983) * __fractdiuda: Fixed-point fractional library routines. ! (line 990) * __fractdiudq: Fixed-point fractional library routines. ! (line 987) * __fractdiuha: Fixed-point fractional library routines. ! (line 988) * __fractdiuhq: Fixed-point fractional library routines. ! (line 985) * __fractdiuqq: Fixed-point fractional library routines. ! (line 984) * __fractdiusa: Fixed-point fractional library routines. ! (line 989) * __fractdiusq: Fixed-point fractional library routines. ! (line 986) * __fractdiuta: Fixed-point fractional library routines. ! (line 991) * __fractdqda: Fixed-point fractional library routines. ! (line 551) * __fractdqdf: Fixed-point fractional library routines. ! (line 573) * __fractdqdi: Fixed-point fractional library routines. ! (line 570) * __fractdqha: Fixed-point fractional library routines. ! (line 549) * __fractdqhi: Fixed-point fractional library routines. ! (line 568) * __fractdqhq2: Fixed-point fractional library routines. ! (line 547) * __fractdqqi: Fixed-point fractional library routines. ! (line 567) * __fractdqqq2: Fixed-point fractional library routines. ! (line 546) * __fractdqsa: Fixed-point fractional library routines. ! (line 550) * __fractdqsf: Fixed-point fractional library routines. ! (line 572) * __fractdqsi: Fixed-point fractional library routines. ! (line 569) * __fractdqsq2: Fixed-point fractional library routines. ! (line 548) * __fractdqta: Fixed-point fractional library routines. ! (line 552) * __fractdqti: Fixed-point fractional library routines. ! (line 571) * __fractdquda: Fixed-point fractional library routines. ! (line 563) * __fractdqudq: Fixed-point fractional library routines. ! (line 558) * __fractdquha: Fixed-point fractional library routines. ! (line 560) * __fractdquhq: Fixed-point fractional library routines. ! (line 555) * __fractdquqq: Fixed-point fractional library routines. ! (line 553) * __fractdqusa: Fixed-point fractional library routines. ! (line 562) * __fractdqusq: Fixed-point fractional library routines. ! (line 556) * __fractdquta: Fixed-point fractional library routines. ! (line 565) * __fracthada2: Fixed-point fractional library routines. ! (line 579) * __fracthadf: Fixed-point fractional library routines. ! (line 597) * __fracthadi: Fixed-point fractional library routines. ! (line 594) * __fracthadq: Fixed-point fractional library routines. ! (line 577) * __fracthahi: Fixed-point fractional library routines. ! (line 592) * __fracthahq: Fixed-point fractional library routines. ! (line 575) * __fracthaqi: Fixed-point fractional library routines. ! (line 591) * __fracthaqq: Fixed-point fractional library routines. ! (line 574) * __fracthasa2: Fixed-point fractional library routines. ! (line 578) * __fracthasf: Fixed-point fractional library routines. ! (line 596) * __fracthasi: Fixed-point fractional library routines. ! (line 593) * __fracthasq: Fixed-point fractional library routines. ! (line 576) * __fracthata2: Fixed-point fractional library routines. ! (line 580) * __fracthati: Fixed-point fractional library routines. - (line 595) - * __fracthauda: Fixed-point fractional library routines. (line 588) * __fracthaudq: Fixed-point fractional library routines. ! (line 584) * __fracthauha: Fixed-point fractional library routines. ! (line 586) * __fracthauhq: Fixed-point fractional library routines. ! (line 582) * __fracthauqq: Fixed-point fractional library routines. ! (line 581) * __fracthausa: Fixed-point fractional library routines. ! (line 587) * __fracthausq: Fixed-point fractional library routines. ! (line 583) * __fracthauta: Fixed-point fractional library routines. ! (line 589) * __fracthida: Fixed-point fractional library routines. ! (line 950) * __fracthidq: Fixed-point fractional library routines. ! (line 947) * __fracthiha: Fixed-point fractional library routines. ! (line 948) * __fracthihq: Fixed-point fractional library routines. ! (line 945) * __fracthiqq: Fixed-point fractional library routines. ! (line 944) * __fracthisa: Fixed-point fractional library routines. ! (line 949) * __fracthisq: Fixed-point fractional library routines. ! (line 946) * __fracthita: Fixed-point fractional library routines. ! (line 951) * __fracthiuda: Fixed-point fractional library routines. ! (line 958) * __fracthiudq: Fixed-point fractional library routines. ! (line 955) * __fracthiuha: Fixed-point fractional library routines. ! (line 956) * __fracthiuhq: Fixed-point fractional library routines. ! (line 953) * __fracthiuqq: Fixed-point fractional library routines. ! (line 952) * __fracthiusa: Fixed-point fractional library routines. ! (line 957) * __fracthiusq: Fixed-point fractional library routines. ! (line 954) * __fracthiuta: Fixed-point fractional library routines. ! (line 959) * __fracthqda: Fixed-point fractional library routines. ! (line 505) * __fracthqdf: Fixed-point fractional library routines. ! (line 521) * __fracthqdi: Fixed-point fractional library routines. ! (line 518) * __fracthqdq2: Fixed-point fractional library routines. ! (line 502) * __fracthqha: Fixed-point fractional library routines. ! (line 503) * __fracthqhi: Fixed-point fractional library routines. ! (line 516) * __fracthqqi: Fixed-point fractional library routines. ! (line 515) * __fracthqqq2: Fixed-point fractional library routines. ! (line 500) * __fracthqsa: Fixed-point fractional library routines. ! (line 504) * __fracthqsf: Fixed-point fractional library routines. ! (line 520) * __fracthqsi: Fixed-point fractional library routines. ! (line 517) * __fracthqsq2: Fixed-point fractional library routines. ! (line 501) * __fracthqta: Fixed-point fractional library routines. ! (line 506) * __fracthqti: Fixed-point fractional library routines. ! (line 519) * __fracthquda: Fixed-point fractional library routines. ! (line 513) * __fracthqudq: Fixed-point fractional library routines. ! (line 510) * __fracthquha: Fixed-point fractional library routines. ! (line 511) * __fracthquhq: Fixed-point fractional library routines. ! (line 508) * __fracthquqq: Fixed-point fractional library routines. ! (line 507) * __fracthqusa: Fixed-point fractional library routines. ! (line 512) * __fracthqusq: Fixed-point fractional library routines. ! (line 509) * __fracthquta: Fixed-point fractional library routines. ! (line 514) * __fractqida: Fixed-point fractional library routines. ! (line 932) * __fractqidq: Fixed-point fractional library routines. ! (line 929) * __fractqiha: Fixed-point fractional library routines. ! (line 930) * __fractqihq: Fixed-point fractional library routines. ! (line 927) * __fractqiqq: Fixed-point fractional library routines. ! (line 926) * __fractqisa: Fixed-point fractional library routines. ! (line 931) * __fractqisq: Fixed-point fractional library routines. ! (line 928) * __fractqita: Fixed-point fractional library routines. ! (line 933) * __fractqiuda: Fixed-point fractional library routines. ! (line 941) * __fractqiudq: Fixed-point fractional library routines. ! (line 937) * __fractqiuha: Fixed-point fractional library routines. ! (line 939) * __fractqiuhq: Fixed-point fractional library routines. ! (line 935) * __fractqiuqq: Fixed-point fractional library routines. ! (line 934) * __fractqiusa: Fixed-point fractional library routines. ! (line 940) * __fractqiusq: Fixed-point fractional library routines. ! (line 936) * __fractqiuta: Fixed-point fractional library routines. ! (line 942) * __fractqqda: Fixed-point fractional library routines. ! (line 481) * __fractqqdf: Fixed-point fractional library routines. ! (line 499) * __fractqqdi: Fixed-point fractional library routines. ! (line 496) * __fractqqdq2: Fixed-point fractional library routines. ! (line 478) * __fractqqha: Fixed-point fractional library routines. ! (line 479) * __fractqqhi: Fixed-point fractional library routines. ! (line 494) * __fractqqhq2: Fixed-point fractional library routines. ! (line 476) * __fractqqqi: Fixed-point fractional library routines. ! (line 493) * __fractqqsa: Fixed-point fractional library routines. ! (line 480) * __fractqqsf: Fixed-point fractional library routines. ! (line 498) * __fractqqsi: Fixed-point fractional library routines. ! (line 495) * __fractqqsq2: Fixed-point fractional library routines. ! (line 477) * __fractqqta: Fixed-point fractional library routines. ! (line 482) * __fractqqti: Fixed-point fractional library routines. - (line 497) - * __fractqquda: Fixed-point fractional library routines. (line 490) * __fractqqudq: Fixed-point fractional library routines. ! (line 486) * __fractqquha: Fixed-point fractional library routines. ! (line 488) * __fractqquhq: Fixed-point fractional library routines. ! (line 484) * __fractqquqq: Fixed-point fractional library routines. ! (line 483) * __fractqqusa: Fixed-point fractional library routines. ! (line 489) * __fractqqusq: Fixed-point fractional library routines. ! (line 485) * __fractqquta: Fixed-point fractional library routines. ! (line 491) * __fractsada2: Fixed-point fractional library routines. ! (line 603) * __fractsadf: Fixed-point fractional library routines. ! (line 619) * __fractsadi: Fixed-point fractional library routines. ! (line 616) * __fractsadq: Fixed-point fractional library routines. ! (line 601) * __fractsaha2: Fixed-point fractional library routines. ! (line 602) * __fractsahi: Fixed-point fractional library routines. ! (line 614) * __fractsahq: Fixed-point fractional library routines. ! (line 599) * __fractsaqi: Fixed-point fractional library routines. ! (line 613) * __fractsaqq: Fixed-point fractional library routines. ! (line 598) * __fractsasf: Fixed-point fractional library routines. ! (line 618) * __fractsasi: Fixed-point fractional library routines. ! (line 615) * __fractsasq: Fixed-point fractional library routines. ! (line 600) * __fractsata2: Fixed-point fractional library routines. ! (line 604) * __fractsati: Fixed-point fractional library routines. ! (line 617) * __fractsauda: Fixed-point fractional library routines. ! (line 611) * __fractsaudq: Fixed-point fractional library routines. ! (line 608) * __fractsauha: Fixed-point fractional library routines. ! (line 609) * __fractsauhq: Fixed-point fractional library routines. ! (line 606) * __fractsauqq: Fixed-point fractional library routines. ! (line 605) * __fractsausa: Fixed-point fractional library routines. ! (line 610) * __fractsausq: Fixed-point fractional library routines. ! (line 607) * __fractsauta: Fixed-point fractional library routines. ! (line 612) * __fractsfda: Fixed-point fractional library routines. ! (line 1016) * __fractsfdq: Fixed-point fractional library routines. ! (line 1013) * __fractsfha: Fixed-point fractional library routines. ! (line 1014) * __fractsfhq: Fixed-point fractional library routines. ! (line 1011) * __fractsfqq: Fixed-point fractional library routines. ! (line 1010) * __fractsfsa: Fixed-point fractional library routines. ! (line 1015) * __fractsfsq: Fixed-point fractional library routines. ! (line 1012) * __fractsfta: Fixed-point fractional library routines. ! (line 1017) * __fractsfuda: Fixed-point fractional library routines. ! (line 1024) * __fractsfudq: Fixed-point fractional library routines. ! (line 1021) * __fractsfuha: Fixed-point fractional library routines. ! (line 1022) * __fractsfuhq: Fixed-point fractional library routines. ! (line 1019) * __fractsfuqq: Fixed-point fractional library routines. ! (line 1018) * __fractsfusa: Fixed-point fractional library routines. ! (line 1023) * __fractsfusq: Fixed-point fractional library routines. ! (line 1020) * __fractsfuta: Fixed-point fractional library routines. ! (line 1025) * __fractsida: Fixed-point fractional library routines. ! (line 966) * __fractsidq: Fixed-point fractional library routines. ! (line 963) * __fractsiha: Fixed-point fractional library routines. ! (line 964) * __fractsihq: Fixed-point fractional library routines. ! (line 961) * __fractsiqq: Fixed-point fractional library routines. ! (line 960) * __fractsisa: Fixed-point fractional library routines. ! (line 965) * __fractsisq: Fixed-point fractional library routines. ! (line 962) * __fractsita: Fixed-point fractional library routines. ! (line 967) * __fractsiuda: Fixed-point fractional library routines. ! (line 974) * __fractsiudq: Fixed-point fractional library routines. ! (line 971) * __fractsiuha: Fixed-point fractional library routines. ! (line 972) * __fractsiuhq: Fixed-point fractional library routines. ! (line 969) * __fractsiuqq: Fixed-point fractional library routines. ! (line 968) * __fractsiusa: Fixed-point fractional library routines. ! (line 973) * __fractsiusq: Fixed-point fractional library routines. ! (line 970) * __fractsiuta: Fixed-point fractional library routines. ! (line 975) * __fractsqda: Fixed-point fractional library routines. ! (line 527) * __fractsqdf: Fixed-point fractional library routines. ! (line 545) * __fractsqdi: Fixed-point fractional library routines. ! (line 542) * __fractsqdq2: Fixed-point fractional library routines. ! (line 524) * __fractsqha: Fixed-point fractional library routines. ! (line 525) * __fractsqhi: Fixed-point fractional library routines. ! (line 540) * __fractsqhq2: Fixed-point fractional library routines. ! (line 523) * __fractsqqi: Fixed-point fractional library routines. ! (line 539) * __fractsqqq2: Fixed-point fractional library routines. ! (line 522) * __fractsqsa: Fixed-point fractional library routines. ! (line 526) * __fractsqsf: Fixed-point fractional library routines. ! (line 544) * __fractsqsi: Fixed-point fractional library routines. ! (line 541) * __fractsqta: Fixed-point fractional library routines. ! (line 528) * __fractsqti: Fixed-point fractional library routines. - (line 543) - * __fractsquda: Fixed-point fractional library routines. (line 536) * __fractsqudq: Fixed-point fractional library routines. ! (line 532) * __fractsquha: Fixed-point fractional library routines. ! (line 534) * __fractsquhq: Fixed-point fractional library routines. ! (line 530) * __fractsquqq: Fixed-point fractional library routines. ! (line 529) * __fractsqusa: Fixed-point fractional library routines. ! (line 535) * __fractsqusq: Fixed-point fractional library routines. ! (line 531) * __fractsquta: Fixed-point fractional library routines. ! (line 537) * __fracttada2: Fixed-point fractional library routines. ! (line 650) * __fracttadf: Fixed-point fractional library routines. ! (line 671) * __fracttadi: Fixed-point fractional library routines. ! (line 668) * __fracttadq: Fixed-point fractional library routines. ! (line 647) * __fracttaha2: Fixed-point fractional library routines. ! (line 648) * __fracttahi: Fixed-point fractional library routines. ! (line 666) * __fracttahq: Fixed-point fractional library routines. ! (line 645) * __fracttaqi: Fixed-point fractional library routines. ! (line 665) * __fracttaqq: Fixed-point fractional library routines. ! (line 644) * __fracttasa2: Fixed-point fractional library routines. ! (line 649) * __fracttasf: Fixed-point fractional library routines. ! (line 670) * __fracttasi: Fixed-point fractional library routines. ! (line 667) * __fracttasq: Fixed-point fractional library routines. ! (line 646) * __fracttati: Fixed-point fractional library routines. ! (line 669) * __fracttauda: Fixed-point fractional library routines. ! (line 661) * __fracttaudq: Fixed-point fractional library routines. ! (line 656) * __fracttauha: Fixed-point fractional library routines. ! (line 658) * __fracttauhq: Fixed-point fractional library routines. ! (line 653) * __fracttauqq: Fixed-point fractional library routines. ! (line 651) * __fracttausa: Fixed-point fractional library routines. ! (line 660) * __fracttausq: Fixed-point fractional library routines. ! (line 654) * __fracttauta: Fixed-point fractional library routines. ! (line 663) * __fracttida: Fixed-point fractional library routines. ! (line 998) * __fracttidq: Fixed-point fractional library routines. ! (line 995) * __fracttiha: Fixed-point fractional library routines. ! (line 996) * __fracttihq: Fixed-point fractional library routines. ! (line 993) * __fracttiqq: Fixed-point fractional library routines. ! (line 992) * __fracttisa: Fixed-point fractional library routines. ! (line 997) * __fracttisq: Fixed-point fractional library routines. ! (line 994) * __fracttita: Fixed-point fractional library routines. ! (line 999) * __fracttiuda: Fixed-point fractional library routines. ! (line 1007) * __fracttiudq: Fixed-point fractional library routines. ! (line 1003) * __fracttiuha: Fixed-point fractional library routines. ! (line 1005) * __fracttiuhq: Fixed-point fractional library routines. ! (line 1001) * __fracttiuqq: Fixed-point fractional library routines. ! (line 1000) * __fracttiusa: Fixed-point fractional library routines. ! (line 1006) * __fracttiusq: Fixed-point fractional library routines. ! (line 1002) * __fracttiuta: Fixed-point fractional library routines. ! (line 1008) * __fractudada: Fixed-point fractional library routines. ! (line 865) * __fractudadf: Fixed-point fractional library routines. ! (line 888) * __fractudadi: Fixed-point fractional library routines. ! (line 885) * __fractudadq: Fixed-point fractional library routines. ! (line 861) * __fractudaha: Fixed-point fractional library routines. ! (line 863) * __fractudahi: Fixed-point fractional library routines. ! (line 883) * __fractudahq: Fixed-point fractional library routines. ! (line 859) * __fractudaqi: Fixed-point fractional library routines. ! (line 882) * __fractudaqq: Fixed-point fractional library routines. ! (line 858) * __fractudasa: Fixed-point fractional library routines. ! (line 864) * __fractudasf: Fixed-point fractional library routines. ! (line 887) * __fractudasi: Fixed-point fractional library routines. ! (line 884) * __fractudasq: Fixed-point fractional library routines. ! (line 860) * __fractudata: Fixed-point fractional library routines. ! (line 866) * __fractudati: Fixed-point fractional library routines. ! (line 886) * __fractudaudq: Fixed-point fractional library routines. ! (line 874) * __fractudauha2: Fixed-point fractional library routines. - (line 876) - * __fractudauhq: Fixed-point fractional library routines. (line 870) * __fractudauqq: Fixed-point fractional library routines. ! (line 868) * __fractudausa2: Fixed-point fractional library routines. - (line 878) - * __fractudausq: Fixed-point fractional library routines. (line 872) * __fractudauta2: Fixed-point fractional library routines. ! (line 880) * __fractudqda: Fixed-point fractional library routines. ! (line 772) * __fractudqdf: Fixed-point fractional library routines. ! (line 798) * __fractudqdi: Fixed-point fractional library routines. ! (line 794) * __fractudqdq: Fixed-point fractional library routines. ! (line 767) * __fractudqha: Fixed-point fractional library routines. ! (line 769) * __fractudqhi: Fixed-point fractional library routines. ! (line 792) * __fractudqhq: Fixed-point fractional library routines. ! (line 764) * __fractudqqi: Fixed-point fractional library routines. ! (line 790) * __fractudqqq: Fixed-point fractional library routines. ! (line 762) * __fractudqsa: Fixed-point fractional library routines. ! (line 771) * __fractudqsf: Fixed-point fractional library routines. ! (line 797) * __fractudqsi: Fixed-point fractional library routines. ! (line 793) * __fractudqsq: Fixed-point fractional library routines. ! (line 765) * __fractudqta: Fixed-point fractional library routines. ! (line 774) * __fractudqti: Fixed-point fractional library routines. ! (line 795) * __fractudquda: Fixed-point fractional library routines. ! (line 786) * __fractudquha: Fixed-point fractional library routines. ! (line 782) * __fractudquhq2: Fixed-point fractional library routines. ! (line 778) * __fractudquqq2: Fixed-point fractional library routines. ! (line 776) * __fractudqusa: Fixed-point fractional library routines. ! (line 784) * __fractudqusq2: Fixed-point fractional library routines. ! (line 780) * __fractudquta: Fixed-point fractional library routines. ! (line 788) * __fractuhada: Fixed-point fractional library routines. ! (line 806) * __fractuhadf: Fixed-point fractional library routines. ! (line 829) * __fractuhadi: Fixed-point fractional library routines. ! (line 826) * __fractuhadq: Fixed-point fractional library routines. ! (line 802) * __fractuhaha: Fixed-point fractional library routines. ! (line 804) * __fractuhahi: Fixed-point fractional library routines. ! (line 824) * __fractuhahq: Fixed-point fractional library routines. ! (line 800) * __fractuhaqi: Fixed-point fractional library routines. ! (line 823) * __fractuhaqq: Fixed-point fractional library routines. ! (line 799) * __fractuhasa: Fixed-point fractional library routines. ! (line 805) * __fractuhasf: Fixed-point fractional library routines. ! (line 828) * __fractuhasi: Fixed-point fractional library routines. ! (line 825) * __fractuhasq: Fixed-point fractional library routines. ! (line 801) * __fractuhata: Fixed-point fractional library routines. ! (line 807) * __fractuhati: Fixed-point fractional library routines. ! (line 827) * __fractuhauda2: Fixed-point fractional library routines. ! (line 819) * __fractuhaudq: Fixed-point fractional library routines. ! (line 815) * __fractuhauhq: Fixed-point fractional library routines. ! (line 811) * __fractuhauqq: Fixed-point fractional library routines. ! (line 809) * __fractuhausa2: Fixed-point fractional library routines. ! (line 817) * __fractuhausq: Fixed-point fractional library routines. ! (line 813) * __fractuhauta2: Fixed-point fractional library routines. ! (line 821) * __fractuhqda: Fixed-point fractional library routines. ! (line 709) * __fractuhqdf: Fixed-point fractional library routines. ! (line 730) * __fractuhqdi: Fixed-point fractional library routines. ! (line 727) * __fractuhqdq: Fixed-point fractional library routines. ! (line 706) * __fractuhqha: Fixed-point fractional library routines. ! (line 707) * __fractuhqhi: Fixed-point fractional library routines. ! (line 725) * __fractuhqhq: Fixed-point fractional library routines. ! (line 704) * __fractuhqqi: Fixed-point fractional library routines. ! (line 724) * __fractuhqqq: Fixed-point fractional library routines. ! (line 703) * __fractuhqsa: Fixed-point fractional library routines. ! (line 708) * __fractuhqsf: Fixed-point fractional library routines. ! (line 729) * __fractuhqsi: Fixed-point fractional library routines. ! (line 726) * __fractuhqsq: Fixed-point fractional library routines. ! (line 705) * __fractuhqta: Fixed-point fractional library routines. ! (line 710) * __fractuhqti: Fixed-point fractional library routines. ! (line 728) * __fractuhquda: Fixed-point fractional library routines. ! (line 720) * __fractuhqudq2: Fixed-point fractional library routines. ! (line 715) * __fractuhquha: Fixed-point fractional library routines. - (line 717) - * __fractuhquqq2: Fixed-point fractional library routines. (line 711) * __fractuhqusa: Fixed-point fractional library routines. ! (line 719) * __fractuhqusq2: Fixed-point fractional library routines. ! (line 713) * __fractuhquta: Fixed-point fractional library routines. ! (line 722) * __fractunsdadi: Fixed-point fractional library routines. ! (line 1562) * __fractunsdahi: Fixed-point fractional library routines. ! (line 1560) * __fractunsdaqi: Fixed-point fractional library routines. ! (line 1559) * __fractunsdasi: Fixed-point fractional library routines. ! (line 1561) * __fractunsdati: Fixed-point fractional library routines. ! (line 1563) * __fractunsdida: Fixed-point fractional library routines. ! (line 1714) * __fractunsdidq: Fixed-point fractional library routines. ! (line 1711) * __fractunsdiha: Fixed-point fractional library routines. ! (line 1712) * __fractunsdihq: Fixed-point fractional library routines. ! (line 1709) * __fractunsdiqq: Fixed-point fractional library routines. ! (line 1708) * __fractunsdisa: Fixed-point fractional library routines. ! (line 1713) * __fractunsdisq: Fixed-point fractional library routines. ! (line 1710) * __fractunsdita: Fixed-point fractional library routines. ! (line 1715) * __fractunsdiuda: Fixed-point fractional library routines. ! (line 1726) * __fractunsdiudq: Fixed-point fractional library routines. ! (line 1721) * __fractunsdiuha: Fixed-point fractional library routines. ! (line 1723) * __fractunsdiuhq: Fixed-point fractional library routines. ! (line 1718) * __fractunsdiuqq: Fixed-point fractional library routines. ! (line 1716) * __fractunsdiusa: Fixed-point fractional library routines. ! (line 1725) * __fractunsdiusq: Fixed-point fractional library routines. ! (line 1719) * __fractunsdiuta: Fixed-point fractional library routines. ! (line 1728) * __fractunsdqdi: Fixed-point fractional library routines. ! (line 1546) * __fractunsdqhi: Fixed-point fractional library routines. ! (line 1544) * __fractunsdqqi: Fixed-point fractional library routines. ! (line 1543) * __fractunsdqsi: Fixed-point fractional library routines. ! (line 1545) * __fractunsdqti: Fixed-point fractional library routines. ! (line 1547) * __fractunshadi: Fixed-point fractional library routines. ! (line 1552) * __fractunshahi: Fixed-point fractional library routines. ! (line 1550) * __fractunshaqi: Fixed-point fractional library routines. ! (line 1549) * __fractunshasi: Fixed-point fractional library routines. ! (line 1551) * __fractunshati: Fixed-point fractional library routines. ! (line 1553) * __fractunshida: Fixed-point fractional library routines. ! (line 1670) * __fractunshidq: Fixed-point fractional library routines. ! (line 1667) * __fractunshiha: Fixed-point fractional library routines. ! (line 1668) * __fractunshihq: Fixed-point fractional library routines. ! (line 1665) * __fractunshiqq: Fixed-point fractional library routines. ! (line 1664) * __fractunshisa: Fixed-point fractional library routines. ! (line 1669) * __fractunshisq: Fixed-point fractional library routines. ! (line 1666) * __fractunshita: Fixed-point fractional library routines. ! (line 1671) * __fractunshiuda: Fixed-point fractional library routines. ! (line 1682) * __fractunshiudq: Fixed-point fractional library routines. ! (line 1677) * __fractunshiuha: Fixed-point fractional library routines. ! (line 1679) * __fractunshiuhq: Fixed-point fractional library routines. ! (line 1674) * __fractunshiuqq: Fixed-point fractional library routines. ! (line 1672) * __fractunshiusa: Fixed-point fractional library routines. ! (line 1681) * __fractunshiusq: Fixed-point fractional library routines. ! (line 1675) * __fractunshiuta: Fixed-point fractional library routines. ! (line 1684) * __fractunshqdi: Fixed-point fractional library routines. ! (line 1536) * __fractunshqhi: Fixed-point fractional library routines. ! (line 1534) * __fractunshqqi: Fixed-point fractional library routines. ! (line 1533) * __fractunshqsi: Fixed-point fractional library routines. ! (line 1535) * __fractunshqti: Fixed-point fractional library routines. ! (line 1537) * __fractunsqida: Fixed-point fractional library routines. ! (line 1648) * __fractunsqidq: Fixed-point fractional library routines. ! (line 1645) * __fractunsqiha: Fixed-point fractional library routines. ! (line 1646) * __fractunsqihq: Fixed-point fractional library routines. ! (line 1643) * __fractunsqiqq: Fixed-point fractional library routines. ! (line 1642) * __fractunsqisa: Fixed-point fractional library routines. ! (line 1647) * __fractunsqisq: Fixed-point fractional library routines. ! (line 1644) * __fractunsqita: Fixed-point fractional library routines. ! (line 1649) * __fractunsqiuda: Fixed-point fractional library routines. ! (line 1660) * __fractunsqiudq: Fixed-point fractional library routines. ! (line 1655) * __fractunsqiuha: Fixed-point fractional library routines. ! (line 1657) * __fractunsqiuhq: Fixed-point fractional library routines. ! (line 1652) * __fractunsqiuqq: Fixed-point fractional library routines. ! (line 1650) * __fractunsqiusa: Fixed-point fractional library routines. ! (line 1659) * __fractunsqiusq: Fixed-point fractional library routines. ! (line 1653) * __fractunsqiuta: Fixed-point fractional library routines. ! (line 1662) * __fractunsqqdi: Fixed-point fractional library routines. ! (line 1531) * __fractunsqqhi: Fixed-point fractional library routines. ! (line 1529) * __fractunsqqqi: Fixed-point fractional library routines. ! (line 1528) * __fractunsqqsi: Fixed-point fractional library routines. ! (line 1530) * __fractunsqqti: Fixed-point fractional library routines. ! (line 1532) * __fractunssadi: Fixed-point fractional library routines. ! (line 1557) * __fractunssahi: Fixed-point fractional library routines. ! (line 1555) * __fractunssaqi: Fixed-point fractional library routines. ! (line 1554) * __fractunssasi: Fixed-point fractional library routines. ! (line 1556) * __fractunssati: Fixed-point fractional library routines. ! (line 1558) * __fractunssida: Fixed-point fractional library routines. ! (line 1692) * __fractunssidq: Fixed-point fractional library routines. ! (line 1689) * __fractunssiha: Fixed-point fractional library routines. ! (line 1690) * __fractunssihq: Fixed-point fractional library routines. ! (line 1687) * __fractunssiqq: Fixed-point fractional library routines. ! (line 1686) * __fractunssisa: Fixed-point fractional library routines. ! (line 1691) * __fractunssisq: Fixed-point fractional library routines. ! (line 1688) * __fractunssita: Fixed-point fractional library routines. ! (line 1693) * __fractunssiuda: Fixed-point fractional library routines. ! (line 1704) * __fractunssiudq: Fixed-point fractional library routines. ! (line 1699) * __fractunssiuha: Fixed-point fractional library routines. ! (line 1701) * __fractunssiuhq: Fixed-point fractional library routines. ! (line 1696) * __fractunssiuqq: Fixed-point fractional library routines. ! (line 1694) * __fractunssiusa: Fixed-point fractional library routines. ! (line 1703) * __fractunssiusq: Fixed-point fractional library routines. ! (line 1697) * __fractunssiuta: Fixed-point fractional library routines. ! (line 1706) * __fractunssqdi: Fixed-point fractional library routines. ! (line 1541) * __fractunssqhi: Fixed-point fractional library routines. ! (line 1539) * __fractunssqqi: Fixed-point fractional library routines. ! (line 1538) * __fractunssqsi: Fixed-point fractional library routines. ! (line 1540) * __fractunssqti: Fixed-point fractional library routines. ! (line 1542) * __fractunstadi: Fixed-point fractional library routines. ! (line 1567) * __fractunstahi: Fixed-point fractional library routines. ! (line 1565) * __fractunstaqi: Fixed-point fractional library routines. ! (line 1564) * __fractunstasi: Fixed-point fractional library routines. ! (line 1566) * __fractunstati: Fixed-point fractional library routines. ! (line 1568) * __fractunstida: Fixed-point fractional library routines. ! (line 1737) * __fractunstidq: Fixed-point fractional library routines. ! (line 1733) * __fractunstiha: Fixed-point fractional library routines. ! (line 1735) * __fractunstihq: Fixed-point fractional library routines. ! (line 1731) * __fractunstiqq: Fixed-point fractional library routines. ! (line 1730) * __fractunstisa: Fixed-point fractional library routines. ! (line 1736) * __fractunstisq: Fixed-point fractional library routines. ! (line 1732) * __fractunstita: Fixed-point fractional library routines. ! (line 1738) * __fractunstiuda: Fixed-point fractional library routines. - (line 1752) - * __fractunstiudq: Fixed-point fractional library routines. (line 1746) * __fractunstiuha: Fixed-point fractional library routines. - (line 1748) - * __fractunstiuhq: Fixed-point fractional library routines. (line 1742) * __fractunstiuqq: Fixed-point fractional library routines. ! (line 1740) * __fractunstiusa: Fixed-point fractional library routines. - (line 1750) - * __fractunstiusq: Fixed-point fractional library routines. (line 1744) * __fractunstiuta: Fixed-point fractional library routines. ! (line 1754) * __fractunsudadi: Fixed-point fractional library routines. ! (line 1628) * __fractunsudahi: Fixed-point fractional library routines. ! (line 1624) * __fractunsudaqi: Fixed-point fractional library routines. ! (line 1622) * __fractunsudasi: Fixed-point fractional library routines. ! (line 1626) * __fractunsudati: Fixed-point fractional library routines. ! (line 1630) * __fractunsudqdi: Fixed-point fractional library routines. ! (line 1602) * __fractunsudqhi: Fixed-point fractional library routines. ! (line 1598) * __fractunsudqqi: Fixed-point fractional library routines. ! (line 1596) * __fractunsudqsi: Fixed-point fractional library routines. ! (line 1600) * __fractunsudqti: Fixed-point fractional library routines. ! (line 1604) * __fractunsuhadi: Fixed-point fractional library routines. ! (line 1612) * __fractunsuhahi: Fixed-point fractional library routines. ! (line 1608) * __fractunsuhaqi: Fixed-point fractional library routines. ! (line 1606) * __fractunsuhasi: Fixed-point fractional library routines. ! (line 1610) * __fractunsuhati: Fixed-point fractional library routines. ! (line 1614) * __fractunsuhqdi: Fixed-point fractional library routines. ! (line 1583) * __fractunsuhqhi: Fixed-point fractional library routines. ! (line 1581) * __fractunsuhqqi: Fixed-point fractional library routines. ! (line 1580) * __fractunsuhqsi: Fixed-point fractional library routines. ! (line 1582) * __fractunsuhqti: Fixed-point fractional library routines. ! (line 1584) * __fractunsuqqdi: Fixed-point fractional library routines. ! (line 1576) * __fractunsuqqhi: Fixed-point fractional library routines. ! (line 1572) * __fractunsuqqqi: Fixed-point fractional library routines. ! (line 1570) * __fractunsuqqsi: Fixed-point fractional library routines. ! (line 1574) * __fractunsuqqti: Fixed-point fractional library routines. ! (line 1578) * __fractunsusadi: Fixed-point fractional library routines. ! (line 1619) * __fractunsusahi: Fixed-point fractional library routines. ! (line 1617) * __fractunsusaqi: Fixed-point fractional library routines. ! (line 1616) * __fractunsusasi: Fixed-point fractional library routines. ! (line 1618) * __fractunsusati: Fixed-point fractional library routines. ! (line 1620) * __fractunsusqdi: Fixed-point fractional library routines. ! (line 1592) * __fractunsusqhi: Fixed-point fractional library routines. ! (line 1588) * __fractunsusqqi: Fixed-point fractional library routines. ! (line 1586) * __fractunsusqsi: Fixed-point fractional library routines. ! (line 1590) * __fractunsusqti: Fixed-point fractional library routines. ! (line 1594) * __fractunsutadi: Fixed-point fractional library routines. ! (line 1638) * __fractunsutahi: Fixed-point fractional library routines. ! (line 1634) * __fractunsutaqi: Fixed-point fractional library routines. ! (line 1632) * __fractunsutasi: Fixed-point fractional library routines. ! (line 1636) * __fractunsutati: Fixed-point fractional library routines. ! (line 1640) * __fractuqqda: Fixed-point fractional library routines. ! (line 679) * __fractuqqdf: Fixed-point fractional library routines. ! (line 702) * __fractuqqdi: Fixed-point fractional library routines. ! (line 699) * __fractuqqdq: Fixed-point fractional library routines. ! (line 675) * __fractuqqha: Fixed-point fractional library routines. ! (line 677) * __fractuqqhi: Fixed-point fractional library routines. ! (line 697) * __fractuqqhq: Fixed-point fractional library routines. ! (line 673) * __fractuqqqi: Fixed-point fractional library routines. ! (line 696) * __fractuqqqq: Fixed-point fractional library routines. ! (line 672) * __fractuqqsa: Fixed-point fractional library routines. ! (line 678) * __fractuqqsf: Fixed-point fractional library routines. ! (line 701) * __fractuqqsi: Fixed-point fractional library routines. ! (line 698) * __fractuqqsq: Fixed-point fractional library routines. ! (line 674) * __fractuqqta: Fixed-point fractional library routines. ! (line 680) * __fractuqqti: Fixed-point fractional library routines. ! (line 700) * __fractuqquda: Fixed-point fractional library routines. - (line 692) - * __fractuqqudq2: Fixed-point fractional library routines. (line 686) * __fractuqquha: Fixed-point fractional library routines. - (line 688) - * __fractuqquhq2: Fixed-point fractional library routines. (line 682) * __fractuqqusa: Fixed-point fractional library routines. - (line 690) - * __fractuqqusq2: Fixed-point fractional library routines. (line 684) * __fractuqquta: Fixed-point fractional library routines. ! (line 694) * __fractusada: Fixed-point fractional library routines. ! (line 836) * __fractusadf: Fixed-point fractional library routines. ! (line 857) * __fractusadi: Fixed-point fractional library routines. ! (line 854) * __fractusadq: Fixed-point fractional library routines. ! (line 833) * __fractusaha: Fixed-point fractional library routines. ! (line 834) * __fractusahi: Fixed-point fractional library routines. ! (line 852) * __fractusahq: Fixed-point fractional library routines. ! (line 831) * __fractusaqi: Fixed-point fractional library routines. ! (line 851) * __fractusaqq: Fixed-point fractional library routines. ! (line 830) * __fractusasa: Fixed-point fractional library routines. ! (line 835) * __fractusasf: Fixed-point fractional library routines. ! (line 856) * __fractusasi: Fixed-point fractional library routines. ! (line 853) * __fractusasq: Fixed-point fractional library routines. ! (line 832) * __fractusata: Fixed-point fractional library routines. ! (line 837) * __fractusati: Fixed-point fractional library routines. ! (line 855) * __fractusauda2: Fixed-point fractional library routines. ! (line 847) * __fractusaudq: Fixed-point fractional library routines. ! (line 843) * __fractusauha2: Fixed-point fractional library routines. ! (line 845) * __fractusauhq: Fixed-point fractional library routines. ! (line 840) * __fractusauqq: Fixed-point fractional library routines. ! (line 838) * __fractusausq: Fixed-point fractional library routines. ! (line 841) * __fractusauta2: Fixed-point fractional library routines. ! (line 849) * __fractusqda: Fixed-point fractional library routines. ! (line 738) * __fractusqdf: Fixed-point fractional library routines. ! (line 761) * __fractusqdi: Fixed-point fractional library routines. ! (line 758) * __fractusqdq: Fixed-point fractional library routines. ! (line 734) * __fractusqha: Fixed-point fractional library routines. ! (line 736) * __fractusqhi: Fixed-point fractional library routines. ! (line 756) * __fractusqhq: Fixed-point fractional library routines. ! (line 732) * __fractusqqi: Fixed-point fractional library routines. ! (line 755) * __fractusqqq: Fixed-point fractional library routines. ! (line 731) * __fractusqsa: Fixed-point fractional library routines. ! (line 737) * __fractusqsf: Fixed-point fractional library routines. ! (line 760) * __fractusqsi: Fixed-point fractional library routines. ! (line 757) * __fractusqsq: Fixed-point fractional library routines. ! (line 733) * __fractusqta: Fixed-point fractional library routines. ! (line 739) * __fractusqti: Fixed-point fractional library routines. ! (line 759) * __fractusquda: Fixed-point fractional library routines. - (line 751) - * __fractusqudq2: Fixed-point fractional library routines. (line 745) * __fractusquha: Fixed-point fractional library routines. ! (line 747) * __fractusquhq2: Fixed-point fractional library routines. ! (line 743) * __fractusquqq2: Fixed-point fractional library routines. ! (line 741) * __fractusqusa: Fixed-point fractional library routines. ! (line 749) * __fractusquta: Fixed-point fractional library routines. ! (line 753) * __fractutada: Fixed-point fractional library routines. ! (line 899) * __fractutadf: Fixed-point fractional library routines. ! (line 925) * __fractutadi: Fixed-point fractional library routines. ! (line 921) * __fractutadq: Fixed-point fractional library routines. ! (line 894) * __fractutaha: Fixed-point fractional library routines. ! (line 896) * __fractutahi: Fixed-point fractional library routines. ! (line 919) * __fractutahq: Fixed-point fractional library routines. ! (line 891) * __fractutaqi: Fixed-point fractional library routines. ! (line 917) * __fractutaqq: Fixed-point fractional library routines. ! (line 889) * __fractutasa: Fixed-point fractional library routines. ! (line 898) * __fractutasf: Fixed-point fractional library routines. ! (line 924) * __fractutasi: Fixed-point fractional library routines. ! (line 920) * __fractutasq: Fixed-point fractional library routines. ! (line 892) * __fractutata: Fixed-point fractional library routines. ! (line 901) * __fractutati: Fixed-point fractional library routines. ! (line 922) * __fractutauda2: Fixed-point fractional library routines. - (line 915) - * __fractutaudq: Fixed-point fractional library routines. (line 909) * __fractutauha2: Fixed-point fractional library routines. - (line 911) - * __fractutauhq: Fixed-point fractional library routines. (line 905) * __fractutauqq: Fixed-point fractional library routines. ! (line 903) * __fractutausa2: Fixed-point fractional library routines. - (line 913) - * __fractutausq: Fixed-point fractional library routines. (line 907) * __gedf2: Soft float library routines. ! (line 205) * __gesf2: Soft float library routines. ! (line 204) * __getf2: Soft float library routines. ! (line 206) * __gtdf2: Soft float library routines. ! (line 223) * __gtsf2: Soft float library routines. ! (line 222) * __gttf2: Soft float library routines. ! (line 224) * __ledf2: Soft float library routines. ! (line 217) * __lesf2: Soft float library routines. ! (line 216) * __letf2: Soft float library routines. ! (line 218) * __lshrdi3: Integer library routines. ! (line 30) * __lshrsi3: Integer library routines. ! (line 29) * __lshrti3: Integer library routines. ! (line 31) * __lshruda3: Fixed-point fractional library routines. - (line 396) - * __lshrudq3: Fixed-point fractional library routines. (line 390) * __lshruha3: Fixed-point fractional library routines. - (line 392) - * __lshruhq3: Fixed-point fractional library routines. (line 386) * __lshruqq3: Fixed-point fractional library routines. ! (line 384) * __lshrusa3: Fixed-point fractional library routines. - (line 394) - * __lshrusq3: Fixed-point fractional library routines. (line 388) * __lshruta3: Fixed-point fractional library routines. ! (line 398) * __ltdf2: Soft float library routines. ! (line 211) * __ltsf2: Soft float library routines. ! (line 210) * __lttf2: Soft float library routines. ! (line 212) * __main: Collect2. (line 15) * __moddi3: Integer library routines. ! (line 36) * __modsi3: Integer library routines. ! (line 35) * __modti3: Integer library routines. ! (line 37) * __morestack_current_segment: Miscellaneous routines. - (line 45) - * __morestack_initial_sp: Miscellaneous routines. (line 46) * __morestack_segments: Miscellaneous routines. ! (line 44) * __mulda3: Fixed-point fractional library routines. ! (line 178) * __muldc3: Soft float library routines. ! (line 239) * __muldf3: Soft float library routines. ! (line 39) * __muldi3: Integer library routines. ! (line 42) * __muldq3: Fixed-point fractional library routines. ! (line 165) * __mulha3: Fixed-point fractional library routines. ! (line 175) * __mulhq3: Fixed-point fractional library routines. ! (line 163) * __mulqq3: Fixed-point fractional library routines. ! (line 161) * __mulsa3: Fixed-point fractional library routines. ! (line 177) * __mulsc3: Soft float library routines. ! (line 237) * __mulsf3: Soft float library routines. ! (line 38) * __mulsi3: Integer library routines. ! (line 41) * __mulsq3: Fixed-point fractional library routines. ! (line 164) * __multa3: Fixed-point fractional library routines. ! (line 179) * __multc3: Soft float library routines. ! (line 241) * __multf3: Soft float library routines. ! (line 40) * __multi3: Integer library routines. ! (line 43) * __muluda3: Fixed-point fractional library routines. ! (line 185) * __muludq3: Fixed-point fractional library routines. ! (line 173) * __muluha3: Fixed-point fractional library routines. ! (line 181) * __muluhq3: Fixed-point fractional library routines. ! (line 169) * __muluqq3: Fixed-point fractional library routines. ! (line 167) * __mulusa3: Fixed-point fractional library routines. ! (line 183) * __mulusq3: Fixed-point fractional library routines. ! (line 171) * __muluta3: Fixed-point fractional library routines. ! (line 187) * __mulvdi3: Integer library routines. ! (line 114) * __mulvsi3: Integer library routines. ! (line 113) * __mulxc3: Soft float library routines. ! (line 243) * __mulxf3: Soft float library routines. ! (line 42) * __nedf2: Soft float library routines. ! (line 199) * __negda2: Fixed-point fractional library routines. ! (line 306) * __negdf2: Soft float library routines. ! (line 55) * __negdi2: Integer library routines. ! (line 46) * __negdq2: Fixed-point fractional library routines. ! (line 296) * __negha2: Fixed-point fractional library routines. ! (line 304) * __neghq2: Fixed-point fractional library routines. ! (line 294) * __negqq2: Fixed-point fractional library routines. ! (line 293) * __negsa2: Fixed-point fractional library routines. ! (line 305) * __negsf2: Soft float library routines. ! (line 54) * __negsq2: Fixed-point fractional library routines. ! (line 295) * __negta2: Fixed-point fractional library routines. ! (line 307) * __negtf2: Soft float library routines. ! (line 56) * __negti2: Integer library routines. ! (line 47) * __neguda2: Fixed-point fractional library routines. ! (line 311) * __negudq2: Fixed-point fractional library routines. ! (line 302) * __neguha2: Fixed-point fractional library routines. ! (line 308) * __neguhq2: Fixed-point fractional library routines. ! (line 299) * __neguqq2: Fixed-point fractional library routines. ! (line 297) * __negusa2: Fixed-point fractional library routines. ! (line 310) * __negusq2: Fixed-point fractional library routines. ! (line 300) * __neguta2: Fixed-point fractional library routines. ! (line 313) * __negvdi2: Integer library routines. ! (line 118) * __negvsi2: Integer library routines. ! (line 117) * __negxf2: Soft float library routines. ! (line 57) * __nesf2: Soft float library routines. ! (line 198) * __netf2: Soft float library routines. ! (line 200) * __paritydi2: Integer library routines. ! (line 150) * __paritysi2: Integer library routines. ! (line 149) * __parityti2: Integer library routines. ! (line 151) * __popcountdi2: Integer library routines. ! (line 156) * __popcountsi2: Integer library routines. ! (line 155) * __popcountti2: Integer library routines. ! (line 157) * __powidf2: Soft float library routines. ! (line 232) * __powisf2: Soft float library routines. ! (line 231) * __powitf2: Soft float library routines. - (line 233) - * __powixf2: Soft float library routines. (line 234) * __satfractdadq: Fixed-point fractional library routines. ! (line 1160) * __satfractdaha2: Fixed-point fractional library routines. ! (line 1161) * __satfractdahq: Fixed-point fractional library routines. ! (line 1158) * __satfractdaqq: Fixed-point fractional library routines. ! (line 1157) * __satfractdasa2: Fixed-point fractional library routines. ! (line 1162) * __satfractdasq: Fixed-point fractional library routines. ! (line 1159) * __satfractdata2: Fixed-point fractional library routines. ! (line 1163) * __satfractdauda: Fixed-point fractional library routines. ! (line 1173) * __satfractdaudq: Fixed-point fractional library routines. ! (line 1168) * __satfractdauha: Fixed-point fractional library routines. ! (line 1170) * __satfractdauhq: Fixed-point fractional library routines. ! (line 1166) * __satfractdauqq: Fixed-point fractional library routines. ! (line 1164) * __satfractdausa: Fixed-point fractional library routines. ! (line 1172) * __satfractdausq: Fixed-point fractional library routines. ! (line 1167) * __satfractdauta: Fixed-point fractional library routines. ! (line 1174) * __satfractdfda: Fixed-point fractional library routines. ! (line 1513) * __satfractdfdq: Fixed-point fractional library routines. ! (line 1510) * __satfractdfha: Fixed-point fractional library routines. ! (line 1511) * __satfractdfhq: Fixed-point fractional library routines. ! (line 1508) * __satfractdfqq: Fixed-point fractional library routines. ! (line 1507) * __satfractdfsa: Fixed-point fractional library routines. ! (line 1512) * __satfractdfsq: Fixed-point fractional library routines. ! (line 1509) * __satfractdfta: Fixed-point fractional library routines. ! (line 1514) * __satfractdfuda: Fixed-point fractional library routines. ! (line 1522) * __satfractdfudq: Fixed-point fractional library routines. ! (line 1518) * __satfractdfuha: Fixed-point fractional library routines. ! (line 1520) * __satfractdfuhq: Fixed-point fractional library routines. ! (line 1516) * __satfractdfuqq: Fixed-point fractional library routines. ! (line 1515) * __satfractdfusa: Fixed-point fractional library routines. ! (line 1521) * __satfractdfusq: Fixed-point fractional library routines. ! (line 1517) * __satfractdfuta: Fixed-point fractional library routines. ! (line 1523) * __satfractdida: Fixed-point fractional library routines. ! (line 1463) * __satfractdidq: Fixed-point fractional library routines. ! (line 1460) * __satfractdiha: Fixed-point fractional library routines. ! (line 1461) * __satfractdihq: Fixed-point fractional library routines. ! (line 1458) * __satfractdiqq: Fixed-point fractional library routines. ! (line 1457) * __satfractdisa: Fixed-point fractional library routines. ! (line 1462) * __satfractdisq: Fixed-point fractional library routines. ! (line 1459) * __satfractdita: Fixed-point fractional library routines. ! (line 1464) * __satfractdiuda: Fixed-point fractional library routines. ! (line 1471) * __satfractdiudq: Fixed-point fractional library routines. ! (line 1468) * __satfractdiuha: Fixed-point fractional library routines. ! (line 1469) * __satfractdiuhq: Fixed-point fractional library routines. ! (line 1466) * __satfractdiuqq: Fixed-point fractional library routines. ! (line 1465) * __satfractdiusa: Fixed-point fractional library routines. ! (line 1470) * __satfractdiusq: Fixed-point fractional library routines. ! (line 1467) * __satfractdiuta: Fixed-point fractional library routines. ! (line 1472) * __satfractdqda: Fixed-point fractional library routines. ! (line 1105) * __satfractdqha: Fixed-point fractional library routines. ! (line 1103) * __satfractdqhq2: Fixed-point fractional library routines. ! (line 1101) * __satfractdqqq2: Fixed-point fractional library routines. ! (line 1100) * __satfractdqsa: Fixed-point fractional library routines. ! (line 1104) * __satfractdqsq2: Fixed-point fractional library routines. ! (line 1102) * __satfractdqta: Fixed-point fractional library routines. ! (line 1106) * __satfractdquda: Fixed-point fractional library routines. ! (line 1117) * __satfractdqudq: Fixed-point fractional library routines. ! (line 1112) * __satfractdquha: Fixed-point fractional library routines. ! (line 1114) * __satfractdquhq: Fixed-point fractional library routines. ! (line 1109) * __satfractdquqq: Fixed-point fractional library routines. ! (line 1107) * __satfractdqusa: Fixed-point fractional library routines. ! (line 1116) * __satfractdqusq: Fixed-point fractional library routines. ! (line 1110) * __satfractdquta: Fixed-point fractional library routines. ! (line 1119) * __satfracthada2: Fixed-point fractional library routines. ! (line 1126) * __satfracthadq: Fixed-point fractional library routines. ! (line 1124) * __satfracthahq: Fixed-point fractional library routines. ! (line 1122) * __satfracthaqq: Fixed-point fractional library routines. ! (line 1121) * __satfracthasa2: Fixed-point fractional library routines. ! (line 1125) * __satfracthasq: Fixed-point fractional library routines. ! (line 1123) * __satfracthata2: Fixed-point fractional library routines. ! (line 1127) * __satfracthauda: Fixed-point fractional library routines. ! (line 1138) * __satfracthaudq: Fixed-point fractional library routines. ! (line 1133) * __satfracthauha: Fixed-point fractional library routines. ! (line 1135) * __satfracthauhq: Fixed-point fractional library routines. ! (line 1130) * __satfracthauqq: Fixed-point fractional library routines. ! (line 1128) * __satfracthausa: Fixed-point fractional library routines. ! (line 1137) * __satfracthausq: Fixed-point fractional library routines. ! (line 1131) * __satfracthauta: Fixed-point fractional library routines. ! (line 1140) * __satfracthida: Fixed-point fractional library routines. ! (line 1431) * __satfracthidq: Fixed-point fractional library routines. ! (line 1428) * __satfracthiha: Fixed-point fractional library routines. ! (line 1429) * __satfracthihq: Fixed-point fractional library routines. ! (line 1426) * __satfracthiqq: Fixed-point fractional library routines. ! (line 1425) * __satfracthisa: Fixed-point fractional library routines. ! (line 1430) * __satfracthisq: Fixed-point fractional library routines. ! (line 1427) * __satfracthita: Fixed-point fractional library routines. ! (line 1432) * __satfracthiuda: Fixed-point fractional library routines. ! (line 1439) * __satfracthiudq: Fixed-point fractional library routines. ! (line 1436) * __satfracthiuha: Fixed-point fractional library routines. ! (line 1437) * __satfracthiuhq: Fixed-point fractional library routines. ! (line 1434) * __satfracthiuqq: Fixed-point fractional library routines. ! (line 1433) * __satfracthiusa: Fixed-point fractional library routines. ! (line 1438) * __satfracthiusq: Fixed-point fractional library routines. ! (line 1435) * __satfracthiuta: Fixed-point fractional library routines. ! (line 1440) * __satfracthqda: Fixed-point fractional library routines. ! (line 1071) * __satfracthqdq2: Fixed-point fractional library routines. ! (line 1068) * __satfracthqha: Fixed-point fractional library routines. ! (line 1069) * __satfracthqqq2: Fixed-point fractional library routines. ! (line 1066) * __satfracthqsa: Fixed-point fractional library routines. ! (line 1070) * __satfracthqsq2: Fixed-point fractional library routines. ! (line 1067) * __satfracthqta: Fixed-point fractional library routines. ! (line 1072) * __satfracthquda: Fixed-point fractional library routines. ! (line 1079) * __satfracthqudq: Fixed-point fractional library routines. ! (line 1076) * __satfracthquha: Fixed-point fractional library routines. ! (line 1077) * __satfracthquhq: Fixed-point fractional library routines. ! (line 1074) * __satfracthquqq: Fixed-point fractional library routines. ! (line 1073) * __satfracthqusa: Fixed-point fractional library routines. ! (line 1078) * __satfracthqusq: Fixed-point fractional library routines. ! (line 1075) * __satfracthquta: Fixed-point fractional library routines. ! (line 1080) * __satfractqida: Fixed-point fractional library routines. ! (line 1409) * __satfractqidq: Fixed-point fractional library routines. ! (line 1406) * __satfractqiha: Fixed-point fractional library routines. ! (line 1407) * __satfractqihq: Fixed-point fractional library routines. ! (line 1404) * __satfractqiqq: Fixed-point fractional library routines. ! (line 1403) * __satfractqisa: Fixed-point fractional library routines. ! (line 1408) * __satfractqisq: Fixed-point fractional library routines. ! (line 1405) * __satfractqita: Fixed-point fractional library routines. ! (line 1410) * __satfractqiuda: Fixed-point fractional library routines. ! (line 1421) * __satfractqiudq: Fixed-point fractional library routines. ! (line 1416) * __satfractqiuha: Fixed-point fractional library routines. ! (line 1418) * __satfractqiuhq: Fixed-point fractional library routines. ! (line 1413) * __satfractqiuqq: Fixed-point fractional library routines. ! (line 1411) * __satfractqiusa: Fixed-point fractional library routines. ! (line 1420) * __satfractqiusq: Fixed-point fractional library routines. ! (line 1414) * __satfractqiuta: Fixed-point fractional library routines. ! (line 1423) * __satfractqqda: Fixed-point fractional library routines. ! (line 1050) * __satfractqqdq2: Fixed-point fractional library routines. ! (line 1047) * __satfractqqha: Fixed-point fractional library routines. ! (line 1048) * __satfractqqhq2: Fixed-point fractional library routines. ! (line 1045) * __satfractqqsa: Fixed-point fractional library routines. ! (line 1049) * __satfractqqsq2: Fixed-point fractional library routines. ! (line 1046) * __satfractqqta: Fixed-point fractional library routines. ! (line 1051) * __satfractqquda: Fixed-point fractional library routines. ! (line 1062) * __satfractqqudq: Fixed-point fractional library routines. ! (line 1057) * __satfractqquha: Fixed-point fractional library routines. ! (line 1059) * __satfractqquhq: Fixed-point fractional library routines. ! (line 1054) * __satfractqquqq: Fixed-point fractional library routines. ! (line 1052) * __satfractqqusa: Fixed-point fractional library routines. ! (line 1061) * __satfractqqusq: Fixed-point fractional library routines. ! (line 1055) * __satfractqquta: Fixed-point fractional library routines. ! (line 1064) * __satfractsada2: Fixed-point fractional library routines. ! (line 1147) * __satfractsadq: Fixed-point fractional library routines. ! (line 1145) * __satfractsaha2: Fixed-point fractional library routines. ! (line 1146) * __satfractsahq: Fixed-point fractional library routines. ! (line 1143) * __satfractsaqq: Fixed-point fractional library routines. ! (line 1142) * __satfractsasq: Fixed-point fractional library routines. ! (line 1144) * __satfractsata2: Fixed-point fractional library routines. ! (line 1148) * __satfractsauda: Fixed-point fractional library routines. ! (line 1155) * __satfractsaudq: Fixed-point fractional library routines. ! (line 1152) * __satfractsauha: Fixed-point fractional library routines. ! (line 1153) * __satfractsauhq: Fixed-point fractional library routines. ! (line 1150) * __satfractsauqq: Fixed-point fractional library routines. ! (line 1149) * __satfractsausa: Fixed-point fractional library routines. ! (line 1154) * __satfractsausq: Fixed-point fractional library routines. ! (line 1151) * __satfractsauta: Fixed-point fractional library routines. ! (line 1156) * __satfractsfda: Fixed-point fractional library routines. ! (line 1497) * __satfractsfdq: Fixed-point fractional library routines. ! (line 1494) * __satfractsfha: Fixed-point fractional library routines. ! (line 1495) * __satfractsfhq: Fixed-point fractional library routines. ! (line 1492) * __satfractsfqq: Fixed-point fractional library routines. ! (line 1491) * __satfractsfsa: Fixed-point fractional library routines. ! (line 1496) * __satfractsfsq: Fixed-point fractional library routines. ! (line 1493) * __satfractsfta: Fixed-point fractional library routines. ! (line 1498) * __satfractsfuda: Fixed-point fractional library routines. ! (line 1505) * __satfractsfudq: Fixed-point fractional library routines. ! (line 1502) * __satfractsfuha: Fixed-point fractional library routines. ! (line 1503) * __satfractsfuhq: Fixed-point fractional library routines. ! (line 1500) * __satfractsfuqq: Fixed-point fractional library routines. ! (line 1499) * __satfractsfusa: Fixed-point fractional library routines. ! (line 1504) * __satfractsfusq: Fixed-point fractional library routines. ! (line 1501) * __satfractsfuta: Fixed-point fractional library routines. ! (line 1506) * __satfractsida: Fixed-point fractional library routines. ! (line 1447) * __satfractsidq: Fixed-point fractional library routines. ! (line 1444) * __satfractsiha: Fixed-point fractional library routines. ! (line 1445) * __satfractsihq: Fixed-point fractional library routines. ! (line 1442) * __satfractsiqq: Fixed-point fractional library routines. ! (line 1441) * __satfractsisa: Fixed-point fractional library routines. ! (line 1446) * __satfractsisq: Fixed-point fractional library routines. ! (line 1443) * __satfractsita: Fixed-point fractional library routines. ! (line 1448) * __satfractsiuda: Fixed-point fractional library routines. ! (line 1455) * __satfractsiudq: Fixed-point fractional library routines. ! (line 1452) * __satfractsiuha: Fixed-point fractional library routines. ! (line 1453) * __satfractsiuhq: Fixed-point fractional library routines. ! (line 1450) * __satfractsiuqq: Fixed-point fractional library routines. ! (line 1449) * __satfractsiusa: Fixed-point fractional library routines. ! (line 1454) * __satfractsiusq: Fixed-point fractional library routines. ! (line 1451) * __satfractsiuta: Fixed-point fractional library routines. ! (line 1456) * __satfractsqda: Fixed-point fractional library routines. ! (line 1086) * __satfractsqdq2: Fixed-point fractional library routines. ! (line 1083) * __satfractsqha: Fixed-point fractional library routines. ! (line 1084) * __satfractsqhq2: Fixed-point fractional library routines. ! (line 1082) * __satfractsqqq2: Fixed-point fractional library routines. ! (line 1081) * __satfractsqsa: Fixed-point fractional library routines. ! (line 1085) * __satfractsqta: Fixed-point fractional library routines. ! (line 1087) * __satfractsquda: Fixed-point fractional library routines. ! (line 1097) * __satfractsqudq: Fixed-point fractional library routines. ! (line 1092) * __satfractsquha: Fixed-point fractional library routines. ! (line 1094) * __satfractsquhq: Fixed-point fractional library routines. ! (line 1090) * __satfractsquqq: Fixed-point fractional library routines. ! (line 1088) * __satfractsqusa: Fixed-point fractional library routines. ! (line 1096) * __satfractsqusq: Fixed-point fractional library routines. ! (line 1091) * __satfractsquta: Fixed-point fractional library routines. ! (line 1098) * __satfracttada2: Fixed-point fractional library routines. ! (line 1182) * __satfracttadq: Fixed-point fractional library routines. ! (line 1179) * __satfracttaha2: Fixed-point fractional library routines. ! (line 1180) * __satfracttahq: Fixed-point fractional library routines. ! (line 1177) * __satfracttaqq: Fixed-point fractional library routines. ! (line 1176) * __satfracttasa2: Fixed-point fractional library routines. ! (line 1181) * __satfracttasq: Fixed-point fractional library routines. ! (line 1178) * __satfracttauda: Fixed-point fractional library routines. ! (line 1193) * __satfracttaudq: Fixed-point fractional library routines. ! (line 1188) * __satfracttauha: Fixed-point fractional library routines. ! (line 1190) * __satfracttauhq: Fixed-point fractional library routines. ! (line 1185) * __satfracttauqq: Fixed-point fractional library routines. ! (line 1183) * __satfracttausa: Fixed-point fractional library routines. ! (line 1192) * __satfracttausq: Fixed-point fractional library routines. ! (line 1186) * __satfracttauta: Fixed-point fractional library routines. ! (line 1195) * __satfracttida: Fixed-point fractional library routines. ! (line 1479) * __satfracttidq: Fixed-point fractional library routines. ! (line 1476) * __satfracttiha: Fixed-point fractional library routines. ! (line 1477) * __satfracttihq: Fixed-point fractional library routines. ! (line 1474) * __satfracttiqq: Fixed-point fractional library routines. ! (line 1473) * __satfracttisa: Fixed-point fractional library routines. ! (line 1478) * __satfracttisq: Fixed-point fractional library routines. ! (line 1475) * __satfracttita: Fixed-point fractional library routines. ! (line 1480) * __satfracttiuda: Fixed-point fractional library routines. ! (line 1488) * __satfracttiudq: Fixed-point fractional library routines. ! (line 1484) * __satfracttiuha: Fixed-point fractional library routines. ! (line 1486) * __satfracttiuhq: Fixed-point fractional library routines. ! (line 1482) * __satfracttiuqq: Fixed-point fractional library routines. ! (line 1481) * __satfracttiusa: Fixed-point fractional library routines. ! (line 1487) * __satfracttiusq: Fixed-point fractional library routines. ! (line 1483) * __satfracttiuta: Fixed-point fractional library routines. ! (line 1489) * __satfractudada: Fixed-point fractional library routines. ! (line 1358) * __satfractudadq: Fixed-point fractional library routines. ! (line 1353) * __satfractudaha: Fixed-point fractional library routines. ! (line 1355) * __satfractudahq: Fixed-point fractional library routines. ! (line 1351) * __satfractudaqq: Fixed-point fractional library routines. ! (line 1349) * __satfractudasa: Fixed-point fractional library routines. ! (line 1357) * __satfractudasq: Fixed-point fractional library routines. ! (line 1352) * __satfractudata: Fixed-point fractional library routines. ! (line 1359) * __satfractudaudq: Fixed-point fractional library routines. ! (line 1367) * __satfractudauha2: Fixed-point fractional library routines. - (line 1369) - * __satfractudauhq: Fixed-point fractional library routines. (line 1363) * __satfractudauqq: Fixed-point fractional library routines. ! (line 1361) * __satfractudausa2: Fixed-point fractional library routines. - (line 1371) - * __satfractudausq: Fixed-point fractional library routines. (line 1365) * __satfractudauta2: Fixed-point fractional library routines. ! (line 1373) * __satfractudqda: Fixed-point fractional library routines. ! (line 1282) * __satfractudqdq: Fixed-point fractional library routines. ! (line 1277) * __satfractudqha: Fixed-point fractional library routines. ! (line 1279) * __satfractudqhq: Fixed-point fractional library routines. ! (line 1274) * __satfractudqqq: Fixed-point fractional library routines. ! (line 1272) * __satfractudqsa: Fixed-point fractional library routines. ! (line 1281) * __satfractudqsq: Fixed-point fractional library routines. ! (line 1275) * __satfractudqta: Fixed-point fractional library routines. ! (line 1284) * __satfractudquda: Fixed-point fractional library routines. ! (line 1296) * __satfractudquha: Fixed-point fractional library routines. ! (line 1292) * __satfractudquhq2: Fixed-point fractional library routines. ! (line 1288) * __satfractudquqq2: Fixed-point fractional library routines. ! (line 1286) * __satfractudqusa: Fixed-point fractional library routines. ! (line 1294) * __satfractudqusq2: Fixed-point fractional library routines. ! (line 1290) * __satfractudquta: Fixed-point fractional library routines. ! (line 1298) * __satfractuhada: Fixed-point fractional library routines. ! (line 1310) * __satfractuhadq: Fixed-point fractional library routines. ! (line 1305) * __satfractuhaha: Fixed-point fractional library routines. ! (line 1307) * __satfractuhahq: Fixed-point fractional library routines. ! (line 1302) * __satfractuhaqq: Fixed-point fractional library routines. ! (line 1300) * __satfractuhasa: Fixed-point fractional library routines. ! (line 1309) * __satfractuhasq: Fixed-point fractional library routines. ! (line 1303) * __satfractuhata: Fixed-point fractional library routines. ! (line 1312) * __satfractuhauda2: Fixed-point fractional library routines. ! (line 1324) * __satfractuhaudq: Fixed-point fractional library routines. ! (line 1320) * __satfractuhauhq: Fixed-point fractional library routines. ! (line 1316) * __satfractuhauqq: Fixed-point fractional library routines. ! (line 1314) * __satfractuhausa2: Fixed-point fractional library routines. ! (line 1322) * __satfractuhausq: Fixed-point fractional library routines. ! (line 1318) * __satfractuhauta2: Fixed-point fractional library routines. ! (line 1326) * __satfractuhqda: Fixed-point fractional library routines. ! (line 1231) * __satfractuhqdq: Fixed-point fractional library routines. ! (line 1228) * __satfractuhqha: Fixed-point fractional library routines. ! (line 1229) * __satfractuhqhq: Fixed-point fractional library routines. ! (line 1226) * __satfractuhqqq: Fixed-point fractional library routines. ! (line 1225) * __satfractuhqsa: Fixed-point fractional library routines. ! (line 1230) * __satfractuhqsq: Fixed-point fractional library routines. ! (line 1227) * __satfractuhqta: Fixed-point fractional library routines. ! (line 1232) * __satfractuhquda: Fixed-point fractional library routines. ! (line 1242) * __satfractuhqudq2: Fixed-point fractional library routines. ! (line 1237) * __satfractuhquha: Fixed-point fractional library routines. - (line 1239) - * __satfractuhquqq2: Fixed-point fractional library routines. (line 1233) * __satfractuhqusa: Fixed-point fractional library routines. ! (line 1241) * __satfractuhqusq2: Fixed-point fractional library routines. ! (line 1235) * __satfractuhquta: Fixed-point fractional library routines. ! (line 1244) * __satfractunsdida: Fixed-point fractional library routines. ! (line 1841) * __satfractunsdidq: Fixed-point fractional library routines. ! (line 1837) * __satfractunsdiha: Fixed-point fractional library routines. ! (line 1839) * __satfractunsdihq: Fixed-point fractional library routines. ! (line 1835) * __satfractunsdiqq: Fixed-point fractional library routines. ! (line 1834) * __satfractunsdisa: Fixed-point fractional library routines. ! (line 1840) * __satfractunsdisq: Fixed-point fractional library routines. ! (line 1836) * __satfractunsdita: Fixed-point fractional library routines. ! (line 1842) * __satfractunsdiuda: Fixed-point fractional library routines. - (line 1856) - * __satfractunsdiudq: Fixed-point fractional library routines. (line 1850) * __satfractunsdiuha: Fixed-point fractional library routines. - (line 1852) - * __satfractunsdiuhq: Fixed-point fractional library routines. (line 1846) * __satfractunsdiuqq: Fixed-point fractional library routines. ! (line 1844) * __satfractunsdiusa: Fixed-point fractional library routines. - (line 1854) - * __satfractunsdiusq: Fixed-point fractional library routines. (line 1848) * __satfractunsdiuta: Fixed-point fractional library routines. ! (line 1858) * __satfractunshida: Fixed-point fractional library routines. ! (line 1793) * __satfractunshidq: Fixed-point fractional library routines. ! (line 1789) * __satfractunshiha: Fixed-point fractional library routines. ! (line 1791) * __satfractunshihq: Fixed-point fractional library routines. ! (line 1787) * __satfractunshiqq: Fixed-point fractional library routines. ! (line 1786) * __satfractunshisa: Fixed-point fractional library routines. ! (line 1792) * __satfractunshisq: Fixed-point fractional library routines. ! (line 1788) * __satfractunshita: Fixed-point fractional library routines. ! (line 1794) * __satfractunshiuda: Fixed-point fractional library routines. - (line 1808) - * __satfractunshiudq: Fixed-point fractional library routines. (line 1802) * __satfractunshiuha: Fixed-point fractional library routines. - (line 1804) - * __satfractunshiuhq: Fixed-point fractional library routines. (line 1798) * __satfractunshiuqq: Fixed-point fractional library routines. ! (line 1796) * __satfractunshiusa: Fixed-point fractional library routines. - (line 1806) - * __satfractunshiusq: Fixed-point fractional library routines. (line 1800) * __satfractunshiuta: Fixed-point fractional library routines. ! (line 1810) * __satfractunsqida: Fixed-point fractional library routines. ! (line 1767) * __satfractunsqidq: Fixed-point fractional library routines. ! (line 1763) * __satfractunsqiha: Fixed-point fractional library routines. ! (line 1765) * __satfractunsqihq: Fixed-point fractional library routines. ! (line 1761) * __satfractunsqiqq: Fixed-point fractional library routines. ! (line 1760) * __satfractunsqisa: Fixed-point fractional library routines. ! (line 1766) * __satfractunsqisq: Fixed-point fractional library routines. ! (line 1762) * __satfractunsqita: Fixed-point fractional library routines. ! (line 1768) * __satfractunsqiuda: Fixed-point fractional library routines. - (line 1782) - * __satfractunsqiudq: Fixed-point fractional library routines. (line 1776) * __satfractunsqiuha: Fixed-point fractional library routines. - (line 1778) - * __satfractunsqiuhq: Fixed-point fractional library routines. (line 1772) * __satfractunsqiuqq: Fixed-point fractional library routines. ! (line 1770) * __satfractunsqiusa: Fixed-point fractional library routines. - (line 1780) - * __satfractunsqiusq: Fixed-point fractional library routines. (line 1774) * __satfractunsqiuta: Fixed-point fractional library routines. ! (line 1784) * __satfractunssida: Fixed-point fractional library routines. ! (line 1818) * __satfractunssidq: Fixed-point fractional library routines. ! (line 1815) * __satfractunssiha: Fixed-point fractional library routines. ! (line 1816) * __satfractunssihq: Fixed-point fractional library routines. ! (line 1813) * __satfractunssiqq: Fixed-point fractional library routines. ! (line 1812) * __satfractunssisa: Fixed-point fractional library routines. ! (line 1817) * __satfractunssisq: Fixed-point fractional library routines. ! (line 1814) * __satfractunssita: Fixed-point fractional library routines. ! (line 1819) * __satfractunssiuda: Fixed-point fractional library routines. ! (line 1830) * __satfractunssiudq: Fixed-point fractional library routines. ! (line 1825) * __satfractunssiuha: Fixed-point fractional library routines. ! (line 1827) * __satfractunssiuhq: Fixed-point fractional library routines. ! (line 1822) * __satfractunssiuqq: Fixed-point fractional library routines. ! (line 1820) * __satfractunssiusa: Fixed-point fractional library routines. ! (line 1829) * __satfractunssiusq: Fixed-point fractional library routines. ! (line 1823) * __satfractunssiuta: Fixed-point fractional library routines. ! (line 1832) * __satfractunstida: Fixed-point fractional library routines. ! (line 1870) * __satfractunstidq: Fixed-point fractional library routines. ! (line 1865) * __satfractunstiha: Fixed-point fractional library routines. ! (line 1867) * __satfractunstihq: Fixed-point fractional library routines. ! (line 1862) * __satfractunstiqq: Fixed-point fractional library routines. ! (line 1860) * __satfractunstisa: Fixed-point fractional library routines. ! (line 1869) * __satfractunstisq: Fixed-point fractional library routines. ! (line 1863) * __satfractunstita: Fixed-point fractional library routines. ! (line 1872) * __satfractunstiuda: Fixed-point fractional library routines. - (line 1886) - * __satfractunstiudq: Fixed-point fractional library routines. (line 1880) * __satfractunstiuha: Fixed-point fractional library routines. - (line 1882) - * __satfractunstiuhq: Fixed-point fractional library routines. (line 1876) * __satfractunstiuqq: Fixed-point fractional library routines. ! (line 1874) * __satfractunstiusa: Fixed-point fractional library routines. - (line 1884) - * __satfractunstiusq: Fixed-point fractional library routines. (line 1878) * __satfractunstiuta: Fixed-point fractional library routines. ! (line 1888) * __satfractuqqda: Fixed-point fractional library routines. ! (line 1207) * __satfractuqqdq: Fixed-point fractional library routines. ! (line 1202) * __satfractuqqha: Fixed-point fractional library routines. ! (line 1204) * __satfractuqqhq: Fixed-point fractional library routines. ! (line 1199) * __satfractuqqqq: Fixed-point fractional library routines. ! (line 1197) * __satfractuqqsa: Fixed-point fractional library routines. ! (line 1206) * __satfractuqqsq: Fixed-point fractional library routines. ! (line 1200) * __satfractuqqta: Fixed-point fractional library routines. ! (line 1209) * __satfractuqquda: Fixed-point fractional library routines. - (line 1221) - * __satfractuqqudq2: Fixed-point fractional library routines. (line 1215) * __satfractuqquha: Fixed-point fractional library routines. - (line 1217) - * __satfractuqquhq2: Fixed-point fractional library routines. (line 1211) * __satfractuqqusa: Fixed-point fractional library routines. - (line 1219) - * __satfractuqqusq2: Fixed-point fractional library routines. (line 1213) * __satfractuqquta: Fixed-point fractional library routines. ! (line 1223) * __satfractusada: Fixed-point fractional library routines. ! (line 1334) * __satfractusadq: Fixed-point fractional library routines. ! (line 1331) * __satfractusaha: Fixed-point fractional library routines. ! (line 1332) * __satfractusahq: Fixed-point fractional library routines. ! (line 1329) * __satfractusaqq: Fixed-point fractional library routines. ! (line 1328) * __satfractusasa: Fixed-point fractional library routines. ! (line 1333) * __satfractusasq: Fixed-point fractional library routines. ! (line 1330) * __satfractusata: Fixed-point fractional library routines. ! (line 1335) * __satfractusauda2: Fixed-point fractional library routines. ! (line 1345) * __satfractusaudq: Fixed-point fractional library routines. ! (line 1341) * __satfractusauha2: Fixed-point fractional library routines. ! (line 1343) * __satfractusauhq: Fixed-point fractional library routines. ! (line 1338) * __satfractusauqq: Fixed-point fractional library routines. ! (line 1336) * __satfractusausq: Fixed-point fractional library routines. ! (line 1339) * __satfractusauta2: Fixed-point fractional library routines. ! (line 1347) * __satfractusqda: Fixed-point fractional library routines. ! (line 1255) * __satfractusqdq: Fixed-point fractional library routines. ! (line 1250) * __satfractusqha: Fixed-point fractional library routines. ! (line 1252) * __satfractusqhq: Fixed-point fractional library routines. ! (line 1248) * __satfractusqqq: Fixed-point fractional library routines. ! (line 1246) * __satfractusqsa: Fixed-point fractional library routines. ! (line 1254) * __satfractusqsq: Fixed-point fractional library routines. ! (line 1249) * __satfractusqta: Fixed-point fractional library routines. ! (line 1256) * __satfractusquda: Fixed-point fractional library routines. - (line 1268) - * __satfractusqudq2: Fixed-point fractional library routines. (line 1262) * __satfractusquha: Fixed-point fractional library routines. ! (line 1264) * __satfractusquhq2: Fixed-point fractional library routines. ! (line 1260) * __satfractusquqq2: Fixed-point fractional library routines. ! (line 1258) * __satfractusqusa: Fixed-point fractional library routines. ! (line 1266) * __satfractusquta: Fixed-point fractional library routines. ! (line 1270) * __satfractutada: Fixed-point fractional library routines. ! (line 1385) * __satfractutadq: Fixed-point fractional library routines. ! (line 1380) * __satfractutaha: Fixed-point fractional library routines. ! (line 1382) * __satfractutahq: Fixed-point fractional library routines. ! (line 1377) * __satfractutaqq: Fixed-point fractional library routines. ! (line 1375) * __satfractutasa: Fixed-point fractional library routines. ! (line 1384) * __satfractutasq: Fixed-point fractional library routines. ! (line 1378) * __satfractutata: Fixed-point fractional library routines. ! (line 1387) * __satfractutauda2: Fixed-point fractional library routines. - (line 1401) - * __satfractutaudq: Fixed-point fractional library routines. (line 1395) * __satfractutauha2: Fixed-point fractional library routines. - (line 1397) - * __satfractutauhq: Fixed-point fractional library routines. (line 1391) * __satfractutauqq: Fixed-point fractional library routines. ! (line 1389) * __satfractutausa2: Fixed-point fractional library routines. - (line 1399) - * __satfractutausq: Fixed-point fractional library routines. (line 1393) * __splitstack_find: Miscellaneous routines. ! (line 15) * __ssaddda3: Fixed-point fractional library routines. ! (line 74) * __ssadddq3: Fixed-point fractional library routines. ! (line 69) * __ssaddha3: Fixed-point fractional library routines. ! (line 71) * __ssaddhq3: Fixed-point fractional library routines. ! (line 67) * __ssaddqq3: Fixed-point fractional library routines. ! (line 65) * __ssaddsa3: Fixed-point fractional library routines. ! (line 73) * __ssaddsq3: Fixed-point fractional library routines. ! (line 68) * __ssaddta3: Fixed-point fractional library routines. ! (line 75) * __ssashlda3: Fixed-point fractional library routines. ! (line 409) * __ssashldq3: Fixed-point fractional library routines. ! (line 405) * __ssashlha3: Fixed-point fractional library routines. ! (line 407) * __ssashlhq3: Fixed-point fractional library routines. ! (line 403) * __ssashlsa3: Fixed-point fractional library routines. ! (line 408) * __ssashlsq3: Fixed-point fractional library routines. ! (line 404) * __ssashlta3: Fixed-point fractional library routines. ! (line 410) * __ssdivda3: Fixed-point fractional library routines. ! (line 268) * __ssdivdq3: Fixed-point fractional library routines. ! (line 263) * __ssdivha3: Fixed-point fractional library routines. ! (line 265) * __ssdivhq3: Fixed-point fractional library routines. ! (line 261) * __ssdivqq3: Fixed-point fractional library routines. ! (line 259) * __ssdivsa3: Fixed-point fractional library routines. ! (line 267) * __ssdivsq3: Fixed-point fractional library routines. ! (line 262) * __ssdivta3: Fixed-point fractional library routines. ! (line 269) * __ssmulda3: Fixed-point fractional library routines. ! (line 200) * __ssmuldq3: Fixed-point fractional library routines. ! (line 195) * __ssmulha3: Fixed-point fractional library routines. ! (line 197) * __ssmulhq3: Fixed-point fractional library routines. ! (line 193) * __ssmulqq3: Fixed-point fractional library routines. ! (line 191) * __ssmulsa3: Fixed-point fractional library routines. ! (line 199) * __ssmulsq3: Fixed-point fractional library routines. ! (line 194) * __ssmulta3: Fixed-point fractional library routines. ! (line 201) * __ssnegda2: Fixed-point fractional library routines. ! (line 323) * __ssnegdq2: Fixed-point fractional library routines. ! (line 320) * __ssnegha2: Fixed-point fractional library routines. ! (line 321) * __ssneghq2: Fixed-point fractional library routines. ! (line 318) * __ssnegqq2: Fixed-point fractional library routines. ! (line 317) * __ssnegsa2: Fixed-point fractional library routines. ! (line 322) * __ssnegsq2: Fixed-point fractional library routines. ! (line 319) * __ssnegta2: Fixed-point fractional library routines. ! (line 324) * __sssubda3: Fixed-point fractional library routines. ! (line 136) * __sssubdq3: Fixed-point fractional library routines. ! (line 131) * __sssubha3: Fixed-point fractional library routines. ! (line 133) * __sssubhq3: Fixed-point fractional library routines. ! (line 129) * __sssubqq3: Fixed-point fractional library routines. ! (line 127) * __sssubsa3: Fixed-point fractional library routines. ! (line 135) * __sssubsq3: Fixed-point fractional library routines. ! (line 130) * __sssubta3: Fixed-point fractional library routines. ! (line 137) * __subda3: Fixed-point fractional library routines. ! (line 114) * __subdf3: Soft float library routines. ! (line 30) * __subdq3: Fixed-point fractional library routines. ! (line 101) * __subha3: Fixed-point fractional library routines. ! (line 111) * __subhq3: Fixed-point fractional library routines. ! (line 99) * __subqq3: Fixed-point fractional library routines. ! (line 97) * __subsa3: Fixed-point fractional library routines. ! (line 113) * __subsf3: Soft float library routines. ! (line 29) * __subsq3: Fixed-point fractional library routines. ! (line 100) * __subta3: Fixed-point fractional library routines. ! (line 115) * __subtf3: Soft float library routines. ! (line 31) * __subuda3: Fixed-point fractional library routines. ! (line 121) * __subudq3: Fixed-point fractional library routines. ! (line 109) * __subuha3: Fixed-point fractional library routines. ! (line 117) * __subuhq3: Fixed-point fractional library routines. ! (line 105) * __subuqq3: Fixed-point fractional library routines. ! (line 103) * __subusa3: Fixed-point fractional library routines. ! (line 119) * __subusq3: Fixed-point fractional library routines. ! (line 107) * __subuta3: Fixed-point fractional library routines. ! (line 123) * __subvdi3: Integer library routines. ! (line 122) * __subvsi3: Integer library routines. ! (line 121) * __subxf3: Soft float library routines. ! (line 33) * __truncdfsf2: Soft float library routines. ! (line 75) * __trunctfdf2: Soft float library routines. ! (line 72) * __trunctfsf2: Soft float library routines. ! (line 74) * __truncxfdf2: Soft float library routines. ! (line 71) * __truncxfsf2: Soft float library routines. ! (line 73) * __ucmpdi2: Integer library routines. - (line 92) - * __ucmpti2: Integer library routines. (line 93) * __udivdi3: Integer library routines. ! (line 52) * __udivmoddi4: Integer library routines. - (line 59) - * __udivmodti4: Integer library routines. (line 61) * __udivsi3: Integer library routines. ! (line 50) * __udivti3: Integer library routines. ! (line 54) * __udivuda3: Fixed-point fractional library routines. - (line 252) - * __udivudq3: Fixed-point fractional library routines. (line 246) * __udivuha3: Fixed-point fractional library routines. - (line 248) - * __udivuhq3: Fixed-point fractional library routines. (line 242) * __udivuqq3: Fixed-point fractional library routines. ! (line 240) * __udivusa3: Fixed-point fractional library routines. - (line 250) - * __udivusq3: Fixed-point fractional library routines. (line 244) * __udivuta3: Fixed-point fractional library routines. ! (line 254) * __umoddi3: Integer library routines. ! (line 69) * __umodsi3: Integer library routines. ! (line 67) * __umodti3: Integer library routines. ! (line 71) * __unorddf2: Soft float library routines. ! (line 172) * __unordsf2: Soft float library routines. ! (line 171) * __unordtf2: Soft float library routines. ! (line 173) * __usadduda3: Fixed-point fractional library routines. - (line 91) - * __usaddudq3: Fixed-point fractional library routines. (line 85) * __usadduha3: Fixed-point fractional library routines. - (line 87) - * __usadduhq3: Fixed-point fractional library routines. (line 81) * __usadduqq3: Fixed-point fractional library routines. ! (line 79) * __usaddusa3: Fixed-point fractional library routines. - (line 89) - * __usaddusq3: Fixed-point fractional library routines. (line 83) * __usadduta3: Fixed-point fractional library routines. ! (line 93) * __usashluda3: Fixed-point fractional library routines. - (line 427) - * __usashludq3: Fixed-point fractional library routines. (line 421) * __usashluha3: Fixed-point fractional library routines. - (line 423) - * __usashluhq3: Fixed-point fractional library routines. (line 417) * __usashluqq3: Fixed-point fractional library routines. ! (line 415) * __usashlusa3: Fixed-point fractional library routines. - (line 425) - * __usashlusq3: Fixed-point fractional library routines. (line 419) * __usashluta3: Fixed-point fractional library routines. ! (line 429) * __usdivuda3: Fixed-point fractional library routines. - (line 286) - * __usdivudq3: Fixed-point fractional library routines. (line 280) * __usdivuha3: Fixed-point fractional library routines. - (line 282) - * __usdivuhq3: Fixed-point fractional library routines. (line 276) * __usdivuqq3: Fixed-point fractional library routines. ! (line 274) * __usdivusa3: Fixed-point fractional library routines. - (line 284) - * __usdivusq3: Fixed-point fractional library routines. (line 278) * __usdivuta3: Fixed-point fractional library routines. ! (line 288) * __usmuluda3: Fixed-point fractional library routines. - (line 218) - * __usmuludq3: Fixed-point fractional library routines. (line 212) * __usmuluha3: Fixed-point fractional library routines. - (line 214) - * __usmuluhq3: Fixed-point fractional library routines. (line 208) * __usmuluqq3: Fixed-point fractional library routines. ! (line 206) * __usmulusa3: Fixed-point fractional library routines. - (line 216) - * __usmulusq3: Fixed-point fractional library routines. (line 210) * __usmuluta3: Fixed-point fractional library routines. ! (line 220) * __usneguda2: Fixed-point fractional library routines. ! (line 337) * __usnegudq2: Fixed-point fractional library routines. ! (line 332) * __usneguha2: Fixed-point fractional library routines. ! (line 334) * __usneguhq2: Fixed-point fractional library routines. ! (line 329) * __usneguqq2: Fixed-point fractional library routines. ! (line 327) * __usnegusa2: Fixed-point fractional library routines. ! (line 336) * __usnegusq2: Fixed-point fractional library routines. ! (line 330) * __usneguta2: Fixed-point fractional library routines. ! (line 339) * __ussubuda3: Fixed-point fractional library routines. - (line 154) - * __ussubudq3: Fixed-point fractional library routines. (line 148) * __ussubuha3: Fixed-point fractional library routines. - (line 150) - * __ussubuhq3: Fixed-point fractional library routines. (line 144) * __ussubuqq3: Fixed-point fractional library routines. ! (line 142) * __ussubusa3: Fixed-point fractional library routines. - (line 152) - * __ussubusq3: Fixed-point fractional library routines. (line 146) * __ussubuta3: Fixed-point fractional library routines. ! (line 156) ! * abort: Portability. (line 20) ! * abs: Arithmetic. (line 200) ! * abs and attributes: Expressions. (line 83) ! * absence_set: Processor pipeline description. ! (line 223) ! * absM2 instruction pattern: Standard Names. (line 610) ! * absolute value: Arithmetic. (line 200) * ABS_EXPR: Unary and Binary Expressions. (line 6) * access to operands: Accessors. (line 6) * access to special operands: Special Accessors. (line 6) * accessors: Accessors. (line 6) ! * ACCUMULATE_OUTGOING_ARGS: Stack Arguments. (line 48) ! * ACCUMULATE_OUTGOING_ARGS and stack frames: Function Entry. (line 133) ! * ACCUM_TYPE_SIZE: Type Layout. (line 87) ! * acosM2 instruction pattern: Standard Names. (line 697) ! * ADA_LONG_TYPE_SIZE: Type Layout. (line 25) * Adding a new GIMPLE statement code: Adding a new GIMPLE statement code. (line 6) ! * ADDITIONAL_REGISTER_NAMES: Instruction Output. (line 14) ! * addM3 instruction pattern: Standard Names. (line 295) ! * addMODEcc instruction pattern: Standard Names. (line 1266) ! * addptrM3 instruction pattern: Standard Names. (line 328) ! * address constraints: Simple Constraints. (line 162) ! * addressing modes: Addressing Modes. (line 6) ! * address_operand: Machine-Independent Predicates. ! (line 62) ! * address_operand <1>: Simple Constraints. (line 166) ! * addr_diff_vec: Side Effects. (line 314) * addr_diff_vec, length of: Insn Lengths. (line 26) * ADDR_EXPR: Storage References. (line 6) ! * addr_vec: Side Effects. (line 309) * addr_vec, length of: Insn Lengths. (line 26) ! * addvM4 instruction pattern: Standard Names. (line 311) ! * ADJUST_FIELD_ALIGN: Storage Layout. (line 195) * ADJUST_INSN_LENGTH: Insn Lengths. (line 41) ! * ADJUST_REG_ALLOC_ORDER: Allocation Order. (line 22) * aggregates as return values: Aggregate Return. (line 6) * alias: Alias analysis. (line 6) - * allocate_stack instruction pattern: Standard Names. (line 1594) * ALL_REGS: Register Classes. (line 17) * alternate entry points: Insns. (line 146) * anchored addresses: Anchored Addresses. (line 6) ! * and: Arithmetic. (line 158) * and and attributes: Expressions. (line 50) * and, canonicalization of: Insn Canonicalizations. ! (line 51) ! * andM3 instruction pattern: Standard Names. (line 301) * ANNOTATE_EXPR: Unary and Binary Expressions. (line 6) * annotations: Annotations. (line 6) * APPLY_RESULT_SIZE: Scalar Return. (line 112) ! * ARGS_GROW_DOWNWARD: Frame Layout. (line 30) * argument passing: Interface. (line 36) * arguments in registers: Register Arguments. (line 6) * arguments on stack: Stack Arguments. (line 6) - * ARG_POINTER_CFA_OFFSET: Frame Layout. (line 190) - * ARG_POINTER_REGNUM: Frame Registers. (line 40) - * ARG_POINTER_REGNUM and virtual registers: Regs and Memory. (line 65) - * arg_pointer_rtx: Frame Registers. (line 104) * arithmetic library: Soft float library routines. (line 6) ! * arithmetic shift: Arithmetic. (line 173) ! * arithmetic shift with signed saturation: Arithmetic. (line 173) ! * arithmetic shift with unsigned saturation: Arithmetic. (line 173) * arithmetic, in RTL: Arithmetic. (line 6) ! * ARITHMETIC_TYPE_P: Types for C++. (line 59) * array: Types. (line 6) * ARRAY_RANGE_REF: Storage References. (line 6) * ARRAY_REF: Storage References. (line 6) * ARRAY_TYPE: Types. (line 6) ! * ashift: Arithmetic. (line 173) ! * ashift and attributes: Expressions. (line 83) ! * ashiftrt: Arithmetic. (line 190) ! * ashiftrt and attributes: Expressions. (line 83) ! * ashlM3 instruction pattern: Standard Names. (line 579) ! * ashrM3 instruction pattern: Standard Names. (line 591) ! * asinM2 instruction pattern: Standard Names. (line 691) ! * ASM_APP_OFF: File Framework. (line 76) ! * ASM_APP_ON: File Framework. (line 69) ! * ASM_COMMENT_START: File Framework. (line 64) ! * ASM_DECLARE_COLD_FUNCTION_NAME: Label Output. (line 136) ! * ASM_DECLARE_COLD_FUNCTION_SIZE: Label Output. (line 151) ! * ASM_DECLARE_FUNCTION_NAME: Label Output. (line 108) ! * ASM_DECLARE_FUNCTION_SIZE: Label Output. (line 123) ! * ASM_DECLARE_OBJECT_NAME: Label Output. (line 164) ! * ASM_DECLARE_REGISTER_GLOBAL: Label Output. (line 192) ! * ASM_FINAL_SPEC: Driver. (line 81) ! * ASM_FINISH_DECLARE_OBJECT: Label Output. (line 200) ! * ASM_FORMAT_PRIVATE_NAME: Label Output. (line 426) ! * asm_fprintf: Instruction Output. (line 150) ! * ASM_FPRINTF_EXTENSIONS: Instruction Output. (line 160) ! * ASM_GENERATE_INTERNAL_LABEL: Label Output. (line 410) ! * asm_input: Side Effects. (line 296) * asm_input and /v: Flags. (line 76) ! * ASM_MAYBE_OUTPUT_ENCODED_ADDR_RTX: Exception Handling. (line 80) ! * asm_noperands: Insns. (line 304) ! * ASM_NO_SKIP_IN_TEXT: Alignment Output. (line 78) * asm_operands and /v: Flags. (line 76) * asm_operands, RTL sharing: Sharing. (line 45) * asm_operands, usage: Assembler. (line 6) ! * ASM_OUTPUT_ADDR_DIFF_ELT: Dispatch Tables. (line 8) ! * ASM_OUTPUT_ADDR_VEC_ELT: Dispatch Tables. (line 25) ! * ASM_OUTPUT_ALIGN: Alignment Output. (line 85) ! * ASM_OUTPUT_ALIGNED_BSS: Uninitialized Data. (line 45) ! * ASM_OUTPUT_ALIGNED_COMMON: Uninitialized Data. (line 29) ! * ASM_OUTPUT_ALIGNED_DECL_COMMON: Uninitialized Data. (line 36) ! * ASM_OUTPUT_ALIGNED_DECL_LOCAL: Uninitialized Data. (line 89) ! * ASM_OUTPUT_ALIGNED_LOCAL: Uninitialized Data. (line 82) ! * ASM_OUTPUT_ALIGN_WITH_NOP: Alignment Output. (line 90) ! * ASM_OUTPUT_ASCII: Data Output. (line 54) ! * ASM_OUTPUT_CASE_END: Dispatch Tables. (line 50) ! * ASM_OUTPUT_CASE_LABEL: Dispatch Tables. (line 37) ! * ASM_OUTPUT_COMMON: Uninitialized Data. (line 9) ! * ASM_OUTPUT_DEBUG_LABEL: Label Output. (line 398) ! * ASM_OUTPUT_DEF: Label Output. (line 447) ! * ASM_OUTPUT_DEF_FROM_DECLS: Label Output. (line 454) ! * ASM_OUTPUT_DWARF_DATAREL: SDB and DWARF. (line 97) ! * ASM_OUTPUT_DWARF_DELTA: SDB and DWARF. (line 77) ! * ASM_OUTPUT_DWARF_OFFSET: SDB and DWARF. (line 86) ! * ASM_OUTPUT_DWARF_PCREL: SDB and DWARF. (line 92) ! * ASM_OUTPUT_DWARF_TABLE_REF: SDB and DWARF. (line 102) ! * ASM_OUTPUT_DWARF_VMS_DELTA: SDB and DWARF. (line 81) ! * ASM_OUTPUT_EXTERNAL: Label Output. (line 327) ! * ASM_OUTPUT_FDESC: Data Output. (line 63) ! * ASM_OUTPUT_FUNCTION_LABEL: Label Output. (line 16) ! * ASM_OUTPUT_INTERNAL_LABEL: Label Output. (line 27) ! * ASM_OUTPUT_LABEL: Label Output. (line 8) ! * ASM_OUTPUT_LABELREF: Label Output. (line 349) ! * ASM_OUTPUT_LABEL_REF: Label Output. (line 371) ! * ASM_OUTPUT_LOCAL: Uninitialized Data. (line 69) ! * ASM_OUTPUT_MAX_SKIP_ALIGN: Alignment Output. (line 94) ! * ASM_OUTPUT_MEASURED_SIZE: Label Output. (line 51) ! * ASM_OUTPUT_OPCODE: Instruction Output. (line 35) ! * ASM_OUTPUT_POOL_EPILOGUE: Data Output. (line 112) ! * ASM_OUTPUT_POOL_PROLOGUE: Data Output. (line 76) ! * ASM_OUTPUT_REG_POP: Instruction Output. (line 206) ! * ASM_OUTPUT_REG_PUSH: Instruction Output. (line 201) ! * ASM_OUTPUT_SIZE_DIRECTIVE: Label Output. (line 45) ! * ASM_OUTPUT_SKIP: Alignment Output. (line 72) ! * ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 83) ! * ASM_OUTPUT_SPECIAL_POOL_ENTRY: Data Output. (line 87) ! * ASM_OUTPUT_SYMBOL_REF: Label Output. (line 364) ! * ASM_OUTPUT_TYPE_DIRECTIVE: Label Output. (line 98) ! * ASM_OUTPUT_WEAKREF: Label Output. (line 259) ! * ASM_OUTPUT_WEAK_ALIAS: Label Output. (line 473) ! * ASM_PREFERRED_EH_DATA_FORMAT: Exception Handling. (line 66) ! * ASM_SPEC: Driver. (line 73) ! * ASM_STABD_OP: DBX Options. (line 34) ! * ASM_STABN_OP: DBX Options. (line 41) ! * ASM_STABS_OP: DBX Options. (line 28) ! * ASM_WEAKEN_DECL: Label Output. (line 251) ! * ASM_WEAKEN_LABEL: Label Output. (line 238) * assembler format: File Framework. (line 6) * assembler instructions in RTL: Assembler. (line 6) ! * ASSEMBLER_DIALECT: Instruction Output. (line 172) ! * assemble_name: Label Output. (line 8) ! * assemble_name_raw: Label Output. (line 27) * assigning attribute values to insns: Tagging Insns. (line 6) ! * ASSUME_EXTENDED_UNWIND_CONTEXT: Frame Registers. (line 165) * asterisk in template: Output Statement. (line 29) ! * AS_NEEDS_DASH_FOR_PIPED_INPUT: Driver. (line 88) ! * atan2M3 instruction pattern: Standard Names. (line 792) ! * atanM2 instruction pattern: Standard Names. (line 703) ! * atomic: GTY Options. (line 195) ! * atomic_addMODE instruction pattern: Standard Names. (line 1996) ! * atomic_add_fetchMODE instruction pattern: Standard Names. (line 2025) ! * atomic_andMODE instruction pattern: Standard Names. (line 1996) ! * atomic_and_fetchMODE instruction pattern: Standard Names. (line 2025) * atomic_compare_and_swapMODE instruction pattern: Standard Names. ! (line 1932) ! * atomic_exchangeMODE instruction pattern: Standard Names. (line 1984) ! * atomic_fetch_addMODE instruction pattern: Standard Names. (line 2010) ! * atomic_fetch_andMODE instruction pattern: Standard Names. (line 2010) ! * atomic_fetch_nandMODE instruction pattern: Standard Names. (line 2010) ! * atomic_fetch_orMODE instruction pattern: Standard Names. (line 2010) ! * atomic_fetch_subMODE instruction pattern: Standard Names. (line 2010) ! * atomic_fetch_xorMODE instruction pattern: Standard Names. (line 2010) ! * atomic_loadMODE instruction pattern: Standard Names. (line 1963) ! * atomic_nandMODE instruction pattern: Standard Names. (line 1996) ! * atomic_nand_fetchMODE instruction pattern: Standard Names. (line 2025) ! * atomic_orMODE instruction pattern: Standard Names. (line 1996) ! * atomic_or_fetchMODE instruction pattern: Standard Names. (line 2025) ! * atomic_storeMODE instruction pattern: Standard Names. (line 1973) ! * atomic_subMODE instruction pattern: Standard Names. (line 1996) ! * atomic_sub_fetchMODE instruction pattern: Standard Names. (line 2025) ! * atomic_test_and_set instruction pattern: Standard Names. (line 2042) ! * atomic_xorMODE instruction pattern: Standard Names. (line 1996) ! * atomic_xor_fetchMODE instruction pattern: Standard Names. (line 2025) ! * attr: Expressions. (line 163) * attr <1>: Tagging Insns. (line 54) * attribute expressions: Expressions. (line 6) * attribute specifications: Attr Example. (line 6) * attribute specifications example: Attr Example. (line 6) * attributes: Attributes. (line 6) * attributes, defining: Defining Attributes. (line 6) * attributes, target-specific: Target Attributes. (line 6) ! * ATTRIBUTE_ALIGNED_VALUE: Storage Layout. (line 177) ! * attr_flag: Expressions. (line 138) ! * autoincrement addressing, availability: Portability. (line 20) * autoincrement/decrement addressing: Simple Constraints. (line 30) * automata_option: Processor pipeline description. ! (line 304) * automaton based pipeline description: Processor pipeline description. (line 6) - * automaton based pipeline description <1>: Processor pipeline description. - (line 49) * automaton based scheduler: Processor pipeline description. (line 6) * AVOID_CCMODE_COPIES: Values in Registers. ! (line 150) * backslash: Output Template. (line 46) ! * barrier: Insns. (line 176) * barrier and /f: Flags. (line 107) * barrier and /v: Flags. (line 44) ! * BASE_REG_CLASS: Register Classes. (line 111) * basic block: Basic Blocks. (line 6) * Basic Statements: Basic Statements. (line 6) * basic-block.h: Control Flow. (line 6) - * basic_block: Basic Blocks. (line 6) * BASIC_BLOCK: Basic Blocks. (line 14) * BB_HEAD, BB_END: Maintaining the CFG. ! (line 76) ! * bb_seq: GIMPLE sequences. (line 72) ! * BIGGEST_ALIGNMENT: Storage Layout. (line 162) ! * BIGGEST_FIELD_ALIGNMENT: Storage Layout. (line 188) * BImode: Machine Modes. (line 22) * BIND_EXPR: Unary and Binary Expressions. (line 6) * BINFO_TYPE: Classes. (line 6) * bit-fields: Bit-Fields. (line 6) - * BITFIELD_NBYTES_LIMITED: Storage Layout. (line 398) - * BITS_BIG_ENDIAN: Storage Layout. (line 11) - * BITS_BIG_ENDIAN, effect on sign_extract: Bit-Fields. (line 8) - * BITS_PER_UNIT: Machine Modes. (line 354) - * BITS_PER_WORD: Storage Layout. (line 50) - * bitwise complement: Arithmetic. (line 154) - * bitwise exclusive-or: Arithmetic. (line 168) - * bitwise inclusive-or: Arithmetic. (line 163) - * bitwise logical-and: Arithmetic. (line 158) * BIT_AND_EXPR: Unary and Binary Expressions. (line 6) * BIT_IOR_EXPR: Unary and Binary Expressions. --- 44470,47999 ---- * /s in RTL dump: Flags. (line 245) * /u in RTL dump: Flags. (line 296) * /v in RTL dump: Flags. (line 328) ! * 0 in constraint: Simple Constraints. (line 130) ! * < in constraint: Simple Constraints. (line 48) * = in constraint: Modifiers. (line 8) ! * > in constraint: Simple Constraints. (line 61) * ? in constraint: Multi-Alternative. (line 42) * \: Output Template. (line 46) * ^ in constraint: Multi-Alternative. (line 53) * __absvdi2: Integer library routines. ! (line 107) * __absvsi2: Integer library routines. ! (line 106) * __addda3: Fixed-point fractional library routines. ! (line 45) * __adddf3: Soft float library routines. ! (line 23) * __adddq3: Fixed-point fractional library routines. ! (line 33) * __addha3: Fixed-point fractional library routines. ! (line 43) * __addhq3: Fixed-point fractional library routines. ! (line 30) * __addqq3: Fixed-point fractional library routines. ! (line 29) * __addsa3: Fixed-point fractional library routines. ! (line 44) * __addsf3: Soft float library routines. ! (line 22) * __addsq3: Fixed-point fractional library routines. ! (line 31) * __addta3: Fixed-point fractional library routines. ! (line 47) * __addtf3: Soft float library routines. ! (line 25) * __adduda3: Fixed-point fractional library routines. ! (line 53) * __addudq3: Fixed-point fractional library routines. ! (line 41) * __adduha3: Fixed-point fractional library routines. ! (line 49) * __adduhq3: Fixed-point fractional library routines. ! (line 37) * __adduqq3: Fixed-point fractional library routines. ! (line 35) * __addusa3: Fixed-point fractional library routines. ! (line 51) * __addusq3: Fixed-point fractional library routines. ! (line 39) * __adduta3: Fixed-point fractional library routines. ! (line 55) * __addvdi3: Integer library routines. ! (line 111) * __addvsi3: Integer library routines. ! (line 110) * __addxf3: Soft float library routines. ! (line 27) * __ashlda3: Fixed-point fractional library routines. ! (line 351) * __ashldi3: Integer library routines. ! (line 14) * __ashldq3: Fixed-point fractional library routines. ! (line 340) * __ashlha3: Fixed-point fractional library routines. ! (line 349) * __ashlhq3: Fixed-point fractional library routines. ! (line 337) * __ashlqq3: Fixed-point fractional library routines. ! (line 336) * __ashlsa3: Fixed-point fractional library routines. ! (line 350) * __ashlsi3: Integer library routines. ! (line 13) * __ashlsq3: Fixed-point fractional library routines. ! (line 338) * __ashlta3: Fixed-point fractional library routines. ! (line 353) * __ashlti3: Integer library routines. ! (line 15) * __ashluda3: Fixed-point fractional library routines. ! (line 359) * __ashludq3: Fixed-point fractional library routines. ! (line 348) * __ashluha3: Fixed-point fractional library routines. ! (line 355) * __ashluhq3: Fixed-point fractional library routines. ! (line 344) * __ashluqq3: Fixed-point fractional library routines. ! (line 342) * __ashlusa3: Fixed-point fractional library routines. ! (line 357) * __ashlusq3: Fixed-point fractional library routines. ! (line 346) * __ashluta3: Fixed-point fractional library routines. ! (line 361) * __ashrda3: Fixed-point fractional library routines. ! (line 371) * __ashrdi3: Integer library routines. ! (line 19) * __ashrdq3: Fixed-point fractional library routines. ! (line 368) * __ashrha3: Fixed-point fractional library routines. ! (line 369) * __ashrhq3: Fixed-point fractional library routines. ! (line 365) * __ashrqq3: Fixed-point fractional library routines. ! (line 364) * __ashrsa3: Fixed-point fractional library routines. ! (line 370) * __ashrsi3: Integer library routines. ! (line 18) * __ashrsq3: Fixed-point fractional library routines. ! (line 366) * __ashrta3: Fixed-point fractional library routines. ! (line 373) * __ashrti3: Integer library routines. ! (line 20) * __bid_adddd3: Decimal float library routines. ! (line 25) * __bid_addsd3: Decimal float library routines. ! (line 21) * __bid_addtd3: Decimal float library routines. ! (line 29) * __bid_divdd3: Decimal float library routines. ! (line 68) * __bid_divsd3: Decimal float library routines. ! (line 64) * __bid_divtd3: Decimal float library routines. ! (line 72) * __bid_eqdd2: Decimal float library routines. ! (line 259) * __bid_eqsd2: Decimal float library routines. ! (line 257) * __bid_eqtd2: Decimal float library routines. ! (line 261) * __bid_extendddtd2: Decimal float library routines. ! (line 92) * __bid_extendddtf: Decimal float library routines. ! (line 140) * __bid_extendddxf: Decimal float library routines. ! (line 134) * __bid_extenddfdd: Decimal float library routines. ! (line 147) * __bid_extenddftd: Decimal float library routines. ! (line 107) * __bid_extendsddd2: Decimal float library routines. ! (line 88) * __bid_extendsddf: Decimal float library routines. ! (line 128) * __bid_extendsdtd2: Decimal float library routines. ! (line 90) * __bid_extendsdtf: Decimal float library routines. ! (line 138) * __bid_extendsdxf: Decimal float library routines. ! (line 132) * __bid_extendsfdd: Decimal float library routines. ! (line 103) * __bid_extendsfsd: Decimal float library routines. ! (line 145) * __bid_extendsftd: Decimal float library routines. ! (line 105) * __bid_extendtftd: Decimal float library routines. ! (line 149) * __bid_extendxftd: Decimal float library routines. ! (line 109) * __bid_fixdddi: Decimal float library routines. ! (line 170) * __bid_fixddsi: Decimal float library routines. ! (line 162) * __bid_fixsddi: Decimal float library routines. ! (line 168) * __bid_fixsdsi: Decimal float library routines. ! (line 160) * __bid_fixtddi: Decimal float library routines. ! (line 172) * __bid_fixtdsi: Decimal float library routines. ! (line 164) * __bid_fixunsdddi: Decimal float library routines. ! (line 187) * __bid_fixunsddsi: Decimal float library routines. ! (line 178) * __bid_fixunssddi: Decimal float library routines. ! (line 185) * __bid_fixunssdsi: Decimal float library routines. ! (line 176) * __bid_fixunstddi: Decimal float library routines. ! (line 189) * __bid_fixunstdsi: Decimal float library routines. ! (line 180) * __bid_floatdidd: Decimal float library routines. ! (line 205) * __bid_floatdisd: Decimal float library routines. ! (line 203) * __bid_floatditd: Decimal float library routines. ! (line 207) * __bid_floatsidd: Decimal float library routines. ! (line 196) * __bid_floatsisd: Decimal float library routines. ! (line 194) * __bid_floatsitd: Decimal float library routines. ! (line 198) * __bid_floatunsdidd: Decimal float library routines. ! (line 223) * __bid_floatunsdisd: Decimal float library routines. ! (line 221) * __bid_floatunsditd: Decimal float library routines. ! (line 225) * __bid_floatunssidd: Decimal float library routines. ! (line 214) * __bid_floatunssisd: Decimal float library routines. ! (line 212) * __bid_floatunssitd: Decimal float library routines. ! (line 216) * __bid_gedd2: Decimal float library routines. ! (line 277) * __bid_gesd2: Decimal float library routines. ! (line 275) * __bid_getd2: Decimal float library routines. ! (line 279) * __bid_gtdd2: Decimal float library routines. ! (line 304) * __bid_gtsd2: Decimal float library routines. ! (line 302) * __bid_gttd2: Decimal float library routines. ! (line 306) * __bid_ledd2: Decimal float library routines. ! (line 295) * __bid_lesd2: Decimal float library routines. ! (line 293) * __bid_letd2: Decimal float library routines. ! (line 297) * __bid_ltdd2: Decimal float library routines. ! (line 286) * __bid_ltsd2: Decimal float library routines. ! (line 284) * __bid_lttd2: Decimal float library routines. ! (line 288) * __bid_muldd3: Decimal float library routines. ! (line 54) * __bid_mulsd3: Decimal float library routines. ! (line 50) * __bid_multd3: Decimal float library routines. ! (line 58) * __bid_nedd2: Decimal float library routines. ! (line 268) * __bid_negdd2: Decimal float library routines. ! (line 78) * __bid_negsd2: Decimal float library routines. ! (line 76) * __bid_negtd2: Decimal float library routines. ! (line 80) * __bid_nesd2: Decimal float library routines. ! (line 266) * __bid_netd2: Decimal float library routines. ! (line 270) * __bid_subdd3: Decimal float library routines. ! (line 39) * __bid_subsd3: Decimal float library routines. ! (line 35) * __bid_subtd3: Decimal float library routines. ! (line 43) * __bid_truncdddf: Decimal float library routines. ! (line 153) * __bid_truncddsd2: Decimal float library routines. ! (line 94) * __bid_truncddsf: Decimal float library routines. ! (line 124) * __bid_truncdfsd: Decimal float library routines. ! (line 111) * __bid_truncsdsf: Decimal float library routines. ! (line 151) * __bid_trunctddd2: Decimal float library routines. ! (line 98) * __bid_trunctddf: Decimal float library routines. ! (line 130) * __bid_trunctdsd2: Decimal float library routines. ! (line 96) * __bid_trunctdsf: Decimal float library routines. ! (line 126) * __bid_trunctdtf: Decimal float library routines. ! (line 155) * __bid_trunctdxf: Decimal float library routines. ! (line 136) * __bid_trunctfdd: Decimal float library routines. ! (line 119) * __bid_trunctfsd: Decimal float library routines. ! (line 115) * __bid_truncxfdd: Decimal float library routines. ! (line 117) * __bid_truncxfsd: Decimal float library routines. ! (line 113) * __bid_unorddd2: Decimal float library routines. ! (line 235) * __bid_unordsd2: Decimal float library routines. ! (line 233) * __bid_unordtd2: Decimal float library routines. ! (line 237) * __bswapdi2: Integer library routines. ! (line 162) * __bswapsi2: Integer library routines. ! (line 161) ! * __builtin_classify_type: Varargs. (line 51) ! * __builtin_next_arg: Varargs. (line 42) ! * __builtin_saveregs: Varargs. (line 24) ! * __chkp_bndcl: Misc. (line 652) ! * __chkp_bndcu: Misc. (line 658) ! * __chkp_bndldx: Misc. (line 646) ! * __chkp_bndmk: Misc. (line 633) ! * __chkp_bndret: Misc. (line 663) ! * __chkp_bndstx: Misc. (line 640) ! * __chkp_intersect: Misc. (line 670) ! * __chkp_narrow: Misc. (line 675) ! * __chkp_sizeof: Misc. (line 680) * __clear_cache: Miscellaneous routines. ! (line 10) * __clzdi2: Integer library routines. ! (line 131) * __clzsi2: Integer library routines. ! (line 130) * __clzti2: Integer library routines. ! (line 132) * __cmpda2: Fixed-point fractional library routines. ! (line 451) * __cmpdf2: Soft float library routines. ! (line 164) * __cmpdi2: Integer library routines. ! (line 87) * __cmpdq2: Fixed-point fractional library routines. ! (line 441) * __cmpha2: Fixed-point fractional library routines. ! (line 449) * __cmphq2: Fixed-point fractional library routines. ! (line 438) * __cmpqq2: Fixed-point fractional library routines. ! (line 437) * __cmpsa2: Fixed-point fractional library routines. ! (line 450) * __cmpsf2: Soft float library routines. ! (line 163) * __cmpsq2: Fixed-point fractional library routines. ! (line 439) * __cmpta2: Fixed-point fractional library routines. ! (line 453) * __cmptf2: Soft float library routines. ! (line 165) * __cmpti2: Integer library routines. ! (line 88) * __cmpuda2: Fixed-point fractional library routines. ! (line 458) * __cmpudq2: Fixed-point fractional library routines. ! (line 448) * __cmpuha2: Fixed-point fractional library routines. ! (line 455) * __cmpuhq2: Fixed-point fractional library routines. ! (line 444) * __cmpuqq2: Fixed-point fractional library routines. ! (line 443) * __cmpusa2: Fixed-point fractional library routines. ! (line 456) * __cmpusq2: Fixed-point fractional library routines. ! (line 446) * __cmputa2: Fixed-point fractional library routines. ! (line 460) * __CTOR_LIST__: Initialization. (line 25) * __ctzdi2: Integer library routines. ! (line 138) * __ctzsi2: Integer library routines. ! (line 137) * __ctzti2: Integer library routines. ! (line 139) * __divda3: Fixed-point fractional library routines. ! (line 227) * __divdc3: Soft float library routines. ! (line 252) * __divdf3: Soft float library routines. ! (line 48) * __divdi3: Integer library routines. ! (line 25) * __divdq3: Fixed-point fractional library routines. ! (line 223) * __divha3: Fixed-point fractional library routines. ! (line 225) * __divhq3: Fixed-point fractional library routines. ! (line 220) * __divqq3: Fixed-point fractional library routines. ! (line 219) * __divsa3: Fixed-point fractional library routines. ! (line 226) * __divsc3: Soft float library routines. ! (line 250) * __divsf3: Soft float library routines. ! (line 47) * __divsi3: Integer library routines. ! (line 24) * __divsq3: Fixed-point fractional library routines. ! (line 221) * __divta3: Fixed-point fractional library routines. ! (line 229) * __divtc3: Soft float library routines. ! (line 254) * __divtf3: Soft float library routines. ! (line 50) * __divti3: Integer library routines. ! (line 26) * __divxc3: Soft float library routines. ! (line 256) * __divxf3: Soft float library routines. ! (line 52) * __dpd_adddd3: Decimal float library routines. ! (line 23) * __dpd_addsd3: Decimal float library routines. ! (line 19) * __dpd_addtd3: Decimal float library routines. ! (line 27) * __dpd_divdd3: Decimal float library routines. ! (line 66) * __dpd_divsd3: Decimal float library routines. ! (line 62) * __dpd_divtd3: Decimal float library routines. ! (line 70) * __dpd_eqdd2: Decimal float library routines. ! (line 258) * __dpd_eqsd2: Decimal float library routines. ! (line 256) * __dpd_eqtd2: Decimal float library routines. ! (line 260) * __dpd_extendddtd2: Decimal float library routines. ! (line 91) * __dpd_extendddtf: Decimal float library routines. ! (line 139) * __dpd_extendddxf: Decimal float library routines. ! (line 133) * __dpd_extenddfdd: Decimal float library routines. ! (line 146) * __dpd_extenddftd: Decimal float library routines. ! (line 106) * __dpd_extendsddd2: Decimal float library routines. ! (line 87) * __dpd_extendsddf: Decimal float library routines. ! (line 127) * __dpd_extendsdtd2: Decimal float library routines. ! (line 89) * __dpd_extendsdtf: Decimal float library routines. ! (line 137) * __dpd_extendsdxf: Decimal float library routines. ! (line 131) * __dpd_extendsfdd: Decimal float library routines. ! (line 102) * __dpd_extendsfsd: Decimal float library routines. ! (line 144) * __dpd_extendsftd: Decimal float library routines. ! (line 104) * __dpd_extendtftd: Decimal float library routines. ! (line 148) * __dpd_extendxftd: Decimal float library routines. ! (line 108) * __dpd_fixdddi: Decimal float library routines. ! (line 169) * __dpd_fixddsi: Decimal float library routines. ! (line 161) * __dpd_fixsddi: Decimal float library routines. ! (line 167) * __dpd_fixsdsi: Decimal float library routines. ! (line 159) * __dpd_fixtddi: Decimal float library routines. ! (line 171) * __dpd_fixtdsi: Decimal float library routines. ! (line 163) * __dpd_fixunsdddi: Decimal float library routines. ! (line 186) * __dpd_fixunsddsi: Decimal float library routines. ! (line 177) * __dpd_fixunssddi: Decimal float library routines. ! (line 184) * __dpd_fixunssdsi: Decimal float library routines. ! (line 175) * __dpd_fixunstddi: Decimal float library routines. ! (line 188) * __dpd_fixunstdsi: Decimal float library routines. ! (line 179) * __dpd_floatdidd: Decimal float library routines. ! (line 204) * __dpd_floatdisd: Decimal float library routines. ! (line 202) * __dpd_floatditd: Decimal float library routines. ! (line 206) * __dpd_floatsidd: Decimal float library routines. ! (line 195) * __dpd_floatsisd: Decimal float library routines. ! (line 193) * __dpd_floatsitd: Decimal float library routines. ! (line 197) * __dpd_floatunsdidd: Decimal float library routines. ! (line 222) * __dpd_floatunsdisd: Decimal float library routines. ! (line 220) * __dpd_floatunsditd: Decimal float library routines. ! (line 224) * __dpd_floatunssidd: Decimal float library routines. ! (line 213) * __dpd_floatunssisd: Decimal float library routines. ! (line 211) * __dpd_floatunssitd: Decimal float library routines. ! (line 215) * __dpd_gedd2: Decimal float library routines. ! (line 276) * __dpd_gesd2: Decimal float library routines. ! (line 274) * __dpd_getd2: Decimal float library routines. ! (line 278) * __dpd_gtdd2: Decimal float library routines. ! (line 303) * __dpd_gtsd2: Decimal float library routines. ! (line 301) * __dpd_gttd2: Decimal float library routines. ! (line 305) * __dpd_ledd2: Decimal float library routines. ! (line 294) * __dpd_lesd2: Decimal float library routines. ! (line 292) * __dpd_letd2: Decimal float library routines. ! (line 296) * __dpd_ltdd2: Decimal float library routines. ! (line 285) * __dpd_ltsd2: Decimal float library routines. ! (line 283) * __dpd_lttd2: Decimal float library routines. ! (line 287) * __dpd_muldd3: Decimal float library routines. ! (line 52) * __dpd_mulsd3: Decimal float library routines. ! (line 48) * __dpd_multd3: Decimal float library routines. ! (line 56) * __dpd_nedd2: Decimal float library routines. ! (line 267) * __dpd_negdd2: Decimal float library routines. ! (line 77) * __dpd_negsd2: Decimal float library routines. ! (line 75) * __dpd_negtd2: Decimal float library routines. ! (line 79) * __dpd_nesd2: Decimal float library routines. ! (line 265) * __dpd_netd2: Decimal float library routines. ! (line 269) * __dpd_subdd3: Decimal float library routines. ! (line 37) * __dpd_subsd3: Decimal float library routines. ! (line 33) * __dpd_subtd3: Decimal float library routines. ! (line 41) * __dpd_truncdddf: Decimal float library routines. ! (line 152) * __dpd_truncddsd2: Decimal float library routines. ! (line 93) * __dpd_truncddsf: Decimal float library routines. ! (line 123) * __dpd_truncdfsd: Decimal float library routines. ! (line 110) * __dpd_truncsdsf: Decimal float library routines. ! (line 150) * __dpd_trunctddd2: Decimal float library routines. ! (line 97) * __dpd_trunctddf: Decimal float library routines. ! (line 129) * __dpd_trunctdsd2: Decimal float library routines. ! (line 95) * __dpd_trunctdsf: Decimal float library routines. ! (line 125) * __dpd_trunctdtf: Decimal float library routines. ! (line 154) * __dpd_trunctdxf: Decimal float library routines. ! (line 135) * __dpd_trunctfdd: Decimal float library routines. ! (line 118) * __dpd_trunctfsd: Decimal float library routines. ! (line 114) * __dpd_truncxfdd: Decimal float library routines. ! (line 116) * __dpd_truncxfsd: Decimal float library routines. ! (line 112) * __dpd_unorddd2: Decimal float library routines. ! (line 234) * __dpd_unordsd2: Decimal float library routines. ! (line 232) * __dpd_unordtd2: Decimal float library routines. ! (line 236) * __DTOR_LIST__: Initialization. (line 25) * __eqdf2: Soft float library routines. ! (line 194) * __eqsf2: Soft float library routines. ! (line 193) * __eqtf2: Soft float library routines. ! (line 195) * __extenddftf2: Soft float library routines. (line 68) + * __extenddfxf2: Soft float library routines. + (line 69) * __extendsfdf2: Soft float library routines. (line 65) ! * __extendsftf2: Soft float library routines. (line 66) + * __extendsfxf2: Soft float library routines. + (line 67) * __ffsdi2: Integer library routines. (line 144) + * __ffsti2: Integer library routines. + (line 145) * __fixdfdi: Soft float library routines. ! (line 88) * __fixdfsi: Soft float library routines. ! (line 81) * __fixdfti: Soft float library routines. ! (line 94) * __fixsfdi: Soft float library routines. ! (line 87) * __fixsfsi: Soft float library routines. ! (line 80) * __fixsfti: Soft float library routines. ! (line 93) * __fixtfdi: Soft float library routines. ! (line 89) * __fixtfsi: Soft float library routines. ! (line 82) * __fixtfti: Soft float library routines. ! (line 95) * __fixunsdfdi: Soft float library routines. ! (line 108) * __fixunsdfsi: Soft float library routines. ! (line 101) * __fixunsdfti: Soft float library routines. ! (line 115) * __fixunssfdi: Soft float library routines. ! (line 107) * __fixunssfsi: Soft float library routines. ! (line 100) * __fixunssfti: Soft float library routines. ! (line 114) * __fixunstfdi: Soft float library routines. ! (line 109) * __fixunstfsi: Soft float library routines. ! (line 102) * __fixunstfti: Soft float library routines. ! (line 116) * __fixunsxfdi: Soft float library routines. ! (line 110) * __fixunsxfsi: Soft float library routines. ! (line 103) * __fixunsxfti: Soft float library routines. ! (line 117) * __fixxfdi: Soft float library routines. ! (line 90) * __fixxfsi: Soft float library routines. ! (line 83) * __fixxfti: Soft float library routines. ! (line 96) * __floatdidf: Soft float library routines. ! (line 128) * __floatdisf: Soft float library routines. ! (line 127) * __floatditf: Soft float library routines. (line 129) + * __floatdixf: Soft float library routines. + (line 130) * __floatsidf: Soft float library routines. ! (line 122) * __floatsisf: Soft float library routines. ! (line 121) * __floatsitf: Soft float library routines. (line 123) + * __floatsixf: Soft float library routines. + (line 124) * __floattidf: Soft float library routines. ! (line 134) * __floattisf: Soft float library routines. ! (line 133) * __floattitf: Soft float library routines. (line 135) + * __floattixf: Soft float library routines. + (line 136) * __floatundidf: Soft float library routines. ! (line 146) * __floatundisf: Soft float library routines. ! (line 145) * __floatunditf: Soft float library routines. (line 147) + * __floatundixf: Soft float library routines. + (line 148) * __floatunsidf: Soft float library routines. ! (line 140) * __floatunsisf: Soft float library routines. ! (line 139) * __floatunsitf: Soft float library routines. (line 141) + * __floatunsixf: Soft float library routines. + (line 142) * __floatuntidf: Soft float library routines. ! (line 152) * __floatuntisf: Soft float library routines. ! (line 151) * __floatuntitf: Soft float library routines. (line 153) + * __floatuntixf: Soft float library routines. + (line 154) * __fractdadf: Fixed-point fractional library routines. ! (line 636) * __fractdadi: Fixed-point fractional library routines. ! (line 633) * __fractdadq: Fixed-point fractional library routines. ! (line 616) * __fractdaha2: Fixed-point fractional library routines. ! (line 617) * __fractdahi: Fixed-point fractional library routines. ! (line 631) * __fractdahq: Fixed-point fractional library routines. ! (line 614) * __fractdaqi: Fixed-point fractional library routines. ! (line 630) * __fractdaqq: Fixed-point fractional library routines. ! (line 613) * __fractdasa2: Fixed-point fractional library routines. ! (line 618) * __fractdasf: Fixed-point fractional library routines. ! (line 635) * __fractdasi: Fixed-point fractional library routines. ! (line 632) * __fractdasq: Fixed-point fractional library routines. ! (line 615) * __fractdata2: Fixed-point fractional library routines. ! (line 619) * __fractdati: Fixed-point fractional library routines. (line 634) + * __fractdauda: Fixed-point fractional library routines. + (line 627) * __fractdaudq: Fixed-point fractional library routines. ! (line 624) * __fractdauha: Fixed-point fractional library routines. ! (line 625) * __fractdauhq: Fixed-point fractional library routines. ! (line 621) * __fractdauqq: Fixed-point fractional library routines. ! (line 620) * __fractdausa: Fixed-point fractional library routines. ! (line 626) * __fractdausq: Fixed-point fractional library routines. ! (line 622) * __fractdauta: Fixed-point fractional library routines. ! (line 629) * __fractdfda: Fixed-point fractional library routines. ! (line 1025) * __fractdfdq: Fixed-point fractional library routines. ! (line 1022) * __fractdfha: Fixed-point fractional library routines. ! (line 1023) * __fractdfhq: Fixed-point fractional library routines. ! (line 1020) * __fractdfqq: Fixed-point fractional library routines. ! (line 1019) * __fractdfsa: Fixed-point fractional library routines. ! (line 1024) * __fractdfsq: Fixed-point fractional library routines. ! (line 1021) * __fractdfta: Fixed-point fractional library routines. ! (line 1026) * __fractdfuda: Fixed-point fractional library routines. ! (line 1033) * __fractdfudq: Fixed-point fractional library routines. ! (line 1030) * __fractdfuha: Fixed-point fractional library routines. ! (line 1031) * __fractdfuhq: Fixed-point fractional library routines. ! (line 1028) * __fractdfuqq: Fixed-point fractional library routines. ! (line 1027) * __fractdfusa: Fixed-point fractional library routines. ! (line 1032) * __fractdfusq: Fixed-point fractional library routines. ! (line 1029) * __fractdfuta: Fixed-point fractional library routines. ! (line 1034) * __fractdida: Fixed-point fractional library routines. ! (line 975) * __fractdidq: Fixed-point fractional library routines. ! (line 972) * __fractdiha: Fixed-point fractional library routines. ! (line 973) * __fractdihq: Fixed-point fractional library routines. ! (line 970) * __fractdiqq: Fixed-point fractional library routines. ! (line 969) * __fractdisa: Fixed-point fractional library routines. ! (line 974) * __fractdisq: Fixed-point fractional library routines. ! (line 971) * __fractdita: Fixed-point fractional library routines. ! (line 976) * __fractdiuda: Fixed-point fractional library routines. ! (line 983) * __fractdiudq: Fixed-point fractional library routines. ! (line 980) * __fractdiuha: Fixed-point fractional library routines. ! (line 981) * __fractdiuhq: Fixed-point fractional library routines. ! (line 978) * __fractdiuqq: Fixed-point fractional library routines. ! (line 977) * __fractdiusa: Fixed-point fractional library routines. ! (line 982) * __fractdiusq: Fixed-point fractional library routines. ! (line 979) * __fractdiuta: Fixed-point fractional library routines. ! (line 984) * __fractdqda: Fixed-point fractional library routines. ! (line 544) * __fractdqdf: Fixed-point fractional library routines. ! (line 566) * __fractdqdi: Fixed-point fractional library routines. ! (line 563) * __fractdqha: Fixed-point fractional library routines. ! (line 542) * __fractdqhi: Fixed-point fractional library routines. ! (line 561) * __fractdqhq2: Fixed-point fractional library routines. ! (line 540) * __fractdqqi: Fixed-point fractional library routines. ! (line 560) * __fractdqqq2: Fixed-point fractional library routines. ! (line 539) * __fractdqsa: Fixed-point fractional library routines. ! (line 543) * __fractdqsf: Fixed-point fractional library routines. ! (line 565) * __fractdqsi: Fixed-point fractional library routines. ! (line 562) * __fractdqsq2: Fixed-point fractional library routines. ! (line 541) * __fractdqta: Fixed-point fractional library routines. ! (line 545) * __fractdqti: Fixed-point fractional library routines. ! (line 564) * __fractdquda: Fixed-point fractional library routines. ! (line 557) * __fractdqudq: Fixed-point fractional library routines. ! (line 552) * __fractdquha: Fixed-point fractional library routines. ! (line 554) * __fractdquhq: Fixed-point fractional library routines. ! (line 548) * __fractdquqq: Fixed-point fractional library routines. ! (line 547) * __fractdqusa: Fixed-point fractional library routines. ! (line 555) * __fractdqusq: Fixed-point fractional library routines. ! (line 550) * __fractdquta: Fixed-point fractional library routines. ! (line 559) * __fracthada2: Fixed-point fractional library routines. ! (line 572) * __fracthadf: Fixed-point fractional library routines. ! (line 590) * __fracthadi: Fixed-point fractional library routines. ! (line 587) * __fracthadq: Fixed-point fractional library routines. ! (line 570) * __fracthahi: Fixed-point fractional library routines. ! (line 585) * __fracthahq: Fixed-point fractional library routines. ! (line 568) * __fracthaqi: Fixed-point fractional library routines. ! (line 584) * __fracthaqq: Fixed-point fractional library routines. ! (line 567) * __fracthasa2: Fixed-point fractional library routines. ! (line 571) * __fracthasf: Fixed-point fractional library routines. ! (line 589) * __fracthasi: Fixed-point fractional library routines. ! (line 586) * __fracthasq: Fixed-point fractional library routines. ! (line 569) * __fracthata2: Fixed-point fractional library routines. ! (line 573) * __fracthati: Fixed-point fractional library routines. (line 588) + * __fracthauda: Fixed-point fractional library routines. + (line 581) * __fracthaudq: Fixed-point fractional library routines. ! (line 578) * __fracthauha: Fixed-point fractional library routines. ! (line 579) * __fracthauhq: Fixed-point fractional library routines. ! (line 575) * __fracthauqq: Fixed-point fractional library routines. ! (line 574) * __fracthausa: Fixed-point fractional library routines. ! (line 580) * __fracthausq: Fixed-point fractional library routines. ! (line 576) * __fracthauta: Fixed-point fractional library routines. ! (line 583) * __fracthida: Fixed-point fractional library routines. ! (line 943) * __fracthidq: Fixed-point fractional library routines. ! (line 940) * __fracthiha: Fixed-point fractional library routines. ! (line 941) * __fracthihq: Fixed-point fractional library routines. ! (line 938) * __fracthiqq: Fixed-point fractional library routines. ! (line 937) * __fracthisa: Fixed-point fractional library routines. ! (line 942) * __fracthisq: Fixed-point fractional library routines. ! (line 939) * __fracthita: Fixed-point fractional library routines. ! (line 944) * __fracthiuda: Fixed-point fractional library routines. ! (line 951) * __fracthiudq: Fixed-point fractional library routines. ! (line 948) * __fracthiuha: Fixed-point fractional library routines. ! (line 949) * __fracthiuhq: Fixed-point fractional library routines. ! (line 946) * __fracthiuqq: Fixed-point fractional library routines. ! (line 945) * __fracthiusa: Fixed-point fractional library routines. ! (line 950) * __fracthiusq: Fixed-point fractional library routines. ! (line 947) * __fracthiuta: Fixed-point fractional library routines. ! (line 952) * __fracthqda: Fixed-point fractional library routines. ! (line 498) * __fracthqdf: Fixed-point fractional library routines. ! (line 514) * __fracthqdi: Fixed-point fractional library routines. ! (line 511) * __fracthqdq2: Fixed-point fractional library routines. ! (line 495) * __fracthqha: Fixed-point fractional library routines. ! (line 496) * __fracthqhi: Fixed-point fractional library routines. ! (line 509) * __fracthqqi: Fixed-point fractional library routines. ! (line 508) * __fracthqqq2: Fixed-point fractional library routines. ! (line 493) * __fracthqsa: Fixed-point fractional library routines. ! (line 497) * __fracthqsf: Fixed-point fractional library routines. ! (line 513) * __fracthqsi: Fixed-point fractional library routines. ! (line 510) * __fracthqsq2: Fixed-point fractional library routines. ! (line 494) * __fracthqta: Fixed-point fractional library routines. ! (line 499) * __fracthqti: Fixed-point fractional library routines. ! (line 512) * __fracthquda: Fixed-point fractional library routines. ! (line 506) * __fracthqudq: Fixed-point fractional library routines. ! (line 503) * __fracthquha: Fixed-point fractional library routines. ! (line 504) * __fracthquhq: Fixed-point fractional library routines. ! (line 501) * __fracthquqq: Fixed-point fractional library routines. ! (line 500) * __fracthqusa: Fixed-point fractional library routines. ! (line 505) * __fracthqusq: Fixed-point fractional library routines. ! (line 502) * __fracthquta: Fixed-point fractional library routines. ! (line 507) * __fractqida: Fixed-point fractional library routines. ! (line 925) * __fractqidq: Fixed-point fractional library routines. ! (line 922) * __fractqiha: Fixed-point fractional library routines. ! (line 923) * __fractqihq: Fixed-point fractional library routines. ! (line 920) * __fractqiqq: Fixed-point fractional library routines. ! (line 919) * __fractqisa: Fixed-point fractional library routines. ! (line 924) * __fractqisq: Fixed-point fractional library routines. ! (line 921) * __fractqita: Fixed-point fractional library routines. ! (line 926) * __fractqiuda: Fixed-point fractional library routines. ! (line 934) * __fractqiudq: Fixed-point fractional library routines. ! (line 931) * __fractqiuha: Fixed-point fractional library routines. ! (line 932) * __fractqiuhq: Fixed-point fractional library routines. ! (line 928) * __fractqiuqq: Fixed-point fractional library routines. ! (line 927) * __fractqiusa: Fixed-point fractional library routines. ! (line 933) * __fractqiusq: Fixed-point fractional library routines. ! (line 929) * __fractqiuta: Fixed-point fractional library routines. ! (line 936) * __fractqqda: Fixed-point fractional library routines. ! (line 474) * __fractqqdf: Fixed-point fractional library routines. ! (line 492) * __fractqqdi: Fixed-point fractional library routines. ! (line 489) * __fractqqdq2: Fixed-point fractional library routines. ! (line 471) * __fractqqha: Fixed-point fractional library routines. ! (line 472) * __fractqqhi: Fixed-point fractional library routines. ! (line 487) * __fractqqhq2: Fixed-point fractional library routines. ! (line 469) * __fractqqqi: Fixed-point fractional library routines. ! (line 486) * __fractqqsa: Fixed-point fractional library routines. ! (line 473) * __fractqqsf: Fixed-point fractional library routines. ! (line 491) * __fractqqsi: Fixed-point fractional library routines. ! (line 488) * __fractqqsq2: Fixed-point fractional library routines. ! (line 470) * __fractqqta: Fixed-point fractional library routines. ! (line 475) * __fractqqti: Fixed-point fractional library routines. (line 490) + * __fractqquda: Fixed-point fractional library routines. + (line 483) * __fractqqudq: Fixed-point fractional library routines. ! (line 480) * __fractqquha: Fixed-point fractional library routines. ! (line 481) * __fractqquhq: Fixed-point fractional library routines. ! (line 477) * __fractqquqq: Fixed-point fractional library routines. ! (line 476) * __fractqqusa: Fixed-point fractional library routines. ! (line 482) * __fractqqusq: Fixed-point fractional library routines. ! (line 478) * __fractqquta: Fixed-point fractional library routines. ! (line 485) * __fractsada2: Fixed-point fractional library routines. ! (line 596) * __fractsadf: Fixed-point fractional library routines. ! (line 612) * __fractsadi: Fixed-point fractional library routines. ! (line 609) * __fractsadq: Fixed-point fractional library routines. ! (line 594) * __fractsaha2: Fixed-point fractional library routines. ! (line 595) * __fractsahi: Fixed-point fractional library routines. ! (line 607) * __fractsahq: Fixed-point fractional library routines. ! (line 592) * __fractsaqi: Fixed-point fractional library routines. ! (line 606) * __fractsaqq: Fixed-point fractional library routines. ! (line 591) * __fractsasf: Fixed-point fractional library routines. ! (line 611) * __fractsasi: Fixed-point fractional library routines. ! (line 608) * __fractsasq: Fixed-point fractional library routines. ! (line 593) * __fractsata2: Fixed-point fractional library routines. ! (line 597) * __fractsati: Fixed-point fractional library routines. ! (line 610) * __fractsauda: Fixed-point fractional library routines. ! (line 604) * __fractsaudq: Fixed-point fractional library routines. ! (line 601) * __fractsauha: Fixed-point fractional library routines. ! (line 602) * __fractsauhq: Fixed-point fractional library routines. ! (line 599) * __fractsauqq: Fixed-point fractional library routines. ! (line 598) * __fractsausa: Fixed-point fractional library routines. ! (line 603) * __fractsausq: Fixed-point fractional library routines. ! (line 600) * __fractsauta: Fixed-point fractional library routines. ! (line 605) * __fractsfda: Fixed-point fractional library routines. ! (line 1009) * __fractsfdq: Fixed-point fractional library routines. ! (line 1006) * __fractsfha: Fixed-point fractional library routines. ! (line 1007) * __fractsfhq: Fixed-point fractional library routines. ! (line 1004) * __fractsfqq: Fixed-point fractional library routines. ! (line 1003) * __fractsfsa: Fixed-point fractional library routines. ! (line 1008) * __fractsfsq: Fixed-point fractional library routines. ! (line 1005) * __fractsfta: Fixed-point fractional library routines. ! (line 1010) * __fractsfuda: Fixed-point fractional library routines. ! (line 1017) * __fractsfudq: Fixed-point fractional library routines. ! (line 1014) * __fractsfuha: Fixed-point fractional library routines. ! (line 1015) * __fractsfuhq: Fixed-point fractional library routines. ! (line 1012) * __fractsfuqq: Fixed-point fractional library routines. ! (line 1011) * __fractsfusa: Fixed-point fractional library routines. ! (line 1016) * __fractsfusq: Fixed-point fractional library routines. ! (line 1013) * __fractsfuta: Fixed-point fractional library routines. ! (line 1018) * __fractsida: Fixed-point fractional library routines. ! (line 959) * __fractsidq: Fixed-point fractional library routines. ! (line 956) * __fractsiha: Fixed-point fractional library routines. ! (line 957) * __fractsihq: Fixed-point fractional library routines. ! (line 954) * __fractsiqq: Fixed-point fractional library routines. ! (line 953) * __fractsisa: Fixed-point fractional library routines. ! (line 958) * __fractsisq: Fixed-point fractional library routines. ! (line 955) * __fractsita: Fixed-point fractional library routines. ! (line 960) * __fractsiuda: Fixed-point fractional library routines. ! (line 967) * __fractsiudq: Fixed-point fractional library routines. ! (line 964) * __fractsiuha: Fixed-point fractional library routines. ! (line 965) * __fractsiuhq: Fixed-point fractional library routines. ! (line 962) * __fractsiuqq: Fixed-point fractional library routines. ! (line 961) * __fractsiusa: Fixed-point fractional library routines. ! (line 966) * __fractsiusq: Fixed-point fractional library routines. ! (line 963) * __fractsiuta: Fixed-point fractional library routines. ! (line 968) * __fractsqda: Fixed-point fractional library routines. ! (line 520) * __fractsqdf: Fixed-point fractional library routines. ! (line 538) * __fractsqdi: Fixed-point fractional library routines. ! (line 535) * __fractsqdq2: Fixed-point fractional library routines. ! (line 517) * __fractsqha: Fixed-point fractional library routines. ! (line 518) * __fractsqhi: Fixed-point fractional library routines. ! (line 533) * __fractsqhq2: Fixed-point fractional library routines. ! (line 516) * __fractsqqi: Fixed-point fractional library routines. ! (line 532) * __fractsqqq2: Fixed-point fractional library routines. ! (line 515) * __fractsqsa: Fixed-point fractional library routines. ! (line 519) * __fractsqsf: Fixed-point fractional library routines. ! (line 537) * __fractsqsi: Fixed-point fractional library routines. ! (line 534) * __fractsqta: Fixed-point fractional library routines. ! (line 521) * __fractsqti: Fixed-point fractional library routines. (line 536) + * __fractsquda: Fixed-point fractional library routines. + (line 529) * __fractsqudq: Fixed-point fractional library routines. ! (line 526) * __fractsquha: Fixed-point fractional library routines. ! (line 527) * __fractsquhq: Fixed-point fractional library routines. ! (line 523) * __fractsquqq: Fixed-point fractional library routines. ! (line 522) * __fractsqusa: Fixed-point fractional library routines. ! (line 528) * __fractsqusq: Fixed-point fractional library routines. ! (line 524) * __fractsquta: Fixed-point fractional library routines. ! (line 531) * __fracttada2: Fixed-point fractional library routines. ! (line 643) * __fracttadf: Fixed-point fractional library routines. ! (line 664) * __fracttadi: Fixed-point fractional library routines. ! (line 661) * __fracttadq: Fixed-point fractional library routines. ! (line 640) * __fracttaha2: Fixed-point fractional library routines. ! (line 641) * __fracttahi: Fixed-point fractional library routines. ! (line 659) * __fracttahq: Fixed-point fractional library routines. ! (line 638) * __fracttaqi: Fixed-point fractional library routines. ! (line 658) * __fracttaqq: Fixed-point fractional library routines. ! (line 637) * __fracttasa2: Fixed-point fractional library routines. ! (line 642) * __fracttasf: Fixed-point fractional library routines. ! (line 663) * __fracttasi: Fixed-point fractional library routines. ! (line 660) * __fracttasq: Fixed-point fractional library routines. ! (line 639) * __fracttati: Fixed-point fractional library routines. ! (line 662) * __fracttauda: Fixed-point fractional library routines. ! (line 655) * __fracttaudq: Fixed-point fractional library routines. ! (line 650) * __fracttauha: Fixed-point fractional library routines. ! (line 652) * __fracttauhq: Fixed-point fractional library routines. ! (line 646) * __fracttauqq: Fixed-point fractional library routines. ! (line 645) * __fracttausa: Fixed-point fractional library routines. ! (line 653) * __fracttausq: Fixed-point fractional library routines. ! (line 648) * __fracttauta: Fixed-point fractional library routines. ! (line 657) * __fracttida: Fixed-point fractional library routines. ! (line 991) * __fracttidq: Fixed-point fractional library routines. ! (line 988) * __fracttiha: Fixed-point fractional library routines. ! (line 989) * __fracttihq: Fixed-point fractional library routines. ! (line 986) * __fracttiqq: Fixed-point fractional library routines. ! (line 985) * __fracttisa: Fixed-point fractional library routines. ! (line 990) * __fracttisq: Fixed-point fractional library routines. ! (line 987) * __fracttita: Fixed-point fractional library routines. ! (line 992) * __fracttiuda: Fixed-point fractional library routines. ! (line 1000) * __fracttiudq: Fixed-point fractional library routines. ! (line 997) * __fracttiuha: Fixed-point fractional library routines. ! (line 998) * __fracttiuhq: Fixed-point fractional library routines. ! (line 994) * __fracttiuqq: Fixed-point fractional library routines. ! (line 993) * __fracttiusa: Fixed-point fractional library routines. ! (line 999) * __fracttiusq: Fixed-point fractional library routines. ! (line 995) * __fracttiuta: Fixed-point fractional library routines. ! (line 1002) * __fractudada: Fixed-point fractional library routines. ! (line 858) * __fractudadf: Fixed-point fractional library routines. ! (line 881) * __fractudadi: Fixed-point fractional library routines. ! (line 878) * __fractudadq: Fixed-point fractional library routines. ! (line 855) * __fractudaha: Fixed-point fractional library routines. ! (line 856) * __fractudahi: Fixed-point fractional library routines. ! (line 876) * __fractudahq: Fixed-point fractional library routines. ! (line 852) * __fractudaqi: Fixed-point fractional library routines. ! (line 875) * __fractudaqq: Fixed-point fractional library routines. ! (line 851) * __fractudasa: Fixed-point fractional library routines. ! (line 857) * __fractudasf: Fixed-point fractional library routines. ! (line 880) * __fractudasi: Fixed-point fractional library routines. ! (line 877) * __fractudasq: Fixed-point fractional library routines. ! (line 853) * __fractudata: Fixed-point fractional library routines. ! (line 860) * __fractudati: Fixed-point fractional library routines. ! (line 879) * __fractudaudq: Fixed-point fractional library routines. ! (line 868) * __fractudauha2: Fixed-point fractional library routines. (line 870) + * __fractudauhq: Fixed-point fractional library routines. + (line 864) * __fractudauqq: Fixed-point fractional library routines. ! (line 862) * __fractudausa2: Fixed-point fractional library routines. (line 872) + * __fractudausq: Fixed-point fractional library routines. + (line 866) * __fractudauta2: Fixed-point fractional library routines. ! (line 874) * __fractudqda: Fixed-point fractional library routines. ! (line 766) * __fractudqdf: Fixed-point fractional library routines. ! (line 791) * __fractudqdi: Fixed-point fractional library routines. ! (line 787) * __fractudqdq: Fixed-point fractional library routines. ! (line 761) * __fractudqha: Fixed-point fractional library routines. ! (line 763) * __fractudqhi: Fixed-point fractional library routines. ! (line 785) * __fractudqhq: Fixed-point fractional library routines. ! (line 757) * __fractudqqi: Fixed-point fractional library routines. ! (line 784) * __fractudqqq: Fixed-point fractional library routines. ! (line 756) * __fractudqsa: Fixed-point fractional library routines. ! (line 764) * __fractudqsf: Fixed-point fractional library routines. ! (line 790) * __fractudqsi: Fixed-point fractional library routines. ! (line 786) * __fractudqsq: Fixed-point fractional library routines. ! (line 759) * __fractudqta: Fixed-point fractional library routines. ! (line 768) * __fractudqti: Fixed-point fractional library routines. ! (line 789) * __fractudquda: Fixed-point fractional library routines. ! (line 780) * __fractudquha: Fixed-point fractional library routines. ! (line 776) * __fractudquhq2: Fixed-point fractional library routines. ! (line 772) * __fractudquqq2: Fixed-point fractional library routines. ! (line 770) * __fractudqusa: Fixed-point fractional library routines. ! (line 778) * __fractudqusq2: Fixed-point fractional library routines. ! (line 774) * __fractudquta: Fixed-point fractional library routines. ! (line 782) * __fractuhada: Fixed-point fractional library routines. ! (line 799) * __fractuhadf: Fixed-point fractional library routines. ! (line 822) * __fractuhadi: Fixed-point fractional library routines. ! (line 819) * __fractuhadq: Fixed-point fractional library routines. ! (line 796) * __fractuhaha: Fixed-point fractional library routines. ! (line 797) * __fractuhahi: Fixed-point fractional library routines. ! (line 817) * __fractuhahq: Fixed-point fractional library routines. ! (line 793) * __fractuhaqi: Fixed-point fractional library routines. ! (line 816) * __fractuhaqq: Fixed-point fractional library routines. ! (line 792) * __fractuhasa: Fixed-point fractional library routines. ! (line 798) * __fractuhasf: Fixed-point fractional library routines. ! (line 821) * __fractuhasi: Fixed-point fractional library routines. ! (line 818) * __fractuhasq: Fixed-point fractional library routines. ! (line 794) * __fractuhata: Fixed-point fractional library routines. ! (line 801) * __fractuhati: Fixed-point fractional library routines. ! (line 820) * __fractuhauda2: Fixed-point fractional library routines. ! (line 813) * __fractuhaudq: Fixed-point fractional library routines. ! (line 809) * __fractuhauhq: Fixed-point fractional library routines. ! (line 805) * __fractuhauqq: Fixed-point fractional library routines. ! (line 803) * __fractuhausa2: Fixed-point fractional library routines. ! (line 811) * __fractuhausq: Fixed-point fractional library routines. ! (line 807) * __fractuhauta2: Fixed-point fractional library routines. ! (line 815) * __fractuhqda: Fixed-point fractional library routines. ! (line 702) * __fractuhqdf: Fixed-point fractional library routines. ! (line 723) * __fractuhqdi: Fixed-point fractional library routines. ! (line 720) * __fractuhqdq: Fixed-point fractional library routines. ! (line 699) * __fractuhqha: Fixed-point fractional library routines. ! (line 700) * __fractuhqhi: Fixed-point fractional library routines. ! (line 718) * __fractuhqhq: Fixed-point fractional library routines. ! (line 697) * __fractuhqqi: Fixed-point fractional library routines. ! (line 717) * __fractuhqqq: Fixed-point fractional library routines. ! (line 696) * __fractuhqsa: Fixed-point fractional library routines. ! (line 701) * __fractuhqsf: Fixed-point fractional library routines. ! (line 722) * __fractuhqsi: Fixed-point fractional library routines. ! (line 719) * __fractuhqsq: Fixed-point fractional library routines. ! (line 698) * __fractuhqta: Fixed-point fractional library routines. ! (line 703) * __fractuhqti: Fixed-point fractional library routines. ! (line 721) * __fractuhquda: Fixed-point fractional library routines. ! (line 714) * __fractuhqudq2: Fixed-point fractional library routines. ! (line 709) * __fractuhquha: Fixed-point fractional library routines. (line 711) + * __fractuhquqq2: Fixed-point fractional library routines. + (line 705) * __fractuhqusa: Fixed-point fractional library routines. ! (line 712) * __fractuhqusq2: Fixed-point fractional library routines. ! (line 707) * __fractuhquta: Fixed-point fractional library routines. ! (line 716) * __fractunsdadi: Fixed-point fractional library routines. ! (line 1555) * __fractunsdahi: Fixed-point fractional library routines. ! (line 1553) * __fractunsdaqi: Fixed-point fractional library routines. ! (line 1552) * __fractunsdasi: Fixed-point fractional library routines. ! (line 1554) * __fractunsdati: Fixed-point fractional library routines. ! (line 1556) * __fractunsdida: Fixed-point fractional library routines. ! (line 1707) * __fractunsdidq: Fixed-point fractional library routines. ! (line 1704) * __fractunsdiha: Fixed-point fractional library routines. ! (line 1705) * __fractunsdihq: Fixed-point fractional library routines. ! (line 1702) * __fractunsdiqq: Fixed-point fractional library routines. ! (line 1701) * __fractunsdisa: Fixed-point fractional library routines. ! (line 1706) * __fractunsdisq: Fixed-point fractional library routines. ! (line 1703) * __fractunsdita: Fixed-point fractional library routines. ! (line 1708) * __fractunsdiuda: Fixed-point fractional library routines. ! (line 1720) * __fractunsdiudq: Fixed-point fractional library routines. ! (line 1715) * __fractunsdiuha: Fixed-point fractional library routines. ! (line 1717) * __fractunsdiuhq: Fixed-point fractional library routines. ! (line 1711) * __fractunsdiuqq: Fixed-point fractional library routines. ! (line 1710) * __fractunsdiusa: Fixed-point fractional library routines. ! (line 1718) * __fractunsdiusq: Fixed-point fractional library routines. ! (line 1713) * __fractunsdiuta: Fixed-point fractional library routines. ! (line 1722) * __fractunsdqdi: Fixed-point fractional library routines. ! (line 1539) * __fractunsdqhi: Fixed-point fractional library routines. ! (line 1537) * __fractunsdqqi: Fixed-point fractional library routines. ! (line 1536) * __fractunsdqsi: Fixed-point fractional library routines. ! (line 1538) * __fractunsdqti: Fixed-point fractional library routines. ! (line 1541) * __fractunshadi: Fixed-point fractional library routines. ! (line 1545) * __fractunshahi: Fixed-point fractional library routines. ! (line 1543) * __fractunshaqi: Fixed-point fractional library routines. ! (line 1542) * __fractunshasi: Fixed-point fractional library routines. ! (line 1544) * __fractunshati: Fixed-point fractional library routines. ! (line 1546) * __fractunshida: Fixed-point fractional library routines. ! (line 1663) * __fractunshidq: Fixed-point fractional library routines. ! (line 1660) * __fractunshiha: Fixed-point fractional library routines. ! (line 1661) * __fractunshihq: Fixed-point fractional library routines. ! (line 1658) * __fractunshiqq: Fixed-point fractional library routines. ! (line 1657) * __fractunshisa: Fixed-point fractional library routines. ! (line 1662) * __fractunshisq: Fixed-point fractional library routines. ! (line 1659) * __fractunshita: Fixed-point fractional library routines. ! (line 1664) * __fractunshiuda: Fixed-point fractional library routines. ! (line 1676) * __fractunshiudq: Fixed-point fractional library routines. ! (line 1671) * __fractunshiuha: Fixed-point fractional library routines. ! (line 1673) * __fractunshiuhq: Fixed-point fractional library routines. ! (line 1667) * __fractunshiuqq: Fixed-point fractional library routines. ! (line 1666) * __fractunshiusa: Fixed-point fractional library routines. ! (line 1674) * __fractunshiusq: Fixed-point fractional library routines. ! (line 1669) * __fractunshiuta: Fixed-point fractional library routines. ! (line 1678) * __fractunshqdi: Fixed-point fractional library routines. ! (line 1529) * __fractunshqhi: Fixed-point fractional library routines. ! (line 1527) * __fractunshqqi: Fixed-point fractional library routines. ! (line 1526) * __fractunshqsi: Fixed-point fractional library routines. ! (line 1528) * __fractunshqti: Fixed-point fractional library routines. ! (line 1530) * __fractunsqida: Fixed-point fractional library routines. ! (line 1641) * __fractunsqidq: Fixed-point fractional library routines. ! (line 1638) * __fractunsqiha: Fixed-point fractional library routines. ! (line 1639) * __fractunsqihq: Fixed-point fractional library routines. ! (line 1636) * __fractunsqiqq: Fixed-point fractional library routines. ! (line 1635) * __fractunsqisa: Fixed-point fractional library routines. ! (line 1640) * __fractunsqisq: Fixed-point fractional library routines. ! (line 1637) * __fractunsqita: Fixed-point fractional library routines. ! (line 1642) * __fractunsqiuda: Fixed-point fractional library routines. ! (line 1654) * __fractunsqiudq: Fixed-point fractional library routines. ! (line 1649) * __fractunsqiuha: Fixed-point fractional library routines. ! (line 1651) * __fractunsqiuhq: Fixed-point fractional library routines. ! (line 1645) * __fractunsqiuqq: Fixed-point fractional library routines. ! (line 1644) * __fractunsqiusa: Fixed-point fractional library routines. ! (line 1652) * __fractunsqiusq: Fixed-point fractional library routines. ! (line 1647) * __fractunsqiuta: Fixed-point fractional library routines. ! (line 1656) * __fractunsqqdi: Fixed-point fractional library routines. ! (line 1524) * __fractunsqqhi: Fixed-point fractional library routines. ! (line 1522) * __fractunsqqqi: Fixed-point fractional library routines. ! (line 1521) * __fractunsqqsi: Fixed-point fractional library routines. ! (line 1523) * __fractunsqqti: Fixed-point fractional library routines. ! (line 1525) * __fractunssadi: Fixed-point fractional library routines. ! (line 1550) * __fractunssahi: Fixed-point fractional library routines. ! (line 1548) * __fractunssaqi: Fixed-point fractional library routines. ! (line 1547) * __fractunssasi: Fixed-point fractional library routines. ! (line 1549) * __fractunssati: Fixed-point fractional library routines. ! (line 1551) * __fractunssida: Fixed-point fractional library routines. ! (line 1685) * __fractunssidq: Fixed-point fractional library routines. ! (line 1682) * __fractunssiha: Fixed-point fractional library routines. ! (line 1683) * __fractunssihq: Fixed-point fractional library routines. ! (line 1680) * __fractunssiqq: Fixed-point fractional library routines. ! (line 1679) * __fractunssisa: Fixed-point fractional library routines. ! (line 1684) * __fractunssisq: Fixed-point fractional library routines. ! (line 1681) * __fractunssita: Fixed-point fractional library routines. ! (line 1686) * __fractunssiuda: Fixed-point fractional library routines. ! (line 1698) * __fractunssiudq: Fixed-point fractional library routines. ! (line 1693) * __fractunssiuha: Fixed-point fractional library routines. ! (line 1695) * __fractunssiuhq: Fixed-point fractional library routines. ! (line 1689) * __fractunssiuqq: Fixed-point fractional library routines. ! (line 1688) * __fractunssiusa: Fixed-point fractional library routines. ! (line 1696) * __fractunssiusq: Fixed-point fractional library routines. ! (line 1691) * __fractunssiuta: Fixed-point fractional library routines. ! (line 1700) * __fractunssqdi: Fixed-point fractional library routines. ! (line 1534) * __fractunssqhi: Fixed-point fractional library routines. ! (line 1532) * __fractunssqqi: Fixed-point fractional library routines. ! (line 1531) * __fractunssqsi: Fixed-point fractional library routines. ! (line 1533) * __fractunssqti: Fixed-point fractional library routines. ! (line 1535) * __fractunstadi: Fixed-point fractional library routines. ! (line 1560) * __fractunstahi: Fixed-point fractional library routines. ! (line 1558) * __fractunstaqi: Fixed-point fractional library routines. ! (line 1557) * __fractunstasi: Fixed-point fractional library routines. ! (line 1559) * __fractunstati: Fixed-point fractional library routines. ! (line 1562) * __fractunstida: Fixed-point fractional library routines. ! (line 1730) * __fractunstidq: Fixed-point fractional library routines. ! (line 1727) * __fractunstiha: Fixed-point fractional library routines. ! (line 1728) * __fractunstihq: Fixed-point fractional library routines. ! (line 1724) * __fractunstiqq: Fixed-point fractional library routines. ! (line 1723) * __fractunstisa: Fixed-point fractional library routines. ! (line 1729) * __fractunstisq: Fixed-point fractional library routines. ! (line 1725) * __fractunstita: Fixed-point fractional library routines. ! (line 1732) * __fractunstiuda: Fixed-point fractional library routines. (line 1746) + * __fractunstiudq: Fixed-point fractional library routines. + (line 1740) * __fractunstiuha: Fixed-point fractional library routines. (line 1742) + * __fractunstiuhq: Fixed-point fractional library routines. + (line 1736) * __fractunstiuqq: Fixed-point fractional library routines. ! (line 1734) * __fractunstiusa: Fixed-point fractional library routines. (line 1744) + * __fractunstiusq: Fixed-point fractional library routines. + (line 1738) * __fractunstiuta: Fixed-point fractional library routines. ! (line 1748) * __fractunsudadi: Fixed-point fractional library routines. ! (line 1622) * __fractunsudahi: Fixed-point fractional library routines. ! (line 1618) * __fractunsudaqi: Fixed-point fractional library routines. ! (line 1616) * __fractunsudasi: Fixed-point fractional library routines. ! (line 1620) * __fractunsudati: Fixed-point fractional library routines. ! (line 1624) * __fractunsudqdi: Fixed-point fractional library routines. ! (line 1596) * __fractunsudqhi: Fixed-point fractional library routines. ! (line 1592) * __fractunsudqqi: Fixed-point fractional library routines. ! (line 1590) * __fractunsudqsi: Fixed-point fractional library routines. ! (line 1594) * __fractunsudqti: Fixed-point fractional library routines. ! (line 1598) * __fractunsuhadi: Fixed-point fractional library routines. ! (line 1606) * __fractunsuhahi: Fixed-point fractional library routines. ! (line 1602) * __fractunsuhaqi: Fixed-point fractional library routines. ! (line 1600) * __fractunsuhasi: Fixed-point fractional library routines. ! (line 1604) * __fractunsuhati: Fixed-point fractional library routines. ! (line 1608) * __fractunsuhqdi: Fixed-point fractional library routines. ! (line 1576) * __fractunsuhqhi: Fixed-point fractional library routines. ! (line 1574) * __fractunsuhqqi: Fixed-point fractional library routines. ! (line 1573) * __fractunsuhqsi: Fixed-point fractional library routines. ! (line 1575) * __fractunsuhqti: Fixed-point fractional library routines. ! (line 1578) * __fractunsuqqdi: Fixed-point fractional library routines. ! (line 1570) * __fractunsuqqhi: Fixed-point fractional library routines. ! (line 1566) * __fractunsuqqqi: Fixed-point fractional library routines. ! (line 1564) * __fractunsuqqsi: Fixed-point fractional library routines. ! (line 1568) * __fractunsuqqti: Fixed-point fractional library routines. ! (line 1572) * __fractunsusadi: Fixed-point fractional library routines. ! (line 1612) * __fractunsusahi: Fixed-point fractional library routines. ! (line 1610) * __fractunsusaqi: Fixed-point fractional library routines. ! (line 1609) * __fractunsusasi: Fixed-point fractional library routines. ! (line 1611) * __fractunsusati: Fixed-point fractional library routines. ! (line 1614) * __fractunsusqdi: Fixed-point fractional library routines. ! (line 1586) * __fractunsusqhi: Fixed-point fractional library routines. ! (line 1582) * __fractunsusqqi: Fixed-point fractional library routines. ! (line 1580) * __fractunsusqsi: Fixed-point fractional library routines. ! (line 1584) * __fractunsusqti: Fixed-point fractional library routines. ! (line 1588) * __fractunsutadi: Fixed-point fractional library routines. ! (line 1632) * __fractunsutahi: Fixed-point fractional library routines. ! (line 1628) * __fractunsutaqi: Fixed-point fractional library routines. ! (line 1626) * __fractunsutasi: Fixed-point fractional library routines. ! (line 1630) * __fractunsutati: Fixed-point fractional library routines. ! (line 1634) * __fractuqqda: Fixed-point fractional library routines. ! (line 672) * __fractuqqdf: Fixed-point fractional library routines. ! (line 695) * __fractuqqdi: Fixed-point fractional library routines. ! (line 692) * __fractuqqdq: Fixed-point fractional library routines. ! (line 669) * __fractuqqha: Fixed-point fractional library routines. ! (line 670) * __fractuqqhi: Fixed-point fractional library routines. ! (line 690) * __fractuqqhq: Fixed-point fractional library routines. ! (line 666) * __fractuqqqi: Fixed-point fractional library routines. ! (line 689) * __fractuqqqq: Fixed-point fractional library routines. ! (line 665) * __fractuqqsa: Fixed-point fractional library routines. ! (line 671) * __fractuqqsf: Fixed-point fractional library routines. ! (line 694) * __fractuqqsi: Fixed-point fractional library routines. ! (line 691) * __fractuqqsq: Fixed-point fractional library routines. ! (line 667) * __fractuqqta: Fixed-point fractional library routines. ! (line 674) * __fractuqqti: Fixed-point fractional library routines. ! (line 693) * __fractuqquda: Fixed-point fractional library routines. (line 686) + * __fractuqqudq2: Fixed-point fractional library routines. + (line 680) * __fractuqquha: Fixed-point fractional library routines. (line 682) + * __fractuqquhq2: Fixed-point fractional library routines. + (line 676) * __fractuqqusa: Fixed-point fractional library routines. (line 684) + * __fractuqqusq2: Fixed-point fractional library routines. + (line 678) * __fractuqquta: Fixed-point fractional library routines. ! (line 688) * __fractusada: Fixed-point fractional library routines. ! (line 829) * __fractusadf: Fixed-point fractional library routines. ! (line 850) * __fractusadi: Fixed-point fractional library routines. ! (line 847) * __fractusadq: Fixed-point fractional library routines. ! (line 826) * __fractusaha: Fixed-point fractional library routines. ! (line 827) * __fractusahi: Fixed-point fractional library routines. ! (line 845) * __fractusahq: Fixed-point fractional library routines. ! (line 824) * __fractusaqi: Fixed-point fractional library routines. ! (line 844) * __fractusaqq: Fixed-point fractional library routines. ! (line 823) * __fractusasa: Fixed-point fractional library routines. ! (line 828) * __fractusasf: Fixed-point fractional library routines. ! (line 849) * __fractusasi: Fixed-point fractional library routines. ! (line 846) * __fractusasq: Fixed-point fractional library routines. ! (line 825) * __fractusata: Fixed-point fractional library routines. ! (line 830) * __fractusati: Fixed-point fractional library routines. ! (line 848) * __fractusauda2: Fixed-point fractional library routines. ! (line 841) * __fractusaudq: Fixed-point fractional library routines. ! (line 837) * __fractusauha2: Fixed-point fractional library routines. ! (line 839) * __fractusauhq: Fixed-point fractional library routines. ! (line 833) * __fractusauqq: Fixed-point fractional library routines. ! (line 832) * __fractusausq: Fixed-point fractional library routines. ! (line 835) * __fractusauta2: Fixed-point fractional library routines. ! (line 843) * __fractusqda: Fixed-point fractional library routines. ! (line 731) * __fractusqdf: Fixed-point fractional library routines. ! (line 754) * __fractusqdi: Fixed-point fractional library routines. ! (line 751) * __fractusqdq: Fixed-point fractional library routines. ! (line 728) * __fractusqha: Fixed-point fractional library routines. ! (line 729) * __fractusqhi: Fixed-point fractional library routines. ! (line 749) * __fractusqhq: Fixed-point fractional library routines. ! (line 725) * __fractusqqi: Fixed-point fractional library routines. ! (line 748) * __fractusqqq: Fixed-point fractional library routines. ! (line 724) * __fractusqsa: Fixed-point fractional library routines. ! (line 730) * __fractusqsf: Fixed-point fractional library routines. ! (line 753) * __fractusqsi: Fixed-point fractional library routines. ! (line 750) * __fractusqsq: Fixed-point fractional library routines. ! (line 726) * __fractusqta: Fixed-point fractional library routines. ! (line 733) * __fractusqti: Fixed-point fractional library routines. ! (line 752) * __fractusquda: Fixed-point fractional library routines. (line 745) + * __fractusqudq2: Fixed-point fractional library routines. + (line 739) * __fractusquha: Fixed-point fractional library routines. ! (line 741) * __fractusquhq2: Fixed-point fractional library routines. ! (line 737) * __fractusquqq2: Fixed-point fractional library routines. ! (line 735) * __fractusqusa: Fixed-point fractional library routines. ! (line 743) * __fractusquta: Fixed-point fractional library routines. ! (line 747) * __fractutada: Fixed-point fractional library routines. ! (line 893) * __fractutadf: Fixed-point fractional library routines. ! (line 918) * __fractutadi: Fixed-point fractional library routines. ! (line 914) * __fractutadq: Fixed-point fractional library routines. ! (line 888) * __fractutaha: Fixed-point fractional library routines. ! (line 890) * __fractutahi: Fixed-point fractional library routines. ! (line 912) * __fractutahq: Fixed-point fractional library routines. ! (line 884) * __fractutaqi: Fixed-point fractional library routines. ! (line 911) * __fractutaqq: Fixed-point fractional library routines. ! (line 883) * __fractutasa: Fixed-point fractional library routines. ! (line 891) * __fractutasf: Fixed-point fractional library routines. ! (line 917) * __fractutasi: Fixed-point fractional library routines. ! (line 913) * __fractutasq: Fixed-point fractional library routines. ! (line 886) * __fractutata: Fixed-point fractional library routines. ! (line 895) * __fractutati: Fixed-point fractional library routines. ! (line 916) * __fractutauda2: Fixed-point fractional library routines. (line 909) + * __fractutaudq: Fixed-point fractional library routines. + (line 903) * __fractutauha2: Fixed-point fractional library routines. (line 905) + * __fractutauhq: Fixed-point fractional library routines. + (line 899) * __fractutauqq: Fixed-point fractional library routines. ! (line 897) * __fractutausa2: Fixed-point fractional library routines. (line 907) + * __fractutausq: Fixed-point fractional library routines. + (line 901) * __gedf2: Soft float library routines. ! (line 206) * __gesf2: Soft float library routines. ! (line 205) * __getf2: Soft float library routines. ! (line 207) * __gtdf2: Soft float library routines. ! (line 224) * __gtsf2: Soft float library routines. ! (line 223) * __gttf2: Soft float library routines. ! (line 225) * __ledf2: Soft float library routines. ! (line 218) * __lesf2: Soft float library routines. ! (line 217) * __letf2: Soft float library routines. ! (line 219) * __lshrdi3: Integer library routines. ! (line 31) * __lshrsi3: Integer library routines. ! (line 30) * __lshrti3: Integer library routines. ! (line 32) * __lshruda3: Fixed-point fractional library routines. (line 390) + * __lshrudq3: Fixed-point fractional library routines. + (line 384) * __lshruha3: Fixed-point fractional library routines. (line 386) + * __lshruhq3: Fixed-point fractional library routines. + (line 380) * __lshruqq3: Fixed-point fractional library routines. ! (line 378) * __lshrusa3: Fixed-point fractional library routines. (line 388) + * __lshrusq3: Fixed-point fractional library routines. + (line 382) * __lshruta3: Fixed-point fractional library routines. ! (line 392) * __ltdf2: Soft float library routines. ! (line 212) * __ltsf2: Soft float library routines. ! (line 211) * __lttf2: Soft float library routines. ! (line 213) * __main: Collect2. (line 15) * __moddi3: Integer library routines. ! (line 37) * __modsi3: Integer library routines. ! (line 36) * __modti3: Integer library routines. ! (line 38) * __morestack_current_segment: Miscellaneous routines. (line 46) + * __morestack_initial_sp: Miscellaneous routines. + (line 47) * __morestack_segments: Miscellaneous routines. ! (line 45) * __mulda3: Fixed-point fractional library routines. ! (line 171) * __muldc3: Soft float library routines. ! (line 241) * __muldf3: Soft float library routines. ! (line 40) * __muldi3: Integer library routines. ! (line 43) * __muldq3: Fixed-point fractional library routines. ! (line 159) * __mulha3: Fixed-point fractional library routines. ! (line 169) * __mulhq3: Fixed-point fractional library routines. ! (line 156) * __mulqq3: Fixed-point fractional library routines. ! (line 155) * __mulsa3: Fixed-point fractional library routines. ! (line 170) * __mulsc3: Soft float library routines. ! (line 239) * __mulsf3: Soft float library routines. ! (line 39) * __mulsi3: Integer library routines. ! (line 42) * __mulsq3: Fixed-point fractional library routines. ! (line 157) * __multa3: Fixed-point fractional library routines. ! (line 173) * __multc3: Soft float library routines. ! (line 243) * __multf3: Soft float library routines. ! (line 42) * __multi3: Integer library routines. ! (line 44) * __muluda3: Fixed-point fractional library routines. ! (line 179) * __muludq3: Fixed-point fractional library routines. ! (line 167) * __muluha3: Fixed-point fractional library routines. ! (line 175) * __muluhq3: Fixed-point fractional library routines. ! (line 163) * __muluqq3: Fixed-point fractional library routines. ! (line 161) * __mulusa3: Fixed-point fractional library routines. ! (line 177) * __mulusq3: Fixed-point fractional library routines. ! (line 165) * __muluta3: Fixed-point fractional library routines. ! (line 181) * __mulvdi3: Integer library routines. ! (line 115) * __mulvsi3: Integer library routines. ! (line 114) * __mulxc3: Soft float library routines. ! (line 245) * __mulxf3: Soft float library routines. ! (line 44) * __nedf2: Soft float library routines. ! (line 200) * __negda2: Fixed-point fractional library routines. ! (line 299) * __negdf2: Soft float library routines. ! (line 56) * __negdi2: Integer library routines. ! (line 47) * __negdq2: Fixed-point fractional library routines. ! (line 289) * __negha2: Fixed-point fractional library routines. ! (line 297) * __neghq2: Fixed-point fractional library routines. ! (line 287) * __negqq2: Fixed-point fractional library routines. ! (line 286) * __negsa2: Fixed-point fractional library routines. ! (line 298) * __negsf2: Soft float library routines. ! (line 55) * __negsq2: Fixed-point fractional library routines. ! (line 288) * __negta2: Fixed-point fractional library routines. ! (line 300) * __negtf2: Soft float library routines. ! (line 57) * __negti2: Integer library routines. ! (line 48) * __neguda2: Fixed-point fractional library routines. ! (line 305) * __negudq2: Fixed-point fractional library routines. ! (line 296) * __neguha2: Fixed-point fractional library routines. ! (line 302) * __neguhq2: Fixed-point fractional library routines. ! (line 292) * __neguqq2: Fixed-point fractional library routines. ! (line 291) * __negusa2: Fixed-point fractional library routines. ! (line 303) * __negusq2: Fixed-point fractional library routines. ! (line 294) * __neguta2: Fixed-point fractional library routines. ! (line 307) * __negvdi2: Integer library routines. ! (line 119) * __negvsi2: Integer library routines. ! (line 118) * __negxf2: Soft float library routines. ! (line 58) * __nesf2: Soft float library routines. ! (line 199) * __netf2: Soft float library routines. ! (line 201) * __paritydi2: Integer library routines. ! (line 151) * __paritysi2: Integer library routines. ! (line 150) * __parityti2: Integer library routines. ! (line 152) * __popcountdi2: Integer library routines. ! (line 157) * __popcountsi2: Integer library routines. ! (line 156) * __popcountti2: Integer library routines. ! (line 158) * __powidf2: Soft float library routines. ! (line 233) * __powisf2: Soft float library routines. ! (line 232) * __powitf2: Soft float library routines. (line 234) + * __powixf2: Soft float library routines. + (line 235) * __satfractdadq: Fixed-point fractional library routines. ! (line 1153) * __satfractdaha2: Fixed-point fractional library routines. ! (line 1154) * __satfractdahq: Fixed-point fractional library routines. ! (line 1151) * __satfractdaqq: Fixed-point fractional library routines. ! (line 1150) * __satfractdasa2: Fixed-point fractional library routines. ! (line 1155) * __satfractdasq: Fixed-point fractional library routines. ! (line 1152) * __satfractdata2: Fixed-point fractional library routines. ! (line 1156) * __satfractdauda: Fixed-point fractional library routines. ! (line 1166) * __satfractdaudq: Fixed-point fractional library routines. ! (line 1162) * __satfractdauha: Fixed-point fractional library routines. ! (line 1164) * __satfractdauhq: Fixed-point fractional library routines. ! (line 1159) * __satfractdauqq: Fixed-point fractional library routines. ! (line 1158) * __satfractdausa: Fixed-point fractional library routines. ! (line 1165) * __satfractdausq: Fixed-point fractional library routines. ! (line 1160) * __satfractdauta: Fixed-point fractional library routines. ! (line 1168) * __satfractdfda: Fixed-point fractional library routines. ! (line 1506) * __satfractdfdq: Fixed-point fractional library routines. ! (line 1503) * __satfractdfha: Fixed-point fractional library routines. ! (line 1504) * __satfractdfhq: Fixed-point fractional library routines. ! (line 1501) * __satfractdfqq: Fixed-point fractional library routines. ! (line 1500) * __satfractdfsa: Fixed-point fractional library routines. ! (line 1505) * __satfractdfsq: Fixed-point fractional library routines. ! (line 1502) * __satfractdfta: Fixed-point fractional library routines. ! (line 1507) * __satfractdfuda: Fixed-point fractional library routines. ! (line 1515) * __satfractdfudq: Fixed-point fractional library routines. ! (line 1512) * __satfractdfuha: Fixed-point fractional library routines. ! (line 1513) * __satfractdfuhq: Fixed-point fractional library routines. ! (line 1509) * __satfractdfuqq: Fixed-point fractional library routines. ! (line 1508) * __satfractdfusa: Fixed-point fractional library routines. ! (line 1514) * __satfractdfusq: Fixed-point fractional library routines. ! (line 1510) * __satfractdfuta: Fixed-point fractional library routines. ! (line 1517) * __satfractdida: Fixed-point fractional library routines. ! (line 1456) * __satfractdidq: Fixed-point fractional library routines. ! (line 1453) * __satfractdiha: Fixed-point fractional library routines. ! (line 1454) * __satfractdihq: Fixed-point fractional library routines. ! (line 1451) * __satfractdiqq: Fixed-point fractional library routines. ! (line 1450) * __satfractdisa: Fixed-point fractional library routines. ! (line 1455) * __satfractdisq: Fixed-point fractional library routines. ! (line 1452) * __satfractdita: Fixed-point fractional library routines. ! (line 1457) * __satfractdiuda: Fixed-point fractional library routines. ! (line 1464) * __satfractdiudq: Fixed-point fractional library routines. ! (line 1461) * __satfractdiuha: Fixed-point fractional library routines. ! (line 1462) * __satfractdiuhq: Fixed-point fractional library routines. ! (line 1459) * __satfractdiuqq: Fixed-point fractional library routines. ! (line 1458) * __satfractdiusa: Fixed-point fractional library routines. ! (line 1463) * __satfractdiusq: Fixed-point fractional library routines. ! (line 1460) * __satfractdiuta: Fixed-point fractional library routines. ! (line 1465) * __satfractdqda: Fixed-point fractional library routines. ! (line 1098) * __satfractdqha: Fixed-point fractional library routines. ! (line 1096) * __satfractdqhq2: Fixed-point fractional library routines. ! (line 1094) * __satfractdqqq2: Fixed-point fractional library routines. ! (line 1093) * __satfractdqsa: Fixed-point fractional library routines. ! (line 1097) * __satfractdqsq2: Fixed-point fractional library routines. ! (line 1095) * __satfractdqta: Fixed-point fractional library routines. ! (line 1099) * __satfractdquda: Fixed-point fractional library routines. ! (line 1111) * __satfractdqudq: Fixed-point fractional library routines. ! (line 1106) * __satfractdquha: Fixed-point fractional library routines. ! (line 1108) * __satfractdquhq: Fixed-point fractional library routines. ! (line 1102) * __satfractdquqq: Fixed-point fractional library routines. ! (line 1101) * __satfractdqusa: Fixed-point fractional library routines. ! (line 1109) * __satfractdqusq: Fixed-point fractional library routines. ! (line 1104) * __satfractdquta: Fixed-point fractional library routines. ! (line 1113) * __satfracthada2: Fixed-point fractional library routines. ! (line 1119) * __satfracthadq: Fixed-point fractional library routines. ! (line 1117) * __satfracthahq: Fixed-point fractional library routines. ! (line 1115) * __satfracthaqq: Fixed-point fractional library routines. ! (line 1114) * __satfracthasa2: Fixed-point fractional library routines. ! (line 1118) * __satfracthasq: Fixed-point fractional library routines. ! (line 1116) * __satfracthata2: Fixed-point fractional library routines. ! (line 1120) * __satfracthauda: Fixed-point fractional library routines. ! (line 1132) * __satfracthaudq: Fixed-point fractional library routines. ! (line 1127) * __satfracthauha: Fixed-point fractional library routines. ! (line 1129) * __satfracthauhq: Fixed-point fractional library routines. ! (line 1123) * __satfracthauqq: Fixed-point fractional library routines. ! (line 1122) * __satfracthausa: Fixed-point fractional library routines. ! (line 1130) * __satfracthausq: Fixed-point fractional library routines. ! (line 1125) * __satfracthauta: Fixed-point fractional library routines. ! (line 1134) * __satfracthida: Fixed-point fractional library routines. ! (line 1424) * __satfracthidq: Fixed-point fractional library routines. ! (line 1421) * __satfracthiha: Fixed-point fractional library routines. ! (line 1422) * __satfracthihq: Fixed-point fractional library routines. ! (line 1419) * __satfracthiqq: Fixed-point fractional library routines. ! (line 1418) * __satfracthisa: Fixed-point fractional library routines. ! (line 1423) * __satfracthisq: Fixed-point fractional library routines. ! (line 1420) * __satfracthita: Fixed-point fractional library routines. ! (line 1425) * __satfracthiuda: Fixed-point fractional library routines. ! (line 1432) * __satfracthiudq: Fixed-point fractional library routines. ! (line 1429) * __satfracthiuha: Fixed-point fractional library routines. ! (line 1430) * __satfracthiuhq: Fixed-point fractional library routines. ! (line 1427) * __satfracthiuqq: Fixed-point fractional library routines. ! (line 1426) * __satfracthiusa: Fixed-point fractional library routines. ! (line 1431) * __satfracthiusq: Fixed-point fractional library routines. ! (line 1428) * __satfracthiuta: Fixed-point fractional library routines. ! (line 1433) * __satfracthqda: Fixed-point fractional library routines. ! (line 1064) * __satfracthqdq2: Fixed-point fractional library routines. ! (line 1061) * __satfracthqha: Fixed-point fractional library routines. ! (line 1062) * __satfracthqqq2: Fixed-point fractional library routines. ! (line 1059) * __satfracthqsa: Fixed-point fractional library routines. ! (line 1063) * __satfracthqsq2: Fixed-point fractional library routines. ! (line 1060) * __satfracthqta: Fixed-point fractional library routines. ! (line 1065) * __satfracthquda: Fixed-point fractional library routines. ! (line 1072) * __satfracthqudq: Fixed-point fractional library routines. ! (line 1069) * __satfracthquha: Fixed-point fractional library routines. ! (line 1070) * __satfracthquhq: Fixed-point fractional library routines. ! (line 1067) * __satfracthquqq: Fixed-point fractional library routines. ! (line 1066) * __satfracthqusa: Fixed-point fractional library routines. ! (line 1071) * __satfracthqusq: Fixed-point fractional library routines. ! (line 1068) * __satfracthquta: Fixed-point fractional library routines. ! (line 1073) * __satfractqida: Fixed-point fractional library routines. ! (line 1402) * __satfractqidq: Fixed-point fractional library routines. ! (line 1399) * __satfractqiha: Fixed-point fractional library routines. ! (line 1400) * __satfractqihq: Fixed-point fractional library routines. ! (line 1397) * __satfractqiqq: Fixed-point fractional library routines. ! (line 1396) * __satfractqisa: Fixed-point fractional library routines. ! (line 1401) * __satfractqisq: Fixed-point fractional library routines. ! (line 1398) * __satfractqita: Fixed-point fractional library routines. ! (line 1403) * __satfractqiuda: Fixed-point fractional library routines. ! (line 1415) * __satfractqiudq: Fixed-point fractional library routines. ! (line 1410) * __satfractqiuha: Fixed-point fractional library routines. ! (line 1412) * __satfractqiuhq: Fixed-point fractional library routines. ! (line 1406) * __satfractqiuqq: Fixed-point fractional library routines. ! (line 1405) * __satfractqiusa: Fixed-point fractional library routines. ! (line 1413) * __satfractqiusq: Fixed-point fractional library routines. ! (line 1408) * __satfractqiuta: Fixed-point fractional library routines. ! (line 1417) * __satfractqqda: Fixed-point fractional library routines. ! (line 1043) * __satfractqqdq2: Fixed-point fractional library routines. ! (line 1040) * __satfractqqha: Fixed-point fractional library routines. ! (line 1041) * __satfractqqhq2: Fixed-point fractional library routines. ! (line 1038) * __satfractqqsa: Fixed-point fractional library routines. ! (line 1042) * __satfractqqsq2: Fixed-point fractional library routines. ! (line 1039) * __satfractqqta: Fixed-point fractional library routines. ! (line 1044) * __satfractqquda: Fixed-point fractional library routines. ! (line 1056) * __satfractqqudq: Fixed-point fractional library routines. ! (line 1051) * __satfractqquha: Fixed-point fractional library routines. ! (line 1053) * __satfractqquhq: Fixed-point fractional library routines. ! (line 1047) * __satfractqquqq: Fixed-point fractional library routines. ! (line 1046) * __satfractqqusa: Fixed-point fractional library routines. ! (line 1054) * __satfractqqusq: Fixed-point fractional library routines. ! (line 1049) * __satfractqquta: Fixed-point fractional library routines. ! (line 1058) * __satfractsada2: Fixed-point fractional library routines. ! (line 1140) * __satfractsadq: Fixed-point fractional library routines. ! (line 1138) * __satfractsaha2: Fixed-point fractional library routines. ! (line 1139) * __satfractsahq: Fixed-point fractional library routines. ! (line 1136) * __satfractsaqq: Fixed-point fractional library routines. ! (line 1135) * __satfractsasq: Fixed-point fractional library routines. ! (line 1137) * __satfractsata2: Fixed-point fractional library routines. ! (line 1141) * __satfractsauda: Fixed-point fractional library routines. ! (line 1148) * __satfractsaudq: Fixed-point fractional library routines. ! (line 1145) * __satfractsauha: Fixed-point fractional library routines. ! (line 1146) * __satfractsauhq: Fixed-point fractional library routines. ! (line 1143) * __satfractsauqq: Fixed-point fractional library routines. ! (line 1142) * __satfractsausa: Fixed-point fractional library routines. ! (line 1147) * __satfractsausq: Fixed-point fractional library routines. ! (line 1144) * __satfractsauta: Fixed-point fractional library routines. ! (line 1149) * __satfractsfda: Fixed-point fractional library routines. ! (line 1490) * __satfractsfdq: Fixed-point fractional library routines. ! (line 1487) * __satfractsfha: Fixed-point fractional library routines. ! (line 1488) * __satfractsfhq: Fixed-point fractional library routines. ! (line 1485) * __satfractsfqq: Fixed-point fractional library routines. ! (line 1484) * __satfractsfsa: Fixed-point fractional library routines. ! (line 1489) * __satfractsfsq: Fixed-point fractional library routines. ! (line 1486) * __satfractsfta: Fixed-point fractional library routines. ! (line 1491) * __satfractsfuda: Fixed-point fractional library routines. ! (line 1498) * __satfractsfudq: Fixed-point fractional library routines. ! (line 1495) * __satfractsfuha: Fixed-point fractional library routines. ! (line 1496) * __satfractsfuhq: Fixed-point fractional library routines. ! (line 1493) * __satfractsfuqq: Fixed-point fractional library routines. ! (line 1492) * __satfractsfusa: Fixed-point fractional library routines. ! (line 1497) * __satfractsfusq: Fixed-point fractional library routines. ! (line 1494) * __satfractsfuta: Fixed-point fractional library routines. ! (line 1499) * __satfractsida: Fixed-point fractional library routines. ! (line 1440) * __satfractsidq: Fixed-point fractional library routines. ! (line 1437) * __satfractsiha: Fixed-point fractional library routines. ! (line 1438) * __satfractsihq: Fixed-point fractional library routines. ! (line 1435) * __satfractsiqq: Fixed-point fractional library routines. ! (line 1434) * __satfractsisa: Fixed-point fractional library routines. ! (line 1439) * __satfractsisq: Fixed-point fractional library routines. ! (line 1436) * __satfractsita: Fixed-point fractional library routines. ! (line 1441) * __satfractsiuda: Fixed-point fractional library routines. ! (line 1448) * __satfractsiudq: Fixed-point fractional library routines. ! (line 1445) * __satfractsiuha: Fixed-point fractional library routines. ! (line 1446) * __satfractsiuhq: Fixed-point fractional library routines. ! (line 1443) * __satfractsiuqq: Fixed-point fractional library routines. ! (line 1442) * __satfractsiusa: Fixed-point fractional library routines. ! (line 1447) * __satfractsiusq: Fixed-point fractional library routines. ! (line 1444) * __satfractsiuta: Fixed-point fractional library routines. ! (line 1449) * __satfractsqda: Fixed-point fractional library routines. ! (line 1079) * __satfractsqdq2: Fixed-point fractional library routines. ! (line 1076) * __satfractsqha: Fixed-point fractional library routines. ! (line 1077) * __satfractsqhq2: Fixed-point fractional library routines. ! (line 1075) * __satfractsqqq2: Fixed-point fractional library routines. ! (line 1074) * __satfractsqsa: Fixed-point fractional library routines. ! (line 1078) * __satfractsqta: Fixed-point fractional library routines. ! (line 1080) * __satfractsquda: Fixed-point fractional library routines. ! (line 1090) * __satfractsqudq: Fixed-point fractional library routines. ! (line 1086) * __satfractsquha: Fixed-point fractional library routines. ! (line 1088) * __satfractsquhq: Fixed-point fractional library routines. ! (line 1083) * __satfractsquqq: Fixed-point fractional library routines. ! (line 1082) * __satfractsqusa: Fixed-point fractional library routines. ! (line 1089) * __satfractsqusq: Fixed-point fractional library routines. ! (line 1084) * __satfractsquta: Fixed-point fractional library routines. ! (line 1092) * __satfracttada2: Fixed-point fractional library routines. ! (line 1175) * __satfracttadq: Fixed-point fractional library routines. ! (line 1172) * __satfracttaha2: Fixed-point fractional library routines. ! (line 1173) * __satfracttahq: Fixed-point fractional library routines. ! (line 1170) * __satfracttaqq: Fixed-point fractional library routines. ! (line 1169) * __satfracttasa2: Fixed-point fractional library routines. ! (line 1174) * __satfracttasq: Fixed-point fractional library routines. ! (line 1171) * __satfracttauda: Fixed-point fractional library routines. ! (line 1187) * __satfracttaudq: Fixed-point fractional library routines. ! (line 1182) * __satfracttauha: Fixed-point fractional library routines. ! (line 1184) * __satfracttauhq: Fixed-point fractional library routines. ! (line 1178) * __satfracttauqq: Fixed-point fractional library routines. ! (line 1177) * __satfracttausa: Fixed-point fractional library routines. ! (line 1185) * __satfracttausq: Fixed-point fractional library routines. ! (line 1180) * __satfracttauta: Fixed-point fractional library routines. ! (line 1189) * __satfracttida: Fixed-point fractional library routines. ! (line 1472) * __satfracttidq: Fixed-point fractional library routines. ! (line 1469) * __satfracttiha: Fixed-point fractional library routines. ! (line 1470) * __satfracttihq: Fixed-point fractional library routines. ! (line 1467) * __satfracttiqq: Fixed-point fractional library routines. ! (line 1466) * __satfracttisa: Fixed-point fractional library routines. ! (line 1471) * __satfracttisq: Fixed-point fractional library routines. ! (line 1468) * __satfracttita: Fixed-point fractional library routines. ! (line 1473) * __satfracttiuda: Fixed-point fractional library routines. ! (line 1481) * __satfracttiudq: Fixed-point fractional library routines. ! (line 1478) * __satfracttiuha: Fixed-point fractional library routines. ! (line 1479) * __satfracttiuhq: Fixed-point fractional library routines. ! (line 1475) * __satfracttiuqq: Fixed-point fractional library routines. ! (line 1474) * __satfracttiusa: Fixed-point fractional library routines. ! (line 1480) * __satfracttiusq: Fixed-point fractional library routines. ! (line 1476) * __satfracttiuta: Fixed-point fractional library routines. ! (line 1483) * __satfractudada: Fixed-point fractional library routines. ! (line 1351) * __satfractudadq: Fixed-point fractional library routines. ! (line 1347) * __satfractudaha: Fixed-point fractional library routines. ! (line 1349) * __satfractudahq: Fixed-point fractional library routines. ! (line 1344) * __satfractudaqq: Fixed-point fractional library routines. ! (line 1343) * __satfractudasa: Fixed-point fractional library routines. ! (line 1350) * __satfractudasq: Fixed-point fractional library routines. ! (line 1345) * __satfractudata: Fixed-point fractional library routines. ! (line 1353) * __satfractudaudq: Fixed-point fractional library routines. ! (line 1361) * __satfractudauha2: Fixed-point fractional library routines. (line 1363) + * __satfractudauhq: Fixed-point fractional library routines. + (line 1357) * __satfractudauqq: Fixed-point fractional library routines. ! (line 1355) * __satfractudausa2: Fixed-point fractional library routines. (line 1365) + * __satfractudausq: Fixed-point fractional library routines. + (line 1359) * __satfractudauta2: Fixed-point fractional library routines. ! (line 1367) * __satfractudqda: Fixed-point fractional library routines. ! (line 1276) * __satfractudqdq: Fixed-point fractional library routines. ! (line 1271) * __satfractudqha: Fixed-point fractional library routines. ! (line 1273) * __satfractudqhq: Fixed-point fractional library routines. ! (line 1267) * __satfractudqqq: Fixed-point fractional library routines. ! (line 1266) * __satfractudqsa: Fixed-point fractional library routines. ! (line 1274) * __satfractudqsq: Fixed-point fractional library routines. ! (line 1269) * __satfractudqta: Fixed-point fractional library routines. ! (line 1278) * __satfractudquda: Fixed-point fractional library routines. ! (line 1290) * __satfractudquha: Fixed-point fractional library routines. ! (line 1286) * __satfractudquhq2: Fixed-point fractional library routines. ! (line 1282) * __satfractudquqq2: Fixed-point fractional library routines. ! (line 1280) * __satfractudqusa: Fixed-point fractional library routines. ! (line 1288) * __satfractudqusq2: Fixed-point fractional library routines. ! (line 1284) * __satfractudquta: Fixed-point fractional library routines. ! (line 1292) * __satfractuhada: Fixed-point fractional library routines. ! (line 1304) * __satfractuhadq: Fixed-point fractional library routines. ! (line 1299) * __satfractuhaha: Fixed-point fractional library routines. ! (line 1301) * __satfractuhahq: Fixed-point fractional library routines. ! (line 1295) * __satfractuhaqq: Fixed-point fractional library routines. ! (line 1294) * __satfractuhasa: Fixed-point fractional library routines. ! (line 1302) * __satfractuhasq: Fixed-point fractional library routines. ! (line 1297) * __satfractuhata: Fixed-point fractional library routines. ! (line 1306) * __satfractuhauda2: Fixed-point fractional library routines. ! (line 1318) * __satfractuhaudq: Fixed-point fractional library routines. ! (line 1314) * __satfractuhauhq: Fixed-point fractional library routines. ! (line 1310) * __satfractuhauqq: Fixed-point fractional library routines. ! (line 1308) * __satfractuhausa2: Fixed-point fractional library routines. ! (line 1316) * __satfractuhausq: Fixed-point fractional library routines. ! (line 1312) * __satfractuhauta2: Fixed-point fractional library routines. ! (line 1320) * __satfractuhqda: Fixed-point fractional library routines. ! (line 1224) * __satfractuhqdq: Fixed-point fractional library routines. ! (line 1221) * __satfractuhqha: Fixed-point fractional library routines. ! (line 1222) * __satfractuhqhq: Fixed-point fractional library routines. ! (line 1219) * __satfractuhqqq: Fixed-point fractional library routines. ! (line 1218) * __satfractuhqsa: Fixed-point fractional library routines. ! (line 1223) * __satfractuhqsq: Fixed-point fractional library routines. ! (line 1220) * __satfractuhqta: Fixed-point fractional library routines. ! (line 1225) * __satfractuhquda: Fixed-point fractional library routines. ! (line 1236) * __satfractuhqudq2: Fixed-point fractional library routines. ! (line 1231) * __satfractuhquha: Fixed-point fractional library routines. (line 1233) + * __satfractuhquqq2: Fixed-point fractional library routines. + (line 1227) * __satfractuhqusa: Fixed-point fractional library routines. ! (line 1234) * __satfractuhqusq2: Fixed-point fractional library routines. ! (line 1229) * __satfractuhquta: Fixed-point fractional library routines. ! (line 1238) * __satfractunsdida: Fixed-point fractional library routines. ! (line 1834) * __satfractunsdidq: Fixed-point fractional library routines. ! (line 1831) * __satfractunsdiha: Fixed-point fractional library routines. ! (line 1832) * __satfractunsdihq: Fixed-point fractional library routines. ! (line 1828) * __satfractunsdiqq: Fixed-point fractional library routines. ! (line 1827) * __satfractunsdisa: Fixed-point fractional library routines. ! (line 1833) * __satfractunsdisq: Fixed-point fractional library routines. ! (line 1829) * __satfractunsdita: Fixed-point fractional library routines. ! (line 1836) * __satfractunsdiuda: Fixed-point fractional library routines. (line 1850) + * __satfractunsdiudq: Fixed-point fractional library routines. + (line 1844) * __satfractunsdiuha: Fixed-point fractional library routines. (line 1846) + * __satfractunsdiuhq: Fixed-point fractional library routines. + (line 1840) * __satfractunsdiuqq: Fixed-point fractional library routines. ! (line 1838) * __satfractunsdiusa: Fixed-point fractional library routines. (line 1848) + * __satfractunsdiusq: Fixed-point fractional library routines. + (line 1842) * __satfractunsdiuta: Fixed-point fractional library routines. ! (line 1852) * __satfractunshida: Fixed-point fractional library routines. ! (line 1786) * __satfractunshidq: Fixed-point fractional library routines. ! (line 1783) * __satfractunshiha: Fixed-point fractional library routines. ! (line 1784) * __satfractunshihq: Fixed-point fractional library routines. ! (line 1780) * __satfractunshiqq: Fixed-point fractional library routines. ! (line 1779) * __satfractunshisa: Fixed-point fractional library routines. ! (line 1785) * __satfractunshisq: Fixed-point fractional library routines. ! (line 1781) * __satfractunshita: Fixed-point fractional library routines. ! (line 1788) * __satfractunshiuda: Fixed-point fractional library routines. (line 1802) + * __satfractunshiudq: Fixed-point fractional library routines. + (line 1796) * __satfractunshiuha: Fixed-point fractional library routines. (line 1798) + * __satfractunshiuhq: Fixed-point fractional library routines. + (line 1792) * __satfractunshiuqq: Fixed-point fractional library routines. ! (line 1790) * __satfractunshiusa: Fixed-point fractional library routines. (line 1800) + * __satfractunshiusq: Fixed-point fractional library routines. + (line 1794) * __satfractunshiuta: Fixed-point fractional library routines. ! (line 1804) * __satfractunsqida: Fixed-point fractional library routines. ! (line 1760) * __satfractunsqidq: Fixed-point fractional library routines. ! (line 1757) * __satfractunsqiha: Fixed-point fractional library routines. ! (line 1758) * __satfractunsqihq: Fixed-point fractional library routines. ! (line 1754) * __satfractunsqiqq: Fixed-point fractional library routines. ! (line 1753) * __satfractunsqisa: Fixed-point fractional library routines. ! (line 1759) * __satfractunsqisq: Fixed-point fractional library routines. ! (line 1755) * __satfractunsqita: Fixed-point fractional library routines. ! (line 1762) * __satfractunsqiuda: Fixed-point fractional library routines. (line 1776) + * __satfractunsqiudq: Fixed-point fractional library routines. + (line 1770) * __satfractunsqiuha: Fixed-point fractional library routines. (line 1772) + * __satfractunsqiuhq: Fixed-point fractional library routines. + (line 1766) * __satfractunsqiuqq: Fixed-point fractional library routines. ! (line 1764) * __satfractunsqiusa: Fixed-point fractional library routines. (line 1774) + * __satfractunsqiusq: Fixed-point fractional library routines. + (line 1768) * __satfractunsqiuta: Fixed-point fractional library routines. ! (line 1778) * __satfractunssida: Fixed-point fractional library routines. ! (line 1811) * __satfractunssidq: Fixed-point fractional library routines. ! (line 1808) * __satfractunssiha: Fixed-point fractional library routines. ! (line 1809) * __satfractunssihq: Fixed-point fractional library routines. ! (line 1806) * __satfractunssiqq: Fixed-point fractional library routines. ! (line 1805) * __satfractunssisa: Fixed-point fractional library routines. ! (line 1810) * __satfractunssisq: Fixed-point fractional library routines. ! (line 1807) * __satfractunssita: Fixed-point fractional library routines. ! (line 1812) * __satfractunssiuda: Fixed-point fractional library routines. ! (line 1824) * __satfractunssiudq: Fixed-point fractional library routines. ! (line 1819) * __satfractunssiuha: Fixed-point fractional library routines. ! (line 1821) * __satfractunssiuhq: Fixed-point fractional library routines. ! (line 1815) * __satfractunssiuqq: Fixed-point fractional library routines. ! (line 1814) * __satfractunssiusa: Fixed-point fractional library routines. ! (line 1822) * __satfractunssiusq: Fixed-point fractional library routines. ! (line 1817) * __satfractunssiuta: Fixed-point fractional library routines. ! (line 1826) * __satfractunstida: Fixed-point fractional library routines. ! (line 1864) * __satfractunstidq: Fixed-point fractional library routines. ! (line 1859) * __satfractunstiha: Fixed-point fractional library routines. ! (line 1861) * __satfractunstihq: Fixed-point fractional library routines. ! (line 1855) * __satfractunstiqq: Fixed-point fractional library routines. ! (line 1854) * __satfractunstisa: Fixed-point fractional library routines. ! (line 1862) * __satfractunstisq: Fixed-point fractional library routines. ! (line 1857) * __satfractunstita: Fixed-point fractional library routines. ! (line 1866) * __satfractunstiuda: Fixed-point fractional library routines. (line 1880) + * __satfractunstiudq: Fixed-point fractional library routines. + (line 1874) * __satfractunstiuha: Fixed-point fractional library routines. (line 1876) + * __satfractunstiuhq: Fixed-point fractional library routines. + (line 1870) * __satfractunstiuqq: Fixed-point fractional library routines. ! (line 1868) * __satfractunstiusa: Fixed-point fractional library routines. (line 1878) + * __satfractunstiusq: Fixed-point fractional library routines. + (line 1872) * __satfractunstiuta: Fixed-point fractional library routines. ! (line 1882) * __satfractuqqda: Fixed-point fractional library routines. ! (line 1201) * __satfractuqqdq: Fixed-point fractional library routines. ! (line 1196) * __satfractuqqha: Fixed-point fractional library routines. ! (line 1198) * __satfractuqqhq: Fixed-point fractional library routines. ! (line 1192) * __satfractuqqqq: Fixed-point fractional library routines. ! (line 1191) * __satfractuqqsa: Fixed-point fractional library routines. ! (line 1199) * __satfractuqqsq: Fixed-point fractional library routines. ! (line 1194) * __satfractuqqta: Fixed-point fractional library routines. ! (line 1203) * __satfractuqquda: Fixed-point fractional library routines. (line 1215) + * __satfractuqqudq2: Fixed-point fractional library routines. + (line 1209) * __satfractuqquha: Fixed-point fractional library routines. (line 1211) + * __satfractuqquhq2: Fixed-point fractional library routines. + (line 1205) * __satfractuqqusa: Fixed-point fractional library routines. (line 1213) + * __satfractuqqusq2: Fixed-point fractional library routines. + (line 1207) * __satfractuqquta: Fixed-point fractional library routines. ! (line 1217) * __satfractusada: Fixed-point fractional library routines. ! (line 1327) * __satfractusadq: Fixed-point fractional library routines. ! (line 1324) * __satfractusaha: Fixed-point fractional library routines. ! (line 1325) * __satfractusahq: Fixed-point fractional library routines. ! (line 1322) * __satfractusaqq: Fixed-point fractional library routines. ! (line 1321) * __satfractusasa: Fixed-point fractional library routines. ! (line 1326) * __satfractusasq: Fixed-point fractional library routines. ! (line 1323) * __satfractusata: Fixed-point fractional library routines. ! (line 1328) * __satfractusauda2: Fixed-point fractional library routines. ! (line 1339) * __satfractusaudq: Fixed-point fractional library routines. ! (line 1335) * __satfractusauha2: Fixed-point fractional library routines. ! (line 1337) * __satfractusauhq: Fixed-point fractional library routines. ! (line 1331) * __satfractusauqq: Fixed-point fractional library routines. ! (line 1330) * __satfractusausq: Fixed-point fractional library routines. ! (line 1333) * __satfractusauta2: Fixed-point fractional library routines. ! (line 1341) * __satfractusqda: Fixed-point fractional library routines. ! (line 1248) * __satfractusqdq: Fixed-point fractional library routines. ! (line 1244) * __satfractusqha: Fixed-point fractional library routines. ! (line 1246) * __satfractusqhq: Fixed-point fractional library routines. ! (line 1241) * __satfractusqqq: Fixed-point fractional library routines. ! (line 1240) * __satfractusqsa: Fixed-point fractional library routines. ! (line 1247) * __satfractusqsq: Fixed-point fractional library routines. ! (line 1242) * __satfractusqta: Fixed-point fractional library routines. ! (line 1250) * __satfractusquda: Fixed-point fractional library routines. (line 1262) + * __satfractusqudq2: Fixed-point fractional library routines. + (line 1256) * __satfractusquha: Fixed-point fractional library routines. ! (line 1258) * __satfractusquhq2: Fixed-point fractional library routines. ! (line 1254) * __satfractusquqq2: Fixed-point fractional library routines. ! (line 1252) * __satfractusqusa: Fixed-point fractional library routines. ! (line 1260) * __satfractusquta: Fixed-point fractional library routines. ! (line 1264) * __satfractutada: Fixed-point fractional library routines. ! (line 1379) * __satfractutadq: Fixed-point fractional library routines. ! (line 1374) * __satfractutaha: Fixed-point fractional library routines. ! (line 1376) * __satfractutahq: Fixed-point fractional library routines. ! (line 1370) * __satfractutaqq: Fixed-point fractional library routines. ! (line 1369) * __satfractutasa: Fixed-point fractional library routines. ! (line 1377) * __satfractutasq: Fixed-point fractional library routines. ! (line 1372) * __satfractutata: Fixed-point fractional library routines. ! (line 1381) * __satfractutauda2: Fixed-point fractional library routines. (line 1395) + * __satfractutaudq: Fixed-point fractional library routines. + (line 1389) * __satfractutauha2: Fixed-point fractional library routines. (line 1391) + * __satfractutauhq: Fixed-point fractional library routines. + (line 1385) * __satfractutauqq: Fixed-point fractional library routines. ! (line 1383) * __satfractutausa2: Fixed-point fractional library routines. (line 1393) + * __satfractutausq: Fixed-point fractional library routines. + (line 1387) * __splitstack_find: Miscellaneous routines. ! (line 18) * __ssaddda3: Fixed-point fractional library routines. ! (line 67) * __ssadddq3: Fixed-point fractional library routines. ! (line 63) * __ssaddha3: Fixed-point fractional library routines. ! (line 65) * __ssaddhq3: Fixed-point fractional library routines. ! (line 60) * __ssaddqq3: Fixed-point fractional library routines. ! (line 59) * __ssaddsa3: Fixed-point fractional library routines. ! (line 66) * __ssaddsq3: Fixed-point fractional library routines. ! (line 61) * __ssaddta3: Fixed-point fractional library routines. ! (line 69) * __ssashlda3: Fixed-point fractional library routines. ! (line 402) * __ssashldq3: Fixed-point fractional library routines. ! (line 399) * __ssashlha3: Fixed-point fractional library routines. ! (line 400) * __ssashlhq3: Fixed-point fractional library routines. ! (line 396) * __ssashlsa3: Fixed-point fractional library routines. ! (line 401) * __ssashlsq3: Fixed-point fractional library routines. ! (line 397) * __ssashlta3: Fixed-point fractional library routines. ! (line 404) * __ssdivda3: Fixed-point fractional library routines. ! (line 261) * __ssdivdq3: Fixed-point fractional library routines. ! (line 257) * __ssdivha3: Fixed-point fractional library routines. ! (line 259) * __ssdivhq3: Fixed-point fractional library routines. ! (line 254) * __ssdivqq3: Fixed-point fractional library routines. ! (line 253) * __ssdivsa3: Fixed-point fractional library routines. ! (line 260) * __ssdivsq3: Fixed-point fractional library routines. ! (line 255) * __ssdivta3: Fixed-point fractional library routines. ! (line 263) * __ssmulda3: Fixed-point fractional library routines. ! (line 193) * __ssmuldq3: Fixed-point fractional library routines. ! (line 189) * __ssmulha3: Fixed-point fractional library routines. ! (line 191) * __ssmulhq3: Fixed-point fractional library routines. ! (line 186) * __ssmulqq3: Fixed-point fractional library routines. ! (line 185) * __ssmulsa3: Fixed-point fractional library routines. ! (line 192) * __ssmulsq3: Fixed-point fractional library routines. ! (line 187) * __ssmulta3: Fixed-point fractional library routines. ! (line 195) * __ssnegda2: Fixed-point fractional library routines. ! (line 316) * __ssnegdq2: Fixed-point fractional library routines. ! (line 313) * __ssnegha2: Fixed-point fractional library routines. ! (line 314) * __ssneghq2: Fixed-point fractional library routines. ! (line 311) * __ssnegqq2: Fixed-point fractional library routines. ! (line 310) * __ssnegsa2: Fixed-point fractional library routines. ! (line 315) * __ssnegsq2: Fixed-point fractional library routines. ! (line 312) * __ssnegta2: Fixed-point fractional library routines. ! (line 317) * __sssubda3: Fixed-point fractional library routines. ! (line 129) * __sssubdq3: Fixed-point fractional library routines. ! (line 125) * __sssubha3: Fixed-point fractional library routines. ! (line 127) * __sssubhq3: Fixed-point fractional library routines. ! (line 122) * __sssubqq3: Fixed-point fractional library routines. ! (line 121) * __sssubsa3: Fixed-point fractional library routines. ! (line 128) * __sssubsq3: Fixed-point fractional library routines. ! (line 123) * __sssubta3: Fixed-point fractional library routines. ! (line 131) * __subda3: Fixed-point fractional library routines. ! (line 107) * __subdf3: Soft float library routines. ! (line 31) * __subdq3: Fixed-point fractional library routines. ! (line 95) * __subha3: Fixed-point fractional library routines. ! (line 105) * __subhq3: Fixed-point fractional library routines. ! (line 92) * __subqq3: Fixed-point fractional library routines. ! (line 91) * __subsa3: Fixed-point fractional library routines. ! (line 106) * __subsf3: Soft float library routines. ! (line 30) * __subsq3: Fixed-point fractional library routines. ! (line 93) * __subta3: Fixed-point fractional library routines. ! (line 109) * __subtf3: Soft float library routines. ! (line 33) * __subuda3: Fixed-point fractional library routines. ! (line 115) * __subudq3: Fixed-point fractional library routines. ! (line 103) * __subuha3: Fixed-point fractional library routines. ! (line 111) * __subuhq3: Fixed-point fractional library routines. ! (line 99) * __subuqq3: Fixed-point fractional library routines. ! (line 97) * __subusa3: Fixed-point fractional library routines. ! (line 113) * __subusq3: Fixed-point fractional library routines. ! (line 101) * __subuta3: Fixed-point fractional library routines. ! (line 117) * __subvdi3: Integer library routines. ! (line 123) * __subvsi3: Integer library routines. ! (line 122) * __subxf3: Soft float library routines. ! (line 35) * __truncdfsf2: Soft float library routines. ! (line 76) * __trunctfdf2: Soft float library routines. ! (line 73) * __trunctfsf2: Soft float library routines. ! (line 75) * __truncxfdf2: Soft float library routines. ! (line 72) * __truncxfsf2: Soft float library routines. ! (line 74) * __ucmpdi2: Integer library routines. (line 93) + * __ucmpti2: Integer library routines. + (line 95) * __udivdi3: Integer library routines. ! (line 54) * __udivmoddi4: Integer library routines. (line 61) + * __udivmodti4: Integer library routines. + (line 63) * __udivsi3: Integer library routines. ! (line 52) * __udivti3: Integer library routines. ! (line 56) * __udivuda3: Fixed-point fractional library routines. (line 246) + * __udivudq3: Fixed-point fractional library routines. + (line 240) * __udivuha3: Fixed-point fractional library routines. (line 242) + * __udivuhq3: Fixed-point fractional library routines. + (line 236) * __udivuqq3: Fixed-point fractional library routines. ! (line 234) * __udivusa3: Fixed-point fractional library routines. (line 244) + * __udivusq3: Fixed-point fractional library routines. + (line 238) * __udivuta3: Fixed-point fractional library routines. ! (line 248) * __umoddi3: Integer library routines. ! (line 71) * __umodsi3: Integer library routines. ! (line 69) * __umodti3: Integer library routines. ! (line 73) * __unorddf2: Soft float library routines. ! (line 173) * __unordsf2: Soft float library routines. ! (line 172) * __unordtf2: Soft float library routines. ! (line 174) * __usadduda3: Fixed-point fractional library routines. (line 85) + * __usaddudq3: Fixed-point fractional library routines. + (line 79) * __usadduha3: Fixed-point fractional library routines. (line 81) + * __usadduhq3: Fixed-point fractional library routines. + (line 75) * __usadduqq3: Fixed-point fractional library routines. ! (line 73) * __usaddusa3: Fixed-point fractional library routines. (line 83) + * __usaddusq3: Fixed-point fractional library routines. + (line 77) * __usadduta3: Fixed-point fractional library routines. ! (line 87) * __usashluda3: Fixed-point fractional library routines. (line 421) + * __usashludq3: Fixed-point fractional library routines. + (line 415) * __usashluha3: Fixed-point fractional library routines. (line 417) + * __usashluhq3: Fixed-point fractional library routines. + (line 411) * __usashluqq3: Fixed-point fractional library routines. ! (line 409) * __usashlusa3: Fixed-point fractional library routines. (line 419) + * __usashlusq3: Fixed-point fractional library routines. + (line 413) * __usashluta3: Fixed-point fractional library routines. ! (line 423) * __usdivuda3: Fixed-point fractional library routines. (line 280) + * __usdivudq3: Fixed-point fractional library routines. + (line 274) * __usdivuha3: Fixed-point fractional library routines. (line 276) + * __usdivuhq3: Fixed-point fractional library routines. + (line 270) * __usdivuqq3: Fixed-point fractional library routines. ! (line 268) * __usdivusa3: Fixed-point fractional library routines. (line 278) + * __usdivusq3: Fixed-point fractional library routines. + (line 272) * __usdivuta3: Fixed-point fractional library routines. ! (line 282) * __usmuluda3: Fixed-point fractional library routines. (line 212) + * __usmuludq3: Fixed-point fractional library routines. + (line 206) * __usmuluha3: Fixed-point fractional library routines. (line 208) + * __usmuluhq3: Fixed-point fractional library routines. + (line 202) * __usmuluqq3: Fixed-point fractional library routines. ! (line 200) * __usmulusa3: Fixed-point fractional library routines. (line 210) + * __usmulusq3: Fixed-point fractional library routines. + (line 204) * __usmuluta3: Fixed-point fractional library routines. ! (line 214) * __usneguda2: Fixed-point fractional library routines. ! (line 331) * __usnegudq2: Fixed-point fractional library routines. ! (line 326) * __usneguha2: Fixed-point fractional library routines. ! (line 328) * __usneguhq2: Fixed-point fractional library routines. ! (line 322) * __usneguqq2: Fixed-point fractional library routines. ! (line 321) * __usnegusa2: Fixed-point fractional library routines. ! (line 329) * __usnegusq2: Fixed-point fractional library routines. ! (line 324) * __usneguta2: Fixed-point fractional library routines. ! (line 333) * __ussubuda3: Fixed-point fractional library routines. (line 148) + * __ussubudq3: Fixed-point fractional library routines. + (line 142) * __ussubuha3: Fixed-point fractional library routines. (line 144) + * __ussubuhq3: Fixed-point fractional library routines. + (line 138) * __ussubuqq3: Fixed-point fractional library routines. ! (line 136) * __ussubusa3: Fixed-point fractional library routines. (line 146) + * __ussubusq3: Fixed-point fractional library routines. + (line 140) * __ussubuta3: Fixed-point fractional library routines. ! (line 150) ! * abort: Portability. (line 21) ! * abs: Arithmetic. (line 199) ! * abs and attributes: Expressions. (line 85) * ABS_EXPR: Unary and Binary Expressions. (line 6) + * absence_set: Processor pipeline description. + (line 224) + * absM2 instruction pattern: Standard Names. (line 616) + * absolute value: Arithmetic. (line 199) * access to operands: Accessors. (line 6) * access to special operands: Special Accessors. (line 6) * accessors: Accessors. (line 6) ! * ACCUM_TYPE_SIZE: Type Layout. (line 88) ! * ACCUMULATE_OUTGOING_ARGS: Stack Arguments. (line 49) ! * ACCUMULATE_OUTGOING_ARGS and stack frames: Function Entry. (line 135) ! * acosM2 instruction pattern: Standard Names. (line 703) ! * ADA_LONG_TYPE_SIZE: Type Layout. (line 26) * Adding a new GIMPLE statement code: Adding a new GIMPLE statement code. (line 6) ! * ADDITIONAL_REGISTER_NAMES: Instruction Output. (line 15) ! * addM3 instruction pattern: Standard Names. (line 299) ! * addMODEcc instruction pattern: Standard Names. (line 1272) ! * addptrM3 instruction pattern: Standard Names. (line 332) ! * addr_diff_vec: Side Effects. (line 315) * addr_diff_vec, length of: Insn Lengths. (line 26) * ADDR_EXPR: Storage References. (line 6) ! * addr_vec: Side Effects. (line 310) * addr_vec, length of: Insn Lengths. (line 26) ! * address constraints: Simple Constraints. (line 164) ! * address_operand <1>: Simple Constraints. (line 168) ! * address_operand: Machine-Independent Predicates. ! (line 63) ! * addressing modes: Addressing Modes. (line 6) ! * addvM4 instruction pattern: Standard Names. (line 315) ! * ADJUST_FIELD_ALIGN: Storage Layout. (line 197) * ADJUST_INSN_LENGTH: Insn Lengths. (line 41) ! * ADJUST_REG_ALLOC_ORDER: Allocation Order. (line 23) * aggregates as return values: Aggregate Return. (line 6) * alias: Alias analysis. (line 6) * ALL_REGS: Register Classes. (line 17) + * allocate_stack instruction pattern: Standard Names. (line 1603) * alternate entry points: Insns. (line 146) * anchored addresses: Anchored Addresses. (line 6) ! * and: Arithmetic. (line 157) * and and attributes: Expressions. (line 50) * and, canonicalization of: Insn Canonicalizations. ! (line 52) ! * andM3 instruction pattern: Standard Names. (line 305) * ANNOTATE_EXPR: Unary and Binary Expressions. (line 6) * annotations: Annotations. (line 6) * APPLY_RESULT_SIZE: Scalar Return. (line 112) ! * ARG_POINTER_CFA_OFFSET: Frame Layout. (line 192) ! * ARG_POINTER_REGNUM: Frame Registers. (line 41) ! * ARG_POINTER_REGNUM and virtual registers: Regs and Memory. (line 65) ! * arg_pointer_rtx: Frame Registers. (line 104) ! * ARGS_GROW_DOWNWARD: Frame Layout. (line 31) * argument passing: Interface. (line 36) * arguments in registers: Register Arguments. (line 6) * arguments on stack: Stack Arguments. (line 6) * arithmetic library: Soft float library routines. (line 6) ! * arithmetic shift: Arithmetic. (line 172) ! * arithmetic shift with signed saturation: Arithmetic. (line 172) ! * arithmetic shift with unsigned saturation: Arithmetic. (line 172) * arithmetic, in RTL: Arithmetic. (line 6) ! * ARITHMETIC_TYPE_P: Types for C++. (line 61) * array: Types. (line 6) * ARRAY_RANGE_REF: Storage References. (line 6) * ARRAY_REF: Storage References. (line 6) * ARRAY_TYPE: Types. (line 6) ! * AS_NEEDS_DASH_FOR_PIPED_INPUT: Driver. (line 89) ! * ashift: Arithmetic. (line 172) ! * ashift and attributes: Expressions. (line 85) ! * ashiftrt: Arithmetic. (line 189) ! * ashiftrt and attributes: Expressions. (line 85) ! * ashlM3 instruction pattern: Standard Names. (line 585) ! * ashrM3 instruction pattern: Standard Names. (line 597) ! * asinM2 instruction pattern: Standard Names. (line 697) ! * ASM_APP_OFF: File Framework. (line 78) ! * ASM_APP_ON: File Framework. (line 71) ! * ASM_COMMENT_START: File Framework. (line 66) ! * ASM_DECLARE_COLD_FUNCTION_NAME: Label Output. (line 139) ! * ASM_DECLARE_COLD_FUNCTION_SIZE: Label Output. (line 154) ! * ASM_DECLARE_FUNCTION_NAME: Label Output. (line 111) ! * ASM_DECLARE_FUNCTION_SIZE: Label Output. (line 126) ! * ASM_DECLARE_OBJECT_NAME: Label Output. (line 167) ! * ASM_DECLARE_REGISTER_GLOBAL: Label Output. (line 196) ! * ASM_FINAL_SPEC: Driver. (line 82) ! * ASM_FINISH_DECLARE_OBJECT: Label Output. (line 204) ! * ASM_FORMAT_PRIVATE_NAME: Label Output. (line 430) ! * asm_fprintf: Instruction Output. (line 151) ! * ASM_FPRINTF_EXTENSIONS: Instruction Output. (line 162) ! * ASM_GENERATE_INTERNAL_LABEL: Label Output. (line 414) ! * asm_input: Side Effects. (line 297) * asm_input and /v: Flags. (line 76) ! * ASM_MAYBE_OUTPUT_ENCODED_ADDR_RTX: Exception Handling. (line 82) ! * ASM_NO_SKIP_IN_TEXT: Alignment Output. (line 79) ! * asm_noperands: Insns. (line 308) * asm_operands and /v: Flags. (line 76) * asm_operands, RTL sharing: Sharing. (line 45) * asm_operands, usage: Assembler. (line 6) ! * ASM_OUTPUT_ADDR_DIFF_ELT: Dispatch Tables. (line 9) ! * ASM_OUTPUT_ADDR_VEC_ELT: Dispatch Tables. (line 26) ! * ASM_OUTPUT_ALIGN: Alignment Output. (line 86) ! * ASM_OUTPUT_ALIGN_WITH_NOP: Alignment Output. (line 91) ! * ASM_OUTPUT_ALIGNED_BSS: Uninitialized Data. (line 46) ! * ASM_OUTPUT_ALIGNED_COMMON: Uninitialized Data. (line 30) ! * ASM_OUTPUT_ALIGNED_DECL_COMMON: Uninitialized Data. (line 38) ! * ASM_OUTPUT_ALIGNED_DECL_LOCAL: Uninitialized Data. (line 91) ! * ASM_OUTPUT_ALIGNED_LOCAL: Uninitialized Data. (line 83) ! * ASM_OUTPUT_ASCII: Data Output. (line 55) ! * ASM_OUTPUT_CASE_END: Dispatch Tables. (line 51) ! * ASM_OUTPUT_CASE_LABEL: Dispatch Tables. (line 38) ! * ASM_OUTPUT_COMMON: Uninitialized Data. (line 10) ! * ASM_OUTPUT_DEBUG_LABEL: Label Output. (line 402) ! * ASM_OUTPUT_DEF: Label Output. (line 451) ! * ASM_OUTPUT_DEF_FROM_DECLS: Label Output. (line 459) ! * ASM_OUTPUT_DWARF_DATAREL: SDB and DWARF. (line 98) ! * ASM_OUTPUT_DWARF_DELTA: SDB and DWARF. (line 78) ! * ASM_OUTPUT_DWARF_OFFSET: SDB and DWARF. (line 87) ! * ASM_OUTPUT_DWARF_PCREL: SDB and DWARF. (line 93) ! * ASM_OUTPUT_DWARF_TABLE_REF: SDB and DWARF. (line 103) ! * ASM_OUTPUT_DWARF_VMS_DELTA: SDB and DWARF. (line 82) ! * ASM_OUTPUT_EXTERNAL: Label Output. (line 331) ! * ASM_OUTPUT_FDESC: Data Output. (line 64) ! * ASM_OUTPUT_FUNCTION_LABEL: Label Output. (line 17) ! * ASM_OUTPUT_INTERNAL_LABEL: Label Output. (line 29) ! * ASM_OUTPUT_LABEL: Label Output. (line 9) ! * ASM_OUTPUT_LABEL_REF: Label Output. (line 375) ! * ASM_OUTPUT_LABELREF: Label Output. (line 353) ! * ASM_OUTPUT_LOCAL: Uninitialized Data. (line 70) ! * ASM_OUTPUT_MAX_SKIP_ALIGN: Alignment Output. (line 95) ! * ASM_OUTPUT_MEASURED_SIZE: Label Output. (line 53) ! * ASM_OUTPUT_OPCODE: Instruction Output. (line 36) ! * ASM_OUTPUT_POOL_EPILOGUE: Data Output. (line 114) ! * ASM_OUTPUT_POOL_PROLOGUE: Data Output. (line 77) ! * ASM_OUTPUT_REG_POP: Instruction Output. (line 208) ! * ASM_OUTPUT_REG_PUSH: Instruction Output. (line 203) ! * ASM_OUTPUT_SIZE_DIRECTIVE: Label Output. (line 47) ! * ASM_OUTPUT_SKIP: Alignment Output. (line 73) ! * ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 85) ! * ASM_OUTPUT_SPECIAL_POOL_ENTRY: Data Output. (line 89) ! * ASM_OUTPUT_SYMBOL_REF: Label Output. (line 368) ! * ASM_OUTPUT_TYPE_DIRECTIVE: Label Output. (line 101) ! * ASM_OUTPUT_WEAK_ALIAS: Label Output. (line 477) ! * ASM_OUTPUT_WEAKREF: Label Output. (line 263) ! * ASM_PREFERRED_EH_DATA_FORMAT: Exception Handling. (line 67) ! * ASM_SPEC: Driver. (line 74) ! * ASM_STABD_OP: DBX Options. (line 36) ! * ASM_STABN_OP: DBX Options. (line 43) ! * ASM_STABS_OP: DBX Options. (line 29) ! * ASM_WEAKEN_DECL: Label Output. (line 255) ! * ASM_WEAKEN_LABEL: Label Output. (line 242) ! * assemble_name: Label Output. (line 8) ! * assemble_name_raw: Label Output. (line 28) * assembler format: File Framework. (line 6) * assembler instructions in RTL: Assembler. (line 6) ! * ASSEMBLER_DIALECT: Instruction Output. (line 174) * assigning attribute values to insns: Tagging Insns. (line 6) ! * ASSUME_EXTENDED_UNWIND_CONTEXT: Frame Registers. (line 164) * asterisk in template: Output Statement. (line 29) ! * atan2M3 instruction pattern: Standard Names. (line 798) ! * atanM2 instruction pattern: Standard Names. (line 709) ! * atomic: GTY Options. (line 188) ! * atomic_add_fetchMODE instruction pattern: Standard Names. (line 2036) ! * atomic_addMODE instruction pattern: Standard Names. (line 2007) ! * atomic_and_fetchMODE instruction pattern: Standard Names. (line 2036) ! * atomic_andMODE instruction pattern: Standard Names. (line 2007) * atomic_compare_and_swapMODE instruction pattern: Standard Names. ! (line 1943) ! * atomic_exchangeMODE instruction pattern: Standard Names. (line 1995) ! * atomic_fetch_addMODE instruction pattern: Standard Names. (line 2021) ! * atomic_fetch_andMODE instruction pattern: Standard Names. (line 2021) ! * atomic_fetch_nandMODE instruction pattern: Standard Names. (line 2021) ! * atomic_fetch_orMODE instruction pattern: Standard Names. (line 2021) ! * atomic_fetch_subMODE instruction pattern: Standard Names. (line 2021) ! * atomic_fetch_xorMODE instruction pattern: Standard Names. (line 2021) ! * atomic_loadMODE instruction pattern: Standard Names. (line 1974) ! * atomic_nand_fetchMODE instruction pattern: Standard Names. (line 2036) ! * atomic_nandMODE instruction pattern: Standard Names. (line 2007) ! * atomic_or_fetchMODE instruction pattern: Standard Names. (line 2036) ! * atomic_orMODE instruction pattern: Standard Names. (line 2007) ! * atomic_storeMODE instruction pattern: Standard Names. (line 1984) ! * atomic_sub_fetchMODE instruction pattern: Standard Names. (line 2036) ! * atomic_subMODE instruction pattern: Standard Names. (line 2007) ! * atomic_test_and_set instruction pattern: Standard Names. (line 2053) ! * atomic_xor_fetchMODE instruction pattern: Standard Names. (line 2036) ! * atomic_xorMODE instruction pattern: Standard Names. (line 2007) * attr <1>: Tagging Insns. (line 54) + * attr: Expressions. (line 165) + * attr_flag: Expressions. (line 140) * attribute expressions: Expressions. (line 6) * attribute specifications: Attr Example. (line 6) * attribute specifications example: Attr Example. (line 6) + * ATTRIBUTE_ALIGNED_VALUE: Storage Layout. (line 179) * attributes: Attributes. (line 6) * attributes, defining: Defining Attributes. (line 6) * attributes, target-specific: Target Attributes. (line 6) ! * autoincrement addressing, availability: Portability. (line 21) * autoincrement/decrement addressing: Simple Constraints. (line 30) * automata_option: Processor pipeline description. ! (line 305) * automaton based pipeline description: Processor pipeline description. (line 6) * automaton based scheduler: Processor pipeline description. (line 6) * AVOID_CCMODE_COPIES: Values in Registers. ! (line 153) * backslash: Output Template. (line 46) ! * barrier: Insns. (line 177) * barrier and /f: Flags. (line 107) * barrier and /v: Flags. (line 44) ! * BASE_REG_CLASS: Register Classes. (line 114) * basic block: Basic Blocks. (line 6) * Basic Statements: Basic Statements. (line 6) * basic-block.h: Control Flow. (line 6) * BASIC_BLOCK: Basic Blocks. (line 14) + * basic_block: Basic Blocks. (line 6) * BB_HEAD, BB_END: Maintaining the CFG. ! (line 77) ! * bb_seq: GIMPLE sequences. (line 73) ! * BIGGEST_ALIGNMENT: Storage Layout. (line 164) ! * BIGGEST_FIELD_ALIGNMENT: Storage Layout. (line 190) * BImode: Machine Modes. (line 22) * BIND_EXPR: Unary and Binary Expressions. (line 6) * BINFO_TYPE: Classes. (line 6) * bit-fields: Bit-Fields. (line 6) * BIT_AND_EXPR: Unary and Binary Expressions. (line 6) * BIT_IOR_EXPR: Unary and Binary Expressions. *************** Concept Index *** 47538,47564 **** (line 6) * BIT_XOR_EXPR: Unary and Binary Expressions. (line 6) ! * BLKmode: Machine Modes. (line 185) * BLKmode, and function return values: Calls. (line 23) - * blockage instruction pattern: Standard Names. (line 1795) - * Blocks: Blocks. (line 6) * BLOCK_FOR_INSN, gimple_bb: Maintaining the CFG. ! (line 28) ! * BLOCK_REG_PADDING: Register Arguments. (line 242) ! * BND32mode: Machine Modes. (line 209) ! * BND64mode: Machine Modes. (line 209) ! * bool: Misc. (line 994) * BOOLEAN_TYPE: Types. (line 6) - * BOOL_TYPE_SIZE: Type Layout. (line 43) * branch prediction: Profile information. (line 24) ! * BRANCH_COST: Costs. (line 104) ! * break_out_memory_refs: Addressing Modes. (line 134) * BREAK_STMT: Statements for C++. (line 6) ! * BSS_SECTION_ASM_OP: Sections. (line 67) * bswap: Arithmetic. (line 246) ! * bswapM2 instruction pattern: Standard Names. (line 599) ! * btruncM2 instruction pattern: Standard Names. (line 807) * build0: Macros and Functions. (line 16) * build1: Macros and Functions. --- 48002,48037 ---- (line 6) * BIT_XOR_EXPR: Unary and Binary Expressions. (line 6) ! * BITFIELD_NBYTES_LIMITED: Storage Layout. (line 402) ! * BITS_BIG_ENDIAN: Storage Layout. (line 12) ! * BITS_BIG_ENDIAN, effect on sign_extract: Bit-Fields. (line 8) ! * BITS_PER_UNIT: Machine Modes. (line 355) ! * BITS_PER_WORD: Storage Layout. (line 51) ! * bitwise complement: Arithmetic. (line 153) ! * bitwise exclusive-or: Arithmetic. (line 167) ! * bitwise inclusive-or: Arithmetic. (line 162) ! * bitwise logical-and: Arithmetic. (line 157) ! * BLKmode: Machine Modes. (line 186) * BLKmode, and function return values: Calls. (line 23) * BLOCK_FOR_INSN, gimple_bb: Maintaining the CFG. ! (line 29) ! * BLOCK_REG_PADDING: Register Arguments. (line 244) ! * blockage instruction pattern: Standard Names. (line 1806) ! * Blocks: Blocks. (line 6) ! * BND32mode: Machine Modes. (line 210) ! * BND64mode: Machine Modes. (line 210) ! * bool: Misc. (line 999) ! * BOOL_TYPE_SIZE: Type Layout. (line 44) * BOOLEAN_TYPE: Types. (line 6) * branch prediction: Profile information. (line 24) ! * BRANCH_COST: Costs. (line 105) ! * break_out_memory_refs: Addressing Modes. (line 135) * BREAK_STMT: Statements for C++. (line 6) ! * BSS_SECTION_ASM_OP: Sections. (line 68) * bswap: Arithmetic. (line 246) ! * bswapM2 instruction pattern: Standard Names. (line 605) ! * btruncM2 instruction pattern: Standard Names. (line 813) * build0: Macros and Functions. (line 16) * build1: Macros and Functions. *************** Concept Index *** 47573,47604 **** (line 21) * build6: Macros and Functions. (line 22) ! * builtin_longjmp instruction pattern: Standard Names. (line 1692) * builtin_setjmp_receiver instruction pattern: Standard Names. ! (line 1682) ! * builtin_setjmp_setup instruction pattern: Standard Names. (line 1671) ! * BYTES_BIG_ENDIAN: Storage Layout. (line 23) ! * BYTES_BIG_ENDIAN, effect on subreg: Regs and Memory. (line 219) ! * byte_mode: Machine Modes. (line 367) * C statements for assembler output: Output Statement. (line 6) ! * cache: GTY Options. (line 125) ! * call: Flags. (line 221) * call <1>: Side Effects. (line 92) ! * call instruction pattern: Standard Names. (line 1337) * call usage: Calls. (line 10) * call, in call_insn: Flags. (line 33) * call, in mem: Flags. (line 81) * call-clobbered register: Register Basics. (line 35) - * call-clobbered register <1>: Register Basics. (line 46) - * call-clobbered register <2>: Register Basics. (line 53) * call-saved register: Register Basics. (line 35) - * call-saved register <1>: Register Basics. (line 46) - * call-saved register <2>: Register Basics. (line 53) * call-used register: Register Basics. (line 35) - * call-used register <1>: Register Basics. (line 46) - * call-used register <2>: Register Basics. (line 53) - * calling conventions: Stack and Calling. (line 6) - * calling functions in RTL: Calls. (line 6) * CALL_EXPR: Unary and Binary Expressions. (line 6) * call_insn: Insns. (line 95) --- 48046,48072 ---- (line 21) * build6: Macros and Functions. (line 22) ! * builtin_longjmp instruction pattern: Standard Names. (line 1703) * builtin_setjmp_receiver instruction pattern: Standard Names. ! (line 1693) ! * builtin_setjmp_setup instruction pattern: Standard Names. (line 1682) ! * byte_mode: Machine Modes. (line 368) ! * BYTES_BIG_ENDIAN: Storage Layout. (line 24) ! * BYTES_BIG_ENDIAN, effect on subreg: Regs and Memory. (line 221) * C statements for assembler output: Output Statement. (line 6) ! * C_COMMON_OVERRIDE_OPTIONS: Run-time Target. (line 137) ! * c_register_pragma: Misc. (line 410) ! * c_register_pragma_with_expansion: Misc. (line 412) ! * cache: GTY Options. (line 124) * call <1>: Side Effects. (line 92) ! * call: Flags. (line 221) ! * call instruction pattern: Standard Names. (line 1343) * call usage: Calls. (line 10) * call, in call_insn: Flags. (line 33) * call, in mem: Flags. (line 81) * call-clobbered register: Register Basics. (line 35) * call-saved register: Register Basics. (line 35) * call-used register: Register Basics. (line 35) * CALL_EXPR: Unary and Binary Expressions. (line 6) * call_insn: Insns. (line 95) *************** Concept Index *** 47607,47731 **** * call_insn and /i: Flags. (line 24) * call_insn and /j: Flags. (line 161) * call_insn and /s: Flags. (line 49) - * call_insn and /s <1>: Flags. (line 148) * call_insn and /u: Flags. (line 19) - * call_insn and /u <1>: Flags. (line 39) * call_insn and /u or /i: Flags. (line 29) * call_insn and /v: Flags. (line 44) * CALL_INSN_FUNCTION_USAGE: Insns. (line 101) ! * call_pop instruction pattern: Standard Names. (line 1365) ! * CALL_POPS_ARGS: Stack Arguments. (line 138) ! * CALL_REALLY_USED_REGISTERS: Register Basics. (line 45) ! * CALL_USED_REGISTERS: Register Basics. (line 34) * call_used_regs: Register Basics. (line 59) ! * call_value instruction pattern: Standard Names. (line 1357) ! * call_value_pop instruction pattern: Standard Names. (line 1365) * canadian: Configure Terms. (line 6) ! * CANNOT_CHANGE_MODE_CLASS: Register Classes. (line 533) * CANNOT_CHANGE_MODE_CLASS and subreg semantics: Regs and Memory. ! (line 276) * canonicalization of instructions: Insn Canonicalizations. (line 6) * canonicalize_funcptr_for_compare instruction pattern: Standard Names. ! (line 1526) ! * can_create_pseudo_p: Standard Names. (line 75) ! * can_fallthru: Basic Blocks. (line 67) * caret: Multi-Alternative. (line 53) ! * casesi instruction pattern: Standard Names. (line 1458) ! * CASE_VECTOR_MODE: Misc. (line 26) ! * CASE_VECTOR_PC_RELATIVE: Misc. (line 39) ! * CASE_VECTOR_SHORTEN_MODE: Misc. (line 30) ! * cbranchMODE4 instruction pattern: Standard Names. (line 1326) ! * cc0: Regs and Memory. (line 303) * cc0 <1>: CC0 Condition Codes. (line 6) * cc0, RTL sharing: Sharing. (line 27) ! * cc0_rtx: Regs and Memory. (line 329) ! * CC1PLUS_SPEC: Driver. (line 63) ! * CC1_SPEC: Driver. (line 55) ! * CCmode: Machine Modes. (line 178) ! * CCmode <1>: MODE_CC Condition Codes. ! (line 6) * cc_status: CC0 Condition Codes. (line 6) * CC_STATUS_MDEP: CC0 Condition Codes. ! (line 16) * CC_STATUS_MDEP_INIT: CC0 Condition Codes. ! (line 22) ! * CDImode: Machine Modes. (line 204) ! * ceilM2 instruction pattern: Standard Names. (line 822) * CEIL_DIV_EXPR: Unary and Binary Expressions. (line 6) * CEIL_MOD_EXPR: Unary and Binary Expressions. (line 6) ! * CFA_FRAME_BASE_OFFSET: Frame Layout. (line 222) * CFG verification: Maintaining the CFG. ! (line 117) * CFG, Control Flow Graph: Control Flow. (line 6) * cfghooks.h: Maintaining the CFG. (line 6) ! * cgraph_finalize_function: Parsing pass. (line 51) ! * chain_circular: GTY Options. (line 158) ! * chain_next: GTY Options. (line 158) ! * chain_prev: GTY Options. (line 158) * change_address: Standard Names. (line 47) ! * CHAR_TYPE_SIZE: Type Layout. (line 38) ! * check_stack instruction pattern: Standard Names. (line 1612) ! * CHImode: Machine Modes. (line 204) * CILK_PLUS: Cilk Plus Transformation. (line 6) * class definitions, register: Register Classes. (line 6) * class preference constraints: Class Preferences. (line 6) * class, scope: Classes. (line 6) * classes of RTX codes: RTL Classes. (line 6) * CLASSTYPE_DECLARED_CLASS: Classes. (line 6) * CLASSTYPE_HAS_MUTABLE: Classes. (line 85) * CLASSTYPE_NON_POD_P: Classes. (line 90) - * CLASS_MAX_NREGS: Register Classes. (line 521) - * CLASS_TYPE_P: Types for C++. (line 63) - * Cleanups: Cleanups. (line 6) * CLEANUP_DECL: Statements for C++. (line 6) * CLEANUP_EXPR: Statements for C++. (line 6) * CLEANUP_POINT_EXPR: Unary and Binary Expressions. (line 6) * CLEANUP_STMT: Statements for C++. (line 6) ! * clear_cache instruction pattern: Standard Names. (line 2102) ! * CLEAR_INSN_CACHE: Trampolines. (line 98) ! * CLEAR_RATIO: Costs. (line 204) * clobber: Side Effects. (line 106) * clrsb: Arithmetic. (line 215) ! * clrsbM2 instruction pattern: Standard Names. (line 885) * clz: Arithmetic. (line 222) ! * clzM2 instruction pattern: Standard Names. (line 901) ! * CLZ_DEFINED_VALUE_AT_ZERO: Misc. (line 304) ! * cmpmemM instruction pattern: Standard Names. (line 1066) ! * cmpstrM instruction pattern: Standard Names. (line 1045) ! * cmpstrnM instruction pattern: Standard Names. (line 1032) * code generation RTL sequences: Expander Definitions. (line 6) * code iterators in .md files: Code Iterators. (line 6) - * codes, RTL expression: RTL Objects. (line 47) - * code_label: Insns. (line 125) * CODE_LABEL: Basic Blocks. (line 50) * code_label and /i: Flags. (line 59) * code_label and /v: Flags. (line 44) * CODE_LABEL_NUMBER: Insns. (line 125) ! * COImode: Machine Modes. (line 204) * COLLECT2_HOST_INITIALIZATION: Host Misc. (line 32) ! * COLLECT_EXPORT_LIST: Misc. (line 867) * COLLECT_SHARED_FINI_FUNC: Macros for Initialization. ! (line 43) * COLLECT_SHARED_INIT_FUNC: Macros for Initialization. ! (line 32) * commit_edge_insertions: Maintaining the CFG. ! (line 105) ! * compare: Arithmetic. (line 46) * compare, canonicalization of: Insn Canonicalizations. ! (line 36) * comparison_operator: Machine-Independent Predicates. ! (line 110) * compiler passes and files: Passes. (line 6) ! * complement, bitwise: Arithmetic. (line 154) * COMPLEX_CST: Constant expressions. (line 6) * COMPLEX_EXPR: Unary and Binary Expressions. --- 48075,48199 ---- * call_insn and /i: Flags. (line 24) * call_insn and /j: Flags. (line 161) * call_insn and /s: Flags. (line 49) * call_insn and /u: Flags. (line 19) * call_insn and /u or /i: Flags. (line 29) * call_insn and /v: Flags. (line 44) * CALL_INSN_FUNCTION_USAGE: Insns. (line 101) ! * call_pop instruction pattern: Standard Names. (line 1371) ! * CALL_POPS_ARGS: Stack Arguments. (line 139) ! * CALL_REALLY_USED_REGISTERS: Register Basics. (line 46) ! * CALL_USED_REGISTERS: Register Basics. (line 35) * call_used_regs: Register Basics. (line 59) ! * call_value instruction pattern: Standard Names. (line 1363) ! * call_value_pop instruction pattern: Standard Names. (line 1371) ! * calling conventions: Stack and Calling. (line 6) ! * calling functions in RTL: Calls. (line 6) ! * can_create_pseudo_p: Standard Names. (line 75) ! * can_fallthru: Basic Blocks. (line 67) * canadian: Configure Terms. (line 6) ! * CANNOT_CHANGE_MODE_CLASS: Register Classes. (line 538) * CANNOT_CHANGE_MODE_CLASS and subreg semantics: Regs and Memory. ! (line 280) * canonicalization of instructions: Insn Canonicalizations. (line 6) * canonicalize_funcptr_for_compare instruction pattern: Standard Names. ! (line 1534) * caret: Multi-Alternative. (line 53) ! * CASE_VECTOR_MODE: Misc. (line 27) ! * CASE_VECTOR_PC_RELATIVE: Misc. (line 40) ! * CASE_VECTOR_SHORTEN_MODE: Misc. (line 31) ! * casesi instruction pattern: Standard Names. (line 1465) ! * cbranchMODE4 instruction pattern: Standard Names. (line 1332) * cc0 <1>: CC0 Condition Codes. (line 6) + * cc0: Regs and Memory. (line 307) * cc0, RTL sharing: Sharing. (line 27) ! * cc0_rtx: Regs and Memory. (line 333) ! * CC1_SPEC: Driver. (line 56) ! * CC1PLUS_SPEC: Driver. (line 64) * cc_status: CC0 Condition Codes. (line 6) * CC_STATUS_MDEP: CC0 Condition Codes. ! (line 17) * CC_STATUS_MDEP_INIT: CC0 Condition Codes. ! (line 23) ! * CCmode <1>: MODE_CC Condition Codes. ! (line 6) ! * CCmode: Machine Modes. (line 179) ! * CDImode: Machine Modes. (line 205) * CEIL_DIV_EXPR: Unary and Binary Expressions. (line 6) * CEIL_MOD_EXPR: Unary and Binary Expressions. (line 6) ! * ceilM2 instruction pattern: Standard Names. (line 828) ! * CFA_FRAME_BASE_OFFSET: Frame Layout. (line 224) * CFG verification: Maintaining the CFG. ! (line 119) * CFG, Control Flow Graph: Control Flow. (line 6) * cfghooks.h: Maintaining the CFG. (line 6) ! * cgraph_finalize_function: Parsing pass. (line 52) ! * chain_circular: GTY Options. (line 154) ! * chain_next: GTY Options. (line 154) ! * chain_prev: GTY Options. (line 154) * change_address: Standard Names. (line 47) ! * CHAR_TYPE_SIZE: Type Layout. (line 39) ! * check_stack instruction pattern: Standard Names. (line 1621) ! * CHImode: Machine Modes. (line 205) * CILK_PLUS: Cilk Plus Transformation. (line 6) * class definitions, register: Register Classes. (line 6) * class preference constraints: Class Preferences. (line 6) * class, scope: Classes. (line 6) + * CLASS_MAX_NREGS: Register Classes. (line 526) + * CLASS_TYPE_P: Types for C++. (line 65) * classes of RTX codes: RTL Classes. (line 6) * CLASSTYPE_DECLARED_CLASS: Classes. (line 6) * CLASSTYPE_HAS_MUTABLE: Classes. (line 85) * CLASSTYPE_NON_POD_P: Classes. (line 90) * CLEANUP_DECL: Statements for C++. (line 6) * CLEANUP_EXPR: Statements for C++. (line 6) * CLEANUP_POINT_EXPR: Unary and Binary Expressions. (line 6) * CLEANUP_STMT: Statements for C++. (line 6) ! * Cleanups: Cleanups. (line 6) ! * clear_cache instruction pattern: Standard Names. (line 2113) ! * CLEAR_INSN_CACHE: Trampolines. (line 99) ! * CLEAR_RATIO: Costs. (line 205) * clobber: Side Effects. (line 106) * clrsb: Arithmetic. (line 215) ! * clrsbM2 instruction pattern: Standard Names. (line 891) * clz: Arithmetic. (line 222) ! * CLZ_DEFINED_VALUE_AT_ZERO: Misc. (line 305) ! * clzM2 instruction pattern: Standard Names. (line 907) ! * cmpmemM instruction pattern: Standard Names. (line 1072) ! * cmpstrM instruction pattern: Standard Names. (line 1051) ! * cmpstrnM instruction pattern: Standard Names. (line 1038) * code generation RTL sequences: Expander Definitions. (line 6) * code iterators in .md files: Code Iterators. (line 6) * CODE_LABEL: Basic Blocks. (line 50) + * code_label: Insns. (line 125) * code_label and /i: Flags. (line 59) * code_label and /v: Flags. (line 44) * CODE_LABEL_NUMBER: Insns. (line 125) ! * codes, RTL expression: RTL Objects. (line 47) ! * COImode: Machine Modes. (line 205) * COLLECT2_HOST_INITIALIZATION: Host Misc. (line 32) ! * COLLECT_EXPORT_LIST: Misc. (line 871) * COLLECT_SHARED_FINI_FUNC: Macros for Initialization. ! (line 44) * COLLECT_SHARED_INIT_FUNC: Macros for Initialization. ! (line 33) * commit_edge_insertions: Maintaining the CFG. ! (line 107) ! * compare: Arithmetic. (line 43) * compare, canonicalization of: Insn Canonicalizations. ! (line 37) * comparison_operator: Machine-Independent Predicates. ! (line 111) * compiler passes and files: Passes. (line 6) ! * complement, bitwise: Arithmetic. (line 153) * COMPLEX_CST: Constant expressions. (line 6) * COMPLEX_EXPR: Unary and Binary Expressions. *************** Concept Index *** 47740,47755 **** * COMPOUND_LITERAL_EXPR: Unary and Binary Expressions. (line 6) * COMPOUND_LITERAL_EXPR_DECL: Unary and Binary Expressions. ! (line 377) * COMPOUND_LITERAL_EXPR_DECL_EXPR: Unary and Binary Expressions. ! (line 377) ! * computed jump: Edges. (line 127) * computing the length of an insn: Insn Lengths. (line 6) ! * concat: Regs and Memory. (line 381) ! * concatn: Regs and Memory. (line 387) * cond: Comparisons. (line 90) * cond and attributes: Expressions. (line 37) ! * condition code register: Regs and Memory. (line 303) * condition code status: Condition Code. (line 6) * condition codes: Comparisons. (line 20) * conditional execution: Conditional Execution. --- 48208,48226 ---- * COMPOUND_LITERAL_EXPR: Unary and Binary Expressions. (line 6) * COMPOUND_LITERAL_EXPR_DECL: Unary and Binary Expressions. ! (line 378) * COMPOUND_LITERAL_EXPR_DECL_EXPR: Unary and Binary Expressions. ! (line 378) ! * computed jump: Edges. (line 128) * computing the length of an insn: Insn Lengths. (line 6) ! * concat: Regs and Memory. (line 385) ! * concatn: Regs and Memory. (line 391) * cond: Comparisons. (line 90) * cond and attributes: Expressions. (line 37) ! * cond_exec: Side Effects. (line 254) ! * COND_EXPR: Unary and Binary Expressions. ! (line 6) ! * condition code register: Regs and Memory. (line 307) * condition code status: Condition Code. (line 6) * condition codes: Comparisons. (line 20) * conditional execution: Conditional Execution. *************** Concept Index *** 47757,47817 **** * Conditional Expressions: Conditional Expressions. (line 6) * conditions, in patterns: Patterns. (line 43) - * cond_exec: Side Effects. (line 254) - * COND_EXPR: Unary and Binary Expressions. - (line 6) - * configuration file: Filesystem. (line 6) * configuration file <1>: Host Misc. (line 6) * configure terms: Configure Terms. (line 6) * CONJ_EXPR: Unary and Binary Expressions. (line 6) * const: Constants. (line 140) - * const0_rtx: Constants. (line 21) * CONST0_RTX: Constants. (line 160) ! * const1_rtx: Constants. (line 21) * CONST1_RTX: Constants. (line 160) ! * const2_rtx: Constants. (line 21) * CONST2_RTX: Constants. (line 160) ! * constant attributes: Constant Attributes. ! (line 6) ! * constant definitions: Constant Definitions. ! (line 6) ! * constants in constraints: Simple Constraints. (line 68) ! * CONSTANT_ADDRESS_P: Addressing Modes. (line 28) ! * CONSTANT_ALIGNMENT: Storage Layout. (line 241) ! * CONSTANT_P: Addressing Modes. (line 35) ! * CONSTANT_POOL_ADDRESS_P: Flags. (line 10) ! * CONSTANT_POOL_BEFORE_FUNCTION: Data Output. (line 68) ! * constm1_rtx: Constants. (line 21) ! * constraint modifier characters: Modifiers. (line 6) ! * constraint, matching: Simple Constraints. (line 140) ! * constraints: Constraints. (line 6) ! * constraints, defining: Define Constraints. (line 6) ! * constraints, machine specific: Machine Constraints. ! (line 6) ! * constraints, testing: C Constraint Interface. ! (line 6) ! * constraint_num: C Constraint Interface. ! (line 30) ! * constraint_satisfied_p: C Constraint Interface. ! (line 42) ! * CONSTRUCTOR: Unary and Binary Expressions. ! (line 6) ! * constructors, automatic calls: Collect2. (line 15) ! * constructors, output of: Initialization. (line 6) * CONST_DECL: Declarations. (line 6) * const_double: Constants. (line 37) * const_double, RTL sharing: Sharing. (line 29) * CONST_DOUBLE_LOW: Constants. (line 54) * const_double_operand: Machine-Independent Predicates. ! (line 20) * const_fixed: Constants. (line 93) * const_int: Constants. (line 8) * const_int and attribute tests: Expressions. (line 47) * const_int and attributes: Expressions. (line 10) * const_int, RTL sharing: Sharing. (line 23) * const_int_operand: Machine-Independent Predicates. ! (line 15) * const_string: Constants. (line 112) * const_string and attributes: Expressions. (line 20) * const_true_rtx: Constants. (line 31) --- 48228,48258 ---- * Conditional Expressions: Conditional Expressions. (line 6) * conditions, in patterns: Patterns. (line 43) * configuration file <1>: Host Misc. (line 6) + * configuration file: Filesystem. (line 6) * configure terms: Configure Terms. (line 6) * CONJ_EXPR: Unary and Binary Expressions. (line 6) * const: Constants. (line 140) * CONST0_RTX: Constants. (line 160) ! * const0_rtx: Constants. (line 21) * CONST1_RTX: Constants. (line 160) ! * const1_rtx: Constants. (line 21) * CONST2_RTX: Constants. (line 160) ! * const2_rtx: Constants. (line 21) * CONST_DECL: Declarations. (line 6) * const_double: Constants. (line 37) * const_double, RTL sharing: Sharing. (line 29) * CONST_DOUBLE_LOW: Constants. (line 54) * const_double_operand: Machine-Independent Predicates. ! (line 21) * const_fixed: Constants. (line 93) * const_int: Constants. (line 8) * const_int and attribute tests: Expressions. (line 47) * const_int and attributes: Expressions. (line 10) * const_int, RTL sharing: Sharing. (line 23) * const_int_operand: Machine-Independent Predicates. ! (line 16) * const_string: Constants. (line 112) * const_string and attributes: Expressions. (line 20) * const_true_rtx: Constants. (line 31) *************** Concept Index *** 47821,47826 **** --- 48262,48294 ---- * CONST_WIDE_INT_ELT: Constants. (line 89) * CONST_WIDE_INT_NUNITS: Constants. (line 84) * CONST_WIDE_INT_VEC: Constants. (line 80) + * constant attributes: Constant Attributes. + (line 6) + * constant definitions: Constant Definitions. + (line 6) + * CONSTANT_ADDRESS_P: Addressing Modes. (line 29) + * CONSTANT_ALIGNMENT: Storage Layout. (line 245) + * CONSTANT_P: Addressing Modes. (line 36) + * CONSTANT_POOL_ADDRESS_P: Flags. (line 10) + * CONSTANT_POOL_BEFORE_FUNCTION: Data Output. (line 69) + * constants in constraints: Simple Constraints. (line 70) + * constm1_rtx: Constants. (line 21) + * constraint modifier characters: Modifiers. (line 6) + * constraint, matching: Simple Constraints. (line 142) + * constraint_num: C Constraint Interface. + (line 31) + * constraint_satisfied_p: C Constraint Interface. + (line 44) + * constraints: Constraints. (line 6) + * constraints, defining: Define Constraints. (line 6) + * constraints, machine specific: Machine Constraints. + (line 6) + * constraints, testing: C Constraint Interface. + (line 6) + * CONSTRUCTOR: Unary and Binary Expressions. + (line 6) + * constructors, automatic calls: Collect2. (line 15) + * constructors, output of: Initialization. (line 6) * container: Containers. (line 6) * CONTINUE_STMT: Statements for C++. (line 6) * contributors: Contributors. (line 6) *************** Concept Index *** 47830,47972 **** * conversions: Conversions. (line 6) * CONVERT_EXPR: Unary and Binary Expressions. (line 6) ! * copysignM3 instruction pattern: Standard Names. (line 865) ! * copy_rtx: Addressing Modes. (line 189) * copy_rtx_if_shared: Sharing. (line 64) ! * cosM2 instruction pattern: Standard Names. (line 662) * costs of instructions: Costs. (line 6) ! * CPLUSPLUS_CPP_SPEC: Driver. (line 50) ! * CPP_SPEC: Driver. (line 43) ! * CP_INTEGRAL_TYPE: Types for C++. (line 55) * cp_namespace_decls: Namespaces. (line 49) * CP_TYPE_CONST_NON_VOLATILE_P: Types for C++. (line 33) * CP_TYPE_CONST_P: Types for C++. (line 24) * cp_type_quals: Types for C++. (line 6) - * cp_type_quals <1>: Types for C++. (line 16) * CP_TYPE_RESTRICT_P: Types for C++. (line 30) * CP_TYPE_VOLATILE_P: Types for C++. (line 27) ! * CQImode: Machine Modes. (line 204) * cross compilation and floating point: Floating Point. (line 6) ! * crtl->args.pops_args: Function Entry. (line 104) ! * crtl->args.pretend_args_size: Function Entry. (line 110) * crtl->outgoing_args_size: Stack Arguments. (line 48) * CRTSTUFF_T_CFLAGS: Target Fragment. (line 15) * CRTSTUFF_T_CFLAGS_S: Target Fragment. (line 19) ! * CRT_CALL_STATIC_FUNCTION: Sections. (line 120) ! * CSImode: Machine Modes. (line 204) ! * cstoreMODE4 instruction pattern: Standard Names. (line 1287) ! * CTImode: Machine Modes. (line 204) ! * ctrapMM4 instruction pattern: Standard Names. (line 1764) * ctz: Arithmetic. (line 230) ! * ctzM2 instruction pattern: Standard Names. (line 916) ! * CTZ_DEFINED_VALUE_AT_ZERO: Misc. (line 305) ! * CUMULATIVE_ARGS: Register Arguments. (line 140) ! * current_function_is_leaf: Leaf Functions. (line 50) ! * current_function_uses_only_leaf_regs: Leaf Functions. (line 50) * current_insn_predicate: Conditional Execution. (line 27) ! * C_COMMON_OVERRIDE_OPTIONS: Run-time Target. (line 136) ! * c_register_pragma: Misc. (line 407) ! * c_register_pragma_with_expansion: Misc. (line 409) ! * DAmode: Machine Modes. (line 154) * data bypass: Processor pipeline description. ! (line 105) ! * data bypass <1>: Processor pipeline description. ! (line 196) * data dependence delays: Processor pipeline description. (line 6) * Data Dependency Analysis: Dependency analysis. (line 6) * data structures: Per-Function Data. (line 6) ! * DATA_ABI_ALIGNMENT: Storage Layout. (line 233) ! * DATA_ALIGNMENT: Storage Layout. (line 220) ! * DATA_SECTION_ASM_OP: Sections. (line 52) ! * DBR_OUTPUT_SEQEND: Instruction Output. (line 133) ! * dbr_sequence_length: Instruction Output. (line 133) ! * DBX_BLOCKS_FUNCTION_RELATIVE: DBX Options. (line 100) ! * DBX_CONTIN_CHAR: DBX Options. (line 63) ! * DBX_CONTIN_LENGTH: DBX Options. (line 53) ! * DBX_DEBUGGING_INFO: DBX Options. (line 8) ! * DBX_FUNCTION_FIRST: DBX Options. (line 94) ! * DBX_LINES_FUNCTION_RELATIVE: DBX Options. (line 106) ! * DBX_NO_XREFS: DBX Options. (line 47) ! * DBX_OUTPUT_MAIN_SOURCE_FILENAME: File Names and DBX. (line 8) ! * DBX_OUTPUT_MAIN_SOURCE_FILE_END: File Names and DBX. (line 33) * DBX_OUTPUT_NULL_N_SO_AT_MAIN_SOURCE_FILE_END: File Names and DBX. ! (line 41) ! * DBX_OUTPUT_SOURCE_LINE: DBX Hooks. (line 8) ! * DBX_REGISTER_NUMBER: All Debuggers. (line 8) ! * DBX_REGPARM_STABS_CODE: DBX Options. (line 84) ! * DBX_REGPARM_STABS_LETTER: DBX Options. (line 89) ! * DBX_STATIC_CONST_VAR_CODE: DBX Options. (line 79) ! * DBX_STATIC_STAB_DATA_SECTION: DBX Options. (line 70) ! * DBX_TYPE_DECL_STABS_CODE: DBX Options. (line 75) ! * DBX_USE_BINCL: DBX Options. (line 112) ! * DCmode: Machine Modes. (line 199) * DDmode: Machine Modes. (line 93) * De Morgan's law: Insn Canonicalizations. ! (line 51) * dead_or_set_p: define_peephole. (line 65) - * DEBUGGER_ARG_OFFSET: All Debuggers. (line 36) - * DEBUGGER_AUTO_OFFSET: All Debuggers. (line 27) * debug_expr: Debug Information. (line 22) * DEBUG_EXPR_DECL: Declarations. (line 6) ! * debug_insn: Insns. (line 236) ! * DEBUG_SYMS_TEXT: DBX Options. (line 24) * decimal float library: Decimal float library routines. (line 6) - * declaration: Declarations. (line 6) - * declarations, RTL: RTL Declarations. (line 6) - * DECLARE_LIBRARY_RENAMES: Library Calls. (line 8) * DECL_ALIGN: Declarations. (line 6) * DECL_ANTICIPATED: Functions for C++. (line 42) * DECL_ARGUMENTS: Function Basics. (line 36) * DECL_ARRAY_DELETE_OPERATOR_P: Functions for C++. (line 158) * DECL_ARTIFICIAL: Working with declarations. (line 24) - * DECL_ARTIFICIAL <1>: Function Basics. (line 6) - * DECL_ARTIFICIAL <2>: Function Properties. - (line 47) * DECL_ASSEMBLER_NAME: Function Basics. (line 6) ! * DECL_ASSEMBLER_NAME <1>: Function Basics. (line 19) ! * DECL_ATTRIBUTES: Attributes. (line 21) * DECL_BASE_CONSTRUCTOR_P: Functions for C++. (line 88) * DECL_COMPLETE_CONSTRUCTOR_P: Functions for C++. (line 84) * DECL_COMPLETE_DESTRUCTOR_P: Functions for C++. (line 98) - * DECL_CONSTRUCTOR_P: Functions for C++. (line 77) * DECL_CONST_MEMFUNC_P: Functions for C++. (line 71) * DECL_CONTEXT: Namespaces. (line 31) * DECL_CONV_FN_P: Functions for C++. (line 105) * DECL_COPY_CONSTRUCTOR_P: Functions for C++. (line 92) * DECL_DESTRUCTOR_P: Functions for C++. (line 95) ! * DECL_EXTERNAL: Declarations. (line 6) * DECL_EXTERNAL <1>: Function Properties. (line 25) ! * DECL_EXTERN_C_FUNCTION_P: Functions for C++. (line 46) * DECL_FUNCTION_MEMBER_P: Functions for C++. (line 61) - * DECL_FUNCTION_SPECIFIC_OPTIMIZATION: Function Basics. (line 6) * DECL_FUNCTION_SPECIFIC_OPTIMIZATION <1>: Function Properties. (line 61) ! * DECL_FUNCTION_SPECIFIC_TARGET: Function Basics. (line 6) * DECL_FUNCTION_SPECIFIC_TARGET <1>: Function Properties. (line 55) * DECL_GLOBAL_CTOR_P: Functions for C++. (line 108) * DECL_GLOBAL_DTOR_P: Functions for C++. (line 112) - * DECL_INITIAL: Declarations. (line 6) * DECL_INITIAL <1>: Function Basics. (line 51) * DECL_LINKONCE_P: Functions for C++. (line 50) * DECL_LOCAL_FUNCTION_P: Functions for C++. (line 38) * DECL_MAIN_P: Functions for C++. (line 34) * DECL_NAME: Working with declarations. (line 7) - * DECL_NAME <1>: Function Basics. (line 6) - * DECL_NAME <2>: Function Basics. (line 9) - * DECL_NAME <3>: Namespaces. (line 20) * DECL_NAMESPACE_ALIAS: Namespaces. (line 35) * DECL_NAMESPACE_STD_P: Namespaces. (line 45) * DECL_NONCONVERTING_P: Functions for C++. (line 80) * DECL_NONSTATIC_MEMBER_FUNCTION_P: Functions for C++. (line 68) - * DECL_NON_THUNK_FUNCTION_P: Functions for C++. (line 138) * DECL_OVERLOADED_OPERATOR_P: Functions for C++. (line 102) * DECL_PURE_P: Function Properties. (line 40) --- 48298,48429 ---- * conversions: Conversions. (line 6) * CONVERT_EXPR: Unary and Binary Expressions. (line 6) ! * copy_rtx: Addressing Modes. (line 190) * copy_rtx_if_shared: Sharing. (line 64) ! * copysignM3 instruction pattern: Standard Names. (line 871) ! * cosM2 instruction pattern: Standard Names. (line 668) * costs of instructions: Costs. (line 6) ! * CP_INTEGRAL_TYPE: Types for C++. (line 57) * cp_namespace_decls: Namespaces. (line 49) * CP_TYPE_CONST_NON_VOLATILE_P: Types for C++. (line 33) * CP_TYPE_CONST_P: Types for C++. (line 24) * cp_type_quals: Types for C++. (line 6) * CP_TYPE_RESTRICT_P: Types for C++. (line 30) * CP_TYPE_VOLATILE_P: Types for C++. (line 27) ! * CPLUSPLUS_CPP_SPEC: Driver. (line 51) ! * CPP_SPEC: Driver. (line 44) ! * CQImode: Machine Modes. (line 205) * cross compilation and floating point: Floating Point. (line 6) ! * CRT_CALL_STATIC_FUNCTION: Sections. (line 121) ! * crtl->args.pops_args: Function Entry. (line 106) ! * crtl->args.pretend_args_size: Function Entry. (line 112) * crtl->outgoing_args_size: Stack Arguments. (line 48) * CRTSTUFF_T_CFLAGS: Target Fragment. (line 15) * CRTSTUFF_T_CFLAGS_S: Target Fragment. (line 19) ! * CSImode: Machine Modes. (line 205) ! * cstoreMODE4 instruction pattern: Standard Names. (line 1293) ! * CTImode: Machine Modes. (line 205) ! * ctrapMM4 instruction pattern: Standard Names. (line 1775) * ctz: Arithmetic. (line 230) ! * CTZ_DEFINED_VALUE_AT_ZERO: Misc. (line 306) ! * ctzM2 instruction pattern: Standard Names. (line 922) ! * CUMULATIVE_ARGS: Register Arguments. (line 142) ! * current_function_is_leaf: Leaf Functions. (line 51) ! * current_function_uses_only_leaf_regs: Leaf Functions. (line 51) * current_insn_predicate: Conditional Execution. (line 27) ! * DAmode: Machine Modes. (line 155) * data bypass: Processor pipeline description. ! (line 106) * data dependence delays: Processor pipeline description. (line 6) * Data Dependency Analysis: Dependency analysis. (line 6) * data structures: Per-Function Data. (line 6) ! * DATA_ABI_ALIGNMENT: Storage Layout. (line 237) ! * DATA_ALIGNMENT: Storage Layout. (line 224) ! * DATA_SECTION_ASM_OP: Sections. (line 53) ! * DBR_OUTPUT_SEQEND: Instruction Output. (line 135) ! * dbr_sequence_length: Instruction Output. (line 134) ! * DBX_BLOCKS_FUNCTION_RELATIVE: DBX Options. (line 103) ! * DBX_CONTIN_CHAR: DBX Options. (line 66) ! * DBX_CONTIN_LENGTH: DBX Options. (line 56) ! * DBX_DEBUGGING_INFO: DBX Options. (line 9) ! * DBX_FUNCTION_FIRST: DBX Options. (line 97) ! * DBX_LINES_FUNCTION_RELATIVE: DBX Options. (line 109) ! * DBX_NO_XREFS: DBX Options. (line 50) ! * DBX_OUTPUT_MAIN_SOURCE_FILE_END: File Names and DBX. (line 34) ! * DBX_OUTPUT_MAIN_SOURCE_FILENAME: File Names and DBX. (line 9) * DBX_OUTPUT_NULL_N_SO_AT_MAIN_SOURCE_FILE_END: File Names and DBX. ! (line 42) ! * DBX_OUTPUT_SOURCE_LINE: DBX Hooks. (line 9) ! * DBX_REGISTER_NUMBER: All Debuggers. (line 9) ! * DBX_REGPARM_STABS_CODE: DBX Options. (line 87) ! * DBX_REGPARM_STABS_LETTER: DBX Options. (line 92) ! * DBX_STATIC_CONST_VAR_CODE: DBX Options. (line 82) ! * DBX_STATIC_STAB_DATA_SECTION: DBX Options. (line 73) ! * DBX_TYPE_DECL_STABS_CODE: DBX Options. (line 78) ! * DBX_USE_BINCL: DBX Options. (line 115) ! * DCmode: Machine Modes. (line 200) * DDmode: Machine Modes. (line 93) * De Morgan's law: Insn Canonicalizations. ! (line 52) * dead_or_set_p: define_peephole. (line 65) * debug_expr: Debug Information. (line 22) * DEBUG_EXPR_DECL: Declarations. (line 6) ! * debug_insn: Insns. (line 239) ! * DEBUG_SYMS_TEXT: DBX Options. (line 25) ! * DEBUGGER_ARG_OFFSET: All Debuggers. (line 37) ! * DEBUGGER_AUTO_OFFSET: All Debuggers. (line 28) * decimal float library: Decimal float library routines. (line 6) * DECL_ALIGN: Declarations. (line 6) * DECL_ANTICIPATED: Functions for C++. (line 42) * DECL_ARGUMENTS: Function Basics. (line 36) * DECL_ARRAY_DELETE_OPERATOR_P: Functions for C++. (line 158) + * DECL_ARTIFICIAL <1>: Function Properties. + (line 47) + * DECL_ARTIFICIAL <2>: Function Basics. (line 6) * DECL_ARTIFICIAL: Working with declarations. (line 24) * DECL_ASSEMBLER_NAME: Function Basics. (line 6) ! * DECL_ATTRIBUTES: Attributes. (line 22) * DECL_BASE_CONSTRUCTOR_P: Functions for C++. (line 88) * DECL_COMPLETE_CONSTRUCTOR_P: Functions for C++. (line 84) * DECL_COMPLETE_DESTRUCTOR_P: Functions for C++. (line 98) * DECL_CONST_MEMFUNC_P: Functions for C++. (line 71) + * DECL_CONSTRUCTOR_P: Functions for C++. (line 77) * DECL_CONTEXT: Namespaces. (line 31) * DECL_CONV_FN_P: Functions for C++. (line 105) * DECL_COPY_CONSTRUCTOR_P: Functions for C++. (line 92) * DECL_DESTRUCTOR_P: Functions for C++. (line 95) ! * DECL_EXTERN_C_FUNCTION_P: Functions for C++. (line 46) * DECL_EXTERNAL <1>: Function Properties. (line 25) ! * DECL_EXTERNAL: Declarations. (line 6) * DECL_FUNCTION_MEMBER_P: Functions for C++. (line 61) * DECL_FUNCTION_SPECIFIC_OPTIMIZATION <1>: Function Properties. (line 61) ! * DECL_FUNCTION_SPECIFIC_OPTIMIZATION: Function Basics. (line 6) * DECL_FUNCTION_SPECIFIC_TARGET <1>: Function Properties. (line 55) + * DECL_FUNCTION_SPECIFIC_TARGET: Function Basics. (line 6) * DECL_GLOBAL_CTOR_P: Functions for C++. (line 108) * DECL_GLOBAL_DTOR_P: Functions for C++. (line 112) * DECL_INITIAL <1>: Function Basics. (line 51) + * DECL_INITIAL: Declarations. (line 6) * DECL_LINKONCE_P: Functions for C++. (line 50) * DECL_LOCAL_FUNCTION_P: Functions for C++. (line 38) * DECL_MAIN_P: Functions for C++. (line 34) + * DECL_NAME <1>: Namespaces. (line 20) + * DECL_NAME <2>: Function Basics. (line 6) * DECL_NAME: Working with declarations. (line 7) * DECL_NAMESPACE_ALIAS: Namespaces. (line 35) * DECL_NAMESPACE_STD_P: Namespaces. (line 45) + * DECL_NON_THUNK_FUNCTION_P: Functions for C++. (line 138) * DECL_NONCONVERTING_P: Functions for C++. (line 80) * DECL_NONSTATIC_MEMBER_FUNCTION_P: Functions for C++. (line 68) * DECL_OVERLOADED_OPERATOR_P: Functions for C++. (line 102) * DECL_PURE_P: Function Properties. (line 40) *************** Concept Index *** 47980,48028 **** * DECL_VIRTUAL_P: Function Properties. (line 44) * DECL_VOLATILE_MEMFUNC_P: Functions for C++. (line 74) * decrement_and_branch_until_zero instruction pattern: Standard Names. ! (line 1495) * default: GTY Options. (line 88) * default_file_start: File Framework. (line 8) ! * DEFAULT_GDB_EXTENSIONS: DBX Options. (line 17) ! * DEFAULT_PCC_STRUCT_RETURN: Aggregate Return. (line 34) ! * DEFAULT_SIGNED_CHAR: Type Layout. (line 123) ! * define_address_constraint: Define Constraints. (line 113) * define_asm_attributes: Tagging Insns. (line 73) * define_attr: Defining Attributes. (line 6) * define_automaton: Processor pipeline description. (line 53) * define_bypass: Processor pipeline description. ! (line 196) * define_code_attr: Code Iterators. (line 6) * define_code_iterator: Code Iterators. (line 6) * define_cond_exec: Conditional Execution. (line 13) * define_constants: Constant Definitions. (line 6) ! * define_constraint: Define Constraints. (line 45) * define_cpu_unit: Processor pipeline description. (line 68) - * define_c_enum: Constant Definitions. - (line 49) * define_delay: Delay Slots. (line 25) * define_enum: Constant Definitions. (line 118) - * define_enum_attr: Defining Attributes. - (line 83) * define_enum_attr <1>: Constant Definitions. (line 136) * define_expand: Expander Definitions. (line 11) * define_insn: Patterns. (line 6) * define_insn example: Example. (line 6) * define_insn_and_split: Insn Splitting. (line 170) * define_insn_reservation: Processor pipeline description. ! (line 105) * define_int_attr: Int Iterators. (line 6) * define_int_iterator: Int Iterators. (line 6) ! * define_memory_constraint: Define Constraints. (line 80) * define_mode_attr: Substitutions. (line 6) * define_mode_iterator: Defining Mode Iterators. (line 6) --- 48437,48488 ---- * DECL_VIRTUAL_P: Function Properties. (line 44) * DECL_VOLATILE_MEMFUNC_P: Functions for C++. (line 74) + * declaration: Declarations. (line 6) + * declarations, RTL: RTL Declarations. (line 6) + * DECLARE_LIBRARY_RENAMES: Library Calls. (line 9) * decrement_and_branch_until_zero instruction pattern: Standard Names. ! (line 1503) * default: GTY Options. (line 88) * default_file_start: File Framework. (line 8) ! * DEFAULT_GDB_EXTENSIONS: DBX Options. (line 18) ! * DEFAULT_PCC_STRUCT_RETURN: Aggregate Return. (line 35) ! * DEFAULT_SIGNED_CHAR: Type Layout. (line 124) ! * define_address_constraint: Define Constraints. (line 121) * define_asm_attributes: Tagging Insns. (line 73) * define_attr: Defining Attributes. (line 6) * define_automaton: Processor pipeline description. (line 53) * define_bypass: Processor pipeline description. ! (line 197) ! * define_c_enum: Constant Definitions. ! (line 49) * define_code_attr: Code Iterators. (line 6) * define_code_iterator: Code Iterators. (line 6) * define_cond_exec: Conditional Execution. (line 13) * define_constants: Constant Definitions. (line 6) ! * define_constraint: Define Constraints. (line 48) * define_cpu_unit: Processor pipeline description. (line 68) * define_delay: Delay Slots. (line 25) * define_enum: Constant Definitions. (line 118) * define_enum_attr <1>: Constant Definitions. (line 136) + * define_enum_attr: Defining Attributes. + (line 83) * define_expand: Expander Definitions. (line 11) * define_insn: Patterns. (line 6) * define_insn example: Example. (line 6) * define_insn_and_split: Insn Splitting. (line 170) * define_insn_reservation: Processor pipeline description. ! (line 106) * define_int_attr: Int Iterators. (line 6) * define_int_iterator: Int Iterators. (line 6) ! * define_memory_constraint: Define Constraints. (line 88) * define_mode_attr: Substitutions. (line 6) * define_mode_iterator: Defining Mode Iterators. (line 6) *************** Concept Index *** 48032,48055 **** (line 6) * define_query_cpu_unit: Processor pipeline description. (line 90) ! * define_register_constraint: Define Constraints. (line 26) * define_reservation: Processor pipeline description. ! (line 185) ! * define_special_memory_constraint: Define Constraints. (line 99) * define_special_predicate: Defining Predicates. (line 6) * define_split: Insn Splitting. (line 32) ! * define_subst: Define Subst. (line 6) ! * define_subst <1>: Define Subst Example. (line 6) ! * define_subst <2>: Define Subst Pattern Matching. (line 6) ! * define_subst <3>: Define Subst Output Template. (line 6) ! * define_subst <4>: Define Subst. (line 14) ! * define_subst <5>: Subst Iterators. (line 6) * define_subst_attr: Subst Iterators. (line 6) - * define_subst_attr <1>: Subst Iterators. (line 26) * defining attributes and their values: Defining Attributes. (line 6) * defining constraints: Define Constraints. (line 6) --- 48492,48513 ---- (line 6) * define_query_cpu_unit: Processor pipeline description. (line 90) ! * define_register_constraint: Define Constraints. (line 28) * define_reservation: Processor pipeline description. ! (line 186) ! * define_special_memory_constraint: Define Constraints. (line 107) * define_special_predicate: Defining Predicates. (line 6) * define_split: Insn Splitting. (line 32) ! * define_subst <1>: Subst Iterators. (line 6) ! * define_subst <2>: Define Subst Output Template. (line 6) ! * define_subst <3>: Define Subst Pattern Matching. (line 6) ! * define_subst <4>: Define Subst Example. (line 6) ! * define_subst: Define Subst. (line 6) * define_subst_attr: Subst Iterators. (line 6) * defining attributes and their values: Defining Attributes. (line 6) * defining constraints: Define Constraints. (line 6) *************** Concept Index *** 48062,48154 **** * defining RTL sequences for code generation: Expander Definitions. (line 6) * delay slots, defining: Delay Slots. (line 6) ! * deletable: GTY Options. (line 132) * DELETE_IF_ORDINARY: Filesystem. (line 79) * Dependent Patterns: Dependent Patterns. (line 6) * desc: GTY Options. (line 88) * destructors, output of: Initialization. (line 6) * deterministic finite state automaton: Processor pipeline description. (line 6) - * deterministic finite state automaton <1>: Processor pipeline description. - (line 304) * DFmode: Machine Modes. (line 76) ! * digits in constraint: Simple Constraints. (line 128) * DImode: Machine Modes. (line 45) - * directory options .md: Including Patterns. (line 47) * DIR_SEPARATOR: Filesystem. (line 18) * DIR_SEPARATOR_2: Filesystem. (line 19) * disabling certain registers: Register Basics. (line 73) * dispatch table: Dispatch Tables. (line 8) ! * div: Arithmetic. (line 116) ! * div and attributes: Expressions. (line 83) ! * division: Arithmetic. (line 116) ! * division <1>: Arithmetic. (line 130) ! * division <2>: Arithmetic. (line 136) ! * divM3 instruction pattern: Standard Names. (line 301) ! * divmodM4 instruction pattern: Standard Names. (line 559) * dollar sign: Multi-Alternative. (line 57) ! * DOLLARS_IN_IDENTIFIERS: Misc. (line 452) ! * doloop_begin instruction pattern: Standard Names. (line 1517) ! * doloop_end instruction pattern: Standard Names. (line 1505) * DONE: Expander Definitions. (line 77) * DONT_USE_BUILTIN_SETJMP: Exception Region Output. ! (line 78) ! * DOUBLE_TYPE_SIZE: Type Layout. (line 52) ! * DO_BODY: Statements for C++. (line 6) ! * DO_COND: Statements for C++. (line 6) ! * DO_STMT: Statements for C++. (line 6) * DQmode: Machine Modes. (line 118) * driver: Driver. (line 6) ! * DRIVER_SELF_SPECS: Driver. (line 8) * dump examples: Dump examples. (line 6) * dump setup: Dump setup. (line 6) * dump types: Dump types. (line 6) * dump verbosity: Dump output verbosity. (line 6) ! * DUMPFILE_FORMAT: Filesystem. (line 67) ! * dump_basic_block: Dump types. (line 29) ! * dump_generic_expr: Dump types. (line 31) ! * dump_gimple_stmt: Dump types. (line 33) * dump_printf: Dump types. (line 6) ! * DWARF2_ASM_LINE_DEBUG_INFO: SDB and DWARF. (line 49) ! * DWARF2_DEBUGGING_INFO: SDB and DWARF. (line 12) ! * DWARF2_FRAME_INFO: SDB and DWARF. (line 29) ! * DWARF2_FRAME_REG_OUT: Frame Registers. (line 151) * DWARF2_UNWIND_INFO: Exception Region Output. ! (line 39) ! * DWARF_ALT_FRAME_RETURN_COLUMN: Frame Layout. (line 148) * DWARF_CIE_DATA_ALIGNMENT: Exception Region Output. ! (line 90) ! * DWARF_FRAME_REGISTERS: Frame Registers. (line 109) ! * DWARF_FRAME_REGNUM: Frame Registers. (line 143) * DWARF_REG_TO_UNWIND_COLUMN: Frame Registers. (line 134) ! * DWARF_ZERO_REG: Frame Layout. (line 159) ! * DYNAMIC_CHAIN_ADDRESS: Frame Layout. (line 86) ! * E in constraint: Simple Constraints. (line 87) * earlyclobber operand: Modifiers. (line 25) * edge: Edges. (line 6) * edge in the flow graph: Edges. (line 6) * edge iterators: Edges. (line 15) * edge splitting: Maintaining the CFG. ! (line 105) ! * EDGE_ABNORMAL: Edges. (line 127) ! * EDGE_ABNORMAL, EDGE_ABNORMAL_CALL: Edges. (line 171) ! * EDGE_ABNORMAL, EDGE_EH: Edges. (line 95) ! * EDGE_ABNORMAL, EDGE_SIBCALL: Edges. (line 121) ! * EDGE_FALLTHRU, force_nonfallthru: Edges. (line 85) * EDOM, implicit usage: Library Calls. (line 59) * EH_FRAME_SECTION_NAME: Exception Region Output. ! (line 9) * EH_FRAME_THROUGH_COLLECT2: Exception Region Output. ! (line 19) ! * eh_return instruction pattern: Standard Names. (line 1698) ! * EH_RETURN_DATA_REGNO: Exception Handling. (line 6) ! * EH_RETURN_HANDLER_RTX: Exception Handling. (line 38) ! * EH_RETURN_STACKADJ_RTX: Exception Handling. (line 21) * EH_TABLES_CAN_BE_READ_ONLY: Exception Region Output. ! (line 29) ! * EH_USES: Function Entry. (line 155) * ei_edge: Edges. (line 43) * ei_end_p: Edges. (line 27) * ei_last: Edges. (line 23) --- 48520,48608 ---- * defining RTL sequences for code generation: Expander Definitions. (line 6) * delay slots, defining: Delay Slots. (line 6) ! * deletable: GTY Options. (line 131) * DELETE_IF_ORDINARY: Filesystem. (line 79) * Dependent Patterns: Dependent Patterns. (line 6) * desc: GTY Options. (line 88) * destructors, output of: Initialization. (line 6) * deterministic finite state automaton: Processor pipeline description. (line 6) * DFmode: Machine Modes. (line 76) ! * digits in constraint: Simple Constraints. (line 130) * DImode: Machine Modes. (line 45) * DIR_SEPARATOR: Filesystem. (line 18) * DIR_SEPARATOR_2: Filesystem. (line 19) + * directory options .md: Including Patterns. (line 44) * disabling certain registers: Register Basics. (line 73) * dispatch table: Dispatch Tables. (line 8) ! * div: Arithmetic. (line 115) ! * div and attributes: Expressions. (line 85) ! * division: Arithmetic. (line 115) ! * divM3 instruction pattern: Standard Names. (line 305) ! * divmodM4 instruction pattern: Standard Names. (line 565) ! * DO_BODY: Statements for C++. (line 6) ! * DO_COND: Statements for C++. (line 6) ! * DO_STMT: Statements for C++. (line 6) * dollar sign: Multi-Alternative. (line 57) ! * DOLLARS_IN_IDENTIFIERS: Misc. (line 454) ! * doloop_begin instruction pattern: Standard Names. (line 1525) ! * doloop_end instruction pattern: Standard Names. (line 1513) * DONE: Expander Definitions. (line 77) * DONT_USE_BUILTIN_SETJMP: Exception Region Output. ! (line 80) ! * DOUBLE_TYPE_SIZE: Type Layout. (line 53) * DQmode: Machine Modes. (line 118) * driver: Driver. (line 6) ! * DRIVER_SELF_SPECS: Driver. (line 9) * dump examples: Dump examples. (line 6) * dump setup: Dump setup. (line 6) * dump types: Dump types. (line 6) * dump verbosity: Dump output verbosity. (line 6) ! * dump_basic_block: Dump types. (line 30) ! * dump_generic_expr: Dump types. (line 33) ! * dump_gimple_stmt: Dump types. (line 36) * dump_printf: Dump types. (line 6) ! * DUMPFILE_FORMAT: Filesystem. (line 67) ! * DWARF2_ASM_LINE_DEBUG_INFO: SDB and DWARF. (line 50) ! * DWARF2_DEBUGGING_INFO: SDB and DWARF. (line 13) ! * DWARF2_FRAME_INFO: SDB and DWARF. (line 30) ! * DWARF2_FRAME_REG_OUT: Frame Registers. (line 150) * DWARF2_UNWIND_INFO: Exception Region Output. ! (line 41) ! * DWARF_ALT_FRAME_RETURN_COLUMN: Frame Layout. (line 150) * DWARF_CIE_DATA_ALIGNMENT: Exception Region Output. ! (line 92) ! * DWARF_FRAME_REGISTERS: Frame Registers. (line 110) ! * DWARF_FRAME_REGNUM: Frame Registers. (line 142) * DWARF_REG_TO_UNWIND_COLUMN: Frame Registers. (line 134) ! * DWARF_ZERO_REG: Frame Layout. (line 161) ! * DYNAMIC_CHAIN_ADDRESS: Frame Layout. (line 88) ! * E in constraint: Simple Constraints. (line 89) * earlyclobber operand: Modifiers. (line 25) * edge: Edges. (line 6) * edge in the flow graph: Edges. (line 6) * edge iterators: Edges. (line 15) * edge splitting: Maintaining the CFG. ! (line 107) ! * EDGE_ABNORMAL: Edges. (line 128) ! * EDGE_ABNORMAL, EDGE_ABNORMAL_CALL: Edges. (line 172) ! * EDGE_ABNORMAL, EDGE_EH: Edges. (line 96) ! * EDGE_ABNORMAL, EDGE_SIBCALL: Edges. (line 122) ! * EDGE_FALLTHRU, force_nonfallthru: Edges. (line 86) * EDOM, implicit usage: Library Calls. (line 59) * EH_FRAME_SECTION_NAME: Exception Region Output. ! (line 10) * EH_FRAME_THROUGH_COLLECT2: Exception Region Output. ! (line 20) ! * eh_return instruction pattern: Standard Names. (line 1709) ! * EH_RETURN_DATA_REGNO: Exception Handling. (line 7) ! * EH_RETURN_HANDLER_RTX: Exception Handling. (line 39) ! * EH_RETURN_STACKADJ_RTX: Exception Handling. (line 22) * EH_TABLES_CAN_BE_READ_ONLY: Exception Region Output. ! (line 30) ! * EH_USES: Function Entry. (line 158) * ei_edge: Edges. (line 43) * ei_end_p: Edges. (line 27) * ei_last: Edges. (line 23) *************** Concept Index *** 48157,48258 **** * ei_prev: Edges. (line 39) * ei_safe_safe: Edges. (line 47) * ei_start: Edges. (line 19) ! * ELIMINABLE_REGS: Elimination. (line 46) * ELSE_CLAUSE: Statements for C++. (line 6) * Embedded C: Fixed-point fractional library routines. (line 6) * Empty Statements: Empty Statements. (line 6) * EMPTY_CLASS_EXPR: Statements for C++. (line 6) ! * EMPTY_FIELD_BOUNDARY: Storage Layout. (line 311) * Emulated TLS: Emulated TLS. (line 6) * enabled: Disable Insn Alternatives. (line 6) ! * ENDFILE_SPEC: Driver. (line 155) ! * endianness: Portability. (line 20) * ENTRY_BLOCK_PTR, EXIT_BLOCK_PTR: Basic Blocks. (line 10) ! * enum reg_class: Register Classes. (line 70) * ENUMERAL_TYPE: Types. (line 6) * enumerations: Constant Definitions. (line 49) * epilogue: Function Entry. (line 6) ! * epilogue instruction pattern: Standard Names. (line 1736) ! * EPILOGUE_USES: Function Entry. (line 149) * eq: Comparisons. (line 52) ! * eq and attributes: Expressions. (line 83) ! * equal: Comparisons. (line 52) ! * eq_attr: Expressions. (line 104) * EQ_EXPR: Unary and Binary Expressions. (line 6) * errno, implicit usage: Library Calls. (line 71) * EXACT_DIV_EXPR: Unary and Binary Expressions. (line 6) * examining SSA_NAMEs: SSA. (line 182) - * exception handling: Edges. (line 95) * exception handling <1>: Exception Handling. (line 6) ! * exception_receiver instruction pattern: Standard Names. (line 1663) * exclamation point: Multi-Alternative. (line 48) * exclusion_set: Processor pipeline description. ! (line 223) ! * exclusive-or, bitwise: Arithmetic. (line 168) * EXIT_EXPR: Unary and Binary Expressions. (line 6) ! * EXIT_IGNORE_STACK: Function Entry. (line 137) ! * exp10M2 instruction pattern: Standard Names. (line 726) ! * exp2M2 instruction pattern: Standard Names. (line 733) * expander definitions: Expander Definitions. (line 6) ! * expm1M2 instruction pattern: Standard Names. (line 716) ! * expM2 instruction pattern: Standard Names. (line 709) ! * expression: Expression trees. (line 6) ! * expression codes: RTL Objects. (line 47) * EXPR_FILENAME: Working with declarations. (line 14) * EXPR_LINENO: Working with declarations. (line 20) ! * expr_list: Insns. (line 540) * EXPR_STMT: Statements for C++. (line 6) * EXPR_STMT_EXPR: Statements for C++. (line 6) ! * extendMN2 instruction pattern: Standard Names. (line 1124) ! * extensible constraints: Simple Constraints. (line 171) ! * EXTRA_SPECS: Driver. (line 182) ! * extv instruction pattern: Standard Names. (line 1215) ! * extvM instruction pattern: Standard Names. (line 1160) ! * extvmisalignM instruction pattern: Standard Names. (line 1170) ! * extzv instruction pattern: Standard Names. (line 1233) ! * extzvM instruction pattern: Standard Names. (line 1184) ! * extzvmisalignM instruction pattern: Standard Names. (line 1187) ! * F in constraint: Simple Constraints. (line 92) * FAIL: Expander Definitions. (line 83) ! * fall-thru: Edges. (line 68) * FATAL_EXIT_CODE: Host Misc. (line 6) * FDL, GNU Free Documentation License: GNU Free Documentation License. (line 6) * features, optional, in system conventions: Run-time Target. (line 59) * ffs: Arithmetic. (line 210) ! * ffsM2 instruction pattern: Standard Names. (line 872) * FIELD_DECL: Declarations. (line 6) * files and passes of the compiler: Passes. (line 6) * files, generated: Files. (line 6) - * file_end_indicate_exec_stack: File Framework. (line 39) * final_absence_set: Processor pipeline description. ! (line 223) ! * FINAL_PRESCAN_INSN: Instruction Output. (line 60) * final_presence_set: Processor pipeline description. ! (line 223) ! * final_sequence: Instruction Output. (line 144) ! * FIND_BASE_TERM: Addressing Modes. (line 117) * finite state automaton minimization: Processor pipeline description. ! (line 304) ! * FINI_ARRAY_SECTION_ASM_OP: Sections. (line 113) ! * FINI_SECTION_ASM_OP: Sections. (line 98) ! * FIRST_PARM_OFFSET: Frame Layout. (line 61) * FIRST_PARM_OFFSET and virtual registers: Regs and Memory. (line 65) ! * FIRST_PSEUDO_REGISTER: Register Basics. (line 8) ! * FIRST_STACK_REG: Stack Registers. (line 26) * FIRST_VIRTUAL_REGISTER: Regs and Memory. (line 51) * fix: Conversions. (line 66) * fixed register: Register Basics. (line 15) * fixed-point fractional library: Fixed-point fractional library routines. (line 6) --- 48611,48715 ---- * ei_prev: Edges. (line 39) * ei_safe_safe: Edges. (line 47) * ei_start: Edges. (line 19) ! * ELIMINABLE_REGS: Elimination. (line 47) * ELSE_CLAUSE: Statements for C++. (line 6) * Embedded C: Fixed-point fractional library routines. (line 6) * Empty Statements: Empty Statements. (line 6) * EMPTY_CLASS_EXPR: Statements for C++. (line 6) ! * EMPTY_FIELD_BOUNDARY: Storage Layout. (line 315) * Emulated TLS: Emulated TLS. (line 6) * enabled: Disable Insn Alternatives. (line 6) ! * ENDFILE_SPEC: Driver. (line 156) ! * endianness: Portability. (line 21) * ENTRY_BLOCK_PTR, EXIT_BLOCK_PTR: Basic Blocks. (line 10) ! * enum reg_class: Register Classes. (line 72) * ENUMERAL_TYPE: Types. (line 6) * enumerations: Constant Definitions. (line 49) * epilogue: Function Entry. (line 6) ! * epilogue instruction pattern: Standard Names. (line 1747) ! * EPILOGUE_USES: Function Entry. (line 152) * eq: Comparisons. (line 52) ! * eq and attributes: Expressions. (line 85) ! * eq_attr: Expressions. (line 106) * EQ_EXPR: Unary and Binary Expressions. (line 6) + * equal: Comparisons. (line 52) * errno, implicit usage: Library Calls. (line 71) * EXACT_DIV_EXPR: Unary and Binary Expressions. (line 6) * examining SSA_NAMEs: SSA. (line 182) * exception handling <1>: Exception Handling. (line 6) ! * exception handling: Edges. (line 96) ! * exception_receiver instruction pattern: Standard Names. (line 1673) * exclamation point: Multi-Alternative. (line 48) * exclusion_set: Processor pipeline description. ! (line 224) ! * exclusive-or, bitwise: Arithmetic. (line 167) * EXIT_EXPR: Unary and Binary Expressions. (line 6) ! * EXIT_IGNORE_STACK: Function Entry. (line 140) ! * exp10M2 instruction pattern: Standard Names. (line 732) ! * exp2M2 instruction pattern: Standard Names. (line 739) * expander definitions: Expander Definitions. (line 6) ! * expm1M2 instruction pattern: Standard Names. (line 722) ! * expM2 instruction pattern: Standard Names. (line 715) * EXPR_FILENAME: Working with declarations. (line 14) * EXPR_LINENO: Working with declarations. (line 20) ! * expr_list: Insns. (line 548) * EXPR_STMT: Statements for C++. (line 6) * EXPR_STMT_EXPR: Statements for C++. (line 6) ! * expression: Expression trees. (line 6) ! * expression codes: RTL Objects. (line 47) ! * extendMN2 instruction pattern: Standard Names. (line 1130) ! * extensible constraints: Simple Constraints. (line 173) ! * EXTRA_SPECS: Driver. (line 183) ! * extv instruction pattern: Standard Names. (line 1221) ! * extvM instruction pattern: Standard Names. (line 1166) ! * extvmisalignM instruction pattern: Standard Names. (line 1176) ! * extzv instruction pattern: Standard Names. (line 1239) ! * extzvM instruction pattern: Standard Names. (line 1190) ! * extzvmisalignM instruction pattern: Standard Names. (line 1193) ! * F in constraint: Simple Constraints. (line 94) * FAIL: Expander Definitions. (line 83) ! * fall-thru: Edges. (line 69) * FATAL_EXIT_CODE: Host Misc. (line 6) * FDL, GNU Free Documentation License: GNU Free Documentation License. (line 6) * features, optional, in system conventions: Run-time Target. (line 59) * ffs: Arithmetic. (line 210) ! * ffsM2 instruction pattern: Standard Names. (line 878) * FIELD_DECL: Declarations. (line 6) + * file_end_indicate_exec_stack: File Framework. (line 41) * files and passes of the compiler: Passes. (line 6) * files, generated: Files. (line 6) * final_absence_set: Processor pipeline description. ! (line 224) ! * FINAL_PRESCAN_INSN: Instruction Output. (line 61) * final_presence_set: Processor pipeline description. ! (line 224) ! * final_sequence: Instruction Output. (line 145) ! * FIND_BASE_TERM: Addressing Modes. (line 119) ! * FINI_ARRAY_SECTION_ASM_OP: Sections. (line 114) ! * FINI_SECTION_ASM_OP: Sections. (line 99) * finite state automaton minimization: Processor pipeline description. ! (line 305) ! * FIRST_PARM_OFFSET: Frame Layout. (line 63) * FIRST_PARM_OFFSET and virtual registers: Regs and Memory. (line 65) ! * FIRST_PSEUDO_REGISTER: Register Basics. (line 9) ! * FIRST_STACK_REG: Stack Registers. (line 27) * FIRST_VIRTUAL_REGISTER: Regs and Memory. (line 51) * fix: Conversions. (line 66) + * FIX_TRUNC_EXPR: Unary and Binary Expressions. + (line 6) + * fix_truncMN2 instruction pattern: Standard Names. (line 1117) * fixed register: Register Basics. (line 15) * fixed-point fractional library: Fixed-point fractional library routines. (line 6) *************** Concept Index *** 48261,48326 **** * FIXED_CST: Constant expressions. (line 6) * FIXED_POINT_TYPE: Types. (line 6) ! * FIXED_REGISTERS: Register Basics. (line 14) * fixed_regs: Register Basics. (line 59) ! * fixMN2 instruction pattern: Standard Names. (line 1091) ! * fixunsMN2 instruction pattern: Standard Names. (line 1100) ! * fixuns_truncMN2 instruction pattern: Standard Names. (line 1115) ! * fix_truncMN2 instruction pattern: Standard Names. (line 1111) ! * FIX_TRUNC_EXPR: Unary and Binary Expressions. ! (line 6) * flags in RTL expression: Flags. (line 6) * float: Conversions. (line 58) - * floating point and cross compilation: Floating Point. (line 6) - * floatMN2 instruction pattern: Standard Names. (line 1083) - * floatunsMN2 instruction pattern: Standard Names. (line 1087) * FLOAT_EXPR: Unary and Binary Expressions. (line 6) * float_extend: Conversions. (line 33) ! * FLOAT_LIB_COMPARE_RETURNS_BOOL: Library Calls. (line 32) ! * FLOAT_STORE_FLAG_VALUE: Misc. (line 286) * float_truncate: Conversions. (line 53) ! * FLOAT_TYPE_SIZE: Type Layout. (line 48) ! * FLOAT_WORDS_BIG_ENDIAN: Storage Layout. (line 41) * FLOAT_WORDS_BIG_ENDIAN, (lack of) effect on subreg: Regs and Memory. ! (line 224) ! * floorM2 instruction pattern: Standard Names. (line 800) * FLOOR_DIV_EXPR: Unary and Binary Expressions. (line 6) * FLOOR_MOD_EXPR: Unary and Binary Expressions. (line 6) * flow-insensitive alias analysis: Alias analysis. (line 6) * flow-sensitive alias analysis: Alias analysis. (line 6) ! * fma: Arithmetic. (line 112) ! * fmaM4 instruction pattern: Standard Names. (line 338) ! * fmaxM3 instruction pattern: Standard Names. (line 369) ! * fminM3 instruction pattern: Standard Names. (line 369) ! * fmodM3 instruction pattern: Standard Names. (line 632) ! * fmsM4 instruction pattern: Standard Names. (line 345) ! * fnmaM4 instruction pattern: Standard Names. (line 351) ! * fnmsM4 instruction pattern: Standard Names. (line 357) ! * FORCE_CODE_SECTION_ALIGN: Sections. (line 144) ! * force_reg: Standard Names. (line 36) * FOR_BODY: Statements for C++. (line 6) * FOR_COND: Statements for C++. (line 6) * FOR_EXPR: Statements for C++. (line 6) * FOR_INIT_STMT: Statements for C++. (line 6) * FOR_STMT: Statements for C++. (line 6) * for_user: GTY Options. (line 82) * fractional types: Fixed-point fractional library routines. (line 6) ! * fractMN2 instruction pattern: Standard Names. (line 1133) ! * fractunsMN2 instruction pattern: Standard Names. (line 1148) ! * fract_convert: Conversions. (line 82) ! * FRACT_TYPE_SIZE: Type Layout. (line 67) * frame layout: Frame Layout. (line 6) ! * FRAME_ADDR_RTX: Frame Layout. (line 110) ! * FRAME_GROWS_DOWNWARD: Frame Layout. (line 26) * FRAME_GROWS_DOWNWARD and virtual registers: Regs and Memory. (line 69) ! * FRAME_POINTER_CFA_OFFSET: Frame Layout. (line 208) * frame_pointer_needed: Function Entry. (line 34) ! * FRAME_POINTER_REGNUM: Frame Registers. (line 13) * FRAME_POINTER_REGNUM and virtual registers: Regs and Memory. (line 74) * frame_pointer_rtx: Frame Registers. (line 104) --- 48718,48780 ---- * FIXED_CST: Constant expressions. (line 6) * FIXED_POINT_TYPE: Types. (line 6) ! * FIXED_REGISTERS: Register Basics. (line 15) * fixed_regs: Register Basics. (line 59) ! * fixMN2 instruction pattern: Standard Names. (line 1097) ! * fixuns_truncMN2 instruction pattern: Standard Names. (line 1121) ! * fixunsMN2 instruction pattern: Standard Names. (line 1106) * flags in RTL expression: Flags. (line 6) * float: Conversions. (line 58) * FLOAT_EXPR: Unary and Binary Expressions. (line 6) * float_extend: Conversions. (line 33) ! * FLOAT_LIB_COMPARE_RETURNS_BOOL: Library Calls. (line 33) ! * FLOAT_STORE_FLAG_VALUE: Misc. (line 287) * float_truncate: Conversions. (line 53) ! * FLOAT_TYPE_SIZE: Type Layout. (line 49) ! * FLOAT_WORDS_BIG_ENDIAN: Storage Layout. (line 42) * FLOAT_WORDS_BIG_ENDIAN, (lack of) effect on subreg: Regs and Memory. ! (line 226) ! * floating point and cross compilation: Floating Point. (line 6) ! * floatMN2 instruction pattern: Standard Names. (line 1089) ! * floatunsMN2 instruction pattern: Standard Names. (line 1093) * FLOOR_DIV_EXPR: Unary and Binary Expressions. (line 6) * FLOOR_MOD_EXPR: Unary and Binary Expressions. (line 6) + * floorM2 instruction pattern: Standard Names. (line 806) * flow-insensitive alias analysis: Alias analysis. (line 6) * flow-sensitive alias analysis: Alias analysis. (line 6) ! * fma: Arithmetic. (line 111) ! * fmaM4 instruction pattern: Standard Names. (line 342) ! * fmaxM3 instruction pattern: Standard Names. (line 373) ! * fminM3 instruction pattern: Standard Names. (line 373) ! * fmodM3 instruction pattern: Standard Names. (line 638) ! * fmsM4 instruction pattern: Standard Names. (line 349) ! * fnmaM4 instruction pattern: Standard Names. (line 355) ! * fnmsM4 instruction pattern: Standard Names. (line 361) * FOR_BODY: Statements for C++. (line 6) * FOR_COND: Statements for C++. (line 6) * FOR_EXPR: Statements for C++. (line 6) * FOR_INIT_STMT: Statements for C++. (line 6) * FOR_STMT: Statements for C++. (line 6) * for_user: GTY Options. (line 82) + * FORCE_CODE_SECTION_ALIGN: Sections. (line 145) + * force_reg: Standard Names. (line 36) + * fract_convert: Conversions. (line 82) + * FRACT_TYPE_SIZE: Type Layout. (line 68) * fractional types: Fixed-point fractional library routines. (line 6) ! * fractMN2 instruction pattern: Standard Names. (line 1139) ! * fractunsMN2 instruction pattern: Standard Names. (line 1154) * frame layout: Frame Layout. (line 6) ! * FRAME_ADDR_RTX: Frame Layout. (line 112) ! * FRAME_GROWS_DOWNWARD: Frame Layout. (line 27) * FRAME_GROWS_DOWNWARD and virtual registers: Regs and Memory. (line 69) ! * FRAME_POINTER_CFA_OFFSET: Frame Layout. (line 210) * frame_pointer_needed: Function Entry. (line 34) ! * FRAME_POINTER_REGNUM: Frame Registers. (line 14) * FRAME_POINTER_REGNUM and virtual registers: Regs and Memory. (line 74) * frame_pointer_rtx: Frame Registers. (line 104) *************** Concept Index *** 48332,48362 **** * frame_related, in symbol_ref: Flags. (line 165) * frequency, count, BB_FREQ_BASE: Profile information. (line 30) ! * ftruncM2 instruction pattern: Standard Names. (line 1106) ! * function: Functions. (line 6) * function <1>: Functions for C++. (line 6) * function call conventions: Interface. (line 6) * function entry and exit: Function Entry. (line 6) * function entry point, alternate function entry point: Edges. ! (line 180) * function properties: Function Properties. (line 6) * function-call insns: Calls. (line 6) ! * functions, leaf: Leaf Functions. (line 6) ! * FUNCTION_ARG_OFFSET: Register Arguments. (line 210) ! * FUNCTION_ARG_PADDING: Register Arguments. (line 217) ! * FUNCTION_ARG_REGNO_P: Register Arguments. (line 265) ! * FUNCTION_BOUNDARY: Storage Layout. (line 159) ! * FUNCTION_DECL: Functions. (line 6) * FUNCTION_DECL <1>: Functions for C++. (line 6) ! * FUNCTION_MODE: Misc. (line 341) ! * FUNCTION_PROFILER: Profiling. (line 8) * FUNCTION_TYPE: Types. (line 6) * FUNCTION_VALUE: Scalar Return. (line 52) * FUNCTION_VALUE_REGNO_P: Scalar Return. (line 78) * fundamental type: Types. (line 6) ! * G in constraint: Simple Constraints. (line 96) ! * g in constraint: Simple Constraints. (line 118) * garbage collector, invocation: Invoking the garbage collector. (line 6) * garbage collector, troubleshooting: Troubleshooting. (line 6) --- 48786,48816 ---- * frame_related, in symbol_ref: Flags. (line 165) * frequency, count, BB_FREQ_BASE: Profile information. (line 30) ! * ftruncM2 instruction pattern: Standard Names. (line 1112) * function <1>: Functions for C++. (line 6) + * function: Functions. (line 6) * function call conventions: Interface. (line 6) * function entry and exit: Function Entry. (line 6) * function entry point, alternate function entry point: Edges. ! (line 181) * function properties: Function Properties. (line 6) * function-call insns: Calls. (line 6) ! * FUNCTION_ARG_OFFSET: Register Arguments. (line 212) ! * FUNCTION_ARG_PADDING: Register Arguments. (line 219) ! * FUNCTION_ARG_REGNO_P: Register Arguments. (line 267) ! * FUNCTION_BOUNDARY: Storage Layout. (line 161) * FUNCTION_DECL <1>: Functions for C++. (line 6) ! * FUNCTION_DECL: Functions. (line 6) ! * FUNCTION_MODE: Misc. (line 342) ! * FUNCTION_PROFILER: Profiling. (line 9) * FUNCTION_TYPE: Types. (line 6) * FUNCTION_VALUE: Scalar Return. (line 52) * FUNCTION_VALUE_REGNO_P: Scalar Return. (line 78) + * functions, leaf: Leaf Functions. (line 6) * fundamental type: Types. (line 6) ! * g in constraint: Simple Constraints. (line 120) ! * G in constraint: Simple Constraints. (line 98) * garbage collector, invocation: Invoking the garbage collector. (line 6) * garbage collector, troubleshooting: Troubleshooting. (line 6) *************** Concept Index *** 48365,48421 **** * gcov_type: Profile information. (line 41) * ge: Comparisons. (line 72) ! * ge and attributes: Expressions. (line 83) * gencodes: RTL passes. (line 18) * general_operand: Machine-Independent Predicates. ! (line 104) ! * GENERAL_REGS: Register Classes. (line 22) * generated files: Files. (line 6) * generating assembler output: Output Statement. (line 6) * generating insns: RTL Template. (line 6) - * GENERIC: Parsing pass. (line 6) * GENERIC <1>: GENERIC. (line 6) * generic predicates: Machine-Independent Predicates. (line 6) * genflags: RTL passes. (line 18) ! * GEN_ERRNO_RTX: Library Calls. (line 71) ! * get_attr: Expressions. (line 99) * get_attr_length: Insn Lengths. (line 52) ! * GET_CLASS_NARROWEST_MODE: Machine Modes. (line 344) * GET_CODE: RTL Objects. (line 47) * get_frame_size: Elimination. (line 34) * get_insns: Insns. (line 34) * get_last_insn: Insns. (line 34) ! * GET_MODE: Machine Modes. (line 291) ! * GET_MODE_ALIGNMENT: Machine Modes. (line 331) ! * GET_MODE_BITSIZE: Machine Modes. (line 315) ! * GET_MODE_CLASS: Machine Modes. (line 305) ! * GET_MODE_FBIT: Machine Modes. (line 322) ! * GET_MODE_IBIT: Machine Modes. (line 318) ! * GET_MODE_MASK: Machine Modes. (line 326) ! * GET_MODE_NAME: Machine Modes. (line 302) ! * GET_MODE_NUNITS: Machine Modes. (line 340) ! * GET_MODE_SIZE: Machine Modes. (line 312) ! * GET_MODE_UNIT_SIZE: Machine Modes. (line 334) ! * GET_MODE_WIDER_MODE: Machine Modes. (line 308) * GET_RTX_CLASS: RTL Classes. (line 6) * GET_RTX_FORMAT: RTL Classes. (line 131) * GET_RTX_LENGTH: RTL Classes. (line 128) * get_thread_pointerMODE instruction pattern: Standard Names. ! (line 2073) * geu: Comparisons. (line 72) ! * geu and attributes: Expressions. (line 83) ! * GE_EXPR: Unary and Binary Expressions. ! (line 6) * GGC: Type Information. (line 6) * ggc_collect: Invoking the garbage collector. (line 6) - * GIMPLE: Parsing pass. (line 13) - * GIMPLE <1>: Gimplification pass. - (line 6) - * GIMPLE <2>: GIMPLE. (line 6) * gimple: Tuple representation. (line 14) * GIMPLE API: GIMPLE API. (line 6) * GIMPLE class hierarchy: Class hierarchy of GIMPLE statements. (line 6) --- 48819,48875 ---- * gcov_type: Profile information. (line 41) * ge: Comparisons. (line 72) ! * ge and attributes: Expressions. (line 85) ! * GE_EXPR: Unary and Binary Expressions. ! (line 6) ! * GEN_ERRNO_RTX: Library Calls. (line 72) * gencodes: RTL passes. (line 18) * general_operand: Machine-Independent Predicates. ! (line 105) ! * GENERAL_REGS: Register Classes. (line 23) * generated files: Files. (line 6) * generating assembler output: Output Statement. (line 6) * generating insns: RTL Template. (line 6) * GENERIC <1>: GENERIC. (line 6) + * GENERIC: Parsing pass. (line 6) * generic predicates: Machine-Independent Predicates. (line 6) * genflags: RTL passes. (line 18) ! * get_attr: Expressions. (line 101) * get_attr_length: Insn Lengths. (line 52) ! * GET_CLASS_NARROWEST_MODE: Machine Modes. (line 345) * GET_CODE: RTL Objects. (line 47) * get_frame_size: Elimination. (line 34) * get_insns: Insns. (line 34) * get_last_insn: Insns. (line 34) ! * GET_MODE: Machine Modes. (line 292) ! * GET_MODE_ALIGNMENT: Machine Modes. (line 332) ! * GET_MODE_BITSIZE: Machine Modes. (line 316) ! * GET_MODE_CLASS: Machine Modes. (line 306) ! * GET_MODE_FBIT: Machine Modes. (line 323) ! * GET_MODE_IBIT: Machine Modes. (line 319) ! * GET_MODE_MASK: Machine Modes. (line 327) ! * GET_MODE_NAME: Machine Modes. (line 303) ! * GET_MODE_NUNITS: Machine Modes. (line 341) ! * GET_MODE_SIZE: Machine Modes. (line 313) ! * GET_MODE_UNIT_SIZE: Machine Modes. (line 335) ! * GET_MODE_WIDER_MODE: Machine Modes. (line 309) * GET_RTX_CLASS: RTL Classes. (line 6) * GET_RTX_FORMAT: RTL Classes. (line 131) * GET_RTX_LENGTH: RTL Classes. (line 128) * get_thread_pointerMODE instruction pattern: Standard Names. ! (line 2084) * geu: Comparisons. (line 72) ! * geu and attributes: Expressions. (line 85) * GGC: Type Information. (line 6) * ggc_collect: Invoking the garbage collector. (line 6) * gimple: Tuple representation. (line 14) + * GIMPLE <1>: GIMPLE. (line 6) + * GIMPLE <2>: Gimplification pass. + (line 6) + * GIMPLE: Parsing pass. (line 14) * GIMPLE API: GIMPLE API. (line 6) * GIMPLE class hierarchy: Class hierarchy of GIMPLE statements. (line 6) *************** Concept Index *** 48424,48942 **** * GIMPLE instruction set: GIMPLE instruction set. (line 6) * GIMPLE sequences: GIMPLE sequences. (line 6) - * GIMPLE statement iterators: Basic Blocks. (line 78) * GIMPLE statement iterators <1>: Maintaining the CFG. ! (line 33) * gimple_addresses_taken: Manipulating GIMPLE statements. ! (line 89) * GIMPLE_ASM: GIMPLE_ASM. (line 6) ! * gimple_asm_clobber_op: GIMPLE_ASM. (line 39) ! * gimple_asm_input_op: GIMPLE_ASM. (line 23) ! * gimple_asm_nclobbers: GIMPLE_ASM. (line 20) ! * gimple_asm_ninputs: GIMPLE_ASM. (line 14) ! * gimple_asm_noutputs: GIMPLE_ASM. (line 17) ! * gimple_asm_output_op: GIMPLE_ASM. (line 31) ! * gimple_asm_set_clobber_op: GIMPLE_ASM. (line 43) ! * gimple_asm_set_input_op: GIMPLE_ASM. (line 27) ! * gimple_asm_set_output_op: GIMPLE_ASM. (line 35) ! * gimple_asm_set_volatile: GIMPLE_ASM. (line 54) ! * gimple_asm_string: GIMPLE_ASM. (line 47) ! * gimple_asm_volatile_p: GIMPLE_ASM. (line 51) * GIMPLE_ASSIGN: GIMPLE_ASSIGN. (line 6) ! * gimple_assign_cast_p: Logical Operators. (line 158) ! * gimple_assign_cast_p <1>: GIMPLE_ASSIGN. (line 104) ! * gimple_assign_lhs: GIMPLE_ASSIGN. (line 62) ! * gimple_assign_lhs_ptr: GIMPLE_ASSIGN. (line 65) ! * gimple_assign_rhs1: GIMPLE_ASSIGN. (line 68) ! * gimple_assign_rhs1_ptr: GIMPLE_ASSIGN. (line 71) ! * gimple_assign_rhs2: GIMPLE_ASSIGN. (line 75) ! * gimple_assign_rhs2_ptr: GIMPLE_ASSIGN. (line 78) ! * gimple_assign_rhs3: GIMPLE_ASSIGN. (line 82) ! * gimple_assign_rhs3_ptr: GIMPLE_ASSIGN. (line 85) ! * gimple_assign_rhs_class: GIMPLE_ASSIGN. (line 56) ! * gimple_assign_rhs_code: GIMPLE_ASSIGN. (line 52) ! * gimple_assign_set_lhs: GIMPLE_ASSIGN. (line 89) ! * gimple_assign_set_rhs1: GIMPLE_ASSIGN. (line 92) ! * gimple_assign_set_rhs2: GIMPLE_ASSIGN. (line 96) ! * gimple_assign_set_rhs3: GIMPLE_ASSIGN. (line 100) * gimple_bb: Manipulating GIMPLE statements. ! (line 17) * GIMPLE_BIND: GIMPLE_BIND. (line 6) ! * gimple_bind_add_seq: GIMPLE_BIND. (line 34) ! * gimple_bind_add_stmt: GIMPLE_BIND. (line 31) ! * gimple_bind_append_vars: GIMPLE_BIND. (line 18) ! * gimple_bind_block: GIMPLE_BIND. (line 39) ! * gimple_bind_body: GIMPLE_BIND. (line 22) ! * gimple_bind_set_block: GIMPLE_BIND. (line 44) ! * gimple_bind_set_body: GIMPLE_BIND. (line 26) ! * gimple_bind_set_vars: GIMPLE_BIND. (line 14) ! * gimple_bind_vars: GIMPLE_BIND. (line 11) * gimple_block: Manipulating GIMPLE statements. ! (line 20) ! * gimple_build: GIMPLE API. (line 34) ! * gimple_build <1>: GIMPLE API. (line 36) ! * gimple_build <2>: GIMPLE API. (line 38) ! * gimple_build <3>: GIMPLE API. (line 41) ! * gimple_build <4>: GIMPLE API. (line 44) ! * gimple_build <5>: GIMPLE API. (line 47) ! * gimple_build_nop: GIMPLE_NOP. (line 6) ! * gimple_build_omp_master: GIMPLE_OMP_MASTER. (line 6) ! * gimple_build_omp_ordered: GIMPLE_OMP_ORDERED. (line 6) ! * gimple_build_omp_return: GIMPLE_OMP_RETURN. (line 6) ! * gimple_build_omp_section: GIMPLE_OMP_SECTION. (line 6) * gimple_build_omp_sections_switch: GIMPLE_OMP_SECTIONS. ! (line 13) * gimple_build_wce: GIMPLE_WITH_CLEANUP_EXPR. ! (line 6) * GIMPLE_CALL: GIMPLE_CALL. (line 6) ! * gimple_call_arg: GIMPLE_CALL. (line 65) ! * gimple_call_arg_ptr: GIMPLE_CALL. (line 69) ! * gimple_call_chain: GIMPLE_CALL. (line 56) ! * gimple_call_copy_skip_args: GIMPLE_CALL. (line 90) ! * gimple_call_fn: GIMPLE_CALL. (line 37) ! * gimple_call_fndecl: GIMPLE_CALL. (line 45) ! * gimple_call_lhs: GIMPLE_CALL. (line 28) ! * gimple_call_lhs_ptr: GIMPLE_CALL. (line 31) ! * gimple_call_noreturn_p: GIMPLE_CALL. (line 87) ! * gimple_call_num_args: GIMPLE_CALL. (line 62) ! * gimple_call_return_type: GIMPLE_CALL. (line 53) ! * gimple_call_set_arg: GIMPLE_CALL. (line 74) ! * gimple_call_set_chain: GIMPLE_CALL. (line 59) ! * gimple_call_set_fn: GIMPLE_CALL. (line 41) ! * gimple_call_set_fndecl: GIMPLE_CALL. (line 50) ! * gimple_call_set_lhs: GIMPLE_CALL. (line 34) ! * gimple_call_set_tail: GIMPLE_CALL. (line 79) ! * gimple_call_tail_p: GIMPLE_CALL. (line 84) * GIMPLE_CATCH: GIMPLE_CATCH. (line 6) ! * gimple_catch_handler: GIMPLE_CATCH. (line 19) ! * gimple_catch_set_handler: GIMPLE_CATCH. (line 26) ! * gimple_catch_set_types: GIMPLE_CATCH. (line 23) ! * gimple_catch_types: GIMPLE_CATCH. (line 12) ! * gimple_catch_types_ptr: GIMPLE_CATCH. (line 15) * gimple_code: Manipulating GIMPLE statements. ! (line 14) * GIMPLE_COND: GIMPLE_COND. (line 6) ! * gimple_cond_code: GIMPLE_COND. (line 20) ! * gimple_cond_false_label: GIMPLE_COND. (line 59) ! * gimple_cond_lhs: GIMPLE_COND. (line 29) ! * gimple_cond_make_false: GIMPLE_COND. (line 63) ! * gimple_cond_make_true: GIMPLE_COND. (line 66) ! * gimple_cond_rhs: GIMPLE_COND. (line 37) ! * gimple_cond_set_code: GIMPLE_COND. (line 24) ! * gimple_cond_set_false_label: GIMPLE_COND. (line 54) ! * gimple_cond_set_lhs: GIMPLE_COND. (line 33) ! * gimple_cond_set_rhs: GIMPLE_COND. (line 41) ! * gimple_cond_set_true_label: GIMPLE_COND. (line 49) ! * gimple_cond_true_label: GIMPLE_COND. (line 45) ! * gimple_convert: GIMPLE API. (line 50) * gimple_copy: Manipulating GIMPLE statements. ! (line 146) * GIMPLE_DEBUG: GIMPLE_DEBUG. (line 6) * GIMPLE_DEBUG_BIND: GIMPLE_DEBUG. (line 6) ! * gimple_debug_bind_get_value: GIMPLE_DEBUG. (line 46) ! * gimple_debug_bind_get_value_ptr: GIMPLE_DEBUG. (line 50) ! * gimple_debug_bind_get_var: GIMPLE_DEBUG. (line 43) ! * gimple_debug_bind_has_value_p: GIMPLE_DEBUG. (line 68) ! * gimple_debug_bind_p: Logical Operators. (line 162) ! * gimple_debug_bind_reset_value: GIMPLE_DEBUG. (line 64) ! * gimple_debug_bind_set_value: GIMPLE_DEBUG. (line 59) ! * gimple_debug_bind_set_var: GIMPLE_DEBUG. (line 55) * gimple_def_ops: Manipulating GIMPLE statements. ! (line 93) * GIMPLE_EH_FILTER: GIMPLE_EH_FILTER. (line 6) ! * gimple_eh_filter_failure: GIMPLE_EH_FILTER. (line 18) ! * gimple_eh_filter_set_failure: GIMPLE_EH_FILTER. (line 27) ! * gimple_eh_filter_set_types: GIMPLE_EH_FILTER. (line 22) ! * gimple_eh_filter_types: GIMPLE_EH_FILTER. (line 11) ! * gimple_eh_filter_types_ptr: GIMPLE_EH_FILTER. (line 14) ! * gimple_eh_must_not_throw_fndecl: GIMPLE_EH_FILTER. (line 32) ! * gimple_eh_must_not_throw_set_fndecl: GIMPLE_EH_FILTER. (line 36) * gimple_expr_code: Manipulating GIMPLE statements. ! (line 30) * gimple_expr_type: Manipulating GIMPLE statements. ! (line 23) * GIMPLE_GOTO: GIMPLE_GOTO. (line 6) ! * gimple_goto_dest: GIMPLE_GOTO. (line 9) ! * gimple_goto_set_dest: GIMPLE_GOTO. (line 12) * gimple_has_mem_ops: Manipulating GIMPLE statements. ! (line 71) * gimple_has_ops: Manipulating GIMPLE statements. ! (line 68) * gimple_has_volatile_ops: Manipulating GIMPLE statements. ! (line 133) * GIMPLE_LABEL: GIMPLE_LABEL. (line 6) ! * gimple_label_label: GIMPLE_LABEL. (line 10) ! * gimple_label_set_label: GIMPLE_LABEL. (line 13) * gimple_loaded_syms: Manipulating GIMPLE statements. ! (line 121) * gimple_locus: Manipulating GIMPLE statements. ! (line 41) * gimple_locus_empty_p: Manipulating GIMPLE statements. ! (line 47) * gimple_modified_p: Manipulating GIMPLE statements. ! (line 129) ! * GIMPLE_NOP: GIMPLE_NOP. (line 6) ! * gimple_nop_p: GIMPLE_NOP. (line 9) * gimple_no_warning_p: Manipulating GIMPLE statements. ! (line 50) ! * gimple_num_ops: Logical Operators. (line 76) * gimple_num_ops <1>: Manipulating GIMPLE statements. ! (line 74) * GIMPLE_OMP_ATOMIC_LOAD: GIMPLE_OMP_ATOMIC_LOAD. (line 6) * gimple_omp_atomic_load_lhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 16) * gimple_omp_atomic_load_rhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 24) * gimple_omp_atomic_load_set_lhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 12) * gimple_omp_atomic_load_set_rhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 20) * GIMPLE_OMP_ATOMIC_STORE: GIMPLE_OMP_ATOMIC_STORE. (line 6) * gimple_omp_atomic_store_set_val: GIMPLE_OMP_ATOMIC_STORE. ! (line 11) * gimple_omp_atomic_store_val: GIMPLE_OMP_ATOMIC_STORE. ! (line 15) * gimple_omp_body: GIMPLE_OMP_PARALLEL. ! (line 23) * GIMPLE_OMP_CONTINUE: GIMPLE_OMP_CONTINUE. (line 6) * gimple_omp_continue_control_def: GIMPLE_OMP_CONTINUE. ! (line 12) * gimple_omp_continue_control_def_ptr: GIMPLE_OMP_CONTINUE. ! (line 17) * gimple_omp_continue_control_use: GIMPLE_OMP_CONTINUE. ! (line 26) * gimple_omp_continue_control_use_ptr: GIMPLE_OMP_CONTINUE. ! (line 31) * gimple_omp_continue_set_control_def: GIMPLE_OMP_CONTINUE. ! (line 21) * gimple_omp_continue_set_control_use: GIMPLE_OMP_CONTINUE. ! (line 35) * GIMPLE_OMP_CRITICAL: GIMPLE_OMP_CRITICAL. (line 6) * gimple_omp_critical_name: GIMPLE_OMP_CRITICAL. ! (line 12) * gimple_omp_critical_name_ptr: GIMPLE_OMP_CRITICAL. ! (line 16) * gimple_omp_critical_set_name: GIMPLE_OMP_CRITICAL. ! (line 21) * GIMPLE_OMP_FOR: GIMPLE_OMP_FOR. (line 6) ! * gimple_omp_for_clauses: GIMPLE_OMP_FOR. (line 17) ! * gimple_omp_for_clauses_ptr: GIMPLE_OMP_FOR. (line 20) ! * gimple_omp_for_cond: GIMPLE_OMP_FOR. (line 80) ! * gimple_omp_for_final: GIMPLE_OMP_FOR. (line 48) ! * gimple_omp_for_final_ptr: GIMPLE_OMP_FOR. (line 51) ! * gimple_omp_for_incr: GIMPLE_OMP_FOR. (line 58) ! * gimple_omp_for_incr_ptr: GIMPLE_OMP_FOR. (line 61) ! * gimple_omp_for_index: GIMPLE_OMP_FOR. (line 28) ! * gimple_omp_for_index_ptr: GIMPLE_OMP_FOR. (line 31) ! * gimple_omp_for_initial: GIMPLE_OMP_FOR. (line 38) ! * gimple_omp_for_initial_ptr: GIMPLE_OMP_FOR. (line 41) ! * gimple_omp_for_pre_body: GIMPLE_OMP_FOR. (line 67) ! * gimple_omp_for_set_clauses: GIMPLE_OMP_FOR. (line 23) ! * gimple_omp_for_set_cond: GIMPLE_OMP_FOR. (line 76) ! * gimple_omp_for_set_final: GIMPLE_OMP_FOR. (line 54) ! * gimple_omp_for_set_incr: GIMPLE_OMP_FOR. (line 64) ! * gimple_omp_for_set_index: GIMPLE_OMP_FOR. (line 34) ! * gimple_omp_for_set_initial: GIMPLE_OMP_FOR. (line 44) ! * gimple_omp_for_set_pre_body: GIMPLE_OMP_FOR. (line 71) * GIMPLE_OMP_MASTER: GIMPLE_OMP_MASTER. (line 6) * GIMPLE_OMP_ORDERED: GIMPLE_OMP_ORDERED. (line 6) * GIMPLE_OMP_PARALLEL: GIMPLE_OMP_PARALLEL. (line 6) * gimple_omp_parallel_child_fn: GIMPLE_OMP_PARALLEL. ! (line 42) * gimple_omp_parallel_child_fn_ptr: GIMPLE_OMP_PARALLEL. ! (line 47) * gimple_omp_parallel_clauses: GIMPLE_OMP_PARALLEL. ! (line 30) * gimple_omp_parallel_clauses_ptr: GIMPLE_OMP_PARALLEL. ! (line 33) * gimple_omp_parallel_combined_p: GIMPLE_OMP_PARALLEL. ! (line 15) * gimple_omp_parallel_data_arg: GIMPLE_OMP_PARALLEL. ! (line 56) * gimple_omp_parallel_data_arg_ptr: GIMPLE_OMP_PARALLEL. ! (line 61) * gimple_omp_parallel_set_child_fn: GIMPLE_OMP_PARALLEL. ! (line 52) * gimple_omp_parallel_set_clauses: GIMPLE_OMP_PARALLEL. ! (line 37) * gimple_omp_parallel_set_combined_p: GIMPLE_OMP_PARALLEL. ! (line 19) * gimple_omp_parallel_set_data_arg: GIMPLE_OMP_PARALLEL. ! (line 65) * GIMPLE_OMP_RETURN: GIMPLE_OMP_RETURN. (line 6) ! * gimple_omp_return_nowait_p: GIMPLE_OMP_RETURN. (line 13) ! * gimple_omp_return_set_nowait: GIMPLE_OMP_RETURN. (line 10) * GIMPLE_OMP_SECTION: GIMPLE_OMP_SECTION. (line 6) * GIMPLE_OMP_SECTIONS: GIMPLE_OMP_SECTIONS. (line 6) * gimple_omp_sections_clauses: GIMPLE_OMP_SECTIONS. ! (line 29) * gimple_omp_sections_clauses_ptr: GIMPLE_OMP_SECTIONS. ! (line 32) * gimple_omp_sections_control: GIMPLE_OMP_SECTIONS. ! (line 16) * gimple_omp_sections_control_ptr: GIMPLE_OMP_SECTIONS. ! (line 20) * gimple_omp_sections_set_clauses: GIMPLE_OMP_SECTIONS. ! (line 35) * gimple_omp_sections_set_control: GIMPLE_OMP_SECTIONS. - (line 24) - * gimple_omp_section_last_p: GIMPLE_OMP_SECTION. (line 11) - * gimple_omp_section_set_last: GIMPLE_OMP_SECTION. (line 15) - * gimple_omp_set_body: GIMPLE_OMP_PARALLEL. (line 26) * GIMPLE_OMP_SINGLE: GIMPLE_OMP_SINGLE. (line 6) ! * gimple_omp_single_clauses: GIMPLE_OMP_SINGLE. (line 13) ! * gimple_omp_single_clauses_ptr: GIMPLE_OMP_SINGLE. (line 16) ! * gimple_omp_single_set_clauses: GIMPLE_OMP_SINGLE. (line 19) ! * gimple_op: Logical Operators. (line 79) * gimple_op <1>: Manipulating GIMPLE statements. ! (line 80) ! * gimple_ops: Logical Operators. (line 82) ! * gimple_ops <1>: Manipulating GIMPLE statements. ! (line 77) * gimple_op_ptr: Manipulating GIMPLE statements. ! (line 83) * GIMPLE_PHI: GIMPLE_PHI. (line 6) ! * gimple_phi_arg: GIMPLE_PHI. (line 24) ! * gimple_phi_arg <1>: SSA. (line 62) ! * gimple_phi_arg_def: SSA. (line 68) ! * gimple_phi_arg_edge: SSA. (line 65) ! * gimple_phi_capacity: GIMPLE_PHI. (line 6) ! * gimple_phi_num_args: GIMPLE_PHI. (line 10) ! * gimple_phi_num_args <1>: SSA. (line 58) ! * gimple_phi_result: GIMPLE_PHI. (line 15) ! * gimple_phi_result <1>: SSA. (line 55) ! * gimple_phi_result_ptr: GIMPLE_PHI. (line 18) ! * gimple_phi_set_arg: GIMPLE_PHI. (line 28) ! * gimple_phi_set_result: GIMPLE_PHI. (line 21) * gimple_plf: Manipulating GIMPLE statements. ! (line 64) * GIMPLE_RESX: GIMPLE_RESX. (line 6) ! * gimple_resx_region: GIMPLE_RESX. (line 12) ! * gimple_resx_set_region: GIMPLE_RESX. (line 15) * GIMPLE_RETURN: GIMPLE_RETURN. (line 6) ! * gimple_return_retval: GIMPLE_RETURN. (line 9) ! * gimple_return_set_retval: GIMPLE_RETURN. (line 12) ! * gimple_seq_add_seq: GIMPLE sequences. (line 30) ! * gimple_seq_add_stmt: GIMPLE sequences. (line 24) ! * gimple_seq_alloc: GIMPLE sequences. (line 61) ! * gimple_seq_copy: GIMPLE sequences. (line 65) ! * gimple_seq_deep_copy: GIMPLE sequences. (line 36) ! * gimple_seq_empty_p: GIMPLE sequences. (line 69) ! * gimple_seq_first: GIMPLE sequences. (line 43) ! * gimple_seq_init: GIMPLE sequences. (line 58) ! * gimple_seq_last: GIMPLE sequences. (line 46) ! * gimple_seq_reverse: GIMPLE sequences. (line 39) ! * gimple_seq_set_first: GIMPLE sequences. (line 53) ! * gimple_seq_set_last: GIMPLE sequences. (line 49) ! * gimple_seq_singleton_p: GIMPLE sequences. (line 78) * gimple_set_block: Manipulating GIMPLE statements. ! (line 38) * gimple_set_def_ops: Manipulating GIMPLE statements. ! (line 96) * gimple_set_has_volatile_ops: Manipulating GIMPLE statements. ! (line 136) * gimple_set_locus: Manipulating GIMPLE statements. ! (line 44) * gimple_set_op: Manipulating GIMPLE statements. ! (line 86) * gimple_set_plf: Manipulating GIMPLE statements. ! (line 60) * gimple_set_use_ops: Manipulating GIMPLE statements. ! (line 103) * gimple_set_vdef_ops: Manipulating GIMPLE statements. ! (line 117) * gimple_set_visited: Manipulating GIMPLE statements. ! (line 53) * gimple_set_vuse_ops: Manipulating GIMPLE statements. ! (line 110) ! * gimple_simplify: GIMPLE API. (line 6) ! * gimple_simplify <1>: GIMPLE API. (line 8) ! * gimple_simplify <2>: GIMPLE API. (line 10) ! * gimple_simplify <3>: GIMPLE API. (line 12) ! * gimple_simplify <4>: GIMPLE API. (line 14) ! * gimple_simplify <5>: GIMPLE API. (line 16) * gimple_statement_with_ops: Tuple representation. (line 96) * gimple_stored_syms: Manipulating GIMPLE statements. ! (line 125) * GIMPLE_SWITCH: GIMPLE_SWITCH. (line 6) ! * gimple_switch_default_label: GIMPLE_SWITCH. (line 41) ! * gimple_switch_index: GIMPLE_SWITCH. (line 24) ! * gimple_switch_label: GIMPLE_SWITCH. (line 31) ! * gimple_switch_num_labels: GIMPLE_SWITCH. (line 14) ! * gimple_switch_set_default_label: GIMPLE_SWITCH. (line 45) ! * gimple_switch_set_index: GIMPLE_SWITCH. (line 27) ! * gimple_switch_set_label: GIMPLE_SWITCH. (line 36) ! * gimple_switch_set_num_labels: GIMPLE_SWITCH. (line 19) * GIMPLE_TRY: GIMPLE_TRY. (line 6) ! * gimple_try_catch_is_cleanup: GIMPLE_TRY. (line 19) ! * gimple_try_cleanup: GIMPLE_TRY. (line 26) ! * gimple_try_eval: GIMPLE_TRY. (line 22) ! * gimple_try_kind: GIMPLE_TRY. (line 15) ! * gimple_try_set_catch_is_cleanup: GIMPLE_TRY. (line 30) ! * gimple_try_set_cleanup: GIMPLE_TRY. (line 38) ! * gimple_try_set_eval: GIMPLE_TRY. (line 34) * gimple_use_ops: Manipulating GIMPLE statements. ! (line 100) * gimple_vdef_ops: Manipulating GIMPLE statements. ! (line 114) * gimple_visited_p: Manipulating GIMPLE statements. ! (line 57) * gimple_vuse_ops: Manipulating GIMPLE statements. ! (line 107) * gimple_wce_cleanup: GIMPLE_WITH_CLEANUP_EXPR. ! (line 10) * gimple_wce_cleanup_eh_only: GIMPLE_WITH_CLEANUP_EXPR. ! (line 17) * gimple_wce_set_cleanup: GIMPLE_WITH_CLEANUP_EXPR. ! (line 13) * gimple_wce_set_cleanup_eh_only: GIMPLE_WITH_CLEANUP_EXPR. ! (line 20) * GIMPLE_WITH_CLEANUP_EXPR: GIMPLE_WITH_CLEANUP_EXPR. (line 6) - * gimplification: Parsing pass. (line 13) * gimplification <1>: Gimplification pass. (line 6) ! * gimplifier: Parsing pass. (line 13) ! * gimplify_assign: GIMPLE_ASSIGN. (line 41) * gimplify_expr: Gimplification pass. (line 18) * gimplify_function_tree: Gimplification pass. (line 18) * GLOBAL_INIT_PRIORITY: Functions for C++. (line 141) * global_regs: Register Basics. (line 59) ! * GO_IF_LEGITIMATE_ADDRESS: Addressing Modes. (line 90) * greater than: Comparisons. (line 60) ! * greater than <1>: Comparisons. (line 64) ! * greater than <2>: Comparisons. (line 72) ! * gsi_after_labels: Sequence iterators. (line 74) ! * gsi_bb: Sequence iterators. (line 82) ! * gsi_commit_edge_inserts: Sequence iterators. (line 193) * gsi_commit_edge_inserts <1>: Maintaining the CFG. ! (line 105) ! * gsi_commit_one_edge_insert: Sequence iterators. (line 188) ! * gsi_end_p: Sequence iterators. (line 59) * gsi_end_p <1>: Maintaining the CFG. ! (line 48) ! * gsi_for_stmt: Sequence iterators. (line 156) ! * gsi_insert_after: Sequence iterators. (line 145) * gsi_insert_after <1>: Maintaining the CFG. ! (line 60) ! * gsi_insert_before: Sequence iterators. (line 134) * gsi_insert_before <1>: Maintaining the CFG. ! (line 66) ! * gsi_insert_on_edge: Sequence iterators. (line 173) * gsi_insert_on_edge <1>: Maintaining the CFG. ! (line 105) ! * gsi_insert_on_edge_immediate: Sequence iterators. (line 183) ! * gsi_insert_seq_after: Sequence iterators. (line 152) ! * gsi_insert_seq_before: Sequence iterators. (line 141) ! * gsi_insert_seq_on_edge: Sequence iterators. (line 177) ! * gsi_last: Sequence iterators. (line 49) * gsi_last <1>: Maintaining the CFG. ! (line 44) ! * gsi_last_bb: Sequence iterators. (line 55) ! * gsi_link_after: Sequence iterators. (line 113) ! * gsi_link_before: Sequence iterators. (line 103) ! * gsi_link_seq_after: Sequence iterators. (line 108) ! * gsi_link_seq_before: Sequence iterators. (line 97) ! * gsi_move_after: Sequence iterators. (line 159) ! * gsi_move_before: Sequence iterators. (line 164) ! * gsi_move_to_bb_end: Sequence iterators. (line 169) ! * gsi_next: Sequence iterators. (line 65) * gsi_next <1>: Maintaining the CFG. ! (line 52) ! * gsi_one_before_end_p: Sequence iterators. (line 62) ! * gsi_prev: Sequence iterators. (line 68) * gsi_prev <1>: Maintaining the CFG. ! (line 56) ! * gsi_remove: Sequence iterators. (line 88) * gsi_remove <1>: Maintaining the CFG. ! (line 72) ! * gsi_replace: Sequence iterators. (line 128) ! * gsi_seq: Sequence iterators. (line 85) ! * gsi_split_seq_after: Sequence iterators. (line 118) ! * gsi_split_seq_before: Sequence iterators. (line 123) ! * gsi_start: Sequence iterators. (line 39) * gsi_start <1>: Maintaining the CFG. ! (line 40) ! * gsi_start_bb: Sequence iterators. (line 45) ! * gsi_stmt: Sequence iterators. (line 71) ! * gsi_stmt_ptr: Sequence iterators. (line 79) * gt: Comparisons. (line 60) ! * gt and attributes: Expressions. (line 83) ! * gtu: Comparisons. (line 64) ! * gtu and attributes: Expressions. (line 83) ! * GTY: Type Information. (line 6) * GT_EXPR: Unary and Binary Expressions. (line 6) ! * H in constraint: Simple Constraints. (line 96) ! * HAmode: Machine Modes. (line 146) * HANDLER: Statements for C++. (line 6) * HANDLER_BODY: Statements for C++. (line 6) * HANDLER_PARMS: Statements for C++. (line 6) - * HANDLE_PRAGMA_PACK_WITH_EXPANSION: Misc. (line 442) * hard registers: Regs and Memory. (line 9) ! * HARD_FRAME_POINTER_IS_ARG_POINTER: Frame Registers. (line 57) ! * HARD_FRAME_POINTER_IS_FRAME_POINTER: Frame Registers. (line 50) ! * HARD_FRAME_POINTER_REGNUM: Frame Registers. (line 19) ! * HARD_REGNO_CALLER_SAVE_MODE: Caller Saves. (line 10) ! * HARD_REGNO_CALL_PART_CLOBBERED: Register Basics. (line 52) * HARD_REGNO_MODE_OK: Values in Registers. ! (line 57) * HARD_REGNO_NREGS: Values in Registers. ! (line 10) * HARD_REGNO_NREGS_HAS_PADDING: Values in Registers. ! (line 24) * HARD_REGNO_NREGS_WITH_PADDING: Values in Registers. ! (line 42) * HARD_REGNO_RENAME_OK: Values in Registers. ! (line 117) * HAS_INIT_SECTION: Macros for Initialization. ! (line 18) ! * HAS_LONG_COND_BRANCH: Misc. (line 8) ! * HAS_LONG_UNCOND_BRANCH: Misc. (line 17) * HAVE_DOS_BASED_FILE_SYSTEM: Filesystem. (line 11) ! * HAVE_POST_DECREMENT: Addressing Modes. (line 11) ! * HAVE_POST_INCREMENT: Addressing Modes. (line 10) ! * HAVE_POST_MODIFY_DISP: Addressing Modes. (line 17) ! * HAVE_POST_MODIFY_REG: Addressing Modes. (line 23) ! * HAVE_PRE_DECREMENT: Addressing Modes. (line 9) ! * HAVE_PRE_INCREMENT: Addressing Modes. (line 8) ! * HAVE_PRE_MODIFY_DISP: Addressing Modes. (line 16) ! * HAVE_PRE_MODIFY_REG: Addressing Modes. (line 22) ! * HCmode: Machine Modes. (line 199) * HFmode: Machine Modes. (line 61) * high: Constants. (line 150) * HImode: Machine Modes. (line 29) ! * HImode, in insn: Insns. (line 268) ! * HONOR_REG_ALLOC_ORDER: Allocation Order. (line 36) * host configuration: Host Config. (line 6) * host functions: Host Common. (line 6) * host hooks: Host Common. (line 6) * host makefile fragment: Host Fragment. (line 6) * HOST_BIT_BUCKET: Filesystem. (line 51) * HOST_EXECUTABLE_SUFFIX: Filesystem. (line 45) ! * HOST_HOOKS_EXTRA_SIGNALS: Host Common. (line 11) ! * HOST_HOOKS_GT_PCH_ALLOC_GRANULARITY: Host Common. (line 43) ! * HOST_HOOKS_GT_PCH_GET_ADDRESS: Host Common. (line 15) ! * HOST_HOOKS_GT_PCH_USE_ADDRESS: Host Common. (line 24) * HOST_LACKS_INODE_NUMBERS: Filesystem. (line 89) * HOST_LONG_FORMAT: Host Misc. (line 45) * HOST_LONG_LONG_FORMAT: Host Misc. (line 41) * HOST_OBJECT_SUFFIX: Filesystem. (line 40) * HOST_PTR_PRINTF: Host Misc. (line 49) ! * HOT_TEXT_SECTION_NAME: Sections. (line 42) * HQmode: Machine Modes. (line 110) ! * i in constraint: Simple Constraints. (line 68) ! * I in constraint: Simple Constraints. (line 79) * identifier: Identifiers. (line 6) * IDENTIFIER_LENGTH: Identifiers. (line 22) * IDENTIFIER_NODE: Identifiers. (line 6) --- 48878,49384 ---- * GIMPLE instruction set: GIMPLE instruction set. (line 6) * GIMPLE sequences: GIMPLE sequences. (line 6) * GIMPLE statement iterators <1>: Maintaining the CFG. ! (line 34) ! * GIMPLE statement iterators: Basic Blocks. (line 78) * gimple_addresses_taken: Manipulating GIMPLE statements. ! (line 90) * GIMPLE_ASM: GIMPLE_ASM. (line 6) ! * gimple_asm_clobber_op: GIMPLE_ASM. (line 41) ! * gimple_asm_input_op: GIMPLE_ASM. (line 25) ! * gimple_asm_nclobbers: GIMPLE_ASM. (line 21) ! * gimple_asm_ninputs: GIMPLE_ASM. (line 15) ! * gimple_asm_noutputs: GIMPLE_ASM. (line 18) ! * gimple_asm_output_op: GIMPLE_ASM. (line 33) ! * gimple_asm_set_clobber_op: GIMPLE_ASM. (line 45) ! * gimple_asm_set_input_op: GIMPLE_ASM. (line 29) ! * gimple_asm_set_output_op: GIMPLE_ASM. (line 37) ! * gimple_asm_set_volatile: GIMPLE_ASM. (line 56) ! * gimple_asm_string: GIMPLE_ASM. (line 48) ! * gimple_asm_volatile_p: GIMPLE_ASM. (line 52) * GIMPLE_ASSIGN: GIMPLE_ASSIGN. (line 6) ! * gimple_assign_cast_p <1>: GIMPLE_ASSIGN. (line 105) ! * gimple_assign_cast_p: Logical Operators. (line 160) ! * gimple_assign_lhs: GIMPLE_ASSIGN. (line 63) ! * gimple_assign_lhs_ptr: GIMPLE_ASSIGN. (line 66) ! * gimple_assign_rhs1: GIMPLE_ASSIGN. (line 69) ! * gimple_assign_rhs1_ptr: GIMPLE_ASSIGN. (line 72) ! * gimple_assign_rhs2: GIMPLE_ASSIGN. (line 76) ! * gimple_assign_rhs2_ptr: GIMPLE_ASSIGN. (line 79) ! * gimple_assign_rhs3: GIMPLE_ASSIGN. (line 83) ! * gimple_assign_rhs3_ptr: GIMPLE_ASSIGN. (line 86) ! * gimple_assign_rhs_class: GIMPLE_ASSIGN. (line 58) ! * gimple_assign_rhs_code: GIMPLE_ASSIGN. (line 53) ! * gimple_assign_set_lhs: GIMPLE_ASSIGN. (line 90) ! * gimple_assign_set_rhs1: GIMPLE_ASSIGN. (line 93) ! * gimple_assign_set_rhs2: GIMPLE_ASSIGN. (line 97) ! * gimple_assign_set_rhs3: GIMPLE_ASSIGN. (line 101) * gimple_bb: Manipulating GIMPLE statements. ! (line 18) * GIMPLE_BIND: GIMPLE_BIND. (line 6) ! * gimple_bind_add_seq: GIMPLE_BIND. (line 36) ! * gimple_bind_add_stmt: GIMPLE_BIND. (line 32) ! * gimple_bind_append_vars: GIMPLE_BIND. (line 19) ! * gimple_bind_block: GIMPLE_BIND. (line 40) ! * gimple_bind_body: GIMPLE_BIND. (line 23) ! * gimple_bind_set_block: GIMPLE_BIND. (line 45) ! * gimple_bind_set_body: GIMPLE_BIND. (line 28) ! * gimple_bind_set_vars: GIMPLE_BIND. (line 15) ! * gimple_bind_vars: GIMPLE_BIND. (line 12) * gimple_block: Manipulating GIMPLE statements. ! (line 21) ! * gimple_build: GIMPLE API. (line 36) ! * gimple_build_nop: GIMPLE_NOP. (line 7) ! * gimple_build_omp_master: GIMPLE_OMP_MASTER. (line 7) ! * gimple_build_omp_ordered: GIMPLE_OMP_ORDERED. (line 7) ! * gimple_build_omp_return: GIMPLE_OMP_RETURN. (line 7) ! * gimple_build_omp_section: GIMPLE_OMP_SECTION. (line 7) * gimple_build_omp_sections_switch: GIMPLE_OMP_SECTIONS. ! (line 14) * gimple_build_wce: GIMPLE_WITH_CLEANUP_EXPR. ! (line 7) * GIMPLE_CALL: GIMPLE_CALL. (line 6) ! * gimple_call_arg: GIMPLE_CALL. (line 66) ! * gimple_call_arg_ptr: GIMPLE_CALL. (line 71) ! * gimple_call_chain: GIMPLE_CALL. (line 57) ! * gimple_call_copy_skip_args: GIMPLE_CALL. (line 92) ! * gimple_call_fn: GIMPLE_CALL. (line 38) ! * gimple_call_fndecl: GIMPLE_CALL. (line 46) ! * gimple_call_lhs: GIMPLE_CALL. (line 29) ! * gimple_call_lhs_ptr: GIMPLE_CALL. (line 32) ! * gimple_call_noreturn_p: GIMPLE_CALL. (line 88) ! * gimple_call_num_args: GIMPLE_CALL. (line 63) ! * gimple_call_return_type: GIMPLE_CALL. (line 54) ! * gimple_call_set_arg: GIMPLE_CALL. (line 76) ! * gimple_call_set_chain: GIMPLE_CALL. (line 60) ! * gimple_call_set_fn: GIMPLE_CALL. (line 42) ! * gimple_call_set_fndecl: GIMPLE_CALL. (line 51) ! * gimple_call_set_lhs: GIMPLE_CALL. (line 35) ! * gimple_call_set_tail: GIMPLE_CALL. (line 80) ! * gimple_call_tail_p: GIMPLE_CALL. (line 85) * GIMPLE_CATCH: GIMPLE_CATCH. (line 6) ! * gimple_catch_handler: GIMPLE_CATCH. (line 20) ! * gimple_catch_set_handler: GIMPLE_CATCH. (line 28) ! * gimple_catch_set_types: GIMPLE_CATCH. (line 24) ! * gimple_catch_types: GIMPLE_CATCH. (line 13) ! * gimple_catch_types_ptr: GIMPLE_CATCH. (line 16) * gimple_code: Manipulating GIMPLE statements. ! (line 15) * GIMPLE_COND: GIMPLE_COND. (line 6) ! * gimple_cond_code: GIMPLE_COND. (line 21) ! * gimple_cond_false_label: GIMPLE_COND. (line 60) ! * gimple_cond_lhs: GIMPLE_COND. (line 30) ! * gimple_cond_make_false: GIMPLE_COND. (line 64) ! * gimple_cond_make_true: GIMPLE_COND. (line 67) ! * gimple_cond_rhs: GIMPLE_COND. (line 38) ! * gimple_cond_set_code: GIMPLE_COND. (line 26) ! * gimple_cond_set_false_label: GIMPLE_COND. (line 56) ! * gimple_cond_set_lhs: GIMPLE_COND. (line 34) ! * gimple_cond_set_rhs: GIMPLE_COND. (line 42) ! * gimple_cond_set_true_label: GIMPLE_COND. (line 51) ! * gimple_cond_true_label: GIMPLE_COND. (line 46) ! * gimple_convert: GIMPLE API. (line 52) * gimple_copy: Manipulating GIMPLE statements. ! (line 147) * GIMPLE_DEBUG: GIMPLE_DEBUG. (line 6) * GIMPLE_DEBUG_BIND: GIMPLE_DEBUG. (line 6) ! * gimple_debug_bind_get_value: GIMPLE_DEBUG. (line 48) ! * gimple_debug_bind_get_value_ptr: GIMPLE_DEBUG. (line 53) ! * gimple_debug_bind_get_var: GIMPLE_DEBUG. (line 45) ! * gimple_debug_bind_has_value_p: GIMPLE_DEBUG. (line 70) ! * gimple_debug_bind_p: Logical Operators. (line 164) ! * gimple_debug_bind_reset_value: GIMPLE_DEBUG. (line 66) ! * gimple_debug_bind_set_value: GIMPLE_DEBUG. (line 62) ! * gimple_debug_bind_set_var: GIMPLE_DEBUG. (line 58) * gimple_def_ops: Manipulating GIMPLE statements. ! (line 94) * GIMPLE_EH_FILTER: GIMPLE_EH_FILTER. (line 6) ! * gimple_eh_filter_failure: GIMPLE_EH_FILTER. (line 19) ! * gimple_eh_filter_set_failure: GIMPLE_EH_FILTER. (line 29) ! * gimple_eh_filter_set_types: GIMPLE_EH_FILTER. (line 24) ! * gimple_eh_filter_types: GIMPLE_EH_FILTER. (line 12) ! * gimple_eh_filter_types_ptr: GIMPLE_EH_FILTER. (line 15) ! * gimple_eh_must_not_throw_fndecl: GIMPLE_EH_FILTER. (line 34) ! * gimple_eh_must_not_throw_set_fndecl: GIMPLE_EH_FILTER. (line 38) * gimple_expr_code: Manipulating GIMPLE statements. ! (line 31) * gimple_expr_type: Manipulating GIMPLE statements. ! (line 24) * GIMPLE_GOTO: GIMPLE_GOTO. (line 6) ! * gimple_goto_dest: GIMPLE_GOTO. (line 10) ! * gimple_goto_set_dest: GIMPLE_GOTO. (line 13) * gimple_has_mem_ops: Manipulating GIMPLE statements. ! (line 72) * gimple_has_ops: Manipulating GIMPLE statements. ! (line 69) * gimple_has_volatile_ops: Manipulating GIMPLE statements. ! (line 134) * GIMPLE_LABEL: GIMPLE_LABEL. (line 6) ! * gimple_label_label: GIMPLE_LABEL. (line 11) ! * gimple_label_set_label: GIMPLE_LABEL. (line 14) * gimple_loaded_syms: Manipulating GIMPLE statements. ! (line 122) * gimple_locus: Manipulating GIMPLE statements. ! (line 42) * gimple_locus_empty_p: Manipulating GIMPLE statements. ! (line 48) * gimple_modified_p: Manipulating GIMPLE statements. ! (line 130) * gimple_no_warning_p: Manipulating GIMPLE statements. ! (line 51) ! * GIMPLE_NOP: GIMPLE_NOP. (line 6) ! * gimple_nop_p: GIMPLE_NOP. (line 10) * gimple_num_ops <1>: Manipulating GIMPLE statements. ! (line 75) ! * gimple_num_ops: Logical Operators. (line 78) * GIMPLE_OMP_ATOMIC_LOAD: GIMPLE_OMP_ATOMIC_LOAD. (line 6) * gimple_omp_atomic_load_lhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 18) * gimple_omp_atomic_load_rhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 26) * gimple_omp_atomic_load_set_lhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 14) * gimple_omp_atomic_load_set_rhs: GIMPLE_OMP_ATOMIC_LOAD. ! (line 22) * GIMPLE_OMP_ATOMIC_STORE: GIMPLE_OMP_ATOMIC_STORE. (line 6) * gimple_omp_atomic_store_set_val: GIMPLE_OMP_ATOMIC_STORE. ! (line 13) * gimple_omp_atomic_store_val: GIMPLE_OMP_ATOMIC_STORE. ! (line 17) * gimple_omp_body: GIMPLE_OMP_PARALLEL. ! (line 24) * GIMPLE_OMP_CONTINUE: GIMPLE_OMP_CONTINUE. (line 6) * gimple_omp_continue_control_def: GIMPLE_OMP_CONTINUE. ! (line 14) * gimple_omp_continue_control_def_ptr: GIMPLE_OMP_CONTINUE. ! (line 19) * gimple_omp_continue_control_use: GIMPLE_OMP_CONTINUE. ! (line 28) * gimple_omp_continue_control_use_ptr: GIMPLE_OMP_CONTINUE. ! (line 33) * gimple_omp_continue_set_control_def: GIMPLE_OMP_CONTINUE. ! (line 23) * gimple_omp_continue_set_control_use: GIMPLE_OMP_CONTINUE. ! (line 37) * GIMPLE_OMP_CRITICAL: GIMPLE_OMP_CRITICAL. (line 6) * gimple_omp_critical_name: GIMPLE_OMP_CRITICAL. ! (line 14) * gimple_omp_critical_name_ptr: GIMPLE_OMP_CRITICAL. ! (line 18) * gimple_omp_critical_set_name: GIMPLE_OMP_CRITICAL. ! (line 23) * GIMPLE_OMP_FOR: GIMPLE_OMP_FOR. (line 6) ! * gimple_omp_for_clauses: GIMPLE_OMP_FOR. (line 18) ! * gimple_omp_for_clauses_ptr: GIMPLE_OMP_FOR. (line 21) ! * gimple_omp_for_cond: GIMPLE_OMP_FOR. (line 81) ! * gimple_omp_for_final: GIMPLE_OMP_FOR. (line 49) ! * gimple_omp_for_final_ptr: GIMPLE_OMP_FOR. (line 52) ! * gimple_omp_for_incr: GIMPLE_OMP_FOR. (line 59) ! * gimple_omp_for_incr_ptr: GIMPLE_OMP_FOR. (line 62) ! * gimple_omp_for_index: GIMPLE_OMP_FOR. (line 29) ! * gimple_omp_for_index_ptr: GIMPLE_OMP_FOR. (line 32) ! * gimple_omp_for_initial: GIMPLE_OMP_FOR. (line 39) ! * gimple_omp_for_initial_ptr: GIMPLE_OMP_FOR. (line 42) ! * gimple_omp_for_pre_body: GIMPLE_OMP_FOR. (line 68) ! * gimple_omp_for_set_clauses: GIMPLE_OMP_FOR. (line 25) ! * gimple_omp_for_set_cond: GIMPLE_OMP_FOR. (line 78) ! * gimple_omp_for_set_final: GIMPLE_OMP_FOR. (line 56) ! * gimple_omp_for_set_incr: GIMPLE_OMP_FOR. (line 65) ! * gimple_omp_for_set_index: GIMPLE_OMP_FOR. (line 36) ! * gimple_omp_for_set_initial: GIMPLE_OMP_FOR. (line 46) ! * gimple_omp_for_set_pre_body: GIMPLE_OMP_FOR. (line 73) * GIMPLE_OMP_MASTER: GIMPLE_OMP_MASTER. (line 6) * GIMPLE_OMP_ORDERED: GIMPLE_OMP_ORDERED. (line 6) * GIMPLE_OMP_PARALLEL: GIMPLE_OMP_PARALLEL. (line 6) * gimple_omp_parallel_child_fn: GIMPLE_OMP_PARALLEL. ! (line 44) * gimple_omp_parallel_child_fn_ptr: GIMPLE_OMP_PARALLEL. ! (line 49) * gimple_omp_parallel_clauses: GIMPLE_OMP_PARALLEL. ! (line 31) * gimple_omp_parallel_clauses_ptr: GIMPLE_OMP_PARALLEL. ! (line 35) * gimple_omp_parallel_combined_p: GIMPLE_OMP_PARALLEL. ! (line 16) * gimple_omp_parallel_data_arg: GIMPLE_OMP_PARALLEL. ! (line 58) * gimple_omp_parallel_data_arg_ptr: GIMPLE_OMP_PARALLEL. ! (line 63) * gimple_omp_parallel_set_child_fn: GIMPLE_OMP_PARALLEL. ! (line 54) * gimple_omp_parallel_set_clauses: GIMPLE_OMP_PARALLEL. ! (line 39) * gimple_omp_parallel_set_combined_p: GIMPLE_OMP_PARALLEL. ! (line 20) * gimple_omp_parallel_set_data_arg: GIMPLE_OMP_PARALLEL. ! (line 67) * GIMPLE_OMP_RETURN: GIMPLE_OMP_RETURN. (line 6) ! * gimple_omp_return_nowait_p: GIMPLE_OMP_RETURN. (line 14) ! * gimple_omp_return_set_nowait: GIMPLE_OMP_RETURN. (line 11) * GIMPLE_OMP_SECTION: GIMPLE_OMP_SECTION. (line 6) + * gimple_omp_section_last_p: GIMPLE_OMP_SECTION. (line 12) + * gimple_omp_section_set_last: GIMPLE_OMP_SECTION. (line 16) * GIMPLE_OMP_SECTIONS: GIMPLE_OMP_SECTIONS. (line 6) * gimple_omp_sections_clauses: GIMPLE_OMP_SECTIONS. ! (line 30) * gimple_omp_sections_clauses_ptr: GIMPLE_OMP_SECTIONS. ! (line 33) * gimple_omp_sections_control: GIMPLE_OMP_SECTIONS. ! (line 17) * gimple_omp_sections_control_ptr: GIMPLE_OMP_SECTIONS. ! (line 21) * gimple_omp_sections_set_clauses: GIMPLE_OMP_SECTIONS. ! (line 37) * gimple_omp_sections_set_control: GIMPLE_OMP_SECTIONS. (line 26) + * gimple_omp_set_body: GIMPLE_OMP_PARALLEL. + (line 28) * GIMPLE_OMP_SINGLE: GIMPLE_OMP_SINGLE. (line 6) ! * gimple_omp_single_clauses: GIMPLE_OMP_SINGLE. (line 14) ! * gimple_omp_single_clauses_ptr: GIMPLE_OMP_SINGLE. (line 17) ! * gimple_omp_single_set_clauses: GIMPLE_OMP_SINGLE. (line 21) * gimple_op <1>: Manipulating GIMPLE statements. ! (line 81) ! * gimple_op: Logical Operators. (line 81) * gimple_op_ptr: Manipulating GIMPLE statements. ! (line 84) ! * gimple_ops <1>: Manipulating GIMPLE statements. ! (line 78) ! * gimple_ops: Logical Operators. (line 84) * GIMPLE_PHI: GIMPLE_PHI. (line 6) ! * gimple_phi_arg <1>: SSA. (line 63) ! * gimple_phi_arg: GIMPLE_PHI. (line 25) ! * gimple_phi_arg_def: SSA. (line 69) ! * gimple_phi_arg_edge: SSA. (line 66) ! * gimple_phi_capacity: GIMPLE_PHI. (line 7) ! * gimple_phi_num_args <1>: SSA. (line 59) ! * gimple_phi_num_args: GIMPLE_PHI. (line 11) ! * gimple_phi_result <1>: SSA. (line 56) ! * gimple_phi_result: GIMPLE_PHI. (line 16) ! * gimple_phi_result_ptr: GIMPLE_PHI. (line 19) ! * gimple_phi_set_arg: GIMPLE_PHI. (line 30) ! * gimple_phi_set_result: GIMPLE_PHI. (line 22) * gimple_plf: Manipulating GIMPLE statements. ! (line 66) * GIMPLE_RESX: GIMPLE_RESX. (line 6) ! * gimple_resx_region: GIMPLE_RESX. (line 13) ! * gimple_resx_set_region: GIMPLE_RESX. (line 16) * GIMPLE_RETURN: GIMPLE_RETURN. (line 6) ! * gimple_return_retval: GIMPLE_RETURN. (line 10) ! * gimple_return_set_retval: GIMPLE_RETURN. (line 14) ! * gimple_seq_add_seq: GIMPLE sequences. (line 32) ! * gimple_seq_add_stmt: GIMPLE sequences. (line 26) ! * gimple_seq_alloc: GIMPLE sequences. (line 62) ! * gimple_seq_copy: GIMPLE sequences. (line 67) ! * gimple_seq_deep_copy: GIMPLE sequences. (line 37) ! * gimple_seq_empty_p: GIMPLE sequences. (line 70) ! * gimple_seq_first: GIMPLE sequences. (line 44) ! * gimple_seq_init: GIMPLE sequences. (line 59) ! * gimple_seq_last: GIMPLE sequences. (line 47) ! * gimple_seq_reverse: GIMPLE sequences. (line 40) ! * gimple_seq_set_first: GIMPLE sequences. (line 55) ! * gimple_seq_set_last: GIMPLE sequences. (line 51) ! * gimple_seq_singleton_p: GIMPLE sequences. (line 79) * gimple_set_block: Manipulating GIMPLE statements. ! (line 39) * gimple_set_def_ops: Manipulating GIMPLE statements. ! (line 98) * gimple_set_has_volatile_ops: Manipulating GIMPLE statements. ! (line 138) * gimple_set_locus: Manipulating GIMPLE statements. ! (line 45) * gimple_set_op: Manipulating GIMPLE statements. ! (line 87) * gimple_set_plf: Manipulating GIMPLE statements. ! (line 62) * gimple_set_use_ops: Manipulating GIMPLE statements. ! (line 105) * gimple_set_vdef_ops: Manipulating GIMPLE statements. ! (line 119) * gimple_set_visited: Manipulating GIMPLE statements. ! (line 55) * gimple_set_vuse_ops: Manipulating GIMPLE statements. ! (line 112) ! * gimple_simplify: GIMPLE API. (line 8) * gimple_statement_with_ops: Tuple representation. (line 96) * gimple_stored_syms: Manipulating GIMPLE statements. ! (line 126) * GIMPLE_SWITCH: GIMPLE_SWITCH. (line 6) ! * gimple_switch_default_label: GIMPLE_SWITCH. (line 43) ! * gimple_switch_index: GIMPLE_SWITCH. (line 25) ! * gimple_switch_label: GIMPLE_SWITCH. (line 33) ! * gimple_switch_num_labels: GIMPLE_SWITCH. (line 16) ! * gimple_switch_set_default_label: GIMPLE_SWITCH. (line 47) ! * gimple_switch_set_index: GIMPLE_SWITCH. (line 29) ! * gimple_switch_set_label: GIMPLE_SWITCH. (line 38) ! * gimple_switch_set_num_labels: GIMPLE_SWITCH. (line 21) * GIMPLE_TRY: GIMPLE_TRY. (line 6) ! * gimple_try_catch_is_cleanup: GIMPLE_TRY. (line 20) ! * gimple_try_cleanup: GIMPLE_TRY. (line 27) ! * gimple_try_eval: GIMPLE_TRY. (line 23) ! * gimple_try_kind: GIMPLE_TRY. (line 16) ! * gimple_try_set_catch_is_cleanup: GIMPLE_TRY. (line 32) ! * gimple_try_set_cleanup: GIMPLE_TRY. (line 40) ! * gimple_try_set_eval: GIMPLE_TRY. (line 35) * gimple_use_ops: Manipulating GIMPLE statements. ! (line 101) * gimple_vdef_ops: Manipulating GIMPLE statements. ! (line 115) * gimple_visited_p: Manipulating GIMPLE statements. ! (line 58) * gimple_vuse_ops: Manipulating GIMPLE statements. ! (line 108) * gimple_wce_cleanup: GIMPLE_WITH_CLEANUP_EXPR. ! (line 11) * gimple_wce_cleanup_eh_only: GIMPLE_WITH_CLEANUP_EXPR. ! (line 18) * gimple_wce_set_cleanup: GIMPLE_WITH_CLEANUP_EXPR. ! (line 15) * gimple_wce_set_cleanup_eh_only: GIMPLE_WITH_CLEANUP_EXPR. ! (line 22) * GIMPLE_WITH_CLEANUP_EXPR: GIMPLE_WITH_CLEANUP_EXPR. (line 6) * gimplification <1>: Gimplification pass. (line 6) ! * gimplification: Parsing pass. (line 14) ! * gimplifier: Parsing pass. (line 14) ! * gimplify_assign: GIMPLE_ASSIGN. (line 43) * gimplify_expr: Gimplification pass. (line 18) * gimplify_function_tree: Gimplification pass. (line 18) * GLOBAL_INIT_PRIORITY: Functions for C++. (line 141) * global_regs: Register Basics. (line 59) ! * GO_IF_LEGITIMATE_ADDRESS: Addressing Modes. (line 91) * greater than: Comparisons. (line 60) ! * gsi_after_labels: Sequence iterators. (line 76) ! * gsi_bb: Sequence iterators. (line 83) * gsi_commit_edge_inserts <1>: Maintaining the CFG. ! (line 107) ! * gsi_commit_edge_inserts: Sequence iterators. (line 194) ! * gsi_commit_one_edge_insert: Sequence iterators. (line 190) * gsi_end_p <1>: Maintaining the CFG. ! (line 49) ! * gsi_end_p: Sequence iterators. (line 60) ! * gsi_for_stmt: Sequence iterators. (line 157) * gsi_insert_after <1>: Maintaining the CFG. ! (line 61) ! * gsi_insert_after: Sequence iterators. (line 147) * gsi_insert_before <1>: Maintaining the CFG. ! (line 67) ! * gsi_insert_before: Sequence iterators. (line 136) * gsi_insert_on_edge <1>: Maintaining the CFG. ! (line 107) ! * gsi_insert_on_edge: Sequence iterators. (line 174) ! * gsi_insert_on_edge_immediate: Sequence iterators. (line 185) ! * gsi_insert_seq_after: Sequence iterators. (line 154) ! * gsi_insert_seq_before: Sequence iterators. (line 143) ! * gsi_insert_seq_on_edge: Sequence iterators. (line 179) * gsi_last <1>: Maintaining the CFG. ! (line 45) ! * gsi_last: Sequence iterators. (line 50) ! * gsi_last_bb: Sequence iterators. (line 56) ! * gsi_link_after: Sequence iterators. (line 115) ! * gsi_link_before: Sequence iterators. (line 105) ! * gsi_link_seq_after: Sequence iterators. (line 110) ! * gsi_link_seq_before: Sequence iterators. (line 99) ! * gsi_move_after: Sequence iterators. (line 161) ! * gsi_move_before: Sequence iterators. (line 166) ! * gsi_move_to_bb_end: Sequence iterators. (line 171) * gsi_next <1>: Maintaining the CFG. ! (line 53) ! * gsi_next: Sequence iterators. (line 66) ! * gsi_one_before_end_p: Sequence iterators. (line 63) * gsi_prev <1>: Maintaining the CFG. ! (line 57) ! * gsi_prev: Sequence iterators. (line 69) * gsi_remove <1>: Maintaining the CFG. ! (line 73) ! * gsi_remove: Sequence iterators. (line 90) ! * gsi_replace: Sequence iterators. (line 130) ! * gsi_seq: Sequence iterators. (line 86) ! * gsi_split_seq_after: Sequence iterators. (line 120) ! * gsi_split_seq_before: Sequence iterators. (line 125) * gsi_start <1>: Maintaining the CFG. ! (line 41) ! * gsi_start: Sequence iterators. (line 40) ! * gsi_start_bb: Sequence iterators. (line 46) ! * gsi_stmt: Sequence iterators. (line 72) ! * gsi_stmt_ptr: Sequence iterators. (line 80) * gt: Comparisons. (line 60) ! * gt and attributes: Expressions. (line 85) * GT_EXPR: Unary and Binary Expressions. (line 6) ! * gtu: Comparisons. (line 64) ! * gtu and attributes: Expressions. (line 85) ! * GTY: Type Information. (line 6) ! * H in constraint: Simple Constraints. (line 98) ! * HAmode: Machine Modes. (line 147) ! * HANDLE_PRAGMA_PACK_WITH_EXPANSION: Misc. (line 444) * HANDLER: Statements for C++. (line 6) * HANDLER_BODY: Statements for C++. (line 6) * HANDLER_PARMS: Statements for C++. (line 6) * hard registers: Regs and Memory. (line 9) ! * HARD_FRAME_POINTER_IS_ARG_POINTER: Frame Registers. (line 58) ! * HARD_FRAME_POINTER_IS_FRAME_POINTER: Frame Registers. (line 51) ! * HARD_FRAME_POINTER_REGNUM: Frame Registers. (line 20) ! * HARD_REGNO_CALL_PART_CLOBBERED: Register Basics. (line 53) ! * HARD_REGNO_CALLER_SAVE_MODE: Caller Saves. (line 11) * HARD_REGNO_MODE_OK: Values in Registers. ! (line 58) * HARD_REGNO_NREGS: Values in Registers. ! (line 11) * HARD_REGNO_NREGS_HAS_PADDING: Values in Registers. ! (line 25) * HARD_REGNO_NREGS_WITH_PADDING: Values in Registers. ! (line 43) * HARD_REGNO_RENAME_OK: Values in Registers. ! (line 119) * HAS_INIT_SECTION: Macros for Initialization. ! (line 19) ! * HAS_LONG_COND_BRANCH: Misc. (line 9) ! * HAS_LONG_UNCOND_BRANCH: Misc. (line 18) * HAVE_DOS_BASED_FILE_SYSTEM: Filesystem. (line 11) ! * HAVE_POST_DECREMENT: Addressing Modes. (line 12) ! * HAVE_POST_INCREMENT: Addressing Modes. (line 11) ! * HAVE_POST_MODIFY_DISP: Addressing Modes. (line 18) ! * HAVE_POST_MODIFY_REG: Addressing Modes. (line 24) ! * HAVE_PRE_DECREMENT: Addressing Modes. (line 10) ! * HAVE_PRE_INCREMENT: Addressing Modes. (line 9) ! * HAVE_PRE_MODIFY_DISP: Addressing Modes. (line 17) ! * HAVE_PRE_MODIFY_REG: Addressing Modes. (line 23) ! * HCmode: Machine Modes. (line 200) * HFmode: Machine Modes. (line 61) * high: Constants. (line 150) * HImode: Machine Modes. (line 29) ! * HImode, in insn: Insns. (line 272) ! * HONOR_REG_ALLOC_ORDER: Allocation Order. (line 37) * host configuration: Host Config. (line 6) * host functions: Host Common. (line 6) * host hooks: Host Common. (line 6) * host makefile fragment: Host Fragment. (line 6) * HOST_BIT_BUCKET: Filesystem. (line 51) * HOST_EXECUTABLE_SUFFIX: Filesystem. (line 45) ! * HOST_HOOKS_EXTRA_SIGNALS: Host Common. (line 12) ! * HOST_HOOKS_GT_PCH_ALLOC_GRANULARITY: Host Common. (line 45) ! * HOST_HOOKS_GT_PCH_GET_ADDRESS: Host Common. (line 17) ! * HOST_HOOKS_GT_PCH_USE_ADDRESS: Host Common. (line 26) * HOST_LACKS_INODE_NUMBERS: Filesystem. (line 89) * HOST_LONG_FORMAT: Host Misc. (line 45) * HOST_LONG_LONG_FORMAT: Host Misc. (line 41) * HOST_OBJECT_SUFFIX: Filesystem. (line 40) * HOST_PTR_PRINTF: Host Misc. (line 49) ! * HOT_TEXT_SECTION_NAME: Sections. (line 43) * HQmode: Machine Modes. (line 110) ! * I in constraint: Simple Constraints. (line 81) ! * i in constraint: Simple Constraints. (line 70) * identifier: Identifiers. (line 6) * IDENTIFIER_LENGTH: Identifiers. (line 22) * IDENTIFIER_NODE: Identifiers. (line 6) *************** Concept Index *** 48945,49005 **** * IDENTIFIER_TYPENAME_P: Identifiers. (line 33) * IEEE 754-2008: Decimal float library routines. (line 6) - * IFCVT_MACHDEP_INIT: Misc. (line 568) - * IFCVT_MODIFY_CANCEL: Misc. (line 562) - * IFCVT_MODIFY_FINAL: Misc. (line 556) - * IFCVT_MODIFY_INSN: Misc. (line 550) - * IFCVT_MODIFY_MULTIPLE_TESTS: Misc. (line 542) - * IFCVT_MODIFY_TESTS: Misc. (line 532) * IF_COND: Statements for C++. (line 6) * IF_STMT: Statements for C++. (line 6) * if_then_else: Comparisons. (line 80) * if_then_else and attributes: Expressions. (line 32) * if_then_else usage: Side Effects. (line 56) * IMAGPART_EXPR: Unary and Binary Expressions. (line 6) ! * Immediate Uses: SSA Operands. (line 258) * immediate_operand: Machine-Independent Predicates. ! (line 10) ! * IMMEDIATE_PREFIX: Instruction Output. (line 153) * include: Including Patterns. (line 6) ! * INCLUDE_DEFAULTS: Driver. (line 331) ! * inclusive-or, bitwise: Arithmetic. (line 163) ! * INCOMING_FRAME_SP_OFFSET: Frame Layout. (line 179) ! * INCOMING_REGNO: Register Basics. (line 86) ! * INCOMING_REG_PARM_STACK_SPACE: Stack Arguments. (line 73) ! * INCOMING_RETURN_ADDR_RTX: Frame Layout. (line 135) ! * INCOMING_STACK_BOUNDARY: Storage Layout. (line 154) ! * INDEX_REG_CLASS: Register Classes. (line 140) ! * indirect_jump instruction pattern: Standard Names. (line 1454) * indirect_operand: Machine-Independent Predicates. ! (line 70) * INDIRECT_REF: Storage References. (line 6) ! * initialization routines: Initialization. (line 6) ! * INITIAL_ELIMINATION_OFFSET: Elimination. (line 84) ! * INITIAL_FRAME_ADDRESS_RTX: Frame Layout. (line 77) ! * INITIAL_FRAME_POINTER_OFFSET: Elimination. (line 34) ! * INIT_ARRAY_SECTION_ASM_OP: Sections. (line 106) ! * INIT_CUMULATIVE_ARGS: Register Arguments. (line 161) ! * INIT_CUMULATIVE_INCOMING_ARGS: Register Arguments. (line 189) ! * INIT_CUMULATIVE_LIBCALL_ARGS: Register Arguments. (line 183) ! * INIT_ENVIRONMENT: Driver. (line 309) ! * INIT_EXPANDERS: Per-Function Data. (line 36) * INIT_EXPR: Unary and Binary Expressions. (line 6) ! * init_machine_status: Per-Function Data. (line 42) * init_one_libfunc: Library Calls. (line 15) - * INIT_SECTION_ASM_OP: Sections. (line 90) * INIT_SECTION_ASM_OP <1>: Macros for Initialization. ! (line 9) * inlining: Target Attributes. (line 95) * insert_insn_on_edge: Maintaining the CFG. ! (line 105) * insn: Insns. (line 63) * insn and /f: Flags. (line 107) * insn and /j: Flags. (line 157) * insn and /s: Flags. (line 49) - * insn and /s <1>: Flags. (line 148) * insn and /u: Flags. (line 39) * insn and /v: Flags. (line 44) * insn attributes: Insn Attributes. (line 6) --- 49387,49452 ---- * IDENTIFIER_TYPENAME_P: Identifiers. (line 33) * IEEE 754-2008: Decimal float library routines. (line 6) * IF_COND: Statements for C++. (line 6) * IF_STMT: Statements for C++. (line 6) * if_then_else: Comparisons. (line 80) * if_then_else and attributes: Expressions. (line 32) * if_then_else usage: Side Effects. (line 56) + * IFCVT_MACHDEP_INIT: Misc. (line 569) + * IFCVT_MODIFY_CANCEL: Misc. (line 563) + * IFCVT_MODIFY_FINAL: Misc. (line 557) + * IFCVT_MODIFY_INSN: Misc. (line 551) + * IFCVT_MODIFY_MULTIPLE_TESTS: Misc. (line 544) + * IFCVT_MODIFY_TESTS: Misc. (line 533) * IMAGPART_EXPR: Unary and Binary Expressions. (line 6) ! * Immediate Uses: SSA Operands. (line 261) * immediate_operand: Machine-Independent Predicates. ! (line 11) ! * IMMEDIATE_PREFIX: Instruction Output. (line 155) ! * in_struct: Flags. (line 245) ! * in_struct, in code_label and note: Flags. (line 59) ! * in_struct, in insn and jump_insn and call_insn: Flags. (line 49) ! * in_struct, in insn, call_insn, jump_insn and jump_table_data: Flags. ! (line 148) ! * in_struct, in subreg: Flags. (line 187) * include: Including Patterns. (line 6) ! * INCLUDE_DEFAULTS: Driver. (line 332) ! * inclusive-or, bitwise: Arithmetic. (line 162) ! * INCOMING_FRAME_SP_OFFSET: Frame Layout. (line 181) ! * INCOMING_REG_PARM_STACK_SPACE: Stack Arguments. (line 74) ! * INCOMING_REGNO: Register Basics. (line 87) ! * INCOMING_RETURN_ADDR_RTX: Frame Layout. (line 137) ! * INCOMING_STACK_BOUNDARY: Storage Layout. (line 156) ! * INDEX_REG_CLASS: Register Classes. (line 143) ! * indirect_jump instruction pattern: Standard Names. (line 1461) * indirect_operand: Machine-Independent Predicates. ! (line 71) * INDIRECT_REF: Storage References. (line 6) ! * INIT_ARRAY_SECTION_ASM_OP: Sections. (line 107) ! * INIT_CUMULATIVE_ARGS: Register Arguments. (line 164) ! * INIT_CUMULATIVE_INCOMING_ARGS: Register Arguments. (line 191) ! * INIT_CUMULATIVE_LIBCALL_ARGS: Register Arguments. (line 185) ! * INIT_ENVIRONMENT: Driver. (line 310) ! * INIT_EXPANDERS: Per-Function Data. (line 39) * INIT_EXPR: Unary and Binary Expressions. (line 6) ! * init_machine_status: Per-Function Data. (line 45) * init_one_libfunc: Library Calls. (line 15) * INIT_SECTION_ASM_OP <1>: Macros for Initialization. ! (line 10) ! * INIT_SECTION_ASM_OP: Sections. (line 91) ! * INITIAL_ELIMINATION_OFFSET: Elimination. (line 85) ! * INITIAL_FRAME_ADDRESS_RTX: Frame Layout. (line 79) ! * INITIAL_FRAME_POINTER_OFFSET: Elimination. (line 35) ! * initialization routines: Initialization. (line 6) * inlining: Target Attributes. (line 95) * insert_insn_on_edge: Maintaining the CFG. ! (line 107) * insn: Insns. (line 63) * insn and /f: Flags. (line 107) * insn and /j: Flags. (line 157) * insn and /s: Flags. (line 49) * insn and /u: Flags. (line 39) * insn and /v: Flags. (line 44) * insn attributes: Insn Attributes. (line 6) *************** Concept Index *** 49011,49045 **** * insn splitting: Insn Splitting. (line 6) * insn-attr.h: Defining Attributes. (line 34) - * insns: Insns. (line 6) - * insns, generating: RTL Template. (line 6) - * insns, recognizing: RTL Template. (line 6) * INSN_ANNULLED_BRANCH_P: Flags. (line 39) ! * INSN_CODE: Insns. (line 295) * INSN_DELETED_P: Flags. (line 44) * INSN_FROM_TARGET_P: Flags. (line 49) ! * insn_list: Insns. (line 540) ! * INSN_REFERENCES_ARE_DELAYED: Misc. (line 469) ! * INSN_SETS_ARE_DELAYED: Misc. (line 458) * INSN_UID: Insns. (line 23) ! * INSN_VAR_LOCATION: Insns. (line 236) * instruction attributes: Insn Attributes. (line 6) * instruction latency time: Processor pipeline description. (line 6) - * instruction latency time <1>: Processor pipeline description. - (line 105) - * instruction latency time <2>: Processor pipeline description. - (line 196) * instruction patterns: Patterns. (line 6) * instruction splitting: Insn Splitting. (line 6) ! * insv instruction pattern: Standard Names. (line 1239) ! * insvM instruction pattern: Standard Names. (line 1191) ! * insvmisalignM instruction pattern: Standard Names. (line 1201) * int iterators in .md files: Int Iterators. (line 6) ! * INT16_TYPE: Type Layout. (line 216) ! * INT32_TYPE: Type Layout. (line 217) ! * INT64_TYPE: Type Layout. (line 218) ! * INT8_TYPE: Type Layout. (line 215) * INTEGER_CST: Constant expressions. (line 6) * INTEGER_TYPE: Types. (line 6) --- 49458,49497 ---- * insn splitting: Insn Splitting. (line 6) * insn-attr.h: Defining Attributes. (line 34) * INSN_ANNULLED_BRANCH_P: Flags. (line 39) ! * INSN_CODE: Insns. (line 299) * INSN_DELETED_P: Flags. (line 44) * INSN_FROM_TARGET_P: Flags. (line 49) ! * insn_list: Insns. (line 548) ! * INSN_REFERENCES_ARE_DELAYED: Misc. (line 471) ! * INSN_SETS_ARE_DELAYED: Misc. (line 460) * INSN_UID: Insns. (line 23) ! * INSN_VAR_LOCATION: Insns. (line 239) ! * insns: Insns. (line 6) ! * insns, generating: RTL Template. (line 6) ! * insns, recognizing: RTL Template. (line 6) * instruction attributes: Insn Attributes. (line 6) * instruction latency time: Processor pipeline description. (line 6) * instruction patterns: Patterns. (line 6) * instruction splitting: Insn Splitting. (line 6) ! * insv instruction pattern: Standard Names. (line 1245) ! * insvM instruction pattern: Standard Names. (line 1197) ! * insvmisalignM instruction pattern: Standard Names. (line 1207) * int iterators in .md files: Int Iterators. (line 6) ! * INT16_TYPE: Type Layout. (line 217) ! * INT32_TYPE: Type Layout. (line 218) ! * INT64_TYPE: Type Layout. (line 219) ! * INT8_TYPE: Type Layout. (line 216) ! * INT_FAST16_TYPE: Type Layout. (line 233) ! * INT_FAST32_TYPE: Type Layout. (line 234) ! * INT_FAST64_TYPE: Type Layout. (line 235) ! * INT_FAST8_TYPE: Type Layout. (line 232) ! * INT_LEAST16_TYPE: Type Layout. (line 225) ! * INT_LEAST32_TYPE: Type Layout. (line 226) ! * INT_LEAST64_TYPE: Type Layout. (line 227) ! * INT_LEAST8_TYPE: Type Layout. (line 224) ! * INT_TYPE_SIZE: Type Layout. (line 12) * INTEGER_CST: Constant expressions. (line 6) * INTEGER_TYPE: Types. (line 6) *************** Concept Index *** 49047,49122 **** * interfacing to GCC output: Interface. (line 6) * interlock delays: Processor pipeline description. (line 6) ! * intermediate representation lowering: Parsing pass. (line 13) ! * INTMAX_TYPE: Type Layout. (line 192) ! * INTPTR_TYPE: Type Layout. (line 239) * introduction: Top. (line 6) - * INT_FAST16_TYPE: Type Layout. (line 232) - * INT_FAST32_TYPE: Type Layout. (line 233) - * INT_FAST64_TYPE: Type Layout. (line 234) - * INT_FAST8_TYPE: Type Layout. (line 231) - * INT_LEAST16_TYPE: Type Layout. (line 224) - * INT_LEAST32_TYPE: Type Layout. (line 225) - * INT_LEAST64_TYPE: Type Layout. (line 226) - * INT_LEAST8_TYPE: Type Layout. (line 223) - * INT_TYPE_SIZE: Type Layout. (line 11) * INVOKE__main: Macros for Initialization. ! (line 50) ! * in_struct: Flags. (line 245) ! * in_struct, in code_label and note: Flags. (line 59) ! * in_struct, in insn and jump_insn and call_insn: Flags. (line 49) ! * in_struct, in insn, call_insn, jump_insn and jump_table_data: Flags. ! (line 148) ! * in_struct, in subreg: Flags. (line 187) ! * ior: Arithmetic. (line 163) * ior and attributes: Expressions. (line 50) * ior, canonicalization of: Insn Canonicalizations. ! (line 51) ! * iorM3 instruction pattern: Standard Names. (line 301) ! * IRA_HARD_REGNO_ADD_COST_MULTIPLIER: Allocation Order. (line 44) ! * IS_ASM_LOGICAL_LINE_SEPARATOR: Data Output. (line 123) ! * is_gimple_addressable: Logical Operators. (line 113) ! * is_gimple_asm_val: Logical Operators. (line 117) ! * is_gimple_assign: Logical Operators. (line 149) ! * is_gimple_call: Logical Operators. (line 152) ! * is_gimple_call_addr: Logical Operators. (line 120) ! * is_gimple_constant: Logical Operators. (line 128) ! * is_gimple_debug: Logical Operators. (line 155) ! * is_gimple_ip_invariant: Logical Operators. (line 137) ! * is_gimple_ip_invariant_address: Logical Operators. (line 142) ! * is_gimple_mem_ref_addr: Logical Operators. (line 124) ! * is_gimple_min_invariant: Logical Operators. (line 131) ! * is_gimple_omp: Logical Operators. (line 166) ! * is_gimple_val: Logical Operators. (line 107) * iterators in .md files: Iterators. (line 6) * IV analysis on GIMPLE: Scalar evolutions. (line 6) * IV analysis on RTL: loop-iv. (line 6) * JMP_BUF_SIZE: Exception Region Output. ! (line 83) * jump: Flags. (line 286) ! * jump instruction pattern: Standard Names. (line 1332) * jump instruction patterns: Jump Patterns. (line 6) * jump instructions and set: Side Effects. (line 56) * jump, in call_insn: Flags. (line 161) * jump, in insn: Flags. (line 157) * jump, in mem: Flags. (line 70) ! * Jumps: Jumps. (line 6) ! * JUMP_ALIGN: Alignment Output. (line 8) * jump_insn: Insns. (line 73) * jump_insn and /f: Flags. (line 107) * jump_insn and /s: Flags. (line 49) - * jump_insn and /s <1>: Flags. (line 148) * jump_insn and /u: Flags. (line 39) * jump_insn and /v: Flags. (line 44) * JUMP_LABEL: Insns. (line 80) - * JUMP_TABLES_IN_TEXT_SECTION: Sections. (line 150) * jump_table_data: Insns. (line 166) * jump_table_data and /s: Flags. (line 148) * jump_table_data and /v: Flags. (line 44) ! * LABEL_ALIGN: Alignment Output. (line 57) ! * LABEL_ALIGN_AFTER_BARRIER: Alignment Output. (line 26) ! * LABEL_ALTERNATE_NAME: Edges. (line 180) * LABEL_ALT_ENTRY_P: Insns. (line 146) * LABEL_DECL: Declarations. (line 6) * LABEL_KIND: Insns. (line 146) * LABEL_NUSES: Insns. (line 142) --- 49499,49558 ---- * interfacing to GCC output: Interface. (line 6) * interlock delays: Processor pipeline description. (line 6) ! * intermediate representation lowering: Parsing pass. (line 14) ! * INTMAX_TYPE: Type Layout. (line 193) ! * INTPTR_TYPE: Type Layout. (line 240) * introduction: Top. (line 6) * INVOKE__main: Macros for Initialization. ! (line 51) ! * ior: Arithmetic. (line 162) * ior and attributes: Expressions. (line 50) * ior, canonicalization of: Insn Canonicalizations. ! (line 52) ! * iorM3 instruction pattern: Standard Names. (line 305) ! * IRA_HARD_REGNO_ADD_COST_MULTIPLIER: Allocation Order. (line 46) ! * IS_ASM_LOGICAL_LINE_SEPARATOR: Data Output. (line 125) ! * is_gimple_addressable: Logical Operators. (line 115) ! * is_gimple_asm_val: Logical Operators. (line 119) ! * is_gimple_assign: Logical Operators. (line 151) ! * is_gimple_call: Logical Operators. (line 154) ! * is_gimple_call_addr: Logical Operators. (line 122) ! * is_gimple_constant: Logical Operators. (line 130) ! * is_gimple_debug: Logical Operators. (line 157) ! * is_gimple_ip_invariant: Logical Operators. (line 139) ! * is_gimple_ip_invariant_address: Logical Operators. (line 144) ! * is_gimple_mem_ref_addr: Logical Operators. (line 126) ! * is_gimple_min_invariant: Logical Operators. (line 133) ! * is_gimple_omp: Logical Operators. (line 168) ! * is_gimple_val: Logical Operators. (line 109) * iterators in .md files: Iterators. (line 6) * IV analysis on GIMPLE: Scalar evolutions. (line 6) * IV analysis on RTL: loop-iv. (line 6) * JMP_BUF_SIZE: Exception Region Output. ! (line 85) * jump: Flags. (line 286) ! * jump instruction pattern: Standard Names. (line 1338) * jump instruction patterns: Jump Patterns. (line 6) * jump instructions and set: Side Effects. (line 56) * jump, in call_insn: Flags. (line 161) * jump, in insn: Flags. (line 157) * jump, in mem: Flags. (line 70) ! * JUMP_ALIGN: Alignment Output. (line 9) * jump_insn: Insns. (line 73) * jump_insn and /f: Flags. (line 107) * jump_insn and /s: Flags. (line 49) * jump_insn and /u: Flags. (line 39) * jump_insn and /v: Flags. (line 44) * JUMP_LABEL: Insns. (line 80) * jump_table_data: Insns. (line 166) * jump_table_data and /s: Flags. (line 148) * jump_table_data and /v: Flags. (line 44) ! * JUMP_TABLES_IN_TEXT_SECTION: Sections. (line 151) ! * Jumps: Jumps. (line 6) ! * LABEL_ALIGN: Alignment Output. (line 58) ! * LABEL_ALIGN_AFTER_BARRIER: Alignment Output. (line 27) * LABEL_ALT_ENTRY_P: Insns. (line 146) + * LABEL_ALTERNATE_NAME: Edges. (line 181) * LABEL_DECL: Declarations. (line 6) * LABEL_KIND: Insns. (line 146) * LABEL_NUSES: Insns. (line 142) *************** Concept Index *** 49125,49213 **** * label_ref and /v: Flags. (line 65) * label_ref, RTL sharing: Sharing. (line 35) * LABEL_REF_NONLOCAL_P: Flags. (line 65) - * language-dependent trees: Language-dependent trees. - (line 6) - * language-independent intermediate representation: Parsing pass. - (line 13) * lang_hooks.gimplify_expr: Gimplification pass. (line 18) * lang_hooks.parse_file: Parsing pass. (line 6) * large return values: Aggregate Return. (line 6) ! * LAST_STACK_REG: Stack Registers. (line 30) * LAST_VIRTUAL_REGISTER: Regs and Memory. (line 51) ! * lceilMN2: Standard Names. (line 860) * LCSSA: LCSSA. (line 6) - * LDD_SUFFIX: Macros for Initialization. - (line 121) - * ldexpM3 instruction pattern: Standard Names. (line 653) * LD_FINI_SWITCH: Macros for Initialization. ! (line 28) * LD_INIT_SWITCH: Macros for Initialization. ! (line 24) * le: Comparisons. (line 76) ! * le and attributes: Expressions. (line 83) * leaf functions: Leaf Functions. (line 6) ! * leaf_function_p: Standard Names. (line 1416) ! * LEAF_REGISTERS: Leaf Functions. (line 23) ! * LEAF_REG_REMAP: Leaf Functions. (line 37) ! * left rotate: Arithmetic. (line 195) ! * left shift: Arithmetic. (line 173) ! * LEGITIMATE_PIC_OPERAND_P: PIC. (line 31) ! * LEGITIMIZE_RELOAD_ADDRESS: Addressing Modes. (line 150) ! * length: GTY Options. (line 47) * less than: Comparisons. (line 68) * less than or equal: Comparisons. (line 76) * leu: Comparisons. (line 76) ! * leu and attributes: Expressions. (line 83) ! * LE_EXPR: Unary and Binary Expressions. ! (line 6) ! * lfloorMN2: Standard Names. (line 855) * LIB2FUNCS_EXTRA: Target Fragment. (line 11) * LIBCALL_VALUE: Scalar Return. (line 56) * libgcc.a: Library Calls. (line 6) * LIBGCC2_CFLAGS: Target Fragment. (line 8) ! * LIBGCC2_GNU_PREFIX: Type Layout. (line 102) ! * LIBGCC2_UNWIND_ATTRIBUTE: Misc. (line 1090) ! * LIBGCC_SPEC: Driver. (line 115) * library subroutine names: Library Calls. (line 6) ! * LIBRARY_PATH_ENV: Misc. (line 510) ! * LIB_SPEC: Driver. (line 107) ! * LIMIT_RELOAD_CLASS: Register Classes. (line 296) ! * LINK_COMMAND_SPEC: Driver. (line 240) ! * LINK_EH_SPEC: Driver. (line 142) ! * LINK_GCC_C_SEQUENCE_SPEC: Driver. (line 232) ! * LINK_LIBGCC_SPECIAL_1: Driver. (line 227) ! * LINK_SPEC: Driver. (line 100) * list: Containers. (line 6) * Liveness representation: Liveness information. (line 6) ! * load address instruction: Simple Constraints. (line 162) ! * LOAD_EXTEND_OP: Misc. (line 59) ! * load_multiple instruction pattern: Standard Names. (line 136) ! * Local Register Allocator (LRA): RTL passes. (line 187) ! * LOCAL_ALIGNMENT: Storage Layout. (line 254) * LOCAL_CLASS_P: Classes. (line 73) ! * LOCAL_DECL_ALIGNMENT: Storage Layout. (line 291) ! * LOCAL_INCLUDE_DIR: Driver. (line 316) ! * LOCAL_LABEL_PREFIX: Instruction Output. (line 151) ! * LOCAL_REGNO: Register Basics. (line 100) ! * log10M2 instruction pattern: Standard Names. (line 757) ! * log1pM2 instruction pattern: Standard Names. (line 747) ! * log2M2 instruction pattern: Standard Names. (line 764) ! * logbM2 instruction pattern: Standard Names. (line 771) * Logical Operators: Logical Operators. (line 6) ! * logical-and, bitwise: Arithmetic. (line 158) ! * LOGICAL_OP_NON_SHORT_CIRCUIT: Costs. (line 273) ! * logM2 instruction pattern: Standard Names. (line 740) ! * LOG_LINKS: Insns. (line 314) * longjmp and automatic variables: Interface. (line 52) - * LONG_ACCUM_TYPE_SIZE: Type Layout. (line 92) - * LONG_DOUBLE_TYPE_SIZE: Type Layout. (line 57) - * LONG_FRACT_TYPE_SIZE: Type Layout. (line 72) - * LONG_LONG_ACCUM_TYPE_SIZE: Type Layout. (line 97) - * LONG_LONG_FRACT_TYPE_SIZE: Type Layout. (line 77) - * LONG_LONG_TYPE_SIZE: Type Layout. (line 32) - * LONG_TYPE_SIZE: Type Layout. (line 21) * Loop analysis: Loop representation. (line 6) * Loop manipulation: Loop manipulation. (line 6) --- 49561,49650 ---- * label_ref and /v: Flags. (line 65) * label_ref, RTL sharing: Sharing. (line 35) * LABEL_REF_NONLOCAL_P: Flags. (line 65) * lang_hooks.gimplify_expr: Gimplification pass. (line 18) * lang_hooks.parse_file: Parsing pass. (line 6) + * language-dependent trees: Language-dependent trees. + (line 6) + * language-independent intermediate representation: Parsing pass. + (line 14) * large return values: Aggregate Return. (line 6) ! * LAST_STACK_REG: Stack Registers. (line 31) * LAST_VIRTUAL_REGISTER: Regs and Memory. (line 51) ! * lceilMN2: Standard Names. (line 866) * LCSSA: LCSSA. (line 6) * LD_FINI_SWITCH: Macros for Initialization. ! (line 29) * LD_INIT_SWITCH: Macros for Initialization. ! (line 25) ! * LDD_SUFFIX: Macros for Initialization. ! (line 122) ! * ldexpM3 instruction pattern: Standard Names. (line 659) * le: Comparisons. (line 76) ! * le and attributes: Expressions. (line 85) ! * LE_EXPR: Unary and Binary Expressions. ! (line 6) * leaf functions: Leaf Functions. (line 6) ! * leaf_function_p: Standard Names. (line 1423) ! * LEAF_REG_REMAP: Leaf Functions. (line 39) ! * LEAF_REGISTERS: Leaf Functions. (line 25) ! * left rotate: Arithmetic. (line 194) ! * left shift: Arithmetic. (line 172) ! * LEGITIMATE_PIC_OPERAND_P: PIC. (line 32) ! * LEGITIMIZE_RELOAD_ADDRESS: Addressing Modes. (line 153) ! * length: GTY Options. (line 50) * less than: Comparisons. (line 68) * less than or equal: Comparisons. (line 76) * leu: Comparisons. (line 76) ! * leu and attributes: Expressions. (line 85) ! * lfloorMN2: Standard Names. (line 861) * LIB2FUNCS_EXTRA: Target Fragment. (line 11) + * LIB_SPEC: Driver. (line 108) * LIBCALL_VALUE: Scalar Return. (line 56) * libgcc.a: Library Calls. (line 6) * LIBGCC2_CFLAGS: Target Fragment. (line 8) ! * LIBGCC2_GNU_PREFIX: Type Layout. (line 103) ! * LIBGCC2_UNWIND_ATTRIBUTE: Misc. (line 1096) ! * LIBGCC_SPEC: Driver. (line 116) * library subroutine names: Library Calls. (line 6) ! * LIBRARY_PATH_ENV: Misc. (line 512) ! * LIMIT_RELOAD_CLASS: Register Classes. (line 300) ! * LINK_COMMAND_SPEC: Driver. (line 241) ! * LINK_EH_SPEC: Driver. (line 143) ! * LINK_GCC_C_SEQUENCE_SPEC: Driver. (line 233) ! * LINK_LIBGCC_SPECIAL_1: Driver. (line 228) ! * LINK_SPEC: Driver. (line 101) * list: Containers. (line 6) * Liveness representation: Liveness information. (line 6) ! * lo_sum: Arithmetic. (line 24) ! * load address instruction: Simple Constraints. (line 164) ! * LOAD_EXTEND_OP: Misc. (line 60) ! * load_multiple instruction pattern: Standard Names. (line 137) ! * Local Register Allocator (LRA): RTL passes. (line 188) ! * LOCAL_ALIGNMENT: Storage Layout. (line 258) * LOCAL_CLASS_P: Classes. (line 73) ! * LOCAL_DECL_ALIGNMENT: Storage Layout. (line 295) ! * LOCAL_INCLUDE_DIR: Driver. (line 317) ! * LOCAL_LABEL_PREFIX: Instruction Output. (line 153) ! * LOCAL_REGNO: Register Basics. (line 101) ! * log10M2 instruction pattern: Standard Names. (line 763) ! * log1pM2 instruction pattern: Standard Names. (line 753) ! * log2M2 instruction pattern: Standard Names. (line 770) ! * LOG_LINKS: Insns. (line 318) ! * logbM2 instruction pattern: Standard Names. (line 777) * Logical Operators: Logical Operators. (line 6) ! * logical-and, bitwise: Arithmetic. (line 157) ! * LOGICAL_OP_NON_SHORT_CIRCUIT: Costs. (line 274) ! * logM2 instruction pattern: Standard Names. (line 746) ! * LONG_ACCUM_TYPE_SIZE: Type Layout. (line 93) ! * LONG_DOUBLE_TYPE_SIZE: Type Layout. (line 58) ! * LONG_FRACT_TYPE_SIZE: Type Layout. (line 73) ! * LONG_LONG_ACCUM_TYPE_SIZE: Type Layout. (line 98) ! * LONG_LONG_FRACT_TYPE_SIZE: Type Layout. (line 78) ! * LONG_LONG_TYPE_SIZE: Type Layout. (line 33) ! * LONG_TYPE_SIZE: Type Layout. (line 22) * longjmp and automatic variables: Interface. (line 52) * Loop analysis: Loop representation. (line 6) * Loop manipulation: Loop manipulation. (line 6) *************** Concept Index *** 49215,49243 **** * Loop representation: Loop representation. (line 6) * Loop-closed SSA form: LCSSA. (line 6) ! * looping instruction patterns: Looping Patterns. (line 6) ! * LOOP_ALIGN: Alignment Output. (line 40) * LOOP_EXPR: Unary and Binary Expressions. (line 6) * lowering, language-dependent intermediate representation: Parsing pass. ! (line 13) ! * lo_sum: Arithmetic. (line 25) ! * lrintMN2: Standard Names. (line 845) ! * lroundMN2: Standard Names. (line 850) ! * lshiftrt: Arithmetic. (line 190) ! * lshiftrt and attributes: Expressions. (line 83) * LSHIFT_EXPR: Unary and Binary Expressions. (line 6) ! * lshrM3 instruction pattern: Standard Names. (line 591) * lt: Comparisons. (line 68) ! * lt and attributes: Expressions. (line 83) * LTGT_EXPR: Unary and Binary Expressions. (line 6) * lto: LTO. (line 6) * ltrans: LTO. (line 6) * ltu: Comparisons. (line 68) - * LT_EXPR: Unary and Binary Expressions. - (line 6) * m in constraint: Simple Constraints. (line 17) * machine attributes: Target Attributes. (line 6) * machine description macros: Target Macros. (line 6) --- 49652,49679 ---- * Loop representation: Loop representation. (line 6) * Loop-closed SSA form: LCSSA. (line 6) ! * LOOP_ALIGN: Alignment Output. (line 41) * LOOP_EXPR: Unary and Binary Expressions. (line 6) + * looping instruction patterns: Looping Patterns. (line 6) * lowering, language-dependent intermediate representation: Parsing pass. ! (line 14) ! * lrintMN2: Standard Names. (line 851) ! * lroundMN2: Standard Names. (line 856) * LSHIFT_EXPR: Unary and Binary Expressions. (line 6) ! * lshiftrt: Arithmetic. (line 189) ! * lshiftrt and attributes: Expressions. (line 85) ! * lshrM3 instruction pattern: Standard Names. (line 597) * lt: Comparisons. (line 68) ! * lt and attributes: Expressions. (line 85) ! * LT_EXPR: Unary and Binary Expressions. ! (line 6) * LTGT_EXPR: Unary and Binary Expressions. (line 6) * lto: LTO. (line 6) * ltrans: LTO. (line 6) * ltu: Comparisons. (line 68) * m in constraint: Simple Constraints. (line 17) * machine attributes: Target Attributes. (line 6) * machine description macros: Target Macros. (line 6) *************** Concept Index *** 49250,49406 **** (line 6) * machine_mode: Machine Modes. (line 6) * macros, target description: Target Macros. (line 6) ! * maddMN4 instruction pattern: Standard Names. (line 512) ! * makefile fragment: Fragments. (line 6) ! * makefile targets: Makefile. (line 6) ! * MAKE_DECL_ONE_ONLY: Label Output. (line 281) * make_safe_from: Expander Definitions. (line 151) ! * MALLOC_ABI_ALIGNMENT: Storage Layout. (line 173) * Manipulating GIMPLE statements: Manipulating GIMPLE statements. (line 6) * marking roots: GGC Roots. (line 6) - * maskloadMN instruction pattern: Standard Names. (line 244) - * maskstoreMN instruction pattern: Standard Names. (line 251) * MASK_RETURN_ADDR: Exception Region Output. ! (line 35) * Match and Simplify: Match and Simplify. (line 6) - * matching constraint: Simple Constraints. (line 140) - * matching operands: Output Template. (line 49) - * match_dup: RTL Template. (line 73) * match_dup <1>: define_peephole2. (line 28) * match_dup and attributes: Insn Lengths. (line 16) * match_operand: RTL Template. (line 16) * match_operand and attributes: Expressions. (line 55) * match_operator: RTL Template. (line 95) - * match_op_dup: RTL Template. (line 163) - * match_parallel: RTL Template. (line 172) * match_par_dup: RTL Template. (line 219) ! * match_scratch: RTL Template. (line 58) * match_scratch <1>: define_peephole2. (line 28) * match_test and attributes: Expressions. (line 64) * math library: Soft float library routines. (line 6) * math, in RTL: Arithmetic. (line 6) * matherr: Library Calls. (line 59) ! * MATH_LIBRARY: Misc. (line 503) ! * maxM3 instruction pattern: Standard Names. (line 363) ! * MAX_BITSIZE_MODE_ANY_INT: Machine Modes. (line 358) ! * MAX_BITSIZE_MODE_ANY_MODE: Machine Modes. (line 364) ! * MAX_BITS_PER_WORD: Storage Layout. (line 54) ! * MAX_CONDITIONAL_EXECUTE: Misc. (line 525) ! * MAX_FIXED_MODE_SIZE: Storage Layout. (line 436) ! * MAX_MOVE_MAX: Misc. (line 105) ! * MAX_OFILE_ALIGNMENT: Storage Layout. (line 208) ! * MAX_REGS_PER_ADDRESS: Addressing Modes. (line 42) ! * MAX_STACK_ALIGNMENT: Storage Layout. (line 202) ! * maybe_undef: GTY Options. (line 139) ! * may_trap_p, tree_could_trap_p: Edges. (line 114) * mcount: Profiling. (line 12) ! * MD_EXEC_PREFIX: Driver. (line 271) ! * MD_FALLBACK_FRAME_STATE_FOR: Exception Handling. (line 93) ! * MD_HANDLE_UNWABI: Exception Handling. (line 112) ! * MD_STARTFILE_PREFIX: Driver. (line 299) ! * MD_STARTFILE_PREFIX_1: Driver. (line 304) ! * mem: Regs and Memory. (line 370) * mem and /c: Flags. (line 81) * mem and /f: Flags. (line 85) * mem and /j: Flags. (line 70) * mem and /u: Flags. (line 134) * mem and /v: Flags. (line 76) * mem, RTL sharing: Sharing. (line 40) ! * memory model: Memory model. (line 6) ! * memory reference, nonoffsettable: Simple Constraints. (line 254) ! * memory references in constraints: Simple Constraints. (line 17) ! * memory_barrier instruction pattern: Standard Names. (line 1802) ! * MEMORY_MOVE_COST: Costs. (line 53) ! * memory_operand: Machine-Independent Predicates. ! (line 57) ! * MEM_ADDR_SPACE: Special Accessors. (line 48) * MEM_ALIAS_SET: Special Accessors. (line 9) ! * MEM_ALIGN: Special Accessors. (line 45) ! * MEM_EXPR: Special Accessors. (line 19) * MEM_KEEP_ALIAS_SET_P: Flags. (line 70) * MEM_NOTRAP_P: Flags. (line 81) ! * MEM_OFFSET: Special Accessors. (line 31) ! * MEM_OFFSET_KNOWN_P: Special Accessors. (line 27) * MEM_POINTER: Flags. (line 85) * MEM_READONLY_P: Flags. (line 134) * MEM_REF: Storage References. (line 6) ! * mem_signal_fenceMODE instruction pattern: Standard Names. (line 2061) ! * MEM_SIZE: Special Accessors. (line 39) ! * MEM_SIZE_KNOWN_P: Special Accessors. (line 35) ! * mem_thread_fenceMODE instruction pattern: Standard Names. (line 2053) * MEM_VOLATILE_P: Flags. (line 76) * METHOD_TYPE: Types. (line 6) ! * MINIMUM_ALIGNMENT: Storage Layout. (line 304) ! * MINIMUM_ATOMIC_ALIGNMENT: Storage Layout. (line 181) ! * minM3 instruction pattern: Standard Names. (line 363) ! * minus: Arithmetic. (line 38) ! * minus and attributes: Expressions. (line 83) * minus, canonicalization of: Insn Canonicalizations. (line 27) * MINUS_EXPR: Unary and Binary Expressions. (line 6) - * MIN_UNITS_PER_WORD: Storage Layout. (line 64) * MIPS coprocessor-definition macros: MIPS Coprocessors. (line 6) * miscellaneous register hooks: Miscellaneous Register Hooks. (line 6) * mnemonic attribute: Mnemonic Attribute. (line 6) ! * mod: Arithmetic. (line 136) ! * mod and attributes: Expressions. (line 83) ! * mode classes: Machine Modes. (line 225) * mode iterators in .md files: Mode Iterators. (line 6) * mode switching: Mode Switching. (line 6) ! * MODES_TIEABLE_P: Values in Registers. ! (line 127) ! * MODE_ACCUM: Machine Modes. (line 255) ! * MODE_BASE_REG_CLASS: Register Classes. (line 116) ! * MODE_BASE_REG_REG_CLASS: Register Classes. (line 122) ! * MODE_CC: Machine Modes. (line 274) * MODE_CC <1>: MODE_CC Condition Codes. (line 6) ! * MODE_CODE_BASE_REG_CLASS: Register Classes. (line 129) ! * MODE_COMPLEX_FLOAT: Machine Modes. (line 266) ! * MODE_COMPLEX_INT: Machine Modes. (line 263) ! * MODE_DECIMAL_FLOAT: Machine Modes. (line 243) ! * MODE_FLOAT: Machine Modes. (line 239) ! * MODE_FRACT: Machine Modes. (line 247) ! * MODE_FUNCTION: Machine Modes. (line 270) ! * MODE_INT: Machine Modes. (line 231) ! * MODE_PARTIAL_INT: Machine Modes. (line 235) ! * MODE_POINTER_BOUNDS: Machine Modes. (line 279) ! * MODE_RANDOM: Machine Modes. (line 284) ! * MODE_UACCUM: Machine Modes. (line 259) ! * MODE_UFRACT: Machine Modes. (line 251) * modifiers in constraints: Modifiers. (line 6) * MODIFY_EXPR: Unary and Binary Expressions. (line 6) ! * MODIFY_JNI_METHOD_CALL: Misc. (line 874) ! * modM3 instruction pattern: Standard Names. (line 301) ! * modulo scheduling: RTL passes. (line 123) ! * MOVE_MAX: Misc. (line 100) ! * MOVE_MAX_PIECES: Costs. (line 199) ! * MOVE_RATIO: Costs. (line 148) * movM instruction pattern: Standard Names. (line 11) ! * movmemM instruction pattern: Standard Names. (line 959) ! * movmisalignM instruction pattern: Standard Names. (line 125) ! * movMODEcc instruction pattern: Standard Names. (line 1253) ! * movstr instruction pattern: Standard Names. (line 994) ! * movstrictM instruction pattern: Standard Names. (line 119) ! * msubMN4 instruction pattern: Standard Names. (line 535) ! * mulhisi3 instruction pattern: Standard Names. (line 488) ! * mulM3 instruction pattern: Standard Names. (line 301) ! * mulqihi3 instruction pattern: Standard Names. (line 492) ! * mulsidi3 instruction pattern: Standard Names. (line 492) ! * mult: Arithmetic. (line 93) ! * mult and attributes: Expressions. (line 83) * mult, canonicalization of: Insn Canonicalizations. (line 27) ! * mult, canonicalization of <1>: Insn Canonicalizations. ! (line 91) * MULTIARCH_DIRNAME: Target Fragment. (line 170) ! * MULTILIB_DEFAULTS: Driver. (line 256) * MULTILIB_DIRNAMES: Target Fragment. (line 44) * MULTILIB_EXCEPTIONS: Target Fragment. (line 70) * MULTILIB_EXTRA_OPTS: Target Fragment. (line 132) --- 49686,49844 ---- (line 6) * machine_mode: Machine Modes. (line 6) * macros, target description: Target Macros. (line 6) ! * maddMN4 instruction pattern: Standard Names. (line 518) ! * MAKE_DECL_ONE_ONLY: Label Output. (line 285) * make_safe_from: Expander Definitions. (line 151) ! * makefile fragment: Fragments. (line 6) ! * makefile targets: Makefile. (line 6) ! * MALLOC_ABI_ALIGNMENT: Storage Layout. (line 175) * Manipulating GIMPLE statements: Manipulating GIMPLE statements. (line 6) * marking roots: GGC Roots. (line 6) * MASK_RETURN_ADDR: Exception Region Output. ! (line 36) ! * maskloadMN instruction pattern: Standard Names. (line 246) ! * maskstoreMN instruction pattern: Standard Names. (line 253) * Match and Simplify: Match and Simplify. (line 6) * match_dup <1>: define_peephole2. (line 28) + * match_dup: RTL Template. (line 73) * match_dup and attributes: Insn Lengths. (line 16) + * match_op_dup: RTL Template. (line 163) * match_operand: RTL Template. (line 16) * match_operand and attributes: Expressions. (line 55) * match_operator: RTL Template. (line 95) * match_par_dup: RTL Template. (line 219) ! * match_parallel: RTL Template. (line 172) * match_scratch <1>: define_peephole2. (line 28) + * match_scratch: RTL Template. (line 58) * match_test and attributes: Expressions. (line 64) + * matching constraint: Simple Constraints. (line 142) + * matching operands: Output Template. (line 49) * math library: Soft float library routines. (line 6) * math, in RTL: Arithmetic. (line 6) + * MATH_LIBRARY: Misc. (line 505) * matherr: Library Calls. (line 59) ! * MAX_BITS_PER_WORD: Storage Layout. (line 55) ! * MAX_BITSIZE_MODE_ANY_INT: Machine Modes. (line 359) ! * MAX_BITSIZE_MODE_ANY_MODE: Machine Modes. (line 365) ! * MAX_CONDITIONAL_EXECUTE: Misc. (line 527) ! * MAX_FIXED_MODE_SIZE: Storage Layout. (line 441) ! * MAX_MOVE_MAX: Misc. (line 106) ! * MAX_OFILE_ALIGNMENT: Storage Layout. (line 212) ! * MAX_REGS_PER_ADDRESS: Addressing Modes. (line 43) ! * MAX_STACK_ALIGNMENT: Storage Layout. (line 205) ! * maxM3 instruction pattern: Standard Names. (line 367) ! * may_trap_p, tree_could_trap_p: Edges. (line 115) ! * maybe_undef: GTY Options. (line 137) * mcount: Profiling. (line 12) ! * MD_EXEC_PREFIX: Driver. (line 272) ! * MD_FALLBACK_FRAME_STATE_FOR: Exception Handling. (line 94) ! * MD_HANDLE_UNWABI: Exception Handling. (line 114) ! * MD_STARTFILE_PREFIX: Driver. (line 300) ! * MD_STARTFILE_PREFIX_1: Driver. (line 305) ! * mem: Regs and Memory. (line 374) * mem and /c: Flags. (line 81) * mem and /f: Flags. (line 85) * mem and /j: Flags. (line 70) * mem and /u: Flags. (line 134) * mem and /v: Flags. (line 76) * mem, RTL sharing: Sharing. (line 40) ! * MEM_ADDR_SPACE: Special Accessors. (line 49) * MEM_ALIAS_SET: Special Accessors. (line 9) ! * MEM_ALIGN: Special Accessors. (line 46) ! * MEM_EXPR: Special Accessors. (line 20) * MEM_KEEP_ALIAS_SET_P: Flags. (line 70) * MEM_NOTRAP_P: Flags. (line 81) ! * MEM_OFFSET: Special Accessors. (line 32) ! * MEM_OFFSET_KNOWN_P: Special Accessors. (line 28) * MEM_POINTER: Flags. (line 85) * MEM_READONLY_P: Flags. (line 134) * MEM_REF: Storage References. (line 6) ! * mem_signal_fenceMODE instruction pattern: Standard Names. (line 2072) ! * MEM_SIZE: Special Accessors. (line 40) ! * MEM_SIZE_KNOWN_P: Special Accessors. (line 36) ! * mem_thread_fenceMODE instruction pattern: Standard Names. (line 2064) * MEM_VOLATILE_P: Flags. (line 76) + * memory model: Memory model. (line 6) + * memory reference, nonoffsettable: Simple Constraints. (line 256) + * memory references in constraints: Simple Constraints. (line 17) + * memory_barrier instruction pattern: Standard Names. (line 1813) + * MEMORY_MOVE_COST: Costs. (line 54) + * memory_operand: Machine-Independent Predicates. + (line 58) * METHOD_TYPE: Types. (line 6) ! * MIN_UNITS_PER_WORD: Storage Layout. (line 65) ! * MINIMUM_ALIGNMENT: Storage Layout. (line 308) ! * MINIMUM_ATOMIC_ALIGNMENT: Storage Layout. (line 183) ! * minM3 instruction pattern: Standard Names. (line 367) ! * minus: Arithmetic. (line 36) ! * minus and attributes: Expressions. (line 85) * minus, canonicalization of: Insn Canonicalizations. (line 27) * MINUS_EXPR: Unary and Binary Expressions. (line 6) * MIPS coprocessor-definition macros: MIPS Coprocessors. (line 6) * miscellaneous register hooks: Miscellaneous Register Hooks. (line 6) * mnemonic attribute: Mnemonic Attribute. (line 6) ! * mod: Arithmetic. (line 135) ! * mod and attributes: Expressions. (line 85) ! * mode classes: Machine Modes. (line 226) * mode iterators in .md files: Mode Iterators. (line 6) * mode switching: Mode Switching. (line 6) ! * MODE_ACCUM: Machine Modes. (line 256) ! * MODE_BASE_REG_CLASS: Register Classes. (line 119) ! * MODE_BASE_REG_REG_CLASS: Register Classes. (line 125) * MODE_CC <1>: MODE_CC Condition Codes. (line 6) ! * MODE_CC: Machine Modes. (line 275) ! * MODE_CODE_BASE_REG_CLASS: Register Classes. (line 133) ! * MODE_COMPLEX_FLOAT: Machine Modes. (line 267) ! * MODE_COMPLEX_INT: Machine Modes. (line 264) ! * MODE_DECIMAL_FLOAT: Machine Modes. (line 244) ! * MODE_FLOAT: Machine Modes. (line 240) ! * MODE_FRACT: Machine Modes. (line 248) ! * MODE_FUNCTION: Machine Modes. (line 271) ! * MODE_INT: Machine Modes. (line 232) ! * MODE_PARTIAL_INT: Machine Modes. (line 236) ! * MODE_POINTER_BOUNDS: Machine Modes. (line 280) ! * MODE_RANDOM: Machine Modes. (line 285) ! * MODE_UACCUM: Machine Modes. (line 260) ! * MODE_UFRACT: Machine Modes. (line 252) ! * MODES_TIEABLE_P: Values in Registers. ! (line 129) * modifiers in constraints: Modifiers. (line 6) * MODIFY_EXPR: Unary and Binary Expressions. (line 6) ! * MODIFY_JNI_METHOD_CALL: Misc. (line 878) ! * modM3 instruction pattern: Standard Names. (line 305) ! * modulo scheduling: RTL passes. (line 124) ! * MOVE_MAX: Misc. (line 101) ! * MOVE_MAX_PIECES: Costs. (line 200) ! * MOVE_RATIO: Costs. (line 149) * movM instruction pattern: Standard Names. (line 11) ! * movmemM instruction pattern: Standard Names. (line 965) ! * movmisalignM instruction pattern: Standard Names. (line 126) ! * movMODEcc instruction pattern: Standard Names. (line 1259) ! * movstr instruction pattern: Standard Names. (line 1000) ! * movstrictM instruction pattern: Standard Names. (line 120) ! * msubMN4 instruction pattern: Standard Names. (line 541) ! * mulhisi3 instruction pattern: Standard Names. (line 494) ! * mulM3 instruction pattern: Standard Names. (line 305) ! * mulqihi3 instruction pattern: Standard Names. (line 498) ! * mulsidi3 instruction pattern: Standard Names. (line 498) ! * mult: Arithmetic. (line 92) ! * mult and attributes: Expressions. (line 85) * mult, canonicalization of: Insn Canonicalizations. (line 27) ! * MULT_EXPR: Unary and Binary Expressions. ! (line 6) ! * MULT_HIGHPART_EXPR: Unary and Binary Expressions. ! (line 6) * MULTIARCH_DIRNAME: Target Fragment. (line 170) ! * MULTILIB_DEFAULTS: Driver. (line 257) * MULTILIB_DIRNAMES: Target Fragment. (line 44) * MULTILIB_EXCEPTIONS: Target Fragment. (line 70) * MULTILIB_EXTRA_OPTS: Target Fragment. (line 132) *************** Concept Index *** 49410,49515 **** * MULTILIB_REQUIRED: Target Fragment. (line 82) * MULTILIB_REUSE: Target Fragment. (line 103) * multiple alternative constraints: Multi-Alternative. (line 6) ! * MULTIPLE_SYMBOL_SPACES: Misc. (line 482) ! * multiplication: Arithmetic. (line 93) ! * multiplication with signed saturation: Arithmetic. (line 93) ! * multiplication with unsigned saturation: Arithmetic. (line 93) ! * MULT_EXPR: Unary and Binary Expressions. ! (line 6) ! * MULT_HIGHPART_EXPR: Unary and Binary Expressions. ! (line 6) ! * mulvM4 instruction pattern: Standard Names. (line 317) ! * n in constraint: Simple Constraints. (line 73) * name: Identifiers. (line 6) * named address spaces: Named Address Spaces. (line 6) * named patterns and conditions: Patterns. (line 49) * names, pattern: Standard Names. (line 6) * namespace, scope: Namespaces. (line 6) - * NAMESPACE_DECL: Declarations. (line 6) * NAMESPACE_DECL <1>: Namespaces. (line 6) ! * NATIVE_SYSTEM_HEADER_COMPONENT: Driver. (line 326) * ne: Comparisons. (line 56) ! * ne and attributes: Expressions. (line 83) ! * nearbyintM2 instruction pattern: Standard Names. (line 829) ! * neg: Arithmetic. (line 82) ! * neg and attributes: Expressions. (line 83) * neg, canonicalization of: Insn Canonicalizations. (line 27) * NEGATE_EXPR: Unary and Binary Expressions. (line 6) ! * negation: Arithmetic. (line 82) ! * negation with signed saturation: Arithmetic. (line 82) ! * negation with unsigned saturation: Arithmetic. (line 82) ! * negM2 instruction pattern: Standard Names. (line 603) ! * negMODEcc instruction pattern: Standard Names. (line 1273) ! * negvM3 instruction pattern: Standard Names. (line 606) * nested functions, trampolines for: Trampolines. (line 6) ! * nested_ptr: GTY Options. (line 147) * next_bb, prev_bb, FOR_EACH_BB, FOR_ALL_BB: Basic Blocks. (line 25) * NEXT_INSN: Insns. (line 30) ! * NEXT_OBJC_RUNTIME: Library Calls. (line 82) ! * NE_EXPR: Unary and Binary Expressions. ! (line 6) * nil: RTL Objects. (line 73) * NM_FLAGS: Macros for Initialization. ! (line 110) * nondeterministic finite state automaton: Processor pipeline description. ! (line 304) * nonimmediate_operand: Machine-Independent Predicates. ! (line 100) ! * nonlocal goto handler: Edges. (line 171) ! * nonlocal_goto instruction pattern: Standard Names. (line 1636) * nonlocal_goto_receiver instruction pattern: Standard Names. ! (line 1653) * nonmemory_operand: Machine-Independent Predicates. ! (line 96) ! * nonoffsettable memory reference: Simple Constraints. (line 254) ! * NON_LVALUE_EXPR: Unary and Binary Expressions. ! (line 6) ! * nop instruction pattern: Standard Names. (line 1449) * NOP_EXPR: Unary and Binary Expressions. (line 6) * normal predicates: Predicates. (line 31) ! * not: Arithmetic. (line 154) * not and attributes: Expressions. (line 50) * not equal: Comparisons. (line 56) * not, canonicalization of: Insn Canonicalizations. (line 27) ! * note: Insns. (line 183) * note and /i: Flags. (line 59) * note and /v: Flags. (line 44) * NOTE_INSN_BASIC_BLOCK: Basic Blocks. (line 50) ! * NOTE_INSN_BASIC_BLOCK <1>: Basic Blocks. (line 52) ! * NOTE_INSN_BLOCK_BEG: Insns. (line 208) ! * NOTE_INSN_BLOCK_END: Insns. (line 208) ! * NOTE_INSN_DELETED: Insns. (line 198) ! * NOTE_INSN_DELETED_LABEL: Insns. (line 203) ! * NOTE_INSN_EH_REGION_BEG: Insns. (line 214) ! * NOTE_INSN_EH_REGION_END: Insns. (line 214) ! * NOTE_INSN_FUNCTION_BEG: Insns. (line 221) ! * NOTE_INSN_VAR_LOCATION: Insns. (line 225) ! * NOTE_LINE_NUMBER: Insns. (line 183) ! * NOTE_SOURCE_FILE: Insns. (line 183) ! * NOTE_VAR_LOCATION: Insns. (line 225) * NOTICE_UPDATE_CC: CC0 Condition Codes. ! (line 30) ! * notMODEcc instruction pattern: Standard Names. (line 1280) ! * NO_DBX_BNSYM_ENSYM: DBX Hooks. (line 25) ! * NO_DBX_FUNCTION_END: DBX Hooks. (line 19) ! * NO_DBX_GCC_MARKER: File Names and DBX. (line 27) ! * NO_DBX_MAIN_SOURCE_DIRECTORY: File Names and DBX. (line 22) ! * NO_DOLLAR_IN_LABEL: Label Output. (line 64) ! * NO_DOT_IN_LABEL: Label Output. (line 70) ! * NO_FUNCTION_CSE: Costs. (line 268) ! * NO_IMPLICIT_EXTERN_C: Misc. (line 381) ! * NO_PROFILE_COUNTERS: Profiling. (line 27) ! * NO_REGS: Register Classes. (line 17) * Number of iterations analysis: Number of iterations. (line 6) - * NUM_MACHINE_MODES: Machine Modes. (line 297) - * NUM_MODES_FOR_MODE_SWITCHING: Mode Switching. (line 30) - * N_REG_CLASSES: Register Classes. (line 81) * o in constraint: Simple Constraints. (line 23) * OACC_CACHE: OpenACC. (line 6) * OACC_DATA: OpenACC. (line 6) --- 49848,49948 ---- * MULTILIB_REQUIRED: Target Fragment. (line 82) * MULTILIB_REUSE: Target Fragment. (line 103) * multiple alternative constraints: Multi-Alternative. (line 6) ! * MULTIPLE_SYMBOL_SPACES: Misc. (line 484) ! * multiplication: Arithmetic. (line 92) ! * multiplication with signed saturation: Arithmetic. (line 92) ! * multiplication with unsigned saturation: Arithmetic. (line 92) ! * mulvM4 instruction pattern: Standard Names. (line 321) ! * n in constraint: Simple Constraints. (line 75) ! * N_REG_CLASSES: Register Classes. (line 83) * name: Identifiers. (line 6) * named address spaces: Named Address Spaces. (line 6) * named patterns and conditions: Patterns. (line 49) * names, pattern: Standard Names. (line 6) * namespace, scope: Namespaces. (line 6) * NAMESPACE_DECL <1>: Namespaces. (line 6) ! * NAMESPACE_DECL: Declarations. (line 6) ! * NATIVE_SYSTEM_HEADER_COMPONENT: Driver. (line 327) * ne: Comparisons. (line 56) ! * ne and attributes: Expressions. (line 85) ! * NE_EXPR: Unary and Binary Expressions. ! (line 6) ! * nearbyintM2 instruction pattern: Standard Names. (line 835) ! * neg: Arithmetic. (line 81) ! * neg and attributes: Expressions. (line 85) * neg, canonicalization of: Insn Canonicalizations. (line 27) * NEGATE_EXPR: Unary and Binary Expressions. (line 6) ! * negation: Arithmetic. (line 81) ! * negation with signed saturation: Arithmetic. (line 81) ! * negation with unsigned saturation: Arithmetic. (line 81) ! * negM2 instruction pattern: Standard Names. (line 609) ! * negMODEcc instruction pattern: Standard Names. (line 1279) ! * negvM3 instruction pattern: Standard Names. (line 612) * nested functions, trampolines for: Trampolines. (line 6) ! * nested_ptr: GTY Options. (line 144) * next_bb, prev_bb, FOR_EACH_BB, FOR_ALL_BB: Basic Blocks. (line 25) * NEXT_INSN: Insns. (line 30) ! * NEXT_OBJC_RUNTIME: Library Calls. (line 83) * nil: RTL Objects. (line 73) * NM_FLAGS: Macros for Initialization. ! (line 111) ! * NO_DBX_BNSYM_ENSYM: DBX Hooks. (line 26) ! * NO_DBX_FUNCTION_END: DBX Hooks. (line 20) ! * NO_DBX_GCC_MARKER: File Names and DBX. (line 28) ! * NO_DBX_MAIN_SOURCE_DIRECTORY: File Names and DBX. (line 23) ! * NO_DOLLAR_IN_LABEL: Label Output. (line 67) ! * NO_DOT_IN_LABEL: Label Output. (line 73) ! * NO_FUNCTION_CSE: Costs. (line 269) ! * NO_IMPLICIT_EXTERN_C: Misc. (line 382) ! * NO_PROFILE_COUNTERS: Profiling. (line 28) ! * NO_REGS: Register Classes. (line 17) ! * NON_LVALUE_EXPR: Unary and Binary Expressions. ! (line 6) * nondeterministic finite state automaton: Processor pipeline description. ! (line 305) * nonimmediate_operand: Machine-Independent Predicates. ! (line 101) ! * nonlocal goto handler: Edges. (line 172) ! * nonlocal_goto instruction pattern: Standard Names. (line 1645) * nonlocal_goto_receiver instruction pattern: Standard Names. ! (line 1662) * nonmemory_operand: Machine-Independent Predicates. ! (line 97) ! * nonoffsettable memory reference: Simple Constraints. (line 256) ! * nop instruction pattern: Standard Names. (line 1456) * NOP_EXPR: Unary and Binary Expressions. (line 6) * normal predicates: Predicates. (line 31) ! * not: Arithmetic. (line 153) * not and attributes: Expressions. (line 50) * not equal: Comparisons. (line 56) * not, canonicalization of: Insn Canonicalizations. (line 27) ! * note: Insns. (line 185) * note and /i: Flags. (line 59) * note and /v: Flags. (line 44) * NOTE_INSN_BASIC_BLOCK: Basic Blocks. (line 50) ! * NOTE_INSN_BLOCK_BEG: Insns. (line 210) ! * NOTE_INSN_BLOCK_END: Insns. (line 210) ! * NOTE_INSN_DELETED: Insns. (line 200) ! * NOTE_INSN_DELETED_LABEL: Insns. (line 205) ! * NOTE_INSN_EH_REGION_BEG: Insns. (line 216) ! * NOTE_INSN_EH_REGION_END: Insns. (line 216) ! * NOTE_INSN_FUNCTION_BEG: Insns. (line 223) ! * NOTE_INSN_VAR_LOCATION: Insns. (line 227) ! * NOTE_LINE_NUMBER: Insns. (line 185) ! * NOTE_SOURCE_FILE: Insns. (line 185) ! * NOTE_VAR_LOCATION: Insns. (line 227) * NOTICE_UPDATE_CC: CC0 Condition Codes. ! (line 31) ! * notMODEcc instruction pattern: Standard Names. (line 1286) ! * NUM_MACHINE_MODES: Machine Modes. (line 298) ! * NUM_MODES_FOR_MODE_SWITCHING: Mode Switching. (line 31) * Number of iterations analysis: Number of iterations. (line 6) * o in constraint: Simple Constraints. (line 23) * OACC_CACHE: OpenACC. (line 6) * OACC_DATA: OpenACC. (line 6) *************** Concept Index *** 49521,49532 **** * OACC_LOOP: OpenACC. (line 6) * OACC_PARALLEL: OpenACC. (line 6) * OACC_UPDATE: OpenACC. (line 6) ! * OBJC_GEN_METHOD_LABEL: Label Output. (line 482) ! * OBJC_JBLEN: Misc. (line 1085) * OBJECT_FORMAT_COFF: Macros for Initialization. ! (line 96) ! * offsettable address: Simple Constraints. (line 23) * OFFSET_TYPE: Types. (line 6) * OImode: Machine Modes. (line 51) * OMP_ATOMIC: OpenMP. (line 6) * OMP_CLAUSE: OpenMP. (line 6) --- 49954,49965 ---- * OACC_LOOP: OpenACC. (line 6) * OACC_PARALLEL: OpenACC. (line 6) * OACC_UPDATE: OpenACC. (line 6) ! * OBJC_GEN_METHOD_LABEL: Label Output. (line 487) ! * OBJC_JBLEN: Misc. (line 1091) * OBJECT_FORMAT_COFF: Macros for Initialization. ! (line 97) * OFFSET_TYPE: Types. (line 6) + * offsettable address: Simple Constraints. (line 23) * OImode: Machine Modes. (line 51) * OMP_ATOMIC: OpenMP. (line 6) * OMP_CLAUSE: OpenMP. (line 6) *************** Concept Index *** 49540,49555 **** * OMP_SECTION: OpenMP. (line 6) * OMP_SECTIONS: OpenMP. (line 6) * OMP_SINGLE: OpenMP. (line 6) ! * one_cmplM2 instruction pattern: Standard Names. (line 956) * operand access: Accessors. (line 6) ! * Operand Access Routines: SSA Operands. (line 116) * operand constraints: Constraints. (line 6) ! * Operand Iterators: SSA Operands. (line 116) * operand predicates: Predicates. (line 6) * operand substitution: Output Template. (line 6) - * Operands: Operands. (line 6) - * operands: SSA Operands. (line 6) * operands <1>: Patterns. (line 55) * operator predicates: Predicates. (line 6) * optc-gen.awk: Options. (line 6) * OPTGROUP_ALL: Optimization groups. --- 49973,49988 ---- * OMP_SECTION: OpenMP. (line 6) * OMP_SECTIONS: OpenMP. (line 6) * OMP_SINGLE: OpenMP. (line 6) ! * one_cmplM2 instruction pattern: Standard Names. (line 962) * operand access: Accessors. (line 6) ! * Operand Access Routines: SSA Operands. (line 119) * operand constraints: Constraints. (line 6) ! * Operand Iterators: SSA Operands. (line 119) * operand predicates: Predicates. (line 6) * operand substitution: Output Template. (line 6) * operands <1>: Patterns. (line 55) + * operands: SSA Operands. (line 6) + * Operands: Operands. (line 6) * operator predicates: Predicates. (line 6) * optc-gen.awk: Options. (line 6) * OPTGROUP_ALL: Optimization groups. *************** Concept Index *** 49570,49630 **** * optimization info file names: Dump files and streams. (line 6) * Optimization infrastructure for GIMPLE: Tree SSA. (line 6) ! * OPTIMIZE_MODE_SWITCHING: Mode Switching. (line 8) * option specification files: Options. (line 6) * optional hardware or system features: Run-time Target. (line 59) ! * options, directory search: Including Patterns. (line 47) ! * OPTION_DEFAULT_SPECS: Driver. (line 25) * order of register allocation: Allocation Order. (line 6) * ordered_comparison_operator: Machine-Independent Predicates. ! (line 115) * ORDERED_EXPR: Unary and Binary Expressions. (line 6) * Ordering of Patterns: Pattern Ordering. (line 6) ! * ORIGINAL_REGNO: Special Accessors. (line 53) ! * other register constraints: Simple Constraints. (line 171) * outgoing_args_size: Stack Arguments. (line 48) ! * OUTGOING_REGNO: Register Basics. (line 93) ! * OUTGOING_REG_PARM_STACK_SPACE: Stack Arguments. (line 79) * output of assembler code: File Framework. (line 6) * output statements: Output Statement. (line 6) * output templates: Output Template. (line 6) ! * output_asm_insn: Output Statement. (line 52) ! * OUTPUT_QUOTED_STRING: File Framework. (line 106) ! * OVERLAPPING_REGISTER_NAMES: Instruction Output. (line 20) * OVERLOAD: Functions for C++. (line 6) ! * OVERRIDE_ABI_FORMAT: Register Arguments. (line 153) * OVL_CURRENT: Functions for C++. (line 6) * OVL_NEXT: Functions for C++. (line 6) ! * p in constraint: Simple Constraints. (line 162) ! * PAD_VARARGS_DOWN: Register Arguments. (line 234) * parallel: Side Effects. (line 210) * parameters, c++ abi: C++ ABI. (line 6) * parameters, miscellaneous: Misc. (line 6) * parameters, precompiled headers: PCH Target. (line 6) * parity: Arithmetic. (line 242) ! * parityM2 instruction pattern: Standard Names. (line 943) ! * PARM_BOUNDARY: Storage Layout. (line 133) * PARM_DECL: Declarations. (line 6) * PARSE_LDD_OUTPUT: Macros for Initialization. ! (line 125) * pass dumps: Passes. (line 6) * passes and files of the compiler: Passes. (line 6) * passing arguments: Interface. (line 36) - * pass_duplicate_computed_gotos: Edges. (line 161) * PATH_SEPARATOR: Filesystem. (line 31) ! * PATTERN: Insns. (line 284) * pattern conditions: Patterns. (line 43) * pattern names: Standard Names. (line 6) * Pattern Ordering: Pattern Ordering. (line 6) * patterns: Patterns. (line 6) ! * pc: Regs and Memory. (line 357) * pc and attributes: Insn Lengths. (line 20) * pc, RTL sharing: Sharing. (line 25) ! * PCC_BITFIELD_TYPE_MATTERS: Storage Layout. (line 330) ! * PCC_STATIC_STRUCT_RETURN: Aggregate Return. (line 64) ! * PC_REGNUM: Register Basics. (line 107) ! * pc_rtx: Regs and Memory. (line 362) * PDImode: Machine Modes. (line 40) * peephole optimization, RTL representation: Side Effects. (line 244) * peephole optimizer definitions: Peephole Definitions. --- 50003,50063 ---- * optimization info file names: Dump files and streams. (line 6) * Optimization infrastructure for GIMPLE: Tree SSA. (line 6) ! * OPTIMIZE_MODE_SWITCHING: Mode Switching. (line 9) * option specification files: Options. (line 6) + * OPTION_DEFAULT_SPECS: Driver. (line 26) * optional hardware or system features: Run-time Target. (line 59) ! * options, directory search: Including Patterns. (line 44) * order of register allocation: Allocation Order. (line 6) * ordered_comparison_operator: Machine-Independent Predicates. ! (line 116) * ORDERED_EXPR: Unary and Binary Expressions. (line 6) * Ordering of Patterns: Pattern Ordering. (line 6) ! * ORIGINAL_REGNO: Special Accessors. (line 54) ! * other register constraints: Simple Constraints. (line 173) * outgoing_args_size: Stack Arguments. (line 48) ! * OUTGOING_REG_PARM_STACK_SPACE: Stack Arguments. (line 80) ! * OUTGOING_REGNO: Register Basics. (line 94) * output of assembler code: File Framework. (line 6) * output statements: Output Statement. (line 6) * output templates: Output Template. (line 6) ! * output_asm_insn: Output Statement. (line 53) ! * OUTPUT_QUOTED_STRING: File Framework. (line 108) ! * OVERLAPPING_REGISTER_NAMES: Instruction Output. (line 21) * OVERLOAD: Functions for C++. (line 6) ! * OVERRIDE_ABI_FORMAT: Register Arguments. (line 155) * OVL_CURRENT: Functions for C++. (line 6) * OVL_NEXT: Functions for C++. (line 6) ! * p in constraint: Simple Constraints. (line 164) ! * PAD_VARARGS_DOWN: Register Arguments. (line 236) * parallel: Side Effects. (line 210) * parameters, c++ abi: C++ ABI. (line 6) * parameters, miscellaneous: Misc. (line 6) * parameters, precompiled headers: PCH Target. (line 6) * parity: Arithmetic. (line 242) ! * parityM2 instruction pattern: Standard Names. (line 949) ! * PARM_BOUNDARY: Storage Layout. (line 135) * PARM_DECL: Declarations. (line 6) * PARSE_LDD_OUTPUT: Macros for Initialization. ! (line 127) * pass dumps: Passes. (line 6) + * pass_duplicate_computed_gotos: Edges. (line 162) * passes and files of the compiler: Passes. (line 6) * passing arguments: Interface. (line 36) * PATH_SEPARATOR: Filesystem. (line 31) ! * PATTERN: Insns. (line 288) * pattern conditions: Patterns. (line 43) * pattern names: Standard Names. (line 6) * Pattern Ordering: Pattern Ordering. (line 6) * patterns: Patterns. (line 6) ! * pc: Regs and Memory. (line 361) * pc and attributes: Insn Lengths. (line 20) * pc, RTL sharing: Sharing. (line 25) ! * PC_REGNUM: Register Basics. (line 108) ! * pc_rtx: Regs and Memory. (line 366) ! * PCC_BITFIELD_TYPE_MATTERS: Storage Layout. (line 334) ! * PCC_STATIC_STRUCT_RETURN: Aggregate Return. (line 65) * PDImode: Machine Modes. (line 40) * peephole optimization, RTL representation: Side Effects. (line 244) * peephole optimizer definitions: Peephole Definitions. *************** Concept Index *** 49633,49680 **** * percent sign: Output Template. (line 6) * PHI nodes: SSA. (line 31) * PIC: PIC. (line 6) ! * PIC_OFFSET_TABLE_REGNUM: PIC. (line 15) ! * PIC_OFFSET_TABLE_REG_CALL_CLOBBERED: PIC. (line 25) * pipeline hazard recognizer: Processor pipeline description. (line 6) - * pipeline hazard recognizer <1>: Processor pipeline description. - (line 53) * Plugins: Plugins. (line 6) * plus: Arithmetic. (line 14) ! * plus and attributes: Expressions. (line 83) * plus, canonicalization of: Insn Canonicalizations. (line 27) * PLUS_EXPR: Unary and Binary Expressions. (line 6) ! * Pmode: Misc. (line 329) * pmode_register_operand: Machine-Independent Predicates. ! (line 34) * pointer: Types. (line 6) - * POINTERS_EXTEND_UNSIGNED: Storage Layout. (line 76) * POINTER_PLUS_EXPR: Unary and Binary Expressions. (line 6) ! * POINTER_SIZE: Storage Layout. (line 70) * POINTER_TYPE: Types. (line 6) ! * popcount: Arithmetic. (line 238) ! * popcountM2 instruction pattern: Standard Names. (line 931) ! * pops_args: Function Entry. (line 104) * pop_operand: Machine-Independent Predicates. ! (line 87) * portability: Portability. (line 6) * position independent code: PIC. (line 6) - * POSTDECREMENT_EXPR: Unary and Binary Expressions. - (line 6) - * POSTINCREMENT_EXPR: Unary and Binary Expressions. - (line 6) * post_dec: Incdec. (line 25) * post_inc: Incdec. (line 30) ! * POST_LINK_SPEC: Driver. (line 236) * post_modify: Incdec. (line 33) * post_order_compute, inverted_post_order_compute, walk_dominator_tree: Basic Blocks. (line 34) ! * POWI_MAX_MULTS: Misc. (line 963) ! * powM3 instruction pattern: Standard Names. (line 785) * pragma: Misc. (line 387) * PREDECREMENT_EXPR: Unary and Binary Expressions. (line 6) * predefined macros: Run-time Target. (line 6) --- 50066,50115 ---- * percent sign: Output Template. (line 6) * PHI nodes: SSA. (line 31) * PIC: PIC. (line 6) ! * PIC_OFFSET_TABLE_REG_CALL_CLOBBERED: PIC. (line 26) ! * PIC_OFFSET_TABLE_REGNUM: PIC. (line 16) * pipeline hazard recognizer: Processor pipeline description. (line 6) * Plugins: Plugins. (line 6) * plus: Arithmetic. (line 14) ! * plus and attributes: Expressions. (line 85) * plus, canonicalization of: Insn Canonicalizations. (line 27) * PLUS_EXPR: Unary and Binary Expressions. (line 6) ! * Pmode: Misc. (line 330) * pmode_register_operand: Machine-Independent Predicates. ! (line 35) * pointer: Types. (line 6) * POINTER_PLUS_EXPR: Unary and Binary Expressions. (line 6) ! * POINTER_SIZE: Storage Layout. (line 71) * POINTER_TYPE: Types. (line 6) ! * POINTERS_EXTEND_UNSIGNED: Storage Layout. (line 77) * pop_operand: Machine-Independent Predicates. ! (line 88) ! * popcount: Arithmetic. (line 238) ! * popcountM2 instruction pattern: Standard Names. (line 937) ! * pops_args: Function Entry. (line 106) * portability: Portability. (line 6) * position independent code: PIC. (line 6) * post_dec: Incdec. (line 25) * post_inc: Incdec. (line 30) ! * POST_LINK_SPEC: Driver. (line 237) * post_modify: Incdec. (line 33) * post_order_compute, inverted_post_order_compute, walk_dominator_tree: Basic Blocks. (line 34) ! * POSTDECREMENT_EXPR: Unary and Binary Expressions. ! (line 6) ! * POSTINCREMENT_EXPR: Unary and Binary Expressions. ! (line 6) ! * POWI_MAX_MULTS: Misc. (line 968) ! * powM3 instruction pattern: Standard Names. (line 791) * pragma: Misc. (line 387) + * pre_dec: Incdec. (line 8) + * PRE_GCC3_DWARF_FRAME_REGISTERS: Frame Registers. (line 127) + * pre_inc: Incdec. (line 22) + * pre_modify: Incdec. (line 51) * PREDECREMENT_EXPR: Unary and Binary Expressions. (line 6) * predefined macros: Run-time Target. (line 6) *************** Concept Index *** 49684,49801 **** (line 6) * predict.def: Profile information. (line 24) ! * PREFERRED_DEBUGGING_TYPE: All Debuggers. (line 41) ! * PREFERRED_RELOAD_CLASS: Register Classes. (line 249) ! * PREFERRED_STACK_BOUNDARY: Storage Layout. (line 147) ! * prefetch: Side Effects. (line 324) * prefetch and /v: Flags. (line 214) ! * prefetch instruction pattern: Standard Names. (line 1779) * PREFETCH_SCHEDULE_BARRIER_P: Flags. (line 214) * PREINCREMENT_EXPR: Unary and Binary Expressions. (line 6) * presence_set: Processor pipeline description. ! (line 223) * preserving SSA form: SSA. (line 74) ! * pretend_args_size: Function Entry. (line 110) * prev_active_insn: define_peephole. (line 60) * PREV_INSN: Insns. (line 26) ! * pre_dec: Incdec. (line 8) ! * PRE_GCC3_DWARF_FRAME_REGISTERS: Frame Registers. (line 126) ! * pre_inc: Incdec. (line 22) ! * pre_modify: Incdec. (line 52) ! * PRINT_OPERAND: Instruction Output. (line 95) ! * PRINT_OPERAND_ADDRESS: Instruction Output. (line 122) ! * PRINT_OPERAND_PUNCT_VALID_P: Instruction Output. (line 115) ! * probe_stack instruction pattern: Standard Names. (line 1628) ! * probe_stack_address instruction pattern: Standard Names. (line 1621) * processor functional units: Processor pipeline description. (line 6) - * processor functional units <1>: Processor pipeline description. - (line 68) * processor pipeline description: Processor pipeline description. (line 6) ! * product: Arithmetic. (line 93) * profile feedback: Profile information. (line 14) * profile representation: Profile information. (line 6) ! * PROFILE_BEFORE_PROLOGUE: Profiling. (line 34) ! * PROFILE_HOOK: Profiling. (line 22) * profiling, code generation: Profiling. (line 6) ! * program counter: Regs and Memory. (line 358) * prologue: Function Entry. (line 6) ! * prologue instruction pattern: Standard Names. (line 1717) ! * PROMOTE_MODE: Storage Layout. (line 87) * pseudo registers: Regs and Memory. (line 9) * PSImode: Machine Modes. (line 32) ! * PTRDIFF_TYPE: Type Layout. (line 163) ! * purge_dead_edges: Edges. (line 103) * purge_dead_edges <1>: Maintaining the CFG. ! (line 81) ! * push address instruction: Simple Constraints. (line 162) ! * pushM1 instruction pattern: Standard Names. (line 288) ! * PUSH_ARGS: Stack Arguments. (line 17) ! * PUSH_ARGS_REVERSED: Stack Arguments. (line 25) * push_operand: Machine-Independent Predicates. ! (line 80) ! * push_reload: Addressing Modes. (line 176) ! * PUSH_ROUNDING: Stack Arguments. (line 31) * PUT_CODE: RTL Objects. (line 47) ! * PUT_MODE: Machine Modes. (line 294) ! * PUT_REG_NOTE_KIND: Insns. (line 346) ! * PUT_SDB_...: SDB and DWARF. (line 114) ! * QCmode: Machine Modes. (line 199) * QFmode: Machine Modes. (line 57) * QImode: Machine Modes. (line 25) ! * QImode, in insn: Insns. (line 268) * QQmode: Machine Modes. (line 106) - * qualified type: Types. (line 6) * qualified type <1>: Types for C++. (line 6) * querying function unit reservations: Processor pipeline description. (line 90) * question mark: Multi-Alternative. (line 42) ! * quotient: Arithmetic. (line 116) ! * r in constraint: Simple Constraints. (line 64) * RDIV_EXPR: Unary and Binary Expressions. (line 6) ! * READONLY_DATA_SECTION_ASM_OP: Sections. (line 62) * real operands: SSA Operands. (line 6) - * REALPART_EXPR: Unary and Binary Expressions. - (line 6) * REAL_CST: Constant expressions. (line 6) ! * REAL_LIBGCC_SPEC: Driver. (line 124) * REAL_NM_FILE_NAME: Macros for Initialization. ! (line 105) * REAL_TYPE: Types. (line 6) ! * REAL_VALUE_ABS: Floating Point. (line 58) ! * REAL_VALUE_ATOF: Floating Point. (line 39) ! * REAL_VALUE_FIX: Floating Point. (line 31) ! * REAL_VALUE_ISINF: Floating Point. (line 49) ! * REAL_VALUE_ISNAN: Floating Point. (line 52) ! * REAL_VALUE_NEGATE: Floating Point. (line 55) ! * REAL_VALUE_NEGATIVE: Floating Point. (line 46) ! * REAL_VALUE_TO_TARGET_DECIMAL128: Data Output. (line 147) ! * REAL_VALUE_TO_TARGET_DECIMAL32: Data Output. (line 145) ! * REAL_VALUE_TO_TARGET_DECIMAL64: Data Output. (line 146) ! * REAL_VALUE_TO_TARGET_DOUBLE: Data Output. (line 143) ! * REAL_VALUE_TO_TARGET_LONG_DOUBLE: Data Output. (line 144) ! * REAL_VALUE_TO_TARGET_SINGLE: Data Output. (line 142) ! * REAL_VALUE_TYPE: Floating Point. (line 25) ! * REAL_VALUE_UNSIGNED_FIX: Floating Point. (line 34) ! * recognizing insns: RTL Template. (line 6) * recog_data.operand: Instruction Output. (line 54) ! * RECORD_TYPE: Types. (line 6) * RECORD_TYPE <1>: Classes. (line 6) * redirect_edge_and_branch: Profile information. (line 71) * redirect_edge_and_branch, redirect_jump: Maintaining the CFG. ! (line 90) ! * reduc_plus_scal_M instruction pattern: Standard Names. (line 390) ! * reduc_smax_scal_M instruction pattern: Standard Names. (line 380) ! * reduc_smin_scal_M instruction pattern: Standard Names. (line 380) ! * reduc_umax_scal_M instruction pattern: Standard Names. (line 385) ! * reduc_umin_scal_M instruction pattern: Standard Names. (line 385) * reference: Types. (line 6) * REFERENCE_TYPE: Types. (line 6) * reg: Regs and Memory. (line 9) --- 50119,50230 ---- (line 6) * predict.def: Profile information. (line 24) ! * PREFERRED_DEBUGGING_TYPE: All Debuggers. (line 42) ! * PREFERRED_RELOAD_CLASS: Register Classes. (line 253) ! * PREFERRED_STACK_BOUNDARY: Storage Layout. (line 149) ! * prefetch: Side Effects. (line 325) * prefetch and /v: Flags. (line 214) ! * prefetch instruction pattern: Standard Names. (line 1790) * PREFETCH_SCHEDULE_BARRIER_P: Flags. (line 214) * PREINCREMENT_EXPR: Unary and Binary Expressions. (line 6) * presence_set: Processor pipeline description. ! (line 224) * preserving SSA form: SSA. (line 74) ! * pretend_args_size: Function Entry. (line 112) * prev_active_insn: define_peephole. (line 60) * PREV_INSN: Insns. (line 26) ! * PRINT_OPERAND: Instruction Output. (line 96) ! * PRINT_OPERAND_ADDRESS: Instruction Output. (line 124) ! * PRINT_OPERAND_PUNCT_VALID_P: Instruction Output. (line 117) ! * probe_stack instruction pattern: Standard Names. (line 1637) ! * probe_stack_address instruction pattern: Standard Names. (line 1630) * processor functional units: Processor pipeline description. (line 6) * processor pipeline description: Processor pipeline description. (line 6) ! * product: Arithmetic. (line 92) * profile feedback: Profile information. (line 14) * profile representation: Profile information. (line 6) ! * PROFILE_BEFORE_PROLOGUE: Profiling. (line 35) ! * PROFILE_HOOK: Profiling. (line 23) * profiling, code generation: Profiling. (line 6) ! * program counter: Regs and Memory. (line 362) * prologue: Function Entry. (line 6) ! * prologue instruction pattern: Standard Names. (line 1728) ! * PROMOTE_MODE: Storage Layout. (line 88) * pseudo registers: Regs and Memory. (line 9) * PSImode: Machine Modes. (line 32) ! * PTRDIFF_TYPE: Type Layout. (line 164) * purge_dead_edges <1>: Maintaining the CFG. ! (line 82) ! * purge_dead_edges: Edges. (line 104) ! * push address instruction: Simple Constraints. (line 164) ! * PUSH_ARGS: Stack Arguments. (line 18) ! * PUSH_ARGS_REVERSED: Stack Arguments. (line 26) * push_operand: Machine-Independent Predicates. ! (line 81) ! * push_reload: Addressing Modes. (line 177) ! * PUSH_ROUNDING: Stack Arguments. (line 32) ! * pushM1 instruction pattern: Standard Names. (line 292) * PUT_CODE: RTL Objects. (line 47) ! * PUT_MODE: Machine Modes. (line 295) ! * PUT_REG_NOTE_KIND: Insns. (line 352) ! * PUT_SDB_: SDB and DWARF. (line 115) ! * QCmode: Machine Modes. (line 200) * QFmode: Machine Modes. (line 57) * QImode: Machine Modes. (line 25) ! * QImode, in insn: Insns. (line 272) * QQmode: Machine Modes. (line 106) * qualified type <1>: Types for C++. (line 6) + * qualified type: Types. (line 6) * querying function unit reservations: Processor pipeline description. (line 90) * question mark: Multi-Alternative. (line 42) ! * quotient: Arithmetic. (line 115) ! * r in constraint: Simple Constraints. (line 66) * RDIV_EXPR: Unary and Binary Expressions. (line 6) ! * READONLY_DATA_SECTION_ASM_OP: Sections. (line 63) * real operands: SSA Operands. (line 6) * REAL_CST: Constant expressions. (line 6) ! * REAL_LIBGCC_SPEC: Driver. (line 125) * REAL_NM_FILE_NAME: Macros for Initialization. ! (line 106) * REAL_TYPE: Types. (line 6) ! * REAL_VALUE_ABS: Floating Point. (line 59) ! * REAL_VALUE_ATOF: Floating Point. (line 41) ! * REAL_VALUE_FIX: Floating Point. (line 32) ! * REAL_VALUE_ISINF: Floating Point. (line 50) ! * REAL_VALUE_ISNAN: Floating Point. (line 53) ! * REAL_VALUE_NEGATE: Floating Point. (line 56) ! * REAL_VALUE_NEGATIVE: Floating Point. (line 47) ! * REAL_VALUE_TO_TARGET_DECIMAL128: Data Output. (line 149) ! * REAL_VALUE_TO_TARGET_DECIMAL32: Data Output. (line 147) ! * REAL_VALUE_TO_TARGET_DECIMAL64: Data Output. (line 148) ! * REAL_VALUE_TO_TARGET_DOUBLE: Data Output. (line 145) ! * REAL_VALUE_TO_TARGET_LONG_DOUBLE: Data Output. (line 146) ! * REAL_VALUE_TO_TARGET_SINGLE: Data Output. (line 144) ! * REAL_VALUE_TYPE: Floating Point. (line 26) ! * REAL_VALUE_UNSIGNED_FIX: Floating Point. (line 36) ! * REALPART_EXPR: Unary and Binary Expressions. ! (line 6) * recog_data.operand: Instruction Output. (line 54) ! * recognizing insns: RTL Template. (line 6) * RECORD_TYPE <1>: Classes. (line 6) + * RECORD_TYPE: Types. (line 6) * redirect_edge_and_branch: Profile information. (line 71) * redirect_edge_and_branch, redirect_jump: Maintaining the CFG. ! (line 92) ! * reduc_plus_scal_M instruction pattern: Standard Names. (line 394) ! * reduc_smax_scal_M instruction pattern: Standard Names. (line 384) ! * reduc_smin_scal_M instruction pattern: Standard Names. (line 384) ! * reduc_umax_scal_M instruction pattern: Standard Names. (line 389) ! * reduc_umin_scal_M instruction pattern: Standard Names. (line 389) * reference: Types. (line 6) * REFERENCE_TYPE: Types. (line 6) * reg: Regs and Memory. (line 9) *************** Concept Index *** 49803,49957 **** * reg and /i: Flags. (line 89) * reg and /v: Flags. (line 98) * reg, RTL sharing: Sharing. (line 17) ! * register allocation order: Allocation Order. (line 6) ! * register class definitions: Register Classes. (line 6) ! * register class preference constraints: Class Preferences. (line 6) ! * register pairs: Values in Registers. ! (line 69) ! * Register Transfer Language (RTL): RTL. (line 6) ! * register usage: Registers. (line 6) ! * registers arguments: Register Arguments. (line 6) ! * registers in constraints: Simple Constraints. (line 64) ! * REGISTER_MOVE_COST: Costs. (line 9) ! * REGISTER_NAMES: Instruction Output. (line 8) ! * register_operand: Machine-Independent Predicates. ! (line 29) ! * REGISTER_PREFIX: Instruction Output. (line 150) ! * REGISTER_TARGET_PRAGMAS: Misc. (line 387) ! * REGMODE_NATURAL_SIZE: Values in Registers. ! (line 49) ! * REGNO_MODE_CODE_OK_FOR_BASE_P: Register Classes. (line 172) ! * REGNO_MODE_OK_FOR_BASE_P: Register Classes. (line 150) ! * REGNO_MODE_OK_FOR_REG_BASE_P: Register Classes. (line 160) ! * REGNO_OK_FOR_BASE_P: Register Classes. (line 146) ! * REGNO_OK_FOR_INDEX_P: Register Classes. (line 186) ! * REGNO_REG_CLASS: Register Classes. (line 105) ! * regs_ever_live: Function Entry. (line 21) ! * regular expressions: Processor pipeline description. ! (line 6) ! * regular expressions <1>: Processor pipeline description. ! (line 105) ! * REG_ALLOC_ORDER: Allocation Order. (line 8) ! * REG_BR_PRED: Insns. (line 526) ! * REG_BR_PROB: Insns. (line 519) * REG_BR_PROB_BASE, BB_FREQ_BASE, count: Profile information. (line 82) * REG_BR_PROB_BASE, EDGE_FREQUENCY: Profile information. (line 52) ! * REG_CC_SETTER: Insns. (line 491) ! * REG_CC_USER: Insns. (line 491) * reg_class_contents: Register Basics. (line 59) - * REG_CLASS_CONTENTS: Register Classes. (line 91) * reg_class_for_constraint: C Constraint Interface. ! (line 48) ! * REG_CLASS_NAMES: Register Classes. (line 86) ! * REG_CROSSING_JUMP: Insns. (line 405) ! * REG_DEAD: Insns. (line 357) * REG_DEAD, REG_UNUSED: Liveness information. (line 32) ! * REG_DEP_ANTI: Insns. (line 513) ! * REG_DEP_OUTPUT: Insns. (line 509) ! * REG_DEP_TRUE: Insns. (line 506) ! * REG_EH_REGION, EDGE_ABNORMAL_CALL: Edges. (line 109) ! * REG_EQUAL: Insns. (line 420) ! * REG_EQUIV: Insns. (line 420) ! * REG_EXPR: Special Accessors. (line 58) ! * REG_FRAME_RELATED_EXPR: Insns. (line 532) * REG_FUNCTION_VALUE_P: Flags. (line 89) ! * REG_INC: Insns. (line 373) * reg_label and /v: Flags. (line 65) ! * REG_LABEL_OPERAND: Insns. (line 387) ! * REG_LABEL_TARGET: Insns. (line 396) * reg_names: Register Basics. (line 59) ! * reg_names <1>: Instruction Output. (line 107) ! * REG_NONNEG: Insns. (line 379) ! * REG_NOTES: Insns. (line 321) ! * REG_NOTE_KIND: Insns. (line 346) ! * REG_OFFSET: Special Accessors. (line 62) ! * REG_OK_STRICT: Addressing Modes. (line 99) ! * REG_PARM_STACK_SPACE: Stack Arguments. (line 58) * REG_PARM_STACK_SPACE, and TARGET_FUNCTION_ARG: Register Arguments. ! (line 56) * REG_POINTER: Flags. (line 94) ! * REG_SETJMP: Insns. (line 414) ! * REG_UNUSED: Insns. (line 366) * REG_USERVAR_P: Flags. (line 98) ! * REG_VALUE_IN_UNWIND_CONTEXT: Frame Registers. (line 158) ! * REG_WORDS_BIG_ENDIAN: Storage Layout. (line 35) * relative costs: Costs. (line 6) ! * RELATIVE_PREFIX_NOT_LINKDIR: Driver. (line 266) ! * reloading: RTL passes. (line 170) ! * reload_completed: Standard Names. (line 1416) ! * reload_in instruction pattern: Standard Names. (line 98) * reload_in_progress: Standard Names. (line 57) ! * reload_out instruction pattern: Standard Names. (line 98) ! * remainder: Arithmetic. (line 136) ! * remainderM3 instruction pattern: Standard Names. (line 639) ! * reorder: GTY Options. (line 173) * representation of RTL: RTL. (line 6) * reservation delays: Processor pipeline description. (line 6) ! * restore_stack_block instruction pattern: Standard Names. (line 1542) * restore_stack_function instruction pattern: Standard Names. ! (line 1542) * restore_stack_nonlocal instruction pattern: Standard Names. ! (line 1542) ! * rest_of_decl_compilation: Parsing pass. (line 51) ! * rest_of_type_compilation: Parsing pass. (line 51) * RESULT_DECL: Declarations. (line 6) * return: Side Effects. (line 72) ! * return instruction pattern: Standard Names. (line 1390) * return values in registers: Scalar Return. (line 6) ! * returning aggregate values: Aggregate Return. (line 6) ! * returning structures and unions: Interface. (line 10) ! * RETURN_ADDRESS_POINTER_REGNUM: Frame Registers. (line 64) ! * RETURN_ADDR_IN_PREVIOUS_FRAME: Frame Layout. (line 129) ! * RETURN_ADDR_OFFSET: Exception Handling. (line 59) ! * RETURN_ADDR_RTX: Frame Layout. (line 118) * RETURN_EXPR: Statements for C++. (line 6) * RETURN_STMT: Statements for C++. (line 6) * return_val: Flags. (line 274) * return_val, in call_insn: Flags. (line 24) * return_val, in reg: Flags. (line 89) * return_val, in symbol_ref: Flags. (line 202) * reverse probability: Profile information. (line 66) * REVERSE_CONDITION: MODE_CC Condition Codes. ! (line 92) * REVERSIBLE_CC_MODE: MODE_CC Condition Codes. ! (line 77) ! * right rotate: Arithmetic. (line 195) ! * right shift: Arithmetic. (line 190) ! * rintM2 instruction pattern: Standard Names. (line 837) * RISC: Processor pipeline description. (line 6) - * RISC <1>: Processor pipeline description. - (line 223) * roots, marking: GGC Roots. (line 6) ! * rotate: Arithmetic. (line 195) ! * rotate <1>: Arithmetic. (line 195) ! * rotatert: Arithmetic. (line 195) ! * rotlM3 instruction pattern: Standard Names. (line 591) ! * rotrM3 instruction pattern: Standard Names. (line 591) ! * roundM2 instruction pattern: Standard Names. (line 814) * ROUND_DIV_EXPR: Unary and Binary Expressions. (line 6) * ROUND_MOD_EXPR: Unary and Binary Expressions. (line 6) ! * ROUND_TYPE_ALIGN: Storage Layout. (line 427) * RSHIFT_EXPR: Unary and Binary Expressions. (line 6) ! * rsqrtM2 instruction pattern: Standard Names. (line 619) * RTL addition: Arithmetic. (line 14) * RTL addition with signed saturation: Arithmetic. (line 14) * RTL addition with unsigned saturation: Arithmetic. (line 14) * RTL classes: RTL Classes. (line 6) ! * RTL comparison: Arithmetic. (line 46) * RTL comparison operations: Comparisons. (line 6) * RTL constant expression types: Constants. (line 6) * RTL constants: Constants. (line 6) * RTL declarations: RTL Declarations. (line 6) ! * RTL difference: Arithmetic. (line 38) * RTL expression: RTL Objects. (line 6) * RTL expressions for arithmetic: Arithmetic. (line 6) * RTL format: RTL Classes. (line 72) --- 50232,50381 ---- * reg and /i: Flags. (line 89) * reg and /v: Flags. (line 98) * reg, RTL sharing: Sharing. (line 17) ! * REG_ALLOC_ORDER: Allocation Order. (line 9) ! * REG_BR_PRED: Insns. (line 534) ! * REG_BR_PROB: Insns. (line 527) * REG_BR_PROB_BASE, BB_FREQ_BASE, count: Profile information. (line 82) * REG_BR_PROB_BASE, EDGE_FREQUENCY: Profile information. (line 52) ! * REG_CC_SETTER: Insns. (line 498) ! * REG_CC_USER: Insns. (line 498) ! * REG_CLASS_CONTENTS: Register Classes. (line 93) * reg_class_contents: Register Basics. (line 59) * reg_class_for_constraint: C Constraint Interface. ! (line 50) ! * REG_CLASS_NAMES: Register Classes. (line 88) ! * REG_CROSSING_JUMP: Insns. (line 411) ! * REG_DEAD: Insns. (line 363) * REG_DEAD, REG_UNUSED: Liveness information. (line 32) ! * REG_DEP_ANTI: Insns. (line 520) ! * REG_DEP_OUTPUT: Insns. (line 516) ! * REG_DEP_TRUE: Insns. (line 513) ! * REG_EH_REGION, EDGE_ABNORMAL_CALL: Edges. (line 110) ! * REG_EQUAL: Insns. (line 426) ! * REG_EQUIV: Insns. (line 426) ! * REG_EXPR: Special Accessors. (line 60) ! * REG_FRAME_RELATED_EXPR: Insns. (line 540) * REG_FUNCTION_VALUE_P: Flags. (line 89) ! * REG_INC: Insns. (line 379) * reg_label and /v: Flags. (line 65) ! * REG_LABEL_OPERAND: Insns. (line 393) ! * REG_LABEL_TARGET: Insns. (line 402) ! * reg_names <1>: Instruction Output. (line 108) * reg_names: Register Basics. (line 59) ! * REG_NONNEG: Insns. (line 385) ! * REG_NOTE_KIND: Insns. (line 352) ! * REG_NOTES: Insns. (line 325) ! * REG_OFFSET: Special Accessors. (line 64) ! * REG_OK_STRICT: Addressing Modes. (line 100) ! * REG_PARM_STACK_SPACE: Stack Arguments. (line 59) * REG_PARM_STACK_SPACE, and TARGET_FUNCTION_ARG: Register Arguments. ! (line 57) * REG_POINTER: Flags. (line 94) ! * REG_SETJMP: Insns. (line 420) ! * REG_UNUSED: Insns. (line 372) * REG_USERVAR_P: Flags. (line 98) ! * REG_VALUE_IN_UNWIND_CONTEXT: Frame Registers. (line 157) ! * REG_WORDS_BIG_ENDIAN: Storage Layout. (line 36) ! * register allocation order: Allocation Order. (line 6) ! * register class definitions: Register Classes. (line 6) ! * register class preference constraints: Class Preferences. (line 6) ! * register pairs: Values in Registers. ! (line 69) ! * Register Transfer Language (RTL): RTL. (line 6) ! * register usage: Registers. (line 6) ! * REGISTER_MOVE_COST: Costs. (line 10) ! * REGISTER_NAMES: Instruction Output. (line 9) ! * register_operand: Machine-Independent Predicates. ! (line 30) ! * REGISTER_PREFIX: Instruction Output. (line 152) ! * REGISTER_TARGET_PRAGMAS: Misc. (line 388) ! * registers arguments: Register Arguments. (line 6) ! * registers in constraints: Simple Constraints. (line 66) ! * REGMODE_NATURAL_SIZE: Values in Registers. ! (line 50) ! * REGNO_MODE_CODE_OK_FOR_BASE_P: Register Classes. (line 176) ! * REGNO_MODE_OK_FOR_BASE_P: Register Classes. (line 153) ! * REGNO_MODE_OK_FOR_REG_BASE_P: Register Classes. (line 163) ! * REGNO_OK_FOR_BASE_P: Register Classes. (line 149) ! * REGNO_OK_FOR_INDEX_P: Register Classes. (line 190) ! * REGNO_REG_CLASS: Register Classes. (line 108) ! * regs_ever_live: Function Entry. (line 21) ! * regular expressions: Processor pipeline description. ! (line 6) * relative costs: Costs. (line 6) ! * RELATIVE_PREFIX_NOT_LINKDIR: Driver. (line 267) ! * reload_completed: Standard Names. (line 1423) ! * reload_in instruction pattern: Standard Names. (line 99) * reload_in_progress: Standard Names. (line 57) ! * reload_out instruction pattern: Standard Names. (line 99) ! * reloading: RTL passes. (line 171) ! * remainder: Arithmetic. (line 135) ! * remainderM3 instruction pattern: Standard Names. (line 645) ! * reorder: GTY Options. (line 168) * representation of RTL: RTL. (line 6) * reservation delays: Processor pipeline description. (line 6) ! * rest_of_decl_compilation: Parsing pass. (line 52) ! * rest_of_type_compilation: Parsing pass. (line 52) ! * restore_stack_block instruction pattern: Standard Names. (line 1550) * restore_stack_function instruction pattern: Standard Names. ! (line 1550) * restore_stack_nonlocal instruction pattern: Standard Names. ! (line 1550) * RESULT_DECL: Declarations. (line 6) * return: Side Effects. (line 72) ! * return instruction pattern: Standard Names. (line 1396) * return values in registers: Scalar Return. (line 6) ! * RETURN_ADDR_IN_PREVIOUS_FRAME: Frame Layout. (line 131) ! * RETURN_ADDR_OFFSET: Exception Handling. (line 60) ! * RETURN_ADDR_RTX: Frame Layout. (line 120) ! * RETURN_ADDRESS_POINTER_REGNUM: Frame Registers. (line 65) * RETURN_EXPR: Statements for C++. (line 6) * RETURN_STMT: Statements for C++. (line 6) * return_val: Flags. (line 274) * return_val, in call_insn: Flags. (line 24) * return_val, in reg: Flags. (line 89) * return_val, in symbol_ref: Flags. (line 202) + * returning aggregate values: Aggregate Return. (line 6) + * returning structures and unions: Interface. (line 10) * reverse probability: Profile information. (line 66) * REVERSE_CONDITION: MODE_CC Condition Codes. ! (line 93) * REVERSIBLE_CC_MODE: MODE_CC Condition Codes. ! (line 78) ! * right rotate: Arithmetic. (line 194) ! * right shift: Arithmetic. (line 189) ! * rintM2 instruction pattern: Standard Names. (line 843) * RISC: Processor pipeline description. (line 6) * roots, marking: GGC Roots. (line 6) ! * rotate: Arithmetic. (line 194) ! * rotatert: Arithmetic. (line 194) ! * rotlM3 instruction pattern: Standard Names. (line 597) ! * rotrM3 instruction pattern: Standard Names. (line 597) * ROUND_DIV_EXPR: Unary and Binary Expressions. (line 6) * ROUND_MOD_EXPR: Unary and Binary Expressions. (line 6) ! * ROUND_TYPE_ALIGN: Storage Layout. (line 432) ! * roundM2 instruction pattern: Standard Names. (line 820) * RSHIFT_EXPR: Unary and Binary Expressions. (line 6) ! * rsqrtM2 instruction pattern: Standard Names. (line 625) * RTL addition: Arithmetic. (line 14) * RTL addition with signed saturation: Arithmetic. (line 14) * RTL addition with unsigned saturation: Arithmetic. (line 14) * RTL classes: RTL Classes. (line 6) ! * RTL comparison: Arithmetic. (line 43) * RTL comparison operations: Comparisons. (line 6) * RTL constant expression types: Constants. (line 6) * RTL constants: Constants. (line 6) * RTL declarations: RTL Declarations. (line 6) ! * RTL difference: Arithmetic. (line 36) * RTL expression: RTL Objects. (line 6) * RTL expressions for arithmetic: Arithmetic. (line 6) * RTL format: RTL Classes. (line 72) *************** Concept Index *** 49970,49978 **** * RTL side effect expressions: Side Effects. (line 6) * RTL strings: RTL Objects. (line 6) * RTL structure sharing assumptions: Sharing. (line 6) ! * RTL subtraction: Arithmetic. (line 38) ! * RTL subtraction with signed saturation: Arithmetic. (line 38) ! * RTL subtraction with unsigned saturation: Arithmetic. (line 38) * RTL sum: Arithmetic. (line 14) * RTL vectors: RTL Objects. (line 6) * RTL_CONST_CALL_P: Flags. (line 19) --- 50394,50402 ---- * RTL side effect expressions: Side Effects. (line 6) * RTL strings: RTL Objects. (line 6) * RTL structure sharing assumptions: Sharing. (line 6) ! * RTL subtraction: Arithmetic. (line 36) ! * RTL subtraction with signed saturation: Arithmetic. (line 36) ! * RTL subtraction with unsigned saturation: Arithmetic. (line 36) * RTL sum: Arithmetic. (line 14) * RTL vectors: RTL Objects. (line 6) * RTL_CONST_CALL_P: Flags. (line 19) *************** Concept Index *** 49984,50199 **** * RTX_FRAME_RELATED_P: Flags. (line 107) * run-time conventions: Interface. (line 6) * run-time target specification: Run-time Target. (line 6) ! * s in constraint: Simple Constraints. (line 100) * SAD_EXPR: Vectors. (line 6) ! * same_type_p: Types. (line 86) ! * SAmode: Machine Modes. (line 150) ! * satfractMN2 instruction pattern: Standard Names. (line 1141) ! * satfractunsMN2 instruction pattern: Standard Names. (line 1154) ! * satisfies_constraint_M: C Constraint Interface. ! (line 36) * sat_fract: Conversions. (line 90) * SAVE_EXPR: Unary and Binary Expressions. (line 6) ! * save_stack_block instruction pattern: Standard Names. (line 1542) ! * save_stack_function instruction pattern: Standard Names. (line 1542) ! * save_stack_nonlocal instruction pattern: Standard Names. (line 1542) ! * SBSS_SECTION_ASM_OP: Sections. (line 75) * Scalar evolutions: Scalar evolutions. (line 6) * scalars, returned as values: Scalar Return. (line 6) ! * scalbM3 instruction pattern: Standard Names. (line 646) * SCHED_GROUP_P: Flags. (line 148) ! * SCmode: Machine Modes. (line 199) ! * scratch: Regs and Memory. (line 294) ! * scratch operands: Regs and Memory. (line 294) * scratch, RTL sharing: Sharing. (line 35) * scratch_operand: Machine-Independent Predicates. ! (line 49) ! * SDATA_SECTION_ASM_OP: Sections. (line 57) ! * SDB_ALLOW_FORWARD_REFERENCES: SDB and DWARF. (line 132) ! * SDB_ALLOW_UNKNOWN_REFERENCES: SDB and DWARF. (line 127) ! * SDB_DEBUGGING_INFO: SDB and DWARF. (line 8) ! * SDB_DELIM: SDB and DWARF. (line 120) ! * SDB_OUTPUT_SOURCE_LINE: SDB and DWARF. (line 137) * SDmode: Machine Modes. (line 88) ! * sdot_prodM instruction pattern: Standard Names. (line 395) ! * search options: Including Patterns. (line 47) ! * SECONDARY_INPUT_RELOAD_CLASS: Register Classes. (line 391) ! * SECONDARY_MEMORY_NEEDED: Register Classes. (line 447) ! * SECONDARY_MEMORY_NEEDED_MODE: Register Classes. (line 466) ! * SECONDARY_MEMORY_NEEDED_RTX: Register Classes. (line 457) ! * SECONDARY_OUTPUT_RELOAD_CLASS: Register Classes. (line 392) ! * SECONDARY_RELOAD_CLASS: Register Classes. (line 390) * SELECT_CC_MODE: MODE_CC Condition Codes. ! (line 6) ! * sequence: Side Effects. (line 259) * Sequence iterators: Sequence iterators. (line 6) * set: Side Effects. (line 15) * set and /f: Flags. (line 107) ! * setmemM instruction pattern: Standard Names. (line 1005) ! * SETUP_FRAME_ADDRESSES: Frame Layout. (line 96) ! * SET_ASM_OP: Label Output. (line 451) ! * SET_ASM_OP <1>: Label Output. (line 462) * set_attr: Tagging Insns. (line 31) * set_attr_alternative: Tagging Insns. (line 49) ! * set_bb_seq: GIMPLE sequences. (line 75) * SET_DEST: Side Effects. (line 69) * SET_IS_RETURN_P: Flags. (line 157) * SET_LABEL_KIND: Insns. (line 146) * set_optab_libfunc: Library Calls. (line 15) ! * SET_RATIO: Costs. (line 216) * SET_SRC: Side Effects. (line 69) * set_thread_pointerMODE instruction pattern: Standard Names. ! (line 2073) * SET_TYPE_STRUCTURAL_EQUALITY: Types. (line 6) ! * SET_TYPE_STRUCTURAL_EQUALITY <1>: Types. (line 81) * SFmode: Machine Modes. (line 69) * sharing of RTL components: Sharing. (line 6) ! * shift: Arithmetic. (line 173) ! * SHIFT_COUNT_TRUNCATED: Misc. (line 112) * SHLIB_SUFFIX: Macros for Initialization. ! (line 133) ! * SHORT_ACCUM_TYPE_SIZE: Type Layout. (line 82) ! * SHORT_FRACT_TYPE_SIZE: Type Layout. (line 62) ! * SHORT_IMMEDIATES_SIGN_EXTEND: Misc. (line 86) ! * SHORT_TYPE_SIZE: Type Layout. (line 15) ! * sibcall_epilogue instruction pattern: Standard Names. (line 1749) ! * sibling call: Edges. (line 121) * SIBLING_CALL_P: Flags. (line 161) ! * signed division: Arithmetic. (line 116) ! * signed division with signed saturation: Arithmetic. (line 116) ! * signed maximum: Arithmetic. (line 141) ! * signed minimum: Arithmetic. (line 141) ! * significandM2 instruction pattern: Standard Names. (line 778) * sign_extend: Conversions. (line 23) * sign_extract: Bit-Fields. (line 8) * sign_extract, canonicalization of: Insn Canonicalizations. ! (line 87) ! * SIG_ATOMIC_TYPE: Type Layout. (line 214) * SImode: Machine Modes. (line 37) * simple constraints: Simple Constraints. (line 6) * simple_return: Side Effects. (line 86) ! * simple_return instruction pattern: Standard Names. (line 1405) ! * sincosM3 instruction pattern: Standard Names. (line 674) ! * sinM2 instruction pattern: Standard Names. (line 668) ! * SIZETYPE: Type Layout. (line 153) ! * SIZE_ASM_OP: Label Output. (line 33) ! * SIZE_TYPE: Type Layout. (line 137) ! * skip: GTY Options. (line 76) ! * SLOW_BYTE_ACCESS: Costs. (line 117) ! * SLOW_UNALIGNED_ACCESS: Costs. (line 132) ! * smax: Arithmetic. (line 141) ! * smin: Arithmetic. (line 141) ! * sms, swing, software pipelining: RTL passes. (line 123) ! * smulM3_highpart instruction pattern: Standard Names. (line 504) * soft float library: Soft float library routines. (line 6) ! * special: GTY Options. (line 236) * special predicates: Predicates. (line 31) * SPECS: Target Fragment. (line 191) * speed of instructions: Costs. (line 6) - * splitting instructions: Insn Splitting. (line 6) * split_block: Maintaining the CFG. ! (line 97) * SQmode: Machine Modes. (line 114) * sqrt: Arithmetic. (line 206) ! * sqrtM2 instruction pattern: Standard Names. (line 613) * square root: Arithmetic. (line 206) ! * SSA: SSA. (line 6) ! * ssaddM3 instruction pattern: Standard Names. (line 301) ! * ssadM instruction pattern: Standard Names. (line 404) ! * ssashlM3 instruction pattern: Standard Names. (line 579) ! * SSA_NAME_DEF_STMT: SSA. (line 184) ! * SSA_NAME_VERSION: SSA. (line 189) ! * ssdivM3 instruction pattern: Standard Names. (line 301) ! * ssmaddMN4 instruction pattern: Standard Names. (line 527) ! * ssmsubMN4 instruction pattern: Standard Names. (line 551) ! * ssmulM3 instruction pattern: Standard Names. (line 301) ! * ssnegM2 instruction pattern: Standard Names. (line 603) ! * sssubM3 instruction pattern: Standard Names. (line 301) ! * ss_abs: Arithmetic. (line 200) ! * ss_ashift: Arithmetic. (line 173) ! * ss_div: Arithmetic. (line 116) ! * ss_minus: Arithmetic. (line 38) ! * ss_mult: Arithmetic. (line 93) ! * ss_neg: Arithmetic. (line 82) * ss_plus: Arithmetic. (line 14) * ss_truncate: Conversions. (line 43) * stack arguments: Stack Arguments. (line 6) * stack frame layout: Frame Layout. (line 6) * stack smashing protection: Stack Smashing Protection. (line 6) ! * STACK_ALIGNMENT_NEEDED: Frame Layout. (line 43) ! * STACK_BOUNDARY: Storage Layout. (line 139) ! * STACK_CHECK_BUILTIN: Stack Checking. (line 31) ! * STACK_CHECK_FIXED_FRAME_SIZE: Stack Checking. (line 83) ! * STACK_CHECK_MAX_FRAME_SIZE: Stack Checking. (line 74) ! * STACK_CHECK_MAX_VAR_SIZE: Stack Checking. (line 90) ! * STACK_CHECK_MOVING_SP: Stack Checking. (line 53) ! * STACK_CHECK_PROBE_INTERVAL_EXP: Stack Checking. (line 45) ! * STACK_CHECK_PROTECT: Stack Checking. (line 62) ! * STACK_CHECK_STATIC_BUILTIN: Stack Checking. (line 38) ! * STACK_DYNAMIC_OFFSET: Frame Layout. (line 69) * STACK_DYNAMIC_OFFSET and virtual registers: Regs and Memory. (line 83) ! * STACK_GROWS_DOWNWARD: Frame Layout. (line 8) ! * STACK_PARMS_IN_REG_PARM_AREA: Stack Arguments. (line 89) ! * STACK_POINTER_OFFSET: Frame Layout. (line 53) * STACK_POINTER_OFFSET and virtual registers: Regs and Memory. (line 93) ! * STACK_POINTER_REGNUM: Frame Registers. (line 8) * STACK_POINTER_REGNUM and virtual registers: Regs and Memory. (line 83) * stack_pointer_rtx: Frame Registers. (line 104) ! * stack_protect_set instruction pattern: Standard Names. (line 2083) ! * stack_protect_test instruction pattern: Standard Names. (line 2093) ! * STACK_PUSH_CODE: Frame Layout. (line 12) ! * STACK_REGS: Stack Registers. (line 19) ! * STACK_REG_COVER_CLASS: Stack Registers. (line 22) ! * STACK_SAVEAREA_MODE: Storage Layout. (line 443) ! * STACK_SIZE_MODE: Storage Layout. (line 454) ! * STACK_SLOT_ALIGNMENT: Storage Layout. (line 275) * standard pattern names: Standard Names. (line 6) ! * STANDARD_STARTFILE_PREFIX: Driver. (line 278) ! * STANDARD_STARTFILE_PREFIX_1: Driver. (line 285) ! * STANDARD_STARTFILE_PREFIX_2: Driver. (line 292) ! * STARTFILE_SPEC: Driver. (line 147) ! * STARTING_FRAME_OFFSET: Frame Layout. (line 34) * STARTING_FRAME_OFFSET and virtual registers: Regs and Memory. (line 74) * Statement and operand traversals: Statement and operand traversals. (line 6) * Statement Sequences: Statement Sequences. (line 6) ! * Statements: Statements. (line 6) * statements: Function Properties. (line 6) ! * statements <1>: Statements for C++. (line 6) * Static profile estimation: Profile information. (line 24) * static single assignment: SSA. (line 6) ! * STATIC_CHAIN_INCOMING_REGNUM: Frame Registers. (line 77) ! * STATIC_CHAIN_REGNUM: Frame Registers. (line 76) * stdarg.h and register arguments: Register Arguments. (line 51) ! * STDC_0_IN_SYSTEM_HEADERS: Misc. (line 350) * STMT_EXPR: Unary and Binary Expressions. (line 6) * STMT_IS_FULL_EXPR_P: Statements for C++. (line 22) * storage layout: Storage Layout. (line 6) ! * STORE_FLAG_VALUE: Misc. (line 201) ! * store_multiple instruction pattern: Standard Names. (line 159) ! * strcpy: Storage Layout. (line 228) ! * STRICT_ALIGNMENT: Storage Layout. (line 325) * strict_low_part: RTL Declarations. (line 9) ! * strict_memory_address_p: Addressing Modes. (line 186) * STRING_CST: Constant expressions. (line 6) * STRING_POOL_ADDRESS_P: Flags. (line 165) ! * strlenM instruction pattern: Standard Names. (line 1076) * structure value address: Aggregate Return. (line 6) * structures, returning: Interface. (line 10) ! * STRUCTURE_SIZE_BOUNDARY: Storage Layout. (line 317) ! * subM3 instruction pattern: Standard Names. (line 301) * SUBOBJECT: Statements for C++. (line 6) * SUBOBJECT_CLEANUP: Statements for C++. (line 6) * subreg: Regs and Memory. (line 97) --- 50408,50621 ---- * RTX_FRAME_RELATED_P: Flags. (line 107) * run-time conventions: Interface. (line 6) * run-time target specification: Run-time Target. (line 6) ! * s in constraint: Simple Constraints. (line 102) * SAD_EXPR: Vectors. (line 6) ! * same_type_p: Types. (line 88) ! * SAmode: Machine Modes. (line 151) * sat_fract: Conversions. (line 90) + * satfractMN2 instruction pattern: Standard Names. (line 1147) + * satfractunsMN2 instruction pattern: Standard Names. (line 1160) + * satisfies_constraint_: C Constraint Interface. + (line 37) * SAVE_EXPR: Unary and Binary Expressions. (line 6) ! * save_stack_block instruction pattern: Standard Names. (line 1550) ! * save_stack_function instruction pattern: Standard Names. (line 1550) ! * save_stack_nonlocal instruction pattern: Standard Names. (line 1550) ! * SBSS_SECTION_ASM_OP: Sections. (line 76) * Scalar evolutions: Scalar evolutions. (line 6) * scalars, returned as values: Scalar Return. (line 6) ! * scalbM3 instruction pattern: Standard Names. (line 652) * SCHED_GROUP_P: Flags. (line 148) ! * SCmode: Machine Modes. (line 200) ! * scratch: Regs and Memory. (line 298) ! * scratch operands: Regs and Memory. (line 298) * scratch, RTL sharing: Sharing. (line 35) * scratch_operand: Machine-Independent Predicates. ! (line 50) ! * SDATA_SECTION_ASM_OP: Sections. (line 58) ! * SDB_ALLOW_FORWARD_REFERENCES: SDB and DWARF. (line 133) ! * SDB_ALLOW_UNKNOWN_REFERENCES: SDB and DWARF. (line 128) ! * SDB_DEBUGGING_INFO: SDB and DWARF. (line 9) ! * SDB_DELIM: SDB and DWARF. (line 121) ! * SDB_OUTPUT_SOURCE_LINE: SDB and DWARF. (line 138) * SDmode: Machine Modes. (line 88) ! * sdot_prodM instruction pattern: Standard Names. (line 399) ! * search options: Including Patterns. (line 44) ! * SECONDARY_INPUT_RELOAD_CLASS: Register Classes. (line 396) ! * SECONDARY_MEMORY_NEEDED: Register Classes. (line 452) ! * SECONDARY_MEMORY_NEEDED_MODE: Register Classes. (line 471) ! * SECONDARY_MEMORY_NEEDED_RTX: Register Classes. (line 462) ! * SECONDARY_OUTPUT_RELOAD_CLASS: Register Classes. (line 397) ! * SECONDARY_RELOAD_CLASS: Register Classes. (line 395) * SELECT_CC_MODE: MODE_CC Condition Codes. ! (line 7) ! * sequence: Side Effects. (line 260) * Sequence iterators: Sequence iterators. (line 6) * set: Side Effects. (line 15) * set and /f: Flags. (line 107) ! * SET_ASM_OP: Label Output. (line 454) * set_attr: Tagging Insns. (line 31) * set_attr_alternative: Tagging Insns. (line 49) ! * set_bb_seq: GIMPLE sequences. (line 76) * SET_DEST: Side Effects. (line 69) * SET_IS_RETURN_P: Flags. (line 157) * SET_LABEL_KIND: Insns. (line 146) * set_optab_libfunc: Library Calls. (line 15) ! * SET_RATIO: Costs. (line 217) * SET_SRC: Side Effects. (line 69) * set_thread_pointerMODE instruction pattern: Standard Names. ! (line 2084) * SET_TYPE_STRUCTURAL_EQUALITY: Types. (line 6) ! * setmemM instruction pattern: Standard Names. (line 1011) ! * SETUP_FRAME_ADDRESSES: Frame Layout. (line 98) * SFmode: Machine Modes. (line 69) * sharing of RTL components: Sharing. (line 6) ! * shift: Arithmetic. (line 172) ! * SHIFT_COUNT_TRUNCATED: Misc. (line 113) * SHLIB_SUFFIX: Macros for Initialization. ! (line 135) ! * SHORT_ACCUM_TYPE_SIZE: Type Layout. (line 83) ! * SHORT_FRACT_TYPE_SIZE: Type Layout. (line 63) ! * SHORT_IMMEDIATES_SIGN_EXTEND: Misc. (line 87) ! * SHORT_TYPE_SIZE: Type Layout. (line 16) ! * sibcall_epilogue instruction pattern: Standard Names. (line 1760) ! * sibling call: Edges. (line 122) * SIBLING_CALL_P: Flags. (line 161) ! * SIG_ATOMIC_TYPE: Type Layout. (line 215) * sign_extend: Conversions. (line 23) * sign_extract: Bit-Fields. (line 8) * sign_extract, canonicalization of: Insn Canonicalizations. ! (line 88) ! * signed division: Arithmetic. (line 115) ! * signed division with signed saturation: Arithmetic. (line 115) ! * signed maximum: Arithmetic. (line 140) ! * signed minimum: Arithmetic. (line 140) ! * significandM2 instruction pattern: Standard Names. (line 784) * SImode: Machine Modes. (line 37) * simple constraints: Simple Constraints. (line 6) * simple_return: Side Effects. (line 86) ! * simple_return instruction pattern: Standard Names. (line 1412) ! * sincosM3 instruction pattern: Standard Names. (line 680) ! * sinM2 instruction pattern: Standard Names. (line 674) ! * SIZE_ASM_OP: Label Output. (line 35) ! * SIZE_TYPE: Type Layout. (line 138) ! * SIZETYPE: Type Layout. (line 154) ! * skip: GTY Options. (line 77) ! * SLOW_BYTE_ACCESS: Costs. (line 118) ! * SLOW_UNALIGNED_ACCESS: Costs. (line 133) ! * smax: Arithmetic. (line 140) ! * smin: Arithmetic. (line 140) ! * sms, swing, software pipelining: RTL passes. (line 124) ! * smulM3_highpart instruction pattern: Standard Names. (line 510) * soft float library: Soft float library routines. (line 6) ! * special: GTY Options. (line 229) * special predicates: Predicates. (line 31) * SPECS: Target Fragment. (line 191) * speed of instructions: Costs. (line 6) * split_block: Maintaining the CFG. ! (line 99) ! * splitting instructions: Insn Splitting. (line 6) * SQmode: Machine Modes. (line 114) * sqrt: Arithmetic. (line 206) ! * sqrtM2 instruction pattern: Standard Names. (line 619) * square root: Arithmetic. (line 206) ! * ss_abs: Arithmetic. (line 199) ! * ss_ashift: Arithmetic. (line 172) ! * ss_div: Arithmetic. (line 115) ! * ss_minus: Arithmetic. (line 36) ! * ss_mult: Arithmetic. (line 92) ! * ss_neg: Arithmetic. (line 81) * ss_plus: Arithmetic. (line 14) * ss_truncate: Conversions. (line 43) + * SSA: SSA. (line 6) + * SSA_NAME_DEF_STMT: SSA. (line 185) + * SSA_NAME_VERSION: SSA. (line 190) + * ssaddM3 instruction pattern: Standard Names. (line 305) + * ssadM instruction pattern: Standard Names. (line 408) + * ssashlM3 instruction pattern: Standard Names. (line 585) + * ssdivM3 instruction pattern: Standard Names. (line 305) + * ssmaddMN4 instruction pattern: Standard Names. (line 533) + * ssmsubMN4 instruction pattern: Standard Names. (line 557) + * ssmulM3 instruction pattern: Standard Names. (line 305) + * ssnegM2 instruction pattern: Standard Names. (line 609) + * sssubM3 instruction pattern: Standard Names. (line 305) * stack arguments: Stack Arguments. (line 6) * stack frame layout: Frame Layout. (line 6) * stack smashing protection: Stack Smashing Protection. (line 6) ! * STACK_ALIGNMENT_NEEDED: Frame Layout. (line 44) ! * STACK_BOUNDARY: Storage Layout. (line 141) ! * STACK_CHECK_BUILTIN: Stack Checking. (line 32) ! * STACK_CHECK_FIXED_FRAME_SIZE: Stack Checking. (line 84) ! * STACK_CHECK_MAX_FRAME_SIZE: Stack Checking. (line 75) ! * STACK_CHECK_MAX_VAR_SIZE: Stack Checking. (line 91) ! * STACK_CHECK_MOVING_SP: Stack Checking. (line 54) ! * STACK_CHECK_PROBE_INTERVAL_EXP: Stack Checking. (line 46) ! * STACK_CHECK_PROTECT: Stack Checking. (line 63) ! * STACK_CHECK_STATIC_BUILTIN: Stack Checking. (line 39) ! * STACK_DYNAMIC_OFFSET: Frame Layout. (line 71) * STACK_DYNAMIC_OFFSET and virtual registers: Regs and Memory. (line 83) ! * STACK_GROWS_DOWNWARD: Frame Layout. (line 9) ! * STACK_PARMS_IN_REG_PARM_AREA: Stack Arguments. (line 90) ! * STACK_POINTER_OFFSET: Frame Layout. (line 54) * STACK_POINTER_OFFSET and virtual registers: Regs and Memory. (line 93) ! * STACK_POINTER_REGNUM: Frame Registers. (line 9) * STACK_POINTER_REGNUM and virtual registers: Regs and Memory. (line 83) * stack_pointer_rtx: Frame Registers. (line 104) ! * stack_protect_set instruction pattern: Standard Names. (line 2094) ! * stack_protect_test instruction pattern: Standard Names. (line 2104) ! * STACK_PUSH_CODE: Frame Layout. (line 13) ! * STACK_REG_COVER_CLASS: Stack Registers. (line 23) ! * STACK_REGS: Stack Registers. (line 20) ! * STACK_SAVEAREA_MODE: Storage Layout. (line 448) ! * STACK_SIZE_MODE: Storage Layout. (line 459) ! * STACK_SLOT_ALIGNMENT: Storage Layout. (line 279) * standard pattern names: Standard Names. (line 6) ! * STANDARD_STARTFILE_PREFIX: Driver. (line 279) ! * STANDARD_STARTFILE_PREFIX_1: Driver. (line 286) ! * STANDARD_STARTFILE_PREFIX_2: Driver. (line 293) ! * STARTFILE_SPEC: Driver. (line 148) ! * STARTING_FRAME_OFFSET: Frame Layout. (line 35) * STARTING_FRAME_OFFSET and virtual registers: Regs and Memory. (line 74) * Statement and operand traversals: Statement and operand traversals. (line 6) * Statement Sequences: Statement Sequences. (line 6) ! * statements <1>: Statements for C++. (line 6) * statements: Function Properties. (line 6) ! * Statements: Statements. (line 6) * Static profile estimation: Profile information. (line 24) * static single assignment: SSA. (line 6) ! * STATIC_CHAIN_INCOMING_REGNUM: Frame Registers. (line 78) ! * STATIC_CHAIN_REGNUM: Frame Registers. (line 77) * stdarg.h and register arguments: Register Arguments. (line 51) ! * STDC_0_IN_SYSTEM_HEADERS: Misc. (line 351) * STMT_EXPR: Unary and Binary Expressions. (line 6) * STMT_IS_FULL_EXPR_P: Statements for C++. (line 22) * storage layout: Storage Layout. (line 6) ! * STORE_FLAG_VALUE: Misc. (line 202) ! * store_multiple instruction pattern: Standard Names. (line 160) ! * strcpy: Storage Layout. (line 231) ! * STRICT_ALIGNMENT: Storage Layout. (line 329) * strict_low_part: RTL Declarations. (line 9) ! * strict_memory_address_p: Addressing Modes. (line 187) * STRING_CST: Constant expressions. (line 6) * STRING_POOL_ADDRESS_P: Flags. (line 165) ! * strlenM instruction pattern: Standard Names. (line 1082) * structure value address: Aggregate Return. (line 6) + * STRUCTURE_SIZE_BOUNDARY: Storage Layout. (line 321) * structures, returning: Interface. (line 10) ! * subM3 instruction pattern: Standard Names. (line 305) * SUBOBJECT: Statements for C++. (line 6) * SUBOBJECT_CLEANUP: Statements for C++. (line 6) * subreg: Regs and Memory. (line 97) *************** Concept Index *** 50201,50830 **** * subreg and /u: Flags. (line 180) * subreg and /u and /v: Flags. (line 170) * subreg, in strict_low_part: RTL Declarations. (line 9) ! * SUBREG_BYTE: Regs and Memory. (line 285) * SUBREG_PROMOTED_UNSIGNED_P: Flags. (line 170) * SUBREG_PROMOTED_UNSIGNED_SET: Flags. (line 180) * SUBREG_PROMOTED_VAR_P: Flags. (line 187) ! * SUBREG_REG: Regs and Memory. (line 285) * subst iterators in .md files: Subst Iterators. (line 6) ! * subvM4 instruction pattern: Standard Names. (line 317) * SUCCESS_EXIT_CODE: Host Misc. (line 12) * SUPPORTS_INIT_PRIORITY: Macros for Initialization. ! (line 57) ! * SUPPORTS_ONE_ONLY: Label Output. (line 290) ! * SUPPORTS_WEAK: Label Output. (line 264) ! * SWITCHABLE_TARGET: Run-time Target. (line 164) * SWITCH_BODY: Statements for C++. (line 6) * SWITCH_COND: Statements for C++. (line 6) * SWITCH_STMT: Statements for C++. (line 6) ! * symbolic label: Sharing. (line 20) ! * SYMBOL_FLAG_ANCHOR: Special Accessors. (line 117) ! * SYMBOL_FLAG_EXTERNAL: Special Accessors. (line 99) ! * SYMBOL_FLAG_FUNCTION: Special Accessors. (line 92) ! * SYMBOL_FLAG_HAS_BLOCK_INFO: Special Accessors. (line 113) ! * SYMBOL_FLAG_LOCAL: Special Accessors. (line 95) ! * SYMBOL_FLAG_SMALL: Special Accessors. (line 104) ! * SYMBOL_FLAG_TLS_SHIFT: Special Accessors. (line 108) * symbol_ref: Constants. (line 117) * symbol_ref and /f: Flags. (line 165) * symbol_ref and /i: Flags. (line 202) * symbol_ref and /u: Flags. (line 10) * symbol_ref and /v: Flags. (line 206) * symbol_ref, RTL sharing: Sharing. (line 20) ! * SYMBOL_REF_ANCHOR_P: Special Accessors. (line 117) ! * SYMBOL_REF_BLOCK: Special Accessors. (line 130) ! * SYMBOL_REF_BLOCK_OFFSET: Special Accessors. (line 135) ! * SYMBOL_REF_CONSTANT: Special Accessors. (line 78) ! * SYMBOL_REF_DATA: Special Accessors. (line 82) ! * SYMBOL_REF_DECL: Special Accessors. (line 67) ! * SYMBOL_REF_EXTERNAL_P: Special Accessors. (line 99) * SYMBOL_REF_FLAG: Flags. (line 206) * SYMBOL_REF_FLAG, in TARGET_ENCODE_SECTION_INFO: Sections. (line 277) ! * SYMBOL_REF_FLAGS: Special Accessors. (line 86) ! * SYMBOL_REF_FUNCTION_P: Special Accessors. (line 92) ! * SYMBOL_REF_HAS_BLOCK_INFO_P: Special Accessors. (line 113) ! * SYMBOL_REF_LOCAL_P: Special Accessors. (line 95) ! * SYMBOL_REF_SMALL_P: Special Accessors. (line 104) ! * SYMBOL_REF_TLS_MODEL: Special Accessors. (line 108) * SYMBOL_REF_USED: Flags. (line 197) * SYMBOL_REF_WEAK: Flags. (line 202) ! * sync_addMODE instruction pattern: Standard Names. (line 1848) ! * sync_andMODE instruction pattern: Standard Names. (line 1848) * sync_compare_and_swapMODE instruction pattern: Standard Names. ! (line 1808) ! * sync_iorMODE instruction pattern: Standard Names. (line 1848) ! * sync_lock_releaseMODE instruction pattern: Standard Names. (line 1913) * sync_lock_test_and_setMODE instruction pattern: Standard Names. ! (line 1887) ! * sync_nandMODE instruction pattern: Standard Names. (line 1848) ! * sync_new_addMODE instruction pattern: Standard Names. (line 1880) ! * sync_new_andMODE instruction pattern: Standard Names. (line 1880) ! * sync_new_iorMODE instruction pattern: Standard Names. (line 1880) ! * sync_new_nandMODE instruction pattern: Standard Names. (line 1880) ! * sync_new_subMODE instruction pattern: Standard Names. (line 1880) ! * sync_new_xorMODE instruction pattern: Standard Names. (line 1880) ! * sync_old_addMODE instruction pattern: Standard Names. (line 1863) ! * sync_old_andMODE instruction pattern: Standard Names. (line 1863) ! * sync_old_iorMODE instruction pattern: Standard Names. (line 1863) ! * sync_old_nandMODE instruction pattern: Standard Names. (line 1863) ! * sync_old_subMODE instruction pattern: Standard Names. (line 1863) ! * sync_old_xorMODE instruction pattern: Standard Names. (line 1863) ! * sync_subMODE instruction pattern: Standard Names. (line 1848) ! * sync_xorMODE instruction pattern: Standard Names. (line 1848) ! * SYSROOT_HEADERS_SUFFIX_SPEC: Driver. (line 176) ! * SYSROOT_SUFFIX_SPEC: Driver. (line 171) * t-TARGET: Target Fragment. (line 6) * table jump: Basic Blocks. (line 67) ! * tablejump instruction pattern: Standard Names. (line 1478) * tag: GTY Options. (line 88) * tagging insns: Tagging Insns. (line 6) * tail calls: Tail Calls. (line 6) ! * TAmode: Machine Modes. (line 158) ! * tanM2 instruction pattern: Standard Names. (line 685) * target attributes: Target Attributes. (line 6) * target description macros: Target Macros. (line 6) * target functions: Target Structure. (line 6) * target hooks: Target Structure. (line 6) * target makefile fragment: Target Fragment. (line 6) * target specifications: Run-time Target. (line 6) ! * targetm: Target Structure. (line 6) ! * targets, makefile: Makefile. (line 6) ! * TARGET_ABSOLUTE_BIGGEST_ALIGNMENT: Storage Layout. (line 168) ! * TARGET_ADDRESS_COST: Costs. (line 323) * TARGET_ADDR_SPACE_ADDRESS_MODE: Named Address Spaces. ! (line 42) * TARGET_ADDR_SPACE_CONVERT: Named Address Spaces. ! (line 89) * TARGET_ADDR_SPACE_DEBUG: Named Address Spaces. ! (line 99) * TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P: Named Address Spaces. ! (line 59) * TARGET_ADDR_SPACE_LEGITIMIZE_ADDRESS: Named Address Spaces. ! (line 67) * TARGET_ADDR_SPACE_POINTER_MODE: Named Address Spaces. ! (line 36) * TARGET_ADDR_SPACE_SUBSET_P: Named Address Spaces. ! (line 74) * TARGET_ADDR_SPACE_VALID_POINTER_MODE: Named Address Spaces. ! (line 48) * TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID: Named Address Spaces. ! (line 83) ! * TARGET_ALIGN_ANON_BITFIELD: Storage Layout. (line 402) ! * TARGET_ALLOCATE_INITIAL_VALUE: Misc. (line 810) ! * TARGET_ALLOCATE_STACK_SLOTS_FOR_ARGS: Misc. (line 1107) ! * TARGET_ALWAYS_STRIP_DOTDOT: Driver. (line 250) ! * TARGET_ARG_PARTIAL_BYTES: Register Arguments. (line 95) * TARGET_ARM_EABI_UNWINDER: Exception Region Output. ! (line 134) ! * TARGET_ARRAY_MODE_SUPPORTED_P: Register Arguments. (line 345) ! * TARGET_ASAN_SHADOW_OFFSET: Misc. (line 1135) ! * TARGET_ASM_ALIGNED_DI_OP: Data Output. (line 9) ! * TARGET_ASM_ALIGNED_HI_OP: Data Output. (line 7) ! * TARGET_ASM_ALIGNED_SI_OP: Data Output. (line 8) ! * TARGET_ASM_ALIGNED_TI_OP: Data Output. (line 10) ! * TARGET_ASM_ASSEMBLE_UNDEFINED_DECL: Label Output. (line 231) ! * TARGET_ASM_ASSEMBLE_VISIBILITY: Label Output. (line 301) ! * TARGET_ASM_BYTE_OP: Data Output. (line 6) ! * TARGET_ASM_CAN_OUTPUT_MI_THUNK: Function Entry. (line 202) ! * TARGET_ASM_CLOSE_PAREN: Data Output. (line 133) ! * TARGET_ASM_CODE_END: File Framework. (line 57) * TARGET_ASM_CONSTRUCTOR: Macros for Initialization. ! (line 68) ! * TARGET_ASM_DECLARE_CONSTANT_NAME: Label Output. (line 177) ! * TARGET_ASM_DECL_END: Data Output. (line 38) * TARGET_ASM_DESTRUCTOR: Macros for Initialization. ! (line 82) ! * TARGET_ASM_EMIT_EXCEPT_PERSONALITY: Dispatch Tables. (line 80) ! * TARGET_ASM_EMIT_EXCEPT_TABLE_LABEL: Dispatch Tables. (line 73) ! * TARGET_ASM_EMIT_UNWIND_LABEL: Dispatch Tables. (line 61) ! * TARGET_ASM_EXTERNAL_LIBCALL: Label Output. (line 337) ! * TARGET_ASM_FILE_END: File Framework. (line 35) ! * TARGET_ASM_FILE_START: File Framework. (line 8) ! * TARGET_ASM_FILE_START_APP_OFF: File Framework. (line 16) ! * TARGET_ASM_FILE_START_FILE_DIRECTIVE: File Framework. (line 29) ! * TARGET_ASM_FINAL_POSTSCAN_INSN: Instruction Output. (line 82) ! * TARGET_ASM_FUNCTION_BEGIN_EPILOGUE: Function Entry. (line 59) ! * TARGET_ASM_FUNCTION_END_PROLOGUE: Function Entry. (line 53) ! * TARGET_ASM_FUNCTION_EPILOGUE: Function Entry. (line 65) ! * TARGET_ASM_FUNCTION_PROLOGUE: Function Entry. (line 9) ! * TARGET_ASM_FUNCTION_RODATA_SECTION: Sections. (line 213) ! * TARGET_ASM_FUNCTION_SECTION: File Framework. (line 121) * TARGET_ASM_FUNCTION_SWITCHED_TEXT_SECTIONS: File Framework. ! (line 131) ! * TARGET_ASM_GLOBALIZE_DECL_NAME: Label Output. (line 222) ! * TARGET_ASM_GLOBALIZE_LABEL: Label Output. (line 213) ! * TARGET_ASM_INIT_SECTIONS: Sections. (line 159) ! * TARGET_ASM_INTEGER: Data Output. (line 25) ! * TARGET_ASM_INTERNAL_LABEL: Label Output. (line 380) ! * TARGET_ASM_JUMP_ALIGN_MAX_SKIP: Alignment Output. (line 21) * TARGET_ASM_LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP: Alignment Output. ! (line 34) ! * TARGET_ASM_LABEL_ALIGN_MAX_SKIP: Alignment Output. (line 68) ! * TARGET_ASM_LOOP_ALIGN_MAX_SKIP: Alignment Output. (line 53) ! * TARGET_ASM_LTO_END: File Framework. (line 52) ! * TARGET_ASM_LTO_START: File Framework. (line 47) ! * TARGET_ASM_MARK_DECL_PRESERVED: Label Output. (line 343) ! * TARGET_ASM_MERGEABLE_RODATA_PREFIX: Sections. (line 221) ! * TARGET_ASM_NAMED_SECTION: File Framework. (line 113) ! * TARGET_ASM_OPEN_PAREN: Data Output. (line 132) ! * TARGET_ASM_OUTPUT_ADDR_CONST_EXTRA: Data Output. (line 42) ! * TARGET_ASM_OUTPUT_ANCHOR: Anchored Addresses. (line 42) ! * TARGET_ASM_OUTPUT_DWARF_DTPREL: SDB and DWARF. (line 108) ! * TARGET_ASM_OUTPUT_IDENT: File Framework. (line 100) ! * TARGET_ASM_OUTPUT_MI_THUNK: Function Entry. (line 160) ! * TARGET_ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 91) ! * TARGET_ASM_RECORD_GCC_SWITCHES: File Framework. (line 162) ! * TARGET_ASM_RECORD_GCC_SWITCHES_SECTION: File Framework. (line 207) ! * TARGET_ASM_RELOC_RW_MASK: Sections. (line 168) ! * TARGET_ASM_SELECT_RTX_SECTION: Sections. (line 230) ! * TARGET_ASM_SELECT_SECTION: Sections. (line 179) ! * TARGET_ASM_TM_CLONE_TABLE_SECTION: Sections. (line 226) ! * TARGET_ASM_TRAMPOLINE_TEMPLATE: Trampolines. (line 28) * TARGET_ASM_TTYPE: Exception Region Output. ! (line 128) ! * TARGET_ASM_UNALIGNED_DI_OP: Data Output. (line 13) ! * TARGET_ASM_UNALIGNED_HI_OP: Data Output. (line 11) ! * TARGET_ASM_UNALIGNED_SI_OP: Data Output. (line 12) ! * TARGET_ASM_UNALIGNED_TI_OP: Data Output. (line 14) ! * TARGET_ASM_UNIQUE_SECTION: Sections. (line 201) ! * TARGET_ASM_UNWIND_EMIT: Dispatch Tables. (line 87) ! * TARGET_ASM_UNWIND_EMIT_BEFORE_INSN: Dispatch Tables. (line 93) ! * TARGET_ATOMIC_ALIGN_FOR_MODE: Misc. (line 1154) ! * TARGET_ATOMIC_ASSIGN_EXPAND_FENV: Misc. (line 1160) ! * TARGET_ATOMIC_TEST_AND_SET_TRUEVAL: Misc. (line 1145) ! * TARGET_ATTRIBUTE_TABLE: Target Attributes. (line 10) ! * TARGET_ATTRIBUTE_TAKES_IDENTIFIER_P: Target Attributes. (line 17) ! * TARGET_BINDS_LOCAL_P: Sections. (line 308) ! * TARGET_BRANCH_TARGET_REGISTER_CALLEE_SAVED: Misc. (line 907) ! * TARGET_BRANCH_TARGET_REGISTER_CLASS: Misc. (line 900) ! * TARGET_BUILD_BUILTIN_VA_LIST: Register Arguments. (line 285) * TARGET_BUILTIN_CHKP_FUNCTION: Misc. (line 625) ! * TARGET_BUILTIN_DECL: Misc. (line 604) ! * TARGET_BUILTIN_RECIPROCAL: Addressing Modes. (line 261) ! * TARGET_BUILTIN_SETJMP_FRAME_VALUE: Frame Layout. (line 103) ! * TARGET_CALLEE_COPIES: Register Arguments. (line 127) ! * TARGET_CALL_ARGS: Varargs. (line 123) * TARGET_CALL_FUSAGE_CONTAINS_NON_CALLEE_CLOBBERS: Miscellaneous Register Hooks. ! (line 6) ! * TARGET_CANNOT_FORCE_CONST_MEM: Addressing Modes. (line 234) ! * TARGET_CANNOT_MODIFY_JUMPS_P: Misc. (line 887) ! * TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P: Register Classes. (line 597) * TARGET_CANONICALIZE_COMPARISON: MODE_CC Condition Codes. ! (line 55) ! * TARGET_CANONICAL_VA_LIST_TYPE: Register Arguments. (line 306) ! * TARGET_CAN_ELIMINATE: Elimination. (line 73) ! * TARGET_CAN_FOLLOW_JUMP: Misc. (line 796) ! * TARGET_CAN_INLINE_P: Target Attributes. (line 165) ! * TARGET_CAN_USE_DOLOOP_P: Misc. (line 760) ! * TARGET_CASE_VALUES_THRESHOLD: Misc. (line 46) * TARGET_CC_MODES_COMPATIBLE: MODE_CC Condition Codes. ! (line 120) ! * TARGET_CHECK_PCH_TARGET_FLAGS: PCH Target. (line 26) ! * TARGET_CHECK_STRING_OBJECT_FORMAT_ARG: Run-time Target. (line 119) ! * TARGET_CHKP_BOUND_MODE: Misc. (line 697) ! * TARGET_CHKP_BOUND_TYPE: Misc. (line 695) ! * TARGET_CHKP_FUNCTION_VALUE_BOUNDS: Varargs. (line 182) ! * TARGET_CHKP_INITIALIZE_BOUNDS: Misc. (line 703) ! * TARGET_CHKP_MAKE_BOUNDS_CONSTANT: Misc. (line 699) ! * TARGET_CLASS_LIKELY_SPILLED_P: Register Classes. (line 489) ! * TARGET_CLASS_MAX_NREGS: Register Classes. (line 505) ! * TARGET_COMMUTATIVE_P: Misc. (line 803) ! * TARGET_COMPARE_VERSION_PRIORITY: Misc. (line 737) ! * TARGET_COMP_TYPE_ATTRIBUTES: Target Attributes. (line 25) ! * TARGET_CONDITIONAL_REGISTER_USAGE: Register Basics. (line 59) ! * TARGET_CONST_ANCHOR: Misc. (line 1118) ! * TARGET_CONST_NOT_OK_FOR_DEBUG_P: Addressing Modes. (line 230) ! * TARGET_CONVERT_TO_TYPE: Misc. (line 1072) ! * TARGET_CPU_CPP_BUILTINS: Run-time Target. (line 8) ! * TARGET_CSTORE_MODE: Register Classes. (line 620) ! * TARGET_CXX_ADJUST_CLASS_AT_DEFINITION: C++ ABI. (line 86) ! * TARGET_CXX_CDTOR_RETURNS_THIS: C++ ABI. (line 37) ! * TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT: C++ ABI. (line 61) ! * TARGET_CXX_COOKIE_HAS_SIZE: C++ ABI. (line 24) ! * TARGET_CXX_DECL_MANGLING_CONTEXT: C++ ABI. (line 92) ! * TARGET_CXX_DETERMINE_CLASS_DATA_VISIBILITY: C++ ABI. (line 52) ! * TARGET_CXX_GET_COOKIE_SIZE: C++ ABI. (line 17) ! * TARGET_CXX_GUARD_MASK_BIT: C++ ABI. (line 11) ! * TARGET_CXX_GUARD_TYPE: C++ ABI. (line 6) ! * TARGET_CXX_IMPLICIT_EXTERN_C: Misc. (line 373) ! * TARGET_CXX_IMPORT_EXPORT_CLASS: C++ ABI. (line 28) ! * TARGET_CXX_KEY_METHOD_MAY_BE_INLINE: C++ ABI. (line 42) ! * TARGET_CXX_LIBRARY_RTTI_COMDAT: C++ ABI. (line 68) ! * TARGET_CXX_USE_AEABI_ATEXIT: C++ ABI. (line 73) ! * TARGET_CXX_USE_ATEXIT_FOR_CXA_ATEXIT: C++ ABI. (line 79) ! * TARGET_C_PREINCLUDE: Misc. (line 361) ! * TARGET_DEBUG_UNWIND_INFO: SDB and DWARF. (line 36) ! * TARGET_DECIMAL_FLOAT_SUPPORTED_P: Storage Layout. (line 507) ! * TARGET_DECLSPEC: Target Attributes. (line 72) ! * TARGET_DEFAULT_PACK_STRUCT: Misc. (line 446) ! * TARGET_DEFAULT_SHORT_ENUMS: Type Layout. (line 129) ! * TARGET_DEFAULT_TARGET_FLAGS: Run-time Target. (line 55) ! * TARGET_DEFERRED_OUTPUT_DEFS: Label Output. (line 465) ! * TARGET_DELAY_SCHED2: SDB and DWARF. (line 65) ! * TARGET_DELAY_VARTRACK: SDB and DWARF. (line 69) ! * TARGET_DELEGITIMIZE_ADDRESS: Addressing Modes. (line 221) ! * TARGET_DIFFERENT_ADDR_DISPLACEMENT_P: Register Classes. (line 590) * TARGET_DLLIMPORT_DECL_ATTRIBUTES: Target Attributes. (line 55) ! * TARGET_DWARF_CALLING_CONVENTION: SDB and DWARF. (line 16) * TARGET_DWARF_FRAME_REG_MODE: Exception Region Output. ! (line 114) ! * TARGET_DWARF_HANDLE_FRAME_UNSPEC: Frame Layout. (line 167) * TARGET_DWARF_REGISTER_SPAN: Exception Region Output. ! (line 105) ! * TARGET_EDOM: Library Calls. (line 59) ! * TARGET_EMUTLS_DEBUG_FORM_TLS_ADDRESS: Emulated TLS. (line 67) ! * TARGET_EMUTLS_GET_ADDRESS: Emulated TLS. (line 18) ! * TARGET_EMUTLS_REGISTER_COMMON: Emulated TLS. (line 23) ! * TARGET_EMUTLS_TMPL_PREFIX: Emulated TLS. (line 44) ! * TARGET_EMUTLS_TMPL_SECTION: Emulated TLS. (line 35) ! * TARGET_EMUTLS_VAR_ALIGN_FIXED: Emulated TLS. (line 62) ! * TARGET_EMUTLS_VAR_FIELDS: Emulated TLS. (line 48) ! * TARGET_EMUTLS_VAR_INIT: Emulated TLS. (line 55) ! * TARGET_EMUTLS_VAR_PREFIX: Emulated TLS. (line 40) ! * TARGET_EMUTLS_VAR_SECTION: Emulated TLS. (line 30) ! * TARGET_ENCODE_SECTION_INFO: Sections. (line 251) * TARGET_ENCODE_SECTION_INFO and address validation: Addressing Modes. ! (line 82) ! * TARGET_ENCODE_SECTION_INFO usage: Instruction Output. (line 127) ! * TARGET_END_CALL_ARGS: Varargs. (line 137) ! * TARGET_ENUM_VA_LIST_P: Register Arguments. (line 289) * TARGET_EXCEPT_UNWIND_INFO: Exception Region Output. ! (line 46) ! * TARGET_EXECUTABLE_SUFFIX: Misc. (line 861) ! * TARGET_EXPAND_BUILTIN: Misc. (line 614) ! * TARGET_EXPAND_BUILTIN_SAVEREGS: Varargs. (line 64) ! * TARGET_EXPAND_TO_RTL_HOOK: Storage Layout. (line 513) * TARGET_EXPR: Unary and Binary Expressions. (line 6) ! * TARGET_EXTRA_INCLUDES: Misc. (line 973) ! * TARGET_EXTRA_LIVE_ON_ENTRY: Tail Calls. (line 20) ! * TARGET_EXTRA_PRE_INCLUDES: Misc. (line 980) * TARGET_FIXED_CONDITION_CODE_REGS: MODE_CC Condition Codes. ! (line 105) ! * TARGET_FIXED_POINT_SUPPORTED_P: Storage Layout. (line 510) ! * target_flags: Run-time Target. (line 51) * TARGET_FLAGS_REGNUM: MODE_CC Condition Codes. ! (line 133) * TARGET_FLOAT_EXCEPTIONS_ROUNDING_SUPPORTED_P: Run-time Target. ! (line 183) ! * TARGET_FLT_EVAL_METHOD: Type Layout. (line 110) ! * TARGET_FN_ABI_VA_LIST: Register Arguments. (line 301) ! * TARGET_FOLD_BUILTIN: Misc. (line 720) ! * TARGET_FORCE_AT_COMP_DIR: SDB and DWARF. (line 60) ! * TARGET_FORMAT_TYPES: Misc. (line 1001) ! * TARGET_FRAME_POINTER_REQUIRED: Elimination. (line 8) ! * TARGET_FUNCTION_ARG: Register Arguments. (line 10) ! * TARGET_FUNCTION_ARG_ADVANCE: Register Arguments. (line 198) ! * TARGET_FUNCTION_ARG_BOUNDARY: Register Arguments. (line 252) ! * TARGET_FUNCTION_ARG_ROUND_BOUNDARY: Register Arguments. (line 258) ! * TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P: Target Attributes. (line 93) ! * TARGET_FUNCTION_INCOMING_ARG: Register Arguments. (line 71) ! * TARGET_FUNCTION_OK_FOR_SIBCALL: Tail Calls. (line 6) ! * TARGET_FUNCTION_VALUE: Scalar Return. (line 9) ! * TARGET_FUNCTION_VALUE_REGNO_P: Scalar Return. (line 96) ! * TARGET_GENERATE_VERSION_DISPATCHER_BODY: Misc. (line 753) ! * TARGET_GEN_CCMP_FIRST: Misc. (line 927) ! * TARGET_GEN_CCMP_NEXT: Misc. (line 938) ! * TARGET_GET_DRAP_RTX: Misc. (line 1101) ! * TARGET_GET_FUNCTION_VERSIONS_DISPATCHER: Misc. (line 746) ! * TARGET_GET_PCH_VALIDITY: PCH Target. (line 6) ! * TARGET_GET_RAW_ARG_MODE: Aggregate Return. (line 81) ! * TARGET_GET_RAW_RESULT_MODE: Aggregate Return. (line 76) ! * TARGET_GIMPLE_FOLD_BUILTIN: Misc. (line 730) ! * TARGET_GIMPLIFY_VA_ARG_EXPR: Register Arguments. (line 311) ! * TARGET_GOACC_DIM_LIMIT: Addressing Modes. (line 442) ! * TARGET_GOACC_FORK_JOIN: Addressing Modes. (line 446) ! * TARGET_GOACC_REDUCTION: Addressing Modes. (line 457) ! * TARGET_GOACC_VALIDATE_DIMS: Addressing Modes. (line 429) ! * TARGET_HANDLE_C_OPTION: Run-time Target. (line 73) ! * TARGET_HANDLE_OPTION: Run-time Target. (line 59) * TARGET_HARD_REGNO_SCRATCH_OK: Values in Registers. ! (line 141) ! * TARGET_HAS_IFUNC_P: Misc. (line 1149) ! * TARGET_HAS_NO_HW_DIVIDE: Library Calls. (line 52) ! * TARGET_HAVE_CONDITIONAL_EXECUTION: Misc. (line 921) * TARGET_HAVE_CTORS_DTORS: Macros for Initialization. ! (line 63) ! * TARGET_HAVE_NAMED_SECTIONS: File Framework. (line 139) ! * TARGET_HAVE_SRODATA_SECTION: Sections. (line 297) ! * TARGET_HAVE_SWITCHABLE_BSS_SECTIONS: File Framework. (line 144) ! * TARGET_HAVE_TLS: Sections. (line 317) ! * TARGET_INIT_BUILTINS: Misc. (line 588) * TARGET_INIT_DWARF_REG_SIZES_EXTRA: Exception Region Output. ! (line 120) ! * TARGET_INIT_LIBFUNCS: Library Calls. (line 15) ! * TARGET_INIT_PIC_REG: Register Arguments. (line 91) ! * TARGET_INSERT_ATTRIBUTES: Target Attributes. (line 80) ! * TARGET_INSTANTIATE_DECLS: Storage Layout. (line 521) ! * TARGET_INVALID_ARG_FOR_UNPROTOTYPED_FN: Misc. (line 1025) ! * TARGET_INVALID_BINARY_OP: Misc. (line 1044) ! * TARGET_INVALID_CONVERSION: Misc. (line 1031) ! * TARGET_INVALID_PARAMETER_TYPE: Misc. (line 1050) ! * TARGET_INVALID_RETURN_TYPE: Misc. (line 1057) ! * TARGET_INVALID_UNARY_OP: Misc. (line 1037) ! * TARGET_INVALID_WITHIN_DOLOOP: Misc. (line 777) ! * TARGET_IN_SMALL_DATA_P: Sections. (line 293) ! * TARGET_IRA_CHANGE_PSEUDO_ALLOCNO_CLASS: Register Classes. (line 557) ! * TARGET_KEEP_LEAF_WHEN_PROFILED: Profiling. (line 39) ! * TARGET_LEGITIMATE_ADDRESS_P: Addressing Modes. (line 48) ! * TARGET_LEGITIMATE_COMBINED_INSN: Misc. (line 791) ! * TARGET_LEGITIMATE_CONSTANT_P: Addressing Modes. (line 213) ! * TARGET_LEGITIMIZE_ADDRESS: Addressing Modes. (line 129) ! * TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT: Register Classes. (line 605) ! * TARGET_LIBCALL_VALUE: Scalar Return. (line 65) ! * TARGET_LIBC_HAS_FUNCTION: Library Calls. (line 77) ! * TARGET_LIBFUNC_GNU_PREFIX: Library Calls. (line 24) ! * TARGET_LIBGCC_CMP_RETURN_MODE: Storage Layout. (line 463) * TARGET_LIBGCC_FLOATING_MODE_SUPPORTED_P: Register Arguments. ! (line 369) ! * TARGET_LIBGCC_SDATA_SECTION: Sections. (line 131) ! * TARGET_LIBGCC_SHIFT_COUNT_MODE: Storage Layout. (line 469) ! * TARGET_LIB_INT_CMP_BIASED: Library Calls. (line 42) ! * TARGET_LOAD_BOUNDS_FOR_ARG: Varargs. (line 153) ! * TARGET_LOAD_RETURNED_BOUNDS: Varargs. (line 172) ! * TARGET_LOOP_UNROLL_ADJUST: Misc. (line 954) ! * TARGET_LRA_P: Register Classes. (line 564) ! * TARGET_MACHINE_DEPENDENT_REORG: Misc. (line 573) ! * TARGET_MANGLE_ASSEMBLER_NAME: Label Output. (line 356) ! * TARGET_MANGLE_DECL_ASSEMBLER_NAME: Sections. (line 241) ! * TARGET_MANGLE_TYPE: Storage Layout. (line 525) ! * TARGET_MAX_ANCHOR_OFFSET: Anchored Addresses. (line 38) ! * TARGET_MD_ASM_ADJUST: Misc. (line 491) ! * TARGET_MEMBER_TYPE_FORCES_BLK: Storage Layout. (line 415) ! * TARGET_MEMMODEL_CHECK: Misc. (line 1140) ! * TARGET_MEMORY_MOVE_COST: Costs. (line 79) ! * TARGET_MEM_CONSTRAINT: Addressing Modes. (line 107) * TARGET_MEM_REF: Storage References. (line 6) ! * TARGET_MERGE_DECL_ATTRIBUTES: Target Attributes. (line 45) ! * TARGET_MERGE_TYPE_ATTRIBUTES: Target Attributes. (line 37) ! * TARGET_MIN_ANCHOR_OFFSET: Anchored Addresses. (line 32) ! * TARGET_MIN_DIVISIONS_FOR_RECIP_MUL: Misc. (line 90) ! * TARGET_MODE_AFTER: Mode Switching. (line 57) ! * TARGET_MODE_DEPENDENT_ADDRESS_P: Addressing Modes. (line 196) ! * TARGET_MODE_EMIT: Mode Switching. (line 42) ! * TARGET_MODE_ENTRY: Mode Switching. (line 64) ! * TARGET_MODE_EXIT: Mode Switching. (line 71) ! * TARGET_MODE_NEEDED: Mode Switching. (line 50) ! * TARGET_MODE_PRIORITY: Mode Switching. (line 78) ! * TARGET_MODE_REP_EXTENDED: Misc. (line 175) ! * TARGET_MS_BITFIELD_LAYOUT_P: Storage Layout. (line 479) ! * TARGET_MUST_PASS_IN_STACK: Register Arguments. (line 64) * TARGET_MUST_PASS_IN_STACK, and TARGET_FUNCTION_ARG: Register Arguments. ! (line 56) ! * TARGET_NARROW_VOLATILE_BITFIELD: Storage Layout. (line 408) ! * TARGET_NO_REGISTER_ALLOCATION: SDB and DWARF. (line 73) ! * TARGET_NO_SPECULATION_IN_DELAY_SLOTS_P: Costs. (line 359) ! * TARGET_N_FORMAT_TYPES: Misc. (line 1006) ! * TARGET_OBJC_CONSTRUCT_STRING_OBJECT: Run-time Target. (line 88) ! * TARGET_OBJC_DECLARE_CLASS_DEFINITION: Run-time Target. (line 109) * TARGET_OBJC_DECLARE_UNRESOLVED_CLASS_REFERENCE: Run-time Target. ! (line 104) ! * TARGET_OBJECT_SUFFIX: Misc. (line 856) ! * TARGET_OBJFMT_CPP_BUILTINS: Run-time Target. (line 45) ! * TARGET_OFFLOAD_OPTIONS: Misc. (line 1183) * TARGET_OMIT_STRUCT_RETURN_REG: Scalar Return. (line 117) ! * TARGET_OPTAB_SUPPORTED_P: Costs. (line 278) ! * TARGET_OPTF: Misc. (line 988) ! * TARGET_OPTION_DEFAULT_PARAMS: Run-time Target. (line 160) ! * TARGET_OPTION_FUNCTION_VERSIONS: Target Attributes. (line 157) ! * TARGET_OPTION_INIT_STRUCT: Run-time Target. (line 156) ! * TARGET_OPTION_OPTIMIZATION_TABLE: Run-time Target. (line 142) ! * TARGET_OPTION_OVERRIDE: Target Attributes. (line 144) ! * TARGET_OPTION_POST_STREAM_IN: Target Attributes. (line 125) ! * TARGET_OPTION_PRAGMA_PARSE: Target Attributes. (line 137) ! * TARGET_OPTION_PRINT: Target Attributes. (line 131) ! * TARGET_OPTION_RESTORE: Target Attributes. (line 119) ! * TARGET_OPTION_SAVE: Target Attributes. (line 112) ! * TARGET_OPTION_VALID_ATTRIBUTE_P: Target Attributes. (line 100) ! * TARGET_OS_CPP_BUILTINS: Run-time Target. (line 41) ! * TARGET_OVERRIDES_FORMAT_ATTRIBUTES: Misc. (line 1010) ! * TARGET_OVERRIDES_FORMAT_ATTRIBUTES_COUNT: Misc. (line 1016) ! * TARGET_OVERRIDES_FORMAT_INIT: Misc. (line 1020) ! * TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE: Run-time Target. (line 126) ! * TARGET_PASS_BY_REFERENCE: Register Arguments. (line 115) ! * TARGET_PCH_VALID_P: PCH Target. (line 11) ! * TARGET_POSIX_IO: Misc. (line 517) ! * TARGET_PREFERRED_OUTPUT_RELOAD_CLASS: Register Classes. (line 284) ! * TARGET_PREFERRED_RELOAD_CLASS: Register Classes. (line 213) ! * TARGET_PREFERRED_RENAME_CLASS: Register Classes. (line 201) ! * TARGET_PREPARE_PCH_SAVE: PCH Target. (line 34) ! * TARGET_PRETEND_OUTGOING_VARARGS_NAMED: Varargs. (line 144) ! * TARGET_PROFILE_BEFORE_PROLOGUE: Sections. (line 301) ! * TARGET_PROMOTED_TYPE: Misc. (line 1064) ! * TARGET_PROMOTE_FUNCTION_MODE: Storage Layout. (line 109) ! * TARGET_PROMOTE_PROTOTYPES: Stack Arguments. (line 10) ! * TARGET_PTRMEMFUNC_VBIT_LOCATION: Type Layout. (line 256) ! * TARGET_RECORD_OFFLOAD_SYMBOL: Misc. (line 1178) ! * TARGET_REF_MAY_ALIAS_ERRNO: Register Arguments. (line 322) ! * TARGET_REGISTER_MOVE_COST: Costs. (line 31) ! * TARGET_REGISTER_PRIORITY: Register Classes. (line 569) ! * TARGET_REGISTER_USAGE_LEVELING_P: Register Classes. (line 580) ! * TARGET_RELAYOUT_FUNCTION: Target Attributes. (line 172) ! * TARGET_RESOLVE_OVERLOADED_BUILTIN: Misc. (line 709) ! * TARGET_RETURN_IN_MEMORY: Aggregate Return. (line 15) * TARGET_RETURN_IN_MSB: Scalar Return. (line 124) ! * TARGET_RETURN_POPS_ARGS: Stack Arguments. (line 98) ! * TARGET_RTX_COSTS: Costs. (line 292) ! * TARGET_SCALAR_MODE_SUPPORTED_P: Register Arguments. (line 329) ! * TARGET_SCHED_ADJUST_COST: Scheduling. (line 35) ! * TARGET_SCHED_ADJUST_PRIORITY: Scheduling. (line 50) ! * TARGET_SCHED_ALLOC_SCHED_CONTEXT: Scheduling. (line 294) ! * TARGET_SCHED_CLEAR_SCHED_CONTEXT: Scheduling. (line 309) ! * TARGET_SCHED_DEPENDENCIES_EVALUATION_HOOK: Scheduling. (line 101) ! * TARGET_SCHED_DFA_NEW_CYCLE: Scheduling. (line 255) ! * TARGET_SCHED_DFA_POST_ADVANCE_CYCLE: Scheduling. (line 172) ! * TARGET_SCHED_DFA_POST_CYCLE_INSN: Scheduling. (line 156) ! * TARGET_SCHED_DFA_PRE_ADVANCE_CYCLE: Scheduling. (line 165) ! * TARGET_SCHED_DFA_PRE_CYCLE_INSN: Scheduling. (line 144) ! * TARGET_SCHED_DISPATCH: Scheduling. (line 363) ! * TARGET_SCHED_DISPATCH_DO: Scheduling. (line 368) ! * TARGET_SCHED_EXPOSED_PIPELINE: Scheduling. (line 372) ! * TARGET_SCHED_FINISH: Scheduling. (line 122) ! * TARGET_SCHED_FINISH_GLOBAL: Scheduling. (line 137) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BACKTRACK: Scheduling. (line 235) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BEGIN: Scheduling. (line 223) * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD: Scheduling. ! (line 179) * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD_GUARD: Scheduling. ! (line 207) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END: Scheduling. (line 240) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_FINI: Scheduling. (line 250) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_INIT: Scheduling. (line 245) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_ISSUE: Scheduling. (line 229) ! * TARGET_SCHED_FREE_SCHED_CONTEXT: Scheduling. (line 313) ! * TARGET_SCHED_FUSION_PRIORITY: Scheduling. (line 382) ! * TARGET_SCHED_GEN_SPEC_CHECK: Scheduling. (line 335) ! * TARGET_SCHED_H_I_D_EXTENDED: Scheduling. (line 289) ! * TARGET_SCHED_INIT: Scheduling. (line 111) ! * TARGET_SCHED_INIT_DFA_POST_CYCLE_INSN: Scheduling. (line 161) ! * TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN: Scheduling. (line 153) ! * TARGET_SCHED_INIT_GLOBAL: Scheduling. (line 129) ! * TARGET_SCHED_INIT_SCHED_CONTEXT: Scheduling. (line 298) ! * TARGET_SCHED_ISSUE_RATE: Scheduling. (line 11) ! * TARGET_SCHED_IS_COSTLY_DEPENDENCE: Scheduling. (line 267) ! * TARGET_SCHED_MACRO_FUSION_P: Scheduling. (line 87) ! * TARGET_SCHED_MACRO_FUSION_PAIR_P: Scheduling. (line 91) ! * TARGET_SCHED_NEEDS_BLOCK_P: Scheduling. (line 328) ! * TARGET_SCHED_REASSOCIATION_WIDTH: Scheduling. (line 377) ! * TARGET_SCHED_REORDER: Scheduling. (line 58) ! * TARGET_SCHED_REORDER2: Scheduling. (line 75) ! * TARGET_SCHED_SET_SCHED_CONTEXT: Scheduling. (line 305) ! * TARGET_SCHED_SET_SCHED_FLAGS: Scheduling. (line 347) ! * TARGET_SCHED_SMS_RES_MII: Scheduling. (line 354) ! * TARGET_SCHED_SPECULATE_INSN: Scheduling. (line 316) ! * TARGET_SCHED_VARIABLE_ISSUE: Scheduling. (line 22) ! * TARGET_SECONDARY_RELOAD: Register Classes. (line 312) ! * TARGET_SECTION_TYPE_FLAGS: File Framework. (line 149) ! * TARGET_SETUP_INCOMING_VARARGS: Varargs. (line 71) ! * TARGET_SETUP_INCOMING_VARARG_BOUNDS: Varargs. (line 188) ! * TARGET_SET_CURRENT_FUNCTION: Misc. (line 838) ! * TARGET_SET_DEFAULT_TYPE_ATTRIBUTES: Target Attributes. (line 33) ! * TARGET_SET_UP_BY_PROLOGUE: Tail Calls. (line 29) ! * TARGET_SHIFT_TRUNCATION_MASK: Misc. (line 138) ! * TARGET_SIMD_CLONE_ADJUST: Addressing Modes. (line 419) * TARGET_SIMD_CLONE_COMPUTE_VECSIZE_AND_SIMDLEN: Addressing Modes. ! (line 411) ! * TARGET_SIMD_CLONE_USABLE: Addressing Modes. (line 423) * TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P: Register Arguments. ! (line 377) ! * TARGET_SPILL_CLASS: Register Classes. (line 613) ! * TARGET_SPLIT_COMPLEX_ARG: Register Arguments. (line 273) * TARGET_STACK_PROTECT_FAIL: Stack Smashing Protection. ! (line 16) * TARGET_STACK_PROTECT_GUARD: Stack Smashing Protection. ! (line 6) ! * TARGET_STATIC_CHAIN: Frame Registers. (line 90) ! * TARGET_STORE_BOUNDS_FOR_ARG: Varargs. (line 163) ! * TARGET_STORE_RETURNED_BOUNDS: Varargs. (line 177) ! * TARGET_STRICT_ARGUMENT_NAMING: Varargs. (line 107) ! * TARGET_STRING_OBJECT_REF_TYPE_P: Run-time Target. (line 114) ! * TARGET_STRIP_NAME_ENCODING: Sections. (line 288) ! * TARGET_STRUCT_VALUE_RTX: Aggregate Return. (line 44) * TARGET_SUPPORTS_SPLIT_STACK: Stack Smashing Protection. ! (line 25) ! * TARGET_SUPPORTS_WEAK: Label Output. (line 272) ! * TARGET_SUPPORTS_WIDE_INT: Misc. (line 1191) * TARGET_TERMINATE_DW2_EH_FRAME_INFO: Exception Region Output. ! (line 99) ! * TARGET_TRAMPOLINE_ADJUST_ADDRESS: Trampolines. (line 74) ! * TARGET_TRAMPOLINE_INIT: Trampolines. (line 54) ! * TARGET_UNSPEC_MAY_TRAP_P: Misc. (line 829) * TARGET_UNWIND_TABLES_DEFAULT: Exception Region Output. ! (line 73) ! * TARGET_UNWIND_WORD_MODE: Storage Layout. (line 475) ! * TARGET_UPDATE_STACK_BOUNDARY: Misc. (line 1097) ! * TARGET_USES_WEAK_UNWIND_INFO: Exception Handling. (line 123) ! * TARGET_USE_ANCHORS_FOR_SYMBOL_P: Anchored Addresses. (line 53) ! * TARGET_USE_BLOCKS_FOR_CONSTANT_P: Addressing Modes. (line 248) ! * TARGET_USE_BLOCKS_FOR_DECL_P: Addressing Modes. (line 255) ! * TARGET_USE_BY_PIECES_INFRASTRUCTURE_P: Costs. (line 164) ! * TARGET_USE_JCR_SECTION: Misc. (line 1079) ! * TARGET_USE_PSEUDO_PIC_REG: Register Arguments. (line 87) ! * TARGET_VALID_DLLIMPORT_ATTRIBUTE_P: Target Attributes. (line 66) ! * TARGET_VALID_POINTER_MODE: Register Arguments. (line 317) ! * TARGET_VECTORIZE_ADD_STMT_COST: Addressing Modes. (line 374) * TARGET_VECTORIZE_AUTOVECTORIZE_VECTOR_SIZES: Addressing Modes. ! (line 351) ! * TARGET_VECTORIZE_BUILTIN_CONVERSION: Addressing Modes. (line 307) ! * TARGET_VECTORIZE_BUILTIN_GATHER: Addressing Modes. (line 397) ! * TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD: Addressing Modes. (line 266) * TARGET_VECTORIZE_BUILTIN_MD_VECTORIZED_FUNCTION: Addressing Modes. ! (line 327) ! * TARGET_VECTORIZE_BUILTIN_SCATTER: Addressing Modes. (line 404) * TARGET_VECTORIZE_BUILTIN_VECTORIZATION_COST: Addressing Modes. ! (line 292) * TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION: Addressing Modes. ! (line 319) ! * TARGET_VECTORIZE_DESTROY_COST_DATA: Addressing Modes. (line 392) ! * TARGET_VECTORIZE_FINISH_COST: Addressing Modes. (line 385) ! * TARGET_VECTORIZE_GET_MASK_MODE: Addressing Modes. (line 359) ! * TARGET_VECTORIZE_INIT_COST: Addressing Modes. (line 365) ! * TARGET_VECTORIZE_PREFERRED_SIMD_MODE: Addressing Modes. (line 344) * TARGET_VECTORIZE_SUPPORT_VECTOR_MISALIGNMENT: Addressing Modes. ! (line 334) * TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE: Addressing Modes. ! (line 298) ! * TARGET_VECTORIZE_VEC_PERM_CONST_OK: Addressing Modes. (line 303) ! * TARGET_VECTOR_ALIGNMENT: Storage Layout. (line 268) ! * TARGET_VECTOR_MODE_SUPPORTED_P: Register Arguments. (line 340) ! * TARGET_VTABLE_DATA_ENTRY_DISTANCE: Type Layout. (line 309) ! * TARGET_VTABLE_ENTRY_ALIGN: Type Layout. (line 303) ! * TARGET_VTABLE_USES_DESCRIPTORS: Type Layout. (line 292) ! * TARGET_WANT_DEBUG_PUB_SECTIONS: SDB and DWARF. (line 55) ! * TARGET_WARN_FUNC_RETURN: Tail Calls. (line 35) ! * TARGET_WEAK_NOT_IN_ARCHIVE_TOC: Label Output. (line 308) ! * TCmode: Machine Modes. (line 199) * TDmode: Machine Modes. (line 97) * TEMPLATE_DECL: Declarations. (line 6) * Temporaries: Temporaries. (line 6) * termination routines: Initialization. (line 6) * testing constraints: C Constraint Interface. (line 6) ! * TEXT_SECTION_ASM_OP: Sections. (line 37) * TFmode: Machine Modes. (line 101) * The Language: The Language. (line 6) * THEN_CLAUSE: Statements for C++. (line 6) ! * THREAD_MODEL_SPEC: Driver. (line 162) * THROW_EXPR: Unary and Binary Expressions. (line 6) * THUNK_DECL: Declarations. (line 6) * THUNK_DELTA: Declarations. (line 6) * TImode: Machine Modes. (line 48) ! * TImode, in insn: Insns. (line 268) ! * TLS_COMMON_ASM_OP: Sections. (line 80) ! * TLS_SECTION_ASM_FLAG: Sections. (line 85) * tm.h macros: Target Macros. (line 6) * TQFmode: Machine Modes. (line 65) * TQmode: Machine Modes. (line 122) * trampolines for nested functions: Trampolines. (line 6) ! * TRAMPOLINE_ALIGNMENT: Trampolines. (line 48) ! * TRAMPOLINE_SECTION: Trampolines. (line 39) ! * TRAMPOLINE_SIZE: Trampolines. (line 44) ! * TRANSFER_FROM_TRAMPOLINE: Trampolines. (line 110) ! * trap instruction pattern: Standard Names. (line 1759) ! * tree: Tree overview. (line 6) * tree <1>: Macros and Functions. (line 6) * Tree SSA: Tree SSA. (line 6) * TREE_CHAIN: Macros and Functions. (line 6) --- 50623,51252 ---- * subreg and /u: Flags. (line 180) * subreg and /u and /v: Flags. (line 170) * subreg, in strict_low_part: RTL Declarations. (line 9) ! * SUBREG_BYTE: Regs and Memory. (line 289) * SUBREG_PROMOTED_UNSIGNED_P: Flags. (line 170) * SUBREG_PROMOTED_UNSIGNED_SET: Flags. (line 180) * SUBREG_PROMOTED_VAR_P: Flags. (line 187) ! * SUBREG_REG: Regs and Memory. (line 289) * subst iterators in .md files: Subst Iterators. (line 6) ! * subvM4 instruction pattern: Standard Names. (line 321) * SUCCESS_EXIT_CODE: Host Misc. (line 12) * SUPPORTS_INIT_PRIORITY: Macros for Initialization. ! (line 58) ! * SUPPORTS_ONE_ONLY: Label Output. (line 294) ! * SUPPORTS_WEAK: Label Output. (line 268) * SWITCH_BODY: Statements for C++. (line 6) * SWITCH_COND: Statements for C++. (line 6) * SWITCH_STMT: Statements for C++. (line 6) ! * SWITCHABLE_TARGET: Run-time Target. (line 165) ! * SYMBOL_FLAG_ANCHOR: Special Accessors. (line 120) ! * SYMBOL_FLAG_EXTERNAL: Special Accessors. (line 102) ! * SYMBOL_FLAG_FUNCTION: Special Accessors. (line 95) ! * SYMBOL_FLAG_HAS_BLOCK_INFO: Special Accessors. (line 116) ! * SYMBOL_FLAG_LOCAL: Special Accessors. (line 98) ! * SYMBOL_FLAG_SMALL: Special Accessors. (line 107) ! * SYMBOL_FLAG_TLS_SHIFT: Special Accessors. (line 111) * symbol_ref: Constants. (line 117) * symbol_ref and /f: Flags. (line 165) * symbol_ref and /i: Flags. (line 202) * symbol_ref and /u: Flags. (line 10) * symbol_ref and /v: Flags. (line 206) * symbol_ref, RTL sharing: Sharing. (line 20) ! * SYMBOL_REF_ANCHOR_P: Special Accessors. (line 120) ! * SYMBOL_REF_BLOCK: Special Accessors. (line 133) ! * SYMBOL_REF_BLOCK_OFFSET: Special Accessors. (line 138) ! * SYMBOL_REF_CONSTANT: Special Accessors. (line 81) ! * SYMBOL_REF_DATA: Special Accessors. (line 85) ! * SYMBOL_REF_DECL: Special Accessors. (line 69) ! * SYMBOL_REF_EXTERNAL_P: Special Accessors. (line 102) * SYMBOL_REF_FLAG: Flags. (line 206) * SYMBOL_REF_FLAG, in TARGET_ENCODE_SECTION_INFO: Sections. (line 277) ! * SYMBOL_REF_FLAGS: Special Accessors. (line 89) ! * SYMBOL_REF_FUNCTION_P: Special Accessors. (line 95) ! * SYMBOL_REF_HAS_BLOCK_INFO_P: Special Accessors. (line 116) ! * SYMBOL_REF_LOCAL_P: Special Accessors. (line 98) ! * SYMBOL_REF_SMALL_P: Special Accessors. (line 107) ! * SYMBOL_REF_TLS_MODEL: Special Accessors. (line 111) * SYMBOL_REF_USED: Flags. (line 197) * SYMBOL_REF_WEAK: Flags. (line 202) ! * symbolic label: Sharing. (line 20) ! * sync_addMODE instruction pattern: Standard Names. (line 1859) ! * sync_andMODE instruction pattern: Standard Names. (line 1859) * sync_compare_and_swapMODE instruction pattern: Standard Names. ! (line 1819) ! * sync_iorMODE instruction pattern: Standard Names. (line 1859) ! * sync_lock_releaseMODE instruction pattern: Standard Names. (line 1924) * sync_lock_test_and_setMODE instruction pattern: Standard Names. ! (line 1898) ! * sync_nandMODE instruction pattern: Standard Names. (line 1859) ! * sync_new_addMODE instruction pattern: Standard Names. (line 1891) ! * sync_new_andMODE instruction pattern: Standard Names. (line 1891) ! * sync_new_iorMODE instruction pattern: Standard Names. (line 1891) ! * sync_new_nandMODE instruction pattern: Standard Names. (line 1891) ! * sync_new_subMODE instruction pattern: Standard Names. (line 1891) ! * sync_new_xorMODE instruction pattern: Standard Names. (line 1891) ! * sync_old_addMODE instruction pattern: Standard Names. (line 1874) ! * sync_old_andMODE instruction pattern: Standard Names. (line 1874) ! * sync_old_iorMODE instruction pattern: Standard Names. (line 1874) ! * sync_old_nandMODE instruction pattern: Standard Names. (line 1874) ! * sync_old_subMODE instruction pattern: Standard Names. (line 1874) ! * sync_old_xorMODE instruction pattern: Standard Names. (line 1874) ! * sync_subMODE instruction pattern: Standard Names. (line 1859) ! * sync_xorMODE instruction pattern: Standard Names. (line 1859) ! * SYSROOT_HEADERS_SUFFIX_SPEC: Driver. (line 177) ! * SYSROOT_SUFFIX_SPEC: Driver. (line 172) * t-TARGET: Target Fragment. (line 6) * table jump: Basic Blocks. (line 67) ! * tablejump instruction pattern: Standard Names. (line 1485) * tag: GTY Options. (line 88) * tagging insns: Tagging Insns. (line 6) * tail calls: Tail Calls. (line 6) ! * TAmode: Machine Modes. (line 159) ! * tanM2 instruction pattern: Standard Names. (line 691) * target attributes: Target Attributes. (line 6) * target description macros: Target Macros. (line 6) * target functions: Target Structure. (line 6) * target hooks: Target Structure. (line 6) * target makefile fragment: Target Fragment. (line 6) * target specifications: Run-time Target. (line 6) ! * TARGET_ABSOLUTE_BIGGEST_ALIGNMENT: Storage Layout. (line 170) * TARGET_ADDR_SPACE_ADDRESS_MODE: Named Address Spaces. ! (line 44) * TARGET_ADDR_SPACE_CONVERT: Named Address Spaces. ! (line 92) * TARGET_ADDR_SPACE_DEBUG: Named Address Spaces. ! (line 101) * TARGET_ADDR_SPACE_LEGITIMATE_ADDRESS_P: Named Address Spaces. ! (line 61) * TARGET_ADDR_SPACE_LEGITIMIZE_ADDRESS: Named Address Spaces. ! (line 70) * TARGET_ADDR_SPACE_POINTER_MODE: Named Address Spaces. ! (line 38) * TARGET_ADDR_SPACE_SUBSET_P: Named Address Spaces. ! (line 77) * TARGET_ADDR_SPACE_VALID_POINTER_MODE: Named Address Spaces. ! (line 50) * TARGET_ADDR_SPACE_ZERO_ADDRESS_VALID: Named Address Spaces. ! (line 86) ! * TARGET_ADDRESS_COST: Costs. (line 325) ! * TARGET_ALIGN_ANON_BITFIELD: Storage Layout. (line 406) ! * TARGET_ALLOCATE_INITIAL_VALUE: Misc. (line 815) ! * TARGET_ALLOCATE_STACK_SLOTS_FOR_ARGS: Misc. (line 1113) ! * TARGET_ALWAYS_STRIP_DOTDOT: Driver. (line 251) ! * TARGET_ARG_PARTIAL_BYTES: Register Arguments. (line 98) * TARGET_ARM_EABI_UNWINDER: Exception Region Output. ! (line 136) ! * TARGET_ARRAY_MODE_SUPPORTED_P: Register Arguments. (line 349) ! * TARGET_ASAN_SHADOW_OFFSET: Misc. (line 1141) ! * TARGET_ASM_ALIGNED_DI_OP: Data Output. (line 10) ! * TARGET_ASM_ALIGNED_HI_OP: Data Output. (line 8) ! * TARGET_ASM_ALIGNED_SI_OP: Data Output. (line 9) ! * TARGET_ASM_ALIGNED_TI_OP: Data Output. (line 11) ! * TARGET_ASM_ASSEMBLE_UNDEFINED_DECL: Label Output. (line 236) ! * TARGET_ASM_ASSEMBLE_VISIBILITY: Label Output. (line 306) ! * TARGET_ASM_BYTE_OP: Data Output. (line 7) ! * TARGET_ASM_CAN_OUTPUT_MI_THUNK: Function Entry. (line 207) ! * TARGET_ASM_CLOSE_PAREN: Data Output. (line 135) ! * TARGET_ASM_CODE_END: File Framework. (line 59) * TARGET_ASM_CONSTRUCTOR: Macros for Initialization. ! (line 69) ! * TARGET_ASM_DECL_END: Data Output. (line 39) ! * TARGET_ASM_DECLARE_CONSTANT_NAME: Label Output. (line 182) * TARGET_ASM_DESTRUCTOR: Macros for Initialization. ! (line 83) ! * TARGET_ASM_EMIT_EXCEPT_PERSONALITY: Dispatch Tables. (line 82) ! * TARGET_ASM_EMIT_EXCEPT_TABLE_LABEL: Dispatch Tables. (line 74) ! * TARGET_ASM_EMIT_UNWIND_LABEL: Dispatch Tables. (line 63) ! * TARGET_ASM_EXTERNAL_LIBCALL: Label Output. (line 341) ! * TARGET_ASM_FILE_END: File Framework. (line 37) ! * TARGET_ASM_FILE_START: File Framework. (line 9) ! * TARGET_ASM_FILE_START_APP_OFF: File Framework. (line 17) ! * TARGET_ASM_FILE_START_FILE_DIRECTIVE: File Framework. (line 31) ! * TARGET_ASM_FINAL_POSTSCAN_INSN: Instruction Output. (line 84) ! * TARGET_ASM_FUNCTION_BEGIN_EPILOGUE: Function Entry. (line 61) ! * TARGET_ASM_FUNCTION_END_PROLOGUE: Function Entry. (line 55) ! * TARGET_ASM_FUNCTION_EPILOGUE: Function Entry. (line 68) ! * TARGET_ASM_FUNCTION_PROLOGUE: Function Entry. (line 11) ! * TARGET_ASM_FUNCTION_RODATA_SECTION: Sections. (line 215) ! * TARGET_ASM_FUNCTION_SECTION: File Framework. (line 124) * TARGET_ASM_FUNCTION_SWITCHED_TEXT_SECTIONS: File Framework. ! (line 134) ! * TARGET_ASM_GLOBALIZE_DECL_NAME: Label Output. (line 227) ! * TARGET_ASM_GLOBALIZE_LABEL: Label Output. (line 218) ! * TARGET_ASM_INIT_SECTIONS: Sections. (line 160) ! * TARGET_ASM_INTEGER: Data Output. (line 27) ! * TARGET_ASM_INTERNAL_LABEL: Label Output. (line 385) ! * TARGET_ASM_JUMP_ALIGN_MAX_SKIP: Alignment Output. (line 22) * TARGET_ASM_LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP: Alignment Output. ! (line 36) ! * TARGET_ASM_LABEL_ALIGN_MAX_SKIP: Alignment Output. (line 69) ! * TARGET_ASM_LOOP_ALIGN_MAX_SKIP: Alignment Output. (line 54) ! * TARGET_ASM_LTO_END: File Framework. (line 54) ! * TARGET_ASM_LTO_START: File Framework. (line 49) ! * TARGET_ASM_MARK_DECL_PRESERVED: Label Output. (line 348) ! * TARGET_ASM_MERGEABLE_RODATA_PREFIX: Sections. (line 222) ! * TARGET_ASM_NAMED_SECTION: File Framework. (line 116) ! * TARGET_ASM_OPEN_PAREN: Data Output. (line 134) ! * TARGET_ASM_OUTPUT_ADDR_CONST_EXTRA: Data Output. (line 44) ! * TARGET_ASM_OUTPUT_ANCHOR: Anchored Addresses. (line 44) ! * TARGET_ASM_OUTPUT_DWARF_DTPREL: SDB and DWARF. (line 110) ! * TARGET_ASM_OUTPUT_IDENT: File Framework. (line 102) ! * TARGET_ASM_OUTPUT_MI_THUNK: Function Entry. (line 165) ! * TARGET_ASM_OUTPUT_SOURCE_FILENAME: File Framework. (line 94) ! * TARGET_ASM_RECORD_GCC_SWITCHES: File Framework. (line 165) ! * TARGET_ASM_RECORD_GCC_SWITCHES_SECTION: File Framework. (line 209) ! * TARGET_ASM_RELOC_RW_MASK: Sections. (line 169) ! * TARGET_ASM_SELECT_RTX_SECTION: Sections. (line 232) ! * TARGET_ASM_SELECT_SECTION: Sections. (line 181) ! * TARGET_ASM_TM_CLONE_TABLE_SECTION: Sections. (line 227) ! * TARGET_ASM_TRAMPOLINE_TEMPLATE: Trampolines. (line 29) * TARGET_ASM_TTYPE: Exception Region Output. ! (line 130) ! * TARGET_ASM_UNALIGNED_DI_OP: Data Output. (line 14) ! * TARGET_ASM_UNALIGNED_HI_OP: Data Output. (line 12) ! * TARGET_ASM_UNALIGNED_SI_OP: Data Output. (line 13) ! * TARGET_ASM_UNALIGNED_TI_OP: Data Output. (line 15) ! * TARGET_ASM_UNIQUE_SECTION: Sections. (line 202) ! * TARGET_ASM_UNWIND_EMIT: Dispatch Tables. (line 89) ! * TARGET_ASM_UNWIND_EMIT_BEFORE_INSN: Dispatch Tables. (line 94) ! * TARGET_ATOMIC_ALIGN_FOR_MODE: Misc. (line 1161) ! * TARGET_ATOMIC_ASSIGN_EXPAND_FENV: Misc. (line 1167) ! * TARGET_ATOMIC_TEST_AND_SET_TRUEVAL: Misc. (line 1151) ! * TARGET_ATTRIBUTE_TABLE: Target Attributes. (line 11) ! * TARGET_ATTRIBUTE_TAKES_IDENTIFIER_P: Target Attributes. (line 19) ! * TARGET_BINDS_LOCAL_P: Sections. (line 309) ! * TARGET_BRANCH_TARGET_REGISTER_CALLEE_SAVED: Misc. (line 912) ! * TARGET_BRANCH_TARGET_REGISTER_CLASS: Misc. (line 904) ! * TARGET_BUILD_BUILTIN_VA_LIST: Register Arguments. (line 287) * TARGET_BUILTIN_CHKP_FUNCTION: Misc. (line 625) ! * TARGET_BUILTIN_DECL: Misc. (line 606) ! * TARGET_BUILTIN_RECIPROCAL: Addressing Modes. (line 263) ! * TARGET_BUILTIN_SETJMP_FRAME_VALUE: Frame Layout. (line 105) ! * TARGET_C_PREINCLUDE: Misc. (line 362) ! * TARGET_CALL_ARGS: Varargs. (line 127) * TARGET_CALL_FUSAGE_CONTAINS_NON_CALLEE_CLOBBERS: Miscellaneous Register Hooks. ! (line 7) ! * TARGET_CALLEE_COPIES: Register Arguments. (line 130) ! * TARGET_CAN_ELIMINATE: Elimination. (line 75) ! * TARGET_CAN_FOLLOW_JUMP: Misc. (line 802) ! * TARGET_CAN_INLINE_P: Target Attributes. (line 166) ! * TARGET_CAN_USE_DOLOOP_P: Misc. (line 768) ! * TARGET_CANNOT_FORCE_CONST_MEM: Addressing Modes. (line 237) ! * TARGET_CANNOT_MODIFY_JUMPS_P: Misc. (line 891) ! * TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P: Register Classes. (line 604) ! * TARGET_CANONICAL_VA_LIST_TYPE: Register Arguments. (line 308) * TARGET_CANONICALIZE_COMPARISON: MODE_CC Condition Codes. ! (line 57) ! * TARGET_CASE_VALUES_THRESHOLD: Misc. (line 47) * TARGET_CC_MODES_COMPATIBLE: MODE_CC Condition Codes. ! (line 122) ! * TARGET_CHECK_PCH_TARGET_FLAGS: PCH Target. (line 28) ! * TARGET_CHECK_STRING_OBJECT_FORMAT_ARG: Run-time Target. (line 121) ! * TARGET_CHKP_BOUND_MODE: Misc. (line 700) ! * TARGET_CHKP_BOUND_TYPE: Misc. (line 697) ! * TARGET_CHKP_FUNCTION_VALUE_BOUNDS: Varargs. (line 188) ! * TARGET_CHKP_INITIALIZE_BOUNDS: Misc. (line 709) ! * TARGET_CHKP_MAKE_BOUNDS_CONSTANT: Misc. (line 704) ! * TARGET_CLASS_LIKELY_SPILLED_P: Register Classes. (line 494) ! * TARGET_CLASS_MAX_NREGS: Register Classes. (line 511) ! * TARGET_COMMUTATIVE_P: Misc. (line 808) ! * TARGET_COMP_TYPE_ATTRIBUTES: Target Attributes. (line 27) ! * TARGET_COMPARE_VERSION_PRIORITY: Misc. (line 743) ! * TARGET_CONDITIONAL_REGISTER_USAGE: Register Basics. (line 60) ! * TARGET_CONST_ANCHOR: Misc. (line 1124) ! * TARGET_CONST_NOT_OK_FOR_DEBUG_P: Addressing Modes. (line 232) ! * TARGET_CONVERT_TO_TYPE: Misc. (line 1077) ! * TARGET_CPU_CPP_BUILTINS: Run-time Target. (line 9) ! * TARGET_CSTORE_MODE: Register Classes. (line 628) ! * TARGET_CXX_ADJUST_CLASS_AT_DEFINITION: C++ ABI. (line 87) ! * TARGET_CXX_CDTOR_RETURNS_THIS: C++ ABI. (line 38) ! * TARGET_CXX_CLASS_DATA_ALWAYS_COMDAT: C++ ABI. (line 62) ! * TARGET_CXX_COOKIE_HAS_SIZE: C++ ABI. (line 25) ! * TARGET_CXX_DECL_MANGLING_CONTEXT: C++ ABI. (line 93) ! * TARGET_CXX_DETERMINE_CLASS_DATA_VISIBILITY: C++ ABI. (line 54) ! * TARGET_CXX_GET_COOKIE_SIZE: C++ ABI. (line 18) ! * TARGET_CXX_GUARD_MASK_BIT: C++ ABI. (line 12) ! * TARGET_CXX_GUARD_TYPE: C++ ABI. (line 7) ! * TARGET_CXX_IMPLICIT_EXTERN_C: Misc. (line 374) ! * TARGET_CXX_IMPORT_EXPORT_CLASS: C++ ABI. (line 30) ! * TARGET_CXX_KEY_METHOD_MAY_BE_INLINE: C++ ABI. (line 43) ! * TARGET_CXX_LIBRARY_RTTI_COMDAT: C++ ABI. (line 69) ! * TARGET_CXX_USE_AEABI_ATEXIT: C++ ABI. (line 74) ! * TARGET_CXX_USE_ATEXIT_FOR_CXA_ATEXIT: C++ ABI. (line 80) ! * TARGET_DEBUG_UNWIND_INFO: SDB and DWARF. (line 37) ! * TARGET_DECIMAL_FLOAT_SUPPORTED_P: Storage Layout. (line 512) ! * TARGET_DECLSPEC: Target Attributes. (line 73) ! * TARGET_DEFAULT_PACK_STRUCT: Misc. (line 448) ! * TARGET_DEFAULT_SHORT_ENUMS: Type Layout. (line 130) ! * TARGET_DEFAULT_TARGET_FLAGS: Run-time Target. (line 56) ! * TARGET_DEFERRED_OUTPUT_DEFS: Label Output. (line 469) ! * TARGET_DELAY_SCHED2: SDB and DWARF. (line 66) ! * TARGET_DELAY_VARTRACK: SDB and DWARF. (line 70) ! * TARGET_DELEGITIMIZE_ADDRESS: Addressing Modes. (line 223) ! * TARGET_DIFFERENT_ADDR_DISPLACEMENT_P: Register Classes. (line 597) * TARGET_DLLIMPORT_DECL_ATTRIBUTES: Target Attributes. (line 55) ! * TARGET_DWARF_CALLING_CONVENTION: SDB and DWARF. (line 18) * TARGET_DWARF_FRAME_REG_MODE: Exception Region Output. ! (line 116) ! * TARGET_DWARF_HANDLE_FRAME_UNSPEC: Frame Layout. (line 170) * TARGET_DWARF_REGISTER_SPAN: Exception Region Output. ! (line 107) ! * TARGET_EDOM: Library Calls. (line 60) ! * TARGET_EMUTLS_DEBUG_FORM_TLS_ADDRESS: Emulated TLS. (line 68) ! * TARGET_EMUTLS_GET_ADDRESS: Emulated TLS. (line 19) ! * TARGET_EMUTLS_REGISTER_COMMON: Emulated TLS. (line 24) ! * TARGET_EMUTLS_TMPL_PREFIX: Emulated TLS. (line 45) ! * TARGET_EMUTLS_TMPL_SECTION: Emulated TLS. (line 36) ! * TARGET_EMUTLS_VAR_ALIGN_FIXED: Emulated TLS. (line 63) ! * TARGET_EMUTLS_VAR_FIELDS: Emulated TLS. (line 49) ! * TARGET_EMUTLS_VAR_INIT: Emulated TLS. (line 57) ! * TARGET_EMUTLS_VAR_PREFIX: Emulated TLS. (line 41) ! * TARGET_EMUTLS_VAR_SECTION: Emulated TLS. (line 31) ! * TARGET_ENCODE_SECTION_INFO: Sections. (line 253) * TARGET_ENCODE_SECTION_INFO and address validation: Addressing Modes. ! (line 83) ! * TARGET_ENCODE_SECTION_INFO usage: Instruction Output. (line 128) ! * TARGET_END_CALL_ARGS: Varargs. (line 141) ! * TARGET_ENUM_VA_LIST_P: Register Arguments. (line 292) * TARGET_EXCEPT_UNWIND_INFO: Exception Region Output. ! (line 49) ! * TARGET_EXECUTABLE_SUFFIX: Misc. (line 865) ! * TARGET_EXPAND_BUILTIN: Misc. (line 616) ! * TARGET_EXPAND_BUILTIN_SAVEREGS: Varargs. (line 67) ! * TARGET_EXPAND_TO_RTL_HOOK: Storage Layout. (line 518) * TARGET_EXPR: Unary and Binary Expressions. (line 6) ! * TARGET_EXTRA_INCLUDES: Misc. (line 979) ! * TARGET_EXTRA_LIVE_ON_ENTRY: Tail Calls. (line 21) ! * TARGET_EXTRA_PRE_INCLUDES: Misc. (line 986) * TARGET_FIXED_CONDITION_CODE_REGS: MODE_CC Condition Codes. ! (line 107) ! * TARGET_FIXED_POINT_SUPPORTED_P: Storage Layout. (line 515) ! * target_flags: Run-time Target. (line 52) * TARGET_FLAGS_REGNUM: MODE_CC Condition Codes. ! (line 134) * TARGET_FLOAT_EXCEPTIONS_ROUNDING_SUPPORTED_P: Run-time Target. ! (line 185) ! * TARGET_FLT_EVAL_METHOD: Type Layout. (line 111) ! * TARGET_FN_ABI_VA_LIST: Register Arguments. (line 303) ! * TARGET_FOLD_BUILTIN: Misc. (line 726) ! * TARGET_FORCE_AT_COMP_DIR: SDB and DWARF. (line 61) ! * TARGET_FORMAT_TYPES: Misc. (line 1006) ! * TARGET_FRAME_POINTER_REQUIRED: Elimination. (line 9) ! * TARGET_FUNCTION_ARG: Register Arguments. (line 12) ! * TARGET_FUNCTION_ARG_ADVANCE: Register Arguments. (line 201) ! * TARGET_FUNCTION_ARG_BOUNDARY: Register Arguments. (line 255) ! * TARGET_FUNCTION_ARG_ROUND_BOUNDARY: Register Arguments. (line 261) ! * TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P: Target Attributes. (line 95) ! * TARGET_FUNCTION_INCOMING_ARG: Register Arguments. (line 74) ! * TARGET_FUNCTION_OK_FOR_SIBCALL: Tail Calls. (line 8) ! * TARGET_FUNCTION_VALUE: Scalar Return. (line 11) ! * TARGET_FUNCTION_VALUE_REGNO_P: Scalar Return. (line 97) ! * TARGET_GEN_CCMP_FIRST: Misc. (line 933) ! * TARGET_GEN_CCMP_NEXT: Misc. (line 944) ! * TARGET_GENERATE_VERSION_DISPATCHER_BODY: Misc. (line 760) ! * TARGET_GET_DRAP_RTX: Misc. (line 1107) ! * TARGET_GET_FUNCTION_VERSIONS_DISPATCHER: Misc. (line 753) ! * TARGET_GET_PCH_VALIDITY: PCH Target. (line 7) ! * TARGET_GET_RAW_ARG_MODE: Aggregate Return. (line 82) ! * TARGET_GET_RAW_RESULT_MODE: Aggregate Return. (line 77) ! * TARGET_GIMPLE_FOLD_BUILTIN: Misc. (line 736) ! * TARGET_GIMPLIFY_VA_ARG_EXPR: Register Arguments. (line 314) ! * TARGET_GOACC_DIM_LIMIT: Addressing Modes. (line 448) ! * TARGET_GOACC_FORK_JOIN: Addressing Modes. (line 453) ! * TARGET_GOACC_REDUCTION: Addressing Modes. (line 463) ! * TARGET_GOACC_VALIDATE_DIMS: Addressing Modes. (line 436) ! * TARGET_HANDLE_C_OPTION: Run-time Target. (line 75) ! * TARGET_HANDLE_OPTION: Run-time Target. (line 62) * TARGET_HARD_REGNO_SCRATCH_OK: Values in Registers. ! (line 144) ! * TARGET_HAS_IFUNC_P: Misc. (line 1155) ! * TARGET_HAS_NO_HW_DIVIDE: Library Calls. (line 53) ! * TARGET_HAVE_CONDITIONAL_EXECUTION: Misc. (line 926) * TARGET_HAVE_CTORS_DTORS: Macros for Initialization. ! (line 64) ! * TARGET_HAVE_NAMED_SECTIONS: File Framework. (line 141) ! * TARGET_HAVE_SRODATA_SECTION: Sections. (line 298) ! * TARGET_HAVE_SWITCHABLE_BSS_SECTIONS: File Framework. (line 146) ! * TARGET_HAVE_TLS: Sections. (line 318) ! * TARGET_IN_SMALL_DATA_P: Sections. (line 294) ! * TARGET_INIT_BUILTINS: Misc. (line 589) * TARGET_INIT_DWARF_REG_SIZES_EXTRA: Exception Region Output. ! (line 122) ! * TARGET_INIT_LIBFUNCS: Library Calls. (line 16) ! * TARGET_INIT_PIC_REG: Register Arguments. (line 93) ! * TARGET_INSERT_ATTRIBUTES: Target Attributes. (line 82) ! * TARGET_INSTANTIATE_DECLS: Storage Layout. (line 526) ! * TARGET_INVALID_ARG_FOR_UNPROTOTYPED_FN: Misc. (line 1031) ! * TARGET_INVALID_BINARY_OP: Misc. (line 1050) ! * TARGET_INVALID_CONVERSION: Misc. (line 1037) ! * TARGET_INVALID_PARAMETER_TYPE: Misc. (line 1056) ! * TARGET_INVALID_RETURN_TYPE: Misc. (line 1063) ! * TARGET_INVALID_UNARY_OP: Misc. (line 1043) ! * TARGET_INVALID_WITHIN_DOLOOP: Misc. (line 784) ! * TARGET_IRA_CHANGE_PSEUDO_ALLOCNO_CLASS: Register Classes. (line 564) ! * TARGET_KEEP_LEAF_WHEN_PROFILED: Profiling. (line 40) ! * TARGET_LEGITIMATE_ADDRESS_P: Addressing Modes. (line 50) ! * TARGET_LEGITIMATE_COMBINED_INSN: Misc. (line 796) ! * TARGET_LEGITIMATE_CONSTANT_P: Addressing Modes. (line 216) ! * TARGET_LEGITIMIZE_ADDRESS: Addressing Modes. (line 132) ! * TARGET_LEGITIMIZE_ADDRESS_DISPLACEMENT: Register Classes. (line 614) ! * TARGET_LIB_INT_CMP_BIASED: Library Calls. (line 43) ! * TARGET_LIBC_HAS_FUNCTION: Library Calls. (line 79) ! * TARGET_LIBCALL_VALUE: Scalar Return. (line 66) ! * TARGET_LIBFUNC_GNU_PREFIX: Library Calls. (line 25) ! * TARGET_LIBGCC_CMP_RETURN_MODE: Storage Layout. (line 468) * TARGET_LIBGCC_FLOATING_MODE_SUPPORTED_P: Register Arguments. ! (line 373) ! * TARGET_LIBGCC_SDATA_SECTION: Sections. (line 132) ! * TARGET_LIBGCC_SHIFT_COUNT_MODE: Storage Layout. (line 474) ! * TARGET_LOAD_BOUNDS_FOR_ARG: Varargs. (line 158) ! * TARGET_LOAD_RETURNED_BOUNDS: Varargs. (line 177) ! * TARGET_LOOP_UNROLL_ADJUST: Misc. (line 960) ! * TARGET_LRA_P: Register Classes. (line 570) ! * TARGET_MACHINE_DEPENDENT_REORG: Misc. (line 574) ! * TARGET_MANGLE_ASSEMBLER_NAME: Label Output. (line 360) ! * TARGET_MANGLE_DECL_ASSEMBLER_NAME: Sections. (line 243) ! * TARGET_MANGLE_TYPE: Storage Layout. (line 530) ! * TARGET_MAX_ANCHOR_OFFSET: Anchored Addresses. (line 39) ! * TARGET_MD_ASM_ADJUST: Misc. (line 495) ! * TARGET_MEM_CONSTRAINT: Addressing Modes. (line 109) * TARGET_MEM_REF: Storage References. (line 6) ! * TARGET_MEMBER_TYPE_FORCES_BLK: Storage Layout. (line 421) ! * TARGET_MEMMODEL_CHECK: Misc. (line 1147) ! * TARGET_MEMORY_MOVE_COST: Costs. (line 81) ! * TARGET_MERGE_DECL_ATTRIBUTES: Target Attributes. (line 47) ! * TARGET_MERGE_TYPE_ATTRIBUTES: Target Attributes. (line 39) ! * TARGET_MIN_ANCHOR_OFFSET: Anchored Addresses. (line 33) ! * TARGET_MIN_DIVISIONS_FOR_RECIP_MUL: Misc. (line 92) ! * TARGET_MODE_AFTER: Mode Switching. (line 59) ! * TARGET_MODE_DEPENDENT_ADDRESS_P: Addressing Modes. (line 199) ! * TARGET_MODE_EMIT: Mode Switching. (line 44) ! * TARGET_MODE_ENTRY: Mode Switching. (line 65) ! * TARGET_MODE_EXIT: Mode Switching. (line 72) ! * TARGET_MODE_NEEDED: Mode Switching. (line 51) ! * TARGET_MODE_PRIORITY: Mode Switching. (line 79) ! * TARGET_MODE_REP_EXTENDED: Misc. (line 177) ! * TARGET_MS_BITFIELD_LAYOUT_P: Storage Layout. (line 485) ! * TARGET_MUST_PASS_IN_STACK: Register Arguments. (line 67) * TARGET_MUST_PASS_IN_STACK, and TARGET_FUNCTION_ARG: Register Arguments. ! (line 57) ! * TARGET_N_FORMAT_TYPES: Misc. (line 1011) ! * TARGET_NARROW_VOLATILE_BITFIELD: Storage Layout. (line 412) ! * TARGET_NO_REGISTER_ALLOCATION: SDB and DWARF. (line 74) ! * TARGET_NO_SPECULATION_IN_DELAY_SLOTS_P: Costs. (line 361) ! * TARGET_OBJC_CONSTRUCT_STRING_OBJECT: Run-time Target. (line 90) ! * TARGET_OBJC_DECLARE_CLASS_DEFINITION: Run-time Target. (line 111) * TARGET_OBJC_DECLARE_UNRESOLVED_CLASS_REFERENCE: Run-time Target. ! (line 106) ! * TARGET_OBJECT_SUFFIX: Misc. (line 860) ! * TARGET_OBJFMT_CPP_BUILTINS: Run-time Target. (line 46) ! * TARGET_OFFLOAD_OPTIONS: Misc. (line 1191) * TARGET_OMIT_STRUCT_RETURN_REG: Scalar Return. (line 117) ! * TARGET_OPTAB_SUPPORTED_P: Costs. (line 280) ! * TARGET_OPTF: Misc. (line 993) ! * TARGET_OPTION_DEFAULT_PARAMS: Run-time Target. (line 161) ! * TARGET_OPTION_FUNCTION_VERSIONS: Target Attributes. (line 159) ! * TARGET_OPTION_INIT_STRUCT: Run-time Target. (line 158) ! * TARGET_OPTION_OPTIMIZATION_TABLE: Run-time Target. (line 144) ! * TARGET_OPTION_OVERRIDE: Target Attributes. (line 145) ! * TARGET_OPTION_POST_STREAM_IN: Target Attributes. (line 127) ! * TARGET_OPTION_PRAGMA_PARSE: Target Attributes. (line 139) ! * TARGET_OPTION_PRINT: Target Attributes. (line 133) ! * TARGET_OPTION_RESTORE: Target Attributes. (line 121) ! * TARGET_OPTION_SAVE: Target Attributes. (line 114) ! * TARGET_OPTION_VALID_ATTRIBUTE_P: Target Attributes. (line 102) ! * TARGET_OS_CPP_BUILTINS: Run-time Target. (line 42) ! * TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE: Run-time Target. (line 127) ! * TARGET_OVERRIDES_FORMAT_ATTRIBUTES: Misc. (line 1015) ! * TARGET_OVERRIDES_FORMAT_ATTRIBUTES_COUNT: Misc. (line 1021) ! * TARGET_OVERRIDES_FORMAT_INIT: Misc. (line 1025) ! * TARGET_PASS_BY_REFERENCE: Register Arguments. (line 118) ! * TARGET_PCH_VALID_P: PCH Target. (line 13) ! * TARGET_POSIX_IO: Misc. (line 519) ! * TARGET_PREFERRED_OUTPUT_RELOAD_CLASS: Register Classes. (line 289) ! * TARGET_PREFERRED_RELOAD_CLASS: Register Classes. (line 218) ! * TARGET_PREFERRED_RENAME_CLASS: Register Classes. (line 206) ! * TARGET_PREPARE_PCH_SAVE: PCH Target. (line 35) ! * TARGET_PRETEND_OUTGOING_VARARGS_NAMED: Varargs. (line 149) ! * TARGET_PROFILE_BEFORE_PROLOGUE: Sections. (line 302) ! * TARGET_PROMOTE_FUNCTION_MODE: Storage Layout. (line 113) ! * TARGET_PROMOTE_PROTOTYPES: Stack Arguments. (line 11) ! * TARGET_PROMOTED_TYPE: Misc. (line 1069) ! * TARGET_PTRMEMFUNC_VBIT_LOCATION: Type Layout. (line 258) ! * TARGET_RECORD_OFFLOAD_SYMBOL: Misc. (line 1185) ! * TARGET_REF_MAY_ALIAS_ERRNO: Register Arguments. (line 325) ! * TARGET_REGISTER_MOVE_COST: Costs. (line 33) ! * TARGET_REGISTER_PRIORITY: Register Classes. (line 575) ! * TARGET_REGISTER_USAGE_LEVELING_P: Register Classes. (line 587) ! * TARGET_RELAYOUT_FUNCTION: Target Attributes. (line 173) ! * TARGET_RESOLVE_OVERLOADED_BUILTIN: Misc. (line 715) ! * TARGET_RETURN_IN_MEMORY: Aggregate Return. (line 17) * TARGET_RETURN_IN_MSB: Scalar Return. (line 124) ! * TARGET_RETURN_POPS_ARGS: Stack Arguments. (line 100) ! * TARGET_RTX_COSTS: Costs. (line 294) ! * TARGET_SCALAR_MODE_SUPPORTED_P: Register Arguments. (line 332) ! * TARGET_SCHED_ADJUST_COST: Scheduling. (line 37) ! * TARGET_SCHED_ADJUST_PRIORITY: Scheduling. (line 52) ! * TARGET_SCHED_ALLOC_SCHED_CONTEXT: Scheduling. (line 297) ! * TARGET_SCHED_CLEAR_SCHED_CONTEXT: Scheduling. (line 312) ! * TARGET_SCHED_DEPENDENCIES_EVALUATION_HOOK: Scheduling. (line 103) ! * TARGET_SCHED_DFA_NEW_CYCLE: Scheduling. (line 258) ! * TARGET_SCHED_DFA_POST_ADVANCE_CYCLE: Scheduling. (line 174) ! * TARGET_SCHED_DFA_POST_CYCLE_INSN: Scheduling. (line 158) ! * TARGET_SCHED_DFA_PRE_ADVANCE_CYCLE: Scheduling. (line 167) ! * TARGET_SCHED_DFA_PRE_CYCLE_INSN: Scheduling. (line 146) ! * TARGET_SCHED_DISPATCH: Scheduling. (line 366) ! * TARGET_SCHED_DISPATCH_DO: Scheduling. (line 371) ! * TARGET_SCHED_EXPOSED_PIPELINE: Scheduling. (line 375) ! * TARGET_SCHED_FINISH: Scheduling. (line 123) ! * TARGET_SCHED_FINISH_GLOBAL: Scheduling. (line 140) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BACKTRACK: Scheduling. (line 237) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_BEGIN: Scheduling. (line 226) * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD: Scheduling. ! (line 182) * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_DFA_LOOKAHEAD_GUARD: Scheduling. ! (line 211) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_END: Scheduling. (line 242) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_FINI: Scheduling. (line 252) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_INIT: Scheduling. (line 247) ! * TARGET_SCHED_FIRST_CYCLE_MULTIPASS_ISSUE: Scheduling. (line 232) ! * TARGET_SCHED_FREE_SCHED_CONTEXT: Scheduling. (line 316) ! * TARGET_SCHED_FUSION_PRIORITY: Scheduling. (line 386) ! * TARGET_SCHED_GEN_SPEC_CHECK: Scheduling. (line 339) ! * TARGET_SCHED_H_I_D_EXTENDED: Scheduling. (line 292) ! * TARGET_SCHED_INIT: Scheduling. (line 113) ! * TARGET_SCHED_INIT_DFA_POST_CYCLE_INSN: Scheduling. (line 163) ! * TARGET_SCHED_INIT_DFA_PRE_CYCLE_INSN: Scheduling. (line 155) ! * TARGET_SCHED_INIT_GLOBAL: Scheduling. (line 132) ! * TARGET_SCHED_INIT_SCHED_CONTEXT: Scheduling. (line 302) ! * TARGET_SCHED_IS_COSTLY_DEPENDENCE: Scheduling. (line 269) ! * TARGET_SCHED_ISSUE_RATE: Scheduling. (line 12) ! * TARGET_SCHED_MACRO_FUSION_P: Scheduling. (line 88) ! * TARGET_SCHED_MACRO_FUSION_PAIR_P: Scheduling. (line 93) ! * TARGET_SCHED_NEEDS_BLOCK_P: Scheduling. (line 332) ! * TARGET_SCHED_REASSOCIATION_WIDTH: Scheduling. (line 381) ! * TARGET_SCHED_REORDER: Scheduling. (line 60) ! * TARGET_SCHED_REORDER2: Scheduling. (line 77) ! * TARGET_SCHED_SET_SCHED_CONTEXT: Scheduling. (line 308) ! * TARGET_SCHED_SET_SCHED_FLAGS: Scheduling. (line 351) ! * TARGET_SCHED_SMS_RES_MII: Scheduling. (line 357) ! * TARGET_SCHED_SPECULATE_INSN: Scheduling. (line 320) ! * TARGET_SCHED_VARIABLE_ISSUE: Scheduling. (line 24) ! * TARGET_SECONDARY_RELOAD: Register Classes. (line 318) ! * TARGET_SECTION_TYPE_FLAGS: File Framework. (line 152) ! * TARGET_SET_CURRENT_FUNCTION: Misc. (line 842) ! * TARGET_SET_DEFAULT_TYPE_ATTRIBUTES: Target Attributes. (line 34) ! * TARGET_SET_UP_BY_PROLOGUE: Tail Calls. (line 31) ! * TARGET_SETUP_INCOMING_VARARG_BOUNDS: Varargs. (line 195) ! * TARGET_SETUP_INCOMING_VARARGS: Varargs. (line 76) ! * TARGET_SHIFT_TRUNCATION_MASK: Misc. (line 140) ! * TARGET_SIMD_CLONE_ADJUST: Addressing Modes. (line 425) * TARGET_SIMD_CLONE_COMPUTE_VECSIZE_AND_SIMDLEN: Addressing Modes. ! (line 418) ! * TARGET_SIMD_CLONE_USABLE: Addressing Modes. (line 429) * TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P: Register Arguments. ! (line 381) ! * TARGET_SPILL_CLASS: Register Classes. (line 622) ! * TARGET_SPLIT_COMPLEX_ARG: Register Arguments. (line 275) * TARGET_STACK_PROTECT_FAIL: Stack Smashing Protection. ! (line 17) * TARGET_STACK_PROTECT_GUARD: Stack Smashing Protection. ! (line 7) ! * TARGET_STATIC_CHAIN: Frame Registers. (line 92) ! * TARGET_STORE_BOUNDS_FOR_ARG: Varargs. (line 168) ! * TARGET_STORE_RETURNED_BOUNDS: Varargs. (line 183) ! * TARGET_STRICT_ARGUMENT_NAMING: Varargs. (line 112) ! * TARGET_STRING_OBJECT_REF_TYPE_P: Run-time Target. (line 116) ! * TARGET_STRIP_NAME_ENCODING: Sections. (line 290) ! * TARGET_STRUCT_VALUE_RTX: Aggregate Return. (line 45) * TARGET_SUPPORTS_SPLIT_STACK: Stack Smashing Protection. ! (line 27) ! * TARGET_SUPPORTS_WEAK: Label Output. (line 276) ! * TARGET_SUPPORTS_WIDE_INT: Misc. (line 1200) * TARGET_TERMINATE_DW2_EH_FRAME_INFO: Exception Region Output. ! (line 101) ! * TARGET_TRAMPOLINE_ADJUST_ADDRESS: Trampolines. (line 75) ! * TARGET_TRAMPOLINE_INIT: Trampolines. (line 56) ! * TARGET_UNSPEC_MAY_TRAP_P: Misc. (line 834) * TARGET_UNWIND_TABLES_DEFAULT: Exception Region Output. ! (line 75) ! * TARGET_UNWIND_WORD_MODE: Storage Layout. (line 480) ! * TARGET_UPDATE_STACK_BOUNDARY: Misc. (line 1103) ! * TARGET_USE_ANCHORS_FOR_SYMBOL_P: Anchored Addresses. (line 55) ! * TARGET_USE_BLOCKS_FOR_CONSTANT_P: Addressing Modes. (line 251) ! * TARGET_USE_BLOCKS_FOR_DECL_P: Addressing Modes. (line 257) ! * TARGET_USE_BY_PIECES_INFRASTRUCTURE_P: Costs. (line 167) ! * TARGET_USE_JCR_SECTION: Misc. (line 1085) ! * TARGET_USE_PSEUDO_PIC_REG: Register Arguments. (line 89) ! * TARGET_USES_WEAK_UNWIND_INFO: Exception Handling. (line 126) ! * TARGET_VALID_DLLIMPORT_ATTRIBUTE_P: Target Attributes. (line 68) ! * TARGET_VALID_POINTER_MODE: Register Arguments. (line 320) ! * TARGET_VECTOR_ALIGNMENT: Storage Layout. (line 272) ! * TARGET_VECTOR_MODE_SUPPORTED_P: Register Arguments. (line 343) ! * TARGET_VECTORIZE_ADD_STMT_COST: Addressing Modes. (line 381) * TARGET_VECTORIZE_AUTOVECTORIZE_VECTOR_SIZES: Addressing Modes. ! (line 355) ! * TARGET_VECTORIZE_BUILTIN_CONVERSION: Addressing Modes. (line 311) ! * TARGET_VECTORIZE_BUILTIN_GATHER: Addressing Modes. (line 404) ! * TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD: Addressing Modes. (line 268) * TARGET_VECTORIZE_BUILTIN_MD_VECTORIZED_FUNCTION: Addressing Modes. ! (line 331) ! * TARGET_VECTORIZE_BUILTIN_SCATTER: Addressing Modes. (line 411) * TARGET_VECTORIZE_BUILTIN_VECTORIZATION_COST: Addressing Modes. ! (line 295) * TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION: Addressing Modes. ! (line 323) ! * TARGET_VECTORIZE_DESTROY_COST_DATA: Addressing Modes. (line 398) ! * TARGET_VECTORIZE_FINISH_COST: Addressing Modes. (line 392) ! * TARGET_VECTORIZE_GET_MASK_MODE: Addressing Modes. (line 363) ! * TARGET_VECTORIZE_INIT_COST: Addressing Modes. (line 369) ! * TARGET_VECTORIZE_PREFERRED_SIMD_MODE: Addressing Modes. (line 348) * TARGET_VECTORIZE_SUPPORT_VECTOR_MISALIGNMENT: Addressing Modes. ! (line 339) ! * TARGET_VECTORIZE_VEC_PERM_CONST_OK: Addressing Modes. (line 307) * TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE: Addressing Modes. ! (line 301) ! * TARGET_VTABLE_DATA_ENTRY_DISTANCE: Type Layout. (line 311) ! * TARGET_VTABLE_ENTRY_ALIGN: Type Layout. (line 305) ! * TARGET_VTABLE_USES_DESCRIPTORS: Type Layout. (line 294) ! * TARGET_WANT_DEBUG_PUB_SECTIONS: SDB and DWARF. (line 56) ! * TARGET_WARN_FUNC_RETURN: Tail Calls. (line 36) ! * TARGET_WEAK_NOT_IN_ARCHIVE_TOC: Label Output. (line 312) ! * targetm: Target Structure. (line 7) ! * targets, makefile: Makefile. (line 6) ! * TCmode: Machine Modes. (line 200) * TDmode: Machine Modes. (line 97) * TEMPLATE_DECL: Declarations. (line 6) * Temporaries: Temporaries. (line 6) * termination routines: Initialization. (line 6) * testing constraints: C Constraint Interface. (line 6) ! * TEXT_SECTION_ASM_OP: Sections. (line 38) * TFmode: Machine Modes. (line 101) * The Language: The Language. (line 6) * THEN_CLAUSE: Statements for C++. (line 6) ! * THREAD_MODEL_SPEC: Driver. (line 163) * THROW_EXPR: Unary and Binary Expressions. (line 6) * THUNK_DECL: Declarations. (line 6) * THUNK_DELTA: Declarations. (line 6) * TImode: Machine Modes. (line 48) ! * TImode, in insn: Insns. (line 272) ! * TLS_COMMON_ASM_OP: Sections. (line 81) ! * TLS_SECTION_ASM_FLAG: Sections. (line 86) * tm.h macros: Target Macros. (line 6) * TQFmode: Machine Modes. (line 65) * TQmode: Machine Modes. (line 122) + * TRAMPOLINE_ALIGNMENT: Trampolines. (line 49) + * TRAMPOLINE_SECTION: Trampolines. (line 40) + * TRAMPOLINE_SIZE: Trampolines. (line 45) * trampolines for nested functions: Trampolines. (line 6) ! * TRANSFER_FROM_TRAMPOLINE: Trampolines. (line 111) ! * trap instruction pattern: Standard Names. (line 1770) * tree <1>: Macros and Functions. (line 6) + * tree: Tree overview. (line 6) * Tree SSA: Tree SSA. (line 6) * TREE_CHAIN: Macros and Functions. (line 6) *************** Concept Index *** 50845,50853 **** (line 6) * TREE_LIST: Containers. (line 6) * TREE_OPERAND: Expression trees. (line 6) - * TREE_PUBLIC: Function Basics. (line 6) * TREE_PUBLIC <1>: Function Properties. (line 28) * TREE_PURPOSE: Containers. (line 6) * TREE_READONLY: Function Properties. (line 37) --- 51267,51275 ---- (line 6) * TREE_LIST: Containers. (line 6) * TREE_OPERAND: Expression trees. (line 6) * TREE_PUBLIC <1>: Function Properties. (line 28) + * TREE_PUBLIC: Function Basics. (line 6) * TREE_PURPOSE: Containers. (line 6) * TREE_READONLY: Function Properties. (line 37) *************** Concept Index *** 50865,50900 **** (line 6) * tree_to_uhwi: Constant expressions. (line 6) * TREE_TYPE: Macros and Functions. (line 6) - * TREE_TYPE <1>: Types. (line 6) - * TREE_TYPE <2>: Working with declarations. - (line 11) - * TREE_TYPE <3>: Expression trees. (line 6) - * TREE_TYPE <4>: Expression trees. (line 17) - * TREE_TYPE <5>: Function Basics. (line 47) - * TREE_TYPE <6>: Types for C++. (line 6) * TREE_VALUE: Containers. (line 6) * TREE_VEC: Containers. (line 6) * TREE_VEC_ELT: Containers. (line 6) * TREE_VEC_LENGTH: Containers. (line 6) ! * TRULY_NOOP_TRUNCATION: Misc. (line 162) ! * truncate: Conversions. (line 38) ! * truncMN2 instruction pattern: Standard Names. (line 1119) * TRUNC_DIV_EXPR: Unary and Binary Expressions. (line 6) * TRUNC_MOD_EXPR: Unary and Binary Expressions. (line 6) ! * TRUTH_ANDIF_EXPR: Unary and Binary Expressions. ! (line 6) * TRUTH_AND_EXPR: Unary and Binary Expressions. (line 6) ! * TRUTH_NOT_EXPR: Unary and Binary Expressions. (line 6) ! * TRUTH_ORIF_EXPR: Unary and Binary Expressions. (line 6) * TRUTH_OR_EXPR: Unary and Binary Expressions. (line 6) * TRUTH_XOR_EXPR: Unary and Binary Expressions. (line 6) * TRY_BLOCK: Statements for C++. (line 6) --- 51287,51321 ---- (line 6) * tree_to_uhwi: Constant expressions. (line 6) + * TREE_TYPE <1>: Types for C++. (line 6) + * TREE_TYPE <2>: Function Basics. (line 47) + * TREE_TYPE <3>: Expression trees. (line 6) + * TREE_TYPE <4>: Working with declarations. + (line 11) + * TREE_TYPE <5>: Types. (line 6) * TREE_TYPE: Macros and Functions. (line 6) * TREE_VALUE: Containers. (line 6) * TREE_VEC: Containers. (line 6) * TREE_VEC_ELT: Containers. (line 6) * TREE_VEC_LENGTH: Containers. (line 6) ! * TRULY_NOOP_TRUNCATION: Misc. (line 163) * TRUNC_DIV_EXPR: Unary and Binary Expressions. (line 6) * TRUNC_MOD_EXPR: Unary and Binary Expressions. (line 6) ! * truncate: Conversions. (line 38) ! * truncMN2 instruction pattern: Standard Names. (line 1125) * TRUTH_AND_EXPR: Unary and Binary Expressions. (line 6) ! * TRUTH_ANDIF_EXPR: Unary and Binary Expressions. (line 6) ! * TRUTH_NOT_EXPR: Unary and Binary Expressions. (line 6) * TRUTH_OR_EXPR: Unary and Binary Expressions. (line 6) + * TRUTH_ORIF_EXPR: Unary and Binary Expressions. + (line 6) * TRUTH_XOR_EXPR: Unary and Binary Expressions. (line 6) * TRY_BLOCK: Statements for C++. (line 6) *************** Concept Index *** 50906,51023 **** (line 6) * type: Types. (line 6) * type declaration: Declarations. (line 6) ! * TYPENAME_TYPE: Types for C++. (line 6) ! * TYPENAME_TYPE_FULLNAME: Types. (line 6) ! * TYPENAME_TYPE_FULLNAME <1>: Types for C++. (line 6) ! * TYPEOF_TYPE: Types for C++. (line 6) * TYPE_ALIGN: Types. (line 6) - * TYPE_ALIGN <1>: Types. (line 30) - * TYPE_ALIGN <2>: Types for C++. (line 6) - * TYPE_ALIGN <3>: Types for C++. (line 44) - * TYPE_ARG_TYPES: Types. (line 6) * TYPE_ARG_TYPES <1>: Types for C++. (line 6) ! * TYPE_ASM_OP: Label Output. (line 76) ! * TYPE_ATTRIBUTES: Attributes. (line 24) * TYPE_BINFO: Classes. (line 6) ! * TYPE_BUILT_IN: Types for C++. (line 66) * TYPE_CANONICAL: Types. (line 6) - * TYPE_CANONICAL <1>: Types. (line 41) - * TYPE_CONTEXT: Types. (line 6) * TYPE_CONTEXT <1>: Types for C++. (line 6) * TYPE_DECL: Declarations. (line 6) * TYPE_FIELDS: Types. (line 6) - * TYPE_FIELDS <1>: Types for C++. (line 6) - * TYPE_FIELDS <2>: Classes. (line 6) * TYPE_HAS_ARRAY_NEW_OPERATOR: Classes. (line 96) * TYPE_HAS_DEFAULT_CONSTRUCTOR: Classes. (line 81) * TYPE_HAS_MUTABLE_P: Classes. (line 86) * TYPE_HAS_NEW_OPERATOR: Classes. (line 93) * TYPE_MAIN_VARIANT: Types. (line 6) - * TYPE_MAIN_VARIANT <1>: Types. (line 19) - * TYPE_MAIN_VARIANT <2>: Types for C++. (line 6) * TYPE_MAX_VALUE: Types. (line 6) - * TYPE_METHODS: Classes. (line 6) - * TYPE_METHOD_BASETYPE: Types. (line 6) * TYPE_METHOD_BASETYPE <1>: Types for C++. (line 6) * TYPE_MIN_VALUE: Types. (line 6) * TYPE_NAME: Types. (line 6) - * TYPE_NAME <1>: Types. (line 33) - * TYPE_NAME <2>: Types for C++. (line 6) - * TYPE_NAME <3>: Types for C++. (line 47) * TYPE_NOTHROW_P: Functions for C++. (line 154) - * TYPE_OFFSET_BASETYPE: Types. (line 6) * TYPE_OFFSET_BASETYPE <1>: Types for C++. (line 6) ! * TYPE_OPERAND_FMT: Label Output. (line 87) * TYPE_OVERLOADS_ARRAY_REF: Classes. (line 104) * TYPE_OVERLOADS_ARROW: Classes. (line 107) * TYPE_OVERLOADS_CALL_EXPR: Classes. (line 100) * TYPE_POLYMORPHIC_P: Classes. (line 77) - * TYPE_PRECISION: Types. (line 6) * TYPE_PRECISION <1>: Types for C++. (line 6) * TYPE_PTRDATAMEM_P: Types for C++. (line 6) ! * TYPE_PTRDATAMEM_P <1>: Types for C++. (line 69) ! * TYPE_PTRFN_P: Types for C++. (line 76) * TYPE_PTROBV_P: Types for C++. (line 6) - * TYPE_PTROB_P: Types for C++. (line 79) - * TYPE_PTR_P: Types for C++. (line 72) - * TYPE_QUAL_CONST: Types. (line 6) * TYPE_QUAL_CONST <1>: Types for C++. (line 6) ! * TYPE_QUAL_RESTRICT: Types. (line 6) * TYPE_QUAL_RESTRICT <1>: Types for C++. (line 6) ! * TYPE_QUAL_VOLATILE: Types. (line 6) * TYPE_QUAL_VOLATILE <1>: Types for C++. (line 6) * TYPE_RAISES_EXCEPTIONS: Functions for C++. (line 149) * TYPE_SIZE: Types. (line 6) - * TYPE_SIZE <1>: Types. (line 25) - * TYPE_SIZE <2>: Types for C++. (line 6) - * TYPE_SIZE <3>: Types for C++. (line 39) * TYPE_STRUCTURAL_EQUALITY_P: Types. (line 6) - * TYPE_STRUCTURAL_EQUALITY_P <1>: Types. (line 77) - * TYPE_UNQUALIFIED: Types. (line 6) * TYPE_UNQUALIFIED <1>: Types for C++. (line 6) * TYPE_VFIELD: Classes. (line 6) ! * uaddvM4 instruction pattern: Standard Names. (line 320) ! * UDAmode: Machine Modes. (line 170) ! * udiv: Arithmetic. (line 130) ! * udivM3 instruction pattern: Standard Names. (line 301) ! * udivmodM4 instruction pattern: Standard Names. (line 576) ! * udot_prodM instruction pattern: Standard Names. (line 396) ! * UDQmode: Machine Modes. (line 138) ! * UHAmode: Machine Modes. (line 162) ! * UHQmode: Machine Modes. (line 130) ! * UINT16_TYPE: Type Layout. (line 220) ! * UINT32_TYPE: Type Layout. (line 221) ! * UINT64_TYPE: Type Layout. (line 222) ! * UINT8_TYPE: Type Layout. (line 219) ! * UINTMAX_TYPE: Type Layout. (line 203) ! * UINTPTR_TYPE: Type Layout. (line 240) ! * UINT_FAST16_TYPE: Type Layout. (line 236) ! * UINT_FAST32_TYPE: Type Layout. (line 237) ! * UINT_FAST64_TYPE: Type Layout. (line 238) ! * UINT_FAST8_TYPE: Type Layout. (line 235) ! * UINT_LEAST16_TYPE: Type Layout. (line 228) ! * UINT_LEAST32_TYPE: Type Layout. (line 229) ! * UINT_LEAST64_TYPE: Type Layout. (line 230) ! * UINT_LEAST8_TYPE: Type Layout. (line 227) ! * umaddMN4 instruction pattern: Standard Names. (line 523) ! * umax: Arithmetic. (line 149) ! * umaxM3 instruction pattern: Standard Names. (line 301) ! * umin: Arithmetic. (line 149) ! * uminM3 instruction pattern: Standard Names. (line 301) ! * umod: Arithmetic. (line 136) ! * umodM3 instruction pattern: Standard Names. (line 301) ! * umsubMN4 instruction pattern: Standard Names. (line 547) ! * umulhisi3 instruction pattern: Standard Names. (line 495) ! * umulM3_highpart instruction pattern: Standard Names. (line 509) ! * umulqihi3 instruction pattern: Standard Names. (line 495) ! * umulsidi3 instruction pattern: Standard Names. (line 495) ! * umulvM4 instruction pattern: Standard Names. (line 325) * unchanging: Flags. (line 296) * unchanging, in call_insn: Flags. (line 19) * unchanging, in jump_insn, call_insn and insn: Flags. (line 39) * unchanging, in mem: Flags. (line 134) * unchanging, in subreg: Flags. (line 170) - * unchanging, in subreg <1>: Flags. (line 180) * unchanging, in symbol_ref: Flags. (line 10) * UNEQ_EXPR: Unary and Binary Expressions. (line 6) --- 51327,51433 ---- (line 6) * type: Types. (line 6) * type declaration: Declarations. (line 6) ! * TYPE_ALIGN <1>: Types for C++. (line 6) * TYPE_ALIGN: Types. (line 6) * TYPE_ARG_TYPES <1>: Types for C++. (line 6) ! * TYPE_ARG_TYPES: Types. (line 6) ! * TYPE_ASM_OP: Label Output. (line 79) ! * TYPE_ATTRIBUTES: Attributes. (line 25) * TYPE_BINFO: Classes. (line 6) ! * TYPE_BUILT_IN: Types for C++. (line 68) * TYPE_CANONICAL: Types. (line 6) * TYPE_CONTEXT <1>: Types for C++. (line 6) + * TYPE_CONTEXT: Types. (line 6) * TYPE_DECL: Declarations. (line 6) + * TYPE_FIELDS <1>: Classes. (line 6) + * TYPE_FIELDS <2>: Types for C++. (line 6) * TYPE_FIELDS: Types. (line 6) * TYPE_HAS_ARRAY_NEW_OPERATOR: Classes. (line 96) * TYPE_HAS_DEFAULT_CONSTRUCTOR: Classes. (line 81) * TYPE_HAS_MUTABLE_P: Classes. (line 86) * TYPE_HAS_NEW_OPERATOR: Classes. (line 93) + * TYPE_MAIN_VARIANT <1>: Types for C++. (line 6) * TYPE_MAIN_VARIANT: Types. (line 6) * TYPE_MAX_VALUE: Types. (line 6) * TYPE_METHOD_BASETYPE <1>: Types for C++. (line 6) + * TYPE_METHOD_BASETYPE: Types. (line 6) + * TYPE_METHODS: Classes. (line 6) * TYPE_MIN_VALUE: Types. (line 6) + * TYPE_NAME <1>: Types for C++. (line 6) * TYPE_NAME: Types. (line 6) * TYPE_NOTHROW_P: Functions for C++. (line 154) * TYPE_OFFSET_BASETYPE <1>: Types for C++. (line 6) ! * TYPE_OFFSET_BASETYPE: Types. (line 6) ! * TYPE_OPERAND_FMT: Label Output. (line 90) * TYPE_OVERLOADS_ARRAY_REF: Classes. (line 104) * TYPE_OVERLOADS_ARROW: Classes. (line 107) * TYPE_OVERLOADS_CALL_EXPR: Classes. (line 100) * TYPE_POLYMORPHIC_P: Classes. (line 77) * TYPE_PRECISION <1>: Types for C++. (line 6) + * TYPE_PRECISION: Types. (line 6) + * TYPE_PTR_P: Types for C++. (line 74) * TYPE_PTRDATAMEM_P: Types for C++. (line 6) ! * TYPE_PTRFN_P: Types for C++. (line 78) ! * TYPE_PTROB_P: Types for C++. (line 81) * TYPE_PTROBV_P: Types for C++. (line 6) * TYPE_QUAL_CONST <1>: Types for C++. (line 6) ! * TYPE_QUAL_CONST: Types. (line 6) * TYPE_QUAL_RESTRICT <1>: Types for C++. (line 6) ! * TYPE_QUAL_RESTRICT: Types. (line 6) * TYPE_QUAL_VOLATILE <1>: Types for C++. (line 6) + * TYPE_QUAL_VOLATILE: Types. (line 6) * TYPE_RAISES_EXCEPTIONS: Functions for C++. (line 149) + * TYPE_SIZE <1>: Types for C++. (line 6) * TYPE_SIZE: Types. (line 6) * TYPE_STRUCTURAL_EQUALITY_P: Types. (line 6) * TYPE_UNQUALIFIED <1>: Types for C++. (line 6) + * TYPE_UNQUALIFIED: Types. (line 6) * TYPE_VFIELD: Classes. (line 6) ! * TYPENAME_TYPE: Types for C++. (line 6) ! * TYPENAME_TYPE_FULLNAME <1>: Types for C++. (line 6) ! * TYPENAME_TYPE_FULLNAME: Types. (line 6) ! * TYPEOF_TYPE: Types for C++. (line 6) ! * uaddvM4 instruction pattern: Standard Names. (line 324) ! * UDAmode: Machine Modes. (line 171) ! * udiv: Arithmetic. (line 129) ! * udivM3 instruction pattern: Standard Names. (line 305) ! * udivmodM4 instruction pattern: Standard Names. (line 582) ! * udot_prodM instruction pattern: Standard Names. (line 400) ! * UDQmode: Machine Modes. (line 139) ! * UHAmode: Machine Modes. (line 163) ! * UHQmode: Machine Modes. (line 131) ! * UINT16_TYPE: Type Layout. (line 221) ! * UINT32_TYPE: Type Layout. (line 222) ! * UINT64_TYPE: Type Layout. (line 223) ! * UINT8_TYPE: Type Layout. (line 220) ! * UINT_FAST16_TYPE: Type Layout. (line 237) ! * UINT_FAST32_TYPE: Type Layout. (line 238) ! * UINT_FAST64_TYPE: Type Layout. (line 239) ! * UINT_FAST8_TYPE: Type Layout. (line 236) ! * UINT_LEAST16_TYPE: Type Layout. (line 229) ! * UINT_LEAST32_TYPE: Type Layout. (line 230) ! * UINT_LEAST64_TYPE: Type Layout. (line 231) ! * UINT_LEAST8_TYPE: Type Layout. (line 228) ! * UINTMAX_TYPE: Type Layout. (line 204) ! * UINTPTR_TYPE: Type Layout. (line 241) ! * umaddMN4 instruction pattern: Standard Names. (line 529) ! * umax: Arithmetic. (line 148) ! * umaxM3 instruction pattern: Standard Names. (line 305) ! * umin: Arithmetic. (line 148) ! * uminM3 instruction pattern: Standard Names. (line 305) ! * umod: Arithmetic. (line 135) ! * umodM3 instruction pattern: Standard Names. (line 305) ! * umsubMN4 instruction pattern: Standard Names. (line 553) ! * umulhisi3 instruction pattern: Standard Names. (line 501) ! * umulM3_highpart instruction pattern: Standard Names. (line 515) ! * umulqihi3 instruction pattern: Standard Names. (line 501) ! * umulsidi3 instruction pattern: Standard Names. (line 501) ! * umulvM4 instruction pattern: Standard Names. (line 329) * unchanging: Flags. (line 296) * unchanging, in call_insn: Flags. (line 19) * unchanging, in jump_insn, call_insn and insn: Flags. (line 39) * unchanging, in mem: Flags. (line 134) * unchanging, in subreg: Flags. (line 170) * unchanging, in symbol_ref: Flags. (line 10) * UNEQ_EXPR: Unary and Binary Expressions. (line 6) *************** Concept Index *** 51025,51194 **** (line 6) * UNGT_EXPR: Unary and Binary Expressions. (line 6) - * unions, returning: Interface. (line 10) - * UNION_TYPE: Types. (line 6) * UNION_TYPE <1>: Classes. (line 6) ! * UNITS_PER_WORD: Storage Layout. (line 60) ! * UNKNOWN_TYPE: Types. (line 6) * UNKNOWN_TYPE <1>: Types for C++. (line 6) * UNLE_EXPR: Unary and Binary Expressions. (line 6) ! * UNLIKELY_EXECUTED_TEXT_SECTION_NAME: Sections. (line 48) * UNLT_EXPR: Unary and Binary Expressions. (line 6) * UNORDERED_EXPR: Unary and Binary Expressions. (line 6) * unshare_all_rtl: Sharing. (line 58) ! * unsigned division: Arithmetic. (line 130) ! * unsigned division with unsigned saturation: Arithmetic. (line 130) * unsigned greater than: Comparisons. (line 64) - * unsigned greater than <1>: Comparisons. (line 72) * unsigned less than: Comparisons. (line 68) ! * unsigned less than <1>: Comparisons. (line 76) ! * unsigned minimum and maximum: Arithmetic. (line 149) * unsigned_fix: Conversions. (line 77) * unsigned_float: Conversions. (line 62) * unsigned_fract_convert: Conversions. (line 97) * unsigned_sat_fract: Conversions. (line 103) - * unspec: Side Effects. (line 299) * unspec <1>: Constant Definitions. (line 111) ! * unspec_volatile: Side Effects. (line 299) * unspec_volatile <1>: Constant Definitions. (line 99) ! * untyped_call instruction pattern: Standard Names. (line 1375) ! * untyped_return instruction pattern: Standard Names. (line 1438) * UPDATE_PATH_HOST_CANONICALIZE (PATH): Filesystem. (line 59) * update_ssa: SSA. (line 74) - * update_stmt: Manipulating GIMPLE statements. - (line 140) * update_stmt <1>: SSA Operands. (line 6) * update_stmt_if_modified: Manipulating GIMPLE statements. ! (line 143) * UQQmode: Machine Modes. (line 126) ! * usaddM3 instruction pattern: Standard Names. (line 301) ! * usadM instruction pattern: Standard Names. (line 405) ! * USAmode: Machine Modes. (line 166) ! * usashlM3 instruction pattern: Standard Names. (line 579) ! * usdivM3 instruction pattern: Standard Names. (line 301) * use: Side Effects. (line 168) * used: Flags. (line 314) * used, in symbol_ref: Flags. (line 197) ! * user: GTY Options. (line 243) * user gc: User GC. (line 6) ! * USER_LABEL_PREFIX: Instruction Output. (line 152) ! * USE_C_ALLOCA: Host Misc. (line 19) ! * USE_LD_AS_NEEDED: Driver. (line 135) ! * USE_LOAD_POST_DECREMENT: Costs. (line 233) ! * USE_LOAD_POST_INCREMENT: Costs. (line 228) ! * USE_LOAD_PRE_DECREMENT: Costs. (line 243) ! * USE_LOAD_PRE_INCREMENT: Costs. (line 238) ! * USE_SELECT_SECTION_FOR_FUNCTIONS: Sections. (line 193) ! * USE_STORE_POST_DECREMENT: Costs. (line 253) ! * USE_STORE_POST_INCREMENT: Costs. (line 248) ! * USE_STORE_PRE_DECREMENT: Costs. (line 263) ! * USE_STORE_PRE_INCREMENT: Costs. (line 258) * USING_STMT: Statements for C++. (line 6) ! * usmaddMN4 instruction pattern: Standard Names. (line 531) ! * usmsubMN4 instruction pattern: Standard Names. (line 555) ! * usmulhisi3 instruction pattern: Standard Names. (line 499) ! * usmulM3 instruction pattern: Standard Names. (line 301) ! * usmulqihi3 instruction pattern: Standard Names. (line 499) ! * usmulsidi3 instruction pattern: Standard Names. (line 499) ! * usnegM2 instruction pattern: Standard Names. (line 603) ! * USQmode: Machine Modes. (line 134) ! * ussubM3 instruction pattern: Standard Names. (line 301) ! * usubvM4 instruction pattern: Standard Names. (line 325) ! * us_ashift: Arithmetic. (line 173) ! * us_minus: Arithmetic. (line 38) ! * us_mult: Arithmetic. (line 93) ! * us_neg: Arithmetic. (line 82) ! * us_plus: Arithmetic. (line 14) ! * us_truncate: Conversions. (line 48) ! * UTAmode: Machine Modes. (line 174) ! * UTQmode: Machine Modes. (line 142) * V in constraint: Simple Constraints. (line 43) * values, returned by functions: Scalar Return. (line 6) * varargs implementation: Varargs. (line 6) * variable: Declarations. (line 6) * Variable Location Debug Information in RTL: Debug Information. (line 6) ! * VAR_DECL: Declarations. (line 6) ! * var_location: Debug Information. (line 14) ! * vashlM3 instruction pattern: Standard Names. (line 595) ! * vashrM3 instruction pattern: Standard Names. (line 595) ! * VA_ARG_EXPR: Unary and Binary Expressions. ! (line 6) ! * vcondMN instruction pattern: Standard Names. (line 227) ! * vconduMN instruction pattern: Standard Names. (line 237) ! * vcond_mask_MN instruction pattern: Standard Names. (line 240) ! * vector: Containers. (line 6) ! * vector operations: Vector Operations. (line 6) ! * VECTOR_CST: Constant expressions. ! (line 6) ! * VECTOR_STORE_FLAG_VALUE: Misc. (line 293) ! * vec_cmpMN instruction pattern: Standard Names. (line 217) ! * vec_cmpuMN instruction pattern: Standard Names. (line 224) * vec_concat: Vector Operations. (line 28) * vec_duplicate: Vector Operations. (line 33) ! * vec_extractM instruction pattern: Standard Names. (line 207) ! * vec_initM instruction pattern: Standard Names. (line 212) ! * vec_load_lanesMN instruction pattern: Standard Names. (line 165) * VEC_LSHIFT_EXPR: Vectors. (line 6) * vec_merge: Vector Operations. (line 11) * VEC_PACK_FIX_TRUNC_EXPR: Vectors. (line 6) * VEC_PACK_SAT_EXPR: Vectors. (line 6) ! * vec_pack_sfix_trunc_M instruction pattern: Standard Names. (line 440) ! * vec_pack_ssat_M instruction pattern: Standard Names. (line 433) * VEC_PACK_TRUNC_EXPR: Vectors. (line 6) ! * vec_pack_trunc_M instruction pattern: Standard Names. (line 426) ! * vec_pack_ufix_trunc_M instruction pattern: Standard Names. (line 440) ! * vec_pack_usat_M instruction pattern: Standard Names. (line 433) ! * vec_permM instruction pattern: Standard Names. (line 258) ! * vec_perm_constM instruction pattern: Standard Names. (line 274) * VEC_RSHIFT_EXPR: Vectors. (line 6) * vec_select: Vector Operations. (line 19) ! * vec_setM instruction pattern: Standard Names. (line 202) ! * vec_shr_M instruction pattern: Standard Names. (line 420) ! * vec_store_lanesMN instruction pattern: Standard Names. (line 189) ! * vec_unpacks_float_hi_M instruction pattern: Standard Names. ! (line 461) ! * vec_unpacks_float_lo_M instruction pattern: Standard Names. ! (line 461) ! * vec_unpacks_hi_M instruction pattern: Standard Names. (line 447) ! * vec_unpacks_lo_M instruction pattern: Standard Names. (line 447) ! * vec_unpacku_float_hi_M instruction pattern: Standard Names. ! (line 461) ! * vec_unpacku_float_lo_M instruction pattern: Standard Names. ! (line 461) ! * vec_unpacku_hi_M instruction pattern: Standard Names. (line 454) ! * vec_unpacku_lo_M instruction pattern: Standard Names. (line 454) * VEC_UNPACK_FLOAT_HI_EXPR: Vectors. (line 6) * VEC_UNPACK_FLOAT_LO_EXPR: Vectors. (line 6) * VEC_UNPACK_HI_EXPR: Vectors. (line 6) * VEC_UNPACK_LO_EXPR: Vectors. (line 6) * VEC_WIDEN_MULT_HI_EXPR: Vectors. (line 6) * VEC_WIDEN_MULT_LO_EXPR: Vectors. (line 6) * vec_widen_smult_even_M instruction pattern: Standard Names. ! (line 470) ! * vec_widen_smult_hi_M instruction pattern: Standard Names. (line 470) ! * vec_widen_smult_lo_M instruction pattern: Standard Names. (line 470) ! * vec_widen_smult_odd_M instruction pattern: Standard Names. (line 470) * vec_widen_sshiftl_hi_M instruction pattern: Standard Names. ! (line 481) * vec_widen_sshiftl_lo_M instruction pattern: Standard Names. ! (line 481) * vec_widen_umult_even_M instruction pattern: Standard Names. ! (line 470) ! * vec_widen_umult_hi_M instruction pattern: Standard Names. (line 470) ! * vec_widen_umult_lo_M instruction pattern: Standard Names. (line 470) ! * vec_widen_umult_odd_M instruction pattern: Standard Names. (line 470) * vec_widen_ushiftl_hi_M instruction pattern: Standard Names. ! (line 481) * vec_widen_ushiftl_lo_M instruction pattern: Standard Names. ! (line 481) * verify_flow_info: Maintaining the CFG. ! (line 117) * virtual operands: SSA Operands. (line 6) * VIRTUAL_INCOMING_ARGS_REGNUM: Regs and Memory. (line 59) * VIRTUAL_OUTGOING_ARGS_REGNUM: Regs and Memory. (line 87) --- 51435,51602 ---- (line 6) * UNGT_EXPR: Unary and Binary Expressions. (line 6) * UNION_TYPE <1>: Classes. (line 6) ! * UNION_TYPE: Types. (line 6) ! * unions, returning: Interface. (line 10) ! * UNITS_PER_WORD: Storage Layout. (line 61) * UNKNOWN_TYPE <1>: Types for C++. (line 6) + * UNKNOWN_TYPE: Types. (line 6) * UNLE_EXPR: Unary and Binary Expressions. (line 6) ! * UNLIKELY_EXECUTED_TEXT_SECTION_NAME: Sections. (line 49) * UNLT_EXPR: Unary and Binary Expressions. (line 6) * UNORDERED_EXPR: Unary and Binary Expressions. (line 6) * unshare_all_rtl: Sharing. (line 58) ! * unsigned division: Arithmetic. (line 129) ! * unsigned division with unsigned saturation: Arithmetic. (line 129) * unsigned greater than: Comparisons. (line 64) * unsigned less than: Comparisons. (line 68) ! * unsigned minimum and maximum: Arithmetic. (line 148) * unsigned_fix: Conversions. (line 77) * unsigned_float: Conversions. (line 62) * unsigned_fract_convert: Conversions. (line 97) * unsigned_sat_fract: Conversions. (line 103) * unspec <1>: Constant Definitions. (line 111) ! * unspec: Side Effects. (line 300) * unspec_volatile <1>: Constant Definitions. (line 99) ! * unspec_volatile: Side Effects. (line 300) ! * untyped_call instruction pattern: Standard Names. (line 1381) ! * untyped_return instruction pattern: Standard Names. (line 1445) * UPDATE_PATH_HOST_CANONICALIZE (PATH): Filesystem. (line 59) * update_ssa: SSA. (line 74) * update_stmt <1>: SSA Operands. (line 6) + * update_stmt: Manipulating GIMPLE statements. + (line 141) * update_stmt_if_modified: Manipulating GIMPLE statements. ! (line 144) * UQQmode: Machine Modes. (line 126) ! * us_ashift: Arithmetic. (line 172) ! * us_minus: Arithmetic. (line 36) ! * us_mult: Arithmetic. (line 92) ! * us_neg: Arithmetic. (line 81) ! * us_plus: Arithmetic. (line 14) ! * us_truncate: Conversions. (line 48) ! * usaddM3 instruction pattern: Standard Names. (line 305) ! * usadM instruction pattern: Standard Names. (line 409) ! * USAmode: Machine Modes. (line 167) ! * usashlM3 instruction pattern: Standard Names. (line 585) ! * usdivM3 instruction pattern: Standard Names. (line 305) * use: Side Effects. (line 168) + * USE_C_ALLOCA: Host Misc. (line 19) + * USE_LD_AS_NEEDED: Driver. (line 136) + * USE_LOAD_POST_DECREMENT: Costs. (line 234) + * USE_LOAD_POST_INCREMENT: Costs. (line 229) + * USE_LOAD_PRE_DECREMENT: Costs. (line 244) + * USE_LOAD_PRE_INCREMENT: Costs. (line 239) + * USE_SELECT_SECTION_FOR_FUNCTIONS: Sections. (line 194) + * USE_STORE_POST_DECREMENT: Costs. (line 254) + * USE_STORE_POST_INCREMENT: Costs. (line 249) + * USE_STORE_PRE_DECREMENT: Costs. (line 264) + * USE_STORE_PRE_INCREMENT: Costs. (line 259) * used: Flags. (line 314) * used, in symbol_ref: Flags. (line 197) ! * user: GTY Options. (line 235) * user gc: User GC. (line 6) ! * USER_LABEL_PREFIX: Instruction Output. (line 154) * USING_STMT: Statements for C++. (line 6) ! * usmaddMN4 instruction pattern: Standard Names. (line 537) ! * usmsubMN4 instruction pattern: Standard Names. (line 561) ! * usmulhisi3 instruction pattern: Standard Names. (line 505) ! * usmulM3 instruction pattern: Standard Names. (line 305) ! * usmulqihi3 instruction pattern: Standard Names. (line 505) ! * usmulsidi3 instruction pattern: Standard Names. (line 505) ! * usnegM2 instruction pattern: Standard Names. (line 609) ! * USQmode: Machine Modes. (line 135) ! * ussubM3 instruction pattern: Standard Names. (line 305) ! * usubvM4 instruction pattern: Standard Names. (line 329) ! * UTAmode: Machine Modes. (line 175) ! * UTQmode: Machine Modes. (line 143) * V in constraint: Simple Constraints. (line 43) + * VA_ARG_EXPR: Unary and Binary Expressions. + (line 6) * values, returned by functions: Scalar Return. (line 6) + * VAR_DECL: Declarations. (line 6) + * var_location: Debug Information. (line 14) * varargs implementation: Varargs. (line 6) * variable: Declarations. (line 6) * Variable Location Debug Information in RTL: Debug Information. (line 6) ! * vashlM3 instruction pattern: Standard Names. (line 601) ! * vashrM3 instruction pattern: Standard Names. (line 601) ! * vcond_mask_MN instruction pattern: Standard Names. (line 242) ! * vcondMN instruction pattern: Standard Names. (line 228) ! * vconduMN instruction pattern: Standard Names. (line 239) ! * vec_cmpMN instruction pattern: Standard Names. (line 218) ! * vec_cmpuMN instruction pattern: Standard Names. (line 225) * vec_concat: Vector Operations. (line 28) * vec_duplicate: Vector Operations. (line 33) ! * vec_extractM instruction pattern: Standard Names. (line 208) ! * vec_initM instruction pattern: Standard Names. (line 213) ! * vec_load_lanesMN instruction pattern: Standard Names. (line 166) * VEC_LSHIFT_EXPR: Vectors. (line 6) * vec_merge: Vector Operations. (line 11) * VEC_PACK_FIX_TRUNC_EXPR: Vectors. (line 6) * VEC_PACK_SAT_EXPR: Vectors. (line 6) ! * vec_pack_sfix_trunc_M instruction pattern: Standard Names. (line 445) ! * vec_pack_ssat_M instruction pattern: Standard Names. (line 438) * VEC_PACK_TRUNC_EXPR: Vectors. (line 6) ! * vec_pack_trunc_M instruction pattern: Standard Names. (line 431) ! * vec_pack_ufix_trunc_M instruction pattern: Standard Names. (line 445) ! * vec_pack_usat_M instruction pattern: Standard Names. (line 438) ! * vec_perm_constM instruction pattern: Standard Names. (line 278) ! * vec_permM instruction pattern: Standard Names. (line 260) * VEC_RSHIFT_EXPR: Vectors. (line 6) * vec_select: Vector Operations. (line 19) ! * vec_setM instruction pattern: Standard Names. (line 203) ! * vec_shr_M instruction pattern: Standard Names. (line 425) ! * vec_store_lanesMN instruction pattern: Standard Names. (line 190) * VEC_UNPACK_FLOAT_HI_EXPR: Vectors. (line 6) * VEC_UNPACK_FLOAT_LO_EXPR: Vectors. (line 6) * VEC_UNPACK_HI_EXPR: Vectors. (line 6) * VEC_UNPACK_LO_EXPR: Vectors. (line 6) + * vec_unpacks_float_hi_M instruction pattern: Standard Names. + (line 467) + * vec_unpacks_float_lo_M instruction pattern: Standard Names. + (line 467) + * vec_unpacks_hi_M instruction pattern: Standard Names. (line 452) + * vec_unpacks_lo_M instruction pattern: Standard Names. (line 452) + * vec_unpacku_float_hi_M instruction pattern: Standard Names. + (line 467) + * vec_unpacku_float_lo_M instruction pattern: Standard Names. + (line 467) + * vec_unpacku_hi_M instruction pattern: Standard Names. (line 460) + * vec_unpacku_lo_M instruction pattern: Standard Names. (line 460) * VEC_WIDEN_MULT_HI_EXPR: Vectors. (line 6) * VEC_WIDEN_MULT_LO_EXPR: Vectors. (line 6) * vec_widen_smult_even_M instruction pattern: Standard Names. ! (line 476) ! * vec_widen_smult_hi_M instruction pattern: Standard Names. (line 476) ! * vec_widen_smult_lo_M instruction pattern: Standard Names. (line 476) ! * vec_widen_smult_odd_M instruction pattern: Standard Names. (line 476) * vec_widen_sshiftl_hi_M instruction pattern: Standard Names. ! (line 487) * vec_widen_sshiftl_lo_M instruction pattern: Standard Names. ! (line 487) * vec_widen_umult_even_M instruction pattern: Standard Names. ! (line 476) ! * vec_widen_umult_hi_M instruction pattern: Standard Names. (line 476) ! * vec_widen_umult_lo_M instruction pattern: Standard Names. (line 476) ! * vec_widen_umult_odd_M instruction pattern: Standard Names. (line 476) * vec_widen_ushiftl_hi_M instruction pattern: Standard Names. ! (line 487) * vec_widen_ushiftl_lo_M instruction pattern: Standard Names. ! (line 487) ! * vector: Containers. (line 6) ! * vector operations: Vector Operations. (line 6) ! * VECTOR_CST: Constant expressions. ! (line 6) ! * VECTOR_STORE_FLAG_VALUE: Misc. (line 294) * verify_flow_info: Maintaining the CFG. ! (line 119) * virtual operands: SSA Operands. (line 6) * VIRTUAL_INCOMING_ARGS_REGNUM: Regs and Memory. (line 59) * VIRTUAL_OUTGOING_ARGS_REGNUM: Regs and Memory. (line 87) *************** Concept Index *** 51196,51210 **** * VIRTUAL_STACK_VARS_REGNUM: Regs and Memory. (line 69) * VLIW: Processor pipeline description. (line 6) ! * VLIW <1>: Processor pipeline description. ! (line 223) ! * vlshrM3 instruction pattern: Standard Names. (line 595) * VMS: Filesystem. (line 37) ! * VMS_DEBUGGING_INFO: VMS Debug. (line 8) ! * void: Misc. (line 686) ! * void <1>: Misc. (line 691) ! * VOIDmode: Machine Modes. (line 192) * VOID_TYPE: Types. (line 6) * volatil: Flags. (line 328) * volatil, in insn, call_insn, jump_insn, code_label, jump_table_data, barrier, and note: Flags. (line 44) --- 51604,51615 ---- * VIRTUAL_STACK_VARS_REGNUM: Regs and Memory. (line 69) * VLIW: Processor pipeline description. (line 6) ! * vlshrM3 instruction pattern: Standard Names. (line 601) * VMS: Filesystem. (line 37) ! * VMS_DEBUGGING_INFO: VMS Debug. (line 9) ! * void: Misc. (line 688) * VOID_TYPE: Types. (line 6) + * VOIDmode: Machine Modes. (line 193) * volatil: Flags. (line 328) * volatil, in insn, call_insn, jump_insn, code_label, jump_table_data, barrier, and note: Flags. (line 44) *************** Concept Index *** 51212,51659 **** * volatil, in mem, asm_operands, and asm_input: Flags. (line 76) * volatil, in reg: Flags. (line 98) * volatil, in subreg: Flags. (line 170) - * volatil, in subreg <1>: Flags. (line 180) * volatil, in symbol_ref: Flags. (line 206) * volatile memory references: Flags. (line 329) * volatile, in prefetch: Flags. (line 214) * voting between constraint alternatives: Class Preferences. (line 6) ! * vrotlM3 instruction pattern: Standard Names. (line 595) ! * vrotrM3 instruction pattern: Standard Names. (line 595) ! * walk_dominator_tree: SSA. (line 195) * walk_gimple_op: Statement and operand traversals. ! (line 30) * walk_gimple_seq: Statement and operand traversals. ! (line 47) * walk_gimple_stmt: Statement and operand traversals. ! (line 10) ! * WCHAR_TYPE: Type Layout. (line 171) ! * WCHAR_TYPE_SIZE: Type Layout. (line 179) ! * which_alternative: Output Statement. (line 58) * WHILE_BODY: Statements for C++. (line 6) * WHILE_COND: Statements for C++. (line 6) * WHILE_STMT: Statements for C++. (line 6) * whopr: LTO. (line 6) ! * widen_ssumM3 instruction pattern: Standard Names. (line 413) ! * widen_usumM3 instruction pattern: Standard Names. (line 414) ! * WIDEST_HARDWARE_FP_SIZE: Type Layout. (line 116) ! * window_save instruction pattern: Standard Names. (line 1730) ! * WINT_TYPE: Type Layout. (line 184) ! * WORDS_BIG_ENDIAN: Storage Layout. (line 28) ! * WORDS_BIG_ENDIAN, effect on subreg: Regs and Memory. (line 215) ! * word_mode: Machine Modes. (line 367) ! * WORD_REGISTER_OPERATIONS: Misc. (line 53) * wpa: LTO. (line 6) ! * X in constraint: Simple Constraints. (line 122) * x-HOST: Host Fragment. (line 6) ! * XCmode: Machine Modes. (line 199) ! * XCOFF_DEBUGGING_INFO: DBX Options. (line 12) * XEXP: Accessors. (line 6) * XFmode: Machine Modes. (line 82) * XImode: Machine Modes. (line 54) * XINT: Accessors. (line 6) - * xm-MACHINE.h: Filesystem. (line 6) * xm-MACHINE.h <1>: Host Misc. (line 6) ! * xor: Arithmetic. (line 168) * xor, canonicalization of: Insn Canonicalizations. ! (line 78) ! * xorM3 instruction pattern: Standard Names. (line 301) * XSTR: Accessors. (line 6) * XVEC: Accessors. (line 41) * XVECEXP: Accessors. (line 48) * XVECLEN: Accessors. (line 44) * XWINT: Accessors. (line 6) * zero_extend: Conversions. (line 28) ! * zero_extendMN2 instruction pattern: Standard Names. (line 1129) * zero_extract: Bit-Fields. (line 30) * zero_extract, canonicalization of: Insn Canonicalizations. ! (line 87)  Tag Table: ! Node: Top1789 ! Node: Contributing4971 ! Node: Portability5700 ! Node: Interface7488 ! Node: Libgcc10529 ! Node: Integer library routines12356 ! Node: Soft float library routines19324 ! Node: Decimal float library routines31262 ! Node: Fixed-point fractional library routines47020 ! Node: Exception handling routines147416 ! Node: Miscellaneous routines148523 ! Node: Languages150643 ! Node: Source Tree152190 ! Node: Configure Terms152772 ! Node: Top Level155728 ! Node: gcc Directory159215 ! Node: Subdirectories160167 ! Node: Configuration162335 ! Node: Config Fragments163055 ! Node: System Config164280 ! Node: Configuration Files165216 ! Node: Build168033 ! Node: Makefile168445 ! Ref: Makefile-Footnote-1175249 ! Ref: Makefile-Footnote-2175396 ! Node: Library Files175470 ! Node: Headers176032 ! Node: Documentation178115 ! Node: Texinfo Manuals178974 ! Node: Man Page Generation181303 ! Node: Miscellaneous Docs183216 ! Node: Front End184603 ! Node: Front End Directory188277 ! Node: Front End Config189593 ! Node: Front End Makefile192409 ! Node: Back End196177 ! Node: Testsuites199958 ! Node: Test Idioms200889 ! Node: Test Directives204287 ! Node: Directives204814 ! Node: Selectors215111 ! Node: Effective-Target Keywords216467 ! Ref: arm_fp_ok223643 ! Ref: arm_neon_ok224572 ! Ref: arm_neonv2_ok224730 ! Ref: arm_neon_fp16_ok224902 ! Ref: arm_vfp3_ok225542 ! Node: Add Options237375 ! Node: Require Support238878 ! Node: Final Actions241385 ! Node: Ada Tests247044 ! Node: C Tests248375 ! Node: libgcj Tests252770 ! Node: LTO Testing253897 ! Node: gcov Testing255545 ! Node: profopt Testing258535 ! Node: compat Testing260250 ! Node: Torture Tests264490 ! Node: Options266105 ! Node: Option file format266546 ! Node: Option properties273535 ! Node: Passes287181 ! Node: Parsing pass288071 ! Node: Cilk Plus Transformation291604 ! Node: Gimplification pass294986 ! Node: Pass manager296831 ! Node: Tree SSA passes298677 ! Node: RTL passes319862 ! Node: Optimization info332166 ! Node: Dump setup332985 ! Node: Optimization groups334114 ! Node: Dump files and streams335003 ! Node: Dump output verbosity336201 ! Node: Dump types337257 ! Node: Dump examples338747 ! Node: GENERIC340093 ! Node: Deficiencies341969 ! Node: Tree overview342210 ! Node: Macros and Functions346334 ! Node: Identifiers347159 ! Node: Containers348768 ! Node: Types349925 ! Node: Declarations361999 ! Node: Working with declarations362494 ! Node: Internal structure368098 ! Node: Current structure hierarchy368482 ! Node: Adding new DECL node types370575 ! Node: Attributes374859 ! Node: Expression trees376103 ! Node: Constant expressions377857 ! Node: Storage References381153 ! Node: Unary and Binary Expressions384672 ! Node: Vectors404820 ! Node: Statements410015 ! Node: Basic Statements410547 ! Node: Blocks415054 ! Node: Statement Sequences416755 ! Node: Empty Statements417088 ! Node: Jumps417662 ! Node: Cleanups418315 ! Node: OpenMP420082 ! Node: OpenACC425927 ! Node: Functions426968 ! Node: Function Basics427439 ! Node: Function Properties431123 ! Node: Language-dependent trees433904 ! Node: C and C++ Trees434791 ! Node: Types for C++437695 ! Node: Namespaces442665 ! Node: Classes445771 ! Node: Functions for C++450828 ! Node: Statements for C++457079 ! Node: C++ Expressions465852 ! Node: Java Trees467357 ! Node: GIMPLE467470 ! Node: Tuple representation471135 ! Node: Class hierarchy of GIMPLE statements478095 ! Node: GIMPLE instruction set483083 ! Node: GIMPLE Exception Handling484715 ! Node: Temporaries486627 ! Ref: Temporaries-Footnote-1487945 ! Node: Operands488010 ! Node: Compound Expressions488771 ! Node: Compound Lvalues489005 ! Node: Conditional Expressions489767 ! Node: Logical Operators490426 ! Node: Manipulating GIMPLE statements497290 ! Node: Tuple specific accessors503226 ! Node: GIMPLE_ASM504005 ! Node: GIMPLE_ASSIGN506388 ! Node: GIMPLE_BIND511092 ! Node: GIMPLE_CALL512906 ! Node: GIMPLE_CATCH516934 ! Node: GIMPLE_COND518084 ! Node: GIMPLE_DEBUG520879 ! Node: GIMPLE_EH_FILTER524252 ! Node: GIMPLE_LABEL525815 ! Node: GIMPLE_GOTO526428 ! Node: GIMPLE_NOP526951 ! Node: GIMPLE_OMP_ATOMIC_LOAD527313 ! Node: GIMPLE_OMP_ATOMIC_STORE528309 ! Node: GIMPLE_OMP_CONTINUE529008 ! Node: GIMPLE_OMP_CRITICAL530487 ! Node: GIMPLE_OMP_FOR531481 ! Node: GIMPLE_OMP_MASTER534897 ! Node: GIMPLE_OMP_ORDERED535275 ! Node: GIMPLE_OMP_PARALLEL535669 ! Node: GIMPLE_OMP_RETURN538438 ! Node: GIMPLE_OMP_SECTION539083 ! Node: GIMPLE_OMP_SECTIONS539743 ! Node: GIMPLE_OMP_SINGLE541353 ! Node: GIMPLE_PHI542299 ! Node: GIMPLE_RESX543578 ! Node: GIMPLE_RETURN544297 ! Node: GIMPLE_SWITCH544871 ! Node: GIMPLE_TRY546746 ! Node: GIMPLE_WITH_CLEANUP_EXPR548518 ! Node: GIMPLE sequences549397 ! Node: Sequence iterators552603 ! Node: Adding a new GIMPLE statement code561060 ! Node: Statement and operand traversals562405 ! Node: Tree SSA564997 ! Node: Annotations566785 ! Node: SSA Operands567190 ! Node: SSA581265 ! Node: Alias analysis590971 ! Node: Memory model594745 ! Node: RTL596104 ! Node: RTL Objects598292 ! Node: RTL Classes602166 ! Node: Accessors607212 ! Node: Special Accessors609606 ! Node: Flags615393 ! Node: Machine Modes630157 ! Node: Constants643805 ! Node: Regs and Memory651892 ! Node: Arithmetic669780 ! Node: Comparisons679825 ! Node: Bit-Fields684117 ! Node: Vector Operations685669 ! Node: Conversions687550 ! Node: RTL Declarations692048 ! Node: Side Effects692869 ! Node: Incdec709880 ! Node: Assembler713216 ! Node: Debug Information714761 ! Node: Insns715958 ! Node: Calls742351 ! Node: Sharing744944 ! Node: Reading RTL748055 ! Node: Control Flow749046 ! Node: Basic Blocks750815 ! Node: Edges756269 ! Node: Profile information764898 ! Node: Maintaining the CFG769582 ! Node: Liveness information775444 ! Node: Loop Analysis and Representation777570 ! Node: Loop representation778606 ! Node: Loop querying786169 ! Node: Loop manipulation788990 ! Node: LCSSA791351 ! Node: Scalar evolutions793420 ! Node: loop-iv796664 ! Node: Number of iterations798586 ! Node: Dependency analysis801392 ! Node: Machine Desc807742 ! Node: Overview810305 ! Node: Patterns812345 ! Node: Example815853 ! Node: RTL Template817314 ! Node: Output Template827970 ! Node: Output Statement831933 ! Node: Predicates836272 ! Node: Machine-Independent Predicates839190 ! Node: Defining Predicates844134 ! Node: Constraints850097 ! Node: Simple Constraints851566 ! Node: Multi-Alternative864406 ! Node: Class Preferences867615 ! Node: Modifiers868507 ! Node: Machine Constraints873240 ! Node: Disable Insn Alternatives933983 ! Node: Define Constraints937475 ! Node: C Constraint Interface944870 ! Node: Standard Names948019 ! Ref: shift patterns973445 ! Ref: prologue instruction pattern1023742 ! Ref: window_save instruction pattern1024235 ! Ref: epilogue instruction pattern1024512 ! Node: Pattern Ordering1042082 ! Node: Dependent Patterns1043318 ! Node: Jump Patterns1044938 ! Ref: Jump Patterns-Footnote-11047085 ! Node: Looping Patterns1047133 ! Node: Insn Canonicalizations1051862 ! Node: Expander Definitions1056447 ! Node: Insn Splitting1064661 ! Node: Including Patterns1074264 ! Node: Peephole Definitions1076048 ! Node: define_peephole1077301 ! Node: define_peephole21083631 ! Node: Insn Attributes1086697 ! Node: Defining Attributes1087879 ! Ref: define_enum_attr1091372 ! Node: Expressions1092408 ! Node: Tagging Insns1099158 ! Node: Attr Example1103511 ! Node: Insn Lengths1105884 ! Node: Constant Attributes1109292 ! Node: Mnemonic Attribute1110468 ! Node: Delay Slots1111987 ! Node: Processor pipeline description1115210 ! Ref: Processor pipeline description-Footnote-11134027 ! Node: Conditional Execution1134351 ! Node: Define Subst1137834 ! Node: Define Subst Example1139870 ! Node: Define Subst Pattern Matching1142864 ! Node: Define Subst Output Template1144090 ! Node: Constant Definitions1146160 ! Ref: define_enum1149942 ! Node: Iterators1150430 ! Node: Mode Iterators1151008 ! Node: Defining Mode Iterators1151986 ! Node: Substitutions1153480 ! Node: Examples1155722 ! Node: Code Iterators1157170 ! Node: Int Iterators1159449 ! Node: Subst Iterators1161895 ! Node: Target Macros1163587 ! Node: Target Structure1166599 ! Node: Driver1168715 ! Node: Run-time Target1187685 ! Node: Per-Function Data1197396 ! Node: Storage Layout1200160 ! Node: Type Layout1225910 ! Node: Registers1239536 ! Node: Register Basics1240510 ! Node: Allocation Order1245948 ! Node: Values in Registers1248432 ! Node: Leaf Functions1255910 ! Node: Stack Registers1258769 ! Node: Register Classes1260041 ! Node: Stack and Calling1292683 ! Node: Frame Layout1293249 ! Node: Exception Handling1304096 ! Node: Stack Checking1310306 ! Node: Frame Registers1315147 ! Node: Elimination1323412 ! Node: Stack Arguments1327640 ! Node: Register Arguments1334822 ! Node: Scalar Return1355867 ! Node: Aggregate Return1362323 ! Node: Caller Saves1366512 ! Node: Function Entry1367254 ! Node: Profiling1378346 ! Node: Tail Calls1380456 ! Node: Stack Smashing Protection1382357 ! Node: Miscellaneous Register Hooks1384020 ! Node: Varargs1384886 ! Node: Trampolines1394995 ! Node: Library Calls1401038 ! Node: Addressing Modes1405722 ! Node: Anchored Addresses1429012 ! Node: Condition Code1431655 ! Node: CC0 Condition Codes1433982 ! Node: MODE_CC Condition Codes1437228 ! Node: Costs1444036 ! Node: Scheduling1462212 ! Node: Sections1485390 ! Node: PIC1501083 ! Node: Assembler Format1503142 ! Node: File Framework1504280 ! Ref: TARGET_HAVE_SWITCHABLE_BSS_SECTIONS1511212 ! Node: Data Output1514482 ! Node: Uninitialized Data1522428 ! Node: Label Output1527439 ! Node: Initialization1552050 ! Node: Macros for Initialization1558011 ! Node: Instruction Output1564730 ! Node: Dispatch Tables1575359 ! Node: Exception Region Output1579759 ! Node: Alignment Output1586853 ! Node: Debugging Info1591456 ! Node: All Debuggers1592126 ! Node: DBX Options1594981 ! Node: DBX Hooks1600419 ! Node: File Names and DBX1601728 ! Node: SDB and DWARF1603840 ! Node: VMS Debug1610323 ! Node: Floating Point1610910 ! Node: Mode Switching1613665 ! Node: Target Attributes1618101 ! Node: Emulated TLS1627067 ! Node: MIPS Coprocessors1630457 ! Node: PCH Target1631616 ! Node: C++ ABI1633458 ! Node: Named Address Spaces1638252 ! Node: Misc1643521 ! Ref: TARGET_SHIFT_TRUNCATION_MASK1650268 ! Node: Host Config1706443 ! Node: Host Common1707511 ! Node: Filesystem1709885 ! Node: Host Misc1714000 ! Node: Fragments1716449 ! Node: Target Fragment1717644 ! Node: Host Fragment1728273 ! Node: Collect21728513 ! Node: Header Dirs1731149 ! Node: Type Information1732572 ! Node: GTY Options1735848 ! Node: Inheritance and GTY1747095 ! Ref: Inheritance and GTY-Footnote-11748660 ! Node: User GC1748930 ! Node: GGC Roots1752669 ! Node: Files1753382 ! Node: Invoking the garbage collector1756089 ! Node: Troubleshooting1757594 ! Node: Plugins1758669 ! Node: Plugins loading1759798 ! Node: Plugin API1760668 ! Node: Plugins pass1768394 ! Node: Plugins GC1770365 ! Node: Plugins description1772083 ! Node: Plugins attr1772619 ! Node: Plugins recording1774893 ! Node: Plugins gate1775743 ! Node: Plugins tracking1776334 ! Node: Plugins building1776922 ! Node: LTO1778712 ! Node: LTO Overview1779584 ! Node: LTO object file layout1785416 ! Node: IPA1790046 ! Node: WHOPR1799011 ! Node: Internal flags1803571 ! Node: Match and Simplify1804982 ! Node: GIMPLE API1805936 ! Node: The Language1808731 ! Node: Funding1819836 ! Node: GNU Project1822335 ! Node: Copying1822984 ! Node: GNU Free Documentation License1860496 ! Node: Contributors1885617 ! Node: Option Index1924426 ! Node: Concept Index1925303  End Tag Table --- 51617,52063 ---- * volatil, in mem, asm_operands, and asm_input: Flags. (line 76) * volatil, in reg: Flags. (line 98) * volatil, in subreg: Flags. (line 170) * volatil, in symbol_ref: Flags. (line 206) * volatile memory references: Flags. (line 329) * volatile, in prefetch: Flags. (line 214) * voting between constraint alternatives: Class Preferences. (line 6) ! * vrotlM3 instruction pattern: Standard Names. (line 601) ! * vrotrM3 instruction pattern: Standard Names. (line 601) ! * walk_dominator_tree: SSA. (line 196) * walk_gimple_op: Statement and operand traversals. ! (line 32) * walk_gimple_seq: Statement and operand traversals. ! (line 50) * walk_gimple_stmt: Statement and operand traversals. ! (line 13) ! * WCHAR_TYPE: Type Layout. (line 172) ! * WCHAR_TYPE_SIZE: Type Layout. (line 180) ! * which_alternative: Output Statement. (line 59) * WHILE_BODY: Statements for C++. (line 6) * WHILE_COND: Statements for C++. (line 6) * WHILE_STMT: Statements for C++. (line 6) * whopr: LTO. (line 6) ! * widen_ssumM3 instruction pattern: Standard Names. (line 418) ! * widen_usumM3 instruction pattern: Standard Names. (line 419) ! * WIDEST_HARDWARE_FP_SIZE: Type Layout. (line 117) ! * window_save instruction pattern: Standard Names. (line 1741) ! * WINT_TYPE: Type Layout. (line 185) ! * word_mode: Machine Modes. (line 368) ! * WORD_REGISTER_OPERATIONS: Misc. (line 54) ! * WORDS_BIG_ENDIAN: Storage Layout. (line 29) ! * WORDS_BIG_ENDIAN, effect on subreg: Regs and Memory. (line 217) * wpa: LTO. (line 6) ! * X in constraint: Simple Constraints. (line 124) * x-HOST: Host Fragment. (line 6) ! * XCmode: Machine Modes. (line 200) ! * XCOFF_DEBUGGING_INFO: DBX Options. (line 13) * XEXP: Accessors. (line 6) * XFmode: Machine Modes. (line 82) * XImode: Machine Modes. (line 54) * XINT: Accessors. (line 6) * xm-MACHINE.h <1>: Host Misc. (line 6) ! * xm-MACHINE.h: Filesystem. (line 6) ! * xor: Arithmetic. (line 167) * xor, canonicalization of: Insn Canonicalizations. ! (line 79) ! * xorM3 instruction pattern: Standard Names. (line 305) * XSTR: Accessors. (line 6) * XVEC: Accessors. (line 41) * XVECEXP: Accessors. (line 48) * XVECLEN: Accessors. (line 44) * XWINT: Accessors. (line 6) * zero_extend: Conversions. (line 28) ! * zero_extendMN2 instruction pattern: Standard Names. (line 1135) * zero_extract: Bit-Fields. (line 30) * zero_extract, canonicalization of: Insn Canonicalizations. ! (line 88)  Tag Table: ! Node: Top1842 ! Node: Contributing5024 ! Node: Portability5765 ! Node: Interface7553 ! Node: Libgcc10593 ! Node: Integer library routines12434 ! Node: Soft float library routines19402 ! Node: Decimal float library routines31339 ! Node: Fixed-point fractional library routines47096 ! Node: Exception handling routines147494 ! Node: Miscellaneous routines148601 ! Node: Languages150721 ! Node: Source Tree152270 ! Node: Configure Terms152852 ! Node: Top Level155810 ! Node: gcc Directory159296 ! Node: Subdirectories160246 ! Node: Configuration162413 ! Node: Config Fragments163133 ! Node: System Config164362 ! Node: Configuration Files165298 ! Node: Build168123 ! Node: Makefile168535 ! Ref: Makefile-Footnote-1175338 ! Ref: Makefile-Footnote-2175483 ! Node: Library Files175555 ! Node: Headers176117 ! Node: Documentation178200 ! Node: Texinfo Manuals179059 ! Node: Man Page Generation181392 ! Node: Miscellaneous Docs183307 ! Node: Front End184701 ! Node: Front End Directory188394 ! Node: Front End Config189714 ! Node: Front End Makefile192540 ! Node: Back End196322 ! Node: Testsuites200119 ! Node: Test Idioms201050 ! Node: Test Directives204447 ! Node: Directives204974 ! Node: Selectors215284 ! Node: Effective-Target Keywords216642 ! Ref: arm_fp_ok223823 ! Ref: arm_neon_ok224752 ! Ref: arm_neonv2_ok224910 ! Ref: arm_neon_fp16_ok225082 ! Ref: arm_vfp3_ok225722 ! Node: Add Options237604 ! Node: Require Support239107 ! Node: Final Actions241614 ! Node: Ada Tests247275 ! Node: C Tests248607 ! Node: libgcj Tests253030 ! Node: LTO Testing254157 ! Node: gcov Testing255804 ! Node: profopt Testing258791 ! Node: compat Testing260506 ! Node: Torture Tests264746 ! Node: Options266363 ! Node: Option file format266803 ! Node: Option properties273793 ! Node: Passes287446 ! Node: Parsing pass288336 ! Node: Cilk Plus Transformation291871 ! Node: Gimplification pass295258 ! Node: Pass manager297103 ! Node: Tree SSA passes298948 ! Node: RTL passes320147 ! Node: Optimization info332468 ! Node: Dump setup333286 ! Node: Optimization groups334408 ! Node: Dump files and streams335291 ! Node: Dump output verbosity336482 ! Node: Dump types337533 ! Node: Dump examples339023 ! Node: GENERIC340365 ! Node: Deficiencies342240 ! Node: Tree overview342481 ! Node: Macros and Functions346608 ! Node: Identifiers347433 ! Node: Containers349044 ! Node: Types350201 ! Node: Declarations362297 ! Node: Working with declarations362792 ! Node: Internal structure368398 ! Node: Current structure hierarchy368782 ! Node: Adding new DECL node types370876 ! Node: Attributes375161 ! Node: Expression trees376406 ! Node: Constant expressions378159 ! Node: Storage References381465 ! Node: Unary and Binary Expressions384984 ! Node: Vectors405135 ! Node: Statements410326 ! Node: Basic Statements410858 ! Node: Blocks415365 ! Node: Statement Sequences417066 ! Node: Empty Statements417399 ! Node: Jumps417973 ! Node: Cleanups418626 ! Node: OpenMP420394 ! Node: OpenACC426229 ! Node: Functions427261 ! Node: Function Basics427732 ! Node: Function Properties431417 ! Node: Language-dependent trees434199 ! Node: C and C++ Trees435085 ! Node: Types for C++437989 ! Node: Namespaces442967 ! Node: Classes446074 ! Node: Functions for C++451132 ! Node: Statements for C++457385 ! Node: C++ Expressions466159 ! Node: Java Trees467660 ! Node: GIMPLE467773 ! Node: Tuple representation471435 ! Node: Class hierarchy of GIMPLE statements478368 ! Node: GIMPLE instruction set483356 ! Node: GIMPLE Exception Handling485040 ! Node: Temporaries486954 ! Ref: Temporaries-Footnote-1488269 ! Node: Operands488332 ! Node: Compound Expressions489094 ! Node: Compound Lvalues489328 ! Node: Conditional Expressions490090 ! Node: Logical Operators490748 ! Node: Manipulating GIMPLE statements497613 ! Node: Tuple specific accessors503547 ! Node: `GIMPLE_ASM'504384 ! Node: `GIMPLE_ASSIGN'506772 ! Node: `GIMPLE_BIND'511482 ! Node: `GIMPLE_CALL'513301 ! Node: `GIMPLE_CATCH'517334 ! Node: `GIMPLE_COND'518490 ! Node: `GIMPLE_DEBUG'521291 ! Node: `GIMPLE_EH_FILTER'524675 ! Node: `GIMPLE_LABEL'526244 ! Node: `GIMPLE_GOTO'526863 ! Node: `GIMPLE_NOP'527392 ! Node: `GIMPLE_OMP_ATOMIC_LOAD'527760 ! Node: `GIMPLE_OMP_ATOMIC_STORE'528762 ! Node: `GIMPLE_OMP_CONTINUE'529466 ! Node: `GIMPLE_OMP_CRITICAL'530951 ! Node: `GIMPLE_OMP_FOR'531950 ! Node: `GIMPLE_OMP_MASTER'535372 ! Node: `GIMPLE_OMP_ORDERED'535755 ! Node: `GIMPLE_OMP_PARALLEL'536155 ! Node: `GIMPLE_OMP_RETURN'538931 ! Node: `GIMPLE_OMP_SECTION'539581 ! Node: `GIMPLE_OMP_SECTIONS'540247 ! Node: `GIMPLE_OMP_SINGLE'541862 ! Node: `GIMPLE_PHI'542813 ! Node: `GIMPLE_RESX'544097 ! Node: `GIMPLE_RETURN'544822 ! Node: `GIMPLE_SWITCH'545402 ! Node: `GIMPLE_TRY'547281 ! Node: `GIMPLE_WITH_CLEANUP_EXPR'549058 ! Node: GIMPLE sequences549941 ! Node: Sequence iterators553147 ! Node: Adding a new GIMPLE statement code561605 ! Node: Statement and operand traversals562950 ! Node: Tree SSA565550 ! Node: Annotations567336 ! Node: SSA Operands567741 ! Node: SSA581822 ! Node: Alias analysis591528 ! Node: Memory model595308 ! Node: RTL596671 ! Node: RTL Objects598859 ! Node: RTL Classes602733 ! Node: Accessors607780 ! Node: Special Accessors610174 ! Node: Flags615944 ! Node: Machine Modes630706 ! Node: Constants644358 ! Node: Regs and Memory652444 ! Node: Arithmetic670345 ! Node: Comparisons680398 ! Node: Bit-Fields684690 ! Node: Vector Operations686242 ! Node: Conversions688124 ! Node: RTL Declarations692622 ! Node: Side Effects693443 ! Node: Incdec710458 ! Node: Assembler713793 ! Node: Debug Information715338 ! Node: Insns716536 ! Node: Calls742944 ! Node: Sharing745537 ! Node: Reading RTL748647 ! Node: Control Flow749639 ! Node: Basic Blocks751407 ! Node: Edges756863 ! Node: Profile information765495 ! Node: Maintaining the CFG770179 ! Node: Liveness information776042 ! Node: Loop Analysis and Representation778168 ! Node: Loop representation779204 ! Node: Loop querying786769 ! Node: Loop manipulation789607 ! Node: LCSSA791975 ! Node: Scalar evolutions794047 ! Node: loop-iv797291 ! Node: Number of iterations799217 ! Node: Dependency analysis802026 ! Node: Machine Desc808379 ! Node: Overview810942 ! Node: Patterns812983 ! Node: Example816491 ! Node: RTL Template817952 ! Node: Output Template828608 ! Node: Output Statement832573 ! Node: Predicates836912 ! Node: Machine-Independent Predicates839830 ! Node: Defining Predicates844775 ! Node: Constraints850740 ! Node: Simple Constraints852209 ! Node: Multi-Alternative865065 ! Node: Class Preferences868274 ! Node: Modifiers869166 ! Node: Machine Constraints873898 ! Node: Disable Insn Alternatives934125 ! Node: Define Constraints937614 ! Node: C Constraint Interface945011 ! Node: Standard Names948151 ! Ref: shift patterns973587 ! Ref: prologue instruction pattern1023911 ! Ref: window_save instruction pattern1024404 ! Ref: epilogue instruction pattern1024679 ! Node: Pattern Ordering1042250 ! Node: Dependent Patterns1043486 ! Node: Jump Patterns1045106 ! Ref: Jump Patterns-Footnote-11047250 ! Node: Looping Patterns1047296 ! Node: Insn Canonicalizations1052024 ! Node: Expander Definitions1056615 ! Node: Insn Splitting1064827 ! Node: Including Patterns1074429 ! Node: Peephole Definitions1076209 ! Node: define_peephole1077462 ! Node: define_peephole21083793 ! Node: Insn Attributes1086859 ! Node: Defining Attributes1088041 ! Ref: define_enum_attr1091529 ! Node: Expressions1092564 ! Node: Tagging Insns1099313 ! Node: Attr Example1103666 ! Node: Insn Lengths1106040 ! Node: Constant Attributes1109448 ! Node: Mnemonic Attribute1110624 ! Node: Delay Slots1112143 ! Node: Processor pipeline description1115366 ! Ref: Processor pipeline description-Footnote-11134178 ! Node: Conditional Execution1134500 ! Node: Define Subst1137980 ! Node: Define Subst Example1140014 ! Node: Define Subst Pattern Matching1143008 ! Node: Define Subst Output Template1144233 ! Node: Constant Definitions1146303 ! Ref: define_enum1150085 ! Node: Iterators1150573 ! Node: Mode Iterators1151151 ! Node: Defining Mode Iterators1152129 ! Node: Substitutions1153623 ! Node: Examples1155864 ! Node: Code Iterators1157312 ! Node: Int Iterators1159591 ! Node: Subst Iterators1162034 ! Node: Target Macros1163726 ! Node: Target Structure1166738 ! Node: Driver1168853 ! Node: Run-time Target1187821 ! Node: Per-Function Data1197519 ! Node: Storage Layout1200284 ! Node: Type Layout1226050 ! Node: Registers1239680 ! Node: Register Basics1240654 ! Node: Allocation Order1246089 ! Node: Values in Registers1248577 ! Node: Leaf Functions1256066 ! Node: Stack Registers1258924 ! Node: Register Classes1260196 ! Node: Stack and Calling1292895 ! Node: Frame Layout1293461 ! Node: Exception Handling1304312 ! Node: Stack Checking1310532 ! Node: Frame Registers1315372 ! Node: Elimination1323637 ! Node: Stack Arguments1327864 ! Node: Register Arguments1335045 ! Node: Scalar Return1356103 ! Node: Aggregate Return1362558 ! Node: Caller Saves1366746 ! Node: Function Entry1367489 ! Node: Profiling1378591 ! Node: Tail Calls1380705 ! Node: Stack Smashing Protection1382606 ! Node: Miscellaneous Register Hooks1384269 ! Node: Varargs1385135 ! Node: Trampolines1395257 ! Node: Library Calls1401300 ! Node: Addressing Modes1405984 ! Node: Anchored Addresses1429394 ! Node: Condition Code1432043 ! Node: CC0 Condition Codes1434370 ! Node: MODE_CC Condition Codes1437616 ! Node: Costs1444421 ! Node: Scheduling1462602 ! Node: Sections1485786 ! Node: PIC1501479 ! Node: Assembler Format1503539 ! Node: File Framework1504677 ! Ref: TARGET_HAVE_SWITCHABLE_BSS_SECTIONS1511618 ! Node: Data Output1514883 ! Node: Uninitialized Data1522836 ! Node: Label Output1527847 ! Node: Initialization1552470 ! Node: Macros for Initialization1558432 ! Node: Instruction Output1565155 ! Node: Dispatch Tables1575790 ! Node: Exception Region Output1580190 ! Node: Alignment Output1587289 ! Node: Debugging Info1591891 ! Node: All Debuggers1592561 ! Node: DBX Options1595416 ! Node: DBX Hooks1600865 ! Node: File Names and DBX1602174 ! Node: SDB and DWARF1604286 ! Node: VMS Debug1610770 ! Node: Floating Point1611357 ! Node: Mode Switching1614112 ! Node: Target Attributes1618545 ! Node: Emulated TLS1627509 ! Node: MIPS Coprocessors1630899 ! Node: PCH Target1632058 ! Node: C++ ABI1633900 ! Node: Named Address Spaces1638692 ! Node: Misc1643966 ! Ref: TARGET_SHIFT_TRUNCATION_MASK1650713 ! Node: Host Config1706927 ! Node: Host Common1707995 ! Node: Filesystem1710374 ! Node: Host Misc1714489 ! Node: Fragments1716938 ! Node: Target Fragment1718133 ! Node: Host Fragment1728767 ! Node: Collect21729007 ! Node: Header Dirs1731643 ! Node: Type Information1733066 ! Node: GTY Options1736346 ! Node: Inheritance and GTY1747592 ! Ref: Inheritance and GTY-Footnote-11749157 ! Node: User GC1749425 ! Node: GGC Roots1753160 ! Node: Files1753876 ! Node: Invoking the garbage collector1756583 ! Node: Troubleshooting1758086 ! Node: Plugins1759162 ! Node: Plugins loading1760291 ! Node: Plugin API1761160 ! Node: Plugins pass1768887 ! Node: Plugins GC1770856 ! Node: Plugins description1772571 ! Node: Plugins attr1773106 ! Node: Plugins recording1775377 ! Node: Plugins gate1776227 ! Node: Plugins tracking1776818 ! Node: Plugins building1777406 ! Node: LTO1779195 ! Node: LTO Overview1780067 ! Node: LTO object file layout1785894 ! Node: IPA1790526 ! Node: WHOPR1799491 ! Node: Internal flags1804052 ! Node: Match and Simplify1805464 ! Node: GIMPLE API1806425 ! Node: The Language1809220 ! Node: Funding1820325 ! Node: GNU Project1822823 ! Node: Copying1823472 ! Node: GNU Free Documentation License1861003 ! Node: Contributors1886143 ! Node: Option Index1924955 ! Node: Concept Index1925832  End Tag Table diff -Nrcpad gcc-6.3.0/gcc/doc/gccint.texi gcc-6.4.0/gcc/doc/gccint.texi *** gcc-6.3.0/gcc/doc/gccint.texi Mon Jan 4 13:03:35 2016 --- gcc-6.4.0/gcc/doc/gccint.texi Tue Jul 4 07:15:57 2017 *************** *** 26,32 **** @c %**end of header @copying ! Copyright @copyright{} 1988-2016 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 --- 26,32 ---- @c %**end of header @copying ! Copyright @copyright{} 1988-2017 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 diff -Nrcpad gcc-6.3.0/gcc/doc/gcj-dbtool.1 gcc-6.4.0/gcc/doc/gcj-dbtool.1 *** gcc-6.3.0/gcc/doc/gcj-dbtool.1 Wed Dec 21 09:16:01 2016 --- gcc-6.4.0/gcc/doc/gcj-dbtool.1 Tue Jul 4 09:08:00 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GCJ-DBTOOL 1" ! .TH GCJ-DBTOOL 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GCJ-DBTOOL 1" ! .TH GCJ-DBTOOL 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/gcj.1 gcc-6.4.0/gcc/doc/gcj.1 *** gcc-6.3.0/gcc/doc/gcj.1 Wed Dec 21 09:16:01 2016 --- gcc-6.4.0/gcc/doc/gcj.1 Tue Jul 4 09:07:59 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GCJ 1" ! .TH GCJ 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GCJ 1" ! .TH GCJ 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** It is safe to use this option if you are *** 436,442 **** .IP "\fB\-fjni\fR" 4 .IX Item "-fjni" With \fBgcj\fR there are two options for writing native methods: \s-1CNI\s0 ! and \s-1JNI.\s0 By default \fBgcj\fR assumes you are using \s-1CNI.\s0 If you are compiling a class with native methods, and these methods are implemented using \s-1JNI,\s0 then you must use \f(CW\*(C`\-fjni\*(C'\fR. This option causes \&\fBgcj\fR to generate stubs which will invoke the underlying \s-1JNI\s0 --- 440,446 ---- .IP "\fB\-fjni\fR" 4 .IX Item "-fjni" With \fBgcj\fR there are two options for writing native methods: \s-1CNI\s0 ! and \s-1JNI. \s0 By default \fBgcj\fR assumes you are using \s-1CNI. \s0 If you are compiling a class with native methods, and these methods are implemented using \s-1JNI,\s0 then you must use \f(CW\*(C`\-fjni\*(C'\fR. This option causes \&\fBgcj\fR to generate stubs which will invoke the underlying \s-1JNI\s0 *************** interpreted and compiled code. *** 486,492 **** Note that, at present, \f(CW\*(C`\-findirect\-dispatch\*(C'\fR can only be used when compiling \fI.class\fR files. It will not work when compiling from source. \s-1CNI\s0 also does not yet work with the binary compatibility ! \&\s-1ABI.\s0 These restrictions will be lifted in some future release. .Sp However, if you compile \s-1CNI\s0 code with the standard \s-1ABI,\s0 you can call it from code built with the binary compatibility \s-1ABI.\s0 --- 490,496 ---- Note that, at present, \f(CW\*(C`\-findirect\-dispatch\*(C'\fR can only be used when compiling \fI.class\fR files. It will not work when compiling from source. \s-1CNI\s0 also does not yet work with the binary compatibility ! \&\s-1ABI. \s0 These restrictions will be lifted in some future release. .Sp However, if you compile \s-1CNI\s0 code with the standard \s-1ABI,\s0 you can call it from code built with the binary compatibility \s-1ABI.\s0 *************** or call methods in the \f(CW\*(C`java.la *** 513,520 **** \&\f(CW\*(C`\-freduced\-reflection\*(C'\fR will result in proper operation with a savings in executable code size. .Sp ! \&\s-1JNI\s0 (\f(CW\*(C`\-fjni\*(C'\fR) and the binary compatibility \s-1ABI\s0 ! (\f(CW\*(C`\-findirect\-dispatch\*(C'\fR) do not work properly without full reflection meta-data. Because of this, it is an error to use these options with \f(CW\*(C`\-freduced\-reflection\*(C'\fR. .Sp --- 517,524 ---- \&\f(CW\*(C`\-freduced\-reflection\*(C'\fR will result in proper operation with a savings in executable code size. .Sp ! \&\s-1JNI \s0(\f(CW\*(C`\-fjni\*(C'\fR) and the binary compatibility \s-1ABI ! \&\s0(\f(CW\*(C`\-findirect\-dispatch\*(C'\fR) do not work properly without full reflection meta-data. Because of this, it is an error to use these options with \f(CW\*(C`\-freduced\-reflection\*(C'\fR. .Sp diff -Nrcpad gcc-6.3.0/gcc/doc/gcj.info gcc-6.4.0/gcc/doc/gcj.info *** gcc-6.3.0/gcc/doc/gcj.info Wed Dec 21 09:34:09 2016 --- gcc-6.4.0/gcc/doc/gcj.info Tue Jul 4 09:27:46 2017 *************** *** 1,4 **** ! This is gcj.info, produced by makeinfo version 6.1 from gcj.texi. Copyright (C) 2001-2016 Free Software Foundation, Inc. --- 1,5 ---- ! This is doc/gcj.info, produced by makeinfo version 4.13 from ! /space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/java/gcj.texi. Copyright (C) 2001-2016 Free Software Foundation, Inc. *************** is included in the section entitled "GNU *** 16,23 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * Gcj: (gcj). Ahead-of-time compiler for the Java language --- 17,25 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. ! INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * Gcj: (gcj). Ahead-of-time compiler for the Java language *************** START-INFO-DIR-ENTRY *** 43,50 **** into one system-wide database. END-INFO-DIR-ENTRY - - Copyright (C) 2001-2016 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document --- 45,50 ---- *************** is included in the section entitled "GNU *** 61,68 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development.  File: gcj.info, Node: Top, Next: Copying, Up: (dir) --- 61,68 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development.  File: gcj.info, Node: Top, Next: Copying, Up: (dir) *************** File: gcj.info, Node: Top, Next: Copyi *** 70,85 **** Introduction ************ ! This manual describes how to use 'gcj', the GNU compiler for the Java ! programming language. 'gcj' can generate both '.class' files and object ! files, and it can read both Java source code and '.class' files. * Menu: * Copying:: The GNU General Public License * GNU Free Documentation License:: How you can share and copy this manual ! * Invoking gcj:: Compiler options supported by 'gcj' * Compatibility:: Compatibility between gcj and other tools for Java * Invoking jcf-dump:: Print information about class files * Invoking gij:: Interpreting Java bytecodes --- 70,85 ---- Introduction ************ ! This manual describes how to use `gcj', the GNU compiler for the Java ! programming language. `gcj' can generate both `.class' files and ! object files, and it can read both Java source code and `.class' files. * Menu: * Copying:: The GNU General Public License * GNU Free Documentation License:: How you can share and copy this manual ! * Invoking gcj:: Compiler options supported by `gcj' * Compatibility:: Compatibility between gcj and other tools for Java * Invoking jcf-dump:: Print information about class files * Invoking gij:: Interpreting Java bytecodes *************** GNU General Public License *** 103,109 **** Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 103,109 ---- Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** want it, that you can change the softwar *** 131,139 **** free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you have ! certain responsibilities if you distribute copies of the software, or if ! you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same --- 131,139 ---- free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you ! have certain responsibilities if you distribute copies of the software, ! or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same *************** changed, so that their problems will not *** 152,166 **** authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the manufacturer ! can do so. This is fundamentally incompatible with the aim of ! protecting users' freedom to change the software. The systematic ! pattern of such abuse occurs in the area of products for individuals to ! use, which is precisely where it is most unacceptable. Therefore, we ! have designed this version of the GPL to prohibit the practice for those ! products. If such problems arise substantially in other domains, we ! stand ready to extend this provision to those domains in future versions ! of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of --- 152,167 ---- authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the ! manufacturer can do so. This is fundamentally incompatible with the ! aim of protecting users' freedom to change the software. The ! systematic pattern of such abuse occurs in the area of products for ! individuals to use, which is precisely where it is most unacceptable. ! Therefore, we have designed this version of the GPL to prohibit the ! practice for those products. If such problems arise substantially in ! other domains, we stand ready to extend this provision to those domains ! in future versions of the GPL, as needed to protect the freedom of ! users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of *************** TERMS AND CONDITIONS *** 197,204 **** To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it on ! a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. --- 198,205 ---- To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it ! on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. *************** TERMS AND CONDITIONS *** 212,219 **** to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may convey ! the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. --- 213,220 ---- to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may ! convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. *************** TERMS AND CONDITIONS *** 221,228 **** 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any non-source ! form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in --- 222,229 ---- 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any ! non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in *************** TERMS AND CONDITIONS *** 233,242 **** The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work with ! that Major Component, or to implement a Standard Interface for ! which an implementation is available to the public in source code ! form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code --- 234,243 ---- The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work ! with that Major Component, or to implement a Standard Interface ! for which an implementation is available to the public in source ! code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code *************** TERMS AND CONDITIONS *** 244,258 **** The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including scripts ! to control those activities. However, it does not include the ! work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files associated ! with source files for the work, and the source code for shared ! libraries and dynamically linked subprograms that the work is ! specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. --- 245,259 ---- The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including ! scripts to control those activities. However, it does not include ! the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files ! associated with source files for the work, and the source code for ! shared libraries and dynamically linked subprograms that the work ! is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. *************** TERMS AND CONDITIONS *** 269,290 **** copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, given ! its content, constitutes a covered work. This License acknowledges ! your rights of fair use or other equivalent, as provided by ! copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for you, ! or provide you with facilities for running those works, provided ! that you comply with the terms of this License in conveying all ! material for which you do not control copyright. Those thus making ! or running the covered works for you must do so exclusively on your ! behalf, under your direction and control, on terms that prohibit ! them from making any copies of your copyrighted material outside ! their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section --- 270,291 ---- copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, ! given its content, constitutes a covered work. This License ! acknowledges your rights of fair use or other equivalent, as ! provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for ! you, or provide you with facilities for running those works, ! provided that you comply with the terms of this License in ! conveying all material for which you do not control copyright. ! Those thus making or running the covered works for you must do so ! exclusively on your behalf, under your direction and control, on ! terms that prohibit them from making any copies of your ! copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section *************** TERMS AND CONDITIONS *** 301,308 **** When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention to ! limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. --- 302,309 ---- When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention ! to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. *************** TERMS AND CONDITIONS *** 372,379 **** b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for as ! long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a --- 373,380 ---- b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for ! as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a *************** TERMS AND CONDITIONS *** 383,413 **** to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of the ! written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access to ! the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated by ! you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to the ! object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long as ! needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. --- 384,415 ---- to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of ! the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access ! to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated ! by you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to ! the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long ! as needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. + A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. *************** TERMS AND CONDITIONS *** 415,422 **** A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product is ! a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the --- 417,424 ---- A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product ! is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the *************** TERMS AND CONDITIONS *** 447,457 **** The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or installed ! by the recipient, or for the User Product in which it has been ! modified or installed. Access to a network may be denied when the ! modification itself materially and adversely affects the operation ! of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information --- 449,459 ---- The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or ! installed by the recipient, or for the User Product in which it ! has been modified or installed. Access to a network may be denied ! when the modification itself materially and adversely affects the ! operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information *************** TERMS AND CONDITIONS *** 481,488 **** Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License with ! terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or --- 483,490 ---- Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License ! with terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or *************** TERMS AND CONDITIONS *** 492,499 **** Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be marked ! in reasonable ways as different from the original version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or --- 494,502 ---- Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be ! marked in reasonable ways as different from the original ! version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or *************** TERMS AND CONDITIONS *** 512,521 **** you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or conveying ! under this License, you may add to a covered work material governed ! by the terms of that license document, provided that the further ! restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the --- 515,525 ---- you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or ! conveying under this License, you may add to a covered work ! material governed by the terms of that license document, provided ! that the further restriction does not survive such relicensing or ! conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the *************** TERMS AND CONDITIONS *** 531,543 **** You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under the ! third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 535,547 ---- You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under ! the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** TERMS AND CONDITIONS *** 549,558 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, you do not qualify to receive new licenses ! for the same material under section 10. 9. Acceptance Not Required for Having Copies. --- 553,562 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, you do not qualify to receive new ! licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. *************** TERMS AND CONDITIONS *** 566,572 **** by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and --- 570,576 ---- by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and *************** TERMS AND CONDITIONS *** 580,600 **** covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to possession ! of the Corresponding Source of the work from the predecessor in ! interest, if the predecessor has it or can get it with reasonable ! efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for exercise ! of rights granted under this License, and you may not initiate ! litigation (including a cross-claim or counterclaim in a lawsuit) ! alleging that any patent claim is infringed by making, using, ! selling, offering for sale, or importing the Program or any portion ! of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. --- 584,604 ---- covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to ! possession of the Corresponding Source of the work from the ! predecessor in interest, if the predecessor has it or can get it ! with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for ! exercise of rights granted under this License, and you may not ! initiate litigation (including a cross-claim or counterclaim in a ! lawsuit) alleging that any patent claim is infringed by making, ! using, selling, offering for sale, or importing the Program or any ! portion of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. *************** TERMS AND CONDITIONS *** 614,628 **** Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its contributor ! version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To "grant" ! such a patent license to a party means to make such an agreement or ! commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available --- 618,632 ---- Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its ! contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To ! "grant" such a patent license to a party means to make such an ! agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available *************** TERMS AND CONDITIONS *** 652,686 **** conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under which ! you make payment to the third party based on the extent of your ! activity of conveying the work, and under which the third party ! grants, to any of the parties who would receive the covered work ! from you, a discriminatory patent license (a) in connection with ! copies of the covered work conveyed by you (or copies made from ! those copies), or (b) primarily for and in connection with specific ! products or compilations that contain the covered work, unless you ! entered into that arrangement, or that patent license was granted, ! prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, agreement ! or otherwise) that contradict the conditions of this License, they ! do not excuse you from the conditions of this License. If you ! cannot convey a covered work so as to satisfy simultaneously your ! obligations under this License and any other pertinent obligations, ! then as a consequence you may not convey it at all. For example, ! if you agree to terms that obligate you to collect a royalty for ! further conveying from those to whom you convey the Program, the ! only way you could satisfy both those terms and this License would ! be to refrain entirely from conveying the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed --- 656,691 ---- conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under ! which you make payment to the third party based on the extent of ! your activity of conveying the work, and under which the third ! party grants, to any of the parties who would receive the covered ! work from you, a discriminatory patent license (a) in connection ! with copies of the covered work conveyed by you (or copies made ! from those copies), or (b) primarily for and in connection with ! specific products or compilations that contain the covered work, ! unless you entered into that arrangement, or that patent license ! was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, ! agreement or otherwise) that contradict the conditions of this ! License, they do not excuse you from the conditions of this ! License. If you cannot convey a covered work so as to satisfy ! simultaneously your obligations under this License and any other ! pertinent obligations, then as a consequence you may not convey it ! at all. For example, if you agree to terms that obligate you to ! collect a royalty for further conveying from those to whom you ! convey the Program, the only way you could satisfy both those ! terms and this License would be to refrain entirely from conveying ! the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed *************** TERMS AND CONDITIONS *** 691,711 **** General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. Such ! new versions will be similar in spirit to the present version, but ! may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the Free ! Software Foundation. If the Program does not specify a version ! number of the GNU General Public License, you may choose any ! version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that --- 696,717 ---- General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. ! Such new versions will be similar in spirit to the present ! version, but may differ in detail to address new problems or ! concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the ! Free Software Foundation. If the Program does not specify a ! version number of the GNU General Public License, you may choose ! any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that *************** TERMS AND CONDITIONS *** 717,740 **** author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR ! DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD --- 723,746 ---- author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU ! FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD *************** TERMS AND CONDITIONS *** 742,748 **** PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, --- 748,754 ---- PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, *************** TERMS AND CONDITIONS *** 751,756 **** --- 757,763 ---- connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. + END OF TERMS AND CONDITIONS =========================== *************** state the exclusion of warranty; and eac *** 781,787 **** General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. --- 788,794 ---- General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see `http://www.gnu.org/licenses/'. Also add information on how to contact you by electronic and paper mail. *************** mail. *** 790,800 **** notice like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type 'show c' for details. ! The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". --- 797,807 ---- notice like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type `show c' for details. ! The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". *************** use an "about box". *** 802,815 **** You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read .  File: gcj.info, Node: GNU Free Documentation License, Next: Invoking gcj, Prev: Copying, Up: Top --- 809,822 ---- You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see `http://www.gnu.org/licenses/'. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.  File: gcj.info, Node: GNU Free Documentation License, Next: Invoking gcj, Prev: Copying, Up: Top *************** GNU Free Documentation License *** 820,826 **** Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 827,833 ---- Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU Free Documentation License *** 845,865 **** free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. We ! recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it can ! be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You accept ! the license if you copy, modify or distribute the work in a way ! requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with --- 852,872 ---- free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. ! We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it ! can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You ! accept the license if you copy, modify or distribute the work in a ! way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with *************** GNU Free Documentation License *** 877,888 **** regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in the ! notice that says that the Document is released under this License. ! If a section does not fit the above definition of Secondary then it ! is not allowed to be designated as Invariant. The Document may ! contain zero Invariant Sections. If the Document does not identify ! any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice --- 884,895 ---- regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in ! the notice that says that the Document is released under this ! License. If a section does not fit the above definition of ! Secondary then it is not allowed to be designated as Invariant. ! The Document may contain zero Invariant Sections. If the Document ! does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice *************** GNU Free Documentation License *** 893,919 **** A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images composed ! of pixels) generic paint programs or (for drawings) some widely ! available drawing editor, and that is suitable for input to text ! formatters or for automatic translation to a variety of formats ! suitable for input to text formatters. A copy made in an otherwise ! Transparent file format whose markup, or absence of markup, has ! been arranged to thwart or discourage subsequent modification by ! readers is not Transparent. An image format is not Transparent if ! used for any substantial amount of text. A copy that is not ! "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and standard-conforming ! simple HTML, PostScript or PDF designed for human modification. ! Examples of transparent image formats include PNG, XCF and JPG. ! Opaque formats include proprietary formats that can be read and ! edited only by proprietary word processors, SGML or XML for which ! the DTD and/or processing tools are not generally available, and ! the machine-generated HTML, PostScript or PDF produced by some word ! processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the --- 900,926 ---- A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images ! composed of pixels) generic paint programs or (for drawings) some ! widely available drawing editor, and that is suitable for input to ! text formatters or for automatic translation to a variety of ! formats suitable for input to text formatters. A copy made in an ! otherwise Transparent file format whose markup, or absence of ! markup, has been arranged to thwart or discourage subsequent ! modification by readers is not Transparent. An image format is ! not Transparent if used for any substantial amount of text. A ! copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and ! standard-conforming simple HTML, PostScript or PDF designed for ! human modification. Examples of transparent image formats include ! PNG, XCF and JPG. Opaque formats include proprietary formats that ! can be read and edited only by proprietary word processors, SGML or ! XML for which the DTD and/or processing tools are not generally ! available, and the machine-generated HTML, PostScript or PDF ! produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the *************** GNU Free Documentation License *** 951,958 **** may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow the ! conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. --- 958,965 ---- may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow ! the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. *************** GNU Free Documentation License *** 966,976 **** these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the title ! equally prominent and visible. You may add other material on the ! covers in addition. Copying with changes limited to the covers, as ! long as they preserve the title of the Document and satisfy these ! conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit --- 973,984 ---- these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the ! title equally prominent and visible. You may add other material ! on the covers in addition. Copying with changes limited to the ! covers, as long as they preserve the title of the Document and ! satisfy these conditions, can be treated as verbatim copying in ! other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit *************** GNU Free Documentation License *** 978,1016 **** adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a machine-readable ! Transparent copy along with each Opaque copy, or state in or with ! each Opaque copy a computer-network location from which the general ! network-using public has access to download using public-standard ! network protocols a complete Transparent copy of the Document, free ! of added material. If you use the latter option, you must take ! reasonably prudent steps, when you begin distribution of Opaque ! copies in quantity, to ensure that this Transparent copy will ! remain thus accessible at the stated location until at least one ! year after the last time you distribute an Opaque copy (directly or ! through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of copies, ! to give them a chance to provide you with an updated version of the ! Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with the ! Modified Version filling the role of the Document, thus licensing ! distribution and modification of the Modified Version to whoever ! possesses a copy of it. In addition, you must do these things in ! the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of previous ! versions (which should, if there were any, be listed in the ! History section of the Document). You may use the same title ! as a previous version if the original publisher of that ! version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in --- 986,1025 ---- adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a ! machine-readable Transparent copy along with each Opaque copy, or ! state in or with each Opaque copy a computer-network location from ! which the general network-using public has access to download ! using public-standard network protocols a complete Transparent ! copy of the Document, free of added material. If you use the ! latter option, you must take reasonably prudent steps, when you ! begin distribution of Opaque copies in quantity, to ensure that ! this Transparent copy will remain thus accessible at the stated ! location until at least one year after the last time you ! distribute an Opaque copy (directly or through your agents or ! retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of ! copies, to give them a chance to provide you with an updated ! version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with ! the Modified Version filling the role of the Document, thus ! licensing distribution and modification of the Modified Version to ! whoever possesses a copy of it. In addition, you must do these ! things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of ! previous versions (which should, if there were any, be listed ! in the History section of the Document). You may use the ! same title as a previous version if the original publisher of ! that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in *************** GNU Free Documentation License *** 1040,1069 **** I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on the ! Title Page. If there is no section Entitled "History" in the ! Document, create one stating the title, year, authors, and ! publisher of the Document as given on its Title Page, then add ! an item describing the Modified Version as stated in the ! previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in the ! "History" section. You may omit a network location for a work ! that was published at least four years before the Document ! itself, or if the original publisher of the version it refers ! to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the section ! all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, unaltered ! in their text and in their titles. Section numbers or the ! equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. --- 1049,1079 ---- I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on ! the Title Page. If there is no section Entitled "History" in ! the Document, create one stating the title, year, authors, ! and publisher of the Document as given on its Title Page, ! then add an item describing the Modified Version as stated in ! the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in ! the "History" section. You may omit a network location for a ! work that was published at least four years before the ! Document itself, or if the original publisher of the version ! it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the ! section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, ! unaltered in their text and in their titles. Section numbers ! or the equivalent are not considered part of the section ! titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. *************** GNU Free Documentation License *** 1076,1086 **** If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option designate ! some or all of these sections as invariant. To do this, add their ! titles to the list of Invariant Sections in the Modified Version's ! license notice. These titles must be distinct from any other ! section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various --- 1086,1096 ---- If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option ! designate some or all of these sections as invariant. To do this, ! add their titles to the list of Invariant Sections in the Modified ! Version's license notice. These titles must be distinct from any ! other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various *************** GNU Free Documentation License *** 1089,1103 **** definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end of ! the list of Cover Texts in the Modified Version. Only one passage ! of Front-Cover Text and one of Back-Cover Text may be added by (or ! through arrangements made by) any one entity. If the Document ! already includes a cover text for the same cover, previously added ! by you or by arrangement made by the same entity you are acting on ! behalf of, you may not add another; but you may replace the old ! one, on explicit permission from the previous publisher that added ! the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to --- 1099,1113 ---- definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end ! of the list of Cover Texts in the Modified Version. Only one ! passage of Front-Cover Text and one of Back-Cover Text may be ! added by (or through arrangements made by) any one entity. If the ! Document already includes a cover text for the same cover, ! previously added by you or by arrangement made by the same entity ! you are acting on behalf of, you may not add another; but you may ! replace the old one, on explicit permission from the previous ! publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to *************** GNU Free Documentation License *** 1107,1114 **** You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination all ! of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. --- 1117,1124 ---- You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination ! all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. *************** GNU Free Documentation License *** 1135,1154 **** documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the documents ! in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow this ! License in all other respects regarding verbatim copying of that ! document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of a ! storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this --- 1145,1164 ---- documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the ! documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow ! this License in all other respects regarding verbatim copying of ! that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of ! a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this *************** GNU Free Documentation License *** 1193,1200 **** However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 1203,1210 ---- However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** GNU Free Documentation License *** 1206,1238 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, receipt of a copy of some or all of the ! same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! . Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If the ! Document does not specify a version number of this License, you may ! choose any version ever published (not as a draft) by the Free ! Software Foundation. If the Document specifies that a proxy can ! decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also --- 1216,1248 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, receipt of a copy of some or all of ! the same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! `http://www.gnu.org/copyleft/'. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If ! the Document does not specify a version number of this License, ! you may choose any version ever published (not as a draft) by the ! Free Software Foundation. If the Document specifies that a proxy ! can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also *************** GNU Free Documentation License *** 1262,1267 **** --- 1272,1278 ---- site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. + ADDENDUM: How to use this License for your documents ==================================================== *************** notices just after the title page: *** 1278,1284 **** Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts --- 1289,1295 ---- Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts *************** combination of the three, merge those tw *** 1289,1297 **** situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of free ! software license, such as the GNU General Public License, to permit ! their use in free software.  File: gcj.info, Node: Invoking gcj, Next: Compatibility, Prev: GNU Free Documentation License, Up: Top --- 1300,1308 ---- situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of ! free software license, such as the GNU General Public License, to ! permit their use in free software.  File: gcj.info, Node: Invoking gcj, Next: Compatibility, Prev: GNU Free Documentation License, Up: Top *************** File: gcj.info, Node: Invoking gcj, Ne *** 1299,1307 **** 1 Invoking gcj ************** ! As 'gcj' is just another front end to 'gcc', it supports many of the same options as gcc. *Note Option Summary: (gcc)Option Summary. This ! manual only documents the options specific to 'gcj'. * Menu: --- 1310,1318 ---- 1 Invoking gcj ************** ! As `gcj' is just another front end to `gcc', it supports many of the same options as gcc. *Note Option Summary: (gcc)Option Summary. This ! manual only documents the options specific to `gcj'. * Menu: *************** File: gcj.info, Node: Input and output *** 1319,1355 **** 1.1 Input and output files ========================== ! A 'gcj' command is like a 'gcc' command, in that it consists of a number ! of options and file names. The following kinds of input file names are ! supported: ! 'FILE.java' Java source files. ! 'FILE.class' Java bytecode files. ! 'FILE.zip' ! 'FILE.jar' ! An archive containing one or more '.class' files, all of which are compiled. The archive may be compressed. Files in an archive ! which don't end with '.class' are treated as resource files; they ! are compiled into the resulting object file as 'core:' URLs. ! '@FILE' A file containing a whitespace-separated list of input file names. ! (Currently, these must all be '.java' source files, but that may change.) Each named file is compiled, just as if it had been on the command line. - 'LIBRARY.a' - 'LIBRARY.so' - '-lLIBNAME' - Libraries to use when linking. See the 'gcc' manual. ! You can specify more than one input file on the 'gcj' command line, ! in which case they will all be compiled. If you specify a '-o FILENAME' option, all the input files will be compiled together, producing a single output file, named FILENAME. This is allowed even when using ! '-S' or '-c', but not when using '-C' or '--resource'. (This is an ! extension beyond the what plain 'gcc' allows.) (If more than one input ! file is specified, all must currently be '.java' files, though we hope to fix this.)  --- 1330,1370 ---- 1.1 Input and output files ========================== ! A `gcj' command is like a `gcc' command, in that it consists of a ! number of options and file names. The following kinds of input file ! names are supported: ! `FILE.java' Java source files. ! ! `FILE.class' Java bytecode files. ! ! `FILE.zip' ! `FILE.jar' ! An archive containing one or more `.class' files, all of which are compiled. The archive may be compressed. Files in an archive ! which don't end with `.class' are treated as resource files; they ! are compiled into the resulting object file as `core:' URLs. ! ! `@FILE' A file containing a whitespace-separated list of input file names. ! (Currently, these must all be `.java' source files, but that may change.) Each named file is compiled, just as if it had been on the command line. ! `LIBRARY.a' ! `LIBRARY.so' ! `-lLIBNAME' ! Libraries to use when linking. See the `gcc' manual. ! ! You can specify more than one input file on the `gcj' command line, ! in which case they will all be compiled. If you specify a `-o FILENAME' option, all the input files will be compiled together, producing a single output file, named FILENAME. This is allowed even when using ! `-S' or `-c', but not when using `-C' or `--resource'. (This is an ! extension beyond the what plain `gcc' allows.) (If more than one input ! file is specified, all must currently be `.java' files, though we hope to fix this.)  *************** File: gcj.info, Node: Input Options, N *** 1358,1436 **** 1.2 Input Options ================= ! 'gcj' has options to control where it looks to find files it needs. For ! instance, 'gcj' might need to load a class that is referenced by the ! file it has been asked to compile. Like other compilers for the Java ! language, 'gcj' has a notion of a "class path". There are several options and environment variables which can be used to manipulate the ! class path. When 'gcj' looks for a given class, it searches the class ! path looking for matching '.class' or '.java' file. 'gcj' comes with a ! built-in class path which points at the installed 'libgcj.jar', a file which contains all the standard classes. In the text below, a directory or path component can refer either to ! an actual directory on the filesystem, or to a '.zip' or '.jar' file, ! which 'gcj' will search as if it is a directory. ! '-IDIR' ! All directories specified by '-I' are kept in order and prepended to the class path constructed from all the other options. Unless ! compatibility with tools like 'javac' is important, we recommend ! always using '-I' instead of the other options for manipulating the class path. ! '--classpath=PATH' This sets the class path to PATH, a colon-separated list of paths (on Windows-based systems, a semicolon-separate list of paths). This does not override the builtin ("boot") search path. ! '--CLASSPATH=PATH' ! Deprecated synonym for '--classpath'. ! '--bootclasspath=PATH' Where to find the standard builtin classes, such as ! 'java.lang.String'. ! '--extdirs=PATH' For each directory in the PATH, place the contents of that directory at the end of the class path. ! 'CLASSPATH' This is an environment variable which holds a list of paths. The final class path is constructed like so: ! * First come all directories specified via '-I'. ! * If '--classpath' is specified, its value is appended. Otherwise, ! if the 'CLASSPATH' environment variable is specified, then its ! value is appended. Otherwise, the current directory ('"."') is appended. ! * If '--bootclasspath' was specified, append its value. Otherwise, ! append the built-in system directory, 'libgcj.jar'. ! * Finally, if '--extdirs' was specified, append the contents of the specified directories at the end of the class path. Otherwise, append the contents of the built-in extdirs at ! '$(prefix)/share/java/ext'. ! The classfile built by 'gcj' for the class 'java.lang.Object' (and ! placed in 'libgcj.jar') contains a special zero length attribute ! 'gnu.gcj.gcj-compiled'. The compiler looks for this attribute when ! loading 'java.lang.Object' and will report an error if it isn't found, unless it compiles to bytecode (the option ! '-fforce-classes-archive-check' can be used to override this behavior in ! this particular case.) ! '-fforce-classes-archive-check' This forces the compiler to always check for the special zero ! length attribute 'gnu.gcj.gcj-compiled' in 'java.lang.Object' and issue an error if it isn't found. ! '-fsource=VERSION' ! This option is used to choose the source version accepted by 'gcj'. ! The default is '1.5'.  File: gcj.info, Node: Encodings, Next: Warnings, Prev: Input Options, Up: Invoking gcj --- 1373,1451 ---- 1.2 Input Options ================= ! `gcj' has options to control where it looks to find files it needs. ! For instance, `gcj' might need to load a class that is referenced by ! the file it has been asked to compile. Like other compilers for the ! Java language, `gcj' has a notion of a "class path". There are several options and environment variables which can be used to manipulate the ! class path. When `gcj' looks for a given class, it searches the class ! path looking for matching `.class' or `.java' file. `gcj' comes with a ! built-in class path which points at the installed `libgcj.jar', a file which contains all the standard classes. In the text below, a directory or path component can refer either to ! an actual directory on the filesystem, or to a `.zip' or `.jar' file, ! which `gcj' will search as if it is a directory. ! `-IDIR' ! All directories specified by `-I' are kept in order and prepended to the class path constructed from all the other options. Unless ! compatibility with tools like `javac' is important, we recommend ! always using `-I' instead of the other options for manipulating the class path. ! `--classpath=PATH' This sets the class path to PATH, a colon-separated list of paths (on Windows-based systems, a semicolon-separate list of paths). This does not override the builtin ("boot") search path. ! `--CLASSPATH=PATH' ! Deprecated synonym for `--classpath'. ! `--bootclasspath=PATH' Where to find the standard builtin classes, such as ! `java.lang.String'. ! `--extdirs=PATH' For each directory in the PATH, place the contents of that directory at the end of the class path. ! `CLASSPATH' This is an environment variable which holds a list of paths. The final class path is constructed like so: ! * First come all directories specified via `-I'. ! * If `--classpath' is specified, its value is appended. Otherwise, ! if the `CLASSPATH' environment variable is specified, then its ! value is appended. Otherwise, the current directory (`"."') is appended. ! * If `--bootclasspath' was specified, append its value. Otherwise, ! append the built-in system directory, `libgcj.jar'. ! * Finally, if `--extdirs' was specified, append the contents of the specified directories at the end of the class path. Otherwise, append the contents of the built-in extdirs at ! `$(prefix)/share/java/ext'. ! The classfile built by `gcj' for the class `java.lang.Object' (and ! placed in `libgcj.jar') contains a special zero length attribute ! `gnu.gcj.gcj-compiled'. The compiler looks for this attribute when ! loading `java.lang.Object' and will report an error if it isn't found, unless it compiles to bytecode (the option ! `-fforce-classes-archive-check' can be used to override this behavior ! in this particular case.) ! `-fforce-classes-archive-check' This forces the compiler to always check for the special zero ! length attribute `gnu.gcj.gcj-compiled' in `java.lang.Object' and issue an error if it isn't found. ! `-fsource=VERSION' ! This option is used to choose the source version accepted by ! `gcj'. The default is `1.5'.  File: gcj.info, Node: Encodings, Next: Warnings, Prev: Input Options, Up: Invoking gcj *************** File: gcj.info, Node: Encodings, Next: *** 1439,1461 **** ============= The Java programming language uses Unicode throughout. In an effort to ! integrate well with other locales, 'gcj' allows '.java' files to be ! written using almost any encoding. 'gcj' knows how to convert these encodings into its internal encoding at compile time. ! You can use the '--encoding=NAME' option to specify an encoding (of a ! particular character set) to use for source files. If this is not ! specified, the default encoding comes from your current locale. If your ! host system has insufficient locale support, then 'gcj' assumes the ! default encoding to be the 'UTF-8' encoding of Unicode. ! To implement '--encoding', 'gcj' simply uses the host platform's ! 'iconv' conversion routine. This means that in practice 'gcj' is limited by the capabilities of the host platform. ! The names allowed for the argument '--encoding' vary from platform to ! platform (since they are not standardized anywhere). However, 'gcj' ! implements the encoding named 'UTF-8' internally, so if you choose to use this for your source files you can be assured that it will work on every host. --- 1454,1476 ---- ============= The Java programming language uses Unicode throughout. In an effort to ! integrate well with other locales, `gcj' allows `.java' files to be ! written using almost any encoding. `gcj' knows how to convert these encodings into its internal encoding at compile time. ! You can use the `--encoding=NAME' option to specify an encoding (of ! a particular character set) to use for source files. If this is not ! specified, the default encoding comes from your current locale. If ! your host system has insufficient locale support, then `gcj' assumes ! the default encoding to be the `UTF-8' encoding of Unicode. ! To implement `--encoding', `gcj' simply uses the host platform's ! `iconv' conversion routine. This means that in practice `gcj' is limited by the capabilities of the host platform. ! The names allowed for the argument `--encoding' vary from platform ! to platform (since they are not standardized anywhere). However, `gcj' ! implements the encoding named `UTF-8' internally, so if you choose to use this for your source files you can be assured that it will work on every host. *************** File: gcj.info, Node: Warnings, Next: *** 1465,1497 **** 1.4 Warnings ============ ! 'gcj' implements several warnings. As with other generic 'gcc' ! warnings, if an option of the form '-Wfoo' enables a warning, then ! '-Wno-foo' will disable it. Here we've chosen to document the form of the warning which will have an effect - the default being the opposite of what is listed. ! '-Wredundant-modifiers' ! With this flag, 'gcj' will warn about redundant modifiers. For ! instance, it will warn if an interface method is declared 'public'. ! '-Wextraneous-semicolon' ! This causes 'gcj' to warn about empty statements. Empty statements have been deprecated. ! '-Wno-out-of-date' ! This option will cause 'gcj' not to warn when a source file is ! newer than its matching class file. By default 'gcj' will warn about this. ! '-Wno-deprecated' Warn if a deprecated class, method, or field is referred to. ! '-Wunused' ! This is the same as 'gcc''s '-Wunused'. ! '-Wall' ! This is the same as '-Wredundant-modifiers -Wextraneous-semicolon -Wunused'.  --- 1480,1512 ---- 1.4 Warnings ============ ! `gcj' implements several warnings. As with other generic `gcc' ! warnings, if an option of the form `-Wfoo' enables a warning, then ! `-Wno-foo' will disable it. Here we've chosen to document the form of the warning which will have an effect - the default being the opposite of what is listed. ! `-Wredundant-modifiers' ! With this flag, `gcj' will warn about redundant modifiers. For ! instance, it will warn if an interface method is declared `public'. ! `-Wextraneous-semicolon' ! This causes `gcj' to warn about empty statements. Empty statements have been deprecated. ! `-Wno-out-of-date' ! This option will cause `gcj' not to warn when a source file is ! newer than its matching class file. By default `gcj' will warn about this. ! `-Wno-deprecated' Warn if a deprecated class, method, or field is referred to. ! `-Wunused' ! This is the same as `gcc''s `-Wunused'. ! `-Wall' ! This is the same as `-Wredundant-modifiers -Wextraneous-semicolon -Wunused'.  *************** File: gcj.info, Node: Linking, Next: C *** 1502,1561 **** To turn a Java application into an executable program, you need to link it with the needed libraries, just as for C or C++. The linker by ! default looks for a global function named 'main'. Since Java does not have global functions, and a collection of Java classes may have more ! than one class with a 'main' method, you need to let the linker know ! which of those 'main' methods it should invoke when starting the application. You can do that in any of these ways: ! * Specify the class containing the desired 'main' method when you ! link the application, using the '--main' flag, described below. * Link the Java package(s) into a shared library (dll) rather than an ! executable. Then invoke the application using the 'gij' program, ! making sure that 'gij' can find the libraries it needs. ! * Link the Java packages(s) with the flag '-lgij', which links in the ! 'main' routine from the 'gij' command. This allows you to select ! the class whose 'main' method you want to run when you run the ! application. You can also use other 'gij' flags, such as '-D' ! flags to set properties. Using the '-lgij' library (rather than ! the 'gij' program of the previous mechanism) has some advantages: it is compatible with static linking, and does not require configuring or installing libraries. ! These 'gij' options relate to linking an executable: ! '--main=CLASSNAME' This option is used when linking to specify the name of the class ! whose 'main' method should be invoked when the resulting executable ! is run. ! '-DNAME[=VALUE]' ! This option can only be used with '--main'. It defines a system property named NAME with value VALUE. If VALUE is not specified then it defaults to the empty string. These system properties are initialized at the program's startup and can be retrieved at ! runtime using the 'java.lang.System.getProperty' method. ! '-lgij' Create an application whose command-line processing is that of the ! 'gij' command. ! This option is an alternative to using '--main'; you cannot use both. ! '-static-libgcj' This option causes linking to be done against a static version of the libgcj runtime library. This option is only available if corresponding linker support exists. *Caution:* Static linking of libgcj may cause essential parts of libgcj to be omitted. Some parts of libgcj use reflection to load ! classes at runtime. Since the linker does not see these references ! at link time, it can omit the referred to classes. The result is ! usually (but not always) a 'ClassNotFoundException' being thrown at ! runtime. Caution must be used when using this option. For more ! details see: !  File: gcj.info, Node: Code Generation, Next: Configure-time Options, Prev: Linking, Up: Invoking gcj --- 1517,1578 ---- To turn a Java application into an executable program, you need to link it with the needed libraries, just as for C or C++. The linker by ! default looks for a global function named `main'. Since Java does not have global functions, and a collection of Java classes may have more ! than one class with a `main' method, you need to let the linker know ! which of those `main' methods it should invoke when starting the application. You can do that in any of these ways: ! * Specify the class containing the desired `main' method when you ! link the application, using the `--main' flag, described below. ! * Link the Java package(s) into a shared library (dll) rather than an ! executable. Then invoke the application using the `gij' program, ! making sure that `gij' can find the libraries it needs. ! ! * Link the Java packages(s) with the flag `-lgij', which links in ! the `main' routine from the `gij' command. This allows you to ! select the class whose `main' method you want to run when you run ! the application. You can also use other `gij' flags, such as `-D' ! flags to set properties. Using the `-lgij' library (rather than ! the `gij' program of the previous mechanism) has some advantages: it is compatible with static linking, and does not require configuring or installing libraries. ! These `gij' options relate to linking an executable: ! `--main=CLASSNAME' This option is used when linking to specify the name of the class ! whose `main' method should be invoked when the resulting ! executable is run. ! `-DNAME[=VALUE]' ! This option can only be used with `--main'. It defines a system property named NAME with value VALUE. If VALUE is not specified then it defaults to the empty string. These system properties are initialized at the program's startup and can be retrieved at ! runtime using the `java.lang.System.getProperty' method. ! `-lgij' Create an application whose command-line processing is that of the ! `gij' command. ! This option is an alternative to using `--main'; you cannot use both. ! `-static-libgcj' This option causes linking to be done against a static version of the libgcj runtime library. This option is only available if corresponding linker support exists. *Caution:* Static linking of libgcj may cause essential parts of libgcj to be omitted. Some parts of libgcj use reflection to load ! classes at runtime. Since the linker does not see these ! references at link time, it can omit the referred to classes. The ! result is usually (but not always) a `ClassNotFoundException' ! being thrown at runtime. Caution must be used when using this ! option. For more details see: ! `http://gcc.gnu.org/wiki/Statically%20linking%20libgcj'  File: gcj.info, Node: Code Generation, Next: Configure-time Options, Prev: Linking, Up: Invoking gcj *************** File: gcj.info, Node: Code Generation, *** 1563,1745 **** 1.6 Code Generation =================== ! In addition to the many 'gcc' options controlling code generation, 'gcj' ! has several options specific to itself. ! '-C' ! This option is used to tell 'gcj' to generate bytecode ('.class' files) rather than object code. ! '--resource RESOURCE-NAME' ! This option is used to tell 'gcj' to compile the contents of a ! given file to object code so it may be accessed at runtime with the ! core protocol handler as 'core:/RESOURCE-NAME'. Note that RESOURCE-NAME is the name of the resource as found at runtime; for ! instance, it could be used in a call to 'ResourceBundle.getBundle'. The actual file name to be compiled this way must be specified separately. ! '-ftarget=VERSION' ! This can be used with '-C' to choose the version of bytecode ! emitted by 'gcj'. The default is '1.5'. When not generating bytecode, this option has no effect. ! '-d DIRECTORY' ! When used with '-C', this causes all generated '.class' files to be ! put in the appropriate subdirectory of DIRECTORY. By default they ! will be put in subdirectories of the current working directory. ! '-fno-bounds-check' ! By default, 'gcj' generates code which checks the bounds of all array indexing operations. With this option, these checks are omitted, which can improve performance for code that uses arrays extensively. Note that this can result in unpredictable behavior if the code in question actually does violate array bounds constraints. It is safe to use this option if you are sure that ! your code will never throw an 'ArrayIndexOutOfBoundsException'. ! '-fno-store-check' Don't generate array store checks. When storing objects into arrays, a runtime check is normally generated in order to ensure ! that the object is assignment compatible with the component type of ! the array (which may not be known at compile-time). With this ! option, these checks are omitted. This can improve performance for ! code which stores objects into arrays frequently. It is safe to ! use this option if you are sure your code will never throw an ! 'ArrayStoreException'. ! '-fjni' ! With 'gcj' there are two options for writing native methods: CNI ! and JNI. By default 'gcj' assumes you are using CNI. If you are compiling a class with native methods, and these methods are ! implemented using JNI, then you must use '-fjni'. This option ! causes 'gcj' to generate stubs which will invoke the underlying JNI methods. ! '-fno-assert' ! Don't recognize the 'assert' keyword. This is for compatibility with older versions of the language specification. ! '-fno-optimize-static-class-initialization' ! When the optimization level is greater or equal to '-O2', 'gcj' will try to optimize the way calls into the runtime are made to initialize static classes upon their first use (this optimization ! isn't carried out if '-C' was specified.) When compiling to native ! code, '-fno-optimize-static-class-initialization' will turn this optimization off, regardless of the optimization level in use. ! '--disable-assertions[=CLASS-OR-PACKAGE]' Don't include code for checking assertions in the compiled code. ! If '=CLASS-OR-PACKAGE' is missing disables assertion code generation for all classes, unless overridden by a more specific ! '--enable-assertions' flag. If CLASS-OR-PACKAGE is a class name, ! only disables generating assertion checks within the named class or ! its inner classes. If CLASS-OR-PACKAGE is a package name, disables ! generating assertion checks within the named package or a subpackage. By default, assertions are enabled when generating class files or when not optimizing, and disabled when generating optimized binaries. ! '--enable-assertions[=CLASS-OR-PACKAGE]' Generates code to check assertions. The option is perhaps misnamed, as you still need to turn on assertion checking at run-time, and we don't support any easy way to do that. So this flag isn't very useful yet, except to partially override ! '--disable-assertions'. ! '-findirect-dispatch' ! 'gcj' has a special binary compatibility ABI, which is enabled by ! the '-findirect-dispatch' option. In this mode, the code generated ! by 'gcj' honors the binary compatibility guarantees in the Java ! Language Specification, and the resulting object files do not need ! to be directly linked against their dependencies. Instead, all ! dependencies are looked up at runtime. This allows free mixing of ! interpreted and compiled code. ! Note that, at present, '-findirect-dispatch' can only be used when ! compiling '.class' files. It will not work when compiling from source. CNI also does not yet work with the binary compatibility ! ABI. These restrictions will be lifted in some future release. However, if you compile CNI code with the standard ABI, you can call it from code built with the binary compatibility ABI. ! '-fbootstrap-classes' ! This option can be use to tell 'libgcj' that the compiled classes should be loaded by the bootstrap loader, not the system class loader. By default, if you compile a class and link it into an ! executable, it will be treated as if it was loaded using the system ! class loader. This is convenient, as it means that things like ! 'Class.forName()' will search 'CLASSPATH' to find the desired class. ! '-freduced-reflection' ! This option causes the code generated by 'gcj' to contain a reduced ! amount of the class meta-data used to support runtime reflection. ! The cost of this savings is the loss of the ability to use certain ! reflection capabilities of the standard Java runtime environment. ! When set all meta-data except for that which is needed to obtain ! correct runtime semantics is eliminated. ! For code that does not use reflection (i.e. serialization, RMI, ! CORBA or call methods in the 'java.lang.reflect' package), ! '-freduced-reflection' will result in proper operation with a savings in executable code size. ! JNI ('-fjni') and the binary compatibility ABI ! ('-findirect-dispatch') do not work properly without full ! reflection meta-data. Because of this, it is an error to use these ! options with '-freduced-reflection'. *Caution:* If there is no reflection meta-data, code that uses a ! 'SecurityManager' may not work properly. Also calling ! 'Class.forName()' may fail if the calling method has no reflection meta-data.  File: gcj.info, Node: Configure-time Options, Prev: Code Generation, Up: Invoking gcj 1.7 Configure-time Options ========================== ! Some 'gcj' code generations options affect the resulting ABI, and so can ! only be meaningfully given when 'libgcj', the runtime package, is ! configured. 'libgcj' puts the appropriate options from this group into ! a 'spec' file which is read by 'gcj'. These options are listed here for ! completeness; if you are using 'libgcj' then you won't want to touch ! these options. ! '-fuse-boehm-gc' This enables the use of the Boehm GC bitmap marking code. In ! particular this causes 'gcj' to put an object marking descriptor into each vtable. ! '-fhash-synchronization' ! By default, synchronization data (the data used for 'synchronize', ! 'wait', and 'notify') is pointed to by a word in each object. With ! this option 'gcj' assumes that this information is stored in a hash ! table and not in the object itself. ! '-fuse-divide-subroutine' On some systems, a library routine is called to perform integer division. This is required to get exception handling correct when dividing by zero. ! '-fcheck-references' On some systems it's necessary to insert inline checks whenever accessing an object via a reference. On other systems you won't ! need this because null pointer accesses are caught automatically by ! the processor. ! '-fuse-atomic-builtins' On some systems, GCC can generate code for built-in atomic operations. Use this option to force gcj to use these builtins when compiling Java code. Where this capability is present it should be automatically detected, so you won't usually need to use this option.  File: gcj.info, Node: Compatibility, Next: Invoking jcf-dump, Prev: Invoking gcj, Up: Top --- 1580,1765 ---- 1.6 Code Generation =================== ! In addition to the many `gcc' options controlling code generation, ! `gcj' has several options specific to itself. ! `-C' ! This option is used to tell `gcj' to generate bytecode (`.class' files) rather than object code. ! `--resource RESOURCE-NAME' ! This option is used to tell `gcj' to compile the contents of a ! given file to object code so it may be accessed at runtime with ! the core protocol handler as `core:/RESOURCE-NAME'. Note that RESOURCE-NAME is the name of the resource as found at runtime; for ! instance, it could be used in a call to `ResourceBundle.getBundle'. The actual file name to be compiled this way must be specified separately. ! `-ftarget=VERSION' ! This can be used with `-C' to choose the version of bytecode ! emitted by `gcj'. The default is `1.5'. When not generating bytecode, this option has no effect. ! `-d DIRECTORY' ! When used with `-C', this causes all generated `.class' files to ! be put in the appropriate subdirectory of DIRECTORY. By default ! they will be put in subdirectories of the current working ! directory. ! `-fno-bounds-check' ! By default, `gcj' generates code which checks the bounds of all array indexing operations. With this option, these checks are omitted, which can improve performance for code that uses arrays extensively. Note that this can result in unpredictable behavior if the code in question actually does violate array bounds constraints. It is safe to use this option if you are sure that ! your code will never throw an `ArrayIndexOutOfBoundsException'. ! `-fno-store-check' Don't generate array store checks. When storing objects into arrays, a runtime check is normally generated in order to ensure ! that the object is assignment compatible with the component type ! of the array (which may not be known at compile-time). With this ! option, these checks are omitted. This can improve performance ! for code which stores objects into arrays frequently. It is safe ! to use this option if you are sure your code will never throw an ! `ArrayStoreException'. ! `-fjni' ! With `gcj' there are two options for writing native methods: CNI ! and JNI. By default `gcj' assumes you are using CNI. If you are compiling a class with native methods, and these methods are ! implemented using JNI, then you must use `-fjni'. This option ! causes `gcj' to generate stubs which will invoke the underlying JNI methods. ! `-fno-assert' ! Don't recognize the `assert' keyword. This is for compatibility with older versions of the language specification. ! `-fno-optimize-static-class-initialization' ! When the optimization level is greater or equal to `-O2', `gcj' will try to optimize the way calls into the runtime are made to initialize static classes upon their first use (this optimization ! isn't carried out if `-C' was specified.) When compiling to native ! code, `-fno-optimize-static-class-initialization' will turn this optimization off, regardless of the optimization level in use. ! `--disable-assertions[=CLASS-OR-PACKAGE]' Don't include code for checking assertions in the compiled code. ! If `=CLASS-OR-PACKAGE' is missing disables assertion code generation for all classes, unless overridden by a more specific ! `--enable-assertions' flag. If CLASS-OR-PACKAGE is a class name, ! only disables generating assertion checks within the named class ! or its inner classes. If CLASS-OR-PACKAGE is a package name, ! disables generating assertion checks within the named package or a subpackage. By default, assertions are enabled when generating class files or when not optimizing, and disabled when generating optimized binaries. ! `--enable-assertions[=CLASS-OR-PACKAGE]' Generates code to check assertions. The option is perhaps misnamed, as you still need to turn on assertion checking at run-time, and we don't support any easy way to do that. So this flag isn't very useful yet, except to partially override ! `--disable-assertions'. ! `-findirect-dispatch' ! `gcj' has a special binary compatibility ABI, which is enabled by ! the `-findirect-dispatch' option. In this mode, the code ! generated by `gcj' honors the binary compatibility guarantees in ! the Java Language Specification, and the resulting object files do ! not need to be directly linked against their dependencies. ! Instead, all dependencies are looked up at runtime. This allows ! free mixing of interpreted and compiled code. ! Note that, at present, `-findirect-dispatch' can only be used when ! compiling `.class' files. It will not work when compiling from source. CNI also does not yet work with the binary compatibility ! ABI. These restrictions will be lifted in some future release. However, if you compile CNI code with the standard ABI, you can call it from code built with the binary compatibility ABI. ! `-fbootstrap-classes' ! This option can be use to tell `libgcj' that the compiled classes should be loaded by the bootstrap loader, not the system class loader. By default, if you compile a class and link it into an ! executable, it will be treated as if it was loaded using the ! system class loader. This is convenient, as it means that things ! like `Class.forName()' will search `CLASSPATH' to find the desired class. ! `-freduced-reflection' ! This option causes the code generated by `gcj' to contain a ! reduced amount of the class meta-data used to support runtime ! reflection. The cost of this savings is the loss of the ability to ! use certain reflection capabilities of the standard Java runtime ! environment. When set all meta-data except for that which is ! needed to obtain correct runtime semantics is eliminated. ! For code that does not use reflection (i.e. serialization, RMI, ! CORBA or call methods in the `java.lang.reflect' package), ! `-freduced-reflection' will result in proper operation with a savings in executable code size. ! JNI (`-fjni') and the binary compatibility ABI ! (`-findirect-dispatch') do not work properly without full ! reflection meta-data. Because of this, it is an error to use ! these options with `-freduced-reflection'. *Caution:* If there is no reflection meta-data, code that uses a ! `SecurityManager' may not work properly. Also calling ! `Class.forName()' may fail if the calling method has no reflection meta-data. +  File: gcj.info, Node: Configure-time Options, Prev: Code Generation, Up: Invoking gcj 1.7 Configure-time Options ========================== ! Some `gcj' code generations options affect the resulting ABI, and so ! can only be meaningfully given when `libgcj', the runtime package, is ! configured. `libgcj' puts the appropriate options from this group into ! a `spec' file which is read by `gcj'. These options are listed here ! for completeness; if you are using `libgcj' then you won't want to ! touch these options. ! `-fuse-boehm-gc' This enables the use of the Boehm GC bitmap marking code. In ! particular this causes `gcj' to put an object marking descriptor into each vtable. ! `-fhash-synchronization' ! By default, synchronization data (the data used for `synchronize', ! `wait', and `notify') is pointed to by a word in each object. ! With this option `gcj' assumes that this information is stored in a ! hash table and not in the object itself. ! `-fuse-divide-subroutine' On some systems, a library routine is called to perform integer division. This is required to get exception handling correct when dividing by zero. ! `-fcheck-references' On some systems it's necessary to insert inline checks whenever accessing an object via a reference. On other systems you won't ! need this because null pointer accesses are caught automatically ! by the processor. ! `-fuse-atomic-builtins' On some systems, GCC can generate code for built-in atomic operations. Use this option to force gcj to use these builtins when compiling Java code. Where this capability is present it should be automatically detected, so you won't usually need to use this option. +  File: gcj.info, Node: Compatibility, Next: Invoking jcf-dump, Prev: Invoking gcj, Up: Top *************** File: gcj.info, Node: Compatibility, N *** 1747,1760 **** ************************************** As we believe it is important that the Java platform not be fragmented, ! 'gcj' and 'libgcj' try to conform to the relevant Java specifications. However, limited manpower and incomplete and unclear documentation work ! against us. So, there are caveats to using 'gcj'. * Menu: ! * Limitations:: ! * Extensions::  File: gcj.info, Node: Limitations, Next: Extensions, Up: Compatibility --- 1767,1780 ---- ************************************** As we believe it is important that the Java platform not be fragmented, ! `gcj' and `libgcj' try to conform to the relevant Java specifications. However, limited manpower and incomplete and unclear documentation work ! against us. So, there are caveats to using `gcj'. * Menu: ! * Limitations:: ! * Extensions::  File: gcj.info, Node: Limitations, Next: Extensions, Up: Compatibility *************** File: gcj.info, Node: Limitations, Nex *** 1764,1792 **** This list of compatibility issues is by no means complete. ! * 'gcj' implements the JDK 1.2 language. It supports inner classes ! and the new 1.4 'assert' keyword. It does not yet support the Java ! 2 'strictfp' keyword (it recognizes the keyword but ignores it). ! * 'libgcj' is largely compatible with the JDK 1.2 libraries. ! However, 'libgcj' is missing many packages, most notably ! 'java.awt'. There are also individual missing classes and methods. We currently do not have a list showing differences between ! 'libgcj' and the Java 2 platform. ! * Sometimes the 'libgcj' implementation of a method or class differs from the JDK implementation. This is not always a bug. Still, if ! it affects you, it probably makes sense to report it so that we can ! discuss the appropriate response. ! * 'gcj' does not currently allow for piecemeal replacement of ! components within 'libgcj'. Unfortunately, programmers often want to use newer versions of certain packages, such as those provided by the Apache Software Foundation's Jakarta project. This has ! forced us to place the 'org.w3c.dom' and 'org.xml.sax' packages ! into their own libraries, separate from 'libgcj'. If you intend to use these classes, you must link them explicitly with ! '-l-org-w3c-dom' and '-l-org-xml-sax'. Future versions of 'gcj' may not have this restriction.  --- 1784,1813 ---- This list of compatibility issues is by no means complete. ! * `gcj' implements the JDK 1.2 language. It supports inner classes ! and the new 1.4 `assert' keyword. It does not yet support the ! Java 2 `strictfp' keyword (it recognizes the keyword but ignores ! it). ! * `libgcj' is largely compatible with the JDK 1.2 libraries. ! However, `libgcj' is missing many packages, most notably ! `java.awt'. There are also individual missing classes and methods. We currently do not have a list showing differences between ! `libgcj' and the Java 2 platform. ! * Sometimes the `libgcj' implementation of a method or class differs from the JDK implementation. This is not always a bug. Still, if ! it affects you, it probably makes sense to report it so that we ! can discuss the appropriate response. ! * `gcj' does not currently allow for piecemeal replacement of ! components within `libgcj'. Unfortunately, programmers often want to use newer versions of certain packages, such as those provided by the Apache Software Foundation's Jakarta project. This has ! forced us to place the `org.w3c.dom' and `org.xml.sax' packages ! into their own libraries, separate from `libgcj'. If you intend to use these classes, you must link them explicitly with ! `-l-org-w3c-dom' and `-l-org-xml-sax'. Future versions of `gcj' may not have this restriction.  *************** File: gcj.info, Node: Extensions, Prev *** 1795,1851 **** 2.2 Extra features unique to gcj ================================ ! The main feature of 'gcj' is that it can compile programs written in the ! Java programming language to native code. Most extensions that have ! been added are to facilitate this functionality. ! * 'gcj' makes it easy and efficient to mix code written in Java and C++. *Note About CNI::, for more info on how to use this in your programs. * When you compile your classes into a shared library using ! '-findirect-dispatch' then add them to the system-wide classmap.db ! file using 'gcj-dbtool', they will be automatically loaded by the ! 'libgcj' system classloader. This is the new, preferred classname-to-library resolution mechanism. *Note Invoking gcj-dbtool::, for more information on using the classmap database. * The old classname-to-library lookup mechanism is still supported ! through the 'gnu.gcj.runtime.VMClassLoader.library_control' property, but it is deprecated and will likely be removed in some ! future release. When trying to load a class 'gnu.pkg.SomeClass' the system classloader will first try to load the shared library ! 'lib-gnu-pkg-SomeClass.so', if that fails to load the class then it ! will try to load 'lib-gnu-pkg.so' and finally when the class is ! still not loaded it will try to load 'lib-gnu.so'. Note that all ! '.'s will be transformed into '-'s and that searching for inner classes starts with their outermost outer class. If the class cannot be found this way the system classloader tries to use the ! 'libgcj' bytecode interpreter to load the class from the standard classpath. This process can be controlled to some degree via the ! 'gnu.gcj.runtime.VMClassLoader.library_control' property; *Note libgcj Runtime Properties::. ! * 'libgcj' includes a special 'gcjlib' URL type. A URL of this form ! is like a 'jar' URL, and looks like ! 'gcjlib:/path/to/shared/library.so!/path/to/resource'. An access ! to one of these URLs causes the shared library to be 'dlopen()'d, and then the resource is looked for in that library. These URLs are most useful when used in conjunction with ! 'java.net.URLClassLoader'. Note that, due to implementation limitations, currently any such URL can be accessed by only one class loader, and libraries are never unloaded. This means some ! care must be exercised to make sure that a 'gcjlib' URL is not accessed by more than one class loader at once. In a future release this limitation will be lifted, and such libraries will be mapped privately. ! * A program compiled by 'gcj' will examine the 'GCJ_PROPERTIES' environment variable and change its behavior in some ways. In ! particular 'GCJ_PROPERTIES' holds a list of assignments to global ! properties, such as would be set with the '-D' option to 'java'. ! For instance, 'java.compiler=gcj' is a valid (but currently ! meaningless) setting.  File: gcj.info, Node: Invoking jcf-dump, Next: Invoking gij, Prev: Compatibility, Up: Top --- 1816,1873 ---- 2.2 Extra features unique to gcj ================================ ! The main feature of `gcj' is that it can compile programs written in ! the Java programming language to native code. Most extensions that ! have been added are to facilitate this functionality. ! * `gcj' makes it easy and efficient to mix code written in Java and C++. *Note About CNI::, for more info on how to use this in your programs. * When you compile your classes into a shared library using ! `-findirect-dispatch' then add them to the system-wide classmap.db ! file using `gcj-dbtool', they will be automatically loaded by the ! `libgcj' system classloader. This is the new, preferred classname-to-library resolution mechanism. *Note Invoking gcj-dbtool::, for more information on using the classmap database. * The old classname-to-library lookup mechanism is still supported ! through the `gnu.gcj.runtime.VMClassLoader.library_control' property, but it is deprecated and will likely be removed in some ! future release. When trying to load a class `gnu.pkg.SomeClass' the system classloader will first try to load the shared library ! `lib-gnu-pkg-SomeClass.so', if that fails to load the class then ! it will try to load `lib-gnu-pkg.so' and finally when the class is ! still not loaded it will try to load `lib-gnu.so'. Note that all ! `.'s will be transformed into `-'s and that searching for inner classes starts with their outermost outer class. If the class cannot be found this way the system classloader tries to use the ! `libgcj' bytecode interpreter to load the class from the standard classpath. This process can be controlled to some degree via the ! `gnu.gcj.runtime.VMClassLoader.library_control' property; *Note libgcj Runtime Properties::. ! * `libgcj' includes a special `gcjlib' URL type. A URL of this form ! is like a `jar' URL, and looks like ! `gcjlib:/path/to/shared/library.so!/path/to/resource'. An access ! to one of these URLs causes the shared library to be `dlopen()'d, and then the resource is looked for in that library. These URLs are most useful when used in conjunction with ! `java.net.URLClassLoader'. Note that, due to implementation limitations, currently any such URL can be accessed by only one class loader, and libraries are never unloaded. This means some ! care must be exercised to make sure that a `gcjlib' URL is not accessed by more than one class loader at once. In a future release this limitation will be lifted, and such libraries will be mapped privately. ! * A program compiled by `gcj' will examine the `GCJ_PROPERTIES' environment variable and change its behavior in some ways. In ! particular `GCJ_PROPERTIES' holds a list of assignments to global ! properties, such as would be set with the `-D' option to `java'. ! For instance, `java.compiler=gcj' is a valid (but currently ! meaningless) setting. !  File: gcj.info, Node: Invoking jcf-dump, Next: Invoking gij, Prev: Compatibility, Up: Top *************** File: gcj.info, Node: Invoking jcf-dump *** 1853,1889 **** 3 Invoking jcf-dump ******************* ! This is a class file examiner, similar to 'javap'. It will print information about a number of classes, which are specified by class name or file name. ! '-c' Disassemble method bodies. By default method bodies are not printed. ! '--print-constants' Print the constant pool. When printing a reference to a constant also print its index in the constant pool. ! '--javap' ! Generate output in 'javap' format. The implementation of this feature is very incomplete. ! '--classpath=PATH' ! '--CLASSPATH=PATH' ! '-IDIRECTORY' ! '-o FILE' ! These options as the same as the corresponding 'gcj' options. ! '--help' Print help, then exit. ! '--version' Print version number, then exit. ! '-v, --verbose' Print extra information while running. Implies ! '--print-constants'.  File: gcj.info, Node: Invoking gij, Next: Invoking gcj-dbtool, Prev: Invoking jcf-dump, Up: Top --- 1875,1911 ---- 3 Invoking jcf-dump ******************* ! This is a class file examiner, similar to `javap'. It will print information about a number of classes, which are specified by class name or file name. ! `-c' Disassemble method bodies. By default method bodies are not printed. ! `--print-constants' Print the constant pool. When printing a reference to a constant also print its index in the constant pool. ! `--javap' ! Generate output in `javap' format. The implementation of this feature is very incomplete. ! `--classpath=PATH' ! `--CLASSPATH=PATH' ! `-IDIRECTORY' ! `-o FILE' ! These options as the same as the corresponding `gcj' options. ! `--help' Print help, then exit. ! `--version' Print version number, then exit. ! `-v, --verbose' Print extra information while running. Implies ! `--print-constants'.  File: gcj.info, Node: Invoking gij, Next: Invoking gcj-dbtool, Prev: Invoking jcf-dump, Up: Top *************** File: gcj.info, Node: Invoking gij, Ne *** 1891,1990 **** 4 Invoking gij ************** ! 'gij' is a Java bytecode interpreter included with 'libgcj'. 'gij' is not available on every platform; porting it requires a small amount of assembly programming which has not been done for all the targets ! supported by 'gcj'. ! The primary argument to 'gij' is the name of a class or, with '-jar', ! a jar file. Options before this argument are interpreted by 'gij'; ! remaining options are passed to the interpreted program. ! If a class name is specified and this class does not have a 'main' ! method with the appropriate signature (a 'static void' method with a ! 'String[]' as its sole argument), then 'gij' will print an error and exit. ! If a jar file is specified then 'gij' will use information in it to ! determine which class' 'main' method will be invoked. ! 'gij' will invoke the 'main' method with all the remaining command-line options. ! Note that 'gij' is not limited to interpreting code. Because ! 'libgcj' includes a class loader which can dynamically load shared ! objects, it is possible to give 'gij' the name of a class which has been ! compiled and put into a shared library on the class path. ! '-cp PATH' ! '-classpath PATH' Set the initial class path. The class path is used for finding class and resource files. If specified, this option overrides the ! 'CLASSPATH' environment variable. Note that this option is ignored ! if '-jar' is used. ! '-DNAME[=VALUE]' This defines a system property named NAME with value VALUE. If ! VALUE is not specified then it defaults to the empty string. These ! system properties are initialized at the program's startup and can ! be retrieved at runtime using the 'java.lang.System.getProperty' ! method. ! '-ms=NUMBER' ! Equivalent to '-Xms'. ! '-mx=NUMBER' ! Equivalent to '-Xmx'. ! '-noverify' ! Do not verify compliance of bytecode with the VM specification. In ! addition, this option disables type verification which is otherwise ! performed on BC-ABI compiled code. ! '-X' ! '-XARGUMENT' ! Supplying '-X' by itself will cause 'gij' to list all the supported ! '-X' options. Currently these options are supported: ! '-XmsSIZE' Set the initial heap size. ! '-XmxSIZE' Set the maximum heap size. ! '-XssSIZE' Set the thread stack size. ! Unrecognized '-X' options are ignored, for compatibility with other ! runtimes. ! '-jar' ! This indicates that the name passed to 'gij' should be interpreted as the name of a jar file, not a class. ! '--help' ! '-?' Print help, then exit. ! '--showversion' Print version number and continue. ! '--fullversion' Print detailed version information, then exit. ! '--version' Print version number, then exit. ! '-verbose' ! '-verbose:class' ! Each time a class is initialized, print a short message on standard ! error. ! 'gij' also recognizes and ignores the following options, for ! compatibility with existing application launch scripts: '-client', ! '-server', '-hotspot', '-jrockit', '-agentlib', '-agentpath', '-debug', ! '-d32', '-d64', '-javaagent', '-noclassgc', '-verify', and ! '-verifyremote'.  File: gcj.info, Node: Invoking gcj-dbtool, Next: Invoking jv-convert, Prev: Invoking gij, Up: Top --- 1913,2012 ---- 4 Invoking gij ************** ! `gij' is a Java bytecode interpreter included with `libgcj'. `gij' is not available on every platform; porting it requires a small amount of assembly programming which has not been done for all the targets ! supported by `gcj'. ! The primary argument to `gij' is the name of a class or, with ! `-jar', a jar file. Options before this argument are interpreted by ! `gij'; remaining options are passed to the interpreted program. ! If a class name is specified and this class does not have a `main' ! method with the appropriate signature (a `static void' method with a ! `String[]' as its sole argument), then `gij' will print an error and exit. ! If a jar file is specified then `gij' will use information in it to ! determine which class' `main' method will be invoked. ! `gij' will invoke the `main' method with all the remaining command-line options. ! Note that `gij' is not limited to interpreting code. Because ! `libgcj' includes a class loader which can dynamically load shared ! objects, it is possible to give `gij' the name of a class which has ! been compiled and put into a shared library on the class path. ! `-cp PATH' ! `-classpath PATH' Set the initial class path. The class path is used for finding class and resource files. If specified, this option overrides the ! `CLASSPATH' environment variable. Note that this option is ! ignored if `-jar' is used. ! `-DNAME[=VALUE]' This defines a system property named NAME with value VALUE. If ! VALUE is not specified then it defaults to the empty string. ! These system properties are initialized at the program's startup ! and can be retrieved at runtime using the ! `java.lang.System.getProperty' method. ! `-ms=NUMBER' ! Equivalent to `-Xms'. ! `-mx=NUMBER' ! Equivalent to `-Xmx'. ! `-noverify' ! Do not verify compliance of bytecode with the VM specification. In ! addition, this option disables type verification which is ! otherwise performed on BC-ABI compiled code. ! `-X' ! `-XARGUMENT' ! Supplying `-X' by itself will cause `gij' to list all the ! supported `-X' options. Currently these options are supported: ! `-XmsSIZE' Set the initial heap size. ! `-XmxSIZE' Set the maximum heap size. ! `-XssSIZE' Set the thread stack size. ! Unrecognized `-X' options are ignored, for compatibility with ! other runtimes. ! `-jar' ! This indicates that the name passed to `gij' should be interpreted as the name of a jar file, not a class. ! `--help' ! `-?' Print help, then exit. ! `--showversion' Print version number and continue. ! `--fullversion' Print detailed version information, then exit. ! `--version' Print version number, then exit. ! `-verbose' ! `-verbose:class' ! Each time a class is initialized, print a short message on ! standard error. ! `gij' also recognizes and ignores the following options, for ! compatibility with existing application launch scripts: `-client', ! `-server', `-hotspot', `-jrockit', `-agentlib', `-agentpath', `-debug', ! `-d32', `-d64', `-javaagent', `-noclassgc', `-verify', and ! `-verifyremote'.  File: gcj.info, Node: Invoking gcj-dbtool, Next: Invoking jv-convert, Prev: Invoking gij, Up: Top *************** File: gcj.info, Node: Invoking gcj-dbto *** 1992,2093 **** 5 Invoking gcj-dbtool. ********************** ! 'gcj-dbtool' is a tool for creating and manipulating class file mapping ! databases. 'libgcj' can use these databases to find a shared library corresponding to the bytecode representation of a class. This functionality is useful for ahead-of-time compilation of a program that ! has no knowledge of 'gcj'. ! 'gcj-dbtool' works best if all the jar files added to it are compiled ! using '-findirect-dispatch'. ! Note that 'gcj-dbtool' is currently available as "preview technology". We believe it is a reasonable way to allow application-transparent ahead-of-time compilation, but this is an unexplored area. We welcome your comments. ! '-n DBFILE [SIZE]' This creates a new database. Currently, databases cannot be resized; you can choose a larger initial size if desired. The default size is 32,749. ! '-a DBFILE JARFILE LIB' ! '-f DBFILE JARFILE LIB' This adds a jar file to the database. For each class file in the jar, a cryptographic signature of the bytecode representation of the class is recorded in the database. At runtime, a class is looked up by its signature and the compiled form of the class is ! looked for in the corresponding shared library. The '-a' option ! will verify that LIB exists before adding it to the database; '-f' skips this check. ! '[-][-0] -m DBFILE DBFILE,[DBFILE]' Merge a number of databases. The output database overwrites any existing database. To add databases into an existing database, include the destination in the list of sources. ! If '-' or '-0' are used, the list of files to read is taken from ! standard input instead of the command line. For '-0', Input filenames are terminated by a null character instead of by whitespace. Useful when arguments might contain white space. The GNU find -print0 option produces input suitable for this mode. ! '-t DBFILE' Test a database. ! '-l DBFILE' List the contents of a database. ! '-p' Print the name of the default database. If there is no default ! database, this prints a blank line. If LIBDIR is specified, use it ! instead of the default library directory component of the database ! name. ! '--help' Print a help message, then exit. ! '--version' ! '-v' Print version information, then exit.  File: gcj.info, Node: Invoking jv-convert, Next: Invoking grmic, Prev: Invoking gcj-dbtool, Up: Top 6 Invoking jv-convert ********************* ! 'jv-convert' ['OPTION'] ... [INPUTFILE [OUTPUTFILE]] ! 'jv-convert' is a utility included with 'libgcj' which converts a ! file from one encoding to another. It is similar to the Unix 'iconv' utility. ! The encodings supported by 'jv-convert' are platform-dependent. Currently there is no way to get a list of all supported encodings. ! '--encoding NAME' ! '--from NAME' Use NAME as the input encoding. The default is the current locale's encoding. ! '--to NAME' ! Use NAME as the output encoding. The default is the 'JavaSrc' ! encoding; this is ASCII with '\u' escapes for non-ASCII characters. ! '-i FILE' Read from FILE. The default is to read from standard input. ! '-o FILE' Write to FILE. The default is to write to standard output. ! '--reverse' Swap the input and output encodings. ! '--help' Print a help message, then exit. ! '--version' Print version information, then exit.  --- 2014,2116 ---- 5 Invoking gcj-dbtool. ********************** ! `gcj-dbtool' is a tool for creating and manipulating class file mapping ! databases. `libgcj' can use these databases to find a shared library corresponding to the bytecode representation of a class. This functionality is useful for ahead-of-time compilation of a program that ! has no knowledge of `gcj'. ! `gcj-dbtool' works best if all the jar files added to it are ! compiled using `-findirect-dispatch'. ! Note that `gcj-dbtool' is currently available as "preview technology". We believe it is a reasonable way to allow application-transparent ahead-of-time compilation, but this is an unexplored area. We welcome your comments. ! `-n DBFILE [SIZE]' This creates a new database. Currently, databases cannot be resized; you can choose a larger initial size if desired. The default size is 32,749. ! `-a DBFILE JARFILE LIB' ! `-f DBFILE JARFILE LIB' This adds a jar file to the database. For each class file in the jar, a cryptographic signature of the bytecode representation of the class is recorded in the database. At runtime, a class is looked up by its signature and the compiled form of the class is ! looked for in the corresponding shared library. The `-a' option ! will verify that LIB exists before adding it to the database; `-f' skips this check. ! `[`-'][`-0'] -m DBFILE DBFILE,[DBFILE]' Merge a number of databases. The output database overwrites any existing database. To add databases into an existing database, include the destination in the list of sources. ! If `-' or `-0' are used, the list of files to read is taken from ! standard input instead of the command line. For `-0', Input filenames are terminated by a null character instead of by whitespace. Useful when arguments might contain white space. The GNU find -print0 option produces input suitable for this mode. ! `-t DBFILE' Test a database. ! `-l DBFILE' List the contents of a database. ! `-p' Print the name of the default database. If there is no default ! database, this prints a blank line. If LIBDIR is specified, use ! it instead of the default library directory component of the ! database name. ! `--help' Print a help message, then exit. ! `--version' ! `-v' Print version information, then exit. +  File: gcj.info, Node: Invoking jv-convert, Next: Invoking grmic, Prev: Invoking gcj-dbtool, Up: Top 6 Invoking jv-convert ********************* ! `jv-convert' [`OPTION'] ... [INPUTFILE [OUTPUTFILE]] ! `jv-convert' is a utility included with `libgcj' which converts a ! file from one encoding to another. It is similar to the Unix `iconv' utility. ! The encodings supported by `jv-convert' are platform-dependent. Currently there is no way to get a list of all supported encodings. ! `--encoding NAME' ! `--from NAME' Use NAME as the input encoding. The default is the current locale's encoding. ! `--to NAME' ! Use NAME as the output encoding. The default is the `JavaSrc' ! encoding; this is ASCII with `\u' escapes for non-ASCII characters. ! `-i FILE' Read from FILE. The default is to read from standard input. ! `-o FILE' Write to FILE. The default is to write to standard output. ! `--reverse' Swap the input and output encodings. ! `--help' Print a help message, then exit. ! `--version' Print version information, then exit.  *************** File: gcj.info, Node: Invoking grmic, *** 2096,2144 **** 7 Invoking grmic **************** ! 'grmic' ['OPTION'] ... CLASS ... ! 'grmic' is a utility included with 'libgcj' which generates stubs for ! remote objects. Note that this program isn't yet fully compatible with the JDK ! 'grmic'. Some options, such as '-classpath', are recognized but currently ignored. We have left these options undocumented for now. ! Long options can also be given with a GNU-style leading '--'. For ! instance, '--help' is accepted. ! '-keep' ! '-keepgenerated' ! By default, 'grmic' deletes intermediate files. Either of these options causes it not to delete such files. ! '-v1.1' ! Cause 'grmic' to create stubs and skeletons for the 1.1 protocol version. ! '-vcompat' ! Cause 'grmic' to create stubs and skeletons compatible with both the 1.1 and 1.2 protocol versions. This is the default. ! '-v1.2' ! Cause 'grmic' to create stubs and skeletons for the 1.2 protocol version. ! '-nocompile' Don't compile the generated files. ! '-verbose' ! Print information about what 'grmic' is doing. ! '-d DIRECTORY' ! Put output files in DIRECTORY. By default the files are put in the ! current working directory. ! '-help' Print a help message, then exit. ! '-version' Print version information, then exit.  --- 2119,2167 ---- 7 Invoking grmic **************** ! `grmic' [`OPTION'] ... CLASS ... ! `grmic' is a utility included with `libgcj' which generates stubs ! for remote objects. Note that this program isn't yet fully compatible with the JDK ! `grmic'. Some options, such as `-classpath', are recognized but currently ignored. We have left these options undocumented for now. ! Long options can also be given with a GNU-style leading `--'. For ! instance, `--help' is accepted. ! `-keep' ! `-keepgenerated' ! By default, `grmic' deletes intermediate files. Either of these options causes it not to delete such files. ! `-v1.1' ! Cause `grmic' to create stubs and skeletons for the 1.1 protocol version. ! `-vcompat' ! Cause `grmic' to create stubs and skeletons compatible with both the 1.1 and 1.2 protocol versions. This is the default. ! `-v1.2' ! Cause `grmic' to create stubs and skeletons for the 1.2 protocol version. ! `-nocompile' Don't compile the generated files. ! `-verbose' ! Print information about what `grmic' is doing. ! `-d DIRECTORY' ! Put output files in DIRECTORY. By default the files are put in ! the current working directory. ! `-help' Print a help message, then exit. ! `-version' Print version information, then exit.  *************** File: gcj.info, Node: Invoking gc-analy *** 2147,2164 **** 8 Invoking gc-analyze ********************* ! 'gc-analyze' ['OPTION'] ... [FILE] ! 'gc-analyze' prints an analysis of a GC memory dump to standard out. The memory dumps may be created by calling ! 'gnu.gcj.util.GCInfo.enumerate(String namePrefix)' from java code. A memory dump will be created on an out of memory condition if ! 'gnu.gcj.util.GCInfo.setOOMDump(String namePrefix)' is called before the ! out of memory occurs. ! Running this program will create two files: 'TestDump001' and ! 'TestDump001.bytes'. import gnu.gcj.util.*; import java.util.*; --- 2170,2187 ---- 8 Invoking gc-analyze ********************* ! `gc-analyze' [`OPTION'] ... [FILE] ! `gc-analyze' prints an analysis of a GC memory dump to standard out. The memory dumps may be created by calling ! `gnu.gcj.util.GCInfo.enumerate(String namePrefix)' from java code. A memory dump will be created on an out of memory condition if ! `gnu.gcj.util.GCInfo.setOOMDump(String namePrefix)' is called before ! the out of memory occurs. ! Running this program will create two files: `TestDump001' and ! `TestDump001.bytes'. import gnu.gcj.util.*; import java.util.*; *************** out of memory occurs. *** 2180,2200 **** gc-analyze -v TestDump001 ! '--verbose' ! '-v' Verbose output. ! '-p TOOL-PREFIX' ! Prefix added to the names of the 'nm' and 'readelf' commands. ! '-d DIRECTORY' Directory that contains the executable and shared libraries used when the dump was generated. ! '--help' Print a help message, then exit. ! '--version' Print version information, then exit.  --- 2203,2223 ---- gc-analyze -v TestDump001 ! `--verbose' ! `-v' Verbose output. ! `-p TOOL-PREFIX' ! Prefix added to the names of the `nm' and `readelf' commands. ! `-d DIRECTORY' Directory that contains the executable and shared libraries used when the dump was generated. ! `--help' Print a help message, then exit. ! `--version' Print version information, then exit.  *************** File: gcj.info, Node: Invoking aot-comp *** 2203,2243 **** 9 Invoking aot-compile ********************** ! 'aot-compile' is a script that searches a directory for Java bytecode ! (as class files, or in jars) and uses 'gcj' to compile it to native code ! and generate the databases from it. ! '-M, --make=PATH' ! Specify the path to the 'make' executable to use. ! '-C, --gcj=PATH' ! Specify the path to the 'gcj' executable to use. ! '-D, --dbtool=PATH' ! Specify the path to the 'gcj-dbtool' executable to use. ! '-m, --makeflags=FLAGS' ! Specify flags to pass to 'make' during the build. ! '-c, --gcjflags=FLAGS' ! Specify flags to pass to 'gcj' during compilation, in addition to '-fPIC -findirect-dispatch -fjni'. ! '-l, --ldflags=FLAGS' ! Specify flags to pass to 'gcj' during linking, in addition to '-Wl,-Bsymbolic'. ! '-e, --exclude=PATH' Do not compile PATH.  File: gcj.info, Node: Invoking rebuild-gcj-db, Next: About CNI, Prev: Invoking aot-compile, Up: Top 10 Invoking rebuild-gcj-db ************************** ! 'rebuild-gcj-db' is a script that merges the per-solib databases made by ! 'aot-compile' into one system-wide database so 'gij' can find the solibs.  --- 2226,2267 ---- 9 Invoking aot-compile ********************** ! `aot-compile' is a script that searches a directory for Java bytecode ! (as class files, or in jars) and uses `gcj' to compile it to native ! code and generate the databases from it. ! `-M, --make=PATH' ! Specify the path to the `make' executable to use. ! `-C, --gcj=PATH' ! Specify the path to the `gcj' executable to use. ! `-D, --dbtool=PATH' ! Specify the path to the `gcj-dbtool' executable to use. ! `-m, --makeflags=FLAGS' ! Specify flags to pass to `make' during the build. ! `-c, --gcjflags=FLAGS' ! Specify flags to pass to `gcj' during compilation, in addition to '-fPIC -findirect-dispatch -fjni'. ! `-l, --ldflags=FLAGS' ! Specify flags to pass to `gcj' during linking, in addition to '-Wl,-Bsymbolic'. ! `-e, --exclude=PATH' Do not compile PATH. +  File: gcj.info, Node: Invoking rebuild-gcj-db, Next: About CNI, Prev: Invoking aot-compile, Up: Top 10 Invoking rebuild-gcj-db ************************** ! `rebuild-gcj-db' is a script that merges the per-solib databases made by ! `aot-compile' into one system-wide database so `gij' can find the solibs.  *************** File: gcj.info, Node: Basic concepts, *** 2280,2288 **** In terms of languages features, Java is mostly a subset of C++. Java has a few important extensions, plus a powerful standard class library, but on the whole that does not change the basic similarity. Java is a ! hybrid object-oriented language, with a few native types, in addition to ! class types. It is class-based, where a class may have static as well ! as per-object fields, and static as well as instance methods. Non-static methods may be virtual, and may be overloaded. Overloading is resolved at compile time by matching the actual argument types against the parameter types. Virtual methods are implemented using --- 2304,2312 ---- In terms of languages features, Java is mostly a subset of C++. Java has a few important extensions, plus a powerful standard class library, but on the whole that does not change the basic similarity. Java is a ! hybrid object-oriented language, with a few native types, in addition ! to class types. It is class-based, where a class may have static as ! well as per-object fields, and static as well as instance methods. Non-static methods may be virtual, and may be overloaded. Overloading is resolved at compile time by matching the actual argument types against the parameter types. Virtual methods are implemented using *************** method. Classes are organized in a pack *** 2292,2304 **** All of the listed attributes are also true of C++, though C++ has extra features (for example in C++ objects may be allocated not just on ! the heap, but also statically or in a local stack frame). Because 'gcj' ! uses the same compiler technology as G++ (the GNU C++ compiler), it is ! possible to make the intersection of the two languages use the same ABI ! (object representation and calling conventions). The key idea in CNI is ! that Java objects are C++ objects, and all Java classes are C++ classes ! (but not the other way around). So the most important task in ! integrating Java and C++ is to remove gratuitous incompatibilities. You write CNI code as a regular C++ source file. (You do have to use a Java/CNI-aware C++ compiler, specifically a recent version of G++.) --- 2316,2328 ---- All of the listed attributes are also true of C++, though C++ has extra features (for example in C++ objects may be allocated not just on ! the heap, but also statically or in a local stack frame). Because ! `gcj' uses the same compiler technology as G++ (the GNU C++ compiler), ! it is possible to make the intersection of the two languages use the ! same ABI (object representation and calling conventions). The key idea ! in CNI is that Java objects are C++ objects, and all Java classes are ! C++ classes (but not the other way around). So the most important task ! in integrating Java and C++ is to remove gratuitous incompatibilities. You write CNI code as a regular C++ source file. (You do have to use a Java/CNI-aware C++ compiler, specifically a recent version of G++.) *************** and then must include one header file fo *** 2313,2326 **** #include #include ! These header files are automatically generated by 'gcjh'. CNI provides some functions and macros to make using Java objects and primitive types from C++ easier. In general, these CNI functions and ! macros start with the 'Jv' prefix, for example the function ! 'JvNewObjectArray'. This convention is used to avoid conflicts with other libraries. Internal functions in CNI start with the prefix ! '_Jv_'. You should not call these; if you find a need to, let us know and we will try to come up with an alternate solution. 11.1.1 Limitations --- 2337,2350 ---- #include #include ! These header files are automatically generated by `gcjh'. CNI provides some functions and macros to make using Java objects and primitive types from C++ easier. In general, these CNI functions and ! macros start with the `Jv' prefix, for example the function ! `JvNewObjectArray'. This convention is used to avoid conflicts with other libraries. Internal functions in CNI start with the prefix ! `_Jv_'. You should not call these; if you find a need to, let us know and we will try to come up with an alternate solution. 11.1.1 Limitations *************** freed from the shackles of Java, a CNI C *** 2331,2337 **** rules of the Java programming language. For example: it is not possible to declare a method in a CNI class ! that will take a C string ('char*') as an argument, or to declare a member variable of some non-Java datatype.  --- 2355,2361 ---- rules of the Java programming language. For example: it is not possible to declare a method in a CNI class ! that will take a C string (`char*') as an argument, or to declare a member variable of some non-Java datatype.  *************** sub-packages. Every class belongs to ei *** 2346,2354 **** package that has a hierarchical and globally unique name. A Java package is mapped to a C++ "namespace". The Java class ! 'java.lang.String' is in the package 'java.lang', which is a sub-package ! of 'java'. The C++ equivalent is the class 'java::lang::String', which ! is in the namespace 'java::lang' which is in the namespace 'java'. Here is how you could express this: --- 2370,2379 ---- package that has a hierarchical and globally unique name. A Java package is mapped to a C++ "namespace". The Java class ! `java.lang.String' is in the package `java.lang', which is a ! sub-package of `java'. The C++ equivalent is the class ! `java::lang::String', which is in the namespace `java::lang' which is ! in the namespace `java'. Here is how you could express this: *************** Here is how you could express this: *** 2366,2372 **** ... }; ! The 'gcjh' tool automatically generates the necessary namespace declarations. 11.2.1 Leaving out package names --- 2391,2397 ---- ... }; ! The `gcjh' tool automatically generates the necessary namespace declarations. 11.2.1 Leaving out package names *************** declarations. *** 2375,2394 **** Always using the fully-qualified name of a java class can be tiresomely verbose. Using the full qualified name also ties the code to a single package making code changes necessary should the class move from one ! package to another. The Java 'package' declaration specifies that the ! following class declarations are in the named package, without having to ! explicitly name the full package qualifiers. The 'package' declaration ! can be followed by zero or more 'import' declarations, which allows ! either a single class or all the classes in a package to be named by a ! simple identifier. C++ provides something similar with the 'using' ! declaration and directive. In Java: import PACKAGE-NAME.CLASS-NAME; allows the program text to refer to CLASS-NAME as a shorthand for the ! fully qualified name: 'PACKAGE-NAME.CLASS-NAME'. To achieve the same effect C++, you have to do this: --- 2400,2419 ---- Always using the fully-qualified name of a java class can be tiresomely verbose. Using the full qualified name also ties the code to a single package making code changes necessary should the class move from one ! package to another. The Java `package' declaration specifies that the ! following class declarations are in the named package, without having ! to explicitly name the full package qualifiers. The `package' ! declaration can be followed by zero or more `import' declarations, which ! allows either a single class or all the classes in a package to be ! named by a simple identifier. C++ provides something similar with the ! `using' declaration and directive. In Java: import PACKAGE-NAME.CLASS-NAME; allows the program text to refer to CLASS-NAME as a shorthand for the ! fully qualified name: `PACKAGE-NAME.CLASS-NAME'. To achieve the same effect C++, you have to do this: *************** Java can also cause imports on demand, l *** 2398,2405 **** import PACKAGE-NAME.*; ! Doing this allows any class from the package PACKAGE-NAME to be referred ! to only by its class-name within the program text. The same effect can be achieved in C++ like this: --- 2423,2430 ---- import PACKAGE-NAME.*; ! Doing this allows any class from the package PACKAGE-NAME to be ! referred to only by its class-name within the program text. The same effect can be achieved in C++ like this: *************** example) so CNI provides a special C++ t *** 2419,2451 **** type: *Java type* *C/C++ typename* *Description* ! 'char' 'jchar' 16 bit Unicode character ! 'boolean' 'jboolean' logical (true or false) values ! 'byte' 'jbyte' 8-bit signed integer ! 'short' 'jshort' 16 bit signed integer ! 'int' 'jint' 32 bit signed integer ! 'long' 'jlong' 64 bit signed integer ! 'float' 'jfloat' 32 bit IEEE floating point number ! 'double' 'jdouble' 64 bit IEEE floating point number ! 'void' 'void' no value When referring to a Java type You should always use these C++ ! typenames (e.g.: 'jint') to avoid disappointment. 11.3.1 Reference types associated with primitive types ------------------------------------------------------ In Java each primitive type has an associated reference type, e.g.: ! 'boolean' has an associated 'java.lang.Boolean.TYPE' class. In order to ! make working with such classes easier GCJ provides the macro ! 'JvPrimClass': -- macro: JvPrimClass type ! Return a pointer to the 'Class' object corresponding to the type supplied. JvPrimClass(void) => java.lang.Void.TYPE  File: gcj.info, Node: Reference types, Next: Interfaces, Prev: Primitive types, Up: About CNI --- 2444,2477 ---- type: *Java type* *C/C++ typename* *Description* ! `char' `jchar' 16 bit Unicode character ! `boolean' `jboolean' logical (true or false) values ! `byte' `jbyte' 8-bit signed integer ! `short' `jshort' 16 bit signed integer ! `int' `jint' 32 bit signed integer ! `long' `jlong' 64 bit signed integer ! `float' `jfloat' 32 bit IEEE floating point number ! `double' `jdouble' 64 bit IEEE floating point number ! `void' `void' no value When referring to a Java type You should always use these C++ ! typenames (e.g.: `jint') to avoid disappointment. 11.3.1 Reference types associated with primitive types ------------------------------------------------------ In Java each primitive type has an associated reference type, e.g.: ! `boolean' has an associated `java.lang.Boolean.TYPE' class. In order ! to make working with such classes easier GCJ provides the macro ! `JvPrimClass': -- macro: JvPrimClass type ! Return a pointer to the `Class' object corresponding to the type supplied. JvPrimClass(void) => java.lang.Void.TYPE +  File: gcj.info, Node: Reference types, Next: Interfaces, Prev: Primitive types, Up: About CNI *************** File: gcj.info, Node: Reference types, *** 2454,2475 **** A Java reference type is treated as a class in C++. Classes and interfaces are handled this way. A Java reference is translated to a ! C++ pointer, so for instance a Java 'java.lang.String' becomes, in C++, ! 'java::lang::String *'. CNI provides a few built-in typedefs for the most common classes: *Java type* *C++ typename* *Description* ! 'java.lang.Object' 'jobject' Object type ! 'java.lang.String' 'jstring' String type ! 'java.lang.Class' 'jclass' Class type ! ! Every Java class or interface has a corresponding 'Class' instance. ! These can be accessed in CNI via the static 'class$' field of a class. ! The 'class$' field is of type 'Class' (and not 'Class *'), so you will ! typically take the address of it. ! Here is how you can refer to the class of 'String', which in Java ! would be written 'String.class': using namespace java::lang; doSomething (&String::class$); --- 2480,2501 ---- A Java reference type is treated as a class in C++. Classes and interfaces are handled this way. A Java reference is translated to a ! C++ pointer, so for instance a Java `java.lang.String' becomes, in C++, ! `java::lang::String *'. CNI provides a few built-in typedefs for the most common classes: *Java type* *C++ typename* *Description* ! `java.lang.Object' `jobject' Object type ! `java.lang.String' `jstring' String type ! `java.lang.Class' `jclass' Class type ! ! Every Java class or interface has a corresponding `Class' instance. ! These can be accessed in CNI via the static `class$' field of a class. ! The `class$' field is of type `Class' (and not `Class *'), so you will ! typically take the address of it. ! Here is how you can refer to the class of `String', which in Java ! would be written `String.class': using namespace java::lang; doSomething (&String::class$); *************** File: gcj.info, Node: Interfaces, Next *** 2483,2495 **** A Java class can "implement" zero or more "interfaces", in addition to inheriting from a single base class. ! CNI allows CNI code to implement methods of interfaces. You can also ! call methods through interface references, with some limitations. ! CNI doesn't understand interface inheritance at all yet. So, you can ! only call an interface method when the declared type of the field being ! called matches the interface which declares that method. The workaround ! is to cast the interface reference to the right superinterface. For example if you have: --- 2509,2522 ---- A Java class can "implement" zero or more "interfaces", in addition to inheriting from a single base class. ! CNI allows CNI code to implement methods of interfaces. You can ! also call methods through interface references, with some limitations. ! CNI doesn't understand interface inheritance at all yet. So, you ! can only call an interface method when the declared type of the field ! being called matches the interface which declares that method. The ! workaround is to cast the interface reference to the right ! superinterface. For example if you have: *************** is to cast the interface reference to th *** 2503,2510 **** void b(); } ! and declare a variable of type 'B' in C++, you can't call 'a()' ! unless you cast it to an 'A' first.  File: gcj.info, Node: Objects and Classes, Next: Class Initialization, Prev: Interfaces, Up: About CNI --- 2530,2537 ---- void b(); } ! and declare a variable of type `B' in C++, you can't call `a()' ! unless you cast it to an `A' first.  File: gcj.info, Node: Objects and Classes, Next: Class Initialization, Prev: Interfaces, Up: About CNI *************** File: gcj.info, Node: Objects and Class *** 2515,2527 **** 11.6.1 Classes -------------- ! All Java classes are derived from 'java.lang.Object'. C++ does not have ! a unique root class, but we use the C++ class 'java::lang::Object' as ! the C++ version of the 'java.lang.Object' Java class. All other Java ! classes are mapped into corresponding C++ classes derived from ! 'java::lang::Object'. ! Interface inheritance (the 'implements' keyword) is currently not reflected in the C++ mapping. 11.6.2 Object fields --- 2542,2554 ---- 11.6.1 Classes -------------- ! All Java classes are derived from `java.lang.Object'. C++ does not ! have a unique root class, but we use the C++ class `java::lang::Object' ! as the C++ version of the `java.lang.Object' Java class. All other ! Java classes are mapped into corresponding C++ classes derived from ! `java::lang::Object'. ! Interface inheritance (the `implements' keyword) is currently not reflected in the C++ mapping. 11.6.2 Object fields *************** reflected in the C++ mapping. *** 2529,2546 **** Each object contains an object header, followed by the instance fields of the class, in order. The object header consists of a single pointer ! to a dispatch or virtual function table. (There may be extra fields _in ! front of_ the object, for example for memory management, but this is ! invisible to the application, and the reference to the object points to ! the dispatch table pointer.) The fields are laid out in the same order, alignment, and size as in ! C++. Specifically, 8-bit and 16-bit native types ('byte', 'short', ! 'char', and 'boolean') are _not_ widened to 32 bits. Note that the Java ! VM does extend 8-bit and 16-bit types to 32 bits when on the VM stack or ! temporary registers. ! If you include the 'gcjh'-generated header for a class, you can access fields of Java classes in the _natural_ way. For example, given the following Java class: --- 2556,2573 ---- Each object contains an object header, followed by the instance fields of the class, in order. The object header consists of a single pointer ! to a dispatch or virtual function table. (There may be extra fields ! _in front of_ the object, for example for memory management, but this ! is invisible to the application, and the reference to the object points ! to the dispatch table pointer.) The fields are laid out in the same order, alignment, and size as in ! C++. Specifically, 8-bit and 16-bit native types (`byte', `short', ! `char', and `boolean') are _not_ widened to 32 bits. Note that the ! Java VM does extend 8-bit and 16-bit types to 32 bits when on the VM ! stack or temporary registers. ! If you include the `gcjh'-generated header for a class, you can access fields of Java classes in the _natural_ way. For example, given the following Java class: *************** the following Java class: *** 2568,2576 **** ------------------------ CNI does not strictly enforce the Java access specifiers, because Java ! permissions cannot be directly mapped into C++ permission. Private Java ! fields and methods are mapped to private C++ fields and methods, but ! other fields and methods are mapped to public fields and methods.  File: gcj.info, Node: Class Initialization, Next: Object allocation, Prev: Objects and Classes, Up: About CNI --- 2595,2603 ---- ------------------------ CNI does not strictly enforce the Java access specifiers, because Java ! permissions cannot be directly mapped into C++ permission. Private ! Java fields and methods are mapped to private C++ fields and methods, ! but other fields and methods are mapped to public fields and methods.  File: gcj.info, Node: Class Initialization, Next: Object allocation, Prev: Objects and Classes, Up: About CNI *************** File: gcj.info, Node: Class Initializat *** 2579,2619 **** ========================= Java requires that each class be automatically initialized at the time ! of the first active use. Initializing a class involves initializing the ! static fields, running code in class initializer methods, and initializing base classes. There may also be some implementation ! specific actions, such as allocating 'String' objects corresponding to string literals in the code. ! The GCJ compiler inserts calls to 'JvInitClass' at appropriate places ! to ensure that a class is initialized when required. The C++ compiler ! does not insert these calls automatically--it is the programmer's ! responsibility to make sure classes are initialized. However, this is ! fairly painless because of the conventions assumed by the Java system. ! First, 'libgcj' will make sure a class is initialized before an ! instance of that object is created. This is one of the responsibilities ! of the 'new' operation. This is taken care of both in Java code, and in ! C++ code. When G++ sees a 'new' of a Java class, it will call a routine ! in 'libgcj' to allocate the object, and that routine will take care of ! initializing the class. Note however that this does not happen for Java ! arrays; you must allocate those using the appropriate CNI function. It ! follows that you can access an instance field, or call an instance ! (non-static) method and be safe in the knowledge that the class and all ! of its base classes have been initialized. Invoking a static method is also safe. This is because the Java compiler adds code to the start of a static method to make sure the ! class is initialized. However, the C++ compiler does not add this extra ! code. Hence, if you write a native static method using CNI, you are ! responsible for calling 'JvInitClass' before doing anything else in the ! method (unless you are sure it is safe to leave it out). Accessing a static field also requires the class of the field to be ! initialized. The Java compiler will generate code to call 'JvInitClass' ! before getting or setting the field. However, the C++ compiler will not ! generate this extra code, so it is your responsibility to make sure the ! class is initialized before you access a static field from C++.  File: gcj.info, Node: Object allocation, Next: Memory allocation, Prev: Class Initialization, Up: About CNI --- 2606,2649 ---- ========================= Java requires that each class be automatically initialized at the time ! of the first active use. Initializing a class involves initializing ! the static fields, running code in class initializer methods, and initializing base classes. There may also be some implementation ! specific actions, such as allocating `String' objects corresponding to string literals in the code. ! The GCJ compiler inserts calls to `JvInitClass' at appropriate ! places to ensure that a class is initialized when required. The C++ ! compiler does not insert these calls automatically--it is the ! programmer's responsibility to make sure classes are initialized. ! However, this is fairly painless because of the conventions assumed by ! the Java system. ! First, `libgcj' will make sure a class is initialized before an ! instance of that object is created. This is one of the ! responsibilities of the `new' operation. This is taken care of both in ! Java code, and in C++ code. When G++ sees a `new' of a Java class, it ! will call a routine in `libgcj' to allocate the object, and that ! routine will take care of initializing the class. Note however that ! this does not happen for Java arrays; you must allocate those using the ! appropriate CNI function. It follows that you can access an instance ! field, or call an instance (non-static) method and be safe in the ! knowledge that the class and all of its base classes have been ! initialized. Invoking a static method is also safe. This is because the Java compiler adds code to the start of a static method to make sure the ! class is initialized. However, the C++ compiler does not add this ! extra code. Hence, if you write a native static method using CNI, you ! are responsible for calling `JvInitClass' before doing anything else in ! the method (unless you are sure it is safe to leave it out). Accessing a static field also requires the class of the field to be ! initialized. The Java compiler will generate code to call ! `JvInitClass' before getting or setting the field. However, the C++ ! compiler will not generate this extra code, so it is your ! responsibility to make sure the class is initialized before you access ! a static field from C++.  File: gcj.info, Node: Object allocation, Next: Memory allocation, Prev: Class Initialization, Up: About CNI *************** expression", e.g.: *** 2630,2638 **** objects have to be explicitly deleted; in Java they are automatically deleted by the garbage collector. Using CNI, you can allocate a new Java object using standard C++ syntax and the C++ compiler will allocate ! memory from the garbage collector. If you have overloaded constructors, ! the compiler will choose the correct one using standard C++ overload ! resolution rules. For example: --- 2660,2668 ---- objects have to be explicitly deleted; in Java they are automatically deleted by the garbage collector. Using CNI, you can allocate a new Java object using standard C++ syntax and the C++ compiler will allocate ! memory from the garbage collector. If you have overloaded ! constructors, the compiler will choose the correct one using standard ! C++ overload resolution rules. For example: *************** File: gcj.info, Node: Memory allocation *** 2644,2660 **** 11.9 Memory allocation ====================== ! When allocating memory in CNI methods it is best to handle out-of-memory ! conditions by throwing a Java exception. These functions are provided ! for that purpose: -- Function: void* JvMalloc (jsize SIZE) ! Calls malloc. Throws 'java.lang.OutOfMemoryError' if allocation fails. -- Function: void* JvRealloc (void* PTR, jsize SIZE) ! Calls realloc. Throws 'java.lang.OutOfMemoryError' if reallocation ! fails. -- Function: void JvFree (void* PTR) Calls free. --- 2674,2690 ---- 11.9 Memory allocation ====================== ! When allocating memory in CNI methods it is best to handle ! out-of-memory conditions by throwing a Java exception. These functions ! are provided for that purpose: -- Function: void* JvMalloc (jsize SIZE) ! Calls malloc. Throws `java.lang.OutOfMemoryError' if allocation fails. -- Function: void* JvRealloc (void* PTR, jsize SIZE) ! Calls realloc. Throws `java.lang.OutOfMemoryError' if ! reallocation fails. -- Function: void JvFree (void* PTR) Calls free. *************** While in many ways Java is similar to C *** 2669,2678 **** in its treatment of arrays. C arrays are based on the idea of pointer arithmetic, which would be incompatible with Java's security requirements. Java arrays are true objects (array types inherit from ! 'java.lang.Object'). An array-valued variable is one that contains a reference (pointer) to an array object. ! Referencing a Java array in C++ code is done using the 'JArray' template, which as defined as follows: class __JArray : public java::lang::Object --- 2699,2708 ---- in its treatment of arrays. C arrays are based on the idea of pointer arithmetic, which would be incompatible with Java's security requirements. Java arrays are true objects (array types inherit from ! `java.lang.Object'). An array-valued variable is one that contains a reference (pointer) to an array object. ! Referencing a Java array in C++ code is done using the `JArray' template, which as defined as follows: class __JArray : public java::lang::Object *************** template, which as defined as follows: *** 2689,2695 **** T& operator[](jint i) { return data[i]; } }; ! There are a number of 'typedef's which correspond to 'typedef's from the JNI. Each is the type of an array holding objects of the relevant type: --- 2719,2725 ---- T& operator[](jint i) { return data[i]; } }; ! There are a number of `typedef's which correspond to `typedef's from the JNI. Each is the type of an array holding objects of the relevant type: *************** type: *** 2705,2723 **** typedef JArray *jdoubleArray; -- Method on template: T* elements (JArray ARRAY) ! This template function can be used to get a pointer to the elements ! of the 'array'. For instance, you can fetch a pointer to the ! integers that make up an 'int[]' like so: extern jintArray foo; jint *intp = elements (foo); The name of this function may change in the future. ! -- Function: jobjectArray JvNewObjectArray (jsize LENGTH, jclass KLASS, ! jobject INIT) This creates a new array whose elements have reference type. ! 'klass' is the type of elements of the array and 'init' is the initial value put into every slot in the array. using namespace java::lang; --- 2735,2753 ---- typedef JArray *jdoubleArray; -- Method on template: T* elements (JArray ARRAY) ! This template function can be used to get a pointer to the ! elements of the `array'. For instance, you can fetch a pointer to ! the integers that make up an `int[]' like so: extern jintArray foo; jint *intp = elements (foo); The name of this function may change in the future. ! -- Function: jobjectArray JvNewObjectArray (jsize LENGTH, jclass ! KLASS, jobject INIT) This creates a new array whose elements have reference type. ! `klass' is the type of elements of the array and `init' is the initial value put into every slot in the array. using namespace java::lang; *************** File: gcj.info, Node: Methods, Next: S *** 2754,2762 **** ============= Java methods are mapped directly into C++ methods. The header files ! generated by 'gcjh' include the appropriate method definitions. ! Basically, the generated methods have the same names and _corresponding_ ! types as the Java methods, and are called in the natural manner. 11.11.1 Overloading ------------------- --- 2784,2793 ---- ============= Java methods are mapped directly into C++ methods. The header files ! generated by `gcjh' include the appropriate method definitions. ! Basically, the generated methods have the same names and ! _corresponding_ types as the Java methods, and are called in the ! natural manner. 11.11.1 Overloading ------------------- *************** Both Java and C++ provide method overloa *** 2765,2776 **** a class have the same name, and the correct one is chosen (at compile time) depending on the argument types. The rules for choosing the correct method are (as expected) more complicated in C++ than in Java, ! but given a set of overloaded methods generated by 'gcjh' the C++ compiler will choose the expected one. Common assemblers and linkers are not aware of C++ overloading, so ! the standard implementation strategy is to encode the parameter types of ! a method into its assembly-level name. This encoding is called "mangling", and the encoded name is the "mangled name". The same mechanism is used to implement Java overloading. For C++/Java interoperability, it is important that both the Java and C++ compilers --- 2796,2807 ---- a class have the same name, and the correct one is chosen (at compile time) depending on the argument types. The rules for choosing the correct method are (as expected) more complicated in C++ than in Java, ! but given a set of overloaded methods generated by `gcjh' the C++ compiler will choose the expected one. Common assemblers and linkers are not aware of C++ overloading, so ! the standard implementation strategy is to encode the parameter types ! of a method into its assembly-level name. This encoding is called "mangling", and the encoded name is the "mangled name". The same mechanism is used to implement Java overloading. For C++/Java interoperability, it is important that both the Java and C++ compilers *************** use the _same_ encoding scheme. *** 2780,2786 **** ---------------------- Static Java methods are invoked in CNI using the standard C++ syntax, ! using the '::' operator rather than the '.' operator. For example: --- 2811,2817 ---- ---------------------- Static Java methods are invoked in CNI using the standard C++ syntax, ! using the `::' operator rather than the `.' operator. For example: *************** For example: *** 2800,2814 **** --------------------------- Constructors are called implicitly as part of object allocation using ! the 'new' operator. For example: java::lang::Integer *x = new java::lang::Integer(234); Java does not allow a constructor to be a native method. This ! limitation can be coded round however because a constructor can _call_ a ! native method. 11.11.4 Instance methods ------------------------ --- 2831,2845 ---- --------------------------- Constructors are called implicitly as part of object allocation using ! the `new' operator. For example: java::lang::Integer *x = new java::lang::Integer(234); Java does not allow a constructor to be a native method. This ! limitation can be coded round however because a constructor can _call_ ! a native method. 11.11.4 Instance methods ------------------------ *************** File: gcj.info, Node: Strings, Next: M *** 2846,2880 **** ============= CNI provides a number of utility functions for working with Java Java ! 'String' objects. The names and interfaces are analogous to those of JNI. -- Function: jstring JvNewString (const jchar* CHARS, jsize LEN) ! Returns a Java 'String' object with characters from the array of Unicode characters CHARS up to the index LEN in that array. -- Function: jstring JvNewStringLatin1 (const char* BYTES, jsize LEN) ! Returns a Java 'String' made up of LEN bytes from BYTES. -- Function: jstring JvNewStringLatin1 (const char* BYTES) ! As above but the length of the 'String' is 'strlen(BYTES)'. -- Function: jstring JvNewStringUTF (const char* BYTES) ! Returns a 'String' which is made up of the UTF encoded characters present in the C string BYTES. -- Function: jchar* JvGetStringChars (jstring STR) ! Returns a pointer to an array of characters making up the 'String' STR. -- Function: int JvGetStringUTFLength (jstring STR) Returns the number of bytes required to encode the contents of the ! 'String' STR in UTF-8. -- Function: jsize JvGetStringUTFRegion (jstring STR, jsize START, jsize LEN, char* BUF) ! Puts the UTF-8 encoding of a region of the 'String' STR into the ! buffer 'buf'. The region to fetch is marked by START and LEN. Note that BUF is a buffer, not a C string. It is _not_ null terminated. --- 2877,2911 ---- ============= CNI provides a number of utility functions for working with Java Java ! `String' objects. The names and interfaces are analogous to those of JNI. -- Function: jstring JvNewString (const jchar* CHARS, jsize LEN) ! Returns a Java `String' object with characters from the array of Unicode characters CHARS up to the index LEN in that array. -- Function: jstring JvNewStringLatin1 (const char* BYTES, jsize LEN) ! Returns a Java `String' made up of LEN bytes from BYTES. -- Function: jstring JvNewStringLatin1 (const char* BYTES) ! As above but the length of the `String' is `strlen(BYTES)'. -- Function: jstring JvNewStringUTF (const char* BYTES) ! Returns a `String' which is made up of the UTF encoded characters present in the C string BYTES. -- Function: jchar* JvGetStringChars (jstring STR) ! Returns a pointer to an array of characters making up the `String' STR. -- Function: int JvGetStringUTFLength (jstring STR) Returns the number of bytes required to encode the contents of the ! `String' STR in UTF-8. -- Function: jsize JvGetStringUTFRegion (jstring STR, jsize START, jsize LEN, char* BUF) ! Puts the UTF-8 encoding of a region of the `String' STR into the ! buffer `buf'. The region to fetch is marked by START and LEN. Note that BUF is a buffer, not a C string. It is _not_ null terminated. *************** None of the following is possible with C *** 2907,2913 **** . . . ! } // 'uint' is not a valid Java type, neither is 'char*' Of course, it is ok to use C/C++ types within the scope of a method: --- 2938,2944 ---- . . . ! } // `uint' is not a valid Java type, neither is `char*' Of course, it is ok to use C/C++ types within the scope of a method: *************** Of course, it is ok to use C/C++ types w *** 2924,2931 **** --------------- The above restriction can be problematic, so CNI includes the ! 'gnu.gcj.RawData' class. The 'RawData' class is a "non-scanned ! reference" type. In other words variables declared of type 'RawData' can contain any data and are not checked by the compiler or memory manager in any way. --- 2955,2962 ---- --------------- The above restriction can be problematic, so CNI includes the ! `gnu.gcj.RawData' class. The `RawData' class is a "non-scanned ! reference" type. In other words variables declared of type `RawData' can contain any data and are not checked by the compiler or memory manager in any way. *************** Here are some examples: *** 2965,2977 **** 11.13.2 RawDataManaged ---------------------- ! 'gnu.gcj.RawDataManaged' is another type used to indicate special data ! used by native code. Unlike the 'RawData' type, fields declared as ! 'RawDataManaged' will be "marked" by the memory manager and considered for garbage collection. ! Native data which is allocated using CNI's 'JvAllocBytes()' function ! and stored in a 'RawDataManaged' will be automatically freed when the Java object it is associated with becomes unreachable. 11.13.3 Native memory allocation --- 2996,3008 ---- 11.13.2 RawDataManaged ---------------------- ! `gnu.gcj.RawDataManaged' is another type used to indicate special data ! used by native code. Unlike the `RawData' type, fields declared as ! `RawDataManaged' will be "marked" by the memory manager and considered for garbage collection. ! Native data which is allocated using CNI's `JvAllocBytes()' function ! and stored in a `RawDataManaged' will be automatically freed when the Java object it is associated with becomes unreachable. 11.13.3 Native memory allocation *************** Java object it is associated with become *** 2983,3004 **** but will be freed if no references to it are discovered. This function can be useful if you need to associate some native ! data with a Java object. Using a CNI's special 'RawDataManaged' ! type, native data allocated with 'JvAllocBytes' will be automatically freed when the Java object itself becomes unreachable. 11.13.4 Posix signals --------------------- ! On Posix based systems the 'libgcj' library uses several signals internally. CNI code should not attempt to use the same signals as ! doing so may cause 'libgcj' and/or the CNI code to fail. ! SIGSEGV is used on many systems to generate 'NullPointerExceptions'. ! SIGCHLD is used internally by 'Runtime.exec()'. Several other signals (that vary from platform to platform) can be used by the memory manager ! and by 'Thread.interrupt()'.  File: gcj.info, Node: Exception Handling, Next: Synchronization, Prev: Mixing with C++, Up: About CNI --- 3014,3035 ---- but will be freed if no references to it are discovered. This function can be useful if you need to associate some native ! data with a Java object. Using a CNI's special `RawDataManaged' ! type, native data allocated with `JvAllocBytes' will be automatically freed when the Java object itself becomes unreachable. 11.13.4 Posix signals --------------------- ! On Posix based systems the `libgcj' library uses several signals internally. CNI code should not attempt to use the same signals as ! doing so may cause `libgcj' and/or the CNI code to fail. ! SIGSEGV is used on many systems to generate `NullPointerExceptions'. ! SIGCHLD is used internally by `Runtime.exec()'. Several other signals (that vary from platform to platform) can be used by the memory manager ! and by `Thread.interrupt()'.  File: gcj.info, Node: Exception Handling, Next: Synchronization, Prev: Mixing with C++, Up: About CNI *************** are not yet perfectly integrated. The m *** 3011,3029 **** type information facilities of the two languages are not integrated. Still, things work fairly well. You can throw a Java exception from ! C++ using the ordinary 'throw' construct, and this exception can be caught by Java code. Similarly, you can catch an exception thrown from ! Java using the C++ 'catch' construct. Here is an example: if (i >= count) throw new java::lang::IndexOutOfBoundsException(); ! Normally, G++ will automatically detect when you are writing C++ code ! that uses Java exceptions, and handle them appropriately. However, if ! C++ code only needs to execute destructors when Java exceptions are ! thrown through it, GCC will guess incorrectly. Sample problematic code: struct S { ~S(); }; --- 3042,3061 ---- type information facilities of the two languages are not integrated. Still, things work fairly well. You can throw a Java exception from ! C++ using the ordinary `throw' construct, and this exception can be caught by Java code. Similarly, you can catch an exception thrown from ! Java using the C++ `catch' construct. Here is an example: if (i >= count) throw new java::lang::IndexOutOfBoundsException(); ! Normally, G++ will automatically detect when you are writing C++ ! code that uses Java exceptions, and handle them appropriately. ! However, if C++ code only needs to execute destructors when Java ! exceptions are thrown through it, GCC will guess incorrectly. Sample ! problematic code: struct S { ~S(); }; *************** thrown through it, GCC will guess incorr *** 3035,3046 **** bar(); } ! The usual effect of an incorrect guess is a link failure, complaining ! of a missing routine called '__gxx_personality_v0'. You can inform the compiler that Java exceptions are to be used in a translation unit, irrespective of what it might think, by writing ! '#pragma GCC java_exceptions' at the head of the file. This '#pragma' must appear before any functions that throw or catch exceptions, or run destructors when exceptions are thrown through them. --- 3067,3078 ---- bar(); } ! The usual effect of an incorrect guess is a link failure, ! complaining of a missing routine called `__gxx_personality_v0'. You can inform the compiler that Java exceptions are to be used in a translation unit, irrespective of what it might think, by writing ! `#pragma GCC java_exceptions' at the head of the file. This `#pragma' must appear before any functions that throw or catch exceptions, or run destructors when exceptions are thrown through them. *************** File: gcj.info, Node: Synchronization, *** 3051,3068 **** ===================== Each Java object has an implicit monitor. The Java VM uses the ! instruction 'monitorenter' to acquire and lock a monitor, and ! 'monitorexit' to release it. ! The corresponding CNI macros are 'JvMonitorEnter' and 'JvMonitorExit' ! (JNI has similar methods 'MonitorEnter' and 'MonitorExit'). The Java source language does not provide direct access to these ! primitives. Instead, there is a 'synchronized' statement that does an ! implicit 'monitorenter' before entry to the block, and does a ! 'monitorexit' on exit from the block. Note that the lock has to be released even when the block is abnormally terminated by an exception, ! which means there is an implicit 'try finally' surrounding synchronization locks. From C++, it makes sense to use a destructor to release a lock. CNI --- 3083,3101 ---- ===================== Each Java object has an implicit monitor. The Java VM uses the ! instruction `monitorenter' to acquire and lock a monitor, and ! `monitorexit' to release it. ! The corresponding CNI macros are `JvMonitorEnter' and ! `JvMonitorExit' (JNI has similar methods `MonitorEnter' and ! `MonitorExit'). The Java source language does not provide direct access to these ! primitives. Instead, there is a `synchronized' statement that does an ! implicit `monitorenter' before entry to the block, and does a ! `monitorexit' on exit from the block. Note that the lock has to be released even when the block is abnormally terminated by an exception, ! which means there is an implicit `try finally' surrounding synchronization locks. From C++, it makes sense to use a destructor to release a lock. CNI *************** might become this C++ code: *** 3088,3103 **** CODE; } ! Java also has methods with the 'synchronized' attribute. This is ! equivalent to wrapping the entire method body in a 'synchronized' statement. (Alternatively, an implementation could require the caller to do the synchronization. This is not practical for a compiler, because each virtual method call would have to test at run-time if ! synchronization is needed.) Since in 'gcj' the 'synchronized' attribute ! is handled by the method implementation, it is up to the programmer of a ! synchronized native method to handle the synchronization (in the C++ ! implementation of the method). In other words, you need to manually add ! 'JvSynchronize' in a 'native synchronized' method.  File: gcj.info, Node: Invocation, Next: Reflection, Prev: Synchronization, Up: About CNI --- 3121,3136 ---- CODE; } ! Java also has methods with the `synchronized' attribute. This is ! equivalent to wrapping the entire method body in a `synchronized' statement. (Alternatively, an implementation could require the caller to do the synchronization. This is not practical for a compiler, because each virtual method call would have to test at run-time if ! synchronization is needed.) Since in `gcj' the `synchronized' ! attribute is handled by the method implementation, it is up to the ! programmer of a synchronized native method to handle the synchronization ! (in the C++ implementation of the method). In other words, you need to ! manually add `JvSynchronize' in a `native synchronized' method.  File: gcj.info, Node: Invocation, Next: Reflection, Prev: Synchronization, Up: About CNI *************** File: gcj.info, Node: Invocation, Next *** 3106,3128 **** ================ CNI permits C++ applications to make calls into Java classes, in ! addition to allowing Java code to call into C++. Several functions, known as the "invocation API", are provided to support this. -- Function: jint JvCreateJavaVM (JvVMInitArgs* VM_ARGS) ! ! Initializes the Java runtime. This function performs essential initialization of the threads interface, garbage collector, ! exception handling and other key aspects of the runtime. It must ! be called once by an application with a non-Java 'main()' function, ! before any other Java or CNI calls are made. It is safe, but not ! recommended, to call 'JvCreateJavaVM()' more than once provided it ! is only called from a single thread. The VMARGS parameter can be ! used to specify initialization parameters for the Java runtime. It ! may be 'NULL'. JvVMInitArgs represents a list of virtual machine initialization ! arguments. 'JvCreateJavaVM()' ignores the version field. typedef struct JvVMOption { --- 3139,3160 ---- ================ CNI permits C++ applications to make calls into Java classes, in ! addition to allowing Java code to call into C++. Several functions, known as the "invocation API", are provided to support this. -- Function: jint JvCreateJavaVM (JvVMInitArgs* VM_ARGS) ! Initializes the Java runtime. This function performs essential initialization of the threads interface, garbage collector, ! exception handling and other key aspects of the runtime. It must ! be called once by an application with a non-Java `main()' ! function, before any other Java or CNI calls are made. It is ! safe, but not recommended, to call `JvCreateJavaVM()' more than ! once provided it is only called from a single thread. The VMARGS ! parameter can be used to specify initialization parameters for the ! Java runtime. It may be `NULL'. JvVMInitArgs represents a list of virtual machine initialization ! arguments. `JvCreateJavaVM()' ignores the version field. typedef struct JvVMOption { *************** known as the "invocation API", are provi *** 3147,3186 **** jboolean ignoreUnrecognized; } JvVMInitArgs; ! 'JvCreateJavaVM()' returns '0' upon success, or '-1' if the runtime ! is already initialized. ! _Note:_ In GCJ 3.1, the 'vm_args' parameter is ignored. It is recognized and used as of release 4.0. -- Function: java::lang::Thread* JvAttachCurrentThread (jstring NAME, java::lang::ThreadGroup* GROUP) Registers an existing thread with the Java runtime. This must be called once from each thread, before that thread makes any other ! Java or CNI calls. It must be called after 'JvCreateJavaVM'. NAME ! specifies a name for the thread. It may be 'NULL', in which case a name will be generated. GROUP is the ThreadGroup in which this ! thread will be a member. If it is 'NULL', the thread will be a member of the main thread group. The return value is the Java ! 'Thread' object that represents the thread. It is safe to call ! 'JvAttachCurrentThread()' more than once from the same thread. If the thread is already attached, the call is ignored and the current thread object is returned. -- Function: jint JvDetachCurrentThread () ! Unregisters a thread from the Java runtime. This should be called ! by threads that were attached using 'JvAttachCurrentThread()', ! after they have finished making calls to Java code. This ensures that any resources associated with the thread become eligible for ! garbage collection. This function returns '0' upon success, or ! '-1' if the current thread is not attached. 11.16.1 Handling uncaught exceptions ------------------------------------ If an exception is thrown from Java code called using the invocation API, and no handler for the exception can be found, the runtime will ! abort the application. In order to make the application more robust, it is recommended that code which uses the invocation API be wrapped by a top-level try/catch block that catches all Java exceptions. --- 3179,3218 ---- jboolean ignoreUnrecognized; } JvVMInitArgs; ! `JvCreateJavaVM()' returns `0' upon success, or `-1' if the ! runtime is already initialized. ! _Note:_ In GCJ 3.1, the `vm_args' parameter is ignored. It is recognized and used as of release 4.0. -- Function: java::lang::Thread* JvAttachCurrentThread (jstring NAME, java::lang::ThreadGroup* GROUP) Registers an existing thread with the Java runtime. This must be called once from each thread, before that thread makes any other ! Java or CNI calls. It must be called after `JvCreateJavaVM'. NAME ! specifies a name for the thread. It may be `NULL', in which case a name will be generated. GROUP is the ThreadGroup in which this ! thread will be a member. If it is `NULL', the thread will be a member of the main thread group. The return value is the Java ! `Thread' object that represents the thread. It is safe to call ! `JvAttachCurrentThread()' more than once from the same thread. If the thread is already attached, the call is ignored and the current thread object is returned. -- Function: jint JvDetachCurrentThread () ! Unregisters a thread from the Java runtime. This should be called ! by threads that were attached using `JvAttachCurrentThread()', ! after they have finished making calls to Java code. This ensures that any resources associated with the thread become eligible for ! garbage collection. This function returns `0' upon success, or ! `-1' if the current thread is not attached. 11.16.1 Handling uncaught exceptions ------------------------------------ If an exception is thrown from Java code called using the invocation API, and no handler for the exception can be found, the runtime will ! abort the application. In order to make the application more robust, it is recommended that code which uses the invocation API be wrapped by a top-level try/catch block that catches all Java exceptions. *************** top-level try/catch block that catches a *** 3189,3201 **** The following code demonstrates the use of the invocation API. In this example, the C++ application initializes the Java runtime and attaches ! itself. The 'java.lang.System' class is initialized in order to access ! its 'out' field, and a Java string is printed. Finally, the thread is detached from the runtime once it has finished making Java calls. Everything is wrapped with a try/catch block to provide a default handler for any uncaught exceptions. ! The example can be compiled with 'c++ -c test.cc; gcj test.o'. // test.cc #include --- 3221,3233 ---- The following code demonstrates the use of the invocation API. In this example, the C++ application initializes the Java runtime and attaches ! itself. The `java.lang.System' class is initialized in order to access ! its `out' field, and a Java string is printed. Finally, the thread is detached from the runtime once it has finished making Java calls. Everything is wrapped with a try/catch block to provide a default handler for any uncaught exceptions. ! The example can be compiled with `c++ -c test.cc; gcj test.o'. // test.cc #include *************** File: gcj.info, Node: Reflection, Prev *** 3234,3247 **** Reflection is possible with CNI code, it functions similarly to how it functions with JNI. ! The types 'jfieldID' and 'jmethodID' are as in JNI. The functions: ! * 'JvFromReflectedField', ! * 'JvFromReflectedMethod', ! * 'JvToReflectedField' ! * 'JvToFromReflectedMethod' will be added shortly, as will other functions corresponding to JNI. --- 3266,3282 ---- Reflection is possible with CNI code, it functions similarly to how it functions with JNI. ! The types `jfieldID' and `jmethodID' are as in JNI. The functions: ! * `JvFromReflectedField', ! ! * `JvFromReflectedMethod', ! ! * `JvToReflectedField' ! ! * `JvToFromReflectedMethod' will be added shortly, as will other functions corresponding to JNI. *************** File: gcj.info, Node: System properties *** 3251,3270 **** 12 System properties ******************** ! The runtime behavior of the 'libgcj' library can be modified by setting certain system properties. These properties can be compiled into the ! program using the '-DNAME[=VALUE]' option to 'gcj' or by setting them explicitly in the program by calling the ! 'java.lang.System.setProperty()' method. Some system properties are only used for informational purposes (like giving a version number or a user name). A program can inspect the current value of a property by ! calling the 'java.lang.System.getProperty()' method. * Menu: ! * Standard Properties:: Standard properties supported by 'libgcj' * GNU Classpath Properties:: Properties found in Classpath based libraries ! * libgcj Runtime Properties:: Properties specific to 'libgcj'  File: gcj.info, Node: Standard Properties, Next: GNU Classpath Properties, Up: System properties --- 3286,3305 ---- 12 System properties ******************** ! The runtime behavior of the `libgcj' library can be modified by setting certain system properties. These properties can be compiled into the ! program using the `-DNAME[=VALUE]' option to `gcj' or by setting them explicitly in the program by calling the ! `java.lang.System.setProperty()' method. Some system properties are only used for informational purposes (like giving a version number or a user name). A program can inspect the current value of a property by ! calling the `java.lang.System.getProperty()' method. * Menu: ! * Standard Properties:: Standard properties supported by `libgcj' * GNU Classpath Properties:: Properties found in Classpath based libraries ! * libgcj Runtime Properties:: Properties specific to `libgcj'  File: gcj.info, Node: Standard Properties, Next: GNU Classpath Properties, Up: System properties *************** File: gcj.info, Node: Standard Properti *** 3275,3450 **** The following properties are normally found in all implementations of the core libraries for the Java language. ! 'java.version' ! The 'libgcj' version number. ! 'java.vendor' ! Set to 'The Free Software Foundation, Inc.' ! 'java.vendor.url' ! Set to . ! 'java.home' ! The directory where 'gcj' was installed. Taken from the '--prefix' ! option given to 'configure'. ! 'java.class.version' The class format version number supported by the libgcj byte code ! interpreter. (Currently '46.0') ! 'java.vm.specification.version' ! The Virtual Machine Specification version implemented by 'libgcj'. ! (Currently '1.0') ! 'java.vm.specification.vendor' The name of the Virtual Machine specification designer. ! 'java.vm.specification.name' ! The name of the Virtual Machine specification (Set to 'Java Virtual ! Machine Specification'). ! 'java.vm.version' ! The 'gcj' version number. ! 'java.vm.vendor' ! Set to 'The Free Software Foundation, Inc.' ! 'java.vm.name' ! Set to 'GNU libgcj'. ! 'java.specification.version' The Runtime Environment specification version implemented by ! 'libgcj'. (Currently set to '1.3') ! 'java.specification.vendor' The Runtime Environment specification designer. ! 'java.specification.name' ! The name of the Runtime Environment specification (Set to 'Java Platform API Specification'). ! 'java.class.path' The paths (jar files, zip files and directories) used for finding class files. ! 'java.library.path' Directory path used for finding native libraries. ! 'java.io.tmpdir' The directory used to put temporary files in. ! 'java.compiler' Name of the Just In Time compiler to use by the byte code ! interpreter. Currently not used in 'libgcj'. ! 'java.ext.dirs' Directories containing jar files with extra libraries. Will be used when resolving classes. ! 'java.protocol.handler.pkgs' ! A '|' separated list of package names that is used to find classes ! that implement handlers for 'java.net.URL'. ! 'java.rmi.server.codebase' ! A list of URLs that is used by the 'java.rmi.server.RMIClassLoader' to load classes from. ! 'jdbc.drivers' A list of class names that will be loaded by the ! 'java.sql.DriverManager' when it starts up. ! 'file.separator' The separator used in when directories are included in a filename ! (normally '/' or '\' ). ! 'file.encoding' ! The default character encoding used when converting platform native ! files to Unicode (usually set to '8859_1'). ! 'path.separator' The standard separator used when a string contains multiple paths ! (normally ':' or ';'), the string is usually not a valid character to use in normal directory names.) ! 'line.separator' ! The default line separator used on the platform (normally '\n', ! '\r' or a combination of those two characters). ! 'policy.provider' The class name used for the default policy provider returned by ! 'java.security.Policy.getPolicy'. ! 'user.name' The name of the user running the program. Can be the full name, the login name or empty if unknown. ! 'user.home' The default directory to put user specific files in. ! 'user.dir' The current working directory from which the program was started. ! 'user.language' ! The default language as used by the 'java.util.Locale' class. ! 'user.region' ! The default region as used by the 'java.util.Local' class. ! 'user.variant' The default variant of the language and region local used. ! 'user.timezone' ! The default timezone as used by the 'java.util.TimeZone' class. ! 'os.name' The operating system/kernel name that the program runs on. ! 'os.arch' The hardware that we are running on. ! 'os.version' The version number of the operating system/kernel. ! 'awt.appletWarning' The string to display when an untrusted applet is displayed. ! Returned by 'java.awt.Window.getWarningString()' when the window is "insecure". ! 'awt.toolkit' The class name used for initializing the default ! 'java.awt.Toolkit'. Defaults to 'gnu.awt.gtk.GtkToolkit'. ! 'http.proxyHost' Name of proxy host for http connections. ! 'http.proxyPort' Port number to use when a proxy host is in use.  File: gcj.info, Node: GNU Classpath Properties, Next: libgcj Runtime Properties, Prev: Standard Properties, Up: System properties 12.2 GNU Classpath Properties ============================= ! 'libgcj' is based on the GNU Classpath (Essential Libraries for Java) a GNU project to create free core class libraries for use with virtual machines and compilers for the Java language. The following properties are common to libraries based on GNU Classpath. ! 'gcj.dumpobject' Enables printing serialization debugging by the ! 'java.io.ObjectInput' and 'java.io.ObjectOutput' classes when set to something else then the empty string. Only used when running a debug build of the library. ! 'gnu.classpath.vm.shortname' ! This is a succinct name of the virtual machine. For 'libgcj', this ! will always be 'libgcj'. ! 'gnu.classpath.home.url' A base URL used for finding system property files (e.g., ! 'classpath.security'). By default this is a 'file:' URL pointing ! to the 'lib' directory under 'java.home'.  File: gcj.info, Node: libgcj Runtime Properties, Prev: GNU Classpath Properties, Up: System properties --- 3310,3487 ---- The following properties are normally found in all implementations of the core libraries for the Java language. ! `java.version' ! The `libgcj' version number. ! `java.vendor' ! Set to `The Free Software Foundation, Inc.' ! `java.vendor.url' ! Set to `http://gcc.gnu.org/java/'. ! `java.home' ! The directory where `gcj' was installed. Taken from the `--prefix' ! option given to `configure'. ! `java.class.version' The class format version number supported by the libgcj byte code ! interpreter. (Currently `46.0') ! `java.vm.specification.version' ! The Virtual Machine Specification version implemented by `libgcj'. ! (Currently `1.0') ! `java.vm.specification.vendor' The name of the Virtual Machine specification designer. ! `java.vm.specification.name' ! The name of the Virtual Machine specification (Set to `Java ! Virtual Machine Specification'). ! `java.vm.version' ! The `gcj' version number. ! `java.vm.vendor' ! Set to `The Free Software Foundation, Inc.' ! `java.vm.name' ! Set to `GNU libgcj'. ! `java.specification.version' The Runtime Environment specification version implemented by ! `libgcj'. (Currently set to `1.3') ! `java.specification.vendor' The Runtime Environment specification designer. ! `java.specification.name' ! The name of the Runtime Environment specification (Set to `Java Platform API Specification'). ! `java.class.path' The paths (jar files, zip files and directories) used for finding class files. ! `java.library.path' Directory path used for finding native libraries. ! `java.io.tmpdir' The directory used to put temporary files in. ! `java.compiler' Name of the Just In Time compiler to use by the byte code ! interpreter. Currently not used in `libgcj'. ! `java.ext.dirs' Directories containing jar files with extra libraries. Will be used when resolving classes. ! `java.protocol.handler.pkgs' ! A `|' separated list of package names that is used to find classes ! that implement handlers for `java.net.URL'. ! `java.rmi.server.codebase' ! A list of URLs that is used by the `java.rmi.server.RMIClassLoader' to load classes from. ! `jdbc.drivers' A list of class names that will be loaded by the ! `java.sql.DriverManager' when it starts up. ! `file.separator' The separator used in when directories are included in a filename ! (normally `/' or `\' ). ! `file.encoding' ! The default character encoding used when converting platform ! native files to Unicode (usually set to `8859_1'). ! `path.separator' The standard separator used when a string contains multiple paths ! (normally `:' or `;'), the string is usually not a valid character to use in normal directory names.) ! `line.separator' ! The default line separator used on the platform (normally `\n', ! `\r' or a combination of those two characters). ! `policy.provider' The class name used for the default policy provider returned by ! `java.security.Policy.getPolicy'. ! `user.name' The name of the user running the program. Can be the full name, the login name or empty if unknown. ! `user.home' The default directory to put user specific files in. ! `user.dir' The current working directory from which the program was started. ! `user.language' ! The default language as used by the `java.util.Locale' class. ! `user.region' ! The default region as used by the `java.util.Local' class. ! `user.variant' The default variant of the language and region local used. ! `user.timezone' ! The default timezone as used by the `java.util.TimeZone' class. ! `os.name' The operating system/kernel name that the program runs on. ! `os.arch' The hardware that we are running on. ! `os.version' The version number of the operating system/kernel. ! `awt.appletWarning' The string to display when an untrusted applet is displayed. ! Returned by `java.awt.Window.getWarningString()' when the window is "insecure". ! `awt.toolkit' The class name used for initializing the default ! `java.awt.Toolkit'. Defaults to `gnu.awt.gtk.GtkToolkit'. ! `http.proxyHost' Name of proxy host for http connections. ! `http.proxyPort' Port number to use when a proxy host is in use. +  File: gcj.info, Node: GNU Classpath Properties, Next: libgcj Runtime Properties, Prev: Standard Properties, Up: System properties 12.2 GNU Classpath Properties ============================= ! `libgcj' is based on the GNU Classpath (Essential Libraries for Java) a GNU project to create free core class libraries for use with virtual machines and compilers for the Java language. The following properties are common to libraries based on GNU Classpath. ! `gcj.dumpobject' Enables printing serialization debugging by the ! `java.io.ObjectInput' and `java.io.ObjectOutput' classes when set to something else then the empty string. Only used when running a debug build of the library. ! `gnu.classpath.vm.shortname' ! This is a succinct name of the virtual machine. For `libgcj', ! this will always be `libgcj'. ! `gnu.classpath.home.url' A base URL used for finding system property files (e.g., ! `classpath.security'). By default this is a `file:' URL pointing ! to the `lib' directory under `java.home'. !  File: gcj.info, Node: libgcj Runtime Properties, Prev: GNU Classpath Properties, Up: System properties *************** File: gcj.info, Node: libgcj Runtime Pr *** 3452,3547 **** 12.3 libgcj Runtime Properties ============================== ! The following properties are specific to the 'libgcj' runtime and will normally not be found in other core libraries for the java language. ! 'java.fullversion' ! The combination of 'java.vm.name' and 'java.vm.version'. ! 'java.vm.info' ! Same as 'java.fullversion'. ! 'impl.prefix' ! Used by the 'java.net.DatagramSocket' class when set to something else then the empty string. When set all newly created ! 'DatagramSocket's will try to load a class ! 'java.net.[impl.prefix]DatagramSocketImpl' instead of the normal ! 'java.net.PlainDatagramSocketImpl'. ! 'gnu.gcj.progname' ! The class or binary name that was used to invoke the program. This ! will be the name of the "main" class in the case where the 'gij' front end is used, or the program binary name in the case where an application is compiled to a native binary. ! 'gnu.gcj.user.realname' The real name of the user, as taken from the password file. This may not always hold only the user's name (as some sites put extra information in this field). Also, this property is not available on all platforms. ! 'gnu.gcj.runtime.NameFinder.use_addr2line' ! Whether an external process, 'addr2line', should be used to ! determine line number information when tracing the stack. Setting ! this to 'false' may suppress line numbers when printing stack traces and when using the java.util.logging infrastructure. However, performance may improve significantly for applications that print stack traces or make logging calls frequently. ! 'gnu.gcj.runtime.NameFinder.show_raw' Whether the address of a stack frame should be printed when the ! line number is unavailable. Setting this to 'true' will cause the name of the object and the offset within that object to be printed when no line number is available. This allows for off-line decoding of stack traces if necessary debug information is ! available. The default is 'false', no raw addresses are printed. ! 'gnu.gcj.runtime.NameFinder.remove_unknown' Whether stack frames for non-java code should be included in a ! stack trace. The default value is 'true', stack frames for ! non-java code are suppressed. Setting this to 'false' will cause any non-java stack frames to be printed in addition to frames for the java code. ! 'gnu.gcj.runtime.VMClassLoader.library_control' This controls how shared libraries are automatically loaded by the ! built-in class loader. If this property is set to 'full', a full search is done for each requested class. If this property is set ! to 'cache', then any failed lookups are cached and not tried again. ! If this property is set to 'never' (the default), then lookups are never done. For more information, *Note Extensions::. ! 'gnu.gcj.runtime.endorsed.dirs' ! This is like the standard 'java.endorsed.dirs', property, but specifies some extra directories which are searched after the standard endorsed directories. This is primarily useful for ! telling 'libgcj' about additional libraries which are ordinarily incorporated into the JDK, and which should be loaded by the ! bootstrap class loader, but which are not yet part of 'libgcj' itself for some reason. ! 'gnu.gcj.jit.compiler' ! This is the full path to 'gcj' executable which should be used to ! compile classes just-in-time when 'ClassLoader.defineClass' is ! called. If not set, 'gcj' will not be invoked by the runtime; this ! can also be controlled via 'Compiler.disable'. ! 'gnu.gcj.jit.options' This is a space-separated string of options which should be passed ! to 'gcj' when in JIT mode. If not set, a sensible default is chosen. ! 'gnu.gcj.jit.cachedir' ! This is the directory where cached shared library files are stored. ! If not set, JIT compilation is disabled. This should never be set ! to a directory that is writable by any other user. ! 'gnu.gcj.precompiled.db.path' This is a sequence of file names, each referring to a file created ! by 'gcj-dbtool'. These files will be used by 'libgcj' to find shared libraries corresponding to classes that are loaded from ! bytecode. 'libgcj' often has a built-in default database; it can ! be queried using 'gcj-dbtool -p'.  File: gcj.info, Node: Resources, Next: Index, Prev: System properties, Up: Top --- 3489,3585 ---- 12.3 libgcj Runtime Properties ============================== ! The following properties are specific to the `libgcj' runtime and will normally not be found in other core libraries for the java language. ! `java.fullversion' ! The combination of `java.vm.name' and `java.vm.version'. ! `java.vm.info' ! Same as `java.fullversion'. ! `impl.prefix' ! Used by the `java.net.DatagramSocket' class when set to something else then the empty string. When set all newly created ! `DatagramSocket's will try to load a class ! `java.net.[impl.prefix]DatagramSocketImpl' instead of the normal ! `java.net.PlainDatagramSocketImpl'. ! `gnu.gcj.progname' ! The class or binary name that was used to invoke the program. This ! will be the name of the "main" class in the case where the `gij' front end is used, or the program binary name in the case where an application is compiled to a native binary. ! `gnu.gcj.user.realname' The real name of the user, as taken from the password file. This may not always hold only the user's name (as some sites put extra information in this field). Also, this property is not available on all platforms. ! `gnu.gcj.runtime.NameFinder.use_addr2line' ! Whether an external process, `addr2line', should be used to ! determine line number information when tracing the stack. Setting ! this to `false' may suppress line numbers when printing stack traces and when using the java.util.logging infrastructure. However, performance may improve significantly for applications that print stack traces or make logging calls frequently. ! `gnu.gcj.runtime.NameFinder.show_raw' Whether the address of a stack frame should be printed when the ! line number is unavailable. Setting this to `true' will cause the name of the object and the offset within that object to be printed when no line number is available. This allows for off-line decoding of stack traces if necessary debug information is ! available. The default is `false', no raw addresses are printed. ! `gnu.gcj.runtime.NameFinder.remove_unknown' Whether stack frames for non-java code should be included in a ! stack trace. The default value is `true', stack frames for ! non-java code are suppressed. Setting this to `false' will cause any non-java stack frames to be printed in addition to frames for the java code. ! `gnu.gcj.runtime.VMClassLoader.library_control' This controls how shared libraries are automatically loaded by the ! built-in class loader. If this property is set to `full', a full search is done for each requested class. If this property is set ! to `cache', then any failed lookups are cached and not tried again. ! If this property is set to `never' (the default), then lookups are never done. For more information, *Note Extensions::. ! `gnu.gcj.runtime.endorsed.dirs' ! This is like the standard `java.endorsed.dirs', property, but specifies some extra directories which are searched after the standard endorsed directories. This is primarily useful for ! telling `libgcj' about additional libraries which are ordinarily incorporated into the JDK, and which should be loaded by the ! bootstrap class loader, but which are not yet part of `libgcj' itself for some reason. ! `gnu.gcj.jit.compiler' ! This is the full path to `gcj' executable which should be used to ! compile classes just-in-time when `ClassLoader.defineClass' is ! called. If not set, `gcj' will not be invoked by the runtime; ! this can also be controlled via `Compiler.disable'. ! `gnu.gcj.jit.options' This is a space-separated string of options which should be passed ! to `gcj' when in JIT mode. If not set, a sensible default is chosen. ! `gnu.gcj.jit.cachedir' ! This is the directory where cached shared library files are ! stored. If not set, JIT compilation is disabled. This should ! never be set to a directory that is writable by any other user. ! `gnu.gcj.precompiled.db.path' This is a sequence of file names, each referring to a file created ! by `gcj-dbtool'. These files will be used by `libgcj' to find shared libraries corresponding to classes that are loaded from ! bytecode. `libgcj' often has a built-in default database; it can ! be queried using `gcj-dbtool -p'. !  File: gcj.info, Node: Resources, Next: Index, Prev: System properties, Up: Top *************** File: gcj.info, Node: Resources, Next: *** 3549,3568 **** 13 Resources ************ ! While writing 'gcj' and 'libgcj' we have, of course, relied heavily on documentation from Sun Microsystems. In particular we have used The Java Language Specification (both first and second editions), the Java Class Libraries (volumes one and two), and the Java Virtual Machine Specification. In addition we've used Sun's online documentation. ! The current 'gcj' home page is . ! For more information on GCC, see . ! Some 'libgcj' testing is done using the Mauve test suite. This is a free software Java class library test suite which is being written ! because the JCK is not free. See for ! more information.  File: gcj.info, Node: Index, Prev: Resources, Up: Top --- 3587,3606 ---- 13 Resources ************ ! While writing `gcj' and `libgcj' we have, of course, relied heavily on documentation from Sun Microsystems. In particular we have used The Java Language Specification (both first and second editions), the Java Class Libraries (volumes one and two), and the Java Virtual Machine Specification. In addition we've used Sun's online documentation. ! The current `gcj' home page is `http://gcc.gnu.org/java/'. ! For more information on GCC, see `http://gcc.gnu.org/'. ! Some `libgcj' testing is done using the Mauve test suite. This is a free software Java class library test suite which is being written ! because the JCK is not free. See `http://www.sourceware.org/mauve/' ! for more information.  File: gcj.info, Node: Index, Prev: Resources, Up: Top *************** Index *** 3575,3655 **** * class path: Input Options. (line 6) * class$: Reference types. (line 20) ! * elements on template: Arrays. (line 45) * FDL, GNU Free Documentation License: GNU Free Documentation License. (line 6) * GCJ_PROPERTIES: Extensions. (line 56) - * GCJ_PROPERTIES <1>: Extensions. (line 56) * jclass: Reference types. (line 16) * jobject: Reference types. (line 16) * jstring: Reference types. (line 16) ! * JvAllocBytes: Mixing with C++. (line 98) ! * JvAttachCurrentThread: Invocation. (line 54) ! * JvCreateJavaVM: Invocation. (line 10) * JvDetachCurrentThread: Invocation. (line 68) ! * JvFree: Memory allocation. (line 18) ! * JvGetArrayLength: Arrays. (line 85) ! * JvGetStringChars: Strings. (line 24) ! * JvGetStringUTFLength: Strings. (line 28) ! * JvGetStringUTFRegion: Strings. (line 32) ! * JvMalloc: Memory allocation. (line 10) ! * JvNewBooleanArray: Arrays. (line 82) ! * JvNewObjectArray: Arrays. (line 55) ! * JvNewString: Strings. (line 10) ! * JvNewStringLatin1: Strings. (line 14) ! * JvNewStringLatin1 <1>: Strings. (line 17) ! * JvNewStringUTF: Strings. (line 20) ! * JvPrimClass: Primitive types. (line 35) ! * JvRealloc: Memory allocation. (line 14)  Tag Table: ! Node: Top2679 ! Node: Copying4098 ! Node: GNU Free Documentation License41630 ! Node: Invoking gcj66754 ! Node: Input and output files67517 ! Node: Input Options69039 ! Node: Encodings72314 ! Node: Warnings73520 ! Node: Linking74633 ! Node: Code Generation77571 ! Node: Configure-time Options84347 ! Node: Compatibility86087 ! Node: Limitations86606 ! Node: Extensions88184 ! Node: Invoking jcf-dump91275 ! Node: Invoking gij92220 ! Node: Invoking gcj-dbtool95476 ! Node: Invoking jv-convert97937 ! Node: Invoking grmic99016 ! Node: Invoking gc-analyze100402 ! Node: Invoking aot-compile101843 ! Node: Invoking rebuild-gcj-db102791 ! Node: About CNI103101 ! Node: Basic concepts104560 ! Node: Packages107456 ! Node: Primitive types109784 ! Node: Reference types111461 ! Node: Interfaces112545 ! Node: Objects and Classes113456 ! Node: Class Initialization115651 ! Node: Object allocation117994 ! Node: Memory allocation118784 ! Node: Arrays119416 ! Node: Methods122226 ! Node: Strings125047 ! Node: Mixing with C++126551 ! Node: Exception Handling130024 ! Node: Synchronization131659 ! Node: Invocation133648 ! Node: Reflection138600 ! Node: System properties139058 ! Node: Standard Properties139935 ! Node: GNU Classpath Properties144366 ! Node: libgcj Runtime Properties145412 ! Node: Resources149915 ! Node: Index150729  End Tag Table --- 3613,3691 ---- * class path: Input Options. (line 6) * class$: Reference types. (line 20) ! * elements on template: Arrays. (line 46) * FDL, GNU Free Documentation License: GNU Free Documentation License. (line 6) * GCJ_PROPERTIES: Extensions. (line 56) * jclass: Reference types. (line 16) * jobject: Reference types. (line 16) * jstring: Reference types. (line 16) ! * JvAllocBytes: Mixing with C++. (line 99) ! * JvAttachCurrentThread: Invocation. (line 55) ! * JvCreateJavaVM: Invocation. (line 11) * JvDetachCurrentThread: Invocation. (line 68) ! * JvFree: Memory allocation. (line 19) ! * JvGetArrayLength: Arrays. (line 86) ! * JvGetStringChars: Strings. (line 25) ! * JvGetStringUTFLength: Strings. (line 29) ! * JvGetStringUTFRegion: Strings. (line 34) ! * JvMalloc: Memory allocation. (line 11) ! * JvNewBooleanArray: Arrays. (line 83) ! * JvNewObjectArray: Arrays. (line 57) ! * JvNewString: Strings. (line 11) ! * JvNewStringLatin1: Strings. (line 15) ! * JvNewStringUTF: Strings. (line 21) ! * JvPrimClass: Primitive types. (line 36) ! * JvRealloc: Memory allocation. (line 15)  Tag Table: ! Node: Top2729 ! Node: Copying4148 ! Node: GNU Free Documentation License41698 ! Node: Invoking gcj66841 ! Node: Input and output files67604 ! Node: Input Options69130 ! Node: Encodings72404 ! Node: Warnings73610 ! Node: Linking74723 ! Node: Code Generation77662 ! Node: Configure-time Options84442 ! Node: Compatibility86182 ! Node: Limitations86666 ! Node: Extensions88248 ! Node: Invoking jcf-dump91342 ! Node: Invoking gij92287 ! Node: Invoking gcj-dbtool95538 ! Node: Invoking jv-convert98004 ! Node: Invoking grmic99083 ! Node: Invoking gc-analyze100469 ! Node: Invoking aot-compile101910 ! Node: Invoking rebuild-gcj-db102859 ! Node: About CNI103169 ! Node: Basic concepts104628 ! Node: Packages107524 ! Node: Primitive types109852 ! Node: Reference types111530 ! Node: Interfaces112619 ! Node: Objects and Classes113530 ! Node: Class Initialization115725 ! Node: Object allocation118067 ! Node: Memory allocation118857 ! Node: Arrays119489 ! Node: Methods122299 ! Node: Strings125120 ! Node: Mixing with C++126624 ! Node: Exception Handling130095 ! Node: Synchronization131729 ! Node: Invocation133719 ! Node: Reflection138655 ! Node: System properties139116 ! Node: Standard Properties139993 ! Node: GNU Classpath Properties144425 ! Node: libgcj Runtime Properties145472 ! Node: Resources149974 ! Node: Index150788  End Tag Table diff -Nrcpad gcc-6.3.0/gcc/doc/gcov-dump.1 gcc-6.4.0/gcc/doc/gcov-dump.1 *** gcc-6.3.0/gcc/doc/gcov-dump.1 Thu Jan 1 00:00:00 1970 --- gcc-6.4.0/gcc/doc/gcov-dump.1 Tue Jul 4 07:37:47 2017 *************** *** 0 **** --- 1,217 ---- + .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) + .\" + .\" Standard preamble: + .\" ======================================================================== + .de Sp \" Vertical space (when we can't use .PP) + .if t .sp .5v + .if n .sp + .. + .de Vb \" Begin verbatim text + .ft CW + .nf + .ne \\$1 + .. + .de Ve \" End verbatim text + .ft R + .fi + .. + .\" Set up some character translations and predefined strings. \*(-- will + .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left + .\" double quote, and \*(R" will give a right double quote. \*(C+ will + .\" give a nicer C++. Capital omega is used to do unbreakable dashes and + .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, + .\" nothing in troff, for use with C<>. + .tr \(*W- + .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' + .ie n \{\ + . ds -- \(*W- + . ds PI pi + . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch + . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch + . ds L" "" + . ds R" "" + . ds C` "" + . ds C' "" + 'br\} + .el\{\ + . ds -- \|\(em\| + . ds PI \(*p + . ds L" `` + . ds R" '' + . ds C` + . ds C' + 'br\} + .\" + .\" Escape single quotes in literal strings from groff's Unicode transform. + .ie \n(.g .ds Aq \(aq + .el .ds Aq ' + .\" + .\" If the F register is turned on, we'll generate index entries on stderr for + .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index + .\" entries marked with X<> in POD. Of course, you'll have to process the + .\" output yourself in some meaningful fashion. + .\" + .\" Avoid warning from groff about undefined register 'F'. + .de IX + .. + .nr rF 0 + .if \n(.g .if rF .nr rF 1 + .if (\n(rF:(\n(.g==0)) \{ + . if \nF \{ + . de IX + . tm Index:\\$1\t\\n%\t"\\$2" + .. + . if !\nF==2 \{ + . nr % 0 + . nr F 2 + . \} + . \} + .\} + .rr rF + .\" + .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). + .\" Fear. Run. Save yourself. No user-serviceable parts. + . \" fudge factors for nroff and troff + .if n \{\ + . ds #H 0 + . ds #V .8m + . ds #F .3m + . ds #[ \f1 + . ds #] \fP + .\} + .if t \{\ + . ds #H ((1u-(\\\\n(.fu%2u))*.13m) + . ds #V .6m + . ds #F 0 + . ds #[ \& + . ds #] \& + .\} + . \" simple accents for nroff and troff + .if n \{\ + . ds ' \& + . ds ` \& + . ds ^ \& + . ds , \& + . ds ~ ~ + . ds / + .\} + .if t \{\ + . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" + . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' + . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' + . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' + . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' + . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' + .\} + . \" troff and (daisy-wheel) nroff accents + .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' + .ds 8 \h'\*(#H'\(*b\h'-\*(#H' + .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] + .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' + .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' + .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] + .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] + .ds ae a\h'-(\w'a'u*4/10)'e + .ds Ae A\h'-(\w'A'u*4/10)'E + . \" corrections for vroff + .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' + .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' + . \" for low resolution devices (crt and lpr) + .if \n(.H>23 .if \n(.V>19 \ + \{\ + . ds : e + . ds 8 ss + . ds o a + . ds d- d\h'-1'\(ga + . ds D- D\h'-1'\(hy + . ds th \o'bp' + . ds Th \o'LP' + . ds ae ae + . ds Ae AE + .\} + .rm #[ #] #H #V #F C + .\" ======================================================================== + .\" + .IX Title "GCOV-DUMP 1" + .TH GCOV-DUMP 1 "2017-07-04" "gcc-6.4.0" "GNU" + .\" For nroff, turn off justification. Always turn off hyphenation; it makes + .\" way too many mistakes in technical documents. + .if n .ad l + .nh + .SH "NAME" + gcov\-dump \- offline gcda and gcno profile dump tool + .SH "SYNOPSIS" + .IX Header "SYNOPSIS" + gcov-dump [\fB\-v\fR|\fB\-\-version\fR] + [\fB\-h\fR|\fB\-\-help\fR] + [\fB\-l\fR|\fB\-\-long\fR] + [\fB\-p\fR|\fB\-\-positions\fR] + [\fB\-w\fR|\fB\-\-working\-sets\fR] \fIgcovfiles\fR + .SH "DESCRIPTION" + .IX Header "DESCRIPTION" + \&\fBgcov-dump\fR is a tool you can use in conjunction with \s-1GCC\s0 to + dump content of gcda and gcno profile files offline. + .SH "OPTIONS" + .IX Header "OPTIONS" + .IP "\fB\-h\fR" 4 + .IX Item "-h" + .PD 0 + .IP "\fB\-\-help\fR" 4 + .IX Item "--help" + .PD + Display help about using \fBgcov-dump\fR (on the standard output), and + exit without doing any further processing. + .IP "\fB\-l\fR" 4 + .IX Item "-l" + .PD 0 + .IP "\fB\-\-long\fR" 4 + .IX Item "--long" + .PD + Dump content of records. + .IP "\fB\-p\fR" 4 + .IX Item "-p" + .PD 0 + .IP "\fB\-\-positions\fR" 4 + .IX Item "--positions" + .PD + Dump positions of records. + .IP "\fB\-v\fR" 4 + .IX Item "-v" + .PD 0 + .IP "\fB\-\-version\fR" 4 + .IX Item "--version" + .PD + Display the \fBgcov-dump\fR version number (on the standard output), + and exit without doing any further processing. + .IP "\fB\-w\fR" 4 + .IX Item "-w" + .PD 0 + .IP "\fB\-\-working\-sets\fR" 4 + .IX Item "--working-sets" + .PD + Dump working set computed from summary. + .SH "COPYRIGHT" + .IX Header "COPYRIGHT" + Copyright (c) 2017 Free Software Foundation, Inc. + .PP + Permission is granted to copy, distribute and/or modify this document + under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or + any later version published by the Free Software Foundation; with the + Invariant Sections being \*(L"\s-1GNU\s0 General Public License\*(R" and \*(L"Funding + Free Software\*(R", the Front-Cover texts being (a) (see below), and with + the Back-Cover Texts being (b) (see below). A copy of the license is + included in the \fIgfdl\fR\|(7) man page. + .PP + (a) The \s-1FSF\s0's Front-Cover Text is: + .PP + .Vb 1 + \& A GNU Manual + .Ve + .PP + (b) The \s-1FSF\s0's Back-Cover Text is: + .PP + .Vb 3 + \& You have freedom to copy and modify this GNU Manual, like GNU + \& software. Copies published by the Free Software Foundation raise + \& funds for GNU development. + .Ve diff -Nrcpad gcc-6.3.0/gcc/doc/gcov-dump.texi gcc-6.4.0/gcc/doc/gcov-dump.texi *** gcc-6.3.0/gcc/doc/gcov-dump.texi Thu Jan 1 00:00:00 1970 --- gcc-6.4.0/gcc/doc/gcov-dump.texi Thu Jun 22 11:17:15 2017 *************** *** 0 **** --- 1,93 ---- + @c Copyright (C) 2017 Free Software Foundation, Inc. + @c This is part of the GCC manual. + @c For copying conditions, see the file gcc.texi. + + @ignore + @c man begin COPYRIGHT + Copyright @copyright{} 2017 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 ``GNU General Public License'' and ``Funding + Free Software'', the Front-Cover texts being (a) (see below), and with + the Back-Cover Texts being (b) (see below). A copy of the license is + included in the gfdl(7) man page. + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + @c man end + @c Set file name and title for the man page. + @setfilename gcov-dump + @settitle offline gcda and gcno profile dump tool + @end ignore + + @node Gcov-dump + @chapter @command{gcov-dump}---an Offline Gcda and Gcno Profile Dump Tool + + @menu + * Gcov-dump Intro:: Introduction to gcov-dump. + * Invoking Gcov-dump:: How to use gcov-dump. + @end menu + + @node Gcov-dump Intro + @section Introduction to @command{gcov-dump} + @c man begin DESCRIPTION + + @command{gcov-dump} is a tool you can use in conjunction with GCC to + dump content of gcda and gcno profile files offline. + + @c man end + + @node Invoking Gcov-dump + @section Invoking @command{gcov-dump} + + @smallexample + Usage: gcov-dump @r{[}@var{OPTION}@r{]} ... @var{gcovfiles} + @end smallexample + + @command{gcov-dump} accepts the following options: + + @ignore + @c man begin SYNOPSIS + gcov-dump [@option{-v}|@option{--version}] + [@option{-h}|@option{--help}] + [@option{-l}|@option{--long}] + [@option{-p}|@option{--positions}] + [@option{-w}|@option{--working-sets}] @var{gcovfiles} + @c man end + @end ignore + + @c man begin OPTIONS + @table @gcctabopt + @item -h + @itemx --help + Display help about using @command{gcov-dump} (on the standard output), and + exit without doing any further processing. + + @item -l + @itemx --long + Dump content of records. + + @item -p + @itemx --positions + Dump positions of records. + + @item -v + @itemx --version + Display the @command{gcov-dump} version number (on the standard output), + and exit without doing any further processing. + + @item -w + @itemx --working-sets + Dump working set computed from summary. + @end table + + @c man end diff -Nrcpad gcc-6.3.0/gcc/doc/gcov-tool.1 gcc-6.4.0/gcc/doc/gcov-tool.1 *** gcc-6.3.0/gcc/doc/gcov-tool.1 Wed Dec 21 08:06:54 2016 --- gcc-6.4.0/gcc/doc/gcov-tool.1 Tue Jul 4 07:37:47 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GCOV-TOOL 1" ! .TH GCOV-TOOL 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GCOV-TOOL 1" ! .TH GCOV-TOOL 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** gcov\-tool \- offline gcda profile proce *** 141,163 **** gcov-tool [\fB\-v\fR|\fB\-\-version\fR] [\fB\-h\fR|\fB\-\-help\fR] .PP gcov-tool merge [merge\-options] \fIdirectory1\fR \fIdirectory2\fR [\fB\-v\fR|\fB\-\-verbose\fR] - [\fB\-o\fR| \fB\-\-output\fR \fIdirectory\fR] [\fB\-w\fR|\fB\-\-weight\fR \fIw1,w2\fR] .PP gcov-tool rewrite [rewrite\-options] \fIdirectory\fR ! [\fB\-v\fR|\fB\-\-verbose\fR] [\fB\-o\fR|\fB\-\-output\fR \fIdirectory\fR] [\fB\-s\fR|\fB\-\-scale\fR \fIfloat_or_simple\-frac_value\fR] ! [\fB\-n\fR|\fB\-\-normalize\fR \fIlong_long_value\fR] .PP gcov-tool overlap [overlap\-options] \fIdirectory1\fR \fIdirectory2\fR - [\fB\-v\fR|\fB\-\-verbose\fR] - [\fB\-h\fR|\fB\-\-hotonly\fR] [\fB\-f\fR|\fB\-\-function\fR] [\fB\-F\fR|\fB\-\-fullname\fR] [\fB\-o\fR|\fB\-\-object\fR] [\fB\-t\fR|\fB\-\-hot_threshold\fR] \fIfloat\fR .SH "DESCRIPTION" .IX Header "DESCRIPTION" \&\fBgcov-tool\fR is an offline tool to process gcc's gcda profile files. --- 145,167 ---- gcov-tool [\fB\-v\fR|\fB\-\-version\fR] [\fB\-h\fR|\fB\-\-help\fR] .PP gcov-tool merge [merge\-options] \fIdirectory1\fR \fIdirectory2\fR + [\fB\-o\fR|\fB\-\-output\fR \fIdirectory\fR] [\fB\-v\fR|\fB\-\-verbose\fR] [\fB\-w\fR|\fB\-\-weight\fR \fIw1,w2\fR] .PP gcov-tool rewrite [rewrite\-options] \fIdirectory\fR ! [\fB\-n\fR|\fB\-\-normalize\fR \fIlong_long_value\fR] [\fB\-o\fR|\fB\-\-output\fR \fIdirectory\fR] [\fB\-s\fR|\fB\-\-scale\fR \fIfloat_or_simple\-frac_value\fR] ! [\fB\-v\fR|\fB\-\-verbose\fR] .PP gcov-tool overlap [overlap\-options] \fIdirectory1\fR \fIdirectory2\fR [\fB\-f\fR|\fB\-\-function\fR] [\fB\-F\fR|\fB\-\-fullname\fR] + [\fB\-h\fR|\fB\-\-hotonly\fR] [\fB\-o\fR|\fB\-\-object\fR] [\fB\-t\fR|\fB\-\-hot_threshold\fR] \fIfloat\fR + [\fB\-v\fR|\fB\-\-verbose\fR] .SH "DESCRIPTION" .IX Header "DESCRIPTION" \&\fBgcov-tool\fR is an offline tool to process gcc's gcda profile files. *************** and exit without doing any further proce *** 221,233 **** .IX Item "merge" Merge two profile directories. .RS 4 - .IP "\fB\-v\fR" 4 - .IX Item "-v" - .PD 0 - .IP "\fB\-\-verbose\fR" 4 - .IX Item "--verbose" - .PD - Set the verbose mode. .IP "\fB\-o\fR \fIdirectory\fR" 4 .IX Item "-o directory" .PD 0 --- 225,230 ---- *************** Set the verbose mode. *** 236,241 **** --- 233,245 ---- .PD Set the output profile directory. Default output directory name is \&\fImerged_profile\fR. + .IP "\fB\-v\fR" 4 + .IX Item "-v" + .PD 0 + .IP "\fB\-\-verbose\fR" 4 + .IX Item "--verbose" + .PD + Set the verbose mode. .IP "\fB\-w\fR \fIw1\fR\fB,\fR\fIw2\fR" 4 .IX Item "-w w1,w2" .PD 0 *************** respectively. The default weights are 1 *** 251,263 **** .IX Item "rewrite" Read the specified profile directory and rewrite to a new directory. .RS 4 ! .IP "\fB\-v\fR" 4 ! .IX Item "-v" .PD 0 ! .IP "\fB\-\-verbose\fR" 4 ! .IX Item "--verbose" .PD ! Set the verbose mode. .IP "\fB\-o\fR \fIdirectory\fR" 4 .IX Item "-o directory" .PD 0 --- 255,268 ---- .IX Item "rewrite" Read the specified profile directory and rewrite to a new directory. .RS 4 ! .IP "\fB\-n\fR \fIlong_long_value\fR" 4 ! .IX Item "-n long_long_value" .PD 0 ! .IP "\fB\-\-normalize \fR" 4 ! .IX Item "--normalize " .PD ! Normalize the profile. The specified value is the max counter value ! in the new profile. .IP "\fB\-o\fR \fIdirectory\fR" 4 .IX Item "-o directory" .PD 0 *************** Set the output profile directory. Defaul *** 273,286 **** .PD Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such 1, 2, 2/3, and 5/3. ! .IP "\fB\-n\fR \fIlong_long_value\fR" 4 ! .IX Item "-n long_long_value" .PD 0 ! .IP "\fB\-\-normalize \fR" 4 ! .IX Item "--normalize " .PD ! Normalize the profile. The specified value is the max counter value ! in the new profile. .RE .RS 4 .RE --- 278,290 ---- .PD Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such 1, 2, 2/3, and 5/3. ! .IP "\fB\-v\fR" 4 ! .IX Item "-v" .PD 0 ! .IP "\fB\-\-verbose\fR" 4 ! .IX Item "--verbose" .PD ! Set the verbose mode. .RE .RS 4 .RE *************** for all arc counter i, where p1_counter[ *** 293,312 **** matched counters and p1_sum_all and p2_sum_all are the sum of counter values in profile 1 and profile 2, respectively. .RS 4 - .IP "\fB\-v\fR" 4 - .IX Item "-v" - .PD 0 - .IP "\fB\-\-verbose\fR" 4 - .IX Item "--verbose" - .PD - Set the verbose mode. - .IP "\fB\-h\fR" 4 - .IX Item "-h" - .PD 0 - .IP "\fB\-\-hotonly\fR" 4 - .IX Item "--hotonly" - .PD - Only print info for hot objects/functions. .IP "\fB\-f\fR" 4 .IX Item "-f" .PD 0 --- 297,302 ---- *************** Print function level overlap score. *** 321,326 **** --- 311,323 ---- .IX Item "--fullname" .PD Print full gcda filename. + .IP "\fB\-h\fR" 4 + .IX Item "-h" + .PD 0 + .IP "\fB\-\-hotonly\fR" 4 + .IX Item "--hotonly" + .PD + Only print info for hot objects/functions. .IP "\fB\-o\fR" 4 .IX Item "-o" .PD 0 *************** Print object level overlap score. *** 335,340 **** --- 332,344 ---- .IX Item "--hot_threshold " .PD Set the threshold for hot counter value. + .IP "\fB\-v\fR" 4 + .IX Item "-v" + .PD 0 + .IP "\fB\-\-verbose\fR" 4 + .IX Item "--verbose" + .PD + Set the verbose mode. .RE .RS 4 .RE *************** Set the threshold for hot counter value. *** 344,350 **** \&\fIgcc\fR. .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 2014\-2016 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or --- 348,354 ---- \&\fIgcc\fR. .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 2014\-2017 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or diff -Nrcpad gcc-6.3.0/gcc/doc/gcov-tool.texi gcc-6.4.0/gcc/doc/gcov-tool.texi *** gcc-6.3.0/gcc/doc/gcov-tool.texi Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/doc/gcov-tool.texi Tue Jul 4 07:15:57 2017 *************** *** 4,10 **** @ignore @c man begin COPYRIGHT ! Copyright @copyright{} 2014-2016 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 --- 4,10 ---- @ignore @c man begin COPYRIGHT ! Copyright @copyright{} 2014-2017 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 *************** gcov-tool @r{[}@var{global-options}@r{]} *** 113,135 **** gcov-tool [@option{-v}|@option{--version}] [@option{-h}|@option{--help}] gcov-tool merge [merge-options] @var{directory1} @var{directory2} [@option{-v}|@option{--verbose}] - [@option{-o}|@option{ --output} @var{directory}] [@option{-w}|@option{--weight} @var{w1,w2}] gcov-tool rewrite [rewrite-options] @var{directory} ! [@option{-v}|@option{--verbose}] [@option{-o}|@option{--output} @var{directory}] [@option{-s}|@option{--scale} @var{float_or_simple-frac_value}] ! [@option{-n}|@option{--normalize} @var{long_long_value}] gcov-tool overlap [overlap-options] @var{directory1} @var{directory2} - [@option{-v}|@option{--verbose}] - [@option{-h}|@option{--hotonly}] [@option{-f}|@option{--function}] [@option{-F}|@option{--fullname}] [@option{-o}|@option{--object}] [@option{-t}|@option{--hot_threshold}] @var{float} @c man end @c man begin SEEALSO --- 113,135 ---- gcov-tool [@option{-v}|@option{--version}] [@option{-h}|@option{--help}] gcov-tool merge [merge-options] @var{directory1} @var{directory2} + [@option{-o}|@option{--output} @var{directory}] [@option{-v}|@option{--verbose}] [@option{-w}|@option{--weight} @var{w1,w2}] gcov-tool rewrite [rewrite-options] @var{directory} ! [@option{-n}|@option{--normalize} @var{long_long_value}] [@option{-o}|@option{--output} @var{directory}] [@option{-s}|@option{--scale} @var{float_or_simple-frac_value}] ! [@option{-v}|@option{--verbose}] gcov-tool overlap [overlap-options] @var{directory1} @var{directory2} [@option{-f}|@option{--function}] [@option{-F}|@option{--fullname}] + [@option{-h}|@option{--hotonly}] [@option{-o}|@option{--object}] [@option{-t}|@option{--hot_threshold}] @var{float} + [@option{-v}|@option{--verbose}] @c man end @c man begin SEEALSO *************** and exit without doing any further proce *** 152,168 **** @item merge Merge two profile directories. - @table @gcctabopt - @item -v - @itemx --verbose - Set the verbose mode. @item -o @var{directory} @itemx --output @var{directory} Set the output profile directory. Default output directory name is @var{merged_profile}. @item -w @var{w1},@var{w2} @itemx --weight @var{w1},@var{w2} Set the merge weights of the @var{directory1} and @var{directory2}, --- 152,168 ---- @item merge Merge two profile directories. @table @gcctabopt @item -o @var{directory} @itemx --output @var{directory} Set the output profile directory. Default output directory name is @var{merged_profile}. + @item -v + @itemx --verbose + Set the verbose mode. + @item -w @var{w1},@var{w2} @itemx --weight @var{w1},@var{w2} Set the merge weights of the @var{directory1} and @var{directory2}, *************** respectively. The default weights are 1 *** 171,181 **** @item rewrite Read the specified profile directory and rewrite to a new directory. - @table @gcctabopt ! @item -v ! @itemx --verbose ! Set the verbose mode. @item -o @var{directory} @itemx --output @var{directory} --- 171,182 ---- @item rewrite Read the specified profile directory and rewrite to a new directory. @table @gcctabopt ! ! @item -n @var{long_long_value} ! @itemx --normalize ! Normalize the profile. The specified value is the max counter value ! in the new profile. @item -o @var{directory} @itemx --output @var{directory} *************** Set the output profile directory. Defaul *** 186,195 **** Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such 1, 2, 2/3, and 5/3. ! @item -n @var{long_long_value} ! @itemx --normalize ! Normalize the profile. The specified value is the max counter value ! in the new profile. @end table @item overlap --- 187,195 ---- Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such 1, 2, 2/3, and 5/3. ! @item -v ! @itemx --verbose ! Set the verbose mode. @end table @item overlap *************** matched counters and p1_sum_all and p2_s *** 201,214 **** values in profile 1 and profile 2, respectively. @table @gcctabopt - @item -v - @itemx --verbose - Set the verbose mode. - - @item -h - @itemx --hotonly - Only print info for hot objects/functions. - @item -f @itemx --function Print function level overlap score. --- 201,206 ---- *************** Print function level overlap score. *** 217,222 **** --- 209,218 ---- @itemx --fullname Print full gcda filename. + @item -h + @itemx --hotonly + Only print info for hot objects/functions. + @item -o @itemx --object Print object level overlap score. *************** Print object level overlap score. *** 224,229 **** --- 220,229 ---- @item -t @var{float} @itemx --hot_threshold Set the threshold for hot counter value. + + @item -v + @itemx --verbose + Set the verbose mode. @end table @end table diff -Nrcpad gcc-6.3.0/gcc/doc/gcov.1 gcc-6.4.0/gcc/doc/gcov.1 *** gcc-6.3.0/gcc/doc/gcov.1 Wed Dec 21 08:06:51 2016 --- gcc-6.4.0/gcc/doc/gcov.1 Tue Jul 4 07:37:44 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GCOV 1" ! .TH GCOV 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GCOV 1" ! .TH GCOV 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** in fine-tuning the performance of your p *** 206,231 **** timing information you can use along with the information you get from \&\fBgcov\fR. .PP ! \&\fBgcov\fR works only on code compiled with \s-1GCC.\s0 It is not compatible with any other profiling or test coverage mechanism. .SH "OPTIONS" .IX Header "OPTIONS" - .IP "\fB\-h\fR" 4 - .IX Item "-h" - .PD 0 - .IP "\fB\-\-help\fR" 4 - .IX Item "--help" - .PD - Display help about using \fBgcov\fR (on the standard output), and - exit without doing any further processing. - .IP "\fB\-v\fR" 4 - .IX Item "-v" - .PD 0 - .IP "\fB\-\-version\fR" 4 - .IX Item "--version" - .PD - Display the \fBgcov\fR version number (on the standard output), - and exit without doing any further processing. .IP "\fB\-a\fR" 4 .IX Item "-a" .PD 0 --- 210,219 ---- timing information you can use along with the information you get from \&\fBgcov\fR. .PP ! \&\fBgcov\fR works only on code compiled with \s-1GCC. \s0 It is not compatible with any other profiling or test coverage mechanism. .SH "OPTIONS" .IX Header "OPTIONS" .IP "\fB\-a\fR" 4 .IX Item "-a" .PD 0 *************** be shown, unless the \fB\-u\fR option is *** 254,266 **** .PD Write branch frequencies as the number of branches taken, rather than the percentage of branches taken. ! .IP "\fB\-n\fR" 4 ! .IX Item "-n" .PD 0 ! .IP "\fB\-\-no\-output\fR" 4 ! .IX Item "--no-output" .PD ! Do not create the \fBgcov\fR output file. .IP "\fB\-l\fR" 4 .IX Item "-l" .PD 0 --- 242,311 ---- .PD Write branch frequencies as the number of branches taken, rather than the percentage of branches taken. ! .IP "\fB\-d\fR" 4 ! .IX Item "-d" .PD 0 ! .IP "\fB\-\-display\-progress\fR" 4 ! .IX Item "--display-progress" .PD ! Display the progress on the standard output. ! .IP "\fB\-f\fR" 4 ! .IX Item "-f" ! .PD 0 ! .IP "\fB\-\-function\-summaries\fR" 4 ! .IX Item "--function-summaries" ! .PD ! Output summaries for each function in addition to the file level summary. ! .IP "\fB\-h\fR" 4 ! .IX Item "-h" ! .PD 0 ! .IP "\fB\-\-help\fR" 4 ! .IX Item "--help" ! .PD ! Display help about using \fBgcov\fR (on the standard output), and ! exit without doing any further processing. ! .IP "\fB\-i\fR" 4 ! .IX Item "-i" ! .PD 0 ! .IP "\fB\-\-intermediate\-format\fR" 4 ! .IX Item "--intermediate-format" ! .PD ! Output gcov file in an easy-to-parse intermediate text format that can ! be used by \fBlcov\fR or other tools. The output is a single ! \&\fI.gcov\fR file per \fI.gcda\fR file. No source code is required. ! .Sp ! The format of the intermediate \fI.gcov\fR file is plain text with ! one entry per line ! .Sp ! .Vb 4 ! \& file: ! \& function:,, ! \& lcount:, ! \& branch:, ! \& ! \& Where the is ! \& notexec (Branch not executed) ! \& taken (Branch executed and taken) ! \& nottaken (Branch executed, but not taken) ! \& ! \& There can be multiple entries in an intermediate gcov ! \& file. All entries following a pertain to that source file ! \& until the next entry. ! .Ve ! .Sp ! Here is a sample when \fB\-i\fR is used in conjunction with \fB\-b\fR option: ! .Sp ! .Vb 9 ! \& file:array.cc ! \& function:11,1,_Z3sumRKSt6vectorIPiSaIS0_EE ! \& function:22,1,main ! \& lcount:11,1 ! \& lcount:12,1 ! \& lcount:14,1 ! \& branch:14,taken ! \& lcount:26,1 ! \& branch:28,nottaken ! .Ve .IP "\fB\-l\fR" 4 .IX Item "-l" .PD 0 *************** produce an output file called \fIa.c##x. *** 275,280 **** --- 320,354 ---- multiple source files and you want to see the individual contributions. If you use the \fB\-p\fR option, both the including and included file names will be complete path names. + .IP "\fB\-m\fR" 4 + .IX Item "-m" + .PD 0 + .IP "\fB\-\-demangled\-names\fR" 4 + .IX Item "--demangled-names" + .PD + Display demangled function names in output. The default is to show + mangled function names. + .IP "\fB\-n\fR" 4 + .IX Item "-n" + .PD 0 + .IP "\fB\-\-no\-output\fR" 4 + .IX Item "--no-output" + .PD + Do not create the \fBgcov\fR output file. + .IP "\fB\-o\fR \fIdirectory|file\fR" 4 + .IX Item "-o directory|file" + .PD 0 + .IP "\fB\-\-object\-directory\fR \fIdirectory\fR" 4 + .IX Item "--object-directory directory" + .IP "\fB\-\-object\-file\fR \fIfile\fR" 4 + .IX Item "--object-file file" + .PD + Specify either the directory containing the gcov data files, or the + object path name. The \fI.gcno\fR, and + \&\fI.gcda\fR data files are searched for using this option. If a directory + is specified, the data files are in that directory and named after the + input file name, without its extension. If a file is specified here, + the data files are named after that file, without its extension. .IP "\fB\-p\fR" 4 .IX Item "-p" .PD 0 *************** Only output information about source fil *** 298,324 **** (after source prefix elision). Absolute paths are usually system header files and coverage of any inline functions therein is normally uninteresting. - .IP "\fB\-f\fR" 4 - .IX Item "-f" - .PD 0 - .IP "\fB\-\-function\-summaries\fR" 4 - .IX Item "--function-summaries" - .PD - Output summaries for each function in addition to the file level summary. - .IP "\fB\-o\fR \fIdirectory|file\fR" 4 - .IX Item "-o directory|file" - .PD 0 - .IP "\fB\-\-object\-directory\fR \fIdirectory\fR" 4 - .IX Item "--object-directory directory" - .IP "\fB\-\-object\-file\fR \fIfile\fR" 4 - .IX Item "--object-file file" - .PD - Specify either the directory containing the gcov data files, or the - object path name. The \fI.gcno\fR, and - \&\fI.gcda\fR data files are searched for using this option. If a directory - is specified, the data files are in that directory and named after the - input file name, without its extension. If a file is specified here, - the data files are named after that file, without its extension. .IP "\fB\-s\fR \fIdirectory\fR" 4 .IX Item "-s directory" .PD 0 --- 372,377 ---- *************** applied before determining whether the s *** 338,400 **** .PD When branch probabilities are given, include those of unconditional branches. Unconditional branches are normally not interesting. ! .IP "\fB\-d\fR" 4 ! .IX Item "-d" .PD 0 ! .IP "\fB\-\-display\-progress\fR" 4 ! .IX Item "--display-progress" .PD ! Display the progress on the standard output. ! .IP "\fB\-i\fR" 4 ! .IX Item "-i" .PD 0 ! .IP "\fB\-\-intermediate\-format\fR" 4 ! .IX Item "--intermediate-format" .PD ! Output gcov file in an easy-to-parse intermediate text format that can ! be used by \fBlcov\fR or other tools. The output is a single ! \&\fI.gcov\fR file per \fI.gcda\fR file. No source code is required. ! .Sp ! The format of the intermediate \fI.gcov\fR file is plain text with ! one entry per line ! .Sp ! .Vb 4 ! \& file: ! \& function:,, ! \& lcount:, ! \& branch:, ! \& ! \& Where the is ! \& notexec (Branch not executed) ! \& taken (Branch executed and taken) ! \& nottaken (Branch executed, but not taken) ! \& ! \& There can be multiple entries in an intermediate gcov ! \& file. All entries following a pertain to that source file ! \& until the next entry. ! .Ve ! .Sp ! Here is a sample when \fB\-i\fR is used in conjunction with \fB\-b\fR option: ! .Sp ! .Vb 9 ! \& file:array.cc ! \& function:11,1,_Z3sumRKSt6vectorIPiSaIS0_EE ! \& function:22,1,main ! \& lcount:11,1 ! \& lcount:12,1 ! \& lcount:14,1 ! \& branch:14,taken ! \& lcount:26,1 ! \& branch:28,nottaken ! .Ve ! .IP "\fB\-m\fR" 4 ! .IX Item "-m" .PD 0 ! .IP "\fB\-\-demangled\-names\fR" 4 ! .IX Item "--demangled-names" .PD ! Display demangled function names in output. The default is to show ! mangled function names. .PP \&\fBgcov\fR should be run with the current directory the same as that when you invoked the compiler. Otherwise it will not be able to locate --- 391,424 ---- .PD When branch probabilities are given, include those of unconditional branches. Unconditional branches are normally not interesting. ! .IP "\fB\-v\fR" 4 ! .IX Item "-v" .PD 0 ! .IP "\fB\-\-version\fR" 4 ! .IX Item "--version" .PD ! Display the \fBgcov\fR version number (on the standard output), ! and exit without doing any further processing. ! .IP "\fB\-w\fR" 4 ! .IX Item "-w" .PD 0 ! .IP "\fB\-\-verbose\fR" 4 ! .IX Item "--verbose" .PD ! Print verbose informations related to basic blocks and arcs. ! .IP "\fB\-x\fR" 4 ! .IX Item "-x" .PD 0 ! .IP "\fB\-\-hash\-filenames\fR" 4 ! .IX Item "--hash-filenames" .PD ! By default, gcov uses the full pathname of the source files to to create ! an output filename. This can lead to long filenames that can overflow ! filesystem limits. This option creates names of the form ! \&\fI\fIsource-file\fI##\fImd5\fI.gcov\fR, ! where the \fIsource-file\fR component is the final filename part and ! the \fImd5\fR component is calculated from the full mangled name that ! would have been used otherwise. .PP \&\fBgcov\fR should be run with the current directory the same as that when you invoked the compiler. Otherwise it will not be able to locate *************** command line option. The \fIexecution_c *** 424,430 **** containing no code. Unexecuted lines are marked \fB#####\fR or \&\fB====\fR, depending on whether they are reachable by non-exceptional paths or only exceptional paths such as \*(C+ exception ! handlers, respectively. .PP Some lines of information at the start have \fIline_number\fR of zero. These preamble lines are of the form --- 448,456 ---- containing no code. Unexecuted lines are marked \fB#####\fR or \&\fB====\fR, depending on whether they are reachable by non-exceptional paths or only exceptional paths such as \*(C+ exception ! handlers, respectively. Given \fB\-a\fR option, unexecuted blocks are ! marked \fB$$$$$\fR or \fB%%%%%\fR, depending on whether a basic block ! is reachable via non-exceptional or exceptional paths. .PP Some lines of information at the start have \fIline_number\fR of zero. These preamble lines are of the form *************** collected at that point to be dumped to *** 704,710 **** \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf\-funding\fR\|(7), \fIgcc\fR\|(1) and the Info entry for \fIgcc\fR. .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1996\-2016 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or --- 730,736 ---- \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf\-funding\fR\|(7), \fIgcc\fR\|(1) and the Info entry for \fIgcc\fR. .SH "COPYRIGHT" .IX Header "COPYRIGHT" ! Copyright (c) 1996\-2017 Free Software Foundation, Inc. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or diff -Nrcpad gcc-6.3.0/gcc/doc/gcov.texi gcc-6.4.0/gcc/doc/gcov.texi *** gcc-6.3.0/gcc/doc/gcov.texi Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/doc/gcov.texi Tue Jul 4 07:15:57 2017 *************** *** 4,10 **** @ignore @c man begin COPYRIGHT ! Copyright @copyright{} 1996-2016 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 --- 4,10 ---- @ignore @c man begin COPYRIGHT ! Copyright @copyright{} 1996-2017 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 *************** gpl(7), gfdl(7), fsf-funding(7), gcc(1) *** 142,156 **** @c man begin OPTIONS @table @gcctabopt - @item -h - @itemx --help - Display help about using @command{gcov} (on the standard output), and - exit without doing any further processing. - - @item -v - @itemx --version - Display the @command{gcov} version number (on the standard output), - and exit without doing any further processing. @item -a @itemx --all-blocks --- 142,147 ---- *************** be shown, unless the @option{-u} option *** 171,238 **** Write branch frequencies as the number of branches taken, rather than the percentage of branches taken. ! @item -n ! @itemx --no-output ! Do not create the @command{gcov} output file. ! ! @item -l ! @itemx --long-file-names ! Create long file names for included source files. For example, if the ! header file @file{x.h} contains code, and was included in the file ! @file{a.c}, then running @command{gcov} on the file @file{a.c} will ! produce an output file called @file{a.c##x.h.gcov} instead of ! @file{x.h.gcov}. This can be useful if @file{x.h} is included in ! multiple source files and you want to see the individual ! contributions. If you use the @samp{-p} option, both the including ! and included file names will be complete path names. ! ! @item -p ! @itemx --preserve-paths ! Preserve complete path information in the names of generated ! @file{.gcov} files. Without this option, just the filename component is ! used. With this option, all directories are used, with @samp{/} characters ! translated to @samp{#} characters, @file{.} directory components ! removed and unremoveable @file{..} ! components renamed to @samp{^}. This is useful if sourcefiles are in several ! different directories. ! ! @item -r ! @itemx --relative-only ! Only output information about source files with a relative pathname ! (after source prefix elision). Absolute paths are usually system ! header files and coverage of any inline functions therein is normally ! uninteresting. @item -f @itemx --function-summaries Output summaries for each function in addition to the file level summary. ! @item -o @var{directory|file} ! @itemx --object-directory @var{directory} ! @itemx --object-file @var{file} ! Specify either the directory containing the gcov data files, or the ! object path name. The @file{.gcno}, and ! @file{.gcda} data files are searched for using this option. If a directory ! is specified, the data files are in that directory and named after the ! input file name, without its extension. If a file is specified here, ! the data files are named after that file, without its extension. ! ! @item -s @var{directory} ! @itemx --source-prefix @var{directory} ! A prefix for source file names to remove when generating the output ! coverage files. This option is useful when building in a separate ! directory, and the pathname to the source directory is not wanted when ! determining the output file names. Note that this prefix detection is ! applied before determining whether the source file is absolute. ! ! @item -u ! @itemx --unconditional-branches ! When branch probabilities are given, include those of unconditional branches. ! Unconditional branches are normally not interesting. ! ! @item -d ! @itemx --display-progress ! Display the progress on the standard output. @item -i @itemx --intermediate-format --- 162,179 ---- Write branch frequencies as the number of branches taken, rather than the percentage of branches taken. ! @item -d ! @itemx --display-progress ! Display the progress on the standard output. @item -f @itemx --function-summaries Output summaries for each function in addition to the file level summary. ! @item -h ! @itemx --help ! Display help about using @command{gcov} (on the standard output), and ! exit without doing any further processing. @item -i @itemx --intermediate-format *************** lcount:26,1 *** 273,283 **** --- 214,298 ---- branch:28,nottaken @end smallexample + @item -l + @itemx --long-file-names + Create long file names for included source files. For example, if the + header file @file{x.h} contains code, and was included in the file + @file{a.c}, then running @command{gcov} on the file @file{a.c} will + produce an output file called @file{a.c##x.h.gcov} instead of + @file{x.h.gcov}. This can be useful if @file{x.h} is included in + multiple source files and you want to see the individual + contributions. If you use the @samp{-p} option, both the including + and included file names will be complete path names. + @item -m @itemx --demangled-names Display demangled function names in output. The default is to show mangled function names. + @item -n + @itemx --no-output + Do not create the @command{gcov} output file. + + @item -o @var{directory|file} + @itemx --object-directory @var{directory} + @itemx --object-file @var{file} + Specify either the directory containing the gcov data files, or the + object path name. The @file{.gcno}, and + @file{.gcda} data files are searched for using this option. If a directory + is specified, the data files are in that directory and named after the + input file name, without its extension. If a file is specified here, + the data files are named after that file, without its extension. + + @item -p + @itemx --preserve-paths + Preserve complete path information in the names of generated + @file{.gcov} files. Without this option, just the filename component is + used. With this option, all directories are used, with @samp{/} characters + translated to @samp{#} characters, @file{.} directory components + removed and unremoveable @file{..} + components renamed to @samp{^}. This is useful if sourcefiles are in several + different directories. + + @item -r + @itemx --relative-only + Only output information about source files with a relative pathname + (after source prefix elision). Absolute paths are usually system + header files and coverage of any inline functions therein is normally + uninteresting. + + @item -s @var{directory} + @itemx --source-prefix @var{directory} + A prefix for source file names to remove when generating the output + coverage files. This option is useful when building in a separate + directory, and the pathname to the source directory is not wanted when + determining the output file names. Note that this prefix detection is + applied before determining whether the source file is absolute. + + @item -u + @itemx --unconditional-branches + When branch probabilities are given, include those of unconditional branches. + Unconditional branches are normally not interesting. + + @item -v + @itemx --version + Display the @command{gcov} version number (on the standard output), + and exit without doing any further processing. + + @item -w + @itemx --verbose + Print verbose informations related to basic blocks and arcs. + + @item -x + @itemx --hash-filenames + By default, gcov uses the full pathname of the source files to to create + an output filename. This can lead to long filenames that can overflow + filesystem limits. This option creates names of the form + @file{@var{source-file}##@var{md5}.gcov}, + where the @var{source-file} component is the final filename part and + the @var{md5} component is calculated from the full mangled name that + would have been used otherwise. + @end table @command{gcov} should be run with the current directory the same as that *************** command line option. The @var{execution *** 308,314 **** containing no code. Unexecuted lines are marked @samp{#####} or @samp{====}, depending on whether they are reachable by non-exceptional paths or only exceptional paths such as C++ exception ! handlers, respectively. Some lines of information at the start have @var{line_number} of zero. These preamble lines are of the form --- 323,331 ---- containing no code. Unexecuted lines are marked @samp{#####} or @samp{====}, depending on whether they are reachable by non-exceptional paths or only exceptional paths such as C++ exception ! handlers, respectively. Given @samp{-a} option, unexecuted blocks are ! marked @samp{$$$$$} or @samp{%%%%%}, depending on whether a basic block ! is reachable via non-exceptional or exceptional paths. Some lines of information at the start have @var{line_number} of zero. These preamble lines are of the form *************** it. This can be overcome by, for exampl *** 653,657 **** setting will name the data file @file{/target/run/build/foo.gcda}. You must move the data files to the expected directory tree in order to ! use them for profile directed optimizations (@option{--use-profile}), or to use the @command{gcov} tool. --- 670,674 ---- setting will name the data file @file{/target/run/build/foo.gcda}. You must move the data files to the expected directory tree in order to ! use them for profile directed optimizations (@option{-fprofile-use}), or to use the @command{gcov} tool. diff -Nrcpad gcc-6.3.0/gcc/doc/generic.texi gcc-6.4.0/gcc/doc/generic.texi *** gcc-6.3.0/gcc/doc/generic.texi Thu Jan 28 15:45:44 2016 --- gcc-6.4.0/gcc/doc/generic.texi Sat Jan 21 22:02:25 2017 *************** This tree has one field that holds the n *** 3241,3247 **** @end smallexample Detailed description for usage and functionality of @code{_Cilk_spawn} can be ! found at http://www.cilkplus.org @item CILK_SYNC_STMT --- 3241,3247 ---- @end smallexample Detailed description for usage and functionality of @code{_Cilk_spawn} can be ! found at @uref{https://www.cilkplus.org}. @item CILK_SYNC_STMT diff -Nrcpad gcc-6.3.0/gcc/doc/gfdl.7 gcc-6.4.0/gcc/doc/gfdl.7 *** gcc-6.3.0/gcc/doc/gfdl.7 Wed Dec 21 08:06:54 2016 --- gcc-6.4.0/gcc/doc/gfdl.7 Tue Jul 4 07:37:47 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GFDL 7" ! .TH GFDL 7 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GFDL 7" ! .TH GFDL 7 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** format, \s-1SGML\s0 or \s-1XML\s0 using *** 239,245 **** \&\s-1DTD,\s0 and standard-conforming simple \s-1HTML,\s0 PostScript or \s-1PDF\s0 designed for human modification. Examples of transparent image formats include \s-1PNG, XCF\s0 and ! \&\s-1JPG.\s0 Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, \s-1SGML\s0 or \&\s-1XML\s0 for which the \s-1DTD\s0 and/or processing tools are not generally available, and the machine-generated \s-1HTML,\s0 --- 243,249 ---- \&\s-1DTD,\s0 and standard-conforming simple \s-1HTML,\s0 PostScript or \s-1PDF\s0 designed for human modification. Examples of transparent image formats include \s-1PNG, XCF\s0 and ! \&\s-1JPG. \s0 Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, \s-1SGML\s0 or \&\s-1XML\s0 for which the \s-1DTD\s0 and/or processing tools are not generally available, and the machine-generated \s-1HTML,\s0 *************** in part, as part of another Document. *** 596,602 **** An \s-1MMC\s0 is \*(L"eligible for relicensing\*(R" if it is licensed under this License, and if all works that were first published under this License somewhere other than this \s-1MMC,\s0 and subsequently incorporated in whole ! or in part into the \s-1MMC,\s0 (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008. .Sp The operator of an \s-1MMC\s0 Site may republish an \s-1MMC\s0 contained in the site --- 600,606 ---- An \s-1MMC\s0 is \*(L"eligible for relicensing\*(R" if it is licensed under this License, and if all works that were first published under this License somewhere other than this \s-1MMC,\s0 and subsequently incorporated in whole ! or in part into the \s-1MMC, \\fIs0\fR\|(1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008. .Sp The operator of an \s-1MMC\s0 Site may republish an \s-1MMC\s0 contained in the site diff -Nrcpad gcc-6.3.0/gcc/doc/gfortran.1 gcc-6.4.0/gcc/doc/gfortran.1 *** gcc-6.3.0/gcc/doc/gfortran.1 Wed Dec 21 09:34:12 2016 --- gcc-6.4.0/gcc/doc/gfortran.1 Tue Jul 4 09:27:49 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GFORTRAN 1" ! .TH GFORTRAN 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GFORTRAN 1" ! .TH GFORTRAN 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** Other flags enabled by this switch are: *** 276,282 **** \&\fB\-fdollar\-ok\fR \fB\-fcray\-pointer\fR \fB\-fdec\-structure\fR .IP "\fB\-fdec\-structure\fR" 4 .IX Item "-fdec-structure" ! Enable \s-1DEC\s0 \f(CW\*(C`STRUCTURE\*(C'\fR and \f(CW\*(C`RECORD\*(C'\fR as well as \f(CW\*(C`UNION\*(C'\fR, \&\f(CW\*(C`MAP\*(C'\fR, and dot ('.') as a member separator (in addition to '%'). This is provided for compatibility only; Fortran 90 derived types should be used instead where possible. --- 280,286 ---- \&\fB\-fdollar\-ok\fR \fB\-fcray\-pointer\fR \fB\-fdec\-structure\fR .IP "\fB\-fdec\-structure\fR" 4 .IX Item "-fdec-structure" ! Enable \s-1DEC \s0\f(CW\*(C`STRUCTURE\*(C'\fR and \f(CW\*(C`RECORD\*(C'\fR as well as \f(CW\*(C`UNION\*(C'\fR, \&\f(CW\*(C`MAP\*(C'\fR, and dot ('.') as a member separator (in addition to '%'). This is provided for compatibility only; Fortran 90 derived types should be used instead where possible. *************** compilation sentinels in free form and \ *** 348,354 **** OpenACC runtime library to be linked in. .Sp Note that this is an experimental feature, incomplete, and subject to ! change in future versions of \s-1GCC.\s0 See <\fBhttps://gcc.gnu.org/wiki/OpenACC\fR> for more information. .IP "\fB\-fopenmp\fR" 4 .IX Item "-fopenmp" --- 352,358 ---- OpenACC runtime library to be linked in. .Sp Note that this is an experimental feature, incomplete, and subject to ! change in future versions of \s-1GCC. \s0 See <\fBhttps://gcc.gnu.org/wiki/OpenACC\fR> for more information. .IP "\fB\-fopenmp\fR" 4 .IX Item "-fopenmp" diff -Nrcpad gcc-6.3.0/gcc/doc/gij.1 gcc-6.4.0/gcc/doc/gij.1 *** gcc-6.3.0/gcc/doc/gij.1 Wed Dec 21 09:16:01 2016 --- gcc-6.4.0/gcc/doc/gij.1 Tue Jul 4 09:07:59 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GIJ 1" ! .TH GIJ 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GIJ 1" ! .TH GIJ 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/gpl.7 gcc-6.4.0/gcc/doc/gpl.7 *** gcc-6.3.0/gcc/doc/gpl.7 Wed Dec 21 08:06:54 2016 --- gcc-6.4.0/gcc/doc/gpl.7 Tue Jul 4 07:37:47 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GPL 7" ! .TH GPL 7 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GPL 7" ! .TH GPL 7 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** later version. *** 748,759 **** .IP "15. Disclaimer of Warranty." 4 .IX Item "15. Disclaimer of Warranty." \&\s-1THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW.\s0 \s-1EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \*(L"AS IS\*(R" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR ! A PARTICULAR PURPOSE.\s0 \s-1THE ENTIRE RISK AS TO THE QUALITY AND ! PERFORMANCE OF THE PROGRAM IS WITH YOU.\s0 \s-1SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.\s0 .IP "16. Limitation of Liability." 4 --- 752,763 ---- .IP "15. Disclaimer of Warranty." 4 .IX Item "15. Disclaimer of Warranty." \&\s-1THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \*(L"AS IS\*(R" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR ! A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND ! PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.\s0 .IP "16. Limitation of Liability." 4 *************** CORRECTION.\s0 *** 762,768 **** WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ! ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM\s0 (\s-1INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS\s0), \s-1EVEN IF SUCH HOLDER OR OTHER --- 766,772 ---- WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ! ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM \s0(\s-1INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS\s0), \s-1EVEN IF SUCH HOLDER OR OTHER diff -Nrcpad gcc-6.3.0/gcc/doc/grmic.1 gcc-6.4.0/gcc/doc/grmic.1 *** gcc-6.3.0/gcc/doc/grmic.1 Wed Dec 21 09:16:01 2016 --- gcc-6.4.0/gcc/doc/grmic.1 Tue Jul 4 09:08:00 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "GRMIC 1" ! .TH GRMIC 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "GRMIC 1" ! .TH GRMIC 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l *************** grmic \- Generate stubs for Remote Metho *** 144,151 **** \&\fBgrmic\fR is a utility included with \f(CW\*(C`libgcj\*(C'\fR which generates stubs for remote objects. .PP ! Note that this program isn't yet fully compatible with the \s-1JDK\s0 ! \&\fBgrmic\fR. Some options, such as \fB\-classpath\fR, are recognized but currently ignored. We have left these options undocumented for now. .PP --- 148,155 ---- \&\fBgrmic\fR is a utility included with \f(CW\*(C`libgcj\*(C'\fR which generates stubs for remote objects. .PP ! Note that this program isn't yet fully compatible with the \s-1JDK ! \&\s0\fBgrmic\fR. Some options, such as \fB\-classpath\fR, are recognized but currently ignored. We have left these options undocumented for now. .PP diff -Nrcpad gcc-6.3.0/gcc/doc/install.texi gcc-6.4.0/gcc/doc/install.texi *** gcc-6.3.0/gcc/doc/install.texi Tue Nov 15 11:10:05 2016 --- gcc-6.4.0/gcc/doc/install.texi Tue Jul 4 07:15:57 2017 *************** *** 69,75 **** @c Part 2 Summary Description and Copyright @copying ! Copyright @copyright{} 1988-2016 Free Software Foundation, Inc. @sp 1 Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or --- 69,75 ---- @c Part 2 Summary Description and Copyright @copying ! Copyright @copyright{} 1988-2017 Free Software Foundation, Inc. @sp 1 Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or *************** and for cross builds configured with @op *** 1063,1068 **** --- 1063,1073 ---- More documentation about multiarch can be found at @uref{https://wiki.debian.org/Multiarch}. + @item --enable-sjlj-exceptions + Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions. + @samp{configure} ordinarily picks the correct value based on the platform. + Only use this option if you are sure you need a different setting. + @item --enable-vtable-verify Specify whether to enable or disable the vtable verification feature. Enabling this feature causes libstdc++ to be built with its virtual calls *************** file to compile into a @file{.class} fil *** 2279,2289 **** @item --with-libiconv-prefix=DIR Search for libiconv in @file{DIR/include} and @file{DIR/lib}. - @item --enable-sjlj-exceptions - Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions. - @samp{configure} ordinarily picks the correct value based on the platform. - Only use this option if you are sure you need a different setting. - @item --with-system-zlib Use installed @samp{zlib} rather than that included with GCC@. --- 2284,2289 ---- diff -Nrcpad gcc-6.3.0/gcc/doc/invoke.texi gcc-6.4.0/gcc/doc/invoke.texi *** gcc-6.3.0/gcc/doc/invoke.texi Fri Jul 8 14:51:44 2016 --- gcc-6.4.0/gcc/doc/invoke.texi Tue Jul 4 07:15:57 2017 *************** *** 8,14 **** @c man end @c man begin COPYRIGHT ! Copyright @copyright{} 1988-2016 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 --- 8,14 ---- @c man end @c man begin COPYRIGHT ! Copyright @copyright{} 1988-2017 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 *************** Objective-C and Objective-C++ Dialects}. *** 256,262 **** -Wno-attributes -Wbool-compare -Wno-builtin-macro-redefined @gol -Wc90-c99-compat -Wc99-c11-compat @gol -Wc++-compat -Wc++11-compat -Wc++14-compat -Wcast-align -Wcast-qual @gol ! -Wchar-subscripts -Wclobbered -Wcomment -Wconditionally-supported @gol -Wconversion -Wcoverage-mismatch -Wno-cpp -Wdate-time -Wdelete-incomplete @gol -Wno-deprecated -Wno-deprecated-declarations -Wno-designated-init @gol -Wdisabled-optimization @gol --- 256,262 ---- -Wno-attributes -Wbool-compare -Wno-builtin-macro-redefined @gol -Wc90-c99-compat -Wc99-c11-compat @gol -Wc++-compat -Wc++11-compat -Wc++14-compat -Wcast-align -Wcast-qual @gol ! -Wchar-subscripts -Wchkp -Wclobbered -Wcomment -Wconditionally-supported @gol -Wconversion -Wcoverage-mismatch -Wno-cpp -Wdate-time -Wdelete-incomplete @gol -Wno-deprecated -Wno-deprecated-declarations -Wno-designated-init @gol -Wdisabled-optimization @gol *************** See RS/6000 and PowerPC Options. *** 1001,1010 **** -mquad-memory-atomic -mno-quad-memory-atomic @gol -mcompat-align-parm -mno-compat-align-parm @gol -mupper-regs-df -mno-upper-regs-df -mupper-regs-sf -mno-upper-regs-sf @gol ! -mupper-regs -mno-upper-regs -mmodulo -mno-modulo @gol -mfloat128 -mno-float128 -mfloat128-hardware -mno-float128-hardware @gol ! -mpower9-fusion -mno-mpower9-fusion -mpower9-vector -mno-power9-vector @gol ! -mpower9-dform -mno-power9-dform -mlra -mno-lra} @emph{RX Options} @gccoptlist{-m64bit-doubles -m32bit-doubles -fpu -nofpu@gol --- 1001,1009 ---- -mquad-memory-atomic -mno-quad-memory-atomic @gol -mcompat-align-parm -mno-compat-align-parm @gol -mupper-regs-df -mno-upper-regs-df -mupper-regs-sf -mno-upper-regs-sf @gol ! -mupper-regs -mno-upper-regs @gol -mfloat128 -mno-float128 -mfloat128-hardware -mno-float128-hardware @gol ! -mlra -mno-lra} @emph{RX Options} @gccoptlist{-m64bit-doubles -m32bit-doubles -fpu -nofpu@gol *************** Warn whenever a comment-start sequence @ *** 3651,3656 **** --- 3650,3660 ---- comment, or whenever a Backslash-Newline appears in a @samp{//} comment. This warning is enabled by @option{-Wall}. + @item -Wchkp + @opindex Wchkp + Warn about an invalid memory access that is found by Pointer Bounds Checker + (@option{-fcheck-pointer-bounds}). + @item -Wno-coverage-mismatch @opindex Wno-coverage-mismatch Warn if feedback profiles do not match when using the *************** following options: *** 19880,19887 **** -mpowerpc-gpopt -mpowerpc-gfxopt -msingle-float -mdouble-float @gol -msimple-fpu -mstring -mmulhw -mdlmzb -mmfpgpr -mvsx @gol -mcrypto -mdirect-move -mhtm -mpower8-fusion -mpower8-vector @gol ! -mquad-memory -mquad-memory-atomic -mmodulo -mfloat128 -mfloat128-hardware @gol ! -mpower9-fusion -mpower9-vector -mpower9-dform} The particular options set for any particular CPU varies between compiler versions, depending on what setting seems to produce optimal --- 19884,19890 ---- -mpowerpc-gpopt -mpowerpc-gfxopt -msingle-float -mdouble-float @gol -msimple-fpu -mstring -mmulhw -mdlmzb -mmfpgpr -mvsx @gol -mcrypto -mdirect-move -mhtm -mpower8-fusion -mpower8-vector @gol ! -mquad-memory -mquad-memory-atomic -mfloat128 -mfloat128-hardware} The particular options set for any particular CPU varies between compiler versions, depending on what setting seems to produce optimal *************** Generate code that uses (does not use) t *** 20113,20120 **** instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the PowerPC ISA. @option{-mupper-regs-sf} is turned on by default if you ! use either of the @option{-mcpu=power8} or @option{-mpower8-vector} ! options. @item -mupper-regs @itemx -mno-upper-regs --- 20116,20123 ---- instructions that target all 64 registers in the vector/scalar floating point register set that were added in version 2.07 of the PowerPC ISA. @option{-mupper-regs-sf} is turned on by default if you ! use either of the @option{-mcpu=power8}, @option{-mpower8-vector}, or ! @option{-mcpu=power9} options. @item -mupper-regs @itemx -mno-upper-regs *************** If you select ISA 3.0 instructions with *** 20159,20198 **** not use either @option{-mfloat128} or @option{-mfloat128-hardware}, the IEEE 128-bit floating point support will not be enabled. - @item -mmodulo - @itemx -mno-modulo - @opindex mmodulo - @opindex mno-module - Generate code that uses (does not use) the ISA 3.0 integer modulo - instructions. The @option{-mmodulo} option is enabled by default - with the @option{-mcpu=power9} option. - - @item -mpower9-fusion - @itemx -mno-power9-fusion - @opindex mpower9-fusion - @opindex mno-power9-fusion - Generate code that keeps (does not keeps) some operations adjacent so - that the instructions can be fused together on power9 and later - processors. - - @item -mpower9-vector - @itemx -mno-power9-vector - @opindex mpower9-vector - @opindex mno-power9-vector - Generate code that uses (does not use) the vector and scalar - instructions that were added in version 3.0 of the PowerPC ISA. Also - enable the use of built-in functions that allow more direct access to - the vector instructions. - - @item -mpower9-dform - @itemx -mno-power9-dform - @opindex mpower9-dform - @opindex mno-power9-dform - Enable (disable) scalar d-form (register + offset) memory instructions - to load/store traditional Altivec registers. If the @var{LRA} register - allocator is enabled, also enable (disable) vector d-form memory - instructions. - @item -mfloat-gprs=@var{yes/single/double/no} @itemx -mfloat-gprs @opindex mfloat-gprs --- 20162,20167 ---- diff -Nrcpad gcc-6.3.0/gcc/doc/jcf-dump.1 gcc-6.4.0/gcc/doc/jcf-dump.1 *** gcc-6.3.0/gcc/doc/jcf-dump.1 Wed Dec 21 09:16:01 2016 --- gcc-6.4.0/gcc/doc/jcf-dump.1 Tue Jul 4 09:07:59 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "JCF-DUMP 1" ! .TH JCF-DUMP 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "JCF-DUMP 1" ! .TH JCF-DUMP 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/jv-convert.1 gcc-6.4.0/gcc/doc/jv-convert.1 *** gcc-6.3.0/gcc/doc/jv-convert.1 Wed Dec 21 09:16:01 2016 --- gcc-6.4.0/gcc/doc/jv-convert.1 Tue Jul 4 09:08:00 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "JV-CONVERT 1" ! .TH JV-CONVERT 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "JV-CONVERT 1" ! .TH JV-CONVERT 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/lto.texi gcc-6.4.0/gcc/doc/lto.texi *** gcc-6.3.0/gcc/doc/lto.texi Tue Jan 19 21:49:32 2016 --- gcc-6.4.0/gcc/doc/lto.texi Fri May 26 11:31:33 2017 *************** existing build systems, as one can, for *** 43,49 **** the files. Additionally, one might be able to ship one set of fat objects which could be used both for development and the production of optimized builds. A, perhaps surprising, side effect of this feature ! is that any mistake in the toolchain that leads to LTO information not being used (e.g.@: an older @code{libtool} calling @code{ld} directly). This is both an advantage, as the system is more robust, and a disadvantage, as the user is not informed that the optimization has --- 43,49 ---- the files. Additionally, one might be able to ship one set of fat objects which could be used both for development and the production of optimized builds. A, perhaps surprising, side effect of this feature ! is that any mistake in the toolchain leads to LTO information not being used (e.g.@: an older @code{libtool} calling @code{ld} directly). This is both an advantage, as the system is more robust, and a disadvantage, as the user is not informed that the optimization has diff -Nrcpad gcc-6.3.0/gcc/doc/md.texi gcc-6.4.0/gcc/doc/md.texi *** gcc-6.3.0/gcc/doc/md.texi Thu Jun 9 23:28:23 2016 --- gcc-6.4.0/gcc/doc/md.texi Wed Mar 29 23:15:51 2017 *************** asm ("xsaddqp %x0,%x1,%x2" : "=v" (v1) : *** 3139,3151 **** is incorrect. @item wb ! Altivec register if @option{-mpower9-dform} is used or NO_REGS. @item wd VSX vector register to hold vector double data or NO_REGS. @item we ! VSX register if the @option{-mpower9-vector} and @option{-m64} options were used or NO_REGS. @item wf --- 3139,3151 ---- is incorrect. @item wb ! Altivec register if @option{-mcpu=power9} is used or NO_REGS. @item wd VSX vector register to hold vector double data or NO_REGS. @item we ! VSX register if the @option{-mcpu=power9} and @option{-m64} options were used or NO_REGS. @item wf *************** FP or VSX register to perform ISA 2.07 f *** 3211,3216 **** --- 3211,3219 ---- @item wz Floating point register if the LFIWZX instruction is enabled or NO_REGS. + @item wA + Address base register if 64-bit instructions are enabled or NO_REGS. + @item wD Int constant that is the element number of the 64-bit scalar in a vector. diff -Nrcpad gcc-6.3.0/gcc/doc/passes.texi gcc-6.4.0/gcc/doc/passes.texi *** gcc-6.3.0/gcc/doc/passes.texi Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/doc/passes.texi Sat Jan 21 22:02:25 2017 *************** done by @code{builtin_expand_cilk_pop_fr *** 163,169 **** @end itemize Documentation about Cilk Plus and language specification is provided under the ! "Learn" section in @w{@uref{http://www.cilkplus.org/}}. It is worth mentioning that the current implementation follows ABI 1.1. @node Gimplification pass --- 163,169 ---- @end itemize Documentation about Cilk Plus and language specification is provided under the ! "Learn" section in @w{@uref{https://www.cilkplus.org}}. It is worth mentioning that the current implementation follows ABI 1.1. @node Gimplification pass diff -Nrcpad gcc-6.3.0/gcc/doc/rebuild-gcj-db.1 gcc-6.4.0/gcc/doc/rebuild-gcj-db.1 *** gcc-6.3.0/gcc/doc/rebuild-gcj-db.1 Wed Dec 21 09:34:12 2016 --- gcc-6.4.0/gcc/doc/rebuild-gcj-db.1 Tue Jul 4 09:27:49 2017 *************** *** 1,4 **** ! .\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== --- 1,4 ---- ! .\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== *************** *** 46,52 **** .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. --- 46,52 ---- .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ! .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. *************** *** 54,69 **** .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .if !\nF .nr F 0 ! .if \nF>0 \{\ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{\ ! . nr % 0 ! . nr F 2 . \} .\} .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. --- 54,73 ---- .\" Avoid warning from groff about undefined register 'F'. .de IX .. ! .nr rF 0 ! .if \n(.g .if rF .nr rF 1 ! .if (\n(rF:(\n(.g==0)) \{ ! . if \nF \{ ! . de IX ! . tm Index:\\$1\t\\n%\t"\\$2" .. ! . if !\nF==2 \{ ! . nr % 0 ! . nr F 2 ! . \} . \} .\} + .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. *************** *** 129,135 **** .\" ======================================================================== .\" .IX Title "REBUILD-GCJ-DB 1" ! .TH REBUILD-GCJ-DB 1 "2016-12-21" "gcc-6.3.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l --- 133,139 ---- .\" ======================================================================== .\" .IX Title "REBUILD-GCJ-DB 1" ! .TH REBUILD-GCJ-DB 1 "2017-07-04" "gcc-6.4.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -Nrcpad gcc-6.3.0/gcc/doc/sourcebuild.texi gcc-6.4.0/gcc/doc/sourcebuild.texi *** gcc-6.3.0/gcc/doc/sourcebuild.texi Fri Feb 19 14:20:27 2016 --- gcc-6.4.0/gcc/doc/sourcebuild.texi Tue Jun 6 11:50:48 2017 *************** Target supports @option{-mpe-aligned-com *** 1950,1955 **** --- 1950,1958 ---- @item pie Target supports @option{-pie}, @option{-fpie} and @option{-fPIE}. + @item rdynamic + Target supports @option{-rdynamic}. + @item section_anchors Target supports section anchors. diff -Nrcpad gcc-6.3.0/gcc/doc/tm.texi gcc-6.4.0/gcc/doc/tm.texi *** gcc-6.3.0/gcc/doc/tm.texi Wed Mar 2 21:46:55 2016 --- gcc-6.4.0/gcc/doc/tm.texi Thu Jun 22 07:22:13 2017 *************** misalignment value (@var{misalign}). *** 5650,5656 **** @end deftypefn @deftypefn {Target Hook} bool TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE (const_tree @var{type}, bool @var{is_packed}) ! Return true if vector alignment is reachable (by peeling N iterations) for the given type. @end deftypefn @deftypefn {Target Hook} bool TARGET_VECTORIZE_VEC_PERM_CONST_OK (machine_mode, const unsigned char *@var{sel}) --- 5650,5656 ---- @end deftypefn @deftypefn {Target Hook} bool TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE (const_tree @var{type}, bool @var{is_packed}) ! Return true if vector alignment is reachable (by peeling N iterations) for the given scalar type @var{type}. @var{is_packed} is false if the scalar access using @var{type} is known to be naturally aligned. @end deftypefn @deftypefn {Target Hook} bool TARGET_VECTORIZE_VEC_PERM_CONST_OK (machine_mode, const unsigned char *@var{sel}) diff -Nrcpad gcc-6.3.0/gcc/dwarf2out.c gcc-6.4.0/gcc/dwarf2out.c *** gcc-6.3.0/gcc/dwarf2out.c Thu Sep 1 11:43:15 2016 --- gcc-6.4.0/gcc/dwarf2out.c Fri May 5 21:50:27 2017 *************** static dw_loc_descr_ref *** 16615,16624 **** field_byte_offset (const_tree decl, struct vlr_context *ctx, HOST_WIDE_INT *cst_offset) { - offset_int object_offset_in_bits; - offset_int object_offset_in_bytes; - offset_int bitpos_int; - bool is_byte_offset_cst, is_bit_offset_cst; tree tree_result; dw_loc_list_ref loc_result; --- 16615,16620 ---- *************** field_byte_offset (const_tree decl, stru *** 16629,16648 **** else gcc_assert (TREE_CODE (decl) == FIELD_DECL); - is_bit_offset_cst = TREE_CODE (DECL_FIELD_BIT_OFFSET (decl)) != INTEGER_CST; - is_byte_offset_cst = TREE_CODE (DECL_FIELD_OFFSET (decl)) != INTEGER_CST; - /* We cannot handle variable bit offsets at the moment, so abort if it's the case. */ ! if (is_bit_offset_cst) return NULL; #ifdef PCC_BITFIELD_TYPE_MATTERS /* We used to handle only constant offsets in all cases. Now, we handle properly dynamic byte offsets only when PCC bitfield type doesn't matter. */ ! if (PCC_BITFIELD_TYPE_MATTERS && is_byte_offset_cst && is_bit_offset_cst) { tree type; tree field_size_tree; offset_int deepest_bitpos; --- 16625,16645 ---- else gcc_assert (TREE_CODE (decl) == FIELD_DECL); /* We cannot handle variable bit offsets at the moment, so abort if it's the case. */ ! if (TREE_CODE (DECL_FIELD_BIT_OFFSET (decl)) != INTEGER_CST) return NULL; #ifdef PCC_BITFIELD_TYPE_MATTERS /* We used to handle only constant offsets in all cases. Now, we handle properly dynamic byte offsets only when PCC bitfield type doesn't matter. */ ! if (PCC_BITFIELD_TYPE_MATTERS ! && TREE_CODE (DECL_FIELD_OFFSET (decl)) == INTEGER_CST) { + offset_int object_offset_in_bits; + offset_int object_offset_in_bytes; + offset_int bitpos_int; tree type; tree field_size_tree; offset_int deepest_bitpos; *************** field_byte_offset (const_tree decl, stru *** 16737,16749 **** object_offset_in_bits = round_up_to_align (object_offset_in_bits, decl_align_in_bits); } } #endif /* PCC_BITFIELD_TYPE_MATTERS */ - tree_result = byte_position (decl); if (ctx->variant_part_offset != NULL_TREE) ! tree_result = fold (build2 (PLUS_EXPR, TREE_TYPE (tree_result), ! ctx->variant_part_offset, tree_result)); /* If the byte offset is a constant, it's simplier to handle a native constant rather than a DWARF expression. */ --- 16734,16756 ---- object_offset_in_bits = round_up_to_align (object_offset_in_bits, decl_align_in_bits); } + + object_offset_in_bytes + = wi::lrshift (object_offset_in_bits, LOG2_BITS_PER_UNIT); + if (ctx->variant_part_offset == NULL_TREE) + { + *cst_offset = object_offset_in_bytes.to_shwi (); + return NULL; + } + tree_result = wide_int_to_tree (sizetype, object_offset_in_bytes); } + else #endif /* PCC_BITFIELD_TYPE_MATTERS */ + tree_result = byte_position (decl); if (ctx->variant_part_offset != NULL_TREE) ! tree_result = fold_build2 (PLUS_EXPR, TREE_TYPE (tree_result), ! ctx->variant_part_offset, tree_result); /* If the byte offset is a constant, it's simplier to handle a native constant rather than a DWARF expression. */ *************** analyze_variants_discr (tree variant_par *** 22221,22234 **** if (!lower_cst_included) lower_cst ! = fold (build2 (PLUS_EXPR, TREE_TYPE (lower_cst), ! lower_cst, ! build_int_cst (TREE_TYPE (lower_cst), 1))); if (!upper_cst_included) upper_cst ! = fold (build2 (MINUS_EXPR, TREE_TYPE (upper_cst), ! upper_cst, ! build_int_cst (TREE_TYPE (upper_cst), 1))); if (!get_discr_value (lower_cst, &new_node->dw_discr_lower_bound) --- 22228,22239 ---- if (!lower_cst_included) lower_cst ! = fold_build2 (PLUS_EXPR, TREE_TYPE (lower_cst), lower_cst, ! build_int_cst (TREE_TYPE (lower_cst), 1)); if (!upper_cst_included) upper_cst ! = fold_build2 (MINUS_EXPR, TREE_TYPE (upper_cst), upper_cst, ! build_int_cst (TREE_TYPE (upper_cst), 1)); if (!get_discr_value (lower_cst, &new_node->dw_discr_lower_bound) *************** gen_variant_part (tree variant_part_decl *** 22397,22404 **** we recurse. */ vlr_sub_ctx.variant_part_offset ! = fold (build2 (PLUS_EXPR, TREE_TYPE (variant_part_offset), ! variant_part_offset, byte_position (member))); gen_variant_part (member, &vlr_sub_ctx, variant_die); } else --- 22402,22409 ---- we recurse. */ vlr_sub_ctx.variant_part_offset ! = fold_build2 (PLUS_EXPR, TREE_TYPE (variant_part_offset), ! variant_part_offset, byte_position (member)); gen_variant_part (member, &vlr_sub_ctx, variant_die); } else *************** decls_for_scope (tree stmt, dw_die_ref c *** 23151,23158 **** for (decl = BLOCK_VARS (stmt); decl != NULL; decl = DECL_CHAIN (decl)) process_scope_var (stmt, decl, NULL_TREE, context_die); for (i = 0; i < BLOCK_NUM_NONLOCALIZED_VARS (stmt); i++) ! process_scope_var (stmt, NULL, BLOCK_NONLOCALIZED_VAR (stmt, i), ! context_die); } /* Even if we're at -g1, we need to process the subblocks in order to get --- 23156,23173 ---- for (decl = BLOCK_VARS (stmt); decl != NULL; decl = DECL_CHAIN (decl)) process_scope_var (stmt, decl, NULL_TREE, context_die); for (i = 0; i < BLOCK_NUM_NONLOCALIZED_VARS (stmt); i++) ! { ! decl = BLOCK_NONLOCALIZED_VAR (stmt, i); ! if (decl == current_function_decl) ! /* Ignore declarations of the current function, while they ! are declarations, gen_subprogram_die would treat them ! as definitions again, because they are equal to ! current_function_decl and endlessly recurse. */; ! else if (TREE_CODE (decl) == FUNCTION_DECL) ! process_scope_var (stmt, decl, NULL_TREE, context_die); ! else ! process_scope_var (stmt, NULL_TREE, decl, context_die); ! } } /* Even if we're at -g1, we need to process the subblocks in order to get *************** dwarf2out_late_global_decl (tree decl) *** 23752,23758 **** { dw_die_ref die = lookup_decl_die (decl); if (die) ! add_location_or_const_value_attribute (die, decl, false); } } --- 23767,23782 ---- { dw_die_ref die = lookup_decl_die (decl); if (die) ! { ! /* We get called via the symtab code invoking late_global_decl ! for symbols that are optimized out. Do not add locations ! for those. */ ! varpool_node *node = varpool_node::get (decl); ! if (! node || ! node->definition) ! tree_add_const_value_attribute_for_decl (die, decl); ! else ! add_location_or_const_value_attribute (die, decl, false); ! } } } diff -Nrcpad gcc-6.3.0/gcc/expr.c gcc-6.4.0/gcc/expr.c *** gcc-6.3.0/gcc/expr.c Wed Dec 7 22:45:33 2016 --- gcc-6.4.0/gcc/expr.c Tue May 9 12:24:53 2017 *************** static tree clear_storage_libcall_fn (in *** 120,126 **** static rtx_insn *compress_float_constant (rtx, rtx); static rtx get_subtarget (rtx); static void store_constructor_field (rtx, unsigned HOST_WIDE_INT, ! HOST_WIDE_INT, machine_mode, tree, int, alias_set_type, bool); static void store_constructor (tree, rtx, int, HOST_WIDE_INT, bool); static rtx store_field (rtx, HOST_WIDE_INT, HOST_WIDE_INT, --- 120,127 ---- static rtx_insn *compress_float_constant (rtx, rtx); static rtx get_subtarget (rtx); static void store_constructor_field (rtx, unsigned HOST_WIDE_INT, ! HOST_WIDE_INT, unsigned HOST_WIDE_INT, ! unsigned HOST_WIDE_INT, machine_mode, tree, int, alias_set_type, bool); static void store_constructor (tree, rtx, int, HOST_WIDE_INT, bool); static rtx store_field (rtx, HOST_WIDE_INT, HOST_WIDE_INT, *************** optimize_bitfield_assignment_op (unsigne *** 4648,4654 **** If the access does not need to be restricted, 0 is returned in both *BITSTART and *BITEND. */ ! static void get_bit_range (unsigned HOST_WIDE_INT *bitstart, unsigned HOST_WIDE_INT *bitend, tree exp, --- 4649,4655 ---- If the access does not need to be restricted, 0 is returned in both *BITSTART and *BITEND. */ ! void get_bit_range (unsigned HOST_WIDE_INT *bitstart, unsigned HOST_WIDE_INT *bitend, tree exp, *************** all_zeros_p (const_tree exp) *** 5932,5938 **** static void store_constructor_field (rtx target, unsigned HOST_WIDE_INT bitsize, ! HOST_WIDE_INT bitpos, machine_mode mode, tree exp, int cleared, alias_set_type alias_set, bool reverse) { --- 5933,5942 ---- static void store_constructor_field (rtx target, unsigned HOST_WIDE_INT bitsize, ! HOST_WIDE_INT bitpos, ! unsigned HOST_WIDE_INT bitregion_start, ! unsigned HOST_WIDE_INT bitregion_end, ! machine_mode mode, tree exp, int cleared, alias_set_type alias_set, bool reverse) { *************** store_constructor_field (rtx target, uns *** 5967,5974 **** reverse); } else ! store_field (target, bitsize, bitpos, 0, 0, mode, exp, alias_set, false, ! reverse); } --- 5971,5978 ---- reverse); } else ! store_field (target, bitsize, bitpos, bitregion_start, bitregion_end, mode, ! exp, alias_set, false, reverse); } *************** store_constructor (tree exp, rtx target, *** 6003,6008 **** --- 6007,6013 ---- { tree type = TREE_TYPE (exp); HOST_WIDE_INT exp_size = int_size_in_bytes (type); + HOST_WIDE_INT bitregion_end = size > 0 ? size * BITS_PER_UNIT - 1 : 0; switch (TREE_CODE (type)) { *************** store_constructor (tree exp, rtx target, *** 6081,6087 **** if (tree_fits_uhwi_p (DECL_SIZE (field))) bitsize = tree_to_uhwi (DECL_SIZE (field)); else ! bitsize = -1; mode = DECL_MODE (field); if (DECL_BIT_FIELD (field)) --- 6086,6092 ---- if (tree_fits_uhwi_p (DECL_SIZE (field))) bitsize = tree_to_uhwi (DECL_SIZE (field)); else ! gcc_unreachable (); mode = DECL_MODE (field); if (DECL_BIT_FIELD (field)) *************** store_constructor (tree exp, rtx target, *** 6092,6122 **** && tree_fits_shwi_p (bit_position (field))) { bitpos = int_bit_position (field); ! offset = 0; } else ! bitpos = tree_to_shwi (DECL_FIELD_BIT_OFFSET (field)); ! ! if (offset) ! { ! machine_mode address_mode; ! rtx offset_rtx; ! ! offset ! = SUBSTITUTE_PLACEHOLDER_IN_EXPR (offset, ! make_tree (TREE_TYPE (exp), ! target)); ! ! offset_rtx = expand_normal (offset); ! gcc_assert (MEM_P (to_rtx)); ! ! address_mode = get_address_mode (to_rtx); ! if (GET_MODE (offset_rtx) != address_mode) ! offset_rtx = convert_to_mode (address_mode, offset_rtx, 0); ! ! to_rtx = offset_address (to_rtx, offset_rtx, ! highest_pow2_factor (offset)); ! } /* If this initializes a field that is smaller than a word, at the start of a word, try to widen it to a full --- 6097,6106 ---- && tree_fits_shwi_p (bit_position (field))) { bitpos = int_bit_position (field); ! offset = NULL_TREE; } else ! gcc_unreachable (); /* If this initializes a field that is smaller than a word, at the start of a word, try to widen it to a full *************** store_constructor (tree exp, rtx target, *** 6164,6170 **** MEM_KEEP_ALIAS_SET_P (to_rtx) = 1; } ! store_constructor_field (to_rtx, bitsize, bitpos, mode, value, cleared, get_alias_set (TREE_TYPE (field)), reverse); --- 6148,6155 ---- MEM_KEEP_ALIAS_SET_P (to_rtx) = 1; } ! store_constructor_field (to_rtx, bitsize, bitpos, ! 0, bitregion_end, mode, value, cleared, get_alias_set (TREE_TYPE (field)), reverse); *************** store_constructor (tree exp, rtx target, *** 6324,6330 **** } store_constructor_field ! (target, bitsize, bitpos, mode, value, cleared, get_alias_set (elttype), reverse); } } --- 6309,6316 ---- } store_constructor_field ! (target, bitsize, bitpos, 0, bitregion_end, ! mode, value, cleared, get_alias_set (elttype), reverse); } } *************** store_constructor (tree exp, rtx target, *** 6427,6433 **** target = copy_rtx (target); MEM_KEEP_ALIAS_SET_P (target) = 1; } ! store_constructor_field (target, bitsize, bitpos, mode, value, cleared, get_alias_set (elttype), reverse); } --- 6413,6420 ---- target = copy_rtx (target); MEM_KEEP_ALIAS_SET_P (target) = 1; } ! store_constructor_field (target, bitsize, bitpos, 0, ! bitregion_end, mode, value, cleared, get_alias_set (elttype), reverse); } *************** store_constructor (tree exp, rtx target, *** 6561,6567 **** ? TYPE_MODE (TREE_TYPE (value)) : eltmode; bitpos = eltpos * elt_size; ! store_constructor_field (target, bitsize, bitpos, value_mode, value, cleared, alias, reverse); } } --- 6548,6555 ---- ? TYPE_MODE (TREE_TYPE (value)) : eltmode; bitpos = eltpos * elt_size; ! store_constructor_field (target, bitsize, bitpos, 0, ! bitregion_end, value_mode, value, cleared, alias, reverse); } } *************** store_field (rtx target, HOST_WIDE_INT b *** 6700,6712 **** temp = expand_normal (exp); ! /* If the value has a record type and an integral mode then, if BITSIZE ! is narrower than this mode and this is for big-endian data, we must ! first put the value into the low-order bits. Moreover, the field may ! be not aligned on a byte boundary; in this case, if it has reverse ! storage order, it needs to be accessed as a scalar field with reverse ! storage order and we must first put the value into target order. */ ! if (TREE_CODE (TREE_TYPE (exp)) == RECORD_TYPE && GET_MODE_CLASS (GET_MODE (temp)) == MODE_INT) { HOST_WIDE_INT size = GET_MODE_BITSIZE (GET_MODE (temp)); --- 6688,6723 ---- temp = expand_normal (exp); ! /* Handle calls that return values in multiple non-contiguous locations. ! The Irix 6 ABI has examples of this. */ ! if (GET_CODE (temp) == PARALLEL) ! { ! HOST_WIDE_INT size = int_size_in_bytes (TREE_TYPE (exp)); ! machine_mode temp_mode ! = smallest_mode_for_size (size * BITS_PER_UNIT, MODE_INT); ! rtx temp_target = gen_reg_rtx (temp_mode); ! emit_group_store (temp_target, temp, TREE_TYPE (exp), size); ! temp = temp_target; ! } ! ! /* Handle calls that return BLKmode values in registers. */ ! else if (mode == BLKmode && REG_P (temp) && TREE_CODE (exp) == CALL_EXPR) ! { ! rtx temp_target = gen_reg_rtx (GET_MODE (temp)); ! copy_blkmode_from_reg (temp_target, temp, TREE_TYPE (exp)); ! temp = temp_target; ! } ! ! /* If the value has aggregate type and an integral mode then, if BITSIZE ! is narrower than this mode and this is for big-endian data, we first ! need to put the value into the low-order bits for store_bit_field, ! except when MODE is BLKmode and BITSIZE larger than the word size ! (see the handling of fields larger than a word in store_bit_field). ! Moreover, the field may be not aligned on a byte boundary; in this ! case, if it has reverse storage order, it needs to be accessed as a ! scalar field with reverse storage order and we must first put the ! value into target order. */ ! if (AGGREGATE_TYPE_P (TREE_TYPE (exp)) && GET_MODE_CLASS (GET_MODE (temp)) == MODE_INT) { HOST_WIDE_INT size = GET_MODE_BITSIZE (GET_MODE (temp)); *************** store_field (rtx target, HOST_WIDE_INT b *** 6717,6723 **** temp = flip_storage_order (GET_MODE (temp), temp); if (bitsize < size ! && reverse ? !BYTES_BIG_ENDIAN : BYTES_BIG_ENDIAN) temp = expand_shift (RSHIFT_EXPR, GET_MODE (temp), temp, size - bitsize, NULL_RTX, 1); } --- 6728,6735 ---- temp = flip_storage_order (GET_MODE (temp), temp); if (bitsize < size ! && reverse ? !BYTES_BIG_ENDIAN : BYTES_BIG_ENDIAN ! && !(mode == BLKmode && bitsize > BITS_PER_WORD)) temp = expand_shift (RSHIFT_EXPR, GET_MODE (temp), temp, size - bitsize, NULL_RTX, 1); } *************** store_field (rtx target, HOST_WIDE_INT b *** 6727,6738 **** && mode != TYPE_MODE (TREE_TYPE (exp))) temp = convert_modes (mode, TYPE_MODE (TREE_TYPE (exp)), temp, 1); ! /* If TEMP is not a PARALLEL (see below) and its mode and that of TARGET ! are both BLKmode, both must be in memory and BITPOS must be aligned ! on a byte boundary. If so, we simply do a block copy. Likewise for ! a BLKmode-like TARGET. */ ! if (GET_CODE (temp) != PARALLEL ! && GET_MODE (temp) == BLKmode && (GET_MODE (target) == BLKmode || (MEM_P (target) && GET_MODE_CLASS (GET_MODE (target)) == MODE_INT --- 6739,6748 ---- && mode != TYPE_MODE (TREE_TYPE (exp))) temp = convert_modes (mode, TYPE_MODE (TREE_TYPE (exp)), temp, 1); ! /* If the mode of TEMP and TARGET is BLKmode, both must be in memory ! and BITPOS must be aligned on a byte boundary. If so, we simply do ! a block copy. Likewise for a BLKmode-like TARGET. */ ! if (GET_MODE (temp) == BLKmode && (GET_MODE (target) == BLKmode || (MEM_P (target) && GET_MODE_CLASS (GET_MODE (target)) == MODE_INT *************** store_field (rtx target, HOST_WIDE_INT b *** 6751,6788 **** return const0_rtx; } ! /* Handle calls that return values in multiple non-contiguous locations. ! The Irix 6 ABI has examples of this. */ ! if (GET_CODE (temp) == PARALLEL) ! { ! HOST_WIDE_INT size = int_size_in_bytes (TREE_TYPE (exp)); ! rtx temp_target; ! if (mode == BLKmode || mode == VOIDmode) ! mode = smallest_mode_for_size (size * BITS_PER_UNIT, MODE_INT); ! temp_target = gen_reg_rtx (mode); ! emit_group_store (temp_target, temp, TREE_TYPE (exp), size); ! temp = temp_target; ! } ! else if (mode == BLKmode) { ! /* Handle calls that return BLKmode values in registers. */ ! if (REG_P (temp) && TREE_CODE (exp) == CALL_EXPR) ! { ! rtx temp_target = gen_reg_rtx (GET_MODE (temp)); ! copy_blkmode_from_reg (temp_target, temp, TREE_TYPE (exp)); ! temp = temp_target; ! } ! else ! { ! HOST_WIDE_INT size = int_size_in_bytes (TREE_TYPE (exp)); ! rtx temp_target; ! mode = smallest_mode_for_size (size * BITS_PER_UNIT, MODE_INT); ! temp_target = gen_reg_rtx (mode); ! temp_target ! = extract_bit_field (temp, size * BITS_PER_UNIT, 0, 1, ! temp_target, mode, mode, false); ! temp = temp_target; ! } } /* Store the value in the bitfield. */ --- 6761,6773 ---- return const0_rtx; } ! /* If the mode of TEMP is still BLKmode and BITSIZE not larger than the ! word size, we need to load the value (see again store_bit_field). */ ! if (GET_MODE (temp) == BLKmode && bitsize <= BITS_PER_WORD) { ! machine_mode temp_mode = smallest_mode_for_size (bitsize, MODE_INT); ! temp = extract_bit_field (temp, bitsize, 0, 1, NULL_RTX, temp_mode, ! temp_mode, false); } /* Store the value in the bitfield. */ *************** expand_expr_real_2 (sepops ops, rtx targ *** 8800,8805 **** --- 8785,8802 ---- if (temp != 0) return temp; + /* For vector MIN , expand it a VEC_COND_EXPR + and similarly for MAX . */ + if (VECTOR_TYPE_P (type)) + { + tree t0 = make_tree (type, op0); + tree t1 = make_tree (type, op1); + tree comparison = build2 (code == MIN_EXPR ? LE_EXPR : GE_EXPR, + type, t0, t1); + return expand_vec_cond_expr (type, comparison, t0, t1, + original_target); + } + /* At this point, a MEM target is no longer useful; we will get better code without it. */ *************** expand_expr_real_2 (sepops ops, rtx targ *** 8941,8949 **** /* Left shift optimization when shifting across word_size boundary. ! If mode == GET_MODE_WIDER_MODE (word_mode), then normally there isn't ! native instruction to support this wide mode left shift. Given below ! scenario: Type A = (Type) B << C --- 8938,8946 ---- /* Left shift optimization when shifting across word_size boundary. ! If mode == GET_MODE_WIDER_MODE (word_mode), then normally ! there isn't native instruction to support this wide mode ! left shift. Given below scenario: Type A = (Type) B << C *************** expand_expr_real_2 (sepops ops, rtx targ *** 8952,8961 **** | word_size | ! If the shift amount C caused we shift B to across the word size ! boundary, i.e part of B shifted into high half of destination ! register, and part of B remains in the low half, then GCC will use ! the following left shift expand logic: 1. Initialize dest_low to B. 2. Initialize every bit of dest_high to the sign bit of B. --- 8949,8959 ---- | word_size | ! If the shift amount C caused we shift B to across the word ! size boundary, i.e part of B shifted into high half of ! destination register, and part of B remains in the low ! half, then GCC will use the following left shift expand ! logic: 1. Initialize dest_low to B. 2. Initialize every bit of dest_high to the sign bit of B. *************** expand_expr_real_2 (sepops ops, rtx targ *** 8965,8984 **** 5. Logic right shift D by (word_size - C). 6. Or the result of 4 and 5 to finalize dest_high. ! While, by checking gimple statements, if operand B is coming from ! signed extension, then we can simplify above expand logic into: 1. dest_high = src_low >> (word_size - C). 2. dest_low = src_low << C. ! We can use one arithmetic right shift to finish all the purpose of ! steps 2, 4, 5, 6, thus we reduce the steps needed from 6 into 2. */ temp = NULL_RTX; if (code == LSHIFT_EXPR && target && REG_P (target) - && ! unsignedp && mode == GET_MODE_WIDER_MODE (word_mode) && GET_MODE_SIZE (mode) == 2 * GET_MODE_SIZE (word_mode) && TREE_CONSTANT (treeop1) --- 8963,8992 ---- 5. Logic right shift D by (word_size - C). 6. Or the result of 4 and 5 to finalize dest_high. ! While, by checking gimple statements, if operand B is ! coming from signed extension, then we can simplify above ! expand logic into: 1. dest_high = src_low >> (word_size - C). 2. dest_low = src_low << C. ! We can use one arithmetic right shift to finish all the ! purpose of steps 2, 4, 5, 6, thus we reduce the steps ! needed from 6 into 2. ! ! The case is similar for zero extension, except that we ! initialize dest_high to zero rather than copies of the sign ! bit from B. Furthermore, we need to use a logical right shift ! in this case. ! ! The choice of sign-extension versus zero-extension is ! determined entirely by whether or not B is signed and is ! independent of the current setting of unsignedp. */ temp = NULL_RTX; if (code == LSHIFT_EXPR && target && REG_P (target) && mode == GET_MODE_WIDER_MODE (word_mode) && GET_MODE_SIZE (mode) == 2 * GET_MODE_SIZE (word_mode) && TREE_CONSTANT (treeop1) *************** expand_expr_real_2 (sepops ops, rtx targ *** 8999,9004 **** --- 9007,9014 ---- rtx_insn *seq, *seq_old; unsigned int high_off = subreg_highpart_offset (word_mode, mode); + bool extend_unsigned + = TYPE_UNSIGNED (TREE_TYPE (gimple_assign_rhs1 (def))); rtx low = lowpart_subreg (word_mode, op0, mode); rtx dest_low = lowpart_subreg (word_mode, target, mode); rtx dest_high = simplify_gen_subreg (word_mode, target, *************** expand_expr_real_2 (sepops ops, rtx targ *** 9010,9016 **** start_sequence (); /* dest_high = src_low >> (word_size - C). */ temp = expand_variable_shift (RSHIFT_EXPR, word_mode, low, ! rshift, dest_high, unsignedp); if (temp != dest_high) emit_move_insn (dest_high, temp); --- 9020,9027 ---- start_sequence (); /* dest_high = src_low >> (word_size - C). */ temp = expand_variable_shift (RSHIFT_EXPR, word_mode, low, ! rshift, dest_high, ! extend_unsigned); if (temp != dest_high) emit_move_insn (dest_high, temp); diff -Nrcpad gcc-6.3.0/gcc/expr.h gcc-6.4.0/gcc/expr.h *** gcc-6.3.0/gcc/expr.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/expr.h Tue May 9 12:24:53 2017 *************** extern rtx push_block (rtx, int, int); *** 223,228 **** --- 223,232 ---- extern bool emit_push_insn (rtx, machine_mode, tree, rtx, unsigned int, int, rtx, int, rtx, rtx, int, rtx, bool); + /* Extract the accessible bit-range from a COMPONENT_REF. */ + extern void get_bit_range (unsigned HOST_WIDE_INT *, unsigned HOST_WIDE_INT *, + tree, HOST_WIDE_INT *, tree *); + /* Expand an assignment that stores the value of FROM into TO. */ extern void expand_assignment (tree, tree, bool); diff -Nrcpad gcc-6.3.0/gcc/fold-const.c gcc-6.4.0/gcc/fold-const.c *** gcc-6.3.0/gcc/fold-const.c Wed Nov 23 14:31:16 2016 --- gcc-6.4.0/gcc/fold-const.c Thu Jun 22 07:30:03 2017 *************** static tree fold_relational_const (enum *** 143,148 **** --- 143,149 ---- static tree fold_convert_const (enum tree_code, tree, tree); static tree fold_view_convert_expr (tree, tree); static bool vec_cst_ctor_to_array (tree, tree *); + static tree fold_negate_expr (location_t, tree); /* Return EXPR_LOCATION of T if it is not UNKNOWN_LOCATION. *************** negate_expr_p (tree t) *** 530,536 **** returned. */ static tree ! fold_negate_expr (location_t loc, tree t) { tree type = TREE_TYPE (t); tree tem; --- 531,537 ---- returned. */ static tree ! fold_negate_expr_1 (location_t loc, tree t) { tree type = TREE_TYPE (t); tree tem; *************** fold_negate_expr (location_t loc, tree t *** 541,547 **** case BIT_NOT_EXPR: if (INTEGRAL_TYPE_P (type)) return fold_build2_loc (loc, PLUS_EXPR, type, TREE_OPERAND (t, 0), ! build_one_cst (type)); break; case INTEGER_CST: --- 542,548 ---- case BIT_NOT_EXPR: if (INTEGRAL_TYPE_P (type)) return fold_build2_loc (loc, PLUS_EXPR, type, TREE_OPERAND (t, 0), ! build_one_cst (type)); break; case INTEGER_CST: *************** fold_negate_expr (location_t loc, tree t *** 589,602 **** case COMPLEX_EXPR: if (negate_expr_p (t)) return fold_build2_loc (loc, COMPLEX_EXPR, type, ! fold_negate_expr (loc, TREE_OPERAND (t, 0)), ! fold_negate_expr (loc, TREE_OPERAND (t, 1))); break; case CONJ_EXPR: if (negate_expr_p (t)) return fold_build1_loc (loc, CONJ_EXPR, type, ! fold_negate_expr (loc, TREE_OPERAND (t, 0))); break; case NEGATE_EXPR: --- 590,603 ---- case COMPLEX_EXPR: if (negate_expr_p (t)) return fold_build2_loc (loc, COMPLEX_EXPR, type, ! fold_negate_expr (loc, TREE_OPERAND (t, 0)), ! fold_negate_expr (loc, TREE_OPERAND (t, 1))); break; case CONJ_EXPR: if (negate_expr_p (t)) return fold_build1_loc (loc, CONJ_EXPR, type, ! fold_negate_expr (loc, TREE_OPERAND (t, 0))); break; case NEGATE_EXPR: *************** fold_negate_expr (location_t loc, tree t *** 615,621 **** { tem = negate_expr (TREE_OPERAND (t, 1)); return fold_build2_loc (loc, MINUS_EXPR, type, ! tem, TREE_OPERAND (t, 0)); } /* -(A + B) -> (-A) - B. */ --- 616,622 ---- { tem = negate_expr (TREE_OPERAND (t, 1)); return fold_build2_loc (loc, MINUS_EXPR, type, ! tem, TREE_OPERAND (t, 0)); } /* -(A + B) -> (-A) - B. */ *************** fold_negate_expr (location_t loc, tree t *** 623,629 **** { tem = negate_expr (TREE_OPERAND (t, 0)); return fold_build2_loc (loc, MINUS_EXPR, type, ! tem, TREE_OPERAND (t, 1)); } } break; --- 624,630 ---- { tem = negate_expr (TREE_OPERAND (t, 0)); return fold_build2_loc (loc, MINUS_EXPR, type, ! tem, TREE_OPERAND (t, 1)); } } break; *************** fold_negate_expr (location_t loc, tree t *** 634,640 **** && !HONOR_SIGNED_ZEROS (element_mode (type)) && reorder_operands_p (TREE_OPERAND (t, 0), TREE_OPERAND (t, 1))) return fold_build2_loc (loc, MINUS_EXPR, type, ! TREE_OPERAND (t, 1), TREE_OPERAND (t, 0)); break; case MULT_EXPR: --- 635,641 ---- && !HONOR_SIGNED_ZEROS (element_mode (type)) && reorder_operands_p (TREE_OPERAND (t, 0), TREE_OPERAND (t, 1))) return fold_build2_loc (loc, MINUS_EXPR, type, ! TREE_OPERAND (t, 1), TREE_OPERAND (t, 0)); break; case MULT_EXPR: *************** fold_negate_expr (location_t loc, tree t *** 649,659 **** tem = TREE_OPERAND (t, 1); if (negate_expr_p (tem)) return fold_build2_loc (loc, TREE_CODE (t), type, ! TREE_OPERAND (t, 0), negate_expr (tem)); tem = TREE_OPERAND (t, 0); if (negate_expr_p (tem)) return fold_build2_loc (loc, TREE_CODE (t), type, ! negate_expr (tem), TREE_OPERAND (t, 1)); } break; --- 650,660 ---- tem = TREE_OPERAND (t, 1); if (negate_expr_p (tem)) return fold_build2_loc (loc, TREE_CODE (t), type, ! TREE_OPERAND (t, 0), negate_expr (tem)); tem = TREE_OPERAND (t, 0); if (negate_expr_p (tem)) return fold_build2_loc (loc, TREE_CODE (t), type, ! negate_expr (tem), TREE_OPERAND (t, 1)); } break; *************** fold_negate_expr (location_t loc, tree t *** 726,731 **** --- 727,745 ---- return NULL_TREE; } + /* A wrapper for fold_negate_expr_1. */ + + static tree + fold_negate_expr (location_t loc, tree t) + { + tree type = TREE_TYPE (t); + STRIP_SIGN_NOPS (t); + tree tem = fold_negate_expr_1 (loc, t); + if (tem == NULL_TREE) + return NULL_TREE; + return fold_convert_loc (loc, type, tem); + } + /* Like fold_negate_expr, but return a NEGATE_EXPR tree, if T can not be negated in a simpler way. Also allow for T to be NULL_TREE, in which case return NULL_TREE. */ *************** split_tree (location_t loc, tree in, tre *** 828,835 **** /* Now do any needed negations. */ if (neg_litp_p) *minus_litp = *litp, *litp = 0; ! if (neg_conp_p) ! *conp = negate_expr (*conp); if (neg_var_p && var) { /* Convert to TYPE before negating. */ --- 842,853 ---- /* Now do any needed negations. */ if (neg_litp_p) *minus_litp = *litp, *litp = 0; ! if (neg_conp_p && *conp) ! { ! /* Convert to TYPE before negating. */ ! *conp = fold_convert_loc (loc, type, *conp); ! *conp = negate_expr (*conp); ! } if (neg_var_p && var) { /* Convert to TYPE before negating. */ *************** split_tree (location_t loc, tree in, tre *** 856,862 **** *minus_litp = *litp, *litp = 0; else if (*minus_litp) *litp = *minus_litp, *minus_litp = 0; ! *conp = negate_expr (*conp); if (var) { /* Convert to TYPE before negating. */ --- 874,885 ---- *minus_litp = *litp, *litp = 0; else if (*minus_litp) *litp = *minus_litp, *minus_litp = 0; ! if (*conp) ! { ! /* Convert to TYPE before negating. */ ! *conp = fold_convert_loc (loc, type, *conp); ! *conp = negate_expr (*conp); ! } if (var) { /* Convert to TYPE before negating. */ *************** make_bit_field_ref (location_t loc, tree *** 3787,3792 **** --- 3810,3840 ---- { tree result, bftype; + /* Attempt not to lose the access path if possible. */ + if (TREE_CODE (orig_inner) == COMPONENT_REF) + { + tree ninner = TREE_OPERAND (orig_inner, 0); + machine_mode nmode; + HOST_WIDE_INT nbitsize, nbitpos; + tree noffset; + int nunsignedp, nreversep, nvolatilep = 0; + tree base = get_inner_reference (ninner, &nbitsize, &nbitpos, + &noffset, &nmode, &nunsignedp, + &nreversep, &nvolatilep, false); + if (base == inner + && noffset == NULL_TREE + && nbitsize >= bitsize + && nbitpos <= bitpos + && bitpos + bitsize <= nbitpos + nbitsize + && !reversep + && !nreversep + && !nvolatilep) + { + inner = ninner; + bitpos -= nbitpos; + } + } + alias_set_type iset = get_alias_set (orig_inner); if (iset == 0 && get_alias_set (inner) != iset) inner = fold_build2 (MEM_REF, TREE_TYPE (inner), *************** optimize_bit_field_compare (location_t l *** 3881,3889 **** return 0; } /* See if we can find a mode to refer to this field. We should be able to, but fail if we can't. */ ! nmode = get_best_mode (lbitsize, lbitpos, 0, 0, const_p ? TYPE_ALIGN (TREE_TYPE (linner)) : MIN (TYPE_ALIGN (TREE_TYPE (linner)), TYPE_ALIGN (TREE_TYPE (rinner))), --- 3929,3947 ---- return 0; } + /* Honor the C++ memory model and mimic what RTL expansion does. */ + unsigned HOST_WIDE_INT bitstart = 0; + unsigned HOST_WIDE_INT bitend = 0; + if (TREE_CODE (lhs) == COMPONENT_REF) + { + get_bit_range (&bitstart, &bitend, lhs, &lbitpos, &offset); + if (offset != NULL_TREE) + return 0; + } + /* See if we can find a mode to refer to this field. We should be able to, but fail if we can't. */ ! nmode = get_best_mode (lbitsize, lbitpos, bitstart, bitend, const_p ? TYPE_ALIGN (TREE_TYPE (linner)) : MIN (TYPE_ALIGN (TREE_TYPE (linner)), TYPE_ALIGN (TREE_TYPE (rinner))), *************** fold_comparison (location_t loc, enum tr *** 8864,8870 **** if (save_p) { tem = save_expr (build2 (code, type, cval1, cval2)); ! SET_EXPR_LOCATION (tem, loc); return tem; } return fold_build2_loc (loc, code, type, cval1, cval2); --- 8922,8928 ---- if (save_p) { tem = save_expr (build2 (code, type, cval1, cval2)); ! protected_set_expr_location (tem, loc); return tem; } return fold_build2_loc (loc, code, type, cval1, cval2); *************** fold_binary_loc (location_t loc, *** 10107,10118 **** } if (c3 != c1) ! return fold_build2_loc (loc, BIT_IOR_EXPR, type, ! fold_build2_loc (loc, BIT_AND_EXPR, type, ! TREE_OPERAND (arg0, 0), ! wide_int_to_tree (type, ! c3)), ! arg1); } /* See if this can be simplified into a rotate first. If that --- 10165,10176 ---- } if (c3 != c1) ! { ! tem = fold_convert_loc (loc, type, TREE_OPERAND (arg0, 0)); ! tem = fold_build2_loc (loc, BIT_AND_EXPR, type, tem, ! wide_int_to_tree (type, c3)); ! return fold_build2_loc (loc, BIT_IOR_EXPR, type, tem, arg1); ! } } /* See if this can be simplified into a rotate first. If that *************** fold_binary_loc (location_t loc, *** 10435,10441 **** /* Convert -A / -B to A / B when the type is signed and overflow is undefined. */ if ((!INTEGRAL_TYPE_P (type) || TYPE_OVERFLOW_UNDEFINED (type)) ! && TREE_CODE (arg0) == NEGATE_EXPR && negate_expr_p (op1)) { if (INTEGRAL_TYPE_P (type)) --- 10493,10499 ---- /* Convert -A / -B to A / B when the type is signed and overflow is undefined. */ if ((!INTEGRAL_TYPE_P (type) || TYPE_OVERFLOW_UNDEFINED (type)) ! && TREE_CODE (op0) == NEGATE_EXPR && negate_expr_p (op1)) { if (INTEGRAL_TYPE_P (type)) *************** split_address_to_core_and_offset (tree e *** 14549,14554 **** --- 14607,14630 ---- &volatilep, false); core = build_fold_addr_expr_loc (loc, core); } + else if (TREE_CODE (exp) == POINTER_PLUS_EXPR) + { + core = TREE_OPERAND (exp, 0); + STRIP_NOPS (core); + *pbitpos = 0; + *poffset = TREE_OPERAND (exp, 1); + if (TREE_CODE (*poffset) == INTEGER_CST) + { + offset_int tem = wi::sext (wi::to_offset (*poffset), + TYPE_PRECISION (TREE_TYPE (*poffset))); + tem = wi::lshift (tem, LOG2_BITS_PER_UNIT); + if (wi::fits_shwi_p (tem)) + { + *pbitpos = tem.to_shwi (); + *poffset = NULL_TREE; + } + } + } else { core = exp; diff -Nrcpad gcc-6.3.0/gcc/fortran/ChangeLog gcc-6.4.0/gcc/fortran/ChangeLog *** gcc-6.3.0/gcc/fortran/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/fortran/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,151 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-06-22 Jakub Jelinek + + Backported from mainline + 2017-06-02 Jakub Jelinek + + PR fortran/80918 + * openmp.c (resolve_omp_clauses): Fix a typo. + + 2017-06-09 Janus Weil + + Backport from trunk + PR fortran/70601 + * trans-expr.c (gfc_conv_procedure_call): Fix detection of allocatable + function results. + + 2017-05-03 Thomas Koenig + + PR fortran/65542 + Backport from trunk + * intrinsic.c (gfc_intrinsic_func_interface): Return an error + for -std=f95 for disallowed transformational functions in + initialization expressions. + + 2017-06-02 Thomas Koenig + + PR fortran/80904 + Backport from trunk + * frontend-passes.c (matmul_lhs_realloc): Correct + allocation size for case A1B2. + + 2017-05-15 Steven G. Kargl + + PR fortran/80752 + * expr.c (gfc_generate_initializer): If type conversion fails, + check for error and return NULL. + + 2017-05-01 Janus Weil + + Backport from trunk + PR fortran/80392 + * trans-types.c (gfc_get_derived_type): Prevent an infinite loop when + building a derived type that includes a procedure pointer component + with a polymorphic result. + + 2017-04-21 Janus Weil + + Backport from trunk + PR fortran/80361 + * class.c (generate_finalization_wrapper): Give the finalization wrapper + the recursive attribute. + + 2017-04-01 Paul Thomas + + Backport from trunk + PR fortran/71838 + * symbol.c (check_conflict): A dummy procedure in a submodule, + module procedure is not an error. + (gfc_add_flavor): Ditto. + + 2017-04-01 Paul Thomas + + Backport from trunk + PR fortran/79676 + * module.c (mio_symbol_attribute): Remove reset of the flag + 'no_module_procedures'. + (check_for_module_procedures): New function. Move declaration + of 'no_module_procedures' to above it. + (gfc_dump_module): Traverse namespace calling new function. + + 2017-03-26 Paul Thomas + + Backport from trunk + PR fortran/79434 + * parse.c (check_component, parse_union): Whitespace. + (set_syms_host_assoc): For a derived type, check if the module + in which it was declared is one of the submodule ancestors. If + it is, make the components public. Otherwise, reset attribute + 'host_assoc' and set 'use-assoc' so that encapsulation is + preserved. + + 2017-03-14 Richard Biener + + Backport from mainline + 2017-03-06 Richard Biener + + PR fortran/79894 + * trans.c (gfc_add_modify_loc): Weaken assert. + + 2017-02-25 Paul Thomas + + PR fortran/78474 + * module.c (gfc_match_submodule): If there is more than one + colon, it is a syntax error. + + PR fortran/78331 + * module.c (gfc_use_module): If an smod file does not exist it + is either because the module does not have a module procedure + interface or there is an error in the module. + + 2017-02-07 Steven G. Kargl + + * trans-types.c (gfc_get_int_kind_from_width_isofortranen): Choose + REAL type with the widest precision if two (or more) have the same + storage size. + + 2017-01-29 Andre Vehreschild + + Backported from trunk + 2017-01-13 Andre Vehreschild + + PR fortran/70697 + * resolve.c (resolve_lock_unlock_event): Resolve the expression for + event's until_count. + + 2017-01-29 Andre Vehreschild + + Backport from trunk + PR fortran/70696 + * trans-expr.c (gfc_get_tree_for_caf_expr): Ensure the backend_decl + is valid before accessing it. Remove unnecessary assert. + * trans-decl.c (gfc_build_qualified_array): Add static tokens to the + parent function's scope only, when the decl-context is not the + translation unit. + + 2017-01-17 Jakub Jelinek + + Backported from mainline + 2016-12-21 Jakub Jelinek + + PR fortran/78866 + * openmp.c (resolve_omp_clauses): Diagnose assumed size arrays in + OpenMP map, to and from clauses. + * trans-openmp.c: Include diagnostic-core.h, temporarily redefining + GCC_DIAG_STYLE to __gcc_tdiag__. + (gfc_omp_finish_clause): Diagnose implicitly mapped assumed size + arrays. + + 2016-12-22 Thomas Koenig + + Backport from trunk + PR fortran/78239 + * decl.c (char_len_param_value): Also check for -fimplicit-none + when determining if implicit none is in force. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/fortran/class.c gcc-6.4.0/gcc/fortran/class.c *** gcc-6.3.0/gcc/fortran/class.c Sun Dec 4 16:00:27 2016 --- gcc-6.4.0/gcc/fortran/class.c Fri Apr 21 21:11:22 2017 *************** generate_finalization_wrapper (gfc_symbo *** 1599,1604 **** --- 1599,1605 ---- final->attr.flavor = FL_PROCEDURE; final->attr.function = 1; final->attr.pure = 0; + final->attr.recursive = 1; final->result = final; final->ts.type = BT_INTEGER; final->ts.kind = 4; diff -Nrcpad gcc-6.3.0/gcc/fortran/decl.c gcc-6.4.0/gcc/fortran/decl.c *** gcc-6.3.0/gcc/fortran/decl.c Wed Sep 28 20:18:56 2016 --- gcc-6.4.0/gcc/fortran/decl.c Thu Dec 22 17:05:13 2016 *************** char_len_param_value (gfc_expr **expr, b *** 922,928 **** if (!t && e->ts.type == BT_UNKNOWN && e->symtree->n.sym->attr.untyped == 1 ! && (e->symtree->n.sym->ns->seen_implicit_none == 1 || e->symtree->n.sym->ns->parent->seen_implicit_none == 1)) { gfc_free_expr (e); --- 922,929 ---- if (!t && e->ts.type == BT_UNKNOWN && e->symtree->n.sym->attr.untyped == 1 ! && (flag_implicit_none ! || e->symtree->n.sym->ns->seen_implicit_none == 1 || e->symtree->n.sym->ns->parent->seen_implicit_none == 1)) { gfc_free_expr (e); diff -Nrcpad gcc-6.3.0/gcc/fortran/expr.c gcc-6.4.0/gcc/fortran/expr.c *** gcc-6.3.0/gcc/fortran/expr.c Thu Nov 24 19:26:33 2016 --- gcc-6.4.0/gcc/fortran/expr.c Mon May 15 23:02:42 2017 *************** gfc_default_initializer (gfc_typespec *t *** 3983,3989 **** if ((comp->ts.type != comp->initializer->ts.type || comp->ts.kind != comp->initializer->ts.kind) && !comp->attr.pointer && !comp->attr.proc_pointer) ! gfc_convert_type_warn (ctor->expr, &comp->ts, 2, false); } if (comp->attr.allocatable --- 3983,3994 ---- if ((comp->ts.type != comp->initializer->ts.type || comp->ts.kind != comp->initializer->ts.kind) && !comp->attr.pointer && !comp->attr.proc_pointer) ! { ! bool val; ! val = gfc_convert_type_warn (ctor->expr, &comp->ts, 1, false); ! if (val == false) ! return NULL; ! } } if (comp->attr.allocatable diff -Nrcpad gcc-6.3.0/gcc/fortran/frontend-passes.c gcc-6.4.0/gcc/fortran/frontend-passes.c *** gcc-6.3.0/gcc/fortran/frontend-passes.c Mon Oct 31 18:28:11 2016 --- gcc-6.4.0/gcc/fortran/frontend-passes.c Fri Jun 2 19:29:29 2017 *************** matmul_lhs_realloc (gfc_expr *c, gfc_exp *** 2306,2312 **** break; case A1B2: ! ar->start[0] = get_array_inq_function (GFC_ISYM_SIZE, b, 1); cond = build_logical_expr (INTRINSIC_NE, get_array_inq_function (GFC_ISYM_SIZE, c, 1), get_array_inq_function (GFC_ISYM_SIZE, b, 2)); --- 2306,2312 ---- break; case A1B2: ! ar->start[0] = get_array_inq_function (GFC_ISYM_SIZE, b, 2); cond = build_logical_expr (INTRINSIC_NE, get_array_inq_function (GFC_ISYM_SIZE, c, 1), get_array_inq_function (GFC_ISYM_SIZE, b, 2)); diff -Nrcpad gcc-6.3.0/gcc/fortran/gfortran.info gcc-6.4.0/gcc/fortran/gfortran.info *** gcc-6.3.0/gcc/fortran/gfortran.info Wed Dec 21 09:34:08 2016 --- gcc-6.4.0/gcc/fortran/gfortran.info Tue Jul 4 09:27:46 2017 *************** *** 1,5 **** ! This is gfortran.info, produced by makeinfo version 6.1 from ! gfortran.texi. Copyright (C) 1999-2016 Free Software Foundation, Inc. --- 1,5 ---- ! This is doc/gfortran.info, produced by makeinfo version 4.13 from ! /space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/fortran/gfortran.texi. Copyright (C) 1999-2016 Free Software Foundation, Inc. *************** Free Documentation License". *** 18,32 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * gfortran: (gfortran). The GNU Fortran Compiler. END-INFO-DIR-ENTRY - This file documents the use and the internals of the GNU Fortran ! compiler, ('gfortran'). Published by the Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110-1301 USA --- 18,32 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development. ! INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * gfortran: (gfortran). The GNU Fortran Compiler. END-INFO-DIR-ENTRY This file documents the use and the internals of the GNU Fortran ! compiler, (`gfortran'). Published by the Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110-1301 USA *************** Free Documentation License". *** 48,55 **** (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise funds ! for GNU development.  File: gfortran.info, Node: Top, Next: Introduction, Up: (dir) --- 48,55 ---- (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU ! software. Copies published by the Free Software Foundation raise ! funds for GNU development.  File: gfortran.info, Node: Top, Next: Introduction, Up: (dir) *************** File: gfortran.info, Node: Top, Next: *** 57,64 **** Introduction ************ ! This manual documents the use of 'gfortran', the GNU Fortran compiler. ! You can find in this manual how to invoke 'gfortran', as well as its features and incompatibilities. * Menu: --- 57,64 ---- Introduction ************ ! This manual documents the use of `gfortran', the GNU Fortran compiler. ! You can find in this manual how to invoke `gfortran', as well as its features and incompatibilities. * Menu: *************** features and incompatibilities. *** 66,72 **** * Introduction:: Part I: Invoking GNU Fortran ! * Invoking GNU Fortran:: Command options supported by 'gfortran'. * Runtime:: Influencing runtime behavior with environment variables. Part II: Language Reference --- 66,72 ---- * Introduction:: Part I: Invoking GNU Fortran ! * Invoking GNU Fortran:: Command options supported by `gfortran'. * Runtime:: Influencing runtime behavior with environment variables. Part II: Language Reference *************** File: gfortran.info, Node: Introduction *** 94,100 **** ************** The GNU Fortran compiler front end was designed initially as a free ! replacement for, or alternative to, the Unix 'f95' command; 'gfortran' is the command you will use to invoke the compiler. * Menu: --- 94,100 ---- ************** The GNU Fortran compiler front end was designed initially as a free ! replacement for, or alternative to, the Unix `f95' command; `gfortran' is the command you will use to invoke the compiler. * Menu: *************** completely, parts of the Fortran 2003 an *** 117,190 **** several vendor extensions. The development goal is to provide the following features: ! * Read a user's program, stored in a file and containing instructions ! written in Fortran 77, Fortran 90, Fortran 95, Fortran 2003 or ! Fortran 2008. This file contains "source code". ! * Translate the user's program into instructions a computer can carry ! out more quickly than it takes to translate the instructions in the ! first place. The result after compilation of a program is "machine ! code", code designed to be efficiently translated and processed by ! a machine such as your computer. Humans usually are not as good ! writing machine code as they are at writing Fortran (or C++, Ada, ! or Java), because it is easy to make tiny mistakes writing machine ! code. * Provide the user with information about the reasons why the compiler is unable to create a binary from the source code. Usually this will be the case if the source code is flawed. The Fortran 90 standard requires that the compiler can point out ! mistakes to the user. An incorrect usage of the language causes an ! "error message". The compiler will also attempt to diagnose cases where the user's ! program contains a correct usage of the language, but instructs the ! computer to do something questionable. This kind of diagnostics ! message is called a "warning message". * Provide optional information about the translation passes from the source code to machine code. This can help a user of the compiler to find the cause of certain bugs which may not be obvious in the ! source code, but may be more easily found at a lower level compiler ! output. It also helps developers to find bugs in the compiler ! itself. * Provide information in the generated machine code that can make it easier to find bugs in the program (using a debugging tool, called ! a "debugger", such as the GNU Debugger 'gdb'). ! * Locate and gather machine code already generated to perform actions ! requested by statements in the user's program. This machine code ! is organized into "modules" and is located and "linked" to the user ! program. The GNU Fortran compiler consists of several components: ! * A version of the 'gcc' command (which also might be installed as ! the system's 'cc' command) that also understands and accepts ! Fortran source code. The 'gcc' command is the "driver" program for ! all the languages in the GNU Compiler Collection (GCC); With 'gcc', you can compile the source code of any language for which a front end is available in GCC. ! * The 'gfortran' command itself, which also might be installed as the ! system's 'f95' command. 'gfortran' is just another driver program, but specifically for the Fortran compiler only. The difference ! with 'gcc' is that 'gfortran' will automatically link the correct libraries to your program. * A collection of run-time libraries. These libraries contain the ! machine code needed to support capabilities of the Fortran language ! that are not directly provided by the machine code generated by the ! 'gfortran' compilation phase, such as intrinsic functions and ! subroutines, and routines for interaction with files and the ! operating system. ! * The Fortran compiler itself, ('f951'). This is the GNU Fortran parser and code generator, linked to and interfaced with the GCC ! backend library. 'f951' "translates" the source code to assembler code. You would typically not use this program directly; instead, ! the 'gcc' or 'gfortran' driver programs will call it for you.  File: gfortran.info, Node: GNU Fortran and GCC, Next: Preprocessing and conditional compilation, Prev: About GNU Fortran, Up: Introduction --- 117,190 ---- several vendor extensions. The development goal is to provide the following features: ! * Read a user's program, stored in a file and containing ! instructions written in Fortran 77, Fortran 90, Fortran 95, ! Fortran 2003 or Fortran 2008. This file contains "source code". ! * Translate the user's program into instructions a computer can ! carry out more quickly than it takes to translate the instructions ! in the first place. The result after compilation of a program is ! "machine code", code designed to be efficiently translated and ! processed by a machine such as your computer. Humans usually are ! not as good writing machine code as they are at writing Fortran ! (or C++, Ada, or Java), because it is easy to make tiny mistakes ! writing machine code. * Provide the user with information about the reasons why the compiler is unable to create a binary from the source code. Usually this will be the case if the source code is flawed. The Fortran 90 standard requires that the compiler can point out ! mistakes to the user. An incorrect usage of the language causes ! an "error message". The compiler will also attempt to diagnose cases where the user's ! program contains a correct usage of the language, but instructs ! the computer to do something questionable. This kind of ! diagnostics message is called a "warning message". * Provide optional information about the translation passes from the source code to machine code. This can help a user of the compiler to find the cause of certain bugs which may not be obvious in the ! source code, but may be more easily found at a lower level ! compiler output. It also helps developers to find bugs in the ! compiler itself. * Provide information in the generated machine code that can make it easier to find bugs in the program (using a debugging tool, called ! a "debugger", such as the GNU Debugger `gdb'). ! * Locate and gather machine code already generated to perform ! actions requested by statements in the user's program. This ! machine code is organized into "modules" and is located and ! "linked" to the user program. The GNU Fortran compiler consists of several components: ! * A version of the `gcc' command (which also might be installed as ! the system's `cc' command) that also understands and accepts ! Fortran source code. The `gcc' command is the "driver" program for ! all the languages in the GNU Compiler Collection (GCC); With `gcc', you can compile the source code of any language for which a front end is available in GCC. ! * The `gfortran' command itself, which also might be installed as the ! system's `f95' command. `gfortran' is just another driver program, but specifically for the Fortran compiler only. The difference ! with `gcc' is that `gfortran' will automatically link the correct libraries to your program. * A collection of run-time libraries. These libraries contain the ! machine code needed to support capabilities of the Fortran ! language that are not directly provided by the machine code ! generated by the `gfortran' compilation phase, such as intrinsic ! functions and subroutines, and routines for interaction with files ! and the operating system. ! * The Fortran compiler itself, (`f951'). This is the GNU Fortran parser and code generator, linked to and interfaced with the GCC ! backend library. `f951' "translates" the source code to assembler code. You would typically not use this program directly; instead, ! the `gcc' or `gfortran' driver programs will call it for you.  File: gfortran.info, Node: GNU Fortran and GCC, Next: Preprocessing and conditional compilation, Prev: About GNU Fortran, Up: Introduction *************** File: gfortran.info, Node: GNU Fortran *** 195,230 **** GNU Fortran is a part of GCC, the "GNU Compiler Collection". GCC consists of a collection of front ends for various languages, which translate the source code into a language-independent form called ! "GENERIC". This is then processed by a common middle end which provides ! optimization, and then passed to one of a collection of back ends which ! generate code for different computer architectures and operating ! systems. ! Functionally, this is implemented with a driver program ('gcc') which ! provides the command-line interface for the compiler. It calls the ! relevant compiler front-end program (e.g., 'f951' for Fortran) for each ! file in the source code, and then calls the assembler and linker as ! appropriate to produce the compiled output. In a copy of GCC which has ! been compiled with Fortran language support enabled, 'gcc' will ! recognize files with '.f', '.for', '.ftn', '.f90', '.f95', '.f03' and ! '.f08' extensions as Fortran source code, and compile it accordingly. A ! 'gfortran' driver program is also provided, which is identical to 'gcc' ! except that it automatically links the Fortran runtime libraries into ! the compiled program. ! Source files with '.f', '.for', '.fpp', '.ftn', '.F', '.FOR', '.FPP', ! and '.FTN' extensions are treated as fixed form. Source files with ! '.f90', '.f95', '.f03', '.f08', '.F90', '.F95', '.F03' and '.F08' ! extensions are treated as free form. The capitalized versions of either ! form are run through preprocessing. Source files with the lower case ! '.fpp' extension are also run through preprocessing. This manual specifically documents the Fortran front end, which ! handles the programming language's syntax and semantics. The aspects of ! GCC which relate to the optimization passes and the back-end code generation are documented in the GCC manual; see *note Introduction: ! (gcc)Top. The two manuals together provide a complete reference for the ! GNU Fortran compiler.  File: gfortran.info, Node: Preprocessing and conditional compilation, Next: GNU Fortran and G77, Prev: GNU Fortran and GCC, Up: Introduction --- 195,230 ---- GNU Fortran is a part of GCC, the "GNU Compiler Collection". GCC consists of a collection of front ends for various languages, which translate the source code into a language-independent form called ! "GENERIC". This is then processed by a common middle end which ! provides optimization, and then passed to one of a collection of back ! ends which generate code for different computer architectures and ! operating systems. ! Functionally, this is implemented with a driver program (`gcc') ! which provides the command-line interface for the compiler. It calls ! the relevant compiler front-end program (e.g., `f951' for Fortran) for ! each file in the source code, and then calls the assembler and linker ! as appropriate to produce the compiled output. In a copy of GCC which ! has been compiled with Fortran language support enabled, `gcc' will ! recognize files with `.f', `.for', `.ftn', `.f90', `.f95', `.f03' and ! `.f08' extensions as Fortran source code, and compile it accordingly. ! A `gfortran' driver program is also provided, which is identical to ! `gcc' except that it automatically links the Fortran runtime libraries ! into the compiled program. ! Source files with `.f', `.for', `.fpp', `.ftn', `.F', `.FOR', ! `.FPP', and `.FTN' extensions are treated as fixed form. Source files ! with `.f90', `.f95', `.f03', `.f08', `.F90', `.F95', `.F03' and `.F08' ! extensions are treated as free form. The capitalized versions of ! either form are run through preprocessing. Source files with the lower ! case `.fpp' extension are also run through preprocessing. This manual specifically documents the Fortran front end, which ! handles the programming language's syntax and semantics. The aspects ! of GCC which relate to the optimization passes and the back-end code generation are documented in the GCC manual; see *note Introduction: ! (gcc)Top. The two manuals together provide a complete reference for ! the GNU Fortran compiler.  File: gfortran.info, Node: Preprocessing and conditional compilation, Next: GNU Fortran and G77, Prev: GNU Fortran and GCC, Up: Introduction *************** File: gfortran.info, Node: Preprocessin *** 234,262 **** Many Fortran compilers including GNU Fortran allow passing the source code through a C preprocessor (CPP; sometimes also called the Fortran ! preprocessor, FPP) to allow for conditional compilation. In the case of ! GNU Fortran, this is the GNU C Preprocessor in the traditional mode. On ! systems with case-preserving file names, the preprocessor is ! automatically invoked if the filename extension is '.F', '.FOR', '.FTN', ! '.fpp', '.FPP', '.F90', '.F95', '.F03' or '.F08'. To manually invoke ! the preprocessor on any file, use '-cpp', to disable preprocessing on ! files where the preprocessor is run automatically, use '-nocpp'. If a preprocessed file includes another file with the Fortran ! 'INCLUDE' statement, the included file is not preprocessed. To preprocess included files, use the equivalent preprocessor statement ! '#include'. ! If GNU Fortran invokes the preprocessor, '__GFORTRAN__' is defined ! and '__GNUC__', '__GNUC_MINOR__' and '__GNUC_PATCHLEVEL__' can be used ! to determine the version of the compiler. See *note Overview: (cpp)Top. ! for details. While CPP is the de-facto standard for preprocessing Fortran code, Part 3 of the Fortran 95 standard (ISO/IEC 1539-3:1998) defines Conditional Compilation, which is not widely used and not directly supported by the GNU Fortran compiler. You can use the program coco to ! preprocess such files ().  File: gfortran.info, Node: GNU Fortran and G77, Next: Project Status, Prev: Preprocessing and conditional compilation, Up: Introduction --- 234,263 ---- Many Fortran compilers including GNU Fortran allow passing the source code through a C preprocessor (CPP; sometimes also called the Fortran ! preprocessor, FPP) to allow for conditional compilation. In the case ! of GNU Fortran, this is the GNU C Preprocessor in the traditional mode. ! On systems with case-preserving file names, the preprocessor is ! automatically invoked if the filename extension is `.F', `.FOR', ! `.FTN', `.fpp', `.FPP', `.F90', `.F95', `.F03' or `.F08'. To manually ! invoke the preprocessor on any file, use `-cpp', to disable ! preprocessing on files where the preprocessor is run automatically, use ! `-nocpp'. If a preprocessed file includes another file with the Fortran ! `INCLUDE' statement, the included file is not preprocessed. To preprocess included files, use the equivalent preprocessor statement ! `#include'. ! If GNU Fortran invokes the preprocessor, `__GFORTRAN__' is defined ! and `__GNUC__', `__GNUC_MINOR__' and `__GNUC_PATCHLEVEL__' can be used ! to determine the version of the compiler. See *note Overview: ! (cpp)Top. for details. While CPP is the de-facto standard for preprocessing Fortran code, Part 3 of the Fortran 95 standard (ISO/IEC 1539-3:1998) defines Conditional Compilation, which is not widely used and not directly supported by the GNU Fortran compiler. You can use the program coco to ! preprocess such files (`http://www.daniellnagle.com/coco.html').  File: gfortran.info, Node: GNU Fortran and G77, Next: Project Status, Prev: Preprocessing and conditional compilation, Up: Introduction *************** File: gfortran.info, Node: GNU Fortran *** 264,275 **** 1.4 GNU Fortran and G77 ======================= ! The GNU Fortran compiler is the successor to 'g77', the Fortran 77 front ! end included in GCC prior to version 4. It is an entirely new program ! that has been designed to provide Fortran 95 support and extensibility ! for future Fortran language standards, as well as providing backwards ! compatibility for Fortran 77 and nearly all of the GNU language ! extensions supported by 'g77'.  File: gfortran.info, Node: Project Status, Next: Standards, Prev: GNU Fortran and G77, Up: Introduction --- 265,276 ---- 1.4 GNU Fortran and G77 ======================= ! The GNU Fortran compiler is the successor to `g77', the Fortran 77 ! front end included in GCC prior to version 4. It is an entirely new ! program that has been designed to provide Fortran 95 support and ! extensibility for future Fortran language standards, as well as ! providing backwards compatibility for Fortran 77 and nearly all of the ! GNU language extensions supported by `g77'.  File: gfortran.info, Node: Project Status, Next: Standards, Prev: GNU Fortran and G77, Up: Introduction *************** File: gfortran.info, Node: Project Stat *** 277,292 **** 1.5 Project Status ================== ! As soon as 'gfortran' can parse all of the statements correctly, it ! will be in the "larva" state. When we generate code, the "puppa" ! state. When 'gfortran' is done, we'll see if it will be a beautiful butterfly, or just a big bug.... -Andy Vaught, April 2000 The start of the GNU Fortran 95 project was announced on the GCC ! homepage in March 18, 2000 (even though Andy had already been working on ! it for a while, of course). The GNU Fortran compiler is able to compile nearly all standard-compliant Fortran 95, Fortran 90, and Fortran 77 programs, --- 278,293 ---- 1.5 Project Status ================== ! As soon as `gfortran' can parse all of the statements correctly, ! it will be in the "larva" state. When we generate code, the ! "puppa" state. When `gfortran' is done, we'll see if it will be a beautiful butterfly, or just a big bug.... -Andy Vaught, April 2000 The start of the GNU Fortran 95 project was announced on the GCC ! homepage in March 18, 2000 (even though Andy had already been working ! on it for a while, of course). The GNU Fortran compiler is able to compile nearly all standard-compliant Fortran 95, Fortran 90, and Fortran 77 programs, *************** used on real-world programs. In particu *** 295,303 **** include OpenMP, Cray-style pointers, some old vendor extensions, and several Fortran 2003 and Fortran 2008 features, including TR 15581. However, it is still under development and has a few remaining rough ! edges. There also is initial support for OpenACC. Note that this is an ! experimental feature, incomplete, and subject to change in future ! versions of GCC. See for more information. At present, the GNU Fortran compiler passes the NIST Fortran 77 Test --- 296,304 ---- include OpenMP, Cray-style pointers, some old vendor extensions, and several Fortran 2003 and Fortran 2008 features, including TR 15581. However, it is still under development and has a few remaining rough ! edges. There also is initial support for OpenACC. Note that this is ! an experimental feature, incomplete, and subject to change in future ! versions of GCC. See `https://gcc.gnu.org/wiki/OpenACC' for more information. At present, the GNU Fortran compiler passes the NIST Fortran 77 Test *************** compile a number of large real-world pro *** 312,323 **** and HIRLAM weather forecasting code (http://hirlam.org/) and the Tonto quantum chemistry package (http://physical-chemistry.scb.uwa.edu.au/tonto/wiki/index.php/Main_Page); ! see for an extended list. Among other things, the GNU Fortran compiler is intended as a replacement for G77. At this point, nearly all programs that could be ! compiled with G77 can be compiled with GNU Fortran, although there are a ! few minor known regressions. The primary work remaining to be done on GNU Fortran falls into three categories: bug fixing (primarily regarding the treatment of invalid --- 313,324 ---- and HIRLAM weather forecasting code (http://hirlam.org/) and the Tonto quantum chemistry package (http://physical-chemistry.scb.uwa.edu.au/tonto/wiki/index.php/Main_Page); ! see `https://gcc.gnu.org/wiki/GfortranApps' for an extended list. Among other things, the GNU Fortran compiler is intended as a replacement for G77. At this point, nearly all programs that could be ! compiled with G77 can be compiled with GNU Fortran, although there are ! a few minor known regressions. The primary work remaining to be done on GNU Fortran falls into three categories: bug fixing (primarily regarding the treatment of invalid *************** File: gfortran.info, Node: Standards, *** 336,362 **** * Varying Length Character Strings:: ! The GNU Fortran compiler implements ISO/IEC 1539:1997 (Fortran 95). As ! such, it can also compile essentially all standard-compliant Fortran 90 ! and Fortran 77 programs. It also supports the ISO/IEC TR-15581 enhancements to allocatable arrays. GNU Fortran also have a partial support for ISO/IEC 1539-1:2004 (Fortran 2003), ISO/IEC 1539-1:2010 (Fortran 2008), the Technical ! Specification 'Further Interoperability of Fortran with C' (ISO/IEC TS 29113:2012). Full support of those standards and future Fortran ! standards is planned. The current status of the support is can be found ! in the *note Fortran 2003 status::, *note Fortran 2008 status::, *note ! TS 29113 status:: and *note TS 18508 status:: sections of the documentation. Additionally, the GNU Fortran compilers supports the OpenMP specification (version 4.0, ! ). There also is initial support for the OpenACC specification (targeting version 2.0, ! ). Note that this is an experimental feature, ! incomplete, and subject to change in future versions of GCC. See ! for more information.  File: gfortran.info, Node: Varying Length Character Strings, Up: Standards --- 337,363 ---- * Varying Length Character Strings:: ! The GNU Fortran compiler implements ISO/IEC 1539:1997 (Fortran 95). ! As such, it can also compile essentially all standard-compliant Fortran ! 90 and Fortran 77 programs. It also supports the ISO/IEC TR-15581 enhancements to allocatable arrays. GNU Fortran also have a partial support for ISO/IEC 1539-1:2004 (Fortran 2003), ISO/IEC 1539-1:2010 (Fortran 2008), the Technical ! Specification `Further Interoperability of Fortran with C' (ISO/IEC TS 29113:2012). Full support of those standards and future Fortran ! standards is planned. The current status of the support is can be ! found in the *note Fortran 2003 status::, *note Fortran 2008 status::, ! *note TS 29113 status:: and *note TS 18508 status:: sections of the documentation. Additionally, the GNU Fortran compilers supports the OpenMP specification (version 4.0, ! `http://openmp.org/wp/openmp-specifications/'). There also is initial support for the OpenACC specification (targeting version 2.0, ! `http://www.openacc.org/'). Note that this is an experimental feature, ! incomplete, and subject to change in future versions of GCC. See ! `https://gcc.gnu.org/wiki/OpenACC' for more information.  File: gfortran.info, Node: Varying Length Character Strings, Up: Standards *************** The Fortran 95 standard specifies in Par *** 368,380 **** varying length character strings. While GNU Fortran currently does not support such strings directly, there exist two Fortran implementations for them, which work with GNU Fortran. They can be found at ! and at ! . Deferred-length character strings of Fortran 2003 supports part of ! the features of 'ISO_VARYING_STRING' and should be considered as ! replacement. (Namely, allocatable or pointers of the type ! 'character(len=:)'.)  File: gfortran.info, Node: Invoking GNU Fortran, Next: Runtime, Prev: Introduction, Up: Top --- 369,381 ---- varying length character strings. While GNU Fortran currently does not support such strings directly, there exist two Fortran implementations for them, which work with GNU Fortran. They can be found at ! `http://www.fortran.com/iso_varying_string.f95' and at ! `ftp://ftp.nag.co.uk/sc22wg5/ISO_VARYING_STRING/'. Deferred-length character strings of Fortran 2003 supports part of ! the features of `ISO_VARYING_STRING' and should be considered as ! replacement. (Namely, allocatable or pointers of the type ! `character(len=:)'.)  File: gfortran.info, Node: Invoking GNU Fortran, Next: Runtime, Prev: Introduction, Up: Top *************** File: gfortran.info, Node: Invoking GNU *** 382,406 **** 2 GNU Fortran Command Options ***************************** ! The 'gfortran' command supports all the options supported by the 'gcc' command. Only options specific to GNU Fortran are documented here. *Note GCC Command Options: (gcc)Invoking GCC, for information on the ! non-Fortran-specific aspects of the 'gcc' command (and, therefore, the ! 'gfortran' command). ! All GCC and GNU Fortran options are accepted both by 'gfortran' and ! by 'gcc' (as well as any other drivers built at the same time, such as ! 'g++'), since adding GNU Fortran to the GCC distribution enables acceptance of GNU Fortran options by all of the relevant drivers. ! In some cases, options have positive and negative forms; the negative ! form of '-ffoo' would be '-fno-foo'. This manual documents only one of ! these two forms, whichever one is not the default. * Menu: ! * Option Summary:: Brief list of all 'gfortran' options, without explanations. * Fortran Dialect Options:: Controlling the variant of Fortran language compiled. --- 383,407 ---- 2 GNU Fortran Command Options ***************************** ! The `gfortran' command supports all the options supported by the `gcc' command. Only options specific to GNU Fortran are documented here. *Note GCC Command Options: (gcc)Invoking GCC, for information on the ! non-Fortran-specific aspects of the `gcc' command (and, therefore, the ! `gfortran' command). ! All GCC and GNU Fortran options are accepted both by `gfortran' and ! by `gcc' (as well as any other drivers built at the same time, such as ! `g++'), since adding GNU Fortran to the GCC distribution enables acceptance of GNU Fortran options by all of the relevant drivers. ! In some cases, options have positive and negative forms; the ! negative form of `-ffoo' would be `-fno-foo'. This manual documents ! only one of these two forms, whichever one is not the default. * Menu: ! * Option Summary:: Brief list of all `gfortran' options, without explanations. * Fortran Dialect Options:: Controlling the variant of Fortran language compiled. *************** these two forms, whichever one is not th *** 412,418 **** * Runtime Options:: Influencing runtime behavior * Code Gen Options:: Specifying conventions for function calls, data layout and register usage. ! * Environment Variables:: Environment variables that affect 'gfortran'.  File: gfortran.info, Node: Option Summary, Next: Fortran Dialect Options, Up: Invoking GNU Fortran --- 413,419 ---- * Runtime Options:: Influencing runtime behavior * Code Gen Options:: Specifying conventions for function calls, data layout and register usage. ! * Environment Variables:: Environment variables that affect `gfortran'.  File: gfortran.info, Node: Option Summary, Next: Fortran Dialect Options, Up: Invoking GNU Fortran *************** File: gfortran.info, Node: Option Summa *** 420,427 **** 2.1 Option summary ================== ! Here is a summary of all the options specific to GNU Fortran, grouped by ! type. Explanations are in the following sections. _Fortran Language Options_ *Note Options controlling Fortran dialect: Fortran Dialect Options. --- 421,428 ---- 2.1 Option summary ================== ! Here is a summary of all the options specific to GNU Fortran, grouped ! by type. Explanations are in the following sections. _Fortran Language Options_ *Note Options controlling Fortran dialect: Fortran Dialect Options. *************** _Fortran Language Options_ *** 435,441 **** -fopenacc -fopenmp -freal-4-real-10 -freal-4-real-16 -freal-4-real-8 -freal-8-real-10 -freal-8-real-16 -freal-8-real-4 -std=STD - _Preprocessing Options_ *Note Enable and customize preprocessing: Preprocessing Options. -A-QUESTION[=ANSWER] --- 436,441 ---- *************** _Preprocessing Options_ *** 447,456 **** -nostdinc -undef - _Error and Warning Options_ ! *Note Options to request or suppress errors and warnings: Error and ! Warning Options. -Waliasing -Wall -Wampersand -Warray-bounds -Wc-binding-type -Wcharacter-truncation -Wconversion -Wfunction-elimination -Wimplicit-interface --- 447,455 ---- -nostdinc -undef _Error and Warning Options_ ! *Note Options to request or suppress errors and warnings: Error ! and Warning Options. -Waliasing -Wall -Wampersand -Warray-bounds -Wc-binding-type -Wcharacter-truncation -Wconversion -Wfunction-elimination -Wimplicit-interface *************** _Error and Warning Options_ *** 459,472 **** -Wsurprising -Wunderflow -Wunused-parameter -Wrealloc-lhs -Wrealloc-lhs-all -Wtarget-lifetime -fmax-errors=N -fsyntax-only -pedantic -pedantic-errors - _Debugging Options_ *Note Options for debugging your program or GNU Fortran: Debugging Options. -fbacktrace -fdump-fortran-optimized -fdump-fortran-original -fdump-parse-tree -ffpe-trap=LIST -ffpe-summary=LIST - _Directory Options_ *Note Options for directory search: Directory Options. -IDIR -JDIR -fintrinsic-modules-path DIR --- 458,469 ---- *************** _Runtime Options_ *** 480,486 **** -fconvert=CONVERSION -fmax-subrecord-length=LENGTH -frecord-marker=LENGTH -fsign-zero - _Code Generation Options_ *Note Options for code generation conventions: Code Gen Options. -faggressive-function-elimination -fblas-matmul-limit=N --- 477,482 ---- *************** File: gfortran.info, Node: Fortran Dial *** 508,707 **** The following options control the details of the Fortran dialect accepted by the compiler: ! '-ffree-form' ! '-ffixed-form' Specify the layout used by the source file. The free form layout was introduced in Fortran 90. Fixed form was traditionally used in older Fortran programs. When neither option is specified, the source form is determined by the file extension. ! '-fall-intrinsics' This option causes all intrinsic procedures (including the GNU-specific extensions) to be accepted. This can be useful with ! '-std=f95' to force standard-compliance but get access to the full ! range of intrinsics available with 'gfortran'. As a consequence, ! '-Wintrinsics-std' will be ignored and no user-defined procedure with the same name as any intrinsic will be called except when it ! is explicitly declared 'EXTERNAL'. ! '-fd-lines-as-code' ! '-fd-lines-as-comments' ! Enable special treatment for lines beginning with 'd' or 'D' in ! fixed form sources. If the '-fd-lines-as-code' option is given they are treated as if the first column contained a blank. If the ! '-fd-lines-as-comments' option is given, they are treated as comment lines. ! '-fdec' ! DEC compatibility mode. Enables extensions and other features that ! mimic the default behavior of older compilers (such as DEC). These ! features are non-standard and should be avoided at all costs. For ! details on GNU Fortran's implementation of these extensions see the ! full documentation. ! Other flags enabled by this switch are: '-fdollar-ok' ! '-fcray-pointer' '-fdec-structure' ! '-fdec-structure' ! Enable DEC 'STRUCTURE' and 'RECORD' as well as 'UNION', 'MAP', and ! dot ('.') as a member separator (in addition to '%'). This is ! provided for compatibility only; Fortran 90 derived types should be ! used instead where possible. ! '-fdollar-ok' ! Allow '$' as a valid non-first character in a symbol name. Symbols ! that start with '$' are rejected since it is unclear which rules to apply to implicit typing as different vendors implement different ! rules. Using '$' in 'IMPLICIT' statements is also rejected. ! '-fbackslash' Change the interpretation of backslashes in string literals from a ! single backslash character to "C-style" escape characters. The ! following combinations are expanded '\a', '\b', '\f', '\n', '\r', ! '\t', '\v', '\\', and '\0' to the ASCII characters alert, backspace, form feed, newline, carriage return, horizontal tab, vertical tab, backslash, and NUL, respectively. Additionally, ! '\x'NN, '\u'NNNN and '\U'NNNNNNNN (where each N is a hexadecimal digit) are translated into the Unicode characters corresponding to ! the specified code points. All other combinations of a character preceded by \ are unexpanded. ! '-fmodule-private' ! Set the default accessibility of module entities to 'PRIVATE'. Use-associated entities will not be accessible unless they are ! explicitly declared as 'PUBLIC'. ! '-ffixed-line-length-N' Set column after which characters are ignored in typical fixed-form lines in the source file, and through which spaces are assumed (as if padded to that length) after the ends of short fixed-form lines. Popular values for N include 72 (the standard and the default), 80 (card image), and 132 (corresponding to "extended-source" options ! in some popular compilers). N may also be 'none', meaning that the ! entire line is meaningful and that continued character constants ! never have implicit spaces appended to them to fill out the line. ! '-ffixed-line-length-0' means the same thing as ! '-ffixed-line-length-none'. ! '-ffree-line-length-N' Set column after which characters are ignored in typical free-form ! lines in the source file. The default value is 132. N may be ! 'none', meaning that the entire line is meaningful. ! '-ffree-line-length-0' means the same thing as ! '-ffree-line-length-none'. ! '-fmax-identifier-length=N' ! Specify the maximum allowed identifier length. Typical values are 31 (Fortran 95) and 63 (Fortran 2003 and Fortran 2008). ! '-fimplicit-none' Specify that no implicit typing is allowed, unless overridden by ! explicit 'IMPLICIT' statements. This is the equivalent of adding ! 'implicit none' to the start of every procedure. ! '-fcray-pointer' Enable the Cray pointer extension, which provides C-like pointer functionality. ! '-fopenacc' ! Enable the OpenACC extensions. This includes OpenACC '!$acc' ! directives in free form and 'c$acc', '*$acc' and '!$acc' directives ! in fixed form, '!$' conditional compilation sentinels in free form ! and 'c$', '*$' and '!$' sentinels in fixed form, and when linking ! arranges for the OpenACC runtime library to be linked in. Note that this is an experimental feature, incomplete, and subject ! to change in future versions of GCC. See ! for more information. ! '-fopenmp' ! Enable the OpenMP extensions. This includes OpenMP '!$omp' ! directives in free form and 'c$omp', '*$omp' and '!$omp' directives ! in fixed form, '!$' conditional compilation sentinels in free form ! and 'c$', '*$' and '!$' sentinels in fixed form, and when linking ! arranges for the OpenMP runtime library to be linked in. The ! option '-fopenmp' implies '-frecursive'. ! '-fno-range-check' Disable range checking on results of simplification of constant expressions during compilation. For example, GNU Fortran will give ! an error at compile time when simplifying 'a = 1. / 0'. With this ! option, no error will be given and 'a' will be assigned the value ! '+Infinity'. If an expression evaluates to a value outside of the ! relevant range of ['-HUGE()':'HUGE()'], then the expression will be ! replaced by '-Inf' or '+Inf' as appropriate. Similarly, 'DATA ! i/Z'FFFFFFFF'/' will result in an integer overflow on most systems, ! but with '-fno-range-check' the value will "wrap around" and 'i' ! will be initialized to -1 instead. ! '-fdefault-integer-8' Set the default integer and logical types to an 8 byte wide type. ! This option also affects the kind of integer constants like '42'. ! Unlike '-finteger-4-integer-8', it does not promote variables with explicit kind declaration. ! '-fdefault-real-8' ! Set the default real type to an 8 byte wide type. This option also ! affects the kind of non-double real constants like '1.0', and does ! promote the default width of 'DOUBLE PRECISION' to 16 bytes if ! possible, unless '-fdefault-double-8' is given, too. Unlike ! '-freal-4-real-8', it does not promote variables with explicit kind ! declaration. ! '-fdefault-double-8' ! Set the 'DOUBLE PRECISION' type to an 8 byte wide type. Do nothing ! if this is already the default. If '-fdefault-real-8' is given, ! 'DOUBLE PRECISION' would instead be promoted to 16 bytes if ! possible, and '-fdefault-double-8' can be used to prevent this. ! The kind of real constants like '1.d0' will not be changed by ! '-fdefault-real-8' though, so also '-fdefault-double-8' does not affect it. ! '-finteger-4-integer-8' ! Promote all 'INTEGER(KIND=4)' entities to an 'INTEGER(KIND=8)' ! entities. If 'KIND=8' is unavailable, then an error will be issued. This option should be used with care and may not be suitable for your codes. Areas of possible concern include calls ! to external procedures, alignment in 'EQUIVALENCE' and/or 'COMMON', ! generic interfaces, BOZ literal constant conversion, and I/O. ! Inspection of the intermediate representation of the translated ! Fortran code, produced by '-fdump-tree-original', is suggested. ! '-freal-4-real-8' ! '-freal-4-real-10' ! '-freal-4-real-16' ! '-freal-8-real-4' ! '-freal-8-real-10' ! '-freal-8-real-16' ! Promote all 'REAL(KIND=M)' entities to 'REAL(KIND=N)' entities. If ! 'REAL(KIND=N)' is unavailable, then an error will be issued. All ! other real kind types are unaffected by this option. These options ! should be used with care and may not be suitable for your codes. ! Areas of possible concern include calls to external procedures, ! alignment in 'EQUIVALENCE' and/or 'COMMON', generic interfaces, BOZ ! literal constant conversion, and I/O. Inspection of the ! intermediate representation of the translated Fortran code, ! produced by '-fdump-tree-original', is suggested. ! '-std=STD' Specify the standard to which the program is expected to conform, ! which may be one of 'f95', 'f2003', 'f2008', 'gnu', or 'legacy'. ! The default value for STD is 'gnu', which specifies a superset of the Fortran 95 standard that includes all of the extensions supported by GNU Fortran, although warnings will be given for obsolete extensions not recommended for use in new code. The ! 'legacy' value is equivalent but without the warnings for obsolete extensions, and may be useful for old non-standard programs. The ! 'f95', 'f2003' and 'f2008' values specify strict conformance to the ! Fortran 95, Fortran 2003 and Fortran 2008 standards, respectively; ! errors are given for all extensions beyond the relevant language ! standard, and warnings are given for the Fortran 77 features that ! are permitted but obsolescent in later standards. '-std=f2008ts' ! allows the Fortran 2008 standard including the additions of the ! Technical Specification (TS) 29113 on Further Interoperability of ! Fortran with C and TS 18508 on Additional Parallel Features in ! Fortran.  File: gfortran.info, Node: Preprocessing Options, Next: Error and Warning Options, Prev: Fortran Dialect Options, Up: Invoking GNU Fortran --- 504,706 ---- The following options control the details of the Fortran dialect accepted by the compiler: ! `-ffree-form' ! `-ffixed-form' Specify the layout used by the source file. The free form layout was introduced in Fortran 90. Fixed form was traditionally used in older Fortran programs. When neither option is specified, the source form is determined by the file extension. ! `-fall-intrinsics' This option causes all intrinsic procedures (including the GNU-specific extensions) to be accepted. This can be useful with ! `-std=f95' to force standard-compliance but get access to the full ! range of intrinsics available with `gfortran'. As a consequence, ! `-Wintrinsics-std' will be ignored and no user-defined procedure with the same name as any intrinsic will be called except when it ! is explicitly declared `EXTERNAL'. ! `-fd-lines-as-code' ! `-fd-lines-as-comments' ! Enable special treatment for lines beginning with `d' or `D' in ! fixed form sources. If the `-fd-lines-as-code' option is given they are treated as if the first column contained a blank. If the ! `-fd-lines-as-comments' option is given, they are treated as comment lines. ! `-fdec' ! DEC compatibility mode. Enables extensions and other features that ! mimic the default behavior of older compilers (such as DEC). ! These features are non-standard and should be avoided at all costs. ! For details on GNU Fortran's implementation of these extensions ! see the full documentation. ! Other flags enabled by this switch are: `-fdollar-ok' ! `-fcray-pointer' `-fdec-structure' ! `-fdec-structure' ! Enable DEC `STRUCTURE' and `RECORD' as well as `UNION', `MAP', and ! dot ('.') as a member separator (in addition to '%'). This is ! provided for compatibility only; Fortran 90 derived types should ! be used instead where possible. ! `-fdollar-ok' ! Allow `$' as a valid non-first character in a symbol name. Symbols ! that start with `$' are rejected since it is unclear which rules to apply to implicit typing as different vendors implement different ! rules. Using `$' in `IMPLICIT' statements is also rejected. ! `-fbackslash' Change the interpretation of backslashes in string literals from a ! single backslash character to "C-style" escape characters. The ! following combinations are expanded `\a', `\b', `\f', `\n', `\r', ! `\t', `\v', `\\', and `\0' to the ASCII characters alert, backspace, form feed, newline, carriage return, horizontal tab, vertical tab, backslash, and NUL, respectively. Additionally, ! `\x'NN, `\u'NNNN and `\U'NNNNNNNN (where each N is a hexadecimal digit) are translated into the Unicode characters corresponding to ! the specified code points. All other combinations of a character preceded by \ are unexpanded. ! `-fmodule-private' ! Set the default accessibility of module entities to `PRIVATE'. Use-associated entities will not be accessible unless they are ! explicitly declared as `PUBLIC'. ! `-ffixed-line-length-N' Set column after which characters are ignored in typical fixed-form lines in the source file, and through which spaces are assumed (as if padded to that length) after the ends of short fixed-form lines. Popular values for N include 72 (the standard and the default), 80 (card image), and 132 (corresponding to "extended-source" options ! in some popular compilers). N may also be `none', meaning that ! the entire line is meaningful and that continued character ! constants never have implicit spaces appended to them to fill out ! the line. `-ffixed-line-length-0' means the same thing as ! `-ffixed-line-length-none'. ! `-ffree-line-length-N' Set column after which characters are ignored in typical free-form ! lines in the source file. The default value is 132. N may be ! `none', meaning that the entire line is meaningful. ! `-ffree-line-length-0' means the same thing as ! `-ffree-line-length-none'. ! `-fmax-identifier-length=N' ! Specify the maximum allowed identifier length. Typical values are 31 (Fortran 95) and 63 (Fortran 2003 and Fortran 2008). ! `-fimplicit-none' Specify that no implicit typing is allowed, unless overridden by ! explicit `IMPLICIT' statements. This is the equivalent of adding ! `implicit none' to the start of every procedure. ! `-fcray-pointer' Enable the Cray pointer extension, which provides C-like pointer functionality. ! `-fopenacc' ! Enable the OpenACC extensions. This includes OpenACC `!$acc' ! directives in free form and `c$acc', `*$acc' and `!$acc' ! directives in fixed form, `!$' conditional compilation sentinels ! in free form and `c$', `*$' and `!$' sentinels in fixed form, and ! when linking arranges for the OpenACC runtime library to be linked ! in. Note that this is an experimental feature, incomplete, and subject ! to change in future versions of GCC. See ! `https://gcc.gnu.org/wiki/OpenACC' for more information. ! `-fopenmp' ! Enable the OpenMP extensions. This includes OpenMP `!$omp' ! directives in free form and `c$omp', `*$omp' and `!$omp' ! directives in fixed form, `!$' conditional compilation sentinels ! in free form and `c$', `*$' and `!$' sentinels in fixed form, and ! when linking arranges for the OpenMP runtime library to be linked ! in. The option `-fopenmp' implies `-frecursive'. ! `-fno-range-check' Disable range checking on results of simplification of constant expressions during compilation. For example, GNU Fortran will give ! an error at compile time when simplifying `a = 1. / 0'. With this ! option, no error will be given and `a' will be assigned the value ! `+Infinity'. If an expression evaluates to a value outside of the ! relevant range of [`-HUGE()':`HUGE()'], then the expression will ! be replaced by `-Inf' or `+Inf' as appropriate. Similarly, `DATA ! i/Z'FFFFFFFF'/' will result in an integer overflow on most ! systems, but with `-fno-range-check' the value will "wrap around" ! and `i' will be initialized to -1 instead. ! `-fdefault-integer-8' Set the default integer and logical types to an 8 byte wide type. ! This option also affects the kind of integer constants like `42'. ! Unlike `-finteger-4-integer-8', it does not promote variables with explicit kind declaration. ! `-fdefault-real-8' ! Set the default real type to an 8 byte wide type. This option also ! affects the kind of non-double real constants like `1.0', and does ! promote the default width of `DOUBLE PRECISION' to 16 bytes if ! possible, unless `-fdefault-double-8' is given, too. Unlike ! `-freal-4-real-8', it does not promote variables with explicit ! kind declaration. ! `-fdefault-double-8' ! Set the `DOUBLE PRECISION' type to an 8 byte wide type. Do ! nothing if this is already the default. If `-fdefault-real-8' is ! given, `DOUBLE PRECISION' would instead be promoted to 16 bytes if ! possible, and `-fdefault-double-8' can be used to prevent this. ! The kind of real constants like `1.d0' will not be changed by ! `-fdefault-real-8' though, so also `-fdefault-double-8' does not affect it. ! `-finteger-4-integer-8' ! Promote all `INTEGER(KIND=4)' entities to an `INTEGER(KIND=8)' ! entities. If `KIND=8' is unavailable, then an error will be issued. This option should be used with care and may not be suitable for your codes. Areas of possible concern include calls ! to external procedures, alignment in `EQUIVALENCE' and/or ! `COMMON', generic interfaces, BOZ literal constant conversion, and ! I/O. Inspection of the intermediate representation of the ! translated Fortran code, produced by `-fdump-tree-original', is ! suggested. ! `-freal-4-real-8' ! `-freal-4-real-10' ! `-freal-4-real-16' ! `-freal-8-real-4' ! `-freal-8-real-10' ! `-freal-8-real-16' ! Promote all `REAL(KIND=M)' entities to `REAL(KIND=N)' entities. ! If `REAL(KIND=N)' is unavailable, then an error will be issued. ! All other real kind types are unaffected by this option. These ! options should be used with care and may not be suitable for your ! codes. Areas of possible concern include calls to external ! procedures, alignment in `EQUIVALENCE' and/or `COMMON', generic ! interfaces, BOZ literal constant conversion, and I/O. Inspection ! of the intermediate representation of the translated Fortran code, ! produced by `-fdump-tree-original', is suggested. ! `-std=STD' Specify the standard to which the program is expected to conform, ! which may be one of `f95', `f2003', `f2008', `gnu', or `legacy'. ! The default value for STD is `gnu', which specifies a superset of the Fortran 95 standard that includes all of the extensions supported by GNU Fortran, although warnings will be given for obsolete extensions not recommended for use in new code. The ! `legacy' value is equivalent but without the warnings for obsolete extensions, and may be useful for old non-standard programs. The ! `f95', `f2003' and `f2008' values specify strict conformance to ! the Fortran 95, Fortran 2003 and Fortran 2008 standards, ! respectively; errors are given for all extensions beyond the ! relevant language standard, and warnings are given for the Fortran ! 77 features that are permitted but obsolescent in later standards. ! `-std=f2008ts' allows the Fortran 2008 standard including the ! additions of the Technical Specification (TS) 29113 on Further ! Interoperability of Fortran with C and TS 18508 on Additional ! Parallel Features in Fortran. !  File: gfortran.info, Node: Preprocessing Options, Next: Error and Warning Options, Prev: Fortran Dialect Options, Up: Invoking GNU Fortran *************** File: gfortran.info, Node: Preprocessin *** 709,864 **** 2.3 Enable and customize preprocessing ====================================== ! Preprocessor related options. See section *note Preprocessing and ! conditional compilation:: for more detailed information on preprocessing ! in 'gfortran'. ! '-cpp' ! '-nocpp' ! Enable preprocessing. The preprocessor is automatically invoked if ! the file extension is '.fpp', '.FPP', '.F', '.FOR', '.FTN', '.F90', ! '.F95', '.F03' or '.F08'. Use this option to manually enable ! preprocessing of any kind of Fortran file. To disable preprocessing of files with any of the above listed ! extensions, use the negative form: '-nocpp'. ! The preprocessor is run in traditional mode. Any restrictions of the file-format, especially the limits on line length, apply for preprocessed output as well, so it might be advisable to use the ! '-ffree-line-length-none' or '-ffixed-line-length-none' options. ! '-dM' ! Instead of the normal output, generate a list of ''#define'' directives for all the macros defined during the execution of the ! preprocessor, including predefined macros. This gives you a way of finding out what is predefined in your version of the preprocessor. ! Assuming you have no file 'foo.f90', the command touch foo.f90; gfortran -cpp -E -dM foo.f90 will show all the predefined macros. ! '-dD' ! Like '-dM' except in two respects: it does not include the ! predefined macros, and it outputs both the '#define' directives and ! the result of preprocessing. Both kinds of output go to the standard output file. ! '-dN' ! Like '-dD', but emit only the macro names, not their expansions. ! '-dU' ! Like 'dD' except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and ! ''#undef'' directives are also output for macros tested but undefined at the time. ! '-dI' ! Output ''#include'' directives in addition to the result of preprocessing. ! '-fworking-directory' Enable generation of linemarkers in the preprocessor output that will let the compiler know the current working directory at the ! time of preprocessing. When this option is enabled, the preprocessor will emit, after the initial linemarker, a second linemarker with the current working directory followed by two ! slashes. GCC will use this directory, when it is present in the ! preprocessed input, as the directory emitted as the current working ! directory in some debugging information formats. This option is ! implicitly enabled if debugging information is enabled, but this ! can be inhibited with the negated form '-fno-working-directory'. ! If the '-P' flag is present in the command line, this option has no ! effect, since no '#line' directives are emitted whatsoever. ! '-idirafter DIR' Search DIR for include files, but do it after all directories ! specified with '-I' and the standard system directories have been ! exhausted. DIR is treated as a system include directory. If dir ! begins with '=', then the '=' will be replaced by the sysroot ! prefix; see '--sysroot' and '-isysroot'. ! '-imultilib DIR' Use DIR as a subdirectory of the directory containing target-specific C++ headers. ! '-iprefix PREFIX' ! Specify PREFIX as the prefix for subsequent '-iwithprefix' options. ! If the PREFIX represents a directory, you should include the final ! ''/''. ! '-isysroot DIR' ! This option is like the '--sysroot' option, but applies only to ! header files. See the '--sysroot' option for more information. ! '-iquote DIR' ! Search DIR only for header files requested with '#include "file"'; ! they are not searched for '#include ', before all directories ! specified by '-I' and before the standard system directories. If ! DIR begins with '=', then the '=' will be replaced by the sysroot ! prefix; see '--sysroot' and '-isysroot'. ! '-isystem DIR' Search DIR for header files, after all directories specified by ! '-I' but before the standard system directories. Mark it as a system directory, so that it gets the same special treatment as is ! applied to the standard system directories. If DIR begins with ! '=', then the '=' will be replaced by the sysroot prefix; see ! '--sysroot' and '-isysroot'. ! '-nostdinc' Do not search the standard system directories for header files. ! Only the directories you have specified with '-I' options (and the directory of the current file, if appropriate) are searched. ! '-undef' Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. ! '-APREDICATE=ANSWER' Make an assertion with the predicate PREDICATE and answer ANSWER. This form is preferred to the older form -A predicate(answer), which is still supported, because it does not use shell special characters. ! '-A-PREDICATE=ANSWER' Cancel an assertion with the predicate PREDICATE and answer ANSWER. ! '-C' ! Do not discard comments. All comments are passed through to the ! output file, except for comments in processed directives, which are ! deleted along with the directive. ! You should be prepared for side effects when using '-C'; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no ! longer a ''#''. ! Warning: this currently handles C-Style comments only. The preprocessor does not yet recognize Fortran-style comments. ! '-CC' ! Do not discard comments, including during macro expansion. This is ! like '-C', except that comments contained within macros are also passed through to the output file where the macro is expanded. ! In addition to the side-effects of the '-C' option, the '-CC' ! option causes all C++-style comments inside a macro to be converted ! to C-style comments. This is to prevent later use of that macro ! from inadvertently commenting out the remainder of the source line. ! The '-CC' option is generally used to support lint comments. ! Warning: this currently handles C- and C++-Style comments only. ! The preprocessor does not yet recognize Fortran-style comments. ! '-DNAME' ! Predefine name as a macro, with definition '1'. ! '-DNAME=DEFINITION' The contents of DEFINITION are tokenized and processed as if they ! appeared during translation phase three in a ''#define'' directive. In particular, the definition will be truncated by embedded newline characters. --- 708,865 ---- 2.3 Enable and customize preprocessing ====================================== ! Preprocessor related options. See section *note Preprocessing and ! conditional compilation:: for more detailed information on ! preprocessing in `gfortran'. ! `-cpp' ! `-nocpp' ! Enable preprocessing. The preprocessor is automatically invoked if ! the file extension is `.fpp', `.FPP', `.F', `.FOR', `.FTN', ! `.F90', `.F95', `.F03' or `.F08'. Use this option to manually ! enable preprocessing of any kind of Fortran file. To disable preprocessing of files with any of the above listed ! extensions, use the negative form: `-nocpp'. ! The preprocessor is run in traditional mode. Any restrictions of the file-format, especially the limits on line length, apply for preprocessed output as well, so it might be advisable to use the ! `-ffree-line-length-none' or `-ffixed-line-length-none' options. ! `-dM' ! Instead of the normal output, generate a list of `'#define'' directives for all the macros defined during the execution of the ! preprocessor, including predefined macros. This gives you a way of finding out what is predefined in your version of the preprocessor. ! Assuming you have no file `foo.f90', the command touch foo.f90; gfortran -cpp -E -dM foo.f90 will show all the predefined macros. ! `-dD' ! Like `-dM' except in two respects: it does not include the ! predefined macros, and it outputs both the `#define' directives ! and the result of preprocessing. Both kinds of output go to the standard output file. ! `-dN' ! Like `-dD', but emit only the macro names, not their expansions. ! `-dU' ! Like `dD' except that only macros that are expanded, or whose definedness is tested in preprocessor directives, are output; the output is delayed until the use or test of the macro; and ! `'#undef'' directives are also output for macros tested but undefined at the time. ! `-dI' ! Output `'#include'' directives in addition to the result of preprocessing. ! `-fworking-directory' Enable generation of linemarkers in the preprocessor output that will let the compiler know the current working directory at the ! time of preprocessing. When this option is enabled, the preprocessor will emit, after the initial linemarker, a second linemarker with the current working directory followed by two ! slashes. GCC will use this directory, when it is present in the ! preprocessed input, as the directory emitted as the current ! working directory in some debugging information formats. This ! option is implicitly enabled if debugging information is enabled, ! but this can be inhibited with the negated form ! `-fno-working-directory'. If the `-P' flag is present in the ! command line, this option has no effect, since no `#line' ! directives are emitted whatsoever. ! `-idirafter DIR' Search DIR for include files, but do it after all directories ! specified with `-I' and the standard system directories have been ! exhausted. DIR is treated as a system include directory. If dir ! begins with `=', then the `=' will be replaced by the sysroot ! prefix; see `--sysroot' and `-isysroot'. ! `-imultilib DIR' Use DIR as a subdirectory of the directory containing target-specific C++ headers. ! `-iprefix PREFIX' ! Specify PREFIX as the prefix for subsequent `-iwithprefix' ! options. If the PREFIX represents a directory, you should include ! the final `'/''. ! `-isysroot DIR' ! This option is like the `--sysroot' option, but applies only to ! header files. See the `--sysroot' option for more information. ! `-iquote DIR' ! Search DIR only for header files requested with `#include "file"'; ! they are not searched for `#include ', before all directories ! specified by `-I' and before the standard system directories. If ! DIR begins with `=', then the `=' will be replaced by the sysroot ! prefix; see `--sysroot' and `-isysroot'. ! `-isystem DIR' Search DIR for header files, after all directories specified by ! `-I' but before the standard system directories. Mark it as a system directory, so that it gets the same special treatment as is ! applied to the standard system directories. If DIR begins with ! `=', then the `=' will be replaced by the sysroot prefix; see ! `--sysroot' and `-isysroot'. ! `-nostdinc' Do not search the standard system directories for header files. ! Only the directories you have specified with `-I' options (and the directory of the current file, if appropriate) are searched. ! `-undef' Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. ! `-APREDICATE=ANSWER' Make an assertion with the predicate PREDICATE and answer ANSWER. This form is preferred to the older form -A predicate(answer), which is still supported, because it does not use shell special characters. ! `-A-PREDICATE=ANSWER' Cancel an assertion with the predicate PREDICATE and answer ANSWER. ! `-C' ! Do not discard comments. All comments are passed through to the ! output file, except for comments in processed directives, which ! are deleted along with the directive. ! You should be prepared for side effects when using `-C'; it causes the preprocessor to treat comments as tokens in their own right. For example, comments appearing at the start of what would be a directive line have the effect of turning that line into an ordinary source line, since the first token on the line is no ! longer a `'#''. ! Warning: this currently handles C-Style comments only. The preprocessor does not yet recognize Fortran-style comments. ! `-CC' ! Do not discard comments, including during macro expansion. This is ! like `-C', except that comments contained within macros are also passed through to the output file where the macro is expanded. ! In addition to the side-effects of the `-C' option, the `-CC' ! option causes all C++-style comments inside a macro to be ! converted to C-style comments. This is to prevent later use of ! that macro from inadvertently commenting out the remainder of the ! source line. The `-CC' option is generally used to support lint ! comments. ! Warning: this currently handles C- and C++-Style comments only. The ! preprocessor does not yet recognize Fortran-style comments. ! `-DNAME' ! Predefine name as a macro, with definition `1'. ! `-DNAME=DEFINITION' The contents of DEFINITION are tokenized and processed as if they ! appeared during translation phase three in a `'#define'' directive. In particular, the definition will be truncated by embedded newline characters. *************** in 'gfortran'. *** 868,895 **** If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the ! equals sign (if any). Parentheses are meaningful to most shells, ! so you will need to quote the option. With sh and csh, ! '-D'name(args...)=definition'' works. ! '-D' and '-U' options are processed in the order they are given on ! the command line. All -imacros file and -include file options are processed after all -D and -U options. ! '-H' Print the name of each header file used, in addition to other ! normal activities. Each name is indented to show how deep in the ! ''#include'' stack it is. ! '-P' Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. ! '-UNAME' Cancel any previous definition of NAME, either built in or provided ! with a '-D' option.  File: gfortran.info, Node: Error and Warning Options, Next: Debugging Options, Prev: Preprocessing Options, Up: Invoking GNU Fortran --- 869,896 ---- If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the ! equals sign (if any). Parentheses are meaningful to most shells, ! so you will need to quote the option. With sh and csh, ! `-D'name(args...)=definition'' works. ! `-D' and `-U' options are processed in the order they are given on ! the command line. All -imacros file and -include file options are processed after all -D and -U options. ! `-H' Print the name of each header file used, in addition to other ! normal activities. Each name is indented to show how deep in the ! `'#include'' stack it is. ! `-P' Inhibit generation of linemarkers in the output from the preprocessor. This might be useful when running the preprocessor on something that is not C code, and will be sent to a program which might be confused by the linemarkers. ! `-UNAME' Cancel any previous definition of NAME, either built in or provided ! with a `-D' option.  File: gfortran.info, Node: Error and Warning Options, Next: Debugging Options, Prev: Preprocessing Options, Up: Invoking GNU Fortran *************** to aid in debugging, but will not produc *** 904,968 **** Warnings are diagnostic messages that report constructions which are not inherently erroneous but which are risky or suggest there is likely ! to be a bug in the program. Unless '-Werror' is specified, they do not prevent compilation of the program. ! You can request many specific warnings with options beginning '-W', ! for example '-Wimplicit' to request warnings on implicit declarations. Each of these specific warning options also has a negative form ! beginning '-Wno-' to turn off warnings; for example, '-Wno-implicit'. This manual lists only one of the two forms, whichever is not the default. These options control the amount and kinds of errors and warnings produced by GNU Fortran: ! '-fmax-errors=N' Limits the maximum number of error messages to N, at which point ! GNU Fortran bails out rather than attempting to continue processing ! the source code. If N is 0, there is no limit on the number of ! error messages produced. ! '-fsyntax-only' Check the code for syntax errors, but do not actually compile it. This will generate module files for each module present in the code, but no other output file. ! '-pedantic' ! Issue warnings for uses of extensions to Fortran 95. '-pedantic' also applies to C-language constructs where they occur in GNU ! Fortran source files, such as use of '\e' in a character constant ! within a directive like '#include'. Valid Fortran 95 programs should compile properly with or without this option. However, without this option, certain GNU extensions and traditional Fortran features are supported as well. With this option, many of them are rejected. ! Some users try to use '-pedantic' to check programs for conformance. They soon find that it does not do quite what they want--it finds some nonstandard practices, but not all. However, improvements to GNU Fortran in this area are welcome. ! This should be used in conjunction with '-std=f95', '-std=f2003' or ! '-std=f2008'. ! '-pedantic-errors' ! Like '-pedantic', except that errors are produced rather than warnings. ! '-Wall' Enables commonly used warning options pertaining to usage that we recommend avoiding and that we believe are easy to avoid. This ! currently includes '-Waliasing', '-Wampersand', '-Wconversion', ! '-Wsurprising', '-Wc-binding-type', '-Wintrinsics-std', '-Wtabs', ! '-Wintrinsic-shadow', '-Wline-truncation', '-Wtarget-lifetime', ! '-Winteger-division', '-Wreal-q-constant' and '-Wunused'. ! '-Waliasing' ! Warn about possible aliasing of dummy arguments. Specifically, it warns if the same actual argument is associated with a dummy ! argument with 'INTENT(IN)' and a dummy argument with 'INTENT(OUT)' in a call with an explicit interface. The following example will trigger the warning. --- 905,969 ---- Warnings are diagnostic messages that report constructions which are not inherently erroneous but which are risky or suggest there is likely ! to be a bug in the program. Unless `-Werror' is specified, they do not prevent compilation of the program. ! You can request many specific warnings with options beginning `-W', ! for example `-Wimplicit' to request warnings on implicit declarations. Each of these specific warning options also has a negative form ! beginning `-Wno-' to turn off warnings; for example, `-Wno-implicit'. This manual lists only one of the two forms, whichever is not the default. These options control the amount and kinds of errors and warnings produced by GNU Fortran: ! `-fmax-errors=N' Limits the maximum number of error messages to N, at which point ! GNU Fortran bails out rather than attempting to continue ! processing the source code. If N is 0, there is no limit on the ! number of error messages produced. ! `-fsyntax-only' Check the code for syntax errors, but do not actually compile it. This will generate module files for each module present in the code, but no other output file. ! `-pedantic' ! Issue warnings for uses of extensions to Fortran 95. `-pedantic' also applies to C-language constructs where they occur in GNU ! Fortran source files, such as use of `\e' in a character constant ! within a directive like `#include'. Valid Fortran 95 programs should compile properly with or without this option. However, without this option, certain GNU extensions and traditional Fortran features are supported as well. With this option, many of them are rejected. ! Some users try to use `-pedantic' to check programs for conformance. They soon find that it does not do quite what they want--it finds some nonstandard practices, but not all. However, improvements to GNU Fortran in this area are welcome. ! This should be used in conjunction with `-std=f95', `-std=f2003' ! or `-std=f2008'. ! `-pedantic-errors' ! Like `-pedantic', except that errors are produced rather than warnings. ! `-Wall' Enables commonly used warning options pertaining to usage that we recommend avoiding and that we believe are easy to avoid. This ! currently includes `-Waliasing', `-Wampersand', `-Wconversion', ! `-Wsurprising', `-Wc-binding-type', `-Wintrinsics-std', `-Wtabs', ! `-Wintrinsic-shadow', `-Wline-truncation', `-Wtarget-lifetime', ! `-Winteger-division', `-Wreal-q-constant' and `-Wunused'. ! `-Waliasing' ! Warn about possible aliasing of dummy arguments. Specifically, it warns if the same actual argument is associated with a dummy ! argument with `INTENT(IN)' and a dummy argument with `INTENT(OUT)' in a call with an explicit interface. The following example will trigger the warning. *************** produced by GNU Fortran: *** 976,1049 **** call bar(a,a) ! '-Wampersand' ! Warn about missing ampersand in continued character constants. The ! warning is given with '-Wampersand', '-pedantic', '-std=f95', ! '-std=f2003' and '-std=f2008'. Note: With no ampersand given in a continued character constant, GNU Fortran assumes continuation at the first non-comment, non-whitespace character after the ampersand that initiated the continuation. ! '-Warray-temporaries' Warn about array temporaries generated by the compiler. The information generated by this warning is sometimes useful in optimization, in order to avoid such temporaries. ! '-Wc-binding-type' Warn if the a variable might not be C interoperable. In particular, warn if the variable has been declared using an intrinsic type with default kind instead of using a kind parameter ! defined for C interoperability in the intrinsic 'ISO_C_Binding' ! module. This option is implied by '-Wall'. ! '-Wcharacter-truncation' Warn when a character assignment will truncate the assigned string. ! '-Wline-truncation' Warn when a source code line will be truncated. This option is ! implied by '-Wall'. For free-form source code, the default is ! '-Werror=line-truncation' such that truncations are reported as error. ! '-Wconversion' ! Warn about implicit conversions that are likely to change the value ! of the expression after conversion. Implied by '-Wall'. ! '-Wconversion-extra' Warn about implicit conversions between different types and kinds. ! This option does _not_ imply '-Wconversion'. ! '-Wextra' Enables some warning options for usages of language features which ! may be problematic. This currently includes '-Wcompare-reals' and ! '-Wunused-parameter'. ! '-Wimplicit-interface' Warn if a procedure is called without an explicit interface. Note this only checks that an explicit interface is present. It does not check that the declared interfaces are consistent across program units. ! '-Wimplicit-procedure' Warn if a procedure is called that has neither an explicit ! interface nor has been declared as 'EXTERNAL'. ! '-Winteger-division' Warn if a constant integer division truncates it result. As an example, 3/5 evaluates to 0. ! '-Wintrinsics-std' ! Warn if 'gfortran' finds a procedure named like an intrinsic not ! available in the currently selected standard (with '-std') and ! treats it as 'EXTERNAL' procedure because of this. ! '-fall-intrinsics' can be used to never trigger this behavior and always link to the intrinsic regardless of the selected standard. ! '-Wreal-q-constant' ! Produce a warning if a real-literal-constant contains a 'q' exponent-letter. ! '-Wsurprising' Produce a warning when "suspicious" code constructs are encountered. While technically legal these usually indicate that an error has been made. --- 977,1050 ---- call bar(a,a) ! `-Wampersand' ! Warn about missing ampersand in continued character constants. The ! warning is given with `-Wampersand', `-pedantic', `-std=f95', ! `-std=f2003' and `-std=f2008'. Note: With no ampersand given in a continued character constant, GNU Fortran assumes continuation at the first non-comment, non-whitespace character after the ampersand that initiated the continuation. ! `-Warray-temporaries' Warn about array temporaries generated by the compiler. The information generated by this warning is sometimes useful in optimization, in order to avoid such temporaries. ! `-Wc-binding-type' Warn if the a variable might not be C interoperable. In particular, warn if the variable has been declared using an intrinsic type with default kind instead of using a kind parameter ! defined for C interoperability in the intrinsic `ISO_C_Binding' ! module. This option is implied by `-Wall'. ! `-Wcharacter-truncation' Warn when a character assignment will truncate the assigned string. ! `-Wline-truncation' Warn when a source code line will be truncated. This option is ! implied by `-Wall'. For free-form source code, the default is ! `-Werror=line-truncation' such that truncations are reported as error. ! `-Wconversion' ! Warn about implicit conversions that are likely to change the ! value of the expression after conversion. Implied by `-Wall'. ! `-Wconversion-extra' Warn about implicit conversions between different types and kinds. ! This option does _not_ imply `-Wconversion'. ! `-Wextra' Enables some warning options for usages of language features which ! may be problematic. This currently includes `-Wcompare-reals' and ! `-Wunused-parameter'. ! `-Wimplicit-interface' Warn if a procedure is called without an explicit interface. Note this only checks that an explicit interface is present. It does not check that the declared interfaces are consistent across program units. ! `-Wimplicit-procedure' Warn if a procedure is called that has neither an explicit ! interface nor has been declared as `EXTERNAL'. ! `-Winteger-division' Warn if a constant integer division truncates it result. As an example, 3/5 evaluates to 0. ! `-Wintrinsics-std' ! Warn if `gfortran' finds a procedure named like an intrinsic not ! available in the currently selected standard (with `-std') and ! treats it as `EXTERNAL' procedure because of this. ! `-fall-intrinsics' can be used to never trigger this behavior and always link to the intrinsic regardless of the selected standard. ! `-Wreal-q-constant' ! Produce a warning if a real-literal-constant contains a `q' exponent-letter. ! `-Wsurprising' Produce a warning when "suspicious" code constructs are encountered. While technically legal these usually indicate that an error has been made. *************** produced by GNU Fortran: *** 1060,1150 **** destination. * The type of a function result is declared more than once with ! the same type. If '-pedantic' or standard-conforming mode is enabled, this is an error. ! * A 'CHARACTER' variable is declared with negative length. ! '-Wtabs' By default, tabs are accepted as whitespace, but tabs are not members of the Fortran Character Set. For continuation lines, a ! tab followed by a digit between 1 and 9 is supported. '-Wtabs' ! will cause a warning to be issued if a tab is encountered. Note, ! '-Wtabs' is active for '-pedantic', '-std=f95', '-std=f2003', ! '-std=f2008', '-std=f2008ts' and '-Wall'. ! '-Wunderflow' Produce a warning when numerical constant expressions are ! encountered, which yield an UNDERFLOW during compilation. Enabled by default. ! '-Wintrinsic-shadow' Warn if a user-defined procedure or module procedure has the same name as an intrinsic; in this case, an explicit interface or ! 'EXTERNAL' or 'INTRINSIC' declaration might be needed to get calls later resolved to the desired intrinsic/procedure. This option is ! implied by '-Wall'. ! '-Wuse-without-only' ! Warn if a 'USE' statement has no 'ONLY' qualifier and thus implicitly imports all public entities of the used module. ! '-Wunused-dummy-argument' ! Warn about unused dummy arguments. This option is implied by ! '-Wall'. ! '-Wunused-parameter' ! Contrary to 'gcc''s meaning of '-Wunused-parameter', 'gfortran''s implementation of this option does not warn about unused dummy ! arguments (see '-Wunused-dummy-argument'), but about unused ! 'PARAMETER' values. '-Wunused-parameter' is implied by '-Wextra' ! if also '-Wunused' or '-Wall' is used. ! '-Walign-commons' ! By default, 'gfortran' warns about any occasion of variables being ! padded for proper alignment inside a 'COMMON' block. This warning ! can be turned off via '-Wno-align-commons'. See also ! '-falign-commons'. ! '-Wfunction-elimination' Warn if any calls to functions are eliminated by the optimizations ! enabled by the '-ffrontend-optimize' option. ! '-Wrealloc-lhs' Warn when the compiler might insert code to for allocation or reallocation of an allocatable array variable of intrinsic type in ! intrinsic assignments. In hot loops, the Fortran 2003 reallocation ! feature may reduce the performance. If the array is already ! allocated with the correct shape, consider using a whole-array ! array-spec (e.g. '(:,:,:)') for the variable on the left-hand side ! to prevent the reallocation check. Note that in some cases the ! warning is shown, even if the compiler will optimize reallocation ! checks away. For instance, when the right-hand side contains the ! same variable multiplied by a scalar. See also '-frealloc-lhs'. ! '-Wrealloc-lhs-all' Warn when the compiler inserts code to for allocation or reallocation of an allocatable variable; this includes scalars and derived types. ! '-Wcompare-reals' Warn when comparing real or complex types for equality or ! inequality. This option is implied by '-Wextra'. ! '-Wtarget-lifetime' Warn if the pointer in a pointer assignment might be longer than ! the its target. This option is implied by '-Wall'. ! '-Wzerotrip' ! Warn if a 'DO' loop is known to execute zero times at compile time. ! This option is implied by '-Wall'. ! '-Werror' Turns all warnings into errors. *Note Options to Request or Suppress Errors and Warnings: ! (gcc)Warning Options, for information on more options offered by the GBE ! shared by 'gfortran', 'gcc' and other GNU compilers. Some of these have no effect when compiling programs written in Fortran. --- 1061,1152 ---- destination. * The type of a function result is declared more than once with ! the same type. If `-pedantic' or standard-conforming mode is enabled, this is an error. ! * A `CHARACTER' variable is declared with negative length. ! `-Wtabs' By default, tabs are accepted as whitespace, but tabs are not members of the Fortran Character Set. For continuation lines, a ! tab followed by a digit between 1 and 9 is supported. `-Wtabs' ! will cause a warning to be issued if a tab is encountered. Note, ! `-Wtabs' is active for `-pedantic', `-std=f95', `-std=f2003', ! `-std=f2008', `-std=f2008ts' and `-Wall'. ! `-Wunderflow' Produce a warning when numerical constant expressions are ! encountered, which yield an UNDERFLOW during compilation. Enabled by default. ! `-Wintrinsic-shadow' Warn if a user-defined procedure or module procedure has the same name as an intrinsic; in this case, an explicit interface or ! `EXTERNAL' or `INTRINSIC' declaration might be needed to get calls later resolved to the desired intrinsic/procedure. This option is ! implied by `-Wall'. ! `-Wuse-without-only' ! Warn if a `USE' statement has no `ONLY' qualifier and thus implicitly imports all public entities of the used module. ! `-Wunused-dummy-argument' ! Warn about unused dummy arguments. This option is implied by ! `-Wall'. ! `-Wunused-parameter' ! Contrary to `gcc''s meaning of `-Wunused-parameter', `gfortran''s implementation of this option does not warn about unused dummy ! arguments (see `-Wunused-dummy-argument'), but about unused ! `PARAMETER' values. `-Wunused-parameter' is implied by `-Wextra' ! if also `-Wunused' or `-Wall' is used. ! `-Walign-commons' ! By default, `gfortran' warns about any occasion of variables being ! padded for proper alignment inside a `COMMON' block. This warning ! can be turned off via `-Wno-align-commons'. See also ! `-falign-commons'. ! `-Wfunction-elimination' Warn if any calls to functions are eliminated by the optimizations ! enabled by the `-ffrontend-optimize' option. ! `-Wrealloc-lhs' Warn when the compiler might insert code to for allocation or reallocation of an allocatable array variable of intrinsic type in ! intrinsic assignments. In hot loops, the Fortran 2003 ! reallocation feature may reduce the performance. If the array is ! already allocated with the correct shape, consider using a ! whole-array array-spec (e.g. `(:,:,:)') for the variable on the ! left-hand side to prevent the reallocation check. Note that in ! some cases the warning is shown, even if the compiler will ! optimize reallocation checks away. For instance, when the ! right-hand side contains the same variable multiplied by a scalar. ! See also `-frealloc-lhs'. ! `-Wrealloc-lhs-all' Warn when the compiler inserts code to for allocation or reallocation of an allocatable variable; this includes scalars and derived types. ! `-Wcompare-reals' Warn when comparing real or complex types for equality or ! inequality. This option is implied by `-Wextra'. ! `-Wtarget-lifetime' Warn if the pointer in a pointer assignment might be longer than ! the its target. This option is implied by `-Wall'. ! `-Wzerotrip' ! Warn if a `DO' loop is known to execute zero times at compile ! time. This option is implied by `-Wall'. ! `-Werror' Turns all warnings into errors. *Note Options to Request or Suppress Errors and Warnings: ! (gcc)Warning Options, for information on more options offered by the ! GBE shared by `gfortran', `gcc' and other GNU compilers. Some of these have no effect when compiling programs written in Fortran. *************** File: gfortran.info, Node: Debugging Op *** 1158,1223 **** GNU Fortran has various special options that are used for debugging either your program or the GNU Fortran compiler. ! '-fdump-fortran-original' Output the internal parse tree after translating the source program into internal representation. Only really useful for debugging the GNU Fortran compiler itself. ! '-fdump-fortran-optimized' Output the parse tree after front-end optimization. Only really useful for debugging the GNU Fortran compiler itself. ! '-fdump-parse-tree' Output the internal parse tree after translating the source program into internal representation. Only really useful for debugging the GNU Fortran compiler itself. This option is deprecated; use ! '-fdump-fortran-original' instead. ! '-ffpe-trap=LIST' Specify a list of floating point exception traps to enable. On ! most systems, if a floating point exception occurs and the trap for ! that exception is enabled, a SIGFPE signal will be sent and the ! program being aborted, producing a core file useful for debugging. ! LIST is a (possibly empty) comma-separated list of the following ! exceptions: 'invalid' (invalid floating point operation, such as ! 'SQRT(-1.0)'), 'zero' (division by zero), 'overflow' (overflow in a ! floating point operation), 'underflow' (underflow in a floating ! point operation), 'inexact' (loss of precision during operation), ! and 'denormal' (operation performed on a denormal value). The ! first five exceptions correspond to the five IEEE 754 exceptions, ! whereas the last one ('denormal') is not part of the IEEE 754 ! standard but is available on some common architectures such as x86. ! The first three exceptions ('invalid', 'zero', and 'overflow') often indicate serious errors, and unless the program has provisions for dealing with these exceptions, enabling traps for these three exceptions is probably a good idea. Many, if not most, floating point operations incur loss of ! precision due to rounding, and hence the 'ffpe-trap=inexact' is likely to be uninteresting in practice. By default no exception traps are enabled. ! '-ffpe-summary=LIST' Specify a list of floating-point exceptions, whose flag status is ! printed to 'ERROR_UNIT' when invoking 'STOP' and 'ERROR STOP'. ! LIST can be either 'none', 'all' or a comma-separated list of the ! following exceptions: 'invalid', 'zero', 'overflow', 'underflow', ! 'inexact' and 'denormal'. (See '-ffpe-trap' for a description of the exceptions.) ! By default, a summary for all exceptions but 'inexact' is shown. ! '-fno-backtrace' When a serious runtime error is encountered or a deadly signal is emitted (segmentation fault, illegal instruction, bus error, floating-point exception, and the other POSIX signals that have the ! action 'core'), the Fortran runtime library tries to output a ! backtrace of the error. '-fno-backtrace' disables the backtrace ! generation. This option only has influence for compilation of the Fortran main program. *Note Options for Debugging Your Program or GCC: (gcc)Debugging Options, for more information on debugging options. --- 1160,1227 ---- GNU Fortran has various special options that are used for debugging either your program or the GNU Fortran compiler. ! `-fdump-fortran-original' Output the internal parse tree after translating the source program into internal representation. Only really useful for debugging the GNU Fortran compiler itself. ! `-fdump-fortran-optimized' Output the parse tree after front-end optimization. Only really useful for debugging the GNU Fortran compiler itself. ! `-fdump-parse-tree' Output the internal parse tree after translating the source program into internal representation. Only really useful for debugging the GNU Fortran compiler itself. This option is deprecated; use ! `-fdump-fortran-original' instead. ! `-ffpe-trap=LIST' Specify a list of floating point exception traps to enable. On ! most systems, if a floating point exception occurs and the trap ! for that exception is enabled, a SIGFPE signal will be sent and ! the program being aborted, producing a core file useful for ! debugging. LIST is a (possibly empty) comma-separated list of the ! following exceptions: `invalid' (invalid floating point operation, ! such as `SQRT(-1.0)'), `zero' (division by zero), `overflow' ! (overflow in a floating point operation), `underflow' (underflow ! in a floating point operation), `inexact' (loss of precision ! during operation), and `denormal' (operation performed on a ! denormal value). The first five exceptions correspond to the five ! IEEE 754 exceptions, whereas the last one (`denormal') is not part ! of the IEEE 754 standard but is available on some common ! architectures such as x86. ! The first three exceptions (`invalid', `zero', and `overflow') often indicate serious errors, and unless the program has provisions for dealing with these exceptions, enabling traps for these three exceptions is probably a good idea. Many, if not most, floating point operations incur loss of ! precision due to rounding, and hence the `ffpe-trap=inexact' is likely to be uninteresting in practice. By default no exception traps are enabled. ! `-ffpe-summary=LIST' Specify a list of floating-point exceptions, whose flag status is ! printed to `ERROR_UNIT' when invoking `STOP' and `ERROR STOP'. ! LIST can be either `none', `all' or a comma-separated list of the ! following exceptions: `invalid', `zero', `overflow', `underflow', ! `inexact' and `denormal'. (See `-ffpe-trap' for a description of the exceptions.) ! By default, a summary for all exceptions but `inexact' is shown. ! `-fno-backtrace' When a serious runtime error is encountered or a deadly signal is emitted (segmentation fault, illegal instruction, bus error, floating-point exception, and the other POSIX signals that have the ! action `core'), the Fortran runtime library tries to output a ! backtrace of the error. `-fno-backtrace' disables the backtrace ! generation. This option only has influence for compilation of the Fortran main program. + *Note Options for Debugging Your Program or GCC: (gcc)Debugging Options, for more information on debugging options. *************** File: gfortran.info, Node: Directory Op *** 1227,1262 **** 2.6 Options for directory search ================================ ! These options affect how GNU Fortran searches for files specified by the ! 'INCLUDE' directive and where it searches for previously compiled modules. ! It also affects the search paths used by 'cpp' when used to preprocess Fortran source. ! '-IDIR' ! These affect interpretation of the 'INCLUDE' directive (as well as ! of the '#include' directive of the 'cpp' preprocessor). ! Also note that the general behavior of '-I' and 'INCLUDE' is pretty ! much the same as of '-I' with '#include' in the 'cpp' preprocessor, ! with regard to looking for 'header.gcc' files and other such ! things. ! This path is also used to search for '.mod' files when previously ! compiled modules are required by a 'USE' statement. *Note Options for Directory Search: (gcc)Directory Options, for ! information on the '-I' option. ! '-JDIR' ! This option specifies where to put '.mod' files for compiled modules. It is also added to the list of directories to searched ! by an 'USE' statement. The default is the current directory. ! '-fintrinsic-modules-path DIR' This option specifies the location of pre-compiled intrinsic modules, if they are not in the default location expected by the compiler. --- 1231,1266 ---- 2.6 Options for directory search ================================ ! These options affect how GNU Fortran searches for files specified by ! the `INCLUDE' directive and where it searches for previously compiled modules. ! It also affects the search paths used by `cpp' when used to preprocess Fortran source. ! `-IDIR' ! These affect interpretation of the `INCLUDE' directive (as well as ! of the `#include' directive of the `cpp' preprocessor). ! Also note that the general behavior of `-I' and `INCLUDE' is ! pretty much the same as of `-I' with `#include' in the `cpp' ! preprocessor, with regard to looking for `header.gcc' files and ! other such things. ! This path is also used to search for `.mod' files when previously ! compiled modules are required by a `USE' statement. *Note Options for Directory Search: (gcc)Directory Options, for ! information on the `-I' option. ! `-JDIR' ! This option specifies where to put `.mod' files for compiled modules. It is also added to the list of directories to searched ! by an `USE' statement. The default is the current directory. ! `-fintrinsic-modules-path DIR' This option specifies the location of pre-compiled intrinsic modules, if they are not in the default location expected by the compiler. *************** File: gfortran.info, Node: Link Options *** 1268,1280 **** ================================ These options come into play when the compiler links object files into ! an executable output file. They are meaningless if the compiler is not doing a link step. ! '-static-libgfortran' ! On systems that provide 'libgfortran' as a shared and a static ! library, this option forces the use of the static version. If no ! shared version of 'libgfortran' was built when the compiler was configured, this option has no effect.  --- 1272,1284 ---- ================================ These options come into play when the compiler links object files into ! an executable output file. They are meaningless if the compiler is not doing a link step. ! `-static-libgfortran' ! On systems that provide `libgfortran' as a shared and a static ! library, this option forces the use of the static version. If no ! shared version of `libgfortran' was built when the compiler was configured, this option has no effect.  *************** File: gfortran.info, Node: Runtime Opti *** 1286,1323 **** These options affect the runtime behavior of programs compiled with GNU Fortran. ! '-fconvert=CONVERSION' Specify the representation of data for unformatted files. Valid ! values for conversion are: 'native', the default; 'swap', swap ! between big- and little-endian; 'big-endian', use big-endian ! representation for unformatted files; 'little-endian', use little-endian representation for unformatted files. ! _This option has an effect only when used in the main program. The ! 'CONVERT' specifier and the GFORTRAN_CONVERT_UNIT environment ! variable override the default specified by '-fconvert'._ ! '-frecord-marker=LENGTH' Specify the length of record markers for unformatted files. Valid values for LENGTH are 4 and 8. Default is 4. _This is different ! from previous versions of 'gfortran'_, which specified a default record marker length of 8 on most systems. If you want to read or ! write files compatible with earlier versions of 'gfortran', use ! '-frecord-marker=8'. ! '-fmax-subrecord-length=LENGTH' Specify the maximum length for a subrecord. The maximum permitted value for length is 2147483639, which is also the default. Only really useful for use by the gfortran testsuite. ! '-fsign-zero' When enabled, floating point numbers of value zero with the sign bit set are written as negative number in formatted output and ! treated as negative in the 'SIGN' intrinsic. '-fno-sign-zero' does ! not print the negative sign of zero values (or values rounded to ! zero for I/O) and regards zero as positive number in the 'SIGN' ! intrinsic for compatibility with Fortran 77. The default is ! '-fsign-zero'.  File: gfortran.info, Node: Code Gen Options, Next: Environment Variables, Prev: Runtime Options, Up: Invoking GNU Fortran --- 1290,1327 ---- These options affect the runtime behavior of programs compiled with GNU Fortran. ! `-fconvert=CONVERSION' Specify the representation of data for unformatted files. Valid ! values for conversion are: `native', the default; `swap', swap ! between big- and little-endian; `big-endian', use big-endian ! representation for unformatted files; `little-endian', use little-endian representation for unformatted files. ! _This option has an effect only when used in the main program. ! The `CONVERT' specifier and the GFORTRAN_CONVERT_UNIT environment ! variable override the default specified by `-fconvert'._ ! `-frecord-marker=LENGTH' Specify the length of record markers for unformatted files. Valid values for LENGTH are 4 and 8. Default is 4. _This is different ! from previous versions of `gfortran'_, which specified a default record marker length of 8 on most systems. If you want to read or ! write files compatible with earlier versions of `gfortran', use ! `-frecord-marker=8'. ! `-fmax-subrecord-length=LENGTH' Specify the maximum length for a subrecord. The maximum permitted value for length is 2147483639, which is also the default. Only really useful for use by the gfortran testsuite. ! `-fsign-zero' When enabled, floating point numbers of value zero with the sign bit set are written as negative number in formatted output and ! treated as negative in the `SIGN' intrinsic. `-fno-sign-zero' ! does not print the negative sign of zero values (or values rounded ! to zero for I/O) and regards zero as positive number in the `SIGN' ! intrinsic for compatibility with Fortran 77. The default is ! `-fsign-zero'.  File: gfortran.info, Node: Code Gen Options, Next: Environment Variables, Prev: Runtime Options, Up: Invoking GNU Fortran *************** File: gfortran.info, Node: Code Gen Opt *** 1325,1407 **** 2.9 Options for code generation conventions =========================================== ! These machine-independent options control the interface conventions used ! in code generation. Most of them have both positive and negative forms; the negative form ! of '-ffoo' would be '-fno-foo'. In the table below, only one of the forms is listed--the one which is not the default. You can figure out ! the other form by either removing 'no-' or adding it. ! '-fno-automatic' Treat each program unit (except those marked as RECURSIVE) as if ! the 'SAVE' statement were specified for every local variable and ! array referenced in it. Does not affect common blocks. (Some ! Fortran compilers provide this option under the name '-static' or ! '-save'.) The default, which is '-fautomatic', uses the stack for local variables smaller than the value given by ! '-fmax-stack-var-size'. Use the option '-frecursive' to use no static memory. ! '-ff2c' Generate code designed to be compatible with code generated by ! 'g77' and 'f2c'. ! The calling conventions used by 'g77' (originally implemented in ! 'f2c') require functions that return type default 'REAL' to ! actually return the C type 'double', and functions that return type ! 'COMPLEX' to return the values via an extra argument in the calling ! sequence that points to where to store the return value. Under the ! default GNU calling conventions, such functions simply return their ! results as they would in GNU C--default 'REAL' functions return the ! C type 'float', and 'COMPLEX' functions return the GNU C type ! 'complex'. Additionally, this option implies the ! '-fsecond-underscore' option, unless '-fno-second-underscore' is ! explicitly requested. This does not affect the generation of code that interfaces with ! the 'libgfortran' library. _Caution:_ It is not a good idea to mix Fortran code compiled with ! '-ff2c' with code compiled with the default '-fno-f2c' calling ! conventions as, calling 'COMPLEX' or default 'REAL' functions between program parts which were compiled with different calling conventions will break at execution time. ! _Caution:_ This will break code which passes intrinsic functions of ! type default 'REAL' or 'COMPLEX' as actual arguments, as the ! library implementations use the '-fno-f2c' calling conventions. ! '-fno-underscoring' Do not transform names of entities specified in the Fortran source file by appending underscores to them. ! With '-funderscoring' in effect, GNU Fortran appends one underscore ! to external names with no underscores. This is done to ensure ! compatibility with code produced by many UNIX Fortran compilers. ! _Caution_: The default behavior of GNU Fortran is incompatible with ! 'f2c' and 'g77', please use the '-ff2c' option if you want object ! files compiled with GNU Fortran to be compatible with object code ! created with these tools. ! Use of '-fno-underscoring' is not recommended unless you are experimenting with issues such as integration of GNU Fortran into existing system environments (vis-a`-vis existing libraries, tools, and so on). ! For example, with '-funderscoring', and assuming that 'j()' and ! 'max_count()' are external functions while 'my_var' and 'lvar' are local variables, a statement like I = J() + MAX_COUNT (MY_VAR, LVAR) is implemented as something akin to: i = j_() + max_count__(&my_var__, &lvar); ! With '-fno-underscoring', the same statement is implemented as: i = j() + max_count(&my_var, &lvar); ! Use of '-fno-underscoring' allows direct specification of user-defined names while debugging and when interfacing GNU Fortran code with other languages. --- 1329,1412 ---- 2.9 Options for code generation conventions =========================================== ! These machine-independent options control the interface conventions ! used in code generation. Most of them have both positive and negative forms; the negative form ! of `-ffoo' would be `-fno-foo'. In the table below, only one of the forms is listed--the one which is not the default. You can figure out ! the other form by either removing `no-' or adding it. ! `-fno-automatic' Treat each program unit (except those marked as RECURSIVE) as if ! the `SAVE' statement were specified for every local variable and ! array referenced in it. Does not affect common blocks. (Some ! Fortran compilers provide this option under the name `-static' or ! `-save'.) The default, which is `-fautomatic', uses the stack for local variables smaller than the value given by ! `-fmax-stack-var-size'. Use the option `-frecursive' to use no static memory. ! `-ff2c' Generate code designed to be compatible with code generated by ! `g77' and `f2c'. ! The calling conventions used by `g77' (originally implemented in ! `f2c') require functions that return type default `REAL' to ! actually return the C type `double', and functions that return ! type `COMPLEX' to return the values via an extra argument in the ! calling sequence that points to where to store the return value. ! Under the default GNU calling conventions, such functions simply ! return their results as they would in GNU C--default `REAL' ! functions return the C type `float', and `COMPLEX' functions ! return the GNU C type `complex'. Additionally, this option ! implies the `-fsecond-underscore' option, unless ! `-fno-second-underscore' is explicitly requested. This does not affect the generation of code that interfaces with ! the `libgfortran' library. _Caution:_ It is not a good idea to mix Fortran code compiled with ! `-ff2c' with code compiled with the default `-fno-f2c' calling ! conventions as, calling `COMPLEX' or default `REAL' functions between program parts which were compiled with different calling conventions will break at execution time. ! _Caution:_ This will break code which passes intrinsic functions ! of type default `REAL' or `COMPLEX' as actual arguments, as the ! library implementations use the `-fno-f2c' calling conventions. ! `-fno-underscoring' Do not transform names of entities specified in the Fortran source file by appending underscores to them. ! With `-funderscoring' in effect, GNU Fortran appends one ! underscore to external names with no underscores. This is done to ! ensure compatibility with code produced by many UNIX Fortran ! compilers. ! _Caution_: The default behavior of GNU Fortran is incompatible ! with `f2c' and `g77', please use the `-ff2c' option if you want ! object files compiled with GNU Fortran to be compatible with ! object code created with these tools. ! Use of `-fno-underscoring' is not recommended unless you are experimenting with issues such as integration of GNU Fortran into existing system environments (vis-a`-vis existing libraries, tools, and so on). ! For example, with `-funderscoring', and assuming that `j()' and ! `max_count()' are external functions while `my_var' and `lvar' are local variables, a statement like I = J() + MAX_COUNT (MY_VAR, LVAR) is implemented as something akin to: i = j_() + max_count__(&my_var__, &lvar); ! With `-fno-underscoring', the same statement is implemented as: i = j() + max_count(&my_var, &lvar); ! Use of `-fno-underscoring' allows direct specification of user-defined names while debugging and when interfacing GNU Fortran code with other languages. *************** the other form by either removing 'no-' *** 1409,1421 **** interface implemented by GNU Fortran for an external name matches the interface implemented by some other language for that same name. That is, getting code produced by GNU Fortran to link to ! code produced by some other compiler using this or any other method ! can be only a small part of the overall solution--getting the code ! generated by both compilers to agree on issues other than naming ! can require significant effort, and, unlike naming disagreements, ! linkers normally cannot detect disagreements in these other areas. ! Also, note that with '-fno-underscoring', the lack of appended underscores introduces the very real possibility that a user-defined external name will conflict with a name in a system library, which could make finding unresolved-reference bugs quite --- 1414,1427 ---- interface implemented by GNU Fortran for an external name matches the interface implemented by some other language for that same name. That is, getting code produced by GNU Fortran to link to ! code produced by some other compiler using this or any other ! method can be only a small part of the overall solution--getting ! the code generated by both compilers to agree on issues other than ! naming can require significant effort, and, unlike naming ! disagreements, linkers normally cannot detect disagreements in ! these other areas. ! Also, note that with `-fno-underscoring', the lack of appended underscores introduces the very real possibility that a user-defined external name will conflict with a name in a system library, which could make finding unresolved-reference bugs quite *************** the other form by either removing 'no-' *** 1423,1483 **** show up only as buggy behavior at run time. In future versions of GNU Fortran we hope to improve naming and ! linking issues so that debugging always involves using the names as ! they appear in the source, even if the names as seen by the linker ! are mangled to prevent accidental linking between procedures with ! incompatible interfaces. ! '-fsecond-underscore' By default, GNU Fortran appends an underscore to external names. ! If this option is used GNU Fortran appends two underscores to names ! with underscores and one underscore to external names with no ! underscores. GNU Fortran also appends two underscores to internal ! names with underscores to avoid naming collisions with external ! names. ! This option has no effect if '-fno-underscoring' is in effect. It ! is implied by the '-ff2c' option. ! Otherwise, with this option, an external name such as 'MAX_COUNT' is implemented as a reference to the link-time external symbol ! 'max_count__', instead of 'max_count_'. This is required for ! compatibility with 'g77' and 'f2c', and is implied by use of the ! '-ff2c' option. ! '-fcoarray=' ! 'none' Disable coarray support; using coarray declarations and image-control statements will produce a compile-time error. (Default) ! 'single' ! Single-image mode, i.e. 'num_images()' is always one. ! 'lib' Library-based coarray parallelization; a suitable GNU Fortran coarray library needs to be linked. ! '-fcheck=' ! Enable the generation of run-time checks; the argument shall be a comma-delimited list of the following keywords. Prefixing a check ! with 'no-' disables it if it was activated by a previous specification. ! 'all' ! Enable all run-time test of '-fcheck'. ! 'array-temps' Warns at run time when for passing an actual argument a ! temporary array had to be generated. The information ! generated by this warning is sometimes useful in optimization, ! in order to avoid such temporaries. Note: The warning is only printed once per location. ! 'bounds' Enable generation of run-time checks for array subscripts and against the declared minimum and maximum values. It also checks array indices for assumed and deferred shape arrays --- 1429,1488 ---- show up only as buggy behavior at run time. In future versions of GNU Fortran we hope to improve naming and ! linking issues so that debugging always involves using the names ! as they appear in the source, even if the names as seen by the ! linker are mangled to prevent accidental linking between ! procedures with incompatible interfaces. ! `-fsecond-underscore' By default, GNU Fortran appends an underscore to external names. ! If this option is used GNU Fortran appends two underscores to ! names with underscores and one underscore to external names with ! no underscores. GNU Fortran also appends two underscores to ! internal names with underscores to avoid naming collisions with ! external names. ! This option has no effect if `-fno-underscoring' is in effect. It ! is implied by the `-ff2c' option. ! Otherwise, with this option, an external name such as `MAX_COUNT' is implemented as a reference to the link-time external symbol ! `max_count__', instead of `max_count_'. This is required for ! compatibility with `g77' and `f2c', and is implied by use of the ! `-ff2c' option. ! `-fcoarray=' ! `none' Disable coarray support; using coarray declarations and image-control statements will produce a compile-time error. (Default) ! `single' ! Single-image mode, i.e. `num_images()' is always one. ! `lib' Library-based coarray parallelization; a suitable GNU Fortran coarray library needs to be linked. ! `-fcheck=' Enable the generation of run-time checks; the argument shall be a comma-delimited list of the following keywords. Prefixing a check ! with `no-' disables it if it was activated by a previous specification. ! `all' ! Enable all run-time test of `-fcheck'. ! `array-temps' Warns at run time when for passing an actual argument a ! temporary array had to be generated. The information ! generated by this warning is sometimes useful in ! optimization, in order to avoid such temporaries. Note: The warning is only printed once per location. ! `bounds' Enable generation of run-time checks for array subscripts and against the declared minimum and maximum values. It also checks array indices for assumed and deferred shape arrays *************** the other form by either removing 'no-' *** 1485,1528 **** string lengths are equal for character array constructors without an explicit typespec. ! Some checks require that '-fcheck=bounds' is set for the compilation of the main program. Note: In the future this may also include other forms of checking, e.g., checking substring references. ! 'do' Enable generation of run-time checks for invalid modification of loop iteration variables. ! 'mem' Enable generation of run-time checks for memory allocation. Note: This option does not affect explicit allocations using ! the 'ALLOCATE' statement, which will be always checked. ! 'pointer' Enable generation of run-time checks for pointers and allocatables. ! 'recursion' Enable generation of run-time checks for recursively called subroutines and functions which are not marked as recursive. ! See also '-frecursive'. Note: This check does not work for OpenMP programs and is disabled if used together with ! '-frecursive' and '-fopenmp'. ! Example: Assuming you have a file 'foo.f90', the command gfortran -fcheck=all,no-array-temps foo.f90 will compile the file with all checks enabled as specified above except warnings for generated array temporaries. ! '-fbounds-check' ! Deprecated alias for '-fcheck=bounds'. ! '-fcheck-array-temporaries' ! Deprecated alias for '-fcheck=array-temps'. ! '-fmax-array-constructor=N' This option can be used to increase the upper limit permitted in array constructors. The code below requires this option to expand the array at compile time. --- 1490,1533 ---- string lengths are equal for character array constructors without an explicit typespec. ! Some checks require that `-fcheck=bounds' is set for the compilation of the main program. Note: In the future this may also include other forms of checking, e.g., checking substring references. ! `do' Enable generation of run-time checks for invalid modification of loop iteration variables. ! `mem' Enable generation of run-time checks for memory allocation. Note: This option does not affect explicit allocations using ! the `ALLOCATE' statement, which will be always checked. ! `pointer' Enable generation of run-time checks for pointers and allocatables. ! `recursion' Enable generation of run-time checks for recursively called subroutines and functions which are not marked as recursive. ! See also `-frecursive'. Note: This check does not work for OpenMP programs and is disabled if used together with ! `-frecursive' and `-fopenmp'. ! Example: Assuming you have a file `foo.f90', the command gfortran -fcheck=all,no-array-temps foo.f90 will compile the file with all checks enabled as specified above except warnings for generated array temporaries. ! `-fbounds-check' ! Deprecated alias for `-fcheck=bounds'. ! `-fcheck-array-temporaries' ! Deprecated alias for `-fcheck=array-temps'. ! `-fmax-array-constructor=N' This option can be used to increase the upper limit permitted in array constructors. The code below requires this option to expand the array at compile time. *************** the other form by either removing 'no-' *** 1535,1552 **** print '(10(I0,1X))', i end program test ! _Caution: This option can lead to long compile times and excessively large object files._ The default value for N is 65535. ! '-fmax-stack-var-size=N' This option specifies the size in bytes of the largest array that will be put on the stack; if the size is exceeded static memory is used (except in procedures marked as RECURSIVE). Use the option ! '-frecursive' to allow for recursive procedures which do not have a ! RECURSIVE attribute or for parallel programs. Use '-fno-automatic' ! to never use the stack. This option currently only affects local arrays declared with constant bounds, and may not apply to all character variables. --- 1540,1557 ---- print '(10(I0,1X))', i end program test ! _Caution: This option can lead to long compile times and excessively large object files._ The default value for N is 65535. ! `-fmax-stack-var-size=N' This option specifies the size in bytes of the largest array that will be put on the stack; if the size is exceeded static memory is used (except in procedures marked as RECURSIVE). Use the option ! `-frecursive' to allow for recursive procedures which do not have ! a RECURSIVE attribute or for parallel programs. Use ! `-fno-automatic' to never use the stack. This option currently only affects local arrays declared with constant bounds, and may not apply to all character variables. *************** the other form by either removing 'no-' *** 1554,1714 **** The default value for N is 32768. ! '-fstack-arrays' Adding this option will make the Fortran compiler put all local arrays, even those of unknown size onto stack memory. If your program uses very large local arrays it is possible that you will have to extend your runtime limits for stack memory on some ! operating systems. This flag is enabled by default at optimization ! level '-Ofast'. ! '-fpack-derived' This option tells GNU Fortran to pack derived type members as closely as possible. Code compiled with this option is likely to be incompatible with code compiled without this option, and may execute slower. ! '-frepack-arrays' In some circumstances GNU Fortran may pass assumed shape array sections via a descriptor describing a noncontiguous area of memory. This option adds code to the function prologue to repack the data into a contiguous block at runtime. ! This should result in faster accesses to the array. However it can ! introduce significant overhead to the function call, especially ! when the passed data is noncontiguous. ! '-fshort-enums' This option is provided for interoperability with C code that was ! compiled with the '-fshort-enums' option. It will make GNU Fortran ! choose the smallest 'INTEGER' kind a given enumerator set will fit ! in, and give all its enumerators this kind. ! '-fexternal-blas' ! This option will make 'gfortran' generate calls to BLAS functions ! for some matrix operations like 'MATMUL', instead of using our own algorithms, if the size of the matrices involved is larger than a ! given limit (see '-fblas-matmul-limit'). This may be profitable if ! an optimized vendor BLAS library is available. The BLAS library ! will have to be specified at link time. ! '-fblas-matmul-limit=N' ! Only significant when '-fexternal-blas' is in effect. Matrix multiplication of matrices with size larger than (or equal to) N will be performed by calls to BLAS functions, while others will be ! handled by 'gfortran' internal algorithms. If the matrices involved are not square, the size comparison is performed using the geometric mean of the dimensions of the argument and result matrices. The default value for N is 30. ! '-finline-matmul-limit=N' ! When front-end optimiztion is active, some calls to the 'MATMUL' intrinsic function will be inlined. This may result in code size increase if the size of the matrix cannot be determined at compile time, as code for both cases is generated. Setting ! '-finline-matmul-limit=0' will disable inlining in all cases. Setting this option with a value of N will produce inline code for ! matrices with size up to N. If the matrices involved are not square, the size comparison is performed using the geometric mean of the dimensions of the argument and result matrices. The default value for N is the value specified for ! '-fblas-matmul-limit' if this option is specified, or unlimitited otherwise. ! '-frecursive' Allow indirect recursion by forcing all local arrays to be ! allocated on the stack. This flag cannot be used together with ! '-fmax-stack-var-size=' or '-fno-automatic'. ! '-finit-local-zero' ! '-finit-integer=N' ! '-finit-real=' ! '-finit-logical=' ! '-finit-character=N' ! The '-finit-local-zero' option instructs the compiler to initialize ! local 'INTEGER', 'REAL', and 'COMPLEX' variables to zero, 'LOGICAL' ! variables to false, and 'CHARACTER' variables to a string of null ! bytes. Finer-grained initialization options are provided by the ! '-finit-integer=N', '-finit-real=' (which ! also initializes the real and imaginary parts of local 'COMPLEX' ! variables), '-finit-logical=', and '-finit-character=N' ! (where N is an ASCII character value) options. These options do ! not initialize * allocatable arrays * components of derived type variables ! * variables that appear in an 'EQUIVALENCE' statement. (These limitations may be removed in future releases). ! Note that the '-finit-real=nan' option initializes 'REAL' and ! 'COMPLEX' variables with a quiet NaN. For a signalling NaN use ! '-finit-real=snan'; note, however, that compile-time optimizations may convert them into quiet NaN and that trapping needs to be ! enabled (e.g. via '-ffpe-trap'). ! Finally, note that enabling any of the '-finit-*' options will ! silence warnings that would have been emitted by '-Wuninitialized' for the affected local variables. ! '-falign-commons' ! By default, 'gfortran' enforces proper alignment of all variables ! in a 'COMMON' block by padding them as needed. On certain platforms this is mandatory, on others it increases performance. ! If a 'COMMON' block is not declared with consistent data types everywhere, this padding can cause trouble, and ! '-fno-align-commons' can be used to disable automatic alignment. The same form of this option should be used for all files that ! share a 'COMMON' block. To avoid potential alignment issues in ! 'COMMON' blocks, it is recommended to order objects from largest to ! smallest. ! '-fno-protect-parens' By default the parentheses in expression are honored for all optimization levels such that the compiler does not do any ! re-association. Using '-fno-protect-parens' allows the compiler to ! reorder 'REAL' and 'COMPLEX' expressions to produce faster code. ! Note that for the re-association optimization '-fno-signed-zeros' ! and '-fno-trapping-math' need to be in effect. The parentheses ! protection is enabled by default, unless '-Ofast' is given. ! '-frealloc-lhs' An allocatable left-hand side of an intrinsic assignment is automatically (re)allocated if it is either unallocated or has a ! different shape. The option is enabled by default except when ! '-std=f95' is given. See also '-Wrealloc-lhs'. ! '-faggressive-function-elimination' Functions with identical argument lists are eliminated within ! statements, regardless of whether these functions are marked 'PURE' ! or not. For example, in a = f(b,c) + f(b,c) ! there will only be a single call to 'f'. This option only works if ! '-ffrontend-optimize' is in effect. ! '-ffrontend-optimize' This option performs front-end optimization, based on manipulating ! parts the Fortran parse tree. Enabled by default by any '-O' option. Optimizations enabled by this option include inlining ! calls to 'MATMUL', elimination of identical function calls within ! expressions, removing unnecessary calls to 'TRIM' in comparisons ! and assignments and replacing 'TRIM(a)' with 'a(1:LEN_TRIM(a))'. ! It can be deselected by specifying '-fno-frontend-optimize'. ! *Note Options for Code Generation Conventions: (gcc)Code Gen Options, ! for information on more options offered by the GBE shared by 'gfortran', ! 'gcc', and other GNU compilers.  File: gfortran.info, Node: Environment Variables, Prev: Code Gen Options, Up: Invoking GNU Fortran ! 2.10 Environment variables affecting 'gfortran' =============================================== ! The 'gfortran' compiler currently does not make use of any environment variables to control its operation above and beyond those that affect ! the operation of 'gcc'. *Note Environment Variables Affecting GCC: (gcc)Environment Variables, for information on environment variables. --- 1559,1722 ---- The default value for N is 32768. ! `-fstack-arrays' Adding this option will make the Fortran compiler put all local arrays, even those of unknown size onto stack memory. If your program uses very large local arrays it is possible that you will have to extend your runtime limits for stack memory on some ! operating systems. This flag is enabled by default at optimization ! level `-Ofast'. ! `-fpack-derived' This option tells GNU Fortran to pack derived type members as closely as possible. Code compiled with this option is likely to be incompatible with code compiled without this option, and may execute slower. ! `-frepack-arrays' In some circumstances GNU Fortran may pass assumed shape array sections via a descriptor describing a noncontiguous area of memory. This option adds code to the function prologue to repack the data into a contiguous block at runtime. ! This should result in faster accesses to the array. However it ! can introduce significant overhead to the function call, ! especially when the passed data is noncontiguous. ! `-fshort-enums' This option is provided for interoperability with C code that was ! compiled with the `-fshort-enums' option. It will make GNU ! Fortran choose the smallest `INTEGER' kind a given enumerator set ! will fit in, and give all its enumerators this kind. ! `-fexternal-blas' ! This option will make `gfortran' generate calls to BLAS functions ! for some matrix operations like `MATMUL', instead of using our own algorithms, if the size of the matrices involved is larger than a ! given limit (see `-fblas-matmul-limit'). This may be profitable ! if an optimized vendor BLAS library is available. The BLAS ! library will have to be specified at link time. ! `-fblas-matmul-limit=N' ! Only significant when `-fexternal-blas' is in effect. Matrix multiplication of matrices with size larger than (or equal to) N will be performed by calls to BLAS functions, while others will be ! handled by `gfortran' internal algorithms. If the matrices involved are not square, the size comparison is performed using the geometric mean of the dimensions of the argument and result matrices. The default value for N is 30. ! `-finline-matmul-limit=N' ! When front-end optimiztion is active, some calls to the `MATMUL' intrinsic function will be inlined. This may result in code size increase if the size of the matrix cannot be determined at compile time, as code for both cases is generated. Setting ! `-finline-matmul-limit=0' will disable inlining in all cases. Setting this option with a value of N will produce inline code for ! matrices with size up to N. If the matrices involved are not square, the size comparison is performed using the geometric mean of the dimensions of the argument and result matrices. The default value for N is the value specified for ! `-fblas-matmul-limit' if this option is specified, or unlimitited otherwise. ! `-frecursive' Allow indirect recursion by forcing all local arrays to be ! allocated on the stack. This flag cannot be used together with ! `-fmax-stack-var-size=' or `-fno-automatic'. ! `-finit-local-zero' ! `-finit-integer=N' ! `-finit-real=' ! `-finit-logical=' ! `-finit-character=N' ! The `-finit-local-zero' option instructs the compiler to ! initialize local `INTEGER', `REAL', and `COMPLEX' variables to ! zero, `LOGICAL' variables to false, and `CHARACTER' variables to a ! string of null bytes. Finer-grained initialization options are ! provided by the `-finit-integer=N', ! `-finit-real=' (which also initializes the ! real and imaginary parts of local `COMPLEX' variables), ! `-finit-logical=', and `-finit-character=N' (where N ! is an ASCII character value) options. These options do not ! initialize * allocatable arrays + * components of derived type variables ! ! * variables that appear in an `EQUIVALENCE' statement. (These limitations may be removed in future releases). ! Note that the `-finit-real=nan' option initializes `REAL' and ! `COMPLEX' variables with a quiet NaN. For a signalling NaN use ! `-finit-real=snan'; note, however, that compile-time optimizations may convert them into quiet NaN and that trapping needs to be ! enabled (e.g. via `-ffpe-trap'). ! Finally, note that enabling any of the `-finit-*' options will ! silence warnings that would have been emitted by `-Wuninitialized' for the affected local variables. ! `-falign-commons' ! By default, `gfortran' enforces proper alignment of all variables ! in a `COMMON' block by padding them as needed. On certain platforms this is mandatory, on others it increases performance. ! If a `COMMON' block is not declared with consistent data types everywhere, this padding can cause trouble, and ! `-fno-align-commons' can be used to disable automatic alignment. The same form of this option should be used for all files that ! share a `COMMON' block. To avoid potential alignment issues in ! `COMMON' blocks, it is recommended to order objects from largest ! to smallest. ! `-fno-protect-parens' By default the parentheses in expression are honored for all optimization levels such that the compiler does not do any ! re-association. Using `-fno-protect-parens' allows the compiler to ! reorder `REAL' and `COMPLEX' expressions to produce faster code. ! Note that for the re-association optimization `-fno-signed-zeros' ! and `-fno-trapping-math' need to be in effect. The parentheses ! protection is enabled by default, unless `-Ofast' is given. ! `-frealloc-lhs' An allocatable left-hand side of an intrinsic assignment is automatically (re)allocated if it is either unallocated or has a ! different shape. The option is enabled by default except when ! `-std=f95' is given. See also `-Wrealloc-lhs'. ! `-faggressive-function-elimination' Functions with identical argument lists are eliminated within ! statements, regardless of whether these functions are marked ! `PURE' or not. For example, in a = f(b,c) + f(b,c) ! there will only be a single call to `f'. This option only works ! if `-ffrontend-optimize' is in effect. ! `-ffrontend-optimize' This option performs front-end optimization, based on manipulating ! parts the Fortran parse tree. Enabled by default by any `-O' option. Optimizations enabled by this option include inlining ! calls to `MATMUL', elimination of identical function calls within ! expressions, removing unnecessary calls to `TRIM' in comparisons ! and assignments and replacing `TRIM(a)' with `a(1:LEN_TRIM(a))'. ! It can be deselected by specifying `-fno-frontend-optimize'. ! *Note Options for Code Generation Conventions: (gcc)Code Gen ! Options, for information on more options offered by the GBE shared by ! `gfortran', `gcc', and other GNU compilers.  File: gfortran.info, Node: Environment Variables, Prev: Code Gen Options, Up: Invoking GNU Fortran ! 2.10 Environment variables affecting `gfortran' =============================================== ! The `gfortran' compiler currently does not make use of any environment variables to control its operation above and beyond those that affect ! the operation of `gcc'. *Note Environment Variables Affecting GCC: (gcc)Environment Variables, for information on environment variables. *************** behavior of programs compiled with GNU F *** 1719,1728 ****  File: gfortran.info, Node: Runtime, Next: Fortran 2003 and 2008 status, Prev: Invoking GNU Fortran, Up: Top ! 3 Runtime: Influencing runtime behavior with environment variables ! ****************************************************************** ! The behavior of the 'gfortran' can be influenced by environment variables. Malformed environment variables are silently ignored. --- 1727,1736 ----  File: gfortran.info, Node: Runtime, Next: Fortran 2003 and 2008 status, Prev: Invoking GNU Fortran, Up: Top ! 3 Runtime: Influencing runtime behavior with environment variables ! ******************************************************************* ! The behavior of the `gfortran' can be influenced by environment variables. Malformed environment variables are silently ignored. *************** variables. *** 1745,1770 ****  File: gfortran.info, Node: TMPDIR, Next: GFORTRAN_STDIN_UNIT, Up: Runtime ! 3.1 'TMPDIR'--Directory for scratch files ========================================= ! When opening a file with 'STATUS='SCRATCH'', GNU Fortran tries to create ! the file in one of the potential directories by testing each directory ! in the order below. ! 1. The environment variable 'TMPDIR', if it exists. ! 2. On the MinGW target, the directory returned by the 'GetTempPath' ! function. Alternatively, on the Cygwin target, the 'TMP' and ! 'TEMP' environment variables, if they exist, in that order. ! 3. The 'P_tmpdir' macro if it is defined, otherwise the directory ! '/tmp'.  File: gfortran.info, Node: GFORTRAN_STDIN_UNIT, Next: GFORTRAN_STDOUT_UNIT, Prev: TMPDIR, Up: Runtime ! 3.2 'GFORTRAN_STDIN_UNIT'--Unit number for standard input ========================================================= This environment variable can be used to select the unit number --- 1753,1778 ----  File: gfortran.info, Node: TMPDIR, Next: GFORTRAN_STDIN_UNIT, Up: Runtime ! 3.1 `TMPDIR'--Directory for scratch files ========================================= ! When opening a file with `STATUS='SCRATCH'', GNU Fortran tries to ! create the file in one of the potential directories by testing each ! directory in the order below. ! 1. The environment variable `TMPDIR', if it exists. ! 2. On the MinGW target, the directory returned by the `GetTempPath' ! function. Alternatively, on the Cygwin target, the `TMP' and ! `TEMP' environment variables, if they exist, in that order. ! 3. The `P_tmpdir' macro if it is defined, otherwise the directory ! `/tmp'.  File: gfortran.info, Node: GFORTRAN_STDIN_UNIT, Next: GFORTRAN_STDOUT_UNIT, Prev: TMPDIR, Up: Runtime ! 3.2 `GFORTRAN_STDIN_UNIT'--Unit number for standard input ========================================================= This environment variable can be used to select the unit number *************** default value is 5. *** 1774,1780 ****  File: gfortran.info, Node: GFORTRAN_STDOUT_UNIT, Next: GFORTRAN_STDERR_UNIT, Prev: GFORTRAN_STDIN_UNIT, Up: Runtime ! 3.3 'GFORTRAN_STDOUT_UNIT'--Unit number for standard output =========================================================== This environment variable can be used to select the unit number --- 1782,1788 ----  File: gfortran.info, Node: GFORTRAN_STDOUT_UNIT, Next: GFORTRAN_STDERR_UNIT, Prev: GFORTRAN_STDIN_UNIT, Up: Runtime ! 3.3 `GFORTRAN_STDOUT_UNIT'--Unit number for standard output =========================================================== This environment variable can be used to select the unit number *************** default value is 6. *** 1784,1790 ****  File: gfortran.info, Node: GFORTRAN_STDERR_UNIT, Next: GFORTRAN_UNBUFFERED_ALL, Prev: GFORTRAN_STDOUT_UNIT, Up: Runtime ! 3.4 'GFORTRAN_STDERR_UNIT'--Unit number for standard error ========================================================== This environment variable can be used to select the unit number --- 1792,1798 ----  File: gfortran.info, Node: GFORTRAN_STDERR_UNIT, Next: GFORTRAN_UNBUFFERED_ALL, Prev: GFORTRAN_STDOUT_UNIT, Up: Runtime ! 3.4 `GFORTRAN_STDERR_UNIT'--Unit number for standard error ========================================================== This environment variable can be used to select the unit number *************** default value is 0. *** 1794,1856 ****  File: gfortran.info, Node: GFORTRAN_UNBUFFERED_ALL, Next: GFORTRAN_UNBUFFERED_PRECONNECTED, Prev: GFORTRAN_STDERR_UNIT, Up: Runtime ! 3.5 'GFORTRAN_UNBUFFERED_ALL'--Do not buffer I/O on all units ============================================================= This environment variable controls whether all I/O is unbuffered. If ! the first letter is 'y', 'Y' or '1', all I/O is unbuffered. This will slow down small sequential reads and writes. If the first letter is ! 'n', 'N' or '0', I/O is buffered. This is the default.  File: gfortran.info, Node: GFORTRAN_UNBUFFERED_PRECONNECTED, Next: GFORTRAN_SHOW_LOCUS, Prev: GFORTRAN_UNBUFFERED_ALL, Up: Runtime ! 3.6 'GFORTRAN_UNBUFFERED_PRECONNECTED'--Do not buffer I/O on preconnected units =============================================================================== ! The environment variable named 'GFORTRAN_UNBUFFERED_PRECONNECTED' controls whether I/O on a preconnected unit (i.e. STDOUT or STDERR) is ! unbuffered. If the first letter is 'y', 'Y' or '1', I/O is unbuffered. This will slow down small sequential reads and writes. If the first ! letter is 'n', 'N' or '0', I/O is buffered. This is the default.  File: gfortran.info, Node: GFORTRAN_SHOW_LOCUS, Next: GFORTRAN_OPTIONAL_PLUS, Prev: GFORTRAN_UNBUFFERED_PRECONNECTED, Up: Runtime ! 3.7 'GFORTRAN_SHOW_LOCUS'--Show location for runtime errors =========================================================== ! If the first letter is 'y', 'Y' or '1', filename and line numbers for ! runtime errors are printed. If the first letter is 'n', 'N' or '0', do not print filename and line numbers for runtime errors. The default is to print the location.  File: gfortran.info, Node: GFORTRAN_OPTIONAL_PLUS, Next: GFORTRAN_DEFAULT_RECL, Prev: GFORTRAN_SHOW_LOCUS, Up: Runtime ! 3.8 'GFORTRAN_OPTIONAL_PLUS'--Print leading + where permitted ============================================================= ! If the first letter is 'y', 'Y' or '1', a plus sign is printed where ! permitted by the Fortran standard. If the first letter is 'n', 'N' or ! '0', a plus sign is not printed in most cases. Default is not to print plus signs.  File: gfortran.info, Node: GFORTRAN_DEFAULT_RECL, Next: GFORTRAN_LIST_SEPARATOR, Prev: GFORTRAN_OPTIONAL_PLUS, Up: Runtime ! 3.9 'GFORTRAN_DEFAULT_RECL'--Default record length for new files ================================================================ ! This environment variable specifies the default record length, in bytes, ! for files which are opened without a 'RECL' tag in the 'OPEN' statement. ! This must be a positive integer. The default value is 1073741824 bytes ! (1 GB).  File: gfortran.info, Node: GFORTRAN_LIST_SEPARATOR, Next: GFORTRAN_CONVERT_UNIT, Prev: GFORTRAN_DEFAULT_RECL, Up: Runtime ! 3.10 'GFORTRAN_LIST_SEPARATOR'--Separator for list output ========================================================= This environment variable specifies the separator when writing --- 1802,1864 ----  File: gfortran.info, Node: GFORTRAN_UNBUFFERED_ALL, Next: GFORTRAN_UNBUFFERED_PRECONNECTED, Prev: GFORTRAN_STDERR_UNIT, Up: Runtime ! 3.5 `GFORTRAN_UNBUFFERED_ALL'--Do not buffer I/O on all units ============================================================= This environment variable controls whether all I/O is unbuffered. If ! the first letter is `y', `Y' or `1', all I/O is unbuffered. This will slow down small sequential reads and writes. If the first letter is ! `n', `N' or `0', I/O is buffered. This is the default.  File: gfortran.info, Node: GFORTRAN_UNBUFFERED_PRECONNECTED, Next: GFORTRAN_SHOW_LOCUS, Prev: GFORTRAN_UNBUFFERED_ALL, Up: Runtime ! 3.6 `GFORTRAN_UNBUFFERED_PRECONNECTED'--Do not buffer I/O on preconnected units =============================================================================== ! The environment variable named `GFORTRAN_UNBUFFERED_PRECONNECTED' controls whether I/O on a preconnected unit (i.e. STDOUT or STDERR) is ! unbuffered. If the first letter is `y', `Y' or `1', I/O is unbuffered. This will slow down small sequential reads and writes. If the first ! letter is `n', `N' or `0', I/O is buffered. This is the default.  File: gfortran.info, Node: GFORTRAN_SHOW_LOCUS, Next: GFORTRAN_OPTIONAL_PLUS, Prev: GFORTRAN_UNBUFFERED_PRECONNECTED, Up: Runtime ! 3.7 `GFORTRAN_SHOW_LOCUS'--Show location for runtime errors =========================================================== ! If the first letter is `y', `Y' or `1', filename and line numbers for ! runtime errors are printed. If the first letter is `n', `N' or `0', do not print filename and line numbers for runtime errors. The default is to print the location.  File: gfortran.info, Node: GFORTRAN_OPTIONAL_PLUS, Next: GFORTRAN_DEFAULT_RECL, Prev: GFORTRAN_SHOW_LOCUS, Up: Runtime ! 3.8 `GFORTRAN_OPTIONAL_PLUS'--Print leading + where permitted ============================================================= ! If the first letter is `y', `Y' or `1', a plus sign is printed where ! permitted by the Fortran standard. If the first letter is `n', `N' or ! `0', a plus sign is not printed in most cases. Default is not to print plus signs.  File: gfortran.info, Node: GFORTRAN_DEFAULT_RECL, Next: GFORTRAN_LIST_SEPARATOR, Prev: GFORTRAN_OPTIONAL_PLUS, Up: Runtime ! 3.9 `GFORTRAN_DEFAULT_RECL'--Default record length for new files ================================================================ ! This environment variable specifies the default record length, in ! bytes, for files which are opened without a `RECL' tag in the `OPEN' ! statement. This must be a positive integer. The default value is ! 1073741824 bytes (1 GB).  File: gfortran.info, Node: GFORTRAN_LIST_SEPARATOR, Next: GFORTRAN_CONVERT_UNIT, Prev: GFORTRAN_DEFAULT_RECL, Up: Runtime ! 3.10 `GFORTRAN_LIST_SEPARATOR'--Separator for list output ========================================================= This environment variable specifies the separator when writing *************** list-directed output. It may contain an *** 1858,1907 **** one comma. If you specify this on the command line, be sure to quote spaces, as in $ GFORTRAN_LIST_SEPARATOR=' , ' ./a.out ! when 'a.out' is the compiled Fortran program that you want to run. Default is a single space.  File: gfortran.info, Node: GFORTRAN_CONVERT_UNIT, Next: GFORTRAN_ERROR_BACKTRACE, Prev: GFORTRAN_LIST_SEPARATOR, Up: Runtime ! 3.11 'GFORTRAN_CONVERT_UNIT'--Set endianness for unformatted I/O ================================================================ ! By setting the 'GFORTRAN_CONVERT_UNIT' variable, it is possible to ! change the representation of data for unformatted files. The syntax for ! the 'GFORTRAN_CONVERT_UNIT' variable is: GFORTRAN_CONVERT_UNIT: mode | mode ';' exception | exception ; mode: 'native' | 'swap' | 'big_endian' | 'little_endian' ; exception: mode ':' unit_list | unit_list ; unit_list: unit_spec | unit_list unit_spec ; unit_spec: INTEGER | INTEGER '-' INTEGER ; ! The variable consists of an optional default mode, followed by a list ! of optional exceptions, which are separated by semicolons from the preceding default and each other. Each exception consists of a format ! and a comma-separated list of units. Valid values for the modes are the ! same as for the 'CONVERT' specifier: ! 'NATIVE' Use the native format. This is the default. ! 'SWAP' Swap between little- and big-endian. ! 'LITTLE_ENDIAN' Use the little-endian format for unformatted files. ! 'BIG_ENDIAN' Use the big-endian format for unformatted files. ! A missing mode for an exception is taken to mean 'BIG_ENDIAN'. ! Examples of values for 'GFORTRAN_CONVERT_UNIT' are: ! ''big_endian'' Do all unformatted I/O in big_endian mode. ! ''little_endian;native:10-20,25'' Do all unformatted I/O in little_endian mode, except for units 10 to 20 and 25, which are in native format. ! ''10-20'' Units 10 to 20 are big-endian, the rest is native. Setting the environment variables should be done on the command line ! or via the 'export' command for 'sh'-compatible shells and via 'setenv' ! for 'csh'-compatible shells. ! Example for 'sh': $ gfortran foo.f90 $ GFORTRAN_CONVERT_UNIT='big_endian;native:10-20' ./a.out ! Example code for 'csh': % gfortran foo.f90 % setenv GFORTRAN_CONVERT_UNIT 'big_endian;native:10-20' % ./a.out --- 1866,1920 ---- one comma. If you specify this on the command line, be sure to quote spaces, as in $ GFORTRAN_LIST_SEPARATOR=' , ' ./a.out ! when `a.out' is the compiled Fortran program that you want to run. Default is a single space.  File: gfortran.info, Node: GFORTRAN_CONVERT_UNIT, Next: GFORTRAN_ERROR_BACKTRACE, Prev: GFORTRAN_LIST_SEPARATOR, Up: Runtime ! 3.11 `GFORTRAN_CONVERT_UNIT'--Set endianness for unformatted I/O ================================================================ ! By setting the `GFORTRAN_CONVERT_UNIT' variable, it is possible to ! change the representation of data for unformatted files. The syntax ! for the `GFORTRAN_CONVERT_UNIT' variable is: GFORTRAN_CONVERT_UNIT: mode | mode ';' exception | exception ; mode: 'native' | 'swap' | 'big_endian' | 'little_endian' ; exception: mode ':' unit_list | unit_list ; unit_list: unit_spec | unit_list unit_spec ; unit_spec: INTEGER | INTEGER '-' INTEGER ; ! The variable consists of an optional default mode, followed by a ! list of optional exceptions, which are separated by semicolons from the preceding default and each other. Each exception consists of a format ! and a comma-separated list of units. Valid values for the modes are ! the same as for the `CONVERT' specifier: ! `NATIVE' Use the native format. This is the default. ! ! `SWAP' Swap between little- and big-endian. ! ! `LITTLE_ENDIAN' Use the little-endian format for unformatted files. ! ! `BIG_ENDIAN' Use the big-endian format for unformatted files. ! A missing mode for an exception is taken to mean `BIG_ENDIAN'. ! Examples of values for `GFORTRAN_CONVERT_UNIT' are: ! `'big_endian'' Do all unformatted I/O in big_endian mode. ! ! `'little_endian;native:10-20,25'' Do all unformatted I/O in little_endian mode, except for units 10 to 20 and 25, which are in native format. ! ! `'10-20'' Units 10 to 20 are big-endian, the rest is native. Setting the environment variables should be done on the command line ! or via the `export' command for `sh'-compatible shells and via `setenv' ! for `csh'-compatible shells. ! Example for `sh': $ gfortran foo.f90 $ GFORTRAN_CONVERT_UNIT='big_endian;native:10-20' ./a.out ! Example code for `csh': % gfortran foo.f90 % setenv GFORTRAN_CONVERT_UNIT 'big_endian;native:10-20' % ./a.out *************** for 'csh'-compatible shells. *** 1910,1919 **** carries a significant speed overhead. If speed in this area matters to you, it is best if you use this only for data that needs to be portable. ! *Note CONVERT specifier::, for an alternative way to specify the data ! representation for unformatted files. *Note Runtime Options::, for setting a default data representation for the whole program. The ! 'CONVERT' specifier overrides the '-fconvert' compile options. _Note that the values specified via the GFORTRAN_CONVERT_UNIT environment variable will override the CONVERT specifier in the open --- 1923,1932 ---- carries a significant speed overhead. If speed in this area matters to you, it is best if you use this only for data that needs to be portable. ! *Note CONVERT specifier::, for an alternative way to specify the ! data representation for unformatted files. *Note Runtime Options::, for setting a default data representation for the whole program. The ! `CONVERT' specifier overrides the `-fconvert' compile options. _Note that the values specified via the GFORTRAN_CONVERT_UNIT environment variable will override the CONVERT specifier in the open *************** not have the source code of their progra *** 1923,1936 ****  File: gfortran.info, Node: GFORTRAN_ERROR_BACKTRACE, Prev: GFORTRAN_CONVERT_UNIT, Up: Runtime ! 3.12 'GFORTRAN_ERROR_BACKTRACE'--Show backtrace on run-time errors ================================================================== ! If the 'GFORTRAN_ERROR_BACKTRACE' variable is set to 'y', 'Y' or '1' (only the first letter is relevant) then a backtrace is printed when a serious run-time error occurs. To disable the backtracing, set the ! variable to 'n', 'N', '0'. Default is to print a backtrace unless the ! '-fno-backtrace' compile option was used.  File: gfortran.info, Node: Fortran 2003 and 2008 status, Next: Compiler Characteristics, Prev: Runtime, Up: Top --- 1936,1949 ----  File: gfortran.info, Node: GFORTRAN_ERROR_BACKTRACE, Prev: GFORTRAN_CONVERT_UNIT, Up: Runtime ! 3.12 `GFORTRAN_ERROR_BACKTRACE'--Show backtrace on run-time errors ================================================================== ! If the `GFORTRAN_ERROR_BACKTRACE' variable is set to `y', `Y' or `1' (only the first letter is relevant) then a backtrace is printed when a serious run-time error occurs. To disable the backtracing, set the ! variable to `n', `N', `0'. Default is to print a backtrace unless the ! `-fno-backtrace' compile option was used.  File: gfortran.info, Node: Fortran 2003 and 2008 status, Next: Compiler Characteristics, Prev: Runtime, Up: Top *************** can be found below. See also the wiki p *** 1956,2083 **** (https://gcc.gnu.org/wiki/Fortran2003) about Fortran 2003. * Procedure pointers including procedure-pointer components with ! 'PASS' attribute. * Procedures which are bound to a derived type (type-bound ! procedures) including 'PASS', 'PROCEDURE' and 'GENERIC', and operators bound to a type. * Abstract interfaces and type extension with the possibility to override type-bound procedures or to have deferred binding. ! * Polymorphic entities ("'CLASS'") for derived types and unlimited ! polymorphism ("'CLASS(*)'") - including 'SAME_TYPE_AS', ! 'EXTENDS_TYPE_OF' and 'SELECT TYPE' for scalars and arrays and finalization. * Generic interface names, which have the same name as derived types, ! are now supported. This allows one to write constructor functions. Note that Fortran does not support static constructor functions. For static variables, only default initialization or structure-constructor initialization are available. ! * The 'ASSOCIATE' construct. * Interoperability with C including enumerations, * In structure constructors the components with default values may be omitted. ! * Extensions to the 'ALLOCATE' statement, allowing for a type-specification with type parameter and for allocation and ! initialization from a 'SOURCE=' expression; 'ALLOCATE' and ! 'DEALLOCATE' optionally return an error message string via ! 'ERRMSG='. * Reallocation on assignment: If an intrinsic assignment is used, an allocatable variable on the left-hand side is automatically allocated (if unallocated) or reallocated (if the shape is ! different). Currently, scalar deferred character length left-hand sides are correctly handled but arrays are not yet fully implemented. * Deferred-length character variables and scalar deferred-length ! character components of derived types are supported. (Note that array-valued compoents are not yet implemented.) ! * Transferring of allocations via 'MOVE_ALLOC'. ! * The 'PRIVATE' and 'PUBLIC' attributes may be given individually to derived-type components. * In pointer assignments, the lower bound may be specified and the remapping of elements is supported. ! * For pointers an 'INTENT' may be specified which affect the association status not the value of the pointer target. ! * Intrinsics 'command_argument_count', 'get_command', ! 'get_command_argument', and 'get_environment_variable'. ! * Support for Unicode characters (ISO 10646) and UTF-8, including the ! 'SELECTED_CHAR_KIND' and 'NEW_LINE' intrinsic functions. * Support for binary, octal and hexadecimal (BOZ) constants in the ! intrinsic functions 'INT', 'REAL', 'CMPLX' and 'DBLE'. * Support for namelist variables with allocatable and pointer attribute and nonconstant length type parameter. ! * Array constructors using square brackets. That is, '[...]' rather ! than '(/.../)'. Type-specification for array constructors like '(/ ! some-type :: ... /)'. * Extensions to the specification and initialization expressions, including the support for intrinsics with real and complex arguments. ! * Support for the asynchronous input/output syntax; however, the data ! transfer is currently always synchronously performed. ! * 'FLUSH' statement. ! * 'IOMSG=' specifier for I/O statements. ! * Support for the declaration of enumeration constants via the 'ENUM' ! and 'ENUMERATOR' statements. Interoperability with 'gcc' is ! guaranteed also for the case where the '-fshort-enums' command line ! option is given. * TR 15581: ! * 'ALLOCATABLE' dummy arguments. ! * 'ALLOCATABLE' function results ! * 'ALLOCATABLE' components of derived types ! * The 'OPEN' statement supports the 'ACCESS='STREAM'' specifier, allowing I/O without any record structure. * Namelist input/output for internal files. * Minor I/O features: Rounding during formatted output, using of a decimal comma instead of a decimal point, setting whether a plus ! sign should appear for positive numbers. On systems where 'strtod' honours the rounding mode, the rounding mode is also supported for input. ! * The 'PROTECTED' statement and attribute. ! * The 'VALUE' statement and attribute. ! * The 'VOLATILE' statement and attribute. ! * The 'IMPORT' statement, allowing to import host-associated derived types. ! * The intrinsic modules 'ISO_FORTRAN_ENVIRONMENT' is supported, which ! contains parameters of the I/O units, storage sizes. Additionally, ! procedures for C interoperability are available in the ! 'ISO_C_BINDING' module. ! * 'USE' statement with 'INTRINSIC' and 'NON_INTRINSIC' attribute; ! supported intrinsic modules: 'ISO_FORTRAN_ENV', 'ISO_C_BINDING', ! 'OMP_LIB' and 'OMP_LIB_KINDS', and 'OPENACC'. - * Renaming of operators in the 'USE' statement.  File: gfortran.info, Node: Fortran 2008 status, Next: TS 29113 status, Prev: Fortran 2003 status, Up: Fortran 2003 and 2008 status --- 1969,2099 ---- (https://gcc.gnu.org/wiki/Fortran2003) about Fortran 2003. * Procedure pointers including procedure-pointer components with ! `PASS' attribute. * Procedures which are bound to a derived type (type-bound ! procedures) including `PASS', `PROCEDURE' and `GENERIC', and operators bound to a type. * Abstract interfaces and type extension with the possibility to override type-bound procedures or to have deferred binding. ! * Polymorphic entities ("`CLASS'") for derived types and unlimited ! polymorphism ("`CLASS(*)'") - including `SAME_TYPE_AS', ! `EXTENDS_TYPE_OF' and `SELECT TYPE' for scalars and arrays and finalization. * Generic interface names, which have the same name as derived types, ! are now supported. This allows one to write constructor functions. Note that Fortran does not support static constructor functions. For static variables, only default initialization or structure-constructor initialization are available. ! * The `ASSOCIATE' construct. * Interoperability with C including enumerations, * In structure constructors the components with default values may be omitted. ! * Extensions to the `ALLOCATE' statement, allowing for a type-specification with type parameter and for allocation and ! initialization from a `SOURCE=' expression; `ALLOCATE' and ! `DEALLOCATE' optionally return an error message string via ! `ERRMSG='. * Reallocation on assignment: If an intrinsic assignment is used, an allocatable variable on the left-hand side is automatically allocated (if unallocated) or reallocated (if the shape is ! different). Currently, scalar deferred character length left-hand sides are correctly handled but arrays are not yet fully implemented. * Deferred-length character variables and scalar deferred-length ! character components of derived types are supported. (Note that array-valued compoents are not yet implemented.) ! * Transferring of allocations via `MOVE_ALLOC'. ! * The `PRIVATE' and `PUBLIC' attributes may be given individually to derived-type components. * In pointer assignments, the lower bound may be specified and the remapping of elements is supported. ! * For pointers an `INTENT' may be specified which affect the association status not the value of the pointer target. ! * Intrinsics `command_argument_count', `get_command', ! `get_command_argument', and `get_environment_variable'. ! * Support for Unicode characters (ISO 10646) and UTF-8, including ! the `SELECTED_CHAR_KIND' and `NEW_LINE' intrinsic functions. * Support for binary, octal and hexadecimal (BOZ) constants in the ! intrinsic functions `INT', `REAL', `CMPLX' and `DBLE'. * Support for namelist variables with allocatable and pointer attribute and nonconstant length type parameter. ! * Array constructors using square brackets. That is, `[...]' rather ! than `(/.../)'. Type-specification for array constructors like ! `(/ some-type :: ... /)'. * Extensions to the specification and initialization expressions, including the support for intrinsics with real and complex arguments. ! * Support for the asynchronous input/output syntax; however, the ! data transfer is currently always synchronously performed. ! * `FLUSH' statement. ! * `IOMSG=' specifier for I/O statements. ! * Support for the declaration of enumeration constants via the ! `ENUM' and `ENUMERATOR' statements. Interoperability with `gcc' ! is guaranteed also for the case where the `-fshort-enums' command ! line option is given. * TR 15581: ! * `ALLOCATABLE' dummy arguments. ! * `ALLOCATABLE' function results ! ! * `ALLOCATABLE' components of derived types ! ! * The `OPEN' statement supports the `ACCESS='STREAM'' specifier, allowing I/O without any record structure. * Namelist input/output for internal files. * Minor I/O features: Rounding during formatted output, using of a decimal comma instead of a decimal point, setting whether a plus ! sign should appear for positive numbers. On systems where `strtod' honours the rounding mode, the rounding mode is also supported for input. ! * The `PROTECTED' statement and attribute. ! * The `VALUE' statement and attribute. ! * The `VOLATILE' statement and attribute. ! * The `IMPORT' statement, allowing to import host-associated derived types. ! * The intrinsic modules `ISO_FORTRAN_ENVIRONMENT' is supported, ! which contains parameters of the I/O units, storage sizes. ! Additionally, procedures for C interoperability are available in ! the `ISO_C_BINDING' module. ! * `USE' statement with `INTRINSIC' and `NON_INTRINSIC' attribute; ! supported intrinsic modules: `ISO_FORTRAN_ENV', `ISO_C_BINDING', ! `OMP_LIB' and `OMP_LIB_KINDS', and `OPENACC'. ! ! * Renaming of operators in the `USE' statement.  File: gfortran.info, Node: Fortran 2008 status, Next: TS 29113 status, Prev: Fortran 2003 status, Up: Fortran 2003 and 2008 status *************** informally known as Fortran 2008. The o *** 2090,2099 **** from International Organization for Standardization (ISO) or its national member organizations. The the final draft (FDIS) can be downloaded free of charge from ! . Fortran is developed by the Working Group 5 of Sub-Committee 22 of the Joint Technical Committee 1 of the International Organization for Standardization and the ! International Electrotechnical Commission (IEC). This group is known as WG5 (http://www.nag.co.uk/sc22wg5/). The GNU Fortran compiler supports several of the new features of --- 2106,2115 ---- from International Organization for Standardization (ISO) or its national member organizations. The the final draft (FDIS) can be downloaded free of charge from ! `http://www.nag.co.uk/sc22wg5/links.html'. Fortran is developed by the Working Group 5 of Sub-Committee 22 of the Joint Technical Committee 1 of the International Organization for Standardization and the ! International Electrotechnical Commission (IEC). This group is known as WG5 (http://www.nag.co.uk/sc22wg5/). The GNU Fortran compiler supports several of the new features of *************** Fortran 2008; the wiki (https://gcc.gnu. *** 2101,2202 **** some information about the current Fortran 2008 implementation status. In particular, the following is implemented. ! * The '-std=f2008' option and support for the file extensions '.f08' ! and '.F08'. ! * The 'OPEN' statement now supports the 'NEWUNIT=' option, which returns a unique file unit, thus preventing inadvertent use of the same unit in different parts of the program. ! * The 'g0' format descriptor and unlimited format items. ! * The mathematical intrinsics 'ASINH', 'ACOSH', 'ATANH', 'ERF', ! 'ERFC', 'GAMMA', 'LOG_GAMMA', 'BESSEL_J0', 'BESSEL_J1', ! 'BESSEL_JN', 'BESSEL_Y0', 'BESSEL_Y1', 'BESSEL_YN', 'HYPOT', ! 'NORM2', and 'ERFC_SCALED'. ! * Using complex arguments with 'TAN', 'SINH', 'COSH', 'TANH', 'ASIN', ! 'ACOS', and 'ATAN' is now possible; 'ATAN'(Y,X) is now an alias for ! 'ATAN2'(Y,X). ! * Support of the 'PARITY' intrinsic functions. ! * The following bit intrinsics: 'LEADZ' and 'TRAILZ' for counting the ! number of leading and trailing zero bits, 'POPCNT' and 'POPPAR' for ! counting the number of one bits and returning the parity; 'BGE', ! 'BGT', 'BLE', and 'BLT' for bitwise comparisons; 'DSHIFTL' and ! 'DSHIFTR' for combined left and right shifts, 'MASKL' and 'MASKR' ! for simple left and right justified masks, 'MERGE_BITS' for a ! bitwise merge using a mask, 'SHIFTA', 'SHIFTL' and 'SHIFTR' for ! shift operations, and the transformational bit intrinsics 'IALL', ! 'IANY' and 'IPARITY'. ! * Support of the 'EXECUTE_COMMAND_LINE' intrinsic subroutine. ! * Support for the 'STORAGE_SIZE' intrinsic inquiry function. ! * The 'INT{8,16,32}' and 'REAL{32,64,128}' kind type parameters and ! the array-valued named constants 'INTEGER_KINDS', 'LOGICAL_KINDS', ! 'REAL_KINDS' and 'CHARACTER_KINDS' of the intrinsic module ! 'ISO_FORTRAN_ENV'. ! * The module procedures 'C_SIZEOF' of the intrinsic module ! 'ISO_C_BINDINGS' and 'COMPILER_VERSION' and 'COMPILER_OPTIONS' of ! 'ISO_FORTRAN_ENV'. ! * Coarray support for serial programs with '-fcoarray=single' flag and experimental support for multiple images with the ! '-fcoarray=lib' flag. ! * Submodules are supported. It should noted that 'MODULEs' do not ! produce the smod file needed by the descendent 'SUBMODULEs' unless ! they contain at least one 'MODULE PROCEDURE' interface. The reason ! for this is that 'SUBMODULEs' are useless without 'MODULE ! PROCEDUREs'. See http://j3-fortran.org/doc/meeting/207/15-209.txt ! for a discussion and a draft interpretation. Adopting this interpretation has the advantage that code that does not use submodules does not generate smod files. ! * The 'DO CONCURRENT' construct is supported. ! * The 'BLOCK' construct is supported. ! * The 'STOP' and the new 'ERROR STOP' statements now support all ! constant expressions. Both show the signals which were signaling at termination. ! * Support for the 'CONTIGUOUS' attribute. ! * Support for 'ALLOCATE' with 'MOLD'. ! * Support for the 'IMPURE' attribute for procedures, which allows for ! 'ELEMENTAL' procedures without the restrictions of 'PURE'. ! * Null pointers (including 'NULL()') and not-allocated variables can be used as actual argument to optional non-pointer, non-allocatable dummy arguments, denoting an absent argument. ! * Non-pointer variables with 'TARGET' attribute can be used as actual ! argument to 'POINTER' dummies with 'INTENT(IN)'. * Pointers including procedure pointers and those in a derived type (pointer components) can now be initialized by a target instead of ! only by 'NULL'. ! * The 'EXIT' statement (with construct-name) can be now be used to ! leave not only the 'DO' but also the 'ASSOCIATE', 'BLOCK', 'IF', ! 'SELECT CASE' and 'SELECT TYPE' constructs. * Internal procedures can now be used as actual argument. ! * Minor features: obsolesce diagnostics for 'ENTRY' with ! '-std=f2008'; a line may start with a semicolon; for internal and ! module procedures 'END' can be used instead of 'END SUBROUTINE' and ! 'END FUNCTION'; 'SELECTED_REAL_KIND' now also takes a 'RADIX' argument; intrinsic types are supported for ! 'TYPE'(INTRINSIC-TYPE-SPEC); multiple type-bound procedures can be ! declared in a single 'PROCEDURE' statement; implied-shape arrays ! are supported for named constants ('PARAMETER').  File: gfortran.info, Node: TS 29113 status, Next: TS 18508 status, Prev: Fortran 2008 status, Up: Fortran 2003 and 2008 status --- 2117,2218 ---- some information about the current Fortran 2008 implementation status. In particular, the following is implemented. ! * The `-std=f2008' option and support for the file extensions `.f08' ! and `.F08'. ! * The `OPEN' statement now supports the `NEWUNIT=' option, which returns a unique file unit, thus preventing inadvertent use of the same unit in different parts of the program. ! * The `g0' format descriptor and unlimited format items. ! * The mathematical intrinsics `ASINH', `ACOSH', `ATANH', `ERF', ! `ERFC', `GAMMA', `LOG_GAMMA', `BESSEL_J0', `BESSEL_J1', ! `BESSEL_JN', `BESSEL_Y0', `BESSEL_Y1', `BESSEL_YN', `HYPOT', ! `NORM2', and `ERFC_SCALED'. ! * Using complex arguments with `TAN', `SINH', `COSH', `TANH', ! `ASIN', `ACOS', and `ATAN' is now possible; `ATAN'(Y,X) is now an ! alias for `ATAN2'(Y,X). ! * Support of the `PARITY' intrinsic functions. ! * The following bit intrinsics: `LEADZ' and `TRAILZ' for counting ! the number of leading and trailing zero bits, `POPCNT' and ! `POPPAR' for counting the number of one bits and returning the ! parity; `BGE', `BGT', `BLE', and `BLT' for bitwise comparisons; ! `DSHIFTL' and `DSHIFTR' for combined left and right shifts, ! `MASKL' and `MASKR' for simple left and right justified masks, ! `MERGE_BITS' for a bitwise merge using a mask, `SHIFTA', `SHIFTL' ! and `SHIFTR' for shift operations, and the transformational bit ! intrinsics `IALL', `IANY' and `IPARITY'. ! * Support of the `EXECUTE_COMMAND_LINE' intrinsic subroutine. ! * Support for the `STORAGE_SIZE' intrinsic inquiry function. ! * The `INT{8,16,32}' and `REAL{32,64,128}' kind type parameters and ! the array-valued named constants `INTEGER_KINDS', `LOGICAL_KINDS', ! `REAL_KINDS' and `CHARACTER_KINDS' of the intrinsic module ! `ISO_FORTRAN_ENV'. ! * The module procedures `C_SIZEOF' of the intrinsic module ! `ISO_C_BINDINGS' and `COMPILER_VERSION' and `COMPILER_OPTIONS' of ! `ISO_FORTRAN_ENV'. ! * Coarray support for serial programs with `-fcoarray=single' flag and experimental support for multiple images with the ! `-fcoarray=lib' flag. ! * Submodules are supported. It should noted that `MODULEs' do not ! produce the smod file needed by the descendent `SUBMODULEs' unless ! they contain at least one `MODULE PROCEDURE' interface. The reason ! for this is that `SUBMODULEs' are useless without `MODULE ! PROCEDUREs'. See http://j3-fortran.org/doc/meeting/207/15-209.txt ! for a discussion and a draft interpretation. Adopting this interpretation has the advantage that code that does not use submodules does not generate smod files. ! * The `DO CONCURRENT' construct is supported. ! * The `BLOCK' construct is supported. ! * The `STOP' and the new `ERROR STOP' statements now support all ! constant expressions. Both show the signals which were signaling at termination. ! * Support for the `CONTIGUOUS' attribute. ! * Support for `ALLOCATE' with `MOLD'. ! * Support for the `IMPURE' attribute for procedures, which allows ! for `ELEMENTAL' procedures without the restrictions of `PURE'. ! * Null pointers (including `NULL()') and not-allocated variables can be used as actual argument to optional non-pointer, non-allocatable dummy arguments, denoting an absent argument. ! * Non-pointer variables with `TARGET' attribute can be used as ! actual argument to `POINTER' dummies with `INTENT(IN)'. * Pointers including procedure pointers and those in a derived type (pointer components) can now be initialized by a target instead of ! only by `NULL'. ! * The `EXIT' statement (with construct-name) can be now be used to ! leave not only the `DO' but also the `ASSOCIATE', `BLOCK', `IF', ! `SELECT CASE' and `SELECT TYPE' constructs. * Internal procedures can now be used as actual argument. ! * Minor features: obsolesce diagnostics for `ENTRY' with ! `-std=f2008'; a line may start with a semicolon; for internal and ! module procedures `END' can be used instead of `END SUBROUTINE' ! and `END FUNCTION'; `SELECTED_REAL_KIND' now also takes a `RADIX' argument; intrinsic types are supported for ! `TYPE'(INTRINSIC-TYPE-SPEC); multiple type-bound procedures can be ! declared in a single `PROCEDURE' statement; implied-shape arrays ! are supported for named constants (`PARAMETER').  File: gfortran.info, Node: TS 29113 status, Next: TS 18508 status, Prev: Fortran 2008 status, Up: Fortran 2003 and 2008 status *************** following is implemented. *** 2212,2230 **** See also *note Further Interoperability of Fortran with C::. ! * The '-std=f2008ts' option. ! * The 'OPTIONAL' attribute is allowed for dummy arguments of 'BIND(C) ! procedures.' ! * The 'RANK' intrinsic is supported. ! * GNU Fortran's implementation for variables with 'ASYNCHRONOUS' attribute is compatible with TS 29113. ! * Assumed types ('TYPE(*)'. ! * Assumed-rank ('DIMENSION(..)'). However, the array descriptor of the TS is not yet supported.  --- 2228,2246 ---- See also *note Further Interoperability of Fortran with C::. ! * The `-std=f2008ts' option. ! * The `OPTIONAL' attribute is allowed for dummy arguments of ! `BIND(C) procedures.' ! * The `RANK' intrinsic is supported. ! * GNU Fortran's implementation for variables with `ASYNCHRONOUS' attribute is compatible with TS 29113. ! * Assumed types (`TYPE(*)'. ! * Assumed-rank (`DIMENSION(..)'). However, the array descriptor of the TS is not yet supported.  *************** Specification 18508 on Additional Parall *** 2239,2250 **** * The new atomic ADD, CAS, FETCH and ADD/OR/XOR, OR and XOR intrinsics. ! * The 'CO_MIN' and 'CO_MAX' and 'SUM' reduction intrinsics. And the ! 'CO_BROADCAST' and 'CO_REDUCE' intrinsic, except that those do not support polymorphic types or types with allocatable, pointer or polymorphic components. ! * Events ('EVENT POST', 'EVENT WAIT', 'EVENT_QUERY')  File: gfortran.info, Node: Compiler Characteristics, Next: Extensions, Prev: Fortran 2003 and 2008 status, Up: Top --- 2255,2266 ---- * The new atomic ADD, CAS, FETCH and ADD/OR/XOR, OR and XOR intrinsics. ! * The `CO_MIN' and `CO_MAX' and `SUM' reduction intrinsics. And the ! `CO_BROADCAST' and `CO_REDUCE' intrinsic, except that those do not support polymorphic types or types with allocatable, pointer or polymorphic components. ! * Events (`EVENT POST', `EVENT WAIT', `EVENT_QUERY')  File: gfortran.info, Node: Compiler Characteristics, Next: Extensions, Prev: Fortran 2003 and 2008 status, Up: Top *************** File: gfortran.info, Node: KIND Type Pa *** 2271,2311 **** 5.1 KIND Type Parameters ======================== ! The 'KIND' type parameters supported by GNU Fortran for the primitive data types are: ! 'INTEGER' 1, 2, 4, 8*, 16*, default: 4** ! 'LOGICAL' 1, 2, 4, 8*, 16*, default: 4** ! 'REAL' 4, 8, 10*, 16*, default: 4*** ! 'COMPLEX' 4, 8, 10*, 16*, default: 4*** ! 'DOUBLE PRECISION' 4, 8, 10*, 16*, default: 8*** ! 'CHARACTER' 1, 4, default: 1 * not available on all systems ! ** unless '-fdefault-integer-8' is used ! *** unless '-fdefault-real-8' is used (see *note Fortran Dialect Options::) ! The 'KIND' value matches the storage size in bytes, except for 'COMPLEX' ! where the storage size is twice as much (or both real and imaginary part ! are a real value of the given size). It is recommended to use the *note ! SELECTED_CHAR_KIND::, *note SELECTED_INT_KIND:: and *note ! SELECTED_REAL_KIND:: intrinsics or the 'INT8', 'INT16', 'INT32', ! 'INT64', 'REAL32', 'REAL64', and 'REAL128' parameters of the ! 'ISO_FORTRAN_ENV' module instead of the concrete values. The available ! kind parameters can be found in the constant arrays 'CHARACTER_KINDS', ! 'INTEGER_KINDS', 'LOGICAL_KINDS' and 'REAL_KINDS' in the *note ISO_FORTRAN_ENV:: module. For C interoperability, the kind parameters of the *note ISO_C_BINDING:: module should be used. --- 2287,2328 ---- 5.1 KIND Type Parameters ======================== ! The `KIND' type parameters supported by GNU Fortran for the primitive data types are: ! `INTEGER' 1, 2, 4, 8*, 16*, default: 4** ! `LOGICAL' 1, 2, 4, 8*, 16*, default: 4** ! `REAL' 4, 8, 10*, 16*, default: 4*** ! `COMPLEX' 4, 8, 10*, 16*, default: 4*** ! `DOUBLE PRECISION' 4, 8, 10*, 16*, default: 8*** ! `CHARACTER' 1, 4, default: 1 + * not available on all systems ! ** unless `-fdefault-integer-8' is used ! *** unless `-fdefault-real-8' is used (see *note Fortran Dialect Options::) ! The `KIND' value matches the storage size in bytes, except for ! `COMPLEX' where the storage size is twice as much (or both real and ! imaginary part are a real value of the given size). It is recommended ! to use the *note SELECTED_CHAR_KIND::, *note SELECTED_INT_KIND:: and ! *note SELECTED_REAL_KIND:: intrinsics or the `INT8', `INT16', `INT32', ! `INT64', `REAL32', `REAL64', and `REAL128' parameters of the ! `ISO_FORTRAN_ENV' module instead of the concrete values. The available ! kind parameters can be found in the constant arrays `CHARACTER_KINDS', ! `INTEGER_KINDS', `LOGICAL_KINDS' and `REAL_KINDS' in the *note ISO_FORTRAN_ENV:: module. For C interoperability, the kind parameters of the *note ISO_C_BINDING:: module should be used. *************** File: gfortran.info, Node: Internal rep *** 2315,2328 **** 5.2 Internal representation of LOGICAL variables ================================================ ! The Fortran standard does not specify how variables of 'LOGICAL' type ! are represented, beyond requiring that 'LOGICAL' variables of default ! kind have the same storage size as default 'INTEGER' and 'REAL' variables. The GNU Fortran internal representation is as follows. ! A 'LOGICAL(KIND=N)' variable is represented as an 'INTEGER(KIND=N)' ! variable, however, with only two permissible values: '1' for '.TRUE.' ! and '0' for '.FALSE.'. Any other integer value results in undefined behavior. See also *note Argument passing conventions:: and *note --- 2332,2345 ---- 5.2 Internal representation of LOGICAL variables ================================================ ! The Fortran standard does not specify how variables of `LOGICAL' type ! are represented, beyond requiring that `LOGICAL' variables of default ! kind have the same storage size as default `INTEGER' and `REAL' variables. The GNU Fortran internal representation is as follows. ! A `LOGICAL(KIND=N)' variable is represented as an `INTEGER(KIND=N)' ! variable, however, with only two permissible values: `1' for `.TRUE.' ! and `0' for `.FALSE.'. Any other integer value results in undefined behavior. See also *note Argument passing conventions:: and *note *************** File: gfortran.info, Node: Thread-safet *** 2334,2377 **** 5.3 Thread-safety of the runtime library ======================================== ! GNU Fortran can be used in programs with multiple threads, e.g. by using ! OpenMP, by calling OS thread handling functions via the 'ISO_C_BINDING' ! facility, or by GNU Fortran compiled library code being called from a ! multi-threaded program. ! The GNU Fortran runtime library, ('libgfortran'), supports being called concurrently from multiple threads with the following exceptions. ! During library initialization, the C 'getenv' function is used, which ! need not be thread-safe. Similarly, the 'getenv' function is used to ! implement the 'GET_ENVIRONMENT_VARIABLE' and 'GETENV' intrinsics. It is ! the responsibility of the user to ensure that the environment is not ! being updated concurrently when any of these actions are taking place. ! The 'EXECUTE_COMMAND_LINE' and 'SYSTEM' intrinsics are implemented ! with the 'system' function, which need not be thread-safe. It is the ! responsibility of the user to ensure that 'system' is not called concurrently. For platforms not supporting thread-safe POSIX functions, further ! functionality might not be thread-safe. For details, please consult the ! documentation for your operating system. The GNU Fortran runtime library uses various C library functions that ! depend on the locale, such as 'strtod' and 'snprintf'. In order to work ! correctly in locale-aware programs that set the locale using ! 'setlocale', the locale is reset to the default "C" locale while ! executing a formatted 'READ' or 'WRITE' statement. On targets supporting the POSIX 2008 per-thread locale functions (e.g. ! 'newlocale', 'uselocale', 'freelocale'), these are used and thus the ! global locale set using 'setlocale' or the per-thread locales in other threads are not affected. However, on targets lacking this functionality, the global LC_NUMERIC locale is set to "C" during the ! formatted I/O. Thus, on such targets it's not safe to call 'setlocale' ! concurrently from another thread while a Fortran formatted I/O operation ! is in progress. Also, other threads doing something dependent on the ! LC_NUMERIC locale might not work correctly if a formatted I/O operation ! is in progress in another thread.  File: gfortran.info, Node: Data consistency and durability, Next: Files opened without an explicit ACTION= specifier, Prev: Thread-safety of the runtime library, Up: Compiler Characteristics --- 2351,2395 ---- 5.3 Thread-safety of the runtime library ======================================== ! GNU Fortran can be used in programs with multiple threads, e.g. by ! using OpenMP, by calling OS thread handling functions via the ! `ISO_C_BINDING' facility, or by GNU Fortran compiled library code being ! called from a multi-threaded program. ! The GNU Fortran runtime library, (`libgfortran'), supports being called concurrently from multiple threads with the following exceptions. ! During library initialization, the C `getenv' function is used, ! which need not be thread-safe. Similarly, the `getenv' function is ! used to implement the `GET_ENVIRONMENT_VARIABLE' and `GETENV' ! intrinsics. It is the responsibility of the user to ensure that the ! environment is not being updated concurrently when any of these actions ! are taking place. ! The `EXECUTE_COMMAND_LINE' and `SYSTEM' intrinsics are implemented ! with the `system' function, which need not be thread-safe. It is the ! responsibility of the user to ensure that `system' is not called concurrently. For platforms not supporting thread-safe POSIX functions, further ! functionality might not be thread-safe. For details, please consult ! the documentation for your operating system. The GNU Fortran runtime library uses various C library functions that ! depend on the locale, such as `strtod' and `snprintf'. In order to ! work correctly in locale-aware programs that set the locale using ! `setlocale', the locale is reset to the default "C" locale while ! executing a formatted `READ' or `WRITE' statement. On targets supporting the POSIX 2008 per-thread locale functions (e.g. ! `newlocale', `uselocale', `freelocale'), these are used and thus the ! global locale set using `setlocale' or the per-thread locales in other threads are not affected. However, on targets lacking this functionality, the global LC_NUMERIC locale is set to "C" during the ! formatted I/O. Thus, on such targets it's not safe to call `setlocale' ! concurrently from another thread while a Fortran formatted I/O ! operation is in progress. Also, other threads doing something ! dependent on the LC_NUMERIC locale might not work correctly if a ! formatted I/O operation is in progress in another thread.  File: gfortran.info, Node: Data consistency and durability, Next: Files opened without an explicit ACTION= specifier, Prev: Thread-safety of the runtime library, Up: Compiler Characteristics *************** This section contains a brief overview o *** 2383,2394 **** and durability issues when doing I/O. With respect to durability, GNU Fortran makes no effort to ensure ! that data is committed to stable storage. If this is required, the GNU ! Fortran programmer can use the intrinsic 'FNUM' to retrieve the low ! level file descriptor corresponding to an open Fortran unit. Then, ! using e.g. the 'ISO_C_BINDING' feature, one can call the underlying ! system call to flush dirty data to stable storage, such as 'fsync' on ! POSIX, '_commit' on MingW, or 'fcntl(fd, F_FULLSYNC, 0)' on Mac OS X. The following example shows how to call fsync: ! Declare the interface for POSIX fsync function --- 2401,2412 ---- and durability issues when doing I/O. With respect to durability, GNU Fortran makes no effort to ensure ! that data is committed to stable storage. If this is required, the GNU ! Fortran programmer can use the intrinsic `FNUM' to retrieve the low ! level file descriptor corresponding to an open Fortran unit. Then, ! using e.g. the `ISO_C_BINDING' feature, one can call the underlying ! system call to flush dirty data to stable storage, such as `fsync' on ! POSIX, `_commit' on MingW, or `fcntl(fd, F_FULLSYNC, 0)' on Mac OS X. The following example shows how to call fsync: ! Declare the interface for POSIX fsync function *************** The following example shows how to call *** 2418,2446 **** if (ret /= 0) stop "Error calling FSYNC" With respect to consistency, for regular files GNU Fortran uses ! buffered I/O in order to improve performance. This buffer is flushed ! automatically when full and in some other situations, e.g. when closing ! a unit. It can also be explicitly flushed with the 'FLUSH' statement. ! Also, the buffering can be turned off with the 'GFORTRAN_UNBUFFERED_ALL' ! and 'GFORTRAN_UNBUFFERED_PRECONNECTED' environment variables. Special ! files, such as terminals and pipes, are always unbuffered. Sometimes, ! however, further things may need to be done in order to allow other ! processes to see data that GNU Fortran has written, as follows. The Windows platform supports a relaxed metadata consistency model, ! where file metadata is written to the directory lazily. This means ! that, for instance, the 'dir' command can show a stale size for a file. One can force a directory metadata update by closing the unit, or by ! calling '_commit' on the file descriptor. Note, though, that '_commit' will force all dirty data to stable storage, which is often a very slow operation. The Network File System (NFS) implements a relaxed consistency model ! called open-to-close consistency. Closing a file forces dirty data and metadata to be flushed to the server, and opening a file forces the client to contact the server in order to revalidate cached data. ! 'fsync' will also force a flush of dirty data and metadata to the ! server. Similar to 'open' and 'close', acquiring and releasing 'fcntl' file locks, if the server supports them, will also force cache validation and flushing dirty data and metadata. --- 2436,2465 ---- if (ret /= 0) stop "Error calling FSYNC" With respect to consistency, for regular files GNU Fortran uses ! buffered I/O in order to improve performance. This buffer is flushed ! automatically when full and in some other situations, e.g. when closing ! a unit. It can also be explicitly flushed with the `FLUSH' statement. ! Also, the buffering can be turned off with the ! `GFORTRAN_UNBUFFERED_ALL' and `GFORTRAN_UNBUFFERED_PRECONNECTED' ! environment variables. Special files, such as terminals and pipes, are ! always unbuffered. Sometimes, however, further things may need to be ! done in order to allow other processes to see data that GNU Fortran has ! written, as follows. The Windows platform supports a relaxed metadata consistency model, ! where file metadata is written to the directory lazily. This means ! that, for instance, the `dir' command can show a stale size for a file. One can force a directory metadata update by closing the unit, or by ! calling `_commit' on the file descriptor. Note, though, that `_commit' will force all dirty data to stable storage, which is often a very slow operation. The Network File System (NFS) implements a relaxed consistency model ! called open-to-close consistency. Closing a file forces dirty data and metadata to be flushed to the server, and opening a file forces the client to contact the server in order to revalidate cached data. ! `fsync' will also force a flush of dirty data and metadata to the ! server. Similar to `open' and `close', acquiring and releasing `fcntl' file locks, if the server supports them, will also force cache validation and flushing dirty data and metadata. *************** File: gfortran.info, Node: Files opened *** 2450,2462 **** 5.5 Files opened without an explicit ACTION= specifier ====================================================== ! The Fortran standard says that if an 'OPEN' statement is executed ! without an explicit 'ACTION=' specifier, the default value is processor dependent. GNU Fortran behaves as follows: ! 1. Attempt to open the file with 'ACTION='READWRITE'' ! 2. If that fails, try to open with 'ACTION='READ'' ! 3. If that fails, try to open with 'ACTION='WRITE'' 4. If that fails, generate an error  --- 2469,2484 ---- 5.5 Files opened without an explicit ACTION= specifier ====================================================== ! The Fortran standard says that if an `OPEN' statement is executed ! without an explicit `ACTION=' specifier, the default value is processor dependent. GNU Fortran behaves as follows: ! 1. Attempt to open the file with `ACTION='READWRITE'' ! ! 2. If that fails, try to open with `ACTION='READ'' ! ! 3. If that fails, try to open with `ACTION='WRITE'' ! 4. If that fails, generate an error  *************** This section documents the behavior of G *** 2469,2487 **** on symbolic links, on systems that support them. * Results of INQUIRE statements of the "inquire by file" form will ! relate to the target of the symbolic link. For example, ! 'INQUIRE(FILE="foo",EXIST=ex)' will set EX to .TRUE. if FOO is a ! symbolic link pointing to an existing file, and .FALSE. if FOO points to an non-existing file ("dangling" symbolic link). ! * Using the 'OPEN' statement with a 'STATUS="NEW"' specifier on a symbolic link will result in an error condition, whether the symbolic link points to an existing target or is dangling. ! * If a symbolic link was connected, using the 'CLOSE' statement with ! a 'STATUS="DELETE"' specifier will cause the symbolic link itself to be deleted, not its target.  File: gfortran.info, Node: Extensions, Next: Mixed-Language Programming, Prev: Compiler Characteristics, Up: Top --- 2491,2510 ---- on symbolic links, on systems that support them. * Results of INQUIRE statements of the "inquire by file" form will ! relate to the target of the symbolic link. For example, ! `INQUIRE(FILE="foo",EXIST=ex)' will set EX to .TRUE. if FOO is a ! symbolic link pointing to an existing file, and .FALSE. if FOO points to an non-existing file ("dangling" symbolic link). ! * Using the `OPEN' statement with a `STATUS="NEW"' specifier on a symbolic link will result in an error condition, whether the symbolic link points to an existing target or is dangling. ! * If a symbolic link was connected, using the `CLOSE' statement with ! a `STATUS="DELETE"' specifier will cause the symbolic link itself to be deleted, not its target. +  File: gfortran.info, Node: Extensions, Next: Mixed-Language Programming, Prev: Compiler Characteristics, Up: Top *************** GNU Fortran implements a number of exten *** 2510,2520 **** This chapter contains information on their syntax and meaning. There are currently two categories of GNU Fortran extensions, those that provide functionality beyond that provided by any standard, and those ! that are supported by GNU Fortran purely for backward compatibility with ! legacy compilers. By default, '-std=gnu' allows the compiler to accept ! both types of extensions, but to warn about the use of the latter. ! Specifying either '-std=f95', '-std=f2003' or '-std=f2008' disables both ! types of extensions, and '-std=legacy' allows both without warning. * Menu: --- 2533,2544 ---- This chapter contains information on their syntax and meaning. There are currently two categories of GNU Fortran extensions, those that provide functionality beyond that provided by any standard, and those ! that are supported by GNU Fortran purely for backward compatibility ! with legacy compilers. By default, `-std=gnu' allows the compiler to ! accept both types of extensions, but to warn about the use of the ! latter. Specifying either `-std=f95', `-std=f2003' or `-std=f2008' ! disables both types of extensions, and `-std=legacy' allows both ! without warning. * Menu: *************** types of extensions, and '-std=legacy' a *** 2525,2531 **** * Commas in FORMAT specifications:: * Missing period in FORMAT specifications:: * I/O item lists:: ! * Q exponent-letter:: * BOZ literal constants:: * Real array indices:: * Unary operators:: --- 2549,2555 ---- * Commas in FORMAT specifications:: * Missing period in FORMAT specifications:: * I/O item lists:: ! * `Q' exponent-letter:: * BOZ literal constants:: * Real array indices:: * Unary operators:: *************** File: gfortran.info, Node: Old-style ki *** 2549,2565 **** GNU Fortran allows old-style kind specifications in declarations. These look like: TYPESPEC*size x,y,z ! where 'TYPESPEC' is a basic type ('INTEGER', 'REAL', etc.), and where ! 'size' is a byte count corresponding to the storage size of a valid kind ! for that type. (For 'COMPLEX' variables, 'size' is the total size of ! the real and imaginary parts.) The statement then declares 'x', 'y' and ! 'z' to be of type 'TYPESPEC' with the appropriate kind. This is ! equivalent to the standard-conforming declaration TYPESPEC(k) x,y,z ! where 'k' is the kind parameter suitable for the intended precision. As ! kind parameters are implementation-dependent, use the 'KIND', ! 'SELECTED_INT_KIND' and 'SELECTED_REAL_KIND' intrinsics to retrieve the ! correct value, for instance 'REAL*8 x' can be replaced by: INTEGER, PARAMETER :: dbl = KIND(1.0d0) REAL(KIND=dbl) :: x --- 2573,2589 ---- GNU Fortran allows old-style kind specifications in declarations. These look like: TYPESPEC*size x,y,z ! where `TYPESPEC' is a basic type (`INTEGER', `REAL', etc.), and ! where `size' is a byte count corresponding to the storage size of a ! valid kind for that type. (For `COMPLEX' variables, `size' is the ! total size of the real and imaginary parts.) The statement then ! declares `x', `y' and `z' to be of type `TYPESPEC' with the appropriate ! kind. This is equivalent to the standard-conforming declaration TYPESPEC(k) x,y,z ! where `k' is the kind parameter suitable for the intended precision. ! As kind parameters are implementation-dependent, use the `KIND', ! `SELECTED_INT_KIND' and `SELECTED_REAL_KIND' intrinsics to retrieve the ! correct value, for instance `REAL*8 x' can be replaced by: INTEGER, PARAMETER :: dbl = KIND(1.0d0) REAL(KIND=dbl) :: x *************** File: gfortran.info, Node: Old-style va *** 2572,2583 **** GNU Fortran allows old-style initialization of variables of the form: INTEGER i/1/,j/2/ REAL x(2,2) /3*0.,1./ ! The syntax for the initializers is as for the 'DATA' statement, but ! unlike in a 'DATA' statement, an initializer only applies to the variable immediately preceding the initialization. In other words, ! something like 'INTEGER I,J/2,3/' is not valid. This style of initialization is only allowed in declarations without double colons ! ('::'); the double colons were introduced in Fortran 90, which also introduced a standard syntax for initializing variables in type declarations. --- 2596,2607 ---- GNU Fortran allows old-style initialization of variables of the form: INTEGER i/1/,j/2/ REAL x(2,2) /3*0.,1./ ! The syntax for the initializers is as for the `DATA' statement, but ! unlike in a `DATA' statement, an initializer only applies to the variable immediately preceding the initialization. In other words, ! something like `INTEGER I,J/2,3/' is not valid. This style of initialization is only allowed in declarations without double colons ! (`::'); the double colons were introduced in Fortran 90, which also introduced a standard syntax for initializing variables in type declarations. *************** are: *** 2592,2598 **** DATA i/1/, j/2/, x/3*0.,1./ Note that variables which are explicitly initialized in declarations ! or in 'DATA' statements automatically acquire the 'SAVE' attribute.  File: gfortran.info, Node: Extensions to namelist, Next: X format descriptor without count field, Prev: Old-style variable initialization, Up: Extensions implemented in GNU Fortran --- 2616,2622 ---- DATA i/1/, j/2/, x/3*0.,1./ Note that variables which are explicitly initialized in declarations ! or in `DATA' statements automatically acquire the `SAVE' attribute.  File: gfortran.info, Node: Extensions to namelist, Next: X format descriptor without count field, Prev: Old-style variable initialization, Up: Extensions implemented in GNU Fortran *************** types. The output from a namelist write *** 2606,2622 **** read. The output has all names in upper case and indentation to column 1 after the namelist name. Two extensions are permitted: ! Old-style use of '$' instead of '&' $MYNML X(:)%Y(2) = 1.0 2.0 3.0 CH(1:4) = "abcd" $END ! It should be noted that the default terminator is '/' rather than ! '&END'. Querying of the namelist when inputting from stdin. After at least ! one space, entering '?' sends to stdout the namelist name and the names of the variables in the namelist: ? --- 2630,2646 ---- read. The output has all names in upper case and indentation to column 1 after the namelist name. Two extensions are permitted: ! Old-style use of `$' instead of `&' $MYNML X(:)%Y(2) = 1.0 2.0 3.0 CH(1:4) = "abcd" $END ! It should be noted that the default terminator is `/' rather than ! `&END'. Querying of the namelist when inputting from stdin. After at least ! one space, entering `?' sends to stdout the namelist name and the names of the variables in the namelist: ? *************** of the variables in the namelist: *** 2626,2632 **** ch &end ! Entering '=?' outputs the namelist to stdout, as if 'WRITE(*,NML = mynml)' had been called: =? --- 2650,2656 ---- ch &end ! Entering `=?' outputs the namelist to stdout, as if `WRITE(*,NML = mynml)' had been called: =? *************** mynml)' had been called: *** 2637,2646 **** CH=abcd, / To aid this dialog, when input is from stdin, errors send their ! messages to stderr and execution continues, even if 'IOSTAT' is set. ! 'PRINT' namelist is permitted. This causes an error if '-std=f95' is ! used. PROGRAM test_print REAL, dimension (4) :: x = (/1.0, 2.0, 3.0, 4.0/) NAMELIST /mynml/ x --- 2661,2670 ---- CH=abcd, / To aid this dialog, when input is from stdin, errors send their ! messages to stderr and execution continues, even if `IOSTAT' is set. ! `PRINT' namelist is permitted. This causes an error if `-std=f95' ! is used. PROGRAM test_print REAL, dimension (4) :: x = (/1.0, 2.0, 3.0, 4.0/) NAMELIST /mynml/ x *************** used. *** 2648,2662 **** END PROGRAM test_print Expanded namelist reads are permitted. This causes an error if ! '-std=f95' is used. In the following example, the first element of the array will be given the value 0.00 and the two succeeding elements will be given the values 1.00 and 2.00. &MYNML X(1,1) = 0.00 , 1.00 , 2.00 / ! When writing a namelist, if no 'DELIM=' is specified, by default a ! double quote is used to delimit character strings. If -std=F95, F2003, or F2008, etc, the delim status is set to 'none'. Defaulting to quotes ensures that namelists with character strings can be subsequently read back in accurately. --- 2672,2686 ---- END PROGRAM test_print Expanded namelist reads are permitted. This causes an error if ! `-std=f95' is used. In the following example, the first element of the array will be given the value 0.00 and the two succeeding elements will be given the values 1.00 and 2.00. &MYNML X(1,1) = 0.00 , 1.00 , 2.00 / ! When writing a namelist, if no `DELIM=' is specified, by default a ! double quote is used to delimit character strings. If -std=F95, F2003, or F2008, etc, the delim status is set to 'none'. Defaulting to quotes ensures that namelists with character strings can be subsequently read back in accurately. *************** back in accurately. *** 2664,2675 ****  File: gfortran.info, Node: X format descriptor without count field, Next: Commas in FORMAT specifications, Prev: Extensions to namelist, Up: Extensions implemented in GNU Fortran ! 6.1.4 'X' format descriptor without count field ----------------------------------------------- ! To support legacy codes, GNU Fortran permits the count field of the 'X' ! edit descriptor in 'FORMAT' statements to be omitted. When omitted, the ! count is implicitly assumed to be one. PRINT 10, 2, 3 10 FORMAT (I1, X, I1) --- 2688,2699 ----  File: gfortran.info, Node: X format descriptor without count field, Next: Commas in FORMAT specifications, Prev: Extensions to namelist, Up: Extensions implemented in GNU Fortran ! 6.1.4 `X' format descriptor without count field ----------------------------------------------- ! To support legacy codes, GNU Fortran permits the count field of the `X' ! edit descriptor in `FORMAT' statements to be omitted. When omitted, ! the count is implicitly assumed to be one. PRINT 10, 2, 3 10 FORMAT (I1, X, I1) *************** count is implicitly assumed to be one. *** 2677,2688 ****  File: gfortran.info, Node: Commas in FORMAT specifications, Next: Missing period in FORMAT specifications, Prev: X format descriptor without count field, Up: Extensions implemented in GNU Fortran ! 6.1.5 Commas in 'FORMAT' specifications --------------------------------------- To support legacy codes, GNU Fortran allows the comma separator to be omitted immediately before and after character string edit descriptors ! in 'FORMAT' statements. PRINT 10, 2, 3 10 FORMAT ('FOO='I1' BAR='I2) --- 2701,2712 ----  File: gfortran.info, Node: Commas in FORMAT specifications, Next: Missing period in FORMAT specifications, Prev: X format descriptor without count field, Up: Extensions implemented in GNU Fortran ! 6.1.5 Commas in `FORMAT' specifications --------------------------------------- To support legacy codes, GNU Fortran allows the comma separator to be omitted immediately before and after character string edit descriptors ! in `FORMAT' statements. PRINT 10, 2, 3 10 FORMAT ('FOO='I1' BAR='I2) *************** in 'FORMAT' statements. *** 2690,2700 ****  File: gfortran.info, Node: Missing period in FORMAT specifications, Next: I/O item lists, Prev: Commas in FORMAT specifications, Up: Extensions implemented in GNU Fortran ! 6.1.6 Missing period in 'FORMAT' specifications ----------------------------------------------- To support legacy codes, GNU Fortran allows missing periods in format ! specifications if and only if '-std=legacy' is given on the command line. This is considered non-conforming code and is discouraged. REAL :: value --- 2714,2724 ----  File: gfortran.info, Node: Missing period in FORMAT specifications, Next: I/O item lists, Prev: Commas in FORMAT specifications, Up: Extensions implemented in GNU Fortran ! 6.1.6 Missing period in `FORMAT' specifications ----------------------------------------------- To support legacy codes, GNU Fortran allows missing periods in format ! specifications if and only if `-std=legacy' is given on the command line. This is considered non-conforming code and is discouraged. REAL :: value *************** line. This is considered non-conforming *** 2702,2774 **** 10 FORMAT ('F4')  ! File: gfortran.info, Node: I/O item lists, Next: Q exponent-letter, Prev: Missing period in FORMAT specifications, Up: Extensions implemented in GNU Fortran 6.1.7 I/O item lists -------------------- To support legacy codes, GNU Fortran allows the input item list of the ! 'READ' statement, and the output item lists of the 'WRITE' and 'PRINT' statements, to start with a comma.  ! File: gfortran.info, Node: Q exponent-letter, Next: BOZ literal constants, Prev: I/O item lists, Up: Extensions implemented in GNU Fortran ! 6.1.8 'Q' exponent-letter ------------------------- GNU Fortran accepts real literal constants with an exponent-letter of ! 'Q', for example, '1.23Q45'. The constant is interpreted as a ! 'REAL(16)' entity on targets that support this type. If the target does ! not support 'REAL(16)' but has a 'REAL(10)' type, then the ! real-literal-constant will be interpreted as a 'REAL(10)' entity. In ! the absence of 'REAL(16)' and 'REAL(10)', an error will occur.  ! File: gfortran.info, Node: BOZ literal constants, Next: Real array indices, Prev: Q exponent-letter, Up: Extensions implemented in GNU Fortran 6.1.9 BOZ literal constants --------------------------- ! Besides decimal constants, Fortran also supports binary ('b'), octal ! ('o') and hexadecimal ('z') integer constants. The syntax is: 'prefix ! quote digits quote', were the prefix is either 'b', 'o' or 'z', quote is ! either ''' or '"' and the digits are for binary '0' or '1', for octal ! between '0' and '7', and for hexadecimal between '0' and 'F'. (Example: ! 'b'01011101''.) Up to Fortran 95, BOZ literals were only allowed to initialize integer variables in DATA statements. Since Fortran 2003 BOZ literals ! are also allowed as argument of 'REAL', 'DBLE', 'INT' and 'CMPLX'; the result is the same as if the integer BOZ literal had been converted by ! 'TRANSFER' to, respectively, 'real', 'double precision', 'integer' or ! 'complex'. As GNU Fortran extension the intrinsic procedures 'FLOAT', ! 'DFLOAT', 'COMPLEX' and 'DCMPLX' are treated alike. ! As an extension, GNU Fortran allows hexadecimal BOZ literal constants ! to be specified using the 'X' prefix, in addition to the standard 'Z' ! prefix. The BOZ literal can also be specified by adding a suffix to the ! string, for example, 'Z'ABC'' and ''ABC'Z' are equivalent. Furthermore, GNU Fortran allows using BOZ literal constants outside DATA statements and the four intrinsic functions allowed by Fortran 2003. In DATA statements, in direct assignments, where the right-hand side only contains a BOZ literal constant, and for old-style ! initializers of the form 'integer i /o'0173'/', the constant is ! transferred as if 'TRANSFER' had been used; for 'COMPLEX' numbers, only ! the real part is initialized unless 'CMPLX' is used. In all other ! cases, the BOZ literal constant is converted to an 'INTEGER' value with the largest decimal representation. This value is then converted numerically to the type and kind of the variable in question. (For ! instance, 'real :: r = b'0000001' + 1' initializes 'r' with '2.0'.) As different compilers implement the extension differently, one should be careful when doing bitwise initialization of non-integer variables. ! Note that initializing an 'INTEGER' variable with a statement such as ! 'DATA i/Z'FFFFFFFF'/' will give an integer overflow error rather than ! the desired result of -1 when 'i' is a 32-bit integer on a system that ! supports 64-bit integers. The '-fno-range-check' option can be used as ! a workaround for legacy code that initializes integers in this manner.  File: gfortran.info, Node: Real array indices, Next: Unary operators, Prev: BOZ literal constants, Up: Extensions implemented in GNU Fortran --- 2726,2799 ---- 10 FORMAT ('F4')  ! File: gfortran.info, Node: I/O item lists, Next: `Q' exponent-letter, Prev: Missing period in FORMAT specifications, Up: Extensions implemented in GNU Fortran 6.1.7 I/O item lists -------------------- To support legacy codes, GNU Fortran allows the input item list of the ! `READ' statement, and the output item lists of the `WRITE' and `PRINT' statements, to start with a comma.  ! File: gfortran.info, Node: `Q' exponent-letter, Next: BOZ literal constants, Prev: I/O item lists, Up: Extensions implemented in GNU Fortran ! 6.1.8 `Q' exponent-letter ------------------------- GNU Fortran accepts real literal constants with an exponent-letter of ! `Q', for example, `1.23Q45'. The constant is interpreted as a ! `REAL(16)' entity on targets that support this type. If the target ! does not support `REAL(16)' but has a `REAL(10)' type, then the ! real-literal-constant will be interpreted as a `REAL(10)' entity. In ! the absence of `REAL(16)' and `REAL(10)', an error will occur.  ! File: gfortran.info, Node: BOZ literal constants, Next: Real array indices, Prev: `Q' exponent-letter, Up: Extensions implemented in GNU Fortran 6.1.9 BOZ literal constants --------------------------- ! Besides decimal constants, Fortran also supports binary (`b'), octal ! (`o') and hexadecimal (`z') integer constants. The syntax is: `prefix ! quote digits quote', were the prefix is either `b', `o' or `z', quote ! is either `'' or `"' and the digits are for binary `0' or `1', for ! octal between `0' and `7', and for hexadecimal between `0' and `F'. ! (Example: `b'01011101''.) Up to Fortran 95, BOZ literals were only allowed to initialize integer variables in DATA statements. Since Fortran 2003 BOZ literals ! are also allowed as argument of `REAL', `DBLE', `INT' and `CMPLX'; the result is the same as if the integer BOZ literal had been converted by ! `TRANSFER' to, respectively, `real', `double precision', `integer' or ! `complex'. As GNU Fortran extension the intrinsic procedures `FLOAT', ! `DFLOAT', `COMPLEX' and `DCMPLX' are treated alike. ! As an extension, GNU Fortran allows hexadecimal BOZ literal ! constants to be specified using the `X' prefix, in addition to the ! standard `Z' prefix. The BOZ literal can also be specified by adding a ! suffix to the string, for example, `Z'ABC'' and `'ABC'Z' are equivalent. Furthermore, GNU Fortran allows using BOZ literal constants outside DATA statements and the four intrinsic functions allowed by Fortran 2003. In DATA statements, in direct assignments, where the right-hand side only contains a BOZ literal constant, and for old-style ! initializers of the form `integer i /o'0173'/', the constant is ! transferred as if `TRANSFER' had been used; for `COMPLEX' numbers, only ! the real part is initialized unless `CMPLX' is used. In all other ! cases, the BOZ literal constant is converted to an `INTEGER' value with the largest decimal representation. This value is then converted numerically to the type and kind of the variable in question. (For ! instance, `real :: r = b'0000001' + 1' initializes `r' with `2.0'.) As different compilers implement the extension differently, one should be careful when doing bitwise initialization of non-integer variables. ! Note that initializing an `INTEGER' variable with a statement such ! as `DATA i/Z'FFFFFFFF'/' will give an integer overflow error rather ! than the desired result of -1 when `i' is a 32-bit integer on a system ! that supports 64-bit integers. The `-fno-range-check' option can be ! used as a workaround for legacy code that initializes integers in this ! manner.  File: gfortran.info, Node: Real array indices, Next: Unary operators, Prev: BOZ literal constants, Up: Extensions implemented in GNU Fortran *************** File: gfortran.info, Node: Real array i *** 2776,2782 **** 6.1.10 Real array indices ------------------------- ! As an extension, GNU Fortran allows the use of 'REAL' expressions or variables as array indices.  --- 2801,2807 ---- 6.1.10 Real array indices ------------------------- ! As an extension, GNU Fortran allows the use of `REAL' expressions or variables as array indices.  *************** the need for parenthesis. *** 2794,2817 ****  File: gfortran.info, Node: Implicitly convert LOGICAL and INTEGER values, Next: Hollerith constants support, Prev: Unary operators, Up: Extensions implemented in GNU Fortran ! 6.1.12 Implicitly convert 'LOGICAL' and 'INTEGER' values -------------------------------------------------------- As an extension for backwards compatibility with other compilers, GNU ! Fortran allows the implicit conversion of 'LOGICAL' values to 'INTEGER' ! values and vice versa. When converting from a 'LOGICAL' to an ! 'INTEGER', '.FALSE.' is interpreted as zero, and '.TRUE.' is interpreted ! as one. When converting from 'INTEGER' to 'LOGICAL', the value zero is ! interpreted as '.FALSE.' and any nonzero value is interpreted as ! '.TRUE.'. LOGICAL :: l l = 1 INTEGER :: i i = .TRUE. ! However, there is no implicit conversion of 'INTEGER' values in ! 'if'-statements, nor of 'LOGICAL' or 'INTEGER' values in I/O operations.  File: gfortran.info, Node: Hollerith constants support, Next: Cray pointers, Prev: Implicitly convert LOGICAL and INTEGER values, Up: Extensions implemented in GNU Fortran --- 2819,2843 ----  File: gfortran.info, Node: Implicitly convert LOGICAL and INTEGER values, Next: Hollerith constants support, Prev: Unary operators, Up: Extensions implemented in GNU Fortran ! 6.1.12 Implicitly convert `LOGICAL' and `INTEGER' values -------------------------------------------------------- As an extension for backwards compatibility with other compilers, GNU ! Fortran allows the implicit conversion of `LOGICAL' values to `INTEGER' ! values and vice versa. When converting from a `LOGICAL' to an ! `INTEGER', `.FALSE.' is interpreted as zero, and `.TRUE.' is ! interpreted as one. When converting from `INTEGER' to `LOGICAL', the ! value zero is interpreted as `.FALSE.' and any nonzero value is ! interpreted as `.TRUE.'. LOGICAL :: l l = 1 + INTEGER :: i i = .TRUE. ! However, there is no implicit conversion of `INTEGER' values in ! `if'-statements, nor of `LOGICAL' or `INTEGER' values in I/O operations.  File: gfortran.info, Node: Hollerith constants support, Next: Cray pointers, Prev: Implicitly convert LOGICAL and INTEGER values, Up: Extensions implemented in GNU Fortran *************** File: gfortran.info, Node: Hollerith co *** 2820,2831 **** ---------------------------------- GNU Fortran supports Hollerith constants in assignments, function ! arguments, and 'DATA' and 'ASSIGN' statements. A Hollerith constant is written as a string of characters preceded by an integer constant ! indicating the character count, and the letter 'H' or 'h', and stored in ! bytewise fashion in a numeric ('INTEGER', 'REAL', or 'complex') or ! 'LOGICAL' variable. The constant will be padded or truncated to fit the ! size of the variable in which it is stored. Examples of valid uses of Hollerith constants: complex*16 x(2) --- 2846,2857 ---- ---------------------------------- GNU Fortran supports Hollerith constants in assignments, function ! arguments, and `DATA' and `ASSIGN' statements. A Hollerith constant is written as a string of characters preceded by an integer constant ! indicating the character count, and the letter `H' or `h', and stored ! in bytewise fashion in a numeric (`INTEGER', `REAL', or `complex') or ! `LOGICAL' variable. The constant will be padded or truncated to fit ! the size of the variable in which it is stored. Examples of valid uses of Hollerith constants: complex*16 x(2) *************** size of the variable in which it is stor *** 2840,2851 **** In general, Hollerith constants were used to provide a rudimentary facility for handling character strings in early Fortran compilers, ! prior to the introduction of 'CHARACTER' variables in Fortran 77; in ! those cases, the standard-compliant equivalent is to convert the program ! to use proper character strings. On occasion, there may be a case where ! the intent is specifically to initialize a numeric variable with a given ! byte sequence. In these cases, the same result can be obtained by using ! the 'TRANSFER' statement, as in this example. INTEGER(KIND=4) :: a a = TRANSFER ("abcd", a) ! equivalent to: a = 4Habcd --- 2866,2877 ---- In general, Hollerith constants were used to provide a rudimentary facility for handling character strings in early Fortran compilers, ! prior to the introduction of `CHARACTER' variables in Fortran 77; in ! those cases, the standard-compliant equivalent is to convert the ! program to use proper character strings. On occasion, there may be a ! case where the intent is specifically to initialize a numeric variable ! with a given byte sequence. In these cases, the same result can be ! obtained by using the `TRANSFER' statement, as in this example. INTEGER(KIND=4) :: a a = TRANSFER ("abcd", a) ! equivalent to: a = 4Habcd *************** variables: an integer "pointer" that hol *** 2865,2881 **** or, pointer ( , ), ( , ), ... The pointer is an integer that is intended to hold a memory address. ! The pointee may be an array or scalar. A pointee can be an assumed size ! array--that is, the last dimension may be left unspecified by using a ! '*' in place of a value--but a pointee cannot be an assumed shape array. ! No space is allocated for the pointee. The pointee may have its type declared before or after the pointer statement, and its array specification (if any) may be declared before, during, or after the pointer statement. The pointer may be declared as an integer prior to the pointer statement. However, some machines have ! default integer sizes that are different than the size of a pointer, and ! so the following code is not portable: integer ipt pointer (ipt, iarr) If a pointer is declared with a kind that is too small, the compiler --- 2891,2907 ---- or, pointer ( , ), ( , ), ... The pointer is an integer that is intended to hold a memory address. ! The pointee may be an array or scalar. A pointee can be an assumed ! size array--that is, the last dimension may be left unspecified by ! using a `*' in place of a value--but a pointee cannot be an assumed ! shape array. No space is allocated for the pointee. The pointee may have its type declared before or after the pointer statement, and its array specification (if any) may be declared before, during, or after the pointer statement. The pointer may be declared as an integer prior to the pointer statement. However, some machines have ! default integer sizes that are different than the size of a pointer, ! and so the following code is not portable: integer ipt pointer (ipt, iarr) If a pointer is declared with a kind that is too small, the compiler *************** explicit declaration of ipt's type is om *** 2886,2915 **** ensure that ipt is an integer variable large enough to hold a pointer. Pointer arithmetic is valid with Cray pointers, but it is not the ! same as C pointer arithmetic. Cray pointers are just ordinary integers, ! so the user is responsible for determining how many bytes to add to a ! pointer in order to increment it. Consider the following example: real target(10) real pointee(10) pointer (ipt, pointee) ipt = loc (target) ipt = ipt + 1 ! The last statement does not set 'ipt' to the address of 'target(1)', ! as it would in C pointer arithmetic. Adding '1' to 'ipt' just adds one ! byte to the address stored in 'ipt'. Any expression involving the pointee will be translated to use the value stored in the pointer as the base address. To get the address of elements, this extension provides an intrinsic ! function 'LOC()'. The 'LOC()' function is equivalent to the '&' operator in C, except the address is cast to an integer type: real ar(10) pointer(ipt, arpte(10)) real arpte ipt = loc(ar) ! Makes arpte is an alias for ar arpte(1) = 1.0 ! Sets ar(1) to 1.0 ! The pointer can also be set by a call to the 'MALLOC' intrinsic (see *note MALLOC::). Cray pointees often are used to alias an existing variable. For --- 2912,2942 ---- ensure that ipt is an integer variable large enough to hold a pointer. Pointer arithmetic is valid with Cray pointers, but it is not the ! same as C pointer arithmetic. Cray pointers are just ordinary ! integers, so the user is responsible for determining how many bytes to ! add to a pointer in order to increment it. Consider the following ! example: real target(10) real pointee(10) pointer (ipt, pointee) ipt = loc (target) ipt = ipt + 1 ! The last statement does not set `ipt' to the address of `target(1)', ! as it would in C pointer arithmetic. Adding `1' to `ipt' just adds one ! byte to the address stored in `ipt'. Any expression involving the pointee will be translated to use the value stored in the pointer as the base address. To get the address of elements, this extension provides an intrinsic ! function `LOC()'. The `LOC()' function is equivalent to the `&' operator in C, except the address is cast to an integer type: real ar(10) pointer(ipt, arpte(10)) real arpte ipt = loc(ar) ! Makes arpte is an alias for ar arpte(1) = 1.0 ! Sets ar(1) to 1.0 ! The pointer can also be set by a call to the `MALLOC' intrinsic (see *note MALLOC::). Cray pointees often are used to alias an existing variable. For *************** example: *** 2918,2947 **** integer iarr(10) pointer (ipt, iarr) ipt = loc(target) ! As long as 'ipt' remains unchanged, 'iarr' is now an alias for ! 'target'. The optimizer, however, will not detect this aliasing, so it ! is unsafe to use 'iarr' and 'target' simultaneously. Using a pointee in ! any way that violates the Fortran aliasing rules or assumptions is illegal. It is the user's responsibility to avoid doing this; the compiler works under the assumption that no such aliasing occurs. Cray pointers will work correctly when there is no aliasing (i.e., when they are used to access a dynamically allocated block of memory), and also in any routine where a pointee is used, but any variable with ! which it shares storage is not used. Code that violates these rules may ! not run as the user intends. This is not a bug in the optimizer; any ! code that violates the aliasing rules is illegal. (Note that this is ! not unique to GNU Fortran; any Fortran compiler that supports Cray pointers will "incorrectly" optimize code with illegal aliasing.) There are a number of restrictions on the attributes that can be applied to Cray pointers and pointees. Pointees may not have the ! 'ALLOCATABLE', 'INTENT', 'OPTIONAL', 'DUMMY', 'TARGET', 'INTRINSIC', or ! 'POINTER' attributes. Pointers may not have the 'DIMENSION', 'POINTER', ! 'TARGET', 'ALLOCATABLE', 'EXTERNAL', or 'INTRINSIC' attributes, nor may ! they be function results. Pointees may not occur in more than one ! pointer statement. A pointee cannot be a pointer. Pointees cannot ! occur in equivalence, common, or data statements. A Cray pointer may also point to a function or a subroutine. For example, the following excerpt is valid: --- 2945,2974 ---- integer iarr(10) pointer (ipt, iarr) ipt = loc(target) ! As long as `ipt' remains unchanged, `iarr' is now an alias for ! `target'. The optimizer, however, will not detect this aliasing, so it ! is unsafe to use `iarr' and `target' simultaneously. Using a pointee ! in any way that violates the Fortran aliasing rules or assumptions is illegal. It is the user's responsibility to avoid doing this; the compiler works under the assumption that no such aliasing occurs. Cray pointers will work correctly when there is no aliasing (i.e., when they are used to access a dynamically allocated block of memory), and also in any routine where a pointee is used, but any variable with ! which it shares storage is not used. Code that violates these rules ! may not run as the user intends. This is not a bug in the optimizer; ! any code that violates the aliasing rules is illegal. (Note that this ! is not unique to GNU Fortran; any Fortran compiler that supports Cray pointers will "incorrectly" optimize code with illegal aliasing.) There are a number of restrictions on the attributes that can be applied to Cray pointers and pointees. Pointees may not have the ! `ALLOCATABLE', `INTENT', `OPTIONAL', `DUMMY', `TARGET', `INTRINSIC', or ! `POINTER' attributes. Pointers may not have the `DIMENSION', ! `POINTER', `TARGET', `ALLOCATABLE', `EXTERNAL', or `INTRINSIC' ! attributes, nor may they be function results. Pointees may not occur ! in more than one pointer statement. A pointee cannot be a pointer. ! Pointees cannot occur in equivalence, common, or data statements. A Cray pointer may also point to a function or a subroutine. For example, the following excerpt is valid: *************** example, the following excerpt is valid: *** 2958,2986 **** A pointer may be modified during the course of a program, and this will change the location to which the pointee refers. However, when ! pointees are passed as arguments, they are treated as ordinary variables ! in the invoked function. Subsequent changes to the pointer will not ! change the base address of the array that was passed.  File: gfortran.info, Node: CONVERT specifier, Next: OpenMP, Prev: Cray pointers, Up: Extensions implemented in GNU Fortran ! 6.1.15 'CONVERT' specifier -------------------------- GNU Fortran allows the conversion of unformatted data between little- and big-endian representation to facilitate moving of data between ! different systems. The conversion can be indicated with the 'CONVERT' ! specifier on the 'OPEN' statement. *Note GFORTRAN_CONVERT_UNIT::, for an alternative way of specifying the data format via an environment variable. ! Valid values for 'CONVERT' are: ! 'CONVERT='NATIVE'' Use the native format. This is the default. ! 'CONVERT='SWAP'' Swap between little- and big-endian. ! 'CONVERT='LITTLE_ENDIAN'' Use the little-endian representation for unformatted files. ! 'CONVERT='BIG_ENDIAN'' Use the big-endian representation for unformatted files. Using the option could look like this: --- 2985,3016 ---- A pointer may be modified during the course of a program, and this will change the location to which the pointee refers. However, when ! pointees are passed as arguments, they are treated as ordinary ! variables in the invoked function. Subsequent changes to the pointer ! will not change the base address of the array that was passed.  File: gfortran.info, Node: CONVERT specifier, Next: OpenMP, Prev: Cray pointers, Up: Extensions implemented in GNU Fortran ! 6.1.15 `CONVERT' specifier -------------------------- GNU Fortran allows the conversion of unformatted data between little- and big-endian representation to facilitate moving of data between ! different systems. The conversion can be indicated with the `CONVERT' ! specifier on the `OPEN' statement. *Note GFORTRAN_CONVERT_UNIT::, for an alternative way of specifying the data format via an environment variable. ! Valid values for `CONVERT' are: ! `CONVERT='NATIVE'' Use the native format. This is the default. ! ! `CONVERT='SWAP'' Swap between little- and big-endian. ! ! `CONVERT='LITTLE_ENDIAN'' Use the little-endian representation for unformatted files. ! ! `CONVERT='BIG_ENDIAN'' Use the big-endian representation for unformatted files. Using the option could look like this: *************** variable. *** 2988,3001 **** convert='big_endian') The value of the conversion can be queried by using ! 'INQUIRE(CONVERT=ch)'. The values returned are ''BIG_ENDIAN'' and ! ''LITTLE_ENDIAN''. ! 'CONVERT' works between big- and little-endian for 'INTEGER' values ! of all supported kinds and for 'REAL' on IEEE systems of kinds 4 and 8. Conversion between different "extended double" types on different architectures such as m68k and x86_64, which GNU Fortran supports as ! 'REAL(KIND=10)' and 'REAL(KIND=16)', will probably not work. _Note that the values specified via the GFORTRAN_CONVERT_UNIT environment variable will override the CONVERT specifier in the open --- 3018,3031 ---- convert='big_endian') The value of the conversion can be queried by using ! `INQUIRE(CONVERT=ch)'. The values returned are `'BIG_ENDIAN'' and ! `'LITTLE_ENDIAN''. ! `CONVERT' works between big- and little-endian for `INTEGER' values ! of all supported kinds and for `REAL' on IEEE systems of kinds 4 and 8. Conversion between different "extended double" types on different architectures such as m68k and x86_64, which GNU Fortran supports as ! `REAL(KIND=10)' and `REAL(KIND=16)', will probably not work. _Note that the values specified via the GFORTRAN_CONVERT_UNIT environment variable will override the CONVERT specifier in the open *************** run-time behavior. *** 3022,3038 **** GNU Fortran strives to be compatible to the OpenMP Application Program Interface v4.0 (http://openmp.org/wp/openmp-specifications/). ! To enable the processing of the OpenMP directive '!$omp' in free-form ! source code; the 'c$omp', '*$omp' and '!$omp' directives in fixed form; ! the '!$' conditional compilation sentinels in free form; and the 'c$', ! '*$' and '!$' sentinels in fixed form, 'gfortran' needs to be invoked ! with the '-fopenmp'. This also arranges for automatic linking of the ! GNU Offloading and Multi Processing Runtime Library *note libgomp: ! (libgomp)Top. The OpenMP Fortran runtime library routines are provided both in a ! form of a Fortran 90 module named 'omp_lib' and in a form of a Fortran ! 'include' file named 'omp_lib.h'. An example of a parallelized loop taken from Appendix A.1 of the OpenMP Application Program Interface v2.5: --- 3052,3068 ---- GNU Fortran strives to be compatible to the OpenMP Application Program Interface v4.0 (http://openmp.org/wp/openmp-specifications/). ! To enable the processing of the OpenMP directive `!$omp' in ! free-form source code; the `c$omp', `*$omp' and `!$omp' directives in ! fixed form; the `!$' conditional compilation sentinels in free form; ! and the `c$', `*$' and `!$' sentinels in fixed form, `gfortran' needs ! to be invoked with the `-fopenmp'. This also arranges for automatic ! linking of the GNU Offloading and Multi Processing Runtime Library ! *note libgomp: (libgomp)Top. The OpenMP Fortran runtime library routines are provided both in a ! form of a Fortran 90 module named `omp_lib' and in a form of a Fortran ! `include' file named `omp_lib.h'. An example of a parallelized loop taken from Appendix A.1 of the OpenMP Application Program Interface v2.5: *************** OpenMP Application Program Interface v2. *** 3047,3063 **** END SUBROUTINE A1 Please note: ! * '-fopenmp' implies '-frecursive', i.e., all local arrays will be ! allocated on the stack. When porting existing code to OpenMP, this ! may lead to surprising results, especially to segmentation faults ! if the stacksize is limited. * On glibc-based systems, OpenMP enabled applications cannot be statically linked due to limitations of the underlying pthreads-implementation. It might be possible to get a working ! solution if '-Wl,--whole-archive -lpthread -Wl,--no-whole-archive' is added to the command line. However, this is not supported by ! 'gcc' and thus not recommended.  File: gfortran.info, Node: OpenACC, Next: Argument list functions, Prev: OpenMP, Up: Extensions implemented in GNU Fortran --- 3077,3093 ---- END SUBROUTINE A1 Please note: ! * `-fopenmp' implies `-frecursive', i.e., all local arrays will be ! allocated on the stack. When porting existing code to OpenMP, ! this may lead to surprising results, especially to segmentation ! faults if the stacksize is limited. * On glibc-based systems, OpenMP enabled applications cannot be statically linked due to limitations of the underlying pthreads-implementation. It might be possible to get a working ! solution if `-Wl,--whole-archive -lpthread -Wl,--no-whole-archive' is added to the command line. However, this is not supported by ! `gcc' and thus not recommended.  File: gfortran.info, Node: OpenACC, Next: Argument list functions, Prev: OpenMP, Up: Extensions implemented in GNU Fortran *************** influence run-time behavior. *** 3073,3115 **** GNU Fortran strives to be compatible to the OpenACC Application Programming Interface v2.0 (http://www.openacc.org/). ! To enable the processing of the OpenACC directive '!$acc' in ! free-form source code; the 'c$acc', '*$acc' and '!$acc' directives in ! fixed form; the '!$' conditional compilation sentinels in free form; and ! the 'c$', '*$' and '!$' sentinels in fixed form, 'gfortran' needs to be ! invoked with the '-fopenacc'. This also arranges for automatic linking ! of the GNU Offloading and Multi Processing Runtime Library *note ! libgomp: (libgomp)Top. The OpenACC Fortran runtime library routines are provided both in a ! form of a Fortran 90 module named 'openacc' and in a form of a Fortran ! 'include' file named 'openacc_lib.h'. Note that this is an experimental feature, incomplete, and subject to ! change in future versions of GCC. See ! for more information.  File: gfortran.info, Node: Argument list functions, Next: Read/Write after EOF marker, Prev: OpenACC, Up: Extensions implemented in GNU Fortran ! 6.1.18 Argument list functions '%VAL', '%REF' and '%LOC' -------------------------------------------------------- ! GNU Fortran supports argument list functions '%VAL', '%REF' and '%LOC' ! statements, for backward compatibility with g77. It is recommended that ! these should be used only for code that is accessing facilities outside ! of GNU Fortran, such as operating system or windowing facilities. It is ! best to constrain such uses to isolated portions of a program-portions ! that deal specifically and exclusively with low-level, system-dependent ! facilities. Such portions might well provide a portable interface for ! use by the program as a whole, but are themselves not portable, and ! should be thoroughly tested each time they are rebuilt using a new ! compiler or version of a compiler. ! '%VAL' passes a scalar argument by value, '%REF' passes it by ! reference and '%LOC' passes its memory location. Since gfortran already ! passes scalar arguments by reference, '%REF' is in effect a do-nothing. ! '%LOC' has the same effect as a Fortran pointer. An example of passing an argument by value to a C subroutine foo.: C --- 3103,3145 ---- GNU Fortran strives to be compatible to the OpenACC Application Programming Interface v2.0 (http://www.openacc.org/). ! To enable the processing of the OpenACC directive `!$acc' in ! free-form source code; the `c$acc', `*$acc' and `!$acc' directives in ! fixed form; the `!$' conditional compilation sentinels in free form; ! and the `c$', `*$' and `!$' sentinels in fixed form, `gfortran' needs ! to be invoked with the `-fopenacc'. This also arranges for automatic ! linking of the GNU Offloading and Multi Processing Runtime Library ! *note libgomp: (libgomp)Top. The OpenACC Fortran runtime library routines are provided both in a ! form of a Fortran 90 module named `openacc' and in a form of a Fortran ! `include' file named `openacc_lib.h'. Note that this is an experimental feature, incomplete, and subject to ! change in future versions of GCC. See ! `https://gcc.gnu.org/wiki/OpenACC' for more information.  File: gfortran.info, Node: Argument list functions, Next: Read/Write after EOF marker, Prev: OpenACC, Up: Extensions implemented in GNU Fortran ! 6.1.18 Argument list functions `%VAL', `%REF' and `%LOC' -------------------------------------------------------- ! GNU Fortran supports argument list functions `%VAL', `%REF' and `%LOC' ! statements, for backward compatibility with g77. It is recommended ! that these should be used only for code that is accessing facilities ! outside of GNU Fortran, such as operating system or windowing ! facilities. It is best to constrain such uses to isolated portions of ! a program-portions that deal specifically and exclusively with ! low-level, system-dependent facilities. Such portions might well ! provide a portable interface for use by the program as a whole, but are ! themselves not portable, and should be thoroughly tested each time they ! are rebuilt using a new compiler or version of a compiler. ! `%VAL' passes a scalar argument by value, `%REF' passes it by ! reference and `%LOC' passes its memory location. Since gfortran ! already passes scalar arguments by reference, `%REF' is in effect a ! do-nothing. `%LOC' has the same effect as a Fortran pointer. An example of passing an argument by value to a C subroutine foo.: C *************** passes scalar arguments by reference, '% *** 3122,3130 **** end For details refer to the g77 manual ! . ! Also, 'c_by_val.f' and its partner 'c_by_val.c' of the GNU Fortran testsuite are worth a look.  --- 3152,3160 ---- end For details refer to the g77 manual ! `https://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/index.html#Top'. ! Also, `c_by_val.f' and its partner `c_by_val.c' of the GNU Fortran testsuite are worth a look.  *************** File: gfortran.info, Node: Read/Write a *** 3133,3149 **** 6.1.19 Read/Write after EOF marker ---------------------------------- ! Some legacy codes rely on allowing 'READ' or 'WRITE' after the EOF file ! marker in order to find the end of a file. GNU Fortran normally rejects ! these codes with a run-time error message and suggests the user consider ! 'BACKSPACE' or 'REWIND' to properly position the file before the EOF ! marker. As an extension, the run-time error may be disabled using ! -std=legacy.  File: gfortran.info, Node: STRUCTURE and RECORD, Next: UNION and MAP, Prev: Read/Write after EOF marker, Up: Extensions implemented in GNU Fortran ! 6.1.20 'STRUCTURE' and 'RECORD' ------------------------------- Record structures are a pre-Fortran-90 vendor extension to create --- 3163,3179 ---- 6.1.19 Read/Write after EOF marker ---------------------------------- ! Some legacy codes rely on allowing `READ' or `WRITE' after the EOF file ! marker in order to find the end of a file. GNU Fortran normally rejects ! these codes with a run-time error message and suggests the user ! consider `BACKSPACE' or `REWIND' to properly position the file before ! the EOF marker. As an extension, the run-time error may be disabled ! using -std=legacy.  File: gfortran.info, Node: STRUCTURE and RECORD, Next: UNION and MAP, Prev: Read/Write after EOF marker, Up: Extensions implemented in GNU Fortran ! 6.1.20 `STRUCTURE' and `RECORD' ------------------------------- Record structures are a pre-Fortran-90 vendor extension to create *************** structures, only Fortran 90's "derived t *** 3152,3161 **** syntax. In many cases, record structures can easily be converted to derived ! types. To convert, replace 'STRUCTURE /'STRUCTURE-NAME'/' by 'TYPE' ! TYPE-NAME. Additionally, replace 'RECORD /'STRUCTURE-NAME'/' by ! 'TYPE('TYPE-NAME')'. Finally, in the component access, replace the ! period ('.') by the percent sign ('%'). Here is an example of code using the non portable record structure syntax: --- 3182,3191 ---- syntax. In many cases, record structures can easily be converted to derived ! types. To convert, replace `STRUCTURE /'STRUCTURE-NAME`/' by `TYPE' ! TYPE-NAME. Additionally, replace `RECORD /'STRUCTURE-NAME`/' by ! `TYPE('TYPE-NAME`)'. Finally, in the component access, replace the ! period (`.') by the percent sign (`%'). Here is an example of code using the non portable record structure syntax: *************** This code can easily be rewritten in the *** 3213,3222 **** GNU Fortran implements STRUCTURES like derived types with the following rules and exceptions: ! * Structures act like derived types with the 'SEQUENCE' attribute. Otherwise they may contain no specifiers. ! * Structures may share names with other symbols. For example, the following is invalid for derived types, but valid for structures: structure /header/ --- 3243,3252 ---- GNU Fortran implements STRUCTURES like derived types with the following rules and exceptions: ! * Structures act like derived types with the `SEQUENCE' attribute. Otherwise they may contain no specifiers. ! * Structures may share names with other symbols. For example, the following is invalid for derived types, but valid for structures: structure /header/ *************** rules and exceptions: *** 3233,3239 **** The type name may be ommitted, in which case the structure type itself is anonymous, and other structures of the same type cannot ! be instantiated. The following shows some examples: structure /appointment/ ! nested structure definition: app_time is an array of two 'time' --- 3263,3269 ---- The type name may be ommitted, in which case the structure type itself is anonymous, and other structures of the same type cannot ! be instantiated. The following shows some examples: structure /appointment/ ! nested structure definition: app_time is an array of two 'time' *************** rules and exceptions: *** 3257,3290 **** character(10) memo end structure ! * Structures may contain 'UNION' blocks. For more detail see the section on *note UNION and MAP::. * Structures support old-style initialization of components, like ! those described in *note Old-style variable initialization::. For array initializers, an initializer may contain a repeat ! specification of the form ' * ! '. The value of the integer indicates the number of times to repeat the constant initializer when expanding the initializer list.  File: gfortran.info, Node: UNION and MAP, Prev: STRUCTURE and RECORD, Up: Extensions implemented in GNU Fortran ! 6.1.21 'UNION' and 'MAP' ------------------------ Unions are an old vendor extension which were commonly used with the ! non-standard *note STRUCTURE and RECORD:: extensions. Use of 'UNION' ! and 'MAP' is automatically enabled with '-fdec-structure'. ! A 'UNION' declaration occurs within a structure; within the ! definition of each union is a number of 'MAP' blocks. Each 'MAP' shares storage with its sibling maps (in the same union), and the size of the union is the size of the largest map within it, just as with unions in C. The major difference is that component references do not indicate ! which union or map the component is in (the compiler gets to figure that ! out). Here is a small example: structure /myunion/ --- 3287,3320 ---- character(10) memo end structure ! * Structures may contain `UNION' blocks. For more detail see the section on *note UNION and MAP::. * Structures support old-style initialization of components, like ! those described in *note Old-style variable initialization::. For array initializers, an initializer may contain a repeat ! specification of the form ` * ! '. The value of the integer indicates the number of times to repeat the constant initializer when expanding the initializer list.  File: gfortran.info, Node: UNION and MAP, Prev: STRUCTURE and RECORD, Up: Extensions implemented in GNU Fortran ! 6.1.21 `UNION' and `MAP' ------------------------ Unions are an old vendor extension which were commonly used with the ! non-standard *note STRUCTURE and RECORD:: extensions. Use of `UNION' and ! `MAP' is automatically enabled with `-fdec-structure'. ! A `UNION' declaration occurs within a structure; within the ! definition of each union is a number of `MAP' blocks. Each `MAP' shares storage with its sibling maps (in the same union), and the size of the union is the size of the largest map within it, just as with unions in C. The major difference is that component references do not indicate ! which union or map the component is in (the compiler gets to figure ! that out). Here is a small example: structure /myunion/ *************** some features crucial to users in the fi *** 3385,3392 **** existence of a number of important extensions to the language. While some of the most useful or popular extensions are supported by the GNU Fortran compiler, not all existing extensions are supported. This ! section aims at listing these extensions and offering advice on how best ! make code that uses them running with the GNU Fortran compiler. * Menu: --- 3415,3422 ---- existence of a number of important extensions to the language. While some of the most useful or popular extensions are supported by the GNU Fortran compiler, not all existing extensions are supported. This ! section aims at listing these extensions and offering advice on how ! best make code that uses them running with the GNU Fortran compiler. * Menu: *************** make code that uses them running with th *** 3399,3410 ****  File: gfortran.info, Node: ENCODE and DECODE statements, Next: Variable FORMAT expressions, Up: Extensions not implemented in GNU Fortran ! 6.2.1 'ENCODE' and 'DECODE' statements -------------------------------------- ! GNU Fortran does not support the 'ENCODE' and 'DECODE' statements. ! These statements are best replaced by 'READ' and 'WRITE' statements ! involving internal files ('CHARACTER' variables and arrays), which have been part of the Fortran standard since Fortran 77. For example, replace a code fragment like --- 3429,3440 ----  File: gfortran.info, Node: ENCODE and DECODE statements, Next: Variable FORMAT expressions, Up: Extensions not implemented in GNU Fortran ! 6.2.1 `ENCODE' and `DECODE' statements -------------------------------------- ! GNU Fortran does not support the `ENCODE' and `DECODE' statements. ! These statements are best replaced by `READ' and `WRITE' statements ! involving internal files (`CHARACTER' variables and arrays), which have been part of the Fortran standard since Fortran 77. For example, replace a code fragment like *************** with the following: *** 3441,3455 ****  File: gfortran.info, Node: Variable FORMAT expressions, Next: Alternate complex function syntax, Prev: ENCODE and DECODE statements, Up: Extensions not implemented in GNU Fortran ! 6.2.2 Variable 'FORMAT' expressions ----------------------------------- ! A variable 'FORMAT' expression is format statement which includes angle ! brackets enclosing a Fortran expression: 'FORMAT(I)'. GNU Fortran does not support this legacy extension. The effect of variable format expressions can be reproduced by using the more powerful (and standard) ! combination of internal output and string formats. For example, replace ! a code fragment like this: WRITE(6,20) INT1 20 FORMAT(I) --- 3471,3485 ----  File: gfortran.info, Node: Variable FORMAT expressions, Next: Alternate complex function syntax, Prev: ENCODE and DECODE statements, Up: Extensions not implemented in GNU Fortran ! 6.2.2 Variable `FORMAT' expressions ----------------------------------- ! A variable `FORMAT' expression is format statement which includes angle ! brackets enclosing a Fortran expression: `FORMAT(I)'. GNU Fortran does not support this legacy extension. The effect of variable format expressions can be reproduced by using the more powerful (and standard) ! combination of internal output and string formats. For example, ! replace a code fragment like this: WRITE(6,20) INT1 20 FORMAT(I) *************** File: gfortran.info, Node: Alternate co *** 3480,3512 **** 6.2.3 Alternate complex function syntax --------------------------------------- ! Some Fortran compilers, including 'g77', let the user declare complex ! functions with the syntax 'COMPLEX FUNCTION name*16()', as well as ! 'COMPLEX*16 FUNCTION name()'. Both are non-standard, legacy extensions. ! 'gfortran' accepts the latter form, which is more common, but not the ! former.  File: gfortran.info, Node: Volatile COMMON blocks, Next: OPEN( ... NAME=), Prev: Alternate complex function syntax, Up: Extensions not implemented in GNU Fortran ! 6.2.4 Volatile 'COMMON' blocks ------------------------------ ! Some Fortran compilers, including 'g77', let the user declare 'COMMON' ! with the 'VOLATILE' attribute. This is invalid standard Fortran syntax ! and is not supported by 'gfortran'. Note that 'gfortran' accepts ! 'VOLATILE' variables in 'COMMON' blocks since revision 4.3.  File: gfortran.info, Node: OPEN( ... NAME=), Prev: Volatile COMMON blocks, Up: Extensions not implemented in GNU Fortran ! 6.2.5 'OPEN( ... NAME=)' ------------------------ ! Some Fortran compilers, including 'g77', let the user declare 'OPEN( ... ! NAME=)'. This is invalid standard Fortran syntax and is not supported ! by 'gfortran'. 'OPEN( ... NAME=)' should be replaced with 'OPEN( ... ! FILE=)'.  File: gfortran.info, Node: Mixed-Language Programming, Next: Coarray Programming, Prev: Extensions, Up: Top --- 3510,3542 ---- 6.2.3 Alternate complex function syntax --------------------------------------- ! Some Fortran compilers, including `g77', let the user declare complex ! functions with the syntax `COMPLEX FUNCTION name*16()', as well as ! `COMPLEX*16 FUNCTION name()'. Both are non-standard, legacy ! extensions. `gfortran' accepts the latter form, which is more common, ! but not the former.  File: gfortran.info, Node: Volatile COMMON blocks, Next: OPEN( ... NAME=), Prev: Alternate complex function syntax, Up: Extensions not implemented in GNU Fortran ! 6.2.4 Volatile `COMMON' blocks ------------------------------ ! Some Fortran compilers, including `g77', let the user declare `COMMON' ! with the `VOLATILE' attribute. This is invalid standard Fortran syntax ! and is not supported by `gfortran'. Note that `gfortran' accepts ! `VOLATILE' variables in `COMMON' blocks since revision 4.3.  File: gfortran.info, Node: OPEN( ... NAME=), Prev: Volatile COMMON blocks, Up: Extensions not implemented in GNU Fortran ! 6.2.5 `OPEN( ... NAME=)' ------------------------ ! Some Fortran compilers, including `g77', let the user declare `OPEN( ! ... NAME=)'. This is invalid standard Fortran syntax and is not ! supported by `gfortran'. `OPEN( ... NAME=)' should be replaced with ! `OPEN( ... FILE=)'.  File: gfortran.info, Node: Mixed-Language Programming, Next: Coarray Programming, Prev: Extensions, Up: Top *************** File: gfortran.info, Node: Mixed-Langua *** 3521,3530 **** * Non-Fortran Main Program:: * Naming and argument-passing conventions:: ! This chapter is about mixed-language interoperability, but also applies ! if one links Fortran code compiled by different compilers. In most ! cases, use of the C Binding features of the Fortran 2003 standard is ! sufficient, and their use is highly recommended.  File: gfortran.info, Node: Interoperability with C, Next: GNU Fortran Compiler Directives, Up: Mixed-Language Programming --- 3551,3560 ---- * Non-Fortran Main Program:: * Naming and argument-passing conventions:: ! This chapter is about mixed-language interoperability, but also ! applies if one links Fortran code compiled by different compilers. In ! most cases, use of the C Binding features of the Fortran 2003 standard ! is sufficient, and their use is highly recommended.  File: gfortran.info, Node: Interoperability with C, Next: GNU Fortran Compiler Directives, Up: Mixed-Language Programming *************** File: gfortran.info, Node: Interoperabi *** 3541,3561 **** * Working with Pointers:: * Further Interoperability of Fortran with C:: ! Since Fortran 2003 (ISO/IEC 1539-1:2004(E)) there is a standardized way ! to generate procedure and derived-type declarations and global variables ! which are interoperable with C (ISO/IEC 9899:1999). The 'bind(C)' ! attribute has been added to inform the compiler that a symbol shall be ! interoperable with C; also, some constraints are added. Note, however, ! that not all C features have a Fortran equivalent or vice versa. For ! instance, neither C's unsigned integers nor C's functions with variable ! number of arguments have an equivalent in Fortran. ! Note that array dimensions are reversely ordered in C and that arrays ! in C always start with index 0 while in Fortran they start by default ! with 1. Thus, an array declaration 'A(n,m)' in Fortran matches ! 'A[m][n]' in C and accessing the element 'A(i,j)' matches 'A[j-1][i-1]'. ! The element following 'A(i,j)' (C: 'A[j-1][i-1]'; assuming i < n) in ! memory is 'A(i+1,j)' (C: 'A[j-1][i]').  File: gfortran.info, Node: Intrinsic Types, Next: Derived Types and struct, Up: Interoperability with C --- 3571,3591 ---- * Working with Pointers:: * Further Interoperability of Fortran with C:: ! Since Fortran 2003 (ISO/IEC 1539-1:2004(E)) there is a standardized ! way to generate procedure and derived-type declarations and global ! variables which are interoperable with C (ISO/IEC 9899:1999). The ! `bind(C)' attribute has been added to inform the compiler that a symbol ! shall be interoperable with C; also, some constraints are added. Note, ! however, that not all C features have a Fortran equivalent or vice ! versa. For instance, neither C's unsigned integers nor C's functions ! with variable number of arguments have an equivalent in Fortran. ! Note that array dimensions are reversely ordered in C and that ! arrays in C always start with index 0 while in Fortran they start by ! default with 1. Thus, an array declaration `A(n,m)' in Fortran matches ! `A[m][n]' in C and accessing the element `A(i,j)' matches ! `A[j-1][i-1]'. The element following `A(i,j)' (C: `A[j-1][i-1]'; ! assuming i < n) in memory is `A(i+1,j)' (C: `A[j-1][i]').  File: gfortran.info, Node: Intrinsic Types, Next: Derived Types and struct, Up: Interoperability with C *************** File: gfortran.info, Node: Intrinsic Ty *** 3564,3582 **** --------------------- In order to ensure that exactly the same variable type and kind is used ! in C and Fortran, the named constants shall be used which are defined in ! the 'ISO_C_BINDING' intrinsic module. That module contains named constants for kind parameters and character named constants for the ! escape sequences in C. For a list of the constants, see *note ISO_C_BINDING::. For logical types, please note that the Fortran standard only ! guarantees interoperability between C99's '_Bool' and Fortran's ! 'C_Bool'-kind logicals and C99 defines that 'true' has the value 1 and ! 'false' the value 0. Using any other integer value with GNU Fortran's ! 'LOGICAL' (with any kind parameter) gives an undefined result. (Passing ! other integer values than 0 and 1 to GCC's '_Bool' is also undefined, ! unless the integer is explicitly or implicitly casted to '_Bool'.)  File: gfortran.info, Node: Derived Types and struct, Next: Interoperable Global Variables, Prev: Intrinsic Types, Up: Interoperability with C --- 3594,3613 ---- --------------------- In order to ensure that exactly the same variable type and kind is used ! in C and Fortran, the named constants shall be used which are defined ! in the `ISO_C_BINDING' intrinsic module. That module contains named constants for kind parameters and character named constants for the ! escape sequences in C. For a list of the constants, see *note ISO_C_BINDING::. For logical types, please note that the Fortran standard only ! guarantees interoperability between C99's `_Bool' and Fortran's ! `C_Bool'-kind logicals and C99 defines that `true' has the value 1 and ! `false' the value 0. Using any other integer value with GNU Fortran's ! `LOGICAL' (with any kind parameter) gives an undefined result. ! (Passing other integer values than 0 and 1 to GCC's `_Bool' is also ! undefined, unless the integer is explicitly or implicitly casted to ! `_Bool'.)  File: gfortran.info, Node: Derived Types and struct, Next: Interoperable Global Variables, Prev: Intrinsic Types, Up: Interoperability with C *************** File: gfortran.info, Node: Derived Type *** 3584,3591 **** 7.1.2 Derived Types and struct ------------------------------ ! For compatibility of derived types with 'struct', one needs to use the ! 'BIND(C)' attribute in the type declaration. For instance, the following type declaration USE ISO_C_BINDING --- 3615,3622 ---- 7.1.2 Derived Types and struct ------------------------------ ! For compatibility of derived types with `struct', one needs to use the ! `BIND(C)' attribute in the type declaration. For instance, the following type declaration USE ISO_C_BINDING *************** following type declaration *** 3597,3603 **** CHARACTER(KIND=C_CHAR) :: str(5) END TYPE ! matches the following 'struct' declaration in C struct { int i1, i2; --- 3628,3634 ---- CHARACTER(KIND=C_CHAR) :: str(5) END TYPE ! matches the following `struct' declaration in C struct { int i1, i2; *************** following type declaration *** 3609,3618 **** } myType; Derived types with the C binding attribute shall not have the ! 'sequence' attribute, type parameters, the 'extends' attribute, nor type-bound procedures. Every component must be of interoperable type ! and kind and may not have the 'pointer' or 'allocatable' attribute. The ! names of the components are irrelevant for interoperability. As there exist no direct Fortran equivalents, neither unions nor structs with bit field or variable-length array members are --- 3640,3649 ---- } myType; Derived types with the C binding attribute shall not have the ! `sequence' attribute, type parameters, the `extends' attribute, nor type-bound procedures. Every component must be of interoperable type ! and kind and may not have the `pointer' or `allocatable' attribute. ! The names of the components are irrelevant for interoperability. As there exist no direct Fortran equivalents, neither unions nor structs with bit field or variable-length array members are *************** File: gfortran.info, Node: Interoperabl *** 3626,3634 **** Variables can be made accessible from C using the C binding attribute, optionally together with specifying a binding name. Those variables ! have to be declared in the declaration part of a 'MODULE', be of ! interoperable type, and have neither the 'pointer' nor the 'allocatable' ! attribute. MODULE m USE myType_module --- 3657,3665 ---- Variables can be made accessible from C using the C binding attribute, optionally together with specifying a binding name. Those variables ! have to be declared in the declaration part of a `MODULE', be of ! interoperable type, and have neither the `pointer' nor the ! `allocatable' attribute. MODULE m USE myType_module *************** attribute. *** 3637,3650 **** type(myType), bind(C) :: tp END MODULE ! Here, '_MyProject_flags' is the case-sensitive name of the variable ! as seen from C programs while 'global_flag' is the case-insensitive name ! as seen from Fortran. If no binding name is specified, as for TP, the C ! binding name is the (lowercase) Fortran binding name. If a binding name ! is specified, only a single variable may be after the double colon. ! Note of warning: You cannot use a global variable to access ERRNO of the ! C library as the C standard allows it to be a macro. Use the 'IERRNO' ! intrinsic (GNU extension) instead.  File: gfortran.info, Node: Interoperable Subroutines and Functions, Next: Working with Pointers, Prev: Interoperable Global Variables, Up: Interoperability with C --- 3668,3681 ---- type(myType), bind(C) :: tp END MODULE ! Here, `_MyProject_flags' is the case-sensitive name of the variable ! as seen from C programs while `global_flag' is the case-insensitive ! name as seen from Fortran. If no binding name is specified, as for TP, ! the C binding name is the (lowercase) Fortran binding name. If a ! binding name is specified, only a single variable may be after the ! double colon. Note of warning: You cannot use a global variable to ! access ERRNO of the C library as the C standard allows it to be a ! macro. Use the `IERRNO' intrinsic (GNU extension) instead.  File: gfortran.info, Node: Interoperable Subroutines and Functions, Next: Working with Pointers, Prev: Interoperable Global Variables, Up: Interoperability with C *************** File: gfortran.info, Node: Interoperabl *** 3652,3672 **** 7.1.4 Interoperable Subroutines and Functions --------------------------------------------- ! Subroutines and functions have to have the 'BIND(C)' attribute to be ! compatible with C. The dummy argument declaration is relatively straightforward. However, one needs to be careful because C uses call-by-value by default while Fortran behaves usually similar to call-by-reference. Furthermore, strings and pointers are handled differently. Note that in Fortran 2003 and 2008 only explicit size and assumed-size arrays are supported but not assumed-shape or ! deferred-shape (i.e. allocatable or pointer) arrays. However, those are allowed since the Technical Specification 29113, see *note Further Interoperability of Fortran with C:: ! To pass a variable by value, use the 'VALUE' attribute. Thus, the following C prototype ! int func(int i, int *j) matches the Fortran declaration --- 3683,3703 ---- 7.1.4 Interoperable Subroutines and Functions --------------------------------------------- ! Subroutines and functions have to have the `BIND(C)' attribute to be ! compatible with C. The dummy argument declaration is relatively straightforward. However, one needs to be careful because C uses call-by-value by default while Fortran behaves usually similar to call-by-reference. Furthermore, strings and pointers are handled differently. Note that in Fortran 2003 and 2008 only explicit size and assumed-size arrays are supported but not assumed-shape or ! deferred-shape (i.e. allocatable or pointer) arrays. However, those are allowed since the Technical Specification 29113, see *note Further Interoperability of Fortran with C:: ! To pass a variable by value, use the `VALUE' attribute. Thus, the following C prototype ! `int func(int i, int *j)' matches the Fortran declaration *************** following C prototype *** 3675,3687 **** integer(c_int), VALUE :: i integer(c_int) :: j ! Note that pointer arguments also frequently need the 'VALUE' attribute, see *note Working with Pointers::. Strings are handled quite differently in C and Fortran. In C a ! string is a 'NUL'-terminated array of characters while in Fortran each string has a length associated with it and is thus not terminated (by ! e.g. 'NUL'). For example, if one wants to use the following C function, #include --- 3706,3718 ---- integer(c_int), VALUE :: i integer(c_int) :: j ! Note that pointer arguments also frequently need the `VALUE' attribute, see *note Working with Pointers::. Strings are handled quite differently in C and Fortran. In C a ! string is a `NUL'-terminated array of characters while in Fortran each string has a length associated with it and is thus not terminated (by ! e.g. `NUL'). For example, if one wants to use the following C function, #include *************** function, *** 3701,3720 **** end interface call print_c(C_CHAR_"Hello World"//C_NULL_CHAR) ! As the example shows, one needs to ensure that the string is 'NUL' ! terminated. Additionally, the dummy argument STRING of 'print_C' is a ! length-one assumed-size array; using 'character(len=*)' is not allowed. ! The example above uses 'c_char_"Hello World"' to ensure the string literal has the right type; typically the default character kind and ! 'c_char' are the same and thus '"Hello World"' is equivalent. However, the standard does not guarantee this. The use of strings is now further illustrated using the C library ! function 'strncpy', whose prototype is char *strncpy(char *restrict s1, const char *restrict s2, size_t n); ! The function 'strncpy' copies at most N characters from string S2 to S1 and returns S1. In the following example, we ignore the return value: --- 3732,3751 ---- end interface call print_c(C_CHAR_"Hello World"//C_NULL_CHAR) ! As the example shows, one needs to ensure that the string is `NUL' ! terminated. Additionally, the dummy argument STRING of `print_C' is a ! length-one assumed-size array; using `character(len=*)' is not allowed. ! The example above uses `c_char_"Hello World"' to ensure the string literal has the right type; typically the default character kind and ! `c_char' are the same and thus `"Hello World"' is equivalent. However, the standard does not guarantee this. The use of strings is now further illustrated using the C library ! function `strncpy', whose prototype is char *strncpy(char *restrict s1, const char *restrict s2, size_t n); ! The function `strncpy' copies at most N characters from string S2 to S1 and returns S1. In the following example, we ignore the return value: *************** File: gfortran.info, Node: Working with *** 3747,3756 **** --------------------------- C pointers are represented in Fortran via the special opaque derived ! type 'type(c_ptr)' (with private components). Thus one needs to use intrinsic conversion procedures to convert from or to C pointers. ! For some applications, using an assumed type ('TYPE(*)') can be an alternative to a C pointer; see *note Further Interoperability of Fortran with C::. --- 3778,3787 ---- --------------------------- C pointers are represented in Fortran via the special opaque derived ! type `type(c_ptr)' (with private components). Thus one needs to use intrinsic conversion procedures to convert from or to C pointers. ! For some applications, using an assumed type (`TYPE(*)') can be an alternative to a C pointer; see *note Further Interoperability of Fortran with C::. *************** Fortran with C::. *** 3767,3787 **** call c_f_pointer(cptr2, ps) call c_f_pointer(cptr2, pa, shape=[7]) ! When converting C to Fortran arrays, the one-dimensional 'SHAPE' argument has to be passed. If a pointer is a dummy-argument of an interoperable procedure, it ! usually has to be declared using the 'VALUE' attribute. 'void*' matches ! 'TYPE(C_PTR), VALUE', while 'TYPE(C_PTR)' alone matches 'void**'. Procedure pointers are handled analogously to pointers; the C type is ! 'TYPE(C_FUNPTR)' and the intrinsic conversion procedures are ! 'C_F_PROCPOINTER' and 'C_FUNLOC'. Let us consider two examples of actually passing a procedure pointer from C to Fortran and vice versa. Note that these examples are also ! very similar to passing ordinary pointers between both languages. ! First, consider this code in C: /* Procedure implemented in Fortran. */ void get_values (void (*)(double)); --- 3798,3819 ---- call c_f_pointer(cptr2, ps) call c_f_pointer(cptr2, pa, shape=[7]) ! When converting C to Fortran arrays, the one-dimensional `SHAPE' argument has to be passed. If a pointer is a dummy-argument of an interoperable procedure, it ! usually has to be declared using the `VALUE' attribute. `void*' ! matches `TYPE(C_PTR), VALUE', while `TYPE(C_PTR)' alone matches ! `void**'. Procedure pointers are handled analogously to pointers; the C type is ! `TYPE(C_FUNPTR)' and the intrinsic conversion procedures are ! `C_F_PROCPOINTER' and `C_FUNLOC'. Let us consider two examples of actually passing a procedure pointer from C to Fortran and vice versa. Note that these examples are also ! very similar to passing ordinary pointers between both languages. First, ! consider this code in C: /* Procedure implemented in Fortran. */ void get_values (void (*)(double)); *************** First, consider this code in C: *** 3800,3808 **** get_values (&print_it); } ! A matching implementation for 'get_values' in Fortran, that correctly receives the procedure pointer from C and is able to call it, is given ! in the following 'MODULE': MODULE m IMPLICIT NONE --- 3832,3840 ---- get_values (&print_it); } ! A matching implementation for `get_values' in Fortran, that correctly receives the procedure pointer from C and is able to call it, is given ! in the following `MODULE': MODULE m IMPLICIT NONE *************** File: gfortran.info, Node: Further Inte *** 3893,3958 **** The Technical Specification ISO/IEC TS 29113:2012 on further interoperability of Fortran with C extends the interoperability support ! of Fortran 2003 and Fortran 2008. Besides removing some restrictions ! and constraints, it adds assumed-type ('TYPE(*)') and assumed-rank ! ('dimension') variables and allows for interoperability of assumed-shape, assumed-rank and deferred-shape arrays, including allocatables and pointers. Note: Currently, GNU Fortran does not support the array descriptor (dope vector) as specified in the Technical Specification, but uses an ! array descriptor with different fields. The Chasm Language ! Interoperability Tools, , provide ! an interface to GNU Fortran's array descriptor. The Technical Specification adds the following new features, which are supported by GNU Fortran: ! * The 'ASYNCHRONOUS' attribute has been clarified and extended to allow its use with asynchronous communication in user-provided libraries such as in implementations of the Message Passing Interface specification. ! * Many constraints have been relaxed, in particular for the 'C_LOC' ! and 'C_F_POINTER' intrinsics. ! * The 'OPTIONAL' attribute is now allowed for dummy arguments; an ! absent argument matches a 'NULL' pointer. ! * Assumed types ('TYPE(*)') have been added, which may only be used for dummy arguments. They are unlimited polymorphic but contrary ! to 'CLASS(*)' they do not contain any type information, similar to ! C's 'void *' pointers. Expressions of any type and kind can be ! passed; thus, it can be used as replacement for 'TYPE(C_PTR)', ! avoiding the use of 'C_LOC' in the caller. ! Note, however, that 'TYPE(*)' only accepts scalar arguments, unless ! the 'DIMENSION' is explicitly specified. As 'DIMENSION(*)' only ! supports array (including array elements) but no scalars, it is not ! a full replacement for 'C_LOC'. On the other hand, assumed-type ! assumed-rank dummy arguments ('TYPE(*), DIMENSION(..)') allow for ! both scalars and arrays, but require special code on the callee ! side to handle the array descriptor. ! * Assumed-rank arrays ('DIMENSION(..)') as dummy argument allow that scalars and arrays of any rank can be passed as actual argument. ! As the Technical Specification does not provide for direct means to ! operate with them, they have to be used either from the C side or ! be converted using 'C_LOC' and 'C_F_POINTER' to scalars or arrays ! of a specific rank. The rank can be determined using the 'RANK' ! intrinisic. Currently unimplemented: * GNU Fortran always uses an array descriptor, which does not match ! the one of the Technical Specification. The ! 'ISO_Fortran_binding.h' header file and the C functions it specifies are not available. * Using assumed-shape, assumed-rank and deferred-shape arrays in ! 'BIND(C)' procedures is not fully supported. In particular, C ! interoperable strings of other length than one are not supported as ! this requires the new array descriptor.  File: gfortran.info, Node: GNU Fortran Compiler Directives, Next: Non-Fortran Main Program, Prev: Interoperability with C, Up: Mixed-Language Programming --- 3925,3990 ---- The Technical Specification ISO/IEC TS 29113:2012 on further interoperability of Fortran with C extends the interoperability support ! of Fortran 2003 and Fortran 2008. Besides removing some restrictions ! and constraints, it adds assumed-type (`TYPE(*)') and assumed-rank ! (`dimension') variables and allows for interoperability of assumed-shape, assumed-rank and deferred-shape arrays, including allocatables and pointers. Note: Currently, GNU Fortran does not support the array descriptor (dope vector) as specified in the Technical Specification, but uses an ! array descriptor with different fields. The Chasm Language ! Interoperability Tools, `http://chasm-interop.sourceforge.net/', ! provide an interface to GNU Fortran's array descriptor. The Technical Specification adds the following new features, which are supported by GNU Fortran: ! * The `ASYNCHRONOUS' attribute has been clarified and extended to allow its use with asynchronous communication in user-provided libraries such as in implementations of the Message Passing Interface specification. ! * Many constraints have been relaxed, in particular for the `C_LOC' ! and `C_F_POINTER' intrinsics. ! * The `OPTIONAL' attribute is now allowed for dummy arguments; an ! absent argument matches a `NULL' pointer. ! * Assumed types (`TYPE(*)') have been added, which may only be used for dummy arguments. They are unlimited polymorphic but contrary ! to `CLASS(*)' they do not contain any type information, similar to ! C's `void *' pointers. Expressions of any type and kind can be ! passed; thus, it can be used as replacement for `TYPE(C_PTR)', ! avoiding the use of `C_LOC' in the caller. ! Note, however, that `TYPE(*)' only accepts scalar arguments, ! unless the `DIMENSION' is explicitly specified. As `DIMENSION(*)' ! only supports array (including array elements) but no scalars, it ! is not a full replacement for `C_LOC'. On the other hand, ! assumed-type assumed-rank dummy arguments (`TYPE(*), ! DIMENSION(..)') allow for both scalars and arrays, but require ! special code on the callee side to handle the array descriptor. ! * Assumed-rank arrays (`DIMENSION(..)') as dummy argument allow that scalars and arrays of any rank can be passed as actual argument. ! As the Technical Specification does not provide for direct means ! to operate with them, they have to be used either from the C side ! or be converted using `C_LOC' and `C_F_POINTER' to scalars or ! arrays of a specific rank. The rank can be determined using the ! `RANK' intrinisic. Currently unimplemented: * GNU Fortran always uses an array descriptor, which does not match ! the one of the Technical Specification. The ! `ISO_Fortran_binding.h' header file and the C functions it specifies are not available. * Using assumed-shape, assumed-rank and deferred-shape arrays in ! `BIND(C)' procedures is not fully supported. In particular, C ! interoperable strings of other length than one are not supported ! as this requires the new array descriptor.  File: gfortran.info, Node: GNU Fortran Compiler Directives, Next: Non-Fortran Main Program, Prev: Interoperability with C, Up: Mixed-Language Programming *************** allow the user to choose specific implem *** 3966,3980 **** directives can be used to set attributes of variables and procedures which are not part of the standard. Whether a given attribute is supported and its exact effects depend on both the operating system and ! on the processor; see *note C Extensions: (gcc)Top. for details. For procedures and procedure pointers, the following attributes can be used to change the calling convention: ! * 'CDECL' - standard C calling convention ! * 'STDCALL' - convention where the called procedure pops the stack ! * 'FASTCALL' - part of the arguments are passed via registers instead ! using the stack Besides changing the calling convention, the attributes also influence the decoration of the symbol name, e.g., by a leading --- 3998,4014 ---- directives can be used to set attributes of variables and procedures which are not part of the standard. Whether a given attribute is supported and its exact effects depend on both the operating system and ! on the processor; see *note C Extensions: (gcc)Top. for details. For procedures and procedure pointers, the following attributes can be used to change the calling convention: ! * `CDECL' - standard C calling convention ! ! * `STDCALL' - convention where the called procedure pops the stack ! ! * `FASTCALL' - part of the arguments are passed via registers ! instead using the stack Besides changing the calling convention, the attributes also influence the decoration of the symbol name, e.g., by a leading *************** the stack. When assigning a procedure t *** 3983,4020 **** should use the same calling convention. On some systems, procedures and global variables (module variables ! and 'COMMON' blocks) need special handling to be accessible when they are in a shared library. The following attributes are available: ! * 'DLLEXPORT' - provide a global pointer to a pointer in the DLL ! * 'DLLIMPORT' - reference the function or variable using a global pointer ! For dummy arguments, the 'NO_ARG_CHECK' attribute can be used; in ! other compilers, it is also known as 'IGNORE_TKR'. For dummy arguments with this attribute actual arguments of any type and kind (similar to ! 'TYPE(*)'), scalars and arrays of any rank (no equivalent in Fortran ! standard) are accepted. As with 'TYPE(*)', the argument is unlimited polymorphic and no type information is available. Additionally, the ! argument may only be passed to dummy arguments with the 'NO_ARG_CHECK' ! attribute and as argument to the 'PRESENT' intrinsic function and to ! 'C_LOC' of the 'ISO_C_BINDING' module. ! Variables with 'NO_ARG_CHECK' attribute shall be of assumed-type ! ('TYPE(*)'; recommended) or of type 'INTEGER', 'LOGICAL', 'REAL' or ! 'COMPLEX'. They shall not have the 'ALLOCATE', 'CODIMENSION', ! 'INTENT(OUT)', 'POINTER' or 'VALUE' attribute; furthermore, they shall ! be either scalar or of assumed-size ('dimension(*)'). As 'TYPE(*)', the ! 'NO_ARG_CHECK' attribute requires an explicit interface. ! * 'NO_ARG_CHECK' - disable the type, kind and rank checking The attributes are specified using the syntax ! '!GCC$ ATTRIBUTES' ATTRIBUTE-LIST '::' VARIABLE-LIST where in free-form source code only whitespace is allowed before ! '!GCC$' and in fixed-form source code '!GCC$', 'cGCC$' or '*GCC$' shall start in the first column. For procedures, the compiler directives shall be placed into the body --- 4017,4055 ---- should use the same calling convention. On some systems, procedures and global variables (module variables ! and `COMMON' blocks) need special handling to be accessible when they are in a shared library. The following attributes are available: ! * `DLLEXPORT' - provide a global pointer to a pointer in the DLL ! ! * `DLLIMPORT' - reference the function or variable using a global pointer ! For dummy arguments, the `NO_ARG_CHECK' attribute can be used; in ! other compilers, it is also known as `IGNORE_TKR'. For dummy arguments with this attribute actual arguments of any type and kind (similar to ! `TYPE(*)'), scalars and arrays of any rank (no equivalent in Fortran ! standard) are accepted. As with `TYPE(*)', the argument is unlimited polymorphic and no type information is available. Additionally, the ! argument may only be passed to dummy arguments with the `NO_ARG_CHECK' ! attribute and as argument to the `PRESENT' intrinsic function and to ! `C_LOC' of the `ISO_C_BINDING' module. ! Variables with `NO_ARG_CHECK' attribute shall be of assumed-type ! (`TYPE(*)'; recommended) or of type `INTEGER', `LOGICAL', `REAL' or ! `COMPLEX'. They shall not have the `ALLOCATE', `CODIMENSION', ! `INTENT(OUT)', `POINTER' or `VALUE' attribute; furthermore, they shall ! be either scalar or of assumed-size (`dimension(*)'). As `TYPE(*)', the ! `NO_ARG_CHECK' attribute requires an explicit interface. ! * `NO_ARG_CHECK' - disable the type, kind and rank checking The attributes are specified using the syntax ! `!GCC$ ATTRIBUTES' ATTRIBUTE-LIST `::' VARIABLE-LIST where in free-form source code only whitespace is allowed before ! `!GCC$' and in fixed-form source code `!GCC$', `cGCC$' or `*GCC$' shall start in the first column. For procedures, the compiler directives shall be placed into the body *************** File: gfortran.info, Node: Non-Fortran *** 4036,4066 **** * _gfortran_set_fpe:: Set when a Floating Point Exception should be raised * _gfortran_set_max_subrecord_length:: Set subrecord length ! Even if you are doing mixed-language programming, it is very likely that ! you do not need to know or use the information in this section. Since ! it is about the internal structure of GNU Fortran, it may also change in ! GCC minor releases. ! When you compile a 'PROGRAM' with GNU Fortran, a function with the ! name 'main' (in the symbol table of the object file) is generated, which ! initializes the libgfortran library and then calls the actual program ! which uses the name 'MAIN__', for historic reasons. If you link GNU ! Fortran compiled procedures to, e.g., a C or C++ program or to a Fortran ! program compiled by a different compiler, the libgfortran library is not ! initialized and thus a few intrinsic procedures do not work properly, ! e.g. those for obtaining the command-line arguments. ! Therefore, if your 'PROGRAM' is not compiled with GNU Fortran and the ! GNU Fortran compiled procedures require intrinsics relying on the library initialization, you need to initialize the library yourself. ! Using the default options, gfortran calls '_gfortran_set_args' and ! '_gfortran_set_options'. The initialization of the former is needed if ! the called procedures access the command line (and for backtracing); the ! latter sets some flags based on the standard chosen or to enable backtracing. In typical programs, it is not necessary to call any initialization function. ! If your 'PROGRAM' is compiled with GNU Fortran, you shall not call any of the following functions. The libgfortran initialization functions are shown in C syntax but using C bindings they are also accessible from Fortran. --- 4071,4101 ---- * _gfortran_set_fpe:: Set when a Floating Point Exception should be raised * _gfortran_set_max_subrecord_length:: Set subrecord length ! Even if you are doing mixed-language programming, it is very likely ! that you do not need to know or use the information in this section. ! Since it is about the internal structure of GNU Fortran, it may also ! change in GCC minor releases. ! When you compile a `PROGRAM' with GNU Fortran, a function with the ! name `main' (in the symbol table of the object file) is generated, ! which initializes the libgfortran library and then calls the actual ! program which uses the name `MAIN__', for historic reasons. If you ! link GNU Fortran compiled procedures to, e.g., a C or C++ program or to ! a Fortran program compiled by a different compiler, the libgfortran ! library is not initialized and thus a few intrinsic procedures do not ! work properly, e.g. those for obtaining the command-line arguments. ! Therefore, if your `PROGRAM' is not compiled with GNU Fortran and ! the GNU Fortran compiled procedures require intrinsics relying on the library initialization, you need to initialize the library yourself. ! Using the default options, gfortran calls `_gfortran_set_args' and ! `_gfortran_set_options'. The initialization of the former is needed if ! the called procedures access the command line (and for backtracing); ! the latter sets some flags based on the standard chosen or to enable backtracing. In typical programs, it is not necessary to call any initialization function. ! If your `PROGRAM' is compiled with GNU Fortran, you shall not call any of the following functions. The libgfortran initialization functions are shown in C syntax but using C bindings they are also accessible from Fortran. *************** accessible from Fortran. *** 4068,4089 ****  File: gfortran.info, Node: _gfortran_set_args, Next: _gfortran_set_options, Up: Non-Fortran Main Program ! 7.3.1 '_gfortran_set_args' -- Save command-line arguments --------------------------------------------------------- _Description_: ! '_gfortran_set_args' saves the command-line arguments; this ! initialization is required if any of the command-line intrinsics is ! called. Additionally, it shall be called if backtracing is enabled ! (see '_gfortran_set_options'). _Syntax_: ! 'void _gfortran_set_args (int argc, char *argv[])' _Arguments_: ! ARGC number of command line argument strings ! ARGV the command-line argument strings; argv[0] is ! the pathname of the executable itself. _Example_: int main (int argc, char *argv[]) --- 4103,4124 ----  File: gfortran.info, Node: _gfortran_set_args, Next: _gfortran_set_options, Up: Non-Fortran Main Program ! 7.3.1 `_gfortran_set_args' -- Save command-line arguments --------------------------------------------------------- _Description_: ! `_gfortran_set_args' saves the command-line arguments; this ! initialization is required if any of the command-line intrinsics ! is called. Additionally, it shall be called if backtracing is ! enabled (see `_gfortran_set_options'). _Syntax_: ! `void _gfortran_set_args (int argc, char *argv[])' _Arguments_: ! ARGC number of command line argument strings ! ARGV the command-line argument strings; argv[0] is ! the pathname of the executable itself. _Example_: int main (int argc, char *argv[]) *************** _Example_: *** 4096,4163 ****  File: gfortran.info, Node: _gfortran_set_options, Next: _gfortran_set_convert, Prev: _gfortran_set_args, Up: Non-Fortran Main Program ! 7.3.2 '_gfortran_set_options' -- Set library option flags --------------------------------------------------------- _Description_: ! '_gfortran_set_options' sets several flags related to the Fortran standard to be used, whether backtracing should be enabled and whether range checks should be performed. The syntax allows for ! upward compatibility since the number of passed flags is specified; ! for non-passed flags, the default value is used. See also *note ! Code Gen Options::. Please note that not all flags are actually ! used. _Syntax_: ! 'void _gfortran_set_options (int num, int options[])' _Arguments_: ! NUM number of options passed ! ARGV The list of flag values _option flag list_: ! OPTION[0] Allowed standard; can give run-time errors if ! e.g. an input-output edit descriptor is invalid ! in a given standard. Possible values are ! (bitwise or-ed) 'GFC_STD_F77' (1), ! 'GFC_STD_F95_OBS' (2), 'GFC_STD_F95_DEL' (4), ! 'GFC_STD_F95' (8), 'GFC_STD_F2003' (16), ! 'GFC_STD_GNU' (32), 'GFC_STD_LEGACY' (64), ! 'GFC_STD_F2008' (128), 'GFC_STD_F2008_OBS' (256) ! and GFC_STD_F2008_TS (512). Default: ! 'GFC_STD_F95_OBS | GFC_STD_F95_DEL | GFC_STD_F95 ! | GFC_STD_F2003 | GFC_STD_F2008 | ! GFC_STD_F2008_TS | GFC_STD_F2008_OBS | ! GFC_STD_F77 | GFC_STD_GNU | GFC_STD_LEGACY'. ! OPTION[1] Standard-warning flag; prints a warning to ! standard error. Default: 'GFC_STD_F95_DEL | ! GFC_STD_LEGACY'. ! OPTION[2] If non zero, enable pedantic checking. Default: ! off. ! OPTION[3] Unused. ! OPTION[4] If non zero, enable backtracing on run-time ! errors. Default: off. (Default in the ! compiler: on.) Note: Installs a signal handler ! and requires command-line initialization using ! '_gfortran_set_args'. ! OPTION[5] If non zero, supports signed zeros. Default: ! enabled. ! OPTION[6] Enables run-time checking. Possible values are ! (bitwise or-ed): GFC_RTCHECK_BOUNDS (1), ! GFC_RTCHECK_ARRAY_TEMPS (2), ! GFC_RTCHECK_RECURSION (4), GFC_RTCHECK_DO (16), ! GFC_RTCHECK_POINTER (32). Default: disabled. ! OPTION[7] Unused. ! OPTION[8] Show a warning when invoking 'STOP' and 'ERROR ! STOP' if a floating-point exception occurred. ! Possible values are (bitwise or-ed) ! 'GFC_FPE_INVALID' (1), 'GFC_FPE_DENORMAL' (2), ! 'GFC_FPE_ZERO' (4), 'GFC_FPE_OVERFLOW' (8), ! 'GFC_FPE_UNDERFLOW' (16), 'GFC_FPE_INEXACT' ! (32). Default: None (0). (Default in the ! compiler: 'GFC_FPE_INVALID | GFC_FPE_DENORMAL | ! GFC_FPE_ZERO | GFC_FPE_OVERFLOW | ! GFC_FPE_UNDERFLOW'.) _Example_: /* Use gfortran 4.9 default options. */ --- 4131,4199 ----  File: gfortran.info, Node: _gfortran_set_options, Next: _gfortran_set_convert, Prev: _gfortran_set_args, Up: Non-Fortran Main Program ! 7.3.2 `_gfortran_set_options' -- Set library option flags --------------------------------------------------------- _Description_: ! `_gfortran_set_options' sets several flags related to the Fortran standard to be used, whether backtracing should be enabled and whether range checks should be performed. The syntax allows for ! upward compatibility since the number of passed flags is ! specified; for non-passed flags, the default value is used. See ! also *note Code Gen Options::. Please note that not all flags are ! actually used. _Syntax_: ! `void _gfortran_set_options (int num, int options[])' _Arguments_: ! NUM number of options passed ! ARGV The list of flag values _option flag list_: ! OPTION[0] Allowed standard; can give run-time errors if ! e.g. an input-output edit descriptor is ! invalid in a given standard. Possible values ! are (bitwise or-ed) `GFC_STD_F77' (1), ! `GFC_STD_F95_OBS' (2), `GFC_STD_F95_DEL' (4), ! `GFC_STD_F95' (8), `GFC_STD_F2003' (16), ! `GFC_STD_GNU' (32), `GFC_STD_LEGACY' (64), ! `GFC_STD_F2008' (128), `GFC_STD_F2008_OBS' ! (256) and GFC_STD_F2008_TS (512). Default: ! `GFC_STD_F95_OBS | GFC_STD_F95_DEL | ! GFC_STD_F95 | GFC_STD_F2003 | GFC_STD_F2008 | ! GFC_STD_F2008_TS | GFC_STD_F2008_OBS | ! GFC_STD_F77 | GFC_STD_GNU | GFC_STD_LEGACY'. ! OPTION[1] Standard-warning flag; prints a warning to ! standard error. Default: `GFC_STD_F95_DEL | ! GFC_STD_LEGACY'. ! OPTION[2] If non zero, enable pedantic checking. ! Default: off. ! OPTION[3] Unused. ! OPTION[4] If non zero, enable backtracing on run-time ! errors. Default: off. (Default in the ! compiler: on.) Note: Installs a signal ! handler and requires command-line ! initialization using `_gfortran_set_args'. ! OPTION[5] If non zero, supports signed zeros. Default: ! enabled. ! OPTION[6] Enables run-time checking. Possible values ! are (bitwise or-ed): GFC_RTCHECK_BOUNDS (1), ! GFC_RTCHECK_ARRAY_TEMPS (2), ! GFC_RTCHECK_RECURSION (4), GFC_RTCHECK_DO ! (16), GFC_RTCHECK_POINTER (32). Default: ! disabled. ! OPTION[7] Unused. ! OPTION[8] Show a warning when invoking `STOP' and `ERROR ! STOP' if a floating-point exception occurred. ! Possible values are (bitwise or-ed) ! `GFC_FPE_INVALID' (1), `GFC_FPE_DENORMAL' (2), ! `GFC_FPE_ZERO' (4), `GFC_FPE_OVERFLOW' (8), ! `GFC_FPE_UNDERFLOW' (16), `GFC_FPE_INEXACT' ! (32). Default: None (0). (Default in the ! compiler: `GFC_FPE_INVALID | GFC_FPE_DENORMAL | ! GFC_FPE_ZERO | GFC_FPE_OVERFLOW | ! GFC_FPE_UNDERFLOW'.) _Example_: /* Use gfortran 4.9 default options. */ *************** _Example_: *** 4167,4187 ****  File: gfortran.info, Node: _gfortran_set_convert, Next: _gfortran_set_record_marker, Prev: _gfortran_set_options, Up: Non-Fortran Main Program ! 7.3.3 '_gfortran_set_convert' -- Set endian conversion ------------------------------------------------------ _Description_: ! '_gfortran_set_convert' set the representation of data for unformatted files. _Syntax_: ! 'void _gfortran_set_convert (int conv)' _Arguments_: ! CONV Endian conversion, possible values: ! GFC_CONVERT_NATIVE (0, default), ! GFC_CONVERT_SWAP (1), GFC_CONVERT_BIG (2), ! GFC_CONVERT_LITTLE (3). _Example_: int main (int argc, char *argv[]) --- 4203,4223 ----  File: gfortran.info, Node: _gfortran_set_convert, Next: _gfortran_set_record_marker, Prev: _gfortran_set_options, Up: Non-Fortran Main Program ! 7.3.3 `_gfortran_set_convert' -- Set endian conversion ------------------------------------------------------ _Description_: ! `_gfortran_set_convert' set the representation of data for unformatted files. _Syntax_: ! `void _gfortran_set_convert (int conv)' _Arguments_: ! CONV Endian conversion, possible values: ! GFC_CONVERT_NATIVE (0, default), ! GFC_CONVERT_SWAP (1), GFC_CONVERT_BIG (2), ! GFC_CONVERT_LITTLE (3). _Example_: int main (int argc, char *argv[]) *************** _Example_: *** 4195,4213 ****  File: gfortran.info, Node: _gfortran_set_record_marker, Next: _gfortran_set_fpe, Prev: _gfortran_set_convert, Up: Non-Fortran Main Program ! 7.3.4 '_gfortran_set_record_marker' -- Set length of record markers ------------------------------------------------------------------- _Description_: ! '_gfortran_set_record_marker' sets the length of record markers for ! unformatted files. _Syntax_: ! 'void _gfortran_set_record_marker (int val)' _Arguments_: ! VAL Length of the record marker; valid values are 4 ! and 8. Default is 4. _Example_: int main (int argc, char *argv[]) --- 4231,4249 ----  File: gfortran.info, Node: _gfortran_set_record_marker, Next: _gfortran_set_fpe, Prev: _gfortran_set_convert, Up: Non-Fortran Main Program ! 7.3.4 `_gfortran_set_record_marker' -- Set length of record markers ------------------------------------------------------------------- _Description_: ! `_gfortran_set_record_marker' sets the length of record markers ! for unformatted files. _Syntax_: ! `void _gfortran_set_record_marker (int val)' _Arguments_: ! VAL Length of the record marker; valid values are ! 4 and 8. Default is 4. _Example_: int main (int argc, char *argv[]) *************** _Example_: *** 4221,4244 ****  File: gfortran.info, Node: _gfortran_set_fpe, Next: _gfortran_set_max_subrecord_length, Prev: _gfortran_set_record_marker, Up: Non-Fortran Main Program ! 7.3.5 '_gfortran_set_fpe' -- Enable floating point exception traps ------------------------------------------------------------------ _Description_: ! '_gfortran_set_fpe' enables floating point exception traps for the specified exceptions. On most systems, this will result in a SIGFPE signal being sent and the program being aborted. _Syntax_: ! 'void _gfortran_set_fpe (int val)' _Arguments_: ! OPTION[0] IEEE exceptions. Possible values are (bitwise ! or-ed) zero (0, default) no trapping, ! 'GFC_FPE_INVALID' (1), 'GFC_FPE_DENORMAL' (2), ! 'GFC_FPE_ZERO' (4), 'GFC_FPE_OVERFLOW' (8), ! 'GFC_FPE_UNDERFLOW' (16), and 'GFC_FPE_INEXACT' ! (32). _Example_: int main (int argc, char *argv[]) --- 4257,4280 ----  File: gfortran.info, Node: _gfortran_set_fpe, Next: _gfortran_set_max_subrecord_length, Prev: _gfortran_set_record_marker, Up: Non-Fortran Main Program ! 7.3.5 `_gfortran_set_fpe' -- Enable floating point exception traps ------------------------------------------------------------------ _Description_: ! `_gfortran_set_fpe' enables floating point exception traps for the specified exceptions. On most systems, this will result in a SIGFPE signal being sent and the program being aborted. _Syntax_: ! `void _gfortran_set_fpe (int val)' _Arguments_: ! OPTION[0] IEEE exceptions. Possible values are (bitwise ! or-ed) zero (0, default) no trapping, ! `GFC_FPE_INVALID' (1), `GFC_FPE_DENORMAL' (2), ! `GFC_FPE_ZERO' (4), `GFC_FPE_OVERFLOW' (8), ! `GFC_FPE_UNDERFLOW' (16), and ! `GFC_FPE_INEXACT' (32). _Example_: int main (int argc, char *argv[]) *************** _Example_: *** 4253,4273 ****  File: gfortran.info, Node: _gfortran_set_max_subrecord_length, Prev: _gfortran_set_fpe, Up: Non-Fortran Main Program ! 7.3.6 '_gfortran_set_max_subrecord_length' -- Set subrecord length ------------------------------------------------------------------ _Description_: ! '_gfortran_set_max_subrecord_length' set the maximum length for a subrecord. This option only makes sense for testing and debugging of unformatted I/O. _Syntax_: ! 'void _gfortran_set_max_subrecord_length (int val)' _Arguments_: ! VAL the maximum length for a subrecord; the maximum ! permitted value is 2147483639, which is also the ! default. _Example_: int main (int argc, char *argv[]) --- 4289,4309 ----  File: gfortran.info, Node: _gfortran_set_max_subrecord_length, Prev: _gfortran_set_fpe, Up: Non-Fortran Main Program ! 7.3.6 `_gfortran_set_max_subrecord_length' -- Set subrecord length ------------------------------------------------------------------ _Description_: ! `_gfortran_set_max_subrecord_length' set the maximum length for a subrecord. This option only makes sense for testing and debugging of unformatted I/O. _Syntax_: ! `void _gfortran_set_max_subrecord_length (int val)' _Arguments_: ! VAL the maximum length for a subrecord; the ! maximum permitted value is 2147483639, which ! is also the default. _Example_: int main (int argc, char *argv[]) *************** File: gfortran.info, Node: Naming conve *** 4303,4329 **** ------------------------ According the Fortran standard, valid Fortran names consist of a letter ! between 'A' to 'Z', 'a' to 'z', digits '0', '1' to '9' and underscores ! ('_') with the restriction that names may only start with a letter. As ! vendor extension, the dollar sign ('$') is additionally permitted with ! the option '-fdollar-ok', but not as first character and only if the target system supports it. By default, the procedure name is the lower-cased Fortran name with ! an appended underscore ('_'); using '-fno-underscoring' no underscore is ! appended while '-fsecond-underscore' appends two underscores. Depending ! on the target system and the calling convention, the procedure might be ! additionally dressed; for instance, on 32bit Windows with 'stdcall', an ! at-sign '@' followed by an integer number is appended. For the changing ! the calling convention, see *note GNU Fortran Compiler Directives::. ! For common blocks, the same convention is used, i.e. by default an underscore is appended to the lower-cased Fortran name. Blank commons ! have the name '__BLNK__'. For procedures and variables declared in the specification space of a ! module, the name is formed by '__', followed by the lower-cased module ! name, '_MOD_', and the lower-cased Fortran name. Note that no underscore is appended.  --- 4339,4366 ---- ------------------------ According the Fortran standard, valid Fortran names consist of a letter ! between `A' to `Z', `a' to `z', digits `0', `1' to `9' and underscores ! (`_') with the restriction that names may only start with a letter. As ! vendor extension, the dollar sign (`$') is additionally permitted with ! the option `-fdollar-ok', but not as first character and only if the target system supports it. By default, the procedure name is the lower-cased Fortran name with ! an appended underscore (`_'); using `-fno-underscoring' no underscore ! is appended while `-fsecond-underscore' appends two underscores. ! Depending on the target system and the calling convention, the ! procedure might be additionally dressed; for instance, on 32bit Windows ! with `stdcall', an at-sign `@' followed by an integer number is ! appended. For the changing the calling convention, see *note GNU ! Fortran Compiler Directives::. ! For common blocks, the same convention is used, i.e. by default an underscore is appended to the lower-cased Fortran name. Blank commons ! have the name `__BLNK__'. For procedures and variables declared in the specification space of a ! module, the name is formed by `__', followed by the lower-cased module ! name, `_MOD_', and the lower-cased Fortran name. Note that no underscore is appended.  *************** File: gfortran.info, Node: Argument pas *** 4332,4412 **** 7.4.2 Argument passing conventions ---------------------------------- ! Subroutines do not return a value (matching C99's 'void') while functions either return a value as specified in the platform ABI or the result variable is passed as hidden argument to the function and no result is returned. A hidden result variable is used when the result ! variable is an array or of type 'CHARACTER'. Arguments are passed according to the platform ABI. In particular, complex arguments might not be compatible to a struct with two real ! components for the real and imaginary part. The argument passing ! matches the one of C99's '_Complex'. Functions with scalar complex result variables return their value and do not use a by-reference ! argument. Note that with the '-ff2c' option, the argument passing is ! modified and no longer completely matches the platform ABI. Some other ! Fortran compilers use 'f2c' semantic by default; this might cause problems with interoperablility. ! GNU Fortran passes most arguments by reference, i.e. by passing a pointer to the data. Note that the compiler might use a temporary variable into which the actual argument has been copied, if required semantically (copy-in/copy-out). ! For arguments with 'ALLOCATABLE' and 'POINTER' attribute (including procedure pointers), a pointer to the pointer is passed such that the pointer address can be modified in the procedure. ! For dummy arguments with the 'VALUE' attribute: Scalar arguments of ! the type 'INTEGER', 'LOGICAL', 'REAL' and 'COMPLEX' are passed by value ! according to the platform ABI. (As vendor extension and not recommended, ! using '%VAL()' in the call to a procedure has the same effect.) For ! 'TYPE(C_PTR)' and procedure pointers, the pointer itself is passed such ! that it can be modified without affecting the caller. ! For Boolean ('LOGICAL') arguments, please note that GCC expects only ! the integer value 0 and 1. If a GNU Fortran 'LOGICAL' variable contains ! another integer value, the result is undefined. As some other Fortran ! compilers use -1 for '.TRUE.', extra care has to be taken - such as ! passing the value as 'INTEGER'. (The same value restriction also ! applies to other front ends of GCC, e.g. to GCC's C99 compiler for ! '_Bool' or GCC's Ada compiler for 'Boolean'.) ! For arguments of 'CHARACTER' type, the character length is passed as hidden argument. For deferred-length strings, the value is passed by reference, otherwise by value. The character length has the type ! 'INTEGER(kind=4)'. Note with C binding, 'CHARACTER(len=1)' result variables are returned according to the platform ABI and no hidden ! length argument is used for dummy arguments; with 'VALUE', those variables are passed by value. ! For 'OPTIONAL' dummy arguments, an absent argument is denoted by a ! NULL pointer, except for scalar dummy arguments of type 'INTEGER', ! 'LOGICAL', 'REAL' and 'COMPLEX' which have the 'VALUE' attribute. For ! those, a hidden Boolean argument ('logical(kind=C_bool),value') is used to indicate whether the argument is present. Arguments which are assumed-shape, assumed-rank or deferred-rank ! arrays or, with '-fcoarray=lib', allocatable scalar coarrays use an array descriptor. All other arrays pass the address of the first ! element of the array. With '-fcoarray=lib', the token and the offset belonging to nonallocatable coarrays dummy arguments are passed as hidden argument along the character length hidden arguments. The token is an oparque pointer identifying the coarray and the offset is a ! passed-by-value integer of kind 'C_PTRDIFF_T', denoting the byte offset between the base address of the coarray and the passed scalar or first element of the passed array. The arguments are passed in the following order * Result variable, when the function result is passed by reference * Character length of the function result, if it is a of type ! 'CHARACTER' and no C binding is used * The arguments in the order in which they appear in the Fortran declaration * The the present status for optional arguments with value attribute, which are internally passed by value * The character length and/or coarray token and offset for the first ! argument which is a 'CHARACTER' or a nonallocatable coarray dummy argument, followed by the hidden arguments of the next dummy argument of such a type --- 4369,4453 ---- 7.4.2 Argument passing conventions ---------------------------------- ! Subroutines do not return a value (matching C99's `void') while functions either return a value as specified in the platform ABI or the result variable is passed as hidden argument to the function and no result is returned. A hidden result variable is used when the result ! variable is an array or of type `CHARACTER'. Arguments are passed according to the platform ABI. In particular, complex arguments might not be compatible to a struct with two real ! components for the real and imaginary part. The argument passing ! matches the one of C99's `_Complex'. Functions with scalar complex result variables return their value and do not use a by-reference ! argument. Note that with the `-ff2c' option, the argument passing is ! modified and no longer completely matches the platform ABI. Some other ! Fortran compilers use `f2c' semantic by default; this might cause problems with interoperablility. ! GNU Fortran passes most arguments by reference, i.e. by passing a pointer to the data. Note that the compiler might use a temporary variable into which the actual argument has been copied, if required semantically (copy-in/copy-out). ! For arguments with `ALLOCATABLE' and `POINTER' attribute (including procedure pointers), a pointer to the pointer is passed such that the pointer address can be modified in the procedure. ! For dummy arguments with the `VALUE' attribute: Scalar arguments of ! the type `INTEGER', `LOGICAL', `REAL' and `COMPLEX' are passed by value ! according to the platform ABI. (As vendor extension and not ! recommended, using `%VAL()' in the call to a procedure has the same ! effect.) For `TYPE(C_PTR)' and procedure pointers, the pointer itself ! is passed such that it can be modified without affecting the caller. ! For Boolean (`LOGICAL') arguments, please note that GCC expects only ! the integer value 0 and 1. If a GNU Fortran `LOGICAL' variable ! contains another integer value, the result is undefined. As some other ! Fortran compilers use -1 for `.TRUE.', extra care has to be taken - ! such as passing the value as `INTEGER'. (The same value restriction ! also applies to other front ends of GCC, e.g. to GCC's C99 compiler for ! `_Bool' or GCC's Ada compiler for `Boolean'.) ! For arguments of `CHARACTER' type, the character length is passed as hidden argument. For deferred-length strings, the value is passed by reference, otherwise by value. The character length has the type ! `INTEGER(kind=4)'. Note with C binding, `CHARACTER(len=1)' result variables are returned according to the platform ABI and no hidden ! length argument is used for dummy arguments; with `VALUE', those variables are passed by value. ! For `OPTIONAL' dummy arguments, an absent argument is denoted by a ! NULL pointer, except for scalar dummy arguments of type `INTEGER', ! `LOGICAL', `REAL' and `COMPLEX' which have the `VALUE' attribute. For ! those, a hidden Boolean argument (`logical(kind=C_bool),value') is used to indicate whether the argument is present. Arguments which are assumed-shape, assumed-rank or deferred-rank ! arrays or, with `-fcoarray=lib', allocatable scalar coarrays use an array descriptor. All other arrays pass the address of the first ! element of the array. With `-fcoarray=lib', the token and the offset belonging to nonallocatable coarrays dummy arguments are passed as hidden argument along the character length hidden arguments. The token is an oparque pointer identifying the coarray and the offset is a ! passed-by-value integer of kind `C_PTRDIFF_T', denoting the byte offset between the base address of the coarray and the passed scalar or first element of the passed array. The arguments are passed in the following order * Result variable, when the function result is passed by reference + * Character length of the function result, if it is a of type ! `CHARACTER' and no C binding is used ! * The arguments in the order in which they appear in the Fortran declaration + * The the present status for optional arguments with value attribute, which are internally passed by value + * The character length and/or coarray token and offset for the first ! argument which is a `CHARACTER' or a nonallocatable coarray dummy argument, followed by the hidden arguments of the next dummy argument of such a type *************** File: gfortran.info, Node: Type and enu *** 4435,4450 ****  File: gfortran.info, Node: caf_token_t, Next: caf_register_t, Up: Type and enum ABI Documentation ! 8.1.1 'caf_token_t' ------------------- ! Typedef of type 'void *' on the compiler side. Can be any data type on the library side.  File: gfortran.info, Node: caf_register_t, Prev: caf_token_t, Up: Type and enum ABI Documentation ! 8.1.2 'caf_register_t' ---------------------- Indicates which kind of coarray variable should be registered. --- 4476,4491 ----  File: gfortran.info, Node: caf_token_t, Next: caf_register_t, Up: Type and enum ABI Documentation ! 8.1.1 `caf_token_t' ------------------- ! Typedef of type `void *' on the compiler side. Can be any data type on the library side.  File: gfortran.info, Node: caf_register_t, Prev: caf_token_t, Up: Type and enum ABI Documentation ! 8.1.2 `caf_register_t' ---------------------- Indicates which kind of coarray variable should be registered. *************** File: gfortran.info, Node: Function ABI *** 4500,4524 ****  File: gfortran.info, Node: _gfortran_caf_init, Next: _gfortran_caf_finish, Up: Function ABI Documentation ! 8.2.1 '_gfortran_caf_init' -- Initialiation function ---------------------------------------------------- _Description_: This function is called at startup of the program before the Fortran main program, if the latter has been compiled with ! '-fcoarray=lib'. It takes as arguments the command-line arguments ! of the program. It is permitted to pass to 'NULL' pointers as ! argument; if non-'NULL', the library is permitted to modify the arguments. _Syntax_: ! 'void _gfortran_caf_init (int *argc, char ***argv)' _Arguments_: ! ARGC intent(inout) An integer pointer with the number ! of arguments passed to the program or 'NULL'. ! ARGV intent(inout) A pointer to an array of strings ! with the command-line arguments or 'NULL'. _NOTES_ The function is modelled after the initialization function of the --- 4541,4566 ----  File: gfortran.info, Node: _gfortran_caf_init, Next: _gfortran_caf_finish, Up: Function ABI Documentation ! 8.2.1 `_gfortran_caf_init' -- Initialiation function ---------------------------------------------------- _Description_: This function is called at startup of the program before the Fortran main program, if the latter has been compiled with ! `-fcoarray=lib'. It takes as arguments the command-line arguments ! of the program. It is permitted to pass to `NULL' pointers as ! argument; if non-`NULL', the library is permitted to modify the arguments. _Syntax_: ! `void _gfortran_caf_init (int *argc, char ***argv)' _Arguments_: ! ARGC intent(inout) An integer pointer with the ! number of arguments passed to the program or ! `NULL'. ! ARGV intent(inout) A pointer to an array of strings ! with the command-line arguments or `NULL'. _NOTES_ The function is modelled after the initialization function of the *************** _NOTES_ *** 4532,4671 ****  File: gfortran.info, Node: _gfortran_caf_finish, Next: _gfortran_caf_this_image, Prev: _gfortran_caf_init, Up: Function ABI Documentation ! 8.2.2 '_gfortran_caf_finish' -- Finalization function ----------------------------------------------------- _Description_: This function is called at the end of the Fortran main program, if ! it has been compiled with the '-fcoarray=lib' option. _Syntax_: ! 'void _gfortran_caf_finish (void)' _NOTES_ ! For non-Fortran programs, it is recommended to call the function at ! the end of the main program. To ensure that the shutdown is also ! performed for programs where this function is not explicitly ! invoked, for instance non-Fortran programs or calls to the system's ! exit() function, the library can use a destructor function. Note ! that programs can also be terminated using the STOP and ERROR STOP ! statements; those use different library calls.  File: gfortran.info, Node: _gfortran_caf_this_image, Next: _gfortran_caf_num_images, Prev: _gfortran_caf_finish, Up: Function ABI Documentation ! 8.2.3 '_gfortran_caf_this_image' -- Querying the image number ------------------------------------------------------------- _Description_: ! This function returns the current image number, which is a positive ! number. _Syntax_: ! 'int _gfortran_caf_this_image (int distance)' _Arguments_: ! DISTANCE As specified for the 'this_image' intrinsic in ! TS18508. Shall be a nonnegative number. _NOTES_ ! If the Fortran intrinsic 'this_image' is invoked without an argument, which is the only permitted form in Fortran 2008, GCC ! passes '0' as first argument.  File: gfortran.info, Node: _gfortran_caf_num_images, Next: _gfortran_caf_register, Prev: _gfortran_caf_this_image, Up: Function ABI Documentation ! 8.2.4 '_gfortran_caf_num_images' -- Querying the maximal number of images ------------------------------------------------------------------------- _Description_: This function returns the number of images in the current team, if DISTANCE is 0 or the number of images in the parent team at the ! specified distance. If failed is -1, the function returns the number of all images at the specified distance; if it is 0, the ! function returns the number of nonfailed images, and if it is 1, it ! returns the number of failed images. _Syntax_: ! 'int _gfortran_caf_num_images(int distance, int failed)' _Arguments_: ! DISTANCE the distance from this image to the ancestor. ! Shall be positive. ! FAILED shall be -1, 0, or 1 _NOTES_ ! This function follows TS18508. If the num_image intrinsic has no ! arguments, the the compiler passes 'distance=0' and 'failed=-1' to the function.  File: gfortran.info, Node: _gfortran_caf_register, Next: _gfortran_caf_deregister, Prev: _gfortran_caf_num_images, Up: Function ABI Documentation ! 8.2.5 '_gfortran_caf_register' -- Registering coarrays ------------------------------------------------------ _Description_: Allocates memory for a coarray and creates a token to identify the ! coarray. The function is called for both coarrays with 'SAVE' ! attribute and using an explicit 'ALLOCATE' statement. If an error ! occurs and STAT is a 'NULL' pointer, the function shall abort with printing an error message and starting the error termination. If no error occurs and STAT is present, it shall be set to zero. ! Otherwise, it shall be set to a positive value and, if not-'NULL', ! ERRMSG shall be set to a string describing the failure. The function shall return a pointer to the requested memory for the ! local image as a call to 'malloc' would do. ! For 'CAF_REGTYPE_COARRAY_STATIC' and 'CAF_REGTYPE_COARRAY_ALLOC', the passed size is the byte size requested. For ! 'CAF_REGTYPE_LOCK_STATIC', 'CAF_REGTYPE_LOCK_ALLOC' and ! 'CAF_REGTYPE_CRITICAL' it is the array size or one for a scalar. _Syntax_: ! 'void *caf_register (size_t size, caf_register_t type, caf_token_t *token, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! SIZE For normal coarrays, the byte size of the ! coarray to be allocated; for lock types and ! event types, the number of elements. ! TYPE one of the caf_register_t types. ! TOKEN intent(out) An opaque pointer identifying the ! coarray. ! STAT intent(out) For allocatable coarrays, stores the ! STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ Nonalloatable coarrays have to be registered prior use from remote images. In order to guarantee this, they have to be registered ! before the main program. This can be achieved by creating ! constructor functions. That is what GCC does such that also nonallocatable coarrays the memory is allocated and no static memory is used. The token permits to identify the coarray; to the ! processor, the token is a nonaliasing pointer. The library can, for instance, store the base address of the coarray in the token, some handle or a more complicated struct. For normal coarrays, the returned pointer is used for accesses on ! the local image. For lock types, the value shall only used for ! checking the allocation status. Note that for critical blocks, the locking is only required on one image; in the locking statement, the processor shall always pass always an image index of one for ! critical-block lock variables ('CAF_REGTYPE_CRITICAL'). For lock types and critical-block variables, the initial value shall be unlocked (or, respecitively, not in critical section) such as the ! value false; for event types, the initial state should be no event, ! e.g. zero.  File: gfortran.info, Node: _gfortran_caf_deregister, Next: _gfortran_caf_send, Prev: _gfortran_caf_register, Up: Function ABI Documentation ! 8.2.6 '_gfortran_caf_deregister' -- Deregistering coarrays ---------------------------------------------------------- _Description_: --- 4574,4713 ----  File: gfortran.info, Node: _gfortran_caf_finish, Next: _gfortran_caf_this_image, Prev: _gfortran_caf_init, Up: Function ABI Documentation ! 8.2.2 `_gfortran_caf_finish' -- Finalization function ----------------------------------------------------- _Description_: This function is called at the end of the Fortran main program, if ! it has been compiled with the `-fcoarray=lib' option. _Syntax_: ! `void _gfortran_caf_finish (void)' _NOTES_ ! For non-Fortran programs, it is recommended to call the function ! at the end of the main program. To ensure that the shutdown is ! also performed for programs where this function is not explicitly ! invoked, for instance non-Fortran programs or calls to the ! system's exit() function, the library can use a destructor ! function. Note that programs can also be terminated using the ! STOP and ERROR STOP statements; those use different library calls.  File: gfortran.info, Node: _gfortran_caf_this_image, Next: _gfortran_caf_num_images, Prev: _gfortran_caf_finish, Up: Function ABI Documentation ! 8.2.3 `_gfortran_caf_this_image' -- Querying the image number ------------------------------------------------------------- _Description_: ! This function returns the current image number, which is a ! positive number. _Syntax_: ! `int _gfortran_caf_this_image (int distance)' _Arguments_: ! DISTANCE As specified for the `this_image' intrinsic in ! TS18508. Shall be a nonnegative number. _NOTES_ ! If the Fortran intrinsic `this_image' is invoked without an argument, which is the only permitted form in Fortran 2008, GCC ! passes `0' as first argument.  File: gfortran.info, Node: _gfortran_caf_num_images, Next: _gfortran_caf_register, Prev: _gfortran_caf_this_image, Up: Function ABI Documentation ! 8.2.4 `_gfortran_caf_num_images' -- Querying the maximal number of images ------------------------------------------------------------------------- _Description_: This function returns the number of images in the current team, if DISTANCE is 0 or the number of images in the parent team at the ! specified distance. If failed is -1, the function returns the number of all images at the specified distance; if it is 0, the ! function returns the number of nonfailed images, and if it is 1, ! it returns the number of failed images. _Syntax_: ! `int _gfortran_caf_num_images(int distance, int failed)' _Arguments_: ! DISTANCE the distance from this image to the ancestor. ! Shall be positive. ! FAILED shall be -1, 0, or 1 _NOTES_ ! This function follows TS18508. If the num_image intrinsic has no ! arguments, the the compiler passes `distance=0' and `failed=-1' to the function.  File: gfortran.info, Node: _gfortran_caf_register, Next: _gfortran_caf_deregister, Prev: _gfortran_caf_num_images, Up: Function ABI Documentation ! 8.2.5 `_gfortran_caf_register' -- Registering coarrays ------------------------------------------------------ _Description_: Allocates memory for a coarray and creates a token to identify the ! coarray. The function is called for both coarrays with `SAVE' ! attribute and using an explicit `ALLOCATE' statement. If an error ! occurs and STAT is a `NULL' pointer, the function shall abort with printing an error message and starting the error termination. If no error occurs and STAT is present, it shall be set to zero. ! Otherwise, it shall be set to a positive value and, if not-`NULL', ! ERRMSG shall be set to a string describing the failure. The function shall return a pointer to the requested memory for the ! local image as a call to `malloc' would do. ! For `CAF_REGTYPE_COARRAY_STATIC' and `CAF_REGTYPE_COARRAY_ALLOC', the passed size is the byte size requested. For ! `CAF_REGTYPE_LOCK_STATIC', `CAF_REGTYPE_LOCK_ALLOC' and ! `CAF_REGTYPE_CRITICAL' it is the array size or one for a scalar. _Syntax_: ! `void *caf_register (size_t size, caf_register_t type, caf_token_t *token, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! SIZE For normal coarrays, the byte size of the ! coarray to be allocated; for lock types and ! event types, the number of elements. ! TYPE one of the caf_register_t types. ! TOKEN intent(out) An opaque pointer identifying the ! coarray. ! STAT intent(out) For allocatable coarrays, stores ! the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ Nonalloatable coarrays have to be registered prior use from remote images. In order to guarantee this, they have to be registered ! before the main program. This can be achieved by creating ! constructor functions. That is what GCC does such that also nonallocatable coarrays the memory is allocated and no static memory is used. The token permits to identify the coarray; to the ! processor, the token is a nonaliasing pointer. The library can, for instance, store the base address of the coarray in the token, some handle or a more complicated struct. For normal coarrays, the returned pointer is used for accesses on ! the local image. For lock types, the value shall only used for ! checking the allocation status. Note that for critical blocks, the locking is only required on one image; in the locking statement, the processor shall always pass always an image index of one for ! critical-block lock variables (`CAF_REGTYPE_CRITICAL'). For lock types and critical-block variables, the initial value shall be unlocked (or, respecitively, not in critical section) such as the ! value false; for event types, the initial state should be no ! event, e.g. zero.  File: gfortran.info, Node: _gfortran_caf_deregister, Next: _gfortran_caf_send, Prev: _gfortran_caf_register, Up: Function ABI Documentation ! 8.2.6 `_gfortran_caf_deregister' -- Deregistering coarrays ---------------------------------------------------------- _Description_: *************** _Description_: *** 4675,4688 **** STAT variable is not null. _Syntax_: ! 'void caf_deregister (const caf_token_t *token, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ For nonalloatable coarrays this function is never called. If a --- 4717,4730 ---- STAT variable is not null. _Syntax_: ! `void caf_deregister (const caf_token_t *token, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ For nonalloatable coarrays this function is never called. If a *************** _NOTES_ *** 4692,4698 ****  File: gfortran.info, Node: _gfortran_caf_send, Next: _gfortran_caf_get, Prev: _gfortran_caf_deregister, Up: Function ABI Documentation ! 8.2.7 '_gfortran_caf_send' -- Sending data from a local image to a remote image ------------------------------------------------------------------------------- _Description_: --- 4734,4740 ----  File: gfortran.info, Node: _gfortran_caf_send, Next: _gfortran_caf_get, Prev: _gfortran_caf_deregister, Up: Function ABI Documentation ! 8.2.7 `_gfortran_caf_send' -- Sending data from a local image to a remote image ------------------------------------------------------------------------------- _Description_: *************** _Description_: *** 4700,4755 **** local to a remote image identified by the image_index. _Syntax_: ! 'void _gfortran_caf_send (caf_token_t token, size_t offset, int image_index, gfc_descriptor_t *dest, caf_vector_t *dst_vector, gfc_descriptor_t *src, int dst_kind, int src_kind, bool may_require_tmp)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number. ! DEST intent(in) Array descriptor for the remote image ! for the bounds and the size. The base_addr ! shall not be accessed. ! DST_VECTOR intent(int) If not NULL, it contains the vector ! subscript of the destination array; the values ! are relative to the dimension triplet of the ! dest argument. ! SRC intent(in) Array descriptor of the local array ! to be transferred to the remote image ! DST_KIND Kind of the destination argument ! SRC_KIND Kind of the source argument MAY_REQUIRE_TMPThe variable is false it is known at compile ! time that the DEST and SRC either cannot overlap ! or overlap (fully or partially) such that ! walking SRC and DEST in element wise element ! order (honoring the stride value) will not lead ! to wrong results. Otherwise, the value is true. _NOTES_ It is permitted to have image_id equal the current image; the memory of the send-to and the send-from might (partially) overlap ! in that case. The implementation has to take care that it handles ! this case, e.g. using 'memmove' which handles (partially) ! overlapping memory. If MAY_REQUIRE_TMP is true, the library might additionally create a temporary variable, unless additional checks ! show that this is not required (e.g. because walking backward is ! possible or because both arrays are contiguous and 'memmove' takes care of overlap issues). ! Note that the assignment of a scalar to an array is permitted. In ! addition, the library has to handle numeric-type conversion and for ! strings, padding and different character kinds.  File: gfortran.info, Node: _gfortran_caf_get, Next: _gfortran_caf_sendget, Prev: _gfortran_caf_send, Up: Function ABI Documentation ! 8.2.8 '_gfortran_caf_get' -- Getting data from a remote image ------------------------------------------------------------- _Description_: --- 4742,4798 ---- local to a remote image identified by the image_index. _Syntax_: ! `void _gfortran_caf_send (caf_token_t token, size_t offset, int image_index, gfc_descriptor_t *dest, caf_vector_t *dst_vector, gfc_descriptor_t *src, int dst_kind, int src_kind, bool may_require_tmp)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number. ! DEST intent(in) Array descriptor for the remote ! image for the bounds and the size. The ! base_addr shall not be accessed. ! DST_VECTOR intent(int) If not NULL, it contains the ! vector subscript of the destination array; the ! values are relative to the dimension triplet ! of the dest argument. ! SRC intent(in) Array descriptor of the local array ! to be transferred to the remote image ! DST_KIND Kind of the destination argument ! SRC_KIND Kind of the source argument MAY_REQUIRE_TMPThe variable is false it is known at compile ! time that the DEST and SRC either cannot ! overlap or overlap (fully or partially) such ! that walking SRC and DEST in element wise ! element order (honoring the stride value) will ! not lead to wrong results. Otherwise, the ! value is true. _NOTES_ It is permitted to have image_id equal the current image; the memory of the send-to and the send-from might (partially) overlap ! in that case. The implementation has to take care that it handles ! this case, e.g. using `memmove' which handles (partially) ! overlapping memory. If MAY_REQUIRE_TMP is true, the library might additionally create a temporary variable, unless additional checks ! show that this is not required (e.g. because walking backward is ! possible or because both arrays are contiguous and `memmove' takes care of overlap issues). ! Note that the assignment of a scalar to an array is permitted. In ! addition, the library has to handle numeric-type conversion and ! for strings, padding and different character kinds.  File: gfortran.info, Node: _gfortran_caf_get, Next: _gfortran_caf_sendget, Prev: _gfortran_caf_send, Up: Function ABI Documentation ! 8.2.8 `_gfortran_caf_get' -- Getting data from a remote image ------------------------------------------------------------- _Description_: *************** _Description_: *** 4757,4811 **** image identified by the image_index. _Syntax_: ! 'void _gfortran_caf_get_desc (caf_token_t token, size_t offset, int ! image_index, gfc_descriptor_t *src, caf_vector_t *src_vector, gfc_descriptor_t *dest, int src_kind, int dst_kind, bool may_require_tmp)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number. ! DEST intent(in) Array descriptor of the local array ! to be transferred to the remote image ! SRC intent(in) Array descriptor for the remote image ! for the bounds and the size. The base_addr ! shall not be accessed. ! SRC_VECTOR intent(int) If not NULL, it contains the vector ! subscript of the destination array; the values ! are relative to the dimension triplet of the ! dest argument. ! DST_KIND Kind of the destination argument ! SRC_KIND Kind of the source argument MAY_REQUIRE_TMPThe variable is false it is known at compile ! time that the DEST and SRC either cannot overlap ! or overlap (fully or partially) such that ! walking SRC and DEST in element wise element ! order (honoring the stride value) will not lead ! to wrong results. Otherwise, the value is true. _NOTES_ It is permitted to have image_id equal the current image; the memory of the send-to and the send-from might (partially) overlap ! in that case. The implementation has to take care that it handles ! this case, e.g. using 'memmove' which handles (partially) ! overlapping memory. If MAY_REQUIRE_TMP is true, the library might additionally create a temporary variable, unless additional checks ! show that this is not required (e.g. because walking backward is ! possible or because both arrays are contiguous and 'memmove' takes care of overlap issues). ! Note that the library has to handle numeric-type conversion and for ! strings, padding and different character kinds.  File: gfortran.info, Node: _gfortran_caf_sendget, Next: _gfortran_caf_lock, Prev: _gfortran_caf_get, Up: Function ABI Documentation ! 8.2.9 '_gfortran_caf_sendget' -- Sending data between remote images ------------------------------------------------------------------- _Description_: --- 4800,4855 ---- image identified by the image_index. _Syntax_: ! `void _gfortran_caf_get_desc (caf_token_t token, size_t offset, ! int image_index, gfc_descriptor_t *src, caf_vector_t *src_vector, gfc_descriptor_t *dest, int src_kind, int dst_kind, bool may_require_tmp)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number. ! DEST intent(in) Array descriptor of the local array ! to be transferred to the remote image ! SRC intent(in) Array descriptor for the remote ! image for the bounds and the size. The ! base_addr shall not be accessed. ! SRC_VECTOR intent(int) If not NULL, it contains the ! vector subscript of the destination array; the ! values are relative to the dimension triplet ! of the dest argument. ! DST_KIND Kind of the destination argument ! SRC_KIND Kind of the source argument MAY_REQUIRE_TMPThe variable is false it is known at compile ! time that the DEST and SRC either cannot ! overlap or overlap (fully or partially) such ! that walking SRC and DEST in element wise ! element order (honoring the stride value) will ! not lead to wrong results. Otherwise, the ! value is true. _NOTES_ It is permitted to have image_id equal the current image; the memory of the send-to and the send-from might (partially) overlap ! in that case. The implementation has to take care that it handles ! this case, e.g. using `memmove' which handles (partially) ! overlapping memory. If MAY_REQUIRE_TMP is true, the library might additionally create a temporary variable, unless additional checks ! show that this is not required (e.g. because walking backward is ! possible or because both arrays are contiguous and `memmove' takes care of overlap issues). ! Note that the library has to handle numeric-type conversion and ! for strings, padding and different character kinds.  File: gfortran.info, Node: _gfortran_caf_sendget, Next: _gfortran_caf_lock, Prev: _gfortran_caf_get, Up: Function ABI Documentation ! 8.2.9 `_gfortran_caf_sendget' -- Sending data between remote images ------------------------------------------------------------------- _Description_: *************** _Description_: *** 4814,4908 **** identified by the dst_image_index. _Syntax_: ! 'void _gfortran_caf_sendget (caf_token_t dst_token, size_t dst_offset, int dst_image_index, gfc_descriptor_t *dest, ! caf_vector_t *dst_vector, caf_token_t src_token, size_t src_offset, ! int src_image_index, gfc_descriptor_t *src, caf_vector_t ! *src_vector, int dst_kind, int src_kind, bool may_require_tmp)' _Arguments_: ! DST_TOKEN intent(in) An opaque pointer identifying the ! destination coarray. ! DST_OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! destination coarray. ! DST_IMAGE_INDEXThe ID of the destination remote image; must be ! a positive number. ! DEST intent(in) Array descriptor for the destination ! remote image for the bounds and the size. The ! base_addr shall not be accessed. ! DST_VECTOR intent(int) If not NULL, it contains the vector ! subscript of the destination array; the values ! are relative to the dimension triplet of the ! dest argument. ! SRC_TOKEN An opaque pointer identifying the source ! coarray. ! SRC_OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! source coarray. SRC_IMAGE_INDEXThe ID of the source remote image; must be a ! positive number. ! SRC intent(in) Array descriptor of the local array ! to be transferred to the remote image. ! SRC_VECTOR intent(in) Array descriptor of the local array ! to be transferred to the remote image ! DST_KIND Kind of the destination argument ! SRC_KIND Kind of the source argument MAY_REQUIRE_TMPThe variable is false it is known at compile ! time that the DEST and SRC either cannot overlap ! or overlap (fully or partially) such that ! walking SRC and DEST in element wise element ! order (honoring the stride value) will not lead ! to wrong results. Otherwise, the value is true. _NOTES_ It is permitted to have image_ids equal; the memory of the send-to ! and the send-from might (partially) overlap in that case. The implementation has to take care that it handles this case, e.g. ! using 'memmove' which handles (partially) overlapping memory. If MAY_REQUIRE_TMP is true, the library might additionally create a temporary variable, unless additional checks show that this is not ! required (e.g. because walking backward is possible or because ! both arrays are contiguous and 'memmove' takes care of overlap issues). ! Note that the assignment of a scalar to an array is permitted. In ! addition, the library has to handle numeric-type conversion and for ! strings, padding and different character kinds.  File: gfortran.info, Node: _gfortran_caf_lock, Next: _gfortran_caf_unlock, Prev: _gfortran_caf_sendget, Up: Function ABI Documentation ! 8.2.10 '_gfortran_caf_lock' -- Locking a lock variable ------------------------------------------------------ _Description_: Acquire a lock on the given image on a scalar locking variable or ! for the given array element for an array-valued variable. If the ! AQUIRED_LOCK is 'NULL', the function return after having obtained ! the lock. If it is nonnull, the result is is assigned the value true (one) when the lock could be obtained and false (zero) otherwise. Locking a lock variable which has already been locked by the same image is an error. _Syntax_: ! 'void _gfortran_caf_lock (caf_token_t token, size_t index, int image_index, int *aquired_lock, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number. ! AQUIRED_LOCKintent(out) If not NULL, it returns whether lock ! could be obtained ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ This function is also called for critical blocks; for those, the --- 4858,4954 ---- identified by the dst_image_index. _Syntax_: ! `void _gfortran_caf_sendget (caf_token_t dst_token, size_t dst_offset, int dst_image_index, gfc_descriptor_t *dest, ! caf_vector_t *dst_vector, caf_token_t src_token, size_t ! src_offset, int src_image_index, gfc_descriptor_t *src, ! caf_vector_t *src_vector, int dst_kind, int src_kind, bool ! may_require_tmp)' _Arguments_: ! DST_TOKEN intent(in) An opaque pointer identifying the ! destination coarray. ! DST_OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! destination coarray. ! DST_IMAGE_INDEXThe ID of the destination remote image; must ! be a positive number. ! DEST intent(in) Array descriptor for the destination ! remote image for the bounds and the size. The ! base_addr shall not be accessed. ! DST_VECTOR intent(int) If not NULL, it contains the ! vector subscript of the destination array; the ! values are relative to the dimension triplet ! of the dest argument. ! SRC_TOKEN An opaque pointer identifying the source ! coarray. ! SRC_OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! source coarray. SRC_IMAGE_INDEXThe ID of the source remote image; must be a ! positive number. ! SRC intent(in) Array descriptor of the local array ! to be transferred to the remote image. ! SRC_VECTOR intent(in) Array descriptor of the local array ! to be transferred to the remote image ! DST_KIND Kind of the destination argument ! SRC_KIND Kind of the source argument MAY_REQUIRE_TMPThe variable is false it is known at compile ! time that the DEST and SRC either cannot ! overlap or overlap (fully or partially) such ! that walking SRC and DEST in element wise ! element order (honoring the stride value) will ! not lead to wrong results. Otherwise, the ! value is true. _NOTES_ It is permitted to have image_ids equal; the memory of the send-to ! and the send-from might (partially) overlap in that case. The implementation has to take care that it handles this case, e.g. ! using `memmove' which handles (partially) overlapping memory. If MAY_REQUIRE_TMP is true, the library might additionally create a temporary variable, unless additional checks show that this is not ! required (e.g. because walking backward is possible or because ! both arrays are contiguous and `memmove' takes care of overlap issues). ! Note that the assignment of a scalar to an array is permitted. In ! addition, the library has to handle numeric-type conversion and ! for strings, padding and different character kinds.  File: gfortran.info, Node: _gfortran_caf_lock, Next: _gfortran_caf_unlock, Prev: _gfortran_caf_sendget, Up: Function ABI Documentation ! 8.2.10 `_gfortran_caf_lock' -- Locking a lock variable ------------------------------------------------------ _Description_: Acquire a lock on the given image on a scalar locking variable or ! for the given array element for an array-valued variable. If the ! AQUIRED_LOCK is `NULL', the function return after having obtained ! the lock. If it is nonnull, the result is is assigned the value true (one) when the lock could be obtained and false (zero) otherwise. Locking a lock variable which has already been locked by the same image is an error. _Syntax_: ! `void _gfortran_caf_lock (caf_token_t token, size_t index, int image_index, int *aquired_lock, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number. ! AQUIRED_LOCKintent(out) If not NULL, it returns whether ! lock could be obtained ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ This function is also called for critical blocks; for those, the *************** _NOTES_ *** 4913,4943 ****  File: gfortran.info, Node: _gfortran_caf_unlock, Next: _gfortran_caf_event_post, Prev: _gfortran_caf_lock, Up: Function ABI Documentation ! 8.2.11 '_gfortran_caf_lock' -- Unlocking a lock variable -------------------------------------------------------- _Description_: Release a lock on the given image on a scalar locking variable or for the given array element for an array-valued variable. ! Unlocking a lock variable which is unlocked or has been locked by a ! different image is an error. _Syntax_: ! 'void _gfortran_caf_unlock (caf_token_t token, size_t index, int image_index, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number. ! STAT intent(out) For allocatable coarrays, stores the ! STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ This function is also called for critical block; for those, the --- 4959,4989 ----  File: gfortran.info, Node: _gfortran_caf_unlock, Next: _gfortran_caf_event_post, Prev: _gfortran_caf_lock, Up: Function ABI Documentation ! 8.2.11 `_gfortran_caf_lock' -- Unlocking a lock variable -------------------------------------------------------- _Description_: Release a lock on the given image on a scalar locking variable or for the given array element for an array-valued variable. ! Unlocking a lock variable which is unlocked or has been locked by ! a different image is an error. _Syntax_: ! `void _gfortran_caf_unlock (caf_token_t token, size_t index, int image_index, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number. ! STAT intent(out) For allocatable coarrays, stores ! the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ This function is also called for critical block; for those, the *************** _NOTES_ *** 4948,4987 ****  File: gfortran.info, Node: _gfortran_caf_event_post, Next: _gfortran_caf_event_wait, Prev: _gfortran_caf_unlock, Up: Function ABI Documentation ! 8.2.12 '_gfortran_caf_event_post' -- Post an event -------------------------------------------------- _Description_: Increment the event count of the specified event variable. _Syntax_: ! 'void _gfortran_caf_event_post (caf_token_t token, size_t index, int image_index, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number; zero indicates the current image when ! accessed noncoindexed. ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ This acts like an atomic add of one to the remote image's event ! variable. The statement is an image-control statement but does not ! imply sync memory. Still, all preceeding push communications of ! this image to the specified remote image has to be completed before ! 'event_wait' on the remote image returns.  File: gfortran.info, Node: _gfortran_caf_event_wait, Next: _gfortran_caf_event_query, Prev: _gfortran_caf_event_post, Up: Function ABI Documentation ! 8.2.13 '_gfortran_caf_event_wait' -- Wait that an event occurred ---------------------------------------------------------------- _Description_: --- 4994,5033 ----  File: gfortran.info, Node: _gfortran_caf_event_post, Next: _gfortran_caf_event_wait, Prev: _gfortran_caf_unlock, Up: Function ABI Documentation ! 8.2.12 `_gfortran_caf_event_post' -- Post an event -------------------------------------------------- _Description_: Increment the event count of the specified event variable. _Syntax_: ! `void _gfortran_caf_event_post (caf_token_t token, size_t index, int image_index, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number; zero indicates the current image when ! accessed noncoindexed. ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ This acts like an atomic add of one to the remote image's event ! variable. The statement is an image-control statement but does ! not imply sync memory. Still, all preceeding push communications ! of this image to the specified remote image has to be completed ! before `event_wait' on the remote image returns.  File: gfortran.info, Node: _gfortran_caf_event_wait, Next: _gfortran_caf_event_query, Prev: _gfortran_caf_event_post, Up: Function ABI Documentation ! 8.2.13 `_gfortran_caf_event_wait' -- Wait that an event occurred ---------------------------------------------------------------- _Description_: *************** _Description_: *** 4990,5055 **** amount and return. _Syntax_: ! 'void _gfortran_caf_event_wait (caf_token_t token, size_t index, int until_count, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! UNTIL_COUNT The number of events which have to be available ! before the function returns. ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ ! This function only operates on a local coarray. It acts like a loop checking atomically the value of the event variable, breaking if the value is greater or equal the requested number of counts. Before the function returns, the event variable has to be decremented by the requested UNTIL_COUNT value. A possible implementation would be a busy loop for a certain number of spins ! (possibly depending on the number of threads relative to the number ! of available cores) followed by other waiting strategy such as a ! sleeping wait (possibly with an increasing number of sleep time) ! or, if possible, a futex wait. ! The statement is an image-control statement but does not imply sync ! memory. Still, all preceeding push communications to this image of ! images having issued a 'event_push' have to be completed before ! this function returns.  File: gfortran.info, Node: _gfortran_caf_event_query, Next: _gfortran_caf_sync_all, Prev: _gfortran_caf_event_wait, Up: Function ABI Documentation ! 8.2.14 '_gfortran_caf_event_query' -- Query event count ------------------------------------------------------- _Description_: Return the event count of the specified event count. _Syntax_: ! 'void _gfortran_caf_event_query (caf_token_t token, size_t index, int image_index, int *count, int *stat)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number; zero indicates the current image when ! accessed noncoindexed. ! COUNT intent(out) The number of events currently ! posted to the event variable ! STAT intent(out) Stores the STAT=; may be NULL _NOTES_ The typical use is to check the local even variable to only call ! 'event_wait' when the data is available. However, a coindexed variable is permitted; there is no ordering or synchronization implied. It acts like an atomic fetch of the value of the event variable. --- 5036,5101 ---- amount and return. _Syntax_: ! `void _gfortran_caf_event_wait (caf_token_t token, size_t index, int until_count, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! UNTIL_COUNTThe number of events which have to be available ! before the function returns. ! STAT intent(out) Stores the STAT=; may be NULL ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ ! This function only operates on a local coarray. It acts like a loop checking atomically the value of the event variable, breaking if the value is greater or equal the requested number of counts. Before the function returns, the event variable has to be decremented by the requested UNTIL_COUNT value. A possible implementation would be a busy loop for a certain number of spins ! (possibly depending on the number of threads relative to the ! number of available cores) followed by other waiting strategy such ! as a sleeping wait (possibly with an increasing number of sleep ! time) or, if possible, a futex wait. ! The statement is an image-control statement but does not imply ! sync memory. Still, all preceeding push communications to this ! image of images having issued a `event_push' have to be completed ! before this function returns.  File: gfortran.info, Node: _gfortran_caf_event_query, Next: _gfortran_caf_sync_all, Prev: _gfortran_caf_event_wait, Up: Function ABI Documentation ! 8.2.14 `_gfortran_caf_event_query' -- Query event count ------------------------------------------------------- _Description_: Return the event count of the specified event count. _Syntax_: ! `void _gfortran_caf_event_query (caf_token_t token, size_t index, int image_index, int *count, int *stat)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! INDEX Array index; first array index is 0. For ! scalars, it is always 0. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number; zero indicates the current image when ! accessed noncoindexed. ! COUNT intent(out) The number of events currently ! posted to the event variable ! STAT intent(out) Stores the STAT=; may be NULL _NOTES_ The typical use is to check the local even variable to only call ! `event_wait' when the data is available. However, a coindexed variable is permitted; there is no ordering or synchronization implied. It acts like an atomic fetch of the value of the event variable. *************** _NOTES_ *** 5057,5210 ****  File: gfortran.info, Node: _gfortran_caf_sync_all, Next: _gfortran_caf_sync_images, Prev: _gfortran_caf_event_query, Up: Function ABI Documentation ! 8.2.15 '_gfortran_caf_sync_all' -- All-image barrier ---------------------------------------------------- _Description_: ! Synchronization of all images in the current team; the program only ! continues on a given image after this function has been called on ! all images of the current team. Additionally, it ensures that all ! pending data transfers of previous segment have completed. _Syntax_: ! 'void _gfortran_caf_sync_all (int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg.  File: gfortran.info, Node: _gfortran_caf_sync_images, Next: _gfortran_caf_sync_memory, Prev: _gfortran_caf_sync_all, Up: Function ABI Documentation ! 8.2.16 '_gfortran_caf_sync_images' -- Barrier for selected images ----------------------------------------------------------------- _Description_: Synchronization between the specified images; the program only continues on a given image after this function has been called on ! all images specified for that image. Note that one image can wait ! for all other images in the current team (e.g. via 'sync images(*)') while those only wait for that specific image. ! Additionally, 'sync images' it ensures that all pending data transfers of previous segment have completed. _Syntax_: ! 'void _gfortran_caf_sync_images (int count, int images[], int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! COUNT the number of images which are provided in the ! next argument. For a zero-sized array, the ! value is zero. For 'sync images (*)', the value ! is -1. ! IMAGES intent(in) an array with the images provided by ! the user. If COUNT is zero, a NULL pointer is ! passed. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg.  File: gfortran.info, Node: _gfortran_caf_sync_memory, Next: _gfortran_caf_error_stop, Prev: _gfortran_caf_sync_images, Up: Function ABI Documentation ! 8.2.17 '_gfortran_caf_sync_memory' -- Wait for completion of segment-memory operations -------------------------------------------------------------------------------------- _Description_: ! Acts as optimization barrier between different segments. It also ensures that all pending memory operations of this image have been completed. _Syntax_: ! 'void _gfortran_caf_sync_memory (int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTE_ A simple implementation could be ! '__asm__ __volatile__ ("":::"memory")' to prevent code movements.  File: gfortran.info, Node: _gfortran_caf_error_stop, Next: _gfortran_caf_error_stop_str, Prev: _gfortran_caf_sync_memory, Up: Function ABI Documentation ! 8.2.18 '_gfortran_caf_error_stop' -- Error termination with exit code --------------------------------------------------------------------- _Description_: ! Invoked for an 'ERROR STOP' statement which has an integer argument. The function should terminate the program with the specified exit code. _Syntax_: ! 'void _gfortran_caf_error_stop (int32_t error)' _Arguments_: ! ERROR the exit status to be used.  File: gfortran.info, Node: _gfortran_caf_error_stop_str, Next: _gfortran_caf_atomic_define, Prev: _gfortran_caf_error_stop, Up: Function ABI Documentation ! 8.2.19 '_gfortran_caf_error_stop_str' -- Error termination with string ---------------------------------------------------------------------- _Description_: ! Invoked for an 'ERROR STOP' statement which has a string as argument. The function should terminate the program with a nonzero-exit code. _Syntax_: ! 'void _gfortran_caf_error_stop (const char *string, int32_t len)' _Arguments_: ! STRING the error message (not zero terminated) ! LEN the length of the string  File: gfortran.info, Node: _gfortran_caf_atomic_define, Next: _gfortran_caf_atomic_ref, Prev: _gfortran_caf_error_stop_str, Up: Function ABI Documentation ! 8.2.20 '_gfortran_caf_atomic_define' -- Atomic variable assignment ------------------------------------------------------------------ _Description_: Assign atomically a value to an integer or logical variable. _Syntax_: ! 'void _gfortran_caf_atomic_define (caf_token_t token, size_t offset, int image_index, void *value, int *stat, int type, int kind)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! VALUE intent(in) the value to be assigned, passed by ! reference. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. 'BT_INTEGER' (1) or ! 'BT_LOGICAL' (2). ! KIND The kind value (only 4; always 'int')  File: gfortran.info, Node: _gfortran_caf_atomic_ref, Next: _gfortran_caf_atomic_cas, Prev: _gfortran_caf_atomic_define, Up: Function ABI Documentation ! 8.2.21 '_gfortran_caf_atomic_ref' -- Atomic variable reference -------------------------------------------------------------- _Description_: --- 5103,5257 ----  File: gfortran.info, Node: _gfortran_caf_sync_all, Next: _gfortran_caf_sync_images, Prev: _gfortran_caf_event_query, Up: Function ABI Documentation ! 8.2.15 `_gfortran_caf_sync_all' -- All-image barrier ---------------------------------------------------- _Description_: ! Synchronization of all images in the current team; the program ! only continues on a given image after this function has been ! called on all images of the current team. Additionally, it ! ensures that all pending data transfers of previous segment have ! completed. _Syntax_: ! `void _gfortran_caf_sync_all (int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg.  File: gfortran.info, Node: _gfortran_caf_sync_images, Next: _gfortran_caf_sync_memory, Prev: _gfortran_caf_sync_all, Up: Function ABI Documentation ! 8.2.16 `_gfortran_caf_sync_images' -- Barrier for selected images ----------------------------------------------------------------- _Description_: Synchronization between the specified images; the program only continues on a given image after this function has been called on ! all images specified for that image. Note that one image can wait ! for all other images in the current team (e.g. via `sync images(*)') while those only wait for that specific image. ! Additionally, `sync images' it ensures that all pending data transfers of previous segment have completed. _Syntax_: ! `void _gfortran_caf_sync_images (int count, int images[], int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! COUNT the number of images which are provided in the ! next argument. For a zero-sized array, the ! value is zero. For `sync images (*)', the ! value is -1. ! IMAGES intent(in) an array with the images provided ! by the user. If COUNT is zero, a NULL pointer ! is passed. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg.  File: gfortran.info, Node: _gfortran_caf_sync_memory, Next: _gfortran_caf_error_stop, Prev: _gfortran_caf_sync_images, Up: Function ABI Documentation ! 8.2.17 `_gfortran_caf_sync_memory' -- Wait for completion of segment-memory operations -------------------------------------------------------------------------------------- _Description_: ! Acts as optimization barrier between different segments. It also ensures that all pending memory operations of this image have been completed. _Syntax_: ! `void _gfortran_caf_sync_memory (int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTE_ A simple implementation could be ! `__asm__ __volatile__ ("":::"memory")' to prevent code movements.  File: gfortran.info, Node: _gfortran_caf_error_stop, Next: _gfortran_caf_error_stop_str, Prev: _gfortran_caf_sync_memory, Up: Function ABI Documentation ! 8.2.18 `_gfortran_caf_error_stop' -- Error termination with exit code --------------------------------------------------------------------- _Description_: ! Invoked for an `ERROR STOP' statement which has an integer argument. The function should terminate the program with the specified exit code. _Syntax_: ! `void _gfortran_caf_error_stop (int32_t error)' _Arguments_: ! ERROR the exit status to be used.  File: gfortran.info, Node: _gfortran_caf_error_stop_str, Next: _gfortran_caf_atomic_define, Prev: _gfortran_caf_error_stop, Up: Function ABI Documentation ! 8.2.19 `_gfortran_caf_error_stop_str' -- Error termination with string ---------------------------------------------------------------------- _Description_: ! Invoked for an `ERROR STOP' statement which has a string as argument. The function should terminate the program with a nonzero-exit code. _Syntax_: ! `void _gfortran_caf_error_stop (const char *string, int32_t len)' _Arguments_: ! STRING the error message (not zero terminated) ! LEN the length of the string  File: gfortran.info, Node: _gfortran_caf_atomic_define, Next: _gfortran_caf_atomic_ref, Prev: _gfortran_caf_error_stop_str, Up: Function ABI Documentation ! 8.2.20 `_gfortran_caf_atomic_define' -- Atomic variable assignment ------------------------------------------------------------------ _Description_: Assign atomically a value to an integer or logical variable. _Syntax_: ! `void _gfortran_caf_atomic_define (caf_token_t token, size_t offset, int image_index, void *value, int *stat, int type, int kind)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! VALUE intent(in) the value to be assigned, passed by ! reference. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. `BT_INTEGER' (1) or ! `BT_LOGICAL' (2). ! KIND The kind value (only 4; always `int')  File: gfortran.info, Node: _gfortran_caf_atomic_ref, Next: _gfortran_caf_atomic_cas, Prev: _gfortran_caf_atomic_define, Up: Function ABI Documentation ! 8.2.21 `_gfortran_caf_atomic_ref' -- Atomic variable reference -------------------------------------------------------------- _Description_: *************** _Description_: *** 5212,5242 **** variable. _Syntax_: ! 'void _gfortran_caf_atomic_ref (caf_token_t token, size_t offset, int image_index, void *value, int *stat, int type, int kind)' _Arguments_: _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! VALUE intent(out) The variable assigned the atomically ! referenced variable. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. 'BT_INTEGER' (1) or ! 'BT_LOGICAL' (2). ! KIND The kind value (only 4; always 'int')  File: gfortran.info, Node: _gfortran_caf_atomic_cas, Next: _gfortran_caf_atomic_op, Prev: _gfortran_caf_atomic_ref, Up: Function ABI Documentation ! 8.2.22 '_gfortran_caf_atomic_cas' -- Atomic compare and swap ------------------------------------------------------------ _Description_: --- 5259,5290 ---- variable. _Syntax_: ! `void _gfortran_caf_atomic_ref (caf_token_t token, size_t offset, int image_index, void *value, int *stat, int type, int kind)' _Arguments_: + _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! VALUE intent(out) The variable assigned the ! atomically referenced variable. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. `BT_INTEGER' (1) or ! `BT_LOGICAL' (2). ! KIND The kind value (only 4; always `int')  File: gfortran.info, Node: _gfortran_caf_atomic_cas, Next: _gfortran_caf_atomic_op, Prev: _gfortran_caf_atomic_ref, Up: Function ABI Documentation ! 8.2.22 `_gfortran_caf_atomic_cas' -- Atomic compare and swap ------------------------------------------------------------ _Description_: *************** _Description_: *** 5245,5376 **** the latter has the value specified by the passed condition value. _Syntax_: ! 'void _gfortran_caf_atomic_cas (caf_token_t token, size_t offset, int image_index, void *old, void *compare, void *new_val, int *stat, int type, int kind)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! OLD intent(out) the value which the atomic variable ! had just before the cas operation. ! COMPARE intent(in) The value used for comparision. ! NEW_VAL intent(in) The new value for the atomic ! variable, assigned to the atomic variable, if ! 'compare' equals the value of the atomic ! variable. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. 'BT_INTEGER' (1) or ! 'BT_LOGICAL' (2). ! KIND The kind value (only 4; always 'int')  File: gfortran.info, Node: _gfortran_caf_atomic_op, Next: _gfortran_caf_co_broadcast, Prev: _gfortran_caf_atomic_cas, Up: Function ABI Documentation ! 8.2.23 '_gfortran_caf_atomic_op' -- Atomic operation ---------------------------------------------------- _Description_: Apply an operation atomically to an atomic integer or logical variable. After the operation, OLD contains the value just before the operation, which, respectively, adds (GFC_CAF_ATOMIC_ADD) ! atomically the 'value' to the atomic integer variable or does a bitwise AND, OR or exclusive OR of the between the atomic variable and VALUE; the result is then stored in the atomic variable. _Syntax_: ! 'void _gfortran_caf_atomic_op (int op, caf_token_t token, size_t offset, int image_index, void *value, void *old, int *stat, int type, int kind)' _Arguments_: ! OP the operation to be performed; possible values ! 'GFC_CAF_ATOMIC_ADD' (1), 'GFC_CAF_ATOMIC_AND' ! (2), 'GFC_CAF_ATOMIC_OR' (3), ! 'GFC_CAF_ATOMIC_XOR' (4). ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEX The ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! OLD intent(out) the value which the atomic variable ! had just before the atomic operation. ! VAL intent(in) The new value for the atomic ! variable, assigned to the atomic variable, if ! 'compare' equals the value of the atomic ! variable. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. 'BT_INTEGER' (1) or ! 'BT_LOGICAL' (2). ! KIND The kind value (only 4; always 'int')  File: gfortran.info, Node: _gfortran_caf_co_broadcast, Next: _gfortran_caf_co_max, Prev: _gfortran_caf_atomic_op, Up: Function ABI Documentation ! 8.2.24 '_gfortran_caf_co_broadcast' -- Sending data to all images ----------------------------------------------------------------- _Description_: Distribute a value from a given image to all other images in the ! team. Has to be called collectively. _Syntax_: ! 'void _gfortran_caf_co_broadcast (gfc_descriptor_t *a, int source_image, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the data ! to be breoadcasted (on SOURCE_IMAGE) or to be ! received (other images). SOURCE_IMAGEThe ID of the image from which the data should ! be taken. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg.  File: gfortran.info, Node: _gfortran_caf_co_max, Next: _gfortran_caf_co_min, Prev: _gfortran_caf_co_broadcast, Up: Function ABI Documentation ! 8.2.25 '_gfortran_caf_co_max' -- Collective maximum reduction ------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the ! maximum value for that element in the current team; if RESULT_IMAGE ! has the value 0, the result shall be stored on all images, ! otherwise, only on the specified image. This function operates on ! numeric values and character strings. _Syntax_: ! 'void _gfortran_caf_co_max (gfc_descriptor_t *a, int result_image, int *stat, char *errmsg, int a_len, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the data ! to be breoadcasted (on SOURCE_IMAGE) or to be ! received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! A_LEN The string length of argument A. ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the --- 5293,5424 ---- the latter has the value specified by the passed condition value. _Syntax_: ! `void _gfortran_caf_atomic_cas (caf_token_t token, size_t offset, int image_index, void *old, void *compare, void *new_val, int *stat, int type, int kind)' _Arguments_: ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! OLD intent(out) the value which the atomic ! variable had just before the cas operation. ! COMPARE intent(in) The value used for comparision. ! NEW_VAL intent(in) The new value for the atomic ! variable, assigned to the atomic variable, if ! `compare' equals the value of the atomic ! variable. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. `BT_INTEGER' (1) or ! `BT_LOGICAL' (2). ! KIND The kind value (only 4; always `int')  File: gfortran.info, Node: _gfortran_caf_atomic_op, Next: _gfortran_caf_co_broadcast, Prev: _gfortran_caf_atomic_cas, Up: Function ABI Documentation ! 8.2.23 `_gfortran_caf_atomic_op' -- Atomic operation ---------------------------------------------------- _Description_: Apply an operation atomically to an atomic integer or logical variable. After the operation, OLD contains the value just before the operation, which, respectively, adds (GFC_CAF_ATOMIC_ADD) ! atomically the `value' to the atomic integer variable or does a bitwise AND, OR or exclusive OR of the between the atomic variable and VALUE; the result is then stored in the atomic variable. _Syntax_: ! `void _gfortran_caf_atomic_op (int op, caf_token_t token, size_t offset, int image_index, void *value, void *old, int *stat, int type, int kind)' _Arguments_: ! OP the operation to be performed; possible values ! `GFC_CAF_ATOMIC_ADD' (1), `GFC_CAF_ATOMIC_AND' ! (2), `GFC_CAF_ATOMIC_OR' (3), ! `GFC_CAF_ATOMIC_XOR' (4). ! TOKEN intent(in) An opaque pointer identifying the ! coarray. ! OFFSET By which amount of bytes the actual data is ! shifted compared to the base address of the ! coarray. ! IMAGE_INDEXThe ID of the remote image; must be a positive ! number; zero indicates the current image when ! used noncoindexed. ! OLD intent(out) the value which the atomic ! variable had just before the atomic operation. ! VAL intent(in) The new value for the atomic ! variable, assigned to the atomic variable, if ! `compare' equals the value of the atomic ! variable. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! TYPE the data type, i.e. `BT_INTEGER' (1) or ! `BT_LOGICAL' (2). ! KIND The kind value (only 4; always `int')  File: gfortran.info, Node: _gfortran_caf_co_broadcast, Next: _gfortran_caf_co_max, Prev: _gfortran_caf_atomic_op, Up: Function ABI Documentation ! 8.2.24 `_gfortran_caf_co_broadcast' -- Sending data to all images ----------------------------------------------------------------- _Description_: Distribute a value from a given image to all other images in the ! team. Has to be called collectively. _Syntax_: ! `void _gfortran_caf_co_broadcast (gfc_descriptor_t *a, int source_image, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the ! data to be breoadcasted (on SOURCE_IMAGE) or ! to be received (other images). SOURCE_IMAGEThe ID of the image from which the data should ! be taken. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg.  File: gfortran.info, Node: _gfortran_caf_co_max, Next: _gfortran_caf_co_min, Prev: _gfortran_caf_co_broadcast, Up: Function ABI Documentation ! 8.2.25 `_gfortran_caf_co_max' -- Collective maximum reduction ------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the ! maximum value for that element in the current team; if ! RESULT_IMAGE has the value 0, the result shall be stored on all ! images, otherwise, only on the specified image. This function ! operates on numeric values and character strings. _Syntax_: ! `void _gfortran_caf_co_max (gfc_descriptor_t *a, int result_image, int *stat, char *errmsg, int a_len, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the ! data to be breoadcasted (on SOURCE_IMAGE) or ! to be received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! A_LEN The string length of argument A. ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the *************** _NOTES_ *** 5380,5412 ****  File: gfortran.info, Node: _gfortran_caf_co_min, Next: _gfortran_caf_co_sum, Prev: _gfortran_caf_co_max, Up: Function ABI Documentation ! 8.2.26 '_gfortran_caf_co_min' -- Collective minimum reduction ------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the ! minimum value for that element in the current team; if RESULT_IMAGE ! has the value 0, the result shall be stored on all images, ! otherwise, only on the specified image. This function operates on ! numeric values and character strings. _Syntax_: ! 'void _gfortran_caf_co_min (gfc_descriptor_t *a, int result_image, int *stat, char *errmsg, int a_len, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the data ! to be breoadcasted (on SOURCE_IMAGE) or to be ! received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! A_LEN The string length of argument A. ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the --- 5428,5460 ----  File: gfortran.info, Node: _gfortran_caf_co_min, Next: _gfortran_caf_co_sum, Prev: _gfortran_caf_co_max, Up: Function ABI Documentation ! 8.2.26 `_gfortran_caf_co_min' -- Collective minimum reduction ------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the ! minimum value for that element in the current team; if ! RESULT_IMAGE has the value 0, the result shall be stored on all ! images, otherwise, only on the specified image. This function ! operates on numeric values and character strings. _Syntax_: ! `void _gfortran_caf_co_min (gfc_descriptor_t *a, int result_image, int *stat, char *errmsg, int a_len, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the ! data to be breoadcasted (on SOURCE_IMAGE) or ! to be received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! A_LEN The string length of argument A. ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the *************** _NOTES_ *** 5416,5446 ****  File: gfortran.info, Node: _gfortran_caf_co_sum, Next: _gfortran_caf_co_reduce, Prev: _gfortran_caf_co_min, Up: Function ABI Documentation ! 8.2.27 '_gfortran_caf_co_sum' -- Collective summing reduction ------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the sum value for that element in the current team; if RESULT_IMAGE has the value 0, the result shall be stored on all images, otherwise, only ! on the specified image. This function operates on numeric values. _Syntax_: ! 'void _gfortran_caf_co_sum (gfc_descriptor_t *a, int result_image, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the data ! to be breoadcasted (on SOURCE_IMAGE) or to be ! received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the --- 5464,5494 ----  File: gfortran.info, Node: _gfortran_caf_co_sum, Next: _gfortran_caf_co_reduce, Prev: _gfortran_caf_co_min, Up: Function ABI Documentation ! 8.2.27 `_gfortran_caf_co_sum' -- Collective summing reduction ------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the sum value for that element in the current team; if RESULT_IMAGE has the value 0, the result shall be stored on all images, otherwise, only ! on the specified image. This function operates on numeric values. _Syntax_: ! `void _gfortran_caf_co_sum (gfc_descriptor_t *a, int result_image, int *stat, char *errmsg, int errmsg_len)' _Arguments_: ! A intent(inout) And array descriptor with the ! data to be breoadcasted (on SOURCE_IMAGE) or ! to be received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the *************** _NOTES_ *** 5450,5503 ****  File: gfortran.info, Node: _gfortran_caf_co_reduce, Prev: _gfortran_caf_co_sum, Up: Function ABI Documentation ! 8.2.28 '_gfortran_caf_co_reduce' -- Generic collective reduction ---------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the reduction value for that element in the current team; if RESULT_IMAGE has the value 0, the result shall be stored on all ! images, otherwise, only on the specified image. The OPR is a pure function doing a mathematically commutative and associative operation. The OPR_FLAGS denote the following; the values are bitwise ored. ! 'GFC_CAF_BYREF' (1) if the result should be returned by value; ! 'GFC_CAF_HIDDENLEN' (2) whether the result and argument string ! lengths shall be specified as hidden argument; 'GFC_CAF_ARG_VALUE' (4) whether the arguments shall be passed by value, ! 'GFC_CAF_ARG_DESC' (8) whether the arguments shall be passed by descriptor. _Syntax_: ! 'void _gfortran_caf_co_reduce (gfc_descriptor_t *a, void * (*opr) (void *, void *), int opr_flags, int result_image, int *stat, char *errmsg, int a_len, int errmsg_len)' _Arguments_: ! OPR Function pointer to the reduction function. ! OPR_FLAGS Flags regarding the reduction function ! A intent(inout) And array descriptor with the data ! to be breoadcasted (on SOURCE_IMAGE) or to be ! received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! A_LEN The string length of argument A. ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the specified one become undefined; hence, the library may make use of this. For character arguments, the result is passed as first argument, followed by the result string length, next come the two ! string arguments, followed by the two hidden arguments. With C ! binding, there are no hidden arguments and by-reference passing and ! either only a single character is passed or an array descriptor.  File: gfortran.info, Node: Intrinsic Procedures, Next: Intrinsic Modules, Prev: Coarray Programming, Up: Top --- 5498,5552 ----  File: gfortran.info, Node: _gfortran_caf_co_reduce, Prev: _gfortran_caf_co_sum, Up: Function ABI Documentation ! 8.2.28 `_gfortran_caf_co_reduce' -- Generic collective reduction ---------------------------------------------------------------- _Description_: Calculates the for the each array element of the variable A the reduction value for that element in the current team; if RESULT_IMAGE has the value 0, the result shall be stored on all ! images, otherwise, only on the specified image. The OPR is a pure function doing a mathematically commutative and associative operation. The OPR_FLAGS denote the following; the values are bitwise ored. ! `GFC_CAF_BYREF' (1) if the result should be returned by value; ! `GFC_CAF_HIDDENLEN' (2) whether the result and argument string ! lengths shall be specified as hidden argument; `GFC_CAF_ARG_VALUE' (4) whether the arguments shall be passed by value, ! `GFC_CAF_ARG_DESC' (8) whether the arguments shall be passed by descriptor. _Syntax_: ! `void _gfortran_caf_co_reduce (gfc_descriptor_t *a, void * (*opr) (void *, void *), int opr_flags, int result_image, int *stat, char *errmsg, int a_len, int errmsg_len)' _Arguments_: ! OPR Function pointer to the reduction function. ! OPR_FLAGS Flags regarding the reduction function ! A intent(inout) And array descriptor with the ! data to be breoadcasted (on SOURCE_IMAGE) or ! to be received (other images). RESULT_IMAGEThe ID of the image to which the reduced value ! should be copied to; if zero, it has to be ! copied to all images. ! STAT intent(out) Stores the status STAT= and may be ! NULL. ! ERRMSG intent(out) When an error occurs, this will be ! set to an error message; may be NULL ! A_LEN The string length of argument A. ! ERRMSG_LEN the buffer size of errmsg. _NOTES_ If RESULT_IMAGE is nonzero, the value on all images except of the specified one become undefined; hence, the library may make use of this. For character arguments, the result is passed as first argument, followed by the result string length, next come the two ! string arguments, followed by the two hidden arguments. With C ! binding, there are no hidden arguments and by-reference passing ! and either only a single character is passed or an array ! descriptor.  File: gfortran.info, Node: Intrinsic Procedures, Next: Intrinsic Modules, Prev: Coarray Programming, Up: Top *************** File: gfortran.info, Node: Intrinsic Pr *** 5508,5784 **** * Menu: * Introduction: Introduction to Intrinsics ! * 'ABORT': ABORT, Abort the program ! * 'ABS': ABS, Absolute value ! * 'ACCESS': ACCESS, Checks file access modes ! * 'ACHAR': ACHAR, Character in ASCII collating sequence ! * 'ACOS': ACOS, Arccosine function ! * 'ACOSH': ACOSH, Inverse hyperbolic cosine function ! * 'ADJUSTL': ADJUSTL, Left adjust a string ! * 'ADJUSTR': ADJUSTR, Right adjust a string ! * 'AIMAG': AIMAG, Imaginary part of complex number ! * 'AINT': AINT, Truncate to a whole number ! * 'ALARM': ALARM, Set an alarm clock ! * 'ALL': ALL, Determine if all values are true ! * 'ALLOCATED': ALLOCATED, Status of allocatable entity ! * 'AND': AND, Bitwise logical AND ! * 'ANINT': ANINT, Nearest whole number ! * 'ANY': ANY, Determine if any values are true ! * 'ASIN': ASIN, Arcsine function ! * 'ASINH': ASINH, Inverse hyperbolic sine function ! * 'ASSOCIATED': ASSOCIATED, Status of a pointer or pointer/target pair ! * 'ATAN': ATAN, Arctangent function ! * 'ATAN2': ATAN2, Arctangent function ! * 'ATANH': ATANH, Inverse hyperbolic tangent function ! * 'ATOMIC_ADD': ATOMIC_ADD, Atomic ADD operation ! * 'ATOMIC_AND': ATOMIC_AND, Atomic bitwise AND operation ! * 'ATOMIC_CAS': ATOMIC_CAS, Atomic compare and swap ! * 'ATOMIC_DEFINE': ATOMIC_DEFINE, Setting a variable atomically ! * 'ATOMIC_FETCH_ADD': ATOMIC_FETCH_ADD, Atomic ADD operation with prior fetch ! * 'ATOMIC_FETCH_AND': ATOMIC_FETCH_AND, Atomic bitwise AND operation with prior fetch ! * 'ATOMIC_FETCH_OR': ATOMIC_FETCH_OR, Atomic bitwise OR operation with prior fetch ! * 'ATOMIC_FETCH_XOR': ATOMIC_FETCH_XOR, Atomic bitwise XOR operation with prior fetch ! * 'ATOMIC_OR': ATOMIC_OR, Atomic bitwise OR operation ! * 'ATOMIC_REF': ATOMIC_REF, Obtaining the value of a variable atomically ! * 'ATOMIC_XOR': ATOMIC_XOR, Atomic bitwise OR operation ! * 'BACKTRACE': BACKTRACE, Show a backtrace ! * 'BESSEL_J0': BESSEL_J0, Bessel function of the first kind of order 0 ! * 'BESSEL_J1': BESSEL_J1, Bessel function of the first kind of order 1 ! * 'BESSEL_JN': BESSEL_JN, Bessel function of the first kind ! * 'BESSEL_Y0': BESSEL_Y0, Bessel function of the second kind of order 0 ! * 'BESSEL_Y1': BESSEL_Y1, Bessel function of the second kind of order 1 ! * 'BESSEL_YN': BESSEL_YN, Bessel function of the second kind ! * 'BGE': BGE, Bitwise greater than or equal to ! * 'BGT': BGT, Bitwise greater than ! * 'BIT_SIZE': BIT_SIZE, Bit size inquiry function ! * 'BLE': BLE, Bitwise less than or equal to ! * 'BLT': BLT, Bitwise less than ! * 'BTEST': BTEST, Bit test function ! * 'C_ASSOCIATED': C_ASSOCIATED, Status of a C pointer ! * 'C_F_POINTER': C_F_POINTER, Convert C into Fortran pointer ! * 'C_F_PROCPOINTER': C_F_PROCPOINTER, Convert C into Fortran procedure pointer ! * 'C_FUNLOC': C_FUNLOC, Obtain the C address of a procedure ! * 'C_LOC': C_LOC, Obtain the C address of an object ! * 'C_SIZEOF': C_SIZEOF, Size in bytes of an expression ! * 'CEILING': CEILING, Integer ceiling function ! * 'CHAR': CHAR, Integer-to-character conversion function ! * 'CHDIR': CHDIR, Change working directory ! * 'CHMOD': CHMOD, Change access permissions of files ! * 'CMPLX': CMPLX, Complex conversion function ! * 'CO_BROADCAST': CO_BROADCAST, Copy a value to all images the current set of images ! * 'CO_MAX': CO_MAX, Maximal value on the current set of images ! * 'CO_MIN': CO_MIN, Minimal value on the current set of images ! * 'CO_REDUCE': CO_REDUCE, Reduction of values on the current set of images ! * 'CO_SUM': CO_SUM, Sum of values on the current set of images ! * 'COMMAND_ARGUMENT_COUNT': COMMAND_ARGUMENT_COUNT, Get number of command line arguments ! * 'COMPILER_OPTIONS': COMPILER_OPTIONS, Options passed to the compiler ! * 'COMPILER_VERSION': COMPILER_VERSION, Compiler version string ! * 'COMPLEX': COMPLEX, Complex conversion function ! * 'CONJG': CONJG, Complex conjugate function ! * 'COS': COS, Cosine function ! * 'COSH': COSH, Hyperbolic cosine function ! * 'COUNT': COUNT, Count occurrences of TRUE in an array ! * 'CPU_TIME': CPU_TIME, CPU time subroutine ! * 'CSHIFT': CSHIFT, Circular shift elements of an array ! * 'CTIME': CTIME, Subroutine (or function) to convert a time into a string ! * 'DATE_AND_TIME': DATE_AND_TIME, Date and time subroutine ! * 'DBLE': DBLE, Double precision conversion function ! * 'DCMPLX': DCMPLX, Double complex conversion function ! * 'DIGITS': DIGITS, Significant digits function ! * 'DIM': DIM, Positive difference ! * 'DOT_PRODUCT': DOT_PRODUCT, Dot product function ! * 'DPROD': DPROD, Double product function ! * 'DREAL': DREAL, Double real part function ! * 'DSHIFTL': DSHIFTL, Combined left shift ! * 'DSHIFTR': DSHIFTR, Combined right shift ! * 'DTIME': DTIME, Execution time subroutine (or function) ! * 'EOSHIFT': EOSHIFT, End-off shift elements of an array ! * 'EPSILON': EPSILON, Epsilon function ! * 'ERF': ERF, Error function ! * 'ERFC': ERFC, Complementary error function ! * 'ERFC_SCALED': ERFC_SCALED, Exponentially-scaled complementary error function ! * 'ETIME': ETIME, Execution time subroutine (or function) ! * 'EVENT_QUERY': EVENT_QUERY, Query whether a coarray event has occurred ! * 'EXECUTE_COMMAND_LINE': EXECUTE_COMMAND_LINE, Execute a shell command ! * 'EXIT': EXIT, Exit the program with status. ! * 'EXP': EXP, Exponential function ! * 'EXPONENT': EXPONENT, Exponent function ! * 'EXTENDS_TYPE_OF': EXTENDS_TYPE_OF, Query dynamic type for extension ! * 'FDATE': FDATE, Subroutine (or function) to get the current time as a string ! * 'FGET': FGET, Read a single character in stream mode from stdin ! * 'FGETC': FGETC, Read a single character in stream mode ! * 'FLOOR': FLOOR, Integer floor function ! * 'FLUSH': FLUSH, Flush I/O unit(s) ! * 'FNUM': FNUM, File number function ! * 'FPUT': FPUT, Write a single character in stream mode to stdout ! * 'FPUTC': FPUTC, Write a single character in stream mode ! * 'FRACTION': FRACTION, Fractional part of the model representation ! * 'FREE': FREE, Memory de-allocation subroutine ! * 'FSEEK': FSEEK, Low level file positioning subroutine ! * 'FSTAT': FSTAT, Get file status ! * 'FTELL': FTELL, Current stream position ! * 'GAMMA': GAMMA, Gamma function ! * 'GERROR': GERROR, Get last system error message ! * 'GETARG': GETARG, Get command line arguments ! * 'GET_COMMAND': GET_COMMAND, Get the entire command line ! * 'GET_COMMAND_ARGUMENT': GET_COMMAND_ARGUMENT, Get command line arguments ! * 'GETCWD': GETCWD, Get current working directory ! * 'GETENV': GETENV, Get an environmental variable ! * 'GET_ENVIRONMENT_VARIABLE': GET_ENVIRONMENT_VARIABLE, Get an environmental variable ! * 'GETGID': GETGID, Group ID function ! * 'GETLOG': GETLOG, Get login name ! * 'GETPID': GETPID, Process ID function ! * 'GETUID': GETUID, User ID function ! * 'GMTIME': GMTIME, Convert time to GMT info ! * 'HOSTNM': HOSTNM, Get system host name ! * 'HUGE': HUGE, Largest number of a kind ! * 'HYPOT': HYPOT, Euclidean distance function ! * 'IACHAR': IACHAR, Code in ASCII collating sequence ! * 'IALL': IALL, Bitwise AND of array elements ! * 'IAND': IAND, Bitwise logical and ! * 'IANY': IANY, Bitwise OR of array elements ! * 'IARGC': IARGC, Get the number of command line arguments ! * 'IBCLR': IBCLR, Clear bit ! * 'IBITS': IBITS, Bit extraction ! * 'IBSET': IBSET, Set bit ! * 'ICHAR': ICHAR, Character-to-integer conversion function ! * 'IDATE': IDATE, Current local time (day/month/year) ! * 'IEOR': IEOR, Bitwise logical exclusive or ! * 'IERRNO': IERRNO, Function to get the last system error number ! * 'IMAGE_INDEX': IMAGE_INDEX, Cosubscript to image index conversion ! * 'INDEX': INDEX intrinsic, Position of a substring within a string ! * 'INT': INT, Convert to integer type ! * 'INT2': INT2, Convert to 16-bit integer type ! * 'INT8': INT8, Convert to 64-bit integer type ! * 'IOR': IOR, Bitwise logical or ! * 'IPARITY': IPARITY, Bitwise XOR of array elements ! * 'IRAND': IRAND, Integer pseudo-random number ! * 'IS_IOSTAT_END': IS_IOSTAT_END, Test for end-of-file value ! * 'IS_IOSTAT_EOR': IS_IOSTAT_EOR, Test for end-of-record value ! * 'ISATTY': ISATTY, Whether a unit is a terminal device ! * 'ISHFT': ISHFT, Shift bits ! * 'ISHFTC': ISHFTC, Shift bits circularly ! * 'ISNAN': ISNAN, Tests for a NaN ! * 'ITIME': ITIME, Current local time (hour/minutes/seconds) ! * 'KILL': KILL, Send a signal to a process ! * 'KIND': KIND, Kind of an entity ! * 'LBOUND': LBOUND, Lower dimension bounds of an array ! * 'LCOBOUND': LCOBOUND, Lower codimension bounds of an array ! * 'LEADZ': LEADZ, Number of leading zero bits of an integer ! * 'LEN': LEN, Length of a character entity ! * 'LEN_TRIM': LEN_TRIM, Length of a character entity without trailing blank characters ! * 'LGE': LGE, Lexical greater than or equal ! * 'LGT': LGT, Lexical greater than ! * 'LINK': LINK, Create a hard link ! * 'LLE': LLE, Lexical less than or equal ! * 'LLT': LLT, Lexical less than ! * 'LNBLNK': LNBLNK, Index of the last non-blank character in a string ! * 'LOC': LOC, Returns the address of a variable ! * 'LOG': LOG, Logarithm function ! * 'LOG10': LOG10, Base 10 logarithm function ! * 'LOG_GAMMA': LOG_GAMMA, Logarithm of the Gamma function ! * 'LOGICAL': LOGICAL, Convert to logical type ! * 'LONG': LONG, Convert to integer type ! * 'LSHIFT': LSHIFT, Left shift bits ! * 'LSTAT': LSTAT, Get file status ! * 'LTIME': LTIME, Convert time to local time info ! * 'MALLOC': MALLOC, Dynamic memory allocation function ! * 'MASKL': MASKL, Left justified mask ! * 'MASKR': MASKR, Right justified mask ! * 'MATMUL': MATMUL, matrix multiplication ! * 'MAX': MAX, Maximum value of an argument list ! * 'MAXEXPONENT': MAXEXPONENT, Maximum exponent of a real kind ! * 'MAXLOC': MAXLOC, Location of the maximum value within an array ! * 'MAXVAL': MAXVAL, Maximum value of an array ! * 'MCLOCK': MCLOCK, Time function ! * 'MCLOCK8': MCLOCK8, Time function (64-bit) ! * 'MERGE': MERGE, Merge arrays ! * 'MERGE_BITS': MERGE_BITS, Merge of bits under mask ! * 'MIN': MIN, Minimum value of an argument list ! * 'MINEXPONENT': MINEXPONENT, Minimum exponent of a real kind ! * 'MINLOC': MINLOC, Location of the minimum value within an array ! * 'MINVAL': MINVAL, Minimum value of an array ! * 'MOD': MOD, Remainder function ! * 'MODULO': MODULO, Modulo function ! * 'MOVE_ALLOC': MOVE_ALLOC, Move allocation from one object to another ! * 'MVBITS': MVBITS, Move bits from one integer to another ! * 'NEAREST': NEAREST, Nearest representable number ! * 'NEW_LINE': NEW_LINE, New line character ! * 'NINT': NINT, Nearest whole number ! * 'NORM2': NORM2, Euclidean vector norm ! * 'NOT': NOT, Logical negation ! * 'NULL': NULL, Function that returns an disassociated pointer ! * 'NUM_IMAGES': NUM_IMAGES, Number of images ! * 'OR': OR, Bitwise logical OR ! * 'PACK': PACK, Pack an array into an array of rank one ! * 'PARITY': PARITY, Reduction with exclusive OR ! * 'PERROR': PERROR, Print system error message ! * 'POPCNT': POPCNT, Number of bits set ! * 'POPPAR': POPPAR, Parity of the number of bits set ! * 'PRECISION': PRECISION, Decimal precision of a real kind ! * 'PRESENT': PRESENT, Determine whether an optional dummy argument is specified ! * 'PRODUCT': PRODUCT, Product of array elements ! * 'RADIX': RADIX, Base of a data model ! * 'RAN': RAN, Real pseudo-random number ! * 'RAND': RAND, Real pseudo-random number ! * 'RANDOM_NUMBER': RANDOM_NUMBER, Pseudo-random number ! * 'RANDOM_SEED': RANDOM_SEED, Initialize a pseudo-random number sequence ! * 'RANGE': RANGE, Decimal exponent range ! * 'RANK' : RANK, Rank of a data object ! * 'REAL': REAL, Convert to real type ! * 'RENAME': RENAME, Rename a file ! * 'REPEAT': REPEAT, Repeated string concatenation ! * 'RESHAPE': RESHAPE, Function to reshape an array ! * 'RRSPACING': RRSPACING, Reciprocal of the relative spacing ! * 'RSHIFT': RSHIFT, Right shift bits ! * 'SAME_TYPE_AS': SAME_TYPE_AS, Query dynamic types for equality ! * 'SCALE': SCALE, Scale a real value ! * 'SCAN': SCAN, Scan a string for the presence of a set of characters ! * 'SECNDS': SECNDS, Time function ! * 'SECOND': SECOND, CPU time function ! * 'SELECTED_CHAR_KIND': SELECTED_CHAR_KIND, Choose character kind ! * 'SELECTED_INT_KIND': SELECTED_INT_KIND, Choose integer kind ! * 'SELECTED_REAL_KIND': SELECTED_REAL_KIND, Choose real kind ! * 'SET_EXPONENT': SET_EXPONENT, Set the exponent of the model ! * 'SHAPE': SHAPE, Determine the shape of an array ! * 'SHIFTA': SHIFTA, Right shift with fill ! * 'SHIFTL': SHIFTL, Left shift ! * 'SHIFTR': SHIFTR, Right shift ! * 'SIGN': SIGN, Sign copying function ! * 'SIGNAL': SIGNAL, Signal handling subroutine (or function) ! * 'SIN': SIN, Sine function ! * 'SINH': SINH, Hyperbolic sine function ! * 'SIZE': SIZE, Function to determine the size of an array ! * 'SIZEOF': SIZEOF, Determine the size in bytes of an expression ! * 'SLEEP': SLEEP, Sleep for the specified number of seconds ! * 'SPACING': SPACING, Smallest distance between two numbers of a given type ! * 'SPREAD': SPREAD, Add a dimension to an array ! * 'SQRT': SQRT, Square-root function ! * 'SRAND': SRAND, Reinitialize the random number generator ! * 'STAT': STAT, Get file status ! * 'STORAGE_SIZE': STORAGE_SIZE, Storage size in bits ! * 'SUM': SUM, Sum of array elements ! * 'SYMLNK': SYMLNK, Create a symbolic link ! * 'SYSTEM': SYSTEM, Execute a shell command ! * 'SYSTEM_CLOCK': SYSTEM_CLOCK, Time function ! * 'TAN': TAN, Tangent function ! * 'TANH': TANH, Hyperbolic tangent function ! * 'THIS_IMAGE': THIS_IMAGE, Cosubscript index of this image ! * 'TIME': TIME, Time function ! * 'TIME8': TIME8, Time function (64-bit) ! * 'TINY': TINY, Smallest positive number of a real kind ! * 'TRAILZ': TRAILZ, Number of trailing zero bits of an integer ! * 'TRANSFER': TRANSFER, Transfer bit patterns ! * 'TRANSPOSE': TRANSPOSE, Transpose an array of rank two ! * 'TRIM': TRIM, Remove trailing blank characters of a string ! * 'TTYNAM': TTYNAM, Get the name of a terminal device. ! * 'UBOUND': UBOUND, Upper dimension bounds of an array ! * 'UCOBOUND': UCOBOUND, Upper codimension bounds of an array ! * 'UMASK': UMASK, Set the file creation mask ! * 'UNLINK': UNLINK, Remove a file from the file system ! * 'UNPACK': UNPACK, Unpack an array of rank one into an array ! * 'VERIFY': VERIFY, Scan a string for the absence of a set of characters ! * 'XOR': XOR, Bitwise logical exclusive or  File: gfortran.info, Node: Introduction to Intrinsics, Next: ABORT, Up: Intrinsic Procedures --- 5557,5833 ---- * Menu: * Introduction: Introduction to Intrinsics ! * `ABORT': ABORT, Abort the program ! * `ABS': ABS, Absolute value ! * `ACCESS': ACCESS, Checks file access modes ! * `ACHAR': ACHAR, Character in ASCII collating sequence ! * `ACOS': ACOS, Arccosine function ! * `ACOSH': ACOSH, Inverse hyperbolic cosine function ! * `ADJUSTL': ADJUSTL, Left adjust a string ! * `ADJUSTR': ADJUSTR, Right adjust a string ! * `AIMAG': AIMAG, Imaginary part of complex number ! * `AINT': AINT, Truncate to a whole number ! * `ALARM': ALARM, Set an alarm clock ! * `ALL': ALL, Determine if all values are true ! * `ALLOCATED': ALLOCATED, Status of allocatable entity ! * `AND': AND, Bitwise logical AND ! * `ANINT': ANINT, Nearest whole number ! * `ANY': ANY, Determine if any values are true ! * `ASIN': ASIN, Arcsine function ! * `ASINH': ASINH, Inverse hyperbolic sine function ! * `ASSOCIATED': ASSOCIATED, Status of a pointer or pointer/target pair ! * `ATAN': ATAN, Arctangent function ! * `ATAN2': ATAN2, Arctangent function ! * `ATANH': ATANH, Inverse hyperbolic tangent function ! * `ATOMIC_ADD': ATOMIC_ADD, Atomic ADD operation ! * `ATOMIC_AND': ATOMIC_AND, Atomic bitwise AND operation ! * `ATOMIC_CAS': ATOMIC_CAS, Atomic compare and swap ! * `ATOMIC_DEFINE': ATOMIC_DEFINE, Setting a variable atomically ! * `ATOMIC_FETCH_ADD': ATOMIC_FETCH_ADD, Atomic ADD operation with prior fetch ! * `ATOMIC_FETCH_AND': ATOMIC_FETCH_AND, Atomic bitwise AND operation with prior fetch ! * `ATOMIC_FETCH_OR': ATOMIC_FETCH_OR, Atomic bitwise OR operation with prior fetch ! * `ATOMIC_FETCH_XOR': ATOMIC_FETCH_XOR, Atomic bitwise XOR operation with prior fetch ! * `ATOMIC_OR': ATOMIC_OR, Atomic bitwise OR operation ! * `ATOMIC_REF': ATOMIC_REF, Obtaining the value of a variable atomically ! * `ATOMIC_XOR': ATOMIC_XOR, Atomic bitwise OR operation ! * `BACKTRACE': BACKTRACE, Show a backtrace ! * `BESSEL_J0': BESSEL_J0, Bessel function of the first kind of order 0 ! * `BESSEL_J1': BESSEL_J1, Bessel function of the first kind of order 1 ! * `BESSEL_JN': BESSEL_JN, Bessel function of the first kind ! * `BESSEL_Y0': BESSEL_Y0, Bessel function of the second kind of order 0 ! * `BESSEL_Y1': BESSEL_Y1, Bessel function of the second kind of order 1 ! * `BESSEL_YN': BESSEL_YN, Bessel function of the second kind ! * `BGE': BGE, Bitwise greater than or equal to ! * `BGT': BGT, Bitwise greater than ! * `BIT_SIZE': BIT_SIZE, Bit size inquiry function ! * `BLE': BLE, Bitwise less than or equal to ! * `BLT': BLT, Bitwise less than ! * `BTEST': BTEST, Bit test function ! * `C_ASSOCIATED': C_ASSOCIATED, Status of a C pointer ! * `C_F_POINTER': C_F_POINTER, Convert C into Fortran pointer ! * `C_F_PROCPOINTER': C_F_PROCPOINTER, Convert C into Fortran procedure pointer ! * `C_FUNLOC': C_FUNLOC, Obtain the C address of a procedure ! * `C_LOC': C_LOC, Obtain the C address of an object ! * `C_SIZEOF': C_SIZEOF, Size in bytes of an expression ! * `CEILING': CEILING, Integer ceiling function ! * `CHAR': CHAR, Integer-to-character conversion function ! * `CHDIR': CHDIR, Change working directory ! * `CHMOD': CHMOD, Change access permissions of files ! * `CMPLX': CMPLX, Complex conversion function ! * `CO_BROADCAST': CO_BROADCAST, Copy a value to all images the current set of images ! * `CO_MAX': CO_MAX, Maximal value on the current set of images ! * `CO_MIN': CO_MIN, Minimal value on the current set of images ! * `CO_REDUCE': CO_REDUCE, Reduction of values on the current set of images ! * `CO_SUM': CO_SUM, Sum of values on the current set of images ! * `COMMAND_ARGUMENT_COUNT': COMMAND_ARGUMENT_COUNT, Get number of command line arguments ! * `COMPILER_OPTIONS': COMPILER_OPTIONS, Options passed to the compiler ! * `COMPILER_VERSION': COMPILER_VERSION, Compiler version string ! * `COMPLEX': COMPLEX, Complex conversion function ! * `CONJG': CONJG, Complex conjugate function ! * `COS': COS, Cosine function ! * `COSH': COSH, Hyperbolic cosine function ! * `COUNT': COUNT, Count occurrences of TRUE in an array ! * `CPU_TIME': CPU_TIME, CPU time subroutine ! * `CSHIFT': CSHIFT, Circular shift elements of an array ! * `CTIME': CTIME, Subroutine (or function) to convert a time into a string ! * `DATE_AND_TIME': DATE_AND_TIME, Date and time subroutine ! * `DBLE': DBLE, Double precision conversion function ! * `DCMPLX': DCMPLX, Double complex conversion function ! * `DIGITS': DIGITS, Significant digits function ! * `DIM': DIM, Positive difference ! * `DOT_PRODUCT': DOT_PRODUCT, Dot product function ! * `DPROD': DPROD, Double product function ! * `DREAL': DREAL, Double real part function ! * `DSHIFTL': DSHIFTL, Combined left shift ! * `DSHIFTR': DSHIFTR, Combined right shift ! * `DTIME': DTIME, Execution time subroutine (or function) ! * `EOSHIFT': EOSHIFT, End-off shift elements of an array ! * `EPSILON': EPSILON, Epsilon function ! * `ERF': ERF, Error function ! * `ERFC': ERFC, Complementary error function ! * `ERFC_SCALED': ERFC_SCALED, Exponentially-scaled complementary error function ! * `ETIME': ETIME, Execution time subroutine (or function) ! * `EVENT_QUERY': EVENT_QUERY, Query whether a coarray event has occurred ! * `EXECUTE_COMMAND_LINE': EXECUTE_COMMAND_LINE, Execute a shell command ! * `EXIT': EXIT, Exit the program with status. ! * `EXP': EXP, Exponential function ! * `EXPONENT': EXPONENT, Exponent function ! * `EXTENDS_TYPE_OF': EXTENDS_TYPE_OF, Query dynamic type for extension ! * `FDATE': FDATE, Subroutine (or function) to get the current time as a string ! * `FGET': FGET, Read a single character in stream mode from stdin ! * `FGETC': FGETC, Read a single character in stream mode ! * `FLOOR': FLOOR, Integer floor function ! * `FLUSH': FLUSH, Flush I/O unit(s) ! * `FNUM': FNUM, File number function ! * `FPUT': FPUT, Write a single character in stream mode to stdout ! * `FPUTC': FPUTC, Write a single character in stream mode ! * `FRACTION': FRACTION, Fractional part of the model representation ! * `FREE': FREE, Memory de-allocation subroutine ! * `FSEEK': FSEEK, Low level file positioning subroutine ! * `FSTAT': FSTAT, Get file status ! * `FTELL': FTELL, Current stream position ! * `GAMMA': GAMMA, Gamma function ! * `GERROR': GERROR, Get last system error message ! * `GETARG': GETARG, Get command line arguments ! * `GET_COMMAND': GET_COMMAND, Get the entire command line ! * `GET_COMMAND_ARGUMENT': GET_COMMAND_ARGUMENT, Get command line arguments ! * `GETCWD': GETCWD, Get current working directory ! * `GETENV': GETENV, Get an environmental variable ! * `GET_ENVIRONMENT_VARIABLE': GET_ENVIRONMENT_VARIABLE, Get an environmental variable ! * `GETGID': GETGID, Group ID function ! * `GETLOG': GETLOG, Get login name ! * `GETPID': GETPID, Process ID function ! * `GETUID': GETUID, User ID function ! * `GMTIME': GMTIME, Convert time to GMT info ! * `HOSTNM': HOSTNM, Get system host name ! * `HUGE': HUGE, Largest number of a kind ! * `HYPOT': HYPOT, Euclidean distance function ! * `IACHAR': IACHAR, Code in ASCII collating sequence ! * `IALL': IALL, Bitwise AND of array elements ! * `IAND': IAND, Bitwise logical and ! * `IANY': IANY, Bitwise OR of array elements ! * `IARGC': IARGC, Get the number of command line arguments ! * `IBCLR': IBCLR, Clear bit ! * `IBITS': IBITS, Bit extraction ! * `IBSET': IBSET, Set bit ! * `ICHAR': ICHAR, Character-to-integer conversion function ! * `IDATE': IDATE, Current local time (day/month/year) ! * `IEOR': IEOR, Bitwise logical exclusive or ! * `IERRNO': IERRNO, Function to get the last system error number ! * `IMAGE_INDEX': IMAGE_INDEX, Cosubscript to image index conversion ! * `INDEX': INDEX intrinsic, Position of a substring within a string ! * `INT': INT, Convert to integer type ! * `INT2': INT2, Convert to 16-bit integer type ! * `INT8': INT8, Convert to 64-bit integer type ! * `IOR': IOR, Bitwise logical or ! * `IPARITY': IPARITY, Bitwise XOR of array elements ! * `IRAND': IRAND, Integer pseudo-random number ! * `IS_IOSTAT_END': IS_IOSTAT_END, Test for end-of-file value ! * `IS_IOSTAT_EOR': IS_IOSTAT_EOR, Test for end-of-record value ! * `ISATTY': ISATTY, Whether a unit is a terminal device ! * `ISHFT': ISHFT, Shift bits ! * `ISHFTC': ISHFTC, Shift bits circularly ! * `ISNAN': ISNAN, Tests for a NaN ! * `ITIME': ITIME, Current local time (hour/minutes/seconds) ! * `KILL': KILL, Send a signal to a process ! * `KIND': KIND, Kind of an entity ! * `LBOUND': LBOUND, Lower dimension bounds of an array ! * `LCOBOUND': LCOBOUND, Lower codimension bounds of an array ! * `LEADZ': LEADZ, Number of leading zero bits of an integer ! * `LEN': LEN, Length of a character entity ! * `LEN_TRIM': LEN_TRIM, Length of a character entity without trailing blank characters ! * `LGE': LGE, Lexical greater than or equal ! * `LGT': LGT, Lexical greater than ! * `LINK': LINK, Create a hard link ! * `LLE': LLE, Lexical less than or equal ! * `LLT': LLT, Lexical less than ! * `LNBLNK': LNBLNK, Index of the last non-blank character in a string ! * `LOC': LOC, Returns the address of a variable ! * `LOG': LOG, Logarithm function ! * `LOG10': LOG10, Base 10 logarithm function ! * `LOG_GAMMA': LOG_GAMMA, Logarithm of the Gamma function ! * `LOGICAL': LOGICAL, Convert to logical type ! * `LONG': LONG, Convert to integer type ! * `LSHIFT': LSHIFT, Left shift bits ! * `LSTAT': LSTAT, Get file status ! * `LTIME': LTIME, Convert time to local time info ! * `MALLOC': MALLOC, Dynamic memory allocation function ! * `MASKL': MASKL, Left justified mask ! * `MASKR': MASKR, Right justified mask ! * `MATMUL': MATMUL, matrix multiplication ! * `MAX': MAX, Maximum value of an argument list ! * `MAXEXPONENT': MAXEXPONENT, Maximum exponent of a real kind ! * `MAXLOC': MAXLOC, Location of the maximum value within an array ! * `MAXVAL': MAXVAL, Maximum value of an array ! * `MCLOCK': MCLOCK, Time function ! * `MCLOCK8': MCLOCK8, Time function (64-bit) ! * `MERGE': MERGE, Merge arrays ! * `MERGE_BITS': MERGE_BITS, Merge of bits under mask ! * `MIN': MIN, Minimum value of an argument list ! * `MINEXPONENT': MINEXPONENT, Minimum exponent of a real kind ! * `MINLOC': MINLOC, Location of the minimum value within an array ! * `MINVAL': MINVAL, Minimum value of an array ! * `MOD': MOD, Remainder function ! * `MODULO': MODULO, Modulo function ! * `MOVE_ALLOC': MOVE_ALLOC, Move allocation from one object to another ! * `MVBITS': MVBITS, Move bits from one integer to another ! * `NEAREST': NEAREST, Nearest representable number ! * `NEW_LINE': NEW_LINE, New line character ! * `NINT': NINT, Nearest whole number ! * `NORM2': NORM2, Euclidean vector norm ! * `NOT': NOT, Logical negation ! * `NULL': NULL, Function that returns an disassociated pointer ! * `NUM_IMAGES': NUM_IMAGES, Number of images ! * `OR': OR, Bitwise logical OR ! * `PACK': PACK, Pack an array into an array of rank one ! * `PARITY': PARITY, Reduction with exclusive OR ! * `PERROR': PERROR, Print system error message ! * `POPCNT': POPCNT, Number of bits set ! * `POPPAR': POPPAR, Parity of the number of bits set ! * `PRECISION': PRECISION, Decimal precision of a real kind ! * `PRESENT': PRESENT, Determine whether an optional dummy argument is specified ! * `PRODUCT': PRODUCT, Product of array elements ! * `RADIX': RADIX, Base of a data model ! * `RAN': RAN, Real pseudo-random number ! * `RAND': RAND, Real pseudo-random number ! * `RANDOM_NUMBER': RANDOM_NUMBER, Pseudo-random number ! * `RANDOM_SEED': RANDOM_SEED, Initialize a pseudo-random number sequence ! * `RANGE': RANGE, Decimal exponent range ! * `RANK' : RANK, Rank of a data object ! * `REAL': REAL, Convert to real type ! * `RENAME': RENAME, Rename a file ! * `REPEAT': REPEAT, Repeated string concatenation ! * `RESHAPE': RESHAPE, Function to reshape an array ! * `RRSPACING': RRSPACING, Reciprocal of the relative spacing ! * `RSHIFT': RSHIFT, Right shift bits ! * `SAME_TYPE_AS': SAME_TYPE_AS, Query dynamic types for equality ! * `SCALE': SCALE, Scale a real value ! * `SCAN': SCAN, Scan a string for the presence of a set of characters ! * `SECNDS': SECNDS, Time function ! * `SECOND': SECOND, CPU time function ! * `SELECTED_CHAR_KIND': SELECTED_CHAR_KIND, Choose character kind ! * `SELECTED_INT_KIND': SELECTED_INT_KIND, Choose integer kind ! * `SELECTED_REAL_KIND': SELECTED_REAL_KIND, Choose real kind ! * `SET_EXPONENT': SET_EXPONENT, Set the exponent of the model ! * `SHAPE': SHAPE, Determine the shape of an array ! * `SHIFTA': SHIFTA, Right shift with fill ! * `SHIFTL': SHIFTL, Left shift ! * `SHIFTR': SHIFTR, Right shift ! * `SIGN': SIGN, Sign copying function ! * `SIGNAL': SIGNAL, Signal handling subroutine (or function) ! * `SIN': SIN, Sine function ! * `SINH': SINH, Hyperbolic sine function ! * `SIZE': SIZE, Function to determine the size of an array ! * `SIZEOF': SIZEOF, Determine the size in bytes of an expression ! * `SLEEP': SLEEP, Sleep for the specified number of seconds ! * `SPACING': SPACING, Smallest distance between two numbers of a given type ! * `SPREAD': SPREAD, Add a dimension to an array ! * `SQRT': SQRT, Square-root function ! * `SRAND': SRAND, Reinitialize the random number generator ! * `STAT': STAT, Get file status ! * `STORAGE_SIZE': STORAGE_SIZE, Storage size in bits ! * `SUM': SUM, Sum of array elements ! * `SYMLNK': SYMLNK, Create a symbolic link ! * `SYSTEM': SYSTEM, Execute a shell command ! * `SYSTEM_CLOCK': SYSTEM_CLOCK, Time function ! * `TAN': TAN, Tangent function ! * `TANH': TANH, Hyperbolic tangent function ! * `THIS_IMAGE': THIS_IMAGE, Cosubscript index of this image ! * `TIME': TIME, Time function ! * `TIME8': TIME8, Time function (64-bit) ! * `TINY': TINY, Smallest positive number of a real kind ! * `TRAILZ': TRAILZ, Number of trailing zero bits of an integer ! * `TRANSFER': TRANSFER, Transfer bit patterns ! * `TRANSPOSE': TRANSPOSE, Transpose an array of rank two ! * `TRIM': TRIM, Remove trailing blank characters of a string ! * `TTYNAM': TTYNAM, Get the name of a terminal device. ! * `UBOUND': UBOUND, Upper dimension bounds of an array ! * `UCOBOUND': UCOBOUND, Upper codimension bounds of an array ! * `UMASK': UMASK, Set the file creation mask ! * `UNLINK': UNLINK, Remove a file from the file system ! * `UNPACK': UNPACK, Unpack an array of rank one into an array ! * `VERIFY': VERIFY, Scan a string for the absence of a set of characters ! * `XOR': XOR, Bitwise logical exclusive or  File: gfortran.info, Node: Introduction to Intrinsics, Next: ABORT, Up: Intrinsic Procedures *************** either the Fortran 95 standard, the Fort *** 5795,5838 **** 2008 standard is unintentional, and the standard(s) should be considered authoritative. ! The enumeration of the 'KIND' type parameter is processor defined in the Fortran 95 standard. GNU Fortran defines the default integer type ! and default real type by 'INTEGER(KIND=4)' and 'REAL(KIND=4)', respectively. The standard mandates that both data types shall have another kind, which have more precision. On typical target ! architectures supported by 'gfortran', this kind type parameter is ! 'KIND=8'. Hence, 'REAL(KIND=8)' and 'DOUBLE PRECISION' are equivalent. In the description of generic intrinsic procedures, the kind type ! parameter will be specified by 'KIND=*', and in the description of specific names for an intrinsic procedure the kind type parameter will ! be explicitly given (e.g., 'REAL(KIND=4)' or 'REAL(KIND=8)'). Finally, ! for brevity the optional 'KIND=' syntax will be omitted. Many of the intrinsic procedures take one or more optional arguments. This document follows the convention used in the Fortran 95 standard, and denotes such arguments by square brackets. ! GNU Fortran offers the '-std=f95' and '-std=gnu' options, which can ! be used to restrict the set of intrinsic procedures to a given standard. ! By default, 'gfortran' sets the '-std=gnu' option, and so all intrinsic ! procedures described here are accepted. There is one caveat. For a ! select group of intrinsic procedures, 'g77' implemented both a function ! and a subroutine. Both classes have been implemented in 'gfortran' for ! backwards compatibility with 'g77'. It is noted here that these ! functions and subroutines cannot be intermixed in a given subprogram. ! In the descriptions that follow, the applicable standard for each ! intrinsic procedure is noted.  File: gfortran.info, Node: ABORT, Next: ABS, Prev: Introduction to Intrinsics, Up: Intrinsic Procedures ! 9.2 'ABORT' -- Abort the program ================================ _Description_: ! 'ABORT' causes immediate termination of the program. On operating ! systems that support a core dump, 'ABORT' will produce a core dump. ! It will also print a backtrace, unless '-fno-backtrace' is given. _Standard_: GNU extension --- 5844,5887 ---- 2008 standard is unintentional, and the standard(s) should be considered authoritative. ! The enumeration of the `KIND' type parameter is processor defined in the Fortran 95 standard. GNU Fortran defines the default integer type ! and default real type by `INTEGER(KIND=4)' and `REAL(KIND=4)', respectively. The standard mandates that both data types shall have another kind, which have more precision. On typical target ! architectures supported by `gfortran', this kind type parameter is ! `KIND=8'. Hence, `REAL(KIND=8)' and `DOUBLE PRECISION' are equivalent. In the description of generic intrinsic procedures, the kind type ! parameter will be specified by `KIND=*', and in the description of specific names for an intrinsic procedure the kind type parameter will ! be explicitly given (e.g., `REAL(KIND=4)' or `REAL(KIND=8)'). Finally, ! for brevity the optional `KIND=' syntax will be omitted. Many of the intrinsic procedures take one or more optional arguments. This document follows the convention used in the Fortran 95 standard, and denotes such arguments by square brackets. ! GNU Fortran offers the `-std=f95' and `-std=gnu' options, which can ! be used to restrict the set of intrinsic procedures to a given ! standard. By default, `gfortran' sets the `-std=gnu' option, and so ! all intrinsic procedures described here are accepted. There is one ! caveat. For a select group of intrinsic procedures, `g77' implemented ! both a function and a subroutine. Both classes have been implemented ! in `gfortran' for backwards compatibility with `g77'. It is noted here ! that these functions and subroutines cannot be intermixed in a given ! subprogram. In the descriptions that follow, the applicable standard ! for each intrinsic procedure is noted.  File: gfortran.info, Node: ABORT, Next: ABS, Prev: Introduction to Intrinsics, Up: Intrinsic Procedures ! 9.2 `ABORT' -- Abort the program ================================ _Description_: ! `ABORT' causes immediate termination of the program. On operating ! systems that support a core dump, `ABORT' will produce a core dump. ! It will also print a backtrace, unless `-fno-backtrace' is given. _Standard_: GNU extension *************** _Class_: *** 5841,5847 **** Subroutine _Syntax_: ! 'CALL ABORT' _Return value_: Does not return. --- 5890,5896 ---- Subroutine _Syntax_: ! `CALL ABORT' _Return value_: Does not return. *************** _Example_: *** 5855,5868 **** _See also_: *note EXIT::, *note KILL::, *note BACKTRACE::  File: gfortran.info, Node: ABS, Next: ACCESS, Prev: ABORT, Up: Intrinsic Procedures ! 9.3 'ABS' -- Absolute value =========================== _Description_: ! 'ABS(A)' computes the absolute value of 'A'. _Standard_: Fortran 77 and later, has overloads that are GNU extensions --- 5904,5918 ---- _See also_: *note EXIT::, *note KILL::, *note BACKTRACE:: +  File: gfortran.info, Node: ABS, Next: ACCESS, Prev: ABORT, Up: Intrinsic Procedures ! 9.3 `ABS' -- Absolute value =========================== _Description_: ! `ABS(A)' computes the absolute value of `A'. _Standard_: Fortran 77 and later, has overloads that are GNU extensions *************** _Class_: *** 5871,5885 **** Elemental function _Syntax_: ! 'RESULT = ABS(A)' _Arguments_: ! A The type of the argument shall be an 'INTEGER', ! 'REAL', or 'COMPLEX'. _Return value_: The return value is of the same type and kind as the argument ! except the return value is 'REAL' for a 'COMPLEX' argument. _Example_: program test_abs --- 5921,5935 ---- Elemental function _Syntax_: ! `RESULT = ABS(A)' _Arguments_: ! A The type of the argument shall be an `INTEGER', ! `REAL', or `COMPLEX'. _Return value_: The return value is of the same type and kind as the argument ! except the return value is `REAL' for a `COMPLEX' argument. _Example_: program test_abs *************** _Example_: *** 5892,5921 **** end program test_abs _Specific names_: ! Name Argument Return type Standard ! 'ABS(A)' 'REAL(4) A' 'REAL(4)' Fortran 77 and ! later ! 'CABS(A)' 'COMPLEX(4) 'REAL(4)' Fortran 77 and ! A' later ! 'DABS(A)' 'REAL(8) A' 'REAL(8)' Fortran 77 and ! later ! 'IABS(A)' 'INTEGER(4) 'INTEGER(4)' Fortran 77 and ! A' later ! 'ZABS(A)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! A' ! 'CDABS(A)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! A'  File: gfortran.info, Node: ACCESS, Next: ACHAR, Prev: ABS, Up: Intrinsic Procedures ! 9.4 'ACCESS' -- Checks file access modes ======================================== _Description_: ! 'ACCESS(NAME, MODE)' checks whether the file NAME exists, is ! readable, writable or executable. Except for the executable check, ! 'ACCESS' can be replaced by Fortran 95's 'INQUIRE'. _Standard_: GNU extension --- 5942,5971 ---- end program test_abs _Specific names_: ! Name Argument Return type Standard ! `ABS(A)' `REAL(4) A' `REAL(4)' Fortran 77 and ! later ! `CABS(A)' `COMPLEX(4) `REAL(4)' Fortran 77 and ! A' later ! `DABS(A)' `REAL(8) A' `REAL(8)' Fortran 77 and ! later ! `IABS(A)' `INTEGER(4) `INTEGER(4)' Fortran 77 and ! A' later ! `ZABS(A)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! A' ! `CDABS(A)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! A'  File: gfortran.info, Node: ACCESS, Next: ACHAR, Prev: ABS, Up: Intrinsic Procedures ! 9.4 `ACCESS' -- Checks file access modes ======================================== _Description_: ! `ACCESS(NAME, MODE)' checks whether the file NAME exists, is ! readable, writable or executable. Except for the executable check, ! `ACCESS' can be replaced by Fortran 95's `INQUIRE'. _Standard_: GNU extension *************** _Class_: *** 5924,5946 **** Inquiry function _Syntax_: ! 'RESULT = ACCESS(NAME, MODE)' _Arguments_: ! NAME Scalar 'CHARACTER' of default kind with the file ! name. Tailing blank are ignored unless the ! character 'achar(0)' is present, then all ! characters up to and excluding 'achar(0)' are ! used as file name. ! MODE Scalar 'CHARACTER' of default kind with the file ! access mode, may be any concatenation of '"r"' ! (readable), '"w"' (writable) and '"x"' ! (executable), or '" "' to check for existence. _Return value_: ! Returns a scalar 'INTEGER', which is '0' if the file is accessible in the given mode; otherwise or if an invalid argument has been ! given for 'MODE' the value '1' is returned. _Example_: program access_test --- 5974,5996 ---- Inquiry function _Syntax_: ! `RESULT = ACCESS(NAME, MODE)' _Arguments_: ! NAME Scalar `CHARACTER' of default kind with the ! file name. Tailing blank are ignored unless ! the character `achar(0)' is present, then all ! characters up to and excluding `achar(0)' are ! used as file name. ! MODE Scalar `CHARACTER' of default kind with the ! file access mode, may be any concatenation of ! `"r"' (readable), `"w"' (writable) and `"x"' ! (executable), or `" "' to check for existence. _Return value_: ! Returns a scalar `INTEGER', which is `0' if the file is accessible in the given mode; otherwise or if an invalid argument has been ! given for `MODE' the value `1' is returned. _Example_: program access_test *************** _Example_: *** 5954,5970 **** if(access(file2,'rwx') == 0) & print *, trim(file2),' is readable, writable and executable' end program access_test _Specific names_: _See also_:  File: gfortran.info, Node: ACHAR, Next: ACOS, Prev: ACCESS, Up: Intrinsic Procedures ! 9.5 'ACHAR' -- Character in ASCII collating sequence ==================================================== _Description_: ! 'ACHAR(I)' returns the character located at position 'I' in the ASCII collating sequence. _Standard_: --- 6004,6022 ---- if(access(file2,'rwx') == 0) & print *, trim(file2),' is readable, writable and executable' end program access_test + _Specific names_: + _See also_:  File: gfortran.info, Node: ACHAR, Next: ACOS, Prev: ACCESS, Up: Intrinsic Procedures ! 9.5 `ACHAR' -- Character in ASCII collating sequence ==================================================== _Description_: ! `ACHAR(I)' returns the character located at position `I' in the ASCII collating sequence. _Standard_: *************** _Class_: *** 5974,5989 **** Elemental function _Syntax_: ! 'RESULT = ACHAR(I [, KIND])' _Arguments_: ! I The type shall be 'INTEGER'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'CHARACTER' with a length of one. If the KIND argument is present, the return value is of the specified kind and of the default kind otherwise. --- 6026,6041 ---- Elemental function _Syntax_: ! `RESULT = ACHAR(I [, KIND])' _Arguments_: ! I The type shall be `INTEGER'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `CHARACTER' with a length of one. If the KIND argument is present, the return value is of the specified kind and of the default kind otherwise. *************** _Note_: *** 6000,6013 **** _See also_: *note CHAR::, *note IACHAR::, *note ICHAR::  File: gfortran.info, Node: ACOS, Next: ACOSH, Prev: ACHAR, Up: Intrinsic Procedures ! 9.6 'ACOS' -- Arccosine function ================================ _Description_: ! 'ACOS(X)' computes the arccosine of X (inverse of 'COS(X)'). _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later --- 6052,6066 ---- _See also_: *note CHAR::, *note IACHAR::, *note ICHAR:: +  File: gfortran.info, Node: ACOS, Next: ACOSH, Prev: ACHAR, Up: Intrinsic Procedures ! 9.6 `ACOS' -- Arccosine function ================================ _Description_: ! `ACOS(X)' computes the arccosine of X (inverse of `COS(X)'). _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later *************** _Class_: *** 6016,6027 **** Elemental function _Syntax_: ! 'RESULT = ACOS(X)' _Arguments_: ! X The type shall either be 'REAL' with a magnitude ! that is less than or equal to one - or the type ! shall be 'COMPLEX'. _Return value_: The return value is of the same type and kind as X. The real part --- 6069,6080 ---- Elemental function _Syntax_: ! `RESULT = ACOS(X)' _Arguments_: ! X The type shall either be `REAL' with a ! magnitude that is less than or equal to one - ! or the type shall be `COMPLEX'. _Return value_: The return value is of the same type and kind as X. The real part *************** _Example_: *** 6035,6057 **** end program test_acos _Specific names_: ! Name Argument Return type Standard ! 'ACOS(X)' 'REAL(4) X' 'REAL(4)' Fortran 77 and ! later ! 'DACOS(X)' 'REAL(8) X' 'REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note COS::  File: gfortran.info, Node: ACOSH, Next: ADJUSTL, Prev: ACOS, Up: Intrinsic Procedures ! 9.7 'ACOSH' -- Inverse hyperbolic cosine function ================================================= _Description_: ! 'ACOSH(X)' computes the inverse hyperbolic cosine of X. _Standard_: Fortran 2008 and later --- 6088,6111 ---- end program test_acos _Specific names_: ! Name Argument Return type Standard ! `ACOS(X)' `REAL(4) X' `REAL(4)' Fortran 77 and ! later ! `DACOS(X)' `REAL(8) X' `REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note COS:: +  File: gfortran.info, Node: ACOSH, Next: ADJUSTL, Prev: ACOS, Up: Intrinsic Procedures ! 9.7 `ACOSH' -- Inverse hyperbolic cosine function ================================================= _Description_: ! `ACOSH(X)' computes the inverse hyperbolic cosine of X. _Standard_: Fortran 2008 and later *************** _Class_: *** 6060,6073 **** Elemental function _Syntax_: ! 'RESULT = ACOSH(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value has the same type and kind as X. If X is complex, ! the imaginary part of the result is in radians and lies between 0 \leq \Im \acosh(x) \leq \pi. _Example_: --- 6114,6127 ---- Elemental function _Syntax_: ! `RESULT = ACOSH(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value has the same type and kind as X. If X is complex, ! the imaginary part of the result is in radians and lies between 0 \leq \Im \acosh(x) \leq \pi. _Example_: *************** _Example_: *** 6077,6084 **** END PROGRAM _Specific names_: ! Name Argument Return type Standard ! 'DACOSH(X)' 'REAL(8) X' 'REAL(8)' GNU extension _See also_: Inverse function: *note COSH:: --- 6131,6138 ---- END PROGRAM _Specific names_: ! Name Argument Return type Standard ! `DACOSH(X)' `REAL(8) X' `REAL(8)' GNU extension _See also_: Inverse function: *note COSH:: *************** _See also_: *** 6086,6096 ****  File: gfortran.info, Node: ADJUSTL, Next: ADJUSTR, Prev: ACOSH, Up: Intrinsic Procedures ! 9.8 'ADJUSTL' -- Left adjust a string ===================================== _Description_: ! 'ADJUSTL(STRING)' will left adjust a string by removing leading spaces. Spaces are inserted at the end of the string as needed. _Standard_: --- 6140,6150 ----  File: gfortran.info, Node: ADJUSTL, Next: ADJUSTR, Prev: ACOSH, Up: Intrinsic Procedures ! 9.8 `ADJUSTL' -- Left adjust a string ===================================== _Description_: ! `ADJUSTL(STRING)' will left adjust a string by removing leading spaces. Spaces are inserted at the end of the string as needed. _Standard_: *************** _Class_: *** 6100,6112 **** Elemental function _Syntax_: ! 'RESULT = ADJUSTL(STRING)' _Arguments_: ! STRING The type shall be 'CHARACTER'. _Return value_: ! The return value is of type 'CHARACTER' and of the same kind as STRING where leading spaces are removed and the same number of spaces are inserted on the end of STRING. --- 6154,6166 ---- Elemental function _Syntax_: ! `RESULT = ADJUSTL(STRING)' _Arguments_: ! STRING The type shall be `CHARACTER'. _Return value_: ! The return value is of type `CHARACTER' and of the same kind as STRING where leading spaces are removed and the same number of spaces are inserted on the end of STRING. *************** _See also_: *** 6123,6133 ****  File: gfortran.info, Node: ADJUSTR, Next: AIMAG, Prev: ADJUSTL, Up: Intrinsic Procedures ! 9.9 'ADJUSTR' -- Right adjust a string ====================================== _Description_: ! 'ADJUSTR(STRING)' will right adjust a string by removing trailing spaces. Spaces are inserted at the start of the string as needed. _Standard_: --- 6177,6187 ----  File: gfortran.info, Node: ADJUSTR, Next: AIMAG, Prev: ADJUSTL, Up: Intrinsic Procedures ! 9.9 `ADJUSTR' -- Right adjust a string ====================================== _Description_: ! `ADJUSTR(STRING)' will right adjust a string by removing trailing spaces. Spaces are inserted at the start of the string as needed. _Standard_: *************** _Class_: *** 6137,6149 **** Elemental function _Syntax_: ! 'RESULT = ADJUSTR(STRING)' _Arguments_: ! STR The type shall be 'CHARACTER'. _Return value_: ! The return value is of type 'CHARACTER' and of the same kind as STRING where trailing spaces are removed and the same number of spaces are inserted at the start of STRING. --- 6191,6203 ---- Elemental function _Syntax_: ! `RESULT = ADJUSTR(STRING)' _Arguments_: ! STR The type shall be `CHARACTER'. _Return value_: ! The return value is of type `CHARACTER' and of the same kind as STRING where trailing spaces are removed and the same number of spaces are inserted at the start of STRING. *************** _See also_: *** 6160,6172 ****  File: gfortran.info, Node: AIMAG, Next: AINT, Prev: ADJUSTR, Up: Intrinsic Procedures ! 9.10 'AIMAG' -- Imaginary part of complex number ================================================ _Description_: ! 'AIMAG(Z)' yields the imaginary part of complex argument 'Z'. The ! 'IMAG(Z)' and 'IMAGPART(Z)' intrinsic functions are provided for ! compatibility with 'g77', and their use in new code is strongly discouraged. _Standard_: --- 6214,6226 ----  File: gfortran.info, Node: AIMAG, Next: AINT, Prev: ADJUSTR, Up: Intrinsic Procedures ! 9.10 `AIMAG' -- Imaginary part of complex number ================================================ _Description_: ! `AIMAG(Z)' yields the imaginary part of complex argument `Z'. The ! `IMAG(Z)' and `IMAGPART(Z)' intrinsic functions are provided for ! compatibility with `g77', and their use in new code is strongly discouraged. _Standard_: *************** _Class_: *** 6176,6188 **** Elemental function _Syntax_: ! 'RESULT = AIMAG(Z)' _Arguments_: ! Z The type of the argument shall be 'COMPLEX'. _Return value_: ! The return value is of type 'REAL' with the kind type parameter of the argument. _Example_: --- 6230,6242 ---- Elemental function _Syntax_: ! `RESULT = AIMAG(Z)' _Arguments_: ! Z The type of the argument shall be `COMPLEX'. _Return value_: ! The return value is of type `REAL' with the kind type parameter of the argument. _Example_: *************** _Example_: *** 6195,6215 **** end program test_aimag _Specific names_: ! Name Argument Return type Standard ! 'AIMAG(Z)' 'COMPLEX Z' 'REAL' GNU extension ! 'DIMAG(Z)' 'COMPLEX(8) 'REAL(8)' GNU extension ! Z' ! 'IMAG(Z)' 'COMPLEX Z' 'REAL' GNU extension ! 'IMAGPART(Z)' 'COMPLEX Z' 'REAL' GNU extension  File: gfortran.info, Node: AINT, Next: ALARM, Prev: AIMAG, Up: Intrinsic Procedures ! 9.11 'AINT' -- Truncate to a whole number ========================================= _Description_: ! 'AINT(A [, KIND])' truncates its argument to a whole number. _Standard_: Fortran 77 and later --- 6249,6269 ---- end program test_aimag _Specific names_: ! Name Argument Return type Standard ! `AIMAG(Z)' `COMPLEX Z' `REAL' GNU extension ! `DIMAG(Z)' `COMPLEX(8) `REAL(8)' GNU extension ! Z' ! `IMAG(Z)' `COMPLEX Z' `REAL' GNU extension ! `IMAGPART(Z)' `COMPLEX Z' `REAL' GNU extension  File: gfortran.info, Node: AINT, Next: ALARM, Prev: AIMAG, Up: Intrinsic Procedures ! 9.11 `AINT' -- Truncate to a whole number ========================================= _Description_: ! `AINT(A [, KIND])' truncates its argument to a whole number. _Standard_: Fortran 77 and later *************** _Class_: *** 6218,6236 **** Elemental function _Syntax_: ! 'RESULT = AINT(A [, KIND])' _Arguments_: ! A The type of the argument shall be 'REAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'REAL' with the kind type parameter of the argument if the optional KIND is absent; otherwise, the kind type parameter will be given by KIND. If the magnitude of X is ! less than one, 'AINT(X)' returns zero. If the magnitude is equal to or greater than one then it returns the largest whole number that does not exceed its magnitude. The sign is the same as the sign of X. --- 6272,6290 ---- Elemental function _Syntax_: ! `RESULT = AINT(A [, KIND])' _Arguments_: ! A The type of the argument shall be `REAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `REAL' with the kind type parameter of the argument if the optional KIND is absent; otherwise, the kind type parameter will be given by KIND. If the magnitude of X is ! less than one, `AINT(X)' returns zero. If the magnitude is equal to or greater than one then it returns the largest whole number that does not exceed its magnitude. The sign is the same as the sign of X. *************** _Example_: *** 6246,6270 **** end program test_aint _Specific names_: ! Name Argument Return type Standard ! 'AINT(A)' 'REAL(4) A' 'REAL(4)' Fortran 77 and ! later ! 'DINT(A)' 'REAL(8) A' 'REAL(8)' Fortran 77 and ! later  File: gfortran.info, Node: ALARM, Next: ALL, Prev: AINT, Up: Intrinsic Procedures ! 9.12 'ALARM' -- Execute a routine after a given delay ===================================================== _Description_: ! 'ALARM(SECONDS, HANDLER [, STATUS])' causes external subroutine ! HANDLER to be executed after a delay of SECONDS by using 'alarm(2)' ! to set up a signal and 'signal(2)' to catch it. If STATUS is ! supplied, it will be returned with the number of seconds remaining ! until any previously scheduled alarm was due to be delivered, or ! zero if there was no previously scheduled alarm. _Standard_: GNU extension --- 6300,6324 ---- end program test_aint _Specific names_: ! Name Argument Return type Standard ! `AINT(A)' `REAL(4) A' `REAL(4)' Fortran 77 and ! later ! `DINT(A)' `REAL(8) A' `REAL(8)' Fortran 77 and ! later  File: gfortran.info, Node: ALARM, Next: ALL, Prev: AINT, Up: Intrinsic Procedures ! 9.12 `ALARM' -- Execute a routine after a given delay ===================================================== _Description_: ! `ALARM(SECONDS, HANDLER [, STATUS])' causes external subroutine ! HANDLER to be executed after a delay of SECONDS by using ! `alarm(2)' to set up a signal and `signal(2)' to catch it. If ! STATUS is supplied, it will be returned with the number of seconds ! remaining until any previously scheduled alarm was due to be ! delivered, or zero if there was no previously scheduled alarm. _Standard_: GNU extension *************** _Class_: *** 6273,6291 **** Subroutine _Syntax_: ! 'CALL ALARM(SECONDS, HANDLER [, STATUS])' _Arguments_: ! SECONDS The type of the argument shall be a scalar ! 'INTEGER'. It is 'INTENT(IN)'. ! HANDLER Signal handler ('INTEGER FUNCTION' or ! 'SUBROUTINE') or dummy/global 'INTEGER' scalar. ! The scalar values may be either 'SIG_IGN=1' to ! ignore the alarm generated or 'SIG_DFL=0' to set ! the default action. It is 'INTENT(IN)'. ! STATUS (Optional) STATUS shall be a scalar variable of ! the default 'INTEGER' kind. It is ! 'INTENT(OUT)'. _Example_: program test_alarm --- 6327,6346 ---- Subroutine _Syntax_: ! `CALL ALARM(SECONDS, HANDLER [, STATUS])' _Arguments_: ! SECONDS The type of the argument shall be a scalar ! `INTEGER'. It is `INTENT(IN)'. ! HANDLER Signal handler (`INTEGER FUNCTION' or ! `SUBROUTINE') or dummy/global `INTEGER' ! scalar. The scalar values may be either ! `SIG_IGN=1' to ignore the alarm generated or ! `SIG_DFL=0' to set the default action. It is ! `INTENT(IN)'. ! STATUS (Optional) STATUS shall be a scalar variable ! of the default `INTEGER' kind. It is ! `INTENT(OUT)'. _Example_: program test_alarm *************** _Example_: *** 6301,6311 ****  File: gfortran.info, Node: ALL, Next: ALLOCATED, Prev: ALARM, Up: Intrinsic Procedures ! 9.13 'ALL' -- All values in MASK along DIM are true =================================================== _Description_: ! 'ALL(MASK [, DIM])' determines if all the values are true in MASK in the array along dimension DIM. _Standard_: --- 6356,6366 ----  File: gfortran.info, Node: ALL, Next: ALLOCATED, Prev: ALARM, Up: Intrinsic Procedures ! 9.13 `ALL' -- All values in MASK along DIM are true =================================================== _Description_: ! `ALL(MASK [, DIM])' determines if all the values are true in MASK in the array along dimension DIM. _Standard_: *************** _Class_: *** 6315,6343 **** Transformational function _Syntax_: ! 'RESULT = ALL(MASK [, DIM])' _Arguments_: ! MASK The type of the argument shall be 'LOGICAL' and ! it shall not be scalar. ! DIM (Optional) DIM shall be a scalar integer with a ! value that lies between one and the rank of ! MASK. _Return value_: ! 'ALL(MASK)' returns a scalar value of type 'LOGICAL' where the kind ! type parameter is the same as the kind type parameter of MASK. If ! DIM is present, then 'ALL(MASK, DIM)' returns an array with the ! rank of MASK minus 1. The shape is determined from the shape of ! MASK where the DIM dimension is elided. ! (A) ! 'ALL(MASK)' is true if all elements of MASK are true. It also ! is true if MASK has zero size; otherwise, it is false. ! (B) ! If the rank of MASK is one, then 'ALL(MASK,DIM)' is equivalent ! to 'ALL(MASK)'. If the rank is greater than one, then ! 'ALL(MASK,DIM)' is determined by applying 'ALL' to the array sections. _Example_: --- 6370,6399 ---- Transformational function _Syntax_: ! `RESULT = ALL(MASK [, DIM])' _Arguments_: ! MASK The type of the argument shall be `LOGICAL' and ! it shall not be scalar. ! DIM (Optional) DIM shall be a scalar integer with ! a value that lies between one and the rank of ! MASK. _Return value_: ! `ALL(MASK)' returns a scalar value of type `LOGICAL' where the ! kind type parameter is the same as the kind type parameter of ! MASK. If DIM is present, then `ALL(MASK, DIM)' returns an array ! with the rank of MASK minus 1. The shape is determined from the ! shape of MASK where the DIM dimension is elided. ! (A) ! `ALL(MASK)' is true if all elements of MASK are true. It ! also is true if MASK has zero size; otherwise, it is false. ! ! (B) ! If the rank of MASK is one, then `ALL(MASK,DIM)' is equivalent ! to `ALL(MASK)'. If the rank is greater than one, then ! `ALL(MASK,DIM)' is determined by applying `ALL' to the array sections. _Example_: *************** _Example_: *** 6360,6391 ****  File: gfortran.info, Node: ALLOCATED, Next: AND, Prev: ALL, Up: Intrinsic Procedures ! 9.14 'ALLOCATED' -- Status of an allocatable entity =================================================== _Description_: ! 'ALLOCATED(ARRAY)' and 'ALLOCATED(SCALAR)' check the allocation status of ARRAY and SCALAR, respectively. _Standard_: ! Fortran 95 and later. Note, the 'SCALAR=' keyword and allocatable scalar entities are available in Fortran 2003 and later. _Class_: Inquiry function _Syntax_: ! 'RESULT = ALLOCATED(ARRAY)' ! 'RESULT = ALLOCATED(SCALAR)' _Arguments_: ! ARRAY The argument shall be an 'ALLOCATABLE' array. ! SCALAR The argument shall be an 'ALLOCATABLE' scalar. _Return value_: ! The return value is a scalar 'LOGICAL' with the default logical ! kind type parameter. If the argument is allocated, then the result ! is '.TRUE.'; otherwise, it returns '.FALSE.' _Example_: program test_allocated --- 6416,6447 ----  File: gfortran.info, Node: ALLOCATED, Next: AND, Prev: ALL, Up: Intrinsic Procedures ! 9.14 `ALLOCATED' -- Status of an allocatable entity =================================================== _Description_: ! `ALLOCATED(ARRAY)' and `ALLOCATED(SCALAR)' check the allocation status of ARRAY and SCALAR, respectively. _Standard_: ! Fortran 95 and later. Note, the `SCALAR=' keyword and allocatable scalar entities are available in Fortran 2003 and later. _Class_: Inquiry function _Syntax_: ! `RESULT = ALLOCATED(ARRAY)' ! `RESULT = ALLOCATED(SCALAR)' _Arguments_: ! ARRAY The argument shall be an `ALLOCATABLE' array. ! SCALAR The argument shall be an `ALLOCATABLE' scalar. _Return value_: ! The return value is a scalar `LOGICAL' with the default logical ! kind type parameter. If the argument is allocated, then the ! result is `.TRUE.'; otherwise, it returns `.FALSE.' _Example_: program test_allocated *************** _Example_: *** 6397,6407 ****  File: gfortran.info, Node: AND, Next: ANINT, Prev: ALLOCATED, Up: Intrinsic Procedures ! 9.15 'AND' -- Bitwise logical AND ================================= _Description_: ! Bitwise logical 'AND'. This intrinsic routine is provided for backwards compatibility with GNU Fortran 77. For integer arguments, programmers should consider --- 6453,6463 ----  File: gfortran.info, Node: AND, Next: ANINT, Prev: ALLOCATED, Up: Intrinsic Procedures ! 9.15 `AND' -- Bitwise logical AND ================================= _Description_: ! Bitwise logical `AND'. This intrinsic routine is provided for backwards compatibility with GNU Fortran 77. For integer arguments, programmers should consider *************** _Class_: *** 6415,6432 **** Function _Syntax_: ! 'RESULT = AND(I, J)' _Arguments_: ! I The type shall be either a scalar 'INTEGER' type ! or a scalar 'LOGICAL' type. ! J The type shall be the same as the type of I. _Return value_: ! The return type is either a scalar 'INTEGER' or a scalar 'LOGICAL'. ! If the kind type parameters differ, then the smaller kind type is ! implicitly converted to larger kind, and the return has the larger ! kind. _Example_: PROGRAM test_and --- 6471,6488 ---- Function _Syntax_: ! `RESULT = AND(I, J)' _Arguments_: ! I The type shall be either a scalar `INTEGER' ! type or a scalar `LOGICAL' type. ! J The type shall be the same as the type of I. _Return value_: ! The return type is either a scalar `INTEGER' or a scalar ! `LOGICAL'. If the kind type parameters differ, then the smaller ! kind type is implicitly converted to larger kind, and the return ! has the larger kind. _Example_: PROGRAM test_and *************** _See also_: *** 6444,6454 ****  File: gfortran.info, Node: ANINT, Next: ANY, Prev: AND, Up: Intrinsic Procedures ! 9.16 'ANINT' -- Nearest whole number ==================================== _Description_: ! 'ANINT(A [, KIND])' rounds its argument to the nearest whole number. _Standard_: --- 6500,6510 ----  File: gfortran.info, Node: ANINT, Next: ANY, Prev: AND, Up: Intrinsic Procedures ! 9.16 `ANINT' -- Nearest whole number ==================================== _Description_: ! `ANINT(A [, KIND])' rounds its argument to the nearest whole number. _Standard_: *************** _Class_: *** 6458,6477 **** Elemental function _Syntax_: ! 'RESULT = ANINT(A [, KIND])' _Arguments_: ! A The type of the argument shall be 'REAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: The return value is of type real with the kind type parameter of the argument if the optional KIND is absent; otherwise, the kind type parameter will be given by KIND. If A is greater than zero, ! 'ANINT(A)' returns 'AINT(X+0.5)'. If A is less than or equal to ! zero then it returns 'AINT(X-0.5)'. _Example_: program test_anint --- 6514,6533 ---- Elemental function _Syntax_: ! `RESULT = ANINT(A [, KIND])' _Arguments_: ! A The type of the argument shall be `REAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: The return value is of type real with the kind type parameter of the argument if the optional KIND is absent; otherwise, the kind type parameter will be given by KIND. If A is greater than zero, ! `ANINT(A)' returns `AINT(X+0.5)'. If A is less than or equal to ! zero then it returns `AINT(X-0.5)'. _Example_: program test_anint *************** _Example_: *** 6484,6504 **** end program test_anint _Specific names_: ! Name Argument Return type Standard ! 'AINT(A)' 'REAL(4) A' 'REAL(4)' Fortran 77 and ! later ! 'DNINT(A)' 'REAL(8) A' 'REAL(8)' Fortran 77 and ! later  File: gfortran.info, Node: ANY, Next: ASIN, Prev: ANINT, Up: Intrinsic Procedures ! 9.17 'ANY' -- Any value in MASK along DIM is true ================================================= _Description_: ! 'ANY(MASK [, DIM])' determines if any of the values in the logical ! array MASK along dimension DIM are '.TRUE.'. _Standard_: Fortran 95 and later --- 6540,6560 ---- end program test_anint _Specific names_: ! Name Argument Return type Standard ! `AINT(A)' `REAL(4) A' `REAL(4)' Fortran 77 and ! later ! `DNINT(A)' `REAL(8) A' `REAL(8)' Fortran 77 and ! later  File: gfortran.info, Node: ANY, Next: ASIN, Prev: ANINT, Up: Intrinsic Procedures ! 9.17 `ANY' -- Any value in MASK along DIM is true ================================================= _Description_: ! `ANY(MASK [, DIM])' determines if any of the values in the logical ! array MASK along dimension DIM are `.TRUE.'. _Standard_: Fortran 95 and later *************** _Class_: *** 6507,6535 **** Transformational function _Syntax_: ! 'RESULT = ANY(MASK [, DIM])' _Arguments_: ! MASK The type of the argument shall be 'LOGICAL' and ! it shall not be scalar. ! DIM (Optional) DIM shall be a scalar integer with a ! value that lies between one and the rank of ! MASK. _Return value_: ! 'ANY(MASK)' returns a scalar value of type 'LOGICAL' where the kind ! type parameter is the same as the kind type parameter of MASK. If ! DIM is present, then 'ANY(MASK, DIM)' returns an array with the ! rank of MASK minus 1. The shape is determined from the shape of ! MASK where the DIM dimension is elided. ! (A) ! 'ANY(MASK)' is true if any element of MASK is true; otherwise, ! it is false. It also is false if MASK has zero size. ! (B) ! If the rank of MASK is one, then 'ANY(MASK,DIM)' is equivalent ! to 'ANY(MASK)'. If the rank is greater than one, then ! 'ANY(MASK,DIM)' is determined by applying 'ANY' to the array sections. _Example_: --- 6563,6593 ---- Transformational function _Syntax_: ! `RESULT = ANY(MASK [, DIM])' _Arguments_: ! MASK The type of the argument shall be `LOGICAL' and ! it shall not be scalar. ! DIM (Optional) DIM shall be a scalar integer with ! a value that lies between one and the rank of ! MASK. _Return value_: ! `ANY(MASK)' returns a scalar value of type `LOGICAL' where the ! kind type parameter is the same as the kind type parameter of ! MASK. If DIM is present, then `ANY(MASK, DIM)' returns an array ! with the rank of MASK minus 1. The shape is determined from the ! shape of MASK where the DIM dimension is elided. ! (A) ! `ANY(MASK)' is true if any element of MASK is true; ! otherwise, it is false. It also is false if MASK has zero ! size. ! ! (B) ! If the rank of MASK is one, then `ANY(MASK,DIM)' is equivalent ! to `ANY(MASK)'. If the rank is greater than one, then ! `ANY(MASK,DIM)' is determined by applying `ANY' to the array sections. _Example_: *************** _Example_: *** 6552,6562 ****  File: gfortran.info, Node: ASIN, Next: ASINH, Prev: ANY, Up: Intrinsic Procedures ! 9.18 'ASIN' -- Arcsine function =============================== _Description_: ! 'ASIN(X)' computes the arcsine of its X (inverse of 'SIN(X)'). _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later --- 6610,6620 ----  File: gfortran.info, Node: ASIN, Next: ASINH, Prev: ANY, Up: Intrinsic Procedures ! 9.18 `ASIN' -- Arcsine function =============================== _Description_: ! `ASIN(X)' computes the arcsine of its X (inverse of `SIN(X)'). _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later *************** _Class_: *** 6565,6576 **** Elemental function _Syntax_: ! 'RESULT = ASIN(X)' _Arguments_: ! X The type shall be either 'REAL' and a magnitude ! that is less than or equal to one - or be ! 'COMPLEX'. _Return value_: The return value is of the same type and kind as X. The real part --- 6623,6634 ---- Elemental function _Syntax_: ! `RESULT = ASIN(X)' _Arguments_: ! X The type shall be either `REAL' and a ! magnitude that is less than or equal to one - ! or be `COMPLEX'. _Return value_: The return value is of the same type and kind as X. The real part *************** _Example_: *** 6584,6606 **** end program test_asin _Specific names_: ! Name Argument Return type Standard ! 'ASIN(X)' 'REAL(4) X' 'REAL(4)' Fortran 77 and ! later ! 'DASIN(X)' 'REAL(8) X' 'REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note SIN::  File: gfortran.info, Node: ASINH, Next: ASSOCIATED, Prev: ASIN, Up: Intrinsic Procedures ! 9.19 'ASINH' -- Inverse hyperbolic sine function ================================================ _Description_: ! 'ASINH(X)' computes the inverse hyperbolic sine of X. _Standard_: Fortran 2008 and later --- 6642,6665 ---- end program test_asin _Specific names_: ! Name Argument Return type Standard ! `ASIN(X)' `REAL(4) X' `REAL(4)' Fortran 77 and ! later ! `DASIN(X)' `REAL(8) X' `REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note SIN:: +  File: gfortran.info, Node: ASINH, Next: ASSOCIATED, Prev: ASIN, Up: Intrinsic Procedures ! 9.19 `ASINH' -- Inverse hyperbolic sine function ================================================ _Description_: ! `ASINH(X)' computes the inverse hyperbolic sine of X. _Standard_: Fortran 2008 and later *************** _Class_: *** 6609,6621 **** Elemental function _Syntax_: ! 'RESULT = ASINH(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value is of the same type and kind as X. If X is complex, the imaginary part of the result is in radians and lies between -\pi/2 \leq \Im \asinh(x) \leq \pi/2. --- 6668,6680 ---- Elemental function _Syntax_: ! `RESULT = ASINH(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value is of the same type and kind as X. If X is complex, the imaginary part of the result is in radians and lies between -\pi/2 \leq \Im \asinh(x) \leq \pi/2. *************** _Example_: *** 6626,6633 **** END PROGRAM _Specific names_: ! Name Argument Return type Standard ! 'DASINH(X)' 'REAL(8) X' 'REAL(8)' GNU extension. _See also_: Inverse function: *note SINH:: --- 6685,6692 ---- END PROGRAM _Specific names_: ! Name Argument Return type Standard ! `DASINH(X)' `REAL(8) X' `REAL(8)' GNU extension. _See also_: Inverse function: *note SINH:: *************** _See also_: *** 6635,6645 ****  File: gfortran.info, Node: ASSOCIATED, Next: ATAN, Prev: ASINH, Up: Intrinsic Procedures ! 9.20 'ASSOCIATED' -- Status of a pointer or pointer/target pair =============================================================== _Description_: ! 'ASSOCIATED(POINTER [, TARGET])' determines the status of the pointer POINTER or if POINTER is associated with the target TARGET. _Standard_: --- 6694,6704 ----  File: gfortran.info, Node: ASSOCIATED, Next: ATAN, Prev: ASINH, Up: Intrinsic Procedures ! 9.20 `ASSOCIATED' -- Status of a pointer or pointer/target pair =============================================================== _Description_: ! `ASSOCIATED(POINTER [, TARGET])' determines the status of the pointer POINTER or if POINTER is associated with the target TARGET. _Standard_: *************** _Class_: *** 6649,6687 **** Inquiry function _Syntax_: ! 'RESULT = ASSOCIATED(POINTER [, TARGET])' _Arguments_: ! POINTER POINTER shall have the 'POINTER' attribute and ! it can be of any type. ! TARGET (Optional) TARGET shall be a pointer or a ! target. It must have the same type, kind type ! parameter, and array rank as POINTER. The association status of neither POINTER nor TARGET shall be undefined. _Return value_: ! 'ASSOCIATED(POINTER)' returns a scalar value of type 'LOGICAL(4)'. There are several cases: ! (A) When the optional TARGET is not present then ! 'ASSOCIATED(POINTER)' is true if POINTER is associated with a target; otherwise, it returns false. ! (B) If TARGET is present and a scalar target, the result is true if TARGET is not a zero-sized storage sequence and the target associated with POINTER occupies the same storage units. If POINTER is disassociated, the result is false. ! (C) If TARGET is present and an array target, the result is true if TARGET and POINTER have the same shape, are not zero-sized arrays, are arrays whose elements are not zero-sized storage sequences, and TARGET and POINTER occupy the same storage units in array element order. As in case(B), the result is false, if POINTER is disassociated. ! (D) If TARGET is present and an scalar pointer, the result is true if TARGET is associated with POINTER, the target associated with TARGET are not zero-sized storage sequences and occupy ! the same storage units. The result is false, if either TARGET ! or POINTER is disassociated. ! (E) If TARGET is present and an array pointer, the result is true if target associated with POINTER and the target associated with TARGET have the same shape, are not zero-sized arrays, are arrays whose elements are not zero-sized storage sequences, --- 6708,6750 ---- Inquiry function _Syntax_: ! `RESULT = ASSOCIATED(POINTER [, TARGET])' _Arguments_: ! POINTER POINTER shall have the `POINTER' attribute and ! it can be of any type. ! TARGET (Optional) TARGET shall be a pointer or a ! target. It must have the same type, kind type ! parameter, and array rank as POINTER. The association status of neither POINTER nor TARGET shall be undefined. _Return value_: ! `ASSOCIATED(POINTER)' returns a scalar value of type `LOGICAL(4)'. There are several cases: ! (A) When the optional TARGET is not present then ! `ASSOCIATED(POINTER)' is true if POINTER is associated with a target; otherwise, it returns false. ! ! (B) If TARGET is present and a scalar target, the result is true if TARGET is not a zero-sized storage sequence and the target associated with POINTER occupies the same storage units. If POINTER is disassociated, the result is false. ! ! (C) If TARGET is present and an array target, the result is true if TARGET and POINTER have the same shape, are not zero-sized arrays, are arrays whose elements are not zero-sized storage sequences, and TARGET and POINTER occupy the same storage units in array element order. As in case(B), the result is false, if POINTER is disassociated. ! ! (D) If TARGET is present and an scalar pointer, the result is true if TARGET is associated with POINTER, the target associated with TARGET are not zero-sized storage sequences and occupy ! the same storage units. The result is false, if either ! TARGET or POINTER is disassociated. ! ! (E) If TARGET is present and an array pointer, the result is true if target associated with POINTER and the target associated with TARGET have the same shape, are not zero-sized arrays, are arrays whose elements are not zero-sized storage sequences, *************** _See also_: *** 6705,6715 ****  File: gfortran.info, Node: ATAN, Next: ATAN2, Prev: ASSOCIATED, Up: Intrinsic Procedures ! 9.21 'ATAN' -- Arctangent function ================================== _Description_: ! 'ATAN(X)' computes the arctangent of X. _Standard_: Fortran 77 and later, for a complex argument and for two arguments --- 6768,6778 ----  File: gfortran.info, Node: ATAN, Next: ATAN2, Prev: ASSOCIATED, Up: Intrinsic Procedures ! 9.21 `ATAN' -- Arctangent function ================================== _Description_: ! `ATAN(X)' computes the arctangent of X. _Standard_: Fortran 77 and later, for a complex argument and for two arguments *************** _Class_: *** 6719,6739 **** Elemental function _Syntax_: ! 'RESULT = ATAN(X)' ! 'RESULT = ATAN(Y, X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'; if Y is ! present, X shall be REAL. ! Y shall ! be of the ! same type ! and kind ! as X. _Return value_: The return value is of the same type and kind as X. If Y is ! present, the result is identical to 'ATAN2(Y,X)'. Otherwise, it the arcus tangent of X, where the real part of the result is in radians and lies in the range -\pi/2 \leq \Re \atan(x) \leq \pi/2. --- 6782,6802 ---- Elemental function _Syntax_: ! `RESULT = ATAN(X)' ! `RESULT = ATAN(Y, X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'; if Y is ! present, X shall be REAL. ! Y shall ! be of the ! same type ! and kind ! as X. _Return value_: The return value is of the same type and kind as X. If Y is ! present, the result is identical to `ATAN2(Y,X)'. Otherwise, it the arcus tangent of X, where the real part of the result is in radians and lies in the range -\pi/2 \leq \Re \atan(x) \leq \pi/2. *************** _Example_: *** 6744,6768 **** end program test_atan _Specific names_: ! Name Argument Return type Standard ! 'ATAN(X)' 'REAL(4) X' 'REAL(4)' Fortran 77 and ! later ! 'DATAN(X)' 'REAL(8) X' 'REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note TAN::  File: gfortran.info, Node: ATAN2, Next: ATANH, Prev: ATAN, Up: Intrinsic Procedures ! 9.22 'ATAN2' -- Arctangent function =================================== _Description_: ! 'ATAN2(Y, X)' computes the principal value of the argument function ! of the complex number X + i Y. This function can be used to ! transform from Cartesian into polar coordinates and allows to determine the angle in the correct quadrant. _Standard_: --- 6807,6832 ---- end program test_atan _Specific names_: ! Name Argument Return type Standard ! `ATAN(X)' `REAL(4) X' `REAL(4)' Fortran 77 and ! later ! `DATAN(X)' `REAL(8) X' `REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note TAN:: +  File: gfortran.info, Node: ATAN2, Next: ATANH, Prev: ATAN, Up: Intrinsic Procedures ! 9.22 `ATAN2' -- Arctangent function =================================== _Description_: ! `ATAN2(Y, X)' computes the principal value of the argument ! function of the complex number X + i Y. This function can be used ! to transform from Cartesian into polar coordinates and allows to determine the angle in the correct quadrant. _Standard_: *************** _Class_: *** 6772,6788 **** Elemental function _Syntax_: ! 'RESULT = ATAN2(Y, X)' _Arguments_: ! Y The type shall be 'REAL'. ! X The type and kind type parameter shall be the ! same as Y. If Y is zero, then X must be ! nonzero. _Return value_: ! The return value has the same type and kind type parameter as Y. ! It is the principal value of the complex number X + i Y. If X is nonzero, then it lies in the range -\pi \le \atan (x) \leq \pi. The sign is positive if Y is positive. If Y is zero, then the return value is zero if X is strictly positive, \pi if X is --- 6836,6852 ---- Elemental function _Syntax_: ! `RESULT = ATAN2(Y, X)' _Arguments_: ! Y The type shall be `REAL'. ! X The type and kind type parameter shall be the ! same as Y. If Y is zero, then X must be ! nonzero. _Return value_: ! The return value has the same type and kind type parameter as Y. It ! is the principal value of the complex number X + i Y. If X is nonzero, then it lies in the range -\pi \le \atan (x) \leq \pi. The sign is positive if Y is positive. If Y is zero, then the return value is zero if X is strictly positive, \pi if X is *************** _Example_: *** 6797,6816 **** end program test_atan2 _Specific names_: ! Name Argument Return type Standard ! 'ATAN2(X, 'REAL(4) X, 'REAL(4)' Fortran 77 and ! Y)' Y' later ! 'DATAN2(X, 'REAL(8) X, 'REAL(8)' Fortran 77 and ! Y)' Y' later  File: gfortran.info, Node: ATANH, Next: ATOMIC_ADD, Prev: ATAN2, Up: Intrinsic Procedures ! 9.23 'ATANH' -- Inverse hyperbolic tangent function =================================================== _Description_: ! 'ATANH(X)' computes the inverse hyperbolic tangent of X. _Standard_: Fortran 2008 and later --- 6861,6880 ---- end program test_atan2 _Specific names_: ! Name Argument Return type Standard ! `ATAN2(X, `REAL(4) X, `REAL(4)' Fortran 77 and ! Y)' Y' later ! `DATAN2(X, `REAL(8) X, `REAL(8)' Fortran 77 and ! Y)' Y' later  File: gfortran.info, Node: ATANH, Next: ATOMIC_ADD, Prev: ATAN2, Up: Intrinsic Procedures ! 9.23 `ATANH' -- Inverse hyperbolic tangent function =================================================== _Description_: ! `ATANH(X)' computes the inverse hyperbolic tangent of X. _Standard_: Fortran 2008 and later *************** _Class_: *** 6819,6831 **** Elemental function _Syntax_: ! 'RESULT = ATANH(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value has same type and kind as X. If X is complex, the imaginary part of the result is in radians and lies between -\pi/2 \leq \Im \atanh(x) \leq \pi/2. --- 6883,6895 ---- Elemental function _Syntax_: ! `RESULT = ATANH(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value has same type and kind as X. If X is complex, the imaginary part of the result is in radians and lies between -\pi/2 \leq \Im \atanh(x) \leq \pi/2. *************** _Example_: *** 6836,6843 **** END PROGRAM _Specific names_: ! Name Argument Return type Standard ! 'DATANH(X)' 'REAL(8) X' 'REAL(8)' GNU extension _See also_: Inverse function: *note TANH:: --- 6900,6907 ---- END PROGRAM _Specific names_: ! Name Argument Return type Standard ! `DATANH(X)' `REAL(8) X' `REAL(8)' GNU extension _See also_: Inverse function: *note TANH:: *************** _See also_: *** 6845,6862 ****  File: gfortran.info, Node: ATOMIC_ADD, Next: ATOMIC_AND, Prev: ATANH, Up: Intrinsic Procedures ! 9.24 'ATOMIC_ADD' -- Atomic ADD operation ========================================= _Description_: ! 'ATOMIC_ADD(ATOM, VALUE)' atomically adds the value of VAR to the ! variable ATOM. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 6909,6926 ----  File: gfortran.info, Node: ATOMIC_ADD, Next: ATOMIC_AND, Prev: ATANH, Up: Intrinsic Procedures ! 9.24 `ATOMIC_ADD' -- Atomic ADD operation ========================================= _Description_: ! `ATOMIC_ADD(ATOM, VALUE)' atomically adds the value of VAR to the ! variable ATOM. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 6865,6879 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_ADD (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 6929,6944 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_ADD (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 6890,6907 ****  File: gfortran.info, Node: ATOMIC_AND, Next: ATOMIC_CAS, Prev: ATOMIC_ADD, Up: Intrinsic Procedures ! 9.25 'ATOMIC_AND' -- Atomic bitwise AND operation ================================================= _Description_: ! 'ATOMIC_AND(ATOM, VALUE)' atomically defines ATOM with the bitwise ! AND between the values of ATOM and VALUE. When STAT is present and ! the invokation was successful, it is assigned the value 0. If it ! is present and the invokation has failed, it is assigned a positive ! value; in particular, for a coindexed ATOM, if the remote image has ! stopped, it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 6955,6972 ----  File: gfortran.info, Node: ATOMIC_AND, Next: ATOMIC_CAS, Prev: ATOMIC_ADD, Up: Intrinsic Procedures ! 9.25 `ATOMIC_AND' -- Atomic bitwise AND operation ================================================= _Description_: ! `ATOMIC_AND(ATOM, VALUE)' atomically defines ATOM with the bitwise ! AND between the values of ATOM and VALUE. When STAT is present and ! the invokation was successful, it is assigned the value 0. If it ! is present and the invokation has failed, it is assigned a ! positive value; in particular, for a coindexed ATOM, if the remote ! image has stopped, it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 6910,6924 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_AND (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 6975,6990 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_AND (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 6935,6954 ****  File: gfortran.info, Node: ATOMIC_CAS, Next: ATOMIC_DEFINE, Prev: ATOMIC_AND, Up: Intrinsic Procedures ! 9.26 'ATOMIC_CAS' -- Atomic compare and swap ============================================ _Description_: ! 'ATOMIC_CAS' compares the variable ATOM with the value of COMPARE; if the value is the same, ATOM is set to the value of NEW. ! Additionally, OLD is set to the value of ATOM that was used for the ! comparison. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 7001,7020 ----  File: gfortran.info, Node: ATOMIC_CAS, Next: ATOMIC_DEFINE, Prev: ATOMIC_AND, Up: Intrinsic Procedures ! 9.26 `ATOMIC_CAS' -- Atomic compare and swap ============================================ _Description_: ! `ATOMIC_CAS' compares the variable ATOM with the value of COMPARE; if the value is the same, ATOM is set to the value of NEW. ! Additionally, OLD is set to the value of ATOM that was used for ! the comparison. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 6957,6975 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_CAS (ATOM, OLD, COMPARE, NEW [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of either ! integer type with 'ATOMIC_INT_KIND' kind or ! logical type with 'ATOMIC_LOGICAL_KIND' kind. ! OLD Scalar of the same type and kind as ATOM. ! COMPARE Scalar variable of the same type and kind as ! ATOM. ! NEW Scalar variable of the same type as ATOM. If ! kind is different, the value is converted to the ! kind of ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7023,7042 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_CAS (ATOM, OLD, COMPARE, NEW [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of either ! integer type with `ATOMIC_INT_KIND' kind or ! logical type with `ATOMIC_LOGICAL_KIND' kind. ! OLD Scalar of the same type and kind as ATOM. ! COMPARE Scalar variable of the same type and kind as ! ATOM. ! NEW Scalar variable of the same type as ATOM. If ! kind is different, the value is converted to ! the kind of ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 6984,7001 ****  File: gfortran.info, Node: ATOMIC_DEFINE, Next: ATOMIC_FETCH_ADD, Prev: ATOMIC_CAS, Up: Intrinsic Procedures ! 9.27 'ATOMIC_DEFINE' -- Setting a variable atomically ===================================================== _Description_: ! 'ATOMIC_DEFINE(ATOM, VALUE)' defines the variable ATOM with the ! value VALUE atomically. When STAT is present and the invokation ! was successful, it is assigned the value 0. If it is present and ! the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: Fortran 2008 and later; with STAT, TS 18508 or later --- 7051,7068 ----  File: gfortran.info, Node: ATOMIC_DEFINE, Next: ATOMIC_FETCH_ADD, Prev: ATOMIC_CAS, Up: Intrinsic Procedures ! 9.27 `ATOMIC_DEFINE' -- Setting a variable atomically ===================================================== _Description_: ! `ATOMIC_DEFINE(ATOM, VALUE)' defines the variable ATOM with the ! value VALUE atomically. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the ! invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: Fortran 2008 and later; with STAT, TS 18508 or later *************** _Class_: *** 7004,7020 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_DEFINE (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of either ! integer type with 'ATOMIC_INT_KIND' kind or ! logical type with 'ATOMIC_LOGICAL_KIND' kind. ! ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7071,7087 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_DEFINE (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of either ! integer type with `ATOMIC_INT_KIND' kind or ! logical type with `ATOMIC_LOGICAL_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7031,7048 ****  File: gfortran.info, Node: ATOMIC_FETCH_ADD, Next: ATOMIC_FETCH_AND, Prev: ATOMIC_DEFINE, Up: Intrinsic Procedures ! 9.28 'ATOMIC_FETCH_ADD' -- Atomic ADD operation with prior fetch ================================================================ _Description_: ! 'ATOMIC_FETCH_ADD(ATOM, VALUE, OLD)' atomically stores the value of ! ATOM in OLD and adds the value of VAR to the variable ATOM. When STAT is present and the invokation was successful, it is assigned ! the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, it is assigned the value of ! 'ISO_FORTRAN_ENV''s 'STAT_STOPPED_IMAGE' and if the remote image ! has failed, the value 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 7098,7115 ----  File: gfortran.info, Node: ATOMIC_FETCH_ADD, Next: ATOMIC_FETCH_AND, Prev: ATOMIC_DEFINE, Up: Intrinsic Procedures ! 9.28 `ATOMIC_FETCH_ADD' -- Atomic ADD operation with prior fetch ================================================================ _Description_: ! `ATOMIC_FETCH_ADD(ATOM, VALUE, OLD)' atomically stores the value of ! ATOM in OLD and adds the value of VAR to the variable ATOM. When STAT is present and the invokation was successful, it is assigned ! the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, it is assigned the value of ! `ISO_FORTRAN_ENV''s `STAT_STOPPED_IMAGE' and if the remote image ! has failed, the value `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 7051,7068 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_FETCH_ADD (ATOM, VALUE, old [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! 'ATOMIC_LOGICAL_KIND' kind. ! ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7118,7135 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_FETCH_ADD (ATOM, VALUE, old [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! `ATOMIC_LOGICAL_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7079,7097 ****  File: gfortran.info, Node: ATOMIC_FETCH_AND, Next: ATOMIC_FETCH_OR, Prev: ATOMIC_FETCH_ADD, Up: Intrinsic Procedures ! 9.29 'ATOMIC_FETCH_AND' -- Atomic bitwise AND operation with prior fetch ======================================================================== _Description_: ! 'ATOMIC_AND(ATOM, VALUE)' atomically stores the value of ATOM in OLD and defines ATOM with the bitwise AND between the values of ! ATOM and VALUE. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 7146,7164 ----  File: gfortran.info, Node: ATOMIC_FETCH_AND, Next: ATOMIC_FETCH_OR, Prev: ATOMIC_FETCH_ADD, Up: Intrinsic Procedures ! 9.29 `ATOMIC_FETCH_AND' -- Atomic bitwise AND operation with prior fetch ======================================================================== _Description_: ! `ATOMIC_AND(ATOM, VALUE)' atomically stores the value of ATOM in OLD and defines ATOM with the bitwise AND between the values of ! ATOM and VALUE. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 7100,7115 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_FETCH_AND (ATOM, VALUE, OLD [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7167,7183 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_FETCH_AND (ATOM, VALUE, OLD [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7126,7143 ****  File: gfortran.info, Node: ATOMIC_FETCH_OR, Next: ATOMIC_FETCH_XOR, Prev: ATOMIC_FETCH_AND, Up: Intrinsic Procedures ! 9.30 'ATOMIC_FETCH_OR' -- Atomic bitwise OR operation with prior fetch ====================================================================== _Description_: ! 'ATOMIC_OR(ATOM, VALUE)' atomically stores the value of ATOM in OLD ! and defines ATOM with the bitwise OR between the values of ATOM and ! VALUE. When STAT is present and the invokation was successful, it ! is assigned the value 0. If it is present and the invokation has ! failed, it is assigned a positive value; in particular, for a ! coindexed ATOM, if the remote image has stopped, it is assigned the ! value of 'ISO_FORTRAN_ENV''s 'STAT_STOPPED_IMAGE' and if the remote ! image has failed, the value 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 7194,7212 ----  File: gfortran.info, Node: ATOMIC_FETCH_OR, Next: ATOMIC_FETCH_XOR, Prev: ATOMIC_FETCH_AND, Up: Intrinsic Procedures ! 9.30 `ATOMIC_FETCH_OR' -- Atomic bitwise OR operation with prior fetch ====================================================================== _Description_: ! `ATOMIC_OR(ATOM, VALUE)' atomically stores the value of ATOM in ! OLD and defines ATOM with the bitwise OR between the values of ! ATOM and VALUE. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the ! invokation has failed, it is assigned a positive value; in ! particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 7146,7161 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_FETCH_OR (ATOM, VALUE, OLD [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7215,7231 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_FETCH_OR (ATOM, VALUE, OLD [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7172,7190 ****  File: gfortran.info, Node: ATOMIC_FETCH_XOR, Next: ATOMIC_OR, Prev: ATOMIC_FETCH_OR, Up: Intrinsic Procedures ! 9.31 'ATOMIC_FETCH_XOR' -- Atomic bitwise XOR operation with prior fetch ======================================================================== _Description_: ! 'ATOMIC_XOR(ATOM, VALUE)' atomically stores the value of ATOM in OLD and defines ATOM with the bitwise XOR between the values of ! ATOM and VALUE. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 7242,7260 ----  File: gfortran.info, Node: ATOMIC_FETCH_XOR, Next: ATOMIC_OR, Prev: ATOMIC_FETCH_OR, Up: Intrinsic Procedures ! 9.31 `ATOMIC_FETCH_XOR' -- Atomic bitwise XOR operation with prior fetch ======================================================================== _Description_: ! `ATOMIC_XOR(ATOM, VALUE)' atomically stores the value of ATOM in OLD and defines ATOM with the bitwise XOR between the values of ! ATOM and VALUE. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 7193,7208 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_FETCH_XOR (ATOM, VALUE, OLD [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7263,7279 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_FETCH_XOR (ATOM, VALUE, OLD [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! OLD Scalar of the same type and kind as ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7219,7236 ****  File: gfortran.info, Node: ATOMIC_OR, Next: ATOMIC_REF, Prev: ATOMIC_FETCH_XOR, Up: Intrinsic Procedures ! 9.32 'ATOMIC_OR' -- Atomic bitwise OR operation =============================================== _Description_: ! 'ATOMIC_OR(ATOM, VALUE)' atomically defines ATOM with the bitwise ! AND between the values of ATOM and VALUE. When STAT is present and ! the invokation was successful, it is assigned the value 0. If it ! is present and the invokation has failed, it is assigned a positive ! value; in particular, for a coindexed ATOM, if the remote image has ! stopped, it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 7290,7307 ----  File: gfortran.info, Node: ATOMIC_OR, Next: ATOMIC_REF, Prev: ATOMIC_FETCH_XOR, Up: Intrinsic Procedures ! 9.32 `ATOMIC_OR' -- Atomic bitwise OR operation =============================================== _Description_: ! `ATOMIC_OR(ATOM, VALUE)' atomically defines ATOM with the bitwise ! AND between the values of ATOM and VALUE. When STAT is present and ! the invokation was successful, it is assigned the value 0. If it ! is present and the invokation has failed, it is assigned a ! positive value; in particular, for a coindexed ATOM, if the remote ! image has stopped, it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 7239,7253 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_OR (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7310,7325 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_OR (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7264,7281 ****  File: gfortran.info, Node: ATOMIC_REF, Next: ATOMIC_XOR, Prev: ATOMIC_OR, Up: Intrinsic Procedures ! 9.33 'ATOMIC_REF' -- Obtaining the value of a variable atomically ================================================================= _Description_: ! 'ATOMIC_DEFINE(ATOM, VALUE)' atomically assigns the value of the ! variable ATOM to VALUE. When STAT is present and the invokation ! was successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: Fortran 2008 and later; with STAT, TS 18508 or later --- 7336,7353 ----  File: gfortran.info, Node: ATOMIC_REF, Next: ATOMIC_XOR, Prev: ATOMIC_OR, Up: Intrinsic Procedures ! 9.33 `ATOMIC_REF' -- Obtaining the value of a variable atomically ================================================================= _Description_: ! `ATOMIC_DEFINE(ATOM, VALUE)' atomically assigns the value of the ! variable ATOM to VALUE. When STAT is present and the invokation ! was successful, it is assigned the value 0. If it is present and the invokation has failed, it is assigned a positive value; in particular, for a coindexed ATOM, if the remote image has stopped, ! it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: Fortran 2008 and later; with STAT, TS 18508 or later *************** _Class_: *** 7284,7299 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_REF(VALUE, ATOM [, STAT])' _Arguments_: ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! ATOM Scalar coarray or coindexed variable of either ! integer type with 'ATOMIC_INT_KIND' kind or ! logical type with 'ATOMIC_LOGICAL_KIND' kind. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7356,7372 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_REF(VALUE, ATOM [, STAT])' _Arguments_: ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! ATOM Scalar coarray or coindexed variable of either ! integer type with `ATOMIC_INT_KIND' kind or ! logical type with `ATOMIC_LOGICAL_KIND' kind. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7316,7333 ****  File: gfortran.info, Node: ATOMIC_XOR, Next: BACKTRACE, Prev: ATOMIC_REF, Up: Intrinsic Procedures ! 9.34 'ATOMIC_XOR' -- Atomic bitwise OR operation ================================================ _Description_: ! 'ATOMIC_AND(ATOM, VALUE)' atomically defines ATOM with the bitwise ! XOR between the values of ATOM and VALUE. When STAT is present and ! the invokation was successful, it is assigned the value 0. If it ! is present and the invokation has failed, it is assigned a positive ! value; in particular, for a coindexed ATOM, if the remote image has ! stopped, it is assigned the value of 'ISO_FORTRAN_ENV''s ! 'STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! 'STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later --- 7389,7406 ----  File: gfortran.info, Node: ATOMIC_XOR, Next: BACKTRACE, Prev: ATOMIC_REF, Up: Intrinsic Procedures ! 9.34 `ATOMIC_XOR' -- Atomic bitwise OR operation ================================================ _Description_: ! `ATOMIC_AND(ATOM, VALUE)' atomically defines ATOM with the bitwise ! XOR between the values of ATOM and VALUE. When STAT is present and ! the invokation was successful, it is assigned the value 0. If it ! is present and the invokation has failed, it is assigned a ! positive value; in particular, for a coindexed ATOM, if the remote ! image has stopped, it is assigned the value of `ISO_FORTRAN_ENV''s ! `STAT_STOPPED_IMAGE' and if the remote image has failed, the value ! `STAT_FAILED_IMAGE'. _Standard_: TS 18508 or later *************** _Class_: *** 7336,7350 **** Atomic subroutine _Syntax_: ! 'CALL ATOMIC_XOR (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with 'ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind is ! different, the value is converted to the kind of ! ATOM. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 7409,7424 ---- Atomic subroutine _Syntax_: ! `CALL ATOMIC_XOR (ATOM, VALUE [, STAT])' _Arguments_: ! ATOM Scalar coarray or coindexed variable of integer ! type with `ATOMIC_INT_KIND' kind. ! VALUE Scalar of the same type as ATOM. If the kind ! is different, the value is converted to the ! kind of ATOM. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _See also_: *** 7361,7374 ****  File: gfortran.info, Node: BACKTRACE, Next: BESSEL_J0, Prev: ATOMIC_XOR, Up: Intrinsic Procedures ! 9.35 'BACKTRACE' -- Show a backtrace ==================================== _Description_: ! 'BACKTRACE' shows a backtrace at an arbitrary place in user code. ! Program execution continues normally afterwards. The backtrace ! information is printed to the unit corresponding to 'ERROR_UNIT' in ! 'ISO_FORTRAN_ENV'. _Standard_: GNU Extension --- 7435,7448 ----  File: gfortran.info, Node: BACKTRACE, Next: BESSEL_J0, Prev: ATOMIC_XOR, Up: Intrinsic Procedures ! 9.35 `BACKTRACE' -- Show a backtrace ==================================== _Description_: ! `BACKTRACE' shows a backtrace at an arbitrary place in user code. ! Program execution continues normally afterwards. The backtrace ! information is printed to the unit corresponding to `ERROR_UNIT' ! in `ISO_FORTRAN_ENV'. _Standard_: GNU Extension *************** _Class_: *** 7377,7383 **** Subroutine _Syntax_: ! 'CALL BACKTRACE' _Arguments_: None --- 7451,7457 ---- Subroutine _Syntax_: ! `CALL BACKTRACE' _Arguments_: None *************** _See also_: *** 7388,7399 ****  File: gfortran.info, Node: BESSEL_J0, Next: BESSEL_J1, Prev: BACKTRACE, Up: Intrinsic Procedures ! 9.36 'BESSEL_J0' -- Bessel function of the first kind of order 0 ================================================================ _Description_: ! 'BESSEL_J0(X)' computes the Bessel function of the first kind of ! order 0 of X. This function is available under the name 'BESJ0' as a GNU extension. _Standard_: --- 7462,7473 ----  File: gfortran.info, Node: BESSEL_J0, Next: BESSEL_J1, Prev: BACKTRACE, Up: Intrinsic Procedures ! 9.36 `BESSEL_J0' -- Bessel function of the first kind of order 0 ================================================================ _Description_: ! `BESSEL_J0(X)' computes the Bessel function of the first kind of ! order 0 of X. This function is available under the name `BESJ0' as a GNU extension. _Standard_: *************** _Class_: *** 7403,7416 **** Elemental function _Syntax_: ! 'RESULT = BESSEL_J0(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL' and lies in the range - ! 0.4027... \leq Bessel (0,x) \leq 1. It has the same kind as X. _Example_: program test_besj0 --- 7477,7490 ---- Elemental function _Syntax_: ! `RESULT = BESSEL_J0(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL' and lies in the range - ! 0.4027... \leq Bessel (0,x) \leq 1. It has the same kind as X. _Example_: program test_besj0 *************** _Example_: *** 7419,7436 **** end program test_besj0 _Specific names_: ! Name Argument Return type Standard ! 'DBESJ0(X)' 'REAL(8) X' 'REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_J1, Next: BESSEL_JN, Prev: BESSEL_J0, Up: Intrinsic Procedures ! 9.37 'BESSEL_J1' -- Bessel function of the first kind of order 1 ================================================================ _Description_: ! 'BESSEL_J1(X)' computes the Bessel function of the first kind of ! order 1 of X. This function is available under the name 'BESJ1' as a GNU extension. _Standard_: --- 7493,7510 ---- end program test_besj0 _Specific names_: ! Name Argument Return type Standard ! `DBESJ0(X)' `REAL(8) X' `REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_J1, Next: BESSEL_JN, Prev: BESSEL_J0, Up: Intrinsic Procedures ! 9.37 `BESSEL_J1' -- Bessel function of the first kind of order 1 ================================================================ _Description_: ! `BESSEL_J1(X)' computes the Bessel function of the first kind of ! order 1 of X. This function is available under the name `BESJ1' as a GNU extension. _Standard_: *************** _Class_: *** 7440,7453 **** Elemental function _Syntax_: ! 'RESULT = BESSEL_J1(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL' and lies in the range - ! 0.5818... \leq Bessel (0,x) \leq 0.5818 . It has the same kind as X. _Example_: --- 7514,7527 ---- Elemental function _Syntax_: ! `RESULT = BESSEL_J1(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL' and lies in the range - ! 0.5818... \leq Bessel (0,x) \leq 0.5818 . It has the same kind as X. _Example_: *************** _Example_: *** 7457,7478 **** end program test_besj1 _Specific names_: ! Name Argument Return type Standard ! 'DBESJ1(X)' 'REAL(8) X' 'REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_JN, Next: BESSEL_Y0, Prev: BESSEL_J1, Up: Intrinsic Procedures ! 9.38 'BESSEL_JN' -- Bessel function of the first kind ===================================================== _Description_: ! 'BESSEL_JN(N, X)' computes the Bessel function of the first kind of ! order N of X. This function is available under the name 'BESJN' as a GNU extension. If N and X are arrays, their ranks and shapes shall conform. ! 'BESSEL_JN(N1, N2, X)' returns an array with the Bessel functions of the first kind of the orders N1 to N2. _Standard_: --- 7531,7552 ---- end program test_besj1 _Specific names_: ! Name Argument Return type Standard ! `DBESJ1(X)' `REAL(8) X' `REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_JN, Next: BESSEL_Y0, Prev: BESSEL_J1, Up: Intrinsic Procedures ! 9.38 `BESSEL_JN' -- Bessel function of the first kind ===================================================== _Description_: ! `BESSEL_JN(N, X)' computes the Bessel function of the first kind of ! order N of X. This function is available under the name `BESJN' as a GNU extension. If N and X are arrays, their ranks and shapes shall conform. ! `BESSEL_JN(N1, N2, X)' returns an array with the Bessel functions of the first kind of the orders N1 to N2. _Standard_: *************** _Standard_: *** 7480,7502 **** _Class_: Elemental function, except for the transformational function ! 'BESSEL_JN(N1, N2, X)' _Syntax_: ! 'RESULT = BESSEL_JN(N, X)' ! 'RESULT = BESSEL_JN(N1, N2, X)' _Arguments_: ! N Shall be a scalar or an array of type 'INTEGER'. ! N1 Shall be a non-negative scalar of type ! 'INTEGER'. ! N2 Shall be a non-negative scalar of type ! 'INTEGER'. ! X Shall be a scalar or an array of type 'REAL'; ! for 'BESSEL_JN(N1, N2, X)' it shall be scalar. _Return value_: ! The return value is a scalar of type 'REAL'. It has the same kind as X. _Note_: --- 7554,7577 ---- _Class_: Elemental function, except for the transformational function ! `BESSEL_JN(N1, N2, X)' _Syntax_: ! `RESULT = BESSEL_JN(N, X)' ! `RESULT = BESSEL_JN(N1, N2, X)' _Arguments_: ! N Shall be a scalar or an array of type ! `INTEGER'. ! N1 Shall be a non-negative scalar of type ! `INTEGER'. ! N2 Shall be a non-negative scalar of type ! `INTEGER'. ! X Shall be a scalar or an array of type `REAL'; ! for `BESSEL_JN(N1, N2, X)' it shall be scalar. _Return value_: ! The return value is a scalar of type `REAL'. It has the same kind as X. _Note_: *************** _Example_: *** 7511,7530 **** end program test_besjn _Specific names_: ! Name Argument Return type Standard ! 'DBESJN(N, 'INTEGER N' 'REAL(8)' GNU extension ! X)' ! 'REAL(8) X'  File: gfortran.info, Node: BESSEL_Y0, Next: BESSEL_Y1, Prev: BESSEL_JN, Up: Intrinsic Procedures ! 9.39 'BESSEL_Y0' -- Bessel function of the second kind of order 0 ================================================================= _Description_: ! 'BESSEL_Y0(X)' computes the Bessel function of the second kind of ! order 0 of X. This function is available under the name 'BESY0' as a GNU extension. _Standard_: --- 7586,7605 ---- end program test_besjn _Specific names_: ! Name Argument Return type Standard ! `DBESJN(N, `INTEGER N' `REAL(8)' GNU extension ! X)' ! `REAL(8) X'  File: gfortran.info, Node: BESSEL_Y0, Next: BESSEL_Y1, Prev: BESSEL_JN, Up: Intrinsic Procedures ! 9.39 `BESSEL_Y0' -- Bessel function of the second kind of order 0 ================================================================= _Description_: ! `BESSEL_Y0(X)' computes the Bessel function of the second kind of ! order 0 of X. This function is available under the name `BESY0' as a GNU extension. _Standard_: *************** _Class_: *** 7534,7546 **** Elemental function _Syntax_: ! 'RESULT = BESSEL_Y0(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL'. It has the same kind as X. _Example_: program test_besy0 --- 7609,7621 ---- Elemental function _Syntax_: ! `RESULT = BESSEL_Y0(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL'. It has the same kind as X. _Example_: program test_besy0 *************** _Example_: *** 7549,7566 **** end program test_besy0 _Specific names_: ! Name Argument Return type Standard ! 'DBESY0(X)' 'REAL(8) X' 'REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_Y1, Next: BESSEL_YN, Prev: BESSEL_Y0, Up: Intrinsic Procedures ! 9.40 'BESSEL_Y1' -- Bessel function of the second kind of order 1 ================================================================= _Description_: ! 'BESSEL_Y1(X)' computes the Bessel function of the second kind of ! order 1 of X. This function is available under the name 'BESY1' as a GNU extension. _Standard_: --- 7624,7641 ---- end program test_besy0 _Specific names_: ! Name Argument Return type Standard ! `DBESY0(X)' `REAL(8) X' `REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_Y1, Next: BESSEL_YN, Prev: BESSEL_Y0, Up: Intrinsic Procedures ! 9.40 `BESSEL_Y1' -- Bessel function of the second kind of order 1 ================================================================= _Description_: ! `BESSEL_Y1(X)' computes the Bessel function of the second kind of ! order 1 of X. This function is available under the name `BESY1' as a GNU extension. _Standard_: *************** _Class_: *** 7570,7582 **** Elemental function _Syntax_: ! 'RESULT = BESSEL_Y1(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL'. It has the same kind as X. _Example_: program test_besy1 --- 7645,7657 ---- Elemental function _Syntax_: ! `RESULT = BESSEL_Y1(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL'. It has the same kind as X. _Example_: program test_besy1 *************** _Example_: *** 7585,7606 **** end program test_besy1 _Specific names_: ! Name Argument Return type Standard ! 'DBESY1(X)' 'REAL(8) X' 'REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_YN, Next: BGE, Prev: BESSEL_Y1, Up: Intrinsic Procedures ! 9.41 'BESSEL_YN' -- Bessel function of the second kind ====================================================== _Description_: ! 'BESSEL_YN(N, X)' computes the Bessel function of the second kind ! of order N of X. This function is available under the name 'BESYN' as a GNU extension. If N and X are arrays, their ranks and shapes shall conform. ! 'BESSEL_YN(N1, N2, X)' returns an array with the Bessel functions of the first kind of the orders N1 to N2. _Standard_: --- 7660,7681 ---- end program test_besy1 _Specific names_: ! Name Argument Return type Standard ! `DBESY1(X)' `REAL(8) X' `REAL(8)' GNU extension  File: gfortran.info, Node: BESSEL_YN, Next: BGE, Prev: BESSEL_Y1, Up: Intrinsic Procedures ! 9.41 `BESSEL_YN' -- Bessel function of the second kind ====================================================== _Description_: ! `BESSEL_YN(N, X)' computes the Bessel function of the second kind ! of order N of X. This function is available under the name `BESYN' as a GNU extension. If N and X are arrays, their ranks and shapes shall conform. ! `BESSEL_YN(N1, N2, X)' returns an array with the Bessel functions of the first kind of the orders N1 to N2. _Standard_: *************** _Standard_: *** 7608,7631 **** _Class_: Elemental function, except for the transformational function ! 'BESSEL_YN(N1, N2, X)' _Syntax_: ! 'RESULT = BESSEL_YN(N, X)' ! 'RESULT = BESSEL_YN(N1, N2, X)' _Arguments_: ! N Shall be a scalar or an array of type 'INTEGER' ! . ! N1 Shall be a non-negative scalar of type ! 'INTEGER'. ! N2 Shall be a non-negative scalar of type ! 'INTEGER'. ! X Shall be a scalar or an array of type 'REAL'; ! for 'BESSEL_YN(N1, N2, X)' it shall be scalar. _Return value_: ! The return value is a scalar of type 'REAL'. It has the same kind as X. _Note_: --- 7683,7706 ---- _Class_: Elemental function, except for the transformational function ! `BESSEL_YN(N1, N2, X)' _Syntax_: ! `RESULT = BESSEL_YN(N, X)' ! `RESULT = BESSEL_YN(N1, N2, X)' _Arguments_: ! N Shall be a scalar or an array of type ! `INTEGER' . ! N1 Shall be a non-negative scalar of type ! `INTEGER'. ! N2 Shall be a non-negative scalar of type ! `INTEGER'. ! X Shall be a scalar or an array of type `REAL'; ! for `BESSEL_YN(N1, N2, X)' it shall be scalar. _Return value_: ! The return value is a scalar of type `REAL'. It has the same kind as X. _Note_: *************** _Example_: *** 7640,7653 **** end program test_besyn _Specific names_: ! Name Argument Return type Standard ! 'DBESYN(N,X)' 'INTEGER N' 'REAL(8)' GNU extension ! 'REAL(8) X'  File: gfortran.info, Node: BGE, Next: BGT, Prev: BESSEL_YN, Up: Intrinsic Procedures ! 9.42 'BGE' -- Bitwise greater than or equal to ============================================== _Description_: --- 7715,7728 ---- end program test_besyn _Specific names_: ! Name Argument Return type Standard ! `DBESYN(N,X)' `INTEGER N' `REAL(8)' GNU extension ! `REAL(8) X'  File: gfortran.info, Node: BGE, Next: BGT, Prev: BESSEL_YN, Up: Intrinsic Procedures ! 9.42 `BGE' -- Bitwise greater than or equal to ============================================== _Description_: *************** _Class_: *** 7661,7675 **** Elemental function _Syntax_: ! 'RESULT = BGE(I, J)' _Arguments_: ! I Shall be of 'INTEGER' type. ! J Shall be of 'INTEGER' type, and of the same kind ! as I. _Return value_: ! The return value is of type 'LOGICAL' and of the default kind. _See also_: *note BGT::, *note BLE::, *note BLT:: --- 7736,7750 ---- Elemental function _Syntax_: ! `RESULT = BGE(I, J)' _Arguments_: ! I Shall be of `INTEGER' type. ! J Shall be of `INTEGER' type, and of the same ! kind as I. _Return value_: ! The return value is of type `LOGICAL' and of the default kind. _See also_: *note BGT::, *note BLE::, *note BLT:: *************** _See also_: *** 7677,7683 ****  File: gfortran.info, Node: BGT, Next: BIT_SIZE, Prev: BGE, Up: Intrinsic Procedures ! 9.43 'BGT' -- Bitwise greater than ================================== _Description_: --- 7752,7758 ----  File: gfortran.info, Node: BGT, Next: BIT_SIZE, Prev: BGE, Up: Intrinsic Procedures ! 9.43 `BGT' -- Bitwise greater than ================================== _Description_: *************** _Class_: *** 7690,7704 **** Elemental function _Syntax_: ! 'RESULT = BGT(I, J)' _Arguments_: ! I Shall be of 'INTEGER' type. ! J Shall be of 'INTEGER' type, and of the same kind ! as I. _Return value_: ! The return value is of type 'LOGICAL' and of the default kind. _See also_: *note BGE::, *note BLE::, *note BLT:: --- 7765,7779 ---- Elemental function _Syntax_: ! `RESULT = BGT(I, J)' _Arguments_: ! I Shall be of `INTEGER' type. ! J Shall be of `INTEGER' type, and of the same ! kind as I. _Return value_: ! The return value is of type `LOGICAL' and of the default kind. _See also_: *note BGE::, *note BLE::, *note BLT:: *************** _See also_: *** 7706,7718 ****  File: gfortran.info, Node: BIT_SIZE, Next: BLE, Prev: BGT, Up: Intrinsic Procedures ! 9.44 'BIT_SIZE' -- Bit size inquiry function ============================================ _Description_: ! 'BIT_SIZE(I)' returns the number of bits (integer precision plus sign bit) represented by the type of I. The result of ! 'BIT_SIZE(I)' is independent of the actual value of I. _Standard_: Fortran 95 and later --- 7781,7793 ----  File: gfortran.info, Node: BIT_SIZE, Next: BLE, Prev: BGT, Up: Intrinsic Procedures ! 9.44 `BIT_SIZE' -- Bit size inquiry function ============================================ _Description_: ! `BIT_SIZE(I)' returns the number of bits (integer precision plus sign bit) represented by the type of I. The result of ! `BIT_SIZE(I)' is independent of the actual value of I. _Standard_: Fortran 95 and later *************** _Class_: *** 7721,7733 **** Inquiry function _Syntax_: ! 'RESULT = BIT_SIZE(I)' _Arguments_: ! I The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' _Example_: program test_bit_size --- 7796,7808 ---- Inquiry function _Syntax_: ! `RESULT = BIT_SIZE(I)' _Arguments_: ! I The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' _Example_: program test_bit_size *************** _Example_: *** 7740,7746 ****  File: gfortran.info, Node: BLE, Next: BLT, Prev: BIT_SIZE, Up: Intrinsic Procedures ! 9.45 'BLE' -- Bitwise less than or equal to =========================================== _Description_: --- 7815,7821 ----  File: gfortran.info, Node: BLE, Next: BLT, Prev: BIT_SIZE, Up: Intrinsic Procedures ! 9.45 `BLE' -- Bitwise less than or equal to =========================================== _Description_: *************** _Class_: *** 7754,7768 **** Elemental function _Syntax_: ! 'RESULT = BLE(I, J)' _Arguments_: ! I Shall be of 'INTEGER' type. ! J Shall be of 'INTEGER' type, and of the same kind ! as I. _Return value_: ! The return value is of type 'LOGICAL' and of the default kind. _See also_: *note BGT::, *note BGE::, *note BLT:: --- 7829,7843 ---- Elemental function _Syntax_: ! `RESULT = BLE(I, J)' _Arguments_: ! I Shall be of `INTEGER' type. ! J Shall be of `INTEGER' type, and of the same ! kind as I. _Return value_: ! The return value is of type `LOGICAL' and of the default kind. _See also_: *note BGT::, *note BGE::, *note BLT:: *************** _See also_: *** 7770,7776 ****  File: gfortran.info, Node: BLT, Next: BTEST, Prev: BLE, Up: Intrinsic Procedures ! 9.46 'BLT' -- Bitwise less than =============================== _Description_: --- 7845,7851 ----  File: gfortran.info, Node: BLT, Next: BTEST, Prev: BLE, Up: Intrinsic Procedures ! 9.46 `BLT' -- Bitwise less than =============================== _Description_: *************** _Class_: *** 7783,7797 **** Elemental function _Syntax_: ! 'RESULT = BLT(I, J)' _Arguments_: ! I Shall be of 'INTEGER' type. ! J Shall be of 'INTEGER' type, and of the same kind ! as I. _Return value_: ! The return value is of type 'LOGICAL' and of the default kind. _See also_: *note BGE::, *note BGT::, *note BLE:: --- 7858,7872 ---- Elemental function _Syntax_: ! `RESULT = BLT(I, J)' _Arguments_: ! I Shall be of `INTEGER' type. ! J Shall be of `INTEGER' type, and of the same ! kind as I. _Return value_: ! The return value is of type `LOGICAL' and of the default kind. _See also_: *note BGE::, *note BGT::, *note BLE:: *************** _See also_: *** 7799,7809 ****  File: gfortran.info, Node: BTEST, Next: C_ASSOCIATED, Prev: BLT, Up: Intrinsic Procedures ! 9.47 'BTEST' -- Bit test function ================================= _Description_: ! 'BTEST(I,POS)' returns logical '.TRUE.' if the bit at POS in I is set. The counting of the bits starts at 0. _Standard_: --- 7874,7884 ----  File: gfortran.info, Node: BTEST, Next: C_ASSOCIATED, Prev: BLT, Up: Intrinsic Procedures ! 9.47 `BTEST' -- Bit test function ================================= _Description_: ! `BTEST(I,POS)' returns logical `.TRUE.' if the bit at POS in I is set. The counting of the bits starts at 0. _Standard_: *************** _Class_: *** 7813,7826 **** Elemental function _Syntax_: ! 'RESULT = BTEST(I, POS)' _Arguments_: ! I The type shall be 'INTEGER'. ! POS The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'LOGICAL' _Example_: program test_btest --- 7888,7901 ---- Elemental function _Syntax_: ! `RESULT = BTEST(I, POS)' _Arguments_: ! I The type shall be `INTEGER'. ! POS The type shall be `INTEGER'. _Return value_: ! The return value is of type `LOGICAL' _Example_: program test_btest *************** _Example_: *** 7836,7846 ****  File: gfortran.info, Node: C_ASSOCIATED, Next: C_F_POINTER, Prev: BTEST, Up: Intrinsic Procedures ! 9.48 'C_ASSOCIATED' -- Status of a C pointer ============================================ _Description_: ! 'C_ASSOCIATED(c_ptr_1[, c_ptr_2])' determines the status of the C pointer C_PTR_1 or if C_PTR_1 is associated with the target C_PTR_2. --- 7911,7921 ----  File: gfortran.info, Node: C_ASSOCIATED, Next: C_F_POINTER, Prev: BTEST, Up: Intrinsic Procedures ! 9.48 `C_ASSOCIATED' -- Status of a C pointer ============================================ _Description_: ! `C_ASSOCIATED(c_ptr_1[, c_ptr_2])' determines the status of the C pointer C_PTR_1 or if C_PTR_1 is associated with the target C_PTR_2. *************** _Class_: *** 7851,7864 **** Inquiry function _Syntax_: ! 'RESULT = C_ASSOCIATED(c_ptr_1[, c_ptr_2])' _Arguments_: ! C_PTR_1 Scalar of the type 'C_PTR' or 'C_FUNPTR'. ! C_PTR_2 (Optional) Scalar of the same type as C_PTR_1. _Return value_: ! The return value is of type 'LOGICAL'; it is '.false.' if either C_PTR_1 is a C NULL pointer or if C_PTR1 and C_PTR_2 point to different addresses. --- 7926,7939 ---- Inquiry function _Syntax_: ! `RESULT = C_ASSOCIATED(c_ptr_1[, c_ptr_2])' _Arguments_: ! C_PTR_1 Scalar of the type `C_PTR' or `C_FUNPTR'. ! C_PTR_2 (Optional) Scalar of the same type as C_PTR_1. _Return value_: ! The return value is of type `LOGICAL'; it is `.false.' if either C_PTR_1 is a C NULL pointer or if C_PTR1 and C_PTR_2 point to different addresses. *************** _See also_: *** 7878,7888 ****  File: gfortran.info, Node: C_F_POINTER, Next: C_F_PROCPOINTER, Prev: C_ASSOCIATED, Up: Intrinsic Procedures ! 9.49 'C_F_POINTER' -- Convert C into Fortran pointer ==================================================== _Description_: ! 'C_F_POINTER(CPTR, FPTR[, SHAPE])' assigns the target of the C pointer CPTR to the Fortran pointer FPTR and specifies its shape. _Standard_: --- 7953,7963 ----  File: gfortran.info, Node: C_F_POINTER, Next: C_F_PROCPOINTER, Prev: C_ASSOCIATED, Up: Intrinsic Procedures ! 9.49 `C_F_POINTER' -- Convert C into Fortran pointer ==================================================== _Description_: ! `C_F_POINTER(CPTR, FPTR[, SHAPE])' assigns the target of the C pointer CPTR to the Fortran pointer FPTR and specifies its shape. _Standard_: *************** _Class_: *** 7892,7907 **** Subroutine _Syntax_: ! 'CALL C_F_POINTER(CPTR, FPTR[, SHAPE])' _Arguments_: ! CPTR scalar of the type 'C_PTR'. It is 'INTENT(IN)'. ! FPTR pointer interoperable with CPTR. It is ! 'INTENT(OUT)'. ! SHAPE (Optional) Rank-one array of type 'INTEGER' with ! 'INTENT(IN)'. It shall be present if and only ! if FPTR is an array. The size must be equal to ! the rank of FPTR. _Example_: program main --- 7967,7982 ---- Subroutine _Syntax_: ! `CALL C_F_POINTER(CPTR, FPTR[, SHAPE])' _Arguments_: ! CPTR scalar of the type `C_PTR'. It is `INTENT(IN)'. ! FPTR pointer interoperable with CPTR. It is ! `INTENT(OUT)'. ! SHAPE (Optional) Rank-one array of type `INTEGER' ! with `INTENT(IN)'. It shall be present if and ! only if FPTR is an array. The size must be ! equal to the rank of FPTR. _Example_: program main *************** _See also_: *** 7925,7935 ****  File: gfortran.info, Node: C_F_PROCPOINTER, Next: C_FUNLOC, Prev: C_F_POINTER, Up: Intrinsic Procedures ! 9.50 'C_F_PROCPOINTER' -- Convert C into Fortran procedure pointer ================================================================== _Description_: ! 'C_F_PROCPOINTER(CPTR, FPTR)' Assign the target of the C function pointer CPTR to the Fortran procedure pointer FPTR. _Standard_: --- 8000,8010 ----  File: gfortran.info, Node: C_F_PROCPOINTER, Next: C_FUNLOC, Prev: C_F_POINTER, Up: Intrinsic Procedures ! 9.50 `C_F_PROCPOINTER' -- Convert C into Fortran procedure pointer ================================================================== _Description_: ! `C_F_PROCPOINTER(CPTR, FPTR)' Assign the target of the C function pointer CPTR to the Fortran procedure pointer FPTR. _Standard_: *************** _Class_: *** 7939,7951 **** Subroutine _Syntax_: ! 'CALL C_F_PROCPOINTER(cptr, fptr)' _Arguments_: ! CPTR scalar of the type 'C_FUNPTR'. It is ! 'INTENT(IN)'. ! FPTR procedure pointer interoperable with CPTR. It ! is 'INTENT(OUT)'. _Example_: program main --- 8014,8026 ---- Subroutine _Syntax_: ! `CALL C_F_PROCPOINTER(cptr, fptr)' _Arguments_: ! CPTR scalar of the type `C_FUNPTR'. It is ! `INTENT(IN)'. ! FPTR procedure pointer interoperable with CPTR. It ! is `INTENT(OUT)'. _Example_: program main *************** _See also_: *** 7976,7986 ****  File: gfortran.info, Node: C_FUNLOC, Next: C_LOC, Prev: C_F_PROCPOINTER, Up: Intrinsic Procedures ! 9.51 'C_FUNLOC' -- Obtain the C address of a procedure ====================================================== _Description_: ! 'C_FUNLOC(x)' determines the C address of the argument. _Standard_: Fortran 2003 and later --- 8051,8061 ----  File: gfortran.info, Node: C_FUNLOC, Next: C_LOC, Prev: C_F_PROCPOINTER, Up: Intrinsic Procedures ! 9.51 `C_FUNLOC' -- Obtain the C address of a procedure ====================================================== _Description_: ! `C_FUNLOC(x)' determines the C address of the argument. _Standard_: Fortran 2003 and later *************** _Class_: *** 7989,8002 **** Inquiry function _Syntax_: ! 'RESULT = C_FUNLOC(x)' _Arguments_: ! X Interoperable function or pointer to such ! function. _Return value_: ! The return value is of type 'C_FUNPTR' and contains the C address of the argument. _Example_: --- 8064,8077 ---- Inquiry function _Syntax_: ! `RESULT = C_FUNLOC(x)' _Arguments_: ! X Interoperable function or pointer to such ! function. _Return value_: ! The return value is of type `C_FUNPTR' and contains the C address of the argument. _Example_: *************** _See also_: *** 8029,8039 ****  File: gfortran.info, Node: C_LOC, Next: C_SIZEOF, Prev: C_FUNLOC, Up: Intrinsic Procedures ! 9.52 'C_LOC' -- Obtain the C address of an object ================================================= _Description_: ! 'C_LOC(X)' determines the C address of the argument. _Standard_: Fortran 2003 and later --- 8104,8114 ----  File: gfortran.info, Node: C_LOC, Next: C_SIZEOF, Prev: C_FUNLOC, Up: Intrinsic Procedures ! 9.52 `C_LOC' -- Obtain the C address of an object ================================================= _Description_: ! `C_LOC(X)' determines the C address of the argument. _Standard_: Fortran 2003 and later *************** _Class_: *** 8042,8059 **** Inquiry function _Syntax_: ! 'RESULT = C_LOC(X)' _Arguments_: ! X Shall have either the POINTER or TARGET attribute. ! It shall not be a coindexed object. It shall either ! be a variable with interoperable type and kind type ! parameters, or be a scalar, nonpolymorphic variable ! with no length type parameters. ! _Return value_: ! The return value is of type 'C_PTR' and contains the C address of the argument. _Example_: --- 8117,8134 ---- Inquiry function _Syntax_: ! `RESULT = C_LOC(X)' _Arguments_: ! X Shall have either the POINTER or TARGET ! attribute. It shall not be a coindexed object. It ! shall either be a variable with interoperable ! type and kind type parameters, or be a scalar, ! nonpolymorphic variable with no length type ! parameters. _Return value_: ! The return value is of type `C_PTR' and contains the C address of the argument. _Example_: *************** _See also_: *** 8073,8105 ****  File: gfortran.info, Node: C_SIZEOF, Next: CEILING, Prev: C_LOC, Up: Intrinsic Procedures ! 9.53 'C_SIZEOF' -- Size in bytes of an expression ================================================= _Description_: ! 'C_SIZEOF(X)' calculates the number of bytes of storage the ! expression 'X' occupies. _Standard_: Fortran 2008 _Class_: ! Inquiry function of the module 'ISO_C_BINDING' _Syntax_: ! 'N = C_SIZEOF(X)' _Arguments_: ! X The argument shall be an interoperable data ! entity. _Return value_: The return value is of type integer and of the system-dependent ! kind 'C_SIZE_T' (from the 'ISO_C_BINDING' module). Its value is ! the number of bytes occupied by the argument. If the argument has ! the 'POINTER' attribute, the number of bytes of the storage area pointed to is returned. If the argument is of a derived type with ! 'POINTER' or 'ALLOCATABLE' components, the return value does not account for the sizes of the data pointed to by these components. _Example_: --- 8148,8180 ----  File: gfortran.info, Node: C_SIZEOF, Next: CEILING, Prev: C_LOC, Up: Intrinsic Procedures ! 9.53 `C_SIZEOF' -- Size in bytes of an expression ================================================= _Description_: ! `C_SIZEOF(X)' calculates the number of bytes of storage the ! expression `X' occupies. _Standard_: Fortran 2008 _Class_: ! Inquiry function of the module `ISO_C_BINDING' _Syntax_: ! `N = C_SIZEOF(X)' _Arguments_: ! X The argument shall be an interoperable data ! entity. _Return value_: The return value is of type integer and of the system-dependent ! kind `C_SIZE_T' (from the `ISO_C_BINDING' module). Its value is the ! number of bytes occupied by the argument. If the argument has the ! `POINTER' attribute, the number of bytes of the storage area pointed to is returned. If the argument is of a derived type with ! `POINTER' or `ALLOCATABLE' components, the return value does not account for the sizes of the data pointed to by these components. _Example_: *************** _Example_: *** 8108,8115 **** real(c_float) :: r, s(5) print *, (c_sizeof(s)/c_sizeof(r) == 5) end ! The example will print '.TRUE.' unless you are using a platform ! where default 'REAL' variables are unusually padded. _See also_: *note SIZEOF::, *note STORAGE_SIZE:: --- 8183,8190 ---- real(c_float) :: r, s(5) print *, (c_sizeof(s)/c_sizeof(r) == 5) end ! The example will print `.TRUE.' unless you are using a platform ! where default `REAL' variables are unusually padded. _See also_: *note SIZEOF::, *note STORAGE_SIZE:: *************** _See also_: *** 8117,8127 ****  File: gfortran.info, Node: CEILING, Next: CHAR, Prev: C_SIZEOF, Up: Intrinsic Procedures ! 9.54 'CEILING' -- Integer ceiling function ========================================== _Description_: ! 'CEILING(A)' returns the least integer greater than or equal to A. _Standard_: Fortran 95 and later --- 8192,8202 ----  File: gfortran.info, Node: CEILING, Next: CHAR, Prev: C_SIZEOF, Up: Intrinsic Procedures ! 9.54 `CEILING' -- Integer ceiling function ========================================== _Description_: ! `CEILING(A)' returns the least integer greater than or equal to A. _Standard_: Fortran 95 and later *************** _Class_: *** 8130,8146 **** Elemental function _Syntax_: ! 'RESULT = CEILING(A [, KIND])' _Arguments_: ! A The type shall be 'REAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER(KIND)' if KIND is present and ! a default-kind 'INTEGER' otherwise. _Example_: program test_ceiling --- 8205,8221 ---- Elemental function _Syntax_: ! `RESULT = CEILING(A [, KIND])' _Arguments_: ! A The type shall be `REAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER(KIND)' if KIND is present and ! a default-kind `INTEGER' otherwise. _Example_: program test_ceiling *************** _Example_: *** 8153,8167 **** _See also_: *note FLOOR::, *note NINT::  File: gfortran.info, Node: CHAR, Next: CHDIR, Prev: CEILING, Up: Intrinsic Procedures ! 9.55 'CHAR' -- Character conversion function ============================================ _Description_: ! 'CHAR(I [, KIND])' returns the character represented by the integer ! I. _Standard_: Fortran 77 and later --- 8228,8243 ---- _See also_: *note FLOOR::, *note NINT:: +  File: gfortran.info, Node: CHAR, Next: CHDIR, Prev: CEILING, Up: Intrinsic Procedures ! 9.55 `CHAR' -- Character conversion function ============================================ _Description_: ! `CHAR(I [, KIND])' returns the character represented by the ! integer I. _Standard_: Fortran 77 and later *************** _Class_: *** 8170,8185 **** Elemental function _Syntax_: ! 'RESULT = CHAR(I [, KIND])' _Arguments_: ! I The type shall be 'INTEGER'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'CHARACTER(1)' _Example_: program test_char --- 8246,8261 ---- Elemental function _Syntax_: ! `RESULT = CHAR(I [, KIND])' _Arguments_: ! I The type shall be `INTEGER'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `CHARACTER(1)' _Example_: program test_char *************** _Example_: *** 8190,8197 **** end program test_char _Specific names_: ! Name Argument Return type Standard ! 'CHAR(I)' 'INTEGER I' 'CHARACTER(LEN=1)'F77 and later _Note_: See *note ICHAR:: for a discussion of converting between numerical --- 8266,8273 ---- end program test_char _Specific names_: ! Name Argument Return type Standard ! `CHAR(I)' `INTEGER I' `CHARACTER(LEN=1)'F77 and later _Note_: See *note ICHAR:: for a discussion of converting between numerical *************** _Note_: *** 8200,8209 **** _See also_: *note ACHAR::, *note IACHAR::, *note ICHAR::  File: gfortran.info, Node: CHDIR, Next: CHMOD, Prev: CHAR, Up: Intrinsic Procedures ! 9.56 'CHDIR' -- Change working directory ======================================== _Description_: --- 8276,8286 ---- _See also_: *note ACHAR::, *note IACHAR::, *note ICHAR:: +  File: gfortran.info, Node: CHDIR, Next: CHMOD, Prev: CHAR, Up: Intrinsic Procedures ! 9.56 `CHDIR' -- Change working directory ======================================== _Description_: *************** _Class_: *** 8219,8234 **** Subroutine, function _Syntax_: ! 'CALL CHDIR(NAME [, STATUS])' ! 'STATUS = CHDIR(NAME)' _Arguments_: ! NAME The type shall be 'CHARACTER' of default kind ! and shall specify a valid path within the file ! system. ! STATUS (Optional) 'INTEGER' status flag of the default ! kind. Returns 0 on success, and a system ! specific and nonzero error code otherwise. _Example_: PROGRAM test_chdir --- 8296,8311 ---- Subroutine, function _Syntax_: ! `CALL CHDIR(NAME [, STATUS])' ! `STATUS = CHDIR(NAME)' _Arguments_: ! NAME The type shall be `CHARACTER' of default kind ! and shall specify a valid path within the file ! system. ! STATUS (Optional) `INTEGER' status flag of the default ! kind. Returns 0 on success, and a system ! specific and nonzero error code otherwise. _Example_: PROGRAM test_chdir *************** _See also_: *** 8246,8256 ****  File: gfortran.info, Node: CHMOD, Next: CMPLX, Prev: CHDIR, Up: Intrinsic Procedures ! 9.57 'CHMOD' -- Change access permissions of files ================================================== _Description_: ! 'CHMOD' changes the permissions of a file. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 8323,8333 ----  File: gfortran.info, Node: CHMOD, Next: CMPLX, Prev: CHDIR, Up: Intrinsic Procedures ! 9.57 `CHMOD' -- Change access permissions of files ================================================== _Description_: ! `CHMOD' changes the permissions of a file. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 8262,8301 **** Subroutine, function _Syntax_: ! 'CALL CHMOD(NAME, MODE[, STATUS])' ! 'STATUS = CHMOD(NAME, MODE)' _Arguments_: ! ! NAME Scalar 'CHARACTER' of default kind with the file ! name. Trailing blanks are ignored unless the ! character 'achar(0)' is present, then all ! characters up to and excluding 'achar(0)' are ! used as the file name. ! ! MODE Scalar 'CHARACTER' of default kind giving the ! file permission. MODE uses the same syntax as ! the 'chmod' utility as defined by the POSIX ! standard. The argument shall either be a string ! of a nonnegative octal number or a symbolic ! mode. ! ! STATUS (optional) scalar 'INTEGER', which is '0' on ! success and nonzero otherwise. _Return value_: ! In either syntax, STATUS is set to '0' on success and nonzero otherwise. _Example_: ! 'CHMOD' as subroutine program chmod_test implicit none integer :: status call chmod('test.dat','u+x',status) print *, 'Status: ', status end program chmod_test ! 'CHMOD' as function: program chmod_test implicit none integer :: status --- 8339,8375 ---- Subroutine, function _Syntax_: ! `CALL CHMOD(NAME, MODE[, STATUS])' ! `STATUS = CHMOD(NAME, MODE)' _Arguments_: ! NAME Scalar `CHARACTER' of default kind with the ! file name. Trailing blanks are ignored unless ! the character `achar(0)' is present, then all ! characters up to and excluding `achar(0)' are ! used as the file name. ! MODE Scalar `CHARACTER' of default kind giving the ! file permission. MODE uses the same syntax as ! the `chmod' utility as defined by the POSIX ! standard. The argument shall either be a ! string of a nonnegative octal number or a ! symbolic mode. ! STATUS (optional) scalar `INTEGER', which is `0' on ! success and nonzero otherwise. _Return value_: ! In either syntax, STATUS is set to `0' on success and nonzero otherwise. _Example_: ! `CHMOD' as subroutine program chmod_test implicit none integer :: status call chmod('test.dat','u+x',status) print *, 'Status: ', status end program chmod_test ! `CHMOD' as function: program chmod_test implicit none integer :: status *************** _Example_: *** 8303,8320 **** print *, 'Status: ', status end program chmod_test  File: gfortran.info, Node: CMPLX, Next: CO_BROADCAST, Prev: CHMOD, Up: Intrinsic Procedures ! 9.58 'CMPLX' -- Complex conversion function =========================================== _Description_: ! 'CMPLX(X [, Y [, KIND]])' returns a complex number where X is converted to the real component. If Y is present it is converted ! to the imaginary component. If Y is not present then the imaginary ! component is set to 0.0. If X is complex then Y must not be ! present. _Standard_: Fortran 77 and later --- 8377,8395 ---- print *, 'Status: ', status end program chmod_test +  File: gfortran.info, Node: CMPLX, Next: CO_BROADCAST, Prev: CHMOD, Up: Intrinsic Procedures ! 9.58 `CMPLX' -- Complex conversion function =========================================== _Description_: ! `CMPLX(X [, Y [, KIND]])' returns a complex number where X is converted to the real component. If Y is present it is converted ! to the imaginary component. If Y is not present then the ! imaginary component is set to 0.0. If X is complex then Y must ! not be present. _Standard_: Fortran 77 and later *************** _Class_: *** 8323,8342 **** Elemental function _Syntax_: ! 'RESULT = CMPLX(X [, Y [, KIND]])' _Arguments_: ! X The type may be 'INTEGER', 'REAL', or 'COMPLEX'. ! Y (Optional; only allowed if X is not 'COMPLEX'.) ! May be 'INTEGER' or 'REAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of 'COMPLEX' type, with a kind equal to KIND if ! it is specified. If KIND is not specified, the result is of the ! default 'COMPLEX' kind, regardless of the kinds of X and Y. _Example_: program test_cmplx --- 8398,8418 ---- Elemental function _Syntax_: ! `RESULT = CMPLX(X [, Y [, KIND]])' _Arguments_: ! X The type may be `INTEGER', `REAL', or ! `COMPLEX'. ! Y (Optional; only allowed if X is not ! `COMPLEX'.) May be `INTEGER' or `REAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of `COMPLEX' type, with a kind equal to KIND ! if it is specified. If KIND is not specified, the result is of ! the default `COMPLEX' kind, regardless of the kinds of X and Y. _Example_: program test_cmplx *************** _See also_: *** 8353,8368 ****  File: gfortran.info, Node: CO_BROADCAST, Next: CO_MAX, Prev: CMPLX, Up: Intrinsic Procedures ! 9.59 'CO_BROADCAST' -- Copy a value to all images the current set of images =========================================================================== _Description_: ! 'CO_BROADCAST' copies the value of argument A on the image with ! image index 'SOURCE_IMAGE' to all images in the current team. A becomes defined as if by intrinsic assignment. If the execution was successful and STAT is present, it is assigned the value zero. ! If the execution failed, STAT gets assigned a nonzero value and, if ! present, ERRMSG gets assigned a value describing the occurred error. _Standard_: --- 8429,8444 ----  File: gfortran.info, Node: CO_BROADCAST, Next: CO_MAX, Prev: CMPLX, Up: Intrinsic Procedures ! 9.59 `CO_BROADCAST' -- Copy a value to all images the current set of images =========================================================================== _Description_: ! `CO_BROADCAST' copies the value of argument A on the image with ! image index `SOURCE_IMAGE' to all images in the current team. A becomes defined as if by intrinsic assignment. If the execution was successful and STAT is present, it is assigned the value zero. ! If the execution failed, STAT gets assigned a nonzero value and, ! if present, ERRMSG gets assigned a value describing the occurred error. _Standard_: *************** _Class_: *** 8372,8389 **** Collective subroutine _Syntax_: ! 'CALL CO_BROADCAST(A, SOURCE_IMAGE [, STAT, ERRMSG])' _Arguments_: ! A INTENT(INOUT) argument; shall have the same ! dynamic type and type paramters on all images of ! the current team. If it is an array, it shall ! have the same shape on all images. ! SOURCE_IMAGEa scalar integer expression. It shall have the ! same the same value on all images and refer to ! an image of the current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test --- 8448,8465 ---- Collective subroutine _Syntax_: ! `CALL CO_BROADCAST(A, SOURCE_IMAGE [, STAT, ERRMSG])' _Arguments_: ! A INTENT(INOUT) argument; shall have the same ! dynamic type and type paramters on all images ! of the current team. If it is an array, it ! shall have the same shape on all images. ! SOURCE_IMAGEa scalar integer expression. It shall have ! the same the same value on all images and ! refer to an image of the current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test *************** _See also_: *** 8401,8419 ****  File: gfortran.info, Node: CO_MAX, Next: CO_MIN, Prev: CO_BROADCAST, Up: Intrinsic Procedures ! 9.60 'CO_MAX' -- Maximal value on the current set of images =========================================================== _Description_: ! 'CO_MAX' determines element-wise the maximal value of A on all images of the current team. If RESULT_IMAGE is present, the maximum values are returned in A on the specified image only and the value of A on the other images become undefined. If RESULT_IMAGE is not present, the value is returned on all images. ! If the execution was successful and STAT is present, it is assigned ! the value zero. If the execution failed, STAT gets assigned a ! nonzero value and, if present, ERRMSG gets assigned a value ! describing the occurred error. _Standard_: Technical Specification (TS) 18508 or later --- 8477,8495 ----  File: gfortran.info, Node: CO_MAX, Next: CO_MIN, Prev: CO_BROADCAST, Up: Intrinsic Procedures ! 9.60 `CO_MAX' -- Maximal value on the current set of images =========================================================== _Description_: ! `CO_MAX' determines element-wise the maximal value of A on all images of the current team. If RESULT_IMAGE is present, the maximum values are returned in A on the specified image only and the value of A on the other images become undefined. If RESULT_IMAGE is not present, the value is returned on all images. ! If the execution was successful and STAT is present, it is ! assigned the value zero. If the execution failed, STAT gets ! assigned a nonzero value and, if present, ERRMSG gets assigned a ! value describing the occurred error. _Standard_: Technical Specification (TS) 18508 or later *************** _Class_: *** 8422,8439 **** Collective subroutine _Syntax_: ! 'CALL CO_MAX(A [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A shall be an integer, real or character variable, ! which has the same type and type parameters on ! all images of the team. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test --- 8498,8515 ---- Collective subroutine _Syntax_: ! `CALL CO_MAX(A [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A shall be an integer, real or character ! variable, which has the same type and type ! parameters on all images of the team. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test *************** _See also_: *** 8452,8470 ****  File: gfortran.info, Node: CO_MIN, Next: CO_REDUCE, Prev: CO_MAX, Up: Intrinsic Procedures ! 9.61 'CO_MIN' -- Minimal value on the current set of images =========================================================== _Description_: ! 'CO_MIN' determines element-wise the minimal value of A on all images of the current team. If RESULT_IMAGE is present, the minimal values are returned in A on the specified image only and the value of A on the other images become undefined. If RESULT_IMAGE is not present, the value is returned on all images. ! If the execution was successful and STAT is present, it is assigned ! the value zero. If the execution failed, STAT gets assigned a ! nonzero value and, if present, ERRMSG gets assigned a value ! describing the occurred error. _Standard_: Technical Specification (TS) 18508 or later --- 8528,8546 ----  File: gfortran.info, Node: CO_MIN, Next: CO_REDUCE, Prev: CO_MAX, Up: Intrinsic Procedures ! 9.61 `CO_MIN' -- Minimal value on the current set of images =========================================================== _Description_: ! `CO_MIN' determines element-wise the minimal value of A on all images of the current team. If RESULT_IMAGE is present, the minimal values are returned in A on the specified image only and the value of A on the other images become undefined. If RESULT_IMAGE is not present, the value is returned on all images. ! If the execution was successful and STAT is present, it is ! assigned the value zero. If the execution failed, STAT gets ! assigned a nonzero value and, if present, ERRMSG gets assigned a ! value describing the occurred error. _Standard_: Technical Specification (TS) 18508 or later *************** _Class_: *** 8473,8490 **** Collective subroutine _Syntax_: ! 'CALL CO_MIN(A [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A shall be an integer, real or character variable, ! which has the same type and type parameters on ! all images of the team. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test --- 8549,8566 ---- Collective subroutine _Syntax_: ! `CALL CO_MIN(A [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A shall be an integer, real or character ! variable, which has the same type and type ! parameters on all images of the team. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test *************** _See also_: *** 8503,8524 ****  File: gfortran.info, Node: CO_REDUCE, Next: CO_SUM, Prev: CO_MIN, Up: Intrinsic Procedures ! 9.62 'CO_REDUCE' -- Reduction of values on the current set of images ==================================================================== _Description_: ! 'CO_REDUCE' determines element-wise the reduction of the value of A on all images of the current team. The pure function passed as OPERATOR is used to pairwise reduce the values of A by passing either the value of A of different images or the result values of such a reduction as argument. If A is an array, the deduction is ! done element wise. If RESULT_IMAGE is present, the result values ! are returned in A on the specified image only and the value of A on ! the other images become undefined. If RESULT_IMAGE is not present, ! the value is returned on all images. If the execution was ! successful and STAT is present, it is assigned the value zero. If ! the execution failed, STAT gets assigned a nonzero value and, if ! present, ERRMSG gets assigned a value describing the occurred error. _Standard_: --- 8579,8600 ----  File: gfortran.info, Node: CO_REDUCE, Next: CO_SUM, Prev: CO_MIN, Up: Intrinsic Procedures ! 9.62 `CO_REDUCE' -- Reduction of values on the current set of images ==================================================================== _Description_: ! `CO_REDUCE' determines element-wise the reduction of the value of A on all images of the current team. The pure function passed as OPERATOR is used to pairwise reduce the values of A by passing either the value of A of different images or the result values of such a reduction as argument. If A is an array, the deduction is ! done element wise. If RESULT_IMAGE is present, the result values ! are returned in A on the specified image only and the value of A ! on the other images become undefined. If RESULT_IMAGE is not ! present, the value is returned on all images. If the execution ! was successful and STAT is present, it is assigned the value zero. ! If the execution failed, STAT gets assigned a nonzero value and, ! if present, ERRMSG gets assigned a value describing the occurred error. _Standard_: *************** _Class_: *** 8528,8559 **** Collective subroutine _Syntax_: ! 'CALL CO_REDUCE(A, OPERATOR, [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A is an 'INTENT(INOUT)' argument and shall be ! nonpolymorphic. If it is allocatable, it shall ! be allocated; if it is a pointer, it shall be ! associated. A shall have the same type and type ! parameters on all images of the team; if it is ! an array, it shall have the same shape on all ! images. ! OPERATOR pure function with two scalar nonallocatable ! arguments, which shall be nonpolymorphic and ! have the same type and type parameters as A. ! The function shall return a nonallocatable ! scalar of the same type and type parameters as ! A. The function shall be the same on all images ! and with regards to the arguments mathematically ! commutative and associative. Note that OPERATOR ! may not be an elemental function, unless it is ! an intrisic function. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test --- 8604,8635 ---- Collective subroutine _Syntax_: ! `CALL CO_REDUCE(A, OPERATOR, [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A is an `INTENT(INOUT)' argument and shall be ! nonpolymorphic. If it is allocatable, it shall ! be allocated; if it is a pointer, it shall be ! associated. A shall have the same type and ! type parameters on all images of the team; if ! it is an array, it shall have the same shape ! on all images. ! OPERATOR pure function with two scalar nonallocatable ! arguments, which shall be nonpolymorphic and ! have the same type and type parameters as A. ! The function shall return a nonallocatable ! scalar of the same type and type parameters as ! A. The function shall be the same on all ! images and with regards to the arguments ! mathematically commutative and associative. ! Note that OPERATOR may not be an elemental ! function, unless it is an intrisic function. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test *************** _See also_: *** 8584,8598 ****  File: gfortran.info, Node: CO_SUM, Next: COMMAND_ARGUMENT_COUNT, Prev: CO_REDUCE, Up: Intrinsic Procedures ! 9.63 'CO_SUM' -- Sum of values on the current set of images =========================================================== _Description_: ! 'CO_SUM' sums up the values of each element of A on all images of ! the current team. If RESULT_IMAGE is present, the summed-up values ! are returned in A on the specified image only and the value of A on ! the other images become undefined. If RESULT_IMAGE is not present, ! the value is returned on all images. If the execution was successful and STAT is present, it is assigned the value zero. If the execution failed, STAT gets assigned a nonzero value and, if present, ERRMSG gets assigned a value describing the occurred --- 8660,8674 ----  File: gfortran.info, Node: CO_SUM, Next: COMMAND_ARGUMENT_COUNT, Prev: CO_REDUCE, Up: Intrinsic Procedures ! 9.63 `CO_SUM' -- Sum of values on the current set of images =========================================================== _Description_: ! `CO_SUM' sums up the values of each element of A on all images of ! the current team. If RESULT_IMAGE is present, the summed-up ! values are returned in A on the specified image only and the value ! of A on the other images become undefined. If RESULT_IMAGE is not ! present, the value is returned on all images. If the execution was successful and STAT is present, it is assigned the value zero. If the execution failed, STAT gets assigned a nonzero value and, if present, ERRMSG gets assigned a value describing the occurred *************** _Class_: *** 8605,8622 **** Collective subroutine _Syntax_: ! 'CALL CO_MIN(A [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A shall be an integer, real or complex variable, ! which has the same type and type parameters on ! all images of the team. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test --- 8681,8698 ---- Collective subroutine _Syntax_: ! `CALL CO_MIN(A [, RESULT_IMAGE, STAT, ERRMSG])' _Arguments_: ! A shall be an integer, real or complex variable, ! which has the same type and type parameters on ! all images of the team. RESULT_IMAGE(optional) a scalar integer expression; if ! present, it shall have the same the same value ! on all images and refer to an image of the ! current team. ! STAT (optional) a scalar integer variable ! ERRMSG (optional) a scalar character variable _Example_: program test *************** _See also_: *** 8635,8645 ****  File: gfortran.info, Node: COMMAND_ARGUMENT_COUNT, Next: COMPILER_OPTIONS, Prev: CO_SUM, Up: Intrinsic Procedures ! 9.64 'COMMAND_ARGUMENT_COUNT' -- Get number of command line arguments ===================================================================== _Description_: ! 'COMMAND_ARGUMENT_COUNT' returns the number of arguments passed on the command line when the containing program was invoked. _Standard_: --- 8711,8721 ----  File: gfortran.info, Node: COMMAND_ARGUMENT_COUNT, Next: COMPILER_OPTIONS, Prev: CO_SUM, Up: Intrinsic Procedures ! 9.64 `COMMAND_ARGUMENT_COUNT' -- Get number of command line arguments ===================================================================== _Description_: ! `COMMAND_ARGUMENT_COUNT' returns the number of arguments passed on the command line when the containing program was invoked. _Standard_: *************** _Class_: *** 8649,8661 **** Inquiry function _Syntax_: ! 'RESULT = COMMAND_ARGUMENT_COUNT()' _Arguments_: ! None _Return value_: ! The return value is an 'INTEGER' of default kind. _Example_: program test_command_argument_count --- 8725,8737 ---- Inquiry function _Syntax_: ! `RESULT = COMMAND_ARGUMENT_COUNT()' _Arguments_: ! None _Return value_: ! The return value is an `INTEGER' of default kind. _Example_: program test_command_argument_count *************** _See also_: *** 8670,8690 ****  File: gfortran.info, Node: COMPILER_OPTIONS, Next: COMPILER_VERSION, Prev: COMMAND_ARGUMENT_COUNT, Up: Intrinsic Procedures ! 9.65 'COMPILER_OPTIONS' -- Options passed to the compiler ========================================================= _Description_: ! 'COMPILER_OPTIONS' returns a string with the options used for compiling. _Standard_: Fortran 2008 _Class_: ! Inquiry function of the module 'ISO_FORTRAN_ENV' _Syntax_: ! 'STR = COMPILER_OPTIONS()' _Arguments_: None. --- 8746,8766 ----  File: gfortran.info, Node: COMPILER_OPTIONS, Next: COMPILER_VERSION, Prev: COMMAND_ARGUMENT_COUNT, Up: Intrinsic Procedures ! 9.65 `COMPILER_OPTIONS' -- Options passed to the compiler ========================================================= _Description_: ! `COMPILER_OPTIONS' returns a string with the options used for compiling. _Standard_: Fortran 2008 _Class_: ! Inquiry function of the module `ISO_FORTRAN_ENV' _Syntax_: ! `STR = COMPILER_OPTIONS()' _Arguments_: None. *************** _Arguments_: *** 8692,8698 **** _Return value_: The return value is a default-kind string with system-dependent length. It contains the compiler flags used to compile the file, ! which called the 'COMPILER_OPTIONS' intrinsic. _Example_: use iso_fortran_env --- 8768,8774 ---- _Return value_: The return value is a default-kind string with system-dependent length. It contains the compiler flags used to compile the file, ! which called the `COMPILER_OPTIONS' intrinsic. _Example_: use iso_fortran_env *************** _See also_: *** 8707,8727 ****  File: gfortran.info, Node: COMPILER_VERSION, Next: COMPLEX, Prev: COMPILER_OPTIONS, Up: Intrinsic Procedures ! 9.66 'COMPILER_VERSION' -- Compiler version string ================================================== _Description_: ! 'COMPILER_VERSION' returns a string with the name and the version of the compiler. _Standard_: Fortran 2008 _Class_: ! Inquiry function of the module 'ISO_FORTRAN_ENV' _Syntax_: ! 'STR = COMPILER_VERSION()' _Arguments_: None. --- 8783,8803 ----  File: gfortran.info, Node: COMPILER_VERSION, Next: COMPLEX, Prev: COMPILER_OPTIONS, Up: Intrinsic Procedures ! 9.66 `COMPILER_VERSION' -- Compiler version string ================================================== _Description_: ! `COMPILER_VERSION' returns a string with the name and the version of the compiler. _Standard_: Fortran 2008 _Class_: ! Inquiry function of the module `ISO_FORTRAN_ENV' _Syntax_: ! `STR = COMPILER_VERSION()' _Arguments_: None. *************** _See also_: *** 8744,8754 ****  File: gfortran.info, Node: COMPLEX, Next: CONJG, Prev: COMPILER_VERSION, Up: Intrinsic Procedures ! 9.67 'COMPLEX' -- Complex conversion function ============================================= _Description_: ! 'COMPLEX(X, Y)' returns a complex number where X is converted to the real component and Y is converted to the imaginary component. _Standard_: --- 8820,8830 ----  File: gfortran.info, Node: COMPLEX, Next: CONJG, Prev: COMPILER_VERSION, Up: Intrinsic Procedures ! 9.67 `COMPLEX' -- Complex conversion function ============================================= _Description_: ! `COMPLEX(X, Y)' returns a complex number where X is converted to the real component and Y is converted to the imaginary component. _Standard_: *************** _Class_: *** 8758,8776 **** Elemental function _Syntax_: ! 'RESULT = COMPLEX(X, Y)' _Arguments_: ! X The type may be 'INTEGER' or 'REAL'. ! Y The type may be 'INTEGER' or 'REAL'. _Return value_: ! If X and Y are both of 'INTEGER' type, then the return value is of ! default 'COMPLEX' type. ! If X and Y are of 'REAL' type, or one is of 'REAL' type and one is ! of 'INTEGER' type, then the return value is of 'COMPLEX' type with ! a kind equal to that of the 'REAL' argument with the highest precision. _Example_: --- 8834,8852 ---- Elemental function _Syntax_: ! `RESULT = COMPLEX(X, Y)' _Arguments_: ! X The type may be `INTEGER' or `REAL'. ! Y The type may be `INTEGER' or `REAL'. _Return value_: ! If X and Y are both of `INTEGER' type, then the return value is of ! default `COMPLEX' type. ! If X and Y are of `REAL' type, or one is of `REAL' type and one is ! of `INTEGER' type, then the return value is of `COMPLEX' type with ! a kind equal to that of the `REAL' argument with the highest precision. _Example_: *************** _See also_: *** 8786,8797 ****  File: gfortran.info, Node: CONJG, Next: COS, Prev: COMPLEX, Up: Intrinsic Procedures ! 9.68 'CONJG' -- Complex conjugate function ========================================== _Description_: ! 'CONJG(Z)' returns the conjugate of Z. If Z is '(x, y)' then the ! result is '(x, -y)' _Standard_: Fortran 77 and later, has overloads that are GNU extensions --- 8862,8873 ----  File: gfortran.info, Node: CONJG, Next: COS, Prev: COMPLEX, Up: Intrinsic Procedures ! 9.68 `CONJG' -- Complex conjugate function ========================================== _Description_: ! `CONJG(Z)' returns the conjugate of Z. If Z is `(x, y)' then the ! result is `(x, -y)' _Standard_: Fortran 77 and later, has overloads that are GNU extensions *************** _Class_: *** 8800,8812 **** Elemental function _Syntax_: ! 'Z = CONJG(Z)' _Arguments_: ! Z The type shall be 'COMPLEX'. _Return value_: ! The return value is of type 'COMPLEX'. _Example_: program test_conjg --- 8876,8888 ---- Elemental function _Syntax_: ! `Z = CONJG(Z)' _Arguments_: ! Z The type shall be `COMPLEX'. _Return value_: ! The return value is of type `COMPLEX'. _Example_: program test_conjg *************** _Example_: *** 8819,8837 **** end program test_conjg _Specific names_: ! Name Argument Return type Standard ! 'CONJG(Z)' 'COMPLEX Z' 'COMPLEX' GNU extension ! 'DCONJG(Z)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! Z'  File: gfortran.info, Node: COS, Next: COSH, Prev: CONJG, Up: Intrinsic Procedures ! 9.69 'COS' -- Cosine function ============================= _Description_: ! 'COS(X)' computes the cosine of X. _Standard_: Fortran 77 and later, has overloads that are GNU extensions --- 8895,8913 ---- end program test_conjg _Specific names_: ! Name Argument Return type Standard ! `CONJG(Z)' `COMPLEX Z' `COMPLEX' GNU extension ! `DCONJG(Z)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! Z'  File: gfortran.info, Node: COS, Next: COSH, Prev: CONJG, Up: Intrinsic Procedures ! 9.69 `COS' -- Cosine function ============================= _Description_: ! `COS(X)' computes the cosine of X. _Standard_: Fortran 77 and later, has overloads that are GNU extensions *************** _Class_: *** 8840,8854 **** Elemental function _Syntax_: ! 'RESULT = COS(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value is of the same type and kind as X. The real part ! of the result is in radians. If X is of the type 'REAL', the ! return value lies in the range -1 \leq \cos (x) \leq 1. _Example_: program test_cos --- 8916,8930 ---- Elemental function _Syntax_: ! `RESULT = COS(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value is of the same type and kind as X. The real part ! of the result is in radians. If X is of the type `REAL', the ! return value lies in the range -1 \leq \cos (x) \leq 1. _Example_: program test_cos *************** _Example_: *** 8857,8885 **** end program test_cos _Specific names_: ! Name Argument Return type Standard ! 'COS(X)' 'REAL(4) X' 'REAL(4)' Fortran 77 and ! later ! 'DCOS(X)' 'REAL(8) X' 'REAL(8)' Fortran 77 and ! later ! 'CCOS(X)' 'COMPLEX(4) 'COMPLEX(4)' Fortran 77 and ! X' later ! 'ZCOS(X)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! X' ! 'CDCOS(X)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! X' _See also_: Inverse function: *note ACOS::  File: gfortran.info, Node: COSH, Next: COUNT, Prev: COS, Up: Intrinsic Procedures ! 9.70 'COSH' -- Hyperbolic cosine function ========================================= _Description_: ! 'COSH(X)' computes the hyperbolic cosine of X. _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later --- 8933,8962 ---- end program test_cos _Specific names_: ! Name Argument Return type Standard ! `COS(X)' `REAL(4) X' `REAL(4)' Fortran 77 and ! later ! `DCOS(X)' `REAL(8) X' `REAL(8)' Fortran 77 and ! later ! `CCOS(X)' `COMPLEX(4) `COMPLEX(4)' Fortran 77 and ! X' later ! `ZCOS(X)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! X' ! `CDCOS(X)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! X' _See also_: Inverse function: *note ACOS:: +  File: gfortran.info, Node: COSH, Next: COUNT, Prev: COS, Up: Intrinsic Procedures ! 9.70 `COSH' -- Hyperbolic cosine function ========================================= _Description_: ! `COSH(X)' computes the hyperbolic cosine of X. _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later *************** _Class_: *** 8888,8901 **** Elemental function _Syntax_: ! 'X = COSH(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value has same type and kind as X. If X is complex, the ! imaginary part of the result is in radians. If X is 'REAL', the return value has a lower bound of one, \cosh (x) \geq 1. _Example_: --- 8965,8978 ---- Elemental function _Syntax_: ! `X = COSH(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value has same type and kind as X. If X is complex, the ! imaginary part of the result is in radians. If X is `REAL', the return value has a lower bound of one, \cosh (x) \geq 1. _Example_: *************** _Example_: *** 8905,8932 **** end program test_cosh _Specific names_: ! Name Argument Return type Standard ! 'COSH(X)' 'REAL(4) X' 'REAL(4)' Fortran 77 and ! later ! 'DCOSH(X)' 'REAL(8) X' 'REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note ACOSH::  File: gfortran.info, Node: COUNT, Next: CPU_TIME, Prev: COSH, Up: Intrinsic Procedures ! 9.71 'COUNT' -- Count function ============================== _Description_: ! ! Counts the number of '.TRUE.' elements in a logical MASK, or, if the DIM argument is supplied, counts the number of elements along each row of the array in the DIM direction. If the array has zero ! size, or all of the elements of MASK are '.FALSE.', then the result ! is '0'. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later --- 8982,9009 ---- end program test_cosh _Specific names_: ! Name Argument Return type Standard ! `COSH(X)' `REAL(4) X' `REAL(4)' Fortran 77 and ! later ! `DCOSH(X)' `REAL(8) X' `REAL(8)' Fortran 77 and ! later _See also_: Inverse function: *note ACOSH:: +  File: gfortran.info, Node: COUNT, Next: CPU_TIME, Prev: COSH, Up: Intrinsic Procedures ! 9.71 `COUNT' -- Count function ============================== _Description_: ! Counts the number of `.TRUE.' elements in a logical MASK, or, if the DIM argument is supplied, counts the number of elements along each row of the array in the DIM direction. If the array has zero ! size, or all of the elements of MASK are `.FALSE.', then the ! result is `0'. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later *************** _Class_: *** 8935,8951 **** Transformational function _Syntax_: ! 'RESULT = COUNT(MASK [, DIM, KIND])' _Arguments_: ! MASK The type shall be 'LOGICAL'. ! DIM (Optional) The type shall be 'INTEGER'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is present, the result is an array with a rank one less than the rank of ARRAY, and a size corresponding to the shape of ARRAY with the --- 9012,9028 ---- Transformational function _Syntax_: ! `RESULT = COUNT(MASK [, DIM, KIND])' _Arguments_: ! MASK The type shall be `LOGICAL'. ! DIM (Optional) The type shall be `INTEGER'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is present, the result is an array with a rank one less than the rank of ARRAY, and a size corresponding to the shape of ARRAY with the *************** _Example_: *** 8977,8996 ****  File: gfortran.info, Node: CPU_TIME, Next: CSHIFT, Prev: COUNT, Up: Intrinsic Procedures ! 9.72 'CPU_TIME' -- CPU elapsed time in seconds ============================================== _Description_: ! Returns a 'REAL' value representing the elapsed CPU time in seconds. This is useful for testing segments of code to determine execution time. If a time source is available, time will be reported with ! microsecond resolution. If no time source is available, TIME is ! set to '-1.0'. Note that TIME may contain a, system dependent, arbitrary offset ! and may not start with '0.0'. For 'CPU_TIME', the absolute value is meaningless, only differences between subsequent calls to this subroutine, as shown in the example below, should be used. --- 9054,9073 ----  File: gfortran.info, Node: CPU_TIME, Next: CSHIFT, Prev: COUNT, Up: Intrinsic Procedures ! 9.72 `CPU_TIME' -- CPU elapsed time in seconds ============================================== _Description_: ! Returns a `REAL' value representing the elapsed CPU time in seconds. This is useful for testing segments of code to determine execution time. If a time source is available, time will be reported with ! microsecond resolution. If no time source is available, TIME is ! set to `-1.0'. Note that TIME may contain a, system dependent, arbitrary offset ! and may not start with `0.0'. For `CPU_TIME', the absolute value is meaningless, only differences between subsequent calls to this subroutine, as shown in the example below, should be used. *************** _Class_: *** 9001,9010 **** Subroutine _Syntax_: ! 'CALL CPU_TIME(TIME)' _Arguments_: ! TIME The type shall be 'REAL' with 'INTENT(OUT)'. _Return value_: None --- 9078,9087 ---- Subroutine _Syntax_: ! `CALL CPU_TIME(TIME)' _Arguments_: ! TIME The type shall be `REAL' with `INTENT(OUT)'. _Return value_: None *************** _See also_: *** 9024,9042 ****  File: gfortran.info, Node: CSHIFT, Next: CTIME, Prev: CPU_TIME, Up: Intrinsic Procedures ! 9.73 'CSHIFT' -- Circular shift elements of an array ==================================================== _Description_: ! 'CSHIFT(ARRAY, SHIFT [, DIM])' performs a circular shift on ! elements of ARRAY along the dimension of DIM. If DIM is omitted it ! is taken to be '1'. DIM is a scalar of type 'INTEGER' in the range ! of 1 \leq DIM \leq n) where n is the rank of ARRAY. If the rank of ! ARRAY is one, then all elements of ARRAY are shifted by SHIFT ! places. If rank is greater than one, then all complete rank one ! sections of ARRAY along the given dimension are shifted. Elements ! shifted out one end of each rank one section are shifted back in ! the other end. _Standard_: Fortran 95 and later --- 9101,9119 ----  File: gfortran.info, Node: CSHIFT, Next: CTIME, Prev: CPU_TIME, Up: Intrinsic Procedures ! 9.73 `CSHIFT' -- Circular shift elements of an array ==================================================== _Description_: ! `CSHIFT(ARRAY, SHIFT [, DIM])' performs a circular shift on ! elements of ARRAY along the dimension of DIM. If DIM is omitted ! it is taken to be `1'. DIM is a scalar of type `INTEGER' in the ! range of 1 \leq DIM \leq n) where n is the rank of ARRAY. If the ! rank of ARRAY is one, then all elements of ARRAY are shifted by ! SHIFT places. If rank is greater than one, then all complete rank ! one sections of ARRAY along the given dimension are shifted. ! Elements shifted out one end of each rank one section are shifted ! back in the other end. _Standard_: Fortran 95 and later *************** _Class_: *** 9045,9056 **** Transformational function _Syntax_: ! 'RESULT = CSHIFT(ARRAY, SHIFT [, DIM])' _Arguments_: ! ARRAY Shall be an array of any type. ! SHIFT The type shall be 'INTEGER'. ! DIM The type shall be 'INTEGER'. _Return value_: Returns an array of same type and rank as the ARRAY argument. --- 9122,9133 ---- Transformational function _Syntax_: ! `RESULT = CSHIFT(ARRAY, SHIFT [, DIM])' _Arguments_: ! ARRAY Shall be an array of any type. ! SHIFT The type shall be `INTEGER'. ! DIM The type shall be `INTEGER'. _Return value_: Returns an array of same type and rank as the ARRAY argument. *************** _Example_: *** 9072,9083 ****  File: gfortran.info, Node: CTIME, Next: DATE_AND_TIME, Prev: CSHIFT, Up: Intrinsic Procedures ! 9.74 'CTIME' -- Convert a time into a string ============================================ _Description_: ! 'CTIME' converts a system time value, such as returned by 'TIME8', ! to a string. The output will be of the form 'Sat Aug 19 18:13:14 1995'. This intrinsic is provided in both subroutine and function forms; --- 9149,9160 ----  File: gfortran.info, Node: CTIME, Next: DATE_AND_TIME, Prev: CSHIFT, Up: Intrinsic Procedures ! 9.74 `CTIME' -- Convert a time into a string ============================================ _Description_: ! `CTIME' converts a system time value, such as returned by `TIME8', ! to a string. The output will be of the form `Sat Aug 19 18:13:14 1995'. This intrinsic is provided in both subroutine and function forms; *************** _Class_: *** 9090,9105 **** Subroutine, function _Syntax_: ! 'CALL CTIME(TIME, RESULT)'. ! 'RESULT = CTIME(TIME)'. _Arguments_: ! TIME The type shall be of type 'INTEGER'. ! RESULT The type shall be of type 'CHARACTER' and of ! default kind. It is an 'INTENT(OUT)' argument. ! If the length of this variable is too short for ! the time and date string to fit completely, it ! will be blank on procedure return. _Return value_: The converted date and time as a string. --- 9167,9183 ---- Subroutine, function _Syntax_: ! `CALL CTIME(TIME, RESULT)'. ! `RESULT = CTIME(TIME)'. _Arguments_: ! TIME The type shall be of type `INTEGER'. ! RESULT The type shall be of type `CHARACTER' and of ! default kind. It is an `INTENT(OUT)' argument. ! If the length of this variable is too short ! for the time and date string to fit ! completely, it will be blank on procedure ! return. _Return value_: The converted date and time as a string. *************** _Example_: *** 9117,9151 **** end program test_ctime _See Also_: ! *note DATE_AND_TIME::, *note GMTIME::, *note LTIME::, *note TIME::, ! *note TIME8::  File: gfortran.info, Node: DATE_AND_TIME, Next: DBLE, Prev: CTIME, Up: Intrinsic Procedures ! 9.75 'DATE_AND_TIME' -- Date and time subroutine ================================================ _Description_: ! 'DATE_AND_TIME(DATE, TIME, ZONE, VALUES)' gets the corresponding date and time information from the real-time system clock. DATE is ! 'INTENT(OUT)' and has form ccyymmdd. TIME is 'INTENT(OUT)' and has ! form hhmmss.sss. ZONE is 'INTENT(OUT)' and has form (+-)hhmm, representing the difference with respect to Coordinated Universal ! Time (UTC). Unavailable time and date parameters return blanks. ! VALUES is 'INTENT(OUT)' and provides the following: ! 'VALUE(1)': The year ! 'VALUE(2)': The month ! 'VALUE(3)': The day of the month ! 'VALUE(4)': Time difference with UTC in ! minutes ! 'VALUE(5)': The hour of the day ! 'VALUE(6)': The minutes of the hour ! 'VALUE(7)': The seconds of the minute ! 'VALUE(8)': The milliseconds of the ! second _Standard_: Fortran 95 and later --- 9195,9229 ---- end program test_ctime _See Also_: ! *note DATE_AND_TIME::, *note GMTIME::, *note LTIME::, *note ! TIME::, *note TIME8::  File: gfortran.info, Node: DATE_AND_TIME, Next: DBLE, Prev: CTIME, Up: Intrinsic Procedures ! 9.75 `DATE_AND_TIME' -- Date and time subroutine ================================================ _Description_: ! `DATE_AND_TIME(DATE, TIME, ZONE, VALUES)' gets the corresponding date and time information from the real-time system clock. DATE is ! `INTENT(OUT)' and has form ccyymmdd. TIME is `INTENT(OUT)' and ! has form hhmmss.sss. ZONE is `INTENT(OUT)' and has form (+-)hhmm, representing the difference with respect to Coordinated Universal ! Time (UTC). Unavailable time and date parameters return blanks. ! VALUES is `INTENT(OUT)' and provides the following: ! `VALUE(1)': The year ! `VALUE(2)': The month ! `VALUE(3)': The day of the month ! `VALUE(4)': Time difference with UTC ! in minutes ! `VALUE(5)': The hour of the day ! `VALUE(6)': The minutes of the hour ! `VALUE(7)': The seconds of the minute ! `VALUE(8)': The milliseconds of the ! second _Standard_: Fortran 95 and later *************** _Class_: *** 9154,9169 **** Subroutine _Syntax_: ! 'CALL DATE_AND_TIME([DATE, TIME, ZONE, VALUES])' _Arguments_: ! DATE (Optional) The type shall be 'CHARACTER(LEN=8)' ! or larger, and of default kind. ! TIME (Optional) The type shall be 'CHARACTER(LEN=10)' ! or larger, and of default kind. ! ZONE (Optional) The type shall be 'CHARACTER(LEN=5)' ! or larger, and of default kind. ! VALUES (Optional) The type shall be 'INTEGER(8)'. _Return value_: None --- 9232,9248 ---- Subroutine _Syntax_: ! `CALL DATE_AND_TIME([DATE, TIME, ZONE, VALUES])' _Arguments_: ! DATE (Optional) The type shall be `CHARACTER(LEN=8)' ! or larger, and of default kind. ! TIME (Optional) The type shall be ! `CHARACTER(LEN=10)' or larger, and of default ! kind. ! ZONE (Optional) The type shall be `CHARACTER(LEN=5)' ! or larger, and of default kind. ! VALUES (Optional) The type shall be `INTEGER(8)'. _Return value_: None *************** _See also_: *** 9189,9199 ****  File: gfortran.info, Node: DBLE, Next: DCMPLX, Prev: DATE_AND_TIME, Up: Intrinsic Procedures ! 9.76 'DBLE' -- Double conversion function ========================================= _Description_: ! 'DBLE(A)' Converts A to double precision real type. _Standard_: Fortran 77 and later --- 9268,9278 ----  File: gfortran.info, Node: DBLE, Next: DCMPLX, Prev: DATE_AND_TIME, Up: Intrinsic Procedures ! 9.76 `DBLE' -- Double conversion function ========================================= _Description_: ! `DBLE(A)' Converts A to double precision real type. _Standard_: Fortran 77 and later *************** _Class_: *** 9202,9212 **** Elemental function _Syntax_: ! 'RESULT = DBLE(A)' _Arguments_: ! A The type shall be 'INTEGER', 'REAL', or ! 'COMPLEX'. _Return value_: The return value is of type double precision real. --- 9281,9291 ---- Elemental function _Syntax_: ! `RESULT = DBLE(A)' _Arguments_: ! A The type shall be `INTEGER', `REAL', or ! `COMPLEX'. _Return value_: The return value is of type double precision real. *************** _See also_: *** 9225,9239 ****  File: gfortran.info, Node: DCMPLX, Next: DIGITS, Prev: DBLE, Up: Intrinsic Procedures ! 9.77 'DCMPLX' -- Double complex conversion function =================================================== _Description_: ! 'DCMPLX(X [,Y])' returns a double complex number where X is converted to the real component. If Y is present it is converted ! to the imaginary component. If Y is not present then the imaginary ! component is set to 0.0. If X is complex then Y must not be ! present. _Standard_: GNU extension --- 9304,9318 ----  File: gfortran.info, Node: DCMPLX, Next: DIGITS, Prev: DBLE, Up: Intrinsic Procedures ! 9.77 `DCMPLX' -- Double complex conversion function =================================================== _Description_: ! `DCMPLX(X [,Y])' returns a double complex number where X is converted to the real component. If Y is present it is converted ! to the imaginary component. If Y is not present then the ! imaginary component is set to 0.0. If X is complex then Y must ! not be present. _Standard_: GNU extension *************** _Class_: *** 9242,9256 **** Elemental function _Syntax_: ! 'RESULT = DCMPLX(X [, Y])' _Arguments_: ! X The type may be 'INTEGER', 'REAL', or 'COMPLEX'. ! Y (Optional if X is not 'COMPLEX'.) May be ! 'INTEGER' or 'REAL'. _Return value_: ! The return value is of type 'COMPLEX(8)' _Example_: program test_dcmplx --- 9321,9336 ---- Elemental function _Syntax_: ! `RESULT = DCMPLX(X [, Y])' _Arguments_: ! X The type may be `INTEGER', `REAL', or ! `COMPLEX'. ! Y (Optional if X is not `COMPLEX'.) May be ! `INTEGER' or `REAL'. _Return value_: ! The return value is of type `COMPLEX(8)' _Example_: program test_dcmplx *************** _Example_: *** 9267,9280 ****  File: gfortran.info, Node: DIGITS, Next: DIM, Prev: DCMPLX, Up: Intrinsic Procedures ! 9.78 'DIGITS' -- Significant binary digits function =================================================== _Description_: ! 'DIGITS(X)' returns the number of significant binary digits of the ! internal model representation of X. For example, on a system using ! a 32-bit floating point representation, a default real number would ! likely return 24. _Standard_: Fortran 95 and later --- 9347,9360 ----  File: gfortran.info, Node: DIGITS, Next: DIM, Prev: DCMPLX, Up: Intrinsic Procedures ! 9.78 `DIGITS' -- Significant binary digits function =================================================== _Description_: ! `DIGITS(X)' returns the number of significant binary digits of the ! internal model representation of X. For example, on a system ! using a 32-bit floating point representation, a default real ! number would likely return 24. _Standard_: Fortran 95 and later *************** _Class_: *** 9283,9295 **** Inquiry function _Syntax_: ! 'RESULT = DIGITS(X)' _Arguments_: ! X The type may be 'INTEGER' or 'REAL'. _Return value_: ! The return value is of type 'INTEGER'. _Example_: program test_digits --- 9363,9375 ---- Inquiry function _Syntax_: ! `RESULT = DIGITS(X)' _Arguments_: ! X The type may be `INTEGER' or `REAL'. _Return value_: ! The return value is of type `INTEGER'. _Example_: program test_digits *************** _Example_: *** 9304,9314 ****  File: gfortran.info, Node: DIM, Next: DOT_PRODUCT, Prev: DIGITS, Up: Intrinsic Procedures ! 9.79 'DIM' -- Positive difference ================================= _Description_: ! 'DIM(X,Y)' returns the difference 'X-Y' if the result is positive; otherwise returns zero. _Standard_: --- 9384,9394 ----  File: gfortran.info, Node: DIM, Next: DOT_PRODUCT, Prev: DIGITS, Up: Intrinsic Procedures ! 9.79 `DIM' -- Positive difference ================================= _Description_: ! `DIM(X,Y)' returns the difference `X-Y' if the result is positive; otherwise returns zero. _Standard_: *************** _Class_: *** 9318,9331 **** Elemental function _Syntax_: ! 'RESULT = DIM(X, Y)' _Arguments_: ! X The type shall be 'INTEGER' or 'REAL' ! Y The type shall be the same type and kind as X. _Return value_: ! The return value is of type 'INTEGER' or 'REAL'. _Example_: program test_dim --- 9398,9411 ---- Elemental function _Syntax_: ! `RESULT = DIM(X, Y)' _Arguments_: ! X The type shall be `INTEGER' or `REAL' ! Y The type shall be the same type and kind as X. _Return value_: ! The return value is of type `INTEGER' or `REAL'. _Example_: program test_dim *************** _Example_: *** 9338,9365 **** end program test_dim _Specific names_: ! Name Argument Return type Standard ! 'DIM(X,Y)' 'REAL(4) X, 'REAL(4)' Fortran 77 and ! Y' later ! 'IDIM(X,Y)' 'INTEGER(4) 'INTEGER(4)' Fortran 77 and ! X, Y' later ! 'DDIM(X,Y)' 'REAL(8) X, 'REAL(8)' Fortran 77 and ! Y' later  File: gfortran.info, Node: DOT_PRODUCT, Next: DPROD, Prev: DIM, Up: Intrinsic Procedures ! 9.80 'DOT_PRODUCT' -- Dot product function ========================================== _Description_: ! 'DOT_PRODUCT(VECTOR_A, VECTOR_B)' computes the dot product multiplication of two vectors VECTOR_A and VECTOR_B. The two ! vectors may be either numeric or logical and must be arrays of rank ! one and of equal size. If the vectors are 'INTEGER' or 'REAL', the ! result is 'SUM(VECTOR_A*VECTOR_B)'. If the vectors are 'COMPLEX', ! the result is 'SUM(CONJG(VECTOR_A)*VECTOR_B)'. If the vectors are ! 'LOGICAL', the result is 'ANY(VECTOR_A .AND. VECTOR_B)'. _Standard_: Fortran 95 and later --- 9418,9446 ---- end program test_dim _Specific names_: ! Name Argument Return type Standard ! `DIM(X,Y)' `REAL(4) X, `REAL(4)' Fortran 77 and ! Y' later ! `IDIM(X,Y)' `INTEGER(4) `INTEGER(4)' Fortran 77 and ! X, Y' later ! `DDIM(X,Y)' `REAL(8) X, `REAL(8)' Fortran 77 and ! Y' later  File: gfortran.info, Node: DOT_PRODUCT, Next: DPROD, Prev: DIM, Up: Intrinsic Procedures ! 9.80 `DOT_PRODUCT' -- Dot product function ========================================== _Description_: ! `DOT_PRODUCT(VECTOR_A, VECTOR_B)' computes the dot product multiplication of two vectors VECTOR_A and VECTOR_B. The two ! vectors may be either numeric or logical and must be arrays of ! rank one and of equal size. If the vectors are `INTEGER' or ! `REAL', the result is `SUM(VECTOR_A*VECTOR_B)'. If the vectors are ! `COMPLEX', the result is `SUM(CONJG(VECTOR_A)*VECTOR_B)'. If the ! vectors are `LOGICAL', the result is `ANY(VECTOR_A .AND. ! VECTOR_B)'. _Standard_: Fortran 95 and later *************** _Class_: *** 9368,9385 **** Transformational function _Syntax_: ! 'RESULT = DOT_PRODUCT(VECTOR_A, VECTOR_B)' _Arguments_: ! VECTOR_A The type shall be numeric or 'LOGICAL', rank 1. ! VECTOR_B The type shall be numeric if VECTOR_A is of ! numeric type or 'LOGICAL' if VECTOR_A is of type ! 'LOGICAL'. VECTOR_B shall be a rank-one array. _Return value_: If the arguments are numeric, the return value is a scalar of ! numeric type, 'INTEGER', 'REAL', or 'COMPLEX'. If the arguments ! are 'LOGICAL', the return value is '.TRUE.' or '.FALSE.'. _Example_: program test_dot_prod --- 9449,9467 ---- Transformational function _Syntax_: ! `RESULT = DOT_PRODUCT(VECTOR_A, VECTOR_B)' _Arguments_: ! VECTOR_A The type shall be numeric or `LOGICAL', rank 1. ! VECTOR_B The type shall be numeric if VECTOR_A is of ! numeric type or `LOGICAL' if VECTOR_A is of ! type `LOGICAL'. VECTOR_B shall be a rank-one ! array. _Return value_: If the arguments are numeric, the return value is a scalar of ! numeric type, `INTEGER', `REAL', or `COMPLEX'. If the arguments ! are `LOGICAL', the return value is `.TRUE.' or `.FALSE.'. _Example_: program test_dot_prod *************** _Example_: *** 9396,9406 ****  File: gfortran.info, Node: DPROD, Next: DREAL, Prev: DOT_PRODUCT, Up: Intrinsic Procedures ! 9.81 'DPROD' -- Double product function ======================================= _Description_: ! 'DPROD(X,Y)' returns the product 'X*Y'. _Standard_: Fortran 77 and later --- 9478,9488 ----  File: gfortran.info, Node: DPROD, Next: DREAL, Prev: DOT_PRODUCT, Up: Intrinsic Procedures ! 9.81 `DPROD' -- Double product function ======================================= _Description_: ! `DPROD(X,Y)' returns the product `X*Y'. _Standard_: Fortran 77 and later *************** _Class_: *** 9409,9422 **** Elemental function _Syntax_: ! 'RESULT = DPROD(X, Y)' _Arguments_: ! X The type shall be 'REAL'. ! Y The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL(8)'. _Example_: program test_dprod --- 9491,9504 ---- Elemental function _Syntax_: ! `RESULT = DPROD(X, Y)' _Arguments_: ! X The type shall be `REAL'. ! Y The type shall be `REAL'. _Return value_: ! The return value is of type `REAL(8)'. _Example_: program test_dprod *************** _Example_: *** 9428,9445 **** end program test_dprod _Specific names_: ! Name Argument Return type Standard ! 'DPROD(X,Y)' 'REAL(4) X, 'REAL(8)' Fortran 77 and ! Y' later  File: gfortran.info, Node: DREAL, Next: DSHIFTL, Prev: DPROD, Up: Intrinsic Procedures ! 9.82 'DREAL' -- Double real part function ========================================= _Description_: ! 'DREAL(Z)' returns the real part of complex variable Z. _Standard_: GNU extension --- 9510,9528 ---- end program test_dprod _Specific names_: ! Name Argument Return type Standard ! `DPROD(X,Y)' `REAL(4) X, `REAL(8)' Fortran 77 and ! Y' later !  File: gfortran.info, Node: DREAL, Next: DSHIFTL, Prev: DPROD, Up: Intrinsic Procedures ! 9.82 `DREAL' -- Double real part function ========================================= _Description_: ! `DREAL(Z)' returns the real part of complex variable Z. _Standard_: GNU extension *************** _Class_: *** 9448,9460 **** Elemental function _Syntax_: ! 'RESULT = DREAL(A)' _Arguments_: ! A The type shall be 'COMPLEX(8)'. _Return value_: ! The return value is of type 'REAL(8)'. _Example_: program test_dreal --- 9531,9543 ---- Elemental function _Syntax_: ! `RESULT = DREAL(A)' _Arguments_: ! A The type shall be `COMPLEX(8)'. _Return value_: ! The return value is of type `REAL(8)'. _Example_: program test_dreal *************** _Example_: *** 9465,9478 **** _See also_: *note AIMAG::  File: gfortran.info, Node: DSHIFTL, Next: DSHIFTR, Prev: DREAL, Up: Intrinsic Procedures ! 9.83 'DSHIFTL' -- Combined left shift ===================================== _Description_: ! 'DSHIFTL(I, J, SHIFT)' combines bits of I and J. The rightmost SHIFT bits of the result are the leftmost SHIFT bits of J, and the remaining bits are the rightmost bits of I. --- 9548,9562 ---- _See also_: *note AIMAG:: +  File: gfortran.info, Node: DSHIFTL, Next: DSHIFTR, Prev: DREAL, Up: Intrinsic Procedures ! 9.83 `DSHIFTL' -- Combined left shift ===================================== _Description_: ! `DSHIFTL(I, J, SHIFT)' combines bits of I and J. The rightmost SHIFT bits of the result are the leftmost SHIFT bits of J, and the remaining bits are the rightmost bits of I. *************** _Class_: *** 9483,9505 **** Elemental function _Syntax_: ! 'RESULT = DSHIFTL(I, J, SHIFT)' _Arguments_: ! I Shall be of type 'INTEGER' or a BOZ constant. ! J Shall be of type 'INTEGER' or a BOZ constant. ! If both I and J have integer type, then they ! shall have the same kind type parameter. I and ! J shall not both be BOZ constants. ! SHIFT Shall be of type 'INTEGER'. It shall be ! nonnegative. If I is not a BOZ constant, then ! SHIFT shall be less than or equal to ! 'BIT_SIZE(I)'; otherwise, SHIFT shall be less ! than or equal to 'BIT_SIZE(J)'. _Return value_: If either I or J is a BOZ constant, it is first converted as if by ! the intrinsic function 'INT' to an integer type with the kind type parameter of the other. _See also_: --- 9567,9589 ---- Elemental function _Syntax_: ! `RESULT = DSHIFTL(I, J, SHIFT)' _Arguments_: ! I Shall be of type `INTEGER' or a BOZ constant. ! J Shall be of type `INTEGER' or a BOZ constant. ! If both I and J have integer type, then they ! shall have the same kind type parameter. I and ! J shall not both be BOZ constants. ! SHIFT Shall be of type `INTEGER'. It shall be ! nonnegative. If I is not a BOZ constant, then ! SHIFT shall be less than or equal to ! `BIT_SIZE(I)'; otherwise, SHIFT shall be less ! than or equal to `BIT_SIZE(J)'. _Return value_: If either I or J is a BOZ constant, it is first converted as if by ! the intrinsic function `INT' to an integer type with the kind type parameter of the other. _See also_: *************** _See also_: *** 9508,9520 ****  File: gfortran.info, Node: DSHIFTR, Next: DTIME, Prev: DSHIFTL, Up: Intrinsic Procedures ! 9.84 'DSHIFTR' -- Combined right shift ====================================== _Description_: ! 'DSHIFTR(I, J, SHIFT)' combines bits of I and J. The leftmost ! SHIFT bits of the result are the rightmost SHIFT bits of I, and the ! remaining bits are the leftmost bits of J. _Standard_: Fortran 2008 and later --- 9592,9604 ----  File: gfortran.info, Node: DSHIFTR, Next: DTIME, Prev: DSHIFTL, Up: Intrinsic Procedures ! 9.84 `DSHIFTR' -- Combined right shift ====================================== _Description_: ! `DSHIFTR(I, J, SHIFT)' combines bits of I and J. The leftmost ! SHIFT bits of the result are the rightmost SHIFT bits of I, and ! the remaining bits are the leftmost bits of J. _Standard_: Fortran 2008 and later *************** _Class_: *** 9523,9545 **** Elemental function _Syntax_: ! 'RESULT = DSHIFTR(I, J, SHIFT)' _Arguments_: ! I Shall be of type 'INTEGER' or a BOZ constant. ! J Shall be of type 'INTEGER' or a BOZ constant. ! If both I and J have integer type, then they ! shall have the same kind type parameter. I and ! J shall not both be BOZ constants. ! SHIFT Shall be of type 'INTEGER'. It shall be ! nonnegative. If I is not a BOZ constant, then ! SHIFT shall be less than or equal to ! 'BIT_SIZE(I)'; otherwise, SHIFT shall be less ! than or equal to 'BIT_SIZE(J)'. _Return value_: If either I or J is a BOZ constant, it is first converted as if by ! the intrinsic function 'INT' to an integer type with the kind type parameter of the other. _See also_: --- 9607,9629 ---- Elemental function _Syntax_: ! `RESULT = DSHIFTR(I, J, SHIFT)' _Arguments_: ! I Shall be of type `INTEGER' or a BOZ constant. ! J Shall be of type `INTEGER' or a BOZ constant. ! If both I and J have integer type, then they ! shall have the same kind type parameter. I and ! J shall not both be BOZ constants. ! SHIFT Shall be of type `INTEGER'. It shall be ! nonnegative. If I is not a BOZ constant, then ! SHIFT shall be less than or equal to ! `BIT_SIZE(I)'; otherwise, SHIFT shall be less ! than or equal to `BIT_SIZE(J)'. _Return value_: If either I or J is a BOZ constant, it is first converted as if by ! the intrinsic function `INT' to an integer type with the kind type parameter of the other. _See also_: *************** _See also_: *** 9548,9588 ****  File: gfortran.info, Node: DTIME, Next: EOSHIFT, Prev: DSHIFTR, Up: Intrinsic Procedures ! 9.85 'DTIME' -- Execution time subroutine (or function) ======================================================= _Description_: ! 'DTIME(VALUES, TIME)' initially returns the number of seconds of runtime since the start of the process's execution in TIME. VALUES ! returns the user and system components of this time in 'VALUES(1)' ! and 'VALUES(2)' respectively. TIME is equal to 'VALUES(1) + VALUES(2)'. ! Subsequent invocations of 'DTIME' return values accumulated since the previous invocation. ! On some systems, the underlying timings are represented using types ! with sufficiently small limits that overflows (wrap around) are ! possible, such as 32-bit types. Therefore, the values returned by ! this intrinsic might be, or become, negative, or numerically less ! than previous values, during a single run of the compiled program. ! Please note, that this implementation is thread safe if used within ! OpenMP directives, i.e., its state will be consistent while called ! from multiple threads. However, if 'DTIME' is called from multiple ! threads, the result is still the time since the last invocation. ! This may not give the intended results. If possible, use ! 'CPU_TIME' instead. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! VALUES and TIME are 'INTENT(OUT)' and provide the following: ! 'VALUES(1)': User time in seconds. ! 'VALUES(2)': System time in seconds. ! 'TIME': Run time since start in ! seconds. _Standard_: GNU extension --- 9632,9673 ----  File: gfortran.info, Node: DTIME, Next: EOSHIFT, Prev: DSHIFTR, Up: Intrinsic Procedures ! 9.85 `DTIME' -- Execution time subroutine (or function) ======================================================= _Description_: ! `DTIME(VALUES, TIME)' initially returns the number of seconds of runtime since the start of the process's execution in TIME. VALUES ! returns the user and system components of this time in `VALUES(1)' ! and `VALUES(2)' respectively. TIME is equal to `VALUES(1) + VALUES(2)'. ! Subsequent invocations of `DTIME' return values accumulated since the previous invocation. ! On some systems, the underlying timings are represented using ! types with sufficiently small limits that overflows (wrap around) ! are possible, such as 32-bit types. Therefore, the values returned ! by this intrinsic might be, or become, negative, or numerically ! less than previous values, during a single run of the compiled ! program. ! Please note, that this implementation is thread safe if used ! within OpenMP directives, i.e., its state will be consistent while ! called from multiple threads. However, if `DTIME' is called from ! multiple threads, the result is still the time since the last ! invocation. This may not give the intended results. If possible, ! use `CPU_TIME' instead. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! VALUES and TIME are `INTENT(OUT)' and provide the following: ! `VALUES(1)': User time in seconds. ! `VALUES(2)': System time in seconds. ! `TIME': Run time since start in ! seconds. _Standard_: GNU extension *************** _Class_: *** 9591,9602 **** Subroutine, function _Syntax_: ! 'CALL DTIME(VALUES, TIME)'. ! 'TIME = DTIME(VALUES)', (not recommended). _Arguments_: ! VALUES The type shall be 'REAL(4), DIMENSION(2)'. ! TIME The type shall be 'REAL(4)'. _Return value_: Elapsed time in seconds since the last invocation or since the --- 9676,9687 ---- Subroutine, function _Syntax_: ! `CALL DTIME(VALUES, TIME)'. ! `TIME = DTIME(VALUES)', (not recommended). _Arguments_: ! VALUES The type shall be `REAL(4), DIMENSION(2)'. ! TIME The type shall be `REAL(4)'. _Return value_: Elapsed time in seconds since the last invocation or since the *************** _Example_: *** 9623,9652 **** _See also_: *note CPU_TIME::  File: gfortran.info, Node: EOSHIFT, Next: EPSILON, Prev: DTIME, Up: Intrinsic Procedures ! 9.86 'EOSHIFT' -- End-off shift elements of an array ==================================================== _Description_: ! 'EOSHIFT(ARRAY, SHIFT[, BOUNDARY, DIM])' performs an end-off shift ! on elements of ARRAY along the dimension of DIM. If DIM is omitted ! it is taken to be '1'. DIM is a scalar of type 'INTEGER' in the ! range of 1 \leq DIM \leq n) where n is the rank of ARRAY. If the ! rank of ARRAY is one, then all elements of ARRAY are shifted by ! SHIFT places. If rank is greater than one, then all complete rank ! one sections of ARRAY along the given dimension are shifted. ! Elements shifted out one end of each rank one section are dropped. ! If BOUNDARY is present then the corresponding value of from ! BOUNDARY is copied back in the other end. If BOUNDARY is not ! present then the following are copied in depending on the type of ! ARRAY. ! _Array _Boundary Value_ ! Type_ ! Numeric 0 of the type and kind of ARRAY. ! Logical '.FALSE.'. Character(LEN)LEN blanks. _Standard_: --- 9708,9738 ---- _See also_: *note CPU_TIME:: +  File: gfortran.info, Node: EOSHIFT, Next: EPSILON, Prev: DTIME, Up: Intrinsic Procedures ! 9.86 `EOSHIFT' -- End-off shift elements of an array ==================================================== _Description_: ! `EOSHIFT(ARRAY, SHIFT[, BOUNDARY, DIM])' performs an end-off shift ! on elements of ARRAY along the dimension of DIM. If DIM is ! omitted it is taken to be `1'. DIM is a scalar of type `INTEGER' ! in the range of 1 \leq DIM \leq n) where n is the rank of ARRAY. ! If the rank of ARRAY is one, then all elements of ARRAY are ! shifted by SHIFT places. If rank is greater than one, then all ! complete rank one sections of ARRAY along the given dimension are ! shifted. Elements shifted out one end of each rank one section ! are dropped. If BOUNDARY is present then the corresponding value ! of from BOUNDARY is copied back in the other end. If BOUNDARY is ! not present then the following are copied in depending on the type ! of ARRAY. ! _Array _Boundary Value_ ! Type_ ! Numeric 0 of the type and kind of ARRAY. ! Logical `.FALSE.'. Character(LEN)LEN blanks. _Standard_: *************** _Class_: *** 9656,9668 **** Transformational function _Syntax_: ! 'RESULT = EOSHIFT(ARRAY, SHIFT [, BOUNDARY, DIM])' _Arguments_: ! ARRAY May be any type, not scalar. ! SHIFT The type shall be 'INTEGER'. ! BOUNDARY Same type as ARRAY. ! DIM The type shall be 'INTEGER'. _Return value_: Returns an array of same type and rank as the ARRAY argument. --- 9742,9754 ---- Transformational function _Syntax_: ! `RESULT = EOSHIFT(ARRAY, SHIFT [, BOUNDARY, DIM])' _Arguments_: ! ARRAY May be any type, not scalar. ! SHIFT The type shall be `INTEGER'. ! BOUNDARY Same type as ARRAY. ! DIM The type shall be `INTEGER'. _Return value_: Returns an array of same type and rank as the ARRAY argument. *************** _Example_: *** 9684,9694 ****  File: gfortran.info, Node: EPSILON, Next: ERF, Prev: EOSHIFT, Up: Intrinsic Procedures ! 9.87 'EPSILON' -- Epsilon function ================================== _Description_: ! 'EPSILON(X)' returns the smallest number E of the same kind as X such that 1 + E > 1. _Standard_: --- 9770,9780 ----  File: gfortran.info, Node: EPSILON, Next: ERF, Prev: EOSHIFT, Up: Intrinsic Procedures ! 9.87 `EPSILON' -- Epsilon function ================================== _Description_: ! `EPSILON(X)' returns the smallest number E of the same kind as X such that 1 + E > 1. _Standard_: *************** _Class_: *** 9698,9707 **** Inquiry function _Syntax_: ! 'RESULT = EPSILON(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: The return value is of same type as the argument. --- 9784,9793 ---- Inquiry function _Syntax_: ! `RESULT = EPSILON(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: The return value is of same type as the argument. *************** _Example_: *** 9717,9727 ****  File: gfortran.info, Node: ERF, Next: ERFC, Prev: EPSILON, Up: Intrinsic Procedures ! 9.88 'ERF' -- Error function ============================ _Description_: ! 'ERF(X)' computes the error function of X. _Standard_: Fortran 2008 and later --- 9803,9813 ----  File: gfortran.info, Node: ERF, Next: ERFC, Prev: EPSILON, Up: Intrinsic Procedures ! 9.88 `ERF' -- Error function ============================ _Description_: ! `ERF(X)' computes the error function of X. _Standard_: Fortran 2008 and later *************** _Class_: *** 9730,9742 **** Elemental function _Syntax_: ! 'RESULT = ERF(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL', of the same kind as X and lies in the range -1 \leq erf (x) \leq 1 . _Example_: --- 9816,9828 ---- Elemental function _Syntax_: ! `RESULT = ERF(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL', of the same kind as X and lies in the range -1 \leq erf (x) \leq 1 . _Example_: *************** _Example_: *** 9746,9762 **** end program test_erf _Specific names_: ! Name Argument Return type Standard ! 'DERF(X)' 'REAL(8) X' 'REAL(8)' GNU extension  File: gfortran.info, Node: ERFC, Next: ERFC_SCALED, Prev: ERF, Up: Intrinsic Procedures ! 9.89 'ERFC' -- Error function ============================= _Description_: ! 'ERFC(X)' computes the complementary error function of X. _Standard_: Fortran 2008 and later --- 9832,9848 ---- end program test_erf _Specific names_: ! Name Argument Return type Standard ! `DERF(X)' `REAL(8) X' `REAL(8)' GNU extension  File: gfortran.info, Node: ERFC, Next: ERFC_SCALED, Prev: ERF, Up: Intrinsic Procedures ! 9.89 `ERFC' -- Error function ============================= _Description_: ! `ERFC(X)' computes the complementary error function of X. _Standard_: Fortran 2008 and later *************** _Class_: *** 9765,9778 **** Elemental function _Syntax_: ! 'RESULT = ERFC(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL' and of the same kind as X. It ! lies in the range 0 \leq erfc (x) \leq 2 . _Example_: program test_erfc --- 9851,9864 ---- Elemental function _Syntax_: ! `RESULT = ERFC(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL' and of the same kind as X. It ! lies in the range 0 \leq erfc (x) \leq 2 . _Example_: program test_erfc *************** _Example_: *** 9781,9797 **** end program test_erfc _Specific names_: ! Name Argument Return type Standard ! 'DERFC(X)' 'REAL(8) X' 'REAL(8)' GNU extension  File: gfortran.info, Node: ERFC_SCALED, Next: ETIME, Prev: ERFC, Up: Intrinsic Procedures ! 9.90 'ERFC_SCALED' -- Error function ==================================== _Description_: ! 'ERFC_SCALED(X)' computes the exponentially-scaled complementary error function of X. _Standard_: --- 9867,9883 ---- end program test_erfc _Specific names_: ! Name Argument Return type Standard ! `DERFC(X)' `REAL(8) X' `REAL(8)' GNU extension  File: gfortran.info, Node: ERFC_SCALED, Next: ETIME, Prev: ERFC, Up: Intrinsic Procedures ! 9.90 `ERFC_SCALED' -- Error function ==================================== _Description_: ! `ERFC_SCALED(X)' computes the exponentially-scaled complementary error function of X. _Standard_: *************** _Class_: *** 9801,9813 **** Elemental function _Syntax_: ! 'RESULT = ERFC_SCALED(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL' and of the same kind as X. _Example_: program test_erfc_scaled --- 9887,9899 ---- Elemental function _Syntax_: ! `RESULT = ERFC_SCALED(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL' and of the same kind as X. _Example_: program test_erfc_scaled *************** _Example_: *** 9818,9847 ****  File: gfortran.info, Node: ETIME, Next: EVENT_QUERY, Prev: ERFC_SCALED, Up: Intrinsic Procedures ! 9.91 'ETIME' -- Execution time subroutine (or function) ======================================================= _Description_: ! 'ETIME(VALUES, TIME)' returns the number of seconds of runtime ! since the start of the process's execution in TIME. VALUES returns ! the user and system components of this time in 'VALUES(1)' and ! 'VALUES(2)' respectively. TIME is equal to 'VALUES(1) + VALUES(2)'. ! On some systems, the underlying timings are represented using types ! with sufficiently small limits that overflows (wrap around) are ! possible, such as 32-bit types. Therefore, the values returned by ! this intrinsic might be, or become, negative, or numerically less ! than previous values, during a single run of the compiled program. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! VALUES and TIME are 'INTENT(OUT)' and provide the following: ! 'VALUES(1)': User time in seconds. ! 'VALUES(2)': System time in seconds. ! 'TIME': Run time since start in seconds. _Standard_: GNU extension --- 9904,9934 ----  File: gfortran.info, Node: ETIME, Next: EVENT_QUERY, Prev: ERFC_SCALED, Up: Intrinsic Procedures ! 9.91 `ETIME' -- Execution time subroutine (or function) ======================================================= _Description_: ! `ETIME(VALUES, TIME)' returns the number of seconds of runtime ! since the start of the process's execution in TIME. VALUES ! returns the user and system components of this time in `VALUES(1)' ! and `VALUES(2)' respectively. TIME is equal to `VALUES(1) + VALUES(2)'. ! On some systems, the underlying timings are represented using ! types with sufficiently small limits that overflows (wrap around) ! are possible, such as 32-bit types. Therefore, the values returned ! by this intrinsic might be, or become, negative, or numerically ! less than previous values, during a single run of the compiled ! program. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! VALUES and TIME are `INTENT(OUT)' and provide the following: ! `VALUES(1)': User time in seconds. ! `VALUES(2)': System time in seconds. ! `TIME': Run time since start in seconds. _Standard_: GNU extension *************** _Class_: *** 9850,9861 **** Subroutine, function _Syntax_: ! 'CALL ETIME(VALUES, TIME)'. ! 'TIME = ETIME(VALUES)', (not recommended). _Arguments_: ! VALUES The type shall be 'REAL(4), DIMENSION(2)'. ! TIME The type shall be 'REAL(4)'. _Return value_: Elapsed time in seconds since the start of program execution. --- 9937,9948 ---- Subroutine, function _Syntax_: ! `CALL ETIME(VALUES, TIME)'. ! `TIME = ETIME(VALUES)', (not recommended). _Arguments_: ! VALUES The type shall be `REAL(4), DIMENSION(2)'. ! TIME The type shall be `REAL(4)'. _Return value_: Elapsed time in seconds since the start of program execution. *************** _Example_: *** 9881,9899 **** _See also_: *note CPU_TIME::  File: gfortran.info, Node: EVENT_QUERY, Next: EXECUTE_COMMAND_LINE, Prev: ETIME, Up: Intrinsic Procedures ! 9.92 'EVENT_QUERY' -- Query whether a coarray event has occurred ================================================================ _Description_: ! 'EVENT_QUERY' assignes the number of events to COUNT which have been posted to the EVENT variable and not yet been removed by ! calling 'EVENT WAIT'. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the ! invokation has failed, it is assigned a positive value and COUNT is ! assigned the value -1. _Standard_: TS 18508 or later --- 9968,9987 ---- _See also_: *note CPU_TIME:: +  File: gfortran.info, Node: EVENT_QUERY, Next: EXECUTE_COMMAND_LINE, Prev: ETIME, Up: Intrinsic Procedures ! 9.92 `EVENT_QUERY' -- Query whether a coarray event has occurred ================================================================ _Description_: ! `EVENT_QUERY' assignes the number of events to COUNT which have been posted to the EVENT variable and not yet been removed by ! calling `EVENT WAIT'. When STAT is present and the invokation was ! successful, it is assigned the value 0. If it is present and the ! invokation has failed, it is assigned a positive value and COUNT ! is assigned the value -1. _Standard_: TS 18508 or later *************** _Class_: *** 9902,9916 **** subroutine _Syntax_: ! 'CALL EVENT_QUERY (EVENT, COUNT [, STAT])' _Arguments_: ! EVENT (intent(IN)) Scalar of type 'EVENT_TYPE', ! defined in 'ISO_FORTRAN_ENV'; shall not be ! coindexed. ! COUNT (intent(out))Scalar integer with at least the ! precision of default integer. ! STAT (optional) Scalar default-kind integer variable. _Example_: program atomic --- 9990,10005 ---- subroutine _Syntax_: ! `CALL EVENT_QUERY (EVENT, COUNT [, STAT])' _Arguments_: ! EVENT (intent(IN)) Scalar of type `EVENT_TYPE', ! defined in `ISO_FORTRAN_ENV'; shall not be ! coindexed. ! COUNT (intent(out))Scalar integer with at least the ! precision of default integer. ! STAT (optional) Scalar default-kind integer ! variable. _Example_: program atomic *************** _Example_: *** 9926,9956 **** end if end program atomic  File: gfortran.info, Node: EXECUTE_COMMAND_LINE, Next: EXIT, Prev: EVENT_QUERY, Up: Intrinsic Procedures ! 9.93 'EXECUTE_COMMAND_LINE' -- Execute a shell command ====================================================== _Description_: ! 'EXECUTE_COMMAND_LINE' runs a shell command, synchronously or asynchronously. ! The 'COMMAND' argument is passed to the shell and executed, using ! the C library's 'system' call. (The shell is 'sh' on Unix systems, ! and 'cmd.exe' on Windows.) If 'WAIT' is present and has the value ! false, the execution of the command is asynchronous if the system ! supports it; otherwise, the command is executed synchronously. The three last arguments allow the user to get status information. ! After synchronous execution, 'EXITSTAT' contains the integer exit ! code of the command, as returned by 'system'. 'CMDSTAT' is set to zero if the command line was executed (whatever its exit status ! was). 'CMDMSG' is assigned an error message if an error has occurred. ! Note that the 'system' function need not be thread-safe. It is the ! responsibility of the user to ensure that 'system' is not called concurrently. _Standard_: --- 10015,10047 ---- end if end program atomic +  File: gfortran.info, Node: EXECUTE_COMMAND_LINE, Next: EXIT, Prev: EVENT_QUERY, Up: Intrinsic Procedures ! 9.93 `EXECUTE_COMMAND_LINE' -- Execute a shell command ====================================================== _Description_: ! `EXECUTE_COMMAND_LINE' runs a shell command, synchronously or asynchronously. ! The `COMMAND' argument is passed to the shell and executed, using ! the C library's `system' call. (The shell is `sh' on Unix ! systems, and `cmd.exe' on Windows.) If `WAIT' is present and has ! the value false, the execution of the command is asynchronous if ! the system supports it; otherwise, the command is executed ! synchronously. The three last arguments allow the user to get status information. ! After synchronous execution, `EXITSTAT' contains the integer exit ! code of the command, as returned by `system'. `CMDSTAT' is set to zero if the command line was executed (whatever its exit status ! was). `CMDMSG' is assigned an error message if an error has occurred. ! Note that the `system' function need not be thread-safe. It is the ! responsibility of the user to ensure that `system' is not called concurrently. _Standard_: *************** _Class_: *** 9960,9977 **** Subroutine _Syntax_: ! 'CALL EXECUTE_COMMAND_LINE(COMMAND [, WAIT, EXITSTAT, CMDSTAT, CMDMSG ])' _Arguments_: ! COMMAND Shall be a default 'CHARACTER' scalar. ! WAIT (Optional) Shall be a default 'LOGICAL' scalar. ! EXITSTAT (Optional) Shall be an 'INTEGER' of the default ! kind. ! CMDSTAT (Optional) Shall be an 'INTEGER' of the default ! kind. ! CMDMSG (Optional) Shall be an 'CHARACTER' scalar of the ! default kind. _Example_: program test_exec --- 10051,10068 ---- Subroutine _Syntax_: ! `CALL EXECUTE_COMMAND_LINE(COMMAND [, WAIT, EXITSTAT, CMDSTAT, CMDMSG ])' _Arguments_: ! COMMAND Shall be a default `CHARACTER' scalar. ! WAIT (Optional) Shall be a default `LOGICAL' scalar. ! EXITSTAT (Optional) Shall be an `INTEGER' of the ! default kind. ! CMDSTAT (Optional) Shall be an `INTEGER' of the ! default kind. ! CMDMSG (Optional) Shall be an `CHARACTER' scalar of ! the default kind. _Example_: program test_exec *************** _Example_: *** 9986,9997 **** end program test_exec _Note_: ! ! Because this intrinsic is implemented in terms of the 'system' function call, its behavior with respect to signaling is processor ! dependent. In particular, on POSIX-compliant systems, the SIGINT and SIGQUIT signals will be ignored, and the SIGCHLD will be ! blocked. As such, if the parent process is terminated, the child process might not be terminated alongside. _See also_: --- 10077,10087 ---- end program test_exec _Note_: ! Because this intrinsic is implemented in terms of the `system' function call, its behavior with respect to signaling is processor ! dependent. In particular, on POSIX-compliant systems, the SIGINT and SIGQUIT signals will be ignored, and the SIGCHLD will be ! blocked. As such, if the parent process is terminated, the child process might not be terminated alongside. _See also_: *************** _See also_: *** 10000,10011 ****  File: gfortran.info, Node: EXIT, Next: EXP, Prev: EXECUTE_COMMAND_LINE, Up: Intrinsic Procedures ! 9.94 'EXIT' -- Exit the program with status. ============================================ _Description_: ! 'EXIT' causes immediate termination of the program with status. If ! status is omitted it returns the canonical _success_ for the system. All Fortran I/O units are closed. _Standard_: --- 10090,10101 ----  File: gfortran.info, Node: EXIT, Next: EXP, Prev: EXECUTE_COMMAND_LINE, Up: Intrinsic Procedures ! 9.94 `EXIT' -- Exit the program with status. ============================================ _Description_: ! `EXIT' causes immediate termination of the program with status. ! If status is omitted it returns the canonical _success_ for the system. All Fortran I/O units are closed. _Standard_: *************** _Class_: *** 10015,10027 **** Subroutine _Syntax_: ! 'CALL EXIT([STATUS])' _Arguments_: ! STATUS Shall be an 'INTEGER' of the default kind. _Return value_: ! 'STATUS' is passed to the parent process on exit. _Example_: program test_exit --- 10105,10117 ---- Subroutine _Syntax_: ! `CALL EXIT([STATUS])' _Arguments_: ! STATUS Shall be an `INTEGER' of the default kind. _Return value_: ! `STATUS' is passed to the parent process on exit. _Example_: program test_exit *************** _See also_: *** 10036,10046 ****  File: gfortran.info, Node: EXP, Next: EXPONENT, Prev: EXIT, Up: Intrinsic Procedures ! 9.95 'EXP' -- Exponential function ================================== _Description_: ! 'EXP(X)' computes the base e exponential of X. _Standard_: Fortran 77 and later, has overloads that are GNU extensions --- 10126,10136 ----  File: gfortran.info, Node: EXP, Next: EXPONENT, Prev: EXIT, Up: Intrinsic Procedures ! 9.95 `EXP' -- Exponential function ================================== _Description_: ! `EXP(X)' computes the base e exponential of X. _Standard_: Fortran 77 and later, has overloads that are GNU extensions *************** _Class_: *** 10049,10058 **** Elemental function _Syntax_: ! 'RESULT = EXP(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: The return value has same type and kind as X. --- 10139,10148 ---- Elemental function _Syntax_: ! `RESULT = EXP(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: The return value has same type and kind as X. *************** _Example_: *** 10064,10089 **** end program test_exp _Specific names_: ! Name Argument Return type Standard ! 'EXP(X)' 'REAL(4) X' 'REAL(4)' Fortran 77 and ! later ! 'DEXP(X)' 'REAL(8) X' 'REAL(8)' Fortran 77 and ! later ! 'CEXP(X)' 'COMPLEX(4) 'COMPLEX(4)' Fortran 77 and ! X' later ! 'ZEXP(X)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! X' ! 'CDEXP(X)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! X'  File: gfortran.info, Node: EXPONENT, Next: EXTENDS_TYPE_OF, Prev: EXP, Up: Intrinsic Procedures ! 9.96 'EXPONENT' -- Exponent function ==================================== _Description_: ! 'EXPONENT(X)' returns the value of the exponent part of X. If X is zero the value returned is zero. _Standard_: --- 10154,10179 ---- end program test_exp _Specific names_: ! Name Argument Return type Standard ! `EXP(X)' `REAL(4) X' `REAL(4)' Fortran 77 and ! later ! `DEXP(X)' `REAL(8) X' `REAL(8)' Fortran 77 and ! later ! `CEXP(X)' `COMPLEX(4) `COMPLEX(4)' Fortran 77 and ! X' later ! `ZEXP(X)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! X' ! `CDEXP(X)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! X'  File: gfortran.info, Node: EXPONENT, Next: EXTENDS_TYPE_OF, Prev: EXP, Up: Intrinsic Procedures ! 9.96 `EXPONENT' -- Exponent function ==================================== _Description_: ! `EXPONENT(X)' returns the value of the exponent part of X. If X is zero the value returned is zero. _Standard_: *************** _Class_: *** 10093,10105 **** Elemental function _Syntax_: ! 'RESULT = EXPONENT(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type default 'INTEGER'. _Example_: program test_exponent --- 10183,10195 ---- Elemental function _Syntax_: ! `RESULT = EXPONENT(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type default `INTEGER'. _Example_: program test_exponent *************** _Example_: *** 10113,10120 ****  File: gfortran.info, Node: EXTENDS_TYPE_OF, Next: FDATE, Prev: EXPONENT, Up: Intrinsic Procedures ! 9.97 'EXTENDS_TYPE_OF' -- Query dynamic type for extension ! ========================================================== _Description_: Query dynamic type for extension. --- 10203,10210 ----  File: gfortran.info, Node: EXTENDS_TYPE_OF, Next: FDATE, Prev: EXPONENT, Up: Intrinsic Procedures ! 9.97 `EXTENDS_TYPE_OF' -- Query dynamic type for extension ! =========================================================== _Description_: Query dynamic type for extension. *************** _Class_: *** 10126,10141 **** Inquiry function _Syntax_: ! 'RESULT = EXTENDS_TYPE_OF(A, MOLD)' _Arguments_: ! A Shall be an object of extensible declared type ! or unlimited polymorphic. ! MOLD Shall be an object of extensible declared type ! or unlimited polymorphic. _Return value_: ! The return value is a scalar of type default logical. It is true if and only if the dynamic type of A is an extension type of the dynamic type of MOLD. --- 10216,10231 ---- Inquiry function _Syntax_: ! `RESULT = EXTENDS_TYPE_OF(A, MOLD)' _Arguments_: ! A Shall be an object of extensible declared type ! or unlimited polymorphic. ! MOLD Shall be an object of extensible declared type ! or unlimited polymorphic. _Return value_: ! The return value is a scalar of type default logical. It is true if and only if the dynamic type of A is an extension type of the dynamic type of MOLD. *************** _See also_: *** 10145,10156 ****  File: gfortran.info, Node: FDATE, Next: FGET, Prev: EXTENDS_TYPE_OF, Up: Intrinsic Procedures ! 9.98 'FDATE' -- Get the current time as a string ================================================ _Description_: ! 'FDATE(DATE)' returns the current date (using the same format as ! 'CTIME') in DATE. It is equivalent to 'CALL CTIME(DATE, TIME())'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 10235,10246 ----  File: gfortran.info, Node: FDATE, Next: FGET, Prev: EXTENDS_TYPE_OF, Up: Intrinsic Procedures ! 9.98 `FDATE' -- Get the current time as a string ================================================ _Description_: ! `FDATE(DATE)' returns the current date (using the same format as ! `CTIME') in DATE. It is equivalent to `CALL CTIME(DATE, TIME())'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 10162,10176 **** Subroutine, function _Syntax_: ! 'CALL FDATE(DATE)'. ! 'DATE = FDATE()'. _Arguments_: ! DATE The type shall be of type 'CHARACTER' of the ! default kind. It is an 'INTENT(OUT)' argument. ! If the length of this variable is too short for ! the date and time string to fit completely, it ! will be blank on procedure return. _Return value_: The current date and time as a string. --- 10252,10267 ---- Subroutine, function _Syntax_: ! `CALL FDATE(DATE)'. ! `DATE = FDATE()'. _Arguments_: ! DATE The type shall be of type `CHARACTER' of the ! default kind. It is an `INTENT(OUT)' argument. ! If the length of this variable is too short ! for the date and time string to fit ! completely, it will be blank on procedure ! return. _Return value_: The current date and time as a string. *************** _See also_: *** 10194,10216 ****  File: gfortran.info, Node: FGET, Next: FGETC, Prev: FDATE, Up: Intrinsic Procedures ! 9.99 'FGET' -- Read a single character in stream mode from stdin ================================================================ _Description_: Read a single character in stream mode from stdin by bypassing ! normal formatted output. Stream I/O should not be mixed with normal record-oriented (formatted or unformatted) I/O on the same unit; the results are unpredictable. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the 'FGET' intrinsic is provided for backwards ! compatibility with 'g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new stream ! IO feature in new code for future portability. See also *note ! Fortran 2003 status::. _Standard_: GNU extension --- 10285,10307 ----  File: gfortran.info, Node: FGET, Next: FGETC, Prev: FDATE, Up: Intrinsic Procedures ! 9.99 `FGET' -- Read a single character in stream mode from stdin ================================================================ _Description_: Read a single character in stream mode from stdin by bypassing ! normal formatted output. Stream I/O should not be mixed with normal record-oriented (formatted or unformatted) I/O on the same unit; the results are unpredictable. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the `FGET' intrinsic is provided for backwards ! compatibility with `g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new ! stream IO feature in new code for future portability. See also ! *note Fortran 2003 status::. _Standard_: GNU extension *************** _Class_: *** 10219,10233 **** Subroutine, function _Syntax_: ! 'CALL FGET(C [, STATUS])' ! 'STATUS = FGET(C)' _Arguments_: ! C The type shall be 'CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type 'INTEGER'. ! Returns 0 on success, -1 on end-of-file, and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fget --- 10310,10324 ---- Subroutine, function _Syntax_: ! `CALL FGET(C [, STATUS])' ! `STATUS = FGET(C)' _Arguments_: ! C The type shall be `CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type `INTEGER'. ! Returns 0 on success, -1 on end-of-file, and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fget *************** _See also_: *** 10250,10256 ****  File: gfortran.info, Node: FGETC, Next: FLOOR, Prev: FGET, Up: Intrinsic Procedures ! 9.100 'FGETC' -- Read a single character in stream mode ======================================================= _Description_: --- 10341,10347 ----  File: gfortran.info, Node: FGETC, Next: FLOOR, Prev: FGET, Up: Intrinsic Procedures ! 9.100 `FGETC' -- Read a single character in stream mode ======================================================= _Description_: *************** _Description_: *** 10262,10272 **** This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the 'FGET' intrinsic is provided for backwards ! compatibility with 'g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new stream ! IO feature in new code for future portability. See also *note ! Fortran 2003 status::. _Standard_: GNU extension --- 10353,10363 ---- This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the `FGET' intrinsic is provided for backwards ! compatibility with `g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new ! stream IO feature in new code for future portability. See also ! *note Fortran 2003 status::. _Standard_: GNU extension *************** _Class_: *** 10275,10290 **** Subroutine, function _Syntax_: ! 'CALL FGETC(UNIT, C [, STATUS])' ! 'STATUS = FGETC(UNIT, C)' _Arguments_: ! UNIT The type shall be 'INTEGER'. ! C The type shall be 'CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type 'INTEGER'. ! Returns 0 on success, -1 on end-of-file and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fgetc --- 10366,10381 ---- Subroutine, function _Syntax_: ! `CALL FGETC(UNIT, C [, STATUS])' ! `STATUS = FGETC(UNIT, C)' _Arguments_: ! UNIT The type shall be `INTEGER'. ! C The type shall be `CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type `INTEGER'. ! Returns 0 on success, -1 on end-of-file and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fgetc *************** _See also_: *** 10306,10316 ****  File: gfortran.info, Node: FLOOR, Next: FLUSH, Prev: FGETC, Up: Intrinsic Procedures ! 9.101 'FLOOR' -- Integer floor function ======================================= _Description_: ! 'FLOOR(A)' returns the greatest integer less than or equal to X. _Standard_: Fortran 95 and later --- 10397,10407 ----  File: gfortran.info, Node: FLOOR, Next: FLUSH, Prev: FGETC, Up: Intrinsic Procedures ! 9.101 `FLOOR' -- Integer floor function ======================================= _Description_: ! `FLOOR(A)' returns the greatest integer less than or equal to X. _Standard_: Fortran 95 and later *************** _Class_: *** 10319,10335 **** Elemental function _Syntax_: ! 'RESULT = FLOOR(A [, KIND])' _Arguments_: ! A The type shall be 'REAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER(KIND)' if KIND is present and ! of default-kind 'INTEGER' otherwise. _Example_: program test_floor --- 10410,10426 ---- Elemental function _Syntax_: ! `RESULT = FLOOR(A [, KIND])' _Arguments_: ! A The type shall be `REAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER(KIND)' if KIND is present and ! of default-kind `INTEGER' otherwise. _Example_: program test_floor *************** _Example_: *** 10342,10355 **** _See also_: *note CEILING::, *note NINT::  File: gfortran.info, Node: FLUSH, Next: FNUM, Prev: FLOOR, Up: Intrinsic Procedures ! 9.102 'FLUSH' -- Flush I/O unit(s) ================================== _Description_: ! Flushes Fortran unit(s) currently open for output. Without the optional argument, all units are flushed, otherwise just the unit specified. --- 10433,10447 ---- _See also_: *note CEILING::, *note NINT:: +  File: gfortran.info, Node: FLUSH, Next: FNUM, Prev: FLOOR, Up: Intrinsic Procedures ! 9.102 `FLUSH' -- Flush I/O unit(s) ================================== _Description_: ! Flushes Fortran unit(s) currently open for output. Without the optional argument, all units are flushed, otherwise just the unit specified. *************** _Class_: *** 10360,10383 **** Subroutine _Syntax_: ! 'CALL FLUSH(UNIT)' _Arguments_: ! UNIT (Optional) The type shall be 'INTEGER'. _Note_: ! Beginning with the Fortran 2003 standard, there is a 'FLUSH' ! statement that should be preferred over the 'FLUSH' intrinsic. ! The 'FLUSH' intrinsic and the Fortran 2003 'FLUSH' statement have identical effect: they flush the runtime library's I/O buffer so ! that the data becomes visible to other processes. This does not guarantee that the data is committed to disk. ! On POSIX systems, you can request that all data is transferred to ! the storage device by calling the 'fsync' function, with the POSIX file descriptor of the I/O unit as argument (retrieved with GNU ! intrinsic 'FNUM'). The following example shows how: ! Declare the interface for POSIX fsync function interface --- 10452,10475 ---- Subroutine _Syntax_: ! `CALL FLUSH(UNIT)' _Arguments_: ! UNIT (Optional) The type shall be `INTEGER'. _Note_: ! Beginning with the Fortran 2003 standard, there is a `FLUSH' ! statement that should be preferred over the `FLUSH' intrinsic. ! The `FLUSH' intrinsic and the Fortran 2003 `FLUSH' statement have identical effect: they flush the runtime library's I/O buffer so ! that the data becomes visible to other processes. This does not guarantee that the data is committed to disk. ! On POSIX systems, you can request that all data is transferred to ! the storage device by calling the `fsync' function, with the POSIX file descriptor of the I/O unit as argument (retrieved with GNU ! intrinsic `FNUM'). The following example shows how: ! Declare the interface for POSIX fsync function interface *************** _Note_: *** 10405,10419 **** ! Handle possible error if (ret /= 0) stop "Error calling FSYNC"  File: gfortran.info, Node: FNUM, Next: FPUT, Prev: FLUSH, Up: Intrinsic Procedures ! 9.103 'FNUM' -- File number function ==================================== _Description_: ! 'FNUM(UNIT)' returns the POSIX file descriptor number corresponding ! to the open Fortran I/O unit 'UNIT'. _Standard_: GNU extension --- 10497,10512 ---- ! Handle possible error if (ret /= 0) stop "Error calling FSYNC" +  File: gfortran.info, Node: FNUM, Next: FPUT, Prev: FLUSH, Up: Intrinsic Procedures ! 9.103 `FNUM' -- File number function ==================================== _Description_: ! `FNUM(UNIT)' returns the POSIX file descriptor number ! corresponding to the open Fortran I/O unit `UNIT'. _Standard_: GNU extension *************** _Class_: *** 10422,10434 **** Function _Syntax_: ! 'RESULT = FNUM(UNIT)' _Arguments_: ! UNIT The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' _Example_: program test_fnum --- 10515,10527 ---- Function _Syntax_: ! `RESULT = FNUM(UNIT)' _Arguments_: ! UNIT The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' _Example_: program test_fnum *************** _Example_: *** 10442,10464 ****  File: gfortran.info, Node: FPUT, Next: FPUTC, Prev: FNUM, Up: Intrinsic Procedures ! 9.104 'FPUT' -- Write a single character in stream mode to stdout ================================================================= _Description_: Write a single character in stream mode to stdout by bypassing ! normal formatted output. Stream I/O should not be mixed with normal record-oriented (formatted or unformatted) I/O on the same unit; the results are unpredictable. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the 'FGET' intrinsic is provided for backwards ! compatibility with 'g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new stream ! IO feature in new code for future portability. See also *note ! Fortran 2003 status::. _Standard_: GNU extension --- 10535,10557 ----  File: gfortran.info, Node: FPUT, Next: FPUTC, Prev: FNUM, Up: Intrinsic Procedures ! 9.104 `FPUT' -- Write a single character in stream mode to stdout ================================================================= _Description_: Write a single character in stream mode to stdout by bypassing ! normal formatted output. Stream I/O should not be mixed with normal record-oriented (formatted or unformatted) I/O on the same unit; the results are unpredictable. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the `FGET' intrinsic is provided for backwards ! compatibility with `g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new ! stream IO feature in new code for future portability. See also ! *note Fortran 2003 status::. _Standard_: GNU extension *************** _Class_: *** 10467,10481 **** Subroutine, function _Syntax_: ! 'CALL FPUT(C [, STATUS])' ! 'STATUS = FPUT(C)' _Arguments_: ! C The type shall be 'CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type 'INTEGER'. ! Returns 0 on success, -1 on end-of-file and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fput --- 10560,10574 ---- Subroutine, function _Syntax_: ! `CALL FPUT(C [, STATUS])' ! `STATUS = FPUT(C)' _Arguments_: ! C The type shall be `CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type `INTEGER'. ! Returns 0 on success, -1 on end-of-file and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fput *************** _See also_: *** 10492,10514 ****  File: gfortran.info, Node: FPUTC, Next: FRACTION, Prev: FPUT, Up: Intrinsic Procedures ! 9.105 'FPUTC' -- Write a single character in stream mode ======================================================== _Description_: Write a single character in stream mode by bypassing normal ! formatted output. Stream I/O should not be mixed with normal record-oriented (formatted or unformatted) I/O on the same unit; the results are unpredictable. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the 'FGET' intrinsic is provided for backwards ! compatibility with 'g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new stream ! IO feature in new code for future portability. See also *note ! Fortran 2003 status::. _Standard_: GNU extension --- 10585,10607 ----  File: gfortran.info, Node: FPUTC, Next: FRACTION, Prev: FPUT, Up: Intrinsic Procedures ! 9.105 `FPUTC' -- Write a single character in stream mode ======================================================== _Description_: Write a single character in stream mode by bypassing normal ! formatted output. Stream I/O should not be mixed with normal record-oriented (formatted or unformatted) I/O on the same unit; the results are unpredictable. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the `FGET' intrinsic is provided for backwards ! compatibility with `g77'. GNU Fortran provides the Fortran 2003 ! Stream facility. Programmers should consider the use of new ! stream IO feature in new code for future portability. See also ! *note Fortran 2003 status::. _Standard_: GNU extension *************** _Class_: *** 10517,10532 **** Subroutine, function _Syntax_: ! 'CALL FPUTC(UNIT, C [, STATUS])' ! 'STATUS = FPUTC(UNIT, C)' _Arguments_: ! UNIT The type shall be 'INTEGER'. ! C The type shall be 'CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type 'INTEGER'. ! Returns 0 on success, -1 on end-of-file and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fputc --- 10610,10625 ---- Subroutine, function _Syntax_: ! `CALL FPUTC(UNIT, C [, STATUS])' ! `STATUS = FPUTC(UNIT, C)' _Arguments_: ! UNIT The type shall be `INTEGER'. ! C The type shall be `CHARACTER' and of default ! kind. ! STATUS (Optional) status flag of type `INTEGER'. ! Returns 0 on success, -1 on end-of-file and a ! system specific positive error code otherwise. _Example_: PROGRAM test_fputc *************** _See also_: *** 10546,10557 ****  File: gfortran.info, Node: FRACTION, Next: FREE, Prev: FPUTC, Up: Intrinsic Procedures ! 9.106 'FRACTION' -- Fractional part of the model representation =============================================================== _Description_: ! 'FRACTION(X)' returns the fractional part of the model ! representation of 'X'. _Standard_: Fortran 95 and later --- 10639,10650 ----  File: gfortran.info, Node: FRACTION, Next: FREE, Prev: FPUTC, Up: Intrinsic Procedures ! 9.106 `FRACTION' -- Fractional part of the model representation =============================================================== _Description_: ! `FRACTION(X)' returns the fractional part of the model ! representation of `X'. _Standard_: Fortran 95 and later *************** _Class_: *** 10560,10574 **** Elemental function _Syntax_: ! 'Y = FRACTION(X)' _Arguments_: ! X The type of the argument shall be a 'REAL'. _Return value_: ! The return value is of the same type and kind as the argument. The ! fractional part of the model representation of 'X' is returned; it ! is 'X * RADIX(X)**(-EXPONENT(X))'. _Example_: program test_fraction --- 10653,10667 ---- Elemental function _Syntax_: ! `Y = FRACTION(X)' _Arguments_: ! X The type of the argument shall be a `REAL'. _Return value_: ! The return value is of the same type and kind as the argument. ! The fractional part of the model representation of `X' is returned; ! it is `X * RADIX(X)**(-EXPONENT(X))'. _Example_: program test_fraction *************** _Example_: *** 10577,10594 **** print *, fraction(x), x * radix(x)**(-exponent(x)) end program test_fraction  File: gfortran.info, Node: FREE, Next: FSEEK, Prev: FRACTION, Up: Intrinsic Procedures ! 9.107 'FREE' -- Frees memory ============================ _Description_: ! Frees memory previously allocated by 'MALLOC'. The 'FREE' intrinsic is an extension intended to be used with Cray pointers, and is provided in GNU Fortran to allow user to compile legacy ! code. For new code using Fortran 95 pointers, the memory ! de-allocation intrinsic is 'DEALLOCATE'. _Standard_: GNU extension --- 10670,10688 ---- print *, fraction(x), x * radix(x)**(-exponent(x)) end program test_fraction +  File: gfortran.info, Node: FREE, Next: FSEEK, Prev: FRACTION, Up: Intrinsic Procedures ! 9.107 `FREE' -- Frees memory ============================ _Description_: ! Frees memory previously allocated by `MALLOC'. The `FREE' intrinsic is an extension intended to be used with Cray pointers, and is provided in GNU Fortran to allow user to compile legacy ! code. For new code using Fortran 95 pointers, the memory ! de-allocation intrinsic is `DEALLOCATE'. _Standard_: GNU extension *************** _Class_: *** 10597,10614 **** Subroutine _Syntax_: ! 'CALL FREE(PTR)' _Arguments_: ! PTR The type shall be 'INTEGER'. It represents the ! location of the memory that should be ! de-allocated. _Return value_: None _Example_: ! See 'MALLOC' for an example. _See also_: *note MALLOC:: --- 10691,10708 ---- Subroutine _Syntax_: ! `CALL FREE(PTR)' _Arguments_: ! PTR The type shall be `INTEGER'. It represents the ! location of the memory that should be ! de-allocated. _Return value_: None _Example_: ! See `MALLOC' for an example. _See also_: *note MALLOC:: *************** _See also_: *** 10616,10635 ****  File: gfortran.info, Node: FSEEK, Next: FSTAT, Prev: FREE, Up: Intrinsic Procedures ! 9.108 'FSEEK' -- Low level file positioning subroutine ====================================================== _Description_: ! Moves UNIT to the specified OFFSET. If WHENCE is set to 0, the ! OFFSET is taken as an absolute value 'SEEK_SET', if set to 1, ! OFFSET is taken to be relative to the current position 'SEEK_CUR', ! and if set to 2 relative to the end of the file 'SEEK_END'. On ! error, STATUS is set to a nonzero value. If STATUS the seek fails silently. This intrinsic routine is not fully backwards compatible with ! 'g77'. In 'g77', the 'FSEEK' takes a statement label instead of a ! STATUS variable. If FSEEK is used in old code, change CALL FSEEK(UNIT, OFFSET, WHENCE, *label) to INTEGER :: status --- 10710,10729 ----  File: gfortran.info, Node: FSEEK, Next: FSTAT, Prev: FREE, Up: Intrinsic Procedures ! 9.108 `FSEEK' -- Low level file positioning subroutine ====================================================== _Description_: ! Moves UNIT to the specified OFFSET. If WHENCE is set to 0, the ! OFFSET is taken as an absolute value `SEEK_SET', if set to 1, ! OFFSET is taken to be relative to the current position `SEEK_CUR', ! and if set to 2 relative to the end of the file `SEEK_END'. On ! error, STATUS is set to a nonzero value. If STATUS the seek fails silently. This intrinsic routine is not fully backwards compatible with ! `g77'. In `g77', the `FSEEK' takes a statement label instead of a ! STATUS variable. If FSEEK is used in old code, change CALL FSEEK(UNIT, OFFSET, WHENCE, *label) to INTEGER :: status *************** _Description_: *** 10638,10644 **** Please note that GNU Fortran provides the Fortran 2003 Stream facility. Programmers should consider the use of new stream IO ! feature in new code for future portability. See also *note Fortran 2003 status::. _Standard_: --- 10732,10738 ---- Please note that GNU Fortran provides the Fortran 2003 Stream facility. Programmers should consider the use of new stream IO ! feature in new code for future portability. See also *note Fortran 2003 status::. _Standard_: *************** _Class_: *** 10648,10662 **** Subroutine _Syntax_: ! 'CALL FSEEK(UNIT, OFFSET, WHENCE[, STATUS])' _Arguments_: ! UNIT Shall be a scalar of type 'INTEGER'. ! OFFSET Shall be a scalar of type 'INTEGER'. ! WHENCE Shall be a scalar of type 'INTEGER'. Its value ! shall be either 0, 1 or 2. ! STATUS (Optional) shall be a scalar of type ! 'INTEGER(4)'. _Example_: PROGRAM test_fseek --- 10742,10756 ---- Subroutine _Syntax_: ! `CALL FSEEK(UNIT, OFFSET, WHENCE[, STATUS])' _Arguments_: ! UNIT Shall be a scalar of type `INTEGER'. ! OFFSET Shall be a scalar of type `INTEGER'. ! WHENCE Shall be a scalar of type `INTEGER'. Its ! value shall be either 0, 1 or 2. ! STATUS (Optional) shall be a scalar of type ! `INTEGER(4)'. _Example_: PROGRAM test_fseek *************** _See also_: *** 10686,10699 ****  File: gfortran.info, Node: FSTAT, Next: FTELL, Prev: FSEEK, Up: Intrinsic Procedures ! 9.109 'FSTAT' -- Get file status ================================ _Description_: ! 'FSTAT' is identical to *note STAT::, except that information about ! an already opened file is obtained. ! The elements in 'VALUES' are the same as described by *note STAT::. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 10780,10793 ----  File: gfortran.info, Node: FSTAT, Next: FTELL, Prev: FSEEK, Up: Intrinsic Procedures ! 9.109 `FSTAT' -- Get file status ================================ _Description_: ! `FSTAT' is identical to *note STAT::, except that information ! about an already opened file is obtained. ! The elements in `VALUES' are the same as described by *note STAT::. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 10705,10719 **** Subroutine, function _Syntax_: ! 'CALL FSTAT(UNIT, VALUES [, STATUS])' ! 'STATUS = FSTAT(UNIT, VALUES)' _Arguments_: ! UNIT An open I/O unit number of type 'INTEGER'. ! VALUES The type shall be 'INTEGER(4), DIMENSION(13)'. ! STATUS (Optional) status flag of type 'INTEGER(4)'. ! Returns 0 on success and a system specific error ! code otherwise. _Example_: See *note STAT:: for an example. --- 10799,10813 ---- Subroutine, function _Syntax_: ! `CALL FSTAT(UNIT, VALUES [, STATUS])' ! `STATUS = FSTAT(UNIT, VALUES)' _Arguments_: ! UNIT An open I/O unit number of type `INTEGER'. ! VALUES The type shall be `INTEGER(4), DIMENSION(13)'. ! STATUS (Optional) status flag of type `INTEGER(4)'. ! Returns 0 on success and a system specific ! error code otherwise. _Example_: See *note STAT:: for an example. *************** _See also_: *** 10724,10730 ****  File: gfortran.info, Node: FTELL, Next: GAMMA, Prev: FSTAT, Up: Intrinsic Procedures ! 9.110 'FTELL' -- Current stream position ======================================== _Description_: --- 10818,10824 ----  File: gfortran.info, Node: FTELL, Next: GAMMA, Prev: FSTAT, Up: Intrinsic Procedures ! 9.110 `FTELL' -- Current stream position ======================================== _Description_: *************** _Class_: *** 10740,10751 **** Subroutine, function _Syntax_: ! 'CALL FTELL(UNIT, OFFSET)' ! 'OFFSET = FTELL(UNIT)' _Arguments_: ! OFFSET Shall of type 'INTEGER'. ! UNIT Shall of type 'INTEGER'. _Return value_: In either syntax, OFFSET is set to the current offset of unit --- 10834,10845 ---- Subroutine, function _Syntax_: ! `CALL FTELL(UNIT, OFFSET)' ! `OFFSET = FTELL(UNIT)' _Arguments_: ! OFFSET Shall of type `INTEGER'. ! UNIT Shall of type `INTEGER'. _Return value_: In either syntax, OFFSET is set to the current offset of unit *************** _See also_: *** 10765,10777 ****  File: gfortran.info, Node: GAMMA, Next: GERROR, Prev: FTELL, Up: Intrinsic Procedures ! 9.111 'GAMMA' -- Gamma function =============================== _Description_: ! 'GAMMA(X)' computes Gamma (\Gamma) of X. For positive, integer ! values of X the Gamma function simplifies to the factorial function ! \Gamma(x)=(x-1)!. _Standard_: Fortran 2008 and later --- 10859,10871 ----  File: gfortran.info, Node: GAMMA, Next: GERROR, Prev: FTELL, Up: Intrinsic Procedures ! 9.111 `GAMMA' -- Gamma function =============================== _Description_: ! `GAMMA(X)' computes Gamma (\Gamma) of X. For positive, integer ! values of X the Gamma function simplifies to the factorial ! function \Gamma(x)=(x-1)!. _Standard_: Fortran 2008 and later *************** _Class_: *** 10780,10793 **** Elemental function _Syntax_: ! 'X = GAMMA(X)' _Arguments_: ! X Shall be of type 'REAL' and neither zero nor a ! negative integer. _Return value_: ! The return value is of type 'REAL' of the same kind as X. _Example_: program test_gamma --- 10874,10887 ---- Elemental function _Syntax_: ! `X = GAMMA(X)' _Arguments_: ! X Shall be of type `REAL' and neither zero nor a ! negative integer. _Return value_: ! The return value is of type `REAL' of the same kind as X. _Example_: program test_gamma *************** _Example_: *** 10796,10817 **** end program test_gamma _Specific names_: ! Name Argument Return type Standard ! 'GAMMA(X)' 'REAL(4) X' 'REAL(4)' GNU Extension ! 'DGAMMA(X)' 'REAL(8) X' 'REAL(8)' GNU Extension _See also_: Logarithm of the Gamma function: *note LOG_GAMMA::  File: gfortran.info, Node: GERROR, Next: GETARG, Prev: GAMMA, Up: Intrinsic Procedures ! 9.112 'GERROR' -- Get last system error message =============================================== _Description_: Returns the system error message corresponding to the last system ! error. This resembles the functionality of 'strerror(3)' in C. _Standard_: GNU extension --- 10890,10912 ---- end program test_gamma _Specific names_: ! Name Argument Return type Standard ! `GAMMA(X)' `REAL(4) X' `REAL(4)' GNU Extension ! `DGAMMA(X)' `REAL(8) X' `REAL(8)' GNU Extension _See also_: Logarithm of the Gamma function: *note LOG_GAMMA:: +  File: gfortran.info, Node: GERROR, Next: GETARG, Prev: GAMMA, Up: Intrinsic Procedures ! 9.112 `GERROR' -- Get last system error message =============================================== _Description_: Returns the system error message corresponding to the last system ! error. This resembles the functionality of `strerror(3)' in C. _Standard_: GNU extension *************** _Class_: *** 10820,10829 **** Subroutine _Syntax_: ! 'CALL GERROR(RESULT)' _Arguments_: ! RESULT Shall of type 'CHARACTER' and of default _Example_: PROGRAM test_gerror --- 10915,10924 ---- Subroutine _Syntax_: ! `CALL GERROR(RESULT)' _Arguments_: ! RESULT Shall of type `CHARACTER' and of default _Example_: PROGRAM test_gerror *************** _See also_: *** 10838,10844 ****  File: gfortran.info, Node: GETARG, Next: GET_COMMAND, Prev: GERROR, Up: Intrinsic Procedures ! 9.113 'GETARG' -- Get command line arguments ============================================ _Description_: --- 10933,10939 ----  File: gfortran.info, Node: GETARG, Next: GET_COMMAND, Prev: GERROR, Up: Intrinsic Procedures ! 9.113 `GETARG' -- Get command line arguments ============================================ _Description_: *************** _Class_: *** 10857,10875 **** Subroutine _Syntax_: ! 'CALL GETARG(POS, VALUE)' _Arguments_: ! POS Shall be of type 'INTEGER' and not wider than ! the default integer kind; POS \geq 0 ! VALUE Shall be of type 'CHARACTER' and of default ! kind. ! VALUE Shall be of type 'CHARACTER'. _Return value_: ! After 'GETARG' returns, the VALUE argument holds the POSth command ! line argument. If VALUE can not hold the argument, it is truncated ! to fit the length of VALUE. If there are less than POS arguments specified at the command line, VALUE will be filled with blanks. If POS = 0, VALUE is set to the name of the program (on systems that support this feature). --- 10952,10970 ---- Subroutine _Syntax_: ! `CALL GETARG(POS, VALUE)' _Arguments_: ! POS Shall be of type `INTEGER' and not wider than ! the default integer kind; POS \geq 0 ! VALUE Shall be of type `CHARACTER' and of default ! kind. ! VALUE Shall be of type `CHARACTER'. _Return value_: ! After `GETARG' returns, the VALUE argument holds the POSth command ! line argument. If VALUE can not hold the argument, it is truncated ! to fit the length of VALUE. If there are less than POS arguments specified at the command line, VALUE will be filled with blanks. If POS = 0, VALUE is set to the name of the program (on systems that support this feature). *************** _See also_: *** 10894,10900 ****  File: gfortran.info, Node: GET_COMMAND, Next: GET_COMMAND_ARGUMENT, Prev: GETARG, Up: Intrinsic Procedures ! 9.114 'GET_COMMAND' -- Get the entire command line ================================================== _Description_: --- 10989,10995 ----  File: gfortran.info, Node: GET_COMMAND, Next: GET_COMMAND_ARGUMENT, Prev: GETARG, Up: Intrinsic Procedures ! 9.114 `GET_COMMAND' -- Get the entire command line ================================================== _Description_: *************** _Class_: *** 10908,10927 **** Subroutine _Syntax_: ! 'CALL GET_COMMAND([COMMAND, LENGTH, STATUS])' _Arguments_: ! COMMAND (Optional) shall be of type 'CHARACTER' and of ! default kind. ! LENGTH (Optional) Shall be of type 'INTEGER' and of ! default kind. ! STATUS (Optional) Shall be of type 'INTEGER' and of ! default kind. _Return value_: If COMMAND is present, stores the entire command line that was used ! to invoke the program in COMMAND. If LENGTH is present, it is ! assigned the length of the command line. If STATUS is present, it is assigned 0 upon success of the command, -1 if COMMAND is too short to store the command line, or a positive value in case of an error. --- 11003,11022 ---- Subroutine _Syntax_: ! `CALL GET_COMMAND([COMMAND, LENGTH, STATUS])' _Arguments_: ! COMMAND (Optional) shall be of type `CHARACTER' and of ! default kind. ! LENGTH (Optional) Shall be of type `INTEGER' and of ! default kind. ! STATUS (Optional) Shall be of type `INTEGER' and of ! default kind. _Return value_: If COMMAND is present, stores the entire command line that was used ! to invoke the program in COMMAND. If LENGTH is present, it is ! assigned the length of the command line. If STATUS is present, it is assigned 0 upon success of the command, -1 if COMMAND is too short to store the command line, or a positive value in case of an error. *************** _See also_: *** 10939,10950 ****  File: gfortran.info, Node: GET_COMMAND_ARGUMENT, Next: GETCWD, Prev: GET_COMMAND, Up: Intrinsic Procedures ! 9.115 'GET_COMMAND_ARGUMENT' -- Get command line arguments ========================================================== _Description_: ! Retrieve the NUMBER-th argument that was passed on the command line ! when the containing program was invoked. _Standard_: Fortran 2003 and later --- 11034,11045 ----  File: gfortran.info, Node: GET_COMMAND_ARGUMENT, Next: GETCWD, Prev: GET_COMMAND, Up: Intrinsic Procedures ! 9.115 `GET_COMMAND_ARGUMENT' -- Get command line arguments ========================================================== _Description_: ! Retrieve the NUMBER-th argument that was passed on the command ! line when the containing program was invoked. _Standard_: Fortran 2003 and later *************** _Class_: *** 10953,10981 **** Subroutine _Syntax_: ! 'CALL GET_COMMAND_ARGUMENT(NUMBER [, VALUE, LENGTH, STATUS])' _Arguments_: ! NUMBER Shall be a scalar of type 'INTEGER' and of ! default kind, NUMBER \geq 0 ! VALUE (Optional) Shall be a scalar of type 'CHARACTER' ! and of default kind. ! LENGTH (Optional) Shall be a scalar of type 'INTEGER' ! and of default kind. ! STATUS (Optional) Shall be a scalar of type 'INTEGER' ! and of default kind. _Return value_: ! After 'GET_COMMAND_ARGUMENT' returns, the VALUE argument holds the ! NUMBER-th command line argument. If VALUE can not hold the ! argument, it is truncated to fit the length of VALUE. If there are less than NUMBER arguments specified at the command line, VALUE will be filled with blanks. If NUMBER = 0, VALUE is set to the ! name of the program (on systems that support this feature). The LENGTH argument contains the length of the NUMBER-th command line ! argument. If the argument retrieval fails, STATUS is a positive ! number; if VALUE contains a truncated command line argument, STATUS ! is -1; and otherwise the STATUS is zero. _Example_: PROGRAM test_get_command_argument --- 11048,11076 ---- Subroutine _Syntax_: ! `CALL GET_COMMAND_ARGUMENT(NUMBER [, VALUE, LENGTH, STATUS])' _Arguments_: ! NUMBER Shall be a scalar of type `INTEGER' and of ! default kind, NUMBER \geq 0 ! VALUE (Optional) Shall be a scalar of type ! `CHARACTER' and of default kind. ! LENGTH (Optional) Shall be a scalar of type `INTEGER' ! and of default kind. ! STATUS (Optional) Shall be a scalar of type `INTEGER' ! and of default kind. _Return value_: ! After `GET_COMMAND_ARGUMENT' returns, the VALUE argument holds the ! NUMBER-th command line argument. If VALUE can not hold the ! argument, it is truncated to fit the length of VALUE. If there are less than NUMBER arguments specified at the command line, VALUE will be filled with blanks. If NUMBER = 0, VALUE is set to the ! name of the program (on systems that support this feature). The LENGTH argument contains the length of the NUMBER-th command line ! argument. If the argument retrieval fails, STATUS is a positive ! number; if VALUE contains a truncated command line argument, ! STATUS is -1; and otherwise the STATUS is zero. _Example_: PROGRAM test_get_command_argument *************** _See also_: *** 10998,11004 ****  File: gfortran.info, Node: GETCWD, Next: GETENV, Prev: GET_COMMAND_ARGUMENT, Up: Intrinsic Procedures ! 9.116 'GETCWD' -- Get current working directory =============================================== _Description_: --- 11093,11099 ----  File: gfortran.info, Node: GETCWD, Next: GETENV, Prev: GET_COMMAND_ARGUMENT, Up: Intrinsic Procedures ! 9.116 `GETCWD' -- Get current working directory =============================================== _Description_: *************** _Class_: *** 11014,11028 **** Subroutine, function _Syntax_: ! 'CALL GETCWD(C [, STATUS])' ! 'STATUS = GETCWD(C)' _Arguments_: ! C The type shall be 'CHARACTER' and of default ! kind. ! STATUS (Optional) status flag. Returns 0 on success, a ! system specific and nonzero error code ! otherwise. _Example_: PROGRAM test_getcwd --- 11109,11123 ---- Subroutine, function _Syntax_: ! `CALL GETCWD(C [, STATUS])' ! `STATUS = GETCWD(C)' _Arguments_: ! C The type shall be `CHARACTER' and of default ! kind. ! STATUS (Optional) status flag. Returns 0 on success, ! a system specific and nonzero error code ! otherwise. _Example_: PROGRAM test_getcwd *************** _See also_: *** 11037,11043 ****  File: gfortran.info, Node: GETENV, Next: GET_ENVIRONMENT_VARIABLE, Prev: GETCWD, Up: Intrinsic Procedures ! 9.117 'GETENV' -- Get an environmental variable =============================================== _Description_: --- 11132,11138 ----  File: gfortran.info, Node: GETENV, Next: GET_ENVIRONMENT_VARIABLE, Prev: GETCWD, Up: Intrinsic Procedures ! 9.117 `GETENV' -- Get an environmental variable =============================================== _Description_: *************** _Description_: *** 11048,11056 **** of the *note GET_ENVIRONMENT_VARIABLE:: intrinsic defined by the Fortran 2003 standard. ! Note that 'GETENV' need not be thread-safe. It is the responsibility of the user to ensure that the environment is not ! being updated concurrently with a call to the 'GETENV' intrinsic. _Standard_: GNU extension --- 11143,11151 ---- of the *note GET_ENVIRONMENT_VARIABLE:: intrinsic defined by the Fortran 2003 standard. ! Note that `GETENV' need not be thread-safe. It is the responsibility of the user to ensure that the environment is not ! being updated concurrently with a call to the `GETENV' intrinsic. _Standard_: GNU extension *************** _Class_: *** 11059,11075 **** Subroutine _Syntax_: ! 'CALL GETENV(NAME, VALUE)' _Arguments_: ! NAME Shall be of type 'CHARACTER' and of default ! kind. ! VALUE Shall be of type 'CHARACTER' and of default ! kind. _Return value_: ! Stores the value of NAME in VALUE. If VALUE is not large enough to ! hold the data, it is truncated. If NAME is not set, VALUE will be filled with blanks. _Example_: --- 11154,11170 ---- Subroutine _Syntax_: ! `CALL GETENV(NAME, VALUE)' _Arguments_: ! NAME Shall be of type `CHARACTER' and of default ! kind. ! VALUE Shall be of type `CHARACTER' and of default ! kind. _Return value_: ! Stores the value of NAME in VALUE. If VALUE is not large enough to ! hold the data, it is truncated. If NAME is not set, VALUE will be filled with blanks. _Example_: *************** _See also_: *** 11085,11100 ****  File: gfortran.info, Node: GET_ENVIRONMENT_VARIABLE, Next: GETGID, Prev: GETENV, Up: Intrinsic Procedures ! 9.118 'GET_ENVIRONMENT_VARIABLE' -- Get an environmental variable ================================================================= _Description_: Get the VALUE of the environmental variable NAME. ! Note that 'GET_ENVIRONMENT_VARIABLE' need not be thread-safe. It is the responsibility of the user to ensure that the environment is not being updated concurrently with a call to the ! 'GET_ENVIRONMENT_VARIABLE' intrinsic. _Standard_: Fortran 2003 and later --- 11180,11195 ----  File: gfortran.info, Node: GET_ENVIRONMENT_VARIABLE, Next: GETGID, Prev: GETENV, Up: Intrinsic Procedures ! 9.118 `GET_ENVIRONMENT_VARIABLE' -- Get an environmental variable ================================================================= _Description_: Get the VALUE of the environmental variable NAME. ! Note that `GET_ENVIRONMENT_VARIABLE' need not be thread-safe. It is the responsibility of the user to ensure that the environment is not being updated concurrently with a call to the ! `GET_ENVIRONMENT_VARIABLE' intrinsic. _Standard_: Fortran 2003 and later *************** _Class_: *** 11103,11134 **** Subroutine _Syntax_: ! 'CALL GET_ENVIRONMENT_VARIABLE(NAME[, VALUE, LENGTH, STATUS, TRIM_NAME)' _Arguments_: ! NAME Shall be a scalar of type 'CHARACTER' and of ! default kind. ! VALUE (Optional) Shall be a scalar of type 'CHARACTER' ! and of default kind. ! LENGTH (Optional) Shall be a scalar of type 'INTEGER' ! and of default kind. ! STATUS (Optional) Shall be a scalar of type 'INTEGER' ! and of default kind. ! TRIM_NAME (Optional) Shall be a scalar of type 'LOGICAL' ! and of default kind. _Return value_: ! Stores the value of NAME in VALUE. If VALUE is not large enough to ! hold the data, it is truncated. If NAME is not set, VALUE will be ! filled with blanks. Argument LENGTH contains the length needed for ! storing the environment variable NAME or zero if it is not present. ! STATUS is -1 if VALUE is present but too short for the environment ! variable; it is 1 if the environment variable does not exist and 2 ! if the processor does not support environment variables; in all ! other cases STATUS is zero. If TRIM_NAME is present with the value ! '.FALSE.', the trailing blanks in NAME are significant; otherwise ! they are not part of the environment variable name. _Example_: PROGRAM test_getenv --- 11198,11230 ---- Subroutine _Syntax_: ! `CALL GET_ENVIRONMENT_VARIABLE(NAME[, VALUE, LENGTH, STATUS, TRIM_NAME)' _Arguments_: ! NAME Shall be a scalar of type `CHARACTER' and of ! default kind. ! VALUE (Optional) Shall be a scalar of type ! `CHARACTER' and of default kind. ! LENGTH (Optional) Shall be a scalar of type `INTEGER' ! and of default kind. ! STATUS (Optional) Shall be a scalar of type `INTEGER' ! and of default kind. ! TRIM_NAME (Optional) Shall be a scalar of type `LOGICAL' ! and of default kind. _Return value_: ! Stores the value of NAME in VALUE. If VALUE is not large enough to ! hold the data, it is truncated. If NAME is not set, VALUE will be ! filled with blanks. Argument LENGTH contains the length needed for ! storing the environment variable NAME or zero if it is not ! present. STATUS is -1 if VALUE is present but too short for the ! environment variable; it is 1 if the environment variable does not ! exist and 2 if the processor does not support environment ! variables; in all other cases STATUS is zero. If TRIM_NAME is ! present with the value `.FALSE.', the trailing blanks in NAME are ! significant; otherwise they are not part of the environment ! variable name. _Example_: PROGRAM test_getenv *************** _Example_: *** 11140,11146 ****  File: gfortran.info, Node: GETGID, Next: GETLOG, Prev: GET_ENVIRONMENT_VARIABLE, Up: Intrinsic Procedures ! 9.119 'GETGID' -- Group ID function =================================== _Description_: --- 11236,11242 ----  File: gfortran.info, Node: GETGID, Next: GETLOG, Prev: GET_ENVIRONMENT_VARIABLE, Up: Intrinsic Procedures ! 9.119 `GETGID' -- Group ID function =================================== _Description_: *************** _Class_: *** 11153,11165 **** Function _Syntax_: ! 'RESULT = GETGID()' _Return value_: ! The return value of 'GETGID' is an 'INTEGER' of the default kind. _Example_: ! See 'GETPID' for an example. _See also_: *note GETPID::, *note GETUID:: --- 11249,11261 ---- Function _Syntax_: ! `RESULT = GETGID()' _Return value_: ! The return value of `GETGID' is an `INTEGER' of the default kind. _Example_: ! See `GETPID' for an example. _See also_: *note GETPID::, *note GETUID:: *************** _See also_: *** 11167,11173 ****  File: gfortran.info, Node: GETLOG, Next: GETPID, Prev: GETGID, Up: Intrinsic Procedures ! 9.120 'GETLOG' -- Get login name ================================ _Description_: --- 11263,11269 ----  File: gfortran.info, Node: GETLOG, Next: GETPID, Prev: GETGID, Up: Intrinsic Procedures ! 9.120 `GETLOG' -- Get login name ================================ _Description_: *************** _Class_: *** 11180,11195 **** Subroutine _Syntax_: ! 'CALL GETLOG(C)' _Arguments_: ! C Shall be of type 'CHARACTER' and of default ! kind. _Return value_: Stores the current user name in LOGIN. (On systems where POSIX ! functions 'geteuid' and 'getpwuid' are not available, and the ! 'getlogin' function is not implemented either, this will return a blank string.) _Example_: --- 11276,11291 ---- Subroutine _Syntax_: ! `CALL GETLOG(C)' _Arguments_: ! C Shall be of type `CHARACTER' and of default ! kind. _Return value_: Stores the current user name in LOGIN. (On systems where POSIX ! functions `geteuid' and `getpwuid' are not available, and the ! `getlogin' function is not implemented either, this will return a blank string.) _Example_: *************** _See also_: *** 11205,11211 ****  File: gfortran.info, Node: GETPID, Next: GETUID, Prev: GETLOG, Up: Intrinsic Procedures ! 9.121 'GETPID' -- Process ID function ===================================== _Description_: --- 11301,11307 ----  File: gfortran.info, Node: GETPID, Next: GETUID, Prev: GETLOG, Up: Intrinsic Procedures ! 9.121 `GETPID' -- Process ID function ===================================== _Description_: *************** _Class_: *** 11218,11227 **** Function _Syntax_: ! 'RESULT = GETPID()' _Return value_: ! The return value of 'GETPID' is an 'INTEGER' of the default kind. _Example_: program info --- 11314,11323 ---- Function _Syntax_: ! `RESULT = GETPID()' _Return value_: ! The return value of `GETPID' is an `INTEGER' of the default kind. _Example_: program info *************** _See also_: *** 11236,11242 ****  File: gfortran.info, Node: GETUID, Next: GMTIME, Prev: GETPID, Up: Intrinsic Procedures ! 9.122 'GETUID' -- User ID function ================================== _Description_: --- 11332,11338 ----  File: gfortran.info, Node: GETUID, Next: GMTIME, Prev: GETPID, Up: Intrinsic Procedures ! 9.122 `GETUID' -- User ID function ================================== _Description_: *************** _Class_: *** 11249,11261 **** Function _Syntax_: ! 'RESULT = GETUID()' _Return value_: ! The return value of 'GETUID' is an 'INTEGER' of the default kind. _Example_: ! See 'GETPID' for an example. _See also_: *note GETPID::, *note GETLOG:: --- 11345,11357 ---- Function _Syntax_: ! `RESULT = GETUID()' _Return value_: ! The return value of `GETUID' is an `INTEGER' of the default kind. _Example_: ! See `GETPID' for an example. _See also_: *note GETPID::, *note GETLOG:: *************** _See also_: *** 11263,11276 ****  File: gfortran.info, Node: GMTIME, Next: HOSTNM, Prev: GETUID, Up: Intrinsic Procedures ! 9.123 'GMTIME' -- Convert time to GMT info ========================================== _Description_: ! Given a system time value TIME (as provided by the 'TIME8' intrinsic), fills VALUES with values extracted from it appropriate to the UTC time zone (Universal Coordinated Time, also known in ! some countries as GMT, Greenwich Mean Time), using 'gmtime(3)'. _Standard_: GNU extension --- 11359,11372 ----  File: gfortran.info, Node: GMTIME, Next: HOSTNM, Prev: GETUID, Up: Intrinsic Procedures ! 9.123 `GMTIME' -- Convert time to GMT info ========================================== _Description_: ! Given a system time value TIME (as provided by the `TIME8' intrinsic), fills VALUES with values extracted from it appropriate to the UTC time zone (Universal Coordinated Time, also known in ! some countries as GMT, Greenwich Mean Time), using `gmtime(3)'. _Standard_: GNU extension *************** _Class_: *** 11279,11303 **** Subroutine _Syntax_: ! 'CALL GMTIME(TIME, VALUES)' _Arguments_: ! TIME An 'INTEGER' scalar expression corresponding to ! a system time, with 'INTENT(IN)'. ! VALUES A default 'INTEGER' array with 9 elements, with ! 'INTENT(OUT)'. _Return value_: The elements of VALUES are assigned as follows: 1. Seconds after the minute, range 0-59 or 0-61 to allow for leap seconds 2. Minutes after the hour, range 0-59 3. Hours past midnight, range 0-23 4. Day of month, range 0-31 5. Number of months since January, range 0-12 6. Years since 1900 7. Number of days since Sunday, range 0-6 8. Days since January 1 9. Daylight savings indicator: positive if daylight savings is in effect, zero if not, and negative if the information is not available. --- 11375,11407 ---- Subroutine _Syntax_: ! `CALL GMTIME(TIME, VALUES)' _Arguments_: ! TIME An `INTEGER' scalar expression corresponding ! to a system time, with `INTENT(IN)'. ! VALUES A default `INTEGER' array with 9 elements, ! with `INTENT(OUT)'. _Return value_: The elements of VALUES are assigned as follows: 1. Seconds after the minute, range 0-59 or 0-61 to allow for leap seconds + 2. Minutes after the hour, range 0-59 + 3. Hours past midnight, range 0-23 + 4. Day of month, range 0-31 + 5. Number of months since January, range 0-12 + 6. Years since 1900 + 7. Number of days since Sunday, range 0-6 + 8. Days since January 1 + 9. Daylight savings indicator: positive if daylight savings is in effect, zero if not, and negative if the information is not available. *************** _Return value_: *** 11305,11314 **** _See also_: *note CTIME::, *note LTIME::, *note TIME::, *note TIME8::  File: gfortran.info, Node: HOSTNM, Next: HUGE, Prev: GMTIME, Up: Intrinsic Procedures ! 9.124 'HOSTNM' -- Get system host name ====================================== _Description_: --- 11409,11419 ---- _See also_: *note CTIME::, *note LTIME::, *note TIME::, *note TIME8:: +  File: gfortran.info, Node: HOSTNM, Next: HUGE, Prev: GMTIME, Up: Intrinsic Procedures ! 9.124 `HOSTNM' -- Get system host name ====================================== _Description_: *************** _Class_: *** 11325,11352 **** Subroutine, function _Syntax_: ! 'CALL HOSTNM(C [, STATUS])' ! 'STATUS = HOSTNM(NAME)' _Arguments_: ! C Shall of type 'CHARACTER' and of default kind. ! STATUS (Optional) status flag of type 'INTEGER'. ! Returns 0 on success, or a system specific error ! code otherwise. _Return value_: In either syntax, NAME is set to the current hostname if it can be obtained, or to a blank string otherwise.  File: gfortran.info, Node: HUGE, Next: HYPOT, Prev: HOSTNM, Up: Intrinsic Procedures ! 9.125 'HUGE' -- Largest number of a kind ======================================== _Description_: ! 'HUGE(X)' returns the largest number that is not an infinity in the ! model of the type of 'X'. _Standard_: Fortran 95 and later --- 11430,11458 ---- Subroutine, function _Syntax_: ! `CALL HOSTNM(C [, STATUS])' ! `STATUS = HOSTNM(NAME)' _Arguments_: ! C Shall of type `CHARACTER' and of default kind. ! STATUS (Optional) status flag of type `INTEGER'. ! Returns 0 on success, or a system specific ! error code otherwise. _Return value_: In either syntax, NAME is set to the current hostname if it can be obtained, or to a blank string otherwise. +  File: gfortran.info, Node: HUGE, Next: HYPOT, Prev: HOSTNM, Up: Intrinsic Procedures ! 9.125 `HUGE' -- Largest number of a kind ======================================== _Description_: ! `HUGE(X)' returns the largest number that is not an infinity in ! the model of the type of `X'. _Standard_: Fortran 95 and later *************** _Class_: *** 11355,11364 **** Inquiry function _Syntax_: ! 'RESULT = HUGE(X)' _Arguments_: ! X Shall be of type 'REAL' or 'INTEGER'. _Return value_: The return value is of the same type and kind as X --- 11461,11470 ---- Inquiry function _Syntax_: ! `RESULT = HUGE(X)' _Arguments_: ! X Shall be of type `REAL' or `INTEGER'. _Return value_: The return value is of the same type and kind as X *************** _Example_: *** 11372,11383 ****  File: gfortran.info, Node: HYPOT, Next: IACHAR, Prev: HUGE, Up: Intrinsic Procedures ! 9.126 'HYPOT' -- Euclidean distance function ============================================ _Description_: ! 'HYPOT(X,Y)' is the Euclidean distance function. It is equal to ! \sqrt{X^2 + Y^2}, without undue underflow or overflow. _Standard_: Fortran 2008 and later --- 11478,11489 ----  File: gfortran.info, Node: HYPOT, Next: IACHAR, Prev: HUGE, Up: Intrinsic Procedures ! 9.126 `HYPOT' -- Euclidean distance function ============================================ _Description_: ! `HYPOT(X,Y)' is the Euclidean distance function. It is equal to ! \sqrtX^2 + Y^2, without undue underflow or overflow. _Standard_: Fortran 2008 and later *************** _Class_: *** 11386,11397 **** Elemental function _Syntax_: ! 'RESULT = HYPOT(X, Y)' _Arguments_: ! X The type shall be 'REAL'. ! Y The type and kind type parameter shall be the ! same as X. _Return value_: The return value has the same type and kind type parameter as X. --- 11492,11503 ---- Elemental function _Syntax_: ! `RESULT = HYPOT(X, Y)' _Arguments_: ! X The type shall be `REAL'. ! Y The type and kind type parameter shall be the ! same as X. _Return value_: The return value has the same type and kind type parameter as X. *************** _Example_: *** 11405,11416 ****  File: gfortran.info, Node: IACHAR, Next: IALL, Prev: HYPOT, Up: Intrinsic Procedures ! 9.127 'IACHAR' -- Code in ASCII collating sequence ================================================== _Description_: ! 'IACHAR(C)' returns the code for the ASCII character in the first ! character position of 'C'. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later --- 11511,11522 ----  File: gfortran.info, Node: IACHAR, Next: IALL, Prev: HYPOT, Up: Intrinsic Procedures ! 9.127 `IACHAR' -- Code in ASCII collating sequence ================================================== _Description_: ! `IACHAR(C)' returns the code for the ASCII character in the first ! character position of `C'. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later *************** _Class_: *** 11419,11434 **** Elemental function _Syntax_: ! 'RESULT = IACHAR(C [, KIND])' _Arguments_: ! C Shall be a scalar 'CHARACTER', with 'INTENT(IN)' ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: --- 11525,11541 ---- Elemental function _Syntax_: ! `RESULT = IACHAR(C [, KIND])' _Arguments_: ! C Shall be a scalar `CHARACTER', with ! `INTENT(IN)' ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: *************** _Note_: *** 11444,11458 **** _See also_: *note ACHAR::, *note CHAR::, *note ICHAR::  File: gfortran.info, Node: IALL, Next: IAND, Prev: IACHAR, Up: Intrinsic Procedures ! 9.128 'IALL' -- Bitwise AND of array elements ============================================= _Description_: Reduces with bitwise AND the elements of ARRAY along dimension DIM ! if the corresponding element in MASK is 'TRUE'. _Standard_: Fortran 2008 and later --- 11551,11566 ---- _See also_: *note ACHAR::, *note CHAR::, *note ICHAR:: +  File: gfortran.info, Node: IALL, Next: IAND, Prev: IACHAR, Up: Intrinsic Procedures ! 9.128 `IALL' -- Bitwise AND of array elements ============================================= _Description_: Reduces with bitwise AND the elements of ARRAY along dimension DIM ! if the corresponding element in MASK is `TRUE'. _Standard_: Fortran 2008 and later *************** _Class_: *** 11461,11483 **** Transformational function _Syntax_: ! 'RESULT = IALL(ARRAY[, MASK])' ! 'RESULT = IALL(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER' ! DIM (Optional) shall be a scalar of type 'INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type 'LOGICAL' and either ! be a scalar or an array of the same shape as ! ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the bitwise ALL of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. --- 11569,11591 ---- Transformational function _Syntax_: ! `RESULT = IALL(ARRAY[, MASK])' ! `RESULT = IALL(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER' ! DIM (Optional) shall be a scalar of type `INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type `LOGICAL' and ! either be a scalar or an array of the same ! shape as ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the bitwise ALL of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. *************** _See also_: *** 11498,11508 ****  File: gfortran.info, Node: IAND, Next: IANY, Prev: IALL, Up: Intrinsic Procedures ! 9.129 'IAND' -- Bitwise logical and =================================== _Description_: ! Bitwise logical 'AND'. _Standard_: Fortran 95 and later --- 11606,11616 ----  File: gfortran.info, Node: IAND, Next: IANY, Prev: IALL, Up: Intrinsic Procedures ! 9.129 `IAND' -- Bitwise logical and =================================== _Description_: ! Bitwise logical `AND'. _Standard_: Fortran 95 and later *************** _Class_: *** 11511,11528 **** Elemental function _Syntax_: ! 'RESULT = IAND(I, J)' _Arguments_: ! I The type shall be 'INTEGER'. ! J The type shall be 'INTEGER', of the same kind as ! I. (As a GNU extension, different kinds are ! also permitted.) _Return value_: ! The return type is 'INTEGER', of the same kind as the arguments. ! (If the argument kinds differ, it is of the same kind as the larger ! argument.) _Example_: PROGRAM test_iand --- 11619,11636 ---- Elemental function _Syntax_: ! `RESULT = IAND(I, J)' _Arguments_: ! I The type shall be `INTEGER'. ! J The type shall be `INTEGER', of the same kind ! as I. (As a GNU extension, different kinds ! are also permitted.) _Return value_: ! The return type is `INTEGER', of the same kind as the arguments. ! (If the argument kinds differ, it is of the same kind as the ! larger argument.) _Example_: PROGRAM test_iand *************** _See also_: *** 11535,11549 **** *note IOR::, *note IEOR::, *note IBITS::, *note IBSET::, *note IBCLR::, *note NOT::  File: gfortran.info, Node: IANY, Next: IARGC, Prev: IAND, Up: Intrinsic Procedures ! 9.130 'IANY' -- Bitwise OR of array elements ============================================ _Description_: Reduces with bitwise OR (inclusive or) the elements of ARRAY along ! dimension DIM if the corresponding element in MASK is 'TRUE'. _Standard_: Fortran 2008 and later --- 11643,11658 ---- *note IOR::, *note IEOR::, *note IBITS::, *note IBSET::, *note IBCLR::, *note NOT:: +  File: gfortran.info, Node: IANY, Next: IARGC, Prev: IAND, Up: Intrinsic Procedures ! 9.130 `IANY' -- Bitwise OR of array elements ============================================ _Description_: Reduces with bitwise OR (inclusive or) the elements of ARRAY along ! dimension DIM if the corresponding element in MASK is `TRUE'. _Standard_: Fortran 2008 and later *************** _Class_: *** 11552,11574 **** Transformational function _Syntax_: ! 'RESULT = IANY(ARRAY[, MASK])' ! 'RESULT = IANY(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER' ! DIM (Optional) shall be a scalar of type 'INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type 'LOGICAL' and either ! be a scalar or an array of the same shape as ! ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the bitwise OR of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. --- 11661,11683 ---- Transformational function _Syntax_: ! `RESULT = IANY(ARRAY[, MASK])' ! `RESULT = IANY(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER' ! DIM (Optional) shall be a scalar of type `INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type `LOGICAL' and ! either be a scalar or an array of the same ! shape as ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the bitwise OR of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. *************** _See also_: *** 11589,11599 ****  File: gfortran.info, Node: IARGC, Next: IBCLR, Prev: IANY, Up: Intrinsic Procedures ! 9.131 'IARGC' -- Get the number of command line arguments ========================================================= _Description_: ! 'IARGC' returns the number of arguments passed on the command line when the containing program was invoked. This intrinsic routine is provided for backwards compatibility with --- 11698,11708 ----  File: gfortran.info, Node: IARGC, Next: IBCLR, Prev: IANY, Up: Intrinsic Procedures ! 9.131 `IARGC' -- Get the number of command line arguments ========================================================= _Description_: ! `IARGC' returns the number of arguments passed on the command line when the containing program was invoked. This intrinsic routine is provided for backwards compatibility with *************** _Class_: *** 11608,11620 **** Function _Syntax_: ! 'RESULT = IARGC()' _Arguments_: None. _Return value_: ! The number of command line arguments, type 'INTEGER(4)'. _Example_: See *note GETARG:: --- 11717,11729 ---- Function _Syntax_: ! `RESULT = IARGC()' _Arguments_: None. _Return value_: ! The number of command line arguments, type `INTEGER(4)'. _Example_: See *note GETARG:: *************** _See also_: *** 11628,11638 ****  File: gfortran.info, Node: IBCLR, Next: IBITS, Prev: IARGC, Up: Intrinsic Procedures ! 9.132 'IBCLR' -- Clear bit ========================== _Description_: ! 'IBCLR' returns the value of I with the bit at position POS set to zero. _Standard_: --- 11737,11747 ----  File: gfortran.info, Node: IBCLR, Next: IBITS, Prev: IARGC, Up: Intrinsic Procedures ! 9.132 `IBCLR' -- Clear bit ========================== _Description_: ! `IBCLR' returns the value of I with the bit at position POS set to zero. _Standard_: *************** _Class_: *** 11642,11671 **** Elemental function _Syntax_: ! 'RESULT = IBCLR(I, POS)' _Arguments_: ! I The type shall be 'INTEGER'. ! POS The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note IBITS::, *note IBSET::, *note IAND::, *note IOR::, *note IEOR::, *note MVBITS::  File: gfortran.info, Node: IBITS, Next: IBSET, Prev: IBCLR, Up: Intrinsic Procedures ! 9.133 'IBITS' -- Bit extraction =============================== _Description_: ! 'IBITS' extracts a field of length LEN from I, starting from bit position POS and extending left for LEN bits. The result is right-justified and the remaining bits are zeroed. The value of ! 'POS+LEN' must be less than or equal to the value 'BIT_SIZE(I)'. _Standard_: Fortran 95 and later --- 11751,11781 ---- Elemental function _Syntax_: ! `RESULT = IBCLR(I, POS)' _Arguments_: ! I The type shall be `INTEGER'. ! POS The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note IBITS::, *note IBSET::, *note IAND::, *note IOR::, *note IEOR::, *note MVBITS:: +  File: gfortran.info, Node: IBITS, Next: IBSET, Prev: IBCLR, Up: Intrinsic Procedures ! 9.133 `IBITS' -- Bit extraction =============================== _Description_: ! `IBITS' extracts a field of length LEN from I, starting from bit position POS and extending left for LEN bits. The result is right-justified and the remaining bits are zeroed. The value of ! `POS+LEN' must be less than or equal to the value `BIT_SIZE(I)'. _Standard_: Fortran 95 and later *************** _Class_: *** 11674,11701 **** Elemental function _Syntax_: ! 'RESULT = IBITS(I, POS, LEN)' _Arguments_: ! I The type shall be 'INTEGER'. ! POS The type shall be 'INTEGER'. ! LEN The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: ! *note BIT_SIZE::, *note IBCLR::, *note IBSET::, *note IAND::, *note ! IOR::, *note IEOR::  File: gfortran.info, Node: IBSET, Next: ICHAR, Prev: IBITS, Up: Intrinsic Procedures ! 9.134 'IBSET' -- Set bit ======================== _Description_: ! 'IBSET' returns the value of I with the bit at position POS set to one. _Standard_: --- 11784,11811 ---- Elemental function _Syntax_: ! `RESULT = IBITS(I, POS, LEN)' _Arguments_: ! I The type shall be `INTEGER'. ! POS The type shall be `INTEGER'. ! LEN The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: ! *note BIT_SIZE::, *note IBCLR::, *note IBSET::, *note IAND::, ! *note IOR::, *note IEOR::  File: gfortran.info, Node: IBSET, Next: ICHAR, Prev: IBITS, Up: Intrinsic Procedures ! 9.134 `IBSET' -- Set bit ======================== _Description_: ! `IBSET' returns the value of I with the bit at position POS set to one. _Standard_: *************** _Class_: *** 11705,11732 **** Elemental function _Syntax_: ! 'RESULT = IBSET(I, POS)' _Arguments_: ! I The type shall be 'INTEGER'. ! POS The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note IBCLR::, *note IBITS::, *note IAND::, *note IOR::, *note IEOR::, *note MVBITS::  File: gfortran.info, Node: ICHAR, Next: IDATE, Prev: IBSET, Up: Intrinsic Procedures ! 9.135 'ICHAR' -- Character-to-integer conversion function ========================================================= _Description_: ! 'ICHAR(C)' returns the code for the character in the first ! character position of 'C' in the system's native character set. The correspondence between characters and their codes is not necessarily the same across different GNU Fortran implementations. --- 11815,11843 ---- Elemental function _Syntax_: ! `RESULT = IBSET(I, POS)' _Arguments_: ! I The type shall be `INTEGER'. ! POS The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note IBCLR::, *note IBITS::, *note IAND::, *note IOR::, *note IEOR::, *note MVBITS:: +  File: gfortran.info, Node: ICHAR, Next: IDATE, Prev: IBSET, Up: Intrinsic Procedures ! 9.135 `ICHAR' -- Character-to-integer conversion function ========================================================= _Description_: ! `ICHAR(C)' returns the code for the character in the first ! character position of `C' in the system's native character set. The correspondence between characters and their codes is not necessarily the same across different GNU Fortran implementations. *************** _Class_: *** 11737,11752 **** Elemental function _Syntax_: ! 'RESULT = ICHAR(C [, KIND])' _Arguments_: ! C Shall be a scalar 'CHARACTER', with 'INTENT(IN)' ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: --- 11848,11864 ---- Elemental function _Syntax_: ! `RESULT = ICHAR(C [, KIND])' _Arguments_: ! C Shall be a scalar `CHARACTER', with ! `INTENT(IN)' ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: *************** _Example_: *** 11756,11770 **** end program test_ichar _Specific names_: ! Name Argument Return type Standard ! 'ICHAR(C)' 'CHARACTER 'INTEGER(4)' Fortran 77 and ! C' later _Note_: No intrinsic exists to convert between a numeric value and a formatted character string representation - for instance, given the ! 'CHARACTER' value ''154'', obtaining an 'INTEGER' or 'REAL' value ! with the value 154, or vice versa. Instead, this functionality is provided by internal-file I/O, as in the following example: program read_val integer value --- 11868,11882 ---- end program test_ichar _Specific names_: ! Name Argument Return type Standard ! `ICHAR(C)' `CHARACTER `INTEGER(4)' Fortran 77 and ! C' later _Note_: No intrinsic exists to convert between a numeric value and a formatted character string representation - for instance, given the ! `CHARACTER' value `'154'', obtaining an `INTEGER' or `REAL' value ! with the value 154, or vice versa. Instead, this functionality is provided by internal-file I/O, as in the following example: program read_val integer value *************** _Note_: *** 11783,11797 **** _See also_: *note ACHAR::, *note CHAR::, *note IACHAR::  File: gfortran.info, Node: IDATE, Next: IEOR, Prev: ICHAR, Up: Intrinsic Procedures ! 9.136 'IDATE' -- Get current local time subroutine (day/month/year) =================================================================== _Description_: ! 'IDATE(VALUES)' Fills VALUES with the numerical values at the ! current local time. The day (in the range 1-31), month (in the range 1-12), and year appear in elements 1, 2, and 3 of VALUES, respectively. The year has four significant digits. --- 11895,11910 ---- _See also_: *note ACHAR::, *note CHAR::, *note IACHAR:: +  File: gfortran.info, Node: IDATE, Next: IEOR, Prev: ICHAR, Up: Intrinsic Procedures ! 9.136 `IDATE' -- Get current local time subroutine (day/month/year) =================================================================== _Description_: ! `IDATE(VALUES)' Fills VALUES with the numerical values at the ! current local time. The day (in the range 1-31), month (in the range 1-12), and year appear in elements 1, 2, and 3 of VALUES, respectively. The year has four significant digits. *************** _Class_: *** 11802,11812 **** Subroutine _Syntax_: ! 'CALL IDATE(VALUES)' _Arguments_: ! VALUES The type shall be 'INTEGER, DIMENSION(3)' and ! the kind shall be the default integer kind. _Return value_: Does not return anything. --- 11915,11925 ---- Subroutine _Syntax_: ! `CALL IDATE(VALUES)' _Arguments_: ! VALUES The type shall be `INTEGER, DIMENSION(3)' and ! the kind shall be the default integer kind. _Return value_: Does not return anything. *************** _Example_: *** 11823,11833 ****  File: gfortran.info, Node: IEOR, Next: IERRNO, Prev: IDATE, Up: Intrinsic Procedures ! 9.137 'IEOR' -- Bitwise logical exclusive or ============================================ _Description_: ! 'IEOR' returns the bitwise Boolean exclusive-OR of I and J. _Standard_: Fortran 95 and later --- 11936,11946 ----  File: gfortran.info, Node: IEOR, Next: IERRNO, Prev: IDATE, Up: Intrinsic Procedures ! 9.137 `IEOR' -- Bitwise logical exclusive or ============================================ _Description_: ! `IEOR' returns the bitwise Boolean exclusive-OR of I and J. _Standard_: Fortran 95 and later *************** _Class_: *** 11836,11853 **** Elemental function _Syntax_: ! 'RESULT = IEOR(I, J)' _Arguments_: ! I The type shall be 'INTEGER'. ! J The type shall be 'INTEGER', of the same kind as ! I. (As a GNU extension, different kinds are ! also permitted.) _Return value_: ! The return type is 'INTEGER', of the same kind as the arguments. ! (If the argument kinds differ, it is of the same kind as the larger ! argument.) _See also_: *note IOR::, *note IAND::, *note IBITS::, *note IBSET::, *note --- 11949,11966 ---- Elemental function _Syntax_: ! `RESULT = IEOR(I, J)' _Arguments_: ! I The type shall be `INTEGER'. ! J The type shall be `INTEGER', of the same kind ! as I. (As a GNU extension, different kinds ! are also permitted.) _Return value_: ! The return type is `INTEGER', of the same kind as the arguments. ! (If the argument kinds differ, it is of the same kind as the ! larger argument.) _See also_: *note IOR::, *note IAND::, *note IBITS::, *note IBSET::, *note *************** _See also_: *** 11856,11866 ****  File: gfortran.info, Node: IERRNO, Next: IMAGE_INDEX, Prev: IEOR, Up: Intrinsic Procedures ! 9.138 'IERRNO' -- Get the last system error number ================================================== _Description_: ! Returns the last system error number, as given by the C 'errno' variable. _Standard_: --- 11969,11979 ----  File: gfortran.info, Node: IERRNO, Next: IMAGE_INDEX, Prev: IEOR, Up: Intrinsic Procedures ! 9.138 `IERRNO' -- Get the last system error number ================================================== _Description_: ! Returns the last system error number, as given by the C `errno' variable. _Standard_: *************** _Class_: *** 11870,11882 **** Function _Syntax_: ! 'RESULT = IERRNO()' _Arguments_: None. _Return value_: ! The return value is of type 'INTEGER' and of the default integer kind. _See also_: --- 11983,11995 ---- Function _Syntax_: ! `RESULT = IERRNO()' _Arguments_: None. _Return value_: ! The return value is of type `INTEGER' and of the default integer kind. _See also_: *************** _See also_: *** 11885,11891 ****  File: gfortran.info, Node: IMAGE_INDEX, Next: INDEX intrinsic, Prev: IERRNO, Up: Intrinsic Procedures ! 9.139 'IMAGE_INDEX' -- Function that converts a cosubscript to an image index ============================================================================= _Description_: --- 11998,12004 ----  File: gfortran.info, Node: IMAGE_INDEX, Next: INDEX intrinsic, Prev: IERRNO, Up: Intrinsic Procedures ! 9.139 `IMAGE_INDEX' -- Function that converts a cosubscript to an image index ============================================================================= _Description_: *************** _Class_: *** 11898,11913 **** Inquiry function. _Syntax_: ! 'RESULT = IMAGE_INDEX(COARRAY, SUB)' _Arguments_: None. ! COARRAY Coarray of any type. ! SUB default integer rank-1 array of a size equal to ! the corank of COARRAY. _Return value_: Scalar default integer with the value of the image index which ! corresponds to the cosubscripts. For invalid cosubscripts the result is zero. _Example_: --- 12011,12026 ---- Inquiry function. _Syntax_: ! `RESULT = IMAGE_INDEX(COARRAY, SUB)' _Arguments_: None. ! COARRAY Coarray of any type. ! SUB default integer rank-1 array of a size equal to ! the corank of COARRAY. _Return value_: Scalar default integer with the value of the image index which ! corresponds to the cosubscripts. For invalid cosubscripts the result is zero. _Example_: *************** _See also_: *** 11921,11927 ****  File: gfortran.info, Node: INDEX intrinsic, Next: INT, Prev: IMAGE_INDEX, Up: Intrinsic Procedures ! 9.140 'INDEX' -- Position of a substring within a string ======================================================== _Description_: --- 12034,12040 ----  File: gfortran.info, Node: INDEX intrinsic, Next: INT, Prev: IMAGE_INDEX, Up: Intrinsic Procedures ! 9.140 `INDEX' -- Position of a substring within a string ======================================================== _Description_: *************** _Class_: *** 11938,11962 **** Elemental function _Syntax_: ! 'RESULT = INDEX(STRING, SUBSTRING [, BACK [, KIND]])' _Arguments_: ! STRING Shall be a scalar 'CHARACTER', with 'INTENT(IN)' ! SUBSTRING Shall be a scalar 'CHARACTER', with 'INTENT(IN)' ! BACK (Optional) Shall be a scalar 'LOGICAL', with ! 'INTENT(IN)' ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Specific names_: ! Name Argument Return type Standard ! 'INDEX(STRING, 'CHARACTER' 'INTEGER(4)' Fortran 77 and ! SUBSTRING)' later _See also_: *note SCAN::, *note VERIFY:: --- 12051,12077 ---- Elemental function _Syntax_: ! `RESULT = INDEX(STRING, SUBSTRING [, BACK [, KIND]])' _Arguments_: ! STRING Shall be a scalar `CHARACTER', with ! `INTENT(IN)' ! SUBSTRING Shall be a scalar `CHARACTER', with ! `INTENT(IN)' ! BACK (Optional) Shall be a scalar `LOGICAL', with ! `INTENT(IN)' ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Specific names_: ! Name Argument Return type Standard ! `INDEX(STRING,`CHARACTER' `INTEGER(4)' Fortran 77 and ! SUBSTRING)' later _See also_: *note SCAN::, *note VERIFY:: *************** _See also_: *** 11964,11970 ****  File: gfortran.info, Node: INT, Next: INT2, Prev: INDEX intrinsic, Up: Intrinsic Procedures ! 9.141 'INT' -- Convert to integer type ====================================== _Description_: --- 12079,12085 ----  File: gfortran.info, Node: INT, Next: INT2, Prev: INDEX intrinsic, Up: Intrinsic Procedures ! 9.141 `INT' -- Convert to integer type ====================================== _Description_: *************** _Class_: *** 11977,12004 **** Elemental function _Syntax_: ! 'RESULT = INT(A [, KIND))' _Arguments_: ! A Shall be of type 'INTEGER', 'REAL', or ! 'COMPLEX'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! These functions return a 'INTEGER' variable or array under the following rules: ! (A) ! If A is of type 'INTEGER', 'INT(A) = A' ! (B) ! If A is of type 'REAL' and |A| < 1, 'INT(A)' equals '0'. If ! |A| \geq 1, then 'INT(A)' is the integer whose magnitude is the largest integer that does not exceed the magnitude of A and whose sign is the same as the sign of A. ! (C) ! If A is of type 'COMPLEX', rule B is applied to the real part of A. _Example_: --- 12092,12121 ---- Elemental function _Syntax_: ! `RESULT = INT(A [, KIND))' _Arguments_: ! A Shall be of type `INTEGER', `REAL', or ! `COMPLEX'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! These functions return a `INTEGER' variable or array under the following rules: ! (A) ! If A is of type `INTEGER', `INT(A) = A' ! ! (B) ! If A is of type `REAL' and |A| < 1, `INT(A)' equals `0'. If ! |A| \geq 1, then `INT(A)' is the integer whose magnitude is the largest integer that does not exceed the magnitude of A and whose sign is the same as the sign of A. ! ! (C) ! If A is of type `COMPLEX', rule B is applied to the real part of A. _Example_: *************** _Example_: *** 12010,12035 **** end program _Specific names_: ! Name Argument Return type Standard ! 'INT(A)' 'REAL(4) A' 'INTEGER' Fortran 77 and ! later ! 'IFIX(A)' 'REAL(4) A' 'INTEGER' Fortran 77 and ! later ! 'IDINT(A)' 'REAL(8) A' 'INTEGER' Fortran 77 and ! later  File: gfortran.info, Node: INT2, Next: INT8, Prev: INT, Up: Intrinsic Procedures ! 9.142 'INT2' -- Convert to 16-bit integer type ============================================== _Description_: ! Convert to a 'KIND=2' integer type. This is equivalent to the ! standard 'INT' intrinsic with an optional argument of 'KIND=2', and ! is only included for backwards compatibility. ! The 'SHORT' intrinsic is equivalent to 'INT2'. _Standard_: GNU extension --- 12127,12153 ---- end program _Specific names_: ! Name Argument Return type Standard ! `INT(A)' `REAL(4) A' `INTEGER' Fortran 77 and ! later ! `IFIX(A)' `REAL(4) A' `INTEGER' Fortran 77 and ! later ! `IDINT(A)' `REAL(8) A' `INTEGER' Fortran 77 and ! later !  File: gfortran.info, Node: INT2, Next: INT8, Prev: INT, Up: Intrinsic Procedures ! 9.142 `INT2' -- Convert to 16-bit integer type ============================================== _Description_: ! Convert to a `KIND=2' integer type. This is equivalent to the ! standard `INT' intrinsic with an optional argument of `KIND=2', ! and is only included for backwards compatibility. ! The `SHORT' intrinsic is equivalent to `INT2'. _Standard_: GNU extension *************** _Class_: *** 12038,12051 **** Elemental function _Syntax_: ! 'RESULT = INT2(A)' _Arguments_: ! A Shall be of type 'INTEGER', 'REAL', or ! 'COMPLEX'. _Return value_: ! The return value is a 'INTEGER(2)' variable. _See also_: *note INT::, *note INT8::, *note LONG:: --- 12156,12169 ---- Elemental function _Syntax_: ! `RESULT = INT2(A)' _Arguments_: ! A Shall be of type `INTEGER', `REAL', or ! `COMPLEX'. _Return value_: ! The return value is a `INTEGER(2)' variable. _See also_: *note INT::, *note INT8::, *note LONG:: *************** _See also_: *** 12053,12065 ****  File: gfortran.info, Node: INT8, Next: IOR, Prev: INT2, Up: Intrinsic Procedures ! 9.143 'INT8' -- Convert to 64-bit integer type ============================================== _Description_: ! Convert to a 'KIND=8' integer type. This is equivalent to the ! standard 'INT' intrinsic with an optional argument of 'KIND=8', and ! is only included for backwards compatibility. _Standard_: GNU extension --- 12171,12183 ----  File: gfortran.info, Node: INT8, Next: IOR, Prev: INT2, Up: Intrinsic Procedures ! 9.143 `INT8' -- Convert to 64-bit integer type ============================================== _Description_: ! Convert to a `KIND=8' integer type. This is equivalent to the ! standard `INT' intrinsic with an optional argument of `KIND=8', ! and is only included for backwards compatibility. _Standard_: GNU extension *************** _Class_: *** 12068,12081 **** Elemental function _Syntax_: ! 'RESULT = INT8(A)' _Arguments_: ! A Shall be of type 'INTEGER', 'REAL', or ! 'COMPLEX'. _Return value_: ! The return value is a 'INTEGER(8)' variable. _See also_: *note INT::, *note INT2::, *note LONG:: --- 12186,12199 ---- Elemental function _Syntax_: ! `RESULT = INT8(A)' _Arguments_: ! A Shall be of type `INTEGER', `REAL', or ! `COMPLEX'. _Return value_: ! The return value is a `INTEGER(8)' variable. _See also_: *note INT::, *note INT2::, *note LONG:: *************** _See also_: *** 12083,12093 ****  File: gfortran.info, Node: IOR, Next: IPARITY, Prev: INT8, Up: Intrinsic Procedures ! 9.144 'IOR' -- Bitwise logical or ================================= _Description_: ! 'IOR' returns the bitwise Boolean inclusive-OR of I and J. _Standard_: Fortran 95 and later --- 12201,12211 ----  File: gfortran.info, Node: IOR, Next: IPARITY, Prev: INT8, Up: Intrinsic Procedures ! 9.144 `IOR' -- Bitwise logical or ================================= _Description_: ! `IOR' returns the bitwise Boolean inclusive-OR of I and J. _Standard_: Fortran 95 and later *************** _Class_: *** 12096,12113 **** Elemental function _Syntax_: ! 'RESULT = IOR(I, J)' _Arguments_: ! I The type shall be 'INTEGER'. ! J The type shall be 'INTEGER', of the same kind as ! I. (As a GNU extension, different kinds are ! also permitted.) _Return value_: ! The return type is 'INTEGER', of the same kind as the arguments. ! (If the argument kinds differ, it is of the same kind as the larger ! argument.) _See also_: *note IEOR::, *note IAND::, *note IBITS::, *note IBSET::, *note --- 12214,12231 ---- Elemental function _Syntax_: ! `RESULT = IOR(I, J)' _Arguments_: ! I The type shall be `INTEGER'. ! J The type shall be `INTEGER', of the same kind ! as I. (As a GNU extension, different kinds ! are also permitted.) _Return value_: ! The return type is `INTEGER', of the same kind as the arguments. ! (If the argument kinds differ, it is of the same kind as the ! larger argument.) _See also_: *note IEOR::, *note IAND::, *note IBITS::, *note IBSET::, *note *************** _See also_: *** 12116,12127 ****  File: gfortran.info, Node: IPARITY, Next: IRAND, Prev: IOR, Up: Intrinsic Procedures ! 9.145 'IPARITY' -- Bitwise XOR of array elements ================================================ _Description_: Reduces with bitwise XOR (exclusive or) the elements of ARRAY along ! dimension DIM if the corresponding element in MASK is 'TRUE'. _Standard_: Fortran 2008 and later --- 12234,12245 ----  File: gfortran.info, Node: IPARITY, Next: IRAND, Prev: IOR, Up: Intrinsic Procedures ! 9.145 `IPARITY' -- Bitwise XOR of array elements ================================================ _Description_: Reduces with bitwise XOR (exclusive or) the elements of ARRAY along ! dimension DIM if the corresponding element in MASK is `TRUE'. _Standard_: Fortran 2008 and later *************** _Class_: *** 12130,12152 **** Transformational function _Syntax_: ! 'RESULT = IPARITY(ARRAY[, MASK])' ! 'RESULT = IPARITY(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER' ! DIM (Optional) shall be a scalar of type 'INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type 'LOGICAL' and either ! be a scalar or an array of the same shape as ! ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the bitwise XOR of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. --- 12248,12270 ---- Transformational function _Syntax_: ! `RESULT = IPARITY(ARRAY[, MASK])' ! `RESULT = IPARITY(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER' ! DIM (Optional) shall be a scalar of type `INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type `LOGICAL' and ! either be a scalar or an array of the same ! shape as ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the bitwise XOR of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. *************** _See also_: *** 12167,12187 ****  File: gfortran.info, Node: IRAND, Next: IS_IOSTAT_END, Prev: IPARITY, Up: Intrinsic Procedures ! 9.146 'IRAND' -- Integer pseudo-random number ============================================= _Description_: ! 'IRAND(FLAG)' returns a pseudo-random number from a uniform distribution between 0 and a system-dependent limit (which is in ! most cases 2147483647). If FLAG is 0, the next number in the current sequence is returned; if FLAG is 1, the generator is ! restarted by 'CALL SRAND(0)'; if FLAG has any other value, it is ! used as a new seed with 'SRAND'. This intrinsic routine is provided for backwards compatibility with ! GNU Fortran 77. It implements a simple modulo generator as ! provided by 'g77'. For new code, one should consider the use of ! *note RANDOM_NUMBER:: as it implements a superior algorithm. _Standard_: GNU extension --- 12285,12305 ----  File: gfortran.info, Node: IRAND, Next: IS_IOSTAT_END, Prev: IPARITY, Up: Intrinsic Procedures ! 9.146 `IRAND' -- Integer pseudo-random number ============================================= _Description_: ! `IRAND(FLAG)' returns a pseudo-random number from a uniform distribution between 0 and a system-dependent limit (which is in ! most cases 2147483647). If FLAG is 0, the next number in the current sequence is returned; if FLAG is 1, the generator is ! restarted by `CALL SRAND(0)'; if FLAG has any other value, it is ! used as a new seed with `SRAND'. This intrinsic routine is provided for backwards compatibility with ! GNU Fortran 77. It implements a simple modulo generator as provided ! by `g77'. For new code, one should consider the use of *note ! RANDOM_NUMBER:: as it implements a superior algorithm. _Standard_: GNU extension *************** _Class_: *** 12190,12202 **** Function _Syntax_: ! 'RESULT = IRAND(I)' _Arguments_: ! I Shall be a scalar 'INTEGER' of kind 4. _Return value_: ! The return value is of 'INTEGER(kind=4)' type. _Example_: program test_irand --- 12308,12320 ---- Function _Syntax_: ! `RESULT = IRAND(I)' _Arguments_: ! I Shall be a scalar `INTEGER' of kind 4. _Return value_: ! The return value is of `INTEGER(kind=4)' type. _Example_: program test_irand *************** _Example_: *** 12207,12223 **** print *, irand(seed), irand(), irand(), irand() end program test_irand  File: gfortran.info, Node: IS_IOSTAT_END, Next: IS_IOSTAT_EOR, Prev: IRAND, Up: Intrinsic Procedures ! 9.147 'IS_IOSTAT_END' -- Test for end-of-file value =================================================== _Description_: ! 'IS_IOSTAT_END' tests whether an variable has the value of the I/O ! status "end of file". The function is equivalent to comparing the ! variable with the 'IOSTAT_END' parameter of the intrinsic module ! 'ISO_FORTRAN_ENV'. _Standard_: Fortran 2003 and later --- 12325,12342 ---- print *, irand(seed), irand(), irand(), irand() end program test_irand +  File: gfortran.info, Node: IS_IOSTAT_END, Next: IS_IOSTAT_EOR, Prev: IRAND, Up: Intrinsic Procedures ! 9.147 `IS_IOSTAT_END' -- Test for end-of-file value =================================================== _Description_: ! `IS_IOSTAT_END' tests whether an variable has the value of the I/O ! status "end of file". The function is equivalent to comparing the ! variable with the `IOSTAT_END' parameter of the intrinsic module ! `ISO_FORTRAN_ENV'. _Standard_: Fortran 2003 and later *************** _Class_: *** 12226,12240 **** Elemental function _Syntax_: ! 'RESULT = IS_IOSTAT_END(I)' _Arguments_: ! I Shall be of the type 'INTEGER'. _Return value_: ! Returns a 'LOGICAL' of the default kind, which '.TRUE.' if I has ! the value which indicates an end of file condition for 'IOSTAT=' ! specifiers, and is '.FALSE.' otherwise. _Example_: PROGRAM iostat --- 12345,12359 ---- Elemental function _Syntax_: ! `RESULT = IS_IOSTAT_END(I)' _Arguments_: ! I Shall be of the type `INTEGER'. _Return value_: ! Returns a `LOGICAL' of the default kind, which `.TRUE.' if I has ! the value which indicates an end of file condition for `IOSTAT=' ! specifiers, and is `.FALSE.' otherwise. _Example_: PROGRAM iostat *************** _Example_: *** 12248,12261 ****  File: gfortran.info, Node: IS_IOSTAT_EOR, Next: ISATTY, Prev: IS_IOSTAT_END, Up: Intrinsic Procedures ! 9.148 'IS_IOSTAT_EOR' -- Test for end-of-record value ===================================================== _Description_: ! 'IS_IOSTAT_EOR' tests whether an variable has the value of the I/O ! status "end of record". The function is equivalent to comparing ! the variable with the 'IOSTAT_EOR' parameter of the intrinsic ! module 'ISO_FORTRAN_ENV'. _Standard_: Fortran 2003 and later --- 12367,12380 ----  File: gfortran.info, Node: IS_IOSTAT_EOR, Next: ISATTY, Prev: IS_IOSTAT_END, Up: Intrinsic Procedures ! 9.148 `IS_IOSTAT_EOR' -- Test for end-of-record value ===================================================== _Description_: ! `IS_IOSTAT_EOR' tests whether an variable has the value of the I/O ! status "end of record". The function is equivalent to comparing the ! variable with the `IOSTAT_EOR' parameter of the intrinsic module ! `ISO_FORTRAN_ENV'. _Standard_: Fortran 2003 and later *************** _Class_: *** 12264,12278 **** Elemental function _Syntax_: ! 'RESULT = IS_IOSTAT_EOR(I)' _Arguments_: ! I Shall be of the type 'INTEGER'. _Return value_: ! Returns a 'LOGICAL' of the default kind, which '.TRUE.' if I has ! the value which indicates an end of file condition for 'IOSTAT=' ! specifiers, and is '.FALSE.' otherwise. _Example_: PROGRAM iostat --- 12383,12397 ---- Elemental function _Syntax_: ! `RESULT = IS_IOSTAT_EOR(I)' _Arguments_: ! I Shall be of the type `INTEGER'. _Return value_: ! Returns a `LOGICAL' of the default kind, which `.TRUE.' if I has ! the value which indicates an end of file condition for `IOSTAT=' ! specifiers, and is `.FALSE.' otherwise. _Example_: PROGRAM iostat *************** _Example_: *** 12286,12292 ****  File: gfortran.info, Node: ISATTY, Next: ISHFT, Prev: IS_IOSTAT_EOR, Up: Intrinsic Procedures ! 9.149 'ISATTY' -- Whether a unit is a terminal device. ====================================================== _Description_: --- 12405,12411 ----  File: gfortran.info, Node: ISATTY, Next: ISHFT, Prev: IS_IOSTAT_EOR, Up: Intrinsic Procedures ! 9.149 `ISATTY' -- Whether a unit is a terminal device. ====================================================== _Description_: *************** _Class_: *** 12299,12312 **** Function _Syntax_: ! 'RESULT = ISATTY(UNIT)' _Arguments_: ! UNIT Shall be a scalar 'INTEGER'. _Return value_: ! Returns '.TRUE.' if the UNIT is connected to a terminal device, ! '.FALSE.' otherwise. _Example_: PROGRAM test_isatty --- 12418,12431 ---- Function _Syntax_: ! `RESULT = ISATTY(UNIT)' _Arguments_: ! UNIT Shall be a scalar `INTEGER'. _Return value_: ! Returns `.TRUE.' if the UNIT is connected to a terminal device, ! `.FALSE.' otherwise. _Example_: PROGRAM test_isatty *************** _Example_: *** 12315,12335 **** write(*,*) isatty(unit=unit) END DO END PROGRAM _See also_: *note TTYNAM::  File: gfortran.info, Node: ISHFT, Next: ISHFTC, Prev: ISATTY, Up: Intrinsic Procedures ! 9.150 'ISHFT' -- Shift bits =========================== _Description_: ! 'ISHFT' returns a value corresponding to I with all of the bits shifted SHIFT places. A value of SHIFT greater than zero corresponds to a left shift, a value of zero corresponds to no ! shift, and a value less than zero corresponds to a right shift. If ! the absolute value of SHIFT is greater than 'BIT_SIZE(I)', the value is undefined. Bits shifted out from the left end or right end are lost; zeros are shifted in from the opposite end. --- 12434,12455 ---- write(*,*) isatty(unit=unit) END DO END PROGRAM + _See also_: *note TTYNAM::  File: gfortran.info, Node: ISHFT, Next: ISHFTC, Prev: ISATTY, Up: Intrinsic Procedures ! 9.150 `ISHFT' -- Shift bits =========================== _Description_: ! `ISHFT' returns a value corresponding to I with all of the bits shifted SHIFT places. A value of SHIFT greater than zero corresponds to a left shift, a value of zero corresponds to no ! shift, and a value less than zero corresponds to a right shift. ! If the absolute value of SHIFT is greater than `BIT_SIZE(I)', the value is undefined. Bits shifted out from the left end or right end are lost; zeros are shifted in from the opposite end. *************** _Class_: *** 12340,12353 **** Elemental function _Syntax_: ! 'RESULT = ISHFT(I, SHIFT)' _Arguments_: ! I The type shall be 'INTEGER'. ! SHIFT The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note ISHFTC:: --- 12460,12473 ---- Elemental function _Syntax_: ! `RESULT = ISHFT(I, SHIFT)' _Arguments_: ! I The type shall be `INTEGER'. ! SHIFT The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note ISHFTC:: *************** _See also_: *** 12355,12372 ****  File: gfortran.info, Node: ISHFTC, Next: ISNAN, Prev: ISHFT, Up: Intrinsic Procedures ! 9.151 'ISHFTC' -- Shift bits circularly ======================================= _Description_: ! 'ISHFTC' returns a value corresponding to I with the rightmost SIZE ! bits shifted circularly SHIFT places; that is, bits shifted out one ! end are shifted into the opposite end. A value of SHIFT greater ! than zero corresponds to a left shift, a value of zero corresponds ! to no shift, and a value less than zero corresponds to a right ! shift. The absolute value of SHIFT must be less than SIZE. If the ! SIZE argument is omitted, it is taken to be equivalent to ! 'BIT_SIZE(I)'. _Standard_: Fortran 95 and later --- 12475,12492 ----  File: gfortran.info, Node: ISHFTC, Next: ISNAN, Prev: ISHFT, Up: Intrinsic Procedures ! 9.151 `ISHFTC' -- Shift bits circularly ======================================= _Description_: ! `ISHFTC' returns a value corresponding to I with the rightmost ! SIZE bits shifted circularly SHIFT places; that is, bits shifted ! out one end are shifted into the opposite end. A value of SHIFT ! greater than zero corresponds to a left shift, a value of zero ! corresponds to no shift, and a value less than zero corresponds to ! a right shift. The absolute value of SHIFT must be less than ! SIZE. If the SIZE argument is omitted, it is taken to be ! equivalent to `BIT_SIZE(I)'. _Standard_: Fortran 95 and later *************** _Class_: *** 12375,12391 **** Elemental function _Syntax_: ! 'RESULT = ISHFTC(I, SHIFT [, SIZE])' _Arguments_: ! I The type shall be 'INTEGER'. ! SHIFT The type shall be 'INTEGER'. ! SIZE (Optional) The type shall be 'INTEGER'; the ! value must be greater than zero and less than or ! equal to 'BIT_SIZE(I)'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note ISHFT:: --- 12495,12511 ---- Elemental function _Syntax_: ! `RESULT = ISHFTC(I, SHIFT [, SIZE])' _Arguments_: ! I The type shall be `INTEGER'. ! SHIFT The type shall be `INTEGER'. ! SIZE (Optional) The type shall be `INTEGER'; the ! value must be greater than zero and less than ! or equal to `BIT_SIZE(I)'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note ISHFT:: *************** _See also_: *** 12393,12404 ****  File: gfortran.info, Node: ISNAN, Next: ITIME, Prev: ISHFTC, Up: Intrinsic Procedures ! 9.152 'ISNAN' -- Test for a NaN =============================== _Description_: ! 'ISNAN' tests whether a floating-point value is an IEEE Not-a-Number (NaN). _Standard_: GNU extension --- 12513,12525 ----  File: gfortran.info, Node: ISNAN, Next: ITIME, Prev: ISHFTC, Up: Intrinsic Procedures ! 9.152 `ISNAN' -- Test for a NaN =============================== _Description_: ! `ISNAN' tests whether a floating-point value is an IEEE Not-a-Number (NaN). + _Standard_: GNU extension *************** _Class_: *** 12406,12420 **** Elemental function _Syntax_: ! 'ISNAN(X)' _Arguments_: ! X Variable of the type 'REAL'. ! _Return value_: ! Returns a default-kind 'LOGICAL'. The returned value is 'TRUE' if ! X is a NaN and 'FALSE' otherwise. _Example_: program test_nan --- 12527,12540 ---- Elemental function _Syntax_: ! `ISNAN(X)' _Arguments_: ! X Variable of the type `REAL'. _Return value_: ! Returns a default-kind `LOGICAL'. The returned value is `TRUE' if ! X is a NaN and `FALSE' otherwise. _Example_: program test_nan *************** _Example_: *** 12428,12439 ****  File: gfortran.info, Node: ITIME, Next: KILL, Prev: ISNAN, Up: Intrinsic Procedures ! 9.153 'ITIME' -- Get current local time subroutine (hour/minutes/seconds) ========================================================================= _Description_: ! 'IDATE(VALUES)' Fills VALUES with the numerical values at the ! current local time. The hour (in the range 1-24), minute (in the range 1-60), and seconds (in the range 1-60) appear in elements 1, 2, and 3 of VALUES, respectively. --- 12548,12559 ----  File: gfortran.info, Node: ITIME, Next: KILL, Prev: ISNAN, Up: Intrinsic Procedures ! 9.153 `ITIME' -- Get current local time subroutine (hour/minutes/seconds) ========================================================================= _Description_: ! `IDATE(VALUES)' Fills VALUES with the numerical values at the ! current local time. The hour (in the range 1-24), minute (in the range 1-60), and seconds (in the range 1-60) appear in elements 1, 2, and 3 of VALUES, respectively. *************** _Class_: *** 12444,12454 **** Subroutine _Syntax_: ! 'CALL ITIME(VALUES)' _Arguments_: ! VALUES The type shall be 'INTEGER, DIMENSION(3)' and ! the kind shall be the default integer kind. _Return value_: Does not return anything. --- 12564,12574 ---- Subroutine _Syntax_: ! `CALL ITIME(VALUES)' _Arguments_: ! VALUES The type shall be `INTEGER, DIMENSION(3)' and ! the kind shall be the default integer kind. _Return value_: Does not return anything. *************** _Example_: *** 12465,12477 ****  File: gfortran.info, Node: KILL, Next: KIND, Prev: ITIME, Up: Intrinsic Procedures ! 9.154 'KILL' -- Send a signal to a process ========================================== _Description_: _Standard_: Sends the signal specified by SIGNAL to the process PID. See ! 'kill(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 12585,12598 ----  File: gfortran.info, Node: KILL, Next: KIND, Prev: ITIME, Up: Intrinsic Procedures ! 9.154 `KILL' -- Send a signal to a process ========================================== _Description_: + _Standard_: Sends the signal specified by SIGNAL to the process PID. See ! `kill(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 12480,12494 **** Subroutine, function _Syntax_: ! 'CALL KILL(C, VALUE [, STATUS])' ! 'STATUS = KILL(C, VALUE)' _Arguments_: ! C Shall be a scalar 'INTEGER', with 'INTENT(IN)' ! VALUE Shall be a scalar 'INTEGER', with 'INTENT(IN)' ! STATUS (Optional) status flag of type 'INTEGER(4)' or ! 'INTEGER(8)'. Returns 0 on success, or a ! system-specific error code otherwise. _See also_: *note ABORT::, *note EXIT:: --- 12601,12615 ---- Subroutine, function _Syntax_: ! `CALL KILL(C, VALUE [, STATUS])' ! `STATUS = KILL(C, VALUE)' _Arguments_: ! C Shall be a scalar `INTEGER', with `INTENT(IN)' ! VALUE Shall be a scalar `INTEGER', with `INTENT(IN)' ! STATUS (Optional) status flag of type `INTEGER(4)' or ! `INTEGER(8)'. Returns 0 on success, or a ! system-specific error code otherwise. _See also_: *note ABORT::, *note EXIT:: *************** _See also_: *** 12496,12506 ****  File: gfortran.info, Node: KIND, Next: LBOUND, Prev: KILL, Up: Intrinsic Procedures ! 9.155 'KIND' -- Kind of an entity ================================= _Description_: ! 'KIND(X)' returns the kind value of the entity X. _Standard_: Fortran 95 and later --- 12617,12627 ----  File: gfortran.info, Node: KIND, Next: LBOUND, Prev: KILL, Up: Intrinsic Procedures ! 9.155 `KIND' -- Kind of an entity ================================= _Description_: ! `KIND(X)' returns the kind value of the entity X. _Standard_: Fortran 95 and later *************** _Class_: *** 12509,12522 **** Inquiry function _Syntax_: ! 'K = KIND(X)' _Arguments_: ! X Shall be of type 'LOGICAL', 'INTEGER', 'REAL', ! 'COMPLEX' or 'CHARACTER'. _Return value_: ! The return value is a scalar of type 'INTEGER' and of the default integer kind. _Example_: --- 12630,12643 ---- Inquiry function _Syntax_: ! `K = KIND(X)' _Arguments_: ! X Shall be of type `LOGICAL', `INTEGER', `REAL', ! `COMPLEX' or `CHARACTER'. _Return value_: ! The return value is a scalar of type `INTEGER' and of the default integer kind. _Example_: *************** _Example_: *** 12528,12542 **** print *, "The default logical kind is ", kl end program test_kind  File: gfortran.info, Node: LBOUND, Next: LCOBOUND, Prev: KIND, Up: Intrinsic Procedures ! 9.156 'LBOUND' -- Lower dimension bounds of an array ==================================================== _Description_: ! Returns the lower bounds of an array, or a single lower bound along ! the DIM dimension. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later --- 12649,12665 ---- print *, "The default logical kind is ", kl end program test_kind +  File: gfortran.info, Node: LBOUND, Next: LCOBOUND, Prev: KIND, Up: Intrinsic Procedures ! 9.156 `LBOUND' -- Lower dimension bounds of an array ==================================================== _Description_: ! Returns the lower bounds of an array, or a single lower bound ! along the DIM dimension. ! _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later *************** _Class_: *** 12544,12567 **** Inquiry function _Syntax_: ! 'RESULT = LBOUND(ARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an array, of any type. ! DIM (Optional) Shall be a scalar 'INTEGER'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the lower bounds of ARRAY. If DIM is present, the result is a scalar corresponding to the lower ! bound of the array along that dimension. If ARRAY is an expression ! rather than a whole array or array structure component, or if it ! has a zero extent along the relevant dimension, the lower bound is ! taken to be 1. _See also_: *note UBOUND::, *note LCOBOUND:: --- 12667,12690 ---- Inquiry function _Syntax_: ! `RESULT = LBOUND(ARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an array, of any type. ! DIM (Optional) Shall be a scalar `INTEGER'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the lower bounds of ARRAY. If DIM is present, the result is a scalar corresponding to the lower ! bound of the array along that dimension. If ARRAY is an ! expression rather than a whole array or array structure component, ! or if it has a zero extent along the relevant dimension, the lower ! bound is taken to be 1. _See also_: *note UBOUND::, *note LCOBOUND:: *************** _See also_: *** 12569,12580 ****  File: gfortran.info, Node: LCOBOUND, Next: LEADZ, Prev: LBOUND, Up: Intrinsic Procedures ! 9.157 'LCOBOUND' -- Lower codimension bounds of an array ======================================================== _Description_: Returns the lower bounds of a coarray, or a single lower cobound along the DIM codimension. _Standard_: Fortran 2008 and later --- 12692,12704 ----  File: gfortran.info, Node: LCOBOUND, Next: LEADZ, Prev: LBOUND, Up: Intrinsic Procedures ! 9.157 `LCOBOUND' -- Lower codimension bounds of an array ======================================================== _Description_: Returns the lower bounds of a coarray, or a single lower cobound along the DIM codimension. + _Standard_: Fortran 2008 and later *************** _Class_: *** 12582,12598 **** Inquiry function _Syntax_: ! 'RESULT = LCOBOUND(COARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an coarray, of any type. ! DIM (Optional) Shall be a scalar 'INTEGER'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the lower cobounds of COARRAY. If DIM is present, the result is a scalar corresponding to the --- 12706,12722 ---- Inquiry function _Syntax_: ! `RESULT = LCOBOUND(COARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an coarray, of any type. ! DIM (Optional) Shall be a scalar `INTEGER'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the lower cobounds of COARRAY. If DIM is present, the result is a scalar corresponding to the *************** _See also_: *** 12604,12614 ****  File: gfortran.info, Node: LEADZ, Next: LEN, Prev: LCOBOUND, Up: Intrinsic Procedures ! 9.158 'LEADZ' -- Number of leading zero bits of an integer ========================================================== _Description_: ! 'LEADZ' returns the number of leading zero bits of an integer. _Standard_: Fortran 2008 and later --- 12728,12738 ----  File: gfortran.info, Node: LEADZ, Next: LEN, Prev: LCOBOUND, Up: Intrinsic Procedures ! 9.158 `LEADZ' -- Number of leading zero bits of an integer ========================================================== _Description_: ! `LEADZ' returns the number of leading zero bits of an integer. _Standard_: Fortran 2008 and later *************** _Class_: *** 12617,12630 **** Elemental function _Syntax_: ! 'RESULT = LEADZ(I)' _Arguments_: ! I Shall be of type 'INTEGER'. _Return value_: ! The type of the return value is the default 'INTEGER'. If all the ! bits of 'I' are zero, the result value is 'BIT_SIZE(I)'. _Example_: PROGRAM test_leadz --- 12741,12754 ---- Elemental function _Syntax_: ! `RESULT = LEADZ(I)' _Arguments_: ! I Shall be of type `INTEGER'. _Return value_: ! The type of the return value is the default `INTEGER'. If all the ! bits of `I' are zero, the result value is `BIT_SIZE(I)'. _Example_: PROGRAM test_leadz *************** _See also_: *** 12638,12644 ****  File: gfortran.info, Node: LEN, Next: LEN_TRIM, Prev: LEADZ, Up: Intrinsic Procedures ! 9.159 'LEN' -- Length of a character entity =========================================== _Description_: --- 12762,12768 ----  File: gfortran.info, Node: LEN, Next: LEN_TRIM, Prev: LEADZ, Up: Intrinsic Procedures ! 9.159 `LEN' -- Length of a character entity =========================================== _Description_: *************** _Class_: *** 12654,12676 **** Inquiry function _Syntax_: ! 'L = LEN(STRING [, KIND])' _Arguments_: ! STRING Shall be a scalar or array of type 'CHARACTER', ! with 'INTENT(IN)' ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Specific names_: ! Name Argument Return type Standard ! 'LEN(STRING)' 'CHARACTER' 'INTEGER' Fortran 77 and ! later _See also_: *note LEN_TRIM::, *note ADJUSTL::, *note ADJUSTR:: --- 12778,12800 ---- Inquiry function _Syntax_: ! `L = LEN(STRING [, KIND])' _Arguments_: ! STRING Shall be a scalar or array of type ! `CHARACTER', with `INTENT(IN)' ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Specific names_: ! Name Argument Return type Standard ! `LEN(STRING)' `CHARACTER' `INTEGER' Fortran 77 and ! later _See also_: *note LEN_TRIM::, *note ADJUSTL::, *note ADJUSTR:: *************** _See also_: *** 12678,12684 ****  File: gfortran.info, Node: LEN_TRIM, Next: LGE, Prev: LEN, Up: Intrinsic Procedures ! 9.160 'LEN_TRIM' -- Length of a character entity without trailing blank characters ================================================================================== _Description_: --- 12802,12808 ----  File: gfortran.info, Node: LEN_TRIM, Next: LGE, Prev: LEN, Up: Intrinsic Procedures ! 9.160 `LEN_TRIM' -- Length of a character entity without trailing blank characters ================================================================================== _Description_: *************** _Class_: *** 12692,12708 **** Elemental function _Syntax_: ! 'RESULT = LEN_TRIM(STRING [, KIND])' _Arguments_: ! STRING Shall be a scalar of type 'CHARACTER', with ! 'INTENT(IN)' ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _See also_: --- 12816,12832 ---- Elemental function _Syntax_: ! `RESULT = LEN_TRIM(STRING [, KIND])' _Arguments_: ! STRING Shall be a scalar of type `CHARACTER', with ! `INTENT(IN)' ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _See also_: *************** _See also_: *** 12711,12717 ****  File: gfortran.info, Node: LGE, Next: LGT, Prev: LEN_TRIM, Up: Intrinsic Procedures ! 9.161 'LGE' -- Lexical greater than or equal ============================================ _Description_: --- 12835,12841 ----  File: gfortran.info, Node: LGE, Next: LGT, Prev: LEN_TRIM, Up: Intrinsic Procedures ! 9.161 `LGE' -- Lexical greater than or equal ============================================ _Description_: *************** _Description_: *** 12721,12731 **** same length, the shorter is compared as if spaces were appended to it to form a value that has the same length as the longer. ! In general, the lexical comparison intrinsics 'LGE', 'LGT', 'LLE', ! and 'LLT' differ from the corresponding intrinsic operators '.GE.', ! '.GT.', '.LE.', and '.LT.', in that the latter use the processor's ! character ordering (which is not ASCII on some targets), whereas ! the former always use the ASCII ordering. _Standard_: Fortran 77 and later --- 12845,12855 ---- same length, the shorter is compared as if spaces were appended to it to form a value that has the same length as the longer. ! In general, the lexical comparison intrinsics `LGE', `LGT', `LLE', ! and `LLT' differ from the corresponding intrinsic operators ! `.GE.', `.GT.', `.LE.', and `.LT.', in that the latter use the ! processor's character ordering (which is not ASCII on some ! targets), whereas the former always use the ASCII ordering. _Standard_: Fortran 77 and later *************** _Class_: *** 12734,12753 **** Elemental function _Syntax_: ! 'RESULT = LGE(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default 'CHARACTER' type. ! STRING_B Shall be of default 'CHARACTER' type. _Return value_: ! Returns '.TRUE.' if 'STRING_A >= STRING_B', and '.FALSE.' otherwise, based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! 'LGE(STRING_A, 'CHARACTER' 'LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGT::, *note LLE::, *note LLT:: --- 12858,12877 ---- Elemental function _Syntax_: ! `RESULT = LGE(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default `CHARACTER' type. ! STRING_B Shall be of default `CHARACTER' type. _Return value_: ! Returns `.TRUE.' if `STRING_A >= STRING_B', and `.FALSE.' otherwise, based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! `LGE(STRING_A,`CHARACTER' `LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGT::, *note LLE::, *note LLT:: *************** _See also_: *** 12755,12775 ****  File: gfortran.info, Node: LGT, Next: LINK, Prev: LGE, Up: Intrinsic Procedures ! 9.162 'LGT' -- Lexical greater than =================================== _Description_: Determines whether one string is lexically greater than another string, where the two strings are interpreted as containing ASCII character codes. If the String A and String B are not the same ! length, the shorter is compared as if spaces were appended to it to ! form a value that has the same length as the longer. ! In general, the lexical comparison intrinsics 'LGE', 'LGT', 'LLE', ! and 'LLT' differ from the corresponding intrinsic operators '.GE.', ! '.GT.', '.LE.', and '.LT.', in that the latter use the processor's ! character ordering (which is not ASCII on some targets), whereas ! the former always use the ASCII ordering. _Standard_: Fortran 77 and later --- 12879,12899 ----  File: gfortran.info, Node: LGT, Next: LINK, Prev: LGE, Up: Intrinsic Procedures ! 9.162 `LGT' -- Lexical greater than =================================== _Description_: Determines whether one string is lexically greater than another string, where the two strings are interpreted as containing ASCII character codes. If the String A and String B are not the same ! length, the shorter is compared as if spaces were appended to it ! to form a value that has the same length as the longer. ! In general, the lexical comparison intrinsics `LGE', `LGT', `LLE', ! and `LLT' differ from the corresponding intrinsic operators ! `.GE.', `.GT.', `.LE.', and `.LT.', in that the latter use the ! processor's character ordering (which is not ASCII on some ! targets), whereas the former always use the ASCII ordering. _Standard_: Fortran 77 and later *************** _Class_: *** 12778,12797 **** Elemental function _Syntax_: ! 'RESULT = LGT(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default 'CHARACTER' type. ! STRING_B Shall be of default 'CHARACTER' type. _Return value_: ! Returns '.TRUE.' if 'STRING_A > STRING_B', and '.FALSE.' otherwise, ! based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! 'LGT(STRING_A, 'CHARACTER' 'LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGE::, *note LLE::, *note LLT:: --- 12902,12921 ---- Elemental function _Syntax_: ! `RESULT = LGT(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default `CHARACTER' type. ! STRING_B Shall be of default `CHARACTER' type. _Return value_: ! Returns `.TRUE.' if `STRING_A > STRING_B', and `.FALSE.' ! otherwise, based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! `LGT(STRING_A,`CHARACTER' `LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGE::, *note LLE::, *note LLT:: *************** _See also_: *** 12799,12813 ****  File: gfortran.info, Node: LINK, Next: LLE, Prev: LGT, Up: Intrinsic Procedures ! 9.163 'LINK' -- Create a hard link ================================== _Description_: ! Makes a (hard) link from file PATH1 to PATH2. A null character ! ('CHAR(0)') can be used to mark the end of the names in PATH1 and PATH2; otherwise, trailing blanks in the file names are ignored. If the STATUS argument is supplied, it contains 0 on success or a ! nonzero error code upon return; see 'link(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 12923,12937 ----  File: gfortran.info, Node: LINK, Next: LLE, Prev: LGT, Up: Intrinsic Procedures ! 9.163 `LINK' -- Create a hard link ================================== _Description_: ! Makes a (hard) link from file PATH1 to PATH2. A null character ! (`CHAR(0)') can be used to mark the end of the names in PATH1 and PATH2; otherwise, trailing blanks in the file names are ignored. If the STATUS argument is supplied, it contains 0 on success or a ! nonzero error code upon return; see `link(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 12819,12831 **** Subroutine, function _Syntax_: ! 'CALL LINK(PATH1, PATH2 [, STATUS])' ! 'STATUS = LINK(PATH1, PATH2)' _Arguments_: ! PATH1 Shall be of default 'CHARACTER' type. ! PATH2 Shall be of default 'CHARACTER' type. ! STATUS (Optional) Shall be of default 'INTEGER' type. _See also_: *note SYMLNK::, *note UNLINK:: --- 12943,12955 ---- Subroutine, function _Syntax_: ! `CALL LINK(PATH1, PATH2 [, STATUS])' ! `STATUS = LINK(PATH1, PATH2)' _Arguments_: ! PATH1 Shall be of default `CHARACTER' type. ! PATH2 Shall be of default `CHARACTER' type. ! STATUS (Optional) Shall be of default `INTEGER' type. _See also_: *note SYMLNK::, *note UNLINK:: *************** _See also_: *** 12833,12853 ****  File: gfortran.info, Node: LLE, Next: LLT, Prev: LINK, Up: Intrinsic Procedures ! 9.164 'LLE' -- Lexical less than or equal ========================================= _Description_: Determines whether one string is lexically less than or equal to ! another string, where the two strings are interpreted as containing ! ASCII character codes. If the String A and String B are not the ! same length, the shorter is compared as if spaces were appended to ! it to form a value that has the same length as the longer. ! In general, the lexical comparison intrinsics 'LGE', 'LGT', 'LLE', ! and 'LLT' differ from the corresponding intrinsic operators '.GE.', ! '.GT.', '.LE.', and '.LT.', in that the latter use the processor's ! character ordering (which is not ASCII on some targets), whereas ! the former always use the ASCII ordering. _Standard_: Fortran 77 and later --- 12957,12978 ----  File: gfortran.info, Node: LLE, Next: LLT, Prev: LINK, Up: Intrinsic Procedures ! 9.164 `LLE' -- Lexical less than or equal ========================================= _Description_: Determines whether one string is lexically less than or equal to ! another string, where the two strings are interpreted as ! containing ASCII character codes. If the String A and String B ! are not the same length, the shorter is compared as if spaces were ! appended to it to form a value that has the same length as the ! longer. ! In general, the lexical comparison intrinsics `LGE', `LGT', `LLE', ! and `LLT' differ from the corresponding intrinsic operators ! `.GE.', `.GT.', `.LE.', and `.LT.', in that the latter use the ! processor's character ordering (which is not ASCII on some ! targets), whereas the former always use the ASCII ordering. _Standard_: Fortran 77 and later *************** _Class_: *** 12856,12875 **** Elemental function _Syntax_: ! 'RESULT = LLE(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default 'CHARACTER' type. ! STRING_B Shall be of default 'CHARACTER' type. _Return value_: ! Returns '.TRUE.' if 'STRING_A <= STRING_B', and '.FALSE.' otherwise, based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! 'LLE(STRING_A, 'CHARACTER' 'LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGE::, *note LGT::, *note LLT:: --- 12981,13000 ---- Elemental function _Syntax_: ! `RESULT = LLE(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default `CHARACTER' type. ! STRING_B Shall be of default `CHARACTER' type. _Return value_: ! Returns `.TRUE.' if `STRING_A <= STRING_B', and `.FALSE.' otherwise, based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! `LLE(STRING_A,`CHARACTER' `LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGE::, *note LGT::, *note LLT:: *************** _See also_: *** 12877,12897 ****  File: gfortran.info, Node: LLT, Next: LNBLNK, Prev: LLE, Up: Intrinsic Procedures ! 9.165 'LLT' -- Lexical less than ================================ _Description_: Determines whether one string is lexically less than another string, where the two strings are interpreted as containing ASCII character codes. If the String A and String B are not the same ! length, the shorter is compared as if spaces were appended to it to ! form a value that has the same length as the longer. ! In general, the lexical comparison intrinsics 'LGE', 'LGT', 'LLE', ! and 'LLT' differ from the corresponding intrinsic operators '.GE.', ! '.GT.', '.LE.', and '.LT.', in that the latter use the processor's ! character ordering (which is not ASCII on some targets), whereas ! the former always use the ASCII ordering. _Standard_: Fortran 77 and later --- 13002,13022 ----  File: gfortran.info, Node: LLT, Next: LNBLNK, Prev: LLE, Up: Intrinsic Procedures ! 9.165 `LLT' -- Lexical less than ================================ _Description_: Determines whether one string is lexically less than another string, where the two strings are interpreted as containing ASCII character codes. If the String A and String B are not the same ! length, the shorter is compared as if spaces were appended to it ! to form a value that has the same length as the longer. ! In general, the lexical comparison intrinsics `LGE', `LGT', `LLE', ! and `LLT' differ from the corresponding intrinsic operators ! `.GE.', `.GT.', `.LE.', and `.LT.', in that the latter use the ! processor's character ordering (which is not ASCII on some ! targets), whereas the former always use the ASCII ordering. _Standard_: Fortran 77 and later *************** _Class_: *** 12900,12919 **** Elemental function _Syntax_: ! 'RESULT = LLT(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default 'CHARACTER' type. ! STRING_B Shall be of default 'CHARACTER' type. _Return value_: ! Returns '.TRUE.' if 'STRING_A < STRING_B', and '.FALSE.' otherwise, ! based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! 'LLT(STRING_A, 'CHARACTER' 'LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGE::, *note LGT::, *note LLE:: --- 13025,13044 ---- Elemental function _Syntax_: ! `RESULT = LLT(STRING_A, STRING_B)' _Arguments_: ! STRING_A Shall be of default `CHARACTER' type. ! STRING_B Shall be of default `CHARACTER' type. _Return value_: ! Returns `.TRUE.' if `STRING_A < STRING_B', and `.FALSE.' ! otherwise, based on the ASCII ordering. _Specific names_: ! Name Argument Return type Standard ! `LLT(STRING_A,`CHARACTER' `LOGICAL' Fortran 77 and ! STRING_B)' later _See also_: *note LGE::, *note LGT::, *note LLE:: *************** _See also_: *** 12921,12932 ****  File: gfortran.info, Node: LNBLNK, Next: LOC, Prev: LLT, Up: Intrinsic Procedures ! 9.166 'LNBLNK' -- Index of the last non-blank character in a string =================================================================== _Description_: Returns the length of a character string, ignoring any trailing ! blanks. This is identical to the standard 'LEN_TRIM' intrinsic, and is only included for backwards compatibility. _Standard_: --- 13046,13057 ----  File: gfortran.info, Node: LNBLNK, Next: LOC, Prev: LLT, Up: Intrinsic Procedures ! 9.166 `LNBLNK' -- Index of the last non-blank character in a string =================================================================== _Description_: Returns the length of a character string, ignoring any trailing ! blanks. This is identical to the standard `LEN_TRIM' intrinsic, and is only included for backwards compatibility. _Standard_: *************** _Class_: *** 12936,12949 **** Elemental function _Syntax_: ! 'RESULT = LNBLNK(STRING)' _Arguments_: ! STRING Shall be a scalar of type 'CHARACTER', with ! 'INTENT(IN)' _Return value_: ! The return value is of 'INTEGER(kind=4)' type. _See also_: *note INDEX intrinsic::, *note LEN_TRIM:: --- 13061,13074 ---- Elemental function _Syntax_: ! `RESULT = LNBLNK(STRING)' _Arguments_: ! STRING Shall be a scalar of type `CHARACTER', with ! `INTENT(IN)' _Return value_: ! The return value is of `INTEGER(kind=4)' type. _See also_: *note INDEX intrinsic::, *note LEN_TRIM:: *************** _See also_: *** 12951,12961 ****  File: gfortran.info, Node: LOC, Next: LOG, Prev: LNBLNK, Up: Intrinsic Procedures ! 9.167 'LOC' -- Returns the address of a variable ================================================ _Description_: ! 'LOC(X)' returns the address of X as an integer. _Standard_: GNU extension --- 13076,13086 ----  File: gfortran.info, Node: LOC, Next: LOG, Prev: LNBLNK, Up: Intrinsic Procedures ! 9.167 `LOC' -- Returns the address of a variable ================================================ _Description_: ! `LOC(X)' returns the address of X as an integer. _Standard_: GNU extension *************** _Class_: *** 12964,12976 **** Inquiry function _Syntax_: ! 'RESULT = LOC(X)' _Arguments_: ! X Variable of any type. _Return value_: ! The return value is of type 'INTEGER', with a 'KIND' corresponding to the size (in bytes) of a memory address on the target machine. _Example_: --- 13089,13101 ---- Inquiry function _Syntax_: ! `RESULT = LOC(X)' _Arguments_: ! X Variable of any type. _Return value_: ! The return value is of type `INTEGER', with a `KIND' corresponding to the size (in bytes) of a memory address on the target machine. _Example_: *************** _Example_: *** 12984,12994 ****  File: gfortran.info, Node: LOG, Next: LOG10, Prev: LOC, Up: Intrinsic Procedures ! 9.168 'LOG' -- Natural logarithm function ========================================= _Description_: ! 'LOG(X)' computes the natural logarithm of X, i.e. the logarithm to the base e. _Standard_: --- 13109,13119 ----  File: gfortran.info, Node: LOG, Next: LOG10, Prev: LOC, Up: Intrinsic Procedures ! 9.168 `LOG' -- Natural logarithm function ========================================= _Description_: ! `LOG(X)' computes the natural logarithm of X, i.e. the logarithm to the base e. _Standard_: *************** _Class_: *** 12998,13011 **** Elemental function _Syntax_: ! 'RESULT = LOG(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value is of type 'REAL' or 'COMPLEX'. The kind type ! parameter is the same as X. If X is 'COMPLEX', the imaginary part \omega is in the range -\pi < \omega \leq \pi. _Example_: --- 13123,13136 ---- Elemental function _Syntax_: ! `RESULT = LOG(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value is of type `REAL' or `COMPLEX'. The kind type ! parameter is the same as X. If X is `COMPLEX', the imaginary part \omega is in the range -\pi < \omega \leq \pi. _Example_: *************** _Example_: *** 13017,13040 **** end program test_log _Specific names_: ! Name Argument Return type Standard ! 'ALOG(X)' 'REAL(4) X' 'REAL(4)' f95, gnu ! 'DLOG(X)' 'REAL(8) X' 'REAL(8)' f95, gnu ! 'CLOG(X)' 'COMPLEX(4) 'COMPLEX(4)' f95, gnu ! X' ! 'ZLOG(X)' 'COMPLEX(8) 'COMPLEX(8)' f95, gnu ! X' ! 'CDLOG(X)' 'COMPLEX(8) 'COMPLEX(8)' f95, gnu ! X'  File: gfortran.info, Node: LOG10, Next: LOG_GAMMA, Prev: LOG, Up: Intrinsic Procedures ! 9.169 'LOG10' -- Base 10 logarithm function =========================================== _Description_: ! 'LOG10(X)' computes the base 10 logarithm of X. _Standard_: Fortran 77 and later --- 13142,13165 ---- end program test_log _Specific names_: ! Name Argument Return type Standard ! `ALOG(X)' `REAL(4) X' `REAL(4)' f95, gnu ! `DLOG(X)' `REAL(8) X' `REAL(8)' f95, gnu ! `CLOG(X)' `COMPLEX(4) `COMPLEX(4)' f95, gnu ! X' ! `ZLOG(X)' `COMPLEX(8) `COMPLEX(8)' f95, gnu ! X' ! `CDLOG(X)' `COMPLEX(8) `COMPLEX(8)' f95, gnu ! X'  File: gfortran.info, Node: LOG10, Next: LOG_GAMMA, Prev: LOG, Up: Intrinsic Procedures ! 9.169 `LOG10' -- Base 10 logarithm function =========================================== _Description_: ! `LOG10(X)' computes the base 10 logarithm of X. _Standard_: Fortran 77 and later *************** _Class_: *** 13043,13055 **** Elemental function _Syntax_: ! 'RESULT = LOG10(X)' _Arguments_: ! X The type shall be 'REAL'. _Return value_: ! The return value is of type 'REAL' or 'COMPLEX'. The kind type parameter is the same as X. _Example_: --- 13168,13180 ---- Elemental function _Syntax_: ! `RESULT = LOG10(X)' _Arguments_: ! X The type shall be `REAL'. _Return value_: ! The return value is of type `REAL' or `COMPLEX'. The kind type parameter is the same as X. _Example_: *************** _Example_: *** 13059,13078 **** end program test_log10 _Specific names_: ! Name Argument Return type Standard ! 'ALOG10(X)' 'REAL(4) X' 'REAL(4)' Fortran 95 and ! later ! 'DLOG10(X)' 'REAL(8) X' 'REAL(8)' Fortran 95 and ! later  File: gfortran.info, Node: LOG_GAMMA, Next: LOGICAL, Prev: LOG10, Up: Intrinsic Procedures ! 9.170 'LOG_GAMMA' -- Logarithm of the Gamma function ==================================================== _Description_: ! 'LOG_GAMMA(X)' computes the natural logarithm of the absolute value of the Gamma (\Gamma) function. _Standard_: --- 13184,13203 ---- end program test_log10 _Specific names_: ! Name Argument Return type Standard ! `ALOG10(X)' `REAL(4) X' `REAL(4)' Fortran 95 and ! later ! `DLOG10(X)' `REAL(8) X' `REAL(8)' Fortran 95 and ! later  File: gfortran.info, Node: LOG_GAMMA, Next: LOGICAL, Prev: LOG10, Up: Intrinsic Procedures ! 9.170 `LOG_GAMMA' -- Logarithm of the Gamma function ==================================================== _Description_: ! `LOG_GAMMA(X)' computes the natural logarithm of the absolute value of the Gamma (\Gamma) function. _Standard_: *************** _Class_: *** 13082,13095 **** Elemental function _Syntax_: ! 'X = LOG_GAMMA(X)' _Arguments_: ! X Shall be of type 'REAL' and neither zero nor a ! negative integer. _Return value_: ! The return value is of type 'REAL' of the same kind as X. _Example_: program test_log_gamma --- 13207,13220 ---- Elemental function _Syntax_: ! `X = LOG_GAMMA(X)' _Arguments_: ! X Shall be of type `REAL' and neither zero nor a ! negative integer. _Return value_: ! The return value is of type `REAL' of the same kind as X. _Example_: program test_log_gamma *************** _Example_: *** 13098,13119 **** end program test_log_gamma _Specific names_: ! Name Argument Return type Standard ! 'LGAMMA(X)' 'REAL(4) X' 'REAL(4)' GNU Extension ! 'ALGAMA(X)' 'REAL(4) X' 'REAL(4)' GNU Extension ! 'DLGAMA(X)' 'REAL(8) X' 'REAL(8)' GNU Extension _See also_: Gamma function: *note GAMMA::  File: gfortran.info, Node: LOGICAL, Next: LONG, Prev: LOG_GAMMA, Up: Intrinsic Procedures ! 9.171 'LOGICAL' -- Convert to logical type ========================================== _Description_: ! Converts one kind of 'LOGICAL' variable to another. _Standard_: Fortran 95 and later --- 13223,13245 ---- end program test_log_gamma _Specific names_: ! Name Argument Return type Standard ! `LGAMMA(X)' `REAL(4) X' `REAL(4)' GNU Extension ! `ALGAMA(X)' `REAL(4) X' `REAL(4)' GNU Extension ! `DLGAMA(X)' `REAL(8) X' `REAL(8)' GNU Extension _See also_: Gamma function: *note GAMMA:: +  File: gfortran.info, Node: LOGICAL, Next: LONG, Prev: LOG_GAMMA, Up: Intrinsic Procedures ! 9.171 `LOGICAL' -- Convert to logical type ========================================== _Description_: ! Converts one kind of `LOGICAL' variable to another. _Standard_: Fortran 95 and later *************** _Class_: *** 13122,13137 **** Elemental function _Syntax_: ! 'RESULT = LOGICAL(L [, KIND])' _Arguments_: ! L The type shall be 'LOGICAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is a 'LOGICAL' value equal to L, with a kind corresponding to KIND, or of the default logical kind if KIND is not given. --- 13248,13263 ---- Elemental function _Syntax_: ! `RESULT = LOGICAL(L [, KIND])' _Arguments_: ! L The type shall be `LOGICAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is a `LOGICAL' value equal to L, with a kind corresponding to KIND, or of the default logical kind if KIND is not given. *************** _See also_: *** 13141,13154 ****  File: gfortran.info, Node: LONG, Next: LSHIFT, Prev: LOGICAL, Up: Intrinsic Procedures ! 9.172 'LONG' -- Convert to integer type ======================================= _Description_: ! Convert to a 'KIND=4' integer type, which is the same size as a C ! 'long' integer. This is equivalent to the standard 'INT' intrinsic ! with an optional argument of 'KIND=4', and is only included for ! backwards compatibility. _Standard_: GNU extension --- 13267,13280 ----  File: gfortran.info, Node: LONG, Next: LSHIFT, Prev: LOGICAL, Up: Intrinsic Procedures ! 9.172 `LONG' -- Convert to integer type ======================================= _Description_: ! Convert to a `KIND=4' integer type, which is the same size as a C ! `long' integer. This is equivalent to the standard `INT' ! intrinsic with an optional argument of `KIND=4', and is only ! included for backwards compatibility. _Standard_: GNU extension *************** _Class_: *** 13157,13170 **** Elemental function _Syntax_: ! 'RESULT = LONG(A)' _Arguments_: ! A Shall be of type 'INTEGER', 'REAL', or ! 'COMPLEX'. _Return value_: ! The return value is a 'INTEGER(4)' variable. _See also_: *note INT::, *note INT2::, *note INT8:: --- 13283,13296 ---- Elemental function _Syntax_: ! `RESULT = LONG(A)' _Arguments_: ! A Shall be of type `INTEGER', `REAL', or ! `COMPLEX'. _Return value_: ! The return value is a `INTEGER(4)' variable. _See also_: *note INT::, *note INT2::, *note INT8:: *************** _See also_: *** 13172,13189 ****  File: gfortran.info, Node: LSHIFT, Next: LSTAT, Prev: LONG, Up: Intrinsic Procedures ! 9.173 'LSHIFT' -- Left shift bits ================================= _Description_: ! 'LSHIFT' returns a value corresponding to I with all of the bits shifted left by SHIFT places. If the absolute value of SHIFT is ! greater than 'BIT_SIZE(I)', the value is undefined. Bits shifted out from the left end are lost; zeros are shifted in from the opposite end. ! This function has been superseded by the 'ISHFT' intrinsic, which ! is standard in Fortran 95 and later, and the 'SHIFTL' intrinsic, which is standard in Fortran 2008 and later. _Standard_: --- 13298,13315 ----  File: gfortran.info, Node: LSHIFT, Next: LSTAT, Prev: LONG, Up: Intrinsic Procedures ! 9.173 `LSHIFT' -- Left shift bits ================================= _Description_: ! `LSHIFT' returns a value corresponding to I with all of the bits shifted left by SHIFT places. If the absolute value of SHIFT is ! greater than `BIT_SIZE(I)', the value is undefined. Bits shifted out from the left end are lost; zeros are shifted in from the opposite end. ! This function has been superseded by the `ISHFT' intrinsic, which ! is standard in Fortran 95 and later, and the `SHIFTL' intrinsic, which is standard in Fortran 2008 and later. _Standard_: *************** _Class_: *** 13193,13223 **** Elemental function _Syntax_: ! 'RESULT = LSHIFT(I, SHIFT)' _Arguments_: ! I The type shall be 'INTEGER'. ! SHIFT The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note ISHFT::, *note ISHFTC::, *note RSHIFT::, *note SHIFTA::, *note SHIFTL::, *note SHIFTR::  File: gfortran.info, Node: LSTAT, Next: LTIME, Prev: LSHIFT, Up: Intrinsic Procedures ! 9.174 'LSTAT' -- Get file status ================================ _Description_: ! 'LSTAT' is identical to *note STAT::, except that if path is a symbolic link, then the link itself is statted, not the file that it refers to. ! The elements in 'VALUES' are the same as described by *note STAT::. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 13319,13350 ---- Elemental function _Syntax_: ! `RESULT = LSHIFT(I, SHIFT)' _Arguments_: ! I The type shall be `INTEGER'. ! SHIFT The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note ISHFT::, *note ISHFTC::, *note RSHIFT::, *note SHIFTA::, *note SHIFTL::, *note SHIFTR:: +  File: gfortran.info, Node: LSTAT, Next: LTIME, Prev: LSHIFT, Up: Intrinsic Procedures ! 9.174 `LSTAT' -- Get file status ================================ _Description_: ! `LSTAT' is identical to *note STAT::, except that if path is a symbolic link, then the link itself is statted, not the file that it refers to. ! The elements in `VALUES' are the same as described by *note STAT::. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 13229,13244 **** Subroutine, function _Syntax_: ! 'CALL LSTAT(NAME, VALUES [, STATUS])' ! 'STATUS = LSTAT(NAME, VALUES)' _Arguments_: ! NAME The type shall be 'CHARACTER' of the default ! kind, a valid path within the file system. ! VALUES The type shall be 'INTEGER(4), DIMENSION(13)'. ! STATUS (Optional) status flag of type 'INTEGER(4)'. ! Returns 0 on success and a system specific error ! code otherwise. _Example_: See *note STAT:: for an example. --- 13356,13371 ---- Subroutine, function _Syntax_: ! `CALL LSTAT(NAME, VALUES [, STATUS])' ! `STATUS = LSTAT(NAME, VALUES)' _Arguments_: ! NAME The type shall be `CHARACTER' of the default ! kind, a valid path within the file system. ! VALUES The type shall be `INTEGER(4), DIMENSION(13)'. ! STATUS (Optional) status flag of type `INTEGER(4)'. ! Returns 0 on success and a system specific ! error code otherwise. _Example_: See *note STAT:: for an example. *************** _See also_: *** 13249,13261 ****  File: gfortran.info, Node: LTIME, Next: MALLOC, Prev: LSTAT, Up: Intrinsic Procedures ! 9.175 'LTIME' -- Convert time to local time info ================================================ _Description_: ! Given a system time value TIME (as provided by the 'TIME8' intrinsic), fills VALUES with values extracted from it appropriate ! to the local time zone using 'localtime(3)'. _Standard_: GNU extension --- 13376,13388 ----  File: gfortran.info, Node: LTIME, Next: MALLOC, Prev: LSTAT, Up: Intrinsic Procedures ! 9.175 `LTIME' -- Convert time to local time info ================================================ _Description_: ! Given a system time value TIME (as provided by the `TIME8' intrinsic), fills VALUES with values extracted from it appropriate ! to the local time zone using `localtime(3)'. _Standard_: GNU extension *************** _Class_: *** 13264,13288 **** Subroutine _Syntax_: ! 'CALL LTIME(TIME, VALUES)' _Arguments_: ! TIME An 'INTEGER' scalar expression corresponding to ! a system time, with 'INTENT(IN)'. ! VALUES A default 'INTEGER' array with 9 elements, with ! 'INTENT(OUT)'. _Return value_: The elements of VALUES are assigned as follows: 1. Seconds after the minute, range 0-59 or 0-61 to allow for leap seconds 2. Minutes after the hour, range 0-59 3. Hours past midnight, range 0-23 4. Day of month, range 0-31 5. Number of months since January, range 0-12 6. Years since 1900 7. Number of days since Sunday, range 0-6 8. Days since January 1 9. Daylight savings indicator: positive if daylight savings is in effect, zero if not, and negative if the information is not available. --- 13391,13423 ---- Subroutine _Syntax_: ! `CALL LTIME(TIME, VALUES)' _Arguments_: ! TIME An `INTEGER' scalar expression corresponding ! to a system time, with `INTENT(IN)'. ! VALUES A default `INTEGER' array with 9 elements, ! with `INTENT(OUT)'. _Return value_: The elements of VALUES are assigned as follows: 1. Seconds after the minute, range 0-59 or 0-61 to allow for leap seconds + 2. Minutes after the hour, range 0-59 + 3. Hours past midnight, range 0-23 + 4. Day of month, range 0-31 + 5. Number of months since January, range 0-12 + 6. Years since 1900 + 7. Number of days since Sunday, range 0-6 + 8. Days since January 1 + 9. Daylight savings indicator: positive if daylight savings is in effect, zero if not, and negative if the information is not available. *************** _Return value_: *** 13290,13308 **** _See also_: *note CTIME::, *note GMTIME::, *note TIME::, *note TIME8::  File: gfortran.info, Node: MALLOC, Next: MASKL, Prev: LTIME, Up: Intrinsic Procedures ! 9.176 'MALLOC' -- Allocate dynamic memory ========================================= _Description_: ! 'MALLOC(SIZE)' allocates SIZE bytes of dynamic memory and returns ! the address of the allocated memory. The 'MALLOC' intrinsic is an extension intended to be used with Cray pointers, and is provided ! in GNU Fortran to allow the user to compile legacy code. For new code using Fortran 95 pointers, the memory allocation intrinsic is ! 'ALLOCATE'. _Standard_: GNU extension --- 13425,13444 ---- _See also_: *note CTIME::, *note GMTIME::, *note TIME::, *note TIME8:: +  File: gfortran.info, Node: MALLOC, Next: MASKL, Prev: LTIME, Up: Intrinsic Procedures ! 9.176 `MALLOC' -- Allocate dynamic memory ========================================= _Description_: ! `MALLOC(SIZE)' allocates SIZE bytes of dynamic memory and returns ! the address of the allocated memory. The `MALLOC' intrinsic is an extension intended to be used with Cray pointers, and is provided ! in GNU Fortran to allow the user to compile legacy code. For new code using Fortran 95 pointers, the memory allocation intrinsic is ! `ALLOCATE'. _Standard_: GNU extension *************** _Class_: *** 13311,13328 **** Function _Syntax_: ! 'PTR = MALLOC(SIZE)' _Arguments_: ! SIZE The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER(K)', with K such that ! variables of type 'INTEGER(K)' have the same size as C pointers ! ('sizeof(void *)'). _Example_: ! The following example demonstrates the use of 'MALLOC' and 'FREE' with Cray pointers. program test_malloc --- 13447,13464 ---- Function _Syntax_: ! `PTR = MALLOC(SIZE)' _Arguments_: ! SIZE The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER(K)', with K such that ! variables of type `INTEGER(K)' have the same size as C pointers ! (`sizeof(void *)'). _Example_: ! The following example demonstrates the use of `MALLOC' and `FREE' with Cray pointers. program test_malloc *************** _See also_: *** 13349,13359 ****  File: gfortran.info, Node: MASKL, Next: MASKR, Prev: MALLOC, Up: Intrinsic Procedures ! 9.177 'MASKL' -- Left justified mask ==================================== _Description_: ! 'MASKL(I[, KIND])' has its leftmost I bits set to 1, and the remaining bits set to 0. _Standard_: --- 13485,13495 ----  File: gfortran.info, Node: MASKL, Next: MASKR, Prev: MALLOC, Up: Intrinsic Procedures ! 9.177 `MASKL' -- Left justified mask ==================================== _Description_: ! `MASKL(I[, KIND])' has its leftmost I bits set to 1, and the remaining bits set to 0. _Standard_: *************** _Class_: *** 13363,13377 **** Elemental function _Syntax_: ! 'RESULT = MASKL(I[, KIND])' _Arguments_: ! I Shall be of type 'INTEGER'. ! KIND Shall be a scalar constant expression of type ! 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER'. If KIND is present, it specifies the kind value of the return type; otherwise, it is of the default integer kind. --- 13499,13513 ---- Elemental function _Syntax_: ! `RESULT = MASKL(I[, KIND])' _Arguments_: ! I Shall be of type `INTEGER'. ! KIND Shall be a scalar constant expression of type ! `INTEGER'. _Return value_: ! The return value is of type `INTEGER'. If KIND is present, it specifies the kind value of the return type; otherwise, it is of the default integer kind. *************** _See also_: *** 13381,13391 ****  File: gfortran.info, Node: MASKR, Next: MATMUL, Prev: MASKL, Up: Intrinsic Procedures ! 9.178 'MASKR' -- Right justified mask ===================================== _Description_: ! 'MASKL(I[, KIND])' has its rightmost I bits set to 1, and the remaining bits set to 0. _Standard_: --- 13517,13527 ----  File: gfortran.info, Node: MASKR, Next: MATMUL, Prev: MASKL, Up: Intrinsic Procedures ! 9.178 `MASKR' -- Right justified mask ===================================== _Description_: ! `MASKL(I[, KIND])' has its rightmost I bits set to 1, and the remaining bits set to 0. _Standard_: *************** _Class_: *** 13395,13409 **** Elemental function _Syntax_: ! 'RESULT = MASKR(I[, KIND])' _Arguments_: ! I Shall be of type 'INTEGER'. ! KIND Shall be a scalar constant expression of type ! 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER'. If KIND is present, it specifies the kind value of the return type; otherwise, it is of the default integer kind. --- 13531,13545 ---- Elemental function _Syntax_: ! `RESULT = MASKR(I[, KIND])' _Arguments_: ! I Shall be of type `INTEGER'. ! KIND Shall be a scalar constant expression of type ! `INTEGER'. _Return value_: ! The return value is of type `INTEGER'. If KIND is present, it specifies the kind value of the return type; otherwise, it is of the default integer kind. *************** _See also_: *** 13413,13419 ****  File: gfortran.info, Node: MATMUL, Next: MAX, Prev: MASKR, Up: Intrinsic Procedures ! 9.179 'MATMUL' -- matrix multiplication ======================================= _Description_: --- 13549,13555 ----  File: gfortran.info, Node: MATMUL, Next: MAX, Prev: MASKR, Up: Intrinsic Procedures ! 9.179 `MATMUL' -- matrix multiplication ======================================= _Description_: *************** _Class_: *** 13426,13454 **** Transformational function _Syntax_: ! 'RESULT = MATMUL(MATRIX_A, MATRIX_B)' _Arguments_: ! MATRIX_A An array of 'INTEGER', 'REAL', 'COMPLEX', or ! 'LOGICAL' type, with a rank of one or two. ! MATRIX_B An array of 'INTEGER', 'REAL', or 'COMPLEX' type ! if MATRIX_A is of a numeric type; otherwise, an ! array of 'LOGICAL' type. The rank shall be one ! or two, and the first (or only) dimension of ! MATRIX_B shall be equal to the last (or only) ! dimension of MATRIX_A. _Return value_: The matrix product of MATRIX_A and MATRIX_B. The type and kind of the result follow the usual type and kind promotion rules, as for ! the '*' or '.AND.' operators. _See also_:  File: gfortran.info, Node: MAX, Next: MAXEXPONENT, Prev: MATMUL, Up: Intrinsic Procedures ! 9.180 'MAX' -- Maximum value of an argument list ================================================ _Description_: --- 13562,13590 ---- Transformational function _Syntax_: ! `RESULT = MATMUL(MATRIX_A, MATRIX_B)' _Arguments_: ! MATRIX_A An array of `INTEGER', `REAL', `COMPLEX', or ! `LOGICAL' type, with a rank of one or two. ! MATRIX_B An array of `INTEGER', `REAL', or `COMPLEX' ! type if MATRIX_A is of a numeric type; ! otherwise, an array of `LOGICAL' type. The ! rank shall be one or two, and the first (or ! only) dimension of MATRIX_B shall be equal to ! the last (or only) dimension of MATRIX_A. _Return value_: The matrix product of MATRIX_A and MATRIX_B. The type and kind of the result follow the usual type and kind promotion rules, as for ! the `*' or `.AND.' operators. _See also_:  File: gfortran.info, Node: MAX, Next: MAXEXPONENT, Prev: MATMUL, Up: Intrinsic Procedures ! 9.180 `MAX' -- Maximum value of an argument list ================================================ _Description_: *************** _Class_: *** 13461,13503 **** Elemental function _Syntax_: ! 'RESULT = MAX(A1, A2 [, A3 [, ...]])' _Arguments_: ! A1 The type shall be 'INTEGER' or 'REAL'. ! A2, A3, An expression of the same type and kind as A1. ! ... (As a GNU extension, arguments of different ! kinds are permitted.) _Return value_: The return value corresponds to the maximum value among the arguments, and has the same type and kind as the first argument. _Specific names_: ! Name Argument Return type Standard ! 'MAX0(A1)' 'INTEGER(4) 'INTEGER(4)' Fortran 77 and ! A1' later ! 'AMAX0(A1)' 'INTEGER(4) 'REAL(MAX(X))' Fortran 77 and ! A1' later ! 'MAX1(A1)' 'REAL A1' 'INT(MAX(X))' Fortran 77 and ! later ! 'AMAX1(A1)' 'REAL(4) A1' 'REAL(4)' Fortran 77 and ! later ! 'DMAX1(A1)' 'REAL(8) A1' 'REAL(8)' Fortran 77 and ! later _See also_: *note MAXLOC:: *note MAXVAL::, *note MIN::  File: gfortran.info, Node: MAXEXPONENT, Next: MAXLOC, Prev: MAX, Up: Intrinsic Procedures ! 9.181 'MAXEXPONENT' -- Maximum exponent of a real kind ====================================================== _Description_: ! 'MAXEXPONENT(X)' returns the maximum exponent in the model of the ! type of 'X'. _Standard_: Fortran 95 and later --- 13597,13640 ---- Elemental function _Syntax_: ! `RESULT = MAX(A1, A2 [, A3 [, ...]])' _Arguments_: ! A1 The type shall be `INTEGER' or `REAL'. ! A2, A3, An expression of the same type and kind as A1. ! ... (As a GNU extension, arguments of different ! kinds are permitted.) _Return value_: The return value corresponds to the maximum value among the arguments, and has the same type and kind as the first argument. _Specific names_: ! Name Argument Return type Standard ! `MAX0(A1)' `INTEGER(4) `INTEGER(4)' Fortran 77 and ! A1' later ! `AMAX0(A1)' `INTEGER(4) `REAL(MAX(X))'Fortran 77 and ! A1' later ! `MAX1(A1)' `REAL A1' `INT(MAX(X))' Fortran 77 and ! later ! `AMAX1(A1)' `REAL(4) A1' `REAL(4)' Fortran 77 and ! later ! `DMAX1(A1)' `REAL(8) A1' `REAL(8)' Fortran 77 and ! later _See also_: *note MAXLOC:: *note MAXVAL::, *note MIN:: +  File: gfortran.info, Node: MAXEXPONENT, Next: MAXLOC, Prev: MAX, Up: Intrinsic Procedures ! 9.181 `MAXEXPONENT' -- Maximum exponent of a real kind ====================================================== _Description_: ! `MAXEXPONENT(X)' returns the maximum exponent in the model of the ! type of `X'. _Standard_: Fortran 95 and later *************** _Class_: *** 13506,13518 **** Inquiry function _Syntax_: ! 'RESULT = MAXEXPONENT(X)' _Arguments_: ! X Shall be of type 'REAL'. _Return value_: ! The return value is of type 'INTEGER' and of the default integer kind. _Example_: --- 13643,13655 ---- Inquiry function _Syntax_: ! `RESULT = MAXEXPONENT(X)' _Arguments_: ! X Shall be of type `REAL'. _Return value_: ! The return value is of type `INTEGER' and of the default integer kind. _Example_: *************** _Example_: *** 13527,13533 ****  File: gfortran.info, Node: MAXLOC, Next: MAXVAL, Prev: MAXEXPONENT, Up: Intrinsic Procedures ! 9.182 'MAXLOC' -- Location of the maximum value within an array =============================================================== _Description_: --- 13664,13670 ----  File: gfortran.info, Node: MAXLOC, Next: MAXVAL, Prev: MAXEXPONENT, Up: Intrinsic Procedures ! 9.182 `MAXLOC' -- Location of the maximum value within an array =============================================================== _Description_: *************** _Description_: *** 13535,13547 **** maximum value, or, if the DIM argument is supplied, determines the locations of the maximum element along each row of the array in the DIM direction. If MASK is present, only the elements for which ! MASK is '.TRUE.' are considered. If more than one element in the array has the maximum value, the location returned is that of the first such element in array element order. If the array has zero ! size, or all of the elements of MASK are '.FALSE.', then the result ! is an array of zeroes. Similarly, if DIM is supplied and all of ! the elements of MASK along a given row are zero, the result value ! for that row is zero. _Standard_: Fortran 95 and later --- 13672,13684 ---- maximum value, or, if the DIM argument is supplied, determines the locations of the maximum element along each row of the array in the DIM direction. If MASK is present, only the elements for which ! MASK is `.TRUE.' are considered. If more than one element in the array has the maximum value, the location returned is that of the first such element in array element order. If the array has zero ! size, or all of the elements of MASK are `.FALSE.', then the ! result is an array of zeroes. Similarly, if DIM is supplied and ! all of the elements of MASK along a given row are zero, the result ! value for that row is zero. _Standard_: Fortran 95 and later *************** _Class_: *** 13550,13566 **** Transformational function _Syntax_: ! 'RESULT = MAXLOC(ARRAY, DIM [, MASK])' ! 'RESULT = MAXLOC(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER' or 'REAL'. ! DIM (Optional) Shall be a scalar of type 'INTEGER', ! with a value between one and the rank of ARRAY, ! inclusive. It may not be an optional dummy ! argument. ! MASK Shall be an array of type 'LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, the result is a rank-one array with a length --- 13687,13703 ---- Transformational function _Syntax_: ! `RESULT = MAXLOC(ARRAY, DIM [, MASK])' ! `RESULT = MAXLOC(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER' or `REAL'. ! DIM (Optional) Shall be a scalar of type ! `INTEGER', with a value between one and the ! rank of ARRAY, inclusive. It may not be an ! optional dummy argument. ! MASK Shall be an array of type `LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, the result is a rank-one array with a length *************** _Return value_: *** 13568,13592 **** array with a rank one less than the rank of ARRAY, and a size corresponding to the size of ARRAY with the DIM dimension removed. If DIM is present and ARRAY has a rank of one, the result is a ! scalar. In all cases, the result is of default 'INTEGER' type. _See also_: *note MAX::, *note MAXVAL::  File: gfortran.info, Node: MAXVAL, Next: MCLOCK, Prev: MAXLOC, Up: Intrinsic Procedures ! 9.183 'MAXVAL' -- Maximum value of an array =========================================== _Description_: ! Determines the maximum value of the elements in an array value, or, ! if the DIM argument is supplied, determines the maximum value along ! each row of the array in the DIM direction. If MASK is present, ! only the elements for which MASK is '.TRUE.' are considered. If ! the array has zero size, or all of the elements of MASK are ! '.FALSE.', then the result is '-HUGE(ARRAY)' if ARRAY is numeric, ! or a string of nulls if ARRAY is of character type. _Standard_: Fortran 95 and later --- 13705,13730 ---- array with a rank one less than the rank of ARRAY, and a size corresponding to the size of ARRAY with the DIM dimension removed. If DIM is present and ARRAY has a rank of one, the result is a ! scalar. In all cases, the result is of default `INTEGER' type. _See also_: *note MAX::, *note MAXVAL:: +  File: gfortran.info, Node: MAXVAL, Next: MCLOCK, Prev: MAXLOC, Up: Intrinsic Procedures ! 9.183 `MAXVAL' -- Maximum value of an array =========================================== _Description_: ! Determines the maximum value of the elements in an array value, ! or, if the DIM argument is supplied, determines the maximum value ! along each row of the array in the DIM direction. If MASK is ! present, only the elements for which MASK is `.TRUE.' are ! considered. If the array has zero size, or all of the elements of ! MASK are `.FALSE.', then the result is `-HUGE(ARRAY)' if ARRAY is ! numeric, or a string of nulls if ARRAY is of character type. _Standard_: Fortran 95 and later *************** _Class_: *** 13595,13611 **** Transformational function _Syntax_: ! 'RESULT = MAXVAL(ARRAY, DIM [, MASK])' ! 'RESULT = MAXVAL(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER' or 'REAL'. ! DIM (Optional) Shall be a scalar of type 'INTEGER', ! with a value between one and the rank of ARRAY, ! inclusive. It may not be an optional dummy ! argument. ! MASK Shall be an array of type 'LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, or if ARRAY has a rank of one, the result is a --- 13733,13749 ---- Transformational function _Syntax_: ! `RESULT = MAXVAL(ARRAY, DIM [, MASK])' ! `RESULT = MAXVAL(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER' or `REAL'. ! DIM (Optional) Shall be a scalar of type ! `INTEGER', with a value between one and the ! rank of ARRAY, inclusive. It may not be an ! optional dummy argument. ! MASK Shall be an array of type `LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, or if ARRAY has a rank of one, the result is a *************** _See also_: *** 13620,13634 ****  File: gfortran.info, Node: MCLOCK, Next: MCLOCK8, Prev: MAXVAL, Up: Intrinsic Procedures ! 9.184 'MCLOCK' -- Time function =============================== _Description_: Returns the number of clock ticks since the start of the process, ! based on the function 'clock(3)' in the C standard library. This intrinsic is not fully portable, such as to systems with ! 32-bit 'INTEGER' types but supporting times wider than 32 bits. Therefore, the values returned by this intrinsic might be, or become, negative, or numerically less than previous values, during a single run of the compiled program. --- 13758,13772 ----  File: gfortran.info, Node: MCLOCK, Next: MCLOCK8, Prev: MAXVAL, Up: Intrinsic Procedures ! 9.184 `MCLOCK' -- Time function =============================== _Description_: Returns the number of clock ticks since the start of the process, ! based on the function `clock(3)' in the C standard library. This intrinsic is not fully portable, such as to systems with ! 32-bit `INTEGER' types but supporting times wider than 32 bits. Therefore, the values returned by this intrinsic might be, or become, negative, or numerically less than previous values, during a single run of the compiled program. *************** _Class_: *** 13640,13673 **** Function _Syntax_: ! 'RESULT = MCLOCK()' _Return value_: ! The return value is a scalar of type 'INTEGER(4)', equal to the ! number of clock ticks since the start of the process, or '-1' if ! the system does not support 'clock(3)'. _See also_: ! *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK::, *note ! TIME::  File: gfortran.info, Node: MCLOCK8, Next: MERGE, Prev: MCLOCK, Up: Intrinsic Procedures ! 9.185 'MCLOCK8' -- Time function (64-bit) ========================================= _Description_: Returns the number of clock ticks since the start of the process, ! based on the function 'clock(3)' in the C standard library. _Warning:_ this intrinsic does not increase the range of the timing ! values over that returned by 'clock(3)'. On a system with a 32-bit ! 'clock(3)', 'MCLOCK8' will return a 32-bit value, even though it is ! converted to a 64-bit 'INTEGER(8)' value. That means overflows of ! the 32-bit value can still occur. Therefore, the values returned ! by this intrinsic might be or become negative or numerically less ! than previous values during a single run of the compiled program. _Standard_: GNU extension --- 13778,13813 ---- Function _Syntax_: ! `RESULT = MCLOCK()' _Return value_: ! The return value is a scalar of type `INTEGER(4)', equal to the ! number of clock ticks since the start of the process, or `-1' if ! the system does not support `clock(3)'. _See also_: ! *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK::, ! *note TIME:: !  File: gfortran.info, Node: MCLOCK8, Next: MERGE, Prev: MCLOCK, Up: Intrinsic Procedures ! 9.185 `MCLOCK8' -- Time function (64-bit) ========================================= _Description_: Returns the number of clock ticks since the start of the process, ! based on the function `clock(3)' in the C standard library. _Warning:_ this intrinsic does not increase the range of the timing ! values over that returned by `clock(3)'. On a system with a 32-bit ! `clock(3)', `MCLOCK8' will return a 32-bit value, even though it ! is converted to a 64-bit `INTEGER(8)' value. That means overflows ! of the 32-bit value can still occur. Therefore, the values ! returned by this intrinsic might be or become negative or ! numerically less than previous values during a single run of the ! compiled program. _Standard_: GNU extension *************** _Class_: *** 13676,13702 **** Function _Syntax_: ! 'RESULT = MCLOCK8()' _Return value_: ! The return value is a scalar of type 'INTEGER(8)', equal to the ! number of clock ticks since the start of the process, or '-1' if ! the system does not support 'clock(3)'. _See also_: ! *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK::, *note ! TIME8::  File: gfortran.info, Node: MERGE, Next: MERGE_BITS, Prev: MCLOCK8, Up: Intrinsic Procedures ! 9.186 'MERGE' -- Merge variables ================================ _Description_: Select values from two arrays according to a logical mask. The ! result is equal to TSOURCE if MASK is '.TRUE.', or equal to FSOURCE ! if it is '.FALSE.'. _Standard_: Fortran 95 and later --- 13816,13843 ---- Function _Syntax_: ! `RESULT = MCLOCK8()' _Return value_: ! The return value is a scalar of type `INTEGER(8)', equal to the ! number of clock ticks since the start of the process, or `-1' if ! the system does not support `clock(3)'. _See also_: ! *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK::, ! *note TIME8:: !  File: gfortran.info, Node: MERGE, Next: MERGE_BITS, Prev: MCLOCK8, Up: Intrinsic Procedures ! 9.186 `MERGE' -- Merge variables ================================ _Description_: Select values from two arrays according to a logical mask. The ! result is equal to TSOURCE if MASK is `.TRUE.', or equal to ! FSOURCE if it is `.FALSE.'. _Standard_: Fortran 95 and later *************** _Class_: *** 13705,13732 **** Elemental function _Syntax_: ! 'RESULT = MERGE(TSOURCE, FSOURCE, MASK)' _Arguments_: ! TSOURCE May be of any type. ! FSOURCE Shall be of the same type and type parameters as ! TSOURCE. ! MASK Shall be of type 'LOGICAL'. _Return value_: The result is of the same type and type parameters as TSOURCE.  File: gfortran.info, Node: MERGE_BITS, Next: MIN, Prev: MERGE, Up: Intrinsic Procedures ! 9.187 'MERGE_BITS' -- Merge of bits under mask ============================================== _Description_: ! 'MERGE_BITS(I, J, MASK)' merges the bits of I and J as determined by the mask. The i-th bit of the result is equal to the i-th bit ! of I if the i-th bit of MASK is 1; it is equal to the i-th bit of J ! otherwise. _Standard_: Fortran 2008 and later --- 13846,13874 ---- Elemental function _Syntax_: ! `RESULT = MERGE(TSOURCE, FSOURCE, MASK)' _Arguments_: ! TSOURCE May be of any type. ! FSOURCE Shall be of the same type and type parameters ! as TSOURCE. ! MASK Shall be of type `LOGICAL'. _Return value_: The result is of the same type and type parameters as TSOURCE. +  File: gfortran.info, Node: MERGE_BITS, Next: MIN, Prev: MERGE, Up: Intrinsic Procedures ! 9.187 `MERGE_BITS' -- Merge of bits under mask ============================================== _Description_: ! `MERGE_BITS(I, J, MASK)' merges the bits of I and J as determined by the mask. The i-th bit of the result is equal to the i-th bit ! of I if the i-th bit of MASK is 1; it is equal to the i-th bit of ! J otherwise. _Standard_: Fortran 2008 and later *************** _Class_: *** 13735,13756 **** Elemental function _Syntax_: ! 'RESULT = MERGE_BITS(I, J, MASK)' _Arguments_: ! I Shall be of type 'INTEGER'. ! J Shall be of type 'INTEGER' and of the same kind ! as I. ! MASK Shall be of type 'INTEGER' and of the same kind ! as I. _Return value_: The result is of the same type and kind as I.  File: gfortran.info, Node: MIN, Next: MINEXPONENT, Prev: MERGE_BITS, Up: Intrinsic Procedures ! 9.188 'MIN' -- Minimum value of an argument list ================================================ _Description_: --- 13877,13899 ---- Elemental function _Syntax_: ! `RESULT = MERGE_BITS(I, J, MASK)' _Arguments_: ! I Shall be of type `INTEGER'. ! J Shall be of type `INTEGER' and of the same ! kind as I. ! MASK Shall be of type `INTEGER' and of the same ! kind as I. _Return value_: The result is of the same type and kind as I. +  File: gfortran.info, Node: MIN, Next: MINEXPONENT, Prev: MERGE_BITS, Up: Intrinsic Procedures ! 9.188 `MIN' -- Minimum value of an argument list ================================================ _Description_: *************** _Class_: *** 13763,13792 **** Elemental function _Syntax_: ! 'RESULT = MIN(A1, A2 [, A3, ...])' _Arguments_: ! A1 The type shall be 'INTEGER' or 'REAL'. ! A2, A3, An expression of the same type and kind as A1. ! ... (As a GNU extension, arguments of different ! kinds are permitted.) _Return value_: The return value corresponds to the maximum value among the arguments, and has the same type and kind as the first argument. _Specific names_: ! Name Argument Return type Standard ! 'MIN0(A1)' 'INTEGER(4) 'INTEGER(4)' Fortran 77 and ! A1' later ! 'AMIN0(A1)' 'INTEGER(4) 'REAL(4)' Fortran 77 and ! A1' later ! 'MIN1(A1)' 'REAL A1' 'INTEGER(4)' Fortran 77 and ! later ! 'AMIN1(A1)' 'REAL(4) A1' 'REAL(4)' Fortran 77 and ! later ! 'DMIN1(A1)' 'REAL(8) A1' 'REAL(8)' Fortran 77 and ! later _See also_: *note MAX::, *note MINLOC::, *note MINVAL:: --- 13906,13935 ---- Elemental function _Syntax_: ! `RESULT = MIN(A1, A2 [, A3, ...])' _Arguments_: ! A1 The type shall be `INTEGER' or `REAL'. ! A2, A3, An expression of the same type and kind as A1. ! ... (As a GNU extension, arguments of different ! kinds are permitted.) _Return value_: The return value corresponds to the maximum value among the arguments, and has the same type and kind as the first argument. _Specific names_: ! Name Argument Return type Standard ! `MIN0(A1)' `INTEGER(4) `INTEGER(4)' Fortran 77 and ! A1' later ! `AMIN0(A1)' `INTEGER(4) `REAL(4)' Fortran 77 and ! A1' later ! `MIN1(A1)' `REAL A1' `INTEGER(4)' Fortran 77 and ! later ! `AMIN1(A1)' `REAL(4) A1' `REAL(4)' Fortran 77 and ! later ! `DMIN1(A1)' `REAL(8) A1' `REAL(8)' Fortran 77 and ! later _See also_: *note MAX::, *note MINLOC::, *note MINVAL:: *************** _See also_: *** 13794,13805 ****  File: gfortran.info, Node: MINEXPONENT, Next: MINLOC, Prev: MIN, Up: Intrinsic Procedures ! 9.189 'MINEXPONENT' -- Minimum exponent of a real kind ====================================================== _Description_: ! 'MINEXPONENT(X)' returns the minimum exponent in the model of the ! type of 'X'. _Standard_: Fortran 95 and later --- 13937,13948 ----  File: gfortran.info, Node: MINEXPONENT, Next: MINLOC, Prev: MIN, Up: Intrinsic Procedures ! 9.189 `MINEXPONENT' -- Minimum exponent of a real kind ====================================================== _Description_: ! `MINEXPONENT(X)' returns the minimum exponent in the model of the ! type of `X'. _Standard_: Fortran 95 and later *************** _Class_: *** 13808,13829 **** Inquiry function _Syntax_: ! 'RESULT = MINEXPONENT(X)' _Arguments_: ! X Shall be of type 'REAL'. _Return value_: ! The return value is of type 'INTEGER' and of the default integer kind. _Example_: ! See 'MAXEXPONENT' for an example.  File: gfortran.info, Node: MINLOC, Next: MINVAL, Prev: MINEXPONENT, Up: Intrinsic Procedures ! 9.190 'MINLOC' -- Location of the minimum value within an array =============================================================== _Description_: --- 13951,13972 ---- Inquiry function _Syntax_: ! `RESULT = MINEXPONENT(X)' _Arguments_: ! X Shall be of type `REAL'. _Return value_: ! The return value is of type `INTEGER' and of the default integer kind. _Example_: ! See `MAXEXPONENT' for an example.  File: gfortran.info, Node: MINLOC, Next: MINVAL, Prev: MINEXPONENT, Up: Intrinsic Procedures ! 9.190 `MINLOC' -- Location of the minimum value within an array =============================================================== _Description_: *************** _Description_: *** 13831,13843 **** minimum value, or, if the DIM argument is supplied, determines the locations of the minimum element along each row of the array in the DIM direction. If MASK is present, only the elements for which ! MASK is '.TRUE.' are considered. If more than one element in the array has the minimum value, the location returned is that of the first such element in array element order. If the array has zero ! size, or all of the elements of MASK are '.FALSE.', then the result ! is an array of zeroes. Similarly, if DIM is supplied and all of ! the elements of MASK along a given row are zero, the result value ! for that row is zero. _Standard_: Fortran 95 and later --- 13974,13986 ---- minimum value, or, if the DIM argument is supplied, determines the locations of the minimum element along each row of the array in the DIM direction. If MASK is present, only the elements for which ! MASK is `.TRUE.' are considered. If more than one element in the array has the minimum value, the location returned is that of the first such element in array element order. If the array has zero ! size, or all of the elements of MASK are `.FALSE.', then the ! result is an array of zeroes. Similarly, if DIM is supplied and ! all of the elements of MASK along a given row are zero, the result ! value for that row is zero. _Standard_: Fortran 95 and later *************** _Class_: *** 13846,13862 **** Transformational function _Syntax_: ! 'RESULT = MINLOC(ARRAY, DIM [, MASK])' ! 'RESULT = MINLOC(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER' or 'REAL'. ! DIM (Optional) Shall be a scalar of type 'INTEGER', ! with a value between one and the rank of ARRAY, ! inclusive. It may not be an optional dummy ! argument. ! MASK Shall be an array of type 'LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, the result is a rank-one array with a length --- 13989,14005 ---- Transformational function _Syntax_: ! `RESULT = MINLOC(ARRAY, DIM [, MASK])' ! `RESULT = MINLOC(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER' or `REAL'. ! DIM (Optional) Shall be a scalar of type ! `INTEGER', with a value between one and the ! rank of ARRAY, inclusive. It may not be an ! optional dummy argument. ! MASK Shall be an array of type `LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, the result is a rank-one array with a length *************** _Return value_: *** 13864,13888 **** array with a rank one less than the rank of ARRAY, and a size corresponding to the size of ARRAY with the DIM dimension removed. If DIM is present and ARRAY has a rank of one, the result is a ! scalar. In all cases, the result is of default 'INTEGER' type. _See also_: *note MIN::, *note MINVAL::  File: gfortran.info, Node: MINVAL, Next: MOD, Prev: MINLOC, Up: Intrinsic Procedures ! 9.191 'MINVAL' -- Minimum value of an array =========================================== _Description_: ! Determines the minimum value of the elements in an array value, or, ! if the DIM argument is supplied, determines the minimum value along ! each row of the array in the DIM direction. If MASK is present, ! only the elements for which MASK is '.TRUE.' are considered. If ! the array has zero size, or all of the elements of MASK are ! '.FALSE.', then the result is 'HUGE(ARRAY)' if ARRAY is numeric, or ! a string of 'CHAR(255)' characters if ARRAY is of character type. _Standard_: Fortran 95 and later --- 14007,14033 ---- array with a rank one less than the rank of ARRAY, and a size corresponding to the size of ARRAY with the DIM dimension removed. If DIM is present and ARRAY has a rank of one, the result is a ! scalar. In all cases, the result is of default `INTEGER' type. _See also_: *note MIN::, *note MINVAL:: +  File: gfortran.info, Node: MINVAL, Next: MOD, Prev: MINLOC, Up: Intrinsic Procedures ! 9.191 `MINVAL' -- Minimum value of an array =========================================== _Description_: ! Determines the minimum value of the elements in an array value, ! or, if the DIM argument is supplied, determines the minimum value ! along each row of the array in the DIM direction. If MASK is ! present, only the elements for which MASK is `.TRUE.' are ! considered. If the array has zero size, or all of the elements of ! MASK are `.FALSE.', then the result is `HUGE(ARRAY)' if ARRAY is ! numeric, or a string of `CHAR(255)' characters if ARRAY is of ! character type. _Standard_: Fortran 95 and later *************** _Class_: *** 13891,13907 **** Transformational function _Syntax_: ! 'RESULT = MINVAL(ARRAY, DIM [, MASK])' ! 'RESULT = MINVAL(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER' or 'REAL'. ! DIM (Optional) Shall be a scalar of type 'INTEGER', ! with a value between one and the rank of ARRAY, ! inclusive. It may not be an optional dummy ! argument. ! MASK Shall be an array of type 'LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, or if ARRAY has a rank of one, the result is a --- 14036,14052 ---- Transformational function _Syntax_: ! `RESULT = MINVAL(ARRAY, DIM [, MASK])' ! `RESULT = MINVAL(ARRAY [, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER' or `REAL'. ! DIM (Optional) Shall be a scalar of type ! `INTEGER', with a value between one and the ! rank of ARRAY, inclusive. It may not be an ! optional dummy argument. ! MASK Shall be an array of type `LOGICAL', and ! conformable with ARRAY. _Return value_: If DIM is absent, or if ARRAY has a rank of one, the result is a *************** _Return value_: *** 13913,13926 **** _See also_: *note MIN::, *note MINLOC::  File: gfortran.info, Node: MOD, Next: MODULO, Prev: MINVAL, Up: Intrinsic Procedures ! 9.192 'MOD' -- Remainder function ================================= _Description_: ! 'MOD(A,P)' computes the remainder of the division of A by P. _Standard_: Fortran 77 and later --- 14058,14072 ---- _See also_: *note MIN::, *note MINLOC:: +  File: gfortran.info, Node: MOD, Next: MODULO, Prev: MINVAL, Up: Intrinsic Procedures ! 9.192 `MOD' -- Remainder function ================================= _Description_: ! `MOD(A,P)' computes the remainder of the division of A by P. _Standard_: Fortran 77 and later *************** _Class_: *** 13929,13946 **** Elemental function _Syntax_: ! 'RESULT = MOD(A, P)' _Arguments_: ! A Shall be a scalar of type 'INTEGER' or 'REAL'. ! P Shall be a scalar of the same type and kind as A ! and not equal to zero. _Return value_: ! The return value is the result of 'A - (INT(A/P) * P)'. The type and kind of the return value is the same as that of the arguments. ! The returned value has the same sign as A and a magnitude less than ! the magnitude of P. _Example_: program test_mod --- 14075,14092 ---- Elemental function _Syntax_: ! `RESULT = MOD(A, P)' _Arguments_: ! A Shall be a scalar of type `INTEGER' or `REAL'. ! P Shall be a scalar of the same type and kind as ! A and not equal to zero. _Return value_: ! The return value is the result of `A - (INT(A/P) * P)'. The type and kind of the return value is the same as that of the arguments. ! The returned value has the same sign as A and a magnitude less ! than the magnitude of P. _Example_: program test_mod *************** _Example_: *** 13961,13985 **** end program test_mod _Specific names_: ! Name Arguments Return type Standard ! 'MOD(A,P)' 'INTEGER 'INTEGER' Fortran 95 and ! A,P' later ! 'AMOD(A,P)' 'REAL(4) 'REAL(4)' Fortran 95 and ! A,P' later ! 'DMOD(A,P)' 'REAL(8) 'REAL(8)' Fortran 95 and ! A,P' later _See also_: *note MODULO::  File: gfortran.info, Node: MODULO, Next: MOVE_ALLOC, Prev: MOD, Up: Intrinsic Procedures ! 9.193 'MODULO' -- Modulo function ================================= _Description_: ! 'MODULO(A,P)' computes the A modulo P. _Standard_: Fortran 95 and later --- 14107,14132 ---- end program test_mod _Specific names_: ! Name Arguments Return type Standard ! `MOD(A,P)' `INTEGER `INTEGER' Fortran 95 and ! A,P' later ! `AMOD(A,P)' `REAL(4) `REAL(4)' Fortran 95 and ! A,P' later ! `DMOD(A,P)' `REAL(8) `REAL(8)' Fortran 95 and ! A,P' later _See also_: *note MODULO:: +  File: gfortran.info, Node: MODULO, Next: MOVE_ALLOC, Prev: MOD, Up: Intrinsic Procedures ! 9.193 `MODULO' -- Modulo function ================================= _Description_: ! `MODULO(A,P)' computes the A modulo P. _Standard_: Fortran 95 and later *************** _Class_: *** 13988,14007 **** Elemental function _Syntax_: ! 'RESULT = MODULO(A, P)' _Arguments_: ! A Shall be a scalar of type 'INTEGER' or 'REAL'. ! P Shall be a scalar of the same type and kind as ! A. It shall not be zero. _Return value_: The type and kind of the result are those of the arguments. ! If A and P are of type 'INTEGER': ! 'MODULO(A,P)' has the value R such that 'A=Q*P+R', where Q is an integer and R is between 0 (inclusive) and P (exclusive). ! If A and P are of type 'REAL': ! 'MODULO(A,P)' has the value of 'A - FLOOR (A / P) * P'. The returned value has the same sign as P and a magnitude less than the magnitude of P. --- 14135,14155 ---- Elemental function _Syntax_: ! `RESULT = MODULO(A, P)' _Arguments_: ! A Shall be a scalar of type `INTEGER' or `REAL'. ! P Shall be a scalar of the same type and kind as ! A. It shall not be zero. _Return value_: The type and kind of the result are those of the arguments. ! If A and P are of type `INTEGER': ! `MODULO(A,P)' has the value R such that `A=Q*P+R', where Q is an integer and R is between 0 (inclusive) and P (exclusive). ! ! If A and P are of type `REAL': ! `MODULO(A,P)' has the value of `A - FLOOR (A / P) * P'. The returned value has the same sign as P and a magnitude less than the magnitude of P. *************** _Example_: *** 14020,14033 **** _See also_: *note MOD::  File: gfortran.info, Node: MOVE_ALLOC, Next: MVBITS, Prev: MODULO, Up: Intrinsic Procedures ! 9.194 'MOVE_ALLOC' -- Move allocation from one object to another ================================================================ _Description_: ! 'MOVE_ALLOC(FROM, TO)' moves the allocation from FROM to TO. FROM will become deallocated in the process. _Standard_: --- 14168,14182 ---- _See also_: *note MOD:: +  File: gfortran.info, Node: MOVE_ALLOC, Next: MVBITS, Prev: MODULO, Up: Intrinsic Procedures ! 9.194 `MOVE_ALLOC' -- Move allocation from one object to another ================================================================ _Description_: ! `MOVE_ALLOC(FROM, TO)' moves the allocation from FROM to TO. FROM will become deallocated in the process. _Standard_: *************** _Class_: *** 14037,14049 **** Pure subroutine _Syntax_: ! 'CALL MOVE_ALLOC(FROM, TO)' _Arguments_: ! FROM 'ALLOCATABLE', 'INTENT(INOUT)', may be of any ! type and kind. ! TO 'ALLOCATABLE', 'INTENT(OUT)', shall be of the ! same type, kind and rank as FROM. _Return value_: None --- 14186,14198 ---- Pure subroutine _Syntax_: ! `CALL MOVE_ALLOC(FROM, TO)' _Arguments_: ! FROM `ALLOCATABLE', `INTENT(INOUT)', may be of any ! type and kind. ! TO `ALLOCATABLE', `INTENT(OUT)', shall be of the ! same type, kind and rank as FROM. _Return value_: None *************** _Example_: *** 14062,14076 ****  File: gfortran.info, Node: MVBITS, Next: NEAREST, Prev: MOVE_ALLOC, Up: Intrinsic Procedures ! 9.195 'MVBITS' -- Move bits from one integer to another ======================================================= _Description_: ! Moves LEN bits from positions FROMPOS through 'FROMPOS+LEN-1' of ! FROM to positions TOPOS through 'TOPOS+LEN-1' of TO. The portion of argument TO not affected by the movement of bits is unchanged. ! The values of 'FROMPOS+LEN-1' and 'TOPOS+LEN-1' must be less than ! 'BIT_SIZE(FROM)'. _Standard_: Fortran 95 and later --- 14211,14225 ----  File: gfortran.info, Node: MVBITS, Next: NEAREST, Prev: MOVE_ALLOC, Up: Intrinsic Procedures ! 9.195 `MVBITS' -- Move bits from one integer to another ======================================================= _Description_: ! Moves LEN bits from positions FROMPOS through `FROMPOS+LEN-1' of ! FROM to positions TOPOS through `TOPOS+LEN-1' of TO. The portion of argument TO not affected by the movement of bits is unchanged. ! The values of `FROMPOS+LEN-1' and `TOPOS+LEN-1' must be less than ! `BIT_SIZE(FROM)'. _Standard_: Fortran 95 and later *************** _Class_: *** 14079,14093 **** Elemental subroutine _Syntax_: ! 'CALL MVBITS(FROM, FROMPOS, LEN, TO, TOPOS)' _Arguments_: ! FROM The type shall be 'INTEGER'. ! FROMPOS The type shall be 'INTEGER'. ! LEN The type shall be 'INTEGER'. ! TO The type shall be 'INTEGER', of the same kind as ! FROM. ! TOPOS The type shall be 'INTEGER'. _See also_: *note IBCLR::, *note IBSET::, *note IBITS::, *note IAND::, *note --- 14228,14242 ---- Elemental subroutine _Syntax_: ! `CALL MVBITS(FROM, FROMPOS, LEN, TO, TOPOS)' _Arguments_: ! FROM The type shall be `INTEGER'. ! FROMPOS The type shall be `INTEGER'. ! LEN The type shall be `INTEGER'. ! TO The type shall be `INTEGER', of the same kind ! as FROM. ! TOPOS The type shall be `INTEGER'. _See also_: *note IBCLR::, *note IBSET::, *note IBITS::, *note IAND::, *note *************** _See also_: *** 14096,14107 ****  File: gfortran.info, Node: NEAREST, Next: NEW_LINE, Prev: MVBITS, Up: Intrinsic Procedures ! 9.196 'NEAREST' -- Nearest representable number =============================================== _Description_: ! 'NEAREST(X, S)' returns the processor-representable number nearest ! to 'X' in the direction indicated by the sign of 'S'. _Standard_: Fortran 95 and later --- 14245,14256 ----  File: gfortran.info, Node: NEAREST, Next: NEW_LINE, Prev: MVBITS, Up: Intrinsic Procedures ! 9.196 `NEAREST' -- Nearest representable number =============================================== _Description_: ! `NEAREST(X, S)' returns the processor-representable number nearest ! to `X' in the direction indicated by the sign of `S'. _Standard_: Fortran 95 and later *************** _Class_: *** 14110,14126 **** Elemental function _Syntax_: ! 'RESULT = NEAREST(X, S)' _Arguments_: ! X Shall be of type 'REAL'. ! S Shall be of type 'REAL' and not equal to zero. _Return value_: ! The return value is of the same type as 'X'. If 'S' is positive, ! 'NEAREST' returns the processor-representable number greater than ! 'X' and nearest to it. If 'S' is negative, 'NEAREST' returns the ! processor-representable number smaller than 'X' and nearest to it. _Example_: program test_nearest --- 14259,14275 ---- Elemental function _Syntax_: ! `RESULT = NEAREST(X, S)' _Arguments_: ! X Shall be of type `REAL'. ! S Shall be of type `REAL' and not equal to zero. _Return value_: ! The return value is of the same type as `X'. If `S' is positive, ! `NEAREST' returns the processor-representable number greater than ! `X' and nearest to it. If `S' is negative, `NEAREST' returns the ! processor-representable number smaller than `X' and nearest to it. _Example_: program test_nearest *************** _Example_: *** 14133,14143 ****  File: gfortran.info, Node: NEW_LINE, Next: NINT, Prev: NEAREST, Up: Intrinsic Procedures ! 9.197 'NEW_LINE' -- New line character ====================================== _Description_: ! 'NEW_LINE(C)' returns the new-line character. _Standard_: Fortran 2003 and later --- 14282,14292 ----  File: gfortran.info, Node: NEW_LINE, Next: NINT, Prev: NEAREST, Up: Intrinsic Procedures ! 9.197 `NEW_LINE' -- New line character ====================================== _Description_: ! `NEW_LINE(C)' returns the new-line character. _Standard_: Fortran 2003 and later *************** _Class_: *** 14146,14156 **** Inquiry function _Syntax_: ! 'RESULT = NEW_LINE(C)' _Arguments_: ! C The argument shall be a scalar or array of the ! type 'CHARACTER'. _Return value_: Returns a CHARACTER scalar of length one with the new-line --- 14295,14305 ---- Inquiry function _Syntax_: ! `RESULT = NEW_LINE(C)' _Arguments_: ! C The argument shall be a scalar or array of the ! type `CHARACTER'. _Return value_: Returns a CHARACTER scalar of length one with the new-line *************** _Example_: *** 14165,14175 ****  File: gfortran.info, Node: NINT, Next: NORM2, Prev: NEW_LINE, Up: Intrinsic Procedures ! 9.198 'NINT' -- Nearest whole number ==================================== _Description_: ! 'NINT(A)' rounds its argument to the nearest whole number. _Standard_: Fortran 77 and later, with KIND argument Fortran 90 and later --- 14314,14324 ----  File: gfortran.info, Node: NINT, Next: NORM2, Prev: NEW_LINE, Up: Intrinsic Procedures ! 9.198 `NINT' -- Nearest whole number ==================================== _Description_: ! `NINT(A)' rounds its argument to the nearest whole number. _Standard_: Fortran 77 and later, with KIND argument Fortran 90 and later *************** _Class_: *** 14178,14195 **** Elemental function _Syntax_: ! 'RESULT = NINT(A [, KIND])' _Arguments_: ! A The type of the argument shall be 'REAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: Returns A with the fractional portion of its magnitude eliminated by rounding to the nearest whole number and with its sign ! preserved, converted to an 'INTEGER' of the default kind. _Example_: program test_nint --- 14327,14344 ---- Elemental function _Syntax_: ! `RESULT = NINT(A [, KIND])' _Arguments_: ! A The type of the argument shall be `REAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: Returns A with the fractional portion of its magnitude eliminated by rounding to the nearest whole number and with its sign ! preserved, converted to an `INTEGER' of the default kind. _Example_: program test_nint *************** _Example_: *** 14201,14219 **** end program test_nint _Specific names_: ! Name Argument Return Type Standard ! 'NINT(A)' 'REAL(4) A' 'INTEGER' Fortran 95 and ! later ! 'IDNINT(A)' 'REAL(8) A' 'INTEGER' Fortran 95 and ! later _See also_: *note CEILING::, *note FLOOR::  File: gfortran.info, Node: NORM2, Next: NOT, Prev: NINT, Up: Intrinsic Procedures ! 9.199 'NORM2' -- Euclidean vector norms ======================================= _Description_: --- 14350,14369 ---- end program test_nint _Specific names_: ! Name Argument Return Type Standard ! `NINT(A)' `REAL(4) A' `INTEGER' Fortran 95 and ! later ! `IDNINT(A)' `REAL(8) A' `INTEGER' Fortran 95 and ! later _See also_: *note CEILING::, *note FLOOR:: +  File: gfortran.info, Node: NORM2, Next: NOT, Prev: NINT, Up: Intrinsic Procedures ! 9.199 `NORM2' -- Euclidean vector norms ======================================= _Description_: *************** _Class_: *** 14227,14247 **** Transformational function _Syntax_: ! 'RESULT = NORM2(ARRAY[, DIM])' _Arguments_: ! ARRAY Shall be an array of type 'REAL' ! DIM (Optional) shall be a scalar of type 'INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the square root of the sum of all ! elements in ARRAY squared is returned. Otherwise, an array of rank ! n-1, where n equals the rank of ARRAY, and a shape similar to that ! of ARRAY with dimension DIM dropped is returned. _Example_: PROGRAM test_sum --- 14377,14397 ---- Transformational function _Syntax_: ! `RESULT = NORM2(ARRAY[, DIM])' _Arguments_: ! ARRAY Shall be an array of type `REAL' ! DIM (Optional) shall be a scalar of type `INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the square root of the sum of all ! elements in ARRAY squared is returned. Otherwise, an array of ! rank n-1, where n equals the rank of ARRAY, and a shape similar to ! that of ARRAY with dimension DIM dropped is returned. _Example_: PROGRAM test_sum *************** _Example_: *** 14252,14262 ****  File: gfortran.info, Node: NOT, Next: NULL, Prev: NORM2, Up: Intrinsic Procedures ! 9.200 'NOT' -- Logical negation =============================== _Description_: ! 'NOT' returns the bitwise Boolean inverse of I. _Standard_: Fortran 95 and later --- 14402,14412 ----  File: gfortran.info, Node: NOT, Next: NULL, Prev: NORM2, Up: Intrinsic Procedures ! 9.200 `NOT' -- Logical negation =============================== _Description_: ! `NOT' returns the bitwise Boolean inverse of I. _Standard_: Fortran 95 and later *************** _Class_: *** 14265,14286 **** Elemental function _Syntax_: ! 'RESULT = NOT(I)' _Arguments_: ! I The type shall be 'INTEGER'. _Return value_: ! The return type is 'INTEGER', of the same kind as the argument. _See also_: *note IAND::, *note IEOR::, *note IOR::, *note IBITS::, *note IBSET::, *note IBCLR::  File: gfortran.info, Node: NULL, Next: NUM_IMAGES, Prev: NOT, Up: Intrinsic Procedures ! 9.201 'NULL' -- Function that returns an disassociated pointer ============================================================== _Description_: --- 14415,14437 ---- Elemental function _Syntax_: ! `RESULT = NOT(I)' _Arguments_: ! I The type shall be `INTEGER'. _Return value_: ! The return type is `INTEGER', of the same kind as the argument. _See also_: *note IAND::, *note IEOR::, *note IOR::, *note IBITS::, *note IBSET::, *note IBCLR:: +  File: gfortran.info, Node: NULL, Next: NUM_IMAGES, Prev: NOT, Up: Intrinsic Procedures ! 9.201 `NULL' -- Function that returns an disassociated pointer ============================================================== _Description_: *************** _Description_: *** 14289,14295 **** If MOLD is present, a disassociated pointer of the same type is returned, otherwise the type is determined by context. ! In Fortran 95, MOLD is optional. Please note that Fortran 2003 includes cases where it is required. _Standard_: --- 14440,14446 ---- If MOLD is present, a disassociated pointer of the same type is returned, otherwise the type is determined by context. ! In Fortran 95, MOLD is optional. Please note that Fortran 2003 includes cases where it is required. _Standard_: *************** _Class_: *** 14299,14309 **** Transformational function _Syntax_: ! 'PTR => NULL([MOLD])' _Arguments_: ! MOLD (Optional) shall be a pointer of any association ! status and of any type. _Return value_: A disassociated pointer. --- 14450,14460 ---- Transformational function _Syntax_: ! `PTR => NULL([MOLD])' _Arguments_: ! MOLD (Optional) shall be a pointer of any ! association status and of any type. _Return value_: A disassociated pointer. *************** _See also_: *** 14317,14352 ****  File: gfortran.info, Node: NUM_IMAGES, Next: OR, Prev: NULL, Up: Intrinsic Procedures ! 9.202 'NUM_IMAGES' -- Function that returns the number of images ================================================================ _Description_: Returns the number of images. _Standard_: ! Fortran 2008 and later. With DISTANCE or FAILED argument, Technical Specification (TS) 18508 or later _Class_: Transformational function _Syntax_: ! 'RESULT = NUM_IMAGES(DISTANCE, FAILED)' _Arguments_: ! DISTANCE (optional, intent(in)) Nonnegative scalar ! integer ! FAILED (optional, intent(in)) Scalar logical expression _Return value_: Scalar default-kind integer. If DISTANCE is not present or has ! value 0, the number of images in the current team is returned. For values smaller or equal distance to the initial team, it returns the number of images index on the ancestor team which has a ! distance of DISTANCE from the invoking team. If DISTANCE is larger than the distance to the initial team, the number of images of the ! initial team is returned. If FAILED is not present the total ! number of images is returned; if it has the value '.TRUE.', the number of failed images is returned, otherwise, the number of images which do have not the failed status. --- 14468,14504 ----  File: gfortran.info, Node: NUM_IMAGES, Next: OR, Prev: NULL, Up: Intrinsic Procedures ! 9.202 `NUM_IMAGES' -- Function that returns the number of images ================================================================ _Description_: Returns the number of images. _Standard_: ! Fortran 2008 and later. With DISTANCE or FAILED argument, Technical Specification (TS) 18508 or later _Class_: Transformational function _Syntax_: ! `RESULT = NUM_IMAGES(DISTANCE, FAILED)' _Arguments_: ! DISTANCE (optional, intent(in)) Nonnegative scalar ! integer ! FAILED (optional, intent(in)) Scalar logical ! expression _Return value_: Scalar default-kind integer. If DISTANCE is not present or has ! value 0, the number of images in the current team is returned. For values smaller or equal distance to the initial team, it returns the number of images index on the ancestor team which has a ! distance of DISTANCE from the invoking team. If DISTANCE is larger than the distance to the initial team, the number of images of the ! initial team is returned. If FAILED is not present the total ! number of images is returned; if it has the value `.TRUE.', the number of failed images is returned, otherwise, the number of images which do have not the failed status. *************** _See also_: *** 14367,14377 ****  File: gfortran.info, Node: OR, Next: PACK, Prev: NUM_IMAGES, Up: Intrinsic Procedures ! 9.203 'OR' -- Bitwise logical OR ================================ _Description_: ! Bitwise logical 'OR'. This intrinsic routine is provided for backwards compatibility with GNU Fortran 77. For integer arguments, programmers should consider --- 14519,14529 ----  File: gfortran.info, Node: OR, Next: PACK, Prev: NUM_IMAGES, Up: Intrinsic Procedures ! 9.203 `OR' -- Bitwise logical OR ================================ _Description_: ! Bitwise logical `OR'. This intrinsic routine is provided for backwards compatibility with GNU Fortran 77. For integer arguments, programmers should consider *************** _Class_: *** 14385,14402 **** Function _Syntax_: ! 'RESULT = OR(I, J)' _Arguments_: ! I The type shall be either a scalar 'INTEGER' type ! or a scalar 'LOGICAL' type. ! J The type shall be the same as the type of J. _Return value_: ! The return type is either a scalar 'INTEGER' or a scalar 'LOGICAL'. ! If the kind type parameters differ, then the smaller kind type is ! implicitly converted to larger kind, and the return has the larger ! kind. _Example_: PROGRAM test_or --- 14537,14554 ---- Function _Syntax_: ! `RESULT = OR(I, J)' _Arguments_: ! I The type shall be either a scalar `INTEGER' ! type or a scalar `LOGICAL' type. ! J The type shall be the same as the type of J. _Return value_: ! The return type is either a scalar `INTEGER' or a scalar ! `LOGICAL'. If the kind type parameters differ, then the smaller ! kind type is implicitly converted to larger kind, and the return ! has the larger kind. _Example_: PROGRAM test_or *************** _See also_: *** 14414,14427 ****  File: gfortran.info, Node: PACK, Next: PARITY, Prev: OR, Up: Intrinsic Procedures ! 9.204 'PACK' -- Pack an array into an array of rank one ======================================================= _Description_: Stores the elements of ARRAY in an array of rank one. The beginning of the resulting array is made up of elements whose ! MASK equals 'TRUE'. Afterwards, positions are filled with elements taken from VECTOR. _Standard_: --- 14566,14579 ----  File: gfortran.info, Node: PACK, Next: PARITY, Prev: OR, Up: Intrinsic Procedures ! 9.204 `PACK' -- Pack an array into an array of rank one ======================================================= _Description_: Stores the elements of ARRAY in an array of rank one. The beginning of the resulting array is made up of elements whose ! MASK equals `TRUE'. Afterwards, positions are filled with elements taken from VECTOR. _Standard_: *************** _Class_: *** 14431,14455 **** Transformational function _Syntax_: ! 'RESULT = PACK(ARRAY, MASK[,VECTOR])' _Arguments_: ! ARRAY Shall be an array of any type. ! MASK Shall be an array of type 'LOGICAL' and of the ! same size as ARRAY. Alternatively, it may be a ! 'LOGICAL' scalar. ! VECTOR (Optional) shall be an array of the same type as ! ARRAY and of rank one. If present, the number ! of elements in VECTOR shall be equal to or ! greater than the number of true elements in ! MASK. If MASK is scalar, the number of elements ! in VECTOR shall be equal to or greater than the ! number of elements in ARRAY. _Return value_: The result is an array of rank one and the same type as that of ARRAY. If VECTOR is present, the result size is that of VECTOR, ! the number of 'TRUE' values in MASK otherwise. _Example_: Gathering nonzero elements from an array: --- 14583,14607 ---- Transformational function _Syntax_: ! `RESULT = PACK(ARRAY, MASK[,VECTOR])' _Arguments_: ! ARRAY Shall be an array of any type. ! MASK Shall be an array of type `LOGICAL' and of the ! same size as ARRAY. Alternatively, it may be a ! `LOGICAL' scalar. ! VECTOR (Optional) shall be an array of the same type ! as ARRAY and of rank one. If present, the ! number of elements in VECTOR shall be equal to ! or greater than the number of true elements in ! MASK. If MASK is scalar, the number of ! elements in VECTOR shall be equal to or ! greater than the number of elements in ARRAY. _Return value_: The result is an array of rank one and the same type as that of ARRAY. If VECTOR is present, the result size is that of VECTOR, ! the number of `TRUE' values in MASK otherwise. _Example_: Gathering nonzero elements from an array: *************** _See also_: *** 14473,14483 ****  File: gfortran.info, Node: PARITY, Next: PERROR, Prev: PACK, Up: Intrinsic Procedures ! 9.205 'PARITY' -- Reduction with exclusive OR ============================================= _Description_: ! Calculates the parity, i.e. the reduction using '.XOR.', of MASK along dimension DIM. _Standard_: --- 14625,14635 ----  File: gfortran.info, Node: PARITY, Next: PERROR, Prev: PACK, Up: Intrinsic Procedures ! 9.205 `PARITY' -- Reduction with exclusive OR ============================================= _Description_: ! Calculates the parity, i.e. the reduction using `.XOR.', of MASK along dimension DIM. _Standard_: *************** _Class_: *** 14487,14505 **** Transformational function _Syntax_: ! 'RESULT = PARITY(MASK[, DIM])' _Arguments_: ! LOGICAL Shall be an array of type 'LOGICAL' ! DIM (Optional) shall be a scalar of type 'INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of MASK. _Return value_: The result is of the same type as MASK. If DIM is absent, a scalar with the parity of all elements in MASK ! is returned, i.e. true if an odd number of elements is '.true.' and false otherwise. If DIM is present, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of MASK with dimension DIM dropped is returned. --- 14639,14657 ---- Transformational function _Syntax_: ! `RESULT = PARITY(MASK[, DIM])' _Arguments_: ! LOGICAL Shall be an array of type `LOGICAL' ! DIM (Optional) shall be a scalar of type `INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of MASK. _Return value_: The result is of the same type as MASK. If DIM is absent, a scalar with the parity of all elements in MASK ! is returned, i.e. true if an odd number of elements is `.true.' and false otherwise. If DIM is present, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of MASK with dimension DIM dropped is returned. *************** _Example_: *** 14513,14525 ****  File: gfortran.info, Node: PERROR, Next: POPCNT, Prev: PARITY, Up: Intrinsic Procedures ! 9.206 'PERROR' -- Print system error message ============================================ _Description_: ! Prints (on the C 'stderr' stream) a newline-terminated error ! message corresponding to the last system error. This is prefixed ! by STRING, a colon and a space. See 'perror(3)'. _Standard_: GNU extension --- 14665,14677 ----  File: gfortran.info, Node: PERROR, Next: POPCNT, Prev: PARITY, Up: Intrinsic Procedures ! 9.206 `PERROR' -- Print system error message ============================================ _Description_: ! Prints (on the C `stderr' stream) a newline-terminated error ! message corresponding to the last system error. This is prefixed by ! STRING, a colon and a space. See `perror(3)'. _Standard_: GNU extension *************** _Class_: *** 14528,14538 **** Subroutine _Syntax_: ! 'CALL PERROR(STRING)' _Arguments_: ! STRING A scalar of type 'CHARACTER' and of the default ! kind. _See also_: *note IERRNO:: --- 14680,14690 ---- Subroutine _Syntax_: ! `CALL PERROR(STRING)' _Arguments_: ! STRING A scalar of type `CHARACTER' and of the ! default kind. _See also_: *note IERRNO:: *************** _See also_: *** 14540,14551 ****  File: gfortran.info, Node: POPCNT, Next: POPPAR, Prev: PERROR, Up: Intrinsic Procedures ! 9.207 'POPCNT' -- Number of bits set ==================================== _Description_: ! 'POPCNT(I)' returns the number of bits set ('1' bits) in the binary ! representation of 'I'. _Standard_: Fortran 2008 and later --- 14692,14703 ----  File: gfortran.info, Node: POPCNT, Next: POPPAR, Prev: PERROR, Up: Intrinsic Procedures ! 9.207 `POPCNT' -- Number of bits set ==================================== _Description_: ! `POPCNT(I)' returns the number of bits set ('1' bits) in the binary ! representation of `I'. _Standard_: Fortran 2008 and later *************** _Class_: *** 14554,14566 **** Elemental function _Syntax_: ! 'RESULT = POPCNT(I)' _Arguments_: ! I Shall be of type 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the default integer kind. _See also_: --- 14706,14718 ---- Elemental function _Syntax_: ! `RESULT = POPCNT(I)' _Arguments_: ! I Shall be of type `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the default integer kind. _See also_: *************** _Example_: *** 14576,14588 ****  File: gfortran.info, Node: POPPAR, Next: PRECISION, Prev: POPCNT, Up: Intrinsic Procedures ! 9.208 'POPPAR' -- Parity of the number of bits set ================================================== _Description_: ! 'POPPAR(I)' returns parity of the integer 'I', i.e. the parity of the number of bits set ('1' bits) in the binary representation of ! 'I'. It is equal to 0 if 'I' has an even number of bits set, and 1 for an odd number of '1' bits. _Standard_: --- 14728,14740 ----  File: gfortran.info, Node: POPPAR, Next: PRECISION, Prev: POPCNT, Up: Intrinsic Procedures ! 9.208 `POPPAR' -- Parity of the number of bits set ================================================== _Description_: ! `POPPAR(I)' returns parity of the integer `I', i.e. the parity of the number of bits set ('1' bits) in the binary representation of ! `I'. It is equal to 0 if `I' has an even number of bits set, and 1 for an odd number of '1' bits. _Standard_: *************** _Class_: *** 14592,14604 **** Elemental function _Syntax_: ! 'RESULT = POPPAR(I)' _Arguments_: ! I Shall be of type 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the default integer kind. _See also_: --- 14744,14756 ---- Elemental function _Syntax_: ! `RESULT = POPPAR(I)' _Arguments_: ! I Shall be of type `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the default integer kind. _See also_: *************** _Example_: *** 14614,14625 ****  File: gfortran.info, Node: PRECISION, Next: PRESENT, Prev: POPPAR, Up: Intrinsic Procedures ! 9.209 'PRECISION' -- Decimal precision of a real kind ===================================================== _Description_: ! 'PRECISION(X)' returns the decimal precision in the model of the ! type of 'X'. _Standard_: Fortran 95 and later --- 14766,14777 ----  File: gfortran.info, Node: PRECISION, Next: PRESENT, Prev: POPPAR, Up: Intrinsic Procedures ! 9.209 `PRECISION' -- Decimal precision of a real kind ===================================================== _Description_: ! `PRECISION(X)' returns the decimal precision in the model of the ! type of `X'. _Standard_: Fortran 95 and later *************** _Class_: *** 14628,14640 **** Inquiry function _Syntax_: ! 'RESULT = PRECISION(X)' _Arguments_: ! X Shall be of type 'REAL' or 'COMPLEX'. _Return value_: ! The return value is of type 'INTEGER' and of the default integer kind. _See also_: --- 14780,14792 ---- Inquiry function _Syntax_: ! `RESULT = PRECISION(X)' _Arguments_: ! X Shall be of type `REAL' or `COMPLEX'. _Return value_: ! The return value is of type `INTEGER' and of the default integer kind. _See also_: *************** _Example_: *** 14652,14658 ****  File: gfortran.info, Node: PRESENT, Next: PRODUCT, Prev: PRECISION, Up: Intrinsic Procedures ! 9.210 'PRESENT' -- Determine whether an optional dummy argument is specified ============================================================================ _Description_: --- 14804,14810 ----  File: gfortran.info, Node: PRESENT, Next: PRODUCT, Prev: PRECISION, Up: Intrinsic Procedures ! 9.210 `PRESENT' -- Determine whether an optional dummy argument is specified ============================================================================ _Description_: *************** _Class_: *** 14665,14682 **** Inquiry function _Syntax_: ! 'RESULT = PRESENT(A)' _Arguments_: ! A May be of any type and may be a pointer, scalar ! or array value, or a dummy procedure. It shall ! be the name of an optional dummy argument ! accessible within the current subroutine or ! function. _Return value_: ! Returns either 'TRUE' if the optional argument A is present, or ! 'FALSE' otherwise. _Example_: PROGRAM test_present --- 14817,14834 ---- Inquiry function _Syntax_: ! `RESULT = PRESENT(A)' _Arguments_: ! A May be of any type and may be a pointer, ! scalar or array value, or a dummy procedure. ! It shall be the name of an optional dummy ! argument accessible within the current ! subroutine or function. _Return value_: ! Returns either `TRUE' if the optional argument A is present, or ! `FALSE' otherwise. _Example_: PROGRAM test_present *************** _Example_: *** 14691,14702 ****  File: gfortran.info, Node: PRODUCT, Next: RADIX, Prev: PRESENT, Up: Intrinsic Procedures ! 9.211 'PRODUCT' -- Product of array elements ============================================ _Description_: Multiplies the elements of ARRAY along dimension DIM if the ! corresponding element in MASK is 'TRUE'. _Standard_: Fortran 95 and later --- 14843,14854 ----  File: gfortran.info, Node: PRODUCT, Next: RADIX, Prev: PRESENT, Up: Intrinsic Procedures ! 9.211 `PRODUCT' -- Product of array elements ============================================ _Description_: Multiplies the elements of ARRAY along dimension DIM if the ! corresponding element in MASK is `TRUE'. _Standard_: Fortran 95 and later *************** _Class_: *** 14705,14728 **** Transformational function _Syntax_: ! 'RESULT = PRODUCT(ARRAY[, MASK])' ! 'RESULT = PRODUCT(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER', 'REAL' or ! 'COMPLEX'. ! DIM (Optional) shall be a scalar of type 'INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type 'LOGICAL' and either ! be a scalar or an array of the same shape as ! ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the product of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. --- 14857,14880 ---- Transformational function _Syntax_: ! `RESULT = PRODUCT(ARRAY[, MASK])' ! `RESULT = PRODUCT(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER', `REAL' or ! `COMPLEX'. ! DIM (Optional) shall be a scalar of type `INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type `LOGICAL' and ! either be a scalar or an array of the same ! shape as ARRAY. _Return value_: The result is of the same type as ARRAY. If DIM is absent, a scalar with the product of all elements in ! ARRAY is returned. Otherwise, an array of rank n-1, where n equals the rank of ARRAY, and a shape similar to that of ARRAY with dimension DIM dropped is returned. *************** _See also_: *** 14739,14749 ****  File: gfortran.info, Node: RADIX, Next: RAN, Prev: PRODUCT, Up: Intrinsic Procedures ! 9.212 'RADIX' -- Base of a model number ======================================= _Description_: ! 'RADIX(X)' returns the base of the model representing the entity X. _Standard_: Fortran 95 and later --- 14891,14901 ----  File: gfortran.info, Node: RADIX, Next: RAN, Prev: PRODUCT, Up: Intrinsic Procedures ! 9.212 `RADIX' -- Base of a model number ======================================= _Description_: ! `RADIX(X)' returns the base of the model representing the entity X. _Standard_: Fortran 95 and later *************** _Class_: *** 14752,14764 **** Inquiry function _Syntax_: ! 'RESULT = RADIX(X)' _Arguments_: ! X Shall be of type 'INTEGER' or 'REAL' _Return value_: ! The return value is a scalar of type 'INTEGER' and of the default integer kind. _See also_: --- 14904,14916 ---- Inquiry function _Syntax_: ! `RESULT = RADIX(X)' _Arguments_: ! X Shall be of type `INTEGER' or `REAL' _Return value_: ! The return value is a scalar of type `INTEGER' and of the default integer kind. _See also_: *************** _Example_: *** 14770,14784 **** print *, "The radix for the default real kind is", radix(0.0) end program test_radix  File: gfortran.info, Node: RAN, Next: RAND, Prev: RADIX, Up: Intrinsic Procedures ! 9.213 'RAN' -- Real pseudo-random number ======================================== _Description_: ! For compatibility with HP FORTRAN 77/iX, the 'RAN' intrinsic is ! provided as an alias for 'RAND'. See *note RAND:: for complete documentation. _Standard_: --- 14922,14937 ---- print *, "The radix for the default real kind is", radix(0.0) end program test_radix +  File: gfortran.info, Node: RAN, Next: RAND, Prev: RADIX, Up: Intrinsic Procedures ! 9.213 `RAN' -- Real pseudo-random number ======================================== _Description_: ! For compatibility with HP FORTRAN 77/iX, the `RAN' intrinsic is ! provided as an alias for `RAND'. See *note RAND:: for complete documentation. _Standard_: *************** _See also_: *** 14793,14812 ****  File: gfortran.info, Node: RAND, Next: RANDOM_NUMBER, Prev: RAN, Up: Intrinsic Procedures ! 9.214 'RAND' -- Real pseudo-random number ========================================= _Description_: ! 'RAND(FLAG)' returns a pseudo-random number from a uniform ! distribution between 0 and 1. If FLAG is 0, the next number in the current sequence is returned; if FLAG is 1, the generator is ! restarted by 'CALL SRAND(0)'; if FLAG has any other value, it is ! used as a new seed with 'SRAND'. This intrinsic routine is provided for backwards compatibility with ! GNU Fortran 77. It implements a simple modulo generator as ! provided by 'g77'. For new code, one should consider the use of ! *note RANDOM_NUMBER:: as it implements a superior algorithm. _Standard_: GNU extension --- 14946,14965 ----  File: gfortran.info, Node: RAND, Next: RANDOM_NUMBER, Prev: RAN, Up: Intrinsic Procedures ! 9.214 `RAND' -- Real pseudo-random number ========================================= _Description_: ! `RAND(FLAG)' returns a pseudo-random number from a uniform ! distribution between 0 and 1. If FLAG is 0, the next number in the current sequence is returned; if FLAG is 1, the generator is ! restarted by `CALL SRAND(0)'; if FLAG has any other value, it is ! used as a new seed with `SRAND'. This intrinsic routine is provided for backwards compatibility with ! GNU Fortran 77. It implements a simple modulo generator as provided ! by `g77'. For new code, one should consider the use of *note ! RANDOM_NUMBER:: as it implements a superior algorithm. _Standard_: GNU extension *************** _Class_: *** 14815,14827 **** Function _Syntax_: ! 'RESULT = RAND(I)' _Arguments_: ! I Shall be a scalar 'INTEGER' of kind 4. _Return value_: ! The return value is of 'REAL' type and the default kind. _Example_: program test_rand --- 14968,14980 ---- Function _Syntax_: ! `RESULT = RAND(I)' _Arguments_: ! I Shall be a scalar `INTEGER' of kind 4. _Return value_: ! The return value is of `REAL' type and the default kind. _Example_: program test_rand *************** _Example_: *** 14835,14867 **** _See also_: *note SRAND::, *note RANDOM_NUMBER::  File: gfortran.info, Node: RANDOM_NUMBER, Next: RANDOM_SEED, Prev: RAND, Up: Intrinsic Procedures ! 9.215 'RANDOM_NUMBER' -- Pseudo-random number ============================================= _Description_: Returns a single pseudorandom number or an array of pseudorandom ! numbers from the uniform distribution over the range 0 \leq x < 1. The runtime-library implements George Marsaglia's KISS (Keep It Simple Stupid) random number generator (RNG). This RNG combines: 1. The congruential generator x(n) = 69069 \cdot x(n-1) + ! 1327217885 with a period of 2^{32}, ! 2. A 3-shift shift-register generator with a period of 2^{32} - ! 1, 3. Two 16-bit multiply-with-carry generators with a period of ! 597273182964842497 > 2^{59}. ! The overall period exceeds 2^{123}. Please note, this RNG is thread safe if used within OpenMP directives, i.e., its state will be consistent while called from multiple threads. However, the KISS generator does not create random numbers in parallel from multiple sources, but in sequence ! from a single source. If an OpenMP-enabled application heavily ! relies on random numbers, one should consider employing a dedicated ! parallel random number generator instead. _Standard_: Fortran 95 and later --- 14988,15022 ---- _See also_: *note SRAND::, *note RANDOM_NUMBER:: +  File: gfortran.info, Node: RANDOM_NUMBER, Next: RANDOM_SEED, Prev: RAND, Up: Intrinsic Procedures ! 9.215 `RANDOM_NUMBER' -- Pseudo-random number ============================================= _Description_: Returns a single pseudorandom number or an array of pseudorandom ! numbers from the uniform distribution over the range 0 \leq x < 1. The runtime-library implements George Marsaglia's KISS (Keep It Simple Stupid) random number generator (RNG). This RNG combines: 1. The congruential generator x(n) = 69069 \cdot x(n-1) + ! 1327217885 with a period of 2^32, ! ! 2. A 3-shift shift-register generator with a period of 2^32 - 1, ! 3. Two 16-bit multiply-with-carry generators with a period of ! 597273182964842497 > 2^59. ! The overall period exceeds 2^123. Please note, this RNG is thread safe if used within OpenMP directives, i.e., its state will be consistent while called from multiple threads. However, the KISS generator does not create random numbers in parallel from multiple sources, but in sequence ! from a single source. If an OpenMP-enabled application heavily ! relies on random numbers, one should consider employing a ! dedicated parallel random number generator instead. _Standard_: Fortran 95 and later *************** _Class_: *** 14870,14879 **** Subroutine _Syntax_: ! 'RANDOM_NUMBER(HARVEST)' _Arguments_: ! HARVEST Shall be a scalar or an array of type 'REAL'. _Example_: program test_random_number --- 15025,15034 ---- Subroutine _Syntax_: ! `RANDOM_NUMBER(HARVEST)' _Arguments_: ! HARVEST Shall be a scalar or an array of type `REAL'. _Example_: program test_random_number *************** _See also_: *** 14888,14906 ****  File: gfortran.info, Node: RANDOM_SEED, Next: RANGE, Prev: RANDOM_NUMBER, Up: Intrinsic Procedures ! 9.216 'RANDOM_SEED' -- Initialize a pseudo-random number sequence ================================================================= _Description_: Restarts or queries the state of the pseudorandom number generator ! used by 'RANDOM_NUMBER'. ! If 'RANDOM_SEED' is called without arguments, it is initialized to ! a default state. The example below shows how to initialize the random seed with a varying seed in order to ensure a different ! random number sequence for each invocation of the program. Note ! that setting any of the seed values to zero should be avoided as it ! can result in poor quality random numbers being generated. _Standard_: Fortran 95 and later --- 15043,15061 ----  File: gfortran.info, Node: RANDOM_SEED, Next: RANGE, Prev: RANDOM_NUMBER, Up: Intrinsic Procedures ! 9.216 `RANDOM_SEED' -- Initialize a pseudo-random number sequence ================================================================= _Description_: Restarts or queries the state of the pseudorandom number generator ! used by `RANDOM_NUMBER'. ! If `RANDOM_SEED' is called without arguments, it is initialized to ! a default state. The example below shows how to initialize the random seed with a varying seed in order to ensure a different ! random number sequence for each invocation of the program. Note ! that setting any of the seed values to zero should be avoided as ! it can result in poor quality random numbers being generated. _Standard_: Fortran 95 and later *************** _Class_: *** 14909,14931 **** Subroutine _Syntax_: ! 'CALL RANDOM_SEED([SIZE, PUT, GET])' _Arguments_: ! SIZE (Optional) Shall be a scalar and of type default ! 'INTEGER', with 'INTENT(OUT)'. It specifies the ! minimum size of the arrays used with the PUT and ! GET arguments. ! PUT (Optional) Shall be an array of type default ! 'INTEGER' and rank one. It is 'INTENT(IN)' and ! the size of the array must be larger than or ! equal to the number returned by the SIZE ! argument. ! GET (Optional) Shall be an array of type default ! 'INTEGER' and rank one. It is 'INTENT(OUT)' and ! the size of the array must be larger than or ! equal to the number returned by the SIZE ! argument. _Example_: subroutine init_random_seed() --- 15064,15086 ---- Subroutine _Syntax_: ! `CALL RANDOM_SEED([SIZE, PUT, GET])' _Arguments_: ! SIZE (Optional) Shall be a scalar and of type ! default `INTEGER', with `INTENT(OUT)'. It ! specifies the minimum size of the arrays used ! with the PUT and GET arguments. ! PUT (Optional) Shall be an array of type default ! `INTEGER' and rank one. It is `INTENT(IN)' and ! the size of the array must be larger than or ! equal to the number returned by the SIZE ! argument. ! GET (Optional) Shall be an array of type default ! `INTEGER' and rank one. It is `INTENT(OUT)' ! and the size of the array must be larger than ! or equal to the number returned by the SIZE ! argument. _Example_: subroutine init_random_seed() *************** _See also_: *** 14986,14997 ****  File: gfortran.info, Node: RANGE, Next: RANK, Prev: RANDOM_SEED, Up: Intrinsic Procedures ! 9.217 'RANGE' -- Decimal exponent range ======================================= _Description_: ! 'RANGE(X)' returns the decimal exponent range in the model of the ! type of 'X'. _Standard_: Fortran 95 and later --- 15141,15152 ----  File: gfortran.info, Node: RANGE, Next: RANK, Prev: RANDOM_SEED, Up: Intrinsic Procedures ! 9.217 `RANGE' -- Decimal exponent range ======================================= _Description_: ! `RANGE(X)' returns the decimal exponent range in the model of the ! type of `X'. _Standard_: Fortran 95 and later *************** _Class_: *** 15000,15028 **** Inquiry function _Syntax_: ! 'RESULT = RANGE(X)' _Arguments_: ! X Shall be of type 'INTEGER', 'REAL' or 'COMPLEX'. _Return value_: ! The return value is of type 'INTEGER' and of the default integer kind. _See also_: *note SELECTED_REAL_KIND::, *note PRECISION:: _Example_: ! See 'PRECISION' for an example.  File: gfortran.info, Node: RANK, Next: REAL, Prev: RANGE, Up: Intrinsic Procedures ! 9.218 'RANK' -- Rank of a data object ===================================== _Description_: ! 'RANK(A)' returns the rank of a scalar or array data object. _Standard_: Technical Specification (TS) 29113 --- 15155,15184 ---- Inquiry function _Syntax_: ! `RESULT = RANGE(X)' _Arguments_: ! X Shall be of type `INTEGER', `REAL' or ! `COMPLEX'. _Return value_: ! The return value is of type `INTEGER' and of the default integer kind. _See also_: *note SELECTED_REAL_KIND::, *note PRECISION:: _Example_: ! See `PRECISION' for an example.  File: gfortran.info, Node: RANK, Next: REAL, Prev: RANGE, Up: Intrinsic Procedures ! 9.218 `RANK' -- Rank of a data object ===================================== _Description_: ! `RANK(A)' returns the rank of a scalar or array data object. _Standard_: Technical Specification (TS) 29113 *************** _Class_: *** 15031,15044 **** Inquiry function _Syntax_: ! 'RESULT = RANK(A)' _Arguments_: ! A can be of any type _Return value_: ! The return value is of type 'INTEGER' and of the default integer ! kind. For arrays, their rank is returned; for scalars zero is returned. _Example_: --- 15187,15200 ---- Inquiry function _Syntax_: ! `RESULT = RANK(A)' _Arguments_: ! A can be of any type _Return value_: ! The return value is of type `INTEGER' and of the default integer ! kind. For arrays, their rank is returned; for scalars zero is returned. _Example_: *************** _Example_: *** 15049,15063 **** print *, rank(a), rank(b) ! Prints: 0 2 end program test_rank  File: gfortran.info, Node: REAL, Next: RENAME, Prev: RANK, Up: Intrinsic Procedures ! 9.219 'REAL' -- Convert to real type ==================================== _Description_: ! 'REAL(A [, KIND])' converts its argument A to a real type. The ! 'REALPART' function is provided for compatibility with 'g77', and its use is strongly discouraged. _Standard_: --- 15205,15220 ---- print *, rank(a), rank(b) ! Prints: 0 2 end program test_rank +  File: gfortran.info, Node: REAL, Next: RENAME, Prev: RANK, Up: Intrinsic Procedures ! 9.219 `REAL' -- Convert to real type ==================================== _Description_: ! `REAL(A [, KIND])' converts its argument A to a real type. The ! `REALPART' function is provided for compatibility with `g77', and its use is strongly discouraged. _Standard_: *************** _Class_: *** 15067,15093 **** Elemental function _Syntax_: ! 'RESULT = REAL(A [, KIND])' ! 'RESULT = REALPART(Z)' _Arguments_: ! A Shall be 'INTEGER', 'REAL', or 'COMPLEX'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! These functions return a 'REAL' variable or array under the following rules: ! (A) ! 'REAL(A)' is converted to a default real type if A is an integer or real variable. ! (B) ! 'REAL(A)' is converted to a real type with the kind type parameter of A if A is a complex variable. ! (C) ! 'REAL(A, KIND)' is converted to a real type with kind type parameter KIND if A is a complex, integer, or real variable. _Example_: --- 15224,15252 ---- Elemental function _Syntax_: ! `RESULT = REAL(A [, KIND])' ! `RESULT = REALPART(Z)' _Arguments_: ! A Shall be `INTEGER', `REAL', or `COMPLEX'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! These functions return a `REAL' variable or array under the following rules: ! (A) ! `REAL(A)' is converted to a default real type if A is an integer or real variable. ! ! (B) ! `REAL(A)' is converted to a real type with the kind type parameter of A if A is a complex variable. ! ! (C) ! `REAL(A, KIND)' is converted to a real type with kind type parameter KIND if A is a complex, integer, or real variable. _Example_: *************** _Example_: *** 15097,15124 **** end program test_real _Specific names_: ! Name Argument Return type Standard ! 'FLOAT(A)' 'INTEGER(4)' 'REAL(4)' Fortran 77 and ! later ! 'DFLOAT(A)' 'INTEGER(4)' 'REAL(8)' GNU extension ! 'SNGL(A)' 'INTEGER(8)' 'REAL(4)' Fortran 77 and ! later _See also_: *note DBLE::  File: gfortran.info, Node: RENAME, Next: REPEAT, Prev: REAL, Up: Intrinsic Procedures ! 9.220 'RENAME' -- Rename a file =============================== _Description_: ! Renames a file from file PATH1 to PATH2. A null character ! ('CHAR(0)') can be used to mark the end of the names in PATH1 and PATH2; otherwise, trailing blanks in the file names are ignored. If the STATUS argument is supplied, it contains 0 on success or a ! nonzero error code upon return; see 'rename(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 15256,15284 ---- end program test_real _Specific names_: ! Name Argument Return type Standard ! `FLOAT(A)' `INTEGER(4)' `REAL(4)' Fortran 77 and ! later ! `DFLOAT(A)' `INTEGER(4)' `REAL(8)' GNU extension ! `SNGL(A)' `INTEGER(8)' `REAL(4)' Fortran 77 and ! later _See also_: *note DBLE:: +  File: gfortran.info, Node: RENAME, Next: REPEAT, Prev: REAL, Up: Intrinsic Procedures ! 9.220 `RENAME' -- Rename a file =============================== _Description_: ! Renames a file from file PATH1 to PATH2. A null character ! (`CHAR(0)') can be used to mark the end of the names in PATH1 and PATH2; otherwise, trailing blanks in the file names are ignored. If the STATUS argument is supplied, it contains 0 on success or a ! nonzero error code upon return; see `rename(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 15130,15150 **** Subroutine, function _Syntax_: ! 'CALL RENAME(PATH1, PATH2 [, STATUS])' ! 'STATUS = RENAME(PATH1, PATH2)' _Arguments_: ! PATH1 Shall be of default 'CHARACTER' type. ! PATH2 Shall be of default 'CHARACTER' type. ! STATUS (Optional) Shall be of default 'INTEGER' type. _See also_: *note LINK::  File: gfortran.info, Node: REPEAT, Next: RESHAPE, Prev: RENAME, Up: Intrinsic Procedures ! 9.221 'REPEAT' -- Repeated string concatenation =============================================== _Description_: --- 15290,15311 ---- Subroutine, function _Syntax_: ! `CALL RENAME(PATH1, PATH2 [, STATUS])' ! `STATUS = RENAME(PATH1, PATH2)' _Arguments_: ! PATH1 Shall be of default `CHARACTER' type. ! PATH2 Shall be of default `CHARACTER' type. ! STATUS (Optional) Shall be of default `INTEGER' type. _See also_: *note LINK:: +  File: gfortran.info, Node: REPEAT, Next: RESHAPE, Prev: RENAME, Up: Intrinsic Procedures ! 9.221 `REPEAT' -- Repeated string concatenation =============================================== _Description_: *************** _Class_: *** 15157,15170 **** Transformational function _Syntax_: ! 'RESULT = REPEAT(STRING, NCOPIES)' _Arguments_: ! STRING Shall be scalar and of type 'CHARACTER'. ! NCOPIES Shall be scalar and of type 'INTEGER'. _Return value_: ! A new scalar of type 'CHARACTER' built up from NCOPIES copies of STRING. _Example_: --- 15318,15331 ---- Transformational function _Syntax_: ! `RESULT = REPEAT(STRING, NCOPIES)' _Arguments_: ! STRING Shall be scalar and of type `CHARACTER'. ! NCOPIES Shall be scalar and of type `INTEGER'. _Return value_: ! A new scalar of type `CHARACTER' built up from NCOPIES copies of STRING. _Example_: *************** _Example_: *** 15175,15185 ****  File: gfortran.info, Node: RESHAPE, Next: RRSPACING, Prev: REPEAT, Up: Intrinsic Procedures ! 9.222 'RESHAPE' -- Function to reshape an array =============================================== _Description_: ! Reshapes SOURCE to correspond to SHAPE. If necessary, the new array may be padded with elements from PAD or permuted as defined by ORDER. --- 15336,15346 ----  File: gfortran.info, Node: RESHAPE, Next: RRSPACING, Prev: REPEAT, Up: Intrinsic Procedures ! 9.222 `RESHAPE' -- Function to reshape an array =============================================== _Description_: ! Reshapes SOURCE to correspond to SHAPE. If necessary, the new array may be padded with elements from PAD or permuted as defined by ORDER. *************** _Class_: *** 15190,15208 **** Transformational function _Syntax_: ! 'RESULT = RESHAPE(SOURCE, SHAPE[, PAD, ORDER])' _Arguments_: ! SOURCE Shall be an array of any type. ! SHAPE Shall be of type 'INTEGER' and an array of rank ! one. Its values must be positive or zero. ! PAD (Optional) shall be an array of the same type as ! SOURCE. ! ORDER (Optional) shall be of type 'INTEGER' and an ! array of the same shape as SHAPE. Its values ! shall be a permutation of the numbers from 1 to ! n, where n is the size of SHAPE. If ORDER is ! absent, the natural ordering shall be assumed. _Return value_: The result is an array of shape SHAPE with the same type as SOURCE. --- 15351,15370 ---- Transformational function _Syntax_: ! `RESULT = RESHAPE(SOURCE, SHAPE[, PAD, ORDER])' _Arguments_: ! SOURCE Shall be an array of any type. ! SHAPE Shall be of type `INTEGER' and an array of ! rank one. Its values must be positive or zero. ! PAD (Optional) shall be an array of the same type ! as SOURCE. ! ORDER (Optional) shall be of type `INTEGER' and an ! array of the same shape as SHAPE. Its values ! shall be a permutation of the numbers from 1 ! to n, where n is the size of SHAPE. If ORDER ! is absent, the natural ordering shall be ! assumed. _Return value_: The result is an array of shape SHAPE with the same type as SOURCE. *************** _See also_: *** 15220,15230 ****  File: gfortran.info, Node: RRSPACING, Next: RSHIFT, Prev: RESHAPE, Up: Intrinsic Procedures ! 9.223 'RRSPACING' -- Reciprocal of the relative spacing ======================================================= _Description_: ! 'RRSPACING(X)' returns the reciprocal of the relative spacing of model numbers near X. _Standard_: --- 15382,15392 ----  File: gfortran.info, Node: RRSPACING, Next: RSHIFT, Prev: RESHAPE, Up: Intrinsic Procedures ! 9.223 `RRSPACING' -- Reciprocal of the relative spacing ======================================================= _Description_: ! `RRSPACING(X)' returns the reciprocal of the relative spacing of model numbers near X. _Standard_: *************** _Class_: *** 15234,15247 **** Elemental function _Syntax_: ! 'RESULT = RRSPACING(X)' _Arguments_: ! X Shall be of type 'REAL'. _Return value_: The return value is of the same type and kind as X. The value ! returned is equal to 'ABS(FRACTION(X)) * FLOAT(RADIX(X))**DIGITS(X)'. _See also_: --- 15396,15409 ---- Elemental function _Syntax_: ! `RESULT = RRSPACING(X)' _Arguments_: ! X Shall be of type `REAL'. _Return value_: The return value is of the same type and kind as X. The value ! returned is equal to `ABS(FRACTION(X)) * FLOAT(RADIX(X))**DIGITS(X)'. _See also_: *************** _See also_: *** 15250,15267 ****  File: gfortran.info, Node: RSHIFT, Next: SAME_TYPE_AS, Prev: RRSPACING, Up: Intrinsic Procedures ! 9.224 'RSHIFT' -- Right shift bits ================================== _Description_: ! 'RSHIFT' returns a value corresponding to I with all of the bits shifted right by SHIFT places. If the absolute value of SHIFT is ! greater than 'BIT_SIZE(I)', the value is undefined. Bits shifted ! out from the right end are lost. The fill is arithmetic: the bits shifted in from the left end are equal to the leftmost bit, which in two's complement representation is the sign bit. ! This function has been superseded by the 'SHIFTA' intrinsic, which is standard in Fortran 2008 and later. _Standard_: --- 15412,15429 ----  File: gfortran.info, Node: RSHIFT, Next: SAME_TYPE_AS, Prev: RRSPACING, Up: Intrinsic Procedures ! 9.224 `RSHIFT' -- Right shift bits ================================== _Description_: ! `RSHIFT' returns a value corresponding to I with all of the bits shifted right by SHIFT places. If the absolute value of SHIFT is ! greater than `BIT_SIZE(I)', the value is undefined. Bits shifted ! out from the right end are lost. The fill is arithmetic: the bits shifted in from the left end are equal to the leftmost bit, which in two's complement representation is the sign bit. ! This function has been superseded by the `SHIFTA' intrinsic, which is standard in Fortran 2008 and later. _Standard_: *************** _Class_: *** 15271,15294 **** Elemental function _Syntax_: ! 'RESULT = RSHIFT(I, SHIFT)' _Arguments_: ! I The type shall be 'INTEGER'. ! SHIFT The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note ISHFT::, *note ISHFTC::, *note LSHIFT::, *note SHIFTA::, *note SHIFTR::, *note SHIFTL::  File: gfortran.info, Node: SAME_TYPE_AS, Next: SCALE, Prev: RSHIFT, Up: Intrinsic Procedures ! 9.225 'SAME_TYPE_AS' -- Query dynamic types for equality ! ======================================================== _Description_: Query dynamic types for equality. --- 15433,15457 ---- Elemental function _Syntax_: ! `RESULT = RSHIFT(I, SHIFT)' _Arguments_: ! I The type shall be `INTEGER'. ! SHIFT The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note ISHFT::, *note ISHFTC::, *note LSHIFT::, *note SHIFTA::, *note SHIFTR::, *note SHIFTL:: +  File: gfortran.info, Node: SAME_TYPE_AS, Next: SCALE, Prev: RSHIFT, Up: Intrinsic Procedures ! 9.225 `SAME_TYPE_AS' -- Query dynamic types for equality ! ========================================================= _Description_: Query dynamic types for equality. *************** _Class_: *** 15300,15329 **** Inquiry function _Syntax_: ! 'RESULT = SAME_TYPE_AS(A, B)' _Arguments_: ! A Shall be an object of extensible declared type ! or unlimited polymorphic. ! B Shall be an object of extensible declared type ! or unlimited polymorphic. _Return value_: ! The return value is a scalar of type default logical. It is true if and only if the dynamic type of A is the same as the dynamic type of B. _See also_: *note EXTENDS_TYPE_OF::  File: gfortran.info, Node: SCALE, Next: SCAN, Prev: SAME_TYPE_AS, Up: Intrinsic Procedures ! 9.226 'SCALE' -- Scale a real value =================================== _Description_: ! 'SCALE(X,I)' returns 'X * RADIX(X)**I'. _Standard_: Fortran 95 and later --- 15463,15493 ---- Inquiry function _Syntax_: ! `RESULT = SAME_TYPE_AS(A, B)' _Arguments_: ! A Shall be an object of extensible declared type ! or unlimited polymorphic. ! B Shall be an object of extensible declared type ! or unlimited polymorphic. _Return value_: ! The return value is a scalar of type default logical. It is true if and only if the dynamic type of A is the same as the dynamic type of B. _See also_: *note EXTENDS_TYPE_OF:: +  File: gfortran.info, Node: SCALE, Next: SCAN, Prev: SAME_TYPE_AS, Up: Intrinsic Procedures ! 9.226 `SCALE' -- Scale a real value =================================== _Description_: ! `SCALE(X,I)' returns `X * RADIX(X)**I'. _Standard_: Fortran 95 and later *************** _Class_: *** 15332,15346 **** Elemental function _Syntax_: ! 'RESULT = SCALE(X, I)' _Arguments_: ! X The type of the argument shall be a 'REAL'. ! I The type of the argument shall be a 'INTEGER'. _Return value_: The return value is of the same type and kind as X. Its value is ! 'X * RADIX(X)**I'. _Example_: program test_scale --- 15496,15510 ---- Elemental function _Syntax_: ! `RESULT = SCALE(X, I)' _Arguments_: ! X The type of the argument shall be a `REAL'. ! I The type of the argument shall be a `INTEGER'. _Return value_: The return value is of the same type and kind as X. Its value is ! `X * RADIX(X)**I'. _Example_: program test_scale *************** _Example_: *** 15349,15366 **** print *, scale(x,i), x*radix(x)**i end program test_scale  File: gfortran.info, Node: SCAN, Next: SECNDS, Prev: SCALE, Up: Intrinsic Procedures ! 9.227 'SCAN' -- Scan a string for the presence of a set of characters ===================================================================== _Description_: Scans a STRING for any of the characters in a SET of characters. ! If BACK is either absent or equals 'FALSE', this function returns the position of the leftmost character of STRING that is in SET. ! If BACK equals 'TRUE', the rightmost position is returned. If no character of SET is found in STRING, the result is zero. _Standard_: --- 15513,15531 ---- print *, scale(x,i), x*radix(x)**i end program test_scale +  File: gfortran.info, Node: SCAN, Next: SECNDS, Prev: SCALE, Up: Intrinsic Procedures ! 9.227 `SCAN' -- Scan a string for the presence of a set of characters ===================================================================== _Description_: Scans a STRING for any of the characters in a SET of characters. ! If BACK is either absent or equals `FALSE', this function returns the position of the leftmost character of STRING that is in SET. ! If BACK equals `TRUE', the rightmost position is returned. If no character of SET is found in STRING, the result is zero. _Standard_: *************** _Class_: *** 15370,15387 **** Elemental function _Syntax_: ! 'RESULT = SCAN(STRING, SET[, BACK [, KIND]])' _Arguments_: ! STRING Shall be of type 'CHARACTER'. ! SET Shall be of type 'CHARACTER'. ! BACK (Optional) shall be of type 'LOGICAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: --- 15535,15552 ---- Elemental function _Syntax_: ! `RESULT = SCAN(STRING, SET[, BACK [, KIND]])' _Arguments_: ! STRING Shall be of type `CHARACTER'. ! SET Shall be of type `CHARACTER'. ! BACK (Optional) shall be of type `LOGICAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: *************** _See also_: *** 15397,15409 ****  File: gfortran.info, Node: SECNDS, Next: SECOND, Prev: SCAN, Up: Intrinsic Procedures ! 9.228 'SECNDS' -- Time function =============================== _Description_: ! 'SECNDS(X)' gets the time in seconds from the real-time system ! clock. X is a reference time, also in seconds. If this is zero, ! the time in seconds from midnight is returned. This function is non-standard and its use is discouraged. _Standard_: --- 15562,15574 ----  File: gfortran.info, Node: SECNDS, Next: SECOND, Prev: SCAN, Up: Intrinsic Procedures ! 9.228 `SECNDS' -- Time function =============================== _Description_: ! `SECNDS(X)' gets the time in seconds from the real-time system ! clock. X is a reference time, also in seconds. If this is zero, ! the time in seconds from midnight is returned. This function is non-standard and its use is discouraged. _Standard_: *************** _Class_: *** 15413,15423 **** Function _Syntax_: ! 'RESULT = SECNDS (X)' _Arguments_: ! T Shall be of type 'REAL(4)'. ! X Shall be of type 'REAL(4)'. _Return value_: None --- 15578,15588 ---- Function _Syntax_: ! `RESULT = SECNDS (X)' _Arguments_: ! T Shall be of type `REAL(4)'. ! X Shall be of type `REAL(4)'. _Return value_: None *************** _Example_: *** 15437,15449 ****  File: gfortran.info, Node: SECOND, Next: SELECTED_CHAR_KIND, Prev: SECNDS, Up: Intrinsic Procedures ! 9.229 'SECOND' -- CPU time function =================================== _Description_: ! Returns a 'REAL(4)' value representing the elapsed CPU time in seconds. This provides the same functionality as the standard ! 'CPU_TIME' intrinsic, and is only included for backwards compatibility. This intrinsic is provided in both subroutine and function forms; --- 15602,15614 ----  File: gfortran.info, Node: SECOND, Next: SELECTED_CHAR_KIND, Prev: SECNDS, Up: Intrinsic Procedures ! 9.229 `SECOND' -- CPU time function =================================== _Description_: ! Returns a `REAL(4)' value representing the elapsed CPU time in seconds. This provides the same functionality as the standard ! `CPU_TIME' intrinsic, and is only included for backwards compatibility. This intrinsic is provided in both subroutine and function forms; *************** _Class_: *** 15456,15466 **** Subroutine, function _Syntax_: ! 'CALL SECOND(TIME)' ! 'TIME = SECOND()' _Arguments_: ! TIME Shall be of type 'REAL(4)'. _Return value_: In either syntax, TIME is set to the process's current runtime in --- 15621,15631 ---- Subroutine, function _Syntax_: ! `CALL SECOND(TIME)' ! `TIME = SECOND()' _Arguments_: ! TIME Shall be of type `REAL(4)'. _Return value_: In either syntax, TIME is set to the process's current runtime in *************** _Return value_: *** 15469,15485 **** _See also_: *note CPU_TIME::  File: gfortran.info, Node: SELECTED_CHAR_KIND, Next: SELECTED_INT_KIND, Prev: SECOND, Up: Intrinsic Procedures ! 9.230 'SELECTED_CHAR_KIND' -- Choose character kind =================================================== _Description_: ! ! 'SELECTED_CHAR_KIND(NAME)' returns the kind value for the character set named NAME, if a character set with such a name is supported, ! or -1 otherwise. Currently, supported character sets include "ASCII" and "DEFAULT", which are equivalent, and "ISO_10646" (Universal Character Set, UCS-4) which is commonly known as Unicode. --- 15634,15650 ---- _See also_: *note CPU_TIME:: +  File: gfortran.info, Node: SELECTED_CHAR_KIND, Next: SELECTED_INT_KIND, Prev: SECOND, Up: Intrinsic Procedures ! 9.230 `SELECTED_CHAR_KIND' -- Choose character kind =================================================== _Description_: ! `SELECTED_CHAR_KIND(NAME)' returns the kind value for the character set named NAME, if a character set with such a name is supported, ! or -1 otherwise. Currently, supported character sets include "ASCII" and "DEFAULT", which are equivalent, and "ISO_10646" (Universal Character Set, UCS-4) which is commonly known as Unicode. *************** _Class_: *** 15491,15501 **** Transformational function _Syntax_: ! 'RESULT = SELECTED_CHAR_KIND(NAME)' _Arguments_: ! NAME Shall be a scalar and of the default character ! type. _Example_: program character_kind --- 15656,15666 ---- Transformational function _Syntax_: ! `RESULT = SELECTED_CHAR_KIND(NAME)' _Arguments_: ! NAME Shall be a scalar and of the default character ! type. _Example_: program character_kind *************** _Example_: *** 15521,15534 ****  File: gfortran.info, Node: SELECTED_INT_KIND, Next: SELECTED_REAL_KIND, Prev: SELECTED_CHAR_KIND, Up: Intrinsic Procedures ! 9.231 'SELECTED_INT_KIND' -- Choose integer kind ================================================ _Description_: ! 'SELECTED_INT_KIND(R)' return the kind value of the smallest integer type that can represent all values ranging from -10^R ! (exclusive) to 10^R (exclusive). If there is no integer kind that ! accommodates this range, 'SELECTED_INT_KIND' returns -1. _Standard_: Fortran 95 and later --- 15686,15699 ----  File: gfortran.info, Node: SELECTED_INT_KIND, Next: SELECTED_REAL_KIND, Prev: SELECTED_CHAR_KIND, Up: Intrinsic Procedures ! 9.231 `SELECTED_INT_KIND' -- Choose integer kind ================================================ _Description_: ! `SELECTED_INT_KIND(R)' return the kind value of the smallest integer type that can represent all values ranging from -10^R ! (exclusive) to 10^R (exclusive). If there is no integer kind that ! accommodates this range, `SELECTED_INT_KIND' returns -1. _Standard_: Fortran 95 and later *************** _Class_: *** 15537,15546 **** Transformational function _Syntax_: ! 'RESULT = SELECTED_INT_KIND(R)' _Arguments_: ! R Shall be a scalar and of type 'INTEGER'. _Example_: program large_integers --- 15702,15711 ---- Transformational function _Syntax_: ! `RESULT = SELECTED_INT_KIND(R)' _Arguments_: ! R Shall be a scalar and of type `INTEGER'. _Example_: program large_integers *************** _Example_: *** 15559,15612 ****  File: gfortran.info, Node: SELECTED_REAL_KIND, Next: SET_EXPONENT, Prev: SELECTED_INT_KIND, Up: Intrinsic Procedures ! 9.232 'SELECTED_REAL_KIND' -- Choose real kind ============================================== _Description_: ! 'SELECTED_REAL_KIND(P,R)' returns the kind value of a real data ! type with decimal precision of at least 'P' digits, exponent range ! of at least 'R', and with a radix of 'RADIX'. _Standard_: ! Fortran 95 and later, with 'RADIX' Fortran 2008 or later _Class_: Transformational function _Syntax_: ! 'RESULT = SELECTED_REAL_KIND([P, R, RADIX])' _Arguments_: ! P (Optional) shall be a scalar and of type ! 'INTEGER'. ! R (Optional) shall be a scalar and of type ! 'INTEGER'. ! RADIX (Optional) shall be a scalar and of type ! 'INTEGER'. Before Fortran 2008, at least one of the arguments R or P shall be present; since Fortran 2008, they are assumed to be zero if absent. _Return value_: ! ! 'SELECTED_REAL_KIND' returns the value of the kind type parameter ! of a real data type with decimal precision of at least 'P' digits, ! a decimal exponent range of at least 'R', and with the requested ! 'RADIX'. If the 'RADIX' parameter is absent, real kinds with any ! radix can be returned. If more than one real data type meet the criteria, the kind of the data type with the smallest decimal ! precision is returned. If no real data type matches the criteria, the result is ! -1 if the processor does not support a real data type with a ! precision greater than or equal to 'P', but the 'R' and ! 'RADIX' requirements can be fulfilled ! -2 if the processor does not support a real type with an exponent ! range greater than or equal to 'R', but 'P' and 'RADIX' are fulfillable ! -3 if 'RADIX' but not 'P' and 'R' requirements are fulfillable ! -4 if 'RADIX' and either 'P' or 'R' requirements are fulfillable ! -5 if there is no real type with the given 'RADIX' _See also_: *note PRECISION::, *note RANGE::, *note RADIX:: --- 15724,15780 ----  File: gfortran.info, Node: SELECTED_REAL_KIND, Next: SET_EXPONENT, Prev: SELECTED_INT_KIND, Up: Intrinsic Procedures ! 9.232 `SELECTED_REAL_KIND' -- Choose real kind ============================================== _Description_: ! `SELECTED_REAL_KIND(P,R)' returns the kind value of a real data ! type with decimal precision of at least `P' digits, exponent range ! of at least `R', and with a radix of `RADIX'. _Standard_: ! Fortran 95 and later, with `RADIX' Fortran 2008 or later _Class_: Transformational function _Syntax_: ! `RESULT = SELECTED_REAL_KIND([P, R, RADIX])' _Arguments_: ! P (Optional) shall be a scalar and of type ! `INTEGER'. ! R (Optional) shall be a scalar and of type ! `INTEGER'. ! RADIX (Optional) shall be a scalar and of type ! `INTEGER'. Before Fortran 2008, at least one of the arguments R or P shall be present; since Fortran 2008, they are assumed to be zero if absent. _Return value_: ! `SELECTED_REAL_KIND' returns the value of the kind type parameter ! of a real data type with decimal precision of at least `P' digits, ! a decimal exponent range of at least `R', and with the requested ! `RADIX'. If the `RADIX' parameter is absent, real kinds with any ! radix can be returned. If more than one real data type meet the criteria, the kind of the data type with the smallest decimal ! precision is returned. If no real data type matches the criteria, the result is ! -1 if the processor does not support a real data type with a ! precision greater than or equal to `P', but the `R' and ! `RADIX' requirements can be fulfilled ! ! -2 if the processor does not support a real type with an exponent ! range greater than or equal to `R', but `P' and `RADIX' are fulfillable ! ! -3 if `RADIX' but not `P' and `R' requirements are fulfillable ! ! -4 if `RADIX' and either `P' or `R' requirements are fulfillable ! ! -5 if there is no real type with the given `RADIX' _See also_: *note PRECISION::, *note RANGE::, *note RADIX:: *************** _Example_: *** 15628,15638 ****  File: gfortran.info, Node: SET_EXPONENT, Next: SHAPE, Prev: SELECTED_REAL_KIND, Up: Intrinsic Procedures ! 9.233 'SET_EXPONENT' -- Set the exponent of the model ===================================================== _Description_: ! 'SET_EXPONENT(X, I)' returns the real number whose fractional part is that that of X and whose exponent part is I. _Standard_: --- 15796,15806 ----  File: gfortran.info, Node: SET_EXPONENT, Next: SHAPE, Prev: SELECTED_REAL_KIND, Up: Intrinsic Procedures ! 9.233 `SET_EXPONENT' -- Set the exponent of the model ===================================================== _Description_: ! `SET_EXPONENT(X, I)' returns the real number whose fractional part is that that of X and whose exponent part is I. _Standard_: *************** _Class_: *** 15642,15657 **** Elemental function _Syntax_: ! 'RESULT = SET_EXPONENT(X, I)' _Arguments_: ! X Shall be of type 'REAL'. ! I Shall be of type 'INTEGER'. _Return value_: The return value is of the same type and kind as X. The real number whose fractional part is that that of X and whose exponent ! part if I is returned; it is 'FRACTION(X) * RADIX(X)**I'. _Example_: PROGRAM test_setexp --- 15810,15825 ---- Elemental function _Syntax_: ! `RESULT = SET_EXPONENT(X, I)' _Arguments_: ! X Shall be of type `REAL'. ! I Shall be of type `INTEGER'. _Return value_: The return value is of the same type and kind as X. The real number whose fractional part is that that of X and whose exponent ! part if I is returned; it is `FRACTION(X) * RADIX(X)**I'. _Example_: PROGRAM test_setexp *************** _Example_: *** 15660,15669 **** PRINT *, SET_EXPONENT(x, i), FRACTION(x) * RADIX(x)**i END PROGRAM  File: gfortran.info, Node: SHAPE, Next: SHIFTA, Prev: SET_EXPONENT, Up: Intrinsic Procedures ! 9.234 'SHAPE' -- Determine the shape of an array ================================================ _Description_: --- 15828,15838 ---- PRINT *, SET_EXPONENT(x, i), FRACTION(x) * RADIX(x)**i END PROGRAM +  File: gfortran.info, Node: SHAPE, Next: SHIFTA, Prev: SET_EXPONENT, Up: Intrinsic Procedures ! 9.234 `SHAPE' -- Determine the shape of an array ================================================ _Description_: *************** _Class_: *** 15676,15698 **** Inquiry function _Syntax_: ! 'RESULT = SHAPE(SOURCE [, KIND])' _Arguments_: ! SOURCE Shall be an array or scalar of any type. If ! SOURCE is a pointer it must be associated and ! allocatable arrays must be allocated. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! An 'INTEGER' array of rank one with as many elements as SOURCE has ! dimensions. The elements of the resulting array correspond to the ! extend of SOURCE along the respective dimensions. If SOURCE is a ! scalar, the result is the rank one array of size zero. If KIND is ! absent, the return value has the default integer kind otherwise the ! specified kind. _Example_: PROGRAM test_shape --- 15845,15867 ---- Inquiry function _Syntax_: ! `RESULT = SHAPE(SOURCE [, KIND])' _Arguments_: ! SOURCE Shall be an array or scalar of any type. If ! SOURCE is a pointer it must be associated and ! allocatable arrays must be allocated. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! An `INTEGER' array of rank one with as many elements as SOURCE has ! dimensions. The elements of the resulting array correspond to the ! extend of SOURCE along the respective dimensions. If SOURCE is a ! scalar, the result is the rank one array of size zero. If KIND is ! absent, the return value has the default integer kind otherwise ! the specified kind. _Example_: PROGRAM test_shape *************** _See also_: *** 15707,15720 ****  File: gfortran.info, Node: SHIFTA, Next: SHIFTL, Prev: SHAPE, Up: Intrinsic Procedures ! 9.235 'SHIFTA' -- Right shift with fill ======================================= _Description_: ! 'SHIFTA' returns a value corresponding to I with all of the bits shifted right by SHIFT places. If the absolute value of SHIFT is ! greater than 'BIT_SIZE(I)', the value is undefined. Bits shifted ! out from the right end are lost. The fill is arithmetic: the bits shifted in from the left end are equal to the leftmost bit, which in two's complement representation is the sign bit. --- 15876,15889 ----  File: gfortran.info, Node: SHIFTA, Next: SHIFTL, Prev: SHAPE, Up: Intrinsic Procedures ! 9.235 `SHIFTA' -- Right shift with fill ======================================= _Description_: ! `SHIFTA' returns a value corresponding to I with all of the bits shifted right by SHIFT places. If the absolute value of SHIFT is ! greater than `BIT_SIZE(I)', the value is undefined. Bits shifted ! out from the right end are lost. The fill is arithmetic: the bits shifted in from the left end are equal to the leftmost bit, which in two's complement representation is the sign bit. *************** _Class_: *** 15725,15738 **** Elemental function _Syntax_: ! 'RESULT = SHIFTA(I, SHIFT)' _Arguments_: ! I The type shall be 'INTEGER'. ! SHIFT The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note SHIFTL::, *note SHIFTR:: --- 15894,15907 ---- Elemental function _Syntax_: ! `RESULT = SHIFTA(I, SHIFT)' _Arguments_: ! I The type shall be `INTEGER'. ! SHIFT The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note SHIFTL::, *note SHIFTR:: *************** _See also_: *** 15740,15752 ****  File: gfortran.info, Node: SHIFTL, Next: SHIFTR, Prev: SHIFTA, Up: Intrinsic Procedures ! 9.236 'SHIFTL' -- Left shift ============================ _Description_: ! 'SHIFTL' returns a value corresponding to I with all of the bits shifted left by SHIFT places. If the absolute value of SHIFT is ! greater than 'BIT_SIZE(I)', the value is undefined. Bits shifted out from the left end are lost, and bits shifted in from the right end are set to 0. --- 15909,15921 ----  File: gfortran.info, Node: SHIFTL, Next: SHIFTR, Prev: SHIFTA, Up: Intrinsic Procedures ! 9.236 `SHIFTL' -- Left shift ============================ _Description_: ! `SHIFTL' returns a value corresponding to I with all of the bits shifted left by SHIFT places. If the absolute value of SHIFT is ! greater than `BIT_SIZE(I)', the value is undefined. Bits shifted out from the left end are lost, and bits shifted in from the right end are set to 0. *************** _Class_: *** 15757,15770 **** Elemental function _Syntax_: ! 'RESULT = SHIFTL(I, SHIFT)' _Arguments_: ! I The type shall be 'INTEGER'. ! SHIFT The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note SHIFTA::, *note SHIFTR:: --- 15926,15939 ---- Elemental function _Syntax_: ! `RESULT = SHIFTL(I, SHIFT)' _Arguments_: ! I The type shall be `INTEGER'. ! SHIFT The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note SHIFTA::, *note SHIFTR:: *************** _See also_: *** 15772,15784 ****  File: gfortran.info, Node: SHIFTR, Next: SIGN, Prev: SHIFTL, Up: Intrinsic Procedures ! 9.237 'SHIFTR' -- Right shift ============================= _Description_: ! 'SHIFTR' returns a value corresponding to I with all of the bits shifted right by SHIFT places. If the absolute value of SHIFT is ! greater than 'BIT_SIZE(I)', the value is undefined. Bits shifted out from the right end are lost, and bits shifted in from the left end are set to 0. --- 15941,15953 ----  File: gfortran.info, Node: SHIFTR, Next: SIGN, Prev: SHIFTL, Up: Intrinsic Procedures ! 9.237 `SHIFTR' -- Right shift ============================= _Description_: ! `SHIFTR' returns a value corresponding to I with all of the bits shifted right by SHIFT places. If the absolute value of SHIFT is ! greater than `BIT_SIZE(I)', the value is undefined. Bits shifted out from the right end are lost, and bits shifted in from the left end are set to 0. *************** _Class_: *** 15789,15802 **** Elemental function _Syntax_: ! 'RESULT = SHIFTR(I, SHIFT)' _Arguments_: ! I The type shall be 'INTEGER'. ! SHIFT The type shall be 'INTEGER'. _Return value_: ! The return value is of type 'INTEGER' and of the same kind as I. _See also_: *note SHIFTA::, *note SHIFTL:: --- 15958,15971 ---- Elemental function _Syntax_: ! `RESULT = SHIFTR(I, SHIFT)' _Arguments_: ! I The type shall be `INTEGER'. ! SHIFT The type shall be `INTEGER'. _Return value_: ! The return value is of type `INTEGER' and of the same kind as I. _See also_: *note SHIFTA::, *note SHIFTL:: *************** _See also_: *** 15804,15814 ****  File: gfortran.info, Node: SIGN, Next: SIGNAL, Prev: SHIFTR, Up: Intrinsic Procedures ! 9.238 'SIGN' -- Sign copying function ===================================== _Description_: ! 'SIGN(A,B)' returns the value of A with the sign of B. _Standard_: Fortran 77 and later --- 15973,15983 ----  File: gfortran.info, Node: SIGN, Next: SIGNAL, Prev: SHIFTR, Up: Intrinsic Procedures ! 9.238 `SIGN' -- Sign copying function ===================================== _Description_: ! `SIGN(A,B)' returns the value of A with the sign of B. _Standard_: Fortran 77 and later *************** _Class_: *** 15817,15831 **** Elemental function _Syntax_: ! 'RESULT = SIGN(A, B)' _Arguments_: ! A Shall be of type 'INTEGER' or 'REAL' ! B Shall be of the same type and kind as A _Return value_: The kind of the return value is that of A and B. If B\ge 0 then ! the result is 'ABS(A)', else it is '-ABS(A)'. _Example_: program test_sign --- 15986,16000 ---- Elemental function _Syntax_: ! `RESULT = SIGN(A, B)' _Arguments_: ! A Shall be of type `INTEGER' or `REAL' ! B Shall be of the same type and kind as A _Return value_: The kind of the return value is that of A and B. If B\ge 0 then ! the result is `ABS(A)', else it is `-ABS(A)'. _Example_: program test_sign *************** _Example_: *** 15839,15867 **** end program test_sign _Specific names_: ! Name Arguments Return type Standard ! 'SIGN(A,B)' 'REAL(4) A, 'REAL(4)' f77, gnu ! B' ! 'ISIGN(A,B)' 'INTEGER(4) 'INTEGER(4)' f77, gnu ! A, B' ! 'DSIGN(A,B)' 'REAL(8) A, 'REAL(8)' f77, gnu ! B'  File: gfortran.info, Node: SIGNAL, Next: SIN, Prev: SIGN, Up: Intrinsic Procedures ! 9.239 'SIGNAL' -- Signal handling subroutine (or function) ========================================================== _Description_: ! 'SIGNAL(NUMBER, HANDLER [, STATUS])' causes external subroutine HANDLER to be executed with a single integer argument when signal NUMBER occurs. If HANDLER is an integer, it can be used to turn ! off handling of signal NUMBER or revert to its default action. See ! 'signal(2)'. ! If 'SIGNAL' is called as a subroutine and the STATUS argument is ! supplied, it is set to the value returned by 'signal(2)'. _Standard_: GNU extension --- 16008,16036 ---- end program test_sign _Specific names_: ! Name Arguments Return type Standard ! `SIGN(A,B)' `REAL(4) A, `REAL(4)' f77, gnu ! B' ! `ISIGN(A,B)' `INTEGER(4) `INTEGER(4)' f77, gnu ! A, B' ! `DSIGN(A,B)' `REAL(8) A, `REAL(8)' f77, gnu ! B'  File: gfortran.info, Node: SIGNAL, Next: SIN, Prev: SIGN, Up: Intrinsic Procedures ! 9.239 `SIGNAL' -- Signal handling subroutine (or function) ========================================================== _Description_: ! `SIGNAL(NUMBER, HANDLER [, STATUS])' causes external subroutine HANDLER to be executed with a single integer argument when signal NUMBER occurs. If HANDLER is an integer, it can be used to turn ! off handling of signal NUMBER or revert to its default action. ! See `signal(2)'. ! If `SIGNAL' is called as a subroutine and the STATUS argument is ! supplied, it is set to the value returned by `signal(2)'. _Standard_: GNU extension *************** _Class_: *** 15870,15888 **** Subroutine, function _Syntax_: ! 'CALL SIGNAL(NUMBER, HANDLER [, STATUS])' ! 'STATUS = SIGNAL(NUMBER, HANDLER)' _Arguments_: ! NUMBER Shall be a scalar integer, with 'INTENT(IN)' ! HANDLER Signal handler ('INTEGER FUNCTION' or ! 'SUBROUTINE') or dummy/global 'INTEGER' scalar. ! 'INTEGER'. It is 'INTENT(IN)'. ! STATUS (Optional) STATUS shall be a scalar integer. It ! has 'INTENT(OUT)'. _Return value_: ! The 'SIGNAL' function returns the value returned by 'signal(2)'. _Example_: program test_signal --- 16039,16057 ---- Subroutine, function _Syntax_: ! `CALL SIGNAL(NUMBER, HANDLER [, STATUS])' ! `STATUS = SIGNAL(NUMBER, HANDLER)' _Arguments_: ! NUMBER Shall be a scalar integer, with `INTENT(IN)' ! HANDLER Signal handler (`INTEGER FUNCTION' or ! `SUBROUTINE') or dummy/global `INTEGER' scalar. ! `INTEGER'. It is `INTENT(IN)'. ! STATUS (Optional) STATUS shall be a scalar integer. ! It has `INTENT(OUT)'. _Return value_: ! The `SIGNAL' function returns the value returned by `signal(2)'. _Example_: program test_signal *************** _Example_: *** 15898,15908 ****  File: gfortran.info, Node: SIN, Next: SINH, Prev: SIGNAL, Up: Intrinsic Procedures ! 9.240 'SIN' -- Sine function ============================ _Description_: ! 'SIN(X)' computes the sine of X. _Standard_: Fortran 77 and later --- 16067,16077 ----  File: gfortran.info, Node: SIN, Next: SINH, Prev: SIGNAL, Up: Intrinsic Procedures ! 9.240 `SIN' -- Sine function ============================ _Description_: ! `SIN(X)' computes the sine of X. _Standard_: Fortran 77 and later *************** _Class_: *** 15911,15920 **** Elemental function _Syntax_: ! 'RESULT = SIN(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: The return value has same type and kind as X. --- 16080,16089 ---- Elemental function _Syntax_: ! `RESULT = SIN(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: The return value has same type and kind as X. *************** _Example_: *** 15926,15940 **** end program test_sin _Specific names_: ! Name Argument Return type Standard ! 'SIN(X)' 'REAL(4) X' 'REAL(4)' f77, gnu ! 'DSIN(X)' 'REAL(8) X' 'REAL(8)' f95, gnu ! 'CSIN(X)' 'COMPLEX(4) 'COMPLEX(4)' f95, gnu ! X' ! 'ZSIN(X)' 'COMPLEX(8) 'COMPLEX(8)' f95, gnu ! X' ! 'CDSIN(X)' 'COMPLEX(8) 'COMPLEX(8)' f95, gnu ! X' _See also_: *note ASIN:: --- 16095,16109 ---- end program test_sin _Specific names_: ! Name Argument Return type Standard ! `SIN(X)' `REAL(4) X' `REAL(4)' f77, gnu ! `DSIN(X)' `REAL(8) X' `REAL(8)' f95, gnu ! `CSIN(X)' `COMPLEX(4) `COMPLEX(4)' f95, gnu ! X' ! `ZSIN(X)' `COMPLEX(8) `COMPLEX(8)' f95, gnu ! X' ! `CDSIN(X)' `COMPLEX(8) `COMPLEX(8)' f95, gnu ! X' _See also_: *note ASIN:: *************** _See also_: *** 15942,15952 ****  File: gfortran.info, Node: SINH, Next: SIZE, Prev: SIN, Up: Intrinsic Procedures ! 9.241 'SINH' -- Hyperbolic sine function ======================================== _Description_: ! 'SINH(X)' computes the hyperbolic sine of X. _Standard_: Fortran 95 and later, for a complex argument Fortran 2008 or later --- 16111,16121 ----  File: gfortran.info, Node: SINH, Next: SIZE, Prev: SIN, Up: Intrinsic Procedures ! 9.241 `SINH' -- Hyperbolic sine function ======================================== _Description_: ! `SINH(X)' computes the hyperbolic sine of X. _Standard_: Fortran 95 and later, for a complex argument Fortran 2008 or later *************** _Class_: *** 15955,15964 **** Elemental function _Syntax_: ! 'RESULT = SINH(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: The return value has same type and kind as X. --- 16124,16133 ---- Elemental function _Syntax_: ! `RESULT = SINH(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: The return value has same type and kind as X. *************** _Example_: *** 15970,15980 **** end program test_sinh _Specific names_: ! Name Argument Return type Standard ! 'SINH(X)' 'REAL(4) X' 'REAL(4)' Fortran 95 and ! later ! 'DSINH(X)' 'REAL(8) X' 'REAL(8)' Fortran 95 and ! later _See also_: *note ASINH:: --- 16139,16149 ---- end program test_sinh _Specific names_: ! Name Argument Return type Standard ! `SINH(X)' `REAL(4) X' `REAL(4)' Fortran 95 and ! later ! `DSINH(X)' `REAL(8) X' `REAL(8)' Fortran 95 and ! later _See also_: *note ASINH:: *************** _See also_: *** 15982,15988 ****  File: gfortran.info, Node: SIZE, Next: SIZEOF, Prev: SINH, Up: Intrinsic Procedures ! 9.242 'SIZE' -- Determine the size of an array ============================================== _Description_: --- 16151,16157 ----  File: gfortran.info, Node: SIZE, Next: SIZEOF, Prev: SINH, Up: Intrinsic Procedures ! 9.242 `SIZE' -- Determine the size of an array ============================================== _Description_: *************** _Class_: *** 15996,16016 **** Inquiry function _Syntax_: ! 'RESULT = SIZE(ARRAY[, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an array of any type. If ARRAY is a ! pointer it must be associated and allocatable ! arrays must be allocated. ! DIM (Optional) shall be a scalar of type 'INTEGER' ! and its value shall be in the range from 1 to n, ! where n equals the rank of ARRAY. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: --- 16165,16185 ---- Inquiry function _Syntax_: ! `RESULT = SIZE(ARRAY[, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an array of any type. If ARRAY is a ! pointer it must be associated and allocatable ! arrays must be allocated. ! DIM (Optional) shall be a scalar of type `INTEGER' ! and its value shall be in the range from 1 to ! n, where n equals the rank of ARRAY. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: *************** _See also_: *** 16024,16035 ****  File: gfortran.info, Node: SIZEOF, Next: SLEEP, Prev: SIZE, Up: Intrinsic Procedures ! 9.243 'SIZEOF' -- Size in bytes of an expression ================================================ _Description_: ! 'SIZEOF(X)' calculates the number of bytes of storage the ! expression 'X' occupies. _Standard_: GNU extension --- 16193,16204 ----  File: gfortran.info, Node: SIZEOF, Next: SLEEP, Prev: SIZE, Up: Intrinsic Procedures ! 9.243 `SIZEOF' -- Size in bytes of an expression ================================================ _Description_: ! `SIZEOF(X)' calculates the number of bytes of storage the ! expression `X' occupies. _Standard_: GNU extension *************** _Class_: *** 16038,16060 **** Inquiry function _Syntax_: ! 'N = SIZEOF(X)' _Arguments_: ! X The argument shall be of any type, rank or ! shape. _Return value_: The return value is of type integer and of the system-dependent ! kind C_SIZE_T (from the ISO_C_BINDING module). Its value is the number of bytes occupied by the argument. If the argument has the ! 'POINTER' attribute, the number of bytes of the storage area pointed to is returned. If the argument is of a derived type with ! 'POINTER' or 'ALLOCATABLE' components, the return value does not account for the sizes of the data pointed to by these components. If the argument is polymorphic, the size according to the dynamic ! type is returned. The argument may not be a procedure or procedure ! pointer. Note that the code assumes for arrays that those are contiguous; for contiguous arrays, it returns the storage or an array element multiplied by the size of the array. --- 16207,16229 ---- Inquiry function _Syntax_: ! `N = SIZEOF(X)' _Arguments_: ! X The argument shall be of any type, rank or ! shape. _Return value_: The return value is of type integer and of the system-dependent ! kind C_SIZE_T (from the ISO_C_BINDING module). Its value is the number of bytes occupied by the argument. If the argument has the ! `POINTER' attribute, the number of bytes of the storage area pointed to is returned. If the argument is of a derived type with ! `POINTER' or `ALLOCATABLE' components, the return value does not account for the sizes of the data pointed to by these components. If the argument is polymorphic, the size according to the dynamic ! type is returned. The argument may not be a procedure or procedure ! pointer. Note that the code assumes for arrays that those are contiguous; for contiguous arrays, it returns the storage or an array element multiplied by the size of the array. *************** _Example_: *** 16063,16070 **** real :: r, s(5) print *, (sizeof(s)/sizeof(r) == 5) end ! The example will print '.TRUE.' unless you are using a platform ! where default 'REAL' variables are unusually padded. _See also_: *note C_SIZEOF::, *note STORAGE_SIZE:: --- 16232,16239 ---- real :: r, s(5) print *, (sizeof(s)/sizeof(r) == 5) end ! The example will print `.TRUE.' unless you are using a platform ! where default `REAL' variables are unusually padded. _See also_: *note C_SIZEOF::, *note STORAGE_SIZE:: *************** _See also_: *** 16072,16078 ****  File: gfortran.info, Node: SLEEP, Next: SPACING, Prev: SIZEOF, Up: Intrinsic Procedures ! 9.244 'SLEEP' -- Sleep for the specified number of seconds ========================================================== _Description_: --- 16241,16247 ----  File: gfortran.info, Node: SLEEP, Next: SPACING, Prev: SIZEOF, Up: Intrinsic Procedures ! 9.244 `SLEEP' -- Sleep for the specified number of seconds ========================================================== _Description_: *************** _Class_: *** 16086,16095 **** Subroutine _Syntax_: ! 'CALL SLEEP(SECONDS)' _Arguments_: ! SECONDS The type shall be of default 'INTEGER'. _Example_: program test_sleep --- 16255,16264 ---- Subroutine _Syntax_: ! `CALL SLEEP(SECONDS)' _Arguments_: ! SECONDS The type shall be of default `INTEGER'. _Example_: program test_sleep *************** _Example_: *** 16099,16105 ****  File: gfortran.info, Node: SPACING, Next: SPREAD, Prev: SLEEP, Up: Intrinsic Procedures ! 9.245 'SPACING' -- Smallest distance between two numbers of a given type ======================================================================== _Description_: --- 16268,16274 ----  File: gfortran.info, Node: SPACING, Next: SPREAD, Prev: SLEEP, Up: Intrinsic Procedures ! 9.245 `SPACING' -- Smallest distance between two numbers of a given type ======================================================================== _Description_: *************** _Class_: *** 16113,16122 **** Elemental function _Syntax_: ! 'RESULT = SPACING(X)' _Arguments_: ! X Shall be of type 'REAL'. _Return value_: The result is of the same type as the input argument X. --- 16282,16291 ---- Elemental function _Syntax_: ! `RESULT = SPACING(X)' _Arguments_: ! X Shall be of type `REAL'. _Return value_: The result is of the same type as the input argument X. *************** _See also_: *** 16136,16147 ****  File: gfortran.info, Node: SPREAD, Next: SQRT, Prev: SPACING, Up: Intrinsic Procedures ! 9.246 'SPREAD' -- Add a dimension to an array ============================================= _Description_: ! Replicates a SOURCE array NCOPIES times along a specified dimension ! DIM. _Standard_: Fortran 95 and later --- 16305,16316 ----  File: gfortran.info, Node: SPREAD, Next: SQRT, Prev: SPACING, Up: Intrinsic Procedures ! 9.246 `SPREAD' -- Add a dimension to an array ============================================= _Description_: ! Replicates a SOURCE array NCOPIES times along a specified ! dimension DIM. _Standard_: Fortran 95 and later *************** _Class_: *** 16150,16164 **** Transformational function _Syntax_: ! 'RESULT = SPREAD(SOURCE, DIM, NCOPIES)' _Arguments_: ! SOURCE Shall be a scalar or an array of any type and a ! rank less than seven. ! DIM Shall be a scalar of type 'INTEGER' with a value ! in the range from 1 to n+1, where n equals the ! rank of SOURCE. ! NCOPIES Shall be a scalar of type 'INTEGER'. _Return value_: The result is an array of the same type as SOURCE and has rank n+1 --- 16319,16333 ---- Transformational function _Syntax_: ! `RESULT = SPREAD(SOURCE, DIM, NCOPIES)' _Arguments_: ! SOURCE Shall be a scalar or an array of any type and ! a rank less than seven. ! DIM Shall be a scalar of type `INTEGER' with a ! value in the range from 1 to n+1, where n ! equals the rank of SOURCE. ! NCOPIES Shall be a scalar of type `INTEGER'. _Return value_: The result is an array of the same type as SOURCE and has rank n+1 *************** _See also_: *** 16177,16187 ****  File: gfortran.info, Node: SQRT, Next: SRAND, Prev: SPREAD, Up: Intrinsic Procedures ! 9.247 'SQRT' -- Square-root function ==================================== _Description_: ! 'SQRT(X)' computes the square root of X. _Standard_: Fortran 77 and later --- 16346,16356 ----  File: gfortran.info, Node: SQRT, Next: SRAND, Prev: SPREAD, Up: Intrinsic Procedures ! 9.247 `SQRT' -- Square-root function ==================================== _Description_: ! `SQRT(X)' computes the square root of X. _Standard_: Fortran 77 and later *************** _Class_: *** 16190,16202 **** Elemental function _Syntax_: ! 'RESULT = SQRT(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value is of type 'REAL' or 'COMPLEX'. The kind type parameter is the same as X. _Example_: --- 16359,16371 ---- Elemental function _Syntax_: ! `RESULT = SQRT(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value is of type `REAL' or `COMPLEX'. The kind type parameter is the same as X. _Example_: *************** _Example_: *** 16208,16234 **** end program test_sqrt _Specific names_: ! Name Argument Return type Standard ! 'SQRT(X)' 'REAL(4) X' 'REAL(4)' Fortran 95 and ! later ! 'DSQRT(X)' 'REAL(8) X' 'REAL(8)' Fortran 95 and ! later ! 'CSQRT(X)' 'COMPLEX(4) 'COMPLEX(4)' Fortran 95 and ! X' later ! 'ZSQRT(X)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! X' ! 'CDSQRT(X)' 'COMPLEX(8) 'COMPLEX(8)' GNU extension ! X'  File: gfortran.info, Node: SRAND, Next: STAT, Prev: SQRT, Up: Intrinsic Procedures ! 9.248 'SRAND' -- Reinitialize the random number generator ========================================================= _Description_: ! 'SRAND' reinitializes the pseudo-random number generator called by ! 'RAND' and 'IRAND'. The new seed used by the generator is specified by the required argument SEED. _Standard_: --- 16377,16403 ---- end program test_sqrt _Specific names_: ! Name Argument Return type Standard ! `SQRT(X)' `REAL(4) X' `REAL(4)' Fortran 95 and ! later ! `DSQRT(X)' `REAL(8) X' `REAL(8)' Fortran 95 and ! later ! `CSQRT(X)' `COMPLEX(4) `COMPLEX(4)' Fortran 95 and ! X' later ! `ZSQRT(X)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! X' ! `CDSQRT(X)' `COMPLEX(8) `COMPLEX(8)' GNU extension ! X'  File: gfortran.info, Node: SRAND, Next: STAT, Prev: SQRT, Up: Intrinsic Procedures ! 9.248 `SRAND' -- Reinitialize the random number generator ========================================================= _Description_: ! `SRAND' reinitializes the pseudo-random number generator called by ! `RAND' and `IRAND'. The new seed used by the generator is specified by the required argument SEED. _Standard_: *************** _Class_: *** 16238,16294 **** Subroutine _Syntax_: ! 'CALL SRAND(SEED)' _Arguments_: ! SEED Shall be a scalar 'INTEGER(kind=4)'. _Return value_: Does not return anything. _Example_: ! See 'RAND' and 'IRAND' for examples. _Notes_: The Fortran standard specifies the intrinsic subroutines ! 'RANDOM_SEED' to initialize the pseudo-random number generator and ! 'RANDOM_NUMBER' to generate pseudo-random numbers. These subroutines should be used in new codes. Please note that in GNU Fortran, these two sets of intrinsics ! ('RAND', 'IRAND' and 'SRAND' on the one hand, 'RANDOM_NUMBER' and ! 'RANDOM_SEED' on the other hand) access two independent pseudo-random number generators. _See also_: *note RAND::, *note RANDOM_SEED::, *note RANDOM_NUMBER::  File: gfortran.info, Node: STAT, Next: STORAGE_SIZE, Prev: SRAND, Up: Intrinsic Procedures ! 9.249 'STAT' -- Get file status =============================== _Description_: ! This function returns information about a file. No permissions are required on the file itself, but execute (search) permission is required on all of the directories in path that lead to the file. ! The elements that are obtained and stored in the array 'VALUES': ! 'VALUES(1)' Device ID ! 'VALUES(2)' Inode number ! 'VALUES(3)' File mode ! 'VALUES(4)' Number of links ! 'VALUES(5)' Owner's uid ! 'VALUES(6)' Owner's gid ! 'VALUES(7)' ID of device containing directory entry for file ! (0 if not available) ! 'VALUES(8)' File size (bytes) ! 'VALUES(9)' Last access time ! 'VALUES(10)'Last modification time ! 'VALUES(11)'Last file status change time ! 'VALUES(12)'Preferred I/O block size (-1 if not available) ! 'VALUES(13)'Number of blocks allocated (-1 if not available) Not all these elements are relevant on all systems. If an element is not relevant, it is returned as 0. --- 16407,16465 ---- Subroutine _Syntax_: ! `CALL SRAND(SEED)' _Arguments_: ! SEED Shall be a scalar `INTEGER(kind=4)'. _Return value_: Does not return anything. _Example_: ! See `RAND' and `IRAND' for examples. _Notes_: The Fortran standard specifies the intrinsic subroutines ! `RANDOM_SEED' to initialize the pseudo-random number generator and ! `RANDOM_NUMBER' to generate pseudo-random numbers. These subroutines should be used in new codes. Please note that in GNU Fortran, these two sets of intrinsics ! (`RAND', `IRAND' and `SRAND' on the one hand, `RANDOM_NUMBER' and ! `RANDOM_SEED' on the other hand) access two independent pseudo-random number generators. _See also_: *note RAND::, *note RANDOM_SEED::, *note RANDOM_NUMBER:: +  File: gfortran.info, Node: STAT, Next: STORAGE_SIZE, Prev: SRAND, Up: Intrinsic Procedures ! 9.249 `STAT' -- Get file status =============================== _Description_: ! This function returns information about a file. No permissions are required on the file itself, but execute (search) permission is required on all of the directories in path that lead to the file. ! The elements that are obtained and stored in the array `VALUES': ! `VALUES(1)'Device ID ! `VALUES(2)'Inode number ! `VALUES(3)'File mode ! `VALUES(4)'Number of links ! `VALUES(5)'Owner's uid ! `VALUES(6)'Owner's gid ! `VALUES(7)'ID of device containing directory entry for ! file (0 if not available) ! `VALUES(8)'File size (bytes) ! `VALUES(9)'Last access time ! `VALUES(10)'Last modification time ! `VALUES(11)'Last file status change time ! `VALUES(12)'Preferred I/O block size (-1 if not available) ! `VALUES(13)'Number of blocks allocated (-1 if not ! available) Not all these elements are relevant on all systems. If an element is not relevant, it is returned as 0. *************** _Class_: *** 16303,16318 **** Subroutine, function _Syntax_: ! 'CALL STAT(NAME, VALUES [, STATUS])' ! 'STATUS = STAT(NAME, VALUES)' _Arguments_: ! NAME The type shall be 'CHARACTER', of the default ! kind and a valid path within the file system. ! VALUES The type shall be 'INTEGER(4), DIMENSION(13)'. ! STATUS (Optional) status flag of type 'INTEGER(4)'. ! Returns 0 on success and a system specific error ! code otherwise. _Example_: PROGRAM test_stat --- 16474,16489 ---- Subroutine, function _Syntax_: ! `CALL STAT(NAME, VALUES [, STATUS])' ! `STATUS = STAT(NAME, VALUES)' _Arguments_: ! NAME The type shall be `CHARACTER', of the default ! kind and a valid path within the file system. ! VALUES The type shall be `INTEGER(4), DIMENSION(13)'. ! STATUS (Optional) status flag of type `INTEGER(4)'. ! Returns 0 on success and a system specific ! error code otherwise. _Example_: PROGRAM test_stat *************** _See also_: *** 16344,16371 ****  File: gfortran.info, Node: STORAGE_SIZE, Next: SUM, Prev: STAT, Up: Intrinsic Procedures ! 9.250 'STORAGE_SIZE' -- Storage size in bits ============================================ _Description_: Returns the storage size of argument A in bits. _Standard_: Fortran 2008 and later _Class_: Inquiry function _Syntax_: ! 'RESULT = STORAGE_SIZE(A [, KIND])' _Arguments_: ! A Shall be a scalar or array of any type. ! KIND (Optional) shall be a scalar integer constant ! expression. _Return Value_: The result is a scalar integer with the kind type parameter specified by KIND (or default integer type if KIND is missing). ! The result value is the size expressed in bits for an element of an ! array that has the dynamic type and type parameters of A. _See also_: *note C_SIZEOF::, *note SIZEOF:: --- 16515,16545 ----  File: gfortran.info, Node: STORAGE_SIZE, Next: SUM, Prev: STAT, Up: Intrinsic Procedures ! 9.250 `STORAGE_SIZE' -- Storage size in bits ============================================ _Description_: Returns the storage size of argument A in bits. + _Standard_: Fortran 2008 and later + _Class_: Inquiry function + _Syntax_: ! `RESULT = STORAGE_SIZE(A [, KIND])' _Arguments_: ! A Shall be a scalar or array of any type. ! KIND (Optional) shall be a scalar integer constant ! expression. _Return Value_: The result is a scalar integer with the kind type parameter specified by KIND (or default integer type if KIND is missing). ! The result value is the size expressed in bits for an element of ! an array that has the dynamic type and type parameters of A. _See also_: *note C_SIZEOF::, *note SIZEOF:: *************** _See also_: *** 16373,16384 ****  File: gfortran.info, Node: SUM, Next: SYMLNK, Prev: STORAGE_SIZE, Up: Intrinsic Procedures ! 9.251 'SUM' -- Sum of array elements ==================================== _Description_: ! Adds the elements of ARRAY along dimension DIM if the corresponding ! element in MASK is 'TRUE'. _Standard_: Fortran 95 and later --- 16547,16558 ----  File: gfortran.info, Node: SUM, Next: SYMLNK, Prev: STORAGE_SIZE, Up: Intrinsic Procedures ! 9.251 `SUM' -- Sum of array elements ==================================== _Description_: ! Adds the elements of ARRAY along dimension DIM if the ! corresponding element in MASK is `TRUE'. _Standard_: Fortran 95 and later *************** _Class_: *** 16387,16412 **** Transformational function _Syntax_: ! 'RESULT = SUM(ARRAY[, MASK])' ! 'RESULT = SUM(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type 'INTEGER', 'REAL' or ! 'COMPLEX'. ! DIM (Optional) shall be a scalar of type 'INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type 'LOGICAL' and either ! be a scalar or an array of the same shape as ! ARRAY. _Return value_: The result is of the same type as ARRAY. ! If DIM is absent, a scalar with the sum of all elements in ARRAY is ! returned. Otherwise, an array of rank n-1, where n equals the rank ! of ARRAY, and a shape similar to that of ARRAY with dimension DIM ! dropped is returned. _Example_: PROGRAM test_sum --- 16561,16586 ---- Transformational function _Syntax_: ! `RESULT = SUM(ARRAY[, MASK])' ! `RESULT = SUM(ARRAY, DIM[, MASK])' _Arguments_: ! ARRAY Shall be an array of type `INTEGER', `REAL' or ! `COMPLEX'. ! DIM (Optional) shall be a scalar of type `INTEGER' ! with a value in the range from 1 to n, where n ! equals the rank of ARRAY. ! MASK (Optional) shall be of type `LOGICAL' and ! either be a scalar or an array of the same ! shape as ARRAY. _Return value_: The result is of the same type as ARRAY. ! If DIM is absent, a scalar with the sum of all elements in ARRAY ! is returned. Otherwise, an array of rank n-1, where n equals the ! rank of ARRAY, and a shape similar to that of ARRAY with dimension ! DIM dropped is returned. _Example_: PROGRAM test_sum *************** _See also_: *** 16421,16436 ****  File: gfortran.info, Node: SYMLNK, Next: SYSTEM, Prev: SUM, Up: Intrinsic Procedures ! 9.252 'SYMLNK' -- Create a symbolic link ======================================== _Description_: ! Makes a symbolic link from file PATH1 to PATH2. A null character ! ('CHAR(0)') can be used to mark the end of the names in PATH1 and PATH2; otherwise, trailing blanks in the file names are ignored. If the STATUS argument is supplied, it contains 0 on success or a ! nonzero error code upon return; see 'symlink(2)'. If the system ! does not supply 'symlink(2)', 'ENOSYS' is returned. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 16595,16610 ----  File: gfortran.info, Node: SYMLNK, Next: SYSTEM, Prev: SUM, Up: Intrinsic Procedures ! 9.252 `SYMLNK' -- Create a symbolic link ======================================== _Description_: ! Makes a symbolic link from file PATH1 to PATH2. A null character ! (`CHAR(0)') can be used to mark the end of the names in PATH1 and PATH2; otherwise, trailing blanks in the file names are ignored. If the STATUS argument is supplied, it contains 0 on success or a ! nonzero error code upon return; see `symlink(2)'. If the system ! does not supply `symlink(2)', `ENOSYS' is returned. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 16442,16476 **** Subroutine, function _Syntax_: ! 'CALL SYMLNK(PATH1, PATH2 [, STATUS])' ! 'STATUS = SYMLNK(PATH1, PATH2)' _Arguments_: ! PATH1 Shall be of default 'CHARACTER' type. ! PATH2 Shall be of default 'CHARACTER' type. ! STATUS (Optional) Shall be of default 'INTEGER' type. _See also_: *note LINK::, *note UNLINK::  File: gfortran.info, Node: SYSTEM, Next: SYSTEM_CLOCK, Prev: SYMLNK, Up: Intrinsic Procedures ! 9.253 'SYSTEM' -- Execute a shell command ========================================= _Description_: ! Passes the command COMMAND to a shell (see 'system(3)'). If argument STATUS is present, it contains the value returned by ! 'system(3)', which is presumably 0 if the shell command succeeded. Note that which shell is used to invoke the command is system-dependent and environment-dependent. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the 'system' function need not be thread-safe. It is the ! responsibility of the user to ensure that 'system' is not called concurrently. _Standard_: --- 16616,16651 ---- Subroutine, function _Syntax_: ! `CALL SYMLNK(PATH1, PATH2 [, STATUS])' ! `STATUS = SYMLNK(PATH1, PATH2)' _Arguments_: ! PATH1 Shall be of default `CHARACTER' type. ! PATH2 Shall be of default `CHARACTER' type. ! STATUS (Optional) Shall be of default `INTEGER' type. _See also_: *note LINK::, *note UNLINK:: +  File: gfortran.info, Node: SYSTEM, Next: SYSTEM_CLOCK, Prev: SYMLNK, Up: Intrinsic Procedures ! 9.253 `SYSTEM' -- Execute a shell command ========================================= _Description_: ! Passes the command COMMAND to a shell (see `system(3)'). If argument STATUS is present, it contains the value returned by ! `system(3)', which is presumably 0 if the shell command succeeded. Note that which shell is used to invoke the command is system-dependent and environment-dependent. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. ! Note that the `system' function need not be thread-safe. It is the ! responsibility of the user to ensure that `system' is not called concurrently. _Standard_: *************** _Class_: *** 16480,16491 **** Subroutine, function _Syntax_: ! 'CALL SYSTEM(COMMAND [, STATUS])' ! 'STATUS = SYSTEM(COMMAND)' _Arguments_: ! COMMAND Shall be of default 'CHARACTER' type. ! STATUS (Optional) Shall be of default 'INTEGER' type. _See also_: *note EXECUTE_COMMAND_LINE::, which is part of the Fortran 2008 --- 16655,16666 ---- Subroutine, function _Syntax_: ! `CALL SYSTEM(COMMAND [, STATUS])' ! `STATUS = SYSTEM(COMMAND)' _Arguments_: ! COMMAND Shall be of default `CHARACTER' type. ! STATUS (Optional) Shall be of default `INTEGER' type. _See also_: *note EXECUTE_COMMAND_LINE::, which is part of the Fortran 2008 *************** _See also_: *** 16494,16534 ****  File: gfortran.info, Node: SYSTEM_CLOCK, Next: TAN, Prev: SYSTEM, Up: Intrinsic Procedures ! 9.254 'SYSTEM_CLOCK' -- Time function ===================================== _Description_: ! Determines the COUNT of a processor clock since an unspecified time ! in the past modulo COUNT_MAX, COUNT_RATE determines the number of ! clock ticks per second. If the platform supports a monotonic ! clock, that clock is used and can, depending on the platform clock ! implementation, provide up to nanosecond resolution. If a ! monotonic clock is not available, the implementation falls back to ! a realtime clock. COUNT_RATE is system dependent and can vary depending on the kind ! of the arguments. For KIND=4 arguments (and smaller integer ! kinds), COUNT represents milliseconds, while for KIND=8 arguments ! (and larger integer kinds), COUNT typically represents micro- or nanoseconds depending on resolution of the underlying platform ! clock. COUNT_MAX usually equals 'HUGE(COUNT_MAX)'. Note that the ! millisecond resolution of the KIND=4 version implies that the COUNT ! will wrap around in roughly 25 days. In order to avoid issues with ! the wrap around and for more precise timing, please use the KIND=8 ! version. If there is no clock, or querying the clock fails, COUNT is set to ! '-HUGE(COUNT)', and COUNT_RATE and COUNT_MAX are set to zero. When running on a platform using the GNU C library (glibc) version 2.16 or older, or a derivative thereof, the high resolution ! monotonic clock is available only when linking with the RT library. ! This can be done explicitly by adding the '-lrt' flag when linking ! the application, but is also done implicitly when using OpenMP. ! On the Windows platform, the version with KIND=4 arguments uses the ! 'GetTickCount' function, whereas the KIND=8 version uses ! 'QueryPerformanceCounter' and 'QueryPerformanceCounterFrequency'. For more information, and potential caveats, please see the platform documentation. --- 16669,16710 ----  File: gfortran.info, Node: SYSTEM_CLOCK, Next: TAN, Prev: SYSTEM, Up: Intrinsic Procedures ! 9.254 `SYSTEM_CLOCK' -- Time function ===================================== _Description_: ! Determines the COUNT of a processor clock since an unspecified ! time in the past modulo COUNT_MAX, COUNT_RATE determines the ! number of clock ticks per second. If the platform supports a ! monotonic clock, that clock is used and can, depending on the ! platform clock implementation, provide up to nanosecond ! resolution. If a monotonic clock is not available, the ! implementation falls back to a realtime clock. COUNT_RATE is system dependent and can vary depending on the kind ! of the arguments. For KIND=4 arguments (and smaller integer kinds), ! COUNT represents milliseconds, while for KIND=8 arguments (and ! larger integer kinds), COUNT typically represents micro- or nanoseconds depending on resolution of the underlying platform ! clock. COUNT_MAX usually equals `HUGE(COUNT_MAX)'. Note that the ! millisecond resolution of the KIND=4 version implies that the ! COUNT will wrap around in roughly 25 days. In order to avoid issues ! with the wrap around and for more precise timing, please use the ! KIND=8 version. If there is no clock, or querying the clock fails, COUNT is set to ! `-HUGE(COUNT)', and COUNT_RATE and COUNT_MAX are set to zero. When running on a platform using the GNU C library (glibc) version 2.16 or older, or a derivative thereof, the high resolution ! monotonic clock is available only when linking with the RT ! library. This can be done explicitly by adding the `-lrt' flag ! when linking the application, but is also done implicitly when ! using OpenMP. ! On the Windows platform, the version with KIND=4 arguments uses ! the `GetTickCount' function, whereas the KIND=8 version uses ! `QueryPerformanceCounter' and `QueryPerformanceCounterFrequency'. For more information, and potential caveats, please see the platform documentation. *************** _Class_: *** 16539,16553 **** Subroutine _Syntax_: ! 'CALL SYSTEM_CLOCK([COUNT, COUNT_RATE, COUNT_MAX])' _Arguments_: ! COUNT (Optional) shall be a scalar of type 'INTEGER' ! with 'INTENT(OUT)'. ! COUNT_RATE (Optional) shall be a scalar of type 'INTEGER' ! or 'REAL', with 'INTENT(OUT)'. ! COUNT_MAX (Optional) shall be a scalar of type 'INTEGER' ! with 'INTENT(OUT)'. _Example_: PROGRAM test_system_clock --- 16715,16729 ---- Subroutine _Syntax_: ! `CALL SYSTEM_CLOCK([COUNT, COUNT_RATE, COUNT_MAX])' _Arguments_: ! COUNT (Optional) shall be a scalar of type `INTEGER' ! with `INTENT(OUT)'. ! COUNT_RATE (Optional) shall be a scalar of type `INTEGER' ! or `REAL', with `INTENT(OUT)'. ! COUNT_MAX (Optional) shall be a scalar of type `INTEGER' ! with `INTENT(OUT)'. _Example_: PROGRAM test_system_clock *************** _See also_: *** 16562,16572 ****  File: gfortran.info, Node: TAN, Next: TANH, Prev: SYSTEM_CLOCK, Up: Intrinsic Procedures ! 9.255 'TAN' -- Tangent function =============================== _Description_: ! 'TAN(X)' computes the tangent of X. _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later --- 16738,16748 ----  File: gfortran.info, Node: TAN, Next: TANH, Prev: SYSTEM_CLOCK, Up: Intrinsic Procedures ! 9.255 `TAN' -- Tangent function =============================== _Description_: ! `TAN(X)' computes the tangent of X. _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later *************** _Class_: *** 16575,16584 **** Elemental function _Syntax_: ! 'RESULT = TAN(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: The return value has same type and kind as X. --- 16751,16760 ---- Elemental function _Syntax_: ! `RESULT = TAN(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: The return value has same type and kind as X. *************** _Example_: *** 16590,16600 **** end program test_tan _Specific names_: ! Name Argument Return type Standard ! 'TAN(X)' 'REAL(4) X' 'REAL(4)' Fortran 95 and ! later ! 'DTAN(X)' 'REAL(8) X' 'REAL(8)' Fortran 95 and ! later _See also_: *note ATAN:: --- 16766,16776 ---- end program test_tan _Specific names_: ! Name Argument Return type Standard ! `TAN(X)' `REAL(4) X' `REAL(4)' Fortran 95 and ! later ! `DTAN(X)' `REAL(8) X' `REAL(8)' Fortran 95 and ! later _See also_: *note ATAN:: *************** _See also_: *** 16602,16612 ****  File: gfortran.info, Node: TANH, Next: THIS_IMAGE, Prev: TAN, Up: Intrinsic Procedures ! 9.256 'TANH' -- Hyperbolic tangent function =========================================== _Description_: ! 'TANH(X)' computes the hyperbolic tangent of X. _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later --- 16778,16788 ----  File: gfortran.info, Node: TANH, Next: THIS_IMAGE, Prev: TAN, Up: Intrinsic Procedures ! 9.256 `TANH' -- Hyperbolic tangent function =========================================== _Description_: ! `TANH(X)' computes the hyperbolic tangent of X. _Standard_: Fortran 77 and later, for a complex argument Fortran 2008 or later *************** _Class_: *** 16615,16629 **** Elemental function _Syntax_: ! 'X = TANH(X)' _Arguments_: ! X The type shall be 'REAL' or 'COMPLEX'. _Return value_: ! The return value has same type and kind as X. If X is complex, the ! imaginary part of the result is in radians. If X is 'REAL', the ! return value lies in the range - 1 \leq tanh(x) \leq 1 . _Example_: program test_tanh --- 16791,16805 ---- Elemental function _Syntax_: ! `X = TANH(X)' _Arguments_: ! X The type shall be `REAL' or `COMPLEX'. _Return value_: ! The return value has same type and kind as X. If X is complex, the ! imaginary part of the result is in radians. If X is `REAL', the ! return value lies in the range - 1 \leq tanh(x) \leq 1 . _Example_: program test_tanh *************** _Example_: *** 16632,16642 **** end program test_tanh _Specific names_: ! Name Argument Return type Standard ! 'TANH(X)' 'REAL(4) X' 'REAL(4)' Fortran 95 and ! later ! 'DTANH(X)' 'REAL(8) X' 'REAL(8)' Fortran 95 and ! later _See also_: *note ATANH:: --- 16808,16818 ---- end program test_tanh _Specific names_: ! Name Argument Return type Standard ! `TANH(X)' `REAL(4) X' `REAL(4)' Fortran 95 and ! later ! `DTANH(X)' `REAL(8) X' `REAL(8)' Fortran 95 and ! later _See also_: *note ATANH:: *************** _See also_: *** 16644,16689 ****  File: gfortran.info, Node: THIS_IMAGE, Next: TIME, Prev: TANH, Up: Intrinsic Procedures ! 9.257 'THIS_IMAGE' -- Function that returns the cosubscript index of this image =============================================================================== _Description_: Returns the cosubscript for this image. _Standard_: ! Fortran 2008 and later. With DISTANCE argument, Technical Specification (TS) 18508 or later _Class_: Transformational function _Syntax_: ! 'RESULT = THIS_IMAGE()' ! 'RESULT = THIS_IMAGE(DISTANCE)' ! 'RESULT = THIS_IMAGE(COARRAY [, DIM])' _Arguments_: ! DISTANCE (optional, intent(in)) Nonnegative scalar ! integer (not permitted together with COARRAY). ! COARRAY Coarray of any type (optional; if DIM present, ! required). ! DIM default integer scalar (optional). If present, ! DIM shall be between one and the corank of ! COARRAY. _Return value_: ! Default integer. If COARRAY is not present, it is scalar; if DISTANCE is not present or has value 0, its value is the image index on the invoking image for the current team, for values ! smaller or equal distance to the initial team, it returns the image ! index on the ancestor team which has a distance of DISTANCE from ! the invoking team. If DISTANCE is larger than the distance to the ! initial team, the image index of the initial team is returned. Otherwise when the COARRAY is present, if DIM is not present, a rank-1 array with corank elements is returned, containing the ! cosubscripts for COARRAY specifying the invoking image. If DIM is ! present, a scalar is returned, with the value of the DIM element of ! 'THIS_IMAGE(COARRAY)'. _Example_: INTEGER :: value[*] --- 16820,16865 ----  File: gfortran.info, Node: THIS_IMAGE, Next: TIME, Prev: TANH, Up: Intrinsic Procedures ! 9.257 `THIS_IMAGE' -- Function that returns the cosubscript index of this image =============================================================================== _Description_: Returns the cosubscript for this image. _Standard_: ! Fortran 2008 and later. With DISTANCE argument, Technical Specification (TS) 18508 or later _Class_: Transformational function _Syntax_: ! `RESULT = THIS_IMAGE()' ! `RESULT = THIS_IMAGE(DISTANCE)' ! `RESULT = THIS_IMAGE(COARRAY [, DIM])' _Arguments_: ! DISTANCE (optional, intent(in)) Nonnegative scalar ! integer (not permitted together with COARRAY). ! COARRAY Coarray of any type (optional; if DIM ! present, required). ! DIM default integer scalar (optional). If present, ! DIM shall be between one and the corank of ! COARRAY. _Return value_: ! Default integer. If COARRAY is not present, it is scalar; if DISTANCE is not present or has value 0, its value is the image index on the invoking image for the current team, for values ! smaller or equal distance to the initial team, it returns the ! image index on the ancestor team which has a distance of DISTANCE ! from the invoking team. If DISTANCE is larger than the distance to ! the initial team, the image index of the initial team is returned. Otherwise when the COARRAY is present, if DIM is not present, a rank-1 array with corank elements is returned, containing the ! cosubscripts for COARRAY specifying the invoking image. If DIM is ! present, a scalar is returned, with the value of the DIM element ! of `THIS_IMAGE(COARRAY)'. _Example_: INTEGER :: value[*] *************** _See also_: *** 16706,16721 ****  File: gfortran.info, Node: TIME, Next: TIME8, Prev: THIS_IMAGE, Up: Intrinsic Procedures ! 9.258 'TIME' -- Time function ============================= _Description_: Returns the current time encoded as an integer (in the manner of ! the function 'time(3)' in the C standard library). This value is ! suitable for passing to 'CTIME', 'GMTIME', and 'LTIME'. This intrinsic is not fully portable, such as to systems with ! 32-bit 'INTEGER' types but supporting times wider than 32 bits. Therefore, the values returned by this intrinsic might be, or become, negative, or numerically less than previous values, during a single run of the compiled program. --- 16882,16897 ----  File: gfortran.info, Node: TIME, Next: TIME8, Prev: THIS_IMAGE, Up: Intrinsic Procedures ! 9.258 `TIME' -- Time function ============================= _Description_: Returns the current time encoded as an integer (in the manner of ! the function `time(3)' in the C standard library). This value is ! suitable for passing to `CTIME', `GMTIME', and `LTIME'. This intrinsic is not fully portable, such as to systems with ! 32-bit `INTEGER' types but supporting times wider than 32 bits. Therefore, the values returned by this intrinsic might be, or become, negative, or numerically less than previous values, during a single run of the compiled program. *************** _Class_: *** 16731,16761 **** Function _Syntax_: ! 'RESULT = TIME()' _Return value_: ! The return value is a scalar of type 'INTEGER(4)'. _See also_: ! *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK::, *note ! TIME8::  File: gfortran.info, Node: TIME8, Next: TINY, Prev: TIME, Up: Intrinsic Procedures ! 9.259 'TIME8' -- Time function (64-bit) ======================================= _Description_: Returns the current time encoded as an integer (in the manner of ! the function 'time(3)' in the C standard library). This value is ! suitable for passing to 'CTIME', 'GMTIME', and 'LTIME'. _Warning:_ this intrinsic does not increase the range of the timing ! values over that returned by 'time(3)'. On a system with a 32-bit ! 'time(3)', 'TIME8' will return a 32-bit value, even though it is ! converted to a 64-bit 'INTEGER(8)' value. That means overflows of ! the 32-bit value can still occur. Therefore, the values returned by this intrinsic might be or become negative or numerically less than previous values during a single run of the compiled program. --- 16907,16938 ---- Function _Syntax_: ! `RESULT = TIME()' _Return value_: ! The return value is a scalar of type `INTEGER(4)'. _See also_: ! *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK::, ! *note TIME8:: !  File: gfortran.info, Node: TIME8, Next: TINY, Prev: TIME, Up: Intrinsic Procedures ! 9.259 `TIME8' -- Time function (64-bit) ======================================= _Description_: Returns the current time encoded as an integer (in the manner of ! the function `time(3)' in the C standard library). This value is ! suitable for passing to `CTIME', `GMTIME', and `LTIME'. _Warning:_ this intrinsic does not increase the range of the timing ! values over that returned by `time(3)'. On a system with a 32-bit ! `time(3)', `TIME8' will return a 32-bit value, even though it is ! converted to a 64-bit `INTEGER(8)' value. That means overflows of ! the 32-bit value can still occur. Therefore, the values returned by this intrinsic might be or become negative or numerically less than previous values during a single run of the compiled program. *************** _Class_: *** 16766,16789 **** Function _Syntax_: ! 'RESULT = TIME8()' _Return value_: ! The return value is a scalar of type 'INTEGER(8)'. _See also_: *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK8::, *note TIME::  File: gfortran.info, Node: TINY, Next: TRAILZ, Prev: TIME8, Up: Intrinsic Procedures ! 9.260 'TINY' -- Smallest positive number of a real kind ======================================================= _Description_: ! 'TINY(X)' returns the smallest positive (non zero) number in the ! model of the type of 'X'. _Standard_: Fortran 95 and later --- 16943,16967 ---- Function _Syntax_: ! `RESULT = TIME8()' _Return value_: ! The return value is a scalar of type `INTEGER(8)'. _See also_: *note CTIME::, *note GMTIME::, *note LTIME::, *note MCLOCK8::, *note TIME:: +  File: gfortran.info, Node: TINY, Next: TRAILZ, Prev: TIME8, Up: Intrinsic Procedures ! 9.260 `TINY' -- Smallest positive number of a real kind ======================================================= _Description_: ! `TINY(X)' returns the smallest positive (non zero) number in the ! model of the type of `X'. _Standard_: Fortran 95 and later *************** _Class_: *** 16792,16816 **** Inquiry function _Syntax_: ! 'RESULT = TINY(X)' _Arguments_: ! X Shall be of type 'REAL'. _Return value_: The return value is of the same type and kind as X _Example_: ! See 'HUGE' for an example.  File: gfortran.info, Node: TRAILZ, Next: TRANSFER, Prev: TINY, Up: Intrinsic Procedures ! 9.261 'TRAILZ' -- Number of trailing zero bits of an integer ============================================================ _Description_: ! 'TRAILZ' returns the number of trailing zero bits of an integer. _Standard_: Fortran 2008 and later --- 16970,16994 ---- Inquiry function _Syntax_: ! `RESULT = TINY(X)' _Arguments_: ! X Shall be of type `REAL'. _Return value_: The return value is of the same type and kind as X _Example_: ! See `HUGE' for an example.  File: gfortran.info, Node: TRAILZ, Next: TRANSFER, Prev: TINY, Up: Intrinsic Procedures ! 9.261 `TRAILZ' -- Number of trailing zero bits of an integer ============================================================ _Description_: ! `TRAILZ' returns the number of trailing zero bits of an integer. _Standard_: Fortran 2008 and later *************** _Class_: *** 16819,16832 **** Elemental function _Syntax_: ! 'RESULT = TRAILZ(I)' _Arguments_: ! I Shall be of type 'INTEGER'. _Return value_: ! The type of the return value is the default 'INTEGER'. If all the ! bits of 'I' are zero, the result value is 'BIT_SIZE(I)'. _Example_: PROGRAM test_trailz --- 16997,17010 ---- Elemental function _Syntax_: ! `RESULT = TRAILZ(I)' _Arguments_: ! I Shall be of type `INTEGER'. _Return value_: ! The type of the return value is the default `INTEGER'. If all the ! bits of `I' are zero, the result value is `BIT_SIZE(I)'. _Example_: PROGRAM test_trailz *************** _See also_: *** 16839,16845 ****  File: gfortran.info, Node: TRANSFER, Next: TRANSPOSE, Prev: TRAILZ, Up: Intrinsic Procedures ! 9.262 'TRANSFER' -- Transfer bit patterns ========================================= _Description_: --- 17017,17023 ----  File: gfortran.info, Node: TRANSFER, Next: TRANSPOSE, Prev: TRAILZ, Up: Intrinsic Procedures ! 9.262 `TRANSFER' -- Transfer bit patterns ========================================= _Description_: *************** _Class_: *** 16857,16868 **** Transformational function _Syntax_: ! 'RESULT = TRANSFER(SOURCE, MOLD[, SIZE])' _Arguments_: ! SOURCE Shall be a scalar or an array of any type. ! MOLD Shall be a scalar or an array of any type. ! SIZE (Optional) shall be a scalar of type 'INTEGER'. _Return value_: The result has the same type as MOLD, with the bit level --- 17035,17046 ---- Transformational function _Syntax_: ! `RESULT = TRANSFER(SOURCE, MOLD[, SIZE])' _Arguments_: ! SOURCE Shall be a scalar or an array of any type. ! MOLD Shall be a scalar or an array of any type. ! SIZE (Optional) shall be a scalar of type `INTEGER'. _Return value_: The result has the same type as MOLD, with the bit level *************** _Return value_: *** 16870,16876 **** one-dimensional array of length SIZE. If SIZE is absent but MOLD is an array (of any size or shape), the result is a one- dimensional array of the minimum length needed to contain the ! entirety of the bitwise representation of SOURCE. If SIZE is absent and MOLD is a scalar, the result is a scalar. If the bitwise representation of the result is longer than that of --- 17048,17054 ---- one-dimensional array of length SIZE. If SIZE is absent but MOLD is an array (of any size or shape), the result is a one- dimensional array of the minimum length needed to contain the ! entirety of the bitwise representation of SOURCE. If SIZE is absent and MOLD is a scalar, the result is a scalar. If the bitwise representation of the result is longer than that of *************** _Return value_: *** 16880,16888 **** When the resulting bit representation does not correspond to a valid representation of a variable of the same type as MOLD, the results are undefined, and subsequent operations on the result ! cannot be guaranteed to produce sensible behavior. For example, it ! is possible to create 'LOGICAL' variables for which 'VAR' and ! '.NOT.VAR' both appear to be true. _Example_: PROGRAM test_transfer --- 17058,17066 ---- When the resulting bit representation does not correspond to a valid representation of a variable of the same type as MOLD, the results are undefined, and subsequent operations on the result ! cannot be guaranteed to produce sensible behavior. For example, ! it is possible to create `LOGICAL' variables for which `VAR' and ! `.NOT.VAR' both appear to be true. _Example_: PROGRAM test_transfer *************** _Example_: *** 16893,16904 ****  File: gfortran.info, Node: TRANSPOSE, Next: TRIM, Prev: TRANSFER, Up: Intrinsic Procedures ! 9.263 'TRANSPOSE' -- Transpose an array of rank two =================================================== _Description_: ! Transpose an array of rank two. Element (i, j) of the result has ! the value 'MATRIX(j, i)', for all i, j. _Standard_: Fortran 95 and later --- 17071,17082 ----  File: gfortran.info, Node: TRANSPOSE, Next: TRIM, Prev: TRANSFER, Up: Intrinsic Procedures ! 9.263 `TRANSPOSE' -- Transpose an array of rank two =================================================== _Description_: ! Transpose an array of rank two. Element (i, j) of the result has ! the value `MATRIX(j, i)', for all i, j. _Standard_: Fortran 95 and later *************** _Class_: *** 16907,16926 **** Transformational function _Syntax_: ! 'RESULT = TRANSPOSE(MATRIX)' _Arguments_: ! MATRIX Shall be an array of any type and have a rank of ! two. _Return value_: ! The result has the same type as MATRIX, and has shape '(/ m, n /)' ! if MATRIX has shape '(/ n, m /)'.  File: gfortran.info, Node: TRIM, Next: TTYNAM, Prev: TRANSPOSE, Up: Intrinsic Procedures ! 9.264 'TRIM' -- Remove trailing blank characters of a string ============================================================ _Description_: --- 17085,17104 ---- Transformational function _Syntax_: ! `RESULT = TRANSPOSE(MATRIX)' _Arguments_: ! MATRIX Shall be an array of any type and have a rank ! of two. _Return value_: ! The result has the same type as MATRIX, and has shape `(/ m, n /)' ! if MATRIX has shape `(/ n, m /)'.  File: gfortran.info, Node: TRIM, Next: TTYNAM, Prev: TRANSPOSE, Up: Intrinsic Procedures ! 9.264 `TRIM' -- Remove trailing blank characters of a string ============================================================ _Description_: *************** _Class_: *** 16933,16945 **** Transformational function _Syntax_: ! 'RESULT = TRIM(STRING)' _Arguments_: ! STRING Shall be a scalar of type 'CHARACTER'. _Return value_: ! A scalar of type 'CHARACTER' which length is that of STRING less the number of trailing blanks. _Example_: --- 17111,17123 ---- Transformational function _Syntax_: ! `RESULT = TRIM(STRING)' _Arguments_: ! STRING Shall be a scalar of type `CHARACTER'. _Return value_: ! A scalar of type `CHARACTER' which length is that of STRING less the number of trailing blanks. _Example_: *************** _See also_: *** 16954,16965 ****  File: gfortran.info, Node: TTYNAM, Next: UBOUND, Prev: TRIM, Up: Intrinsic Procedures ! 9.265 'TTYNAM' -- Get the name of a terminal device. ==================================================== _Description_: ! Get the name of a terminal device. For more information, see ! 'ttyname(3)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 17132,17143 ----  File: gfortran.info, Node: TTYNAM, Next: UBOUND, Prev: TRIM, Up: Intrinsic Procedures ! 9.265 `TTYNAM' -- Get the name of a terminal device. ==================================================== _Description_: ! Get the name of a terminal device. For more information, see ! `ttyname(3)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 16971,16982 **** Subroutine, function _Syntax_: ! 'CALL TTYNAM(UNIT, NAME)' ! 'NAME = TTYNAM(UNIT)' _Arguments_: ! UNIT Shall be a scalar 'INTEGER'. ! NAME Shall be of type 'CHARACTER'. _Example_: PROGRAM test_ttynam --- 17149,17160 ---- Subroutine, function _Syntax_: ! `CALL TTYNAM(UNIT, NAME)' ! `NAME = TTYNAM(UNIT)' _Arguments_: ! UNIT Shall be a scalar `INTEGER'. ! NAME Shall be of type `CHARACTER'. _Example_: PROGRAM test_ttynam *************** _See also_: *** 16992,17003 ****  File: gfortran.info, Node: UBOUND, Next: UCOBOUND, Prev: TTYNAM, Up: Intrinsic Procedures ! 9.266 'UBOUND' -- Upper dimension bounds of an array ==================================================== _Description_: ! Returns the upper bounds of an array, or a single upper bound along ! the DIM dimension. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later --- 17170,17182 ----  File: gfortran.info, Node: UBOUND, Next: UCOBOUND, Prev: TTYNAM, Up: Intrinsic Procedures ! 9.266 `UBOUND' -- Upper dimension bounds of an array ==================================================== _Description_: ! Returns the upper bounds of an array, or a single upper bound ! along the DIM dimension. ! _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later *************** _Class_: *** 17005,17028 **** Inquiry function _Syntax_: ! 'RESULT = UBOUND(ARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an array, of any type. ! DIM (Optional) Shall be a scalar 'INTEGER'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the upper bounds of ARRAY. If DIM is present, the result is a scalar corresponding to the upper ! bound of the array along that dimension. If ARRAY is an expression ! rather than a whole array or array structure component, or if it ! has a zero extent along the relevant dimension, the upper bound is ! taken to be the number of elements along the relevant dimension. _See also_: *note LBOUND::, *note LCOBOUND:: --- 17184,17208 ---- Inquiry function _Syntax_: ! `RESULT = UBOUND(ARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an array, of any type. ! DIM (Optional) Shall be a scalar `INTEGER'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the upper bounds of ARRAY. If DIM is present, the result is a scalar corresponding to the upper ! bound of the array along that dimension. If ARRAY is an ! expression rather than a whole array or array structure component, ! or if it has a zero extent along the relevant dimension, the upper ! bound is taken to be the number of elements along the relevant ! dimension. _See also_: *note LBOUND::, *note LCOBOUND:: *************** _See also_: *** 17030,17041 ****  File: gfortran.info, Node: UCOBOUND, Next: UMASK, Prev: UBOUND, Up: Intrinsic Procedures ! 9.267 'UCOBOUND' -- Upper codimension bounds of an array ======================================================== _Description_: Returns the upper cobounds of a coarray, or a single upper cobound along the DIM codimension. _Standard_: Fortran 2008 and later --- 17210,17222 ----  File: gfortran.info, Node: UCOBOUND, Next: UMASK, Prev: UBOUND, Up: Intrinsic Procedures ! 9.267 `UCOBOUND' -- Upper codimension bounds of an array ======================================================== _Description_: Returns the upper cobounds of a coarray, or a single upper cobound along the DIM codimension. + _Standard_: Fortran 2008 and later *************** _Class_: *** 17043,17059 **** Inquiry function _Syntax_: ! 'RESULT = UCOBOUND(COARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an coarray, of any type. ! DIM (Optional) Shall be a scalar 'INTEGER'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the lower cobounds of COARRAY. If DIM is present, the result is a scalar corresponding to the --- 17224,17240 ---- Inquiry function _Syntax_: ! `RESULT = UCOBOUND(COARRAY [, DIM [, KIND]])' _Arguments_: ! ARRAY Shall be an coarray, of any type. ! DIM (Optional) Shall be a scalar `INTEGER'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. If DIM is absent, the result is an array of the lower cobounds of COARRAY. If DIM is present, the result is a scalar corresponding to the *************** _See also_: *** 17065,17077 ****  File: gfortran.info, Node: UMASK, Next: UNLINK, Prev: UCOBOUND, Up: Intrinsic Procedures ! 9.268 'UMASK' -- Set the file creation mask =========================================== _Description_: ! Sets the file creation mask to MASK. If called as a function, it ! returns the old value. If called as a subroutine and argument OLD ! if it is supplied, it is set to the old value. See 'umask(2)'. _Standard_: GNU extension --- 17246,17258 ----  File: gfortran.info, Node: UMASK, Next: UNLINK, Prev: UCOBOUND, Up: Intrinsic Procedures ! 9.268 `UMASK' -- Set the file creation mask =========================================== _Description_: ! Sets the file creation mask to MASK. If called as a function, it ! returns the old value. If called as a subroutine and argument OLD ! if it is supplied, it is set to the old value. See `umask(2)'. _Standard_: GNU extension *************** _Class_: *** 17080,17104 **** Subroutine, function _Syntax_: ! 'CALL UMASK(MASK [, OLD])' ! 'OLD = UMASK(MASK)' _Arguments_: ! MASK Shall be a scalar of type 'INTEGER'. ! OLD (Optional) Shall be a scalar of type 'INTEGER'.  File: gfortran.info, Node: UNLINK, Next: UNPACK, Prev: UMASK, Up: Intrinsic Procedures ! 9.269 'UNLINK' -- Remove a file from the file system ==================================================== _Description_: ! Unlinks the file PATH. A null character ('CHAR(0)') can be used to ! mark the end of the name in PATH; otherwise, trailing blanks in the ! file name are ignored. If the STATUS argument is supplied, it contains 0 on success or a nonzero error code upon return; see ! 'unlink(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. --- 17261,17286 ---- Subroutine, function _Syntax_: ! `CALL UMASK(MASK [, OLD])' ! `OLD = UMASK(MASK)' _Arguments_: ! MASK Shall be a scalar of type `INTEGER'. ! OLD (Optional) Shall be a scalar of type `INTEGER'. !  File: gfortran.info, Node: UNLINK, Next: UNPACK, Prev: UMASK, Up: Intrinsic Procedures ! 9.269 `UNLINK' -- Remove a file from the file system ==================================================== _Description_: ! Unlinks the file PATH. A null character (`CHAR(0)') can be used to ! mark the end of the name in PATH; otherwise, trailing blanks in ! the file name are ignored. If the STATUS argument is supplied, it contains 0 on success or a nonzero error code upon return; see ! `unlink(2)'. This intrinsic is provided in both subroutine and function forms; however, only one form can be used in any given program unit. *************** _Class_: *** 17110,17121 **** Subroutine, function _Syntax_: ! 'CALL UNLINK(PATH [, STATUS])' ! 'STATUS = UNLINK(PATH)' _Arguments_: ! PATH Shall be of default 'CHARACTER' type. ! STATUS (Optional) Shall be of default 'INTEGER' type. _See also_: *note LINK::, *note SYMLNK:: --- 17292,17303 ---- Subroutine, function _Syntax_: ! `CALL UNLINK(PATH [, STATUS])' ! `STATUS = UNLINK(PATH)' _Arguments_: ! PATH Shall be of default `CHARACTER' type. ! STATUS (Optional) Shall be of default `INTEGER' type. _See also_: *note LINK::, *note SYMLNK:: *************** _See also_: *** 17123,17129 ****  File: gfortran.info, Node: UNPACK, Next: VERIFY, Prev: UNLINK, Up: Intrinsic Procedures ! 9.270 'UNPACK' -- Unpack an array of rank one into an array =========================================================== _Description_: --- 17305,17311 ----  File: gfortran.info, Node: UNPACK, Next: VERIFY, Prev: UNLINK, Up: Intrinsic Procedures ! 9.270 `UNPACK' -- Unpack an array of rank one into an array =========================================================== _Description_: *************** _Class_: *** 17136,17153 **** Transformational function _Syntax_: ! 'RESULT = UNPACK(VECTOR, MASK, FIELD)' _Arguments_: ! VECTOR Shall be an array of any type and rank one. It ! shall have at least as many elements as MASK has ! 'TRUE' values. ! MASK Shall be an array of type 'LOGICAL'. ! FIELD Shall be of the same type as VECTOR and have the ! same shape as MASK. _Return value_: ! The resulting array corresponds to FIELD with 'TRUE' elements of MASK replaced by values from VECTOR in array element order. _Example_: --- 17318,17335 ---- Transformational function _Syntax_: ! `RESULT = UNPACK(VECTOR, MASK, FIELD)' _Arguments_: ! VECTOR Shall be an array of any type and rank one. It ! shall have at least as many elements as MASK ! has `TRUE' values. ! MASK Shall be an array of type `LOGICAL'. ! FIELD Shall be of the same type as VECTOR and have ! the same shape as MASK. _Return value_: ! The resulting array corresponds to FIELD with `TRUE' elements of MASK replaced by values from VECTOR in array element order. _Example_: *************** _See also_: *** 17166,17182 ****  File: gfortran.info, Node: VERIFY, Next: XOR, Prev: UNPACK, Up: Intrinsic Procedures ! 9.271 'VERIFY' -- Scan a string for characters not a given set ============================================================== _Description_: Verifies that all the characters in STRING belong to the set of characters in SET. ! If BACK is either absent or equals 'FALSE', this function returns the position of the leftmost character of STRING that is not in ! SET. If BACK equals 'TRUE', the rightmost position is returned. ! If all characters of STRING are found in SET, the result is zero. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later --- 17348,17364 ----  File: gfortran.info, Node: VERIFY, Next: XOR, Prev: UNPACK, Up: Intrinsic Procedures ! 9.271 `VERIFY' -- Scan a string for characters not a given set ============================================================== _Description_: Verifies that all the characters in STRING belong to the set of characters in SET. ! If BACK is either absent or equals `FALSE', this function returns the position of the leftmost character of STRING that is not in ! SET. If BACK equals `TRUE', the rightmost position is returned. If ! all characters of STRING are found in SET, the result is zero. _Standard_: Fortran 95 and later, with KIND argument Fortran 2003 and later *************** _Class_: *** 17185,17202 **** Elemental function _Syntax_: ! 'RESULT = VERIFY(STRING, SET[, BACK [, KIND]])' _Arguments_: ! STRING Shall be of type 'CHARACTER'. ! SET Shall be of type 'CHARACTER'. ! BACK (Optional) shall be of type 'LOGICAL'. ! KIND (Optional) An 'INTEGER' initialization ! expression indicating the kind parameter of the ! result. _Return value_: ! The return value is of type 'INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: --- 17367,17384 ---- Elemental function _Syntax_: ! `RESULT = VERIFY(STRING, SET[, BACK [, KIND]])' _Arguments_: ! STRING Shall be of type `CHARACTER'. ! SET Shall be of type `CHARACTER'. ! BACK (Optional) shall be of type `LOGICAL'. ! KIND (Optional) An `INTEGER' initialization ! expression indicating the kind parameter of ! the result. _Return value_: ! The return value is of type `INTEGER' and of kind KIND. If KIND is absent, the return value is of default integer kind. _Example_: *************** _See also_: *** 17214,17220 ****  File: gfortran.info, Node: XOR, Prev: VERIFY, Up: Intrinsic Procedures ! 9.272 'XOR' -- Bitwise logical exclusive OR =========================================== _Description_: --- 17396,17402 ----  File: gfortran.info, Node: XOR, Prev: VERIFY, Up: Intrinsic Procedures ! 9.272 `XOR' -- Bitwise logical exclusive OR =========================================== _Description_: *************** _Description_: *** 17223,17229 **** This intrinsic routine is provided for backwards compatibility with GNU Fortran 77. For integer arguments, programmers should consider the use of the *note IEOR:: intrinsic and for logical arguments the ! '.NEQV.' operator, which are both defined by the Fortran standard. _Standard_: GNU extension --- 17405,17411 ---- This intrinsic routine is provided for backwards compatibility with GNU Fortran 77. For integer arguments, programmers should consider the use of the *note IEOR:: intrinsic and for logical arguments the ! `.NEQV.' operator, which are both defined by the Fortran standard. _Standard_: GNU extension *************** _Class_: *** 17232,17249 **** Function _Syntax_: ! 'RESULT = XOR(I, J)' _Arguments_: ! I The type shall be either a scalar 'INTEGER' type ! or a scalar 'LOGICAL' type. ! J The type shall be the same as the type of I. _Return value_: ! The return type is either a scalar 'INTEGER' or a scalar 'LOGICAL'. ! If the kind type parameters differ, then the smaller kind type is ! implicitly converted to larger kind, and the return has the larger ! kind. _Example_: PROGRAM test_xor --- 17414,17431 ---- Function _Syntax_: ! `RESULT = XOR(I, J)' _Arguments_: ! I The type shall be either a scalar `INTEGER' ! type or a scalar `LOGICAL' type. ! J The type shall be the same as the type of I. _Return value_: ! The return type is either a scalar `INTEGER' or a scalar ! `LOGICAL'. If the kind type parameters differ, then the smaller ! kind type is implicitly converted to larger kind, and the return ! has the larger kind. _Example_: PROGRAM test_xor *************** File: gfortran.info, Node: Intrinsic Mo *** 17275,17395 ****  File: gfortran.info, Node: ISO_FORTRAN_ENV, Next: ISO_C_BINDING, Up: Intrinsic Modules ! 10.1 'ISO_FORTRAN_ENV' ====================== _Standard_: Fortran 2003 and later, except when otherwise noted ! The 'ISO_FORTRAN_ENV' module provides the following scalar default-integer named constants: ! 'ATOMIC_INT_KIND': Default-kind integer constant to be used as kind parameter when ! defining integer variables used in atomic operations. (Fortran 2008 or later.) ! 'ATOMIC_LOGICAL_KIND': Default-kind integer constant to be used as kind parameter when ! defining logical variables used in atomic operations. (Fortran 2008 or later.) ! 'CHARACTER_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the 'CHARACTER' type. (Fortran 2008 or later.) ! 'CHARACTER_STORAGE_SIZE': Size in bits of the character storage unit. ! 'ERROR_UNIT': Identifies the preconnected unit used for error reporting. ! 'FILE_STORAGE_SIZE': Size in bits of the file-storage unit. ! 'INPUT_UNIT': ! Identifies the preconnected unit identified by the asterisk ('*') ! in 'READ' statement. ! 'INT8', 'INT16', 'INT32', 'INT64': ! Kind type parameters to specify an INTEGER type with a storage size ! of 16, 32, and 64 bits. It is negative if a target platform does ! not support the particular kind. (Fortran 2008 or later.) ! 'INTEGER_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the 'INTEGER' type. (Fortran 2008 or later.) ! 'IOSTAT_END': ! The value assigned to the variable passed to the 'IOSTAT=' specifier of an input/output statement if an end-of-file condition occurred. ! 'IOSTAT_EOR': ! The value assigned to the variable passed to the 'IOSTAT=' specifier of an input/output statement if an end-of-record condition occurred. ! 'IOSTAT_INQUIRE_INTERNAL_UNIT': ! Scalar default-integer constant, used by 'INQUIRE' for the ! 'IOSTAT=' specifier to denote an that a unit number identifies an ! internal unit. (Fortran 2008 or later.) ! 'NUMERIC_STORAGE_SIZE': The size in bits of the numeric storage unit. ! 'LOGICAL_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the 'LOGICAL' type. (Fortran 2008 or later.) ! 'OUTPUT_UNIT': ! Identifies the preconnected unit identified by the asterisk ('*') ! in 'WRITE' statement. ! 'REAL32', 'REAL64', 'REAL128': Kind type parameters to specify a REAL type with a storage size of ! 32, 64, and 128 bits. It is negative if a target platform does not ! support the particular kind. (Fortran 2008 or later.) ! 'REAL_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the 'REAL' type. (Fortran 2008 or later.) ! 'STAT_LOCKED': Scalar default-integer constant used as STAT= return value by ! 'LOCK' to denote that the lock variable is locked by the executing ! image. (Fortran 2008 or later.) ! 'STAT_LOCKED_OTHER_IMAGE': Scalar default-integer constant used as STAT= return value by ! 'UNLOCK' to denote that the lock variable is locked by another ! image. (Fortran 2008 or later.) ! 'STAT_STOPPED_IMAGE': Positive, scalar default-integer constant used as STAT= return value if the argument in the statement requires synchronisation with an image, which has initiated the termination of the ! execution. (Fortran 2008 or later.) ! 'STAT_FAILED_IMAGE': Positive, scalar default-integer constant used as STAT= return value if the argument in the statement requires communication with ! an image, which has is in the failed state. (TS 18508 or later.) ! 'STAT_UNLOCKED': Scalar default-integer constant used as STAT= return value by ! 'UNLOCK' to denote that the lock variable is unlocked. (Fortran 2008 or later.) The module provides the following derived type: ! 'LOCK_TYPE': ! Derived type with private components to be use with the 'LOCK' and ! 'UNLOCK' statement. A variable of its type has to be always declared as coarray and may not appear in a variable-definition context. (Fortran 2008 or later.) --- 17457,17577 ----  File: gfortran.info, Node: ISO_FORTRAN_ENV, Next: ISO_C_BINDING, Up: Intrinsic Modules ! 10.1 `ISO_FORTRAN_ENV' ====================== _Standard_: Fortran 2003 and later, except when otherwise noted ! The `ISO_FORTRAN_ENV' module provides the following scalar default-integer named constants: ! `ATOMIC_INT_KIND': Default-kind integer constant to be used as kind parameter when ! defining integer variables used in atomic operations. (Fortran 2008 or later.) ! `ATOMIC_LOGICAL_KIND': Default-kind integer constant to be used as kind parameter when ! defining logical variables used in atomic operations. (Fortran 2008 or later.) ! `CHARACTER_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the `CHARACTER' type. (Fortran 2008 or later.) ! `CHARACTER_STORAGE_SIZE': Size in bits of the character storage unit. ! `ERROR_UNIT': Identifies the preconnected unit used for error reporting. ! `FILE_STORAGE_SIZE': Size in bits of the file-storage unit. ! `INPUT_UNIT': ! Identifies the preconnected unit identified by the asterisk (`*') ! in `READ' statement. ! `INT8', `INT16', `INT32', `INT64': ! Kind type parameters to specify an INTEGER type with a storage ! size of 16, 32, and 64 bits. It is negative if a target platform ! does not support the particular kind. (Fortran 2008 or later.) ! `INTEGER_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the `INTEGER' type. (Fortran 2008 or later.) ! `IOSTAT_END': ! The value assigned to the variable passed to the `IOSTAT=' specifier of an input/output statement if an end-of-file condition occurred. ! `IOSTAT_EOR': ! The value assigned to the variable passed to the `IOSTAT=' specifier of an input/output statement if an end-of-record condition occurred. ! `IOSTAT_INQUIRE_INTERNAL_UNIT': ! Scalar default-integer constant, used by `INQUIRE' for the ! `IOSTAT=' specifier to denote an that a unit number identifies an ! internal unit. (Fortran 2008 or later.) ! `NUMERIC_STORAGE_SIZE': The size in bits of the numeric storage unit. ! `LOGICAL_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the `LOGICAL' type. (Fortran 2008 or later.) ! `OUTPUT_UNIT': ! Identifies the preconnected unit identified by the asterisk (`*') ! in `WRITE' statement. ! `REAL32', `REAL64', `REAL128': Kind type parameters to specify a REAL type with a storage size of ! 32, 64, and 128 bits. It is negative if a target platform does not ! support the particular kind. (Fortran 2008 or later.) ! `REAL_KINDS': Default-kind integer constant array of rank one containing the ! supported kind parameters of the `REAL' type. (Fortran 2008 or later.) ! `STAT_LOCKED': Scalar default-integer constant used as STAT= return value by ! `LOCK' to denote that the lock variable is locked by the executing ! image. (Fortran 2008 or later.) ! `STAT_LOCKED_OTHER_IMAGE': Scalar default-integer constant used as STAT= return value by ! `UNLOCK' to denote that the lock variable is locked by another ! image. (Fortran 2008 or later.) ! `STAT_STOPPED_IMAGE': Positive, scalar default-integer constant used as STAT= return value if the argument in the statement requires synchronisation with an image, which has initiated the termination of the ! execution. (Fortran 2008 or later.) ! `STAT_FAILED_IMAGE': Positive, scalar default-integer constant used as STAT= return value if the argument in the statement requires communication with ! an image, which has is in the failed state. (TS 18508 or later.) ! `STAT_UNLOCKED': Scalar default-integer constant used as STAT= return value by ! `UNLOCK' to denote that the lock variable is unlocked. (Fortran 2008 or later.) The module provides the following derived type: ! `LOCK_TYPE': ! Derived type with private components to be use with the `LOCK' and ! `UNLOCK' statement. A variable of its type has to be always declared as coarray and may not appear in a variable-definition context. (Fortran 2008 or later.) *************** COMPILER_OPTIONS:: and *note COMPILER_VE *** 17399,17405 ****  File: gfortran.info, Node: ISO_C_BINDING, Next: IEEE modules, Prev: ISO_FORTRAN_ENV, Up: Intrinsic Modules ! 10.2 'ISO_C_BINDING' ==================== _Standard_: --- 17581,17587 ----  File: gfortran.info, Node: ISO_C_BINDING, Next: IEEE modules, Prev: ISO_FORTRAN_ENV, Up: Intrinsic Modules ! 10.2 `ISO_C_BINDING' ==================== _Standard_: *************** _Standard_: *** 17409,17588 **** definition can be found in the section Intrinsic Procedures of this manual. ! 'C_ASSOCIATED' ! 'C_F_POINTER' ! 'C_F_PROCPOINTER' ! 'C_FUNLOC' ! 'C_LOC' ! 'C_SIZEOF' ! The 'ISO_C_BINDING' module provides the following named constants of type default integer, which can be used as KIND type parameters. In addition to the integer named constants required by the Fortran ! 2003 standard and 'C_PTRDIFF_T' of TS 29113, GNU Fortran provides as an extension named constants for the 128-bit integer types supported by the ! C compiler: 'C_INT128_T, C_INT_LEAST128_T, C_INT_FAST128_T'. ! Furthermore, if '__float128' is supported in C, the named constants ! 'C_FLOAT128, C_FLOAT128_COMPLEX' are defined. Fortran Named constant C type Extension ! Type ! 'INTEGER' 'C_INT' 'int' ! 'INTEGER' 'C_SHORT' 'short int' ! 'INTEGER' 'C_LONG' 'long int' ! 'INTEGER' 'C_LONG_LONG' 'long long int' ! 'INTEGER' 'C_SIGNED_CHAR' 'signed char'/'unsigned ! char' ! 'INTEGER' 'C_SIZE_T' 'size_t' ! 'INTEGER' 'C_INT8_T' 'int8_t' ! 'INTEGER' 'C_INT16_T' 'int16_t' ! 'INTEGER' 'C_INT32_T' 'int32_t' ! 'INTEGER' 'C_INT64_T' 'int64_t' ! 'INTEGER' 'C_INT128_T' 'int128_t' Ext. ! 'INTEGER' 'C_INT_LEAST8_T' 'int_least8_t' ! 'INTEGER' 'C_INT_LEAST16_T' 'int_least16_t' ! 'INTEGER' 'C_INT_LEAST32_T' 'int_least32_t' ! 'INTEGER' 'C_INT_LEAST64_T' 'int_least64_t' ! 'INTEGER' 'C_INT_LEAST128_T' 'int_least128_t' Ext. ! 'INTEGER' 'C_INT_FAST8_T' 'int_fast8_t' ! 'INTEGER' 'C_INT_FAST16_T' 'int_fast16_t' ! 'INTEGER' 'C_INT_FAST32_T' 'int_fast32_t' ! 'INTEGER' 'C_INT_FAST64_T' 'int_fast64_t' ! 'INTEGER' 'C_INT_FAST128_T' 'int_fast128_t' Ext. ! 'INTEGER' 'C_INTMAX_T' 'intmax_t' ! 'INTEGER' 'C_INTPTR_T' 'intptr_t' ! 'INTEGER' 'C_PTRDIFF_T' 'intptr_t' TS 29113 ! 'REAL' 'C_FLOAT' 'float' ! 'REAL' 'C_DOUBLE' 'double' ! 'REAL' 'C_LONG_DOUBLE' 'long double' ! 'REAL' 'C_FLOAT128' '__float128' Ext. ! 'COMPLEX' 'C_FLOAT_COMPLEX' 'float _Complex' ! 'COMPLEX' 'C_DOUBLE_COMPLEX' 'double _Complex' ! 'COMPLEX' 'C_LONG_DOUBLE_COMPLEX' 'long double _Complex' ! 'REAL' 'C_FLOAT128_COMPLEX' '__float128 _Complex' Ext. ! 'LOGICAL' 'C_BOOL' '_Bool' ! 'CHARACTER' 'C_CHAR' 'char' Additionally, the following parameters of type ! 'CHARACTER(KIND=C_CHAR)' are defined. Name C definition Value ! 'C_NULL_CHAR' null character ''\0'' ! 'C_ALERT' alert ''\a'' ! 'C_BACKSPACE' backspace ''\b'' ! 'C_FORM_FEED' form feed ''\f'' ! 'C_NEW_LINE' new line ''\n'' ! 'C_CARRIAGE_RETURN'carriage return ''\r'' ! 'C_HORIZONTAL_TAB'horizontal tab ''\t'' ! 'C_VERTICAL_TAB'vertical tab ''\v'' Moreover, the following two named constants are defined: Name Type ! 'C_NULL_PTR' 'C_PTR' ! 'C_NULL_FUNPTR''C_FUNPTR' ! Both are equivalent to the value 'NULL' in C.  File: gfortran.info, Node: IEEE modules, Next: OpenMP Modules OMP_LIB and OMP_LIB_KINDS, Prev: ISO_C_BINDING, Up: Intrinsic Modules ! 10.3 IEEE modules: 'IEEE_EXCEPTIONS', 'IEEE_ARITHMETIC', and 'IEEE_FEATURES' ============================================================================ _Standard_: Fortran 2003 and later ! The 'IEEE_EXCEPTIONS', 'IEEE_ARITHMETIC', and 'IEEE_FEATURES' intrinsic modules provide support for exceptions and IEEE arithmetic, as defined in Fortran 2003 and later standards, and the IEC 60559:1989 standard (_Binary floating-point arithmetic for microprocessor ! systems_). These modules are only provided on the following supported platforms: * i386 and x86_64 processors * platforms which use the GNU C Library (glibc) * platforms with support for SysV/386 routines for floating point interface (including Solaris and BSDs) * platforms with the AIX OS For full compliance with the Fortran standards, code using the ! 'IEEE_EXCEPTIONS' or 'IEEE_ARITHMETIC' modules should be compiled with ! the following options: '-fno-unsafe-math-optimizations -frounding-math -fsignaling-nans'.  File: gfortran.info, Node: OpenMP Modules OMP_LIB and OMP_LIB_KINDS, Next: OpenACC Module OPENACC, Prev: IEEE modules, Up: Intrinsic Modules ! 10.4 OpenMP Modules 'OMP_LIB' and 'OMP_LIB_KINDS' ================================================= _Standard_: OpenMP Application Program Interface v4.0 The OpenMP Fortran runtime library routines are provided both in a ! form of two Fortran 90 modules, named 'OMP_LIB' and 'OMP_LIB_KINDS', and ! in a form of a Fortran 'include' file named 'omp_lib.h'. The procedures ! provided by 'OMP_LIB' can be found in the *note Introduction: ! (libgomp)Top. manual, the named constants defined in the modules are ! listed below. For details refer to the actual OpenMP Application Program Interface v4.0 (http://www.openmp.org/mp-documents/OpenMP4.0.0.pdf). ! 'OMP_LIB_KINDS' provides the following scalar default-integer named constants: ! 'omp_lock_kind' ! 'omp_nest_lock_kind' ! 'omp_proc_bind_kind' ! 'omp_sched_kind' ! 'OMP_LIB' provides the scalar default-integer named constant ! 'openmp_version' with a value of the form YYYYMM, where 'yyyy' is the year and MM the month of the OpenMP version; for OpenMP v4.0 the value ! is '201307'. The following scalar integer named constants of the kind ! 'omp_sched_kind': ! 'omp_sched_static' ! 'omp_sched_dynamic' ! 'omp_sched_guided' ! 'omp_sched_auto' And the following scalar integer named constants of the kind ! 'omp_proc_bind_kind': ! 'omp_proc_bind_false' ! 'omp_proc_bind_true' ! 'omp_proc_bind_master' ! 'omp_proc_bind_close' ! 'omp_proc_bind_spread'  File: gfortran.info, Node: OpenACC Module OPENACC, Prev: OpenMP Modules OMP_LIB and OMP_LIB_KINDS, Up: Intrinsic Modules ! 10.5 OpenACC Module 'OPENACC' ============================= _Standard_: OpenACC Application Programming Interface v2.0 The OpenACC Fortran runtime library routines are provided both in a ! form of a Fortran 90 module, named 'OPENACC', and in form of a Fortran ! 'include' file named 'openacc_lib.h'. The procedures provided by ! 'OPENACC' can be found in the *note Introduction: (libgomp)Top. manual, the named constants defined in the modules are listed below. For details refer to the actual OpenACC Application Programming Interface v2.0 (http://www.openacc.org/). ! 'OPENACC' provides the scalar default-integer named constant ! 'openacc_version' with a value of the form YYYYMM, where 'yyyy' is the ! year and MM the month of the OpenACC version; for OpenACC v2.0 the value ! is '201306'.  File: gfortran.info, Node: Contributing, Next: Copying, Prev: Intrinsic Modules, Up: Top --- 17591,17788 ---- definition can be found in the section Intrinsic Procedures of this manual. ! `C_ASSOCIATED' ! `C_F_POINTER' ! ! `C_F_PROCPOINTER' ! ! `C_FUNLOC' ! ! `C_LOC' ! ! `C_SIZEOF' ! ! The `ISO_C_BINDING' module provides the following named constants of type default integer, which can be used as KIND type parameters. In addition to the integer named constants required by the Fortran ! 2003 standard and `C_PTRDIFF_T' of TS 29113, GNU Fortran provides as an extension named constants for the 128-bit integer types supported by the ! C compiler: `C_INT128_T, C_INT_LEAST128_T, C_INT_FAST128_T'. ! Furthermore, if `__float128' is supported in C, the named constants ! `C_FLOAT128, C_FLOAT128_COMPLEX' are defined. Fortran Named constant C type Extension ! Type ! `INTEGER' `C_INT' `int' ! `INTEGER' `C_SHORT' `short int' ! `INTEGER' `C_LONG' `long int' ! `INTEGER' `C_LONG_LONG' `long long int' ! `INTEGER' `C_SIGNED_CHAR' `signed char'/`unsigned ! char' ! `INTEGER' `C_SIZE_T' `size_t' ! `INTEGER' `C_INT8_T' `int8_t' ! `INTEGER' `C_INT16_T' `int16_t' ! `INTEGER' `C_INT32_T' `int32_t' ! `INTEGER' `C_INT64_T' `int64_t' ! `INTEGER' `C_INT128_T' `int128_t' Ext. ! `INTEGER' `C_INT_LEAST8_T' `int_least8_t' ! `INTEGER' `C_INT_LEAST16_T' `int_least16_t' ! `INTEGER' `C_INT_LEAST32_T' `int_least32_t' ! `INTEGER' `C_INT_LEAST64_T' `int_least64_t' ! `INTEGER' `C_INT_LEAST128_T' `int_least128_t' Ext. ! `INTEGER' `C_INT_FAST8_T' `int_fast8_t' ! `INTEGER' `C_INT_FAST16_T' `int_fast16_t' ! `INTEGER' `C_INT_FAST32_T' `int_fast32_t' ! `INTEGER' `C_INT_FAST64_T' `int_fast64_t' ! `INTEGER' `C_INT_FAST128_T' `int_fast128_t' Ext. ! `INTEGER' `C_INTMAX_T' `intmax_t' ! `INTEGER' `C_INTPTR_T' `intptr_t' ! `INTEGER' `C_PTRDIFF_T' `intptr_t' TS 29113 ! `REAL' `C_FLOAT' `float' ! `REAL' `C_DOUBLE' `double' ! `REAL' `C_LONG_DOUBLE' `long double' ! `REAL' `C_FLOAT128' `__float128' Ext. ! `COMPLEX' `C_FLOAT_COMPLEX' `float _Complex' ! `COMPLEX' `C_DOUBLE_COMPLEX' `double _Complex' ! `COMPLEX' `C_LONG_DOUBLE_COMPLEX' `long double _Complex' ! `REAL' `C_FLOAT128_COMPLEX' `__float128 _Complex' Ext. ! `LOGICAL' `C_BOOL' `_Bool' ! `CHARACTER' `C_CHAR' `char' Additionally, the following parameters of type ! `CHARACTER(KIND=C_CHAR)' are defined. Name C definition Value ! `C_NULL_CHAR' null character `'\0'' ! `C_ALERT' alert `'\a'' ! `C_BACKSPACE' backspace `'\b'' ! `C_FORM_FEED' form feed `'\f'' ! `C_NEW_LINE' new line `'\n'' ! `C_CARRIAGE_RETURN'carriage return `'\r'' ! `C_HORIZONTAL_TAB'horizontal tab `'\t'' ! `C_VERTICAL_TAB'vertical tab `'\v'' Moreover, the following two named constants are defined: Name Type ! `C_NULL_PTR' `C_PTR' ! `C_NULL_FUNPTR'`C_FUNPTR' ! Both are equivalent to the value `NULL' in C.  File: gfortran.info, Node: IEEE modules, Next: OpenMP Modules OMP_LIB and OMP_LIB_KINDS, Prev: ISO_C_BINDING, Up: Intrinsic Modules ! 10.3 IEEE modules: `IEEE_EXCEPTIONS', `IEEE_ARITHMETIC', and `IEEE_FEATURES' ============================================================================ _Standard_: Fortran 2003 and later ! The `IEEE_EXCEPTIONS', `IEEE_ARITHMETIC', and `IEEE_FEATURES' intrinsic modules provide support for exceptions and IEEE arithmetic, as defined in Fortran 2003 and later standards, and the IEC 60559:1989 standard (_Binary floating-point arithmetic for microprocessor ! systems_). These modules are only provided on the following supported platforms: * i386 and x86_64 processors + * platforms which use the GNU C Library (glibc) + * platforms with support for SysV/386 routines for floating point interface (including Solaris and BSDs) + * platforms with the AIX OS For full compliance with the Fortran standards, code using the ! `IEEE_EXCEPTIONS' or `IEEE_ARITHMETIC' modules should be compiled with ! the following options: `-fno-unsafe-math-optimizations -frounding-math -fsignaling-nans'.  File: gfortran.info, Node: OpenMP Modules OMP_LIB and OMP_LIB_KINDS, Next: OpenACC Module OPENACC, Prev: IEEE modules, Up: Intrinsic Modules ! 10.4 OpenMP Modules `OMP_LIB' and `OMP_LIB_KINDS' ================================================= _Standard_: OpenMP Application Program Interface v4.0 The OpenMP Fortran runtime library routines are provided both in a ! form of two Fortran 90 modules, named `OMP_LIB' and `OMP_LIB_KINDS', ! and in a form of a Fortran `include' file named `omp_lib.h'. The ! procedures provided by `OMP_LIB' can be found in the *note ! Introduction: (libgomp)Top. manual, the named constants defined in the ! modules are listed below. For details refer to the actual OpenMP Application Program Interface v4.0 (http://www.openmp.org/mp-documents/OpenMP4.0.0.pdf). ! `OMP_LIB_KINDS' provides the following scalar default-integer named constants: ! `omp_lock_kind' ! `omp_nest_lock_kind' ! ! `omp_proc_bind_kind' ! ! `omp_sched_kind' ! ! `OMP_LIB' provides the scalar default-integer named constant ! `openmp_version' with a value of the form YYYYMM, where `yyyy' is the year and MM the month of the OpenMP version; for OpenMP v4.0 the value ! is `201307'. The following scalar integer named constants of the kind ! `omp_sched_kind': ! `omp_sched_static' ! ! `omp_sched_dynamic' ! ! `omp_sched_guided' ! ! `omp_sched_auto' And the following scalar integer named constants of the kind ! `omp_proc_bind_kind': ! `omp_proc_bind_false' ! ! `omp_proc_bind_true' ! ! `omp_proc_bind_master' ! ! `omp_proc_bind_close' ! ! `omp_proc_bind_spread'  File: gfortran.info, Node: OpenACC Module OPENACC, Prev: OpenMP Modules OMP_LIB and OMP_LIB_KINDS, Up: Intrinsic Modules ! 10.5 OpenACC Module `OPENACC' ============================= _Standard_: OpenACC Application Programming Interface v2.0 The OpenACC Fortran runtime library routines are provided both in a ! form of a Fortran 90 module, named `OPENACC', and in form of a Fortran ! `include' file named `openacc_lib.h'. The procedures provided by ! `OPENACC' can be found in the *note Introduction: (libgomp)Top. manual, the named constants defined in the modules are listed below. For details refer to the actual OpenACC Application Programming Interface v2.0 (http://www.openacc.org/). ! `OPENACC' provides the scalar default-integer named constant ! `openacc_version' with a value of the form YYYYMM, where `yyyy' is the ! year and MM the month of the OpenACC version; for OpenACC v2.0 the ! value is `201306'.  File: gfortran.info, Node: Contributing, Next: Copying, Prev: Intrinsic Modules, Up: Top *************** File: gfortran.info, Node: Contributing *** 17590,17598 **** Contributing ************ ! Free software is only possible if people contribute to efforts to create ! it. We're always in need of more people helping out with ideas and ! comments, writing documentation and contributing code. If you want to contribute to GNU Fortran, have a look at the long lists of projects you can take on. Some of these projects are small, --- 17790,17798 ---- Contributing ************ ! Free software is only possible if people contribute to efforts to ! create it. We're always in need of more people helping out with ideas ! and comments, writing documentation and contributing code. If you want to contribute to GNU Fortran, have a look at the long lists of projects you can take on. Some of these projects are small, *************** with GCC was written by _Paul Brook_. *** 17622,17658 **** --- 17822,17890 ---- significant help to the GNU Fortran project (in alphabetical order): - Janne Blomqvist + - Steven Bosscher + - Paul Brook + - Tobias Burnus + - Franc,ois-Xavier Coudert + - Bud Davis + - Jerry DeLisle + - Erik Edelmann + - Bernhard Fischer + - Daniel Franke + - Richard Guenther + - Richard Henderson + - Katherine Holcomb + - Jakub Jelinek + - Niels Kristian Bech Jensen + - Steven Johnson + - Steven G. Kargl + - Thomas Koenig + - Asher Langton + - H. J. Lu + - Toon Moene + - Brooks Moses + - Andrew Pinski + - Tim Prince + - Christopher D. Rickett + - Richard Sandiford + - Tobias Schlu"ter + - Roger Sayle + - Paul Thomas + - Andy Vaught + - Feng Wang + - Janus Weil + - Daniel Kraft The following people have contributed bug reports, smaller or larger *************** patches, and much needed feedback and en *** 17660,17668 **** --- 17892,17904 ---- project: - Bill Clodius + - Dominique d'Humie`res + - Kate Hedstrom + - Erik Schnetter + - Joost VandeVondele Many other individuals have helped debug, test and improve the GNU *************** Projects *** 17678,17705 **** _Help build the test suite_ Solicit more code for donation to the test suite: the more ! extensive the testsuite, the smaller the risk of breaking things in ! the future! We can keep code private on request. _Bug hunting/squishing_ ! Find bugs and write more test cases! Test cases are especially ! very welcome, because it allows us to concentrate on fixing bugs instead of isolating them. Going through the bugzilla database at ! to reduce testcases posted there and add more information (for example, for which version does the ! testcase work, for which versions does it fail?) is also very helpful.  File: gfortran.info, Node: Proposed Extensions, Prev: Projects, Up: Contributing Proposed Extensions =================== ! Here's a list of proposed extensions for the GNU Fortran compiler, in no ! particular order. Most of these are necessary to be fully compatible ! with existing Fortran compilers, but they are not part of the official ! J3 Fortran 95 standard. Compiler extensions: -------------------- --- 17914,17942 ---- _Help build the test suite_ Solicit more code for donation to the test suite: the more ! extensive the testsuite, the smaller the risk of breaking things ! in the future! We can keep code private on request. _Bug hunting/squishing_ ! Find bugs and write more test cases! Test cases are especially very ! welcome, because it allows us to concentrate on fixing bugs instead of isolating them. Going through the bugzilla database at ! `https://gcc.gnu.org/bugzilla/' to reduce testcases posted there and add more information (for example, for which version does the ! testcase work, for which versions does it fail?) is also very helpful. +  File: gfortran.info, Node: Proposed Extensions, Prev: Projects, Up: Contributing Proposed Extensions =================== ! Here's a list of proposed extensions for the GNU Fortran compiler, in ! no particular order. Most of these are necessary to be fully ! compatible with existing Fortran compilers, but they are not part of ! the official J3 Fortran 95 standard. Compiler extensions: -------------------- *************** Compiler extensions: *** 17708,17715 **** * Automatically extend single precision constants to double. ! * Compile code that conserves memory by dynamically allocating common ! and module storage either on stack or heap. * Compile flag to generate code for array conformance checking (suggest -CC). --- 17945,17952 ---- * Automatically extend single precision constants to double. ! * Compile code that conserves memory by dynamically allocating ! common and module storage either on stack or heap. * Compile flag to generate code for array conformance checking (suggest -CC). *************** Environment Options *** 17757,17762 **** --- 17994,18000 ---- * Environment variable forcing standard output to be line buffered (Unix). +  File: gfortran.info, Node: Copying, Next: GNU Free Documentation License, Prev: Contributing, Up: Top *************** GNU General Public License *** 17765,17771 **** Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 18003,18009 ---- Version 3, 29 June 2007 ! Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** want it, that you can change the softwar *** 17793,17801 **** free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you have ! certain responsibilities if you distribute copies of the software, or if ! you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same --- 18031,18039 ---- free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you ! these rights or asking you to surrender the rights. Therefore, you ! have certain responsibilities if you distribute copies of the software, ! or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same *************** changed, so that their problems will not *** 17814,17828 **** authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the manufacturer ! can do so. This is fundamentally incompatible with the aim of ! protecting users' freedom to change the software. The systematic ! pattern of such abuse occurs in the area of products for individuals to ! use, which is precisely where it is most unacceptable. Therefore, we ! have designed this version of the GPL to prohibit the practice for those ! products. If such problems arise substantially in other domains, we ! stand ready to extend this provision to those domains in future versions ! of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of --- 18052,18067 ---- authors of previous versions. Some devices are designed to deny users access to install or run ! modified versions of the software inside them, although the ! manufacturer can do so. This is fundamentally incompatible with the ! aim of protecting users' freedom to change the software. The ! systematic pattern of such abuse occurs in the area of products for ! individuals to use, which is precisely where it is most unacceptable. ! Therefore, we have designed this version of the GPL to prohibit the ! practice for those products. If such problems arise substantially in ! other domains, we stand ready to extend this provision to those domains ! in future versions of the GPL, as needed to protect the freedom of ! users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of *************** TERMS AND CONDITIONS *** 17859,17866 **** To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it on ! a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. --- 18098,18105 ---- To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for ! infringement under applicable copyright law, except executing it ! on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. *************** TERMS AND CONDITIONS *** 17874,17881 **** to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may convey ! the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. --- 18113,18120 ---- to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to ! the extent that warranties are provided), that licensees may ! convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. *************** TERMS AND CONDITIONS *** 17883,17890 **** 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any non-source ! form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in --- 18122,18129 ---- 1. Source Code. The "source code" for a work means the preferred form of the work ! for making modifications to it. "Object code" means any ! non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in *************** TERMS AND CONDITIONS *** 17895,17904 **** The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work with ! that Major Component, or to implement a Standard Interface for ! which an implementation is available to the public in source code ! form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code --- 18134,18143 ---- The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that ! Major Component, and (b) serves only to enable use of the work ! with that Major Component, or to implement a Standard Interface ! for which an implementation is available to the public in source ! code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code *************** TERMS AND CONDITIONS *** 17906,17920 **** The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including scripts ! to control those activities. However, it does not include the ! work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files associated ! with source files for the work, and the source code for shared ! libraries and dynamically linked subprograms that the work is ! specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. --- 18145,18159 ---- The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable ! work) run the object code and to modify the work, including ! scripts to control those activities. However, it does not include ! the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, ! Corresponding Source includes interface definition files ! associated with source files for the work, and the source code for ! shared libraries and dynamically linked subprograms that the work ! is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. *************** TERMS AND CONDITIONS *** 17931,17952 **** copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, given ! its content, constitutes a covered work. This License acknowledges ! your rights of fair use or other equivalent, as provided by ! copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for you, ! or provide you with facilities for running those works, provided ! that you comply with the terms of this License in conveying all ! material for which you do not control copyright. Those thus making ! or running the covered works for you must do so exclusively on your ! behalf, under your direction and control, on terms that prohibit ! them from making any copies of your copyrighted material outside ! their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section --- 18170,18191 ---- copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running ! a covered work is covered by this License only if the output, ! given its content, constitutes a covered work. This License ! acknowledges your rights of fair use or other equivalent, as ! provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the ! sole purpose of having them make modifications exclusively for ! you, or provide you with facilities for running those works, ! provided that you comply with the terms of this License in ! conveying all material for which you do not control copyright. ! Those thus making or running the covered works for you must do so ! exclusively on your behalf, under your direction and control, on ! terms that prohibit them from making any copies of your ! copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section *************** TERMS AND CONDITIONS *** 17963,17970 **** When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention to ! limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. --- 18202,18209 ---- When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License ! with respect to the covered work, and you disclaim any intention ! to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. *************** TERMS AND CONDITIONS *** 18034,18041 **** b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for as ! long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a --- 18273,18280 ---- b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a ! written offer, valid for at least three years and valid for ! as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a *************** TERMS AND CONDITIONS *** 18045,18075 **** to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of the ! written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access to ! the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated by ! you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to the ! object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long as ! needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. --- 18284,18315 ---- to copy the Corresponding Source from a network server at no charge. ! c. Convey individual copies of the object code with a copy of ! the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d. Convey the object code by offering access from a designated ! place (gratis or for a charge), and offer equivalent access ! to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the ! Corresponding Source may be on a different server (operated ! by you or a third party) that supports equivalent copying ! facilities, provided you maintain clear directions next to ! the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you ! remain obligated to ensure that it is available for as long ! as needed to satisfy these requirements. e. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. + A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. *************** TERMS AND CONDITIONS *** 18077,18084 **** A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product is ! a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the --- 18317,18324 ---- A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for ! incorporation into a dwelling. In determining whether a product ! is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the *************** TERMS AND CONDITIONS *** 18109,18119 **** The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or installed ! by the recipient, or for the User Product in which it has been ! modified or installed. Access to a network may be denied when the ! modification itself materially and adversely affects the operation ! of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information --- 18349,18359 ---- The requirement to provide Installation Information does not include a requirement to continue to provide support service, ! warranty, or updates for a work that has been modified or ! installed by the recipient, or for the User Product in which it ! has been modified or installed. Access to a network may be denied ! when the modification itself materially and adversely affects the ! operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information *************** TERMS AND CONDITIONS *** 18143,18150 **** Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License with ! terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or --- 18383,18390 ---- Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright ! holders of that material) supplement the terms of this License ! with terms: a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or *************** TERMS AND CONDITIONS *** 18154,18161 **** Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be marked ! in reasonable ways as different from the original version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or --- 18394,18402 ---- Legal Notices displayed by works containing it; or c. Prohibiting misrepresentation of the origin of that material, ! or requiring that modified versions of such material be ! marked in reasonable ways as different from the original ! version; or d. Limiting the use for publicity purposes of names of licensors or authors of the material; or *************** TERMS AND CONDITIONS *** 18174,18183 **** you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or conveying ! under this License, you may add to a covered work material governed ! by the terms of that license document, provided that the further ! restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the --- 18415,18425 ---- you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document ! contains a further restriction but permits relicensing or ! conveying under this License, you may add to a covered work ! material governed by the terms of that license document, provided ! that the further restriction does not survive such relicensing or ! conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the *************** TERMS AND CONDITIONS *** 18193,18205 **** You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under the ! third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 18435,18447 ---- You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights ! under this License (including any patent licenses granted under ! the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** TERMS AND CONDITIONS *** 18211,18220 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, you do not qualify to receive new licenses ! for the same material under section 10. 9. Acceptance Not Required for Having Copies. --- 18453,18462 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, you do not qualify to receive new ! licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. *************** TERMS AND CONDITIONS *** 18228,18234 **** by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and --- 18470,18476 ---- by modifying or propagating a covered work, you indicate your acceptance of this License to do so. ! 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and *************** TERMS AND CONDITIONS *** 18242,18262 **** covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to possession ! of the Corresponding Source of the work from the predecessor in ! interest, if the predecessor has it or can get it with reasonable ! efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for exercise ! of rights granted under this License, and you may not initiate ! litigation (including a cross-claim or counterclaim in a lawsuit) ! alleging that any patent claim is infringed by making, using, ! selling, offering for sale, or importing the Program or any portion ! of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. --- 18484,18504 ---- covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or ! could give under the previous paragraph, plus a right to ! possession of the Corresponding Source of the work from the ! predecessor in interest, if the predecessor has it or can get it ! with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you ! may not impose a license fee, royalty, or other charge for ! exercise of rights granted under this License, and you may not ! initiate litigation (including a cross-claim or counterclaim in a ! lawsuit) alleging that any patent claim is infringed by making, ! using, selling, offering for sale, or importing the Program or any ! portion of it. ! 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. *************** TERMS AND CONDITIONS *** 18276,18290 **** Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its contributor ! version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To "grant" ! such a patent license to a party means to make such an agreement or ! commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available --- 18518,18532 ---- Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and ! otherwise run, modify and propagate the contents of its ! contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a ! patent or covenant not to sue for patent infringement). To ! "grant" such a patent license to a party means to make such an ! agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available *************** TERMS AND CONDITIONS *** 18314,18348 **** conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under which ! you make payment to the third party based on the extent of your ! activity of conveying the work, and under which the third party ! grants, to any of the parties who would receive the covered work ! from you, a discriminatory patent license (a) in connection with ! copies of the covered work conveyed by you (or copies made from ! those copies), or (b) primarily for and in connection with specific ! products or compilations that contain the covered work, unless you ! entered into that arrangement, or that patent license was granted, ! prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, agreement ! or otherwise) that contradict the conditions of this License, they ! do not excuse you from the conditions of this License. If you ! cannot convey a covered work so as to satisfy simultaneously your ! obligations under this License and any other pertinent obligations, ! then as a consequence you may not convey it at all. For example, ! if you agree to terms that obligate you to collect a royalty for ! further conveying from those to whom you convey the Program, the ! only way you could satisfy both those terms and this License would ! be to refrain entirely from conveying the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed --- 18556,18591 ---- conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third ! party that is in the business of distributing software, under ! which you make payment to the third party based on the extent of ! your activity of conveying the work, and under which the third ! party grants, to any of the parties who would receive the covered ! work from you, a discriminatory patent license (a) in connection ! with copies of the covered work conveyed by you (or copies made ! from those copies), or (b) primarily for and in connection with ! specific products or compilations that contain the covered work, ! unless you entered into that arrangement, or that patent license ! was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. ! 12. No Surrender of Others' Freedom. ! If conditions are imposed on you (whether by court order, ! agreement or otherwise) that contradict the conditions of this ! License, they do not excuse you from the conditions of this ! License. If you cannot convey a covered work so as to satisfy ! simultaneously your obligations under this License and any other ! pertinent obligations, then as a consequence you may not convey it ! at all. For example, if you agree to terms that obligate you to ! collect a royalty for further conveying from those to whom you ! convey the Program, the only way you could satisfy both those ! terms and this License would be to refrain entirely from conveying ! the Program. ! 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed *************** TERMS AND CONDITIONS *** 18353,18373 **** General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. Such ! new versions will be similar in spirit to the present version, but ! may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the Free ! Software Foundation. If the Program does not specify a version ! number of the GNU General Public License, you may choose any ! version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that --- 18596,18617 ---- General Public License, section 13, concerning interaction through a network will apply to the combination as such. ! 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new ! versions of the GNU General Public License from time to time. ! Such new versions will be similar in spirit to the present ! version, but may differ in detail to address new problems or ! concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of ! that numbered version or of any later version published by the ! Free Software Foundation. If the Program does not specify a ! version number of the GNU General Public License, you may choose ! any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that *************** TERMS AND CONDITIONS *** 18379,18402 **** author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR ! DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD --- 18623,18646 ---- author or copyright holder as a result of your choosing to follow a later version. ! 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY ! APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF ! MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. ! 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES ! AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU ! FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD *************** TERMS AND CONDITIONS *** 18404,18410 **** PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, --- 18648,18654 ---- PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ! 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, *************** TERMS AND CONDITIONS *** 18413,18418 **** --- 18657,18663 ---- connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. + END OF TERMS AND CONDITIONS =========================== *************** state the exclusion of warranty; and eac *** 18443,18449 **** General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. --- 18688,18694 ---- General Public License for more details. You should have received a copy of the GNU General Public License ! along with this program. If not, see `http://www.gnu.org/licenses/'. Also add information on how to contact you by electronic and paper mail. *************** mail. *** 18452,18462 **** notice like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type 'show c' for details. ! The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". --- 18697,18707 ---- notice like this when it starts in an interactive mode: PROGRAM Copyright (C) YEAR NAME OF AUTHOR ! This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it ! under certain conditions; type `show c' for details. ! The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". *************** use an "about box". *** 18464,18477 **** You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read .  File: gfortran.info, Node: GNU Free Documentation License, Next: Funding, Prev: Copying, Up: Top --- 18709,18722 ---- You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow ! the GNU GPL, see `http://www.gnu.org/licenses/'. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, ! please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.  File: gfortran.info, Node: GNU Free Documentation License, Next: Funding, Prev: Copying, Up: Top *************** GNU Free Documentation License *** 18482,18488 **** Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. --- 18727,18733 ---- Version 1.3, 3 November 2008 Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. ! `http://fsf.org/' Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. *************** GNU Free Documentation License *** 18507,18527 **** free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. We ! recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it can ! be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You accept ! the license if you copy, modify or distribute the work in a way ! requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with --- 18752,18772 ---- free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless ! of subject matter or whether it is published as a printed book. ! We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, ! that contains a notice placed by the copyright holder saying it ! can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member ! of the public is a licensee, and is addressed as "you". You ! accept the license if you copy, modify or distribute the work in a ! way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with *************** GNU Free Documentation License *** 18539,18550 **** regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in the ! notice that says that the Document is released under this License. ! If a section does not fit the above definition of Secondary then it ! is not allowed to be designated as Invariant. The Document may ! contain zero Invariant Sections. If the Document does not identify ! any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice --- 18784,18795 ---- regarding them. The "Invariant Sections" are certain Secondary Sections whose ! titles are designated, as being those of Invariant Sections, in ! the notice that says that the Document is released under this ! License. If a section does not fit the above definition of ! Secondary then it is not allowed to be designated as Invariant. ! The Document may contain zero Invariant Sections. If the Document ! does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice *************** GNU Free Documentation License *** 18555,18581 **** A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images composed ! of pixels) generic paint programs or (for drawings) some widely ! available drawing editor, and that is suitable for input to text ! formatters or for automatic translation to a variety of formats ! suitable for input to text formatters. A copy made in an otherwise ! Transparent file format whose markup, or absence of markup, has ! been arranged to thwart or discourage subsequent modification by ! readers is not Transparent. An image format is not Transparent if ! used for any substantial amount of text. A copy that is not ! "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and standard-conforming ! simple HTML, PostScript or PDF designed for human modification. ! Examples of transparent image formats include PNG, XCF and JPG. ! Opaque formats include proprietary formats that can be read and ! edited only by proprietary word processors, SGML or XML for which ! the DTD and/or processing tools are not generally available, and ! the machine-generated HTML, PostScript or PDF produced by some word ! processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the --- 18800,18826 ---- A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document ! straightforwardly with generic text editors or (for images ! composed of pixels) generic paint programs or (for drawings) some ! widely available drawing editor, and that is suitable for input to ! text formatters or for automatic translation to a variety of ! formats suitable for input to text formatters. A copy made in an ! otherwise Transparent file format whose markup, or absence of ! markup, has been arranged to thwart or discourage subsequent ! modification by readers is not Transparent. An image format is ! not Transparent if used for any substantial amount of text. A ! copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, ! SGML or XML using a publicly available DTD, and ! standard-conforming simple HTML, PostScript or PDF designed for ! human modification. Examples of transparent image formats include ! PNG, XCF and JPG. Opaque formats include proprietary formats that ! can be read and edited only by proprietary word processors, SGML or ! XML for which the DTD and/or processing tools are not generally ! available, and the machine-generated HTML, PostScript or PDF ! produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the *************** GNU Free Documentation License *** 18613,18620 **** may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow the ! conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. --- 18858,18865 ---- may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you ! distribute a large enough number of copies you must also follow ! the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. *************** GNU Free Documentation License *** 18628,18638 **** these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the title ! equally prominent and visible. You may add other material on the ! covers in addition. Copying with changes limited to the covers, as ! long as they preserve the title of the Document and satisfy these ! conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit --- 18873,18884 ---- these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The ! front cover must present the full title with all words of the ! title equally prominent and visible. You may add other material ! on the covers in addition. Copying with changes limited to the ! covers, as long as they preserve the title of the Document and ! satisfy these conditions, can be treated as verbatim copying in ! other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit *************** GNU Free Documentation License *** 18640,18678 **** adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a machine-readable ! Transparent copy along with each Opaque copy, or state in or with ! each Opaque copy a computer-network location from which the general ! network-using public has access to download using public-standard ! network protocols a complete Transparent copy of the Document, free ! of added material. If you use the latter option, you must take ! reasonably prudent steps, when you begin distribution of Opaque ! copies in quantity, to ensure that this Transparent copy will ! remain thus accessible at the stated location until at least one ! year after the last time you distribute an Opaque copy (directly or ! through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of copies, ! to give them a chance to provide you with an updated version of the ! Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with the ! Modified Version filling the role of the Document, thus licensing ! distribution and modification of the Modified Version to whoever ! possesses a copy of it. In addition, you must do these things in ! the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of previous ! versions (which should, if there were any, be listed in the ! History section of the Document). You may use the same title ! as a previous version if the original publisher of that ! version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in --- 18886,18925 ---- adjacent pages. If you publish or distribute Opaque copies of the Document ! numbering more than 100, you must either include a ! machine-readable Transparent copy along with each Opaque copy, or ! state in or with each Opaque copy a computer-network location from ! which the general network-using public has access to download ! using public-standard network protocols a complete Transparent ! copy of the Document, free of added material. If you use the ! latter option, you must take reasonably prudent steps, when you ! begin distribution of Opaque copies in quantity, to ensure that ! this Transparent copy will remain thus accessible at the stated ! location until at least one year after the last time you ! distribute an Opaque copy (directly or through your agents or ! retailers) of that edition to the public. It is requested, but not required, that you contact the authors of ! the Document well before redistributing any large number of ! copies, to give them a chance to provide you with an updated ! version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you ! release the Modified Version under precisely this License, with ! the Modified Version filling the role of the Document, thus ! licensing distribution and modification of the Modified Version to ! whoever possesses a copy of it. In addition, you must do these ! things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title ! distinct from that of the Document, and from those of ! previous versions (which should, if there were any, be listed ! in the History section of the Document). You may use the ! same title as a previous version if the original publisher of ! that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in *************** GNU Free Documentation License *** 18702,18731 **** I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on the ! Title Page. If there is no section Entitled "History" in the ! Document, create one stating the title, year, authors, and ! publisher of the Document as given on its Title Page, then add ! an item describing the Modified Version as stated in the ! previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in the ! "History" section. You may omit a network location for a work ! that was published at least four years before the Document ! itself, or if the original publisher of the version it refers ! to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the section ! all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, unaltered ! in their text and in their titles. Section numbers or the ! equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. --- 18949,18979 ---- I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new ! authors, and publisher of the Modified Version as given on ! the Title Page. If there is no section Entitled "History" in ! the Document, create one stating the title, year, authors, ! and publisher of the Document as given on its Title Page, ! then add an item describing the Modified Version as stated in ! the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for ! previous versions it was based on. These may be placed in ! the "History" section. You may omit a network location for a ! work that was published at least four years before the ! Document itself, or if the original publisher of the version ! it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", ! Preserve the Title of the section, and preserve in the ! section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. ! L. Preserve all the Invariant Sections of the Document, ! unaltered in their text and in their titles. Section numbers ! or the equivalent are not considered part of the section ! titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. *************** GNU Free Documentation License *** 18738,18748 **** If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option designate ! some or all of these sections as invariant. To do this, add their ! titles to the list of Invariant Sections in the Modified Version's ! license notice. These titles must be distinct from any other ! section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various --- 18986,18996 ---- If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no ! material copied from the Document, you may at your option ! designate some or all of these sections as invariant. To do this, ! add their titles to the list of Invariant Sections in the Modified ! Version's license notice. These titles must be distinct from any ! other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various *************** GNU Free Documentation License *** 18751,18765 **** definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end of ! the list of Cover Texts in the Modified Version. Only one passage ! of Front-Cover Text and one of Back-Cover Text may be added by (or ! through arrangements made by) any one entity. If the Document ! already includes a cover text for the same cover, previously added ! by you or by arrangement made by the same entity you are acting on ! behalf of, you may not add another; but you may replace the old ! one, on explicit permission from the previous publisher that added ! the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to --- 18999,19013 ---- definition of a standard. You may add a passage of up to five words as a Front-Cover Text, ! and a passage of up to 25 words as a Back-Cover Text, to the end ! of the list of Cover Texts in the Modified Version. Only one ! passage of Front-Cover Text and one of Back-Cover Text may be ! added by (or through arrangements made by) any one entity. If the ! Document already includes a cover text for the same cover, ! previously added by you or by arrangement made by the same entity ! you are acting on behalf of, you may not add another; but you may ! replace the old one, on explicit permission from the previous ! publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to *************** GNU Free Documentation License *** 18769,18776 **** You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination all ! of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. --- 19017,19024 ---- You may combine the Document with other documents released under this License, under the terms defined in section 4 above for ! modified versions, provided that you include in the combination ! all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. *************** GNU Free Documentation License *** 18797,18816 **** documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the documents ! in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow this ! License in all other respects regarding verbatim copying of that ! document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of a ! storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this --- 19045,19064 ---- documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the ! rules of this License for verbatim copying of each of the ! documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert ! a copy of this License into the extracted document, and follow ! this License in all other respects regarding verbatim copying of ! that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other ! separate and independent documents or works, in or on a volume of ! a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this *************** GNU Free Documentation License *** 18855,18862 **** However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly and ! finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. --- 19103,19110 ---- However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) ! provisionally, unless and until the copyright holder explicitly ! and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. *************** GNU Free Documentation License *** 18868,18900 **** after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from you ! under this License. If your rights have been terminated and not ! permanently reinstated, receipt of a copy of some or all of the ! same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! . Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If the ! Document does not specify a version number of this License, you may ! choose any version ever published (not as a draft) by the Free ! Software Foundation. If the Document specifies that a proxy can ! decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also --- 19116,19148 ---- after your receipt of the notice. Termination of your rights under this section does not terminate ! the licenses of parties who have received copies or rights from ! you under this License. If your rights have been terminated and ! not permanently reinstated, receipt of a copy of some or all of ! the same material does not give you any rights to use it. ! 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See ! `http://www.gnu.org/copyleft/'. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been ! published (not as a draft) by the Free Software Foundation. If ! the Document does not specify a version number of this License, ! you may choose any version ever published (not as a draft) by the ! Free Software Foundation. If the Document specifies that a proxy ! can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document. ! 11. RELICENSING "Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also *************** GNU Free Documentation License *** 18924,18929 **** --- 19172,19178 ---- site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. + ADDENDUM: How to use this License for your documents ==================================================== *************** notices just after the title page: *** 18940,18946 **** Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts --- 19189,19195 ---- Free Documentation License''. If you have Invariant Sections, Front-Cover Texts and Back-Cover ! Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts *************** combination of the three, merge those tw *** 18951,18959 **** situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of free ! software license, such as the GNU General Public License, to permit ! their use in free software.  File: gfortran.info, Node: Funding, Next: Option Index, Prev: GNU Free Documentation License, Up: Top --- 19200,19208 ---- situation. If your document contains nontrivial examples of program code, we ! recommend releasing these examples in parallel under your choice of ! free software license, such as the GNU General Public License, to ! permit their use in free software.  File: gfortran.info, Node: Funding, Next: Option Index, Prev: GNU Free Documentation License, Up: Top *************** for comparison. *** 18983,18990 **** Even a precise fraction "of the profits from this disk" is not very meaningful, since creative accounting and unrelated business decisions ! can greatly alter what fraction of the sales price counts as profit. If ! the price you pay is $50, ten percent of the profit is probably less than a dollar; it might be a few cents, or nothing at all. Some redistributors do development work themselves. This is useful --- 19232,19239 ---- Even a precise fraction "of the profits from this disk" is not very meaningful, since creative accounting and unrelated business decisions ! can greatly alter what fraction of the sales price counts as profit. ! If the price you pay is $50, ten percent of the profit is probably less than a dollar; it might be a few cents, or nothing at all. Some redistributors do development work themselves. This is useful *************** difference than others. For example, ma *** 18994,19001 **** a program contributes very little; maintaining the standard version of a program for the whole community contributes much. Easy new ports contribute little, since someone else would surely do them; difficult ! ports such as adding a new CPU to the GNU Compiler Collection contribute ! more; major new features or packages contribute the most. By establishing the idea that supporting further development is "the proper thing to do" when distributing free software for a fee, we can --- 19243,19250 ---- a program contributes very little; maintaining the standard version of a program for the whole community contributes much. Easy new ports contribute little, since someone else would surely do them; difficult ! ports such as adding a new CPU to the GNU Compiler Collection ! contribute more; major new features or packages contribute the most. By establishing the idea that supporting further development is "the proper thing to do" when distributing free software for a fee, we can *************** File: gfortran.info, Node: Option Index *** 19011,19035 **** Option Index ************ ! 'gfortran''s command line options are indexed here without any initial ! '-' or '--'. Where an option has both positive and negative forms (such ! as -foption and -fno-option), relevant entries in the manual are indexed ! under the most appropriate form; it may sometimes be useful to look up ! both forms. [index] * Menu: * A-PREDICATE=ANSWER: Preprocessing Options. ! (line 119) * APREDICATE=ANSWER: Preprocessing Options. ! (line 113) * backslash: Fortran Dialect Options. (line 56) * C: Preprocessing Options. ! (line 122) * CC: Preprocessing Options. ! (line 137) * cpp: Preprocessing Options. (line 12) * dD: Preprocessing Options. --- 19260,19284 ---- Option Index ************ ! `gfortran''s command line options are indexed here without any initial ! `-' or `--'. Where an option has both positive and negative forms ! (such as -foption and -fno-option), relevant entries in the manual are ! indexed under the most appropriate form; it may sometimes be useful to ! look up both forms. [index] * Menu: * A-PREDICATE=ANSWER: Preprocessing Options. ! (line 120) * APREDICATE=ANSWER: Preprocessing Options. ! (line 114) * backslash: Fortran Dialect Options. (line 56) * C: Preprocessing Options. ! (line 123) * CC: Preprocessing Options. ! (line 138) * cpp: Preprocessing Options. (line 12) * dD: Preprocessing Options. *************** both forms. *** 19041,19060 **** * dN: Preprocessing Options. (line 41) * DNAME: Preprocessing Options. ! (line 151) * DNAME=DEFINITION: Preprocessing Options. ! (line 154) * dU: Preprocessing Options. (line 44) ! * faggressive-function-elimination: Code Gen Options. (line 361) ! * falign-commons: Code Gen Options. (line 334) * fall-intrinsics: Fortran Dialect Options. (line 17) ! * fblas-matmul-limit: Code Gen Options. (line 274) ! * fbounds-check: Code Gen Options. (line 198) ! * fcheck: Code Gen Options. (line 141) ! * fcheck-array-temporaries: Code Gen Options. (line 201) ! * fcoarray: Code Gen Options. (line 127) * fconvert=CONVERSION: Runtime Options. (line 10) * fcray-pointer: Fortran Dialect Options. (line 102) --- 19290,19309 ---- * dN: Preprocessing Options. (line 41) * DNAME: Preprocessing Options. ! (line 153) * DNAME=DEFINITION: Preprocessing Options. ! (line 156) * dU: Preprocessing Options. (line 44) ! * faggressive-function-elimination: Code Gen Options. (line 365) ! * falign-commons: Code Gen Options. (line 338) * fall-intrinsics: Fortran Dialect Options. (line 17) ! * fblas-matmul-limit: Code Gen Options. (line 275) ! * fbounds-check: Code Gen Options. (line 199) ! * fcheck: Code Gen Options. (line 143) ! * fcheck-array-temporaries: Code Gen Options. (line 202) ! * fcoarray: Code Gen Options. (line 129) * fconvert=CONVERSION: Runtime Options. (line 10) * fcray-pointer: Fortran Dialect Options. (line 102) *************** both forms. *** 19067,19089 **** * fdec-structure: Fortran Dialect Options. (line 44) * fdefault-double-8: Fortran Dialect Options. ! (line 151) * fdefault-integer-8: Fortran Dialect Options. ! (line 137) * fdefault-real-8: Fortran Dialect Options. ! (line 143) * fdollar-ok: Fortran Dialect Options. (line 50) * fdump-fortran-optimized: Debugging Options. (line 15) * fdump-fortran-original: Debugging Options. (line 10) * fdump-parse-tree: Debugging Options. (line 19) ! * fexternal-blas: Code Gen Options. (line 266) * ff2c: Code Gen Options. (line 25) * ffixed-form: Fortran Dialect Options. (line 11) * ffixed-line-length-N: Fortran Dialect Options. (line 73) ! * ffpe-summary=LIST: Debugging Options. (line 51) * ffpe-trap=LIST: Debugging Options. (line 25) * ffree-form: Fortran Dialect Options. (line 11) --- 19316,19338 ---- * fdec-structure: Fortran Dialect Options. (line 44) * fdefault-double-8: Fortran Dialect Options. ! (line 152) * fdefault-integer-8: Fortran Dialect Options. ! (line 138) * fdefault-real-8: Fortran Dialect Options. ! (line 144) * fdollar-ok: Fortran Dialect Options. (line 50) * fdump-fortran-optimized: Debugging Options. (line 15) * fdump-fortran-original: Debugging Options. (line 10) * fdump-parse-tree: Debugging Options. (line 19) ! * fexternal-blas: Code Gen Options. (line 267) * ff2c: Code Gen Options. (line 25) * ffixed-form: Fortran Dialect Options. (line 11) * ffixed-line-length-N: Fortran Dialect Options. (line 73) ! * ffpe-summary=LIST: Debugging Options. (line 52) * ffpe-trap=LIST: Debugging Options. (line 25) * ffree-form: Fortran Dialect Options. (line 11) *************** both forms. *** 19091,19185 **** (line 86) * fimplicit-none: Fortran Dialect Options. (line 97) ! * finit-character: Code Gen Options. (line 309) ! * finit-integer: Code Gen Options. (line 309) ! * finit-local-zero: Code Gen Options. (line 309) ! * finit-logical: Code Gen Options. (line 309) ! * finit-real: Code Gen Options. (line 309) ! * finline-matmul-limit: Code Gen Options. (line 285) * finteger-4-integer-8: Fortran Dialect Options. ! (line 160) * fintrinsic-modules-path DIR: Directory Options. (line 36) ! * fmax-array-constructor: Code Gen Options. (line 204) * fmax-errors=N: Error and Warning Options. (line 27) * fmax-identifier-length=N: Fortran Dialect Options. (line 93) ! * fmax-stack-var-size: Code Gen Options. (line 222) * fmax-subrecord-length=LENGTH: Runtime Options. (line 29) * fmodule-private: Fortran Dialect Options. (line 68) * fno-automatic: Code Gen Options. (line 15) ! * fno-backtrace: Debugging Options. (line 61) ! * fno-protect-parens: Code Gen Options. (line 346) * fno-underscoring: Code Gen Options. (line 54) * fopenacc: Fortran Dialect Options. (line 106) * fopenmp: Fortran Dialect Options. ! (line 117) ! * fpack-derived: Code Gen Options. (line 244) * fpp: Preprocessing Options. (line 12) * frange-check: Fortran Dialect Options. ! (line 125) * freal-4-real-10: Fortran Dialect Options. ! (line 175) * freal-4-real-16: Fortran Dialect Options. ! (line 175) * freal-4-real-8: Fortran Dialect Options. ! (line 175) * freal-8-real-10: Fortran Dialect Options. ! (line 175) * freal-8-real-16: Fortran Dialect Options. ! (line 175) * freal-8-real-4: Fortran Dialect Options. ! (line 175) ! * frealloc-lhs: Code Gen Options. (line 355) * frecord-marker=LENGTH: Runtime Options. (line 21) ! * frecursive: Code Gen Options. (line 300) ! * frepack-arrays: Code Gen Options. (line 250) ! * frontend-optimize: Code Gen Options. (line 369) ! * fsecond-underscore: Code Gen Options. (line 110) ! * fshort-enums: Code Gen Options. (line 260) * fshort-enums <1>: Fortran 2003 status. (line 93) * fsign-zero: Runtime Options. (line 34) ! * fstack-arrays: Code Gen Options. (line 236) * fsyntax-only: Error and Warning Options. (line 33) * fworking-directory: Preprocessing Options. (line 55) * H: Preprocessing Options. ! (line 174) * IDIR: Directory Options. (line 14) * idirafter DIR: Preprocessing Options. ! (line 69) * imultilib DIR: Preprocessing Options. ! (line 76) * iprefix PREFIX: Preprocessing Options. ! (line 80) * iquote DIR: Preprocessing Options. ! (line 89) * isysroot DIR: Preprocessing Options. ! (line 85) * isystem DIR: Preprocessing Options. ! (line 96) * JDIR: Directory Options. (line 29) * MDIR: Directory Options. (line 29) * nostdinc: Preprocessing Options. ! (line 104) * P: Preprocessing Options. ! (line 179) * pedantic: Error and Warning Options. (line 38) * pedantic-errors: Error and Warning Options. (line 57) * static-libgfortran: Link Options. (line 11) * std=STD option: Fortran Dialect Options. ! (line 186) * UNAME: Preprocessing Options. ! (line 185) * undef: Preprocessing Options. ! (line 109) * Waliasing: Error and Warning Options. (line 69) * Walign-commons: Error and Warning Options. --- 19340,19434 ---- (line 86) * fimplicit-none: Fortran Dialect Options. (line 97) ! * finit-character: Code Gen Options. (line 310) ! * finit-integer: Code Gen Options. (line 310) ! * finit-local-zero: Code Gen Options. (line 310) ! * finit-logical: Code Gen Options. (line 310) ! * finit-real: Code Gen Options. (line 310) ! * finline-matmul-limit: Code Gen Options. (line 286) * finteger-4-integer-8: Fortran Dialect Options. ! (line 161) * fintrinsic-modules-path DIR: Directory Options. (line 36) ! * fmax-array-constructor: Code Gen Options. (line 205) * fmax-errors=N: Error and Warning Options. (line 27) * fmax-identifier-length=N: Fortran Dialect Options. (line 93) ! * fmax-stack-var-size: Code Gen Options. (line 223) * fmax-subrecord-length=LENGTH: Runtime Options. (line 29) * fmodule-private: Fortran Dialect Options. (line 68) * fno-automatic: Code Gen Options. (line 15) ! * fno-backtrace: Debugging Options. (line 62) ! * fno-protect-parens: Code Gen Options. (line 350) * fno-underscoring: Code Gen Options. (line 54) * fopenacc: Fortran Dialect Options. (line 106) * fopenmp: Fortran Dialect Options. ! (line 118) ! * fpack-derived: Code Gen Options. (line 245) * fpp: Preprocessing Options. (line 12) * frange-check: Fortran Dialect Options. ! (line 126) * freal-4-real-10: Fortran Dialect Options. ! (line 177) * freal-4-real-16: Fortran Dialect Options. ! (line 177) * freal-4-real-8: Fortran Dialect Options. ! (line 177) * freal-8-real-10: Fortran Dialect Options. ! (line 177) * freal-8-real-16: Fortran Dialect Options. ! (line 177) * freal-8-real-4: Fortran Dialect Options. ! (line 177) ! * frealloc-lhs: Code Gen Options. (line 359) * frecord-marker=LENGTH: Runtime Options. (line 21) ! * frecursive: Code Gen Options. (line 301) ! * frepack-arrays: Code Gen Options. (line 251) ! * frontend-optimize: Code Gen Options. (line 373) ! * fsecond-underscore: Code Gen Options. (line 112) * fshort-enums <1>: Fortran 2003 status. (line 93) + * fshort-enums: Code Gen Options. (line 261) * fsign-zero: Runtime Options. (line 34) ! * fstack-arrays: Code Gen Options. (line 237) * fsyntax-only: Error and Warning Options. (line 33) * fworking-directory: Preprocessing Options. (line 55) * H: Preprocessing Options. ! (line 176) * IDIR: Directory Options. (line 14) * idirafter DIR: Preprocessing Options. ! (line 70) * imultilib DIR: Preprocessing Options. ! (line 77) * iprefix PREFIX: Preprocessing Options. ! (line 81) * iquote DIR: Preprocessing Options. ! (line 90) * isysroot DIR: Preprocessing Options. ! (line 86) * isystem DIR: Preprocessing Options. ! (line 97) * JDIR: Directory Options. (line 29) * MDIR: Directory Options. (line 29) * nostdinc: Preprocessing Options. ! (line 105) * P: Preprocessing Options. ! (line 181) * pedantic: Error and Warning Options. (line 38) * pedantic-errors: Error and Warning Options. (line 57) * static-libgfortran: Link Options. (line 11) * std=STD option: Fortran Dialect Options. ! (line 188) * UNAME: Preprocessing Options. ! (line 187) * undef: Preprocessing Options. ! (line 110) * Waliasing: Error and Warning Options. (line 69) * Walign-commons: Error and Warning Options. *************** both forms. *** 19195,19207 **** * Wcharacter-truncation: Error and Warning Options. (line 106) * Wcompare-reals: Error and Warning Options. ! (line 237) * Wconversion: Error and Warning Options. (line 115) * Wconversion-extra: Error and Warning Options. (line 119) * Werror: Error and Warning Options. ! (line 249) * Wextra: Error and Warning Options. (line 123) * Wfunction-elimination: Error and Warning Options. --- 19444,19456 ---- * Wcharacter-truncation: Error and Warning Options. (line 106) * Wcompare-reals: Error and Warning Options. ! (line 238) * Wconversion: Error and Warning Options. (line 115) * Wconversion-extra: Error and Warning Options. (line 119) * Werror: Error and Warning Options. ! (line 250) * Wextra: Error and Warning Options. (line 123) * Wfunction-elimination: Error and Warning Options. *************** both forms. *** 19223,19235 **** * Wrealloc-lhs: Error and Warning Options. (line 220) * Wrealloc-lhs-all: Error and Warning Options. ! (line 232) * Wsurprising: Error and Warning Options. (line 153) * Wtabs: Error and Warning Options. (line 175) * Wtargt-lifetime: Error and Warning Options. ! (line 241) * Wunderflow: Error and Warning Options. (line 183) * Wunused-dummy-argument: Error and Warning Options. --- 19472,19484 ---- * Wrealloc-lhs: Error and Warning Options. (line 220) * Wrealloc-lhs-all: Error and Warning Options. ! (line 233) * Wsurprising: Error and Warning Options. (line 153) * Wtabs: Error and Warning Options. (line 175) * Wtargt-lifetime: Error and Warning Options. ! (line 242) * Wunderflow: Error and Warning Options. (line 183) * Wunused-dummy-argument: Error and Warning Options. *************** both forms. *** 19239,19245 **** * Wuse-without-only: Error and Warning Options. (line 195) * Wzerotrip: Error and Warning Options. ! (line 245)  File: gfortran.info, Node: Keyword Index, Prev: Option Index, Up: Top --- 19488,19494 ---- * Wuse-without-only: Error and Warning Options. (line 195) * Wzerotrip: Error and Warning Options. ! (line 246)  File: gfortran.info, Node: Keyword Index, Prev: Option Index, Up: Top *************** Keyword Index *** 19275,19286 **** * ABS: ABS. (line 6) * absolute value: ABS. (line 6) * ACCESS: ACCESS. (line 6) ! * ACCESS='STREAM' I/O: Fortran 2003 status. (line 103) * ACHAR: ACHAR. (line 6) * ACOS: ACOS. (line 6) * ACOSH: ACOSH. (line 6) - * adjust string: ADJUSTL. (line 6) * adjust string <1>: ADJUSTR. (line 6) * ADJUSTL: ADJUSTL. (line 6) * ADJUSTR: ADJUSTR. (line 6) * AIMAG: AIMAG. (line 6) --- 19524,19535 ---- * ABS: ABS. (line 6) * absolute value: ABS. (line 6) * ACCESS: ACCESS. (line 6) ! * ACCESS='STREAM' I/O: Fortran 2003 status. (line 105) * ACHAR: ACHAR. (line 6) * ACOS: ACOS. (line 6) * ACOSH: ACOSH. (line 6) * adjust string <1>: ADJUSTR. (line 6) + * adjust string: ADJUSTL. (line 6) * ADJUSTL: ADJUSTL. (line 6) * ADJUSTR: ADJUSTR. (line 6) * AIMAG: AIMAG. (line 6) *************** Keyword Index *** 19289,19304 **** * ALGAMA: LOG_GAMMA. (line 6) * aliasing: Error and Warning Options. (line 69) * alignment of COMMON blocks: Error and Warning Options. (line 210) - * alignment of COMMON blocks <1>: Code Gen Options. (line 334) * ALL: ALL. (line 6) * all warnings: Error and Warning Options. (line 61) * ALLOCATABLE components of derived types: Fortran 2003 status. ! (line 101) * ALLOCATABLE dummy arguments: Fortran 2003 status. (line 99) ! * ALLOCATABLE function results: Fortran 2003 status. (line 100) * ALLOCATED: ALLOCATED. (line 6) * allocation, moving: MOVE_ALLOC. (line 6) * allocation, status: ALLOCATED. (line 6) --- 19538,19553 ---- * ALGAMA: LOG_GAMMA. (line 6) * aliasing: Error and Warning Options. (line 69) + * alignment of COMMON blocks <1>: Code Gen Options. (line 338) * alignment of COMMON blocks: Error and Warning Options. (line 210) * ALL: ALL. (line 6) * all warnings: Error and Warning Options. (line 61) * ALLOCATABLE components of derived types: Fortran 2003 status. ! (line 103) * ALLOCATABLE dummy arguments: Fortran 2003 status. (line 99) ! * ALLOCATABLE function results: Fortran 2003 status. (line 101) * ALLOCATED: ALLOCATED. (line 6) * allocation, moving: MOVE_ALLOC. (line 6) * allocation, status: ALLOCATED. (line 6) *************** Keyword Index *** 19317,19338 **** * area hyperbolic tangent: ATANH. (line 6) * argument list functions: Argument list functions. (line 6) ! * arguments, to program: COMMAND_ARGUMENT_COUNT. (line 6) ! * arguments, to program <1>: GETARG. (line 6) ! * arguments, to program <2>: GET_COMMAND. (line 6) ! * arguments, to program <3>: GET_COMMAND_ARGUMENT. (line 6) - * arguments, to program <4>: IARGC. (line 6) * array, add elements: SUM. (line 6) * array, AND: IALL. (line 6) - * array, apply condition: ALL. (line 6) * array, apply condition <1>: ANY. (line 6) ! * array, bounds checking: Code Gen Options. (line 141) * array, change dimensions: RESHAPE. (line 6) * array, combine arrays: MERGE. (line 6) - * array, condition testing: ALL. (line 6) * array, condition testing <1>: ANY. (line 6) * array, conditionally add elements: SUM. (line 6) * array, conditionally count elements: COUNT. (line 6) * array, conditionally multiply elements: PRODUCT. (line 6) --- 19566,19587 ---- * area hyperbolic tangent: ATANH. (line 6) * argument list functions: Argument list functions. (line 6) ! * arguments, to program <1>: IARGC. (line 6) ! * arguments, to program <2>: GET_COMMAND_ARGUMENT. (line 6) ! * arguments, to program <3>: GET_COMMAND. (line 6) ! * arguments, to program <4>: GETARG. (line 6) ! * arguments, to program: COMMAND_ARGUMENT_COUNT. (line 6) * array, add elements: SUM. (line 6) * array, AND: IALL. (line 6) * array, apply condition <1>: ANY. (line 6) ! * array, apply condition: ALL. (line 6) ! * array, bounds checking: Code Gen Options. (line 143) * array, change dimensions: RESHAPE. (line 6) * array, combine arrays: MERGE. (line 6) * array, condition testing <1>: ANY. (line 6) + * array, condition testing: ALL. (line 6) * array, conditionally add elements: SUM. (line 6) * array, conditionally count elements: COUNT. (line 6) * array, conditionally multiply elements: PRODUCT. (line 6) *************** Keyword Index *** 19342,19349 **** * array, duplicate elements: SPREAD. (line 6) * array, element counting: COUNT. (line 6) * array, gather elements: PACK. (line 6) - * array, increase dimension: SPREAD. (line 6) * array, increase dimension <1>: UNPACK. (line 6) * array, indices of type real: Real array indices. (line 6) * array, location of maximum element: MAXLOC. (line 6) * array, location of minimum element: MINLOC. (line 6) --- 19591,19598 ---- * array, duplicate elements: SPREAD. (line 6) * array, element counting: COUNT. (line 6) * array, gather elements: PACK. (line 6) * array, increase dimension <1>: UNPACK. (line 6) + * array, increase dimension: SPREAD. (line 6) * array, indices of type real: Real array indices. (line 6) * array, location of maximum element: MAXLOC. (line 6) * array, location of minimum element: MINLOC. (line 6) *************** Keyword Index *** 19352,19359 **** * array, merge arrays: MERGE. (line 6) * array, minimum value: MINVAL. (line 6) * array, multiply elements: PRODUCT. (line 6) - * array, number of elements: COUNT. (line 6) * array, number of elements <1>: SIZE. (line 6) * array, OR: IANY. (line 6) * array, packing: PACK. (line 6) * array, parity: IPARITY. (line 6) --- 19601,19608 ---- * array, merge arrays: MERGE. (line 6) * array, minimum value: MINVAL. (line 6) * array, multiply elements: PRODUCT. (line 6) * array, number of elements <1>: SIZE. (line 6) + * array, number of elements: COUNT. (line 6) * array, OR: IANY. (line 6) * array, packing: PACK. (line 6) * array, parity: IPARITY. (line 6) *************** Keyword Index *** 19372,19379 **** * array, unpacking: UNPACK. (line 6) * array, upper bound: UBOUND. (line 6) * array, XOR: IPARITY. (line 6) - * ASCII collating sequence: ACHAR. (line 6) * ASCII collating sequence <1>: IACHAR. (line 6) * ASIN: ASIN. (line 6) * ASINH: ASINH. (line 6) * ASSOCIATED: ASSOCIATED. (line 6) --- 19621,19628 ---- * array, unpacking: UNPACK. (line 6) * array, upper bound: UBOUND. (line 6) * array, XOR: IPARITY. (line 6) * ASCII collating sequence <1>: IACHAR. (line 6) + * ASCII collating sequence: ACHAR. (line 6) * ASIN: ASIN. (line 6) * ASINH: ASINH. (line 6) * ASSOCIATED: ASSOCIATED. (line 6) *************** Keyword Index *** 19395,19402 **** * Atomic subroutine, XOR with fetch: ATOMIC_FETCH_XOR. (line 6) * ATOMIC_ADD: ATOMIC_ADD. (line 6) * ATOMIC_AND: ATOMIC_AND. (line 6) - * ATOMIC_DEFINE: ATOMIC_CAS. (line 6) * ATOMIC_DEFINE <1>: ATOMIC_DEFINE. (line 6) * ATOMIC_FETCH_ADD: ATOMIC_FETCH_ADD. (line 6) * ATOMIC_FETCH_AND: ATOMIC_FETCH_AND. (line 6) * ATOMIC_FETCH_OR: ATOMIC_FETCH_OR. (line 6) --- 19644,19651 ---- * Atomic subroutine, XOR with fetch: ATOMIC_FETCH_XOR. (line 6) * ATOMIC_ADD: ATOMIC_ADD. (line 6) * ATOMIC_AND: ATOMIC_AND. (line 6) * ATOMIC_DEFINE <1>: ATOMIC_DEFINE. (line 6) + * ATOMIC_DEFINE: ATOMIC_CAS. (line 6) * ATOMIC_FETCH_ADD: ATOMIC_FETCH_ADD. (line 6) * ATOMIC_FETCH_AND: ATOMIC_FETCH_AND. (line 6) * ATOMIC_FETCH_OR: ATOMIC_FETCH_OR. (line 6) *************** Keyword Index *** 19409,19427 **** (line 56) * BACKSPACE: Read/Write after EOF marker. (line 6) * BACKTRACE: BACKTRACE. (line 6) ! * backtrace: Debugging Options. (line 61) ! * backtrace <1>: BACKTRACE. (line 6) * base 10 logarithm function: LOG10. (line 6) * BESJ0: BESSEL_J0. (line 6) * BESJ1: BESSEL_J1. (line 6) * BESJN: BESSEL_JN. (line 6) * Bessel function, first kind: BESSEL_J0. (line 6) ! * Bessel function, first kind <1>: BESSEL_J1. (line 6) ! * Bessel function, first kind <2>: BESSEL_JN. (line 6) * Bessel function, second kind: BESSEL_Y0. (line 6) - * Bessel function, second kind <1>: BESSEL_Y1. (line 6) - * Bessel function, second kind <2>: BESSEL_YN. (line 6) * BESSEL_J0: BESSEL_J0. (line 6) * BESSEL_J1: BESSEL_J1. (line 6) * BESSEL_JN: BESSEL_JN. (line 6) --- 19658,19676 ---- (line 56) * BACKSPACE: Read/Write after EOF marker. (line 6) + * backtrace: BACKTRACE. (line 6) * BACKTRACE: BACKTRACE. (line 6) ! * backtrace: Debugging Options. (line 62) * base 10 logarithm function: LOG10. (line 6) * BESJ0: BESSEL_J0. (line 6) * BESJ1: BESSEL_J1. (line 6) * BESJN: BESSEL_JN. (line 6) + * Bessel function, first kind <1>: BESSEL_JN. (line 6) + * Bessel function, first kind <2>: BESSEL_J1. (line 6) * Bessel function, first kind: BESSEL_J0. (line 6) ! * Bessel function, second kind <1>: BESSEL_YN. (line 6) ! * Bessel function, second kind <2>: BESSEL_Y1. (line 6) * Bessel function, second kind: BESSEL_Y0. (line 6) * BESSEL_J0: BESSEL_J0. (line 6) * BESSEL_J1: BESSEL_J1. (line 6) * BESSEL_JN: BESSEL_JN. (line 6) *************** Keyword Index *** 19433,19480 **** * BESYN: BESSEL_YN. (line 6) * BGE: BGE. (line 6) * BGT: BGT. (line 6) - * binary representation: POPCNT. (line 6) * binary representation <1>: POPPAR. (line 6) * bits set: POPCNT. (line 6) * bits, AND of array elements: IALL. (line 6) * bits, clear: IBCLR. (line 6) * bits, extract: IBITS. (line 6) * bits, get: IBITS. (line 6) * bits, merge: MERGE_BITS. (line 6) - * bits, move: MVBITS. (line 6) * bits, move <1>: TRANSFER. (line 6) * bits, negate: NOT. (line 6) * bits, number of: BIT_SIZE. (line 6) * bits, OR of array elements: IANY. (line 6) * bits, set: IBSET. (line 6) * bits, shift: ISHFT. (line 6) * bits, shift circular: ISHFTC. (line 6) - * bits, shift left: LSHIFT. (line 6) * bits, shift left <1>: SHIFTL. (line 6) * bits, shift right: RSHIFT. (line 6) - * bits, shift right <1>: SHIFTA. (line 6) - * bits, shift right <2>: SHIFTR. (line 6) * bits, testing: BTEST. (line 6) * bits, unset: IBCLR. (line 6) * bits, XOR of array elements: IPARITY. (line 6) ! * bitwise comparison: BGE. (line 6) ! * bitwise comparison <1>: BGT. (line 6) * bitwise comparison <2>: BLE. (line 6) ! * bitwise comparison <3>: BLT. (line 6) ! * bitwise logical and: AND. (line 6) * bitwise logical and <1>: IAND. (line 6) ! * bitwise logical exclusive or: IEOR. (line 6) * bitwise logical exclusive or <1>: XOR. (line 6) * bitwise logical not: NOT. (line 6) - * bitwise logical or: IOR. (line 6) * bitwise logical or <1>: OR. (line 6) ! * BIT_SIZE: BIT_SIZE. (line 6) * BLE: BLE. (line 6) * BLT: BLT. (line 6) ! * bounds checking: Code Gen Options. (line 141) * BOZ literal constants: BOZ literal constants. (line 6) * BTEST: BTEST. (line 6) * CABS: ABS. (line 6) * calling convention: Code Gen Options. (line 25) * CCOS: COS. (line 6) --- 19682,19735 ---- * BESYN: BESSEL_YN. (line 6) * BGE: BGE. (line 6) * BGT: BGT. (line 6) * binary representation <1>: POPPAR. (line 6) + * binary representation: POPCNT. (line 6) + * BIT_SIZE: BIT_SIZE. (line 6) * bits set: POPCNT. (line 6) * bits, AND of array elements: IALL. (line 6) * bits, clear: IBCLR. (line 6) * bits, extract: IBITS. (line 6) * bits, get: IBITS. (line 6) * bits, merge: MERGE_BITS. (line 6) * bits, move <1>: TRANSFER. (line 6) + * bits, move: MVBITS. (line 6) * bits, negate: NOT. (line 6) * bits, number of: BIT_SIZE. (line 6) * bits, OR of array elements: IANY. (line 6) * bits, set: IBSET. (line 6) * bits, shift: ISHFT. (line 6) * bits, shift circular: ISHFTC. (line 6) * bits, shift left <1>: SHIFTL. (line 6) + * bits, shift left: LSHIFT. (line 6) + * bits, shift right <1>: SHIFTR. (line 6) + * bits, shift right <2>: SHIFTA. (line 6) * bits, shift right: RSHIFT. (line 6) * bits, testing: BTEST. (line 6) * bits, unset: IBCLR. (line 6) * bits, XOR of array elements: IPARITY. (line 6) ! * bitwise comparison <1>: BLT. (line 6) * bitwise comparison <2>: BLE. (line 6) ! * bitwise comparison <3>: BGT. (line 6) ! * bitwise comparison: BGE. (line 6) * bitwise logical and <1>: IAND. (line 6) ! * bitwise logical and: AND. (line 6) * bitwise logical exclusive or <1>: XOR. (line 6) + * bitwise logical exclusive or: IEOR. (line 6) * bitwise logical not: NOT. (line 6) * bitwise logical or <1>: OR. (line 6) ! * bitwise logical or: IOR. (line 6) * BLE: BLE. (line 6) * BLT: BLT. (line 6) ! * bounds checking: Code Gen Options. (line 143) * BOZ literal constants: BOZ literal constants. (line 6) * BTEST: BTEST. (line 6) + * C_ASSOCIATED: C_ASSOCIATED. (line 6) + * C_F_POINTER: C_F_POINTER. (line 6) + * C_F_PROCPOINTER: C_F_PROCPOINTER. (line 6) + * C_FUNLOC: C_FUNLOC. (line 6) + * C_LOC: C_LOC. (line 6) + * C_SIZEOF: C_SIZEOF. (line 6) * CABS: ABS. (line 6) * calling convention: Code Gen Options. (line 25) * CCOS: COS. (line 6) *************** Keyword Index *** 19484,19511 **** * CDLOG: LOG. (line 6) * CDSIN: SIN. (line 6) * CDSQRT: SQRT. (line 6) * CEILING: CEILING. (line 6) * ceiling: ANINT. (line 6) - * ceiling <1>: CEILING. (line 6) * CEXP: EXP. (line 6) * CHAR: CHAR. (line 6) * character kind: SELECTED_CHAR_KIND. (line 6) * character set: Fortran Dialect Options. (line 50) * CHDIR: CHDIR. (line 6) ! * checking array temporaries: Code Gen Options. (line 141) ! * checking subscripts: Code Gen Options. (line 141) * CHMOD: CHMOD. (line 6) * clock ticks: MCLOCK. (line 6) - * clock ticks <1>: MCLOCK8. (line 6) - * clock ticks <2>: SYSTEM_CLOCK. (line 6) * CLOG: LOG. (line 6) * CMPLX: CMPLX. (line 6) ! * coarray, IMAGE_INDEX: IMAGE_INDEX. (line 6) ! * coarray, lower bound: LCOBOUND. (line 6) ! * coarray, NUM_IMAGES: NUM_IMAGES. (line 6) ! * coarray, THIS_IMAGE: THIS_IMAGE. (line 6) ! * coarray, upper bound: UCOBOUND. (line 6) * Coarray, _gfortran_caf_atomic_cas: _gfortran_caf_atomic_cas. (line 6) * Coarray, _gfortran_caf_atomic_define: _gfortran_caf_atomic_define. --- 19739,19766 ---- * CDLOG: LOG. (line 6) * CDSIN: SIN. (line 6) * CDSQRT: SQRT. (line 6) + * ceiling: CEILING. (line 6) * CEILING: CEILING. (line 6) * ceiling: ANINT. (line 6) * CEXP: EXP. (line 6) * CHAR: CHAR. (line 6) * character kind: SELECTED_CHAR_KIND. (line 6) * character set: Fortran Dialect Options. (line 50) * CHDIR: CHDIR. (line 6) ! * checking array temporaries: Code Gen Options. (line 143) ! * checking subscripts: Code Gen Options. (line 143) * CHMOD: CHMOD. (line 6) + * clock ticks <1>: SYSTEM_CLOCK. (line 6) + * clock ticks <2>: MCLOCK8. (line 6) * clock ticks: MCLOCK. (line 6) * CLOG: LOG. (line 6) * CMPLX: CMPLX. (line 6) ! * CO_BROADCAST: CO_BROADCAST. (line 6) ! * CO_MAX: CO_MAX. (line 6) ! * CO_MIN: CO_MIN. (line 6) ! * CO_REDUCE: CO_REDUCE. (line 6) ! * CO_SUM: CO_SUM. (line 6) * Coarray, _gfortran_caf_atomic_cas: _gfortran_caf_atomic_cas. (line 6) * Coarray, _gfortran_caf_atomic_define: _gfortran_caf_atomic_define. *************** Keyword Index *** 19524,19533 **** (line 6) * Coarray, _gfortran_caf_co_sum: _gfortran_caf_co_sum. (line 6) - * Coarray, _gfortran_caf_deregister: _gfortran_caf_register. - (line 6) * Coarray, _gfortran_caf_deregister <1>: _gfortran_caf_deregister. (line 6) * Coarray, _gfortran_caf_error_stop: _gfortran_caf_error_stop. (line 6) * Coarray, _gfortran_caf_error_stop_str: _gfortran_caf_error_stop_str. --- 19779,19788 ---- (line 6) * Coarray, _gfortran_caf_co_sum: _gfortran_caf_co_sum. (line 6) * Coarray, _gfortran_caf_deregister <1>: _gfortran_caf_deregister. (line 6) + * Coarray, _gfortran_caf_deregister: _gfortran_caf_register. + (line 6) * Coarray, _gfortran_caf_error_stop: _gfortran_caf_error_stop. (line 6) * Coarray, _gfortran_caf_error_stop_str: _gfortran_caf_error_stop_str. *************** Keyword Index *** 19558,19568 **** (line 6) * Coarray, _gfortran_caf_unlock: _gfortran_caf_unlock. (line 6) ! * coarrays: Code Gen Options. (line 127) * Coarrays: Coarray Programming. (line 6) * code generation, conventions: Code Gen Options. (line 6) - * collating sequence, ASCII: ACHAR. (line 6) * collating sequence, ASCII <1>: IACHAR. (line 6) * Collectives, generic reduction: CO_REDUCE. (line 6) * Collectives, maximal value: CO_MAX. (line 6) * Collectives, minimal value: CO_MIN. (line 6) --- 19813,19828 ---- (line 6) * Coarray, _gfortran_caf_unlock: _gfortran_caf_unlock. (line 6) ! * coarray, IMAGE_INDEX: IMAGE_INDEX. (line 6) ! * coarray, lower bound: LCOBOUND. (line 6) ! * coarray, NUM_IMAGES: NUM_IMAGES. (line 6) ! * coarray, THIS_IMAGE: THIS_IMAGE. (line 6) ! * coarray, upper bound: UCOBOUND. (line 6) * Coarrays: Coarray Programming. (line 6) + * coarrays: Code Gen Options. (line 129) * code generation, conventions: Code Gen Options. (line 6) * collating sequence, ASCII <1>: IACHAR. (line 6) + * collating sequence, ASCII: ACHAR. (line 6) * Collectives, generic reduction: CO_REDUCE. (line 6) * Collectives, maximal value: CO_MAX. (line 6) * Collectives, minimal value: CO_MIN. (line 6) *************** Keyword Index *** 19572,19587 **** (line 6) * command options: Invoking GNU Fortran. (line 6) ! * command-line arguments: COMMAND_ARGUMENT_COUNT. (line 6) ! * command-line arguments <1>: GETARG. (line 6) ! * command-line arguments <2>: GET_COMMAND. (line 6) ! * command-line arguments <3>: GET_COMMAND_ARGUMENT. (line 6) ! * command-line arguments <4>: IARGC. (line 6) * command-line arguments, number of: COMMAND_ARGUMENT_COUNT. (line 6) - * command-line arguments, number of <1>: IARGC. (line 6) * COMMAND_ARGUMENT_COUNT: COMMAND_ARGUMENT_COUNT. (line 6) * COMMON: Volatile COMMON blocks. --- 19832,19847 ---- (line 6) * command options: Invoking GNU Fortran. (line 6) ! * command-line arguments <1>: IARGC. (line 6) ! * command-line arguments <2>: GET_COMMAND_ARGUMENT. (line 6) ! * command-line arguments <3>: GET_COMMAND. (line 6) ! * command-line arguments <4>: GETARG. (line 6) ! * command-line arguments: COMMAND_ARGUMENT_COUNT. (line 6) ! * command-line arguments, number of <1>: IARGC. (line 6) * command-line arguments, number of: COMMAND_ARGUMENT_COUNT. (line 6) * COMMAND_ARGUMENT_COUNT: COMMAND_ARGUMENT_COUNT. (line 6) * COMMON: Volatile COMMON blocks. *************** Keyword Index *** 19594,19605 **** * complex conjugate: CONJG. (line 6) * Complex function: Alternate complex function syntax. (line 6) * complex numbers, conversion to: CMPLX. (line 6) - * complex numbers, conversion to <1>: COMPLEX. (line 6) - * complex numbers, conversion to <2>: DCMPLX. (line 6) * complex numbers, imaginary part: AIMAG. (line 6) - * complex numbers, real part: DREAL. (line 6) * complex numbers, real part <1>: REAL. (line 6) * Conditional compilation: Preprocessing and conditional compilation. (line 6) * CONJG: CONJG. (line 6) --- 19854,19865 ---- * complex conjugate: CONJG. (line 6) * Complex function: Alternate complex function syntax. (line 6) + * complex numbers, conversion to <1>: DCMPLX. (line 6) + * complex numbers, conversion to <2>: COMPLEX. (line 6) * complex numbers, conversion to: CMPLX. (line 6) * complex numbers, imaginary part: AIMAG. (line 6) * complex numbers, real part <1>: REAL. (line 6) + * complex numbers, real part: DREAL. (line 6) * Conditional compilation: Preprocessing and conditional compilation. (line 6) * CONJG: CONJG. (line 6) *************** Keyword Index *** 19609,19633 **** * Contributors: Contributors. (line 6) * conversion: Error and Warning Options. (line 115) - * conversion <1>: Error and Warning Options. - (line 119) * conversion, to character: CHAR. (line 6) * conversion, to complex: CMPLX. (line 6) ! * conversion, to complex <1>: COMPLEX. (line 6) ! * conversion, to complex <2>: DCMPLX. (line 6) * conversion, to integer: Implicitly convert LOGICAL and INTEGER values. (line 6) ! * conversion, to integer <1>: IACHAR. (line 6) ! * conversion, to integer <2>: ICHAR. (line 6) ! * conversion, to integer <3>: INT. (line 6) ! * conversion, to integer <4>: INT2. (line 6) ! * conversion, to integer <5>: INT8. (line 6) ! * conversion, to integer <6>: LONG. (line 6) * conversion, to logical: Implicitly convert LOGICAL and INTEGER values. (line 6) - * conversion, to logical <1>: LOGICAL. (line 6) - * conversion, to real: DBLE. (line 6) * conversion, to real <1>: REAL. (line 6) * conversion, to string: CTIME. (line 6) * CONVERT specifier: CONVERT specifier. (line 6) * core, dump: ABORT. (line 6) --- 19869,19891 ---- * Contributors: Contributors. (line 6) * conversion: Error and Warning Options. (line 115) * conversion, to character: CHAR. (line 6) + * conversion, to complex <1>: DCMPLX. (line 6) + * conversion, to complex <2>: COMPLEX. (line 6) * conversion, to complex: CMPLX. (line 6) ! * conversion, to integer <1>: LONG. (line 6) ! * conversion, to integer <2>: INT8. (line 6) ! * conversion, to integer <3>: INT2. (line 6) ! * conversion, to integer <4>: INT. (line 6) ! * conversion, to integer <5>: ICHAR. (line 6) ! * conversion, to integer <6>: IACHAR. (line 6) * conversion, to integer: Implicitly convert LOGICAL and INTEGER values. (line 6) ! * conversion, to logical <1>: LOGICAL. (line 6) * conversion, to logical: Implicitly convert LOGICAL and INTEGER values. (line 6) * conversion, to real <1>: REAL. (line 6) + * conversion, to real: DBLE. (line 6) * conversion, to string: CTIME. (line 6) * CONVERT specifier: CONVERT specifier. (line 6) * core, dump: ABORT. (line 6) *************** Keyword Index *** 19638,19672 **** * cosine, hyperbolic, inverse: ACOSH. (line 6) * cosine, inverse: ACOS. (line 6) * COUNT: COUNT. (line 6) - * CO_BROADCAST: CO_BROADCAST. (line 6) - * CO_MAX: CO_MAX. (line 6) - * CO_MIN: CO_MIN. (line 6) - * CO_REDUCE: CO_REDUCE. (line 6) - * CO_SUM: CO_SUM. (line 6) - * CPP: Preprocessing and conditional compilation. - (line 6) * CPP <1>: Preprocessing Options. (line 6) * CPU_TIME: CPU_TIME. (line 6) * Credits: Contributors. (line 6) * CSHIFT: CSHIFT. (line 6) * CSIN: SIN. (line 6) * CSQRT: SQRT. (line 6) * CTIME: CTIME. (line 6) * current date: DATE_AND_TIME. (line 6) ! * current date <1>: FDATE. (line 6) ! * current date <2>: IDATE. (line 6) * current time: DATE_AND_TIME. (line 6) - * current time <1>: FDATE. (line 6) - * current time <2>: ITIME. (line 6) - * current time <3>: TIME. (line 6) - * current time <4>: TIME8. (line 6) - * C_ASSOCIATED: C_ASSOCIATED. (line 6) - * C_FUNLOC: C_FUNLOC. (line 6) - * C_F_POINTER: C_F_POINTER. (line 6) - * C_F_PROCPOINTER: C_F_PROCPOINTER. (line 6) - * C_LOC: C_LOC. (line 6) - * C_SIZEOF: C_SIZEOF. (line 6) * DABS: ABS. (line 6) * DACOS: ACOS. (line 6) * DACOSH: ACOSH. (line 6) --- 19896,19919 ---- * cosine, hyperbolic, inverse: ACOSH. (line 6) * cosine, inverse: ACOS. (line 6) * COUNT: COUNT. (line 6) * CPP <1>: Preprocessing Options. (line 6) + * CPP: Preprocessing and conditional compilation. + (line 6) * CPU_TIME: CPU_TIME. (line 6) * Credits: Contributors. (line 6) * CSHIFT: CSHIFT. (line 6) * CSIN: SIN. (line 6) * CSQRT: SQRT. (line 6) * CTIME: CTIME. (line 6) + * current date <1>: IDATE. (line 6) + * current date <2>: FDATE. (line 6) * current date: DATE_AND_TIME. (line 6) ! * current time <1>: TIME8. (line 6) ! * current time <2>: TIME. (line 6) ! * current time <3>: ITIME. (line 6) ! * current time <4>: FDATE. (line 6) * current time: DATE_AND_TIME. (line 6) * DABS: ABS. (line 6) * DACOS: ACOS. (line 6) * DACOSH: ACOSH. (line 6) *************** Keyword Index *** 19675,19683 **** * DATAN: ATAN. (line 6) * DATAN2: ATAN2. (line 6) * DATANH: ATANH. (line 6) * date, current: DATE_AND_TIME. (line 6) - * date, current <1>: FDATE. (line 6) - * date, current <2>: IDATE. (line 6) * DATE_AND_TIME: DATE_AND_TIME. (line 6) * DBESJ0: BESSEL_J0. (line 6) * DBESJ1: BESSEL_J1. (line 6) --- 19922,19930 ---- * DATAN: ATAN. (line 6) * DATAN2: ATAN2. (line 6) * DATANH: ATANH. (line 6) + * date, current <1>: IDATE. (line 6) + * date, current <2>: FDATE. (line 6) * date, current: DATE_AND_TIME. (line 6) * DATE_AND_TIME: DATE_AND_TIME. (line 6) * DBESJ0: BESSEL_J0. (line 6) * DBESJ1: BESSEL_J1. (line 6) *************** Keyword Index *** 19694,19711 **** * debugging information options: Debugging Options. (line 6) * debugging, preprocessor: Preprocessing Options. (line 26) - * debugging, preprocessor <1>: Preprocessing Options. - (line 35) - * debugging, preprocessor <2>: Preprocessing Options. - (line 41) - * debugging, preprocessor <3>: Preprocessing Options. - (line 44) - * debugging, preprocessor <4>: Preprocessing Options. - (line 51) * DECODE: ENCODE and DECODE statements. (line 6) - * delayed execution: ALARM. (line 6) * delayed execution <1>: SLEEP. (line 6) * DEXP: EXP. (line 6) * DFLOAT: REAL. (line 6) * DGAMMA: GAMMA. (line 6) --- 19941,19950 ---- * debugging information options: Debugging Options. (line 6) * debugging, preprocessor: Preprocessing Options. (line 26) * DECODE: ENCODE and DECODE statements. (line 6) * delayed execution <1>: SLEEP. (line 6) + * delayed execution: ALARM. (line 6) * DEXP: EXP. (line 6) * DFLOAT: REAL. (line 6) * DGAMMA: GAMMA. (line 6) *************** Keyword Index *** 19742,19761 **** * DTIME: DTIME. (line 6) * dummy argument, unused: Error and Warning Options. (line 199) * elapsed time: DTIME. (line 6) - * elapsed time <1>: SECNDS. (line 6) - * elapsed time <2>: SECOND. (line 6) * Elimination of functions with identical argument lists: Code Gen Options. ! (line 361) * ENCODE: ENCODE and DECODE statements. (line 6) * ENUM statement: Fortran 2003 status. (line 93) * ENUMERATOR statement: Fortran 2003 status. (line 93) ! * environment variable: Environment Variables. (line 6) - * environment variable <1>: Runtime. (line 6) * environment variable <2>: GETENV. (line 6) ! * environment variable <3>: GET_ENVIRONMENT_VARIABLE. (line 6) * EOF: Read/Write after EOF marker. (line 6) --- 19981,20000 ---- * DTIME: DTIME. (line 6) * dummy argument, unused: Error and Warning Options. (line 199) + * elapsed time <1>: SECOND. (line 6) + * elapsed time <2>: SECNDS. (line 6) * elapsed time: DTIME. (line 6) * Elimination of functions with identical argument lists: Code Gen Options. ! (line 365) * ENCODE: ENCODE and DECODE statements. (line 6) * ENUM statement: Fortran 2003 status. (line 93) * ENUMERATOR statement: Fortran 2003 status. (line 93) ! * environment variable <1>: GET_ENVIRONMENT_VARIABLE. (line 6) * environment variable <2>: GETENV. (line 6) ! * environment variable <3>: Runtime. (line 6) ! * environment variable: Environment Variables. (line 6) * EOF: Read/Write after EOF marker. (line 6) *************** Keyword Index *** 19775,19792 **** * ETIME: ETIME. (line 6) * Euclidean distance: HYPOT. (line 6) * Euclidean vector norm: NORM2. (line 6) - * Events, EVENT_QUERY: EVENT_QUERY. (line 6) * EVENT_QUERY: EVENT_QUERY. (line 6) * EXECUTE_COMMAND_LINE: EXECUTE_COMMAND_LINE. (line 6) * EXIT: EXIT. (line 6) * EXP: EXP. (line 6) * EXPONENT: EXPONENT. (line 6) * exponential function: EXP. (line 6) - * exponential function, inverse: LOG. (line 6) * exponential function, inverse <1>: LOG10. (line 6) ! * expression size: C_SIZEOF. (line 6) * expression size <1>: SIZEOF. (line 6) * EXTENDS_TYPE_OF: EXTENDS_TYPE_OF. (line 6) * extensions: Extensions. (line 6) * extensions, implemented: Extensions implemented in GNU Fortran. --- 20014,20031 ---- * ETIME: ETIME. (line 6) * Euclidean distance: HYPOT. (line 6) * Euclidean vector norm: NORM2. (line 6) * EVENT_QUERY: EVENT_QUERY. (line 6) + * Events, EVENT_QUERY: EVENT_QUERY. (line 6) * EXECUTE_COMMAND_LINE: EXECUTE_COMMAND_LINE. (line 6) * EXIT: EXIT. (line 6) * EXP: EXP. (line 6) * EXPONENT: EXPONENT. (line 6) * exponential function: EXP. (line 6) * exponential function, inverse <1>: LOG10. (line 6) ! * exponential function, inverse: LOG. (line 6) * expression size <1>: SIZEOF. (line 6) + * expression size: C_SIZEOF. (line 6) * EXTENDS_TYPE_OF: EXTENDS_TYPE_OF. (line 6) * extensions: Extensions. (line 6) * extensions, implemented: Extensions implemented in GNU Fortran. *************** Keyword Index *** 19796,19802 **** * extra warnings: Error and Warning Options. (line 123) * f2c calling convention: Code Gen Options. (line 25) - * f2c calling convention <1>: Code Gen Options. (line 110) * Factorial function: GAMMA. (line 6) * FDATE: FDATE. (line 6) * FDL, GNU Free Documentation License: GNU Free Documentation License. --- 20035,20040 ---- *************** Keyword Index *** 19805,19833 **** * FGETC: FGETC. (line 6) * file format, fixed: Fortran Dialect Options. (line 11) - * file format, fixed <1>: Fortran Dialect Options. - (line 73) * file format, free: Fortran Dialect Options. (line 11) - * file format, free <1>: Fortran Dialect Options. - (line 86) * file operation, file number: FNUM. (line 6) * file operation, flush: FLUSH. (line 6) - * file operation, position: FSEEK. (line 6) * file operation, position <1>: FTELL. (line 6) ! * file operation, read character: FGET. (line 6) * file operation, read character <1>: FGETC. (line 6) * file operation, seek: FSEEK. (line 6) - * file operation, write character: FPUT. (line 6) * file operation, write character <1>: FPUTC. (line 6) * file system, access mode: ACCESS. (line 6) * file system, change access mode: CHMOD. (line 6) - * file system, create link: LINK. (line 6) * file system, create link <1>: SYMLNK. (line 6) * file system, file creation mask: UMASK. (line 6) * file system, file status: FSTAT. (line 6) - * file system, file status <1>: LSTAT. (line 6) - * file system, file status <2>: STAT. (line 6) * file system, hard link: LINK. (line 6) * file system, remove file: UNLINK. (line 6) * file system, rename file: RENAME. (line 6) --- 20043,20067 ---- * FGETC: FGETC. (line 6) * file format, fixed: Fortran Dialect Options. (line 11) * file format, free: Fortran Dialect Options. (line 11) * file operation, file number: FNUM. (line 6) * file operation, flush: FLUSH. (line 6) * file operation, position <1>: FTELL. (line 6) ! * file operation, position: FSEEK. (line 6) * file operation, read character <1>: FGETC. (line 6) + * file operation, read character: FGET. (line 6) * file operation, seek: FSEEK. (line 6) * file operation, write character <1>: FPUTC. (line 6) + * file operation, write character: FPUT. (line 6) * file system, access mode: ACCESS. (line 6) * file system, change access mode: CHMOD. (line 6) * file system, create link <1>: SYMLNK. (line 6) + * file system, create link: LINK. (line 6) * file system, file creation mask: UMASK. (line 6) + * file system, file status <1>: STAT. (line 6) + * file system, file status <2>: LSTAT. (line 6) * file system, file status: FSTAT. (line 6) * file system, hard link: LINK. (line 6) * file system, remove file: UNLINK. (line 6) * file system, rename file: RENAME. (line 6) *************** Keyword Index *** 19839,19851 **** * floating point, exponent: EXPONENT. (line 6) * floating point, fraction: FRACTION. (line 6) * floating point, nearest different: NEAREST. (line 6) - * floating point, relative spacing: RRSPACING. (line 6) * floating point, relative spacing <1>: SPACING. (line 6) * floating point, scale: SCALE. (line 6) * floating point, set exponent: SET_EXPONENT. (line 6) * FLOOR: FLOOR. (line 6) * floor: AINT. (line 6) - * floor <1>: FLOOR. (line 6) * FLUSH: FLUSH. (line 6) * FLUSH statement: Fortran 2003 status. (line 89) * FNUM: FNUM. (line 6) --- 20073,20085 ---- * floating point, exponent: EXPONENT. (line 6) * floating point, fraction: FRACTION. (line 6) * floating point, nearest different: NEAREST. (line 6) * floating point, relative spacing <1>: SPACING. (line 6) + * floating point, relative spacing: RRSPACING. (line 6) * floating point, scale: SCALE. (line 6) * floating point, set exponent: SET_EXPONENT. (line 6) + * floor: FLOOR. (line 6) * FLOOR: FLOOR. (line 6) * floor: AINT. (line 6) * FLUSH: FLUSH. (line 6) * FLUSH statement: Fortran 2003 status. (line 89) * FNUM: FNUM. (line 6) *************** Keyword Index *** 19858,19864 **** * FPUTC: FPUTC. (line 6) * FRACTION: FRACTION. (line 6) * FREE: FREE. (line 6) ! * Front-end optimization: Code Gen Options. (line 369) * FSEEK: FSEEK. (line 6) * FSTAT: FSTAT. (line 6) * FTELL: FTELL. (line 6) --- 20092,20098 ---- * FPUTC: FPUTC. (line 6) * FRACTION: FRACTION. (line 6) * FREE: FREE. (line 6) ! * Front-end optimization: Code Gen Options. (line 373) * FSEEK: FSEEK. (line 6) * FSTAT: FSTAT. (line 6) * FTELL: FTELL. (line 6) *************** Keyword Index *** 19866,19877 **** (line 216) * g77: GNU Fortran and G77. (line 6) * g77 calling convention: Code Gen Options. (line 25) - * g77 calling convention <1>: Code Gen Options. (line 110) * GAMMA: GAMMA. (line 6) * Gamma function: GAMMA. (line 6) * Gamma function, logarithm of: LOG_GAMMA. (line 6) * GCC: GNU Fortran and GCC. (line 6) * GERROR: GERROR. (line 6) * GETARG: GETARG. (line 6) * GETCWD: GETCWD. (line 6) * GETENV: GETENV. (line 6) --- 20100,20115 ---- (line 216) * g77: GNU Fortran and G77. (line 6) * g77 calling convention: Code Gen Options. (line 25) * GAMMA: GAMMA. (line 6) * Gamma function: GAMMA. (line 6) * Gamma function, logarithm of: LOG_GAMMA. (line 6) * GCC: GNU Fortran and GCC. (line 6) * GERROR: GERROR. (line 6) + * GET_COMMAND: GET_COMMAND. (line 6) + * GET_COMMAND_ARGUMENT: GET_COMMAND_ARGUMENT. + (line 6) + * GET_ENVIRONMENT_VARIABLE: GET_ENVIRONMENT_VARIABLE. + (line 6) * GETARG: GETARG. (line 6) * GETCWD: GETCWD. (line 6) * GETENV: GETENV. (line 6) *************** Keyword Index *** 19879,19889 **** * GETLOG: GETLOG. (line 6) * GETPID: GETPID. (line 6) * GETUID: GETUID. (line 6) - * GET_COMMAND: GET_COMMAND. (line 6) - * GET_COMMAND_ARGUMENT: GET_COMMAND_ARGUMENT. - (line 6) - * GET_ENVIRONMENT_VARIABLE: GET_ENVIRONMENT_VARIABLE. - (line 6) * GMTIME: GMTIME. (line 6) * GNU Compiler Collection: GNU Fortran and GCC. (line 6) * GNU Fortran command options: Invoking GNU Fortran. --- 20117,20122 ---- *************** Keyword Index *** 19922,19933 **** * IERRNO: IERRNO. (line 6) * IFIX: INT. (line 6) * IMAG: AIMAG. (line 6) * images, cosubscript to image index conversion: IMAGE_INDEX. (line 6) * images, index of this image: THIS_IMAGE. (line 6) * images, number of: NUM_IMAGES. (line 6) - * IMAGE_INDEX: IMAGE_INDEX. (line 6) * IMAGPART: AIMAG. (line 6) ! * IMPORT statement: Fortran 2003 status. (line 120) * INCLUDE directive: Directory Options. (line 6) * inclusion, directory search paths for: Directory Options. (line 14) * INDEX: INDEX intrinsic. (line 6) --- 20155,20166 ---- * IERRNO: IERRNO. (line 6) * IFIX: INT. (line 6) * IMAG: AIMAG. (line 6) + * IMAGE_INDEX: IMAGE_INDEX. (line 6) * images, cosubscript to image index conversion: IMAGE_INDEX. (line 6) * images, index of this image: THIS_IMAGE. (line 6) * images, number of: NUM_IMAGES. (line 6) * IMAGPART: AIMAG. (line 6) ! * IMPORT statement: Fortran 2003 status. (line 122) * INCLUDE directive: Directory Options. (line 6) * inclusion, directory search paths for: Directory Options. (line 14) * INDEX: INDEX intrinsic. (line 6) *************** Keyword Index *** 19939,19946 **** (line 6) * intrinsic: Error and Warning Options. (line 188) - * intrinsic <1>: Error and Warning Options. - (line 195) * intrinsic Modules: Intrinsic Modules. (line 6) * intrinsic procedures: Intrinsic Procedures. (line 6) --- 20172,20177 ---- *************** Keyword Index *** 19954,19973 **** * IOSTAT, end of record: IS_IOSTAT_EOR. (line 6) * IPARITY: IPARITY. (line 6) * IRAND: IRAND. (line 6) * ISATTY: ISATTY. (line 6) * ISHFT: ISHFT. (line 6) * ISHFTC: ISHFTC. (line 6) * ISIGN: SIGN. (line 6) * ISNAN: ISNAN. (line 6) ! * ISO_FORTRAN_ENV statement: Fortran 2003 status. (line 128) ! * IS_IOSTAT_END: IS_IOSTAT_END. (line 6) ! * IS_IOSTAT_EOR: IS_IOSTAT_EOR. (line 6) * ITIME: ITIME. (line 6) * KILL: KILL. (line 6) * kind: KIND Type Parameters. (line 6) - * KIND: KIND. (line 6) - * kind <1>: KIND. (line 6) * kind, character: SELECTED_CHAR_KIND. (line 6) * kind, integer: SELECTED_INT_KIND. (line 6) * kind, old-style: Old-style kind specifications. --- 20185,20204 ---- * IOSTAT, end of record: IS_IOSTAT_EOR. (line 6) * IPARITY: IPARITY. (line 6) * IRAND: IRAND. (line 6) + * IS_IOSTAT_END: IS_IOSTAT_END. (line 6) + * IS_IOSTAT_EOR: IS_IOSTAT_EOR. (line 6) * ISATTY: ISATTY. (line 6) * ISHFT: ISHFT. (line 6) * ISHFTC: ISHFTC. (line 6) * ISIGN: SIGN. (line 6) * ISNAN: ISNAN. (line 6) ! * ISO_FORTRAN_ENV statement: Fortran 2003 status. (line 130) * ITIME: ITIME. (line 6) * KILL: KILL. (line 6) + * kind: KIND. (line 6) + * KIND: KIND. (line 6) * kind: KIND Type Parameters. (line 6) * kind, character: SELECTED_CHAR_KIND. (line 6) * kind, integer: SELECTED_INT_KIND. (line 6) * kind, old-style: Old-style kind specifications. *************** Keyword Index *** 19982,19996 **** * left shift, combined: DSHIFTL. (line 6) * LEN: LEN. (line 6) * LEN_TRIM: LEN_TRIM. (line 6) ! * lexical comparison of strings: LGE. (line 6) ! * lexical comparison of strings <1>: LGT. (line 6) * lexical comparison of strings <2>: LLE. (line 6) ! * lexical comparison of strings <3>: LLT. (line 6) * LGAMMA: LOG_GAMMA. (line 6) * LGE: LGE. (line 6) * LGT: LGT. (line 6) * libf2c calling convention: Code Gen Options. (line 25) - * libf2c calling convention <1>: Code Gen Options. (line 110) * libgfortran initialization, set_args: _gfortran_set_args. (line 6) * libgfortran initialization, set_convert: _gfortran_set_convert. (line 6) --- 20213,20226 ---- * left shift, combined: DSHIFTL. (line 6) * LEN: LEN. (line 6) * LEN_TRIM: LEN_TRIM. (line 6) ! * lexical comparison of strings <1>: LLT. (line 6) * lexical comparison of strings <2>: LLE. (line 6) ! * lexical comparison of strings <3>: LGT. (line 6) ! * lexical comparison of strings: LGE. (line 6) * LGAMMA: LOG_GAMMA. (line 6) * LGE: LGE. (line 6) * LGT: LGT. (line 6) * libf2c calling convention: Code Gen Options. (line 25) * libgfortran initialization, set_args: _gfortran_set_args. (line 6) * libgfortran initialization, set_convert: _gfortran_set_convert. (line 6) *************** Keyword Index *** 20012,20032 **** * location of a variable in memory: LOC. (line 6) * LOG: LOG. (line 6) * LOG10: LOG10. (line 6) * logarithm function: LOG. (line 6) * logarithm function with base 10: LOG10. (line 6) * logarithm function, inverse: EXP. (line 6) * LOGICAL: LOGICAL. (line 6) - * logical and, bitwise: AND. (line 6) * logical and, bitwise <1>: IAND. (line 6) ! * logical exclusive or, bitwise: IEOR. (line 6) * logical exclusive or, bitwise <1>: XOR. (line 6) * logical not, bitwise: NOT. (line 6) - * logical or, bitwise: IOR. (line 6) * logical or, bitwise <1>: OR. (line 6) * logical, variable representation: Internal representation of LOGICAL variables. (line 6) * login name: GETLOG. (line 6) - * LOG_GAMMA: LOG_GAMMA. (line 6) * LONG: LONG. (line 6) * LSHIFT: LSHIFT. (line 6) * LSTAT: LSTAT. (line 6) --- 20242,20262 ---- * location of a variable in memory: LOC. (line 6) * LOG: LOG. (line 6) * LOG10: LOG10. (line 6) + * LOG_GAMMA: LOG_GAMMA. (line 6) * logarithm function: LOG. (line 6) * logarithm function with base 10: LOG10. (line 6) * logarithm function, inverse: EXP. (line 6) * LOGICAL: LOGICAL. (line 6) * logical and, bitwise <1>: IAND. (line 6) ! * logical and, bitwise: AND. (line 6) * logical exclusive or, bitwise <1>: XOR. (line 6) + * logical exclusive or, bitwise: IEOR. (line 6) * logical not, bitwise: NOT. (line 6) * logical or, bitwise <1>: OR. (line 6) + * logical or, bitwise: IOR. (line 6) * logical, variable representation: Internal representation of LOGICAL variables. (line 6) * login name: GETLOG. (line 6) * LONG: LONG. (line 6) * LSHIFT: LSHIFT. (line 6) * LSTAT: LSTAT. (line 6) *************** Keyword Index *** 20044,20056 **** * MAX0: MAX. (line 6) * MAX1: MAX. (line 6) * MAXEXPONENT: MAXEXPONENT. (line 6) - * maximum value: MAX. (line 6) * maximum value <1>: MAXVAL. (line 6) * MAXLOC: MAXLOC. (line 6) * MAXVAL: MAXVAL. (line 6) * MCLOCK: MCLOCK. (line 6) * MCLOCK8: MCLOCK8. (line 6) ! * memory checking: Code Gen Options. (line 141) * MERGE: MERGE. (line 6) * MERGE_BITS: MERGE_BITS. (line 6) * messages, error: Error and Warning Options. --- 20274,20286 ---- * MAX0: MAX. (line 6) * MAX1: MAX. (line 6) * MAXEXPONENT: MAXEXPONENT. (line 6) * maximum value <1>: MAXVAL. (line 6) + * maximum value: MAX. (line 6) * MAXLOC: MAXLOC. (line 6) * MAXVAL: MAXVAL. (line 6) * MCLOCK: MCLOCK. (line 6) * MCLOCK8: MCLOCK8. (line 6) ! * memory checking: Code Gen Options. (line 143) * MERGE: MERGE. (line 6) * MERGE_BITS: MERGE_BITS. (line 6) * messages, error: Error and Warning Options. *************** Keyword Index *** 20061,20068 **** * MIN0: MIN. (line 6) * MIN1: MIN. (line 6) * MINEXPONENT: MINEXPONENT. (line 6) - * minimum value: MIN. (line 6) * minimum value <1>: MINVAL. (line 6) * MINLOC: MINLOC. (line 6) * MINVAL: MINVAL. (line 6) * Mixed-language programming: Mixed-Language Programming. --- 20291,20298 ---- * MIN0: MIN. (line 6) * MIN1: MIN. (line 6) * MINEXPONENT: MINEXPONENT. (line 6) * minimum value <1>: MINVAL. (line 6) + * minimum value: MIN. (line 6) * MINLOC: MINLOC. (line 6) * MINVAL: MINVAL. (line 6) * Mixed-language programming: Mixed-Language Programming. *************** Keyword Index *** 20081,20090 **** * module entities: Fortran Dialect Options. (line 68) * module search path: Directory Options. (line 14) - * module search path <1>: Directory Options. (line 29) - * module search path <2>: Directory Options. (line 36) - * MODULO: MODULO. (line 6) * modulo: MODULO. (line 6) * MOVE_ALLOC: MOVE_ALLOC. (line 6) * moving allocation: MOVE_ALLOC. (line 6) * multiply array elements: PRODUCT. (line 6) --- 20311,20318 ---- * module entities: Fortran Dialect Options. (line 68) * module search path: Directory Options. (line 14) * modulo: MODULO. (line 6) + * MODULO: MODULO. (line 6) * MOVE_ALLOC: MOVE_ALLOC. (line 6) * moving allocation: MOVE_ALLOC. (line 6) * multiply array elements: PRODUCT. (line 6) *************** Keyword Index *** 20094,20101 **** (line 6) * natural logarithm function: LOG. (line 6) * NEAREST: NEAREST. (line 6) - * newline: NEW_LINE. (line 6) * NEW_LINE: NEW_LINE. (line 6) * NINT: NINT. (line 6) * norm, Euclidean: NORM2. (line 6) * NORM2: NORM2. (line 6) --- 20322,20329 ---- (line 6) * natural logarithm function: LOG. (line 6) * NEAREST: NEAREST. (line 6) * NEW_LINE: NEW_LINE. (line 6) + * newline: NEW_LINE. (line 6) * NINT: NINT. (line 6) * norm, Euclidean: NORM2. (line 6) * NORM2: NORM2. (line 6) *************** Keyword Index *** 20104,20115 **** * NUM_IMAGES: NUM_IMAGES. (line 6) * open, action: Files opened without an explicit ACTION= specifier. (line 6) * OpenACC: Fortran Dialect Options. (line 106) - * OpenACC <1>: OpenACC. (line 6) - * OpenMP: Fortran Dialect Options. - (line 117) * OpenMP <1>: OpenMP. (line 6) * operators, unary: Unary operators. (line 6) * options inquiry function: COMPILER_OPTIONS. (line 6) * options, code generation: Code Gen Options. (line 6) --- 20332,20343 ---- * NUM_IMAGES: NUM_IMAGES. (line 6) * open, action: Files opened without an explicit ACTION= specifier. (line 6) + * OpenACC <1>: OpenACC. (line 6) * OpenACC: Fortran Dialect Options. (line 106) * OpenMP <1>: OpenMP. (line 6) + * OpenMP: Fortran Dialect Options. + (line 118) * operators, unary: Unary operators. (line 6) * options inquiry function: COMPILER_OPTIONS. (line 6) * options, code generation: Code Gen Options. (line 6) *************** Keyword Index *** 20129,20135 **** * options, preprocessor: Preprocessing Options. (line 6) * options, real kind type promotion: Fortran Dialect Options. ! (line 175) * options, run-time: Code Gen Options. (line 6) * options, runtime: Runtime Options. (line 6) * options, warnings: Error and Warning Options. --- 20357,20363 ---- * options, preprocessor: Preprocessing Options. (line 6) * options, real kind type promotion: Fortran Dialect Options. ! (line 177) * options, run-time: Code Gen Options. (line 6) * options, runtime: Runtime Options. (line 6) * options, warnings: Error and Warning Options. *************** Keyword Index *** 20137,20160 **** * OR: OR. (line 6) * output, newline: NEW_LINE. (line 6) * PACK: PACK. (line 6) - * PARITY: PARITY. (line 6) - * Parity: PARITY. (line 6) * parity: POPPAR. (line 6) * paths, search: Directory Options. (line 14) - * paths, search <1>: Directory Options. (line 29) - * paths, search <2>: Directory Options. (line 36) * PERROR: PERROR. (line 6) ! * pointer checking: Code Gen Options. (line 141) * pointer, C address of pointers: C_F_PROCPOINTER. (line 6) * pointer, C address of procedures: C_FUNLOC. (line 6) * pointer, C association status: C_ASSOCIATED. (line 6) * pointer, convert C to Fortran: C_F_POINTER. (line 6) - * pointer, Cray: Cray pointers. (line 6) - * pointer, cray: FREE. (line 6) * pointer, cray <1>: MALLOC. (line 6) * pointer, disassociated: NULL. (line 6) - * pointer, status: ASSOCIATED. (line 6) * pointer, status <1>: NULL. (line 6) * POPCNT: POPCNT. (line 6) * POPPAR: POPPAR. (line 6) * positive difference: DIM. (line 6) --- 20365,20386 ---- * OR: OR. (line 6) * output, newline: NEW_LINE. (line 6) * PACK: PACK. (line 6) * parity: POPPAR. (line 6) + * Parity: PARITY. (line 6) + * PARITY: PARITY. (line 6) * paths, search: Directory Options. (line 14) * PERROR: PERROR. (line 6) ! * pointer checking: Code Gen Options. (line 143) * pointer, C address of pointers: C_F_PROCPOINTER. (line 6) * pointer, C address of procedures: C_FUNLOC. (line 6) * pointer, C association status: C_ASSOCIATED. (line 6) * pointer, convert C to Fortran: C_F_POINTER. (line 6) * pointer, cray <1>: MALLOC. (line 6) + * pointer, cray: FREE. (line 6) + * pointer, Cray: Cray pointers. (line 6) * pointer, disassociated: NULL. (line 6) * pointer, status <1>: NULL. (line 6) + * pointer, status: ASSOCIATED. (line 6) * POPCNT: POPCNT. (line 6) * POPPAR: POPPAR. (line 6) * positive difference: DIM. (line 6) *************** Keyword Index *** 20162,20206 **** * Preprocessing: Preprocessing and conditional compilation. (line 6) * preprocessing, assertion: Preprocessing Options. ! (line 113) ! * preprocessing, assertion <1>: Preprocessing Options. ! (line 119) * preprocessing, define macros: Preprocessing Options. ! (line 151) ! * preprocessing, define macros <1>: Preprocessing Options. ! (line 154) * preprocessing, include path: Preprocessing Options. ! (line 69) ! * preprocessing, include path <1>: Preprocessing Options. ! (line 76) ! * preprocessing, include path <2>: Preprocessing Options. ! (line 80) ! * preprocessing, include path <3>: Preprocessing Options. ! (line 85) ! * preprocessing, include path <4>: Preprocessing Options. ! (line 89) ! * preprocessing, include path <5>: Preprocessing Options. ! (line 96) * preprocessing, keep comments: Preprocessing Options. ! (line 122) ! * preprocessing, keep comments <1>: Preprocessing Options. ! (line 137) * preprocessing, no linemarkers: Preprocessing Options. ! (line 179) * preprocessing, undefine macros: Preprocessing Options. ! (line 185) * preprocessor: Preprocessing Options. (line 6) * preprocessor, debugging: Preprocessing Options. (line 26) - * preprocessor, debugging <1>: Preprocessing Options. - (line 35) - * preprocessor, debugging <2>: Preprocessing Options. - (line 41) - * preprocessor, debugging <3>: Preprocessing Options. - (line 44) - * preprocessor, debugging <4>: Preprocessing Options. - (line 51) * preprocessor, disable: Preprocessing Options. (line 12) * preprocessor, enable: Preprocessing Options. --- 20388,20408 ---- * Preprocessing: Preprocessing and conditional compilation. (line 6) * preprocessing, assertion: Preprocessing Options. ! (line 114) * preprocessing, define macros: Preprocessing Options. ! (line 153) * preprocessing, include path: Preprocessing Options. ! (line 70) * preprocessing, keep comments: Preprocessing Options. ! (line 123) * preprocessing, no linemarkers: Preprocessing Options. ! (line 181) * preprocessing, undefine macros: Preprocessing Options. ! (line 187) * preprocessor: Preprocessing Options. (line 6) * preprocessor, debugging: Preprocessing Options. (line 26) * preprocessor, disable: Preprocessing Options. (line 12) * preprocessor, enable: Preprocessing Options. *************** Keyword Index *** 20220,20257 **** * product, vector: DOT_PRODUCT. (line 6) * program termination: EXIT. (line 6) * program termination, with core dump: ABORT. (line 6) ! * PROTECTED statement: Fortran 2003 status. (line 114) * Q exponent-letter: Q exponent-letter. (line 6) * RADIX: RADIX. (line 6) * radix, real: SELECTED_REAL_KIND. (line 6) * RAN: RAN. (line 6) * RAND: RAND. (line 6) ! * random number generation: IRAND. (line 6) ! * random number generation <1>: RAN. (line 6) * random number generation <2>: RAND. (line 6) ! * random number generation <3>: RANDOM_NUMBER. (line 6) ! * random number generation, seeding: RANDOM_SEED. (line 6) * random number generation, seeding <1>: SRAND. (line 6) * RANDOM_NUMBER: RANDOM_NUMBER. (line 6) * RANDOM_SEED: RANDOM_SEED. (line 6) * RANGE: RANGE. (line 6) ! * range checking: Code Gen Options. (line 141) ! * RANK: RANK. (line 6) * rank: RANK. (line 6) * re-association of parenthesized expressions: Code Gen Options. ! (line 346) ! * read character, stream mode: FGET. (line 6) * read character, stream mode <1>: FGETC. (line 6) * REAL: REAL. (line 6) * real kind: SELECTED_REAL_KIND. (line 6) * real number, exponent: EXPONENT. (line 6) * real number, fraction: FRACTION. (line 6) * real number, nearest different: NEAREST. (line 6) - * real number, relative spacing: RRSPACING. (line 6) * real number, relative spacing <1>: SPACING. (line 6) * real number, scale: SCALE. (line 6) * real number, set exponent: SET_EXPONENT. (line 6) ! * Reallocate the LHS in assignments: Code Gen Options. (line 355) * Reallocate the LHS in assignments, notification: Error and Warning Options. (line 220) * REALPART: REAL. (line 6) --- 20422,20459 ---- * product, vector: DOT_PRODUCT. (line 6) * program termination: EXIT. (line 6) * program termination, with core dump: ABORT. (line 6) ! * PROTECTED statement: Fortran 2003 status. (line 116) * Q exponent-letter: Q exponent-letter. (line 6) * RADIX: RADIX. (line 6) * radix, real: SELECTED_REAL_KIND. (line 6) * RAN: RAN. (line 6) * RAND: RAND. (line 6) ! * random number generation <1>: RANDOM_NUMBER. (line 6) * random number generation <2>: RAND. (line 6) ! * random number generation <3>: RAN. (line 6) ! * random number generation: IRAND. (line 6) * random number generation, seeding <1>: SRAND. (line 6) + * random number generation, seeding: RANDOM_SEED. (line 6) * RANDOM_NUMBER: RANDOM_NUMBER. (line 6) * RANDOM_SEED: RANDOM_SEED. (line 6) * RANGE: RANGE. (line 6) ! * range checking: Code Gen Options. (line 143) * rank: RANK. (line 6) + * RANK: RANK. (line 6) * re-association of parenthesized expressions: Code Gen Options. ! (line 350) * read character, stream mode <1>: FGETC. (line 6) + * read character, stream mode: FGET. (line 6) * REAL: REAL. (line 6) * real kind: SELECTED_REAL_KIND. (line 6) * real number, exponent: EXPONENT. (line 6) * real number, fraction: FRACTION. (line 6) * real number, nearest different: NEAREST. (line 6) * real number, relative spacing <1>: SPACING. (line 6) + * real number, relative spacing: RRSPACING. (line 6) * real number, scale: SCALE. (line 6) * real number, set exponent: SET_EXPONENT. (line 6) ! * Reallocate the LHS in assignments: Code Gen Options. (line 359) * Reallocate the LHS in assignments, notification: Error and Warning Options. (line 220) * REALPART: REAL. (line 6) *************** Keyword Index *** 20260,20280 **** * Reduction, XOR: PARITY. (line 6) * remainder: MOD. (line 6) * RENAME: RENAME. (line 6) ! * repacking arrays: Code Gen Options. (line 250) * REPEAT: REPEAT. (line 6) * RESHAPE: RESHAPE. (line 6) * REWIND: Read/Write after EOF marker. (line 6) * right shift, combined: DSHIFTR. (line 6) * root: SQRT. (line 6) - * rounding, ceiling: ANINT. (line 6) * rounding, ceiling <1>: CEILING. (line 6) ! * rounding, floor: AINT. (line 6) * rounding, floor <1>: FLOOR. (line 6) * rounding, nearest whole number: NINT. (line 6) * RRSPACING: RRSPACING. (line 6) * RSHIFT: RSHIFT. (line 6) ! * run-time checking: Code Gen Options. (line 141) * SAME_TYPE_AS: SAME_TYPE_AS. (line 6) * SAVE statement: Code Gen Options. (line 15) * SCALE: SCALE. (line 6) --- 20462,20482 ---- * Reduction, XOR: PARITY. (line 6) * remainder: MOD. (line 6) * RENAME: RENAME. (line 6) ! * repacking arrays: Code Gen Options. (line 251) * REPEAT: REPEAT. (line 6) * RESHAPE: RESHAPE. (line 6) * REWIND: Read/Write after EOF marker. (line 6) * right shift, combined: DSHIFTR. (line 6) * root: SQRT. (line 6) * rounding, ceiling <1>: CEILING. (line 6) ! * rounding, ceiling: ANINT. (line 6) * rounding, floor <1>: FLOOR. (line 6) + * rounding, floor: AINT. (line 6) * rounding, nearest whole number: NINT. (line 6) * RRSPACING: RRSPACING. (line 6) * RSHIFT: RSHIFT. (line 6) ! * run-time checking: Code Gen Options. (line 143) * SAME_TYPE_AS: SAME_TYPE_AS. (line 6) * SAVE statement: Code Gen Options. (line 15) * SCALE: SCALE. (line 6) *************** Keyword Index *** 20283,20299 **** * search paths, for included files: Directory Options. (line 14) * SECNDS: SECNDS. (line 6) * SECOND: SECOND. (line 6) - * seeding a random number generator: RANDOM_SEED. (line 6) * seeding a random number generator <1>: SRAND. (line 6) * SELECTED_CHAR_KIND: SELECTED_CHAR_KIND. (line 6) * SELECTED_INT_KIND: SELECTED_INT_KIND. (line 6) * SELECTED_REAL_KIND: SELECTED_REAL_KIND. (line 6) * SET_EXPONENT: SET_EXPONENT. (line 6) * SHAPE: SHAPE. (line 6) - * shift, left: DSHIFTL. (line 6) * shift, left <1>: SHIFTL. (line 6) ! * shift, right: DSHIFTR. (line 6) * shift, right <1>: SHIFTR. (line 6) * shift, right with fill: SHIFTA. (line 6) * SHIFTA: SHIFTA. (line 6) * SHIFTL: SHIFTL. (line 6) --- 20485,20501 ---- * search paths, for included files: Directory Options. (line 14) * SECNDS: SECNDS. (line 6) * SECOND: SECOND. (line 6) * seeding a random number generator <1>: SRAND. (line 6) + * seeding a random number generator: RANDOM_SEED. (line 6) * SELECTED_CHAR_KIND: SELECTED_CHAR_KIND. (line 6) * SELECTED_INT_KIND: SELECTED_INT_KIND. (line 6) * SELECTED_REAL_KIND: SELECTED_REAL_KIND. (line 6) * SET_EXPONENT: SET_EXPONENT. (line 6) * SHAPE: SHAPE. (line 6) * shift, left <1>: SHIFTL. (line 6) ! * shift, left: DSHIFTL. (line 6) * shift, right <1>: SHIFTR. (line 6) + * shift, right: DSHIFTR. (line 6) * shift, right with fill: SHIFTA. (line 6) * SHIFTA: SHIFTA. (line 6) * SHIFTL: SHIFTL. (line 6) *************** Keyword Index *** 20310,20317 **** * SINH: SINH. (line 6) * SIZE: SIZE. (line 6) * size of a variable, in bits: BIT_SIZE. (line 6) - * size of an expression: C_SIZEOF. (line 6) * size of an expression <1>: SIZEOF. (line 6) * SIZEOF: SIZEOF. (line 6) * SLEEP: SLEEP. (line 6) * SNGL: REAL. (line 6) --- 20512,20519 ---- * SINH: SINH. (line 6) * SIZE: SIZE. (line 6) * size of a variable, in bits: BIT_SIZE. (line 6) * size of an expression <1>: SIZEOF. (line 6) + * size of an expression: C_SIZEOF. (line 6) * SIZEOF: SIZEOF. (line 6) * SLEEP: SLEEP. (line 6) * SNGL: REAL. (line 6) *************** Keyword Index *** 20325,20350 **** * statement, ENUM: Fortran 2003 status. (line 93) * statement, ENUMERATOR: Fortran 2003 status. (line 93) * statement, FLUSH: Fortran 2003 status. (line 89) ! * statement, IMPORT: Fortran 2003 status. (line 120) ! * statement, ISO_FORTRAN_ENV: Fortran 2003 status. (line 128) ! * statement, PROTECTED: Fortran 2003 status. (line 114) * statement, SAVE: Code Gen Options. (line 15) ! * statement, USE, INTRINSIC: Fortran 2003 status. (line 128) ! * statement, VALUE: Fortran 2003 status. (line 116) ! * statement, VOLATILE: Fortran 2003 status. (line 118) * storage size: STORAGE_SIZE. (line 6) * STORAGE_SIZE: STORAGE_SIZE. (line 6) ! * STREAM I/O: Fortran 2003 status. (line 103) ! * stream mode, read character: FGET. (line 6) * stream mode, read character <1>: FGETC. (line 6) ! * stream mode, write character: FPUT. (line 6) * stream mode, write character <1>: FPUTC. (line 6) * string, adjust left: ADJUSTL. (line 6) * string, adjust right: ADJUSTR. (line 6) ! * string, comparison: LGE. (line 6) ! * string, comparison <1>: LGT. (line 6) * string, comparison <2>: LLE. (line 6) ! * string, comparison <3>: LLT. (line 6) * string, concatenate: REPEAT. (line 6) * string, find missing set: VERIFY. (line 6) * string, find non-blank character: LNBLNK. (line 6) --- 20527,20552 ---- * statement, ENUM: Fortran 2003 status. (line 93) * statement, ENUMERATOR: Fortran 2003 status. (line 93) * statement, FLUSH: Fortran 2003 status. (line 89) ! * statement, IMPORT: Fortran 2003 status. (line 122) ! * statement, ISO_FORTRAN_ENV: Fortran 2003 status. (line 130) ! * statement, PROTECTED: Fortran 2003 status. (line 116) * statement, SAVE: Code Gen Options. (line 15) ! * statement, USE, INTRINSIC: Fortran 2003 status. (line 130) ! * statement, VALUE: Fortran 2003 status. (line 118) ! * statement, VOLATILE: Fortran 2003 status. (line 120) * storage size: STORAGE_SIZE. (line 6) * STORAGE_SIZE: STORAGE_SIZE. (line 6) ! * STREAM I/O: Fortran 2003 status. (line 105) * stream mode, read character <1>: FGETC. (line 6) ! * stream mode, read character: FGET. (line 6) * stream mode, write character <1>: FPUTC. (line 6) + * stream mode, write character: FPUT. (line 6) * string, adjust left: ADJUSTL. (line 6) * string, adjust right: ADJUSTR. (line 6) ! * string, comparison <1>: LLT. (line 6) * string, comparison <2>: LLE. (line 6) ! * string, comparison <3>: LGT. (line 6) ! * string, comparison: LGE. (line 6) * string, concatenate: REPEAT. (line 6) * string, find missing set: VERIFY. (line 6) * string, find non-blank character: LNBLNK. (line 6) *************** Keyword Index *** 20358,20365 **** (line 6) * STRUCTURE: STRUCTURE and RECORD. (line 6) ! * structure packing: Code Gen Options. (line 244) ! * subscript checking: Code Gen Options. (line 141) * substring position: INDEX intrinsic. (line 6) * SUM: SUM. (line 6) * sum array elements: SUM. (line 6) --- 20560,20567 ---- (line 6) * STRUCTURE: STRUCTURE and RECORD. (line 6) ! * structure packing: Code Gen Options. (line 245) ! * subscript checking: Code Gen Options. (line 143) * substring position: INDEX intrinsic. (line 6) * SUM: SUM. (line 6) * sum array elements: SUM. (line 6) *************** Keyword Index *** 20368,20396 **** * symbol names: Fortran Dialect Options. (line 50) * symbol names, transforming: Code Gen Options. (line 54) - * symbol names, transforming <1>: Code Gen Options. (line 110) * symbol names, underscores: Code Gen Options. (line 54) - * symbol names, underscores <1>: Code Gen Options. (line 110) * SYMLNK: SYMLNK. (line 6) * syntax checking: Error and Warning Options. (line 33) * SYSTEM: SYSTEM. (line 6) * system, error handling: GERROR. (line 6) - * system, error handling <1>: IERRNO. (line 6) - * system, error handling <2>: PERROR. (line 6) * system, group ID: GETGID. (line 6) * system, host name: HOSTNM. (line 6) * system, login name: GETLOG. (line 6) * system, process ID: GETPID. (line 6) * system, signal handling: SIGNAL. (line 6) * system, system call: EXECUTE_COMMAND_LINE. (line 6) - * system, system call <1>: SYSTEM. (line 6) - * system, terminal: ISATTY. (line 6) * system, terminal <1>: TTYNAM. (line 6) * system, user ID: GETUID. (line 6) - * system, working directory: CHDIR. (line 6) * system, working directory <1>: GETCWD. (line 6) * SYSTEM_CLOCK: SYSTEM_CLOCK. (line 6) * tabulators: Error and Warning Options. (line 175) --- 20570,20596 ---- * symbol names: Fortran Dialect Options. (line 50) * symbol names, transforming: Code Gen Options. (line 54) * symbol names, underscores: Code Gen Options. (line 54) * SYMLNK: SYMLNK. (line 6) * syntax checking: Error and Warning Options. (line 33) * SYSTEM: SYSTEM. (line 6) + * system, error handling <1>: PERROR. (line 6) + * system, error handling <2>: IERRNO. (line 6) * system, error handling: GERROR. (line 6) * system, group ID: GETGID. (line 6) * system, host name: HOSTNM. (line 6) * system, login name: GETLOG. (line 6) * system, process ID: GETPID. (line 6) * system, signal handling: SIGNAL. (line 6) + * system, system call <1>: SYSTEM. (line 6) * system, system call: EXECUTE_COMMAND_LINE. (line 6) * system, terminal <1>: TTYNAM. (line 6) + * system, terminal: ISATTY. (line 6) * system, user ID: GETUID. (line 6) * system, working directory <1>: GETCWD. (line 6) + * system, working directory: CHDIR. (line 6) * SYSTEM_CLOCK: SYSTEM_CLOCK. (line 6) * tabulators: Error and Warning Options. (line 175) *************** Keyword Index *** 20398,20405 **** * tangent: TAN. (line 6) * tangent, hyperbolic: TANH. (line 6) * tangent, hyperbolic, inverse: ATANH. (line 6) - * tangent, inverse: ATAN. (line 6) * tangent, inverse <1>: ATAN2. (line 6) * TANH: TANH. (line 6) * terminate program: EXIT. (line 6) * terminate program, with core dump: ABORT. (line 6) --- 20598,20605 ---- * tangent: TAN. (line 6) * tangent, hyperbolic: TANH. (line 6) * tangent, hyperbolic, inverse: ATANH. (line 6) * tangent, inverse <1>: ATAN2. (line 6) + * tangent, inverse: ATAN. (line 6) * TANH: TANH. (line 6) * terminate program: EXIT. (line 6) * terminate program, with core dump: ABORT. (line 6) *************** Keyword Index *** 20407,20445 **** * thread-safety, threads: Thread-safety of the runtime library. (line 6) * TIME: TIME. (line 6) * time, clock ticks: MCLOCK. (line 6) - * time, clock ticks <1>: MCLOCK8. (line 6) - * time, clock ticks <2>: SYSTEM_CLOCK. (line 6) * time, conversion to GMT info: GMTIME. (line 6) * time, conversion to local time info: LTIME. (line 6) * time, conversion to string: CTIME. (line 6) * time, current: DATE_AND_TIME. (line 6) ! * time, current <1>: FDATE. (line 6) ! * time, current <2>: ITIME. (line 6) ! * time, current <3>: TIME. (line 6) ! * time, current <4>: TIME8. (line 6) * time, elapsed: CPU_TIME. (line 6) - * time, elapsed <1>: DTIME. (line 6) - * time, elapsed <2>: ETIME. (line 6) - * time, elapsed <3>: SECNDS. (line 6) - * time, elapsed <4>: SECOND. (line 6) * TIME8: TIME8. (line 6) * TINY: TINY. (line 6) * TR 15581: Fortran 2003 status. (line 98) ! * trace: Debugging Options. (line 61) * TRAILZ: TRAILZ. (line 6) * TRANSFER: TRANSFER. (line 6) * transforming symbol names: Code Gen Options. (line 54) - * transforming symbol names <1>: Code Gen Options. (line 110) - * TRANSPOSE: TRANSPOSE. (line 6) * transpose: TRANSPOSE. (line 6) * trigonometric function, cosine: COS. (line 6) * trigonometric function, cosine, inverse: ACOS. (line 6) * trigonometric function, sine: SIN. (line 6) * trigonometric function, sine, inverse: ASIN. (line 6) * trigonometric function, tangent: TAN. (line 6) - * trigonometric function, tangent, inverse: ATAN. (line 6) * trigonometric function, tangent, inverse <1>: ATAN2. (line 6) * TRIM: TRIM. (line 6) * TTYNAM: TTYNAM. (line 6) * type cast: TRANSFER. (line 6) --- 20607,20644 ---- * thread-safety, threads: Thread-safety of the runtime library. (line 6) * TIME: TIME. (line 6) + * time, clock ticks <1>: SYSTEM_CLOCK. (line 6) + * time, clock ticks <2>: MCLOCK8. (line 6) * time, clock ticks: MCLOCK. (line 6) * time, conversion to GMT info: GMTIME. (line 6) * time, conversion to local time info: LTIME. (line 6) * time, conversion to string: CTIME. (line 6) + * time, current <1>: TIME8. (line 6) + * time, current <2>: TIME. (line 6) + * time, current <3>: ITIME. (line 6) + * time, current <4>: FDATE. (line 6) * time, current: DATE_AND_TIME. (line 6) ! * time, elapsed <1>: SECOND. (line 6) ! * time, elapsed <2>: SECNDS. (line 6) ! * time, elapsed <3>: ETIME. (line 6) ! * time, elapsed <4>: DTIME. (line 6) * time, elapsed: CPU_TIME. (line 6) * TIME8: TIME8. (line 6) * TINY: TINY. (line 6) * TR 15581: Fortran 2003 status. (line 98) ! * trace: Debugging Options. (line 62) * TRAILZ: TRAILZ. (line 6) * TRANSFER: TRANSFER. (line 6) * transforming symbol names: Code Gen Options. (line 54) * transpose: TRANSPOSE. (line 6) + * TRANSPOSE: TRANSPOSE. (line 6) * trigonometric function, cosine: COS. (line 6) * trigonometric function, cosine, inverse: ACOS. (line 6) * trigonometric function, sine: SIN. (line 6) * trigonometric function, sine, inverse: ASIN. (line 6) * trigonometric function, tangent: TAN. (line 6) * trigonometric function, tangent, inverse <1>: ATAN2. (line 6) + * trigonometric function, tangent, inverse: ATAN. (line 6) * TRIM: TRIM. (line 6) * TTYNAM: TTYNAM. (line 6) * type cast: TRANSFER. (line 6) *************** Keyword Index *** 20449,20455 **** * underflow: Error and Warning Options. (line 183) * underscore: Code Gen Options. (line 54) - * underscore <1>: Code Gen Options. (line 110) * UNION: UNION and MAP. (line 6) * UNLINK: UNLINK. (line 6) * UNPACK: UNPACK. (line 6) --- 20648,20653 ---- *************** Keyword Index *** 20457,20465 **** (line 199) * unused parameter: Error and Warning Options. (line 203) ! * USE, INTRINSIC statement: Fortran 2003 status. (line 128) * user id: GETUID. (line 6) ! * VALUE statement: Fortran 2003 status. (line 116) * Varying length character strings: Varying Length Character Strings. (line 6) * Varying length strings: Varying Length Character Strings. --- 20655,20663 ---- (line 199) * unused parameter: Error and Warning Options. (line 203) ! * USE, INTRINSIC statement: Fortran 2003 status. (line 130) * user id: GETUID. (line 6) ! * VALUE statement: Fortran 2003 status. (line 118) * Varying length character strings: Varying Length Character Strings. (line 6) * Varying length strings: Varying Length Character Strings. *************** Keyword Index *** 20469,20475 **** * version of the compiler: COMPILER_VERSION. (line 6) * VOLATILE: Volatile COMMON blocks. (line 6) ! * VOLATILE statement: Fortran 2003 status. (line 118) * warning, C binding type: Error and Warning Options. (line 99) * warnings, aliasing: Error and Warning Options. --- 20667,20673 ---- * version of the compiler: COMPILER_VERSION. (line 6) * VOLATILE: Volatile COMMON blocks. (line 6) ! * VOLATILE statement: Fortran 2003 status. (line 120) * warning, C binding type: Error and Warning Options. (line 99) * warnings, aliasing: Error and Warning Options. *************** Keyword Index *** 20486,20493 **** (line 106) * warnings, conversion: Error and Warning Options. (line 115) - * warnings, conversion <1>: Error and Warning Options. - (line 119) * warnings, division of integers: Error and Warning Options. (line 138) * warnings, extra: Error and Warning Options. --- 20684,20689 ---- *************** Keyword Index *** 20517,20523 **** * warnings, tabs: Error and Warning Options. (line 175) * warnings, to errors: Error and Warning Options. ! (line 249) * warnings, underflow: Error and Warning Options. (line 183) * warnings, unused dummy argument: Error and Warning Options. --- 20713,20719 ---- * warnings, tabs: Error and Warning Options. (line 175) * warnings, to errors: Error and Warning Options. ! (line 250) * warnings, underflow: Error and Warning Options. (line 183) * warnings, unused dummy argument: Error and Warning Options. *************** Keyword Index *** 20526,20539 **** (line 203) * warnings, use statements: Error and Warning Options. (line 195) - * write character, stream mode: FPUT. (line 6) * write character, stream mode <1>: FPUTC. (line 6) * XOR: XOR. (line 6) * XOR reduction: PARITY. (line 6) * ZABS: ABS. (line 6) * ZCOS: COS. (line 6) - * zero bits: LEADZ. (line 6) * zero bits <1>: TRAILZ. (line 6) * ZEXP: EXP. (line 6) * ZLOG: LOG. (line 6) * ZSIN: SIN. (line 6) --- 20722,20735 ---- (line 203) * warnings, use statements: Error and Warning Options. (line 195) * write character, stream mode <1>: FPUTC. (line 6) + * write character, stream mode: FPUT. (line 6) * XOR: XOR. (line 6) * XOR reduction: PARITY. (line 6) * ZABS: ABS. (line 6) * ZCOS: COS. (line 6) * zero bits <1>: TRAILZ. (line 6) + * zero bits: LEADZ. (line 6) * ZEXP: EXP. (line 6) * ZLOG: LOG. (line 6) * ZSIN: SIN. (line 6) *************** Keyword Index *** 20542,20960 ****  Tag Table: ! Node: Top1950 ! Node: Introduction3361 ! Node: About GNU Fortran4110 ! Node: GNU Fortran and GCC8099 ! Node: Preprocessing and conditional compilation10213 ! Node: GNU Fortran and G7711858 ! Node: Project Status12431 ! Node: Standards15159 ! Node: Varying Length Character Strings16473 ! Node: Invoking GNU Fortran17225 ! Node: Option Summary18948 ! Node: Fortran Dialect Options22452 ! Node: Preprocessing Options32410 ! Node: Error and Warning Options40651 ! Node: Debugging Options51353 ! Node: Directory Options54821 ! Node: Link Options56256 ! Node: Runtime Options56882 ! Node: Code Gen Options58789 ! Node: Environment Variables76101 ! Node: Runtime76706 ! Node: TMPDIR77806 ! Node: GFORTRAN_STDIN_UNIT78476 ! Node: GFORTRAN_STDOUT_UNIT78858 ! Node: GFORTRAN_STDERR_UNIT79259 ! Node: GFORTRAN_UNBUFFERED_ALL79661 ! Node: GFORTRAN_UNBUFFERED_PRECONNECTED80192 ! Node: GFORTRAN_SHOW_LOCUS80836 ! Node: GFORTRAN_OPTIONAL_PLUS81332 ! Node: GFORTRAN_DEFAULT_RECL81808 ! Node: GFORTRAN_LIST_SEPARATOR82296 ! Node: GFORTRAN_CONVERT_UNIT82905 ! Node: GFORTRAN_ERROR_BACKTRACE85760 ! Node: Fortran 2003 and 2008 status86317 ! Node: Fortran 2003 status86597 ! Node: Fortran 2008 status91840 ! Node: TS 29113 status97218 ! Node: TS 18508 status98220 ! Node: Compiler Characteristics98920 ! Node: KIND Type Parameters99549 ! Node: Internal representation of LOGICAL variables100977 ! Node: Thread-safety of the runtime library101837 ! Node: Data consistency and durability104240 ! Node: Files opened without an explicit ACTION= specifier107353 ! Node: File operations on symbolic links108044 ! Node: Extensions109114 ! Node: Extensions implemented in GNU Fortran109719 ! Node: Old-style kind specifications111161 ! Node: Old-style variable initialization112263 ! Node: Extensions to namelist113575 ! Node: X format descriptor without count field115878 ! Node: Commas in FORMAT specifications116405 ! Node: Missing period in FORMAT specifications116922 ! Node: I/O item lists117484 ! Node: Q exponent-letter117869 ! Node: BOZ literal constants118467 ! Node: Real array indices121046 ! Node: Unary operators121345 ! Node: Implicitly convert LOGICAL and INTEGER values121759 ! Node: Hollerith constants support122718 ! Node: Cray pointers124490 ! Node: CONVERT specifier129937 ! Node: OpenMP131932 ! Node: OpenACC134190 ! Node: Argument list functions135499 ! Node: Read/Write after EOF marker137142 ! Node: STRUCTURE and RECORD137745 ! Node: UNION and MAP142242 ! Node: Extensions not implemented in GNU Fortran145165 ! Node: ENCODE and DECODE statements146110 ! Node: Variable FORMAT expressions147441 ! Node: Alternate complex function syntax148546 ! Node: Volatile COMMON blocks149096 ! Node: OPEN( ... NAME=)149598 ! Node: Mixed-Language Programming150000 ! Node: Interoperability with C150580 ! Node: Intrinsic Types151914 ! Node: Derived Types and struct152910 ! Node: Interoperable Global Variables154268 ! Node: Interoperable Subroutines and Functions155543 ! Node: Working with Pointers159337 ! Node: Further Interoperability of Fortran with C163813 ! Node: GNU Fortran Compiler Directives167167 ! Node: Non-Fortran Main Program170419 ! Node: _gfortran_set_args172607 ! Node: _gfortran_set_options173545 ! Node: _gfortran_set_convert176945 ! Node: _gfortran_set_record_marker177813 ! Node: _gfortran_set_fpe178623 ! Node: _gfortran_set_max_subrecord_length179821 ! Node: Naming and argument-passing conventions180744 ! Node: Naming conventions181463 ! Node: Argument passing conventions182935 ! Node: Coarray Programming187429 ! Node: Type and enum ABI Documentation187676 ! Node: caf_token_t187918 ! Node: caf_register_t188154 ! Node: Function ABI Documentation188608 ! Node: _gfortran_caf_init190351 ! Node: _gfortran_caf_finish191776 ! Node: _gfortran_caf_this_image192715 ! Node: _gfortran_caf_num_images193469 ! Node: _gfortran_caf_register194575 ! Node: _gfortran_caf_deregister197780 ! Node: _gfortran_caf_send198849 ! Node: _gfortran_caf_get201654 ! Node: _gfortran_caf_sendget204333 ! Node: _gfortran_caf_lock207761 ! Node: _gfortran_caf_unlock209494 ! Node: _gfortran_caf_event_post210939 ! Node: _gfortran_caf_event_wait212350 ! Node: _gfortran_caf_event_query214409 ! Node: _gfortran_caf_sync_all215713 ! Node: _gfortran_caf_sync_images216627 ! Node: _gfortran_caf_sync_memory218139 ! Node: _gfortran_caf_error_stop219117 ! Node: _gfortran_caf_error_stop_str219714 ! Node: _gfortran_caf_atomic_define220384 ! Node: _gfortran_caf_atomic_ref221660 ! Node: _gfortran_caf_atomic_cas222955 ! Node: _gfortran_caf_atomic_op224672 ! Node: _gfortran_caf_co_broadcast226727 ! Node: _gfortran_caf_co_max227802 ! Node: _gfortran_caf_co_min229364 ! Node: _gfortran_caf_co_sum230920 ! Node: _gfortran_caf_co_reduce232387 ! Node: Intrinsic Procedures234888 ! Node: Introduction to Intrinsics251441 ! Node: ABORT253791 ! Node: ABS254536 ! Node: ACCESS256138 ! Node: ACHAR258068 ! Node: ACOS259272 ! Node: ACOSH260526 ! Node: ADJUSTL261521 ! Node: ADJUSTR262463 ! Node: AIMAG263411 ! Node: AINT264783 ! Node: ALARM266389 ! Node: ALL268021 ! Node: ALLOCATED269945 ! Node: AND271084 ! Node: ANINT272383 ! Node: ANY273880 ! Node: ASIN275806 ! Node: ASINH277049 ! Node: ASSOCIATED278054 ! Node: ATAN281065 ! Node: ATAN2282483 ! Node: ATANH284273 ! Node: ATOMIC_ADD285278 ! Node: ATOMIC_AND286810 ! Node: ATOMIC_CAS288398 ! Node: ATOMIC_DEFINE290257 ! Node: ATOMIC_FETCH_ADD291976 ! Node: ATOMIC_FETCH_AND293776 ! Node: ATOMIC_FETCH_OR295566 ! Node: ATOMIC_FETCH_XOR297343 ! Node: ATOMIC_OR299126 ! Node: ATOMIC_REF300711 ! Node: ATOMIC_XOR302607 ! Node: BACKTRACE304192 ! Node: BESSEL_J0304772 ! Node: BESSEL_J1305788 ! Node: BESSEL_JN306805 ! Node: BESSEL_Y0308630 ! Node: BESSEL_Y1309585 ! Node: BESSEL_YN310540 ! Node: BGE312371 ! Node: BGT313063 ! Node: BIT_SIZE313713 ! Node: BLE314535 ! Node: BLT315217 ! Node: BTEST315855 ! Node: C_ASSOCIATED316740 ! Node: C_F_POINTER317951 ! Node: C_F_PROCPOINTER319386 ! Node: C_FUNLOC320893 ! Node: C_LOC322264 ! Node: C_SIZEOF323543 ! Node: CEILING324956 ! Node: CHAR325964 ! Node: CHDIR327176 ! Node: CHMOD328350 ! Node: CMPLX330265 ! Node: CO_BROADCAST331708 ! Node: CO_MAX333481 ! Node: CO_MIN335361 ! Node: CO_REDUCE337227 ! Node: CO_SUM340730 ! Node: COMMAND_ARGUMENT_COUNT342637 ! Node: COMPILER_OPTIONS343554 ! Node: COMPILER_VERSION344580 ! Node: COMPLEX345544 ! Node: CONJG346683 ! Node: COS347739 ! Node: COSH349163 ! Node: COUNT350345 ! Node: CPU_TIME352368 ! Node: CSHIFT353725 ! Node: CTIME355385 ! Node: DATE_AND_TIME356887 ! Node: DBLE359367 ! Node: DCMPLX360162 ! Node: DIGITS361344 ! Node: DIM362311 ! Node: DOT_PRODUCT363592 ! Node: DPROD365235 ! Node: DREAL366162 ! Node: DSHIFTL366828 ! Node: DSHIFTR368161 ! Node: DTIME369495 ! Node: EOSHIFT372310 ! Node: EPSILON374383 ! Node: ERF375110 ! Node: ERFC375891 ! Node: ERFC_SCALED376701 ! Node: ETIME377394 ! Node: EVENT_QUERY379633 ! Node: EXECUTE_COMMAND_LINE381222 ! Node: EXIT383815 ! Node: EXP384691 ! Node: EXPONENT385942 ! Node: EXTENDS_TYPE_OF386704 ! Node: FDATE387560 ! Node: FGET389033 ! Node: FGETC390858 ! Node: FLOOR392666 ! Node: FLUSH393655 ! Node: FNUM395534 ! Node: FPUT396259 ! Node: FPUTC397893 ! Node: FRACTION399674 ! Node: FREE400578 ! Node: FSEEK401421 ! Node: FSTAT403727 ! Node: FTELL404814 ! Node: GAMMA405796 ! Node: GERROR406850 ! Node: GETARG407572 ! Node: GET_COMMAND409345 ! Node: GET_COMMAND_ARGUMENT410719 ! Node: GETCWD412767 ! Node: GETENV413747 ! Node: GET_ENVIRONMENT_VARIABLE415179 ! Node: GETGID417342 ! Node: GETLOG417879 ! Node: GETPID418741 ! Node: GETUID419471 ! Node: GMTIME419987 ! Node: HOSTNM421471 ! Node: HUGE422392 ! Node: HYPOT423114 ! Node: IACHAR423940 ! Node: IALL425108 ! Node: IAND426593 ! Node: IANY427580 ! Node: IARGC429074 ! Node: IBCLR430095 ! Node: IBITS430757 ! Node: IBSET431675 ! Node: ICHAR432332 ! Node: IDATE434502 ! Node: IEOR435532 ! Node: IERRNO436412 ! Node: IMAGE_INDEX436961 ! Node: INDEX intrinsic437989 ! Node: INT439515 ! Node: INT2441274 ! Node: INT8442042 ! Node: IOR442757 ! Node: IPARITY443613 ! Node: IRAND445145 ! Node: IS_IOSTAT_END446504 ! Node: IS_IOSTAT_EOR447603 ! Node: ISATTY448732 ! Node: ISHFT449515 ! Node: ISHFTC450498 ! Node: ISNAN451719 ! Node: ITIME452486 ! Node: KILL453514 ! Node: KIND454423 ! Node: LBOUND455269 ! Node: LCOBOUND456607 ! Node: LEADZ457742 ! Node: LEN458603 ! Node: LEN_TRIM459899 ! Node: LGE460887 ! Node: LGT462400 ! Node: LINK463878 ! Node: LLE464917 ! Node: LLT466417 ! Node: LNBLNK467888 ! Node: LOC468666 ! Node: LOG469398 ! Node: LOG10470743 ! Node: LOG_GAMMA471733 ! Node: LOGICAL472835 ! Node: LONG473647 ! Node: LSHIFT474405 ! Node: LSTAT475491 ! Node: LTIME476691 ! Node: MALLOC478097 ! Node: MASKL479559 ! Node: MASKR480326 ! Node: MATMUL481096 ! Node: MAX482194 ! Node: MAXEXPONENT483729 ! Node: MAXLOC484546 ! Node: MAXVAL486571 ! Node: MCLOCK488211 ! Node: MCLOCK8489234 ! Node: MERGE490464 ! Node: MERGE_BITS491216 ! Node: MIN492081 ! Node: MINEXPONENT493619 ! Node: MINLOC494250 ! Node: MINVAL496275 ! Node: MOD497928 ! Node: MODULO499697 ! Node: MOVE_ALLOC501000 ! Node: MVBITS502033 ! Node: NEAREST503099 ! Node: NEW_LINE504199 ! Node: NINT504972 ! Node: NORM2506393 ! Node: NOT507535 ! Node: NULL508119 ! Node: NUM_IMAGES509027 ! Node: OR510728 ! Node: PACK512014 ! Node: PARITY514022 ! Node: PERROR515243 ! Node: POPCNT515868 ! Node: POPPAR516740 ! Node: PRECISION517794 ! Node: PRESENT518681 ! Node: PRODUCT519793 ! Node: RADIX521327 ! Node: RAN522139 ! Node: RAND522595 ! Node: RANDOM_NUMBER523930 ! Node: RANDOM_SEED525659 ! Node: RANGE529490 ! Node: RANK530171 ! Node: REAL530952 ! Node: RENAME532749 ! Node: REPEAT533771 ! Node: RESHAPE534499 ! Node: RRSPACING535966 ! Node: RSHIFT536659 ! Node: SAME_TYPE_AS537799 ! Node: SCALE538631 ! Node: SCAN539412 ! Node: SECNDS540970 ! Node: SECOND542062 ! Node: SELECTED_CHAR_KIND542938 ! Node: SELECTED_INT_KIND544533 ! Node: SELECTED_REAL_KIND545710 ! Node: SET_EXPONENT548387 ! Node: SHAPE549384 ! Node: SHIFTA550808 ! Node: SHIFTL551772 ! Node: SHIFTR552609 ! Node: SIGN553447 ! Node: SIGNAL554673 ! Node: SIN556179 ! Node: SINH557221 ! Node: SIZE558233 ! Node: SIZEOF559552 ! Node: SLEEP561207 ! Node: SPACING561768 ! Node: SPREAD562782 ! Node: SQRT563933 ! Node: SRAND565265 ! Node: STAT566499 ! Node: STORAGE_SIZE569667 ! Node: SUM570546 ! Node: SYMLNK572038 ! Node: SYSTEM573173 ! Node: SYSTEM_CLOCK574428 ! Node: TAN577258 ! Node: TANH578246 ! Node: THIS_IMAGE579420 ! Node: TIME581720 ! Node: TIME8582845 ! Node: TINY583998 ! Node: TRAILZ584599 ! Node: TRANSFER585417 ! Node: TRANSPOSE587453 ! Node: TRIM588143 ! Node: TTYNAM589001 ! Node: UBOUND589919 ! Node: UCOBOUND591309 ! Node: UMASK592446 ! Node: UNLINK593128 ! Node: UNPACK594108 ! Node: VERIFY595403 ! Node: XOR597132 ! Node: Intrinsic Modules598505 ! Node: ISO_FORTRAN_ENV598794 ! Node: ISO_C_BINDING603197 ! Node: IEEE modules606903 ! Node: OpenMP Modules OMP_LIB and OMP_LIB_KINDS608046 ! Node: OpenACC Module OPENACC609581 ! Node: Contributing610508 ! Node: Contributors611362 ! Node: Projects612993 ! Node: Proposed Extensions613800 ! Node: Copying615810 ! Node: GNU Free Documentation License653356 ! Node: Funding678480 ! Node: Option Index681006 ! Node: Keyword Index696910  End Tag Table --- 20738,21156 ----  Tag Table: ! Node: Top2004 ! Node: Introduction3415 ! Node: About GNU Fortran4164 ! Node: GNU Fortran and GCC8153 ! Node: Preprocessing and conditional compilation10267 ! Node: GNU Fortran and G7711911 ! Node: Project Status12484 ! Node: Standards15214 ! Node: Varying Length Character Strings16532 ! Node: Invoking GNU Fortran17283 ! Node: Option Summary19006 ! Node: Fortran Dialect Options22505 ! Node: Preprocessing Options32465 ! Node: Error and Warning Options40696 ! Node: Debugging Options51389 ! Node: Directory Options54861 ! Node: Link Options56296 ! Node: Runtime Options56920 ! Node: Code Gen Options58825 ! Node: Environment Variables76128 ! Node: Runtime76733 ! Node: TMPDIR77835 ! Node: GFORTRAN_STDIN_UNIT78504 ! Node: GFORTRAN_STDOUT_UNIT78886 ! Node: GFORTRAN_STDERR_UNIT79287 ! Node: GFORTRAN_UNBUFFERED_ALL79689 ! Node: GFORTRAN_UNBUFFERED_PRECONNECTED80220 ! Node: GFORTRAN_SHOW_LOCUS80864 ! Node: GFORTRAN_OPTIONAL_PLUS81360 ! Node: GFORTRAN_DEFAULT_RECL81836 ! Node: GFORTRAN_LIST_SEPARATOR82325 ! Node: GFORTRAN_CONVERT_UNIT82934 ! Node: GFORTRAN_ERROR_BACKTRACE85797 ! Node: Fortran 2003 and 2008 status86354 ! Node: Fortran 2003 status86634 ! Node: Fortran 2008 status91875 ! Node: TS 29113 status97249 ! Node: TS 18508 status98250 ! Node: Compiler Characteristics98950 ! Node: KIND Type Parameters99579 ! Node: Internal representation of LOGICAL variables101008 ! Node: Thread-safety of the runtime library101868 ! Node: Data consistency and durability104272 ! Node: Files opened without an explicit ACTION= specifier107373 ! Node: File operations on symbolic links108067 ! Node: Extensions109136 ! Node: Extensions implemented in GNU Fortran109741 ! Node: Old-style kind specifications111186 ! Node: Old-style variable initialization112293 ! Node: Extensions to namelist113605 ! Node: X format descriptor without count field115907 ! Node: Commas in FORMAT specifications116434 ! Node: Missing period in FORMAT specifications116951 ! Node: I/O item lists117513 ! Node: `Q' exponent-letter117900 ! Node: BOZ literal constants118500 ! Node: Real array indices121079 ! Node: Unary operators121378 ! Node: Implicitly convert LOGICAL and INTEGER values121792 ! Node: Hollerith constants support122752 ! Node: Cray pointers124524 ! Node: CONVERT specifier129971 ! Node: OpenMP131969 ! Node: OpenACC134227 ! Node: Argument list functions135537 ! Node: Read/Write after EOF marker137181 ! Node: STRUCTURE and RECORD137783 ! Node: UNION and MAP142274 ! Node: Extensions not implemented in GNU Fortran145195 ! Node: ENCODE and DECODE statements146140 ! Node: Variable FORMAT expressions147471 ! Node: Alternate complex function syntax148576 ! Node: Volatile COMMON blocks149127 ! Node: OPEN( ... NAME=)149628 ! Node: Mixed-Language Programming150029 ! Node: Interoperability with C150612 ! Node: Intrinsic Types151950 ! Node: Derived Types and struct152946 ! Node: Interoperable Global Variables154303 ! Node: Interoperable Subroutines and Functions155579 ! Node: Working with Pointers159375 ! Node: Further Interoperability of Fortran with C163851 ! Node: GNU Fortran Compiler Directives167200 ! Node: Non-Fortran Main Program170454 ! Node: _gfortran_set_args172644 ! Node: _gfortran_set_options173579 ! Node: _gfortran_set_convert176946 ! Node: _gfortran_set_record_marker177810 ! Node: _gfortran_set_fpe178618 ! Node: _gfortran_set_max_subrecord_length179810 ! Node: Naming and argument-passing conventions180730 ! Node: Naming conventions181449 ! Node: Argument passing conventions182919 ! Node: Coarray Programming187415 ! Node: Type and enum ABI Documentation187662 ! Node: caf_token_t187904 ! Node: caf_register_t188139 ! Node: Function ABI Documentation188593 ! Node: _gfortran_caf_init190336 ! Node: _gfortran_caf_finish191773 ! Node: _gfortran_caf_this_image192712 ! Node: _gfortran_caf_num_images193463 ! Node: _gfortran_caf_register194564 ! Node: _gfortran_caf_deregister197748 ! Node: _gfortran_caf_send198813 ! Node: _gfortran_caf_get201607 ! Node: _gfortran_caf_sendget204276 ! Node: _gfortran_caf_lock207692 ! Node: _gfortran_caf_unlock209411 ! Node: _gfortran_caf_event_post210844 ! Node: _gfortran_caf_event_wait212243 ! Node: _gfortran_caf_event_query214290 ! Node: _gfortran_caf_sync_all215582 ! Node: _gfortran_caf_sync_images216496 ! Node: _gfortran_caf_sync_memory217993 ! Node: _gfortran_caf_error_stop218965 ! Node: _gfortran_caf_error_stop_str219561 ! Node: _gfortran_caf_atomic_define220229 ! Node: _gfortran_caf_atomic_ref221489 ! Node: _gfortran_caf_atomic_cas222769 ! Node: _gfortran_caf_atomic_op224465 ! Node: _gfortran_caf_co_broadcast226496 ! Node: _gfortran_caf_co_max227561 ! Node: _gfortran_caf_co_min229111 ! Node: _gfortran_caf_co_sum230655 ! Node: _gfortran_caf_co_reduce232111 ! Node: Intrinsic Procedures234602 ! Node: Introduction to Intrinsics251155 ! Node: ABORT253507 ! Node: ABS254253 ! Node: ACCESS255870 ! Node: ACHAR257791 ! Node: ACOS258992 ! Node: ACOSH260229 ! Node: ADJUSTL261217 ! Node: ADJUSTR262158 ! Node: AIMAG263105 ! Node: AINT264486 ! Node: ALARM266073 ! Node: ALL267707 ! Node: ALLOCATED269625 ! Node: AND270762 ! Node: ANINT272059 ! Node: ANY273537 ! Node: ASIN275467 ! Node: ASINH276693 ! Node: ASSOCIATED277691 ! Node: ATAN280696 ! Node: ATAN2282115 ! Node: ATANH283887 ! Node: ATOMIC_ADD284884 ! Node: ATOMIC_AND286423 ! Node: ATOMIC_CAS288018 ! Node: ATOMIC_DEFINE289881 ! Node: ATOMIC_FETCH_ADD291588 ! Node: ATOMIC_FETCH_AND293375 ! Node: ATOMIC_FETCH_OR295171 ! Node: ATOMIC_FETCH_XOR296959 ! Node: ATOMIC_OR298748 ! Node: ATOMIC_REF300340 ! Node: ATOMIC_XOR302242 ! Node: BACKTRACE303834 ! Node: BESSEL_J0304413 ! Node: BESSEL_J1305421 ! Node: BESSEL_JN306430 ! Node: BESSEL_Y0308312 ! Node: BESSEL_Y1309258 ! Node: BESSEL_YN310204 ! Node: BGE312036 ! Node: BGT312725 ! Node: BIT_SIZE313372 ! Node: BLE314193 ! Node: BLT314872 ! Node: BTEST315507 ! Node: C_ASSOCIATED316390 ! Node: C_F_POINTER317599 ! Node: C_F_PROCPOINTER319023 ! Node: C_FUNLOC320524 ! Node: C_LOC321893 ! Node: C_SIZEOF323170 ! Node: CEILING324580 ! Node: CHAR325585 ! Node: CHDIR326789 ! Node: CHMOD327957 ! Node: CMPLX329820 ! Node: CO_BROADCAST331274 ! Node: CO_MAX333038 ! Node: CO_MIN334910 ! Node: CO_REDUCE336768 ! Node: CO_SUM340245 ! Node: COMMAND_ARGUMENT_COUNT342144 ! Node: COMPILER_OPTIONS343068 ! Node: COMPILER_VERSION344094 ! Node: COMPLEX345058 ! Node: CONJG346195 ! Node: COS347266 ! Node: COSH348712 ! Node: COUNT349877 ! Node: CPU_TIME351893 ! Node: CSHIFT353247 ! Node: CTIME354903 ! Node: DATE_AND_TIME356413 ! Node: DBLE358873 ! Node: DCMPLX359666 ! Node: DIGITS360860 ! Node: DIM361826 ! Node: DOT_PRODUCT363084 ! Node: DPROD364740 ! Node: DREAL365657 ! Node: DSHIFTL366323 ! Node: DSHIFTR367643 ! Node: DTIME368964 ! Node: EOSHIFT371767 ! Node: EPSILON373840 ! Node: ERF374566 ! Node: ERFC375340 ! Node: ERFC_SCALED376144 ! Node: ETIME376836 ! Node: EVENT_QUERY379068 ! Node: EXECUTE_COMMAND_LINE380666 ! Node: EXIT383252 ! Node: EXP384126 ! Node: EXPONENT385399 ! Node: EXTENDS_TYPE_OF386159 ! Node: FDATE387012 ! Node: FGET388494 ! Node: FGETC390312 ! Node: FLOOR392113 ! Node: FLUSH393099 ! Node: FNUM394976 ! Node: FPUT395700 ! Node: FPUTC397327 ! Node: FRACTION399100 ! Node: FREE400003 ! Node: FSEEK400840 ! Node: FSTAT403136 ! Node: FTELL404218 ! Node: GAMMA405198 ! Node: GERROR406241 ! Node: GETARG406962 ! Node: GET_COMMAND408728 ! Node: GET_COMMAND_ARGUMENT410094 ! Node: GETCWD412130 ! Node: GETENV413104 ! Node: GET_ENVIRONMENT_VARIABLE414529 ! Node: GETGID416682 ! Node: GETLOG417219 ! Node: GETPID418079 ! Node: GETUID418809 ! Node: GMTIME419325 ! Node: HOSTNM420814 ! Node: HUGE421732 ! Node: HYPOT422453 ! Node: IACHAR423273 ! Node: IALL424453 ! Node: IAND425930 ! Node: IANY426914 ! Node: IARGC428400 ! Node: IBCLR429421 ! Node: IBITS430082 ! Node: IBSET430997 ! Node: ICHAR431653 ! Node: IDATE433825 ! Node: IEOR434852 ! Node: IERRNO435728 ! Node: IMAGE_INDEX436277 ! Node: INDEX intrinsic437301 ! Node: INT438842 ! Node: INT2440574 ! Node: INT8441339 ! Node: IOR442051 ! Node: IPARITY442903 ! Node: IRAND444427 ! Node: IS_IOSTAT_END445783 ! Node: IS_IOSTAT_EOR446880 ! Node: ISATTY448007 ! Node: ISHFT448790 ! Node: ISHFTC449770 ! Node: ISNAN450986 ! Node: ITIME451734 ! Node: KILL452759 ! Node: KIND453663 ! Node: LBOUND454508 ! Node: LCOBOUND455841 ! Node: LEADZ456971 ! Node: LEN457831 ! Node: LEN_TRIM459112 ! Node: LGE460094 ! Node: LGT461596 ! Node: LINK463063 ! Node: LLE464098 ! Node: LLT465592 ! Node: LNBLNK467052 ! Node: LOC467828 ! Node: LOG468559 ! Node: LOG10469959 ! Node: LOG_GAMMA470933 ! Node: LOGICAL472022 ! Node: LONG472830 ! Node: LSHIFT473586 ! Node: LSTAT474671 ! Node: LTIME475865 ! Node: MALLOC477276 ! Node: MASKL478735 ! Node: MASKR479498 ! Node: MATMUL480264 ! Node: MAX481353 ! Node: MAXEXPONENT482852 ! Node: MAXLOC483668 ! Node: MAXVAL485687 ! Node: MCLOCK487320 ! Node: MCLOCK8488344 ! Node: MERGE489577 ! Node: MERGE_BITS490326 ! Node: MIN491187 ! Node: MINEXPONENT492688 ! Node: MINLOC493318 ! Node: MINVAL495337 ! Node: MOD496989 ! Node: MODULO498734 ! Node: MOVE_ALLOC500034 ! Node: MVBITS501063 ! Node: NEAREST502122 ! Node: NEW_LINE503218 ! Node: NINT503989 ! Node: NORM2505392 ! Node: NOT506530 ! Node: NULL507114 ! Node: NUM_IMAGES508019 ! Node: OR509729 ! Node: PACK511013 ! Node: PARITY513006 ! Node: PERROR514221 ! Node: POPCNT514842 ! Node: POPPAR515713 ! Node: PRECISION516764 ! Node: PRESENT517650 ! Node: PRODUCT518756 ! Node: RADIX520281 ! Node: RAN521093 ! Node: RAND521549 ! Node: RANDOM_NUMBER522881 ! Node: RANDOM_SEED524598 ! Node: RANGE528410 ! Node: RANK529106 ! Node: REAL529886 ! Node: RENAME531661 ! Node: REPEAT532680 ! Node: RESHAPE533406 ! Node: RRSPACING534875 ! Node: RSHIFT535568 ! Node: SAME_TYPE_AS536706 ! Node: SCALE537536 ! Node: SCAN538316 ! Node: SECNDS539866 ! Node: SECOND540954 ! Node: SELECTED_CHAR_KIND541830 ! Node: SELECTED_INT_KIND543421 ! Node: SELECTED_REAL_KIND544596 ! Node: SET_EXPONENT547262 ! Node: SHAPE548258 ! Node: SHIFTA549673 ! Node: SHIFTL550634 ! Node: SHIFTR551469 ! Node: SIGN552305 ! Node: SIGNAL553589 ! Node: SIN555086 ! Node: SINH556184 ! Node: SIZE557180 ! Node: SIZEOF558488 ! Node: SLEEP560138 ! Node: SPACING560698 ! Node: SPREAD561711 ! Node: SQRT562856 ! Node: SRAND564210 ! Node: STAT565443 ! Node: STORAGE_SIZE568610 ! Node: SUM569489 ! Node: SYMLNK570972 ! Node: SYSTEM572104 ! Node: SYSTEM_CLOCK573355 ! Node: TAN576182 ! Node: TANH577154 ! Node: THIS_IMAGE578311 ! Node: TIME580600 ! Node: TIME8581725 ! Node: TINY582875 ! Node: TRAILZ583475 ! Node: TRANSFER584292 ! Node: TRANSPOSE586326 ! Node: TRIM587013 ! Node: TTYNAM587870 ! Node: UBOUND588785 ! Node: UCOBOUND590175 ! Node: UMASK591307 ! Node: UNLINK591985 ! Node: UNPACK592962 ! Node: VERIFY594250 ! Node: XOR595971 ! Node: Intrinsic Modules597343 ! Node: ISO_FORTRAN_ENV597632 ! Node: ISO_C_BINDING602018 ! Node: IEEE modules606209 ! Node: OpenMP Modules OMP_LIB and OMP_LIB_KINDS607354 ! Node: OpenACC Module OPENACC608898 ! Node: Contributing609825 ! Node: Contributors610679 ! Node: Projects612346 ! Node: Proposed Extensions613151 ! Node: Copying615162 ! Node: GNU Free Documentation License652726 ! Node: Funding677869 ! Node: Option Index680394 ! Node: Keyword Index696298  End Tag Table diff -Nrcpad gcc-6.3.0/gcc/fortran/gfortranspec.c gcc-6.4.0/gcc/fortran/gfortranspec.c *** gcc-6.3.0/gcc/fortran/gfortranspec.c Mon Jan 4 13:03:35 2016 --- gcc-6.4.0/gcc/fortran/gfortranspec.c Tue Jul 4 07:15:57 2017 *************** lang_specific_driver (struct cl_decoded_ *** 276,282 **** case OPT__version: printf ("GNU Fortran %s%s\n", pkgversion_string, version_string); ! printf ("Copyright %s 2016 Free Software Foundation, Inc.\n", _("(C)")); fputs (_("This is free software; see the source for copying conditions. There is NO\n\ warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n"), --- 276,282 ---- case OPT__version: printf ("GNU Fortran %s%s\n", pkgversion_string, version_string); ! printf ("Copyright %s 2017 Free Software Foundation, Inc.\n", _("(C)")); fputs (_("This is free software; see the source for copying conditions. There is NO\n\ warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n"), diff -Nrcpad gcc-6.3.0/gcc/fortran/intrinsic.c gcc-6.4.0/gcc/fortran/intrinsic.c *** gcc-6.3.0/gcc/fortran/intrinsic.c Wed Sep 28 20:18:56 2016 --- gcc-6.4.0/gcc/fortran/intrinsic.c Sat Jun 3 11:26:38 2017 *************** gfc_intrinsic_func_interface (gfc_expr * *** 4449,4454 **** --- 4449,4475 ---- return MATCH_ERROR; } + /* F95, 7.1.6.1: Only transformational functions REPEAT, RESHAPE, + SELECTED_INT_KIND, SELECTED_REAL_KIND, TRANSFER, and TRIM are allowed in + initialization expressions. */ + + if (gfc_init_expr_flag && isym->transformational) + { + gfc_isym_id id = isym->id; + if (id != GFC_ISYM_REPEAT && id != GFC_ISYM_RESHAPE + && id != GFC_ISYM_SI_KIND && id != GFC_ISYM_SR_KIND + && id != GFC_ISYM_TRANSFER && id != GFC_ISYM_TRIM + && !gfc_notify_std (GFC_STD_F2003, "Transformational function %qs " + "at %L is invalid in an initialization " + "expression", name, &expr->where)) + { + if (!error_flag) + gfc_pop_suppress_errors (); + + return MATCH_ERROR; + } + } + gfc_current_intrinsic_where = &expr->where; /* Bypass the generic list for min, max and ISO_C_Binding's c_loc. */ diff -Nrcpad gcc-6.3.0/gcc/fortran/module.c gcc-6.4.0/gcc/fortran/module.c *** gcc-6.3.0/gcc/fortran/module.c Sat May 14 19:52:46 2016 --- gcc-6.4.0/gcc/fortran/module.c Sat Apr 1 09:35:52 2017 *************** static const char *module_name; *** 193,202 **** /* The name of the .smod file that the submodule will write to. */ static const char *submodule_name; - /* Suppress the output of a .smod file by module, if no module - procedures have been seen. */ - static bool no_module_procedures; - static gfc_use_list *module_list; /* If we're reading an intrinsic module, this is its ID. */ --- 193,198 ---- *************** gfc_match_submodule (void) *** 740,745 **** --- 736,742 ---- match m; char name[GFC_MAX_SYMBOL_LEN + 1]; gfc_use_list *use_list; + bool seen_colon = false; if (!gfc_notify_std (GFC_STD_F2008, "SUBMODULE declaration at %C")) return MATCH_ERROR; *************** gfc_match_submodule (void) *** 772,778 **** } else { ! module_list = use_list; use_list->module_name = gfc_get_string (name); use_list->submodule_name = use_list->module_name; } --- 769,775 ---- } else { ! module_list = use_list; use_list->module_name = gfc_get_string (name); use_list->submodule_name = use_list->module_name; } *************** gfc_match_submodule (void) *** 780,787 **** if (gfc_match_char (')') == MATCH_YES) break; ! if (gfc_match_char (':') != MATCH_YES) goto syntax; } m = gfc_match (" %s%t", &gfc_new_block); --- 777,787 ---- if (gfc_match_char (')') == MATCH_YES) break; ! if (gfc_match_char (':') != MATCH_YES ! || seen_colon) goto syntax; + + seen_colon = true; } m = gfc_match (" %s%t", &gfc_new_block); *************** mio_symbol_attribute (symbol_attribute * *** 2236,2245 **** if (attr->array_outer_dependency) MIO_NAME (ab_attribute) (AB_ARRAY_OUTER_DEPENDENCY, attr_bits); if (attr->module_procedure) - { MIO_NAME (ab_attribute) (AB_MODULE_PROCEDURE, attr_bits); - no_module_procedures = false; - } if (attr->oacc_declare_create) MIO_NAME (ab_attribute) (AB_OACC_DECLARE_CREATE, attr_bits); if (attr->oacc_declare_copyin) --- 2236,2242 ---- *************** dump_module (const char *name, int dump_ *** 6125,6130 **** --- 6122,6139 ---- } + /* Suppress the output of a .smod file by module, if no module + procedures have been seen. */ + static bool no_module_procedures; + + static void + check_for_module_procedures (gfc_symbol *sym) + { + if (sym && sym->attr.module_procedure) + no_module_procedures = false; + } + + void gfc_dump_module (const char *name, int dump_flag) { *************** gfc_dump_module (const char *name, int d *** 6134,6139 **** --- 6143,6150 ---- dump_smod =false; no_module_procedures = true; + gfc_traverse_ns (gfc_current_ns, check_for_module_procedures); + dump_module (name, dump_flag); if (no_module_procedures || dump_smod) *************** gfc_use_module (gfc_use_list *module) *** 6917,6924 **** } if (module_fp == NULL) ! gfc_fatal_error ("Can't open module file %qs for reading at %C: %s", ! filename, xstrerror (errno)); /* Check that we haven't already USEd an intrinsic module with the same name. */ --- 6928,6944 ---- } if (module_fp == NULL) ! { ! if (gfc_state_stack->state != COMP_SUBMODULE ! && module->submodule_name == NULL) ! gfc_fatal_error ("Can't open module file %qs for reading at %C: %s", ! filename, xstrerror (errno)); ! else ! gfc_fatal_error ("Module file %qs has not been generated, either " ! "because the module does not contain a MODULE " ! "PROCEDURE or there is an error in the module.", ! filename); ! } /* Check that we haven't already USEd an intrinsic module with the same name. */ diff -Nrcpad gcc-6.3.0/gcc/fortran/openmp.c gcc-6.4.0/gcc/fortran/openmp.c *** gcc-6.3.0/gcc/fortran/openmp.c Thu Sep 1 11:48:02 2016 --- gcc-6.4.0/gcc/fortran/openmp.c Thu Jun 22 11:09:58 2017 *************** resolve_omp_clauses (gfc_code *code, gfc *** 3530,3535 **** --- 3530,3540 ---- else resolve_oacc_data_clauses (n->sym, n->where, name); } + else if (list != OMP_LIST_DEPEND + && n->sym->as + && n->sym->as->type == AS_ASSUMED_SIZE) + gfc_error ("Assumed size array %qs in %s clause at %L", + n->sym->name, name, &n->where); } if (list != OMP_LIST_DEPEND) diff -Nrcpad gcc-6.3.0/gcc/fortran/parse.c gcc-6.4.0/gcc/fortran/parse.c *** gcc-6.3.0/gcc/fortran/parse.c Sun Oct 23 22:19:36 2016 --- gcc-6.4.0/gcc/fortran/parse.c Sun Mar 26 20:01:07 2017 *************** check_component (gfc_symbol *sym, gfc_co *** 2795,2801 **** coarray = true; sym->attr.coarray_comp = 1; } ! if (c->ts.type == BT_DERIVED && c->ts.u.derived->attr.coarray_comp && !c->attr.pointer) { --- 2795,2801 ---- coarray = true; sym->attr.coarray_comp = 1; } ! if (c->ts.type == BT_DERIVED && c->ts.u.derived->attr.coarray_comp && !c->attr.pointer) { *************** parse_union (void) *** 2959,2965 **** /* Add a component to the union for each map. */ if (!gfc_add_component (un, gfc_new_block->name, &c)) { ! gfc_internal_error ("failed to create map component '%s'", gfc_new_block->name); reject_statement (); return; --- 2959,2965 ---- /* Add a component to the union for each map. */ if (!gfc_add_component (un, gfc_new_block->name, &c)) { ! gfc_internal_error ("failed to create map component '%s'", gfc_new_block->name); reject_statement (); return; *************** static void *** 5668,5673 **** --- 5668,5676 ---- set_syms_host_assoc (gfc_symbol *sym) { gfc_component *c; + const char dot[2] = "."; + char parent1[GFC_MAX_SYMBOL_LEN + 1]; + char parent2[GFC_MAX_SYMBOL_LEN + 1]; if (sym == NULL) return; *************** set_syms_host_assoc (gfc_symbol *sym) *** 5675,5690 **** if (sym->attr.module_procedure) sym->attr.external = 0; - /* sym->attr.access = ACCESS_PUBLIC; */ - sym->attr.use_assoc = 0; sym->attr.host_assoc = 1; sym->attr.used_in_submodule =1; if (sym->attr.flavor == FL_DERIVED) { ! for (c = sym->components; c; c = c->next) ! c->attr.access = ACCESS_PUBLIC; } } --- 5678,5709 ---- if (sym->attr.module_procedure) sym->attr.external = 0; sym->attr.use_assoc = 0; sym->attr.host_assoc = 1; sym->attr.used_in_submodule =1; if (sym->attr.flavor == FL_DERIVED) { ! /* Derived types with PRIVATE components that are declared in ! modules other than the parent module must not be changed to be ! PUBLIC. The 'use-assoc' attribute must be reset so that the ! test in symbol.c(gfc_find_component) works correctly. This is ! not necessary for PRIVATE symbols since they are not read from ! the module. */ ! memset(parent1, '\0', sizeof(parent1)); ! memset(parent2, '\0', sizeof(parent2)); ! strcpy (parent1, gfc_new_block->name); ! strcpy (parent2, sym->module); ! if (strcmp (strtok (parent1, dot), strtok (parent2, dot)) == 0) ! { ! for (c = sym->components; c; c = c->next) ! c->attr.access = ACCESS_PUBLIC; ! } ! else ! { ! sym->attr.use_assoc = 1; ! sym->attr.host_assoc = 0; ! } } } diff -Nrcpad gcc-6.3.0/gcc/fortran/resolve.c gcc-6.4.0/gcc/fortran/resolve.c *** gcc-6.3.0/gcc/fortran/resolve.c Sun Nov 20 20:12:18 2016 --- gcc-6.4.0/gcc/fortran/resolve.c Sun Jan 29 14:47:28 2017 *************** resolve_lock_unlock_event (gfc_code *cod *** 8840,8849 **** return; /* Check for EVENT WAIT the UNTIL_COUNT. */ ! if (code->op == EXEC_EVENT_WAIT && code->expr4 ! && (code->expr4->ts.type != BT_INTEGER || code->expr4->rank != 0)) ! gfc_error ("UNTIL_COUNT= argument at %L must be a scalar INTEGER " ! "expression", &code->expr4->where); } --- 8840,8852 ---- return; /* Check for EVENT WAIT the UNTIL_COUNT. */ ! if (code->op == EXEC_EVENT_WAIT && code->expr4) ! { ! if (!gfc_resolve_expr (code->expr4) || code->expr4->ts.type != BT_INTEGER ! || code->expr4->rank != 0) ! gfc_error ("UNTIL_COUNT= argument at %L must be a scalar INTEGER " ! "expression", &code->expr4->where); ! } } diff -Nrcpad gcc-6.3.0/gcc/fortran/symbol.c gcc-6.4.0/gcc/fortran/symbol.c *** gcc-6.3.0/gcc/fortran/symbol.c Fri Oct 28 23:40:07 2016 --- gcc-6.4.0/gcc/fortran/symbol.c Sat Apr 1 11:35:14 2017 *************** check_conflict (symbol_attribute *attr, *** 464,471 **** } } ! if (attr->dummy && ((attr->function || attr->subroutine) && ! gfc_current_state () == COMP_CONTAINS)) gfc_error_now ("internal procedure %qs at %L conflicts with " "DUMMY argument", name, where); --- 464,476 ---- } } ! /* The copying of procedure dummy arguments for module procedures in ! a submodule occur whilst the current state is COMP_CONTAINS. It ! is necessary, therefore, to let this through. */ ! if (attr->dummy ! && (attr->function || attr->subroutine) ! && gfc_current_state () == COMP_CONTAINS ! && !(gfc_new_block && gfc_new_block->abr_modproc_decl)) gfc_error_now ("internal procedure %qs at %L conflicts with " "DUMMY argument", name, where); *************** gfc_add_flavor (symbol_attribute *attr, *** 1587,1592 **** --- 1592,1604 ---- if (attr->flavor == f && f == FL_VARIABLE) return true; + /* Copying a procedure dummy argument for a module procedure in a + submodule results in the flavor being copied and would result in + an error without this. */ + if (gfc_new_block && gfc_new_block->abr_modproc_decl + && attr->flavor == f && f == FL_PROCEDURE) + return true; + if (attr->flavor != FL_UNKNOWN) { if (where == NULL) diff -Nrcpad gcc-6.3.0/gcc/fortran/trans-decl.c gcc-6.4.0/gcc/fortran/trans-decl.c *** gcc-6.3.0/gcc/fortran/trans-decl.c Wed Sep 28 20:18:56 2016 --- gcc-6.4.0/gcc/fortran/trans-decl.c Sun Jan 29 13:50:23 2017 *************** gfc_build_qualified_array (tree decl, gf *** 887,892 **** --- 887,896 ---- DECL_CONTEXT (token) = sym->ns->proc_name->backend_decl; gfc_module_add_decl (cur_module, token); } + else if (sym->attr.host_assoc + && TREE_CODE (DECL_CONTEXT (current_function_decl)) + != TRANSLATION_UNIT_DECL) + gfc_add_decl_to_parent_function (token); else gfc_add_decl_to_function (token); } diff -Nrcpad gcc-6.3.0/gcc/fortran/trans-expr.c gcc-6.4.0/gcc/fortran/trans-expr.c *** gcc-6.3.0/gcc/fortran/trans-expr.c Sun Oct 23 11:55:44 2016 --- gcc-6.4.0/gcc/fortran/trans-expr.c Fri Jun 9 18:10:48 2017 *************** gfc_get_tree_for_caf_expr (gfc_expr *exp *** 1898,1905 **** &expr->where); } ! caf_decl = expr->symtree->n.sym->backend_decl; ! gcc_assert (caf_decl); if (expr->symtree->n.sym->ts.type == BT_CLASS) caf_decl = gfc_class_data_get (caf_decl); if (expr->symtree->n.sym->attr.codimension) --- 1898,1908 ---- &expr->where); } ! /* Make sure the backend_decl is present before accessing it. */ ! caf_decl = expr->symtree->n.sym->backend_decl == NULL_TREE ! ? gfc_get_symbol_decl (expr->symtree->n.sym) ! : expr->symtree->n.sym->backend_decl; ! if (expr->symtree->n.sym->ts.type == BT_CLASS) caf_decl = gfc_class_data_get (caf_decl); if (expr->symtree->n.sym->attr.codimension) *************** gfc_conv_procedure_call (gfc_se * se, gf *** 6069,6075 **** after use. This necessitates the creation of a temporary to hold the result to prevent duplicate calls. */ if (!byref && sym->ts.type != BT_CHARACTER ! && sym->attr.allocatable && !sym->attr.dimension) { tmp = gfc_create_var (TREE_TYPE (se->expr), NULL); gfc_add_modify (&se->pre, tmp, se->expr); --- 6072,6078 ---- after use. This necessitates the creation of a temporary to hold the result to prevent duplicate calls. */ if (!byref && sym->ts.type != BT_CHARACTER ! && sym->attr.allocatable && !sym->attr.dimension && !comp) { tmp = gfc_create_var (TREE_TYPE (se->expr), NULL); gfc_add_modify (&se->pre, tmp, se->expr); diff -Nrcpad gcc-6.3.0/gcc/fortran/trans-openmp.c gcc-6.4.0/gcc/fortran/trans-openmp.c *** gcc-6.3.0/gcc/fortran/trans-openmp.c Wed Dec 7 22:34:05 2016 --- gcc-6.4.0/gcc/fortran/trans-openmp.c Tue Jan 17 20:29:19 2017 *************** along with GCC; see the file COPYING3. *** 37,42 **** --- 37,47 ---- #include "arith.h" #include "omp-low.h" #include "gomp-constants.h" + #undef GCC_DIAG_STYLE + #define GCC_DIAG_STYLE __gcc_tdiag__ + #include "diagnostic-core.h" + #undef GCC_DIAG_STYLE + #define GCC_DIAG_STYLE __gcc_gfc__ int ompws_flags; *************** gfc_omp_finish_clause (tree c, gimple_se *** 1028,1033 **** --- 1033,1053 ---- return; tree decl = OMP_CLAUSE_DECL (c); + + /* Assumed-size arrays can't be mapped implicitly, they have to be + mapped explicitly using array sections. */ + if (TREE_CODE (decl) == PARM_DECL + && GFC_ARRAY_TYPE_P (TREE_TYPE (decl)) + && GFC_TYPE_ARRAY_AKIND (TREE_TYPE (decl)) == GFC_ARRAY_UNKNOWN + && GFC_TYPE_ARRAY_UBOUND (TREE_TYPE (decl), + GFC_TYPE_ARRAY_RANK (TREE_TYPE (decl)) - 1) + == NULL) + { + error_at (OMP_CLAUSE_LOCATION (c), + "implicit mapping of assumed size array %qD", decl); + return; + } + tree c2 = NULL_TREE, c3 = NULL_TREE, c4 = NULL_TREE; if (POINTER_TYPE_P (TREE_TYPE (decl))) { diff -Nrcpad gcc-6.3.0/gcc/fortran/trans-types.c gcc-6.4.0/gcc/fortran/trans-types.c *** gcc-6.3.0/gcc/fortran/trans-types.c Sat May 14 19:52:46 2016 --- gcc-6.4.0/gcc/fortran/trans-types.c Mon May 1 09:56:52 2017 *************** gfc_get_int_kind_from_width_isofortranen *** 234,260 **** return -1; } ! /* Get the kind number corresponding to a real of given storage size, ! following the required return values for ISO_FORTRAN_ENV REAL* constants: ! -2 is returned if we support a kind of larger size, -1 otherwise. */ int gfc_get_real_kind_from_width_isofortranenv (int size) { ! int i; size /= 8; /* Look for a kind with matching storage size. */ for (i = 0; gfc_real_kinds[i].kind != 0; i++) if (int_size_in_bytes (gfc_get_real_type (gfc_real_kinds[i].kind)) == size) ! return gfc_real_kinds[i].kind; /* Look for a kind with larger storage size. */ for (i = 0; gfc_real_kinds[i].kind != 0; i++) if (int_size_in_bytes (gfc_get_real_type (gfc_real_kinds[i].kind)) > size) ! return -2; ! return -1; } --- 234,275 ---- return -1; } ! ! /* Get the kind number corresponding to a real of a given storage size. ! If two real's have the same storage size, then choose the real with ! the largest precision. If a kind type is unavailable and a real ! exists with wider storage, then return -2; otherwise, return -1. */ ! int gfc_get_real_kind_from_width_isofortranenv (int size) { ! int digits, i, kind; size /= 8; + kind = -1; + digits = 0; + /* Look for a kind with matching storage size. */ for (i = 0; gfc_real_kinds[i].kind != 0; i++) if (int_size_in_bytes (gfc_get_real_type (gfc_real_kinds[i].kind)) == size) ! { ! if (gfc_real_kinds[i].digits > digits) ! { ! digits = gfc_real_kinds[i].digits; ! kind = gfc_real_kinds[i].kind; ! } ! } ! ! if (kind != -1) ! return kind; /* Look for a kind with larger storage size. */ for (i = 0; gfc_real_kinds[i].kind != 0; i++) if (int_size_in_bytes (gfc_get_real_type (gfc_real_kinds[i].kind)) > size) ! kind = -2; ! return kind; } *************** gfc_get_derived_type (gfc_symbol * deriv *** 2595,2603 **** the same as derived, by forcing the procedure pointer component to be built as if the explicit interface does not exist. */ if (c->attr.proc_pointer ! && ((c->ts.type != BT_DERIVED && c->ts.type != BT_CLASS) ! || (c->ts.u.derived ! && !gfc_compare_derived_types (derived, c->ts.u.derived)))) field_type = gfc_get_ppc_type (c); else if (c->attr.proc_pointer && derived->backend_decl) { --- 2610,2619 ---- the same as derived, by forcing the procedure pointer component to be built as if the explicit interface does not exist. */ if (c->attr.proc_pointer ! && (c->ts.type != BT_DERIVED || (c->ts.u.derived ! && !gfc_compare_derived_types (derived, c->ts.u.derived))) ! && (c->ts.type != BT_CLASS || (CLASS_DATA (c)->ts.u.derived ! && !gfc_compare_derived_types (derived, CLASS_DATA (c)->ts.u.derived)))) field_type = gfc_get_ppc_type (c); else if (c->attr.proc_pointer && derived->backend_decl) { diff -Nrcpad gcc-6.3.0/gcc/fortran/trans.c gcc-6.4.0/gcc/fortran/trans.c *** gcc-6.3.0/gcc/fortran/trans.c Sat Feb 27 11:57:16 2016 --- gcc-6.4.0/gcc/fortran/trans.c Tue Mar 14 12:57:08 2017 *************** gfc_add_modify_loc (location_t loc, stmt *** 151,161 **** tree t1, t2; t1 = TREE_TYPE (rhs); t2 = TREE_TYPE (lhs); ! /* Make sure that the types of the rhs and the lhs are the same for scalar assignments. We should probably have something similar for aggregates, but right now removing that check just breaks everything. */ ! gcc_checking_assert (t1 == t2 || AGGREGATE_TYPE_P (TREE_TYPE (lhs))); tmp = fold_build2_loc (loc, MODIFY_EXPR, void_type_node, lhs, --- 151,161 ---- tree t1, t2; t1 = TREE_TYPE (rhs); t2 = TREE_TYPE (lhs); ! /* Make sure that the types of the rhs and the lhs are compatible for scalar assignments. We should probably have something similar for aggregates, but right now removing that check just breaks everything. */ ! gcc_checking_assert (TYPE_MAIN_VARIANT (t1) == TYPE_MAIN_VARIANT (t2) || AGGREGATE_TYPE_P (TREE_TYPE (lhs))); tmp = fold_build2_loc (loc, MODIFY_EXPR, void_type_node, lhs, diff -Nrcpad gcc-6.3.0/gcc/function.c gcc-6.4.0/gcc/function.c *** gcc-6.3.0/gcc/function.c Wed Jun 22 13:15:48 2016 --- gcc-6.4.0/gcc/function.c Fri Jan 20 09:33:15 2017 *************** invoke_set_current_function_hook (tree f *** 4800,4808 **** /* cfun should never be set directly; use this function. */ void ! set_cfun (struct function *new_cfun) { ! if (cfun != new_cfun) { cfun = new_cfun; invoke_set_current_function_hook (new_cfun ? new_cfun->decl : NULL_TREE); --- 4800,4808 ---- /* cfun should never be set directly; use this function. */ void ! set_cfun (struct function *new_cfun, bool force) { ! if (cfun != new_cfun || force) { cfun = new_cfun; invoke_set_current_function_hook (new_cfun ? new_cfun->decl : NULL_TREE); diff -Nrcpad gcc-6.3.0/gcc/function.h gcc-6.4.0/gcc/function.h *** gcc-6.3.0/gcc/function.h Wed Mar 16 16:50:18 2016 --- gcc-6.4.0/gcc/function.h Fri Jan 20 09:33:15 2017 *************** extern tree block_chainon (tree, tree); *** 606,612 **** extern void number_blocks (tree); /* cfun shouldn't be set directly; use one of these functions instead. */ ! extern void set_cfun (struct function *new_cfun); extern void push_cfun (struct function *new_cfun); extern void pop_cfun (void); --- 606,612 ---- extern void number_blocks (tree); /* cfun shouldn't be set directly; use one of these functions instead. */ ! extern void set_cfun (struct function *new_cfun, bool force = false); extern void push_cfun (struct function *new_cfun); extern void pop_cfun (void); diff -Nrcpad gcc-6.3.0/gcc/gcc.c gcc-6.4.0/gcc/gcc.c *** gcc-6.3.0/gcc/gcc.c Mon Aug 15 11:19:34 2016 --- gcc-6.4.0/gcc/gcc.c Tue Jul 4 07:15:57 2017 *************** static int have_c = 0; *** 1919,1924 **** --- 1919,1927 ---- /* Was the option -o passed. */ static int have_o = 0; + /* Was the option -E passed. */ + static int have_E = 0; + /* Pointer to output file name passed in with -o. */ static const char *output_file = 0; *************** driver_handle_option (struct gcc_options *** 4031,4036 **** --- 4034,4043 ---- validated = true; break; + case OPT_E: + have_E = true; + break; + case OPT_x: spec_lang = arg; if (!strcmp (spec_lang, "none")) *************** process_command (unsigned int decoded_op *** 4415,4420 **** --- 4422,4430 ---- output_file); } + if (output_file != NULL && output_file[0] == '\0') + fatal_error (input_location, "output filename may not be empty"); + /* If -save-temps=obj and -o name, create the prefix to use for %b. Otherwise just make -save-temps=obj the same as -save-temps=cwd. */ if (save_temps_flag == SAVE_TEMPS_OBJ && save_temps_prefix != NULL) *************** driver::build_option_suggestions (void) *** 7692,7697 **** --- 7702,7718 ---- { for (int j = 0; sanitizer_opts[j].name != NULL; ++j) { + struct cl_option optb; + /* -fsanitize=all is not valid, only -fno-sanitize=all. + So don't register the positive misspelling candidates + for it. */ + if (sanitizer_opts[j].flag == ~0U && i == OPT_fsanitize_) + { + optb = *option; + optb.opt_text = opt_text = "-fno-sanitize="; + optb.cl_reject_negative = true; + option = &optb; + } /* Get one arg at a time e.g. "-fsanitize=address". */ char *with_arg = concat (opt_text, sanitizer_opts[j].name, *************** driver::maybe_print_and_exit () const *** 7898,7904 **** { printf (_("%s %s%s\n"), progname, pkgversion_string, version_string); ! printf ("Copyright %s 2016 Free Software Foundation, Inc.\n", _("(C)")); fputs (_("This is free software; see the source for copying conditions. There is NO\n\ warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n"), --- 7919,7925 ---- { printf (_("%s %s%s\n"), progname, pkgversion_string, version_string); ! printf ("Copyright %s 2017 Free Software Foundation, Inc.\n", _("(C)")); fputs (_("This is free software; see the source for copying conditions. There is NO\n\ warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n"), *************** lookup_compiler (const char *name, size_ *** 8273,8279 **** { for (cp = compilers + n_compilers - 1; cp >= compilers; cp--) if (cp->suffix[0] == '@' && !strcmp (cp->suffix + 1, language)) ! return cp; error ("language %s not recognized", language); return 0; --- 8294,8310 ---- { for (cp = compilers + n_compilers - 1; cp >= compilers; cp--) if (cp->suffix[0] == '@' && !strcmp (cp->suffix + 1, language)) ! { ! if (name != NULL && strcmp (name, "-") == 0 ! && (strcmp (cp->suffix, "@c-header") == 0 ! || strcmp (cp->suffix, "@c++-header") == 0) ! && !have_E) ! fatal_error (input_location, ! "cannot use %<-%> as input filename for a " ! "precompiled header"); ! ! return cp; ! } error ("language %s not recognized", language); return 0; diff -Nrcpad gcc-6.3.0/gcc/gcov-dump.c gcc-6.4.0/gcc/gcov-dump.c *** gcc-6.3.0/gcc/gcov-dump.c Mon Jan 4 13:03:35 2016 --- gcc-6.4.0/gcc/gcov-dump.c Tue Jul 4 07:15:57 2017 *************** print_usage (void) *** 132,148 **** printf ("Usage: gcov-dump [OPTION] ... gcovfiles\n"); printf ("Print coverage file contents\n"); printf (" -h, --help Print this help\n"); - printf (" -v, --version Print version number\n"); printf (" -l, --long Dump record contents too\n"); printf (" -p, --positions Dump record positions\n"); printf (" -w, --working-sets Dump working set computed from summary\n"); } static void print_version (void) { printf ("gcov-dump %s%s\n", pkgversion_string, version_string); ! printf ("Copyright (C) 2016 Free Software Foundation, Inc.\n"); printf ("This is free software; see the source for copying conditions.\n" "There is NO warranty; not even for MERCHANTABILITY or \n" "FITNESS FOR A PARTICULAR PURPOSE.\n\n"); --- 132,150 ---- printf ("Usage: gcov-dump [OPTION] ... gcovfiles\n"); printf ("Print coverage file contents\n"); printf (" -h, --help Print this help\n"); printf (" -l, --long Dump record contents too\n"); printf (" -p, --positions Dump record positions\n"); + printf (" -v, --version Print version number\n"); printf (" -w, --working-sets Dump working set computed from summary\n"); + printf ("\nFor bug reporting instructions, please see:\n%s.\n", + bug_report_url); } static void print_version (void) { printf ("gcov-dump %s%s\n", pkgversion_string, version_string); ! printf ("Copyright (C) 2017 Free Software Foundation, Inc.\n"); printf ("This is free software; see the source for copying conditions.\n" "There is NO warranty; not even for MERCHANTABILITY or \n" "FITNESS FOR A PARTICULAR PURPOSE.\n\n"); diff -Nrcpad gcc-6.3.0/gcc/gcov-io.c gcc-6.4.0/gcc/gcov-io.c *** gcc-6.3.0/gcc/gcov-io.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/gcov-io.c Fri May 26 11:30:54 2017 *************** gcov_write_string (const char *string) *** 372,379 **** buffer = gcov_write_words (1 + alloc); buffer[0] = alloc; ! buffer[alloc] = 0; ! memcpy (&buffer[1], string, length); } #endif --- 372,383 ---- buffer = gcov_write_words (1 + alloc); buffer[0] = alloc; ! ! if (alloc > 0) ! { ! buffer[alloc] = 0; /* place nul terminators. */ ! memcpy (&buffer[1], string, length); ! } } #endif diff -Nrcpad gcc-6.3.0/gcc/gcov-tool.c gcc-6.4.0/gcc/gcov-tool.c *** gcc-6.3.0/gcc/gcov-tool.c Mon Jan 4 13:03:35 2016 --- gcc-6.4.0/gcc/gcov-tool.c Thu Jun 22 11:17:15 2017 *************** extern int gcov_profile_normalize (struc *** 46,51 **** --- 46,52 ---- extern int gcov_profile_scale (struct gcov_info*, float, int, int); extern struct gcov_info* gcov_read_profile_dir (const char*, int); extern void gcov_do_dump (struct gcov_info *, int); + extern const char *gcov_get_filename (struct gcov_info *list); extern void gcov_set_verbose (void); /* Set to verbose output mode. */ *************** gcov_output_files (const char *out, stru *** 114,119 **** --- 115,128 ---- if (ret) fatal_error (input_location, "Cannot change directory to %s", out); + /* Verify that output file does not exist (either was removed by + unlink_profile_data or removed by user). */ + const char *filename = gcov_get_filename (profile); + + if (access (filename, F_OK) != -1) + fatal_error (input_location, "output file %s already exists in folder %s", + filename, out); + gcov_do_dump (profile, 0); ret = chdir (pwd); *************** print_merge_usage_message (int error_p) *** 164,171 **** FILE *file = error_p ? stderr : stdout; fnotice (file, " merge [options] Merge coverage file contents\n"); - fnotice (file, " -v, --verbose Verbose mode\n"); fnotice (file, " -o, --output

Output directory\n"); fnotice (file, " -w, --weight Set weights (float point values)\n"); } --- 173,180 ---- FILE *file = error_p ? stderr : stdout; fnotice (file, " merge [options] Merge coverage file contents\n"); fnotice (file, " -o, --output Output directory\n"); + fnotice (file, " -v, --verbose Verbose mode\n"); fnotice (file, " -w, --weight Set weights (float point values)\n"); } *************** print_rewrite_usage_message (int error_p *** 258,267 **** FILE *file = error_p ? stderr : stdout; fnotice (file, " rewrite [options] Rewrite coverage file contents\n"); ! fnotice (file, " -v, --verbose Verbose mode\n"); fnotice (file, " -o, --output Output directory\n"); fnotice (file, " -s, --scale Scale the profile counters\n"); fnotice (file, " -n, --normalize Normalize the profile\n"); } static const struct option rewrite_options[] = --- 267,277 ---- FILE *file = error_p ? stderr : stdout; fnotice (file, " rewrite [options] Rewrite coverage file contents\n"); ! fnotice (file, " -n, --normalize Normalize the profile\n"); fnotice (file, " -o, --output Output directory\n"); fnotice (file, " -s, --scale Scale the profile counters\n"); fnotice (file, " -n, --normalize Normalize the profile\n"); + fnotice (file, " -v, --verbose Verbose mode\n"); } static const struct option rewrite_options[] = *************** print_overlap_usage_message (int error_p *** 414,425 **** FILE *file = error_p ? stderr : stdout; fnotice (file, " overlap [options] Compute the overlap of two profiles\n"); - fnotice (file, " -v, --verbose Verbose mode\n"); - fnotice (file, " -h, --hotonly Only print info for hot objects/functions\n"); fnotice (file, " -f, --function Print function level info\n"); fnotice (file, " -F, --fullname Print full filename\n"); fnotice (file, " -o, --object Print object level info\n"); fnotice (file, " -t , --hot_threshold Set the threshold for hotness\n"); } --- 424,435 ---- FILE *file = error_p ? stderr : stdout; fnotice (file, " overlap [options] Compute the overlap of two profiles\n"); fnotice (file, " -f, --function Print function level info\n"); fnotice (file, " -F, --fullname Print full filename\n"); + fnotice (file, " -h, --hotonly Only print info for hot objects/functions\n"); fnotice (file, " -o, --object Print object level info\n"); fnotice (file, " -t , --hot_threshold Set the threshold for hotness\n"); + fnotice (file, " -v, --verbose Verbose mode\n"); } diff -Nrcpad gcc-6.3.0/gcc/gcov.c gcc-6.4.0/gcc/gcov.c *** gcc-6.3.0/gcc/gcov.c Thu Nov 3 13:41:39 2016 --- gcc-6.4.0/gcc/gcov.c Tue Jul 4 07:15:57 2017 *************** print_usage (int error_p) *** 469,483 **** FILE *file = error_p ? stderr : stdout; int status = error_p ? FATAL_EXIT_CODE : SUCCESS_EXIT_CODE; ! fnotice (file, "Usage: gcov [OPTION]... SOURCE|OBJ...\n\n"); fnotice (file, "Print code coverage information.\n\n"); - fnotice (file, " -h, --help Print this help, then exit\n"); fnotice (file, " -a, --all-blocks Show information for every basic block\n"); fnotice (file, " -b, --branch-probabilities Include branch probabilities in output\n"); fnotice (file, " -c, --branch-counts Output counts of branches taken\n\ rather than percentages\n"); fnotice (file, " -d, --display-progress Display progress information\n"); fnotice (file, " -f, --function-summaries Output summaries for each function\n"); fnotice (file, " -i, --intermediate-format Output .gcov file in intermediate text format\n"); fnotice (file, " -l, --long-file-names Use long output file names for included\n\ source files\n"); --- 469,483 ---- FILE *file = error_p ? stderr : stdout; int status = error_p ? FATAL_EXIT_CODE : SUCCESS_EXIT_CODE; ! fnotice (file, "Usage: gcov [OPTION...] SOURCE|OBJ...\n\n"); fnotice (file, "Print code coverage information.\n\n"); fnotice (file, " -a, --all-blocks Show information for every basic block\n"); fnotice (file, " -b, --branch-probabilities Include branch probabilities in output\n"); fnotice (file, " -c, --branch-counts Output counts of branches taken\n\ rather than percentages\n"); fnotice (file, " -d, --display-progress Display progress information\n"); fnotice (file, " -f, --function-summaries Output summaries for each function\n"); + fnotice (file, " -h, --help Print this help, then exit\n"); fnotice (file, " -i, --intermediate-format Output .gcov file in intermediate text format\n"); fnotice (file, " -l, --long-file-names Use long output file names for included\n\ source files\n"); *************** static void *** 500,506 **** print_version (void) { fnotice (stdout, "gcov %s%s\n", pkgversion_string, version_string); ! fprintf (stdout, "Copyright %s 2016 Free Software Foundation, Inc.\n", _("(C)")); fnotice (stdout, _("This is free software; see the source for copying conditions.\n" --- 500,506 ---- print_version (void) { fnotice (stdout, "gcov %s%s\n", pkgversion_string, version_string); ! fprintf (stdout, "Copyright %s 2017 Free Software Foundation, Inc.\n", _("(C)")); fnotice (stdout, _("This is free software; see the source for copying conditions.\n" *************** process_args (int argc, char **argv) *** 602,632 **** return optind; } - /* Get the name of the gcov file. The return value must be free'd. - - It appends the '.gcov' extension to the *basename* of the file. - The resulting file name will be in PWD. - - e.g., - input: foo.da, output: foo.da.gcov - input: a/b/foo.cc, output: foo.cc.gcov */ - - static char * - get_gcov_intermediate_filename (const char *file_name) - { - const char *gcov = ".gcov"; - char *result; - const char *cptr; - - /* Find the 'basename'. */ - cptr = lbasename (file_name); - - result = XNEWVEC (char, strlen (cptr) + strlen (gcov) + 1); - sprintf (result, "%s%s", cptr, gcov); - - return result; - } - /* Output the result in intermediate format used by 'lcov'. The intermediate format contains a single file named 'foo.cc.gcov', --- 602,607 ---- *************** output_gcov_file (const char *file_name, *** 792,798 **** if (gcov_file) { fnotice (stdout, "Creating '%s'\n", gcov_file_name); ! output_lines (gcov_file, src); if (ferror (gcov_file)) fnotice (stderr, "Error writing output file '%s'\n", gcov_file_name); fclose (gcov_file); --- 767,777 ---- if (gcov_file) { fnotice (stdout, "Creating '%s'\n", gcov_file_name); ! ! if (flag_intermediate_format) ! output_intermediate_file (gcov_file, src); ! else ! output_lines (gcov_file, src); if (ferror (gcov_file)) fnotice (stderr, "Error writing output file '%s'\n", gcov_file_name); fclose (gcov_file); *************** generate_results (const char *file_name) *** 814,821 **** unsigned ix; source_t *src; function_t *fn; - FILE *gcov_intermediate_file = NULL; - char *gcov_intermediate_filename = NULL; for (ix = n_sources, src = sources; ix--; src++) if (src->num_lines) --- 793,798 ---- *************** generate_results (const char *file_name) *** 845,864 **** file_name = canonicalize_name (file_name); } - if (flag_gcov_file && flag_intermediate_format) - { - /* Open the intermediate file. */ - gcov_intermediate_filename = - get_gcov_intermediate_filename (file_name); - gcov_intermediate_file = fopen (gcov_intermediate_filename, "w"); - if (!gcov_intermediate_file) - { - fnotice (stderr, "Cannot open intermediate output file %s\n", - gcov_intermediate_filename); - return; - } - } - for (ix = n_sources, src = sources; ix--; src++) { if (flag_relative_only) --- 822,827 ---- *************** generate_results (const char *file_name) *** 881,903 **** total_executed += src->coverage.lines_executed; if (flag_gcov_file) { ! if (flag_intermediate_format) ! /* Output the intermediate format without requiring source ! files. This outputs a section to a *single* file. */ ! output_intermediate_file (gcov_intermediate_file, src); ! else ! output_gcov_file (file_name, src); fnotice (stdout, "\n"); } } - if (flag_gcov_file && flag_intermediate_format) - { - /* Now we've finished writing the intermediate file. */ - fclose (gcov_intermediate_file); - XDELETEVEC (gcov_intermediate_filename); - } - if (!file_name) executed_summary (total_lines, total_executed); } --- 844,854 ---- total_executed += src->coverage.lines_executed; if (flag_gcov_file) { ! output_gcov_file (file_name, src); fnotice (stdout, "\n"); } } if (!file_name) executed_summary (total_lines, total_executed); } *************** format_gcov (gcov_type top, gcov_type bo *** 1817,1822 **** --- 1768,1780 ---- { static char buffer[20]; + /* Handle invalid values that would result in a misleading value. */ + if (bottom != 0 && top > bottom && dp >= 0) + { + sprintf (buffer, "NAN %%"); + return buffer; + } + if (dp >= 0) { float ratio = bottom ? (float)top / bottom : 0; diff -Nrcpad gcc-6.3.0/gcc/gcse.c gcc-6.4.0/gcc/gcse.c *** gcc-6.3.0/gcc/gcse.c Tue Mar 1 22:31:52 2016 --- gcc-6.4.0/gcc/gcse.c Wed Mar 22 10:41:18 2017 *************** struct gcse_expr *** 279,285 **** to keep register pressure under control. A value of "0" removes restrictions on how far the expression can travel. */ ! int max_distance; }; /* Occurrence of an expression. --- 279,285 ---- to keep register pressure under control. A value of "0" removes restrictions on how far the expression can travel. */ ! HOST_WIDE_INT max_distance; }; /* Occurrence of an expression. *************** static int oprs_unchanged_p (const_rtx, *** 457,463 **** static int oprs_anticipatable_p (const_rtx, const rtx_insn *); static int oprs_available_p (const_rtx, const rtx_insn *); static void insert_expr_in_table (rtx, machine_mode, rtx_insn *, int, int, ! int, struct gcse_hash_table_d *); static unsigned int hash_expr (const_rtx, machine_mode, int *, int); static void record_last_reg_set_info (rtx_insn *, int); static void record_last_mem_set_info (rtx_insn *); --- 457,463 ---- static int oprs_anticipatable_p (const_rtx, const rtx_insn *); static int oprs_available_p (const_rtx, const rtx_insn *); static void insert_expr_in_table (rtx, machine_mode, rtx_insn *, int, int, ! HOST_WIDE_INT, struct gcse_hash_table_d *); static unsigned int hash_expr (const_rtx, machine_mode, int *, int); static void record_last_reg_set_info (rtx_insn *, int); static void record_last_mem_set_info (rtx_insn *); *************** static void alloc_code_hoist_mem (int, i *** 487,494 **** static void free_code_hoist_mem (void); static void compute_code_hoist_vbeinout (void); static void compute_code_hoist_data (void); ! static int should_hoist_expr_to_dom (basic_block, struct gcse_expr *, basic_block, ! sbitmap, int, int *, enum reg_class, int *, bitmap, rtx_insn *); static int hoist_code (void); static enum reg_class get_regno_pressure_class (int regno, int *nregs); --- 487,496 ---- static void free_code_hoist_mem (void); static void compute_code_hoist_vbeinout (void); static void compute_code_hoist_data (void); ! static int should_hoist_expr_to_dom (basic_block, struct gcse_expr *, ! basic_block, ! sbitmap, HOST_WIDE_INT, int *, ! enum reg_class, int *, bitmap, rtx_insn *); static int hoist_code (void); static enum reg_class get_regno_pressure_class (int regno, int *nregs); *************** static basic_block current_bb; *** 742,748 **** GCSE. */ static int ! want_to_gcse_p (rtx x, machine_mode mode, int *max_distance_ptr) { #ifdef STACK_REGS /* On register stack architectures, don't GCSE constants from the --- 744,750 ---- GCSE. */ static int ! want_to_gcse_p (rtx x, machine_mode mode, HOST_WIDE_INT *max_distance_ptr) { #ifdef STACK_REGS /* On register stack architectures, don't GCSE constants from the *************** want_to_gcse_p (rtx x, machine_mode mode *** 789,795 **** /* PRE doesn't implement max_distance restriction. */ { int cost; ! int max_distance; gcc_assert (!optimize_function_for_speed_p (cfun) && optimize_function_for_size_p (cfun)); --- 791,797 ---- /* PRE doesn't implement max_distance restriction. */ { int cost; ! HOST_WIDE_INT max_distance; gcc_assert (!optimize_function_for_speed_p (cfun) && optimize_function_for_size_p (cfun)); *************** want_to_gcse_p (rtx x, machine_mode mode *** 797,803 **** if (cost < COSTS_N_INSNS (GCSE_UNRESTRICTED_COST)) { ! max_distance = (GCSE_COST_DISTANCE_RATIO * cost) / 10; if (max_distance == 0) return 0; --- 799,806 ---- if (cost < COSTS_N_INSNS (GCSE_UNRESTRICTED_COST)) { ! max_distance ! = ((HOST_WIDE_INT)GCSE_COST_DISTANCE_RATIO * cost) / 10; if (max_distance == 0) return 0; *************** expr_equiv_p (const_rtx x, const_rtx y) *** 1113,1119 **** static void insert_expr_in_table (rtx x, machine_mode mode, rtx_insn *insn, int antic_p, ! int avail_p, int max_distance, struct gcse_hash_table_d *table) { int found, do_not_record_p; unsigned int hash; --- 1116,1123 ---- static void insert_expr_in_table (rtx x, machine_mode mode, rtx_insn *insn, int antic_p, ! int avail_p, HOST_WIDE_INT max_distance, ! struct gcse_hash_table_d *table) { int found, do_not_record_p; unsigned int hash; *************** hash_scan_set (rtx set, rtx_insn *insn, *** 1229,1235 **** else if (REG_P (dest)) { unsigned int regno = REGNO (dest); ! int max_distance = 0; /* See if a REG_EQUAL note shows this equivalent to a simpler expression. --- 1233,1239 ---- else if (REG_P (dest)) { unsigned int regno = REGNO (dest); ! HOST_WIDE_INT max_distance = 0; /* See if a REG_EQUAL note shows this equivalent to a simpler expression. *************** hash_scan_set (rtx set, rtx_insn *insn, *** 1298,1304 **** else if (flag_gcse_las && REG_P (src) && MEM_P (dest)) { unsigned int regno = REGNO (src); ! int max_distance = 0; /* Only record sets of pseudo-regs in the hash table. */ if (regno >= FIRST_PSEUDO_REGISTER --- 1302,1308 ---- else if (flag_gcse_las && REG_P (src) && MEM_P (dest)) { unsigned int regno = REGNO (src); ! HOST_WIDE_INT max_distance = 0; /* Only record sets of pseudo-regs in the hash table. */ if (regno >= FIRST_PSEUDO_REGISTER *************** dump_hash_table (FILE *file, const char *** 1410,1416 **** if (flat_table[i] != 0) { expr = flat_table[i]; ! fprintf (file, "Index %d (hash value %d; max distance %d)\n ", expr->bitmap_index, hash_val[i], expr->max_distance); print_rtl (file, expr->expr); fprintf (file, "\n"); --- 1414,1421 ---- if (flat_table[i] != 0) { expr = flat_table[i]; ! fprintf (file, "Index %d (hash value %d; max distance " ! HOST_WIDE_INT_PRINT_DEC ")\n ", expr->bitmap_index, hash_val[i], expr->max_distance); print_rtl (file, expr->expr); fprintf (file, "\n"); *************** update_bb_reg_pressure (basic_block bb, *** 2874,2880 **** static int should_hoist_expr_to_dom (basic_block expr_bb, struct gcse_expr *expr, ! basic_block bb, sbitmap visited, int distance, int *bb_size, enum reg_class pressure_class, int *nregs, bitmap hoisted_bbs, rtx_insn *from) { --- 2879,2886 ---- static int should_hoist_expr_to_dom (basic_block expr_bb, struct gcse_expr *expr, ! basic_block bb, sbitmap visited, ! HOST_WIDE_INT distance, int *bb_size, enum reg_class pressure_class, int *nregs, bitmap hoisted_bbs, rtx_insn *from) { *************** hoist_code (void) *** 3151,3157 **** computes the expression. */ FOR_EACH_VEC_ELT (domby, j, dominated) { ! int max_distance; /* Ignore self dominance. */ if (bb == dominated) --- 3157,3163 ---- computes the expression. */ FOR_EACH_VEC_ELT (domby, j, dominated) { ! HOST_WIDE_INT max_distance; /* Ignore self dominance. */ if (bb == dominated) diff -Nrcpad gcc-6.3.0/gcc/generic-match-head.c gcc-6.4.0/gcc/generic-match-head.c *** gcc-6.3.0/gcc/generic-match-head.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/generic-match-head.c Fri May 5 21:52:00 2017 *************** along with GCC; see the file COPYING3. *** 33,38 **** --- 33,39 ---- #include "builtins.h" #include "dumpfile.h" #include "case-cfn-macros.h" + #include "gimplify.h" /* Routine to determine if the types T1 and T2 are effectively diff -Nrcpad gcc-6.3.0/gcc/gengtype-lex.c gcc-6.4.0/gcc/gengtype-lex.c *** gcc-6.3.0/gcc/gengtype-lex.c Wed Dec 21 07:57:50 2016 --- gcc-6.4.0/gcc/gengtype-lex.c Tue Jul 4 07:30:56 2017 *************** *** 9,16 **** #define FLEX_SCANNER #define YY_FLEX_MAJOR_VERSION 2 ! #define YY_FLEX_MINOR_VERSION 6 ! #define YY_FLEX_SUBMINOR_VERSION 0 #if YY_FLEX_SUBMINOR_VERSION > 0 #define FLEX_BETA #endif --- 9,16 ---- #define FLEX_SCANNER #define YY_FLEX_MAJOR_VERSION 2 ! #define YY_FLEX_MINOR_VERSION 5 ! #define YY_FLEX_SUBMINOR_VERSION 37 #if YY_FLEX_SUBMINOR_VERSION > 0 #define FLEX_BETA #endif *************** typedef unsigned int flex_uint32_t; *** 143,157 **** /* Size of default input buffer. */ #ifndef YY_BUF_SIZE - #ifdef __ia64__ - /* On IA-64, the buffer size is 16k, not 8k. - * Moreover, YY_BUF_SIZE is 2*YY_READ_BUF_SIZE in the general case. - * Ditto for the __ia64__ case accordingly. - */ - #define YY_BUF_SIZE 32768 - #else #define YY_BUF_SIZE 16384 - #endif /* __ia64__ */ #endif /* The state buf must be large enough to hold one state per character in the main buffer. --- 143,149 ---- *************** extern FILE *yyin, *yyout; *** 177,190 **** #define EOB_ACT_LAST_MATCH 2 #define YY_LESS_LINENO(n) - #define YY_LINENO_REWIND_TO(ptr) /* Return all but the first "n" matched characters back to the input stream. */ #define yyless(n) \ do \ { \ /* Undo effects of setting up yytext. */ \ ! yy_size_t yyless_macro_arg = (n); \ YY_LESS_LINENO(yyless_macro_arg);\ *yy_cp = (yy_hold_char); \ YY_RESTORE_YY_MORE_OFFSET \ --- 169,181 ---- #define EOB_ACT_LAST_MATCH 2 #define YY_LESS_LINENO(n) /* Return all but the first "n" matched characters back to the input stream. */ #define yyless(n) \ do \ { \ /* Undo effects of setting up yytext. */ \ ! int yyless_macro_arg = (n); \ YY_LESS_LINENO(yyless_macro_arg);\ *yy_cp = (yy_hold_char); \ YY_RESTORE_YY_MORE_OFFSET \ *************** struct yy_buffer_state *** 207,218 **** /* Size of input buffer in bytes, not including room for EOB * characters. */ ! yy_size_t yy_buf_size; /* Number of characters read into yy_ch_buf, not including EOB * characters. */ ! yy_size_t yy_n_chars; /* Whether we "own" the buffer - i.e., we know we created it, * and can realloc() it to grow it, and should free() it to --- 198,209 ---- /* Size of input buffer in bytes, not including room for EOB * characters. */ ! int yy_buf_size; /* Number of characters read into yy_ch_buf, not including EOB * characters. */ ! int yy_n_chars; /* Whether we "own" the buffer - i.e., we know we created it, * and can realloc() it to grow it, and should free() it to *************** static YY_BUFFER_STATE * yy_buffer_stack *** 282,288 **** /* yy_hold_char holds the character lost when yytext is formed. */ static char yy_hold_char; ! static yy_size_t yy_n_chars; /* number of characters read into yy_ch_buf */ yy_size_t yyleng; /* Points to current character in buffer. */ --- 273,279 ---- /* yy_hold_char holds the character lost when yytext is formed. */ static char yy_hold_char; ! static int yy_n_chars; /* number of characters read into yy_ch_buf */ yy_size_t yyleng; /* Points to current character in buffer. */ *************** void yyfree (void * ); *** 343,349 **** /* Begin user sect3 */ ! #define yywrap() (/*CONSTCOND*/1) #define YY_SKIP_YYWRAP typedef unsigned char YY_CHAR; --- 334,340 ---- /* Begin user sect3 */ ! #define yywrap() 1 #define YY_SKIP_YYWRAP typedef unsigned char YY_CHAR; *************** extern int yylineno; *** 357,373 **** int yylineno = 1; extern char *yytext; - #ifdef yytext_ptr - #undef yytext_ptr - #endif #define yytext_ptr yytext static yy_state_type yy_get_previous_state (void ); static yy_state_type yy_try_NUL_trans (yy_state_type current_state ); static int yy_get_next_buffer (void ); - #if defined(__GNUC__) && __GNUC__ >= 3 - __attribute__((__noreturn__)) - #endif static void yy_fatal_error (yyconst char msg[] ); /* Done after the current pattern has been matched and before the --- 348,358 ---- *************** static void yy_fatal_error (yyconst char *** 375,381 **** */ #define YY_DO_BEFORE_ACTION \ (yytext_ptr) = yy_bp; \ ! yyleng = (size_t) (yy_cp - yy_bp); \ (yy_hold_char) = *yy_cp; \ *yy_cp = '\0'; \ (yy_c_buf_p) = yy_cp; --- 360,366 ---- */ #define YY_DO_BEFORE_ACTION \ (yytext_ptr) = yy_bp; \ ! yyleng = (int) (yy_cp - yy_bp); \ (yy_hold_char) = *yy_cp; \ *yy_cp = '\0'; \ (yy_c_buf_p) = yy_cp; *************** static yyconst flex_int16_t yy_accept[56 *** 454,460 **** 0, 45, 0, 0, 0, 0, 0, 0, 0, 0 } ; ! static yyconst YY_CHAR yy_ec[256] = { 0, 1, 1, 1, 1, 1, 1, 1, 1, 2, 3, 2, 2, 2, 1, 1, 1, 1, 1, 1, 1, --- 439,445 ---- 0, 45, 0, 0, 0, 0, 0, 0, 0, 0 } ; ! static yyconst flex_int32_t yy_ec[256] = { 0, 1, 1, 1, 1, 1, 1, 1, 1, 2, 3, 2, 2, 2, 1, 1, 1, 1, 1, 1, 1, *************** static yyconst YY_CHAR yy_ec[256] = *** 486,492 **** 1, 1, 1, 1, 1 } ; ! static yyconst YY_CHAR yy_meta[68] = { 0, 1, 2, 3, 1, 1, 1, 1, 1, 1, 4, 5, 1, 1, 6, 6, 7, 8, 9, 9, 9, --- 471,477 ---- 1, 1, 1, 1, 1 } ; ! static yyconst flex_int32_t yy_meta[68] = { 0, 1, 2, 3, 1, 1, 1, 1, 1, 1, 4, 5, 1, 1, 6, 6, 7, 8, 9, 9, 9, *************** static yyconst YY_CHAR yy_meta[68] = *** 497,503 **** 11, 11, 11, 11, 11, 11, 1 } ; ! static yyconst flex_uint16_t yy_base[608] = { 0, 0, 67, 134, 16, 16, 17, 18, 20, 1232, 2403, 2403, 19, 1191, 19, 31, 41, 43, 32, 33, 34, --- 482,488 ---- 11, 11, 11, 11, 11, 11, 1 } ; ! static yyconst flex_int16_t yy_base[608] = { 0, 0, 67, 134, 16, 16, 17, 18, 20, 1232, 2403, 2403, 19, 1191, 19, 31, 41, 43, 32, 33, 34, *************** static yyconst flex_int16_t yy_def[608] *** 639,645 **** 560, 560, 560, 560, 560, 560, 560 } ; ! static yyconst flex_uint16_t yy_nxt[2471] = { 0, 10, 10, 11, 10, 12, 10, 10, 13, 10, 10, 10, 10, 14, 10, 10, 10, 10, 56, 59, 59, --- 624,630 ---- 560, 560, 560, 560, 560, 560, 560 } ; ! static yyconst flex_int16_t yy_nxt[2471] = { 0, 10, 10, 11, 10, 12, 10, 10, 13, 10, 10, 10, 10, 14, 10, 10, 10, 10, 56, 59, 59, *************** int yy_flex_debug = 0; *** 1203,1209 **** #define YY_MORE_ADJ 0 #define YY_RESTORE_YY_MORE_OFFSET char *yytext; ! #line 1 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" /* -*- indented-text -*- */ /* Process source files and output type information. Copyright (C) 2002-2016 Free Software Foundation, Inc. --- 1188,1194 ---- #define YY_MORE_ADJ 0 #define YY_RESTORE_YY_MORE_OFFSET char *yytext; ! #line 1 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" /* -*- indented-text -*- */ /* Process source files and output type information. Copyright (C) 2002-2016 Free Software Foundation, Inc. *************** You should have received a copy of the G *** 1224,1230 **** along with GCC; see the file COPYING3. If not see . */ #define YY_NO_INPUT 1 ! #line 24 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" #ifdef HOST_GENERATOR_FILE #include "config.h" #define GENERATOR_FILE 1 --- 1209,1215 ---- along with GCC; see the file COPYING3. If not see . */ #define YY_NO_INPUT 1 ! #line 24 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" #ifdef HOST_GENERATOR_FILE #include "config.h" #define GENERATOR_FILE 1 *************** update_lineno (const char *l, size_t len *** 1254,1260 **** /* Include '::' in identifiers to capture C++ scope qualifiers. */ ! #line 1257 "gengtype-lex.c" #define INITIAL 0 #define in_struct 1 --- 1239,1245 ---- /* Include '::' in identifiers to capture C++ scope qualifiers. */ ! #line 1242 "gengtype-lex.c" #define INITIAL 0 #define in_struct 1 *************** void yyset_extra (YY_EXTRA_TYPE user_def *** 1290,1300 **** FILE *yyget_in (void ); ! void yyset_in (FILE * _in_str ); FILE *yyget_out (void ); ! void yyset_out (FILE * _out_str ); yy_size_t yyget_leng (void ); --- 1275,1285 ---- FILE *yyget_in (void ); ! void yyset_in (FILE * in_str ); FILE *yyget_out (void ); ! void yyset_out (FILE * out_str ); yy_size_t yyget_leng (void ); *************** char *yyget_text (void ); *** 1302,1308 **** int yyget_lineno (void ); ! void yyset_lineno (int _line_number ); /* Macros after this point can all be overridden by user definitions in * section 1. --- 1287,1293 ---- int yyget_lineno (void ); ! void yyset_lineno (int line_number ); /* Macros after this point can all be overridden by user definitions in * section 1. *************** extern int yywrap (void ); *** 1316,1325 **** #endif #endif - #ifndef YY_NO_UNPUT - - #endif - #ifndef yytext_ptr static void yy_flex_strncpy (char *,yyconst char *,int ); #endif --- 1301,1306 ---- *************** static int input (void ); *** 1340,1351 **** /* Amount of stuff to slurp up with each read. */ #ifndef YY_READ_BUF_SIZE - #ifdef __ia64__ - /* On IA-64, the buffer size is 16k, not 8k */ - #define YY_READ_BUF_SIZE 16384 - #else #define YY_READ_BUF_SIZE 8192 - #endif /* __ia64__ */ #endif /* Copy whatever the last rule matched to the standard output. */ --- 1321,1327 ---- *************** static int input (void ); *** 1377,1383 **** else \ { \ errno=0; \ ! while ( (result = fread(buf, 1, max_size, yyin))==0 && ferror(yyin)) \ { \ if( errno != EINTR) \ { \ --- 1353,1359 ---- else \ { \ errno=0; \ ! while ( (result = (int) fread(buf, 1, max_size, yyin))==0 && ferror(yyin)) \ { \ if( errno != EINTR) \ { \ *************** extern int yylex (void); *** 1432,1438 **** /* Code executed at the end of each rule. */ #ifndef YY_BREAK ! #define YY_BREAK /*LINTED*/break; #endif #define YY_RULE_SETUP \ --- 1408,1414 ---- /* Code executed at the end of each rule. */ #ifndef YY_BREAK ! #define YY_BREAK break; #endif #define YY_RULE_SETUP \ *************** extern int yylex (void); *** 1445,1454 **** */ YY_DECL { ! yy_state_type yy_current_state; ! char *yy_cp, *yy_bp; ! int yy_act; if ( !(yy_init) ) { (yy_init) = 1; --- 1421,1443 ---- */ YY_DECL { ! register yy_state_type yy_current_state; ! register char *yy_cp, *yy_bp; ! register int yy_act; + #line 66 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" + + /* Do this on entry to yylex(): */ + *yylval = 0; + if (lexer_toplevel_done) + { + BEGIN(INITIAL); + lexer_toplevel_done = 0; + } + + /* Things we look for in skipping mode: */ + #line 1439 "gengtype-lex.c" + if ( !(yy_init) ) { (yy_init) = 1; *************** YY_DECL *** 1475,1495 **** yy_load_buffer_state( ); } ! { ! #line 66 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" ! ! /* Do this on entry to yylex(): */ ! *yylval = 0; ! if (lexer_toplevel_done) ! { ! BEGIN(INITIAL); ! lexer_toplevel_done = 0; ! } ! ! /* Things we look for in skipping mode: */ ! #line 1490 "gengtype-lex.c" ! ! while ( /*CONSTCOND*/1 ) /* loops until end-of-file is reached */ { yy_cp = (yy_c_buf_p); --- 1464,1470 ---- yy_load_buffer_state( ); } ! while ( 1 ) /* loops until end-of-file is reached */ { yy_cp = (yy_c_buf_p); *************** YY_DECL *** 1506,1512 **** yy_match: do { ! YY_CHAR yy_c = yy_ec[YY_SC_TO_UI(*yy_cp)] ; if ( yy_accept[yy_current_state] ) { (yy_last_accepting_state) = yy_current_state; --- 1481,1487 ---- yy_match: do { ! register YY_CHAR yy_c = yy_ec[YY_SC_TO_UI(*yy_cp)]; if ( yy_accept[yy_current_state] ) { (yy_last_accepting_state) = yy_current_state; *************** yy_match: *** 1518,1524 **** if ( yy_current_state >= 561 ) yy_c = yy_meta[(unsigned int) yy_c]; } ! yy_current_state = yy_nxt[yy_base[yy_current_state] + (unsigned int) yy_c]; ++yy_cp; } while ( yy_current_state != 560 ); --- 1493,1499 ---- if ( yy_current_state >= 561 ) yy_c = yy_meta[(unsigned int) yy_c]; } ! yy_current_state = yy_nxt[yy_base[yy_current_state] + (flex_int16_t) yy_c]; ++yy_cp; } while ( yy_current_state != 560 ); *************** do_action: /* This label is used only to *** 1544,1554 **** case 1: /* rule 1 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 77 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return TYPEDEF; --- 1519,1528 ---- case 1: /* rule 1 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 77 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return TYPEDEF; *************** YY_RULE_SETUP *** 1557,1567 **** case 2: /* rule 2 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 81 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return STRUCT; --- 1531,1540 ---- case 2: /* rule 2 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 81 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return STRUCT; *************** YY_RULE_SETUP *** 1570,1580 **** case 3: /* rule 3 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 85 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return UNION; --- 1543,1552 ---- case 3: /* rule 3 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 85 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return UNION; *************** YY_RULE_SETUP *** 1583,1593 **** case 4: /* rule 4 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 89 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return STRUCT; --- 1555,1564 ---- case 4: /* rule 4 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 89 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return STRUCT; *************** YY_RULE_SETUP *** 1596,1606 **** case 5: /* rule 5 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 93 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return EXTERN; --- 1567,1576 ---- case 5: /* rule 5 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 93 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return EXTERN; *************** YY_RULE_SETUP *** 1609,1619 **** case 6: /* rule 6 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 97 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return STATIC; --- 1579,1588 ---- case 6: /* rule 6 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 97 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct); return STATIC; *************** YY_RULE_SETUP *** 1624,1677 **** case 7: YY_RULE_SETUP ! #line 105 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct_comment); } YY_BREAK case 8: /* rule 8 can match eol */ YY_RULE_SETUP ! #line 106 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 9: /* rule 9 can match eol */ YY_RULE_SETUP ! #line 108 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { update_lineno (yytext, yyleng); } YY_BREAK case 10: /* rule 10 can match eol */ YY_RULE_SETUP ! #line 109 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 11: /* rule 11 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 5); (yy_c_buf_p) = yy_cp = yy_bp + 5; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 111 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" /* don't care */ YY_BREAK case 12: /* rule 12 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ ! #line 113 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 13: /* rule 13 can match eol */ ! #line 114 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 14: /* rule 14 can match eol */ ! #line 115 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 15: /* rule 15 can match eol */ YY_RULE_SETUP ! #line 115 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext, yyleng, yyleng + 1); return IGNORABLE_CXX_KEYWORD; --- 1593,1644 ---- case 7: YY_RULE_SETUP ! #line 105 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct_comment); } YY_BREAK case 8: /* rule 8 can match eol */ YY_RULE_SETUP ! #line 106 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 9: /* rule 9 can match eol */ YY_RULE_SETUP ! #line 108 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { update_lineno (yytext, yyleng); } YY_BREAK case 10: /* rule 10 can match eol */ YY_RULE_SETUP ! #line 109 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 11: /* rule 11 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 5; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 111 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" /* don't care */ YY_BREAK case 12: /* rule 12 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ ! #line 113 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 13: /* rule 13 can match eol */ ! #line 114 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 14: /* rule 14 can match eol */ ! #line 115 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 15: /* rule 15 can match eol */ YY_RULE_SETUP ! #line 115 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext, yyleng, yyleng + 1); return IGNORABLE_CXX_KEYWORD; *************** YY_RULE_SETUP *** 1680,1788 **** case 16: /* rule 16 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 3); (yy_c_buf_p) = yy_cp = yy_bp + 3; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 119 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return GTY_TOKEN; } YY_BREAK case 17: /* rule 17 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 5); (yy_c_buf_p) = yy_cp = yy_bp + 5; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 120 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return UNION; } YY_BREAK case 18: /* rule 18 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 6); (yy_c_buf_p) = yy_cp = yy_bp + 6; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 121 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return STRUCT; } YY_BREAK case 19: /* rule 19 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 5); (yy_c_buf_p) = yy_cp = yy_bp + 5; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 122 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return STRUCT; } YY_BREAK case 20: /* rule 20 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 7); (yy_c_buf_p) = yy_cp = yy_bp + 7; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 123 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return TYPEDEF; } YY_BREAK case 21: /* rule 21 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 4); (yy_c_buf_p) = yy_cp = yy_bp + 4; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 124 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return ENUM; } YY_BREAK case 22: /* rule 22 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 9); (yy_c_buf_p) = yy_cp = yy_bp + 9; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 125 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return PTR_ALIAS; } YY_BREAK case 23: /* rule 23 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 10); (yy_c_buf_p) = yy_cp = yy_bp + 10; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 126 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return NESTED_PTR; } YY_BREAK case 24: /* rule 24 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 4); (yy_c_buf_p) = yy_cp = yy_bp + 4; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 127 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return USER_GTY; } YY_BREAK case 25: YY_RULE_SETUP ! #line 128 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return NUM; } YY_BREAK case 26: /* rule 26 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ ! #line 131 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 27: /* rule 27 can match eol */ YY_RULE_SETUP ! #line 131 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { size_t len; --- 1647,1745 ---- case 16: /* rule 16 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 3; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 119 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return GTY_TOKEN; } YY_BREAK case 17: /* rule 17 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 5; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 120 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return UNION; } YY_BREAK case 18: /* rule 18 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 6; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 121 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return STRUCT; } YY_BREAK case 19: /* rule 19 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 5; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 122 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return STRUCT; } YY_BREAK case 20: /* rule 20 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 7; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 123 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return TYPEDEF; } YY_BREAK case 21: /* rule 21 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 4; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 124 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return ENUM; } YY_BREAK case 22: /* rule 22 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 9; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 125 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return PTR_ALIAS; } YY_BREAK case 23: /* rule 23 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 10; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 126 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return NESTED_PTR; } YY_BREAK case 24: /* rule 24 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 4; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 127 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return USER_GTY; } YY_BREAK case 25: YY_RULE_SETUP ! #line 128 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return NUM; } YY_BREAK case 26: /* rule 26 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ ! #line 131 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 27: /* rule 27 can match eol */ YY_RULE_SETUP ! #line 131 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { size_t len; *************** YY_RULE_SETUP *** 1797,1807 **** case 28: /* rule 28 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_cp - 1); (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 142 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext, yyleng, yyleng+1); return ID; --- 1754,1763 ---- case 28: /* rule 28 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp -= 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 142 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext, yyleng, yyleng+1); return ID; *************** YY_RULE_SETUP *** 1810,1816 **** case 29: /* rule 29 can match eol */ YY_RULE_SETUP ! #line 147 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext+1, yyleng-2, yyleng-1); return STRING; --- 1766,1772 ---- case 29: /* rule 29 can match eol */ YY_RULE_SETUP ! #line 147 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext+1, yyleng-2, yyleng-1); return STRING; *************** YY_RULE_SETUP *** 1820,1826 **** case 30: /* rule 30 can match eol */ YY_RULE_SETUP ! #line 152 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext+1, yyleng-2, yyleng-1); return ARRAY; --- 1776,1782 ---- case 30: /* rule 30 can match eol */ YY_RULE_SETUP ! #line 152 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext+1, yyleng-2, yyleng-1); return ARRAY; *************** YY_RULE_SETUP *** 1829,1835 **** case 31: /* rule 31 can match eol */ YY_RULE_SETUP ! #line 156 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext+1, yyleng-2, yyleng); return CHAR; --- 1785,1791 ---- case 31: /* rule 31 can match eol */ YY_RULE_SETUP ! #line 156 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { *yylval = XDUPVAR (const char, yytext+1, yyleng-2, yyleng); return CHAR; *************** YY_RULE_SETUP *** 1837,1860 **** YY_BREAK case 32: YY_RULE_SETUP ! #line 161 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return ELLIPSIS; } YY_BREAK case 33: YY_RULE_SETUP ! #line 162 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { return yytext[0]; } YY_BREAK /* ignore pp-directives */ case 34: /* rule 34 can match eol */ YY_RULE_SETUP ! #line 165 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" {lexer_line.line++;} YY_BREAK case 35: YY_RULE_SETUP ! #line 167 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { error_at_line (&lexer_line, "unexpected character `%s'", yytext); } --- 1793,1816 ---- YY_BREAK case 32: YY_RULE_SETUP ! #line 161 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return ELLIPSIS; } YY_BREAK case 33: YY_RULE_SETUP ! #line 162 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { return yytext[0]; } YY_BREAK /* ignore pp-directives */ case 34: /* rule 34 can match eol */ YY_RULE_SETUP ! #line 165 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" {lexer_line.line++;} YY_BREAK case 35: YY_RULE_SETUP ! #line 167 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { error_at_line (&lexer_line, "unexpected character `%s'", yytext); } *************** YY_RULE_SETUP *** 1862,1949 **** case 36: YY_RULE_SETUP ! #line 172 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_comment); } YY_BREAK case 37: /* rule 37 can match eol */ YY_RULE_SETUP ! #line 173 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 38: /* rule 38 can match eol */ YY_RULE_SETUP ! #line 174 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 39: ! #line 176 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 40: /* rule 40 can match eol */ ! #line 177 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 41: /* rule 41 can match eol */ YY_RULE_SETUP ! #line 177 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 42: /* rule 42 can match eol */ YY_RULE_SETUP ! #line 178 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { update_lineno (yytext, yyleng); } YY_BREAK case 43: /* rule 43 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 1); (yy_c_buf_p) = yy_cp = yy_bp + 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 179 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 44: /* rule 44 can match eol */ YY_RULE_SETUP ! #line 182 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 45: ! #line 184 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 46: YY_RULE_SETUP ! #line 184 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 47: /* rule 47 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ - YY_LINENO_REWIND_TO(yy_bp + 1); (yy_c_buf_p) = yy_cp = yy_bp + 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 185 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 48: YY_RULE_SETUP ! #line 188 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(INITIAL); } YY_BREAK case 49: YY_RULE_SETUP ! #line 189 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { BEGIN(in_struct); } YY_BREAK case 50: ! #line 192 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" case 51: YY_RULE_SETUP ! #line 192 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" { error_at_line (&lexer_line, "unterminated comment or string; unexpected EOF"); --- 1818,1903 ---- case 36: YY_RULE_SETUP ! #line 172 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_comment); } YY_BREAK case 37: /* rule 37 can match eol */ YY_RULE_SETUP ! #line 173 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 38: /* rule 38 can match eol */ YY_RULE_SETUP ! #line 174 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 39: ! #line 176 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 40: /* rule 40 can match eol */ ! #line 177 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 41: /* rule 41 can match eol */ YY_RULE_SETUP ! #line 177 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 42: /* rule 42 can match eol */ YY_RULE_SETUP ! #line 178 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { update_lineno (yytext, yyleng); } YY_BREAK case 43: /* rule 43 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 179 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 44: /* rule 44 can match eol */ YY_RULE_SETUP ! #line 182 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { lexer_line.line++; } YY_BREAK case 45: ! #line 184 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 46: YY_RULE_SETUP ! #line 184 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 47: /* rule 47 can match eol */ *yy_cp = (yy_hold_char); /* undo effects of setting up yytext */ (yy_c_buf_p) = yy_cp = yy_bp + 1; YY_DO_BEFORE_ACTION; /* set up yytext again */ YY_RULE_SETUP ! #line 185 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 48: YY_RULE_SETUP ! #line 188 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(INITIAL); } YY_BREAK case 49: YY_RULE_SETUP ! #line 189 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { BEGIN(in_struct); } YY_BREAK case 50: ! #line 192 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" case 51: YY_RULE_SETUP ! #line 192 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" { error_at_line (&lexer_line, "unterminated comment or string; unexpected EOF"); *************** YY_RULE_SETUP *** 1952,1966 **** case 52: /* rule 52 can match eol */ YY_RULE_SETUP ! #line 197 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 53: YY_RULE_SETUP ! #line 199 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" YY_FATAL_ERROR( "flex scanner jammed" ); YY_BREAK ! #line 1963 "gengtype-lex.c" case YY_STATE_EOF(INITIAL): case YY_STATE_EOF(in_struct): case YY_STATE_EOF(in_struct_comment): --- 1906,1920 ---- case 52: /* rule 52 can match eol */ YY_RULE_SETUP ! #line 197 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" /* do nothing */ YY_BREAK case 53: YY_RULE_SETUP ! #line 199 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" YY_FATAL_ERROR( "flex scanner jammed" ); YY_BREAK ! #line 1917 "gengtype-lex.c" case YY_STATE_EOF(INITIAL): case YY_STATE_EOF(in_struct): case YY_STATE_EOF(in_struct_comment): *************** case YY_STATE_EOF(in_comment): *** 2095,2101 **** "fatal flex scanner internal error--no action found" ); } /* end of action switch */ } /* end of scanning one token */ - } /* end of user's declarations */ } /* end of yylex */ /* yy_get_next_buffer - try to read in a new buffer --- 2049,2054 ---- *************** case YY_STATE_EOF(in_comment): *** 2107,2115 **** */ static int yy_get_next_buffer (void) { ! char *dest = YY_CURRENT_BUFFER_LVALUE->yy_ch_buf; ! char *source = (yytext_ptr); ! yy_size_t number_to_move, i; int ret_val; if ( (yy_c_buf_p) > &YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[(yy_n_chars) + 1] ) --- 2060,2068 ---- */ static int yy_get_next_buffer (void) { ! register char *dest = YY_CURRENT_BUFFER_LVALUE->yy_ch_buf; ! register char *source = (yytext_ptr); ! register int number_to_move, i; int ret_val; if ( (yy_c_buf_p) > &YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[(yy_n_chars) + 1] ) *************** static int yy_get_next_buffer (void) *** 2138,2144 **** /* Try to read more data. */ /* First move last chars to start of buffer. */ ! number_to_move = (yy_size_t) ((yy_c_buf_p) - (yytext_ptr)) - 1; for ( i = 0; i < number_to_move; ++i ) *(dest++) = *(source++); --- 2091,2097 ---- /* Try to read more data. */ /* First move last chars to start of buffer. */ ! number_to_move = (int) ((yy_c_buf_p) - (yytext_ptr)) - 1; for ( i = 0; i < number_to_move; ++i ) *(dest++) = *(source++); *************** static int yy_get_next_buffer (void) *** 2186,2192 **** (yy_c_buf_p) = &b->yy_ch_buf[yy_c_buf_p_offset]; ! num_to_read = YY_CURRENT_BUFFER_LVALUE->yy_buf_size - number_to_move - 1; } --- 2139,2145 ---- (yy_c_buf_p) = &b->yy_ch_buf[yy_c_buf_p_offset]; ! num_to_read = (int) YY_CURRENT_BUFFER_LVALUE->yy_buf_size - number_to_move - 1; } *************** static int yy_get_next_buffer (void) *** 2220,2228 **** else ret_val = EOB_ACT_CONTINUE_SCAN; ! if ((yy_size_t) ((yy_n_chars) + number_to_move) > YY_CURRENT_BUFFER_LVALUE->yy_buf_size) { /* Extend the array by 50%, plus the number we really need. */ ! yy_size_t new_size = (yy_n_chars) + number_to_move + ((yy_n_chars) >> 1); YY_CURRENT_BUFFER_LVALUE->yy_ch_buf = (char *) yyrealloc((void *) YY_CURRENT_BUFFER_LVALUE->yy_ch_buf,new_size ); if ( ! YY_CURRENT_BUFFER_LVALUE->yy_ch_buf ) YY_FATAL_ERROR( "out of dynamic memory in yy_get_next_buffer()" ); --- 2173,2181 ---- else ret_val = EOB_ACT_CONTINUE_SCAN; ! if ((int) ((yy_n_chars) + number_to_move) > YY_CURRENT_BUFFER_LVALUE->yy_buf_size) { /* Extend the array by 50%, plus the number we really need. */ ! int new_size = (yy_n_chars) + number_to_move + ((yy_n_chars) >> 1); YY_CURRENT_BUFFER_LVALUE->yy_ch_buf = (char *) yyrealloc((void *) YY_CURRENT_BUFFER_LVALUE->yy_ch_buf,new_size ); if ( ! YY_CURRENT_BUFFER_LVALUE->yy_ch_buf ) YY_FATAL_ERROR( "out of dynamic memory in yy_get_next_buffer()" ); *************** static int yy_get_next_buffer (void) *** 2241,2255 **** static yy_state_type yy_get_previous_state (void) { ! yy_state_type yy_current_state; ! char *yy_cp; yy_current_state = (yy_start); yy_current_state += YY_AT_BOL(); for ( yy_cp = (yytext_ptr) + YY_MORE_ADJ; yy_cp < (yy_c_buf_p); ++yy_cp ) { ! YY_CHAR yy_c = (*yy_cp ? yy_ec[YY_SC_TO_UI(*yy_cp)] : 1); if ( yy_accept[yy_current_state] ) { (yy_last_accepting_state) = yy_current_state; --- 2194,2208 ---- static yy_state_type yy_get_previous_state (void) { ! register yy_state_type yy_current_state; ! register char *yy_cp; yy_current_state = (yy_start); yy_current_state += YY_AT_BOL(); for ( yy_cp = (yytext_ptr) + YY_MORE_ADJ; yy_cp < (yy_c_buf_p); ++yy_cp ) { ! register YY_CHAR yy_c = (*yy_cp ? yy_ec[YY_SC_TO_UI(*yy_cp)] : 1); if ( yy_accept[yy_current_state] ) { (yy_last_accepting_state) = yy_current_state; *************** static int yy_get_next_buffer (void) *** 2261,2267 **** if ( yy_current_state >= 561 ) yy_c = yy_meta[(unsigned int) yy_c]; } ! yy_current_state = yy_nxt[yy_base[yy_current_state] + (unsigned int) yy_c]; } return yy_current_state; --- 2214,2220 ---- if ( yy_current_state >= 561 ) yy_c = yy_meta[(unsigned int) yy_c]; } ! yy_current_state = yy_nxt[yy_base[yy_current_state] + (flex_int16_t) yy_c]; } return yy_current_state; *************** static int yy_get_next_buffer (void) *** 2274,2283 **** */ static yy_state_type yy_try_NUL_trans (yy_state_type yy_current_state ) { ! int yy_is_jam; ! char *yy_cp = (yy_c_buf_p); ! YY_CHAR yy_c = 1; if ( yy_accept[yy_current_state] ) { (yy_last_accepting_state) = yy_current_state; --- 2227,2236 ---- */ static yy_state_type yy_try_NUL_trans (yy_state_type yy_current_state ) { ! register int yy_is_jam; ! register char *yy_cp = (yy_c_buf_p); ! register YY_CHAR yy_c = 1; if ( yy_accept[yy_current_state] ) { (yy_last_accepting_state) = yy_current_state; *************** static int yy_get_next_buffer (void) *** 2289,2304 **** if ( yy_current_state >= 561 ) yy_c = yy_meta[(unsigned int) yy_c]; } ! yy_current_state = yy_nxt[yy_base[yy_current_state] + (unsigned int) yy_c]; yy_is_jam = (yy_current_state == 560); return yy_is_jam ? 0 : yy_current_state; } - #ifndef YY_NO_UNPUT - - #endif - #ifndef YY_NO_INPUT #ifdef __cplusplus static int yyinput (void) --- 2242,2253 ---- if ( yy_current_state >= 561 ) yy_c = yy_meta[(unsigned int) yy_c]; } ! yy_current_state = yy_nxt[yy_base[yy_current_state] + (flex_int16_t) yy_c]; yy_is_jam = (yy_current_state == 560); return yy_is_jam ? 0 : yy_current_state; } #ifndef YY_NO_INPUT #ifdef __cplusplus static int yyinput (void) *************** static void yy_load_buffer_state (void) *** 2450,2456 **** if ( ! b ) YY_FATAL_ERROR( "out of dynamic memory in yy_create_buffer()" ); ! b->yy_buf_size = (yy_size_t)size; /* yy_ch_buf has to be 2 characters longer than the size given because * we need to put in 2 end-of-buffer characters. --- 2399,2405 ---- if ( ! b ) YY_FATAL_ERROR( "out of dynamic memory in yy_create_buffer()" ); ! b->yy_buf_size = size; /* yy_ch_buf has to be 2 characters longer than the size given because * we need to put in 2 end-of-buffer characters. *************** static void yyensure_buffer_stack (void) *** 2605,2611 **** * scanner will even need a stack. We use 2 instead of 1 to avoid an * immediate realloc on the next call. */ ! num_to_alloc = 1; /* After all that talk, this was set to 1 anyways... */ (yy_buffer_stack) = (struct yy_buffer_state**)yyalloc (num_to_alloc * sizeof(struct yy_buffer_state*) ); --- 2554,2560 ---- * scanner will even need a stack. We use 2 instead of 1 to avoid an * immediate realloc on the next call. */ ! num_to_alloc = 1; (yy_buffer_stack) = (struct yy_buffer_state**)yyalloc (num_to_alloc * sizeof(struct yy_buffer_state*) ); *************** static void yyensure_buffer_stack (void) *** 2622,2628 **** if ((yy_buffer_stack_top) >= ((yy_buffer_stack_max)) - 1){ /* Increase the buffer to prepare for a possible push. */ ! yy_size_t grow_size = 8 /* arbitrary grow size */; num_to_alloc = (yy_buffer_stack_max) + grow_size; (yy_buffer_stack) = (struct yy_buffer_state**)yyrealloc --- 2571,2577 ---- if ((yy_buffer_stack_top) >= ((yy_buffer_stack_max)) - 1){ /* Increase the buffer to prepare for a possible push. */ ! int grow_size = 8 /* arbitrary grow size */; num_to_alloc = (yy_buffer_stack_max) + grow_size; (yy_buffer_stack) = (struct yy_buffer_state**)yyrealloc *************** YY_BUFFER_STATE yy_scan_buffer (char * *** 2684,2690 **** YY_BUFFER_STATE yy_scan_string (yyconst char * yystr ) { ! return yy_scan_bytes(yystr,strlen(yystr) ); } /** Setup the input buffer state to scan the given bytes. The next call to yylex() will --- 2633,2639 ---- YY_BUFFER_STATE yy_scan_string (yyconst char * yystr ) { ! return yy_scan_bytes(yystr,(int) strlen(yystr) ); } /** Setup the input buffer state to scan the given bytes. The next call to yylex() will *************** YY_BUFFER_STATE yy_scan_bytes (yyconst *** 2699,2708 **** YY_BUFFER_STATE b; char *buf; yy_size_t n; ! yy_size_t i; /* Get memory for full buffer, including space for trailing EOB's. */ ! n = _yybytes_len + 2; buf = (char *) yyalloc(n ); if ( ! buf ) YY_FATAL_ERROR( "out of dynamic memory in yy_scan_bytes()" ); --- 2648,2657 ---- YY_BUFFER_STATE b; char *buf; yy_size_t n; ! int i; /* Get memory for full buffer, including space for trailing EOB's. */ ! n = (yy_size_t) _yybytes_len + 2; buf = (char *) yyalloc(n ); if ( ! buf ) YY_FATAL_ERROR( "out of dynamic memory in yy_scan_bytes()" ); *************** YY_BUFFER_STATE yy_scan_bytes (yyconst *** 2730,2736 **** static void yy_fatal_error (yyconst char* msg ) { ! (void) fprintf( stderr, "%s\n", msg ); exit( YY_EXIT_FAILURE ); } --- 2679,2685 ---- static void yy_fatal_error (yyconst char* msg ) { ! (void) fprintf( stderr, "%s\n", msg ); exit( YY_EXIT_FAILURE ); } *************** static void yy_fatal_error (yyconst char *** 2741,2747 **** do \ { \ /* Undo effects of setting up yytext. */ \ ! yy_size_t yyless_macro_arg = (n); \ YY_LESS_LINENO(yyless_macro_arg);\ yytext[yyleng] = (yy_hold_char); \ (yy_c_buf_p) = yytext + yyless_macro_arg; \ --- 2690,2696 ---- do \ { \ /* Undo effects of setting up yytext. */ \ ! int yyless_macro_arg = (n); \ YY_LESS_LINENO(yyless_macro_arg);\ yytext[yyleng] = (yy_hold_char); \ (yy_c_buf_p) = yytext + yyless_macro_arg; \ *************** char *yyget_text (void) *** 2796,2824 **** } /** Set the current line number. ! * @param _line_number line number * */ ! void yyset_lineno (int _line_number ) { ! yylineno = _line_number; } /** Set the input stream. This does not discard the current * input buffer. ! * @param _in_str A readable stream. * * @see yy_switch_to_buffer */ ! void yyset_in (FILE * _in_str ) { ! yyin = _in_str ; } ! void yyset_out (FILE * _out_str ) { ! yyout = _out_str ; } int yyget_debug (void) --- 2745,2773 ---- } /** Set the current line number. ! * @param line_number * */ ! void yyset_lineno (int line_number ) { ! yylineno = line_number; } /** Set the input stream. This does not discard the current * input buffer. ! * @param in_str A readable stream. * * @see yy_switch_to_buffer */ ! void yyset_in (FILE * in_str ) { ! yyin = in_str ; } ! void yyset_out (FILE * out_str ) { ! yyout = out_str ; } int yyget_debug (void) *************** int yyget_debug (void) *** 2826,2834 **** return yy_flex_debug; } ! void yyset_debug (int _bdebug ) { ! yy_flex_debug = _bdebug ; } static int yy_init_globals (void) --- 2775,2783 ---- return yy_flex_debug; } ! void yyset_debug (int bdebug ) { ! yy_flex_debug = bdebug ; } static int yy_init_globals (void) *************** int yylex_destroy (void) *** 2888,2895 **** #ifndef yytext_ptr static void yy_flex_strncpy (char* s1, yyconst char * s2, int n ) { ! ! int i; for ( i = 0; i < n; ++i ) s1[i] = s2[i]; } --- 2837,2843 ---- #ifndef yytext_ptr static void yy_flex_strncpy (char* s1, yyconst char * s2, int n ) { ! register int i; for ( i = 0; i < n; ++i ) s1[i] = s2[i]; } *************** static void yy_flex_strncpy (char* s1, y *** 2898,2904 **** #ifdef YY_NEED_STRLEN static int yy_flex_strlen (yyconst char * s ) { ! int n; for ( n = 0; s[n]; ++n ) ; --- 2846,2852 ---- #ifdef YY_NEED_STRLEN static int yy_flex_strlen (yyconst char * s ) { ! register int n; for ( n = 0; s[n]; ++n ) ; *************** static int yy_flex_strlen (yyconst char *** 2908,2919 **** void *yyalloc (yy_size_t size ) { ! return (void *) malloc( size ); } void *yyrealloc (void * ptr, yy_size_t size ) { - /* The cast to (char *) in the following accommodates both * implementations that use char* generic pointers, and those * that use void* generic pointers. It works with the latter --- 2856,2866 ---- void *yyalloc (yy_size_t size ) { ! return (void *) malloc( size ); } void *yyrealloc (void * ptr, yy_size_t size ) { /* The cast to (char *) in the following accommodates both * implementations that use char* generic pointers, and those * that use void* generic pointers. It works with the latter *************** void *yyrealloc (void * ptr, yy_size_t *** 2926,2937 **** void yyfree (void * ptr ) { ! free( (char *) ptr ); /* see yyrealloc() for (char *) cast */ } #define YYTABLES_NAME "yytables" ! #line 199 "/d/gcc-6.3.0/gcc-6.3.0/gcc/gengtype-lex.l" --- 2873,2884 ---- void yyfree (void * ptr ) { ! free( (char *) ptr ); /* see yyrealloc() for (char *) cast */ } #define YYTABLES_NAME "yytables" ! #line 199 "/space/rguenther/gcc-6.4.0/gcc-6.4.0/gcc/gengtype-lex.l" diff -Nrcpad gcc-6.3.0/gcc/genmatch.c gcc-6.4.0/gcc/genmatch.c *** gcc-6.3.0/gcc/genmatch.c Fri Apr 22 11:08:16 2016 --- gcc-6.4.0/gcc/genmatch.c Fri May 5 21:52:00 2017 *************** capture::gen_transform (FILE *f, int ind *** 2389,2395 **** } } ! fprintf_indent (f, indent, "%s = captures[%u];\n", dest, where); /* ??? Stupid tcc_comparison GENERIC trees in COND_EXPRs. Deal with substituting a capture of that. */ --- 2389,2406 ---- } } ! /* If in GENERIC some capture is used multiple times, unshare it except ! when emitting the last use. */ ! if (!gimple ! && cinfo->info.exists () ! && cinfo->info[cinfo->info[where].same_as].result_use_count > 1) ! { ! fprintf_indent (f, indent, "%s = unshare_expr (captures[%u]);\n", ! dest, where); ! cinfo->info[cinfo->info[where].same_as].result_use_count--; ! } ! else ! fprintf_indent (f, indent, "%s = captures[%u];\n", dest, where); /* ??? Stupid tcc_comparison GENERIC trees in COND_EXPRs. Deal with substituting a capture of that. */ diff -Nrcpad gcc-6.3.0/gcc/gimple-expr.c gcc-6.4.0/gcc/gimple-expr.c *** gcc-6.3.0/gcc/gimple-expr.c Fri Mar 11 12:28:50 2016 --- gcc-6.4.0/gcc/gimple-expr.c Tue Mar 14 12:57:08 2017 *************** useless_type_conversion_p (tree outer_ty *** 123,129 **** /* Fixed point types with the same mode are compatible. */ else if (FIXED_POINT_TYPE_P (inner_type) && FIXED_POINT_TYPE_P (outer_type)) ! return true; /* We need to take special care recursing to pointed-to types. */ else if (POINTER_TYPE_P (inner_type) --- 123,129 ---- /* Fixed point types with the same mode are compatible. */ else if (FIXED_POINT_TYPE_P (inner_type) && FIXED_POINT_TYPE_P (outer_type)) ! return TYPE_SATURATING (inner_type) == TYPE_SATURATING (outer_type); /* We need to take special care recursing to pointed-to types. */ else if (POINTER_TYPE_P (inner_type) diff -Nrcpad gcc-6.3.0/gcc/gimple-fold.c gcc-6.4.0/gcc/gimple-fold.c *** gcc-6.3.0/gcc/gimple-fold.c Tue Sep 27 10:54:00 2016 --- gcc-6.4.0/gcc/gimple-fold.c Mon May 15 07:53:37 2017 *************** fold_ctor_reference (tree type, tree cto *** 5506,5514 **** && !compare_tree_int (TYPE_SIZE (TREE_TYPE (ctor)), size)) { ret = canonicalize_constructor_val (unshare_expr (ctor), from_decl); - ret = fold_unary (VIEW_CONVERT_EXPR, type, ret); if (ret) ! STRIP_USELESS_TYPE_CONVERSION (ret); return ret; } /* For constants and byte-aligned/sized reads try to go through --- 5506,5517 ---- && !compare_tree_int (TYPE_SIZE (TREE_TYPE (ctor)), size)) { ret = canonicalize_constructor_val (unshare_expr (ctor), from_decl); if (ret) ! { ! ret = fold_unary (VIEW_CONVERT_EXPR, type, ret); ! if (ret) ! STRIP_USELESS_TYPE_CONVERSION (ret); ! } return ret; } /* For constants and byte-aligned/sized reads try to go through diff -Nrcpad gcc-6.3.0/gcc/gimple.c gcc-6.4.0/gcc/gimple.c *** gcc-6.3.0/gcc/gimple.c Fri Jun 10 09:45:51 2016 --- gcc-6.4.0/gcc/gimple.c Tue Mar 14 12:57:08 2017 *************** gimple_builtin_call_types_compatible_p ( *** 2487,2493 **** if (!targs) return true; tree arg = gimple_call_arg (stmt, i); ! if (!useless_type_conversion_p (TREE_VALUE (targs), TREE_TYPE (arg))) return false; targs = TREE_CHAIN (targs); } --- 2487,2502 ---- if (!targs) return true; tree arg = gimple_call_arg (stmt, i); ! tree type = TREE_VALUE (targs); ! if (!useless_type_conversion_p (type, TREE_TYPE (arg)) ! /* char/short integral arguments are promoted to int ! by several frontends if targetm.calls.promote_prototypes ! is true. Allow such promotion too. */ ! && !(INTEGRAL_TYPE_P (type) ! && TYPE_PRECISION (type) < TYPE_PRECISION (integer_type_node) ! && targetm.calls.promote_prototypes (TREE_TYPE (fndecl)) ! && useless_type_conversion_p (integer_type_node, ! TREE_TYPE (arg)))) return false; targs = TREE_CHAIN (targs); } diff -Nrcpad gcc-6.3.0/gcc/gimplify.c gcc-6.4.0/gcc/gimplify.c *** gcc-6.3.0/gcc/gimplify.c Wed Dec 7 22:40:40 2016 --- gcc-6.4.0/gcc/gimplify.c Thu Jun 22 11:23:19 2017 *************** gimplify_modify_expr_rhs (tree *expr_p, *** 4362,4367 **** --- 4362,4375 ---- if (ret != GS_ERROR) ret = GS_OK; + /* If we are going to write RESULT more than once, clear + TREE_READONLY flag, otherwise we might incorrectly promote + the variable to static const and initialize it at compile + time in one of the branches. */ + if (VAR_P (result) + && TREE_TYPE (TREE_OPERAND (cond, 1)) != void_type_node + && TREE_TYPE (TREE_OPERAND (cond, 2)) != void_type_node) + TREE_READONLY (result) = 0; if (TREE_TYPE (TREE_OPERAND (cond, 1)) != void_type_node) TREE_OPERAND (cond, 1) = build2 (code, void_type_node, result, *************** omp_add_variable (struct gimplify_omp_ct *** 5799,5807 **** return; /* Never elide decls whose type has TREE_ADDRESSABLE set. This means ! there are constructors involved somewhere. */ ! if (TREE_ADDRESSABLE (TREE_TYPE (decl)) ! || TYPE_NEEDS_CONSTRUCTING (TREE_TYPE (decl))) flags |= GOVD_SEEN; n = splay_tree_lookup (ctx->variables, (splay_tree_key)decl); --- 5807,5817 ---- return; /* Never elide decls whose type has TREE_ADDRESSABLE set. This means ! there are constructors involved somewhere. Exception is a shared clause, ! there is nothing privatized in that case. */ ! if ((flags & GOVD_SHARED) == 0 ! && (TREE_ADDRESSABLE (TREE_TYPE (decl)) ! || TYPE_NEEDS_CONSTRUCTING (TREE_TYPE (decl)))) flags |= GOVD_SEEN; n = splay_tree_lookup (ctx->variables, (splay_tree_key)decl); *************** omp_add_variable (struct gimplify_omp_ct *** 5860,5866 **** of PRIVATE. The sharing would take place via the pointer variable which we remapped above. */ if (flags & GOVD_SHARED) ! flags = GOVD_PRIVATE | GOVD_DEBUG_PRIVATE | (flags & (GOVD_SEEN | GOVD_EXPLICIT)); /* We're going to make use of the TYPE_SIZE_UNIT at least in the --- 5870,5876 ---- of PRIVATE. The sharing would take place via the pointer variable which we remapped above. */ if (flags & GOVD_SHARED) ! flags = GOVD_SHARED | GOVD_DEBUG_PRIVATE | (flags & (GOVD_SEEN | GOVD_EXPLICIT)); /* We're going to make use of the TYPE_SIZE_UNIT at least in the *************** gimplify_adjust_omp_clauses_1 (splay_tre *** 7767,7773 **** return 0; if (flags & GOVD_DEBUG_PRIVATE) { ! gcc_assert ((flags & GOVD_DATA_SHARE_CLASS) == GOVD_PRIVATE); private_debug = true; } else if (flags & GOVD_MAP) --- 7777,7783 ---- return 0; if (flags & GOVD_DEBUG_PRIVATE) { ! gcc_assert ((flags & GOVD_DATA_SHARE_CLASS) == GOVD_SHARED); private_debug = true; } else if (flags & GOVD_MAP) *************** gimplify_adjust_omp_clauses (gimple_seq *** 7980,7986 **** { gcc_assert ((n->value & GOVD_DEBUG_PRIVATE) == 0 || ((n->value & GOVD_DATA_SHARE_CLASS) ! == GOVD_PRIVATE)); OMP_CLAUSE_SET_CODE (c, OMP_CLAUSE_PRIVATE); OMP_CLAUSE_PRIVATE_DEBUG (c) = 1; } --- 7990,7996 ---- { gcc_assert ((n->value & GOVD_DEBUG_PRIVATE) == 0 || ((n->value & GOVD_DATA_SHARE_CLASS) ! == GOVD_SHARED)); OMP_CLAUSE_SET_CODE (c, OMP_CLAUSE_PRIVATE); OMP_CLAUSE_PRIVATE_DEBUG (c) = 1; } *************** gimplify_adjust_omp_clauses (gimple_seq *** 8136,8143 **** if ((ctx->region_type & ORT_TARGET) != 0 && !(n->value & GOVD_SEEN) && GOMP_MAP_ALWAYS_P (OMP_CLAUSE_MAP_KIND (c)) == 0 ! && !lookup_attribute ("omp declare target link", ! DECL_ATTRIBUTES (decl))) { remove = true; /* For struct element mapping, if struct is never referenced --- 8146,8154 ---- if ((ctx->region_type & ORT_TARGET) != 0 && !(n->value & GOVD_SEEN) && GOMP_MAP_ALWAYS_P (OMP_CLAUSE_MAP_KIND (c)) == 0 ! && (!is_global_var (decl) ! || !lookup_attribute ("omp declare target link", ! DECL_ATTRIBUTES (decl)))) { remove = true; /* For struct element mapping, if struct is never referenced *************** gimplify_omp_for (tree *expr_p, gimple_s *** 9434,9441 **** gimple_omp_for_set_combined_into_p (gfor, true); for (i = 0; i < (int) gimple_omp_for_collapse (gfor); i++) { ! t = unshare_expr (gimple_omp_for_index (gfor, i)); ! gimple_omp_for_set_index (gforo, i, t); t = unshare_expr (gimple_omp_for_initial (gfor, i)); gimple_omp_for_set_initial (gforo, i, t); gimple_omp_for_set_cond (gforo, i, --- 9445,9453 ---- gimple_omp_for_set_combined_into_p (gfor, true); for (i = 0; i < (int) gimple_omp_for_collapse (gfor); i++) { ! tree type = TREE_TYPE (gimple_omp_for_index (gfor, i)); ! tree v = create_tmp_var (type); ! gimple_omp_for_set_index (gforo, i, v); t = unshare_expr (gimple_omp_for_initial (gfor, i)); gimple_omp_for_set_initial (gforo, i, t); gimple_omp_for_set_cond (gforo, i, *************** gimplify_omp_for (tree *expr_p, gimple_s *** 9443,9449 **** --- 9455,9467 ---- t = unshare_expr (gimple_omp_for_final (gfor, i)); gimple_omp_for_set_final (gforo, i, t); t = unshare_expr (gimple_omp_for_incr (gfor, i)); + gcc_assert (TREE_OPERAND (t, 0) == gimple_omp_for_index (gfor, i)); + TREE_OPERAND (t, 0) = v; gimple_omp_for_set_incr (gforo, i, t); + t = build_omp_clause (input_location, OMP_CLAUSE_PRIVATE); + OMP_CLAUSE_DECL (t) = v; + OMP_CLAUSE_CHAIN (t) = gimple_omp_for_clauses (gforo); + gimple_omp_for_set_clauses (gforo, t); } gimplify_seq_add_stmt (pre_p, gforo); } *************** gimplify_expr (tree *expr_p, gimple_seq *** 11156,11163 **** if (fallback == fb_none && *expr_p && !is_gimple_stmt (*expr_p)) { /* We aren't looking for a value, and we don't have a valid ! statement. If it doesn't have side-effects, throw it away. */ ! if (!TREE_SIDE_EFFECTS (*expr_p)) *expr_p = NULL; else if (!TREE_THIS_VOLATILE (*expr_p)) { --- 11174,11184 ---- if (fallback == fb_none && *expr_p && !is_gimple_stmt (*expr_p)) { /* We aren't looking for a value, and we don't have a valid ! statement. If it doesn't have side-effects, throw it away. ! We can also get here with code such as "*&&L;", where L is ! a LABEL_DECL that is marked as FORCED_LABEL. */ ! if (TREE_CODE (*expr_p) == LABEL_DECL ! || !TREE_SIDE_EFFECTS (*expr_p)) *expr_p = NULL; else if (!TREE_THIS_VOLATILE (*expr_p)) { diff -Nrcpad gcc-6.3.0/gcc/go/ChangeLog gcc-6.4.0/gcc/go/ChangeLog *** gcc-6.3.0/gcc/go/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/go/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,13 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-05-11 Ian Lance Taylor + + PR go/64238 + * go-gcc.cc (Gcc_backend::implicit_variable_reference): Set + DECL_EXTERNAL, clear TREE_STATIC. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/go/go-gcc.cc gcc-6.4.0/gcc/go/go-gcc.cc *** gcc-6.3.0/gcc/go/go-gcc.cc Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/go/go-gcc.cc Thu May 11 23:53:29 2017 *************** Gcc_backend::implicit_variable_reference *** 2738,2746 **** tree decl = build_decl(BUILTINS_LOCATION, VAR_DECL, get_identifier_from_string(name), type_tree); ! DECL_EXTERNAL(decl) = 0; TREE_PUBLIC(decl) = 1; ! TREE_STATIC(decl) = 1; DECL_ARTIFICIAL(decl) = 1; go_preserve_from_gc(decl); return new Bvariable(decl); --- 2738,2746 ---- tree decl = build_decl(BUILTINS_LOCATION, VAR_DECL, get_identifier_from_string(name), type_tree); ! DECL_EXTERNAL(decl) = 1; TREE_PUBLIC(decl) = 1; ! TREE_STATIC(decl) = 0; DECL_ARTIFICIAL(decl) = 1; go_preserve_from_gc(decl); return new Bvariable(decl); diff -Nrcpad gcc-6.3.0/gcc/go/gofrontend/expressions.cc gcc-6.4.0/gcc/go/gofrontend/expressions.cc *** gcc-6.3.0/gcc/go/gofrontend/expressions.cc Wed Jan 27 18:51:58 2016 --- gcc-6.4.0/gcc/go/gofrontend/expressions.cc Tue Jan 24 03:34:14 2017 *************** Unary_expression::do_lower(Gogo*, Named_ *** 3639,3646 **** if (expr->numeric_constant_value(&nc)) { Numeric_constant result; ! if (Unary_expression::eval_constant(op, &nc, loc, &result)) return result.expression(loc); } } --- 3639,3650 ---- if (expr->numeric_constant_value(&nc)) { Numeric_constant result; ! bool issued_error; ! if (Unary_expression::eval_constant(op, &nc, loc, &result, ! &issued_error)) return result.expression(loc); + else if (issued_error) + return Expression::make_error(this->location()); } } *************** Unary_expression::do_is_constant() const *** 3747,3758 **** } // Apply unary opcode OP to UNC, setting NC. Return true if this ! // could be done, false if not. Issue errors for overflow. bool Unary_expression::eval_constant(Operator op, const Numeric_constant* unc, ! Location location, Numeric_constant* nc) { switch (op) { case OPERATOR_PLUS: --- 3751,3765 ---- } // Apply unary opcode OP to UNC, setting NC. Return true if this ! // could be done, false if not. On overflow, issues an error and sets ! // *ISSUED_ERROR. bool Unary_expression::eval_constant(Operator op, const Numeric_constant* unc, ! Location location, Numeric_constant* nc, ! bool* issued_error) { + *issued_error = false; switch (op) { case OPERATOR_PLUS: *************** Unary_expression::eval_constant(Operator *** 3897,3903 **** mpz_clear(uval); mpz_clear(val); ! return nc->set_type(unc->type(), true, location); } // Return the integral constant value of a unary expression, if it has one. --- 3904,3915 ---- mpz_clear(uval); mpz_clear(val); ! if (!nc->set_type(unc->type(), true, location)) ! { ! *issued_error = true; ! return false; ! } ! return true; } // Return the integral constant value of a unary expression, if it has one. *************** Unary_expression::do_numeric_constant_va *** 3908,3915 **** Numeric_constant unc; if (!this->expr_->numeric_constant_value(&unc)) return false; return Unary_expression::eval_constant(this->op_, &unc, this->location(), ! nc); } // Return the type of a unary expression. --- 3920,3928 ---- Numeric_constant unc; if (!this->expr_->numeric_constant_value(&unc)) return false; + bool issued_error; return Unary_expression::eval_constant(this->op_, &unc, this->location(), ! nc, &issued_error); } // Return the type of a unary expression. *************** Binary_expression::compare_complex(const *** 4539,4551 **** // Apply binary opcode OP to LEFT_NC and RIGHT_NC, setting NC. Return // true if this could be done, false if not. Issue errors at LOCATION ! // as appropriate. bool Binary_expression::eval_constant(Operator op, Numeric_constant* left_nc, Numeric_constant* right_nc, ! Location location, Numeric_constant* nc) { switch (op) { case OPERATOR_OROR: --- 4552,4566 ---- // Apply binary opcode OP to LEFT_NC and RIGHT_NC, setting NC. Return // true if this could be done, false if not. Issue errors at LOCATION ! // as appropriate, and sets *ISSUED_ERROR if it did. bool Binary_expression::eval_constant(Operator op, Numeric_constant* left_nc, Numeric_constant* right_nc, ! Location location, Numeric_constant* nc, ! bool* issued_error) { + *issued_error = false; switch (op) { case OPERATOR_OROR: *************** Binary_expression::eval_constant(Operato *** 4594,4600 **** r = Binary_expression::eval_integer(op, left_nc, right_nc, location, nc); if (r) ! r = nc->set_type(type, true, location); return r; } --- 4609,4619 ---- r = Binary_expression::eval_integer(op, left_nc, right_nc, location, nc); if (r) ! { ! r = nc->set_type(type, true, location); ! if (!r) ! *issued_error = true; ! } return r; } *************** Binary_expression::do_lower(Gogo* gogo, *** 4917,4925 **** else { Numeric_constant nc; if (!Binary_expression::eval_constant(op, &left_nc, &right_nc, ! location, &nc)) return this; return nc.expression(location); } } --- 4936,4950 ---- else { Numeric_constant nc; + bool issued_error; if (!Binary_expression::eval_constant(op, &left_nc, &right_nc, ! location, &nc, ! &issued_error)) ! { ! if (issued_error) ! return Expression::make_error(location); return this; + } return nc.expression(location); } } *************** Binary_expression::do_numeric_constant_v *** 5254,5261 **** Numeric_constant right_nc; if (!this->right_->numeric_constant_value(&right_nc)) return false; return Binary_expression::eval_constant(this->op_, &left_nc, &right_nc, ! this->location(), nc); } // Note that the value is being discarded. --- 5279,5287 ---- Numeric_constant right_nc; if (!this->right_->numeric_constant_value(&right_nc)) return false; + bool issued_error; return Binary_expression::eval_constant(this->op_, &left_nc, &right_nc, ! this->location(), nc, &issued_error); } // Note that the value is being discarded. *************** Binary_expression::do_determine_type(con *** 5354,5360 **** Type_context subcontext(*context); ! if (is_comparison) { // In a comparison, the context does not determine the types of // the operands. --- 5380,5391 ---- Type_context subcontext(*context); ! if (is_constant_expr) ! { ! subcontext.type = NULL; ! subcontext.may_be_abstract = true; ! } ! else if (is_comparison) { // In a comparison, the context does not determine the types of // the operands. *************** Binary_expression::do_determine_type(con *** 5396,5403 **** subcontext.type = subcontext.type->make_non_abstract_type(); } ! if (!is_constant_expr) ! this->left_->determine_type(&subcontext); if (is_shift_op) { --- 5427,5433 ---- subcontext.type = subcontext.type->make_non_abstract_type(); } ! this->left_->determine_type(&subcontext); if (is_shift_op) { *************** Binary_expression::do_determine_type(con *** 5417,5424 **** subcontext.may_be_abstract = false; } ! if (!is_constant_expr) ! this->right_->determine_type(&subcontext); if (is_comparison) { --- 5447,5453 ---- subcontext.may_be_abstract = false; } ! this->right_->determine_type(&subcontext); if (is_comparison) { diff -Nrcpad gcc-6.3.0/gcc/go/gofrontend/expressions.h gcc-6.4.0/gcc/go/gofrontend/expressions.h *** gcc-6.3.0/gcc/go/gofrontend/expressions.h Wed Jan 27 18:51:58 2016 --- gcc-6.4.0/gcc/go/gofrontend/expressions.h Tue Jan 24 03:34:14 2017 *************** class Unary_expression : public Expressi *** 1633,1642 **** } // Apply unary opcode OP to UNC, setting NC. Return true if this ! // could be done, false if not. Issue errors for overflow. static bool eval_constant(Operator op, const Numeric_constant* unc, ! Location, Numeric_constant* nc); static Expression* do_import(Import*); --- 1633,1643 ---- } // Apply unary opcode OP to UNC, setting NC. Return true if this ! // could be done, false if not. On overflow, issues an error and ! // sets *ISSUED_ERROR. static bool eval_constant(Operator op, const Numeric_constant* unc, ! Location, Numeric_constant* nc, bool *issued_error); static Expression* do_import(Import*); *************** class Binary_expression : public Express *** 1755,1765 **** // Apply binary opcode OP to LEFT_NC and RIGHT_NC, setting NC. // Return true if this could be done, false if not. Issue errors at ! // LOCATION as appropriate. static bool eval_constant(Operator op, Numeric_constant* left_nc, Numeric_constant* right_nc, Location location, ! Numeric_constant* nc); // Compare constants LEFT_NC and RIGHT_NC according to OP, setting // *RESULT. Return true if this could be done, false if not. Issue --- 1756,1766 ---- // Apply binary opcode OP to LEFT_NC and RIGHT_NC, setting NC. // Return true if this could be done, false if not. Issue errors at ! // LOCATION as appropriate, and sets *ISSUED_ERROR if it did. static bool eval_constant(Operator op, Numeric_constant* left_nc, Numeric_constant* right_nc, Location location, ! Numeric_constant* nc, bool* issued_error); // Compare constants LEFT_NC and RIGHT_NC according to OP, setting // *RESULT. Return true if this could be done, false if not. Issue diff -Nrcpad gcc-6.3.0/gcc/go/gofrontend/types.cc gcc-6.4.0/gcc/go/gofrontend/types.cc *** gcc-6.3.0/gcc/go/gofrontend/types.cc Wed Feb 3 06:54:41 2016 --- gcc-6.4.0/gcc/go/gofrontend/types.cc Wed Feb 1 23:35:59 2017 *************** Type::make_gc_symbol_var(Gogo* gogo) *** 2175,2185 **** is_common = true; } // Since we are building the GC symbol in this package, we must create the // variable before converting the initializer to its backend representation // because the initializer may refer to the GC symbol for this type. this->gc_symbol_var_ = ! gogo->backend()->implicit_variable(sym_name, sym_btype, false, true, is_common, 0); if (phash != NULL) *phash = this->gc_symbol_var_; --- 2175,2200 ---- is_common = true; } + // The current garbage collector requires that the GC symbol be + // aligned to at least a four byte boundary. See the use of PRECISE + // and LOOP in libgo/runtime/mgc0.c. + int64_t align; + if (!sym_init->type()->backend_type_align(gogo, &align)) + go_assert(saw_errors()); + if (align < 4) + align = 4; + else + { + // Use default alignment. + align = 0; + } + // Since we are building the GC symbol in this package, we must create the // variable before converting the initializer to its backend representation // because the initializer may refer to the GC symbol for this type. this->gc_symbol_var_ = ! gogo->backend()->implicit_variable(sym_name, sym_btype, false, true, ! is_common, align); if (phash != NULL) *phash = this->gc_symbol_var_; diff -Nrcpad gcc-6.3.0/gcc/graphite-isl-ast-to-gimple.c gcc-6.4.0/gcc/graphite-isl-ast-to-gimple.c *** gcc-6.3.0/gcc/graphite-isl-ast-to-gimple.c Fri Dec 9 08:43:50 2016 --- gcc-6.4.0/gcc/graphite-isl-ast-to-gimple.c Wed May 10 07:44:41 2017 *************** bool translate_isl_ast_to_gimple:: *** 1157,1162 **** --- 1157,1165 ---- is_valid_rename (tree rename, basic_block def_bb, basic_block use_bb, phi_node_kind phi_kind, tree old_name, basic_block old_bb) const { + if (SSA_NAME_IS_DEFAULT_DEF (rename)) + return true; + /* The def of the rename must either dominate the uses or come from a back-edge. Also the def must respect the loop closed ssa form. */ if (!is_loop_closed_ssa_use (use_bb, rename)) *************** get_rename (basic_block new_bb, tree old *** 1212,1217 **** --- 1215,1221 ---- basic_block bb = gimple_bb (SSA_NAME_DEF_STMT (rename)); if (is_valid_rename (rename, bb, new_bb, phi_kind, old_name, old_bb) && (phi_kind == close_phi + || ! bb || flow_bb_inside_loop_p (bb->loop_father, new_bb))) return rename; return NULL_TREE; *************** copy_loop_phi_nodes (basic_block bb, bas *** 1913,1919 **** if (is_gimple_reg (res) && scev_analyzable_p (res, region->region)) continue; ! gphi *new_phi = create_phi_node (SSA_NAME_VAR (res), new_bb); tree new_res = create_new_def_for (res, new_phi, gimple_phi_result_ptr (new_phi)); set_rename (res, new_res); --- 1917,1923 ---- if (is_gimple_reg (res) && scev_analyzable_p (res, region->region)) continue; ! gphi *new_phi = create_phi_node (NULL_TREE, new_bb); tree new_res = create_new_def_for (res, new_phi, gimple_phi_result_ptr (new_phi)); set_rename (res, new_res); *************** add_close_phis_to_outer_loops (tree last *** 2013,2019 **** if (!bb_contains_loop_close_phi_nodes (bb) || !single_succ_p (bb)) bb = split_edge (e); ! gphi *close_phi = create_phi_node (SSA_NAME_VAR (last_merge_name), bb); tree res = create_new_def_for (last_merge_name, close_phi, gimple_phi_result_ptr (close_phi)); set_rename (old_close_phi_name, res); --- 2017,2023 ---- if (!bb_contains_loop_close_phi_nodes (bb) || !single_succ_p (bb)) bb = split_edge (e); ! gphi *close_phi = create_phi_node (NULL_TREE, bb); tree res = create_new_def_for (last_merge_name, close_phi, gimple_phi_result_ptr (close_phi)); set_rename (old_close_phi_name, res); *************** add_close_phis_to_merge_points (gphi *ol *** 2058,2064 **** last_merge_name = add_close_phis_to_outer_loops (last_merge_name, merge_e, old_close_phi); ! gphi *merge_phi = create_phi_node (SSA_NAME_VAR (old_close_phi_name), new_merge_bb); tree merge_res = create_new_def_for (old_close_phi_name, merge_phi, gimple_phi_result_ptr (merge_phi)); set_rename (old_close_phi_name, merge_res); --- 2062,2068 ---- last_merge_name = add_close_phis_to_outer_loops (last_merge_name, merge_e, old_close_phi); ! gphi *merge_phi = create_phi_node (NULL_TREE, new_merge_bb); tree merge_res = create_new_def_for (old_close_phi_name, merge_phi, gimple_phi_result_ptr (merge_phi)); set_rename (old_close_phi_name, merge_res); *************** copy_loop_close_phi_args (basic_block ol *** 2111,2117 **** /* Loop close phi nodes should not be scev_analyzable_p. */ gcc_unreachable (); ! gphi *new_close_phi = create_phi_node (SSA_NAME_VAR (res), new_bb); tree new_res = create_new_def_for (res, new_close_phi, gimple_phi_result_ptr (new_close_phi)); set_rename (res, new_res); --- 2115,2121 ---- /* Loop close phi nodes should not be scev_analyzable_p. */ gcc_unreachable (); ! gphi *new_close_phi = create_phi_node (NULL_TREE, new_bb); tree new_res = create_new_def_for (res, new_close_phi, gimple_phi_result_ptr (new_close_phi)); set_rename (res, new_res); *************** copy_cond_phi_nodes (basic_block bb, bas *** 2494,2500 **** if (virtual_operand_p (res)) continue; ! gphi *new_phi = create_phi_node (SSA_NAME_VAR (res), new_bb); tree new_res = create_new_def_for (res, new_phi, gimple_phi_result_ptr (new_phi)); set_rename (res, new_res); --- 2498,2504 ---- if (virtual_operand_p (res)) continue; ! gphi *new_phi = create_phi_node (NULL_TREE, new_bb); tree new_res = create_new_def_for (res, new_phi, gimple_phi_result_ptr (new_phi)); set_rename (res, new_res); diff -Nrcpad gcc-6.3.0/gcc/graphite-scop-detection.c gcc-6.4.0/gcc/graphite-scop-detection.c *** gcc-6.3.0/gcc/graphite-scop-detection.c Sat May 7 07:02:36 2016 --- gcc-6.4.0/gcc/graphite-scop-detection.c Thu Jun 22 07:22:13 2017 *************** scop_detection::merge_sese (sese_l first *** 817,822 **** --- 817,841 ---- != loop_depth (exit->dest->loop_father)) return invalid_sese; + /* For now we just bail out when there is a loop exit in the region + that is not also the exit of the region. We could enlarge the + region to cover the loop that region exits to. See PR79977. */ + if (loop_outer (entry->src->loop_father)) + { + vec exits = get_loop_exit_edges (entry->src->loop_father); + for (unsigned i = 0; i < exits.length (); ++i) + { + if (exits[i] != exit + && bb_in_region (exits[i]->src, entry->dest, exit->src)) + { + DEBUG_PRINT (dp << "[scop-detection-fail] cannot merge seses.\n"); + exits.release (); + return invalid_sese; + } + } + exits.release (); + } + /* For now we just want to bail out when exit does not post-dominate entry. TODO: We might just add a basic_block at the exit to make exit post-dominate entry (the entire region). */ *************** scop_detection::build_scop_breadth (sese *** 905,910 **** --- 924,941 ---- sese_l combined = merge_sese (s1, s2); + /* Combining adjacent loops may add unrelated loops into the + region so we have to check all sub-loops of the outer loop + that are in the combined region. */ + if (combined) + for (l = loop_outer (loop)->inner; l; l = l->next) + if (bb_in_sese_p (l->header, combined) + && ! loop_is_valid_in_scop (l, combined)) + { + combined = invalid_sese; + break; + } + if (combined) s1 = combined; else *************** scop_detection::can_represent_loop_1 (lo *** 931,936 **** --- 962,969 ---- && niter_desc.control.no_overflow && (niter = number_of_latch_executions (loop)) && !chrec_contains_undetermined (niter) + && !chrec_contains_undetermined (scalar_evolution_in_region (scop, + loop, niter)) && graphite_can_represent_expr (scop, loop, niter); } *************** scop_detection::harmful_loop_in_region ( *** 1048,1079 **** print_sese (dump_file, scop)); gcc_assert (dominated_by_p (CDI_DOMINATORS, exit_bb, entry_bb)); ! int depth = bb_dom_dfs_in (CDI_DOMINATORS, exit_bb) ! - bb_dom_dfs_in (CDI_DOMINATORS, entry_bb); ! ! gcc_assert (depth > 0); ! ! vec dom ! = get_dominated_to_depth (CDI_DOMINATORS, entry_bb, depth); ! int i; ! basic_block bb; bitmap loops = BITMAP_ALLOC (NULL); ! FOR_EACH_VEC_ELT (dom, i, bb) { DEBUG_PRINT (dp << "Visiting bb_" << bb->index << "\n"); - /* We don't want to analyze any bb outside sese. */ - if (!dominated_by_p (CDI_POST_DOMINATORS, bb, exit_bb)) - continue; - - /* Basic blocks dominated by the scop->exit are not in the scop. */ - if (bb != exit_bb && dominated_by_p (CDI_DOMINATORS, bb, exit_bb)) - continue; - /* The basic block should not be part of an irreducible loop. */ if (bb->flags & BB_IRREDUCIBLE_LOOP) { - dom.release (); BITMAP_FREE (loops); return true; } --- 1081,1098 ---- print_sese (dump_file, scop)); gcc_assert (dominated_by_p (CDI_DOMINATORS, exit_bb, entry_bb)); ! auto_vec worklist; bitmap loops = BITMAP_ALLOC (NULL); ! ! worklist.safe_push (entry_bb); ! while (! worklist.is_empty ()) { + basic_block bb = worklist.pop (); DEBUG_PRINT (dp << "Visiting bb_" << bb->index << "\n"); /* The basic block should not be part of an irreducible loop. */ if (bb->flags & BB_IRREDUCIBLE_LOOP) { BITMAP_FREE (loops); return true; } *************** scop_detection::harmful_loop_in_region ( *** 1087,1093 **** FOR_EACH_EDGE (e, ei, bb->succs) if (!dominated_by_p (CDI_POST_DOMINATORS, bb, e->dest) && !dominated_by_p (CDI_DOMINATORS, e->dest, bb)) ! return true; } /* Collect all loops in the current region. */ --- 1106,1115 ---- FOR_EACH_EDGE (e, ei, bb->succs) if (!dominated_by_p (CDI_POST_DOMINATORS, bb, e->dest) && !dominated_by_p (CDI_DOMINATORS, e->dest, bb)) ! { ! BITMAP_FREE (loops); ! return true; ! } } /* Collect all loops in the current region. */ *************** scop_detection::harmful_loop_in_region ( *** 1101,1112 **** in loop_is_valid_in_scop. */ if (harmful_stmt_in_bb (scop, bb)) { - dom.release (); BITMAP_FREE (loops); return true; } } } /* Go through all loops and check that they are still valid in the combined --- 1123,1138 ---- in loop_is_valid_in_scop. */ if (harmful_stmt_in_bb (scop, bb)) { BITMAP_FREE (loops); return true; } } + if (bb != exit_bb) + for (basic_block dom = first_dom_son (CDI_DOMINATORS, bb); + dom; + dom = next_dom_son (CDI_DOMINATORS, dom)) + worklist.safe_push (dom); } /* Go through all loops and check that they are still valid in the combined *************** scop_detection::harmful_loop_in_region ( *** 1120,1133 **** if (!loop_is_valid_in_scop (loop, scop)) { - dom.release (); BITMAP_FREE (loops); return true; } } - - dom.release (); BITMAP_FREE (loops); return false; } --- 1146,1157 ---- if (!loop_is_valid_in_scop (loop, scop)) { BITMAP_FREE (loops); return true; } } BITMAP_FREE (loops); + return false; } diff -Nrcpad gcc-6.3.0/gcc/graphite-sese-to-poly.c gcc-6.4.0/gcc/graphite-sese-to-poly.c *** gcc-6.3.0/gcc/graphite-sese-to-poly.c Sat Apr 9 15:28:24 2016 --- gcc-6.4.0/gcc/graphite-sese-to-poly.c Wed Feb 8 13:13:53 2017 *************** extract_affine (scop_p s, tree e, __isl_ *** 407,413 **** case SSA_NAME: gcc_assert (-1 != parameter_index_in_region_1 (e, s->scop_info) ! || !invariant_in_sese_p_rec (e, s->scop_info->region, NULL)); res = extract_affine_name (s, e, space); break; --- 407,413 ---- case SSA_NAME: gcc_assert (-1 != parameter_index_in_region_1 (e, s->scop_info) ! || defined_in_sese_p (e, s->scop_info->region)); res = extract_affine_name (s, e, space); break; *************** extract_affine (scop_p s, tree e, __isl_ *** 436,446 **** /* Returns a linear expression for tree T evaluated in PBB. */ static isl_pw_aff * ! create_pw_aff_from_tree (poly_bb_p pbb, tree t) { scop_p scop = PBB_SCOP (pbb); ! t = scalar_evolution_in_region (scop->scop_info->region, pbb_loop (pbb), t); gcc_assert (!chrec_contains_undetermined (t)); gcc_assert (!automatically_generated_chrec_p (t)); --- 436,446 ---- /* Returns a linear expression for tree T evaluated in PBB. */ static isl_pw_aff * ! create_pw_aff_from_tree (poly_bb_p pbb, loop_p loop, tree t) { scop_p scop = PBB_SCOP (pbb); ! t = scalar_evolution_in_region (scop->scop_info->region, loop, t); gcc_assert (!chrec_contains_undetermined (t)); gcc_assert (!automatically_generated_chrec_p (t)); *************** create_pw_aff_from_tree (poly_bb_p pbb, *** 455,462 **** static void add_condition_to_pbb (poly_bb_p pbb, gcond *stmt, enum tree_code code) { ! isl_pw_aff *lhs = create_pw_aff_from_tree (pbb, gimple_cond_lhs (stmt)); ! isl_pw_aff *rhs = create_pw_aff_from_tree (pbb, gimple_cond_rhs (stmt)); isl_set *cond; switch (code) --- 455,463 ---- static void add_condition_to_pbb (poly_bb_p pbb, gcond *stmt, enum tree_code code) { ! loop_p loop = gimple_bb (stmt)->loop_father; ! isl_pw_aff *lhs = create_pw_aff_from_tree (pbb, loop, gimple_cond_lhs (stmt)); ! isl_pw_aff *rhs = create_pw_aff_from_tree (pbb, loop, gimple_cond_rhs (stmt)); isl_set *cond; switch (code) diff -Nrcpad gcc-6.3.0/gcc/internal-fn.c gcc-6.4.0/gcc/internal-fn.c *** gcc-6.3.0/gcc/internal-fn.c Fri Sep 16 09:38:31 2016 --- gcc-6.4.0/gcc/internal-fn.c Wed Feb 15 06:59:34 2017 *************** expand_mul_overflow (location_t loc, tre *** 1271,1278 **** res = expand_expr_real_2 (&ops, NULL_RTX, wmode, EXPAND_NORMAL); rtx hipart = expand_shift (RSHIFT_EXPR, wmode, res, prec, NULL_RTX, uns); ! hipart = gen_lowpart (mode, hipart); ! res = gen_lowpart (mode, res); if (uns) /* For the unsigned multiplication, there was overflow if HIPART is non-zero. */ --- 1271,1278 ---- res = expand_expr_real_2 (&ops, NULL_RTX, wmode, EXPAND_NORMAL); rtx hipart = expand_shift (RSHIFT_EXPR, wmode, res, prec, NULL_RTX, uns); ! hipart = convert_modes (mode, wmode, hipart, uns); ! res = convert_modes (mode, wmode, res, uns); if (uns) /* For the unsigned multiplication, there was overflow if HIPART is non-zero. */ *************** expand_mul_overflow (location_t loc, tre *** 1305,1320 **** unsigned int hprec = GET_MODE_PRECISION (hmode); rtx hipart0 = expand_shift (RSHIFT_EXPR, mode, op0, hprec, NULL_RTX, uns); ! hipart0 = gen_lowpart (hmode, hipart0); ! rtx lopart0 = gen_lowpart (hmode, op0); rtx signbit0 = const0_rtx; if (!uns) signbit0 = expand_shift (RSHIFT_EXPR, hmode, lopart0, hprec - 1, NULL_RTX, 0); rtx hipart1 = expand_shift (RSHIFT_EXPR, mode, op1, hprec, NULL_RTX, uns); ! hipart1 = gen_lowpart (hmode, hipart1); ! rtx lopart1 = gen_lowpart (hmode, op1); rtx signbit1 = const0_rtx; if (!uns) signbit1 = expand_shift (RSHIFT_EXPR, hmode, lopart1, hprec - 1, --- 1305,1320 ---- unsigned int hprec = GET_MODE_PRECISION (hmode); rtx hipart0 = expand_shift (RSHIFT_EXPR, mode, op0, hprec, NULL_RTX, uns); ! hipart0 = convert_modes (hmode, mode, hipart0, uns); ! rtx lopart0 = convert_modes (hmode, mode, op0, uns); rtx signbit0 = const0_rtx; if (!uns) signbit0 = expand_shift (RSHIFT_EXPR, hmode, lopart0, hprec - 1, NULL_RTX, 0); rtx hipart1 = expand_shift (RSHIFT_EXPR, mode, op1, hprec, NULL_RTX, uns); ! hipart1 = convert_modes (hmode, mode, hipart1, uns); ! rtx lopart1 = convert_modes (hmode, mode, op1, uns); rtx signbit1 = const0_rtx; if (!uns) signbit1 = expand_shift (RSHIFT_EXPR, hmode, lopart1, hprec - 1, *************** expand_mul_overflow (location_t loc, tre *** 1505,1515 **** if (loxhi >> (bitsize / 2) == 0 (if uns). */ rtx hipartloxhi = expand_shift (RSHIFT_EXPR, mode, loxhi, hprec, NULL_RTX, 0); ! hipartloxhi = gen_lowpart (hmode, hipartloxhi); rtx signbitloxhi = const0_rtx; if (!uns) signbitloxhi = expand_shift (RSHIFT_EXPR, hmode, ! gen_lowpart (hmode, loxhi), hprec - 1, NULL_RTX, 0); do_compare_rtx_and_jump (signbitloxhi, hipartloxhi, NE, true, hmode, --- 1505,1516 ---- if (loxhi >> (bitsize / 2) == 0 (if uns). */ rtx hipartloxhi = expand_shift (RSHIFT_EXPR, mode, loxhi, hprec, NULL_RTX, 0); ! hipartloxhi = convert_modes (hmode, mode, hipartloxhi, 0); rtx signbitloxhi = const0_rtx; if (!uns) signbitloxhi = expand_shift (RSHIFT_EXPR, hmode, ! convert_modes (hmode, mode, ! loxhi, 0), hprec - 1, NULL_RTX, 0); do_compare_rtx_and_jump (signbitloxhi, hipartloxhi, NE, true, hmode, *************** expand_mul_overflow (location_t loc, tre *** 1519,1525 **** /* res = (loxhi << (bitsize / 2)) | (hmode) lo0xlo1; */ rtx loxhishifted = expand_shift (LSHIFT_EXPR, mode, loxhi, hprec, NULL_RTX, 1); ! tem = convert_modes (mode, hmode, gen_lowpart (hmode, lo0xlo1), 1); tem = expand_simple_binop (mode, IOR, loxhishifted, tem, res, 1, OPTAB_DIRECT); --- 1520,1527 ---- /* res = (loxhi << (bitsize / 2)) | (hmode) lo0xlo1; */ rtx loxhishifted = expand_shift (LSHIFT_EXPR, mode, loxhi, hprec, NULL_RTX, 1); ! tem = convert_modes (mode, hmode, ! convert_modes (hmode, mode, lo0xlo1, 1), 1); tem = expand_simple_binop (mode, IOR, loxhishifted, tem, res, 1, OPTAB_DIRECT); diff -Nrcpad gcc-6.3.0/gcc/ipa-cp.c gcc-6.4.0/gcc/ipa-cp.c *** gcc-6.3.0/gcc/ipa-cp.c Mon Jan 11 10:09:17 2016 --- gcc-6.4.0/gcc/ipa-cp.c Fri May 26 11:28:44 2017 *************** determine_versionability (struct cgraph_ *** 537,542 **** --- 537,548 ---- decloned constructors, inlining is always better anyway. */ else if (node->comdat_local_p ()) reason = "comdat-local function"; + else if (node->calls_comdat_local) + { + /* TODO: call is versionable if we make sure that all + callers are inside of a comdat group. */ + reason = "calls comdat-local function"; + } if (reason && dump_file && !node->alias && !node->thunk.thunk_p) fprintf (dump_file, "Function %s/%i is not versionable, reason: %s.\n", diff -Nrcpad gcc-6.3.0/gcc/ipa-devirt.c gcc-6.4.0/gcc/ipa-devirt.c *** gcc-6.3.0/gcc/ipa-devirt.c Tue Apr 5 20:58:56 2016 --- gcc-6.4.0/gcc/ipa-devirt.c Thu Jun 22 11:18:57 2017 *************** warn_types_mismatch (tree t1, tree t2, l *** 1225,1231 **** if (types_odr_comparable (t1, t2, true) && types_same_for_odr (t1, t2, true)) inform (loc_t1, ! "type %qT itself violate the C++ One Definition Rule", t1); /* Prevent pointless warnings like "struct aa" should match "struct aa". */ else if (TYPE_NAME (t1) == TYPE_NAME (t2) && TREE_CODE (t1) == TREE_CODE (t2) && !loc_t2_useful) --- 1225,1231 ---- if (types_odr_comparable (t1, t2, true) && types_same_for_odr (t1, t2, true)) inform (loc_t1, ! "type %qT itself violates the C++ One Definition Rule", t1); /* Prevent pointless warnings like "struct aa" should match "struct aa". */ else if (TYPE_NAME (t1) == TYPE_NAME (t2) && TREE_CODE (t1) == TREE_CODE (t2) && !loc_t2_useful) *************** odr_types_equivalent_p (tree t1, tree t2 *** 1572,1578 **** if (DECL_ARTIFICIAL (f1)) break; warn_odr (t1, t2, f1, f2, warn, warned, ! G_("fields has different layout " "in another translation unit")); return false; } --- 1572,1578 ---- if (DECL_ARTIFICIAL (f1)) break; warn_odr (t1, t2, f1, f2, warn, warned, ! G_("fields have different layout " "in another translation unit")); return false; } *************** maybe_record_node (vec & *** 2462,2471 **** nodes.safe_push (target_node); } } ! else if (completep ! && (!type_in_anonymous_namespace_p ! (DECL_CONTEXT (target)) ! || flag_ltrans)) *completep = false; } --- 2462,2480 ---- nodes.safe_push (target_node); } } ! else if (!completep) ! ; ! /* We have definition of __cxa_pure_virtual that is not accessible (it is ! optimized out or partitioned to other unit) so we can not add it. When ! not sanitizing, there is nothing to do. ! Otherwise declare the list incomplete. */ ! else if (pure_virtual) ! { ! if (flag_sanitize & SANITIZE_UNREACHABLE) ! *completep = false; ! } ! else if (flag_ltrans ! || !type_in_anonymous_namespace_p (DECL_CONTEXT (target))) *completep = false; } *************** dump_possible_polymorphic_call_targets ( *** 3358,3364 **** fprintf (f, " Speculative targets:"); dump_targets (f, targets); } ! gcc_assert (targets.length () <= len); fprintf (f, "\n"); } --- 3367,3379 ---- fprintf (f, " Speculative targets:"); dump_targets (f, targets); } ! /* Ugly: during callgraph construction the target cache may get populated ! before all targets are found. While this is harmless (because all local ! types are discovered and only in those case we devirtualize fully and we ! don't do speculative devirtualization before IPA stage) it triggers ! assert here when dumping at that stage also populates the case with ! speculative targets. Quietly ignore this. */ ! gcc_assert (symtab->state < IPA_SSA || targets.length () <= len); fprintf (f, "\n"); } diff -Nrcpad gcc-6.3.0/gcc/ipa-inline-transform.c gcc-6.4.0/gcc/ipa-inline-transform.c *** gcc-6.3.0/gcc/ipa-inline-transform.c Thu Jun 30 08:46:30 2016 --- gcc-6.4.0/gcc/ipa-inline-transform.c Fri Jan 20 09:33:15 2017 *************** inline_call (struct cgraph_edge *e, bool *** 324,329 **** --- 324,331 ---- if (DECL_FUNCTION_PERSONALITY (callee->decl)) DECL_FUNCTION_PERSONALITY (to->decl) = DECL_FUNCTION_PERSONALITY (callee->decl); + + bool reload_optimization_node = false; if (!opt_for_fn (callee->decl, flag_strict_aliasing) && opt_for_fn (to->decl, flag_strict_aliasing)) { *************** inline_call (struct cgraph_edge *e, bool *** 336,343 **** --- 338,350 ---- to->name (), to->order); DECL_FUNCTION_SPECIFIC_OPTIMIZATION (to->decl) = build_optimization_node (&opts); + reload_optimization_node = true; } + /* Reload global optimization flags. */ + if (reload_optimization_node && DECL_STRUCT_FUNCTION (to->decl) == cfun) + set_cfun (cfun, true); + /* If aliases are involved, redirect edge to the actual destination and possibly remove the aliases. */ if (e->callee != callee) diff -Nrcpad gcc-6.3.0/gcc/ipa-polymorphic-call.c gcc-6.4.0/gcc/ipa-polymorphic-call.c *** gcc-6.3.0/gcc/ipa-polymorphic-call.c Tue Aug 9 16:13:37 2016 --- gcc-6.4.0/gcc/ipa-polymorphic-call.c Fri Jan 20 08:49:16 2017 *************** contains_type_p (tree outer_type, HOST_W *** 463,474 **** /* Check that type is within range. */ if (offset < 0) return false; ! if (TYPE_SIZE (outer_type) && TYPE_SIZE (otr_type) ! && TREE_CODE (TYPE_SIZE (outer_type)) == INTEGER_CST ! && TREE_CODE (TYPE_SIZE (otr_type)) == INTEGER_CST ! && wi::ltu_p (wi::to_offset (TYPE_SIZE (outer_type)), ! (wi::to_offset (TYPE_SIZE (otr_type)) + offset))) ! return false; context.offset = offset; context.outer_type = TYPE_MAIN_VARIANT (outer_type); --- 463,474 ---- /* Check that type is within range. */ if (offset < 0) return false; ! ! /* PR ipa/71207 ! As OUTER_TYPE can be a type which has a diamond virtual inheritance, ! it's not necessary that INNER_TYPE will fit within OUTER_TYPE with ! a given offset. It can happen that INNER_TYPE also contains a base object, ! however it would point to the same instance in the OUTER_TYPE. */ context.offset = offset; context.outer_type = TYPE_MAIN_VARIANT (outer_type); diff -Nrcpad gcc-6.3.0/gcc/ipa-prop.c gcc-6.4.0/gcc/ipa-prop.c *** gcc-6.3.0/gcc/ipa-prop.c Tue Aug 9 10:49:36 2016 --- gcc-6.4.0/gcc/ipa-prop.c Wed Mar 1 13:53:33 2017 *************** ipa_prop_write_jump_functions (void) *** 4745,4751 **** lto_symtab_encoder_iterator lsei; lto_symtab_encoder_t encoder; ! if (!ipa_node_params_sum) return; ob = create_output_block (LTO_section_jump_functions); --- 4745,4751 ---- lto_symtab_encoder_iterator lsei; lto_symtab_encoder_t encoder; ! if (!ipa_node_params_sum || !ipa_edge_args_vector) return; ob = create_output_block (LTO_section_jump_functions); diff -Nrcpad gcc-6.3.0/gcc/ipa-pure-const.c gcc-6.4.0/gcc/ipa-pure-const.c *** gcc-6.3.0/gcc/ipa-pure-const.c Wed Apr 13 20:43:10 2016 --- gcc-6.4.0/gcc/ipa-pure-const.c Wed Mar 22 10:46:27 2017 *************** warn_function_const (tree decl, bool kno *** 218,228 **** static void warn_function_noreturn (tree decl) { static hash_set *warned_about; if (!lang_hooks.missing_noreturn_ok_p (decl) && targetm.warn_func_return (decl)) warned_about ! = suggest_attribute (OPT_Wsuggest_attribute_noreturn, decl, true, warned_about, "noreturn"); } --- 218,234 ---- static void warn_function_noreturn (tree decl) { + tree original_decl = decl; + + cgraph_node *node = cgraph_node::get (decl); + if (node->instrumentation_clone) + decl = node->instrumented_version->decl; + static hash_set *warned_about; if (!lang_hooks.missing_noreturn_ok_p (decl) && targetm.warn_func_return (decl)) warned_about ! = suggest_attribute (OPT_Wsuggest_attribute_noreturn, original_decl, true, warned_about, "noreturn"); } *************** static bool *** 1160,1166 **** cdtor_p (cgraph_node *n, void *) { if (DECL_STATIC_CONSTRUCTOR (n->decl) || DECL_STATIC_DESTRUCTOR (n->decl)) ! return !TREE_READONLY (n->decl) && !DECL_PURE_P (n->decl); return false; } --- 1166,1173 ---- cdtor_p (cgraph_node *n, void *) { if (DECL_STATIC_CONSTRUCTOR (n->decl) || DECL_STATIC_DESTRUCTOR (n->decl)) ! return ((!TREE_READONLY (n->decl) && !DECL_PURE_P (n->decl)) ! || DECL_LOOPING_CONST_OR_PURE_P (n->decl)); return false; } diff -Nrcpad gcc-6.3.0/gcc/ipa-split.c gcc-6.4.0/gcc/ipa-split.c *** gcc-6.3.0/gcc/ipa-split.c Fri Feb 12 11:59:00 2016 --- gcc-6.4.0/gcc/ipa-split.c Fri May 26 11:29:35 2017 *************** split_function (basic_block return_bb, s *** 1364,1369 **** --- 1364,1378 ---- node->split_part = true; + if (cur_node->same_comdat_group) + { + /* TODO: call is versionable if we make sure that all + callers are inside of a comdat group. */ + cur_node->calls_comdat_local = 1; + node->add_to_same_comdat_group (cur_node); + } + + /* Let's take a time profile for splitted function. */ node->tp_first_run = cur_node->tp_first_run + 1; diff -Nrcpad gcc-6.3.0/gcc/ipa-visibility.c gcc-6.4.0/gcc/ipa-visibility.c *** gcc-6.3.0/gcc/ipa-visibility.c Mon Apr 4 09:26:29 2016 --- gcc-6.4.0/gcc/ipa-visibility.c Thu Jun 22 11:16:16 2017 *************** static bool *** 90,96 **** non_local_p (struct cgraph_node *node, void *data ATTRIBUTE_UNUSED) { return !(node->only_called_directly_or_aliased_p () ! /* i386 would need update to output thunk with locak calling ocnvetions. */ && !node->thunk.thunk_p && node->definition --- 90,96 ---- non_local_p (struct cgraph_node *node, void *data ATTRIBUTE_UNUSED) { return !(node->only_called_directly_or_aliased_p () ! /* i386 would need update to output thunk with local calling ocnvetions. */ && !node->thunk.thunk_p && node->definition *************** comdat_can_be_unshared_p_1 (symtab_node *** 153,159 **** /* COMDAT functions must be shared only if they have address taken, otherwise we can produce our own private implementation with -fwhole-program. ! Return true when turning COMDAT functoin static can not lead to wrong code when the resulting object links with a library defining same COMDAT. Virtual functions do have their addresses taken from the vtables, --- 153,159 ---- /* COMDAT functions must be shared only if they have address taken, otherwise we can produce our own private implementation with -fwhole-program. ! Return true when turning COMDAT function static can not lead to wrong code when the resulting object links with a library defining same COMDAT. Virtual functions do have their addresses taken from the vtables, *************** optimize_weakref (symtab_node *node) *** 530,535 **** --- 530,611 ---- gcc_assert (node->alias); } + /* NODE is an externally visible definition, which we've discovered is + not needed externally. Make it local to this compilation. */ + + static void + localize_node (bool whole_program, symtab_node *node) + { + gcc_assert (whole_program || in_lto_p || !TREE_PUBLIC (node->decl)); + + /* It is possible that one comdat group contains both hidden and non-hidden + symbols. In this case we can privatize all hidden symbol but we need + to keep non-hidden exported. */ + if (node->same_comdat_group + && node->resolution == LDPR_PREVAILING_DEF_IRONLY) + { + symtab_node *next; + for (next = node->same_comdat_group; + next != node; next = next->same_comdat_group) + if (next->resolution == LDPR_PREVAILING_DEF_IRONLY_EXP + || next->resolution == LDPR_PREVAILING_DEF) + break; + if (node != next) + { + if (!node->transparent_alias) + { + node->resolution = LDPR_PREVAILING_DEF_IRONLY; + node->make_decl_local (); + if (!flag_incremental_link) + node->unique_name |= true; + return; + } + } + } + /* For similar reason do not privatize whole comdat when seeing comdat + local. Wait for non-comdat symbol to be privatized first. */ + if (node->comdat_local_p ()) + return; + + if (node->same_comdat_group && TREE_PUBLIC (node->decl)) + { + for (symtab_node *next = node->same_comdat_group; + next != node; next = next->same_comdat_group) + { + next->set_comdat_group (NULL); + if (!next->alias) + next->set_section (NULL); + if (!next->transparent_alias) + next->make_decl_local (); + next->unique_name + |= ((next->resolution == LDPR_PREVAILING_DEF_IRONLY + || next->resolution == LDPR_PREVAILING_DEF_IRONLY_EXP) + && TREE_PUBLIC (next->decl) + && !flag_incremental_link); + } + + /* Now everything's localized, the grouping has no meaning, and + will cause crashes if we keep it around. */ + node->dissolve_same_comdat_group_list (); + } + + node->unique_name + |= ((node->resolution == LDPR_PREVAILING_DEF_IRONLY + || node->resolution == LDPR_PREVAILING_DEF_IRONLY_EXP) + && TREE_PUBLIC (node->decl) + && !flag_incremental_link); + + if (TREE_PUBLIC (node->decl)) + node->set_comdat_group (NULL); + if (DECL_COMDAT (node->decl) && !node->alias) + node->set_section (NULL); + if (!node->transparent_alias) + { + node->resolution = LDPR_PREVAILING_DEF_IRONLY; + node->make_decl_local (); + } + } + /* Decide on visibility of all symbols. */ static unsigned int *************** function_and_variable_visibility (bool w *** 554,562 **** DECL_STATIC_DESTRUCTOR (node->decl) = 0; } ! /* Frontends and alias code marks nodes as needed before parsing is finished. ! We may end up marking as node external nodes where this flag is meaningless ! strip it. */ if (DECL_EXTERNAL (node->decl) || !node->definition) { node->force_output = 0; --- 630,638 ---- DECL_STATIC_DESTRUCTOR (node->decl) = 0; } ! /* Frontends and alias code marks nodes as needed before parsing ! is finished. We may end up marking as node external nodes ! where this flag is meaningless strip it. */ if (DECL_EXTERNAL (node->decl) || !node->definition) { node->force_output = 0; *************** function_and_variable_visibility (bool w *** 607,653 **** if (!node->externally_visible && node->definition && !node->weakref && !DECL_EXTERNAL (node->decl)) ! { ! gcc_assert (whole_program || in_lto_p ! || !TREE_PUBLIC (node->decl)); ! node->unique_name |= ((node->resolution == LDPR_PREVAILING_DEF_IRONLY ! || node->resolution == LDPR_PREVAILING_DEF_IRONLY_EXP) ! && TREE_PUBLIC (node->decl) ! && !flag_incremental_link); ! node->resolution = LDPR_PREVAILING_DEF_IRONLY; ! if (node->same_comdat_group && TREE_PUBLIC (node->decl)) ! { ! symtab_node *next = node; ! ! /* Set all members of comdat group local. */ ! if (node->same_comdat_group) ! for (next = node->same_comdat_group; ! next != node; ! next = next->same_comdat_group) ! { ! next->set_comdat_group (NULL); ! if (!next->alias) ! next->set_section (NULL); ! if (!next->transparent_alias) ! next->make_decl_local (); ! next->unique_name |= ((next->resolution == LDPR_PREVAILING_DEF_IRONLY ! || next->resolution == LDPR_PREVAILING_DEF_IRONLY_EXP) ! && TREE_PUBLIC (next->decl) ! && !flag_incremental_link); ! } ! /* cgraph_externally_visible_p has already checked all other nodes ! in the group and they will all be made local. We need to ! dissolve the group at once so that the predicate does not ! segfault though. */ ! node->dissolve_same_comdat_group_list (); ! } ! if (TREE_PUBLIC (node->decl)) ! node->set_comdat_group (NULL); ! if (DECL_COMDAT (node->decl) && !node->alias) ! node->set_section (NULL); ! if (!node->transparent_alias) ! node->make_decl_local (); ! } if (node->thunk.thunk_p && !node->thunk.add_pointer_bounds_args --- 683,689 ---- if (!node->externally_visible && node->definition && !node->weakref && !DECL_EXTERNAL (node->decl)) ! localize_node (whole_program, node); if (node->thunk.thunk_p && !node->thunk.add_pointer_bounds_args *************** function_and_variable_visibility (bool w *** 757,805 **** if (lookup_attribute ("no_reorder", DECL_ATTRIBUTES (vnode->decl))) vnode->no_reorder = 1; if (!vnode->externally_visible ! && !vnode->transparent_alias) ! { ! gcc_assert (in_lto_p || whole_program || !TREE_PUBLIC (vnode->decl)); ! vnode->unique_name |= ((vnode->resolution == LDPR_PREVAILING_DEF_IRONLY ! || vnode->resolution ! == LDPR_PREVAILING_DEF_IRONLY_EXP) ! && TREE_PUBLIC (vnode->decl) ! && !flag_incremental_link); ! if (vnode->same_comdat_group && TREE_PUBLIC (vnode->decl)) ! { ! symtab_node *next = vnode; - /* Set all members of comdat group local. */ - if (vnode->same_comdat_group) - for (next = vnode->same_comdat_group; - next != vnode; - next = next->same_comdat_group) - { - next->set_comdat_group (NULL); - if (!next->alias) - next->set_section (NULL); - if (!next->transparent_alias) - { - next->make_decl_local (); - next->unique_name |= ((next->resolution == LDPR_PREVAILING_DEF_IRONLY - || next->resolution == LDPR_PREVAILING_DEF_IRONLY_EXP) - && TREE_PUBLIC (next->decl) - && !flag_incremental_link); - } - } - vnode->dissolve_same_comdat_group_list (); - } - if (TREE_PUBLIC (vnode->decl)) - vnode->set_comdat_group (NULL); - if (DECL_COMDAT (vnode->decl) && !vnode->alias) - vnode->set_section (NULL); - if (!vnode->transparent_alias) - { - vnode->make_decl_local (); - vnode->resolution = LDPR_PREVAILING_DEF_IRONLY; - } - } update_visibility_by_resolution_info (vnode); /* Update virtual tables to point to local aliases where possible. */ --- 793,804 ---- if (lookup_attribute ("no_reorder", DECL_ATTRIBUTES (vnode->decl))) vnode->no_reorder = 1; + if (!vnode->externally_visible ! && !vnode->transparent_alias ! && !DECL_EXTERNAL (vnode->decl)) ! localize_node (whole_program, vnode); update_visibility_by_resolution_info (vnode); /* Update virtual tables to point to local aliases where possible. */ diff -Nrcpad gcc-6.3.0/gcc/ira-costs.c gcc-6.4.0/gcc/ira-costs.c *** gcc-6.3.0/gcc/ira-costs.c Tue Feb 2 17:12:56 2016 --- gcc-6.4.0/gcc/ira-costs.c Wed Feb 15 07:04:05 2017 *************** static struct costs *costs; *** 73,79 **** static struct costs *total_allocno_costs; /* It is the current size of struct costs. */ ! static int struct_costs_size; /* Return pointer to structure containing costs of allocno or pseudo with given NUM in array ARR. */ --- 73,79 ---- static struct costs *total_allocno_costs; /* It is the current size of struct costs. */ ! static size_t struct_costs_size; /* Return pointer to structure containing costs of allocno or pseudo with given NUM in array ARR. */ diff -Nrcpad gcc-6.3.0/gcc/ira-int.h gcc-6.4.0/gcc/ira-int.h *** gcc-6.3.0/gcc/ira-int.h Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/ira-int.h Wed Feb 15 07:04:05 2017 *************** struct target_ira_int { *** 782,788 **** /* Initialized once. It is a maximal possible size of the allocated struct costs. */ ! int x_max_struct_costs_size; /* Allocated and initialized once, and used to initialize cost values for each insn. */ --- 782,788 ---- /* Initialized once. It is a maximal possible size of the allocated struct costs. */ ! size_t x_max_struct_costs_size; /* Allocated and initialized once, and used to initialize cost values for each insn. */ diff -Nrcpad gcc-6.3.0/gcc/ira.c gcc-6.4.0/gcc/ira.c *** gcc-6.3.0/gcc/ira.c Thu Mar 31 13:00:52 2016 --- gcc-6.4.0/gcc/ira.c Tue Jun 27 17:11:01 2017 *************** split_live_ranges_for_shrink_wrap (void) *** 4991,5015 **** if (!dest || dest == pic_offset_table_rtx) continue; ! rtx newreg = NULL_RTX; df_ref use, next; for (use = DF_REG_USE_CHAIN (REGNO (dest)); use; use = next) { rtx_insn *uin = DF_REF_INSN (use); next = DF_REF_NEXT_REG (use); basic_block ubb = BLOCK_FOR_INSN (uin); if (ubb == call_dom || dominated_by_p (CDI_DOMINATORS, ubb, call_dom)) { ! if (!newreg) ! newreg = ira_create_new_reg (dest); ! validate_change (uin, DF_REF_REAL_LOC (use), newreg, true); } } ! if (newreg) { rtx_insn *new_move = gen_move_insn (newreg, dest); emit_insn_after (new_move, bb_note (call_dom)); if (dump_file) --- 4991,5030 ---- if (!dest || dest == pic_offset_table_rtx) continue; ! bool need_newreg = false; df_ref use, next; for (use = DF_REG_USE_CHAIN (REGNO (dest)); use; use = next) { rtx_insn *uin = DF_REF_INSN (use); next = DF_REF_NEXT_REG (use); + if (DEBUG_INSN_P (uin)) + continue; + basic_block ubb = BLOCK_FOR_INSN (uin); if (ubb == call_dom || dominated_by_p (CDI_DOMINATORS, ubb, call_dom)) { ! need_newreg = true; ! break; } } ! if (need_newreg) { + rtx newreg = ira_create_new_reg (dest); + + for (use = DF_REG_USE_CHAIN (REGNO (dest)); use; use = next) + { + rtx_insn *uin = DF_REF_INSN (use); + next = DF_REF_NEXT_REG (use); + + basic_block ubb = BLOCK_FOR_INSN (uin); + if (ubb == call_dom + || dominated_by_p (CDI_DOMINATORS, ubb, call_dom)) + validate_change (uin, DF_REF_REAL_LOC (use), newreg, true); + } + rtx_insn *new_move = gen_move_insn (newreg, dest); emit_insn_after (new_move, bb_note (call_dom)); if (dump_file) diff -Nrcpad gcc-6.3.0/gcc/java/ChangeLog gcc-6.4.0/gcc/java/ChangeLog *** gcc-6.3.0/gcc/java/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/java/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/java/jcf-dump.c gcc-6.4.0/gcc/java/jcf-dump.c *** gcc-6.3.0/gcc/java/jcf-dump.c Mon Jan 4 13:03:35 2016 --- gcc-6.4.0/gcc/java/jcf-dump.c Tue Jul 4 07:15:57 2017 *************** static void *** 1226,1232 **** version (void) { printf ("jcf-dump %s%s\n\n", pkgversion_string, version_string); ! printf ("Copyright %s 2016 Free Software Foundation, Inc.\n", _("(C)")); printf (_("This is free software; see the source for copying conditions. There is NO\n" "warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n")); exit (0); --- 1226,1232 ---- version (void) { printf ("jcf-dump %s%s\n\n", pkgversion_string, version_string); ! printf ("Copyright %s 2017 Free Software Foundation, Inc.\n", _("(C)")); printf (_("This is free software; see the source for copying conditions. There is NO\n" "warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n")); exit (0); diff -Nrcpad gcc-6.3.0/gcc/jit/ChangeLog gcc-6.4.0/gcc/jit/ChangeLog *** gcc-6.3.0/gcc/jit/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/jit/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/loop-doloop.c gcc-6.4.0/gcc/loop-doloop.c *** gcc-6.3.0/gcc/loop-doloop.c Thu Jan 14 23:12:53 2016 --- gcc-6.4.0/gcc/loop-doloop.c Fri May 5 21:44:21 2017 *************** doloop_condition_get (rtx doloop_pat) *** 152,161 **** } else inc = PATTERN (prev_insn); ! /* We expect the condition to be of the form (reg != 0) */ ! cond = XEXP (SET_SRC (cmp), 0); ! if (GET_CODE (cond) != NE || XEXP (cond, 1) != const0_rtx) ! return 0; } else { --- 152,164 ---- } else inc = PATTERN (prev_insn); ! if (GET_CODE (cmp) == SET && GET_CODE (SET_SRC (cmp)) == IF_THEN_ELSE) ! { ! /* We expect the condition to be of the form (reg != 0) */ ! cond = XEXP (SET_SRC (cmp), 0); ! if (GET_CODE (cond) != NE || XEXP (cond, 1) != const0_rtx) ! return 0; ! } } else { diff -Nrcpad gcc-6.3.0/gcc/lra-constraints.c gcc-6.4.0/gcc/lra-constraints.c *** gcc-6.3.0/gcc/lra-constraints.c Tue Sep 20 09:19:55 2016 --- gcc-6.4.0/gcc/lra-constraints.c Tue Jun 27 17:11:01 2017 *************** simple_move_p (void) *** 3380,3385 **** --- 3380,3392 ---- lra_assert (curr_insn_set != NULL_RTX); dest = SET_DEST (curr_insn_set); src = SET_SRC (curr_insn_set); + + /* If the instruction has multiple sets we need to process it even if it + is single_set. This can happen if one or more of the SETs are dead. + See PR73650. */ + if (multiple_sets (curr_insn)) + return false; + return ((dclass = get_op_class (dest)) != NO_REGS && (sclass = get_op_class (src)) != NO_REGS /* The backend guarantees that register moves of cost 2 diff -Nrcpad gcc-6.3.0/gcc/lra-remat.c gcc-6.4.0/gcc/lra-remat.c *** gcc-6.3.0/gcc/lra-remat.c Fri Mar 11 22:38:41 2016 --- gcc-6.4.0/gcc/lra-remat.c Tue Jan 17 10:09:47 2017 *************** update_scratch_ops (rtx_insn *remat_insn *** 1116,1121 **** --- 1116,1122 ---- static bool do_remat (void) { + unsigned regno; rtx_insn *insn; basic_block bb; bitmap_head avail_cands; *************** do_remat (void) *** 1123,1134 **** bool changed_p = false; /* Living hard regs and hard registers of living pseudos. */ HARD_REG_SET live_hard_regs; bitmap_initialize (&avail_cands, ®_obstack); bitmap_initialize (&active_cands, ®_obstack); FOR_EACH_BB_FN (bb, cfun) { ! REG_SET_TO_HARD_REG_SET (live_hard_regs, df_get_live_out (bb)); bitmap_and (&avail_cands, &get_remat_bb_data (bb)->avin_cands, &get_remat_bb_data (bb)->livein_cands); /* Activating insns are always in the same block as their corresponding --- 1124,1144 ---- bool changed_p = false; /* Living hard regs and hard registers of living pseudos. */ HARD_REG_SET live_hard_regs; + bitmap_iterator bi; bitmap_initialize (&avail_cands, ®_obstack); bitmap_initialize (&active_cands, ®_obstack); FOR_EACH_BB_FN (bb, cfun) { ! CLEAR_HARD_REG_SET (live_hard_regs); ! EXECUTE_IF_SET_IN_BITMAP (df_get_live_in (bb), 0, regno, bi) ! { ! int hard_regno = regno < FIRST_PSEUDO_REGISTER ! ? regno ! : reg_renumber[regno]; ! if (hard_regno >= 0) ! SET_HARD_REG_BIT (live_hard_regs, hard_regno); ! } bitmap_and (&avail_cands, &get_remat_bb_data (bb)->avin_cands, &get_remat_bb_data (bb)->livein_cands); /* Activating insns are always in the same block as their corresponding diff -Nrcpad gcc-6.3.0/gcc/lto/ChangeLog gcc-6.4.0/gcc/lto/ChangeLog *** gcc-6.3.0/gcc/lto/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/lto/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,26 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-06-22 Martin Liska + + Backport from mainline + 2017-01-06 Nathan Sidwell + + * lto-partition.c (lto_balanced_map): Reformat/respell comment. + (may_need_named_section_p): Likewise. + (rename_statics): Likewise. + (lto_promote_cross_file_statics): Likewise. + + 2017-01-17 Jakub Jelinek + + Backported from mainline + 2017-01-11 Jakub Jelinek + + PR middle-end/50199 + * lto-lang.c (lto_post_options): Force flag_merge_constants = 1 + if it was 0. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/lto/lto-lang.c gcc-6.4.0/gcc/lto/lto-lang.c *** gcc-6.3.0/gcc/lto/lto-lang.c Thu Mar 17 11:07:10 2016 --- gcc-6.4.0/gcc/lto/lto-lang.c Tue Jan 17 20:33:16 2017 *************** lto_post_options (const char **pfilename *** 852,857 **** --- 852,863 ---- support. */ flag_excess_precision_cmdline = EXCESS_PRECISION_FAST; + /* When partitioning, we can tear appart STRING_CSTs uses from the same + TU into multiple partitions. Without constant merging the constants + might not be equal at runtime. See PR50199. */ + if (!flag_merge_constants) + flag_merge_constants = 1; + /* Initialize the compiler back end. */ return false; } diff -Nrcpad gcc-6.3.0/gcc/lto/lto-partition.c gcc-6.4.0/gcc/lto/lto-partition.c *** gcc-6.3.0/gcc/lto/lto-partition.c Wed Jan 27 12:50:05 2016 --- gcc-6.4.0/gcc/lto/lto-partition.c Thu Jun 22 11:14:49 2017 *************** lto_balanced_map (int n_lto_partitions) *** 664,671 **** vnode = dyn_cast (ref->referring); gcc_assert (vnode->definition); ! /* It is better to couple variables with their users, because it allows them ! to be removed. Coupling with objects they refer to only helps to reduce number of symbols promoted to hidden. */ if (!symbol_partitioned_p (vnode) && flag_toplevel_reorder && !vnode->no_reorder --- 664,672 ---- vnode = dyn_cast (ref->referring); gcc_assert (vnode->definition); ! /* It is better to couple variables with their users, ! because it allows them to be removed. Coupling ! with objects they refer to only helps to reduce number of symbols promoted to hidden. */ if (!symbol_partitioned_p (vnode) && flag_toplevel_reorder && !vnode->no_reorder *************** promote_symbol (symtab_node *node) *** 1003,1012 **** "Promoting as hidden: %s\n", node->name ()); } ! /* Return true if NODE needs named section even if it won't land in the partition ! symbol table. ! FIXME: we should really not use named sections for inline clones and master ! clones. */ static bool may_need_named_section_p (lto_symtab_encoder_t encoder, symtab_node *node) --- 1004,1014 ---- "Promoting as hidden: %s\n", node->name ()); } ! /* Return true if NODE needs named section even if it won't land in ! the partition symbol table. ! ! FIXME: we should really not use named sections for inline clones ! and master clones. */ static bool may_need_named_section_p (lto_symtab_encoder_t encoder, symtab_node *node) *************** rename_statics (lto_symtab_encoder_t enc *** 1084,1090 **** || lto_symtab_encoder_lookup (encoder, s) != LCC_NOT_FOUND)) { if (privatize_symbol_name (s)) ! /* Re-start from beginning since we do not know how many symbols changed a name. */ s = symtab_node::get_for_asmname (name); else s = s->next_sharing_asm_name; } --- 1086,1093 ---- || lto_symtab_encoder_lookup (encoder, s) != LCC_NOT_FOUND)) { if (privatize_symbol_name (s)) ! /* Re-start from beginning since we do not know how many ! symbols changed a name. */ s = symtab_node::get_for_asmname (name); else s = s->next_sharing_asm_name; } *************** lto_promote_cross_file_statics (void) *** 1125,1132 **** { symtab_node *node = lsei_node (lsei); ! /* If symbol is static, rename it if its assembler name clash with ! anything else in this unit. */ rename_statics (encoder, node); /* No need to promote if symbol already is externally visible ... */ --- 1128,1135 ---- { symtab_node *node = lsei_node (lsei); ! /* If symbol is static, rename it if its assembler name ! clashes with anything else in this unit. */ rename_statics (encoder, node); /* No need to promote if symbol already is externally visible ... */ *************** lto_promote_cross_file_statics (void) *** 1134,1140 **** /* ... or if it is part of current partition ... */ || lto_symtab_encoder_in_partition_p (encoder, node) /* ... or if we do not partition it. This mean that it will ! appear in every partition refernecing it. */ || node->get_partitioning_class () != SYMBOL_PARTITION) { validize_symbol_for_target (node); --- 1137,1143 ---- /* ... or if it is part of current partition ... */ || lto_symtab_encoder_in_partition_p (encoder, node) /* ... or if we do not partition it. This mean that it will ! appear in every partition referencing it. */ || node->get_partitioning_class () != SYMBOL_PARTITION) { validize_symbol_for_target (node); diff -Nrcpad gcc-6.3.0/gcc/lto-cgraph.c gcc-6.4.0/gcc/lto-cgraph.c *** gcc-6.3.0/gcc/lto-cgraph.c Mon Feb 15 09:30:31 2016 --- gcc-6.4.0/gcc/lto-cgraph.c Wed Jan 11 16:53:52 2017 *************** lto_output_varpool_node (struct lto_simp *** 623,628 **** --- 623,629 ---- } bp_pack_value (&bp, node->tls_model, 3); bp_pack_value (&bp, node->used_by_single_function, 1); + bp_pack_value (&bp, node->dynamically_initialized, 1); bp_pack_value (&bp, node->need_bounds_init, 1); streamer_write_bitpack (&bp); *************** input_varpool_node (struct lto_file_decl *** 1397,1402 **** --- 1398,1404 ---- node->alias_target = get_alias_symbol (node->decl); node->tls_model = (enum tls_model)bp_unpack_value (&bp, 3); node->used_by_single_function = (enum tls_model)bp_unpack_value (&bp, 1); + node->dynamically_initialized = bp_unpack_value (&bp, 1); node->need_bounds_init = bp_unpack_value (&bp, 1); group = read_identifier (ib); if (group) diff -Nrcpad gcc-6.3.0/gcc/lto-streamer-in.c gcc-6.4.0/gcc/lto-streamer-in.c *** gcc-6.3.0/gcc/lto-streamer-in.c Wed Mar 16 16:50:18 2016 --- gcc-6.4.0/gcc/lto-streamer-in.c Thu Jun 22 11:14:13 2017 *************** static void *** 898,910 **** fixup_call_stmt_edges_1 (struct cgraph_node *node, gimple **stmts, struct function *fn) { struct cgraph_edge *cedge; struct ipa_ref *ref = NULL; unsigned int i; for (cedge = node->callees; cedge; cedge = cedge->next_callee) { ! if (gimple_stmt_max_uid (fn) < cedge->lto_stmt_uid) fatal_error (input_location, "Cgraph edge statement index out of range"); cedge->call_stmt = as_a (stmts[cedge->lto_stmt_uid - 1]); --- 898,913 ---- fixup_call_stmt_edges_1 (struct cgraph_node *node, gimple **stmts, struct function *fn) { + #define STMT_UID_NOT_IN_RANGE(uid) \ + (gimple_stmt_max_uid (fn) < uid || uid == 0) + struct cgraph_edge *cedge; struct ipa_ref *ref = NULL; unsigned int i; for (cedge = node->callees; cedge; cedge = cedge->next_callee) { ! if (STMT_UID_NOT_IN_RANGE (cedge->lto_stmt_uid)) fatal_error (input_location, "Cgraph edge statement index out of range"); cedge->call_stmt = as_a (stmts[cedge->lto_stmt_uid - 1]); *************** fixup_call_stmt_edges_1 (struct cgraph_n *** 914,920 **** } for (cedge = node->indirect_calls; cedge; cedge = cedge->next_callee) { ! if (gimple_stmt_max_uid (fn) < cedge->lto_stmt_uid) fatal_error (input_location, "Cgraph edge statement index out of range"); cedge->call_stmt = as_a (stmts[cedge->lto_stmt_uid - 1]); --- 917,923 ---- } for (cedge = node->indirect_calls; cedge; cedge = cedge->next_callee) { ! if (STMT_UID_NOT_IN_RANGE (cedge->lto_stmt_uid)) fatal_error (input_location, "Cgraph edge statement index out of range"); cedge->call_stmt = as_a (stmts[cedge->lto_stmt_uid - 1]); *************** fixup_call_stmt_edges_1 (struct cgraph_n *** 924,930 **** for (i = 0; node->iterate_reference (i, ref); i++) if (ref->lto_stmt_uid) { ! if (gimple_stmt_max_uid (fn) < ref->lto_stmt_uid) fatal_error (input_location, "Reference statement index out of range"); ref->stmt = stmts[ref->lto_stmt_uid - 1]; --- 927,933 ---- for (i = 0; node->iterate_reference (i, ref); i++) if (ref->lto_stmt_uid) { ! if (STMT_UID_NOT_IN_RANGE (ref->lto_stmt_uid)) fatal_error (input_location, "Reference statement index out of range"); ref->stmt = stmts[ref->lto_stmt_uid - 1]; *************** fixup_call_stmt_edges (struct cgraph_nod *** 946,952 **** orig = orig->clone_of; fn = DECL_STRUCT_FUNCTION (orig->decl); ! fixup_call_stmt_edges_1 (orig, stmts, fn); if (orig->clones) for (node = orig->clones; node != orig;) { --- 949,956 ---- orig = orig->clone_of; fn = DECL_STRUCT_FUNCTION (orig->decl); ! if (!orig->thunk.thunk_p) ! fixup_call_stmt_edges_1 (orig, stmts, fn); if (orig->clones) for (node = orig->clones; node != orig;) { diff -Nrcpad gcc-6.3.0/gcc/lto-streamer.h gcc-6.4.0/gcc/lto-streamer.h *** gcc-6.3.0/gcc/lto-streamer.h Thu May 19 14:56:35 2016 --- gcc-6.4.0/gcc/lto-streamer.h Wed Jan 11 16:53:52 2017 *************** along with GCC; see the file COPYING3. *** 129,135 **** form followed by the data for the string. */ #define LTO_major_version 5 ! #define LTO_minor_version 1 typedef unsigned char lto_decl_flags_t; --- 129,135 ---- form followed by the data for the string. */ #define LTO_major_version 5 ! #define LTO_minor_version 2 typedef unsigned char lto_decl_flags_t; diff -Nrcpad gcc-6.3.0/gcc/match.pd gcc-6.4.0/gcc/match.pd *** gcc-6.3.0/gcc/match.pd Fri Dec 9 08:43:50 2016 --- gcc-6.4.0/gcc/match.pd Thu Jun 22 07:30:03 2017 *************** DEFINE_INT_AND_FLOAT_ROUND_FN (RINT) *** 986,1004 **** /* Contract negates. */ /* A + (-B) -> A - B */ (simplify ! (plus:c (convert1? @0) (convert2? (negate @1))) ! /* Apply STRIP_NOPS on @0 and the negate. */ ! (if (tree_nop_conversion_p (type, TREE_TYPE (@0)) ! && tree_nop_conversion_p (type, TREE_TYPE (@1)) && !TYPE_OVERFLOW_SANITIZED (type)) ! (minus (convert @0) (convert @1)))) /* A - (-B) -> A + B */ (simplify ! (minus (convert1? @0) (convert2? (negate @1))) ! (if (tree_nop_conversion_p (type, TREE_TYPE (@0)) ! && tree_nop_conversion_p (type, TREE_TYPE (@1)) && !TYPE_OVERFLOW_SANITIZED (type)) ! (plus (convert @0) (convert @1)))) /* -(-A) -> A */ (simplify (negate (convert? (negate @1))) --- 986,1016 ---- /* Contract negates. */ /* A + (-B) -> A - B */ (simplify ! (plus:c @0 (convert? (negate @1))) ! /* Apply STRIP_NOPS on the negate. */ ! (if (tree_nop_conversion_p (type, TREE_TYPE (@1)) && !TYPE_OVERFLOW_SANITIZED (type)) ! (with ! { ! tree t1 = type; ! if (INTEGRAL_TYPE_P (type) ! && TYPE_OVERFLOW_WRAPS (type) != TYPE_OVERFLOW_WRAPS (TREE_TYPE (@1))) ! t1 = TYPE_OVERFLOW_WRAPS (type) ? type : TREE_TYPE (@1); ! } ! (convert (minus (convert:t1 @0) (convert:t1 @1)))))) /* A - (-B) -> A + B */ (simplify ! (minus @0 (convert? (negate @1))) ! (if (tree_nop_conversion_p (type, TREE_TYPE (@1)) && !TYPE_OVERFLOW_SANITIZED (type)) ! (with ! { ! tree t1 = type; ! if (INTEGRAL_TYPE_P (type) ! && TYPE_OVERFLOW_WRAPS (type) != TYPE_OVERFLOW_WRAPS (TREE_TYPE (@1))) ! t1 = TYPE_OVERFLOW_WRAPS (type) ? type : TREE_TYPE (@1); ! } ! (convert (plus (convert:t1 @0) (convert:t1 @1)))))) /* -(-A) -> A */ (simplify (negate (convert? (negate @1))) diff -Nrcpad gcc-6.3.0/gcc/multiple_target.c gcc-6.4.0/gcc/multiple_target.c *** gcc-6.3.0/gcc/multiple_target.c Wed Dec 7 22:52:39 2016 --- gcc-6.4.0/gcc/multiple_target.c Wed Mar 22 14:32:42 2017 *************** create_dispatcher_calls (struct cgraph_n *** 68,73 **** --- 68,80 ---- " supported by this target"); break; } + else if (!targetm.get_function_versions_dispatcher) + { + error_at (gimple_location (call), + "target does not support function version dispatcher"); + break; + } + e_next = e->next_caller; idecl = targetm.get_function_versions_dispatcher (decl); if (!idecl) *************** create_dispatcher_calls (struct cgraph_n *** 87,92 **** --- 94,100 ---- inode->resolve_alias (cgraph_node::get (resolver_decl)); e->redirect_callee (inode); + e->redirect_call_stmt_to_callee (); /* Since REDIRECT_CALLEE modifies NEXT_CALLER field we move to previously set NEXT_CALLER. */ e = NULL; *************** expand_target_clones (struct cgraph_node *** 283,288 **** --- 291,297 ---- create_new_asm_name (attr, suffix); /* Create new target clone. */ cgraph_node *new_node = create_target_clone (node, definition, suffix); + new_node->local.local = false; XDELETEVEC (suffix); /* Set new attribute for the clone. */ *************** expand_target_clones (struct cgraph_node *** 325,330 **** --- 334,340 ---- tree attributes = make_attribute ("target", "default", DECL_ATTRIBUTES (node->decl)); DECL_ATTRIBUTES (node->decl) = attributes; + node->local.local = false; location_t saved_loc = input_location; input_location = DECL_SOURCE_LOCATION (node->decl); bool ret *************** expand_target_clones (struct cgraph_node *** 334,350 **** return ret; } - static bool target_clone_pass; - static unsigned int ipa_target_clone (void) { struct cgraph_node *node; ! target_clone_pass = false; FOR_EACH_FUNCTION (node) ! if (node->definition) ! target_clone_pass |= expand_target_clones (node, true); return 0; } --- 344,362 ---- return ret; } static unsigned int ipa_target_clone (void) { struct cgraph_node *node; ! bool target_clone_pass = false; FOR_EACH_FUNCTION (node) ! target_clone_pass |= expand_target_clones (node, node->definition); ! ! if (target_clone_pass) ! FOR_EACH_FUNCTION (node) ! create_dispatcher_calls (node); ! return 0; } *************** const pass_data pass_data_target_clone = *** 360,366 **** 0, /* properties_provided */ 0, /* properties_destroyed */ 0, /* todo_flags_start */ ! 0 /* todo_flags_finish */ }; class pass_target_clone : public simple_ipa_opt_pass --- 372,378 ---- 0, /* properties_provided */ 0, /* properties_destroyed */ 0, /* todo_flags_start */ ! TODO_update_ssa /* todo_flags_finish */ }; class pass_target_clone : public simple_ipa_opt_pass *************** make_pass_target_clone (gcc::context *ct *** 388,445 **** { return new pass_target_clone (ctxt); } - - static unsigned int - ipa_dispatcher_calls (void) - { - struct cgraph_node *node; - - FOR_EACH_FUNCTION (node) - if (!node->definition) - target_clone_pass |= expand_target_clones (node, false); - if (target_clone_pass) - FOR_EACH_FUNCTION (node) - create_dispatcher_calls (node); - return 0; - } - - namespace { - - const pass_data pass_data_dispatcher_calls = - { - SIMPLE_IPA_PASS, /* type */ - "dispachercalls", /* name */ - OPTGROUP_NONE, /* optinfo_flags */ - TV_NONE, /* tv_id */ - ( PROP_ssa | PROP_cfg ), /* properties_required */ - 0, /* properties_provided */ - 0, /* properties_destroyed */ - 0, /* todo_flags_start */ - 0 /* todo_flags_finish */ - }; - - class pass_dispatcher_calls : public simple_ipa_opt_pass - { - public: - pass_dispatcher_calls (gcc::context *ctxt) - : simple_ipa_opt_pass (pass_data_dispatcher_calls, ctxt) - {} - - /* opt_pass methods: */ - virtual bool gate (function *); - virtual unsigned int execute (function *) { return ipa_dispatcher_calls (); } - }; - - bool - pass_dispatcher_calls::gate (function *) - { - return true; - } - - } // anon namespace - - simple_ipa_opt_pass * - make_pass_dispatcher_calls (gcc::context *ctxt) - { - return new pass_dispatcher_calls (ctxt); - } --- 400,402 ---- diff -Nrcpad gcc-6.3.0/gcc/objc/ChangeLog gcc-6.4.0/gcc/objc/ChangeLog *** gcc-6.3.0/gcc/objc/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/objc/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/objcp/ChangeLog gcc-6.4.0/gcc/objcp/ChangeLog *** gcc-6.3.0/gcc/objcp/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/objcp/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,7 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/omp-low.c gcc-6.4.0/gcc/omp-low.c *** gcc-6.3.0/gcc/omp-low.c Wed Dec 7 22:55:55 2016 --- gcc-6.4.0/gcc/omp-low.c Thu Jun 22 11:09:08 2017 *************** scan_omp_task (gimple_stmt_iterator *gsi *** 2711,2719 **** tree name, t; gomp_task *stmt = as_a (gsi_stmt (*gsi)); ! /* Ignore task directives with empty bodies. */ if (optimize > 0 ! && empty_body_p (gimple_omp_body (stmt))) { gsi_replace (gsi, gimple_build_nop (), false); return; --- 2711,2721 ---- tree name, t; gomp_task *stmt = as_a (gsi_stmt (*gsi)); ! /* Ignore task directives with empty bodies, unless they have depend ! clause. */ if (optimize > 0 ! && empty_body_p (gimple_omp_body (stmt)) ! && !find_omp_clause (gimple_omp_task_clauses (stmt), OMP_CLAUSE_DEPEND)) { gsi_replace (gsi, gimple_build_nop (), false); return; *************** scan_omp_task (gimple_stmt_iterator *gsi *** 2765,2770 **** --- 2767,2795 ---- } } + /* Helper function for finish_taskreg_scan, called through walk_tree. + If maybe_lookup_decl_in_outer_context returns non-NULL for some + tree, replace it in the expression. */ + + static tree + finish_taskreg_remap (tree *tp, int *walk_subtrees, void *data) + { + if (VAR_P (*tp)) + { + omp_context *ctx = (omp_context *) data; + tree t = maybe_lookup_decl_in_outer_ctx (*tp, ctx); + if (t != *tp) + { + if (DECL_HAS_VALUE_EXPR_P (t)) + t = unshare_expr (DECL_VALUE_EXPR (t)); + *tp = t; + } + *walk_subtrees = 0; + } + else if (IS_TYPE_OR_DECL_P (*tp)) + *walk_subtrees = 0; + return NULL_TREE; + } /* If any decls have been made addressable during scan_omp, adjust their fields if needed, and layout record types *************** finish_taskreg_scan (omp_context *ctx) *** 2885,2890 **** --- 2910,2920 ---- layout_type (ctx->srecord_type); tree t = fold_convert_loc (loc, long_integer_type_node, TYPE_SIZE_UNIT (ctx->record_type)); + if (TREE_CODE (t) != INTEGER_CST) + { + t = unshare_expr (t); + walk_tree (&t, finish_taskreg_remap, ctx, NULL); + } gimple_omp_task_set_arg_size (ctx->stmt, t); t = build_int_cst (long_integer_type_node, TYPE_ALIGN_UNIT (ctx->record_type)); *************** lower_reduction_clauses (tree clauses, g *** 5806,5820 **** if (OMP_CLAUSE_CODE (c) != OMP_CLAUSE_REDUCTION) continue; orig_var = var = OMP_CLAUSE_DECL (c); if (TREE_CODE (var) == MEM_REF) { var = TREE_OPERAND (var, 0); if (TREE_CODE (var) == POINTER_PLUS_EXPR) var = TREE_OPERAND (var, 0); ! if (TREE_CODE (var) == INDIRECT_REF ! || TREE_CODE (var) == ADDR_EXPR) var = TREE_OPERAND (var, 0); orig_var = var; if (is_variable_sized (var)) { --- 5836,5860 ---- if (OMP_CLAUSE_CODE (c) != OMP_CLAUSE_REDUCTION) continue; + enum omp_clause_code ccode = OMP_CLAUSE_REDUCTION; orig_var = var = OMP_CLAUSE_DECL (c); if (TREE_CODE (var) == MEM_REF) { var = TREE_OPERAND (var, 0); if (TREE_CODE (var) == POINTER_PLUS_EXPR) var = TREE_OPERAND (var, 0); ! if (TREE_CODE (var) == ADDR_EXPR) var = TREE_OPERAND (var, 0); + else + { + /* If this is a pointer or referenced based array + section, the var could be private in the outer + context e.g. on orphaned loop construct. Pretend this + is private variable's outer reference. */ + ccode = OMP_CLAUSE_PRIVATE; + if (TREE_CODE (var) == INDIRECT_REF) + var = TREE_OPERAND (var, 0); + } orig_var = var; if (is_variable_sized (var)) { *************** lower_reduction_clauses (tree clauses, g *** 5828,5834 **** new_var = lookup_decl (var, ctx); if (var == OMP_CLAUSE_DECL (c) && is_reference (var)) new_var = build_simple_mem_ref_loc (clause_loc, new_var); ! ref = build_outer_var_ref (var, ctx); code = OMP_CLAUSE_REDUCTION_CODE (c); /* reduction(-:var) sums up the partial results, so it acts --- 5868,5874 ---- new_var = lookup_decl (var, ctx); if (var == OMP_CLAUSE_DECL (c) && is_reference (var)) new_var = build_simple_mem_ref_loc (clause_loc, new_var); ! ref = build_outer_var_ref (var, ctx, ccode); code = OMP_CLAUSE_REDUCTION_CODE (c); /* reduction(-:var) sums up the partial results, so it acts *************** oacc_loop_sibling_nreverse (oacc_loop *l *** 19225,19231 **** static oacc_loop * oacc_loop_discovery () { ! basic_block bb; oacc_loop *top = new_oacc_loop_outer (current_function_decl); oacc_loop_discover_walk (top, ENTRY_BLOCK_PTR_FOR_FN (cfun)); --- 19265,19273 ---- static oacc_loop * oacc_loop_discovery () { ! /* Clear basic block flags, in particular BB_VISITED which we're going to use ! in the following. */ ! clear_bb_flags (); oacc_loop *top = new_oacc_loop_outer (current_function_decl); oacc_loop_discover_walk (top, ENTRY_BLOCK_PTR_FOR_FN (cfun)); *************** oacc_loop_discovery () *** 19234,19242 **** that diagnostics come out in an unsurprising order. */ top = oacc_loop_sibling_nreverse (top); ! /* Reset the visited flags. */ ! FOR_ALL_BB_FN (bb, cfun) ! bb->flags &= ~BB_VISITED; return top; } --- 19276,19283 ---- that diagnostics come out in an unsurprising order. */ top = oacc_loop_sibling_nreverse (top); ! /* Clear basic block flags again. */ ! clear_bb_flags (); return top; } *************** find_link_var_op (tree *tp, int *walk_su *** 19889,19895 **** { tree t = *tp; ! if (TREE_CODE (t) == VAR_DECL && DECL_HAS_VALUE_EXPR_P (t) && lookup_attribute ("omp declare target link", DECL_ATTRIBUTES (t))) { *walk_subtrees = 0; --- 19930,19938 ---- { tree t = *tp; ! if (TREE_CODE (t) == VAR_DECL ! && DECL_HAS_VALUE_EXPR_P (t) ! && is_global_var (t) && lookup_attribute ("omp declare target link", DECL_ATTRIBUTES (t))) { *walk_subtrees = 0; diff -Nrcpad gcc-6.3.0/gcc/params.def gcc-6.4.0/gcc/params.def *** gcc-6.3.0/gcc/params.def Wed Mar 30 07:47:40 2016 --- gcc-6.4.0/gcc/params.def Thu Jun 22 11:19:55 2017 *************** DEFPARAM (PARAM_COMDAT_SHARING_PROBABILI *** 126,132 **** DEFPARAM (PARAM_PARTIAL_INLINING_ENTRY_PROBABILITY, "partial-inlining-entry-probability", "Maximum probability of the entry BB of split region (in percent relative to entry BB of the function) to make partial inlining happen.", ! 70, 0, 0) /* Limit the number of expansions created by the variable expansion optimization to avoid register pressure. */ --- 126,132 ---- DEFPARAM (PARAM_PARTIAL_INLINING_ENTRY_PROBABILITY, "partial-inlining-entry-probability", "Maximum probability of the entry BB of split region (in percent relative to entry BB of the function) to make partial inlining happen.", ! 70, 0, 100) /* Limit the number of expansions created by the variable expansion optimization to avoid register pressure. */ *************** DEFPARAM(PARAM_SELSCHED_MAX_LOOKAHEAD, *** 634,640 **** DEFPARAM(PARAM_SELSCHED_MAX_SCHED_TIMES, "selsched-max-sched-times", "Maximum number of times that an insn could be scheduled.", ! 2, 0, 0) DEFPARAM(PARAM_SELSCHED_INSNS_TO_RENAME, "selsched-insns-to-rename", --- 634,640 ---- DEFPARAM(PARAM_SELSCHED_MAX_SCHED_TIMES, "selsched-max-sched-times", "Maximum number of times that an insn could be scheduled.", ! 2, 1, 0) DEFPARAM(PARAM_SELSCHED_INSNS_TO_RENAME, "selsched-insns-to-rename", *************** DEFPARAM (PARAM_MAX_SSA_NAME_QUERY_DEPTH *** 1191,1197 **** "max-ssa-name-query-depth", "Maximum recursion depth allowed when querying a property of an" " SSA name.", ! 3, 1, 0) DEFPARAM (PARAM_MAX_RTL_IF_CONVERSION_INSNS, "max-rtl-if-conversion-insns", --- 1191,1197 ---- "max-ssa-name-query-depth", "Maximum recursion depth allowed when querying a property of an" " SSA name.", ! 3, 1, 10) DEFPARAM (PARAM_MAX_RTL_IF_CONVERSION_INSNS, "max-rtl-if-conversion-insns", diff -Nrcpad gcc-6.3.0/gcc/passes.def gcc-6.4.0/gcc/passes.def *** gcc-6.3.0/gcc/passes.def Tue Feb 16 20:46:17 2016 --- gcc-6.4.0/gcc/passes.def Wed Mar 22 14:31:55 2017 *************** along with GCC; see the file COPYING3. *** 132,137 **** --- 132,138 ---- POP_INSERT_PASSES () POP_INSERT_PASSES () + NEXT_PASS (pass_target_clone); NEXT_PASS (pass_ipa_chkp_produce_thunks); NEXT_PASS (pass_ipa_auto_profile); NEXT_PASS (pass_ipa_free_inline_summary); *************** along with GCC; see the file COPYING3. *** 151,157 **** NEXT_PASS (pass_ipa_devirt); NEXT_PASS (pass_ipa_cp); NEXT_PASS (pass_ipa_cdtor_merge); - NEXT_PASS (pass_target_clone); NEXT_PASS (pass_ipa_hsa); NEXT_PASS (pass_ipa_inline); NEXT_PASS (pass_ipa_pure_const); --- 152,157 ---- *************** along with GCC; see the file COPYING3. *** 169,175 **** compiled unit. */ INSERT_PASSES_AFTER (all_late_ipa_passes) NEXT_PASS (pass_ipa_pta); - NEXT_PASS (pass_dispatcher_calls); NEXT_PASS (pass_omp_simd_clone); TERMINATE_PASS_LIST () --- 169,174 ---- diff -Nrcpad gcc-6.3.0/gcc/plugin.c gcc-6.4.0/gcc/plugin.c *** gcc-6.3.0/gcc/plugin.c Mon Jan 4 14:30:50 2016 --- gcc-6.4.0/gcc/plugin.c Wed May 10 07:44:41 2017 *************** static const char *str_plugin_init_func_ *** 114,119 **** --- 114,129 ---- static const char *str_license = "plugin_is_GPL_compatible"; #endif + /* Helper function for hashing the base_name of the plugin_name_args + structure to be inserted into the hash table. */ + + static hashval_t + htab_hash_plugin (const PTR p) + { + const struct plugin_name_args *plugin = (const struct plugin_name_args *) p; + return htab_hash_string (plugin->base_name); + } + /* Helper function for the hash table that compares the base_name of the existing entry (S1) with the given string (S2). */ *************** add_new_plugin (const char* plugin_name) *** 183,192 **** /* If this is the first -fplugin= option we encounter, create 'plugin_name_args_tab' hash table. */ if (!plugin_name_args_tab) ! plugin_name_args_tab = htab_create (10, htab_hash_string, htab_str_eq, NULL); ! slot = htab_find_slot (plugin_name_args_tab, base_name, INSERT); /* If the same plugin (name) has been specified earlier, either emit an error or a warning message depending on if they have identical full --- 193,203 ---- /* If this is the first -fplugin= option we encounter, create 'plugin_name_args_tab' hash table. */ if (!plugin_name_args_tab) ! plugin_name_args_tab = htab_create (10, htab_hash_plugin, htab_str_eq, NULL); ! slot = htab_find_slot_with_hash (plugin_name_args_tab, base_name, ! htab_hash_string (base_name), INSERT); /* If the same plugin (name) has been specified earlier, either emit an error or a warning message depending on if they have identical full *************** parse_plugin_arg_opt (const char *arg) *** 273,279 **** /* Check if the named plugin has already been specified earlier in the command-line. */ if (plugin_name_args_tab ! && ((slot = htab_find_slot (plugin_name_args_tab, name, NO_INSERT)) != NULL)) { struct plugin_name_args *plugin = (struct plugin_name_args *) *slot; --- 284,291 ---- /* Check if the named plugin has already been specified earlier in the command-line. */ if (plugin_name_args_tab ! && ((slot = htab_find_slot_with_hash (plugin_name_args_tab, name, ! htab_hash_string (name), NO_INSERT)) != NULL)) { struct plugin_name_args *plugin = (struct plugin_name_args *) *slot; *************** parse_plugin_arg_opt (const char *arg) *** 329,335 **** static void register_plugin_info (const char* name, struct plugin_info *info) { ! void **slot = htab_find_slot (plugin_name_args_tab, name, NO_INSERT); struct plugin_name_args *plugin = (struct plugin_name_args *) *slot; plugin->version = info->version; plugin->help = info->help; --- 341,348 ---- static void register_plugin_info (const char* name, struct plugin_info *info) { ! void **slot = htab_find_slot_with_hash (plugin_name_args_tab, name, ! htab_hash_string (name), NO_INSERT); struct plugin_name_args *plugin = (struct plugin_name_args *) *slot; plugin->version = info->version; plugin->help = info->help; *************** init_one_plugin (void **slot, void * ARG *** 627,633 **** bool ok = try_init_one_plugin (plugin); if (!ok) { ! htab_remove_elt (plugin_name_args_tab, plugin->base_name); XDELETE (plugin); } return 1; --- 640,647 ---- bool ok = try_init_one_plugin (plugin); if (!ok) { ! htab_remove_elt_with_hash (plugin_name_args_tab, plugin->base_name, ! htab_hash_string (plugin->base_name)); XDELETE (plugin); } return 1; diff -Nrcpad gcc-6.3.0/gcc/po/ChangeLog gcc-6.4.0/gcc/po/ChangeLog *** gcc-6.3.0/gcc/po/ChangeLog Wed Dec 21 07:51:43 2016 --- gcc-6.4.0/gcc/po/ChangeLog Tue Jul 4 07:22:46 2017 *************** *** 1,3 **** --- 1,29 ---- + 2017-07-04 Release Manager + + * GCC 6.4.0 released. + + 2017-01-02 Joseph Myers + + * es.po: Update. + + 2016-12-30 Jakub Jelinek + + PR translation/78745 + * exgettext: Handle multi-line help texts in *.opt files. + * gcc.pot: Regenerate. + + 2016-12-30 Joseph Myers + + * es.po, fr.po: Update. + + 2016-12-27 Jakub Jelinek + + * gcc.pot: Regenerate. + + 2016-12-22 Joseph Myers + + * es.po: Update. + 2016-12-21 Release Manager * GCC 6.3.0 released. diff -Nrcpad gcc-6.3.0/gcc/po/es.gmo gcc-6.4.0/gcc/po/es.gmo *** gcc-6.3.0/gcc/po/es.gmo Wed Dec 21 09:21:14 2016 --- gcc-6.4.0/gcc/po/es.gmo Tue Jul 4 09:12:40 2017 *************** *** 1,1439 **** ! Þ•Äð(láèé-ë1‚K‚ `‚Û‚+]ƒ0‰ƒKºƒ „ „„<3„Bp„R³„>…@E…9†…CÀ…F†5K†I†ˆâ†!÷†$‡ >‡_‡"}‡+ ‡#̇ð‡ˆ‡ˆ'¦ˆΈFìˆ33‰Qg‰7¹‰8ñ‰8*Š5cŠ5™Š]ÏŠ<-‹wj‹Iâ‹A,Œ:nŒK©ŒNõŒ9DB~OÁLŽR^Ž;±Ž8íŽ>&IeI¯Bù4<~q?ðD0‘Eu‘@»‘Eü‘CB’=†’PÄ’{“B‘“?Ô“‰”9ž”/Ø”P•CY•F•Eä•E*–Cp–Q´–N—U—Gæ—Œ.˜O»˜R ™C^™Q¢™Fô™9;š=uš=³š4ñšP&›Mw›BÅ›GœIPœ@šœHÛœB$7gIŸžéžEŸ ! LŸ'WŸ8Ÿ.¸Ÿ.çŸ> U )g 0‘ < +ÿ Z+¡+†¡A²¡mô¡8b¢(›¢;Ä¢E£ F£g£|££$¯£$Ô£*ù£*$¤O¤j¤ …¤ ¦¤²¤#äç¤8þ¤!7¥;Y¥E•¥Û¥5ú¥E0¦v¦0”¦LŦ§%§78§lp§Gݧ$%¨JJ¨*•¨EÀ¨2©E9©l©ì©3ª@<ª}ªJ•ª8àªU«o«ƒ«-—«_Å«Y%¬l¬Xì¬TE­Qš­Kì­L8®S…®5Ù®I¯YY¯c³¯"°=:°x°#ˆ°#¬°5а9±1@±3r±*¦±4ѱ.²25²4h²,²6ʲQ³3S³3‡³=»³(ù³"´C6´7z´I²´Iü´WFµEžµ"äµ9¶.A¶"p¶*“¶J¾¶2 ·&<·,c·P·Há·?*¸Fj¸D±¸Fö¸E=¹?ƒ¹=ùNº@PºA‘ºÓº(óº*»:G» ‚»!£» Å»&æ»4 ¼B¼#[¼¼.›¼ ʼë¼.½!3½,U½S‚½pÖ½XG¾U ¾Hö¾.?¿;n¿]ª¿yÀ7‚ÀAºÀ?üÀ!<Á5^Á@”ÁKÕÁ>!Âf`ÂEÇÂ! Ã!/Ã'QÃjyÃ(äÃ* Ä8Ä-OÄ}Ä:”Ä"ÏÄòÄÅ$0Å2UňşÅU¾Å-Æ?BÆ?‚Æ0ÂÆ+óÆAÇ.aÇ*Ç2»Ç2îÇ1!È0SÈ9„È1¾È2ðÈ1#É+UÉ-É3¯É.ãÉDÊ3WÊ$‹Ê+°ÊCÜÊ: Ë[Ë6xË@¯Ë"ðË1Ì4EÌ$zÌDŸÌ1äÌ/Í1FÍExÍ2¾Í-ñÍÎ>Î]ÎEuÎ<»Î;øÎE4ÏFzÏ5ÁÏ9÷Ï*1Ð*\Ð?‡Ð6ÇÐ8þÐX7ÑEÑ3ÖÑ( ! Ò83ÒRlÒV¿ÒQÓUhÓ4¾Ó2óÓZ&Ô`Ô8âÔ/Õ-KÕ"yÕ8œÕ3ÕÕC Ö.MÖ/|Ö ¬Ö(ÍÖöÖN×1e×J—×'â×" ! Ø&-ØTØ1rؤØ%½Ø1ãØ<Ù9RÙŒÙ,¬Ù!ÙÙ&ûÙ("Ú5KÚeÚ%çÚ? Û4MÛ/‚Û=²Û:ðÛ,+Ü6XÜ:Ü3ÊÜ8þÜ7Ý%QÝ6wÝ*®Ý!ÙÝWûÝJSÞ:žÞ3ÙÞ( ß26ßDiß5®ß)äßoà)~à!¨à+Êà:öà=1á3oá!£á9Åá-ÿá%-â6Sâ/Šâ#ºâ9Þâ=ãGVã-žãÌã2èã#ä'?ä.gä4–ä/Ëä1ûäA-å-oå1å=Ïå, æ*:æ/eæ,•æ+Âæîæ* ! ç5çNçJnç¹ç+Ùçpèvèˆè™è+´è-àèé,é@Jé‹é"ŸéÂé:Ùé9ê9Nê"ˆê3«ê!ßêëë5ë#Uë$yëAžëàëTúë-Oì/}ì­ìFÂì í+$í4Pí7…íS½íGî%Yîî!žî*Àîëî$ï,ï*IïtïW”ï-ìï#ð*>ðið!ð £ð Äð,åð#ñ'6ñ"^ñ&ñ¨ñ#Èñ'ìñ"ò&7ò-^òŒò.žò#Íòñòó:,ógózó$™ó%¾óäó#ô'&ôNô6mô¤ô%Ãôéô õ(õCõ%^õ„õ3 õÔõêõ ö]öyö0ö/Àö#ðö÷(÷G÷,b÷A÷*Ñ÷.ü÷!+ø*Mø!xø'šøHÂø5 ù.Aùpù)‡ù)±ù"Ûù#þù"ú3ú$Cú(hú‘ú;«ú(çúû/ûJûiû$‰û0®û5ßûü"+ü"Nü}qü2ïü6"ý4YýCŽýJÒý*þHþ6gþ'žþIÆþ,ÿ.=ÿ1lÿ2žÿ;Ñÿ6 5Dz%šÀÙó30Ct4Š¿+Ý( 2-Q/(¯"Ø,û'(/P1€'²5Ú0'A1i3›6Ï ?'.g-–+Ä ð.*G'r*šÅ]ß =)^"ˆ'«+ÓÿF'n-Ž ¼Ýó1 \7 L” Iá M+ ! Ky ! ZÅ ! k [Œ Kè N4 0ƒ /´ #ä - &6 ] t >‹ +Ê  ö *.Bq,‘¾Ö*ó.+M'y0¡6ÒC :M;ˆÄ+à ,K"kŽ§Ç)ß) 3N e#†ªÀ$Û2Rm„1œ5Î'),V'l0”6Å*ü,'0T-…+³!ß  "C"c"†F©UðPF'—¿'Ò$ú$3D$x'ºâþ-&J*qœ,µâ7ü'4#\€! %Â#è !( JaX*ºådö-[‰Œ2 2ÓMMT0¢Ó Úçð ! 9Tm#‡O«.û9*d/‚²2É*ü.' )V &€ '§ &Ï &ö #!'A!%i!(! ¸!$Ù! þ!"",B"2o"¢"Â"*á", #.9#*h#A“#3Õ#: $1D$)v$ $À$×$)ñ$%8%S%/o%6Ÿ%Ö%3ñ%7%&>]&,œ&,É&1ö&('1D'$v'0›'Ì'7Ó' (+(G(#[((+Ÿ(Ë(ß(÷(ý( ) )4)L)h):z))µ)Jß)C**n*,†*³*º*,Á* ! î*6ù*0+$L+ q+#’+¶+Õ+ò+( ,:4,o,7Œ,(Ä,í,5 -C-W-)q-/›-!Ë- í-'. 6.0W.ˆ. £. ±.Ò.é.ÿ./2/A/-_/"/°/!Ê/)ì/ 0'70Y_0¹0»0Ä0Í0$Ö03û0/1RK1%ž1Ä1Í1Ö1ß1è1!ñ12 /2<2 E2R2[2d2>m2>¬2Fë223I;3…3¡3Hª3Fó3:4->45l4,¢4Ï4 å4†ñ47x5r°5#6*A6<l6.©6Ø6ô657 G7€U7Ö7;Ü7(8+A8.m8+œ8-È8ö8| 9nŠ93ù9A-:ko:7Û:;.';5V;#Œ;&°;$×;ü;<.2<,a<,Ž<*»<%æ<- =J:=+…=$±=+Ö=>>6>)O>.y>$¨>'Í>/õ>%?;A?7}?$µ?Ú?Fñ?"8@![@:}@S¸@3 A?@AQ€ABÒAEB[[B-·B åB‚òB6uC3¬C6àCGDQ_DH±D#úD#E'BE$jEZEDêEJ/F?zF=ºFBøF1;G7mGA¥G*çGGHMZHL¨H=õHK3I;I?»IEûIbAJJ¤JBïJ,2K-_K/KN½K6 LZCL9žL8ØLwMX‰M2âM;N'QNyN0N4ÁNJöN<AOP~OAÏOQPAcP¥P4ÁP<öPM3QEQ/ÇQC÷QG;RzƒR:þR%9SR_S6²SdéS)NT6xT¯T7ÂT'úT*"U/MUA}UL¿U6 VCCVB‡V+ÊV7öV@.W=oW:­WAèWC*XGnX2¶X(éX.YAY;_YM›Y6éY4 Z,UZ,‚Z(¯Z,ØZ([k.[/š[4Ê[.ÿ[+.\/Z\6Š\HÁ\9 ! ]'D]+l]/˜],È],õ]+"^'N^'v^7ž^!Ö^%ø^_/4_:d_AŸ_*á_* `,7`(d``=«`?é`>)aha>a/ÀaDða:5bpb5‹b&Áb?èb (c'Ic4qc¦c&Àc[çc8Cd(|dB¥d;èd6$e4[e"e)³e-Ýe2 f1>f#pf$”f%¹f,ßf3 g-@gng)Šg,´g:ág.hKhhh‡h8£h0Üh) i27i;ji¦i-Ãi6ñi$(j.Mj|j'™j#Ájåj&kA+k,mk-šk+Èk+ôk l,4l#al>…l0Äl;õl 1m3=m qm(}m¦m¿m Îm!Úm ! ümn%n'·€#ö€E+`NŒAÛm‚0‹‚E¼‚*ƒ@-ƒJnƒL¹ƒL„OS„.£„1Ò„%…D*…Ko…»…:Ù…0†$E†j†$††F«†%ò†)‡4B‡tw‡@ì‡:-ˆhˆFˆˆ/ψ#ÿˆX#‰C|‰6À‰1÷‰7)Š*aŠ!ŒŠ*®Š)ÙŠP‹6T‹/‹‹/»‹/ë‹8Œ9TŒ9ŽŒ6ÈŒ7ÿŒ.79f- :Î< Ž/FŽ>vŽ+µŽáŽöŽ' ! 2L>gG¦ î(38 l';µ9ñD+‘Bp‘D³‘Bø‘?;’{’^™’Pø’5I“*“8ª“%ã“$ ”G.”)v”8 ”;Ù”R•+h•:”•.Ï•Kþ•%J–1p–%¢–%È–$î–2—1F—Kx—DÄ—& ˜$0˜"U˜?x˜.¸˜1ç˜t™9Ž™[È™G$š*lš)—šXÁš#›(>›/g›2—›1Ê›aü›^œ@oœ °œ:¾œ&ùœG Jh1³1å6ž3Nž>‚ž,Áž4îžB#ŸHfŸ:¯Ÿ)êŸ& ; !T v ’ ® +Ç ó  ¡2¡:Q¡GŒ¡@Ô¡1¢;G¢ƒ¢”¢£¢¢.×¢£< £5]£5“£3É£ý£5¤D¤#`¤„¤ ¤.š¤0ɤ8ú¤3¥ES¥@™¥>Ú¥<¦<V¦5“¦=ɦ§['§Aƒ§_ŧc%¨D‰¨MΨG©_d©+Ä©3ð©$ª@ªRªdª=uª8³ª1ìª0«-O«-}«>««6ê«.!¬9P¬KŠ¬2Ö¬8 ­BB­0…­/¶­4æ­®57®Bm®,°®3Ý®<¯N¯!n¯+¯?¼¯8ü¯5°>R°5‘°Ç°à°6ý°'4±:\±7—± ϱݱì±( ! ²3²O²1^² ²0²6β?³$E³*j³>•³@Ô³J´F`´E§´9í´@'µhµ)µ8«µ:äµ"¶0B¶6s¶Wª¶U·?X·"˜·n»·@*¸+k¸!—¸_¹¸¹6¹S¹h¹~¹•¹¬¹ ̹!í¹!º#1º#Uº-yºC§º'ëº'»Q;»Y»,ç» ¼Qµ¼+½/3½Bc½j¦½f¾.x¾?§¾Kç¾3¿*H¿!s¿6•¿7Ì¿#ÀB(ÀOkÀ7»À#óÀ7Á#OÁ9sÁ%­Á9ÓÁ% ÂT3ÂiˆÂ)òÂ<Ã)YÃ'ƒÃB«Ã*îÃ'Ä'AÄIiÄ"³Ä:ÖÄ4Å+FÅJrŽÅ'ÙÅ-Æ_/ÆÆ:®Æ?éÆ6)Ç[`Ç)¼Ç æÇJÈ0RÈ;ƒÈO¿È%É;5ÉqɉɥɴÉ7ÓÉ3 Ê3?ÊsÊ-…Ê2³Ê6æÊ#Ë)AËkË*Ë*¬ËU×Ë$-Ì3RÌ*†ÌO±ÌlÍynÍuèÍ:^ÎD™Î)ÞÎÏ"Ï"<Ï _Ï €Ï$¡Ï$ÆÏ"ëÏ"Ð)1Ð'[Ð*ƒÐ)®Ð,ØÐ&Ñ),Ñ'VÑL~ÑKËÑdÒ?|ÒW¼Ò@Ó>UÓ:”Ó:ÏÓ+ ! Ô86ÔMoÔ:½ÔøÔF Õ PÕqÕBÕÐÕçÕ)ûÕ“%Ö ¹Ö4ÚÖ2×3B×$v×7›×Ó×*ê×EØ9[Ø•Ø,°ØÝØ:öØ 1Ù!RÙ6tÙD«Ù4ðÙ%ÚEÚ;`Ú3œÚ.ÐÚ-ÿÚ,-Û9ZÛ+”Û<ÀÛ=ýÛe;Ü:¡ÜHÜÜ,%ÝXRÝ«Ý4¾ÝóÝ# Þ/Þ)GÞ.qÞ& Þ"ÇÞ&êÞ+ß'=ß3eß4™ß4Îß3à?7à%wà à6¾àFõà{<á'¸á?àá# âDâ._â4Žâ%Ãâ)éâã>ã"[ã~ã&›ã&Âã éã0 ! ä(;ädä&}ä+¤ä'Ðä!øäå!:å!\å-~å(¬å"Õå"øå)æ,Eæ ræ+“æ$¿æ)äæ*ç9ç1Uç-‡çµç:Ëç=è5Dè-zè"¨è7Ëè6é8:é<sé7°é?èé5(ê9^ê3˜ê4Ìê9ë8;ëAtë;¶ë7òë%*ì)Pì,zì5§ì"Ýì.í"/í*Rí}í:íÈí.Þí$ îa2î>”î+ÓîBÿî0Bï0sï6¤ïÛï:øï*3ð)^ð1ˆð-ºð/èð)ñ,Bñ(oñ4˜ñdÍñG2ò1zò*¬ò*×òó>"ó0aó7’ó6Êóôô,2ô)_ô(‰ô/²ôâôôô(õ$/õTõ!tõ–õ%¯õ.Õõ8ö5=ösö/ƒö ³ö"Ôö8÷ö0÷"L÷#o÷C“÷(×÷ø!ø8<øuø/Šø'ºø7âøùE9ù)ù)©ùÓù0óùO$ú)túžú½úÚúôú û*ûDûbû)xû!¢ûÄû âû<ü@ü2Vü ‰ü(ªü7Óü# ý/ývGý<¾ý-ûýc)þ.þt¼þF1ÿ!xÿ;šÿ"Öÿùÿ!!6"X8{9´&îFD\>¡ à-r/(¢ËEå:+f.{Rª+ý)F9bCœà=æ$%=c|›»IÁX dwAŠ$Ì,ñ39NmC¼#0$'U}%+Ã5ï% B %a ‡ ¢   Þ ÿ   ! "< ! %_ ! 0… ! )¶ ! 0à !  :* 2e (˜ 0Á ò   $5  Z h } /˜ $È í 'ý % BE )ˆ ² 3Ï &&*-Q12±ä<5A5w1­)ß: (DOm$½)â% 72/jFš4á40K=|6º-ñ2!R6tE«:ñ9,;fF¢ é$õO=j=¨3æ0CK9;É238?lN¬Mû+I!uI—9á3BO/’>ÂJBL~"Z1\Œ é4÷@,0mž:­>èC'k…›µÑç&%*=P@Ž0Ï0C[o)„®Â×6ì-# !Q 's :› BÖ E!8_!/˜!HÈ!¹"Ë"å""ÿ"*"##M#$q#4–#&Ë#0ò#1#$2U$$ˆ$$­$%Ò$0ø$)%C%*]%<ˆ%,Å%ò%&1&L&f&€&š&´&Ô&ï& ! '%'8@'y'8”'Í'è'((!9([(t((«(Ç(ã(4ÿ(4)#Q)'u)!)!¿);á)0* N*"o*9’*6Ì*/+-3+:a+Iœ+0æ+,,>D,4ƒ,4¸,í,' -#3-(W-]€-Þ-@ü->=.A|.7¾.:ö.21/5d/š/K¶/00*<0-g0'•0½0EÙ01':1Bb1¥11Ä1.ö1%2 E2Jf2X±2- ! 3@834y3H®3!÷3¯4TÉ4N5jm51Ø5 ! 6;)64e6:š6Õ6Dï6L47>75À7+ö7+"8LN8/›8(Ë86ô8=+9=i99§94á9,:-C:(q:Cš:'Þ:;D$;'i;@‘;.Ò;0<!2<<T<F‘<6Ø<.=C>=C‚=&Æ=,í=2>DM> ’>1³>å>9?:>?Py?&Ê?<ñ?8.@-g@•@!³@1Õ@.A56A+lAE˜A2ÞA5B2GB.zB>©B>èBH'CEpC0¶C6çC,D6KDU‚D!ØDúDaEU{E/ÑE2F$4FFYF2 F$ÓFNøFAGG;‰G5ÅGtûGGpH—¸H9PI?ŠI:ÊI8J%>J)dJŽJ#®J#ÒJ)öJ‰ K2ªK%ÝK&L+*L&VLU}LÓL&ðL/M/GM8wM4°M!åM+N23N-fN%”N)ºN%äN& ! O+1O]O/zOaªOŒ PP™PjêP'UQ}QQ1¦Q2ØQ' R23RfR2ƒR7¶R2îR=!S8_S6˜S;ÏS4 T9@T4zT9¯T4éTEU7dU6œUcÓUF7V¾~V=WPWhWzWŠWW´W,ÒW0ÿW*0XL[X.¨X×XðX,Y)=Y8gY7 Y1ØY< ! ZBGZCŠZ.ÎZ/ýZ1-[N_[#®[6Ò[Y \Zc\Q¾\O]?`]! ]#Â]Aæ]U(^~^B^)Ò^_ü^\_+t_< _6Ý_>`)S`*}`$¨`$Í`#ò`$a$;a#`aQ„a8ÖaWb5gb6b:ÔbBc@Rc"“c¶c8Öc)d'9d4ad%–d'¼d&äd. e,:ege e*¢eÍeëef(f"Gf4jf'Ÿf=Çf)g(/g/Xg,ˆg*µg,àg$ h2h Hh?ih,©h'ÖhYþh4Xi,i0ºi=ëi0)j:Zj1•j9Çj1k33k5gk1k2Ïk@l1Cl?ul6µl4ìl4!m<Vm>“m=ÒmBn6SnEŠnAÐnOoHbo «oÌo3áo1p6Gp3~p2²p0åp/q)Fq#pq*”q@¿q%r&r?8r#xr'œr(Är5ír#s8s!Qs5ss©s-¼s&ês t2t'Qt*yt%¤t*ÊtAõtC7u6{u7²u4êu6v3VvIŠv%Ôv úv'w-0w^wQ~wHÐwHx#bx†x*™x(Äxíx1 y)?y-iy,—y,Äy<ñy5.z&dz/‹z=»z&ùz% {7F{5~{,´{<á{$|.C|0r|W£|û|9}ON}ž}º} Ù}ú}?~TV~«~-Æ~Dô~:9!tO–!æ<€<E€&‚€<©€Ræ€;9>u8´aí9O‚3‰‚G½‚XƒG^ƒJ¦ƒDñƒY6„l„Lý„;J…G†…?Î…j†Ky†Uņ[‡lw‡Dä‡O)ˆiyˆOãˆ83‰al‰ΉqPŠWŠ8‹†S‹HÚ‹=#Œ?aŒi¡ŒY uevÛ)RŽ)|Ž¦Ž¿Ž?ÖŽ^=u@³dôCYV9ô6.‘:e‘8 ‘)Ù‘-’'1’%Y’O’%Ï’õ’4“2E“x“ •“1¶“è“(”O1”9”$»”?à”8 •;Y•4••+Ê•4ö•-+–Y–3p–¤–(¼–=å–E#—i—'€—¨— ¿—1Í—&ÿ—6&˜8]˜S–˜ê˜+™ 2™ ?™I™c™x™4™5™=ø™<6š7sš;«š.çšC›AZ›ûœ›옜!…3§1Û ž((žQž4pž3¥ž4Ùž1Ÿ>@Ÿ8Ÿ2¸Ÿ-ëŸ8 R $g 4Œ &Á )è 8¡8K¡%„¡)ª¡FÔ¡&¢7B¢.z¢=©¢9ç¢6!£:X£3“£;Ç£:¤:>¤#y¤8¤ Ö¤`à¤`A¥¢¥:·¥Oò¥B¦5[¦*‘¦)¼¦æ¦ §' §*5§>`§BŸ§â§;¨(=¨f¨C€¨ Ĩ$Ѩ7ö¨.©#I©#m©'‘©#¹©MÝ©7+ª9cª7ª.Õª<«6A«>x«;·«Ló«*@¬9k¬¥¬"½¬"à¬P­JT­8Ÿ­zØ­]S®.±®3à®M¯#b¯,†¯)³¯&ݯ/°44°<i°3¦°&Ú°%±J'±r±Ez±7À±=ø±06²5g²‹²@)³<j³+§³-Ó³´´=+´/i´ ™´º´4Ò´)µ:1µ+lµ(˜µ6ÁµøµO¶gd¶5̶$·C'·"k·0Ž·P¿·S¸Ld¸$±¸8Ö¸\¹l¹$…¹ª¹)ƹ#ð¹1º$Fºkº#‡º$«º6к»"&»[I»0¥»:Ö»=¼DO¼F”¼NÛ¼@*½8k½P¤½Hõ½E>¾.„¾"³¾6Ö¾; ¿.I¿.x¿K§¿?ó¿3À&JÀ'qÀ™À"´À.×ÀÁ&ÁDÁ9aÁ4›Á(ÐÁ!ùÁÂ!;Â]Â}ÂMÂ&ÛÂÃ6Ã>HÃ1‡Ã¹Ã%ÓÃ&ùÃ! ÄBÄ(aÄ ŠÄ.«ÄDÚÄ4Å,TÅ"ŤÅG¾Å&ÆB-ÆApÆ)²Æ ÜÆ<êÆ3'ÇG[Ç<£Ç.àÇ:È#JÈnÈ2ŠÈ ½ÈÞÈ)íÈ2ÉJÉ-eÉ3“É'ÇÉ%ïÉ7Ê5MÊ ƒÊ6‘Ê1ÈÊ/úÊ8*ËcË+‚ËB®Ë ñË3ÌvFÌv½Ìc4͘͵Í,ÉÍjöÍ;aÎ!Î'¿Î$çÎ' Ï>4Ï>sÏ>²ÏñÏ ÐÐ8ÐWÐrjЇÝÐ/eÑ!•Ñ9·ÑñÑYÒK_Ò<«Ò”èÒO}Ó1ÍÓ-ÿÓ--Ô-[Ô‰ÔžÔ8¯Ô*èÔ.ÕDBÕ‡Õ Õ·Õ!ÒÕ,ôÕE!ÖgÖ=õÖ43×1h×eš×3Ø34Ø3hØgœØ>Ù|CÙUÀÙ(Ú9?ÚyÚ0“Ú4ÄÚ0ùÚ/*Û%ZÛ$€Û‚¥Û=(Ü"fÜã‰ÜGmÝDµÝSúÝNNÞDÞWâÞ$:ßb_ßÂß1×ß àDà6bà™à*©àÔà òà&á+:áSfá)ºá2äáâ>7â>vâ)µâ?ßâ[ã@{ã^¼ã9äUä)sää3µä0éä#å,>å>kå3ªåÞåöå1æ$Hæ5mæC£æCçæN+ç<zç!·ç"ÙçJüçGè5cèA™èUÛè%1éWé5ué2«é=Þéê/7ê†gêŠîêeyëßë$ùë0ì Oì.pì ŸìÀì3àì&í1;í(mí,–í3Ãí*÷íK"îAnî"°î3Óî)ï31ï4eï šï»ï6Õï4 ð4Að8vð(¯ð'Øð3ñ44ñ;iñ¥ñAÅñGòNOòNžòVíò^Dóc£óiôhqôÚôZõÚõZöÚö\÷Ü÷^ørÞøQùCnù6²ùéù3ú:ú;Yú5•úËú3çú?û3[û$û3´û&èûü,ü(Jü$sü5˜üHÎü2ý-Jý-xý.¦ýAÕýYþqþ6‘þ/Èþøþ)ÿE;ÿ'ÿ&©ÿ1Ðÿ$'>.R0"²2Õ,(5+^,Š&·+Þ+ ! %6"\#Ÿ&Ã7ê*")M)w$¡-Æ+ô% (F#o'“4»'ð& ?+`Œ1«?Ý;Ym<‹[ÈK$p1† ¸9ÄLþWKH£<ìO) Jy [Ä W ! >x ! G· ! )ÿ ! ¹) <ã . *O (z 8£ 4Ü ) 7; +s +Ÿ -Ë tù LnZ»5OL4œ=ÑA7Q5‰-¿;í0)NZa©T G`B¨5ëS!8uB®-ñ2IRNœVëZByDZ\N·CYJ?¤?ä<$JaJ¬0÷2(4[_DðA5iw/áIo[IËXYnTÈKai\ËŽ(:·7òK*Žv’ ˜ g³ !6!L!1b!/”!4Ä!¢ù!}œ"O#qj#.Ü#R $˜^$˜÷$ %M±%ÿ%&<1&Vn&Å&?à&? '7`';˜'"Ô'.÷'&(/E(3u((©(<Ò(I)@Y)š)/´).ä)-*,A*2n*,¡*6Î*"+(+2F+.y+¨+IÇ+!,@3,7t,)¬,8Ö,-9(-3b-N–--å-/."C.%f.Œ.+«.S×.)+//U/…//£/+Ó/1ÿ/-100_0'0,¸0å01$1"319V1+12¼1#ï1-2A2a21z22¬23ß2031D32v34©3-Þ3* 4)74+a4,40º4-ë4&5&@5$g55Œ5Â5 ×5+ø55$6Z6&s6!š6(¼6/å6H7H^7/§7/×78'$8&L85s82©8XÜ859N9^9p9€9$9(µ9(Þ9::):A:]:w:*: ¸:Â:$Õ:ú:!;+8;Gd;A¬;5î;$<"?<Ib<I¬<Bö<;9=8u=1®=0à=7>&I>,p>&>Ä>8ä>?-8?-f?,”?=Á?=ÿ?==@={@ ¹@)Å@)ï@2A1LAW~A-ÖA9B>B\B2uB1¨BÚBõB=CoRCÂC"ÛC#þC("D&KD-rD: D;ÛDHE`E0|E'­EÕEõEF'FFF^F {F'œFÄFáFüF/ G)=GgG„G"•G2¸GDëG!0H+RH,~H«H4ÊH'ÿH'I?EI…I™I ¹IÚIyùI%sJ™J!²J!ÔJ1öJ (K3IK#}K¡KGºKL:L"SLvL4L(ÂLëLM0MBIM>ŒM9ËM!N5'N-]NA‹NÍNíN O+O>O?QO‘O­OÍO5éOP5=P*sP>žPaÝP.?QnQ*‰Q1´Q3æQR-0R%^R9„R<¾RNûRDJSKS?ÛS@T4\TK‘TYÝT"7UZUDqU*¶U;áUV&3VZV$wV!œV¾V)ÜV(W/W7IW\W&ÞW6X,`@X`F™`Cà`C$a1ha0ša1Ëa%ýaX#b'|bE¤b:êb/%c9Uc!c*±cNÜc0+d=\d@šd>Ûd1e0Le}e%œe4ÂeI÷e#Af9ef-Ÿf5Íf8g=y3¸kì7X€R€>ã€0"LSS Jô4?‚@t‚%µ‚KÛ‚K'ƒNsƒ>ƒg„Vi„%À„*æ„…B…D\…D¡…:æ†:!‡\‡*|‡#§‡!ˇ@í‡g.ˆB–ˆ4Ùˆ4‰;C‰0‰°‰Љiï‰)YŠ)ƒŠ­Š ÍŠÛŠ ìŠ ! öŠ ‹+ ‹:7‹0r‹5£‹2Ù‹/ Œa<Œ;žŒ+ÚŒ9e@=¦@ä%Ž>8Ž-wŽ:¥ŽàŽ0âŽ>bR7µ$í6)ILs<À7ýE5‘,{‘W¨‘?’@’3_’3“’BÇ’? ! “CJ“(Ž“&·“Þ“+ô“% ”iF”M°”1þ”10•Eb•%¨•#Ε%ò•8–8Q–3Š–1¾–Bð–*3—^—;|—=¸—5ö—9,˜*f˜\‘˜8î˜1'™5Y™/™2¿™ò™2ö™5)šQ_š&±šJØš'#›.K›4z›8¯›/è›%œ$>œ%cœ#‰œ)­œ)ל-"/R)g-‘¿-Ó(ž**žUž.mžAœž0Þž/Ÿc?Ÿ9£Ÿ<ÝŸ4 3O >ƒ 3 7ö [.¡ Š¡ –¡.¤¡$Ó¡&ø¡I¢Ii¢³¢JÓ¢#£>B£+£)­£%×£/ý£<-¤.j¤%™¤¿¤/Þ¤?¥8N¥)‡¥±¥1Ê¥;ü¥<8¦9u¦<¯¦8ì¦;%§5a§8—§Ч+ì§+¨+D¨+p¨$œ¨"Á¨*䨩;(©d©:„©5¿©‹õ©2ªE´ª<úª27«(j«0“«0Ä«*õ«0 ¬(Q¬*z¬,¥¬'Ò¬ ú¬+­&4­9[­•­1¦­&Ø­/ÿ­@/®.p®$Ÿ®5Ä®4ú®4/¯;d¯< ¯ ݯ꯰°!9°%[°%°!§°'É°ñ°& ±2±'9±(a±<Š±0DZ%ø±2²>Q²'²¸²NÔ².#³ ! R³.]³:Œ³)dz)ñ³5´EQ´A—´4Ù´4µ Cµdµ,µ$¬µ"ѵ.ôµ%#¶%I¶$o¶”¶4«¶à¶2ö¶)·TH·L·[ê·WF¸Dž¸Pã¸C4¹0x¹&©¹й æ¹9ô¹#.º)Rº|º.’º(Áº>êº")»2L»3»Q³»,¼)2¼0\¼H¼2Ö¼ ½''½*O½ z½†½£½ À½%á½%¾-¾C¾T¾f¾x¾$‹¾ °¾Ѿ%â¾/¿%8¿,^¿,‹¿.¸¿,ç¿,À,AÀ,nÀ*›À&ÆÀ/íÀÁ2Á ;Á#GÁ!kÁ"Á°ÁÏÁîÁ Â7ÂMÂ]Âq zÂ'›ÂÃÂ+âÂ'Ã"6Ã#YÃ)}çÃÇÃçÃ!Ä#)Ä!MÄ$oĔĬÄÅÄ(ÙÄ"ÅH%Å=nÅ/¬Å'ÜÅ0Æ%5Æ+[Æ/‡Æ'·Æ(ßÆÇWÇ9uÇ4¯ÇäÇ&öÇ,È$JÈoÈ+ŽÈ6ºÈñÈ5úÈ0ÉOÉkÉ…É¥É8ÂÉ>ûÉ!:Ê\Ê=|Ê ºÊ-ÛÊ Ë$ËH;Ë)„Ë)®Ë/ØË@Ì-IÌ.wÌ ¦ÌN³Ì.Í(1Í1ZÍ6ŒÍ3ÃÍ3÷Í5+Î=aÎJŸÎ*êÎ"Ï08ÏiÏ„ÏœÏ)¹Ï"ãÏ*Ð*1ÐP\ÐA­Ð+ïÐ4Ñ6PÑ2‡Ñ"ºÑÝÑ9öÑ0ÒAÒ7_Ò!—Ò"¹ÒÜÒ>ôÒ>3ÓDrÓ7·Ó'ïÓ.ÔMFÔH”ÔÝÔ.üÔ +Õ'LÕ-tÕ=¢Õ3àÕÖ/Ö;MÖ#‰Ö6­Ö:äÖ5×U×tׇך×)³×#Ý×(Ø'*Ø&RØ"yØ3œØÐØäØúØ$Ù9ÙPÙmÙÙ™Ù³Ù*ÌÙ ÷Ù ÚÚ/ÚBÚRÚ9gÚ.¡Ú3ÐÚ/Û04Û3eÛ;™ÛFÕÛÜ:Ü#ZÜ~Ü+œÜ.ÈÜ÷Ü!Ý,9ÝfÝ1€Ý-²Ý'àÝ-Þ+6Þ#bÞ †Þ#§Þ-ËÞùÞVß*mß&˜ß&¿ß)æß/à4@à+uà7¡à9Ùà8áLá%ká5‘á ÇáTèá7=â6uâ7¬âäâ1ýâ6/ã-fãT”ã9éã$#ä8Hä+ä<­äêä åå,å=å"Zå'}å¥å»å)Ùå<æ(@æ'iæ/‘æ'Áæ1éæ?ç:[ç–ç$¶çÛç1ôç&è35è'ièo‘è)é3+é_é1}éF¯éEöén<ê3«ê2ßê.ë'Aë7ië.¡ë-Ðëþë6ìSì$nìB“ì)Öì*í&+í&Rí0yí&ªíÑí ïí)î2:î4mî¢î;¿î,ûî1(ï0Zï(‹ï/´ï4äïð%2ð)Xð)‚ð@¬ð$íð<ñ.Oñ4~ñ0³ñäñþñGòLcòL°ò.ýò1,ó/^ó8ŽóPÇó0ô'Iô&qô˜ô$®ôÓôìô+õ+0õ-\õ;Šõ5Æõ-üõD*ö5oö¥ö"Åö èö!òö÷3÷/D÷(t÷'÷<Å÷$ø'ø<øQøjø~ø/šøÊø>êø6)ù>`ù;ŸùÛù0÷ù.(ú3Wú9‹ú8Åú þúûB>ûLû&Îû:õû$0üUü1mü<Ÿü;Üü.ý5Gý1}ý1¯ý.áý.þ5?þ5uþ>«þCêþ..ÿ/]ÿÿ/¦ÿ+Öÿ-&0W"o'’5º(ðN/X~8×:+K4w9¬9æ+ ,L y/š$Êï,)V(i2’4Å2ú(-V"v&™)À.ê.3ab9Ä,þ6+2bU•(ëG>\A›$Ý$ ,' (T B} LÀ  ! - ! .J ! 'y ! H¡ ! 4ê ! P &p .— /Æ *ö 9! +[ .‡ <¶ )ó D Sb T¶ K WCu'¹Eá@'<hD¥@êL+5xB®(ñ;#VFzÁ8Ü<JR,@Ê #+C@oL°Pý;N7Šc &,G t*•-À%î.Cc6|&³1Ú #* N+o›)»)å+Ff#{-Ÿ7Í)%/$U4z*¯1Ú1 0>o6…"¼ßû9/0i'š-Âð$ ,2B_<¢5ß,&+S30³/ä*9?#G)k%•3»Jï':b5v&¬6Ó' ! +2 /^ 'Ž ,¶ 1ã G!>]!!œ!/¾!(î!)"#A"#e"a‰""ë" #/#4O#>„#5Ã#/ù#+)$+U$($$ª$9Ï$. %C8%F|%.Ã%*ò%F&.d& “&6¡&CØ&'0<'m'+‡'#³'!×'-ù'$'($L(#q(•(R©( ü(),;)?h)/¨)0Ø)2 */<*5l*V¢*<ù*S6+UŠ+cà+ED,NŠ,Ù,Lô,-A-+o-7›-:Ó-1.8@.&y.* .1Ë.3ý.'1/%Y/$/;¤/.à/F0V0l0K†01Ò0"1 '1CH1BŒ1Ï1è1*2+-2*Y21„2'¶2FÞ2=%3#c3#‡39«3å34 4:4S4&j4‘44£4Ø46ø4#/5S5-d5,’5%¿5å5$ÿ5$6&C6)j6”6¨6¿6 Ö6 ä6%ò607GI7‘7°7Ð7*å78&'8?N8(Ž8(·8à8 97!9-Y9‡9›9»9Ñ9$ê9!:1:RQ:.¤:PÓ:*$;/O;3;!³;KÕ;!<@<4[<<+¤<+Ð<ü<=2=R=r= = °=4Ñ=/>#6>Z>:l>E§><í> *?!K?m?Š? ?*¹?ä?5@J9@T„@SÙ@8-AfA5uAH«AôA/B3?B+sBAŸBáB8øB71C+iC2•C3ÈC3üC>0D$oD,”D4ÁD&öD6E6TE‹E‘E"¦E!ÉE!ëE" F0FKF$gF%ŒF²FÎF$ëFG"G:G*BG7mG'¥G'ÍG$õG$H)?H%iH%H$µH%ÚHII8I QI3rI3¦I)ÚIJ$J3JQJ`JUoJÅJÔJìJKK6KUKdKuK„KžK8·KðKL%L&5L%\L+‚L®L9ÆLM#MCMRM:aMœM«M½MØMìMþM NN!3N"UNxN‰NœN1¯NáN÷N OO6OGOgO}O‘O¬OÂOÕOæOùO PP3PBPaP5pP(¦PJÏP+QFQbQ~Q”Q¥Q¹QÌQ4àQR!*RLR*lR—R0«RÜRùRS"S4SKS_S|S™S¶SËS*çS0TCT`TxT$“T%¸TÞTöTU+U&=UdUuU‘UA§U@éU*V!GViV|V”V¬VÇVâV÷VW,WDWWWoWK‡WFÓWPXLkX¸XÖX<õX92YUlY0ÂY+óY/Z<OZ9ŒZ,ÆZ2óZ.&[DU[+š[+Æ[<ò[u/\^¥\_]6d]›]+»]Cç]0+^D\^.¡^AÐ^=_AP_(’_I»_&`),`>V`•`B®`ñ` a'a$Eaja*…a°aÐa.àa,b6Äz;{-?{m{!‰{-«{'Ù{9|%;|)a|(‹|/´|2ä|$}-<}0j}R›}=î}$,~5Q~‡~ž~+¼~'è~8Ig*ƒ®4Ì,€/.€<^€›€"µ€!Ø€#ú€.1M ! ’-(Ë-ô$"‚-G‚)u‚Ÿ‚¹‚:Õ‚-ƒ.>ƒmƒ0ƒƒ/´ƒ-äƒ4„6G„*~„6©„#à„#…1(…7Z…5’…È…6Ü…J†@^†6Ÿ† Ö†)÷†$!‡'F‡/n‡,ž‡ˇ6â‡;ˆ9Uˆ3ˆCÈS‰,[‰"ˆ‰#«‰$ωHô‰L=Š.ŠŠ>¹ŠøŠ ‹%‹A‹]‹y‹:’‹OÍ‹HŒEfŒ$¬ŒSÑŒY%ZcÚD>ŽbƒŽ6æŽ ,)M<w´9ÄAþ@Wj ~"‹E®FôB;‘!~‘: ‘1Û‘@ ’:N’1‰’(»’ä’#“((“Q“%p“.–“'Å“í“;”<D”?”)Á”&ë”,•1?•Jq•0¼•,í•.–=I–H‡–%Ж'ö–—-.—'\—„—¤—0Ä—õ—+˜#;˜!_˜-˜$¯˜$Ô˜#ù˜?™3]™,‘™¾™6Ô™ š.'š1Vš5ˆšU¾š[›\p›eÍ›F3œdzœaßœgAh©qžR„žpמ HŸ>iŸ-¨Ÿ-ÖŸ9 I> Eˆ 8Π8¡)@¡;j¡G¦¡Fî¡+5¢a¢/¢-¯¢0Ý¢2£#A£e£+‚£*®£*Ù£*¤9/¤<i¤6¦¤!ݤ1ÿ¤41¥1f¥:˜¥Ó¥Eó¥>9¦/x¦"¨¦-˦,ù¦@&§3g§›§#·§,Û§#¨1,¨%^¨/„¨3´¨3è¨/©5L©"‚©&¥©Ì©å©.ô©D#ª$hª)ª&·ª)Þª0«19«k«;†«0«5ó«3)¬*]¬8ˆ¬Á¬0à¬'­I9­2ƒ­8¶­ï­&®*.®'Y®®›®"¸® Û®5ü®D2¯Pw¯:ȯ5°9°K°8b°)›°0Å°-ö°*$±*O±z±±¢±²±Ʊڱ²&²8²J²[²m²²—²«²¼²βà²ñ²³³+³=³Q³c³u³‰³›³­³¿³ѳå³ù³ ´´1´E´W´k´}´‘´¢´¶´È´Ú´ì´þ´µ$µ6µJµ\µpµ†µœµ®µÀµÒµ/䵶($¶M¶g¶z¶¶#«¶϶ﶷ·1·/O·6·!¶·Ø·÷·'¸'/¸'W¸"¸)¢¸̸1ä¸3¹0J¹4{¹/°¹)à¹G ! º1Rº*„º!¯º!Ѻ%óº»9» R»&s»<š»!×»(ù»/"¼&R¼*y¼+¤¼)м&ú¼3!½U½,q½7ž½Ö½ó½/¾)4¾.^¾0¾¾¾:Þ¾¿#7¿"[¿!~¿& ¿!Ç¿,é¿ À"7À'ZÀ‚À) À!ÊÀ5ìÀ"Á:5Á(pÁ&™Á)ÀÁêÁ1 ! Â<Â!ZÂ+|Â2¨Â>Û Ã&;ÃbÃÃNŸÃîÃ$ ÄT0ÄK…ÄÑÄ)åÄ+Å ;Å.IÅxÅ$–Å#»ÅßÅ+ýÅ)Æ IÆ.VÆ#…Æ'©Æ'ÑÆ(ùÆ*"Ç+MÇ"yÇ1œÇ!ÎÇ(ðÇ!È;ÈKÈcÈ}È ˜È ¹È ÚÈ ûÈ É =É ^É É  É ÁÉ!âÉ Ê%Ê%CÊ#iÊ#Ê"±ÊÔÊôÊË'Ë)EË)oË)™ËÃËãËÿËÌ7ÌNÌjÌ̡̽ÌÙÌõÌÍ-Í0IÍ?zÍ[ºÍ#Î/:Î$jÎ%Î%µÎ3ÛÎ#Ï03ÏdÏ {Ï+œÏÈÏ3ÞÏÐ"-ÐPÐ iÐ1ŠÐ¼Ð%ÙÐ%ÿÐ0%Ñ.VÑ2…Ñ$¸ÑÝÑ÷Ñ)Ò?ÒXÒ)wÒ2¡Ò#ÔÒ%øÒÓ=4Ó$rÓ)—ÓÁÓ#×Ó-ûÓ&)Ô!PÔ#rÔ#–ÔºÔ<ÎÔ Õ8)Õ$bÕ ‡Õ*¨Õ2ÓÕ7Ö/>Ö"nÖ'‘Ö¹Ö9ØÖ×,,×)Y×-ƒ×&±×'Ø×Ø Ø4@Ø,uØ%¢ØÈØÞØ.öØ%Ù$AÙ.fÙ•Ù+¨Ù7ÔÙ ÚÚ5Ú>QÚDÚ2ÕÚ,Û.5Û[dÛmÀÛ(.Ü!WÜ'yÜ'¡Ü$ÉÜ7îÜ#&ÝJÝ)jÝ-”Ý(ÂÝ(ëÝ(Þ(=Þ&fÞ3Þ.ÁÞ*ðÞAß9]ß—ßL«ß/øß(à/Gà.wà(¦à%Ïàõàá#%áIá!iá+‹á/·á4çá:â Wâ7dâ1œâ.Îâ(ýâ1&ã.Xã‡ã!™ãE»ã)ä<+ähä9ˆäÂä"áäåå)åCå,bå*å*ºå#åå! æ!+æ!Mæ!oæ$‘æ"¶æ#Ùæ#ýæ#!ç"Eçhçˆç-¦ç)Ôç þçè?è"_è‚è&¢è'Éè+ñè(éFé%fé"Œé ¯éÐéðé7êfHêV¯ê5ë<ë#Cëgë‡ë§ë,¾ë"ëëìA"ì(dì$ì²ì'ÍìCõì39í"míí«íLÉí,îHCîŒî ›î"¼îßî!ýîï3<ïHpï¹ï Éïêï! ! ð',ð,Tðð5ðÆð=ÞðWñFtñm»ñ)òIò7`ò0˜ò1Éò2ûò/.ó;^ó.šó>Éó6ô!?ô0aô1’ô/Äô2ôô2'õ8Zõ “õ@´õ#õõö&9ö`ö${ö$ ö-Åö&óö ÷-;÷i÷†÷*¤÷!Ï÷*ñ÷%øBø\øsø’ø+°øÜø!üøù%:ù`ù${ù ù$»ù&àù$ú/,ú7\ú-”ú*Âú$íú.û6Aû'xû@ û%áûü%ü;Dü!€ü¢ü ¿üËü%æü! ý.ýNý-hý/–ý5Æý/üý",þGOþ3—þ'Ëþ$óþÿ5ÿ8Tÿ6ÿ@Äÿ2M8?†?Æ1;85t5ª%à62=+p1œIÎ?76wA®.ð3,S)€(ª0Ó:.?&n@•$Öû77M…$š,¿)ì4"K=n.¬*Û*,1,^‹¢²Ê!é) %5 %[  &• ¼ Ú (í  ! * ! E ! /` !  ! "­ ! !Ð ! ò !   * 4: o !†  ¨ (É 8ò 9+ &e Œ  0¾ 1ï E! 7g KŸ !ë " 0Obl%Ïõ(+:+f&’+¹å)ý0'%X~ œ'½.å2!G,ij–2'4@\º2Õ 5)<_+œ.È2÷3*6^M•Dã=(%f5ŒÂ/Û# /6D#{Ÿ ´Õõ$w œ/½'í'8=-v"¤$Ç#ì()9-c'‘G¹-H\'z ¢¯ Î$ï#!8.Z‰5£Ùõ- 7Me/tC¤5è"/A+q2;Ð3 "@&c&Š#±#Õ"ù"?_'}(¥Î2å &5 #\ "€ -£ ,Ñ þ /!(I!r!"’!Cµ!ù!$"5<"4r"'§"!Ï"Eñ"+7#Bc#,¦#;Ó#$3)$4]$’$/®$.Þ$+ %9%*X%-ƒ%0±%'â%/ ! &4:&*o&,š&'Ç&(ï&&'?'(O'Dx'.½'1ì'((RG(9š(4Ô(. )H8)!)(£)EÌ)E*$X*)}*1§*(Ù*&+:)+d+:t+K¯+Mû+6I,+€,¬,É,*ä,-$$-I-h-!‡-©-/Å-õ-ú-4. 6.C.5Y.,.<¼.5ù.&//1V/Lˆ/HÕ/050\R03¯07ã0*1.F1,u1"¢14Å11ú14,25a2(—2À2BÞ2:!3&\3>ƒ3*Â3$í3(4$;4$`4(…4<®4Aë45-5)c525"À5ã5ö5! 6+6J6Ae6@§6:è69#79]7H—7.à7&868%R86x83¯8*ã8/9!>9%`9D†9"Ë9î9::/#:/S:!ƒ:¥:=½:û:H;!^;>€;2¿; ò;C<3W<<‹<È<)è<+=%>=%d=+Š=¶=Ê=æ=>%%>(K>"t>7—>QÏ> !?B?$a?-†?6´?5ë?!@(A@'j@)’@¼@$Ù@+þ@%*A"PA-sA¡A%½A!ãA!B<'B>dB,£BÐBíB@ C'MC!uC —C¸CÓC8ïC1(D5ZD*D»D7ÒD1 ! EL¸\N÷\MF]3”]È]Ú]%ú]+ ^$L^6q^<¨^7å^5_AS_7•_TÍ_T"`>w`F¶`%ý`-#a+Qa6}a-´a.âa-b,?b*lb —b ¸b1Ùb cc,;chcˆc¨c#ÅcécJÿc%Jd&pd&—d&¾d ådDeKeieLeAÎef.fKf`fuf)Šf´fÓf0ðf8!gZg,zg,§gFÔg$h@h ^hh'˜h'Àh2èh$i;@i>|i>»i9úi-4j3bj–j@´j4õj)*kTkkkk(˜kÁk<×kDl=Yl]—l#õlCm,]m<ŠmIÇm.n @n2an'”n4¼n$ñn-o Doeoyo4o)Âo6ìo+#p%Op1up=§p0åp0qGqfq…q$¥q!Êq7ìq!$r1Fr0xr)©r1Ór;s9As${s# s ÄsMås-3tIat«t!»t#Ýtu" uCu*au$Œu$±u6Öu( vJ6v&v5¨v5Þv:w=Ow/w*½w;èw%$x'Jx-rx< xVÝx64yRkyˆ¾y8GzB€z@Ãz9{&>{4e{$š{3¿{'ó{|89|4r|%§|+Í|ù| }7}+W}"ƒ}¦}¸} ! Ð} Û}ü}$~2>~4q~ ¦~)°~#Ú~þ~%+=i8‡&Àç€'$€L€4f€›€$¶€(Û€5 :*[!†"¨"Ëî ‚!$‚F‚`‚/}‚­‚‚&Ù‚ƒ ƒ9ƒ"UƒSxƒ̃ëƒ ! „)„H„?Y„>™„6Ø„*…!:…\…#k…*…)º…,ä…4†)F†=p†(®†=׆,‡AB‡5„‡4º‡)ï‡)ˆ-Cˆ@qˆ"²ˆ*Õˆ+‰,‰-B‰'p‰)˜‰C‰UŠF\Š0£Š&ÔŠ5ûŠ'1‹ Y‹5z‹°‹É‹è‹$Œ,ŒLŒ4iŒJžŒ7éŒ!39-m(›ÄVÝ)4Ž^ŽzŽ0–Ž9ÇŽ!'#'K9s3­;á;6Y/2À2óI&‘3p‘!¤‘3Æ‘/ú‘3*’3^’’’)²’)Ü’+“/2“2b“$•“-º“@è“:)”$d”!‰”#«” ϔ𔕠•'5•]•(r•Z›•-ö•/$–+T–"€–£–·–Í–8é–2"—6U—8Œ—$Å—.ê—9˜(S˜(|˜4¥˜9Ú˜7™=L™3Š™/¾™4î™.#š.Rš4š.¶š.åš,›9A›9{›9µ›:ï›9*œ:dœ9Ÿœ9ÙœWWk.Ãò$ž!,ž/Nž&~ž)¥žÏžëž ! Ÿ.Ÿ LŸ0mŸ#žŸ=Ÿ+ $, Q !q  “ -´ â !þ + ¡-L¡$z¡.Ÿ¡(Ρ.÷¡&¢16¢.h¢*—¢/¢Bò¢35£Bi£'¬£"Ô£+÷£3#¤@W¤D˜¤%ݤ¥+#¥O¥n¥4Ž¥-Ã¥(ñ¥<¦W¦#u¦™¦(¶¦ߦ}§†–§6¨MT¨:¢¨6ݨ6©/K©%{©5¡©&ש7þ©G6ª~ª@–ª2ת$ ! «/« C«:d«3Ÿ«3Ó«@¬@H¬;‰¬Ŭ٬­,­?­T­h­}­‘­¦­¼­Эæ­®®'®8®R®g®}®“®¦®¹®9Ñ®M ¯MY¯@§¯Cè¯(,°3U°%‰°=¯°(í°7±ZN±Y©±N²2R²-…²F³²4ú²+/³+[³,‡³+´³+à³, ´,9´,f´4“´YÈ´H"µWkµXõ-¶5J¶A€¶v¶79·lq·5Þ·;¸UP¸5¦¸Qܸˆ.¹>·¹4ö¹>+º1jº2œºϺ.ﺻ<0»2m»  »Á»2Þ»(¼E:¼E€¼.Ƽ3õ¼c)½½X­½B¾HI¾:’¾F;1¿'F¿n¿%‡¿­¿*Ë¿"ö¿!À);À eÀ†À6¥À ÜÀRýÀ/PÁ$€Á¥Á ºÁÛÁîÁ2 Â/?Â/oÂ(ŸÂÈÂ&â Ã#(Ã"LÃoÃ*ŠÃ!µÃ ×Ã,øÃ*%ÄPÄ3pĤÄÂÄ×Ä)ôÄ7Å!VÅ#xÅ0œÅ&ÍÅ#ôÅ/ÆAHÆ%ŠÆ8°ÆMéÆ67Ç8nÇ.§Ç3ÖÇ- ! ÈC8È,|È>©È&èÈVÉ'fÉDŽÉFÓÉQÊClÊ=°Ê8îÊ;'ËOcË-³ËáË0üË/-Ì]Ì/sÌD£Ì1èÌ,Í0GÍxÍ8”Í'ÍÍ&õÍ+Î%HÎ#nÎH’Î5ÛÎ(Ï$:Ï/_Ï6Ï‚ÆÏCIÐCÐ-ÑÐ-ÿÐ5-Ñ.cÑ%’ѸÑÌÑßÑ0öÑ#'Ò&KÒ rÒ"“Ò#¶Ò$ÚÒ'ÿÒ.'Ó'VÓ(~Ó(§Ó!ÐÓ*òÓ8Ô1VÔ1ˆÔ3ºÔ1îÔ Õ/@ÕpÕF‡Õ/ÎÕ(þÕ)'Ö8QÖ/ŠÖ6ºÖ+ñÖ0× N×Ao×E±×#÷× Ø3<Ø1pØ(¢Ø4ËØÙ/Ù.JÙQyÙËÙêÙ4Ú47Ú3lÚ, Ú)ÍÚ7÷Ú6/Û!fÛ&ˆÛ2¯Û+âÛ.Ü4=ÜrÜÜ/¦Ü?ÖÜ+ÝBBÝ…ÝF¥Ý&ìÝ0Þ#DÞ!hÞŠÞ¦ÞÃÞÛÞ9÷Þ%1ß"Wßzß”ß'©ß$Ñß>öß)5à!_àà“à"¦à4Éàþàá1áQá)iá&“á"ºáHÝá3&â&ZâLâ8Îâ ã(ã;ãPã&kã"’ã)µã*ßã ! ä6$ä<[ä˜ä²äÉä1ßäå..å]å/så0£åÔå òå"ÿå*"æ,MæzæŒæ¥æ*¸æ4ãæç&6ç%]çƒç¢ç½ç$Öçûçè/è IèUè5uè«è)ÁèCëè!/é6Qé<ˆé.Åé'ôé3ê Pê)\ê5†ê¼êÑê#æê. ! ë.9ë$hë6ëÄë%âë=ì&Fìmì‹ì¨ì+Çìóìí!0í!Rítí+ˆíB´í=÷í25î=hî2¦îBÙî7ïTï-nïœï"¸ï9Ûï4ð.Jð)yð£ð"¾ðáðöðdñ>wñ¶ñËñPâñ93ò#mò‘ò&ªòvÑò)Hó@ró+³ó.ßó;ô2Jô>}ô;¼ôIøôBõ&Yõ1€õ0²õ'ãõ? öKö-gö"•ö¸ö)Îöøö-÷GC÷/‹÷.»÷)ê÷)ø4>ø&sø+šø0ÆøD÷ø<ù(Kù)tù1žù4Ðùúú0ú+Eú+qúú ·ú)Øú/û2û-Qû=û/½û;íû)ü/Dü tü)•ü+¿ü*ëü5ý0Lý0}ý1®ý$àý!þ,'þ<TþU‘þ!çþ ÿ0(ÿ#Yÿ}ÿT›ÿZðÿ[Kd§E cRB¶!ù#9]=}C»Dÿ%DWjÂ,â#%32YAŒ$Î#ó-+E@q²5Ð62=Hp ¹Úò "7:Br,µ'â6 ! +A,m/š0Ê5û1 F _ !q =“ !Ñ 5ó $) ! .N ! } ! #“ ! · ! 'Ö ! $þ ! Q#  u A– "Ø (û $ A6  x  „ AŽ Ð 'ð & %? &e 4Œ .Á ð >5Mƒ¢0À+ñ ! "*-*X$ƒ*¨8Ó" /H+h5”6Ê224<g2¤5×) 7Q%l"’ µ Ö-÷"%!H%j%'¶Þî ->\y‘®Â Ö âÒì¿:Á>ü;0Sׄ/\<ŒYÉ # 0<NOYžfø<_Wœ=ôH2I{7ÅWýUm*‹-¶(ä# *13\,Ž½LR&p—X³3 c@A¤KæJ2 6} @´ ]õ >S!„’!]"Ou"EÅ"[ #Pg#C¸#Dü#NA$L$PÝ$?.%=n%C¬%Oð%[@&?œ&BÜ&Š'Cª'Jî'R9(?Œ(FÌ(N)Hb)Y«)‰*J*?Ú*Š+=¥+Dã+b(,X‹,Oä,L4-K-KÍ-[.Uu.ªË.Rv/ŸÉ/ci0[Í0N)1^x1M×1=%2>c2>¢2;á2c3W3OÙ3])4N‡4KÖ4S"5Mv5HÄ5T 7b7V7 ! Ø7)ã7? 83M838Aµ8÷8'9.69Me90³9rä92W:MŠ:ŽØ:Dg;4¬;Bá;S$<%x<ž<¶<%Ì<3ò<3&=6Z=6‘=$È=$í="> 5>C>'Y>>B›>(Þ>I?UQ?"§?CÊ?U@d@1‚@Q´@AAE0A„vAXûA+TBe€B3æBRC?mCZ­C„DD:ªDPåD6EETE>šEgÙEAFUFGiFk±FkG‰Gr H]|H_ÚHX:I`“IWôIELJX’J]ëJjIK$´KHÙK"L-2L-`L7ŽL<ÆL0MF4M+{M6§M0ÞM4N0DN.uN?¤NTäN99O:sOQ®O(P)PI=P<‡POÄPVQakQSÍQ!RO@R5R*ÆR1ñRF#S6jS'¡S/ÉSOùSEIT:TDÊTKUK[UJ§UGòUE:VV€VH×VI WjW6ŠW9ÁWLûW!HX"jXX2«XDÞX#Y'¤k9ãk3lDQl3–l+Êl öl m8mHRmD›m?àmJ nIknEµnPûn2Lo2oQ²oCpEHpkŽpNúp>Iq9ˆqFÂqk rpurjærnQs;Às7üsi4t„žtC#uBgu,ªu×uDõu::vJuv7Àv9øv$2w(Ww%€w]¦w>xaCx(¥x#Îx.òx!!y6Cyzy)—y5ÁyC÷y<;z'xz0 z!Ñz-óz-!{:O{iŠ{*ô{D|6d|B›|JÞ|G)}=q}C¯}Dó}78~<p~­~)Ë~:õ~-0(^e‡aíFO€:–€*Ñ€1ü€Z.A‰+ˆ÷*~‚"©‚-Ì‚Dú‚G?ƒ8‡ƒ(ÀƒEéƒ9/„*i„B”„9ׄ&…E8…H~…DÇ…= †$J†8o†0¨†4Ù†D‡HS‡:œ‡8ׇPˆ0aˆ4’ˆCLj= ‰=I‰=‡‰Bʼn3Š!<Š4^Š“Š$±ŠLÖŠ$#‹+H‹~t‹ó‹ŒŒ36ŒBjŒ$­Œ ÒŒ@óŒ4,IvF>Ö?Ž%UŽ8{Ž"´Ž׎òŽ')8-bOàký6iC äTü!Q‘3s‘D§‘Dì‘]1’L’%Ü’$“#'“0K“ |“(“Æ“6á“(”oA”/±”)á”0 •#<•)`•$Š•1¯•/á•)–.;–(j–-“–%Á–(ç–-—'>—,f—3“—Ç—,Ü—' ˜1˜+J˜=v˜´˜ј#ì˜"™3™"P™%s™$™™=¾™ü™1š+Nš#zšžšºš(Öš)ÿš:)›d› |››h¯›œ7/œ6gœ*žœÉœÜœùœ6NJ/™=É$ž8,ž,ež3’žUÆž5Ÿ3RŸ†Ÿ#žŸ#Ÿ'æŸ) 8 K &a +ˆ ´ BÌ &¡6¡T¡#p¡&”¡'»¡0ã¡;¢P¢ f¢"‡¢ª¢1;£4m£1¢£GÔ£U¤6r¤'©¤AѤ/¥RC¥;–¥8Ò¥6 ¦7B¦Dz¦>¿¦Bþ¦(A§$j§§#¦§ʧ>ê§7)¨a¨8}¨$¶¨5Û¨6©$H©1m©/Ÿ©(Ï©%ø©8ª/Wª8‡ª@Àª/«;1«8m«6¦«<Ý«6¬<Q¬&Ž¬Cµ¬9ù¬73­5k­.¡­Эî­<®4C®0x®©®bÀ®#¯2A¯(t¯-¯8˯°°F(°+o°=›°"Ù°ü°±<&±_c±WñQ²Tm²R²g³}³Zÿ³RZ´U­´7µ6;µ*rµ3µ)ѵûµ¶M+¶-y¶*§¶/Ò¶=·"@·-c·‘·'°·2Ø·4 ¸6@¸-w¸B¥¸5è¸A¹C`¹C¤¹#è¹9 º'Fºnº‰º"¨º˺+庻',»/T»„» »!À»"⻼¼%9¼!_¼6¼¸¼Ô¼ï¼2½3A½0u½*¦½ѽ/í½8¾<V¾1“¾2ž6ø¾7/¿5g¿1¿1Ï¿À'À)FÀ*pÀY›ÀfõÀe\Á4ÂÁ÷Á, Â*9Â/dÂ5”Â&ÊÂñÂ/ Ã"=Ã$`Ã3…Ã)¹Ã4ãÃÄ43ÄhÄ7Ä<¹Ä,öÄ)#Å.MÅ2|Å0¯Å)àÅ) ! Æ 4ÆrBÆ?µÆõÆuÇB|Ç¿ÇÂÇÆÇ6ØÇ6ÈWFÈWžÈ3öÈ*É 1É>ÉGÉXÉaÉGrɺÉÔÉ&ñÉUÊ;nÊFªÊ ñÊ4ËGË*WË#‚Ë'¦Ë"ÎËñË Ì2ÌRÌrÌ Ì°Ì!ÏÌñÌ Í)ÍCÍ%_Í+…ͱÍÊÍ#âÍ%Î.,Î8[ÎS”Î1èÎ8ÏASÏ.•Ï&ÄÏëÏ Ð&&ÐMÐkЇÐ6¤ÐIÛÐ#%ÑIIÑG“ÑJÛÑ=&Ò8dÒ=Ò'ÛÒ7Ó-;Ó@iÓ ªÓN¶Ó(Ô%.ÔTÔ&lÔ%“Ô4¹ÔîÔÕ Õ&Õ6ÕSÕfÕ}Õ˜Õ>«Õ,êÕLÖTdÖ¹Ö3ÒÖ× ×7× ! L×=Wו×%°×/Ö×/Ø"6ØYØ!yØ+›Ø`ÇØ*(ÙOSÙ=£Ù(áÙK ! ÚVÚpÚ)‰Ú0³Ú)äÚ/Û0>Û"oÛF’Û)ÙÛ Ü+Ü<Ü\Ü"yÜ"œÜ¿Ü#ÎÜ@òÜ03ÝdÝ'‚Ý3ªÝ'ÞÝ'Þ].ÞŒÞ ŽÞ šÞ ¦Þ+²Þ8ÞÞ$ßR<ß%ß µß Áß Íß Ùß åß2ñß#$àHà Xàdà tà €à ŒàT˜àTíàWBá šáZ¦á#â %âW1âW‰âáâ.åâ<ã3Qã…ã ! £ã•®ã7Däs|ä$ðä&åA<å/~å®å ÌåIíå 7æ|DæÁæGÇæ4ç7Dç:|ç7·ç9ïç)èŽ@èoÏè>?éa~é†àéLgê´ê=Ñê@ë%Pë,vë,£ë*Ðë$ûë. ì,Oì,|ì*©ì%Ôì-úìR(í*{í%¦í,Ìíùíî4î*Qî1|î#®î+Òî+þî*ï4Hï2}ï#°ïÔïQçï9ðXð@vð[·ð6ñPJñI›ñLåñV2ò`‰ò/êò ó›'ó5Ãó2ùó6,ôXcôg¼ô[$õ$€õ$¥õ(Êõ%óõmöM‡öPÕöV&÷E}÷MÃ÷3ø9EøDø7ÄøZüøYWùT±ù<úTCú@˜úFÙúH ûpiûaÚûM<ü+Šü,¶ü1ãüSý>iý_¨ý@þ5Iþ‡þ[ÿ3cÿ7—ÿ&Ïÿöÿ+ 65 Yl 5Æ Wü ?T O” @ä % 1@ 7r iª I 1^ Q \â –? 7Ö , e; 3¡ yÕ *O 8z ³ :Ê . '4 ,\ V‰ là CM N‘ Mà .. ?] V Pô OE ! U• ! Xë ! \D 2¡ (Ô 2ý %0 <V ]“ Bñ 44 *i ,” &Á ,è & h< 2¥ 6Ø = *M /x :¨ Eã 7) %a +‡ /³ /ã , +@ $l $‘ N¶ ' 1- _ :v Q± Y /] / 1½ -ï ) BG EŠ ;Ð   <# 9` Gš ;â  38 'l H” $Ý ) 1, ^ $y _ž =þ $< Ya 8» 4ô 7) &a -ˆ +¶ 1â 0 'E "m * +» 2ç , G (_ %ˆ ;® ,ê / 1G #y F 7ä , /I @y º 4Ø >  1L +~ ª &È "ï ( (; Cd ,¨ ,Õ ( 3+ _ -r /  GÐ K! Fd! «! Mº! " 0" H" f" ! t" &" ¦" °" ?Â" B# E# ]# j# €# –# ž# §# ¯# Ç# Û# ç# "ø# "$ >$ Q$ a$ n$ ~$ ‘$ ª$ Á$ Ï$ ä$ ý$ % % ,.% :[% H–% -ß% … & r“& 7' ]>' +œ' +È' 9ô' .( GE( =( Ë( 0Û( 5 ) $B) 4g) 3œ) QÐ) A"* Od* W´* { + Hˆ+ 2Ñ+ 9, ;>, Lz, NÇ, >- 0U- ¾†- cE/ e©/ c0 =s0 V±0 '1 01 F1 \1 r1 (1 *¹1 .ä1 02 ,D2 &q2 +˜2 `Ä2 A%3 g3 Pé3 N:4 O‰4 5Ù4 ?5 @O5 5 {!6 n6 / 7 -<7 Vj7 „Á7 @F8 A‡8 ;É8 H9 1N9 N€9 3Ï9 W: P[: {¬: >(; Sg; <»; Dø; ]=< ]›< ]ù< MW= 4¥= 3Ú= +> R:> c> ñ> N? :a? %œ? Â? 6à? ]@ *u@ - @ :Î@ } A G‡A AÏA &B C8B 5|B %²B cØB I=F B|F B¿F ?G ABG 5„G DºG 4ÿG ;4H =pH <®H LëH 28I kI I )–I ÀI +áI N J Y\J >¶J 4õJ D*K +oK 1›K FÍK BL [WL Y³L [ M YiM OÃM 6N mJN [¸N ?O 2TO K‡O 1ÓO 0P R6P 6‰P @ÀP FQ `HQ 2©Q DÜQ 9!R b[R <¾R GûR 3CS 5wS 4­S HâS A+T bmT VÐT ('U 1PU .‚U \±U ;V >JV ‰V C W vMW IÄW /X 0>X boX ÒX %óX <Y @VY B—Y sÚY NZ QdZ ¶Z \ÍZ **[ SU[ Y©[ 9\ *=\ .h\ 4—\ dÌ\ C1] Du] Nº] P ^ AZ^ +œ^ 4È^ ý^ +_ #I_ m_ ‹_ C¦_ #ê_ 5` D` ;e` N¡` Fð` <7a Dta ¹a Ùa %îa b ?/b #ob K“b Ißb L)c Dvc »c FÒc &d 0@d qd d @“d JÔd Me (me \–e @óe >4f Msf NÁf Cg OTg *¤g iÏg O9h ‹‰h ‘i T§i Qüi NNj uj :k ANk #k ´k Îk èk =þk ?àn Ko 2ko ;žo <Úo p /2p Dbp 4§p CÜp N q #oq +“q 2¿q Kòq D>r )ƒr V­r Ks Ps #ns L’s 2ßs It H\t ¥t »t 'Ðt 5øt '.u Vu @ju «u 2¹u ?ìu M,v 7zv 1²v Täv T9w JŽw HÙw G"x Hjx J³x +þx .*y 9Yy M“y +áy < z JJz b•z Xøz @Q{ ’{ ~³{ ?2| 7r| +ª| zÖ| Q} r} “} ¬} Â} Ù} ð} !~ "3~ "V~ $y~ $ž~ 6Ã~ Eú~ '@ 'h s …€ 4Š€ °¿€ Pp 5Á 2÷ S*‚ z~‚ vù‚ 7pƒ M¨ƒ Wöƒ N„ /c„ !“„ @µ„ 5ö„ !,… @N… M… 5Ý… !† 55† !k† 7† #ņ 7é† #!‡ WE‡ l‡ ' ! ˆ ;2ˆ 'nˆ %–ˆ B¼ˆ 4ÿˆ 54‰ 5j‰ [ ‰ *ü‰ C'Š ?kŠ 1«Š kÝŠ !I‹ ,k‹ 4˜‹ `Í‹ .Œ 9KŒ S…Œ 6ÙŒ d 0u ,¦ \Ó ?0Ž @pŽ a±Ž ( I< <† à ä !ò A ;V ;’ Î 2à 7‘ CK‘ 2‘ *‘ í‘ 3 ’ ?@’ f€’ +ç’ >“ 6R“ p‰“ Œú“ ™‡” •!• N·• a– 0h– ™– ²– Ó– ô– — "2— "U— x— ™— 'º— *â— - ˜ ,;˜ /h˜ )˜˜ ,˜ (ï˜ [™ Zt™ iÏ™ H9š g‚š Bêš L-› Hz› LÛ 4œ ;Eœ Zœ JÜœ ' XC 'œ 'Ä ^ì Kž #jž 2Žž ½Áž 0Ÿ @°Ÿ =ñŸ F/  3v  Eª  ð  - ¡ K7¡ :ƒ¡ &¾¡ 0å¡ ¢ A/¢ $q¢ –¢ 5²¢ Lè¢ 95£ )o£ '™£ EÁ£ 6¤ />¤ 1n¤ 8 ¤ GÙ¤ 0!¥ BR¥ Q•¥ xç¥ D`¦ F¥¦ 8ì¦ c%§ ‰§ 3›§ ϧ !æ§ ¨ ,¨ <L¨ &‰¨ "°¨ *Ó¨ .þ¨ 1-© =_© ;© ;Ù© 9ª ;Oª 2‹ª 0¾ª Iïª U9« Ž« 3¬ RR¬ )¥¬ Ϭ 1ë¬ ;­ ,Y­ -†­ ´­ EÁ­ ,® 4® -P® ,~® "«® 7ή /¯ 6¯ (O¯ 2x¯ *«¯ #Ö¯ ú¯ ° $;° 4`° /•° %Å° $ë° 0± 3A± 'u± ?± *ݱ 0² 59² o² I‰² 8Ó² % ³ Q2³ K„³ Bг @´ *T´ E´ EÅ´ E µ RQµ E¤µ Nêµ D9¶ H~¶ AǶ B · HL· G•· PÝ· I.¸ Dx¸ %½¸ /㸠<¹ 9P¹ *Š¹ 0µ¹ *æ¹ -º ?º BOº ’º 4¨º $ݺ a» Ed» 6ª» Ká» :-¼ :h¼ =£¼ (á¼ C ! ½ /N½ /~½ :®½ <é½ <&¾ 0c¾ =”¾ 2Ò¾ J¿ {P¿ ^Ì¿ D+À 0pÀ 4¡À !ÖÀ PøÀ 6IÁ F€Á IÇÁ  "$ 3G 5{ +±Â BÝ  à 2à PDà -•Ã -Ãà "ñà Ä (2Ä 9[Ä B•Ä NØÄ 'Å /7Å %gÅ ,Å EºÅ $Æ (%Æ .NÆ R}Æ 3ÐÆ ,Ç &1Ç FXÇ ŸÇ ,ÀÇ *íÇ JÈ %cÈ M‰È .×È .É !5É :WÉ m’É AÊ .BÊ (qÊ $šÊ $¿Ê (äÊ  Ë "-Ë PË 6nË )¥Ë (ÏË ,øË G%Ì mÌ HŒÌ (ÕÌ /þÌ C.Í -rÍ  Í ·Í L9Î -†Î p´Î .%Ï ŽTÏ SãÏ )7Ð EaÐ %§Ð ÍÐ $ëÐ 2Ñ /CÑ 3sÑ 3§Ñ 0ÛÑ U Ò NbÒ K±Ò -ýÒ 7+Ó qcÓ 2ÕÓ Ô Y)Ô QƒÔ ÕÔ AôÔ a6Õ .˜Õ ÇÕ äÕ @Ö KAÖ Ö I“Ö ÝÖ ,úÖ )'× ,Q× ,~× «× X²× w Ø ƒØ ™Ø S¯Ø +Ù 9/Ù 'iÙ @‘Ù \ÒÙ O/Ú )Ú 9©Ú 1ãÚ ,Û 4BÛ 3wÛ ;«Û )çÛ )Ü 8;Ü !tÜ 0–Ü (ÇÜ 'ðÜ %Ý *>Ý .iÝ /˜Ý =ÈÝ 6Þ @=Þ !~Þ S Þ AôÞ 36ß =jß ¨ß ¾ß $Üß 7à 9à Oà "kà ;Žà 1Êà üà 7á $Ká [pá 6Ìá $â D(â )mâ ,—â 2Äâ 7÷â =/ã $mã F’ã BÙã ?ä <\ä (™ä FÂä 3 å X=å +–å 0Âå "óå @æ 9Wæ W‘æ @éæ =*ç =hç M¦ç @ôç 65è ;lè -¨è BÖè Ué Hoé H¸é Hê iJê ´ê /Àê Yðê JJë H•ë 3Þë =ì TPì L¥ì Jòì >=í ;|í @¸í fùí g`î <Èî )ï Q/ï Cï BÅï Wð =`ð Qžð Kðð @<ñ ‚}ñ %ò d&ò i‹ò õò <ó DCó .ˆó ·ó 8Çó Oô TPô ¥ô Ãô Ýô ûô õ 5õ +Uõ (õ Bªõ Míõ F;ö ‚ö œö ´ö Èö áö öö + ÷ 8÷ M÷ c÷ 9y÷ +³÷ ß÷ &ø ='ø Heø F®ø >õø 24ù Sgù É»ù …ú  ú &»ú :âú 7û 1Uû D‡û 3Ìû ?ü A@ü 6‚ü /¹ü /éü *ý 9Dý ~ý ý ;¼ý Møý -Fþ $tþ #™þ ½þ Ûþ øþ ÿ 2ÿ #Oÿ sÿ ‘ÿ ¯ÿ Íÿ =ëÿ ) ! =G ! … ! £ ! Á ! ß ! $ý ! " ! ? ! ^ ! | ! š ! ¸ ! @Ö !  ! 18 ! *j ! "• ! "¸ ! LÛ ! 8( ! 'a ! *‰ ! K´ ! > ! .? ! *n ! D™ ! SÞ ! <2 ! 5o ! F¥ ! 4ì ! =! ! _ ! 2 ! ,² ! 8ß ! i ! $‚ ! N§ ! Oö ! RF ! E™ ! Hß ! C( ! Fl ! ³ ! kÎ ! : ! ! X ! +v ! 6¢ ! &Ù !  ! F ! d ! 5ƒ ! R¹ !  ! .+ ! BZ !  ! ½ ! KÝ ! t) ! :ž ! BÙ ! 3 ! YP ! -ª ! ùØ ! \Ò ! g/ ! y— ! 8 ! 'J ! Ir ! =¼ ! Dú ! ? ! [Y ! Yµ ! C ! DS ! 4˜ ! *Í ! Tø ! CM ! $‘ ! 5¶ ! <ì ! 6) ! 2` ! 2“ ! 'Æ ! %î ! " ! E7 ! } ! ž ! K½ ! /  ! F9 ! 5€ ! <¶ ! +ó ! G ! Pg ! @¸ ! 5ù ! V/ ! S† ! 2Ú ! 7  ! >E ! J„ ! ,Ï ! 8ü ! %5 ! B[ ! 9ž ! WØ ! 00 ! Fa ! F¨ ! 7ï ! '' ! ,O ! 8| ! 7µ ! ?í ! $- ! IR ! 6œ ! 3Ó ! 4 ! -< ! ;j ! =¦ ! Uä ! R: ! 7 ! @Å ! 7! ! 7>! ! Xv! ! )Ï! ! %ù! ! b" ! W‚" ! 0Ú" ! 3 # ! $?# ! Zd# ! 3¿# ! $ó# ! ]$ ! Uv$ ! DÌ$ ! >% ! …P% ! UÖ% ! «,& ! AØ& ! K' ! Gf' ! E®' ! 2ô' ! 3'( ! )[( ! .…( ! "´( ! .×( ! †) ! 0) ! ¾) ! Ý) ! $ý) ! "* ! cB* ! ¦* ! !¼* ! .Þ* ! + + ! ?9+ ! ;y+ ! )µ+ ! 0ß+ ! ?, ! 8P, ! /‰, ! 3¹, ! í, !  - ! $,- ! Q- ! +g- ! k“- ! ’ÿ- ! Z’. ! í. ! -m/ ! ›/ ! ¼/ ! GÌ/ ! =0 ! *R0 ! :}0 ! ¸0 ! @Ô0 ! E1 ! C[1 ! KŸ1 ! Ië1 ! D52 ! Gz2 ! BÂ2 ! G3 ! BM3 ! G3 ! EØ3 ! ]4 ! J|4 ! :Ç4 ! }5 ! L€5 ! ØÍ5 ! ¦6 ! ¼6 ! Ø6 ! í6 ! 7 ! 7 ! !17 ! -S7 ! 47 ! *¶7 ! Wá7 ! 398 ! m8 ! .ˆ8 ! @·8 ! 1ø8 ! @*9 ! ?k9 ! 8«9 ! Aä9 ! M&: ! Ot: ! 1Ä: ! 0ö: ! D'; ! jl; ! =×; ! C< ! |Y< ! oÖ< ! vF= ! ]½= ! H> ! 'd> ! .Œ> ! E»> ! [? ! ]? ! =s? ! 7±? ! vé? ! `@ ! 4~@ ! N³@ ! >A ! DAA ! -†A ! 0´A ! .åA ! .B ! -CB ! .qB ! . B ! -ÏB ! UýB ! HSC ! ~œC ! ;D ! CWD ! D›D ! JàD ! L+E ! ,xE ! '¥E ! @ÍE ! 1F ! 1@F ! ArF ! -´F ! /âF ! .G ! 9AG ! 7{G ! ³G ! +ÔG ! 8H ! $9H ! ^H ! (H ! 1¨H ! +ÚH ! ?I ! .FI ! KuI ! 1ÁI ! 0óI ! E$J ! FjJ ! *±J ! 7ÜJ ! 2K ! GK ! (eK ! IŽK ! /ØK ! 0L ! ~9L ! 8¸L ! 1ñL ! 4#M ! AXM ! 5šM ! ?ÐM ! 5N ! ;FN ! 6‚N ! 7¹N ! 9ñN ! 5+O ! 6aO ! D˜O ! 5ÝO ! BP ! ;VP ! 9’P ! 8ÌP ! BQ ! DHQ ! FQ ! LÔQ ! A!R ! [cR ! G¿R ! [S ! WcS ! *»S ! æS ! ;T ! 5=T ! 8sT ! ?¬T ! EìT ! E2U ! KxU ! 4ÄU ! -ùU ! 1'V ! LYV ! 3¦V ! ÚV ! LîV ! 9;W ! ;uW ! <±W ! DîW ! 3X ! NX ! ,kX ! @˜X ! ÙX ! 7íX ! %%Y ! KY ! kY ! &‰Y ! )°Y ! $ÚY ! /ÿY ! a/Z ! S‘Z ! <åZ ! ;"[ ! =^[ ! ;œ[ ! @Ø[ ! O\ ! 3i\ ! \ ! 4¯\ ! 8ä\ ! !] ! e?] ! b¥] ! b^ ! -k^ ! ™^ ! ,¯^ ! )Ü^ ! #_ ! 9*_ ! 3d_ ! /˜_ ! 0È_ ! .ù_ ! ?(` ! 5h` ! 'ž` ! 2Æ` ! Où` ! 'Ia ! 'qa ! 9™a ! ;Óa ! 2b ! FBb ! -‰b ! D·b ! Lüb ! bIc ! ¬c ! FÅc ! Y d ! -fd ! '”d ! )¼d ! 'æd ! ]e ! cle ! !Ðe ! Aòe ! P4f ! R…f ! .Øf ! gg ! 0og ! T g ! Cõg ! E9h ! Qh ! xÑh ! CJi ! _Ži ! Yîi ! zHj ! <Ãj ! @k ! YAk ! y›k ! [l ! Tql ! cÆl ! f*m ! ~‘m ! Yn ! Ljn ! `·n ! Ko ! ‚do ! Uço ! `=p ! bžp ! ƒq ! \…q ! eâq ! {Hr ! `Är ! B%s ! lhs ! Õs ! ˆct ! lìt ! >Yu ! ©˜u ! `Bv ! M£v ! Uñv ! vGw ! b¾w ! ˆ!x ! Šªx ! 85y ! 4ny ! £y ! (Äy ! Híy ! n6z ! =¥z ! Hãz ! v,{ ! O£{ ! wó{ ! =k| ! S©| ! Gý| ! EE} ! -‹} ! C¹} ! .ý} ! ,,~ ! gY~ ! +Á~ ! "í~ ! ? ! JP ! $› ! &À ! 8ç ! " € ! -C€ ! Yq€ ! HË€ ! ' ! L< ! ;‰ ! BÅ ! C‚ ! 2L‚ ! :‚ ! -º‚ ! è‚ ! 8þ‚ ! 7ƒ ! *Vƒ ! Fƒ ! Nȃ ! "„ ! 7:„ ! r„ ! „ ! @§„ ! -è„ ! H… ! L_… ! n¬… ! † ! 49† ! n† ! …† ! &–† ! &½† ! ä† ! Eõ† ! I;‡ ! S…‡ ! UÙ‡ ! M/ˆ ! P}ˆ ! ;Έ ! T ! ‰ ! O_‰ ! #¯‰ ! ÓŠ ! 1Ü‹ ! MŒ ! =\Œ ! +šŒ ! -ÆŒ ! )ôŒ ! > ! :] ! A˜ ! 8Ú ! DŽ ! AXŽ ! BšŽ ! ,ÝŽ ! H ! ! S ! :m ! B¨ ! 6ë ! B" ! De ! Bª ! )í ! +‘ ! QC‘ ! +•‘ ! AÁ‘ ! :’ ! F>’ ! D…’ ! <Ê’ ! H“ ! ?P“ ! M“ ! EÞ“ ! F$” ! 6k” ! V¢” ! ! ù” ! u• ! tz• ! ï• ! Q – ! Z[– ! .¶– ! Då– ! 4*— ! ._— ! Ž— ! ¯— ! +¼— ! -è— ! S˜ ! ]j˜ ! Ș ! ;æ˜ ! ,"™ ! 'O™ ! Qw™ ! É™ ! 1Ù™ ! F š ! Rš ! 'mš ! '•š ! +½š ! #éš ! [ › ! Ji› ! N´› ! Dœ ! 4Hœ ! I}œ ! 4Çœ ! Müœ ! HJ ! [“ ! 'ï ! Vž ! nž ! +Šž ! '¶ž ! `Þž ! M?Ÿ ! DŸ ! ‡ÒŸ ! eZ  ! 9À  ! :ú  ! p5¡ ! 3¦¡ ! <Ú¡ ! 9¢ ! /Q¢ ! 2¢ ! C´¢ ! Pø¢ ! II£ ! .“£ ! 5£ ! _ø£ ! X¤ ! W`¤ ! D¸¤ ! Cý¤ ! <A¥ ! F~¥ ! ¨Å¥ ! Kn¦ ! Gº¦ ! 2§ ! 25§ ! h§ ! „§ ! D § ! 5å§ ! *¨ ! !F¨ ! Dh¨ ! 5­¨ ! :㨠! 3© ! *R© ! A}© ! ¿© ! `Ü© ! o=ª ! W­ª ! -« ! b3« ! /–« ! EÆ« ! [ ¬ ! ah¬ ! hʬ ! 43­ ! Uh­ ! p¾­ ! /® ! 3K® ! ® ! Iž® ! ;è® ! J$¯ ! 0o¯ ! $ ¯ ! 'ů ! %í¯ ! N° ! -b° ! ° ! l®° ! ?± ! H[± ! A¤± ! Mæ± ! O4² ! l„² ! Qñ² ! IC³ ! ]³ ! Vë³ ! WB´ ! 3š´ ! 'δ ! 7ö´ ! A.µ ! 7pµ ! =¨µ ! Uæµ ! S<¶ ! ¶ ! +°¶ ! 6ܶ ! · ! ,4· ! 4a· ! /–· ! Æ· ! ã· ! O¸ ! IT¸ ! 9ž¸ ! 2ظ ! 0 ¹ ! 2<¹ ! 0o¹ !  ¹ ! Z·¹ ! /º ! Bº ! HSº ! Lœº ! =éº ! '» ! ,G» ! 7t» ! '¬» ! $Ô» ! /ù» ! ()¼ ! ?R¼ ! V’¼ ! Fé¼ ! 30½ ! d½ ! -ƒ½ ! d±½ ! 1¾ ! XH¾ ! ^¡¾ ! .¿ ! !/¿ ! GQ¿ ! G™¿ ! Tá¿ ! D6À ! 7{À ! O³À ! $Á ! (Á ! NEÁ ! !”Á ! ¶Á ! AÉÁ ! 3  ! ? ! 2] ! M ! -Þ ! / à ! 9<à ! ;và ! ²Ã ! >Àà ! ?ÿà ! <?Ä ! :|Ä ! &·Ä ! 6ÞÄ ! IÅ ! "_Å ! ?‚Å ! ˆÂÅ ! ˆKÆ ! xÔÆ ! )MÇ ! wÇ ! 1“Ç ! ’ÅÇ ! WXÈ ! &°È ! ,×È ! )É ! ,.É ! I[É ! K¥É ! IñÉ ! ;Ê ! ZÊ ! qÊ ! '’Ê ! ºÊ ! •ÛÊ ! ¦qË ! >Ì ! .WÌ ! Q†Ì ! #ØÌ ! küÌ ! ThÍ ! F½Í ! ²Î ! \·Î ! @Ï ! 8UÏ ! 8ŽÏ ! 8ÇÏ ! &Ð ! $'Ð ! MLÐ ! 8šÐ ! @ÓÐ ! MÑ ! (bÑ ! ‹Ñ ! /§Ñ ! /×Ñ ! <Ò ! eDÒ ! ËªÒ ! UvÓ ! HÌÓ ! FÔ ! \Ô ! BÜÔ ! BÕ ! BbÕ ! ¥Õ ! M%Ö ! šsÖ ! `× ! 2o× ! Q¢× ! (ô× ! 8Ø ! <VØ ! 8“Ø ! :ÌØ ! -Ù ! 05Ù ! ‘fÙ ! CøÙ ! '<Ú ! dÚ ! UÛ ! VÕÛ ! e,Ü ! n’Ü ! UÝ ! ^WÝ ! 5¶Ý ! tìÝ ! aÞ ! A€Þ ! ÂÞ ! PßÞ ! G0ß ! xß ! EŒß ! -Òß ! 6à ! ;7à ! Bsà ! a¶à ! ,á ! 7Eá ! +}á ! V©á ! Vâ ! 6Wâ ! XŽâ ! hçâ ! QPã ! r¢ã ! Dä ! (Zä ! .ƒä ! ²ä ! ;Óä ! <å ! 'Lå ! 0tå ! C¥å ! ;éå ! %æ ! %@æ ! Dfæ ! 6«æ ! Eâæ ! L(ç ! Luç ! bÂç ! P%è ! 'vè ! (žè ! dÇè ! #,é ! <Pé ! Lé ! }Úé ! .Xê ! )‡ê ! I±ê ! Iûê ! JEë ! !ë ! <²ë ! Ãïë ! Ƴì ! szí ! îí ! 2 ! î ! :=î ! *xî ! 9£î ! 2Ýî ! &ï ! I7ï ! =ï ! B¿ï ! :ð ! 9=ð ! Cwð ! ;»ð ! X÷ð ! OPñ ! ! ñ ! 7Âñ ! (úñ ! 7#ò ! 8[ò ! $”ò ! ¹ò ! :×ò ! 8ó ! 8Kó ! <„ó ! *Áó ! 3ìó ! 7 ô ! 9Xô ! =’ô ! Ðô ! Cïô ! I3õ ! P}õ ! PÎõ ! Xö ! `xö ! eÙö ! k?÷ ! j«÷ ! ~ø ! ~•ø ! ~ù ! ~“ù ! €ú ! ~“ú ! €û ! ~“û ! tü ! %‡ü ! E­ü ! :óü ! .ý ! 7Ný ! !†ý ! ?¨ý ! 9èý ! "þ ! 7Aþ ! Ayþ ! 7»þ ! *óþ ! 7ÿ ! 'Vÿ ! ~ÿ ! "Ÿÿ ! *Âÿ ! &íÿ ! A RV ?© :é :$ ;_ T› eð V 4w -¬ Ú 4ó Q( $z $Ÿ 5Ä *ú % = 7S ;‹ -Ç =õ 73 2k 4ž 6Ó / !  4: 6o -¦ -Ô * +- 1Y N‹ 7Ú 4 4G /| 7¬ 5ä 0 3K 1 3± Få 5, ! 3b ! (– ! 7¿ ! &÷ ! A I` Eª ð ' :1 ql \Þ ; B[ ž ;¬ Lè ]5 K“ Rß U2 Dˆ nÍ _< @œ YÝ @7 Óx LL 7™ 4Ñ . @5 2v 5© Fß 4& 2[ 2Ž |Á l> m« 7 _Q N± a lb ;Ï G  2S K† 6Ò Z  nd fÓ K: H† ?Ï d =t P² / 33 Ig \±  Š Ž Xª m Zq NÌ c Y JÙ J$! ko! NÛ! /*" 3Z" @Ž" vÏ" DF# \‹# rè# =[$ Q™$ ”ë$ R€% hÓ% g<& s¤& S' hl' mÕ' ›C( >ß( ?) a^) ÐÀ) Ò‘* d+ eƒ+ &é+ , +, CE, =‰, DÇ, Ç - …Ô- aZ. ‰¼. 6F/ Y}/ ©×/ ¨0 &*1 TQ1 ¦1 *»1 Bæ1 Z)2 +„2 W°2 O3 <X3 ?•3 #Õ3 1ù3 #+4 5O4 ?…4 8Å4 Eþ4 bD5 M§5 õ5 =6 @R6 :“6 .Î6 Ký6 >I7 Eˆ7 *Î7 'ù7 /!8 :Q8 $Œ8 V±8 '9 O09 O€9 5Ð9 N: U: Cr: =¶: Vô: 5K; G; "É; %ì; !< 44< Ti< 3¾< 9ò< ,= :M= .ˆ= 8·= 4ð= 7%> *]> 3ˆ> "¼> !ß> ? %? UA? 3—? 9Ë? '@ 5-@ #c@ ‡@ ?¡@ @á@ A"A >dA ?£A @ãA B$B ;gB 8£B 7ÜB 9C :NC B‰C :ÌC BD DJD 1D >ÁD E $!E 6FE G}E ÅE (äE - F .;F 6jF b¡F bG BgG 8ªG )ãG 1 H 0?H ?pH <°H bíH PI nI I –I ©I /¿I 7ïI 5'J ]J rJ ˆJ !¥J ÇJ "æJ 3 K =K "GK ,jK %—K +½K 6éK F L QgL ?¹L ùL -M RGM RšM PíM L>N E‹N <ÑN =O DLO -‘O 3¿O -óO ,!P ANP !P ?²P MòP 4@Q VuQ VÌQ V#R VzR ÑR ?àR - S :NS E‰S ÏS 0QT U‚T %ØT þT EU =`U žU "¿U QâU 4V !´V 3ÖV 0 ! W +;W :gW 5¢W @ØW HX IbX ¬X GÍX 8Y ,NY {Y 8Y +ÆY òY $Z -8Z 4fZ )›Z $ÅZ êZ 8þZ 07[ h[ ‡[ )›[ ;Å[ V\ +X\ =„\ :Â\ 'ý\ ?%] 9e] #Ÿ] YÃ] ^ 2=^ 3p^ %¤^ „Ê^ ,O_ %|_ .¢_ 'Ñ_ =ù_ &7` H^` *§` Ò` fí` Ta Sqa 2Åa )øa <"b /_b b ®b ;Ëb Rc QZc B¬c )ïc :d CTd [˜d #ôd e #8e \e ne J€e Ëe 'ëe f :/f %jf @f 9Ñf D g |Pg 4Íg )h @,h :mh F¨h !ïh 3i 'Ei Imi @·i `øi QYj [«j Ak KIk :•k ]Ðk q.l / l "Ðl Iól )=m =gm ¥m +¼m "èm * n &6n #]n /n .±n àn Eo eFo ,¬o AÙo 9p 9Up )p '¹p Gáp D)q Bnq @±q 1òq >$r Kcr )¯r >Ùr Os _hs _Ès Y(t R‚t ;Õt 1u 7Cu -{u N©u ;øu ^4v M“v -áv ;w 5Kw 3w Cµw Cùw 0=x Lnx ?»x 9ûx L5y Q‚y PÔy P%z Pvz ;Çz >{ 7B{ 4z{ g¯{ 4| JL| 9—| .Ñ| ;} &<} 4c} G˜} 4à} D~ _Z~ Dº~ >ÿ~ => "| 8Ÿ 6Ø V€ .f€ F•€ 9Ü€ F F] I¤ bî 6Q‚ Eˆ‚ E΂ Gƒ *\ƒ {‡ƒ M„ [Q„ @­„ 9î„ .(… ;W… H“… ,Ü… | † 0†† u·† 7-‡ =e‡ W£‡ [û‡ /Wˆ )‡ˆ 6±ˆ Kèˆ 44‰ (i‰ 3’‰ 3Ɖ >ú‰ +9Š NeŠ &´Š AÛŠ 6‹ =T‹ &’‹ &¹‹ :à‹ >Œ VZŒ g±Œ N 8h O¡ ;ñ n-Ž ‰œŽ A& Lh Hµ Aþ `@ /¡ QÑ R#‘ av‘ OØ‘ U(’ N~’ 0Í’ Kþ’ iJ“ @´“ :õ“ X0” 8‰” W” I• Qd• P¶• 9– 1A– Ds– @¸– Kù– RE— D˜— PÝ— =.˜ Pl˜ s½˜ *1™ (\™ E…™ 2Ë™ 4þ™ a3š [•š Zñš <L› O‰› *Ù› 5œ E:œ @€œ BÁœ 9 5> Xt dÍ <2ž Jož :ºž iõž A_Ÿ e¡Ÿ B  6J  S  lÕ  UB¡ 9˜¡ BÒ¡ ,¢ HB¢ P‹¢ CÜ¢ L £ ƒm£ Sñ£ ,E¤ 8r¤ «¤ L±¤ Oþ¤ YN¥ @¨¦ Dé¦ #.§ (R§ *{§ %¦§ F̧ l¨ H€¨ Fɨ F© KW© A£© !å© "ª p*ª 8›ª 5Ôª ( ! « 3« E« `« n« ! |« 6‡« K¾« 1 ! ¬ 4<¬ 3q¬ 0¥¬ …Ö¬ C\­ 6 ­ C×­ y® A•® D×® ¯ B,¯ 2o¯ E¢¯ è¯ 5ê¯ J ° wk° >ã° ("± DK± /± \À± P² Fn² Tµ² 0 ! ³ z;³ O¶³ -´ G4´ >|´ H»´ Lµ VQµ /¨µ 0ص  ¶ 5 ¶ 2V¶ v‰¶ Z· B[· Bž· Ná· (0¸ 5Y¸ &¸ J¶¸ M¹ AO¹ @‘¹ JÒ¹ 9º 3Wº P‹º [ܺ G8» H€» AÉ» i ¼ ?u¼ 7µ¼ <í¼ 4*½ 5_½ •½ >¬½ >ë½ h*¾ 1“¾ Tž 4¿ ;O¿ A‹¿ UÍ¿ =#À 7aÀ 2™À 4ÌÀ =Á >?Á ;~Á 9ºÁ 0ôÁ % *9 Bd §Â @Æ *à 12à dà 3{à R¯Ã 3Ä 26Ä ‹iÄ EõÄ D;Å =€Å ;¾Å DúÅ ;?Æ A{Æ i½Æ 'Ç 3Ç 9AÇ ){Ç 3¥Ç MÙÇ M'È uÈ _‘È 4ñÈ I&É 2pÉ /£É .ÓÉ :Ê D=Ê 5‚Ê -¸Ê $æÊ 5 Ë EAË ?‡Ë 6ÇË þË >Ì H]Ì R¦Ì BùÌ D<Í AÍ CÃÍ >Î @FÎ $‡Î 6¬Î 6ãÎ 6Ï 6QÏ 5ˆÏ -¾Ï /ìÏ Ð ?8Ð %xÐ @žÐ 7ßÐ Ñ 8¥Ñ XÞÑ @7Ò /xÒ 7¨Ò =àÒ 4Ó 2SÓ =†Ó -ÄÓ /òÓ 1"Ô ,TÔ Ô 3Ô -ÄÔ IòÔ <Õ JRÕ 2Õ IÐÕ NÖ =iÖ 6§Ö VÞÖ C5× Ay× C»× Cÿ× CØ %SØ $yØ $žØ .ÃØ HòØ H;Ù *„Ù C¯Ù %óÙ /Ú IÚ DRÚ C—Ú NÛÚ 6*Û .aÛ BÛ cÓÛ 07Ü #hÜ nŒÜ 7ûÜ 3Ý 3?Ý KsÝ .¿Ý 1îÝ ? Þ V`Þ V·Þ Bß BQß #”ß ¸ß 5×ß 1 à ,?à Blà /¯à 1ßà /á Aá H^á §á BÃá "â n)â `˜â aùâ ^[ã Pºã \ ä Thä 1½ä $ïä å )å R7å .Šå 5¹å ïå Hæ 2Qæ >„æ $Ãæ Gèæ 70ç fhç @Ïç 4è GEè Yè :çè *"é 7Mé H…é Îé #âé )ê 10ê /bê 8’ê Ëê ìê ë ë 3ë 4Rë '‡ë ¯ë *Æë 9ñë *+ì 6Vì 6ì 8Äì 6ýì 64í 6kí 6¢í 6Ùí -î 6>î uî î î .¯î +Þî ( ! ï $3ï $Xï }ï œï >®ï íï ð ð >/ð 5nð ,¤ð 9Ñð 5 ñ (Añ 1jñ 7œñ )Ôñ %þñ %$ò +Jò 1vò +¨ò 0Ôò ó #ó Bó ,^ó (‹ó T´ó N ô >Xô +—ô 4Ãô 2øô 4+õ 7`õ :˜õ 8Óõ  ö \)ö 8†ö 2¿ö òö &÷ </÷ &l÷ -“÷ ;Á÷ Fý÷ Dø LNø !›ø ½ø Üø !ùø -ù AIù @‹ù 8Ìù >ú SDú *˜ú ;Ãú %ÿú %û XDû :û 7Øû 4ü DEü /Šü 0ºü ëü Xùü <Rý 5ý IÅý >þ >Nþ ?þ HÍþ Hÿ e_ÿ -Åÿ )óÿ ? ] ~ )š CÄ & 1/ 1a c“ G÷ .? @n @¯ =ð -. \ L} Ê 'Þ F +M 3y ­ >Î >  VL B£ .æ = _S [³ / 8? *x 3£ ?× L ^d 'à 'ë E 6Y L ]Ý I; ! '… ! ­ ! Æ ! #Þ ! A 9D -~ 9¬ 6æ * DH  #© 'Í /õ % .C r +‹ &· %Þ ? D Q $^ ƒ ™ ­ MÆ 3 EH 6Ž :Å ; I< [† %â + $4 %Y 9 :¹ 'ô / 7L „ >¤ 8ã 1 ;N 5Š 1À 'ò - 6H % e¥ .  +: +f 9’ AÌ @ 8O Dˆ GÍ F &\ /ƒ G³ )û t% Jš @å D& %k ;‘ CÍ H jZ AÅ . C6 <z P· + 4 O k )† <° .í " 1? :q M¬ ;ú >6 @u 2¶ ;é J% Ip 2º >í ", @O  H¥ 4î †#! :ª! =å! %#" <I" Z†" Uá" ‡7# O¿# M$ F]$ 3¤$ DØ$ 6% 5T% 0Š% I»% && 5,& Kb& =®& :ì& 7'' )_' 3‰' 0½' (î' %( :=( Fx( ?¿( "ÿ( P") ?s) 9³) 8í) B&* Ci* I­* '÷* ,+ 0L+ =}+ T»+ -, P>, 4, CÄ, G- (P- *y- o¤- t. v‰. :/ ;;/ ;w/ D³/ `ø/ 1Y0 5‹0 7Á0 ù0 /1 A1 X1 /q1 4¡1 +Ö1 M2 ?P2 82 WÉ2 A!3 +c3 /3 ! ¿3 *Ê3 *õ3  4 :54 1p4 -¢4 JÐ4 65 R5 h5 }5 —5 ­5 8Ê5 )6 H-6 Gv6 T¾6 f7 %z7 8 7 5Ù7 98 KI8 O•8 å8 9 V!9 `x9 #Ù9 8ý9 &6: ]: B{: K¾: O ! ; 0Z; H‹; HÔ; B< 8`< 3™< ?Í< D = QR= G¤= 0ì= 1> O> :h> 5£> 9Ù> 2? F? +b? 2Ž? IÁ? 0 @ <@ `Q@ j²@ EA HcA A¬A TîA YCB YB =÷B 65C 3lC : C -ÛC D *D 0GD xD ;”D 2ÐD 3E 27E *jE #•E .¹E 4èE 2F 4PF #…F /©F wÙF @QG ?’G DÒG CH {[H ,×H YI K^I WªI 0J 43J .hJ :—J UÒJ _(K %ˆK ®K 6ÉK &L Z'L <‚L T¿L 2M 0GM -xM .¦M @ÕM 2N 6IN D€N 2ÅN OøN `HO ]©O VP %^P ]„P 4âP LQ QdQ E¶Q GüQ CDR QˆR 8ÚR RS *fS A‘S -ÓS VT XT @rT F³T [úT 5VU DŒU !ÑU &óU 3V ZNV k©V qW i‡W JñW sàX -Y 6MY A„Y &ÆY 9íY ,'Z "TZ EwZ 3½Z <ñZ 8.[ 2g[ /š[ =Ê[ ,\ <5\ 5r\ .¨\ .×\ %] ,] 2E] ;x] O´] )^ 0.^ "_^ 2‚^ *µ^ /à^ /_ .@_ o_ ?ˆ_ )È_ ò_ ` 2` BM` :` *Ë` 7ö` 0.a 9_a 5™a [Ïa K+b Hwb Àb ?Öb 6c FMc 8”c 7Íc d  d 2d >d .Ld #{d Ÿd H¿d We +`e Œe =¤e 0âe ?f .Sf /‚f 5²f .èf @g MXg N¦g Cõg $9h >^h 3h 5Ñh /i '7i y_i 3Ùi / j &=j 6dj L›j Ièj 92k 2lk ?Ÿk 0ßk /l B@l 9ƒl S½l Sm ;em 7¡m YÙm ?3n sn S„n RØn "+o >No o 4«o 0ào +p A=p .p 0®p .ßp q e%q '‹q $³q 6Øq Rr 8br D›r =àr As I`s nªs It qct rÕt uHu \¾u [v &wv Xžv <÷v 74w =lw Gªw 2òw ?%x ,ex 2’x EÅx J y 1Vy /ˆy 0¸y Héy A2z Ttz Éz "äz ^{ 5f{ $œ{ #Á{ Vå{ Q<| Ž| ¬| 8Ê| >} /B} Br} +µ} Xá} J:~ -…~ ,³~ 2à~  4 T s  ,® Û 8î +'€ BS€ +–€ € 6Õ€ 5 !B d )z +¤ +Ð 3ü 0‚ D‚ [‚ r‚ €‚ 3Ž‚ 3‚ Yö‚ $Pƒ "uƒ ˜ƒ .°ƒ ߃ ,øƒ B%„ +h„ +”„ À„ $á„ @… 4G… |… )“… ½… Ô… )ñ… † +:† ff† 5͆ ]‡ 5a‡ 3—‡ 6ˇ /ˆ a2ˆ (”ˆ ½ˆ 8Úˆ ‰ 7+‰ :c‰ ž‰ ¾‰ $Ù‰ $þ‰ #Š %?Š %eŠ F‹Š 8ÒŠ , ‹ 8‹ AL‹ _Ž‹ Hî‹ ,7Œ ,dŒ "‘Œ ´Œ ÓŒ 2ðŒ (# ?L dŒ jñ d\Ž JÁŽ  C Sb #¶ ;Ú A 4X K Ù 9ø @2‘ 6s‘ Cª‘ :î‘ :)’ Ed’ )ª’ 5Ô’ = ! “ +H“ <t“ <±“ î“ ô“ ? ” 3K” +” /«” Û” û” *• +G• !s• "•• %¸• Þ• ô• – 4– @L– 4– +– 'î– 1— ?H— 2ˆ— 1»— 0í— 1˜ P˜ #q˜ •˜ ³˜ AÔ˜ A™ +X™ )„™ ®™ !À™ â™ ô™ Wš ^š pš Šš ¦š Àš Úš ûš  › !› 3› O› :j› ¥› ¸› 5Ê› 6œ 57œ 5mœ £œ L½œ ! '+ S e <w ´ Æ Û ù ž %ž 7ž Iž $cž %ˆž ®ž ž Øž 2îž !Ÿ :Ÿ QŸ hŸ ‚Ÿ !–Ÿ ¸Ÿ ÑŸ èŸ     5  I  _  u  ‡  ¡  #³  ×  Oé  09¡ Sj¡ 6¾¡ õ¡ #¢ 8¢ U¢ g¢ †¢ ¥¢ DÄ¢  £ &£ ,C£ 6p£ §£ GÁ£ ) ¤ 3¤ M¤ h¤ }¤ ›¤ $¸¤ $ݤ $¥ '¥ !D¥ )f¥ @¥ *Ñ¥ %ü¥ '"¦ 3J¦ 1~¦ °¦ /Ѧ § § /3§ c§ #z§ ž§ R¾§ Q¨ *c¨ 6Ž¨ Ũ ⨠© # © %D© j© +‰© "µ© #Ø© ü© $ª ?ª ^_ª Y¾ª b« _{« "Û« !þ« I ¬ Gj¬ l²¬ =­ 5]­ :“­ Hέ E® 2]® J® :Û® J¯ 4a¯ <–¯ VÓ¯ ƒ*° i®° i± 3‚± +¶± 0â± P² 4d² J™² 8ä² Z³ Rx³ ]˳ >)´ \h´ 4Å´ *ú´ C%µ iµ G„µ ,̵ ! ùµ 0¶ ,5¶ b¶ .¶ $®¶ Ó¶ Bæ¶ 9)· Ec· $©· #η +ò· /¸ 9N¸ 8ˆ¸ +Á¸ Dí¸ z2¹ M­¹ û¹ =º Vº >qº 1°º 3⺠3» 4J» » » A›» @Ý» *¼ *I¼ t¼ B‘¼ %Ô¼ ú¼ " ½ !.½ #P½ $t½ !™½ .»½ Aê½ E,¾ r¾ -‡¾ *µ¾ -ྠ#¿ ,2¿ D_¿ >¤¿ Bã¿ ,&À 3SÀ '‡À D¯À #ôÀ :Á 4SÁ $ˆÁ /­Á 0ÝÁ D AS J•Â 4à 5à Kà [Xà /´Ã Täà 9Ä &ZÄ Ä \‰Ä BæÄ 6)Å S`Å +´Å DàÅ K%Æ GqÆ c¹Æ <Ç >ZÇ 0™Ç 4ÊÇ ÿÇ È @3È LtÈ SÁÈ DÉ ZZÉ =µÉ <óÉ >0Ê GoÊ H·Ê *Ë *+Ë ;VË #’Ë '¶Ë 1ÞË 1Ì 1BÌ 2tÌ *§Ì —ÒÌ ¹jÍ P$Î DuÎ FºÎ 5Ï ;7Ï GsÏ O»Ï ! Ð !-Ð &OÐ +vÐ 0¢Ð :ÓÐ .Ñ L=Ñ lŠÑ S÷Ñ YKÒ d¥Ò m ! Ó xÓ YøÓ CRÔ a–Ô [øÔ 4TÕ +‰Õ +µÕ 0áÕ #Ö E6Ö D|Ö CÁÖ ,× -2× B`× 1£× DÕ× 7Ø ;RØ :ŽØ 4ÉØ JþØ .IÙ >xÙ 7·Ù [ïÙ JKÚ 9–Ú IÐÚ )Û 'DÛ =lÛ 8ªÛ MãÛ !1Ü SÜ 8sÜ ¬Ü GÍÜ <Ý @RÝ N“Ý âÝ (Þ +*Þ ,VÞ /ƒÞ 9³Þ íÞ ! ß 4 ß >Aß 0€ß 2±ß ;äß # à #Dà %hà EŽà ;Ôà <á Má 5gá 8á 9Öá Aâ FRâ 2™â ?Ìâ 3 ã 3@ã 3tã E¨ã 2îã !ä F9ä _€ä Ràä D3å 'xå A å 2âå 6æ 1Læ )~æ ¨æ JÅæ Gç PXç F©ç Qðç ZBè ;è )Ùè *é +.é ZZé \µé 9ê LLê ™ê !©ê !Ëê !íê !ë 1ë MPë ]žë Uüë GRì *šì ^Åì f$í d‹í oðí N`î n¯î \ï {ï !ï 4¯ï ;äï  ð A0ð Grð ºð Ûð ôð  ñ .ñ OKñ V›ñ Wòñ Jò Jjò ?µò Gõò ?=ó 7}ó -µó *ãó (ô -7ô "eô *ˆô 1³ô ,åô õ =.õ Ilõ ?¶õ /öõ *&ö .Qö H€ö VÉö 5 ÷ 6V÷ 7÷ PÅ÷ aø (xø /¡ø Ñø 5âø ;ù +Tù "€ù >£ù âù 4ú 05ú +fú A’ú .Ôú 0û .4û Ocû B³û @öû 7ü KRü ,žü 4Ëü 7ý ?8ý `xý hÙý fBþ q©þ Rÿ pnÿ nßÿ vN tÅ : ^º ~ -˜ OÆ 2 5I C Zà Z Fy FÀ 0 G8 ^€ Sß 03 d 8„ 6½ 8ô A- -o ' 7Å 6ý 64 ;k T§ Gü ?D 1„ F¶ Cý KA ! Q ! -ß ! M J[ 7¦ (Þ E DM a’ Iô > ,^ =‹ 7É E 3G ;{ D· Lü 6I F€ /Ç '÷  = BM K +Ü 0 69 0p >¡ ;à  @= 9~ <¸ @õ =6 Ft &» :â . bL @¯ Eð 6 3S 9‡ 0Á ò  &/ $V 4{ P° \ ?^ ;ž Ú ë Q 5U @‹ @Ì /  /= m ƒ œ ² Ê â ú  ' < Q f z  § Ä Ü ó   4 L a y Ž ¦ » Ð è ý  ' < T l „ ™ ® Æ Û ó    7 O d y Ž £ ¸ Ð å ý  * D \ q † › 7³ ë 0þ / O e # +£ /Ï ÿ  1 #Q ?u Gµ &ý #$! H! 7^! 7–! 6Î! ," 32" #f" :Š" :Å" 7# :8# 4s# ,¨# QÕ# 6'$ 0^$ %$ %µ$ -Û$ ) % 3% (T% /}% J­% .ø% 4'& =\& :š& 6Õ& 6 ' 4C' 2x' E«' ñ' .( ;@( |( ( ;²( 7î( 6&) >]) *œ) >Ç) * %'* #M* +q* 0* $Î* 9ó* '-+ ,U+ 4‚+ !·+ 5Ù+ %, >5, t, NŠ, .Ù, 0- 29- &l- <“- #Ð- )ô- 8. 9W. H‘. /Ú. * ! / #5/ (Y/ e‚/ #è/ , 0 i90 X£0 ü0 41 5J1 €1 <‘1 -Î1 +ü1 .(2 $W2 3|2 &°2 ×2 Fë2 .23 3a3 3•3 BÉ3 3 4 4@4 0u4 I¦4 0ð4 7!5 0Y5 Š5 !ž5 #À5 ä5 +6 +06 +\6 +ˆ6 +´6 +à6 + 7 +87 +d7 +7 -¼7 +ê7 (8 .?8 -n8 +œ8 +È8 +ô8 + 9 L9 %k9 >‘9 >Ð9 >: *N: 'y: '¡: 'É: ñ: '; 6; +S; '; '§; 'Ï; '÷; '< 'G< :o< Jª< gõ< /]= E= .Ó= /> 02> =c> 0¡> =Ò> ? $+? /P? €? B ? !ã? 0@ 6@ 'U@ =}@ $»@ -à@ -A 8¼M cûM l_N 1ÌN 'þN .&O .UO /„O @´O 'õO $P -BP 3pP -¤P 8ÒP / Q /;Q -kQ B™Q 8ÜQ 3R RIR FœR ãR cûR 4_S $”S ;¹S ;õS 91T .kT "šT ½T ,ÙT $U '+U ESU 6™U 3ÐU 9V >V @OV 6V 3ÇV .ûV 6*W 3aW •W "ªW NÍW -X IJX %”X FºX &Y 0(Y YY rY ŠY "¨Y 0ËY /üY .,Z ([Z %„Z &ªZ &ÑZ &øZ )[ *I[ (t[ ([ (Æ[ &ï[ #\ !:\ 1\\ -Ž\ $¼\ #á\ #] &)] #P] *t] +Ÿ] /Ë] ,û] #(^ )L^ &v^ $^ #Â^ %æ^ : _ €G_ gÈ_ C0` t` 2~` )±` .Û`  ! a ;*a /fa –a M°a ,þa (+b Tb -rb P b 7ñb *)c #Tc ,xc c¥c 7 d \Ad žd '³d 4Ûd ,e ;=e 6ye D°e Võe Lf )df (Žf *·f +âf 2g Ag HRg #›g V¿g qh Vˆh  ßh €i !ži ;Ài <üi 89j Hrj @»j Iüj ?Fk L†k :Ók %l :4l :ol 7ªl 6âl ;m KUm ,¡m [Îm $*n "On .rn ¡n 5¼n 5òn @(o 4io -žo 8Ìo (p !.p 'Pp "xp +›p &Çp îp  q !q Aq /`q #q &´q Ûq +øq $r )@r jr )†r +°r *Ür :s ;Bs 2~s .±s %às 3t ::t +ut D¡t )æt u #/u =Su 8‘u 3Êu þu v 2/v .bv '‘v !¹v 2Ûv Bw SQw ;¥w #áw Lx BRx *•x )Àx +êx -y HDy Ey FÓy :z [Uz O±z E{ 9G{ \{ CÞ{ H"| 0k| >œ| BÛ| 9} GX} R } +ó} N~ An~ P°~ 6 <8 =u 2³ 7æ A€ A`€ =¢€ 4à€ B )X +‚ L® Lû H‚ 3d‚ /˜‚ +È‚ ?ô‚ +4ƒ G`ƒ 9¨ƒ 1⃠1„ 6F„ 6}„ ´„ Ë„ ä„ (ÿ„ )(… 2R… 1…… .·… æ… .† 0† O† 0d† •† «† *dž :ò† !-‡ *O‡ .z‡ ©‡ Á‡ Ò‡ ï‡ >ˆ @ˆ ._ˆ Žˆ 3¯ˆ F㈠<*‰ ,g‰ ”‰ ª‰ :ʉ 2Š F8Š 9Š b¹Š (‹ ,E‹ (r‹ -›‹ hÉ‹ 22Œ eŒ 0ƒŒ 9´Œ =îŒ ., 6[ ’ -® >Ü 5Ž $QŽ +vŽ 7¢Ž =ÚŽ J $c 6ˆ x¿ 88 ,q Tž +ó %‘ IE‘ (‘ J¸‘ M’ 5Q’ @‡’ LÈ’ I“ =_“ [“ Qù“ JK” 9–” NД • ;?• >{• º• 9Ô• 4– !C– )e– '– |·– -4— #b— 8†— .¿— .î— B˜ 1`˜ $’˜ &·˜ %Þ˜ -™ /2™ ;b™ /ž™ [Ι #*š :Nš ‰š "§š @Êš  › 5› ,P› 2}› 2°› ,ã› ;œ %Lœ Brœ (µœ Þœ =õœ 3 'R z B• NØ I'ž 3qž >¥ž <äž L!Ÿ UnŸ >ÄŸ 2  -6  4d  /™  /É  .ù  .(¡ #W¡ #{¡ 9Ÿ¡ >Ù¡ ¢ J9¢ $„¢ /©¢ +Ù¢ /£ 55£ 6k£ #¢£ BÆ£ 0 ¤ %:¤ )`¤ @Š¤ $ˤ =ð¤ G.¥ Av¥ .¸¥ 1ç¥ ]¦ ;w¦ R³¦ 7§ O>§ !Ž§ D°§ Fõ§ #<¨ 9`¨ ;š¨ 9Ö¨ '© /8© 2h© ?›© =Û© 5ª @Oª 9ª >ʪ 2 « 4<« 1q« £« 5º« \ð« CM¬ C‘¬ :Õ¬ l­ I}­ =Ç­ >® dD® .©® 9Ø® U¯ Uh¯ /¾¯ 5î¯ >$° <c° < ° FÝ° $± S7± i‹± `õ± KV² .¢² 'Ѳ ù² 5³ M³ &_³ †³ ,¦³ 0Ó³ &´ A+´ m´ r´ Dy´ ¾´ Ë´ >æ´ 6%µ D\µ >¡µ -ൠ>¶ PM¶ Mž¶ ì¶ · f(· C· @Ó· 0¸ 7E¸ 8}¸ )¶¸ Fภ2'¹ 2Z¹ A¹ AϹ )º Z;º L–º +㺠I» 9Y» "“» &¶» "Ý» "¼ &#¼ JJ¼ L•¼ 8â¼ 3½ CO½ )“½ ½½ Ô½ (ç½ *¾ $;¾ N`¾ R¯¾ O¿ NR¿ N¡¿ [ð¿ 6LÀ .ƒÀ ²À /ÒÀ HÁ @KÁ 3ŒÁ 5ÀÁ .öÁ 1% OW &§Â Πá ö 3 à 4=à 'rà šÃ ZºÃ "Ä _8Ä 3˜Ä IÌÄ =Å ,TÅ UÅ >×Å DÆ 8[Æ 8”Æ 8ÍÆ 5Ç -<Ç KjÇ ¶Ç ,ÊÇ )÷Ç )!È 0KÈ 8|È 1µÈ 9çÈ c!É (…É ®É 1ÎÉ 4Ê >5Ê =tÊ "²Ê +ÕÊ *Ë D,Ë 'qË -™Ë 4ÇË ,üË ))Ì 9SÌ "Ì +°Ì *ÜÌ 'Í H/Í LxÍ BÅÍ $Î ,-Î KZÎ -¦Î 'ÔÎ &üÎ #Ï "DÏ =gÏ A¥Ï @çÏ 9(Ð #bÐ D†Ð EËÐ dÑ dvÑ AÛÑ 5Ò (SÒ Y|Ò RÖÒ 0)Ó ?ZÓ 6šÓ JÑÓ $Ô 6AÔ [xÔ XÔÔ K-Õ ZyÕ SÔÕ Z(Ö XƒÖ SÜÖ X0× >‰× @È× \ Ø AfØ D¨Ø UíØ gCÙ S«Ù SÿÙ HSÚ HœÚ >åÚ ! $Û /Û ;Û HOÛ R˜Û RëÛ 7>Ü -vÜ /¤Ü LÔÜ F!Ý hÝ `zÝ ÛÝ 7òÝ 8*Þ EcÞ ©Þ (ÇÞ JðÞ N;ß 8Šß <Ãß Ià 8Jà 3ƒà 8·à /ðà A á Gbá Eªá 9ðá G*â drâ M×â -%ã VSã ªã FÁã 2ä 4;ä <pä !­ä 1Ïä 1å ! 3å >å [å 6{å R²å æ 6&æ ?]æ 7æ #Õæ ùæ  ç )ç 2Iç 2|ç ¯ç Ïç +ëç è !2è Tè *pè 6›è /Òè é  é >é (Xé +é A­é +ïé ê ?*ê 7jê 3¢ê 2Öê 5 ë O?ë Që *áë $ ì K1ì /}ì ­ì CÊì í C(í Glí ]´í \î Coî ³î Åî 0æî =ï (Uï D~ï BÃï Eð FLð L“ð Eàð b&ñ b‰ñ Gìñ V4ò 3‹ò >¿ò ;þò Q:ó >Œó >Ëó < ! ô +Gô 3sô ,§ô Ôô 9õô /õ Nõ 7mõ &¥õ 'Ìõ ôõ &ö 9ö VPö !§ö 3Éö *ýö *(÷ "S÷ Sv÷ "Ê÷ í÷ Z ø Udø ºø Ùø ÷ø  ù #ù 19ù !kù ,ù Bºù Qýù !Oú 2qú 2¤ú M×ú %%û Kû 8jû £û (Ãû .ìû @ü 0\ü Iü Q×ü Q)ý F{ý :Âý 4ýý !2þ ETþ :šþ 2Õþ ÿ ''ÿ Oÿ -oÿ ÿ Kºÿ MLTh¡+ ! J6;C½S4U-Š6¸0ï< ']2…(¸áùG0ZK‹4×1 ?>V~BÕB$[9€-º4è4IR+œLÈK:a=œEÚA &b %‰ %¯ aÕ 57 ! Zm ! È ! %Û ! 2 *4 9_ 4™ 3Î % %( AN * b» ) >H 8‡ =À @þ 3?6sLª,÷7$1\EŽlÔ@Ae‚ŠèIsb½N Jo/º4ê-BM*!»<ÝA,\A‰&Ë$ò*2B u–¬À5Ï./4>d;£ ß9é0#!T)v@ 'áB 3L'€/¨<Ø#>9+x*¤:ÏH ! -S:.¼6ë2"Up+‹'·*ß. ! 9V)uŸ"º Ý(þw'!Ÿ4Á4ö4+$`U…OÛG+JsD¾ 5 9U 5 :Å L!5M!Jƒ!7Î!D"BK"DŽ"BÓ"A#?X#4˜#5Í#M$"Q$3t$4¨$Ý$=ü$1:%2l%lŸ%h &cu&BÙ&7'GT'-œ'6Ê':(!<((^('‡('¯($×(+ü(:()Tc)K¸)*D$*5i*2Ÿ*Ò*gê*+R+!~+! +-Â+Ið+:,3X,3Œ,DÀ,<-NB-@‘-<Ò-0.3@.3t.R¨.Fû.0B/Js/F¾/J0IP03š0AÎ0A1IR1Mœ1Nê1A92H{2_Ä2Z$3431´33æ304K4 j4‹43¨4Ü4?ù4p956ª5Pá5.26a66š6"³6LÖ6J#7Nn7]½718>M8<Œ8/É88ù8J29K}9IÉ9T:>h:<§:Dä:;);;e;D¡;;æ;;"<9^<M˜<Mæ<N4=Mƒ=NÑ=M >Nn>N½>a ?_n?-Î?ü?"@5@@T@5•@7Ë@(A%,ARAEfA.¬ABÛA2BHQB6šB3ÑB&C),C(VC5C"µC+ØC3D38D1lD1žD)ÐD-úD(E2:E1mE,ŸE2ÌEGÿE<GFJ„F'ÏF&÷F2G9QGM‹GQÙG=+H/iH3™HÍH*ìHLI8dI4IOÒI"J%@JfJ4…JÀºJ{K™KO'LiwLOáLK1MN}M=ÌM5 ! NA@N*‚NN­NUüNRORiO?¼O0üO-P(FPCoP9³P9íPQ'Q<yQ3¶QêQRR6RQRjR‚RœRµRÏRèRSS6SQSpS‰S¡S´SÓSíST#T;TST9rTP¬T\ýT=ZU@˜U%ÙU7ÿU(7VK`V?¬V3ìV` W_WfáW;HX2„XP·X7Y3@Y2tY4§Y3ÜY2Z3CZ3wZ«Z6ËZ_[Kb[i®[b\2{\3®\Câ\‚&]<©]€æ]4g^Dœ^ká^?M_d_Šò_@}`8¾`@÷`38a0la'a/ÅaõaBb:Ib„b b9¾b5øbU.cU„c;Úc=dcTd*¸dqãdLUeT¢e4÷eZ,f3‡f)»fåf*g"+g/Ng'~g&¦g/Íg&ýg$hCCh)‡hs±hO%i'uii"·iÚi%ði7j4Nj4ƒj-¸jæj.k&4k+[k*‡k²k3Òk*l)1l6[l6’l"ÉlTìl#Amem'„m5¬mGâm-*n4Xn9n/Çn+÷n=#o[ao;½oNùosHpA¼pAþp2@q@sq,´qTáq56rHlrAµrk÷r4csM˜sRæs]9tS—tPëtN+€=j€F¨€6ï€A&JhI³AýE?‚C…‚%É‚7ï‚'ƒ^Eƒ3¤ƒ5؃9„JH„O“„9ã„0…8N…#‡…]«…] †:g†7¢†?Ú†=‡,X‡A…‡+LJEó‡L9ˆZ†ˆ'ሠ‰6(‰6_‰7–‰0Ή.ÿ‰>.Š?mŠ.­Š)ÜŠ9‹1@‹5r‹>¨‹ç‹Œ:ŒLXŒ7¥ŒOÝŒ#-eQ/·5ç'Ž&EŽlŽŒŽªŽ!ÄŽ=æŽ.$&Sz—'«'ÓVû+R"~¡»0Ï9‘':‘b‘+€‘¬‘.Æ‘(õ‘%’MD’<’’*Ï’Rú’OM“$““Ú“!ò“,”-A”.o”0ž”"Ï”Cò”E6•|•š•¶•;Ñ•' –F5–|–B––CÙ–*—H—.\—;‹—7Ç—ÿ—$˜:˜.Q˜@€˜#Á˜2å˜1™-J™!x™š™-·™"噚+(šTš$gšOŒšÜš-ûšY)›1ƒ›?µ›Aõ›77œ4oœ:¤œ ßœ0ìœ9Wo-Œ:º=õ33žGgž*¯ž3ÚžDŸ2SŸ#†Ÿ"ªŸ(ÍŸDöŸ(; $d *‰ (´ Ý 3ò S&¡Jz¡CÅ¡J ¢CT¢P˜¢Ié¢%3£:Y£ ”£$µ£BÚ£E¤>c¤0¢¤!Ó¤1õ¤'¥ >¥q_¥UÑ¥'¦@¦Y[¦=µ¦2ó¦&§(C§l§1ì§L¨7k¨4£¨=ب8©@O©<©RÍ© ª&;ª/bª8’ª0˪Güª D«)e«.«$¾«/㫬73¬^k¬<ʬ;­3C­.w­K¦­1ò­6$®?[®\›®ø®1 ¯2>¯>q¯>°¯ï¯°"°9?°:y°´°<Ô°1±@C±(„±2­±Hà±4)²D^²£²8À²*ù²2$³9W³4‘³IƳ6´6G´D~´/ô,ó´: µC[µbŸµ.¶&1¶CX¶+œ¶(ȶYñ¶aK·_­·j ¸Ix¸i¸M,¹)z¹&¤¹-˹)ù¹O#ºTsºjȺ83»ul»%â»7¼6@¼8w¼7°¼Nè¼%7½$]½1‚½0´½Eå½)+¾@U¾L–¾Eã¾\)¿#†¿ª¿Å¿ß¿õ¿C ÀDQÀ4–À(ËÀ=ôÀ,2Á2_Á5’Á6ÈÁ;ÿÁ;ÂPÂiÂ${ÂP Â.ñÂ8 Ã'YÃ>ÃÀÃ*ÖÃ$Ä6&Ä']ÄR…Ä,ØÄNÅ&TÅ1{Å­ÅKÀÅ ÆÆF!Æ&hÆ,Æ)¼Æ5æÆ7ÇATÇ+–ÇÂÇJáÇG,È"tÈ —È@¸È.ùÈ(É ,É16É7hÉ- É3ÎÉPÊ+SÊÊ&ŸÊ8ÆÊGÿÊ=GË9…Ë9¿ËFùË9@Ì=zÌ8¸Ì"ñÌ#Í38Í/lÍ-œÍ-ÊÍ?øÍ48Î4mÎ/¢Î,ÒÎ)ÿÎ)Ï#9Ï&]Ï„Ï'›Ï&ÃÏêÏ%Ð.ÐIÐ ! dÐ oжP¤/ ð]Sûi Hz&ìÒæìrX~;ö:™çlî ! ¬Qi $‡z† ¡ÿ:‡øb£Eu] ‹K¢ÞÀÒ? ¥þRøþBq k Jb hÓrÛ³¯ã\Ì íþVðW@\CI" £ ºý @ÐÌ‘ ÖQ mL—b!,¾îE† ÊW7Üï ˆ*B5± ÷ ŸëØÅÊ * ! µ1I #Ñ–iOx§ú¿ï 3} õ4X©jË ÓsýïÀž  ! Ñ]® h Ý BSEO Äi& œ?Ó ! š£ á~ðôÏ! HÈ9™¨;V^ð±Î ! # ZÞ% Î8 ! ¦µù ì(Ö5ë È×ÿ«GO( þ ¦ìsq` ú¦ lÝtî G Él©°ƒë& Šš^ ! Bºq ± ! gO© ! àÎ"Îc ¹ SŹ'ù¼RHV“™ ! ”,X ! /-ÚB Î Ìå7…R ! Ž1 zµ ! ( L ÙˆŠŸ K”âÉŒ ¾1,æ¡Ì™c~Î ì•@Ìc¹cvàß¾Q ! 0DØo¤Ø-P a lŠ Çí ! !È Kñû ° ]z"™ ® Y"âÆ3¥P V(áõ¬/ŒÜZ > ,ô\ü ! ˜ ! ÕÝ ,{- öñn»Ô‘ bÝD² ÎFN¨Ë Þ“ð“MŸ¿½ ! v/H·Jš ! ˜ zQdíéLh¢^aÆûë äÜò¶U¤q±iG ƒ¼fÄ_ ‰½U Y¥æFãRZ E  ÆŠˆTAé”@ûû¾–j ÙN Šß‰—ÆËI .’ï‚DÄ: Mš ¨³Í úÿÊÐn¬‰ƒ š?ƽëâû ¥k0(§¶â ðLz ³€ œëq&F Üu »„W ! ß] !  W ï  ;t¼Š¥hW¼Y~’H } ] ¿ zþfÀÇçth„¦ ït¦ .UÞ$¬#m}@/ÇØ<< > Æo ùA^ ! Š´ ÚX 2„aGñú k‡´Œýj„²1 ôp âsÛq«Ù ’ ¸Ã. Î  ÿ^Kâà¾é W›$1 B{ ! o¥º Øk£ …è WõïÜ ‘-n1ò¦!Z ¢¬LŽ ! " ! Ó[jsú. £ÞŒ´ÿ(ÄH§Š b£+ýƒ ž ó²ž70¤=RÅçnäM­`= i }&QÖ ü1&­¡\  ! 5 ¤_ÖˆF ! g¶ïB@ àA Íhn Ö¬ºhÐ1 ! 4L°ôö¸Z–¿" J‹‹k ! ° z o´æ  ¤öX>1o « ! – 'ý&_OfËu2¥°-Ø3þaÞÆ ! £î¶ ‹£µ‘?UŸžZ~3É íãó, ! ÿbÈcN¨Ùúòl /·Ø€µd Ï ] Ž0Æèá ! Æ›¶ë•ò õ(:+…*y  |* Ê:¥w9æÉ«Vy‰h  !×égê ô¶¥žz [Œ>• ø Àê…÷o>Òþ … ŽEã& ! ´ ÄpÐäóÚÍ ¼T ä\ Ʊ ! Ñϯé ! @¨ ?É~©s žež>Ô 2 *n¥ñ *6 …eåP ! Oˆu„´¬ÇÕÖ¦nrŽ Ç& ¤˜±¸(¦i… +¤ý[ 6lŸ¨Ûû m“péŽö)®š—c~ ; Ú90 ‰“ K: ! d_ ! [9ÃkJž ! ßM)© áYô2 ! » ¢o x<ÃK ! ñ|mª§¿ ÈÝä´”g¹ÝŸµ—±Ú;Ç ²~b9 éàzôI¨õÈ ! CÑ ! •Sêc(ŠµÎáz-0 \ €§ ¥ ! ä÷Y qF¯ 3 ì ʪ©œ’àD»ŽuÀ64ƒ¤ “  w ! T =;Ö†_æ eÌ®I¾‚ìºö®ˆ| ! G ! øbåo h†£èº ‚ÇF ¨Ø BOë c×=gÙTší ÅK Ô–´ª¦ ! mBкš€„ì“Ð#ÈßÔÈ Éæ#ž “))A!$ï¢á‡NKböw/sv3LdMÍxö1"H¨?=ŸÛ õ «g‘ÝM rå–Ÿe ! ¡°T: ‚l °¯ ! #þØ4 5 œ âð J âD »‚™!ü}' Ú evDÒ0-¡‚ ! ð@é} !  ªìëöA Áé%3É‚Nìñ ! šWOTµ ‰\\Þ ¢xû(ùÿ~7-  ! R Rˆõ[Âmf ! ï !  Øó(cf" ^ `©Ô [{¦  ! ÝÀp Ã9é/‹ ›ì †ÂÙ×Q rUö ˜³i  š òðÌ› 0ý ! XSP  ! rê%t Ž  ¾ç¬AŽg2Ä«Úü W ¸c ²  àr …I\ ¼@ ! ùŒE¬Ydq~K±É ºô‹£ JZ”g5Ea5Ũ–cT Z"ð ! Ù˪K‘QÒA¤”ê=îN)=÷ (#Õжw \·:J  MÏDn_[z[O ! D ûÚlæ¤ ÃŽdà9 !  |‚ MD QS"Á —õ‘NVw …U³'ÿ¦GÉ­…M6¤™Þ; ! Å ! ’š-èR ! Ó%‹ - x Á¹l~{:@Y H œm O¥ß|;®f¸ ! ¾H ! dØ›¤äÚ Fn+3 úa SÒ Kš Þ^ÄO{ ­ §\ãÏ ¥¸Cò1ov ! xO³ 4 í (ª•t„Ô¡ ! iC{Ôä†^jšÐ»J¼< ! ã ! ]TP† ” ‰_ ·Êù†9¹Oä,Ã?ztD³ Ðè ÁÓ  = ³8 ¡‰¿Óaÿ¿öÇË Z[,°‰2è{FN¯?KeöZz Ý ceoü¸ pÌœ  ž¯×ÙÄ£ûwÞf Ú>pB cêF­ƒQÕ< À^§9£F ûÑéjº™Qû¯³ÊuPM»K±S !  Rü!"^sm# ]© Ä ! ¹=k¾-Ó¹<ËÕ Ô ™ Üǿۼ˲œ°Zë¹ ! c§òC8 ! ã ï ¾ ~¡™U0Ê%ºeS@= !  YmÑFl ~ •üJ ! %·%ìBË*A öÚÆ12ú^xq/)µÐlè ·0Hõ — ë²¼Cù Ñ+Üñ3 ñ –Ñ 7 #>«.+ ~ Ñ iP =å+– q îÍŸ‹Lþ ! p ©Ç÷Îå  X P¶ ! „ vé ! å  Ëò ­I ! ì$ÉGó+ Z?è>2ÐYËW&˜´ £î^V‰Ø‡Äã >𩈥HŠ:@ ì| V—0 ÖÇXJ¦˜8g)rjh ! —ýc^|ë òæ¢a;ˆ ›Bî© Í¤ ¹(† ! §p‰ âÛ¥î .|„ ]ön ! þh37­ ½ φ wè¤. ›)¡ à× ´˜å ! 未B§‰çá Œâ1Üôï\ƒ¯qu¦7Ù ìSk’5¬oà ÙZRQVè! ½ˆ³E| ~ Õ d‰ ‡ ! ¼‰N» ݱÿ”ÚN÷ÃI¡ ’À M‘ÀCù_“ « åâ=… ¼Têâ ! —_ u  «sš»ÜÓè ! sÁ ²ÞÌEIñݬŒ]`|©†žþ ­ ! 5½É˜:DJàüLþw ãdª tyc ! ¡áó~oŸ ¸U [Õ; Í8ó¾þ Eõ ! “ú‘¿ ª,ê›f nÉ®³øÝ ! Ç7ÍÏ3iwÍñ¹€Æ˜| Ý9ò-3 ! µ·*ˆŠ‹Ñ ë¹ ! Š ž»aqCÁ$ ! û¶ Ê¡A¸gÝà‹2 ‡!i /8/1bnÞ [­X#*ƒ pÒ 7„ñ ! ¤£ ´ì¬ |‡† º†xµ’õ›Rë Íò ! ZR/Þ ‰Nbƒ= p“£QÓ1 çV“²6u9³{ûT­ã ƒðG¾Ô J ¦ ÙQç? ! Ü㧈ûSðÍe{ë.Ä nÔx íU§ Å>¶°×:u™"B¨§kÔN·d Ü)l šâ á™_Ø "  óë ¡Gu  ! Þ ! féIØí ù— ! ´ê/^ ¹3 ½U )žØº¨ “ÚõË,}î.}×D 7zÇ÷ z <T]Gg´D«‡ È ûb ! “ ó· ! ®”: ! â?8 ߇=ü Cr? üó% ±mLÝ®âh[ó m • aÓ s ! ¸è ÃuÂÙåD¥6V ; ì] oûXÔ4yîþ7 ! Œ' äÖÇÕZ¨üëm å ýAË × ! ƒà¶lý¯ê’ ! ?˜Û ¸ã ~.ÏÓŒE ! ”ÛðA ! þç b»íâ°9ŠÂ«c’Ä ñh” J¾—gø Må> ·º+^A ’¼ø·ÛáëÎa ³¬3Ó€ ùE\vÉ !m¼Ù¯N% ! Üuå#|Ü ! ¯¼fdíò®¿ xµ8È(çÇÒ\t €xOt ! 4=È%F U;)u ÑdÔóÉž&èࡇ0,=®ñ ri> èH)EF¦™ËŒbØ6»ûvÖjûá1<b8Á@$r¨Â›R= ·îe 8•¾«T½PL× ÿ _˜dò ê@`> ! ½üw®ÂG´Âuu'àF³l2 Y” J#€L íõ•¤ßÖ³žP†Ì_(R(3’£ùà ™× ! 54«o** Ö Ù½û d õ CXy;Öÿ ý½  o¢úDl†½ ÉÑ°;∱`ò Åà#ðÂëo ! æS¦ ½•k)`­þ”Iä Ú , fìÙ0tIü ! îú%?i ! AÝk·#P”×¢?¼ ! x$N ! ŸU v&¢ W „+ í_\û-ì݆è”÷Ì¥Á¢“7 ‰®Ïx/õõôì ´ ! œ”â ÄõÖ ! Ì„©‘½ ·”ÖƒiD ! @âr,dÍ•‹—GqÌÄ g|Æ·Ó0—›í²øUaç Cï¨ ! y˜«ÑÙ©…œ ! *nøM «:swIä ! øÝà ! Àà Z$5¾ä ˆs½ 2á€] á>x<°hlRJ©][%Š ÜN ^"QrÒ¾Eâ笀´ „Y «zkqV»à Ô –:- Ei5  ‚Ê ! „ ¬»úôÓ ÐÈsPßdR ª¨ F–h"¬S @DP~¥_Nø>ðæb­}7rÚEÙÏ ! ¨ f ßPv ¹k ! ç‰hîD¤œ S È ™w+ ! »‡Ì ±é‰ * ržØd– ! >õ ûR"e.`k—A› ×½†VUC ! Œ*U ! îÙ® 9Ù8ì ! ÖÍ3ï~+_ÏhÊ/ T•åçQ8{Ôÿ .]9&™0 5ô™vtï^„¿g BC÷V [%8s§1 ÄÞƒìR|ê¸õ'¢ ! Æ ;â“Œv¡ Tî ãÝ Â¬Eîñ ßÜ{k ±§zZ4 …”ŸÉŒ&Ï( ! ©ËYÌ,Ì Àá Y­ŸÀ8"1fƤ"7<Ï–>ÃÊónª¼ws69 ¦-²Z•‚ ¹êÝ Ò ! ˜ö_ MÏJ™mpÑä @.ç Û…× ÿ2‘ 1Á ! ¸ 4‘a ! ÖÊ k¿¤Û ! 0%¯³)Ë϶ e2ÁãÅ ¤ ïŠ dµªÓßÕ]º|H8 ¡Ò&Î$b h †ÐSNñòC õ † Ñ’¬ DQΡ[­' ! rÎw÷» ! 4u²$‚Š÷ 6÷ _^ ˆ·:è) ! —jdk [ yA Ït •%óÉ,fèGáO Ÿ“² µ  ! ‘ep ŠÛˆ :ýôI¾”ÿå}Ÿ‹j ! ÿíRPɈžƒ O°" óÚxš)Ž)9œÞu´úÕ _`¬0 ! ô ! Ý’J5•àÈËnÌwƒM øØ`Ô²YŽ £€ ¢&<9†› @ ( óœm A þ‘Ra´Ãö ! ^ÎÎÈë ! ¾ E Ç Åè`‡+ÃÈVY… ! ­­`ƒ\ÊSH ñ†…ù C% ¹WV.°Ó‘Î £q‹ïßï— ! Qî_I2 6Fz ! äþç« ãº 2· —í‰ö¯s yÿ:Q?N Pž#Å÷, U‡ ' Ò¿R›g þó!vÉó‚ßl0Z%^baé @Èæ j l@ Œ ® —ôLx Üe„¬çÂVÍ|%  qêü‘–D}d1¾+‚\ Š#mbÓ (².¢Ì ¥ „  7M¿€ ! WÎ VÝ4J _©{HAA; í¾þcóåZ{ ¥ä&a 0íˆ ! v ¾ >ú }ó ?„…æ_­ô€Õ ! d räÙ VáXÃé Û ÑŸY€ð¾Oga&Q ïŒ<Öäj yîî ,à ¨“ ¹fjHÒꋧH €1 ç-0B   Áv n t K² ´‡Ç XÞrÛž©Gií \?ù Ò xXÿ5 ¶ùxÒ‘ ™F„‘f [ͲÔõ°$]Q ÿý!|vºP À}Ê/ëæqi¾"‡u}5cªêS ˆA` {Çp ! ëyo‘ƒð> ä­ Úí[ ! ë<‘Иöêeyx ! [êªßc@x; … ±Õ°ë6gzÉÆ$2‹†s9_|!. 'kþ ÅÝßG ! ©k QCM‘f˜Õ;~ïbP) 6+• w ShI- ! û,ýb3  ñ½´&Ð å–…j m !  „ˆHWš©}X Öí+e* g !  ! À | õÛ Z- 4|9kê+­c«M#;¹ íð7 q œ] ùnÛ^*é ^>;Å¥ s1y”“¸NÆœÿ ! ùõ u e€ü8 ­£ !  l—ô¥DJXN$œŽŽË ! ¯7Ò{ÅÐy “N ævâ‹áiPVê ,u?åÂýÅFœÂë'“²&¸“ ! Tá6YOî-ð ! Â; êL+ñK‰!¥J¢£GG» %¶ï¯yï ‚× xØ o'Æ}îw» ج èˆá Uä/TPªº‘2ùl;ÒÖ $žÅ  I/ nè Õä a¿Þ”Aƒ<R p×{ ÑV Ò¥G ö(E éX÷× ! t,ݼc‹-Ô?:e ×’ßÓ½´ ¦ŠùjaÏÀ}’¿ ÒHZù24MÚÈü2 œ¡´ÄË3)£ ! y ª¿T zÀ#p6 0Es …3OÎÜeÕK âý½ß©“’ ø Úí ! j!˜•f ˜ Y•Ê} ÜËátèºÓþbÏfn$ Ž H ! ŹÝé ç ! [ Ú3( Ä ! ñNÃ"Ø • ä`fú¥ KeJÞx© º‚òqL·œq ! ½¯X S ´­æ3'–ÙýɈ „m“›Á˜‚!á‘ÌÊZ šn’É»Røü~z{ay ! ÒA7 …ÑÞÞŒß C <`xÿ|–³ |­/äÊ? Ùúž 3üìM»þ¤ qc ™ r` ‰éˆê ! ”Æ a ¯ gíÄ5g%  ªà& Þ ìãòUÁÄòWîä ø ™>K Ì ! ȧË˵dXçE ù™ %¼ÉŸËmõ| F ­4”~«› ! â‚ ‡×Ô>B•+ðCÐ2o’ k!ìI¿Ò‚iC ™.ø®ðu$ „Xœb ! T ! †‘|kK¶ÄÇ—çá Þ 02† ! ¬ ! ŒÎB ! ©LS7Æý˜ j§ è8Ïøl/–/I*à[®59 ÉŠ¨¨ÅŸÑ&š?òJ^ ¬÷0ÿ·`˜²«šô ¬ós¦9ÂEÞΨWØ)Œ} ! [Þ¯]àÇ”ìù ! téN8@ÃÁ²K7 ! ‹Í ¿¾܇ Cÿ„èËE];Ð ! ¦bÅe+ÏL³+µ o;kB ®?¾ ! C 0, [XJ·±(Ô Jiƒ÷tI€\ûºÍ¦’Cw5«R‘4T ! /üek÷›³|‡×Ð=¸ÍPÒ9 ¼ f œš¹ŽøÀ ! ãžÛÈ6.ø) ˜Óå /Ìì f“Þü 7« n_2Ÿä0['ሠŒ® U  <mú¥e<6{P Øãà ÂVˆ¨w 5 w§®Àš»[ .H)š Lܹ{}+Lõ4Ú ! k º> ý: ³' j÷"÷EÃF„˜aj ½ÔµòY²<du ã¡ šýî–ðl˱Ÿ h ð ! ±Â‘Il ! ƒl æå*ý O ! ¢ 'Á Dèùjø]¿€›–¦gÍBø ! ¨*÷‚ Vžú˜ Õ·  ! '\üû ² ! ~…$2} ¿M‰'¾Ú _¼ ÔI – X›†‚b S zÔÒ v”/ÛèH*À;Åm°±° ²Á“åôWr wœ%Š ! uG ]$³$ r ! Äí<Nú‹2Û ô ¸ña¯ ›@çñmøòü­çaúس` r#g•g ª ƒ ! «1ý¿Ê ! M§T}¶ø »/ ÀœOUË_ ã}Õòr×™ £ˆJ= ¹3–kOzŒ Toϧʙ<j]® ljDsÐy¼ Là Ð^Ø¶Þ ú ѵ@ °Œv¸ $ Ê ]Š€m‹vz±æ±öwå>½päK·CÓ ßŽùô³\• ! ¿’ž¼Ô§‚iIà¢08u -&EûrÔÈI–Ì¥Ü.„ñ t®Å ˜ ¢Ö Y×–jp¤G np „…¶8¡Ù½6Ûö {µ=È ! ! ß.ÿî‚:cQ ÉÅ¿x&Æ ñ ! Õö¸ô¶Ñ ›ƒü`3h9ä —+ qPR ø& Ê ! \¾(°eWL ! |° Ó*w§® •½E Šr gþW,h;  «Ä÷•v|U$ÕŸV ^åú ! 9U œa Î,%y-øz oÓ) 'LFt° Ï@ê ݘ\ ² 9j» þ ôY‘ ! 2O —Ú‚t½d») ³ #¥t« *Z ! Ÿ=«¯¼‡ */sôj­ê iA‰– 4 ! y ÿŒiËk ˆ †Á Ë á `C…¿"zrO¼ýãiÕEK‰1?Ê· Ï•ÚKe À é U J,0"% —djÈü2‚‡`×uu0Mòóøº ! ØE•ÿ帢Ö[8a$Í×”÷yµéÌ_ÀSbmPéÀ¢ œl"Ýîn 4 ß ¸tŒ±  1ÙJN‰„Ç»+ù Á®” :÷ ! ÕY' —c ! 6 ç=` ! ©Óþ3ôŸ@<‘-ǘŽv&d ! nãWðw.!iÞÛº e s Tð?[ ŠK›ÄŒ ÝQ@w< Ï6~BdþÎqÏŽ¡ jÊÅjG2r ¯bYêU#4 / ! 1(°4v ÄÓ§ ! 4±#Ï«'Í’X‡à¶¢É ! K®‹ Î$ù  ÛíÚa S‰Š¡ÍƒÐ ±4Ñd!Ü ¸Uï€Z Dfëxà <l #¸Cªô‹"C§<ò‹® 1;ŠǾ ñ’­]‡Ûê ‡# ! .£ ð ©}ÿ 8ÖÃHx ! hඉ ! VOª ! ÷ 5, ÷̹ٞÚQ{&¼ˆ ß Î®¬À-[÷!Ûj^ÊSÈvŽnÁ¡Zþt ù K]²QÂS 74u ! ] €•pûI5XÆ(^-YC U ! ¹x BŠpMG¼g› 'ÚŽ6“oöÍœ­ÆKÇŸwFÉ ¼ 5ÁãÉzOPÑtÔ ! ÐßgÓvúš»ú1k ø7Ž ¯„Y¹ © F ÕÊ ³’Ø ! ÅD} Ú\¬ î x pIÒ ! p8ÐA‰ «,Ñ +Ž*v±JŠ¦œ  £Ç=9› šÁ²º¤38 ›óS­ g êS„ ïÎ,DM *pj< ¢ ! †ÚŒÓH¿ ! ªýÉÈç@~Ðê 7ó¢@Ïëµn¯ =® ! XB q! ! Áö {äý3–©û ! Þ¾+«š æ ¡R‹>Ræ ! Ç ¹ .¬# ! ì§Mç>§ õ˜Ùñ|KÁïñãžÂ½2‡l Á›á¤ ! iÐ{¸áò–—  :ZY¬ ¶æÏ鯠—ùÇÕ5Å£ª C·2–  ! çÂt¦ª–òMŸ eo¯ ! Wºúß ! m2ÈÒúy¬à ! _×” ! ü3 "ñv,eÍË Ç î -5$E6ÊL ø AQ†Fh“£Œ8âY W¿ÝZ ! IÑ岎×ÄÙòy€¡e1 ! Cáb:™cyTÂé# A 'm á>^qÄ t+ ! )¸ QãBQóN v ³Qô€ 8¡tÌ…ˆ6ÔfVð µ'o}  °ÜBÛKÆîGæ=6¼ãµ4¹ ç :c ™Ü ?Íú fe Ö/BL€)yU'Ó*ë°‡r º L žµ';Ä`‚Ws¶%Gó rßf$ùw½}þ²O ! ´Ü ]8Õ7Y”¢ö’# ƒ½uÆ% X ‹6> ­ ŽÙD GƉ6ÃsÛÿ4:æ ‡PðhN±5<HSµ<ß Ë­c.f¿ „ ! N =NïÅ ñ ¯¨ ¼Vzó Á#Ÿ ! •+4y ! .M ÊTP¦ ! › ëït¯ÎÊÜŸ‘=L ! ‚²Uô¡¤7Vã“÷ý÷í5ü= Y ! GÐ LF\Ö&=šìWµ Ÿ¶ûå¢õhh Æü õÍ `d~™¦ç×!íÄmÕ `Š”§¨€ ! nFG\ ! OÒ†9õHB5 ! ó ! ]¦ ! ¸ º§ªÃÐ â — ý Ò{åØ ¶$Õ ˜7 H…,Ìÿ\? ! 3£§â,lÌp é c~ gbÁãÛõÑ®°›. ! B ! ?L {¶9Í°ï\W)ø µŽö- Ã'ç¢$êVÜ‹:J¨€mßœª"Aý€*¦L´éÀ–æ 4Ê`ÖÏ .f}œ‘üÃ5‹p oª º ! ¶·s ;p+ ! ò6íõ —ž~æ9oüM ! &ÐoÆÛ¦6 XZ¡!ÌT_é6 ! %¿’Á Zí ô )ÎT_xªÈȼ'Ò#»ñX> ›a»d  ! ã…PTn · Ì sÔ ü T †T º¾¨ è/^± qo#°´lÑg¿f² ¤×MÁ/p7 À ! —¢^´RsBpŽòGÆ{iu;}åH¢ÉŠD Ž p ŽHbƒ\æ : È— …*.žh®™CÂÙ Øåkèó%? ´ªšHÝhaBDÜèþ³äèÑ©ë ~ ! J¶WA ! « ¢+ÛÛ´q Gú pÞ<< K )w7X™Ú Í÷Œ ! Ç9Õÿ· Î 4Í ! vnÑq ! ò TŠÍ€ŒŸ(…y¡¥` ª \1¬šw W³xÂ6 ƒ ѹg ‹ ÖP(áèï·% ‹ ! ¤ÕÐ ! v0¸Y ³ ƒý¨ÃOˆ6ÖR¯Už ̨Ÿ‡aœ ¤RA@ý ©Àµ Sù â o¯ 5%W ! }à‹ 8ì¦íEÁæA ! {*ïfÅrùç!ÓÔ ’‚˜D8_z¸Î Æ { î ¯…kÀ'i $¹‡âñß8N¡û[Ö¢ {&c7Ö¨½ÛW© V ! ó¸ÒÏ Àßö»Üy'! •`¥ ö" ! ˜·{Ù ! Xy m(³ ! âŽúF£0Á~ ± » ƒqæ[* æmW qÓ?Fµ ( ! × 5 ƒàO ¶ $Õ| á‡Àä" £SêŒÅ:ƒ ÜU‰•F’ Ôĺ ! ‚ ! wF s:)øQéªI £ 㤠A€×-GÕ±à¹y Žö`’.Øy!ö håiÄ3‚- ! ú€Èô It’ 4<-÷=° !  `Ò Ls·ô±Ç ! ‚¸!Ið  For bug reporting instructions, please see: --- 1,1588 ---- ! Þ• $¹*,««-«1A«s« ˆ«Û©«+…¬0±¬K⬠.­ ;­G­<[­B˜­RÛ­>.®@m®9®®Cè®F,¯5s¯I©¯ó¯ ! °!°$A° f°‡°"¥°+È°#ô°±©±¯±'αö±F²3[²Q²7á²8³8R³5‹³5Á³]÷³<U´w’´I ! µATµ:–µKѵN¶9l¶B¦¶Oé¶L9·R†·;Ù·8¸>N¸I¸I׸B!¹4d¹~™¹?ºDXºEº@ãºE$»Cj»=®»Pì»{=¼B¹¼?ü¼‰<½9ƽ/¾P0¾C¾FžE ¿ER¿C˜¿QÜ¿N.À}ÀGÁŒVÁOãÁR3ÂC†ÂQÊÂFÃ9cÃ=Ã=ÛÃ4ÄPNÄMŸÄBíÄG0ÅIxÅ@ÂÅHÆBLÆ7ÆIÇÇÈE.È ! tÈ'È8§È.àÈ.É>>É}É)É0¹É<êÉ+'ÊZSÊ+®ÊAÚÊmË8ŠË(ÃË;ìËE(Ì nÌ̷̤Ì$×Ì$üÌ*!Í*LÍwÍ’Í ­Í ÎÍÚÍ#ëÍÎ8&Î!_Î;ÎE½ÎÏ5"ÏEXÏžÏ0¼ÏLíÏ:ÐMÐ7`Ðl˜ÐGÑ$MÑJrÑ*½ÑEèÑ2.ÒEaÒl§ÒÓ30Ó@dÓ¥ÓJ½Ó8ÔUAÔ—Ô«Ô-¿Ô_íÔYMÕl§ÕXÖTmÖQÂÖK×L`×S­×5ØI7ØYØcÛØ"?Ù=bÙ Ù#°Ù#ÔÙ5øÙ9.Ú1hÚ3šÚ*ÎÚ4ùÚ..Û2]Û4Û,ÅÛ6òÛQ)Ü3{Ü3¯Ü=ãÜ(!ÝJÝC^Ý7¢ÝIÚÝI$ÞWnÞEÆÞ" ß9/ß.iß"˜ß*»ßJæß21à&dà,‹àP¸àH á?RáF’áDÙáFâEeâ?«â=ëâN)ã@xãA¹ãûã(ä*Dä:oä ªä!Ëä íä&å45åjå#ƒå§å.Ãå òåæ.,æ![æ,}æSªæpþæXoçUÈçHè.gè;–è]Òèy0é7ªéAâé?$ê!dê5†ê@¼êKýê>IëfˆëEïë!5ì!Wì'yìj¡ì( í*5í`í-wí¥í:¼í"÷íî9î$Xî2}î°îÇîUæî-<ï?jï?ªï0êï+ðAGð.‰ð*¸ð2ãð2ñ1Iñ0{ñ9¬ñ1æñ2ò1Kò+}ò-©ò3×ò. óD:ó3ó$³ó+ØóCô:Hôƒô6 ô@×ô"õ1;õ4mõ$¢õDÇõ1 ö/>ö1nöE ö2æö-÷G÷f÷…÷E÷<ã÷; øE\øF¢ø5éø9ù*Yù*„ù?¯ù6ïù8&úX_úE¸ú3þú(2û8[ûR”ûVçûQ>üUü4æü2ýZNý`©ý8 ! þ/Cþ-sþ"¡þ8Äþ3ýþC1ÿ.uÿ/¤ÿ Ôÿ(õÿN>1J¿' ! "2&U|1šÌ%å1 <=9z´,Ô!&#(J5se©%?54u/ª=Ú:,S6€:·3ò8&_%y6Ÿ*Ö!W#J{:Æ3(52^D‘5Ö) o6 )¦ !Ð +ò : ! =Y ! 3— ! !Ë ! 9í ! -' %U 6{ /² #â 9 =@ G~ -Æ ô 2 #C 'g . 4¾ /ó 1#AU-—1Å=÷,5*b/,½+ê*2]vJ–á+p-ž°Á+Ü-6T@r³"Çê:9<9v"°3Ó!)B]#}$¡AÆT"-w/¥ÕFê1+L4x7­SåG9%§!Æ*è$/T*qœW¼-#B*f‘!© Ë ì, #:'^"†&©Ð#ð'"<&_-†´.Æ#õ6:T¢$Á%æ #*'Nv6•Ì%ë1Pk%†¬3Èü1]C¡0·/è# < P o ,Š A· *ù .$!!S!*u!! !'Â!Hê!53".i"˜")¯")Ù""##&#J#[#$k#(#¹#;Ó#($8$W$r$‘$$±$0Ö$5%=%"S%"v%}™%2&6J&4&C¶&Jú&*E'p'6''Æ'Iî',8(.e(1”(2Æ(;ù(65)5l)¢)%Â)è)**37*0k*œ*4²*ç*++(1+Z+-y+/§+(×+",,#,'P,/x,1¨,'Ú,5-08-'i-1‘-3Ã-6÷- ..?O...-¾.+ì. /9/V/*o/'š/*Â/í/]0 e0)†0"°0'Ó0+û0'191FO1–1-¶1 ä1221-2\_2L¼2I 3MS3K¡3Zí3kH4[´4K5N\50«5/Ü5# 6-06&^6…6œ6>³6+ò6 7*?7.j7™7,¹7æ7þ7*8.F8+u8'¡80É86ú8C19:u9;°9ì9+:4:T:s:"“:¶:Ï:ï:);)1;[;v; ;#®;Ò;è;$<(<2G<z<•<¬<1Ä<5ö<',=)T=~='”=0¼=6í=*$>,O>0|>-­>+Û>!? )? J?k?"‹?"®?FÑ?U@Pn@'¿@ç@'ú@$"A$GA#lA3A$ÄAéA'B.BJB-hB&–B*½BèB,C.C7HC'€C#¨CÌC!ìC%D#4DXD!tD –Da¤D*E1EdBE-§EÕEØEÜE2ìE2FMRFM F0îFG &G3G©O,èO,P1BPtP1P$ÂP0çPQ7QWQwQ“Q#§QËQ+ëQR+RCRIRYRlR€R˜R´R:ÆR)SJ+SCvSºS,ÒSÿST, T ! :T6ET|T$˜T ½T#ÞTU!U>U(WU:€U»U7ØU(V9V5YVV£V)½V/çV!W 9W'ZW ‚W0£WÔW ïW ýWX5XKXdX~XX-«X"ÙXüX!Y)8Y bY'ƒYY«YZZZZ$"Z3GZ{ZR—Z%êZ[["[+[4[!=[_[ {[ˆ[ ‘[ž[§[°[>¹[>ø[F7\~\I‡\Ñ\í\Hö\F?]†]-Š]5¸],î]^ 1^†=^7Ä^rü^o_*_<¸_.õ_$`@`5]` “`€¡`"a0(a+Ya"…aH¨a2ña;$b’`beób(Yc+‚c.®c+Ýc- d7d|NdnËd3:eAnek°e7fTf.hf5—f#Íf&ñf$g.=glgˆg.¢g,Ñg,þg*+h%Vh-|h`ªhG iJSi+ži:Êi$j+*jVjpjŠj)£j.Íj>üj<;k;xk$´k'Ùk/l1l;Ml7‰l$ÁlælFýl"Dm!gm:‰mSÄmLn3enL™n?ænQ&obxoBÛoEp[dp-Àp îpPûp‚Lq6Ïq3r6:rGqrQ¹rH s#Ts#xs'œs$ÄsZésDDtJ‰t?Ôt=uBRu1•u7ÇuAÿu*AvGlvM´vLw=OwKw;Ùw?xEUxb›xJþxBIy,Œy-¹y/çyNz6fzZz9øz82{wk{Xã{2<|;o|'«|Ó|0ê|4}JP}<›}PØ}A)~Qk~A½~ÿ~=4Y<ŽMËE€/_€C€GÓ€z:–%ÑR÷6J‚d‚)æ‚6ƒGƒ7Zƒ'’ƒ*ºƒ/åƒA„LW„6¤„CÛ„B…+b…7Ž…@Æ…=†:E†A€†C†G‡2N‡(‡.ª‡Ù‡7÷‡;/ˆBkˆM®ˆ6üˆ43‰,h‰,•‰(‰,ë‰(ŠkAŠ/­Š4ÝŠ@‹.S‹+‚‹+®‹/Ú‹6 ! ŒHAŒ9ŠŒ'ÄŒIìŒ+6/b,’,¿Mì+:Ž'fŽ'ŽŽ7¶Ž!îŽ%6+L/x:¨Aã*%*P,{(¨Ñ=ï?-‘>m‘¬‘>Å‘/’O4’D„’:É’“5“%U“&{“?¢“Oâ“ 2”oS”'Ô4ë”5 •V•&p•[—•8ó•(,–BU–;˜–6Ô–4 —"@—)c—Q—-ß—2 ˜1@˜#r˜$–˜%»˜,á˜3™-B™p™)Œ™,¶™:ã™.šMšjš‰š8¥š0Þš)›29›;l›¨›-Å›6ó›$*œ.OœA~œÀœ3Ýœ'#9]&|A£,å-ž+@ž+lž˜ž,¬ž#Ùž>ýž0<Ÿ;mŸ ©Ÿ3µŸ éŸ(õŸ 7  F !R  ! t  %Ž '´ Ü  ð ý ¡'¡/¡ 8¡B¡R¡ a¡ m¡y¡”¡¯¡ ¡ Ï¡Ü¡ì¡þ¡¢ &¢0¢@¢P¢ c¢ ! m¢%x¢.ž¢6Í¢!£y&£[ £7ü£O4¤2„¤2·¤0ꤥ?2¥5r¥¨¥+¸¥0ä¥$¦+:¦*f¦A‘¦:Ó¦B§PQ§w¢§C¨'^¨7†¨)¾¨Hè¨J1©1|©'®©‡Ö©V^«Wµ«F ¬)T¬:~¬¹¬BÒ¬7­M­f­ƒ­˜­­­­'×­ÿ­®$/®T®+t®# ®/Ä®%ô®¯8¯(R¯%{¯)¡¯H˯4°)I°*s°*ž°lÉ°H6±C±Bñ(²2/²6b²l™²e³Ml³$º³(ß³?´mH´3¶´2ê´*µ4Hµ>}µ#¼µEàµ+&¶NR¶A¡¶'ã¶5 ·1A·Vs·mÊ·08¸Ei¸*¯¸@Ú¸#¹!?¹Ja¹>¬¹Lë¹L8ºO…º.Õº1»%6»D\»K¡»í»: ¼0F¼$w¼4œ¼Ѽ$í¼F½%Y½)½G©½4ñ½t&¾@›¾:ܾ¿97¿Fq¿/¸¿#è¿X ÀCeÀ6©À1àÀ7Á*JÁ!uÁ*—Á)ÂÁPìÁ6=Â/tÂ/¤Â/ÔÂ8Ã9=Ã9wÃ6±Ã7èÃ. Ä9OÄ-‰Ä:·Ä<òÄ//Å>_Å+žÅÊÅßÅ'óÅÆ5Æ>PÆGÆ ×Æ(øÆ3!Ç UÇ'vÇ;žÇ9ÚÇDÈBYÈDœÈBáÈ?$ÉdÉ^‚ÉPáÉ52Ê*hÊ8“Ê%ÌÊ$òÊGË)_Ë8‰Ë;ÂËRþË+QÌ:}Ì.¸ÌKçÌ%3ÍYÍ&uÍ1œÍ%ÎÍ%ôÍ$Î2?Î1rÎK¤ÎDðÎ25Ï&hÏ$Ï"´Ï?×ÏÐ 3Ð.TÐ1ƒÐtµÐ9*Ñ[dÑGÀÑ*Ò)3ÒX]Ò<¶Ò#óÒ(ÓW@Ó/˜Ó2ÈÓ1ûÓa-ÔÔ@ Ô áÔ:ïÔ&*ÕGQÕ3™ÕJÍÕ1Ö1JÖ6|Ö3³Ö>çÖ,&×4S×Bˆ×HË×:Ø)OØ&yØ Ø!¹ØÛØ÷ØÙ+,ÙXÙ vÙ—Ù:¶ÙGñÙ@9Ú1zÚ;¬ÚèÚùÚÛ'Û.<ÛkÛ<…Û5ÂÛ5øÛ3.ÜbÜ5sÜ©Ü#ÅÜéÜ òÜ.ÿÜ0.Ý8_ݘÝE¸Ý@þÝ>?Þ<~Þ<»Þ5øÞ=.ßlß[ŒßAèß_*àcŠàDîàM3áGá_Éá+)â3Uâ‰â¥â·âÉâ=Úâ8ã1Qã0ƒã-´ã-âã>ä6Oä.†ä9µäKïä2;å8nåB§å0êå/æ4Kæ€æ5œæBÒæ,ç3Bç<vç³ç!Óç+õç?!è8aèšè>·è/öè5&é\éué6’é'Éé:ñé7,ê dêrêê(ŸêÈêäê1óê %ë%2ë0Xë*‰ë)´ë>Þë`ì6~ì?µì$õì%í*@í>kí@ªíJëíF6îE}î9Ãî@ýî>ï)Wï8ï:ºï"õï0ð6IðW€ðUØð?.ñ"nñn‘ñ@ò+Aò!mò!ò:±ò_ìòLóió †ó§óÆó(Ûóôô1ôHô hô!‰ô!«ô#Íô#ñô-õCCõ'‡õ'¯õQ×õY)ö,ƒö9°ö êöQ‹÷+Ý÷/ øB9øj|øfçø.Nù?}ùK½ù úú*2ú!]ú6ú7¶ú#îúBûOUû7¥û#Ýû7ü#9ü9]ü%—ü9½ü%÷üTýirý)Üý<þ)Cþ'mþB•þØþ*õþ' ÿ'Hÿ,pÿIÿ"çÿ: ! 4E+zJ¦ñ' -5_cÃ:â?6][”!ð#O6†)¥ ÏJð0;;lO¨%ø;ZrŽ7¼3ô3(\-n2œ6Ï#)*T*j*•UÀ$3;*oOšlêyW uÑ :G ! D‚ ! 4Ç ! )ü ! 3& #Z ~ " "²  Õ  ö $ $< "a "„ )§ 'Ñ *ù )$ ,N &{ )¢ 'Ì ô >LQKždê?OW#ç$ #0!T@v>·:ö:1+l8˜MÑ:OZªF»F"I lB©ì)*A“l 4!2V3‰$½7â4*K‰v1E2.x"§9Ê,L9e:Ÿ*Ú !&6HD4Ä,ù&F;a3.Ñ$?%-e,“9À+ú<&=c7¡eÙ:?Hz,Ã-ðX.w¦$Ãè 'F:44¶ë# ' )? .i &˜ "¿ &â + !'5!3]!4‘!4Æ!3û!"/"?R"%’" ¸"6Ù"F#{W#:Ó#'$6$?R$#’$¶$6Ñ$.%47%%l%)’%¼%LÅ%>&"Q&t&&‘&&¸& ß&0'(1'Z'&s'+š''Æ'!î'(!0(!R(-t((¢("Ë("î()),;) h)+‰)$µ))Ú)Q*"V**y*¤*1À*-ò* +:6+=q+5¯+-å+",76,6n,8¥,<Þ,7-?S-5“-9É-3.47.9l.8¦.Aß.;!/7]/%•/)»/,å/50"H0.k0"š0*½0è0:ø031.I1$x1a1>ÿ1+>2Bj20­20Þ263F3ic3:Í3*4)341]4-4/½4)í4,5(D54m5d¢5G6BO61’6*Ä6*ï67>:70y77ª7]â70@86q8¨8º8,Ù8)9$09"U9$x979(Õ9/þ9.:@:&R:!y:(›::Ä:$ÿ:$;D;!\;/~;®;%Ç;.í;-<-J<x<8<5É<ÿ</= ?=*`="‹=L®=Gû=8C>|>˜>+´>(à>" ?,?#K?!o?C‘?:Õ?@(,@U@r@!Œ@®@%Å@,ë@A3A+MAyA2˜AËA&åA8 B4EBzB/B'¿B1çB(C7BCzCE™CHßC)(D)RD|D0œDOÍD)E%GE!mEE®EËEåEF F$FAF_FyF2—F8ÊF1G+5GaG)wG!¡GÃGãG1H 3H<TH‘H2§H ÚH(ûH7$I#\I0€I±IvÉI<@J }J=žJ-ÜJ' ! K(2KF[Kc¢K.Lt5LFªL!ñL;M0OM"€M£M6¾M!õM!N"9N)\N8†N9¿N&ùNF ODgO>¬O ëO- Pr:P(­PÖPEðP:6QqQ.†QRµQ+R4RQR9mRC§RëR=ñR/S%HSnS‡S¦SÆSIÌS!TX8TE‘T×TêTAýT$?U,dU‘U3¬UNàUC/V#sV0—V'ÈVðV%W+6W5bW˜WµW%ÔWúWX5X QXrX ŽX"¯X%ÒX0øX))Y0SY„Y:Y2ØY( Z04ZeZvZŽZ$¨Z ÍZÛZðZ/ [$;[`['p[˜[B¸[)û[%\3B\&v\&\YÄ\-]1L]2~]±]<Ñ]5^5D^1z^)¬^:Ö^(_O:_$Š_)¯_%Ù_7ÿ_/7`Fg`4®`4ã`0a=Ia6‡a-¾a2ìa!b6AbExb¾bHÙb:"c7]c:•c7Ðc:d9Cd;}dF¹d e$ eO1e=e=¿e3ýe?1f%qf0—fCÈf9 g;Fg2‚g3µg?ég8)hNbhM±h+ÿh!+iIMi9—i3ÑiBj/Hj>xjJ·jBk~Ek"ÄkZçk\Bl Ÿl4­l@âl0#mTm:cm>žmCÝm!n?n&Yn€nžn)´nÞnøn-o&Boio‡oo&¹o4ào4p4Jp%p=¥p@ãp0$qUqnqe‡q!íq&r6rMr`rxrŒr)¡rËrßrõr ! s6s-Vs!„s¦s¹sÌsésýst$t@tStstŠtªtÁtátøtu)uBu'[u:ƒuB¾uEv8Gv/€vH°v¹ùv#³w×wñw x"&x*Ix#tx$˜x4½x&òx/y0Iy1zy'¬y2Ôy$z$,z%Qz0wz¨z&Âzéz*{<.{0k{0œ{,Í{ú{!|;|[|v||ª|Ä|Þ|þ|}4}O}8j}£}8¾}÷}~-~H~!c~…~ž~º~Õ~ñ~ -)4WŒ#©'Íõ!€!7€;Y€0•€ Æ€"ç€! ! !,$N$s9˜6Ò= ‚/G‚-w‚E¥‚:ë‚I&ƒ5pƒ0¦ƒ,׃>„4C„4x„­„'Ë„'ó„#…(?…0h…0™…+Ê…/ö…/&†/V†,††]³†‡@/‡>p‡A¯‡7ñ‡:)ˆ2dˆ5—ˆ'͈2õˆ(‰KD‰‰­‰*ʉ-õ‰'#ŠKŠEgŠ'­ŠÕŠðŠ- ‹(9‹,b‹,‹,¼‹)é‹Œ,.Œ'[ŒBƒŒÆŒ1åŒ.LF“ ³JÔXŽ-xŽ¦Ž@ÁŽ4C7&{H¢/ë!#=}a¯ßT‘Nä‘j3’1ž’Ð’;ï’4+“:`“›“Dµ“Lú“>G”5†”+¼”+è”L•/a•(‘•6º•=ñ•=/–9m–4§–,Ü–- —(7—C`—'¤—Ì—Dê—'/˜@W˜.˜˜0ǘ!ø˜<™FW™6ž™.Õ™CšCHš&Œš,³š2àšD› X›1y›«›9Ê›:œP?œ&œ<·œ8ôœ--[!y1›.Í5ü+2žE^ž2¤ž5מ2 Ÿ.@Ÿ>oŸ>®ŸHíŸE6 0| 6­ ,ä 6¡UH¡!ž¡À¡aß¡UA¢/—¢2Ç¢$ú¢F£2f£$™£N¾£A ¤;O¤5‹¤tÁ¤G6¥—~¥9¦?P¦:¦8˦%§)*§T§#t§#˜§)¼§‰æ§2p¨%£¨&ɨ+ð¨&©UC©™©&¶©/Ý©/ ª8=ª4vª!«ª+ͪ2ùª-,«%Z«)€«%ª«&Ы+÷«#¬/@¬ap¬ŒÒ¬P_­j°­'®C®c®1l®2ž®'Ñ®2ù®,¯2I¯7|¯2´¯=ç¯8%°6^°;•°4Ñ°9±4@±9u±4¯±Eä±7*²6b²c™²Fý²¾D³´´.´@´P´c´z´,˜´0Å´*ö´L!µ.nµµ¶µ<Öµ,¶)@¶Fj¶8±¶7ê¶1"·<T·B‘·CÔ·.¸/G¸1w¸N©¸#ø¸6¹YS¹Z­¹9ºQBºO”º?äº!$»#F»Aj»U¬»¼B¼)V¼_€¼à¼+ø¼<$½6a½>˜½)×½*¾$,¾$Q¾#v¾$š¾$¿¾#ä¾Q¿8Z¿W“¿5ë¿6!À:XÀB“À@ÖÀ"Á:Á8ZÁ)“Á'½Á4åÁ%Â'@Â&hÂ.Â,¾Âë Ã*&ÃQÃoÊÃ(¢Ã<ËÃ"Ä4+Ä'`Ä=ˆÄ)ÆÄ(ðÄ/Å,IÅ*vÅ,¡Å$ÎÅóÅ Æ*Æ?>Æ,~Æ'«ÆYÓÆ4-Ç,bÇ0Ç=ÀÇ0þÇ:/È1jÈ9œÈ1ÖÈ3É5<É1rÉ2¤É@×É1Ê?JÊJŠÊ6ÕÊ4 Ë4AË<vË>³Ë=òË30ÌBdÌ7§Ì6ßÌEÍA\ÍOžÍHîÍ 7ÎXÎ3mÎ1¡Î6ÓÎ3 ! Ï2>Ï0qÏ/¢Ï)ÒÏ#üÏ* Ð@KÐ%ŒÐ²Ð?ÄÐ#Ñ(Ñ'GÑ(oÑ5˜ÑÎÑãÑ!üÑ5ÒTÒ-gÒ&•Ò ¼ÒÝÒ'üÒ*$Ó%OÓ*uÓ$ ÓAÅÓCÔ6KÔ7‚Ô4ºÔ6ïÔ3&ÕIZÕ%¤Õ ÊÕ'ØÕ-Ö.ÖQNÖH ÖHéÖ#2×V×*i×(”×½×1Ý×)Ø-9Ø,gØ,”Ø<ÁØ5þØ&4Ù/[Ù=‹Ù&ÉÙ%ðÙ7Ú5NÚ,„Ú<±Ú$îÚ.Û0BÛWsÛËÛ9äÛOÜnÜŠÜ ©ÜÊÜ:æÜ?!ÝTaݶÝ7ÑÝ$ Þ-.ÞD\Þ:¡Þ!ÜÞOþÞ!Nß<pß<­ß&êß<àRNà;¡à>Ýà8áaUá9·á3ñáG%âXmâGÆâJãDYãYžãløãLeä;²äGîä?6åjvåKáåU-æ[ƒælßæDLçO‘çiáçOKè8›èaÔè6éq¸éW*ê8‚ꆻêHBë=‹ë?Éëi ìYsìuÍìvCí)ºí)äíî'î?>î^~î=Ýî@ïd\ïCÁïVð9\ð6–ð:Íð8ñ)Añ-kñ'™ñ%ÁñOçñ%7ò]ò4xò2­òàò ýò1óPó(póO™ó9éó$#ô?Hô8ˆô;Áô4ýô+2õ4^õ-“õÁõ3Øõ ö($ö=MöE‹öÑö'èö÷ '÷15÷&g÷6Ž÷8Å÷Sþ÷Rø+nø šø §ø±øÄøÞøóø4ù5=ù=sù<±ù7îù;&ú.búC‘úAÕúûûìü!ý3"ý1Výˆý(£ýÌý4ëý3 þ4Tþ1‰þ>»þ8úþ23ÿ-fÿ8”ÿÍÿ$âÿ4&<;c)Ÿ8É8%;)a‹F¯&ö7.U=„9Â6ü:33n;¢:Þ:<T%‘;·ó! ! #,8P ‰`“`ôU:j¥Oº ! 5#Y*v)¡Ë æ'ò*>EB„Ç;æ(" K Ce  © $¶ 7Û  ! #. ! #R ! 'v ! #ž ! M ! 7 9H 7‚ .º <é 6& >] ;œ LØ *% P 9h "¢ "Å )è .A"Y;|"¸PÛJ,8wz°]+0‰6ºLñM>FŒ.Ó#3&'ZM‚#Ð,ô)!&K/r4¢%×<ý3:(n&—%¾Jä/E77}=µ0ó5$‹Z@æ<'+d-¾Ó4è=/[ ‹¬4Ä)ù:#+^(Š6³êOgV5¾$ô1<KCˆ"Ì)ï0PJS›Lï$<8a\š÷$5)Q#{1Ÿ$Ñö#$66[’"±[Ô00 ;a : =Ø D!F[!N¢!@ñ!82"Pk"H¼"E#.K#"z#6#;Ô#.$.?$Kn$?º$ú$&%'8%`%"{%.ž%Í%í% &9(&4b&D—&4Ü&('!:'\'!|'ž'¾'MÎ'&(C(](;l(6¨(>ß(J)Ni)1¸)ê)%*&**!Q*s*(’* »*.Ü*D +"P+4s+,¨+"Õ+ø+G,3Z,&Ž,Bµ,Aø,):- d-<r-3¯-Gã-<+..h.:—.#Ò.ö.2/ E/f/)u/2Ÿ/Ò/-í/30'O0%w0705Õ0 1611P1/‚18²1ë1+ ! 2B62 y2 ‡2 •2%¶23Ü2v3v‡3cþ3b44,“4jÀ4;+5!g5'‰5$±5'Ö5>þ5>=6>|6E»677.7H7g7rz7‡í7/u8!¥89Ç899Y.9Kˆ9<Ô9”:O¦:1ö:-(;-V;-„;²;Ç;8Ø;@<*R<.}<D¬<2ñ<$===T=!o=,‘=E¾=>’>=¬>4ê>1?eQ?3·?3ë?3@gS@>»@|ú@UwA(ÍA öAB0B9KB…B0ŸB4ÐB0C/6C*fC%‘C$·C‚ÜC=_D"DãÀDG¤EDìES1FN…FDÔFWG)qG$›GbÀG#H18HjHD~H6ÃHúH* ! I5I SI&tI+›ISÇI)J2EJxJ>˜J>×J1K)HK?rK[²K@L^OL9®LèL)M70MhM(€M3©M0ÝM(N#7N,[N<ˆN>ÅN3OS8OAŒOÎOæO1P$8P5]PC“PC×PNQ<jQ!§Q"ÉQJìQ7R5SRA‰RUËR%!SGS5eS2›S=ÎS T/'T†WTŠÞTeiUÏU$éU0V_?V ŸV.ÀV ïVW30W&dW1‹W(½W,æW3X*GXKrXA¾X"Y3#Y)WY3Y4µY êY Z6%Z4\Z4‘Z8ÆZ(ÿZ'([3P[4„[;¹[õ[A\GW\NŸ\Nî\V=]^”]có]iW^hÁ^*_ª_*`ª`*a¬a,b®br.c¡cC¾c6d9d3VdŠd;©d5åde37e?ke3«e$ße3f&8f_f|f(šf$Ãf5èfHg2gg-šg-Èg.ögA%hYghÁh6áh/iHi)aiE‹iGÑi'j&Aj1hj$šj¿jÖj.êj0k"Jk2mk, k(Ík+ök,"l&Ol+vl+¢l%Îl"ôlm#7m&[m7‚m*ºm)åm)n$9n-^n+Œn%¸n(Þn#o'+o4So'ˆo&°o ×o+øo$p1Cp?up;µpñpq<#q$`q[…qKáq-r1Crurr¯r Êr9ÖrLsW]sHµs<þsO;tJ‹t[ÖtW2u>ŠuGÉu)v¹;v<õv.2w*aw(Œw8µw4îw)#x7Mx+…x+±x-Ýxt yL€yZÍy5(zO^z4®z=ãzA!{7c{5›{-Ñ{;ÿ{0;|Nl|a»|T}Gr}Bº}5ý}S3~8‡~BÀ~-21IdN®VýZT€y¯€D)ZnNÉC‚Y\‚?¶‚?ö‚<6ƒJsƒJ¾ƒ0 „2:„4m„_¢„D…AG…i‰…/ó…I#†om†I݆X'‡Y€‡TÚ‡K/ˆa{ˆ\݈Ž:‰:ɉ7ŠK<ŠŽˆŠ’‹ª‹gÅ‹-ŒBŒ]ŒsŒ1‰Œ/»Œ4댢 }ÃOAŽq‘Ž."2RU˜¨˜A Ú&ûM"‘/p‘; ‘Ü‘î‘<’VK’¢’?½’?ý’7=“;u“"±“<Ô“.”@”/_”3”(Ô<ì”)•II•“•@±•ò•/ –.<–!k–-–,»–2è–<—6X—"—²—Зå—)ú—8$˜2]˜.˜@¿˜™I™!i™@‹™7Ì™)š8.šgš9€š3ºšNîš-=›/k›"››%¾›ä›+œS/œ)ƒœ/­œÝœ/ûœ++1W-‰0·'è,ž=ž]ž|ž"‹ž9®ž+èž2Ÿ#GŸ-kŸ™Ÿ¹Ÿ1ÒŸ2 37 0k 1œ 2Π4¡-6¡*d¡)¡+¹¡,å¡0¢-C¢&q¢&˜¢$¿¢5䢣 /£+P£5|£²£&Ë£!ò£(¤/=¤Hm¤H¶¤/ÿ¤//¥_¥'|¥&¤¥5Ë¥2¦:4¦o¦X¦æ¦ÿ¦§!§1§$A§f§$„§©§(ç(ì§ ¨ "¨/¨A¨$Q¨v¨”¨®¨ƨâ¨ü¨D©*W© ‚©-Œ©º©$Í©0ò©#ª!?ª+aªGªAÕª5«)M«w«’«¨« «ã«"þ«I!¬Ik¬Bµ¬-ø¬;&­!b­8„­1½­0ï­7 ®&X®,®&¬®Ó®ó®8 ¯D¯`¯-{¯-©¯,ׯ=°=B°=€°=¾° ü°±)(±5R±)ˆ±2²±å±1ý±/²WG²-Ÿ²9Ͳ³%³2>³1q³£³C¾³´=!´o_´Ï´"è´# µ(/µ&Xµ-µ:­µ1èµ;¶HV¶Ÿ¶0»¶'춷4·P·/b·’·²·Ñ·ï·¸ $¸'E¸m¸Š¸¥¸/¶¸4æ¸)¹4E¹z¹—¹!¨¹"ʹ2í¹D º!eº+‡º,³ºàº4ÿº4»'H»#p»”»!²»Ô»ì»'¼?0¼p¼„¼ ¤¼żå¼y½+~½%ª½>н¾.(¾!W¾Hy¾!¾3ä¾1¿ J¿2k¿3ž¿#Ò¿ö¿GÀGWÀGŸÀçÀÁ:Á"VÁ&yÁ Á4·Á(ìÁÂ2Â0BÂBsÂ>¶Â9õÂ!/Ã5QÃ,‡Ã-´ÃAâÃ0$ÄUÄuĕijÄÆÄ?ÙÄÅ5ÅUÅ5qŧÅ5ÅÅ?ûÅ*;Æ>fÆa¥Æ.Ç6Ç*QÇ1|Ç3®ÇKâÇ:.ÈiÈ-È%­È9ÓÈ< ÉNJÉD™ÉKÞÉ?*Ê@jÊ4«ÊKàÊY,Ë"†Ë©ËDÀË*Ì;0ÌlÌ&‚Ì(©ÌÒÌ$ïÌ!Í6Í)TÍ(~ͧÍ7ÁÍ\ùÍ&VÎ6}Î,´ÎEáÎD'Ï/lÏœÏ%·Ï@ÝÏ9Ð2XÐ4‹Ð'ÀÐ5èÐ3Ñ#RÑ<vÑG³ÑVûÑVRÒW©ÒUÓRWÓLªÓ1÷Ó6)Ô6`Ô&—Ô;¾Ô4úÔW/Õ5‡Õ)½Õ3çÕ*Ö8FÖ.Ö1®Ö=àÖ)×EH×;Ž×8Ê×>Ø@BØFƒØCÊØCÙ1RÙ0„Ù1µÙ%çÙX Ú'fÚJŽÚMÙÚI'ÛEqÛ:·Û/òÛ9"Ü!\Ü*~Ü)©ÜNÓÜ0"Ý=SÝ3‘Ý@ÅÝ>Þ1EÞ0wÞ¨Þ%ÇÞ4íÞI"ß#lß9ßGÊß.à-Aà5oà8¥à=Þà2áROá0¢á<Óá7â7Hâ(€âa©âA ãPMã;žãJÚã2%ä2Xä'‹äQ³ä/å35å+iån•å-æ`2æ/“æ8ÃæZüæQWç+©ç"Õç*øç7#è-[è.‰è ¸è&Ùè"é6#éZé@té<µé!òéCê9Xê3’êÆêæê,ë42ëHgëO°ë;ì,<ì;iì%¥ì,Ëìhøìxaí7Úí^îGqîE¹î7ÿîN7ïO†ï(ÖïDÿïBDðV‡ðYÞðG8ñ;€ñ(¼ñBåñR(ò+{ò2§ò7ÚòEóBXó.›óQÊó,ô/Iô'yô3¡ôGÕôEõ%cõ ‰õ:ªõ4åõ3öCNöE’öAØöO÷2j÷B÷4à÷iø$ø#¤ø5Èøþø%ùEBùOˆùVØù./ú3^úB’ú%Õú0ûú3,û1`û’û=²û)ðû2üMü9jü3¤ü0ØüP ýcZý;¾ý>úý39þkmþ3Ùþ ÿ:-ÿ7hÿR ÿ(óÿ0+M/y>©0èLSfJº@-F4t9©@ã%$KJ>–KÕN!>pg¯(V@%—*½èBðD3Dx:½TøTM0¢:Ó *. #Y !} IŸ @é g* ! $’ ! B· ! 'ú ! ." Q "q !” !¶ "Ø "û 3 "R 4u 4ª ;ß 0 L l i‹ )õ )I iw ˆ ! ’ +§:Ó05?2u/¨aØ;:+v9¢eÜ=B@€Á>Ô-"A:dŸ0¡>Òb7t$¬6Ñ)L2<7¼Eô,:Wg?¿ÿ33RB†?ÉC (M&v+³%ßiMo1½1ïE!%g#%±8×83I1}B¯*ò;;=w5µ9ë*%\P8­1æ5/N2~±2µ5èQ&pJ—'â. ! 498n/§%×$ý%" #H )l )– -À "î !)&!-P!~!-’!(À!*é!".,"A["0"/Î"cþ"9b#<œ#4Ù#3$>B$3$7µ$[í$ I% U%.c%$’%&·%IÞ%I(&r&J’&#Ý&>'+@')l'%–'/¼'<ì'.)(%X(~(/(?Í(8 ))F)p)1‰);»)<÷)94*<n*8«*;ä*5 +8V+++«++×++,+/,$[,"€,*£,Î,;ç,#-:C-5~-‹´-2@.Es.<¹.2ö.()/0R/0ƒ/*´/0ß/(0*90,d0'‘0 ¹0+Ç0&ó091T11e1&—1/¾1@î1./2$^25ƒ24¹24î2;#3<_3 œ3©3Ä3Þ3!ø3%4%@4!f4'ˆ4°4&Ê4ñ4'ø4( 5<I50†5%·52Ý5>6'O6w6N“6.â6 ! 7.7:K7)†7)°75Ú7E8AV84˜84Í8 9#9,>9$k9"9.³9%â9%:$.:S:4j:Ÿ:2µ:è:T;L\;[©;W<D]<P¢<Có<07=&h== ¥=9³=#í=)>;>.Q>(€>>©>"è>2 ?3>?Qr?,Ä?)ñ?0@HL@2•@È@'æ@*A 9AEAbA A% A%ÆAìABB%B7B$JB oBB%¡B/ÇB%÷B,C,JC.wC,¦C,ÓC,D,-D*ZD&…D/¬DÜDñD úD#E!*E"LEoEŽE­E ÇE7ÔE FF0F 9F'ZF‚F+¡F'ÍF"õF#G)ºM!ùMN=;N yN-šNÈNãNHúN)CO)mO/—O@ÇO-P.6P ePNrP.ÁP(ðP1Q6KQ3‚Q3¶Q5êQ= RJ^R*©R"ÔR0÷R(SCS[S)xS"¢S*ÅS*ðSPTAlT+®T4ÚT6U2FU"yUœU9µUïUV7V!VV"xV›V>³V>òVD1W7vW'®W.ÖWMXHSXœX.»X êX' Y-3Y=aY3ŸYÓYîY; Z#HZ6lZ:£Z5ÞZ[3[F[Y[)r[#œ[(À['é[&\"8\3[\\£\¹\$Ó\ø\],]>]X]r]*‹] ¶] Ã]Ð]î]^^9&^.`^3^/Ã^0ó^3$_;X_F”_Û_ù_#`=`+[`.‡`¶`!Ö`,ø`%a1?a-qa'Ÿa-Ça+õa#!b Eb#fb-Šb¸bVÕb*,c&Wc&~c)¥c/Ïc4ÿc+4d7`d9˜d8Òd e%*e5Pe †eT§e7üe64f7kf£f1¼f6îf-%gTSg9¨g$âg8h+@h<lh©hÈhÙhëhüh"i'©|6è|>};^}š}0¶}.ç}3~9J~8„~ ½~Þ~Bý~L@&:´$ï€1,€<^€;›€.×€51<1n. .Ï5þ54‚>j‚C©‚.í‚/ƒLƒ/eƒ+•ƒ-Áƒ&".„'Q„5y„(¯„Ø„Nî„X=…8–…:Ï…+ ! †46†9k†9¥†+߆, ‡ 8‡/Y‡$‰‡®‡͇,臈((ˆ2Qˆ4„ˆ2¹ˆ(숉"5‰&X‰)‰.©‰؉.ò‰a!Š9ƒŠ,½Š6êŠ2!‹UT‹(ª‹GÓ‹>ŒAZŒ$œŒ$ÁŒ,æŒ(B<LÌì. Ž'8ŽH`Ž4©ŽPÞŽ&/.V/…*µ9à+.F<u)²DÜS!‘Tu‘KÊ‘’C4’'x’E ’@æ’<'“Dd“@©“Lê“57”Bm”(°”;Ù”#•F9•€•8›•<Ô•J–,\–@‰–Ê–â–+—@.—Lo—P¼—; ˜7I˜c˜ å˜,™ 3™*T™-™%­™.Ó™š"š6;š&rš1™šËš#éš ›+.›Z›)z›)¤›Λꛜ%œ#:œ-^œ7Œœ)Äœ%îœ$49*n1™1Ë0ý.ž6Dž"{žžžºžמ9îž0(Ÿ'YŸ-Ÿ¯Ÿ$ÌŸ,ñŸB <a 5ž Ô ,å +¡3>¡0r¡/£¡Ó¡é¡ø¡þ¡#¢)*¢%T¢3z¢J®¢'ù¢!£55£&k£6’£'É£+ñ£/¤'M¤,u¤1¢¤GÔ¤>¥![¥/}¥(­¥)Ö¥#¦#$¦aH¦"ª¦ ͦî¦4§>C§5‚§/¸§+è§+¨(@¨$i¨9Ž¨.ȨC÷¨F;©.‚©*±©FÜ©.#ª Rª6`ªC—ªÛª0ûª,«+F«#r«!–«-¸«$æ«$ ¬#0¬T¬Rh¬ »¬ܬ,ú¬?'­/g­0—­2È­/û­5+®Va®<¸®Sõ®UI¯cŸ¯E°NI°˜°L³°-±+.±7Z±:’±1ͱ8ÿ±&8²*_²1Š²3¼²'ð²%³$>³;c³.Ÿ³Fγ´+´KE´1‘´"ô æ´CµBKµŽµ§µ*Áµ+ìµ*¶1C¶'u¶F¶=ä¶#"·#F·9j·¤·÷ß·ù·¸&)¸P¸4b¸—¸6·¸#-#¹,Q¹%~¹¤¹$¾¹ã¹&º))ºSºgº~º •º £º%±º0׺G»P»o»»*¤»Ï»&æ»? ¼(M¼(v¼Ÿ¼ ¿¼7à¼-½F½Z½z½½$©½!νð½R¾.c¾P’¾*ã¾/¿3>¿!r¿K”¿à¿ÿ¿4ÀOÀ+cÀ+À»ÀÕÀñÀÁ1Á NÁ oÁ4Á/ÅÁ#õÁÂ:+ÂEfÂ<¬Â éÂ! ! Ã,ÃIÃ_Ã*xãÃ5ÂÃJøÃTCÄS˜Ä8ìÄ%Å54ÅHjųÅ/ÎÅ3þÅ+2ÆA^Æ Æ8·Æ7ðÆ+(Ç2TÇ3‡Ç3»Ç>ïÇ$.È,SÈ4€È&µÈ6ÜÈ6ÉJÉPÉ"eÉ!ˆÉ!ªÉ"ÌÉïÉ ! Ê$&Ê%KÊqÊÊ$ªÊÏÊáÊùÊ*Ë7,Ë'dË'ŒË$´Ë$ÙË)þË%(Ì%NÌ$tÌ%™Ì¿ÌÛÌ÷Ì Í31Í3eÍ)™ÍÃÍãÍòÍÎÎU.΄ΓΫÎÅÎÝÎõÎÏ#Ï4ÏCÏ]Ï8vϯϿÏ%ÎÏ&ôÏ%Ð+AÐmÐ9…пÐ#ÞÐÑÑ: Ñ[ÑjÑ|їѫѽÑÌÑÛÑ!òÑ"Ò7ÒHÒ[Ò1nÒ Ò¶ÒÊÒÞÒõÒÓ&Ó<ÓPÓkÓÓ”Ó¥Ó¸ÓËÓÚÓòÓÔ Ô5/Ô(eÔJŽÔ+ÙÔÕ!Õ=ÕSÕdÕxÕ‹Õ4ŸÕÔÕ!éÕ Ö*+ÖVÖ0jÖ›Ö¸ÖÍÖáÖóÖ ! ××;×X×u׊×*¦×0Ñ×ØØ7Ø$RØ%wØصØÔØêØ&üØ#Ù4ÙPÙAfÙ@¨ÙéÙ!Ú(Ú;ÚSÚkÚ†Ú¡Ú¶ÚÔÚëÚÛÛ.ÛKFÛF’ÛPÙÛL*ÜwÜ•Ü<´Ü9ñÜU+Ý0Ý+²Ý/ÞÝ<Þ9KÞ,…Þ2²Þ.åÞDß+Yß+…ß<±ßuîß^dà_Ãà6#áZá+záC¦á0êáDâ.`âAâ=ÑâAã(QãIzã&Äã)ëã>äTäBmä°ä Ðä'Üä$å)å*Dåoåå.Ÿå,Îå6ûå2æOæiæ‡æ/§æ0×æ#ç8,çceç?Éç è0#èTè4pè0¥è2Öè2 é3<é pé ~é+Œé)¸é âéê!ê-5êcê }ê‰ê¦êÂêàêÿêë03ë4dë™ë ¨ëÉë åëì($ì:Mì4ˆì4½ì"òì/í&Eí/líœí*»í&æí î#'î%Kî7qî5©î=ßî&ï)Dï nïF{ï&ÂïBéï,ðCðaðChð3¬ð,àðC ñ!Qñ3sñ7§ñ6ßñ7ò+Nò(zò%£ò'Éòñò ó/ó5JóC€ó6Äó8ûó*4ô0_ô;ô2Ìô2ÿô$2õ$Wõ/|õ!¬õ Îõ)ïõ)ö)Cö-mö›öyºöœ4÷0Ñ÷8ø?;ø4{ø*°ø:ÛøCùZùyù˜ù ¸ù,Ùù,ú!3úFUú^œúFûúMBû[ûfìûWSüA«ü9íüT'ýJ|ý+Çý#óý#þ+;þgþ>ƒþ;Âþ-þþ,ÿ!Hÿ-jÿ'˜ÿ9Àÿ%úÿ) (J/s2£$Ö-û0)RZ=­$ë5F]+{'§8Ï&*Bm4‹,À/í<Z"t!—#¹.Ý1 > ! Q-\(Š-³$á-)4^x:”-Ï.ý,0B/s-£4Ñ6*=6h#Ÿ#Ã1ç7 5Q ‡ 6› JÒ @ ! 6^ !  • ! )¶ ! $à ! ' /- ,] Š 6¡ ;Ø 9 3N C‚ SÆ , "G #j $Ž H³ Lü .I>x·Èä8:QOŒHÜE%$kSYäZ>c™DýbB6¥Ü ë) <6s9ƒA½ÿ) ="JEmF³Bú!=:_1š@Ì: 1H(z£#Ã(ç%/.U'„¬;Ç<?@)€&ª,Ñ1þJ00{,¬.Ù=HF%'µÝ-í'Cc0ƒ´+Î#ú!-@$n$“#¸?Ü3,P}6“Ê.æ15GU}[Ó\/eŒFòd9 až g!hh!qÑ!RC"p–" #>(#-g#-•#9Ã#Iý#EG$8$8Æ$)ÿ$;)%Ge%F­%+ô% &/>&-n&0œ&2Í&#'$'+A'*m'*˜'*Ã'9î'<((6e(!œ(1¾(4ð(1%):W)’)a²)E*>Z*/™*"É*-ì*,+@G+3ˆ+¼+#Ø+,ü+#),1M,%,/¥,3Õ,3 -/=-5m-"£-&Æ-í-...DD.$‰.)®.&Ø.)ÿ.0)/1Z/Œ/;§/0ã/005E03{0*¯08Ú01021'c1I‹12Õ182A2&Y2*€2'«2Ó2í2" ! 3 -35N3D„3PÉ3:45U4‹448´4)í405-H5*v5*¡5Ì5ß5ô566,6@6R6f6x6Š6œ6­6¿6Ó6é6ý67 727C7W7i7}77£7µ7Ç7Û7í7ÿ78#878K8_8q8ƒ8—8©8½8Ï8ã8ô899,9>9P9b9v9ˆ9œ9®9Â9Ø9î9::$:/6:f:(v:Ÿ:¹:Ì:â:#ý:!;A;V;i;ƒ;/¡;6Ñ;!<*<I<'Y<'<'©<"Ñ<)ô<=16=3h=0œ=4Í=/>)2>G\>1¤>*Ö>!?!#?%E?k?‹? ¤?&Å?<ì?!)@(K@/t@&¤@*Ë@+ö@)"A&LA3sA§A,ÃA7ðA(BEB/VB)†B.°B0ßBC:0CkC#‰C"­C!ÐC&òC!D,;D hD"‰D'¬DÔD)òD!E5>EtE:‡E(ÂE&ëE)F-G lG&G´GÑGNñG@H$]HT‚HK×H#I)7I+aI I.›IÊI$èI# J1J+OJ{J ›J.¨J#×J'ûJ'#K(KK*tK+ŸK"ËK1îK! L(BL!kLLLµLÏL êL M ,M MM nM M °M ÑM òM N!4N VNwN%•N#»N#ßN"O&OFObOyO)—O)ÁO)ëOP5PQPmP‰P P¼PÓPóPQ+QGQcQQ0›Q?ÌQ[ R#hR/ŒR$¼R%áR%S3-S#aS0…S¶S ÍS+îST30TdT"T¢T »T1ÜTU%+U%QU0wU.¨U2×U$ ! V/VIV)gV‘VªV)ÉV2óV#&W%JWpW=†W$ÄW)éWX#)X-MX&{X!¢X#ÄX#èX Y< Y]Y8{Y$´Y ÙY*úY2%Z7XZ/Z"ÀZ'ãZ [9*[d[,~[)«[-Õ[&\'*\R\r\4’\,Ç\%ô\]0].H]w]$“].¸]ç]+ú]7&^^^q^‡^>£^Dâ^2'_,Z_.‡_[¶_m`(€`!©`'Ë`'ó`$a7@a#xaœa)¼a-æa(b(=b(fb(b&¸b3ßb.c*BcAmc9¯cécLýc/Jdzd/™d.Éd(ød%!eGebe#we›e!»e+Ýe/ f49f:nf ©f7¶f1îf. g(Og1xg.ªgÙg!ëgE h)Sh<}hºh9Úhi"3iViii{i•i,´i*ái* j#7j![j!}j!Ÿj!Áj$ãj"k#+k#Ok#sk"—kºkÚk-øk)&l Plql‘l"±lÔl&ôl'm+Cm(om˜m%¸m"Þm n"nBn7bnfšnVo5XoŽo#•o¹oÙoùo,p"=p`pAtp(¶p$ßpq'qCGq3‹q"¿qâqýqLr,hrH•rÞr ír"s1s!Osqs3ŽsHÂs t tx6Zx!‘x0³x1äx/y2Fy2yy8¬y åy@z#Gzkz&‹z²z$Íz$òz-{&E{ l{-{»{Ø{*ö{!!|*C|%n|”|®|Å|ä|+}.}!N}p}%Œ}²}$Í}ò}$ ~&2~$Y~/~~7®~-æ~*$?.d6“'Ê@ò%3€Y€w€;–€!Ò€ô€ %8!^€ -º/è5‚/N‚"~‚G¡‚3é‚'ƒ$Eƒjƒ‡ƒ8¦ƒ6߃@„2W„MŠ„?Ø„?…1X…;Š…5Æ…5ü…%2†6X†2†+†1î†I ‡j‡?‰‡6ɇAˆ.Bˆ3qˆ,¥ˆ)Òˆ(üˆ0%‰:V‰.‘‰&À‰@ç‰$(ŠMŠ7gŠ7ŸŠ׊$ìŠ,‹)>‹4h‹"‹=À‹.þ‹*-Œ*XŒ,ƒŒ,°ŒÝŒôŒ!;)]%‡%­Ó&çŽ,Ž(?ŽhŽ|Ž—Ž/²ŽâŽ"ÿŽ!"DZi|4ŒÁ!Ø ú(8D9}&·Þ ï0‘1A‘Es‘7¹‘Kñ‘!=’"_’‚’¡’b¾’%!“G“(c“+Œ“+¸“&ä“+ ”7”)O”0y”%ª”Д î”'•.7•2f•!™•,»•jè•2S–'†–@®–ï– —2'— Z—5{—<±—+î—.˜2I˜3|˜6°˜Mç˜D5™=z™%¸™5Þ™š/-š#]šš6–š#Íšñš ›'›G›$É› î›/œ'?œ'gœ8œ-Èœ"öœ$#>(b)‹-µ'ãG žSž-lžšž®ž'Ìž ôžŸ Ÿ$AŸ#fŸ!ŠŸ.¬ŸÛŸ5õŸ+ G -[ ‰ Ÿ · /Æ Cö 5:¡"p¡/“¡+á2ï¡;"¢3^¢"’¢&µ¢&Ü¢#£#'£"K£"n£‘£±£'Ï£(÷£ ¤27¤j¤&‡¤#®¤"Ò¤-õ¤,#¥P¥/k¥(›¥Ä¥"ä¥C¦K¦$i¦5Ž¦4Ħ'ù¦!!§EC§+‰§Bµ§,ø§;%¨a¨3{¨4¯¨ä¨/©.0©+_©‹©*ª©-Õ©0ª'4ª/\ª4Œª*Áª,ìª'«(A«&j«‘«(¡«DÊ«.¬1>¬(p¬R™¬9ì¬4&­.[­HŠ­!Ó­(õ­E®Ed®$ª®)Ï®1ù®(+¯&T¯:{¯¶¯:ƯK°MM°6›°+Ò°þ°±*6±a±$v±›±º±!Ù±û±/²G²L²4S² ˆ²•²5«²,á²<³5K³&³1¨³LÚ³H'´p´‡´\¤´3µ75µ*mµ.˜µ,ǵ"ôµ4¶1L¶4~¶5³¶(鶷B0·:s·&®·>Õ·*¸$?¸(d¸$¸$²¸(׸<¹A=¹5¹)µ¹2ß¹"º5ºHº![º}ºœºA·º@ùº::»9u»9¯»Hé».2¼&a¼ˆ¼%¤¼6ʼ3½*5½/`½!½%²½Dؽ"¾@¾R¾d¾/u¾/¥¾!Õ¾÷¾=¿M¿Hg¿!°¿>Ò¿2À DÀCeÀ3©À<ÝÀÁ):Á+dÁ%Á%¶Á+ÜÁÂÂ8ÂXÂ%wÂ(Â"ÆÂ7éÂQ!à sÔÃ$³Ã-ØÃ6Ä5=ÄsÄ(“Ä'¼Ä)äÄÅ$+Å+PÅ%|Å"¢Å-ÅÅóÅ%Æ!5Æ!WÆ<yÆ>¶Æ,õÆ"Ç?Ç@^Ç'ŸÇ!ÇÇ éÇ ! È%È8AÈ1zÈ5¬È*âÈ É7$É1\ÉLŽÉLÛÉ-(Ê*VÊ"ÊJ¤ÊBïÊ&2Ë%YË.Ë4®Ë ãË.ÌA3ÌOuÌBÅÌKÍJTÍKŸÍKëÍJ7ÎK‚Î5ÎÎ7ÏJ<Ï9‡Ï9ÁÏEûÏQAÐD“ÐDØÐ@Ñ=^Ñ=œÑ ÚÑ äÑðÑ;Ò:@ÒH{Ò3ÄÒ%øÒ&Ó;EÓ:Ó¼Ó<ÍÓ ! Ô-Ô.KÔ*zÔ¥Ô(ÃÔ8ìÔ<%Õ2bÕ6•ÕBÌÕ.Ö(>Ö)gÖ(‘Ö1ºÖ<ìÖ/)×/Y×<‰×ZÆ×7!Ø)YØBƒØÆØ;ÛØ(Ù-@Ù4nÙ£Ù'ÁÙ'éÙ ÚÚ6Ú.SÚJ‚ÚÍÚ,êÚ1Û)IÛ"sÛ–Û«Û ÅÛ1æÛ1Ü JÜkÜ%ˆÜ®ÜÊÜãÜ$Ý.%Ý'TÝ|Ý•Ý­ÝÂÝÜÝ6ùÝ 0Þ QÞ7_Þ.—Þ%ÆÞ.ìÞ1ß@Mß@ŽßÏßïß; à$Hàmà8ˆàÁà2×à> ! áNIáM˜á3æáâ,â%Lâ+râ$žâ6Ãâ<úâ77ã5oãA¥ã7çãTäTtä>ÉäFå%Oå-uå+£å6Ïå-æ.4æ-cæ,‘æ*¾æ éæ ! ç1+ç]çpç,çºçÚçúç#è;èJQè%œè&Âè&éè&é 7éDXéé»éLÓéA êbê€êê²êÇê)Üêë%ë0Bë8së¬ë,Ìë,ùëF&ì$mì’ì °ìÑì'êì'í2:í$mí;’í>Îí> î9Lî-†î3´îèî@ï4Gï)|ï¦ï½ïÓï(êïð<)ðDfð=«ð]éð#GñCkñ,¯ñ<ÜñIò.cò ’ò2³ò'æò4ó$Có-hó –ó·óËó4ßó)ô6>ô+uô%¡ô1Çô=ùô07õ0hõ™õ¸õ×õ$÷õ!ö7>ö!vö1˜ö0Êö)ûö1%÷;W÷9“÷$Í÷#ò÷ øM7ø-…øI³øýø! ù#/ùSù"rù•ù*³ù$Þù$ú6(ú(_úJˆú&Óú5úú50û:fû=¡û/ßû*ü;:ü%vü'œü-Äü<òüV/ý6†ýR½ýˆþ8™þBÒþ@ÿ9Vÿ&ÿ4·ÿ$ìÿ3'Em8‹4Ä%ù+K h‰+©"Õø !  ! " -N$k24à ø)#,P%i+»8Ù&9W'vž4¸í$(-5V Œ*­!Ø"ú"N@ª!Åç/Nc&z¡ ¹Ú"öSmŒ«Êé?ú>: 6y *° !Û ý # ! *0 ! )[ ! ,… ! 4² ! )ç ! = (O =x ,¶ Aã 5% 4[ ) )º -ä @ "S *v +¡ Í -ã ')9CcU§Fý0D&u5œ'Ò ú5Qj‰$¨Íí4 ! J?7ŠÂ3Ú-(<eV~)Õÿ079h!¢'Ä'ì93N;‚;¾6ú/12a2”IÇ3!E3g/›3Ë3ÿ3)S)}+§/Ó2$6-[@‰:Ê$!*#L p‘¨Á'Öþ(Z<-—/Å+õ"!DXn8Š2Ã6ö8-$f.‹9º(ô(4F9{7µ=í3+/_4.Ä.ó4".W.†,µ9â9 9V : 9Ë :!9@!9z!W´!W ".d"“"$¨"!Í"/ï"&#)F#p#Œ#«#.¾# í#0$#?$=c$+¡$$Í$ò$!% 4%-U%ƒ%!Ÿ%+Á%-í%$&.@&(o&.˜&Ç&1×&. '*8'/c'B“'3Ö'B ! ('M("u(+˜(3Ä(@ø(D9)%~)¤)+Ä)ð)*4/*-d*(’*<»*ø*#+:+(W+€+,†7,6¾,Mõ,:C-6~-6µ-/ì-%.5B.&x.7Ÿ.G×./@7/2x/$«/Ð/ ä/:03@03t0@¨0@é0;*1f1z11£1¹1Í1à1õ1 2222G2]2q2‡2¡2µ2È2Ù2ó23343G3Z39r3M¬3Mú3@H4C‰4(Í43ö4%*5=P5(Ž57·5Zï5YJ6N¤62ó6-&7FT74›7+Ð7+ü7,(8+U8+8,­8,Ú8,9449Yi9HÃ9W :Xd:-½:5ë:A!;vc;7Ú;l<5<;µ<Uñ<5G=Q}=ˆÏ=>X>4—>>Ì>1 ?2=?p?.?¿?<Ñ?2@ A@b@2@(²@EÛ@E!A.gA3–AcÊA.BXNBB§BHêB:3CFnC1µC'çCD%(DND*lD"—D!ºD)ÜD E'E6FE }ERžE/ñE$!FFF [F|FF2­F/àF/G(@GiG&ƒGªG#ÉG"íGH*+H!VH xH,™H*ÆHñH3IEIcIxI)•I7¿I!÷I#J0=J&nJ#•J/¹JAéJ%+K8QKMŠK6ØK8L.HL3wL-«LCÙL,M>JM&‰MV°M'ND/NFtNQ»NC O=QO8O;ÈOOP-TP‚P0P/ÎPþP/QDDQ1‰Q,»Q0èQR85R'nR&–R+½R%éR#SH3S5|S(²S$ÛS/T60T‚gTCêTC.U-rU- U5ÎU.V%3VYVmV€V0—V#ÈV&ìV W"4W#WW${W' W.ÈW'÷W(X(HX!qX*“X8¾X1÷X1)Y3[Y1YÁY/áYZF(Z/oZ(ŸZ)ÈZ8òZ/+[6[[+’[0¾[ ï[A\ER\#˜\ ¼\3Ý\1](C]4l]¡]/»].ë]Q^l^‹^4£^4Ø^3 _,A_)n_7˜_6Ð_!`&)`2P`+ƒ`.¯`4Þ`a1a/Ga?wa+·aBãa&bFFb&b0´b#åb! c+cGcdc|c9˜c%Òc"øcd5d'Jd$rd>—d)Öd!e"e4e"Ge4jeŸe¶eÒeòe) ! f&4f"[fH~f3Çf&ûfL"g8og ¨gÉgÜgñg& h"3h)Vh*€h«h6Åh<üh9iSiji1€i²i.Ïiþi/j0Djuj “j" j*Ãj,îjk-kGk`k*sk4žkÓk&ñk%l>l]lxl$‘l¶lÐlêl mm50mfm)|mC¦m!êm6 n<Cn.€n'¯n3×n o)o5AowoŒo#¡o.Åo.ôo$#p6Hpp%p=Ãp&q(qFqcq+‚q®qÌq!ëq! r/r+CrBor=²r2ðr=#s2asB”s7×st-)tWt"st9–t4Ðt.u)4u^u"yuœu±udÍu>2vqv†vPv9îv#(wLw&ewvŒw)x@-x+nx.šx;Éx2y>8y;wyI³yýy&z1;z0mz'žz?Æz{-"{"P{s{)‰{³{-Ð{Gþ{/F|.v|)¥|)Ï|4ù|&.}+U}0}D²}÷}(~)/~1Y~4‹~À~Ó~ë~++,X r)“/½í- €=:€/x€;¨€ä€/ÿ€ /)P+z*¦5Ñ0‚08‚1i‚$›‚!À‚,â‚<ƒULƒ!¢ƒă0ãƒ#„8„TV„Z«„[…db…EÇ…c †Bq†!´†Ö†#ô†‡=8‡Cv‡Dº‡%ÿ‡W%ˆ}ˆ,ˆ#ʈ%îˆ2‰AG‰$‰‰#®‰-Ò‰+Š@,ŠmŠ5‹Š6ÁŠ2øŠH+‹ t‹•‹­‹Ç‹Ý‹7õ‹B-Œ,pŒ'Œ6ÅŒ+üŒ,(/U0…5¶ìŽŽ!,Ž=NŽ!ŒŽ5®Ž$äŽ. 8#Nr'‘$¹QÞ 0AQ"“(¶ßAñ 3‘ ?‘AI‘‹‘'«‘&Ó‘%ú‘& ’4G’.|’«’>É’5“>“]“0{“+¬“Ø“ ! Ý“*è“*”$>”*c”8Ž”"ǔꔕ+#•5O•6…•2¼•2ï•<"–2_–5’–)È–ò– —%'—"M— p— ‘—-²—"à—!˜%%˜%K˜'q˜™˜©˜ ǘè˜ù˜™4™L™i™}™ ‘™ ™Ò§™z›:|›>·›ö›0œ×?œ/<GY„ Þ ë÷N ! žYYžf³ž<ŸWWŸ=¯ŸHíŸI6 7€ W¸ ¡(¡*F¡-q¡(Ÿ¡#È¡*ì¡3¢,K¢Žx¢£ £&+£R£Xn£3Ç£cû£A_¤K¡¤Jí¤68¥@o¥]°¥>¦„M¦]Ò¦O0§E€§[ƧP"¨Cs¨D·¨Nü¨LK©P˜©?é©=)ªCgªO«ª[ûª?W«B—«ŠÚ«Ce¬J©¬Rô¬?G­F‡­NέH®Yf®‰À®JJ¯?•¯ŠÕ¯=`°Dž°bã°XF±OŸ±Lï±K<²Kˆ²[Ô²U0³ª†³R1´Ÿ„´c$µ[ˆµNäµ^3¶M’¶=à¶>·>]·;œ·cØ·W<¸O”¸]ä¸NB¹K‘¹SݹM1ºHºTÈ»¼V<¼ ! “¼)ž¼?ȼ3½3<½Ap½²½'ɽ.ñ½M ¾0n¾rŸ¾2¿ME¿Ž“¿D"À4gÀBœÀSßÀ%3ÁYÁqÁ%‡Á3­Á3áÁ6Â6LÂ$ƒÂ$¨Â"Í ðÂþÂ'Ã<ÃBVÃ(™ÃIÂÃU Ä"bÄC…ÄUÉÄÅ1=ÅQoÅÁÅÖÅEëÅ„1ÆX¶Æ+Çe;Ç3¡ÇRÕÇ?(ÈZhÈ„ÃÈHÉ:eÉP ÉñÉEÊ>UÊg”ÊüÊËG$ËklËkØËDÌrÄÌ]7Í_•ÍXõÍ`NÎW¯ÎEÏXMÏ]¦ÏjÐ$oÐH”ÐÝÐ-íÐ-Ñ7IÑ<Ñ0¾ÑFïÑ+6Ò6bÒ0™Ò4ÊÒ0ÿÒ.0Ó?_ÓTŸÓ9ôÓ:.ÔQiÔ(»ÔäÔIøÔ<BÕOÕVÏÕa&ÖSˆÖÜÖOûÖ5K×*×1¬×FÞ×6%Ø'\Ø/„ØO´ØEÙ:JÙD…ÙKÊÙKÚJbÚG­ÚEõÚV;ÛH’ÛIÛÛ%Ü6EÜ9|ÜL¶Ü!Ý"%ÝHÝ2fÝD™ÝÞÝ'÷ÝÞ,?ÞlÞŠÞ,£Þ0ÐÞ7ßn9ßw¨ßU à[vàWÒà/*á<Zá`—á|øá.uâC¤âJèâ03ã6dãD›ãHàãD)äfnäCÕä+å+Eå1qåm£å(æ-:æhæAæÁæEÛæ0!çRçnç/ŠçBºçýç è[5è=‘èNÏèNé3mé7¡éAÙé6ê7Rê8Šê:Ãê4þê33ëBgë4ªë:ßë4ì.Oì/~ì6®ì:åìC í6dí'›í&ÃíOêíR:î!îH¯îVøî(Oï,xï<¥ï+âïPð>_ð9žð3ØðD ñ3Qñ+…ñ ±ñ ÒñóñH òDVò?›òJÛòI&óEpóP¶ó2ô2:ôQmôC¿ôEõkIõNµõ>ö9CöF}ökÄöp0÷j¡÷n ø;{ø7·øiïø„YùCÞùB"ú,eú’úD°ú:õúJ0û7{û9³û$íû(ü%;ü]aü>¿üaþü(`ý#‰ý.­ý!Üý6þý5þ)Rþ5|þC²þ<öþ'3ÿ0[ÿ!Œÿ-®ÿ-Üÿ: ! iE *¯ DÚ 6 BV J™ Gä =, Cj D® 7ó <+ h )† :° -ë ( eB a¨ F !  :Q *Œ 1· Zé AD +† †² *9 "d -‡ Dµ Gú 8B ({ E¤ 9ê *$ BO 9’ &Ì Eó H9 ! D‚ ! =Ç ! $ 8* 0c 4” DÉ H :W 8’ PË 0 4M C‚ =Æ = =B B€ 3à !÷ 4 N $l L‘ $Þ + ~/ ® ¿ Ñ 3ñ B% $h  @® ï , 1 FJ >‘ ?Ð % 86 "o ’ ­ 'Ë )ó - OK › k¸ 6$ C[ Ÿ T· !  3. Db D§ ]ì LJ %— $½ #â 0 7 (X  6œ (Ó oü /l )œ 0Æ #÷ ) $E 1j /œ )Ì .ö (% -N %| (¢ -Ë 'ù ,! 3N ‚ ,— 'Ä ì + =1 o Œ #§ "Ë î "  %. $T =y · 1× +  #5 Y u (‘ )º :ä  7 X hj Ó 7ê 6"! *Y! „! —! ´! 6Î! N" /T" =„" $Â" 8ç" , # 3M# U# 5×# 3 $ A$ #Y$ #}$ '¡$ )É$ ó$ % &% +C% o% B‡% &Ê% ñ% & #+& &O& 'v& 0ž& ;Ï&  ' !' "B' e' 1ö' 4(( 1]( G( U×( 6-) 'd) AŒ) /Î) Rþ) ;Q* 8* 6Æ* 7ý* D5+ >z+ B¹+ (ü+ $%, J, #a, …, >¥, 7ä, - 88- $q- 5–- 6Ì- $. 1(. /Z. (Š. %³. 8Ù. // 8B/ @{/ /¼/ ;ì/ 8(0 6a0 <˜0 6Õ0 < 1 &I1 Cp1 9´1 7î1 5&2 .\2 ‹2 ©2 <Á2 4þ2 033 d3 b{3 Þ3 2ü3 (/4 -X4 8†4 ¿4 Ï4 Fã4 +*5 =V5 "”5 ·5 Ï5 <á5 _6 W~6 QÖ6 T(7 R}7 gÐ7 88 Zº8 R9 Uh9 7¾9 6ö9 *-: 3X: )Œ: ¶: Ð: Mæ: -4; *b; /; =½; "û; -< L< 'k< 2“< 4Æ< 6û< -2= B`= 5£= AÙ= C> C_> #£> 9Ç> '? )? D? "c? †? + ? Ì? 'ç? /@ ?@ [@ !{@ "@ À@ Ø@ %ô@ !A 6“Z ,ÒZ LÿZ TL[ ¡[ 3º[ î[ õ[ 7ü[ ! 4\ =?\ }\ %˜\ /¾\ /î\ "] A] !a] +ƒ] `¯] *^ O;^ =‹^ (É^ Kò^ >_ X_ )q_ 0›_ )Ì_ /ö_ 0&` "W` Fz` )Á` ë` +ø` $a Da "aa "„a §a #¶a @Úa 0b Lb 'jb 3’b 'Æb 'îb ]c tc vc ‚c Žc +šc 8Æc $ÿc R$d %wd d ©d µd Ád Íd 2Ùd # e 0e @e Le \e he te T€e TÕe W*f ‚f ZŽf #éf g Wg Wqg Ég .Íg <üg 39h mh ! ‹h •–h 7,i sdi $Øi &ýi A$j /fj –j ´j IÕj k |,k ©k 2¯k 5âk /l \Hl A¥l Gçl ž/m yÎm 4Hn 7}n :µn 7ðn 9(o bo Žyo op >xp a·p †q L q íq = ! r @Hr %‰r ,¯r ,Ür < s *Fs $qs .–s ,Ås ,òs *t %Jt -pt lžt N u RZu *­u KØu %$v ,Jv wv ”v ²v *Ïv 1úv D,w Qqw KÃw #x +3x +_x ‹x 4©x 2Þx #y 5y QHy šy ¹y @×y [z Ltz 6Áz Røz PK{ Iœ{ `æ{ LG| V”| `ë| /L} |} k‰} ›õ} 5‘~ 2Ç~ 6ú~ X1 gŠ [ò $N€ $s€ (˜€ %Á€ mç€ MU P£ Vô EK‚ M‘‚ 3ß‚ 9ƒ DMƒ 7’ƒ Zʃ Y%„ T„ <Ô„ T… @f… F§… Hî… p7† a¨† M ! ‡ +X‡ ,„‡ 1±‡ S㇠>7ˆ _vˆ @Öˆ 5‰ ‡M‰ [Õ‰ 31Š 7eŠ &Š ÄŠ +׊ 6‹ Y:‹ 5”‹ WÊ‹ ?"Œ ObŒ @²Œ óŒ @ 1O 7 i¹ I#Ž 1mŽ QŸŽ \ñŽ –N 7å , eJ 3° yä *^‘ 8‰‘ ‘ :Ù‘ .’ 'C’ ,k’ V˜’ lï’ C\“ N “ Mï“ .=” ?l” V¬” P• OT• U¤• Xú• \S– 2°– (ã– 2 — %?— 4e— <š— N×— ]&˜ B„˜ 4ǘ *ü˜ ,'™ &T™ ,{™ &¨™ hÏ™ 28š 6kš J¢š =íš ++› *W› /‚› :²› Eí› 73œ %kœ c‘œ +õœ /! /Q , _® +ž $:ž $_ž N„ž 'Óž 1ûž -Ÿ 6DŸ :{Ÿ Q¶Ÿ Y  /b  /’  1  -ô  )"¡ BL¡ E¡ ;Õ¡ ¢ <(¢ 9e¢ [Ÿ¢ Gû¢ ;C£ £ 3™£ 'Í£ 'õ£ H¤ ^f¤ $Ť ê¤ )x¥ 1¢¥ FÔ¥ ¦ $6¦ _[¦ =»¦ $ù¦ Y§ 8x§ 4±§ 7æ§ &¨ -E¨ `s¨ +Ô¨ 1© 02© 'c© "‹© *®© +Ù© 2ª ,8ª eª (}ª %¦ª ;̪ ,« /5« 1e« #—« F»« 7¬ ,:¬ /g¬ @—¬ ج 4ö¬ >+­ 1j­ +œ­ QÈ­ ® 88® &q® "˜® (»® (ä® C ¯ ,Q¯ ,~¯ («¯ 3Ô¯ ° -° /I° Gy° KÁ° F ± T± Mc± ±± 0À± ñ± ² ! ² &(² O² Y² ?k² B«² î² ³ ³ )³ ?³ G³ P³ X³ p³ „³ ³ "¡³ "ij ç³ ú³ ! ´ ´ '´ :´ S´ j´ x´ ´ ¦´ »´ Ç´ ,×´ :µ H?µ -ˆµ …¶µ r<¶ 7¯¶ ]ç¶ +E· +q· 9· ×· Gî· =6¸ t¸ 0„¸ 5µ¸ $ë¸ 4¹ 3E¹ Qy¹ A˹ O º W]º {µº H1» 2z» 9­» ;ç» L#¼ Np¼ >¿¼ 0þ¼ ¾/½ cî¾ eR¿ c¸¿ =À VZÀ '±À RÙÀ K,Á xÁ ’Á °Á ÆÁ ÜÁ òÁ ( *9 d .€Â !¯Â 0Ñ %à 8(à ,aà "ŽÃ ±Ã &Ñà +øà 7$Ä `\Ä A½Ä 6ÿÄ 76Å 7nÅ ¦Å P(Æ NyÆ OÈÆ 5Ç ?NÇ @ŽÇ ÏÇ {`È nÜÈ /KÉ -{É V©É „Ê @…Ê AÆÊ ;Ë CDË HˆË 1ÑË NÌ 3RÌ W†Ì PÞÌ (/Í 4XÍ 4Í mÂÍ {0Î >¬Î SëÎ <?Ï D|Ï )ÁÏ 'ëÏ ]Ð JqÐ ]¼Ð ]Ñ MxÑ 4ÆÑ 3ûÑ +/Ò R[Ò c®Ò Ó N3Ó :‚Ó %½Ó ;ãÓ Ô 6=Ô ]tÔ *ÒÔ -ýÔ O+Õ :{Õ }¶Õ G4Ö A|Ö &¾Ö AåÖ C'× 5k× %¡× cÇ× I+Ø =uØ ?³Ø EóØ .9Ù 'hÙ .Ù 0¿Ù dðÙ AUÚ 2—Ú .ÊÚ 2ùÚ >,Û BkÛ B®Û ?ñÛ A1Ü 5sÜ D©Ü 4îÜ ;#Ý =_Ý <Ý LÚÝ 2'Þ ZÞ pÞ )…Þ ¯Þ +ÐÞ NüÞ YKß >¥ß 4äß Dà +^à 1Šà F¼à Bá [Fá Y¢á [üá YXâ O²â 6ã m9ã [§ã ?ä 2Cä Kvä 1Âä 0ôä R%å 6xå @¯å Fðå `7æ 2˜æ DËæ 9ç bJç <­ç êç 7è G@è 3ˆè 5¼è 4òè H'é Apé b²é Vê :lê (§ê 1Ðê .ë \1ë #Žë /²ë ;âë >ì ]ì CÝì v!í I˜í /âí 0î bCî P¦î ÷î %ï n>ï <­ï @êï B+ð snð âð Qøð Jñ \añ *¾ñ Séñ N=ò YŒò 9æò * ó .Kó 4zó d¯ó Cô DXô Nô Pìô A=õ +õ 4«õ àõ +ö #,ö Pö nö C‰ö #Íö 5ñö '÷ ;H÷ N„÷ FÓ÷ <ø DWø œø ¼ø %Ñø ÷ø ?ù #Rù Kvù IÂù L ú DYú žú Fµú &üú 0#û Tû dû @vû J·û Mü (Pü \yü @Öü >ý MVý N¤ý Cóý O7þ *‡þ i²þ Oÿ ‹lÿ ‘øÿ TŠ ! Qß ! N1 ! u€ ! :ö ! A1 ! #s ! — ! ± ! Ë ! =á ! ? ! 4_ ! 3” ! 0È ! 0ù ! M* ! ;x ! 4´ ! Oé ! M9 ! ;‡ ! >à ! K ! 2N ! ; ! <½ ! ú ! / ! DE ! 4Š ! C¿ ! N ! #R ! +v ! 2¢ ! KÕ ! D! ! )f ! V ! ?ç ! K' ! s ! #‘ ! Lµ ! 2 ! I5 ! H ! È ! Þ ! 'ó ! 5 ! 'Q ! y ! @ ! Î ! .Ü ! 2 ! 6> ! <u ! I² ! bü ! ?_ ! MŸ ! 7í ! -% ! 1S ! T… ! TÚ ! J/ ! Hz ! Gà ! H  ! JT ! +Ÿ ! .Ë ! 9ú ! M4 ! +‚ ! <® ! Jë ! b6 ! X™ ! @ò ! 3 ! ~T ! ?Ó ! 7 ! +K ! %w ! G ! zå ! ` !  ! !¢ ! Ä ! ä ! 2ý ! 0 ! F ! ] ! t ! !• ! "· ! "Ú ! $ý ! $" ! 6G ! E~ ! 'Ä ! 'ì ! s ! …ˆ ! 4 ! FC ! °Š ! P; ! 5Œ ! 2 ! Sõ ! zI ! vÄ ! 7; ! Ms ! WÁ !  ! 3 ! /H ! !x ! @š ! 5Û ! ! ! @3 ! Mt ! 5 ! !ø ! 5 ! !P ! 7r ! #ª ! 7Î ! #! ! W*! ! l‚! ! 'ï! ! ;" ! 'S" ! %{" ! B¡" ! ä" ! 4þ" ! 53# ! 5i# ! 7Ÿ# ! [×# ! *3$ ! C^$ ! ?¢$ ! 1â$ ! k% ! !€% ! ,¢% ! 4Ï% ! `& ! e& ! 9‚& ! S¼& ! 6' ! dG' ! *¬' ! *×' ! R( ! &U( ! 0|( ! ,­( ! \Ú( ! ?7) ! @w) ! a¸) ! (* ! IC* ! <* ! Ê* ! ë* ! !ù* ! A+ ! ;]+ ! ;™+ ! Õ+ ! 2ç+ ! 7, ! CR, ! 2–, ! *É, ! ô, ! 3- ! ?G- ! f‡- ! +î- ! >. ! 6Y. ! p. ! Œ/ ! ™Ž/ ! •(0 ! N¾0 ! a 1 ! Oo1 ! 0¿1 ! :ð1 ! /+2 ! [2 ! t2 ! •2 ! ¶2 ! Õ2 ! "ô2 ! "3 ! :3 ! [3 ! '|3 ! *¤3 ! -Ï3 ! ,ý3 ! /*4 ! )Z4 ! ,„4 ! (±4 ! "Ú4 ! Mý4 ! [K5 ! Z§5 ! i6 ! Hl6 ! gµ6 ! %7 ! &C7 ! %j7 ! #7 ! B´7 ! L÷7 ! HD8 ! L8 ! 4Ú8 ! ;9 ! ZK9 ! J¦9 ! ]ñ9 ! O: ! \k: ! XÈ: ! -!; ! 'O; ! 'w; ! ^Ÿ; ! þ; ! #< ! 2A< ! 5t< ! ½ª< ! 0h= ! @™= ! =Ú= ! F> ! 3_> ! E“> ! Ù> ! ô> ! - ? ! ž;? ! IÚ? ! K$@ ! +p@ ! œ@ ! :½@ ! &ø@ ! 0A ! PA ! @iA ! AªA ! -ìA ! $B ! ?B ! 5[B ! L‘B ! 9ÞB ! )C ! )BC ! 'lC ! E”C ! 6ÚC ! /D ! %AD ! JgD ! 1²D ! 8äD ! GE ! 0eE ! B–E ! QÙE ! 7+F ! xcF ! DÜF ! F!G ! 8hG ! 5¡G ! c×G ! A;H ! $}H ! 3¢H ! ÖH ! ñH ! I ! Q!I ! 3sI ! >§I ! æI ! !ýI ! J ! ,6J ! <cJ ! & J ! "ÇJ ! *êJ ! .K ! 1DK ! =vK ! ;´K ! ;ðK ! 9,L ! 2fL ! ;™L ! 2ÕL ! 0M ! I9M ! UƒM ! ŽÙM ! 9hN ! 3¢N ! 'ÖN ! RþN ! )QO ! {O ! H—O ! 1àO ! ;P ! ,NP ! -{P ! ©P ! `¶P ! EQ ! ,]Q ! ŠQ ! -¦Q ! ,ÔQ ! "R ! 7$R ! /\R ! ŒR ! (¥R ! 2ÎR ! *S ! #,S ! PS ! pS ! $‘S ! 4¶S ! /ëS ! %T ! $AT ! 0fT ! 3—T ! 'ËT ! ?óT ! *3U ! 0^U ! hU ! 'øU ! 5 V ! VV ! IpV ! 8ºV ! %óV ! QW ! KkW ! B·W ! @úW ! *;X ! EfX ! E¬X ! EòX ! R8Y ! E‹Y ! NÑY ! D Z ! HeZ ! A®Z ! BðZ ! H3[ ! G|[ ! PÄ[ ! I\ ! D_\ ! %¤\ ! /Ê\ ! <ú\ ! 97] ! *q] ! 0œ] ! *Í] ! -ø] ! &^ ! B6^ ! y^ ! 4^ ! $Ä^ ! aé^ ! EK_ ! 6‘_ ! KÈ_ ! :` ! :O` ! =Š` ! (È` ! “ñ` ! C…a ! /Éa ! /ùa ! :)b ! <db ! <¡b ! 0Þb ! =c ! 2Mc ! J€c ! {Ëc ! ^Gd ! R¦d ! Dùd ! 0>e ! 4oe ! !¤e ! PÆe ! 6f ! FNf ! v•f ! F g ! ISg ! g ! "°g ! 3Óg ! 5h ! *=h ! *hh ! ,“h ! PÀh ! +i ! B=i ! €i ! ’i ! ,¤i ! &Ñi ! Pøi ! CIj ! -j ! -»j ! éj ! "k ! 6+k ! bk ! (€k ! 9©k ! 5ãk ! 5l ! Ol ! Bml ! N°l ! ÿl ! /m ! %?m ! 1em ! ,—m ! jÄm ! g/n ! E—n ! Ýn ! $ùn ! 0o ! 0Oo ! (€o ! "©o ! .Ìo ! *ûo ! R&p ! Oyp ! Ép ! 3ép ! "q ! ,@q ! &mq ! ”q ! 2«q ! 7Þq ! r ! 4r ! ;Sr ! "r ! 7²r ! êr ! )s ! F0s ! Cws ! »s ! ,Üs ! * t ! 74t ! /lt ! Jœt ! %çt ! M u ! f[u ! .Âu ! .ñu ! ! v ! :Bv ! m}v ! Aëv ! 6-w ! -dw ! .’w ! (Áw ! $êw ! $x ! $4x ! Yx ! !ex ! (‡x ! °x ! "Ðx ! <óx ! L0y ! ;}y ! 0¹y ! êy ! 6z ! )?z ! (iz ! (’z ! >»z ! ,úz ! G'{ ! o{ ! HŽ{ ! (×{ ! /| ! C0| ! -t| ! F¢| ! é| ! } ! L‚} ! !Ï} ! @ñ} ! -2~ ! &`~ ! '‡~ ! N¯~ ! pþ~ ! .o ! Žž ! S-€ ! )€ ! E«€ ! <ñ€ ! %. ! T ! :r ! $­ ! 2Ò ! /‚ ! 15‚ ! 3g‚ ! 3›‚ ! 0Ï‚ ! Uƒ ! NVƒ ! K¥ƒ ! -ñƒ ! 7„ ! qW„ ! 2É„ ! ü„ ! Y… ! Qw… ! É… ! Aè… ! a*† ! .Œ† ! »† ! ؆ ! @ô† ! K5‡ ! ‡ ! I‡‡ ! ч ! ,î‡ ! )ˆ ! ,Eˆ ! ,rˆ ! Ÿˆ ! X¦ˆ ! &ÿˆ ! w&‰ ! Lž‰ ! ë‰ ! Š ! SŠ ! +kŠ ! 9—Š ! 'ÑŠ ! @ùŠ ! \:‹ ! O—‹ ! )ç‹ ! 9Œ ! 1KŒ ! ,}Œ ! 4ªŒ ! 3ߌ ! ; ! )O ! )y ! 8£ ! !Ü ! 0þ ! (/Ž ! 'XŽ ! %€Ž ! *¦Ž ! .ÑŽ ! / ! =0 ! 6n ! @¥ ! !æ ! S ! A\ ! 3ž ! =Ò ! ‘ ! &‘ ! $D‘ ! 7i‘ ! ¡‘ ! ·‘ ! "Ó‘ ! ;ö‘ ! 12’ ! d’ ! 7{’ ! $³’ ! [Ø’ ! 64“ ! $k“ ! D“ ! )Õ“ ! ,ÿ“ ! d,” ! 2‘” ! 7Ä” ! =ü” ! $:• ! F_• ! B¦• ! ?é• ! <)– ! (f– ! F– ! 3Ö– ! X ! — ! +c— ! 0— ! "À— ! @ã— ! 9$˜ ! W^˜ ! @¶˜ ! =÷˜ ! =5™ ! Ms™ ! @Á™ ! 6š ! ;9š ! -uš ! B£š ! Uæš ! $<› ! Ya› ! ?»› ! >û› ! B:œ ! A}œ ! H¿œ ! H ! HQ ! iš ! ž ! /ž ! Y@ž ! Jšž ! Håž ! 3.Ÿ ! KbŸ ! +®Ÿ ! =ÚŸ ! T  ! Lm  ! Jº  ! >¡ ! ;D¡ ! @€¡ ! JÁ¡ ! f ¢ ! gs¢ ! <Û¢ ! )£ ! QB£ ! C”£ ! BØ£ ! W¤ ! =s¤ ! Q±¤ ! K¥ ! @O¥ ! ‚¥ ! %¦ ! d9¦ ! iž¦ ! § ! <§ ! DV§ ! .›§ ! ʧ ! 8Ú§ ! O¨ ! Tc¨ ! ¸¨ ! Ù¨ ! )÷¨ ! !!© ! C© ! 9]© ! —© ! µ© ! -Õ© ! )ª ! !-ª ! Oª ! iª ! +‰ª ! >µª ! >ôª ! >3« ! (r« ! B›« ! MÞ« ! F,¬ ! s¬ ! ¬ ! i§¬ ! !­ ! *3­ ! ^­ ! v­ ! Š­ ! £­ ! ¸­ ! +έ ! ú­ ! ® ! &® ! <® ! 9R® ! +Œ® ! ¸® ! Ù® ! í® ! ¯ ! ¯ ! 3¯ ! G¯ ! \¯ ! x¯ ! Œ¯ ! ¬¯ ! į ! ä¯ ! ü¯ ! ° ! 4° ! Q° ! f° ! €° ! &š° ! =Á° ! Hÿ° ! FH± ! >± ! 2α ! S² ! ÉU² ! "³ ! B³ ! ]³ ! x³ ! &•³ ! :¼³ ! 7÷³ ! 1/´ ! Da´ ! 3¦´ ! @Ú´ ! ?µ ! A[µ ! *µ ! 6ȵ ! /ÿµ ! //¶ ! *_¶ ! 9Š¶ ! Ķ ! 0㶠! · ! ;3· ! Mo· ! 1½· ! 1ï· ! -!¸ ! $O¸ ! (t¸ ! #¸ ! Á¸ ! ߸ ! ü¸ ! ¹ ! 6¹ ! #S¹ ! w¹ ! •¹ ! ³¹ ! ѹ ! =ï¹ ! -º ! =Kº ! ‰º ! §º ! ź ! 㺠! $» ! &» ! C» ! b» ! €» ! ž» ! ¼» ! 3Ú» ! @¼ ! O¼ ! 1p¼ ! *¢¼ ! #ͼ ! "ñ¼ ! "½ ! L7½ ! 8„½ ! '½½ ! *å½ ! "¾ ! "3¾ ! %V¾ ! %|¾ ! K¢¾ ! >î¾ ! F-¿ ! .t¿ ! *£¿ ! Aο ! DÀ ! SUÀ ! C©À ! <íÀ ! 5*Á ! F`Á ! 4§Á ! =ÜÁ !  ! 2: ! (m ! ,– ! 8à! ;ü ! 08à ! 4ià ! 8žÃ ! 8×à ! 8Ä ! 5IÄ ! iÄ ! $éÄ ! NÅ ! O]Å ! R­Å ! EÆ ! HFÆ ! CÆ ! FÓÆ ! 3Ç ! 3NÇ ! ‚Ç ! kÇ !  È ! 'È ! +EÈ ! 6qÈ ! &¨È ! ÏÈ ! FìÈ ! $3É ! XÉ ! sÉ ! :É ! 2ÊÉ ! 6ýÉ ! 64Ê ! 6kÊ ! 3¢Ê ! ÖÊ ! 3õÊ ! 5)Ë ! R_Ë ! ²Ë ! .ÑË ! BÌ ! PCÌ ! ”Ì ! ´Ì ! KÔÌ ! t Í ! :•Í ! ÐÍ ! BëÍ ! 3.Î ! LbÎ ! %¯Î ! YÕÎ ! 7/Ï ! -gÏ ! 5•Ï ! ËÏ ! ùiÐ ! \cÑ ! gÀÑ ! y(Ò ! 8¢Ò ! 'ÛÒ ! IÓ ! =MÓ ! D‹Ó ! ÐÓ ! [êÓ ! YFÔ ! C Ô ! DäÔ ! 4)Õ ! *^Õ ! T‰Õ ! CÞÕ ! $"Ö ! 5GÖ ! <}Ö ! 6ºÖ ! 2ñÖ ! 2$× ! 'W× ! %× ! "¥× ! EÈ× ! Ø ! /Ø ! KNØ ! /šØ ! FÊØ ! 5Ù ! <GÙ ! +„Ù ! G°Ù ! PøÙ ! @IÚ ! 5ŠÚ ! VÀÚ ! SÛ ! 2kÛ ! 7žÛ ! >ÖÛ ! JÜ ! ,`Ü ! 8Ü ! %ÆÜ ! BìÜ ! 9/Ý ! WiÝ ! 0ÁÝ ! FòÝ ! F9Þ ! 7€Þ ! '¸Þ ! ,àÞ ! 8 ß ! 7Fß ! ?~ß ! $¾ß ! Iãß ! 6-à ! 3dà ! 4˜à ! -Íà ! ;ûà ! =7á ! Uuá ! RËá ! 7â ! @Vâ ! 7—â ! 7Ïâ ! Xã ! )`ã ! %Šã ! b°ã ! Wä ! 0kä ! 3œä ! $Ðä ! Zõä ! 3På ! $„å ! ]©å ! Uæ ! D]æ ! >¢æ ! …áæ ! Ugç ! «½ç ! Aiè ! K«è ! G÷è ! E?é ! 2…é ! 3¸é ! )ìé ! .ê ! "Eê ! .hê ! †—ê ! 0ë ! Oë ! në ! $Žë ! ³ë ! cÓë ! 7ì ! !Mì ! .oì ! +žì ! ?Êì ! ; ! í ! )Fí ! 0pí ! ?¡í ! 8áí ! /î ! 3Jî ! ~î ! î ! $½î ! âî ! +øî ! k$ï ! ’ï ! Z#ð ! ~ð ! -þð ! ,ñ ! Mñ ! G]ñ ! =¥ñ ! *ãñ ! :ò ! Iò ! @eò ! E¦ò ! Cìò ! K0ó ! I|ó ! DÆó ! G ô ! BSô ! G–ô ! BÞô ! G!õ ! Eiõ ! ]¯õ ! J ö ! :Xö ! }“ö ! L÷ ! Ø^÷ ! 7ø ! Mø ! iø ! ~ø ! ‘ø ! §ø ! !Âø ! -äø ! 4ù ! *Gù ! Wrù ! 3Êù ! þù ! .ú ! LHú ! @•ú ! 1Öú ! Eû ! @Nû ! ?û ! 8Ïû ! Aü ! MJü ! O˜ü ! 1èü ! 0ý ! DKý ! jý ! =ûý ! C9þ ! |}þ ! oúþ ! Rjÿ ! v½ÿ ! ]4 H’ 'Û . E2 [x Ô =ê 7( v` × 4õ N* >y D¸ -ý 0+ .\ .‹ -º .è . -F Ut HÊ ~ ;’ CÎ D JW L¢ ,ï ' @D 1… 1· Aé -+ /Y .‰ 9¸ 7ò * ! +K ! 8w ! $° ! Õ ! (ö ! 1 IQ +› ?Ç . K6 1‚ 0´ Eå F+ *r 7 2Õ  (& O Ih /² 0â ~ 8’ 1Ë 4ý A2 5t ?ª 5ê ;  6\ 7“ 9Ë 5 6; Dr 5· Bí Z0 ;‹ 9Ç 8 B: D} F C  LM Jš Aå [' Gƒ [Ë W' * ª ;Å 5 87 ?p E° Eö K< 4ˆ -½ 1ë L 3j ž L² 9ÿ +9 ;e <¡ DÞ # > ,[ @ˆ É 7Ý % ; [ &y )  $Ê /ï 0 aP S² < ;C = ;½ @ù O: 3Š ¾ 4Ð 8! !>! e`! bÆ! b)" -Œ" º" ,Ð" )ý" #'# 9K# 3…# /¹# 0é# .$ ?I$ 5‰$ '¿$ 2ç$ O% 'j% '’% 9º% ;ô% 20& Fc& -ª& DØ& L' bj' Í' Fæ' Y-( -‡( 'µ( )Ý( ') M/) ]}) cÛ) !?* Ga* 7©* Aá* P#+ Rt+ .Ç+ gö+ 0^, T, Cä, E(- Qn- xÀ- C9. _}. YÝ. z7/ <²/ @ï/ Y00 yŠ0 [1 T`1 cµ1 f2 ~€2 Yÿ2 LY3 `¦3 K4 ‚S4 UÖ4 `,5 b5 ƒð5 \t6 eÑ6 {77 `³7 B8 lW8 Ä8 ˆR9 lÛ9 >H: ©‡: `1; M’; Uà; v6< b­< ˆ= Š™= 8$> 4]> ’> (³> HÜ> n%? =”? HÒ? v@ O’@ wâ@ =ZA S˜A GìA E4B -zB C¨B .ìB ,C gHC +°C "ÜC ?ÿC J?D $ŠD &¯D 8ÖD "E -2E Y`E HºE 'F L+F ;xF B´F C÷F 2;G :nG -©G ×G 8íG &H *EH FpH N·H "I 7)I aI I @–I -×I HJ LNJ n›J  ! K 4(K ]K tK …K & K &ÇK îK EÿK IEL SL UãL M9M P‡M ;ØM TN OiN #¹N ÝO 1æP MQ =fQ +¤Q -ÐQ )þQ >(R :gR A¢R 8äR DS AbS B¤S ,çS HT ]T :wT B²T 6õT F,U BsU D¶U BûU )>V +hV ”V «V QÂV +W A@W :‚W F½W DX <IX H†X ?ÏX MY E]Y F£Y IêY ,4Z IaZ «Z 1ÊZ 6üZ V3[ ! Š[ u•[ t \ €\ Qš\ $ì\ Z] .l] D›] à] 4ú] ./^ ^^ ^ +Œ^ -¸^ Sæ^ ]:_ ˜_ ;¶_ ,ò_ '` QG` ™` 1©` FÛ` "a '=a 'ea +a #¹a [Ýa J9b N„b DÓb 4c IMc 4—c MÌc Hd [cd '¿d çd Ve !]e !e (¡e -Êe øe +f @@f 'f `©f M ! g DXg ‡g e%h ?‹h DËh _i \pi ZÍi 9(j *bj :j 0Èj pùj 3jk <žk 9Ûk /l 2El Cxl *¼l Pçl I8m 4‚m .·m 5æm _n |n W„n DÜn C!o <eo F¢o ¨éo K’p GÞp 2&q 2Yq Œq ¨q 9Äq Dþq 5Cr *yr !¤r DÆr 5 s :As 3|s *°s AÛs t `:t o›t W u -cu <‘u HÎu bv /zv 0ªv EÛv [!w a}w hßw 4Hx U}x pÓx Dy 3`y ”y I³y ;ýy J9z 0„z $µz 'Úz %{ N({ -w{ ¥{ lÃ{ ?0| Fp| H·| A} MB} O} là} QM~ IŸ~ ]é~ VG Wž 3ö '*€ 7R€ AŠ€ 7Ì€ = UB S˜ ì + ‚ 68‚ o‚ ,‚ 4½‚ /ò‚ "ƒ ?ƒ O`ƒ I°ƒ Eúƒ 8@„ 9y„ 2³„ 0æ„ 2… 0J… {… Z’… /í… † ;† DL† H‘† LÚ† _'‡ Z‡‡ =⇠ ˆ ,@ˆ 7mˆ '¥ˆ $͈ /òˆ ("‰ ?K‰ V‹‰ )≠F Š 3SŠ ‡Š -¦Š dÔŠ 99‹ 1s‹ X¥‹ ^þ‹ .]Œ !ŒŒ G®Œ GöŒ T> D“ 7Ø OŽ $`Ž …Ž N¢Ž !ñŽ  A& 3h œ 2º Mí -; /i 9™ ;Ó ‘ >‘ ?\‘ <œ‘ :Ù‘ &’ 6;’ Ir’ ¼’ Ì’ "Ü’ 3ÿ’ ?3“ ˆs“ ˆü“ x…” )þ” (• 1D• ’v• W – &a– ,ˆ– )µ– ,ß– I — KV— I¢— [ì— H˜ g˜ ~˜ 'Ÿ˜ ǘ •è˜ ¦~™ >%š .dš Q“š #åš  › k!› T› Fâ› ²)œ \Üœ @9 8z 8³ 8ì &%ž $Lž Mqž [¿ž 8Ÿ @TŸ M•Ÿ E㟠()  R  /n  /ž  <Π e ¡ Ëq¡ )=¢ Ug¢ H½¢ F£ M£ BÍ£ B¤ BS¤ –¤ M¥ šd¥ `ÿ¥ 2`¦ *“¦ #¾¦ '⦠Q ! § (\§ 8…§ <¾§ 8û§ :4¨ 9o¨ -©¨ 0ר ‘© Cš© 'Þ© ª U!« Vw« eΫ n4¬ U£¬ ^ù¬ =X­ 5–­ tÌ­ A® A`® ¢® P¿® G¯ X¯ El¯ -²¯ 6௠;° BS° a–° ,ø° 7%± +]± V‰± Và± G7² 6² X¶² h³ Qx³ rʳ D=´ (‚´ .«´ NÚ´ )µ 9Jµ ;„µ <Àµ 0ýµ '.¶ 0V¶ C‡¶ C˶ ;· ZK· M¦· ô· %¸ D5¸ 6z¸ E±¸ L÷¸ LD¹ b‘¹ Pô¹ 'Eº (mº d–º #ûº <» L\» }©» .'¼ )V¼ I€¼ Iʼ J½ !_½ <½ þ½ Æ‚¾ sI¿ ½¿ 2Ù¿ : À nGÀ *¶À 9áÀ 2Á &NÁ IuÁ =¿Á BýÁ :@ 9{ CµÂ ;ù X5à OŽÃ !Þà 7Ä (8Ä 7aÄ 8™Ä $ÒÄ ÷Ä :Å 8PÅ 8‰Å <ÂÅ *ÿÅ 3*Æ 7^Æ 9–Æ =ÐÆ Ç C-Ç IqÇ P»Ç P È X]È `¶È eÉ k}É jéÉ ~TÊ ~ÓÊ ~RË ~ÑË €PÌ ~ÑÌ €PÍ ~ÑÍ tPÎ %ÅÎ EëÎ :1Ï lÏ 7ŒÏ !ÄÏ ?æÏ 9&Ð `Ð 7Ð A·Ð 7ùÐ *1Ñ 7\Ñ '”Ñ ¼Ñ "ÝÑ *Ò &+Ò ARÒ R”Ò ?çÒ :'Ó :bÓ ;Ó TÙÓ e.Ô ”Ô 4µÔ -êÔ Õ 41Õ QfÕ W¸Õ $Ö $5Ö 5ZÖ *Ö »Ö ÓÖ 7éÖ ;!× -]× =‹× 7É× 2Ø 44Ø 6iØ / Ø 4ÐØ 6Ù -<Ù -jÙ *˜Ù +ÃÙ 1ïÙ N!Ú 7pÚ 4¨Ú 4ÝÚ /Û 7BÛ 5zÛ 0°Û 3áÛ 1Ü 3GÜ F{Ü 5ÂÜ 3øÜ (,Ý 7UÝ &Ý A´Ý IöÝ E@Þ †Þ 'ŸÞ :ÇÞ ,ß q/ß \¡ß þß Bà aà |à ›à ¶à ;Äà Lá ]Má K«á R÷á UJâ D â nåâ _Tã @´ã Yõã @Oä Óä Ldå 7±å 4éå .æ @Mæ 2Žæ 5Áæ F÷æ 4>ç 2sç 2¦ç |Ùç lVè mÃè 71é _ié NÉé aê lzê ;çê G#ë 2kë Kžë 6êë Z!ì n|ì fëì KRí Hží ?çí d'î =Œî PÊî /ï 3Kï Iï \Éï &𠊨ð Ž3ñ XÂñ mò Z‰ò Näò c3ó Y—ó Jñó J<ô k‡ô Nóô /Bõ 3rõ @¦õ vçõ D^ö \£ö r÷ =s÷ Q±÷ ”ø R˜ø hëø gTù s¼ù S0ú h„ú míú ›[û >÷û ?6ü avü ÐØü Ò©ý |þ e›þ ÿ &ÿ Cÿ ^ÿ Cxÿ =¼ÿ Dúÿ Ç? … a ‰ï 6y 1° Yâ ©< ¨æ & (¶ Tß 64 Bk ® *à Bî Z1 +Œ W¸ O <` ? #Ý 7 19 #k 5 ?Å 8 E> $„ b© $ ! M1 !  ! =ž ! @Ü ! ' :E .€ K¯ Rû EN *” '¿ ç  - @G /ˆ :¸ \ó $P Vu 'Ì Oô OD 5” NÊ  C6 =z V¸ 5 GE " %° !Ö 4ø T- 3‚ 9¶ ð : .L 8{ 4´ 7é *! 3L "€ !£ Å %ß U 3[ 9 'É 5ñ #' K ?e @¥ Aæ >( ?g @§ Bè ;+ 8g 7  9Ø : BM : BË D 1S >… Ä $å 6 !  GA ‰ (¨ -Ñ .ÿ 6. be bÈ B+ 8n )§ 1Ñ 0 ?4 <t @± 'ò b } › ® Ã Ö -ì & /A q 7 5Ç ý ! ! ! ,! -B! &p! —! µ! !Ò! ô! "" U6" 3Œ" À" ;Ê" "# ,)# BV# %™# +¿# 6ë# F"$ Qi$ ?»$ *û$ &% F% ]% !x% š% -¶% Rä% R7& PŠ& =Û& L' &f' E' <Ó' =( DN( -“( 3Á( -õ( ,#) P) Ao) ±) !Î) ?ð) M0* 4~* V³* V ! + Va+ V¸+ , %, ?D, A„, -Æ, :ô, /- EK- ‘- ­- 0/. U`. %¶. Ü. Eø. =>/ |/ I/ "ç/ Q ! 0 \0 !Ü0 3þ0 021 +c1 :1 5Ê1 @2 ;A2 H}2 IÆ2 3 G13 8y3 ,²3 ß3 ü3 A4 8P4 +‰4 *µ4 à4 $5 -&5 4T5 )‰5 $³5 Ø5 8ì5 >%6 0d6 A•6 ×6 ö6 + ! 7 )67 ;`7 Vœ7 +ó7 =8 :]8 '˜8 ?À8 9 99 'S9 #{9 $Ÿ9 Ä9 á9 3þ9 Y2: Œ: 2¬: 3ß: &; %:; „`; Då; ,*< DW< %œ< 7Â< .ú< e)= '= T·= = > &J> Aq> H³> *ü> '? fB? n©? i@ .‚@ ±@ SÎ@ 2"A 6UA )ŒA <¶A /óA #B BB ;_B R›B QîB B@C )ƒC :­C 5èC CD [bD 5¾D #ôD E #8E \E nE J€E ËE 'ëE F :/F %jF @F HÑF 9G DTG |™G 4H )KH @uH :¶H FñH Y8I A’I !ÔI 3öI '*J IRJ @œJ `ÝJ Q>K [K AìK K.L :zL ]µL qM /…M "µM IØM )"N =LN ŠN +¡N -ÍN "ûN *O &IO #pO /”O .ÄO óO EP eYP ,¿P AìP 9.Q ShQ Q¼Q 9R )HR 'rR GšR DâR B'S @jS 1«S >ÝS KT )hT >’T OÑT _!U _U oáU nQV YÀV RW ;mW 1©W 7ÛW -X NAX ;X ^ÌX M+Y -yY ;§Y 5ãY EZ 3_Z C“Z C×Z 0[ LL[ ?™[ 9Ù[ L\ Q`\ P²\ P] PT] ;¥] >á] 7 ^ 4X^ g^ 4õ^ L*_ Mw_ KÅ_ J` 9\` .–` ;Å` &a 4(a 4]a G’a 4Úa Db ATb _–b Döb >;c =zc "¸c 8Ûc 6d VKd .¢d FÑd Ye @re 9³e Fíe F4f I{f BÅf bg 6kg E¢g Eèg G.h *vh {¡h Mi [ki @Çi Gj =Pj 9Žj .Èj u÷j ;mk H©k ,òk |l 0œl uÍl 7Cm ={m W¹m [n /mn )n 6Çn Kþn 3Jo 4~o (³o 3Üo 3p >Dp +ƒp N¯p <þp &;q Abq 6¤q =Ûq &r &@r :gr >¢r Vár g8s N s 8ïs O(t 4xt ;­t nét ‰Xu Aâu i$v LŽv HÛv A$w _fw `Æw /'x QWx R©x aüx O^y U®y Nz 0Sz K„z iÐz 6:{ @q{ :²{ Eí{ X3| 7Œ| dÄ| 8)} Wb} Iº} ?~ QD~ P–~ 9ç~ 1! BS D– @Û K€ Rh€ D»€ P =Q P 9à s‚ *Ž‚ (¹‚ Eâ‚ 2(ƒ 4[ƒ aƒ [òƒ ZN„ 1©„ <Û„ O… *h… 5“… EÉ… 7† $G† Sl† 5À† @ö† $7‡ B\‡ 9Ÿ‡ 5Ù‡ Xˆ dhˆ <͈ J ! ‰ :U‰ i‰ Fú‰ $AŠ AfŠ A¨Š eêŠ 2P‹ Kƒ‹ 3Ï‹ <Œ B@Œ 6ƒŒ SºŒ l U{ `Ñ ,2Ž 9_Ž O™Ž BéŽ ,, HY P¢ Pó CD Lˆ ƒÕ *Y‘ S„‘ ,Ø‘ 8’ >’ LD’ O‘’ Yá’ @;” \|” gÙ” AA• Dƒ• #È• (ì• *– %@– ]f– FÄ– l — $x— H— 0æ— 5˜ M˜ k˜ Œ˜ ¬˜ ̘ ì˜ ; ™ .I™ Fx™ F¿™ Kš ARš !”š "¶š pÙš 8J› 5ƒ› (¹› â› ô› œ œ ! +œ 66œ Kmœ 1¹œ 4ëœ 3 0T …… C ž 6Ož C†ž yÊž ADŸ D†Ÿ ËŸ BÛŸ 2  #Q  Eu  »  5½  Jó  w>¡ >¶¡ (õ¡ D¢ /c¢ \“¢ Pð¢ FA£ Tˆ£ 0Ý£ z¤ O‰¤ -Ù¤ G¥ >O¥ HŽ¥ L×¥ V$¦ /{¦ 0«¦ ܦ 5ó¦ 2)§ v\§ ZÓ§ B.¨ Bq¨ N´¨ (© 5,© &b© J‰© MÔ© A"ª @dª J¥ª 9ðª 3*« P^« [¯« G ¬ HS¬ Aœ¬ iÞ¬ ?H­ 7ˆ­ <À­ 4ý­ 52® h® >® >¾® hý® 1f¯ T˜¯ 4í¯ ;"° A^° U ° =ö° 74± 2l± 4Ÿ± =Ô± >² ;Q² 9² 0Dz ø² * ³ B7³ z³ @™³ *Ú³ 1´ 7´ 3N´ R‚´ 3Õ´ 2 µ ‹<µ Eȵ D¶ =S¶ ;‘¶ DͶ ;· AN· i· ú· ¸ 9¸ )N¸ 3x¸ M¬¸ Mú¸ H¹ _d¹ 4Ĺ Iù¹ 2Cº /vº .¦º :Õº D» 5U» -‹» $¹» 5Þ» E¼ ?Z¼ 6š¼ Ѽ >ñ¼ H0½ Ry½ B̽ D¾ AT¾ C–¾ >Ú¾ @¿ $Z¿ 6¿ 6¶¿ 6í¿ 6$À 5[À -‘À /¿À ïÀ ? Á %KÁ @qÁ 7²Á êÁ 8x X±Â @ ! à /Kà 7{à =³Ã 4ñà 2&Ä =YÄ -—Ä /ÅÄ 1õÄ ,'Å TÅ 3cÅ -—Å IÅÅ Æ J%Æ 2pÆ I£Æ NíÆ =<Ç 6zÇ V±Ç CÈ ALÈ CŽÈ CÒÈ É %&É $LÉ $qÉ .–É HÅÉ HÊ *WÊ C‚Ê %ÆÊ /ìÊ Ë D%Ë CjË N®Ë 6ýË .4Ì BcÌ c¦Ì 0 ! Í #;Í n_Í 7ÎÍ Î 3Î KFÎ .’Î 1ÁÎ ?óÎ V3Ï VŠÏ BáÏ B$Ð #gÐ ‹Ð 5ªÐ 1àÐ ,Ñ B?Ñ /‚Ñ 1²Ñ /äÑ Ò H1Ò zÒ B–Ò "ÙÒ nüÒ `kÓ aÌÓ ^.Ô PÔ \ÞÔ T;Õ 1Õ $ÂÕ çÕ üÕ R ! Ö .]Ö 5ŒÖ ÂÖ HÛÖ 2$× >W× $–× G»× 7Ø f;Ø @¢Ø 4ãØ GÙ Y`Ù :ºÙ *õÙ 7 Ú HXÚ ¡Ú #µÚ )ÙÚ 1Û /5Û 8eÛ žÛ ¿Û ØÛ ïÛ Ü 4%Ü 'ZÜ ‚Ü *™Ü 9ÄÜ *þÜ 6)Ý 6`Ý 8—Ý 6ÐÝ 6Þ 6>Þ 6uÞ 6¬Þ -ãÞ 6ß Hß bß pß .‚ß +±ß (Ýß $à $+à Pà oà >à Àà Õà òà >á 5Aá ,wá 9¤á 5Þá (â 1=â 7oâ )§â %Ñâ %÷â +ã 1Iã +{ã 0§ã Øã öã ä ,1ä (^ä T‡ä NÜä >+å +jå 4–å 2Ëå 4þå 73æ :kæ 8¦æ ßæ \üæ 8Yç 2’ç Åç &Ûç <è &?è -fè ;”è FÐè é L!é !né é ¯é !Ìé -îé Aê @^ê 8Ÿê >Øê Së *kë ;–ë %Òë øë Xì :pì 7«ì 4ãì Dí /]í 0í ¾í XÌí <%î 5bî I˜î >âî >!ï ?`ï H ï Héï e2ð -˜ð )Æð ?ðð 0ñ Qñ )mñ C—ñ &Ûñ 1ò 14ò cfò GÊò .ó @Aó @‚ó =Ãó -ô /ô LPô ô '±ô FÙô + õ 3Lõ €õ >¡õ >àõ Vö Bvö .¹ö =èö _&÷ [†÷ /â÷ 8ø *Kø 3vø ?ªø Lêø ^7ù '–ù '¾ù Eæù 6,ú Lcú ]°ú Iû 'Xû €û ™û #±û AÕû 9ü -Qü 9ü 6¹ü *ðü Dý `ý #|ý ' ý /Èý øý .þ Eþ +^þ &Šþ %±þ ?×þ ÿ $ÿ $1ÿ Vÿ lÿ €ÿ M™ÿ 3çÿ E 6a :˜ ;Ó I [Y %µ +Û $ %, 9R :Œ 'Ç /ï 7 W >w 8¶ 1ï ;! 5] 1“ 'Å -í 6 %R ex .Þ +  +9 9e AŸ @á 8" D[ G  Fè &/ /V G† )Î tø Jm @¸ Dù %> ! ;d ! C  ! Hä ! j- A˜ .Ú C <M PŠ +Û  " > )Y <ƒ .À "ï 1 :D M ;Í >  @H 2‰ ;¼ Jø IC 2 >À "ÿ @" c Hx 4Á †ö :} =¸ %ö < ZY U´ ‡ !  O’ Mâ F0 3w D« 6ð 5' 0] IŽ &Ø 5ÿ K5 = :¿ 7ú )2 3\ 0 (Á %ê : FK ?’ "Ò Põ ?F 9† 8À Bù C< I€ 'Ê ,ò 0 =P TŽ -ã P 4b C— GÛ (# *L ow tç v\ :Ó ; ;J D† `Ë 1,! 5^! 7”! Ì! /ä! " +" /D" 4t" +©" MÕ" ?## 8c# Wœ# Aô# +6$ /b$ ! ’$ *$ *È$ ó$ :% 1C% -u% J£% 6î% %& ;& P& j& €& 8& )Ö& H' GI' T‘' fæ' %M( 8s( 5¬( 9â( K) Oh) ¸) ×) Vô) `K* #¬* 8Ð* & + 0+ BN+ K‘+ OÝ+ 0-, H^, H§, Bð, 83- 3l- ? - Dà- Q%. Gw. 0¿. 1ð. "/ :;/ 5v/ 9¬/ 2æ/ 0 +50 2a0 I”0 0Þ0 1 `$1 j…1 Eð1 H62 A2 TÁ2 Y3 Yp3 =Ê3 64 3?4 :s4 -®4 Ü4 ý4 05 K5 ;g5 2£5 3Ö5 2 ! 6 *=6 #h6 .Œ6 4»6 2ð6 4#7 #X7 /|7 w¬7 @$8 ?e8 D¥8 Cê8 {.9 ,ª9 Y×9 K1: W}: 0Õ: 4; .;; :j; U¥; _û; %[< < 6œ< &Ó< Zú< <U= T’= 2ç= 0> -K> .y> @¨> 2é> 6? DS? 2˜? OË? `@ ]|@ VÚ@ %1A ]WA 4µA LêA Q7B E‰B GÏB CC Q[C 8­C RæC *9D AdD -¦D VÔD +E @EE F†E [ÍE 5)F D_F !¤F &ÆF 3íF Z!G k|G qèG iZH JÄH sI /ƒI >³I -òI 6 J AWJ &™J 9ÀJ ,úJ "'K EJK 3K <ÄK 8L 2:L /mL =L ,ÛL <M 5EM .{M .ªM %ÙM ÿM 2N ;KN O‡N )×N 0O "2O 2UO *ˆO /³O /ãO .P BP ?[P )›P ÅP äP Q B Q :cQ *žQ 7ÉQ 0R 92R 5lR [¢R KþR HJS “S ?©S 6éS F T 8gT 7 T ØT óT U U .U #NU rU H’U WÛU +3V _V =wV 0µV ?æV .&W /UW 5…W .»W @êW M+X NyX CÈX $ Y >1Y 3pY 5¤Y /ÚY ' ! Z y2Z 3¬Z /àZ &[ 67[ Ln[ I»[ 9\ 2?\ ?r\ 0²\ /ã\ B] 9V] S] Sä] ;8^ 7t^ Y¬^ ?_ F_ SW_ R«_ "þ_ >!` `` 4~` 0³` +ä` Aa .Ra 0a .²a áa eøa '^b $†b 6«b Râb 85c Dnc =³c Añc I3d n}d Iìd q6e r¨e uf \‘f [îf &Jg Xqg <Êg 7h =?h G}h 2Åh ?øh ,8i 2ei E˜i JÞi 1)j /[j 0‹j H¼j Ak TGk œk "·k ^Úk 59l $ol #”l V¸l Qm am m 8m >Öm /n BEn +ˆn X´n J o -Xo ,†o 2³o æo p 'p Fp cp ,p ®p 8Áp +úp B&q +iq •q 6¨q 5ßq !r 7r )Mr +wr +£r 3Ïr s s .s Es Ss 3as 3•s YÉs $#t "Ht kt .ƒt ²t ,Ët Bøt +;u +gu “u $´u @Ùu 4v Ov )fv v §v )Äv îv + w f9w 5 w ]Öw 54x 3jx 6žx /Õx ay (gy y 8­y æy 7þy :6z qz ‘z $¬z $Ñz öz %{ %8{ F^{ 8¥{ ,Þ{  | A| _a| HÁ| , ! } ,7} "d} ‡} ¦} 2Ã} (ö} ?~ d_~ jÄ~ d/ J” ß Cñ S5€ #‰€ ;­€ Aé€ 4+ K` ¬ 9Ë @‚ 6F‚ C}‚ :Á‚ :ü‚ E7ƒ )}ƒ 5§ƒ =݃ +„ <G„ <„„ Á„ Ç„ ?Þ„ 3… +R… /~… ®… Î… *ï… +† !F† "h† %‹† ±† dž ↠4ê† @‡ 4`‡ +•‡ 'Á‡ 1é‡ ?ˆ 2[ˆ 1Žˆ 0Àˆ 1ñˆ #‰ #D‰ h‰ †‰ A§‰ Aé‰ ++Š )WŠ Š !“Š µŠ ÇŠ WÙŠ 1‹ C‹ ]‹ y‹ “‹ ­‹ ΋ à‹ ô‹ Œ "Œ :=Œ xŒ ‹Œ 5Œ 6ÓŒ 5 ! 5@ v L Ý 'þ &Ž 8Ž <JŽ ‡Ž ™Ž ®Ž ÌŽ ㎠øŽ  !  $6 %[  • « 2Á ô  $ ; U !i ‹ ¤ » Ù ò ‘ ‘ 2‘ H‘ Z‘ t‘ #†‘ ª‘ O¼‘ 0 ’ S=’ 6‘’ È’ #ç’  “ (“ :“ Y“ x“ D—“ Ü“ ù“ ,” 6C” z” G”” )Ü” •  • ;• P• n• $‹• $°• $Õ• ú• !– )9– @c– *¤– %Ï– 'õ– 3— 1Q— ƒ— /¤— Ô— ò— /˜ 6˜ #M˜ q˜ R‘˜ Qä˜ *6™ 6a™ ˜™ µ™ Ô™ #ó™ %š =š +\š "ˆš #«š Ïš $íš › ^2› Y‘› bë› _Nœ "®œ !Ñœ Ióœ G= l… =ò 50ž :fž H¡ž Eêž 20Ÿ JcŸ :®Ÿ JéŸ 44  <i  V¦  ƒý  i¡ ië¡ 3U¢ +‰¢ 0µ¢ Pæ¢ 47£ Jl£ 8·£ Zð£ RK¤ ]ž¤ >ü¤ \;¥ 4˜¥ *Í¥ Cø¥ <¦ GW¦ ,Ÿ¦ ! ̦ 0צ ,§ 5§ .R§ $§ ¦§ B¹§ 9ü§ E6¨ $|¨ #¡¨ +Ũ /ñ¨ 9!© 8[© +”© DÀ© zª M€ª Ϊ =ëª )« >D« 1ƒ« 3µ« 3é« 4¬ R¬ `¬ An¬ @°¬ *ñ¬ *­ G­ Bd­ %§­ Í­ "Þ­ !® ##® $G® !l® .Ž® A½® Eÿ® E¯ -Z¯ *ˆ¯ -³¯ #ᯠ,° D2° >w° B¶° ,ù° 3&± 'Z± D‚± #DZ :ë± 4&² $[² /€² 0°² Dá² A&³ Jh³ 4³³ 5è³ ´ [+´ /‡´ T·´ µ &-µ Tµ \\µ B¹µ 6üµ S3¶ +‡¶ D³¶ Kø¶ GD· cŒ· <ð· >-¸ 0l¸ 4¸ Ò¸ ð¸ @¹ LG¹ S”¹ Dè¹ Z-º =ˆº <ƺ >» GB» HŠ» *Ó» *þ» ;)¼ #e¼ '‰¼ 1±¼ 1ã¼ 1½ 2G½ *z½ —¥½ ¹=¾ P÷¾ DH¿ F¿ 5Ô¿ ; ! À GFÀ OŽÀ !ÞÀ !Á &"Á +IÁ 0uÁ :¦Á .áÁ L l] SÊ Yà dxà mÝà KÄ YËÄ C%Å aiÅ [ËÅ 4'Æ +\Æ +ˆÆ 0´Æ #åÆ E Ç DOÇ C”Ç ,ØÇ -È B3È 1vÈ D¨È 7íÈ ;%É :aÉ 4œÉ JÑÉ .Ê >KÊ 7ŠÊ [ÂÊ JË 9iË I£Ë )íË 'Ì =?Ì 8}Ì M¶Ì !Í &Í 8FÍ Í G Í <èÍ @%Î NfÎ µÎ (ÔÎ +ýÎ ,)Ï /VÏ 9†Ï ÀÏ ! ÔÏ 4ßÏ >Ð 0SÐ 2„Ð ;·Ð #óÐ #Ñ %;Ñ EaÑ ;§Ñ <ãÑ  Ò 5:Ò 8pÒ 9©Ò AãÒ F%Ó 2lÓ ?ŸÓ 3ßÓ 3Ô 3GÔ E{Ô 2ÁÔ ôÔ F Õ _SÕ R³Õ DÖ 'KÖ AsÖ 2µÖ 6èÖ 1× )Q× {× J˜× Gã× P+Ø F|Ø QÃØ ZÙ ;pÙ )¬Ù *ÖÙ +Ú Z-Ú \ˆÚ 9åÚ LÛ lÛ !|Û !žÛ !ÀÛ !âÛ Ü M#Ü ]qÜ UÏÜ G%Ý *mÝ ^˜Ý f÷Ý d^Þ oÃÞ N3ß n‚ß \ñß Nà !`à 4‚à ;·à óà Aá GEá á ®á Çá ßá .ïá Oâ Vnâ WÅâ ã J=ã ?ˆã GÈã ?ä 7Pä -ˆä *¶ä (áä - ! å "8å *[å 1†å ,¸å åå =æ I?æ ?‰æ /Éæ *ùæ .$ç HSç Vœç 5óç 6)è 7`è P˜è aéè (Ké /té ¤é 5µé ;ëé +'ê "Sê >vê µê 4Óê 0ë +9ë Aeë .§ë 0Öë .ì O6ì B†ì @Éì  ! í K%í ,qí 4ží 7Óí ? î `Kî h¬î fï q|ï Rîï pAð n²ð v!ñ t˜ñ  ò ^ò ~ìò -kó O™ó 2éó 5ô CRô Z–ô Zñô FLõ F“õ 0Úõ G ö ^Sö S²ö 0÷ 7÷ 8W÷ 6÷ 8Ç÷ Aø -Bø 'pø 7˜ø 6Ðø 6ù ;>ù Tzù GÏù ?ú 1Wú F‰ú CÐú Kû Q`û -²û „àû Meü J³ü 7þü (6ý E_ý D¥ý aêý ILþ –þ ,¶þ =ãþ 7!ÿ EYÿ 3Ÿÿ ;Óÿ DLT6¡FØ/'Ow•B¥Kè+40`6‘0È>ù;8 t@•7Ö9<H@…=ÆF&K:r.­bÜ@?E€Æ3ã90Q‚¡&¿$æ4 P@\‘?î;. j { Q“ 5å @ ! @\ ! / ! /Í ! ý !  , B Z r Š Ÿ · Ì á ö  !  7 T l ƒ ˜ ­ Ä Ü ñ   6 K ` x  ¢ · Ì ä ü )>Vkƒ˜°Çßô 3H`u¢ºÔì+7C{0Ž¿ßõ#+3/_¨Á#á?GE&#´Ø7î7&6^,•3Â#ö::U7:È4,8Qe6·0î%%E-k)™ Ã(ä/ J=.ˆ4·=ì:*6e6œ4Ó2E;.¡;Ð -;B7~6¶>í*,>W –%·#Ý+0-$^9ƒ'½,å4!G5i%Ÿ>ÅN.i0˜2É&ü<##`)„8®9çH! /j *š #Å (é e!#x!,œ!iÉ!X3"Œ"4¥"5Ú"#<!#-^#+Œ#.¸#$ç#3 $&@$g$F{$.Â$3ñ$3%%BY%3œ%4Ð%0&I6&0€&7±&0é&'!.'#P't'+”'+À'+ì'+(+D(+p(+œ(+È(+ô(+ )-L)+z)(¦).Ï)-þ)+,*+X*+„*+°*Ü*%û*>!+>`+>Ÿ+*Þ+' ,'1,'Y,,'ž,Æ,+ã,'-'7-'_-'‡-'¯-'×-:ÿ-J:.g…./í.E/.c//’/0Â/=ó/010=b0 0$»0/à01B01!s10•1Æ1'å1= 2$K2-p2-ž28Ì2B3@H3.‰3¸3!Õ37÷3 /4'P43x4B¬47ï4;'5"c5K†5.Ò5*6%,60R6/ƒ67³6)ë6.7.D7s7JŽ7!Ù7Aû7-=8+k85—8@Í8H9<W90”92Å9%ø9@:!_:3:'µ:3Ý:,;0>;'o;!—;H¹;0<53<i<‚<8<Ö<0õ<;&=b=5x=@®=ï=>">KA>L>9Ú>7?>L?c‹?lï?1\@'Ž@.¶@.å@/A@DA'…A$­A-ÒA3B-4B8bB/›B/ËB-ûBB)C8lC3¥CRÙCF,DsDc‹D4ïD$$E;IE;…E9ÁE.ûE"*FMF,iF$–F'»FEãF6)G3`G9”GÎG@ßG6 H3WH.‹H6ºH3ñH%I":IN]I-¬IIÚI%$JFJJ&‘J0¸JéJKK"8K0[K/ŒK.¼K(ëK%L&:L&aL&ˆL)¯L*ÙL(M(-M(VM&M#¦M!ÊM1ìM-N$LN#qN#•N&¹N#àN*O+/O/[O,‹O#¸O)ÜO&P$-P#RP%vP:œP€×PgXQCÀQ R2R)AR.kRšR;ºR/öR&SM@S,ŽS(»SäS-TP0T7T*¹T#äT,Uc5U7™U\ÑU.V'CV4kV, V;ÍV6 WD@WV…WÜW)ôW(X*GX+rX2žXÑXHâX#+YVOYq¦YVZ oZ[!.[;P[<Œ[8É[H\@K\IŒ\?Ö\L]:c]%ž]:Ä]:ÿ]7:^6r^;©^Kå^,1_[^_$º_"ß_.`1`5L`5‚`@¸`4ù`-.a8\a(•a!¾a'àa"b++b&Wb~b™b±bÑb/ðb# c&Dckc+ˆc´c)Ðcúc)d+@d*ld:—d;Òd2e.Ae%pe3–e:Êe+fD1f)vf f#¿f=ãf8!g3ZgŽgŸg2¿g.òg'!h!Ih2khBžhSáh;5i#qiL•iBâi*%j)Pj+zj-¦jHÔjEkFck:ªk[åkOAlE‘l9×l\mCnmH²m0ûm>,nBkn9®nGènR0o+ƒoN¯oAþoP@p6‘p<Èp=q2Cq7vqA®qAðq=2r4prB¥r)èr+sL>sL‹sØs3ôs/(t+Xt?„t+ÄtGðt98u1ru1¤u6Öu6 vDv[vtv(v)¸v2âv1w.Gwvw.‘wÀwßw0ôw%x;x*Wx:‚x!½x*ßx. ! y9yQybyy>‘yÐy.ïy z3?zFsz<ºz,÷z${:{:Z{2•{FÈ{9|bI|(¬|,Õ|(}-+}hY}2Â}õ}0~9D~=~~.¼~6ë~"->>l5«$á+€72€=j€J¨€$ó€6xO8È,‚T.‚+ƒ‚%¯‚IÕ‚(ƒJHƒM“ƒ5áƒ@„LX„I¥„=ï„[-…Q‰…JÛ…9&†N`†¯†;φ> ‡J‡9d‡4ž‡!Ó‡)õ‡'ˆ|Gˆ-Ĉ#òˆ8‰.O‰.~‰B­‰1ð‰$"Š&GŠ%nŠ-”Š/Š;òŠ/.‹[^‹#º‹:Þ‹Œ"7Œ@ZŒ›Œ5ªŒ,àŒ2 2@,s; %ÜBŽ(EŽnŽ=…ŽÃŽ'⎠! B%NhI·3>5<tL±Uþ>T‘2“‘-Æ‘4ô‘/)’/Y’.‰’.¸’#ç’# “9/“>i“ ¨“JÉ“$”/9”+i”/•”5Å”6û”#2•BV•0™•%Ê•)ð•@–$[–=€–G¾–A—.H—1w—]©—;˜RC˜7–˜OΘ!™D@™F…™#Ì™9ð™;*š9fš' š/Èš2øš?+›=k›5©›@ß›9 œ>Zœ2™œ4Ìœ135J\€CÝC!ž:ežl žI Ÿ=WŸ>•ŸdÔŸ.9 9h U¢ Uø /N¡5~¡>´¡<ó¡<0¢Fm¢´¢SÇ¢i£`…£Kæ£.2¤'a¤‰¤5§¤ݤ&拉,6¥0c¥&”¥A»¥ý¥¦D ¦ N¦[¦>v¦6µ¦Dì¦>1§-p§>ž§PݧM.¨|¨ —¨f¸¨C©@c©0¤©7Õ©8 ª)FªFpª2·ª2êªA«A_«)¡«ZË«L&¬+s¬IŸ¬9é¬"#­&F­"m­"­&³­JÚ­L%®8r®3«®Cß®)#¯M¯d¯(w¯* ¯$˯Nð¯R?°O’°Nâ°N1±[€±6ܱ.²B²/b²H’²@Û²3³5P³.†³1µ³Oç³&7´^´q´†´3™´4Í´'µ*µZJµ"¥µ_ȵ3(¶I\¶=¦¶,ä¶U·>g·D¦·8ë·8$¸8]¸5–¸-̸Kú¸F¹,Z¹)‡¹)±¹0Û¹8 º1Eº9wºc±º(»>»1^»4»>Å»=¼"B¼+e¼*‘¼D¼¼'½-)½4W½,Œ½)¹½9ã½"¾+@¾*l¾'—¾H¿¾L¿BU¿$˜¿,½¿Kê¿-6À'dÀ&ŒÀ ³À"ÔÀ=÷ÀA5Á@wÁ9¸Á#òÁDÂE[Âd¡ÂdÃAkÃ5­Ã(ãÃY ÄRfÄ0¹Ä?êÄ6*ÅJaÅ$¬Å6ÑÅ[ÆXdÆK½ÆZ ÇSdÇZ¸ÇXÈSlÈXÀÈ>É@XÉ\™ÉAöÉD8ÊU}ÊgÓÊS;ËSËHãËH,Ì>uÌ ! ´Ì ¿ÌËÌHßÌR(ÍR{Í7ÎÍ-Î/4ÎLdÎF±ÎøÎ` ! ÏkÏ7‚Ï8ºÏEóÏ9Ð(WÐJ€ÐNËÐ8Ñ<SÑIÑ8ÚÑ3Ò8GÒ/€ÒA°ÒGòÒE:Ó9€ÓGºÓdÔMgÔ-µÔVãÔ:ÕFQÕ2˜Õ4ËÕ<Ö!=Ö1_Ö1‘Ö ! ÃÖÎÖëÖ6 ×RB× •×6¶×?í×7-Ø#e؉ØعØ2ÙØ2 Ù?Ù_Ù+{Ù§Ù!ÂÙäÙ*Ú6+Ú/bÚ’Ú°ÚÎÚ(èÚ+ÛA=Û+Û«Û?ºÛ7úÛ32Ü2fÜ5™ÜOÏÜQÝ*qÝ$œÝKÁÝ/ Þ=ÞCZÞžÞC¸ÞGüÞ]Dß\¢ßCÿßCà Uà0và=§à(åàDáBSáE–áFÜáL#âEpâb¶âbãG|ãVÄã3ä>Oä;ŽäQÊä>å>[å<šå+×å3æ,7æ dæ9…æ¿æÞæ7ýæ&5ç'\ç„ç&¢çÉçVàç!7è3Yè*è*¸è"ãèSé"Zé}éZ™éUôéJêiê‡êê³ê1Éê!ûê,ëBJëQë!ßë2ì24ìMgì%µìÛì8úì3í(Sí.|í@«í0ìíIîQgîQ¹îF ï:Rï4ï!ÂïEäï:*ð2eð˜ð'·ðßð-ÿð-ñKJñM–ñLäñh1ò+šòJÆò;óCMóS‘ó4åó-ô6Hô0ô<°ô'íô2õ(Hõqõ‰õG¢õ0êõKö4gö1œö?ÎöV÷Be÷B¨÷$ë÷9ø-Jø4xø4­øIâø+,ùLXùK¥ù:ñù=,úEjúA°ú&òú%û%?ûaeû5ÇûZýûXü%kü2‘ü*Äü9ïü4)ý3^ý%’ý%¸ýAÞý* þbKþ)®þ>Øþ8ÿ=Pÿ@Žÿ3Ïÿ6L:,‡7´1ìEld@ÑeŠxIbMN°Jÿ/J4z-¯BÝ* !K<mAª,ìA&[$‚*§2Ò &<P5_.•/Ä>ô;3 o9y0³!ä) @0 'q B™ 3Ü ' ! /8 ! <h ! #¥ ! >É ! + *4 :_ Hš -ã : .L 6{ 2² ]å C ^ +y '¥ *Í .ø 'D)c"¨ Ë(ìw!4¯4ä4$NUsOÉGJaD¬ñ5 9C5}:³Lî5;Jq7¼DôB9D|BÁA?F4†5»Mñ"?3b4–Ë=ê1(2ZlhúccBÇ7 ! GB-Š6¸:ï!*(L'u'$Å+ê:TQK¦òD5W2ÀgØ+@!l!Ž-°IÞ(3F3zD®<óN0@<À0ý3. 3b R– Fé 00!Ja!F¬!Jó!I>"3ˆ"A¼"Aþ"I@#MŠ#NØ#A'$Hi$_²$Z%4m%1¢%3Ô%0&9& X&y&3–&Ê&?ç&p''6˜'PÏ'. (O(o(ˆ("¡(LÄ(J)N\)]«)1 *>;*<z*/·*8ç*J +Kk+I·+T,>V,<•,DÒ,;-;S-D-;Ô-;.9L.M†.MÔ.N"/Mq/N¿/M0N\0N«0aú0_\1-¼1ê1"2#2@B25ƒ27¹2(ñ2%3@3ET3.š3BÉ32 4H?46ˆ43¿4&ó4)5(D55m5"£5+Æ53ò53&61Z61Œ6)¾6-è672(71[7,72º7Gí7<58Jr8'½8&å82 99?9My9QÇ9=:/W:3‡:»:*Ú:L;8R;4‹;OÀ;<%.<T<4s<À¨<i=‡=O>ie>OÏ>K?Nk?=º?5ø?A.@*p@N›@Uê@@ARWA?ªA0êAB(4BC]B9¡B9ÛBQC<gC3¤CØCñC D$D?DXDpDŠD£D½DÖDðD E$E?E^EwEE¢EÁEÛEöEF)FAF9`FPšF\ëF=HG@†G%ÇG7íG(%HKNH?šH3ÚH`I_oIfÏI;6J2rJP¥J7öJ3.K2bK4•K3ÊK2þK31L3eL™L6¹L_ðLKPMiœMbN2iN3œNCÐN‚O<—O€ÔO4UPDŠPkÏP?;Qd{QŠàQ@kR8¬R@åR3&S0ZS'‹S/³SãSBôS:7TrTŽT9¬T5æTUUUrU;ÈU=VcBV*¦VqÑVLCWTW4åWZX3uX)©XÓX*îX"Y/o;o»oÕoéo6p28p@kp:¬p8çp9 q=Zq<˜qCÕq>r=XrF–r6ÝrAsJVsI¡sAësE-tCst%·t7Ýtu^3u3’u5Æu9üuJ6vOv9Ñv0 w8|?[|.›|)Ê|9ô|1.}5`}>–}Õ}ô}: ~LF~7“~OË~#e?/¥5Õ' €&3€Z€z€˜€!²€=Ô€.&Ah…'™'ÁVé+@‚"l‚‚©‚0½‚9î‚'(ƒPƒ+nƒšƒ.´ƒ(ãƒ% „M2„<€„*½„Rè„O;…$‹…°…È…!à…,†-/†.]†0Œ†"½†Cà†E$‡j‡ˆ‡¤‡;¿‡'û‡F#ˆjˆB„ˆCLj* ‰6‰.J‰;y‰7µ‰í‰$Š$(ŠMŠ.dŠ@“Š#ÔŠ2øŠ1+‹-]‹!‹‹­‹-Ê‹"ø‹Œ+;ŒgŒ$zŒOŸŒïŒ-Y<1–?ÈAŽ7JŽ4‚Ž:·Ž òŽ0ÿŽ90j‚-Ÿ:Í=3FGz*Â3íD!‘2f‘#™‘"½‘(à‘D ’(N’$w’*œ’(Ç’ð’3“S9“J“CØ“J”Cg”P«”Iü”%F•:l• §•$È•Bí•E0–>v–0µ–!æ–1—:— Q—qr—Uä—:˜S˜Yn˜=Ș2™9™(V™™1ÿ™L1š7~š4¶š=ëš8)›@b›<£›Rà›3œ&Nœ/uœ8¥œ0ÞœG W)x.¢$Ñ/ö&ž7Fž^~ž<Ýž;Ÿ3VŸ.ŠŸK¹Ÿ1 67 ?n \®  ¡1¡2Q¡>„¡>ᢢ5¢9R¢:Œ¢Ç¢<ç¢1$£@V£(—£2À£Hó£4<¤Dq¤¶¤8Ó¤* ¥27¥9j¥4¤¥IÙ¥6#¦6Z¦D‘¦/Ö¦,§:3§Cn§b²§.¨&D¨Ck¨+¯¨(Û¨Y©a^©_À©j ªI‹ªiÕªM?«)«&·«-Þ«) ¬O6¬T†¬jÛ¬8F­u­%õ­7®6S®8Š®7îNû®%J¯$p¯1•¯0ǯEø¯)>°@h°L©°Eö°\<±#™±½±رò±²C ²Dd²4©²(Þ²=³,E³2r³5¥³6Û³;´N´c´|´$Ž´P³´.µ83µ'lµ>”µÓµ*éµ$¶69¶'p¶R˜¶,ë¶N·&g·1Ž·À·KÓ· ¸,¸F4¸&{¸,¢¸)ϸ5ù¸7/¹Ag¹+©¹Õ¹Jô¹G?º"‡º ªº@˺. »;» ?»1I»7{»-³»3á»P¼+f¼’¼&²¼8Ù¼G½=Z½9˜½9Ò½F ¾9S¾=¾8˾"¿#'¿3K¿/¿-¯¿-Ý¿? À4KÀ4€À/µÀ,åÀ)Á<Á#LÁ&pÁ—Á'®Á&ÖÁýÁ%ÂAÂ\ ! w ‚ÂKŠä ˜9 à J XÚ1¤ î º Ì…¢wÛf;­ šÎ 4p ! #k€§*]6 ú륊!¯ Øn¸;Ox ¦ @IT ! èÐ p yÖâÍ ©*Ôˆ # ! ¦†»¯«P¢'Ü ! Kß„‹ÝÌÐ+õ­#ê£  6ÃA½Ò çö5 Ü Ü‰ €Ø ¾¿ìlЧ ÏuÙ8tÄa  ! k;ï 2§: 7=u ¯"_»ü å²ýIV1® ! o ² Ñ Ôù~—#  <–ª% 1 "þ «¿d"dG Xד…Àk›Œ h5êÂL¡1ETæµÁí Í 'zîþ ÇÐÐ ! Q#B Ü {"À–N—6"‘«Îç W € ! àÙ2ùû¶úñ (¨PÐ ð§ Í+6ät#¯]¨°Õ ! °é ·2‰U¸Ý®à¨TÛˆÚzID vÊtûÖø¹gÇ‹p >²H æÿ–Šš²Pñ Ðä±lÇtí„ëL–Nï¾! ¥j Ž)y J F84g94fv ÕÀ>ø a æ˜Jhµ©Õ ! Ë[l“¨bL=S ¾ÝËVº + àóÖo× Ñ\Q ë Qõ( ! ” å&÷̱‡LX«{&šê ,Ú ¤IÒH¤ ! ž ñ…&vZ AøþÀôfî° ! NÒ8=¥…æ¦B|WI§’S³È#®K“»= ƒaF6?</í Ä8 ~²Â«\â¼Ø;ˆ ! ÿJkDiq ! XvY ! ÌwÏ IÎt  ! ká “ £E 2?UÙõ<%7’Þó Àgßáÿ €{´ß I ! }i@NZ”® ˆ:)¡~§Ÿ ž:ñÏY ‘âœ8¶ N„ ý\ì[´^ohôð‚ ! §E‚u” ³5ôt§Âý Ÿ8 útpL?€S èî ! åšáó ±ƒ¿ §ì8öGË… )½X‚ÓgÎ ½]Ñ X Nô ±NÞ dn_ _ ! ¡ !  =<ܽðô Ø‹‡¢ƒGÊ ™ öOäÔ­ Q3ÐI ¡u¯zþ¨è÷ Gr{‹Ü~ZùWWÃG‘z€ upmq—ø\x¹$"ƒ‚ çN ã%;"[Jø U 6sÚ%ð ! ! \ŠBýa Ê˜é ƒ !  ÕBË-3¦ ²Chø‡³„$ Xeò<| G-‚æW ! qI U× ! —° ! î -"¨¾=Ñ ­rðtýu  Á _ã šn ga“eÃÅý V  B ! LblëæÍc~ vJŸ4­UÔ¼Íü ! Ùèó ! 0ÆÝ ! hp*Ð<'šéâôúë` .oç™4^é©·ùi©m‡@þ$øãüØ çŒncû.Ƭô$Á/¢i föÃã+Í- _Q¿`µ´*Ë­ûKdi ß4D.àøºFë ž ØY}îÅÖ$j’¾#ÔÜ Éð ƒï—ÿŽ'ø¾Ç Œ»Ì ! ¾ƒbå ! b EDè© ÓcŽ·5F‰Œ·É ! ¾Á@ ó ð÷g ! &ÚEdˆ/¶ Ÿfb ¬$å Xð¥Á˜ ! u >qs 9øQ ñ –ÓDZވ‹¡ /ºù Æ9Ôu [y/— ! :g !  ~⯬û( { ©š ®L*»G E¥Qà g–àÙo#1:лڹ™c¡ ˆÃhèS+w ¾±” 2Y EŽ:i‰xžå¬§aY!êMFã>!« ! Œøë0Ê,ŸkÛ:¾|r  H²]©^ — Û èœBrýÏ[»¹Ùs“¥M³h• Ç-4¢cž7 ! KZ m ‡ÓVRÕ µ*\Šj; jH{h Œ ! ßÑ^Èø‹š#1߈¿ê … ûã ! ¬õVÕ 9ÏnöÄ. éw½AÆõï™\ÎHP(ËþPüõ ¤^œ#×229è e·Lç ! aÑ» ðXªïœÎì˜èé \ × 'ô)7W‡E#v ì©û/"øÏíAñ;ý°½áÍ(Õ8ZEÕ F ˆß èk°F#5 : Ð@¿aM6ó¦r5MBF3°. òÏ•µ -!ô&q™ùª˜ÿ­Ç†½•G«Ï ! É+õ 5 ! ôZH¹R± ! G> Ñ3( ê·ÿBRx 5böGÎNµ‡º ªž©“-ú¦b<›ý— êŽêŠ| Žœ ã ! y~ £ ! %Pa£Xù ê÷M {V \Òè›S`GÍ  „¤pSöÒÁÁÁ " >~žé}ÄwRɘ´‡ ßÑ 8%¾^”?ùe æ ! ¸„ +u/~ŠqÍSâ ! ± &œ ᛌz‹ºl ] ! ¾Ÿà }V1‰Ÿý ! ^oŸÖ2£ŒcÆÖAð ! B´§¢Ú ! ŠuÕ=•ÉÒÐ{Á†OÃéâc -40¿I?íº1¡µþ´[ »«£ù,/¦ª& íÒ ÁŽ  ñ€ £ ²C,)žl Î{Ô ~F›§9gÇBj ! {² ñÿ ÔãÂ=n‰ OígŸ¡61« |¼'„M ! ò<>¯€¯ÂÏžB ›ŠÏ cª ·1g)W¹‘Ü„ó'S·âm+U ww ég7³à ¼ ‚¥~¿žÙfÕ»– “a ×3 ! ä n³EÝd­ ý‚K ÅF ^Lß1¸H À ÎMnéeSOŒ c _,æ1̆æ„^ C møA 0†˜g g •Ï¼ë× € òƒ~ ÂïW¬©ŒÚq` ÒŒ ¦C-  Ü þA1oÞ€‰oÎ ! ý P ! ðäs rU~aP‡Tôݶk Qÿ°ÐàB âh‡I p dcx ! j,›„¡}:?ã{ ï Áf†#DTçë‚ÉPÆsõ Z”¦GRªáùÆ f¸?û<¤ÇG ! % 'A .–N>*£®|˜ÍÿOø ôùƒ£ X’ †åӭ“Ǧ: !  ,N ! Ú¸í ¶ ºú ¹@Þ G $) ’zÅ ðÑ8Ù’Knš°$ñd É Ki }Ì Q­T #a§ { þŠ.3Œp‰ØlÕ}]3Gjj̬ ›SN¸í úE ! @ ° »V¬hl²_¸ ! ,z²3RNä ‰ M ­mó-;ªÅŸ˜ ƒÎqê¿ ÆÉiФѵëYD„Áó]•96–” ! Æ P4ÒDˆ,O ‰‚˜ Cá!Q Cu” ¡ Ñ&©> ק*¬+ ! ÈòU¯¨¹; 2þîsZF 2ì ! ¤ ¯ Â=<§ ÀŸ«”Ö À°uY˜€[ñê cH É×$ú ¼ ! ´‹ÙsóO1ϳ õjÖf“ÓÚb{ùšg›eÈ£Áà†ãƒ6„‘ÝSÖVµ66N G«í¹© — ! wÞ ! ëÍ%Õ W`ñ *‹ n£U3 sjþtŸIAÿ5Ç“ !  ú =5¥·XÑè# ‘(¿§=t1âúYÙ£  ! » cM¤Û°@ÊÔ ßÜ#Å õ¨u×Ì Yð/9Ÿ]^ä ì”*ºÏ wÑD ðII Ó· å‡ýð( ÿBÖ ö#ì‹wdTVyÞ¥ !9 : Øx;¾œÔ™ Jñ'0rªDó A¦Þîå"Âß5! ýËø —ëp’ÀÇý(‡l®. ! –­[Êw&ÈØ•Älx3YŽªêc˧á²:úC,O ? úÌ|]z  eU˜ ™È @ ! îâJ n !ÊÛ ‚ a¨F [½®Ó©g=”ÏHä ¯Ý$ï :Ø° ò¿?y/š 3é f ˆ[¬ íÊ ¼5 áÇô©ÈtµÈë %]•Åì¶vñB×Ü•  ! ê ! VŒ\!v'u8´/À CÙQ(/ êio'¸cÅ„¦‰ý´l i‰[m©F·¿äÓDE>óSñI¸ËmkA&%Lt ï'wZã¶ Ä Wx¤kAé¸y‰  ç?·XBX ÛP õùÈ Ú ä|ç. ! ‡À ! Ó?̾ }϶ Ä ¦ãÛ"2í ¡T<Ó…–Pθ ¯¼ ¬z– OΟ`Ås„ví*ô … …ÜÑ7ë ¿7· ²K \1ýø1µéŸŠ ! hN Ö k76 ! A<ZâëGC:‰j¼’2 „ÿâE} HS{“Äã—› ¸ aÊ‚y ! §Q9ˆ¶n ‡Ì¼wqº7W  ’ i@¤ðs†( ÝrôìâÅØÉ¡ÁÉ?¿ÇÐ-Ì j´õ3P¶”Mg‹^ML\$ œ£uÂè74 m4dÑ•x ÖÔj<Qx k¡îY”ÑfžJû ‘ë¹ xÍÐ ¬Áí,´ Mà 3± zþ ! º dbeC·ÉÑL z  ØP‚_ m ¦,ÏýCŽ ÿ–üiKÇ[1 -vëûÒ ˜Êi ! \]FN8n±wb W"ã܃Þ]5.R ·¦Øõ² ™ |Òsj¹*ZÜÞå¸6ù ÀKs-/ì Ko)©…yb7< ¹ ¼%÷]ò ì < ½öhñ÷W¹¬ G7}$e‘¯D?u 7œ ¸ïÌ‚øøU »t‹ó°fW ûÇ22Ûì 2 Uß ! N9]±å>ZIÏ ¥ v ˆ Ù BöÙÈ ! :& ! íïÔØ B Æù (› 3bîŒìND : š¸¬~a ! › ÔáÁÛÃR ! \ ! *Ÿ¦Ä; ÷”‘‡F ! ?¼RsÀ µ ! ô ! ×N×"â;X‘– Ó.5ZuN Ë^µ?Õo»…ê½ï‡ ! G)¨ ‡ í†_г U ¡öÇ" ¨µ¸1 öçÅ⺠&¬Vqiîö™ìå Û'Ý$´ ! ÉO½5ÅvB(l ! ­ï³%&‚.©ÛðÄê™à9Þ ªb ! æ%›eÃ-´0“ ÷– ‡·ú ò­… O£n¸›‰ Ø@š s9û‡&ë÷RpÄ—/Þ ¸+ˆbªƒ &œTŠ |"…ç)„ ü´ ! ì4wD òMæq% Ò ñÑ Ì ¨Ó  û ! b*î¼? ˆ®æ€ÏI òü.òVåôË l.ÊÜ@L0 ee(Ý-¡eó‚K‹×zÏ2 0.þ ȵ¸ Å’åŠ ) ?êר½éÆ„ÔœùJ ! Ê µÚ÷ ’¤ ¯³9ˆŠf¥ ! Òx"Õ  ßÑ ! ¡`韡FÍ£8þ‘»Ä›ˆÓß_M ¾ÚagÞòAŸ Ý0œ­Ig°ý´ƒØ  Uàg! fcJŽy¬ÜØxJ  G Vt ! Å¶çœ  –^ ! »×²k•[ %k €Lçà% eŒ `ø» ! uK¿ ù†4Ñ«kíM Á¼¨Ö Äò=®h '²j œŸ Quk-íJv•P`ºçË)óâwž|ªŠ–5Ã"Î Ál¥Ié ! L íœX ! Ú¹ ! n­½ ˇ % ¼ õìû”\g %¢Yð6 «  t›A‡äïù Ùhaù(\ — [tµ?‡ö[”Ï1(gõù ¨/ õtû Ô ! $3ÝYárÂvì ½í;õõcÕöÔ X ú ! Ad ! ãà ! C¶† ±=4¸§ÉÒ ! éXid øyÂ$´âm®'Ž¨SÂ~þôÛ Àºm]ÓO/éð²H¦;ƒ Û yjbs~ÛJi!ÿ¾ ³öÒw¿Æ•¢©^ÅŲj‰@C¶¯mÓ#Y`R™Üµ @<-ûMÞÃ[ ! Y ïŸ+b.½  ‹ jü[SÑ ßn*Öc[{L'm^ † ! X¤~ì¦s ! V_ `¥¼xn ! ü¶‚o vC­ï2; ! %E»  `÷­IH+^f ¼{Õ x„} ãȘ¨ ! Wì– e‚úQBæ X©›Ö4 3"tÂZ¯Ä¶Î Mñ[ä 2ì  nõãì¬> ! Q£³ ! ¬­=áÕL™Â{||ø«² ! Ö‚Ö¹ Ï#Qx—(´][™ ! , µ n>ÚRjWKP*<í„ó_÷³ áé¢ÔÚ³–•{YCäê' $_×ÀR Ÿ±"zê Ž)•á÷þ¨5Jæ½Þøàg}T‹Õ¢%²ZŽ erâ±!+Å¥x³zùq ̾h± oä^!RlÝ Åq |Cȉ¤²Q °ô_]àm,ìW C 'ˆ 7Á e ! (ù¡hå 8Ô5 Ü' 3Ì µËÓèéÖ‚\Žù+3YÉ ! $˜Py6 PBšÏ© ! Çÿ„ n Ëlr]ß³¢ û->‹ ’Ä ¹”¯… ! ¼CE qeå$j nþ tÈ#à@ª ÄÆdù²ww m&¡B›`æ  ¨®H¦ \v˜} éµE?¼à b ï ‘ ˆ  z ! u ! ¾ÉŽ i> §O@_)¶ Ò ”_Bºvàdí ! cà3óå•Ça‡» {:éоhÕ»: ã]5 ³Y·0“ÜH‹Èn”J¸½>Ò|á ! K’Äšpß þ« Šèp N¢Øß)îh…ž ! ºöZÜü{8¬ËÖ8ã!âE?ñ:“–Äò <â E·¾£æ‚¥Æ² ?h;e;~Àeüª½«Ûp"¹Ë ôK ! ~ ! ! Ñœ³ÂÜ«c÷ ! |fTz‘Þ& ^2Ò “ì»S f)˜Ï;W%ª y 8¤Í±'q ! æfG8 êîE ¥ß2¥“}t¦V÷¢ °@ Ø–PY~|¹á[&Îý“ѱ—¸ ˆñ‚ÅÙ8Ù ! I1w£Zf.#’,¡œ‰ ˆ@·ÿŠ“žY¹»tfØRîù($'š r¤¤Ê^µ}r6Îü{]ªJì¨B ); H²µ ! íî†Äš¤V p« A‰×Ämq‘ J7ê|¨ ÖÒÕ·0A8 ! ö_RÂ) qý¼ûÿ ! ³l ! Ý D}H õD˜v8¶ÿ€Zk Àëñ —›Ž š# >Tš ’v  Ç új‰bÅ žÿ0U™< «$E “†Ù¤Ë­ ! õ LÆ ! u& Q P Z /Bv7U_±IÝ6)“ ¢su=}$NŒk΀ ‚æ ±M·È . ÏZ ! 7Ód©”à Oö Uß/ëƒvÄ ! ­”‘Ø ßFJ£|:7; ðí¼9 ¯ ! pFZÔ D ÙH ! TÚ‘¹], ¿ !  !¬Ùû?®Z}* 1o S$¤¦ ™ ÷7 š(T­rõ ! 78£È* ] ,è¿ ¤ÕlãC — ð -·É ! ê` ×û5‘~{TÝ¢ó ÿ±q{ ! S§4kÛµlÎÌv„ó ! €­3‰ŽÚÓ ` »U ”Ù{c”Ý2 ¸ %  ! ;*CÕ„´ s£0ʾ* ! ì¬S´€|…¿¹á ›eæ¯QÆ™~ÂÊ× ê ! l –X °zK+™x; r³ áf ÃÙ Ãx¡ÁåJ À°0³ƒ:ǧ¶7þüÁN‰x6Íü ® Ú¨ œ¯f^Y ÍËQ ,KÜ«9â  öó= ¦¥¶ ! ý™¼-ÍRÔ:Ób`0Ê•ÿî¯ MB‰2©3 Úã. r þ :CÀ±Õ~ ! äªTYme!j.àé­ ¸)Ì­­úÿ-‘Wàîp"3xÖ cÀÂâp ! ·ÓQS×Þ‡wö'² / K* ¾ /ã³=†q Éü ! y3Ñ°« ! 9à ´7IÝ ! úþ ñ f À ÅzJËý¥7 D½‹ú纀Äþú—G¿- Qd? ± Ù¿ë ;y ÿ,0 vTî÷ƒ B°!ŸßÄOèw±s “ÚÄqu½€,y½4 ª ! r à  l‡áçïFÕ+¡1wØÊÈ›· M] ý º…  àý ÛTÙ'mT d:Z ž;¢—Ü΋K ‹ ! ¨ÿ  г`Ö!WžÌõcâ J­ *öÔ’sáx OÖbe Ÿõ}0 „ ;áçHˆ`Ûqov0¡¹è ò ¸ Ç ^’ÃpV •€ªo‘qÉi&Ðá#æ} å†æò¬xêÇÞïî q‘ ! ×ô§ ! •\¼ÏW! Ž¥ žõà)JuYHU¤°¢–…¦÷Zè ! ã\ˆL\dÆû~!ó}çEÐVþ’•¯4X[7G5è" ž›bÓ£r<W2³ñº ! ÛÞXÛx , ëÊØ\‰ñ¤Ò»g •Ám ¢ äþ° ê8 R¢nzÛ æ¥§*¶™5c gˆ <ßH ž¯×¤ÑCv}Bvj ÐUïbäo¹—Œm ʬ›_Ê× !   +Š ï$9\i¿EƒÖ$ œf" ! ó7Ò A ¥ ʃ ¾5uÔÝcû üß|f~ö RÈ s ƈÕ/ @TÙoM¶tåS:\^Õml ߈® K½ %ç1’ ! LsØü «W4úl6 ! pŒ ä– ! *_ÉÐ AeŠŒ “ Ƨy’‚ š‰ ! M 8- 5]Ñû›ŠL<Æ(b } m- —ûõa 2 ! + ´&[Ÿ ! >y=ÄiŽ Ìp ! šo J±ð?D@ gŽ ? ÀO aÀŸü®{‘AFÙN‘¥ ! áD r@e $/nPf×oŽô 'h Ýí˜SIéQ ! H™YÊ r©0~ëŒäUU"\  “Ky([ ‰¢êÖz©&òÔæò`å$•}äâ ;æÆT S…Ì»ëo ! ä[ÇMŒ‡ªùï !  ! í5 )øä]¹ ¾ ! - >VÒ½ ! n¼ä ! 9³ °a MlNŸS ! åù*ªã   † V  – GÏ‹/z9ù‹©’£# ê ž ! ã¥Ë‡´yÉ—îÛè ?¤ªŠ9a®&†¯Ñã“k ºA”Û EÓÇ & Ið" % ! ž×Ó$\¿ k³{W[aÑ<äö ¤ÑóÔ€o®–ÚÖþdûK ! 9Jl…¤Ì¶P²DCi' ! Îty0²4† Hòiƒ VzU¥Ë)_Dï)+'@£(Ò3Ë «@ßëˆäû!ç ! ³žqè aЫ MÍ9aö÷Ž ! h7, ! Z‘ ÊóQ>¹#& 5<R …Ãmxýì€ÉRæ ! ÝVKÝß> `z{ ! ¿ë ! ƒ7 ÛËåJƒ>,R ÈEå…ƒÅFñàJüF¼ ¬uõèTåó‰ “›#*Å eà q0~E¬½:œ q—÷ÔUã(ïL÷'ß ! 5ÍM[=¶ïzdÅk[qNâ} ~ ¶©ôž 5ˆ€ S<” Ø ! ìãÕ5µå²T >Øç ›à Ü «™F…äê ô>Qv Œˆ¿lJÉ· ·N}² ! ® ! ×é .2ViÀMDP ¡® ! ú¸ÀÏd´‘ÁÍŒñµ ! O| ! do§=‚ÅbÏ“„ :*æ^:ÍÝæ Eƒ¼ã’-Žñ ! F° ¨`ƒL¯ ¢ %6 ykD—I6oV ! ôR-“]Ù¢á s Ê ÄqöGOÞ¶¸WŒ‚4Mz ! ài7!½ ½Ì9*N, ! ÆÓ•`tž s G0N%…™ š¼™ ‰ç "°`ª 1­G†lU ú á hcÎT=n/O^ ˜3Û “RÃ2s±8Er ’R˜áÞ.y¬ õ) ! ŽÊA%û·^%&Šò ÷î ¦¹ÜKÚ åK·ÙéØ…Ò,à>Oä»üTwG + Æ ¥º °ü˜Ï à ! ÿ OÐ7¡œ–°Šqð…=ïš—À4‘™lòž/ĸ8®èñ±p?.èB„˜ÓŠñŠž ½Ÿc Ö˜’Á ÙŠÔi ! =b 5† *î<À [ ªC ” ç8Ðï\ÂT˜£ (@§‹ ‹ ùÃkeH Ñþ= ! Å\A Èÿ.|ðÎ ! ÔX^™»íxî ~? ! ‘¼ýs *…D ! (ýÈgRR‹ ! ¢ðƃÇÞò¢}ŒÒ‹ky ﶆŒÔÚÆËwK„ ! F:ý¢+ ! {8¾¢¢E‚!®ªh_ÃÚ TúàOV¤ÞDñ^£D .eO Û†z`ÑX2 çg'Ô ØL© ÈÊÛû …Ó ™¨g’¶+ÎNy Y(š ! ø HÍ ! <^ ¡Ýçá¾wµ§s¯/3 1 ! „øç'ûŽoi‡ Ž1H0 ’ñ‰0 Cj†6ã ´Û! ! u®«Ì  ! Zª¨ IË Ä å|Ý ! / ¤€Š +Ý ÍD™¥ ÏjÄ  ! kÔÓÕÎ} K ˆ÷šôÉ üÊ‹pueœy8ô+¡.uk ! 4¼ !‹y{4¿ ! ]= `¡/ OF ÂîžS¸ú ­¯³I< ! †«3 äÝùZœ”HŽ,œ ! —.ÈXòkoÅÚ\òOUOÒøÁ}a çþ } ! . ¶`û® ½ò Û+ [=šsvŒÇ¦ ? Ç=ýš`^÷+þOw ¬– íy”èæ   #SÍœU¿Wûï_œ:úøŒ|T®¿‰R¶èüS ÁjÛ ! 3nØ ! ´ jHÝ«• Þ ÍœÒoÁÕhr ! 8f…ê­º Ok^bŒÇ” 6¨™a(L Óiï€"ò ! â J׬Jh5Qaº¨KŸòBè²½ mĬcüY&®; B DøÈ o< ±_‡ p+ -9 !€«r]r ¢Í÷É‹± ! ±À°xÿ€çÉLÁ ! TdyÙ Äúp—Þþ´ë9 hûk< ÐŽ þÀ0QƱ = i sá–Øâ  ! ×3•Š ! Ç2‘ÞäÈt‘rË8£-VÖ¢°>4 ! @ @9 ! Bl ™¹ ®„f(Žl—äh6gÊìé ÆÌF• 6À¤µƒ¤,{ã¦ÍóYª¶H7+å• ! . A¿Þ¢ ! ôÖ#×_¦ ! xÎg(Æ® §‡dñ%úVë‚ÿ Ø,º}&»Ú©n v— ÐÿÓ RÅ÷ÚM7ŽüdÈÑíŸ psUñ|+F ¹¡`­ÐP ¬ŒÖµ·Þú6ÆPžS£_Áê¸ÞÈ¥ 4 pHM–AäšüöâRø6 bÍ ß1 Y iUºÚÜ[™Gx¹l—Ë ! Ë®Ûiÿ@ú ! óQ-ü¦ á…>6|;º YVÅ p¨Íå)u›ø"Þ ´WÁÍZ ©· 3òO:‘ ÃsÅ2m/ Üzº ! "Ò\E `Ÿ˜öIt L DêìèÁ?é§Á†á eõ³P$ÎÐ r¨X/;U ! 1Ê ”' × )0~ü“ c ! ° | hÓ‰¡¦.Z{X>îµ a• HXLÚ)_9ΑU¼’]@´A ! @› ! , î IO ! ~2{ Hç ˜§ºL ! qÚ™•? LQc°A Í÷Î ÈCHšo¶ Ë*É Ô¥©îF#l‚«†pX­¯ ® Pë é4>… ÷ùâM_«ý  _ ! Ê- ! ?r ›Fê=&òø ! 5ê¹Qˆp² rbPÅ ! šw (ßó.ð_¾£»ð ' 2V É ýR¬âJœL ´ ש de nðmÌC ! ~õ¿z§÷ ô ¾ á4&WÙÄj’h0†Pæ£tß ! ‚S ˜bÖ ! %|ºt| ºôÒ¯£v ! õ’ 6½@xóÇö”ça E¥9  fW ! ÿù ! GæöWφu æ ŠW=^Q®"¿ ß„ é rG‚GYó©z‘˜S%˜mƒåº¡9p†¾à ] C™É ¥ZÀ$ r  ! / ! ) Òj óòœ&œF½¾ëîXâqÈiž÷ dh !¡ Ú®á, !¶d xKgü Ó ! ÜØ+eó’ LôŒb´t ! )íü Êõ³ã Pî’Aï è\ Zƒª;A ! Œ“sÎ ëº] zòcCjæŸÿ¥Ì à¢v•bÀ32¹ ’0ÀŠÌì—΃ ! 4h ! ŽU¦k¼¿d"D  ³<Ý/ö ! ,ç AžË—€Þ¹•çø)a'C”d}&D_ wË úEšÈJ‹@t„(PF;Iû1ƒÉþ3‹ íè ^ÌÒð0 ! Cn ! 4p f¼aÙ ! †¢ ëE ÷±$ ! Õ‰Æ< ŠŠ ܵί´jÉ€Ò6› Ÿ²w ! Í  èmjP +nC ! KX\ n m  ! “¬ ! hòx,þ÷‡éˆo =Å…t¾ »q-úœž| io4M ! y ` ! * ! ‚ T1 ! Z`B¦wRÝ Y«»‡ ÖÆ ! üܪÌÐÙ ;oÜru8å _0IÕÜ)yö £]üf ! à ˜ ´ é6$ð SÔz 9›WTË f0wî³k ! ‘¨ mcЪœ· ! Éþ>È„z•ŽÂ±½4–$ ðm ! [ –¯D¨# ¤ Y.¯V Æ >@AÞ|Ç ! d !ìv0íN rN·:Vզ݄€T+#c ‚ `ôÏ7 tÌ>1%ÛÊ ! For bug reporting instructions, please see: *************** write_c_file - output name is %s, prefix *** 1559,1565 **** %d destructors found %d exits recorded for loop %d (having %d exits)%d frame table found %d frame tables found ! %d least significant bits of %s are ignored%i-bit mode not compiled in%q#D conflicts with a previous declaration%q#D has incomplete type%q#D hides constructor for %q#T%q#D is a static data member; it can only be initialized at its definition%q#D is not a function template%q#D is not a non-static data member of %qT%q#D is not a valid template argument for type %qT because a reference variable does not have a constant address%q#D is not const%q#D is volatile%q#D not declared in class%q#D redeclared as different kind of symbol%q#T has no user-provided default constructor%q#T has pointer data members%q#T has virtual base classes%q#T has virtual functions and accessible non-virtual destructor%q#T is not a class%q#T is not a class or a namespace%q#T is not a template%q#T is not a valid type for a template non-type parameter%q#T only defines a private destructor and has no friends%q#T only defines private constructors and has no friends%q#T used where a %qT was expected%q#T used where a floating point value was expected%q#T was previously declared here%q+#D cannot be declared%q+#D cannot be overloaded%q+#D explicitly defaulted here%q+D aliased to external symbol %qE%q+D aliased to undefined symbol %qE%q+D already declared with dllexport attribute: dllimport ignored%q+D declared as a friend%q+D declared to take const reference, but implicit declaration would take non-const%q+D declared with an exception specification%q+D defined both normally and as %qE attribute%q+D invalid in %q#T%q+D is static but declared in inline function %qD which is not static%q+D is usually a function%q+D redeclared as different kind of symbol%q+D redeclared inline with % attribute%q+D redeclared inline without % attribute%q+D redeclared without dllimport attribute after being referenced with dll linkage%q+D redeclared without dllimport attribute: previous dllimport ignored%q+D takes only zero or two arguments%q+D used prior to declaration%q+E is not a constant expression%q+F declared % but never defined%q+F used but never defined%q+T has a previous declaration here%q+T is not literal because:%qD appears more than once in data clauses%qD attribute directive ignored%qD attribute is meaningless since members of the anonymous namespace get local symbols%qD attribute requires a single NTBS argument%qD called in a constant expression%qD cannot appear in a constant-expression%qD cannot be defaulted%qD cannot have default arguments%qD changed semantics in GCC 4.4%qD conflicts with used function%qD declared % outside its class%qD declared as a % field%qD declared as a % parameter%qD declared as a % type%qD declared as a % variable%qD declared as a non-parameter%qD declared as an % field%qD declared as an % parameter%qD declared as an % type%qD declared as an % variable%qD declared as reference but not initialized%qD declared here%qD does not have integral or enumeration type%qD has a previous declaration here%qD has already been defined%qD has invalid argument list%qD has the same name as the class in which it is declared%qD is a namespace%qD is already a friend of %qT%qD is already a friend of class %qT%qD is already declared in this scope%qD is already defined in %qT%qD is already defined in class %qT%qD is already defined in the class %qT%qD is an enumeration template%qD is both a direct base and an indirect virtual base%qD is initialized with itself%qD is normally a non-static function%qD is not a class or namespace%qD is not a function template%qD is not a member of %qD%qD is not a member of %qT%qD is not a member template function%qD is not a namespace-name%qD is not a static data member of a class template%qD is not a template%qD is not a template function%qD is not a type%qD is not a valid template argument because %qD is a variable, not the address of a variable%qD is not a variable%qD is not a variable in clause %%qD is not a variable in clause %%qD is not a variable in clause %qs%qD is not captured%qD is not compatible with %qD%qD is not declared in %qD%qD is not defined outside of function scope%qD is static but used in inline function %qD which is not static%qD is used uninitialized in this function%qD may be used uninitialized in this function%qD may not be declared as static%qD may not be declared within a namespace%qD must be a non-member function%qD must be a nonstatic member function%qD must be either a non-static member function or a non-member function%qD must have an argument of class or enumerated type%qD must not have variable number of arguments%qD must take %%qD must take either one or two arguments%qD must take either zero or one argument%qD must take exactly one argument%qD must take exactly two arguments%qD not declared%qD not defined%qD redeclared with different access%qD redeclared with different visibility%qD should be initialized%qD should be initialized in the member initialization list%qD should have been declared inside %qD%qD should never be overloaded%qD should return by value%qD used before its definition%qD used in its own initializer%qD used without template parameters%qD was declared % and later %%qD was declared %qs which implies default visibility%qD was declared here%qD was not declared %%qD was not declared in this scope%qD was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation%qD was not initialized with a constant expression%qD was used with no declaration before its definition%qD was used with no prototype before its definition%qE 2.95 vtable-compatibility attribute applies only to C++ classes%qE 2.95 vtable-compatibility attribute applies only when compiling a kext%qE appears more than once in data clauses%qE argument not an identifier%qE attribute allows only an integer constant argument%qE attribute applies only to functions%qE attribute applies only to initialized variables with external linkage%qE attribute argument not a string constant%qE attribute argument not an integer constant%qE attribute argument should be between 0 to 255%qE attribute argument should be between 18 to 255%qE attribute can only be applied to Java class definitions%qE attribute can only be applied to class definitions%qE attribute cannot be specified for local variables%qE attribute directive ignored%qE attribute does not apply to types%qE attribute duplicated%qE attribute follows %qE%qE attribute has no effect%qE attribute has no effect on unit local functions%qE attribute have effect only on public objects%qE attribute ignored%qE attribute ignored because %qT is already defined%qE attribute ignored for %qE%qE attribute ignored for field of type %qT%qE attribute ignored on non-class types%qE attribute ignored on types%qE attribute is not supported for R8C target%qE attribute is not supported on this platform%qE attribute is supported only for SH2A%qE attribute only applies to SH2A%qE attribute only applies to function types%qE attribute only applies to functions%qE attribute only applies to functions, not %s%qE attribute only applies to interrupt functions%qE attribute only applies to variables%qE attribute only applies to variables and functions%qE attribute only applies to variadic functions%qE attribute only available for 32-bit%qE attribute requires a string constant argument%qE attribute requires an integer constant argument%qE attribute requires prototypes with named arguments%qE cannot be used as a function%qE cannot be used as a member pointer, since it is of type %qT%qE declared % after first use%qE declared as function returning a function%qE declared as function returning an array%qE defined as wrong kind of tag%qE does not have class type%qE does not name a type%qE fails to be a typedef or built in type%qE has both % and initializer%qE has invalid type for %%qE has not been declared%qE implies default visibility, but %qD has already been declared with a different visibility%qE in %q#T does not name a type%qE in namespace %qE does not name a type%qE incompatible attribute ignored%qE initialized and declared %%qE is an unrecognized format function type%qE is deprecated%qE is deprecated: %s%qE is neither function nor member function; cannot be declared friend%qE is not a class or namespace%qE is not a class, namespace, or enumeration%qE is not a constant expression%qE is not a template%qE is not a type%qE is not a valid template argument for type %qT%qE is not a valid template argument for type %qT because %qD does not have external linkage%qE is not a valid template argument for type %qT because %qD has no linkage%qE is not a valid template argument for type %qT because it is a pointer%qE is not a valid template argument for type %qT because it is not an lvalue%qE is not a valid template argument for type %qT because it is of type %qT%qE is not a valid template argument for type %qT because of conflicts in cv-qualification%qE is not a valid template argument for type %qT because string literals can never be used in this context%qE is not a valid template argument of type %qT because %qD does not have external linkage%qE is not a valid template argument of type %qT because %qD has no linkage%qE is not a valid template argument of type %qT because %qE is not a variable%qE is not a variable in clause %%qE is not a variable in clause %%qE is not a variable in clause %qs%qE is not an Objective-C class name or alias%qE is not at beginning of declaration%qE is not initialized%qE is not of type %qT%qE is obsolete; g++ vtables are now COM-compatible by default%qE is only allowed in Objective-C dialects%qE is predetermined %qs for %qs%qE is used uninitialized in this function%qE may be used uninitialized in this function%qE may not respond to %<%c%E%>%qE must be % for %%qE needs isa option %s%qE needs unknown isa option%qE redeclared as different kind of symbol%qE redeclared with conflicting %qs attributes%qE undeclared (first use in this function)%qE undeclared here (not in a function)%qT and %qT are in disjoint named address spaces%qT declared with greater visibility than its base %qT%qT declared with greater visibility than the type of its field %qD%qT has a base %qT whose type uses the anonymous namespace%qT has a field %qD whose type uses the anonymous namespace%qT has no member named %qE%qT has no non-static data member named %qD%qT is a variably modified type%qT is already a friend of %qT%qT is an ambiguous base of %qT%qT is an inaccessible base of %qT%qT is not a base of %qT%qT is not a class or namespace%qT is not a class type%qT is not a class, struct, or union type%qT is not a member class template of %qT%qT is not a member of %qT%qT is not a namespace%qT is not a nested class of %qT%qT is not a pointer-to-object type%qT is not a template%qT is not a template type%qT is not an accessible base of %qT%qT is not an enumeration type%qT is promoted to %qT when passed through %<...%>%qT is/uses anonymous type%qT referred to as %qs%qT referred to as enum%qT resolves to %qT, which is is not a class type%qT resolves to %qT, which is not an enumeration type%qV qualifiers cannot be applied to %qT%qs appears to be a misspelled %s handler%qs attribute ignored%qs attribute only applies to functions%qs attribute only applies to variadic functions%qs attribute requires prototypes with named arguments%qs cannot appear in a constant-expression%qs combined with % qualifier for %qE%qs combined with % qualifier for %qE%qs declared as function returning a function%qs declared as function returning an array%qs declared in a non-class scope%qs defined in a non-class scope%qs does not support MIPS16 code%qs expects a constant argument%qs function cannot have arguments%qs function cannot return a value%qs function uses % type specifier without trailing return type%qs function with trailing return type has %qT as its type rather than plain %%qs function with trailing return type not declared with % type specifier%qs has both % and initializer%qs has overflowed%qs initialized and declared %%qs is an invalid argument to -mcpu=%qs is an unknown -save-temps option%qs is deprecated; use -fno-zero-initialized-in-bss%qs is deprecated; use -fstack-check%qs is incompatible with %qs%qs is narrower than values of its type%qs is not a gcov data file%qs is not a valid class name%qs is not a valid option to the preprocessor%qs is not available in VLIW functions%qs is not available in non-VLIW functions%qs is not valid for %qs%qs is version %q.*s, expected version %q.*s%qs must be used with %qs%qs requires a target that provides the %qs instruction%qs requires branch-likely instructions%qs specified for auto variable %qE%qs specified for parameter %qE%qs specified for structure field%qs specified for structure field %qE%qs specified for unnamed parameter%qs tag used in naming %q#T%qs uses dynamic stack allocation%r%s:%d:%R %r%s:%d:%R [ skipping %d instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ] %r%s:%d:%R in constexpr expansion of %qs%r%s:%d:%d:%R %r%s:%d:%d:%R [ skipping %d instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ] %r%s:%d:%d:%R in constexpr expansion of %qs%s%s %s Same as %s.%s %<%s%.*s%> expects a matching %<%T%s%> argument%s %<%s%.*s%> expects a matching %<%s%s%> argument%s %<%s%.*s%> expects argument of type %<%T%s%>, but argument %d has type %qT%s %<%s%.*s%> expects argument of type %<%s%s%>, but argument %d has type %qT%s %qE does not fully implement the %qE protocol%s %qs%s %s %p %d --- 1708,1714 ---- %d destructors found %d exits recorded for loop %d (having %d exits)%d frame table found %d frame tables found ! %d least significant bits of %s are ignored%i-bit mode not compiled in%q#D conflicts with a previous declaration%q#D has incomplete type%q#D hides constructor for %q#T%q#D is a static data member; it can only be initialized at its definition%q#D is not a function template%q#D is not a non-static data member of %qT%q#D is not a valid template argument for type %qT because a reference variable does not have a constant address%q#D is not const%q#D is volatile%q#D not declared in class%q#D redeclared as different kind of symbol%q#T has no user-provided default constructor%q#T has pointer data members%q#T has virtual base classes%q#T has virtual functions and accessible non-virtual destructor%q#T is not a class%q#T is not a class or a namespace%q#T is not a template%q#T is not a valid type for a template non-type parameter%q#T only defines a private destructor and has no friends%q#T only defines private constructors and has no friends%q#T used where a %qT was expected%q#T used where a floating point value was expected%q#T was previously declared here%q+#D cannot be declared%q+#D cannot be overloaded%q+#D explicitly defaulted here%q+D aliased to external symbol %qE%q+D aliased to undefined symbol %qE%q+D already declared with dllexport attribute: dllimport ignored%q+D declared as a friend%q+D declared to take const reference, but implicit declaration would take non-const%q+D declared with an exception specification%q+D defined both normally and as %qE attribute%q+D invalid in %q#T%q+D is static but declared in inline function %qD which is not static%q+D is usually a function%q+D redeclared as different kind of symbol%q+D redeclared inline with % attribute%q+D redeclared inline without % attribute%q+D redeclared without dllimport attribute after being referenced with dll linkage%q+D redeclared without dllimport attribute: previous dllimport ignored%q+D takes only zero or two arguments%q+D used prior to declaration%q+E is not a constant expression%q+F declared % but never defined%q+F used but never defined%q+T has a previous declaration here%q+T is not literal because:%qD appears more than once in data clauses%qD attribute directive ignored%qD attribute is meaningless since members of the anonymous namespace get local symbols%qD attribute requires a single NTBS argument%qD called in a constant expression%qD cannot appear in a constant-expression%qD cannot be defaulted%qD cannot have default arguments%qD changed semantics in GCC 4.4%qD conflicts with used function%qD declared % outside its class%qD declared as a % field%qD declared as a % parameter%qD declared as a % type%qD declared as a % variable%qD declared as a non-parameter%qD declared as an % field%qD declared as an % parameter%qD declared as an % type%qD declared as an % variable%qD declared as reference but not initialized%qD declared here%qD does not have integral or enumeration type%qD has a previous declaration here%qD has already been defined%qD has invalid argument list%qD has the same name as the class in which it is declared%qD is a namespace%qD is already a friend of %qT%qD is already a friend of class %qT%qD is already declared in this scope%qD is already defined in %qT%qD is already defined in class %qT%qD is already defined in the class %qT%qD is an enumeration template%qD is both a direct base and an indirect virtual base%qD is initialized with itself%qD is normally a non-static function%qD is not a class or namespace%qD is not a function template%qD is not a member of %qD%qD is not a member of %qT%qD is not a member template function%qD is not a namespace-name%qD is not a static data member of a class template%qD is not a template%qD is not a template function%qD is not a type%qD is not a valid template argument because %qD is a variable, not the address of a variable%qD is not a variable%qD is not a variable in clause %%qD is not a variable in clause %%qD is not a variable in clause %qs%qD is not captured%qD is not compatible with %qD%qD is not declared in %qD%qD is not defined outside of function scope%qD is static but used in inline function %qD which is not static%qD is used uninitialized in this function%qD may be used uninitialized in this function%qD may not be declared as static%qD may not be declared within a namespace%qD must be a non-member function%qD must be a nonstatic member function%qD must be either a non-static member function or a non-member function%qD must have an argument of class or enumerated type%qD must not have variable number of arguments%qD must take %%qD must take either one or two arguments%qD must take either zero or one argument%qD must take exactly one argument%qD must take exactly two arguments%qD not declared%qD not defined%qD redeclared with different access%qD redeclared with different visibility%qD should be initialized%qD should be initialized in the member initialization list%qD should have been declared inside %qD%qD should never be overloaded%qD should return by value%qD used before its definition%qD used in its own initializer%qD used without template parameters%qD was declared % and later %%qD was declared %qs which implies default visibility%qD was declared here%qD was not declared %%qD was not declared in this scope%qD was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation%qD was not initialized with a constant expression%qD was used with no declaration before its definition%qD was used with no prototype before its definition%qE 2.95 vtable-compatibility attribute applies only to C++ classes%qE 2.95 vtable-compatibility attribute applies only when compiling a kext%qE appears more than once in data clauses%qE argument not an identifier%qE attribute allows only an integer constant argument%qE attribute applies only to functions%qE attribute applies only to initialized variables with external linkage%qE attribute argument not a string constant%qE attribute argument not an integer constant%qE attribute argument should be between 0 to 255%qE attribute argument should be between 18 to 255%qE attribute can only be applied to Java class definitions%qE attribute can only be applied to class definitions%qE attribute cannot be specified for local variables%qE attribute directive ignored%qE attribute does not apply to types%qE attribute duplicated%qE attribute follows %qE%qE attribute has no effect%qE attribute has no effect on unit local functions%qE attribute have effect only on public objects%qE attribute ignored%qE attribute ignored because %qT is already defined%qE attribute ignored for %qE%qE attribute ignored for field of type %qT%qE attribute ignored on non-class types%qE attribute ignored on types%qE attribute is not supported for R8C target%qE attribute is not supported on this platform%qE attribute is supported only for SH2A%qE attribute only applies to SH2A%qE attribute only applies to function types%qE attribute only applies to functions%qE attribute only applies to functions, not %s%qE attribute only applies to interrupt functions%qE attribute only applies to variables%qE attribute only applies to variables and functions%qE attribute only applies to variadic functions%qE attribute only available for 32-bit%qE attribute requires a string constant argument%qE attribute requires an integer constant argument%qE attribute requires prototypes with named arguments%qE cannot be used as a function%qE cannot be used as a member pointer, since it is of type %qT%qE declared % after first use%qE declared as function returning a function%qE declared as function returning an array%qE defined as wrong kind of tag%qE does not have class type%qE does not name a type%qE fails to be a typedef or built in type%qE has both % and initializer%qE has invalid type for %%qE has not been declared%qE implies default visibility, but %qD has already been declared with a different visibility%qE in %q#T does not name a type%qE in namespace %qE does not name a type%qE incompatible attribute ignored%qE initialized and declared %%qE is an unrecognized format function type%qE is deprecated%qE is deprecated: %s%qE is neither function nor member function; cannot be declared friend%qE is not a class or namespace%qE is not a class, namespace, or enumeration%qE is not a constant expression%qE is not a template%qE is not a type%qE is not a valid template argument for type %qT%qE is not a valid template argument for type %qT because %qD does not have external linkage%qE is not a valid template argument for type %qT because %qD has no linkage%qE is not a valid template argument for type %qT because it is a pointer%qE is not a valid template argument for type %qT because it is not an lvalue%qE is not a valid template argument for type %qT because it is of type %qT%qE is not a valid template argument for type %qT because of conflicts in cv-qualification%qE is not a valid template argument for type %qT because string literals can never be used in this context%qE is not a valid template argument of type %qT because %qD does not have external linkage%qE is not a valid template argument of type %qT because %qD has no linkage%qE is not a valid template argument of type %qT because %qE is not a variable%qE is not a variable in clause %%qE is not a variable in clause %%qE is not a variable in clause %qs%qE is not an Objective-C class name or alias%qE is not at beginning of declaration%qE is not initialized%qE is not of type %qT%qE is obsolete; g++ vtables are now COM-compatible by default%qE is only allowed in Objective-C dialects%qE is predetermined %qs for %qs%qE is used uninitialized in this function%qE may be used uninitialized in this function%qE may not respond to %<%c%E%>%qE must be % for %%qE needs isa option %s%qE needs unknown isa option%qE redeclared as different kind of symbol%qE redeclared with conflicting %qs attributes%qE undeclared (first use in this function)%qE undeclared here (not in a function)%qT and %qT are in disjoint named address spaces%qT declared with greater visibility than its base %qT%qT declared with greater visibility than the type of its field %qD%qT has a base %qT whose type uses the anonymous namespace%qT has a field %qD whose type uses the anonymous namespace%qT has no member named %qE%qT has no non-static data member named %qD%qT is a variably modified type%qT is already a friend of %qT%qT is an ambiguous base of %qT%qT is an inaccessible base of %qT%qT is not a base of %qT%qT is not a class or namespace%qT is not a class type%qT is not a class, struct, or union type%qT is not a member class template of %qT%qT is not a member of %qT%qT is not a namespace%qT is not a nested class of %qT%qT is not a pointer-to-object type%qT is not a template%qT is not a template type%qT is not an accessible base of %qT%qT is not an enumeration type%qT is promoted to %qT when passed through %<...%>%qT is/uses anonymous type%qT referred to as %qs%qT referred to as enum%qT resolves to %qT, which is is not a class type%qT resolves to %qT, which is not an enumeration type%qV qualifiers cannot be applied to %qT%qs appears to be a misspelled %s handler%qs attribute ignored%qs attribute only applies to functions%qs attribute only applies to variadic functions%qs attribute requires prototypes with named arguments%qs cannot appear in a constant-expression%qs combined with % qualifier for %qE%qs combined with % qualifier for %qE%qs declared as function returning a function%qs declared as function returning an array%qs declared in a non-class scope%qs defined in a non-class scope%qs does not support MIPS16 code%qs expects a constant argument%qs function cannot have arguments%qs function cannot return a value%qs function uses % type specifier without trailing return type%qs function with trailing return type has %qT as its type rather than plain %%qs function with trailing return type not declared with % type specifier%qs has both % and initializer%qs has overflowed%qs initialized and declared %%qs is an invalid argument to -mcpu=%qs is an unknown -save-temps option%qs is deprecated and has no effect%qs is deprecated; use -fno-zero-initialized-in-bss%qs is deprecated; use -fstack-check%qs is incompatible with %qs%qs is narrower than values of its type%qs is not a gcov data file%qs is not a valid class name%qs is not a valid option to the preprocessor%qs is not available in VLIW functions%qs is not available in non-VLIW functions%qs is not valid for %qs%qs is version %q.*s, expected version %q.*s%qs must be used with %qs%qs requires a target that provides the %qs instruction%qs requires branch-likely instructions%qs specified for auto variable %qE%qs specified for parameter %qE%qs specified for structure field%qs specified for structure field %qE%qs specified for unnamed parameter%qs tag used in naming %q#T%qs uses dynamic stack allocation%r%s:%d:%R %r%s:%d:%R [ skipping %d instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ] %r%s:%d:%R in constexpr expansion of %qs%r%s:%d:%d:%R %r%s:%d:%d:%R [ skipping %d instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ] %r%s:%d:%d:%R in constexpr expansion of %qs%s%s %s Same as %s.%s %<%s%.*s%> expects a matching %<%T%s%> argument%s %<%s%.*s%> expects a matching %<%s%s%> argument%s %<%s%.*s%> expects argument of type %<%T%s%>, but argument %d has type %qT%s %<%s%.*s%> expects argument of type %<%s%s%>, but argument %d has type %qT%s %qE does not fully implement the %qE protocol%s %qs%s %s %p %d *************** write_c_file - output name is %s, prefix *** 1598,1663 **** ''' flag'(' flag'+' flag'-' flag'0' flag'B' operand has multiple bits set'B' operand is not constant'E' modifier'I' flag'O' modifier'^' flag'_' flag'a' flag'assign' property %qs is using bit-field instance variable %qs'atomic' property %qs is using bit-field instance variable %qs'getter' attribute of property %qD conflicts with previous declaration'm' flag'nonatomic' attribute of property %qD conflicts with previous declaration'o' operand is not constant'q' flag'readonly' attribute of property %qD conflicts with previous declaration'setter' attribute of property %qD conflicts with previous declaration(C)(Messages without a matching method signature(a pointer to member can only be formed with %<&%E%>)(an out of class initialization is required)(anonymous namespace)(anonymous)(if this is not what you intended, make sure the function template has already been declared and add <> after the function name here) (if you use %<-fpermissive%> G++ will accept your code)(if you use %<-fpermissive%>, G++ will accept your code, but allowing the use of an undeclared name is deprecated)(near initialization for %qs)(perhaps % was intended)(perhaps a semicolon is missing after the definition of %qT)(so you should pass %qT not %qT to %)(static destructors for %s)(static initializers for %s)(the message is displayed only once per source file) ({anonymous})*** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. ! *this--help argument %q.*s is ambiguous, please be more specific--param inline-unit-growth limit reached--param large-function-growth limit reached--param large-stack-frame-growth limit reached--param max-inline-insns-auto limit reached--param max-inline-insns-single limit reached--resource requires -o-A= Assert the to . Putting '-' before disables the to .-D[=] Define a with as its value. If just is given, is taken to be 1.-E or -x required when input is from standard input-F Add to the end of the main framework include path.-G Put global and static data smaller than bytes into a special section (on some targets).-I Add to the end of the main include path.-I- specified twice-J Put MODULE files in 'directory'.-MF Write dependency output to the given file.-MG may only be used with -M or -MM-MQ Add a MAKE-quoted target.-MT Add an unquoted target.-U Undefine .-Werror=%s: no option -%s-Wformat-contains-nul ignored without -Wformat-Wformat-extra-args ignored without -Wformat-Wformat-nonliteral ignored without -Wformat-Wformat-security ignored without -Wformat-Wformat-y2k ignored without -Wformat-Wformat-zero-length ignored without -Wformat-Wnormalized= Warn about non-normalised Unicode strings.-Xbind-now and -Xbind-lazy are incompatible-bundle not allowed with -dynamiclib-bundle_loader not allowed with -dynamiclib-c or -S required for Ada-c required for gnat2scil-c required for gnat2why-client_name not allowed with -dynamiclib-current_version only allowed with -dynamiclib-f%s and -msdata=%s are incompatible-f%s ignored (not supported for DJGPP) ! -f%s is not supported with CONST16 instructions-f%s not supported: ignored-f%sleading-underscore not supported on this target machine-fPIC and -fpic are not supported in this configuration-fPIC and -mcall-%s are incompatible-fPIC is not supported-fada-spec-parent=unit Dump Ada specs as child units of given parent.-falign-labels=%d is not supported-falign-loops=%d is not supported-fassociative-math disabled; other options take precedence-fblas-matmul-limit= Size of the smallest matrix for which matmul will use BLAS.-fcall-saved-REG is not supported for out registers-fcheck=[...] Specify which runtime checks are to be performed.-fcoarray= Specify which coarray parallelization should be used.-fconst-string-class= Use class for constant strings.-fconstexpr-depth= Specify maximum constexpr recursion depth.-fconvert= The endianness used for unformatted files.-fdata-sections not supported for this target-fdbg-cnt=%s-fdeduce-init-list enable deduction of std::initializer_list for a template type parameter from a brace-enclosed initializer-list.-fdirectives-only is incompatible with -Wunused_macros-fdirectives-only is incompatible with -traditional-femit-class-file should used along with -fsyntax-only-femit-struct-debug-baseonly Aggressive reduced debug info for structs.-femit-struct-debug-detailed= Detailed reduced debug info for structs.-femit-struct-debug-reduced Conservative reduced debug info for structs.-fexcess-precision=standard for Ada-fexcess-precision=standard for C++-fexcess-precision=standard for Fortran-fexcess-precision=standard for Java-fexec-charset= Convert all strings and character constants to character set .-ffixed-line-length- Use n as character line width in fixed mode.-ffp-contract=[off|on|fast] Perform floating-point expression contraction.-ffpe-summary=[...] Print summary of floating point exceptions.-ffpe-trap=[...] Stop on following floating point exceptions.-ffree-line-length- Use n as character line width in free mode.-ffunction-sections not supported for this target-fgo-dump- Dump Go frontend internal information.-fgo-optimize- Turn on optimization passes in the frontend.-fgo-pkgpath= Set Go package path.-fgo-prefix= Set package-specific prefix for exported Go names.-fgo-relative-import-path= Treat a relative import as relative to path.-fhandle-exceptions has been renamed -fexceptions (and is now on by default)-findirect-dispatch is incompatible with -freduced-reflection-finit-character= Initialize local character variables to ASCII value n.-finit-integer= Initialize local integer variables to n.-finit-logical= Initialize local logical variables.-finit-real= Initialize local real variables.-finline-matmul-limit= Specify the size of the largest matrix for which matmul will be inlined.-finput-charset= Specify the default character set for source files.-fira-verbose= Control IRA's level of diagnostic messages.-fjni and -femit-class-file are incompatible-fjni and -femit-class-files are incompatible-fjni is incompatible with -freduced-reflection-fmax-array-constructor= Maximum number of objects in an array constructor.-fmax-identifier-length= Maximum identifier length.-fmax-stack-var-size= Size in bytes of the largest array that will be put on the stack.-fmax-subrecord-length= Maximum length for subrecords.-fno-gnu89-inline is only supported in GNU99 or C99 mode-fno-pretty-templates Do not pretty-print template specializations as the template signature followed by the arguments.-fno-threadsafe-statics Do not generate thread-safe code for initializing local statics.-force_flat_namespace not allowed with -dynamiclib-fpic and -fPIC not supported without -mdsbt on this target-fpic and -mapcs-reent are incompatible-fpic is not supported-fprefetch-loop-arrays is not supported with -Os-fprefetch-loop-arrays not supported for this target-fprefetch-loop-arrays not supported for this target (try -march switches)-frecord-gcc-switches is not supported by the current target-freorder-blocks-and-partition does not support unwind info on this architecture-freorder-blocks-and-partition does not work on this architecture-freorder-blocks-and-partition does not work with exceptions on this architecture-freorder-blocks-and-partition not supported on this architecture-frepo must be used with -c-fsplit-stack does not support 3 register parameters-fsplit-stack does not support fastcall with nested function-fsso-struct=[big-endian|little-endian] Set the default scalar storage order.-fstack-limit- options are ignored with -mfdpic; use -mstack-check-l1-fstack-protector not supported for this target-ftabstop= Distance between tab stops for column reporting.-ftemplate-depth= Specify maximum template instantiation depth.-ftrack-macro-expansion=<0|1|2> Track locations of tokens coming from macro expansion and display them in error messages.-fuse-linker-plugin is not supported in this configuration-fuse-linker-plugin, but %s not found-fvisibility=[private|protected|public|package] Set the default symbol visibility.-fvtable-verify is not supported in this configuration-fwide-exec-charset= Convert all wide strings and character constants to character set .-fwpa and -fltrans are mutually exclusive-g is only supported when using GAS on this processor,-g option disabled-g with -mno-apcs-frame may not give sensible debugging-gnat Specify options to GNAT.-gz is not supported in this configuration-gz=zlib is not supported in this configuration-idirafter Add to the end of the system include path.-iframework Add to the end of the system framework include path.-imacros Accept definition of macros in .-imultilib Set to be the multilib include subdirectory.-include Include the contents of before other files.-install_name only allowed with -dynamiclib-iplugindir option not passed from the gcc driver-iprefix Specify as a prefix for next two options.-iquote Add to the end of the quote include path.-isysroot Set to be the system root directory.-isystem Add to the start of the system include path.-iwithprefix Add to the end of the system include path.-iwithprefixbefore Add to the end of the main include path.-keep_private_externs not allowed with -dynamiclib-m%s not supported in this configuration-m64 requires PowerPC64 architecture, enabling-m64 requires a PowerPC64 cpu-mabi=ABI Generate code that conforms to the specified ABI.-maix64 required: 64-bit computation with 32-bit addressing not yet supported-maix64 requires PowerPC64 architecture remain enabled-malign-functions is obsolete, use -falign-functions-malign-functions=%d is not between 0 and %d-malign-jumps is obsolete, use -falign-jumps-malign-jumps=%d is not between 0 and %d-malign-loops is obsolete, use -falign-loops-malign-loops=%d is not between 0 and %d-malign-power is not supported for 64-bit Darwin; it is incompatible with the installed C and C++ libraries-maltivec=le not allowed for big-endian targets-mapcs-stack-check incompatible with -mno-apcs-frame-march=ARCH Use features of architecture ARCH.-mas100-syntax is incompatible with -gdwarf-masm=intel not supported in this configuration-max-stackframe=%d is not usable, not between 0 and %d-mbackchain -mpacked-stack -mhard-float are not supported in combination-mbig-endian and -mlittle-endian may not be used together-mbranch-cost=%d is not between 0 and 5-mc= must be -mc=tiny, -mc=near, or -mc=far-mclip currently has no effect without -mminmax-mcmodel incompatible with other toc options-mcmodel= is not supported on 32 bit systems-mcorea and -mcoreb can%'t be used together-mcorea should be used with -mmulticore-mcoreb should be used with -mmulticore-mcpu= Use features of and schedule code for given CPU.-mcpu=%s conflicts with -march=%s-mcpu=%s has invalid silicon revision-mcpu=%s is not valid-mcpu=CPU Use features of and optimize for CPU.-mcpu=CPU Use features of and schedule code for given CPU.-mcpu=PROCESSOR Use features of and schedule code for given CPU.-mcpu=m16c Compile code for M16C variants.-mcpu=m32c Compile code for M32C variants.-mcpu=m32cm Compile code for M32CM variants.-mcpu=r8c Compile code for R8C variants.-mdebug= Enable debug output.-memregs= Number of memreg bytes (default: 16, range: 0..16).-mfdpic is not supported, please use a bfin-linux-uclibc target-mfentry isn%'t supported for 32-bit in combination with -fpic-mfloat-abi=hard and VFP-mfloat-abi=soft and -mfloat-abi=hard may not be used together-mfloat-gprs= Select GPR floating point method.-mfpu= Specify FP (sp, dp, sp-lite, dp-lite) (implies -mxilinx-fpu).-mhard-dfp can%'t be used in conjunction with -msoft-float-mhard-float not supported-mincoming-stack-boundary=%d is not between %d and 12-mlong-double-64 not allowed with -m64-mlong-double- Specify size of long double (64 or 128 bits).-mmcu=MCU Select the target MCU.-mmulticore can only be used with BF561-mmultiple is not supported on little endian systems-mno-altivec disables vsx-mno-fentry isn%'t compatible with SEH-mno-serialize-volatile Do not serialize volatile memory references with MEMW instructions.-mpcrel -fPIC is not currently supported on selected cpu-mpic-register= is useless without -fpic-mpointer-size=[no,32,short,64,long] Set the default pointer size.-mpreferred-stack-boundary is not supported for this target-mpreferred-stack-boundary=%d is not between %d and %d-mquad-memory is not available in little endian mode-mquad-memory requires 64-bit mode-mquad-memory-atomic requires 64-bit mode-mrecip requires -ffinite-math or -ffast-math-mrecip requires -fno-trapping-math or -ffast-math-mrecip requires -freciprocal-math or -ffast-math-mregparm is ignored in 64-bit mode-mregparm=%d is not between 0 and %d-mrelax is only supported for RTP PIC-mrelocatable and -mcall-%s are incompatible-mrelocatable and -mno-minimal-toc are incompatible-mrelocatable and -msdata=%s are incompatible-ms2600 is used without -ms-msdata=%s and -mcall-%s are incompatible-msecure-plt not supported by your assembler-mshared-library-id= specified without -mid-shared-library-mshared-library-id=%s is not between 0 and %d-msim Use simulator runtime.-msim Use simulator runtime.-msimple-fpu option ignored-msingle-float and -msoft-float cannot both be specified-msingle-float option equivalent to -mhard-float-mstack-guard implies use of -mstack-size-mstring is not supported on little endian systems-mstringop-strategy=rep_8byte not supported for 32-bit code-mtoc-fusion requires 64-bit-mtoc-fusion requires medium/large code model-mtraceback= Select full, part, or no traceback table.-mtune= Schedule code for given CPU.-mtune= expects mn10300, am33, am33-2, or am34-mtune=CPU Optimize for CPU.-mvsx and -mno-altivec are incompatible-mvsx and -mpaired are incompatible-mvsx needs indexed addressing-mvsx requires hardware floating point-mxl-multiply-high can be used only with -mcpu=v6.00.a or greater-mxl-multiply-high requires -mno-xl-soft-mul-pg and -fomit-frame-pointer are incompatible-pie is not supported in this configuration-pipe ignored because -save-temps specified-pipe not supported-private_bundle not allowed with -dynamiclib-trigraphs Support ISO C trigraphs..NOT. operator in expression at %L must have a LOGICAL operand128-bit long double not supported for VAX floats2 byte cop instructions are not allowed in 64-bit VLIW mode31 bit ABI.387 instruction set disabled, using SSE arithmetics64 bit ABI.64-bit ABI not supported in ESA/390 mode !